WEBVTT Kind: captions Language: en 00:00:00.510 --> 00:00:21.349 align:start position:0% [Music] 00:00:21.349 --> 00:00:21.359 align:start position:0% 00:00:21.359 --> 00:00:23.550 align:start position:0% so<00:00:21.720> let's<00:00:21.920> wait<00:00:22.080> for<00:00:22.199> the<00:00:22.320> slide<00:00:22.680> but<00:00:22.880> yeah 00:00:23.550 --> 00:00:23.560 align:start position:0% so let's wait for the slide but yeah 00:00:23.560 --> 00:00:25.150 align:start position:0% so let's wait for the slide but yeah first<00:00:23.840> it's<00:00:24.119> really<00:00:24.359> nice<00:00:24.560> to<00:00:24.680> be<00:00:24.840> here<00:00:25.039> and 00:00:25.150 --> 00:00:25.160 align:start position:0% first it's really nice to be here and 00:00:25.160 --> 00:00:27.349 align:start position:0% first it's really nice to be here and I'm<00:00:25.480> thankful<00:00:26.000> to<00:00:26.160> be<00:00:26.320> invited<00:00:26.679> to<00:00:26.800> speak<00:00:27.039> here 00:00:27.349 --> 00:00:27.359 align:start position:0% I'm thankful to be invited to speak here 00:00:27.359 --> 00:00:30.550 align:start position:0% I'm thankful to be invited to speak here today<00:00:28.359> so<00:00:28.920> why<00:00:29.080> am<00:00:29.279> I<00:00:29.480> speaking<00:00:30.000> about<00:00:30.240> smart 00:00:30.550 --> 00:00:30.560 align:start position:0% today so why am I speaking about smart 00:00:30.560 --> 00:00:32.990 align:start position:0% today so why am I speaking about smart contract<00:00:31.000> security<00:00:31.800> um<00:00:32.200> could<00:00:32.399> be<00:00:32.559> seen<00:00:32.800> as 00:00:32.990 --> 00:00:33.000 align:start position:0% contract security um could be seen as 00:00:33.000 --> 00:00:35.350 align:start position:0% contract security um could be seen as bit<00:00:33.200> ironic<00:00:33.559> for<00:00:33.760> some<00:00:34.120> but<00:00:34.960> actually<00:00:35.239> I've 00:00:35.350 --> 00:00:35.360 align:start position:0% bit ironic for some but actually I've 00:00:35.360 --> 00:00:38.110 align:start position:0% bit ironic for some but actually I've worked<00:00:35.640> for<00:00:36.079> ethereum<00:00:36.600> since<00:00:37.440> two<00:00:37.640> over<00:00:37.879> two 00:00:38.110 --> 00:00:38.120 align:start position:0% worked for ethereum since two over two 00:00:38.120 --> 00:00:40.510 align:start position:0% worked for ethereum since two over two years<00:00:38.360> now<00:00:39.000> and<00:00:39.200> actually<00:00:39.480> my<00:00:39.680> job<00:00:40.039> was<00:00:40.280> to 00:00:40.510 --> 00:00:40.520 align:start position:0% years now and actually my job was to 00:00:40.520 --> 00:00:43.389 align:start position:0% years now and actually my job was to prevent<00:00:40.879> hard<00:00:41.120> fors<00:00:41.680> so<00:00:41.840> to<00:00:42.039> say<00:00:42.879> because<00:00:43.280> I 00:00:43.389 --> 00:00:43.399 align:start position:0% prevent hard fors so to say because I 00:00:43.399 --> 00:00:46.110 align:start position:0% prevent hard fors so to say because I was<00:00:43.640> working<00:00:44.079> on<00:00:44.920> consensus<00:00:45.480> tests<00:00:45.960> and 00:00:46.110 --> 00:00:46.120 align:start position:0% was working on consensus tests and 00:00:46.120 --> 00:00:47.790 align:start position:0% was working on consensus tests and working<00:00:46.480> on<00:00:46.800> getting<00:00:47.039> all<00:00:47.239> the<00:00:47.360> clients<00:00:47.640> to 00:00:47.790 --> 00:00:47.800 align:start position:0% working on getting all the clients to 00:00:47.800 --> 00:00:49.990 align:start position:0% working on getting all the clients to sync<00:00:48.079> and<00:00:48.199> vote<00:00:48.440> thousands<00:00:48.719> of<00:00:48.920> tests<00:00:49.320> and 00:00:49.990 --> 00:00:50.000 align:start position:0% sync and vote thousands of tests and 00:00:50.000 --> 00:00:51.990 align:start position:0% sync and vote thousands of tests and would<00:00:50.199> be<00:00:50.320> so<00:00:50.520> bold<00:00:50.840> to<00:00:51.000> say<00:00:51.239> that<00:00:51.360> I<00:00:51.559> prevented 00:00:51.990 --> 00:00:52.000 align:start position:0% would be so bold to say that I prevented 00:00:52.000 --> 00:00:55.029 align:start position:0% would be so bold to say that I prevented a<00:00:52.079> lot<00:00:52.199> of<00:00:52.359> hard<00:00:52.600> Forks<00:00:53.079> in<00:00:53.239> sense<00:00:53.520> of<00:00:53.960> client 00:00:55.029 --> 00:00:55.039 align:start position:0% a lot of hard Forks in sense of client 00:00:55.039 --> 00:00:58.630 align:start position:0% a lot of hard Forks in sense of client consensus<00:00:56.520> um<00:00:57.520> and<00:00:57.760> now<00:00:57.960> through<00:00:58.239> recent 00:00:58.630 --> 00:00:58.640 align:start position:0% consensus um and now through recent 00:00:58.640 --> 00:01:01.189 align:start position:0% consensus um and now through recent experiences<00:00:59.239> I<00:00:59.359> learned<00:00:59.559> the<00:00:59.680> hard<00:01:00.079> way<00:01:00.480> um 00:01:01.189 --> 00:01:01.199 align:start position:0% experiences I learned the hard way um 00:01:01.199 --> 00:01:03.110 align:start position:0% experiences I learned the hard way um how<00:01:01.399> important<00:01:01.800> smart<00:01:02.120> contact<00:01:02.800> smart 00:01:03.110 --> 00:01:03.120 align:start position:0% how important smart contact smart 00:01:03.120 --> 00:01:04.590 align:start position:0% how important smart contact smart contact<00:01:03.519> security<00:01:03.960> is<00:01:04.119> and<00:01:04.280> that's<00:01:04.400> why<00:01:04.519> I 00:01:04.590 --> 00:01:04.600 align:start position:0% contact security is and that's why I 00:01:04.600 --> 00:01:06.590 align:start position:0% contact security is and that's why I wanted<00:01:04.760> to<00:01:04.920> talk<00:01:05.119> about<00:01:05.280> it 00:01:06.590 --> 00:01:06.600 align:start position:0% wanted to talk about it 00:01:06.600 --> 00:01:10.469 align:start position:0% wanted to talk about it today<00:01:07.600> see<00:01:07.960> so<00:01:08.159> you<00:01:08.280> know<00:01:08.479> about<00:01:08.720> the<00:01:08.880> da<00:01:09.520> um<00:01:10.360> I 00:01:10.469 --> 00:01:10.479 align:start position:0% today see so you know about the da um I 00:01:10.479 --> 00:01:12.670 align:start position:0% today see so you know about the da um I was<00:01:10.920> mainly<00:01:11.320> responsible<00:01:11.759> for<00:01:11.960> writing<00:01:12.360> da 00:01:12.670 --> 00:01:12.680 align:start position:0% was mainly responsible for writing da 00:01:12.680 --> 00:01:17.070 align:start position:0% was mainly responsible for writing da smart<00:01:13.479> contract<00:01:14.640> so<00:01:15.640> on<00:01:15.799> 17th<00:01:16.240> of<00:01:16.360> June<00:01:16.960> there 00:01:17.070 --> 00:01:17.080 align:start position:0% smart contract so on 17th of June there 00:01:17.080 --> 00:01:19.710 align:start position:0% smart contract so on 17th of June there was<00:01:17.200> an<00:01:17.400> attack<00:01:17.680> robbing<00:01:18.159> 3.5<00:01:19.080> million<00:01:19.360> ether 00:01:19.710 --> 00:01:19.720 align:start position:0% was an attack robbing 3.5 million ether 00:01:19.720 --> 00:01:22.030 align:start position:0% was an attack robbing 3.5 million ether out<00:01:19.840> of<00:01:20.000> this<00:01:20.320> small<00:01:20.759> contract<00:01:21.360> by<00:01:21.520> using<00:01:21.840> the 00:01:22.030 --> 00:01:22.040 align:start position:0% out of this small contract by using the 00:01:22.040 --> 00:01:25.109 align:start position:0% out of this small contract by using the re-entry<00:01:23.000> exploit<00:01:24.000> um<00:01:24.439> we<00:01:24.560> have<00:01:24.680> heard<00:01:24.920> about 00:01:25.109 --> 00:01:25.119 align:start position:0% re-entry exploit um we have heard about 00:01:25.119 --> 00:01:26.510 align:start position:0% re-entry exploit um we have heard about this<00:01:25.320> before<00:01:25.600> this<00:01:25.799> conference<00:01:26.159> so<00:01:26.280> I<00:01:26.360> will 00:01:26.510 --> 00:01:26.520 align:start position:0% this before this conference so I will 00:01:26.520 --> 00:01:29.270 align:start position:0% this before this conference so I will not<00:01:26.680> go<00:01:26.799> into<00:01:27.040> details<00:01:27.439> how<00:01:27.600> this<00:01:28.040> works<00:01:29.040> but 00:01:29.270 --> 00:01:29.280 align:start position:0% not go into details how this works but 00:01:29.280 --> 00:01:31.310 align:start position:0% not go into details how this works but those<00:01:29.479> were<00:01:29.640> the<00:01:29.720> L<00:01:30.079> of<00:01:30.240> code<00:01:30.560> in<00:01:30.680> the<00:01:30.840> Dow 00:01:31.310 --> 00:01:31.320 align:start position:0% those were the L of code in the Dow 00:01:31.320 --> 00:01:33.710 align:start position:0% those were the L of code in the Dow itself<00:01:32.320> um<00:01:32.560> basically<00:01:32.960> there<00:01:33.079> was<00:01:33.200> this<00:01:33.399> one 00:01:33.710 --> 00:01:33.720 align:start position:0% itself um basically there was this one 00:01:33.720 --> 00:01:36.990 align:start position:0% itself um basically there was this one function<00:01:34.040> with<00:01:34.840> with<00:01:35.399> reward<00:01:35.720> four<00:01:36.200> which<00:01:36.439> was 00:01:36.990 --> 00:01:37.000 align:start position:0% function with with reward four which was 00:01:37.000 --> 00:01:40.190 align:start position:0% function with with reward four which was vulnerable<00:01:37.439> to<00:01:37.600> this 00:01:40.190 --> 00:01:40.200 align:start position:0% 00:01:40.200 --> 00:01:43.350 align:start position:0% exploit<00:01:41.200> so<00:01:42.159> what<00:01:42.320> can<00:01:42.439> we<00:01:42.560> learn<00:01:42.840> from<00:01:43.040> all<00:01:43.159> of 00:01:43.350 --> 00:01:43.360 align:start position:0% exploit so what can we learn from all of 00:01:43.360 --> 00:01:44.749 align:start position:0% exploit so what can we learn from all of this<00:01:43.600> there's<00:01:43.799> a<00:01:43.920> lot<00:01:44.040> of<00:01:44.159> things<00:01:44.399> happen 00:01:44.749 --> 00:01:44.759 align:start position:0% this there's a lot of things happen 00:01:44.759 --> 00:01:46.910 align:start position:0% this there's a lot of things happen there<00:01:44.960> yesterday<00:01:45.399> and<00:01:45.520> I<00:01:45.640> mean<00:01:46.479> um<00:01:46.640> I<00:01:46.719> will 00:01:46.910 --> 00:01:46.920 align:start position:0% there yesterday and I mean um I will 00:01:46.920 --> 00:01:48.630 align:start position:0% there yesterday and I mean um I will repeat<00:01:47.240> some<00:01:47.399> of<00:01:47.520> them<00:01:47.719> of<00:01:47.840> course<00:01:48.200> but<00:01:48.399> give 00:01:48.630 --> 00:01:48.640 align:start position:0% repeat some of them of course but give 00:01:48.640 --> 00:01:50.590 align:start position:0% repeat some of them of course but give my<00:01:48.880> personal<00:01:49.320> perspective<00:01:49.719> on<00:01:49.840> some<00:01:50.000> of<00:01:50.159> those 00:01:50.590 --> 00:01:50.600 align:start position:0% my personal perspective on some of those 00:01:50.600 --> 00:01:53.910 align:start position:0% my personal perspective on some of those things<00:01:51.600> first<00:01:51.799> of<00:01:51.960> all<00:01:52.680> cap<00:01:52.960> smart 00:01:53.910 --> 00:01:53.920 align:start position:0% things first of all cap smart 00:01:53.920 --> 00:01:57.230 align:start position:0% things first of all cap smart contracts<00:01:54.920> um<00:01:55.399> it's<00:01:55.719> very<00:01:56.039> early<00:01:56.479> days<00:01:56.880> and<00:01:57.039> we 00:01:57.230 --> 00:01:57.240 align:start position:0% contracts um it's very early days and we 00:01:57.240 --> 00:02:00.429 align:start position:0% contracts um it's very early days and we lack<00:01:57.880> experience<00:01:58.880> meaning<00:01:59.600> we<00:01:59.960> just<00:02:00.119> need<00:02:00.280> to 00:02:00.429 --> 00:02:00.439 align:start position:0% lack experience meaning we just need to 00:02:00.439 --> 00:02:03.270 align:start position:0% lack experience meaning we just need to learn<00:02:00.759> some<00:02:01.079> lessons<00:02:01.680> before<00:02:02.200> to<00:02:02.399> know<00:02:02.840> which 00:02:03.270 --> 00:02:03.280 align:start position:0% learn some lessons before to know which 00:02:03.280 --> 00:02:05.789 align:start position:0% learn some lessons before to know which kind<00:02:03.479> of<00:02:03.640> bugs<00:02:04.000> we<00:02:04.119> can<00:02:04.280> do<00:02:05.039> if<00:02:05.159> you<00:02:05.360> just<00:02:05.560> look 00:02:05.789 --> 00:02:05.799 align:start position:0% kind of bugs we can do if you just look 00:02:05.799 --> 00:02:07.070 align:start position:0% kind of bugs we can do if you just look at 00:02:07.070 --> 00:02:07.080 align:start position:0% at 00:02:07.080 --> 00:02:09.869 align:start position:0% at the<00:02:08.080> version<00:02:08.479> numbers<00:02:08.959> of<00:02:09.080> the<00:02:09.239> current 00:02:09.869 --> 00:02:09.879 align:start position:0% the version numbers of the current 00:02:09.879 --> 00:02:12.229 align:start position:0% the version numbers of the current software<00:02:10.879> you<00:02:11.039> can<00:02:11.239> get<00:02:11.360> a<00:02:11.520> feeling<00:02:11.920> of<00:02:12.080> how 00:02:12.229 --> 00:02:12.239 align:start position:0% software you can get a feeling of how 00:02:12.239 --> 00:02:14.309 align:start position:0% software you can get a feeling of how early<00:02:12.520> it<00:02:12.680> is<00:02:12.959> some<00:02:13.360> solidity<00:02:13.959> actually<00:02:14.200> has 00:02:14.309 --> 00:02:14.319 align:start position:0% early it is some solidity actually has 00:02:14.319 --> 00:02:17.350 align:start position:0% early it is some solidity actually has not<00:02:14.519> been<00:02:14.680> released<00:02:15.160> yet<00:02:15.360> as<00:02:15.480> a<00:02:15.599> 1.0<00:02:16.360> version 00:02:17.350 --> 00:02:17.360 align:start position:0% not been released yet as a 1.0 version 00:02:17.360 --> 00:02:19.390 align:start position:0% not been released yet as a 1.0 version um<00:02:17.879> froner<00:02:18.400> has<00:02:18.519> been<00:02:18.599> launched<00:02:18.920> for<00:02:19.080> about<00:02:19.239> a 00:02:19.390 --> 00:02:19.400 align:start position:0% um froner has been launched for about a 00:02:19.400 --> 00:02:23.030 align:start position:0% um froner has been launched for about a year<00:02:19.920> ago<00:02:20.920> so<00:02:21.160> it's<00:02:21.360> all<00:02:22.120> very<00:02:22.319> early<00:02:22.640> days<00:02:22.920> we 00:02:23.030 --> 00:02:23.040 align:start position:0% year ago so it's all very early days we 00:02:23.040 --> 00:02:24.630 align:start position:0% year ago so it's all very early days we have<00:02:23.200> a<00:02:23.400> the<00:02:23.519> number<00:02:23.760> of<00:02:24.000> operating 00:02:24.630 --> 00:02:24.640 align:start position:0% have a the number of operating 00:02:24.640 --> 00:02:26.550 align:start position:0% have a the number of operating decentralized<00:02:25.319> application<00:02:25.720> is<00:02:25.920> also<00:02:26.160> still 00:02:26.550 --> 00:02:26.560 align:start position:0% decentralized application is also still 00:02:26.560 --> 00:02:28.070 align:start position:0% decentralized application is also still very 00:02:28.070 --> 00:02:28.080 align:start position:0% very 00:02:28.080 --> 00:02:31.630 align:start position:0% very low<00:02:29.080> um<00:02:29.480> retail<00:02:30.080> suggested<00:02:30.560> in<00:02:30.680> a<00:02:31.000> blog<00:02:31.319> post 00:02:31.630 --> 00:02:31.640 align:start position:0% low um retail suggested in a blog post 00:02:31.640 --> 00:02:33.270 align:start position:0% low um retail suggested in a blog post that<00:02:31.840> for<00:02:32.000> example<00:02:32.360> right<00:02:32.519> now<00:02:32.720> a<00:02:32.920> cap<00:02:33.160> of 00:02:33.270 --> 00:02:33.280 align:start position:0% that for example right now a cap of 00:02:33.280 --> 00:02:35.790 align:start position:0% that for example right now a cap of about<00:02:33.400> $10<00:02:33.680> million<00:02:34.200> seems<00:02:34.480> about<00:02:34.840> right<00:02:35.640> um 00:02:35.790 --> 00:02:35.800 align:start position:0% about $10 million seems about right um 00:02:35.800 --> 00:02:38.589 align:start position:0% about $10 million seems about right um it's<00:02:36.480> it's<00:02:36.599> an<00:02:36.800> individual<00:02:37.480> decision<00:02:38.280> but<00:02:38.440> of 00:02:38.589 --> 00:02:38.599 align:start position:0% it's it's an individual decision but of 00:02:38.599 --> 00:02:40.670 align:start position:0% it's it's an individual decision but of course<00:02:39.319> would<00:02:39.480> have<00:02:39.640> been<00:02:39.840> nice<00:02:40.120> if<00:02:40.280> the<00:02:40.400> Dow 00:02:40.670 --> 00:02:40.680 align:start position:0% course would have been nice if the Dow 00:02:40.680 --> 00:02:42.949 align:start position:0% course would have been nice if the Dow would<00:02:40.800> have<00:02:41.000> had<00:02:41.239> such<00:02:41.400> a<00:02:41.599> cap<00:02:42.319> um<00:02:42.720> but<00:02:42.879> of 00:02:42.949 --> 00:02:42.959 align:start position:0% would have had such a cap um but of 00:02:42.959 --> 00:02:44.149 align:start position:0% would have had such a cap um but of course<00:02:43.159> nobody<00:02:43.440> did<00:02:43.640> know<00:02:43.800> that<00:02:43.920> it<00:02:44.000> would 00:02:44.149 --> 00:02:44.159 align:start position:0% course nobody did know that it would 00:02:44.159 --> 00:02:47.190 align:start position:0% course nobody did know that it would rise<00:02:44.400> to<00:02:44.560> such<00:02:44.720> a<00:02:44.959> size 00:02:47.190 --> 00:02:47.200 align:start position:0% rise to such a size 00:02:47.200 --> 00:02:49.110 align:start position:0% rise to such a size so<00:02:48.200> next 00:02:49.110 --> 00:02:49.120 align:start position:0% so next 00:02:49.120 --> 00:02:51.949 align:start position:0% so next one<00:02:50.120> former<00:02:50.560> proof<00:02:50.800> verification<00:02:51.519> I<00:02:51.599> will<00:02:51.760> not 00:02:51.949 --> 00:02:51.959 align:start position:0% one former proof verification I will not 00:02:51.959 --> 00:02:53.390 align:start position:0% one former proof verification I will not go<00:02:52.120> into<00:02:52.360> this<00:02:52.519> we<00:02:52.640> have<00:02:52.760> heard<00:02:52.920> about<00:02:53.120> a<00:02:53.200> lot 00:02:53.390 --> 00:02:53.400 align:start position:0% go into this we have heard about a lot 00:02:53.400 --> 00:02:55.710 align:start position:0% go into this we have heard about a lot of<00:02:53.519> this<00:02:53.680> yesterday<00:02:54.200> but<00:02:54.400> yes<00:02:54.840> very<00:02:55.239> important 00:02:55.710 --> 00:02:55.720 align:start position:0% of this yesterday but yes very important 00:02:55.720 --> 00:02:58.670 align:start position:0% of this yesterday but yes very important topic<00:02:56.040> I<00:02:56.159> hope<00:02:56.360> we<00:02:56.560> make<00:02:57.560> to<00:02:58.040> make<00:02:58.200> continuous 00:02:58.670 --> 00:02:58.680 align:start position:0% topic I hope we make to make continuous 00:02:58.680 --> 00:03:00.390 align:start position:0% topic I hope we make to make continuous progress<00:02:59.040> on<00:02:59.159> this<00:02:59.400> topic 00:03:00.390 --> 00:03:00.400 align:start position:0% progress on this topic 00:03:00.400 --> 00:03:03.830 align:start position:0% progress on this topic invariant<00:03:01.239> checks<00:03:02.239> so<00:03:02.440> basically<00:03:02.840> you<00:03:02.959> can 00:03:03.830 --> 00:03:03.840 align:start position:0% invariant checks so basically you can 00:03:03.840 --> 00:03:05.869 align:start position:0% invariant checks so basically you can write<00:03:04.159> see<00:03:04.440> that<00:03:04.640> your<00:03:04.879> smart<00:03:05.239> contract<00:03:05.680> has 00:03:05.869 --> 00:03:05.879 align:start position:0% write see that your smart contract has 00:03:05.879 --> 00:03:08.430 align:start position:0% write see that your smart contract has certain<00:03:06.319> invariant<00:03:07.319> such<00:03:07.560> as<00:03:07.840> for<00:03:08.000> the<00:03:08.120> Dow 00:03:08.430 --> 00:03:08.440 align:start position:0% certain invariant such as for the Dow 00:03:08.440 --> 00:03:09.589 align:start position:0% certain invariant such as for the Dow this<00:03:08.599> would<00:03:08.760> have<00:03:08.879> been<00:03:09.080> that<00:03:09.239> the<00:03:09.360> total 00:03:09.589 --> 00:03:09.599 align:start position:0% this would have been that the total 00:03:09.599 --> 00:03:11.350 align:start position:0% this would have been that the total Supply<00:03:09.959> is<00:03:10.080> smaller<00:03:10.440> than<00:03:10.599> the<00:03:10.720> balance<00:03:11.040> Plus 00:03:11.350 --> 00:03:11.360 align:start position:0% Supply is smaller than the balance Plus 00:03:11.360 --> 00:03:14.710 align:start position:0% Supply is smaller than the balance Plus reward<00:03:11.680> tokens<00:03:12.680> and<00:03:12.840> then<00:03:13.120> after<00:03:13.599> every 00:03:14.710 --> 00:03:14.720 align:start position:0% reward tokens and then after every 00:03:14.720 --> 00:03:17.350 align:start position:0% reward tokens and then after every function<00:03:15.720> um<00:03:16.000> you<00:03:16.120> can<00:03:16.360> check<00:03:16.640> if<00:03:16.760> the<00:03:16.879> invance 00:03:17.350 --> 00:03:17.360 align:start position:0% function um you can check if the invance 00:03:17.360 --> 00:03:18.430 align:start position:0% function um you can check if the invance still 00:03:18.430 --> 00:03:18.440 align:start position:0% still 00:03:18.440 --> 00:03:22.390 align:start position:0% still hold<00:03:19.440> it's<00:03:20.080> reduces<00:03:20.519> of<00:03:20.680> course<00:03:20.879> the<00:03:21.400> risk 00:03:22.390 --> 00:03:22.400 align:start position:0% hold it's reduces of course the risk 00:03:22.400 --> 00:03:25.190 align:start position:0% hold it's reduces of course the risk then<00:03:22.680> this<00:03:22.799> is<00:03:23.000> a<00:03:23.799> interesting<00:03:24.280> topic 00:03:25.190 --> 00:03:25.200 align:start position:0% then this is a interesting topic 00:03:25.200 --> 00:03:26.990 align:start position:0% then this is a interesting topic centralization<00:03:26.200> of<00:03:26.360> course<00:03:26.599> we<00:03:26.720> want<00:03:26.879> to 00:03:26.990 --> 00:03:27.000 align:start position:0% centralization of course we want to 00:03:27.000 --> 00:03:28.910 align:start position:0% centralization of course we want to build<00:03:27.360> decentralized<00:03:28.200> application<00:03:28.760> that's 00:03:28.910 --> 00:03:28.920 align:start position:0% build decentralized application that's 00:03:28.920 --> 00:03:31.270 align:start position:0% build decentralized application that's our<00:03:29.120> main<00:03:29.360> goal<00:03:29.640> and<00:03:29.959> one<00:03:30.080> of<00:03:30.239> the<00:03:30.720> weaknesses 00:03:31.270 --> 00:03:31.280 align:start position:0% our main goal and one of the weaknesses 00:03:31.280 --> 00:03:33.429 align:start position:0% our main goal and one of the weaknesses so<00:03:31.560> to<00:03:31.720> say<00:03:31.840> of<00:03:31.959> the<00:03:32.040> Dow<00:03:32.439> was<00:03:32.920> that<00:03:33.080> it<00:03:33.200> was 00:03:33.429 --> 00:03:33.439 align:start position:0% so to say of the Dow was that it was 00:03:33.439 --> 00:03:35.470 align:start position:0% so to say of the Dow was that it was really<00:03:33.879> decentralized<00:03:34.720> that<00:03:34.920> we<00:03:35.080> had<00:03:35.200> no 00:03:35.470 --> 00:03:35.480 align:start position:0% really decentralized that we had no 00:03:35.480 --> 00:03:37.949 align:start position:0% really decentralized that we had no control<00:03:35.959> nobody<00:03:36.319> had<00:03:36.480> any<00:03:36.720> control<00:03:37.120> over<00:03:37.360> it 00:03:37.949 --> 00:03:37.959 align:start position:0% control nobody had any control over it 00:03:37.959 --> 00:03:39.630 align:start position:0% control nobody had any control over it and<00:03:38.080> this<00:03:38.200> was<00:03:38.400> the<00:03:38.599> problem<00:03:38.959> in<00:03:39.080> the<00:03:39.439> in<00:03:39.560> the 00:03:39.630 --> 00:03:39.640 align:start position:0% and this was the problem in the in the 00:03:39.640 --> 00:03:43.350 align:start position:0% and this was the problem in the in the end<00:03:39.879> because<00:03:40.120> nobody<00:03:40.439> could<00:03:40.599> save<00:03:40.879> the<00:03:41.280> Dow<00:03:42.360> um 00:03:43.350 --> 00:03:43.360 align:start position:0% end because nobody could save the Dow um 00:03:43.360 --> 00:03:45.229 align:start position:0% end because nobody could save the Dow um only<00:03:43.680> the<00:03:43.840> community<00:03:44.280> by<00:03:44.400> doing<00:03:44.640> a<00:03:44.720> hot<00:03:44.920> for 00:03:45.229 --> 00:03:45.239 align:start position:0% only the community by doing a hot for 00:03:45.239 --> 00:03:46.670 align:start position:0% only the community by doing a hot for which<00:03:45.519> of<00:03:45.640> course<00:03:45.879> it's<00:03:46.000> a<00:03:46.080> horrible<00:03:46.439> option 00:03:46.670 --> 00:03:46.680 align:start position:0% which of course it's a horrible option 00:03:46.680 --> 00:03:49.670 align:start position:0% which of course it's a horrible option to<00:03:46.879> do<00:03:47.879> so<00:03:48.120> we<00:03:48.239> need<00:03:48.400> to<00:03:48.560> go<00:03:48.840> stepwise<00:03:49.480> from 00:03:49.670 --> 00:03:49.680 align:start position:0% to do so we need to go stepwise from 00:03:49.680 --> 00:03:52.149 align:start position:0% to do so we need to go stepwise from centralization<00:03:50.439> to<00:03:51.079> decentralization<00:03:52.079> if 00:03:52.149 --> 00:03:52.159 align:start position:0% centralization to decentralization if 00:03:52.159 --> 00:03:53.789 align:start position:0% centralization to decentralization if you<00:03:52.319> think<00:03:52.519> about<00:03:52.720> ethereum<00:03:53.159> we<00:03:53.280> had<00:03:53.400> Olympic 00:03:53.789 --> 00:03:53.799 align:start position:0% you think about ethereum we had Olympic 00:03:53.799 --> 00:03:55.589 align:start position:0% you think about ethereum we had Olympic test<00:03:54.040> net<00:03:54.200> then<00:03:54.319> we<00:03:54.400> had<00:03:54.519> the<00:03:54.599> froner<00:03:55.079> test<00:03:55.360> net 00:03:55.589 --> 00:03:55.599 align:start position:0% test net then we had the froner test net 00:03:55.599 --> 00:03:57.509 align:start position:0% test net then we had the froner test net where<00:03:55.760> we<00:03:55.879> had<00:03:56.040> those<00:03:56.280> canaries<00:03:56.920> I<00:03:57.040> had<00:03:57.200> one<00:03:57.319> of 00:03:57.509 --> 00:03:57.519 align:start position:0% where we had those canaries I had one of 00:03:57.519 --> 00:03:59.470 align:start position:0% where we had those canaries I had one of those<00:03:57.760> keys<00:03:58.439> where<00:03:58.680> basically<00:03:59.040> two<00:03:59.239> out<00:03:59.400> of 00:03:59.470 --> 00:03:59.480 align:start position:0% those keys where basically two out of 00:03:59.480 --> 00:04:01.630 align:start position:0% those keys where basically two out of four<00:04:00.079> keyh<00:04:00.319> holders<00:04:00.760> could<00:04:01.079> more<00:04:01.280> or<00:04:01.439> less 00:04:01.630 --> 00:04:01.640 align:start position:0% four keyh holders could more or less 00:04:01.640 --> 00:04:03.789 align:start position:0% four keyh holders could more or less switch<00:04:01.879> off<00:04:02.040> the<00:04:02.280> miners<00:04:03.280> um<00:04:03.439> if<00:04:03.560> they<00:04:03.680> would 00:04:03.789 --> 00:04:03.799 align:start position:0% switch off the miners um if they would 00:04:03.799 --> 00:04:05.949 align:start position:0% switch off the miners um if they would listen<00:04:04.040> to<00:04:04.159> the<00:04:04.319> canaries<00:04:05.319> we<00:04:05.480> had<00:04:05.799> have 00:04:05.949 --> 00:04:05.959 align:start position:0% listen to the canaries we had have 00:04:05.959 --> 00:04:07.550 align:start position:0% listen to the canaries we had have Homestead<00:04:06.480> that<00:04:06.599> we<00:04:06.720> have<00:04:06.840> this<00:04:07.319> difficulty 00:04:07.550 --> 00:04:07.560 align:start position:0% Homestead that we have this difficulty 00:04:07.560 --> 00:04:09.309 align:start position:0% Homestead that we have this difficulty increase<00:04:08.239> which<00:04:08.360> means<00:04:08.640> we<00:04:08.760> need<00:04:08.920> to<00:04:09.079> have<00:04:09.200> a 00:04:09.309 --> 00:04:09.319 align:start position:0% increase which means we need to have a 00:04:09.319 --> 00:04:12.069 align:start position:0% increase which means we need to have a hard<00:04:09.519> fork<00:04:09.879> in<00:04:10.040> about<00:04:10.239> a<00:04:10.360> year<00:04:10.519> or<00:04:10.680> so<00:04:11.680> and 00:04:12.069 --> 00:04:12.079 align:start position:0% hard fork in about a year or so and 00:04:12.079 --> 00:04:14.350 align:start position:0% hard fork in about a year or so and there's<00:04:12.280> only<00:04:12.480> a<00:04:12.599> couple<00:04:12.840> of<00:04:12.959> people<00:04:13.239> able<00:04:13.480> to 00:04:14.350 --> 00:04:14.360 align:start position:0% there's only a couple of people able to 00:04:14.360 --> 00:04:16.670 align:start position:0% there's only a couple of people able to code<00:04:14.760> up<00:04:15.280> the<00:04:15.400> next<00:04:15.760> version<00:04:15.959> of<00:04:16.079> ethereum<00:04:16.519> so 00:04:16.670 --> 00:04:16.680 align:start position:0% code up the next version of ethereum so 00:04:16.680 --> 00:04:19.229 align:start position:0% code up the next version of ethereum so it's<00:04:16.880> also<00:04:17.400> kind<00:04:17.600> of<00:04:17.799> centralized<00:04:18.440> still<00:04:19.160> and 00:04:19.229 --> 00:04:19.239 align:start position:0% it's also kind of centralized still and 00:04:19.239 --> 00:04:22.310 align:start position:0% it's also kind of centralized still and we<00:04:19.359> will<00:04:19.600> go<00:04:19.880> step<00:04:20.160> to<00:04:20.440> step<00:04:20.680> to<00:04:20.880> more 00:04:22.310 --> 00:04:22.320 align:start position:0% we will go step to step to more 00:04:22.320 --> 00:04:24.510 align:start position:0% we will go step to step to more decentralization<00:04:23.320> um<00:04:23.800> for<00:04:23.919> the<00:04:24.080> Dow<00:04:24.400> that 00:04:24.510 --> 00:04:24.520 align:start position:0% decentralization um for the Dow that 00:04:24.520 --> 00:04:26.670 align:start position:0% decentralization um for the Dow that have<00:04:24.680> been<00:04:24.840> creators<00:04:25.639> they<00:04:25.800> have<00:04:25.960> been<00:04:26.440> given 00:04:26.670 --> 00:04:26.680 align:start position:0% have been creators they have been given 00:04:26.680 --> 00:04:28.670 align:start position:0% have been creators they have been given a<00:04:26.800> lot<00:04:26.960> of<00:04:27.120> power<00:04:27.520> except<00:04:27.960> of<00:04:28.120> the<00:04:28.280> function 00:04:28.670 --> 00:04:28.680 align:start position:0% a lot of power except of the function 00:04:28.680 --> 00:04:30.670 align:start position:0% a lot of power except of the function split<00:04:29.039> Dow<00:04:29.440> because<00:04:29.880> this<00:04:30.000> was<00:04:30.120> a<00:04:30.320> function 00:04:30.670 --> 00:04:30.680 align:start position:0% split Dow because this was a function 00:04:30.680 --> 00:04:33.110 align:start position:0% split Dow because this was a function meant<00:04:30.960> to<00:04:31.759> as<00:04:31.840> a<00:04:32.000> fail<00:04:32.320> day<00:04:32.520> for<00:04:32.720> malicious 00:04:33.110 --> 00:04:33.120 align:start position:0% meant to as a fail day for malicious 00:04:33.120 --> 00:04:35.070 align:start position:0% meant to as a fail day for malicious creators<00:04:34.120> so<00:04:34.320> that's<00:04:34.520> why<00:04:34.600> they<00:04:34.720> didn't<00:04:34.919> have 00:04:35.070 --> 00:04:35.080 align:start position:0% creators so that's why they didn't have 00:04:35.080 --> 00:04:36.749 align:start position:0% creators so that's why they didn't have control<00:04:35.400> over<00:04:35.600> this<00:04:35.759> function<00:04:36.160> couldn't<00:04:36.400> do 00:04:36.749 --> 00:04:36.759 align:start position:0% control over this function couldn't do 00:04:36.759 --> 00:04:38.870 align:start position:0% control over this function couldn't do anything<00:04:37.759> there's<00:04:38.000> all<00:04:38.120> the<00:04:38.240> other<00:04:38.520> Dows 00:04:38.870 --> 00:04:38.880 align:start position:0% anything there's all the other Dows 00:04:38.880 --> 00:04:40.629 align:start position:0% anything there's all the other Dows Stitcher<00:04:39.280> Dow<00:04:39.520> maker<00:04:39.800> Dow<00:04:40.000> and<00:04:40.120> other<00:04:40.280> Dows<00:04:40.560> in 00:04:40.629 --> 00:04:40.639 align:start position:0% Stitcher Dow maker Dow and other Dows in 00:04:40.639 --> 00:04:43.469 align:start position:0% Stitcher Dow maker Dow and other Dows in the<00:04:40.759> progress<00:04:41.680> which<00:04:41.880> start<00:04:42.520> centralized<00:04:43.199> and 00:04:43.469 --> 00:04:43.479 align:start position:0% the progress which start centralized and 00:04:43.479 --> 00:04:45.749 align:start position:0% the progress which start centralized and will<00:04:43.759> go<00:04:44.440> into<00:04:44.680> decentralization<00:04:45.520> then 00:04:45.749 --> 00:04:45.759 align:start position:0% will go into decentralization then 00:04:45.759 --> 00:04:47.749 align:start position:0% will go into decentralization then question<00:04:45.960> is<00:04:46.080> of<00:04:46.199> course<00:04:46.400> who<00:04:46.560> can<00:04:46.800> control 00:04:47.749 --> 00:04:47.759 align:start position:0% question is of course who can control 00:04:47.759 --> 00:04:50.350 align:start position:0% question is of course who can control for<00:04:47.960> a<00:04:48.120> dow<00:04:48.400> was<00:04:48.560> some<00:04:48.720> token<00:04:49.199> holders<00:04:50.199> it 00:04:50.350 --> 00:04:50.360 align:start position:0% for a dow was some token holders it 00:04:50.360 --> 00:04:51.990 align:start position:0% for a dow was some token holders it could<00:04:50.520> be<00:04:50.639> Central<00:04:50.960> trusted<00:04:51.320> authorities<00:04:51.880> and 00:04:51.990 --> 00:04:52.000 align:start position:0% could be Central trusted authorities and 00:04:52.000 --> 00:04:53.510 align:start position:0% could be Central trusted authorities and there<00:04:52.120> is<00:04:52.280> more<00:04:52.520> but<00:04:52.639> the<00:04:52.759> slides<00:04:53.080> don't<00:04:53.320> show 00:04:53.510 --> 00:04:53.520 align:start position:0% there is more but the slides don't show 00:04:53.520 --> 00:04:55.150 align:start position:0% there is more but the slides don't show it<00:04:53.680> up<00:04:53.840> here<00:04:54.039> right<00:04:54.199> now<00:04:54.639> but<00:04:54.759> it<00:04:54.880> could<00:04:55.000> be 00:04:55.150 --> 00:04:55.160 align:start position:0% it up here right now but it could be 00:04:55.160 --> 00:04:57.230 align:start position:0% it up here right now but it could be something<00:04:55.440> like<00:04:55.680> Community<00:04:56.080> multi<00:04:56.960> it<00:04:57.080> could 00:04:57.230 --> 00:04:57.240 align:start position:0% something like Community multi it could 00:04:57.240 --> 00:04:58.710 align:start position:0% something like Community multi it could be<00:04:57.440> something<00:04:57.720> like<00:04:57.840> a<00:04:57.960> stake<00:04:58.240> vote<00:04:58.520> that<00:04:58.639> you 00:04:58.710 --> 00:04:58.720 align:start position:0% be something like a stake vote that you 00:04:58.720 --> 00:05:00.270 align:start position:0% be something like a stake vote that you build<00:04:58.960> in<00:04:59.120> something<00:04:59.360> your<00:04:59.680> smart<00:04:59.919> contract 00:05:00.270 --> 00:05:00.280 align:start position:0% build in something your smart contract 00:05:00.280 --> 00:05:01.830 align:start position:0% build in something your smart contract when<00:05:00.440> a<00:05:00.520> certain<00:05:00.759> amount<00:05:01.000> of<00:05:01.160> ether<00:05:01.479> holders 00:05:01.830 --> 00:05:01.840 align:start position:0% when a certain amount of ether holders 00:05:01.840 --> 00:05:03.950 align:start position:0% when a certain amount of ether holders vote<00:05:02.080> for<00:05:02.240> it<00:05:02.440> stop<00:05:02.759> something<00:05:03.560> so<00:05:03.720> there<00:05:03.800> are 00:05:03.950 --> 00:05:03.960 align:start position:0% vote for it stop something so there are 00:05:03.960 --> 00:05:05.990 align:start position:0% vote for it stop something so there are certain<00:05:04.240> ways<00:05:04.440> of<00:05:04.600> controlling<00:05:05.160> this<00:05:05.680> but<00:05:05.840> I 00:05:05.990 --> 00:05:06.000 align:start position:0% certain ways of controlling this but I 00:05:06.000 --> 00:05:08.390 align:start position:0% certain ways of controlling this but I think<00:05:06.639> we<00:05:06.800> need<00:05:06.960> to<00:05:07.120> go<00:05:07.320> step<00:05:07.560> by<00:05:07.800> step<00:05:08.120> but 00:05:08.390 --> 00:05:08.400 align:start position:0% think we need to go step by step but 00:05:08.400 --> 00:05:10.670 align:start position:0% think we need to go step by step but also<00:05:08.759> I<00:05:08.840> think<00:05:09.039> it's<00:05:09.280> important<00:05:10.280> that<00:05:10.440> we 00:05:10.670 --> 00:05:10.680 align:start position:0% also I think it's important that we 00:05:10.680 --> 00:05:12.230 align:start position:0% also I think it's important that we really<00:05:10.919> want<00:05:11.120> to<00:05:11.240> build<00:05:11.520> decentralized 00:05:12.230 --> 00:05:12.240 align:start position:0% really want to build decentralized 00:05:12.240 --> 00:05:14.629 align:start position:0% really want to build decentralized application<00:05:12.800> and<00:05:13.000> do<00:05:13.160> not<00:05:13.360> use<00:05:13.560> the<00:05:13.759> Dows<00:05:14.120> an 00:05:14.629 --> 00:05:14.639 align:start position:0% application and do not use the Dows an 00:05:14.639 --> 00:05:16.749 align:start position:0% application and do not use the Dows an excuse<00:05:15.400> to<00:05:15.680> only<00:05:15.880> build<00:05:16.160> centralized 00:05:16.749 --> 00:05:16.759 align:start position:0% excuse to only build centralized 00:05:16.759 --> 00:05:19.350 align:start position:0% excuse to only build centralized applications<00:05:17.720> although<00:05:18.039> it's<00:05:18.680> good<00:05:18.840> to<00:05:19.000> start 00:05:19.350 --> 00:05:19.360 align:start position:0% applications although it's good to start 00:05:19.360 --> 00:05:20.870 align:start position:0% applications although it's good to start like<00:05:19.560> this<00:05:19.840> I<00:05:19.960> don't<00:05:20.160> think<00:05:20.319> it<00:05:20.440> should<00:05:20.600> end 00:05:20.870 --> 00:05:20.880 align:start position:0% like this I don't think it should end 00:05:20.880 --> 00:05:23.150 align:start position:0% like this I don't think it should end like<00:05:21.080> this<00:05:21.600> we<00:05:21.720> should<00:05:21.960> move<00:05:22.199> forward<00:05:22.720> to<00:05:22.919> full 00:05:23.150 --> 00:05:23.160 align:start position:0% like this we should move forward to full 00:05:23.160 --> 00:05:26.629 align:start position:0% like this we should move forward to full decentralization<00:05:24.000> one 00:05:26.629 --> 00:05:26.639 align:start position:0% 00:05:26.639 --> 00:05:29.670 align:start position:0% day<00:05:27.639> okay<00:05:27.880> let's<00:05:28.080> see<00:05:28.240> if<00:05:28.400> this<00:05:28.560> works<00:05:28.919> yeah<00:05:29.479> as 00:05:29.670 --> 00:05:29.680 align:start position:0% day okay let's see if this works yeah as 00:05:29.680 --> 00:05:31.590 align:start position:0% day okay let's see if this works yeah as established<00:05:30.080> security<00:05:30.440> patterns<00:05:31.039> meaning 00:05:31.590 --> 00:05:31.600 align:start position:0% established security patterns meaning 00:05:31.600 --> 00:05:33.909 align:start position:0% established security patterns meaning learning<00:05:32.600> we<00:05:32.720> didn't<00:05:32.960> know<00:05:33.199> about<00:05:33.479> the<00:05:33.639> call 00:05:33.909 --> 00:05:33.919 align:start position:0% learning we didn't know about the call 00:05:33.919 --> 00:05:36.189 align:start position:0% learning we didn't know about the call stack<00:05:34.160> depth<00:05:34.880> call<00:05:35.160> stack<00:05:35.440> depth<00:05:35.759> attack<00:05:36.080> we 00:05:36.189 --> 00:05:36.199 align:start position:0% stack depth call stack depth attack we 00:05:36.199 --> 00:05:37.870 align:start position:0% stack depth call stack depth attack we know<00:05:36.400> about<00:05:36.560> the<00:05:36.639> block<00:05:36.960> gas<00:05:37.160> limit<00:05:37.400> so<00:05:37.600> don't 00:05:37.870 --> 00:05:37.880 align:start position:0% know about the block gas limit so don't 00:05:37.880 --> 00:05:40.870 align:start position:0% know about the block gas limit so don't have<00:05:38.199> arbitary<00:05:38.680> length<00:05:39.280> Loops<00:05:40.280> um<00:05:40.600> we<00:05:40.720> know 00:05:40.870 --> 00:05:40.880 align:start position:0% have arbitary length Loops um we know 00:05:40.880 --> 00:05:44.550 align:start position:0% have arbitary length Loops um we know about<00:05:41.080> we<00:05:41.280> anti<00:05:41.479> exploit<00:05:42.160> now<00:05:43.160> we<00:05:43.319> know<00:05:43.720> about 00:05:44.550 --> 00:05:44.560 align:start position:0% about we anti exploit now we know about 00:05:44.560 --> 00:05:47.790 align:start position:0% about we anti exploit now we know about that<00:05:44.759> Isa<00:05:45.160> sent<00:05:46.039> to<00:05:46.240> a<00:05:46.400> contract<00:05:46.880> without<00:05:47.560> it's 00:05:47.790 --> 00:05:47.800 align:start position:0% that Isa sent to a contract without it's 00:05:47.800 --> 00:05:49.550 align:start position:0% that Isa sent to a contract without it's possible<00:05:48.080> to<00:05:48.199> send<00:05:48.520> EA<00:05:48.840> to<00:05:48.960> a<00:05:49.080> contract 00:05:49.550 --> 00:05:49.560 align:start position:0% possible to send EA to a contract 00:05:49.560 --> 00:05:52.189 align:start position:0% possible to send EA to a contract without<00:05:50.080> any<00:05:50.520> contract<00:05:50.919> invocation<00:05:51.759> so<00:05:51.960> even 00:05:52.189 --> 00:05:52.199 align:start position:0% without any contract invocation so even 00:05:52.199 --> 00:05:55.070 align:start position:0% without any contract invocation so even if<00:05:52.280> you<00:05:52.440> use<00:05:52.680> this<00:05:52.840> modifier<00:05:53.759> payable<00:05:54.759> um<00:05:54.880> or 00:05:55.070 --> 00:05:55.080 align:start position:0% if you use this modifier payable um or 00:05:55.080 --> 00:05:56.629 align:start position:0% if you use this modifier payable um or you<00:05:55.199> don't<00:05:55.400> use<00:05:55.560> it<00:05:55.680> at<00:05:55.840> any<00:05:56.039> function<00:05:56.319> you<00:05:56.440> try 00:05:56.629 --> 00:05:56.639 align:start position:0% you don't use it at any function you try 00:05:56.639 --> 00:05:58.909 align:start position:0% you don't use it at any function you try to<00:05:56.840> avoid<00:05:57.199> getting<00:05:57.520> ether<00:05:57.840> as<00:05:57.960> a<00:05:58.120> contract<00:05:58.680> you 00:05:58.909 --> 00:05:58.919 align:start position:0% to avoid getting ether as a contract you 00:05:58.919 --> 00:06:00.629 align:start position:0% to avoid getting ether as a contract you cannot<00:05:59.240> avoid<00:05:59.520> it<00:05:59.840> because<00:06:00.039> you<00:06:00.160> can<00:06:00.280> use<00:06:00.479> the 00:06:00.629 --> 00:06:00.639 align:start position:0% cannot avoid it because you can use the 00:06:00.639 --> 00:06:03.550 align:start position:0% cannot avoid it because you can use the suicide<00:06:01.120> op<00:06:01.400> codee<00:06:02.039> to<00:06:02.520> transfer<00:06:02.960> ether<00:06:03.240> to<00:06:03.400> a 00:06:03.550 --> 00:06:03.560 align:start position:0% suicide op codee to transfer ether to a 00:06:03.560 --> 00:06:06.510 align:start position:0% suicide op codee to transfer ether to a contract<00:06:04.039> without<00:06:04.440> executing<00:06:04.919> any<00:06:05.080> code<00:06:05.400> for 00:06:06.510 --> 00:06:06.520 align:start position:0% contract without executing any code for 00:06:06.520 --> 00:06:09.430 align:start position:0% contract without executing any code for example<00:06:07.520> um<00:06:08.280> specify<00:06:08.759> the<00:06:08.880> right<00:06:09.039> amount<00:06:09.199> of 00:06:09.430 --> 00:06:09.440 align:start position:0% example um specify the right amount of 00:06:09.440 --> 00:06:11.909 align:start position:0% example um specify the right amount of gas<00:06:09.919> Z<00:06:10.280> versus<00:06:10.560> C<00:06:10.840> depending<00:06:11.160> on<00:06:11.319> what<00:06:11.599> exactly 00:06:11.909 --> 00:06:11.919 align:start position:0% gas Z versus C depending on what exactly 00:06:11.919 --> 00:06:12.909 align:start position:0% gas Z versus C depending on what exactly you<00:06:12.039> want<00:06:12.160> to 00:06:12.909 --> 00:06:12.919 align:start position:0% you want to 00:06:12.919 --> 00:06:15.589 align:start position:0% you want to do<00:06:13.919> you<00:06:14.319> have<00:06:14.400> to<00:06:14.520> be<00:06:14.720> careful<00:06:15.039> with<00:06:15.199> the<00:06:15.319> block 00:06:15.589 --> 00:06:15.599 align:start position:0% do you have to be careful with the block 00:06:15.599 --> 00:06:18.029 align:start position:0% do you have to be careful with the block time<00:06:15.800> stamp<00:06:16.199> because<00:06:16.360> it<00:06:16.479> can<00:06:16.599> be<00:06:17.039> manipulated 00:06:18.029 --> 00:06:18.039 align:start position:0% time stamp because it can be manipulated 00:06:18.039 --> 00:06:20.309 align:start position:0% time stamp because it can be manipulated transaction<00:06:18.639> origin<00:06:19.080> versus<00:06:19.639> message<00:06:19.880> sender 00:06:20.309 --> 00:06:20.319 align:start position:0% transaction origin versus message sender 00:06:20.319 --> 00:06:22.589 align:start position:0% transaction origin versus message sender for<00:06:20.479> example<00:06:21.319> can<00:06:21.440> be<00:06:21.560> used<00:06:21.800> for<00:06:21.919> pishing 00:06:22.589 --> 00:06:22.599 align:start position:0% for example can be used for pishing 00:06:22.599 --> 00:06:26.430 align:start position:0% for example can be used for pishing attacks<00:06:23.599> and<00:06:24.400> much<00:06:24.639> more<00:06:25.639> actually<00:06:25.880> it's<00:06:26.280> bad 00:06:26.430 --> 00:06:26.440 align:start position:0% attacks and much more actually it's bad 00:06:26.440 --> 00:06:27.710 align:start position:0% attacks and much more actually it's bad that<00:06:26.599> the<00:06:26.680> slides<00:06:27.000> are<00:06:27.080> not<00:06:27.240> really<00:06:27.440> working 00:06:27.710 --> 00:06:27.720 align:start position:0% that the slides are not really working 00:06:27.720 --> 00:06:29.309 align:start position:0% that the slides are not really working because<00:06:27.919> there<00:06:28.039> are<00:06:28.199> links<00:06:28.720> coming<00:06:29.000> up<00:06:29.199> it's 00:06:29.309 --> 00:06:29.319 align:start position:0% because there are links coming up it's 00:06:29.319 --> 00:06:30.270 align:start position:0% because there are links coming up it's just 00:06:30.270 --> 00:06:30.280 align:start position:0% just 00:06:30.280 --> 00:06:32.350 align:start position:0% just um<00:06:30.440> there<00:06:30.560> are<00:06:30.800> some<00:06:31.319> very<00:06:31.560> good<00:06:31.759> resources 00:06:32.350 --> 00:06:32.360 align:start position:0% um there are some very good resources 00:06:32.360 --> 00:06:34.510 align:start position:0% um there are some very good resources one<00:06:32.520> is<00:06:32.639> from<00:06:32.800> the<00:06:32.919> consensus<00:06:33.520> website<00:06:34.039> best 00:06:34.510 --> 00:06:34.520 align:start position:0% one is from the consensus website best 00:06:34.520 --> 00:06:37.589 align:start position:0% one is from the consensus website best smart<00:06:34.880> contractors<00:06:35.840> best<00:06:36.240> PR<00:06:36.759> um<00:06:37.319> best 00:06:37.589 --> 00:06:37.599 align:start position:0% smart contractors best PR um best 00:06:37.599 --> 00:06:38.909 align:start position:0% smart contractors best PR um best practice<00:06:37.880> of<00:06:38.000> smart<00:06:38.240> contracts<00:06:38.560> or<00:06:38.680> something 00:06:38.909 --> 00:06:38.919 align:start position:0% practice of smart contracts or something 00:06:38.919 --> 00:06:40.870 align:start position:0% practice of smart contracts or something like<00:06:39.080> this<00:06:39.720> you<00:06:39.919> find<00:06:40.160> on<00:06:40.240> the<00:06:40.400> consensus 00:06:40.870 --> 00:06:40.880 align:start position:0% like this you find on the consensus 00:06:40.880 --> 00:06:44.350 align:start position:0% like this you find on the consensus website<00:06:41.240> it's<00:06:41.440> a<00:06:41.680> really<00:06:41.960> nice<00:06:42.319> overview<00:06:43.360> of 00:06:44.350 --> 00:06:44.360 align:start position:0% website it's a really nice overview of 00:06:44.360 --> 00:06:45.990 align:start position:0% website it's a really nice overview of all<00:06:44.520> the<00:06:44.720> things<00:06:45.120> we<00:06:45.280> need<00:06:45.400> to<00:06:45.560> learn<00:06:45.759> and<00:06:45.919> what 00:06:45.990 --> 00:06:46.000 align:start position:0% all the things we need to learn and what 00:06:46.000 --> 00:06:47.710 align:start position:0% all the things we need to learn and what we<00:06:46.120> have<00:06:46.240> learned<00:06:46.520> up<00:06:46.639> to<00:06:46.800> now<00:06:47.120> also<00:06:47.440> the 00:06:47.710 --> 00:06:47.720 align:start position:0% we have learned up to now also the 00:06:47.720 --> 00:06:49.990 align:start position:0% we have learned up to now also the solidity<00:06:48.639> documentation<00:06:49.360> has<00:06:49.479> a<00:06:49.639> section 00:06:49.990 --> 00:06:50.000 align:start position:0% solidity documentation has a section 00:06:50.000 --> 00:06:52.510 align:start position:0% solidity documentation has a section about<00:06:50.800> um<00:06:51.000> security<00:06:51.400> consideration<00:06:52.080> which<00:06:52.199> is 00:06:52.510 --> 00:06:52.520 align:start position:0% about um security consideration which is 00:06:52.520 --> 00:06:55.189 align:start position:0% about um security consideration which is very<00:06:52.759> good<00:06:53.000> and<00:06:53.360> very<00:06:53.800> helpful<00:06:54.800> we<00:06:54.880> should<00:06:55.120> as 00:06:55.189 --> 00:06:55.199 align:start position:0% very good and very helpful we should as 00:06:55.199 --> 00:06:56.710 align:start position:0% very good and very helpful we should as a<00:06:55.360> community<00:06:55.759> learn<00:06:56.039> and<00:06:56.199> put<00:06:56.400> all<00:06:56.560> those 00:06:56.710 --> 00:06:56.720 align:start position:0% a community learn and put all those 00:06:56.720 --> 00:06:58.629 align:start position:0% a community learn and put all those things<00:06:57.080> together<00:06:57.599> so<00:06:57.759> we<00:06:57.919> can<00:06:58.120> teach<00:06:58.400> other 00:06:58.629 --> 00:06:58.639 align:start position:0% things together so we can teach other 00:06:58.639 --> 00:07:03.270 align:start position:0% things together so we can teach other developers<00:06:59.240> what<00:06:59.360> to<00:06:59.639> look<00:06:59.800> out 00:07:03.270 --> 00:07:03.280 align:start position:0% 00:07:03.280 --> 00:07:08.749 align:start position:0% for<00:07:04.280> let's<00:07:04.520> see<00:07:04.680> if<00:07:04.759> we<00:07:04.879> can<00:07:05.039> get<00:07:05.160> to<00:07:05.280> the<00:07:05.440> next 00:07:08.749 --> 00:07:08.759 align:start position:0% 00:07:08.759 --> 00:07:12.189 align:start position:0% slide<00:07:09.759> yes<00:07:10.280> updatable<00:07:10.919> contracts<00:07:11.680> so<00:07:11.840> the<00:07:12.000> da 00:07:12.189 --> 00:07:12.199 align:start position:0% slide yes updatable contracts so the da 00:07:12.199 --> 00:07:13.589 align:start position:0% slide yes updatable contracts so the da had<00:07:12.280> a<00:07:12.520> possibility<00:07:12.919> of<00:07:13.080> updating<00:07:13.440> the 00:07:13.589 --> 00:07:13.599 align:start position:0% had a possibility of updating the 00:07:13.599 --> 00:07:16.189 align:start position:0% had a possibility of updating the contract<00:07:14.000> through<00:07:14.160> a<00:07:14.360> vote<00:07:15.360> it<00:07:15.560> did<00:07:15.720> take<00:07:15.919> a 00:07:16.189 --> 00:07:16.199 align:start position:0% contract through a vote it did take a 00:07:16.199 --> 00:07:19.950 align:start position:0% contract through a vote it did take a two<00:07:16.440> weeks<00:07:16.919> debating<00:07:17.440> time<00:07:18.160> and<00:07:18.840> DOW<00:07:19.160> 1.1<00:07:19.800> so 00:07:19.950 --> 00:07:19.960 align:start position:0% two weeks debating time and DOW 1.1 so 00:07:19.960 --> 00:07:21.550 align:start position:0% two weeks debating time and DOW 1.1 so to<00:07:20.080> say<00:07:20.240> was<00:07:20.360> work<00:07:20.560> in<00:07:20.759> progress<00:07:21.160> but<00:07:21.280> it<00:07:21.400> was 00:07:21.550 --> 00:07:21.560 align:start position:0% to say was work in progress but it was 00:07:21.560 --> 00:07:25.309 align:start position:0% to say was work in progress but it was too<00:07:22.120> late<00:07:23.319> so<00:07:24.319> I<00:07:24.400> would<00:07:24.599> advise<00:07:24.919> you<00:07:25.039> when<00:07:25.160> you 00:07:25.309 --> 00:07:25.319 align:start position:0% too late so I would advise you when you 00:07:25.319 --> 00:07:26.550 align:start position:0% too late so I would advise you when you smart<00:07:25.680> when<00:07:25.919> when<00:07:26.000> you<00:07:26.080> write<00:07:26.319> smart 00:07:26.550 --> 00:07:26.560 align:start position:0% smart when when you write smart 00:07:26.560 --> 00:07:28.510 align:start position:0% smart when when you write smart contracts<00:07:26.960> to<00:07:27.199> have<00:07:27.360> an<00:07:27.599> option<00:07:27.879> to<00:07:28.120> update 00:07:28.510 --> 00:07:28.520 align:start position:0% contracts to have an option to update 00:07:28.520 --> 00:07:30.390 align:start position:0% contracts to have an option to update them<00:07:28.720> the<00:07:28.840> question<00:07:29.080> is<00:07:29.199> only<00:07:29.680> who<00:07:29.840> can<00:07:30.039> update 00:07:30.390 --> 00:07:30.400 align:start position:0% them the question is only who can update 00:07:30.400 --> 00:07:32.070 align:start position:0% them the question is only who can update them<00:07:30.680> in<00:07:30.800> the<00:07:30.960> beginning<00:07:31.280> it<00:07:31.400> can<00:07:31.560> be<00:07:31.720> you<00:07:31.919> of 00:07:32.070 --> 00:07:32.080 align:start position:0% them in the beginning it can be you of 00:07:32.080 --> 00:07:34.150 align:start position:0% them in the beginning it can be you of course<00:07:32.400> centralized<00:07:33.280> it<00:07:33.400> can<00:07:33.560> be<00:07:33.720> the<00:07:33.879> token 00:07:34.150 --> 00:07:34.160 align:start position:0% course centralized it can be the token 00:07:34.160 --> 00:07:35.430 align:start position:0% course centralized it can be the token holders<00:07:34.520> if<00:07:34.599> you<00:07:34.720> have<00:07:34.879> some<00:07:35.120> in<00:07:35.240> your 00:07:35.430 --> 00:07:35.440 align:start position:0% holders if you have some in your 00:07:35.440 --> 00:07:37.070 align:start position:0% holders if you have some in your application<00:07:36.039> depending<00:07:36.400> on<00:07:36.560> what<00:07:36.680> you're 00:07:37.070 --> 00:07:37.080 align:start position:0% application depending on what you're 00:07:37.080 --> 00:07:40.189 align:start position:0% application depending on what you're building<00:07:38.080> and<00:07:38.479> again<00:07:38.759> could<00:07:38.919> be<00:07:39.080> a<00:07:39.199> multii 00:07:40.189 --> 00:07:40.199 align:start position:0% building and again could be a multii 00:07:40.199 --> 00:07:41.510 align:start position:0% building and again could be a multii maybe<00:07:40.400> a<00:07:40.520> community<00:07:40.840> multi<00:07:41.319> there<00:07:41.400> are 00:07:41.510 --> 00:07:41.520 align:start position:0% maybe a community multi there are 00:07:41.520 --> 00:07:43.070 align:start position:0% maybe a community multi there are different<00:07:41.759> ways<00:07:41.919> of<00:07:42.080> doing<00:07:42.360> this<00:07:42.759> but<00:07:42.919> it's 00:07:43.070 --> 00:07:43.080 align:start position:0% different ways of doing this but it's 00:07:43.080 --> 00:07:44.510 align:start position:0% different ways of doing this but it's important<00:07:43.400> to<00:07:43.560> have<00:07:43.720> at<00:07:43.800> least<00:07:44.000> this<00:07:44.199> option 00:07:44.510 --> 00:07:44.520 align:start position:0% important to have at least this option 00:07:44.520 --> 00:07:48.110 align:start position:0% important to have at least this option of<00:07:44.720> being<00:07:45.080> able<00:07:45.319> to<00:07:45.560> update<00:07:46.440> um<00:07:47.120> contracts 00:07:48.110 --> 00:07:48.120 align:start position:0% of being able to update um contracts 00:07:48.120 --> 00:07:50.589 align:start position:0% of being able to update um contracts time<00:07:48.400> delays<00:07:48.840> are<00:07:49.000> also<00:07:49.280> something<00:07:49.599> important 00:07:50.589 --> 00:07:50.599 align:start position:0% time delays are also something important 00:07:50.599 --> 00:07:53.469 align:start position:0% time delays are also something important when<00:07:51.159> you<00:07:52.159> with<00:07:52.400> when<00:07:52.520> someone<00:07:52.800> can<00:07:52.960> restore 00:07:53.469 --> 00:07:53.479 align:start position:0% when you with when someone can restore 00:07:53.479 --> 00:07:55.550 align:start position:0% when you with when someone can restore ether<00:07:53.800> or<00:07:53.919> to<00:07:54.120> take<00:07:54.360> ether<00:07:54.720> out<00:07:54.960> of<00:07:55.120> a<00:07:55.240> smart 00:07:55.550 --> 00:07:55.560 align:start position:0% ether or to take ether out of a smart 00:07:55.560 --> 00:07:57.189 align:start position:0% ether or to take ether out of a smart contract<00:07:56.000> if<00:07:56.120> you<00:07:56.199> have<00:07:56.319> a<00:07:56.520> time<00:07:56.720> delay<00:07:57.039> this 00:07:57.189 --> 00:07:57.199 align:start position:0% contract if you have a time delay this 00:07:57.199 --> 00:07:59.510 align:start position:0% contract if you have a time delay this gives<00:07:57.440> an<00:07:57.639> option<00:07:58.319> if<00:07:58.440> you<00:07:58.759> implement<00:07:59.199> that 00:07:59.510 --> 00:07:59.520 align:start position:0% gives an option if you implement that 00:07:59.520 --> 00:08:02.550 align:start position:0% gives an option if you implement that some<00:07:59.800> authority<00:08:00.319> to<00:08:00.520> do<00:08:00.759> something<00:08:01.360> to<00:08:01.599> act<00:08:02.400> in 00:08:02.550 --> 00:08:02.560 align:start position:0% some authority to do something to act in 00:08:02.560 --> 00:08:04.029 align:start position:0% some authority to do something to act in case<00:08:02.680> of<00:08:02.800> The<00:08:03.000> Da<00:08:03.240> there<00:08:03.360> was<00:08:03.560> no<00:08:03.759> such 00:08:04.029 --> 00:08:04.039 align:start position:0% case of The Da there was no such 00:08:04.039 --> 00:08:06.790 align:start position:0% case of The Da there was no such Authority<00:08:04.520> and<00:08:04.680> the<00:08:04.879> least<00:08:05.199> resort<00:08:05.680> was<00:08:05.879> this 00:08:06.790 --> 00:08:06.800 align:start position:0% Authority and the least resort was this 00:08:06.800 --> 00:08:09.510 align:start position:0% Authority and the least resort was this this<00:08:06.919> awful<00:08:07.199> hot<00:08:07.520> work<00:08:08.280> so<00:08:08.960> therefore<00:08:09.280> if<00:08:09.360> you 00:08:09.510 --> 00:08:09.520 align:start position:0% this awful hot work so therefore if you 00:08:09.520 --> 00:08:11.749 align:start position:0% this awful hot work so therefore if you have<00:08:09.680> time<00:08:09.879> delays<00:08:10.520> and<00:08:10.759> this<00:08:11.280> Authority 00:08:11.749 --> 00:08:11.759 align:start position:0% have time delays and this Authority 00:08:11.759 --> 00:08:13.950 align:start position:0% have time delays and this Authority implemented<00:08:12.680> then<00:08:12.840> this<00:08:13.000> can<00:08:13.240> work<00:08:13.520> nicely 00:08:13.950 --> 00:08:13.960 align:start position:0% implemented then this can work nicely 00:08:13.960 --> 00:08:15.909 align:start position:0% implemented then this can work nicely together<00:08:14.280> to<00:08:14.520> reduce<00:08:14.879> the<00:08:15.039> risk<00:08:15.280> of<00:08:15.720> your 00:08:15.909 --> 00:08:15.919 align:start position:0% together to reduce the risk of your 00:08:15.919 --> 00:08:17.110 align:start position:0% together to reduce the risk of your smart 00:08:17.110 --> 00:08:17.120 align:start position:0% smart 00:08:17.120 --> 00:08:20.230 align:start position:0% smart contract<00:08:18.120> of<00:08:18.199> course<00:08:18.440> minimal<00:08:18.879> complexity<00:08:19.879> um 00:08:20.230 --> 00:08:20.240 align:start position:0% contract of course minimal complexity um 00:08:20.240 --> 00:08:21.710 align:start position:0% contract of course minimal complexity um there<00:08:20.360> are<00:08:20.639> statistics<00:08:21.199> out<00:08:21.400> there<00:08:21.560> which 00:08:21.710 --> 00:08:21.720 align:start position:0% there are statistics out there which 00:08:21.720 --> 00:08:24.149 align:start position:0% there are statistics out there which saying<00:08:22.280> there<00:08:22.400> are<00:08:22.560> 15<00:08:22.960> up<00:08:23.080> to<00:08:23.240> 50<00:08:23.680> bucks<00:08:23.960> per 00:08:24.149 --> 00:08:24.159 align:start position:0% saying there are 15 up to 50 bucks per 00:08:24.159 --> 00:08:26.790 align:start position:0% saying there are 15 up to 50 bucks per thousand<00:08:24.440> lines<00:08:24.680> of<00:08:24.800> code<00:08:25.479> for<00:08:25.639> a<00:08:25.800> website 00:08:26.790 --> 00:08:26.800 align:start position:0% thousand lines of code for a website 00:08:26.800 --> 00:08:28.950 align:start position:0% thousand lines of code for a website it's<00:08:27.120> okay<00:08:27.479> you<00:08:27.639> can<00:08:27.800> fix<00:08:28.000> it<00:08:28.319> but<00:08:28.440> for<00:08:28.560> a<00:08:28.639> smart 00:08:28.950 --> 00:08:28.960 align:start position:0% it's okay you can fix it but for a smart 00:08:28.960 --> 00:08:30.909 align:start position:0% it's okay you can fix it but for a smart contract<00:08:29.280> it's<00:08:29.639> really<00:08:29.879> bad<00:08:30.240> so<00:08:30.400> of<00:08:30.560> course<00:08:30.800> we 00:08:30.909 --> 00:08:30.919 align:start position:0% contract it's really bad so of course we 00:08:30.919 --> 00:08:33.670 align:start position:0% contract it's really bad so of course we need<00:08:31.159> a<00:08:32.159> much<00:08:32.399> much<00:08:32.599> more<00:08:32.800> security<00:08:33.159> for<00:08:33.399> smart 00:08:33.670 --> 00:08:33.680 align:start position:0% need a much much more security for smart 00:08:33.680 --> 00:08:36.670 align:start position:0% need a much much more security for smart contracts<00:08:34.080> than<00:08:34.240> we<00:08:34.560> need<00:08:34.760> for<00:08:34.959> normal<00:08:35.680> stuff 00:08:36.670 --> 00:08:36.680 align:start position:0% contracts than we need for normal stuff 00:08:36.680 --> 00:08:39.190 align:start position:0% contracts than we need for normal stuff so<00:08:36.919> this<00:08:37.120> also<00:08:37.399> means<00:08:37.760> not<00:08:38.200> everything<00:08:38.680> needs 00:08:39.190 --> 00:08:39.200 align:start position:0% so this also means not everything needs 00:08:39.200 --> 00:08:40.949 align:start position:0% so this also means not everything needs decentralization<00:08:40.200> and<00:08:40.360> needs<00:08:40.519> to<00:08:40.640> be<00:08:40.760> in<00:08:40.839> a 00:08:40.949 --> 00:08:40.959 align:start position:0% decentralization and needs to be in a 00:08:40.959 --> 00:08:42.909 align:start position:0% decentralization and needs to be in a smart<00:08:41.240> contract<00:08:41.839> only<00:08:42.159> put<00:08:42.320> in<00:08:42.560> what<00:08:42.680> you 00:08:42.909 --> 00:08:42.919 align:start position:0% smart contract only put in what you 00:08:42.919 --> 00:08:45.030 align:start position:0% smart contract only put in what you really<00:08:43.159> need<00:08:43.640> the<00:08:43.880> core<00:08:44.200> elements<00:08:44.760> of<00:08:44.920> a 00:08:45.030 --> 00:08:45.040 align:start position:0% really need the core elements of a 00:08:45.040 --> 00:08:46.550 align:start position:0% really need the core elements of a decentralized<00:08:45.680> application<00:08:46.240> everything 00:08:46.550 --> 00:08:46.560 align:start position:0% decentralized application everything 00:08:46.560 --> 00:08:48.910 align:start position:0% decentralized application everything else<00:08:46.839> can<00:08:47.000> be<00:08:47.440> maybe<00:08:47.680> in<00:08:47.839> swarm<00:08:48.320> whisper<00:08:48.760> or 00:08:48.910 --> 00:08:48.920 align:start position:0% else can be maybe in swarm whisper or 00:08:48.920 --> 00:08:52.269 align:start position:0% else can be maybe in swarm whisper or even<00:08:49.120> other 00:08:52.269 --> 00:08:52.279 align:start position:0% 00:08:52.279 --> 00:08:54.550 align:start position:0% techniques<00:08:53.279> yeah<00:08:53.839> and<00:08:53.959> the<00:08:54.080> other<00:08:54.279> thing<00:08:54.440> is 00:08:54.550 --> 00:08:54.560 align:start position:0% techniques yeah and the other thing is 00:08:54.560 --> 00:08:57.030 align:start position:0% techniques yeah and the other thing is to<00:08:54.760> reuse<00:08:55.240> trusted<00:08:55.720> proven<00:08:56.080> code<00:08:56.399> this<00:08:56.760> can 00:08:57.030 --> 00:08:57.040 align:start position:0% to reuse trusted proven code this can 00:08:57.040 --> 00:08:59.430 align:start position:0% to reuse trusted proven code this can also<00:08:57.240> be<00:08:57.399> dangerous<00:08:58.160> but<00:08:58.320> for<00:08:58.480> example<00:08:59.279> the 00:08:59.430 --> 00:08:59.440 align:start position:0% also be dangerous but for example the 00:08:59.440 --> 00:09:00.910 align:start position:0% also be dangerous but for example the the<00:08:59.560> standard<00:08:59.880> token<00:09:00.200> contract<00:09:00.640> which<00:09:00.760> was 00:09:00.910 --> 00:09:00.920 align:start position:0% the standard token contract which was 00:09:00.920 --> 00:09:02.430 align:start position:0% the standard token contract which was also<00:09:01.079> used<00:09:01.320> in<00:09:01.440> the<00:09:01.560> da<00:09:01.760> which<00:09:01.880> worked<00:09:02.160> just 00:09:02.430 --> 00:09:02.440 align:start position:0% also used in the da which worked just 00:09:02.440 --> 00:09:05.670 align:start position:0% also used in the da which worked just nice<00:09:03.440> um<00:09:03.680> you<00:09:03.880> have<00:09:04.200> the<00:09:04.360> foundation<00:09:04.800> mulc 00:09:05.670 --> 00:09:05.680 align:start position:0% nice um you have the foundation mulc 00:09:05.680 --> 00:09:08.150 align:start position:0% nice um you have the foundation mulc which<00:09:05.839> seems<00:09:06.079> to<00:09:06.200> hold<00:09:06.480> up<00:09:06.600> till<00:09:06.800> now<00:09:07.079> so<00:09:07.279> means 00:09:08.150 --> 00:09:08.160 align:start position:0% which seems to hold up till now so means 00:09:08.160 --> 00:09:10.310 align:start position:0% which seems to hold up till now so means also<00:09:08.440> looks<00:09:08.720> safe<00:09:09.480> and<00:09:09.640> maybe<00:09:09.880> there<00:09:10.000> will<00:09:10.160> be 00:09:10.310 --> 00:09:10.320 align:start position:0% also looks safe and maybe there will be 00:09:10.320 --> 00:09:12.470 align:start position:0% also looks safe and maybe there will be even<00:09:10.519> a<00:09:10.640> dow<00:09:10.880> standard<00:09:11.200> framework<00:09:11.680> one<00:09:11.880> day 00:09:12.470 --> 00:09:12.480 align:start position:0% even a dow standard framework one day 00:09:12.480 --> 00:09:14.790 align:start position:0% even a dow standard framework one day just<00:09:12.640> to<00:09:12.839> reusable<00:09:13.560> safe<00:09:13.920> code<00:09:14.320> this<00:09:14.560> also 00:09:14.790 --> 00:09:14.800 align:start position:0% just to reusable safe code this also 00:09:14.800 --> 00:09:17.069 align:start position:0% just to reusable safe code this also come<00:09:15.079> with<00:09:15.200> a<00:09:15.399> danger<00:09:16.079> because<00:09:16.399> if<00:09:16.600> then<00:09:16.760> you 00:09:17.069 --> 00:09:17.079 align:start position:0% come with a danger because if then you 00:09:17.079 --> 00:09:19.030 align:start position:0% come with a danger because if then you someone<00:09:17.440> finds<00:09:17.680> a<00:09:17.839> bug<00:09:18.120> in<00:09:18.360> this<00:09:18.519> kind<00:09:18.680> of<00:09:18.800> code 00:09:19.030 --> 00:09:19.040 align:start position:0% someone finds a bug in this kind of code 00:09:19.040 --> 00:09:21.150 align:start position:0% someone finds a bug in this kind of code it<00:09:19.160> will<00:09:19.360> affect<00:09:19.600> a<00:09:19.720> lot<00:09:19.839> of<00:09:20.040> applications<00:09:20.959> so 00:09:21.150 --> 00:09:21.160 align:start position:0% it will affect a lot of applications so 00:09:21.160 --> 00:09:22.470 align:start position:0% it will affect a lot of applications so therefore<00:09:21.480> you<00:09:21.600> also<00:09:21.800> need<00:09:21.920> to<00:09:22.040> be<00:09:22.160> careful 00:09:22.470 --> 00:09:22.480 align:start position:0% therefore you also need to be careful 00:09:22.480 --> 00:09:24.269 align:start position:0% therefore you also need to be careful with<00:09:22.680> those<00:09:22.880> things<00:09:23.480> but<00:09:23.640> I<00:09:23.720> think<00:09:23.920> we<00:09:24.040> as<00:09:24.120> a 00:09:24.269 --> 00:09:24.279 align:start position:0% with those things but I think we as a 00:09:24.279 --> 00:09:25.630 align:start position:0% with those things but I think we as a community<00:09:24.680> need<00:09:24.839> to<00:09:24.959> build<00:09:25.200> trusted 00:09:25.630 --> 00:09:25.640 align:start position:0% community need to build trusted 00:09:25.640 --> 00:09:27.310 align:start position:0% community need to build trusted libraries<00:09:26.120> which<00:09:26.200> are<00:09:26.360> reviewed<00:09:26.839> by<00:09:26.959> many<00:09:27.160> of 00:09:27.310 --> 00:09:27.320 align:start position:0% libraries which are reviewed by many of 00:09:27.320 --> 00:09:33.790 align:start position:0% libraries which are reviewed by many of us<00:09:27.839> to<00:09:28.240> for<00:09:28.480> other<00:09:28.640> developers<00:09:29.079> to<00:09:29.160> use 00:09:33.790 --> 00:09:33.800 align:start position:0% 00:09:33.800 --> 00:09:34.670 align:start position:0% let's 00:09:34.670 --> 00:09:34.680 align:start position:0% let's 00:09:34.680 --> 00:09:37.150 align:start position:0% let's see<00:09:35.680> if<00:09:35.800> we<00:09:35.920> can<00:09:36.040> get<00:09:36.160> to<00:09:36.360> next<00:09:36.519> side<00:09:36.920> better 00:09:37.150 --> 00:09:37.160 align:start position:0% see if we can get to next side better 00:09:37.160 --> 00:09:38.949 align:start position:0% see if we can get to next side better tools<00:09:37.800> you<00:09:37.920> have<00:09:38.040> heard<00:09:38.200> about<00:09:38.320> formal<00:09:38.600> proof 00:09:38.949 --> 00:09:38.959 align:start position:0% tools you have heard about formal proof 00:09:38.959 --> 00:09:41.069 align:start position:0% tools you have heard about formal proof appication<00:09:39.959> we<00:09:40.120> need<00:09:40.320> better<00:09:40.640> compiler 00:09:41.069 --> 00:09:41.079 align:start position:0% appication we need better compiler 00:09:41.079 --> 00:09:43.150 align:start position:0% appication we need better compiler warnings<00:09:41.839> um<00:09:41.959> I<00:09:42.040> think<00:09:42.200> this<00:09:42.320> is<00:09:42.440> all<00:09:42.640> work<00:09:42.880> in 00:09:43.150 --> 00:09:43.160 align:start position:0% warnings um I think this is all work in 00:09:43.160 --> 00:09:45.829 align:start position:0% warnings um I think this is all work in progress<00:09:44.160> we<00:09:44.279> need<00:09:44.480> improved<00:09:44.920> idees<00:09:45.560> we<00:09:45.680> have 00:09:45.829 --> 00:09:45.839 align:start position:0% progress we need improved idees we have 00:09:45.839 --> 00:09:48.069 align:start position:0% progress we need improved idees we have seen<00:09:46.120> remix<00:09:46.920> yesterday<00:09:47.399> which<00:09:47.560> looks<00:09:47.839> really 00:09:48.069 --> 00:09:48.079 align:start position:0% seen remix yesterday which looks really 00:09:48.079 --> 00:09:50.829 align:start position:0% seen remix yesterday which looks really nice<00:09:48.320> and<00:09:48.760> promising<00:09:49.760> um<00:09:50.160> we<00:09:50.279> need<00:09:50.440> trusted 00:09:50.829 --> 00:09:50.839 align:start position:0% nice and promising um we need trusted 00:09:50.839 --> 00:09:53.230 align:start position:0% nice and promising um we need trusted libraries<00:09:51.560> we<00:09:51.680> need<00:09:52.079> best<00:09:52.360> practices<00:09:52.839> liter 00:09:53.230 --> 00:09:53.240 align:start position:0% libraries we need best practices liter 00:09:53.240 --> 00:09:55.750 align:start position:0% libraries we need best practices liter which<00:09:53.360> is<00:09:53.519> also<00:09:53.760> work<00:09:53.959> in<00:09:54.360> progress<00:09:55.360> and<00:09:55.600> we 00:09:55.750 --> 00:09:55.760 align:start position:0% which is also work in progress and we 00:09:55.760 --> 00:09:58.430 align:start position:0% which is also work in progress and we also<00:09:56.000> may<00:09:56.160> need<00:09:56.399> some<00:09:57.040> yeah<00:09:57.440> centralization 00:09:58.430 --> 00:09:58.440 align:start position:0% also may need some yeah centralization 00:09:58.440 --> 00:10:00.790 align:start position:0% also may need some yeah centralization which<00:09:58.680> can<00:09:58.880> be<00:09:59.399> done<00:09:59.600> by<00:09:59.760> master<00:10:00.120> keys<00:10:00.440> so 00:10:00.790 --> 00:10:00.800 align:start position:0% which can be done by master keys so 00:10:00.800 --> 00:10:02.910 align:start position:0% which can be done by master keys so maybe<00:10:01.440> maybe<00:10:01.600> we<00:10:01.720> can<00:10:01.880> do<00:10:02.079> decentralized<00:10:02.760> with 00:10:02.910 --> 00:10:02.920 align:start position:0% maybe maybe we can do decentralized with 00:10:02.920 --> 00:10:05.110 align:start position:0% maybe maybe we can do decentralized with Escape<00:10:03.240> hatches<00:10:03.760> or<00:10:04.279> other<00:10:04.519> things<00:10:04.800> which<00:10:05.000> we 00:10:05.110 --> 00:10:05.120 align:start position:0% Escape hatches or other things which we 00:10:05.120 --> 00:10:08.430 align:start position:0% Escape hatches or other things which we can<00:10:05.360> use<00:10:05.760> in<00:10:05.920> smart<00:10:06.279> contracts<00:10:06.680> for<00:10:06.920> now<00:10:07.760> as<00:10:08.279> so 00:10:08.430 --> 00:10:08.440 align:start position:0% can use in smart contracts for now as so 00:10:08.440 --> 00:10:10.590 align:start position:0% can use in smart contracts for now as so to<00:10:08.600> say<00:10:08.880> a<00:10:09.000> trusted<00:10:09.360> source<00:10:09.640> of<00:10:09.800> information 00:10:10.590 --> 00:10:10.600 align:start position:0% to say a trusted source of information 00:10:10.600 --> 00:10:12.470 align:start position:0% to say a trusted source of information who<00:10:10.760> can<00:10:11.120> update<00:10:11.519> contracts<00:10:11.920> or<00:10:12.040> do<00:10:12.200> certain 00:10:12.470 --> 00:10:12.480 align:start position:0% who can update contracts or do certain 00:10:12.480 --> 00:10:14.710 align:start position:0% who can update contracts or do certain things<00:10:12.680> or<00:10:12.880> stop<00:10:13.120> a<00:10:13.279> contract<00:10:13.640> from 00:10:14.710 --> 00:10:14.720 align:start position:0% things or stop a contract from 00:10:14.720 --> 00:10:17.470 align:start position:0% things or stop a contract from working<00:10:15.720> so<00:10:15.920> as<00:10:16.000> a<00:10:16.200> conclusion<00:10:16.760> I<00:10:16.839> would<00:10:17.040> say 00:10:17.470 --> 00:10:17.480 align:start position:0% working so as a conclusion I would say 00:10:17.480 --> 00:10:20.069 align:start position:0% working so as a conclusion I would say it<00:10:17.680> is<00:10:18.279> very<00:10:18.560> early<00:10:18.959> days<00:10:19.360> and<00:10:19.480> we<00:10:19.640> all<00:10:19.800> need<00:10:19.959> to 00:10:20.069 --> 00:10:20.079 align:start position:0% it is very early days and we all need to 00:10:20.079 --> 00:10:23.990 align:start position:0% it is very early days and we all need to be<00:10:20.360> very<00:10:20.600> very<00:10:21.040> careful<00:10:22.040> um<00:10:22.399> but<00:10:22.640> I<00:10:23.000> think 00:10:23.990 --> 00:10:24.000 align:start position:0% be very very careful um but I think 00:10:24.000 --> 00:10:25.470 align:start position:0% be very very careful um but I think there<00:10:24.120> is<00:10:24.320> of<00:10:24.440> course<00:10:24.640> a<00:10:24.760> lot<00:10:24.920> of<00:10:25.079> lessons<00:10:25.399> to 00:10:25.470 --> 00:10:25.480 align:start position:0% there is of course a lot of lessons to 00:10:25.480 --> 00:10:27.870 align:start position:0% there is of course a lot of lessons to be<00:10:25.600> learned<00:10:25.920> from<00:10:26.160> this<00:10:26.680> but<00:10:27.240> being<00:10:27.560> here<00:10:27.720> the 00:10:27.870 --> 00:10:27.880 align:start position:0% be learned from this but being here the 00:10:27.880 --> 00:10:29.310 align:start position:0% be learned from this but being here the last<00:10:28.079> couple<00:10:28.279> of<00:10:28.399> days<00:10:28.640> got<00:10:28.800> me<00:10:28.920> really<00:10:29.079> EXC 00:10:29.310 --> 00:10:29.320 align:start position:0% last couple of days got me really EXC 00:10:29.320 --> 00:10:31.310 align:start position:0% last couple of days got me really EXC excited<00:10:29.680> to<00:10:29.800> see<00:10:30.279> what<00:10:30.440> came<00:10:30.600> out<00:10:30.760> of<00:10:30.959> this<00:10:31.200> we 00:10:31.310 --> 00:10:31.320 align:start position:0% excited to see what came out of this we 00:10:31.320 --> 00:10:32.990 align:start position:0% excited to see what came out of this we have<00:10:31.440> a<00:10:31.560> lot<00:10:31.720> of<00:10:31.880> Security<00:10:32.360> Experts<00:10:32.760> from 00:10:32.990 --> 00:10:33.000 align:start position:0% have a lot of Security Experts from 00:10:33.000 --> 00:10:34.310 align:start position:0% have a lot of Security Experts from academics<00:10:33.480> we<00:10:33.560> have<00:10:33.680> a<00:10:33.760> lot<00:10:33.880> of<00:10:34.000> media 00:10:34.310 --> 00:10:34.320 align:start position:0% academics we have a lot of media 00:10:34.320 --> 00:10:35.629 align:start position:0% academics we have a lot of media attention<00:10:34.680> a<00:10:34.760> lot<00:10:34.880> of<00:10:35.000> people<00:10:35.200> looking<00:10:35.440> at 00:10:35.629 --> 00:10:35.639 align:start position:0% attention a lot of people looking at 00:10:35.639 --> 00:10:37.069 align:start position:0% attention a lot of people looking at this<00:10:36.000> looking<00:10:36.240> at<00:10:36.360> the<00:10:36.560> right<00:10:36.760> things 00:10:37.069 --> 00:10:37.079 align:start position:0% this looking at the right things 00:10:37.079 --> 00:10:39.590 align:start position:0% this looking at the right things developers<00:10:37.600> being<00:10:37.959> much<00:10:38.160> more<00:10:38.440> careful<00:10:38.920> now 00:10:39.590 --> 00:10:39.600 align:start position:0% developers being much more careful now 00:10:39.600 --> 00:10:41.310 align:start position:0% developers being much more careful now and<00:10:40.120> it's<00:10:40.320> also<00:10:40.560> nice<00:10:40.760> to<00:10:40.880> see<00:10:41.040> a<00:10:41.120> lot<00:10:41.240> of 00:10:41.310 --> 00:10:41.320 align:start position:0% and it's also nice to see a lot of 00:10:41.320 --> 00:10:43.750 align:start position:0% and it's also nice to see a lot of developers<00:10:41.760> coming<00:10:42.000> up<00:10:42.120> to<00:10:42.240> me<00:10:42.440> and<00:10:42.639> say<00:10:43.480> um 00:10:43.750 --> 00:10:43.760 align:start position:0% developers coming up to me and say um 00:10:43.760 --> 00:10:45.790 align:start position:0% developers coming up to me and say um you<00:10:43.959> basically<00:10:44.279> saved<00:10:44.639> my<00:10:44.839> project<00:10:45.399> because<00:10:45.680> I 00:10:45.790 --> 00:10:45.800 align:start position:0% you basically saved my project because I 00:10:45.800 --> 00:10:47.110 align:start position:0% you basically saved my project because I had<00:10:45.959> the<00:10:46.040> same<00:10:46.240> bug<00:10:46.440> in<00:10:46.600> there<00:10:46.720> but<00:10:46.839> I<00:10:46.959> could 00:10:47.110 --> 00:10:47.120 align:start position:0% had the same bug in there but I could 00:10:47.120 --> 00:10:49.710 align:start position:0% had the same bug in there but I could fix<00:10:47.279> it<00:10:47.480> now<00:10:48.160> and<00:10:48.320> so<00:10:48.920> I<00:10:49.079> think<00:10:49.279> a<00:10:49.399> lot<00:10:49.560> of 00:10:49.710 --> 00:10:49.720 align:start position:0% fix it now and so I think a lot of 00:10:49.720 --> 00:10:52.590 align:start position:0% fix it now and so I think a lot of future<00:10:50.720> applications<00:10:51.480> desized<00:10:52.079> applications 00:10:52.590 --> 00:10:52.600 align:start position:0% future applications desized applications 00:10:52.600 --> 00:10:54.870 align:start position:0% future applications desized applications and<00:10:52.720> smart<00:10:53.040> contracts<00:10:53.760> will<00:10:54.040> avoid<00:10:54.519> all<00:10:54.680> of 00:10:54.870 --> 00:10:54.880 align:start position:0% and smart contracts will avoid all of 00:10:54.880 --> 00:10:57.829 align:start position:0% and smart contracts will avoid all of these<00:10:55.120> issues<00:10:56.120> and<00:10:56.760> we<00:10:56.920> can<00:10:57.200> really<00:10:57.440> move<00:10:57.680> into 00:10:57.829 --> 00:10:57.839 align:start position:0% these issues and we can really move into 00:10:57.839 --> 00:11:00.550 align:start position:0% these issues and we can really move into a<00:10:58.000> pride<00:10:58.320> future<00:10:59.399> although<00:10:59.760> being<00:11:00.079> careful<00:11:00.440> in 00:11:00.550 --> 00:11:00.560 align:start position:0% a pride future although being careful in 00:11:00.560 --> 00:11:02.670 align:start position:0% a pride future although being careful in the<00:11:00.680> beginning<00:11:01.079> and<00:11:01.200> it<00:11:01.440> was<00:11:02.440> really 00:11:02.670 --> 00:11:02.680 align:start position:0% the beginning and it was really 00:11:02.680 --> 00:11:04.150 align:start position:0% the beginning and it was really astonishing<00:11:03.160> for<00:11:03.320> me<00:11:03.440> to<00:11:03.560> see<00:11:03.839> how<00:11:04.000> this 00:11:04.150 --> 00:11:04.160 align:start position:0% astonishing for me to see how this 00:11:04.160 --> 00:11:05.910 align:start position:0% astonishing for me to see how this community<00:11:04.519> is<00:11:04.639> moving<00:11:04.920> on<00:11:05.279> I<00:11:05.399> think<00:11:05.639> this<00:11:05.800> was 00:11:05.910 --> 00:11:05.920 align:start position:0% community is moving on I think this was 00:11:05.920 --> 00:11:09.310 align:start position:0% community is moving on I think this was a<00:11:06.680> really<00:11:06.920> nice<00:11:07.680> um<00:11:07.880> experience<00:11:08.360> to<00:11:08.880> talk<00:11:09.120> to 00:11:09.310 --> 00:11:09.320 align:start position:0% a really nice um experience to talk to 00:11:09.320 --> 00:11:11.030 align:start position:0% a really nice um experience to talk to many<00:11:09.560> of<00:11:09.720> you<00:11:10.040> the<00:11:10.200> last<00:11:10.360> couple<00:11:10.600> of<00:11:10.720> days<00:11:10.920> and 00:11:11.030 --> 00:11:11.040 align:start position:0% many of you the last couple of days and 00:11:11.040 --> 00:11:13.710 align:start position:0% many of you the last couple of days and I<00:11:11.160> also<00:11:11.360> want<00:11:11.519> to<00:11:11.639> say<00:11:11.800> a<00:11:12.040> personal<00:11:12.839> thank<00:11:13.040> you 00:11:13.710 --> 00:11:13.720 align:start position:0% I also want to say a personal thank you 00:11:13.720 --> 00:11:17.150 align:start position:0% I also want to say a personal thank you I<00:11:13.800> mean<00:11:14.160> the<00:11:14.360> last<00:11:14.600> couple<00:11:14.839> of<00:11:15.000> month 00:11:17.150 --> 00:11:17.160 align:start position:0% I mean the last couple of month 00:11:17.160 --> 00:11:23.430 align:start position:0% I mean the last couple of month um<00:11:18.160> thank 00:11:23.430 --> 00:11:23.440 align:start position:0% 00:11:23.440 --> 00:11:26.280 align:start position:0% you<00:11:24.440> thank<00:11:24.600> you<00:11:24.760> very 00:11:26.280 --> 00:11:26.290 align:start position:0% you thank you very 00:11:26.290 --> 00:11:28.230 align:start position:0% you thank you very [Applause] 00:11:28.230 --> 00:11:28.240 align:start position:0% [Applause] 00:11:28.240 --> 00:11:35.629 align:start position:0% [Applause] much 00:11:35.629 --> 00:11:35.639 align:start position:0% 00:11:35.639 --> 00:11:38.230 align:start position:0% yeah<00:11:35.880> it<00:11:36.120> has<00:11:37.120> yeah<00:11:37.440> I<00:11:37.519> can<00:11:37.639> only<00:11:37.839> really<00:11:38.040> say 00:11:38.230 --> 00:11:38.240 align:start position:0% yeah it has yeah I can only really say 00:11:38.240 --> 00:11:39.629 align:start position:0% yeah it has yeah I can only really say thank<00:11:38.399> you<00:11:38.519> the<00:11:38.680> last<00:11:38.880> couple<00:11:39.079> of<00:11:39.200> months<00:11:39.480> have 00:11:39.629 --> 00:11:39.639 align:start position:0% thank you the last couple of months have 00:11:39.639 --> 00:11:41.829 align:start position:0% thank you the last couple of months have been<00:11:40.200> as<00:11:40.279> a<00:11:40.480> p<00:11:40.760> as<00:11:40.839> a<00:11:41.040> person<00:11:41.279> for<00:11:41.440> me<00:11:41.680> my 00:11:41.829 --> 00:11:41.839 align:start position:0% been as a p as a person for me my 00:11:41.839 --> 00:11:43.509 align:start position:0% been as a p as a person for me my personal<00:11:42.200> life<00:11:42.399> also<00:11:42.600> as<00:11:42.680> a<00:11:42.800> company<00:11:43.120> hobble 00:11:43.509 --> 00:11:43.519 align:start position:0% personal life also as a company hobble 00:11:43.519 --> 00:11:45.870 align:start position:0% personal life also as a company hobble of<00:11:43.639> course<00:11:44.480> but<00:11:44.760> it's<00:11:44.920> only<00:11:45.360> because<00:11:45.600> of<00:11:45.760> the 00:11:45.870 --> 00:11:45.880 align:start position:0% of course but it's only because of the 00:11:45.880 --> 00:11:47.310 align:start position:0% of course but it's only because of the people<00:11:46.120> sitting<00:11:46.480> here<00:11:46.760> because<00:11:46.959> of<00:11:47.079> the<00:11:47.200> lot 00:11:47.310 --> 00:11:47.320 align:start position:0% people sitting here because of the lot 00:11:47.320 --> 00:11:49.150 align:start position:0% people sitting here because of the lot of<00:11:47.480> Ean<00:11:47.959> community<00:11:48.320> that<00:11:48.480> I<00:11:48.560> can<00:11:48.720> stand<00:11:49.000> here 00:11:49.150 --> 00:11:49.160 align:start position:0% of Ean community that I can stand here 00:11:49.160 --> 00:11:51.550 align:start position:0% of Ean community that I can stand here today<00:11:49.639> and<00:11:49.920> give<00:11:50.160> this<00:11:50.360> talk<00:11:51.079> and<00:11:51.200> I<00:11:51.320> just<00:11:51.440> want 00:11:51.550 --> 00:11:51.560 align:start position:0% today and give this talk and I just want 00:11:51.560 --> 00:11:53.670 align:start position:0% today and give this talk and I just want to<00:11:51.680> say<00:11:51.880> thank<00:11:52.000> you<00:11:52.160> very<00:11:52.320> much 00:11:53.670 --> 00:11:53.680 align:start position:0% to say thank you very much 00:11:53.680 --> 00:11:58.230 align:start position:0% to say thank you very much yeah<00:11:54.680> thank<00:11:55.079> you<00:11:56.079> really<00:11:56.279> thank 00:11:58.230 --> 00:11:58.240 align:start position:0% yeah thank you really thank 00:11:58.240 --> 00:11:59.430 align:start position:0% yeah thank you really thank you 00:11:59.430 --> 00:11:59.440 align:start position:0% you 00:11:59.440 --> 00:12:03.969 align:start position:0% you [Music]