WEBVTT Kind: captions Language: en 00:00:14.519 --> 00:00:20.579 align:start position:0% my<00:00:15.519> name<00:00:15.730> is<00:00:16.000> reine<00:00:16.359> Revere<00:00:16.840> and<00:00:18.179> I'm<00:00:19.179> a<00:00:19.960> smart 00:00:20.579 --> 00:00:20.589 align:start position:0% my name is reine Revere and I'm a smart 00:00:20.589 --> 00:00:23.880 align:start position:0% my name is reine Revere and I'm a smart contract<00:00:20.769> developer<00:00:21.730> I<00:00:22.470> am<00:00:23.470> the<00:00:23.710> lead 00:00:23.880 --> 00:00:23.890 align:start position:0% contract developer I am the lead 00:00:23.890 --> 00:00:27.329 align:start position:0% contract developer I am the lead architect<00:00:24.220> at<00:00:24.730> shape-shift<00:00:25.239> prism<00:00:25.749> and<00:00:26.339> I'm 00:00:27.329 --> 00:00:27.339 align:start position:0% architect at shape-shift prism and I'm 00:00:27.339 --> 00:00:30.380 align:start position:0% architect at shape-shift prism and I'm also<00:00:27.489> the<00:00:27.729> co-founder<00:00:27.909> of<00:00:28.329> Maiden 00:00:30.380 --> 00:00:30.390 align:start position:0% also the co-founder of Maiden 00:00:30.390 --> 00:00:32.880 align:start position:0% also the co-founder of Maiden I've<00:00:31.390> been<00:00:31.779> doing<00:00:32.079> smart<00:00:32.380> contract 00:00:32.880 --> 00:00:32.890 align:start position:0% I've been doing smart contract 00:00:32.890 --> 00:00:36.390 align:start position:0% I've been doing smart contract development<00:00:33.550> for<00:00:33.880> a<00:00:33.910> couple<00:00:34.270> years<00:00:34.300> and<00:00:35.400> our 00:00:36.390 --> 00:00:36.400 align:start position:0% development for a couple years and our 00:00:36.400 --> 00:00:38.340 align:start position:0% development for a couple years and our team<00:00:36.640> has<00:00:36.850> learned<00:00:37.030> so<00:00:37.600> much<00:00:37.810> along<00:00:38.170> the<00:00:38.200> way 00:00:38.340 --> 00:00:38.350 align:start position:0% team has learned so much along the way 00:00:38.350 --> 00:00:41.670 align:start position:0% team has learned so much along the way and<00:00:39.270> it's<00:00:40.270> really<00:00:40.450> an<00:00:40.600> honor<00:00:40.690> to<00:00:40.930> be<00:00:40.960> here<00:00:41.110> and 00:00:41.670 --> 00:00:41.680 align:start position:0% and it's really an honor to be here and 00:00:41.680 --> 00:00:43.260 align:start position:0% and it's really an honor to be here and to<00:00:41.980> be<00:00:42.070> able<00:00:42.160> to<00:00:42.310> share<00:00:42.520> some<00:00:42.550> of<00:00:42.970> those 00:00:43.260 --> 00:00:43.270 align:start position:0% to be able to share some of those 00:00:43.270 --> 00:00:46.290 align:start position:0% to be able to share some of those lessons<00:00:43.660> with<00:00:44.200> you<00:00:44.550> and<00:00:45.550> it's<00:00:45.670> especially<00:00:46.210> an 00:00:46.290 --> 00:00:46.300 align:start position:0% lessons with you and it's especially an 00:00:46.300 --> 00:00:49.050 align:start position:0% lessons with you and it's especially an honor<00:00:46.510> to<00:00:47.260> be<00:00:47.410> one<00:00:47.620> of<00:00:47.770> the<00:00:47.980> few<00:00:48.340> women<00:00:48.580> up<00:00:48.880> on 00:00:49.050 --> 00:00:49.060 align:start position:0% honor to be one of the few women up on 00:00:49.060 --> 00:00:52.770 align:start position:0% honor to be one of the few women up on stage<00:00:49.330> I'm<00:00:49.870> a<00:00:50.080> trans<00:00:50.380> woman<00:00:50.530> and<00:00:51.070> I<00:00:52.000> love<00:00:52.570> this 00:00:52.770 --> 00:00:52.780 align:start position:0% stage I'm a trans woman and I love this 00:00:52.780 --> 00:00:56.250 align:start position:0% stage I'm a trans woman and I love this work<00:00:53.110> and<00:00:53.440> and<00:00:53.710> the<00:00:54.430> community<00:00:54.880> is<00:00:54.940> so<00:00:55.660> amazing 00:00:56.250 --> 00:00:56.260 align:start position:0% work and and the community is so amazing 00:00:56.260 --> 00:00:58.710 align:start position:0% work and and the community is so amazing and<00:00:56.410> so<00:00:56.500> it's<00:00:57.280> such<00:00:57.550> an<00:00:57.700> honor<00:00:57.880> to<00:00:58.030> be<00:00:58.300> able<00:00:58.390> to 00:00:58.710 --> 00:00:58.720 align:start position:0% and so it's such an honor to be able to 00:00:58.720 --> 00:01:01.080 align:start position:0% and so it's such an honor to be able to share<00:00:59.590> some<00:00:59.890> of<00:00:59.920> this<00:01:00.100> expertise<00:01:00.670> and<00:01:00.910> really 00:01:01.080 --> 00:01:01.090 align:start position:0% share some of this expertise and really 00:01:01.090 --> 00:01:03.330 align:start position:0% share some of this expertise and really dig<00:01:01.270> into<00:01:01.450> the<00:01:01.630> details<00:01:02.020> so<00:01:02.920> when<00:01:03.160> I<00:01:03.190> was 00:01:03.330 --> 00:01:03.340 align:start position:0% dig into the details so when I was 00:01:03.340 --> 00:01:05.310 align:start position:0% dig into the details so when I was thinking<00:01:03.520> about<00:01:03.790> what<00:01:04.239> I<00:01:04.449> could<00:01:04.869> possibly 00:01:05.310 --> 00:01:05.320 align:start position:0% thinking about what I could possibly 00:01:05.320 --> 00:01:09.120 align:start position:0% thinking about what I could possibly share<00:01:05.649> I<00:01:07.140> wanted<00:01:08.140> to<00:01:08.259> give<00:01:08.560> something<00:01:08.979> that 00:01:09.120 --> 00:01:09.130 align:start position:0% share I wanted to give something that 00:01:09.130 --> 00:01:11.520 align:start position:0% share I wanted to give something that was<00:01:09.280> really<00:01:09.460> practical<00:01:10.090> and<00:01:10.329> so<00:01:10.960> this<00:01:11.289> talk<00:01:11.499> is 00:01:11.520 --> 00:01:11.530 align:start position:0% was really practical and so this talk is 00:01:11.530 --> 00:01:13.590 align:start position:0% was really practical and so this talk is gonna<00:01:11.799> be<00:01:12.009> pretty<00:01:12.189> straightforward<00:01:12.600> we've 00:01:13.590 --> 00:01:13.600 align:start position:0% gonna be pretty straightforward we've 00:01:13.600 --> 00:01:16.349 align:start position:0% gonna be pretty straightforward we've got<00:01:13.890> lots<00:01:14.890> of<00:01:15.100> things<00:01:15.369> that<00:01:15.579> we<00:01:15.670> learn<00:01:15.880> doing 00:01:16.349 --> 00:01:16.359 align:start position:0% got lots of things that we learn doing 00:01:16.359 --> 00:01:18.510 align:start position:0% got lots of things that we learn doing smart<00:01:16.810> contract<00:01:17.319> development<00:01:17.920> in<00:01:18.130> the<00:01:18.369> real 00:01:18.510 --> 00:01:18.520 align:start position:0% smart contract development in the real 00:01:18.520 --> 00:01:21.770 align:start position:0% smart contract development in the real world<00:01:18.789> so<00:01:19.179> that<00:01:19.389> means<00:01:20.069> production<00:01:21.069> level 00:01:21.770 --> 00:01:21.780 align:start position:0% world so that means production level 00:01:21.780 --> 00:01:24.569 align:start position:0% world so that means production level handling<00:01:22.780> lots<00:01:23.020> of<00:01:23.319> ether<00:01:23.920> on<00:01:23.950> the<00:01:24.399> live 00:01:24.569 --> 00:01:24.579 align:start position:0% handling lots of ether on the live 00:01:24.579 --> 00:01:28.109 align:start position:0% handling lots of ether on the live Network<00:01:25.090> which<00:01:25.869> as<00:01:26.049> you<00:01:26.170> can<00:01:26.200> imagine<00:01:26.549> has<00:01:27.549> a 00:01:28.109 --> 00:01:28.119 align:start position:0% Network which as you can imagine has a 00:01:28.119 --> 00:01:30.300 align:start position:0% Network which as you can imagine has a lot<00:01:28.899> of<00:01:29.020> responsibility<00:01:29.740> that<00:01:29.770> comes<00:01:29.920> with 00:01:30.300 --> 00:01:30.310 align:start position:0% lot of responsibility that comes with 00:01:30.310 --> 00:01:30.830 align:start position:0% lot of responsibility that comes with that 00:01:30.830 --> 00:01:30.840 align:start position:0% that 00:01:30.840 --> 00:01:34.440 align:start position:0% that so<00:01:32.069> what<00:01:33.069> you<00:01:33.159> can<00:01:33.310> expect<00:01:33.639> from<00:01:33.759> this<00:01:33.969> talk<00:01:34.209> is 00:01:34.440 --> 00:01:34.450 align:start position:0% so what you can expect from this talk is 00:01:34.450 --> 00:01:37.169 align:start position:0% so what you can expect from this talk is that<00:01:34.749> I'm<00:01:35.530> going<00:01:36.039> to<00:01:36.159> go<00:01:36.310> from<00:01:36.579> low<00:01:36.789> level<00:01:37.149> to 00:01:37.169 --> 00:01:37.179 align:start position:0% that I'm going to go from low level to 00:01:37.179 --> 00:01:39.719 align:start position:0% that I'm going to go from low level to high<00:01:37.509> level<00:01:37.929> so<00:01:38.799> all<00:01:38.829> of<00:01:39.100> these<00:01:39.219> are<00:01:39.280> pretty 00:01:39.719 --> 00:01:39.729 align:start position:0% high level so all of these are pretty 00:01:39.729 --> 00:01:41.730 align:start position:0% high level so all of these are pretty practical<00:01:39.999> tips<00:01:40.600> for<00:01:41.289> all<00:01:41.380> the<00:01:41.499> smart 00:01:41.730 --> 00:01:41.740 align:start position:0% practical tips for all the smart 00:01:41.740 --> 00:01:44.969 align:start position:0% practical tips for all the smart contract<00:01:41.889> developers<00:01:42.579> in<00:01:42.759> here<00:01:42.999> and<00:01:43.979> I'm 00:01:44.969 --> 00:01:44.979 align:start position:0% contract developers in here and I'm 00:01:44.979 --> 00:01:46.499 align:start position:0% contract developers in here and I'm gonna<00:01:45.100> start<00:01:45.459> with<00:01:45.700> the<00:01:45.819> code<00:01:46.090> and<00:01:46.389> we're 00:01:46.499 --> 00:01:46.509 align:start position:0% gonna start with the code and we're 00:01:46.509 --> 00:01:48.300 align:start position:0% gonna start with the code and we're gonna<00:01:46.600> go<00:01:46.840> over<00:01:46.959> some<00:01:47.229> details<00:01:47.380> and<00:01:47.920> patterns 00:01:48.300 --> 00:01:48.310 align:start position:0% gonna go over some details and patterns 00:01:48.310 --> 00:01:49.919 align:start position:0% gonna go over some details and patterns that<00:01:48.459> I've<00:01:48.670> learned<00:01:49.029> and<00:01:49.329> our<00:01:49.420> team<00:01:49.659> has 00:01:49.919 --> 00:01:49.929 align:start position:0% that I've learned and our team has 00:01:49.929 --> 00:01:52.289 align:start position:0% that I've learned and our team has learned<00:01:50.200> from<00:01:50.499> and<00:01:50.799> then<00:01:51.249> we're<00:01:51.639> gonna<00:01:51.729> end<00:01:51.999> on 00:01:52.289 --> 00:01:52.299 align:start position:0% learned from and then we're gonna end on 00:01:52.299 --> 00:01:55.590 align:start position:0% learned from and then we're gonna end on some<00:01:53.020> higher<00:01:53.409> level<00:01:53.439> patterns<00:01:54.600> especially 00:01:55.590 --> 00:01:55.600 align:start position:0% some higher level patterns especially 00:01:55.600 --> 00:01:58.769 align:start position:0% some higher level patterns especially when<00:01:56.049> it<00:01:56.139> comes<00:01:56.380> to<00:01:56.740> being<00:01:57.429> a<00:01:57.579> lead<00:01:58.270> a<00:01:58.479> leader 00:01:58.769 --> 00:01:58.779 align:start position:0% when it comes to being a lead a leader 00:01:58.779 --> 00:02:01.769 align:start position:0% when it comes to being a lead a leader on<00:01:59.049> your<00:01:59.289> team<00:01:59.499> how<00:02:00.219> do<00:02:00.279> you<00:02:00.549> lead<00:02:00.849> as<00:02:01.090> a<00:02:01.119> smart 00:02:01.769 --> 00:02:01.779 align:start position:0% on your team how do you lead as a smart 00:02:01.779 --> 00:02:05.519 align:start position:0% on your team how do you lead as a smart contract<00:02:01.920> development<00:02:02.920> engineer<00:02:04.170> so<00:02:05.170> first 00:02:05.519 --> 00:02:05.529 align:start position:0% contract development engineer so first 00:02:05.529 --> 00:02:09.330 align:start position:0% contract development engineer so first the<00:02:05.679> low<00:02:05.829> level<00:02:06.099> patterns<00:02:07.860> central<00:02:08.860> logging 00:02:09.330 --> 00:02:09.340 align:start position:0% the low level patterns central logging 00:02:09.340 --> 00:02:12.780 align:start position:0% the low level patterns central logging is<00:02:09.520> something<00:02:10.090> that<00:02:10.330> took<00:02:11.230> me<00:02:11.290> a<00:02:11.800> little<00:02:12.400> while 00:02:12.780 --> 00:02:12.790 align:start position:0% is something that took me a little while 00:02:12.790 --> 00:02:15.390 align:start position:0% is something that took me a little while to<00:02:13.480> find<00:02:13.900> my<00:02:14.110> way<00:02:14.320> to<00:02:14.380> and<00:02:14.860> when 00:02:15.390 --> 00:02:15.400 align:start position:0% to find my way to and when 00:02:15.400 --> 00:02:17.759 align:start position:0% to find my way to and when you<00:02:15.489> design<00:02:15.939> your<00:02:16.090> smart<00:02:16.510> contracts<00:02:17.049> you<00:02:17.620> want 00:02:17.759 --> 00:02:17.769 align:start position:0% you design your smart contracts you want 00:02:17.769 --> 00:02:19.380 align:start position:0% you design your smart contracts you want to<00:02:17.860> modular<00:02:18.310> eyes<00:02:18.459> things<00:02:18.819> right<00:02:19.120> we<00:02:19.239> all<00:02:19.360> know 00:02:19.380 --> 00:02:19.390 align:start position:0% to modular eyes things right we all know 00:02:19.390 --> 00:02:22.199 align:start position:0% to modular eyes things right we all know that<00:02:19.689> as<00:02:19.810> software<00:02:20.140> developers<00:02:20.970> but<00:02:21.970> there's 00:02:22.199 --> 00:02:22.209 align:start position:0% that as software developers but there's 00:02:22.209 --> 00:02:24.300 align:start position:0% that as software developers but there's some<00:02:22.420> quirks<00:02:22.780> in<00:02:22.989> the<00:02:23.049> EVM<00:02:23.590> at<00:02:23.860> least<00:02:24.040> at<00:02:24.189> this 00:02:24.300 --> 00:02:24.310 align:start position:0% some quirks in the EVM at least at this 00:02:24.310 --> 00:02:27.270 align:start position:0% some quirks in the EVM at least at this time<00:02:24.370> that<00:02:24.939> you<00:02:25.659> may<00:02:26.530> not<00:02:26.709> think<00:02:26.890> about<00:02:27.040> ahead 00:02:27.270 --> 00:02:27.280 align:start position:0% time that you may not think about ahead 00:02:27.280 --> 00:02:30.030 align:start position:0% time that you may not think about ahead of<00:02:27.430> time<00:02:27.549> but<00:02:28.000> actually<00:02:28.150> lead<00:02:28.659> to<00:02:28.689> a<00:02:29.290> system 00:02:30.030 --> 00:02:30.040 align:start position:0% of time but actually lead to a system 00:02:30.040 --> 00:02:33.569 align:start position:0% of time but actually lead to a system that<00:02:30.069> is<00:02:30.519> more<00:02:31.360> maintainable<00:02:32.230> and<00:02:32.560> is<00:02:32.920> able<00:02:33.430> to 00:02:33.569 --> 00:02:33.579 align:start position:0% that is more maintainable and is able to 00:02:33.579 --> 00:02:36.300 align:start position:0% that is more maintainable and is able to respond<00:02:34.120> and<00:02:34.569> communicate<00:02:35.560> with<00:02:35.859> your<00:02:36.010> server 00:02:36.300 --> 00:02:36.310 align:start position:0% respond and communicate with your server 00:02:36.310 --> 00:02:37.830 align:start position:0% respond and communicate with your server or<00:02:36.459> whatever<00:02:36.849> other<00:02:37.030> architecture<00:02:37.689> you<00:02:37.810> have 00:02:37.830 --> 00:02:37.840 align:start position:0% or whatever other architecture you have 00:02:37.840 --> 00:02:41.250 align:start position:0% or whatever other architecture you have and<00:02:38.349> one<00:02:39.189> of<00:02:39.340> those<00:02:39.579> is<00:02:39.879> what<00:02:40.629> I<00:02:40.659> call<00:02:40.870> central 00:02:41.250 --> 00:02:41.260 align:start position:0% and one of those is what I call central 00:02:41.260 --> 00:02:45.960 align:start position:0% and one of those is what I call central logging<00:02:41.799> in<00:02:42.700> a<00:02:42.819> multi<00:02:43.150> contract<00:02:43.720> system<00:02:44.970> logs 00:02:45.960 --> 00:02:45.970 align:start position:0% logging in a multi contract system logs 00:02:45.970 --> 00:02:49.860 align:start position:0% logging in a multi contract system logs or<00:02:46.450> events<00:02:47.319> that<00:02:47.530> are<00:02:47.859> fired<00:02:48.129> are<00:02:48.730> really<00:02:49.720> an 00:02:49.860 --> 00:02:49.870 align:start position:0% or events that are fired are really an 00:02:49.870 --> 00:02:51.629 align:start position:0% or events that are fired are really an important<00:02:50.319> way<00:02:50.500> to<00:02:50.560> track<00:02:50.950> what's<00:02:51.220> happening 00:02:51.629 --> 00:02:51.639 align:start position:0% important way to track what's happening 00:02:51.639 --> 00:02:54.449 align:start position:0% important way to track what's happening on<00:02:51.790> chain<00:02:52.150> all<00:02:53.019> of<00:02:53.170> your<00:02:53.290> off<00:02:53.409> chain<00:02:53.739> activity 00:02:54.449 --> 00:02:54.459 align:start position:0% on chain all of your off chain activity 00:02:54.459 --> 00:02:56.399 align:start position:0% on chain all of your off chain activity is<00:02:54.700> going<00:02:55.030> to<00:02:55.180> be<00:02:55.299> based<00:02:55.599> on<00:02:55.810> different<00:02:55.959> events 00:02:56.399 --> 00:02:56.409 align:start position:0% is going to be based on different events 00:02:56.409 --> 00:03:01.589 align:start position:0% is going to be based on different events that<00:02:56.530> are<00:02:56.620> firing<00:02:56.889> and<00:02:58.620> when<00:02:59.620> you<00:02:59.909> are<00:03:00.909> firing 00:03:01.589 --> 00:03:01.599 align:start position:0% that are firing and when you are firing 00:03:01.599 --> 00:03:03.270 align:start position:0% that are firing and when you are firing events<00:03:01.930> from<00:03:02.200> different<00:03:02.500> contracts<00:03:02.980> you 00:03:03.270 --> 00:03:03.280 align:start position:0% events from different contracts you 00:03:03.280 --> 00:03:06.270 align:start position:0% events from different contracts you generally<00:03:03.909> have<00:03:04.120> to<00:03:04.530> monitor<00:03:05.530> those<00:03:05.889> events 00:03:06.270 --> 00:03:06.280 align:start position:0% generally have to monitor those events 00:03:06.280 --> 00:03:08.190 align:start position:0% generally have to monitor those events separately<00:03:06.879> so<00:03:07.120> each<00:03:07.299> contract<00:03:07.900> you're<00:03:08.079> going 00:03:08.190 --> 00:03:08.200 align:start position:0% separately so each contract you're going 00:03:08.200 --> 00:03:10.259 align:start position:0% separately so each contract you're going to<00:03:08.260> be<00:03:08.349> watching<00:03:08.829> those<00:03:08.950> events<00:03:09.310> and<00:03:09.549> so<00:03:10.000> if 00:03:10.259 --> 00:03:10.269 align:start position:0% to be watching those events and so if 00:03:10.269 --> 00:03:13.470 align:start position:0% to be watching those events and so if you<00:03:10.629> have<00:03:10.840> a<00:03:10.870> multi<00:03:11.290> contract<00:03:11.799> system<00:03:12.480> there's 00:03:13.470 --> 00:03:13.480 align:start position:0% you have a multi contract system there's 00:03:13.480 --> 00:03:15.780 align:start position:0% you have a multi contract system there's actually<00:03:13.840> a<00:03:13.870> lot<00:03:14.049> of<00:03:14.170> benefits<00:03:14.620> to<00:03:15.220> using<00:03:15.519> a 00:03:15.780 --> 00:03:15.790 align:start position:0% actually a lot of benefits to using a 00:03:15.790 --> 00:03:19.740 align:start position:0% actually a lot of benefits to using a single<00:03:16.180> logger<00:03:16.450> contract<00:03:17.200> and<00:03:17.489> so<00:03:18.489> when<00:03:19.269> you 00:03:19.740 --> 00:03:19.750 align:start position:0% single logger contract and so when you 00:03:19.750 --> 00:03:21.420 align:start position:0% single logger contract and so when you have<00:03:19.870> a<00:03:19.900> single<00:03:20.230> logger<00:03:20.470> contract<00:03:21.040> all<00:03:21.280> of 00:03:21.420 --> 00:03:21.430 align:start position:0% have a single logger contract all of 00:03:21.430 --> 00:03:23.009 align:start position:0% have a single logger contract all of those<00:03:21.579> events<00:03:21.849> will<00:03:22.209> fire<00:03:22.480> from<00:03:22.750> the<00:03:22.840> same 00:03:23.009 --> 00:03:23.019 align:start position:0% those events will fire from the same 00:03:23.019 --> 00:03:25.110 align:start position:0% those events will fire from the same contract<00:03:23.530> and<00:03:23.709> are<00:03:23.799> easier<00:03:24.099> to<00:03:24.549> monitor<00:03:24.730> so 00:03:25.110 --> 00:03:25.120 align:start position:0% contract and are easier to monitor so 00:03:25.120 --> 00:03:27.300 align:start position:0% contract and are easier to monitor so let<00:03:25.329> me<00:03:25.419> just<00:03:25.599> show<00:03:25.720> you<00:03:25.750> how<00:03:26.019> that<00:03:26.230> looks<00:03:26.560> so 00:03:27.300 --> 00:03:27.310 align:start position:0% let me just show you how that looks so 00:03:27.310 --> 00:03:31.379 align:start position:0% let me just show you how that looks so here's<00:03:27.879> an<00:03:28.629> example<00:03:29.470> of<00:03:30.040> the<00:03:30.250> logger<00:03:30.489> contract 00:03:31.379 --> 00:03:31.389 align:start position:0% here's an example of the logger contract 00:03:31.389 --> 00:03:36.780 align:start position:0% here's an example of the logger contract and<00:03:32.250> what<00:03:33.250> we<00:03:33.340> have<00:03:33.549> here<00:03:34.180> is<00:03:34.739> a<00:03:35.739> white<00:03:36.489> list 00:03:36.780 --> 00:03:36.790 align:start position:0% and what we have here is a white list 00:03:36.790 --> 00:03:42.390 align:start position:0% and what we have here is a white list that<00:03:37.209> map's<00:03:38.069> addresses<00:03:39.069> of<00:03:39.720> contracts<00:03:40.949> to<00:03:41.949> a 00:03:42.390 --> 00:03:42.400 align:start position:0% that map's addresses of contracts to a 00:03:42.400 --> 00:03:44.159 align:start position:0% that map's addresses of contracts to a simple<00:03:42.940> boolean<00:03:43.120> that<00:03:43.359> says<00:03:43.720> whether<00:03:43.900> it's 00:03:44.159 --> 00:03:44.169 align:start position:0% simple boolean that says whether it's 00:03:44.169 --> 00:03:46.289 align:start position:0% simple boolean that says whether it's been<00:03:44.349> approved<00:03:44.709> or<00:03:44.889> not<00:03:44.949> so<00:03:45.790> this<00:03:45.970> is<00:03:46.090> where<00:03:46.209> it 00:03:46.289 --> 00:03:46.299 align:start position:0% been approved or not so this is where it 00:03:46.299 --> 00:03:47.879 align:start position:0% been approved or not so this is where it handles<00:03:46.599> multiple<00:03:46.810> contracts<00:03:47.650> so<00:03:47.739> this 00:03:47.879 --> 00:03:47.889 align:start position:0% handles multiple contracts so this 00:03:47.889 --> 00:03:50.520 align:start position:0% handles multiple contracts so this addresses<00:03:48.400> our<00:03:48.549> of<00:03:48.669> contracts<00:03:49.239> and<00:03:49.419> you<00:03:50.379> have 00:03:50.520 --> 00:03:50.530 align:start position:0% addresses our of contracts and you have 00:03:50.530 --> 00:03:53.119 align:start position:0% addresses our of contracts and you have a<00:03:50.560> modifier<00:03:51.129> that's<00:03:51.549> a<00:03:51.819> simple<00:03:52.389> requirement 00:03:53.119 --> 00:03:53.129 align:start position:0% a modifier that's a simple requirement 00:03:53.129 --> 00:03:56.069 align:start position:0% a modifier that's a simple requirement that<00:03:54.129> the<00:03:54.400> sender<00:03:54.849> is<00:03:55.090> indeed<00:03:55.840> in<00:03:56.049> that 00:03:56.069 --> 00:03:56.079 align:start position:0% that the sender is indeed in that 00:03:56.079 --> 00:03:59.550 align:start position:0% that the sender is indeed in that whitelist<00:03:56.859> and<00:03:57.419> so<00:03:58.419> the<00:03:59.049> modifier 00:03:59.550 --> 00:03:59.560 align:start position:0% whitelist and so the modifier 00:03:59.560 --> 00:04:02.939 align:start position:0% whitelist and so the modifier whitelisted<00:04:00.489> is<00:04:00.900> provided<00:04:01.900> here<00:04:02.199> and<00:04:02.319> then 00:04:02.939 --> 00:04:02.949 align:start position:0% whitelisted is provided here and then 00:04:02.949 --> 00:04:06.030 align:start position:0% whitelisted is provided here and then you<00:04:03.459> can<00:04:03.639> have<00:04:03.849> any<00:04:04.150> event<00:04:04.720> here<00:04:05.379> the<00:04:05.530> event<00:04:05.859> is 00:04:06.030 --> 00:04:06.040 align:start position:0% you can have any event here the event is 00:04:06.040 --> 00:04:08.729 align:start position:0% you can have any event here the event is called<00:04:06.190> registered<00:04:06.879> so<00:04:07.510> that's<00:04:07.690> the<00:04:07.900> red<00:04:08.139> text 00:04:08.729 --> 00:04:08.739 align:start position:0% called registered so that's the red text 00:04:08.739 --> 00:04:11.969 align:start position:0% called registered so that's the red text with<00:04:09.549> the<00:04:09.760> two<00:04:10.419> superscript<00:04:11.139> and<00:04:11.319> the 00:04:11.969 --> 00:04:11.979 align:start position:0% with the two superscript and the 00:04:11.979 --> 00:04:14.849 align:start position:0% with the two superscript and the registered<00:04:12.489> event<00:04:12.790> is<00:04:13.180> simply<00:04:14.049> forwarded 00:04:14.849 --> 00:04:14.859 align:start position:0% registered event is simply forwarded 00:04:14.859 --> 00:04:18.330 align:start position:0% registered event is simply forwarded from<00:04:15.069> the<00:04:15.579> log<00:04:15.760> registered<00:04:16.359> function<00:04:16.889> so<00:04:17.889> if 00:04:18.330 --> 00:04:18.340 align:start position:0% from the log registered function so if 00:04:18.340 --> 00:04:21.479 align:start position:0% from the log registered function so if you<00:04:19.000> have<00:04:19.180> the<00:04:19.389> owner<00:04:19.709> which<00:04:20.709> is<00:04:20.739> provided 00:04:21.479 --> 00:04:21.489 align:start position:0% you have the owner which is provided 00:04:21.489 --> 00:04:24.089 align:start position:0% you have the owner which is provided with<00:04:21.699> the<00:04:22.030> owner<00:04:22.330> super<00:04:23.229> contract<00:04:23.740> and<00:04:24.010> then 00:04:24.089 --> 00:04:24.099 align:start position:0% with the owner super contract and then 00:04:24.099 --> 00:04:26.250 align:start position:0% with the owner super contract and then the<00:04:24.219> only<00:04:24.550> owner<00:04:24.760> modifier<00:04:25.360> pretty<00:04:25.779> standard 00:04:26.250 --> 00:04:26.260 align:start position:0% the only owner modifier pretty standard 00:04:26.260 --> 00:04:29.430 align:start position:0% the only owner modifier pretty standard you<00:04:27.219> can<00:04:27.430> have<00:04:27.610> an<00:04:27.969> owner<00:04:28.719> contract 00:04:29.430 --> 00:04:29.440 align:start position:0% you can have an owner contract 00:04:29.440 --> 00:04:32.340 align:start position:0% you can have an owner contract that<00:04:29.710> is<00:04:29.890> able<00:04:30.100> to<00:04:30.370> register<00:04:31.140> all<00:04:32.140> the 00:04:32.340 --> 00:04:32.350 align:start position:0% that is able to register all the 00:04:32.350 --> 00:04:34.770 align:start position:0% that is able to register all the contracts<00:04:32.830> in<00:04:32.980> the<00:04:33.070> system<00:04:33.430> so<00:04:33.940> contract<00:04:34.630> a 00:04:34.770 --> 00:04:34.780 align:start position:0% contracts in the system so contract a 00:04:34.780 --> 00:04:37.260 align:start position:0% contracts in the system so contract a contract<00:04:34.810> B<00:04:35.440> contract<00:04:35.920> C<00:04:36.130> all<00:04:36.550> of<00:04:36.850> those<00:04:37.000> would 00:04:37.260 --> 00:04:37.270 align:start position:0% contract B contract C all of those would 00:04:37.270 --> 00:04:39.690 align:start position:0% contract B contract C all of those would be<00:04:37.390> an<00:04:37.480> authorized<00:04:38.220> contract<00:04:39.220> to<00:04:39.370> be<00:04:39.490> able<00:04:39.580> to 00:04:39.690 --> 00:04:39.700 align:start position:0% be an authorized contract to be able to 00:04:39.700 --> 00:04:41.940 align:start position:0% be an authorized contract to be able to register<00:04:40.000> those<00:04:40.540> and<00:04:40.900> if<00:04:41.290> that<00:04:41.470> authorized 00:04:41.940 --> 00:04:41.950 align:start position:0% register those and if that authorized 00:04:41.950 --> 00:04:46.080 align:start position:0% register those and if that authorized address<00:04:42.880> was<00:04:43.180> set<00:04:43.990> in<00:04:44.170> creation<00:04:44.740> then<00:04:45.370> you 00:04:46.080 --> 00:04:46.090 align:start position:0% address was set in creation then you 00:04:46.090 --> 00:04:47.790 align:start position:0% address was set in creation then you know<00:04:46.300> exactly<00:04:46.660> who<00:04:47.080> has<00:04:47.230> the<00:04:47.440> ability<00:04:47.770> to 00:04:47.790 --> 00:04:47.800 align:start position:0% know exactly who has the ability to 00:04:47.800 --> 00:04:50.760 align:start position:0% know exactly who has the ability to register<00:04:48.730> new<00:04:48.880> contracts<00:04:49.480> and<00:04:49.780> then<00:04:50.530> those 00:04:50.760 --> 00:04:50.770 align:start position:0% register new contracts and then those 00:04:50.770 --> 00:04:53.720 align:start position:0% register new contracts and then those contracts<00:04:51.370> have<00:04:51.580> the<00:04:51.730> ability<00:04:52.180> to<00:04:52.420> call<00:04:53.290> log 00:04:53.720 --> 00:04:53.730 align:start position:0% contracts have the ability to call log 00:04:53.730 --> 00:04:57.630 align:start position:0% contracts have the ability to call log registered<00:04:54.730> or<00:04:55.090> any<00:04:55.420> event<00:04:56.280> so<00:04:57.280> that's<00:04:57.490> an 00:04:57.630 --> 00:04:57.640 align:start position:0% registered or any event so that's an 00:04:57.640 --> 00:04:59.100 align:start position:0% registered or any event so that's an example<00:04:57.700> of<00:04:58.060> central<00:04:58.480> logging<00:04:58.840> and<00:04:58.990> that's 00:04:59.100 --> 00:04:59.110 align:start position:0% example of central logging and that's 00:04:59.110 --> 00:05:01.370 align:start position:0% example of central logging and that's been<00:04:59.290> super<00:04:59.620> helpful<00:04:59.740> for<00:05:00.220> us<00:05:00.490> to<00:05:00.670> be<00:05:00.790> able<00:05:00.880> to 00:05:01.370 --> 00:05:01.380 align:start position:0% been super helpful for us to be able to 00:05:01.380 --> 00:05:05.820 align:start position:0% been super helpful for us to be able to handle<00:05:02.790> large<00:05:03.790> numbers<00:05:04.330> of<00:05:04.410> events<00:05:05.410> from<00:05:05.560> lots 00:05:05.820 --> 00:05:05.830 align:start position:0% handle large numbers of events from lots 00:05:05.830 --> 00:05:07.110 align:start position:0% handle large numbers of events from lots of<00:05:05.950> different<00:05:06.010> contracts<00:05:06.760> in<00:05:06.820> a<00:05:06.880> multi 00:05:07.110 --> 00:05:07.120 align:start position:0% of different contracts in a multi 00:05:07.120 --> 00:05:10.230 align:start position:0% of different contracts in a multi contract<00:05:07.600> system<00:05:08.610> the<00:05:09.610> next<00:05:09.760> one<00:05:09.940> I<00:05:09.970> want<00:05:10.060> to 00:05:10.230 --> 00:05:10.240 align:start position:0% contract system the next one I want to 00:05:10.240 --> 00:05:12.990 align:start position:0% contract system the next one I want to show<00:05:10.360> you<00:05:10.420> is<00:05:11.160> the<00:05:12.160> idea<00:05:12.280> of<00:05:12.490> modular 00:05:12.990 --> 00:05:13.000 align:start position:0% show you is the idea of modular 00:05:13.000 --> 00:05:16.410 align:start position:0% show you is the idea of modular libraries<00:05:13.690> so<00:05:14.470> libraries<00:05:14.920> in<00:05:15.730> solidity<00:05:16.240> if 00:05:16.410 --> 00:05:16.420 align:start position:0% libraries so libraries in solidity if 00:05:16.420 --> 00:05:19.520 align:start position:0% libraries so libraries in solidity if you're<00:05:16.660> not<00:05:16.870> aware<00:05:16.990> already<00:05:17.500> are<00:05:17.800> a<00:05:18.190> way<00:05:18.730> of 00:05:19.520 --> 00:05:19.530 align:start position:0% you're not aware already are a way of 00:05:19.530 --> 00:05:23.940 align:start position:0% you're not aware already are a way of deploying<00:05:20.530> code<00:05:21.280> once<00:05:21.730> that<00:05:22.420> other<00:05:23.230> contracts 00:05:23.940 --> 00:05:23.950 align:start position:0% deploying code once that other contracts 00:05:23.950 --> 00:05:27.720 align:start position:0% deploying code once that other contracts can<00:05:24.280> use<00:05:24.580> over<00:05:25.150> and<00:05:25.300> over<00:05:25.540> and<00:05:26.280> when<00:05:27.280> you<00:05:27.460> have 00:05:27.720 --> 00:05:27.730 align:start position:0% can use over and over and when you have 00:05:27.730 --> 00:05:29.490 align:start position:0% can use over and over and when you have a<00:05:27.760> multi<00:05:28.240> contract<00:05:28.780> system<00:05:29.020> or<00:05:29.380> you're 00:05:29.490 --> 00:05:29.500 align:start position:0% a multi contract system or you're 00:05:29.500 --> 00:05:32.160 align:start position:0% a multi contract system or you're deploying<00:05:29.980> a<00:05:30.190> new<00:05:30.220> contract<00:05:30.940> for<00:05:31.210> every 00:05:32.160 --> 00:05:32.170 align:start position:0% deploying a new contract for every 00:05:32.170 --> 00:05:34.860 align:start position:0% deploying a new contract for every iteration<00:05:32.650> of<00:05:33.130> something<00:05:33.550> there's<00:05:34.480> a<00:05:34.540> lot<00:05:34.750> of 00:05:34.860 --> 00:05:34.870 align:start position:0% iteration of something there's a lot of 00:05:34.870 --> 00:05:36.420 align:start position:0% iteration of something there's a lot of gas<00:05:35.080> costs<00:05:35.530> in<00:05:35.650> that<00:05:35.770> and<00:05:35.980> if<00:05:36.070> you<00:05:36.220> can 00:05:36.420 --> 00:05:36.430 align:start position:0% gas costs in that and if you can 00:05:36.430 --> 00:05:38.610 align:start position:0% gas costs in that and if you can reference<00:05:37.150> if<00:05:37.540> you<00:05:37.630> can<00:05:37.750> link<00:05:37.990> a<00:05:38.140> library 00:05:38.610 --> 00:05:38.620 align:start position:0% reference if you can link a library 00:05:38.620 --> 00:05:41.010 align:start position:0% reference if you can link a library that's<00:05:38.860> gonna<00:05:39.040> save<00:05:39.400> a<00:05:39.430> lot<00:05:39.730> of<00:05:39.760> gas<00:05:40.060> compared 00:05:41.010 --> 00:05:41.020 align:start position:0% that's gonna save a lot of gas compared 00:05:41.020 --> 00:05:42.840 align:start position:0% that's gonna save a lot of gas compared to<00:05:41.140> implementing<00:05:41.590> and<00:05:42.010> compared<00:05:42.760> to 00:05:42.840 --> 00:05:42.850 align:start position:0% to implementing and compared to 00:05:42.850 --> 00:05:45.860 align:start position:0% to implementing and compared to deploying<00:05:43.419> all<00:05:43.570> the<00:05:43.750> contracts<00:05:44.230> again<00:05:44.669> so 00:05:45.860 --> 00:05:45.870 align:start position:0% deploying all the contracts again so 00:05:45.870 --> 00:05:48.450 align:start position:0% deploying all the contracts again so libraries<00:05:46.870> are<00:05:47.020> known<00:05:47.230> as<00:05:47.470> well-known<00:05:48.160> to<00:05:48.430> be 00:05:48.450 --> 00:05:48.460 align:start position:0% libraries are known as well-known to be 00:05:48.460 --> 00:05:51.240 align:start position:0% libraries are known as well-known to be to<00:05:48.910> provide<00:05:49.150> that<00:05:49.360> gas<00:05:49.570> saving<00:05:49.990> mechanism<00:05:50.530> and 00:05:51.240 --> 00:05:51.250 align:start position:0% to provide that gas saving mechanism and 00:05:51.250 --> 00:05:54.150 align:start position:0% to provide that gas saving mechanism and the<00:05:51.340> idea<00:05:51.580> of<00:05:51.610> modular<00:05:52.150> libraries<00:05:52.750> is<00:05:53.160> the 00:05:54.150 --> 00:05:54.160 align:start position:0% the idea of modular libraries is the 00:05:54.160 --> 00:05:55.260 align:start position:0% the idea of modular libraries is the idea<00:05:54.460> that<00:05:54.610> you<00:05:54.700> can<00:05:54.850> link<00:05:55.060> multiple 00:05:55.260 --> 00:05:55.270 align:start position:0% idea that you can link multiple 00:05:55.270 --> 00:05:57.300 align:start position:0% idea that you can link multiple libraries<00:05:55.990> together<00:05:56.169> in<00:05:56.650> order<00:05:56.830> to<00:05:56.950> provide 00:05:57.300 --> 00:05:57.310 align:start position:0% libraries together in order to provide 00:05:57.310 --> 00:05:59.520 align:start position:0% libraries together in order to provide some<00:05:57.640> abstraction<00:05:58.240> layers<00:05:58.419> so<00:05:59.020> these<00:05:59.200> are<00:05:59.380> all 00:05:59.520 --> 00:05:59.530 align:start position:0% some abstraction layers so these are all 00:05:59.530 --> 00:06:01.680 align:start position:0% some abstraction layers so these are all like<00:05:59.800> architectural<00:06:00.550> patterns<00:06:00.940> for<00:06:01.570> you<00:06:01.660> to 00:06:01.680 --> 00:06:01.690 align:start position:0% like architectural patterns for you to 00:06:01.690 --> 00:06:03.360 align:start position:0% like architectural patterns for you to have<00:06:01.870> more<00:06:02.050> maintainable<00:06:02.620> smart<00:06:02.919> contract 00:06:03.360 --> 00:06:03.370 align:start position:0% have more maintainable smart contract 00:06:03.370 --> 00:06:05.400 align:start position:0% have more maintainable smart contract code<00:06:03.550> so<00:06:04.120> what<00:06:04.240> does<00:06:04.360> this<00:06:04.480> look<00:06:04.690> like<00:06:04.900> the 00:06:05.400 --> 00:06:05.410 align:start position:0% code so what does this look like the 00:06:05.410 --> 00:06:09.810 align:start position:0% code so what does this look like the modular<00:06:05.919> library<00:06:06.510> is<00:06:07.510> one<00:06:08.470> in<00:06:08.650> which<00:06:08.820> the 00:06:09.810 --> 00:06:09.820 align:start position:0% modular library is one in which the 00:06:09.820 --> 00:06:11.640 align:start position:0% modular library is one in which the contract<00:06:10.419> itself<00:06:10.780> doesn't<00:06:11.140> have<00:06:11.320> to<00:06:11.470> know 00:06:11.640 --> 00:06:11.650 align:start position:0% contract itself doesn't have to know 00:06:11.650 --> 00:06:13.560 align:start position:0% contract itself doesn't have to know about<00:06:11.890> all<00:06:12.070> of<00:06:12.430> the<00:06:12.550> different<00:06:12.700> modules<00:06:13.360> and 00:06:13.560 --> 00:06:13.570 align:start position:0% about all of the different modules and 00:06:13.570 --> 00:06:15.470 align:start position:0% about all of the different modules and so<00:06:14.169> it's<00:06:14.290> a<00:06:14.350> way<00:06:14.440> to<00:06:14.500> encapsulate 00:06:15.470 --> 00:06:15.480 align:start position:0% so it's a way to encapsulate 00:06:15.480 --> 00:06:17.909 align:start position:0% so it's a way to encapsulate functionality<00:06:16.480> within<00:06:16.900> a<00:06:16.930> library<00:06:17.620> in<00:06:17.830> order 00:06:17.909 --> 00:06:17.919 align:start position:0% functionality within a library in order 00:06:17.919 --> 00:06:19.170 align:start position:0% functionality within a library in order to<00:06:18.130> have<00:06:18.280> some<00:06:18.520> separation 00:06:19.170 --> 00:06:19.180 align:start position:0% to have some separation 00:06:19.180 --> 00:06:22.050 align:start position:0% to have some separation now<00:06:19.690> libraries<00:06:20.560> are<00:06:20.770> linked<00:06:21.250> and<00:06:21.460> all<00:06:21.820> of<00:06:21.970> the 00:06:22.050 --> 00:06:22.060 align:start position:0% now libraries are linked and all of the 00:06:22.060 --> 00:06:25.680 align:start position:0% now libraries are linked and all of the calls<00:06:22.360> end<00:06:22.750> up<00:06:23.050> appearing<00:06:23.919> internal<00:06:24.460> so<00:06:25.210> this 00:06:25.680 --> 00:06:25.690 align:start position:0% calls end up appearing internal so this 00:06:25.690 --> 00:06:28.860 align:start position:0% calls end up appearing internal so this doesn't<00:06:25.960> actually<00:06:26.230> provide<00:06:27.450> is<00:06:28.450> more<00:06:28.720> of<00:06:28.780> an 00:06:28.860 --> 00:06:28.870 align:start position:0% doesn't actually provide is more of an 00:06:28.870 --> 00:06:30.300 align:start position:0% doesn't actually provide is more of an organizational<00:06:29.680> strategy<00:06:30.160> and 00:06:30.300 --> 00:06:30.310 align:start position:0% organizational strategy and 00:06:30.310 --> 00:06:33.480 align:start position:0% organizational strategy and architectural<00:06:30.910> strategy<00:06:31.600> than<00:06:32.410> changing<00:06:33.130> the 00:06:33.480 --> 00:06:33.490 align:start position:0% architectural strategy than changing the 00:06:33.490 --> 00:06:37.920 align:start position:0% architectural strategy than changing the actual<00:06:33.850> access<00:06:34.680> levels<00:06:35.680> so<00:06:36.780> here's<00:06:37.780> an 00:06:37.920 --> 00:06:37.930 align:start position:0% actual access levels so here's an 00:06:37.930 --> 00:06:41.010 align:start position:0% actual access levels so here's an example<00:06:38.400> for<00:06:39.400> the<00:06:39.520> prism<00:06:39.910> project<00:06:40.479> we<00:06:40.720> have<00:06:40.990> a 00:06:41.010 --> 00:06:41.020 align:start position:0% example for the prism project we have a 00:06:41.020 --> 00:06:42.820 align:start position:0% example for the prism project we have a library<00:06:41.680> called<00:06:41.890> prism<00:06:42.370> Lib 00:06:42.820 --> 00:06:42.830 align:start position:0% library called prism Lib 00:06:42.830 --> 00:06:45.969 align:start position:0% library called prism Lib and<00:06:43.639> there's<00:06:43.909> a<00:06:44.000> lot<00:06:44.210> of<00:06:44.360> different<00:06:44.800> pieces<00:06:45.800> of 00:06:45.969 --> 00:06:45.979 align:start position:0% and there's a lot of different pieces of 00:06:45.979 --> 00:06:48.010 align:start position:0% and there's a lot of different pieces of data<00:06:46.340> and<00:06:46.759> libraries<00:06:47.360> that<00:06:47.389> have<00:06:47.509> functions 00:06:48.010 --> 00:06:48.020 align:start position:0% data and libraries that have functions 00:06:48.020 --> 00:06:50.469 align:start position:0% data and libraries that have functions that<00:06:48.080> operate<00:06:48.289> on<00:06:48.650> that<00:06:48.800> data<00:06:48.860> and<00:06:49.370> as<00:06:50.180> a<00:06:50.210> way 00:06:50.469 --> 00:06:50.479 align:start position:0% that operate on that data and as a way 00:06:50.479 --> 00:06:53.740 align:start position:0% that operate on that data and as a way to<00:06:50.539> break<00:06:51.379> it<00:06:51.530> into<00:06:51.650> smaller<00:06:51.979> pieces<00:06:52.509> one<00:06:53.509> good 00:06:53.740 --> 00:06:53.750 align:start position:0% to break it into smaller pieces one good 00:06:53.750 --> 00:06:58.510 align:start position:0% to break it into smaller pieces one good method<00:06:54.379> is<00:06:54.560> to<00:06:55.340> have<00:06:55.729> data<00:06:56.690> instruct<00:06:57.319> in<00:06:57.620> each 00:06:58.510 --> 00:06:58.520 align:start position:0% method is to have data instruct in each 00:06:58.520 --> 00:07:01.119 align:start position:0% method is to have data instruct in each of<00:06:58.759> the<00:06:58.940> libraries<00:06:59.409> that's<00:07:00.409> defined<00:07:00.830> in<00:07:00.979> each 00:07:01.119 --> 00:07:01.129 align:start position:0% of the libraries that's defined in each 00:07:01.129 --> 00:07:02.860 align:start position:0% of the libraries that's defined in each of<00:07:01.250> the<00:07:01.310> libraries<00:07:01.520> and<00:07:02.060> then<00:07:02.300> that<00:07:02.569> can<00:07:02.750> be 00:07:02.860 --> 00:07:02.870 align:start position:0% of the libraries and then that can be 00:07:02.870 --> 00:07:04.960 align:start position:0% of the libraries and then that can be included<00:07:03.169> in<00:07:03.409> the<00:07:03.530> contract<00:07:04.039> and<00:07:04.250> so<00:07:04.669> you<00:07:04.729> have 00:07:04.960 --> 00:07:04.970 align:start position:0% included in the contract and so you have 00:07:04.970 --> 00:07:07.029 align:start position:0% included in the contract and so you have nested<00:07:05.479> levels<00:07:05.840> of<00:07:05.990> data<00:07:06.199> so<00:07:06.470> the<00:07:06.620> struct<00:07:06.919> is 00:07:07.029 --> 00:07:07.039 align:start position:0% nested levels of data so the struct is 00:07:07.039 --> 00:07:09.460 align:start position:0% nested levels of data so the struct is defined<00:07:07.430> you<00:07:07.639> can<00:07:07.669> see<00:07:08.000> in<00:07:08.210> the<00:07:08.599> blue<00:07:08.870> with<00:07:09.259> the 00:07:09.460 --> 00:07:09.470 align:start position:0% defined you can see in the blue with the 00:07:09.470 --> 00:07:12.640 align:start position:0% defined you can see in the blue with the number<00:07:10.190> one<00:07:10.430> is<00:07:10.699> the<00:07:11.240> data<00:07:11.449> struck<00:07:11.900> and<00:07:12.199> then 00:07:12.640 --> 00:07:12.650 align:start position:0% number one is the data struck and then 00:07:12.650 --> 00:07:15.490 align:start position:0% number one is the data struck and then that's<00:07:13.039> being<00:07:13.340> expected<00:07:13.879> to<00:07:14.120> pass<00:07:14.479> into<00:07:15.169> each 00:07:15.490 --> 00:07:15.500 align:start position:0% that's being expected to pass into each 00:07:15.500 --> 00:07:17.619 align:start position:0% that's being expected to pass into each of<00:07:15.680> the<00:07:15.770> functions<00:07:16.219> so<00:07:16.819> the<00:07:16.969> rebalance 00:07:17.619 --> 00:07:17.629 align:start position:0% of the functions so the rebalance 00:07:17.629 --> 00:07:20.320 align:start position:0% of the functions so the rebalance function<00:07:18.110> on<00:07:18.319> the<00:07:18.590> prism<00:07:18.949> Lib<00:07:19.159> is<00:07:19.370> going<00:07:20.120> to 00:07:20.320 --> 00:07:20.330 align:start position:0% function on the prism Lib is going to 00:07:20.330 --> 00:07:24.730 align:start position:0% function on the prism Lib is going to ask<00:07:20.840> for<00:07:21.469> the<00:07:22.099> prism<00:07:22.550> Lib<00:07:22.729> dot<00:07:23.000> data<00:07:23.300> and<00:07:23.740> then 00:07:24.730 --> 00:07:24.740 align:start position:0% ask for the prism Lib dot data and then 00:07:24.740 --> 00:07:28.029 align:start position:0% ask for the prism Lib dot data and then the<00:07:24.979> nested<00:07:25.550> nature<00:07:25.909> is<00:07:26.349> comes<00:07:27.349> from<00:07:27.500> the<00:07:27.830> fact 00:07:28.029 --> 00:07:28.039 align:start position:0% the nested nature is comes from the fact 00:07:28.039 --> 00:07:31.719 align:start position:0% the nested nature is comes from the fact that<00:07:28.129> portfolio<00:07:28.580> Lib<00:07:29.270> has<00:07:30.050> its<00:07:30.710> own<00:07:31.009> portfolio 00:07:31.719 --> 00:07:31.729 align:start position:0% that portfolio Lib has its own portfolio 00:07:31.729 --> 00:07:35.080 align:start position:0% that portfolio Lib has its own portfolio Lib<00:07:31.940> we<00:07:32.090> can<00:07:32.240> assume<00:07:32.539> is<00:07:32.810> that<00:07:33.430> lit<00:07:34.430> B<00:07:34.759> it's 00:07:35.080 --> 00:07:35.090 align:start position:0% Lib we can assume is that lit B it's 00:07:35.090 --> 00:07:37.300 align:start position:0% Lib we can assume is that lit B it's being<00:07:35.750> imported<00:07:36.110> somewhere<00:07:36.620> else<00:07:36.770> so 00:07:37.300 --> 00:07:37.310 align:start position:0% being imported somewhere else so 00:07:37.310 --> 00:07:40.209 align:start position:0% being imported somewhere else so portfolio<00:07:38.030> Lipp<00:07:38.330> we<00:07:39.139> can<00:07:39.319> assume<00:07:39.560> has<00:07:39.800> its<00:07:39.979> own 00:07:40.209 --> 00:07:40.219 align:start position:0% portfolio Lipp we can assume has its own 00:07:40.219 --> 00:07:45.209 align:start position:0% portfolio Lipp we can assume has its own data<00:07:41.030> struct<00:07:42.039> so<00:07:43.039> portfolio<00:07:43.639> Lib<00:07:43.940> can<00:07:44.509> be 00:07:45.209 --> 00:07:45.219 align:start position:0% data struct so portfolio Lib can be 00:07:45.219 --> 00:07:47.469 align:start position:0% data struct so portfolio Lib can be accessed<00:07:46.219> the<00:07:46.400> functions<00:07:46.819> can<00:07:46.969> be<00:07:47.000> called<00:07:47.330> in 00:07:47.469 --> 00:07:47.479 align:start position:0% accessed the functions can be called in 00:07:47.479 --> 00:07:51.610 align:start position:0% accessed the functions can be called in portfolio<00:07:47.960> Lib<00:07:48.199> and<00:07:48.440> the<00:07:49.400> data<00:07:49.669> is<00:07:50.620> contained 00:07:51.610 --> 00:07:51.620 align:start position:0% portfolio Lib and the data is contained 00:07:51.620 --> 00:07:53.800 align:start position:0% portfolio Lib and the data is contained within<00:07:51.740> that<00:07:52.190> Lib<00:07:52.520> and<00:07:52.729> so<00:07:53.240> there's<00:07:53.539> an 00:07:53.800 --> 00:07:53.810 align:start position:0% within that Lib and so there's an 00:07:53.810 --> 00:07:56.050 align:start position:0% within that Lib and so there's an abstraction<00:07:54.740> there<00:07:55.099> if<00:07:55.190> you<00:07:55.310> notice<00:07:55.669> we're 00:07:56.050 --> 00:07:56.060 align:start position:0% abstraction there if you notice we're 00:07:56.060 --> 00:08:00.399 align:start position:0% abstraction there if you notice we're not<00:07:56.090> passing<00:07:56.750> the<00:07:56.900> entire<00:07:57.610> prism<00:07:58.610> Lib<00:07:58.789> data<00:07:59.409> to 00:08:00.399 --> 00:08:00.409 align:start position:0% not passing the entire prism Lib data to 00:08:00.409 --> 00:08:03.010 align:start position:0% not passing the entire prism Lib data to the<00:08:00.500> Reap<00:08:00.680> to<00:08:00.949> the<00:08:01.159> rebalance<00:08:02.150> portfolio<00:08:02.810> Lib 00:08:03.010 --> 00:08:03.020 align:start position:0% the Reap to the rebalance portfolio Lib 00:08:03.020 --> 00:08:05.800 align:start position:0% the Reap to the rebalance portfolio Lib dot<00:08:03.259> rebalance<00:08:03.740> function<00:08:04.569> we're<00:08:05.569> only 00:08:05.800 --> 00:08:05.810 align:start position:0% dot rebalance function we're only 00:08:05.810 --> 00:08:09.370 align:start position:0% dot rebalance function we're only passing<00:08:06.219> self<00:08:07.219> dot<00:08:07.520> portfolio<00:08:08.150> Lib<00:08:08.509> so<00:08:09.169> the 00:08:09.370 --> 00:08:09.380 align:start position:0% passing self dot portfolio Lib so the 00:08:09.380 --> 00:08:11.350 align:start position:0% passing self dot portfolio Lib so the second<00:08:09.740> red<00:08:09.949> instance<00:08:10.400> number<00:08:10.759> two<00:08:10.969> and<00:08:11.330> so 00:08:11.350 --> 00:08:11.360 align:start position:0% second red instance number two and so 00:08:11.360 --> 00:08:15.040 align:start position:0% second red instance number two and so that<00:08:12.349> way<00:08:12.789> portfolio<00:08:13.789> Lib<00:08:14.029> dot<00:08:14.270> rebalance<00:08:14.870> or 00:08:15.040 --> 00:08:15.050 align:start position:0% that way portfolio Lib dot rebalance or 00:08:15.050 --> 00:08:16.930 align:start position:0% that way portfolio Lib dot rebalance or any<00:08:15.199> other<00:08:15.440> functions<00:08:15.979> in<00:08:16.159> portfolio<00:08:16.699> Lib 00:08:16.930 --> 00:08:16.940 align:start position:0% any other functions in portfolio Lib 00:08:16.940 --> 00:08:18.999 align:start position:0% any other functions in portfolio Lib don't<00:08:17.750> have<00:08:17.930> to<00:08:18.080> know<00:08:18.259> about<00:08:18.409> anything<00:08:18.770> else 00:08:18.999 --> 00:08:19.009 align:start position:0% don't have to know about anything else 00:08:19.009 --> 00:08:21.129 align:start position:0% don't have to know about anything else in<00:08:19.159> the<00:08:19.310> data<00:08:19.520> so<00:08:20.330> this<00:08:20.479> ends<00:08:20.750> up<00:08:20.779> being<00:08:20.840> a 00:08:21.129 --> 00:08:21.139 align:start position:0% in the data so this ends up being a 00:08:21.139 --> 00:08:23.140 align:start position:0% in the data so this ends up being a pretty<00:08:21.319> standard<00:08:21.979> abstraction<00:08:22.669> in<00:08:22.819> hiding 00:08:23.140 --> 00:08:23.150 align:start position:0% pretty standard abstraction in hiding 00:08:23.150 --> 00:08:26.800 align:start position:0% pretty standard abstraction in hiding mechanism<00:08:23.889> but<00:08:24.889> something<00:08:25.639> that<00:08:25.669> we<00:08:26.629> haven't 00:08:26.800 --> 00:08:26.810 align:start position:0% mechanism but something that we haven't 00:08:26.810 --> 00:08:28.869 align:start position:0% mechanism but something that we haven't seen<00:08:27.139> a<00:08:27.529> lot<00:08:27.680> about<00:08:28.039> in<00:08:28.219> the<00:08:28.310> wilds<00:08:28.819> with 00:08:28.869 --> 00:08:28.879 align:start position:0% seen a lot about in the wilds with 00:08:28.879 --> 00:08:31.330 align:start position:0% seen a lot about in the wilds with library<00:08:29.419> development<00:08:30.020> but<00:08:30.770> we<00:08:30.860> found<00:08:31.039> it<00:08:31.250> to 00:08:31.330 --> 00:08:31.340 align:start position:0% library development but we found it to 00:08:31.340 --> 00:08:33.579 align:start position:0% library development but we found it to be<00:08:31.370> really<00:08:31.490> great<00:08:32.380> really<00:08:33.380> great 00:08:33.579 --> 00:08:33.589 align:start position:0% be really great really great 00:08:33.589 --> 00:08:37.959 align:start position:0% be really great really great architectural<00:08:34.279> pattern<00:08:34.640> for<00:08:34.880> prism<00:08:36.760> so<00:08:37.760> now 00:08:37.959 --> 00:08:37.969 align:start position:0% architectural pattern for prism so now 00:08:37.969 --> 00:08:40.000 align:start position:0% architectural pattern for prism so now we<00:08:38.029> get<00:08:38.329> to<00:08:38.630> the<00:08:39.079> last<00:08:39.320> of<00:08:39.500> the<00:08:39.620> low-level 00:08:40.000 --> 00:08:40.010 align:start position:0% we get to the last of the low-level 00:08:40.010 --> 00:08:41.500 align:start position:0% we get to the last of the low-level patterns<00:08:40.550> and<00:08:40.729> I<00:08:40.760> want<00:08:40.940> to<00:08:41.000> share<00:08:41.180> with<00:08:41.300> you 00:08:41.500 --> 00:08:41.510 align:start position:0% patterns and I want to share with you 00:08:41.510 --> 00:08:46.000 align:start position:0% patterns and I want to share with you and<00:08:41.719> this<00:08:42.680> is<00:08:42.949> a<00:08:43.490> higher<00:08:44.529> lower-level<00:08:45.529> pattern 00:08:46.000 --> 00:08:46.010 align:start position:0% and this is a higher lower-level pattern 00:08:46.010 --> 00:08:48.970 align:start position:0% and this is a higher lower-level pattern and<00:08:46.220> this<00:08:47.060> is<00:08:47.240> an<00:08:47.360> idea<00:08:47.660> that<00:08:47.899> has<00:08:48.199> been<00:08:48.230> shared 00:08:48.970 --> 00:08:48.980 align:start position:0% and this is an idea that has been shared 00:08:48.980 --> 00:08:51.189 align:start position:0% and this is an idea that has been shared in<00:08:49.220> other<00:08:49.370> talks<00:08:49.699> here<00:08:50.180> the<00:08:50.540> idea<00:08:50.870> of<00:08:50.930> the 00:08:51.189 --> 00:08:51.199 align:start position:0% in other talks here the idea of the 00:08:51.199 --> 00:08:53.650 align:start position:0% in other talks here the idea of the blockchain<00:08:51.440> as<00:08:51.860> a<00:08:51.890> court<00:08:52.220> system<00:08:52.430> and<00:08:52.850> this 00:08:53.650 --> 00:08:53.660 align:start position:0% blockchain as a court system and this 00:08:53.660 --> 00:08:55.510 align:start position:0% blockchain as a court system and this didn't<00:08:53.959> come<00:08:54.140> to<00:08:54.320> me<00:08:54.470> until<00:08:54.860> much<00:08:55.040> later<00:08:55.070> in 00:08:55.510 --> 00:08:55.520 align:start position:0% didn't come to me until much later in 00:08:55.520 --> 00:08:56.690 align:start position:0% didn't come to me until much later in the<00:08:55.610> development<00:08:56.149> of 00:08:56.690 --> 00:08:56.700 align:start position:0% the development of 00:08:56.700 --> 00:09:00.590 align:start position:0% the development of but<00:08:57.270> the<00:08:57.900> opportunity<00:08:58.890> to<00:08:59.640> save<00:08:59.970> a<00:09:00.000> massive 00:09:00.590 --> 00:09:00.600 align:start position:0% but the opportunity to save a massive 00:09:00.600 --> 00:09:03.860 align:start position:0% but the opportunity to save a massive amount<00:09:00.870> of<00:09:00.960> on<00:09:01.110> chain<00:09:01.520> computation<00:09:02.870> exists 00:09:03.860 --> 00:09:03.870 align:start position:0% amount of on chain computation exists 00:09:03.870 --> 00:09:06.770 align:start position:0% amount of on chain computation exists when<00:09:04.500> you<00:09:04.590> treat<00:09:04.800> the<00:09:04.980> blockchain<00:09:05.220> as<00:09:05.730> a<00:09:05.820> court 00:09:06.770 --> 00:09:06.780 align:start position:0% when you treat the blockchain as a court 00:09:06.780 --> 00:09:10.250 align:start position:0% when you treat the blockchain as a court system<00:09:07.200> or<00:09:07.440> an<00:09:08.040> arbiter<00:09:08.600> which<00:09:09.600> means<00:09:09.960> that 00:09:10.250 --> 00:09:10.260 align:start position:0% system or an arbiter which means that 00:09:10.260 --> 00:09:14.530 align:start position:0% system or an arbiter which means that you<00:09:11.190> assume<00:09:11.820> that<00:09:12.420> parties<00:09:12.870> are<00:09:13.050> acting<00:09:13.500> in 00:09:14.530 --> 00:09:14.540 align:start position:0% you assume that parties are acting in 00:09:14.540 --> 00:09:18.560 align:start position:0% you assume that parties are acting in best<00:09:15.540> best<00:09:16.380> in<00:09:17.250> good<00:09:17.580> with<00:09:17.790> good<00:09:18.030> will<00:09:18.240> and 00:09:18.560 --> 00:09:18.570 align:start position:0% best best in good with good will and 00:09:18.570 --> 00:09:20.750 align:start position:0% best best in good with good will and best<00:09:19.080> interest<00:09:19.560> but<00:09:20.130> you<00:09:20.190> have<00:09:20.430> a<00:09:20.460> mechanism 00:09:20.750 --> 00:09:20.760 align:start position:0% best interest but you have a mechanism 00:09:20.760 --> 00:09:23.090 align:start position:0% best interest but you have a mechanism that<00:09:21.600> if<00:09:21.810> something<00:09:22.260> goes<00:09:22.290> wrong<00:09:22.530> if<00:09:22.890> one 00:09:23.090 --> 00:09:23.100 align:start position:0% that if something goes wrong if one 00:09:23.100 --> 00:09:25.130 align:start position:0% that if something goes wrong if one party<00:09:23.430> says<00:09:23.640> the<00:09:23.700> other<00:09:24.000> is<00:09:24.360> not<00:09:24.840> doing 00:09:25.130 --> 00:09:25.140 align:start position:0% party says the other is not doing 00:09:25.140 --> 00:09:27.530 align:start position:0% party says the other is not doing they're<00:09:25.410> not<00:09:26.370> fulfilling<00:09:26.760> their<00:09:26.970> obligation 00:09:27.530 --> 00:09:27.540 align:start position:0% they're not fulfilling their obligation 00:09:27.540 --> 00:09:31.010 align:start position:0% they're not fulfilling their obligation then<00:09:28.440> you<00:09:29.130> can<00:09:29.400> run<00:09:30.000> an<00:09:30.300> actual<00:09:30.480> smart 00:09:31.010 --> 00:09:31.020 align:start position:0% then you can run an actual smart 00:09:31.020 --> 00:09:33.950 align:start position:0% then you can run an actual smart contract<00:09:31.530> as<00:09:32.150> if<00:09:33.150> you're<00:09:33.360> bringing<00:09:33.720> it<00:09:33.840> to 00:09:33.950 --> 00:09:33.960 align:start position:0% contract as if you're bringing it to 00:09:33.960 --> 00:09:36.230 align:start position:0% contract as if you're bringing it to court<00:09:34.260> and<00:09:34.890> when<00:09:35.490> you<00:09:35.580> run<00:09:35.760> that<00:09:35.970> when<00:09:36.150> you 00:09:36.230 --> 00:09:36.240 align:start position:0% court and when you run that when you 00:09:36.240 --> 00:09:38.330 align:start position:0% court and when you run that when you execute<00:09:36.750> that<00:09:36.780> smart<00:09:37.200> contract<00:09:37.680> then<00:09:38.070> you're 00:09:38.330 --> 00:09:38.340 align:start position:0% execute that smart contract then you're 00:09:38.340 --> 00:09:40.970 align:start position:0% execute that smart contract then you're using<00:09:38.820> the<00:09:39.030> blockchain<00:09:39.270> to<00:09:39.630> orbit<00:09:40.050> to<00:09:40.380> arm<00:09:40.800> it 00:09:40.970 --> 00:09:40.980 align:start position:0% using the blockchain to orbit to arm it 00:09:40.980 --> 00:09:42.830 align:start position:0% using the blockchain to orbit to arm it that<00:09:41.190> to<00:09:41.850> be<00:09:41.970> the<00:09:42.090> arbiter<00:09:42.240> of<00:09:42.600> that 00:09:42.830 --> 00:09:42.840 align:start position:0% that to be the arbiter of that 00:09:42.840 --> 00:09:44.890 align:start position:0% that to be the arbiter of that transaction<00:09:43.290> so<00:09:43.860> what<00:09:44.070> does<00:09:44.160> that<00:09:44.190> look<00:09:44.640> like 00:09:44.890 --> 00:09:44.900 align:start position:0% transaction so what does that look like 00:09:44.900 --> 00:09:48.920 align:start position:0% transaction so what does that look like so<00:09:45.900> here<00:09:46.260> we<00:09:46.440> have<00:09:46.650> a<00:09:47.090> contract<00:09:48.090> this<00:09:48.570> is<00:09:48.720> just 00:09:48.920 --> 00:09:48.930 align:start position:0% so here we have a contract this is just 00:09:48.930 --> 00:09:51.320 align:start position:0% so here we have a contract this is just a<00:09:49.050> general<00:09:49.590> you<00:09:50.130> have<00:09:50.310> some<00:09:50.580> users<00:09:50.970> and 00:09:51.320 --> 00:09:51.330 align:start position:0% a general you have some users and 00:09:51.330 --> 00:09:53.960 align:start position:0% a general you have some users and there's<00:09:51.810> going<00:09:51.990> to<00:09:52.050> be<00:09:52.140> a<00:09:52.200> counterparty<00:09:52.980> the 00:09:53.960 --> 00:09:53.970 align:start position:0% there's going to be a counterparty the 00:09:53.970 --> 00:09:56.540 align:start position:0% there's going to be a counterparty the other<00:09:54.210> end<00:09:54.420> of<00:09:54.570> the<00:09:54.660> deal<00:09:54.870> and<00:09:55.310> they're<00:09:56.310> using 00:09:56.540 --> 00:09:56.550 align:start position:0% other end of the deal and they're using 00:09:56.550 --> 00:09:59.510 align:start position:0% other end of the deal and they're using you're<00:09:56.910> using<00:09:57.120> the<00:09:57.360> smart<00:09:57.630> contract<00:09:58.520> the 00:09:59.510 --> 00:09:59.520 align:start position:0% you're using the smart contract the 00:09:59.520 --> 00:10:01.310 align:start position:0% you're using the smart contract the naive<00:09:59.880> approach<00:10:00.060> would<00:10:00.510> be<00:10:00.540> to<00:10:00.780> execute 00:10:01.310 --> 00:10:01.320 align:start position:0% naive approach would be to execute 00:10:01.320 --> 00:10:05.330 align:start position:0% naive approach would be to execute everything<00:10:01.740> on<00:10:01.860> the<00:10:02.010> smart<00:10:02.280> contract<00:10:04.340> when 00:10:05.330 --> 00:10:05.340 align:start position:0% everything on the smart contract when 00:10:05.340 --> 00:10:08.290 align:start position:0% everything on the smart contract when you<00:10:05.460> have<00:10:05.840> arbitration<00:10:06.840> built<00:10:07.290> in<00:10:07.470> then 00:10:08.290 --> 00:10:08.300 align:start position:0% you have arbitration built in then 00:10:08.300 --> 00:10:11.480 align:start position:0% you have arbitration built in then instead<00:10:09.300> as<00:10:09.540> AI<00:10:09.660> describes<00:10:10.110> you<00:10:10.770> assume<00:10:11.460> that 00:10:11.480 --> 00:10:11.490 align:start position:0% instead as AI describes you assume that 00:10:11.490 --> 00:10:14.210 align:start position:0% instead as AI describes you assume that both<00:10:11.790> parties<00:10:12.240> are<00:10:12.390> acting<00:10:13.220> cooperatively 00:10:14.210 --> 00:10:14.220 align:start position:0% both parties are acting cooperatively 00:10:14.220 --> 00:10:16.340 align:start position:0% both parties are acting cooperatively and<00:10:14.460> correctly<00:10:14.940> but<00:10:15.420> you<00:10:15.540> have<00:10:15.690> the<00:10:15.840> mechanism 00:10:16.340 --> 00:10:16.350 align:start position:0% and correctly but you have the mechanism 00:10:16.350 --> 00:10:18.290 align:start position:0% and correctly but you have the mechanism in<00:10:16.440> place<00:10:16.470> for<00:10:17.280> a<00:10:17.310> dispute<00:10:17.730> resolution 00:10:18.290 --> 00:10:18.300 align:start position:0% in place for a dispute resolution 00:10:18.300 --> 00:10:22.040 align:start position:0% in place for a dispute resolution process<00:10:18.750> so<00:10:19.380> the<00:10:19.620> top<00:10:20.150> interaction<00:10:21.150> here<00:10:21.810> is 00:10:22.040 --> 00:10:22.050 align:start position:0% process so the top interaction here is 00:10:22.050 --> 00:10:24.410 align:start position:0% process so the top interaction here is where<00:10:22.350> the<00:10:22.440> user<00:10:22.940> through<00:10:23.940> the<00:10:24.150> smart 00:10:24.410 --> 00:10:24.420 align:start position:0% where the user through the smart 00:10:24.420 --> 00:10:26.870 align:start position:0% where the user through the smart contract<00:10:24.920> interacts<00:10:25.920> with<00:10:26.160> the<00:10:26.280> counterparty 00:10:26.870 --> 00:10:26.880 align:start position:0% contract interacts with the counterparty 00:10:26.880 --> 00:10:29.210 align:start position:0% contract interacts with the counterparty there's<00:10:27.630> not<00:10:27.870> any<00:10:28.050> execution<00:10:28.650> there's<00:10:29.040> really 00:10:29.210 --> 00:10:29.220 align:start position:0% there's not any execution there's really 00:10:29.220 --> 00:10:31.820 align:start position:0% there's not any execution there's really nothing<00:10:29.610> happening<00:10:30.060> there<00:10:30.270> there's<00:10:30.540> not<00:10:30.830> code 00:10:31.820 --> 00:10:31.830 align:start position:0% nothing happening there there's not code 00:10:31.830 --> 00:10:33.260 align:start position:0% nothing happening there there's not code that's<00:10:32.010> being<00:10:32.160> executed<00:10:32.460> on<00:10:32.790> chain<00:10:33.090> maybe 00:10:33.260 --> 00:10:33.270 align:start position:0% that's being executed on chain maybe 00:10:33.270 --> 00:10:35.600 align:start position:0% that's being executed on chain maybe just<00:10:33.540> a<00:10:33.630> hash<00:10:33.840> that's<00:10:34.290> stored<00:10:34.740> that<00:10:35.310> both 00:10:35.600 --> 00:10:35.610 align:start position:0% just a hash that's stored that both 00:10:35.610 --> 00:10:39.110 align:start position:0% just a hash that's stored that both parties<00:10:36.360> can<00:10:36.750> can<00:10:37.440> use<00:10:37.890> to<00:10:38.250> evaluate<00:10:38.580> off 00:10:39.110 --> 00:10:39.120 align:start position:0% parties can can use to evaluate off 00:10:39.120 --> 00:10:42.320 align:start position:0% parties can can use to evaluate off chain<00:10:39.540> what's<00:10:40.170> happening<00:10:40.680> so<00:10:41.100> user<00:10:41.520> a<00:10:41.670> maybe 00:10:42.320 --> 00:10:42.330 align:start position:0% chain what's happening so user a maybe 00:10:42.330 --> 00:10:45.140 align:start position:0% chain what's happening so user a maybe send<00:10:42.720> some<00:10:42.960> ether<00:10:43.350> to<00:10:43.650> the<00:10:43.770> contract<00:10:44.310> after<00:10:45.120> a 00:10:45.140 --> 00:10:45.150 align:start position:0% send some ether to the contract after a 00:10:45.150 --> 00:10:46.940 align:start position:0% send some ether to the contract after a certain<00:10:45.390> amount<00:10:45.660> of<00:10:45.780> time<00:10:46.020> the<00:10:46.320> counterparty 00:10:46.940 --> 00:10:46.950 align:start position:0% certain amount of time the counterparty 00:10:46.950 --> 00:10:49.250 align:start position:0% certain amount of time the counterparty is<00:10:46.980> expected<00:10:47.580> to<00:10:47.700> send<00:10:47.910> ether<00:10:48.240> back<00:10:48.480> or<00:10:48.840> some 00:10:49.250 --> 00:10:49.260 align:start position:0% is expected to send ether back or some 00:10:49.260 --> 00:10:51.710 align:start position:0% is expected to send ether back or some transaction<00:10:49.830> occurs<00:10:50.130> and<00:10:50.460> at<00:10:51.270> this<00:10:51.420> level 00:10:51.710 --> 00:10:51.720 align:start position:0% transaction occurs and at this level 00:10:51.720 --> 00:10:53.690 align:start position:0% transaction occurs and at this level it's<00:10:52.350> really<00:10:52.710> up<00:10:52.860> to<00:10:53.040> the<00:10:53.130> counterparty 00:10:53.690 --> 00:10:53.700 align:start position:0% it's really up to the counterparty 00:10:53.700 --> 00:10:57.440 align:start position:0% it's really up to the counterparty whether<00:10:53.880> they<00:10:54.060> want<00:10:54.270> to<00:10:54.330> do<00:10:54.450> that<00:10:54.600> or<00:10:54.750> not<00:10:56.450> now 00:10:57.440 --> 00:10:57.450 align:start position:0% whether they want to do that or not now 00:10:57.450 --> 00:10:59.780 align:start position:0% whether they want to do that or not now if<00:10:57.840> the<00:10:58.500> counterparty<00:10:59.040> doesn't<00:10:59.490> do<00:10:59.610> their 00:10:59.780 --> 00:10:59.790 align:start position:0% if the counterparty doesn't do their 00:10:59.790 --> 00:11:04.190 align:start position:0% if the counterparty doesn't do their part<00:11:00.320> you<00:11:01.320> have<00:11:01.560> a<00:11:01.890> time<00:11:02.520> window<00:11:02.790> a<00:11:03.270> week<00:11:03.900> a 00:11:04.190 --> 00:11:04.200 align:start position:0% part you have a time window a week a 00:11:04.200 --> 00:11:06.290 align:start position:0% part you have a time window a week a month<00:11:04.230> whatever<00:11:04.770> the<00:11:04.920> time<00:11:05.130> window<00:11:05.370> is<00:11:05.640> where 00:11:06.290 --> 00:11:06.300 align:start position:0% month whatever the time window is where 00:11:06.300 --> 00:11:10.190 align:start position:0% month whatever the time window is where the<00:11:06.690> user<00:11:06.990> can<00:11:08.060> file<00:11:09.060> a<00:11:09.270> dispute 00:11:10.190 --> 00:11:10.200 align:start position:0% the user can file a dispute 00:11:10.200 --> 00:11:11.990 align:start position:0% the user can file a dispute and<00:11:10.290> that's<00:11:10.440> all<00:11:10.620> on<00:11:10.860> chain<00:11:11.280> so<00:11:11.730> there's<00:11:11.940> a 00:11:11.990 --> 00:11:12.000 align:start position:0% and that's all on chain so there's a 00:11:12.000 --> 00:11:14.030 align:start position:0% and that's all on chain so there's a time<00:11:12.240> window<00:11:12.540> the<00:11:12.930> funds<00:11:13.170> are<00:11:13.350> locked<00:11:13.560> up<00:11:13.830> and 00:11:14.030 --> 00:11:14.040 align:start position:0% time window the funds are locked up and 00:11:14.040 --> 00:11:17.600 align:start position:0% time window the funds are locked up and so<00:11:14.820> imagine<00:11:15.240> user<00:11:15.660> B<00:11:16.020> has<00:11:16.710> a<00:11:16.740> problem<00:11:17.130> and<00:11:17.400> says 00:11:17.600 --> 00:11:17.610 align:start position:0% so imagine user B has a problem and says 00:11:17.610 --> 00:11:19.100 align:start position:0% so imagine user B has a problem and says yeah<00:11:17.820> the<00:11:17.940> counterparty<00:11:18.480> didn't<00:11:18.780> do<00:11:18.900> their 00:11:19.100 --> 00:11:19.110 align:start position:0% yeah the counterparty didn't do their 00:11:19.110 --> 00:11:23.480 align:start position:0% yeah the counterparty didn't do their job<00:11:19.140> so<00:11:20.130> they<00:11:20.340> send<00:11:20.960> a<00:11:21.960> dispute<00:11:22.890> resolution 00:11:23.480 --> 00:11:23.490 align:start position:0% job so they send a dispute resolution 00:11:23.490 --> 00:11:27.160 align:start position:0% job so they send a dispute resolution transaction<00:11:24.150> and<00:11:24.360> this<00:11:25.350> time<00:11:25.650> the<00:11:26.430> whatever 00:11:27.160 --> 00:11:27.170 align:start position:0% transaction and this time the whatever 00:11:27.170 --> 00:11:29.600 align:start position:0% transaction and this time the whatever business<00:11:28.170> logic<00:11:28.350> needed<00:11:28.830> to<00:11:28.920> be<00:11:29.010> executed 00:11:29.600 --> 00:11:29.610 align:start position:0% business logic needed to be executed 00:11:29.610 --> 00:11:31.910 align:start position:0% business logic needed to be executed which<00:11:29.790> could<00:11:29.970> be<00:11:30.060> quite<00:11:30.180> expensive<00:11:30.480> is<00:11:31.020> going 00:11:31.910 --> 00:11:31.920 align:start position:0% which could be quite expensive is going 00:11:31.920 --> 00:11:34.690 align:start position:0% which could be quite expensive is going to<00:11:32.070> be<00:11:32.190> fully<00:11:32.460> executed<00:11:33.180> and<00:11:33.360> because<00:11:34.140> it<00:11:34.470> is 00:11:34.690 --> 00:11:34.700 align:start position:0% to be fully executed and because it is 00:11:34.700 --> 00:11:38.600 align:start position:0% to be fully executed and because it is deterministic<00:11:35.810> the<00:11:36.810> winner<00:11:37.290> of<00:11:37.650> the<00:11:38.130> dispute 00:11:38.600 --> 00:11:38.610 align:start position:0% deterministic the winner of the dispute 00:11:38.610 --> 00:11:39.700 align:start position:0% deterministic the winner of the dispute will<00:11:38.820> always<00:11:39.180> win 00:11:39.700 --> 00:11:39.710 align:start position:0% will always win 00:11:39.710 --> 00:11:42.380 align:start position:0% will always win so<00:11:40.710> the<00:11:41.370> beauty<00:11:41.670> of<00:11:41.700> this<00:11:41.940> is<00:11:42.150> that<00:11:42.180> the 00:11:42.380 --> 00:11:42.390 align:start position:0% so the beauty of this is that the 00:11:42.390 --> 00:11:45.140 align:start position:0% so the beauty of this is that the incentivization<00:11:43.320> is<00:11:43.500> such<00:11:43.710> that<00:11:44.040> if<00:11:44.730> you<00:11:44.790> know 00:11:45.140 --> 00:11:45.150 align:start position:0% incentivization is such that if you know 00:11:45.150 --> 00:11:47.710 align:start position:0% incentivization is such that if you know you're<00:11:45.360> going<00:11:45.570> to<00:11:45.630> lose<00:11:45.960> you<00:11:46.470> you<00:11:46.830> would<00:11:47.010> never 00:11:47.710 --> 00:11:47.720 align:start position:0% you're going to lose you you would never 00:11:47.720 --> 00:11:50.360 align:start position:0% you're going to lose you you would never you<00:11:48.720> would<00:11:48.810> never<00:11:48.990> do<00:11:49.230> the<00:11:49.380> wrong<00:11:49.590> thing 00:11:50.360 --> 00:11:50.370 align:start position:0% you would never do the wrong thing 00:11:50.370 --> 00:11:52.700 align:start position:0% you would never do the wrong thing so<00:11:50.460> the<00:11:50.580> counterparty<00:11:51.270> has<00:11:51.840> zero<00:11:52.200> interest 00:11:52.700 --> 00:11:52.710 align:start position:0% so the counterparty has zero interest 00:11:52.710 --> 00:11:54.380 align:start position:0% so the counterparty has zero interest and<00:11:52.980> the<00:11:53.040> reason<00:11:53.340> you<00:11:53.460> you<00:11:53.730> force<00:11:54.330> that 00:11:54.380 --> 00:11:54.390 align:start position:0% and the reason you you force that 00:11:54.390 --> 00:11:56.960 align:start position:0% and the reason you you force that incentivization<00:11:55.410> to<00:11:55.860> be<00:11:55.980> aligned<00:11:56.310> so 00:11:56.960 --> 00:11:56.970 align:start position:0% incentivization to be aligned so 00:11:56.970 --> 00:12:01.010 align:start position:0% incentivization to be aligned so strictly<00:11:57.420> is<00:11:57.690> that<00:11:58.290> you<00:11:58.560> say<00:11:58.830> if<00:11:59.040> if<00:11:59.720> you<00:12:00.720> lose 00:12:01.010 --> 00:12:01.020 align:start position:0% strictly is that you say if if you lose 00:12:01.020 --> 00:12:02.810 align:start position:0% strictly is that you say if if you lose the<00:12:01.230> dispute<00:12:01.680> you<00:12:01.800> basically<00:12:02.190> lose<00:12:02.520> all<00:12:02.790> of 00:12:02.810 --> 00:12:02.820 align:start position:0% the dispute you basically lose all of 00:12:02.820 --> 00:12:05.210 align:start position:0% the dispute you basically lose all of your<00:12:03.030> money<00:12:03.330> right<00:12:03.870> so<00:12:04.050> you<00:12:04.110> punish<00:12:04.620> the 00:12:05.210 --> 00:12:05.220 align:start position:0% your money right so you punish the 00:12:05.220 --> 00:12:08.900 align:start position:0% your money right so you punish the person<00:12:05.460> for<00:12:06.470> behaving<00:12:07.470> against<00:12:08.130> the<00:12:08.310> expected 00:12:08.900 --> 00:12:08.910 align:start position:0% person for behaving against the expected 00:12:08.910 --> 00:12:12.020 align:start position:0% person for behaving against the expected the<00:12:09.660> expected<00:12:10.200> behavior<00:12:10.650> and<00:12:10.860> so<00:12:11.310> when<00:12:11.760> done 00:12:12.020 --> 00:12:12.030 align:start position:0% the expected behavior and so when done 00:12:12.030 --> 00:12:14.240 align:start position:0% the expected behavior and so when done right<00:12:12.060> there's<00:12:12.810> really<00:12:13.020> no<00:12:13.290> incentive<00:12:13.830> to<00:12:13.860> go 00:12:14.240 --> 00:12:14.250 align:start position:0% right there's really no incentive to go 00:12:14.250 --> 00:12:16.190 align:start position:0% right there's really no incentive to go against<00:12:14.520> the<00:12:14.640> expected<00:12:15.090> behavior<00:12:15.540> you<00:12:16.050> have 00:12:16.190 --> 00:12:16.200 align:start position:0% against the expected behavior you have 00:12:16.200 --> 00:12:20.060 align:start position:0% against the expected behavior you have user<00:12:16.470> a<00:12:16.800> acting<00:12:18.530> expecting<00:12:19.530> a<00:12:19.620> certain<00:12:19.800> thing 00:12:20.060 --> 00:12:20.070 align:start position:0% user a acting expecting a certain thing 00:12:20.070 --> 00:12:21.920 align:start position:0% user a acting expecting a certain thing back<00:12:20.250> from<00:12:20.580> the<00:12:21.090> counterparty<00:12:21.690> of<00:12:21.840> the 00:12:21.920 --> 00:12:21.930 align:start position:0% back from the counterparty of the 00:12:21.930 --> 00:12:24.050 align:start position:0% back from the counterparty of the counterparty<00:12:22.230> doing<00:12:22.740> their<00:12:22.890> job<00:12:23.130> the<00:12:23.730> threat 00:12:24.050 --> 00:12:24.060 align:start position:0% counterparty doing their job the threat 00:12:24.060 --> 00:12:26.890 align:start position:0% counterparty doing their job the threat of<00:12:24.330> the<00:12:24.570> dispute<00:12:25.050> resolution<00:12:25.080> process 00:12:26.890 --> 00:12:26.900 align:start position:0% of the dispute resolution process 00:12:26.900 --> 00:12:29.840 align:start position:0% of the dispute resolution process incentivizes<00:12:27.900> the<00:12:28.020> counterparty<00:12:28.620> to<00:12:28.850> do 00:12:29.840 --> 00:12:29.850 align:start position:0% incentivizes the counterparty to do 00:12:29.850 --> 00:12:31.910 align:start position:0% incentivizes the counterparty to do their<00:12:30.030> part<00:12:30.060> and<00:12:30.660> the<00:12:31.290> beauty<00:12:31.560> here<00:12:31.830> is<00:12:31.860> that 00:12:31.910 --> 00:12:31.920 align:start position:0% their part and the beauty here is that 00:12:31.920 --> 00:12:35.210 align:start position:0% their part and the beauty here is that you're<00:12:32.160> not<00:12:32.340> actually<00:12:33.050> executing<00:12:34.050> the<00:12:34.860> full 00:12:35.210 --> 00:12:35.220 align:start position:0% you're not actually executing the full 00:12:35.220 --> 00:12:38.720 align:start position:0% you're not actually executing the full contract<00:12:35.790> logic<00:12:36.330> on<00:12:36.510> chain<00:12:36.980> it's<00:12:37.980> just<00:12:38.280> user<00:12:38.550> a 00:12:38.720 --> 00:12:38.730 align:start position:0% contract logic on chain it's just user a 00:12:38.730 --> 00:12:41.000 align:start position:0% contract logic on chain it's just user a doing<00:12:39.420> their<00:12:39.600> thing<00:12:39.870> and<00:12:40.080> the<00:12:40.440> counterparty 00:12:41.000 --> 00:12:41.010 align:start position:0% doing their thing and the counterparty 00:12:41.010 --> 00:12:44.180 align:start position:0% doing their thing and the counterparty doing<00:12:41.280> their<00:12:41.460> thing<00:12:41.700> so<00:12:42.540> I<00:12:42.840> see<00:12:43.200> this<00:12:43.410> as<00:12:43.590> a 00:12:44.180 --> 00:12:44.190 align:start position:0% doing their thing so I see this as a 00:12:44.190 --> 00:12:46.040 align:start position:0% doing their thing so I see this as a potentially<00:12:44.910> huge<00:12:45.240> pattern<00:12:45.540> that<00:12:45.840> can<00:12:45.990> be 00:12:46.040 --> 00:12:46.050 align:start position:0% potentially huge pattern that can be 00:12:46.050 --> 00:12:49.670 align:start position:0% potentially huge pattern that can be used<00:12:46.410> across<00:12:47.210> smart<00:12:48.210> contracts<00:12:48.780> in<00:12:49.110> order<00:12:49.380> to 00:12:49.670 --> 00:12:49.680 align:start position:0% used across smart contracts in order to 00:12:49.680 --> 00:12:53.690 align:start position:0% used across smart contracts in order to optimize<00:12:50.460> reduce<00:12:51.240> execution<00:12:51.930> time<00:12:52.170> and<00:12:52.700> this 00:12:53.690 --> 00:12:53.700 align:start position:0% optimize reduce execution time and this 00:12:53.700 --> 00:12:54.860 align:start position:0% optimize reduce execution time and this is<00:12:53.850> something<00:12:54.150> that<00:12:54.180> could<00:12:54.420> be<00:12:54.540> put<00:12:54.720> to<00:12:54.750> good 00:12:54.860 --> 00:12:54.870 align:start position:0% is something that could be put to good 00:12:54.870 --> 00:12:58.580 align:start position:0% is something that could be put to good effect<00:12:55.110> on<00:12:55.380> a<00:12:55.500> lot<00:12:55.530> of<00:12:55.770> projects<00:12:56.570> okay<00:12:57.590> how's 00:12:58.580 --> 00:12:58.590 align:start position:0% effect on a lot of projects okay how's 00:12:58.590 --> 00:13:01.160 align:start position:0% effect on a lot of projects okay how's everybody<00:12:59.130> doing<00:12:59.520> you<00:12:59.610> still<00:12:59.850> with<00:12:59.970> me<00:13:00.170> the 00:13:01.160 --> 00:13:01.170 align:start position:0% everybody doing you still with me the 00:13:01.170 --> 00:13:03.140 align:start position:0% everybody doing you still with me the developers<00:13:01.770> are<00:13:01.980> the<00:13:02.340> developers<00:13:02.850> are<00:13:03.000> like 00:13:03.140 --> 00:13:03.150 align:start position:0% developers are the developers are like 00:13:03.150 --> 00:13:07.760 align:start position:0% developers are the developers are like yeah<00:13:03.360> this<00:13:03.630> is<00:13:03.690> cool<00:13:04.110> okay<00:13:06.110> so<00:13:07.110> we<00:13:07.440> have<00:13:07.620> some 00:13:07.760 --> 00:13:07.770 align:start position:0% yeah this is cool okay so we have some 00:13:07.770 --> 00:13:09.500 align:start position:0% yeah this is cool okay so we have some higher-level<00:13:08.010> patterns<00:13:08.670> and<00:13:08.850> these<00:13:08.970> are<00:13:09.270> for 00:13:09.500 --> 00:13:09.510 align:start position:0% higher-level patterns and these are for 00:13:09.510 --> 00:13:10.970 align:start position:0% higher-level patterns and these are for you<00:13:09.540> as<00:13:09.810> well<00:13:09.990> these<00:13:10.260> are<00:13:10.320> also<00:13:10.620> for 00:13:10.970 --> 00:13:10.980 align:start position:0% you as well these are also for 00:13:10.980 --> 00:13:13.610 align:start position:0% you as well these are also for developers<00:13:11.520> if<00:13:11.730> you<00:13:12.300> spend<00:13:12.720> more<00:13:13.320> than<00:13:13.380> a 00:13:13.610 --> 00:13:13.620 align:start position:0% developers if you spend more than a 00:13:13.620 --> 00:13:16.340 align:start position:0% developers if you spend more than a couple<00:13:13.860> years<00:13:14.090> working<00:13:15.090> in<00:13:15.570> the<00:13:15.930> software 00:13:16.340 --> 00:13:16.350 align:start position:0% couple years working in the software 00:13:16.350 --> 00:13:18.950 align:start position:0% couple years working in the software industry<00:13:16.650> I<00:13:17.250> hate<00:13:18.090> to<00:13:18.240> break<00:13:18.390> it<00:13:18.450> to<00:13:18.600> you<00:13:18.780> but 00:13:18.950 --> 00:13:18.960 align:start position:0% industry I hate to break it to you but 00:13:18.960 --> 00:13:21.050 align:start position:0% industry I hate to break it to you but you're<00:13:19.110> gonna<00:13:19.170> have<00:13:19.500> to<00:13:19.560> do<00:13:20.550> some<00:13:20.820> things 00:13:21.050 --> 00:13:21.060 align:start position:0% you're gonna have to do some things 00:13:21.060 --> 00:13:23.360 align:start position:0% you're gonna have to do some things other<00:13:21.300> than<00:13:21.420> coding<00:13:21.960> you're<00:13:22.860> gonna<00:13:22.980> have<00:13:23.220> to 00:13:23.360 --> 00:13:23.370 align:start position:0% other than coding you're gonna have to 00:13:23.370 --> 00:13:23.600 align:start position:0% other than coding you're gonna have to learn 00:13:23.600 --> 00:13:23.610 align:start position:0% learn 00:13:23.610 --> 00:13:25.610 align:start position:0% learn some<00:13:23.760> other<00:13:23.910> skills<00:13:24.209> and<00:13:24.510> some<00:13:25.230> of<00:13:25.380> those<00:13:25.470> are 00:13:25.610 --> 00:13:25.620 align:start position:0% some other skills and some of those are 00:13:25.620 --> 00:13:27.410 align:start position:0% some other skills and some of those are going<00:13:25.649> to<00:13:25.800> be<00:13:25.920> technical<00:13:26.459> skills<00:13:26.820> and<00:13:27.089> some<00:13:27.300> of 00:13:27.410 --> 00:13:27.420 align:start position:0% going to be technical skills and some of 00:13:27.420 --> 00:13:29.389 align:start position:0% going to be technical skills and some of those<00:13:27.570> are<00:13:27.810> less<00:13:27.930> technical<00:13:28.560> but<00:13:29.070> what<00:13:29.279> are 00:13:29.389 --> 00:13:29.399 align:start position:0% those are less technical but what are 00:13:29.399 --> 00:13:31.040 align:start position:0% those are less technical but what are the<00:13:29.490> higher-level<00:13:29.760> patterns<00:13:30.510> that<00:13:30.750> allow<00:13:30.870> you 00:13:31.040 --> 00:13:31.050 align:start position:0% the higher-level patterns that allow you 00:13:31.050 --> 00:13:33.050 align:start position:0% the higher-level patterns that allow you to<00:13:31.170> be<00:13:31.320> successful<00:13:31.350> as<00:13:32.220> a<00:13:32.279> smart<00:13:32.910> contract 00:13:33.050 --> 00:13:33.060 align:start position:0% to be successful as a smart contract 00:13:33.060 --> 00:13:35.600 align:start position:0% to be successful as a smart contract developer<00:13:33.899> not<00:13:34.560> just<00:13:35.010> when<00:13:35.279> you're<00:13:35.310> in 00:13:35.600 --> 00:13:35.610 align:start position:0% developer not just when you're in 00:13:35.610 --> 00:13:37.819 align:start position:0% developer not just when you're in solidity<00:13:36.180> land<00:13:36.630> but<00:13:37.380> when<00:13:37.529> you're<00:13:37.680> working 00:13:37.819 --> 00:13:37.829 align:start position:0% solidity land but when you're working 00:13:37.829 --> 00:13:40.009 align:start position:0% solidity land but when you're working with<00:13:38.160> your<00:13:38.310> team<00:13:38.600> when<00:13:39.600> you're<00:13:39.750> making 00:13:40.009 --> 00:13:40.019 align:start position:0% with your team when you're making 00:13:40.019 --> 00:13:42.710 align:start position:0% with your team when you're making judgment<00:13:40.470> calls<00:13:40.790> when<00:13:41.790> you're<00:13:42.000> making 00:13:42.710 --> 00:13:42.720 align:start position:0% judgment calls when you're making 00:13:42.720 --> 00:13:45.440 align:start position:0% judgment calls when you're making important<00:13:43.649> decisions<00:13:43.680> about<00:13:44.550> the<00:13:45.029> direction 00:13:45.440 --> 00:13:45.450 align:start position:0% important decisions about the direction 00:13:45.450 --> 00:13:47.780 align:start position:0% important decisions about the direction of<00:13:45.510> your<00:13:45.660> product<00:13:46.110> that<00:13:46.920> the<00:13:47.339> rest<00:13:47.519> of<00:13:47.670> your 00:13:47.780 --> 00:13:47.790 align:start position:0% of your product that the rest of your 00:13:47.790 --> 00:13:53.680 align:start position:0% of your product that the rest of your team<00:13:48.029> is<00:13:48.209> looking<00:13:48.390> to<00:13:48.600> you<00:13:48.899> for<00:13:50.870> so<00:13:51.870> one<00:13:52.709> is 00:13:53.680 --> 00:13:53.690 align:start position:0% team is looking to you for so one is 00:13:53.690 --> 00:13:57.079 align:start position:0% team is looking to you for so one is something<00:13:54.690> that<00:13:54.990> I<00:13:55.230> call<00:13:55.410> role<00:13:55.850> analysis<00:13:56.850> this 00:13:57.079 --> 00:13:57.089 align:start position:0% something that I call role analysis this 00:13:57.089 --> 00:14:00.079 align:start position:0% something that I call role analysis this isn't<00:13:57.630> a<00:13:57.690> technical<00:13:57.990> term<00:13:58.350> but<00:13:58.920> role<00:13:59.490> analysis 00:14:00.079 --> 00:14:00.089 align:start position:0% isn't a technical term but role analysis 00:14:00.089 --> 00:14:02.540 align:start position:0% isn't a technical term but role analysis how<00:14:00.269> do<00:14:00.329> you<00:14:00.510> analyze<00:14:01.019> the<00:14:01.320> roles<00:14:01.589> in<00:14:01.980> the 00:14:02.540 --> 00:14:02.550 align:start position:0% how do you analyze the roles in the 00:14:02.550 --> 00:14:04.940 align:start position:0% how do you analyze the roles in the smart<00:14:02.850> contract<00:14:03.329> and<00:14:03.540> this<00:14:03.660> is<00:14:03.950> something 00:14:04.940 --> 00:14:04.950 align:start position:0% smart contract and this is something 00:14:04.950 --> 00:14:07.519 align:start position:0% smart contract and this is something that<00:14:05.250> you<00:14:05.399> can<00:14:05.579> use<00:14:05.940> this<00:14:06.600> this<00:14:06.930> is<00:14:07.110> simply<00:14:07.410> an 00:14:07.519 --> 00:14:07.529 align:start position:0% that you can use this this is simply an 00:14:07.529 --> 00:14:09.199 align:start position:0% that you can use this this is simply an approach<00:14:07.860> to<00:14:08.070> smart<00:14:08.339> contract<00:14:08.760> development 00:14:09.199 --> 00:14:09.209 align:start position:0% approach to smart contract development 00:14:09.209 --> 00:14:11.150 align:start position:0% approach to smart contract development and<00:14:09.300> design<00:14:09.600> and<00:14:09.959> you<00:14:10.620> can<00:14:10.769> use<00:14:10.890> it<00:14:11.010> at<00:14:11.130> any 00:14:11.150 --> 00:14:11.160 align:start position:0% and design and you can use it at any 00:14:11.160 --> 00:14:13.370 align:start position:0% and design and you can use it at any stage<00:14:11.700> of<00:14:11.850> the<00:14:11.910> process<00:14:12.170> so<00:14:13.170> if<00:14:13.260> you're 00:14:13.370 --> 00:14:13.380 align:start position:0% stage of the process so if you're 00:14:13.380 --> 00:14:15.730 align:start position:0% stage of the process so if you're designing<00:14:13.560> a<00:14:13.950> smart<00:14:14.190> contract<00:14:14.339> from<00:14:14.940> scratch 00:14:15.730 --> 00:14:15.740 align:start position:0% designing a smart contract from scratch 00:14:15.740 --> 00:14:18.970 align:start position:0% designing a smart contract from scratch who<00:14:16.740> is<00:14:17.130> interacting<00:14:18.029> with<00:14:18.510> the<00:14:18.630> system 00:14:18.970 --> 00:14:18.980 align:start position:0% who is interacting with the system 00:14:18.980 --> 00:14:21.259 align:start position:0% who is interacting with the system that's<00:14:19.980> the<00:14:20.190> main<00:14:20.370> question<00:14:20.550> you're<00:14:20.910> asking 00:14:21.259 --> 00:14:21.269 align:start position:0% that's the main question you're asking 00:14:21.269 --> 00:14:24.199 align:start position:0% that's the main question you're asking here<00:14:22.130> who<00:14:23.130> is<00:14:23.250> interacting<00:14:23.550> with<00:14:23.940> the<00:14:24.060> system 00:14:24.199 --> 00:14:24.209 align:start position:0% here who is interacting with the system 00:14:24.209 --> 00:14:27.550 align:start position:0% here who is interacting with the system and<00:14:24.950> what<00:14:25.950> are<00:14:26.070> their<00:14:26.279> incentives<00:14:26.940> and<00:14:27.180> how 00:14:27.550 --> 00:14:27.560 align:start position:0% and what are their incentives and how 00:14:27.560 --> 00:14:29.960 align:start position:0% and what are their incentives and how does<00:14:28.560> the<00:14:28.740> behavior<00:14:29.100> how<00:14:29.640> are<00:14:29.790> their 00:14:29.960 --> 00:14:29.970 align:start position:0% does the behavior how are their 00:14:29.970 --> 00:14:33.250 align:start position:0% does the behavior how are their behaviors<00:14:30.570> going<00:14:31.380> to<00:14:31.500> derive<00:14:31.829> from<00:14:31.860> the 00:14:33.250 --> 00:14:33.260 align:start position:0% behaviors going to derive from the 00:14:33.260 --> 00:14:36.230 align:start position:0% behaviors going to derive from the functions<00:14:34.260> that<00:14:34.740> you<00:14:35.160> exposed<00:14:35.820> to<00:14:36.060> these 00:14:36.230 --> 00:14:36.240 align:start position:0% functions that you exposed to these 00:14:36.240 --> 00:14:39.079 align:start position:0% functions that you exposed to these different<00:14:36.660> roles<00:14:36.810> so<00:14:37.140> I<00:14:38.100> use<00:14:38.459> this<00:14:38.670> both<00:14:38.880> in 00:14:39.079 --> 00:14:39.089 align:start position:0% different roles so I use this both in 00:14:39.089 --> 00:14:41.360 align:start position:0% different roles so I use this both in the<00:14:39.540> design<00:14:39.690> process<00:14:40.410> but<00:14:40.560> I<00:14:40.620> also<00:14:40.890> use<00:14:41.190> this 00:14:41.360 --> 00:14:41.370 align:start position:0% the design process but I also use this 00:14:41.370 --> 00:14:43.790 align:start position:0% the design process but I also use this throughout<00:14:41.579> the<00:14:41.790> entire<00:14:41.820> career<00:14:42.630> of<00:14:42.899> the 00:14:43.790 --> 00:14:43.800 align:start position:0% throughout the entire career of the 00:14:43.800 --> 00:14:46.009 align:start position:0% throughout the entire career of the smart<00:14:44.070> contract<00:14:44.519> system<00:14:44.899> when<00:14:45.899> you're 00:14:46.009 --> 00:14:46.019 align:start position:0% smart contract system when you're 00:14:46.019 --> 00:14:47.620 align:start position:0% smart contract system when you're iterating<00:14:46.649> and<00:14:46.740> you're<00:14:46.890> adding<00:14:47.010> new<00:14:47.220> features 00:14:47.620 --> 00:14:47.630 align:start position:0% iterating and you're adding new features 00:14:47.630 --> 00:14:50.750 align:start position:0% iterating and you're adding new features there's<00:14:48.630> always<00:14:48.959> going<00:14:49.320> to<00:14:49.440> be<00:14:49.760> adjustments 00:14:50.750 --> 00:14:50.760 align:start position:0% there's always going to be adjustments 00:14:50.760 --> 00:14:53.269 align:start position:0% there's always going to be adjustments to<00:14:50.910> the<00:14:51.000> behaviors<00:14:51.630> of<00:14:52.019> the<00:14:52.620> different<00:14:53.040> users 00:14:53.269 --> 00:14:53.279 align:start position:0% to the behaviors of the different users 00:14:53.279 --> 00:14:55.490 align:start position:0% to the behaviors of the different users and<00:14:53.790> the<00:14:54.000> different<00:14:54.329> roles<00:14:54.540> that<00:14:54.899> are 00:14:55.490 --> 00:14:55.500 align:start position:0% and the different roles that are 00:14:55.500 --> 00:14:58.579 align:start position:0% and the different roles that are interacting<00:14:56.490> with<00:14:56.610> your<00:14:56.730> system<00:14:57.120> so<00:14:57.990> to<00:14:58.019> be<00:14:58.560> a 00:14:58.579 --> 00:14:58.589 align:start position:0% interacting with your system so to be a 00:14:58.589 --> 00:15:01.069 align:start position:0% interacting with your system so to be a really<00:14:59.160> good<00:14:59.370> smart<00:14:59.699> contract<00:15:00.180> developer<00:15:00.750> you 00:15:01.069 --> 00:15:01.079 align:start position:0% really good smart contract developer you 00:15:01.079 --> 00:15:04.150 align:start position:0% really good smart contract developer you have<00:15:01.110> to<00:15:01.709> understand<00:15:02.310> all<00:15:02.940> of<00:15:03.360> the<00:15:03.480> roles<00:15:03.720> of 00:15:04.150 --> 00:15:04.160 align:start position:0% have to understand all of the roles of 00:15:04.160 --> 00:15:05.990 align:start position:0% have to understand all of the roles of individuals<00:15:05.160> interacting<00:15:05.730> with<00:15:05.880> your 00:15:05.990 --> 00:15:06.000 align:start position:0% individuals interacting with your 00:15:06.000 --> 00:15:08.810 align:start position:0% individuals interacting with your contract<00:15:06.449> what<00:15:07.380> their<00:15:07.620> different<00:15:08.070> incentives 00:15:08.810 --> 00:15:08.820 align:start position:0% contract what their different incentives 00:15:08.820 --> 00:15:11.449 align:start position:0% contract what their different incentives are<00:15:08.970> and<00:15:09.269> how<00:15:10.199> that<00:15:10.230> affects<00:15:10.860> the<00:15:11.430> overall 00:15:11.449 --> 00:15:11.459 align:start position:0% are and how that affects the overall 00:15:11.459 --> 00:15:13.490 align:start position:0% are and how that affects the overall functioning<00:15:12.300> of<00:15:12.420> the<00:15:12.540> system<00:15:12.690> right<00:15:13.199> this<00:15:13.350> is 00:15:13.490 --> 00:15:13.500 align:start position:0% functioning of the system right this is 00:15:13.500 --> 00:15:15.350 align:start position:0% functioning of the system right this is like<00:15:13.680> the<00:15:13.800> essence<00:15:14.220> of<00:15:14.370> the<00:15:14.550> game<00:15:15.029> theoretic 00:15:15.350 --> 00:15:15.360 align:start position:0% like the essence of the game theoretic 00:15:15.360 --> 00:15:18.199 align:start position:0% like the essence of the game theoretic nature<00:15:15.990> of<00:15:16.490> decentralized<00:15:17.490> smart<00:15:17.760> contracts 00:15:18.199 --> 00:15:18.209 align:start position:0% nature of decentralized smart contracts 00:15:18.209 --> 00:15:21.259 align:start position:0% nature of decentralized smart contracts so<00:15:18.390> just<00:15:18.660> some<00:15:18.839> examples<00:15:19.440> the<00:15:20.310> prism<00:15:20.730> contract 00:15:21.259 --> 00:15:21.269 align:start position:0% so just some examples the prism contract 00:15:21.269 --> 00:15:24.500 align:start position:0% so just some examples the prism contract for<00:15:21.800> shapeshift<00:15:22.800> prism<00:15:23.190> has<00:15:23.610> a<00:15:24.060> few<00:15:24.269> simple 00:15:24.500 --> 00:15:24.510 align:start position:0% for shapeshift prism has a few simple 00:15:24.510 --> 00:15:27.230 align:start position:0% for shapeshift prism has a few simple roles<00:15:24.839> it<00:15:25.050> has<00:15:25.170> a<00:15:25.199> buyer<00:15:25.529> a<00:15:25.890> seller<00:15:26.519> and<00:15:26.850> an 00:15:27.230 --> 00:15:27.240 align:start position:0% roles it has a buyer a seller and an 00:15:27.240 --> 00:15:31.960 align:start position:0% roles it has a buyer a seller and an Oracle<00:15:27.690> and<00:15:28.940> with<00:15:29.940> prism<00:15:30.390> the<00:15:30.810> buyer 00:15:31.960 --> 00:15:31.970 align:start position:0% Oracle and with prism the buyer 00:15:31.970 --> 00:15:36.350 align:start position:0% Oracle and with prism the buyer purchases<00:15:32.970> a<00:15:34.490> contract<00:15:35.490> a<00:15:35.670> portfolio<00:15:36.270> of 00:15:36.350 --> 00:15:36.360 align:start position:0% purchases a contract a portfolio of 00:15:36.360 --> 00:15:37.430 align:start position:0% purchases a contract a portfolio of different<00:15:36.660> digital 00:15:37.430 --> 00:15:37.440 align:start position:0% different digital 00:15:37.440 --> 00:15:39.590 align:start position:0% different digital sets<00:15:37.740> the<00:15:38.520> seller<00:15:38.790> is<00:15:38.970> putting<00:15:39.270> up<00:15:39.390> collateral 00:15:39.590 --> 00:15:39.600 align:start position:0% sets the seller is putting up collateral 00:15:39.600 --> 00:15:43.490 align:start position:0% sets the seller is putting up collateral to<00:15:40.530> ensure<00:15:40.890> that<00:15:41.280> those<00:15:41.730> assets<00:15:42.360> can<00:15:42.690> be<00:15:43.290> paid 00:15:43.490 --> 00:15:43.500 align:start position:0% to ensure that those assets can be paid 00:15:43.500 --> 00:15:44.900 align:start position:0% to ensure that those assets can be paid off<00:15:43.530> depending<00:15:44.190> on<00:15:44.280> whether<00:15:44.520> the<00:15:44.700> portfolio 00:15:44.900 --> 00:15:44.910 align:start position:0% off depending on whether the portfolio 00:15:44.910 --> 00:15:47.750 align:start position:0% off depending on whether the portfolio goes<00:15:45.480> up<00:15:45.660> or<00:15:45.810> down<00:15:45.840> and<00:15:46.320> then<00:15:47.040> the<00:15:47.130> Oracle<00:15:47.610> is 00:15:47.750 --> 00:15:47.760 align:start position:0% goes up or down and then the Oracle is 00:15:47.760 --> 00:15:49.820 align:start position:0% goes up or down and then the Oracle is another<00:15:48.090> entity<00:15:48.450> that's<00:15:48.870> providing<00:15:49.620> the 00:15:49.820 --> 00:15:49.830 align:start position:0% another entity that's providing the 00:15:49.830 --> 00:15:52.370 align:start position:0% another entity that's providing the prices<00:15:50.310> that<00:15:51.210> determines<00:15:51.750> the<00:15:51.870> value<00:15:51.990> of<00:15:52.290> the 00:15:52.370 --> 00:15:52.380 align:start position:0% prices that determines the value of the 00:15:52.380 --> 00:15:56.120 align:start position:0% prices that determines the value of the portfolio<00:15:53.000> so<00:15:54.000> different<00:15:54.510> roles<00:15:54.750> and<00:15:55.130> even 00:15:56.120 --> 00:15:56.130 align:start position:0% portfolio so different roles and even 00:15:56.130 --> 00:15:58.010 align:start position:0% portfolio so different roles and even these<00:15:56.250> simple<00:15:56.460> three<00:15:56.910> roles<00:15:57.180> have<00:15:57.480> involved<00:15:57.930> a 00:15:58.010 --> 00:15:58.020 align:start position:0% these simple three roles have involved a 00:15:58.020 --> 00:16:00.740 align:start position:0% these simple three roles have involved a high<00:15:58.200> level<00:15:58.710> a<00:15:58.950> high<00:15:59.430> degree<00:15:59.610> of<00:15:59.820> analysis<00:16:00.510> on 00:16:00.740 --> 00:16:00.750 align:start position:0% high level a high degree of analysis on 00:16:00.750 --> 00:16:03.410 align:start position:0% high level a high degree of analysis on ongoing<00:16:01.140> analysis<00:16:02.070> to<00:16:02.580> make<00:16:02.790> sure<00:16:03.060> that<00:16:03.300> the 00:16:03.410 --> 00:16:03.420 align:start position:0% ongoing analysis to make sure that the 00:16:03.420 --> 00:16:06.290 align:start position:0% ongoing analysis to make sure that the trust<00:16:03.720> implications<00:16:04.500> are<00:16:04.830> well<00:16:05.640> understood 00:16:06.290 --> 00:16:06.300 align:start position:0% trust implications are well understood 00:16:06.300 --> 00:16:09.080 align:start position:0% trust implications are well understood as<00:16:06.570> the<00:16:07.200> contract<00:16:07.740> develops<00:16:08.640> and<00:16:08.820> becomes 00:16:09.080 --> 00:16:09.090 align:start position:0% as the contract develops and becomes 00:16:09.090 --> 00:16:12.650 align:start position:0% as the contract develops and becomes more<00:16:09.300> sophisticated<00:16:10.130> another<00:16:11.130> example<00:16:11.850> is<00:16:12.060> a 00:16:12.650 --> 00:16:12.660 align:start position:0% more sophisticated another example is a 00:16:12.660 --> 00:16:14.870 align:start position:0% more sophisticated another example is a salt<00:16:13.020> loan<00:16:13.470> let's<00:16:13.950> say<00:16:14.130> you<00:16:14.190> were<00:16:14.400> doing<00:16:14.430> a 00:16:14.870 --> 00:16:14.880 align:start position:0% salt loan let's say you were doing a 00:16:14.880 --> 00:16:19.280 align:start position:0% salt loan let's say you were doing a loan<00:16:15.480> that<00:16:15.900> was<00:16:16.200> backed<00:16:16.980> by<00:16:17.810> by<00:16:18.810> digital 00:16:19.280 --> 00:16:19.290 align:start position:0% loan that was backed by by digital 00:16:19.290 --> 00:16:20.750 align:start position:0% loan that was backed by by digital assets<00:16:19.740> that<00:16:19.890> was<00:16:20.010> collateralized<00:16:20.640> by 00:16:20.750 --> 00:16:20.760 align:start position:0% assets that was collateralized by 00:16:20.760 --> 00:16:22.370 align:start position:0% assets that was collateralized by digital<00:16:21.150> assets<00:16:21.540> in<00:16:21.720> this<00:16:21.840> case<00:16:22.050> you<00:16:22.200> have<00:16:22.290> a 00:16:22.370 --> 00:16:22.380 align:start position:0% digital assets in this case you have a 00:16:22.380 --> 00:16:24.920 align:start position:0% digital assets in this case you have a borrower<00:16:22.760> someone<00:16:23.760> who's<00:16:23.910> borrowing<00:16:24.240> cash 00:16:24.920 --> 00:16:24.930 align:start position:0% borrower someone who's borrowing cash 00:16:24.930 --> 00:16:26.750 align:start position:0% borrower someone who's borrowing cash and<00:16:25.380> then<00:16:25.770> you<00:16:25.890> have<00:16:26.010> a<00:16:26.040> lender<00:16:26.520> who's 00:16:26.750 --> 00:16:26.760 align:start position:0% and then you have a lender who's 00:16:26.760 --> 00:16:29.480 align:start position:0% and then you have a lender who's offering<00:16:27.600> that<00:16:27.780> cash<00:16:28.020> but<00:16:28.380> then<00:16:28.560> locking<00:16:29.160> up 00:16:29.480 --> 00:16:29.490 align:start position:0% offering that cash but then locking up 00:16:29.490 --> 00:16:31.760 align:start position:0% offering that cash but then locking up the<00:16:29.730> collateral<00:16:30.270> and<00:16:30.450> in<00:16:31.050> this<00:16:31.170> case<00:16:31.440> you<00:16:31.590> have 00:16:31.760 --> 00:16:31.770 align:start position:0% the collateral and in this case you have 00:16:31.770 --> 00:16:36.170 align:start position:0% the collateral and in this case you have salt<00:16:32.100> as<00:16:32.280> a<00:16:32.310> kind<00:16:32.700> of<00:16:33.830> multi-sig<00:16:35.150> arbiter<00:16:36.150> to 00:16:36.170 --> 00:16:36.180 align:start position:0% salt as a kind of multi-sig arbiter to 00:16:36.180 --> 00:16:38.900 align:start position:0% salt as a kind of multi-sig arbiter to make<00:16:36.570> sure<00:16:36.810> that<00:16:37.200> if<00:16:37.500> anything<00:16:37.890> funky<00:16:38.550> happens 00:16:38.900 --> 00:16:38.910 align:start position:0% make sure that if anything funky happens 00:16:38.910 --> 00:16:40.610 align:start position:0% make sure that if anything funky happens with<00:16:39.060> the<00:16:39.150> other<00:16:39.300> two<00:16:39.570> salt<00:16:39.960> is<00:16:40.110> in<00:16:40.140> there<00:16:40.440> and 00:16:40.610 --> 00:16:40.620 align:start position:0% with the other two salt is in there and 00:16:40.620 --> 00:16:44.870 align:start position:0% with the other two salt is in there and can<00:16:41.570> have<00:16:42.570> the<00:16:42.720> last<00:16:42.930> word<00:16:43.640> this<00:16:44.640> is<00:16:44.760> an 00:16:44.870 --> 00:16:44.880 align:start position:0% can have the last word this is an 00:16:44.880 --> 00:16:49.010 align:start position:0% can have the last word this is an example<00:16:45.180> from<00:16:45.510> a<00:16:45.630> talk<00:16:45.960> yesterday<00:16:47.660> the<00:16:48.660> liquid 00:16:49.010 --> 00:16:49.020 align:start position:0% example from a talk yesterday the liquid 00:16:49.020 --> 00:16:51.860 align:start position:0% example from a talk yesterday the liquid pledging<00:16:49.610> contract<00:16:50.610> was<00:16:50.880> really<00:16:51.210> I<00:16:51.390> thought 00:16:51.860 --> 00:16:51.870 align:start position:0% pledging contract was really I thought 00:16:51.870 --> 00:16:55.700 align:start position:0% pledging contract was really I thought really<00:16:52.080> a<00:16:52.440> brilliant<00:16:52.800> idea<00:16:53.580> to<00:16:54.110> combine<00:16:55.110> fund 00:16:55.700 --> 00:16:55.710 align:start position:0% really a brilliant idea to combine fund 00:16:55.710 --> 00:17:00.050 align:start position:0% really a brilliant idea to combine fund management<00:16:56.250> with<00:16:57.380> liquid<00:16:58.380> democracy<00:16:59.340> and 00:17:00.050 --> 00:17:00.060 align:start position:0% management with liquid democracy and 00:17:00.060 --> 00:17:02.150 align:start position:0% management with liquid democracy and here<00:17:00.810> there<00:17:01.050> could<00:17:01.200> be<00:17:01.230> many<00:17:01.440> arrangements 00:17:02.150 --> 00:17:02.160 align:start position:0% here there could be many arrangements 00:17:02.160 --> 00:17:04.819 align:start position:0% here there could be many arrangements but<00:17:02.730> a<00:17:03.000> simple<00:17:03.840> arrangement<00:17:04.110> is<00:17:04.530> to<00:17:04.680> have<00:17:04.800> a 00:17:04.819 --> 00:17:04.829 align:start position:0% but a simple arrangement is to have a 00:17:04.829 --> 00:17:07.160 align:start position:0% but a simple arrangement is to have a giver<00:17:05.189> who's<00:17:05.939> providing<00:17:06.540> some<00:17:06.720> ether<00:17:06.870> and 00:17:07.160 --> 00:17:07.170 align:start position:0% giver who's providing some ether and 00:17:07.170 --> 00:17:08.540 align:start position:0% giver who's providing some ether and they<00:17:07.260> want<00:17:07.439> that<00:17:07.530> to<00:17:07.770> go<00:17:07.890> to<00:17:07.949> a<00:17:08.010> to<00:17:08.250> a<00:17:08.280> good 00:17:08.540 --> 00:17:08.550 align:start position:0% they want that to go to a to a good 00:17:08.550 --> 00:17:10.490 align:start position:0% they want that to go to a to a good cause<00:17:08.790> or<00:17:09.060> a<00:17:09.120> good<00:17:09.300> project<00:17:09.540> they<00:17:10.199> don't<00:17:10.380> have 00:17:10.490 --> 00:17:10.500 align:start position:0% cause or a good project they don't have 00:17:10.500 --> 00:17:12.170 align:start position:0% cause or a good project they don't have time<00:17:10.680> to<00:17:10.860> do<00:17:10.949> that<00:17:11.069> themselves<00:17:11.280> or<00:17:11.850> they<00:17:11.939> want 00:17:12.170 --> 00:17:12.180 align:start position:0% time to do that themselves or they want 00:17:12.180 --> 00:17:13.880 align:start position:0% time to do that themselves or they want to<00:17:12.240> trust<00:17:12.540> someone<00:17:12.689> else<00:17:12.900> so<00:17:13.170> they<00:17:13.319> delegate 00:17:13.880 --> 00:17:13.890 align:start position:0% to trust someone else so they delegate 00:17:13.890 --> 00:17:17.480 align:start position:0% to trust someone else so they delegate that<00:17:14.069> to<00:17:14.339> another<00:17:14.910> role<00:17:15.209> and<00:17:15.930> that<00:17:16.490> delegate 00:17:17.480 --> 00:17:17.490 align:start position:0% that to another role and that delegate 00:17:17.490 --> 00:17:19.150 align:start position:0% that to another role and that delegate is<00:17:17.579> gonna<00:17:17.760> choose<00:17:18.060> the<00:17:18.209> project<00:17:18.720> and 00:17:19.150 --> 00:17:19.160 align:start position:0% is gonna choose the project and 00:17:19.160 --> 00:17:21.439 align:start position:0% is gonna choose the project and eventually<00:17:20.160> a<00:17:20.189> reviewer<00:17:20.699> is<00:17:20.939> going<00:17:21.180> to<00:17:21.240> say 00:17:21.439 --> 00:17:21.449 align:start position:0% eventually a reviewer is going to say 00:17:21.449 --> 00:17:22.850 align:start position:0% eventually a reviewer is going to say yes<00:17:21.750> these<00:17:21.959> milestones<00:17:22.589> have<00:17:22.740> been 00:17:22.850 --> 00:17:22.860 align:start position:0% yes these milestones have been 00:17:22.860 --> 00:17:25.510 align:start position:0% yes these milestones have been accomplished<00:17:23.400> and<00:17:23.640> that<00:17:24.180> goes<00:17:24.420> through<00:17:24.689> so 00:17:25.510 --> 00:17:25.520 align:start position:0% accomplished and that goes through so 00:17:25.520 --> 00:17:28.340 align:start position:0% accomplished and that goes through so this<00:17:26.520> is<00:17:26.699> seeming<00:17:27.150> a<00:17:27.240> simple<00:17:27.660> concept<00:17:28.020> but<00:17:28.230> it 00:17:28.340 --> 00:17:28.350 align:start position:0% this is seeming a simple concept but it 00:17:28.350 --> 00:17:30.560 align:start position:0% this is seeming a simple concept but it goes<00:17:28.530> really<00:17:28.800> far<00:17:29.160> and<00:17:29.520> it<00:17:29.940> really<00:17:30.270> is<00:17:30.390> what 00:17:30.560 --> 00:17:30.570 align:start position:0% goes really far and it really is what 00:17:30.570 --> 00:17:32.750 align:start position:0% goes really far and it really is what can<00:17:30.720> separate<00:17:31.200> someone<00:17:31.920> who<00:17:32.100> just<00:17:32.490> knows 00:17:32.750 --> 00:17:32.760 align:start position:0% can separate someone who just knows 00:17:32.760 --> 00:17:35.800 align:start position:0% can separate someone who just knows solidity<00:17:33.240> from<00:17:34.200> someone<00:17:34.650> who<00:17:34.860> can<00:17:35.040> design 00:17:35.800 --> 00:17:35.810 align:start position:0% solidity from someone who can design 00:17:35.810 --> 00:17:39.320 align:start position:0% solidity from someone who can design maintain<00:17:36.810> and<00:17:37.200> scale<00:17:37.770> smart<00:17:38.640> contracts<00:17:39.120> on<00:17:39.300> a 00:17:39.320 --> 00:17:39.330 align:start position:0% maintain and scale smart contracts on a 00:17:39.330 --> 00:17:43.520 align:start position:0% maintain and scale smart contracts on a live<00:17:39.570> network<00:17:41.810> context<00:17:42.810> dependence<00:17:43.320> is 00:17:43.520 --> 00:17:43.530 align:start position:0% live network context dependence is 00:17:43.530 --> 00:17:45.890 align:start position:0% live network context dependence is another<00:17:44.040> skill<00:17:44.400> that<00:17:44.700> comes<00:17:45.690> with<00:17:45.870> experience 00:17:45.890 --> 00:17:45.900 align:start position:0% another skill that comes with experience 00:17:45.900 --> 00:17:49.250 align:start position:0% another skill that comes with experience and<00:17:47.000> is<00:17:48.000> something<00:17:48.330> that<00:17:48.570> is<00:17:48.690> really<00:17:48.840> valued 00:17:49.250 --> 00:17:49.260 align:start position:0% and is something that is really valued 00:17:49.260 --> 00:17:51.200 align:start position:0% and is something that is really valued on<00:17:49.410> a<00:17:49.440> team<00:17:49.740> and<00:17:49.980> by<00:17:50.340> this<00:17:50.400> I<00:17:50.910> mean 00:17:51.200 --> 00:17:51.210 align:start position:0% on a team and by this I mean 00:17:51.210 --> 00:17:55.220 align:start position:0% on a team and by this I mean in<00:17:51.590> analyzing<00:17:52.590> when<00:17:53.190> one<00:17:54.059> action<00:17:54.450> is<00:17:54.570> true<00:17:54.899> in 00:17:55.220 --> 00:17:55.230 align:start position:0% in analyzing when one action is true in 00:17:55.230 --> 00:17:57.470 align:start position:0% in analyzing when one action is true in one<00:17:55.860> situation<00:17:56.100> and<00:17:56.730> the<00:17:56.789> same<00:17:56.940> action<00:17:57.299> might 00:17:57.470 --> 00:17:57.480 align:start position:0% one situation and the same action might 00:17:57.480 --> 00:17:59.330 align:start position:0% one situation and the same action might not<00:17:57.630> be<00:17:57.779> true<00:17:57.960> in<00:17:58.080> another<00:17:58.320> situation<00:17:58.620> I<00:17:59.130> know 00:17:59.330 --> 00:17:59.340 align:start position:0% not be true in another situation I know 00:17:59.340 --> 00:18:01.880 align:start position:0% not be true in another situation I know this<00:18:00.149> is<00:18:00.270> really<00:18:00.450> scary<00:18:00.870> for<00:18:01.350> a<00:18:01.409> lot<00:18:01.470> of<00:18:01.649> you<00:18:01.860> I 00:18:01.880 --> 00:18:01.890 align:start position:0% this is really scary for a lot of you I 00:18:01.890 --> 00:18:03.889 align:start position:0% this is really scary for a lot of you I didn't<00:18:02.220> get<00:18:02.309> into<00:18:02.549> development<00:18:03.149> to<00:18:03.510> deal<00:18:03.720> with 00:18:03.889 --> 00:18:03.899 align:start position:0% didn't get into development to deal with 00:18:03.899 --> 00:18:06.110 align:start position:0% didn't get into development to deal with fuzziness<00:18:04.440> and<00:18:04.529> ambiguity<00:18:05.070> either<00:18:05.250> I<00:18:05.549> love 00:18:06.110 --> 00:18:06.120 align:start position:0% fuzziness and ambiguity either I love 00:18:06.120 --> 00:18:08.120 align:start position:0% fuzziness and ambiguity either I love really<00:18:06.390> straightforward<00:18:06.840> and<00:18:07.500> deterministic 00:18:08.120 --> 00:18:08.130 align:start position:0% really straightforward and deterministic 00:18:08.130 --> 00:18:10.880 align:start position:0% really straightforward and deterministic systems<00:18:08.700> but<00:18:08.880> the<00:18:09.029> truth<00:18:09.240> is<00:18:09.419> any<00:18:09.890> complicated 00:18:10.880 --> 00:18:10.890 align:start position:0% systems but the truth is any complicated 00:18:10.890 --> 00:18:13.610 align:start position:0% systems but the truth is any complicated problem<00:18:11.490> is<00:18:11.669> going<00:18:12.270> to<00:18:12.390> depend<00:18:12.750> on<00:18:13.140> a<00:18:13.169> lot<00:18:13.470> of 00:18:13.610 --> 00:18:13.620 align:start position:0% problem is going to depend on a lot of 00:18:13.620 --> 00:18:17.419 align:start position:0% problem is going to depend on a lot of context<00:18:14.250> so<00:18:14.600> one<00:18:15.600> example<00:18:15.809> in<00:18:16.559> this<00:18:16.799> space<00:18:17.100> is 00:18:17.419 --> 00:18:17.429 align:start position:0% context so one example in this space is 00:18:17.429 --> 00:18:19.250 align:start position:0% context so one example in this space is that<00:18:17.850> you<00:18:17.940> hear<00:18:18.090> a<00:18:18.149> lot<00:18:18.240> of<00:18:18.480> best<00:18:18.659> practices 00:18:19.250 --> 00:18:19.260 align:start position:0% that you hear a lot of best practices 00:18:19.260 --> 00:18:21.320 align:start position:0% that you hear a lot of best practices best<00:18:19.830> practices<00:18:19.950> are<00:18:20.549> great<00:18:20.820> but<00:18:21.059> when<00:18:21.210> they 00:18:21.320 --> 00:18:21.330 align:start position:0% best practices are great but when they 00:18:21.330 --> 00:18:23.480 align:start position:0% best practices are great but when they turn<00:18:21.570> into<00:18:21.750> hard<00:18:22.049> and<00:18:22.200> fast<00:18:22.320> rules<00:18:22.770> you<00:18:23.340> can 00:18:23.480 --> 00:18:23.490 align:start position:0% turn into hard and fast rules you can 00:18:23.490 --> 00:18:25.130 align:start position:0% turn into hard and fast rules you can really<00:18:23.700> miss<00:18:23.909> out<00:18:24.059> on<00:18:24.179> the<00:18:24.270> nuances<00:18:24.870> of<00:18:24.899> the 00:18:25.130 --> 00:18:25.140 align:start position:0% really miss out on the nuances of the 00:18:25.140 --> 00:18:27.919 align:start position:0% really miss out on the nuances of the situation<00:18:25.710> so<00:18:25.890> one<00:18:26.370> I<00:18:26.399> see<00:18:26.669> a<00:18:26.700> lot<00:18:26.940> is<00:18:27.240> sand 00:18:27.919 --> 00:18:27.929 align:start position:0% situation so one I see a lot is sand 00:18:27.929 --> 00:18:30.350 align:start position:0% situation so one I see a lot is sand versus<00:18:28.409> withdraw<00:18:28.799> patterns<00:18:29.370> and<00:18:29.700> and<00:18:30.179> the 00:18:30.350 --> 00:18:30.360 align:start position:0% versus withdraw patterns and and the 00:18:30.360 --> 00:18:32.630 align:start position:0% versus withdraw patterns and and the advice<00:18:30.630> out<00:18:30.840> there<00:18:30.870> is<00:18:31.200> to<00:18:31.320> always<00:18:31.740> have<00:18:31.770> the 00:18:32.630 --> 00:18:32.640 align:start position:0% advice out there is to always have the 00:18:32.640 --> 00:18:35.330 align:start position:0% advice out there is to always have the user<00:18:32.820> withdraw<00:18:33.419> never<00:18:34.289> do<00:18:34.590> a<00:18:34.620> sand<00:18:35.010> so<00:18:35.190> there's 00:18:35.330 --> 00:18:35.340 align:start position:0% user withdraw never do a sand so there's 00:18:35.340 --> 00:18:37.250 align:start position:0% user withdraw never do a sand so there's like<00:18:35.460> push<00:18:35.730> versus<00:18:36.149> pull<00:18:36.179> never<00:18:36.659> do<00:18:36.870> a<00:18:36.899> send 00:18:37.250 --> 00:18:37.260 align:start position:0% like push versus pull never do a send 00:18:37.260 --> 00:18:39.830 align:start position:0% like push versus pull never do a send and<00:18:37.409> I<00:18:38.070> actually<00:18:38.309> don't<00:18:38.669> like<00:18:38.820> this<00:18:39.179> advice 00:18:39.830 --> 00:18:39.840 align:start position:0% and I actually don't like this advice 00:18:39.840 --> 00:18:42.200 align:start position:0% and I actually don't like this advice because<00:18:40.590> it's<00:18:40.740> often<00:18:40.919> just<00:18:41.370> taken<00:18:42.059> without 00:18:42.200 --> 00:18:42.210 align:start position:0% because it's often just taken without 00:18:42.210 --> 00:18:45.260 align:start position:0% because it's often just taken without much<00:18:42.539> thought<00:18:42.980> why<00:18:43.980> don't<00:18:44.039> we<00:18:44.520> do<00:18:44.669> a<00:18:44.700> send<00:18:45.059> well 00:18:45.260 --> 00:18:45.270 align:start position:0% much thought why don't we do a send well 00:18:45.270 --> 00:18:47.120 align:start position:0% much thought why don't we do a send well we<00:18:45.360> don't<00:18:45.630> do<00:18:45.779> a<00:18:45.809> send<00:18:46.140> because<00:18:46.559> there's 00:18:47.120 --> 00:18:47.130 align:start position:0% we don't do a send because there's 00:18:47.130 --> 00:18:49.039 align:start position:0% we don't do a send because there's vulnerabilities<00:18:48.120> if<00:18:48.330> you're<00:18:48.450> trying<00:18:48.720> to<00:18:48.779> send 00:18:49.039 --> 00:18:49.049 align:start position:0% vulnerabilities if you're trying to send 00:18:49.049 --> 00:18:51.740 align:start position:0% vulnerabilities if you're trying to send to<00:18:49.200> multiple<00:18:49.409> people<00:18:50.010> you<00:18:50.820> have<00:18:50.970> to<00:18:51.120> be<00:18:51.240> aware 00:18:51.740 --> 00:18:51.750 align:start position:0% to multiple people you have to be aware 00:18:51.750 --> 00:18:54.080 align:start position:0% to multiple people you have to be aware that<00:18:51.809> any<00:18:52.350> one<00:18:52.679> person<00:18:52.950> their<00:18:53.669> fallback 00:18:54.080 --> 00:18:54.090 align:start position:0% that any one person their fallback 00:18:54.090 --> 00:18:55.820 align:start position:0% that any one person their fallback function<00:18:54.510> could<00:18:54.630> throw<00:18:54.960> they<00:18:55.289> could<00:18:55.470> use<00:18:55.620> up 00:18:55.820 --> 00:18:55.830 align:start position:0% function could throw they could use up 00:18:55.830 --> 00:18:57.560 align:start position:0% function could throw they could use up all<00:18:56.010> the<00:18:56.039> gas<00:18:56.340> they<00:18:56.700> could<00:18:56.850> use<00:18:56.970> up<00:18:57.120> most<00:18:57.390> of 00:18:57.560 --> 00:18:57.570 align:start position:0% all the gas they could use up most of 00:18:57.570 --> 00:19:00.470 align:start position:0% all the gas they could use up most of the<00:18:57.659> gas<00:18:57.840> so<00:18:58.710> there's<00:18:58.919> risks<00:18:59.640> to<00:19:00.000> sending<00:19:00.360> to 00:19:00.470 --> 00:19:00.480 align:start position:0% the gas so there's risks to sending to 00:19:00.480 --> 00:19:02.779 align:start position:0% the gas so there's risks to sending to multiple<00:19:00.809> parties<00:19:01.169> okay<00:19:01.529> I<00:19:01.740> understand<00:19:02.700> that 00:19:02.779 --> 00:19:02.789 align:start position:0% multiple parties okay I understand that 00:19:02.789 --> 00:19:05.180 align:start position:0% multiple parties okay I understand that there<00:19:03.659> are<00:19:03.779> also<00:19:03.960> situations<00:19:04.590> where<00:19:05.010> maybe 00:19:05.180 --> 00:19:05.190 align:start position:0% there are also situations where maybe 00:19:05.190 --> 00:19:07.159 align:start position:0% there are also situations where maybe you<00:19:05.429> don't<00:19:05.669> want<00:19:05.909> for<00:19:06.419> the<00:19:06.510> user<00:19:06.690> experience 00:19:07.159 --> 00:19:07.169 align:start position:0% you don't want for the user experience 00:19:07.169 --> 00:19:10.669 align:start position:0% you don't want for the user experience they<00:19:07.890> don't<00:19:08.220> have<00:19:08.490> another<00:19:09.500> transaction<00:19:10.500> you 00:19:10.669 --> 00:19:10.679 align:start position:0% they don't have another transaction you 00:19:10.679 --> 00:19:11.750 align:start position:0% they don't have another transaction you don't<00:19:10.860> want<00:19:10.980> them<00:19:11.130> to<00:19:11.220> have<00:19:11.370> to<00:19:11.399> do<00:19:11.640> that 00:19:11.750 --> 00:19:11.760 align:start position:0% don't want them to have to do that 00:19:11.760 --> 00:19:13.970 align:start position:0% don't want them to have to do that transaction<00:19:12.419> so<00:19:13.020> maybe<00:19:13.289> the<00:19:13.500> send<00:19:13.740> would<00:19:13.890> be 00:19:13.970 --> 00:19:13.980 align:start position:0% transaction so maybe the send would be 00:19:13.980 --> 00:19:17.779 align:start position:0% transaction so maybe the send would be appropriate<00:19:14.340> in<00:19:14.549> those<00:19:14.669> cases<00:19:16.700> keeping<00:19:17.700> in 00:19:17.779 --> 00:19:17.789 align:start position:0% appropriate in those cases keeping in 00:19:17.789 --> 00:19:20.659 align:start position:0% appropriate in those cases keeping in mind<00:19:18.000> this<00:19:18.360> dictum<00:19:19.080> of<00:19:19.200> it<00:19:19.380> depends<00:19:19.980> I<00:19:20.159> had<00:19:20.640> a 00:19:20.659 --> 00:19:20.669 align:start position:0% mind this dictum of it depends I had a 00:19:20.669 --> 00:19:24.919 align:start position:0% mind this dictum of it depends I had a professor<00:19:21.419> in<00:19:21.840> grad<00:19:22.559> school<00:19:22.590> who<00:19:23.539> this<00:19:24.539> was<00:19:24.750> in 00:19:24.919 --> 00:19:24.929 align:start position:0% professor in grad school who this was in 00:19:24.929 --> 00:19:27.680 align:start position:0% professor in grad school who this was in my<00:19:25.049> counseling<00:19:25.529> program<00:19:25.980> and<00:19:26.539> it<00:19:27.539> was 00:19:27.680 --> 00:19:27.690 align:start position:0% my counseling program and it was 00:19:27.690 --> 00:19:30.260 align:start position:0% my counseling program and it was beautiful<00:19:28.080> every<00:19:28.500> time<00:19:28.529> anybody<00:19:29.309> asked<00:19:30.090> well 00:19:30.260 --> 00:19:30.270 align:start position:0% beautiful every time anybody asked well 00:19:30.270 --> 00:19:32.120 align:start position:0% beautiful every time anybody asked well what<00:19:30.960> if<00:19:31.080> you're<00:19:31.200> working<00:19:31.409> with<00:19:31.559> this<00:19:31.799> client 00:19:32.120 --> 00:19:32.130 align:start position:0% what if you're working with this client 00:19:32.130 --> 00:19:33.620 align:start position:0% what if you're working with this client and<00:19:32.429> they<00:19:32.490> do<00:19:32.549> this<00:19:32.820> what<00:19:33.120> should<00:19:33.240> I<00:19:33.360> do 00:19:33.620 --> 00:19:33.630 align:start position:0% and they do this what should I do 00:19:33.630 --> 00:19:37.340 align:start position:0% and they do this what should I do she<00:19:34.620> always<00:19:34.919> answered<00:19:35.659> she<00:19:36.659> thought<00:19:36.870> about<00:19:36.929> it 00:19:37.340 --> 00:19:37.350 align:start position:0% she always answered she thought about it 00:19:37.350 --> 00:19:40.519 align:start position:0% she always answered she thought about it and<00:19:37.850> then<00:19:38.850> she<00:19:39.000> said<00:19:39.240> well<00:19:39.450> it<00:19:39.720> depends<00:19:40.320> and 00:19:40.519 --> 00:19:40.529 align:start position:0% and then she said well it depends and 00:19:40.529 --> 00:19:43.190 align:start position:0% and then she said well it depends and that<00:19:40.830> would<00:19:40.950> be<00:19:41.070> her<00:19:41.190> answer<00:19:41.520> every<00:19:41.880> time<00:19:42.169> so 00:19:43.190 --> 00:19:43.200 align:start position:0% that would be her answer every time so 00:19:43.200 --> 00:19:46.519 align:start position:0% that would be her answer every time so with<00:19:44.100> skill<00:19:44.610> and<00:19:44.640> experience<00:19:45.320> comes<00:19:46.320> an 00:19:46.519 --> 00:19:46.529 align:start position:0% with skill and experience comes an 00:19:46.529 --> 00:19:48.289 align:start position:0% with skill and experience comes an incredible<00:19:47.010> awareness<00:19:47.399> of<00:19:47.520> context<00:19:48.149> so<00:19:48.179> I 00:19:48.289 --> 00:19:48.299 align:start position:0% incredible awareness of context so I 00:19:48.299 --> 00:19:50.450 align:start position:0% incredible awareness of context so I encourage<00:19:48.630> you<00:19:48.870> to<00:19:49.110> think<00:19:49.380> about<00:19:49.710> context 00:19:50.450 --> 00:19:50.460 align:start position:0% encourage you to think about context 00:19:50.460 --> 00:19:52.639 align:start position:0% encourage you to think about context dependence<00:19:50.940> and<00:19:51.179> lastly<00:19:52.110> I<00:19:52.230> want<00:19:52.500> to<00:19:52.559> say 00:19:52.639 --> 00:19:52.649 align:start position:0% dependence and lastly I want to say 00:19:52.649 --> 00:19:55.190 align:start position:0% dependence and lastly I want to say leadership<00:19:53.429> in<00:19:53.899> blockchain<00:19:54.899> at<00:19:55.110> the 00:19:55.190 --> 00:19:55.200 align:start position:0% leadership in blockchain at the 00:19:55.200 --> 00:19:57.169 align:start position:0% leadership in blockchain at the developer<00:19:55.679> level<00:19:56.010> because<00:19:56.429> contracts<00:19:57.000> are 00:19:57.169 --> 00:19:57.179 align:start position:0% developer level because contracts are 00:19:57.179 --> 00:19:59.480 align:start position:0% developer level because contracts are immutable<00:19:57.770> technical<00:19:58.770> debt<00:19:58.980> is<00:19:59.190> much 00:19:59.480 --> 00:19:59.490 align:start position:0% immutable technical debt is much 00:19:59.490 --> 00:20:01.580 align:start position:0% immutable technical debt is much costlier<00:19:59.990> so<00:20:00.990> when<00:20:01.110> you're<00:20:01.230> making<00:20:01.500> decisions 00:20:01.580 --> 00:20:01.590 align:start position:0% costlier so when you're making decisions 00:20:01.590 --> 00:20:03.830 align:start position:0% costlier so when you're making decisions as<00:20:02.100> a<00:20:02.130> lead<00:20:02.429> engineer<00:20:02.940> you<00:20:03.389> have<00:20:03.539> to<00:20:03.659> make<00:20:03.809> a 00:20:03.830 --> 00:20:03.840 align:start position:0% as a lead engineer you have to make a 00:20:03.840 --> 00:20:05.010 align:start position:0% as a lead engineer you have to make a lot<00:20:04.049> of<00:20:04.080> judgment<00:20:04.559> calls 00:20:05.010 --> 00:20:05.020 align:start position:0% lot of judgment calls 00:20:05.020 --> 00:20:07.050 align:start position:0% lot of judgment calls because<00:20:05.170> that<00:20:05.410> code<00:20:05.710> might<00:20:05.980> be<00:20:06.160> on<00:20:06.370> chain<00:20:06.790> for 00:20:07.050 --> 00:20:07.060 align:start position:0% because that code might be on chain for 00:20:07.060 --> 00:20:09.090 align:start position:0% because that code might be on chain for a<00:20:07.090> long<00:20:07.300> time<00:20:07.600> and<00:20:07.900> that's<00:20:08.560> something<00:20:08.650> to<00:20:08.980> keep 00:20:09.090 --> 00:20:09.100 align:start position:0% a long time and that's something to keep 00:20:09.100 --> 00:20:13.070 align:start position:0% a long time and that's something to keep in<00:20:09.250> mind<00:20:09.870> thank<00:20:10.870> you<00:20:11.020> so<00:20:11.230> much<00:20:11.470> I'm<00:20:12.340> gonna 00:20:13.070 --> 00:20:13.080 align:start position:0% in mind thank you so much I'm gonna 00:20:13.080 --> 00:20:16.230 align:start position:0% in mind thank you so much I'm gonna share<00:20:14.080> it<00:20:14.110> go<00:20:14.350> over<00:20:14.620> the<00:20:14.770> patterns<00:20:15.700> just<00:20:16.060> to 00:20:16.230 --> 00:20:16.240 align:start position:0% share it go over the patterns just to 00:20:16.240 --> 00:20:17.640 align:start position:0% share it go over the patterns just to name<00:20:16.420> them<00:20:16.600> we<00:20:16.750> talked<00:20:16.990> about<00:20:17.140> central 00:20:17.640 --> 00:20:17.650 align:start position:0% name them we talked about central 00:20:17.650 --> 00:20:19.620 align:start position:0% name them we talked about central logging<00:20:18.100> modular<00:20:18.970> libraries<00:20:19.450> and 00:20:19.620 --> 00:20:19.630 align:start position:0% logging modular libraries and 00:20:19.630 --> 00:20:21.540 align:start position:0% logging modular libraries and arbitration<00:20:20.050> as<00:20:20.380> architectural<00:20:20.980> patterns<00:20:21.370> at 00:20:21.540 --> 00:20:21.550 align:start position:0% arbitration as architectural patterns at 00:20:21.550 --> 00:20:23.220 align:start position:0% arbitration as architectural patterns at a<00:20:21.580> lower<00:20:21.790> level<00:20:21.880> and<00:20:22.360> then<00:20:22.840> at<00:20:22.960> the<00:20:23.050> higher 00:20:23.220 --> 00:20:23.230 align:start position:0% a lower level and then at the higher 00:20:23.230 --> 00:20:25.320 align:start position:0% a lower level and then at the higher level<00:20:23.620> I<00:20:23.770> hope<00:20:24.010> you<00:20:24.520> can<00:20:24.730> take<00:20:24.910> some<00:20:25.150> of<00:20:25.240> these 00:20:25.320 --> 00:20:25.330 align:start position:0% level I hope you can take some of these 00:20:25.330 --> 00:20:27.240 align:start position:0% level I hope you can take some of these concepts<00:20:25.840> away<00:20:26.140> about<00:20:26.440> leading<00:20:26.860> your<00:20:26.980> team 00:20:27.240 --> 00:20:27.250 align:start position:0% concepts away about leading your team 00:20:27.250 --> 00:20:30.150 align:start position:0% concepts away about leading your team being<00:20:28.060> more<00:20:28.390> dependent<00:20:28.900> on<00:20:28.990> context<00:20:29.620> and<00:20:29.770> then 00:20:30.150 --> 00:20:30.160 align:start position:0% being more dependent on context and then 00:20:30.160 --> 00:20:31.980 align:start position:0% being more dependent on context and then bringing<00:20:30.430> role<00:20:30.700> analysis<00:20:31.300> to<00:20:31.450> everything<00:20:31.900> you 00:20:31.980 --> 00:20:31.990 align:start position:0% bringing role analysis to everything you 00:20:31.990 --> 00:20:36.550 align:start position:0% bringing role analysis to everything you do<00:20:32.140> thank<00:20:32.410> you<00:20:33.010> very<00:20:33.250> much 00:20:36.550 --> 00:20:36.560 align:start position:0% 00:20:36.560 --> 00:20:44.140 align:start position:0% [Music]