WEBVTT Kind: captions Language: en 00:00:14.440 --> 00:00:17.590 align:start position:0% hello<00:00:15.440> yeah<00:00:16.190> hi<00:00:16.520> everyone<00:00:16.910> it's<00:00:17.180> so<00:00:17.360> exciting 00:00:17.590 --> 00:00:17.600 align:start position:0% hello yeah hi everyone it's so exciting 00:00:17.600 --> 00:00:19.510 align:start position:0% hello yeah hi everyone it's so exciting to<00:00:17.780> be<00:00:17.900> talking<00:00:18.350> to<00:00:18.680> all<00:00:18.800> of<00:00:18.830> you<00:00:18.950> here<00:00:19.220> at<00:00:19.370> Def 00:00:19.510 --> 00:00:19.520 align:start position:0% to be talking to all of you here at Def 00:00:19.520 --> 00:00:21.460 align:start position:0% to be talking to all of you here at Def Con<00:00:19.610> I'm<00:00:19.910> especially<00:00:20.270> talking<00:00:20.720> after<00:00:21.170> dirty 00:00:21.460 --> 00:00:21.470 align:start position:0% Con I'm especially talking after dirty 00:00:21.470 --> 00:00:23.320 align:start position:0% Con I'm especially talking after dirty and<00:00:21.800> all<00:00:21.950> the<00:00:22.130> incredible<00:00:22.400> efforts<00:00:22.820> that<00:00:23.210> they 00:00:23.320 --> 00:00:23.330 align:start position:0% and all the incredible efforts that they 00:00:23.330 --> 00:00:25.030 align:start position:0% and all the incredible efforts that they have<00:00:23.450> been<00:00:23.600> doing<00:00:23.870> with<00:00:24.020> UI<00:00:24.230> hat 00:00:25.030 --> 00:00:25.040 align:start position:0% have been doing with UI hat 00:00:25.040 --> 00:00:28.090 align:start position:0% have been doing with UI hat so<00:00:25.730> yeah<00:00:25.880> I'm<00:00:26.630> Jorge<00:00:27.140> I'm<00:00:27.290> from<00:00:27.650> the<00:00:27.770> Argonne 00:00:28.090 --> 00:00:28.100 align:start position:0% so yeah I'm Jorge I'm from the Argonne 00:00:28.100 --> 00:00:29.980 align:start position:0% so yeah I'm Jorge I'm from the Argonne team<00:00:28.310> and<00:00:28.550> kind<00:00:28.910> of<00:00:29.030> to<00:00:29.180> start<00:00:29.510> framing<00:00:29.690> the 00:00:29.980 --> 00:00:29.990 align:start position:0% team and kind of to start framing the 00:00:29.990 --> 00:00:31.930 align:start position:0% team and kind of to start framing the talk<00:00:30.170> I<00:00:30.380> will<00:00:30.530> talk<00:00:30.800> a<00:00:30.830> little<00:00:31.130> bit<00:00:31.430> about<00:00:31.460> what 00:00:31.930 --> 00:00:31.940 align:start position:0% talk I will talk a little bit about what 00:00:31.940 --> 00:00:35.140 align:start position:0% talk I will talk a little bit about what with<00:00:32.300> Aragon<00:00:32.689> is<00:00:33.010> so<00:00:34.010> Aragon<00:00:34.550> is<00:00:34.670> basically<00:00:35.030> a 00:00:35.140 --> 00:00:35.150 align:start position:0% with Aragon is so Aragon is basically a 00:00:35.150 --> 00:00:36.819 align:start position:0% with Aragon is so Aragon is basically a decentralized<00:00:35.690> organizations<00:00:36.350> platform 00:00:36.819 --> 00:00:36.829 align:start position:0% decentralized organizations platform 00:00:36.829 --> 00:00:39.430 align:start position:0% decentralized organizations platform built<00:00:37.070> on<00:00:37.220> a<00:00:37.250> theorem<00:00:37.640> we<00:00:37.940> build<00:00:38.150> the<00:00:38.510> software 00:00:39.430 --> 00:00:39.440 align:start position:0% built on a theorem we build the software 00:00:39.440 --> 00:00:41.410 align:start position:0% built on a theorem we build the software and<00:00:39.739> the<00:00:39.950> infrastructure<00:00:40.400> so<00:00:40.850> running 00:00:41.410 --> 00:00:41.420 align:start position:0% and the infrastructure so running 00:00:41.420 --> 00:00:43.690 align:start position:0% and the infrastructure so running decentralized<00:00:42.170> organizations<00:00:42.800> can<00:00:43.070> become<00:00:43.340> a 00:00:43.690 --> 00:00:43.700 align:start position:0% decentralized organizations can become a 00:00:43.700 --> 00:00:46.680 align:start position:0% decentralized organizations can become a reality<00:00:44.150> and<00:00:44.600> we<00:00:45.350> are<00:00:45.470> doing<00:00:45.650> this<00:00:45.890> with<00:00:46.190> like 00:00:46.680 --> 00:00:46.690 align:start position:0% reality and we are doing this with like 00:00:46.690 --> 00:00:49.510 align:start position:0% reality and we are doing this with like focusing<00:00:47.690> on<00:00:47.840> like<00:00:48.230> non-technical<00:00:48.829> users<00:00:49.280> or 00:00:49.510 --> 00:00:49.520 align:start position:0% focusing on like non-technical users or 00:00:49.520 --> 00:00:51.370 align:start position:0% focusing on like non-technical users or people<00:00:49.850> that<00:00:50.000> might<00:00:50.270> not<00:00:50.420> have<00:00:50.570> heard<00:00:50.810> about 00:00:51.370 --> 00:00:51.380 align:start position:0% people that might not have heard about 00:00:51.380 --> 00:00:54.010 align:start position:0% people that might not have heard about the<00:00:51.530> theorem<00:00:51.920> as<00:00:52.250> our<00:00:52.489> users<00:00:53.239> so<00:00:53.450> we're<00:00:53.989> very 00:00:54.010 --> 00:00:54.020 align:start position:0% the theorem as our users so we're very 00:00:54.020 --> 00:00:56.710 align:start position:0% the theorem as our users so we're very careful<00:00:54.410> that<00:00:54.800> they<00:00:55.220> will<00:00:55.370> be<00:00:55.489> able<00:00:55.610> to<00:00:55.790> use<00:00:56.510> it 00:00:56.710 --> 00:00:56.720 align:start position:0% careful that they will be able to use it 00:00:56.720 --> 00:00:58.630 align:start position:0% careful that they will be able to use it and<00:00:56.840> also<00:00:57.680> it's<00:00:57.800> very<00:00:57.829> important<00:00:58.309> for<00:00:58.489> us<00:00:58.610> that 00:00:58.630 --> 00:00:58.640 align:start position:0% and also it's very important for us that 00:00:58.640 --> 00:01:01.959 align:start position:0% and also it's very important for us that the<00:00:59.030> system<00:00:59.210> is<00:00:59.540> extendable<00:01:00.020> enough<00:01:00.410> so<00:01:00.980> it 00:01:01.959 --> 00:01:01.969 align:start position:0% the system is extendable enough so it 00:01:01.969 --> 00:01:04.660 align:start position:0% the system is extendable enough so it can<00:01:02.030> be<00:01:02.300> used<00:01:02.480> for<00:01:02.600> very<00:01:03.410> like<00:01:03.920> large-scale 00:01:04.660 --> 00:01:04.670 align:start position:0% can be used for very like large-scale 00:01:04.670 --> 00:01:06.850 align:start position:0% can be used for very like large-scale systems<00:01:05.119> but<00:01:05.329> also<00:01:05.390> for<00:01:05.870> like<00:01:06.049> more<00:01:06.470> tiny 00:01:06.850 --> 00:01:06.860 align:start position:0% systems but also for like more tiny 00:01:06.860 --> 00:01:10.960 align:start position:0% systems but also for like more tiny things<00:01:08.740> so<00:01:09.740> when<00:01:10.190> we<00:01:10.370> talk<00:01:10.549> about<00:01:10.580> like 00:01:10.960 --> 00:01:10.970 align:start position:0% things so when we talk about like 00:01:10.970 --> 00:01:12.820 align:start position:0% things so when we talk about like future-proof<00:01:11.659> smart<00:01:11.960> contracts<00:01:12.380> what<00:01:12.620> we 00:01:12.820 --> 00:01:12.830 align:start position:0% future-proof smart contracts what we 00:01:12.830 --> 00:01:14.649 align:start position:0% future-proof smart contracts what we really<00:01:13.159> mean<00:01:13.310> it's<00:01:13.580> like<00:01:13.760> how<00:01:14.240> can<00:01:14.479> we<00:01:14.540> make 00:01:14.649 --> 00:01:14.659 align:start position:0% really mean it's like how can we make 00:01:14.659 --> 00:01:16.510 align:start position:0% really mean it's like how can we make sure<00:01:14.840> that<00:01:15.350> the<00:01:15.770> contracts<00:01:16.250> that<00:01:16.340> we're 00:01:16.510 --> 00:01:16.520 align:start position:0% sure that the contracts that we're 00:01:16.520 --> 00:01:17.800 align:start position:0% sure that the contracts that we're building<00:01:16.640> today<00:01:16.970> for<00:01:17.360> these<00:01:17.479> organizations 00:01:17.800 --> 00:01:17.810 align:start position:0% building today for these organizations 00:01:17.810 --> 00:01:20.590 align:start position:0% building today for these organizations are<00:01:18.440> going<00:01:19.159> to<00:01:19.400> stand<00:01:19.700> the<00:01:19.790> test<00:01:20.000> of<00:01:20.119> time<00:01:20.330> and 00:01:20.590 --> 00:01:20.600 align:start position:0% are going to stand the test of time and 00:01:20.600 --> 00:01:22.570 align:start position:0% are going to stand the test of time and can<00:01:20.869> be<00:01:21.020> used<00:01:21.229> by<00:01:21.350> organizations<00:01:21.680> for<00:01:22.310> many 00:01:22.570 --> 00:01:22.580 align:start position:0% can be used by organizations for many 00:01:22.580 --> 00:01:25.420 align:start position:0% can be used by organizations for many years<00:01:22.990> so<00:01:23.990> these<00:01:24.320> are<00:01:24.500> kind<00:01:24.710> of<00:01:24.799> like<00:01:24.860> three 00:01:25.420 --> 00:01:25.430 align:start position:0% years so these are kind of like three 00:01:25.430 --> 00:01:28.149 align:start position:0% years so these are kind of like three very<00:01:25.850> obvious<00:01:26.420> points<00:01:26.810> but<00:01:27.020> the<00:01:27.710> the<00:01:27.950> first 00:01:28.149 --> 00:01:28.159 align:start position:0% very obvious points but the the first 00:01:28.159 --> 00:01:30.250 align:start position:0% very obvious points but the the first one<00:01:28.190> is<00:01:28.400> like<00:01:28.580> the<00:01:28.940> damn<00:01:29.330> contracts<00:01:29.869> are<00:01:30.080> the 00:01:30.250 --> 00:01:30.260 align:start position:0% one is like the damn contracts are the 00:01:30.260 --> 00:01:32.530 align:start position:0% one is like the damn contracts are the best<00:01:30.409> buy<00:01:30.560> contracts<00:01:31.040> and<00:01:31.250> the<00:01:31.520> what<00:01:32.030> this 00:01:32.530 --> 00:01:32.540 align:start position:0% best buy contracts and the what this 00:01:32.540 --> 00:01:35.380 align:start position:0% best buy contracts and the what this means<00:01:32.780> is<00:01:32.960> like<00:01:33.110> the<00:01:33.710> easiest<00:01:34.130> and<00:01:34.490> the<00:01:34.520> clear 00:01:35.380 --> 00:01:35.390 align:start position:0% means is like the easiest and the clear 00:01:35.390 --> 00:01:37.840 align:start position:0% means is like the easiest and the clear Edina<00:01:35.780> smart<00:01:36.080> contract<00:01:36.470> is<00:01:36.590> that<00:01:37.070> better<00:01:37.460> for 00:01:37.840 --> 00:01:37.850 align:start position:0% Edina smart contract is that better for 00:01:37.850 --> 00:01:39.340 align:start position:0% Edina smart contract is that better for because<00:01:38.119> everyone<00:01:38.450> will<00:01:38.600> know<00:01:38.840> what<00:01:39.140> are<00:01:39.229> the 00:01:39.340 --> 00:01:39.350 align:start position:0% because everyone will know what are the 00:01:39.350 --> 00:01:41.859 align:start position:0% because everyone will know what are the implications<00:01:39.590> of<00:01:40.010> every<00:01:40.310> action<00:01:40.490> and<00:01:41.450> also<00:01:41.630> it 00:01:41.859 --> 00:01:41.869 align:start position:0% implications of every action and also it 00:01:41.869 --> 00:01:44.560 align:start position:0% implications of every action and also it decreases<00:01:42.350> the<00:01:42.380> the<00:01:42.920> attack<00:01:43.369> vector<00:01:43.400> for<00:01:43.970> for 00:01:44.560 --> 00:01:44.570 align:start position:0% decreases the the attack vector for for 00:01:44.570 --> 00:01:46.840 align:start position:0% decreases the the attack vector for for it<00:01:44.659> also<00:01:45.590> something<00:01:45.979> very<00:01:46.130> important<00:01:46.610> for<00:01:46.759> us 00:01:46.840 --> 00:01:46.850 align:start position:0% it also something very important for us 00:01:46.850 --> 00:01:49.179 align:start position:0% it also something very important for us is<00:01:47.030> like<00:01:47.210> to<00:01:47.450> make<00:01:47.630> sure<00:01:47.840> that<00:01:48.110> we<00:01:48.470> only<00:01:48.650> do<00:01:48.979> in 00:01:49.179 --> 00:01:49.189 align:start position:0% is like to make sure that we only do in 00:01:49.189 --> 00:01:51.370 align:start position:0% is like to make sure that we only do in the<00:01:49.280> smart<00:01:49.490> contracts<00:01:49.880> the<00:01:50.299> minimum<00:01:51.140> amount 00:01:51.370 --> 00:01:51.380 align:start position:0% the smart contracts the minimum amount 00:01:51.380 --> 00:01:53.859 align:start position:0% the smart contracts the minimum amount necessary<00:01:51.680> for<00:01:52.250> the<00:01:52.310> system<00:01:52.610> to<00:01:52.729> work<00:01:52.869> and 00:01:53.859 --> 00:01:53.869 align:start position:0% necessary for the system to work and 00:01:53.869 --> 00:01:56.530 align:start position:0% necessary for the system to work and this<00:01:54.259> is<00:01:54.350> also<00:01:54.470> because<00:01:54.740> this<00:01:55.159> this<00:01:55.729> course 00:01:56.530 --> 00:01:56.540 align:start position:0% this is also because this this course 00:01:56.540 --> 00:01:59.140 align:start position:0% this is also because this this course will<00:01:56.750> be<00:01:56.780> paid<00:01:57.500> by<00:01:57.710> your<00:01:57.860> users<00:01:58.100> and<00:01:58.820> this<00:01:59.000> will 00:01:59.140 --> 00:01:59.150 align:start position:0% will be paid by your users and this will 00:01:59.150 --> 00:02:00.700 align:start position:0% will be paid by your users and this will be<00:01:59.240> the<00:01:59.360> baseline<00:01:59.540> for<00:01:59.900> costs<00:02:00.290> for<00:02:00.439> usin 00:02:00.700 --> 00:02:00.710 align:start position:0% be the baseline for costs for usin 00:02:00.710 --> 00:02:03.039 align:start position:0% be the baseline for costs for usin Aragon<00:02:01.070> and<00:02:01.280> also<00:02:01.820> the<00:02:02.000> Third<00:02:02.270> Point<00:02:02.509> and<00:02:02.810> the 00:02:03.039 --> 00:02:03.049 align:start position:0% Aragon and also the Third Point and the 00:02:03.049 --> 00:02:05.140 align:start position:0% Aragon and also the Third Point and the one<00:02:03.229> that<00:02:03.380> I<00:02:03.439> will<00:02:03.680> spend<00:02:04.579> more<00:02:04.759> time<00:02:04.970> during 00:02:05.140 --> 00:02:05.150 align:start position:0% one that I will spend more time during 00:02:05.150 --> 00:02:07.149 align:start position:0% one that I will spend more time during the<00:02:05.329> talk<00:02:05.509> talking<00:02:05.689> about<00:02:06.049> it's<00:02:06.320> like<00:02:06.409> we 00:02:07.149 --> 00:02:07.159 align:start position:0% the talk talking about it's like we 00:02:07.159 --> 00:02:08.889 align:start position:0% the talk talking about it's like we really<00:02:07.490> feel<00:02:07.729> very<00:02:08.090> strongly<00:02:08.390> that's<00:02:08.750> my 00:02:08.889 --> 00:02:08.899 align:start position:0% really feel very strongly that's my 00:02:08.899 --> 00:02:12.160 align:start position:0% really feel very strongly that's my contracts<00:02:09.379> need<00:02:09.590> to<00:02:09.679> be<00:02:09.800> upgraded<00:02:10.209> and<00:02:11.209> this 00:02:12.160 --> 00:02:12.170 align:start position:0% contracts need to be upgraded and this 00:02:12.170 --> 00:02:13.870 align:start position:0% contracts need to be upgraded and this is<00:02:12.290> kind<00:02:12.560> of<00:02:12.620> like<00:02:12.800> a<00:02:12.830> controversial<00:02:13.430> point 00:02:13.870 --> 00:02:13.880 align:start position:0% is kind of like a controversial point 00:02:13.880 --> 00:02:15.250 align:start position:0% is kind of like a controversial point because<00:02:14.599> there 00:02:15.250 --> 00:02:15.260 align:start position:0% because there 00:02:15.260 --> 00:02:16.990 align:start position:0% because there many<00:02:15.439> things<00:02:15.769> I<00:02:15.950> could<00:02:16.159> go<00:02:16.310> wrong<00:02:16.549> with<00:02:16.790> my 00:02:16.990 --> 00:02:17.000 align:start position:0% many things I could go wrong with my 00:02:17.000 --> 00:02:19.119 align:start position:0% many things I could go wrong with my contract<00:02:17.420> separate<00:02:17.750> ability<00:02:18.170> the<00:02:18.920> first 00:02:19.119 --> 00:02:19.129 align:start position:0% contract separate ability the first 00:02:19.129 --> 00:02:20.589 align:start position:0% contract separate ability the first thing<00:02:19.280> is<00:02:19.400> like<00:02:19.579> we're<00:02:20.120> building<00:02:20.450> this 00:02:20.589 --> 00:02:20.599 align:start position:0% thing is like we're building this 00:02:20.599 --> 00:02:22.600 align:start position:0% thing is like we're building this awesome<00:02:20.780> like<00:02:21.200> trustless<00:02:21.590> systems<00:02:22.040> but<00:02:22.250> if<00:02:22.430> we 00:02:22.600 --> 00:02:22.610 align:start position:0% awesome like trustless systems but if we 00:02:22.610 --> 00:02:24.580 align:start position:0% awesome like trustless systems but if we put<00:02:22.909> one<00:02:23.269> entity<00:02:23.720> that<00:02:23.870> can<00:02:24.110> arbitrarily 00:02:24.580 --> 00:02:24.590 align:start position:0% put one entity that can arbitrarily 00:02:24.590 --> 00:02:26.649 align:start position:0% put one entity that can arbitrarily change<00:02:25.159> the<00:02:25.670> rules<00:02:25.909> of<00:02:26.060> the<00:02:26.120> game<00:02:26.360> well 00:02:26.649 --> 00:02:26.659 align:start position:0% change the rules of the game well 00:02:26.659 --> 00:02:28.330 align:start position:0% change the rules of the game well everyone<00:02:27.049> is<00:02:27.170> doing<00:02:27.319> it<00:02:27.560> we're<00:02:28.069> basically 00:02:28.330 --> 00:02:28.340 align:start position:0% everyone is doing it we're basically 00:02:28.340 --> 00:02:31.110 align:start position:0% everyone is doing it we're basically having<00:02:28.640> like<00:02:29.150> these<00:02:29.720> trans<00:02:30.650> folk<00:02:30.890> on 00:02:31.110 --> 00:02:31.120 align:start position:0% having like these trans folk on 00:02:31.120 --> 00:02:34.420 align:start position:0% having like these trans folk on contracts<00:02:32.120> again<00:02:32.500> but<00:02:33.500> of<00:02:33.890> course<00:02:34.159> we<00:02:34.310> would 00:02:34.420 --> 00:02:34.430 align:start position:0% contracts again but of course we would 00:02:34.430 --> 00:02:35.949 align:start position:0% contracts again but of course we would see<00:02:34.610> like<00:02:34.760> what<00:02:35.120> were<00:02:35.480> two<00:02:35.629> paths<00:02:35.780> to 00:02:35.949 --> 00:02:35.959 align:start position:0% see like what were two paths to 00:02:35.959 --> 00:02:38.500 align:start position:0% see like what were two paths to upgrading<00:02:36.260> is<00:02:36.730> and<00:02:37.730> also<00:02:38.030> there's<00:02:38.390> this 00:02:38.500 --> 00:02:38.510 align:start position:0% upgrading is and also there's this 00:02:38.510 --> 00:02:40.270 align:start position:0% upgrading is and also there's this interesting<00:02:39.230> attack<00:02:39.500> vector<00:02:39.890> that<00:02:40.069> could 00:02:40.270 --> 00:02:40.280 align:start position:0% interesting attack vector that could 00:02:40.280 --> 00:02:43.000 align:start position:0% interesting attack vector that could happen<00:02:40.430> in<00:02:40.760> which<00:02:41.170> someone<00:02:42.170> could<00:02:42.440> front<00:02:42.799> van 00:02:43.000 --> 00:02:43.010 align:start position:0% happen in which someone could front van 00:02:43.010 --> 00:02:45.099 align:start position:0% happen in which someone could front van like<00:02:43.370> a<00:02:43.400> very<00:02:43.879> important<00:02:44.269> transaction<00:02:44.689> to<00:02:45.079> a 00:02:45.099 --> 00:02:45.109 align:start position:0% like a very important transaction to a 00:02:45.109 --> 00:02:47.440 align:start position:0% like a very important transaction to a smart<00:02:45.620> contract<00:02:45.769> by<00:02:46.189> doing<00:02:46.459> an<00:02:46.579> upgrade<00:02:46.730> what 00:02:47.440 --> 00:02:47.450 align:start position:0% smart contract by doing an upgrade what 00:02:47.450 --> 00:02:49.660 align:start position:0% smart contract by doing an upgrade what this<00:02:47.569> means<00:02:47.780> here<00:02:48.019> is<00:02:48.230> like<00:02:48.470> you<00:02:49.280> may<00:02:49.400> be<00:02:49.430> doing 00:02:49.660 --> 00:02:49.670 align:start position:0% this means here is like you may be doing 00:02:49.670 --> 00:02:51.610 align:start position:0% this means here is like you may be doing a<00:02:49.879> transaction<00:02:50.269> expecting<00:02:51.049> that<00:02:51.170> the<00:02:51.319> system 00:02:51.610 --> 00:02:51.620 align:start position:0% a transaction expecting that the system 00:02:51.620 --> 00:02:53.530 align:start position:0% a transaction expecting that the system works<00:02:51.829> in<00:02:51.980> one<00:02:52.129> way<00:02:52.280> but<00:02:52.640> before<00:02:53.420> the 00:02:53.530 --> 00:02:53.540 align:start position:0% works in one way but before the 00:02:53.540 --> 00:02:55.030 align:start position:0% works in one way but before the transaction<00:02:53.870> is<00:02:54.170> mined<00:02:54.379> and<00:02:54.590> half<00:02:54.709> way<00:02:54.829> to<00:02:54.889> is 00:02:55.030 --> 00:02:55.040 align:start position:0% transaction is mined and half way to is 00:02:55.040 --> 00:02:58.300 align:start position:0% transaction is mined and half way to is my<00:02:55.190> contract<00:02:55.639> happens<00:02:56.090> so<00:02:57.040> this<00:02:58.040> is<00:02:58.159> something 00:02:58.300 --> 00:02:58.310 align:start position:0% my contract happens so this is something 00:02:58.310 --> 00:03:00.089 align:start position:0% my contract happens so this is something to<00:02:58.459> take<00:02:59.060> care<00:02:59.269> of 00:03:00.089 --> 00:03:00.099 align:start position:0% to take care of 00:03:00.099 --> 00:03:04.930 align:start position:0% to take care of so<00:03:01.720> anyway<00:03:02.720> why<00:03:03.379> do<00:03:03.889> we<00:03:04.040> need<00:03:04.159> smart<00:03:04.549> contract 00:03:04.930 --> 00:03:04.940 align:start position:0% so anyway why do we need smart contract 00:03:04.940 --> 00:03:05.830 align:start position:0% so anyway why do we need smart contract operators 00:03:05.830 --> 00:03:05.840 align:start position:0% operators 00:03:05.840 --> 00:03:07.569 align:start position:0% operators it's<00:03:06.139> because<00:03:06.409> like<00:03:06.560> as<00:03:06.799> we<00:03:06.980> all<00:03:07.129> know<00:03:07.310> this<00:03:07.519> is 00:03:07.569 --> 00:03:07.579 align:start position:0% it's because like as we all know this is 00:03:07.579 --> 00:03:10.059 align:start position:0% it's because like as we all know this is an<00:03:07.790> extremely<00:03:07.970> young<00:03:08.840> technology<00:03:09.139> and<00:03:09.620> there 00:03:10.059 --> 00:03:10.069 align:start position:0% an extremely young technology and there 00:03:10.069 --> 00:03:11.710 align:start position:0% an extremely young technology and there will<00:03:10.220> be<00:03:10.250> probably<00:03:10.730> backs<00:03:11.060> that<00:03:11.329> are<00:03:11.480> better 00:03:11.710 --> 00:03:11.720 align:start position:0% will be probably backs that are better 00:03:11.720 --> 00:03:13.690 align:start position:0% will be probably backs that are better solved<00:03:12.079> at<00:03:12.200> the<00:03:12.230> contract<00:03:12.980> level<00:03:13.040> than<00:03:13.459> at<00:03:13.579> the 00:03:13.690 --> 00:03:13.700 align:start position:0% solved at the contract level than at the 00:03:13.700 --> 00:03:17.470 align:start position:0% solved at the contract level than at the protocol<00:03:14.030> level<00:03:14.209> and<00:03:15.200> also<00:03:15.500> like<00:03:16.030> we're<00:03:17.030> very 00:03:17.470 --> 00:03:17.480 align:start position:0% protocol level and also like we're very 00:03:17.480 --> 00:03:19.860 align:start position:0% protocol level and also like we're very young<00:03:17.720> so<00:03:18.049> there<00:03:18.349> will<00:03:18.620> be<00:03:18.769> probably<00:03:19.099> need<00:03:19.430> to 00:03:19.860 --> 00:03:19.870 align:start position:0% young so there will be probably need to 00:03:19.870 --> 00:03:22.119 align:start position:0% young so there will be probably need to upgrade<00:03:20.870> our<00:03:21.019> contracts<00:03:21.530> for<00:03:21.680> adding 00:03:22.119 --> 00:03:22.129 align:start position:0% upgrade our contracts for adding 00:03:22.129 --> 00:03:24.369 align:start position:0% upgrade our contracts for adding features<00:03:22.310> either<00:03:22.730> users<00:03:23.239> requests<00:03:24.199> in<00:03:24.349> the 00:03:24.369 --> 00:03:24.379 align:start position:0% features either users requests in the 00:03:24.379 --> 00:03:28.360 align:start position:0% features either users requests in the future<00:03:26.199> doing<00:03:27.199> average<00:03:27.590> right<00:03:27.829> is<00:03:28.010> something 00:03:28.360 --> 00:03:28.370 align:start position:0% future doing average right is something 00:03:28.370 --> 00:03:31.030 align:start position:0% future doing average right is something that<00:03:28.549> we<00:03:28.819> are<00:03:28.940> very<00:03:29.540> passionate<00:03:30.139> about<00:03:30.500> at<00:03:30.859> our 00:03:31.030 --> 00:03:31.040 align:start position:0% that we are very passionate about at our 00:03:31.040 --> 00:03:33.729 align:start position:0% that we are very passionate about at our gun<00:03:31.280> and<00:03:31.910> I<00:03:32.150> think<00:03:32.419> these<00:03:32.569> are<00:03:32.629> also<00:03:33.290> like<00:03:33.500> very 00:03:33.729 --> 00:03:33.739 align:start position:0% gun and I think these are also like very 00:03:33.739 --> 00:03:35.680 align:start position:0% gun and I think these are also like very obvious<00:03:34.129> points<00:03:34.459> but<00:03:34.609> it's<00:03:35.180> very<00:03:35.329> important 00:03:35.680 --> 00:03:35.690 align:start position:0% obvious points but it's very important 00:03:35.690 --> 00:03:37.479 align:start position:0% obvious points but it's very important that<00:03:35.870> these<00:03:36.139> my<00:03:36.440> contact<00:03:36.799> cap<00:03:36.919> rates<00:03:37.129> are<00:03:37.310> not 00:03:37.479 --> 00:03:37.489 align:start position:0% that these my contact cap rates are not 00:03:37.489 --> 00:03:40.240 align:start position:0% that these my contact cap rates are not controlled<00:03:37.910> by<00:03:38.000> just<00:03:38.359> one<00:03:38.599> entity<00:03:38.900> and<00:03:39.319> a<00:03:39.980> very 00:03:40.240 --> 00:03:40.250 align:start position:0% controlled by just one entity and a very 00:03:40.250 --> 00:03:41.470 align:start position:0% controlled by just one entity and a very important<00:03:40.579> point<00:03:40.669> is<00:03:40.940> if<00:03:41.180> they<00:03:41.329> are 00:03:41.470 --> 00:03:41.480 align:start position:0% important point is if they are 00:03:41.480 --> 00:03:44.050 align:start position:0% important point is if they are time-delayed<00:03:42.169> people<00:03:42.680> can<00:03:42.919> then<00:03:43.220> explore<00:03:43.879> the 00:03:44.050 --> 00:03:44.060 align:start position:0% time-delayed people can then explore the 00:03:44.060 --> 00:03:46.210 align:start position:0% time-delayed people can then explore the new<00:03:44.180> contract<00:03:44.660> and<00:03:44.840> decide<00:03:45.290> what<00:03:45.560> to<00:03:45.590> do<00:03:45.919> with 00:03:46.210 --> 00:03:46.220 align:start position:0% new contract and decide what to do with 00:03:46.220 --> 00:03:48.900 align:start position:0% new contract and decide what to do with it<00:03:46.449> and<00:03:47.449> also<00:03:47.780> having<00:03:48.199> an<00:03:48.290> efficient 00:03:48.900 --> 00:03:48.910 align:start position:0% it and also having an efficient 00:03:48.910 --> 00:03:51.939 align:start position:0% it and also having an efficient governance<00:03:49.910> process<00:03:50.329> we<00:03:50.480> before<00:03:50.989> doing<00:03:51.739> an 00:03:51.939 --> 00:03:51.949 align:start position:0% governance process we before doing an 00:03:51.949 --> 00:03:55.539 align:start position:0% governance process we before doing an upgrade<00:03:52.069> this<00:03:52.370> is<00:03:52.579> very<00:03:52.940> important<00:03:54.129> so<00:03:55.129> in 00:03:55.539 --> 00:03:55.549 align:start position:0% upgrade this is very important so in 00:03:55.549 --> 00:03:59.050 align:start position:0% upgrade this is very important so in this<00:03:56.419> road<00:03:57.319> of<00:03:57.590> doing<00:03:57.859> like<00:03:58.040> this<00:03:58.280> better<00:03:58.639> like 00:03:59.050 --> 00:03:59.060 align:start position:0% this road of doing like this better like 00:03:59.060 --> 00:04:01.030 align:start position:0% this road of doing like this better like and<00:03:59.329> future<00:03:59.720> prismatic<00:04:00.169> contrast<00:04:00.560> we<00:04:00.739> kind<00:04:00.949> of 00:04:01.030 --> 00:04:01.040 align:start position:0% and future prismatic contrast we kind of 00:04:01.040 --> 00:04:03.789 align:start position:0% and future prismatic contrast we kind of started<00:04:01.370> early<00:04:01.970> this<00:04:02.000> year<00:04:02.530> focusing<00:04:03.530> a<00:04:03.680> lot 00:04:03.789 --> 00:04:03.799 align:start position:0% started early this year focusing a lot 00:04:03.799 --> 00:04:06.460 align:start position:0% started early this year focusing a lot on<00:04:03.859> the<00:04:04.040> solidity<00:04:04.609> libraries<00:04:05.209> approach<00:04:05.599> the 00:04:06.460 --> 00:04:06.470 align:start position:0% on the solidity libraries approach the 00:04:06.470 --> 00:04:07.930 align:start position:0% on the solidity libraries approach the solidity<00:04:06.949> libraries<00:04:07.340> are<00:04:07.519> great<00:04:07.760> because 00:04:07.930 --> 00:04:07.940 align:start position:0% solidity libraries are great because 00:04:07.940 --> 00:04:09.879 align:start position:0% solidity libraries are great because they<00:04:08.299> allow<00:04:08.599> you<00:04:08.659> to<00:04:09.230> really<00:04:09.739> isolate 00:04:09.879 --> 00:04:09.889 align:start position:0% they allow you to really isolate 00:04:09.889 --> 00:04:12.039 align:start position:0% they allow you to really isolate different<00:04:10.609> logic<00:04:11.419> domains<00:04:11.720> that<00:04:11.870> your 00:04:12.039 --> 00:04:12.049 align:start position:0% different logic domains that your 00:04:12.049 --> 00:04:14.469 align:start position:0% different logic domains that your contracting<00:04:12.470> I<00:04:12.560> have<00:04:12.799> but<00:04:13.579> something<00:04:14.209> that<00:04:14.239> we 00:04:14.469 --> 00:04:14.479 align:start position:0% contracting I have but something that we 00:04:14.479 --> 00:04:17.529 align:start position:0% contracting I have but something that we found<00:04:14.690> is<00:04:15.049> like<00:04:15.549> the<00:04:16.549> problem<00:04:16.880> with<00:04:17.030> libraries 00:04:17.529 --> 00:04:17.539 align:start position:0% found is like the problem with libraries 00:04:17.539 --> 00:04:19.569 align:start position:0% found is like the problem with libraries is<00:04:17.690> that<00:04:17.720> they're<00:04:18.139> linked<00:04:19.130> at<00:04:19.220> compile<00:04:19.549> time 00:04:19.569 --> 00:04:19.579 align:start position:0% is that they're linked at compile time 00:04:19.579 --> 00:04:22.480 align:start position:0% is that they're linked at compile time so<00:04:20.180> you<00:04:20.239> cannot<00:04:20.659> really<00:04:20.720> operate<00:04:21.289> them<00:04:21.500> after 00:04:22.480 --> 00:04:22.490 align:start position:0% so you cannot really operate them after 00:04:22.490 --> 00:04:24.459 align:start position:0% so you cannot really operate them after doing<00:04:22.760> the<00:04:22.880> after<00:04:23.300> after<00:04:23.840> deploying<00:04:24.289> your 00:04:24.459 --> 00:04:24.469 align:start position:0% doing the after after deploying your 00:04:24.469 --> 00:04:27.459 align:start position:0% doing the after after deploying your contract<00:04:25.270> so<00:04:26.270> we<00:04:26.599> work<00:04:26.810> with<00:04:26.840> the<00:04:27.110> sapling 00:04:27.459 --> 00:04:27.469 align:start position:0% contract so we work with the sapling 00:04:27.469 --> 00:04:28.570 align:start position:0% contract so we work with the sapling guys<00:04:27.620> on 00:04:28.570 --> 00:04:28.580 align:start position:0% guys on 00:04:28.580 --> 00:04:31.480 align:start position:0% guys on doing<00:04:29.000> this<00:04:29.150> approach<00:04:29.479> to<00:04:30.009> operate<00:04:31.009> in<00:04:31.129> solid 00:04:31.480 --> 00:04:31.490 align:start position:0% doing this approach to operate in solid 00:04:31.490 --> 00:04:34.779 align:start position:0% doing this approach to operate in solid like<00:04:31.699> solidity<00:04:32.090> libraries<00:04:33.310> what<00:04:34.310> how<00:04:34.639> it 00:04:34.779 --> 00:04:34.789 align:start position:0% like solidity libraries what how it 00:04:34.789 --> 00:04:36.309 align:start position:0% like solidity libraries what how it basically<00:04:34.879> works<00:04:35.360> is<00:04:35.599> that<00:04:35.720> instead<00:04:36.169> of 00:04:36.309 --> 00:04:36.319 align:start position:0% basically works is that instead of 00:04:36.319 --> 00:04:38.200 align:start position:0% basically works is that instead of linking<00:04:36.500> to<00:04:36.860> a<00:04:36.949> specific<00:04:37.699> version<00:04:37.819> of<00:04:38.060> when 00:04:38.200 --> 00:04:38.210 align:start position:0% linking to a specific version of when 00:04:38.210 --> 00:04:41.350 align:start position:0% linking to a specific version of when library<00:04:38.599> we<00:04:39.080> would<00:04:39.379> link<00:04:39.830> it<00:04:40.009> to<00:04:40.310> a<00:04:40.360> proxy 00:04:41.350 --> 00:04:41.360 align:start position:0% library we would link it to a proxy 00:04:41.360 --> 00:04:43.240 align:start position:0% library we would link it to a proxy library<00:04:41.719> that<00:04:42.259> would<00:04:42.379> then<00:04:42.590> dispatch<00:04:42.949> the 00:04:43.240 --> 00:04:43.250 align:start position:0% library that would then dispatch the 00:04:43.250 --> 00:04:45.939 align:start position:0% library that would then dispatch the delivery<00:04:43.939> call<00:04:44.180> to<00:04:44.449> a<00:04:44.479> to<00:04:45.349> T<00:04:45.469> correct<00:04:45.710> my 00:04:45.939 --> 00:04:45.949 align:start position:0% delivery call to a to T correct my 00:04:45.949 --> 00:04:50.290 align:start position:0% delivery call to a to T correct my contract<00:04:47.800> this<00:04:48.800> was<00:04:49.340> interesting<00:04:49.669> because<00:04:50.030> it 00:04:50.290 --> 00:04:50.300 align:start position:0% contract this was interesting because it 00:04:50.300 --> 00:04:52.149 align:start position:0% contract this was interesting because it allowed<00:04:50.599> us<00:04:50.780> to<00:04:51.020> change<00:04:51.469> the<00:04:51.680> business<00:04:52.009> logic 00:04:52.149 --> 00:04:52.159 align:start position:0% allowed us to change the business logic 00:04:52.159 --> 00:04:54.339 align:start position:0% allowed us to change the business logic after<00:04:52.849> the<00:04:52.939> contract<00:04:53.330> was<00:04:53.360> deployed<00:04:53.750> by<00:04:54.319> the 00:04:54.339 --> 00:04:54.349 align:start position:0% after the contract was deployed by the 00:04:54.349 --> 00:04:56.709 align:start position:0% after the contract was deployed by the problem<00:04:54.680> with<00:04:54.800> it<00:04:54.979> is<00:04:55.159> like<00:04:55.189> it<00:04:56.150> didn't<00:04:56.539> allow 00:04:56.709 --> 00:04:56.719 align:start position:0% problem with it is like it didn't allow 00:04:56.719 --> 00:04:59.290 align:start position:0% problem with it is like it didn't allow us<00:04:56.960> to<00:04:57.169> modify<00:04:57.530> this<00:04:57.919> my<00:04:58.069> contract<00:04:58.490> avi1<00:04:58.939> see 00:04:59.290 --> 00:04:59.300 align:start position:0% us to modify this my contract avi1 see 00:04:59.300 --> 00:05:01.809 align:start position:0% us to modify this my contract avi1 see what's<00:04:59.539> avoid<00:04:59.870> so<00:05:00.199> it's<00:05:00.740> not<00:05:00.949> possible<00:05:01.400> to<00:05:01.610> add 00:05:01.809 --> 00:05:01.819 align:start position:0% what's avoid so it's not possible to add 00:05:01.819 --> 00:05:04.209 align:start position:0% what's avoid so it's not possible to add any<00:05:02.090> functions<00:05:02.539> to<00:05:02.659> the<00:05:02.690> contract<00:05:03.199> or<00:05:03.409> to<00:05:04.039> like 00:05:04.209 --> 00:05:04.219 align:start position:0% any functions to the contract or to like 00:05:04.219 --> 00:05:05.619 align:start position:0% any functions to the contract or to like change<00:05:04.639> one<00:05:04.940> of<00:05:05.090> the<00:05:05.180> function<00:05:05.509> parameters 00:05:05.619 --> 00:05:05.629 align:start position:0% change one of the function parameters 00:05:05.629 --> 00:05:07.779 align:start position:0% change one of the function parameters and<00:05:06.259> also<00:05:06.530> the<00:05:06.770> data<00:05:06.979> structures<00:05:07.490> that<00:05:07.520> you 00:05:07.779 --> 00:05:07.789 align:start position:0% and also the data structures that you 00:05:07.789 --> 00:05:10.779 align:start position:0% and also the data structures that you have<00:05:08.030> are<00:05:08.360> going<00:05:08.419> to<00:05:08.690> be<00:05:08.780> fixed<00:05:09.229> forever<00:05:09.789> so 00:05:10.779 --> 00:05:10.789 align:start position:0% have are going to be fixed forever so 00:05:10.789 --> 00:05:12.730 align:start position:0% have are going to be fixed forever so this<00:05:11.300> is<00:05:11.449> very<00:05:11.599> interesting<00:05:11.690> for<00:05:12.110> solving 00:05:12.730 --> 00:05:12.740 align:start position:0% this is very interesting for solving 00:05:12.740 --> 00:05:16.029 align:start position:0% this is very interesting for solving business<00:05:13.550> logic<00:05:13.849> PACs<00:05:14.300> but<00:05:14.719> it<00:05:15.440> isn't<00:05:15.889> as 00:05:16.029 --> 00:05:16.039 align:start position:0% business logic PACs but it isn't as 00:05:16.039 --> 00:05:18.869 align:start position:0% business logic PACs but it isn't as flexible<00:05:17.030> as<00:05:17.240> we<00:05:17.389> would<00:05:17.509> like<00:05:17.629> like<00:05:18.349> it<00:05:18.500> to<00:05:18.590> be 00:05:18.869 --> 00:05:18.879 align:start position:0% flexible as we would like like it to be 00:05:18.879 --> 00:05:22.450 align:start position:0% flexible as we would like like it to be so<00:05:19.879> with<00:05:20.779> this<00:05:20.900> in<00:05:21.050> mind<00:05:21.080> we<00:05:21.469> were<00:05:21.680> -<00:05:21.949> we<00:05:21.979> went 00:05:22.450 --> 00:05:22.460 align:start position:0% so with this in mind we were - we went 00:05:22.460 --> 00:05:24.909 align:start position:0% so with this in mind we were - we went to<00:05:22.550> even<00:05:23.270> simpler<00:05:23.810> approach<00:05:23.930> that<00:05:24.529> we<00:05:24.710> call 00:05:24.909 --> 00:05:24.919 align:start position:0% to even simpler approach that we call 00:05:24.919 --> 00:05:27.249 align:start position:0% to even simpler approach that we call the<00:05:25.099> delegate<00:05:25.520> proxy<00:05:25.940> but<00:05:26.180> like<00:05:26.599> how<00:05:27.110> it 00:05:27.249 --> 00:05:27.259 align:start position:0% the delegate proxy but like how it 00:05:27.259 --> 00:05:29.200 align:start position:0% the delegate proxy but like how it basically<00:05:27.529> works<00:05:28.009> it's<00:05:28.310> like<00:05:28.460> instead<00:05:29.150> of 00:05:29.200 --> 00:05:29.210 align:start position:0% basically works it's like instead of 00:05:29.210 --> 00:05:31.480 align:start position:0% basically works it's like instead of having<00:05:29.599> your<00:05:30.139> contract<00:05:31.009> logic<00:05:31.310> in<00:05:31.460> your 00:05:31.480 --> 00:05:31.490 align:start position:0% having your contract logic in your 00:05:31.490 --> 00:05:33.760 align:start position:0% having your contract logic in your contract<00:05:32.060> you<00:05:32.240> delegate<00:05:33.050> this<00:05:33.289> contract 00:05:33.760 --> 00:05:33.770 align:start position:0% contract you delegate this contract 00:05:33.770 --> 00:05:35.830 align:start position:0% contract you delegate this contract logic<00:05:34.069> to<00:05:34.250> a<00:05:34.279> different<00:05:34.759> contract<00:05:35.150> by<00:05:35.300> using<00:05:35.569> a 00:05:35.830 --> 00:05:35.840 align:start position:0% logic to a different contract by using a 00:05:35.840 --> 00:05:39.010 align:start position:0% logic to a different contract by using a delegate<00:05:36.259> call<00:05:37.270> this<00:05:38.270> code<00:05:38.449> is<00:05:38.599> specially 00:05:39.010 --> 00:05:39.020 align:start position:0% delegate call this code is specially 00:05:39.020 --> 00:05:41.290 align:start position:0% delegate call this code is specially better<00:05:39.199> with<00:05:39.740> the<00:05:39.979> with<00:05:40.460> after<00:05:40.849> device<00:05:41.090> and 00:05:41.290 --> 00:05:41.300 align:start position:0% better with the with after device and 00:05:41.300 --> 00:05:45.490 align:start position:0% better with the with after device and Jim<00:05:41.449> Hartford<00:05:41.900> by<00:05:42.199> when<00:05:42.680> the<00:05:42.919> EIP<00:05:44.289> 211<00:05:45.289> good 00:05:45.490 --> 00:05:45.500 align:start position:0% Jim Hartford by when the EIP 211 good 00:05:45.500 --> 00:05:47.529 align:start position:0% Jim Hartford by when the EIP 211 good code<00:05:45.860> included<00:05:46.279> because<00:05:46.729> right<00:05:47.060> now<00:05:47.240> it 00:05:47.529 --> 00:05:47.539 align:start position:0% code included because right now it 00:05:47.539 --> 00:05:49.779 align:start position:0% code included because right now it allows<00:05:47.779> us<00:05:48.080> to<00:05:48.440> by<00:05:48.919> using<00:05:49.099> the<00:05:49.310> return<00:05:49.490> data 00:05:49.779 --> 00:05:49.789 align:start position:0% allows us to by using the return data 00:05:49.789 --> 00:05:51.490 align:start position:0% allows us to by using the return data size<00:05:50.180> and<00:05:50.449> return<00:05:50.719> date<00:05:50.750> a<00:05:50.870> cop<00:05:51.080> in<00:05:51.229> Europe 00:05:51.490 --> 00:05:51.500 align:start position:0% size and return date a cop in Europe 00:05:51.500 --> 00:05:53.680 align:start position:0% size and return date a cop in Europe codes<00:05:51.740> we<00:05:52.279> can<00:05:52.460> check<00:05:52.729> after<00:05:53.330> doing<00:05:53.599> a 00:05:53.680 --> 00:05:53.690 align:start position:0% codes we can check after doing a 00:05:53.690 --> 00:05:55.659 align:start position:0% codes we can check after doing a delegate<00:05:54.050> call<00:05:54.319> or<00:05:54.500> whatever<00:05:54.710> call<00:05:55.099> we<00:05:55.520> can 00:05:55.659 --> 00:05:55.669 align:start position:0% delegate call or whatever call we can 00:05:55.669 --> 00:05:58.119 align:start position:0% delegate call or whatever call we can see<00:05:55.909> how<00:05:56.330> many<00:05:56.389> bytes<00:05:56.900> did<00:05:57.349> the<00:05:57.560> underlying 00:05:58.119 --> 00:05:58.129 align:start position:0% see how many bytes did the underlying 00:05:58.129 --> 00:06:00.369 align:start position:0% see how many bytes did the underlying call<00:05:58.430> return<00:05:58.729> and<00:05:58.940> then<00:05:59.360> return<00:05:59.839> that<00:06:00.050> many 00:06:00.369 --> 00:06:00.379 align:start position:0% call return and then return that many 00:06:00.379 --> 00:06:03.579 align:start position:0% call return and then return that many data<00:06:00.909> because<00:06:01.909> before<00:06:02.360> this<00:06:02.509> you<00:06:02.960> kind<00:06:03.199> of<00:06:03.349> had 00:06:03.579 --> 00:06:03.589 align:start position:0% data because before this you kind of had 00:06:03.589 --> 00:06:05.709 align:start position:0% data because before this you kind of had to<00:06:03.889> specify<00:06:04.550> how<00:06:04.879> many<00:06:05.089> bytes<00:06:05.330> you<00:06:05.539> were 00:06:05.709 --> 00:06:05.719 align:start position:0% to specify how many bytes you were 00:06:05.719 --> 00:06:07.990 align:start position:0% to specify how many bytes you were expecting<00:06:06.169> from<00:06:06.319> the<00:06:06.469> call<00:06:06.650> and<00:06:06.830> for<00:06:07.520> function 00:06:07.990 --> 00:06:08.000 align:start position:0% expecting from the call and for function 00:06:08.000 --> 00:06:09.939 align:start position:0% expecting from the call and for function calls<00:06:08.029> every<00:06:08.509> turn<00:06:08.690> dynamic<00:06:08.930> data<00:06:09.319> types<00:06:09.620> this 00:06:09.939 --> 00:06:09.949 align:start position:0% calls every turn dynamic data types this 00:06:09.949 --> 00:06:14.559 align:start position:0% calls every turn dynamic data types this wasn't<00:06:10.159> really<00:06:10.400> a<00:06:10.879> good<00:06:11.360> idea<00:06:12.370> and<00:06:13.449> using<00:06:14.449> this 00:06:14.559 --> 00:06:14.569 align:start position:0% wasn't really a good idea and using this 00:06:14.569 --> 00:06:16.209 align:start position:0% wasn't really a good idea and using this technique<00:06:14.900> they're<00:06:15.229> like<00:06:15.529> two<00:06:15.800> things<00:06:16.039> that 00:06:16.209 --> 00:06:16.219 align:start position:0% technique they're like two things that 00:06:16.219 --> 00:06:17.860 align:start position:0% technique they're like two things that we<00:06:16.310> can<00:06:16.520> do<00:06:16.639> here<00:06:16.940> which<00:06:17.270> we<00:06:17.539> call<00:06:17.690> like 00:06:17.860 --> 00:06:17.870 align:start position:0% we can do here which we call like 00:06:17.870 --> 00:06:21.369 align:start position:0% we can do here which we call like flavors<00:06:18.490> but<00:06:19.490> they're<00:06:19.819> like<00:06:20.000> based<00:06:20.839> on<00:06:20.990> the<00:06:21.139> on 00:06:21.369 --> 00:06:21.379 align:start position:0% flavors but they're like based on the on 00:06:21.379 --> 00:06:23.709 align:start position:0% flavors but they're like based on the on this<00:06:21.589> same<00:06:22.009> idea<00:06:22.129> the<00:06:22.879> first<00:06:23.060> one<00:06:23.240> is<00:06:23.479> like 00:06:23.709 --> 00:06:23.719 align:start position:0% this same idea the first one is like 00:06:23.719 --> 00:06:26.260 align:start position:0% this same idea the first one is like this<00:06:24.650> was<00:06:24.800> introduced<00:06:25.219> by<00:06:25.279> Vitalik<00:06:25.759> and<00:06:26.150> we're 00:06:26.260 --> 00:06:26.270 align:start position:0% this was introduced by Vitalik and we're 00:06:26.270 --> 00:06:27.790 align:start position:0% this was introduced by Vitalik and we're ready<00:06:26.479> post<00:06:26.779> back<00:06:26.990> in<00:06:27.169> back<00:06:27.440> in<00:06:27.560> the<00:06:27.620> summer 00:06:27.790 --> 00:06:27.800 align:start position:0% ready post back in back in the summer 00:06:27.800 --> 00:06:31.570 align:start position:0% ready post back in back in the summer and<00:06:28.699> it's<00:06:29.029> a<00:06:29.300> div<00:06:29.569> of<00:06:30.379> stagger<00:06:30.889> D<00:06:31.039> is<00:06:31.159> static 00:06:31.570 --> 00:06:31.580 align:start position:0% and it's a div of stagger D is static 00:06:31.580 --> 00:06:33.189 align:start position:0% and it's a div of stagger D is static forwarders<00:06:32.029> so<00:06:32.240> it<00:06:32.389> doesn't<00:06:32.690> really<00:06:32.930> solve 00:06:33.189 --> 00:06:33.199 align:start position:0% forwarders so it doesn't really solve 00:06:33.199 --> 00:06:36.369 align:start position:0% forwarders so it doesn't really solve the<00:06:33.349> availability<00:06:33.830> feature<00:06:34.819> but<00:06:35.629> the<00:06:35.900> idea<00:06:36.110> is 00:06:36.369 --> 00:06:36.379 align:start position:0% the availability feature but the idea is 00:06:36.379 --> 00:06:38.949 align:start position:0% the availability feature but the idea is like<00:06:36.649> we<00:06:37.159> can<00:06:37.399> deploy<00:06:37.759> these<00:06:38.149> very<00:06:38.419> very<00:06:38.630> cheap 00:06:38.949 --> 00:06:38.959 align:start position:0% like we can deploy these very very cheap 00:06:38.959 --> 00:06:40.269 align:start position:0% like we can deploy these very very cheap contracts<00:06:39.500> this<00:06:39.740> is<00:06:39.860> actually<00:06:40.190> an 00:06:40.269 --> 00:06:40.279 align:start position:0% contracts this is actually an 00:06:40.279 --> 00:06:41.769 align:start position:0% contracts this is actually an implementation<00:06:40.940> it<00:06:41.029> they<00:06:41.240> are<00:06:41.360> so<00:06:41.539> simple 00:06:41.769 --> 00:06:41.779 align:start position:0% implementation it they are so simple 00:06:41.779 --> 00:06:42.430 align:start position:0% implementation it they are so simple that<00:06:42.080> this 00:06:42.430 --> 00:06:42.440 align:start position:0% that this 00:06:42.440 --> 00:06:45.090 align:start position:0% that this plantation<00:06:42.950> Western<00:06:43.340> directly<00:06:43.820> Navy<00:06:44.150> m-code 00:06:45.090 --> 00:06:45.100 align:start position:0% plantation Western directly Navy m-code 00:06:45.100 --> 00:06:48.250 align:start position:0% plantation Western directly Navy m-code so<00:06:46.100> this<00:06:46.280> allows<00:06:46.550> us<00:06:46.580> to<00:06:47.000> really<00:06:47.510> put<00:06:47.840> like<00:06:48.020> to 00:06:48.250 --> 00:06:48.260 align:start position:0% so this allows us to really put like to 00:06:48.260 --> 00:06:50.050 align:start position:0% so this allows us to really put like to deploy<00:06:48.470> clone<00:06:48.830> contracts<00:06:49.280> of<00:06:49.400> one<00:06:49.580> contract 00:06:50.050 --> 00:06:50.060 align:start position:0% deploy clone contracts of one contract 00:06:50.060 --> 00:06:53.440 align:start position:0% deploy clone contracts of one contract for<00:06:50.330> a<00:06:50.660> very<00:06:50.930> tiny<00:06:51.170> amount<00:06:51.320> of<00:06:51.740> of<00:06:52.010> gas<00:06:52.580> and 00:06:53.440 --> 00:06:53.450 align:start position:0% for a very tiny amount of of gas and 00:06:53.450 --> 00:06:54.820 align:start position:0% for a very tiny amount of of gas and this<00:06:53.600> is<00:06:53.720> actually<00:06:54.050> the<00:06:54.170> desolated 00:06:54.820 --> 00:06:54.830 align:start position:0% this is actually the desolated 00:06:54.830 --> 00:06:57.010 align:start position:0% this is actually the desolated implementation<00:06:55.520> done<00:06:55.730> with<00:06:55.970> the<00:06:56.150> from<00:06:56.930> the 00:06:57.010 --> 00:06:57.020 align:start position:0% implementation done with the from the 00:06:57.020 --> 00:07:00.370 align:start position:0% implementation done with the from the code<00:06:57.200> that<00:06:57.410> that<00:06:57.770> we<00:06:58.270> before<00:06:59.270> so<00:06:59.870> these<00:07:00.200> are 00:07:00.370 --> 00:07:00.380 align:start position:0% code that that we before so these are 00:07:00.380 --> 00:07:02.380 align:start position:0% code that that we before so these are like<00:07:00.620> very<00:07:00.890> very<00:07:00.980> cheap<00:07:01.520> to<00:07:01.640> deploy<00:07:01.910> contracts 00:07:02.380 --> 00:07:02.390 align:start position:0% like very very cheap to deploy contracts 00:07:02.390 --> 00:07:03.730 align:start position:0% like very very cheap to deploy contracts and<00:07:02.570> it's<00:07:02.780> like<00:07:03.080> as<00:07:03.200> you<00:07:03.320> can<00:07:03.440> see<00:07:03.590> it's<00:07:03.710> very 00:07:03.730 --> 00:07:03.740 align:start position:0% and it's like as you can see it's very 00:07:03.740 --> 00:07:07.090 align:start position:0% and it's like as you can see it's very trivial<00:07:04.720> deploying<00:07:05.720> with<00:07:05.870> this<00:07:06.050> is<00:07:06.290> like<00:07:06.560> for 00:07:07.090 --> 00:07:07.100 align:start position:0% trivial deploying with this is like for 00:07:07.100 --> 00:07:09.880 align:start position:0% trivial deploying with this is like for every<00:07:07.430> call<00:07:07.730> to<00:07:08.030> these<00:07:08.270> contracts<00:07:08.930> we<00:07:09.440> add<00:07:09.650> an 00:07:09.880 --> 00:07:09.890 align:start position:0% every call to these contracts we add an 00:07:09.890 --> 00:07:11.770 align:start position:0% every call to these contracts we add an overhead<00:07:10.310> of<00:07:10.460> gas<00:07:10.640> because<00:07:10.970> we<00:07:11.270> need<00:07:11.420> to<00:07:11.600> do 00:07:11.770 --> 00:07:11.780 align:start position:0% overhead of gas because we need to do 00:07:11.780 --> 00:07:15.130 align:start position:0% overhead of gas because we need to do this<00:07:12.080> this<00:07:12.530> delegate<00:07:12.920> call<00:07:13.190> so<00:07:13.790> for<00:07:14.690> example 00:07:15.130 --> 00:07:15.140 align:start position:0% this this delegate call so for example 00:07:15.140 --> 00:07:16.870 align:start position:0% this this delegate call so for example this<00:07:15.530> is<00:07:15.710> not<00:07:15.740> a<00:07:15.920> good<00:07:16.100> idea<00:07:16.190> for<00:07:16.400> a<00:07:16.580> talking 00:07:16.870 --> 00:07:16.880 align:start position:0% this is not a good idea for a talking 00:07:16.880 --> 00:07:18.610 align:start position:0% this is not a good idea for a talking contract<00:07:17.270> that<00:07:17.360> gets<00:07:17.600> interacted<00:07:18.140> with<00:07:18.290> in 00:07:18.610 --> 00:07:18.620 align:start position:0% contract that gets interacted with in 00:07:18.620 --> 00:07:21.220 align:start position:0% contract that gets interacted with in many<00:07:18.890> instances<00:07:19.520> the<00:07:20.060> gas<00:07:20.600> course<00:07:20.870> is<00:07:21.050> like 00:07:21.220 --> 00:07:21.230 align:start position:0% many instances the gas course is like 00:07:21.230 --> 00:07:23.920 align:start position:0% many instances the gas course is like 700<00:07:21.650> gas<00:07:22.430> for<00:07:22.820> every<00:07:23.150> additional<00:07:23.330> delegate 00:07:23.920 --> 00:07:23.930 align:start position:0% 700 gas for every additional delegate 00:07:23.930 --> 00:07:25.600 align:start position:0% 700 gas for every additional delegate call<00:07:24.170> that<00:07:24.350> we<00:07:24.410> have<00:07:24.560> to<00:07:24.680> pay<00:07:24.830> in<00:07:24.890> every<00:07:25.190> in 00:07:25.600 --> 00:07:25.610 align:start position:0% call that we have to pay in every in 00:07:25.610 --> 00:07:28.120 align:start position:0% call that we have to pay in every in every<00:07:25.760> call<00:07:26.090> but<00:07:26.930> in<00:07:27.140> the<00:07:27.200> flipside<00:07:27.590> we<00:07:27.920> get 00:07:28.120 --> 00:07:28.130 align:start position:0% every call but in the flipside we get 00:07:28.130 --> 00:07:30.580 align:start position:0% every call but in the flipside we get very<00:07:28.460> very<00:07:28.610> cheap<00:07:29.170> contract<00:07:30.170> deployment 00:07:30.580 --> 00:07:30.590 align:start position:0% very very cheap contract deployment 00:07:30.590 --> 00:07:33.820 align:start position:0% very very cheap contract deployment costs<00:07:31.100> so<00:07:31.580> for<00:07:31.820> example<00:07:32.240> for<00:07:32.570> a<00:07:32.680> contract<00:07:33.680> that 00:07:33.820 --> 00:07:33.830 align:start position:0% costs so for example for a contract that 00:07:33.830 --> 00:07:36.040 align:start position:0% costs so for example for a contract that takes<00:07:34.160> 1<00:07:34.550> million<00:07:34.820> guys<00:07:34.970> to<00:07:35.180> deploy<00:07:35.420> the 00:07:36.040 --> 00:07:36.050 align:start position:0% takes 1 million guys to deploy the 00:07:36.050 --> 00:07:38.710 align:start position:0% takes 1 million guys to deploy the moment<00:07:36.380> that<00:07:36.500> we<00:07:36.620> do<00:07:36.800> more<00:07:37.190> than<00:07:37.720> 1300 00:07:38.710 --> 00:07:38.720 align:start position:0% moment that we do more than 1300 00:07:38.720 --> 00:07:41.680 align:start position:0% moment that we do more than 1300 contracts<00:07:39.440> called<00:07:39.800> duties<00:07:40.250> contract<00:07:41.030> it<00:07:41.450> will 00:07:41.680 --> 00:07:41.690 align:start position:0% contracts called duties contract it will 00:07:41.690 --> 00:07:44.680 align:start position:0% contracts called duties contract it will no<00:07:41.990> longer<00:07:42.260> be<00:07:42.650> worth<00:07:42.830> it<00:07:43.100> in<00:07:43.370> gas<00:07:43.700> wise<00:07:43.940> to<00:07:44.540> do 00:07:44.680 --> 00:07:44.690 align:start position:0% no longer be worth it in gas wise to do 00:07:44.690 --> 00:07:47.409 align:start position:0% no longer be worth it in gas wise to do it<00:07:44.810> but<00:07:45.440> for<00:07:45.650> example<00:07:45.770> and<00:07:46.250> an<00:07:46.850> example<00:07:47.150> of<00:07:47.330> a 00:07:47.409 --> 00:07:47.419 align:start position:0% it but for example and an example of a 00:07:47.419 --> 00:07:48.970 align:start position:0% it but for example and an example of a contract<00:07:47.720> that<00:07:47.990> I<00:07:48.169> think<00:07:48.470> it's<00:07:48.560> a<00:07:48.650> perfect 00:07:48.970 --> 00:07:48.980 align:start position:0% contract that I think it's a perfect 00:07:48.980 --> 00:07:51.940 align:start position:0% contract that I think it's a perfect example<00:07:49.100> to<00:07:49.850> how<00:07:50.240> these<00:07:50.630> can<00:07:50.900> be<00:07:51.020> used<00:07:51.230> is<00:07:51.590> with 00:07:51.940 --> 00:07:51.950 align:start position:0% example to how these can be used is with 00:07:51.950 --> 00:07:54.460 align:start position:0% example to how these can be used is with the<00:07:52.070> en<00:07:52.340> STD<00:07:52.760> contract<00:07:53.210> that<00:07:53.540> gets<00:07:53.870> basically 00:07:54.460 --> 00:07:54.470 align:start position:0% the en STD contract that gets basically 00:07:54.470 --> 00:07:57.670 align:start position:0% the en STD contract that gets basically created<00:07:54.950> every<00:07:55.250> time<00:07:55.490> an<00:07:55.700> SPD<00:07:56.300> is<00:07:56.630> done<00:07:56.870> so 00:07:57.670 --> 00:07:57.680 align:start position:0% created every time an SPD is done so 00:07:57.680 --> 00:08:00.220 align:start position:0% created every time an SPD is done so with<00:07:57.980> this<00:07:58.100> contract<00:07:58.610> if<00:07:59.570> instead<00:08:00.020> of 00:08:00.220 --> 00:08:00.230 align:start position:0% with this contract if instead of 00:08:00.230 --> 00:08:02.470 align:start position:0% with this contract if instead of creating<00:08:00.740> a<00:08:00.980> full<00:08:01.280> contract<00:08:01.730> with<00:08:01.970> with<00:08:02.300> its 00:08:02.470 --> 00:08:02.480 align:start position:0% creating a full contract with with its 00:08:02.480 --> 00:08:04.210 align:start position:0% creating a full contract with with its code<00:08:02.750> that<00:08:03.080> gets<00:08:03.380> stored<00:08:03.890> into<00:08:04.190> the 00:08:04.210 --> 00:08:04.220 align:start position:0% code that gets stored into the 00:08:04.220 --> 00:08:07.480 align:start position:0% code that gets stored into the blockchain<00:08:04.490> every<00:08:04.820> time<00:08:05.030> we<00:08:05.630> created<00:08:06.050> a<00:08:06.490> proxy 00:08:07.480 --> 00:08:07.490 align:start position:0% blockchain every time we created a proxy 00:08:07.490 --> 00:08:09.280 align:start position:0% blockchain every time we created a proxy contract<00:08:07.880> like<00:08:08.030> this<00:08:08.060> this<00:08:08.840> would<00:08:09.020> have<00:08:09.169> been 00:08:09.280 --> 00:08:09.290 align:start position:0% contract like this this would have been 00:08:09.290 --> 00:08:11.770 align:start position:0% contract like this this would have been the<00:08:10.250> biggest<00:08:10.610> savings<00:08:10.910> would<00:08:11.300> have<00:08:11.419> been<00:08:11.570> very 00:08:11.770 --> 00:08:11.780 align:start position:0% the biggest savings would have been very 00:08:11.780 --> 00:08:14.470 align:start position:0% the biggest savings would have been very very<00:08:11.900> significant<00:08:12.650> and<00:08:13.520> I<00:08:13.700> think<00:08:13.730> this<00:08:14.120> is<00:08:14.270> the 00:08:14.470 --> 00:08:14.480 align:start position:0% very significant and I think this is the 00:08:14.480 --> 00:08:15.850 align:start position:0% very significant and I think this is the perfect<00:08:14.810> example<00:08:14.900> for<00:08:15.320> this<00:08:15.410> because<00:08:15.620> the 00:08:15.850 --> 00:08:15.860 align:start position:0% perfect example for this because the 00:08:15.860 --> 00:08:17.920 align:start position:0% perfect example for this because the contractor<00:08:16.340> gets<00:08:16.520> deployed<00:08:16.790> many<00:08:17.090> times<00:08:17.330> but 00:08:17.920 --> 00:08:17.930 align:start position:0% contractor gets deployed many times but 00:08:17.930 --> 00:08:22.290 align:start position:0% contractor gets deployed many times but gets<00:08:18.230> used<00:08:18.560> individually<00:08:18.800> very<00:08:19.340> little<00:08:19.910> times 00:08:22.290 --> 00:08:22.300 align:start position:0% 00:08:22.300 --> 00:08:26.950 align:start position:0% so<00:08:23.300> with<00:08:23.720> this<00:08:24.080> same<00:08:24.320> idea<00:08:24.669> we<00:08:25.669> can<00:08:26.330> like<00:08:26.720> if 00:08:26.950 --> 00:08:26.960 align:start position:0% so with this same idea we can like if 00:08:26.960 --> 00:08:29.590 align:start position:0% so with this same idea we can like if instead<00:08:27.350> of<00:08:27.530> these<00:08:28.000> at<00:08:29.000> Rice<00:08:29.270> that<00:08:29.300> we're 00:08:29.590 --> 00:08:29.600 align:start position:0% instead of these at Rice that we're 00:08:29.600 --> 00:08:31.960 align:start position:0% instead of these at Rice that we're doing<00:08:29.750> the<00:08:29.990> call<00:08:30.320> is<00:08:30.680> being<00:08:31.040> a<00:08:31.190> constant<00:08:31.640> if<00:08:31.820> we 00:08:31.960 --> 00:08:31.970 align:start position:0% doing the call is being a constant if we 00:08:31.970 --> 00:08:34.750 align:start position:0% doing the call is being a constant if we make<00:08:32.180> it<00:08:32.210> flexible<00:08:32.930> and<00:08:33.289> variable<00:08:34.070> we<00:08:34.550> can 00:08:34.750 --> 00:08:34.760 align:start position:0% make it flexible and variable we can 00:08:34.760 --> 00:08:36.550 align:start position:0% make it flexible and variable we can actually<00:08:34.940> do<00:08:35.419> a<00:08:35.660> great<00:08:35.839> ability<00:08:36.050> in<00:08:36.440> this 00:08:36.550 --> 00:08:36.560 align:start position:0% actually do a great ability in this 00:08:36.560 --> 00:08:38.829 align:start position:0% actually do a great ability in this indecent<00:08:37.250> way<00:08:37.400> so<00:08:37.940> here<00:08:38.390> is<00:08:38.510> like<00:08:38.690> an 00:08:38.829 --> 00:08:38.839 align:start position:0% indecent way so here is like an 00:08:38.839 --> 00:08:41.230 align:start position:0% indecent way so here is like an implementation<00:08:39.560> of<00:08:39.770> how<00:08:40.370> these<00:08:40.610> how<00:08:41.030> this 00:08:41.230 --> 00:08:41.240 align:start position:0% implementation of how these how this 00:08:41.240 --> 00:08:42.909 align:start position:0% implementation of how these how this could<00:08:41.390> look<00:08:41.419> like<00:08:41.750> as<00:08:41.960> you<00:08:42.169> can<00:08:42.289> see<00:08:42.469> this<00:08:42.740> is 00:08:42.909 --> 00:08:42.919 align:start position:0% could look like as you can see this is 00:08:42.919 --> 00:08:44.829 align:start position:0% could look like as you can see this is also<00:08:43.190> like<00:08:43.580> using<00:08:44.089> the<00:08:44.330> code<00:08:44.540> that<00:08:44.750> we 00:08:44.829 --> 00:08:44.839 align:start position:0% also like using the code that we 00:08:44.839 --> 00:08:46.960 align:start position:0% also like using the code that we presented<00:08:45.110> before<00:08:45.589> but<00:08:46.190> here<00:08:46.430> instead<00:08:46.790> of 00:08:46.960 --> 00:08:46.970 align:start position:0% presented before but here instead of 00:08:46.970 --> 00:08:49.570 align:start position:0% presented before but here instead of doing<00:08:47.720> the<00:08:47.870> dakotas<00:08:48.680> the<00:08:48.980> same<00:08:49.160> constant 00:08:49.570 --> 00:08:49.580 align:start position:0% doing the dakotas the same constant 00:08:49.580 --> 00:08:52.360 align:start position:0% doing the dakotas the same constant address<00:08:49.850> every<00:08:50.210> time<00:08:50.420> we're<00:08:51.020> doing<00:08:51.320> it<00:08:51.470> to<00:08:51.710> to 00:08:52.360 --> 00:08:52.370 align:start position:0% address every time we're doing it to to 00:08:52.370 --> 00:08:54.280 align:start position:0% address every time we're doing it to to add<00:08:52.490> an<00:08:52.670> add<00:08:52.940> to<00:08:53.180> an<00:08:53.420> address<00:08:53.750> that<00:08:53.780> we<00:08:54.110> can 00:08:54.280 --> 00:08:54.290 align:start position:0% add an add to an address that we can 00:08:54.290 --> 00:08:54.730 align:start position:0% add an add to an address that we can change 00:08:54.730 --> 00:08:54.740 align:start position:0% change 00:08:54.740 --> 00:08:56.060 align:start position:0% change so<00:08:55.010> basically<00:08:55.400> calling 00:08:56.060 --> 00:08:56.070 align:start position:0% so basically calling 00:08:56.070 --> 00:08:57.950 align:start position:0% so basically calling the<00:08:56.130> average<00:08:56.490> function<00:08:56.670> here<00:08:57.150> would<00:08:57.660> change 00:08:57.950 --> 00:08:57.960 align:start position:0% the average function here would change 00:08:57.960 --> 00:09:00.320 align:start position:0% the average function here would change the<00:08:58.140> code<00:08:58.380> where<00:08:58.890> the<00:08:58.920> where<00:08:59.370> the<00:08:59.400> contract<00:08:59.910> is 00:09:00.320 --> 00:09:00.330 align:start position:0% the code where the where the contract is 00:09:00.330 --> 00:09:04.130 align:start position:0% the code where the where the contract is using<00:09:01.370> the<00:09:02.370> problem<00:09:02.700> with<00:09:03.450> this<00:09:03.630> is<00:09:03.930> like 00:09:04.130 --> 00:09:04.140 align:start position:0% using the problem with this is like 00:09:04.140 --> 00:09:06.260 align:start position:0% using the problem with this is like because<00:09:04.800> we're<00:09:04.980> using<00:09:05.190> delegate<00:09:05.700> calls<00:09:05.970> which 00:09:06.260 --> 00:09:06.270 align:start position:0% because we're using delegate calls which 00:09:06.270 --> 00:09:08.780 align:start position:0% because we're using delegate calls which is<00:09:06.300> basically<00:09:06.810> telling<00:09:07.110> the<00:09:07.350> contract<00:09:07.830> okay 00:09:08.780 --> 00:09:08.790 align:start position:0% is basically telling the contract okay 00:09:08.790 --> 00:09:11.600 align:start position:0% is basically telling the contract okay don't<00:09:09.600> run<00:09:09.780> my<00:09:09.930> code<00:09:10.200> my<00:09:10.560> contract<00:09:10.980> out<00:09:11.130> here<00:09:11.430> I 00:09:11.600 --> 00:09:11.610 align:start position:0% don't run my code my contract out here I 00:09:11.610 --> 00:09:13.100 align:start position:0% don't run my code my contract out here I want<00:09:11.880> to<00:09:11.970> tell<00:09:12.150> achates<00:09:12.540> to<00:09:12.720> tease<00:09:12.870> order 00:09:13.100 --> 00:09:13.110 align:start position:0% want to tell achates to tease order 00:09:13.110 --> 00:09:15.320 align:start position:0% want to tell achates to tease order address<00:09:13.470> we<00:09:14.070> need<00:09:14.100> to<00:09:14.460> make<00:09:14.640> sure<00:09:14.820> that<00:09:15.150> this 00:09:15.320 --> 00:09:15.330 align:start position:0% address we need to make sure that this 00:09:15.330 --> 00:09:17.000 align:start position:0% address we need to make sure that this storage<00:09:15.660> like<00:09:16.290> we're<00:09:16.530> in<00:09:16.620> the<00:09:16.740> correct 00:09:17.000 --> 00:09:17.010 align:start position:0% storage like we're in the correct 00:09:17.010 --> 00:09:19.670 align:start position:0% storage like we're in the correct version<00:09:17.220> of<00:09:17.460> the<00:09:17.580> storage<00:09:17.900> so<00:09:18.900> for<00:09:19.110> example<00:09:19.530> in 00:09:19.670 --> 00:09:19.680 align:start position:0% version of the storage so for example in 00:09:19.680 --> 00:09:21.980 align:start position:0% version of the storage so for example in the<00:09:20.160> previous<00:09:20.310> slide<00:09:20.790> we<00:09:21.120> see<00:09:21.480> that<00:09:21.510> both 00:09:21.980 --> 00:09:21.990 align:start position:0% the previous slide we see that both 00:09:21.990 --> 00:09:25.790 align:start position:0% the previous slide we see that both contracts<00:09:22.470> like<00:09:22.890> inherit<00:09:23.490> the<00:09:23.610> same<00:09:24.620> the<00:09:25.620> same 00:09:25.790 --> 00:09:25.800 align:start position:0% contracts like inherit the same the same 00:09:25.800 --> 00:09:27.890 align:start position:0% contracts like inherit the same the same storage<00:09:26.130> contract<00:09:26.700> that's<00:09:27.180> because<00:09:27.540> they 00:09:27.890 --> 00:09:27.900 align:start position:0% storage contract that's because they 00:09:27.900 --> 00:09:29.450 align:start position:0% storage contract that's because they both<00:09:28.050> need<00:09:28.260> to<00:09:28.440> know<00:09:28.590> where<00:09:29.010> the<00:09:29.130> where<00:09:29.430> the 00:09:29.450 --> 00:09:29.460 align:start position:0% both need to know where the where the 00:09:29.460 --> 00:09:32.420 align:start position:0% both need to know where the where the story<00:09:29.790> is<00:09:30.150> and<00:09:30.330> for<00:09:30.750> more<00:09:31.110> more<00:09:31.770> complex<00:09:32.220> cases 00:09:32.420 --> 00:09:32.430 align:start position:0% story is and for more more complex cases 00:09:32.430 --> 00:09:34.670 align:start position:0% story is and for more more complex cases in<00:09:32.760> which<00:09:32.880> you<00:09:33.120> introducing<00:09:33.690> inheritance<00:09:34.470> and 00:09:34.670 --> 00:09:34.680 align:start position:0% in which you introducing inheritance and 00:09:34.680 --> 00:09:37.370 align:start position:0% in which you introducing inheritance and all<00:09:35.010> that<00:09:35.220> you<00:09:35.730> need<00:09:35.880> to<00:09:36.000> be<00:09:36.240> very<00:09:36.810> careful 00:09:37.370 --> 00:09:37.380 align:start position:0% all that you need to be very careful 00:09:37.380 --> 00:09:40.820 align:start position:0% all that you need to be very careful with<00:09:37.980> how<00:09:38.520> you<00:09:38.580> add<00:09:39.090> the<00:09:39.510> the<00:09:39.840> storage<00:09:40.230> so<00:09:40.530> this 00:09:40.820 --> 00:09:40.830 align:start position:0% with how you add the the storage so this 00:09:40.830 --> 00:09:43.580 align:start position:0% with how you add the the storage so this is<00:09:40.950> actually<00:09:41.600> important<00:09:42.600> to<00:09:42.780> understand<00:09:43.320> how 00:09:43.580 --> 00:09:43.590 align:start position:0% is actually important to understand how 00:09:43.590 --> 00:09:46.690 align:start position:0% is actually important to understand how solid<00:09:44.010> it<00:09:44.130> is<00:09:44.250> historian<00:09:44.820> or<00:09:45.000> or<00:09:45.420> data<00:09:45.750> so 00:09:46.690 --> 00:09:46.700 align:start position:0% solid it is historian or or data so 00:09:46.700 --> 00:09:49.370 align:start position:0% solid it is historian or or data so basically<00:09:47.700> the<00:09:48.000> the<00:09:48.240> the<00:09:48.570> it's<00:09:48.900> a<00:09:48.990> very<00:09:49.020> simple 00:09:49.370 --> 00:09:49.380 align:start position:0% basically the the the it's a very simple 00:09:49.380 --> 00:09:52.520 align:start position:0% basically the the the it's a very simple idea<00:09:49.610> it<00:09:50.610> starts<00:09:51.060> counting<00:09:51.270> like<00:09:51.720> how<00:09:52.290> many 00:09:52.520 --> 00:09:52.530 align:start position:0% idea it starts counting like how many 00:09:52.530 --> 00:09:54.650 align:start position:0% idea it starts counting like how many men<00:09:52.770> like<00:09:53.040> storage<00:09:53.580> slots<00:09:53.850> do<00:09:54.180> you<00:09:54.270> have<00:09:54.450> in 00:09:54.650 --> 00:09:54.660 align:start position:0% men like storage slots do you have in 00:09:54.660 --> 00:09:56.660 align:start position:0% men like storage slots do you have in your<00:09:54.750> contract<00:09:55.200> starting<00:09:55.650> for<00:09:55.890> the<00:09:55.920> from<00:09:56.580> the 00:09:56.660 --> 00:09:56.670 align:start position:0% your contract starting for the from the 00:09:56.670 --> 00:09:58.700 align:start position:0% your contract starting for the from the most<00:09:56.880> basic<00:09:57.240> contract<00:09:57.660> so<00:09:58.080> it<00:09:58.350> would<00:09:58.500> start 00:09:58.700 --> 00:09:58.710 align:start position:0% most basic contract so it would start 00:09:58.710 --> 00:10:00.530 align:start position:0% most basic contract so it would start like<00:09:58.920> counting<00:09:59.340> like<00:09:59.550> this<00:09:59.910> would<00:10:00.090> be<00:10:00.210> stored 00:10:00.530 --> 00:10:00.540 align:start position:0% like counting like this would be stored 00:10:00.540 --> 00:10:02.870 align:start position:0% like counting like this would be stored at<00:10:00.690> the<00:10:00.720> at<00:10:01.050> the<00:10:01.230> 0th<00:10:01.650> at<00:10:02.130> the<00:10:02.310> cereal<00:10:02.610> slot 00:10:02.870 --> 00:10:02.880 align:start position:0% at the at the 0th at the cereal slot 00:10:02.880 --> 00:10:04.880 align:start position:0% at the at the 0th at the cereal slot we're<00:10:03.450> talking<00:10:03.720> about<00:10:03.930> the<00:10:04.020> these<00:10:04.470> contact 00:10:04.880 --> 00:10:04.890 align:start position:0% we're talking about the these contact 00:10:04.890 --> 00:10:06.350 align:start position:0% we're talking about the these contact storage<00:10:05.190> but<00:10:05.370> either<00:10:05.610> inherits<00:10:06.060> from<00:10:06.120> this 00:10:06.350 --> 00:10:06.360 align:start position:0% storage but either inherits from this 00:10:06.360 --> 00:10:08.240 align:start position:0% storage but either inherits from this one<00:10:06.540> so<00:10:07.110> these<00:10:07.350> would<00:10:07.560> be<00:10:07.710> stored<00:10:08.010> at<00:10:08.130> the 00:10:08.240 --> 00:10:08.250 align:start position:0% one so these would be stored at the 00:10:08.250 --> 00:10:10.280 align:start position:0% one so these would be stored at the zeros<00:10:08.610> cloud<00:10:08.850> these<00:10:09.330> would<00:10:09.540> be<00:10:09.630> stored<00:10:09.930> at<00:10:10.110> the 00:10:10.280 --> 00:10:10.290 align:start position:0% zeros cloud these would be stored at the 00:10:10.290 --> 00:10:12.830 align:start position:0% zeros cloud these would be stored at the at<00:10:10.560> the<00:10:10.710> first<00:10:11.400> slot<00:10:11.670> of<00:10:11.910> the<00:10:11.940> of<00:10:12.270> the<00:10:12.420> contract 00:10:12.830 --> 00:10:12.840 align:start position:0% at the first slot of the of the contract 00:10:12.840 --> 00:10:15.470 align:start position:0% at the first slot of the of the contract and<00:10:12.960> so<00:10:13.140> on<00:10:13.320> and<00:10:13.440> so<00:10:13.590> forth<00:10:14.210> but<00:10:15.210> for<00:10:15.420> example 00:10:15.470 --> 00:10:15.480 align:start position:0% and so on and so forth but for example 00:10:15.480 --> 00:10:18.260 align:start position:0% and so on and so forth but for example in<00:10:15.930> the<00:10:16.050> case<00:10:16.170> of<00:10:16.230> an<00:10:16.470> extract<00:10:16.920> this<00:10:17.670> would<00:10:18.060> be 00:10:18.260 --> 00:10:18.270 align:start position:0% in the case of an extract this would be 00:10:18.270 --> 00:10:21.290 align:start position:0% in the case of an extract this would be like<00:10:18.840> as<00:10:19.080> if<00:10:19.350> we<00:10:19.620> put<00:10:19.980> this<00:10:20.130> in<00:10:20.490> line<00:10:20.880> right 00:10:21.290 --> 00:10:21.300 align:start position:0% like as if we put this in line right 00:10:21.300 --> 00:10:23.630 align:start position:0% like as if we put this in line right here<00:10:21.600> and<00:10:21.780> distract<00:10:22.560> like<00:10:22.950> quote-unquote<00:10:23.490> in 00:10:23.630 --> 00:10:23.640 align:start position:0% here and distract like quote-unquote in 00:10:23.640 --> 00:10:26.930 align:start position:0% here and distract like quote-unquote in exercise<00:10:24.060> at<00:10:24.240> all<00:10:24.800> the<00:10:25.800> case<00:10:26.010> of<00:10:26.190> the<00:10:26.610> case<00:10:26.790> of 00:10:26.930 --> 00:10:26.940 align:start position:0% exercise at all the case of the case of 00:10:26.940 --> 00:10:29.120 align:start position:0% exercise at all the case of the case of I<00:10:27.060> race<00:10:27.270> is<00:10:27.540> a<00:10:27.570> little<00:10:27.900> bit<00:10:28.050> more<00:10:28.230> complex<00:10:28.590> for 00:10:29.120 --> 00:10:29.130 align:start position:0% I race is a little bit more complex for 00:10:29.130 --> 00:10:31.520 align:start position:0% I race is a little bit more complex for static<00:10:29.460> length<00:10:29.640> arrays<00:10:30.000> like<00:10:30.300> this<00:10:30.750> behaves 00:10:31.520 --> 00:10:31.530 align:start position:0% static length arrays like this behaves 00:10:31.530 --> 00:10:36.140 align:start position:0% static length arrays like this behaves exactly<00:10:31.710> the<00:10:32.220> same<00:10:32.430> way<00:10:34.910> but<00:10:35.910> for<00:10:36.090> a 00:10:36.140 --> 00:10:36.150 align:start position:0% exactly the same way but for a 00:10:36.150 --> 00:10:38.150 align:start position:0% exactly the same way but for a dynamically<00:10:36.690> length<00:10:36.990> array<00:10:37.320> it<00:10:37.710> would<00:10:37.920> put 00:10:38.150 --> 00:10:38.160 align:start position:0% dynamically length array it would put 00:10:38.160 --> 00:10:40.310 align:start position:0% dynamically length array it would put history<00:10:38.580> the<00:10:38.940> the<00:10:39.270> array<00:10:39.510> length<00:10:39.720> in<00:10:40.050> the 00:10:40.310 --> 00:10:40.320 align:start position:0% history the the array length in the 00:10:40.320 --> 00:10:42.980 align:start position:0% history the the array length in the storage<00:10:40.830> slug<00:10:41.160> that<00:10:41.400> it<00:10:41.580> would<00:10:42.060> be<00:10:42.210> but<00:10:42.780> then 00:10:42.980 --> 00:10:42.990 align:start position:0% storage slug that it would be but then 00:10:42.990 --> 00:10:46.220 align:start position:0% storage slug that it would be but then these<00:10:43.350> DeRay<00:10:43.860> values<00:10:44.310> are<00:10:44.760> stored<00:10:45.240> in<00:10:45.540> the<00:10:45.900> in 00:10:46.220 --> 00:10:46.230 align:start position:0% these DeRay values are stored in the in 00:10:46.230 --> 00:10:50.750 align:start position:0% these DeRay values are stored in the in the<00:10:46.440> hash<00:10:46.680> of<00:10:46.920> the<00:10:47.070> of<00:10:47.340> the<00:10:47.490> pointer<00:10:49.610> in<00:10:50.610> the 00:10:50.750 --> 00:10:50.760 align:start position:0% the hash of the of the pointer in the 00:10:50.760 --> 00:10:52.490 align:start position:0% the hash of the of the pointer in the case<00:10:50.880> of<00:10:51.030> mappings<00:10:51.390> is<00:10:51.600> actually<00:10:51.960> a<00:10:51.990> bit 00:10:52.490 --> 00:10:52.500 align:start position:0% case of mappings is actually a bit 00:10:52.500 --> 00:10:55.640 align:start position:0% case of mappings is actually a bit simpler<00:10:52.950> it<00:10:53.760> stores<00:10:54.450> the<00:10:54.660> value<00:10:55.020> at<00:10:55.260> the<00:10:55.440> hash 00:10:55.640 --> 00:10:55.650 align:start position:0% simpler it stores the value at the hash 00:10:55.650 --> 00:10:59.390 align:start position:0% simpler it stores the value at the hash of<00:10:55.980> the<00:10:56.220> of<00:10:56.400> the<00:10:56.760> key<00:10:56.940> and<00:10:57.150> the<00:10:57.270> position<00:10:58.400> so 00:10:59.390 --> 00:10:59.400 align:start position:0% of the of the key and the position so 00:10:59.400 --> 00:11:02.540 align:start position:0% of the of the key and the position so the<00:11:00.210> warnings<00:11:00.630> from<00:11:01.260> these<00:11:01.410> is<00:11:01.770> if<00:11:02.190> you're 00:11:02.540 --> 00:11:02.550 align:start position:0% the warnings from these is if you're 00:11:02.550 --> 00:11:04.910 align:start position:0% the warnings from these is if you're like<00:11:03.180> a<00:11:03.240> braiding<00:11:03.810> from<00:11:04.050> one<00:11:04.290> contract<00:11:04.800> to 00:11:04.910 --> 00:11:04.920 align:start position:0% like a braiding from one contract to 00:11:04.920 --> 00:11:07.910 align:start position:0% like a braiding from one contract to another<00:11:05.130> it's<00:11:05.790> it's<00:11:06.780> better<00:11:07.050> to<00:11:07.410> like<00:11:07.590> know 00:11:07.910 --> 00:11:07.920 align:start position:0% another it's it's better to like know 00:11:07.920 --> 00:11:09.680 align:start position:0% another it's it's better to like know that<00:11:08.100> storage<00:11:08.700> in<00:11:08.880> the<00:11:08.970> middle<00:11:09.240> because<00:11:09.420> I 00:11:09.680 --> 00:11:09.690 align:start position:0% that storage in the middle because I 00:11:09.690 --> 00:11:10.010 align:start position:0% that storage in the middle because I guess 00:11:10.010 --> 00:11:10.020 align:start position:0% guess 00:11:10.020 --> 00:11:12.590 align:start position:0% guess we<00:11:10.170> saw<00:11:10.410> the<00:11:10.980> oldest<00:11:11.430> storage<00:11:11.820> depends<00:11:12.480> on 00:11:12.590 --> 00:11:12.600 align:start position:0% we saw the oldest storage depends on 00:11:12.600 --> 00:11:14.300 align:start position:0% we saw the oldest storage depends on what<00:11:12.779> the<00:11:12.899> position<00:11:13.320> is<00:11:13.440> inside<00:11:13.470> the<00:11:13.890> contract 00:11:14.300 --> 00:11:14.310 align:start position:0% what the position is inside the contract 00:11:14.310 --> 00:11:16.070 align:start position:0% what the position is inside the contract so<00:11:14.580> if<00:11:14.670> we<00:11:14.790> add<00:11:14.910> something<00:11:15.149> in<00:11:15.360> the<00:11:15.450> middle<00:11:15.600> all 00:11:16.070 --> 00:11:16.080 align:start position:0% so if we add something in the middle all 00:11:16.080 --> 00:11:19.070 align:start position:0% so if we add something in the middle all the<00:11:16.220> storage<00:11:17.220> would<00:11:17.550> be<00:11:17.610> broken<00:11:18.450> and<00:11:18.750> the 00:11:19.070 --> 00:11:19.080 align:start position:0% the storage would be broken and the 00:11:19.080 --> 00:11:20.960 align:start position:0% the storage would be broken and the problem<00:11:19.320> with<00:11:19.440> this<00:11:19.560> is<00:11:19.740> like<00:11:19.920> this<00:11:20.520> failing 00:11:20.960 --> 00:11:20.970 align:start position:0% problem with this is like this failing 00:11:20.970 --> 00:11:23.960 align:start position:0% problem with this is like this failing will<00:11:21.240> be<00:11:21.390> silent<00:11:21.870> so<00:11:22.320> it<00:11:22.560> won't<00:11:22.770> like<00:11:22.980> if<00:11:23.670> you 00:11:23.960 --> 00:11:23.970 align:start position:0% will be silent so it won't like if you 00:11:23.970 --> 00:11:25.910 align:start position:0% will be silent so it won't like if you don't<00:11:24.180> do<00:11:24.360> it<00:11:24.390> like<00:11:24.510> nothing<00:11:25.170> will<00:11:25.290> say<00:11:25.500> this 00:11:25.910 --> 00:11:25.920 align:start position:0% don't do it like nothing will say this 00:11:25.920 --> 00:11:27.769 align:start position:0% don't do it like nothing will say this is<00:11:26.250> going<00:11:26.490> to<00:11:26.580> break<00:11:26.700> your<00:11:26.880> contract<00:11:27.120> but 00:11:27.769 --> 00:11:27.779 align:start position:0% is going to break your contract but 00:11:27.779 --> 00:11:30.050 align:start position:0% is going to break your contract but whenever<00:11:28.380> you<00:11:28.770> start<00:11:29.279> using<00:11:29.430> the<00:11:29.640> contract 00:11:30.050 --> 00:11:30.060 align:start position:0% whenever you start using the contract 00:11:30.060 --> 00:11:33.889 align:start position:0% whenever you start using the contract all<00:11:30.240> the<00:11:30.360> storage<00:11:30.600> will<00:11:30.839> be<00:11:30.870> broken<00:11:32.660> so<00:11:33.660> an 00:11:33.889 --> 00:11:33.899 align:start position:0% all the storage will be broken so an 00:11:33.899 --> 00:11:36.050 align:start position:0% all the storage will be broken so an example<00:11:34.020> of<00:11:34.470> an<00:11:34.620> operate<00:11:34.950> that<00:11:35.190> that<00:11:35.820> goes 00:11:36.050 --> 00:11:36.060 align:start position:0% example of an operate that that goes 00:11:36.060 --> 00:11:39.350 align:start position:0% example of an operate that that goes wrong<00:11:36.330> is<00:11:36.600> this<00:11:37.230> one<00:11:37.470> so<00:11:38.070> because<00:11:38.790> of<00:11:38.940> howdy 00:11:39.350 --> 00:11:39.360 align:start position:0% wrong is this one so because of howdy 00:11:39.360 --> 00:11:43.130 align:start position:0% wrong is this one so because of howdy how<00:11:40.050> these<00:11:40.260> tracks<00:11:40.620> get<00:11:41.370> starting<00:11:41.850> raised<00:11:42.140> we 00:11:43.130 --> 00:11:43.140 align:start position:0% how these tracks get starting raised we 00:11:43.140 --> 00:11:44.630 align:start position:0% how these tracks get starting raised we have<00:11:43.350> this<00:11:43.529> initial<00:11:43.920> contracting<00:11:44.490> which 00:11:44.630 --> 00:11:44.640 align:start position:0% have this initial contracting which 00:11:44.640 --> 00:11:49.180 align:start position:0% have this initial contracting which which<00:11:44.850> we<00:11:45.720> are<00:11:45.959> storing<00:11:46.470> instead<00:11:47.399> of<00:11:47.610> employee 00:11:49.180 --> 00:11:49.190 align:start position:0% which we are storing instead of employee 00:11:49.190 --> 00:11:52.220 align:start position:0% which we are storing instead of employee and<00:11:50.190> then<00:11:50.820> we<00:11:51.270> create<00:11:51.630> like<00:11:51.810> a<00:11:51.959> couple 00:11:52.220 --> 00:11:52.230 align:start position:0% and then we create like a couple 00:11:52.230 --> 00:11:54.829 align:start position:0% and then we create like a couple employees<00:11:52.620> here<00:11:52.920> with<00:11:53.160> with<00:11:53.399> their<00:11:53.550> salary<00:11:53.880> if 00:11:54.829 --> 00:11:54.839 align:start position:0% employees here with with their salary if 00:11:54.839 --> 00:11:57.139 align:start position:0% employees here with with their salary if after<00:11:55.320> this<00:11:55.470> we<00:11:55.890> operate<00:11:56.279> this<00:11:56.430> contract<00:11:56.940> to 00:11:57.139 --> 00:11:57.149 align:start position:0% after this we operate this contract to 00:11:57.149 --> 00:12:00.470 align:start position:0% after this we operate this contract to the<00:11:57.330> spiral<00:11:57.779> to<00:11:58.100> contract<00:11:59.100> in<00:11:59.580> which<00:11:59.760> we<00:11:59.940> had<00:12:00.240> a 00:12:00.470 --> 00:12:00.480 align:start position:0% the spiral to contract in which we had a 00:12:00.480 --> 00:12:03.019 align:start position:0% the spiral to contract in which we had a new<00:12:00.779> a<00:12:00.990> new<00:12:01.200> member<00:12:01.470> to<00:12:01.500> distract<00:12:02.010> with<00:12:02.820> this 00:12:03.019 --> 00:12:03.029 align:start position:0% new a new member to distract with this 00:12:03.029 --> 00:12:05.180 align:start position:0% new a new member to distract with this what<00:12:03.450> will<00:12:03.630> happen<00:12:04.020> when<00:12:04.170> we<00:12:04.230> try<00:12:04.649> to<00:12:04.770> fetch 00:12:05.180 --> 00:12:05.190 align:start position:0% what will happen when we try to fetch 00:12:05.190 --> 00:12:08.540 align:start position:0% what will happen when we try to fetch the<00:12:05.459> first<00:12:05.880> the<00:12:06.089> second<00:12:06.420> employee<00:12:07.070> salary<00:12:08.070> is 00:12:08.540 --> 00:12:08.550 align:start position:0% the first the second employee salary is 00:12:08.550 --> 00:12:11.090 align:start position:0% the first the second employee salary is that<00:12:08.850> it<00:12:09.089> will<00:12:09.270> be<00:12:09.480> stored<00:12:10.140> where<00:12:10.890> the 00:12:11.090 --> 00:12:11.100 align:start position:0% that it will be stored where the 00:12:11.100 --> 00:12:13.940 align:start position:0% that it will be stored where the employees<00:12:11.820> first<00:12:12.330> with<00:12:13.170> the<00:12:13.260> first<00:12:13.410> employees 00:12:13.940 --> 00:12:13.950 align:start position:0% employees first with the first employees 00:12:13.950 --> 00:12:16.819 align:start position:0% employees first with the first employees join<00:12:14.339> that<00:12:14.520> is<00:12:14.700> so<00:12:15.360> it<00:12:15.630> will<00:12:15.660> turn<00:12:15.990> its<00:12:16.380> salary 00:12:16.819 --> 00:12:16.829 align:start position:0% join that is so it will turn its salary 00:12:16.829 --> 00:12:20.269 align:start position:0% join that is so it will turn its salary into<00:12:17.130> zero<00:12:17.490> and<00:12:17.790> the<00:12:18.420> salary<00:12:19.140> will<00:12:19.770> be<00:12:19.800> in<00:12:20.160> to 00:12:20.269 --> 00:12:20.279 align:start position:0% into zero and the salary will be in to 00:12:20.279 --> 00:12:23.449 align:start position:0% into zero and the salary will be in to join<00:12:20.490> date<00:12:20.700> but<00:12:21.450> if<00:12:21.810> for<00:12:22.410> example<00:12:22.440> we<00:12:22.980> use<00:12:23.250> some 00:12:23.449 --> 00:12:23.459 align:start position:0% join date but if for example we use some 00:12:23.459 --> 00:12:24.610 align:start position:0% join date but if for example we use some mapping<00:12:23.640> to<00:12:23.970> store<00:12:24.209> this<00:12:24.360> information 00:12:24.610 --> 00:12:24.620 align:start position:0% mapping to store this information 00:12:24.620 --> 00:12:27.710 align:start position:0% mapping to store this information because<00:12:25.620> mapping<00:12:26.339> stones<00:12:26.670> 30<00:12:27.270> values 00:12:27.710 --> 00:12:27.720 align:start position:0% because mapping stones 30 values 00:12:27.720 --> 00:12:30.050 align:start position:0% because mapping stones 30 values subsequently<00:12:28.529> body<00:12:28.920> from<00:12:29.130> value<00:12:29.490> but<00:12:29.730> they're 00:12:30.050 --> 00:12:30.060 align:start position:0% subsequently body from value but they're 00:12:30.060 --> 00:12:32.480 align:start position:0% subsequently body from value but they're in<00:12:30.149> the<00:12:30.240> hash<00:12:30.480> if<00:12:31.200> we<00:12:31.529> do<00:12:31.680> this<00:12:31.980> exact<00:12:32.339> same 00:12:32.480 --> 00:12:32.490 align:start position:0% in the hash if we do this exact same 00:12:32.490 --> 00:12:34.670 align:start position:0% in the hash if we do this exact same thing<00:12:32.550> when<00:12:33.270> after<00:12:33.750> upgrading<00:12:34.170> to<00:12:34.500> this 00:12:34.670 --> 00:12:34.680 align:start position:0% thing when after upgrading to this 00:12:34.680 --> 00:12:37.430 align:start position:0% thing when after upgrading to this second<00:12:35.339> or<00:12:35.550> the<00:12:35.850> second<00:12:36.570> contract<00:12:36.930> in<00:12:37.290> which 00:12:37.430 --> 00:12:37.440 align:start position:0% second or the second contract in which 00:12:37.440 --> 00:12:40.639 align:start position:0% second or the second contract in which see<00:12:37.680> we<00:12:38.070> track<00:12:38.399> the<00:12:38.579> DD<00:12:39.420> employee<00:12:39.690> here<00:12:40.050> both 00:12:40.639 --> 00:12:40.649 align:start position:0% see we track the DD employee here both 00:12:40.649 --> 00:12:42.920 align:start position:0% see we track the DD employee here both salaries<00:12:41.130> would<00:12:41.339> be<00:12:41.459> correct<00:12:41.820> but<00:12:42.420> both 00:12:42.920 --> 00:12:42.930 align:start position:0% salaries would be correct but both 00:12:42.930 --> 00:12:44.540 align:start position:0% salaries would be correct but both joined<00:12:43.230> edge<00:12:43.350> will<00:12:43.560> be<00:12:43.680> 0<00:12:43.890> because<00:12:44.220> we<00:12:44.370> never 00:12:44.540 --> 00:12:44.550 align:start position:0% joined edge will be 0 because we never 00:12:44.550 --> 00:12:49.120 align:start position:0% joined edge will be 0 because we never we<00:12:45.000> never<00:12:45.029> set<00:12:45.450> them<00:12:46.760> so<00:12:47.760> with<00:12:48.120> with<00:12:48.480> all<00:12:48.660> these 00:12:49.120 --> 00:12:49.130 align:start position:0% we never set them so with with all these 00:12:49.130 --> 00:12:52.630 align:start position:0% we never set them so with with all these we<00:12:50.130> we<00:12:50.550> are<00:12:50.670> using<00:12:50.940> this<00:12:51.240> upgradability 00:12:52.630 --> 00:12:52.640 align:start position:0% we we are using this upgradability 00:12:52.640 --> 00:12:55.880 align:start position:0% we we are using this upgradability paradigm<00:12:53.640> in<00:12:53.970> our<00:12:54.120> in<00:12:54.779> our<00:12:54.899> own<00:12:55.050> contracts<00:12:55.620> we 00:12:55.880 --> 00:12:55.890 align:start position:0% paradigm in our in our own contracts we 00:12:55.890 --> 00:12:58.850 align:start position:0% paradigm in our in our own contracts we call<00:12:56.130> it<00:12:56.250> Aragon<00:12:56.760> OS<00:12:57.029> and<00:12:57.300> the<00:12:57.860> implementation 00:12:58.850 --> 00:12:58.860 align:start position:0% call it Aragon OS and the implementation 00:12:58.860 --> 00:13:00.769 align:start position:0% call it Aragon OS and the implementation is<00:12:58.950> actually<00:12:59.100> very<00:12:59.459> very<00:12:59.730> simple<00:13:00.149> we<00:13:00.570> have 00:13:00.769 --> 00:13:00.779 align:start position:0% is actually very very simple we have 00:13:00.779 --> 00:13:04.100 align:start position:0% is actually very very simple we have this<00:13:00.990> tiny<00:13:01.560> kernel<00:13:01.950> contract<00:13:02.940> which<00:13:03.240> actually 00:13:04.100 --> 00:13:04.110 align:start position:0% this tiny kernel contract which actually 00:13:04.110 --> 00:13:07.069 align:start position:0% this tiny kernel contract which actually keeps<00:13:04.950> track<00:13:05.160> of<00:13:05.370> all<00:13:05.760> what<00:13:06.180> the<00:13:06.360> how<00:13:06.720> all<00:13:06.899> the 00:13:07.069 --> 00:13:07.079 align:start position:0% keeps track of all what the how all the 00:13:07.079 --> 00:13:08.269 align:start position:0% keeps track of all what the how all the contracts<00:13:07.500> that<00:13:07.560> depend<00:13:07.950> on<00:13:08.100> that 00:13:08.269 --> 00:13:08.279 align:start position:0% contracts that depend on that 00:13:08.279 --> 00:13:10.550 align:start position:0% contracts that depend on that organization<00:13:09.000> gets<00:13:09.180> stored<00:13:09.450> and<00:13:10.290> we 00:13:10.550 --> 00:13:10.560 align:start position:0% organization gets stored and we 00:13:10.560 --> 00:13:12.860 align:start position:0% organization gets stored and we basically<00:13:10.740> store<00:13:11.310> all<00:13:11.790> the<00:13:12.120> old<00:13:12.329> important 00:13:12.860 --> 00:13:12.870 align:start position:0% basically store all the old important 00:13:12.870 --> 00:13:14.630 align:start position:0% basically store all the old important business<00:13:13.170> logic<00:13:13.350> in<00:13:13.620> an<00:13:13.709> organization<00:13:14.430> is 00:13:14.630 --> 00:13:14.640 align:start position:0% business logic in an organization is 00:13:14.640 --> 00:13:18.170 align:start position:0% business logic in an organization is stored<00:13:15.120> in<00:13:15.390> in<00:13:16.050> apps<00:13:16.410> that<00:13:16.890> are<00:13:17.070> at<00:13:17.339> the<00:13:17.520> at<00:13:17.910> the 00:13:18.170 --> 00:13:18.180 align:start position:0% stored in in apps that are at the at the 00:13:18.180 --> 00:13:20.660 align:start position:0% stored in in apps that are at the at the edges<00:13:18.480> of<00:13:18.600> the<00:13:18.720> system<00:13:19.050> in<00:13:19.800> this<00:13:20.130> way<00:13:20.190> we<00:13:20.520> can 00:13:20.660 --> 00:13:20.670 align:start position:0% edges of the system in this way we can 00:13:20.670 --> 00:13:22.890 align:start position:0% edges of the system in this way we can keep<00:13:20.820> the<00:13:20.970> kernel<00:13:21.630> very<00:13:21.839> very<00:13:21.990> simple 00:13:22.890 --> 00:13:22.900 align:start position:0% keep the kernel very very simple 00:13:22.900 --> 00:13:25.350 align:start position:0% keep the kernel very very simple so<00:13:23.410> this<00:13:24.070> is<00:13:24.190> like<00:13:24.460> kind<00:13:24.730> of<00:13:24.790> the<00:13:24.970> lifecycle 00:13:25.350 --> 00:13:25.360 align:start position:0% so this is like kind of the lifecycle 00:13:25.360 --> 00:13:28.530 align:start position:0% so this is like kind of the lifecycle for<00:13:26.200> a<00:13:26.260> repo<00:13:26.650> for<00:13:26.890> a<00:13:26.920> new<00:13:27.160> contract<00:13:27.970> call<00:13:28.270> that 00:13:28.530 --> 00:13:28.540 align:start position:0% for a repo for a new contract call that 00:13:28.540 --> 00:13:31.290 align:start position:0% for a repo for a new contract call that gets<00:13:28.810> done<00:13:29.020> to<00:13:29.230> an<00:13:29.350> hour<00:13:29.500> ago<00:13:29.740> os<00:13:30.310> contract<00:13:30.790> so 00:13:31.290 --> 00:13:31.300 align:start position:0% gets done to an hour ago os contract so 00:13:31.300 --> 00:13:33.570 align:start position:0% gets done to an hour ago os contract so we<00:13:31.480> will<00:13:31.630> have<00:13:31.839> the<00:13:32.050> the<00:13:32.440> initial<00:13:32.650> call<00:13:33.160> here 00:13:33.570 --> 00:13:33.580 align:start position:0% we will have the the initial call here 00:13:33.580 --> 00:13:36.269 align:start position:0% we will have the the initial call here this<00:13:34.360> will<00:13:34.540> go<00:13:34.660> to<00:13:34.690> the<00:13:35.320> upgrade<00:13:35.860> to<00:13:36.190> an 00:13:36.269 --> 00:13:36.279 align:start position:0% this will go to the upgrade to an 00:13:36.279 --> 00:13:38.640 align:start position:0% this will go to the upgrade to an available<00:13:36.490> proxy<00:13:37.029> contract<00:13:37.480> but<00:13:38.140> instead<00:13:38.589> of 00:13:38.640 --> 00:13:38.650 align:start position:0% available proxy contract but instead of 00:13:38.650 --> 00:13:40.740 align:start position:0% available proxy contract but instead of like<00:13:39.040> knowing<00:13:39.610> where<00:13:39.790> this<00:13:39.880> code<00:13:40.150> is<00:13:40.300> it<00:13:40.570> just 00:13:40.740 --> 00:13:40.750 align:start position:0% like knowing where this code is it just 00:13:40.750 --> 00:13:43.140 align:start position:0% like knowing where this code is it just has<00:13:40.870> the<00:13:41.110> kernel<00:13:41.470> whether<00:13:41.800> there<00:13:42.730> has<00:13:42.880> been<00:13:42.910> an 00:13:43.140 --> 00:13:43.150 align:start position:0% has the kernel whether there has been an 00:13:43.150 --> 00:13:45.300 align:start position:0% has the kernel whether there has been an upgrade<00:13:43.270> and<00:13:43.630> like<00:13:43.900> what<00:13:44.290> what<00:13:44.589> is<00:13:44.680> it<00:13:44.710> the 00:13:45.300 --> 00:13:45.310 align:start position:0% upgrade and like what what is it the 00:13:45.310 --> 00:13:47.850 align:start position:0% upgrade and like what what is it the code<00:13:45.520> implementation<00:13:46.180> for<00:13:46.540> this<00:13:46.660> app<00:13:46.839> when<00:13:47.770> it 00:13:47.850 --> 00:13:47.860 align:start position:0% code implementation for this app when it 00:13:47.860 --> 00:13:50.730 align:start position:0% code implementation for this app when it gets<00:13:48.070> it<00:13:48.279> it<00:13:48.520> doesn't<00:13:48.820> delegate<00:13:49.300> call<00:13:49.600> duty<00:13:50.350> to 00:13:50.730 --> 00:13:50.740 align:start position:0% gets it it doesn't delegate call duty to 00:13:50.740 --> 00:13:52.620 align:start position:0% gets it it doesn't delegate call duty to reveal<00:13:51.100> implementation<00:13:51.970> of<00:13:52.089> the<00:13:52.210> app<00:13:52.330> in<00:13:52.510> this 00:13:52.620 --> 00:13:52.630 align:start position:0% reveal implementation of the app in this 00:13:52.630 --> 00:13:55.200 align:start position:0% reveal implementation of the app in this case<00:13:52.690> it<00:13:53.020> would<00:13:53.140> be<00:13:53.170> app<00:13:53.440> zero<00:13:54.460> version<00:13:55.000> one 00:13:55.200 --> 00:13:55.210 align:start position:0% case it would be app zero version one 00:13:55.210 --> 00:13:57.960 align:start position:0% case it would be app zero version one after<00:13:55.900> that<00:13:56.080> the<00:13:56.410> app<00:13:56.560> if<00:13:56.950> the<00:13:57.430> if<00:13:57.640> it's<00:13:57.820> a 00:13:57.960 --> 00:13:57.970 align:start position:0% after that the app if the if it's a 00:13:57.970 --> 00:13:59.579 align:start position:0% after that the app if the if it's a productive<00:13:58.450> function<00:13:58.870> that<00:13:59.080> it's<00:13:59.350> being 00:13:59.579 --> 00:13:59.589 align:start position:0% productive function that it's being 00:13:59.589 --> 00:14:02.220 align:start position:0% productive function that it's being performed<00:13:59.800> this<00:14:00.460> will<00:14:00.700> ask<00:14:00.910> the<00:14:01.180> the<00:14:01.600> contract 00:14:02.220 --> 00:14:02.230 align:start position:0% performed this will ask the the contract 00:14:02.230 --> 00:14:04.829 align:start position:0% performed this will ask the the contract the<00:14:02.589> kernel<00:14:02.920> again<00:14:03.190> oh<00:14:03.370> hey<00:14:03.820> can<00:14:04.390> this<00:14:04.480> action 00:14:04.829 --> 00:14:04.839 align:start position:0% the kernel again oh hey can this action 00:14:04.839 --> 00:14:08.880 align:start position:0% the kernel again oh hey can this action be<00:14:04.960> perform<00:14:05.350> right<00:14:05.500> now<00:14:06.510> so<00:14:07.510> with<00:14:08.500> this<00:14:08.650> system 00:14:08.880 --> 00:14:08.890 align:start position:0% be perform right now so with this system 00:14:08.890 --> 00:14:11.430 align:start position:0% be perform right now so with this system of<00:14:09.279> the<00:14:09.640> AC<00:14:09.820> of<00:14:10.240> the<00:14:10.420> access<00:14:10.720> control<00:14:11.080> is<00:14:11.260> in 00:14:11.430 --> 00:14:11.440 align:start position:0% of the AC of the access control is in 00:14:11.440 --> 00:14:14.100 align:start position:0% of the AC of the access control is in the<00:14:11.529> NT<00:14:11.800> kernel<00:14:11.950> what<00:14:12.670> we<00:14:12.820> can<00:14:13.000> do<00:14:13.270> is<00:14:13.600> we<00:14:13.960> can 00:14:14.100 --> 00:14:14.110 align:start position:0% the NT kernel what we can do is we can 00:14:14.110 --> 00:14:18.750 align:start position:0% the NT kernel what we can do is we can use<00:14:14.529> these<00:14:15.190> complex<00:14:17.220> governance<00:14:18.220> mechanisms 00:14:18.750 --> 00:14:18.760 align:start position:0% use these complex governance mechanisms 00:14:18.760 --> 00:14:20.190 align:start position:0% use these complex governance mechanisms that<00:14:18.970> you<00:14:19.089> could<00:14:19.300> have<00:14:19.480> in<00:14:19.630> your<00:14:19.660> in<00:14:20.020> your 00:14:20.190 --> 00:14:20.200 align:start position:0% that you could have in your in your 00:14:20.200 --> 00:14:22.560 align:start position:0% that you could have in your in your organization<00:14:20.800> to<00:14:21.010> decide<00:14:21.339> whether<00:14:21.850> or<00:14:21.940> not<00:14:22.210> an 00:14:22.560 --> 00:14:22.570 align:start position:0% organization to decide whether or not an 00:14:22.570 --> 00:14:25.800 align:start position:0% organization to decide whether or not an app<00:14:23.020> which<00:14:23.200> should<00:14:23.410> happen<00:14:24.390> so<00:14:25.390> we<00:14:25.630> are 00:14:25.800 --> 00:14:25.810 align:start position:0% app which should happen so we are 00:14:25.810 --> 00:14:27.690 align:start position:0% app which should happen so we are protecting<00:14:26.350> all<00:14:26.560> the<00:14:26.710> average<00:14:27.070> to<00:14:27.279> kernel 00:14:27.690 --> 00:14:27.700 align:start position:0% protecting all the average to kernel 00:14:27.700 --> 00:14:32.010 align:start position:0% protecting all the average to kernel synapse<00:14:28.089> to<00:14:28.540> like<00:14:29.170> this<00:14:30.330> so<00:14:31.330> how<00:14:31.810> would<00:14:31.870> that 00:14:32.010 --> 00:14:32.020 align:start position:0% synapse to like this so how would that 00:14:32.020 --> 00:14:33.960 align:start position:0% synapse to like this so how would that like<00:14:32.320> how<00:14:32.770> would<00:14:32.920> an<00:14:33.070> app<00:14:33.220> look<00:14:33.520> like<00:14:33.700> it's 00:14:33.960 --> 00:14:33.970 align:start position:0% like how would an app look like it's 00:14:33.970 --> 00:14:38.220 align:start position:0% like how would an app look like it's it's<00:14:34.450> very<00:14:34.540> simple<00:14:35.730> by<00:14:36.730> running<00:14:37.480> this<00:14:37.750> app<00:14:37.959> on 00:14:38.220 --> 00:14:38.230 align:start position:0% it's very simple by running this app on 00:14:38.230 --> 00:14:40.019 align:start position:0% it's very simple by running this app on top<00:14:38.350> of<00:14:38.589> the<00:14:38.740> organization<00:14:39.400> let's<00:14:39.640> say<00:14:39.790> you're 00:14:40.019 --> 00:14:40.029 align:start position:0% top of the organization let's say you're 00:14:40.029 --> 00:14:42.000 align:start position:0% top of the organization let's say you're running<00:14:40.209> this<00:14:40.510> county<00:14:40.900> rap<00:14:41.080> to<00:14:41.560> check<00:14:41.800> how 00:14:42.000 --> 00:14:42.010 align:start position:0% running this county rap to check how 00:14:42.010 --> 00:14:44.730 align:start position:0% running this county rap to check how many<00:14:42.070> icos<00:14:42.760> there<00:14:43.120> were<00:14:43.240> today<00:14:43.540> so<00:14:44.110> we<00:14:44.470> have 00:14:44.730 --> 00:14:44.740 align:start position:0% many icos there were today so we have 00:14:44.740 --> 00:14:47.340 align:start position:0% many icos there were today so we have these<00:14:45.100> these<00:14:45.790> kind<00:14:46.029> of<00:14:46.150> rolls<00:14:46.420> inside<00:14:46.839> the<00:14:47.020> the 00:14:47.340 --> 00:14:47.350 align:start position:0% these these kind of rolls inside the the 00:14:47.350 --> 00:14:49.590 align:start position:0% these these kind of rolls inside the the app<00:14:47.500> that<00:14:47.890> define<00:14:48.490> what<00:14:48.520> are<00:14:49.060> the<00:14:49.209> different 00:14:49.590 --> 00:14:49.600 align:start position:0% app that define what are the different 00:14:49.600 --> 00:14:51.510 align:start position:0% app that define what are the different actions<00:14:49.930> that<00:14:50.110> can<00:14:50.589> happen<00:14:50.830> inside<00:14:51.100> the<00:14:51.400> app 00:14:51.510 --> 00:14:51.520 align:start position:0% actions that can happen inside the app 00:14:51.520 --> 00:14:54.150 align:start position:0% actions that can happen inside the app and<00:14:51.760> then<00:14:52.300> we<00:14:52.540> just<00:14:52.720> protect<00:14:53.080> them<00:14:53.230> here<00:14:53.709> with 00:14:54.150 --> 00:14:54.160 align:start position:0% and then we just protect them here with 00:14:54.160 --> 00:14:56.490 align:start position:0% and then we just protect them here with the<00:14:54.310> alt<00:14:54.430> modifier<00:14:54.810> what<00:14:55.810> this<00:14:55.990> will<00:14:56.170> do<00:14:56.320> is 00:14:56.490 --> 00:14:56.500 align:start position:0% the alt modifier what this will do is 00:14:56.500 --> 00:14:58.519 align:start position:0% the alt modifier what this will do is like<00:14:56.650> this<00:14:56.980> will<00:14:57.190> plug<00:14:57.370> in<00:14:57.610> to<00:14:57.790> the<00:14:57.940> organ<00:14:58.150> the 00:14:58.519 --> 00:14:58.529 align:start position:0% like this will plug in to the organ the 00:14:58.529 --> 00:15:01.970 align:start position:0% like this will plug in to the organ the organization<00:14:59.529> ACL<00:14:59.920> and<00:15:00.209> basically<00:15:01.209> any 00:15:01.970 --> 00:15:01.980 align:start position:0% organization ACL and basically any 00:15:01.980 --> 00:15:03.660 align:start position:0% organization ACL and basically any governance<00:15:02.980> mechanism<00:15:03.490> that<00:15:03.580> the 00:15:03.660 --> 00:15:03.670 align:start position:0% governance mechanism that the 00:15:03.670 --> 00:15:05.579 align:start position:0% governance mechanism that the organization<00:15:04.180> has<00:15:04.390> can<00:15:04.750> decide<00:15:05.080> who<00:15:05.440> can 00:15:05.579 --> 00:15:05.589 align:start position:0% organization has can decide who can 00:15:05.589 --> 00:15:07.730 align:start position:0% organization has can decide who can perform<00:15:05.800> these<00:15:06.220> and<00:15:06.670> their<00:15:06.910> work<00:15:07.029> condition 00:15:07.730 --> 00:15:07.740 align:start position:0% perform these and their work condition 00:15:07.740 --> 00:15:11.220 align:start position:0% perform these and their work condition and<00:15:08.740> by<00:15:09.550> doing<00:15:09.820> this<00:15:09.970> we<00:15:10.390> can<00:15:10.420> actually<00:15:10.810> up 00:15:11.220 --> 00:15:11.230 align:start position:0% and by doing this we can actually up 00:15:11.230 --> 00:15:14.280 align:start position:0% and by doing this we can actually up with<00:15:11.440> the<00:15:11.589> very<00:15:12.100> simple<00:15:12.130> and<00:15:12.790> add<00:15:13.390> a<00:15:13.420> new<00:15:13.750> and<00:15:14.110> a 00:15:14.280 --> 00:15:14.290 align:start position:0% with the very simple and add a new and a 00:15:14.290 --> 00:15:16.769 align:start position:0% with the very simple and add a new and a new<00:15:14.320> storage<00:15:14.830> a<00:15:15.220> new<00:15:15.459> storage<00:15:15.730> value<00:15:16.150> and<00:15:16.450> like 00:15:16.769 --> 00:15:16.779 align:start position:0% new storage a new storage value and like 00:15:16.779 --> 00:15:18.660 align:start position:0% new storage a new storage value and like a<00:15:16.810> couple<00:15:17.080> new<00:15:17.410> functions<00:15:17.830> and<00:15:18.040> this<00:15:18.490> will 00:15:18.660 --> 00:15:18.670 align:start position:0% a couple new functions and this will 00:15:18.670 --> 00:15:20.610 align:start position:0% a couple new functions and this will work<00:15:18.850> and<00:15:19.180> after<00:15:19.630> performing<00:15:20.110> the<00:15:20.230> operate 00:15:20.610 --> 00:15:20.620 align:start position:0% work and after performing the operate 00:15:20.620 --> 00:15:23.180 align:start position:0% work and after performing the operate everyone<00:15:21.310> that's<00:15:21.459> using<00:15:21.760> the<00:15:21.850> app<00:15:21.970> will<00:15:22.330> be 00:15:23.180 --> 00:15:23.190 align:start position:0% everyone that's using the app will be 00:15:23.190 --> 00:15:27.630 align:start position:0% everyone that's using the app will be and<00:15:24.630> this<00:15:25.630> is<00:15:25.750> actually<00:15:26.170> how<00:15:26.770> it's<00:15:27.130> going<00:15:27.459> to 00:15:27.630 --> 00:15:27.640 align:start position:0% and this is actually how it's going to 00:15:27.640 --> 00:15:30.030 align:start position:0% and this is actually how it's going to going<00:15:28.029> to<00:15:28.209> look<00:15:28.360> like<00:15:28.510> this<00:15:28.870> by<00:15:29.500> making<00:15:29.920> these 00:15:30.030 --> 00:15:30.040 align:start position:0% going to look like this by making these 00:15:30.040 --> 00:15:33.270 align:start position:0% going to look like this by making these very<00:15:30.610> very<00:15:30.940> tiny<00:15:31.270> app<00:15:31.839> you<00:15:32.470> can<00:15:32.620> plug<00:15:33.040> this 00:15:33.270 --> 00:15:33.280 align:start position:0% very very tiny app you can plug this 00:15:33.280 --> 00:15:35.699 align:start position:0% very very tiny app you can plug this counter<00:15:33.880> out<00:15:34.060> that<00:15:34.510> you<00:15:34.630> can<00:15:34.810> write<00:15:35.079> very<00:15:35.500> very 00:15:35.699 --> 00:15:35.709 align:start position:0% counter out that you can write very very 00:15:35.709 --> 00:15:36.540 align:start position:0% counter out that you can write very very simply 00:15:36.540 --> 00:15:36.550 align:start position:0% simply 00:15:36.550 --> 00:15:38.400 align:start position:0% simply and<00:15:36.730> plug<00:15:37.000> it<00:15:37.150> into<00:15:37.270> your<00:15:37.540> organization<00:15:38.200> and 00:15:38.400 --> 00:15:38.410 align:start position:0% and plug it into your organization and 00:15:38.410 --> 00:15:41.040 align:start position:0% and plug it into your organization and use<00:15:38.920> it<00:15:39.070> with<00:15:39.280> all<00:15:39.460> the<00:15:39.640> all<00:15:40.000> the<00:15:40.360> other 00:15:41.040 --> 00:15:41.050 align:start position:0% use it with all the all the other 00:15:41.050 --> 00:15:44.700 align:start position:0% use it with all the all the other features<00:15:41.530> that<00:15:41.740> the<00:15:42.100> Aragon<00:15:42.490> has<00:15:43.230> yeah<00:15:44.230> that's 00:15:44.700 --> 00:15:44.710 align:start position:0% features that the Aragon has yeah that's 00:15:44.710 --> 00:15:46.830 align:start position:0% features that the Aragon has yeah that's everything<00:15:44.830> for<00:15:45.160> us<00:15:45.280> if<00:15:46.000> you<00:15:46.270> are<00:15:46.510> curious 00:15:46.830 --> 00:15:46.840 align:start position:0% everything for us if you are curious 00:15:46.840 --> 00:15:48.780 align:start position:0% everything for us if you are curious about<00:15:47.050> this<00:15:47.320> you<00:15:47.650> can<00:15:47.800> contact<00:15:48.070> us<00:15:48.220> here<00:15:48.430> thank 00:15:48.780 --> 00:15:48.790 align:start position:0% about this you can contact us here thank 00:15:48.790 --> 00:15:49.490 align:start position:0% about this you can contact us here thank you 00:15:49.490 --> 00:15:49.500 align:start position:0% you 00:15:49.500 --> 00:15:56.100 align:start position:0% you [Applause] 00:15:56.100 --> 00:15:56.110 align:start position:0% 00:15:56.110 --> 00:16:03.690 align:start position:0% [Music]