WEBVTT Kind: captions Language: en 00:00:09.190 --> 00:00:12.029 align:start position:0% [Music] 00:00:12.029 --> 00:00:12.039 align:start position:0% [Music] 00:00:12.039 --> 00:00:17.410 align:start position:0% [Music] hey<00:00:13.039> everyone<00:00:13.480> thank<00:00:14.480> you<00:00:15.070> so<00:00:16.070> for<00:00:17.030> those<00:00:17.150> of 00:00:17.410 --> 00:00:17.420 align:start position:0% hey everyone thank you so for those of 00:00:17.420 --> 00:00:19.420 align:start position:0% hey everyone thank you so for those of you<00:00:17.539> who<00:00:17.660> don't<00:00:17.750> know<00:00:17.900> us<00:00:18.020> at<00:00:18.440> sapling<00:00:19.040> we 00:00:19.420 --> 00:00:19.430 align:start position:0% you who don't know us at sapling we 00:00:19.430 --> 00:00:21.610 align:start position:0% you who don't know us at sapling we build<00:00:19.790> technology<00:00:19.910> and<00:00:20.630> provide<00:00:21.110> services<00:00:21.560> to 00:00:21.610 --> 00:00:21.620 align:start position:0% build technology and provide services to 00:00:21.620 --> 00:00:24.090 align:start position:0% build technology and provide services to help<00:00:22.010> protect<00:00:22.610> smart<00:00:23.240> contract<00:00:23.540> development 00:00:24.090 --> 00:00:24.100 align:start position:0% help protect smart contract development 00:00:24.100 --> 00:00:26.680 align:start position:0% help protect smart contract development we're<00:00:25.100> mostly<00:00:25.730> well<00:00:25.970> known<00:00:26.150> for<00:00:26.330> our<00:00:26.450> security 00:00:26.680 --> 00:00:26.690 align:start position:0% we're mostly well known for our security 00:00:26.690 --> 00:00:28.690 align:start position:0% we're mostly well known for our security audits<00:00:27.230> but<00:00:27.440> we<00:00:27.590> also<00:00:27.710> have<00:00:27.950> some<00:00:28.280> products 00:00:28.690 --> 00:00:28.700 align:start position:0% audits but we also have some products 00:00:28.700 --> 00:00:30.640 align:start position:0% audits but we also have some products and<00:00:28.910> we<00:00:29.060> maintain<00:00:29.570> the<00:00:29.690> open<00:00:29.900> sapling<00:00:30.230> repo<00:00:30.620> of 00:00:30.640 --> 00:00:30.650 align:start position:0% and we maintain the open sapling repo of 00:00:30.650 --> 00:00:33.220 align:start position:0% and we maintain the open sapling repo of smart<00:00:31.160> contracts<00:00:31.580> so<00:00:32.539> this<00:00:32.719> talk<00:00:32.899> will<00:00:33.079> be 00:00:33.220 --> 00:00:33.230 align:start position:0% smart contracts so this talk will be 00:00:33.230 --> 00:00:35.110 align:start position:0% smart contracts so this talk will be divided<00:00:33.800> it<00:00:33.950> first<00:00:34.220> I'm<00:00:34.460> going<00:00:34.700> to<00:00:34.820> review 00:00:35.110 --> 00:00:35.120 align:start position:0% divided it first I'm going to review 00:00:35.120 --> 00:00:38.980 align:start position:0% divided it first I'm going to review last<00:00:35.840> year<00:00:36.230> since<00:00:36.500> DEFCON<00:00:37.130> 2<00:00:37.340> in<00:00:37.760> terms<00:00:38.240> of<00:00:38.480> how 00:00:38.980 --> 00:00:38.990 align:start position:0% last year since DEFCON 2 in terms of how 00:00:38.990 --> 00:00:41.860 align:start position:0% last year since DEFCON 2 in terms of how the<00:00:39.050> smart<00:00:39.739> contract<00:00:39.950> ecosystem<00:00:40.820> evolved<00:00:41.150> I'm 00:00:41.860 --> 00:00:41.870 align:start position:0% the smart contract ecosystem evolved I'm 00:00:41.870 --> 00:00:43.780 align:start position:0% the smart contract ecosystem evolved I'm then<00:00:42.380> going<00:00:42.680> to<00:00:42.800> focus<00:00:43.310> on<00:00:43.430> some<00:00:43.640> new 00:00:43.780 --> 00:00:43.790 align:start position:0% then going to focus on some new 00:00:43.790 --> 00:00:45.280 align:start position:0% then going to focus on some new techniques<00:00:44.180> on<00:00:44.390> patterns<00:00:44.780> we've<00:00:45.020> seen 00:00:45.280 --> 00:00:45.290 align:start position:0% techniques on patterns we've seen 00:00:45.290 --> 00:00:48.010 align:start position:0% techniques on patterns we've seen arising<00:00:46.250> in<00:00:46.370> industry<00:00:46.790> that<00:00:47.239> I'd<00:00:47.570> like<00:00:47.750> to<00:00:47.870> get 00:00:48.010 --> 00:00:48.020 align:start position:0% arising in industry that I'd like to get 00:00:48.020 --> 00:00:50.229 align:start position:0% arising in industry that I'd like to get more<00:00:48.170> visibility<00:00:48.500> to<00:00:48.739> and<00:00:49.399> finally<00:00:49.940> I'm<00:00:50.060> going 00:00:50.229 --> 00:00:50.239 align:start position:0% more visibility to and finally I'm going 00:00:50.239 --> 00:00:51.700 align:start position:0% more visibility to and finally I'm going to<00:00:50.300> talk<00:00:50.450> about<00:00:50.510> some<00:00:50.870> pending<00:00:51.200> challenges 00:00:51.700 --> 00:00:51.710 align:start position:0% to talk about some pending challenges 00:00:51.710 --> 00:00:53.889 align:start position:0% to talk about some pending challenges it's<00:00:51.920> my<00:00:52.040> contract<00:00:52.399> security<00:00:52.790> and<00:00:53.030> hint<00:00:53.420> into 00:00:53.889 --> 00:00:53.899 align:start position:0% it's my contract security and hint into 00:00:53.899 --> 00:00:55.920 align:start position:0% it's my contract security and hint into some<00:00:54.079> possible<00:00:54.440> solutions<00:00:54.620> were<00:00:54.980> working<00:00:55.309> on 00:00:55.920 --> 00:00:55.930 align:start position:0% some possible solutions were working on 00:00:55.930 --> 00:00:58.479 align:start position:0% some possible solutions were working on so<00:00:56.930> let's<00:00:57.110> start<00:00:57.290> with<00:00:57.380> history<00:00:57.800> the<00:00:58.040> dark 00:00:58.479 --> 00:00:58.489 align:start position:0% so let's start with history the dark 00:00:58.489 --> 00:01:02.770 align:start position:0% so let's start with history the dark ages<00:00:59.050> so<00:01:00.050> 2016<00:01:00.800> was<00:01:01.309> a<00:01:01.340> pretty<00:01:01.910> dark<00:01:02.270> year<00:01:02.570> for 00:01:02.770 --> 00:01:02.780 align:start position:0% ages so 2016 was a pretty dark year for 00:01:02.780 --> 00:01:05.289 align:start position:0% ages so 2016 was a pretty dark year for smart<00:01:03.050> contract<00:01:03.380> security<00:01:03.820> we've<00:01:04.820> seen<00:01:05.059> some 00:01:05.289 --> 00:01:05.299 align:start position:0% smart contract security we've seen some 00:01:05.299 --> 00:01:07.120 align:start position:0% smart contract security we've seen some pretty<00:01:05.540> embarrassing<00:01:06.170> hacks<00:01:06.470> in<00:01:06.799> the<00:01:06.890> space 00:01:07.120 --> 00:01:07.130 align:start position:0% pretty embarrassing hacks in the space 00:01:07.130 --> 00:01:09.820 align:start position:0% pretty embarrassing hacks in the space most<00:01:08.030> of<00:01:08.150> you<00:01:08.270> probably<00:01:08.420> don't<00:01:08.780> remember<00:01:08.900> many 00:01:09.820 --> 00:01:09.830 align:start position:0% most of you probably don't remember many 00:01:09.830 --> 00:01:12.969 align:start position:0% most of you probably don't remember many of<00:01:09.979> these<00:01:10.390> except<00:01:11.390> for<00:01:11.570> the<00:01:11.690> Dow<00:01:11.840> but<00:01:12.530> just<00:01:12.890> to 00:01:12.969 --> 00:01:12.979 align:start position:0% of these except for the Dow but just to 00:01:12.979 --> 00:01:14.649 align:start position:0% of these except for the Dow but just to get<00:01:13.100> a<00:01:13.130> sense<00:01:13.340> of<00:01:13.490> how<00:01:13.610> the<00:01:13.670> industry<00:01:13.880> was<00:01:14.330> at 00:01:14.649 --> 00:01:14.659 align:start position:0% get a sense of how the industry was at 00:01:14.659 --> 00:01:16.420 align:start position:0% get a sense of how the industry was at that<00:01:14.840> moment<00:01:15.020> I<00:01:15.409> want<00:01:15.620> to<00:01:15.710> focus<00:01:15.860> on<00:01:16.130> one<00:01:16.400> of 00:01:16.420 --> 00:01:16.430 align:start position:0% that moment I want to focus on one of 00:01:16.430 --> 00:01:19.270 align:start position:0% that moment I want to focus on one of them<00:01:16.670> specifically<00:01:17.479> which<00:01:17.720> is<00:01:17.900> Rubik's<00:01:18.290> II<00:01:18.440> so 00:01:19.270 --> 00:01:19.280 align:start position:0% them specifically which is Rubik's II so 00:01:19.280 --> 00:01:22.510 align:start position:0% them specifically which is Rubik's II so Rick's<00:01:19.580> it<00:01:19.760> was<00:01:19.880> a<00:01:20.810> formalization<00:01:21.740> in<00:01:22.190> a<00:01:22.280> smart 00:01:22.510 --> 00:01:22.520 align:start position:0% Rick's it was a formalization in a smart 00:01:22.520 --> 00:01:24.640 align:start position:0% Rick's it was a formalization in a smart contract<00:01:22.700> of<00:01:23.150> a<00:01:23.210> pyramid<00:01:23.869> scheme<00:01:24.140> the 00:01:24.640 --> 00:01:24.650 align:start position:0% contract of a pyramid scheme the 00:01:24.650 --> 00:01:27.370 align:start position:0% contract of a pyramid scheme the original<00:01:25.010> name<00:01:25.220> was<00:01:25.250> dynamic<00:01:25.820> pyramid<00:01:26.570> but 00:01:27.370 --> 00:01:27.380 align:start position:0% original name was dynamic pyramid but 00:01:27.380 --> 00:01:29.289 align:start position:0% original name was dynamic pyramid but apparently<00:01:28.010> the<00:01:28.340> developer<00:01:28.760> didn't<00:01:29.119> think 00:01:29.289 --> 00:01:29.299 align:start position:0% apparently the developer didn't think 00:01:29.299 --> 00:01:31.810 align:start position:0% apparently the developer didn't think this<00:01:29.479> was<00:01:29.690> a<00:01:29.740> good<00:01:30.740> name<00:01:31.159> for<00:01:31.189> marketing 00:01:31.810 --> 00:01:31.820 align:start position:0% this was a good name for marketing 00:01:31.820 --> 00:01:34.149 align:start position:0% this was a good name for marketing reasons<00:01:31.880> so<00:01:32.750> he<00:01:32.900> renamed<00:01:33.229> it<00:01:33.350> to<00:01:33.409> Rubik's<00:01:34.010> II 00:01:34.149 --> 00:01:34.159 align:start position:0% reasons so he renamed it to Rubik's II 00:01:34.159 --> 00:01:36.550 align:start position:0% reasons so he renamed it to Rubik's II which<00:01:34.430> is<00:01:34.610> much<00:01:34.760> cooler<00:01:35.000> but<00:01:35.960> he<00:01:36.140> forgot<00:01:36.409> to 00:01:36.550 --> 00:01:36.560 align:start position:0% which is much cooler but he forgot to 00:01:36.560 --> 00:01:39.030 align:start position:0% which is much cooler but he forgot to rename<00:01:36.770> the<00:01:36.950> constructor<00:01:37.520> and<00:01:37.670> this<00:01:38.180> male 00:01:39.030 --> 00:01:39.040 align:start position:0% rename the constructor and this male 00:01:39.040 --> 00:01:42.039 align:start position:0% rename the constructor and this male this<00:01:40.040> made<00:01:40.250> it<00:01:40.460> turn<00:01:41.119> into<00:01:41.360> a<00:01:41.390> public<00:01:41.840> function 00:01:42.039 --> 00:01:42.049 align:start position:0% this made it turn into a public function 00:01:42.049 --> 00:01:44.289 align:start position:0% this made it turn into a public function because<00:01:42.560> that's<00:01:42.830> how<00:01:42.950> solidity<00:01:43.369> works<00:01:43.640> so 00:01:44.289 --> 00:01:44.299 align:start position:0% because that's how solidity works so 00:01:44.299 --> 00:01:47.560 align:start position:0% because that's how solidity works so anyone<00:01:44.960> could<00:01:45.170> call<00:01:45.439> the<00:01:46.340> dynamic<00:01:46.970> parents 00:01:47.560 --> 00:01:47.570 align:start position:0% anyone could call the dynamic parents 00:01:47.570 --> 00:01:50.140 align:start position:0% anyone could call the dynamic parents function<00:01:47.930> and<00:01:48.049> become<00:01:48.320> the<00:01:48.470> owner<00:01:49.150> that's 00:01:50.140 --> 00:01:50.150 align:start position:0% function and become the owner that's 00:01:50.150 --> 00:01:51.969 align:start position:0% function and become the owner that's gaining<00:01:50.420> gaining<00:01:51.020> the<00:01:51.320> ownership<00:01:51.650> of<00:01:51.890> the 00:01:51.969 --> 00:01:51.979 align:start position:0% gaining gaining the ownership of the 00:01:51.979 --> 00:01:53.410 align:start position:0% gaining gaining the ownership of the contract<00:01:52.400> and<00:01:52.520> being<00:01:52.820> able<00:01:52.939> to<00:01:53.090> steal<00:01:53.390> the 00:01:53.410 --> 00:01:53.420 align:start position:0% contract and being able to steal the 00:01:53.420 --> 00:01:55.840 align:start position:0% contract and being able to steal the fees<00:01:54.110> from<00:01:54.320> the<00:01:54.500> contract<00:01:54.890> so<00:01:55.490> this<00:01:55.670> seems 00:01:55.840 --> 00:01:55.850 align:start position:0% fees from the contract so this seems 00:01:55.850 --> 00:01:58.060 align:start position:0% fees from the contract so this seems like<00:01:55.939> a<00:01:56.150> dumb<00:01:56.360> mistake<00:01:56.540> but<00:01:57.439> the<00:01:57.560> same<00:01:57.770> feature 00:01:58.060 --> 00:01:58.070 align:start position:0% like a dumb mistake but the same feature 00:01:58.070 --> 00:02:01.210 align:start position:0% like a dumb mistake but the same feature from<00:01:59.000> solidity<00:01:59.390> probably<00:02:00.020> cost<00:02:00.259> the<00:02:00.619> party 00:02:01.210 --> 00:02:01.220 align:start position:0% from solidity probably cost the party 00:02:01.220 --> 00:02:03.460 align:start position:0% from solidity probably cost the party wallet<00:02:01.520> hack<00:02:01.759> which<00:02:02.329> happened<00:02:02.930> recently<00:02:03.079> and 00:02:03.460 --> 00:02:03.470 align:start position:0% wallet hack which happened recently and 00:02:03.470 --> 00:02:07.420 align:start position:0% wallet hack which happened recently and cost<00:02:04.189> like<00:02:05.470> 30<00:02:06.470> million<00:02:06.710> to<00:02:06.950> be<00:02:07.070> lost<00:02:07.250> to 00:02:07.420 --> 00:02:07.430 align:start position:0% cost like 30 million to be lost to 00:02:07.430 --> 00:02:14.140 align:start position:0% cost like 30 million to be lost to hackers<00:02:07.780> so<00:02:09.819> in<00:02:10.819> in<00:02:11.270> in<00:02:12.140> May<00:02:12.410> 2016<00:02:13.130> a<00:02:13.640> picture 00:02:14.140 --> 00:02:14.150 align:start position:0% hackers so in in in May 2016 a picture 00:02:14.150 --> 00:02:15.360 align:start position:0% hackers so in in in May 2016 a picture of<00:02:14.209> SNS<00:02:14.569> wrote<00:02:14.780> a<00:02:14.810> great 00:02:15.360 --> 00:02:15.370 align:start position:0% of SNS wrote a great 00:02:15.370 --> 00:02:17.309 align:start position:0% of SNS wrote a great girl<00:02:15.580> calling<00:02:16.269> the<00:02:16.450> community<00:02:16.840> to<00:02:17.019> gather 00:02:17.309 --> 00:02:17.319 align:start position:0% girl calling the community to gather 00:02:17.319 --> 00:02:20.160 align:start position:0% girl calling the community to gather around<00:02:17.560> a<00:02:17.980> building<00:02:18.670> best<00:02:19.540> practices<00:02:20.019> for 00:02:20.160 --> 00:02:20.170 align:start position:0% around a building best practices for 00:02:20.170 --> 00:02:22.530 align:start position:0% around a building best practices for smart<00:02:20.440> contract<00:02:20.769> development<00:02:21.220> and<00:02:21.430> one<00:02:22.330> month 00:02:22.530 --> 00:02:22.540 align:start position:0% smart contract development and one month 00:02:22.540 --> 00:02:25.080 align:start position:0% smart contract development and one month later<00:02:22.840> the<00:02:23.349> dalek<00:02:23.709> occurred<00:02:24.040> the<00:02:24.670> contract 00:02:25.080 --> 00:02:25.090 align:start position:0% later the dalek occurred the contract 00:02:25.090 --> 00:02:27.690 align:start position:0% later the dalek occurred the contract held<00:02:25.330> roughly<00:02:25.750> 15%<00:02:26.140> of<00:02:26.650> all<00:02:26.799> ether<00:02:27.159> tokens<00:02:27.580> in 00:02:27.690 --> 00:02:27.700 align:start position:0% held roughly 15% of all ether tokens in 00:02:27.700 --> 00:02:30.210 align:start position:0% held roughly 15% of all ether tokens in existence<00:02:28.180> and<00:02:28.500> fifty<00:02:29.500> million<00:02:29.680> dollars<00:02:30.010> were 00:02:30.210 --> 00:02:30.220 align:start position:0% existence and fifty million dollars were 00:02:30.220 --> 00:02:32.190 align:start position:0% existence and fifty million dollars were lost<00:02:30.250> and<00:02:30.730> at<00:02:30.940> that<00:02:31.090> time<00:02:31.330> the<00:02:31.569> only<00:02:31.780> solution 00:02:32.190 --> 00:02:32.200 align:start position:0% lost and at that time the only solution 00:02:32.200 --> 00:02:34.619 align:start position:0% lost and at that time the only solution at<00:02:32.530> the<00:02:32.680> moment<00:02:33.010> was<00:02:33.220> to<00:02:34.000> hard<00:02:34.180> fork<00:02:34.510> the 00:02:34.619 --> 00:02:34.629 align:start position:0% at the moment was to hard fork the 00:02:34.629 --> 00:02:36.539 align:start position:0% at the moment was to hard fork the protocol<00:02:35.079> so<00:02:35.379> a<00:02:35.409> theorem<00:02:35.769> had<00:02:36.010> to<00:02:36.129> hurt<00:02:36.280> fork 00:02:36.539 --> 00:02:36.549 align:start position:0% protocol so a theorem had to hurt fork 00:02:36.549 --> 00:02:38.339 align:start position:0% protocol so a theorem had to hurt fork which<00:02:37.150> in<00:02:37.390> turn<00:02:37.569> brought<00:02:37.870> a<00:02:38.140> lot<00:02:38.319> of 00:02:38.339 --> 00:02:38.349 align:start position:0% which in turn brought a lot of 00:02:38.349 --> 00:02:40.229 align:start position:0% which in turn brought a lot of complications<00:02:38.980> and<00:02:39.250> security<00:02:39.670> problems<00:02:40.060> so 00:02:40.229 --> 00:02:40.239 align:start position:0% complications and security problems so 00:02:40.239 --> 00:02:45.390 align:start position:0% complications and security problems so it<00:02:40.569> was<00:02:41.110> not<00:02:41.260> a<00:02:41.319> good<00:02:41.470> outcome<00:02:41.799> in<00:02:42.730> the<00:02:42.970> end<00:02:44.400> so 00:02:45.390 --> 00:02:45.400 align:start position:0% it was not a good outcome in the end so 00:02:45.400 --> 00:02:48.900 align:start position:0% it was not a good outcome in the end so at<00:02:46.390> that<00:02:46.540> moment<00:02:46.599> the<00:02:47.200> the<00:02:47.340> the<00:02:48.340> community<00:02:48.760> was 00:02:48.900 --> 00:02:48.910 align:start position:0% at that moment the the the community was 00:02:48.910 --> 00:02:50.699 align:start position:0% at that moment the the the community was pretty<00:02:49.150> aware<00:02:49.420> that<00:02:49.629> we<00:02:49.780> need<00:02:49.930> to<00:02:50.079> ramp<00:02:50.290> up<00:02:50.470> our 00:02:50.699 --> 00:02:50.709 align:start position:0% pretty aware that we need to ramp up our 00:02:50.709 --> 00:02:53.490 align:start position:0% pretty aware that we need to ramp up our security<00:02:51.160> practices<00:02:51.940> and<00:02:52.329> three<00:02:53.230> months 00:02:53.490 --> 00:02:53.500 align:start position:0% security practices and three months 00:02:53.500 --> 00:02:55.199 align:start position:0% security practices and three months later<00:02:53.680> on<00:02:53.829> September<00:02:54.069> we<00:02:54.519> launched<00:02:54.849> open 00:02:55.199 --> 00:02:55.209 align:start position:0% later on September we launched open 00:02:55.209 --> 00:02:57.750 align:start position:0% later on September we launched open sapling<00:02:55.540> as<00:02:55.810> a<00:02:56.049> community<00:02:56.859> effort<00:02:56.950> to<00:02:57.400> gather 00:02:57.750 --> 00:02:57.760 align:start position:0% sapling as a community effort to gather 00:02:57.760 --> 00:02:58.289 align:start position:0% sapling as a community effort to gather around 00:02:58.289 --> 00:02:58.299 align:start position:0% around 00:02:58.299 --> 00:03:00.599 align:start position:0% around auditing<00:02:59.140> contracts<00:02:59.590> creating<00:03:00.069> better 00:03:00.599 --> 00:03:00.609 align:start position:0% auditing contracts creating better 00:03:00.609 --> 00:03:03.240 align:start position:0% auditing contracts creating better security<00:03:01.060> practices<00:03:01.659> and<00:03:01.930> actually<00:03:02.890> gather 00:03:03.240 --> 00:03:03.250 align:start position:0% security practices and actually gather 00:03:03.250 --> 00:03:06.199 align:start position:0% security practices and actually gather some<00:03:03.579> smart<00:03:04.120> contracts<00:03:04.569> called<00:03:05.079> to<00:03:05.379> share<00:03:05.920> a 00:03:06.199 --> 00:03:06.209 align:start position:0% some smart contracts called to share a 00:03:06.209 --> 00:03:09.240 align:start position:0% some smart contracts called to share a week<00:03:07.209> later<00:03:07.450> I<00:03:07.750> was<00:03:07.870> in<00:03:08.260> Shanghai<00:03:08.440> for<00:03:08.680> DEFCON 00:03:09.240 --> 00:03:09.250 align:start position:0% week later I was in Shanghai for DEFCON 00:03:09.250 --> 00:03:11.399 align:start position:0% week later I was in Shanghai for DEFCON 2<00:03:09.430> and<00:03:09.790> everyone<00:03:10.269> loved<00:03:10.510> the<00:03:10.659> idea<00:03:10.780> many 00:03:11.399 --> 00:03:11.409 align:start position:0% 2 and everyone loved the idea many 00:03:11.409 --> 00:03:13.949 align:start position:0% 2 and everyone loved the idea many projects<00:03:11.980> wanted<00:03:12.370> to<00:03:12.519> gather<00:03:13.209> around<00:03:13.540> open 00:03:13.949 --> 00:03:13.959 align:start position:0% projects wanted to gather around open 00:03:13.959 --> 00:03:16.110 align:start position:0% projects wanted to gather around open sapling<00:03:14.290> and<00:03:14.409> help<00:03:14.680> these<00:03:15.310> contracts<00:03:15.790> and 00:03:16.110 --> 00:03:16.120 align:start position:0% sapling and help these contracts and 00:03:16.120 --> 00:03:18.149 align:start position:0% sapling and help these contracts and since<00:03:16.720> then<00:03:16.900> the<00:03:17.290> project<00:03:17.620> has<00:03:17.769> been<00:03:17.950> growing 00:03:18.149 --> 00:03:18.159 align:start position:0% since then the project has been growing 00:03:18.159 --> 00:03:21.390 align:start position:0% since then the project has been growing quite<00:03:18.730> a<00:03:18.790> lot<00:03:19.620> for<00:03:20.620> the<00:03:20.680> past<00:03:20.859> three<00:03:21.069> months<00:03:21.099> we 00:03:21.390 --> 00:03:21.400 align:start position:0% quite a lot for the past three months we 00:03:21.400 --> 00:03:25.199 align:start position:0% quite a lot for the past three months we had<00:03:21.639> more<00:03:22.090> than<00:03:22.239> 8%<00:03:22.480> a<00:03:23.260> weekly<00:03:23.919> growth<00:03:24.430> which 00:03:25.199 --> 00:03:25.209 align:start position:0% had more than 8% a weekly growth which 00:03:25.209 --> 00:03:29.039 align:start position:0% had more than 8% a weekly growth which is<00:03:25.389> the<00:03:25.989> hockey<00:03:26.169> stick<00:03:26.500> figure<00:03:26.889> every<00:03:28.049> Silicon 00:03:29.039 --> 00:03:29.049 align:start position:0% is the hockey stick figure every Silicon 00:03:29.049 --> 00:03:30.990 align:start position:0% is the hockey stick figure every Silicon Valley<00:03:29.230> entrepreneur<00:03:29.739> wants<00:03:29.919> but<00:03:30.639> the<00:03:30.760> truth 00:03:30.990 --> 00:03:31.000 align:start position:0% Valley entrepreneur wants but the truth 00:03:31.000 --> 00:03:33.920 align:start position:0% Valley entrepreneur wants but the truth is<00:03:31.120> we<00:03:31.450> built<00:03:31.989> something<00:03:32.260> that<00:03:32.620> everyone<00:03:33.489> was 00:03:33.920 --> 00:03:33.930 align:start position:0% is we built something that everyone was 00:03:33.930 --> 00:03:36.990 align:start position:0% is we built something that everyone was wanting<00:03:34.930> and<00:03:35.169> the<00:03:35.560> industry<00:03:36.010> grew<00:03:36.250> a<00:03:36.280> lot<00:03:36.519> say 00:03:36.990 --> 00:03:37.000 align:start position:0% wanting and the industry grew a lot say 00:03:37.000 --> 00:03:42.920 align:start position:0% wanting and the industry grew a lot say since<00:03:37.599> then<00:03:37.780> so<00:03:40.169> it<00:03:41.169> grew<00:03:41.379> with<00:03:41.530> the<00:03:41.560> industry 00:03:42.920 --> 00:03:42.930 align:start position:0% since then so it grew with the industry 00:03:42.930 --> 00:03:46.020 align:start position:0% since then so it grew with the industry apart<00:03:43.930> from<00:03:44.139> the<00:03:44.560> community<00:03:44.949> building<00:03:45.760> better 00:03:46.020 --> 00:03:46.030 align:start position:0% apart from the community building better 00:03:46.030 --> 00:03:48.479 align:start position:0% apart from the community building better tools<00:03:46.419> for<00:03:46.540> smart<00:03:46.959> contract<00:03:47.230> development<00:03:47.680> in 00:03:48.479 --> 00:03:48.489 align:start position:0% tools for smart contract development in 00:03:48.489 --> 00:03:50.599 align:start position:0% tools for smart contract development in Syria<00:03:48.819> massive<00:03:49.090> platform<00:03:49.269> evolved<00:03:49.840> a<00:03:49.959> lot<00:03:50.079> too 00:03:50.599 --> 00:03:50.609 align:start position:0% Syria massive platform evolved a lot too 00:03:50.609 --> 00:03:53.490 align:start position:0% Syria massive platform evolved a lot too we've<00:03:51.609> seen<00:03:51.819> the<00:03:51.910> consolidation<00:03:52.449> of<00:03:52.720> the 00:03:53.490 --> 00:03:53.500 align:start position:0% we've seen the consolidation of the 00:03:53.500 --> 00:03:56.479 align:start position:0% we've seen the consolidation of the various<00:03:54.099> standards<00:03:54.340> like<00:03:54.790> they<00:03:55.000> are<00:03:55.180> seat<00:03:55.389> 20 00:03:56.479 --> 00:03:56.489 align:start position:0% various standards like they are seat 20 00:03:56.489 --> 00:03:59.729 align:start position:0% various standards like they are seat 20 proposal<00:03:57.489> that<00:03:57.609> turned<00:03:57.910> into<00:03:58.120> a<00:03:58.449> IP<00:03:58.629> 20<00:03:59.139> for 00:03:59.729 --> 00:03:59.739 align:start position:0% proposal that turned into a IP 20 for 00:03:59.739 --> 00:04:03.449 align:start position:0% proposal that turned into a IP 20 for tokens<00:04:00.280> standard<00:04:01.410> also<00:04:02.410> the<00:04:02.650> platform<00:04:03.099> fixed 00:04:03.449 --> 00:04:03.459 align:start position:0% tokens standard also the platform fixed 00:04:03.459 --> 00:04:06.360 align:start position:0% tokens standard also the platform fixed some<00:04:03.879> security<00:04:04.870> problems<00:04:04.900> like<00:04:05.590> the<00:04:05.799> nasty 00:04:06.360 --> 00:04:06.370 align:start position:0% some security problems like the nasty 00:04:06.370 --> 00:04:08.009 align:start position:0% some security problems like the nasty call<00:04:06.760> stack<00:04:07.030> attack<00:04:07.299> that<00:04:07.510> was<00:04:07.660> possible 00:04:08.009 --> 00:04:08.019 align:start position:0% call stack attack that was possible 00:04:08.019 --> 00:04:10.770 align:start position:0% call stack attack that was possible before<00:04:08.169> and<00:04:08.799> after<00:04:09.129> AI<00:04:09.370> PE<00:04:09.639> 150<00:04:10.329> it's<00:04:10.599> no 00:04:10.770 --> 00:04:10.780 align:start position:0% before and after AI PE 150 it's no 00:04:10.780 --> 00:04:13.979 align:start position:0% before and after AI PE 150 it's no longer<00:04:10.930> possible<00:04:11.849> also<00:04:12.849> solidity<00:04:13.389> the<00:04:13.720> the 00:04:13.979 --> 00:04:13.989 align:start position:0% longer possible also solidity the the 00:04:13.989 --> 00:04:16.229 align:start position:0% longer possible also solidity the the most<00:04:14.139> popular<00:04:14.290> smart<00:04:15.160> contract<00:04:15.459> language<00:04:15.609> got 00:04:16.229 --> 00:04:16.239 align:start position:0% most popular smart contract language got 00:04:16.239 --> 00:04:17.849 align:start position:0% most popular smart contract language got some<00:04:16.660> cool<00:04:16.870> new<00:04:16.989> features<00:04:17.019> in<00:04:17.500> terms<00:04:17.530> of 00:04:17.849 --> 00:04:17.859 align:start position:0% some cool new features in terms of 00:04:17.859 --> 00:04:18.330 align:start position:0% some cool new features in terms of security 00:04:18.330 --> 00:04:18.340 align:start position:0% security 00:04:18.340 --> 00:04:20.909 align:start position:0% security the<00:04:19.000> payable<00:04:19.419> keyword<00:04:19.780> that<00:04:19.810> allows<00:04:20.289> to<00:04:20.680> set 00:04:20.909 --> 00:04:20.919 align:start position:0% the payable keyword that allows to set 00:04:20.919 --> 00:04:23.459 align:start position:0% the payable keyword that allows to set when<00:04:21.849> a<00:04:22.090> contract<00:04:22.539> can<00:04:22.690> or<00:04:22.870> cannot<00:04:23.139> receive 00:04:23.459 --> 00:04:23.469 align:start position:0% when a contract can or cannot receive 00:04:23.469 --> 00:04:25.860 align:start position:0% when a contract can or cannot receive money<00:04:23.710> require<00:04:24.669> an<00:04:24.849> assert<00:04:25.150> that<00:04:25.390> are<00:04:25.510> really 00:04:25.860 --> 00:04:25.870 align:start position:0% money require an assert that are really 00:04:25.870 --> 00:04:28.409 align:start position:0% money require an assert that are really useful<00:04:25.990> for<00:04:26.469> setting<00:04:27.400> the<00:04:27.640> preconditions<00:04:28.270> and 00:04:28.409 --> 00:04:28.419 align:start position:0% useful for setting the preconditions and 00:04:28.419 --> 00:04:28.930 align:start position:0% useful for setting the preconditions and postconditions 00:04:28.930 --> 00:04:28.940 align:start position:0% postconditions 00:04:28.940 --> 00:04:31.960 align:start position:0% postconditions of<00:04:29.330> our<00:04:29.600> functions<00:04:30.520> transfer<00:04:31.520> which<00:04:31.760> is<00:04:31.940> a 00:04:31.960 --> 00:04:31.970 align:start position:0% of our functions transfer which is a 00:04:31.970 --> 00:04:34.330 align:start position:0% of our functions transfer which is a safer<00:04:32.570> way<00:04:32.600> to<00:04:32.780> send<00:04:33.200> money<00:04:33.350> from<00:04:34.160> our 00:04:34.330 --> 00:04:34.340 align:start position:0% safer way to send money from our 00:04:34.340 --> 00:04:38.110 align:start position:0% safer way to send money from our contract<00:04:35.050> revert<00:04:36.050> to<00:04:36.500> cancel<00:04:37.370> execution<00:04:37.850> of 00:04:38.110 --> 00:04:38.120 align:start position:0% contract revert to cancel execution of 00:04:38.120 --> 00:04:40.650 align:start position:0% contract revert to cancel execution of our<00:04:38.480> function<00:04:39.110> without<00:04:39.650> wasting<00:04:40.070> all<00:04:40.220> the<00:04:40.310> gas 00:04:40.650 --> 00:04:40.660 align:start position:0% our function without wasting all the gas 00:04:40.660 --> 00:04:43.060 align:start position:0% our function without wasting all the gas Purim<00:04:41.660> view<00:04:41.900> which<00:04:42.050> are<00:04:42.290> the<00:04:42.560> evolution<00:04:42.980> of 00:04:43.060 --> 00:04:43.070 align:start position:0% Purim view which are the evolution of 00:04:43.070 --> 00:04:44.770 align:start position:0% Purim view which are the evolution of the<00:04:43.190> constant<00:04:43.670> keyword<00:04:44.030> and<00:04:44.270> allowed<00:04:44.600> to 00:04:44.770 --> 00:04:44.780 align:start position:0% the constant keyword and allowed to 00:04:44.780 --> 00:04:48.010 align:start position:0% the constant keyword and allowed to specify<00:04:45.550> if<00:04:46.550> a<00:04:46.730> contract<00:04:47.090> if<00:04:47.330> a<00:04:47.510> function<00:04:47.840> can 00:04:48.010 --> 00:04:48.020 align:start position:0% specify if a contract if a function can 00:04:48.020 --> 00:04:51.040 align:start position:0% specify if a contract if a function can or<00:04:48.380> cannot<00:04:48.800> read<00:04:49.250> or<00:04:49.520> write<00:04:49.820> state<00:04:50.240> from<00:04:50.840> the 00:04:51.040 --> 00:04:51.050 align:start position:0% or cannot read or write state from the 00:04:51.050 --> 00:04:54.540 align:start position:0% or cannot read or write state from the contract<00:04:52.240> we've<00:04:53.240> also<00:04:53.420> seen<00:04:53.690> the<00:04:53.750> death<00:04:54.050> of 00:04:54.540 --> 00:04:54.550 align:start position:0% contract we've also seen the death of 00:04:54.550 --> 00:04:57.640 align:start position:0% contract we've also seen the death of serpent<00:04:55.550> as<00:04:55.760> a<00:04:55.820> language<00:04:56.090> after<00:04:57.050> a<00:04:57.260> knowledge 00:04:57.640 --> 00:04:57.650 align:start position:0% serpent as a language after a knowledge 00:04:57.650 --> 00:05:00.100 align:start position:0% serpent as a language after a knowledge within<00:04:57.860> which<00:04:58.820> in<00:04:59.090> which<00:04:59.300> we<00:04:59.420> found<00:04:59.690> eight 00:05:00.100 --> 00:05:00.110 align:start position:0% within which in which we found eight 00:05:00.110 --> 00:05:03.820 align:start position:0% within which in which we found eight pretty<00:05:00.920> serious<00:05:01.910> vulnerabilities<00:05:02.810> which<00:05:03.560> led 00:05:03.820 --> 00:05:03.830 align:start position:0% pretty serious vulnerabilities which led 00:05:03.830 --> 00:05:06.490 align:start position:0% pretty serious vulnerabilities which led us<00:05:03.980> to<00:05:04.010> find<00:05:04.370> critical<00:05:05.270> vulnerability<00:05:06.140> in<00:05:06.380> the 00:05:06.490 --> 00:05:06.500 align:start position:0% us to find critical vulnerability in the 00:05:06.500 --> 00:05:08.770 align:start position:0% us to find critical vulnerability in the rep<00:05:06.650> token<00:05:07.070> which<00:05:07.580> allowed<00:05:07.880> any<00:05:08.180> attacker<00:05:08.600> to 00:05:08.770 --> 00:05:08.780 align:start position:0% rep token which allowed any attacker to 00:05:08.780 --> 00:05:11.890 align:start position:0% rep token which allowed any attacker to freeze<00:05:09.020> the<00:05:09.170> contract<00:05:09.620> forever<00:05:10.210> and<00:05:11.210> male 00:05:11.890 --> 00:05:11.900 align:start position:0% freeze the contract forever and male 00:05:11.900 --> 00:05:14.680 align:start position:0% freeze the contract forever and male made<00:05:12.530> them<00:05:12.710> have<00:05:13.490> to<00:05:13.670> me<00:05:13.790> migrate<00:05:14.330> the<00:05:14.540> rep 00:05:14.680 --> 00:05:14.690 align:start position:0% made them have to me migrate the rep 00:05:14.690 --> 00:05:18.520 align:start position:0% made them have to me migrate the rep token<00:05:15.050> to<00:05:15.200> solidity<00:05:16.060> the<00:05:17.260> serpent<00:05:18.260> language 00:05:18.520 --> 00:05:18.530 align:start position:0% token to solidity the serpent language 00:05:18.530 --> 00:05:21.130 align:start position:0% token to solidity the serpent language was<00:05:18.800> deprecated<00:05:19.550> after<00:05:20.480> this<00:05:20.660> tweet<00:05:20.960> from 00:05:21.130 --> 00:05:21.140 align:start position:0% was deprecated after this tweet from 00:05:21.140 --> 00:05:23.500 align:start position:0% was deprecated after this tweet from metallic<00:05:21.610> and<00:05:22.610> now<00:05:22.730> although<00:05:22.970> all<00:05:23.330> the 00:05:23.500 --> 00:05:23.510 align:start position:0% metallic and now although all the 00:05:23.510 --> 00:05:25.090 align:start position:0% metallic and now although all the efforts<00:05:23.780> around<00:05:23.960> and<00:05:24.350> an<00:05:24.500> alternative 00:05:25.090 --> 00:05:25.100 align:start position:0% efforts around and an alternative 00:05:25.100 --> 00:05:27.400 align:start position:0% efforts around and an alternative language<00:05:25.490> are<00:05:25.700> focused<00:05:26.180> on<00:05:26.330> Viper<00:05:26.600> which<00:05:26.960> is<00:05:27.140> a 00:05:27.400 --> 00:05:27.410 align:start position:0% language are focused on Viper which is a 00:05:27.410 --> 00:05:29.770 align:start position:0% language are focused on Viper which is a serpent<00:05:28.100> successor<00:05:28.610> and<00:05:29.090> it's<00:05:29.420> pretty<00:05:29.600> cool 00:05:29.770 --> 00:05:29.780 align:start position:0% serpent successor and it's pretty cool 00:05:29.780 --> 00:05:31.120 align:start position:0% serpent successor and it's pretty cool so<00:05:30.020> you<00:05:30.230> should<00:05:30.260> check<00:05:30.560> it<00:05:30.650> out<00:05:30.740> it's<00:05:31.040> not 00:05:31.120 --> 00:05:31.130 align:start position:0% so you should check it out it's not 00:05:31.130 --> 00:05:34.300 align:start position:0% so you should check it out it's not production<00:05:31.610> ready<00:05:31.910> yet<00:05:32.090> but<00:05:32.300> I<00:05:33.200> hope<00:05:33.710> it<00:05:34.130> gets 00:05:34.300 --> 00:05:34.310 align:start position:0% production ready yet but I hope it gets 00:05:34.310 --> 00:05:37.840 align:start position:0% production ready yet but I hope it gets more<00:05:34.550> attention<00:05:35.590> and<00:05:36.590> more<00:05:36.650> recently<00:05:37.190> with 00:05:37.840 --> 00:05:37.850 align:start position:0% more attention and more recently with 00:05:37.850 --> 00:05:39.900 align:start position:0% more attention and more recently with the<00:05:38.090> Byzantine<00:05:38.419> heart<00:05:38.870> fork<00:05:39.200> some 00:05:39.900 --> 00:05:39.910 align:start position:0% the Byzantine heart fork some 00:05:39.910 --> 00:05:42.190 align:start position:0% the Byzantine heart fork some consequences<00:05:40.910> on<00:05:41.090> on<00:05:41.330> security<00:05:41.840> are<00:05:41.990> the 00:05:42.190 --> 00:05:42.200 align:start position:0% consequences on on security are the 00:05:42.200 --> 00:05:44.320 align:start position:0% consequences on on security are the region<00:05:42.919> of<00:05:43.040> begin<00:05:43.490> sugar<00:05:43.760> modular 00:05:44.320 --> 00:05:44.330 align:start position:0% region of begin sugar modular 00:05:44.330 --> 00:05:46.300 align:start position:0% region of begin sugar modular exponentiation<00:05:44.720> which<00:05:45.169> allows<00:05:45.440> RSA 00:05:46.300 --> 00:05:46.310 align:start position:0% exponentiation which allows RSA 00:05:46.310 --> 00:05:48.490 align:start position:0% exponentiation which allows RSA signature<00:05:46.820> verifications<00:05:47.480> we'll<00:05:47.780> see<00:05:47.990> what 00:05:48.490 --> 00:05:48.500 align:start position:0% signature verifications we'll see what 00:05:48.500 --> 00:05:51.370 align:start position:0% signature verifications we'll see what people<00:05:48.800> come<00:05:48.830> up<00:05:49.040> to<00:05:49.490> with<00:05:49.700> this<00:05:49.850> new<00:05:50.390> tool<00:05:50.570> the 00:05:51.370 --> 00:05:51.380 align:start position:0% people come up to with this new tool the 00:05:51.380 --> 00:05:53.320 align:start position:0% people come up to with this new tool the asian<00:05:51.620> of<00:05:51.710> the<00:05:51.830> static<00:05:52.220> called<00:05:52.640> opcode<00:05:53.150> which 00:05:53.320 --> 00:05:53.330 align:start position:0% asian of the static called opcode which 00:05:53.330 --> 00:05:55.810 align:start position:0% asian of the static called opcode which enables<00:05:53.780> safer<00:05:54.290> calls<00:05:54.560> to<00:05:55.310> untrusted 00:05:55.810 --> 00:05:55.820 align:start position:0% enables safer calls to untrusted 00:05:55.820 --> 00:05:58.120 align:start position:0% enables safer calls to untrusted contracts<00:05:56.330> because<00:05:56.600> it<00:05:56.750> makes<00:05:57.140> them<00:05:57.320> not<00:05:57.830> able 00:05:58.120 --> 00:05:58.130 align:start position:0% contracts because it makes them not able 00:05:58.130 --> 00:06:01.930 align:start position:0% contracts because it makes them not able to<00:05:58.280> modify<00:05:58.730> your<00:05:58.820> storage<00:05:59.290> and<00:06:00.490> the<00:06:01.490> asian<00:06:01.760> of 00:06:01.930 --> 00:06:01.940 align:start position:0% to modify your storage and the asian of 00:06:01.940 --> 00:06:04.900 align:start position:0% to modify your storage and the asian of up<00:06:02.240> codes<00:06:02.630> for<00:06:02.780> data<00:06:03.230> handling<00:06:03.500> and<00:06:03.980> revert 00:06:04.900 --> 00:06:04.910 align:start position:0% up codes for data handling and revert 00:06:04.910 --> 00:06:08.290 align:start position:0% up codes for data handling and revert the<00:06:05.510> river<00:06:05.750> top<00:06:06.020> code<00:06:06.230> allow<00:06:06.980> for<00:06:07.250> much<00:06:07.760> easier 00:06:08.290 --> 00:06:08.300 align:start position:0% the river top code allow for much easier 00:06:08.300 --> 00:06:10.630 align:start position:0% the river top code allow for much easier and<00:06:08.419> Tyler<00:06:08.660> ways<00:06:08.990> of<00:06:09.260> implementing<00:06:09.950> upgrade 00:06:10.630 --> 00:06:10.640 align:start position:0% and Tyler ways of implementing upgrade 00:06:10.640 --> 00:06:13.150 align:start position:0% and Tyler ways of implementing upgrade ability<00:06:10.790> proxies<00:06:11.419> which<00:06:11.690> is<00:06:11.950> an<00:06:12.950> ongoing 00:06:13.150 --> 00:06:13.160 align:start position:0% ability proxies which is an ongoing 00:06:13.160 --> 00:06:15.430 align:start position:0% ability proxies which is an ongoing discussion<00:06:13.790> topic<00:06:14.419> in<00:06:14.570> smart<00:06:15.169> contracts 00:06:15.430 --> 00:06:15.440 align:start position:0% discussion topic in smart contracts 00:06:15.440 --> 00:06:19.900 align:start position:0% discussion topic in smart contracts security<00:06:16.300> so<00:06:17.300> that's<00:06:18.200> what<00:06:18.950> happened<00:06:19.340> and<00:06:19.550> now 00:06:19.900 --> 00:06:19.910 align:start position:0% security so that's what happened and now 00:06:19.910 --> 00:06:21.610 align:start position:0% security so that's what happened and now I<00:06:19.940> want<00:06:20.180> to<00:06:20.210> focus<00:06:20.390> on<00:06:20.630> some<00:06:20.840> new<00:06:21.230> techniques 00:06:21.610 --> 00:06:21.620 align:start position:0% I want to focus on some new techniques 00:06:21.620 --> 00:06:23.440 align:start position:0% I want to focus on some new techniques and<00:06:21.830> patterns<00:06:22.190> we've<00:06:22.370> been<00:06:22.640> seeing<00:06:22.880> on<00:06:23.330> our 00:06:23.440 --> 00:06:23.450 align:start position:0% and patterns we've been seeing on our 00:06:23.450 --> 00:06:26.400 align:start position:0% and patterns we've been seeing on our audits<00:06:23.840> and<00:06:24.050> work<00:06:24.590> with<00:06:24.830> opens<00:06:25.100> happening<00:06:25.400> oh 00:06:26.400 --> 00:06:26.410 align:start position:0% audits and work with opens happening oh 00:06:26.410 --> 00:06:30.310 align:start position:0% audits and work with opens happening oh can<00:06:27.410> you<00:06:27.500> see<00:06:27.530> that<00:06:27.830> ok<00:06:28.310> let's<00:06:28.940> say<00:06:29.090> you're<00:06:29.540> a 00:06:30.310 --> 00:06:30.320 align:start position:0% can you see that ok let's say you're a 00:06:30.320 --> 00:06:32.470 align:start position:0% can you see that ok let's say you're a developer<00:06:30.710> running<00:06:31.220> solidity<00:06:31.640> so<00:06:31.910> you<00:06:31.970> create 00:06:32.470 --> 00:06:32.480 align:start position:0% developer running solidity so you create 00:06:32.480 --> 00:06:34.510 align:start position:0% developer running solidity so you create your<00:06:32.960> own<00:06:32.990> you<00:06:33.530> RC<00:06:33.770> twenties<00:06:34.100> all<00:06:34.190> come<00:06:34.340> for 00:06:34.510 --> 00:06:34.520 align:start position:0% your own you RC twenties all come for 00:06:34.520 --> 00:06:37.779 align:start position:0% your own you RC twenties all come for fun<00:06:35.590> by<00:06:36.590> using<00:06:36.740> open<00:06:36.950> selling<00:06:37.400> you<00:06:37.520> can<00:06:37.669> do 00:06:37.779 --> 00:06:37.789 align:start position:0% fun by using open selling you can do 00:06:37.789 --> 00:06:39.520 align:start position:0% fun by using open selling you can do this<00:06:37.940> pretty<00:06:38.360> easily<00:06:38.690> with<00:06:38.900> like<00:06:39.080> ten<00:06:39.320> lines 00:06:39.520 --> 00:06:39.530 align:start position:0% this pretty easily with like ten lines 00:06:39.530 --> 00:06:41.560 align:start position:0% this pretty easily with like ten lines of<00:06:39.680> code<00:06:39.740> so<00:06:40.160> you<00:06:40.640> think<00:06:40.940> you<00:06:41.180> want<00:06:41.360> to<00:06:41.419> add 00:06:41.560 --> 00:06:41.570 align:start position:0% of code so you think you want to add 00:06:41.570 --> 00:06:42.730 align:start position:0% of code so you think you want to add something<00:06:41.840> that<00:06:42.020> sort<00:06:42.380> to<00:06:42.440> make 00:06:42.730 --> 00:06:42.740 align:start position:0% something that sort to make 00:06:42.740 --> 00:06:45.520 align:start position:0% something that sort to make talking<00:06:43.099> cooler<00:06:43.810> just<00:06:44.810> for<00:06:44.990> fine<00:06:45.169> you<00:06:45.289> think 00:06:45.520 --> 00:06:45.530 align:start position:0% talking cooler just for fine you think 00:06:45.530 --> 00:06:47.439 align:start position:0% talking cooler just for fine you think you<00:06:45.740> want<00:06:45.949> your<00:06:46.280> token<00:06:46.819> to<00:06:46.940> have<00:06:47.090> an<00:06:47.180> extra 00:06:47.439 --> 00:06:47.449 align:start position:0% you want your token to have an extra 00:06:47.449 --> 00:06:49.059 align:start position:0% you want your token to have an extra functionality<00:06:48.050> of<00:06:48.199> being<00:06:48.500> able<00:06:48.620> to<00:06:48.889> lock 00:06:49.059 --> 00:06:49.069 align:start position:0% functionality of being able to lock 00:06:49.069 --> 00:06:50.890 align:start position:0% functionality of being able to lock funds<00:06:49.340> for<00:06:49.639> a<00:06:49.699> certain<00:06:50.060> amount<00:06:50.180> of<00:06:50.419> time<00:06:50.630> and 00:06:50.890 --> 00:06:50.900 align:start position:0% funds for a certain amount of time and 00:06:50.900 --> 00:06:53.050 align:start position:0% funds for a certain amount of time and you<00:06:51.259> want<00:06:51.380> to<00:06:51.590> add<00:06:51.680> a<00:06:51.710> little<00:06:52.280> extra<00:06:52.610> gold<00:06:52.970> as 00:06:53.050 --> 00:06:53.060 align:start position:0% you want to add a little extra gold as 00:06:53.060 --> 00:06:56.890 align:start position:0% you want to add a little extra gold as possible<00:06:53.800> so<00:06:54.800> a<00:06:55.039> way<00:06:55.220> to<00:06:55.280> do<00:06:55.460> this<00:06:55.610> is<00:06:56.300> to<00:06:56.750> add<00:06:56.870> a 00:06:56.890 --> 00:06:56.900 align:start position:0% possible so a way to do this is to add a 00:06:56.900 --> 00:06:58.629 align:start position:0% possible so a way to do this is to add a lock<00:06:57.169> function<00:06:57.470> a<00:06:57.860> public<00:06:58.310> lock<00:06:58.490> function 00:06:58.629 --> 00:06:58.639 align:start position:0% lock function a public lock function 00:06:58.639 --> 00:07:01.480 align:start position:0% lock function a public lock function that<00:06:59.380> instantly<00:07:00.380> transfer<00:07:00.800> the<00:07:00.919> tokens<00:07:01.280> but 00:07:01.480 --> 00:07:01.490 align:start position:0% that instantly transfer the tokens but 00:07:01.490 --> 00:07:03.969 align:start position:0% that instantly transfer the tokens but then<00:07:01.699> stores<00:07:02.539> when<00:07:02.990> those<00:07:03.199> tokens<00:07:03.560> should<00:07:03.770> be 00:07:03.969 --> 00:07:03.979 align:start position:0% then stores when those tokens should be 00:07:03.979 --> 00:07:06.610 align:start position:0% then stores when those tokens should be released<00:07:04.550> and<00:07:04.880> then<00:07:05.330> modifying<00:07:05.780> the<00:07:06.110> standard 00:07:06.610 --> 00:07:06.620 align:start position:0% released and then modifying the standard 00:07:06.620 --> 00:07:08.800 align:start position:0% released and then modifying the standard transfer<00:07:07.009> functions<00:07:07.490> to<00:07:07.669> make<00:07:07.849> them<00:07:08.060> honor 00:07:08.800 --> 00:07:08.810 align:start position:0% transfer functions to make them honor 00:07:08.810 --> 00:07:11.379 align:start position:0% transfer functions to make them honor this<00:07:09.139> new<00:07:09.380> extra<00:07:10.069> restriction<00:07:10.849> on<00:07:10.910> that<00:07:10.970> so 00:07:11.379 --> 00:07:11.389 align:start position:0% this new extra restriction on that so 00:07:11.389 --> 00:07:14.860 align:start position:0% this new extra restriction on that so let's<00:07:11.599> see<00:07:11.720> how<00:07:11.930> this<00:07:12.169> would<00:07:12.319> look<00:07:12.349> on<00:07:12.620> coal<00:07:13.870> we 00:07:14.860 --> 00:07:14.870 align:start position:0% let's see how this would look on coal we 00:07:14.870 --> 00:07:16.240 align:start position:0% let's see how this would look on coal we had<00:07:14.990> this<00:07:15.139> I<00:07:15.500> don't<00:07:15.710> know<00:07:15.830> if<00:07:15.889> you<00:07:15.949> can<00:07:16.069> see 00:07:16.240 --> 00:07:16.250 align:start position:0% had this I don't know if you can see 00:07:16.250 --> 00:07:18.730 align:start position:0% had this I don't know if you can see this<00:07:16.370> but<00:07:16.610> you<00:07:16.880> had<00:07:17.150> this<00:07:17.270> a<00:07:17.539> new<00:07:18.110> log<00:07:18.319> function 00:07:18.730 --> 00:07:18.740 align:start position:0% this but you had this a new log function 00:07:18.740 --> 00:07:20.710 align:start position:0% this but you had this a new log function which<00:07:19.190> basically<00:07:19.250> calls<00:07:20.120> the<00:07:20.330> standard 00:07:20.710 --> 00:07:20.720 align:start position:0% which basically calls the standard 00:07:20.720 --> 00:07:24.370 align:start position:0% which basically calls the standard transfer<00:07:21.080> function<00:07:21.500> and<00:07:21.770> then<00:07:22.699> adds<00:07:23.000> in<00:07:23.690> a<00:07:23.750> in 00:07:24.370 --> 00:07:24.380 align:start position:0% transfer function and then adds in a in 00:07:24.380 --> 00:07:27.640 align:start position:0% transfer function and then adds in a in an<00:07:24.560> array<00:07:24.800> of<00:07:25.069> blocks<00:07:25.340> for<00:07:25.729> each<00:07:25.819> address<00:07:26.650> when 00:07:27.640 --> 00:07:27.650 align:start position:0% an array of blocks for each address when 00:07:27.650 --> 00:07:29.800 align:start position:0% an array of blocks for each address when those<00:07:27.889> funds<00:07:28.130> should<00:07:28.370> be<00:07:28.430> released<00:07:28.789> and<00:07:29.120> then 00:07:29.800 --> 00:07:29.810 align:start position:0% those funds should be released and then 00:07:29.810 --> 00:07:31.499 align:start position:0% those funds should be released and then what<00:07:30.380> we<00:07:30.500> need<00:07:30.620> to<00:07:30.710> add<00:07:30.830> to<00:07:30.979> that<00:07:31.099> is 00:07:31.499 --> 00:07:31.509 align:start position:0% what we need to add to that is 00:07:31.509 --> 00:07:33.490 align:start position:0% what we need to add to that is overriding<00:07:32.509> the<00:07:32.840> standard<00:07:33.169> transfer 00:07:33.490 --> 00:07:33.500 align:start position:0% overriding the standard transfer 00:07:33.500 --> 00:07:36.820 align:start position:0% overriding the standard transfer functions<00:07:34.630> adding<00:07:35.630> this<00:07:35.780> extra<00:07:35.960> restriction 00:07:36.820 --> 00:07:36.830 align:start position:0% functions adding this extra restriction 00:07:36.830 --> 00:07:41.499 align:start position:0% functions adding this extra restriction where<00:07:37.720> which<00:07:38.889> via<00:07:39.889> DS<00:07:40.130> can<00:07:40.520> transfer<00:07:41.120> modifier 00:07:41.499 --> 00:07:41.509 align:start position:0% where which via DS can transfer modifier 00:07:41.509 --> 00:07:43.719 align:start position:0% where which via DS can transfer modifier which<00:07:41.750> checks<00:07:42.050> the<00:07:42.319> amount<00:07:43.009> of<00:07:43.159> transferable 00:07:43.719 --> 00:07:43.729 align:start position:0% which checks the amount of transferable 00:07:43.729 --> 00:07:46.059 align:start position:0% which checks the amount of transferable tokens<00:07:44.210> at<00:07:44.419> a<00:07:44.479> certain<00:07:44.960> point<00:07:45.139> in<00:07:45.349> time<00:07:45.380> and 00:07:46.059 --> 00:07:46.069 align:start position:0% tokens at a certain point in time and 00:07:46.069 --> 00:07:49.029 align:start position:0% tokens at a certain point in time and enables<00:07:46.849> or<00:07:47.030> disables<00:07:47.479> the<00:07:47.990> transfers<00:07:48.409> and 00:07:49.029 --> 00:07:49.039 align:start position:0% enables or disables the transfers and 00:07:49.039 --> 00:07:51.850 align:start position:0% enables or disables the transfers and then<00:07:49.400> to<00:07:49.550> implement<00:07:49.759> this<00:07:50.539> a<00:07:50.900> transferable 00:07:51.850 --> 00:07:51.860 align:start position:0% then to implement this a transferable 00:07:51.860 --> 00:07:54.159 align:start position:0% then to implement this a transferable token<00:07:52.610> amount<00:07:52.880> what<00:07:53.240> we<00:07:53.360> do<00:07:53.479> is<00:07:53.539> we<00:07:53.690> iterate 00:07:54.159 --> 00:07:54.169 align:start position:0% token amount what we do is we iterate 00:07:54.169 --> 00:07:57.550 align:start position:0% token amount what we do is we iterate over<00:07:54.380> the<00:07:54.710> array<00:07:54.740> of<00:07:55.219> locks<00:07:55.520> for<00:07:55.909> every<00:07:56.120> ad<00:07:56.750> for 00:07:57.550 --> 00:07:57.560 align:start position:0% over the array of locks for every ad for 00:07:57.560 --> 00:07:59.589 align:start position:0% over the array of locks for every ad for that<00:07:57.710> address<00:07:58.099> and<00:07:58.340> we<00:07:58.490> add<00:07:58.610> up<00:07:58.639> the<00:07:59.270> amount<00:07:59.479> of 00:07:59.589 --> 00:07:59.599 align:start position:0% that address and we add up the amount of 00:07:59.599 --> 00:08:02.709 align:start position:0% that address and we add up the amount of locked<00:07:59.870> tokens<00:08:00.380> and<00:08:00.680> we<00:08:00.919> we<00:08:01.460> return<00:08:01.849> the<00:08:02.509> total 00:08:02.709 --> 00:08:02.719 align:start position:0% locked tokens and we we return the total 00:08:02.719 --> 00:08:05.950 align:start position:0% locked tokens and we we return the total balance<00:08:02.990> -<00:08:03.860> the<00:08:04.070> locks<00:08:04.280> oaken's<00:08:04.750> so<00:08:05.750> in<00:08:05.870> this 00:08:05.950 --> 00:08:05.960 align:start position:0% balance - the locks oaken's so in this 00:08:05.960 --> 00:08:08.320 align:start position:0% balance - the locks oaken's so in this way<00:08:06.550> apparently<00:08:07.550> we<00:08:07.729> added<00:08:07.969> a<00:08:08.030> cool<00:08:08.180> new 00:08:08.320 --> 00:08:08.330 align:start position:0% way apparently we added a cool new 00:08:08.330 --> 00:08:10.450 align:start position:0% way apparently we added a cool new feature<00:08:08.570> to<00:08:08.840> our<00:08:08.930> token<00:08:09.349> and<00:08:09.560> it<00:08:10.009> seems<00:08:10.250> great 00:08:10.450 --> 00:08:10.460 align:start position:0% feature to our token and it seems great 00:08:10.460 --> 00:08:13.629 align:start position:0% feature to our token and it seems great but<00:08:10.759> it<00:08:11.719> actually<00:08:11.990> has<00:08:12.860> a<00:08:12.889> big<00:08:13.159> problem 00:08:13.629 --> 00:08:13.639 align:start position:0% but it actually has a big problem 00:08:13.639 --> 00:08:16.330 align:start position:0% but it actually has a big problem did<00:08:14.150> anyone<00:08:14.360> can<00:08:15.139> even<00:08:15.380> tell<00:08:15.979> me<00:08:16.130> what<00:08:16.250> the 00:08:16.330 --> 00:08:16.340 align:start position:0% did anyone can even tell me what the 00:08:16.340 --> 00:08:19.200 align:start position:0% did anyone can even tell me what the problem<00:08:16.430> is 00:08:19.200 --> 00:08:19.210 align:start position:0% 00:08:19.210 --> 00:08:25.990 align:start position:0% good<00:08:20.210> good<00:08:20.569> you<00:08:21.050> want<00:08:21.229> a<00:08:21.319> t-shirt<00:08:24.729> so<00:08:25.729> we<00:08:25.849> have 00:08:25.990 --> 00:08:26.000 align:start position:0% good good you want a t-shirt so we have 00:08:26.000 --> 00:08:28.059 align:start position:0% good good you want a t-shirt so we have a<00:08:26.030> case<00:08:26.270> of<00:08:26.330> a<00:08:26.599> gassy<00:08:26.990> array<00:08:27.259> as<00:08:27.500> we<00:08:27.800> like<00:08:27.949> to 00:08:28.059 --> 00:08:28.069 align:start position:0% a case of a gassy array as we like to 00:08:28.069 --> 00:08:30.219 align:start position:0% a case of a gassy array as we like to call<00:08:28.250> it<00:08:28.370> the<00:08:29.270> problem<00:08:29.630> with<00:08:29.750> this<00:08:29.900> array<00:08:30.169> is 00:08:30.219 --> 00:08:30.229 align:start position:0% call it the problem with this array is 00:08:30.229 --> 00:08:33.159 align:start position:0% call it the problem with this array is that<00:08:30.590> the<00:08:30.889> length<00:08:31.099> of<00:08:31.400> it<00:08:31.789> is<00:08:32.510> controlled<00:08:33.050> by 00:08:33.159 --> 00:08:33.169 align:start position:0% that the length of it is controlled by 00:08:33.169 --> 00:08:35.050 align:start position:0% that the length of it is controlled by anyone<00:08:33.979> that<00:08:34.130> can<00:08:34.430> call<00:08:34.610> the<00:08:34.729> log<00:08:34.880> function 00:08:35.050 --> 00:08:35.060 align:start position:0% anyone that can call the log function 00:08:35.060 --> 00:08:38.230 align:start position:0% anyone that can call the log function which<00:08:35.510> is<00:08:35.659> in<00:08:35.810> this<00:08:36.169> case<00:08:36.229> is<00:08:36.560> public<00:08:36.950> so<00:08:37.820> you 00:08:38.230 --> 00:08:38.240 align:start position:0% which is in this case is public so you 00:08:38.240 --> 00:08:40.690 align:start position:0% which is in this case is public so you need<00:08:39.020> to<00:08:39.169> see<00:08:39.349> the<00:08:39.440> length<00:08:39.620> of<00:08:39.800> the<00:08:39.950> array<00:08:40.099> as<00:08:40.370> a 00:08:40.690 --> 00:08:40.700 align:start position:0% need to see the length of the array as a 00:08:40.700 --> 00:08:43.000 align:start position:0% need to see the length of the array as a user<00:08:40.909> input<00:08:41.360> and<00:08:41.599> as<00:08:42.169> you<00:08:42.289> know<00:08:42.409> in<00:08:42.560> security 00:08:43.000 --> 00:08:43.010 align:start position:0% user input and as you know in security 00:08:43.010 --> 00:08:46.210 align:start position:0% user input and as you know in security you<00:08:43.039> need<00:08:43.190> to<00:08:43.339> sanitize<00:08:43.570> inputs<00:08:44.570> and<00:08:45.220> any 00:08:46.210 --> 00:08:46.220 align:start position:0% you need to sanitize inputs and any 00:08:46.220 --> 00:08:48.519 align:start position:0% you need to sanitize inputs and any anyone<00:08:46.820> can<00:08:47.060> call<00:08:47.300> the<00:08:47.750> log<00:08:47.899> function<00:08:48.110> and 00:08:48.519 --> 00:08:48.529 align:start position:0% anyone can call the log function and 00:08:48.529 --> 00:08:50.890 align:start position:0% anyone can call the log function and create<00:08:48.800> lots<00:08:49.190> of<00:08:49.310> locks<00:08:49.579> in<00:08:49.820> the<00:08:50.060> array<00:08:50.270> of<00:08:50.570> of 00:08:50.890 --> 00:08:50.900 align:start position:0% create lots of locks in the array of of 00:08:50.900 --> 00:08:53.769 align:start position:0% create lots of locks in the array of of someone<00:08:51.560> they<00:08:51.800> want<00:08:51.980> to<00:08:52.190> mess<00:08:52.610> with<00:08:52.820> and<00:08:53.060> the 00:08:53.769 --> 00:08:53.779 align:start position:0% someone they want to mess with and the 00:08:53.779 --> 00:08:56.199 align:start position:0% someone they want to mess with and the array<00:08:53.959> if<00:08:54.230> in<00:08:54.680> this<00:08:54.860> case<00:08:54.920> I<00:08:55.339> tried<00:08:55.730> it<00:08:55.880> and<00:08:56.000> if 00:08:56.199 --> 00:08:56.209 align:start position:0% array if in this case I tried it and if 00:08:56.209 --> 00:08:56.470 align:start position:0% array if in this case I tried it and if you 00:08:56.470 --> 00:08:56.480 align:start position:0% you 00:08:56.480 --> 00:08:58.930 align:start position:0% you like<00:08:56.750> 5,000<00:08:57.620> logs<00:08:57.830> to<00:08:58.190> Anna<00:08:58.370> to<00:08:58.700> an<00:08:58.790> address 00:08:58.930 --> 00:08:58.940 align:start position:0% like 5,000 logs to Anna to an address 00:08:58.940 --> 00:09:03.160 align:start position:0% like 5,000 logs to Anna to an address the<00:08:59.750> gas<00:08:59.990> cost<00:09:00.440> of<00:09:00.680> calling<00:09:01.070> a<00:09:01.190> transfer<00:09:02.170> for 00:09:03.160 --> 00:09:03.170 align:start position:0% the gas cost of calling a transfer for 00:09:03.170 --> 00:09:05.470 align:start position:0% the gas cost of calling a transfer for that<00:09:03.320> token<00:09:03.710> is<00:09:04.310> so<00:09:04.550> high<00:09:04.760> that<00:09:04.790> it<00:09:05.180> doesn't 00:09:05.470 --> 00:09:05.480 align:start position:0% that token is so high that it doesn't 00:09:05.480 --> 00:09:09.490 align:start position:0% that token is so high that it doesn't fit<00:09:05.630> in<00:09:05.900> a<00:09:06.050> block<00:09:06.260> so<00:09:07.180> the<00:09:08.180> point<00:09:08.390> here<00:09:08.600> is<00:09:08.630> I'm 00:09:09.490 --> 00:09:09.500 align:start position:0% fit in a block so the point here is I'm 00:09:09.500 --> 00:09:13.150 align:start position:0% fit in a block so the point here is I'm sorry<00:09:10.750> by<00:09:11.750> adding<00:09:12.020> an<00:09:12.140> extra<00:09:12.500> feature<00:09:12.680> we 00:09:13.150 --> 00:09:13.160 align:start position:0% sorry by adding an extra feature we 00:09:13.160 --> 00:09:14.350 align:start position:0% sorry by adding an extra feature we actually<00:09:13.490> introduced<00:09:13.850> a<00:09:13.970> security 00:09:14.350 --> 00:09:14.360 align:start position:0% actually introduced a security 00:09:14.360 --> 00:09:17.110 align:start position:0% actually introduced a security vulnerability<00:09:15.310> so<00:09:16.310> there's<00:09:16.700> a<00:09:16.730> simple<00:09:17.090> fix 00:09:17.110 --> 00:09:17.120 align:start position:0% vulnerability so there's a simple fix 00:09:17.120 --> 00:09:20.080 align:start position:0% vulnerability so there's a simple fix for<00:09:17.540> this<00:09:17.630> which<00:09:18.380> is<00:09:18.590> adding<00:09:18.980> a<00:09:19.130> an<00:09:19.700> upper 00:09:20.080 --> 00:09:20.090 align:start position:0% for this which is adding a an upper 00:09:20.090 --> 00:09:21.700 align:start position:0% for this which is adding a an upper bound<00:09:20.240> to<00:09:20.420> the<00:09:20.510> amount<00:09:20.750> of<00:09:20.870> logs<00:09:21.140> for<00:09:21.440> every 00:09:21.700 --> 00:09:21.710 align:start position:0% bound to the amount of logs for every 00:09:21.710 --> 00:09:25.750 align:start position:0% bound to the amount of logs for every address<00:09:21.860> but<00:09:22.640> I<00:09:22.670> wanted<00:09:22.940> to<00:09:24.490> make<00:09:25.490> you<00:09:25.610> think 00:09:25.750 --> 00:09:25.760 align:start position:0% address but I wanted to make you think 00:09:25.760 --> 00:09:27.670 align:start position:0% address but I wanted to make you think about<00:09:25.910> a<00:09:26.240> different<00:09:26.660> approach<00:09:26.750> to<00:09:27.320> adding 00:09:27.670 --> 00:09:27.680 align:start position:0% about a different approach to adding 00:09:27.680 --> 00:09:29.440 align:start position:0% about a different approach to adding features<00:09:27.860> to<00:09:28.160> a<00:09:28.190> tokens<00:09:28.550> which<00:09:28.790> solves<00:09:29.300> this 00:09:29.440 --> 00:09:29.450 align:start position:0% features to a tokens which solves this 00:09:29.450 --> 00:09:31.120 align:start position:0% features to a tokens which solves this problem<00:09:29.600> in<00:09:29.930> particular<00:09:30.170> and<00:09:30.590> I<00:09:30.800> think<00:09:31.010> it's 00:09:31.120 --> 00:09:31.130 align:start position:0% problem in particular and I think it's 00:09:31.130 --> 00:09:34.840 align:start position:0% problem in particular and I think it's better<00:09:31.250> for<00:09:31.580> security<00:09:32.570> conceptually<00:09:33.730> so<00:09:34.730> the 00:09:34.840 --> 00:09:34.850 align:start position:0% better for security conceptually so the 00:09:34.850 --> 00:09:36.880 align:start position:0% better for security conceptually so the idea<00:09:35.060> is<00:09:35.240> to<00:09:35.450> leave<00:09:35.570> the<00:09:35.720> token<00:09:36.050> assist<00:09:36.530> don't 00:09:36.880 --> 00:09:36.890 align:start position:0% idea is to leave the token assist don't 00:09:36.890 --> 00:09:39.190 align:start position:0% idea is to leave the token assist don't any<00:09:37.340> extra<00:09:37.790> functionality<00:09:38.390> and<00:09:38.690> actually 00:09:39.190 --> 00:09:39.200 align:start position:0% any extra functionality and actually 00:09:39.200 --> 00:09:41.950 align:start position:0% any extra functionality and actually implement<00:09:39.560> the<00:09:39.920> the<00:09:40.370> locking<00:09:41.210> functionality 00:09:41.950 --> 00:09:41.960 align:start position:0% implement the the locking functionality 00:09:41.960 --> 00:09:44.290 align:start position:0% implement the the locking functionality as<00:09:42.170> an<00:09:42.320> external<00:09:42.710> contract<00:09:43.400> so<00:09:43.970> when<00:09:44.120> a<00:09:44.150> user 00:09:44.290 --> 00:09:44.300 align:start position:0% as an external contract so when a user 00:09:44.300 --> 00:09:46.930 align:start position:0% as an external contract so when a user wants<00:09:44.720> to<00:09:44.750> lock<00:09:45.050> tokens<00:09:45.920> for<00:09:46.130> another<00:09:46.400> they 00:09:46.930 --> 00:09:46.940 align:start position:0% wants to lock tokens for another they 00:09:46.940 --> 00:09:49.510 align:start position:0% wants to lock tokens for another they instantiate<00:09:47.570> one<00:09:47.840> of<00:09:47.960> these<00:09:48.140> new<00:09:48.740> token<00:09:49.190> time 00:09:49.510 --> 00:09:49.520 align:start position:0% instantiate one of these new token time 00:09:49.520 --> 00:09:51.400 align:start position:0% instantiate one of these new token time lock<00:09:49.700> contracts<00:09:50.210> which<00:09:50.780> received<00:09:51.230> the 00:09:51.400 --> 00:09:51.410 align:start position:0% lock contracts which received the 00:09:51.410 --> 00:09:53.650 align:start position:0% lock contracts which received the beneficiary<00:09:52.130> address<00:09:52.520> and<00:09:52.820> the<00:09:53.090> release<00:09:53.390> time 00:09:53.650 --> 00:09:53.660 align:start position:0% beneficiary address and the release time 00:09:53.660 --> 00:09:55.960 align:start position:0% beneficiary address and the release time and<00:09:53.810> then<00:09:54.350> transfers<00:09:54.920> the<00:09:54.950> the<00:09:55.580> tokens 00:09:55.960 --> 00:09:55.970 align:start position:0% and then transfers the the tokens 00:09:55.970 --> 00:09:58.630 align:start position:0% and then transfers the the tokens manually<00:09:56.840> from<00:09:57.140> the<00:09:57.320> from<00:09:57.860> the<00:09:57.950> normal<00:09:58.340> token 00:09:58.630 --> 00:09:58.640 align:start position:0% manually from the from the normal token 00:09:58.640 --> 00:10:02.380 align:start position:0% manually from the from the normal token contract<00:09:59.030> and<00:09:59.630> now<00:09:59.870> if<00:10:00.200> in<00:10:01.070> this<00:10:01.250> case<00:10:01.310> the<00:10:01.520> the 00:10:02.380 --> 00:10:02.390 align:start position:0% contract and now if in this case the the 00:10:02.390 --> 00:10:04.030 align:start position:0% contract and now if in this case the the previous<00:10:02.720> vulnerability<00:10:03.290> with<00:10:03.440> legacy<00:10:03.740> array 00:10:04.030 --> 00:10:04.040 align:start position:0% previous vulnerability with legacy array 00:10:04.040 --> 00:10:06.040 align:start position:0% previous vulnerability with legacy array was<00:10:04.220> solved<00:10:04.550> but<00:10:05.120> if<00:10:05.240> there<00:10:05.450> were<00:10:05.660> one 00:10:06.040 --> 00:10:06.050 align:start position:0% was solved but if there were one 00:10:06.050 --> 00:10:07.900 align:start position:0% was solved but if there were one vulnerability<00:10:06.830> in<00:10:06.980> this<00:10:07.130> new<00:10:07.310> contract<00:10:07.730> only 00:10:07.900 --> 00:10:07.910 align:start position:0% vulnerability in this new contract only 00:10:07.910 --> 00:10:10.480 align:start position:0% vulnerability in this new contract only the<00:10:08.180> users<00:10:08.530> using<00:10:09.530> this<00:10:09.650> extra<00:10:10.040> feature<00:10:10.250> would 00:10:10.480 --> 00:10:10.490 align:start position:0% the users using this extra feature would 00:10:10.490 --> 00:10:12.880 align:start position:0% the users using this extra feature would be<00:10:10.640> affected<00:10:11.260> whereas<00:10:12.260> with<00:10:12.470> the<00:10:12.590> previous 00:10:12.880 --> 00:10:12.890 align:start position:0% be affected whereas with the previous 00:10:12.890 --> 00:10:15.100 align:start position:0% be affected whereas with the previous version<00:10:12.950> any<00:10:13.460> vulnerability<00:10:14.390> potentially 00:10:15.100 --> 00:10:15.110 align:start position:0% version any vulnerability potentially 00:10:15.110 --> 00:10:17.080 align:start position:0% version any vulnerability potentially could<00:10:15.260> affect<00:10:15.320> normal<00:10:16.220> users<00:10:16.670> that<00:10:16.820> didn't 00:10:17.080 --> 00:10:17.090 align:start position:0% could affect normal users that didn't 00:10:17.090 --> 00:10:19.930 align:start position:0% could affect normal users that didn't want<00:10:17.210> to<00:10:17.390> use<00:10:17.510> the<00:10:17.660> lock<00:10:17.810> function<00:10:18.460> so<00:10:19.460> this<00:10:19.820> is 00:10:19.930 --> 00:10:19.940 align:start position:0% want to use the lock function so this is 00:10:19.940 --> 00:10:22.900 align:start position:0% want to use the lock function so this is one<00:10:20.060> of<00:10:20.090> the<00:10:20.240> patterns<00:10:20.390> with<00:10:20.810> sin<00:10:21.550> in<00:10:22.550> terms<00:10:22.760> of 00:10:22.900 --> 00:10:22.910 align:start position:0% one of the patterns with sin in terms of 00:10:22.910 --> 00:10:25.210 align:start position:0% one of the patterns with sin in terms of improving<00:10:23.510> security<00:10:23.750> in<00:10:24.260> new<00:10:24.830> function 00:10:25.210 --> 00:10:25.220 align:start position:0% improving security in new function 00:10:25.220 --> 00:10:28.630 align:start position:0% improving security in new function design<00:10:25.870> and<00:10:26.870> the<00:10:27.500> point<00:10:27.710> is<00:10:27.860> when<00:10:28.370> you're 00:10:28.630 --> 00:10:28.640 align:start position:0% design and the point is when you're 00:10:28.640 --> 00:10:30.040 align:start position:0% design and the point is when you're thinking<00:10:28.850> about<00:10:29.120> adding<00:10:29.540> new<00:10:29.660> features<00:10:29.840> to 00:10:30.040 --> 00:10:30.050 align:start position:0% thinking about adding new features to 00:10:30.050 --> 00:10:31.810 align:start position:0% thinking about adding new features to your<00:10:30.350> contracts<00:10:30.830> really<00:10:31.220> think<00:10:31.490> about<00:10:31.700> the 00:10:31.810 --> 00:10:31.820 align:start position:0% your contracts really think about the 00:10:31.820 --> 00:10:33.940 align:start position:0% your contracts really think about the security<00:10:32.060> implications<00:10:32.810> not<00:10:33.470> always<00:10:33.740> having 00:10:33.940 --> 00:10:33.950 align:start position:0% security implications not always having 00:10:33.950 --> 00:10:35.500 align:start position:0% security implications not always having more<00:10:34.190> features<00:10:34.520> is<00:10:34.670> better<00:10:34.880> because<00:10:35.150> you 00:10:35.500 --> 00:10:35.510 align:start position:0% more features is better because you 00:10:35.510 --> 00:10:37.540 align:start position:0% more features is better because you increase<00:10:35.780> the<00:10:35.960> attack<00:10:36.380> surface<00:10:36.560> and<00:10:37.310> for 00:10:37.540 --> 00:10:37.550 align:start position:0% increase the attack surface and for 00:10:37.550 --> 00:10:39.970 align:start position:0% increase the attack surface and for another<00:10:37.790> example<00:10:37.910> of<00:10:38.780> how<00:10:39.440> this<00:10:39.590> has<00:10:39.770> been 00:10:39.970 --> 00:10:39.980 align:start position:0% another example of how this has been 00:10:39.980 --> 00:10:42.160 align:start position:0% another example of how this has been implemented<00:10:40.910> in<00:10:41.000> the<00:10:41.120> industry<00:10:41.510> at<00:10:42.020> the 00:10:42.160 --> 00:10:42.170 align:start position:0% implemented in the industry at the 00:10:42.170 --> 00:10:43.900 align:start position:0% implemented in the industry at the beginning<00:10:42.440> of<00:10:42.590> the<00:10:42.740> year<00:10:42.980> most<00:10:43.250> crowd<00:10:43.640> sales 00:10:43.900 --> 00:10:43.910 align:start position:0% beginning of the year most crowd sales 00:10:43.910 --> 00:10:45.700 align:start position:0% beginning of the year most crowd sales were<00:10:44.090> implemented<00:10:44.630> as<00:10:44.750> part<00:10:45.110> of<00:10:45.230> the<00:10:45.380> token 00:10:45.700 --> 00:10:45.710 align:start position:0% were implemented as part of the token 00:10:45.710 --> 00:10:48.760 align:start position:0% were implemented as part of the token code<00:10:45.950> and<00:10:46.340> now<00:10:46.910> most<00:10:47.540> most<00:10:48.170> crowd<00:10:48.380> cells<00:10:48.590> are 00:10:48.760 --> 00:10:48.770 align:start position:0% code and now most most crowd cells are 00:10:48.770 --> 00:10:51.910 align:start position:0% code and now most most crowd cells are implemented<00:10:49.310> as<00:10:49.460> a<00:10:49.520> separate<00:10:49.970> module<00:10:50.200> so<00:10:51.200> it 00:10:51.910 --> 00:10:51.920 align:start position:0% implemented as a separate module so it 00:10:51.920 --> 00:10:53.410 align:start position:0% implemented as a separate module so it if<00:10:52.280> you<00:10:52.460> think<00:10:52.610> about<00:10:52.760> it<00:10:52.970> doesn't<00:10:53.300> make<00:10:53.390> sense 00:10:53.410 --> 00:10:53.420 align:start position:0% if you think about it doesn't make sense 00:10:53.420 --> 00:10:55.930 align:start position:0% if you think about it doesn't make sense to<00:10:53.780> have<00:10:53.960> all<00:10:54.230> the<00:10:54.440> crowd<00:10:54.800> sale<00:10:55.040> code<00:10:55.460> in<00:10:55.730> the 00:10:55.930 --> 00:10:55.940 align:start position:0% to have all the crowd sale code in the 00:10:55.940 --> 00:10:58.150 align:start position:0% to have all the crowd sale code in the token<00:10:56.270> forever<00:10:56.600> for<00:10:56.870> just<00:10:57.110> two<00:10:57.650> weeks<00:10:57.860> or<00:10:58.100> two 00:10:58.150 --> 00:10:58.160 align:start position:0% token forever for just two weeks or two 00:10:58.160 --> 00:11:02.800 align:start position:0% token forever for just two weeks or two minutes<00:10:58.730> of<00:10:58.850> course<00:10:59.060> he'll<00:11:01.360> finally<00:11:02.360> this<00:11:02.540> I 00:11:02.800 --> 00:11:02.810 align:start position:0% minutes of course he'll finally this I 00:11:02.810 --> 00:11:04.960 align:start position:0% minutes of course he'll finally this I want<00:11:03.320> to<00:11:03.380> talk<00:11:03.530> about<00:11:03.650> some<00:11:04.070> the<00:11:04.340> relation 00:11:04.960 --> 00:11:04.970 align:start position:0% want to talk about some the relation 00:11:04.970 --> 00:11:06.850 align:start position:0% want to talk about some the relation between<00:11:05.080> basic<00:11:06.080> security<00:11:06.530> software 00:11:06.850 --> 00:11:06.860 align:start position:0% between basic security software 00:11:06.860 --> 00:11:08.690 align:start position:0% between basic security software engineering<00:11:07.310> practices<00:11:07.820> and<00:11:08.210> more 00:11:08.690 --> 00:11:08.700 align:start position:0% engineering practices and more 00:11:08.700 --> 00:11:11.180 align:start position:0% engineering practices and more under<00:11:08.820> security<00:11:09.620> these<00:11:10.620> are<00:11:10.680> very<00:11:10.980> simple 00:11:11.180 --> 00:11:11.190 align:start position:0% under security these are very simple 00:11:11.190 --> 00:11:14.060 align:start position:0% under security these are very simple stuff<00:11:11.550> but<00:11:11.990> they<00:11:12.990> are<00:11:13.110> not<00:11:13.290> being<00:11:13.500> applied<00:11:13.740> in 00:11:14.060 --> 00:11:14.070 align:start position:0% stuff but they are not being applied in 00:11:14.070 --> 00:11:16.250 align:start position:0% stuff but they are not being applied in in<00:11:14.310> our<00:11:14.460> industry<00:11:14.880> and<00:11:14.910> I<00:11:15.510> think<00:11:15.990> this<00:11:16.110> is 00:11:16.250 --> 00:11:16.260 align:start position:0% in our industry and I think this is 00:11:16.260 --> 00:11:18.680 align:start position:0% in our industry and I think this is basic<00:11:16.950> stuff<00:11:17.040> we<00:11:17.280> should<00:11:17.490> be<00:11:17.610> doing 00:11:18.680 --> 00:11:18.690 align:start position:0% basic stuff we should be doing 00:11:18.690 --> 00:11:20.900 align:start position:0% basic stuff we should be doing so<00:11:19.170> first<00:11:19.590> is<00:11:19.740> clear<00:11:20.190> and<00:11:20.310> simple<00:11:20.490> code<00:11:20.790> is 00:11:20.900 --> 00:11:20.910 align:start position:0% so first is clear and simple code is 00:11:20.910 --> 00:11:22.790 align:start position:0% so first is clear and simple code is always<00:11:21.180> better<00:11:21.510> for<00:11:21.630> security<00:11:22.200> while 00:11:22.790 --> 00:11:22.800 align:start position:0% always better for security while 00:11:22.800 --> 00:11:25.340 align:start position:0% always better for security while security<00:11:23.130> problems<00:11:23.550> come<00:11:23.850> from<00:11:24.210> a<00:11:24.540> difference 00:11:25.340 --> 00:11:25.350 align:start position:0% security problems come from a difference 00:11:25.350 --> 00:11:27.530 align:start position:0% security problems come from a difference between<00:11:25.740> the<00:11:26.250> programmers<00:11:26.760> intention<00:11:27.330> and 00:11:27.530 --> 00:11:27.540 align:start position:0% between the programmers intention and 00:11:27.540 --> 00:11:30.590 align:start position:0% between the programmers intention and what<00:11:27.990> the<00:11:28.110> code<00:11:28.290> actually<00:11:28.530> does<00:11:29.330> so<00:11:30.330> having 00:11:30.590 --> 00:11:30.600 align:start position:0% what the code actually does so having 00:11:30.600 --> 00:11:32.930 align:start position:0% what the code actually does so having clear<00:11:30.930> code<00:11:31.290> makes<00:11:31.530> it<00:11:31.710> easier<00:11:31.980> to<00:11:32.010> check<00:11:32.430> the 00:11:32.930 --> 00:11:32.940 align:start position:0% clear code makes it easier to check the 00:11:32.940 --> 00:11:35.300 align:start position:0% clear code makes it easier to check the programmers<00:11:33.420> intention<00:11:34.020> and<00:11:34.200> that<00:11:34.680> the<00:11:34.830> code 00:11:35.300 --> 00:11:35.310 align:start position:0% programmers intention and that the code 00:11:35.310 --> 00:11:37.730 align:start position:0% programmers intention and that the code actually<00:11:35.460> does<00:11:35.670> what<00:11:36.030> he<00:11:36.180> wants<00:11:36.210> a<00:11:36.740> corollary 00:11:37.730 --> 00:11:37.740 align:start position:0% actually does what he wants a corollary 00:11:37.740 --> 00:11:40.460 align:start position:0% actually does what he wants a corollary of<00:11:37.860> this<00:11:38.070> is<00:11:38.130> that<00:11:38.520> naming<00:11:38.880> matters<00:11:39.450> have<00:11:40.170> seen 00:11:40.460 --> 00:11:40.470 align:start position:0% of this is that naming matters have seen 00:11:40.470 --> 00:11:41.990 align:start position:0% of this is that naming matters have seen really<00:11:40.830> really<00:11:41.160> bad<00:11:41.310> naming<00:11:41.640> in<00:11:41.760> many 00:11:41.990 --> 00:11:42.000 align:start position:0% really really bad naming in many 00:11:42.000 --> 00:11:43.820 align:start position:0% really really bad naming in many contracts<00:11:42.510> so<00:11:42.810> please<00:11:43.050> take<00:11:43.380> your<00:11:43.440> time<00:11:43.680> and 00:11:43.820 --> 00:11:43.830 align:start position:0% contracts so please take your time and 00:11:43.830 --> 00:11:45.200 align:start position:0% contracts so please take your time and think<00:11:43.860> about<00:11:44.190> naming<00:11:44.400> because<00:11:44.790> it<00:11:44.910> helps 00:11:45.200 --> 00:11:45.210 align:start position:0% think about naming because it helps 00:11:45.210 --> 00:11:48.590 align:start position:0% think about naming because it helps increase<00:11:45.840> the<00:11:46.140> security<00:11:46.350> of<00:11:46.590> your<00:11:46.770> code<00:11:47.600> reuse 00:11:48.590 --> 00:11:48.600 align:start position:0% increase the security of your code reuse 00:11:48.600 --> 00:11:50.960 align:start position:0% increase the security of your code reuse existing<00:11:48.930> audited<00:11:49.650> call<00:11:50.010> there's<00:11:50.400> plenty<00:11:50.940> of 00:11:50.960 --> 00:11:50.970 align:start position:0% existing audited call there's plenty of 00:11:50.970 --> 00:11:52.820 align:start position:0% existing audited call there's plenty of good<00:11:51.480> libraries<00:11:51.870> out<00:11:52.020> there<00:11:52.200> you<00:11:52.350> can<00:11:52.530> reuse 00:11:52.820 --> 00:11:52.830 align:start position:0% good libraries out there you can reuse 00:11:52.830 --> 00:11:54.920 align:start position:0% good libraries out there you can reuse there<00:11:53.580> you<00:11:54.060> can't<00:11:54.270> imagine<00:11:54.600> how<00:11:54.720> many<00:11:54.780> times 00:11:54.920 --> 00:11:54.930 align:start position:0% there you can't imagine how many times 00:11:54.930 --> 00:11:57.770 align:start position:0% there you can't imagine how many times we<00:11:55.350> reorder<00:11:55.950> at<00:11:56.130> the<00:11:56.250> same<00:11:56.780> re-implementation 00:11:57.770 --> 00:11:57.780 align:start position:0% we reorder at the same re-implementation 00:11:57.780 --> 00:12:03.170 align:start position:0% we reorder at the same re-implementation of<00:11:58.130> GRC<00:11:59.130> 20<00:11:59.490> standard<00:11:59.820> tokens<00:12:02.000> also<00:12:03.000> don't 00:12:03.170 --> 00:12:03.180 align:start position:0% of GRC 20 standard tokens also don't 00:12:03.180 --> 00:12:06.080 align:start position:0% of GRC 20 standard tokens also don't copy<00:12:03.360> paste<00:12:03.630> code<00:12:03.870> because<00:12:04.200> if<00:12:04.440> the<00:12:05.090> code 00:12:06.080 --> 00:12:06.090 align:start position:0% copy paste code because if the code 00:12:06.090 --> 00:12:07.700 align:start position:0% copy paste code because if the code you're<00:12:06.240> using<00:12:06.480> is<00:12:06.630> updated<00:12:07.080> you<00:12:07.110> don't<00:12:07.620> get 00:12:07.700 --> 00:12:07.710 align:start position:0% you're using is updated you don't get 00:12:07.710 --> 00:12:09.620 align:start position:0% you're using is updated you don't get the<00:12:07.830> updates<00:12:08.160> and<00:12:08.940> also<00:12:09.180> don't<00:12:09.330> repeat 00:12:09.620 --> 00:12:09.630 align:start position:0% the updates and also don't repeat 00:12:09.630 --> 00:12:10.160 align:start position:0% the updates and also don't repeat yourself 00:12:10.160 --> 00:12:10.170 align:start position:0% yourself 00:12:10.170 --> 00:12:13.880 align:start position:0% yourself that's<00:12:11.040> also<00:12:11.250> a<00:12:11.400> source<00:12:12.030> of<00:12:12.150> bugs<00:12:12.660> and<00:12:12.990> finally 00:12:13.880 --> 00:12:13.890 align:start position:0% that's also a source of bugs and finally 00:12:13.890 --> 00:12:16.610 align:start position:0% that's also a source of bugs and finally and<00:12:14.010> most<00:12:14.100> importantly<00:12:14.840> write<00:12:15.840> tests<00:12:16.260> that's 00:12:16.610 --> 00:12:16.620 align:start position:0% and most importantly write tests that's 00:12:16.620 --> 00:12:18.320 align:start position:0% and most importantly write tests that's the<00:12:16.770> best<00:12:16.950> way<00:12:17.160> to<00:12:17.190> check<00:12:17.610> that<00:12:17.670> your 00:12:18.320 --> 00:12:18.330 align:start position:0% the best way to check that your 00:12:18.330 --> 00:12:20.240 align:start position:0% the best way to check that your assumptions<00:12:19.260> about<00:12:19.380> the<00:12:19.590> code<00:12:19.800> are<00:12:19.950> correct 00:12:20.240 --> 00:12:20.250 align:start position:0% assumptions about the code are correct 00:12:20.250 --> 00:12:22.010 align:start position:0% assumptions about the code are correct and<00:12:20.580> also<00:12:20.910> if<00:12:21.030> you<00:12:21.150> change<00:12:21.390> the<00:12:21.570> code<00:12:21.720> after 00:12:22.010 --> 00:12:22.020 align:start position:0% and also if you change the code after 00:12:22.020 --> 00:12:24.260 align:start position:0% and also if you change the code after the<00:12:22.350> fact<00:12:22.560> you<00:12:22.800> can<00:12:22.980> prevent<00:12:23.730> regression 00:12:24.260 --> 00:12:24.270 align:start position:0% the fact you can prevent regression 00:12:24.270 --> 00:12:27.410 align:start position:0% the fact you can prevent regression errors<00:12:25.070> so<00:12:26.070> as<00:12:26.370> I<00:12:26.550> was<00:12:26.640> saying<00:12:26.700> all<00:12:27.060> these<00:12:27.180> are 00:12:27.410 --> 00:12:27.420 align:start position:0% errors so as I was saying all these are 00:12:27.420 --> 00:12:28.520 align:start position:0% errors so as I was saying all these are basic<00:12:28.140> security 00:12:28.520 --> 00:12:28.530 align:start position:0% basic security 00:12:28.530 --> 00:12:30.590 align:start position:0% basic security I<00:12:28.620> mean<00:12:28.950> software<00:12:29.820> engineering<00:12:30.180> practices 00:12:30.590 --> 00:12:30.600 align:start position:0% I mean software engineering practices 00:12:30.600 --> 00:12:33.560 align:start position:0% I mean software engineering practices that<00:12:30.780> every<00:12:31.170> developer<00:12:31.800> should<00:12:31.950> be<00:12:32.130> doing<00:12:33.000> but 00:12:33.560 --> 00:12:33.570 align:start position:0% that every developer should be doing but 00:12:33.570 --> 00:12:36.050 align:start position:0% that every developer should be doing but in<00:12:33.720> our<00:12:33.840> case<00:12:34.020> our<00:12:34.320> code<00:12:34.590> manages<00:12:35.190> real<00:12:35.580> money 00:12:36.050 --> 00:12:36.060 align:start position:0% in our case our code manages real money 00:12:36.060 --> 00:12:38.660 align:start position:0% in our case our code manages real money so<00:12:36.750> we<00:12:36.840> need<00:12:36.960> to<00:12:37.050> protect<00:12:37.350> it<00:12:37.500> from<00:12:37.670> ninja 00:12:38.660 --> 00:12:38.670 align:start position:0% so we need to protect it from ninja 00:12:38.670 --> 00:12:41.900 align:start position:0% so we need to protect it from ninja hackers<00:12:39.260> stupid<00:12:40.260> users<00:12:40.620> and<00:12:40.920> other 00:12:41.900 --> 00:12:41.910 align:start position:0% hackers stupid users and other 00:12:41.910 --> 00:12:47.680 align:start position:0% hackers stupid users and other developers<00:12:42.660> in<00:12:42.810> our<00:12:42.870> team 00:12:47.680 --> 00:12:47.690 align:start position:0% 00:12:47.690 --> 00:12:50.900 align:start position:0% so<00:12:48.690> I<00:12:48.990> want<00:12:49.350> to<00:12:49.410> talk<00:12:49.590> briefly<00:12:49.890> about<00:12:50.070> the 00:12:50.900 --> 00:12:50.910 align:start position:0% so I want to talk briefly about the 00:12:50.910 --> 00:12:52.910 align:start position:0% so I want to talk briefly about the relation<00:12:51.330> between<00:12:51.360> security<00:12:51.990> and<00:12:52.380> trust 00:12:52.910 --> 00:12:52.920 align:start position:0% relation between security and trust 00:12:52.920 --> 00:12:56.390 align:start position:0% relation between security and trust reduction<00:12:54.650> let's<00:12:55.650> say<00:12:55.770> you're<00:12:55.950> a<00:12:55.980> freelance 00:12:56.390 --> 00:12:56.400 align:start position:0% reduction let's say you're a freelance 00:12:56.400 --> 00:12:58.100 align:start position:0% reduction let's say you're a freelance solidity<00:12:56.880> developer<00:12:57.390> and<00:12:57.630> your<00:12:57.750> client 00:12:58.100 --> 00:12:58.110 align:start position:0% solidity developer and your client 00:12:58.110 --> 00:13:00.350 align:start position:0% solidity developer and your client requests<00:12:58.590> a<00:12:58.770> cupped<00:12:59.160> crowd<00:12:59.610> sale<00:12:59.850> so<00:13:00.300> you 00:13:00.350 --> 00:13:00.360 align:start position:0% requests a cupped crowd sale so you 00:13:00.360 --> 00:13:03.290 align:start position:0% requests a cupped crowd sale so you write<00:13:01.020> this<00:13:01.140> simple<00:13:01.500> contract<00:13:01.860> I<00:13:02.240> think<00:13:03.240> he 00:13:03.290 --> 00:13:03.300 align:start position:0% write this simple contract I think he 00:13:03.300 --> 00:13:05.090 align:start position:0% write this simple contract I think he comes<00:13:03.510> and<00:13:03.660> say<00:13:03.840> oh<00:13:04.020> wait<00:13:04.230> don't<00:13:04.410> forget<00:13:04.530> we 00:13:05.090 --> 00:13:05.100 align:start position:0% comes and say oh wait don't forget we 00:13:05.100 --> 00:13:06.920 align:start position:0% comes and say oh wait don't forget we need<00:13:05.250> to<00:13:05.340> create<00:13:05.790> tokens<00:13:06.210> for<00:13:06.330> the<00:13:06.480> foundation 00:13:06.920 --> 00:13:06.930 align:start position:0% need to create tokens for the foundation 00:13:06.930 --> 00:13:09.590 align:start position:0% need to create tokens for the foundation to<00:13:06.960> when<00:13:07.290> the<00:13:07.440> crowd<00:13:07.800> cell<00:13:07.980> finishes<00:13:08.400> so<00:13:08.670> you 00:13:09.590 --> 00:13:09.600 align:start position:0% to when the crowd cell finishes so you 00:13:09.600 --> 00:13:11.290 align:start position:0% to when the crowd cell finishes so you go<00:13:09.750> sure<00:13:10.080> boss 00:13:11.290 --> 00:13:11.300 align:start position:0% go sure boss 00:13:11.300 --> 00:13:14.780 align:start position:0% go sure boss you<00:13:12.300> have<00:13:12.740> you<00:13:13.740> make<00:13:13.920> your<00:13:14.190> crowd<00:13:14.550> sale 00:13:14.780 --> 00:13:14.790 align:start position:0% you have you make your crowd sale 00:13:14.790 --> 00:13:17.060 align:start position:0% you have you make your crowd sale ownable<00:13:15.240> so<00:13:15.660> it<00:13:15.840> has<00:13:16.020> an<00:13:16.170> owner<00:13:16.320> and<00:13:16.590> a 00:13:17.060 --> 00:13:17.070 align:start position:0% ownable so it has an owner and a 00:13:17.070 --> 00:13:18.830 align:start position:0% ownable so it has an owner and a privileged<00:13:17.550> function<00:13:18.030> to<00:13:18.240> mint<00:13:18.450> the 00:13:18.830 --> 00:13:18.840 align:start position:0% privileged function to mint the 00:13:18.840 --> 00:13:19.910 align:start position:0% privileged function to mint the Foundation's<00:13:19.320> tokens 00:13:19.910 --> 00:13:19.920 align:start position:0% Foundation's tokens 00:13:19.920 --> 00:13:21.800 align:start position:0% Foundation's tokens once<00:13:20.160> the<00:13:20.460> cup<00:13:20.640> is<00:13:20.790> reached<00:13:21.030> so 00:13:21.800 --> 00:13:21.810 align:start position:0% once the cup is reached so 00:13:21.810 --> 00:13:23.540 align:start position:0% once the cup is reached so only<00:13:22.050> if<00:13:22.140> the<00:13:22.230> cup<00:13:22.380> is<00:13:22.529> reached<00:13:23.040> will<00:13:23.220> it<00:13:23.340> mint 00:13:23.540 --> 00:13:23.550 align:start position:0% only if the cup is reached will it mint 00:13:23.550 --> 00:13:26.090 align:start position:0% only if the cup is reached will it mint tokens<00:13:24.120> but<00:13:24.840> then<00:13:25.020> your<00:13:25.350> client<00:13:25.650> comes<00:13:25.860> back 00:13:26.090 --> 00:13:26.100 align:start position:0% tokens but then your client comes back 00:13:26.100 --> 00:13:28.640 align:start position:0% tokens but then your client comes back and<00:13:26.310> says<00:13:26.490> oh<00:13:26.760> wait<00:13:27.060> but<00:13:27.570> make<00:13:27.750> it<00:13:27.779> trustless<00:13:28.440> I 00:13:28.640 --> 00:13:28.650 align:start position:0% and says oh wait but make it trustless I 00:13:28.650 --> 00:13:31.970 align:start position:0% and says oh wait but make it trustless I don't<00:13:28.890> want<00:13:29.010> to<00:13:29.100> be<00:13:29.190> the<00:13:29.310> owner<00:13:30.050> so<00:13:31.050> you<00:13:31.110> remove 00:13:31.970 --> 00:13:31.980 align:start position:0% don't want to be the owner so you remove 00:13:31.980 --> 00:13:34.550 align:start position:0% don't want to be the owner so you remove the<00:13:32.190> privilege<00:13:32.550> function<00:13:33.000> put<00:13:33.900> it<00:13:34.020> into<00:13:34.350> the 00:13:34.550 --> 00:13:34.560 align:start position:0% the privilege function put it into the 00:13:34.560 --> 00:13:37.490 align:start position:0% the privilege function put it into the buy<00:13:35.310> tokens<00:13:35.760> function<00:13:36.540> so<00:13:37.050> that<00:13:37.080> the<00:13:37.350> last 00:13:37.490 --> 00:13:37.500 align:start position:0% buy tokens function so that the last 00:13:37.500 --> 00:13:39.590 align:start position:0% buy tokens function so that the last investor<00:13:38.070> when<00:13:38.339> the<00:13:38.640> cup<00:13:38.820> is<00:13:38.910> reached<00:13:39.210> means 00:13:39.590 --> 00:13:39.600 align:start position:0% investor when the cup is reached means 00:13:39.600 --> 00:13:42.260 align:start position:0% investor when the cup is reached means the<00:13:39.870> token<00:13:40.230> for<00:13:40.620> the<00:13:40.920> foundation<00:13:41.430> this<00:13:42.120> is 00:13:42.260 --> 00:13:42.270 align:start position:0% the token for the foundation this is 00:13:42.270 --> 00:13:45.100 align:start position:0% the token for the foundation this is better<00:13:42.450> right<00:13:42.690> it's<00:13:42.870> more<00:13:43.350> trustless<00:13:44.089> wait 00:13:45.100 --> 00:13:45.110 align:start position:0% better right it's more trustless wait 00:13:45.110 --> 00:13:48.590 align:start position:0% better right it's more trustless wait now<00:13:46.110> an<00:13:46.890> investor<00:13:47.339> can<00:13:47.520> come<00:13:47.760> after<00:13:48.180> a<00:13:48.210> cap<00:13:48.450> is 00:13:48.590 --> 00:13:48.600 align:start position:0% now an investor can come after a cap is 00:13:48.600 --> 00:13:51.769 align:start position:0% now an investor can come after a cap is reached<00:13:48.870> and<00:13:49.580> with<00:13:50.580> this<00:13:50.730> particular<00:13:51.150> call<00:13:51.390> if 00:13:51.769 --> 00:13:51.779 align:start position:0% reached and with this particular call if 00:13:51.779 --> 00:13:53.630 align:start position:0% reached and with this particular call if the<00:13:52.170> message<00:13:52.500> value<00:13:52.770> equals<00:13:53.070> to<00:13:53.220> zero<00:13:53.460> they 00:13:53.630 --> 00:13:53.640 align:start position:0% the message value equals to zero they 00:13:53.640 --> 00:13:55.760 align:start position:0% the message value equals to zero they can<00:13:53.790> continue<00:13:54.150> calling<00:13:54.960> this<00:13:55.080> buy<00:13:55.320> tokens 00:13:55.760 --> 00:13:55.770 align:start position:0% can continue calling this buy tokens 00:13:55.770 --> 00:13:58.700 align:start position:0% can continue calling this buy tokens getting<00:13:56.550> zero<00:13:56.820> extra<00:13:57.180> tokens<00:13:57.510> but<00:13:57.710> remaining 00:13:58.700 --> 00:13:58.710 align:start position:0% getting zero extra tokens but remaining 00:13:58.710 --> 00:14:00.829 align:start position:0% getting zero extra tokens but remaining tokens<00:13:59.279> for<00:13:59.430> the<00:13:59.520> foundation<00:14:00.060> ruining<00:14:00.720> the 00:14:00.829 --> 00:14:00.839 align:start position:0% tokens for the foundation ruining the 00:14:00.839 --> 00:14:04.370 align:start position:0% tokens for the foundation ruining the crowd<00:14:01.050> sale<00:14:01.640> the<00:14:02.640> point<00:14:02.850> here<00:14:03.060> is<00:14:03.140> it's<00:14:04.140> not 00:14:04.370 --> 00:14:04.380 align:start position:0% crowd sale the point here is it's not 00:14:04.380 --> 00:14:06.710 align:start position:0% crowd sale the point here is it's not always<00:14:04.529> good<00:14:04.920> to<00:14:05.250> leave<00:14:05.570> critical<00:14:06.570> when<00:14:06.690> I 00:14:06.710 --> 00:14:06.720 align:start position:0% always good to leave critical when I 00:14:06.720 --> 00:14:09.079 align:start position:0% always good to leave critical when I relate<00:14:07.050> a<00:14:07.320> critical<00:14:08.070> functionality<00:14:08.670> of<00:14:09.060> your 00:14:09.079 --> 00:14:09.089 align:start position:0% relate a critical functionality of your 00:14:09.089 --> 00:14:11.510 align:start position:0% relate a critical functionality of your contract<00:14:09.750> in<00:14:09.930> the<00:14:10.050> hands<00:14:10.320> of<00:14:10.380> the<00:14:10.560> public<00:14:10.710> it's 00:14:11.510 --> 00:14:11.520 align:start position:0% contract in the hands of the public it's 00:14:11.520 --> 00:14:13.850 align:start position:0% contract in the hands of the public it's sometimes<00:14:11.880> ok<00:14:12.180> exactly<00:14:12.540> sometimes<00:14:13.470> totally 00:14:13.850 --> 00:14:13.860 align:start position:0% sometimes ok exactly sometimes totally 00:14:13.860 --> 00:14:16.519 align:start position:0% sometimes ok exactly sometimes totally ok<00:14:14.339> to<00:14:14.370> live<00:14:14.730> really<00:14:15.420> critical<00:14:15.960> stuff<00:14:16.230> from 00:14:16.519 --> 00:14:16.529 align:start position:0% ok to live really critical stuff from 00:14:16.529 --> 00:14:18.260 align:start position:0% ok to live really critical stuff from your<00:14:16.740> smart<00:14:17.070> contract<00:14:17.460> in<00:14:17.640> the<00:14:17.790> hands<00:14:18.029> of<00:14:18.120> an 00:14:18.260 --> 00:14:18.270 align:start position:0% your smart contract in the hands of an 00:14:18.270 --> 00:14:20.810 align:start position:0% your smart contract in the hands of an owner<00:14:18.420> especially<00:14:19.080> if<00:14:19.500> they<00:14:19.710> if<00:14:20.040> the 00:14:20.810 --> 00:14:20.820 align:start position:0% owner especially if they if the 00:14:20.820 --> 00:14:22.850 align:start position:0% owner especially if they if the investors<00:14:21.270> or<00:14:21.540> users<00:14:22.110> of<00:14:22.230> the<00:14:22.320> contract<00:14:22.680> are 00:14:22.850 --> 00:14:22.860 align:start position:0% investors or users of the contract are 00:14:22.860 --> 00:14:24.500 align:start position:0% investors or users of the contract are already<00:14:23.160> trusting<00:14:23.640> the<00:14:23.760> owner<00:14:23.910> in<00:14:24.150> some<00:14:24.360> other 00:14:24.500 --> 00:14:24.510 align:start position:0% already trusting the owner in some other 00:14:24.510 --> 00:14:28.850 align:start position:0% already trusting the owner in some other way<00:14:24.720> like<00:14:24.960> giving<00:14:25.350> the<00:14:25.470> money<00:14:25.680> I<00:14:27.770> wanted<00:14:28.770> to 00:14:28.850 --> 00:14:28.860 align:start position:0% way like giving the money I wanted to 00:14:28.860 --> 00:14:33.050 align:start position:0% way like giving the money I wanted to say<00:14:29.550> that<00:14:30.200> so<00:14:31.200> I<00:14:31.530> want<00:14:32.010> I<00:14:32.250> want<00:14:32.730> to<00:14:32.820> end<00:14:32.970> with 00:14:33.050 --> 00:14:33.060 align:start position:0% say that so I want I want to end with 00:14:33.060 --> 00:14:35.240 align:start position:0% say that so I want I want to end with some<00:14:33.660> open<00:14:33.930> problems<00:14:34.080> that<00:14:34.470> we<00:14:34.589> see<00:14:35.040> in<00:14:35.130> the 00:14:35.240 --> 00:14:35.250 align:start position:0% some open problems that we see in the 00:14:35.250 --> 00:14:37.130 align:start position:0% some open problems that we see in the industry<00:14:35.310> and<00:14:35.790> some<00:14:36.180> ideas<00:14:36.510> were<00:14:36.690> working<00:14:37.020> on 00:14:37.130 --> 00:14:37.140 align:start position:0% industry and some ideas were working on 00:14:37.140 --> 00:14:40.340 align:start position:0% industry and some ideas were working on to<00:14:37.410> solve<00:14:37.620> them<00:14:37.770> I<00:14:38.720> briefly<00:14:39.720> touched<00:14:40.170> upon 00:14:40.340 --> 00:14:40.350 align:start position:0% to solve them I briefly touched upon 00:14:40.350 --> 00:14:42.340 align:start position:0% to solve them I briefly touched upon some<00:14:40.560> of<00:14:40.950> this<00:14:41.100> but<00:14:41.339> one<00:14:41.970> of<00:14:42.000> them<00:14:42.210> is 00:14:42.340 --> 00:14:42.350 align:start position:0% some of this but one of them is 00:14:42.350 --> 00:14:45.140 align:start position:0% some of this but one of them is upgradability<00:14:43.350> or<00:14:43.530> both<00:14:44.280> in<00:14:44.400> terms<00:14:44.640> of<00:14:44.820> how<00:14:45.089> to 00:14:45.140 --> 00:14:45.150 align:start position:0% upgradability or both in terms of how to 00:14:45.150 --> 00:14:47.420 align:start position:0% upgradability or both in terms of how to upgrade<00:14:45.510> a<00:14:45.930> smart<00:14:46.260> contract<00:14:46.410> once<00:14:46.920> it<00:14:47.250> has 00:14:47.420 --> 00:14:47.430 align:start position:0% upgrade a smart contract once it has 00:14:47.430 --> 00:14:50.420 align:start position:0% upgrade a smart contract once it has been<00:14:47.580> deployed<00:14:47.880> to<00:14:48.000> the<00:14:48.210> network<00:14:48.830> for<00:14:49.830> like 00:14:50.420 --> 00:14:50.430 align:start position:0% been deployed to the network for like 00:14:50.430 --> 00:14:52.900 align:start position:0% been deployed to the network for like bug<00:14:50.670> fixing<00:14:51.089> or<00:14:51.330> adding<00:14:51.690> extra<00:14:52.050> features 00:14:52.900 --> 00:14:52.910 align:start position:0% bug fixing or adding extra features 00:14:52.910 --> 00:14:55.579 align:start position:0% bug fixing or adding extra features interoperability<00:14:53.910> it<00:14:54.690> there<00:14:54.960> is<00:14:55.050> contracts 00:14:55.579 --> 00:14:55.589 align:start position:0% interoperability it there is contracts 00:14:55.589 --> 00:14:59.210 align:start position:0% interoperability it there is contracts calling<00:14:56.030> them<00:14:57.030> each<00:14:57.450> other<00:14:57.720> the<00:14:58.380> gas<00:14:58.560> costs<00:14:59.070> of 00:14:59.210 --> 00:14:59.220 align:start position:0% calling them each other the gas costs of 00:14:59.220 --> 00:15:01.190 align:start position:0% calling them each other the gas costs of how<00:14:59.700> contracts<00:15:00.240> interact<00:15:00.630> within<00:15:00.839> each<00:15:01.020> other 00:15:01.190 --> 00:15:01.200 align:start position:0% how contracts interact within each other 00:15:01.200 --> 00:15:03.760 align:start position:0% how contracts interact within each other and<00:15:01.440> code<00:15:02.370> duplication<00:15:02.550> in<00:15:03.180> the<00:15:03.360> blockchain 00:15:03.760 --> 00:15:03.770 align:start position:0% and code duplication in the blockchain 00:15:03.770 --> 00:15:08.240 align:start position:0% and code duplication in the blockchain so<00:15:04.770> we<00:15:05.250> recently<00:15:05.940> announced<00:15:06.330> our<00:15:07.110> sibling<00:15:07.770> OS 00:15:08.240 --> 00:15:08.250 align:start position:0% so we recently announced our sibling OS 00:15:08.250 --> 00:15:10.760 align:start position:0% so we recently announced our sibling OS project<00:15:08.700> which<00:15:09.360> tackles<00:15:09.720> these<00:15:10.500> four 00:15:10.760 --> 00:15:10.770 align:start position:0% project which tackles these four 00:15:10.770 --> 00:15:13.520 align:start position:0% project which tackles these four problems<00:15:10.950> and<00:15:11.940> I'm<00:15:12.030> gonna<00:15:12.209> tell<00:15:12.959> you<00:15:13.080> how<00:15:13.470> we 00:15:13.520 --> 00:15:13.530 align:start position:0% problems and I'm gonna tell you how we 00:15:13.530 --> 00:15:15.640 align:start position:0% problems and I'm gonna tell you how we do<00:15:13.740> that<00:15:13.860> how<00:15:14.250> we<00:15:14.310> plan<00:15:14.520> to<00:15:14.550> do<00:15:14.760> that 00:15:15.640 --> 00:15:15.650 align:start position:0% do that how we plan to do that 00:15:15.650 --> 00:15:18.530 align:start position:0% do that how we plan to do that so<00:15:16.650> for<00:15:16.860> code<00:15:17.070> duplication<00:15:17.300> basically<00:15:18.300> what 00:15:18.530 --> 00:15:18.540 align:start position:0% so for code duplication basically what 00:15:18.540 --> 00:15:20.150 align:start position:0% so for code duplication basically what we're<00:15:18.779> going<00:15:18.990> to<00:15:19.110> do<00:15:19.260> is<00:15:19.380> turning<00:15:19.770> open 00:15:20.150 --> 00:15:20.160 align:start position:0% we're going to do is turning open 00:15:20.160 --> 00:15:22.180 align:start position:0% we're going to do is turning open sapling<00:15:20.520> the<00:15:20.700> library<00:15:21.029> into<00:15:21.480> a<00:15:21.510> non<00:15:21.720> chained 00:15:22.180 --> 00:15:22.190 align:start position:0% sapling the library into a non chained 00:15:22.190 --> 00:15:25.010 align:start position:0% sapling the library into a non chained library<00:15:23.190> were<00:15:23.430> applications<00:15:24.420> kind<00:15:24.690> direct 00:15:25.010 --> 00:15:25.020 align:start position:0% library were applications kind direct 00:15:25.020 --> 00:15:27.800 align:start position:0% library were applications kind direct directly<00:15:25.470> connect<00:15:25.920> and<00:15:26.130> Link<00:15:26.370> contracts<00:15:27.120> to 00:15:27.800 --> 00:15:27.810 align:start position:0% directly connect and Link contracts to 00:15:27.810 --> 00:15:29.780 align:start position:0% directly connect and Link contracts to their<00:15:27.990> own<00:15:28.140> chain<00:15:28.380> version<00:15:28.800> to<00:15:29.310> reduce<00:15:29.610> the 00:15:29.780 --> 00:15:29.790 align:start position:0% their own chain version to reduce the 00:15:29.790 --> 00:15:31.520 align:start position:0% their own chain version to reduce the the<00:15:29.820> payload<00:15:30.480> that<00:15:30.660> needs<00:15:30.839> the<00:15:31.170> white<00:15:31.350> code 00:15:31.520 --> 00:15:31.530 align:start position:0% the payload that needs the white code 00:15:31.530 --> 00:15:33.350 align:start position:0% the payload that needs the white code that<00:15:31.680> needs<00:15:31.860> to<00:15:31.980> be<00:15:32.040> uploaded<00:15:32.640> to<00:15:32.670> contract<00:15:33.150> on 00:15:33.350 --> 00:15:33.360 align:start position:0% that needs to be uploaded to contract on 00:15:33.360 --> 00:15:35.510 align:start position:0% that needs to be uploaded to contract on chain<00:15:33.780> and<00:15:34.050> all<00:15:34.680> the<00:15:34.740> other 00:15:35.510 --> 00:15:35.520 align:start position:0% chain and all the other 00:15:35.520 --> 00:15:38.000 align:start position:0% chain and all the other that<00:15:36.000> are<00:15:36.180> reusing<00:15:36.750> open<00:15:37.050> civilian<00:15:37.470> standard 00:15:38.000 --> 00:15:38.010 align:start position:0% that are reusing open civilian standard 00:15:38.010 --> 00:15:40.280 align:start position:0% that are reusing open civilian standard token<00:15:38.610> implementation<00:15:39.210> they<00:15:39.750> can<00:15:39.900> share<00:15:40.140> the 00:15:40.280 --> 00:15:40.290 align:start position:0% token implementation they can share the 00:15:40.290 --> 00:15:42.050 align:start position:0% token implementation they can share the same<00:15:40.470> code<00:15:40.740> on<00:15:40.950> chain<00:15:41.310> and<00:15:41.520> release<00:15:41.760> the<00:15:41.910> gas 00:15:42.050 --> 00:15:42.060 align:start position:0% same code on chain and release the gas 00:15:42.060 --> 00:15:44.770 align:start position:0% same code on chain and release the gas costs<00:15:42.480> of<00:15:42.630> deployment<00:15:43.440> and<00:15:43.800> reduce<00:15:44.490> the 00:15:44.770 --> 00:15:44.780 align:start position:0% costs of deployment and reduce the 00:15:44.780 --> 00:15:49.220 align:start position:0% costs of deployment and reduce the amount<00:15:45.780> of<00:15:45.870> storage<00:15:46.140> needed<00:15:47.270> and<00:15:48.270> this<00:15:48.840> kernel 00:15:49.220 --> 00:15:49.230 align:start position:0% amount of storage needed and this kernel 00:15:49.230 --> 00:15:51.110 align:start position:0% amount of storage needed and this kernel will<00:15:49.410> also<00:15:49.710> have<00:15:50.160> an<00:15:50.400> upgrade<00:15:51.000> ability 00:15:51.110 --> 00:15:51.120 align:start position:0% will also have an upgrade ability 00:15:51.120 --> 00:15:55.460 align:start position:0% will also have an upgrade ability mechanism<00:15:51.900> a<00:15:52.490> via<00:15:53.490> the<00:15:54.360> delegate<00:15:55.050> proxy 00:15:55.460 --> 00:15:55.470 align:start position:0% mechanism a via the delegate proxy 00:15:55.470 --> 00:15:59.120 align:start position:0% mechanism a via the delegate proxy pattern<00:15:56.030> so<00:15:57.030> that<00:15:57.180> we<00:15:57.300> can<00:15:57.510> do<00:15:57.690> upgrades<00:15:58.590> to 00:15:59.120 --> 00:15:59.130 align:start position:0% pattern so that we can do upgrades to 00:15:59.130 --> 00:16:01.580 align:start position:0% pattern so that we can do upgrades to this<00:15:59.280> kernel<00:15:59.850> of<00:15:59.940> really<00:16:00.390> core<00:16:00.840> and<00:16:01.170> important 00:16:01.580 --> 00:16:01.590 align:start position:0% this kernel of really core and important 00:16:01.590 --> 00:16:05.090 align:start position:0% this kernel of really core and important modules<00:16:02.270> from<00:16:03.270> the<00:16:03.360> ecosystem<00:16:03.660> so<00:16:04.470> we<00:16:04.680> find<00:16:04.920> a 00:16:05.090 --> 00:16:05.100 align:start position:0% modules from the ecosystem so we find a 00:16:05.100 --> 00:16:07.520 align:start position:0% modules from the ecosystem so we find a bug<00:16:05.250> or<00:16:05.550> or<00:16:05.880> we<00:16:06.180> need<00:16:06.300> to<00:16:06.450> improve<00:16:06.900> some<00:16:07.320> of<00:16:07.350> the 00:16:07.520 --> 00:16:07.530 align:start position:0% bug or or we need to improve some of the 00:16:07.530 --> 00:16:11.150 align:start position:0% bug or or we need to improve some of the code<00:16:07.740> from<00:16:08.190> from<00:16:08.850> those<00:16:09.060> core<00:16:09.900> libraries<00:16:10.350> we 00:16:11.150 --> 00:16:11.160 align:start position:0% code from from those core libraries we 00:16:11.160 --> 00:16:14.450 align:start position:0% code from from those core libraries we can<00:16:11.310> do<00:16:11.460> so<00:16:11.670> and<00:16:11.990> possibly<00:16:12.990> fix<00:16:13.230> a<00:16:13.470> production 00:16:14.450 --> 00:16:14.460 align:start position:0% can do so and possibly fix a production 00:16:14.460 --> 00:16:17.150 align:start position:0% can do so and possibly fix a production code<00:16:14.670> from<00:16:14.940> some<00:16:15.120> contracts<00:16:15.660> and<00:16:15.920> of<00:16:16.920> course 00:16:17.150 --> 00:16:17.160 align:start position:0% code from some contracts and of course 00:16:17.160 --> 00:16:19.520 align:start position:0% code from some contracts and of course this<00:16:17.480> business<00:16:18.480> a<00:16:18.600> governance<00:16:19.020> mechanism 00:16:19.520 --> 00:16:19.530 align:start position:0% this business a governance mechanism 00:16:19.530 --> 00:16:21.800 align:start position:0% this business a governance mechanism because<00:16:19.830> a<00:16:20.270> nobody<00:16:21.270> would<00:16:21.420> use<00:16:21.450> some 00:16:21.800 --> 00:16:21.810 align:start position:0% because a nobody would use some 00:16:21.810 --> 00:16:23.600 align:start position:0% because a nobody would use some something<00:16:22.350> that<00:16:22.470> is<00:16:22.620> in<00:16:22.860> the<00:16:23.040> hands<00:16:23.310> of<00:16:23.400> a<00:16:23.580> few 00:16:23.600 --> 00:16:23.610 align:start position:0% something that is in the hands of a few 00:16:23.610 --> 00:16:29.800 align:start position:0% something that is in the hands of a few developers<00:16:24.240> which<00:16:24.810> upgrades<00:16:25.250> are<00:16:27.860> approved 00:16:29.800 --> 00:16:29.810 align:start position:0% developers which upgrades are approved 00:16:29.810 --> 00:16:32.270 align:start position:0% developers which upgrades are approved and<00:16:30.810> by<00:16:30.960> the<00:16:31.020> way<00:16:31.170> we<00:16:31.350> we<00:16:31.740> did<00:16:31.920> this<00:16:32.040> the 00:16:32.270 --> 00:16:32.280 align:start position:0% and by the way we we did this the 00:16:32.280 --> 00:16:34.880 align:start position:0% and by the way we we did this the technical<00:16:32.700> research<00:16:33.030> for<00:16:33.330> this<00:16:33.510> we<00:16:34.080> did<00:16:34.260> with 00:16:34.880 --> 00:16:34.890 align:start position:0% technical research for this we did with 00:16:34.890 --> 00:16:36.710 align:start position:0% technical research for this we did with the<00:16:35.100> Oregon<00:16:35.520> guys<00:16:35.700> and<00:16:36.000> they've<00:16:36.210> been<00:16:36.570> using 00:16:36.710 --> 00:16:36.720 align:start position:0% the Oregon guys and they've been using 00:16:36.720 --> 00:16:39.440 align:start position:0% the Oregon guys and they've been using the<00:16:36.960> same<00:16:37.110> idea<00:16:37.410> on<00:16:37.680> Eragon<00:16:38.430> OS<00:16:38.670> so<00:16:38.970> you<00:16:39.030> might 00:16:39.440 --> 00:16:39.450 align:start position:0% the same idea on Eragon OS so you might 00:16:39.450 --> 00:16:43.580 align:start position:0% the same idea on Eragon OS so you might want<00:16:39.630> to<00:16:39.660> check<00:16:39.900> that<00:16:39.930> out<00:16:40.170> too<00:16:41.510> and<00:16:42.510> to<00:16:43.260> two 00:16:43.580 --> 00:16:43.590 align:start position:0% want to check that out too and to two 00:16:43.590 --> 00:16:45.500 align:start position:0% want to check that out too and to two other<00:16:43.740> components<00:16:44.280> of<00:16:44.760> the<00:16:44.820> OS<00:16:45.240> are<00:16:45.390> the 00:16:45.500 --> 00:16:45.510 align:start position:0% other components of the OS are the 00:16:45.510 --> 00:16:47.930 align:start position:0% other components of the OS are the scheduler<00:16:45.960> and<00:16:46.140> the<00:16:46.230> marketplace<00:16:46.560> so<00:16:46.980> the 00:16:47.930 --> 00:16:47.940 align:start position:0% scheduler and the marketplace so the 00:16:47.940 --> 00:16:50.420 align:start position:0% scheduler and the marketplace so the scheduler<00:16:48.300> solves<00:16:48.690> the<00:16:48.900> gas<00:16:49.380> the<00:16:49.830> gas<00:16:49.860> problem 00:16:50.420 --> 00:16:50.430 align:start position:0% scheduler solves the gas the gas problem 00:16:50.430 --> 00:16:52.280 align:start position:0% scheduler solves the gas the gas problem of<00:16:50.610> smart<00:16:51.120> contract<00:16:51.390> interaction<00:16:51.930> and<00:16:52.170> it 00:16:52.280 --> 00:16:52.290 align:start position:0% of smart contract interaction and it 00:16:52.290 --> 00:16:54.350 align:start position:0% of smart contract interaction and it comes<00:16:52.500> from<00:16:52.740> the<00:16:52.950> idea<00:16:53.040> that<00:16:53.400> when<00:16:54.180> two 00:16:54.350 --> 00:16:54.360 align:start position:0% comes from the idea that when two 00:16:54.360 --> 00:16:56.540 align:start position:0% comes from the idea that when two contracts<00:16:54.900> interact<00:16:55.500> if<00:16:56.130> you<00:16:56.250> think<00:16:56.460> about 00:16:56.540 --> 00:16:56.550 align:start position:0% contracts interact if you think about 00:16:56.550 --> 00:16:58.970 align:start position:0% contracts interact if you think about who<00:16:56.940> pays<00:16:57.150> for<00:16:57.210> the<00:16:57.510> gas<00:16:57.660> price<00:16:57.960> for<00:16:58.560> those 00:16:58.970 --> 00:16:58.980 align:start position:0% who pays for the gas price for those 00:16:58.980 --> 00:17:00.800 align:start position:0% who pays for the gas price for those interactions<00:16:59.370> for<00:16:59.670> example<00:17:00.060> a<00:17:00.270> typical 00:17:00.800 --> 00:17:00.810 align:start position:0% interactions for example a typical 00:17:00.810 --> 00:17:02.450 align:start position:0% interactions for example a typical example<00:17:00.900> nowadays<00:17:01.320> is<00:17:01.770> a<00:17:01.920> multi-state 00:17:02.450 --> 00:17:02.460 align:start position:0% example nowadays is a multi-state 00:17:02.460 --> 00:17:04.820 align:start position:0% example nowadays is a multi-state contract<00:17:02.940> controlling<00:17:03.540> a<00:17:03.810> crowd<00:17:04.589> sale 00:17:04.820 --> 00:17:04.830 align:start position:0% contract controlling a crowd sale 00:17:04.830 --> 00:17:06.230 align:start position:0% contract controlling a crowd sale contract<00:17:05.040> some<00:17:05.339> privilege<00:17:05.670> function<00:17:06.089> for 00:17:06.230 --> 00:17:06.240 align:start position:0% contract some privilege function for 00:17:06.240 --> 00:17:10.370 align:start position:0% contract some privilege function for example<00:17:07.760> finalizing<00:17:08.760> the<00:17:08.850> crowd<00:17:09.030> sale<00:17:09.260> if<00:17:10.260> you 00:17:10.370 --> 00:17:10.380 align:start position:0% example finalizing the crowd sale if you 00:17:10.380 --> 00:17:12.050 align:start position:0% example finalizing the crowd sale if you think<00:17:10.560> about<00:17:10.650> it<00:17:10.860> the<00:17:10.980> first<00:17:11.190> let's<00:17:11.880> say<00:17:12.000> you 00:17:12.050 --> 00:17:12.060 align:start position:0% think about it the first let's say you 00:17:12.060 --> 00:17:14.180 align:start position:0% think about it the first let's say you have<00:17:12.300> three<00:17:12.420> of<00:17:12.600> five<00:17:12.780> volt<00:17:13.020> EC<00:17:13.260> the<00:17:13.560> first 00:17:14.180 --> 00:17:14.190 align:start position:0% have three of five volt EC the first 00:17:14.190 --> 00:17:16.460 align:start position:0% have three of five volt EC the first owner<00:17:14.430> proposes<00:17:15.120> to<00:17:15.810> make<00:17:15.959> the<00:17:16.080> call<00:17:16.290> the 00:17:16.460 --> 00:17:16.470 align:start position:0% owner proposes to make the call the 00:17:16.470 --> 00:17:18.350 align:start position:0% owner proposes to make the call the second<00:17:16.740> one<00:17:16.890> signs<00:17:17.250> it<00:17:17.400> off<00:17:17.520> and<00:17:17.940> when<00:17:18.240> the 00:17:18.350 --> 00:17:18.360 align:start position:0% second one signs it off and when the 00:17:18.360 --> 00:17:20.120 align:start position:0% second one signs it off and when the third<00:17:18.570> one<00:17:18.600> signs<00:17:19.020> it<00:17:19.170> off<00:17:19.320> the<00:17:19.890> actual 00:17:20.120 --> 00:17:20.130 align:start position:0% third one signs it off the actual 00:17:20.130 --> 00:17:21.560 align:start position:0% third one signs it off the actual operation<00:17:20.550> is<00:17:20.670> executed 00:17:21.560 --> 00:17:21.570 align:start position:0% operation is executed 00:17:21.570 --> 00:17:23.420 align:start position:0% operation is executed another<00:17:21.839> gas<00:17:22.110> cost<00:17:22.410> of<00:17:22.589> executed<00:17:23.070> that<00:17:23.220> is 00:17:23.420 --> 00:17:23.430 align:start position:0% another gas cost of executed that is 00:17:23.430 --> 00:17:27.110 align:start position:0% another gas cost of executed that is paid<00:17:23.790> by<00:17:24.030> the<00:17:24.060> third<00:17:24.660> or<00:17:25.170> the<00:17:25.230> last<00:17:25.850> owner<00:17:26.850> of 00:17:27.110 --> 00:17:27.120 align:start position:0% paid by the third or the last owner of 00:17:27.120 --> 00:17:31.040 align:start position:0% paid by the third or the last owner of the<00:17:27.209> multi<00:17:27.450> C<00:17:28.130> so<00:17:29.130> with<00:17:29.280> the<00:17:29.370> scheduler<00:17:30.050> we're 00:17:31.040 --> 00:17:31.050 align:start position:0% the multi C so with the scheduler we're 00:17:31.050 --> 00:17:33.560 align:start position:0% the multi C so with the scheduler we're building<00:17:31.320> tools<00:17:31.530> to<00:17:31.790> enable<00:17:32.790> contracts<00:17:33.450> to 00:17:33.560 --> 00:17:33.570 align:start position:0% building tools to enable contracts to 00:17:33.570 --> 00:17:36.020 align:start position:0% building tools to enable contracts to request<00:17:33.990> a<00:17:34.200> synchronous<00:17:34.800> operations<00:17:35.370> in<00:17:35.820> the 00:17:36.020 --> 00:17:36.030 align:start position:0% request a synchronous operations in the 00:17:36.030 --> 00:17:38.660 align:start position:0% request a synchronous operations in the future<00:17:36.300> so<00:17:36.510> a<00:17:36.690> multi<00:17:37.050> could<00:17:37.350> gather<00:17:38.310> all<00:17:38.550> the 00:17:38.660 --> 00:17:38.670 align:start position:0% future so a multi could gather all the 00:17:38.670 --> 00:17:40.490 align:start position:0% future so a multi could gather all the signatures<00:17:38.970> and<00:17:39.150> then<00:17:39.450> request<00:17:39.840> someone<00:17:40.200> else 00:17:40.490 --> 00:17:40.500 align:start position:0% signatures and then request someone else 00:17:40.500 --> 00:17:42.320 align:start position:0% signatures and then request someone else to<00:17:40.710> do<00:17:40.980> the<00:17:41.130> actual<00:17:41.250> execution<00:17:42.120> of<00:17:42.210> the 00:17:42.320 --> 00:17:42.330 align:start position:0% to do the actual execution of the 00:17:42.330 --> 00:17:44.360 align:start position:0% to do the actual execution of the operation<00:17:42.810> so<00:17:43.380> with<00:17:43.590> a<00:17:43.620> couple<00:17:43.980> who<00:17:44.130> pays<00:17:44.340> for 00:17:44.360 --> 00:17:44.370 align:start position:0% operation so with a couple who pays for 00:17:44.370 --> 00:17:46.700 align:start position:0% operation so with a couple who pays for gas<00:17:44.730> and<00:17:45.030> who<00:17:45.330> is<00:17:45.420> actually<00:17:45.620> approving<00:17:46.620> the 00:17:46.700 --> 00:17:46.710 align:start position:0% gas and who is actually approving the 00:17:46.710 --> 00:17:50.070 align:start position:0% gas and who is actually approving the calls 00:17:50.070 --> 00:17:50.080 align:start position:0% 00:17:50.080 --> 00:17:51.870 align:start position:0% and<00:17:50.350> this<00:17:50.559> same<00:17:50.890> mechanism<00:17:51.040> also<00:17:51.490> allows<00:17:51.850> for 00:17:51.870 --> 00:17:51.880 align:start position:0% and this same mechanism also allows for 00:17:51.880 --> 00:17:54.780 align:start position:0% and this same mechanism also allows for a<00:17:52.470> synchronous<00:17:53.470> programming<00:17:53.620> in<00:17:54.160> general<00:17:54.610> not 00:17:54.780 --> 00:17:54.790 align:start position:0% a synchronous programming in general not 00:17:54.790 --> 00:17:58.560 align:start position:0% a synchronous programming in general not just<00:17:55.110> this<00:17:56.220> this<00:17:57.220> thing<00:17:57.490> this<00:17:57.820> thing<00:17:57.880> is<00:17:58.330> gas 00:17:58.560 --> 00:17:58.570 align:start position:0% just this this thing this thing is gas 00:17:58.570 --> 00:18:03.000 align:start position:0% just this this thing this thing is gas but<00:17:59.290> enables<00:17:59.980> a<00:18:00.990> smart<00:18:01.990> contracts<00:18:02.350> to<00:18:02.530> to 00:18:03.000 --> 00:18:03.010 align:start position:0% but enables a smart contracts to to 00:18:03.010 --> 00:18:06.810 align:start position:0% but enables a smart contracts to to request<00:18:03.510> operations<00:18:04.510> in<00:18:04.780> the<00:18:04.929> future<00:18:05.550> and<00:18:06.550> for 00:18:06.810 --> 00:18:06.820 align:start position:0% request operations in the future and for 00:18:06.820 --> 00:18:09.299 align:start position:0% request operations in the future and for the<00:18:06.880> marketplace<00:18:07.270> we<00:18:07.720> are<00:18:08.260> standardizing<00:18:09.220> the 00:18:09.299 --> 00:18:09.309 align:start position:0% the marketplace we are standardizing the 00:18:09.309 --> 00:18:11.190 align:start position:0% the marketplace we are standardizing the way<00:18:09.429> contracts<00:18:10.150> interact<00:18:10.690> with<00:18:10.929> each<00:18:11.080> other 00:18:11.190 --> 00:18:11.200 align:start position:0% way contracts interact with each other 00:18:11.200 --> 00:18:14.490 align:start position:0% way contracts interact with each other so<00:18:12.059> we<00:18:13.059> think<00:18:13.240> that<00:18:13.360> there's<00:18:13.870> a<00:18:14.080> bigger 00:18:14.490 --> 00:18:14.500 align:start position:0% so we think that there's a bigger 00:18:14.500 --> 00:18:16.650 align:start position:0% so we think that there's a bigger potential<00:18:15.040> for<00:18:15.280> smart<00:18:15.760> contracts<00:18:16.179> when<00:18:16.540> they 00:18:16.650 --> 00:18:16.660 align:start position:0% potential for smart contracts when they 00:18:16.660 --> 00:18:18.930 align:start position:0% potential for smart contracts when they start<00:18:16.990> interacting<00:18:17.740> more<00:18:18.160> and<00:18:18.309> we<00:18:18.400> see<00:18:18.610> an 00:18:18.930 --> 00:18:18.940 align:start position:0% start interacting more and we see an 00:18:18.940 --> 00:18:22.169 align:start position:0% start interacting more and we see an ecosystem<00:18:19.270> of<00:18:20.010> contracts<00:18:21.010> interacting<00:18:21.700> and 00:18:22.169 --> 00:18:22.179 align:start position:0% ecosystem of contracts interacting and 00:18:22.179 --> 00:18:24.330 align:start position:0% ecosystem of contracts interacting and we're<00:18:22.330> standardizing<00:18:22.630> the<00:18:23.110> way<00:18:23.260> a<00:18:23.340> contract 00:18:24.330 --> 00:18:24.340 align:start position:0% we're standardizing the way a contract 00:18:24.340 --> 00:18:26.840 align:start position:0% we're standardizing the way a contract can<00:18:24.429> expose<00:18:24.820> its<00:18:25.179> services<00:18:25.720> in<00:18:26.020> terms<00:18:26.320> of<00:18:26.559> I 00:18:26.840 --> 00:18:26.850 align:start position:0% can expose its services in terms of I 00:18:26.850 --> 00:18:30.540 align:start position:0% can expose its services in terms of I this<00:18:27.850> contract<00:18:28.300> offer<00:18:28.480> this<00:18:28.840> API<00:18:29.590> call<00:18:29.890> for<00:18:30.280> a 00:18:30.540 --> 00:18:30.550 align:start position:0% this contract offer this API call for a 00:18:30.550 --> 00:18:32.760 align:start position:0% this contract offer this API call for a monthly<00:18:31.000> payment<00:18:31.210> or<00:18:31.630> a<00:18:31.750> one-time<00:18:32.110> fee<00:18:32.530> and 00:18:32.760 --> 00:18:32.770 align:start position:0% monthly payment or a one-time fee and 00:18:32.770 --> 00:18:35.010 align:start position:0% monthly payment or a one-time fee and you<00:18:32.830> get<00:18:32.980> access<00:18:33.130> to<00:18:33.309> everything<00:18:33.670> or<00:18:34.000> a<00:18:34.780> per 00:18:35.010 --> 00:18:35.020 align:start position:0% you get access to everything or a per 00:18:35.020 --> 00:18:39.060 align:start position:0% you get access to everything or a per call<00:18:35.260> fee<00:18:36.450> and<00:18:37.450> finally<00:18:37.840> part<00:18:38.110> also<00:18:38.679> part<00:18:39.010> of 00:18:39.060 --> 00:18:39.070 align:start position:0% call fee and finally part also part of 00:18:39.070 --> 00:18:41.820 align:start position:0% call fee and finally part also part of sibling<00:18:39.550> OS<00:18:39.790> is<00:18:40.090> a<00:18:40.360> set<00:18:40.570> of<00:18:40.750> of<00:18:41.110> chain<00:18:41.559> tools 00:18:41.820 --> 00:18:41.830 align:start position:0% sibling OS is a set of of chain tools 00:18:41.830 --> 00:18:43.860 align:start position:0% sibling OS is a set of of chain tools which<00:18:42.130> we<00:18:42.309> call<00:18:42.490> the<00:18:42.670> smart<00:18:42.910> contract<00:18:43.059> SDK 00:18:43.860 --> 00:18:43.870 align:start position:0% which we call the smart contract SDK 00:18:43.870 --> 00:18:46.680 align:start position:0% which we call the smart contract SDK which<00:18:44.080> are<00:18:44.260> basically<00:18:44.740> CLI<00:18:45.309> tools<00:18:45.340> and<00:18:45.850> web 00:18:46.680 --> 00:18:46.690 align:start position:0% which are basically CLI tools and web 00:18:46.690 --> 00:18:50.100 align:start position:0% which are basically CLI tools and web applications<00:18:47.500> to<00:18:47.740> manage<00:18:48.360> easy<00:18:49.360> more<00:18:49.870> easily 00:18:50.100 --> 00:18:50.110 align:start position:0% applications to manage easy more easily 00:18:50.110 --> 00:18:55.110 align:start position:0% applications to manage easy more easily your<00:18:50.380> contracts<00:18:52.260> so<00:18:53.260> you<00:18:53.320> can<00:18:53.530> know<00:18:54.160> know<00:18:54.940> more 00:18:55.110 --> 00:18:55.120 align:start position:0% your contracts so you can know know more 00:18:55.120 --> 00:18:57.000 align:start position:0% your contracts so you can know know more about<00:18:55.240> this<00:18:55.510> it's<00:18:55.809> a<00:18:56.020> completely<00:18:56.470> open<00:18:56.590> source 00:18:57.000 --> 00:18:57.010 align:start position:0% about this it's a completely open source 00:18:57.010 --> 00:18:58.770 align:start position:0% about this it's a completely open source project<00:18:57.520> we<00:18:57.790> encourage<00:18:58.390> everyone<00:18:58.660> to 00:18:58.770 --> 00:18:58.780 align:start position:0% project we encourage everyone to 00:18:58.780 --> 00:19:01.880 align:start position:0% project we encourage everyone to participate<00:18:59.020> in<00:18:59.679> by<00:19:00.309> giving<00:19:00.460> ideas<00:19:01.210> and<00:19:01.510> cold 00:19:01.880 --> 00:19:01.890 align:start position:0% participate in by giving ideas and cold 00:19:01.890 --> 00:19:04.620 align:start position:0% participate in by giving ideas and cold and<00:19:02.890> we<00:19:03.580> can<00:19:03.730> talk<00:19:03.880> about<00:19:04.000> more<00:19:04.300> about<00:19:04.540> this 00:19:04.620 --> 00:19:04.630 align:start position:0% and we can talk about more about this 00:19:04.630 --> 00:19:05.070 align:start position:0% and we can talk about more about this later 00:19:05.070 --> 00:19:05.080 align:start position:0% later 00:19:05.080 --> 00:19:07.950 align:start position:0% later finally<00:19:05.950> we're<00:19:06.910> not<00:19:07.059> yesterday<00:19:07.480> we<00:19:07.660> launched 00:19:07.950 --> 00:19:07.960 align:start position:0% finally we're not yesterday we launched 00:19:07.960 --> 00:19:10.440 align:start position:0% finally we're not yesterday we launched solidity<00:19:08.860> culturally<00:19:09.640> flag<00:19:09.850> contest 00:19:10.440 --> 00:19:10.450 align:start position:0% solidity culturally flag contest 00:19:10.450 --> 00:19:13.740 align:start position:0% solidity culturally flag contest we're<00:19:10.660> giving<00:19:10.900> away<00:19:11.250> 10k<00:19:12.250> in<00:19:12.610> prices<00:19:13.150> it's<00:19:13.510> a 00:19:13.740 --> 00:19:13.750 align:start position:0% we're giving away 10k in prices it's a 00:19:13.750 --> 00:19:16.320 align:start position:0% we're giving away 10k in prices it's a hacking<00:19:14.320> contest<00:19:14.740> like<00:19:15.100> there's<00:19:15.880> a<00:19:15.940> couple<00:19:16.210> of 00:19:16.320 --> 00:19:16.330 align:start position:0% hacking contest like there's a couple of 00:19:16.330 --> 00:19:18.030 align:start position:0% hacking contest like there's a couple of contracts<00:19:16.720> you<00:19:16.840> need<00:19:16.960> to<00:19:17.080> hack<00:19:17.260> to<00:19:17.500> advance 00:19:18.030 --> 00:19:18.040 align:start position:0% contracts you need to hack to advance 00:19:18.040 --> 00:19:19.560 align:start position:0% contracts you need to hack to advance the<00:19:18.220> next<00:19:18.309> level<00:19:18.760> so<00:19:18.940> if<00:19:19.090> you<00:19:19.179> want<00:19:19.330> to<00:19:19.420> check 00:19:19.560 --> 00:19:19.570 align:start position:0% the next level so if you want to check 00:19:19.570 --> 00:19:24.419 align:start position:0% the next level so if you want to check it<00:19:19.690> out<00:19:19.780> and<00:19:20.710> it's<00:19:21.220> it's<00:19:21.760> fun<00:19:22.860> and<00:19:23.860> that<00:19:24.190> is<00:19:24.280> all 00:19:24.419 --> 00:19:24.429 align:start position:0% it out and it's it's fun and that is all 00:19:24.429 --> 00:19:25.820 align:start position:0% it out and it's it's fun and that is all thank<00:19:24.790> you<00:19:24.820> very<00:19:25.000> much 00:19:25.820 --> 00:19:25.830 align:start position:0% thank you very much 00:19:25.830 --> 00:19:32.420 align:start position:0% thank you very much [Applause] 00:19:32.420 --> 00:19:32.430 align:start position:0% [Applause] 00:19:32.430 --> 00:19:40.009 align:start position:0% [Applause] [Music]