WEBVTT Kind: captions Language: en 00:00:17.860 --> 00:00:21.850 align:start position:0% hello<00:00:18.860> everyone<00:00:19.300> I'm<00:00:20.300> here<00:00:21.230> to<00:00:21.470> talk<00:00:21.800> about 00:00:21.850 --> 00:00:21.860 align:start position:0% hello everyone I'm here to talk about 00:00:21.860 --> 00:00:24.909 align:start position:0% hello everyone I'm here to talk about maker<00:00:22.520> I'm<00:00:22.820> gonna<00:00:23.000> give<00:00:23.119> a<00:00:23.149> short<00:00:23.300> talk<00:00:23.919> before 00:00:24.909 --> 00:00:24.919 align:start position:0% maker I'm gonna give a short talk before 00:00:24.919 --> 00:00:26.319 align:start position:0% maker I'm gonna give a short talk before I<00:00:24.950> start<00:00:25.220> it's<00:00:25.399> very<00:00:25.579> likely<00:00:25.790> that<00:00:26.119> not 00:00:26.319 --> 00:00:26.329 align:start position:0% I start it's very likely that not 00:00:26.329 --> 00:00:29.679 align:start position:0% I start it's very likely that not everyone<00:00:26.720> here<00:00:26.989> has<00:00:27.110> heard<00:00:27.439> of<00:00:27.559> maker<00:00:27.770> so<00:00:28.689> I'll 00:00:29.679 --> 00:00:29.689 align:start position:0% everyone here has heard of maker so I'll 00:00:29.689 --> 00:00:32.490 align:start position:0% everyone here has heard of maker so I'll just<00:00:29.869> explain<00:00:30.110> maker<00:00:31.099> the<00:00:31.489> contract<00:00:32.000> system 00:00:32.490 --> 00:00:32.500 align:start position:0% just explain maker the contract system 00:00:32.500 --> 00:00:35.799 align:start position:0% just explain maker the contract system whose<00:00:33.500> function<00:00:33.950> is<00:00:34.520> going<00:00:34.910> to<00:00:35.059> be<00:00:35.180> to<00:00:35.660> create 00:00:35.799 --> 00:00:35.809 align:start position:0% whose function is going to be to create 00:00:35.809 --> 00:00:38.080 align:start position:0% whose function is going to be to create the<00:00:36.080> dice<00:00:36.260> table<00:00:36.620> coin<00:00:36.950> and<00:00:37.220> the<00:00:37.580> associated 00:00:38.080 --> 00:00:38.090 align:start position:0% the dice table coin and the associated 00:00:38.090 --> 00:00:42.610 align:start position:0% the dice table coin and the associated credit<00:00:38.450> system<00:00:40.510> and<00:00:41.510> the<00:00:41.990> properties<00:00:42.410> of<00:00:42.440> the 00:00:42.610 --> 00:00:42.620 align:start position:0% credit system and the properties of the 00:00:42.620 --> 00:00:44.440 align:start position:0% credit system and the properties of the die<00:00:42.770> that<00:00:43.010> make<00:00:43.160> it<00:00:43.280> awesome<00:00:43.730> is<00:00:43.910> that 00:00:44.440 --> 00:00:44.450 align:start position:0% die that make it awesome is that 00:00:44.450 --> 00:00:46.180 align:start position:0% die that make it awesome is that well<00:00:44.930> it's<00:00:45.200> initially<00:00:45.500> pegged<00:00:45.710> to<00:00:45.770> the<00:00:45.830> SDR 00:00:46.180 --> 00:00:46.190 align:start position:0% well it's initially pegged to the SDR 00:00:46.190 --> 00:00:48.760 align:start position:0% well it's initially pegged to the SDR but<00:00:46.580> it's<00:00:46.790> deflationary<00:00:47.770> it's 00:00:48.760 --> 00:00:48.770 align:start position:0% but it's deflationary it's 00:00:48.770 --> 00:00:51.160 align:start position:0% but it's deflationary it's collateralized<00:00:49.370> in<00:00:49.550> excess<00:00:50.000> so<00:00:50.540> there<00:00:51.050> is 00:00:51.160 --> 00:00:51.170 align:start position:0% collateralized in excess so there is 00:00:51.170 --> 00:00:53.170 align:start position:0% collateralized in excess so there is more<00:00:51.590> value<00:00:51.950> locked<00:00:52.220> up<00:00:52.430> backing<00:00:52.820> that<00:00:52.940> died 00:00:53.170 --> 00:00:53.180 align:start position:0% more value locked up backing that died 00:00:53.180 --> 00:00:55.690 align:start position:0% more value locked up backing that died all<00:00:53.450> times<00:00:53.720> than<00:00:54.020> there<00:00:54.140> are<00:00:54.310> about<00:00:55.310> the<00:00:55.489> total 00:00:55.690 --> 00:00:55.700 align:start position:0% all times than there are about the total 00:00:55.700 --> 00:00:57.610 align:start position:0% all times than there are about the total value<00:00:56.030> of<00:00:56.060> the<00:00:56.150> die<00:00:56.270> and<00:00:56.750> it's<00:00:57.410> eventually 00:00:57.610 --> 00:00:57.620 align:start position:0% value of the die and it's eventually 00:00:57.620 --> 00:01:00.850 align:start position:0% value of the die and it's eventually trust<00:00:58.100> free<00:00:58.400> which<00:00:58.640> means<00:00:58.880> that<00:00:59.329> it<00:01:00.170> uses<00:01:00.560> the 00:01:00.850 --> 00:01:00.860 align:start position:0% trust free which means that it uses the 00:01:00.860 --> 00:01:03.819 align:start position:0% trust free which means that it uses the most<00:01:01.329> current<00:01:02.329> trust<00:01:02.899> free<00:01:03.140> mechanisms 00:01:03.819 --> 00:01:03.829 align:start position:0% most current trust free mechanisms 00:01:03.829 --> 00:01:06.399 align:start position:0% most current trust free mechanisms available<00:01:03.950> to<00:01:04.489> get<00:01:04.699> data<00:01:04.939> feeds<00:01:05.210> and<00:01:06.110> to<00:01:06.290> do 00:01:06.399 --> 00:01:06.409 align:start position:0% available to get data feeds and to do 00:01:06.409 --> 00:01:09.010 align:start position:0% available to get data feeds and to do the<00:01:06.590> the<00:01:07.130> pegging<00:01:07.460> mechanics<00:01:07.939> that<00:01:08.840> is 00:01:09.010 --> 00:01:09.020 align:start position:0% the the pegging mechanics that is 00:01:09.020 --> 00:01:14.140 align:start position:0% the the pegging mechanics that is available<00:01:09.590> about<00:01:10.010> the<00:01:10.159> time<00:01:11.800> so<00:01:12.940> this<00:01:13.940> talk<00:01:14.120> is 00:01:14.140 --> 00:01:14.150 align:start position:0% available about the time so this talk is 00:01:14.150 --> 00:01:16.210 align:start position:0% available about the time so this talk is not<00:01:14.270> going<00:01:14.510> to<00:01:14.750> be<00:01:14.840> about<00:01:15.260> the<00:01:15.500> actual<00:01:15.800> stable 00:01:16.210 --> 00:01:16.220 align:start position:0% not going to be about the actual stable 00:01:16.220 --> 00:01:18.430 align:start position:0% not going to be about the actual stable flowing<00:01:16.460> mechanics<00:01:17.090> because<00:01:17.990> that<00:01:18.140> is<00:01:18.229> not 00:01:18.430 --> 00:01:18.440 align:start position:0% flowing mechanics because that is not 00:01:18.440 --> 00:01:21.390 align:start position:0% flowing mechanics because that is not appropriate<00:01:19.040> for<00:01:19.340> a<00:01:19.490> 15<00:01:20.360> minutes<00:01:20.659> talk<00:01:20.930> and 00:01:21.390 --> 00:01:21.400 align:start position:0% appropriate for a 15 minutes talk and 00:01:21.400 --> 00:01:23.830 align:start position:0% appropriate for a 15 minutes talk and did<00:01:22.400> we<00:01:22.760> have<00:01:23.000> a<00:01:23.030> great<00:01:23.299> white<00:01:23.570> paper 00:01:23.830 --> 00:01:23.840 align:start position:0% did we have a great white paper 00:01:23.840 --> 00:01:27.370 align:start position:0% did we have a great white paper dedicated<00:01:24.470> to<00:01:24.729> exactly<00:01:25.729> that<00:01:25.970> so<00:01:26.810> instead 00:01:27.370 --> 00:01:27.380 align:start position:0% dedicated to exactly that so instead 00:01:27.380 --> 00:01:31.450 align:start position:0% dedicated to exactly that so instead today<00:01:27.950> we're<00:01:28.220> going<00:01:28.310> to<00:01:28.430> talk<00:01:28.729> about<00:01:30.340> what<00:01:31.340> the 00:01:31.450 --> 00:01:31.460 align:start position:0% today we're going to talk about what the 00:01:31.460 --> 00:01:33.130 align:start position:0% today we're going to talk about what the what<00:01:31.790> the<00:01:32.120> white<00:01:32.330> paper<00:01:32.510> doesn't<00:01:32.750> go<00:01:32.960> into 00:01:33.130 --> 00:01:33.140 align:start position:0% what the white paper doesn't go into 00:01:33.140 --> 00:01:34.870 align:start position:0% what the white paper doesn't go into which<00:01:33.409> is<00:01:33.590> how<00:01:33.740> the<00:01:33.799> actual<00:01:34.190> contract<00:01:34.640> system 00:01:34.870 --> 00:01:34.880 align:start position:0% which is how the actual contract system 00:01:34.880 --> 00:01:37.270 align:start position:0% which is how the actual contract system is<00:01:35.150> designed<00:01:35.299> so<00:01:36.260> what<00:01:36.530> are<00:01:36.650> the<00:01:36.860> different 00:01:37.270 --> 00:01:37.280 align:start position:0% is designed so what are the different 00:01:37.280 --> 00:01:38.740 align:start position:0% is designed so what are the different components<00:01:37.400> and<00:01:37.970> then<00:01:38.180> I'm<00:01:38.299> gonna<00:01:38.420> go<00:01:38.570> also 00:01:38.740 --> 00:01:38.750 align:start position:0% components and then I'm gonna go also 00:01:38.750 --> 00:01:41.680 align:start position:0% components and then I'm gonna go also going<00:01:38.930> to<00:01:38.990> mention<00:01:39.170> how<00:01:39.680> we<00:01:39.740> can<00:01:40.390> go<00:01:41.390> through 00:01:41.680 --> 00:01:41.690 align:start position:0% going to mention how we can go through 00:01:41.690 --> 00:01:43.960 align:start position:0% going to mention how we can go through go<00:01:42.229> about<00:01:42.380> deploying<00:01:42.830> this<00:01:43.250> contract<00:01:43.790> system 00:01:43.960 --> 00:01:43.970 align:start position:0% go about deploying this contract system 00:01:43.970 --> 00:01:46.210 align:start position:0% go about deploying this contract system over<00:01:44.540> time<00:01:44.780> and<00:01:45.080> start<00:01:45.320> getting<00:01:45.619> some<00:01:45.650> utility 00:01:46.210 --> 00:01:46.220 align:start position:0% over time and start getting some utility 00:01:46.220 --> 00:01:48.010 align:start position:0% over time and start getting some utility out<00:01:46.250> of<00:01:46.369> it<00:01:46.580> even<00:01:47.000> before<00:01:47.210> the<00:01:47.540> whole<00:01:47.659> thing<00:01:47.900> is 00:01:48.010 --> 00:01:48.020 align:start position:0% out of it even before the whole thing is 00:01:48.020 --> 00:01:52.810 align:start position:0% out of it even before the whole thing is complete<00:01:50.020> so<00:01:51.020> first<00:01:51.619> I'm<00:01:51.799> gonna<00:01:52.130> introduce 00:01:52.810 --> 00:01:52.820 align:start position:0% complete so first I'm gonna introduce 00:01:52.820 --> 00:01:56.320 align:start position:0% complete so first I'm gonna introduce basically<00:01:53.659> what<00:01:54.140> the<00:01:54.470> version<00:01:55.100> 0<00:01:55.610> of<00:01:55.880> the 00:01:56.320 --> 00:01:56.330 align:start position:0% basically what the version 0 of the 00:01:56.330 --> 00:01:58.480 align:start position:0% basically what the version 0 of the maker<00:01:56.540> contract<00:01:57.080> system<00:01:57.409> is<00:01:58.010> going<00:01:58.189> to<00:01:58.250> look 00:01:58.480 --> 00:01:58.490 align:start position:0% maker contract system is going to look 00:01:58.490 --> 00:02:02.710 align:start position:0% maker contract system is going to look like<00:01:58.670> so<00:01:59.290> this<00:02:00.290> is<00:02:00.670> an<00:02:01.670> authority<00:02:02.180> contract 00:02:02.710 --> 00:02:02.720 align:start position:0% like so this is an authority contract 00:02:02.720 --> 00:02:04.390 align:start position:0% like so this is an authority contract and<00:02:02.900> this<00:02:03.020> is<00:02:03.170> basically<00:02:03.350> a<00:02:03.830> command<00:02:04.280> and 00:02:04.390 --> 00:02:04.400 align:start position:0% and this is basically a command and 00:02:04.400 --> 00:02:06.730 align:start position:0% and this is basically a command and control<00:02:04.490> pattern<00:02:05.210> that<00:02:06.200> we<00:02:06.320> use<00:02:06.530> throughout 00:02:06.730 --> 00:02:06.740 align:start position:0% control pattern that we use throughout 00:02:06.740 --> 00:02:08.710 align:start position:0% control pattern that we use throughout the<00:02:06.979> maker<00:02:07.159> system<00:02:07.670> basically<00:02:08.209> every<00:02:08.420> single 00:02:08.710 --> 00:02:08.720 align:start position:0% the maker system basically every single 00:02:08.720 --> 00:02:11.410 align:start position:0% the maker system basically every single contract<00:02:09.229> I<00:02:10.220> didn't<00:02:10.849> draw<00:02:10.970> arrows<00:02:11.299> because 00:02:11.410 --> 00:02:11.420 align:start position:0% contract I didn't draw arrows because 00:02:11.420 --> 00:02:12.819 align:start position:0% contract I didn't draw arrows because there<00:02:11.569> would<00:02:11.659> be<00:02:11.689> too<00:02:11.870> many<00:02:12.019> they<00:02:12.290> all<00:02:12.469> point 00:02:12.819 --> 00:02:12.829 align:start position:0% there would be too many they all point 00:02:12.829 --> 00:02:15.350 align:start position:0% there would be too many they all point to<00:02:13.090> this<00:02:14.090> one<00:02:14.269> they<00:02:14.359> have<00:02:14.389> a<00:02:14.510> reference 00:02:15.350 --> 00:02:15.360 align:start position:0% to this one they have a reference 00:02:15.360 --> 00:02:18.950 align:start position:0% to this one they have a reference and<00:02:15.450> every<00:02:15.750> single<00:02:16.430> protective<00:02:17.430> function<00:02:17.960> you 00:02:18.950 --> 00:02:18.960 align:start position:0% and every single protective function you 00:02:18.960 --> 00:02:20.630 align:start position:0% and every single protective function you use<00:02:18.990> a<00:02:19.290> modifier<00:02:19.740> that<00:02:19.770> basically<00:02:20.160> asked<00:02:20.460> okay 00:02:20.630 --> 00:02:20.640 align:start position:0% use a modifier that basically asked okay 00:02:20.640 --> 00:02:22.460 align:start position:0% use a modifier that basically asked okay is<00:02:20.760> this<00:02:20.910> caller<00:02:21.180> allowed<00:02:21.660> to<00:02:21.870> call<00:02:22.050> me<00:02:22.080> at 00:02:22.460 --> 00:02:22.470 align:start position:0% is this caller allowed to call me at 00:02:22.470 --> 00:02:24.500 align:start position:0% is this caller allowed to call me at this<00:02:22.710> entry<00:02:22.980> point<00:02:23.010> and<00:02:23.400> the<00:02:23.880> authority<00:02:24.300> says 00:02:24.500 --> 00:02:24.510 align:start position:0% this entry point and the authority says 00:02:24.510 --> 00:02:26.690 align:start position:0% this entry point and the authority says yes<00:02:24.750> or<00:02:24.930> no<00:02:24.960> and<00:02:25.080> the<00:02:26.010> authority<00:02:26.460> is 00:02:26.690 --> 00:02:26.700 align:start position:0% yes or no and the authority is 00:02:26.700 --> 00:02:29.150 align:start position:0% yes or no and the authority is bootstrapped<00:02:27.420> with<00:02:27.720> one<00:02:28.620> some<00:02:29.040> other 00:02:29.150 --> 00:02:29.160 align:start position:0% bootstrapped with one some other 00:02:29.160 --> 00:02:31.670 align:start position:0% bootstrapped with one some other contract<00:02:29.730> that<00:02:29.970> already<00:02:30.870> has<00:02:31.080> permission<00:02:31.650> to 00:02:31.670 --> 00:02:31.680 align:start position:0% contract that already has permission to 00:02:31.680 --> 00:02:35.390 align:start position:0% contract that already has permission to call<00:02:32.250> the<00:02:32.870> set<00:02:33.870> can<00:02:34.200> call<00:02:34.500> function<00:02:35.070> on<00:02:35.190> the 00:02:35.390 --> 00:02:35.400 align:start position:0% call the set can call function on the 00:02:35.400 --> 00:02:37.700 align:start position:0% call the set can call function on the authority<00:02:36.270> so<00:02:36.300> basically<00:02:36.900> it<00:02:37.380> has<00:02:37.560> an 00:02:37.700 --> 00:02:37.710 align:start position:0% authority so basically it has an 00:02:37.710 --> 00:02:41.540 align:start position:0% authority so basically it has an implicit<00:02:37.950> owner<00:02:38.310> at<00:02:39.060> the<00:02:39.240> start<00:02:40.190> so<00:02:41.190> the 00:02:41.540 --> 00:02:41.550 align:start position:0% implicit owner at the start so the 00:02:41.550 --> 00:02:43.280 align:start position:0% implicit owner at the start so the components<00:02:42.030> here<00:02:42.209> so<00:02:42.390> yeah<00:02:42.990> that's<00:02:43.200> the 00:02:43.280 --> 00:02:43.290 align:start position:0% components here so yeah that's the 00:02:43.290 --> 00:02:45.500 align:start position:0% components here so yeah that's the authority<00:02:43.709> this<00:02:44.370> is<00:02:44.610> the<00:02:44.760> maker<00:02:44.970> asset 00:02:45.500 --> 00:02:45.510 align:start position:0% authority this is the maker asset 00:02:45.510 --> 00:02:47.360 align:start position:0% authority this is the maker asset platform<00:02:46.170> is<00:02:46.320> what<00:02:46.470> this<00:02:46.620> stands<00:02:46.890> for<00:02:46.980> it's<00:02:47.280> a 00:02:47.360 --> 00:02:47.370 align:start position:0% platform is what this stands for it's a 00:02:47.370 --> 00:02:49.640 align:start position:0% platform is what this stands for it's a conceptual<00:02:48.090> grouping<00:02:48.660> of<00:02:48.780> the<00:02:48.810> registry<00:02:49.440> of 00:02:49.640 --> 00:02:49.650 align:start position:0% conceptual grouping of the registry of 00:02:49.650 --> 00:02:53.270 align:start position:0% conceptual grouping of the registry of assets<00:02:50.690> which<00:02:51.690> all<00:02:51.959> share<00:02:52.100> the<00:02:53.100> same 00:02:53.270 --> 00:02:53.280 align:start position:0% assets which all share the same 00:02:53.280 --> 00:02:55.670 align:start position:0% assets which all share the same interface<00:02:53.580> and<00:02:53.910> semantics<00:02:54.390> that<00:02:55.080> we<00:02:55.170> need<00:02:55.410> to 00:02:55.670 --> 00:02:55.680 align:start position:0% interface and semantics that we need to 00:02:55.680 --> 00:02:59.170 align:start position:0% interface and semantics that we need to be<00:02:55.830> able<00:02:55.920> to<00:02:56.040> use<00:02:56.340> them<00:02:56.550> in<00:02:56.820> the<00:02:57.530> in<00:02:58.530> the 00:02:59.170 --> 00:02:59.180 align:start position:0% be able to use them in the in the 00:02:59.180 --> 00:03:03.680 align:start position:0% be able to use them in the in the collateral<00:03:00.180> that<00:03:00.600> mechanism<00:03:02.330> so<00:03:03.330> here<00:03:03.540> you 00:03:03.680 --> 00:03:03.690 align:start position:0% collateral that mechanism so here you 00:03:03.690 --> 00:03:05.479 align:start position:0% collateral that mechanism so here you can<00:03:03.810> see<00:03:04.050> how<00:03:04.200> we<00:03:04.260> also<00:03:04.739> separate<00:03:05.250> the<00:03:05.340> data 00:03:05.479 --> 00:03:05.489 align:start position:0% can see how we also separate the data 00:03:05.489 --> 00:03:07.790 align:start position:0% can see how we also separate the data and<00:03:05.730> the<00:03:05.790> controller<00:03:06.209> and<00:03:06.720> this<00:03:07.260> is<00:03:07.410> extremely 00:03:07.790 --> 00:03:07.800 align:start position:0% and the controller and this is extremely 00:03:07.800 --> 00:03:09.260 align:start position:0% and the controller and this is extremely useful<00:03:07.920> because<00:03:08.340> for<00:03:08.730> example<00:03:09.090> right<00:03:09.239> now 00:03:09.260 --> 00:03:09.270 align:start position:0% useful because for example right now 00:03:09.270 --> 00:03:11.210 align:start position:0% useful because for example right now these<00:03:09.480> controllers<00:03:10.050> are<00:03:10.320> the<00:03:10.920> simplest 00:03:11.210 --> 00:03:11.220 align:start position:0% these controllers are the simplest 00:03:11.220 --> 00:03:13.250 align:start position:0% these controllers are the simplest possible<00:03:11.489> asset<00:03:11.850> controlling<00:03:12.450> that<00:03:13.020> there<00:03:13.170> is 00:03:13.250 --> 00:03:13.260 align:start position:0% possible asset controlling that there is 00:03:13.260 --> 00:03:14.840 align:start position:0% possible asset controlling that there is a<00:03:13.320> space<00:03:13.530> have<00:03:13.739> a<00:03:13.770> single<00:03:14.130> transfer<00:03:14.489> function 00:03:14.840 --> 00:03:14.850 align:start position:0% a space have a single transfer function 00:03:14.850 --> 00:03:16.699 align:start position:0% a space have a single transfer function and<00:03:15.000> a<00:03:15.060> single<00:03:15.330> event<00:03:15.420> that<00:03:15.630> it<00:03:15.780> fires<00:03:15.959> on<00:03:16.470> that 00:03:16.699 --> 00:03:16.709 align:start position:0% and a single event that it fires on that 00:03:16.709 --> 00:03:19.180 align:start position:0% and a single event that it fires on that transfer<00:03:17.190> but<00:03:18.090> but<00:03:18.420> we're<00:03:18.600> quickly 00:03:19.180 --> 00:03:19.190 align:start position:0% transfer but but we're quickly 00:03:19.190 --> 00:03:21.320 align:start position:0% transfer but but we're quickly converging<00:03:20.190> on<00:03:20.310> some<00:03:20.489> sort<00:03:20.670> of<00:03:20.760> more 00:03:21.320 --> 00:03:21.330 align:start position:0% converging on some sort of more 00:03:21.330 --> 00:03:23.090 align:start position:0% converging on some sort of more reasonable<00:03:21.840> access<00:03:21.989> standards<00:03:22.350> and<00:03:22.709> ones 00:03:23.090 --> 00:03:23.100 align:start position:0% reasonable access standards and ones 00:03:23.100 --> 00:03:24.380 align:start position:0% reasonable access standards and ones that<00:03:23.190> are<00:03:23.280> more<00:03:23.430> powerful<00:03:23.610> and<00:03:23.880> actually<00:03:24.269> let 00:03:24.380 --> 00:03:24.390 align:start position:0% that are more powerful and actually let 00:03:24.390 --> 00:03:26.870 align:start position:0% that are more powerful and actually let you<00:03:24.480> programmatically<00:03:25.080> do<00:03:25.950> things<00:03:26.250> with<00:03:26.519> with 00:03:26.870 --> 00:03:26.880 align:start position:0% you programmatically do things with with 00:03:26.880 --> 00:03:29.660 align:start position:0% you programmatically do things with with your<00:03:27.060> assets<00:03:27.420> so<00:03:27.660> we<00:03:28.170> might<00:03:28.380> want<00:03:28.620> to<00:03:28.709> swap<00:03:29.459> out 00:03:29.660 --> 00:03:29.670 align:start position:0% your assets so we might want to swap out 00:03:29.670 --> 00:03:31.460 align:start position:0% your assets so we might want to swap out the<00:03:29.760> behavior<00:03:29.880> the<00:03:30.090> controller<00:03:30.510> but<00:03:31.320> then 00:03:31.460 --> 00:03:31.470 align:start position:0% the behavior the controller but then 00:03:31.470 --> 00:03:34.370 align:start position:0% the behavior the controller but then keep<00:03:31.680> keep<00:03:32.340> all<00:03:32.459> the<00:03:32.549> balances<00:03:33.000> in<00:03:33.060> place<00:03:33.390> and 00:03:34.370 --> 00:03:34.380 align:start position:0% keep keep all the balances in place and 00:03:34.380 --> 00:03:36.920 align:start position:0% keep keep all the balances in place and so<00:03:34.940> what<00:03:35.940> this<00:03:36.030> means<00:03:36.090> is<00:03:36.360> that<00:03:36.420> the<00:03:36.630> correct 00:03:36.920 --> 00:03:36.930 align:start position:0% so what this means is that the correct 00:03:36.930 --> 00:03:38.210 align:start position:0% so what this means is that the correct way<00:03:37.110> to<00:03:37.140> actually<00:03:37.470> interact<00:03:37.709> with<00:03:37.890> a<00:03:38.040> maker 00:03:38.210 --> 00:03:38.220 align:start position:0% way to actually interact with a maker 00:03:38.220 --> 00:03:40.520 align:start position:0% way to actually interact with a maker system<00:03:38.700> is<00:03:38.910> to<00:03:39.239> use<00:03:39.510> what's<00:03:39.959> called<00:03:40.049> a<00:03:40.290> maker 00:03:40.520 --> 00:03:40.530 align:start position:0% system is to use what's called a maker 00:03:40.530 --> 00:03:43.789 align:start position:0% system is to use what's called a maker user<00:03:40.910> mixin<00:03:41.910> contract<00:03:42.480> which<00:03:43.140> it's<00:03:43.440> just<00:03:43.709> a 00:03:43.789 --> 00:03:43.799 align:start position:0% user mixin contract which it's just a 00:03:43.799 --> 00:03:45.080 align:start position:0% user mixin contract which it's just a bunch<00:03:43.950> of<00:03:44.070> internal<00:03:44.519> functions<00:03:44.910> and 00:03:45.080 --> 00:03:45.090 align:start position:0% bunch of internal functions and 00:03:45.090 --> 00:03:48.170 align:start position:0% bunch of internal functions and modifiers<00:03:45.570> which<00:03:46.560> help<00:03:47.430> you<00:03:47.580> traverse<00:03:47.850> the 00:03:48.170 --> 00:03:48.180 align:start position:0% modifiers which help you traverse the 00:03:48.180 --> 00:03:50.210 align:start position:0% modifiers which help you traverse the maker<00:03:48.390> systems<00:03:48.900> so<00:03:49.170> for<00:03:49.200> example<00:03:49.739> you<00:03:50.190> would 00:03:50.210 --> 00:03:50.220 align:start position:0% maker systems so for example you would 00:03:50.220 --> 00:03:52.550 align:start position:0% maker systems so for example you would inherit<00:03:50.700> from<00:03:50.880> the<00:03:51.090> the<00:03:51.630> maker<00:03:51.810> user<00:03:52.110> contract 00:03:52.550 --> 00:03:52.560 align:start position:0% inherit from the the maker user contract 00:03:52.560 --> 00:03:54.680 align:start position:0% inherit from the the maker user contract it<00:03:52.739> doesn't<00:03:53.040> add<00:03:53.130> any<00:03:53.340> overhead<00:03:53.640> unless<00:03:54.450> you 00:03:54.680 --> 00:03:54.690 align:start position:0% it doesn't add any overhead unless you 00:03:54.690 --> 00:03:56.690 align:start position:0% it doesn't add any overhead unless you actually<00:03:54.900> use<00:03:55.320> for<00:03:55.350> example<00:03:55.590> get<00:03:55.980> assets<00:03:56.459> and 00:03:56.690 --> 00:03:56.700 align:start position:0% actually use for example get assets and 00:03:56.700 --> 00:03:59.120 align:start position:0% actually use for example get assets and then<00:03:56.880> the<00:03:56.910> the<00:03:57.630> maker<00:03:57.810> these<00:03:58.019> are<00:03:58.230> the<00:03:58.799> you 00:03:59.120 --> 00:03:59.130 align:start position:0% then the the maker these are the you 00:03:59.130 --> 00:04:00.530 align:start position:0% then the the maker these are the you know<00:03:59.160> it's<00:03:59.370> a<00:03:59.400> library<00:03:59.760> we<00:03:59.910> publish<00:04:00.239> and<00:04:00.450> it 00:04:00.530 --> 00:04:00.540 align:start position:0% know it's a library we publish and it 00:04:00.540 --> 00:04:01.789 align:start position:0% know it's a library we publish and it has<00:04:00.720> all<00:04:00.930> the<00:04:01.049> details<00:04:01.410> about<00:04:01.530> how<00:04:01.739> to 00:04:01.789 --> 00:04:01.799 align:start position:0% has all the details about how to 00:04:01.799 --> 00:04:03.800 align:start position:0% has all the details about how to actually<00:04:02.760> look<00:04:02.940> up<00:04:03.060> in<00:04:03.209> the<00:04:03.299> registry<00:04:03.690> of<00:04:03.750> the 00:04:03.800 --> 00:04:03.810 align:start position:0% actually look up in the registry of the 00:04:03.810 --> 00:04:08.690 align:start position:0% actually look up in the registry of the controller<00:04:05.690> okay<00:04:06.690> so<00:04:06.900> this<00:04:07.170> is<00:04:07.320> what<00:04:07.700> the 00:04:08.690 --> 00:04:08.700 align:start position:0% controller okay so this is what the 00:04:08.700 --> 00:04:11.060 align:start position:0% controller okay so this is what the initial<00:04:09.180> version<00:04:09.480> look<00:04:09.630> might<00:04:10.560> look<00:04:10.680> like<00:04:10.739> so 00:04:11.060 --> 00:04:11.070 align:start position:0% initial version look might look like so 00:04:11.070 --> 00:04:13.039 align:start position:0% initial version look might look like so now<00:04:11.340> let's<00:04:11.489> look<00:04:11.579> at<00:04:11.670> what<00:04:11.820> the<00:04:11.880> final<00:04:12.120> version 00:04:13.039 --> 00:04:13.049 align:start position:0% now let's look at what the final version 00:04:13.049 --> 00:04:15.590 align:start position:0% now let's look at what the final version might<00:04:13.739> look<00:04:13.890> like<00:04:14.180> so<00:04:15.180> the<00:04:15.269> first<00:04:15.299> thing<00:04:15.540> you 00:04:15.590 --> 00:04:15.600 align:start position:0% might look like so the first thing you 00:04:15.600 --> 00:04:16.880 align:start position:0% might look like so the first thing you might<00:04:15.720> notice<00:04:15.780> is<00:04:16.140> the<00:04:16.260> mistake<00:04:16.560> that<00:04:16.739> I<00:04:16.799> made 00:04:16.880 --> 00:04:16.890 align:start position:0% might notice is the mistake that I made 00:04:16.890 --> 00:04:18.699 align:start position:0% might notice is the mistake that I made that<00:04:17.160> I<00:04:17.220> only<00:04:17.430> noticed<00:04:17.669> like<00:04:18.060> one<00:04:18.209> minute<00:04:18.450> ago 00:04:18.699 --> 00:04:18.709 align:start position:0% that I only noticed like one minute ago 00:04:18.709 --> 00:04:21.110 align:start position:0% that I only noticed like one minute ago obviously<00:04:19.709> this<00:04:19.829> contract<00:04:20.220> system<00:04:20.340> is<00:04:20.579> not<00:04:20.820> an 00:04:21.110 --> 00:04:21.120 align:start position:0% obviously this contract system is not an 00:04:21.120 --> 00:04:24.050 align:start position:0% obviously this contract system is not an off<00:04:21.239> chain<00:04:21.479> service<00:04:21.840> this<00:04:21.959> is<00:04:22.109> all<00:04:22.580> still<00:04:23.580> just 00:04:24.050 --> 00:04:24.060 align:start position:0% off chain service this is all still just 00:04:24.060 --> 00:04:26.270 align:start position:0% off chain service this is all still just some<00:04:24.150> our<00:04:24.240> contracts<00:04:24.720> but<00:04:25.620> each<00:04:25.919> of<00:04:25.950> these<00:04:26.220> is 00:04:26.270 --> 00:04:26.280 align:start position:0% some our contracts but each of these is 00:04:26.280 --> 00:04:28.709 align:start position:0% some our contracts but each of these is is<00:04:27.120> now<00:04:27.240> a<00:04:27.270> cluster<00:04:27.780> so<00:04:27.930> we've<00:04:28.050> zoomed 00:04:28.709 --> 00:04:28.719 align:start position:0% is now a cluster so we've zoomed 00:04:28.719 --> 00:04:30.809 align:start position:0% is now a cluster so we've zoomed this<00:04:29.530> map<00:04:29.770> is<00:04:29.800> what<00:04:30.069> you<00:04:30.129> just<00:04:30.189> saw<00:04:30.520> and<00:04:30.759> I 00:04:30.809 --> 00:04:30.819 align:start position:0% this map is what you just saw and I 00:04:30.819 --> 00:04:33.420 align:start position:0% this map is what you just saw and I exposed<00:04:31.659> the<00:04:32.409> assets<00:04:32.830> feel<00:04:33.069> as<00:04:33.219> little 00:04:33.420 --> 00:04:33.430 align:start position:0% exposed the assets feel as little 00:04:33.430 --> 00:04:36.779 align:start position:0% exposed the assets feel as little contract<00:04:33.819> so<00:04:33.969> you<00:04:34.090> can<00:04:34.240> see<00:04:34.449> how<00:04:35.250> MKR<00:04:36.250> and<00:04:36.490> I<00:04:36.610> in 00:04:36.779 --> 00:04:36.789 align:start position:0% contract so you can see how MKR and I in 00:04:36.789 --> 00:04:39.390 align:start position:0% contract so you can see how MKR and I in particular<00:04:36.939> wired<00:04:37.509> up<00:04:37.719> directly<00:04:38.080> to<00:04:38.139> the<00:04:38.469> CDP 00:04:39.390 --> 00:04:39.400 align:start position:0% particular wired up directly to the CDP 00:04:39.400 --> 00:04:41.490 align:start position:0% particular wired up directly to the CDP engine<00:04:39.909> which<00:04:40.180> is<00:04:40.389> the<00:04:40.569> collateralized<00:04:41.229> debt 00:04:41.490 --> 00:04:41.500 align:start position:0% engine which is the collateralized debt 00:04:41.500 --> 00:04:44.070 align:start position:0% engine which is the collateralized debt position<00:04:41.860> engine<00:04:42.580> which<00:04:43.180> you<00:04:43.509> should<00:04:43.840> read 00:04:44.070 --> 00:04:44.080 align:start position:0% position engine which you should read 00:04:44.080 --> 00:04:45.809 align:start position:0% position engine which you should read the<00:04:44.139> white<00:04:44.289> paper<00:04:44.469> to<00:04:45.189> understand<00:04:45.610> what<00:04:45.729> that 00:04:45.809 --> 00:04:45.819 align:start position:0% the white paper to understand what that 00:04:45.819 --> 00:04:47.040 align:start position:0% the white paper to understand what that is<00:04:45.969> but<00:04:46.120> it's<00:04:46.270> basically<00:04:46.599> a<00:04:46.689> bit<00:04:46.930> of<00:04:46.990> a 00:04:47.040 --> 00:04:47.050 align:start position:0% is but it's basically a bit of a 00:04:47.050 --> 00:04:48.959 align:start position:0% is but it's basically a bit of a fundamental<00:04:47.590> building<00:04:47.740> block<00:04:48.099> that<00:04:48.610> creates 00:04:48.959 --> 00:04:48.969 align:start position:0% fundamental building block that creates 00:04:48.969 --> 00:04:51.959 align:start position:0% fundamental building block that creates and<00:04:49.270> destroys<00:04:49.389> the<00:04:49.780> dye<00:04:50.189> so<00:04:51.189> this<00:04:51.430> this<00:04:51.729> is<00:04:51.879> an 00:04:51.959 --> 00:04:51.969 align:start position:0% and destroys the dye so this this is an 00:04:51.969 --> 00:04:53.939 align:start position:0% and destroys the dye so this this is an example<00:04:52.270> basically<00:04:52.719> you'll<00:04:53.139> notice<00:04:53.439> the 00:04:53.939 --> 00:04:53.949 align:start position:0% example basically you'll notice the 00:04:53.949 --> 00:04:55.499 align:start position:0% example basically you'll notice the second<00:04:54.250> thing<00:04:54.400> is<00:04:54.580> that<00:04:54.639> there's<00:04:55.210> no<00:04:55.360> more 00:04:55.499 --> 00:04:55.509 align:start position:0% second thing is that there's no more 00:04:55.509 --> 00:04:57.869 align:start position:0% second thing is that there's no more nexus<00:04:55.870> in<00:04:55.990> this<00:04:56.110> picture<00:04:56.439> so<00:04:56.469> in<00:04:56.979> the<00:04:57.460> previous 00:04:57.869 --> 00:04:57.879 align:start position:0% nexus in this picture so in the previous 00:04:57.879 --> 00:04:59.339 align:start position:0% nexus in this picture so in the previous slide 00:04:59.339 --> 00:04:59.349 align:start position:0% slide 00:04:59.349 --> 00:05:01.499 align:start position:0% slide I<00:04:59.379> said<00:05:00.159> that<00:05:00.310> Nexus<00:05:00.729> was<00:05:00.909> like<00:05:01.060> the<00:05:01.180> implicit 00:05:01.499 --> 00:05:01.509 align:start position:0% I said that Nexus was like the implicit 00:05:01.509 --> 00:05:03.269 align:start position:0% I said that Nexus was like the implicit owner<00:05:01.810> of<00:05:02.020> the<00:05:02.139> maker<00:05:02.319> authority<00:05:02.830> but<00:05:03.039> some 00:05:03.269 --> 00:05:03.279 align:start position:0% owner of the maker authority but some 00:05:03.279 --> 00:05:06.869 align:start position:0% owner of the maker authority but some somewhere<00:05:04.180> along<00:05:04.330> the<00:05:04.509> line<00:05:05.009> this<00:05:06.009> this<00:05:06.430> is 00:05:06.869 --> 00:05:06.879 align:start position:0% somewhere along the line this this is 00:05:06.879 --> 00:05:08.850 align:start position:0% somewhere along the line this this is going<00:05:07.090> to<00:05:07.180> be<00:05:07.240> transferred<00:05:07.779> first<00:05:08.409> to<00:05:08.500> MK<00:05:08.740> our 00:05:08.850 --> 00:05:08.860 align:start position:0% going to be transferred first to MK our 00:05:08.860 --> 00:05:10.769 align:start position:0% going to be transferred first to MK our stakeholder<00:05:09.520> the<00:05:09.939> the<00:05:10.150> stakeholder<00:05:10.629> vote 00:05:10.769 --> 00:05:10.779 align:start position:0% stakeholder the the stakeholder vote 00:05:10.779 --> 00:05:12.839 align:start position:0% stakeholder the the stakeholder vote directly<00:05:11.050> but<00:05:12.039> then<00:05:12.189> at<00:05:12.310> some<00:05:12.490> point<00:05:12.729> they're 00:05:12.839 --> 00:05:12.849 align:start position:0% directly but then at some point they're 00:05:12.849 --> 00:05:14.369 align:start position:0% directly but then at some point they're going<00:05:12.939> to<00:05:13.000> also<00:05:13.300> think<00:05:13.689> realize<00:05:14.110> that<00:05:14.259> it's 00:05:14.369 --> 00:05:14.379 align:start position:0% going to also think realize that it's 00:05:14.379 --> 00:05:16.110 align:start position:0% going to also think realize that it's wise<00:05:14.560> to<00:05:14.860> put<00:05:15.009> this<00:05:15.159> intermediate<00:05:15.610> governance 00:05:16.110 --> 00:05:16.120 align:start position:0% wise to put this intermediate governance 00:05:16.120 --> 00:05:18.959 align:start position:0% wise to put this intermediate governance contract<00:05:16.629> between<00:05:17.620> themselves<00:05:17.830> and<00:05:18.490> admin 00:05:18.959 --> 00:05:18.969 align:start position:0% contract between themselves and admin 00:05:18.969 --> 00:05:20.640 align:start position:0% contract between themselves and admin rights<00:05:19.210> which<00:05:19.509> is<00:05:19.539> basically<00:05:20.169> the<00:05:20.319> ability<00:05:20.439> to 00:05:20.640 --> 00:05:20.650 align:start position:0% rights which is basically the ability to 00:05:20.650 --> 00:05:25.409 align:start position:0% rights which is basically the ability to modify<00:05:21.069> the<00:05:21.789> authority's<00:05:22.409> permissions<00:05:24.419> and 00:05:25.409 --> 00:05:25.419 align:start position:0% modify the authority's permissions and 00:05:25.419 --> 00:05:29.179 align:start position:0% modify the authority's permissions and so<00:05:26.279> but<00:05:27.279> basically<00:05:27.430> the<00:05:27.759> idea<00:05:27.789> here<00:05:28.389> is<00:05:28.419> that 00:05:29.179 --> 00:05:29.189 align:start position:0% so but basically the idea here is that 00:05:29.189 --> 00:05:31.709 align:start position:0% so but basically the idea here is that this<00:05:30.189> is<00:05:30.340> an<00:05:30.460> example<00:05:30.580> of<00:05:30.909> how<00:05:31.060> adapt<00:05:31.509> can 00:05:31.709 --> 00:05:31.719 align:start position:0% this is an example of how adapt can 00:05:31.719 --> 00:05:33.719 align:start position:0% this is an example of how adapt can start<00:05:31.990> out<00:05:32.110> highly<00:05:32.830> centralized<00:05:33.370> and<00:05:33.580> very 00:05:33.719 --> 00:05:33.729 align:start position:0% start out highly centralized and very 00:05:33.729 --> 00:05:36.029 align:start position:0% start out highly centralized and very trustful<00:05:34.180> and<00:05:34.599> then<00:05:34.750> over<00:05:35.349> time<00:05:35.589> you<00:05:35.830> can 00:05:36.029 --> 00:05:36.039 align:start position:0% trustful and then over time you can 00:05:36.039 --> 00:05:39.180 align:start position:0% trustful and then over time you can basically<00:05:36.669> update<00:05:37.300> it<00:05:37.449> to<00:05:37.779> lock<00:05:38.589> it<00:05:38.620> lock<00:05:38.919> down 00:05:39.180 --> 00:05:39.190 align:start position:0% basically update it to lock it lock down 00:05:39.190 --> 00:05:42.390 align:start position:0% basically update it to lock it lock down some<00:05:39.219> of<00:05:39.520> its<00:05:39.699> behavior<00:05:40.599> and<00:05:40.810> then<00:05:41.069> any<00:05:42.069> you 00:05:42.390 --> 00:05:42.400 align:start position:0% some of its behavior and then any you 00:05:42.400 --> 00:05:44.909 align:start position:0% some of its behavior and then any you know<00:05:42.490> why<00:05:43.120> I<00:05:43.779> think<00:05:44.020> we<00:05:44.379> can<00:05:44.500> call<00:05:44.650> maker 00:05:44.909 --> 00:05:44.919 align:start position:0% know why I think we can call maker 00:05:44.919 --> 00:05:46.499 align:start position:0% know why I think we can call maker trustless<00:05:45.639> even<00:05:46.000> though<00:05:46.089> there's<00:05:46.270> still<00:05:46.360> a 00:05:46.499 --> 00:05:46.509 align:start position:0% trustless even though there's still a 00:05:46.509 --> 00:05:48.420 align:start position:0% trustless even though there's still a governing<00:05:46.990> body<00:05:47.169> that<00:05:47.349> sort<00:05:47.770> of<00:05:47.800> has<00:05:47.979> two<00:05:48.129> sets 00:05:48.420 --> 00:05:48.430 align:start position:0% governing body that sort of has two sets 00:05:48.430 --> 00:05:51.029 align:start position:0% governing body that sort of has two sets high<00:05:48.699> level<00:05:49.029> monetary<00:05:49.449> policy<00:05:49.990> is<00:05:50.319> because 00:05:51.029 --> 00:05:51.039 align:start position:0% high level monetary policy is because 00:05:51.039 --> 00:05:52.920 align:start position:0% high level monetary policy is because there's<00:05:51.310> this<00:05:51.550> governance<00:05:52.270> contract<00:05:52.750> where 00:05:52.920 --> 00:05:52.930 align:start position:0% there's this governance contract where 00:05:52.930 --> 00:05:55.740 align:start position:0% there's this governance contract where or<00:05:53.259> MKR<00:05:53.770> folders<00:05:54.099> to<00:05:54.279> provably<00:05:54.849> restrict 00:05:55.740 --> 00:05:55.750 align:start position:0% or MKR folders to provably restrict 00:05:55.750 --> 00:05:58.559 align:start position:0% or MKR folders to provably restrict their<00:05:55.870> own<00:05:55.960> powers<00:05:56.409> and<00:05:57.009> the<00:05:57.669> most<00:05:57.849> popular 00:05:58.559 --> 00:05:58.569 align:start position:0% their own powers and the most popular 00:05:58.569 --> 00:06:01.050 align:start position:0% their own powers and the most popular example<00:05:58.960> for<00:05:59.080> that<00:05:59.229> is<00:05:59.289> the<00:06:00.060> time-delayed 00:06:01.050 --> 00:06:01.060 align:start position:0% example for that is the time-delayed 00:06:01.060 --> 00:06:03.510 align:start position:0% example for that is the time-delayed admin<00:06:01.779> action<00:06:02.110> so<00:06:02.349> if<00:06:02.409> the<00:06:02.560> MKR<00:06:03.009> holders<00:06:03.370> are 00:06:03.510 --> 00:06:03.520 align:start position:0% admin action so if the MKR holders are 00:06:03.520 --> 00:06:04.980 align:start position:0% admin action so if the MKR holders are going<00:06:03.639> to<00:06:03.729> do<00:06:03.849> some<00:06:04.089> administrative<00:06:04.300> action 00:06:04.980 --> 00:06:04.990 align:start position:0% going to do some administrative action 00:06:04.990 --> 00:06:08.519 align:start position:0% going to do some administrative action on<00:06:05.080> the<00:06:05.169> system<00:06:06.210> everyone<00:06:07.210> has<00:06:07.449> maybe<00:06:08.169> a<00:06:08.289> week 00:06:08.519 --> 00:06:08.529 align:start position:0% on the system everyone has maybe a week 00:06:08.529 --> 00:06:11.399 align:start position:0% on the system everyone has maybe a week at<00:06:08.949> near<00:06:09.669> the<00:06:09.699> start<00:06:10.029> and<00:06:10.210> then<00:06:10.300> maybe<00:06:10.479> it<00:06:10.990> can 00:06:11.399 --> 00:06:11.409 align:start position:0% at near the start and then maybe it can 00:06:11.409 --> 00:06:13.290 align:start position:0% at near the start and then maybe it can be<00:06:11.469> up<00:06:11.589> to<00:06:11.710> a<00:06:11.740> year<00:06:11.830> if<00:06:12.550> the<00:06:12.699> system<00:06:13.029> is<00:06:13.150> running 00:06:13.290 --> 00:06:13.300 align:start position:0% be up to a year if the system is running 00:06:13.300 --> 00:06:16.950 align:start position:0% be up to a year if the system is running and<00:06:13.719> it's<00:06:13.870> very<00:06:14.050> stable<00:06:14.259> for<00:06:14.589> a<00:06:14.620> long<00:06:14.800> time<00:06:15.960> so 00:06:16.950 --> 00:06:16.960 align:start position:0% and it's very stable for a long time so 00:06:16.960 --> 00:06:19.230 align:start position:0% and it's very stable for a long time so I<00:06:17.379> think<00:06:17.860> I<00:06:18.069> have<00:06:18.219> enough<00:06:18.430> time<00:06:18.580> to<00:06:18.729> basically 00:06:19.230 --> 00:06:19.240 align:start position:0% I think I have enough time to basically 00:06:19.240 --> 00:06:20.969 align:start position:0% I think I have enough time to basically just<00:06:19.509> actually<00:06:19.750> describe<00:06:20.259> how<00:06:20.469> these<00:06:20.589> system 00:06:20.969 --> 00:06:20.979 align:start position:0% just actually describe how these system 00:06:20.979 --> 00:06:26.670 align:start position:0% just actually describe how these system parts<00:06:21.669> interact<00:06:21.849> so<00:06:22.689> the<00:06:25.349> you<00:06:26.349> know<00:06:26.439> here 00:06:26.670 --> 00:06:26.680 align:start position:0% parts interact so the you know here 00:06:26.680 --> 00:06:29.390 align:start position:0% parts interact so the you know here these<00:06:27.009> are<00:06:27.189> all<00:06:27.219> simply<00:06:27.580> registry<00:06:28.479> entries 00:06:29.390 --> 00:06:29.400 align:start position:0% these are all simply registry entries 00:06:29.400 --> 00:06:34.200 align:start position:0% these are all simply registry entries the<00:06:30.400> nkr<00:06:31.289> this<00:06:32.289> talks<00:06:32.889> to<00:06:33.039> the<00:06:33.129> governance<00:06:33.490> to 00:06:34.200 --> 00:06:34.210 align:start position:0% the nkr this talks to the governance to 00:06:34.210 --> 00:06:38.040 align:start position:0% the nkr this talks to the governance to try<00:06:34.539> to<00:06:35.279> cause<00:06:36.279> changes<00:06:36.699> to<00:06:36.759> the<00:06:36.909> system<00:06:37.089> that 00:06:38.040 --> 00:06:38.050 align:start position:0% try to cause changes to the system that 00:06:38.050 --> 00:06:40.350 align:start position:0% try to cause changes to the system that might<00:06:38.229> affect<00:06:38.589> who<00:06:38.889> the<00:06:39.009> feed<00:06:39.190> providers<00:06:39.639> are 00:06:40.350 --> 00:06:40.360 align:start position:0% might affect who the feed providers are 00:06:40.360 --> 00:06:43.439 align:start position:0% might affect who the feed providers are it<00:06:40.599> might<00:06:40.810> affect<00:06:41.139> more<00:06:42.099> basic<00:06:42.460> stuff<00:06:42.699> like<00:06:43.360> in 00:06:43.439 --> 00:06:43.449 align:start position:0% it might affect more basic stuff like in 00:06:43.449 --> 00:06:45.899 align:start position:0% it might affect more basic stuff like in the<00:06:43.539> contract<00:06:44.050> permission<00:06:44.500> wiring<00:06:44.889> and<00:06:45.789> it 00:06:45.899 --> 00:06:45.909 align:start position:0% the contract permission wiring and it 00:06:45.909 --> 00:06:47.459 align:start position:0% the contract permission wiring and it also<00:06:46.030> might<00:06:46.240> affect<00:06:46.569> just<00:06:46.840> move<00:06:46.960> the<00:06:47.050> monetary 00:06:47.459 --> 00:06:47.469 align:start position:0% also might affect just move the monetary 00:06:47.469 --> 00:06:50.279 align:start position:0% also might affect just move the monetary policy<00:06:47.680> inside<00:06:48.430> the<00:06:48.580> CDP<00:06:48.849> engine<00:06:49.270> and<00:06:50.169> then 00:06:50.279 --> 00:06:50.289 align:start position:0% policy inside the CDP engine and then 00:06:50.289 --> 00:06:52.459 align:start position:0% policy inside the CDP engine and then the<00:06:50.379> CVP<00:06:50.770> engine<00:06:51.069> has<00:06:51.250> unique<00:06:51.520> permissions<00:06:52.060> to 00:06:52.459 --> 00:06:52.469 align:start position:0% the CVP engine has unique permissions to 00:06:52.469 --> 00:06:56.480 align:start position:0% the CVP engine has unique permissions to spend<00:06:53.469> money<00:06:53.650> out<00:06:53.860> of<00:06:53.979> the<00:06:54.069> vault<00:06:54.360> which<00:06:55.360> is 00:06:56.480 --> 00:06:56.490 align:start position:0% spend money out of the vault which is 00:06:56.490 --> 00:06:59.670 align:start position:0% spend money out of the vault which is the<00:06:57.659> it's<00:06:58.659> basically<00:06:58.810> where<00:06:59.259> the<00:06:59.379> insurance 00:06:59.670 --> 00:06:59.680 align:start position:0% the it's basically where the insurance 00:06:59.680 --> 00:07:02.100 align:start position:0% the it's basically where the insurance pool<00:07:00.039> is<00:07:00.219> of<00:07:00.550> collected<00:07:01.060> died<00:07:01.210> and<00:07:01.509> then<00:07:01.960> it's 00:07:02.100 --> 00:07:02.110 align:start position:0% pool is of collected died and then it's 00:07:02.110 --> 00:07:04.649 align:start position:0% pool is of collected died and then it's also<00:07:02.289> where<00:07:02.939> assets<00:07:03.939> that<00:07:04.240> might<00:07:04.389> have<00:07:04.539> been 00:07:04.649 --> 00:07:04.659 align:start position:0% also where assets that might have been 00:07:04.659 --> 00:07:07.110 align:start position:0% also where assets that might have been emergency<00:07:05.349> bailed<00:07:05.710> out<00:07:05.889> they<00:07:06.729> go<00:07:06.879> there 00:07:07.110 --> 00:07:07.120 align:start position:0% emergency bailed out they go there 00:07:07.120 --> 00:07:10.980 align:start position:0% emergency bailed out they go there before<00:07:07.479> they're<00:07:07.629> auctioned<00:07:08.020> off<00:07:09.569> okay<00:07:10.569> so<00:07:10.629> I 00:07:10.980 --> 00:07:10.990 align:start position:0% before they're auctioned off okay so I 00:07:10.990 --> 00:07:13.559 align:start position:0% before they're auctioned off okay so I also<00:07:11.409> wants<00:07:11.740> to<00:07:11.770> go<00:07:12.340> ahead<00:07:12.460> and<00:07:12.699> show<00:07:13.389> this 00:07:13.559 --> 00:07:13.569 align:start position:0% also wants to go ahead and show this 00:07:13.569 --> 00:07:17.159 align:start position:0% also wants to go ahead and show this part<00:07:14.199> which<00:07:14.409> is<00:07:14.439> that<00:07:15.870> another<00:07:16.870> really 00:07:17.159 --> 00:07:17.169 align:start position:0% part which is that another really 00:07:17.169 --> 00:07:18.629 align:start position:0% part which is that another really important<00:07:17.529> component<00:07:17.650> of<00:07:17.979> the<00:07:18.069> maker<00:07:18.250> system 00:07:18.629 --> 00:07:18.639 align:start position:0% important component of the maker system 00:07:18.639 --> 00:07:21.809 align:start position:0% important component of the maker system is<00:07:18.819> that<00:07:19.060> there<00:07:19.449> are<00:07:19.569> several<00:07:20.819> incentivize 00:07:21.809 --> 00:07:21.819 align:start position:0% is that there are several incentivize 00:07:21.819 --> 00:07:23.640 align:start position:0% is that there are several incentivize actions<00:07:22.360> that<00:07:22.539> have<00:07:22.779> to<00:07:22.930> happen<00:07:23.289> quickly<00:07:23.469> and 00:07:23.640 --> 00:07:23.650 align:start position:0% actions that have to happen quickly and 00:07:23.650 --> 00:07:26.309 align:start position:0% actions that have to happen quickly and reliably<00:07:23.830> and<00:07:24.490> so<00:07:25.419> you<00:07:25.479> know<00:07:25.779> we<00:07:25.900> say<00:07:26.110> like 00:07:26.309 --> 00:07:26.319 align:start position:0% reliably and so you know we say like 00:07:26.319 --> 00:07:28.290 align:start position:0% reliably and so you know we say like okay<00:07:26.560> the<00:07:26.680> theory<00:07:27.009> is<00:07:27.099> if<00:07:27.550> it's<00:07:27.699> profitable 00:07:28.290 --> 00:07:28.300 align:start position:0% okay the theory is if it's profitable 00:07:28.300 --> 00:07:31.339 align:start position:0% okay the theory is if it's profitable then<00:07:29.189> you<00:07:30.189> we<00:07:30.310> should<00:07:30.490> expect<00:07:30.759> it<00:07:30.879> to<00:07:30.969> happen 00:07:31.339 --> 00:07:31.349 align:start position:0% then you we should expect it to happen 00:07:31.349 --> 00:07:33.330 align:start position:0% then you we should expect it to happen automatically<00:07:32.349> but<00:07:32.500> in<00:07:32.650> but<00:07:32.889> we<00:07:33.039> want<00:07:33.219> to 00:07:33.330 --> 00:07:33.340 align:start position:0% automatically but in but we want to 00:07:33.340 --> 00:07:36.089 align:start position:0% automatically but in but we want to actually<00:07:33.509> make<00:07:34.509> sure<00:07:34.539> this<00:07:34.810> happens<00:07:35.050> so<00:07:35.439> Nexus 00:07:36.089 --> 00:07:36.099 align:start position:0% actually make sure this happens so Nexus 00:07:36.099 --> 00:07:39.300 align:start position:0% actually make sure this happens so Nexus is<00:07:36.250> creating<00:07:36.729> a<00:07:36.909> I<00:07:37.900> guess<00:07:38.680> the<00:07:38.800> software<00:07:39.279> a 00:07:39.300 --> 00:07:39.310 align:start position:0% is creating a I guess the software a 00:07:39.310 --> 00:07:43.170 align:start position:0% is creating a I guess the software a stack<00:07:39.719> for<00:07:41.219> basically<00:07:42.219> a<00:07:42.250> single<00:07:42.639> node<00:07:42.879> which 00:07:43.170 --> 00:07:43.180 align:start position:0% stack for basically a single node which 00:07:43.180 --> 00:07:44.760 align:start position:0% stack for basically a single node which will<00:07:43.210> try<00:07:43.719> to<00:07:43.750> make<00:07:44.050> as<00:07:44.169> much<00:07:44.349> money<00:07:44.409> as 00:07:44.760 --> 00:07:44.770 align:start position:0% will try to make as much money as 00:07:44.770 --> 00:07:46.829 align:start position:0% will try to make as much money as possible<00:07:44.800> off<00:07:45.400> of<00:07:45.550> aetherium<00:07:45.909> because<00:07:46.629> it 00:07:46.829 --> 00:07:46.839 align:start position:0% possible off of aetherium because it 00:07:46.839 --> 00:07:48.839 align:start position:0% possible off of aetherium because it will<00:07:47.050> be<00:07:47.169> aware<00:07:47.500> of<00:07:47.800> all<00:07:48.580> the<00:07:48.729> different 00:07:48.839 --> 00:07:48.849 align:start position:0% will be aware of all the different 00:07:48.849 --> 00:07:51.899 align:start position:0% will be aware of all the different incentivized<00:07:49.750> actions<00:07:50.500> that<00:07:50.650> I<00:07:50.710> can<00:07:51.460> take<00:07:51.699> for 00:07:51.899 --> 00:07:51.909 align:start position:0% incentivized actions that I can take for 00:07:51.909 --> 00:07:55.290 align:start position:0% incentivized actions that I can take for example<00:07:52.050> the<00:07:53.050> margin<00:07:53.409> calls<00:07:53.620> or<00:07:53.949> the<00:07:54.069> the<00:07:54.729> more 00:07:55.290 --> 00:07:55.300 align:start position:0% example the margin calls or the the more 00:07:55.300 --> 00:07:56.969 align:start position:0% example the margin calls or the the more accurate<00:07:55.629> is<00:07:55.719> the<00:07:55.839> collateral<00:07:56.110> redemption<00:07:56.800> in 00:07:56.969 --> 00:07:56.979 align:start position:0% accurate is the collateral redemption in 00:07:56.979 --> 00:07:58.950 align:start position:0% accurate is the collateral redemption in the<00:07:57.009> CDP's<00:07:57.520> that's<00:07:58.180> an<00:07:58.330> example<00:07:58.719> of<00:07:58.779> something 00:07:58.950 --> 00:07:58.960 align:start position:0% the CDP's that's an example of something 00:07:58.960 --> 00:08:00.420 align:start position:0% the CDP's that's an example of something that<00:07:59.050> needs<00:07:59.349> to<00:07:59.379> happen<00:07:59.469> automatically<00:08:00.219> but 00:08:00.420 --> 00:08:00.430 align:start position:0% that needs to happen automatically but 00:08:00.430 --> 00:08:01.950 align:start position:0% that needs to happen automatically but it's<00:08:00.550> actually<00:08:00.819> profitable<00:08:01.330> for<00:08:01.509> the<00:08:01.599> person 00:08:01.950 --> 00:08:01.960 align:start position:0% it's actually profitable for the person 00:08:01.960 --> 00:08:04.709 align:start position:0% it's actually profitable for the person to<00:08:02.080> use<00:08:02.199> so<00:08:02.409> this<00:08:02.560> is<00:08:02.650> an<00:08:02.740> example<00:08:03.330> oh<00:08:04.330> yeah 00:08:04.709 --> 00:08:04.719 align:start position:0% to use so this is an example oh yeah 00:08:04.719 --> 00:08:06.209 align:start position:0% to use so this is an example oh yeah another<00:08:04.900> another<00:08:05.259> great<00:08:05.469> example<00:08:05.560> is<00:08:05.949> like 00:08:06.209 --> 00:08:06.219 align:start position:0% another another great example is like 00:08:06.219 --> 00:08:09.329 align:start position:0% another another great example is like how<00:08:07.180> you<00:08:07.870> know<00:08:07.960> the<00:08:08.080> alarm<00:08:08.259> clock<00:08:08.589> app<00:08:08.830> also 00:08:09.329 --> 00:08:09.339 align:start position:0% how you know the alarm clock app also 00:08:09.339 --> 00:08:11.339 align:start position:0% how you know the alarm clock app also has<00:08:09.550> incentivized<00:08:10.180> actions<00:08:10.599> so<00:08:10.870> there's<00:08:11.169> no 00:08:11.339 --> 00:08:11.349 align:start position:0% has incentivized actions so there's no 00:08:11.349 --> 00:08:14.279 align:start position:0% has incentivized actions so there's no you<00:08:11.589> know<00:08:11.710> we<00:08:11.830> would<00:08:12.659> bundle<00:08:13.659> that<00:08:13.810> into<00:08:14.110> in 00:08:14.279 --> 00:08:14.289 align:start position:0% you know we would bundle that into in 00:08:14.289 --> 00:08:19.790 align:start position:0% you know we would bundle that into in civic<00:08:14.650> keeper<00:08:15.279> stack<00:08:15.490> as<00:08:15.639> well<00:08:16.199> and<00:08:17.199> so<00:08:18.060> yes<00:08:19.060> so 00:08:19.790 --> 00:08:19.800 align:start position:0% civic keeper stack as well and so yes so 00:08:19.800 --> 00:08:23.129 align:start position:0% civic keeper stack as well and so yes so all<00:08:20.800> this<00:08:20.979> is<00:08:21.159> great<00:08:21.419> but<00:08:22.419> this<00:08:22.750> this<00:08:22.990> is<00:08:23.110> a 00:08:23.129 --> 00:08:23.139 align:start position:0% all this is great but this this is a 00:08:23.139 --> 00:08:24.959 align:start position:0% all this is great but this this is a really<00:08:23.439> this<00:08:23.770> is<00:08:23.830> a<00:08:23.949> really<00:08:24.189> long<00:08:24.339> way<00:08:24.580> off<00:08:24.759> and 00:08:24.959 --> 00:08:24.969 align:start position:0% really this is a really long way off and 00:08:24.969 --> 00:08:27.149 align:start position:0% really this is a really long way off and I<00:08:25.719> always<00:08:25.990> hate<00:08:26.589> to<00:08:26.710> tell<00:08:26.889> people<00:08:27.009> these 00:08:27.149 --> 00:08:27.159 align:start position:0% I always hate to tell people these 00:08:27.159 --> 00:08:29.249 align:start position:0% I always hate to tell people these really<00:08:27.400> conservative<00:08:27.909> estimates<00:08:28.330> for<00:08:28.509> when 00:08:29.249 --> 00:08:29.259 align:start position:0% really conservative estimates for when 00:08:29.259 --> 00:08:31.679 align:start position:0% really conservative estimates for when they<00:08:29.680> die<00:08:30.039> as<00:08:30.550> described<00:08:31.120> in<00:08:31.210> the<00:08:31.330> white<00:08:31.449> paper 00:08:31.679 --> 00:08:31.689 align:start position:0% they die as described in the white paper 00:08:31.689 --> 00:08:33.779 align:start position:0% they die as described in the white paper is<00:08:31.810> going<00:08:31.960> to<00:08:32.019> be<00:08:32.140> launched<00:08:32.589> but<00:08:33.459> I'm<00:08:33.550> really 00:08:33.779 --> 00:08:33.789 align:start position:0% is going to be launched but I'm really 00:08:33.789 --> 00:08:36.139 align:start position:0% is going to be launched but I'm really happy<00:08:34.089> to<00:08:34.479> announce<00:08:34.510> that<00:08:34.899> we<00:08:35.409> have 00:08:36.139 --> 00:08:36.149 align:start position:0% happy to announce that we have 00:08:36.149 --> 00:08:40.370 align:start position:0% happy to announce that we have identified<00:08:37.149> a<00:08:37.300> strategy<00:08:37.899> for<00:08:38.260> making<00:08:38.800> a 00:08:40.370 --> 00:08:40.380 align:start position:0% identified a strategy for making a 00:08:40.380 --> 00:08:43.100 align:start position:0% identified a strategy for making a series<00:08:41.380> of<00:08:41.409> dye<00:08:41.680> releases<00:08:42.250> which<00:08:42.550> are 00:08:43.100 --> 00:08:43.110 align:start position:0% series of dye releases which are 00:08:43.110 --> 00:08:45.540 align:start position:0% series of dye releases which are increasingly<00:08:44.110> trustless<00:08:44.800> as<00:08:44.980> time<00:08:45.220> goes<00:08:45.399> on 00:08:45.540 --> 00:08:45.550 align:start position:0% increasingly trustless as time goes on 00:08:45.550 --> 00:08:48.569 align:start position:0% increasingly trustless as time goes on so<00:08:45.790> the<00:08:45.910> the<00:08:46.209> first<00:08:46.560> mechanism<00:08:47.560> you<00:08:48.459> might 00:08:48.569 --> 00:08:48.579 align:start position:0% so the the first mechanism you might 00:08:48.579 --> 00:08:50.010 align:start position:0% so the the first mechanism you might have<00:08:48.760> to<00:08:48.850> trust<00:08:49.060> us<00:08:49.209> completely<00:08:49.540> and<00:08:49.779> we<00:08:49.870> might 00:08:50.010 --> 00:08:50.020 align:start position:0% have to trust us completely and we might 00:08:50.020 --> 00:08:51.840 align:start position:0% have to trust us completely and we might even<00:08:50.170> do<00:08:50.319> whitelisting<00:08:50.860> just<00:08:51.100> to<00:08:51.250> avoid<00:08:51.490> any 00:08:51.840 --> 00:08:51.850 align:start position:0% even do whitelisting just to avoid any 00:08:51.850 --> 00:08:52.260 align:start position:0% even do whitelisting just to avoid any call 00:08:52.260 --> 00:08:52.270 align:start position:0% call 00:08:52.270 --> 00:08:55.890 align:start position:0% call with<00:08:52.450> that<00:08:52.630> but<00:08:53.320> then<00:08:53.470> as<00:08:53.680> we<00:08:54.210> as<00:08:55.210> we<00:08:55.240> can<00:08:55.690> make 00:08:55.890 --> 00:08:55.900 align:start position:0% with that but then as we as we can make 00:08:55.900 --> 00:08:58.560 align:start position:0% with that but then as we as we can make it<00:08:56.020> more<00:08:56.200> and<00:08:56.320> more<00:08:56.470> trust<00:08:56.830> less<00:08:57.070> than<00:08:57.480> even<00:08:58.480> if 00:08:58.560 --> 00:08:58.570 align:start position:0% it more and more trust less than even if 00:08:58.570 --> 00:09:01.350 align:start position:0% it more and more trust less than even if the<00:08:58.660> exact<00:08:58.960> mechanisms<00:08:59.500> changes<00:09:00.040> as<00:09:00.880> long<00:09:01.240> as 00:09:01.350 --> 00:09:01.360 align:start position:0% the exact mechanisms changes as long as 00:09:01.360 --> 00:09:03.450 align:start position:0% the exact mechanisms changes as long as you<00:09:01.510> make<00:09:01.960> the<00:09:02.140> stay<00:09:02.650> the<00:09:02.800> right<00:09:02.980> guarantees 00:09:03.450 --> 00:09:03.460 align:start position:0% you make the stay the right guarantees 00:09:03.460 --> 00:09:05.070 align:start position:0% you make the stay the right guarantees and<00:09:03.760> as<00:09:03.850> long<00:09:04.030> as<00:09:04.060> you<00:09:04.270> basically<00:09:04.630> have<00:09:04.840> enough 00:09:05.070 --> 00:09:05.080 align:start position:0% and as long as you basically have enough 00:09:05.080 --> 00:09:07.860 align:start position:0% and as long as you basically have enough money<00:09:05.290> to<00:09:05.410> back<00:09:05.890> to<00:09:06.360> buffer<00:09:07.360> the<00:09:07.480> buy<00:09:07.600> back 00:09:07.860 --> 00:09:07.870 align:start position:0% money to back to buffer the buy back 00:09:07.870 --> 00:09:11.150 align:start position:0% money to back to buffer the buy back from<00:09:08.110> one<00:09:08.290> type<00:09:08.710> into<00:09:08.950> the<00:09:09.040> other<00:09:09.240> you<00:09:10.240> can 00:09:11.150 --> 00:09:11.160 align:start position:0% from one type into the other you can 00:09:11.160 --> 00:09:14.130 align:start position:0% from one type into the other you can basically<00:09:12.160> do<00:09:13.120> this<00:09:13.270> transition<00:09:13.720> behind<00:09:14.050> the 00:09:14.130 --> 00:09:14.140 align:start position:0% basically do this transition behind the 00:09:14.140 --> 00:09:16.980 align:start position:0% basically do this transition behind the scenes<00:09:14.350> and<00:09:14.530> anyone<00:09:14.950> who<00:09:15.100> uses<00:09:15.370> a<00:09:15.550> die<00:09:15.970> in<00:09:16.630> a 00:09:16.980 --> 00:09:16.990 align:start position:0% scenes and anyone who uses a die in a 00:09:16.990 --> 00:09:19.170 align:start position:0% scenes and anyone who uses a die in a smart<00:09:17.260> contract<00:09:17.460> they<00:09:18.460> don't<00:09:18.700> even<00:09:18.820> have<00:09:19.030> to 00:09:19.170 --> 00:09:19.180 align:start position:0% smart contract they don't even have to 00:09:19.180 --> 00:09:21.270 align:start position:0% smart contract they don't even have to be<00:09:20.080> aware<00:09:20.320> that<00:09:20.380> this<00:09:20.620> transition<00:09:21.160> is 00:09:21.270 --> 00:09:21.280 align:start position:0% be aware that this transition is 00:09:21.280 --> 00:09:24.780 align:start position:0% be aware that this transition is happening<00:09:21.310> so<00:09:22.350> this<00:09:23.350> is<00:09:23.530> exciting<00:09:23.950> because<00:09:24.400> it 00:09:24.780 --> 00:09:24.790 align:start position:0% happening so this is exciting because it 00:09:24.790 --> 00:09:27.120 align:start position:0% happening so this is exciting because it basically<00:09:24.880> there<00:09:25.870> are<00:09:25.900> a<00:09:25.990> lot<00:09:26.140> of<00:09:26.170> people<00:09:26.950> who 00:09:27.120 --> 00:09:27.130 align:start position:0% basically there are a lot of people who 00:09:27.130 --> 00:09:29.760 align:start position:0% basically there are a lot of people who they<00:09:28.090> just<00:09:28.330> they<00:09:28.600> want<00:09:28.840> a<00:09:28.930> stable<00:09:29.470> point<00:09:29.590> but 00:09:29.760 --> 00:09:29.770 align:start position:0% they just they want a stable point but 00:09:29.770 --> 00:09:31.650 align:start position:0% they just they want a stable point but they<00:09:29.860> they<00:09:30.190> just<00:09:30.220> want<00:09:30.580> like<00:09:30.760> a<00:09:30.970> small<00:09:31.390> amount 00:09:31.650 --> 00:09:31.660 align:start position:0% they they just want like a small amount 00:09:31.660 --> 00:09:33.030 align:start position:0% they they just want like a small amount they<00:09:31.960> just<00:09:32.110> want<00:09:32.230> to<00:09:32.260> do<00:09:32.380> a<00:09:32.410> simple<00:09:32.650> proof<00:09:32.890> of 00:09:33.030 --> 00:09:33.040 align:start position:0% they just want to do a simple proof of 00:09:33.040 --> 00:09:34.410 align:start position:0% they just want to do a simple proof of concept<00:09:33.460> and<00:09:33.520> it's<00:09:33.700> not<00:09:33.880> going<00:09:34.030> to<00:09:34.120> be<00:09:34.180> an<00:09:34.270> app 00:09:34.410 --> 00:09:34.420 align:start position:0% concept and it's not going to be an app 00:09:34.420 --> 00:09:36.930 align:start position:0% concept and it's not going to be an app that<00:09:34.690> is<00:09:35.320> gonna<00:09:35.770> be<00:09:36.220> holding<00:09:36.520> a<00:09:36.580> ton<00:09:36.730> of<00:09:36.760> money 00:09:36.930 --> 00:09:36.940 align:start position:0% that is gonna be holding a ton of money 00:09:36.940 --> 00:09:39.000 align:start position:0% that is gonna be holding a ton of money and<00:09:37.120> it<00:09:37.210> doesn't<00:09:37.240> requires<00:09:37.870> trust<00:09:38.140> and<00:09:38.290> so<00:09:38.890> I'm 00:09:39.000 --> 00:09:39.010 align:start position:0% and it doesn't requires trust and so I'm 00:09:39.010 --> 00:09:41.010 align:start position:0% and it doesn't requires trust and so I'm happy<00:09:39.190> to<00:09:39.400> announce<00:09:39.580> that<00:09:39.760> this<00:09:40.420> is<00:09:40.540> possible 00:09:41.010 --> 00:09:41.020 align:start position:0% happy to announce that this is possible 00:09:41.020 --> 00:09:43.860 align:start position:0% happy to announce that this is possible and<00:09:41.200> astute<00:09:42.130> viewers<00:09:42.850> would<00:09:43.480> have<00:09:43.600> noticed 00:09:43.860 --> 00:09:43.870 align:start position:0% and astute viewers would have noticed 00:09:43.870 --> 00:09:46.680 align:start position:0% and astute viewers would have noticed that<00:09:43.960> in<00:09:44.380> the<00:09:44.500> version<00:09:44.710> 0<00:09:45.130> there<00:09:45.880> is<00:09:46.000> a<00:09:46.030> die<00:09:46.300> a 00:09:46.680 --> 00:09:46.690 align:start position:0% that in the version 0 there is a die a 00:09:46.690 --> 00:09:48.540 align:start position:0% that in the version 0 there is a die a balanced<00:09:47.230> database<00:09:47.650> and<00:09:47.860> a<00:09:47.890> diet<00:09:48.070> controller 00:09:48.540 --> 00:09:48.550 align:start position:0% balanced database and a diet controller 00:09:48.550 --> 00:09:52.910 align:start position:0% balanced database and a diet controller and<00:09:49.390> so<00:09:49.810> that<00:09:50.590> version<00:09:51.040> 0<00:09:51.370> is<00:09:51.640> going<00:09:51.910> to<00:09:52.030> be 00:09:52.910 --> 00:09:52.920 align:start position:0% and so that version 0 is going to be 00:09:52.920 --> 00:09:55.200 align:start position:0% and so that version 0 is going to be happening<00:09:53.920> tonight<00:09:54.130> so<00:09:54.640> we're<00:09:54.790> having<00:09:54.940> a 00:09:55.200 --> 00:09:55.210 align:start position:0% happening tonight so we're having a 00:09:55.210 --> 00:09:58.620 align:start position:0% happening tonight so we're having a second<00:09:56.200> of<00:09:56.290> our<00:09:56.380> maker<00:09:56.620> meetup<00:09:57.130> and<00:09:58.030> a<00:09:58.270> deploy 00:09:58.620 --> 00:09:58.630 align:start position:0% second of our maker meetup and a deploy 00:09:58.630 --> 00:10:02.210 align:start position:0% second of our maker meetup and a deploy party<00:09:59.190> it's<00:10:00.190> going<00:10:00.430> to<00:10:00.550> be<00:10:00.640> a<00:10:00.670> king's<00:10:01.090> arm<00:10:01.450> pub 00:10:02.210 --> 00:10:02.220 align:start position:0% party it's going to be a king's arm pub 00:10:02.220 --> 00:10:06.090 align:start position:0% party it's going to be a king's arm pub but<00:10:03.220> we're<00:10:03.310> going<00:10:03.460> to<00:10:03.550> meet<00:10:04.440> outside<00:10:05.440> here<00:10:06.010> at 00:10:06.090 --> 00:10:06.100 align:start position:0% but we're going to meet outside here at 00:10:06.100 --> 00:10:08.100 align:start position:0% but we're going to meet outside here at 4:15<00:10:06.640> and<00:10:06.670> then<00:10:06.940> go<00:10:07.090> over<00:10:07.210> there<00:10:07.420> for<00:10:07.660> 30<00:10:07.840> so 00:10:08.100 --> 00:10:08.110 align:start position:0% 4:15 and then go over there for 30 so 00:10:08.110 --> 00:10:09.810 align:start position:0% 4:15 and then go over there for 30 so you're<00:10:08.410> all<00:10:08.530> welcome<00:10:08.710> to<00:10:08.830> join<00:10:08.950> us<00:10:09.280> we're 00:10:09.810 --> 00:10:09.820 align:start position:0% you're all welcome to join us we're 00:10:09.820 --> 00:10:12.030 align:start position:0% you're all welcome to join us we're going<00:10:10.030> to<00:10:10.150> deploy<00:10:10.510> the<00:10:11.140> MK<00:10:11.440> our<00:10:11.590> controller 00:10:12.030 --> 00:10:12.040 align:start position:0% going to deploy the MK our controller 00:10:12.040 --> 00:10:14.880 align:start position:0% going to deploy the MK our controller and<00:10:12.400> balance<00:10:13.180> database<00:10:13.510> and<00:10:13.780> the<00:10:14.170> die<00:10:14.500> control 00:10:14.880 --> 00:10:14.890 align:start position:0% and balance database and the die control 00:10:14.890 --> 00:10:15.930 align:start position:0% and balance database and the die control arm<00:10:15.010> balance<00:10:15.310> database<00:10:15.580> and<00:10:15.760> all<00:10:15.820> the 00:10:15.930 --> 00:10:15.940 align:start position:0% arm balance database and all the 00:10:15.940 --> 00:10:17.760 align:start position:0% arm balance database and all the associated<00:10:16.450> and<00:10:17.200> all<00:10:17.320> the<00:10:17.410> other<00:10:17.530> stuff<00:10:17.740> you 00:10:17.760 --> 00:10:17.770 align:start position:0% associated and all the other stuff you 00:10:17.770 --> 00:10:19.440 align:start position:0% associated and all the other stuff you saw<00:10:17.980> on<00:10:18.070> the<00:10:18.100> first<00:10:18.190> version<00:10:18.490> there<00:10:19.150> there's 00:10:19.440 --> 00:10:19.450 align:start position:0% saw on the first version there there's 00:10:19.450 --> 00:10:21.210 align:start position:0% saw on the first version there there's not<00:10:19.660> actually<00:10:19.990> going<00:10:20.110> to<00:10:20.170> be<00:10:20.290> die<00:10:20.470> created 00:10:21.210 --> 00:10:21.220 align:start position:0% not actually going to be die created 00:10:21.220 --> 00:10:22.800 align:start position:0% not actually going to be die created unfortunately<00:10:21.880> but<00:10:22.030> you<00:10:22.210> can<00:10:22.360> start<00:10:22.600> writing 00:10:22.800 --> 00:10:22.810 align:start position:0% unfortunately but you can start writing 00:10:22.810 --> 00:10:25.320 align:start position:0% unfortunately but you can start writing your<00:10:22.930> contracts<00:10:23.440> as<00:10:23.590> if<00:10:23.710> it<00:10:23.860> is<00:10:24.070> created<00:10:24.430> and 00:10:25.320 --> 00:10:25.330 align:start position:0% your contracts as if it is created and 00:10:25.330 --> 00:10:28.680 align:start position:0% your contracts as if it is created and the<00:10:25.540> MK<00:10:25.870> r<00:10:26.760> is<00:10:27.760> going<00:10:28.000> to<00:10:28.090> issue<00:10:28.240> and<00:10:28.570> made 00:10:28.680 --> 00:10:28.690 align:start position:0% the MK r is going to issue and made 00:10:28.690 --> 00:10:30.680 align:start position:0% the MK r is going to issue and made liquid<00:10:29.050> so<00:10:29.260> anyone<00:10:29.860> here<00:10:30.100> that<00:10:30.250> might<00:10:30.460> have 00:10:30.680 --> 00:10:30.690 align:start position:0% liquid so anyone here that might have 00:10:30.690 --> 00:10:32.640 align:start position:0% liquid so anyone here that might have participated<00:10:31.690> on<00:10:31.870> a<00:10:31.930> private<00:10:32.110> sales<00:10:32.470> you 00:10:32.640 --> 00:10:32.650 align:start position:0% participated on a private sales you 00:10:32.650 --> 00:10:35.430 align:start position:0% participated on a private sales you actually<00:10:32.980> have<00:10:33.130> your<00:10:33.250> asset<00:10:33.640> is<00:10:34.230> liquid<00:10:35.230> on 00:10:35.430 --> 00:10:35.440 align:start position:0% actually have your asset is liquid on 00:10:35.440 --> 00:10:38.580 align:start position:0% actually have your asset is liquid on Shane<00:10:35.740> tonight<00:10:36.900> so<00:10:37.900> that's<00:10:38.320> the<00:10:38.380> end<00:10:38.470> of<00:10:38.530> my 00:10:38.580 --> 00:10:38.590 align:start position:0% Shane tonight so that's the end of my 00:10:38.590 --> 00:10:40.140 align:start position:0% Shane tonight so that's the end of my talk<00:10:38.830> I<00:10:38.980> hope<00:10:39.130> to<00:10:39.280> see<00:10:39.550> you<00:10:39.640> guys<00:10:39.790> at<00:10:40.030> the 00:10:40.140 --> 00:10:40.150 align:start position:0% talk I hope to see you guys at the 00:10:40.150 --> 00:10:41.370 align:start position:0% talk I hope to see you guys at the Meetup<00:10:40.450> and<00:10:40.600> thank<00:10:40.870> you<00:10:40.960> so<00:10:41.110> much<00:10:41.230> for 00:10:41.370 --> 00:10:41.380 align:start position:0% Meetup and thank you so much for 00:10:41.380 --> 00:10:46.290 align:start position:0% Meetup and thank you so much for listening 00:10:46.290 --> 00:10:46.300 align:start position:0% 00:10:46.300 --> 00:10:48.360 align:start position:0% you