WEBVTT Kind: captions Language: en 00:00:00.060 --> 00:00:03.230 align:start position:0% so<00:00:00.480> welcome<00:00:01.469> everybody<00:00:02.070> to<00:00:02.490> this<00:00:02.700> session 00:00:03.230 --> 00:00:03.240 align:start position:0% so welcome everybody to this session 00:00:03.240 --> 00:00:07.070 align:start position:0% so welcome everybody to this session which<00:00:04.170> is<00:00:04.650> called<00:00:05.609> live<00:00:06.000> hacking<00:00:06.660> smart 00:00:07.070 --> 00:00:07.080 align:start position:0% which is called live hacking smart 00:00:07.080 --> 00:00:14.060 align:start position:0% which is called live hacking smart contracts<00:00:10.849> we're<00:00:11.849> not<00:00:12.030> actually<00:00:12.240> going<00:00:12.690> to<00:00:13.070> do 00:00:14.060 --> 00:00:14.070 align:start position:0% contracts we're not actually going to do 00:00:14.070 --> 00:00:17.720 align:start position:0% contracts we're not actually going to do like<00:00:14.400> depth<00:00:15.000> con<00:00:15.570> style<00:00:15.960> hacking<00:00:16.800> into<00:00:17.039> live 00:00:17.720 --> 00:00:17.730 align:start position:0% like depth con style hacking into live 00:00:17.730 --> 00:00:23.480 align:start position:0% like depth con style hacking into live systems<00:00:20.630> kind<00:00:21.630> of<00:00:21.750> interactive<00:00:22.470> session<00:00:22.920> with 00:00:23.480 --> 00:00:23.490 align:start position:0% systems kind of interactive session with 00:00:23.490 --> 00:00:27.529 align:start position:0% systems kind of interactive session with the<00:00:23.640> audience<00:00:24.470> where<00:00:25.470> we<00:00:25.710> discuss<00:00:26.539> security 00:00:27.529 --> 00:00:27.539 align:start position:0% the audience where we discuss security 00:00:27.539 --> 00:00:29.330 align:start position:0% the audience where we discuss security that's<00:00:28.019> one<00:00:28.199> thing<00:00:28.410> discuss<00:00:28.769> it<00:00:28.949> from<00:00:29.130> like<00:00:29.310> a 00:00:29.330 --> 00:00:29.340 align:start position:0% that's one thing discuss it from like a 00:00:29.340 --> 00:00:33.319 align:start position:0% that's one thing discuss it from like a high-level<00:00:30.029> perspective<00:00:30.390> and<00:00:32.329> meanwhile 00:00:33.319 --> 00:00:33.329 align:start position:0% high-level perspective and meanwhile 00:00:33.329 --> 00:00:36.799 align:start position:0% high-level perspective and meanwhile also<00:00:33.930> trying<00:00:34.230> to<00:00:34.500> actually<00:00:34.980> find<00:00:35.550> bugs<00:00:35.940> in<00:00:36.480> the 00:00:36.799 --> 00:00:36.809 align:start position:0% also trying to actually find bugs in the 00:00:36.809 --> 00:00:40.240 align:start position:0% also trying to actually find bugs in the nitty<00:00:36.989> gritty<00:00:37.320> details<00:00:37.350> of<00:00:38.250> the<00:00:38.489> contract 00:00:40.240 --> 00:00:40.250 align:start position:0% nitty gritty details of the contract 00:00:40.250 --> 00:00:44.119 align:start position:0% nitty gritty details of the contract there<00:00:41.250> will<00:00:41.430> be<00:00:41.460> technical<00:00:42.059> glitches<00:00:42.950> we<00:00:43.950> will 00:00:44.119 --> 00:00:44.129 align:start position:0% there will be technical glitches we will 00:00:44.129 --> 00:00:46.010 align:start position:0% there will be technical glitches we will have<00:00:44.430> to<00:00:44.640> switch<00:00:44.910> over<00:00:45.090> the<00:00:45.360> viewport<00:00:45.840> from 00:00:46.010 --> 00:00:46.020 align:start position:0% have to switch over the viewport from 00:00:46.020 --> 00:00:48.170 align:start position:0% have to switch over the viewport from different<00:00:46.379> laptops<00:00:46.620> and<00:00:47.280> stuff<00:00:47.520> and<00:00:47.820> hope<00:00:48.000> you 00:00:48.170 --> 00:00:48.180 align:start position:0% different laptops and stuff and hope you 00:00:48.180 --> 00:00:52.400 align:start position:0% different laptops and stuff and hope you have<00:00:48.510> some<00:00:49.309> patience<00:00:50.309> with<00:00:50.430> that<00:00:51.350> person<00:00:52.350> so 00:00:52.400 --> 00:00:52.410 align:start position:0% have some patience with that person so 00:00:52.410 --> 00:00:55.400 align:start position:0% have some patience with that person so I'm<00:00:52.590> marked<00:00:53.129> in<00:00:53.340> whole<00:00:53.579> Sanda<00:00:53.969> I<00:00:54.180> work<00:00:54.840> for<00:00:55.320> the 00:00:55.400 --> 00:00:55.410 align:start position:0% I'm marked in whole Sanda I work for the 00:00:55.410 --> 00:00:59.209 align:start position:0% I'm marked in whole Sanda I work for the etherion<00:00:55.770> foundation<00:00:57.109> with<00:00:58.109> security<00:00:58.649> at<00:00:59.070> the 00:00:59.209 --> 00:00:59.219 align:start position:0% etherion foundation with security at the 00:00:59.219 --> 00:01:01.599 align:start position:0% etherion foundation with security at the rim<00:00:59.340> security<00:00:59.820> and<00:01:00.120> also<00:01:00.629> kept<00:01:00.899> development 00:01:01.599 --> 00:01:01.609 align:start position:0% rim security and also kept development 00:01:01.609 --> 00:01:04.729 align:start position:0% rim security and also kept development with<00:01:02.609> me<00:01:02.820> we've<00:01:03.449> got<00:01:03.719> the<00:01:04.080> Matthew<00:01:04.470> differente 00:01:04.729 --> 00:01:04.739 align:start position:0% with me we've got the Matthew differente 00:01:04.739 --> 00:01:09.260 align:start position:0% with me we've got the Matthew differente here<00:01:05.390> founder<00:01:06.390> of<00:01:06.450> seeker<00:01:07.110> labs<00:01:07.380> and<00:01:08.270> smart 00:01:09.260 --> 00:01:09.270 align:start position:0% here founder of seeker labs and smart 00:01:09.270 --> 00:01:12.530 align:start position:0% here founder of seeker labs and smart contracts<00:01:09.840> auditing<00:01:10.470> and<00:01:10.970> yeah<00:01:11.970> creeper 00:01:12.530 --> 00:01:12.540 align:start position:0% contracts auditing and yeah creeper 00:01:12.540 --> 00:01:15.710 align:start position:0% contracts auditing and yeah creeper research<00:01:12.869> and<00:01:12.990> stuff<00:01:13.880> and<00:01:14.880> we<00:01:15.150> got<00:01:15.330> Richard 00:01:15.710 --> 00:01:15.720 align:start position:0% research and stuff and we got Richard 00:01:15.720 --> 00:01:20.990 align:start position:0% research and stuff and we got Richard Moore<00:01:17.150> authors<00:01:18.150> or<00:01:18.450> author<00:01:18.840> of<00:01:19.020> ethers<00:01:20.000> ojs 00:01:20.990 --> 00:01:21.000 align:start position:0% Moore authors or author of ethers ojs 00:01:21.000 --> 00:01:28.160 align:start position:0% Moore authors or author of ethers ojs and<00:01:21.479> also<00:01:22.380> I<00:01:22.710> know<00:01:23.159> does<00:01:23.790> random<00:01:24.479> stuff<00:01:25.610> and<00:01:27.170> we 00:01:28.160 --> 00:01:28.170 align:start position:0% and also I know does random stuff and we 00:01:28.170 --> 00:01:30.350 align:start position:0% and also I know does random stuff and we were<00:01:28.290> just<00:01:28.500> joined<00:01:28.770> by<00:01:29.250> the<00:01:29.880> awesome<00:01:30.210> Nick 00:01:30.350 --> 00:01:30.360 align:start position:0% were just joined by the awesome Nick 00:01:30.360 --> 00:01:40.640 align:start position:0% were just joined by the awesome Nick Johnson<00:01:31.520> came<00:01:32.520> right<00:01:32.820> from<00:01:32.850> a<00:01:33.560> DNS<00:01:34.560> AMA<00:01:39.079> so<00:01:40.079> the 00:01:40.640 --> 00:01:40.650 align:start position:0% Johnson came right from a DNS AMA so the 00:01:40.650 --> 00:01:45.109 align:start position:0% Johnson came right from a DNS AMA so the idea<00:01:41.340> is<00:01:42.000> that<00:01:42.509> we<00:01:43.439> take<00:01:44.430> a<00:01:44.490> piece<00:01:44.729> of<00:01:44.909> code 00:01:45.109 --> 00:01:45.119 align:start position:0% idea is that we take a piece of code 00:01:45.119 --> 00:01:47.840 align:start position:0% idea is that we take a piece of code which<00:01:45.479> someone<00:01:46.229> here<00:01:46.409> submits<00:01:46.829> and<00:01:47.729> we 00:01:47.840 --> 00:01:47.850 align:start position:0% which someone here submits and we 00:01:47.850 --> 00:01:50.539 align:start position:0% which someone here submits and we discuss<00:01:48.149> it<00:01:48.299> and<00:01:48.479> if<00:01:49.110> possible<00:01:49.560> we<00:01:50.130> will<00:01:50.430> be 00:01:50.539 --> 00:01:50.549 align:start position:0% discuss it and if possible we will be 00:01:50.549 --> 00:01:54.230 align:start position:0% discuss it and if possible we will be very<00:01:50.790> grateful<00:01:51.030> if<00:01:51.740> that<00:01:52.740> someone<00:01:53.399> is<00:01:53.579> willing 00:01:54.230 --> 00:01:54.240 align:start position:0% very grateful if that someone is willing 00:01:54.240 --> 00:01:57.350 align:start position:0% very grateful if that someone is willing to<00:01:54.420> come<00:01:54.689> up<00:01:54.810> on<00:01:54.990> stage<00:01:55.020> and<00:01:55.850> chat<00:01:56.850> with<00:01:57.030> us<00:01:57.119> for 00:01:57.350 --> 00:01:57.360 align:start position:0% to come up on stage and chat with us for 00:01:57.360 --> 00:02:02.359 align:start position:0% to come up on stage and chat with us for bids<00:01:57.509> and<00:01:58.200> talk<00:01:58.439> about<00:01:58.560> the<00:01:58.710> contract<00:02:01.159> and<00:02:02.159> as 00:02:02.359 --> 00:02:02.369 align:start position:0% bids and talk about the contract and as 00:02:02.369 --> 00:02:03.770 align:start position:0% bids and talk about the contract and as far<00:02:02.549> as<00:02:02.640> I<00:02:02.700> know<00:02:02.880> we've<00:02:03.090> received<00:02:03.540> one 00:02:03.770 --> 00:02:03.780 align:start position:0% far as I know we've received one 00:02:03.780 --> 00:02:09.469 align:start position:0% far as I know we've received one submission<00:02:04.530> so<00:02:04.799> far<00:02:05.040> over<00:02:05.369> Twitter<00:02:06.680> so<00:02:07.680> is<00:02:08.479> mr. 00:02:09.469 --> 00:02:09.479 align:start position:0% submission so far over Twitter so is mr. 00:02:09.479 --> 00:02:13.880 align:start position:0% submission so far over Twitter so is mr. Appleton<00:02:11.000> present<00:02:12.000> and<00:02:12.270> would<00:02:12.540> he<00:02:12.720> like<00:02:12.989> to 00:02:13.880 --> 00:02:13.890 align:start position:0% Appleton present and would he like to 00:02:13.890 --> 00:02:17.960 align:start position:0% Appleton present and would he like to join<00:02:14.610> us<00:02:14.790> in<00:02:16.130> the<00:02:17.130> room<00:02:17.310> I<00:02:17.490> guess<00:02:17.820> they're<00:02:17.940> not 00:02:17.960 --> 00:02:17.970 align:start position:0% join us in the room I guess they're not 00:02:17.970 --> 00:02:23.120 align:start position:0% join us in the room I guess they're not here<00:02:18.240> they're<00:02:18.960> not<00:02:19.140> there<00:02:21.860> that's<00:02:22.860> a<00:02:23.010> bit 00:02:23.120 --> 00:02:23.130 align:start position:0% here they're not there that's a bit 00:02:23.130 --> 00:02:24.740 align:start position:0% here they're not there that's a bit unfortunate<00:02:23.490> because<00:02:24.120> one<00:02:24.330> of<00:02:24.420> the<00:02:24.510> things 00:02:24.740 --> 00:02:24.750 align:start position:0% unfortunate because one of the things 00:02:24.750 --> 00:02:26.870 align:start position:0% unfortunate because one of the things like<00:02:25.500> from<00:02:25.740> a<00:02:25.800> security<00:02:26.070> perspective<00:02:26.340> that 00:02:26.870 --> 00:02:26.880 align:start position:0% like from a security perspective that 00:02:26.880 --> 00:02:29.240 align:start position:0% like from a security perspective that it's<00:02:27.120> good<00:02:27.300> to<00:02:27.450> do<00:02:27.630> is<00:02:28.020> get<00:02:28.260> a<00:02:28.290> general<00:02:29.100> high 00:02:29.240 --> 00:02:29.250 align:start position:0% it's good to do is get a general high 00:02:29.250 --> 00:02:31.730 align:start position:0% it's good to do is get a general high level<00:02:29.640> understanding<00:02:30.440> what<00:02:31.440> is<00:02:31.560> this 00:02:31.730 --> 00:02:31.740 align:start position:0% level understanding what is this 00:02:31.740 --> 00:02:37.250 align:start position:0% level understanding what is this contract<00:02:32.370> do<00:02:32.580> and<00:02:34.190> what<00:02:35.190> are<00:02:35.280> the<00:02:35.340> assets<00:02:36.260> so 00:02:37.250 --> 00:02:37.260 align:start position:0% contract do and what are the assets so 00:02:37.260 --> 00:02:40.400 align:start position:0% contract do and what are the assets so we<00:02:37.410> kind<00:02:37.620> of<00:02:37.680> have<00:02:37.860> a<00:02:37.890> bounds<00:02:38.400> on<00:02:39.080> what<00:02:40.080> can<00:02:40.350> be 00:02:40.400 --> 00:02:40.410 align:start position:0% we kind of have a bounds on what can be 00:02:40.410 --> 00:02:43.370 align:start position:0% we kind of have a bounds on what can be lost<00:02:40.830> and<00:02:41.690> what<00:02:42.690> would<00:02:42.900> be<00:02:42.990> like<00:02:43.170> the<00:02:43.350> worst 00:02:43.370 --> 00:02:43.380 align:start position:0% lost and what would be like the worst 00:02:43.380 --> 00:02:47.630 align:start position:0% lost and what would be like the worst case<00:02:43.950> to<00:02:44.220> happen<00:02:44.580> and<00:02:45.650> get<00:02:46.650> an<00:02:46.740> idea<00:02:46.950> on<00:02:47.250> what 00:02:47.630 --> 00:02:47.640 align:start position:0% case to happen and get an idea on what 00:02:47.640 --> 00:02:51.380 align:start position:0% case to happen and get an idea on what to<00:02:47.670> look<00:02:47.790> out<00:02:48.060> for<00:02:48.360> him<00:02:50.090> since<00:02:51.090> this 00:02:51.380 --> 00:02:51.390 align:start position:0% to look out for him since this 00:02:51.390 --> 00:02:53.120 align:start position:0% to look out for him since this particular<00:02:52.020> contract<00:02:52.620> was<00:02:52.740> submitted 00:02:53.120 --> 00:02:53.130 align:start position:0% particular contract was submitted 00:02:53.130 --> 00:02:56.090 align:start position:0% particular contract was submitted yesterday<00:02:53.340> I<00:02:53.880> think<00:02:54.810> all<00:02:54.990> four<00:02:55.770> of<00:02:55.830> us<00:02:55.950> have 00:02:56.090 --> 00:02:56.100 align:start position:0% yesterday I think all four of us have 00:02:56.100 --> 00:03:01.280 align:start position:0% yesterday I think all four of us have probably<00:02:56.340> taken<00:02:56.880> at<00:02:57.120> least<00:02:57.180> a<00:02:57.450> peek<00:02:57.720> on<00:02:57.990> it<00:03:00.290> is 00:03:01.280 --> 00:03:01.290 align:start position:0% probably taken at least a peek on it is 00:03:01.290 --> 00:03:04.370 align:start position:0% probably taken at least a peek on it is that<00:03:01.470> one<00:03:01.650> of<00:03:01.770> you<00:03:01.860> guys<00:03:02.040> wanna<00:03:03.050> has<00:03:04.050> seen 00:03:04.370 --> 00:03:04.380 align:start position:0% that one of you guys wanna has seen 00:03:04.380 --> 00:03:05.870 align:start position:0% that one of you guys wanna has seen something<00:03:04.740> interesting<00:03:05.130> sure<00:03:05.250> to<00:03:05.370> go<00:03:05.490> from 00:03:05.870 --> 00:03:05.880 align:start position:0% something interesting sure to go from 00:03:05.880 --> 00:03:10.930 align:start position:0% something interesting sure to go from top<00:03:06.060> to<00:03:06.090> bottom<00:03:06.270> or<00:03:09.080> say<00:03:10.080> what<00:03:10.260> we<00:03:10.410> what<00:03:10.710> we 00:03:10.930 --> 00:03:10.940 align:start position:0% top to bottom or say what we what we 00:03:10.940 --> 00:03:15.020 align:start position:0% top to bottom or say what we what we think<00:03:11.940> about<00:03:12.180> this<00:03:13.580> so<00:03:14.580> it's<00:03:14.730> a<00:03:14.790> token 00:03:15.020 --> 00:03:15.030 align:start position:0% think about this so it's a token 00:03:15.030 --> 00:03:21.050 align:start position:0% think about this so it's a token contract<00:03:18.020> which<00:03:19.020> to<00:03:20.010> most<00:03:20.190> appearances<00:03:20.550> is 00:03:21.050 --> 00:03:21.060 align:start position:0% contract which to most appearances is 00:03:21.060 --> 00:03:29.449 align:start position:0% contract which to most appearances is quite<00:03:21.690> normal<00:03:22.250> it<00:03:23.250> has<00:03:23.970> an<00:03:24.900> owner<00:03:28.340> there<00:03:29.340> is<00:03:29.370> a 00:03:29.449 --> 00:03:29.459 align:start position:0% quite normal it has an owner there is a 00:03:29.459 --> 00:03:32.870 align:start position:0% quite normal it has an owner there is a transfer<00:03:30.120> and<00:03:30.470> this<00:03:31.470> is<00:03:31.610> actually<00:03:32.610> a<00:03:32.640> pattern 00:03:32.870 --> 00:03:32.880 align:start position:0% transfer and this is actually a pattern 00:03:32.880 --> 00:03:34.940 align:start position:0% transfer and this is actually a pattern here<00:03:33.150> which<00:03:33.270> I'd<00:03:33.450> like<00:03:33.660> to<00:03:33.870> race<00:03:34.080> as<00:03:34.320> a<00:03:34.350> good 00:03:34.940 --> 00:03:34.950 align:start position:0% here which I'd like to race as a good 00:03:34.950 --> 00:03:42.040 align:start position:0% here which I'd like to race as a good example<00:03:35.540> which<00:03:36.540> I<00:03:36.720> call<00:03:36.959> the<00:03:37.760> double<00:03:38.760> dispatch 00:03:42.040 --> 00:03:42.050 align:start position:0% 00:03:42.050 --> 00:03:47.040 align:start position:0% ownership<00:03:44.209> no<00:03:45.209> sorry<00:03:45.690> it<00:03:46.020> doesn't<00:03:46.350> have<00:03:46.500> that 00:03:47.040 --> 00:03:47.050 align:start position:0% ownership no sorry it doesn't have that 00:03:47.050 --> 00:03:49.300 align:start position:0% ownership no sorry it doesn't have that [Music] 00:03:49.300 --> 00:03:49.310 align:start position:0% [Music] 00:03:49.310 --> 00:03:51.770 align:start position:0% [Music] so<00:03:50.310> when<00:03:50.490> you<00:03:50.580> transfer<00:03:50.790> ownership<00:03:51.180> of<00:03:51.600> this 00:03:51.770 --> 00:03:51.780 align:start position:0% so when you transfer ownership of this 00:03:51.780 --> 00:03:54.380 align:start position:0% so when you transfer ownership of this thing<00:03:52.050> to<00:03:52.320> someone<00:03:52.560> else<00:03:52.860> it<00:03:53.430> has<00:03:53.640> to<00:03:53.790> check<00:03:54.090> to 00:03:54.380 --> 00:03:54.390 align:start position:0% thing to someone else it has to check to 00:03:54.390 --> 00:03:56.420 align:start position:0% thing to someone else it has to check to see<00:03:54.570> that<00:03:54.600> you<00:03:55.380> don't<00:03:55.590> actually<00:03:55.770> transfer<00:03:56.370> it 00:03:56.420 --> 00:03:56.430 align:start position:0% see that you don't actually transfer it 00:03:56.430 --> 00:04:00.980 align:start position:0% see that you don't actually transfer it to<00:03:56.490> no<00:03:57.360> owner<00:03:59.060> and<00:04:00.060> then<00:04:00.300> it<00:04:00.390> just<00:04:00.540> sets<00:04:00.780> the 00:04:00.980 --> 00:04:00.990 align:start position:0% to no owner and then it just sets the 00:04:00.990 --> 00:04:02.870 align:start position:0% to no owner and then it just sets the owner<00:04:01.200> to<00:04:01.320> the<00:04:01.440> new<00:04:01.620> owner<00:04:01.830> there's<00:04:02.610> another 00:04:02.870 --> 00:04:02.880 align:start position:0% owner to the new owner there's another 00:04:02.880 --> 00:04:05.720 align:start position:0% owner to the new owner there's another way<00:04:03.150> to<00:04:03.209> do<00:04:03.540> this<00:04:03.770> the<00:04:04.770> double<00:04:05.070> dispatch<00:04:05.430> is 00:04:05.720 --> 00:04:05.730 align:start position:0% way to do this the double dispatch is 00:04:05.730 --> 00:04:09.020 align:start position:0% way to do this the double dispatch is that<00:04:06.120> you<00:04:06.240> set<00:04:07.190> you<00:04:08.190> don't<00:04:08.370> set<00:04:08.550> the<00:04:08.580> owner<00:04:08.910> to 00:04:09.020 --> 00:04:09.030 align:start position:0% that you set you don't set the owner to 00:04:09.030 --> 00:04:10.610 align:start position:0% that you set you don't set the owner to new<00:04:09.209> owner<00:04:09.330> you<00:04:09.600> set<00:04:09.780> the<00:04:09.900> potential<00:04:10.440> new 00:04:10.610 --> 00:04:10.620 align:start position:0% new owner you set the potential new 00:04:10.620 --> 00:04:13.729 align:start position:0% new owner you set the potential new owner<00:04:10.800> to<00:04:11.700> the<00:04:11.730> new<00:04:11.970> owner<00:04:12.150> and<00:04:12.570> then<00:04:13.110> the 00:04:13.729 --> 00:04:13.739 align:start position:0% owner to the new owner and then the 00:04:13.739 --> 00:04:16.220 align:start position:0% owner to the new owner and then the actual<00:04:14.520> new<00:04:14.700> owner<00:04:14.910> needs<00:04:15.239> to<00:04:15.360> make<00:04:15.570> a<00:04:15.600> call<00:04:15.900> to 00:04:16.220 --> 00:04:16.230 align:start position:0% actual new owner needs to make a call to 00:04:16.230 --> 00:04:21.080 align:start position:0% actual new owner needs to make a call to accept<00:04:16.859> the<00:04:17.160> ownership<00:04:17.850> and<00:04:18.270> that<00:04:19.230> means<00:04:20.090> that 00:04:21.080 --> 00:04:21.090 align:start position:0% accept the ownership and that means that 00:04:21.090 --> 00:04:22.909 align:start position:0% accept the ownership and that means that you<00:04:21.270> know<00:04:21.450> for<00:04:21.720> a<00:04:21.750> fact<00:04:21.989> that<00:04:22.229> the<00:04:22.560> owner<00:04:22.740> of 00:04:22.909 --> 00:04:22.919 align:start position:0% you know for a fact that the owner of 00:04:22.919 --> 00:04:27.080 align:start position:0% you know for a fact that the owner of the<00:04:23.100> contract<00:04:23.580> is<00:04:23.790> capable<00:04:24.390> of<00:04:25.010> making<00:04:26.010> their 00:04:27.080 --> 00:04:27.090 align:start position:0% the contract is capable of making their 00:04:27.090 --> 00:04:34.450 align:start position:0% the contract is capable of making their messages<00:04:27.540> and<00:04:27.780> interacting<00:04:28.530> with<00:04:29.000> contracts 00:04:34.450 --> 00:04:34.460 align:start position:0% 00:04:34.460 --> 00:04:38.890 align:start position:0% [Music] 00:04:38.890 --> 00:04:38.900 align:start position:0% 00:04:38.900 --> 00:04:42.560 align:start position:0% then<00:04:39.900> we<00:04:40.080> have<00:04:40.229> the<00:04:40.410> ERC<00:04:40.800> 20<00:04:41.699> implementation 00:04:42.560 --> 00:04:42.570 align:start position:0% then we have the ERC 20 implementation 00:04:42.570 --> 00:04:47.260 align:start position:0% then we have the ERC 20 implementation [Music] 00:04:47.260 --> 00:04:47.270 align:start position:0% 00:04:47.270 --> 00:04:55.219 align:start position:0% and<00:04:48.270> we<00:04:49.169> have<00:04:49.320> safe<00:04:49.710> map<00:04:50.780> so<00:04:53.720> anything's<00:04:54.720> there 00:04:55.219 --> 00:04:55.229 align:start position:0% and we have safe map so anything's there 00:04:55.229 --> 00:04:56.930 align:start position:0% and we have safe map so anything's there nothing<00:04:55.919> real<00:04:56.040> to<00:04:56.070> mention<00:04:56.460> about<00:04:56.550> the<00:04:56.729> safe 00:04:56.930 --> 00:04:56.940 align:start position:0% nothing real to mention about the safe 00:04:56.940 --> 00:05:00.469 align:start position:0% nothing real to mention about the safe math<00:04:57.449> is<00:04:57.960> kind<00:04:58.560> of<00:04:58.740> standard<00:04:59.370> although<00:05:00.270> it 00:05:00.469 --> 00:05:00.479 align:start position:0% math is kind of standard although it 00:05:00.479 --> 00:05:02.330 align:start position:0% math is kind of standard although it might<00:05:00.570> be<00:05:00.720> worth<00:05:00.870> noting<00:05:01.220> when<00:05:02.220> you're 00:05:02.330 --> 00:05:02.340 align:start position:0% might be worth noting when you're 00:05:02.340 --> 00:05:03.560 align:start position:0% might be worth noting when you're looking<00:05:02.550> at<00:05:02.639> Elsa's<00:05:02.940> contract<00:05:03.330> you<00:05:03.450> might 00:05:03.560 --> 00:05:03.570 align:start position:0% looking at Elsa's contract you might 00:05:03.570 --> 00:05:04.730 align:start position:0% looking at Elsa's contract you might want<00:05:03.720> to<00:05:03.750> check<00:05:03.990> to<00:05:04.020> make<00:05:04.139> sure<00:05:04.229> the<00:05:04.380> safe<00:05:04.500> Mac 00:05:04.730 --> 00:05:04.740 align:start position:0% want to check to make sure the safe Mac 00:05:04.740 --> 00:05:06.530 align:start position:0% want to check to make sure the safe Mac what<00:05:05.280> Scott<00:05:05.520> was<00:05:05.639> copied<00:05:05.970> over<00:05:06.090> and<00:05:06.450> they 00:05:06.530 --> 00:05:06.540 align:start position:0% what Scott was copied over and they 00:05:06.540 --> 00:05:09.050 align:start position:0% what Scott was copied over and they aren't<00:05:06.780> hiding<00:05:07.410> bugs<00:05:07.800> in<00:05:07.979> that<00:05:08.010> you<00:05:08.940> might 00:05:09.050 --> 00:05:09.060 align:start position:0% aren't hiding bugs in that you might 00:05:09.060 --> 00:05:11.360 align:start position:0% aren't hiding bugs in that you might just<00:05:09.120> loss<00:05:09.360> over<00:05:09.630> I<00:05:09.660> trust<00:05:10.290> it<00:05:10.440> and<00:05:10.560> then<00:05:10.680> who's 00:05:11.360 --> 00:05:11.370 align:start position:0% just loss over I trust it and then who's 00:05:11.370 --> 00:05:14.540 align:start position:0% just loss over I trust it and then who's that<00:05:11.720> yes<00:05:12.720> I<00:05:13.110> think<00:05:13.229> I<00:05:13.560> feel<00:05:13.710> like<00:05:13.740> that's<00:05:14.280> one 00:05:14.540 --> 00:05:14.550 align:start position:0% that yes I think I feel like that's one 00:05:14.550 --> 00:05:17.390 align:start position:0% that yes I think I feel like that's one thing<00:05:14.850> that<00:05:15.270> is<00:05:15.720> like<00:05:16.560> would<00:05:17.010> be<00:05:17.160> really 00:05:17.390 --> 00:05:17.400 align:start position:0% thing that is like would be really 00:05:17.400 --> 00:05:19.640 align:start position:0% thing that is like would be really helpful<00:05:17.639> to<00:05:17.850> have<00:05:18.150> like<00:05:18.330> a<00:05:18.360> compiler<00:05:19.080> level 00:05:19.640 --> 00:05:19.650 align:start position:0% helpful to have like a compiler level 00:05:19.650 --> 00:05:21.260 align:start position:0% helpful to have like a compiler level support<00:05:19.950> for<00:05:20.130> like<00:05:20.250> import<00:05:20.700> the<00:05:20.910> code<00:05:21.060> that 00:05:21.260 --> 00:05:21.270 align:start position:0% support for like import the code that 00:05:21.270 --> 00:05:24.140 align:start position:0% support for like import the code that has<00:05:21.389> this<00:05:21.570> hash<00:05:22.310> rate<00:05:23.310> right<00:05:23.880> because 00:05:24.140 --> 00:05:24.150 align:start position:0% has this hash rate right because 00:05:24.150 --> 00:05:26.480 align:start position:0% has this hash rate right because oftentimes<00:05:24.720> like<00:05:25.169> yeah<00:05:25.590> it's<00:05:25.979> very<00:05:26.190> easy<00:05:26.400> to 00:05:26.480 --> 00:05:26.490 align:start position:0% oftentimes like yeah it's very easy to 00:05:26.490 --> 00:05:28.520 align:start position:0% oftentimes like yeah it's very easy to just<00:05:26.669> assume<00:05:27.060> this<00:05:27.570> is<00:05:27.720> this<00:05:27.930> is<00:05:28.110> fine<00:05:28.350> it 00:05:28.520 --> 00:05:28.530 align:start position:0% just assume this is this is fine it 00:05:28.530 --> 00:05:30.680 align:start position:0% just assume this is this is fine it looks<00:05:28.560> like<00:05:28.830> it<00:05:28.919> turns<00:05:29.160> up<00:05:29.250> Lin<00:05:29.490> or<00:05:29.729> ENS<00:05:30.240> name 00:05:30.680 --> 00:05:30.690 align:start position:0% looks like it turns up Lin or ENS name 00:05:30.690 --> 00:05:31.279 align:start position:0% looks like it turns up Lin or ENS name maybe 00:05:31.279 --> 00:05:31.289 align:start position:0% maybe 00:05:31.289 --> 00:05:33.290 align:start position:0% maybe so<00:05:31.410> the<00:05:31.530> yeah<00:05:31.680> import<00:05:32.070> safe<00:05:32.340> math<00:05:32.580> eath<00:05:33.030> as 00:05:33.290 --> 00:05:33.300 align:start position:0% so the yeah import safe math eath as 00:05:33.300 --> 00:05:35.540 align:start position:0% so the yeah import safe math eath as opposed<00:05:33.630> to<00:05:33.780> because<00:05:34.530> that<00:05:34.650> you<00:05:34.740> guys<00:05:34.860> easily 00:05:35.540 --> 00:05:35.550 align:start position:0% opposed to because that you guys easily 00:05:35.550 --> 00:05:37.850 align:start position:0% opposed to because that you guys easily lie<00:05:35.729> about<00:05:35.970> the<00:05:36.090> hash<00:05:36.330> it's<00:05:36.750> well<00:05:37.500> I<00:05:37.530> camps 00:05:37.850 --> 00:05:37.860 align:start position:0% lie about the hash it's well I camps 00:05:37.860 --> 00:05:39.920 align:start position:0% lie about the hash it's well I camps like<00:05:38.039> a<00:05:38.100> bunch<00:05:38.250> of<00:05:38.310> red<00:05:38.460> I<00:05:38.760> mean<00:05:39.270> if<00:05:39.389> the<00:05:39.720> tool 00:05:39.920 --> 00:05:39.930 align:start position:0% like a bunch of red I mean if the tool 00:05:39.930 --> 00:05:42.680 align:start position:0% like a bunch of red I mean if the tool grabs<00:05:40.410> like<00:05:41.220> something<00:05:42.090> based<00:05:42.300> on<00:05:42.389> the<00:05:42.510> hash 00:05:42.680 --> 00:05:42.690 align:start position:0% grabs like something based on the hash 00:05:42.690 --> 00:05:43.909 align:start position:0% grabs like something based on the hash like<00:05:42.990> I'm<00:05:43.139> thinking<00:05:43.229> if<00:05:43.530> I'm<00:05:43.620> looking<00:05:43.740> at 00:05:43.909 --> 00:05:43.919 align:start position:0% like I'm thinking if I'm looking at 00:05:43.919 --> 00:05:45.740 align:start position:0% like I'm thinking if I'm looking at ether<00:05:44.220> scan<00:05:44.460> I<00:05:44.490> see<00:05:44.820> like<00:05:44.940> import<00:05:45.389> some<00:05:45.539> crazy 00:05:45.740 --> 00:05:45.750 align:start position:0% ether scan I see like import some crazy 00:05:45.750 --> 00:05:47.839 align:start position:0% ether scan I see like import some crazy I'm<00:05:46.289> gonna<00:05:46.410> trust<00:05:46.680> this<00:05:46.950> is<00:05:47.130> safe<00:05:47.310> map<00:05:47.520> and<00:05:47.760> not 00:05:47.839 --> 00:05:47.849 align:start position:0% I'm gonna trust this is safe map and not 00:05:47.849 --> 00:05:49.430 align:start position:0% I'm gonna trust this is safe map and not some<00:05:48.090> sort<00:05:48.240> of<00:05:48.360> oh<00:05:48.510> yeah<00:05:48.870> but<00:05:49.050> it<00:05:49.110> says<00:05:49.229> safe 00:05:49.430 --> 00:05:49.440 align:start position:0% some sort of oh yeah but it says safe 00:05:49.440 --> 00:05:50.960 align:start position:0% some sort of oh yeah but it says safe math<00:05:49.650> dot<00:05:49.860> eath<00:05:50.099> I<00:05:50.310> have<00:05:50.430> more<00:05:50.610> faith<00:05:50.789> that 00:05:50.960 --> 00:05:50.970 align:start position:0% math dot eath I have more faith that 00:05:50.970 --> 00:05:54.140 align:start position:0% math dot eath I have more faith that it's<00:05:51.120> like<00:05:51.270> so<00:05:51.870> I<00:05:51.900> think<00:05:52.220> eath<00:05:53.220> p.m.<00:05:53.610> is<00:05:53.820> trying 00:05:54.140 --> 00:05:54.150 align:start position:0% it's like so I think eath p.m. is trying 00:05:54.150 --> 00:05:56.089 align:start position:0% it's like so I think eath p.m. is trying to<00:05:54.360> accomplish<00:05:54.960> this<00:05:55.380> sort<00:05:55.560> of<00:05:55.620> thing<00:05:55.830> and 00:05:56.089 --> 00:05:56.099 align:start position:0% to accomplish this sort of thing and 00:05:56.099 --> 00:05:57.890 align:start position:0% to accomplish this sort of thing and with<00:05:56.340> some<00:05:56.610> compiler<00:05:57.030> integration<00:05:57.720> that 00:05:57.890 --> 00:05:57.900 align:start position:0% with some compiler integration that 00:05:57.900 --> 00:06:00.070 align:start position:0% with some compiler integration that would<00:05:58.080> be<00:05:58.200> a<00:05:58.229> good<00:05:58.440> starting<00:05:58.889> parade 00:06:00.070 --> 00:06:00.080 align:start position:0% would be a good starting parade 00:06:00.080 --> 00:06:04.640 align:start position:0% would be a good starting parade so<00:06:01.310> here's<00:06:02.310> the<00:06:02.490> ERC<00:06:02.760> xx<00:06:03.530> implementation<00:06:04.530> of 00:06:04.640 --> 00:06:04.650 align:start position:0% so here's the ERC xx implementation of 00:06:04.650 --> 00:06:07.400 align:start position:0% so here's the ERC xx implementation of the<00:06:04.710> specification<00:06:05.400> and<00:06:05.900> so<00:06:06.900> I'd<00:06:07.020> like<00:06:07.050> to<00:06:07.169> ask 00:06:07.400 --> 00:06:07.410 align:start position:0% the specification and so I'd like to ask 00:06:07.410 --> 00:06:10.940 align:start position:0% the specification and so I'd like to ask you<00:06:07.530> guys<00:06:08.030> and<00:06:09.030> and<00:06:09.990> to<00:06:10.110> give<00:06:10.260> some<00:06:10.410> context 00:06:10.940 --> 00:06:10.950 align:start position:0% you guys and and to give some context 00:06:10.950 --> 00:06:13.909 align:start position:0% you guys and and to give some context the<00:06:11.250> ERC<00:06:11.550> xx<00:06:11.910> specification<00:06:12.539> states<00:06:12.840> that<00:06:13.500> the 00:06:13.909 --> 00:06:13.919 align:start position:0% the ERC xx specification states that the 00:06:13.919 --> 00:06:15.650 align:start position:0% the ERC xx specification states that the transfer<00:06:14.310> method<00:06:14.700> should<00:06:15.060> return<00:06:15.120> a<00:06:15.389> boolean 00:06:15.650 --> 00:06:15.660 align:start position:0% transfer method should return a boolean 00:06:15.660 --> 00:06:18.020 align:start position:0% transfer method should return a boolean whether<00:06:16.080> the<00:06:16.320> transfer<00:06:16.979> was<00:06:17.370> successful<00:06:17.400> or 00:06:18.020 --> 00:06:18.030 align:start position:0% whether the transfer was successful or 00:06:18.030 --> 00:06:20.629 align:start position:0% whether the transfer was successful or not<00:06:18.060> and<00:06:19.020> as<00:06:19.320> you<00:06:19.440> can<00:06:19.560> see<00:06:19.770> and<00:06:20.340> this<00:06:20.460> is<00:06:20.550> quite 00:06:20.629 --> 00:06:20.639 align:start position:0% not and as you can see and this is quite 00:06:20.639 --> 00:06:23.870 align:start position:0% not and as you can see and this is quite common<00:06:20.940> to<00:06:21.180> see<00:06:21.330> that<00:06:21.990> it<00:06:22.800> actually<00:06:22.880> never 00:06:23.870 --> 00:06:23.880 align:start position:0% common to see that it actually never 00:06:23.880 --> 00:06:26.690 align:start position:0% common to see that it actually never returns<00:06:24.270> false<00:06:24.539> it<00:06:25.289> either<00:06:25.530> returns<00:06:26.010> true<00:06:26.220> or 00:06:26.690 --> 00:06:26.700 align:start position:0% returns false it either returns true or 00:06:26.700 --> 00:06:29.089 align:start position:0% returns false it either returns true or it<00:06:26.970> throws<00:06:27.289> so<00:06:28.289> worried<00:06:28.500> what<00:06:28.740> it<00:06:28.830> was<00:06:28.919> your 00:06:29.089 --> 00:06:29.099 align:start position:0% it throws so worried what it was your 00:06:29.099 --> 00:06:31.040 align:start position:0% it throws so worried what it was your guy's<00:06:29.280> opinion<00:06:29.550> would<00:06:30.060> you<00:06:30.090> make<00:06:30.690> a<00:06:30.720> note<00:06:31.020> of 00:06:31.040 --> 00:06:31.050 align:start position:0% guy's opinion would you make a note of 00:06:31.050 --> 00:06:32.900 align:start position:0% guy's opinion would you make a note of this<00:06:31.320> and<00:06:31.650> in<00:06:31.889> order<00:06:32.250> to<00:06:32.280> do<00:06:32.490> you<00:06:32.610> recommend 00:06:32.900 --> 00:06:32.910 align:start position:0% this and in order to do you recommend 00:06:32.910 --> 00:06:34.610 align:start position:0% this and in order to do you recommend against<00:06:33.360> it<00:06:33.450> to<00:06:33.570> for<00:06:33.810> it<00:06:33.900> I<00:06:34.110> would<00:06:34.410> definitely 00:06:34.610 --> 00:06:34.620 align:start position:0% against it to for it I would definitely 00:06:34.620 --> 00:06:36.320 align:start position:0% against it to for it I would definitely make<00:06:34.919> no<00:06:35.070> like<00:06:35.340> the<00:06:35.550> problem<00:06:35.820> is<00:06:35.909> something 00:06:36.320 --> 00:06:36.330 align:start position:0% make no like the problem is something 00:06:36.330 --> 00:06:38.149 align:start position:0% make no like the problem is something another<00:06:36.659> contract<00:06:37.229> might<00:06:37.469> be<00:06:37.590> calling<00:06:37.919> us<00:06:38.010> to 00:06:38.149 --> 00:06:38.159 align:start position:0% another contract might be calling us to 00:06:38.159 --> 00:06:40.040 align:start position:0% another contract might be calling us to do<00:06:38.280> something<00:06:38.550> and<00:06:38.789> I<00:06:38.909> Eve<00:06:39.030> called<00:06:39.240> cause<00:06:39.539> that 00:06:40.040 --> 00:06:40.050 align:start position:0% do something and I Eve called cause that 00:06:40.050 --> 00:06:43.189 align:start position:0% do something and I Eve called cause that to<00:06:40.319> fail<00:06:40.500> as<00:06:41.460> a<00:06:41.520> result<00:06:41.940> of<00:06:42.090> you<00:06:42.720> know<00:06:42.810> supposed 00:06:43.189 --> 00:06:43.199 align:start position:0% to fail as a result of you know supposed 00:06:43.199 --> 00:06:44.629 align:start position:0% to fail as a result of you know supposed to<00:06:43.259> return<00:06:43.379> false<00:06:43.650> if<00:06:43.949> it<00:06:44.039> didn't<00:06:44.250> work<00:06:44.340> as 00:06:44.629 --> 00:06:44.639 align:start position:0% to return false if it didn't work as 00:06:44.639 --> 00:06:47.629 align:start position:0% to return false if it didn't work as opposed<00:06:44.909> to<00:06:45.030> bail<00:06:45.990> out<00:06:46.199> of<00:06:46.229> the<00:06:46.379> universe<00:06:46.740> I'm 00:06:47.629 --> 00:06:47.639 align:start position:0% opposed to bail out of the universe I'm 00:06:47.639 --> 00:06:50.420 align:start position:0% opposed to bail out of the universe I'm of<00:06:48.180> the<00:06:48.389> opposite<00:06:48.840> opinion<00:06:49.039> ESA<00:06:50.039> 20<00:06:50.310> was 00:06:50.420 --> 00:06:50.430 align:start position:0% of the opposite opinion ESA 20 was 00:06:50.430 --> 00:06:51.589 align:start position:0% of the opposite opinion ESA 20 was broken<00:06:50.879> when<00:06:51.060> I<00:06:51.090> said<00:06:51.360> that<00:06:51.509> you<00:06:51.569> should 00:06:51.589 --> 00:06:51.599 align:start position:0% broken when I said that you should 00:06:51.599 --> 00:06:53.450 align:start position:0% broken when I said that you should return<00:06:52.020> false<00:06:52.080> and<00:06:52.680> not<00:06:52.710> revert<00:06:53.159> state 00:06:53.450 --> 00:06:53.460 align:start position:0% return false and not revert state 00:06:53.460 --> 00:06:55.249 align:start position:0% return false and not revert state changes<00:06:53.970> if<00:06:54.270> you<00:06:54.569> try<00:06:54.810> and<00:06:54.870> do<00:06:55.050> something 00:06:55.249 --> 00:06:55.259 align:start position:0% changes if you try and do something 00:06:55.259 --> 00:06:59.659 align:start position:0% changes if you try and do something illegal<00:06:55.500> and<00:06:57.590> tried<00:06:58.590> to<00:06:58.710> fight<00:06:58.919> to<00:06:59.129> get<00:06:59.250> people 00:06:59.659 --> 00:06:59.669 align:start position:0% illegal and tried to fight to get people 00:06:59.669 --> 00:07:03.260 align:start position:0% illegal and tried to fight to get people to<00:07:00.000> actually<00:07:00.659> revert<00:07:01.169> when<00:07:02.069> you<00:07:02.849> know<00:07:02.970> illegal 00:07:03.260 --> 00:07:03.270 align:start position:0% to actually revert when you know illegal 00:07:03.270 --> 00:07:06.820 align:start position:0% to actually revert when you know illegal changes<00:07:03.810> are<00:07:03.900> made<00:07:04.020> because<00:07:04.740> it's<00:07:05.280> far<00:07:05.520> too 00:07:06.820 --> 00:07:06.830 align:start position:0% changes are made because it's far too 00:07:06.830 --> 00:07:10.610 align:start position:0% changes are made because it's far too far<00:07:07.830> too<00:07:07.860> error-prone<00:07:08.669> to<00:07:09.360> try<00:07:09.569> and<00:07:09.750> handle 00:07:10.610 --> 00:07:10.620 align:start position:0% far too error-prone to try and handle 00:07:10.620 --> 00:07:12.850 align:start position:0% far too error-prone to try and handle things<00:07:10.949> with<00:07:11.220> an<00:07:11.340> undo<00:07:11.610> mechanism<00:07:12.150> yourself 00:07:12.850 --> 00:07:12.860 align:start position:0% things with an undo mechanism yourself 00:07:12.860 --> 00:07:15.260 align:start position:0% things with an undo mechanism yourself rather<00:07:13.860> than<00:07:14.190> relying<00:07:14.460> on<00:07:14.639> the<00:07:14.789> vm's 00:07:15.260 --> 00:07:15.270 align:start position:0% rather than relying on the vm's 00:07:15.270 --> 00:07:17.809 align:start position:0% rather than relying on the vm's mechanism<00:07:15.810> and<00:07:16.050> if<00:07:16.469> the<00:07:16.710> if<00:07:17.159> it's<00:07:17.460> hard<00:07:17.669> to 00:07:17.809 --> 00:07:17.819 align:start position:0% mechanism and if the if it's hard to 00:07:17.819 --> 00:07:20.390 align:start position:0% mechanism and if the if it's hard to handle<00:07:18.000> a<00:07:18.240> return<00:07:18.629> a<00:07:18.930> reverse<00:07:19.560> in<00:07:19.919> solidity 00:07:20.390 --> 00:07:20.400 align:start position:0% handle a return a reverse in solidity 00:07:20.400 --> 00:07:21.830 align:start position:0% handle a return a reverse in solidity then<00:07:20.639> it's<00:07:20.789> a<00:07:20.849> problem<00:07:20.969> with<00:07:21.180> solidity<00:07:21.569> that 00:07:21.830 --> 00:07:21.840 align:start position:0% then it's a problem with solidity that 00:07:21.840 --> 00:07:24.170 align:start position:0% then it's a problem with solidity that we<00:07:21.930> should<00:07:22.110> fix<00:07:22.460> well<00:07:23.460> I<00:07:23.520> think<00:07:23.759> it's<00:07:24.030> also 00:07:24.170 --> 00:07:24.180 align:start position:0% we should fix well I think it's also 00:07:24.180 --> 00:07:29.240 align:start position:0% we should fix well I think it's also just<00:07:24.530> it's<00:07:25.530> probably<00:07:26.099> better<00:07:26.310> for<00:07:27.560> the<00:07:28.560> next 00:07:29.240 --> 00:07:29.250 align:start position:0% just it's probably better for the next 00:07:29.250 --> 00:07:31.490 align:start position:0% just it's probably better for the next at<00:07:29.759> least<00:07:29.789> the<00:07:30.180> next<00:07:30.419> year<00:07:30.599> or<00:07:30.810> two<00:07:30.840> to<00:07:31.289> just 00:07:31.490 --> 00:07:31.500 align:start position:0% at least the next year or two to just 00:07:31.500 --> 00:07:33.890 align:start position:0% at least the next year or two to just use<00:07:31.889> the<00:07:32.159> throw<00:07:32.400> pattern<00:07:32.729> just<00:07:33.060> because<00:07:33.360> you 00:07:33.890 --> 00:07:33.900 align:start position:0% use the throw pattern just because you 00:07:33.900 --> 00:07:35.420 align:start position:0% use the throw pattern just because you know<00:07:34.680> I<00:07:34.710> don't<00:07:34.919> think<00:07:35.069> you<00:07:35.129> literally 00:07:35.420 --> 00:07:35.430 align:start position:0% know I don't think you literally 00:07:35.430 --> 00:07:37.249 align:start position:0% know I don't think you literally wouldn't<00:07:35.789> have<00:07:35.879> enough<00:07:36.060> gas<00:07:36.270> for<00:07:36.300> non-trivial 00:07:37.249 --> 00:07:37.259 align:start position:0% wouldn't have enough gas for non-trivial 00:07:37.259 --> 00:07:39.950 align:start position:0% wouldn't have enough gas for non-trivial contracts<00:07:38.129> to<00:07:38.340> do<00:07:38.460> try<00:07:38.669> accepted<00:07:39.060> locks<00:07:39.270> right 00:07:39.950 --> 00:07:39.960 align:start position:0% contracts to do try accepted locks right 00:07:39.960 --> 00:07:42.619 align:start position:0% contracts to do try accepted locks right like<00:07:40.139> the<00:07:40.560> amount<00:07:40.800> of<00:07:40.860> checking<00:07:41.370> I<00:07:41.610> mean<00:07:41.789> it's 00:07:42.619 --> 00:07:42.629 align:start position:0% like the amount of checking I mean it's 00:07:42.629 --> 00:07:44.480 align:start position:0% like the amount of checking I mean it's it's<00:07:42.900> already<00:07:43.139> a<00:07:43.169> nightmare<00:07:43.740> to<00:07:44.130> do<00:07:44.250> try 00:07:44.480 --> 00:07:44.490 align:start position:0% it's already a nightmare to do try 00:07:44.490 --> 00:07:47.300 align:start position:0% it's already a nightmare to do try accept<00:07:44.819> walks<00:07:45.150> in<00:07:45.479> in<00:07:46.110> normal<00:07:46.500> software<00:07:46.919> if 00:07:47.300 --> 00:07:47.310 align:start position:0% accept walks in in normal software if 00:07:47.310 --> 00:07:48.379 align:start position:0% accept walks in in normal software if you're<00:07:47.669> trying<00:07:47.819> to<00:07:47.880> do<00:07:47.969> with<00:07:48.090> all<00:07:48.180> the 00:07:48.379 --> 00:07:48.389 align:start position:0% you're trying to do with all the 00:07:48.389 --> 00:07:49.790 align:start position:0% you're trying to do with all the constraints<00:07:48.810> of<00:07:48.870> the<00:07:48.900> blockchain<00:07:49.169> and 00:07:49.790 --> 00:07:49.800 align:start position:0% constraints of the blockchain and 00:07:49.800 --> 00:07:53.480 align:start position:0% constraints of the blockchain and of<00:07:50.400> the<00:07:50.789> EVM<00:07:51.180> and<00:07:51.479> and<00:07:51.630> like<00:07:52.199> the<00:07:53.159> amount<00:07:53.310> of 00:07:53.480 --> 00:07:53.490 align:start position:0% of the EVM and and like the amount of 00:07:53.490 --> 00:07:55.129 align:start position:0% of the EVM and and like the amount of sub<00:07:53.940> solidity<00:07:54.270> doesn't<00:07:54.599> support<00:07:54.870> out<00:07:54.990> of<00:07:55.020> the 00:07:55.129 --> 00:07:55.139 align:start position:0% sub solidity doesn't support out of the 00:07:55.139 --> 00:07:57.950 align:start position:0% sub solidity doesn't support out of the box<00:07:55.199> is<00:07:55.680> I<00:07:56.159> think<00:07:56.550> the<00:07:56.729> amount<00:07:56.940> of<00:07:57.060> errors<00:07:57.360> will 00:07:57.950 --> 00:07:57.960 align:start position:0% box is I think the amount of errors will 00:07:57.960 --> 00:08:00.559 align:start position:0% box is I think the amount of errors will go<00:07:58.080> up<00:07:58.229> a<00:07:58.349> lot<00:07:58.500> and<00:07:58.740> I<00:07:59.039> think<00:07:59.099> yeah<00:07:59.340> the<00:07:59.610> ERC<00:08:00.180> 20 00:08:00.559 --> 00:08:00.569 align:start position:0% go up a lot and I think yeah the ERC 20 00:08:00.569 --> 00:08:02.570 align:start position:0% go up a lot and I think yeah the ERC 20 standard<00:08:00.930> was<00:08:01.050> a<00:08:01.080> bit<00:08:01.259> messy<00:08:02.039> because<00:08:02.130> i<00:08:02.430> mean 00:08:02.570 --> 00:08:02.580 align:start position:0% standard was a bit messy because i mean 00:08:02.580 --> 00:08:05.120 align:start position:0% standard was a bit messy because i mean like<00:08:03.300> this<00:08:03.779> could<00:08:03.960> only<00:08:04.080> ever<00:08:04.319> return<00:08:04.800> true 00:08:05.120 --> 00:08:05.130 align:start position:0% like this could only ever return true 00:08:05.130 --> 00:08:06.409 align:start position:0% like this could only ever return true right<00:08:05.550> I<00:08:05.580> mean<00:08:05.819> this<00:08:05.909> is<00:08:06.029> never<00:08:06.240> going<00:08:06.389> to 00:08:06.409 --> 00:08:06.419 align:start position:0% right I mean this is never going to 00:08:06.419 --> 00:08:09.469 align:start position:0% right I mean this is never going to return<00:08:06.630> false<00:08:06.900> most<00:08:07.139> contracts<00:08:07.710> do<00:08:07.830> that<00:08:08.479> so 00:08:09.469 --> 00:08:09.479 align:start position:0% return false most contracts do that so 00:08:09.479 --> 00:08:12.409 align:start position:0% return false most contracts do that so like<00:08:09.690> why<00:08:10.169> even<00:08:10.409> have<00:08:10.710> abilene<00:08:11.219> at<00:08:11.340> all<00:08:11.490> well 00:08:12.409 --> 00:08:12.419 align:start position:0% like why even have abilene at all well 00:08:12.419 --> 00:08:14.330 align:start position:0% like why even have abilene at all well the<00:08:12.449> original<00:08:12.779> idea<00:08:13.349> was<00:08:13.590> that<00:08:13.650> it<00:08:13.979> shouldn't 00:08:14.330 --> 00:08:14.340 align:start position:0% the original idea was that it shouldn't 00:08:14.340 --> 00:08:16.129 align:start position:0% the original idea was that it shouldn't even<00:08:14.460> throw<00:08:14.849> that<00:08:15.060> should<00:08:15.270> return<00:08:15.509> false<00:08:15.569> if 00:08:16.129 --> 00:08:16.139 align:start position:0% even throw that should return false if 00:08:16.139 --> 00:08:17.749 align:start position:0% even throw that should return false if you<00:08:16.289> tried<00:08:16.500> to<00:08:16.620> transfer<00:08:17.009> more<00:08:17.190> tokens<00:08:17.550> than 00:08:17.749 --> 00:08:17.759 align:start position:0% you tried to transfer more tokens than 00:08:17.759 --> 00:08:19.730 align:start position:0% you tried to transfer more tokens than you<00:08:17.819> add<00:08:17.940> for<00:08:18.210> instance<00:08:18.289> and<00:08:19.289> I<00:08:19.409> think<00:08:19.590> that's 00:08:19.730 --> 00:08:19.740 align:start position:0% you add for instance and I think that's 00:08:19.740 --> 00:08:20.779 align:start position:0% you add for instance and I think that's broken<00:08:20.129> yeah<00:08:20.310> I<00:08:20.400> feel<00:08:20.520> like<00:08:20.610> I've<00:08:20.729> been 00:08:20.779 --> 00:08:20.789 align:start position:0% broken yeah I feel like I've been 00:08:20.789 --> 00:08:24.140 align:start position:0% broken yeah I feel like I've been overthrown<00:08:21.150> but<00:08:21.539> I<00:08:21.569> mean<00:08:22.009> mymy<00:08:23.009> Argan<00:08:23.610> is<00:08:23.669> even 00:08:24.140 --> 00:08:24.150 align:start position:0% overthrown but I mean mymy Argan is even 00:08:24.150 --> 00:08:25.999 align:start position:0% overthrown but I mean mymy Argan is even the<00:08:24.240> specific<00:08:24.449> specification<00:08:25.289> kind<00:08:25.469> of<00:08:25.590> sucks 00:08:25.999 --> 00:08:26.009 align:start position:0% the specific specification kind of sucks 00:08:26.009 --> 00:08:27.529 align:start position:0% the specific specification kind of sucks we<00:08:26.400> should<00:08:26.550> still<00:08:26.729> follow<00:08:26.909> the<00:08:27.000> specification 00:08:27.529 --> 00:08:27.539 align:start position:0% we should still follow the specification 00:08:27.539 --> 00:08:30.740 align:start position:0% we should still follow the specification and<00:08:27.779> make<00:08:28.080> an<00:08:28.229> ER<00:08:28.500> C<00:08:28.789> 20<00:08:29.789> plus<00:08:30.090> something<00:08:30.479> that 00:08:30.740 --> 00:08:30.750 align:start position:0% and make an ER C 20 plus something that 00:08:30.750 --> 00:08:33.740 align:start position:0% and make an ER C 20 plus something that says<00:08:30.930> don't<00:08:31.319> do<00:08:31.469> dumb<00:08:31.650> things<00:08:31.680> so<00:08:32.510> so<00:08:33.510> to<00:08:33.570> be 00:08:33.740 --> 00:08:33.750 align:start position:0% says don't do dumb things so so to be 00:08:33.750 --> 00:08:36.110 align:start position:0% says don't do dumb things so so to be fair<00:08:33.779> I<00:08:34.020> don't<00:08:34.169> think<00:08:34.500> this<00:08:34.620> is<00:08:35.120> non-compliant 00:08:36.110 --> 00:08:36.120 align:start position:0% fair I don't think this is non-compliant 00:08:36.120 --> 00:08:38.060 align:start position:0% fair I don't think this is non-compliant because<00:08:36.449> the<00:08:36.659> ERC<00:08:37.019> 20<00:08:37.380> doesn't<00:08:37.649> say<00:08:37.829> anything 00:08:38.060 --> 00:08:38.070 align:start position:0% because the ERC 20 doesn't say anything 00:08:38.070 --> 00:08:39.800 align:start position:0% because the ERC 20 doesn't say anything about<00:08:38.279> whether<00:08:38.640> you<00:08:38.820> can<00:08:38.940> throw<00:08:39.209> or<00:08:39.390> not 00:08:39.800 --> 00:08:39.810 align:start position:0% about whether you can throw or not 00:08:39.810 --> 00:08:43.159 align:start position:0% about whether you can throw or not if<00:08:40.440> you<00:08:40.680> return<00:08:41.750> successfully<00:08:42.750> you<00:08:42.870> have<00:08:42.899> to 00:08:43.159 --> 00:08:43.169 align:start position:0% if you return successfully you have to 00:08:43.169 --> 00:08:46.340 align:start position:0% if you return successfully you have to return<00:08:43.380> true<00:08:43.970> but<00:08:44.970> throwing<00:08:45.630> in<00:08:45.779> a<00:08:45.870> case<00:08:46.140> of<00:08:46.290> a 00:08:46.340 --> 00:08:46.350 align:start position:0% return true but throwing in a case of a 00:08:46.350 --> 00:08:48.139 align:start position:0% return true but throwing in a case of a failure<00:08:46.560> isn't<00:08:46.829> prohibited<00:08:47.399> that's<00:08:47.760> very<00:08:48.000> and 00:08:48.139 --> 00:08:48.149 align:start position:0% failure isn't prohibited that's very and 00:08:48.149 --> 00:08:51.560 align:start position:0% failure isn't prohibited that's very and then<00:08:48.300> like<00:08:48.510> on<00:08:49.190> the<00:08:50.190> this<00:08:50.520> is<00:08:50.579> this<00:08:51.120> is<00:08:51.329> like<00:08:51.540> a 00:08:51.560 --> 00:08:51.570 align:start position:0% then like on the this is this is like a 00:08:51.570 --> 00:08:53.540 align:start position:0% then like on the this is this is like a real<00:08:51.930> or<00:08:52.380> has<00:08:52.620> been<00:08:52.740> a<00:08:52.829> real<00:08:52.980> bad<00:08:53.160> problem<00:08:53.310> to 00:08:53.540 --> 00:08:53.550 align:start position:0% real or has been a real bad problem to 00:08:53.550 --> 00:08:54.410 align:start position:0% real or has been a real bad problem to compile 00:08:54.410 --> 00:08:54.420 align:start position:0% compile 00:08:54.420 --> 00:08:57.650 align:start position:0% compile it's<00:08:54.900> not<00:08:55.350> strict<00:08:55.770> enough<00:08:55.860> like<00:08:56.400> you<00:08:56.700> could 00:08:57.650 --> 00:08:57.660 align:start position:0% it's not strict enough like you could 00:08:57.660 --> 00:09:00.440 align:start position:0% it's not strict enough like you could for<00:08:57.870> example<00:08:57.950> right<00:08:58.950> at<00:08:59.550> least<00:08:59.670> up<00:09:00.090> until<00:09:00.270> very 00:09:00.440 --> 00:09:00.450 align:start position:0% for example right at least up until very 00:09:00.450 --> 00:09:01.670 align:start position:0% for example right at least up until very recently<00:09:00.930> you<00:09:01.080> could<00:09:01.200> write<00:09:01.380> this<00:09:01.500> function 00:09:01.670 --> 00:09:01.680 align:start position:0% recently you could write this function 00:09:01.680 --> 00:09:03.350 align:start position:0% recently you could write this function without<00:09:01.980> ever<00:09:02.190> returning<00:09:02.580> true<00:09:02.790> right<00:09:03.180> so 00:09:03.350 --> 00:09:03.360 align:start position:0% without ever returning true right so 00:09:03.360 --> 00:09:05.150 align:start position:0% without ever returning true right so like<00:09:03.480> take<00:09:03.900> away<00:09:03.990> that<00:09:04.230> return<00:09:04.500> true<00:09:04.740> and<00:09:04.920> it 00:09:05.150 --> 00:09:05.160 align:start position:0% like take away that return true and it 00:09:05.160 --> 00:09:07.340 align:start position:0% like take away that return true and it would<00:09:05.250> still<00:09:05.460> like<00:09:06.150> it<00:09:06.450> would<00:09:06.630> just<00:09:06.870> put<00:09:07.320> a 00:09:07.340 --> 00:09:07.350 align:start position:0% would still like it would just put a 00:09:07.350 --> 00:09:08.540 align:start position:0% would still like it would just put a deer<00:09:07.530> on<00:09:07.560> the<00:09:07.710> sack<00:09:07.950> basically<00:09:08.400> right 00:09:08.540 --> 00:09:08.550 align:start position:0% deer on the sack basically right 00:09:08.550 --> 00:09:11.660 align:start position:0% deer on the sack basically right silently<00:09:09.140> false<00:09:10.140> and<00:09:10.470> then<00:09:10.620> between<00:09:11.070> compiler 00:09:11.660 --> 00:09:11.670 align:start position:0% silently false and then between compiler 00:09:11.670 --> 00:09:14.230 align:start position:0% silently false and then between compiler version<00:09:12.050> 4.2<00:09:13.050> two<00:09:13.200> and<00:09:13.410> four<00:09:13.590> point<00:09:13.830> two<00:09:13.980> three 00:09:14.230 --> 00:09:14.240 align:start position:0% version 4.2 two and four point two three 00:09:14.240 --> 00:09:16.850 align:start position:0% version 4.2 two and four point two three like<00:09:15.240> a<00:09:15.300> bug<00:09:15.630> was<00:09:15.840> fixed<00:09:16.080> with<00:09:16.350> a<00:09:16.380> call<00:09:16.620> data 00:09:16.850 --> 00:09:16.860 align:start position:0% like a bug was fixed with a call data 00:09:16.860 --> 00:09:19.010 align:start position:0% like a bug was fixed with a call data return<00:09:17.250> where<00:09:18.120> I<00:09:18.150> guess<00:09:18.300> like<00:09:18.480> it<00:09:18.720> was<00:09:18.840> made 00:09:19.010 --> 00:09:19.020 align:start position:0% return where I guess like it was made 00:09:19.020 --> 00:09:21.020 align:start position:0% return where I guess like it was made more<00:09:19.200> strict<00:09:19.590> so<00:09:19.950> now<00:09:20.100> those<00:09:20.310> contracts 00:09:21.020 --> 00:09:21.030 align:start position:0% more strict so now those contracts 00:09:21.030 --> 00:09:23.870 align:start position:0% more strict so now those contracts actually<00:09:21.720> returned<00:09:22.110> zero<00:09:22.590> in<00:09:22.770> under<00:09:23.460> wire 00:09:23.870 --> 00:09:23.880 align:start position:0% actually returned zero in under wire 00:09:23.880 --> 00:09:25.700 align:start position:0% actually returned zero in under wire yeah<00:09:24.210> so<00:09:24.420> the<00:09:24.570> output<00:09:24.930> area<00:09:25.260> is<00:09:25.380> cleared 00:09:25.700 --> 00:09:25.710 align:start position:0% yeah so the output area is cleared 00:09:25.710 --> 00:09:27.710 align:start position:0% yeah so the output area is cleared before<00:09:26.190> the<00:09:26.310> call<00:09:26.550> is<00:09:26.700> made<00:09:26.880> right<00:09:27.330> yeah<00:09:27.510> and 00:09:27.710 --> 00:09:27.720 align:start position:0% before the call is made right yeah and 00:09:27.720 --> 00:09:29.900 align:start position:0% before the call is made right yeah and earlier<00:09:28.170> the<00:09:28.320> output<00:09:28.650> area<00:09:28.920> was<00:09:29.100> they<00:09:29.760> input 00:09:29.900 --> 00:09:29.910 align:start position:0% earlier the output area was they input 00:09:29.910 --> 00:09:32.300 align:start position:0% earlier the output area was they input ordered<00:09:30.510> the<00:09:30.630> recited<00:09:31.080> there<00:09:31.200> and<00:09:31.650> because<00:09:32.100> so 00:09:32.300 --> 00:09:32.310 align:start position:0% ordered the recited there and because so 00:09:32.310 --> 00:09:33.500 align:start position:0% ordered the recited there and because so this<00:09:32.490> because<00:09:32.760> the<00:09:32.850> compiler<00:09:33.120> was<00:09:33.360> too 00:09:33.500 --> 00:09:33.510 align:start position:0% this because the compiler was too 00:09:33.510 --> 00:09:35.600 align:start position:0% this because the compiler was too lenient<00:09:33.690> and<00:09:34.050> now<00:09:34.170> like<00:09:34.500> within<00:09:35.130> if<00:09:35.370> you 00:09:35.600 --> 00:09:35.610 align:start position:0% lenient and now like within if you 00:09:35.610 --> 00:09:37.610 align:start position:0% lenient and now like within if you compile<00:09:36.120> a<00:09:36.420> checking<00:09:36.960> contract<00:09:37.440> that 00:09:37.610 --> 00:09:37.620 align:start position:0% compile a checking contract that 00:09:37.620 --> 00:09:39.680 align:start position:0% compile a checking contract that requires<00:09:37.860> wraps<00:09:38.850> to<00:09:38.970> require<00:09:39.270> around<00:09:39.600> the 00:09:39.680 --> 00:09:39.690 align:start position:0% requires wraps to require around the 00:09:39.690 --> 00:09:41.900 align:start position:0% requires wraps to require around the token<00:09:40.050> transfer<00:09:40.950> and<00:09:41.160> that<00:09:41.190> transfer<00:09:41.790> goes 00:09:41.900 --> 00:09:41.910 align:start position:0% token transfer and that transfer goes 00:09:41.910 --> 00:09:44.060 align:start position:0% token transfer and that transfer goes through<00:09:41.940> okay<00:09:42.360> but<00:09:42.990> it<00:09:43.110> returns<00:09:43.320> zero<00:09:43.620> now 00:09:44.060 --> 00:09:44.070 align:start position:0% through okay but it returns zero now 00:09:44.070 --> 00:09:46.520 align:start position:0% through okay but it returns zero now like<00:09:44.790> it<00:09:44.940> properly<00:09:45.360> allocates<00:09:45.780> at<00:09:45.930> zero<00:09:46.140> then 00:09:46.520 --> 00:09:46.530 align:start position:0% like it properly allocates at zero then 00:09:46.530 --> 00:09:49.010 align:start position:0% like it properly allocates at zero then the<00:09:46.860> like<00:09:47.850> the<00:09:47.970> contract<00:09:48.270> will<00:09:48.360> throw<00:09:48.630> even 00:09:49.010 --> 00:09:49.020 align:start position:0% the like the contract will throw even 00:09:49.020 --> 00:09:50.210 align:start position:0% the like the contract will throw even though<00:09:49.200> it's<00:09:49.710> actually<00:09:49.860> gone<00:09:50.160> through 00:09:50.210 --> 00:09:50.220 align:start position:0% though it's actually gone through 00:09:50.220 --> 00:09:58.270 align:start position:0% though it's actually gone through correctly<00:09:52.370> don't<00:09:56.000> quickening<00:09:57.000> here<00:09:57.240> is<00:09:57.360> the 00:09:58.270 --> 00:09:58.280 align:start position:0% correctly don't quickening here is the 00:09:58.280 --> 00:10:02.150 align:start position:0% correctly don't quickening here is the one<00:09:59.280> lines<00:09:59.700> 123<00:10:00.330> and<00:10:00.480> 124<00:10:01.080> I<00:10:01.440> think<00:10:01.770> I<00:10:01.890> can't 00:10:02.150 --> 00:10:02.160 align:start position:0% one lines 123 and 124 I think I can't 00:10:02.160 --> 00:10:04.700 align:start position:0% one lines 123 and 124 I think I can't quite<00:10:02.340> make<00:10:02.550> out<00:10:02.730> the<00:10:02.910> alignment<00:10:03.470> 124<00:10:04.470> and<00:10:04.500> 125 00:10:04.700 --> 00:10:04.710 align:start position:0% quite make out the alignment 124 and 125 00:10:04.710 --> 00:10:09.380 align:start position:0% quite make out the alignment 124 and 125 are<00:10:05.310> redundant<00:10:06.770> if<00:10:07.770> if<00:10:08.370> the<00:10:08.730> sorry 00:10:09.380 --> 00:10:09.390 align:start position:0% are redundant if if the sorry 00:10:09.390 --> 00:10:13.160 align:start position:0% are redundant if if the sorry like<00:10:10.070> 124<00:10:11.070> isn't<00:10:11.520> the<00:10:12.030> check<00:10:12.270> that<00:10:12.540> the<00:10:12.750> value 00:10:13.160 --> 00:10:13.170 align:start position:0% like 124 isn't the check that the value 00:10:13.170 --> 00:10:14.510 align:start position:0% like 124 isn't the check that the value is<00:10:13.290> less<00:10:13.440> than<00:10:13.470> the<00:10:13.620> balances<00:10:14.100> is<00:10:14.220> also 00:10:14.510 --> 00:10:14.520 align:start position:0% is less than the balances is also 00:10:14.520 --> 00:10:22.700 align:start position:0% is less than the balances is also enforced<00:10:14.910> by<00:10:15.060> safe<00:10:15.300> meth<00:10:21.530> depends<00:10:22.530> on<00:10:22.620> the 00:10:22.700 --> 00:10:22.710 align:start position:0% enforced by safe meth depends on the 00:10:22.710 --> 00:10:25.850 align:start position:0% enforced by safe meth depends on the version<00:10:22.830> of<00:10:23.040> safe<00:10:23.190> manner<00:10:23.430> using<00:10:24.410> okay<00:10:25.410> yep 00:10:25.850 --> 00:10:25.860 align:start position:0% version of safe manner using okay yep 00:10:25.860 --> 00:10:29.930 align:start position:0% version of safe manner using okay yep yep<00:10:27.320> for<00:10:28.320> the<00:10:28.410> room<00:10:28.860> to<00:10:29.070> hear<00:10:29.250> it<00:10:29.370> so<00:10:29.550> the 00:10:29.930 --> 00:10:29.940 align:start position:0% yep for the room to hear it so the 00:10:29.940 --> 00:10:33.590 align:start position:0% yep for the room to hear it so the comment<00:10:30.270> was<00:10:30.300> the<00:10:30.600> the<00:10:30.960> safe<00:10:31.350> mouth<00:10:32.600> faison 00:10:33.590 --> 00:10:33.600 align:start position:0% comment was the the safe mouth faison 00:10:33.600 --> 00:10:42.110 align:start position:0% comment was the the safe mouth faison revert<00:10:34.520> assert<00:10:35.520> as<00:10:35.790> art<00:10:36.230> right<00:10:40.910> it's<00:10:41.910> a<00:10:42.000> good 00:10:42.110 --> 00:10:42.120 align:start position:0% revert assert as art right it's a good 00:10:42.120 --> 00:10:43.940 align:start position:0% revert assert as art right it's a good question<00:10:42.330> like<00:10:42.810> it's<00:10:43.170> kind<00:10:43.380> of<00:10:43.410> a<00:10:43.500> philosophy 00:10:43.940 --> 00:10:43.950 align:start position:0% question like it's kind of a philosophy 00:10:43.950 --> 00:10:46.130 align:start position:0% question like it's kind of a philosophy question<00:10:44.340> and<00:10:44.550> are<00:10:45.120> you<00:10:45.270> using<00:10:45.540> safe<00:10:45.870> math 00:10:46.130 --> 00:10:46.140 align:start position:0% question and are you using safe math 00:10:46.140 --> 00:10:49.220 align:start position:0% question and are you using safe math because<00:10:46.500> you<00:10:46.650> believe<00:10:46.980> it<00:10:47.160> should<00:10:47.370> like<00:10:48.230> throw 00:10:49.220 --> 00:10:49.230 align:start position:0% because you believe it should like throw 00:10:49.230 --> 00:10:52.220 align:start position:0% because you believe it should like throw in<00:10:49.530> the<00:10:49.650> case<00:10:49.830> of<00:10:50.070> a<00:10:50.270> honest<00:10:51.270> mistake<00:10:51.390> like<00:10:52.050> the 00:10:52.220 --> 00:10:52.230 align:start position:0% in the case of a honest mistake like the 00:10:52.230 --> 00:10:54.590 align:start position:0% in the case of a honest mistake like the idea<00:10:52.530> that<00:10:52.590> if<00:10:53.250> say<00:10:53.580> if<00:10:53.730> a<00:10:53.850> safe<00:10:54.030> method<00:10:54.390> method 00:10:54.590 --> 00:10:54.600 align:start position:0% idea that if say if a safe method method 00:10:54.600 --> 00:10:56.720 align:start position:0% idea that if say if a safe method method ever<00:10:54.810> fails<00:10:55.140> it<00:10:55.410> represents<00:10:55.950> an<00:10:56.040> error<00:10:56.460> in<00:10:56.640> the 00:10:56.720 --> 00:10:56.730 align:start position:0% ever fails it represents an error in the 00:10:56.730 --> 00:10:59.420 align:start position:0% ever fails it represents an error in the contract<00:10:57.180> or<00:10:57.420> are<00:10:57.960> you<00:10:58.110> doing<00:10:58.410> it<00:10:58.530> because<00:10:59.220> you 00:10:59.420 --> 00:10:59.430 align:start position:0% contract or are you doing it because you 00:10:59.430 --> 00:11:01.490 align:start position:0% contract or are you doing it because you want<00:10:59.640> it<00:10:59.760> to<00:10:59.910> automatically<00:11:00.450> catch<00:11:00.690> overflows 00:11:01.490 --> 00:11:01.500 align:start position:0% want it to automatically catch overflows 00:11:01.500 --> 00:11:05.090 align:start position:0% want it to automatically catch overflows for<00:11:01.830> you<00:11:02.000> and<00:11:03.000> and<00:11:03.480> one<00:11:04.230> philosophy<00:11:04.740> leads<00:11:04.920> to 00:11:05.090 --> 00:11:05.100 align:start position:0% for you and and one philosophy leads to 00:11:05.100 --> 00:11:09.699 align:start position:0% for you and and one philosophy leads to reverse<00:11:05.400> and<00:11:05.640> the<00:11:05.700> others<00:11:05.940> were<00:11:06.060> assert 00:11:09.699 --> 00:11:09.709 align:start position:0% 00:11:09.709 --> 00:11:11.900 align:start position:0% so<00:11:10.709> the<00:11:10.860> comment<00:11:11.190> from<00:11:11.279> the<00:11:11.399> audience's<00:11:11.880> I 00:11:11.900 --> 00:11:11.910 align:start position:0% so the comment from the audience's I 00:11:11.910 --> 00:11:18.139 align:start position:0% so the comment from the audience's I remove<00:11:12.690> the<00:11:13.700> safe<00:11:14.700> math<00:11:14.970> check<00:11:15.540> on<00:11:15.779> line<00:11:17.149> 128 00:11:18.139 --> 00:11:18.149 align:start position:0% remove the safe math check on line 128 00:11:18.149 --> 00:11:23.329 align:start position:0% remove the safe math check on line 128 and<00:11:18.570> I<00:11:18.660> start<00:11:18.930> do<00:11:19.110> a<00:11:19.140> regular<00:11:19.730> -<00:11:22.010> yeah<00:11:23.010> so<00:11:23.220> these 00:11:23.329 --> 00:11:23.339 align:start position:0% and I start do a regular - yeah so these 00:11:23.339 --> 00:11:25.850 align:start position:0% and I start do a regular - yeah so these are<00:11:23.519> basically<00:11:23.850> the<00:11:23.970> same<00:11:24.209> check<00:11:24.450> and<00:11:24.860> we'll 00:11:25.850 --> 00:11:25.860 align:start position:0% are basically the same check and we'll 00:11:25.860 --> 00:11:28.280 align:start position:0% are basically the same check and we'll the<00:11:26.040> the<00:11:26.610> one<00:11:26.820> on<00:11:26.940> 129<00:11:27.540> cheeks<00:11:27.930> against 00:11:28.280 --> 00:11:28.290 align:start position:0% the the one on 129 cheeks against 00:11:28.290 --> 00:11:36.019 align:start position:0% the the one on 129 cheeks against overflow<00:11:28.769> so<00:11:29.250> 128<00:11:30.149> could<00:11:30.480> succeed<00:11:30.839> in<00:11:31.220> yeah<00:11:35.029> so 00:11:36.019 --> 00:11:36.029 align:start position:0% overflow so 128 could succeed in yeah so 00:11:36.029 --> 00:11:38.240 align:start position:0% overflow so 128 could succeed in yeah so and<00:11:36.329> one<00:11:36.690> important<00:11:37.140> stuff<00:11:37.410> to<00:11:37.680> see<00:11:37.980> that<00:11:38.160> they 00:11:38.240 --> 00:11:38.250 align:start position:0% and one important stuff to see that they 00:11:38.250 --> 00:11:40.430 align:start position:0% and one important stuff to see that they got<00:11:38.399> right<00:11:38.610> here<00:11:38.850> in<00:11:38.970> this<00:11:39.089> section<00:11:39.329> is<00:11:39.990> that 00:11:40.430 --> 00:11:40.440 align:start position:0% got right here in this section is that 00:11:40.440 --> 00:11:42.860 align:start position:0% got right here in this section is that you<00:11:40.649> do<00:11:40.829> the<00:11:41.310> subtraction<00:11:42.000> in<00:11:42.420> addition<00:11:42.779> in 00:11:42.860 --> 00:11:42.870 align:start position:0% you do the subtraction in addition in 00:11:42.870 --> 00:11:45.560 align:start position:0% you do the subtraction in addition in the<00:11:42.959> right<00:11:43.110> order<00:11:43.380> so<00:11:44.250> that<00:11:44.279> you<00:11:44.640> don't<00:11:44.820> like<00:11:45.360> I 00:11:45.560 --> 00:11:45.570 align:start position:0% the right order so that you don't like I 00:11:45.570 --> 00:11:48.920 align:start position:0% the right order so that you don't like I want<00:11:45.839> to<00:11:45.870> transfer<00:11:46.519> ten<00:11:47.519> tokens<00:11:47.970> from<00:11:48.690> myself 00:11:48.920 --> 00:11:48.930 align:start position:0% want to transfer ten tokens from myself 00:11:48.930 --> 00:11:51.139 align:start position:0% want to transfer ten tokens from myself to<00:11:49.320> myself<00:11:49.500> and<00:11:50.010> then<00:11:50.160> you<00:11:50.310> add<00:11:50.640> it<00:11:51.000> to 00:11:51.139 --> 00:11:51.149 align:start position:0% to myself and then you add it to 00:11:51.149 --> 00:11:54.710 align:start position:0% to myself and then you add it to yourself<00:11:51.570> and<00:11:51.750> then<00:11:51.870> you<00:11:52.640> tend<00:11:53.640> to<00:11:53.880> it<00:11:54.000> tell<00:11:54.600> it 00:11:54.710 --> 00:11:54.720 align:start position:0% yourself and then you tend to it tell it 00:11:54.720 --> 00:11:56.060 align:start position:0% yourself and then you tend to it tell it wrong<00:11:54.870> so<00:11:55.110> you<00:11:55.170> get<00:11:55.380> the<00:11:55.500> double 00:11:56.060 --> 00:11:56.070 align:start position:0% wrong so you get the double 00:11:56.070 --> 00:11:57.889 align:start position:0% wrong so you get the double if<00:11:56.700> you<00:11:56.850> do<00:11:56.940> it<00:11:57.029> the<00:11:57.120> other<00:11:57.149> way<00:11:57.300> around<00:11:57.570> and 00:11:57.889 --> 00:11:57.899 align:start position:0% if you do it the other way around and 00:11:57.899 --> 00:11:59.420 align:start position:0% if you do it the other way around and you<00:11:57.959> have<00:11:58.200> zero<00:11:58.380> tokens<00:11:58.890> you<00:11:59.040> can<00:11:59.190> still 00:11:59.420 --> 00:11:59.430 align:start position:0% you have zero tokens you can still 00:11:59.430 --> 00:12:05.470 align:start position:0% you have zero tokens you can still transfer<00:11:59.880> a<00:11:59.910> million<00:12:00.209> tokens<00:12:00.570> to<00:12:00.720> yourself 00:12:05.470 --> 00:12:05.480 align:start position:0% 00:12:05.480 --> 00:12:09.680 align:start position:0% all<00:12:06.480> right<00:12:06.829> let's<00:12:07.829> move<00:12:08.010> on<00:12:08.190> if<00:12:08.430> there's<00:12:09.390> any 00:12:09.680 --> 00:12:09.690 align:start position:0% all right let's move on if there's any 00:12:09.690 --> 00:12:11.930 align:start position:0% all right let's move on if there's any submissions<00:12:10.589> coming<00:12:11.430> in<00:12:11.550> while<00:12:11.730> we're 00:12:11.930 --> 00:12:11.940 align:start position:0% submissions coming in while we're 00:12:11.940 --> 00:12:18.640 align:start position:0% submissions coming in while we're talking<00:12:13.910> yeah<00:12:14.910> keep<00:12:15.240> coming<00:12:15.269> keep<00:12:15.870> coming 00:12:18.640 --> 00:12:18.650 align:start position:0% 00:12:18.650 --> 00:12:23.230 align:start position:0% [Music] 00:12:23.230 --> 00:12:23.240 align:start position:0% 00:12:23.240 --> 00:12:27.110 align:start position:0% so<00:12:24.240> it's<00:12:24.449> it's<00:12:25.079> not<00:12:25.320> a<00:12:26.089> necessarily<00:12:27.089> a 00:12:27.110 --> 00:12:27.120 align:start position:0% so it's it's not a necessarily a 00:12:27.120 --> 00:12:29.930 align:start position:0% so it's it's not a necessarily a security<00:12:27.570> issue<00:12:27.720> but<00:12:28.050> it<00:12:28.140> is<00:12:28.170> a<00:12:28.610> events<00:12:29.610> issue 00:12:29.930 --> 00:12:29.940 align:start position:0% security issue but it is a events issue 00:12:29.940 --> 00:12:32.150 align:start position:0% security issue but it is a events issue if<00:12:30.209> you<00:12:30.810> add<00:12:31.079> to<00:12:31.320> the<00:12:31.410> balance<00:12:31.709> before<00:12:32.070> you 00:12:32.150 --> 00:12:32.160 align:start position:0% if you add to the balance before you 00:12:32.160 --> 00:12:33.829 align:start position:0% if you add to the balance before you subtract<00:12:32.610> and<00:12:32.910> you<00:12:32.940> start<00:12:33.360> off<00:12:33.449> with<00:12:33.600> a<00:12:33.660> zero 00:12:33.829 --> 00:12:33.839 align:start position:0% subtract and you start off with a zero 00:12:33.839 --> 00:12:35.150 align:start position:0% subtract and you start off with a zero balance<00:12:34.079> and<00:12:34.500> you're<00:12:34.620> transferring<00:12:35.010> to 00:12:35.150 --> 00:12:35.160 align:start position:0% balance and you're transferring to 00:12:35.160 --> 00:12:37.310 align:start position:0% balance and you're transferring to yourself<00:12:35.490> then<00:12:36.269> you<00:12:36.570> add<00:12:36.690> a<00:12:36.720> million<00:12:37.019> tokens 00:12:37.310 --> 00:12:37.320 align:start position:0% yourself then you add a million tokens 00:12:37.320 --> 00:12:38.449 align:start position:0% yourself then you add a million tokens to<00:12:37.410> your<00:12:37.529> balance<00:12:37.800> and<00:12:37.949> then<00:12:38.070> you<00:12:38.130> subtract 00:12:38.449 --> 00:12:38.459 align:start position:0% to your balance and then you subtract 00:12:38.459 --> 00:12:39.710 align:start position:0% to your balance and then you subtract two<00:12:38.550> million<00:12:38.790> tokens<00:12:39.089> from<00:12:39.149> your<00:12:39.329> balance<00:12:39.510> and 00:12:39.710 --> 00:12:39.720 align:start position:0% two million tokens from your balance and 00:12:39.720 --> 00:12:41.600 align:start position:0% two million tokens from your balance and that<00:12:39.779> succeeds<00:12:40.260> and<00:12:40.589> it<00:12:41.010> emits<00:12:41.279> an<00:12:41.399> event 00:12:41.600 --> 00:12:41.610 align:start position:0% that succeeds and it emits an event 00:12:41.610 --> 00:12:43.009 align:start position:0% that succeeds and it emits an event saying<00:12:41.940> you<00:12:42.149> seen<00:12:42.329> yourself<00:12:42.449> a<00:12:42.750> million 00:12:43.009 --> 00:12:43.019 align:start position:0% saying you seen yourself a million 00:12:43.019 --> 00:12:46.160 align:start position:0% saying you seen yourself a million tokens<00:12:43.440> which<00:12:44.370> shouldn't<00:12:44.640> be<00:12:44.699> possible<00:12:45.170> but 00:12:46.160 --> 00:12:46.170 align:start position:0% tokens which shouldn't be possible but 00:12:46.170 --> 00:12:49.400 align:start position:0% tokens which shouldn't be possible but it<00:12:46.350> wasn't<00:12:46.769> there<00:12:46.980> act<00:12:47.220> also<00:12:47.880> a<00:12:48.360> case<00:12:49.140> of<00:12:49.290> one 00:12:49.400 --> 00:12:49.410 align:start position:0% it wasn't there act also a case of one 00:12:49.410 --> 00:12:52.460 align:start position:0% it wasn't there act also a case of one of<00:12:49.470> these<00:12:49.560> tokens<00:12:49.769> where<00:12:50.130> you<00:12:50.250> could<00:12:51.470> increase 00:12:52.460 --> 00:12:52.470 align:start position:0% of these tokens where you could increase 00:12:52.470 --> 00:12:57.740 align:start position:0% of these tokens where you could increase your<00:12:52.589> own<00:12:53.149> balance<00:12:55.880> so<00:12:56.880> the<00:12:57.089> consequence 00:12:57.740 --> 00:12:57.750 align:start position:0% your own balance so the consequence 00:12:57.750 --> 00:13:00.439 align:start position:0% your own balance so the consequence would<00:12:57.930> be<00:12:57.990> that<00:12:58.140> it<00:12:58.709> could<00:12:58.980> be<00:12:59.160> read<00:12:59.699> to<00:12:59.730> fake 00:13:00.439 --> 00:13:00.449 align:start position:0% would be that it could be read to fake 00:13:00.449 --> 00:13:03.650 align:start position:0% would be that it could be read to fake overflow<00:13:01.260> if<00:13:02.040> you<00:13:02.370> first<00:13:02.970> increase<00:13:03.510> the 00:13:03.650 --> 00:13:03.660 align:start position:0% overflow if you first increase the 00:13:03.660 --> 00:13:05.750 align:start position:0% overflow if you first increase the balance<00:13:03.810> and<00:13:04.230> you<00:13:05.010> if<00:13:05.220> you're<00:13:05.430> transferring 00:13:05.750 --> 00:13:05.760 align:start position:0% balance and you if you're transferring 00:13:05.760 --> 00:13:07.310 align:start position:0% balance and you if you're transferring from<00:13:06.029> you<00:13:06.180> to<00:13:06.570> yourself<00:13:06.930> then<00:13:07.170> you 00:13:07.310 --> 00:13:07.320 align:start position:0% from you to yourself then you 00:13:07.320 --> 00:13:08.810 align:start position:0% from you to yourself then you effectively<00:13:07.740> double<00:13:08.190> your<00:13:08.310> balance<00:13:08.579> and<00:13:08.730> this 00:13:08.810 --> 00:13:08.820 align:start position:0% effectively double your balance and this 00:13:08.820 --> 00:13:12.050 align:start position:0% effectively double your balance and this kind<00:13:09.060> of<00:13:09.120> our<00:13:09.240> flow<00:13:09.620> even<00:13:10.620> though<00:13:11.160> that<00:13:11.370> this 00:13:12.050 --> 00:13:12.060 align:start position:0% kind of our flow even though that this 00:13:12.060 --> 00:13:13.550 align:start position:0% kind of our flow even though that this is<00:13:12.209> impossible<00:13:12.449> because<00:13:12.990> the<00:13:13.110> total<00:13:13.290> number 00:13:13.550 --> 00:13:13.560 align:start position:0% is impossible because the total number 00:13:13.560 --> 00:13:15.949 align:start position:0% is impossible because the total number of<00:13:13.589> tokens<00:13:13.829> is<00:13:14.250> rather<00:13:14.640> than<00:13:14.850> maximum<00:13:15.569> value 00:13:15.949 --> 00:13:15.959 align:start position:0% of tokens is rather than maximum value 00:13:15.959 --> 00:13:17.660 align:start position:0% of tokens is rather than maximum value but<00:13:16.319> I<00:13:16.440> wanted<00:13:16.770> to<00:13:16.860> comment<00:13:17.069> about<00:13:17.370> the<00:13:17.520> safe 00:13:17.660 --> 00:13:17.670 align:start position:0% but I wanted to comment about the safe 00:13:17.670 --> 00:13:21.610 align:start position:0% but I wanted to comment about the safe Martin<00:13:17.880> fermentation<00:13:18.540> actually<00:13:19.470> it's<00:13:19.620> um 00:13:21.610 --> 00:13:21.620 align:start position:0% Martin fermentation actually it's um 00:13:21.620 --> 00:13:24.800 align:start position:0% Martin fermentation actually it's um that<00:13:22.620> style<00:13:22.950> there<00:13:23.880> I<00:13:24.150> mean<00:13:24.480> this<00:13:24.600> one 00:13:24.800 --> 00:13:24.810 align:start position:0% that style there I mean this one 00:13:24.810 --> 00:13:28.490 align:start position:0% that style there I mean this one implementation<00:13:25.080> top<00:13:26.240> because<00:13:27.240> it<00:13:27.690> allows<00:13:28.170> our 00:13:28.490 --> 00:13:28.500 align:start position:0% implementation top because it allows our 00:13:28.500 --> 00:13:31.730 align:start position:0% implementation top because it allows our flow<00:13:28.860> actually<00:13:29.010> to<00:13:29.510> happen<00:13:30.510> and<00:13:30.750> then<00:13:31.440> try<00:13:31.710> to 00:13:31.730 --> 00:13:31.740 align:start position:0% flow actually to happen and then try to 00:13:31.740 --> 00:13:33.830 align:start position:0% flow actually to happen and then try to detect<00:13:32.100> it<00:13:32.280> off<00:13:32.370> the<00:13:32.490> worse<00:13:32.610> no<00:13:33.060> not<00:13:33.330> this<00:13:33.480> but 00:13:33.830 --> 00:13:33.840 align:start position:0% detect it off the worse no not this but 00:13:33.840 --> 00:13:36.350 align:start position:0% detect it off the worse no not this but the<00:13:34.110> implementation<00:13:34.320> of<00:13:34.770> yeah<00:13:35.250> safe<00:13:36.120> month 00:13:36.350 --> 00:13:36.360 align:start position:0% the implementation of yeah safe month 00:13:36.360 --> 00:13:39.590 align:start position:0% the implementation of yeah safe month right<00:13:36.600> because<00:13:36.960> it's<00:13:37.790> heavily<00:13:38.790> relies<00:13:39.060> on<00:13:39.330> the 00:13:39.590 --> 00:13:39.600 align:start position:0% right because it's heavily relies on the 00:13:39.600 --> 00:13:41.630 align:start position:0% right because it's heavily relies on the particular<00:13:40.050> behavior<00:13:40.470> of<00:13:40.650> overflow<00:13:41.040> which 00:13:41.630 --> 00:13:41.640 align:start position:0% particular behavior of overflow which 00:13:41.640 --> 00:13:43.820 align:start position:0% particular behavior of overflow which particular<00:13:42.120> one<00:13:42.300> we<00:13:42.630> talked<00:13:42.810> about<00:13:42.900> for 00:13:43.820 --> 00:13:43.830 align:start position:0% particular one we talked about for 00:13:43.830 --> 00:13:46.460 align:start position:0% particular one we talked about for example<00:13:44.160> this<00:13:44.250> one<00:13:44.540> multiplication<00:13:45.540> right<00:13:46.050> so 00:13:46.460 --> 00:13:46.470 align:start position:0% example this one multiplication right so 00:13:46.470 --> 00:13:49.430 align:start position:0% example this one multiplication right so it<00:13:46.620> first<00:13:46.920> allows<00:13:47.720> other<00:13:48.720> flow<00:13:48.960> to<00:13:49.020> happen 00:13:49.430 --> 00:13:49.440 align:start position:0% it first allows other flow to happen 00:13:49.440 --> 00:13:52.520 align:start position:0% it first allows other flow to happen client<00:13:50.340> 58<00:13:50.730> right<00:13:51.030> and<00:13:51.330> then<00:13:51.900> tries<00:13:52.140> to<00:13:52.260> detect 00:13:52.520 --> 00:13:52.530 align:start position:0% client 58 right and then tries to detect 00:13:52.530 --> 00:13:55.280 align:start position:0% client 58 right and then tries to detect it<00:13:52.830> afterwards<00:13:53.460> heavily<00:13:54.450> relying<00:13:54.750> on<00:13:54.930> what 00:13:55.280 --> 00:13:55.290 align:start position:0% it afterwards heavily relying on what 00:13:55.290 --> 00:13:57.770 align:start position:0% it afterwards heavily relying on what exact<00:13:55.650> result<00:13:55.980> so<00:13:56.130> it's<00:13:56.490> obvious<00:13:56.970> that<00:13:57.330> if<00:13:57.510> I<00:13:57.720> / 00:13:57.770 --> 00:13:57.780 align:start position:0% exact result so it's obvious that if I / 00:13:57.780 --> 00:14:01.310 align:start position:0% exact result so it's obvious that if I / 14<00:13:58.200> happened<00:13:58.620> that<00:13:59.010> at<00:13:59.490> Lyon<00:13:59.790> 59<00:14:00.480> everything 00:14:01.310 --> 00:14:01.320 align:start position:0% 14 happened that at Lyon 59 everything 00:14:01.320 --> 00:14:03.560 align:start position:0% 14 happened that at Lyon 59 everything will<00:14:01.470> be<00:14:01.560> fine<00:14:01.770> but<00:14:02.130> the<00:14:02.970> opposite<00:14:03.390> is<00:14:03.450> not 00:14:03.560 --> 00:14:03.570 align:start position:0% will be fine but the opposite is not 00:14:03.570 --> 00:14:06.440 align:start position:0% will be fine but the opposite is not obvious<00:14:04.080> I<00:14:04.290> mean<00:14:04.560> it's<00:14:04.740> hard<00:14:05.550> to<00:14:05.880> prove<00:14:06.090> that 00:14:06.440 --> 00:14:06.450 align:start position:0% obvious I mean it's hard to prove that 00:14:06.450 --> 00:14:08.480 align:start position:0% obvious I mean it's hard to prove that if<00:14:06.900> ever<00:14:07.170> for<00:14:07.200> actually<00:14:07.860> happened<00:14:08.190> then 00:14:08.480 --> 00:14:08.490 align:start position:0% if ever for actually happened then 00:14:08.490 --> 00:14:12.740 align:start position:0% if ever for actually happened then condition<00:14:09.060> at<00:14:09.150> 59<00:14:09.810> will<00:14:10.050> be<00:14:10.910> violated<00:14:11.910> it's 00:14:12.740 --> 00:14:12.750 align:start position:0% condition at 59 will be violated it's 00:14:12.750 --> 00:14:14.720 align:start position:0% condition at 59 will be violated it's not<00:14:12.930> that<00:14:13.080> easy<00:14:13.290> to<00:14:13.980> understand<00:14:14.400> and<00:14:14.580> do<00:14:14.640> you 00:14:14.720 --> 00:14:14.730 align:start position:0% not that easy to understand and do you 00:14:14.730 --> 00:14:16.100 align:start position:0% not that easy to understand and do you know<00:14:14.850> you<00:14:15.120> need<00:14:15.330> to<00:14:15.450> know<00:14:15.600> the<00:14:15.810> particular 00:14:16.100 --> 00:14:16.110 align:start position:0% know you need to know the particular 00:14:16.110 --> 00:14:18.170 align:start position:0% know you need to know the particular behavior<00:14:16.620> of<00:14:16.740> however<00:14:17.160> flow<00:14:17.370> works<00:14:17.640> I<00:14:17.910> mean 00:14:18.170 --> 00:14:18.180 align:start position:0% behavior of however flow works I mean 00:14:18.180 --> 00:14:20.770 align:start position:0% behavior of however flow works I mean what<00:14:18.480> exact<00:14:18.810> result<00:14:19.140> will<00:14:19.410> overflow<00:14:19.980> return 00:14:20.770 --> 00:14:20.780 align:start position:0% what exact result will overflow return 00:14:20.780 --> 00:14:23.750 align:start position:0% what exact result will overflow return right<00:14:21.780> so<00:14:22.710> it's<00:14:22.890> better<00:14:23.070> to<00:14:23.190> check<00:14:23.520> before 00:14:23.750 --> 00:14:23.760 align:start position:0% right so it's better to check before 00:14:23.760 --> 00:14:26.150 align:start position:0% right so it's better to check before doing<00:14:24.750> an<00:14:24.810> actual<00:14:25.050> multiplication<00:14:25.770> to<00:14:25.950> check 00:14:26.150 --> 00:14:26.160 align:start position:0% doing an actual multiplication to check 00:14:26.160 --> 00:14:31.310 align:start position:0% doing an actual multiplication to check that<00:14:27.440> is<00:14:28.440> easy<00:14:28.740> check<00:14:29.070> I<00:14:29.360> mean<00:14:30.360> you<00:14:31.170> need<00:14:31.260> to 00:14:31.310 --> 00:14:31.320 align:start position:0% that is easy check I mean you need to 00:14:31.320 --> 00:14:33.770 align:start position:0% that is easy check I mean you need to define<00:14:31.800> marks<00:14:32.430> a<00:14:32.520> lot<00:14:32.610> value<00:14:32.820> by<00:14:33.120> one<00:14:33.330> argument 00:14:33.770 --> 00:14:33.780 align:start position:0% define marks a lot value by one argument 00:14:33.780 --> 00:14:36.770 align:start position:0% define marks a lot value by one argument and<00:14:33.930> compared<00:14:34.230> to<00:14:34.320> another<00:14:34.910> and<00:14:35.910> the<00:14:36.630> same 00:14:36.770 --> 00:14:36.780 align:start position:0% and compared to another and the same 00:14:36.780 --> 00:14:40.490 align:start position:0% and compared to another and the same problem<00:14:37.050> I<00:14:37.110> think<00:14:37.170> with<00:14:37.410> addition<00:14:39.320> but<00:14:40.320> not 00:14:40.490 --> 00:14:40.500 align:start position:0% problem I think with addition but not 00:14:40.500 --> 00:14:44.350 align:start position:0% problem I think with addition but not with<00:14:40.650> subtraction<00:14:40.920> subtraction<00:14:41.130> is<00:14:41.460> okay<00:14:41.640> but 00:14:44.350 --> 00:14:44.360 align:start position:0% 00:14:44.360 --> 00:14:47.960 align:start position:0% like<00:14:45.360> from<00:14:45.600> a<00:14:45.690> practical<00:14:46.200> point<00:14:46.560> of<00:14:46.830> view<00:14:46.970> no 00:14:47.960 --> 00:14:47.970 align:start position:0% like from a practical point of view no 00:14:47.970 --> 00:14:50.000 align:start position:0% like from a practical point of view no actually<00:14:48.540> the<00:14:48.780> other<00:14:49.200> flow<00:14:49.470> behavior<00:14:49.650> is 00:14:50.000 --> 00:14:50.010 align:start position:0% actually the other flow behavior is 00:14:50.010 --> 00:14:52.340 align:start position:0% actually the other flow behavior is predictable<00:14:50.160> at<00:14:50.700> least<00:14:50.880> in<00:14:51.030> nvm<00:14:51.540> but<00:14:52.080> it's<00:14:52.230> not 00:14:52.340 --> 00:14:52.350 align:start position:0% predictable at least in nvm but it's not 00:14:52.350 --> 00:14:54.740 align:start position:0% predictable at least in nvm but it's not that<00:14:52.500> predictable<00:14:52.770> in<00:14:53.250> solidity<00:14:53.750> right 00:14:54.740 --> 00:14:54.750 align:start position:0% that predictable in solidity right 00:14:54.750 --> 00:14:56.420 align:start position:0% that predictable in solidity right because<00:14:55.080> for<00:14:55.260> example<00:14:55.350> the<00:14:55.740> division<00:14:56.070> by<00:14:56.190> zero 00:14:56.420 --> 00:14:56.430 align:start position:0% because for example the division by zero 00:14:56.430 --> 00:14:58.700 align:start position:0% because for example the division by zero behavior<00:14:56.910> already<00:14:57.900> changed<00:14:58.260> in<00:14:58.350> solidity 00:14:58.700 --> 00:14:58.710 align:start position:0% behavior already changed in solidity 00:14:58.710 --> 00:15:01.310 align:start position:0% behavior already changed in solidity while<00:14:58.980> isn't<00:14:59.340> change<00:14:59.670> in<00:14:59.910> Abraham<00:15:00.360> right<00:15:01.110> and 00:15:01.310 --> 00:15:01.320 align:start position:0% while isn't change in Abraham right and 00:15:01.320 --> 00:15:04.040 align:start position:0% while isn't change in Abraham right and so<00:15:01.770> we<00:15:01.980> can't<00:15:02.190> guarantee<00:15:03.150> that<00:15:03.450> overflow 00:15:04.040 --> 00:15:04.050 align:start position:0% so we can't guarantee that overflow 00:15:04.050 --> 00:15:05.630 align:start position:0% so we can't guarantee that overflow behavior<00:15:04.440> will<00:15:04.620> not<00:15:04.770> change<00:15:05.010> in<00:15:05.160> solidity<00:15:05.520> in 00:15:05.630 --> 00:15:05.640 align:start position:0% behavior will not change in solidity in 00:15:05.640 --> 00:15:07.880 align:start position:0% behavior will not change in solidity in the<00:15:05.730> future<00:15:06.090> despite<00:15:06.990> it<00:15:07.170> in<00:15:07.290> EVM<00:15:07.650> and<00:15:07.800> will 00:15:07.880 --> 00:15:07.890 align:start position:0% the future despite it in EVM and will 00:15:07.890 --> 00:15:10.400 align:start position:0% the future despite it in EVM and will stay<00:15:08.100> the<00:15:08.220> same<00:15:08.400> but<00:15:08.610> here<00:15:08.880> we<00:15:09.080> rely<00:15:10.080> on<00:15:10.110> the 00:15:10.400 --> 00:15:10.410 align:start position:0% stay the same but here we rely on the 00:15:10.410 --> 00:15:13.130 align:start position:0% stay the same but here we rely on the particular<00:15:10.800> other<00:15:11.310> blow<00:15:11.490> behavior<00:15:12.140> instead 00:15:13.130 --> 00:15:13.140 align:start position:0% particular other blow behavior instead 00:15:13.140 --> 00:15:16.250 align:start position:0% particular other blow behavior instead of<00:15:13.350> preventing<00:15:13.650> other<00:15:14.220> flow<00:15:14.430> at<00:15:14.550> all<00:15:14.700> and<00:15:15.540> so 00:15:16.250 --> 00:15:16.260 align:start position:0% of preventing other flow at all and so 00:15:16.260 --> 00:15:18.380 align:start position:0% of preventing other flow at all and so in<00:15:16.680> terms<00:15:17.010> of<00:15:17.130> gas<00:15:17.310> cost<00:15:17.520> it<00:15:17.760> will<00:15:17.910> be<00:15:18.030> the<00:15:18.150> same 00:15:18.380 --> 00:15:18.390 align:start position:0% in terms of gas cost it will be the same 00:15:18.390 --> 00:15:20.780 align:start position:0% in terms of gas cost it will be the same I<00:15:18.660> mean<00:15:18.870> preventing<00:15:19.290> overflow<00:15:19.680> or<00:15:19.920> detecting 00:15:20.780 --> 00:15:20.790 align:start position:0% I mean preventing overflow or detecting 00:15:20.790 --> 00:15:32.420 align:start position:0% I mean preventing overflow or detecting it<00:15:21.000> afterwards 00:15:32.420 --> 00:15:32.430 align:start position:0% 00:15:32.430 --> 00:15:35.480 align:start position:0% so<00:15:33.430> I<00:15:33.460> wanted<00:15:33.910> to<00:15:34.030> point<00:15:34.180> out<00:15:34.390> something<00:15:34.630> that 00:15:35.480 --> 00:15:35.490 align:start position:0% so I wanted to point out something that 00:15:35.490 --> 00:15:38.580 align:start position:0% so I wanted to point out something that transfer<00:15:36.490> from<00:15:36.670> isn't<00:15:37.210> doing<00:15:37.510> which<00:15:37.930> is<00:15:38.230> the 00:15:38.580 --> 00:15:38.590 align:start position:0% transfer from isn't doing which is the 00:15:38.590 --> 00:15:40.170 align:start position:0% transfer from isn't doing which is the what<00:15:38.980> I<00:15:39.010> consider<00:15:39.460> at<00:15:39.580> least<00:15:39.610> the<00:15:39.940> anti 00:15:40.170 --> 00:15:40.180 align:start position:0% what I consider at least the anti 00:15:40.180 --> 00:15:42.840 align:start position:0% what I consider at least the anti passion<00:15:40.540> of<00:15:40.690> requiring<00:15:41.140> sorry<00:15:42.070> not<00:15:42.430> transfer 00:15:42.840 --> 00:15:42.850 align:start position:0% passion of requiring sorry not transfer 00:15:42.850 --> 00:15:46.170 align:start position:0% passion of requiring sorry not transfer from<00:15:43.030> approve<00:15:43.810> of<00:15:44.310> requiring<00:15:45.310> someone<00:15:45.910> to<00:15:46.000> sit 00:15:46.170 --> 00:15:46.180 align:start position:0% from approve of requiring someone to sit 00:15:46.180 --> 00:15:47.880 align:start position:0% from approve of requiring someone to sit there<00:15:46.330> approvals<00:15:46.720> to<00:15:46.900> zero<00:15:47.110> before<00:15:47.620> they<00:15:47.740> can 00:15:47.880 --> 00:15:47.890 align:start position:0% there approvals to zero before they can 00:15:47.890 --> 00:15:50.250 align:start position:0% there approvals to zero before they can set<00:15:48.070> them<00:15:48.220> to<00:15:48.340> another<00:15:48.490> value<00:15:48.990> that<00:15:49.990> was 00:15:50.250 --> 00:15:50.260 align:start position:0% set them to another value that was 00:15:50.260 --> 00:15:53.520 align:start position:0% set them to another value that was mooted<00:15:50.710> in<00:15:51.000> result<00:15:52.000> fright<00:15:52.390> of<00:15:52.420> the<00:15:52.990> the<00:15:53.380> issue 00:15:53.520 --> 00:15:53.530 align:start position:0% mooted in result fright of the the issue 00:15:53.530 --> 00:15:56.310 align:start position:0% mooted in result fright of the the issue with<00:15:53.950> sort<00:15:54.940> of<00:15:55.030> front<00:15:55.870> running<00:15:55.960> with 00:15:56.310 --> 00:15:56.320 align:start position:0% with sort of front running with 00:15:56.320 --> 00:15:58.920 align:start position:0% with sort of front running with transaction<00:15:56.860> approvals<00:15:57.390> and<00:15:58.390> in<00:15:58.600> my<00:15:58.810> opinion 00:15:58.920 --> 00:15:58.930 align:start position:0% transaction approvals and in my opinion 00:15:58.930 --> 00:16:01.530 align:start position:0% transaction approvals and in my opinion the<00:15:59.470> the<00:16:00.280> correct<00:16:00.550> way<00:16:00.790> to<00:16:00.820> handle<00:16:01.030> that<00:16:01.300> is 00:16:01.530 --> 00:16:01.540 align:start position:0% the the correct way to handle that is 00:16:01.540 --> 00:16:04.440 align:start position:0% the the correct way to handle that is for<00:16:01.900> end-user<00:16:02.440> clients<00:16:02.980> to<00:16:03.160> seem<00:16:03.400> to<00:16:03.610> send<00:16:04.330> an 00:16:04.440 --> 00:16:04.450 align:start position:0% for end-user clients to seem to send an 00:16:04.450 --> 00:16:06.330 align:start position:0% for end-user clients to seem to send an approval<00:16:04.840> to<00:16:05.020> set<00:16:05.200> it<00:16:05.290> to<00:16:05.410> zero<00:16:05.590> first<00:16:05.920> and 00:16:06.330 --> 00:16:06.340 align:start position:0% approval to set it to zero first and 00:16:06.340 --> 00:16:08.280 align:start position:0% approval to set it to zero first and then<00:16:06.460> just<00:16:06.670> to<00:16:06.850> reset<00:16:07.150> it<00:16:07.330> not<00:16:07.600> for<00:16:07.810> contracts 00:16:08.280 --> 00:16:08.290 align:start position:0% then just to reset it not for contracts 00:16:08.290 --> 00:16:12.060 align:start position:0% then just to reset it not for contracts to<00:16:08.350> enforce<00:16:08.650> it<00:16:08.860> because<00:16:10.410> give<00:16:11.410> some<00:16:11.590> context 00:16:12.060 --> 00:16:12.070 align:start position:0% to enforce it because give some context 00:16:12.070 --> 00:16:14.190 align:start position:0% to enforce it because give some context on<00:16:12.160> that<00:16:12.310> so<00:16:12.520> it's<00:16:12.910> basically<00:16:13.240> if<00:16:13.420> if<00:16:13.750> Nick 00:16:14.190 --> 00:16:14.200 align:start position:0% on that so it's basically if if Nick 00:16:14.200 --> 00:16:16.230 align:start position:0% on that so it's basically if if Nick approves<00:16:14.740> that<00:16:15.070> I<00:16:15.220> can<00:16:15.550> use<00:16:15.760> ten<00:16:16.060> of<00:16:16.180> his 00:16:16.230 --> 00:16:16.240 align:start position:0% approves that I can use ten of his 00:16:16.240 --> 00:16:19.380 align:start position:0% approves that I can use ten of his tokens<00:16:16.720> and<00:16:17.710> then<00:16:18.280> at<00:16:18.430> some<00:16:18.580> later<00:16:18.760> point<00:16:18.910> he 00:16:19.380 --> 00:16:19.390 align:start position:0% tokens and then at some later point he 00:16:19.390 --> 00:16:21.210 align:start position:0% tokens and then at some later point he says<00:16:19.750> no<00:16:19.930> Martin<00:16:20.350> you<00:16:20.410> should<00:16:20.590> only<00:16:20.710> be<00:16:21.130> able 00:16:21.210 --> 00:16:21.220 align:start position:0% says no Martin you should only be able 00:16:21.220 --> 00:16:23.790 align:start position:0% says no Martin you should only be able to<00:16:21.340> use<00:16:21.520> spent<00:16:22.240> five<00:16:22.480> of<00:16:22.630> them<00:16:22.780> and<00:16:23.020> I<00:16:23.260> see<00:16:23.530> his 00:16:23.790 --> 00:16:23.800 align:start position:0% to use spent five of them and I see his 00:16:23.800 --> 00:16:26.430 align:start position:0% to use spent five of them and I see his approval<00:16:24.640> is<00:16:25.180> on<00:16:25.480> the<00:16:25.630> network<00:16:25.990> for<00:16:26.200> five 00:16:26.430 --> 00:16:26.440 align:start position:0% approval is on the network for five 00:16:26.440 --> 00:16:28.800 align:start position:0% approval is on the network for five tokens<00:16:26.770> so<00:16:27.520> then<00:16:27.760> I<00:16:27.850> quickly<00:16:28.120> grabbed<00:16:28.480> the<00:16:28.600> ten 00:16:28.800 --> 00:16:28.810 align:start position:0% tokens so then I quickly grabbed the ten 00:16:28.810 --> 00:16:31.590 align:start position:0% tokens so then I quickly grabbed the ten tokens<00:16:29.020> and<00:16:29.620> his<00:16:30.400> approval<00:16:30.760> comes<00:16:30.880> in<00:16:31.120> and<00:16:31.510> I 00:16:31.590 --> 00:16:31.600 align:start position:0% tokens and his approval comes in and I 00:16:31.600 --> 00:16:33.030 align:start position:0% tokens and his approval comes in and I can<00:16:31.750> go<00:16:31.840> up<00:16:31.870> another<00:16:32.050> five<00:16:32.320> tokens<00:16:32.500> then<00:16:32.800> I<00:16:32.890> got 00:16:33.030 --> 00:16:33.040 align:start position:0% can go up another five tokens then I got 00:16:33.040 --> 00:16:36.000 align:start position:0% can go up another five tokens then I got 15<00:16:33.370> that's<00:16:33.850> and<00:16:34.540> the<00:16:35.170> correct<00:16:35.620> way<00:16:35.680> to<00:16:35.770> handle 00:16:36.000 --> 00:16:36.010 align:start position:0% 15 that's and the correct way to handle 00:16:36.010 --> 00:16:38.490 align:start position:0% 15 that's and the correct way to handle that<00:16:36.220> is<00:16:36.280> either<00:16:36.550> with<00:16:36.960> first<00:16:37.960> sitting<00:16:38.350> there 00:16:38.490 --> 00:16:38.500 align:start position:0% that is either with first sitting there 00:16:38.500 --> 00:16:39.990 align:start position:0% that is either with first sitting there the<00:16:38.800> app<00:16:38.950> either<00:16:39.280> first<00:16:39.580> setting<00:16:39.910> the 00:16:39.990 --> 00:16:40.000 align:start position:0% the app either first setting the 00:16:40.000 --> 00:16:41.790 align:start position:0% the app either first setting the approval<00:16:40.330> to<00:16:40.420> zero<00:16:40.630> and<00:16:40.870> then<00:16:40.990> back<00:16:41.230> but<00:16:41.620> not 00:16:41.790 --> 00:16:41.800 align:start position:0% approval to zero and then back but not 00:16:41.800 --> 00:16:44.460 align:start position:0% approval to zero and then back but not for<00:16:42.130> the<00:16:42.450> token<00:16:43.450> contract<00:16:43.990> to<00:16:44.050> enforce<00:16:44.380> that 00:16:44.460 --> 00:16:44.470 align:start position:0% for the token contract to enforce that 00:16:44.470 --> 00:16:46.620 align:start position:0% for the token contract to enforce that because<00:16:44.980> there<00:16:45.130> are<00:16:45.250> for<00:16:45.460> instance<00:16:45.630> smart 00:16:46.620 --> 00:16:46.630 align:start position:0% because there are for instance smart 00:16:46.630 --> 00:16:48.090 align:start position:0% because there are for instance smart contracts<00:16:47.140> that<00:16:47.350> use<00:16:47.470> the<00:16:47.680> approvals 00:16:48.090 --> 00:16:48.100 align:start position:0% contracts that use the approvals 00:16:48.100 --> 00:16:49.680 align:start position:0% contracts that use the approvals mechanism<00:16:48.610> they're<00:16:48.850> doing<00:16:49.090> that<00:16:49.210> atomically 00:16:49.680 --> 00:16:49.690 align:start position:0% mechanism they're doing that atomically 00:16:49.690 --> 00:16:51.150 align:start position:0% mechanism they're doing that atomically in<00:16:49.870> a<00:16:49.930> single<00:16:50.230> transaction<00:16:50.530> so<00:16:50.920> they're<00:16:51.040> not 00:16:51.150 --> 00:16:51.160 align:start position:0% in a single transaction so they're not 00:16:51.160 --> 00:16:53.370 align:start position:0% in a single transaction so they're not vulnerable<00:16:51.430> to<00:16:51.790> this<00:16:52.030> race<00:16:52.270> condition<00:16:52.780> but 00:16:53.370 --> 00:16:53.380 align:start position:0% vulnerable to this race condition but 00:16:53.380 --> 00:16:54.870 align:start position:0% vulnerable to this race condition but they<00:16:53.530> will<00:16:53.680> nevertheless<00:16:53.950> be<00:16:53.980> broken<00:16:54.670> by<00:16:54.850> a 00:16:54.870 --> 00:16:54.880 align:start position:0% they will nevertheless be broken by a 00:16:54.880 --> 00:16:56.940 align:start position:0% they will nevertheless be broken by a token<00:16:55.330> that<00:16:55.360> does<00:16:55.720> this<00:16:55.930> and<00:16:56.230> possibly 00:16:56.940 --> 00:16:56.950 align:start position:0% token that does this and possibly 00:16:56.950 --> 00:17:00.000 align:start position:0% token that does this and possibly irrevocably<00:16:57.880> broken<00:16:58.360> I<00:16:58.540> mean<00:16:59.530> they're<00:16:59.710> the 00:17:00.000 --> 00:17:00.010 align:start position:0% irrevocably broken I mean they're the 00:17:00.010 --> 00:17:01.710 align:start position:0% irrevocably broken I mean they're the contractor<00:17:00.430> has<00:17:00.550> increase<00:17:01.030> approval<00:17:01.480> on<00:17:01.600> the 00:17:01.710 --> 00:17:01.720 align:start position:0% contractor has increase approval on the 00:17:01.720 --> 00:17:03.900 align:start position:0% contractor has increase approval on the role<00:17:02.410> but<00:17:02.590> then<00:17:02.710> it<00:17:02.830> also<00:17:02.950> has<00:17:03.130> approve<00:17:03.520> I<00:17:03.700> mean 00:17:03.900 --> 00:17:03.910 align:start position:0% role but then it also has approve I mean 00:17:03.910 --> 00:17:05.550 align:start position:0% role but then it also has approve I mean so<00:17:04.449> it<00:17:04.569> would<00:17:04.720> have<00:17:04.780> been<00:17:04.900> great<00:17:05.050> to<00:17:05.079> just<00:17:05.350> know 00:17:05.550 --> 00:17:05.560 align:start position:0% so it would have been great to just know 00:17:05.560 --> 00:17:08.069 align:start position:0% so it would have been great to just know how<00:17:05.709> to<00:17:05.770> prove<00:17:06.189> then<00:17:06.819> it<00:17:06.939> wouldn't<00:17:07.150> be<00:17:07.300> a<00:17:07.329> c20 00:17:08.069 --> 00:17:08.079 align:start position:0% how to prove then it wouldn't be a c20 00:17:08.079 --> 00:17:10.650 align:start position:0% how to prove then it wouldn't be a c20 of<00:17:08.199> course<00:17:08.910> so<00:17:09.910> there's<00:17:10.089> an<00:17:10.209> increase 00:17:10.650 --> 00:17:10.660 align:start position:0% of course so there's an increase 00:17:10.660 --> 00:17:12.600 align:start position:0% of course so there's an increase approval<00:17:11.110> is<00:17:11.260> that<00:17:11.470> standardized<00:17:12.100> in<00:17:12.400> a<00:17:12.430> way 00:17:12.600 --> 00:17:12.610 align:start position:0% approval is that standardized in a way 00:17:12.610 --> 00:17:16.170 align:start position:0% approval is that standardized in a way not<00:17:13.150> really<00:17:13.569> it's<00:17:14.230> a<00:17:14.319> de<00:17:14.530> facto<00:17:14.560> standard<00:17:15.180> it 00:17:16.170 --> 00:17:16.180 align:start position:0% not really it's a de facto standard it 00:17:16.180 --> 00:17:29.010 align:start position:0% not really it's a de facto standard it was<00:17:16.329> an<00:17:16.480> audience<00:17:16.810> question<00:17:17.050> -<00:17:27.720> yes<00:17:28.720> and 00:17:29.010 --> 00:17:29.020 align:start position:0% was an audience question - yes and 00:17:29.020 --> 00:17:33.810 align:start position:0% was an audience question - yes and nothing<00:17:29.650> can<00:17:30.040> stop<00:17:30.220> you<00:17:30.370> from<00:17:30.400> doing<00:17:30.580> that<00:17:32.820> it 00:17:33.810 --> 00:17:33.820 align:start position:0% nothing can stop you from doing that it 00:17:33.820 --> 00:17:36.120 align:start position:0% nothing can stop you from doing that it prevents<00:17:34.240> if<00:17:34.450> it<00:17:34.840> was<00:17:35.110> ten<00:17:35.470> and<00:17:35.740> I'm<00:17:35.830> sitting 00:17:36.120 --> 00:17:36.130 align:start position:0% prevents if it was ten and I'm sitting 00:17:36.130 --> 00:17:38.220 align:start position:0% prevents if it was ten and I'm sitting into<00:17:36.250> five<00:17:36.550> then<00:17:37.420> without<00:17:37.750> loss<00:17:38.080> mitigation 00:17:38.220 --> 00:17:38.230 align:start position:0% into five then without loss mitigation 00:17:38.230 --> 00:17:39.900 align:start position:0% into five then without loss mitigation you<00:17:38.740> could<00:17:38.890> spend<00:17:39.070> a<00:17:39.160> total<00:17:39.430> of<00:17:39.520> fifteen 00:17:39.900 --> 00:17:39.910 align:start position:0% you could spend a total of fifteen 00:17:39.910 --> 00:17:40.649 align:start position:0% you could spend a total of fifteen because<00:17:40.270> you<00:17:40.360> could 00:17:40.649 --> 00:17:40.659 align:start position:0% because you could 00:17:40.659 --> 00:17:42.719 align:start position:0% because you could the<00:17:40.840> teen<00:17:41.049> and<00:17:41.320> then<00:17:41.739> I<00:17:41.830> reappeared<00:17:42.369> you<00:17:42.519> for 00:17:42.719 --> 00:17:42.729 align:start position:0% the teen and then I reappeared you for 00:17:42.729 --> 00:17:45.269 align:start position:0% the teen and then I reappeared you for five<00:17:42.940> and<00:17:43.330> they<00:17:43.690> used<00:17:43.840> to<00:17:43.869> be<00:17:43.929> m25<00:17:44.320> it<00:17:45.159> also 00:17:45.269 --> 00:17:45.279 align:start position:0% five and they used to be m25 it also 00:17:45.279 --> 00:17:46.259 align:start position:0% five and they used to be m25 it also prevents<00:17:45.700> you<00:17:45.789> from<00:17:45.820> the<00:17:45.999> other<00:17:46.119> direction 00:17:46.259 --> 00:17:46.269 align:start position:0% prevents you from the other direction 00:17:46.269 --> 00:17:48.570 align:start position:0% prevents you from the other direction even<00:17:46.779> are<00:17:47.049> you<00:17:47.229> approved<00:17:47.590> for<00:17:47.769> ten<00:17:47.950> I<00:17:48.159> changed 00:17:48.570 --> 00:17:48.580 align:start position:0% even are you approved for ten I changed 00:17:48.580 --> 00:17:50.729 align:start position:0% even are you approved for ten I changed it<00:17:48.759> to<00:17:48.789> approve<00:17:49.269> you<00:17:49.359> for<00:17:49.509> 20<00:17:49.779> in<00:17:49.989> this<00:17:50.499> scheme 00:17:50.729 --> 00:17:50.739 align:start position:0% it to approve you for 20 in this scheme 00:17:50.739 --> 00:17:51.899 align:start position:0% it to approve you for 20 in this scheme you<00:17:50.830> could<00:17:50.950> take<00:17:51.070> a<00:17:51.099> 30<00:17:51.369> right<00:17:51.669> because<00:17:51.820> you 00:17:51.899 --> 00:17:51.909 align:start position:0% you could take a 30 right because you 00:17:51.909 --> 00:17:53.460 align:start position:0% you could take a 30 right because you take<00:17:52.059> that<00:17:52.119> initial<00:17:52.389> 10<00:17:52.599> and<00:17:52.929> then<00:17:53.349> when<00:17:53.440> I 00:17:53.460 --> 00:17:53.470 align:start position:0% take that initial 10 and then when I 00:17:53.470 --> 00:17:54.899 align:start position:0% take that initial 10 and then when I bump<00:17:53.679> it<00:17:53.739> up<00:17:53.799> to<00:17:53.859> 20<00:17:54.190> you're<00:17:54.429> actually<00:17:54.729> able<00:17:54.789> to 00:17:54.899 --> 00:17:54.909 align:start position:0% bump it up to 20 you're actually able to 00:17:54.909 --> 00:18:02.930 align:start position:0% bump it up to 20 you're actually able to so<00:17:55.269> it<00:17:55.629> works<00:17:56.229> in<00:17:56.320> both<00:17:56.440> directions 00:18:02.930 --> 00:18:02.940 align:start position:0% 00:18:02.940 --> 00:18:07.379 align:start position:0% besides<00:18:03.940> setting<00:18:04.359> it<00:18:04.539> to<00:18:04.659> zero<00:18:04.929> and<00:18:06.389> raising 00:18:07.379 --> 00:18:07.389 align:start position:0% besides setting it to zero and raising 00:18:07.389 --> 00:18:08.820 align:start position:0% besides setting it to zero and raising at<00:18:07.479> the<00:18:07.539> end<00:18:07.659> of<00:18:07.779> five<00:18:07.929> has<00:18:08.169> to<00:18:08.200> be<00:18:08.499> two 00:18:08.820 --> 00:18:08.830 align:start position:0% at the end of five has to be two 00:18:08.830 --> 00:18:16.710 align:start position:0% at the end of five has to be two separate<00:18:09.159> transactions<00:18:14.820> I<00:18:15.820> think<00:18:16.539> in 00:18:16.710 --> 00:18:16.720 align:start position:0% separate transactions I think in 00:18:16.720 --> 00:18:18.629 align:start position:0% separate transactions I think in response<00:18:16.960> to<00:18:17.379> the<00:18:17.499> tweet<00:18:17.799> was<00:18:18.070> the<00:18:18.309> the 00:18:18.629 --> 00:18:18.639 align:start position:0% response to the tweet was the the 00:18:18.639 --> 00:18:21.419 align:start position:0% response to the tweet was the the official<00:18:19.029> submission<00:18:19.359> venue<00:18:20.019> yeah<00:18:20.889> we<00:18:21.309> can 00:18:21.419 --> 00:18:21.429 align:start position:0% official submission venue yeah we can 00:18:21.429 --> 00:18:23.369 align:start position:0% official submission venue yeah we can post<00:18:21.789> it<00:18:21.940> somewhere<00:18:22.090> afterwards<00:18:22.479> as<00:18:22.720> well<00:18:22.899> but 00:18:23.369 --> 00:18:23.379 align:start position:0% post it somewhere afterwards as well but 00:18:23.379 --> 00:18:24.839 align:start position:0% post it somewhere afterwards as well but I<00:18:23.440> think<00:18:23.710> he<00:18:23.799> wants<00:18:23.889> to<00:18:24.070> know<00:18:24.159> how<00:18:24.369> he<00:18:24.460> can<00:18:24.700> get 00:18:24.839 --> 00:18:24.849 align:start position:0% I think he wants to know how he can get 00:18:24.849 --> 00:18:26.519 align:start position:0% I think he wants to know how he can get it<00:18:24.999> draw<00:18:25.210> the<00:18:25.269> draw<00:18:25.899> a<00:18:25.929> submission<00:18:26.289> to<00:18:26.499> our 00:18:26.519 --> 00:18:26.529 align:start position:0% it draw the draw a submission to our 00:18:26.529 --> 00:18:28.919 align:start position:0% it draw the draw a submission to our attention<00:18:26.889> now<00:18:27.220> Oh<00:18:27.519> is<00:18:28.389> there<00:18:28.570> a<00:18:28.629> submission 00:18:28.919 --> 00:18:28.929 align:start position:0% attention now Oh is there a submission 00:18:28.929 --> 00:18:42.389 align:start position:0% attention now Oh is there a submission somewhere<00:18:29.799> in<00:18:29.919> some<00:18:30.129> queue<00:18:30.690> cool<00:18:39.029> right<00:18:41.399> we'll 00:18:42.389 --> 00:18:42.399 align:start position:0% somewhere in some queue cool right we'll 00:18:42.399 --> 00:18:47.070 align:start position:0% somewhere in some queue cool right we'll go<00:18:42.879> through<00:18:43.119> this<00:18:43.269> a<00:18:43.330> bit<00:18:43.539> more<00:18:44.940> until<00:18:46.080> because 00:18:47.070 --> 00:18:47.080 align:start position:0% go through this a bit more until because 00:18:47.080 --> 00:18:49.830 align:start position:0% go through this a bit more until because I<00:18:47.109> think<00:18:47.379> there<00:18:47.499> was<00:18:47.619> some<00:18:48.419> and<00:18:49.419> then<00:18:49.690> we'll 00:18:49.830 --> 00:18:49.840 align:start position:0% I think there was some and then we'll 00:18:49.840 --> 00:18:52.549 align:start position:0% I think there was some and then we'll jump<00:18:50.019> to<00:18:50.139> the<00:18:50.229> next<00:18:50.320> one<00:18:50.470> this<00:18:50.950> is<00:18:51.279> the<00:18:51.700> actual 00:18:52.549 --> 00:18:52.559 align:start position:0% jump to the next one this is the actual 00:18:52.559 --> 00:18:55.440 align:start position:0% jump to the next one this is the actual contracts<00:18:53.820> implementation<00:18:54.820> and<00:18:55.029> not<00:18:55.059> just 00:18:55.440 --> 00:18:55.450 align:start position:0% contracts implementation and not just 00:18:55.450 --> 00:18:58.139 align:start position:0% contracts implementation and not just boilerplate<00:18:56.429> well<00:18:57.429> there<00:18:57.609> is<00:18:57.700> actually 00:18:58.139 --> 00:18:58.149 align:start position:0% boilerplate well there is actually 00:18:58.149 --> 00:19:00.330 align:start position:0% boilerplate well there is actually mostly<00:18:58.570> boilerplate<00:18:59.019> in<00:18:59.349> the<00:18:59.529> constructor<00:19:00.159> it 00:19:00.330 --> 00:19:00.340 align:start position:0% mostly boilerplate in the constructor it 00:19:00.340 --> 00:19:03.810 align:start position:0% mostly boilerplate in the constructor it says<00:19:00.639> issue<00:19:00.879> cards<00:19:01.389> for<00:19:02.399> where<00:19:03.399> is<00:19:03.489> that<00:19:03.580> from 00:19:03.810 --> 00:19:03.820 align:start position:0% says issue cards for where is that from 00:19:03.820 --> 00:19:05.639 align:start position:0% says issue cards for where is that from line<00:19:03.970> 255<00:19:04.749> there's<00:19:04.989> a<00:19:05.049> hundred<00:19:05.320> of<00:19:05.379> them<00:19:05.440> my 00:19:05.639 --> 00:19:05.649 align:start position:0% line 255 there's a hundred of them my 00:19:05.649 --> 00:19:11.609 align:start position:0% line 255 there's a hundred of them my counter<00:19:05.950> and<00:19:09.210> every<00:19:10.210> call<00:19:10.869> to<00:19:10.899> issue<00:19:11.259> card 00:19:11.609 --> 00:19:11.619 align:start position:0% counter and every call to issue card 00:19:11.619 --> 00:19:13.109 align:start position:0% counter and every call to issue card here<00:19:11.859> in<00:19:11.979> this<00:19:12.099> constructor<00:19:12.669> will<00:19:12.849> increase 00:19:13.109 --> 00:19:13.119 align:start position:0% here in this constructor will increase 00:19:13.119 --> 00:19:17.129 align:start position:0% here in this constructor will increase the<00:19:13.269> total<00:19:13.419> supply<00:19:14.129> to<00:19:15.129> 100<00:19:16.059> and<00:19:16.330> set<00:19:17.019> the 00:19:17.129 --> 00:19:17.139 align:start position:0% the total supply to 100 and set the 00:19:17.139 --> 00:19:19.820 align:start position:0% the total supply to 100 and set the balances<00:19:17.710> of<00:19:17.950> these<00:19:18.099> hard<00:19:18.399> coded<00:19:18.700> addresses 00:19:19.820 --> 00:19:19.830 align:start position:0% balances of these hard coded addresses 00:19:19.830 --> 00:19:23.070 align:start position:0% balances of these hard coded addresses and<00:19:20.830> then<00:19:21.039> there's<00:19:21.340> this<00:19:21.700> and<00:19:22.090> that's<00:19:22.960> an 00:19:23.070 --> 00:19:23.080 align:start position:0% and then there's this and that's an 00:19:23.080 --> 00:19:24.749 align:start position:0% and then there's this and that's an internal<00:19:23.440> thing<00:19:24.009> so<00:19:24.249> now<00:19:24.340> I'm<00:19:24.489> gonna<00:19:24.580> call 00:19:24.749 --> 00:19:24.759 align:start position:0% internal thing so now I'm gonna call 00:19:24.759 --> 00:19:27.509 align:start position:0% internal thing so now I'm gonna call that<00:19:24.789> external<00:19:25.450> and<00:19:25.769> then<00:19:26.769> we<00:19:26.889> have<00:19:27.070> the<00:19:27.309> bike 00:19:27.509 --> 00:19:27.519 align:start position:0% that external and then we have the bike 00:19:27.519 --> 00:19:29.219 align:start position:0% that external and then we have the bike card<00:19:27.879> there's<00:19:28.450> actually<00:19:28.720> one<00:19:28.779> quick<00:19:28.929> thing<00:19:29.080> I 00:19:29.219 --> 00:19:29.229 align:start position:0% card there's actually one quick thing I 00:19:29.229 --> 00:19:30.629 align:start position:0% card there's actually one quick thing I want<00:19:29.409> to<00:19:29.499> point<00:19:29.559> out<00:19:29.679> with<00:19:29.799> the<00:19:29.919> issue<00:19:30.070> card<00:19:30.460> on 00:19:30.629 --> 00:19:30.639 align:start position:0% want to point out with the issue card on 00:19:30.639 --> 00:19:32.060 align:start position:0% want to point out with the issue card on this<00:19:31.210> part<00:19:31.479> they<00:19:31.539> actually<00:19:31.749> did<00:19:31.840> write 00:19:32.060 --> 00:19:32.070 align:start position:0% this part they actually did write 00:19:32.070 --> 00:19:34.739 align:start position:0% this part they actually did write oftentimes<00:19:33.070> in<00:19:33.639> the<00:19:33.999> constructor<00:19:34.419> people 00:19:34.739 --> 00:19:34.749 align:start position:0% oftentimes in the constructor people 00:19:34.749 --> 00:19:36.599 align:start position:0% oftentimes in the constructor people allocate<00:19:35.229> tokens<00:19:35.590> and<00:19:35.710> don't<00:19:35.919> call<00:19:36.159> transfer 00:19:36.599 --> 00:19:36.609 align:start position:0% allocate tokens and don't call transfer 00:19:36.609 --> 00:19:38.279 align:start position:0% allocate tokens and don't call transfer which<00:19:37.359> means<00:19:37.629> that<00:19:37.809> there's<00:19:37.929> no<00:19:38.019> transfer 00:19:38.279 --> 00:19:38.289 align:start position:0% which means that there's no transfer 00:19:38.289 --> 00:19:39.989 align:start position:0% which means that there's no transfer events<00:19:38.499> so<00:19:38.950> if<00:19:39.039> you<00:19:39.129> are<00:19:39.279> writing<00:19:39.460> a<00:19:39.580> tool<00:19:39.759> that 00:19:39.989 --> 00:19:39.999 align:start position:0% events so if you are writing a tool that 00:19:39.999 --> 00:19:41.369 align:start position:0% events so if you are writing a tool that works<00:19:40.179> against<00:19:40.509> like<00:19:40.599> status<00:19:41.080> or<00:19:41.200> when<00:19:41.289> those 00:19:41.369 --> 00:19:41.379 align:start position:0% works against like status or when those 00:19:41.379 --> 00:19:44.700 align:start position:0% works against like status or when those other<00:19:42.479> apps<00:19:43.479> that<00:19:43.809> that<00:19:44.229> looks<00:19:44.470> at<00:19:44.619> the 00:19:44.700 --> 00:19:44.710 align:start position:0% other apps that that looks at the 00:19:44.710 --> 00:19:46.349 align:start position:0% other apps that that looks at the history<00:19:44.979> to<00:19:45.129> figure<00:19:45.249> out<00:19:45.369> how<00:19:46.059> many<00:19:46.119> tokens 00:19:46.349 --> 00:19:46.359 align:start position:0% history to figure out how many tokens 00:19:46.359 --> 00:19:48.570 align:start position:0% history to figure out how many tokens you<00:19:46.599> have<00:19:46.779> if<00:19:47.559> you<00:19:47.830> were<00:19:47.919> allocated<00:19:48.369> five 00:19:48.570 --> 00:19:48.580 align:start position:0% you have if you were allocated five 00:19:48.580 --> 00:19:50.099 align:start position:0% you have if you were allocated five tokens<00:19:49.029> for<00:19:49.269> example<00:19:49.570> in<00:19:49.629> the<00:19:49.690> constructor 00:19:50.099 --> 00:19:50.109 align:start position:0% tokens for example in the constructor 00:19:50.109 --> 00:19:52.320 align:start position:0% tokens for example in the constructor and<00:19:50.259> a<00:19:50.349> transfer<00:19:51.039> never<00:19:51.220> happened<00:19:51.609> and<00:19:52.179> you're 00:19:52.320 --> 00:19:52.330 align:start position:0% and a transfer never happened and you're 00:19:52.330 --> 00:19:53.990 align:start position:0% and a transfer never happened and you're just<00:19:52.419> looking<00:19:52.539> for<00:19:52.929> those<00:19:53.409> events 00:19:53.990 --> 00:19:54.000 align:start position:0% just looking for those events 00:19:54.000 --> 00:19:55.130 align:start position:0% just looking for those events don't<00:19:54.150> actually<00:19:54.300> know<00:19:54.630> that<00:19:54.660> you<00:19:54.870> had<00:19:54.960> five 00:19:55.130 --> 00:19:55.140 align:start position:0% don't actually know that you had five 00:19:55.140 --> 00:20:02.600 align:start position:0% don't actually know that you had five tokens<00:19:55.340> so<00:19:56.340> that<00:19:56.940> I<00:19:56.970> thought<00:19:57.300> was<00:20:01.280> right<00:20:02.280> from 00:20:02.600 --> 00:20:02.610 align:start position:0% tokens so that I thought was right from 00:20:02.610 --> 00:20:05.510 align:start position:0% tokens so that I thought was right from zero<00:20:02.940> to<00:20:03.030> whoever<00:20:03.450> yeah<00:20:04.320> and<00:20:04.590> it's<00:20:05.160> also<00:20:05.280> good 00:20:05.510 --> 00:20:05.520 align:start position:0% zero to whoever yeah and it's also good 00:20:05.520 --> 00:20:08.030 align:start position:0% zero to whoever yeah and it's also good it's<00:20:06.240> also<00:20:06.420> good<00:20:06.690> like<00:20:06.960> a<00:20:07.200> reminder<00:20:07.740> that<00:20:07.770> the 00:20:08.030 --> 00:20:08.040 align:start position:0% it's also good like a reminder that the 00:20:08.040 --> 00:20:11.090 align:start position:0% it's also good like a reminder that the transfer<00:20:08.610> event<00:20:08.940> is<00:20:09.210> like<00:20:09.900> merely<00:20:10.410> a<00:20:10.560> helper 00:20:11.090 --> 00:20:11.100 align:start position:0% transfer event is like merely a helper 00:20:11.100 --> 00:20:14.420 align:start position:0% transfer event is like merely a helper writes<00:20:11.670> a<00:20:11.820> lot<00:20:12.000> of<00:20:12.090> a<00:20:12.270> lot<00:20:12.420> of<00:20:12.510> apps<00:20:12.800> like<00:20:13.800> just 00:20:14.420 --> 00:20:14.430 align:start position:0% writes a lot of a lot of apps like just 00:20:14.430 --> 00:20:16.250 align:start position:0% writes a lot of a lot of apps like just kind<00:20:15.060> of<00:20:15.120> assuming<00:20:15.360> transfer<00:20:15.780> events<00:20:15.960> as<00:20:16.170> the 00:20:16.250 --> 00:20:16.260 align:start position:0% kind of assuming transfer events as the 00:20:16.260 --> 00:20:18.050 align:start position:0% kind of assuming transfer events as the absolute<00:20:16.470> truth<00:20:16.800> but<00:20:17.040> I<00:20:17.070> but<00:20:17.460> it's<00:20:17.820> good<00:20:17.970> to 00:20:18.050 --> 00:20:18.060 align:start position:0% absolute truth but I but it's good to 00:20:18.060 --> 00:20:20.930 align:start position:0% absolute truth but I but it's good to always<00:20:18.390> at<00:20:18.810> least<00:20:19.020> check<00:20:19.320> on<00:20:19.560> chain<00:20:19.940> whether 00:20:20.930 --> 00:20:20.940 align:start position:0% always at least check on chain whether 00:20:20.940 --> 00:20:23.270 align:start position:0% always at least check on chain whether that<00:20:21.330> transfer<00:20:22.140> event<00:20:22.440> were<00:20:22.620> you<00:20:22.950> know<00:20:23.070> like 00:20:23.270 --> 00:20:23.280 align:start position:0% that transfer event were you know like 00:20:23.280 --> 00:20:26.300 align:start position:0% that transfer event were you know like represents<00:20:23.910> reality<00:20:24.060> right<00:20:24.840> and<00:20:25.320> one<00:20:26.160> of<00:20:26.250> the 00:20:26.300 --> 00:20:26.310 align:start position:0% represents reality right and one of the 00:20:26.310 --> 00:20:27.800 align:start position:0% represents reality right and one of the quick<00:20:26.460> come<00:20:26.580> on<00:20:26.700> I<00:20:26.790> might<00:20:26.940> make<00:20:27.090> as<00:20:27.750> a 00:20:27.800 --> 00:20:27.810 align:start position:0% quick come on I might make as a 00:20:27.810 --> 00:20:30.050 align:start position:0% quick come on I might make as a shameless<00:20:28.470> plug<00:20:28.740> is<00:20:29.130> there's<00:20:29.490> a<00:20:29.580> system 00:20:30.050 --> 00:20:30.060 align:start position:0% shameless plug is there's a system 00:20:30.060 --> 00:20:32.270 align:start position:0% shameless plug is there's a system called<00:20:30.300> Merkel<00:20:30.780> airdrops<00:20:31.290> that<00:20:31.980> might<00:20:32.190> have 00:20:32.270 --> 00:20:32.280 align:start position:0% called Merkel airdrops that might have 00:20:32.280 --> 00:20:34.880 align:start position:0% called Merkel airdrops that might have worked<00:20:32.460> better<00:20:32.640> here<00:20:33.050> for<00:20:34.050> 100<00:20:34.380> maybe<00:20:34.500> not<00:20:34.740> so 00:20:34.880 --> 00:20:34.890 align:start position:0% worked better here for 100 maybe not so 00:20:34.890 --> 00:20:36.440 align:start position:0% worked better here for 100 maybe not so bad<00:20:35.040> but<00:20:35.280> you<00:20:35.340> can<00:20:35.490> imagine<00:20:35.610> you<00:20:36.090> don't<00:20:36.270> want 00:20:36.440 --> 00:20:36.450 align:start position:0% bad but you can imagine you don't want 00:20:36.450 --> 00:20:37.610 align:start position:0% bad but you can imagine you don't want it<00:20:36.570> if<00:20:36.660> you're<00:20:36.810> putting<00:20:37.200> this<00:20:37.260> out<00:20:37.350> into<00:20:37.560> a 00:20:37.610 --> 00:20:37.620 align:start position:0% it if you're putting this out into a 00:20:37.620 --> 00:20:39.470 align:start position:0% it if you're putting this out into a thousand<00:20:38.010> people's<00:20:38.220> hands 00:20:39.470 --> 00:20:39.480 align:start position:0% thousand people's hands 00:20:39.480 --> 00:20:41.600 align:start position:0% thousand people's hands not<00:20:40.410> everyone<00:20:40.740> maybe<00:20:40.860> use<00:20:41.070> their<00:20:41.190> card<00:20:41.430> it 00:20:41.600 --> 00:20:41.610 align:start position:0% not everyone maybe use their card it 00:20:41.610 --> 00:20:44.000 align:start position:0% not everyone maybe use their card it makes<00:20:41.730> more<00:20:41.880> sense<00:20:41.940> to<00:20:42.210> you<00:20:42.630> to<00:20:43.020> Merkel<00:20:43.890> eyes 00:20:44.000 --> 00:20:44.010 align:start position:0% makes more sense to you to Merkel eyes 00:20:44.010 --> 00:20:45.650 align:start position:0% makes more sense to you to Merkel eyes it<00:20:44.190> and<00:20:44.370> just<00:20:44.580> submit<00:20:44.700> the<00:20:44.820> Merkel<00:20:45.150> hash<00:20:45.300> and 00:20:45.650 --> 00:20:45.660 align:start position:0% it and just submit the Merkel hash and 00:20:45.660 --> 00:20:47.660 align:start position:0% it and just submit the Merkel hash and then<00:20:46.230> force<00:20:46.560> people<00:20:46.710> to<00:20:46.830> claim<00:20:47.010> it<00:20:47.220> if<00:20:47.370> that 00:20:47.660 --> 00:20:47.670 align:start position:0% then force people to claim it if that 00:20:47.670 --> 00:20:48.950 align:start position:0% then force people to claim it if that works<00:20:47.910> in<00:20:48.030> your<00:20:48.120> case<00:20:48.300> it<00:20:48.540> might<00:20:48.570> not<00:20:48.750> work<00:20:48.780> in 00:20:48.950 --> 00:20:48.960 align:start position:0% works in your case it might not work in 00:20:48.960 --> 00:20:50.870 align:start position:0% works in your case it might not work in all<00:20:49.020> cases<00:20:49.170> but<00:20:50.130> I<00:20:50.190> could<00:20:50.400> imagine<00:20:50.550> situations 00:20:50.870 --> 00:20:50.880 align:start position:0% all cases but I could imagine situations 00:20:50.880 --> 00:20:52.700 align:start position:0% all cases but I could imagine situations we're<00:20:51.330> deploying<00:20:51.750> this<00:20:52.080> especially<00:20:52.500> if<00:20:52.650> you 00:20:52.700 --> 00:20:52.710 align:start position:0% we're deploying this especially if you 00:20:52.710 --> 00:20:53.210 align:start position:0% we're deploying this especially if you want<00:20:52.800> to<00:20:52.890> issue 00:20:53.210 --> 00:20:53.220 align:start position:0% want to issue 00:20:53.220 --> 00:21:00.310 align:start position:0% want to issue ten<00:20:54.000> million<00:20:54.210> cards<00:20:54.690> would<00:20:54.870> be<00:20:54.930> infeasible 00:21:00.310 --> 00:21:00.320 align:start position:0% 00:21:00.320 --> 00:21:03.020 align:start position:0% use<00:21:01.320> the<00:21:01.470> microphone<00:21:01.890> cause<00:21:02.130> I<00:21:02.160> still<00:21:02.520> has<00:21:02.700> I 00:21:03.020 --> 00:21:03.030 align:start position:0% use the microphone cause I still has I 00:21:03.030 --> 00:21:05.030 align:start position:0% use the microphone cause I still has I think<00:21:03.660> that<00:21:03.750> if<00:21:03.900> you<00:21:04.020> card<00:21:04.230> has<00:21:04.440> a<00:21:04.470> pocket<00:21:04.650> here 00:21:05.030 --> 00:21:05.040 align:start position:0% think that if you card has a pocket here 00:21:05.040 --> 00:21:07.160 align:start position:0% think that if you card has a pocket here because<00:21:06.030> it<00:21:06.150> can<00:21:06.180> lead<00:21:06.330> to<00:21:06.570> inconsistent 00:21:07.160 --> 00:21:07.170 align:start position:0% because it can lead to inconsistent 00:21:07.170 --> 00:21:08.870 align:start position:0% because it can lead to inconsistent total<00:21:07.380> supply<00:21:07.620> because<00:21:07.950> if<00:21:08.100> you<00:21:08.250> issue<00:21:08.520> card 00:21:08.870 --> 00:21:08.880 align:start position:0% total supply because if you issue card 00:21:08.880 --> 00:21:11.000 align:start position:0% total supply because if you issue card to<00:21:09.450> the<00:21:09.570> same<00:21:09.720> address<00:21:09.990> twice<00:21:10.170> then<00:21:10.680> the 00:21:11.000 --> 00:21:11.010 align:start position:0% to the same address twice then the 00:21:11.010 --> 00:21:13.130 align:start position:0% to the same address twice then the balance<00:21:11.280> will<00:21:11.430> be<00:21:11.580> still<00:21:11.910> one<00:21:12.480> but<00:21:12.810> total 00:21:13.130 --> 00:21:13.140 align:start position:0% balance will be still one but total 00:21:13.140 --> 00:21:21.520 align:start position:0% balance will be still one but total supply<00:21:13.380> will<00:21:13.530> be<00:21:13.560> increased<00:21:13.920> twice<00:21:14.130> yes<00:21:15.860> yes 00:21:21.520 --> 00:21:21.530 align:start position:0% 00:21:21.530 --> 00:21:23.900 align:start position:0% hard-coded<00:21:22.530> this<00:21:22.890> can<00:21:23.070> be<00:21:23.190> discovered<00:21:23.520> at<00:21:23.880> the 00:21:23.900 --> 00:21:23.910 align:start position:0% hard-coded this can be discovered at the 00:21:23.910 --> 00:21:27.200 align:start position:0% hard-coded this can be discovered at the you<00:21:24.540> know<00:21:24.630> at<00:21:24.960> the<00:21:25.590> code<00:21:25.800> at<00:21:26.070> the<00:21:26.280> this<00:21:26.760> stage 00:21:27.200 --> 00:21:27.210 align:start position:0% you know at the code at the this stage 00:21:27.210 --> 00:21:29.450 align:start position:0% you know at the code at the this stage where<00:21:27.510> we're<00:21:27.690> at<00:21:27.750> but<00:21:28.110> you<00:21:28.650> total<00:21:29.070> right<00:21:29.220> that 00:21:29.450 --> 00:21:29.460 align:start position:0% where we're at but you total right that 00:21:29.460 --> 00:21:32.630 align:start position:0% where we're at but you total right that I<00:21:29.670> mean<00:21:29.970> in<00:21:30.780> itself<00:21:31.170> yes<00:21:31.500> that<00:21:31.770> is<00:21:31.890> flawed<00:21:32.100> you 00:21:32.630 --> 00:21:32.640 align:start position:0% I mean in itself yes that is flawed you 00:21:32.640 --> 00:21:34.430 align:start position:0% I mean in itself yes that is flawed you also<00:21:32.820> very<00:21:32.970> good<00:21:33.300> point<00:21:33.540> if<00:21:33.690> I<00:21:33.840> was<00:21:34.110> doing<00:21:34.350> this 00:21:34.430 --> 00:21:34.440 align:start position:0% also very good point if I was doing this 00:21:34.440 --> 00:21:36.470 align:start position:0% also very good point if I was doing this I<00:21:34.650> would<00:21:34.710> probably<00:21:34.800> sort<00:21:35.370> the<00:21:35.670> cards<00:21:35.880> so<00:21:36.240> my 00:21:36.470 --> 00:21:36.480 align:start position:0% I would probably sort the cards so my 00:21:36.480 --> 00:21:38.060 align:start position:0% I would probably sort the cards so my inspection<00:21:36.900> you<00:21:37.230> could<00:21:37.350> tell<00:21:37.500> easier<00:21:37.950> if 00:21:38.060 --> 00:21:38.070 align:start position:0% inspection you could tell easier if 00:21:38.070 --> 00:21:39.470 align:start position:0% inspection you could tell easier if there<00:21:38.220> was<00:21:38.310> a<00:21:38.340> do<00:21:38.460> forget<00:21:38.700> one<00:21:38.850> yeah<00:21:39.210> I<00:21:39.240> think 00:21:39.470 --> 00:21:39.480 align:start position:0% there was a do forget one yeah I think 00:21:39.480 --> 00:21:41.060 align:start position:0% there was a do forget one yeah I think this<00:21:39.600> is<00:21:39.720> a<00:21:39.750> good<00:21:39.960> this<00:21:40.740> is<00:21:40.860> I<00:21:41.040> think 00:21:41.060 --> 00:21:41.070 align:start position:0% this is a good this is I think 00:21:41.070 --> 00:21:44.030 align:start position:0% this is a good this is I think regardless<00:21:41.760> I<00:21:42.570> would<00:21:43.080> change<00:21:43.440> this<00:21:43.740> because 00:21:44.030 --> 00:21:44.040 align:start position:0% regardless I would change this because 00:21:44.040 --> 00:21:46.130 align:start position:0% regardless I would change this because this<00:21:44.250> is<00:21:44.310> an<00:21:44.490> example<00:21:45.150> of<00:21:45.210> like<00:21:45.300> very<00:21:45.570> fragile 00:21:46.130 --> 00:21:46.140 align:start position:0% this is an example of like very fragile 00:21:46.140 --> 00:21:48.980 align:start position:0% this is an example of like very fragile code<00:21:46.380> if<00:21:46.590> the<00:21:46.800> guy<00:21:47.040> decides<00:21:47.460> oh<00:21:47.940> actually<00:21:48.360> I 00:21:48.980 --> 00:21:48.990 align:start position:0% code if the guy decides oh actually I 00:21:48.990 --> 00:21:52.370 align:start position:0% code if the guy decides oh actually I don't<00:21:49.380> have<00:21:50.210> like<00:21:51.210> you<00:21:51.480> know<00:21:51.630> hard<00:21:51.900> coded<00:21:52.140> list 00:21:52.370 --> 00:21:52.380 align:start position:0% don't have like you know hard coded list 00:21:52.380 --> 00:21:54.320 align:start position:0% don't have like you know hard coded list I<00:21:52.650> might<00:21:52.890> I<00:21:53.070> need<00:21:53.250> I<00:21:53.430> wanted<00:21:53.700> to<00:21:53.760> be<00:21:53.850> dynamic 00:21:54.320 --> 00:21:54.330 align:start position:0% I might I need I wanted to be dynamic 00:21:54.330 --> 00:21:55.700 align:start position:0% I might I need I wanted to be dynamic and<00:21:54.420> then<00:21:54.600> he<00:21:54.660> changes<00:21:55.050> us<00:21:55.200> and<00:21:55.380> then<00:21:55.620> he 00:21:55.700 --> 00:21:55.710 align:start position:0% and then he changes us and then he 00:21:55.710 --> 00:21:58.430 align:start position:0% and then he changes us and then he forgets<00:21:56.370> to<00:21:56.760> say<00:21:56.790> Oh<00:21:57.180> issue<00:21:57.390> card<00:21:57.810> wasn't<00:21:58.140> made 00:21:58.430 --> 00:21:58.440 align:start position:0% forgets to say Oh issue card wasn't made 00:21:58.440 --> 00:22:00.830 align:start position:0% forgets to say Oh issue card wasn't made for<00:21:58.470> that<00:21:58.680> and<00:21:59.010> he'll<00:21:59.550> deploy<00:21:59.850> that<00:22:00.120> and<00:22:00.450> then 00:22:00.830 --> 00:22:00.840 align:start position:0% for that and he'll deploy that and then 00:22:00.840 --> 00:22:02.720 align:start position:0% for that and he'll deploy that and then that<00:22:01.050> you<00:22:01.230> know<00:22:01.320> like<00:22:01.590> somebody<00:22:02.490> buy 00:22:02.720 --> 00:22:02.730 align:start position:0% that you know like somebody buy 00:22:02.730 --> 00:22:04.280 align:start position:0% that you know like somebody buy something<00:22:03.179> once<00:22:03.390> and<00:22:03.510> then<00:22:03.690> he'll<00:22:03.870> lose<00:22:04.050> like 00:22:04.280 --> 00:22:04.290 align:start position:0% something once and then he'll lose like 00:22:04.290 --> 00:22:06.470 align:start position:0% something once and then he'll lose like you<00:22:04.410> know<00:22:04.530> he'll<00:22:04.980> lose<00:22:05.130> one<00:22:05.280> of<00:22:05.370> them<00:22:05.460> right<00:22:05.610> so 00:22:06.470 --> 00:22:06.480 align:start position:0% you know he'll lose one of them right so 00:22:06.480 --> 00:22:07.850 align:start position:0% you know he'll lose one of them right so yeah<00:22:06.660> it's<00:22:06.780> like<00:22:06.870> always 00:22:07.850 --> 00:22:07.860 align:start position:0% yeah it's like always 00:22:07.860 --> 00:22:09.740 align:start position:0% yeah it's like always it<00:22:08.010> doesn't<00:22:08.370> really<00:22:08.610> cost<00:22:08.820> it<00:22:09.240> we<00:22:09.510> know<00:22:09.600> it 00:22:09.740 --> 00:22:09.750 align:start position:0% it doesn't really cost it we know it 00:22:09.750 --> 00:22:11.450 align:start position:0% it doesn't really cost it we know it would<00:22:09.929> probably<00:22:09.960> end<00:22:10.350> up<00:22:10.440> being<00:22:11.070> like<00:22:11.220> five 00:22:11.450 --> 00:22:11.460 align:start position:0% would probably end up being like five 00:22:11.460 --> 00:22:14.510 align:start position:0% would probably end up being like five more<00:22:11.670> opcodes<00:22:12.179> but<00:22:12.450> it's<00:22:12.540> it's<00:22:12.780> good<00:22:13.340> yeah<00:22:14.340> we 00:22:14.510 --> 00:22:14.520 align:start position:0% more opcodes but it's it's good yeah we 00:22:14.520 --> 00:22:18.830 align:start position:0% more opcodes but it's it's good yeah we like<00:22:15.240> it<00:22:15.270> to<00:22:16.110> dot<00:22:16.320> and<00:22:17.250> then<00:22:17.700> plus<00:22:17.940> yeah<00:22:18.540> oh<00:22:18.630> no 00:22:18.830 --> 00:22:18.840 align:start position:0% like it to dot and then plus yeah oh no 00:22:18.840 --> 00:22:21.830 align:start position:0% like it to dot and then plus yeah oh no okay<00:22:19.290> yeah<00:22:19.710> always<00:22:20.190> always<00:22:20.610> they<00:22:21.450> try<00:22:21.600> to<00:22:21.660> make 00:22:21.830 --> 00:22:21.840 align:start position:0% okay yeah always always they try to make 00:22:21.840 --> 00:22:23.930 align:start position:0% okay yeah always always they try to make your<00:22:21.929> code<00:22:22.140> as<00:22:22.380> anti<00:22:23.010> fragile<00:22:23.250> as<00:22:23.490> possible 00:22:23.930 --> 00:22:23.940 align:start position:0% your code as anti fragile as possible 00:22:23.940 --> 00:22:26.299 align:start position:0% your code as anti fragile as possible just<00:22:24.120> because<00:22:24.210> it's<00:22:24.540> it<00:22:25.110> works<00:22:25.320> if<00:22:25.650> it's<00:22:26.040> work 00:22:26.299 --> 00:22:26.309 align:start position:0% just because it's it works if it's work 00:22:26.309 --> 00:22:28.039 align:start position:0% just because it's it works if it's work if<00:22:26.610> it's<00:22:26.820> wonky<00:22:27.270> but<00:22:27.450> it<00:22:27.540> works<00:22:27.720> in<00:22:27.900> this 00:22:28.039 --> 00:22:28.049 align:start position:0% if it's wonky but it works in this 00:22:28.049 --> 00:22:29.840 align:start position:0% if it's wonky but it works in this specific<00:22:28.530> situation<00:22:28.679> just<00:22:29.309> change<00:22:29.580> it<00:22:29.760> so 00:22:29.840 --> 00:22:29.850 align:start position:0% specific situation just change it so 00:22:29.850 --> 00:22:30.890 align:start position:0% specific situation just change it so that<00:22:29.970> it<00:22:30.059> works<00:22:30.120> in<00:22:30.299> the<00:22:30.390> general<00:22:30.660> case 00:22:30.890 --> 00:22:30.900 align:start position:0% that it works in the general case 00:22:30.900 --> 00:22:32.510 align:start position:0% that it works in the general case because<00:22:31.200> you'll<00:22:31.320> forget<00:22:31.620> to<00:22:31.890> change<00:22:32.070> it<00:22:32.309> later 00:22:32.510 --> 00:22:32.520 align:start position:0% because you'll forget to change it later 00:22:32.520 --> 00:22:33.789 align:start position:0% because you'll forget to change it later on 00:22:33.789 --> 00:22:33.799 align:start position:0% on 00:22:33.799 --> 00:22:36.460 align:start position:0% on having<00:22:34.799> been<00:22:34.920> a<00:22:34.980> security<00:22:35.400> auditor<00:22:35.760> in<00:22:36.059> like 00:22:36.460 --> 00:22:36.470 align:start position:0% having been a security auditor in like 00:22:36.470 --> 00:22:38.900 align:start position:0% having been a security auditor in like general<00:22:37.470> IT<00:22:37.710> security<00:22:38.010> one<00:22:38.370> thing<00:22:38.640> that<00:22:38.760> I've 00:22:38.900 --> 00:22:38.910 align:start position:0% general IT security one thing that I've 00:22:38.910 --> 00:22:41.299 align:start position:0% general IT security one thing that I've learned<00:22:38.940> is<00:22:39.299> that<00:22:39.620> ask<00:22:40.620> a<00:22:40.770> lot<00:22:40.860> of<00:22:40.980> stupid 00:22:41.299 --> 00:22:41.309 align:start position:0% learned is that ask a lot of stupid 00:22:41.309 --> 00:22:43.400 align:start position:0% learned is that ask a lot of stupid questions<00:22:41.370> and<00:22:41.850> don't<00:22:42.030> be<00:22:42.179> afraid<00:22:42.450> to<00:22:42.960> look 00:22:43.400 --> 00:22:43.410 align:start position:0% questions and don't be afraid to look 00:22:43.410 --> 00:22:45.830 align:start position:0% questions and don't be afraid to look stupid<00:22:43.590> because<00:22:44.250> it<00:22:44.400> makes<00:22:44.910> things<00:22:45.120> go<00:22:45.270> faster 00:22:45.830 --> 00:22:45.840 align:start position:0% stupid because it makes things go faster 00:22:45.840 --> 00:22:47.659 align:start position:0% stupid because it makes things go faster if<00:22:45.929> you<00:22:46.020> just<00:22:46.410> spit<00:22:47.040> out<00:22:47.070> things<00:22:47.490> you<00:22:47.580> don't 00:22:47.659 --> 00:22:47.669 align:start position:0% if you just spit out things you don't 00:22:47.669 --> 00:22:48.950 align:start position:0% if you just spit out things you don't understand<00:22:48.090> and<00:22:48.480> I<00:22:48.600> actually<00:22:48.750> don't 00:22:48.950 --> 00:22:48.960 align:start position:0% understand and I actually don't 00:22:48.960 --> 00:22:51.080 align:start position:0% understand and I actually don't understand<00:22:49.380> really<00:22:49.770> how<00:22:50.010> bike<00:22:50.580> card<00:22:50.850> works 00:22:51.080 --> 00:22:51.090 align:start position:0% understand really how bike card works 00:22:51.090 --> 00:22:55.280 align:start position:0% understand really how bike card works because<00:22:51.660> here<00:22:52.410> money<00:22:52.770> comes<00:22:53.070> in<00:22:53.280> I<00:22:53.929> check<00:22:54.929> some 00:22:55.280 --> 00:22:55.290 align:start position:0% because here money comes in I check some 00:22:55.290 --> 00:22:57.440 align:start position:0% because here money comes in I check some stuff<00:22:55.320> and<00:22:55.860> it<00:22:56.280> amidst<00:22:56.669> an<00:22:56.820> event<00:22:57.030> yeah 00:22:57.440 --> 00:22:57.450 align:start position:0% stuff and it amidst an event yeah 00:22:57.450 --> 00:23:00.650 align:start position:0% stuff and it amidst an event yeah someone<00:22:57.870> bought<00:22:58.020> a<00:22:58.049> car<00:22:58.290> and<00:22:59.030> then<00:23:00.030> sends<00:23:00.480> the 00:23:00.650 --> 00:23:00.660 align:start position:0% someone bought a car and then sends the 00:23:00.660 --> 00:23:03.320 align:start position:0% someone bought a car and then sends the money<00:23:00.840> off<00:23:01.049> out<00:23:01.620> to<00:23:02.100> somewhere<00:23:02.400> else<00:23:02.490> doesn't 00:23:03.320 --> 00:23:03.330 align:start position:0% money off out to somewhere else doesn't 00:23:03.330 --> 00:23:05.480 align:start position:0% money off out to somewhere else doesn't actually<00:23:03.660> make<00:23:04.169> any<00:23:04.230> storage<00:23:04.710> changes<00:23:05.100> about 00:23:05.480 --> 00:23:05.490 align:start position:0% actually make any storage changes about 00:23:05.490 --> 00:23:10.840 align:start position:0% actually make any storage changes about who<00:23:05.730> owns<00:23:05.970> the<00:23:06.809> cards<00:23:07.640> so<00:23:08.640> there's<00:23:08.820> no<00:23:08.970> like<00:23:09.210> I 00:23:10.840 --> 00:23:10.850 align:start position:0% who owns the cards so there's no like I 00:23:10.850 --> 00:23:13.490 align:start position:0% who owns the cards so there's no like I have<00:23:11.850> a<00:23:11.880> little<00:23:12.090> external<00:23:12.660> context<00:23:13.230> on<00:23:13.350> this 00:23:13.490 --> 00:23:13.500 align:start position:0% have a little external context on this 00:23:13.500 --> 00:23:15.650 align:start position:0% have a little external context on this yeah<00:23:14.070> the<00:23:14.549> author<00:23:14.700> of<00:23:14.880> this<00:23:15.059> contract<00:23:15.450> is 00:23:15.650 --> 00:23:15.660 align:start position:0% yeah the author of this contract is 00:23:15.660 --> 00:23:17.600 align:start position:0% yeah the author of this contract is present<00:23:16.320> at<00:23:16.440> Def<00:23:16.590> Con<00:23:16.620> and<00:23:17.100> in<00:23:17.160> selling 00:23:17.600 --> 00:23:17.610 align:start position:0% present at Def Con and in selling 00:23:17.610 --> 00:23:20.360 align:start position:0% present at Def Con and in selling physical<00:23:18.090> cards<00:23:18.450> if<00:23:19.110> you<00:23:19.380> transfer<00:23:19.890> one<00:23:20.070> ether 00:23:20.360 --> 00:23:20.370 align:start position:0% physical cards if you transfer one ether 00:23:20.370 --> 00:23:22.940 align:start position:0% physical cards if you transfer one ether using<00:23:20.640> the<00:23:20.730> buy<00:23:20.850> card<00:23:21.120> function<00:23:21.600> with<00:23:21.900> a<00:23:22.110> hash 00:23:22.940 --> 00:23:22.950 align:start position:0% using the buy card function with a hash 00:23:22.950 --> 00:23:25.100 align:start position:0% using the buy card function with a hash and<00:23:23.309> then<00:23:23.820> you<00:23:23.910> provide<00:23:24.270> him<00:23:24.450> in<00:23:24.600> person<00:23:24.809> was 00:23:25.100 --> 00:23:25.110 align:start position:0% and then you provide him in person was 00:23:25.110 --> 00:23:26.480 align:start position:0% and then you provide him in person was the<00:23:25.230> preimage<00:23:25.500> he<00:23:25.950> will<00:23:26.100> give<00:23:26.280> you<00:23:26.370> the 00:23:26.480 --> 00:23:26.490 align:start position:0% the preimage he will give you the 00:23:26.490 --> 00:23:28.250 align:start position:0% the preimage he will give you the physical<00:23:26.640> card<00:23:27.000> right<00:23:27.450> so<00:23:27.750> it's<00:23:27.900> a<00:23:28.020> one-off 00:23:28.250 --> 00:23:28.260 align:start position:0% physical card right so it's a one-off 00:23:28.260 --> 00:23:30.409 align:start position:0% physical card right so it's a one-off purchase<00:23:28.980> physically<00:23:29.610> that<00:23:29.820> you<00:23:29.970> get<00:23:30.240> the 00:23:30.409 --> 00:23:30.419 align:start position:0% purchase physically that you get the 00:23:30.419 --> 00:23:32.690 align:start position:0% purchase physically that you get the Gordon<00:23:30.929> right<00:23:31.530> so<00:23:31.770> that's<00:23:31.919> where<00:23:32.190> there's<00:23:32.460> no 00:23:32.690 --> 00:23:32.700 align:start position:0% Gordon right so that's where there's no 00:23:32.700 --> 00:23:36.080 align:start position:0% Gordon right so that's where there's no actual<00:23:33.450> state<00:23:33.780> change<00:23:34.910> meaningful<00:23:35.910> state 00:23:36.080 --> 00:23:36.090 align:start position:0% actual state change meaningful state 00:23:36.090 --> 00:23:39.010 align:start position:0% actual state change meaningful state change<00:23:36.299> in<00:23:36.450> the<00:23:36.510> bike<00:23:36.660> or<00:23:36.870> function<00:23:37.320> sorry 00:23:39.010 --> 00:23:39.020 align:start position:0% change in the bike or function sorry 00:23:39.020 --> 00:23:41.210 align:start position:0% change in the bike or function sorry along<00:23:40.020> the<00:23:40.169> question<00:23:40.440> of<00:23:40.530> asking<00:23:40.650> questions 00:23:41.210 --> 00:23:41.220 align:start position:0% along the question of asking questions 00:23:41.220 --> 00:23:45.380 align:start position:0% along the question of asking questions and<00:23:41.400> maybe<00:23:42.260> you<00:23:43.260> know<00:23:43.380> silly<00:23:43.830> but<00:23:44.150> use<00:23:45.150> of<00:23:45.179> a 00:23:45.380 --> 00:23:45.390 align:start position:0% and maybe you know silly but use of a 00:23:45.390 --> 00:23:47.720 align:start position:0% and maybe you know silly but use of a pre-image<00:23:45.870> for<00:23:46.260> securing<00:23:47.160> an<00:23:47.250> asset<00:23:47.549> means 00:23:47.720 --> 00:23:47.730 align:start position:0% pre-image for securing an asset means 00:23:47.730 --> 00:23:49.610 align:start position:0% pre-image for securing an asset means that<00:23:47.880> you<00:23:47.970> may<00:23:48.090> be<00:23:48.150> front-run<00:23:48.690> because<00:23:49.020> it's<00:23:49.320> a 00:23:49.610 --> 00:23:49.620 align:start position:0% that you may be front-run because it's a 00:23:49.620 --> 00:23:51.919 align:start position:0% that you may be front-run because it's a symmetric<00:23:50.460> secret<00:23:50.850> meaning<00:23:51.360> that<00:23:51.480> if<00:23:51.870> you 00:23:51.919 --> 00:23:51.929 align:start position:0% symmetric secret meaning that if you 00:23:51.929 --> 00:23:53.930 align:start position:0% symmetric secret meaning that if you observe<00:23:52.559> someone<00:23:53.010> attempting<00:23:53.429> to<00:23:53.460> claim<00:23:53.760> this 00:23:53.930 --> 00:23:53.940 align:start position:0% observe someone attempting to claim this 00:23:53.940 --> 00:23:55.700 align:start position:0% observe someone attempting to claim this and<00:23:54.179> you're<00:23:54.270> not<00:23:54.600> modifying<00:23:55.080> the<00:23:55.230> state<00:23:55.500> of 00:23:55.700 --> 00:23:55.710 align:start position:0% and you're not modifying the state of 00:23:55.710 --> 00:23:57.680 align:start position:0% and you're not modifying the state of the<00:23:55.860> actual<00:23:56.160> contract<00:23:56.549> someone<00:23:57.419> else<00:23:57.540> can 00:23:57.680 --> 00:23:57.690 align:start position:0% the actual contract someone else can 00:23:57.690 --> 00:23:58.940 align:start position:0% the actual contract someone else can observe<00:23:57.990> the<00:23:58.169> fact<00:23:58.380> that<00:23:58.470> you've<00:23:58.620> emitted 00:23:58.940 --> 00:23:58.950 align:start position:0% observe the fact that you've emitted 00:23:58.950 --> 00:24:00.620 align:start position:0% observe the fact that you've emitted that<00:23:59.040> transaction<00:23:59.700> and<00:23:59.880> attempt<00:24:00.179> to<00:24:00.210> perform 00:24:00.620 --> 00:24:00.630 align:start position:0% that transaction and attempt to perform 00:24:00.630 --> 00:24:03.620 align:start position:0% that transaction and attempt to perform the<00:24:00.780> same<00:24:00.929> action<00:24:01.320> to<00:24:01.530> claim<00:24:01.919> the<00:24:02.100> card<00:24:02.340> yep<00:24:02.760> so 00:24:03.620 --> 00:24:03.630 align:start position:0% the same action to claim the card yep so 00:24:03.630 --> 00:24:06.799 align:start position:0% the same action to claim the card yep so that<00:24:03.990> would<00:24:04.440> be<00:24:04.559> a<00:24:04.590> concern<00:24:05.190> actually<00:24:05.700> in<00:24:06.179> this 00:24:06.799 --> 00:24:06.809 align:start position:0% that would be a concern actually in this 00:24:06.809 --> 00:24:08.990 align:start position:0% that would be a concern actually in this specific<00:24:07.470> case<00:24:07.650> all<00:24:07.980> you<00:24:08.010> would<00:24:08.309> be<00:24:08.340> doing<00:24:08.520> is 00:24:08.990 --> 00:24:09.000 align:start position:0% specific case all you would be doing is 00:24:09.000 --> 00:24:11.419 align:start position:0% specific case all you would be doing is just<00:24:09.600> like<00:24:10.140> paying<00:24:10.440> for<00:24:10.530> someone<00:24:10.799> else's<00:24:11.160> card 00:24:11.419 --> 00:24:11.429 align:start position:0% just like paying for someone else's card 00:24:11.429 --> 00:24:14.180 align:start position:0% just like paying for someone else's card right<00:24:11.880> because<00:24:12.780> I<00:24:12.840> think<00:24:12.900> like<00:24:13.200> the<00:24:13.380> the<00:24:13.679> the 00:24:14.180 --> 00:24:14.190 align:start position:0% right because I think like the the the 00:24:14.190 --> 00:24:18.650 align:start position:0% right because I think like the the the data<00:24:14.370> isn't<00:24:15.679> exactly<00:24:16.679> a<00:24:16.850> secret<00:24:17.850> like<00:24:18.480> it's 00:24:18.650 --> 00:24:18.660 align:start position:0% data isn't exactly a secret like it's 00:24:18.660 --> 00:24:20.270 align:start position:0% data isn't exactly a secret like it's not<00:24:18.900> meant<00:24:19.140> to<00:24:19.169> be<00:24:19.260> a<00:24:19.350> secret<00:24:19.470> right<00:24:19.800> well<00:24:20.160> it's 00:24:20.270 --> 00:24:20.280 align:start position:0% not meant to be a secret right well it's 00:24:20.280 --> 00:24:21.430 align:start position:0% not meant to be a secret right well it's a<00:24:20.370> hash<00:24:20.520> of<00:24:20.700> a<00:24:20.760> see 00:24:21.430 --> 00:24:21.440 align:start position:0% a hash of a see 00:24:21.440 --> 00:24:23.680 align:start position:0% a hash of a see right<00:24:22.430> so<00:24:22.640> even<00:24:22.850> if<00:24:22.940> you<00:24:23.030> submit<00:24:23.330> somebody's 00:24:23.680 --> 00:24:23.690 align:start position:0% right so even if you submit somebody's 00:24:23.690 --> 00:24:24.940 align:start position:0% right so even if you submit somebody's else's<00:24:23.930> hash<00:24:24.140> of<00:24:24.290> a<00:24:24.350> secret<00:24:24.620> then<00:24:24.710> you<00:24:24.800> just 00:24:24.940 --> 00:24:24.950 align:start position:0% else's hash of a secret then you just 00:24:24.950 --> 00:24:26.200 align:start position:0% else's hash of a secret then you just want<00:24:25.070> to<00:24:25.100> be<00:24:25.190> able<00:24:25.250> to<00:24:25.340> reveal<00:24:25.670> it<00:24:25.790> in<00:24:25.850> person 00:24:26.200 --> 00:24:26.210 align:start position:0% want to be able to reveal it in person 00:24:26.210 --> 00:24:27.190 align:start position:0% want to be able to reveal it in person yes<00:24:26.390> and<00:24:26.660> if<00:24:26.810> you're<00:24:26.930> talking<00:24:27.140> about 00:24:27.190 --> 00:24:27.200 align:start position:0% yes and if you're talking about 00:24:27.200 --> 00:24:28.690 align:start position:0% yes and if you're talking about front-running<00:24:27.680> Lee<00:24:27.830> revealed<00:24:27.980> in<00:24:28.400> in<00:24:28.520> this 00:24:28.690 --> 00:24:28.700 align:start position:0% front-running Lee revealed in in this 00:24:28.700 --> 00:24:30.490 align:start position:0% front-running Lee revealed in in this case<00:24:28.940> this<00:24:29.180> is<00:24:29.240> an<00:24:29.450> innocent<00:24:29.960> reveal<00:24:30.170> so<00:24:30.410> you 00:24:30.490 --> 00:24:30.500 align:start position:0% case this is an innocent reveal so you 00:24:30.500 --> 00:24:31.930 align:start position:0% case this is an innocent reveal so you would<00:24:30.590> have<00:24:30.680> to<00:24:30.800> literally<00:24:31.100> jump<00:24:31.460> in<00:24:31.610> front<00:24:31.820> of 00:24:31.930 --> 00:24:31.940 align:start position:0% would have to literally jump in front of 00:24:31.940 --> 00:24:37.360 align:start position:0% would have to literally jump in front of them<00:24:32.060> and<00:24:32.180> shout<00:24:32.420> the<00:24:32.600> secret<00:24:35.890> but<00:24:36.890> yeah<00:24:37.040> it's 00:24:37.360 --> 00:24:37.370 align:start position:0% them and shout the secret but yeah it's 00:24:37.370 --> 00:24:39.310 align:start position:0% them and shout the secret but yeah it's a<00:24:37.400> good<00:24:37.520> point<00:24:37.760> like<00:24:38.030> about<00:24:38.420> hair<00:24:38.810> or<00:24:39.050> commit 00:24:39.310 --> 00:24:39.320 align:start position:0% a good point like about hair or commit 00:24:39.320 --> 00:24:42.120 align:start position:0% a good point like about hair or commit and<00:24:39.410> reveal<00:24:39.620> schemes<00:24:39.950> in<00:24:40.100> general<00:24:40.430> you<00:24:40.670> if<00:24:40.940> you 00:24:42.120 --> 00:24:42.130 align:start position:0% and reveal schemes in general you if you 00:24:42.130 --> 00:24:44.590 align:start position:0% and reveal schemes in general you if you you<00:24:43.130> need<00:24:43.340> either<00:24:43.610> the<00:24:43.760> commit<00:24:44.180> needs<00:24:44.390> to 00:24:44.590 --> 00:24:44.600 align:start position:0% you need either the commit needs to 00:24:44.600 --> 00:24:46.330 align:start position:0% you need either the commit needs to contain<00:24:44.900> some<00:24:45.140> data<00:24:45.350> that<00:24:45.620> makes<00:24:46.040> it<00:24:46.190> possible 00:24:46.330 --> 00:24:46.340 align:start position:0% contain some data that makes it possible 00:24:46.340 --> 00:24:48.160 align:start position:0% contain some data that makes it possible impossible<00:24:46.970> for<00:24:47.330> someone<00:24:47.480> else<00:24:47.660> to<00:24:47.810> front-run 00:24:48.160 --> 00:24:48.170 align:start position:0% impossible for someone else to front-run 00:24:48.170 --> 00:24:50.440 align:start position:0% impossible for someone else to front-run it<00:24:48.290> such<00:24:48.560> as<00:24:48.710> the<00:24:48.830> target<00:24:49.130> address<00:24:49.220> or<00:24:50.120> you 00:24:50.440 --> 00:24:50.450 align:start position:0% it such as the target address or you 00:24:50.450 --> 00:24:51.820 align:start position:0% it such as the target address or you need<00:24:50.630> to<00:24:50.720> use<00:24:50.840> something<00:24:51.080> other<00:24:51.260> than<00:24:51.440> just<00:24:51.740> a 00:24:51.820 --> 00:24:51.830 align:start position:0% need to use something other than just a 00:24:51.830 --> 00:24:54.600 align:start position:0% need to use something other than just a simple<00:24:52.010> hash<00:24:52.250> reveal<00:24:52.550> like<00:24:52.910> using<00:24:53.210> a<00:24:53.450> key<00:24:54.170> pair 00:24:54.600 --> 00:24:54.610 align:start position:0% simple hash reveal like using a key pair 00:24:54.610 --> 00:24:56.860 align:start position:0% simple hash reveal like using a key pair so<00:24:55.610> quick<00:24:55.790> question<00:24:55.820> I<00:24:56.150> didn't<00:24:56.420> realize<00:24:56.750> the 00:24:56.860 --> 00:24:56.870 align:start position:0% so quick question I didn't realize the 00:24:56.870 --> 00:24:58.300 align:start position:0% so quick question I didn't realize the context<00:24:57.170> of<00:24:57.260> this<00:24:57.350> contract<00:24:57.830> but<00:24:58.100> you<00:24:58.190> just 00:24:58.300 --> 00:24:58.310 align:start position:0% context of this contract but you just 00:24:58.310 --> 00:25:00.010 align:start position:0% context of this contract but you just mentioned<00:24:58.670> that<00:24:58.730> how-to<00:24:58.970> is<00:24:59.150> house<00:24:59.690> the<00:24:59.840> owner 00:25:00.010 --> 00:25:00.020 align:start position:0% mentioned that how-to is house the owner 00:25:00.020 --> 00:25:01.570 align:start position:0% mentioned that how-to is house the owner actually<00:25:00.560> issued<00:25:01.040> the<00:25:01.130> card<00:25:01.280> to<00:25:01.460> the<00:25:01.550> person 00:25:01.570 --> 00:25:01.580 align:start position:0% actually issued the card to the person 00:25:01.580 --> 00:25:04.060 align:start position:0% actually issued the card to the person he'd<00:25:02.270> hands<00:25:02.660> it<00:25:02.750> to<00:25:02.870> them<00:25:02.990> in<00:25:03.110> person<00:25:03.350> I<00:25:03.830> move 00:25:04.060 --> 00:25:04.070 align:start position:0% he'd hands it to them in person I move 00:25:04.070 --> 00:25:06.220 align:start position:0% he'd hands it to them in person I move it<00:25:04.190> in<00:25:04.250> the<00:25:04.310> contract<00:25:04.640> or<00:25:04.910> or<00:25:05.900> they<00:25:06.020> don't 00:25:06.220 --> 00:25:06.230 align:start position:0% it in the contract or or they don't 00:25:06.230 --> 00:25:16.600 align:start position:0% it in the contract or or they don't they're<00:25:06.920> buying<00:25:07.220> a<00:25:07.370> physical<00:25:07.700> object<00:25:15.430> each<00:25:16.430> of 00:25:16.600 --> 00:25:16.610 align:start position:0% they're buying a physical object each of 00:25:16.610 --> 00:25:18.190 align:start position:0% they're buying a physical object each of these<00:25:16.730> each<00:25:17.030> of<00:25:17.090> these<00:25:17.270> cards<00:25:17.750> he's<00:25:17.900> handing 00:25:18.190 --> 00:25:18.200 align:start position:0% these each of these cards he's handing 00:25:18.200 --> 00:25:20.590 align:start position:0% these each of these cards he's handing out<00:25:18.290> has<00:25:18.680> a<00:25:18.710> key<00:25:18.980> pair<00:25:19.220> on<00:25:19.340> it<00:25:19.490> and<00:25:19.790> each<00:25:20.210> of 00:25:20.590 --> 00:25:20.600 align:start position:0% out has a key pair on it and each of 00:25:20.600 --> 00:25:22.540 align:start position:0% out has a key pair on it and each of those<00:25:21.050> cards<00:25:21.530> is<00:25:21.650> listed<00:25:22.010> in<00:25:22.040> the<00:25:22.130> contract 00:25:22.540 --> 00:25:22.550 align:start position:0% those cards is listed in the contract 00:25:22.550 --> 00:25:24.880 align:start position:0% those cards is listed in the contract here<00:25:22.760> and<00:25:22.970> owns<00:25:23.090> one<00:25:23.450> token<00:25:23.720> and<00:25:24.410> then<00:25:24.650> he<00:25:24.740> will 00:25:24.880 --> 00:25:24.890 align:start position:0% here and owns one token and then he will 00:25:24.890 --> 00:25:26.170 align:start position:0% here and owns one token and then he will physically<00:25:25.340> give<00:25:25.490> you<00:25:25.580> the<00:25:25.670> physical<00:25:26.000> card 00:25:26.170 --> 00:25:26.180 align:start position:0% physically give you the physical card 00:25:26.180 --> 00:25:27.850 align:start position:0% physically give you the physical card and<00:25:26.420> you<00:25:26.480> will<00:25:26.600> now<00:25:26.810> own<00:25:26.990> the<00:25:27.170> key<00:25:27.320> PFF<00:25:27.740> owns 00:25:27.850 --> 00:25:27.860 align:start position:0% and you will now own the key PFF owns 00:25:27.860 --> 00:25:31.990 align:start position:0% and you will now own the key PFF owns the<00:25:28.130> token<00:25:30.670> representing<00:25:31.670> that<00:25:31.760> you<00:25:31.850> have<00:25:31.970> a 00:25:31.990 --> 00:25:32.000 align:start position:0% the token representing that you have a 00:25:32.000 --> 00:25:41.620 align:start position:0% the token representing that you have a card<00:25:35.500> oh<00:25:38.260> yeah<00:25:40.030> they<00:25:41.030> should<00:25:41.060> probably<00:25:41.330> be<00:25:41.540> in 00:25:41.620 --> 00:25:41.630 align:start position:0% card oh yeah they should probably be in 00:25:41.630 --> 00:25:48.100 align:start position:0% card oh yeah they should probably be in if<00:25:41.900> days<00:25:42.140> yeah<00:25:42.560> it's<00:25:42.800> a<00:25:42.920> weird<00:25:46.360> I<00:25:47.360> just<00:25:47.840> like<00:25:47.990> to 00:25:48.100 --> 00:25:48.110 align:start position:0% if days yeah it's a weird I just like to 00:25:48.110 --> 00:25:50.530 align:start position:0% if days yeah it's a weird I just like to imagine<00:25:48.320> one<00:25:49.000> one<00:25:50.000> more<00:25:50.150> thing<00:25:50.330> on<00:25:50.450> this 00:25:50.530 --> 00:25:50.540 align:start position:0% imagine one one more thing on this 00:25:50.540 --> 00:25:51.910 align:start position:0% imagine one one more thing on this contract<00:25:50.810> before<00:25:50.960> we<00:25:51.140> move<00:25:51.380> on<00:25:51.500> to<00:25:51.620> the<00:25:51.710> next 00:25:51.910 --> 00:25:51.920 align:start position:0% contract before we move on to the next 00:25:51.920 --> 00:25:53.140 align:start position:0% contract before we move on to the next and<00:25:52.070> if<00:25:52.130> one<00:25:52.370> of<00:25:52.460> you<00:25:52.550> guys<00:25:52.730> can<00:25:52.940> start 00:25:53.140 --> 00:25:53.150 align:start position:0% and if one of you guys can start 00:25:53.150 --> 00:25:55.570 align:start position:0% and if one of you guys can start bringing<00:25:53.660> up<00:25:53.720> the<00:25:53.870> next<00:25:54.080> contract<00:25:54.520> so<00:25:55.520> we 00:25:55.570 --> 00:25:55.580 align:start position:0% bringing up the next contract so we 00:25:55.580 --> 00:25:59.950 align:start position:0% bringing up the next contract so we switch<00:25:55.850> over<00:25:55.970> to<00:25:56.090> that<00:25:56.180> and<00:25:58.630> this<00:25:59.630> I<00:25:59.870> think 00:25:59.950 --> 00:25:59.960 align:start position:0% switch over to that and this I think 00:25:59.960 --> 00:26:01.930 align:start position:0% switch over to that and this I think it's<00:26:00.260> very<00:26:00.350> good<00:26:00.440> to<00:26:01.070> have<00:26:01.100> an<00:26:01.250> emergen 00:26:01.930 --> 00:26:01.940 align:start position:0% it's very good to have an emergen 00:26:01.940 --> 00:26:04.180 align:start position:0% it's very good to have an emergen on<00:26:02.150> a<00:26:02.210> contract<00:26:02.680> because<00:26:03.680> you<00:26:03.890> never<00:26:04.010> know 00:26:04.180 --> 00:26:04.190 align:start position:0% on a contract because you never know 00:26:04.190 --> 00:26:07.240 align:start position:0% on a contract because you never know what<00:26:04.370> people<00:26:04.400> are<00:26:04.730> going<00:26:04.850> to<00:26:04.940> send<00:26:05.120> to<00:26:05.300> it<00:26:06.250> so 00:26:07.240 --> 00:26:07.250 align:start position:0% what people are going to send to it so 00:26:07.250 --> 00:26:09.370 align:start position:0% what people are going to send to it so even<00:26:07.430> if<00:26:07.520> you<00:26:07.640> don't<00:26:07.790> expect<00:26:08.240> I<00:26:08.660> mean<00:26:09.140> you<00:26:09.230> can 00:26:09.370 --> 00:26:09.380 align:start position:0% even if you don't expect I mean you can 00:26:09.380 --> 00:26:11.890 align:start position:0% even if you don't expect I mean you can prevent<00:26:09.770> getting<00:26:10.330> ether<00:26:11.330> but<00:26:11.660> you<00:26:11.720> can't 00:26:11.890 --> 00:26:11.900 align:start position:0% prevent getting ether but you can't 00:26:11.900 --> 00:26:13.750 align:start position:0% prevent getting ether but you can't prevent<00:26:12.110> getting<00:26:12.290> tokens<00:26:12.890> so<00:26:13.100> if<00:26:13.250> the<00:26:13.400> tokens 00:26:13.750 --> 00:26:13.760 align:start position:0% prevent getting tokens so if the tokens 00:26:13.760 --> 00:26:15.370 align:start position:0% prevent getting tokens so if the tokens wind<00:26:13.970> up<00:26:14.090> there<00:26:14.300> is<00:26:14.360> nice<00:26:14.600> if<00:26:14.840> the<00:26:14.990> owner<00:26:15.140> can 00:26:15.370 --> 00:26:15.380 align:start position:0% wind up there is nice if the owner can 00:26:15.380 --> 00:26:18.520 align:start position:0% wind up there is nice if the owner can ship<00:26:15.950> them<00:26:16.100> up<00:26:16.250> somewhere<00:26:16.580> else<00:26:16.810> and<00:26:17.810> I<00:26:18.470> think 00:26:18.520 --> 00:26:18.530 align:start position:0% ship them up somewhere else and I think 00:26:18.530 --> 00:26:21.400 align:start position:0% ship them up somewhere else and I think this<00:26:18.860> kind<00:26:19.070> of<00:26:19.220> also<00:26:19.310> nicely<00:26:19.610> demonstrates<00:26:20.410> a 00:26:21.400 --> 00:26:21.410 align:start position:0% this kind of also nicely demonstrates a 00:26:21.410 --> 00:26:23.290 align:start position:0% this kind of also nicely demonstrates a minor<00:26:22.160> pet<00:26:22.430> peeve<00:26:22.670> that<00:26:22.880> I<00:26:22.910> have<00:26:23.120> with 00:26:23.290 --> 00:26:23.300 align:start position:0% minor pet peeve that I have with 00:26:23.300 --> 00:26:28.720 align:start position:0% minor pet peeve that I have with solidity<00:26:23.720> and<00:26:25.300> it<00:26:26.300> is<00:26:26.540> that<00:26:27.340> owner<00:26:28.340> in<00:26:28.550> this 00:26:28.720 --> 00:26:28.730 align:start position:0% solidity and it is that owner in this 00:26:28.730 --> 00:26:32.050 align:start position:0% solidity and it is that owner in this case<00:26:29.030> is<00:26:29.360> an<00:26:29.630> address<00:26:30.110> and<00:26:30.920> doing<00:26:31.280> the<00:26:31.580> only 00:26:32.050 --> 00:26:32.060 align:start position:0% case is an address and doing the only 00:26:32.060 --> 00:26:34.600 align:start position:0% case is an address and doing the only butt<00:26:32.420> transfer<00:26:32.900> actually<00:26:33.710> means<00:26:33.920> you 00:26:34.600 --> 00:26:34.610 align:start position:0% butt transfer actually means you 00:26:34.610 --> 00:26:39.100 align:start position:0% butt transfer actually means you doing<00:26:34.820> a<00:26:35.000> call<00:26:35.270> with<00:26:36.070> next<00:26:37.070> to<00:26:37.190> no<00:26:37.340> gas<00:26:37.720> which<00:26:38.720> I 00:26:39.100 --> 00:26:39.110 align:start position:0% doing a call with next to no gas which I 00:26:39.110 --> 00:26:41.760 align:start position:0% doing a call with next to no gas which I cannot<00:26:39.679> is<00:26:40.010> not<00:26:40.190> vulnerable<00:26:40.340> to<00:26:40.730> rien 00:26:41.760 --> 00:26:41.770 align:start position:0% cannot is not vulnerable to rien 00:26:41.770 --> 00:26:45.070 align:start position:0% cannot is not vulnerable to rien principal<00:26:42.770> so<00:26:43.100> protects<00:26:43.670> it<00:26:43.790> if<00:26:43.940> it<00:26:44.390> fails<00:26:44.720> it 00:26:45.070 --> 00:26:45.080 align:start position:0% principal so protects it if it fails it 00:26:45.080 --> 00:26:48.700 align:start position:0% principal so protects it if it fails it would<00:26:45.290> throw<00:26:45.640> whereas<00:26:46.640> in<00:26:47.299> this<00:26:47.809> style<00:26:48.080> where 00:26:48.700 --> 00:26:48.710 align:start position:0% would throw whereas in this style where 00:26:48.710 --> 00:26:50.770 align:start position:0% would throw whereas in this style where it's<00:26:48.830> an<00:26:48.920> ear<00:26:49.040> see<00:26:49.340> 20<00:26:49.730> interface<00:26:50.120> and<00:26:50.390> this 00:26:50.770 --> 00:26:50.780 align:start position:0% it's an ear see 20 interface and this 00:26:50.780 --> 00:26:53.830 align:start position:0% it's an ear see 20 interface and this looks<00:26:51.140> oddly<00:26:51.470> similar<00:26:52.309> I<00:26:52.910> mean<00:26:53.690> it's 00:26:53.830 --> 00:26:53.840 align:start position:0% looks oddly similar I mean it's 00:26:53.840 --> 00:26:56.110 align:start position:0% looks oddly similar I mean it's something<00:26:54.500> dot<00:26:54.890> transfer<00:26:55.429> but<00:26:55.610> actually<00:26:56.000> this 00:26:56.110 --> 00:26:56.120 align:start position:0% something dot transfer but actually this 00:26:56.120 --> 00:26:58.720 align:start position:0% something dot transfer but actually this is<00:26:56.179> a<00:26:56.390> full-blown<00:26:56.780> call<00:26:57.650> with<00:26:58.370> all<00:26:58.490> available 00:26:58.720 --> 00:26:58.730 align:start position:0% is a full-blown call with all available 00:26:58.730 --> 00:27:03.070 align:start position:0% is a full-blown call with all available gas<00:26:59.299> and<00:27:00.880> totally<00:27:01.880> different<00:27:02.240> semantics<00:27:02.809> it 00:27:03.070 --> 00:27:03.080 align:start position:0% gas and totally different semantics it 00:27:03.080 --> 00:27:05.590 align:start position:0% gas and totally different semantics it also<00:27:03.230> has<00:27:03.740> a<00:27:03.770> return<00:27:04.220> value<00:27:04.490> which<00:27:04.940> you<00:27:05.150> might 00:27:05.590 --> 00:27:05.600 align:start position:0% also has a return value which you might 00:27:05.600 --> 00:27:10.120 align:start position:0% also has a return value which you might might<00:27:05.990> not<00:27:06.200> read<00:27:06.440> out<00:27:07.450> and<00:27:08.559> as<00:27:09.559> an<00:27:09.679> auditor 00:27:10.120 --> 00:27:10.130 align:start position:0% might not read out and as an auditor 00:27:10.130 --> 00:27:12.669 align:start position:0% might not read out and as an auditor it's<00:27:10.630> when<00:27:11.630> you're<00:27:11.720> doing<00:27:11.900> manual<00:27:12.350> or<00:27:12.440> did<00:27:12.590> you 00:27:12.669 --> 00:27:12.679 align:start position:0% it's when you're doing manual or did you 00:27:12.679 --> 00:27:14.320 align:start position:0% it's when you're doing manual or did you have<00:27:12.799> to<00:27:12.890> be<00:27:12.980> really<00:27:13.280> careful<00:27:13.790> about<00:27:13.910> all 00:27:14.320 --> 00:27:14.330 align:start position:0% have to be really careful about all 00:27:14.330 --> 00:27:16.150 align:start position:0% have to be really careful about all these<00:27:14.450> things<00:27:14.720> is<00:27:14.960> this<00:27:15.080> an<00:27:15.230> address<00:27:15.740> or<00:27:16.010> is 00:27:16.150 --> 00:27:16.160 align:start position:0% these things is this an address or is 00:27:16.160 --> 00:27:19.810 align:start position:0% these things is this an address or is this<00:27:16.400> an<00:27:17.179> address<00:27:17.630> in<00:27:17.809> the<00:27:17.929> geese<00:27:18.200> of<00:27:18.590> an<00:27:18.890> of<00:27:19.340> an 00:27:19.810 --> 00:27:19.820 align:start position:0% this an address in the geese of an of an 00:27:19.820 --> 00:27:26.580 align:start position:0% this an address in the geese of an of an interface<00:27:20.660> and<00:27:21.190> actually<00:27:22.190> a<00:27:22.370> full-blown<00:27:22.970> call 00:27:26.580 --> 00:27:26.590 align:start position:0% 00:27:26.590 --> 00:27:29.560 align:start position:0% that's<00:27:27.590> that's<00:27:27.919> kind<00:27:28.190> of<00:27:28.220> a<00:27:28.330> thing<00:27:29.330> that<00:27:29.360> you 00:27:29.560 --> 00:27:29.570 align:start position:0% that's that's kind of a thing that you 00:27:29.570 --> 00:27:31.810 align:start position:0% that's that's kind of a thing that you can<00:27:29.720> trip<00:27:29.990> on<00:27:30.169> are<00:27:30.410> they<00:27:30.620> are<00:27:30.980> wasn't<00:27:31.700> there 00:27:31.810 --> 00:27:31.820 align:start position:0% can trip on are they are wasn't there 00:27:31.820 --> 00:27:36.340 align:start position:0% can trip on are they are wasn't there like<00:27:32.320> like<00:27:33.320> a<00:27:34.299> talk<00:27:35.299> of<00:27:35.330> deprecating<00:27:36.020> that<00:27:36.169> or 00:27:36.340 --> 00:27:36.350 align:start position:0% like like a talk of deprecating that or 00:27:36.350 --> 00:27:37.210 align:start position:0% like like a talk of deprecating that or or<00:27:36.590> no 00:27:37.210 --> 00:27:37.220 align:start position:0% or no 00:27:37.220 --> 00:27:52.440 align:start position:0% or no a<00:27:37.250> recent<00:27:37.790> I'm<00:27:38.000> with<00:27:38.720> it<00:27:38.809> I<00:27:38.900> simply<00:27:48.520> okay<00:27:51.100> so 00:27:52.440 --> 00:27:52.450 align:start position:0% a recent I'm with it I simply okay so 00:27:52.450 --> 00:27:54.789 align:start position:0% a recent I'm with it I simply okay so transfer<00:27:53.450> was<00:27:53.630> a<00:27:53.660> recent<00:27:54.049> introduction<00:27:54.410> to 00:27:54.789 --> 00:27:54.799 align:start position:0% transfer was a recent introduction to 00:27:54.799 --> 00:27:56.380 align:start position:0% transfer was a recent introduction to the<00:27:54.890> address<00:27:55.190> object<00:27:55.640> is<00:27:55.850> there 00:27:56.380 --> 00:27:56.390 align:start position:0% the address object is there 00:27:56.390 --> 00:27:58.210 align:start position:0% the address object is there how<00:27:56.780> will<00:27:57.020> you<00:27:57.169> transfer<00:27:57.410> to<00:27:57.799> an<00:27:57.890> address<00:27:58.070> in 00:27:58.210 --> 00:27:58.220 align:start position:0% how will you transfer to an address in 00:27:58.220 --> 00:28:12.730 align:start position:0% how will you transfer to an address in future<00:28:00.549> let's<00:28:01.549> see<00:28:10.809> okay<00:28:11.809> so<00:28:12.140> there<00:28:12.500> anyone 00:28:12.730 --> 00:28:12.740 align:start position:0% future let's see okay so there anyone 00:28:12.740 --> 00:28:14.080 align:start position:0% future let's see okay so there anyone that<00:28:12.860> didn't<00:28:13.100> hear<00:28:13.250> there<00:28:13.520> will<00:28:13.610> be<00:28:13.669> a<00:28:13.790> new 00:28:14.080 --> 00:28:14.090 align:start position:0% that didn't hear there will be a new 00:28:14.090 --> 00:28:16.570 align:start position:0% that didn't hear there will be a new data<00:28:14.929> type<00:28:15.080> payable<00:28:15.740> address<00:28:16.070> which<00:28:16.309> you<00:28:16.460> can 00:28:16.570 --> 00:28:16.580 align:start position:0% data type payable address which you can 00:28:16.580 --> 00:28:18.130 align:start position:0% data type payable address which you can cast<00:28:16.730> an<00:28:16.910> address<00:28:17.179> to<00:28:17.390> and<00:28:17.600> it<00:28:17.660> only<00:28:17.750> has<00:28:17.990> that 00:28:18.130 --> 00:28:18.140 align:start position:0% cast an address to and it only has that 00:28:18.140 --> 00:28:25.980 align:start position:0% cast an address to and it only has that method<00:28:18.530> if<00:28:18.650> it's<00:28:18.830> a<00:28:18.919> payroll<00:28:19.130> type<00:28:21.610> sorry 00:28:25.980 --> 00:28:25.990 align:start position:0% 00:28:25.990 --> 00:28:27.940 align:start position:0% so<00:28:26.990> the<00:28:27.080> comment<00:28:27.320> is<00:28:27.380> you<00:28:27.500> have<00:28:27.620> to<00:28:27.710> make<00:28:27.860> it 00:28:27.940 --> 00:28:27.950 align:start position:0% so the comment is you have to make it 00:28:27.950 --> 00:28:29.260 align:start position:0% so the comment is you have to make it explicit<00:28:28.220> in<00:28:28.490> the<00:28:28.549> constructor<00:28:29.030> for<00:28:29.150> that 00:28:29.260 --> 00:28:29.270 align:start position:0% explicit in the constructor for that 00:28:29.270 --> 00:28:31.780 align:start position:0% explicit in the constructor for that happened<00:28:29.600> but<00:28:30.080> what<00:28:30.950> I<00:28:30.980> mean<00:28:31.100> the<00:28:31.309> constructor 00:28:31.780 --> 00:28:31.790 align:start position:0% happened but what I mean the constructor 00:28:31.790 --> 00:28:34.120 align:start position:0% happened but what I mean the constructor of<00:28:31.820> what<00:28:32.120> if<00:28:32.390> you<00:28:32.570> have<00:28:32.660> an<00:28:32.780> address<00:28:32.929> as<00:28:33.500> some 00:28:34.120 --> 00:28:34.130 align:start position:0% of what if you have an address as some 00:28:34.130 --> 00:28:45.010 align:start position:0% of what if you have an address as some objects<00:28:41.230> within<00:28:42.880> like<00:28:43.880> a<00:28:43.910> function<00:28:44.660> and<00:28:44.960> the 00:28:45.010 --> 00:28:45.020 align:start position:0% objects within like a function and the 00:28:45.020 --> 00:28:46.720 align:start position:0% objects within like a function and the function<00:28:45.050> itself<00:28:45.650> does<00:28:45.800> not<00:28:45.830> have<00:28:46.010> payable<00:28:46.550> it 00:28:46.720 --> 00:28:46.730 align:start position:0% function itself does not have payable it 00:28:46.730 --> 00:28:48.130 align:start position:0% function itself does not have payable it won't<00:28:46.910> be<00:28:47.030> registered 00:28:48.130 --> 00:28:48.140 align:start position:0% won't be registered 00:28:48.140 --> 00:28:50.660 align:start position:0% won't be registered like<00:28:49.140> you<00:28:49.320> won't<00:28:49.500> allow<00:28:49.920> that<00:28:50.130> to<00:28:50.550> actually 00:28:50.660 --> 00:28:50.670 align:start position:0% like you won't allow that to actually 00:28:50.670 --> 00:28:54.110 align:start position:0% like you won't allow that to actually happen<00:28:51.590> no<00:28:52.590> you<00:28:52.650> can<00:28:52.980> you<00:28:53.310> can<00:28:53.460> always<00:28:53.730> send 00:28:54.110 --> 00:28:54.120 align:start position:0% happen no you can you can always send 00:28:54.120 --> 00:28:56.300 align:start position:0% happen no you can you can always send funds<00:28:54.600> out<00:28:54.900> from<00:28:55.230> a<00:28:55.290> non<00:28:55.440> payable<00:28:55.890> function 00:28:56.300 --> 00:28:56.310 align:start position:0% funds out from a non payable function 00:28:56.310 --> 00:28:58.250 align:start position:0% funds out from a non payable function we're<00:28:56.970> talking<00:28:57.300> here<00:28:57.450> about<00:28:57.510> whether<00:28:57.900> you<00:28:58.080> can 00:28:58.250 --> 00:28:58.260 align:start position:0% we're talking here about whether you can 00:28:58.260 --> 00:29:00.290 align:start position:0% we're talking here about whether you can simply<00:28:58.980> calling<00:28:59.220> the<00:28:59.430> transfer<00:28:59.790> method<00:29:00.060> on<00:29:00.180> an 00:29:00.290 --> 00:29:00.300 align:start position:0% simply calling the transfer method on an 00:29:00.300 --> 00:29:02.660 align:start position:0% simply calling the transfer method on an address<00:29:00.690> and<00:29:01.070> apparently<00:29:02.070> in<00:29:02.220> future<00:29:02.550> there 00:29:02.660 --> 00:29:02.670 align:start position:0% address and apparently in future there 00:29:02.670 --> 00:29:04.820 align:start position:0% address and apparently in future there will<00:29:02.760> be<00:29:02.790> an<00:29:02.970> address<00:29:03.150> subtype<00:29:03.750> and<00:29:04.080> only<00:29:04.650> that 00:29:04.820 --> 00:29:04.830 align:start position:0% will be an address subtype and only that 00:29:04.830 --> 00:29:14.530 align:start position:0% will be an address subtype and only that will<00:29:05.040> have<00:29:05.250> the<00:29:05.910> transfer<00:29:06.330> function<00:29:06.780> too 00:29:14.530 --> 00:29:14.540 align:start position:0% 00:29:14.540 --> 00:29:21.710 align:start position:0% right<00:29:19.010> right<00:29:20.010> so<00:29:20.250> this<00:29:20.730> is<00:29:20.790> know<00:29:21.450> with<00:29:21.600> the 00:29:21.710 --> 00:29:21.720 align:start position:0% right right so this is know with the 00:29:21.720 --> 00:29:23.630 align:start position:0% right right so this is know with the right<00:29:21.930> terminology<00:29:22.350> maybe<00:29:22.950> it's<00:29:23.160> a<00:29:23.220> key<00:29:23.460> word 00:29:23.630 --> 00:29:23.640 align:start position:0% right terminology maybe it's a key word 00:29:23.640 --> 00:29:28.040 align:start position:0% right terminology maybe it's a key word but<00:29:24.210> it's<00:29:24.390> like<00:29:24.690> oddly<00:29:25.580> so<00:29:26.580> in<00:29:26.820> this<00:29:27.150> case<00:29:27.450> it's 00:29:28.040 --> 00:29:28.050 align:start position:0% but it's like oddly so in this case it's 00:29:28.050 --> 00:29:31.010 align:start position:0% but it's like oddly so in this case it's the<00:29:28.320> key<00:29:28.500> it's<00:29:28.710> a<00:29:28.800> synthetic<00:29:29.550> thing<00:29:30.360> which<00:29:30.720> has 00:29:31.010 --> 00:29:31.020 align:start position:0% the key it's a synthetic thing which has 00:29:31.020 --> 00:29:33.260 align:start position:0% the key it's a synthetic thing which has been<00:29:31.260> added<00:29:31.530> the<00:29:31.920> syntactic<00:29:32.550> sugar<00:29:32.580> on<00:29:33.150> the 00:29:33.260 --> 00:29:33.270 align:start position:0% been added the syntactic sugar on the 00:29:33.270 --> 00:29:36.170 align:start position:0% been added the syntactic sugar on the address<00:29:33.630> type<00:29:33.810> and<00:29:34.050> this<00:29:34.650> type<00:29:35.370> it's<00:29:35.610> a<00:29:35.700> method 00:29:36.170 --> 00:29:36.180 align:start position:0% address type and this type it's a method 00:29:36.180 --> 00:29:38.510 align:start position:0% address type and this type it's a method with<00:29:37.050> an<00:29:37.200> actual<00:29:37.530> concrete<00:29:37.770> method<00:29:38.310> called 00:29:38.510 --> 00:29:38.520 align:start position:0% with an actual concrete method called 00:29:38.520 --> 00:29:44.330 align:start position:0% with an actual concrete method called transfer<00:29:38.970> on<00:29:39.240> an<00:29:40.050> external<00:29:40.920> account<00:29:41.730> and<00:29:43.340> for 00:29:44.330 --> 00:29:44.340 align:start position:0% transfer on an external account and for 00:29:44.340 --> 00:29:45.980 align:start position:0% transfer on an external account and for security<00:29:44.520> there<00:29:45.300> are<00:29:45.390> very<00:29:45.690> different 00:29:45.980 --> 00:29:45.990 align:start position:0% security there are very different 00:29:45.990 --> 00:29:52.970 align:start position:0% security there are very different semantics<00:29:46.950> and<00:29:47.130> they<00:29:47.490> matter<00:29:47.700> a<00:29:47.850> lot<00:29:48.120> yeah<00:29:51.980> so 00:29:52.970 --> 00:29:52.980 align:start position:0% semantics and they matter a lot yeah so 00:29:52.980 --> 00:29:54.590 align:start position:0% semantics and they matter a lot yeah so I've<00:29:53.070> had<00:29:53.550> a<00:29:53.580> couple<00:29:53.730> of<00:29:53.910> people<00:29:54.210> sent<00:29:54.510> me 00:29:54.590 --> 00:29:54.600 align:start position:0% I've had a couple of people sent me 00:29:54.600 --> 00:29:57.110 align:start position:0% I've had a couple of people sent me things<00:29:55.560> and<00:29:55.770> tweet<00:29:56.040> diems<00:29:56.370> I<00:29:56.670> only<00:29:56.820> have<00:29:57.000> my 00:29:57.110 --> 00:29:57.120 align:start position:0% things and tweet diems I only have my 00:29:57.120 --> 00:29:59.030 align:start position:0% things and tweet diems I only have my phone<00:29:57.360> here<00:29:57.600> so<00:29:57.690> please<00:29:58.140> send<00:29:58.350> them<00:29:58.500> to<00:29:58.650> other 00:29:59.030 --> 00:29:59.040 align:start position:0% phone here so please send them to other 00:29:59.040 --> 00:30:01.760 align:start position:0% phone here so please send them to other people<00:29:59.400> as<00:29:59.490> well<00:29:59.700> yeah<00:30:00.480> while<00:30:00.930> I<00:30:00.960> well<00:30:01.500> I<00:30:01.530> set 00:30:01.760 --> 00:30:01.770 align:start position:0% people as well yeah while I well I set 00:30:01.770 --> 00:30:03.230 align:start position:0% people as well yeah while I well I set this<00:30:01.890> up<00:30:02.040> you<00:30:02.310> just<00:30:02.520> describe<00:30:02.940> what<00:30:02.970> the 00:30:03.230 --> 00:30:03.240 align:start position:0% this up you just describe what the 00:30:03.240 --> 00:30:04.910 align:start position:0% this up you just describe what the contract<00:30:03.600> does<00:30:03.720> if<00:30:03.900> you<00:30:04.080> could<00:30:04.260> yeah<00:30:04.650> so 00:30:04.910 --> 00:30:04.920 align:start position:0% contract does if you could yeah so 00:30:04.920 --> 00:30:06.980 align:start position:0% contract does if you could yeah so everybody<00:30:05.460> my<00:30:05.610> name<00:30:05.730> is<00:30:05.820> Brennan<00:30:06.090> we've 00:30:06.980 --> 00:30:06.990 align:start position:0% everybody my name is Brennan we've 00:30:06.990 --> 00:30:13.160 align:start position:0% everybody my name is Brennan we've created<00:30:07.320> a<00:30:07.650> work<00:30:11.510> we've<00:30:12.510> created<00:30:12.750> a<00:30:12.960> work 00:30:13.160 --> 00:30:13.170 align:start position:0% created a work we've created a work 00:30:13.170 --> 00:30:15.620 align:start position:0% created a work we've created a work contract<00:30:13.620> so<00:30:14.130> that<00:30:14.280> you<00:30:14.430> can<00:30:14.640> deposit<00:30:15.060> tokens 00:30:15.620 --> 00:30:15.630 align:start position:0% contract so that you can deposit tokens 00:30:15.630 --> 00:30:18.020 align:start position:0% contract so that you can deposit tokens in<00:30:15.810> it<00:30:15.930> and<00:30:16.140> then<00:30:16.590> be<00:30:17.160> eligible<00:30:17.430> to<00:30:17.940> be 00:30:18.020 --> 00:30:18.030 align:start position:0% in it and then be eligible to be 00:30:18.030 --> 00:30:20.840 align:start position:0% in it and then be eligible to be selected<00:30:18.480> to<00:30:18.720> complete<00:30:19.320> work<00:30:19.500> so<00:30:20.250> you<00:30:20.640> say 00:30:20.840 --> 00:30:20.850 align:start position:0% selected to complete work so you say 00:30:20.850 --> 00:30:22.820 align:start position:0% selected to complete work so you say deposit<00:30:21.270> a<00:30:21.330> thousand<00:30:21.720> tokens<00:30:22.140> and<00:30:22.530> then<00:30:22.650> now 00:30:22.820 --> 00:30:22.830 align:start position:0% deposit a thousand tokens and then now 00:30:22.830 --> 00:30:26.230 align:start position:0% deposit a thousand tokens and then now you<00:30:22.890> can<00:30:23.430> start<00:30:24.420> working<00:30:24.660> in<00:30:25.020> some<00:30:25.230> capacity 00:30:26.230 --> 00:30:26.240 align:start position:0% you can start working in some capacity 00:30:26.240 --> 00:30:29.450 align:start position:0% you can start working in some capacity so<00:30:27.350> it's<00:30:28.350> still<00:30:28.590> a<00:30:28.620> work<00:30:28.680> in<00:30:28.890> progress<00:30:29.130> so<00:30:29.430> I 00:30:29.450 --> 00:30:29.460 align:start position:0% so it's still a work in progress so I 00:30:29.460 --> 00:30:31.790 align:start position:0% so it's still a work in progress so I think<00:30:29.520> it's<00:30:29.700> gonna<00:30:29.790> get<00:30:29.940> shredded<00:30:30.590> but<00:30:31.590> the 00:30:31.790 --> 00:30:31.800 align:start position:0% think it's gonna get shredded but the 00:30:31.800 --> 00:30:33.560 align:start position:0% think it's gonna get shredded but the idea<00:30:32.070> is<00:30:32.160> that<00:30:32.190> you<00:30:32.670> you<00:30:32.940> to<00:30:33.090> positive<00:30:33.480> so 00:30:33.560 --> 00:30:33.570 align:start position:0% idea is that you you to positive so 00:30:33.570 --> 00:30:35.540 align:start position:0% idea is that you you to positive so amount<00:30:33.780> of<00:30:33.870> tokens<00:30:34.260> and<00:30:34.470> then<00:30:34.890> the<00:30:35.160> work 00:30:35.540 --> 00:30:35.550 align:start position:0% amount of tokens and then the work 00:30:35.550 --> 00:30:38.960 align:start position:0% amount of tokens and then the work manager<00:30:36.120> is<00:30:36.300> able<00:30:36.840> to<00:30:36.960> withdraw<00:30:37.880> from<00:30:38.880> that 00:30:38.960 --> 00:30:38.970 align:start position:0% manager is able to withdraw from that 00:30:38.970 --> 00:30:42.520 align:start position:0% manager is able to withdraw from that deposit<00:30:39.690> for<00:30:39.870> jobs<00:30:40.110> and<00:30:40.440> as<00:30:41.160> soon<00:30:41.340> as<00:30:41.460> that 00:30:42.520 --> 00:30:42.530 align:start position:0% deposit for jobs and as soon as that 00:30:42.530 --> 00:30:46.870 align:start position:0% deposit for jobs and as soon as that deposit<00:30:43.530> drops<00:30:43.830> below<00:30:44.100> the<00:30:45.050> size<00:30:46.050> of<00:30:46.410> the<00:30:46.530> jobs 00:30:46.870 --> 00:30:46.880 align:start position:0% deposit drops below the size of the jobs 00:30:46.880 --> 00:30:49.580 align:start position:0% deposit drops below the size of the jobs requirement<00:30:47.880> like<00:30:48.060> the<00:30:48.210> stake<00:30:48.480> then<00:30:49.110> you'll 00:30:49.580 --> 00:30:49.590 align:start position:0% requirement like the stake then you'll 00:30:49.590 --> 00:30:52.790 align:start position:0% requirement like the stake then you'll become<00:30:49.770> suspended<00:30:50.370> and<00:30:50.700> so<00:30:51.540> you<00:30:52.500> have<00:30:52.620> that 00:30:52.790 --> 00:30:52.800 align:start position:0% become suspended and so you have that 00:30:52.800 --> 00:30:54.230 align:start position:0% become suspended and so you have that forces<00:30:53.130> you<00:30:53.250> deposit<00:30:53.700> back<00:30:53.880> into<00:30:54.150> the 00:30:54.230 --> 00:30:54.240 align:start position:0% forces you deposit back into the 00:30:54.240 --> 00:30:56.720 align:start position:0% forces you deposit back into the contract<00:30:54.750> to<00:30:55.320> refill<00:30:55.710> your<00:30:55.890> your<00:30:56.190> work<00:30:56.340> tokens 00:30:56.720 --> 00:30:56.730 align:start position:0% contract to refill your your work tokens 00:30:56.730 --> 00:30:58.550 align:start position:0% contract to refill your your work tokens so<00:30:57.120> if<00:30:57.240> you<00:30:57.330> can<00:30:57.480> imagine<00:30:57.630> it's<00:30:58.080> like<00:30:58.260> the<00:30:58.410> work 00:30:58.550 --> 00:30:58.560 align:start position:0% so if you can imagine it's like the work 00:30:58.560 --> 00:31:00.860 align:start position:0% so if you can imagine it's like the work deposit<00:30:59.070> is<00:30:59.190> sort<00:30:59.700> of<00:30:59.760> that<00:31:00.150> is<00:31:00.360> the<00:31:00.540> number<00:31:00.750> of 00:31:00.860 --> 00:31:00.870 align:start position:0% deposit is sort of that is the number of 00:31:00.870 --> 00:31:01.640 align:start position:0% deposit is sort of that is the number of jobs<00:31:01.110> you<00:31:01.260> can<00:31:01.380> have 00:31:01.640 --> 00:31:01.650 align:start position:0% jobs you can have 00:31:01.650 --> 00:31:05.870 align:start position:0% jobs you can have on<00:31:01.740> the<00:31:01.890> fly<00:31:02.160> if<00:31:02.610> you<00:31:02.790> will<00:31:03.830> so<00:31:04.830> so<00:31:05.610> there's<00:31:05.790> a 00:31:05.870 --> 00:31:05.880 align:start position:0% on the fly if you will so so there's a 00:31:05.880 --> 00:31:07.460 align:start position:0% on the fly if you will so so there's a few<00:31:06.030> things<00:31:06.090> that<00:31:06.600> we<00:31:06.690> haven't<00:31:06.900> implemented 00:31:07.460 --> 00:31:07.470 align:start position:0% few things that we haven't implemented 00:31:07.470 --> 00:31:10.220 align:start position:0% few things that we haven't implemented like<00:31:07.800> being<00:31:08.340> able<00:31:08.430> to<00:31:08.520> withdraw<00:31:08.880> but<00:31:09.090> or<00:31:10.020> sorry 00:31:10.220 --> 00:31:10.230 align:start position:0% like being able to withdraw but or sorry 00:31:10.230 --> 00:31:11.630 align:start position:0% like being able to withdraw but or sorry I<00:31:10.260> have<00:31:10.380> a<00:31:10.410> having<00:31:10.800> a<00:31:10.890> restriction<00:31:11.460> on<00:31:11.580> the 00:31:11.630 --> 00:31:11.640 align:start position:0% I have a having a restriction on the 00:31:11.640 --> 00:31:13.220 align:start position:0% I have a having a restriction on the timer<00:31:11.910> but<00:31:12.300> I'm<00:31:12.720> not<00:31:12.900> sure<00:31:13.050> if<00:31:13.110> it's 00:31:13.220 --> 00:31:13.230 align:start position:0% timer but I'm not sure if it's 00:31:13.230 --> 00:31:14.840 align:start position:0% timer but I'm not sure if it's absolutely<00:31:13.350> necessary<00:31:13.590> so<00:31:14.160> I<00:31:14.460> guess<00:31:14.730> I'll 00:31:14.840 --> 00:31:14.850 align:start position:0% absolutely necessary so I guess I'll 00:31:14.850 --> 00:31:16.850 align:start position:0% absolutely necessary so I guess I'll hand<00:31:15.030> it<00:31:15.120> off<00:31:15.210> to<00:31:15.240> you<00:31:15.390> guys<00:31:15.540> to<00:31:15.840> have<00:31:16.590> a<00:31:16.650> look 00:31:16.850 --> 00:31:16.860 align:start position:0% hand it off to you guys to have a look 00:31:16.860 --> 00:31:20.540 align:start position:0% hand it off to you guys to have a look so<00:31:18.080> so<00:31:19.080> that<00:31:19.260> is<00:31:19.410> there<00:31:19.650> is<00:31:19.800> there<00:31:19.950> Nate<00:31:20.280> in 00:31:20.540 --> 00:31:20.550 align:start position:0% so so that is there is there Nate in 00:31:20.550 --> 00:31:23.210 align:start position:0% so so that is there is there Nate in Utah<00:31:20.880> margin<00:31:21.180> or<00:31:21.330> are<00:31:21.570> there<00:31:21.810> like<00:31:21.990> it's<00:31:22.890> I've 00:31:23.210 --> 00:31:23.220 align:start position:0% Utah margin or are there like it's I've 00:31:23.220 --> 00:31:25.370 align:start position:0% Utah margin or are there like it's I've actually<00:31:23.430> left<00:31:23.760> that<00:31:24.000> out<00:31:24.180> it's<00:31:24.390> just<00:31:24.480> er<00:31:24.810> c20 00:31:25.370 --> 00:31:25.380 align:start position:0% actually left that out it's just er c20 00:31:25.380 --> 00:31:28.940 align:start position:0% actually left that out it's just er c20 so<00:31:26.280> you<00:31:26.340> can<00:31:26.520> just<00:31:26.700> you<00:31:27.030> know<00:31:27.060> in<00:31:27.810> say<00:31:27.960> okay<00:31:28.860> so 00:31:28.940 --> 00:31:28.950 align:start position:0% so you can just you know in say okay so 00:31:28.950 --> 00:31:31.960 align:start position:0% so you can just you know in say okay so will<00:31:29.280> will<00:31:29.610> this<00:31:29.670> thing<00:31:29.970> be<00:31:30.810> dealing<00:31:31.320> with 00:31:31.960 --> 00:31:31.970 align:start position:0% will will this thing be dealing with 00:31:31.970 --> 00:31:35.350 align:start position:0% will will this thing be dealing with assets<00:31:32.970> of<00:31:33.090> value<00:31:33.120> such<00:31:33.630> as<00:31:33.810> ether<00:31:34.320> or 00:31:35.350 --> 00:31:35.360 align:start position:0% assets of value such as ether or 00:31:35.360 --> 00:31:38.180 align:start position:0% assets of value such as ether or whatever<00:31:36.360> valuable<00:31:36.960> token<00:31:37.350> just<00:31:37.710> a<00:31:37.800> custom 00:31:38.180 --> 00:31:38.190 align:start position:0% whatever valuable token just a custom 00:31:38.190 --> 00:31:39.800 align:start position:0% whatever valuable token just a custom work<00:31:38.340> token<00:31:38.760> that's<00:31:38.970> the<00:31:39.120> custom<00:31:39.270> work<00:31:39.480> token 00:31:39.800 --> 00:31:39.810 align:start position:0% work token that's the custom work token 00:31:39.810 --> 00:31:42.680 align:start position:0% work token that's the custom work token yeah<00:31:40.080> so<00:31:40.500> at<00:31:40.830> this<00:31:41.190> point<00:31:41.520> is<00:31:41.880> there<00:31:42.360> anything 00:31:42.680 --> 00:31:42.690 align:start position:0% yeah so at this point is there anything 00:31:42.690 --> 00:31:44.810 align:start position:0% yeah so at this point is there anything you<00:31:43.680> know<00:31:43.800> what<00:31:43.950> what<00:31:44.160> are<00:31:44.190> the<00:31:44.280> asks<00:31:44.640> are 00:31:44.810 --> 00:31:44.820 align:start position:0% you know what what are the asks are 00:31:44.820 --> 00:31:49.220 align:start position:0% you know what what are the asks are there<00:31:44.850> any<00:31:45.000> assets<00:31:45.570> that<00:31:46.020> are<00:31:46.230> have<00:31:46.670> value 00:31:49.220 --> 00:31:49.230 align:start position:0% there any assets that are have value 00:31:49.230 --> 00:31:52.370 align:start position:0% there any assets that are have value no<00:31:49.980> just<00:31:50.310> the<00:31:50.430> inherent<00:31:51.030> value<00:31:51.420> of<00:31:51.450> being<00:31:52.050> part 00:31:52.370 --> 00:31:52.380 align:start position:0% no just the inherent value of being part 00:31:52.380 --> 00:31:53.600 align:start position:0% no just the inherent value of being part of<00:31:52.500> the<00:31:52.620> work<00:31:52.740> contract<00:31:53.310> so<00:31:53.430> you<00:31:53.460> can 00:31:53.600 --> 00:31:53.610 align:start position:0% of the work contract so you can 00:31:53.610 --> 00:31:56.300 align:start position:0% of the work contract so you can participate<00:31:53.760> in<00:31:54.270> the<00:31:54.480> jobs<00:31:54.750> so<00:31:55.680> that<00:31:56.070> the 00:31:56.300 --> 00:31:56.310 align:start position:0% participate in the jobs so that the 00:31:56.310 --> 00:31:57.860 align:start position:0% participate in the jobs so that the value<00:31:56.610> exchange<00:31:57.000> is<00:31:57.150> outside<00:31:57.510> of<00:31:57.540> that<00:31:57.750> you 00:31:57.860 --> 00:31:57.870 align:start position:0% value exchange is outside of that you 00:31:57.870 --> 00:31:59.810 align:start position:0% value exchange is outside of that you become<00:31:58.110> eligible<00:31:58.350> to<00:31:59.220> take<00:31:59.370> part<00:31:59.430> in<00:31:59.670> that 00:31:59.810 --> 00:31:59.820 align:start position:0% become eligible to take part in that 00:31:59.820 --> 00:32:01.880 align:start position:0% become eligible to take part in that value<00:32:00.000> network<00:32:00.390> by<00:32:00.540> staking<00:32:00.930> tokens<00:32:01.770> in<00:32:01.860> the 00:32:01.880 --> 00:32:01.890 align:start position:0% value network by staking tokens in the 00:32:01.890 --> 00:32:05.690 align:start position:0% value network by staking tokens in the work<00:32:02.040> contract<00:32:02.720> so<00:32:03.720> alright<00:32:04.170> yeah<00:32:04.590> and<00:32:05.340> who 00:32:05.690 --> 00:32:05.700 align:start position:0% work contract so alright yeah and who 00:32:05.700 --> 00:32:08.870 align:start position:0% work contract so alright yeah and who are<00:32:05.820> the<00:32:06.000> difference<00:32:06.560> actors<00:32:07.560> in<00:32:08.040> this<00:32:08.400> model 00:32:08.870 --> 00:32:08.880 align:start position:0% are the difference actors in this model 00:32:08.880 --> 00:32:11.960 align:start position:0% are the difference actors in this model so<00:32:09.060> you<00:32:09.120> have<00:32:09.360> someone<00:32:10.080> who<00:32:10.230> does<00:32:10.410> work<00:32:10.620> yes<00:32:11.400> so 00:32:11.960 --> 00:32:11.970 align:start position:0% so you have someone who does work yes so 00:32:11.970 --> 00:32:13.700 align:start position:0% so you have someone who does work yes so you've<00:32:12.060> got<00:32:12.180> the<00:32:12.330> worker<00:32:12.540> who<00:32:13.050> stakes<00:32:13.560> the 00:32:13.700 --> 00:32:13.710 align:start position:0% you've got the worker who stakes the 00:32:13.710 --> 00:32:16.970 align:start position:0% you've got the worker who stakes the initial<00:32:13.980> deposit<00:32:14.190> you<00:32:15.150> have<00:32:15.360> the<00:32:15.600> job<00:32:16.440> manager 00:32:16.970 --> 00:32:16.980 align:start position:0% initial deposit you have the job manager 00:32:16.980 --> 00:32:19.390 align:start position:0% initial deposit you have the job manager who's<00:32:17.400> responsible<00:32:18.210> for<00:32:18.480> pulling<00:32:18.810> out<00:32:19.050> the 00:32:19.390 --> 00:32:19.400 align:start position:0% who's responsible for pulling out the 00:32:19.400 --> 00:32:22.250 align:start position:0% who's responsible for pulling out the the<00:32:20.400> job<00:32:21.060> deposit<00:32:21.630> if<00:32:21.750> you<00:32:21.900> will<00:32:22.050> which<00:32:22.230> is 00:32:22.250 --> 00:32:22.260 align:start position:0% the job deposit if you will which is 00:32:22.260 --> 00:32:23.390 align:start position:0% the job deposit if you will which is gonna<00:32:22.470> be<00:32:22.560> smaller<00:32:22.830> than<00:32:23.130> the<00:32:23.250> initial 00:32:23.390 --> 00:32:23.400 align:start position:0% gonna be smaller than the initial 00:32:23.400 --> 00:32:25.220 align:start position:0% gonna be smaller than the initial deposit<00:32:23.760> and<00:32:24.210> then<00:32:24.690> of<00:32:24.780> course<00:32:24.810> you<00:32:25.050> have<00:32:25.170> the 00:32:25.220 --> 00:32:25.230 align:start position:0% deposit and then of course you have the 00:32:25.230 --> 00:32:28.310 align:start position:0% deposit and then of course you have the owner<00:32:25.380> of<00:32:25.560> the<00:32:25.650> contract<00:32:26.160> you<00:32:26.550> can<00:32:26.700> deploy<00:32:27.320> and 00:32:28.310 --> 00:32:28.320 align:start position:0% owner of the contract you can deploy and 00:32:28.320 --> 00:32:32.480 align:start position:0% owner of the contract you can deploy and the<00:32:28.950> owner<00:32:29.190> of<00:32:29.550> the<00:32:29.640> contract<00:32:30.180> is<00:32:30.360> this<00:32:31.160> any<00:32:32.160> do 00:32:32.480 --> 00:32:32.490 align:start position:0% the owner of the contract is this any do 00:32:32.490 --> 00:32:35.360 align:start position:0% the owner of the contract is this any do administers<00:32:33.620> administrative<00:32:34.620> stuff<00:32:35.040> on<00:32:35.280> the 00:32:35.360 --> 00:32:35.370 align:start position:0% administers administrative stuff on the 00:32:35.370 --> 00:32:40.250 align:start position:0% administers administrative stuff on the contract<00:32:35.700> mm-hmm<00:32:36.500> like<00:32:37.500> what<00:32:38.630> if<00:32:39.630> I<00:32:39.780> recall 00:32:40.250 --> 00:32:40.260 align:start position:0% contract mm-hmm like what if I recall 00:32:40.260 --> 00:32:41.930 align:start position:0% contract mm-hmm like what if I recall there's<00:32:40.680> a<00:32:40.770> couple<00:32:40.950> weeks<00:32:41.190> ago<00:32:41.310> I<00:32:41.640> believe 00:32:41.930 --> 00:32:41.940 align:start position:0% there's a couple weeks ago I believe 00:32:41.940 --> 00:32:44.930 align:start position:0% there's a couple weeks ago I believe it's<00:32:42.660> just<00:32:43.220> instantiating<00:32:44.220> it<00:32:44.460> and<00:32:44.700> then 00:32:44.930 --> 00:32:44.940 align:start position:0% it's just instantiating it and then 00:32:44.940 --> 00:32:47.120 align:start position:0% it's just instantiating it and then there<00:32:45.360> might<00:32:45.540> be<00:32:45.570> they<00:32:46.470> can<00:32:46.620> set<00:32:46.800> the<00:32:46.920> stake 00:32:47.120 --> 00:32:47.130 align:start position:0% there might be they can set the stake 00:32:47.130 --> 00:32:49.400 align:start position:0% there might be they can set the stake limit<00:32:47.460> for<00:32:47.640> example<00:32:48.030> right<00:32:48.840> right<00:32:49.110> yeah 00:32:49.400 --> 00:32:49.410 align:start position:0% limit for example right right yeah 00:32:49.410 --> 00:32:51.890 align:start position:0% limit for example right right yeah there's<00:32:49.710> a<00:32:49.770> few<00:32:49.980> public<00:32:50.370> variables<00:32:50.760> that<00:32:51.720> you 00:32:51.890 --> 00:32:51.900 align:start position:0% there's a few public variables that you 00:32:51.900 --> 00:32:53.900 align:start position:0% there's a few public variables that you can<00:32:51.930> that<00:32:52.410> you<00:32:52.440> can<00:32:52.530> adjust<00:32:52.650> so<00:32:53.640> hopefully 00:32:53.900 --> 00:32:53.910 align:start position:0% can that you can adjust so hopefully 00:32:53.910 --> 00:32:56.650 align:start position:0% can that you can adjust so hopefully it's<00:32:54.030> small<00:32:54.270> enough<00:32:54.300> for<00:32:54.480> you<00:32:54.600> guys<00:32:54.750> to<00:32:54.900> croc 00:32:56.650 --> 00:32:56.660 align:start position:0% it's small enough for you guys to croc 00:32:56.660 --> 00:33:01.510 align:start position:0% it's small enough for you guys to croc okay 00:33:01.510 --> 00:33:01.520 align:start position:0% 00:33:01.520 --> 00:33:06.380 align:start position:0% so<00:33:02.520> let's<00:33:03.090> see<00:33:03.360> um<00:33:03.770> where<00:33:04.770> would<00:33:04.920> a<00:33:04.950> user<00:33:05.390> what 00:33:06.380 --> 00:33:06.390 align:start position:0% so let's see um where would a user what 00:33:06.390 --> 00:33:08.120 align:start position:0% so let's see um where would a user what would<00:33:06.510> be<00:33:06.660> the<00:33:06.810> first<00:33:07.080> action<00:33:07.380> our<00:33:07.650> user<00:33:07.800> does 00:33:08.120 --> 00:33:08.130 align:start position:0% would be the first action our user does 00:33:08.130 --> 00:33:11.890 align:start position:0% would be the first action our user does let's<00:33:08.730> deposit<00:33:09.720> stake<00:33:09.990> okay<00:33:10.590> so<00:33:10.650> let's<00:33:10.920> go 00:33:11.890 --> 00:33:11.900 align:start position:0% let's deposit stake okay so let's go 00:33:11.900 --> 00:33:14.600 align:start position:0% let's deposit stake okay so let's go it's<00:33:12.900> quite<00:33:13.110> hard<00:33:13.290> for<00:33:13.320> a<00:33:13.410> lot<00:33:13.500> I<00:33:13.560> have<00:33:13.710> to<00:33:13.890> look 00:33:14.600 --> 00:33:14.610 align:start position:0% it's quite hard for a lot I have to look 00:33:14.610 --> 00:33:15.930 align:start position:0% it's quite hard for a lot I have to look at<00:33:14.760> through<00:33:14.880> different<00:33:15.150> things 00:33:15.930 --> 00:33:15.940 align:start position:0% at through different things 00:33:15.940 --> 00:33:18.030 align:start position:0% at through different things so<00:33:16.510> the<00:33:16.630> owner<00:33:16.840> is<00:33:16.930> just<00:33:17.080> like<00:33:17.170> an<00:33:17.320> admin<00:33:17.830> that 00:33:18.030 --> 00:33:18.040 align:start position:0% so the owner is just like an admin that 00:33:18.040 --> 00:33:20.730 align:start position:0% so the owner is just like an admin that manages<00:33:18.460> this<00:33:19.530> okay 00:33:20.730 --> 00:33:20.740 align:start position:0% manages this okay 00:33:20.740 --> 00:33:29.670 align:start position:0% manages this okay so<00:33:27.570> okay<00:33:28.570> so<00:33:28.600> the<00:33:28.750> owner<00:33:29.020> deposits<00:33:29.500> their 00:33:29.670 --> 00:33:29.680 align:start position:0% so okay so the owner deposits their 00:33:29.680 --> 00:33:34.890 align:start position:0% so okay so the owner deposits their stake<00:33:30.480> and<00:33:32.130> it<00:33:33.130> seems<00:33:33.520> like<00:33:33.700> they<00:33:33.850> get<00:33:34.030> tokens 00:33:34.890 --> 00:33:34.900 align:start position:0% stake and it seems like they get tokens 00:33:34.900 --> 00:33:36.300 align:start position:0% stake and it seems like they get tokens just<00:33:35.860> bought<00:33:36.010> it 00:33:36.300 --> 00:33:36.310 align:start position:0% just bought it 00:33:36.310 --> 00:33:38.250 align:start position:0% just bought it I<00:33:36.340> mean<00:33:36.580> sent<00:33:36.850> back<00:33:36.970> to<00:33:37.000> them<00:33:37.210> right<00:33:37.360> yeah<00:33:38.020> and 00:33:38.250 --> 00:33:38.260 align:start position:0% I mean sent back to them right yeah and 00:33:38.260 --> 00:33:41.610 align:start position:0% I mean sent back to them right yeah and just<00:33:38.380> to<00:33:38.440> add<00:33:38.530> add<00:33:38.980> to<00:33:39.250> this<00:33:39.370> so<00:33:40.240> the<00:33:40.620> the 00:33:41.610 --> 00:33:41.620 align:start position:0% just to add add to this so the the 00:33:41.620 --> 00:33:44.700 align:start position:0% just to add add to this so the the worker<00:33:41.830> has<00:33:42.160> to<00:33:42.190> approve<00:33:42.670> the<00:33:43.290> the<00:33:44.290> transfer 00:33:44.700 --> 00:33:44.710 align:start position:0% worker has to approve the the transfer 00:33:44.710 --> 00:33:49.590 align:start position:0% worker has to approve the the transfer before<00:33:44.890> this<00:33:45.310> deposit<00:33:45.700> stake<00:33:46.060> is<00:33:46.180> called<00:33:48.600> so 00:33:49.590 --> 00:33:49.600 align:start position:0% before this deposit stake is called so 00:33:49.600 --> 00:33:51.120 align:start position:0% before this deposit stake is called so one<00:33:49.750> thing<00:33:50.140> I<00:33:50.200> noticed<00:33:50.410> in<00:33:50.470> the<00:33:50.500> deposit<00:33:50.950> stake 00:33:51.120 --> 00:33:51.130 align:start position:0% one thing I noticed in the deposit stake 00:33:51.130 --> 00:33:52.770 align:start position:0% one thing I noticed in the deposit stake is<00:33:51.280> it<00:33:51.400> doesn't<00:33:51.550> seem<00:33:51.880> to<00:33:52.060> care<00:33:52.240> whether<00:33:52.510> it 00:33:52.770 --> 00:33:52.780 align:start position:0% is it doesn't seem to care whether it 00:33:52.780 --> 00:33:55.320 align:start position:0% is it doesn't seem to care whether it actually<00:33:52.960> succeeds<00:33:53.950> like<00:33:54.520> token<00:33:54.850> uh<00:33:54.940> transfer 00:33:55.320 --> 00:33:55.330 align:start position:0% actually succeeds like token uh transfer 00:33:55.330 --> 00:33:57.480 align:start position:0% actually succeeds like token uh transfer from<00:33:55.630> you<00:33:56.560> might<00:33:56.710> have<00:33:56.830> the<00:33:56.950> allowance<00:33:57.340> but 00:33:57.480 --> 00:33:57.490 align:start position:0% from you might have the allowance but 00:33:57.490 --> 00:33:58.470 align:start position:0% from you might have the allowance but you<00:33:57.550> can<00:33:57.670> yeah<00:33:57.760> there<00:33:58.180> could<00:33:58.210> be<00:33:58.300> other 00:33:58.470 --> 00:33:58.480 align:start position:0% you can yeah there could be other 00:33:58.480 --> 00:34:00.990 align:start position:0% you can yeah there could be other restrictions<00:33:59.260> like<00:33:59.620> can't<00:34:00.370> send<00:34:00.700> to<00:34:00.970> a 00:34:00.990 --> 00:34:01.000 align:start position:0% restrictions like can't send to a 00:34:01.000 --> 00:34:03.930 align:start position:0% restrictions like can't send to a contract<00:34:01.590> address<00:34:02.590> or<00:34:02.800> something<00:34:03.130> weird<00:34:03.520> like 00:34:03.930 --> 00:34:03.940 align:start position:0% contract address or something weird like 00:34:03.940 --> 00:34:06.120 align:start position:0% contract address or something weird like itself<00:34:04.330> or<00:34:04.540> you<00:34:05.110> might<00:34:05.350> just<00:34:05.620> not<00:34:05.770> have<00:34:05.950> enough 00:34:06.120 --> 00:34:06.130 align:start position:0% itself or you might just not have enough 00:34:06.130 --> 00:34:14.130 align:start position:0% itself or you might just not have enough tokens<00:34:07.350> great<00:34:10.169> this<00:34:11.169> ambiguity<00:34:11.800> right<00:34:13.140> where 00:34:14.130 --> 00:34:14.140 align:start position:0% tokens great this ambiguity right where 00:34:14.140 --> 00:34:17.610 align:start position:0% tokens great this ambiguity right where if<00:34:14.950> this<00:34:15.730> token<00:34:16.390> is<00:34:16.570> actually<00:34:17.320> an 00:34:17.610 --> 00:34:17.620 align:start position:0% if this token is actually an 00:34:17.620 --> 00:34:19.350 align:start position:0% if this token is actually an implementation<00:34:18.399> of<00:34:18.460> the<00:34:18.610> ERC<00:34:18.880> 20 00:34:19.350 --> 00:34:19.360 align:start position:0% implementation of the ERC 20 00:34:19.360 --> 00:34:22.260 align:start position:0% implementation of the ERC 20 specification<00:34:20.020> which<00:34:20.370> conforms<00:34:21.370> exactly<00:34:22.090> to 00:34:22.260 --> 00:34:22.270 align:start position:0% specification which conforms exactly to 00:34:22.270 --> 00:34:24.630 align:start position:0% specification which conforms exactly to the<00:34:22.390> letter<00:34:22.600> of<00:34:22.780> specification<00:34:23.560> and<00:34:23.740> this 00:34:24.630 --> 00:34:24.640 align:start position:0% the letter of specification and this 00:34:24.640 --> 00:34:28.700 align:start position:0% the letter of specification and this transfer<00:34:25.120> from<00:34:25.300> fails<00:34:25.830> and<00:34:26.830> returns<00:34:27.250> a<00:34:27.399> false 00:34:28.700 --> 00:34:28.710 align:start position:0% transfer from fails and returns a false 00:34:28.710 --> 00:34:32.040 align:start position:0% transfer from fails and returns a false we<00:34:29.710> just<00:34:29.919> don't<00:34:30.220> care<00:34:30.370> about<00:34:30.490> that<00:34:30.820> yeah<00:34:31.149> so 00:34:32.040 --> 00:34:32.050 align:start position:0% we just don't care about that yeah so 00:34:32.050 --> 00:34:35.010 align:start position:0% we just don't care about that yeah so it's<00:34:32.290> a<00:34:32.380> it's<00:34:32.980> a<00:34:33.070> case<00:34:33.220> of<00:34:33.399> being<00:34:33.750> liberal<00:34:34.750> with 00:34:35.010 --> 00:34:35.020 align:start position:0% it's a it's a case of being liberal with 00:34:35.020 --> 00:34:37.260 align:start position:0% it's a it's a case of being liberal with what<00:34:35.169> you<00:34:35.260> accept<00:34:35.649> and<00:34:35.970> careful<00:34:36.970> thought<00:34:37.179> you 00:34:37.260 --> 00:34:37.270 align:start position:0% what you accept and careful thought you 00:34:37.270 --> 00:34:39.389 align:start position:0% what you accept and careful thought you omit<00:34:37.570> if<00:34:38.080> you<00:34:38.350> call<00:34:38.679> transfer<00:34:39.159> you<00:34:39.250> should 00:34:39.389 --> 00:34:39.399 align:start position:0% omit if you call transfer you should 00:34:39.399 --> 00:34:49.139 align:start position:0% omit if you call transfer you should always<00:34:39.520> write<00:34:39.880> that<00:34:39.909> in<00:34:40.149> a<00:34:40.210> require<00:34:46.919> yep<00:34:48.149> yeah 00:34:49.139 --> 00:34:49.149 align:start position:0% always write that in a require yep yeah 00:34:49.149 --> 00:34:50.639 align:start position:0% always write that in a require yep yeah the<00:34:49.330> the<00:34:49.360> check<00:34:49.840> for<00:34:50.020> the<00:34:50.110> allowance<00:34:50.290> isn't 00:34:50.639 --> 00:34:50.649 align:start position:0% the the check for the allowance isn't 00:34:50.649 --> 00:34:52.620 align:start position:0% the the check for the allowance isn't necessary<00:34:51.130> because<00:34:51.310> the<00:34:51.760> transfer<00:34:52.210> of<00:34:52.240> call 00:34:52.620 --> 00:34:52.630 align:start position:0% necessary because the transfer of call 00:34:52.630 --> 00:34:54.710 align:start position:0% necessary because the transfer of call will<00:34:52.840> fail<00:34:53.080> if<00:34:53.350> you<00:34:53.380> don't<00:34:53.500> have<00:34:53.800> an<00:34:53.890> allowance 00:34:54.710 --> 00:34:54.720 align:start position:0% will fail if you don't have an allowance 00:34:54.720 --> 00:34:57.030 align:start position:0% will fail if you don't have an allowance and<00:34:55.720> in<00:34:55.840> this<00:34:55.929> case<00:34:56.200> the<00:34:56.470> the<00:34:56.679> check<00:34:56.830> for<00:34:56.980> the 00:34:57.030 --> 00:34:57.040 align:start position:0% and in this case the the check for the 00:34:57.040 --> 00:34:58.290 align:start position:0% and in this case the the check for the allowance<00:34:57.370> is<00:34:57.430> actually<00:34:57.790> call<00:34:58.000> out<00:34:58.180> to 00:34:58.290 --> 00:34:58.300 align:start position:0% allowance is actually call out to 00:34:58.300 --> 00:34:59.760 align:start position:0% allowance is actually call out to another<00:34:58.420> contract<00:34:58.960> so<00:34:59.080> there's<00:34:59.260> a<00:34:59.290> minimum<00:34:59.620> of 00:34:59.760 --> 00:34:59.770 align:start position:0% another contract so there's a minimum of 00:34:59.770 --> 00:35:03.210 align:start position:0% another contract so there's a minimum of 700<00:35:00.220> gas<00:35:00.430> plus<00:35:01.390> trance<00:35:02.230> state<00:35:02.710> reading<00:35:03.010> fees 00:35:03.210 --> 00:35:03.220 align:start position:0% 700 gas plus trance state reading fees 00:35:03.220 --> 00:35:05.610 align:start position:0% 700 gas plus trance state reading fees all<00:35:03.820> right<00:35:04.000> yep<00:35:04.510> so<00:35:05.050> yeah 00:35:05.610 --> 00:35:05.620 align:start position:0% all right yep so yeah 00:35:05.620 --> 00:35:08.040 align:start position:0% all right yep so yeah always<00:35:06.010> wrap<00:35:06.310> your<00:35:06.760> important<00:35:07.750> stuff<00:35:07.900> in 00:35:08.040 --> 00:35:08.050 align:start position:0% always wrap your important stuff in 00:35:08.050 --> 00:35:11.130 align:start position:0% always wrap your important stuff in requires<00:35:08.380> which<00:35:09.160> again<00:35:10.090> is<00:35:10.630> the<00:35:10.690> sort<00:35:11.110> of 00:35:11.130 --> 00:35:11.140 align:start position:0% requires which again is the sort of 00:35:11.140 --> 00:35:12.060 align:start position:0% requires which again is the sort of thing<00:35:11.290> you're<00:35:11.410> talking<00:35:11.500> about<00:35:11.800> because 00:35:12.060 --> 00:35:12.070 align:start position:0% thing you're talking about because 00:35:12.070 --> 00:35:14.280 align:start position:0% thing you're talking about because transfer<00:35:12.550> and<00:35:12.730> solidity<00:35:13.150> is<00:35:13.450> explicitly 00:35:14.280 --> 00:35:14.290 align:start position:0% transfer and solidity is explicitly 00:35:14.290 --> 00:35:18.920 align:start position:0% transfer and solidity is explicitly doesn't<00:35:14.740> require<00:35:15.010> you<00:35:15.550> wrap<00:35:15.760> it<00:35:15.910> and<00:35:16.030> require 00:35:18.920 --> 00:35:18.930 align:start position:0% 00:35:18.930 --> 00:35:22.980 align:start position:0% also<00:35:20.520> one<00:35:21.520> thing<00:35:21.760> here<00:35:22.210> so<00:35:22.450> going<00:35:22.690> through<00:35:22.810> the 00:35:22.980 --> 00:35:22.990 align:start position:0% also one thing here so going through the 00:35:22.990 --> 00:35:26.910 align:start position:0% also one thing here so going through the scenes<00:35:23.470> since<00:35:23.800> that<00:35:24.070> deposit<00:35:24.970> stake<00:35:25.920> cause 00:35:26.910 --> 00:35:26.920 align:start position:0% scenes since that deposit stake cause 00:35:26.920 --> 00:35:29.490 align:start position:0% scenes since that deposit stake cause the<00:35:27.100> deposit<00:35:27.520> function 00:35:29.490 --> 00:35:29.500 align:start position:0% the deposit function 00:35:29.500 --> 00:35:30.480 align:start position:0% the deposit function if<00:35:29.590> you're<00:35:29.710> gonna<00:35:29.830> use<00:35:29.950> if<00:35:30.280> you're<00:35:30.400> gonna 00:35:30.480 --> 00:35:30.490 align:start position:0% if you're gonna use if you're gonna 00:35:30.490 --> 00:35:31.980 align:start position:0% if you're gonna use if you're gonna import<00:35:30.700> safe<00:35:31.000> math<00:35:31.210> and<00:35:31.420> use<00:35:31.510> it<00:35:31.660> in<00:35:31.780> some 00:35:31.980 --> 00:35:31.990 align:start position:0% import safe math and use it in some 00:35:31.990 --> 00:35:33.990 align:start position:0% import safe math and use it in some places<00:35:32.200> best<00:35:32.650> to<00:35:33.220> use<00:35:33.370> it<00:35:33.580> everywhere 00:35:33.990 --> 00:35:34.000 align:start position:0% places best to use it everywhere 00:35:34.000 --> 00:35:36.870 align:start position:0% places best to use it everywhere consistently<00:35:35.100> at<00:35:36.100> least<00:35:36.400> in<00:35:36.550> my<00:35:36.700> opinion 00:35:36.870 --> 00:35:36.880 align:start position:0% consistently at least in my opinion 00:35:36.880 --> 00:35:39.060 align:start position:0% consistently at least in my opinion because<00:35:37.330> otherwise<00:35:37.540> it's<00:35:37.840> if<00:35:38.380> you<00:35:38.710> get<00:35:38.860> used 00:35:39.060 --> 00:35:39.070 align:start position:0% because otherwise it's if you get used 00:35:39.070 --> 00:35:42.270 align:start position:0% because otherwise it's if you get used to<00:35:39.220> seeing<00:35:39.370> mixed<00:35:39.970> code<00:35:40.770> you<00:35:41.770> know<00:35:41.860> mix<00:35:42.070> it 00:35:42.270 --> 00:35:42.280 align:start position:0% to seeing mixed code you know mix it 00:35:42.280 --> 00:35:44.130 align:start position:0% to seeing mixed code you know mix it some<00:35:42.460> safe<00:35:42.850> math<00:35:43.030> and<00:35:43.240> sometimes<00:35:43.600> otherwise 00:35:44.130 --> 00:35:44.140 align:start position:0% some safe math and sometimes otherwise 00:35:44.140 --> 00:35:47.190 align:start position:0% some safe math and sometimes otherwise not<00:35:44.590> it'll<00:35:45.100> it's<00:35:45.370> also<00:35:45.580> to<00:35:45.760> become<00:35:46.510> become<00:35:46.990> too 00:35:47.190 --> 00:35:47.200 align:start position:0% not it'll it's also to become become too 00:35:47.200 --> 00:35:50.310 align:start position:0% not it'll it's also to become become too easy<00:35:47.410> for<00:35:47.500> you<00:35:47.740> to<00:35:48.220> look<00:35:48.850> at<00:35:49.060> a<00:35:49.240> line<00:35:50.050> that 00:35:50.310 --> 00:35:50.320 align:start position:0% easy for you to look at a line that 00:35:50.320 --> 00:35:52.080 align:start position:0% easy for you to look at a line that needs<00:35:50.440> safe<00:35:50.740> math<00:35:51.010> and<00:35:51.310> then<00:35:51.610> just<00:35:51.760> ignore<00:35:52.060> it 00:35:52.080 --> 00:35:52.090 align:start position:0% needs safe math and then just ignore it 00:35:52.090 --> 00:35:53.820 align:start position:0% needs safe math and then just ignore it because<00:35:52.510> you're<00:35:52.780> just<00:35:52.960> used<00:35:53.140> to<00:35:53.200> you<00:35:53.740> know 00:35:53.820 --> 00:35:53.830 align:start position:0% because you're just used to you know 00:35:53.830 --> 00:35:55.230 align:start position:0% because you're just used to you know like<00:35:54.040> the<00:35:54.160> cognitive<00:35:54.490> overload<00:35:54.790> of<00:35:55.120> like 00:35:55.230 --> 00:35:55.240 align:start position:0% like the cognitive overload of like 00:35:55.240 --> 00:35:57.360 align:start position:0% like the cognitive overload of like keeping<00:35:55.510> track<00:35:55.570> of<00:35:55.840> what<00:35:56.020> which<00:35:56.620> threshold<00:35:57.220> am 00:35:57.360 --> 00:35:57.370 align:start position:0% keeping track of what which threshold am 00:35:57.370 --> 00:35:58.890 align:start position:0% keeping track of what which threshold am I<00:35:57.460> using<00:35:57.610> safe<00:35:57.850> math<00:35:58.030> on<00:35:58.240> you<00:35:58.450> know<00:35:58.540> it's<00:35:58.660> you 00:35:58.890 --> 00:35:58.900 align:start position:0% I using safe math on you know it's you 00:35:58.900 --> 00:36:03.180 align:start position:0% I using safe math on you know it's you can<00:35:59.080> easily<00:35:59.350> get<00:35:59.620> mixed<00:35:59.890> mixed<00:36:00.280> up<00:36:01.950> as<00:36:02.950> a<00:36:03.040> more 00:36:03.180 --> 00:36:03.190 align:start position:0% can easily get mixed mixed up as a more 00:36:03.190 --> 00:36:04.350 align:start position:0% can easily get mixed mixed up as a more generic<00:36:03.310> thing<00:36:03.640> I<00:36:03.700> want<00:36:03.850> pointed<00:36:04.150> as<00:36:04.240> well 00:36:04.350 --> 00:36:04.360 align:start position:0% generic thing I want pointed as well 00:36:04.360 --> 00:36:06.570 align:start position:0% generic thing I want pointed as well like<00:36:04.540> a<00:36:04.570> lot<00:36:04.810> of<00:36:04.840> auditing<00:36:05.830> is<00:36:05.980> just<00:36:06.220> kind<00:36:06.550> of 00:36:06.570 --> 00:36:06.580 align:start position:0% like a lot of auditing is just kind of 00:36:06.580 --> 00:36:07.380 align:start position:0% like a lot of auditing is just kind of getting<00:36:06.730> your<00:36:06.820> head<00:36:06.970> wrapped<00:36:07.120> around<00:36:07.180> with 00:36:07.380 --> 00:36:07.390 align:start position:0% getting your head wrapped around with 00:36:07.390 --> 00:36:08.310 align:start position:0% getting your head wrapped around with the<00:36:07.450> contracts<00:36:07.750> trying<00:36:07.930> to<00:36:07.990> do<00:36:08.050> the<00:36:08.140> first 00:36:08.310 --> 00:36:08.320 align:start position:0% the contracts trying to do the first 00:36:08.320 --> 00:36:10.950 align:start position:0% the contracts trying to do the first place<00:36:08.790> yeah<00:36:09.790> going<00:36:10.090> back<00:36:10.330> to<00:36:10.450> the<00:36:10.540> description 00:36:10.950 --> 00:36:10.960 align:start position:0% place yeah going back to the description 00:36:10.960 --> 00:36:12.660 align:start position:0% place yeah going back to the description like<00:36:11.080> it's<00:36:11.260> a<00:36:11.320> yeah<00:36:11.980> that's<00:36:12.220> kind<00:36:12.460> of<00:36:12.520> why 00:36:12.660 --> 00:36:12.670 align:start position:0% like it's a yeah that's kind of why 00:36:12.670 --> 00:36:17.370 align:start position:0% like it's a yeah that's kind of why being<00:36:13.240> an<00:36:13.570> effective<00:36:14.320> auditor<00:36:16.050> ties<00:36:17.050> well 00:36:17.370 --> 00:36:17.380 align:start position:0% being an effective auditor ties well 00:36:17.380 --> 00:36:19.830 align:start position:0% being an effective auditor ties well together<00:36:17.640> not<00:36:18.640> being<00:36:18.880> afraid<00:36:19.180> to<00:36:19.300> ask<00:36:19.420> stupid 00:36:19.830 --> 00:36:19.840 align:start position:0% together not being afraid to ask stupid 00:36:19.840 --> 00:36:20.490 align:start position:0% together not being afraid to ask stupid questions 00:36:20.490 --> 00:36:20.500 align:start position:0% questions 00:36:20.500 --> 00:36:23.910 align:start position:0% questions exactly<00:36:21.300> yeah<00:36:22.300> yeah<00:36:22.540> oftentimes<00:36:23.200> like<00:36:23.590> the 00:36:23.910 --> 00:36:23.920 align:start position:0% exactly yeah yeah oftentimes like the 00:36:23.920 --> 00:36:26.340 align:start position:0% exactly yeah yeah oftentimes like the the<00:36:24.280> biggest<00:36:24.700> vulnerabilities<00:36:25.510> are<00:36:25.720> the<00:36:26.170> ones 00:36:26.340 --> 00:36:26.350 align:start position:0% the biggest vulnerabilities are the ones 00:36:26.350 --> 00:36:28.710 align:start position:0% the biggest vulnerabilities are the ones that<00:36:26.410> are<00:36:26.560> most<00:36:26.650> obvious<00:36:26.920> or<00:36:27.370> the<00:36:28.120> ones<00:36:28.330> where 00:36:28.710 --> 00:36:28.720 align:start position:0% that are most obvious or the ones where 00:36:28.720 --> 00:36:30.750 align:start position:0% that are most obvious or the ones where like<00:36:29.470> you<00:36:29.620> you<00:36:29.920> know<00:36:30.040> you're<00:36:30.190> reading<00:36:30.370> the 00:36:30.750 --> 00:36:30.760 align:start position:0% like you you know you're reading the 00:36:30.760 --> 00:36:33.540 align:start position:0% like you you know you're reading the code<00:36:30.940> and<00:36:31.240> it<00:36:31.540> kind<00:36:31.990> of<00:36:32.110> it's<00:36:32.950> structured<00:36:33.430> in<00:36:33.490> a 00:36:33.540 --> 00:36:33.550 align:start position:0% code and it kind of it's structured in a 00:36:33.550 --> 00:36:36.780 align:start position:0% code and it kind of it's structured in a way<00:36:33.580> to<00:36:33.730> make<00:36:34.000> you<00:36:34.180> believe<00:36:34.360> something<00:36:35.790> what 00:36:36.780 --> 00:36:36.790 align:start position:0% way to make you believe something what 00:36:36.790 --> 00:36:39.630 align:start position:0% way to make you believe something what that<00:36:36.970> isn't<00:36:37.270> actually<00:36:37.570> true<00:36:37.830> and<00:36:38.830> so<00:36:39.130> you<00:36:39.520> know 00:36:39.630 --> 00:36:39.640 align:start position:0% that isn't actually true and so you know 00:36:39.640 --> 00:36:42.270 align:start position:0% that isn't actually true and so you know like<00:36:40.260> when<00:36:41.260> you<00:36:41.350> get<00:36:41.440> that<00:36:41.620> inclination<00:36:41.830> to<00:36:42.190> be 00:36:42.270 --> 00:36:42.280 align:start position:0% like when you get that inclination to be 00:36:42.280 --> 00:36:43.860 align:start position:0% like when you get that inclination to be like<00:36:42.400> oh<00:36:42.490> should<00:36:42.700> be<00:36:42.790> really<00:36:43.060> this<00:36:43.180> should<00:36:43.420> be 00:36:43.860 --> 00:36:43.870 align:start position:0% like oh should be really this should be 00:36:43.870 --> 00:36:45.690 align:start position:0% like oh should be really this should be should<00:36:44.380> this<00:36:44.500> really<00:36:44.800> business<00:36:45.130> this<00:36:45.490> way 00:36:45.690 --> 00:36:45.700 align:start position:0% should this really business this way 00:36:45.700 --> 00:36:47.880 align:start position:0% should this really business this way it's<00:36:46.390> important<00:36:46.690> to<00:36:46.750> like<00:36:46.930> you<00:36:47.230> know<00:36:47.350> voice 00:36:47.880 --> 00:36:47.890 align:start position:0% it's important to like you know voice 00:36:47.890 --> 00:36:49.470 align:start position:0% it's important to like you know voice those<00:36:48.220> concerns<00:36:48.580> and<00:36:48.670> actually<00:36:48.940> act<00:36:49.120> on<00:36:49.300> them 00:36:49.470 --> 00:36:49.480 align:start position:0% those concerns and actually act on them 00:36:49.480 --> 00:36:51.270 align:start position:0% those concerns and actually act on them super<00:36:50.020> being<00:36:50.230> oh<00:36:50.440> I'm<00:36:50.740> sure<00:36:50.920> that's<00:36:51.070> fine 00:36:51.270 --> 00:36:51.280 align:start position:0% super being oh I'm sure that's fine 00:36:51.280 --> 00:36:54.150 align:start position:0% super being oh I'm sure that's fine nobody<00:36:51.580> would<00:36:51.760> get<00:36:51.880> that<00:36:52.000> wrong<00:36:53.070> you<00:36:54.070> know 00:36:54.150 --> 00:36:54.160 align:start position:0% nobody would get that wrong you know 00:36:54.160 --> 00:36:55.560 align:start position:0% nobody would get that wrong you know like<00:36:54.460> you<00:36:54.700> know<00:36:54.730> we've<00:36:54.970> seen<00:36:55.090> some<00:36:55.150> pretty 00:36:55.560 --> 00:36:55.570 align:start position:0% like you know we've seen some pretty 00:36:55.570 --> 00:36:59.850 align:start position:0% like you know we've seen some pretty pretty<00:36:56.520> drastic<00:36:58.170> outcomes<00:36:59.170> based<00:36:59.500> on<00:36:59.710> you 00:36:59.850 --> 00:36:59.860 align:start position:0% pretty drastic outcomes based on you 00:36:59.860 --> 00:37:02.580 align:start position:0% pretty drastic outcomes based on you know<00:36:59.980> that<00:37:00.160> kind<00:37:00.400> of<00:37:00.520> right<00:37:01.150> mind<00:37:02.110> said<00:37:02.260> two 00:37:02.580 --> 00:37:02.590 align:start position:0% know that kind of right mind said two 00:37:02.590 --> 00:37:13.070 align:start position:0% know that kind of right mind said two lines<00:37:02.830> being<00:37:03.160> flipped<00:37:03.460> yeah<00:37:11.340> our<00:37:12.340> message<00:37:12.790> is 00:37:13.070 --> 00:37:13.080 align:start position:0% lines being flipped yeah our message is 00:37:13.080 --> 00:37:16.470 align:start position:0% lines being flipped yeah our message is like<00:37:14.080> the<00:37:14.950> other<00:37:15.100> way<00:37:15.250> around<00:37:15.400> so<00:37:15.700> it<00:37:16.300> should 00:37:16.470 --> 00:37:16.480 align:start position:0% like the other way around so it should 00:37:16.480 --> 00:37:20.610 align:start position:0% like the other way around so it should say<00:37:16.870> steak<00:37:17.200> is<00:37:17.410> over<00:37:17.980> a<00:37:18.010> limit<00:37:19.140> because<00:37:20.140> that's 00:37:20.610 --> 00:37:20.620 align:start position:0% say steak is over a limit because that's 00:37:20.620 --> 00:37:31.590 align:start position:0% say steak is over a limit because that's what<00:37:20.860> it<00:37:21.370> throws<00:37:21.730> when<00:37:22.170> it<00:37:23.170> fails<00:37:29.910> no<00:37:30.910> no<00:37:31.210> this 00:37:31.590 --> 00:37:31.600 align:start position:0% what it throws when it fails no no this 00:37:31.600 --> 00:37:33.600 align:start position:0% what it throws when it fails no no this is<00:37:31.840> an<00:37:32.080> error<00:37:32.470> message<00:37:32.650> that<00:37:32.860> will<00:37:33.190> be<00:37:33.310> thrown 00:37:33.600 --> 00:37:33.610 align:start position:0% is an error message that will be thrown 00:37:33.610 --> 00:37:36.780 align:start position:0% is an error message that will be thrown right<00:37:34.000> so<00:37:34.390> it<00:37:34.540> should<00:37:34.750> what<00:37:35.740> went<00:37:36.160> wrong<00:37:36.370> but 00:37:36.780 --> 00:37:36.790 align:start position:0% right so it should what went wrong but 00:37:36.790 --> 00:37:40.050 align:start position:0% right so it should what went wrong but he<00:37:36.970> stated<00:37:37.330> what<00:37:37.750> was<00:37:38.380> violated<00:37:39.040> yeah<00:37:39.550> I<00:37:39.940> I 00:37:40.050 --> 00:37:40.060 align:start position:0% he stated what was violated yeah I I 00:37:40.060 --> 00:37:42.360 align:start position:0% he stated what was violated yeah I I agree<00:37:40.540> with<00:37:40.960> you<00:37:41.110> but<00:37:41.320> I<00:37:41.410> can<00:37:41.590> see<00:37:41.800> the<00:37:41.980> the 00:37:42.360 --> 00:37:42.370 align:start position:0% agree with you but I can see the the 00:37:42.370 --> 00:37:43.510 align:start position:0% agree with you but I can see the the other<00:37:42.490> side 00:37:43.510 --> 00:37:43.520 align:start position:0% other side 00:37:43.520 --> 00:37:44.770 align:start position:0% other side because<00:37:43.880> you<00:37:43.970> can<00:37:44.059> imagine<00:37:44.210> the<00:37:44.450> output<00:37:44.690> would 00:37:44.770 --> 00:37:44.780 align:start position:0% because you can imagine the output would 00:37:44.780 --> 00:37:46.839 align:start position:0% because you can imagine the output would say<00:37:44.900> fail<00:37:45.230> and<00:37:45.650> then<00:37:45.920> explain<00:37:46.460> what<00:37:46.609> was 00:37:46.839 --> 00:37:46.849 align:start position:0% say fail and then explain what was 00:37:46.849 --> 00:37:47.710 align:start position:0% say fail and then explain what was supposed<00:37:47.000> to<00:37:47.299> happen 00:37:47.710 --> 00:37:47.720 align:start position:0% supposed to happen 00:37:47.720 --> 00:37:51.849 align:start position:0% supposed to happen it's<00:37:48.079> I<00:37:49.900> this<00:37:50.900> is<00:37:51.079> a<00:37:51.140> question<00:37:51.440> going<00:37:51.589> back 00:37:51.849 --> 00:37:51.859 align:start position:0% it's I this is a question going back 00:37:51.859 --> 00:37:53.589 align:start position:0% it's I this is a question going back maybe<00:37:52.069> like<00:37:52.400> one<00:37:52.609> or<00:37:52.730> two<00:37:52.849> steps<00:37:53.059> when<00:37:53.390> we<00:37:53.540> were 00:37:53.589 --> 00:37:53.599 align:start position:0% maybe like one or two steps when we were 00:37:53.599 --> 00:37:55.359 align:start position:0% maybe like one or two steps when we were talking<00:37:53.869> about<00:37:53.930> wrapping<00:37:54.770> the<00:37:54.890> transfer 00:37:55.359 --> 00:37:55.369 align:start position:0% talking about wrapping the transfer 00:37:55.369 --> 00:37:57.849 align:start position:0% talking about wrapping the transfer function<00:37:55.760> and<00:37:55.940> a<00:37:56.299> require<00:37:56.690> is<00:37:57.020> that<00:37:57.650> like<00:37:57.829> a 00:37:57.849 --> 00:37:57.859 align:start position:0% function and a require is that like a 00:37:57.859 --> 00:37:59.589 align:start position:0% function and a require is that like a general<00:37:58.309> good<00:37:58.640> practice<00:37:59.089> for<00:37:59.119> when<00:37:59.359> you're 00:37:59.589 --> 00:37:59.599 align:start position:0% general good practice for when you're 00:37:59.599 --> 00:38:02.829 align:start position:0% general good practice for when you're making<00:37:59.750> a<00:38:00.079> call<00:38:00.290> out<00:38:00.500> to<00:38:00.740> another<00:38:01.839> contract 00:38:02.829 --> 00:38:02.839 align:start position:0% making a call out to another contract 00:38:02.839 --> 00:38:04.089 align:start position:0% making a call out to another contract function<00:38:03.260> that<00:38:03.380> you<00:38:03.470> should<00:38:03.619> wrap<00:38:03.859> it<00:38:03.890> or 00:38:04.089 --> 00:38:04.099 align:start position:0% function that you should wrap it or 00:38:04.099 --> 00:38:05.920 align:start position:0% function that you should wrap it or acquire<00:38:04.490> if<00:38:05.150> you<00:38:05.299> don't<00:38:05.450> have<00:38:05.599> some<00:38:05.750> other 00:38:05.920 --> 00:38:05.930 align:start position:0% acquire if you don't have some other 00:38:05.930 --> 00:38:08.200 align:start position:0% acquire if you don't have some other mechanism<00:38:06.500> to<00:38:06.710> check<00:38:07.460> to<00:38:07.579> be<00:38:07.700> sure<00:38:07.730> that<00:38:08.059> it's 00:38:08.200 --> 00:38:08.210 align:start position:0% mechanism to check to be sure that it's 00:38:08.210 --> 00:38:11.319 align:start position:0% mechanism to check to be sure that it's exceeded<00:38:08.809> yes<00:38:09.470> or<00:38:09.740> like<00:38:09.859> it<00:38:10.010> I<00:38:10.099> became<00:38:11.059> yeah<00:38:11.299> I 00:38:11.319 --> 00:38:11.329 align:start position:0% exceeded yes or like it I became yeah I 00:38:11.329 --> 00:38:12.789 align:start position:0% exceeded yes or like it I became yeah I mean<00:38:11.569> it<00:38:11.690> that's<00:38:11.960> a<00:38:11.990> good<00:38:12.079> question<00:38:12.410> so<00:38:12.619> like 00:38:12.789 --> 00:38:12.799 align:start position:0% mean it that's a good question so like 00:38:12.799 --> 00:38:15.640 align:start position:0% mean it that's a good question so like definitely<00:38:13.130> don't<00:38:13.460> take<00:38:13.940> from<00:38:14.240> this<00:38:14.480> that<00:38:15.020> you 00:38:15.640 --> 00:38:15.650 align:start position:0% definitely don't take from this that you 00:38:15.650 --> 00:38:17.170 align:start position:0% definitely don't take from this that you should<00:38:15.890> all<00:38:16.160> anytime<00:38:16.730> you're<00:38:16.849> always<00:38:16.940> calling 00:38:17.170 --> 00:38:17.180 align:start position:0% should all anytime you're always calling 00:38:17.180 --> 00:38:18.819 align:start position:0% should all anytime you're always calling out<00:38:17.359> you<00:38:17.480> should<00:38:17.660> always<00:38:17.930> represent<00:38:18.530> our<00:38:18.650> car 00:38:18.819 --> 00:38:18.829 align:start position:0% out you should always represent our car 00:38:18.829 --> 00:38:20.740 align:start position:0% out you should always represent our car because<00:38:19.130> that<00:38:19.160> in<00:38:19.549> itself<00:38:19.700> can<00:38:20.210> create 00:38:20.740 --> 00:38:20.750 align:start position:0% because that in itself can create 00:38:20.750 --> 00:38:22.660 align:start position:0% because that in itself can create vulnerabilities<00:38:20.990> right<00:38:21.740> like<00:38:22.250> if<00:38:22.400> there's<00:38:22.609> a 00:38:22.660 --> 00:38:22.670 align:start position:0% vulnerabilities right like if there's a 00:38:22.670 --> 00:38:24.849 align:start position:0% vulnerabilities right like if there's a contract<00:38:23.210> for<00:38:23.420> example<00:38:23.480> that<00:38:23.990> I<00:38:24.230> to<00:38:24.500> rates 00:38:24.849 --> 00:38:24.859 align:start position:0% contract for example that I to rates 00:38:24.859 --> 00:38:26.890 align:start position:0% contract for example that I to rates over<00:38:25.280> a<00:38:25.309> bunch<00:38:25.520> of<00:38:25.579> addresses<00:38:25.760> and<00:38:26.150> it<00:38:26.480> wants 00:38:26.890 --> 00:38:26.900 align:start position:0% over a bunch of addresses and it wants 00:38:26.900 --> 00:38:27.910 align:start position:0% over a bunch of addresses and it wants to<00:38:26.930> give<00:38:27.109> a<00:38:27.140> payout<00:38:27.380> to<00:38:27.619> each<00:38:27.740> of<00:38:27.859> those 00:38:27.910 --> 00:38:27.920 align:start position:0% to give a payout to each of those 00:38:27.920 --> 00:38:29.109 align:start position:0% to give a payout to each of those addresses<00:38:28.250> right<00:38:28.490> if<00:38:28.700> one<00:38:28.970> of<00:38:29.059> those 00:38:29.109 --> 00:38:29.119 align:start position:0% addresses right if one of those 00:38:29.119 --> 00:38:30.910 align:start position:0% addresses right if one of those addresses<00:38:29.329> is<00:38:29.720> a<00:38:29.750> smart<00:38:30.109> contract<00:38:30.290> that's 00:38:30.910 --> 00:38:30.920 align:start position:0% addresses is a smart contract that's 00:38:30.920 --> 00:38:33.400 align:start position:0% addresses is a smart contract that's malicious<00:38:31.549> it<00:38:31.819> can<00:38:32.210> just<00:38:32.359> throw<00:38:32.690> the<00:38:33.109> moment 00:38:33.400 --> 00:38:33.410 align:start position:0% malicious it can just throw the moment 00:38:33.410 --> 00:38:35.170 align:start position:0% malicious it can just throw the moment you<00:38:33.470> you<00:38:33.740> give<00:38:34.040> something<00:38:34.280> it<00:38:34.490> and<00:38:34.640> then<00:38:34.760> you 00:38:35.170 --> 00:38:35.180 align:start position:0% you you give something it and then you 00:38:35.180 --> 00:38:37.120 align:start position:0% you you give something it and then you you<00:38:35.390> send<00:38:35.630> something<00:38:35.750> to<00:38:35.869> it<00:38:36.140> and<00:38:36.290> then<00:38:36.770> all 00:38:37.120 --> 00:38:37.130 align:start position:0% you send something to it and then all 00:38:37.130 --> 00:38:38.950 align:start position:0% you send something to it and then all the<00:38:37.369> other<00:38:37.490> payouts<00:38:38.000> are<00:38:38.180> stuck<00:38:38.450> because<00:38:38.720> of 00:38:38.950 --> 00:38:38.960 align:start position:0% the other payouts are stuck because of 00:38:38.960 --> 00:38:40.210 align:start position:0% the other payouts are stuck because of my<00:38:39.079> malicious<00:38:39.410> contract<00:38:39.859> and<00:38:40.010> I<00:38:40.069> could 00:38:40.210 --> 00:38:40.220 align:start position:0% my malicious contract and I could 00:38:40.220 --> 00:38:42.190 align:start position:0% my malicious contract and I could blackmail<00:38:40.490> a<00:38:40.819> with<00:38:41.000> that<00:38:41.119> saying<00:38:41.450> now<00:38:41.960> you're 00:38:42.190 --> 00:38:42.200 align:start position:0% blackmail a with that saying now you're 00:38:42.200 --> 00:38:43.720 align:start position:0% blackmail a with that saying now you're gonna<00:38:42.319> you're<00:38:42.680> all<00:38:42.799> gonna<00:38:42.950> send<00:38:43.190> me<00:38:43.280> one 00:38:43.720 --> 00:38:43.730 align:start position:0% gonna you're all gonna send me one 00:38:43.730 --> 00:38:44.170 align:start position:0% gonna you're all gonna send me one either 00:38:44.170 --> 00:38:44.180 align:start position:0% either 00:38:44.180 --> 00:38:46.569 align:start position:0% either otherwise<00:38:44.839> I'm<00:38:45.230> gonna<00:38:45.829> block<00:38:46.040> your<00:38:46.190> to<00:38:46.400> either 00:38:46.569 --> 00:38:46.579 align:start position:0% otherwise I'm gonna block your to either 00:38:46.579 --> 00:38:48.430 align:start position:0% otherwise I'm gonna block your to either payout<00:38:46.880> forever<00:38:47.210> right<00:38:47.569> so<00:38:48.079> you<00:38:48.140> should 00:38:48.430 --> 00:38:48.440 align:start position:0% payout forever right so you should 00:38:48.440 --> 00:38:50.770 align:start position:0% payout forever right so you should always<00:38:49.280> you<00:38:49.819> should<00:38:49.849> first<00:38:50.180> first<00:38:50.630> of<00:38:50.690> all<00:38:50.750> I 00:38:50.770 --> 00:38:50.780 align:start position:0% always you should first first of all I 00:38:50.780 --> 00:38:52.150 align:start position:0% always you should first first of all I try<00:38:50.839> not<00:38:50.990> to<00:38:51.109> do<00:38:51.200> that<00:38:51.319> loop<00:38:51.530> contract<00:38:52.010> which 00:38:52.150 --> 00:38:52.160 align:start position:0% try not to do that loop contract which 00:38:52.160 --> 00:38:55.569 align:start position:0% try not to do that loop contract which is<00:38:52.280> bad<00:38:52.430> but<00:38:52.849> besides<00:38:53.150> that<00:38:53.290> you<00:38:54.290> should<00:38:54.619> you 00:38:55.569 --> 00:38:55.579 align:start position:0% is bad but besides that you should you 00:38:55.579 --> 00:38:57.220 align:start position:0% is bad but besides that you should you should<00:38:55.609> wrap<00:38:55.940> things<00:38:56.299> weren't<00:38:56.480> requires<00:38:56.809> if 00:38:57.220 --> 00:38:57.230 align:start position:0% should wrap things weren't requires if 00:38:57.230 --> 00:39:02.460 align:start position:0% should wrap things weren't requires if and<00:38:57.650> only<00:38:57.710> if<00:38:59.140> that<00:39:00.140> line<00:39:00.859> failing<00:39:01.460> is<00:39:01.640> just 00:39:02.460 --> 00:39:02.470 align:start position:0% and only if that line failing is just 00:39:02.470 --> 00:39:04.510 align:start position:0% and only if that line failing is just critical<00:39:03.470> damage<00:39:03.619> to<00:39:03.890> your<00:39:03.980> contract<00:39:04.369> right 00:39:04.510 --> 00:39:04.520 align:start position:0% critical damage to your contract right 00:39:04.520 --> 00:39:07.780 align:start position:0% critical damage to your contract right if<00:39:04.670> it<00:39:05.059> if<00:39:05.270> like<00:39:05.599> if<00:39:05.990> this<00:39:06.680> line<00:39:06.920> fails<00:39:07.220> then 00:39:07.780 --> 00:39:07.790 align:start position:0% if it if like if this line fails then 00:39:07.790 --> 00:39:09.609 align:start position:0% if it if like if this line fails then nothing<00:39:08.420> should<00:39:08.540> happen<00:39:08.599> right<00:39:09.140> otherwise 00:39:09.609 --> 00:39:09.619 align:start position:0% nothing should happen right otherwise 00:39:09.619 --> 00:39:12.640 align:start position:0% nothing should happen right otherwise try<00:39:10.549> to<00:39:10.609> catch<00:39:10.819> the<00:39:11.210> return<00:39:11.540> right<00:39:11.900> if<00:39:12.109> there 00:39:12.640 --> 00:39:12.650 align:start position:0% try to catch the return right if there 00:39:12.650 --> 00:39:14.289 align:start position:0% try to catch the return right if there is<00:39:12.770> a<00:39:12.799> return<00:39:13.160> you<00:39:13.369> need<00:39:13.549> to<00:39:13.640> be<00:39:13.700> very<00:39:13.849> context 00:39:14.289 --> 00:39:14.299 align:start position:0% is a return you need to be very context 00:39:14.299 --> 00:39:17.349 align:start position:0% is a return you need to be very context aware<00:39:15.369> yeah<00:39:16.369> it<00:39:16.640> looks<00:39:16.940> like<00:39:16.970> important<00:39:17.270> has 00:39:17.349 --> 00:39:17.359 align:start position:0% aware yeah it looks like important has 00:39:17.359 --> 00:39:19.960 align:start position:0% aware yeah it looks like important has something<00:39:17.569> yeah<00:39:18.079> so<00:39:18.410> I<00:39:18.589> think<00:39:19.010> isn't<00:39:19.160> there<00:39:19.520> an 00:39:19.960 --> 00:39:19.970 align:start position:0% something yeah so I think isn't there an 00:39:19.970 --> 00:39:23.950 align:start position:0% something yeah so I think isn't there an hour<00:39:20.210> program<00:39:20.720> on<00:39:21.049> in<00:39:22.040> deposit<00:39:22.660> Texas<00:39:23.660> I<00:39:23.690> mean 00:39:23.950 --> 00:39:23.960 align:start position:0% hour program on in deposit Texas I mean 00:39:23.960 --> 00:39:26.730 align:start position:0% hour program on in deposit Texas I mean internal<00:39:24.440> function<00:39:24.890> but<00:39:25.069> an<00:39:25.280> overflow 00:39:26.730 --> 00:39:26.740 align:start position:0% internal function but an overflow 00:39:26.740 --> 00:39:29.710 align:start position:0% internal function but an overflow because<00:39:27.740> the<00:39:28.069> balance<00:39:28.490> the<00:39:28.670> amount<00:39:28.970> is<00:39:29.329> you<00:39:29.569> in 00:39:29.710 --> 00:39:29.720 align:start position:0% because the balance the amount is you in 00:39:29.720 --> 00:39:33.280 align:start position:0% because the balance the amount is you in 256<00:39:30.369> which<00:39:31.369> arrives<00:39:31.910> from<00:39:32.299> a<00:39:32.359> couple<00:39:32.720> of<00:39:32.869> lines 00:39:33.280 --> 00:39:33.290 align:start position:0% 256 which arrives from a couple of lines 00:39:33.290 --> 00:39:38.260 align:start position:0% 256 which arrives from a couple of lines above<00:39:33.770> and<00:39:34.579> it<00:39:34.849> is<00:39:35.710> addition<00:39:36.710> there<00:39:37.270> without 00:39:38.260 --> 00:39:38.270 align:start position:0% above and it is addition there without 00:39:38.270 --> 00:39:41.530 align:start position:0% above and it is addition there without overflow<00:39:39.069> checking<00:39:40.069> it<00:39:40.520> will<00:39:40.730> overflow<00:39:41.030> the 00:39:41.530 --> 00:39:41.540 align:start position:0% overflow checking it will overflow the 00:39:41.540 --> 00:39:43.210 align:start position:0% overflow checking it will overflow the new<00:39:41.660> balance<00:39:41.900> will<00:39:42.200> be<00:39:42.440> below<00:39:42.799> the<00:39:42.829> stake 00:39:43.210 --> 00:39:43.220 align:start position:0% new balance will be below the stake 00:39:43.220 --> 00:39:46.720 align:start position:0% new balance will be below the stake limits<00:39:43.640> or<00:39:44.089> well<00:39:45.049> not<00:39:46.040> necessarily 00:39:46.720 --> 00:39:46.730 align:start position:0% limits or well not necessarily 00:39:46.730 --> 00:39:50.319 align:start position:0% limits or well not necessarily so<00:39:47.599> or<00:39:48.140> maybe<00:39:48.380> necessarily<00:39:48.890> from<00:39:49.640> from<00:39:50.180> a 00:39:50.319 --> 00:39:50.329 align:start position:0% so or maybe necessarily from from a 00:39:50.329 --> 00:39:51.819 align:start position:0% so or maybe necessarily from from a quick<00:39:50.750> look<00:39:50.960> through<00:39:50.990> I<00:39:51.260> think<00:39:51.440> all<00:39:51.710> the 00:39:51.819 --> 00:39:51.829 align:start position:0% quick look through I think all the 00:39:51.829 --> 00:39:54.460 align:start position:0% quick look through I think all the places<00:39:52.040> deposited<00:39:52.730> called<00:39:53.000> the<00:39:53.569> amount<00:39:54.230> of 00:39:54.460 --> 00:39:54.470 align:start position:0% places deposited called the amount of 00:39:54.470 --> 00:39:56.720 align:start position:0% places deposited called the amount of seat<00:39:54.770> by<00:39:55.040> the<00:39:55.099> smart<00:39:55.520> contract<00:39:56.030> so<00:39:56.329> it<00:39:56.450> can 00:39:56.720 --> 00:39:56.730 align:start position:0% seat by the smart contract so it can 00:39:56.730 --> 00:40:00.110 align:start position:0% seat by the smart contract so it can sure<00:39:57.740> you<00:39:58.740> know<00:39:58.860> that<00:39:59.130> last<00:39:59.430> total<00:39:59.640> suppliers 00:40:00.110 --> 00:40:00.120 align:start position:0% sure you know that last total suppliers 00:40:00.120 --> 00:40:02.330 align:start position:0% sure you know that last total suppliers not<00:40:00.570> overflowed<00:40:01.170> but<00:40:01.380> it's<00:40:01.530> it<00:40:01.830> speaks<00:40:02.220> to 00:40:02.330 --> 00:40:02.340 align:start position:0% not overflowed but it's it speaks to 00:40:02.340 --> 00:40:04.730 align:start position:0% not overflowed but it's it speaks to talking<00:40:02.730> about<00:40:02.970> making<00:40:03.600> ng<00:40:03.810> fragile<00:40:04.170> code<00:40:04.380> we 00:40:04.730 --> 00:40:04.740 align:start position:0% talking about making ng fragile code we 00:40:04.740 --> 00:40:06.860 align:start position:0% talking about making ng fragile code we you<00:40:04.920> should<00:40:04.980> add<00:40:05.700> these<00:40:05.970> chicks<00:40:06.300> even<00:40:06.690> if<00:40:06.780> you 00:40:06.860 --> 00:40:06.870 align:start position:0% you should add these chicks even if you 00:40:06.870 --> 00:40:09.740 align:start position:0% you should add these chicks even if you don't<00:40:07.050> think<00:40:07.140> they<00:40:07.350> can<00:40:07.410> happen<00:40:08.480> is<00:40:09.480> the<00:40:09.600> code 00:40:09.740 --> 00:40:09.750 align:start position:0% don't think they can happen is the code 00:40:09.750 --> 00:40:11.360 align:start position:0% don't think they can happen is the code more<00:40:09.930> readable<00:40:09.960> even<00:40:10.650> if<00:40:10.740> it's<00:40:11.040> gonna<00:40:11.190> be 00:40:11.360 --> 00:40:11.370 align:start position:0% more readable even if it's gonna be 00:40:11.370 --> 00:40:12.740 align:start position:0% more readable even if it's gonna be guaranteed<00:40:11.730> it's<00:40:11.880> nice<00:40:12.030> for<00:40:12.330> a<00:40:12.390> read<00:40:12.600> really 00:40:12.740 --> 00:40:12.750 align:start position:0% guaranteed it's nice for a read really 00:40:12.750 --> 00:40:14.390 align:start position:0% guaranteed it's nice for a read really point<00:40:13.020> of<00:40:13.080> view<00:40:13.170> just<00:40:13.200> scroll<00:40:13.800> up<00:40:13.950> a<00:40:13.980> bit<00:40:14.190> so<00:40:14.310> we 00:40:14.390 --> 00:40:14.400 align:start position:0% point of view just scroll up a bit so we 00:40:14.400 --> 00:40:17.480 align:start position:0% point of view just scroll up a bit so we see<00:40:14.580> where<00:40:14.760> it's<00:40:14.910> called<00:40:15.150> the<00:40:15.390> deposits<00:40:16.490> so 00:40:17.480 --> 00:40:17.490 align:start position:0% see where it's called the deposits so 00:40:17.490 --> 00:40:19.070 align:start position:0% see where it's called the deposits so there's<00:40:17.670> one<00:40:17.790> a<00:40:17.820> deposit<00:40:18.300> jobs<00:40:18.510> take<00:40:18.750> as<00:40:18.930> well 00:40:19.070 --> 00:40:19.080 align:start position:0% there's one a deposit jobs take as well 00:40:19.080 --> 00:40:21.170 align:start position:0% there's one a deposit jobs take as well yeah<00:40:19.950> it's<00:40:20.160> called<00:40:20.310> a<00:40:20.400> few<00:40:20.550> times<00:40:20.580> so<00:40:21.090> that 00:40:21.170 --> 00:40:21.180 align:start position:0% yeah it's called a few times so that 00:40:21.180 --> 00:40:23.390 align:start position:0% yeah it's called a few times so that calls<00:40:21.540> deposit<00:40:22.110> but<00:40:22.380> required<00:40:22.740> stake<00:40:23.100> there 00:40:23.390 --> 00:40:23.400 align:start position:0% calls deposit but required stake there 00:40:23.400 --> 00:40:25.930 align:start position:0% calls deposit but required stake there comes<00:40:23.670> from<00:40:23.850> public<00:40:24.810> as<00:40:25.200> state<00:40:25.800> variable 00:40:25.930 --> 00:40:25.940 align:start position:0% comes from public as state variable 00:40:25.940 --> 00:40:32.830 align:start position:0% comes from public as state variable contract<00:40:30.440> and<00:40:31.440> I<00:40:31.530> guess<00:40:31.680> that's<00:40:31.920> the<00:40:32.040> only<00:40:32.280> one 00:40:32.830 --> 00:40:32.840 align:start position:0% contract and I guess that's the only one 00:40:32.840 --> 00:40:36.350 align:start position:0% contract and I guess that's the only one there<00:40:33.840> as<00:40:34.080> well<00:40:34.290> it<00:40:34.800> was<00:40:34.920> required<00:40:35.360> several 00:40:36.350 --> 00:40:36.360 align:start position:0% there as well it was required several 00:40:36.360 --> 00:40:38.060 align:start position:0% there as well it was required several calls<00:40:36.540> to<00:40:36.660> it<00:40:36.840> but<00:40:36.960> an<00:40:37.050> HS<00:40:37.350> I<00:40:37.650> think<00:40:37.830> it<00:40:37.920> comes 00:40:38.060 --> 00:40:38.070 align:start position:0% calls to it but an HS I think it comes 00:40:38.070 --> 00:40:40.820 align:start position:0% calls to it but an HS I think it comes from<00:40:38.190> a<00:40:38.340> state<00:40:38.550> variable<00:40:38.760> yeah<00:40:39.480> yeah<00:40:40.320> given 00:40:40.820 --> 00:40:40.830 align:start position:0% from a state variable yeah yeah given 00:40:40.830 --> 00:40:43.370 align:start position:0% from a state variable yeah yeah given the<00:40:40.920> context<00:40:41.430> that's<00:40:41.670> fine<00:40:42.000> but<00:40:42.390> it's<00:40:43.170> not 00:40:43.370 --> 00:40:43.380 align:start position:0% the context that's fine but it's not 00:40:43.380 --> 00:40:46.010 align:start position:0% the context that's fine but it's not robust<00:40:43.800> yeah<00:40:44.400> yeah<00:40:44.670> and<00:40:44.880> I<00:40:44.940> think<00:40:45.150> this<00:40:45.870> is 00:40:46.010 --> 00:40:46.020 align:start position:0% robust yeah yeah and I think this is 00:40:46.020 --> 00:40:48.170 align:start position:0% robust yeah yeah and I think this is also<00:40:46.440> another<00:40:46.710> good<00:40:46.920> point<00:40:47.070> I<00:40:47.310> always<00:40:47.730> sort<00:40:48.090> of 00:40:48.170 --> 00:40:48.180 align:start position:0% also another good point I always sort of 00:40:48.180 --> 00:40:50.930 align:start position:0% also another good point I always sort of suggest<00:40:48.570> that<00:40:48.960> if<00:40:49.260> you<00:40:49.680> have<00:40:49.940> multiple 00:40:50.930 --> 00:40:50.940 align:start position:0% suggest that if you have multiple 00:40:50.940 --> 00:40:53.270 align:start position:0% suggest that if you have multiple functions<00:40:51.570> right<00:40:52.020> calling<00:40:52.680> a<00:40:52.860> lower-level 00:40:53.270 --> 00:40:53.280 align:start position:0% functions right calling a lower-level 00:40:53.280 --> 00:40:55.250 align:start position:0% functions right calling a lower-level function<00:40:54.030> or<00:40:54.240> like<00:40:54.390> an<00:40:54.480> internal<00:40:54.750> function 00:40:55.250 --> 00:40:55.260 align:start position:0% function or like an internal function 00:40:55.260 --> 00:40:59.210 align:start position:0% function or like an internal function and<00:40:55.550> there<00:40:56.550> is<00:40:56.670> some<00:40:56.940> a<00:40:57.410> security<00:40:58.410> issue<00:40:58.800> that 00:40:59.210 --> 00:40:59.220 align:start position:0% and there is some a security issue that 00:40:59.220 --> 00:41:01.850 align:start position:0% and there is some a security issue that could<00:40:59.460> arise<00:40:59.700> if<00:41:00.300> those<00:41:00.660> wrapping<00:41:01.380> functions 00:41:01.850 --> 00:41:01.860 align:start position:0% could arise if those wrapping functions 00:41:01.860 --> 00:41:03.650 align:start position:0% could arise if those wrapping functions do<00:41:02.070> not<00:41:02.100> do<00:41:02.490> a<00:41:02.520> performance<00:41:02.940> or<00:41:03.180> an<00:41:03.240> action<00:41:03.510> in 00:41:03.650 --> 00:41:03.660 align:start position:0% do not do a performance or an action in 00:41:03.660 --> 00:41:05.510 align:start position:0% do not do a performance or an action in this<00:41:03.780> case<00:41:04.020> making<00:41:04.620> sure<00:41:04.740> that<00:41:04.980> the<00:41:05.100> allowance 00:41:05.510 --> 00:41:05.520 align:start position:0% this case making sure that the allowance 00:41:05.520 --> 00:41:08.390 align:start position:0% this case making sure that the allowance is<00:41:05.700> within<00:41:06.660> a<00:41:06.780> certain<00:41:06.810> value<00:41:07.080> then<00:41:07.830> you 00:41:08.390 --> 00:41:08.400 align:start position:0% is within a certain value then you 00:41:08.400 --> 00:41:11.720 align:start position:0% is within a certain value then you should<00:41:08.580> absolutely<00:41:09.150> move<00:41:10.160> the<00:41:11.160> track<00:41:11.460> or<00:41:11.700> the 00:41:11.720 --> 00:41:11.730 align:start position:0% should absolutely move the track or the 00:41:11.730 --> 00:41:14.060 align:start position:0% should absolutely move the track or the constraint<00:41:12.180> to<00:41:12.390> the<00:41:12.870> shared<00:41:13.500> function<00:41:13.890> right 00:41:14.060 --> 00:41:14.070 align:start position:0% constraint to the shared function right 00:41:14.070 --> 00:41:16.930 align:start position:0% constraint to the shared function right so<00:41:14.400> in<00:41:14.790> here<00:41:15.180> for<00:41:15.360> example<00:41:15.720> like<00:41:15.870> you<00:41:16.110> know<00:41:16.530> buy 00:41:16.930 --> 00:41:16.940 align:start position:0% so in here for example like you know buy 00:41:16.940 --> 00:41:22.430 align:start position:0% so in here for example like you know buy buy<00:41:18.770> buy<00:41:19.770> work<00:41:20.190> wait<00:41:20.570> by<00:41:21.570> you<00:41:21.990> know<00:41:22.080> putting 00:41:22.430 --> 00:41:22.440 align:start position:0% buy buy work wait by you know putting 00:41:22.440 --> 00:41:27.140 align:start position:0% buy buy work wait by you know putting safe<00:41:22.740> math<00:41:22.980> here<00:41:23.570> you<00:41:24.570> you<00:41:25.490> take<00:41:26.490> away<00:41:26.730> an 00:41:27.140 --> 00:41:27.150 align:start position:0% safe math here you you take away an 00:41:27.150 --> 00:41:29.300 align:start position:0% safe math here you you take away an overflow<00:41:27.630> vulnerability<00:41:27.900> from<00:41:28.590> any<00:41:28.860> function 00:41:29.300 --> 00:41:29.310 align:start position:0% overflow vulnerability from any function 00:41:29.310 --> 00:41:30.950 align:start position:0% overflow vulnerability from any function that<00:41:29.400> uses<00:41:29.520> this<00:41:29.790> function<00:41:30.210> and<00:41:30.360> so<00:41:30.480> the 00:41:30.950 --> 00:41:30.960 align:start position:0% that uses this function and so the 00:41:30.960 --> 00:41:33.170 align:start position:0% that uses this function and so the people<00:41:31.140> you<00:41:31.830> know<00:41:31.920> when<00:41:32.280> you're<00:41:32.460> extending<00:41:32.940> in 00:41:33.170 --> 00:41:33.180 align:start position:0% people you know when you're extending in 00:41:33.180 --> 00:41:34.340 align:start position:0% people you know when you're extending in the<00:41:33.240> future<00:41:33.540> when<00:41:33.720> people<00:41:34.020> are<00:41:34.110> billing 00:41:34.340 --> 00:41:34.350 align:start position:0% the future when people are billing 00:41:34.350 --> 00:41:35.990 align:start position:0% the future when people are billing against<00:41:34.620> your<00:41:34.710> API<00:41:34.950> they<00:41:35.580> don't<00:41:35.730> have<00:41:35.820> to<00:41:35.910> have 00:41:35.990 --> 00:41:36.000 align:start position:0% against your API they don't have to have 00:41:36.000 --> 00:41:37.760 align:start position:0% against your API they don't have to have the<00:41:36.090> cognate<00:41:36.450> overhead<00:41:36.840> of<00:41:36.990> or<00:41:37.170> oh<00:41:37.380> this 00:41:37.760 --> 00:41:37.770 align:start position:0% the cognate overhead of or oh this 00:41:37.770 --> 00:41:39.170 align:start position:0% the cognate overhead of or oh this function<00:41:38.100> is<00:41:38.220> vulnerable<00:41:38.640> to<00:41:38.700> overflows 00:41:39.170 --> 00:41:39.180 align:start position:0% function is vulnerable to overflows 00:41:39.180 --> 00:41:40.940 align:start position:0% function is vulnerable to overflows right<00:41:39.480> so<00:41:39.840> if<00:41:39.990> there's<00:41:40.170> if<00:41:40.380> there's<00:41:40.650> a 00:41:40.940 --> 00:41:40.950 align:start position:0% right so if there's if there's a 00:41:40.950 --> 00:41:44.180 align:start position:0% right so if there's if there's a mitigation<00:41:41.670> that<00:41:42.180> you<00:41:42.330> can<00:41:42.630> build<00:41:43.590> in<00:41:43.800> that's 00:41:44.180 --> 00:41:44.190 align:start position:0% mitigation that you can build in that's 00:41:44.190 --> 00:41:46.370 align:start position:0% mitigation that you can build in that's you<00:41:44.760> know<00:41:44.880> the<00:41:45.540> where<00:41:45.720> there's<00:41:46.110> an<00:41:46.200> issue 00:41:46.370 --> 00:41:46.380 align:start position:0% you know the where there's an issue 00:41:46.380 --> 00:41:49.580 align:start position:0% you know the where there's an issue that's<00:41:47.180> suffered<00:41:48.180> that<00:41:48.450> multiple<00:41:49.230> functions 00:41:49.580 --> 00:41:49.590 align:start position:0% that's suffered that multiple functions 00:41:49.590 --> 00:41:52.640 align:start position:0% that's suffered that multiple functions may<00:41:49.740> suffer<00:41:50.070> always<00:41:50.700> put<00:41:50.940> that<00:41:51.440> mitigation<00:41:52.440> in 00:41:52.640 --> 00:41:52.650 align:start position:0% may suffer always put that mitigation in 00:41:52.650 --> 00:41:57.890 align:start position:0% may suffer always put that mitigation in the<00:41:53.340> most<00:41:54.270> deep<00:41:54.720> function<00:41:55.440> call<00:41:56.900> another 00:41:57.890 --> 00:41:57.900 align:start position:0% the most deep function call another 00:41:57.900 --> 00:42:00.140 align:start position:0% the most deep function call another question<00:41:58.320> there's<00:41:58.980> a<00:41:59.070> function<00:41:59.670> a<00:41:59.730> a<00:41:59.760> select 00:42:00.140 --> 00:42:00.150 align:start position:0% question there's a function a a select 00:42:00.150 --> 00:42:02.000 align:start position:0% question there's a function a a select work<00:42:00.390> or<00:42:00.600> I<00:42:00.630> assume<00:42:00.960> the<00:42:01.140> goal<00:42:01.500> is<00:42:01.710> that<00:42:01.860> that 00:42:02.000 --> 00:42:02.010 align:start position:0% work or I assume the goal is that that 00:42:02.010 --> 00:42:05.720 align:start position:0% work or I assume the goal is that that gets<00:42:02.190> called<00:42:02.400> off<00:42:02.520> chain<00:42:03.860> the<00:42:04.860> select<00:42:05.250> worker 00:42:05.720 --> 00:42:05.730 align:start position:0% gets called off chain the select worker 00:42:05.730 --> 00:42:08.230 align:start position:0% gets called off chain the select worker function<00:42:06.270> does<00:42:06.990> that<00:42:07.140> get<00:42:07.320> called<00:42:07.530> off<00:42:07.710> chain 00:42:08.230 --> 00:42:08.240 align:start position:0% function does that get called off chain 00:42:08.240 --> 00:42:10.580 align:start position:0% function does that get called off chain no<00:42:09.240> it<00:42:09.390> does<00:42:09.570> get<00:42:09.750> called<00:42:09.990> on 00:42:10.580 --> 00:42:10.590 align:start position:0% no it does get called on 00:42:10.590 --> 00:42:12.110 align:start position:0% no it does get called on by<00:42:10.950> something<00:42:11.250> else<00:42:11.490> that<00:42:11.640> supplies<00:42:11.940> the 00:42:12.110 --> 00:42:12.120 align:start position:0% by something else that supplies the 00:42:12.120 --> 00:42:15.440 align:start position:0% by something else that supplies the entropy<00:42:12.360> okay<00:42:13.200> by<00:42:13.470> a<00:42:13.550> another<00:42:14.550> smart<00:42:14.940> contract 00:42:15.440 --> 00:42:15.450 align:start position:0% entropy okay by a another smart contract 00:42:15.450 --> 00:42:18.400 align:start position:0% entropy okay by a another smart contract then<00:42:15.690> essentially<00:42:16.650> the<00:42:16.830> job<00:42:17.040> manager<00:42:17.310> right 00:42:18.400 --> 00:42:18.410 align:start position:0% then essentially the job manager right 00:42:18.410 --> 00:42:20.540 align:start position:0% then essentially the job manager right one<00:42:19.410> thing<00:42:19.590> to<00:42:19.680> bear<00:42:19.800> in<00:42:19.860> mind<00:42:20.040> there<00:42:20.220> is<00:42:20.370> you 00:42:20.540 --> 00:42:20.550 align:start position:0% one thing to bear in mind there is you 00:42:20.550 --> 00:42:22.670 align:start position:0% one thing to bear in mind there is you may<00:42:20.760> not<00:42:20.940> be<00:42:21.180> selecting<00:42:21.810> uniformly<00:42:22.530> at<00:42:22.650> random 00:42:22.670 --> 00:42:22.680 align:start position:0% may not be selecting uniformly at random 00:42:22.680 --> 00:42:25.070 align:start position:0% may not be selecting uniformly at random because<00:42:23.430> of<00:42:23.580> your<00:42:23.820> range<00:42:24.330> the<00:42:24.660> range<00:42:24.690> of<00:42:24.990> your 00:42:25.070 --> 00:42:25.080 align:start position:0% because of your range the range of your 00:42:25.080 --> 00:42:28.100 align:start position:0% because of your range the range of your random<00:42:25.350> values<00:42:25.710> is<00:42:25.920> modulo<00:42:26.670> of<00:42:26.880> the<00:42:27.150> size<00:42:27.750> so 00:42:28.100 --> 00:42:28.110 align:start position:0% random values is modulo of the size so 00:42:28.110 --> 00:42:30.320 align:start position:0% random values is modulo of the size so probably<00:42:29.100> a<00:42:29.220> better<00:42:29.460> approach<00:42:29.850> would<00:42:30.150> be<00:42:30.180> to 00:42:30.320 --> 00:42:30.330 align:start position:0% probably a better approach would be to 00:42:30.330 --> 00:42:32.660 align:start position:0% probably a better approach would be to expose<00:42:30.930> the<00:42:31.170> number<00:42:31.440> of<00:42:31.530> stake<00:42:31.770> is<00:42:32.010> expose<00:42:32.640> a 00:42:32.660 --> 00:42:32.670 align:start position:0% expose the number of stake is expose a 00:42:32.670 --> 00:42:34.490 align:start position:0% expose the number of stake is expose a way<00:42:32.850> to<00:42:32.910> index<00:42:33.240> the<00:42:33.450> stagers<00:42:33.870> and<00:42:34.140> then<00:42:34.380> let 00:42:34.490 --> 00:42:34.500 align:start position:0% way to index the stagers and then let 00:42:34.500 --> 00:42:37.400 align:start position:0% way to index the stagers and then let the<00:42:34.650> caller<00:42:34.860> figure<00:42:35.700> out<00:42:35.850> how<00:42:36.090> to<00:42:36.410> select 00:42:37.400 --> 00:42:37.410 align:start position:0% the caller figure out how to select 00:42:37.410 --> 00:42:39.800 align:start position:0% the caller figure out how to select uniformly<00:42:37.980> at<00:42:38.130> random<00:42:38.240> because<00:42:39.240> this<00:42:39.480> hides 00:42:39.800 --> 00:42:39.810 align:start position:0% uniformly at random because this hides 00:42:39.810 --> 00:42:41.840 align:start position:0% uniformly at random because this hides the<00:42:40.110> fact<00:42:40.290> that<00:42:40.500> it's<00:42:40.740> doing<00:42:41.040> modulo<00:42:41.460> and<00:42:41.790> you 00:42:41.840 --> 00:42:41.850 align:start position:0% the fact that it's doing modulo and you 00:42:41.850 --> 00:42:44.120 align:start position:0% the fact that it's doing modulo and you think<00:42:42.120> it's<00:42:42.300> just<00:42:42.630> you<00:42:43.080> know<00:42:43.170> magically<00:42:43.950> gets 00:42:44.120 --> 00:42:44.130 align:start position:0% think it's just you know magically gets 00:42:44.130 --> 00:42:45.860 align:start position:0% think it's just you know magically gets an<00:42:44.250> even<00:42:44.340> distribution<00:42:44.700> if<00:42:45.420> you<00:42:45.570> google 00:42:45.860 --> 00:42:45.870 align:start position:0% an even distribution if you google 00:42:45.870 --> 00:42:47.870 align:start position:0% an even distribution if you google modulo<00:42:46.260> bias<00:42:46.530> you'll<00:42:46.800> find<00:42:47.040> a<00:42:47.220> nice<00:42:47.400> concise 00:42:47.870 --> 00:42:47.880 align:start position:0% modulo bias you'll find a nice concise 00:42:47.880 --> 00:42:50.750 align:start position:0% modulo bias you'll find a nice concise way<00:42:48.180> to<00:42:48.240> take<00:42:49.200> the<00:42:49.320> backs<00:42:49.530> minus<00:42:50.040> the<00:42:50.310> modulo 00:42:50.750 --> 00:42:50.760 align:start position:0% way to take the backs minus the modulo 00:42:50.760 --> 00:42:53.660 align:start position:0% way to take the backs minus the modulo minus<00:42:51.120> the<00:42:51.330> size<00:42:51.620> it's<00:42:52.620> like<00:42:52.770> a<00:42:53.010> little<00:42:53.490> more 00:42:53.660 --> 00:42:53.670 align:start position:0% minus the size it's like a little more 00:42:53.670 --> 00:42:55.610 align:start position:0% minus the size it's like a little more complicated<00:42:54.030> but<00:42:54.090> you<00:42:54.150> you<00:42:54.990> defeat<00:42:55.290> modulo 00:42:55.610 --> 00:42:55.620 align:start position:0% complicated but you you defeat modulo 00:42:55.620 --> 00:42:57.740 align:start position:0% complicated but you you defeat modulo bias<00:42:55.860> and<00:42:56.730> of<00:42:56.850> course<00:42:57.060> if<00:42:57.210> you're<00:42:57.360> doing<00:42:57.390> the 00:42:57.740 --> 00:42:57.750 align:start position:0% bias and of course if you're doing the 00:42:57.750 --> 00:43:01.130 align:start position:0% bias and of course if you're doing the chicks<00:42:58.290> on<00:42:58.890> chain<00:42:59.310> doing<00:43:00.150> the<00:43:00.270> pseudo-random 00:43:01.130 --> 00:43:01.140 align:start position:0% chicks on chain doing the pseudo-random 00:43:01.140 --> 00:43:02.780 align:start position:0% chicks on chain doing the pseudo-random generation<00:43:01.740> on<00:43:01.860> chain<00:43:02.130> and<00:43:02.370> all<00:43:02.460> the<00:43:02.610> usual 00:43:02.780 --> 00:43:02.790 align:start position:0% generation on chain and all the usual 00:43:02.790 --> 00:43:07.940 align:start position:0% generation on chain and all the usual caveats<00:43:03.210> about<00:43:05.480> apply<00:43:06.480> and<00:43:06.900> yeah<00:43:07.350> and<00:43:07.650> this<00:43:07.740> is 00:43:07.940 --> 00:43:07.950 align:start position:0% caveats about apply and yeah and this is 00:43:07.950 --> 00:43:10.400 align:start position:0% caveats about apply and yeah and this is also<00:43:08.460> vulnerable<00:43:09.000> to<00:43:09.420> a<00:43:09.540> front<00:43:09.870> running<00:43:10.080> if 00:43:10.400 --> 00:43:10.410 align:start position:0% also vulnerable to a front running if 00:43:10.410 --> 00:43:13.640 align:start position:0% also vulnerable to a front running if you<00:43:10.500> can<00:43:11.240> you<00:43:12.240> know<00:43:12.270> increase<00:43:12.750> the<00:43:12.930> length<00:43:13.350> of 00:43:13.640 --> 00:43:13.650 align:start position:0% you can you know increase the length of 00:43:13.650 --> 00:43:15.160 align:start position:0% you can you know increase the length of the<00:43:14.280> stagers 00:43:15.160 --> 00:43:15.170 align:start position:0% the stagers 00:43:15.170 --> 00:43:18.140 align:start position:0% the stagers before<00:43:16.170> that<00:43:16.500> select<00:43:17.190> worker<00:43:17.430> gets<00:43:17.820> a<00:43:17.910> called 00:43:18.140 --> 00:43:18.150 align:start position:0% before that select worker gets a called 00:43:18.150 --> 00:43:20.630 align:start position:0% before that select worker gets a called yes<00:43:18.600> so<00:43:18.840> if<00:43:19.380> you<00:43:19.530> are<00:43:19.650> off<00:43:19.800> by<00:43:20.010> one<00:43:20.040> from<00:43:20.490> being 00:43:20.630 --> 00:43:20.640 align:start position:0% yes so if you are off by one from being 00:43:20.640 --> 00:43:24.650 align:start position:0% yes so if you are off by one from being chosen<00:43:20.910> yeah<00:43:21.540> yeah<00:43:23.180> so<00:43:24.180> I<00:43:24.210> have<00:43:24.450> a<00:43:24.510> question 00:43:24.650 --> 00:43:24.660 align:start position:0% chosen yeah yeah so I have a question 00:43:24.660 --> 00:43:28.010 align:start position:0% chosen yeah yeah so I have a question will<00:43:25.290> you<00:43:25.380> be<00:43:25.560> using<00:43:25.680> some<00:43:26.520> kyc<00:43:27.150> system<00:43:27.570> for 00:43:28.010 --> 00:43:28.020 align:start position:0% will you be using some kyc system for 00:43:28.020 --> 00:43:36.290 align:start position:0% will you be using some kyc system for the<00:43:28.110> workers<00:43:32.870> okay<00:43:33.870> it<00:43:34.680> depends<00:43:35.400> because<00:43:35.520> if 00:43:36.290 --> 00:43:36.300 align:start position:0% the workers okay it depends because if 00:43:36.300 --> 00:43:39.350 align:start position:0% the workers okay it depends because if you<00:43:36.540> won't<00:43:36.840> the<00:43:37.350> stake<00:43:37.590> limit<00:43:38.000> does<00:43:39.000> nothing 00:43:39.350 --> 00:43:39.360 align:start position:0% you won't the stake limit does nothing 00:43:39.360 --> 00:43:42.940 align:start position:0% you won't the stake limit does nothing it's<00:43:40.050> it's<00:43:40.410> not<00:43:40.650> the<00:43:41.450> steak<00:43:42.450> limit<00:43:42.720> you<00:43:42.810> know 00:43:42.940 --> 00:43:42.950 align:start position:0% it's it's not the steak limit you know 00:43:42.950 --> 00:43:45.920 align:start position:0% it's it's not the steak limit you know telling<00:43:43.950> me<00:43:44.040> the<00:43:44.130> maximum<00:43:44.250> steak<00:43:44.760> so<00:43:45.150> much<00:43:45.330> my 00:43:45.920 --> 00:43:45.930 align:start position:0% telling me the maximum steak so much my 00:43:45.930 --> 00:43:49.820 align:start position:0% telling me the maximum steak so much my chance<00:43:46.290> of<00:43:46.560> each<00:43:46.890> worker<00:43:47.160> can<00:43:48.030> be<00:43:48.180> get<00:43:48.830> like 00:43:49.820 --> 00:43:49.830 align:start position:0% chance of each worker can be get like 00:43:49.830 --> 00:43:52.340 align:start position:0% chance of each worker can be get like bypassed<00:43:50.760> by<00:43:51.120> just<00:43:51.660> registering<00:43:52.110> with 00:43:52.340 --> 00:43:52.350 align:start position:0% bypassed by just registering with 00:43:52.350 --> 00:43:55.220 align:start position:0% bypassed by just registering with multiple<00:43:53.010> addresses<00:43:53.900> inside<00:43:54.900> the<00:43:55.020> steak 00:43:55.220 --> 00:43:55.230 align:start position:0% multiple addresses inside the steak 00:43:55.230 --> 00:43:57.380 align:start position:0% multiple addresses inside the steak limit<00:43:55.530> so<00:43:56.160> it's<00:43:56.460> not<00:43:56.580> super<00:43:56.760> resistant 00:43:57.380 --> 00:43:57.390 align:start position:0% limit so it's not super resistant 00:43:57.390 --> 00:44:05.930 align:start position:0% limit so it's not super resistant without<00:43:57.660> a<00:43:57.690> kyc<00:43:58.260> system<00:43:58.650> right<00:44:04.550> it's<00:44:05.550> funny<00:44:05.730> we 00:44:05.930 --> 00:44:05.940 align:start position:0% without a kyc system right it's funny we 00:44:05.940 --> 00:44:07.490 align:start position:0% without a kyc system right it's funny we actually<00:44:06.270> explored<00:44:06.660> that<00:44:06.840> because<00:44:07.260> we<00:44:07.410> were 00:44:07.490 --> 00:44:07.500 align:start position:0% actually explored that because we were 00:44:07.500 --> 00:44:11.270 align:start position:0% actually explored that because we were considering<00:44:08.270> letting<00:44:09.270> people<00:44:09.890> have<00:44:10.890> a<00:44:10.920> lot<00:44:11.250> of 00:44:11.270 --> 00:44:11.280 align:start position:0% considering letting people have a lot of 00:44:11.280 --> 00:44:13.640 align:start position:0% considering letting people have a lot of steak<00:44:11.670> and<00:44:11.880> then<00:44:12.480> wait<00:44:12.810> the<00:44:13.260> workers 00:44:13.640 --> 00:44:13.650 align:start position:0% steak and then wait the workers 00:44:13.650 --> 00:44:14.990 align:start position:0% steak and then wait the workers proportionally<00:44:14.250> according<00:44:14.730> to<00:44:14.790> how<00:44:14.880> much 00:44:14.990 --> 00:44:15.000 align:start position:0% proportionally according to how much 00:44:15.000 --> 00:44:17.150 align:start position:0% proportionally according to how much steak<00:44:15.300> they<00:44:15.450> have<00:44:15.630> but<00:44:16.470> computationally 00:44:17.150 --> 00:44:17.160 align:start position:0% steak they have but computationally 00:44:17.160 --> 00:44:19.190 align:start position:0% steak they have but computationally that's<00:44:17.310> a<00:44:17.400> that's<00:44:17.760> not<00:44:18.120> that's<00:44:18.870> very 00:44:19.190 --> 00:44:19.200 align:start position:0% that's a that's not that's very 00:44:19.200 --> 00:44:21.320 align:start position:0% that's a that's not that's very challenging<00:44:19.650> because<00:44:19.880> basically<00:44:20.880> this<00:44:21.000> is<00:44:21.150> a 00:44:21.320 --> 00:44:21.330 align:start position:0% challenging because basically this is a 00:44:21.330 --> 00:44:24.410 align:start position:0% challenging because basically this is a one<00:44:21.630> for<00:44:22.170> all<00:44:22.260> the<00:44:22.290> operations<00:44:22.980> and 00:44:24.410 --> 00:44:24.420 align:start position:0% one for all the operations and 00:44:24.420 --> 00:44:26.900 align:start position:0% one for all the operations and best<00:44:24.630> to<00:44:24.839> Bo<00:44:25.019> n<00:44:25.349> depending<00:44:26.339> on<00:44:26.460> how<00:44:26.640> you<00:44:26.700> want 00:44:26.900 --> 00:44:26.910 align:start position:0% best to Bo n depending on how you want 00:44:26.910 --> 00:44:28.519 align:start position:0% best to Bo n depending on how you want to<00:44:26.940> balance<00:44:27.119> read<00:44:27.599> optimization<00:44:28.260> versus 00:44:28.519 --> 00:44:28.529 align:start position:0% to balance read optimization versus 00:44:28.529 --> 00:44:30.700 align:start position:0% to balance read optimization versus write<00:44:28.680> optimization<00:44:29.339> so<00:44:29.579> we<00:44:30.210> decided<00:44:30.660> that 00:44:30.700 --> 00:44:30.710 align:start position:0% write optimization so we decided that 00:44:30.710 --> 00:44:33.559 align:start position:0% write optimization so we decided that kyc<00:44:31.710> be<00:44:31.859> damned<00:44:32.069> I<00:44:32.279> guess<00:44:32.490> we<00:44:32.760> just<00:44:32.789> let<00:44:33.390> them 00:44:33.559 --> 00:44:33.569 align:start position:0% kyc be damned I guess we just let them 00:44:33.569 --> 00:44:36.319 align:start position:0% kyc be damned I guess we just let them if<00:44:33.779> they<00:44:33.990> have<00:44:34.289> a<00:44:34.680> million<00:44:35.430> they<00:44:35.880> can<00:44:36.089> stake 00:44:36.319 --> 00:44:36.329 align:start position:0% if they have a million they can stake 00:44:36.329 --> 00:44:38.660 align:start position:0% if they have a million they can stake that<00:44:36.510> many<00:44:36.720> addresses<00:44:36.900> so<00:44:37.769> but<00:44:38.190> it's<00:44:38.309> a<00:44:38.490> bit 00:44:38.660 --> 00:44:38.670 align:start position:0% that many addresses so but it's a bit 00:44:38.670 --> 00:44:39.799 align:start position:0% that many addresses so but it's a bit again<00:44:38.819> I<00:44:38.849> think<00:44:39.029> it's<00:44:39.210> kind<00:44:39.359> of<00:44:39.390> outside<00:44:39.690> the 00:44:39.799 --> 00:44:39.809 align:start position:0% again I think it's kind of outside the 00:44:39.809 --> 00:44:41.059 align:start position:0% again I think it's kind of outside the scope<00:44:39.990> of<00:44:40.079> this<00:44:40.200> it<00:44:40.380> depends<00:44:40.650> on<00:44:40.769> how<00:44:40.920> you<00:44:40.980> want 00:44:41.059 --> 00:44:41.069 align:start position:0% scope of this it depends on how you want 00:44:41.069 --> 00:44:42.769 align:start position:0% scope of this it depends on how you want to<00:44:41.220> use<00:44:41.279> it<00:44:41.549> but<00:44:41.970> you<00:44:42.150> you<00:44:42.359> bring<00:44:42.569> up<00:44:42.660> an 00:44:42.769 --> 00:44:42.779 align:start position:0% to use it but you you bring up an 00:44:42.779 --> 00:44:52.339 align:start position:0% to use it but you you bring up an excellent<00:44:42.839> point<00:44:43.140> I<00:44:43.440> think<00:44:43.500> I<00:44:51.019> mean<00:44:52.019> the<00:44:52.140> stake 00:44:52.339 --> 00:44:52.349 align:start position:0% excellent point I think I mean the stake 00:44:52.349 --> 00:44:54.259 align:start position:0% excellent point I think I mean the stake limit<00:44:52.650> is<00:44:53.069> the<00:44:53.339> question<00:44:53.609> was<00:44:53.730> wouldn't<00:44:54.150> it<00:44:54.210> be 00:44:54.259 --> 00:44:54.269 align:start position:0% limit is the question was wouldn't it be 00:44:54.269 --> 00:44:55.339 align:start position:0% limit is the question was wouldn't it be better<00:44:54.359> to<00:44:54.539> get<00:44:54.630> rid<00:44:54.690> of<00:44:54.839> the<00:44:54.930> stake<00:44:55.079> limit 00:44:55.339 --> 00:44:55.349 align:start position:0% better to get rid of the stake limit 00:44:55.349 --> 00:44:56.630 align:start position:0% better to get rid of the stake limit then<00:44:55.500> so<00:44:55.650> you<00:44:55.740> can<00:44:55.859> stake<00:44:56.190> as<00:44:56.279> much<00:44:56.430> as<00:44:56.549> you 00:44:56.630 --> 00:44:56.640 align:start position:0% then so you can stake as much as you 00:44:56.640 --> 00:44:58.339 align:start position:0% then so you can stake as much as you want<00:44:56.819> and<00:44:57.029> that's<00:44:57.450> still<00:44:57.750> an<00:44:57.869> open<00:44:58.049> question 00:44:58.339 --> 00:44:58.349 align:start position:0% want and that's still an open question 00:44:58.349 --> 00:44:59.599 align:start position:0% want and that's still an open question that<00:44:58.650> we've<00:44:58.740> been<00:44:58.859> talking<00:44:59.130> about<00:44:59.190> because 00:44:59.599 --> 00:44:59.609 align:start position:0% that we've been talking about because 00:44:59.609 --> 00:45:02.000 align:start position:0% that we've been talking about because really<00:45:00.329> if<00:45:00.660> you<00:45:00.839> can<00:45:01.019> just<00:45:01.200> only<00:45:01.380> do<00:45:01.619> one<00:45:01.799> job 00:45:02.000 --> 00:45:02.010 align:start position:0% really if you can just only do one job 00:45:02.010 --> 00:45:04.160 align:start position:0% really if you can just only do one job at<00:45:02.190> a<00:45:02.220> time<00:45:02.309> then<00:45:02.880> really<00:45:03.210> you<00:45:03.450> only<00:45:03.510> need<00:45:03.809> like 00:45:04.160 --> 00:45:04.170 align:start position:0% at a time then really you only need like 00:45:04.170 --> 00:45:04.940 align:start position:0% at a time then really you only need like the<00:45:04.319> job<00:45:04.500> stake 00:45:04.940 --> 00:45:04.950 align:start position:0% the job stake 00:45:04.950 --> 00:45:07.460 align:start position:0% the job stake amount<00:45:05.250> minimum<00:45:05.900> yeah<00:45:06.900> and<00:45:07.140> I<00:45:07.200> think<00:45:07.349> it's 00:45:07.460 --> 00:45:07.470 align:start position:0% amount minimum yeah and I think it's 00:45:07.470 --> 00:45:08.839 align:start position:0% amount minimum yeah and I think it's something<00:45:07.619> to<00:45:07.980> keep<00:45:08.069> in<00:45:08.220> mind<00:45:08.339> in<00:45:08.549> general 00:45:08.839 --> 00:45:08.849 align:start position:0% something to keep in mind in general 00:45:08.849 --> 00:45:09.680 align:start position:0% something to keep in mind in general when<00:45:08.970> you're<00:45:09.059> doing<00:45:09.240> these<00:45:09.359> sorts<00:45:09.569> of<00:45:09.630> things 00:45:09.680 --> 00:45:09.690 align:start position:0% when you're doing these sorts of things 00:45:09.690 --> 00:45:11.180 align:start position:0% when you're doing these sorts of things is<00:45:10.140> to<00:45:10.170> keep<00:45:10.410> in<00:45:10.589> mind<00:45:10.740> because<00:45:10.950> that's 00:45:11.180 --> 00:45:11.190 align:start position:0% is to keep in mind because that's 00:45:11.190 --> 00:45:13.069 align:start position:0% is to keep in mind because that's definitely<00:45:11.670> an<00:45:12.059> issue<00:45:12.240> like<00:45:12.510> wooden<00:45:12.869> people 00:45:13.069 --> 00:45:13.079 align:start position:0% definitely an issue like wooden people 00:45:13.079 --> 00:45:15.109 align:start position:0% definitely an issue like wooden people can<00:45:13.380> be<00:45:13.559> mole<00:45:13.799> when<00:45:14.369> many<00:45:14.640> people<00:45:15.029> could 00:45:15.109 --> 00:45:15.119 align:start position:0% can be mole when many people could 00:45:15.119 --> 00:45:17.299 align:start position:0% can be mole when many people could actually<00:45:15.269> be<00:45:15.450> one<00:45:15.660> actor<00:45:16.069> and<00:45:17.069> this<00:45:17.160> is<00:45:17.279> a 00:45:17.299 --> 00:45:17.309 align:start position:0% actually be one actor and this is a 00:45:17.309 --> 00:45:20.059 align:start position:0% actually be one actor and this is a pattern<00:45:17.519> we<00:45:17.789> do<00:45:17.910> see<00:45:18.059> a<00:45:18.089> lot<00:45:18.240> is<00:45:18.539> people<00:45:19.069> just 00:45:20.059 --> 00:45:20.069 align:start position:0% pattern we do see a lot is people just 00:45:20.069 --> 00:45:21.829 align:start position:0% pattern we do see a lot is people just trusting<00:45:20.519> no<00:45:20.700> no<00:45:20.819> one<00:45:21.119> address<00:45:21.450> means<00:45:21.630> one 00:45:21.829 --> 00:45:21.839 align:start position:0% trusting no no one address means one 00:45:21.839 --> 00:45:24.049 align:start position:0% trusting no no one address means one person<00:45:22.200> but<00:45:22.380> like<00:45:22.740> you<00:45:22.829> said<00:45:23.220> if<00:45:23.400> if<00:45:23.700> you<00:45:23.880> have 00:45:24.049 --> 00:45:24.059 align:start position:0% person but like you said if if you have 00:45:24.059 --> 00:45:25.910 align:start position:0% person but like you said if if you have a<00:45:24.089> million<00:45:24.329> addresses<00:45:24.539> and<00:45:25.019> there's<00:45:25.619> only<00:45:25.740> two 00:45:25.910 --> 00:45:25.920 align:start position:0% a million addresses and there's only two 00:45:25.920 --> 00:45:27.710 align:start position:0% a million addresses and there's only two other<00:45:25.980> workers<00:45:26.369> you<00:45:26.490> have<00:45:26.609> a<00:45:26.700> 1<00:45:27.180> million<00:45:27.450> out 00:45:27.710 --> 00:45:27.720 align:start position:0% other workers you have a 1 million out 00:45:27.720 --> 00:45:29.240 align:start position:0% other workers you have a 1 million out of<00:45:27.750> a<00:45:27.900> million<00:45:28.170> a<00:45:28.260> 2<00:45:28.410> chance<00:45:28.710> of<00:45:28.890> being<00:45:29.039> picked 00:45:29.240 --> 00:45:29.250 align:start position:0% of a million a 2 chance of being picked 00:45:29.250 --> 00:45:37.759 align:start position:0% of a million a 2 chance of being picked for<00:45:29.369> this<00:45:29.579> things<00:45:34.549> alright<00:45:35.549> should<00:45:36.359> we<00:45:36.650> so<00:45:37.650> we 00:45:37.759 --> 00:45:37.769 align:start position:0% for this things alright should we so we 00:45:37.769 --> 00:45:41.839 align:start position:0% for this things alright should we so we got<00:45:37.980> one<00:45:38.940> tiny<00:45:39.799> submission<00:45:40.799> the<00:45:41.279> wicked<00:45:41.640> we 00:45:41.839 --> 00:45:41.849 align:start position:0% got one tiny submission the wicked we 00:45:41.849 --> 00:45:44.180 align:start position:0% got one tiny submission the wicked we could<00:45:42.000> take<00:45:42.150> a<00:45:42.180> look<00:45:42.359> at<00:45:42.480> that<00:45:42.829> we<00:45:43.829> have<00:45:43.950> like 00:45:44.180 --> 00:45:44.190 align:start position:0% could take a look at that we have like 00:45:44.190 --> 00:45:45.470 align:start position:0% could take a look at that we have like 10<00:45:44.490> minutes<00:45:44.519> left 00:45:45.470 --> 00:45:45.480 align:start position:0% 10 minutes left 00:45:45.480 --> 00:45:50.089 align:start position:0% 10 minutes left alternatively<00:45:46.470> we<00:45:46.619> could<00:45:46.769> just<00:45:48.950> talk<00:45:49.950> about 00:45:50.089 --> 00:45:50.099 align:start position:0% alternatively we could just talk about 00:45:50.099 --> 00:46:03.920 align:start position:0% alternatively we could just talk about our<00:45:50.250> favorite<00:45:50.940> piece<00:45:52.789> thanks<00:45:53.789> guys<00:46:02.000> yeah<00:46:03.000> this 00:46:03.920 --> 00:46:03.930 align:start position:0% our favorite piece thanks guys yeah this 00:46:03.930 --> 00:46:06.589 align:start position:0% our favorite piece thanks guys yeah this is<00:46:04.259> pretty<00:46:05.220> small<00:46:05.460> pretty<00:46:05.880> straightforward 00:46:06.589 --> 00:46:06.599 align:start position:0% is pretty small pretty straightforward 00:46:06.599 --> 00:46:09.200 align:start position:0% is pretty small pretty straightforward and<00:46:06.839> I<00:46:07.319> wanted<00:46:08.190> to<00:46:08.250> kind<00:46:08.490> of<00:46:08.670> kick<00:46:08.940> off<00:46:09.059> the 00:46:09.200 --> 00:46:09.210 align:start position:0% and I wanted to kind of kick off the 00:46:09.210 --> 00:46:11.390 align:start position:0% and I wanted to kind of kick off the discussion<00:46:09.329> I<00:46:09.900> mean<00:46:10.140> I<00:46:10.319> think<00:46:10.799> all<00:46:11.130> of<00:46:11.160> you 00:46:11.390 --> 00:46:11.400 align:start position:0% discussion I mean I think all of you 00:46:11.400 --> 00:46:14.480 align:start position:0% discussion I mean I think all of you will<00:46:11.609> immediately<00:46:11.880> see<00:46:12.150> what<00:46:12.539> I'm<00:46:12.720> getting<00:46:13.019> it 00:46:14.480 --> 00:46:14.490 align:start position:0% will immediately see what I'm getting it 00:46:14.490 --> 00:46:17.499 align:start position:0% will immediately see what I'm getting it [Music] 00:46:17.499 --> 00:46:17.509 align:start position:0% [Music] 00:46:17.509 --> 00:46:24.589 align:start position:0% [Music] 9:21<00:46:19.789> so<00:46:21.650> I<00:46:22.650> I<00:46:23.519> mean<00:46:23.789> given<00:46:24.059> that<00:46:24.210> there<00:46:24.390> was 00:46:24.589 --> 00:46:24.599 align:start position:0% 9:21 so I I mean given that there was 00:46:24.599 --> 00:46:27.230 align:start position:0% 9:21 so I I mean given that there was some<00:46:25.019> changes<00:46:25.559> in<00:46:25.710> the<00:46:26.250> new<00:46:26.519> open<00:46:26.910> Zeppelin 00:46:27.230 --> 00:46:27.240 align:start position:0% some changes in the new open Zeppelin 00:46:27.240 --> 00:46:29.539 align:start position:0% some changes in the new open Zeppelin version<00:46:27.539> 2<00:46:27.720> and<00:46:27.750> so<00:46:28.140> on<00:46:28.170> in<00:46:28.349> this<00:46:28.500> direction<00:46:29.369> I 00:46:29.539 --> 00:46:29.549 align:start position:0% version 2 and so on in this direction I 00:46:29.549 --> 00:46:31.900 align:start position:0% version 2 and so on in this direction I wanted<00:46:30.420> to<00:46:30.539> kind<00:46:30.779> of<00:46:30.900> kick<00:46:31.319> off<00:46:31.470> the 00:46:31.900 --> 00:46:31.910 align:start position:0% wanted to kind of kick off the 00:46:31.910 --> 00:46:35.170 align:start position:0% wanted to kind of kick off the discussion<00:46:32.910> towards<00:46:33.450> reentrant<00:46:34.319> see 00:46:35.170 --> 00:46:35.180 align:start position:0% discussion towards reentrant see 00:46:35.180 --> 00:46:37.329 align:start position:0% discussion towards reentrant see protections<00:46:35.599> and<00:46:35.750> so<00:46:35.900> on<00:46:36.020> and<00:46:36.200> what<00:46:36.950> all<00:46:37.160> you 00:46:37.329 --> 00:46:37.339 align:start position:0% protections and so on and what all you 00:46:37.339 --> 00:46:39.609 align:start position:0% protections and so on and what all you guys<00:46:37.400> think<00:46:38.300> about<00:46:38.359> that<00:46:38.540> given<00:46:39.380> that<00:46:39.500> you 00:46:39.609 --> 00:46:39.619 align:start position:0% guys think about that given that you 00:46:39.619 --> 00:46:41.079 align:start position:0% guys think about that given that you were<00:46:39.650> also<00:46:40.069> partially<00:46:40.490> in<00:46:40.550> Worcester<00:46:40.910> State 00:46:41.079 --> 00:46:41.089 align:start position:0% were also partially in Worcester State 00:46:41.089 --> 00:46:43.599 align:start position:0% were also partially in Worcester State and<00:46:41.300> so<00:46:41.420> on<00:46:41.540> yeah<00:46:42.079> so<00:46:42.710> I<00:46:42.740> think<00:46:42.859> the<00:46:43.309> first 00:46:43.599 --> 00:46:43.609 align:start position:0% and so on yeah so I think the first 00:46:43.609 --> 00:46:46.030 align:start position:0% and so on yeah so I think the first thing<00:46:43.700> is<00:46:44.030> that<00:46:44.059> this<00:46:44.569> contract<00:46:45.230> is<00:46:45.530> you<00:46:45.920> know 00:46:46.030 --> 00:46:46.040 align:start position:0% thing is that this contract is you know 00:46:46.040 --> 00:46:49.059 align:start position:0% thing is that this contract is you know like<00:46:46.369> just<00:46:47.329> generally<00:46:47.869> stop<00:46:48.500> doing<00:46:48.770> this 00:46:49.059 --> 00:46:49.069 align:start position:0% like just generally stop doing this 00:46:49.069 --> 00:46:50.559 align:start position:0% like just generally stop doing this you<00:46:49.160> know<00:46:49.250> don't<00:46:49.730> check<00:46:50.059> if<00:46:50.240> things<00:46:50.450> are 00:46:50.559 --> 00:46:50.569 align:start position:0% you know don't check if things are 00:46:50.569 --> 00:46:52.630 align:start position:0% you know don't check if things are contracts<00:46:51.079> there<00:46:51.349> is<00:46:51.440> no<00:46:51.589> way<00:46:51.770> to<00:46:51.800> there's<00:46:52.490> no 00:46:52.630 --> 00:46:52.640 align:start position:0% contracts there is no way to there's no 00:46:52.640 --> 00:46:54.309 align:start position:0% contracts there is no way to there's no way<00:46:52.760> to<00:46:52.819> do<00:46:53.000> this<00:46:53.180> on<00:46:53.540> a<00:46:53.599> theorem<00:46:54.050> that's 00:46:54.309 --> 00:46:54.319 align:start position:0% way to do this on a theorem that's 00:46:54.319 --> 00:46:56.040 align:start position:0% way to do this on a theorem that's foolproof 00:46:56.040 --> 00:46:56.050 align:start position:0% foolproof 00:46:56.050 --> 00:47:01.690 align:start position:0% foolproof there<00:46:57.050> is<00:46:57.730> no<00:46:58.730> no<00:46:59.150> no<00:46:59.440> well<00:47:00.440> actually<00:47:00.770> you<00:47:01.520> can 00:47:01.690 --> 00:47:01.700 align:start position:0% there is no no no well actually you can 00:47:01.700 --> 00:47:03.250 align:start position:0% there is no no no well actually you can prove<00:47:01.880> that<00:47:02.059> it's<00:47:02.240> not<00:47:02.329> a<00:47:02.540> contract<00:47:03.109> by 00:47:03.250 --> 00:47:03.260 align:start position:0% prove that it's not a contract by 00:47:03.260 --> 00:47:04.569 align:start position:0% prove that it's not a contract by checking<00:47:03.530> that<00:47:03.650> the<00:47:03.859> message<00:47:04.160> that<00:47:04.190> sounder 00:47:04.569 --> 00:47:04.579 align:start position:0% checking that the message that sounder 00:47:04.579 --> 00:47:08.260 align:start position:0% checking that the message that sounder equals<00:47:04.880> origin<00:47:05.690> sure<00:47:06.380> but<00:47:06.710> you<00:47:07.460> cannot<00:47:07.910> prove 00:47:08.260 --> 00:47:08.270 align:start position:0% equals origin sure but you cannot prove 00:47:08.270 --> 00:47:10.870 align:start position:0% equals origin sure but you cannot prove that<00:47:08.630> it<00:47:08.900> is<00:47:09.710> a<00:47:09.770> contract<00:47:10.460> it's<00:47:10.550> like<00:47:10.730> when<00:47:10.819> the 00:47:10.870 --> 00:47:10.880 align:start position:0% that it is a contract it's like when the 00:47:10.880 --> 00:47:12.280 align:start position:0% that it is a contract it's like when the big<00:47:11.000> issues<00:47:11.240> is<00:47:11.270> current<00:47:11.660> factual<00:47:12.050> I<00:47:12.140> can 00:47:12.280 --> 00:47:12.290 align:start position:0% big issues is current factual I can 00:47:12.290 --> 00:47:14.230 align:start position:0% big issues is current factual I can compute<00:47:12.770> the<00:47:12.950> address<00:47:13.069> a<00:47:13.280> contract<00:47:13.760> will<00:47:14.000> live 00:47:14.230 --> 00:47:14.240 align:start position:0% compute the address a contract will live 00:47:14.240 --> 00:47:16.720 align:start position:0% compute the address a contract will live at<00:47:14.420> and<00:47:14.690> now<00:47:15.589> I<00:47:15.619> can<00:47:15.829> use<00:47:15.859> that<00:47:16.040> but<00:47:16.550> in<00:47:16.640> the 00:47:16.720 --> 00:47:16.730 align:start position:0% at and now I can use that but in the 00:47:16.730 --> 00:47:21.250 align:start position:0% at and now I can use that but in the future<00:47:16.940> becomes<00:47:17.420> a<00:47:17.540> contract<00:47:17.960> so<00:47:19.960> write<00:47:20.960> a<00:47:20.990> 50 00:47:21.250 --> 00:47:21.260 align:start position:0% future becomes a contract so write a 50 00:47:21.260 --> 00:47:24.520 align:start position:0% future becomes a contract so write a 50 X<00:47:21.349> origins<00:47:21.770> equal<00:47:22.069> yes<00:47:22.309> and<00:47:23.089> but<00:47:24.050> I<00:47:24.109> think<00:47:24.410> in 00:47:24.520 --> 00:47:24.530 align:start position:0% X origins equal yes and but I think in 00:47:24.530 --> 00:47:26.620 align:start position:0% X origins equal yes and but I think in general<00:47:24.740> it's<00:47:25.190> it's<00:47:25.609> I<00:47:25.940> think<00:47:26.210> it's<00:47:26.540> an 00:47:26.620 --> 00:47:26.630 align:start position:0% general it's it's I think it's an 00:47:26.630 --> 00:47:28.210 align:start position:0% general it's it's I think it's an anti-pattern<00:47:26.960> because<00:47:27.470> we<00:47:27.589> want<00:47:27.800> to<00:47:27.829> build<00:47:28.010> a 00:47:28.210 --> 00:47:28.220 align:start position:0% anti-pattern because we want to build a 00:47:28.220 --> 00:47:30.220 align:start position:0% anti-pattern because we want to build a system<00:47:28.369> that<00:47:28.730> is<00:47:28.819> interoperable<00:47:29.119> and<00:47:29.750> if<00:47:30.140> you 00:47:30.220 --> 00:47:30.230 align:start position:0% system that is interoperable and if you 00:47:30.230 --> 00:47:31.960 align:start position:0% system that is interoperable and if you can't<00:47:30.440> build<00:47:30.650> a<00:47:30.770> secure<00:47:31.069> contract<00:47:31.609> unless 00:47:31.960 --> 00:47:31.970 align:start position:0% can't build a secure contract unless 00:47:31.970 --> 00:47:33.490 align:start position:0% can't build a secure contract unless it's<00:47:32.240> being<00:47:32.420> called<00:47:32.660> by<00:47:32.809> an<00:47:32.869> externally<00:47:33.290> under 00:47:33.490 --> 00:47:33.500 align:start position:0% it's being called by an externally under 00:47:33.500 --> 00:47:34.839 align:start position:0% it's being called by an externally under count<00:47:33.710> then<00:47:33.950> you<00:47:33.980> need<00:47:34.250> to<00:47:34.400> rework<00:47:34.790> your 00:47:34.839 --> 00:47:34.849 align:start position:0% count then you need to rework your 00:47:34.849 --> 00:47:40.299 align:start position:0% count then you need to rework your contract<00:47:35.420> so<00:47:35.660> it<00:47:35.720> is<00:47:36.790> right<00:47:37.790> and<00:47:38.440> this<00:47:39.440> was<00:47:40.099> for 00:47:40.299 --> 00:47:40.309 align:start position:0% contract so it is right and this was for 00:47:40.309 --> 00:47:43.390 align:start position:0% contract so it is right and this was for the<00:47:40.369> mechanics<00:47:41.059> of<00:47:41.270> this<00:47:41.950> Nick<00:47:42.950> you<00:47:43.220> wanna 00:47:43.390 --> 00:47:43.400 align:start position:0% the mechanics of this Nick you wanna 00:47:43.400 --> 00:47:47.170 align:start position:0% the mechanics of this Nick you wanna yeah<00:47:43.970> so<00:47:44.420> if<00:47:45.049> you<00:47:45.290> call<00:47:45.440> self-destruct<00:47:46.309> the 00:47:47.170 --> 00:47:47.180 align:start position:0% yeah so if you call self-destruct the 00:47:47.180 --> 00:47:50.319 align:start position:0% yeah so if you call self-destruct the contracts<00:47:47.780> code<00:47:48.339> size<00:47:49.339> will<00:47:49.670> be<00:47:49.790> 0<00:47:50.030> even 00:47:50.319 --> 00:47:50.329 align:start position:0% contracts code size will be 0 even 00:47:50.329 --> 00:47:52.089 align:start position:0% contracts code size will be 0 even though<00:47:50.930> the<00:47:51.079> contracts<00:47:51.500> are<00:47:51.589> still<00:47:51.770> call<00:47:51.980> of 00:47:52.089 --> 00:47:52.099 align:start position:0% though the contracts are still call of 00:47:52.099 --> 00:47:53.470 align:start position:0% though the contracts are still call of all<00:47:52.190> for<00:47:52.369> the<00:47:52.430> rest<00:47:52.579> of<00:47:52.670> the<00:47:52.760> transaction<00:47:53.299> so 00:47:53.470 --> 00:47:53.480 align:start position:0% all for the rest of the transaction so 00:47:53.480 --> 00:47:55.450 align:start position:0% all for the rest of the transaction so you<00:47:53.960> could<00:47:54.230> exploit<00:47:54.559> this<00:47:54.770> by<00:47:55.040> having<00:47:55.369> your 00:47:55.450 --> 00:47:55.460 align:start position:0% you could exploit this by having your 00:47:55.460 --> 00:47:57.309 align:start position:0% you could exploit this by having your contract<00:47:55.910> self-destruct<00:47:56.510> itself<00:47:56.900> and<00:47:57.140> then 00:47:57.309 --> 00:47:57.319 align:start position:0% contract self-destruct itself and then 00:47:57.319 --> 00:47:59.740 align:start position:0% contract self-destruct itself and then called<00:47:57.589> us<00:47:57.799> and<00:47:58.099> then<00:47:58.250> do<00:47:58.819> a<00:47:58.849> entrance<00:47:59.359> e<00:47:59.510> and 00:47:59.740 --> 00:47:59.750 align:start position:0% called us and then do a entrance e and 00:47:59.750 --> 00:48:03.370 align:start position:0% called us and then do a entrance e and then<00:47:59.900> die<00:48:00.049> afterwards<00:48:01.000> no<00:48:02.000> no<00:48:02.299> no<00:48:02.510> no<00:48:02.690> no<00:48:03.079> the<00:48:03.260> X 00:48:03.370 --> 00:48:03.380 align:start position:0% then die afterwards no no no no no the X 00:48:03.380 --> 00:48:06.370 align:start position:0% then die afterwards no no no no no the X code<00:48:03.619> size<00:48:03.890> will<00:48:04.819> not<00:48:04.970> be<00:48:05.119> 0<00:48:05.329> and<00:48:05.809> I<00:48:05.930> get<00:48:06.079> back 00:48:06.370 --> 00:48:06.380 align:start position:0% code size will not be 0 and I get back 00:48:06.380 --> 00:48:10.329 align:start position:0% code size will not be 0 and I get back to<00:48:06.589> the<00:48:06.710> end<00:48:06.829> of<00:48:06.980> the<00:48:07.099> yeah<00:48:08.290> the<00:48:09.290> X<00:48:09.859> code<00:48:10.130> size 00:48:10.329 --> 00:48:10.339 align:start position:0% to the end of the yeah the X code size 00:48:10.339 --> 00:48:12.430 align:start position:0% to the end of the yeah the X code size would<00:48:10.549> still<00:48:10.849> be<00:48:11.150> the<00:48:11.540> actual<00:48:12.079> code<00:48:12.230> size 00:48:12.430 --> 00:48:12.440 align:start position:0% would still be the actual code size 00:48:12.440 --> 00:48:15.400 align:start position:0% would still be the actual code size until<00:48:12.799> after<00:48:13.099> they<00:48:13.220> but<00:48:13.869> the<00:48:14.869> constructor 00:48:15.400 --> 00:48:15.410 align:start position:0% until after they but the constructor 00:48:15.410 --> 00:48:17.500 align:start position:0% until after they but the constructor that's<00:48:15.950> it<00:48:16.099> yeah<00:48:16.220> because<00:48:16.790> they<00:48:17.059> construct 00:48:17.500 --> 00:48:17.510 align:start position:0% that's it yeah because they construct 00:48:17.510 --> 00:48:19.990 align:start position:0% that's it yeah because they construct during<00:48:17.839> the<00:48:17.930> constructor<00:48:18.460> right<00:48:19.460> then<00:48:19.760> the 00:48:19.990 --> 00:48:20.000 align:start position:0% during the constructor right then the 00:48:20.000 --> 00:48:22.240 align:start position:0% during the constructor right then the exercise<00:48:20.329> of<00:48:20.839> that<00:48:21.049> address<00:48:21.410> will<00:48:21.589> be<00:48:21.619> 0<00:48:21.980> and<00:48:22.099> I 00:48:22.240 --> 00:48:22.250 align:start position:0% exercise of that address will be 0 and I 00:48:22.250 --> 00:48:24.190 align:start position:0% exercise of that address will be 0 and I would<00:48:22.520> still<00:48:22.819> not<00:48:23.059> I<00:48:23.299> don't<00:48:23.510> know<00:48:23.569> the<00:48:23.750> TX 00:48:24.190 --> 00:48:24.200 align:start position:0% would still not I don't know the TX 00:48:24.200 --> 00:48:25.930 align:start position:0% would still not I don't know the TX Orion<00:48:24.710> thing<00:48:24.859> doesn't<00:48:25.190> make<00:48:25.339> it's<00:48:25.730> not<00:48:25.910> a 00:48:25.930 --> 00:48:25.940 align:start position:0% Orion thing doesn't make it's not a 00:48:25.940 --> 00:48:27.579 align:start position:0% Orion thing doesn't make it's not a comfortable<00:48:26.210> essential<00:48:26.900> for<00:48:27.049> me<00:48:27.140> long<00:48:27.319> term 00:48:27.579 --> 00:48:27.589 align:start position:0% comfortable essential for me long term 00:48:27.589 --> 00:48:29.829 align:start position:0% comfortable essential for me long term because<00:48:28.010> like<00:48:28.160> for<00:48:28.369> example<00:48:28.460> what<00:48:28.880> if<00:48:29.000> we<00:48:29.690> have 00:48:29.829 --> 00:48:29.839 align:start position:0% because like for example what if we have 00:48:29.839 --> 00:48:32.380 align:start position:0% because like for example what if we have to<00:48:29.990> text<00:48:30.410> abstraction<00:48:31.220> in<00:48:31.339> the<00:48:31.430> future<00:48:31.700> right 00:48:32.380 --> 00:48:32.390 align:start position:0% to text abstraction in the future right 00:48:32.390 --> 00:48:33.970 align:start position:0% to text abstraction in the future right like<00:48:32.599> the<00:48:32.839> you<00:48:33.140> know<00:48:33.230> things<00:48:33.440> coming<00:48:33.710> from<00:48:33.829> the 00:48:33.970 --> 00:48:33.980 align:start position:0% like the you know things coming from the 00:48:33.980 --> 00:48:35.319 align:start position:0% like the you know things coming from the unsigned<00:48:34.369> address<00:48:34.730> that<00:48:34.910> there<00:48:35.180> may<00:48:35.299> be 00:48:35.319 --> 00:48:35.329 align:start position:0% unsigned address that there may be 00:48:35.329 --> 00:48:36.789 align:start position:0% unsigned address that there may be actually<00:48:35.750> be<00:48:35.869> code<00:48:36.140> there<00:48:36.349> because<00:48:36.619> I'm<00:48:36.710> a 00:48:36.789 --> 00:48:36.799 align:start position:0% actually be code there because I'm a 00:48:36.799 --> 00:48:37.480 align:start position:0% actually be code there because I'm a countess 00:48:37.480 --> 00:48:37.490 align:start position:0% countess 00:48:37.490 --> 00:48:38.859 align:start position:0% countess depending<00:48:37.910> on<00:48:37.940> how<00:48:38.059> its<00:48:38.180> implemented<00:48:38.510> in<00:48:38.780> the 00:48:38.859 --> 00:48:38.869 align:start position:0% depending on how its implemented in the 00:48:38.869 --> 00:48:40.510 align:start position:0% depending on how its implemented in the future<00:48:38.960> and<00:48:39.319> may<00:48:39.589> count<00:48:39.799> the<00:48:39.920> stub<00:48:40.130> us<00:48:40.280> code 00:48:40.510 --> 00:48:40.520 align:start position:0% future and may count the stub us code 00:48:40.520 --> 00:48:43.240 align:start position:0% future and may count the stub us code there<00:48:41.030> is<00:48:41.059> actually<00:48:41.450> I<00:48:41.630> think<00:48:41.869> maybe<00:48:42.500> only<00:48:43.040> one 00:48:43.240 --> 00:48:43.250 align:start position:0% there is actually I think maybe only one 00:48:43.250 --> 00:48:43.900 align:start position:0% there is actually I think maybe only one foolproof 00:48:43.900 --> 00:48:43.910 align:start position:0% foolproof 00:48:43.910 --> 00:48:45.880 align:start position:0% foolproof future-proof<00:48:44.809> way<00:48:44.990> to<00:48:45.049> do<00:48:45.230> this<00:48:45.349> which<00:48:45.859> is 00:48:45.880 --> 00:48:45.890 align:start position:0% future-proof way to do this which is 00:48:45.890 --> 00:48:48.190 align:start position:0% future-proof way to do this which is check<00:48:46.790> the<00:48:47.180> hash 00:48:48.190 --> 00:48:48.200 align:start position:0% check the hash 00:48:48.200 --> 00:48:51.160 align:start position:0% check the hash of<00:48:48.260> message<00:48:48.859> sender<00:48:49.220> against<00:48:49.940> a<00:48:50.089> signature<00:48:51.050> of 00:48:51.160 --> 00:48:51.170 align:start position:0% of message sender against a signature of 00:48:51.170 --> 00:48:53.500 align:start position:0% of message sender against a signature of message<00:48:51.800> from<00:48:52.280> that<00:48:52.339> address<00:48:52.640> right<00:48:53.030> because 00:48:53.500 --> 00:48:53.510 align:start position:0% message from that address right because 00:48:53.510 --> 00:48:55.599 align:start position:0% message from that address right because smart<00:48:53.930> contracts<00:48:54.410> obviously<00:48:55.190> anything<00:48:55.430> that 00:48:55.599 --> 00:48:55.609 align:start position:0% smart contracts obviously anything that 00:48:55.609 --> 00:48:57.040 align:start position:0% smart contracts obviously anything that is<00:48:55.880> a<00:48:55.910> public<00:48:56.300> contract<00:48:56.630> can't<00:48:56.900> have<00:48:56.990> a 00:48:57.040 --> 00:48:57.050 align:start position:0% is a public contract can't have a 00:48:57.050 --> 00:48:59.890 align:start position:0% is a public contract can't have a private<00:48:57.440> key<00:48:57.820> so<00:48:58.820> if<00:48:59.210> you<00:48:59.300> if<00:48:59.480> you<00:48:59.570> make<00:48:59.599> sure 00:48:59.890 --> 00:48:59.900 align:start position:0% private key so if you if you make sure 00:48:59.900 --> 00:49:01.750 align:start position:0% private key so if you if you make sure that<00:49:00.050> you<00:49:00.589> get<00:49:00.680> a<00:49:00.740> signature<00:49:01.130> from<00:49:01.430> whoever's 00:49:01.750 --> 00:49:01.760 align:start position:0% that you get a signature from whoever's 00:49:01.760 --> 00:49:04.030 align:start position:0% that you get a signature from whoever's calling<00:49:02.000> then<00:49:02.990> that's<00:49:03.140> that's<00:49:03.440> like<00:49:03.530> a<00:49:03.650> I 00:49:04.030 --> 00:49:04.040 align:start position:0% calling then that's that's like a I 00:49:04.040 --> 00:49:06.220 align:start position:0% calling then that's that's like a I would<00:49:04.760> assume<00:49:04.940> a<00:49:05.060> foolproof<00:49:05.270> way<00:49:05.420> probably 00:49:06.220 --> 00:49:06.230 align:start position:0% would assume a foolproof way probably 00:49:06.230 --> 00:49:08.530 align:start position:0% would assume a foolproof way probably yeah<00:49:07.190> who<00:49:07.339> knows<00:49:07.490> what<00:49:07.700> well<00:49:07.910> is<00:49:08.089> he<00:49:08.180> moon<00:49:08.359> math 00:49:08.530 --> 00:49:08.540 align:start position:0% yeah who knows what well is he moon math 00:49:08.540 --> 00:49:21.160 align:start position:0% yeah who knows what well is he moon math will<00:49:08.690> having<00:49:08.869> a<00:49:08.930> few<00:49:09.079> million<00:49:09.530> I<00:49:20.020> mean<00:49:21.020> I<00:49:21.079> think 00:49:21.160 --> 00:49:21.170 align:start position:0% will having a few million I mean I think 00:49:21.170 --> 00:49:23.050 align:start position:0% will having a few million I mean I think in<00:49:21.530> this<00:49:21.800> particular<00:49:21.950> case<00:49:22.490> it<00:49:22.700> might<00:49:22.849> not 00:49:23.050 --> 00:49:23.060 align:start position:0% in this particular case it might not 00:49:23.060 --> 00:49:24.609 align:start position:0% in this particular case it might not actually<00:49:23.089> be<00:49:23.480> exploitable<00:49:24.050> because<00:49:24.500> it 00:49:24.609 --> 00:49:24.619 align:start position:0% actually be exploitable because it 00:49:24.619 --> 00:49:26.410 align:start position:0% actually be exploitable because it didn't<00:49:24.920> realize<00:49:25.190> they<00:49:25.430> calling<00:49:25.910> the<00:49:26.089> thing<00:49:26.300> as 00:49:26.410 --> 00:49:26.420 align:start position:0% didn't realize they calling the thing as 00:49:26.420 --> 00:49:29.470 align:start position:0% didn't realize they calling the thing as asserted<00:49:26.960> wasn't<00:49:27.560> a<00:49:27.619> contract<00:49:27.950> so<00:49:28.910> if<00:49:29.240> it's 00:49:29.470 --> 00:49:29.480 align:start position:0% asserted wasn't a contract so if it's 00:49:29.480 --> 00:49:31.180 align:start position:0% asserted wasn't a contract so if it's still<00:49:29.750> in<00:49:29.869> the<00:49:29.960> constructor<00:49:30.500> it<00:49:30.650> has<00:49:30.800> no<00:49:30.950> code 00:49:31.180 --> 00:49:31.190 align:start position:0% still in the constructor it has no code 00:49:31.190 --> 00:49:37.000 align:start position:0% still in the constructor it has no code and<00:49:31.460> you<00:49:31.550> can't<00:49:31.820> call<00:49:32.119> it<00:49:32.300> back<00:49:32.540> yet<00:49:32.990> but<00:49:36.010> I 00:49:37.000 --> 00:49:37.010 align:start position:0% and you can't call it back yet but I 00:49:37.010 --> 00:49:41.000 align:start position:0% and you can't call it back yet but I didn't<00:49:37.609> touch<00:49:38.450> that<00:49:38.720> so<00:49:38.930> what<00:49:39.260> was<00:49:39.380> the<00:49:39.530> idea 00:49:41.000 --> 00:49:41.010 align:start position:0% didn't touch that so what was the idea 00:49:41.010 --> 00:49:51.550 align:start position:0% didn't touch that so what was the idea [Music] 00:49:51.550 --> 00:49:51.560 align:start position:0% 00:49:51.560 --> 00:50:00.930 align:start position:0% [Music] 00:50:00.930 --> 00:50:00.940 align:start position:0% 00:50:00.940 --> 00:50:04.089 align:start position:0% yeah<00:50:02.000> in<00:50:02.450> this<00:50:02.630> case<00:50:02.839> message<00:50:03.500> sender<00:50:03.800> has<00:50:03.920> no 00:50:04.089 --> 00:50:04.099 align:start position:0% yeah in this case message sender has no 00:50:04.099 --> 00:50:06.309 align:start position:0% yeah in this case message sender has no code<00:50:04.310> it<00:50:04.490> so<00:50:04.730> works<00:50:05.240> cuz<00:50:05.480> it's<00:50:05.660> just<00:50:05.720> a<00:50:05.990> valley 00:50:06.309 --> 00:50:06.319 align:start position:0% code it so works cuz it's just a valley 00:50:06.319 --> 00:50:08.440 align:start position:0% code it so works cuz it's just a valley transfer<00:50:06.710> yes<00:50:07.190> but<00:50:07.670> it<00:50:07.760> can't<00:50:07.970> be<00:50:08.030> exploited 00:50:08.440 --> 00:50:08.450 align:start position:0% transfer yes but it can't be exploited 00:50:08.450 --> 00:50:10.240 align:start position:0% transfer yes but it can't be exploited very<00:50:08.660> entrance<00:50:08.960> II<00:50:09.200> which<00:50:09.470> I<00:50:09.619> assume<00:50:09.920> is<00:50:10.040> what 00:50:10.240 --> 00:50:10.250 align:start position:0% very entrance II which I assume is what 00:50:10.250 --> 00:50:13.030 align:start position:0% very entrance II which I assume is what the<00:50:10.490> author<00:50:10.940> was<00:50:11.210> worried<00:50:11.480> about<00:50:12.040> question 00:50:13.030 --> 00:50:13.040 align:start position:0% the author was worried about question 00:50:13.040 --> 00:50:15.490 align:start position:0% the author was worried about question actually<00:50:13.190> can<00:50:13.730> you<00:50:13.910> set<00:50:14.359> the<00:50:14.390> unit<00:50:14.660> code<00:50:14.839> to<00:50:15.170> be 00:50:15.490 --> 00:50:15.500 align:start position:0% actually can you set the unit code to be 00:50:15.500 --> 00:50:17.559 align:start position:0% actually can you set the unit code to be empty<00:50:16.099> so<00:50:16.339> you<00:50:16.400> can<00:50:16.670> have<00:50:16.819> a<00:50:16.849> contract<00:50:17.300> with<00:50:17.359> no 00:50:17.559 --> 00:50:17.569 align:start position:0% empty so you can have a contract with no 00:50:17.569 --> 00:50:20.050 align:start position:0% empty so you can have a contract with no code<00:50:17.780> yes<00:50:18.410> you<00:50:18.740> can<00:50:18.950> you<00:50:19.369> can<00:50:19.520> just<00:50:19.550> literally 00:50:20.050 --> 00:50:20.060 align:start position:0% code yes you can you can just literally 00:50:20.060 --> 00:50:20.980 align:start position:0% code yes you can you can just literally return<00:50:20.300> zero<00:50:20.540> vibes 00:50:20.980 --> 00:50:20.990 align:start position:0% return zero vibes 00:50:20.990 --> 00:50:25.000 align:start position:0% return zero vibes great<00:50:21.290> so<00:50:22.130> that<00:50:22.310> idea<00:50:22.670> by<00:50:23.359> the<00:50:23.420> way<00:50:23.569> with<00:50:24.010> that 00:50:25.000 --> 00:50:25.010 align:start position:0% great so that idea by the way with that 00:50:25.010 --> 00:50:28.859 align:start position:0% great so that idea by the way with that depends<00:50:25.400> on<00:50:25.490> that<00:50:25.640> the<00:50:26.630> idea<00:50:26.930> that<00:50:27.170> for<00:50:28.010> a 00:50:28.859 --> 00:50:28.869 align:start position:0% depends on that the idea that for a 00:50:28.869 --> 00:50:31.780 align:start position:0% depends on that the idea that for a transaction<00:50:29.869> a<00:50:30.140> later<00:50:30.380> transaction<00:50:31.280> they 00:50:31.780 --> 00:50:31.790 align:start position:0% transaction a later transaction they 00:50:31.790 --> 00:50:34.240 align:start position:0% transaction a later transaction they cannot<00:50:32.420> have<00:50:32.930> a<00:50:33.140> zero<00:50:33.500> code<00:50:33.710> size<00:50:33.920> again 00:50:34.240 --> 00:50:34.250 align:start position:0% cannot have a zero code size again 00:50:34.250 --> 00:50:35.980 align:start position:0% cannot have a zero code size again because<00:50:34.760> the<00:50:34.880> constructor<00:50:35.270> will<00:50:35.540> not<00:50:35.660> be<00:50:35.810> run 00:50:35.980 --> 00:50:35.990 align:start position:0% because the constructor will not be run 00:50:35.990 --> 00:50:39.760 align:start position:0% because the constructor will not be run again<00:50:36.260> and<00:50:37.869> if<00:50:38.869> it's<00:50:39.140> in<00:50:39.260> a<00:50:39.319> different<00:50:39.470> block 00:50:39.760 --> 00:50:39.770 align:start position:0% again and if it's in a different block 00:50:39.770 --> 00:50:45.120 align:start position:0% again and if it's in a different block and<00:50:40.069> that<00:50:40.400> is<00:50:40.609> true<00:50:41.000> for<00:50:41.800> about<00:50:42.800> another<00:50:43.040> month 00:50:45.120 --> 00:50:45.130 align:start position:0% and that is true for about another month 00:50:45.130 --> 00:50:49.540 align:start position:0% and that is true for about another month but<00:50:46.130> then<00:50:46.310> we<00:50:46.460> have<00:50:46.579> create<00:50:46.940> two<00:50:47.800> coming<00:50:48.800> we 00:50:49.540 --> 00:50:49.550 align:start position:0% but then we have create two coming we 00:50:49.550 --> 00:50:53.410 align:start position:0% but then we have create two coming we kind<00:50:50.390> of<00:50:50.540> changes<00:50:51.079> the<00:50:51.230> semantics<00:50:52.040> and<00:50:52.420> the 00:50:53.410 --> 00:50:53.420 align:start position:0% kind of changes the semantics and the 00:50:53.420 --> 00:50:57.309 align:start position:0% kind of changes the semantics and the pattern<00:50:53.990> of<00:50:54.200> contract<00:50:54.859> creation<00:50:55.430> a<00:50:55.640> bit<00:50:56.319> so 00:50:57.309 --> 00:50:57.319 align:start position:0% pattern of contract creation a bit so 00:50:57.319 --> 00:50:59.980 align:start position:0% pattern of contract creation a bit so that<00:50:57.890> and<00:50:58.369> it<00:50:58.730> will<00:50:58.910> have<00:50:59.060> quite<00:50:59.240> an<00:50:59.420> impact<00:50:59.450> on 00:50:59.980 --> 00:50:59.990 align:start position:0% that and it will have quite an impact on 00:50:59.990 --> 00:51:01.560 align:start position:0% that and it will have quite an impact on security 00:51:01.560 --> 00:51:01.570 align:start position:0% security 00:51:01.570 --> 00:51:04.080 align:start position:0% security on<00:51:02.380> the<00:51:02.620> security<00:51:03.100> aspects<00:51:03.550> of<00:51:03.670> how<00:51:03.790> you<00:51:03.850> deal 00:51:04.080 --> 00:51:04.090 align:start position:0% on the security aspects of how you deal 00:51:04.090 --> 00:51:07.200 align:start position:0% on the security aspects of how you deal with<00:51:04.120> external<00:51:04.720> contracts<00:51:05.590> and<00:51:06.210> assumptions 00:51:07.200 --> 00:51:07.210 align:start position:0% with external contracts and assumptions 00:51:07.210 --> 00:51:10.200 align:start position:0% with external contracts and assumptions that<00:51:07.390> you<00:51:07.510> can<00:51:07.690> make<00:51:07.900> because<00:51:08.790> it<00:51:09.790> will<00:51:10.030> be 00:51:10.200 --> 00:51:10.210 align:start position:0% that you can make because it will be 00:51:10.210 --> 00:51:13.560 align:start position:0% that you can make because it will be possible<00:51:10.420> to<00:51:11.130> take<00:51:12.130> down<00:51:12.430> a<00:51:12.460> contract<00:51:12.970> and 00:51:13.560 --> 00:51:13.570 align:start position:0% possible to take down a contract and 00:51:13.570 --> 00:51:15.120 align:start position:0% possible to take down a contract and replace<00:51:14.140> it<00:51:14.350> with<00:51:14.380> something<00:51:14.830> completely 00:51:15.120 --> 00:51:15.130 align:start position:0% replace it with something completely 00:51:15.130 --> 00:51:19.290 align:start position:0% replace it with something completely different<00:51:15.580> on<00:51:16.360> the<00:51:16.990> same<00:51:17.170> address<00:51:18.300> through 00:51:19.290 --> 00:51:19.300 align:start position:0% different on the same address through 00:51:19.300 --> 00:51:23.610 align:start position:0% different on the same address through the<00:51:19.330> use<00:51:19.750> of<00:51:20.790> loading<00:51:21.790> the<00:51:22.420> actual<00:51:22.990> body<00:51:23.350> code 00:51:23.610 --> 00:51:23.620 align:start position:0% the use of loading the actual body code 00:51:23.620 --> 00:51:25.950 align:start position:0% the use of loading the actual body code from<00:51:23.980> an<00:51:24.130> Oracle<00:51:24.550> on<00:51:24.760> chain<00:51:25.150> in<00:51:25.810> the 00:51:25.950 --> 00:51:25.960 align:start position:0% from an Oracle on chain in the 00:51:25.960 --> 00:51:27.420 align:start position:0% from an Oracle on chain in the constructor<00:51:26.350> because<00:51:26.770> address<00:51:27.250> is 00:51:27.420 --> 00:51:27.430 align:start position:0% constructor because address is 00:51:27.430 --> 00:51:29.190 align:start position:0% constructor because address is determined<00:51:27.940> from<00:51:28.000> the<00:51:28.180> from<00:51:28.660> the<00:51:28.780> init<00:51:29.020> code 00:51:29.190 --> 00:51:29.200 align:start position:0% determined from the from the init code 00:51:29.200 --> 00:51:31.530 align:start position:0% determined from the from the init code and<00:51:29.740> not<00:51:29.860> from<00:51:30.040> the<00:51:30.130> actual<00:51:30.220> runtime<00:51:31.210> byte 00:51:31.530 --> 00:51:31.540 align:start position:0% and not from the actual runtime byte 00:51:31.540 --> 00:51:33.600 align:start position:0% and not from the actual runtime byte code<00:51:31.780> and<00:51:32.530> actually<00:51:32.890> I<00:51:33.070> take<00:51:33.220> back<00:51:33.430> what<00:51:33.580> I 00:51:33.600 --> 00:51:33.610 align:start position:0% code and actually I take back what I 00:51:33.610 --> 00:51:35.550 align:start position:0% code and actually I take back what I said<00:51:33.670> before<00:51:33.850> I'm<00:51:34.690> smart<00:51:34.930> contract<00:51:35.320> there's 00:51:35.550 --> 00:51:35.560 align:start position:0% said before I'm smart contract there's 00:51:35.560 --> 00:51:37.650 align:start position:0% said before I'm smart contract there's technically<00:51:36.340> and<00:51:36.520> extremely<00:51:36.910> statistically 00:51:37.650 --> 00:51:37.660 align:start position:0% technically and extremely statistically 00:51:37.660 --> 00:51:39.540 align:start position:0% technically and extremely statistically unlikely<00:51:37.780> possibility<00:51:38.230> that<00:51:38.830> you<00:51:38.950> can<00:51:39.190> create 00:51:39.540 --> 00:51:39.550 align:start position:0% unlikely possibility that you can create 00:51:39.550 --> 00:51:41.430 align:start position:0% unlikely possibility that you can create as<00:51:39.940> more<00:51:40.210> contract<00:51:40.600> address<00:51:41.020> that<00:51:41.170> you<00:51:41.290> have 00:51:41.430 --> 00:51:41.440 align:start position:0% as more contract address that you have 00:51:41.440 --> 00:51:42.870 align:start position:0% as more contract address that you have private<00:51:41.710> key<00:51:41.830> to<00:51:41.980> there's<00:51:42.280> collisions<00:51:42.700> in 00:51:42.870 --> 00:51:42.880 align:start position:0% private key to there's collisions in 00:51:42.880 --> 00:51:45.960 align:start position:0% private key to there's collisions in this<00:51:43.000> in<00:51:43.210> the<00:51:43.360> name<00:51:43.510> space<00:51:43.750> but<00:51:44.410> it's<00:51:44.970> meteos 00:51:45.960 --> 00:51:45.970 align:start position:0% this in the name space but it's meteos 00:51:45.970 --> 00:51:47.610 align:start position:0% this in the name space but it's meteos simultaneously<00:51:46.810> has<00:51:46.960> ev'ry<00:51:47.230> etherium 00:51:47.610 --> 00:51:47.620 align:start position:0% simultaneously has ev'ry etherium 00:51:47.620 --> 00:51:49.590 align:start position:0% simultaneously has ev'ry etherium practitioner<00:51:48.100> in<00:51:48.190> the<00:51:48.250> world<00:51:48.460> unlikely<00:51:49.060> yeah 00:51:49.590 --> 00:51:49.600 align:start position:0% practitioner in the world unlikely yeah 00:51:49.600 --> 00:52:08.210 align:start position:0% practitioner in the world unlikely yeah yeah<00:51:49.930> what<00:51:50.170> I<00:51:50.200> mean<00:51:50.380> you<00:51:50.620> know<00:51:50.650> possible<00:51:53.400> yes 00:52:08.210 --> 00:52:08.220 align:start position:0% 00:52:08.220 --> 00:52:10.950 align:start position:0% yeah<00:52:09.220> I<00:52:09.490> mean<00:52:09.760> it's<00:52:09.940> it's<00:52:10.120> like<00:52:10.510> getting<00:52:10.810> that 00:52:10.950 --> 00:52:10.960 align:start position:0% yeah I mean it's it's like getting that 00:52:10.960 --> 00:52:13.560 align:start position:0% yeah I mean it's it's like getting that collision<00:52:11.260> is<00:52:11.500> like<00:52:11.710> you<00:52:12.040> know<00:52:12.130> one<00:52:12.910> in<00:52:13.120> ten 00:52:13.560 --> 00:52:13.570 align:start position:0% collision is like you know one in ten 00:52:13.570 --> 00:52:17.210 align:start position:0% collision is like you know one in ten billion<00:52:13.870> universes<00:52:14.380> please<00:52:14.860> don't<00:52:15.160> do<00:52:15.310> it 00:52:17.210 --> 00:52:17.220 align:start position:0% billion universes please don't do it 00:52:17.220 --> 00:52:19.830 align:start position:0% billion universes please don't do it please<00:52:18.220> please<00:52:18.490> don't<00:52:18.730> do<00:52:18.850> it<00:52:18.970> because<00:52:19.300> it's 00:52:19.830 --> 00:52:19.840 align:start position:0% please please don't do it because it's 00:52:19.840 --> 00:52:21.990 align:start position:0% please please don't do it because it's systems<00:52:20.800> are<00:52:20.950> much<00:52:21.040> more<00:52:21.220> useful<00:52:21.610> as<00:52:21.730> they<00:52:21.850> can 00:52:21.990 --> 00:52:22.000 align:start position:0% systems are much more useful as they can 00:52:22.000 --> 00:52:23.820 align:start position:0% systems are much more useful as they can be<00:52:22.090> interacted<00:52:22.600> with<00:52:22.630> by<00:52:22.930> other<00:52:23.080> systems<00:52:23.320> than 00:52:23.820 --> 00:52:23.830 align:start position:0% be interacted with by other systems than 00:52:23.830 --> 00:52:25.260 align:start position:0% be interacted with by other systems than if<00:52:23.950> you<00:52:24.100> try<00:52:24.340> and<00:52:24.490> enforce<00:52:24.790> that<00:52:25.000> they<00:52:25.150> can 00:52:25.260 --> 00:52:25.270 align:start position:0% if you try and enforce that they can 00:52:25.270 --> 00:52:36.720 align:start position:0% if you try and enforce that they can only<00:52:25.390> interact<00:52:25.870> to<00:52:26.020> us<00:52:26.170> by<00:52:26.350> users<00:52:35.400> we<00:52:36.400> kind<00:52:36.610> of 00:52:36.720 --> 00:52:36.730 align:start position:0% only interact to us by users we kind of 00:52:36.730 --> 00:52:38.760 align:start position:0% only interact to us by users we kind of giving<00:52:37.030> up<00:52:37.150> on<00:52:37.300> security<00:52:37.780> do<00:52:37.900> you<00:52:38.440> think<00:52:38.650> the 00:52:38.760 --> 00:52:38.770 align:start position:0% giving up on security do you think the 00:52:38.770 --> 00:52:44.090 align:start position:0% giving up on security do you think the interview<00:52:39.160> happened<00:52:39.640> everything<00:52:39.910> that<00:52:40.210> we 00:52:44.090 --> 00:52:44.100 align:start position:0% 00:52:44.100 --> 00:52:47.100 align:start position:0% think<00:52:45.100> is<00:52:45.640> the<00:52:45.850> reentrant<00:52:46.270> egad<00:52:46.600> structured 00:52:47.100 --> 00:52:47.110 align:start position:0% think is the reentrant egad structured 00:52:47.110 --> 00:52:48.720 align:start position:0% think is the reentrant egad structured like<00:52:47.260> this<00:52:47.290> where<00:52:47.740> it<00:52:47.860> can<00:52:47.980> only<00:52:48.070> be<00:52:48.250> called<00:52:48.460> by 00:52:48.720 --> 00:52:48.730 align:start position:0% like this where it can only be called by 00:52:48.730 --> 00:52:56.670 align:start position:0% like this where it can only be called by external<00:52:49.330> code<00:52:52.350> yep<00:52:53.350> so<00:52:54.070> I<00:52:54.790> would<00:52:55.630> call<00:52:55.870> like<00:52:56.620> a 00:52:56.670 --> 00:52:56.680 align:start position:0% external code yep so I would call like a 00:52:56.680 --> 00:52:59.760 align:start position:0% external code yep so I would call like a mutex<00:52:57.190> like<00:52:57.610> a<00:52:57.640> last<00:52:58.480> like<00:52:59.080> a<00:52:59.110> last<00:52:59.410> resort 00:52:59.760 --> 00:52:59.770 align:start position:0% mutex like a last like a last resort 00:52:59.770 --> 00:53:01.980 align:start position:0% mutex like a last like a last resort it's<00:53:00.130> better<00:53:00.430> than<00:53:00.670> this<00:53:00.850> but<00:53:01.300> it's<00:53:01.690> still 00:53:01.980 --> 00:53:01.990 align:start position:0% it's better than this but it's still 00:53:01.990 --> 00:53:03.270 align:start position:0% it's better than this but it's still like<00:53:02.290> you<00:53:02.440> should<00:53:02.680> be<00:53:02.770> able<00:53:02.860> to<00:53:02.950> write<00:53:03.130> your 00:53:03.270 --> 00:53:03.280 align:start position:0% like you should be able to write your 00:53:03.280 --> 00:53:06.360 align:start position:0% like you should be able to write your code<00:53:03.400> without<00:53:03.580> mutexes<00:53:04.390> if<00:53:05.380> you<00:53:05.830> really<00:53:06.130> can't 00:53:06.360 --> 00:53:06.370 align:start position:0% code without mutexes if you really can't 00:53:06.370 --> 00:53:07.860 align:start position:0% code without mutexes if you really can't then<00:53:06.640> actually<00:53:07.030> mutexes<00:53:07.450> will<00:53:07.600> get<00:53:07.720> more 00:53:07.860 --> 00:53:07.870 align:start position:0% then actually mutexes will get more 00:53:07.870 --> 00:53:09.930 align:start position:0% then actually mutexes will get more efficient<00:53:08.320> in<00:53:08.530> the<00:53:08.650> next<00:53:08.980> hard<00:53:09.340> fork<00:53:09.640> because 00:53:09.930 --> 00:53:09.940 align:start position:0% efficient in the next hard fork because 00:53:09.940 --> 00:53:14.880 align:start position:0% efficient in the next hard fork because of<00:53:10.510> net<00:53:11.020> gas<00:53:11.230> majoring<00:53:11.680> yeah<00:53:13.590> yeah<00:53:14.590> but<00:53:14.800> be 00:53:14.880 --> 00:53:14.890 align:start position:0% of net gas majoring yeah yeah but be 00:53:14.890 --> 00:53:15.390 align:start position:0% of net gas majoring yeah yeah but be careful 00:53:15.390 --> 00:53:15.400 align:start position:0% careful 00:53:15.400 --> 00:53:18.210 align:start position:0% careful yeah<00:53:15.970> everyone<00:53:16.749> read<00:53:16.960> up<00:53:17.109> on<00:53:17.259> create<00:53:17.920> two 00:53:18.210 --> 00:53:18.220 align:start position:0% yeah everyone read up on create two 00:53:18.220 --> 00:53:19.440 align:start position:0% yeah everyone read up on create two because<00:53:18.640> that's<00:53:18.849> gonna<00:53:18.970> break<00:53:19.150> a<00:53:19.210> lot<00:53:19.359> of 00:53:19.440 --> 00:53:19.450 align:start position:0% because that's gonna break a lot of 00:53:19.450 --> 00:53:21.660 align:start position:0% because that's gonna break a lot of assumptions<00:53:19.690> you<00:53:19.900> guys<00:53:20.049> have<00:53:20.259> a<00:53:20.640> lot<00:53:21.640> of 00:53:21.660 --> 00:53:21.670 align:start position:0% assumptions you guys have a lot of 00:53:21.670 --> 00:53:24.870 align:start position:0% assumptions you guys have a lot of opportunities<00:53:22.630> as<00:53:22.960> well<00:53:23.289> yeah<00:53:23.829> so<00:53:24.160> they're 00:53:24.870 --> 00:53:24.880 align:start position:0% opportunities as well yeah so they're 00:53:24.880 --> 00:53:26.999 align:start position:0% opportunities as well yeah so they're like<00:53:25.150> only<00:53:25.990> a<00:53:26.170> couple<00:53:26.380> of<00:53:26.470> minutes<00:53:26.799> and<00:53:26.890> the 00:53:26.999 --> 00:53:27.009 align:start position:0% like only a couple of minutes and the 00:53:27.009 --> 00:53:31.769 align:start position:0% like only a couple of minutes and the next<00:53:27.130> team<00:53:28.049> are<00:53:29.049> back<00:53:29.380> to<00:53:29.589> back<00:53:29.940> so<00:53:30.940> we<00:53:31.059> can 00:53:31.769 --> 00:53:31.779 align:start position:0% next team are back to back so we can 00:53:31.779 --> 00:53:36.599 align:start position:0% next team are back to back so we can have<00:53:31.930> like<00:53:32.140> one<00:53:32.859> more<00:53:33.009> question<00:53:33.160> or<00:53:33.519> so<00:53:35.190> so<00:53:36.190> why 00:53:36.599 --> 00:53:36.609 align:start position:0% have like one more question or so so why 00:53:36.609 --> 00:53:39.029 align:start position:0% have like one more question or so so why wouldn't<00:53:36.940> this<00:53:37.029> contract<00:53:37.660> be<00:53:37.809> vulnerable<00:53:38.769> to 00:53:39.029 --> 00:53:39.039 align:start position:0% wouldn't this contract be vulnerable to 00:53:39.039 --> 00:53:43.829 align:start position:0% wouldn't this contract be vulnerable to reentry<00:53:39.910> couldn't<00:53:40.420> I<00:53:40.539> just<00:53:41.640> call<00:53:42.640> deposit<00:53:43.599> and 00:53:43.829 --> 00:53:43.839 align:start position:0% reentry couldn't I just call deposit and 00:53:43.839 --> 00:53:47.839 align:start position:0% reentry couldn't I just call deposit and send<00:53:44.259> in<00:53:44.589> the<00:53:44.619> constructor<00:53:45.400> of<00:53:45.549> the<00:53:45.670> contract 00:53:47.839 --> 00:53:47.849 align:start position:0% send in the constructor of the contract 00:53:47.849 --> 00:53:50.880 align:start position:0% send in the constructor of the contract yes<00:53:48.849> but<00:53:49.240> if<00:53:49.450> you<00:53:49.569> call<00:53:49.720> seemed<00:53:50.140> then<00:53:50.619> it<00:53:50.740> will 00:53:50.880 --> 00:53:50.890 align:start position:0% yes but if you call seemed then it will 00:53:50.890 --> 00:53:52.349 align:start position:0% yes but if you call seemed then it will try<00:53:51.160> and<00:53:51.279> call<00:53:51.400> you<00:53:51.430> back<00:53:51.670> and<00:53:51.940> because<00:53:52.240> it's 00:53:52.349 --> 00:53:52.359 align:start position:0% try and call you back and because it's 00:53:52.359 --> 00:53:53.549 align:start position:0% try and call you back and because it's in<00:53:52.450> the<00:53:52.539> constructor<00:53:53.049> you<00:53:53.170> don't<00:53:53.380> yet<00:53:53.529> have 00:53:53.549 --> 00:53:53.559 align:start position:0% in the constructor you don't yet have 00:53:53.559 --> 00:53:55.920 align:start position:0% in the constructor you don't yet have any<00:53:53.799> code<00:53:54.039> at<00:53:54.339> that<00:53:54.400> address<00:53:54.759> so<00:53:55.269> it<00:53:55.480> won't<00:53:55.690> be 00:53:55.920 --> 00:53:55.930 align:start position:0% any code at that address so it won't be 00:53:55.930 --> 00:53:58.140 align:start position:0% any code at that address so it won't be able<00:53:56.079> to<00:53:56.230> be<00:53:56.349> reentrant<00:53:56.829> yeah<00:53:57.460> the<00:53:57.609> code<00:53:57.819> the 00:53:58.140 --> 00:53:58.150 align:start position:0% able to be reentrant yeah the code the 00:53:58.150 --> 00:53:59.700 align:start position:0% able to be reentrant yeah the code the way<00:53:58.269> that<00:53:58.420> he<00:53:58.509> theorem<00:53:58.749> works<00:53:58.869> is<00:53:59.200> that<00:53:59.440> the 00:53:59.700 --> 00:53:59.710 align:start position:0% way that he theorem works is that the 00:53:59.710 --> 00:54:03.210 align:start position:0% way that he theorem works is that the constructor<00:54:00.450> returns<00:54:01.450> a<00:54:01.809> string<00:54:02.259> of<00:54:02.829> evm 00:54:03.210 --> 00:54:03.220 align:start position:0% constructor returns a string of evm 00:54:03.220 --> 00:54:05.069 align:start position:0% constructor returns a string of evm bytes<00:54:03.549> and<00:54:03.849> only<00:54:04.539> at<00:54:04.630> the<00:54:04.690> end<00:54:04.900> of<00:54:04.990> the 00:54:05.069 --> 00:54:05.079 align:start position:0% bytes and only at the end of the 00:54:05.079 --> 00:54:06.630 align:start position:0% bytes and only at the end of the transaction<00:54:05.470> or<00:54:05.769> those<00:54:05.980> okay<00:54:06.220> go<00:54:06.430> to<00:54:06.490> the 00:54:06.630 --> 00:54:06.640 align:start position:0% transaction or those okay go to the 00:54:06.640 --> 00:54:08.450 align:start position:0% transaction or those okay go to the contract<00:54:07.059> Thanks 00:54:08.450 --> 00:54:08.460 align:start position:0% contract Thanks 00:54:08.460 --> 00:54:13.559 align:start position:0% contract Thanks don't<00:54:09.460> have<00:54:09.549> time<00:54:09.700> for<00:54:09.759> one<00:54:09.999> more 00:54:13.559 --> 00:54:13.569 align:start position:0% 00:54:13.569 --> 00:54:18.509 align:start position:0% what's<00:54:14.259> the<00:54:14.499> best<00:54:14.799> way<00:54:15.339> to<00:54:16.740> with<00:54:17.740> transferring 00:54:18.509 --> 00:54:18.519 align:start position:0% what's the best way to with transferring 00:54:18.519 --> 00:54:22.380 align:start position:0% what's the best way to with transferring some<00:54:18.880> value<00:54:19.470> to<00:54:20.470> set<00:54:20.710> the<00:54:20.890> gas<00:54:21.099> limits<00:54:21.579> the 00:54:22.380 --> 00:54:22.390 align:start position:0% some value to set the gas limits the 00:54:22.390 --> 00:54:24.420 align:start position:0% some value to set the gas limits the easiest<00:54:22.720> way<00:54:22.930> is<00:54:22.960> to<00:54:23.230> use<00:54:23.259> dot<00:54:23.650> transfer<00:54:24.130> which 00:54:24.420 --> 00:54:24.430 align:start position:0% easiest way is to use dot transfer which 00:54:24.430 --> 00:54:29.450 align:start position:0% easiest way is to use dot transfer which saves<00:54:24.700> it<00:54:24.849> to<00:54:24.940> the<00:54:25.029> minimum<00:54:25.329> which<00:54:25.569> is<00:54:25.950> 29 00:54:29.450 --> 00:54:29.460 align:start position:0% 00:54:29.460 --> 00:54:33.120 align:start position:0% Amick<00:54:30.460> if<00:54:31.119> we<00:54:31.329> want<00:54:31.509> to<00:54:31.720> choose<00:54:32.109> the<00:54:32.499> limit<00:54:32.859> and 00:54:33.120 --> 00:54:33.130 align:start position:0% Amick if we want to choose the limit and 00:54:33.130 --> 00:54:36.450 align:start position:0% Amick if we want to choose the limit and not<00:54:33.369> have<00:54:33.670> the<00:54:33.869> 21,000<00:54:34.869> in<00:54:35.019> solidity<00:54:35.950> you<00:54:36.249> can 00:54:36.450 --> 00:54:36.460 align:start position:0% not have the 21,000 in solidity you can 00:54:36.460 --> 00:54:39.690 align:start position:0% not have the 21,000 in solidity you can do<00:54:36.640> a<00:54:37.269> function<00:54:37.960> named<00:54:38.170> gas<00:54:38.769> in<00:54:39.069> brackets<00:54:39.489> and 00:54:39.690 --> 00:54:39.700 align:start position:0% do a function named gas in brackets and 00:54:39.700 --> 00:54:41.670 align:start position:0% do a function named gas in brackets and then<00:54:39.970> second<00:54:40.569> set<00:54:40.720> of<00:54:40.749> parentheses<00:54:41.319> for<00:54:41.589> the 00:54:41.670 --> 00:54:41.680 align:start position:0% then second set of parentheses for the 00:54:41.680 --> 00:54:43.529 align:start position:0% then second set of parentheses for the function<00:54:42.099> arguments<00:54:42.579> but<00:54:42.940> the<00:54:43.029> thing<00:54:43.269> is<00:54:43.299> even 00:54:43.529 --> 00:54:43.539 align:start position:0% function arguments but the thing is even 00:54:43.539 --> 00:54:46.380 align:start position:0% function arguments but the thing is even if<00:54:43.749> you<00:54:43.869> do<00:54:44.019> if<00:54:44.380> you<00:54:44.529> provide<00:54:44.890> zero<00:54:45.269> there<00:54:46.269> is 00:54:46.380 --> 00:54:46.390 align:start position:0% if you do if you provide zero there is 00:54:46.390 --> 00:54:50.819 align:start position:0% if you do if you provide zero there is always<00:54:46.749> the<00:54:46.950> 2300<00:54:47.950> gas<00:54:48.190> the<00:54:49.349> only<00:54:50.349> sleeping 00:54:50.819 --> 00:54:50.829 align:start position:0% always the 2300 gas the only sleeping 00:54:50.829 --> 00:54:54.359 align:start position:0% always the 2300 gas the only sleeping transfer<00:54:51.640> value<00:54:52.119> yeah<00:54:52.950> you<00:54:53.950> have<00:54:54.039> to<00:54:54.130> send<00:54:54.309> at 00:54:54.359 --> 00:54:54.369 align:start position:0% transfer value yeah you have to send at 00:54:54.369 --> 00:54:58.049 align:start position:0% transfer value yeah you have to send at least<00:54:54.460> one<00:54:54.670> way<00:54:54.819> yeah<00:54:56.549> but<00:54:57.549> generally 00:54:58.049 --> 00:54:58.059 align:start position:0% least one way yeah but generally 00:54:58.059 --> 00:54:59.880 align:start position:0% least one way yeah but generally generally<00:54:58.599> it's<00:54:58.869> friendly<00:54:59.170> just<00:54:59.410> seemed<00:54:59.769> at 00:54:59.880 --> 00:54:59.890 align:start position:0% generally it's friendly just seemed at 00:54:59.890 --> 00:55:01.739 align:start position:0% generally it's friendly just seemed at least<00:55:00.099> 2300<00:55:00.789> guess<00:55:00.970> even<00:55:01.299> if<00:55:01.390> you<00:55:01.450> don't<00:55:01.599> have 00:55:01.739 --> 00:55:01.749 align:start position:0% least 2300 guess even if you don't have 00:55:01.749 --> 00:55:03.329 align:start position:0% least 2300 guess even if you don't have to<00:55:01.960> because<00:55:02.259> that<00:55:02.289> way<00:55:02.529> they<00:55:02.680> can<00:55:02.799> log<00:55:02.950> events 00:55:03.329 --> 00:55:03.339 align:start position:0% to because that way they can log events 00:55:03.339 --> 00:55:04.979 align:start position:0% to because that way they can log events which<00:55:03.549> means<00:55:03.819> you<00:55:04.269> know<00:55:04.390> otherwise<00:55:04.660> it<00:55:04.869> can 00:55:04.979 --> 00:55:04.989 align:start position:0% which means you know otherwise it can 00:55:04.989 --> 00:55:08.370 align:start position:0% which means you know otherwise it can even<00:55:05.109> no<00:55:05.259> effect<00:55:05.589> whatsoever<00:55:06.720> I<00:55:07.720> think<00:55:08.259> that's 00:55:08.370 --> 00:55:08.380 align:start position:0% even no effect whatsoever I think that's 00:55:08.380 --> 00:55:21.240 align:start position:0% even no effect whatsoever I think that's all<00:55:08.499> we<00:55:08.589> have<00:55:08.680> time<00:55:08.859> for<00:55:08.920> yes<00:55:09.869> thank<00:55:10.869> you<00:55:10.989> guys 00:55:21.240 --> 00:55:21.250 align:start position:0% 00:55:21.250 --> 00:55:23.310 align:start position:0% you