WEBVTT Kind: captions Language: en 00:00:05.130 --> 00:00:08.450 align:start position:0% we're<00:00:05.940> gonna<00:00:06.120> talk<00:00:06.480> about<00:00:06.510> dolls<00:00:06.930> today<00:00:07.110> a<00:00:07.980> few 00:00:08.450 --> 00:00:08.460 align:start position:0% we're gonna talk about dolls today a few 00:00:08.460 --> 00:00:09.890 align:start position:0% we're gonna talk about dolls today a few years<00:00:08.670> ago<00:00:08.910> if<00:00:09.060> we<00:00:09.600> were<00:00:09.660> talking<00:00:09.870> about 00:00:09.890 --> 00:00:09.900 align:start position:0% years ago if we were talking about 00:00:09.900 --> 00:00:11.600 align:start position:0% years ago if we were talking about Dallas<00:00:10.200> people<00:00:10.530> were<00:00:10.620> talking<00:00:10.800> that<00:00:11.100> we're 00:00:11.600 --> 00:00:11.610 align:start position:0% Dallas people were talking that we're 00:00:11.610 --> 00:00:13.160 align:start position:0% Dallas people were talking that we're thinking<00:00:11.940> that<00:00:12.059> you<00:00:12.210> know<00:00:12.330> you<00:00:12.990> would<00:00:13.110> just 00:00:13.160 --> 00:00:13.170 align:start position:0% thinking that you know you would just 00:00:13.170 --> 00:00:15.140 align:start position:0% thinking that you know you would just put<00:00:13.440> money<00:00:13.559> into<00:00:13.740> them<00:00:13.980> and<00:00:14.129> your<00:00:14.789> money<00:00:15.000> would 00:00:15.140 --> 00:00:15.150 align:start position:0% put money into them and your money would 00:00:15.150 --> 00:00:17.300 align:start position:0% put money into them and your money would Michael<00:00:15.600> a<00:00:15.780> disappear<00:00:16.260> because<00:00:16.800> of<00:00:16.920> the<00:00:17.100> whole 00:00:17.300 --> 00:00:17.310 align:start position:0% Michael a disappear because of the whole 00:00:17.310 --> 00:00:20.210 align:start position:0% Michael a disappear because of the whole the<00:00:17.640> doll<00:00:17.789> hack<00:00:18.410> the<00:00:19.410> back<00:00:19.560> in<00:00:19.680> the<00:00:19.740> day<00:00:19.890> you 00:00:20.210 --> 00:00:20.220 align:start position:0% the doll hack the back in the day you 00:00:20.220 --> 00:00:22.490 align:start position:0% the doll hack the back in the day you know<00:00:20.250> we<00:00:20.520> were<00:00:20.640> like<00:00:20.850> well<00:00:21.179> that's<00:00:22.050> right<00:00:22.320> not 00:00:22.490 --> 00:00:22.500 align:start position:0% know we were like well that's right not 00:00:22.500 --> 00:00:24.589 align:start position:0% know we were like well that's right not inherently<00:00:23.039> bad<00:00:23.099> so<00:00:23.580> let's<00:00:23.760> just<00:00:24.240> focus<00:00:24.359> on 00:00:24.589 --> 00:00:24.599 align:start position:0% inherently bad so let's just focus on 00:00:24.599 --> 00:00:26.720 align:start position:0% inherently bad so let's just focus on them<00:00:24.750> that's<00:00:24.929> actually<00:00:25.289> making<00:00:25.470> great<00:00:25.949> the 00:00:26.720 --> 00:00:26.730 align:start position:0% them that's actually making great the 00:00:26.730 --> 00:00:28.400 align:start position:0% them that's actually making great the Dow<00:00:26.849> was<00:00:27.060> unfortunate<00:00:27.660> but<00:00:27.810> I<00:00:27.869> also<00:00:28.019> put<00:00:28.289> this 00:00:28.400 --> 00:00:28.410 align:start position:0% Dow was unfortunate but I also put this 00:00:28.410 --> 00:00:30.079 align:start position:0% Dow was unfortunate but I also put this page<00:00:28.560> forward<00:00:28.830> by<00:00:29.400> a<00:00:29.429> lot<00:00:29.670> in<00:00:29.820> terms<00:00:30.000> of 00:00:30.079 --> 00:00:30.089 align:start position:0% page forward by a lot in terms of 00:00:30.089 --> 00:00:33.500 align:start position:0% page forward by a lot in terms of security<00:00:30.410> and<00:00:31.410> so<00:00:32.060> that's<00:00:33.060> what<00:00:33.150> we're<00:00:33.270> doing 00:00:33.500 --> 00:00:33.510 align:start position:0% security and so that's what we're doing 00:00:33.510 --> 00:00:35.300 align:start position:0% security and so that's what we're doing at<00:00:33.600> Eragon<00:00:34.080> we've<00:00:34.290> been<00:00:34.440> doing<00:00:34.620> dolls<00:00:34.830> since 00:00:35.300 --> 00:00:35.310 align:start position:0% at Eragon we've been doing dolls since 00:00:35.310 --> 00:00:39.319 align:start position:0% at Eragon we've been doing dolls since November<00:00:35.970> 2016<00:00:37.460> focusing<00:00:38.460> on<00:00:38.579> making<00:00:39.030> them 00:00:39.319 --> 00:00:39.329 align:start position:0% November 2016 focusing on making them 00:00:39.329 --> 00:00:40.910 align:start position:0% November 2016 focusing on making them very<00:00:39.480> high<00:00:39.629> quality<00:00:39.690> and<00:00:40.200> very<00:00:40.260> easy<00:00:40.559> to<00:00:40.649> use 00:00:40.910 --> 00:00:40.920 align:start position:0% very high quality and very easy to use 00:00:40.920 --> 00:00:43.639 align:start position:0% very high quality and very easy to use for<00:00:40.950> anywhere<00:00:41.789> in<00:00:41.879> the<00:00:41.940> world<00:00:42.090> so<00:00:42.410> what<00:00:43.410> I<00:00:43.440> want 00:00:43.639 --> 00:00:43.649 align:start position:0% for anywhere in the world so what I want 00:00:43.649 --> 00:00:45.740 align:start position:0% for anywhere in the world so what I want to<00:00:43.680> talk<00:00:43.890> about<00:00:44.100> today<00:00:44.489> is<00:00:44.940> how<00:00:45.390> we<00:00:45.420> can<00:00:45.719> use 00:00:45.740 --> 00:00:45.750 align:start position:0% to talk about today is how we can use 00:00:45.750 --> 00:00:48.080 align:start position:0% to talk about today is how we can use those<00:00:46.289> to<00:00:46.739> make<00:00:46.770> decentralized<00:00:47.579> protocols 00:00:48.080 --> 00:00:48.090 align:start position:0% those to make decentralized protocols 00:00:48.090 --> 00:00:51.080 align:start position:0% those to make decentralized protocols actually<00:00:48.629> be<00:00:48.809> centralized<00:00:49.350> so<00:00:50.039> I<00:00:50.609> don't<00:00:51.030> know 00:00:51.080 --> 00:00:51.090 align:start position:0% actually be centralized so I don't know 00:00:51.090 --> 00:00:52.819 align:start position:0% actually be centralized so I don't know if<00:00:51.149> I<00:00:51.239> Cohen<00:00:51.570> this<00:00:51.780> term<00:00:51.989> but<00:00:52.289> I<00:00:52.469> like<00:00:52.500> to<00:00:52.800> use 00:00:52.819 --> 00:00:52.829 align:start position:0% if I Cohen this term but I like to use 00:00:52.829 --> 00:00:56.060 align:start position:0% if I Cohen this term but I like to use the<00:00:53.100> term<00:00:53.280> CFI<00:00:54.059> so<00:00:54.750> probably<00:00:55.020> you<00:00:55.649> all<00:00:55.770> know 00:00:56.060 --> 00:00:56.070 align:start position:0% the term CFI so probably you all know 00:00:56.070 --> 00:00:59.060 align:start position:0% the term CFI so probably you all know defy<00:00:56.609> the<00:00:56.940> centralized<00:00:57.359> finance<00:00:58.070> actually 00:00:59.060 --> 00:00:59.070 align:start position:0% defy the centralized finance actually 00:00:59.070 --> 00:01:01.130 align:start position:0% defy the centralized finance actually and<00:00:59.550> there's<00:00:59.699> no<00:00:59.879> term<00:01:00.149> called<00:01:00.449> C<00:01:00.719> Phi<00:01:00.899> which 00:01:01.130 --> 00:01:01.140 align:start position:0% and there's no term called C Phi which 00:01:01.140 --> 00:01:04.130 align:start position:0% and there's no term called C Phi which is<00:01:01.609> centralized<00:01:02.609> finance<00:01:02.969> and<00:01:03.239> a<00:01:03.570> lot<00:01:03.929> of<00:01:03.960> this 00:01:04.130 --> 00:01:04.140 align:start position:0% is centralized finance and a lot of this 00:01:04.140 --> 00:01:05.479 align:start position:0% is centralized finance and a lot of this defect<00:01:04.530> that<00:01:04.559> we<00:01:04.680> talked<00:01:04.830> about<00:01:04.949> today<00:01:05.190> it's 00:01:05.479 --> 00:01:05.489 align:start position:0% defect that we talked about today it's 00:01:05.489 --> 00:01:08.000 align:start position:0% defect that we talked about today it's actually<00:01:05.610> c5<00:01:06.300> which<00:01:07.290> I<00:01:07.530> mean<00:01:07.650> I<00:01:07.740> would<00:01:07.890> talk 00:01:08.000 --> 00:01:08.010 align:start position:0% actually c5 which I mean I would talk 00:01:08.010 --> 00:01:10.520 align:start position:0% actually c5 which I mean I would talk about<00:01:08.040> that<00:01:08.370> later<00:01:08.550> but<00:01:08.910> I<00:01:08.940> think<00:01:09.180> it's<00:01:09.530> it's 00:01:10.520 --> 00:01:10.530 align:start position:0% about that later but I think it's it's 00:01:10.530 --> 00:01:12.710 align:start position:0% about that later but I think it's it's okay<00:01:10.890> sometimes<00:01:11.130> to<00:01:11.909> start<00:01:12.119> centralized<00:01:12.509> and 00:01:12.710 --> 00:01:12.720 align:start position:0% okay sometimes to start centralized and 00:01:12.720 --> 00:01:14.060 align:start position:0% okay sometimes to start centralized and then<00:01:12.810> decentralized<00:01:13.470> but<00:01:13.619> we<00:01:13.710> have<00:01:13.890> to<00:01:14.009> be 00:01:14.060 --> 00:01:14.070 align:start position:0% then decentralized but we have to be 00:01:14.070 --> 00:01:15.620 align:start position:0% then decentralized but we have to be conscious<00:01:14.250> about<00:01:14.460> it<00:01:14.640> and<00:01:15.090> make<00:01:15.360> a<00:01:15.390> conscious 00:01:15.620 --> 00:01:15.630 align:start position:0% conscious about it and make a conscious 00:01:15.630 --> 00:01:18.649 align:start position:0% conscious about it and make a conscious effort<00:01:15.900> to<00:01:16.200> actually<00:01:16.590> get<00:01:17.360> for<00:01:18.360> it<00:01:18.479> to<00:01:18.570> be 00:01:18.649 --> 00:01:18.659 align:start position:0% effort to actually get for it to be 00:01:18.659 --> 00:01:20.600 align:start position:0% effort to actually get for it to be decentralized<00:01:19.049> and<00:01:19.590> so<00:01:19.799> I<00:01:20.070> want<00:01:20.460> to<00:01:20.520> talk 00:01:20.600 --> 00:01:20.610 align:start position:0% decentralized and so I want to talk 00:01:20.610 --> 00:01:22.969 align:start position:0% decentralized and so I want to talk about<00:01:20.810> some<00:01:21.810> things<00:01:22.020> today<00:01:22.170> starting<00:01:22.799> with 00:01:22.969 --> 00:01:22.979 align:start position:0% about some things today starting with 00:01:22.979 --> 00:01:24.890 align:start position:0% about some things today starting with you<00:01:23.189> know<00:01:23.280> smart<00:01:23.520> contracts<00:01:24.060> the<00:01:24.689> best 00:01:24.890 --> 00:01:24.900 align:start position:0% you know smart contracts the best 00:01:24.900 --> 00:01:27.050 align:start position:0% you know smart contracts the best invention<00:01:25.409> since<00:01:25.650> ramen<00:01:26.130> I<00:01:26.310> think<00:01:26.790> we<00:01:26.909> will 00:01:27.050 --> 00:01:27.060 align:start position:0% invention since ramen I think we will 00:01:27.060 --> 00:01:30.350 align:start position:0% invention since ramen I think we will all<00:01:27.270> agree<00:01:28.280> immutable<00:01:29.280> smart<00:01:29.549> contracts<00:01:30.180> are 00:01:30.350 --> 00:01:30.360 align:start position:0% all agree immutable smart contracts are 00:01:30.360 --> 00:01:32.630 align:start position:0% all agree immutable smart contracts are the<00:01:30.720> default<00:01:31.049> state<00:01:31.380> of<00:01:31.590> smart<00:01:32.070> contracts 00:01:32.630 --> 00:01:32.640 align:start position:0% the default state of smart contracts 00:01:32.640 --> 00:01:34.429 align:start position:0% the default state of smart contracts unleashed<00:01:33.060> on<00:01:33.270> blockchains<00:01:33.990> like<00:01:34.140> aetherium 00:01:34.429 --> 00:01:34.439 align:start position:0% unleashed on blockchains like aetherium 00:01:34.439 --> 00:01:37.609 align:start position:0% unleashed on blockchains like aetherium and<00:01:34.890> so<00:01:35.130> they<00:01:35.729> are<00:01:35.790> fully<00:01:35.970> trackless<00:01:36.540> so<00:01:37.110> call 00:01:37.609 --> 00:01:37.619 align:start position:0% and so they are fully trackless so call 00:01:37.619 --> 00:01:39.859 align:start position:0% and so they are fully trackless so call this<00:01:37.710> law<00:01:37.920> kind<00:01:38.430> of<00:01:38.520> thing<00:01:38.729> what<00:01:39.600> you've<00:01:39.750> read 00:01:39.859 --> 00:01:39.869 align:start position:0% this law kind of thing what you've read 00:01:39.869 --> 00:01:41.840 align:start position:0% this law kind of thing what you've read into<00:01:40.079> a<00:01:40.140> smart<00:01:40.380> contract<00:01:40.829> is<00:01:40.979> basically<00:01:41.460> what 00:01:41.840 --> 00:01:41.850 align:start position:0% into a smart contract is basically what 00:01:41.850 --> 00:01:44.389 align:start position:0% into a smart contract is basically what happens<00:01:42.439> and<00:01:43.439> but<00:01:43.829> the<00:01:43.920> issue<00:01:44.100> is<00:01:44.189> they<00:01:44.310> are 00:01:44.389 --> 00:01:44.399 align:start position:0% happens and but the issue is they are 00:01:44.399 --> 00:01:46.490 align:start position:0% happens and but the issue is they are not<00:01:44.490> upgradeable<00:01:45.060> and<00:01:45.299> so<00:01:45.540> we<00:01:45.810> learn<00:01:46.020> the<00:01:46.229> hard 00:01:46.490 --> 00:01:46.500 align:start position:0% not upgradeable and so we learn the hard 00:01:46.500 --> 00:01:50.120 align:start position:0% not upgradeable and so we learn the hard way<00:01:47.270> we<00:01:48.270> are<00:01:48.450> kind<00:01:49.229> of<00:01:49.290> you<00:01:49.500> know<00:01:49.590> some<00:01:49.920> some 00:01:50.120 --> 00:01:50.130 align:start position:0% way we are kind of you know some some 00:01:50.130 --> 00:01:51.410 align:start position:0% way we are kind of you know some some other<00:01:50.310> issues<00:01:50.759> that<00:01:50.790> we<00:01:50.939> hide<00:01:51.060> the<00:01:51.180> theorem 00:01:51.410 --> 00:01:51.420 align:start position:0% other issues that we hide the theorem 00:01:51.420 --> 00:01:53.810 align:start position:0% other issues that we hide the theorem community<00:01:51.869> that<00:01:52.649> it<00:01:52.979> is<00:01:53.100> very<00:01:53.310> important<00:01:53.790> for 00:01:53.810 --> 00:01:53.820 align:start position:0% community that it is very important for 00:01:53.820 --> 00:01:55.550 align:start position:0% community that it is very important for smart<00:01:54.180> contracts<00:01:54.600> to<00:01:54.750> be<00:01:54.840> upgradable 00:01:55.550 --> 00:01:55.560 align:start position:0% smart contracts to be upgradable 00:01:55.560 --> 00:01:58.100 align:start position:0% smart contracts to be upgradable for<00:01:55.890> mainly<00:01:56.189> two<00:01:56.430> reasons<00:01:56.460> one<00:01:57.090> of<00:01:57.119> them<00:01:57.329> is<00:01:57.600> do 00:01:58.100 --> 00:01:58.110 align:start position:0% for mainly two reasons one of them is do 00:01:58.110 --> 00:01:59.990 align:start position:0% for mainly two reasons one of them is do you<00:01:58.170> want<00:01:58.320> to<00:01:58.409> be<00:01:58.500> able<00:01:58.560> to<00:01:58.710> fix<00:01:59.040> bugs<00:01:59.280> and<00:01:59.640> the 00:01:59.990 --> 00:02:00.000 align:start position:0% you want to be able to fix bugs and the 00:02:00.000 --> 00:02:01.219 align:start position:0% you want to be able to fix bugs and the other<00:02:00.119> one<00:02:00.270> is<00:02:00.390> you<00:02:00.479> want<00:02:00.540> to<00:02:00.689> be<00:02:00.780> able<00:02:00.869> to<00:02:00.990> add 00:02:01.219 --> 00:02:01.229 align:start position:0% other one is you want to be able to add 00:02:01.229 --> 00:02:03.050 align:start position:0% other one is you want to be able to add features<00:02:01.530> it<00:02:01.979> is<00:02:02.070> very<00:02:02.310> hard<00:02:02.520> to<00:02:02.610> compete 00:02:03.050 --> 00:02:03.060 align:start position:0% features it is very hard to compete 00:02:03.060 --> 00:02:05.929 align:start position:0% features it is very hard to compete against<00:02:03.539> other<00:02:04.320> systems<00:02:05.130> that<00:02:05.250> are<00:02:05.399> gradable 00:02:05.929 --> 00:02:05.939 align:start position:0% against other systems that are gradable 00:02:05.939 --> 00:02:08.180 align:start position:0% against other systems that are gradable enhanced<00:02:06.600> over<00:02:06.869> time<00:02:07.110> if<00:02:07.500> we<00:02:07.649> don't<00:02:07.890> have<00:02:08.160> that 00:02:08.180 --> 00:02:08.190 align:start position:0% enhanced over time if we don't have that 00:02:08.190 --> 00:02:10.820 align:start position:0% enhanced over time if we don't have that capability<00:02:08.550> or<00:02:09.270> if<00:02:10.020> the<00:02:10.140> only<00:02:10.259> way<00:02:10.380> to<00:02:10.500> upgrade 00:02:10.820 --> 00:02:10.830 align:start position:0% capability or if the only way to upgrade 00:02:10.830 --> 00:02:14.030 align:start position:0% capability or if the only way to upgrade something<00:02:11.340> is<00:02:11.910> via<00:02:12.240> Forks<00:02:12.660> we<00:02:13.110> which<00:02:13.650> require 00:02:14.030 --> 00:02:14.040 align:start position:0% something is via Forks we which require 00:02:14.040 --> 00:02:15.800 align:start position:0% something is via Forks we which require a<00:02:14.070> lot<00:02:14.400> of<00:02:14.520> human<00:02:14.820> coordination<00:02:15.450> so<00:02:15.540> each<00:02:15.630> time 00:02:15.800 --> 00:02:15.810 align:start position:0% a lot of human coordination so each time 00:02:15.810 --> 00:02:17.330 align:start position:0% a lot of human coordination so each time you<00:02:15.990> want<00:02:16.080> to<00:02:16.200> add<00:02:16.620> something<00:02:16.950> you<00:02:17.190> have<00:02:17.310> to 00:02:17.330 --> 00:02:17.340 align:start position:0% you want to add something you have to 00:02:17.340 --> 00:02:18.110 align:start position:0% you want to add something you have to tell<00:02:17.550> your<00:02:17.670> whole 00:02:18.110 --> 00:02:18.120 align:start position:0% tell your whole 00:02:18.120 --> 00:02:20.089 align:start position:0% tell your whole network<00:02:18.750> yeah<00:02:19.110> I<00:02:19.140> deployed<00:02:19.440> a<00:02:19.470> new<00:02:19.620> contract 00:02:20.089 --> 00:02:20.099 align:start position:0% network yeah I deployed a new contract 00:02:20.099 --> 00:02:23.089 align:start position:0% network yeah I deployed a new contract is<00:02:20.310> the<00:02:20.430> new<00:02:20.580> address<00:02:20.760> and<00:02:21.500> you<00:02:22.500> know<00:02:22.530> they 00:02:23.089 --> 00:02:23.099 align:start position:0% is the new address and you know they 00:02:23.099 --> 00:02:24.380 align:start position:0% is the new address and you know they have<00:02:23.250> to<00:02:23.400> like<00:02:23.550> review<00:02:23.700> it<00:02:23.879> again<00:02:24.060> and<00:02:24.269> it's 00:02:24.380 --> 00:02:24.390 align:start position:0% have to like review it again and it's 00:02:24.390 --> 00:02:25.790 align:start position:0% have to like review it again and it's really<00:02:24.569> they<00:02:24.750> have<00:02:24.900> to<00:02:24.989> reach<00:02:25.140> consensus<00:02:25.680> say 00:02:25.790 --> 00:02:25.800 align:start position:0% really they have to reach consensus say 00:02:25.800 --> 00:02:28.220 align:start position:0% really they have to reach consensus say again<00:02:26.220> that<00:02:26.790> that<00:02:27.000> new<00:02:27.269> contract<00:02:27.690> is<00:02:27.989> the<00:02:28.080> one 00:02:28.220 --> 00:02:28.230 align:start position:0% again that that new contract is the one 00:02:28.230 --> 00:02:30.080 align:start position:0% again that that new contract is the one that<00:02:28.379> this<00:02:28.500> was<00:02:28.680> actually<00:02:28.800> use<00:02:29.190> and<00:02:29.640> you<00:02:29.910> lose 00:02:30.080 --> 00:02:30.090 align:start position:0% that this was actually use and you lose 00:02:30.090 --> 00:02:32.449 align:start position:0% that this was actually use and you lose a<00:02:30.120> lot<00:02:30.660> of<00:02:30.780> network<00:02:31.290> effects<00:02:31.590> as<00:02:31.680> well<00:02:31.860> if<00:02:32.370> you 00:02:32.449 --> 00:02:32.459 align:start position:0% a lot of network effects as well if you 00:02:32.459 --> 00:02:34.850 align:start position:0% a lot of network effects as well if you want<00:02:32.640> to<00:02:32.700> fork<00:02:32.940> every<00:02:33.390> time<00:02:33.629> that<00:02:34.019> you<00:02:34.260> want<00:02:34.739> to 00:02:34.850 --> 00:02:34.860 align:start position:0% want to fork every time that you want to 00:02:34.860 --> 00:02:37.100 align:start position:0% want to fork every time that you want to upgrade<00:02:35.069> a<00:02:35.250> contract<00:02:35.790> that<00:02:36.480> may<00:02:36.660> just<00:02:36.840> break 00:02:37.100 --> 00:02:37.110 align:start position:0% upgrade a contract that may just break 00:02:37.110 --> 00:02:39.380 align:start position:0% upgrade a contract that may just break for<00:02:37.590> example<00:02:38.010> like<00:02:38.160> you<00:02:38.190> know<00:02:38.280> defy<00:02:38.940> protocols 00:02:39.380 --> 00:02:39.390 align:start position:0% for example like you know defy protocols 00:02:39.390 --> 00:02:40.640 align:start position:0% for example like you know defy protocols because<00:02:39.660> they<00:02:39.750> just<00:02:39.900> kind<00:02:40.080> of<00:02:40.140> be<00:02:40.290> like<00:02:40.319> yeah 00:02:40.640 --> 00:02:40.650 align:start position:0% because they just kind of be like yeah 00:02:40.650 --> 00:02:42.890 align:start position:0% because they just kind of be like yeah this<00:02:40.769> is<00:02:40.890> v2<00:02:41.160> and<00:02:41.580> you<00:02:41.910> have<00:02:42.060> to<00:02:42.209> move<00:02:42.360> all<00:02:42.599> your 00:02:42.890 --> 00:02:42.900 align:start position:0% this is v2 and you have to move all your 00:02:42.900 --> 00:02:44.570 align:start position:0% this is v2 and you have to move all your fans<00:02:43.170> from<00:02:43.349> one<00:02:43.530> place<00:02:43.709> to<00:02:43.739> the<00:02:43.890> other<00:02:43.980> imagine 00:02:44.570 --> 00:02:44.580 align:start position:0% fans from one place to the other imagine 00:02:44.580 --> 00:02:46.400 align:start position:0% fans from one place to the other imagine like<00:02:44.730> all<00:02:44.970> of<00:02:45.420> that<00:02:45.629> if<00:02:45.810> people<00:02:45.959> were<00:02:46.230> like 00:02:46.400 --> 00:02:46.410 align:start position:0% like all of that if people were like 00:02:46.410 --> 00:02:48.949 align:start position:0% like all of that if people were like closing<00:02:46.650> CD<00:02:46.980> piece<00:02:47.190> in<00:02:48.060> like<00:02:48.120> you<00:02:48.480> know<00:02:48.599> one 00:02:48.949 --> 00:02:48.959 align:start position:0% closing CD piece in like you know one 00:02:48.959 --> 00:02:51.949 align:start position:0% closing CD piece in like you know one system<00:02:49.410> a<00:02:49.530> bring<00:02:49.709> the<00:02:50.040> other<00:02:50.160> one<00:02:50.840> that<00:02:51.840> would 00:02:51.949 --> 00:02:51.959 align:start position:0% system a bring the other one that would 00:02:51.959 --> 00:02:54.289 align:start position:0% system a bring the other one that would just<00:02:52.110> break<00:02:52.560> everything<00:02:52.739> then<00:02:53.220> on<00:02:54.030> the<00:02:54.150> other 00:02:54.289 --> 00:02:54.299 align:start position:0% just break everything then on the other 00:02:54.299 --> 00:02:56.449 align:start position:0% just break everything then on the other hand<00:02:54.540> we<00:02:55.200> have<00:02:55.349> the<00:02:55.500> centrally<00:02:55.980> govern<00:02:56.280> the 00:02:56.449 --> 00:02:56.459 align:start position:0% hand we have the centrally govern the 00:02:56.459 --> 00:02:58.339 align:start position:0% hand we have the centrally govern the smart<00:02:56.700> contracts<00:02:57.299> that's<00:02:57.900> easy<00:02:58.319> for 00:02:58.339 --> 00:02:58.349 align:start position:0% smart contracts that's easy for 00:02:58.349 --> 00:02:59.660 align:start position:0% smart contracts that's easy for developers<00:02:58.590> right<00:02:59.160> you<00:02:59.280> have<00:02:59.400> a<00:02:59.430> smart 00:02:59.660 --> 00:02:59.670 align:start position:0% developers right you have a smart 00:02:59.670 --> 00:03:01.910 align:start position:0% developers right you have a smart contract<00:02:59.819> and<00:03:00.299> then<00:03:00.480> just<00:03:00.780> upgrade<00:03:01.590> it<00:03:01.739> and 00:03:01.910 --> 00:03:01.920 align:start position:0% contract and then just upgrade it and 00:03:01.920 --> 00:03:04.130 align:start position:0% contract and then just upgrade it and that's<00:03:02.610> it<00:03:02.760> but<00:03:03.390> it<00:03:03.540> is<00:03:03.629> not<00:03:03.720> really<00:03:03.840> trash 00:03:04.130 --> 00:03:04.140 align:start position:0% that's it but it is not really trash 00:03:04.140 --> 00:03:07.430 align:start position:0% that's it but it is not really trash this<00:03:04.849> because<00:03:05.849> it's<00:03:06.510> custodial<00:03:06.989> so<00:03:07.170> you<00:03:07.230> have 00:03:07.430 --> 00:03:07.440 align:start position:0% this because it's custodial so you have 00:03:07.440 --> 00:03:09.650 align:start position:0% this because it's custodial so you have fans<00:03:07.709> and<00:03:08.069> then<00:03:08.250> you<00:03:08.370> have<00:03:08.660> unilateral 00:03:09.650 --> 00:03:09.660 align:start position:0% fans and then you have unilateral 00:03:09.660 --> 00:03:11.270 align:start position:0% fans and then you have unilateral permission<00:03:10.260> to<00:03:10.379> upgrade<00:03:10.799> the<00:03:10.890> smart<00:03:11.129> contract 00:03:11.270 --> 00:03:11.280 align:start position:0% permission to upgrade the smart contract 00:03:11.280 --> 00:03:14.240 align:start position:0% permission to upgrade the smart contract what<00:03:12.239> is<00:03:12.360> the<00:03:12.480> difference<00:03:12.959> with<00:03:13.500> just<00:03:13.890> having 00:03:14.240 --> 00:03:14.250 align:start position:0% what is the difference with just having 00:03:14.250 --> 00:03:16.220 align:start position:0% what is the difference with just having a<00:03:14.489> centralized<00:03:15.239> server<00:03:15.510> in<00:03:15.720> which<00:03:15.750> you<00:03:16.049> can 00:03:16.220 --> 00:03:16.230 align:start position:0% a centralized server in which you can 00:03:16.230 --> 00:03:18.860 align:start position:0% a centralized server in which you can like<00:03:16.560> push<00:03:16.769> code<00:03:17.040> to<00:03:17.280> and<00:03:17.579> so<00:03:18.180> I<00:03:18.420> like<00:03:18.599> to<00:03:18.720> use 00:03:18.860 --> 00:03:18.870 align:start position:0% like push code to and so I like to use 00:03:18.870 --> 00:03:22.520 align:start position:0% like push code to and so I like to use the<00:03:19.079> the<00:03:19.500> ether<00:03:19.799> to<00:03:20.010> ramp<00:03:20.629> analogy<00:03:21.629> here<00:03:21.900> I<00:03:22.109> I 00:03:22.520 --> 00:03:22.530 align:start position:0% the the ether to ramp analogy here I I 00:03:22.530 --> 00:03:24.020 align:start position:0% the the ether to ramp analogy here I I made<00:03:23.130> this<00:03:23.190> kind<00:03:23.340> of<00:03:23.430> picture<00:03:23.730> with<00:03:23.880> like<00:03:24.000> a 00:03:24.020 --> 00:03:24.030 align:start position:0% made this kind of picture with like a 00:03:24.030 --> 00:03:25.520 align:start position:0% made this kind of picture with like a Stephens<00:03:24.450> logo<00:03:24.720> and<00:03:24.870> and<00:03:25.019> tram<00:03:25.230> because<00:03:25.470> I 00:03:25.520 --> 00:03:25.530 align:start position:0% Stephens logo and and tram because I 00:03:25.530 --> 00:03:27.650 align:start position:0% Stephens logo and and tram because I think<00:03:25.590> this<00:03:25.829> is<00:03:25.920> the<00:03:26.010> is<00:03:26.459> the<00:03:26.579> worst<00:03:26.819> from<00:03:27.420> both 00:03:27.650 --> 00:03:27.660 align:start position:0% think this is the is the worst from both 00:03:27.660 --> 00:03:30.949 align:start position:0% think this is the is the worst from both worlds<00:03:27.840> you<00:03:28.230> have<00:03:28.560> like<00:03:28.799> a<00:03:29.730> theorem<00:03:30.630> which<00:03:30.720> is 00:03:30.949 --> 00:03:30.959 align:start position:0% worlds you have like a theorem which is 00:03:30.959 --> 00:03:33.379 align:start position:0% worlds you have like a theorem which is you<00:03:31.470> know<00:03:31.560> like<00:03:31.709> kind<00:03:32.250> of<00:03:32.310> clunky<00:03:32.519> to<00:03:32.760> use<00:03:32.970> and 00:03:33.379 --> 00:03:33.389 align:start position:0% you know like kind of clunky to use and 00:03:33.389 --> 00:03:35.180 align:start position:0% you know like kind of clunky to use and it<00:03:33.450> slow<00:03:33.720> and<00:03:34.079> all<00:03:34.170> of<00:03:34.260> those<00:03:34.380> things<00:03:34.620> and<00:03:35.010> then 00:03:35.180 --> 00:03:35.190 align:start position:0% it slow and all of those things and then 00:03:35.190 --> 00:03:37.220 align:start position:0% it slow and all of those things and then it<00:03:35.280> costs<00:03:35.459> money<00:03:35.760> to<00:03:35.880> like<00:03:36.269> click<00:03:36.510> buttons<00:03:36.930> as 00:03:37.220 --> 00:03:37.230 align:start position:0% it costs money to like click buttons as 00:03:37.230 --> 00:03:40.099 align:start position:0% it costs money to like click buttons as one<00:03:37.590> team<00:03:37.799> member<00:03:37.920> from<00:03:38.130> our<00:03:38.280> team<00:03:38.549> said<00:03:39.109> but 00:03:40.099 --> 00:03:40.109 align:start position:0% one team member from our team said but 00:03:40.109 --> 00:03:41.539 align:start position:0% one team member from our team said but then<00:03:40.200> also<00:03:40.410> you<00:03:40.560> have<00:03:40.709> the<00:03:40.829> worst<00:03:41.010> things<00:03:41.280> from 00:03:41.539 --> 00:03:41.549 align:start position:0% then also you have the worst things from 00:03:41.549 --> 00:03:43.819 align:start position:0% then also you have the worst things from like<00:03:41.730> you<00:03:42.060> know<00:03:42.180> it<00:03:42.480> means<00:03:42.750> centralized<00:03:43.260> so 00:03:43.819 --> 00:03:43.829 align:start position:0% like you know it means centralized so 00:03:43.829 --> 00:03:45.259 align:start position:0% like you know it means centralized so there<00:03:43.980> is<00:03:44.040> one<00:03:44.280> person<00:03:44.519> one<00:03:44.819> sort<00:03:45.060> of<00:03:45.150> like 00:03:45.259 --> 00:03:45.269 align:start position:0% there is one person one sort of like 00:03:45.269 --> 00:03:46.970 align:start position:0% there is one person one sort of like dictator<00:03:45.630> or<00:03:45.780> entity<00:03:46.319> that<00:03:46.349> can<00:03:46.620> just<00:03:46.799> push 00:03:46.970 --> 00:03:46.980 align:start position:0% dictator or entity that can just push 00:03:46.980 --> 00:03:49.009 align:start position:0% dictator or entity that can just push changes<00:03:47.340> right<00:03:47.579> so<00:03:48.150> I<00:03:48.180> think<00:03:48.329> centrally 00:03:49.009 --> 00:03:49.019 align:start position:0% changes right so I think centrally 00:03:49.019 --> 00:03:50.449 align:start position:0% changes right so I think centrally governed<00:03:49.380> the<00:03:49.440> smart<00:03:49.650> contracts<00:03:50.190> are<00:03:50.310> use<00:03:50.430> a 00:03:50.449 --> 00:03:50.459 align:start position:0% governed the smart contracts are use a 00:03:50.459 --> 00:03:52.000 align:start position:0% governed the smart contracts are use a very<00:03:50.819> bad<00:03:51.030> idea 00:03:52.000 --> 00:03:52.010 align:start position:0% very bad idea 00:03:52.010 --> 00:03:54.920 align:start position:0% very bad idea so<00:03:53.010> that's<00:03:53.190> why<00:03:53.370> the<00:03:53.430> data<00:03:53.910> Trump<00:03:54.299> I<00:03:54.480> hope<00:03:54.720> you 00:03:54.920 --> 00:03:54.930 align:start position:0% so that's why the data Trump I hope you 00:03:54.930 --> 00:03:56.839 align:start position:0% so that's why the data Trump I hope you you<00:03:55.530> don't<00:03:55.680> have<00:03:55.799> nightmares<00:03:56.040> about<00:03:56.519> the 00:03:56.839 --> 00:03:56.849 align:start position:0% you don't have nightmares about the 00:03:56.849 --> 00:03:59.360 align:start position:0% you don't have nightmares about the ether<00:03:56.970> Trump<00:03:57.530> and<00:03:58.530> things<00:03:58.769> young<00:03:58.919> for<00:03:59.190> coining 00:03:59.360 --> 00:03:59.370 align:start position:0% ether Trump and things young for coining 00:03:59.370 --> 00:04:02.030 align:start position:0% ether Trump and things young for coining the<00:03:59.489> term<00:03:59.579> it'll<00:03:59.970> Trump<00:04:00.359> I<00:04:00.630> love<00:04:01.049> it 00:04:02.030 --> 00:04:02.040 align:start position:0% the term it'll Trump I love it 00:04:02.040 --> 00:04:05.000 align:start position:0% the term it'll Trump I love it and<00:04:02.489> now<00:04:02.730> well<00:04:03.690> what<00:04:04.019> I<00:04:04.079> wanna<00:04:04.260> propose<00:04:04.560> is<00:04:04.950> a 00:04:05.000 --> 00:04:05.010 align:start position:0% and now well what I wanna propose is a 00:04:05.010 --> 00:04:06.349 align:start position:0% and now well what I wanna propose is a different<00:04:05.489> thing<00:04:05.639> which<00:04:05.819> is<00:04:05.940> a<00:04:05.970> different 00:04:06.349 --> 00:04:06.359 align:start position:0% different thing which is a different 00:04:06.359 --> 00:04:07.879 align:start position:0% different thing which is a different combination<00:04:06.510> that<00:04:07.049> I<00:04:07.079> think<00:04:07.349> takes<00:04:07.530> the<00:04:07.709> best 00:04:07.879 --> 00:04:07.889 align:start position:0% combination that I think takes the best 00:04:07.889 --> 00:04:09.890 align:start position:0% combination that I think takes the best from<00:04:08.340> both<00:04:08.519> worlds<00:04:08.730> and<00:04:09.120> that<00:04:09.389> is<00:04:09.510> community 00:04:09.890 --> 00:04:09.900 align:start position:0% from both worlds and that is community 00:04:09.900 --> 00:04:12.500 align:start position:0% from both worlds and that is community governance<00:04:10.290> smart<00:04:10.769> contracts<00:04:11.370> and<00:04:11.819> so<00:04:12.389> the 00:04:12.500 --> 00:04:12.510 align:start position:0% governance smart contracts and so the 00:04:12.510 --> 00:04:14.839 align:start position:0% governance smart contracts and so the idea<00:04:12.780> for<00:04:13.410> traditional<00:04:14.010> contracts<00:04:14.639> is<00:04:14.790> that 00:04:14.839 --> 00:04:14.849 align:start position:0% idea for traditional contracts is that 00:04:14.849 --> 00:04:16.969 align:start position:0% idea for traditional contracts is that they<00:04:15.209> are<00:04:15.329> upgradeable<00:04:15.930> you<00:04:16.349> can<00:04:16.530> enhance 00:04:16.969 --> 00:04:16.979 align:start position:0% they are upgradeable you can enhance 00:04:16.979 --> 00:04:18.979 align:start position:0% they are upgradeable you can enhance them<00:04:17.310> over<00:04:17.609> time<00:04:17.880> you<00:04:18.450> can<00:04:18.599> enhance<00:04:18.720> your 00:04:18.979 --> 00:04:18.989 align:start position:0% them over time you can enhance your 00:04:18.989 --> 00:04:21.140 align:start position:0% them over time you can enhance your protocol<00:04:19.500> you<00:04:19.620> can<00:04:19.650> enhance<00:04:19.889> your<00:04:20.160> apps<00:04:20.430> but 00:04:21.140 --> 00:04:21.150 align:start position:0% protocol you can enhance your apps but 00:04:21.150 --> 00:04:23.089 align:start position:0% protocol you can enhance your apps but at<00:04:21.239> the<00:04:21.299> same<00:04:21.479> time<00:04:21.810> there's<00:04:22.470> a<00:04:22.560> community 00:04:23.089 --> 00:04:23.099 align:start position:0% at the same time there's a community 00:04:23.099 --> 00:04:24.830 align:start position:0% at the same time there's a community there's<00:04:23.340> a<00:04:23.400> governance<00:04:23.789> process<00:04:24.150> a<00:04:24.570> little 00:04:24.830 --> 00:04:24.840 align:start position:0% there's a governance process a little 00:04:24.840 --> 00:04:28.159 align:start position:0% there's a governance process a little governance<00:04:25.620> process<00:04:26.039> that<00:04:26.880> ensures<00:04:27.000> that<00:04:27.630> you 00:04:28.159 --> 00:04:28.169 align:start position:0% governance process that ensures that you 00:04:28.169 --> 00:04:30.890 align:start position:0% governance process that ensures that you cannot<00:04:28.650> push<00:04:28.890> an<00:04:29.039> update<00:04:29.300> that<00:04:30.300> you<00:04:30.630> know<00:04:30.719> get 00:04:30.890 --> 00:04:30.900 align:start position:0% cannot push an update that you know get 00:04:30.900 --> 00:04:31.999 align:start position:0% cannot push an update that you know get through<00:04:31.050> people's<00:04:31.409> money 00:04:31.999 --> 00:04:32.009 align:start position:0% through people's money 00:04:32.009 --> 00:04:34.670 align:start position:0% through people's money get<00:04:32.129> away<00:04:32.219> with<00:04:32.490> it<00:04:32.639> right<00:04:32.669> and<00:04:33.270> so<00:04:33.869> I<00:04:34.110> think 00:04:34.670 --> 00:04:34.680 align:start position:0% get away with it right and so I think 00:04:34.680 --> 00:04:36.920 align:start position:0% get away with it right and so I think this<00:04:34.919> is<00:04:35.069> very<00:04:35.249> very<00:04:35.819> important<00:04:36.210> to<00:04:36.240> to<00:04:36.749> work 00:04:36.920 --> 00:04:36.930 align:start position:0% this is very very important to to work 00:04:36.930 --> 00:04:39.589 align:start position:0% this is very very important to to work on<00:04:37.169> and<00:04:37.439> the<00:04:38.249> issue<00:04:38.430> here<00:04:38.729> is<00:04:38.849> of<00:04:39.029> course<00:04:39.300> you 00:04:39.589 --> 00:04:39.599 align:start position:0% on and the issue here is of course you 00:04:39.599 --> 00:04:40.760 align:start position:0% on and the issue here is of course you have<00:04:39.749> to<00:04:39.869> figure<00:04:40.020> out<00:04:40.199> your<00:04:40.349> governance 00:04:40.760 --> 00:04:40.770 align:start position:0% have to figure out your governance 00:04:40.770 --> 00:04:43.219 align:start position:0% have to figure out your governance structure<00:04:41.129> you<00:04:41.879> have<00:04:41.999> to<00:04:42.149> think<00:04:42.360> alright<00:04:42.779> if<00:04:43.020> I 00:04:43.219 --> 00:04:43.229 align:start position:0% structure you have to think alright if I 00:04:43.229 --> 00:04:45.409 align:start position:0% structure you have to think alright if I am<00:04:43.469> gonna<00:04:43.710> put<00:04:44.039> my<00:04:44.580> smart<00:04:44.939> contracts 00:04:45.409 --> 00:04:45.419 align:start position:0% am gonna put my smart contracts 00:04:45.419 --> 00:04:48.529 align:start position:0% am gonna put my smart contracts governance<00:04:45.930> behind<00:04:46.649> a<00:04:46.889> Dow<00:04:47.129> or<00:04:47.430> some<00:04:48.270> sort<00:04:48.449> of 00:04:48.529 --> 00:04:48.539 align:start position:0% governance behind a Dow or some sort of 00:04:48.539 --> 00:04:50.480 align:start position:0% governance behind a Dow or some sort of like<00:04:48.659> community<00:04:49.080> governance<00:04:49.349> what<00:04:50.249> is<00:04:50.369> the 00:04:50.480 --> 00:04:50.490 align:start position:0% like community governance what is the 00:04:50.490 --> 00:04:52.100 align:start position:0% like community governance what is the governance<00:04:50.849> structure<00:04:51.389> that<00:04:51.419> fits<00:04:51.689> the<00:04:51.899> best 00:04:52.100 --> 00:04:52.110 align:start position:0% governance structure that fits the best 00:04:52.110 --> 00:04:54.649 align:start position:0% governance structure that fits the best and<00:04:52.559> so<00:04:53.129> we've<00:04:53.639> been<00:04:53.729> working<00:04:53.789> with<00:04:54.149> projects 00:04:54.649 --> 00:04:54.659 align:start position:0% and so we've been working with projects 00:04:54.659 --> 00:04:56.920 align:start position:0% and so we've been working with projects for<00:04:55.349> a<00:04:55.379> long<00:04:55.469> time<00:04:55.680> to<00:04:55.830> figure<00:04:55.979> this<00:04:56.069> out<00:04:56.339> and 00:04:56.920 --> 00:04:56.930 align:start position:0% for a long time to figure this out and 00:04:56.930 --> 00:04:58.820 align:start position:0% for a long time to figure this out and there<00:04:57.930> are<00:04:57.960> a<00:04:58.050> bunch<00:04:58.199> of<00:04:58.409> different<00:04:58.469> things 00:04:58.820 --> 00:04:58.830 align:start position:0% there are a bunch of different things 00:04:58.830 --> 00:05:01.070 align:start position:0% there are a bunch of different things you<00:04:59.069> can<00:04:59.189> do<00:04:59.339> the<00:05:00.089> cool<00:05:00.240> thing<00:05:00.419> about<00:05:00.479> Aragon 00:05:01.070 --> 00:05:01.080 align:start position:0% you can do the cool thing about Aragon 00:05:01.080 --> 00:05:02.929 align:start position:0% you can do the cool thing about Aragon and<00:05:01.259> the<00:05:01.619> way<00:05:01.710> we<00:05:01.830> thought<00:05:01.979> about<00:05:02.039> it<00:05:02.399> is<00:05:02.639> that 00:05:02.929 --> 00:05:02.939 align:start position:0% and the way we thought about it is that 00:05:02.939 --> 00:05:05.540 align:start position:0% and the way we thought about it is that it's<00:05:03.599> very<00:05:03.749> modular<00:05:04.080> so<00:05:04.830> instead<00:05:05.219> of<00:05:05.279> saying 00:05:05.540 --> 00:05:05.550 align:start position:0% it's very modular so instead of saying 00:05:05.550 --> 00:05:08.360 align:start position:0% it's very modular so instead of saying you<00:05:05.729> know<00:05:05.969> we<00:05:06.809> have<00:05:07.080> like<00:05:07.409> the<00:05:07.620> key<00:05:07.830> ingredient 00:05:08.360 --> 00:05:08.370 align:start position:0% you know we have like the key ingredient 00:05:08.370 --> 00:05:09.589 align:start position:0% you know we have like the key ingredient like<00:05:08.520> the<00:05:08.639> Kissel's<00:05:08.999> and<00:05:09.270> there's<00:05:09.419> gonna 00:05:09.589 --> 00:05:09.599 align:start position:0% like the Kissel's and there's gonna 00:05:09.599 --> 00:05:11.510 align:start position:0% like the Kissel's and there's gonna solve<00:05:09.930> all<00:05:10.169> your<00:05:10.259> governance<00:05:10.919> problems<00:05:11.339> and 00:05:11.510 --> 00:05:11.520 align:start position:0% solve all your governance problems and 00:05:11.520 --> 00:05:13.820 align:start position:0% solve all your governance problems and we're<00:05:11.610> gonna<00:05:11.729> use<00:05:11.969> focus<00:05:12.300> on<00:05:12.449> that<00:05:12.649> instead<00:05:13.649> of 00:05:13.820 --> 00:05:13.830 align:start position:0% we're gonna use focus on that instead of 00:05:13.830 --> 00:05:16.219 align:start position:0% we're gonna use focus on that instead of saying<00:05:13.979> that<00:05:14.249> we<00:05:14.879> were<00:05:14.999> like<00:05:15.240> well<00:05:15.539> we<00:05:16.080> don't 00:05:16.219 --> 00:05:16.229 align:start position:0% saying that we were like well we don't 00:05:16.229 --> 00:05:18.769 align:start position:0% saying that we were like well we don't know<00:05:16.409> how<00:05:16.789> organizations<00:05:17.789> of<00:05:18.059> the<00:05:18.089> future<00:05:18.479> are 00:05:18.769 --> 00:05:18.779 align:start position:0% know how organizations of the future are 00:05:18.779 --> 00:05:21.260 align:start position:0% know how organizations of the future are gonna<00:05:18.960> look<00:05:19.110> like<00:05:19.289> we<00:05:20.069> don't<00:05:20.159> know<00:05:20.430> you<00:05:21.149> know 00:05:21.260 --> 00:05:21.270 align:start position:0% gonna look like we don't know you know 00:05:21.270 --> 00:05:22.610 align:start position:0% gonna look like we don't know you know in<00:05:21.389> the<00:05:21.449> future<00:05:21.599> which<00:05:21.960> kind<00:05:22.169> of<00:05:22.199> Dallas 00:05:22.610 --> 00:05:22.620 align:start position:0% in the future which kind of Dallas 00:05:22.620 --> 00:05:25.489 align:start position:0% in the future which kind of Dallas people<00:05:22.949> will<00:05:23.520> want<00:05:23.729> to<00:05:23.759> deploy<00:05:24.229> we<00:05:25.229> think 00:05:25.489 --> 00:05:25.499 align:start position:0% people will want to deploy we think 00:05:25.499 --> 00:05:28.339 align:start position:0% people will want to deploy we think every<00:05:25.949> protocol<00:05:26.399> has<00:05:26.759> or<00:05:27.120> each<00:05:27.629> community 00:05:28.339 --> 00:05:28.349 align:start position:0% every protocol has or each community 00:05:28.349 --> 00:05:30.799 align:start position:0% every protocol has or each community even<00:05:28.499> has<00:05:29.099> their<00:05:29.550> own<00:05:29.669> needs<00:05:29.999> and<00:05:30.149> so<00:05:30.659> let's 00:05:30.799 --> 00:05:30.809 align:start position:0% even has their own needs and so let's 00:05:30.809 --> 00:05:32.510 align:start position:0% even has their own needs and so let's build<00:05:30.930> this<00:05:31.110> very<00:05:31.259> model<00:05:31.680> framework<00:05:32.189> in<00:05:32.459> which 00:05:32.510 --> 00:05:32.520 align:start position:0% build this very model framework in which 00:05:32.520 --> 00:05:34.579 align:start position:0% build this very model framework in which you<00:05:32.879> can<00:05:33.029> basically<00:05:33.240> do<00:05:33.599> everything<00:05:34.409> that<00:05:34.499> is 00:05:34.579 --> 00:05:34.589 align:start position:0% you can basically do everything that is 00:05:34.589 --> 00:05:38.360 align:start position:0% you can basically do everything that is here<00:05:34.830> and<00:05:35.069> much<00:05:35.219> more<00:05:35.399> so<00:05:36.680> they're<00:05:37.680> two<00:05:37.889> axes 00:05:38.360 --> 00:05:38.370 align:start position:0% here and much more so they're two axes 00:05:38.370 --> 00:05:41.089 align:start position:0% here and much more so they're two axes in<00:05:38.610> this<00:05:38.909> in<00:05:39.330> this<00:05:39.479> curve<00:05:39.779> map<00:05:39.990> here<00:05:40.409> and<00:05:40.499> so 00:05:41.089 --> 00:05:41.099 align:start position:0% in this in this curve map here and so 00:05:41.099 --> 00:05:43.219 align:start position:0% in this in this curve map here and so one<00:05:41.249> of<00:05:41.279> them<00:05:41.520> is<00:05:41.550> speed<00:05:42.089> so<00:05:42.719> the<00:05:42.839> speed<00:05:43.110> at 00:05:43.219 --> 00:05:43.229 align:start position:0% one of them is speed so the speed at 00:05:43.229 --> 00:05:45.260 align:start position:0% one of them is speed so the speed at which<00:05:43.259> developers<00:05:44.219> core<00:05:44.550> developers<00:05:45.089> can 00:05:45.260 --> 00:05:45.270 align:start position:0% which developers core developers can 00:05:45.270 --> 00:05:47.509 align:start position:0% which developers core developers can implement<00:05:45.629> changes<00:05:46.080> to<00:05:46.800> the<00:05:46.919> protocol<00:05:47.309> and 00:05:47.509 --> 00:05:47.519 align:start position:0% implement changes to the protocol and 00:05:47.519 --> 00:05:49.159 align:start position:0% implement changes to the protocol and there's<00:05:48.120> the<00:05:48.269> other<00:05:48.300> one<00:05:48.539> which<00:05:48.749> is<00:05:48.779> strapless 00:05:49.159 --> 00:05:49.169 align:start position:0% there's the other one which is strapless 00:05:49.169 --> 00:05:51.769 align:start position:0% there's the other one which is strapless Ness<00:05:49.529> which<00:05:49.919> is<00:05:50.129> how<00:05:50.580> trustless<00:05:51.149> is<00:05:51.360> actually 00:05:51.769 --> 00:05:51.779 align:start position:0% Ness which is how trustless is actually 00:05:51.779 --> 00:05:53.779 align:start position:0% Ness which is how trustless is actually this<00:05:51.930> protocol<00:05:52.379> there<00:05:52.949> is<00:05:53.039> from<00:05:53.219> what<00:05:53.430> trusses 00:05:53.779 --> 00:05:53.789 align:start position:0% this protocol there is from what trusses 00:05:53.789 --> 00:05:55.999 align:start position:0% this protocol there is from what trusses Ness<00:05:53.999> is<00:05:54.209> important<00:05:54.779> it's<00:05:55.050> not<00:05:55.229> because<00:05:55.709> I 00:05:55.999 --> 00:05:56.009 align:start position:0% Ness is important it's not because I 00:05:56.009 --> 00:05:59.570 align:start position:0% Ness is important it's not because I like<00:05:56.699> visualization<00:05:57.449> which<00:05:57.599> I<00:05:57.779> also<00:05:57.930> do<00:05:58.580> it's 00:05:59.570 --> 00:05:59.580 align:start position:0% like visualization which I also do it's 00:05:59.580 --> 00:06:01.759 align:start position:0% like visualization which I also do it's more<00:05:59.879> because<00:06:00.089> if<00:06:00.719> he's<00:06:00.899> not<00:06:00.930> trustless<00:06:01.469> again 00:06:01.759 --> 00:06:01.769 align:start position:0% more because if he's not trustless again 00:06:01.769 --> 00:06:03.290 align:start position:0% more because if he's not trustless again like<00:06:02.009> if<00:06:02.370> you<00:06:02.519> just<00:06:02.610> have<00:06:02.819> like<00:06:02.849> a<00:06:03.059> protocol 00:06:03.290 --> 00:06:03.300 align:start position:0% like if you just have like a protocol 00:06:03.300 --> 00:06:05.299 align:start position:0% like if you just have like a protocol that<00:06:03.449> is<00:06:03.629> custodial<00:06:04.139> you<00:06:04.709> may<00:06:04.830> have<00:06:05.009> a<00:06:05.039> lot<00:06:05.279> of 00:06:05.299 --> 00:06:05.309 align:start position:0% that is custodial you may have a lot of 00:06:05.309 --> 00:06:07.730 align:start position:0% that is custodial you may have a lot of issues<00:06:05.459> from<00:06:06.180> not<00:06:06.689> having<00:06:06.719> trust<00:06:07.349> from<00:06:07.620> your 00:06:07.730 --> 00:06:07.740 align:start position:0% issues from not having trust from your 00:06:07.740 --> 00:06:09.409 align:start position:0% issues from not having trust from your users<00:06:08.129> because<00:06:08.339> you<00:06:08.610> can<00:06:08.759> use<00:06:08.939> with<00:06:09.149> rather 00:06:09.409 --> 00:06:09.419 align:start position:0% users because you can use with rather 00:06:09.419 --> 00:06:12.529 align:start position:0% users because you can use with rather fans<00:06:09.749> or<00:06:10.110> you<00:06:10.860> know<00:06:10.979> maliciously<00:06:11.430> in<00:06:12.089> to<00:06:12.300> like 00:06:12.529 --> 00:06:12.539 align:start position:0% fans or you know maliciously in to like 00:06:12.539 --> 00:06:14.629 align:start position:0% fans or you know maliciously in to like intervene<00:06:13.050> in<00:06:13.169> their<00:06:13.259> apps<00:06:13.469> and<00:06:13.830> the<00:06:14.309> working 00:06:14.629 --> 00:06:14.639 align:start position:0% intervene in their apps and the working 00:06:14.639 --> 00:06:16.369 align:start position:0% intervene in their apps and the working systems<00:06:15.029> or<00:06:15.569> even<00:06:15.930> because<00:06:16.139> you<00:06:16.229> may<00:06:16.349> have 00:06:16.369 --> 00:06:16.379 align:start position:0% systems or even because you may have 00:06:16.379 --> 00:06:19.939 align:start position:0% systems or even because you may have legal<00:06:16.919> legal<00:06:17.430> issues<00:06:17.729> like<00:06:17.969> I<00:06:18.120> love<00:06:18.599> this<00:06:18.949> see 00:06:19.939 --> 00:06:19.949 align:start position:0% legal legal issues like I love this see 00:06:19.949 --> 00:06:22.070 align:start position:0% legal legal issues like I love this see five<00:06:20.159> projects<00:06:20.550> today<00:06:20.819> I<00:06:20.849> think<00:06:21.089> they<00:06:21.809> may 00:06:22.070 --> 00:06:22.080 align:start position:0% five projects today I think they may 00:06:22.080 --> 00:06:23.839 align:start position:0% five projects today I think they may face<00:06:22.409> some<00:06:22.620> kind<00:06:22.800> of<00:06:22.860> legal<00:06:23.099> issue<00:06:23.309> if<00:06:23.669> they 00:06:23.839 --> 00:06:23.849 align:start position:0% face some kind of legal issue if they 00:06:23.849 --> 00:06:25.579 align:start position:0% face some kind of legal issue if they are<00:06:23.939> used<00:06:24.199> basically<00:06:25.199> the<00:06:25.259> ones<00:06:25.409> controlling 00:06:25.579 --> 00:06:25.589 align:start position:0% are used basically the ones controlling 00:06:25.589 --> 00:06:27.110 align:start position:0% are used basically the ones controlling the<00:06:25.919> whole<00:06:26.039> protocol<00:06:26.430> in<00:06:26.669> the<00:06:26.759> background 00:06:27.110 --> 00:06:27.120 align:start position:0% the whole protocol in the background 00:06:27.120 --> 00:06:29.329 align:start position:0% the whole protocol in the background right<00:06:27.240> so<00:06:27.919> because<00:06:28.919> they<00:06:29.009> are<00:06:29.129> and<00:06:29.249> they're 00:06:29.329 --> 00:06:29.339 align:start position:0% right so because they are and they're 00:06:29.339 --> 00:06:30.559 align:start position:0% right so because they are and they're supposed<00:06:29.519> to<00:06:29.610> be<00:06:29.699> licensed<00:06:29.969> revised<00:06:30.209> but<00:06:30.419> they 00:06:30.559 --> 00:06:30.569 align:start position:0% supposed to be licensed revised but they 00:06:30.569 --> 00:06:32.269 align:start position:0% supposed to be licensed revised but they are<00:06:30.659> not<00:06:30.779> in<00:06:30.899> practice<00:06:31.050> so<00:06:31.800> then<00:06:31.949> it<00:06:32.039> is<00:06:32.069> very 00:06:32.269 --> 00:06:32.279 align:start position:0% are not in practice so then it is very 00:06:32.279 --> 00:06:34.850 align:start position:0% are not in practice so then it is very important<00:06:32.809> the<00:06:33.809> boot<00:06:33.959> restlessness<00:06:34.409> first 00:06:34.850 --> 00:06:34.860 align:start position:0% important the boot restlessness first 00:06:34.860 --> 00:06:37.129 align:start position:0% important the boot restlessness first where<00:06:35.249> we're<00:06:35.490> building<00:06:35.610> transit<00:06:36.300> systems<00:06:36.659> if 00:06:37.129 --> 00:06:37.139 align:start position:0% where we're building transit systems if 00:06:37.139 --> 00:06:38.389 align:start position:0% where we're building transit systems if you<00:06:37.199> don't<00:06:37.439> want<00:06:37.589> to<00:06:37.680> trust<00:06:37.830> the<00:06:37.919> system<00:06:38.099> you 00:06:38.389 --> 00:06:38.399 align:start position:0% you don't want to trust the system you 00:06:38.399 --> 00:06:41.029 align:start position:0% you don't want to trust the system you can<00:06:38.430> always<00:06:38.879> use<00:06:39.089> MongoDB<00:06:39.749> and<00:06:40.289> use<00:06:40.740> go 00:06:41.029 --> 00:06:41.039 align:start position:0% can always use MongoDB and use go 00:06:41.039 --> 00:06:42.499 align:start position:0% can always use MongoDB and use go decentralized<00:06:41.550> route<00:06:41.729> so<00:06:42.209> now<00:06:42.329> I<00:06:42.360> have 00:06:42.499 --> 00:06:42.509 align:start position:0% decentralized route so now I have 00:06:42.509 --> 00:06:45.250 align:start position:0% decentralized route so now I have amazing<00:06:42.870> news<00:06:43.079> experience 00:06:45.250 --> 00:06:45.260 align:start position:0% amazing news experience 00:06:45.260 --> 00:06:47.230 align:start position:0% amazing news experience the<00:06:45.440> centralized<00:06:45.920> for<00:06:46.160> me<00:06:46.280> has<00:06:46.490> like<00:06:46.730> very 00:06:47.230 --> 00:06:47.240 align:start position:0% the centralized for me has like very 00:06:47.240 --> 00:06:49.540 align:start position:0% the centralized for me has like very very<00:06:47.510> high<00:06:48.050> speed<00:06:48.380> but<00:06:48.920> it's<00:06:49.040> not<00:06:49.160> trackless 00:06:49.540 --> 00:06:49.550 align:start position:0% very high speed but it's not trackless 00:06:49.550 --> 00:06:51.430 align:start position:0% very high speed but it's not trackless at<00:06:49.670> all<00:06:49.790> then<00:06:50.690> you<00:06:50.780> have<00:06:50.960> something<00:06:51.200> like<00:06:51.320> a 00:06:51.430 --> 00:06:51.440 align:start position:0% at all then you have something like a 00:06:51.440 --> 00:06:55.060 align:start position:0% at all then you have something like a technical<00:06:51.860> council<00:06:52.280> so<00:06:53.030> there<00:06:53.510> is<00:06:53.660> a<00:06:54.260> a 00:06:55.060 --> 00:06:55.070 align:start position:0% technical council so there is a a 00:06:55.070 --> 00:06:57.520 align:start position:0% technical council so there is a a project<00:06:55.490> at<00:06:56.240> V<00:06:56.480> fiber<00:06:56.720> or<00:06:56.900> actually<00:06:57.320> called 00:06:57.520 --> 00:06:57.530 align:start position:0% project at V fiber or actually called 00:06:57.530 --> 00:07:00.640 align:start position:0% project at V fiber or actually called melon<00:06:58.040> protocol<00:06:58.460> and<00:06:58.700> so<00:06:59.420> the<00:07:00.200> way<00:07:00.380> they 00:07:00.640 --> 00:07:00.650 align:start position:0% melon protocol and so the way they 00:07:00.650 --> 00:07:03.130 align:start position:0% melon protocol and so the way they structure<00:07:01.010> their<00:07:01.220> governance<00:07:01.670> they<00:07:02.540> wanted 00:07:03.130 --> 00:07:03.140 align:start position:0% structure their governance they wanted 00:07:03.140 --> 00:07:05.200 align:start position:0% structure their governance they wanted to<00:07:03.260> do<00:07:03.350> something<00:07:03.800> in<00:07:03.950> which<00:07:04.250> token<00:07:04.820> holders 00:07:05.200 --> 00:07:05.210 align:start position:0% to do something in which token holders 00:07:05.210 --> 00:07:07.870 align:start position:0% to do something in which token holders have<00:07:05.450> the<00:07:05.600> ultimate<00:07:05.900> world<00:07:06.230> but<00:07:06.920> also<00:07:07.070> there 00:07:07.870 --> 00:07:07.880 align:start position:0% have the ultimate world but also there 00:07:07.880 --> 00:07:10.540 align:start position:0% have the ultimate world but also there was<00:07:08.090> you<00:07:08.600> know<00:07:08.630> fairly<00:07:09.260> fairly<00:07:09.950> fast<00:07:10.190> to<00:07:10.370> push 00:07:10.540 --> 00:07:10.550 align:start position:0% was you know fairly fairly fast to push 00:07:10.550 --> 00:07:13.330 align:start position:0% was you know fairly fairly fast to push updates<00:07:10.730> right<00:07:11.180> and<00:07:11.360> so<00:07:11.990> today<00:07:12.440> it<00:07:12.830> is<00:07:12.890> very 00:07:13.330 --> 00:07:13.340 align:start position:0% updates right and so today it is very 00:07:13.340 --> 00:07:16.420 align:start position:0% updates right and so today it is very hard<00:07:13.670> to<00:07:13.880> so<00:07:14.810> token<00:07:15.710> holders<00:07:16.100> of<00:07:16.310> your 00:07:16.420 --> 00:07:16.430 align:start position:0% hard to so token holders of your 00:07:16.430 --> 00:07:18.730 align:start position:0% hard to so token holders of your community<00:07:16.910> smart<00:07:17.720> contract<00:07:18.170> and<00:07:18.410> be<00:07:18.560> like 00:07:18.730 --> 00:07:18.740 align:start position:0% community smart contract and be like 00:07:18.740 --> 00:07:20.260 align:start position:0% community smart contract and be like well<00:07:18.950> do<00:07:19.100> you<00:07:19.160> want<00:07:19.340> to<00:07:19.400> approve<00:07:19.580> this<00:07:19.700> upgrade 00:07:20.260 --> 00:07:20.270 align:start position:0% well do you want to approve this upgrade 00:07:20.270 --> 00:07:21.670 align:start position:0% well do you want to approve this upgrade I<00:07:20.300> mean<00:07:20.660> that<00:07:20.780> a<00:07:20.810> crystal<00:07:21.140> of<00:07:21.230> coordination 00:07:21.670 --> 00:07:21.680 align:start position:0% I mean that a crystal of coordination 00:07:21.680 --> 00:07:23.260 align:start position:0% I mean that a crystal of coordination cost<00:07:22.040> and<00:07:22.310> stuff<00:07:22.460> like<00:07:22.580> that<00:07:22.730> and<00:07:22.940> there<00:07:23.150> is 00:07:23.260 --> 00:07:23.270 align:start position:0% cost and stuff like that and there is 00:07:23.270 --> 00:07:24.910 align:start position:0% cost and stuff like that and there is very<00:07:23.840> specific<00:07:23.960> knowledge<00:07:24.380> that<00:07:24.770> they<00:07:24.890> need 00:07:24.910 --> 00:07:24.920 align:start position:0% very specific knowledge that they need 00:07:24.920 --> 00:07:27.550 align:start position:0% very specific knowledge that they need to<00:07:25.100> have<00:07:25.310> on<00:07:25.610> solidity<00:07:26.120> and<00:07:26.510> yet<00:07:27.380> another 00:07:27.550 --> 00:07:27.560 align:start position:0% to have on solidity and yet another 00:07:27.560 --> 00:07:29.650 align:start position:0% to have on solidity and yet another protocol<00:07:27.950> design<00:07:28.280> instead<00:07:29.180> of<00:07:29.270> doing<00:07:29.510> that 00:07:29.650 --> 00:07:29.660 align:start position:0% protocol design instead of doing that 00:07:29.660 --> 00:07:32.110 align:start position:0% protocol design instead of doing that they<00:07:30.410> wanted<00:07:30.710> a<00:07:30.830> technical<00:07:31.190> council<00:07:31.580> so 00:07:32.110 --> 00:07:32.120 align:start position:0% they wanted a technical council so 00:07:32.120 --> 00:07:33.700 align:start position:0% they wanted a technical council so docking<00:07:32.420> holders<00:07:32.780> who<00:07:32.990> like<00:07:33.140> both<00:07:33.470> for<00:07:33.650> this 00:07:33.700 --> 00:07:33.710 align:start position:0% docking holders who like both for this 00:07:33.710 --> 00:07:35.470 align:start position:0% docking holders who like both for this council<00:07:33.920> and<00:07:34.310> then<00:07:34.670> this<00:07:34.820> council<00:07:35.210> would<00:07:35.330> take 00:07:35.470 --> 00:07:35.480 align:start position:0% council and then this council would take 00:07:35.480 --> 00:07:37.270 align:start position:0% council and then this council would take care<00:07:35.660> of<00:07:35.720> the<00:07:35.990> of<00:07:36.140> the<00:07:36.260> upgrades<00:07:36.710> afterwards 00:07:37.270 --> 00:07:37.280 align:start position:0% care of the of the upgrades afterwards 00:07:37.280 --> 00:07:39.640 align:start position:0% care of the of the upgrades afterwards and<00:07:37.610> so<00:07:38.120> for<00:07:38.300> me<00:07:38.420> that's<00:07:38.900> that's<00:07:39.320> not<00:07:39.500> like 00:07:39.640 --> 00:07:39.650 align:start position:0% and so for me that's that's not like 00:07:39.650 --> 00:07:41.110 align:start position:0% and so for me that's that's not like super<00:07:39.950> super<00:07:40.070> transness<00:07:40.550> that<00:07:40.760> I<00:07:40.790> think<00:07:41.060> is 00:07:41.110 --> 00:07:41.120 align:start position:0% super super transness that I think is 00:07:41.120 --> 00:07:43.690 align:start position:0% super super transness that I think is like<00:07:41.210> Travis<00:07:41.600> enough<00:07:41.840> and<00:07:42.500> also<00:07:43.130> guarantees<00:07:43.670> a 00:07:43.690 --> 00:07:43.700 align:start position:0% like Travis enough and also guarantees a 00:07:43.700 --> 00:07:45.340 align:start position:0% like Travis enough and also guarantees a very<00:07:44.060> high<00:07:44.240> speed<00:07:44.540> because<00:07:44.990> you<00:07:45.080> can<00:07:45.200> iterate 00:07:45.340 --> 00:07:45.350 align:start position:0% very high speed because you can iterate 00:07:45.350 --> 00:07:47.170 align:start position:0% very high speed because you can iterate very<00:07:45.560> fast<00:07:46.010> with<00:07:46.250> this<00:07:46.370> council<00:07:46.760> and<00:07:46.910> you<00:07:47.030> can 00:07:47.170 --> 00:07:47.180 align:start position:0% very fast with this council and you can 00:07:47.180 --> 00:07:48.820 align:start position:0% very fast with this council and you can ensure<00:07:47.540> that<00:07:47.570> these<00:07:47.900> people<00:07:48.110> actually<00:07:48.380> know 00:07:48.820 --> 00:07:48.830 align:start position:0% ensure that these people actually know 00:07:48.830 --> 00:07:49.930 align:start position:0% ensure that these people actually know what<00:07:49.010> they<00:07:49.130> are<00:07:49.190> talking<00:07:49.370> about<00:07:49.580> they<00:07:49.910> are 00:07:49.930 --> 00:07:49.940 align:start position:0% what they are talking about they are 00:07:49.940 --> 00:07:52.300 align:start position:0% what they are talking about they are experts<00:07:50.420> in<00:07:50.510> their<00:07:50.660> field<00:07:50.930> so<00:07:51.200> these<00:07:51.860> are<00:07:52.070> very 00:07:52.300 --> 00:07:52.310 align:start position:0% experts in their field so these are very 00:07:52.310 --> 00:07:55.240 align:start position:0% experts in their field so these are very very<00:07:52.370> example<00:07:52.760> of<00:07:52.970> how<00:07:53.570> a<00:07:53.840> protocol<00:07:54.380> went<00:07:55.040> from 00:07:55.240 --> 00:07:55.250 align:start position:0% very example of how a protocol went from 00:07:55.250 --> 00:07:57.400 align:start position:0% very example of how a protocol went from centralized<00:07:55.820> to<00:07:56.120> decentralized<00:07:56.410> using 00:07:57.400 --> 00:07:57.410 align:start position:0% centralized to decentralized using 00:07:57.410 --> 00:08:00.340 align:start position:0% centralized to decentralized using Aragon<00:07:57.860> and<00:07:58.010> our<00:07:58.370> tool<00:07:58.670> in<00:07:58.820> and<00:07:59.810> it's<00:08:00.140> a<00:08:00.200> very 00:08:00.340 --> 00:08:00.350 align:start position:0% Aragon and our tool in and it's a very 00:08:00.350 --> 00:08:02.140 align:start position:0% Aragon and our tool in and it's a very exciting<00:08:00.500> project<00:08:00.710> and<00:08:01.160> right<00:08:01.550> now<00:08:01.700> it's<00:08:02.000> been 00:08:02.140 --> 00:08:02.150 align:start position:0% exciting project and right now it's been 00:08:02.150 --> 00:08:04.510 align:start position:0% exciting project and right now it's been a<00:08:02.180> minute<00:08:02.390> for<00:08:02.720> for<00:08:03.140> a<00:08:03.170> few<00:08:03.440> months<00:08:03.920> in<00:08:04.190> terms 00:08:04.510 --> 00:08:04.520 align:start position:0% a minute for for a few months in terms 00:08:04.520 --> 00:08:05.920 align:start position:0% a minute for for a few months in terms of<00:08:04.760> the<00:08:04.880> the<00:08:05.030> governance<00:08:05.330> structure<00:08:05.600> that 00:08:05.920 --> 00:08:05.930 align:start position:0% of the the governance structure that 00:08:05.930 --> 00:08:07.840 align:start position:0% of the the governance structure that they<00:08:06.020> are<00:08:06.110> using<00:08:06.410> with<00:08:06.530> Aragon<00:08:06.800> and<00:08:07.100> I'm<00:08:07.580> super 00:08:07.840 --> 00:08:07.850 align:start position:0% they are using with Aragon and I'm super 00:08:07.850 --> 00:08:08.980 align:start position:0% they are using with Aragon and I'm super super<00:08:07.880> happy<00:08:08.060> that<00:08:08.420> it's<00:08:08.540> working<00:08:08.750> out<00:08:08.810> for 00:08:08.980 --> 00:08:08.990 align:start position:0% super happy that it's working out for 00:08:08.990 --> 00:08:11.080 align:start position:0% super happy that it's working out for them<00:08:09.130> they<00:08:10.130> you<00:08:10.190> have<00:08:10.370> other<00:08:10.550> models<00:08:10.820> for 00:08:11.080 --> 00:08:11.090 align:start position:0% them they you have other models for 00:08:11.090 --> 00:08:13.570 align:start position:0% them they you have other models for example<00:08:11.450> community<00:08:11.900> veto<00:08:12.110> so<00:08:12.920> here<00:08:13.220> you<00:08:13.400> may 00:08:13.570 --> 00:08:13.580 align:start position:0% example community veto so here you may 00:08:13.580 --> 00:08:16.840 align:start position:0% example community veto so here you may say<00:08:13.820> as<00:08:14.060> the<00:08:14.540> core<00:08:14.690> developer<00:08:15.260> I<00:08:15.610> still<00:08:16.610> want 00:08:16.840 --> 00:08:16.850 align:start position:0% say as the core developer I still want 00:08:16.850 --> 00:08:19.360 align:start position:0% say as the core developer I still want to<00:08:16.940> retain<00:08:17.240> the<00:08:17.390> power<00:08:17.600> to<00:08:18.050> put<00:08:18.230> upgrades<00:08:18.740> but 00:08:19.360 --> 00:08:19.370 align:start position:0% to retain the power to put upgrades but 00:08:19.370 --> 00:08:21.760 align:start position:0% to retain the power to put upgrades but I<00:08:19.430> want<00:08:19.670> to<00:08:19.730> give<00:08:19.850> my<00:08:20.000> community<00:08:20.600> like<00:08:21.020> 24 00:08:21.760 --> 00:08:21.770 align:start position:0% I want to give my community like 24 00:08:21.770 --> 00:08:23.740 align:start position:0% I want to give my community like 24 hours<00:08:22.070> for<00:08:22.610> eight<00:08:22.730> hours<00:08:22.760> whatever<00:08:23.300> time<00:08:23.630> you 00:08:23.740 --> 00:08:23.750 align:start position:0% hours for eight hours whatever time you 00:08:23.750 --> 00:08:25.930 align:start position:0% hours for eight hours whatever time you want<00:08:23.780> for<00:08:24.680> them<00:08:24.770> to<00:08:24.920> check<00:08:25.130> the<00:08:25.310> upgrade<00:08:25.760> and 00:08:25.930 --> 00:08:25.940 align:start position:0% want for them to check the upgrade and 00:08:25.940 --> 00:08:27.910 align:start position:0% want for them to check the upgrade and be<00:08:26.360> able<00:08:26.570> to<00:08:26.690> veto<00:08:26.900> it<00:08:27.080> if<00:08:27.350> you<00:08:27.620> choose<00:08:27.770> like 00:08:27.910 --> 00:08:27.920 align:start position:0% be able to veto it if you choose like 00:08:27.920 --> 00:08:29.710 align:start position:0% be able to veto it if you choose like out<00:08:28.100> Reyes<00:08:28.580> if<00:08:28.820> I'm<00:08:28.970> just<00:08:29.090> gonna<00:08:29.270> like<00:08:29.480> you 00:08:29.710 --> 00:08:29.720 align:start position:0% out Reyes if I'm just gonna like you 00:08:29.720 --> 00:08:31.000 align:start position:0% out Reyes if I'm just gonna like you know<00:08:29.750> steal<00:08:30.200> their<00:08:30.350> money<00:08:30.470> or<00:08:30.650> something<00:08:30.950> like 00:08:31.000 --> 00:08:31.010 align:start position:0% know steal their money or something like 00:08:31.010 --> 00:08:35.140 align:start position:0% know steal their money or something like that<00:08:31.360> so<00:08:32.360> with<00:08:32.900> this<00:08:33.490> you<00:08:34.490> may<00:08:34.760> have<00:08:35.000> this 00:08:35.140 --> 00:08:35.150 align:start position:0% that so with this you may have this 00:08:35.150 --> 00:08:38.020 align:start position:0% that so with this you may have this period<00:08:35.630> where<00:08:35.990> like<00:08:36.169> you<00:08:36.410> need<00:08:36.620> to<00:08:37.370> allow 00:08:38.020 --> 00:08:38.030 align:start position:0% period where like you need to allow 00:08:38.030 --> 00:08:40.150 align:start position:0% period where like you need to allow talking<00:08:38.330> holders<00:08:38.690> to<00:08:38.930> vote<00:08:39.110> no<00:08:39.470> to<00:08:40.040> your 00:08:40.150 --> 00:08:40.160 align:start position:0% talking holders to vote no to your 00:08:40.160 --> 00:08:43.180 align:start position:0% talking holders to vote no to your proposed<00:08:40.550> upgrade<00:08:40.790> so<00:08:41.780> it<00:08:42.110> is<00:08:42.229> not<00:08:42.410> that<00:08:42.620> fast 00:08:43.180 --> 00:08:43.190 align:start position:0% proposed upgrade so it is not that fast 00:08:43.190 --> 00:08:44.890 align:start position:0% proposed upgrade so it is not that fast but<00:08:43.610> it's<00:08:43.700> more<00:08:43.790> trash<00:08:44.030> this<00:08:44.180> right<00:08:44.390> because 00:08:44.890 --> 00:08:44.900 align:start position:0% but it's more trash this right because 00:08:44.900 --> 00:08:45.910 align:start position:0% but it's more trash this right because you<00:08:44.960> can<00:08:45.080> have<00:08:45.200> your<00:08:45.320> whole<00:08:45.470> community 00:08:45.910 --> 00:08:45.920 align:start position:0% you can have your whole community 00:08:45.920 --> 00:08:47.980 align:start position:0% you can have your whole community basically<00:08:46.190> stopped<00:08:46.610> updates<00:08:47.240> at<00:08:47.510> any<00:08:47.750> point 00:08:47.980 --> 00:08:47.990 align:start position:0% basically stopped updates at any point 00:08:47.990 --> 00:08:50.410 align:start position:0% basically stopped updates at any point in<00:08:48.080> time<00:08:48.110> so<00:08:49.100> that's<00:08:49.250> cool<00:08:49.370> when<00:08:50.150> you<00:08:50.240> have 00:08:50.410 --> 00:08:50.420 align:start position:0% in time so that's cool when you have 00:08:50.420 --> 00:08:52.150 align:start position:0% in time so that's cool when you have like<00:08:50.570> stuff<00:08:50.810> like<00:08:51.050> a<00:08:51.080> liquid<00:08:51.350> talking<00:08:51.950> occur 00:08:52.150 --> 00:08:52.160 align:start position:0% like stuff like a liquid talking occur 00:08:52.160 --> 00:08:53.860 align:start position:0% like stuff like a liquid talking occur see<00:08:52.340> there<00:08:53.180> is<00:08:53.270> no<00:08:53.390> I<00:08:53.450> call<00:08:53.600> it<00:08:53.630> talking 00:08:53.860 --> 00:08:53.870 align:start position:0% see there is no I call it talking 00:08:53.870 --> 00:08:55.270 align:start position:0% see there is no I call it talking overseas<00:08:54.410> because<00:08:54.530> it<00:08:54.920> is<00:08:55.070> not<00:08:55.250> like 00:08:55.270 --> 00:08:55.280 align:start position:0% overseas because it is not like 00:08:55.280 --> 00:08:56.740 align:start position:0% overseas because it is not like democracy<00:08:55.940> in<00:08:56.030> the<00:08:56.120> sense<00:08:56.300> that<00:08:56.360> you<00:08:56.570> have 00:08:56.740 --> 00:08:56.750 align:start position:0% democracy in the sense that you have 00:08:56.750 --> 00:08:58.600 align:start position:0% democracy in the sense that you have like<00:08:56.960> one<00:08:57.740> person<00:08:58.040> one<00:08:58.160> vote 00:08:58.600 --> 00:08:58.610 align:start position:0% like one person one vote 00:08:58.610 --> 00:09:00.400 align:start position:0% like one person one vote you<00:08:59.060> can<00:08:59.209> also<00:08:59.360> do<00:08:59.540> that<00:08:59.660> with<00:08:59.720> Aragon<00:09:00.230> there 00:09:00.400 --> 00:09:00.410 align:start position:0% you can also do that with Aragon there 00:09:00.410 --> 00:09:02.620 align:start position:0% you can also do that with Aragon there is<00:09:00.500> another<00:09:00.740> doubt<00:09:01.700> that<00:09:01.910> is<00:09:02.000> theirs<00:09:02.270> in<00:09:02.480> that 00:09:02.620 --> 00:09:02.630 align:start position:0% is another doubt that is theirs in that 00:09:02.630 --> 00:09:05.860 align:start position:0% is another doubt that is theirs in that doing<00:09:03.260> some<00:09:03.470> kind<00:09:03.680> of<00:09:03.740> like<00:09:04.360> civil<00:09:05.360> resistance 00:09:05.860 --> 00:09:05.870 align:start position:0% doing some kind of like civil resistance 00:09:05.870 --> 00:09:07.690 align:start position:0% doing some kind of like civil resistance using<00:09:06.410> an<00:09:06.620> app<00:09:06.770> that<00:09:07.130> they<00:09:07.250> have<00:09:07.430> in<00:09:07.580> which 00:09:07.690 --> 00:09:07.700 align:start position:0% using an app that they have in which 00:09:07.700 --> 00:09:08.769 align:start position:0% using an app that they have in which have<00:09:07.910> to<00:09:08.000> like<00:09:08.120> take<00:09:08.240> a<00:09:08.360> four<00:09:08.540> or<00:09:08.660> something 00:09:08.769 --> 00:09:08.779 align:start position:0% have to like take a four or something 00:09:08.779 --> 00:09:10.930 align:start position:0% have to like take a four or something like<00:09:08.990> that<00:09:09.050> it's<00:09:09.470> a<00:09:09.529> legal<00:09:09.620> system<00:09:10.040> but<00:09:10.250> here 00:09:10.930 --> 00:09:10.940 align:start position:0% like that it's a legal system but here 00:09:10.940 --> 00:09:12.250 align:start position:0% like that it's a legal system but here I'm<00:09:11.060> referring<00:09:11.390> to<00:09:11.420> doctor<00:09:11.720> no<00:09:11.839> curses<00:09:12.140> so 00:09:12.250 --> 00:09:12.260 align:start position:0% I'm referring to doctor no curses so 00:09:12.260 --> 00:09:14.760 align:start position:0% I'm referring to doctor no curses so basically<00:09:12.610> the<00:09:13.610> scheme<00:09:13.850> the<00:09:13.970> game<00:09:14.120> kind<00:09:14.510> of 00:09:14.760 --> 00:09:14.770 align:start position:0% basically the scheme the game kind of 00:09:14.770 --> 00:09:16.900 align:start position:0% basically the scheme the game kind of kind<00:09:15.770> of<00:09:15.830> token<00:09:16.010> are<00:09:16.190> see<00:09:16.459> where<00:09:16.670> like<00:09:16.820> you 00:09:16.900 --> 00:09:16.910 align:start position:0% kind of token are see where like you 00:09:16.910 --> 00:09:18.100 align:start position:0% kind of token are see where like you have<00:09:17.060> one<00:09:17.180> token<00:09:17.450> you<00:09:17.660> have<00:09:17.779> one<00:09:17.959> ball 00:09:18.100 --> 00:09:18.110 align:start position:0% have one token you have one ball 00:09:18.110 --> 00:09:19.990 align:start position:0% have one token you have one ball basically<00:09:18.410> and<00:09:18.890> so<00:09:19.399> you<00:09:19.459> can<00:09:19.670> have<00:09:19.790> something 00:09:19.990 --> 00:09:20.000 align:start position:0% basically and so you can have something 00:09:20.000 --> 00:09:21.850 align:start position:0% basically and so you can have something like<00:09:20.149> a<00:09:20.390> liquid<00:09:20.600> token<00:09:20.899> aa<00:09:20.959> cracy<00:09:21.260> where<00:09:21.740> you 00:09:21.850 --> 00:09:21.860 align:start position:0% like a liquid token aa cracy where you 00:09:21.860 --> 00:09:23.560 align:start position:0% like a liquid token aa cracy where you can<00:09:22.040> delegate<00:09:22.490> to<00:09:22.550> other<00:09:22.880> people's<00:09:23.330> you're 00:09:23.560 --> 00:09:23.570 align:start position:0% can delegate to other people's you're 00:09:23.570 --> 00:09:25.750 align:start position:0% can delegate to other people's you're talking<00:09:23.899> holders<00:09:24.260> don't<00:09:24.500> have<00:09:24.680> to<00:09:24.920> read<00:09:25.550> every 00:09:25.750 --> 00:09:25.760 align:start position:0% talking holders don't have to read every 00:09:25.760 --> 00:09:28.090 align:start position:0% talking holders don't have to read every proposal<00:09:26.510> they<00:09:26.630> can<00:09:26.779> use<00:09:26.959> delegate<00:09:27.560> to<00:09:27.709> other 00:09:28.090 --> 00:09:28.100 align:start position:0% proposal they can use delegate to other 00:09:28.100 --> 00:09:30.310 align:start position:0% proposal they can use delegate to other person<00:09:28.550> that<00:09:28.670> they<00:09:28.820> they<00:09:29.330> think<00:09:29.390> is<00:09:29.630> it's<00:09:30.140> more 00:09:30.310 --> 00:09:30.320 align:start position:0% person that they they think is it's more 00:09:30.320 --> 00:09:32.710 align:start position:0% person that they they think is it's more expert<00:09:30.680> in<00:09:30.709> that<00:09:30.920> in<00:09:31.160> the<00:09:31.279> field<00:09:31.459> but<00:09:32.450> then<00:09:32.600> it 00:09:32.710 --> 00:09:32.720 align:start position:0% expert in that in the field but then it 00:09:32.720 --> 00:09:34.210 align:start position:0% expert in that in the field but then it that<00:09:32.870> person<00:09:33.260> that<00:09:33.410> delegate<00:09:33.830> is<00:09:34.070> not 00:09:34.210 --> 00:09:34.220 align:start position:0% that person that delegate is not 00:09:34.220 --> 00:09:35.769 align:start position:0% that person that delegate is not performing<00:09:34.610> well<00:09:34.790> they<00:09:35.029> can<00:09:35.180> with<00:09:35.360> rollerball 00:09:35.769 --> 00:09:35.779 align:start position:0% performing well they can with rollerball 00:09:35.779 --> 00:09:37.329 align:start position:0% performing well they can with rollerball immediately<00:09:36.410> and<00:09:36.620> give<00:09:36.830> it<00:09:36.890> to<00:09:36.920> someone<00:09:37.190> else 00:09:37.329 --> 00:09:37.339 align:start position:0% immediately and give it to someone else 00:09:37.339 --> 00:09:39.490 align:start position:0% immediately and give it to someone else so<00:09:38.149> that's<00:09:38.300> very<00:09:38.420> cool<00:09:38.720> we're<00:09:39.170> working<00:09:39.410> on 00:09:39.490 --> 00:09:39.500 align:start position:0% so that's very cool we're working on 00:09:39.500 --> 00:09:42.100 align:start position:0% so that's very cool we're working on that<00:09:39.620> implementation<00:09:40.510> and<00:09:41.510> then<00:09:41.690> you<00:09:41.930> have 00:09:42.100 --> 00:09:42.110 align:start position:0% that implementation and then you have 00:09:42.110 --> 00:09:44.079 align:start position:0% that implementation and then you have something<00:09:42.320> that<00:09:42.740> is<00:09:43.130> I<00:09:43.430> think<00:09:43.490> the<00:09:43.730> probably 00:09:44.079 --> 00:09:44.089 align:start position:0% something that is I think the probably 00:09:44.089 --> 00:09:45.610 align:start position:0% something that is I think the probably the<00:09:44.149> most<00:09:44.270> Restless<00:09:44.660> but<00:09:44.810> also<00:09:45.080> like<00:09:45.230> ever 00:09:45.610 --> 00:09:45.620 align:start position:0% the most Restless but also like ever 00:09:45.620 --> 00:09:48.460 align:start position:0% the most Restless but also like ever slow<00:09:45.890> which<00:09:46.520> is<00:09:46.700> direct<00:09:47.060> democracy<00:09:47.470> that's 00:09:48.460 --> 00:09:48.470 align:start position:0% slow which is direct democracy that's 00:09:48.470 --> 00:09:50.980 align:start position:0% slow which is direct democracy that's what<00:09:48.680> we<00:09:48.800> do<00:09:48.920> also<00:09:49.100> in<00:09:49.520> in<00:09:50.029> Aragon<00:09:50.420> for<00:09:50.630> our<00:09:50.779> own 00:09:50.980 --> 00:09:50.990 align:start position:0% what we do also in in Aragon for our own 00:09:50.990 --> 00:09:53.110 align:start position:0% what we do also in in Aragon for our own governance<00:09:51.440> so<00:09:51.920> it's<00:09:52.220> three<00:09:52.520> months<00:09:52.670> Torian 00:09:53.110 --> 00:09:53.120 align:start position:0% governance so it's three months Torian 00:09:53.120 --> 00:09:55.240 align:start position:0% governance so it's three months Torian holders<00:09:53.480> get<00:09:53.899> to<00:09:54.020> decide<00:09:54.350> on<00:09:54.589> the<00:09:54.950> future<00:09:55.070> of 00:09:55.240 --> 00:09:55.250 align:start position:0% holders get to decide on the future of 00:09:55.250 --> 00:09:57.190 align:start position:0% holders get to decide on the future of the<00:09:55.370> project<00:09:55.520> and<00:09:55.970> I<00:09:56.630> think<00:09:56.870> I<00:09:56.930> think<00:09:57.050> that's<00:09:57.170> a 00:09:57.190 --> 00:09:57.200 align:start position:0% the project and I think I think that's a 00:09:57.200 --> 00:09:59.920 align:start position:0% the project and I think I think that's a very<00:09:57.290> cool<00:09:57.500> model<00:09:57.649> it's<00:09:58.580> again<00:09:59.540> like<00:09:59.570> it's 00:09:59.920 --> 00:09:59.930 align:start position:0% very cool model it's again like it's 00:09:59.930 --> 00:10:01.510 align:start position:0% very cool model it's again like it's super<00:10:00.020> trackless<00:10:00.560> like<00:10:00.920> you<00:10:01.220> know<00:10:01.279> every 00:10:01.510 --> 00:10:01.520 align:start position:0% super trackless like you know every 00:10:01.520 --> 00:10:02.590 align:start position:0% super trackless like you know every three<00:10:01.610> months<00:10:01.790> basically<00:10:02.270> they<00:10:02.360> can<00:10:02.480> do 00:10:02.590 --> 00:10:02.600 align:start position:0% three months basically they can do 00:10:02.600 --> 00:10:03.370 align:start position:0% three months basically they can do whatever<00:10:02.750> they<00:10:02.870> want 00:10:03.370 --> 00:10:03.380 align:start position:0% whatever they want 00:10:03.380 --> 00:10:05.199 align:start position:0% whatever they want you<00:10:04.339> don't<00:10:04.490> have<00:10:04.579> to<00:10:04.700> do<00:10:04.760> it<00:10:04.820> every<00:10:05.029> three 00:10:05.199 --> 00:10:05.209 align:start position:0% you don't have to do it every three 00:10:05.209 --> 00:10:06.550 align:start position:0% you don't have to do it every three months<00:10:05.300> you<00:10:05.420> can<00:10:05.630> do<00:10:05.720> like<00:10:05.839> continues<00:10:06.260> as<00:10:06.380> well 00:10:06.550 --> 00:10:06.560 align:start position:0% months you can do like continues as well 00:10:06.560 --> 00:10:08.590 align:start position:0% months you can do like continues as well but<00:10:07.100> of<00:10:07.190> course<00:10:07.459> if<00:10:07.790> you<00:10:07.970> need<00:10:08.089> all<00:10:08.360> the<00:10:08.480> other 00:10:08.590 --> 00:10:08.600 align:start position:0% but of course if you need all the other 00:10:08.600 --> 00:10:10.090 align:start position:0% but of course if you need all the other kind<00:10:08.750> of<00:10:08.779> holders<00:10:09.079> to<00:10:09.230> come<00:10:09.410> together<00:10:09.620> and 00:10:10.090 --> 00:10:10.100 align:start position:0% kind of holders to come together and 00:10:10.100 --> 00:10:12.639 align:start position:0% kind of holders to come together and take<00:10:10.310> a<00:10:10.339> decision<00:10:11.079> maybe<00:10:12.079> it's<00:10:12.320> better<00:10:12.470> to 00:10:12.639 --> 00:10:12.649 align:start position:0% take a decision maybe it's better to 00:10:12.649 --> 00:10:14.949 align:start position:0% take a decision maybe it's better to like<00:10:12.770> concentrate<00:10:13.070> that<00:10:13.430> into<00:10:14.000> one<00:10:14.300> moment 00:10:14.949 --> 00:10:14.959 align:start position:0% like concentrate that into one moment 00:10:14.959 --> 00:10:16.990 align:start position:0% like concentrate that into one moment each<00:10:15.230> quarter<00:10:15.770> one<00:10:16.010> moment<00:10:16.310> each<00:10:16.430> year<00:10:16.670> kind 00:10:16.990 --> 00:10:17.000 align:start position:0% each quarter one moment each year kind 00:10:17.000 --> 00:10:18.639 align:start position:0% each quarter one moment each year kind of<00:10:17.060> things<00:10:17.270> so<00:10:17.450> it's<00:10:17.570> more<00:10:18.170> you<00:10:18.440> know<00:10:18.529> it's<00:10:18.620> a 00:10:18.639 --> 00:10:18.649 align:start position:0% of things so it's more you know it's a 00:10:18.649 --> 00:10:21.850 align:start position:0% of things so it's more you know it's a slower<00:10:18.860> but<00:10:19.459> it's<00:10:19.579> much<00:10:19.670> restless<00:10:20.200> so<00:10:21.200> again 00:10:21.850 --> 00:10:21.860 align:start position:0% slower but it's much restless so again 00:10:21.860 --> 00:10:23.290 align:start position:0% slower but it's much restless so again you<00:10:22.250> know<00:10:22.339> you<00:10:22.430> can<00:10:22.579> defend<00:10:22.850> all<00:10:22.970> of<00:10:23.060> this<00:10:23.149> with 00:10:23.290 --> 00:10:23.300 align:start position:0% you know you can defend all of this with 00:10:23.300 --> 00:10:25.090 align:start position:0% you know you can defend all of this with Aragon<00:10:23.660> and<00:10:23.779> you<00:10:23.990> can<00:10:24.170> basically<00:10:24.350> see<00:10:24.920> what 00:10:25.090 --> 00:10:25.100 align:start position:0% Aragon and you can basically see what 00:10:25.100 --> 00:10:26.380 align:start position:0% Aragon and you can basically see what are<00:10:25.190> you<00:10:25.279> trade-offs<00:10:25.670> what<00:10:25.910> matters<00:10:26.149> to<00:10:26.209> you 00:10:26.380 --> 00:10:26.390 align:start position:0% are you trade-offs what matters to you 00:10:26.390 --> 00:10:28.120 align:start position:0% are you trade-offs what matters to you and<00:10:26.540> then<00:10:26.839> you<00:10:27.200> know<00:10:27.290> customize<00:10:27.740> your<00:10:27.890> doubt 00:10:28.120 --> 00:10:28.130 align:start position:0% and then you know customize your doubt 00:10:28.130 --> 00:10:32.380 align:start position:0% and then you know customize your doubt to<00:10:28.459> fit<00:10:28.640> those<00:10:28.790> needs<00:10:29.230> so<00:10:30.230> I<00:10:30.579> think<00:10:31.579> it<00:10:32.000> is<00:10:32.180> very 00:10:32.380 --> 00:10:32.390 align:start position:0% to fit those needs so I think it is very 00:10:32.390 --> 00:10:34.120 align:start position:0% to fit those needs so I think it is very important<00:10:32.899> to<00:10:32.990> build<00:10:33.260> a<00:10:33.350> community<00:10:33.500> not<00:10:34.070> only 00:10:34.120 --> 00:10:34.130 align:start position:0% important to build a community not only 00:10:34.130 --> 00:10:35.650 align:start position:0% important to build a community not only to<00:10:34.459> ensure<00:10:34.579> that<00:10:34.820> the<00:10:35.089> protocol<00:10:35.480> remains 00:10:35.650 --> 00:10:35.660 align:start position:0% to ensure that the protocol remains 00:10:35.660 --> 00:10:37.750 align:start position:0% to ensure that the protocol remains trustless<00:10:36.290> and<00:10:36.589> so<00:10:36.800> you<00:10:36.920> can<00:10:37.040> eventually<00:10:37.310> move 00:10:37.750 --> 00:10:37.760 align:start position:0% trustless and so you can eventually move 00:10:37.760 --> 00:10:39.550 align:start position:0% trustless and so you can eventually move governance<00:10:38.300> from<00:10:38.930> centralized<00:10:39.410> to 00:10:39.550 --> 00:10:39.560 align:start position:0% governance from centralized to 00:10:39.560 --> 00:10:40.360 align:start position:0% governance from centralized to decentralized 00:10:40.360 --> 00:10:40.370 align:start position:0% decentralized 00:10:40.370 --> 00:10:42.130 align:start position:0% decentralized but<00:10:40.970> also<00:10:41.089> because<00:10:41.390> if<00:10:41.510> you<00:10:41.600> looked<00:10:41.779> at<00:10:41.959> like 00:10:42.130 --> 00:10:42.140 align:start position:0% but also because if you looked at like 00:10:42.140 --> 00:10:44.410 align:start position:0% but also because if you looked at like where<00:10:42.709> is<00:10:42.950> all<00:10:43.130> about<00:10:43.370> is<00:10:43.670> basically<00:10:43.940> network 00:10:44.410 --> 00:10:44.420 align:start position:0% where is all about is basically network 00:10:44.420 --> 00:10:47.019 align:start position:0% where is all about is basically network effects<00:10:44.810> around<00:10:45.320> communities<00:10:45.890> the<00:10:46.550> code<00:10:46.790> can 00:10:47.019 --> 00:10:47.029 align:start position:0% effects around communities the code can 00:10:47.029 --> 00:10:50.920 align:start position:0% effects around communities the code can be<00:10:47.060> forked<00:10:48.070> of<00:10:49.070> course<00:10:49.640> like<00:10:49.850> brand<00:10:50.570> and<00:10:50.779> stuff 00:10:50.920 --> 00:10:50.930 align:start position:0% be forked of course like brand and stuff 00:10:50.930 --> 00:10:53.800 align:start position:0% be forked of course like brand and stuff like<00:10:51.050> that<00:10:51.230> and<00:10:51.470> community<00:10:52.339> cannot<00:10:52.850> so<00:10:53.480> it<00:10:53.720> is 00:10:53.800 --> 00:10:53.810 align:start position:0% like that and community cannot so it is 00:10:53.810 --> 00:10:55.449 align:start position:0% like that and community cannot so it is very<00:10:54.350> very<00:10:54.500> important<00:10:54.800> that<00:10:54.890> we<00:10:54.950> focus<00:10:55.130> on<00:10:55.339> the 00:10:55.449 --> 00:10:55.459 align:start position:0% very very important that we focus on the 00:10:55.459 --> 00:10:57.250 align:start position:0% very very important that we focus on the right<00:10:55.610> things<00:10:55.850> here<00:10:56.120> in<00:10:56.329> communities<00:10:56.839> direct 00:10:57.250 --> 00:10:57.260 align:start position:0% right things here in communities direct 00:10:57.260 --> 00:10:59.500 align:start position:0% right things here in communities direct thing<00:10:57.410> if<00:10:57.529> you<00:10:57.649> look<00:10:57.800> at<00:10:57.890> the<00:10:57.980> theorem<00:10:58.480> you<00:10:59.480> can 00:10:59.500 --> 00:10:59.510 align:start position:0% thing if you look at the theorem you can 00:10:59.510 --> 00:11:01.720 align:start position:0% thing if you look at the theorem you can you<00:10:59.899> can<00:11:00.050> forget<00:11:00.320> theory<00:11:00.529> on<00:11:00.649> today<00:11:00.890> you<00:11:01.520> can 00:11:01.720 --> 00:11:01.730 align:start position:0% you can forget theory on today you can 00:11:01.730 --> 00:11:04.540 align:start position:0% you can forget theory on today you can name<00:11:01.940> it<00:11:01.970> a<00:11:02.300> theorem<00:11:02.720> cache<00:11:03.050> try<00:11:03.920> no<00:11:04.130> one<00:11:04.310> would 00:11:04.540 --> 00:11:04.550 align:start position:0% name it a theorem cache try no one would 00:11:04.550 --> 00:11:06.460 align:start position:0% name it a theorem cache try no one would use<00:11:04.760> it<00:11:04.970> because<00:11:05.120> a<00:11:05.240> community<00:11:05.480> we<00:11:05.959> have<00:11:06.110> here 00:11:06.460 --> 00:11:06.470 align:start position:0% use it because a community we have here 00:11:06.470 --> 00:11:09.400 align:start position:0% use it because a community we have here you<00:11:07.010> guys<00:11:07.220> and<00:11:07.610> everyone<00:11:08.240> out<00:11:08.360> there<00:11:08.449> that 00:11:09.400 --> 00:11:09.410 align:start position:0% you guys and everyone out there that 00:11:09.410 --> 00:11:11.440 align:start position:0% you guys and everyone out there that cannot<00:11:09.829> be<00:11:09.920> forked 00:11:11.440 --> 00:11:11.450 align:start position:0% cannot be forked 00:11:11.450 --> 00:11:15.580 align:start position:0% cannot be forked so<00:11:12.410> I<00:11:12.710> think<00:11:13.700> also<00:11:13.970> is<00:11:14.120> very<00:11:14.180> important<00:11:14.630> as<00:11:15.380> a 00:11:15.580 --> 00:11:15.590 align:start position:0% so I think also is very important as a 00:11:15.590 --> 00:11:17.200 align:start position:0% so I think also is very important as a South<00:11:15.800> South<00:11:16.430> student<00:11:16.820> the<00:11:16.880> other<00:11:17.000> day<00:11:17.180> that 00:11:17.200 --> 00:11:17.210 align:start position:0% South South student the other day that 00:11:17.210 --> 00:11:19.690 align:start position:0% South South student the other day that we<00:11:18.170> see<00:11:18.380> organizations<00:11:19.040> and<00:11:19.310> governance 00:11:19.690 --> 00:11:19.700 align:start position:0% we see organizations and governance 00:11:19.700 --> 00:11:22.420 align:start position:0% we see organizations and governance structures<00:11:20.240> as<00:11:20.510> products<00:11:21.200> and<00:11:21.380> the<00:11:21.980> users 00:11:22.420 --> 00:11:22.430 align:start position:0% structures as products and the users 00:11:22.430 --> 00:11:23.740 align:start position:0% structures as products and the users maybe<00:11:22.700> in<00:11:22.940> this<00:11:23.000> case<00:11:23.060> I<00:11:23.300> was<00:11:23.420> talking<00:11:23.660> about 00:11:23.740 --> 00:11:23.750 align:start position:0% maybe in this case I was talking about 00:11:23.750 --> 00:11:25.540 align:start position:0% maybe in this case I was talking about like<00:11:23.990> a<00:11:24.050> more<00:11:24.650> like<00:11:24.740> a<00:11:24.800> company<00:11:25.100> structure 00:11:25.540 --> 00:11:25.550 align:start position:0% like a more like a company structure 00:11:25.550 --> 00:11:27.400 align:start position:0% like a more like a company structure like<00:11:25.760> an<00:11:25.850> organization<00:11:26.450> but<00:11:27.050> I<00:11:27.080> think<00:11:27.320> it's 00:11:27.400 --> 00:11:27.410 align:start position:0% like an organization but I think it's 00:11:27.410 --> 00:11:28.810 align:start position:0% like an organization but I think it's the<00:11:27.470> same<00:11:27.680> for<00:11:27.710> a<00:11:27.950> cryptic<00:11:28.280> protocol<00:11:28.640> or 00:11:28.810 --> 00:11:28.820 align:start position:0% the same for a cryptic protocol or 00:11:28.820 --> 00:11:31.210 align:start position:0% the same for a cryptic protocol or network<00:11:29.330> so<00:11:30.200> when<00:11:30.650> you<00:11:30.800> create<00:11:30.980> the 00:11:31.210 --> 00:11:31.220 align:start position:0% network so when you create the 00:11:31.220 --> 00:11:33.370 align:start position:0% network so when you create the governance<00:11:31.610> structure<00:11:32.150> that<00:11:32.360> is<00:11:33.050> also<00:11:33.230> a 00:11:33.370 --> 00:11:33.380 align:start position:0% governance structure that is also a 00:11:33.380 --> 00:11:35.620 align:start position:0% governance structure that is also a product<00:11:33.590> that<00:11:34.160> is<00:11:34.250> a<00:11:34.280> product<00:11:34.610> and<00:11:34.880> your<00:11:35.120> users 00:11:35.620 --> 00:11:35.630 align:start position:0% product that is a product and your users 00:11:35.630 --> 00:11:37.930 align:start position:0% product that is a product and your users argue<00:11:36.200> community<00:11:36.620> member<00:11:36.860> for<00:11:37.070> example<00:11:37.160> so 00:11:37.930 --> 00:11:37.940 align:start position:0% argue community member for example so 00:11:37.940 --> 00:11:39.100 align:start position:0% argue community member for example so when<00:11:38.090> I<00:11:38.150> think<00:11:38.210> of<00:11:38.450> the<00:11:38.630> governance<00:11:39.020> process 00:11:39.100 --> 00:11:39.110 align:start position:0% when I think of the governance process 00:11:39.110 --> 00:11:41.980 align:start position:0% when I think of the governance process we<00:11:39.410> created<00:11:39.590> for<00:11:39.950> ourselves<00:11:40.040> in<00:11:40.490> Aragon<00:11:40.990> we 00:11:41.980 --> 00:11:41.990 align:start position:0% we created for ourselves in Aragon we 00:11:41.990 --> 00:11:43.660 align:start position:0% we created for ourselves in Aragon we have<00:11:42.140> a<00:11:42.170> lot<00:11:42.410> of<00:11:42.440> these<00:11:42.560> people<00:11:42.770> who<00:11:43.130> out<00:11:43.340> for 00:11:43.660 --> 00:11:43.670 align:start position:0% have a lot of these people who out for 00:11:43.670 --> 00:11:45.400 align:start position:0% have a lot of these people who out for new<00:11:44.090> governor's<00:11:44.510> proposals<00:11:45.020> we<00:11:45.140> have<00:11:45.290> these 00:11:45.400 --> 00:11:45.410 align:start position:0% new governor's proposals we have these 00:11:45.410 --> 00:11:47.920 align:start position:0% new governor's proposals we have these people<00:11:45.770> who<00:11:46.310> edit<00:11:46.640> them<00:11:46.880> we<00:11:47.660> have<00:11:47.810> these 00:11:47.920 --> 00:11:47.930 align:start position:0% people who edit them we have these 00:11:47.930 --> 00:11:49.600 align:start position:0% people who edit them we have these people<00:11:48.290> who<00:11:48.560> then<00:11:48.770> are<00:11:49.070> community<00:11:49.580> members 00:11:49.600 --> 00:11:49.610 align:start position:0% people who then are community members 00:11:49.610 --> 00:11:51.940 align:start position:0% people who then are community members and<00:11:50.120> they<00:11:50.210> get<00:11:50.450> affected<00:11:50.840> by<00:11:50.990> them<00:11:51.200> so<00:11:51.710> at<00:11:51.860> the 00:11:51.940 --> 00:11:51.950 align:start position:0% and they get affected by them so at the 00:11:51.950 --> 00:11:53.410 align:start position:0% and they get affected by them so at the end<00:11:52.010> of<00:11:52.070> the<00:11:52.190> day<00:11:52.340> you<00:11:52.820> have<00:11:52.970> to<00:11:53.000> look<00:11:53.240> at<00:11:53.330> your 00:11:53.410 --> 00:11:53.420 align:start position:0% end of the day you have to look at your 00:11:53.420 --> 00:11:55.240 align:start position:0% end of the day you have to look at your community<00:11:53.600> and<00:11:54.080> your<00:11:54.200> governance<00:11:54.650> as<00:11:54.860> Houston 00:11:55.240 --> 00:11:55.250 align:start position:0% community and your governance as Houston 00:11:55.250 --> 00:11:57.430 align:start position:0% community and your governance as Houston all<00:11:55.520> product<00:11:55.940> if<00:11:56.120> you<00:11:56.330> have<00:11:56.480> to<00:11:56.660> care<00:11:56.930> of<00:11:56.960> it<00:11:57.230> as 00:11:57.430 --> 00:11:57.440 align:start position:0% all product if you have to care of it as 00:11:57.440 --> 00:11:59.050 align:start position:0% all product if you have to care of it as if<00:11:57.650> it<00:11:57.740> was<00:11:57.890> just<00:11:58.100> another<00:11:58.580> product<00:11:58.940> that 00:11:59.050 --> 00:11:59.060 align:start position:0% if it was just another product that 00:11:59.060 --> 00:12:01.150 align:start position:0% if it was just another product that you're<00:11:59.270> building<00:11:59.450> and<00:11:59.800> of<00:12:00.800> course<00:12:01.010> a<00:12:01.040> very 00:12:01.150 --> 00:12:01.160 align:start position:0% you're building and of course a very 00:12:01.160 --> 00:12:04.840 align:start position:0% you're building and of course a very important<00:12:01.490> one<00:12:01.640> I<00:12:02.950> think<00:12:03.950> also<00:12:04.220> when<00:12:04.610> talking 00:12:04.840 --> 00:12:04.850 align:start position:0% important one I think also when talking 00:12:04.850 --> 00:12:05.850 align:start position:0% important one I think also when talking about 00:12:05.850 --> 00:12:05.860 align:start position:0% about 00:12:05.860 --> 00:12:08.530 align:start position:0% about 1001<00:12:06.860> vote<00:12:07.070> a<00:12:07.340> lot<00:12:07.550> of<00:12:07.640> people<00:12:07.880> get<00:12:08.060> outraged 00:12:08.530 --> 00:12:08.540 align:start position:0% 1001 vote a lot of people get outraged 00:12:08.540 --> 00:12:11.680 align:start position:0% 1001 vote a lot of people get outraged about<00:12:08.810> you<00:12:09.170> know<00:12:09.400> plutocracy<00:12:10.400> and<00:12:10.730> capture 00:12:11.680 --> 00:12:11.690 align:start position:0% about you know plutocracy and capture 00:12:11.690 --> 00:12:14.020 align:start position:0% about you know plutocracy and capture and<00:12:11.990> all<00:12:12.050> of<00:12:12.140> these<00:12:12.260> things<00:12:12.410> right<00:12:12.650> I<00:12:12.890> think<00:12:13.730> if 00:12:14.020 --> 00:12:14.030 align:start position:0% and all of these things right I think if 00:12:14.030 --> 00:12:16.840 align:start position:0% and all of these things right I think if we<00:12:14.240> look<00:12:14.270> at<00:12:14.540> token<00:12:14.810> or<00:12:14.930> se<00:12:15.230> or<00:12:15.640> what<00:12:16.640> I<00:12:16.670> call 00:12:16.840 --> 00:12:16.850 align:start position:0% we look at token or se or what I call 00:12:16.850 --> 00:12:18.310 align:start position:0% we look at token or se or what I call the<00:12:16.910> evolution<00:12:17.600> of<00:12:17.660> a<00:12:17.840> stakeholder 00:12:18.310 --> 00:12:18.320 align:start position:0% the evolution of a stakeholder 00:12:18.320 --> 00:12:19.990 align:start position:0% the evolution of a stakeholder governance<00:12:18.800> if<00:12:19.040> you<00:12:19.160> look<00:12:19.280> at<00:12:19.370> shareholder 00:12:19.990 --> 00:12:20.000 align:start position:0% governance if you look at shareholder 00:12:20.000 --> 00:12:21.730 align:start position:0% governance if you look at shareholder governance<00:12:20.630> for<00:12:20.930> the<00:12:20.990> last<00:12:21.170> hundreds<00:12:21.650> of 00:12:21.730 --> 00:12:21.740 align:start position:0% governance for the last hundreds of 00:12:21.740 --> 00:12:23.740 align:start position:0% governance for the last hundreds of years<00:12:21.800> it<00:12:22.490> has<00:12:22.640> to<00:12:22.790> work<00:12:22.910> beautifully<00:12:23.570> to 00:12:23.740 --> 00:12:23.750 align:start position:0% years it has to work beautifully to 00:12:23.750 --> 00:12:25.840 align:start position:0% years it has to work beautifully to create<00:12:23.990> value<00:12:24.320> now<00:12:25.010> we<00:12:25.040> are<00:12:25.370> in<00:12:25.490> this<00:12:25.610> weird 00:12:25.840 --> 00:12:25.850 align:start position:0% create value now we are in this weird 00:12:25.850 --> 00:12:27.760 align:start position:0% create value now we are in this weird position<00:12:25.970> where<00:12:26.510> we<00:12:26.660> have<00:12:26.690> common<00:12:27.290> goods<00:12:27.500> or 00:12:27.760 --> 00:12:27.770 align:start position:0% position where we have common goods or 00:12:27.770 --> 00:12:29.380 align:start position:0% position where we have common goods or something<00:12:28.220> that<00:12:28.370> kind<00:12:28.610> of<00:12:28.670> resembles<00:12:29.120> a 00:12:29.380 --> 00:12:29.390 align:start position:0% something that kind of resembles a 00:12:29.390 --> 00:12:31.720 align:start position:0% something that kind of resembles a common<00:12:29.660> good<00:12:29.750> or<00:12:30.590> is<00:12:31.070> that<00:12:31.220> you<00:12:31.400> know<00:12:31.490> kind<00:12:31.700> of 00:12:31.720 --> 00:12:31.730 align:start position:0% common good or is that you know kind of 00:12:31.730 --> 00:12:33.430 align:start position:0% common good or is that you know kind of like<00:12:31.910> a<00:12:32.000> gray<00:12:32.210> area<00:12:32.360> between<00:12:32.660> a<00:12:32.960> common<00:12:33.320> good 00:12:33.430 --> 00:12:33.440 align:start position:0% like a gray area between a common good 00:12:33.440 --> 00:12:35.200 align:start position:0% like a gray area between a common good and<00:12:33.680> also<00:12:33.980> like<00:12:34.130> like<00:12:34.460> a<00:12:34.520> parrot<00:12:34.790> property 00:12:35.200 --> 00:12:35.210 align:start position:0% and also like like a parrot property 00:12:35.210 --> 00:12:37.450 align:start position:0% and also like like a parrot property because<00:12:36.110> I<00:12:36.230> mean<00:12:36.350> it's<00:12:36.500> not<00:12:36.590> certainly<00:12:37.160> like<00:12:37.340> a 00:12:37.450 --> 00:12:37.460 align:start position:0% because I mean it's not certainly like a 00:12:37.460 --> 00:12:38.680 align:start position:0% because I mean it's not certainly like a hundred<00:12:37.730> percent<00:12:37.820> common<00:12:38.240> good<00:12:38.390> you<00:12:38.510> have<00:12:38.660> to 00:12:38.680 --> 00:12:38.690 align:start position:0% hundred percent common good you have to 00:12:38.690 --> 00:12:41.050 align:start position:0% hundred percent common good you have to like<00:12:38.930> at<00:12:39.080> quiet<00:12:39.410> if<00:12:39.710> or<00:12:40.070> Bitcoin<00:12:40.670> or<00:12:40.760> whatever 00:12:41.050 --> 00:12:41.060 align:start position:0% like at quiet if or Bitcoin or whatever 00:12:41.060 --> 00:12:43.210 align:start position:0% like at quiet if or Bitcoin or whatever to<00:12:41.240> a<00:12:41.270> part<00:12:41.510> of<00:12:41.600> these<00:12:41.720> networks<00:12:41.960> but<00:12:42.950> the<00:12:43.040> same 00:12:43.210 --> 00:12:43.220 align:start position:0% to a part of these networks but the same 00:12:43.220 --> 00:12:44.920 align:start position:0% to a part of these networks but the same of<00:12:43.340> at<00:12:43.820> the<00:12:43.910> same<00:12:44.060> time<00:12:44.240> like<00:12:44.420> is<00:12:44.540> not<00:12:44.690> use<00:12:44.840> a 00:12:44.920 --> 00:12:44.930 align:start position:0% of at the same time like is not use a 00:12:44.930 --> 00:12:47.110 align:start position:0% of at the same time like is not use a traditional<00:12:45.170> private<00:12:45.740> company<00:12:46.100> safe<00:12:46.670> in<00:12:46.820> here 00:12:47.110 --> 00:12:47.120 align:start position:0% traditional private company safe in here 00:12:47.120 --> 00:12:48.880 align:start position:0% traditional private company safe in here with<00:12:47.330> this<00:12:47.510> evolution<00:12:48.170> of<00:12:48.260> stakeholder 00:12:48.880 --> 00:12:48.890 align:start position:0% with this evolution of stakeholder 00:12:48.890 --> 00:12:51.400 align:start position:0% with this evolution of stakeholder governance<00:12:49.370> one<00:12:49.760> token<00:12:50.000> one<00:12:50.270> vote<00:12:50.600> there<00:12:51.350> are 00:12:51.400 --> 00:12:51.410 align:start position:0% governance one token one vote there are 00:12:51.410 --> 00:12:53.200 align:start position:0% governance one token one vote there are certain<00:12:51.710> things<00:12:51.740> like<00:12:52.010> cool<00:12:52.280> improved<00:12:52.610> but 00:12:53.200 --> 00:12:53.210 align:start position:0% certain things like cool improved but 00:12:53.210 --> 00:12:54.250 align:start position:0% certain things like cool improved but there<00:12:53.300> are<00:12:53.390> also<00:12:53.540> things<00:12:53.810> that<00:12:53.930> are<00:12:54.080> really 00:12:54.250 --> 00:12:54.260 align:start position:0% there are also things that are really 00:12:54.260 --> 00:12:56.320 align:start position:0% there are also things that are really great<00:12:54.470> and<00:12:55.190> they<00:12:55.340> are<00:12:55.400> very<00:12:55.550> handy<00:12:55.880> if<00:12:56.060> you<00:12:56.180> is 00:12:56.320 --> 00:12:56.330 align:start position:0% great and they are very handy if you is 00:12:56.330 --> 00:12:58.540 align:start position:0% great and they are very handy if you is when<00:12:56.510> I<00:12:56.540> like<00:12:56.720> have<00:12:57.440> a<00:12:57.650> community<00:12:58.160> bought<00:12:58.370> in 00:12:58.540 --> 00:12:58.550 align:start position:0% when I like have a community bought in 00:12:58.550 --> 00:12:59.170 align:start position:0% when I like have a community bought in today 00:12:59.170 --> 00:12:59.180 align:start position:0% today 00:12:59.180 --> 00:13:01.690 align:start position:0% today so<00:12:59.630> in<00:12:59.960> service<00:13:00.710> get<00:13:00.860> in<00:13:00.920> the<00:13:01.010> game<00:13:01.160> of<00:13:01.370> course 00:13:01.690 --> 00:13:01.700 align:start position:0% so in service get in the game of course 00:13:01.700 --> 00:13:03.370 align:start position:0% so in service get in the game of course if<00:13:01.820> you<00:13:01.910> have<00:13:02.060> participants<00:13:02.570> in<00:13:02.900> your<00:13:02.930> network 00:13:03.370 --> 00:13:03.380 align:start position:0% if you have participants in your network 00:13:03.380 --> 00:13:05.290 align:start position:0% if you have participants in your network that<00:13:03.410> owned<00:13:03.860> a<00:13:03.890> big<00:13:04.280> stake<00:13:04.610> or<00:13:04.850> they<00:13:04.970> own<00:13:05.180> a 00:13:05.290 --> 00:13:05.300 align:start position:0% that owned a big stake or they own a 00:13:05.300 --> 00:13:07.120 align:start position:0% that owned a big stake or they own a mistake<00:13:05.630> they're<00:13:06.380> going<00:13:06.530> to<00:13:06.590> be<00:13:06.650> incentivized 00:13:07.120 --> 00:13:07.130 align:start position:0% mistake they're going to be incentivized 00:13:07.130 --> 00:13:08.620 align:start position:0% mistake they're going to be incentivized for<00:13:07.310> the<00:13:07.400> network<00:13:07.700> in<00:13:07.910> the<00:13:08.000> community<00:13:08.420> to<00:13:08.510> grow 00:13:08.620 --> 00:13:08.630 align:start position:0% for the network in the community to grow 00:13:08.630 --> 00:13:11.230 align:start position:0% for the network in the community to grow and<00:13:08.960> work<00:13:09.310> they<00:13:10.310> are<00:13:10.430> easy<00:13:10.610> to<00:13:10.730> deploy<00:13:10.880> today 00:13:11.230 --> 00:13:11.240 align:start position:0% and work they are easy to deploy today 00:13:11.240 --> 00:13:13.030 align:start position:0% and work they are easy to deploy today like<00:13:11.720> you<00:13:11.810> can<00:13:11.960> deploy<00:13:12.170> one<00:13:12.410> token<00:13:12.590> one<00:13:12.830> vote 00:13:13.030 --> 00:13:13.040 align:start position:0% like you can deploy one token one vote 00:13:13.040 --> 00:13:15.430 align:start position:0% like you can deploy one token one vote today<00:13:13.310> very<00:13:13.820> very<00:13:13.910> easy<00:13:14.180> allows<00:13:15.080> first 00:13:15.430 --> 00:13:15.440 align:start position:0% today very very easy allows first 00:13:15.440 --> 00:13:17.560 align:start position:0% today very very easy allows first autonomous<00:13:15.650> participants<00:13:16.310> I<00:13:16.700> don't<00:13:17.240> like<00:13:17.390> to 00:13:17.560 --> 00:13:17.570 align:start position:0% autonomous participants I don't like to 00:13:17.570 --> 00:13:19.540 align:start position:0% autonomous participants I don't like to watch<00:13:17.690> it<00:13:17.900> I<00:13:18.080> think<00:13:18.530> it<00:13:18.680> works<00:13:19.160> for<00:13:19.370> some 00:13:19.540 --> 00:13:19.550 align:start position:0% watch it I think it works for some 00:13:19.550 --> 00:13:21.600 align:start position:0% watch it I think it works for some models<00:13:19.700> governance<00:13:20.330> models<00:13:20.570> but<00:13:20.750> I<00:13:20.810> think 00:13:21.600 --> 00:13:21.610 align:start position:0% models governance models but I think 00:13:21.610 --> 00:13:23.740 align:start position:0% models governance models but I think allowing<00:13:22.610> students<00:13:23.000> participation<00:13:23.570> is<00:13:23.660> very 00:13:23.740 --> 00:13:23.750 align:start position:0% allowing students participation is very 00:13:23.750 --> 00:13:24.310 align:start position:0% allowing students participation is very important 00:13:24.310 --> 00:13:24.320 align:start position:0% important 00:13:24.320 --> 00:13:26.140 align:start position:0% important sample<00:13:24.680> in<00:13:24.770> the<00:13:24.860> our<00:13:24.980> own<00:13:25.010> community<00:13:25.580> there 00:13:26.140 --> 00:13:26.150 align:start position:0% sample in the our own community there 00:13:26.150 --> 00:13:27.790 align:start position:0% sample in the our own community there are<00:13:26.240> people<00:13:26.510> who<00:13:26.630> are<00:13:26.720> synonymous<00:13:26.990> they<00:13:27.410> pass 00:13:27.790 --> 00:13:27.800 align:start position:0% are people who are synonymous they pass 00:13:27.800 --> 00:13:29.590 align:start position:0% are people who are synonymous they pass proposals<00:13:28.370> into<00:13:28.640> the<00:13:28.790> ballot<00:13:29.090> and<00:13:29.270> they 00:13:29.590 --> 00:13:29.600 align:start position:0% proposals into the ballot and they 00:13:29.600 --> 00:13:30.970 align:start position:0% proposals into the ballot and they actually<00:13:29.750> get<00:13:30.080> up<00:13:30.140> to<00:13:30.350> buy<00:13:30.440> a<00:13:30.470> whole<00:13:30.740> community 00:13:30.970 --> 00:13:30.980 align:start position:0% actually get up to buy a whole community 00:13:30.980 --> 00:13:32.590 align:start position:0% actually get up to buy a whole community and<00:13:31.400> we<00:13:31.580> don't<00:13:31.760> know<00:13:31.880> who<00:13:32.030> these<00:13:32.150> people<00:13:32.210> are 00:13:32.590 --> 00:13:32.600 align:start position:0% and we don't know who these people are 00:13:32.600 --> 00:13:34.270 align:start position:0% and we don't know who these people are and<00:13:32.810> that's<00:13:33.080> beautiful<00:13:33.290> as<00:13:33.710> a<00:13:33.740> beauty<00:13:34.040> of<00:13:34.130> it 00:13:34.270 --> 00:13:34.280 align:start position:0% and that's beautiful as a beauty of it 00:13:34.280 --> 00:13:36.670 align:start position:0% and that's beautiful as a beauty of it and<00:13:34.430> then<00:13:35.150> also<00:13:35.360> allows<00:13:35.750> everyone<00:13:36.140> to<00:13:36.260> benefit 00:13:36.670 --> 00:13:36.680 align:start position:0% and then also allows everyone to benefit 00:13:36.680 --> 00:13:38.890 align:start position:0% and then also allows everyone to benefit from<00:13:36.860> value<00:13:37.190> creation<00:13:37.490> so<00:13:37.910> a<00:13:38.090> key<00:13:38.480> difference 00:13:38.890 --> 00:13:38.900 align:start position:0% from value creation so a key difference 00:13:38.900 --> 00:13:41.260 align:start position:0% from value creation so a key difference with<00:13:39.260> like<00:13:39.710> private<00:13:40.040> companies<00:13:40.460> decades<00:13:41.030> ago 00:13:41.260 --> 00:13:41.270 align:start position:0% with like private companies decades ago 00:13:41.270 --> 00:13:44.470 align:start position:0% with like private companies decades ago is<00:13:41.510> that<00:13:41.710> you<00:13:42.710> will<00:13:42.860> only<00:13:43.180> benefit<00:13:44.180> from<00:13:44.330> this 00:13:44.470 --> 00:13:44.480 align:start position:0% is that you will only benefit from this 00:13:44.480 --> 00:13:46.300 align:start position:0% is that you will only benefit from this value<00:13:44.750> creation<00:13:45.050> for<00:13:45.410> example<00:13:45.800> in<00:13:45.890> Apple 00:13:46.300 --> 00:13:46.310 align:start position:0% value creation for example in Apple 00:13:46.310 --> 00:13:48.190 align:start position:0% value creation for example in Apple Facebook<00:13:46.760> stuff<00:13:47.000> like<00:13:47.210> that<00:13:47.360> if<00:13:47.780> you<00:13:48.020> were<00:13:48.170> the 00:13:48.190 --> 00:13:48.200 align:start position:0% Facebook stuff like that if you were the 00:13:48.200 --> 00:13:50.440 align:start position:0% Facebook stuff like that if you were the first<00:13:48.350> engine<00:13:49.160> investor<00:13:49.640> the<00:13:49.790> seed<00:13:50.000> investor 00:13:50.440 --> 00:13:50.450 align:start position:0% first engine investor the seed investor 00:13:50.450 --> 00:13:53.050 align:start position:0% first engine investor the seed investor even<00:13:51.380> you<00:13:51.470> know<00:13:51.560> later<00:13:51.800> in<00:13:52.160> the<00:13:52.370> kind<00:13:52.760> of<00:13:52.790> like 00:13:53.050 --> 00:13:53.060 align:start position:0% even you know later in the kind of like 00:13:53.060 --> 00:13:54.610 align:start position:0% even you know later in the kind of like states<00:13:53.660> in<00:13:53.780> which<00:13:53.900> you<00:13:54.020> could<00:13:54.170> buy<00:13:54.290> shares 00:13:54.610 --> 00:13:54.620 align:start position:0% states in which you could buy shares 00:13:54.620 --> 00:13:56.740 align:start position:0% states in which you could buy shares right<00:13:54.980> but<00:13:55.640> not<00:13:55.820> all<00:13:56.000> people<00:13:56.120> have<00:13:56.390> access<00:13:56.480> to 00:13:56.740 --> 00:13:56.750 align:start position:0% right but not all people have access to 00:13:56.750 --> 00:14:00.010 align:start position:0% right but not all people have access to that<00:13:57.340> especially<00:13:58.340> not<00:13:59.000> like<00:13:59.300> everyone<00:13:59.840> who 00:14:00.010 --> 00:14:00.020 align:start position:0% that especially not like everyone who 00:14:00.020 --> 00:14:02.380 align:start position:0% that especially not like everyone who was<00:14:00.170> not<00:14:00.350> a<00:14:00.380> bc<00:14:00.740> here<00:14:01.520> everyone<00:14:02.060> can<00:14:02.270> just 00:14:02.380 --> 00:14:02.390 align:start position:0% was not a bc here everyone can just 00:14:02.390 --> 00:14:05.020 align:start position:0% was not a bc here everyone can just chime<00:14:02.630> in<00:14:02.840> and<00:14:03.110> you<00:14:03.680> know<00:14:03.800> buy<00:14:04.160> bitcoin<00:14:04.610> early 00:14:05.020 --> 00:14:05.030 align:start position:0% chime in and you know buy bitcoin early 00:14:05.030 --> 00:14:06.400 align:start position:0% chime in and you know buy bitcoin early in<00:14:05.090> the<00:14:05.180> day<00:14:05.300> or<00:14:05.540> buy<00:14:05.750> if<00:14:05.930> they're<00:14:06.170> buy 00:14:06.400 --> 00:14:06.410 align:start position:0% in the day or buy if they're buy 00:14:06.410 --> 00:14:07.990 align:start position:0% in the day or buy if they're buy whatever<00:14:06.740> kind<00:14:06.950> of<00:14:06.980> token<00:14:07.190> or<00:14:07.400> community<00:14:07.850> so 00:14:07.990 --> 00:14:08.000 align:start position:0% whatever kind of token or community so 00:14:08.000 --> 00:14:09.370 align:start position:0% whatever kind of token or community so they<00:14:08.090> can<00:14:08.240> become<00:14:08.510> participate<00:14:09.110> in<00:14:09.200> that 00:14:09.370 --> 00:14:09.380 align:start position:0% they can become participate in that 00:14:09.380 --> 00:14:13.360 align:start position:0% they can become participate in that value<00:14:09.680> creation<00:14:10.810> so<00:14:11.810> my<00:14:12.680> message<00:14:12.830> here<00:14:13.160> is 00:14:13.360 --> 00:14:13.370 align:start position:0% value creation so my message here is 00:14:13.370 --> 00:14:16.570 align:start position:0% value creation so my message here is only<00:14:14.180> honor<00:14:14.330> I<00:14:14.630> don't<00:14:14.870> think<00:14:14.990> it<00:14:15.230> will<00:14:15.440> last<00:14:15.650> we 00:14:16.570 --> 00:14:16.580 align:start position:0% only honor I don't think it will last we 00:14:16.580 --> 00:14:17.860 align:start position:0% only honor I don't think it will last we need<00:14:16.670> to<00:14:16.790> improve<00:14:16.970> traffic<00:14:17.270> Ness<00:14:17.630> and 00:14:17.860 --> 00:14:17.870 align:start position:0% need to improve traffic Ness and 00:14:17.870 --> 00:14:20.710 align:start position:0% need to improve traffic Ness and transparency<00:14:18.410> with<00:14:18.560> dowse<00:14:19.540> especially<00:14:20.540> for 00:14:20.710 --> 00:14:20.720 align:start position:0% transparency with dowse especially for 00:14:20.720 --> 00:14:21.850 align:start position:0% transparency with dowse especially for protocols<00:14:21.140> that<00:14:21.260> are<00:14:21.380> supposed<00:14:21.650> to<00:14:21.710> be 00:14:21.850 --> 00:14:21.860 align:start position:0% protocols that are supposed to be 00:14:21.860 --> 00:14:23.560 align:start position:0% protocols that are supposed to be decentralized<00:14:22.190> I<00:14:22.700> think<00:14:23.090> it's<00:14:23.210> important 00:14:23.560 --> 00:14:23.570 align:start position:0% decentralized I think it's important 00:14:23.570 --> 00:14:25.150 align:start position:0% decentralized I think it's important also<00:14:23.690> if<00:14:24.020> you<00:14:24.350> protocol<00:14:24.680> is<00:14:24.770> centralized 00:14:25.150 --> 00:14:25.160 align:start position:0% also if you protocol is centralized 00:14:25.160 --> 00:14:26.830 align:start position:0% also if you protocol is centralized today<00:14:25.430> I<00:14:25.670> think<00:14:26.210> you<00:14:26.300> know<00:14:26.390> there's<00:14:26.720> some 00:14:26.830 --> 00:14:26.840 align:start position:0% today I think you know there's some 00:14:26.840 --> 00:14:28.000 align:start position:0% today I think you know there's some trade-offs<00:14:27.050> there<00:14:27.380> are<00:14:27.440> things<00:14:27.620> that<00:14:27.680> need<00:14:27.800> to 00:14:28.000 --> 00:14:28.010 align:start position:0% trade-offs there are things that need to 00:14:28.010 --> 00:14:30.220 align:start position:0% trade-offs there are things that need to improved<00:14:28.370> and<00:14:28.610> item<00:14:29.090> the<00:14:29.210> angel<00:14:29.510> I<00:14:29.660> technology 00:14:30.220 --> 00:14:30.230 align:start position:0% improved and item the angel I technology 00:14:30.230 --> 00:14:32.560 align:start position:0% improved and item the angel I technology wasn't<00:14:30.770> there<00:14:31.010> a<00:14:31.370> year<00:14:31.610> ago<00:14:31.880> for<00:14:32.420> these 00:14:32.560 --> 00:14:32.570 align:start position:0% wasn't there a year ago for these 00:14:32.570 --> 00:14:33.880 align:start position:0% wasn't there a year ago for these protocols<00:14:32.840> to<00:14:33.170> actually<00:14:33.500> be<00:14:33.680> more 00:14:33.880 --> 00:14:33.890 align:start position:0% protocols to actually be more 00:14:33.890 --> 00:14:36.250 align:start position:0% protocols to actually be more decentralized<00:14:34.670> but<00:14:35.300> it<00:14:35.420> is<00:14:35.510> today<00:14:35.780> and<00:14:36.020> so<00:14:36.170> we 00:14:36.250 --> 00:14:36.260 align:start position:0% decentralized but it is today and so we 00:14:36.260 --> 00:14:37.840 align:start position:0% decentralized but it is today and so we need<00:14:36.380> to<00:14:36.410> like<00:14:36.620> if<00:14:36.980> the<00:14:37.130> way<00:14:37.310> we<00:14:37.460> need<00:14:37.580> to<00:14:37.670> think 00:14:37.840 --> 00:14:37.850 align:start position:0% need to like if the way we need to think 00:14:37.850 --> 00:14:38.860 align:start position:0% need to like if the way we need to think about<00:14:37.940> the<00:14:38.060> roadmap<00:14:38.240> and<00:14:38.600> we<00:14:38.660> need<00:14:38.780> to 00:14:38.860 --> 00:14:38.870 align:start position:0% about the roadmap and we need to 00:14:38.870 --> 00:14:40.150 align:start position:0% about the roadmap and we need to actually<00:14:38.990> get<00:14:39.320> these<00:14:39.440> things<00:14:39.680> into<00:14:39.920> a<00:14:39.950> point 00:14:40.150 --> 00:14:40.160 align:start position:0% actually get these things into a point 00:14:40.160 --> 00:14:43.060 align:start position:0% actually get these things into a point that<00:14:40.220> they<00:14:40.400> are<00:14:40.430> actually<00:14:40.820> trust<00:14:41.060> less<00:14:41.950> if<00:14:42.950> you 00:14:43.060 --> 00:14:43.070 align:start position:0% that they are actually trust less if you 00:14:43.070 --> 00:14:45.010 align:start position:0% that they are actually trust less if you get<00:14:43.220> an<00:14:43.280> early<00:14:43.430> on<00:14:43.640> your<00:14:43.760> problem<00:14:44.090> we<00:14:44.630> can<00:14:44.780> help 00:14:45.010 --> 00:14:45.020 align:start position:0% get an early on your problem we can help 00:14:45.020 --> 00:14:47.530 align:start position:0% get an early on your problem we can help we're<00:14:45.650> working<00:14:45.980> on<00:14:46.100> this<00:14:46.580> one<00:14:46.820> click<00:14:47.270> set<00:14:47.510> up 00:14:47.530 --> 00:14:47.540 align:start position:0% we're working on this one click set up 00:14:47.540 --> 00:14:49.420 align:start position:0% we're working on this one click set up template<00:14:48.050> for<00:14:48.260> protocols<00:14:48.680> so<00:14:49.070> if<00:14:49.160> you<00:14:49.250> go<00:14:49.400> to 00:14:49.420 --> 00:14:49.430 align:start position:0% template for protocols so if you go to 00:14:49.430 --> 00:14:51.940 align:start position:0% template for protocols so if you go to the<00:14:50.180> Oregon<00:14:50.420> app<00:14:50.690> you<00:14:51.320> see<00:14:51.440> these<00:14:51.530> templates 00:14:51.940 --> 00:14:51.950 align:start position:0% the Oregon app you see these templates 00:14:51.950 --> 00:14:54.580 align:start position:0% the Oregon app you see these templates that<00:14:52.160> you<00:14:52.310> can<00:14:52.520> just<00:14:53.180> click<00:14:53.480> on<00:14:53.780> and<00:14:54.020> then<00:14:54.290> feel 00:14:54.580 --> 00:14:54.590 align:start position:0% that you can just click on and then feel 00:14:54.590 --> 00:14:56.320 align:start position:0% that you can just click on and then feel like<00:14:54.620> a<00:14:54.890> bunch<00:14:55.070> of<00:14:55.250> text<00:14:55.670> fields<00:14:56.000> in<00:14:56.210> our 00:14:56.320 --> 00:14:56.330 align:start position:0% like a bunch of text fields in our 00:14:56.330 --> 00:14:58.270 align:start position:0% like a bunch of text fields in our beautiful<00:14:56.630> UI<00:14:56.930> click<00:14:57.680> create 00:14:58.270 --> 00:14:58.280 align:start position:0% beautiful UI click create 00:14:58.280 --> 00:15:01.210 align:start position:0% beautiful UI click create boom<00:14:59.030> done<00:14:59.750> if<00:15:00.560> you<00:15:00.710> want<00:15:00.830> something<00:15:01.070> more 00:15:01.210 --> 00:15:01.220 align:start position:0% boom done if you want something more 00:15:01.220 --> 00:15:03.190 align:start position:0% boom done if you want something more complex<00:15:01.670> there<00:15:01.910> are<00:15:01.940> like<00:15:02.120> CLI<00:15:02.630> like<00:15:02.900> command 00:15:03.190 --> 00:15:03.200 align:start position:0% complex there are like CLI like command 00:15:03.200 --> 00:15:04.870 align:start position:0% complex there are like CLI like command line<00:15:03.320> tools<00:15:03.650> that<00:15:03.950> are<00:15:04.040> like<00:15:04.220> an<00:15:04.310> their<00:15:04.640> second 00:15:04.870 --> 00:15:04.880 align:start position:0% line tools that are like an their second 00:15:04.880 --> 00:15:06.850 align:start position:0% line tools that are like an their second SDK<00:15:05.360> with<00:15:05.570> a<00:15:05.600> bunch<00:15:05.840> of<00:15:05.990> things<00:15:06.200> you<00:15:06.590> can 00:15:06.850 --> 00:15:06.860 align:start position:0% SDK with a bunch of things you can 00:15:06.860 --> 00:15:08.920 align:start position:0% SDK with a bunch of things you can really<00:15:07.160> get<00:15:07.310> crazy<00:15:07.550> with<00:15:07.820> it<00:15:07.850> but<00:15:08.510> if<00:15:08.630> you<00:15:08.720> want 00:15:08.920 --> 00:15:08.930 align:start position:0% really get crazy with it but if you want 00:15:08.930 --> 00:15:10.300 align:start position:0% really get crazy with it but if you want to<00:15:09.050> get<00:15:09.200> like<00:15:09.380> the<00:15:09.530> basic<00:15:09.980> basic<00:15:10.280> basic 00:15:10.300 --> 00:15:10.310 align:start position:0% to get like the basic basic basic 00:15:10.310 --> 00:15:13.300 align:start position:0% to get like the basic basic basic templates<00:15:11.030> is<00:15:11.330> it<00:15:11.840> really<00:15:12.080> like<00:15:12.170> graphic<00:15:13.040> like 00:15:13.300 --> 00:15:13.310 align:start position:0% templates is it really like graphic like 00:15:13.310 --> 00:15:14.740 align:start position:0% templates is it really like graphic like user<00:15:13.520> interface<00:15:13.910> I<00:15:14.090> don't<00:15:14.420> have<00:15:14.540> to<00:15:14.690> do 00:15:14.740 --> 00:15:14.750 align:start position:0% user interface I don't have to do 00:15:14.750 --> 00:15:16.030 align:start position:0% user interface I don't have to do anything<00:15:14.990> else<00:15:15.200> and<00:15:15.410> we're<00:15:15.650> working<00:15:15.950> on 00:15:16.030 --> 00:15:16.040 align:start position:0% anything else and we're working on 00:15:16.040 --> 00:15:18.430 align:start position:0% anything else and we're working on integrating<00:15:16.280> this<00:15:16.610> into<00:15:17.060> our<00:15:17.600> unlike<00:15:18.260> our<00:15:18.410> own 00:15:18.430 --> 00:15:18.440 align:start position:0% integrating this into our unlike our own 00:15:18.440 --> 00:15:20.260 align:start position:0% integrating this into our unlike our own client<00:15:18.890> so<00:15:19.430> in<00:15:19.490> the<00:15:19.550> future<00:15:19.730> you<00:15:19.910> will<00:15:20.030> be<00:15:20.150> able 00:15:20.260 --> 00:15:20.270 align:start position:0% client so in the future you will be able 00:15:20.270 --> 00:15:22.720 align:start position:0% client so in the future you will be able to<00:15:20.450> use<00:15:20.600> go<00:15:20.810> to<00:15:20.870> app<00:15:21.110> argument<00:15:21.800> org<00:15:21.980> select 00:15:22.720 --> 00:15:22.730 align:start position:0% to use go to app argument org select 00:15:22.730 --> 00:15:25.360 align:start position:0% to use go to app argument org select crypto<00:15:23.210> protocol<00:15:23.630> and<00:15:23.870> then<00:15:24.410> basically<00:15:24.920> you 00:15:25.360 --> 00:15:25.370 align:start position:0% crypto protocol and then basically you 00:15:25.370 --> 00:15:28.030 align:start position:0% crypto protocol and then basically you can<00:15:25.520> write<00:15:25.730> your<00:15:25.910> smart<00:15:26.270> contracts<00:15:27.040> which 00:15:28.030 --> 00:15:28.040 align:start position:0% can write your smart contracts which 00:15:28.040 --> 00:15:29.760 align:start position:0% can write your smart contracts which Apple<00:15:28.250> here<00:15:28.460> this<00:15:28.940> can<00:15:29.060> be<00:15:29.180> your<00:15:29.300> protocol 00:15:29.760 --> 00:15:29.770 align:start position:0% Apple here this can be your protocol 00:15:29.770 --> 00:15:31.960 align:start position:0% Apple here this can be your protocol like<00:15:30.770> on<00:15:31.040> the<00:15:31.190> on<00:15:31.310> the<00:15:31.430> left<00:15:31.580> side<00:15:31.730> of<00:15:31.850> the 00:15:31.960 --> 00:15:31.970 align:start position:0% like on the on the left side of the 00:15:31.970 --> 00:15:33.370 align:start position:0% like on the on the left side of the screen<00:15:32.210> you<00:15:32.690> can<00:15:32.720> write<00:15:33.020> your<00:15:33.170> smart 00:15:33.370 --> 00:15:33.380 align:start position:0% screen you can write your smart 00:15:33.380 --> 00:15:36.280 align:start position:0% screen you can write your smart contracts<00:15:33.920> you<00:15:34.580> know<00:15:34.700> as<00:15:34.790> much<00:15:35.290> flexibility 00:15:36.280 --> 00:15:36.290 align:start position:0% contracts you know as much flexibility 00:15:36.290 --> 00:15:37.550 align:start position:0% contracts you know as much flexibility as<00:15:36.380> you<00:15:36.650> want 00:15:37.550 --> 00:15:37.560 align:start position:0% as you want 00:15:37.560 --> 00:15:39.290 align:start position:0% as you want then<00:15:37.770> instead<00:15:38.370> of<00:15:38.460> like<00:15:38.640> putting<00:15:38.910> the<00:15:39.000> only 00:15:39.290 --> 00:15:39.300 align:start position:0% then instead of like putting the only 00:15:39.300 --> 00:15:42.040 align:start position:0% then instead of like putting the only owner<00:15:39.420> to<00:15:39.690> your<00:15:39.810> account<00:15:40.290> or<00:15:41.100> your<00:15:41.430> company's 00:15:42.040 --> 00:15:42.050 align:start position:0% owner to your account or your company's 00:15:42.050 --> 00:15:45.470 align:start position:0% owner to your account or your company's sir<00:15:43.080> let<00:15:43.590> your<00:15:43.800> treasure<00:15:44.250> or<00:15:44.340> whatever<00:15:44.580> what 00:15:45.470 --> 00:15:45.480 align:start position:0% sir let your treasure or whatever what 00:15:45.480 --> 00:15:47.630 align:start position:0% sir let your treasure or whatever what you<00:15:45.510> can<00:15:45.720> do<00:15:45.870> is<00:15:46.110> put<00:15:46.350> the<00:15:46.440> only<00:15:46.740> owner<00:15:46.890> to<00:15:47.340> the 00:15:47.630 --> 00:15:47.640 align:start position:0% you can do is put the only owner to the 00:15:47.640 --> 00:15:49.640 align:start position:0% you can do is put the only owner to the alien<00:15:48.000> tap<00:15:48.210> in<00:15:48.630> the<00:15:48.810> Dow<00:15:48.930> and<00:15:49.230> so<00:15:49.380> basically 00:15:49.640 --> 00:15:49.650 align:start position:0% alien tap in the Dow and so basically 00:15:49.650 --> 00:15:51.950 align:start position:0% alien tap in the Dow and so basically everything<00:15:50.040> to<00:15:50.130> the<00:15:50.190> right<00:15:50.220> is<00:15:50.760> the<00:15:51.150> Dow<00:15:51.300> so 00:15:51.950 --> 00:15:51.960 align:start position:0% everything to the right is the Dow so 00:15:51.960 --> 00:15:54.050 align:start position:0% everything to the right is the Dow so that<00:15:52.080> I<00:15:52.170> can<00:15:52.350> have<00:15:52.500> multiple<00:15:52.980> apps<00:15:53.160> the<00:15:53.760> voting 00:15:54.050 --> 00:15:54.060 align:start position:0% that I can have multiple apps the voting 00:15:54.060 --> 00:15:55.940 align:start position:0% that I can have multiple apps the voting app<00:15:54.210> the<00:15:54.810> finance<00:15:55.140> that<00:15:55.290> allows<00:15:55.589> your<00:15:55.740> doubt 00:15:55.940 --> 00:15:55.950 align:start position:0% app the finance that allows your doubt 00:15:55.950 --> 00:15:58.250 align:start position:0% app the finance that allows your doubt to<00:15:56.100> have<00:15:56.279> money<00:15:56.490> you<00:15:56.820> can<00:15:57.660> get<00:15:57.930> really<00:15:58.080> crazy 00:15:58.250 --> 00:15:58.260 align:start position:0% to have money you can get really crazy 00:15:58.260 --> 00:16:00.050 align:start position:0% to have money you can get really crazy with<00:15:58.470> permissions<00:15:59.010> so<00:15:59.250> for<00:15:59.370> example<00:15:59.760> you<00:15:59.910> can 00:16:00.050 --> 00:16:00.060 align:start position:0% with permissions so for example you can 00:16:00.060 --> 00:16:02.360 align:start position:0% with permissions so for example you can you<00:16:00.870> can<00:16:01.050> give<00:16:01.170> a<00:16:01.200> boring<00:16:01.560> app<00:16:01.710> to<00:16:01.980> get<00:16:02.130> money 00:16:02.360 --> 00:16:02.370 align:start position:0% you can give a boring app to get money 00:16:02.370 --> 00:16:04.220 align:start position:0% you can give a boring app to get money out<00:16:02.490> of<00:16:02.580> the<00:16:02.760> finance<00:16:03.089> app<00:16:03.330> so<00:16:03.870> you<00:16:03.960> can<00:16:03.990> even 00:16:04.220 --> 00:16:04.230 align:start position:0% out of the finance app so you can even 00:16:04.230 --> 00:16:06.410 align:start position:0% out of the finance app so you can even have<00:16:04.470> like<00:16:04.710> a<00:16:04.740> protocol<00:16:05.160> reward<00:16:05.550> out<00:16:05.790> in<00:16:06.210> which 00:16:06.410 --> 00:16:06.420 align:start position:0% have like a protocol reward out in which 00:16:06.420 --> 00:16:09.200 align:start position:0% have like a protocol reward out in which like<00:16:06.600> you<00:16:06.810> know<00:16:06.900> each<00:16:07.020> block<00:16:07.320> or<00:16:08.160> the<00:16:08.580> H<00:16:08.850> worker 00:16:09.200 --> 00:16:09.210 align:start position:0% like you know each block or the H worker 00:16:09.210 --> 00:16:10.730 align:start position:0% like you know each block or the H worker like<00:16:09.330> you<00:16:09.390> know<00:16:09.570> its<00:16:09.779> period<00:16:10.230> of<00:16:10.290> time<00:16:10.500> there's 00:16:10.730 --> 00:16:10.740 align:start position:0% like you know its period of time there's 00:16:10.740 --> 00:16:13.430 align:start position:0% like you know its period of time there's a<00:16:10.800> new<00:16:11.240> talking<00:16:12.240> created<00:16:12.839> that<00:16:13.050> goes<00:16:13.260> into 00:16:13.430 --> 00:16:13.440 align:start position:0% a new talking created that goes into 00:16:13.440 --> 00:16:16.280 align:start position:0% a new talking created that goes into this<00:16:13.680> finance<00:16:14.550> I<00:16:14.700> pinned<00:16:15.120> it<00:16:15.240> down<00:16:15.270> and<00:16:15.690> then 00:16:16.280 --> 00:16:16.290 align:start position:0% this finance I pinned it down and then 00:16:16.290 --> 00:16:18.230 align:start position:0% this finance I pinned it down and then token<00:16:16.770> holders<00:16:17.220> can<00:16:17.400> use<00:16:17.520> the<00:16:17.640> boring<00:16:17.910> app<00:16:18.060> to 00:16:18.230 --> 00:16:18.240 align:start position:0% token holders can use the boring app to 00:16:18.240 --> 00:16:20.000 align:start position:0% token holders can use the boring app to decide<00:16:18.540> how<00:16:18.690> to<00:16:18.750> spend<00:16:18.930> those<00:16:19.350> funds<00:16:19.710> from 00:16:20.000 --> 00:16:20.010 align:start position:0% decide how to spend those funds from 00:16:20.010 --> 00:16:22.490 align:start position:0% decide how to spend those funds from protocol<00:16:20.279> development<00:16:20.990> but<00:16:21.990> then<00:16:22.080> we<00:16:22.170> created 00:16:22.490 --> 00:16:22.500 align:start position:0% protocol development but then we created 00:16:22.500 --> 00:16:24.829 align:start position:0% protocol development but then we created this<00:16:22.620> app<00:16:22.980> called<00:16:23.460> agent<00:16:23.910> inside<00:16:24.300> Oregon<00:16:24.690> an 00:16:24.829 --> 00:16:24.839 align:start position:0% this app called agent inside Oregon an 00:16:24.839 --> 00:16:28.310 align:start position:0% this app called agent inside Oregon an agent<00:16:25.320> is<00:16:25.470> basically<00:16:25.890> the<00:16:26.670> the<00:16:27.120> dowels<00:16:27.630> face 00:16:28.310 --> 00:16:28.320 align:start position:0% agent is basically the the dowels face 00:16:28.320 --> 00:16:31.100 align:start position:0% agent is basically the the dowels face to<00:16:28.770> the<00:16:28.800> world<00:16:29.040> to<00:16:29.580> the<00:16:29.610> worth<00:16:29.850> 3<00:16:30.029> world<00:16:30.240> and<00:16:30.480> so 00:16:31.100 --> 00:16:31.110 align:start position:0% to the world to the worth 3 world and so 00:16:31.110 --> 00:16:33.380 align:start position:0% to the world to the worth 3 world and so what<00:16:31.290> I<00:16:31.410> am<00:16:31.440> tell<00:16:32.250> us<00:16:32.400> is<00:16:32.730> furthered<00:16:33.029> out<00:16:33.150> to 00:16:33.380 --> 00:16:33.390 align:start position:0% what I am tell us is furthered out to 00:16:33.390 --> 00:16:35.570 align:start position:0% what I am tell us is furthered out to interoperate<00:16:33.839> with<00:16:34.110> any<00:16:34.500> worklet<00:16:35.190> protocols 00:16:35.570 --> 00:16:35.580 align:start position:0% interoperate with any worklet protocols 00:16:35.580 --> 00:16:37.760 align:start position:0% interoperate with any worklet protocols so<00:16:36.330> thou<00:16:36.540> may<00:16:36.750> be<00:16:36.810> able<00:16:36.960> to<00:16:37.080> open<00:16:37.350> and<00:16:37.589> see<00:16:37.650> if 00:16:37.760 --> 00:16:37.770 align:start position:0% so thou may be able to open and see if 00:16:37.770 --> 00:16:39.560 align:start position:0% so thou may be able to open and see if your<00:16:37.920> maker<00:16:38.130> that<00:16:38.640> I<00:16:38.760> may<00:16:38.910> be<00:16:38.970> able<00:16:39.150> to<00:16:39.270> lend 00:16:39.560 --> 00:16:39.570 align:start position:0% your maker that I may be able to lend 00:16:39.570 --> 00:16:41.300 align:start position:0% your maker that I may be able to lend money<00:16:39.720> on<00:16:39.900> compound<00:16:40.380> all<00:16:40.650> of<00:16:40.920> those<00:16:41.040> things 00:16:41.300 --> 00:16:41.310 align:start position:0% money on compound all of those things 00:16:41.310 --> 00:16:43.550 align:start position:0% money on compound all of those things and<00:16:41.670> the<00:16:42.030> cool<00:16:42.150> thing<00:16:42.300> here<00:16:42.330> is<00:16:42.720> you<00:16:43.380> don't 00:16:43.550 --> 00:16:43.560 align:start position:0% and the cool thing here is you don't 00:16:43.560 --> 00:16:45.350 align:start position:0% and the cool thing here is you don't need<00:16:43.680> to<00:16:43.800> get<00:16:43.920> into<00:16:44.070> our<00:16:44.310> SDK<00:16:44.880> to<00:16:44.940> use<00:16:45.180> this 00:16:45.350 --> 00:16:45.360 align:start position:0% need to get into our SDK to use this 00:16:45.360 --> 00:16:46.940 align:start position:0% need to get into our SDK to use this like<00:16:45.750> you<00:16:45.870> just<00:16:45.990> basically<00:16:46.200> have<00:16:46.560> to<00:16:46.710> create<00:16:46.890> a 00:16:46.940 --> 00:16:46.950 align:start position:0% like you just basically have to create a 00:16:46.950 --> 00:16:49.490 align:start position:0% like you just basically have to create a protocol<00:16:47.370> whatever<00:16:47.880> way<00:16:48.330> you<00:16:48.390> want<00:16:48.660> and<00:16:48.870> then 00:16:49.490 --> 00:16:49.500 align:start position:0% protocol whatever way you want and then 00:16:49.500 --> 00:16:51.470 align:start position:0% protocol whatever way you want and then put<00:16:49.680> the<00:16:49.800> address<00:16:50.070> of<00:16:50.310> this<00:16:50.460> am<00:16:50.820> tab<00:16:51.000> as<00:16:51.240> the 00:16:51.470 --> 00:16:51.480 align:start position:0% put the address of this am tab as the 00:16:51.480 --> 00:16:54.410 align:start position:0% put the address of this am tab as the only<00:16:51.750> owner<00:16:51.900> and<00:16:52.230> that<00:16:52.740> will<00:16:52.860> basically<00:16:53.420> make 00:16:54.410 --> 00:16:54.420 align:start position:0% only owner and that will basically make 00:16:54.420 --> 00:16:57.230 align:start position:0% only owner and that will basically make your<00:16:54.540> protocol<00:16:54.990> be<00:16:55.140> governed<00:16:55.620> by<00:16:55.650> now<00:16:56.240> it's 00:16:57.230 --> 00:16:57.240 align:start position:0% your protocol be governed by now it's 00:16:57.240 --> 00:16:59.200 align:start position:0% your protocol be governed by now it's that<00:16:57.450> easy 00:16:59.200 --> 00:16:59.210 align:start position:0% that easy 00:16:59.210 --> 00:17:02.780 align:start position:0% that easy so<00:17:00.210> I<00:17:00.450> think<00:17:00.990> as<00:17:01.170> a<00:17:01.200> summary<00:17:01.560> like<00:17:01.620> Dow's<00:17:02.430> make 00:17:02.780 --> 00:17:02.790 align:start position:0% so I think as a summary like Dow's make 00:17:02.790 --> 00:17:06.319 align:start position:0% so I think as a summary like Dow's make defy<00:17:03.210> to<00:17:03.270> serve<00:17:03.630> the<00:17:03.900> D<00:17:04.380> I<00:17:05.150> think<00:17:06.150> I<00:17:06.179> think 00:17:06.319 --> 00:17:06.329 align:start position:0% defy to serve the D I think I think 00:17:06.329 --> 00:17:07.069 align:start position:0% defy to serve the D I think I think right<00:17:06.449> now<00:17:06.480> we're<00:17:06.689> in<00:17:06.750> the<00:17:06.810> process<00:17:06.870> of 00:17:07.069 --> 00:17:07.079 align:start position:0% right now we're in the process of 00:17:07.079 --> 00:17:08.750 align:start position:0% right now we're in the process of actually<00:17:07.319> making<00:17:07.679> sure<00:17:08.160> that<00:17:08.280> if<00:17:08.429> I<00:17:08.579> actually 00:17:08.750 --> 00:17:08.760 align:start position:0% actually making sure that if I actually 00:17:08.760 --> 00:17:10.309 align:start position:0% actually making sure that if I actually deserve<00:17:09.179> that<00:17:09.420> I<00:17:09.600> think<00:17:09.839> it's<00:17:09.959> more<00:17:10.050> like<00:17:10.199> see 00:17:10.309 --> 00:17:10.319 align:start position:0% deserve that I think it's more like see 00:17:10.319 --> 00:17:12.260 align:start position:0% deserve that I think it's more like see if<00:17:10.380> I<00:17:10.470> today<00:17:10.709> I<00:17:10.949> think<00:17:11.490> everyone<00:17:11.970> else<00:17:12.060> are 00:17:12.260 --> 00:17:12.270 align:start position:0% if I today I think everyone else are 00:17:12.270 --> 00:17:13.520 align:start position:0% if I today I think everyone else are very<00:17:12.480> easy<00:17:12.660> to<00:17:12.810> deploy<00:17:12.929> you<00:17:13.140> can<00:17:13.350> literally 00:17:13.520 --> 00:17:13.530 align:start position:0% very easy to deploy you can literally 00:17:13.530 --> 00:17:15.679 align:start position:0% very easy to deploy you can literally blow<00:17:13.829> them<00:17:13.980> in<00:17:14.069> like<00:17:14.189> 30<00:17:14.400> seconds<00:17:14.819> they<00:17:15.660> are 00:17:15.679 --> 00:17:15.689 align:start position:0% blow them in like 30 seconds they are 00:17:15.689 --> 00:17:17.390 align:start position:0% blow them in like 30 seconds they are working<00:17:15.990> canisters<00:17:16.560> from<00:17:16.800> maintenance<00:17:17.040> like 00:17:17.390 --> 00:17:17.400 align:start position:0% working canisters from maintenance like 00:17:17.400 --> 00:17:19.640 align:start position:0% working canisters from maintenance like the<00:17:17.490> one<00:17:17.640> that<00:17:17.760> I<00:17:17.819> mentioned<00:17:17.939> from<00:17:18.410> from<00:17:19.410> melon 00:17:19.640 --> 00:17:19.650 align:start position:0% the one that I mentioned from from melon 00:17:19.650 --> 00:17:21.140 align:start position:0% the one that I mentioned from from melon protocol<00:17:20.040> if<00:17:20.189> you<00:17:20.310> go<00:17:20.459> to<00:17:20.520> the<00:17:20.760> Argonne 00:17:21.140 --> 00:17:21.150 align:start position:0% protocol if you go to the Argonne 00:17:21.150 --> 00:17:22.850 align:start position:0% protocol if you go to the Argonne website<00:17:21.569> there's<00:17:21.929> a<00:17:21.959> case<00:17:22.079> live<00:17:22.260> so<00:17:22.470> with<00:17:22.679> most 00:17:22.850 --> 00:17:22.860 align:start position:0% website there's a case live so with most 00:17:22.860 --> 00:17:25.460 align:start position:0% website there's a case live so with most depot<00:17:23.130> maintenance<00:17:23.160> cases<00:17:23.880> today<00:17:24.140> and<00:17:25.140> we're 00:17:25.460 --> 00:17:25.470 align:start position:0% depot maintenance cases today and we're 00:17:25.470 --> 00:17:26.720 align:start position:0% depot maintenance cases today and we're working<00:17:25.589> on<00:17:25.740> this<00:17:25.829> one<00:17:25.949> click<00:17:26.160> setup<00:17:26.339> template 00:17:26.720 --> 00:17:26.730 align:start position:0% working on this one click setup template 00:17:26.730 --> 00:17:30.290 align:start position:0% working on this one click setup template that<00:17:26.880> will<00:17:27.060> make<00:17:27.270> things<00:17:27.390> way<00:17:27.780> way<00:17:27.959> easier<00:17:29.300> so 00:17:30.290 --> 00:17:30.300 align:start position:0% that will make things way way easier so 00:17:30.300 --> 00:17:32.720 align:start position:0% that will make things way way easier so I<00:17:30.660> said<00:17:31.320> before<00:17:31.410> like<00:17:31.710> we<00:17:32.220> have<00:17:32.370> a<00:17:32.400> bunch<00:17:32.580> of 00:17:32.720 --> 00:17:32.730 align:start position:0% I said before like we have a bunch of 00:17:32.730 --> 00:17:33.800 align:start position:0% I said before like we have a bunch of those<00:17:32.910> now<00:17:33.210> mainly 00:17:33.800 --> 00:17:33.810 align:start position:0% those now mainly 00:17:33.810 --> 00:17:35.300 align:start position:0% those now mainly I<00:17:33.960> think<00:17:34.230> it<00:17:34.320> year<00:17:34.530> ago<00:17:34.710> technology<00:17:34.890> was<00:17:35.280> very 00:17:35.300 --> 00:17:35.310 align:start position:0% I think it year ago technology was very 00:17:35.310 --> 00:17:36.770 align:start position:0% I think it year ago technology was very early<00:17:35.700> I<00:17:35.730> think<00:17:35.820> now<00:17:36.090> we<00:17:36.150> are<00:17:36.300> getting<00:17:36.600> there 00:17:36.770 --> 00:17:36.780 align:start position:0% early I think now we are getting there 00:17:36.780 --> 00:17:40.250 align:start position:0% early I think now we are getting there so<00:17:37.320> more<00:17:37.740> than<00:17:37.830> 700,000<00:17:38.820> minute<00:17:39.179> today<00:17:39.420> you 00:17:40.250 --> 00:17:40.260 align:start position:0% so more than 700,000 minute today you 00:17:40.260 --> 00:17:42.400 align:start position:0% so more than 700,000 minute today you can<00:17:40.410> create<00:17:40.620> yours<00:17:40.890> a<00:17:41.100> tablet<00:17:41.550> argument<00:17:42.030> or 00:17:42.400 --> 00:17:42.410 align:start position:0% can create yours a tablet argument or 00:17:42.410 --> 00:17:45.110 align:start position:0% can create yours a tablet argument or various<00:17:43.410> for<00:17:43.800> like<00:17:43.920> 30<00:17:44.130> seconds<00:17:44.520> we<00:17:45.090> just 00:17:45.110 --> 00:17:45.120 align:start position:0% various for like 30 seconds we just 00:17:45.120 --> 00:17:46.820 align:start position:0% various for like 30 seconds we just released<00:17:45.540> a<00:17:45.600> new<00:17:45.720> version<00:17:45.870> two<00:17:46.200> weeks<00:17:46.350> ago<00:17:46.590> or 00:17:46.820 --> 00:17:46.830 align:start position:0% released a new version two weeks ago or 00:17:46.830 --> 00:17:48.680 align:start position:0% released a new version two weeks ago or three<00:17:46.980> weeks<00:17:47.130> ago<00:17:47.190> that<00:17:47.520> makes<00:17:48.090> the<00:17:48.540> user 00:17:48.680 --> 00:17:48.690 align:start position:0% three weeks ago that makes the user 00:17:48.690 --> 00:17:51.120 align:start position:0% three weeks ago that makes the user experience<00:17:49.040> much<00:17:50.040> better<00:17:50.070> I<00:17:50.429> think<00:17:50.760> we're<00:17:50.880> gay 00:17:51.120 --> 00:17:51.130 align:start position:0% experience much better I think we're gay 00:17:51.130 --> 00:17:53.190 align:start position:0% experience much better I think we're gay they're<00:17:51.370> like<00:17:51.610> we<00:17:51.730> are<00:17:52.090> slowly<00:17:52.600> making<00:17:52.930> sure 00:17:53.190 --> 00:17:53.200 align:start position:0% they're like we are slowly making sure 00:17:53.200 --> 00:17:55.490 align:start position:0% they're like we are slowly making sure that<00:17:53.410> is<00:17:53.560> comparable<00:17:53.980> to<00:17:54.070> web<00:17:54.580> to<00:17:54.730> experiences 00:17:55.490 --> 00:17:55.500 align:start position:0% that is comparable to web to experiences 00:17:55.500 --> 00:17:57.870 align:start position:0% that is comparable to web to experiences in<00:17:56.500> terms<00:17:56.560> of<00:17:56.860> user<00:17:56.980> experience<00:17:57.100> so<00:17:57.610> I'm<00:17:57.760> very 00:17:57.870 --> 00:17:57.880 align:start position:0% in terms of user experience so I'm very 00:17:57.880 --> 00:17:59.850 align:start position:0% in terms of user experience so I'm very happy<00:17:58.030> about<00:17:58.210> that<00:17:58.300> and<00:17:58.630> I<00:17:59.380> just<00:17:59.440> wanna<00:17:59.650> thank 00:17:59.850 --> 00:17:59.860 align:start position:0% happy about that and I just wanna thank 00:17:59.860 --> 00:18:01.680 align:start position:0% happy about that and I just wanna thank everyone<00:18:00.160> you<00:18:00.490> can<00:18:00.670> follow<00:18:00.880> Aragon<00:18:01.600> on 00:18:01.680 --> 00:18:01.690 align:start position:0% everyone you can follow Aragon on 00:18:01.690 --> 00:18:03.300 align:start position:0% everyone you can follow Aragon on Twitter<00:18:01.900> you<00:18:02.200> can<00:18:02.290> follow<00:18:02.440> me<00:18:02.590> on<00:18:02.650> Twitter<00:18:02.950> if 00:18:03.300 --> 00:18:03.310 align:start position:0% Twitter you can follow me on Twitter if 00:18:03.310 --> 00:18:04.800 align:start position:0% Twitter you can follow me on Twitter if you're<00:18:03.520> interested<00:18:04.030> in<00:18:04.180> these<00:18:04.270> challenges 00:18:04.800 --> 00:18:04.810 align:start position:0% you're interested in these challenges 00:18:04.810 --> 00:18:07.170 align:start position:0% you're interested in these challenges the<00:18:05.620> company<00:18:06.250> that<00:18:06.370> I<00:18:06.400> worked<00:18:06.640> for<00:18:06.760> arguing 00:18:07.170 --> 00:18:07.180 align:start position:0% the company that I worked for arguing 00:18:07.180 --> 00:18:09.600 align:start position:0% the company that I worked for arguing one<00:18:07.360> we're<00:18:07.600> hiding<00:18:08.250> much<00:18:09.250> of<00:18:09.400> roles 00:18:09.600 --> 00:18:09.610 align:start position:0% one we're hiding much of roles 00:18:09.610 --> 00:18:11.460 align:start position:0% one we're hiding much of roles especially<00:18:10.150> fronting<00:18:10.720> people<00:18:11.020> just<00:18:11.230> really 00:18:11.460 --> 00:18:11.470 align:start position:0% especially fronting people just really 00:18:11.470 --> 00:18:12.870 align:start position:0% especially fronting people just really care<00:18:11.770> about<00:18:11.920> designing<00:18:12.400> we<00:18:12.550> really<00:18:12.760> care 00:18:12.870 --> 00:18:12.880 align:start position:0% care about designing we really care 00:18:12.880 --> 00:18:14.220 align:start position:0% care about designing we really care about<00:18:12.910> bringing<00:18:13.330> these<00:18:13.480> two<00:18:13.660> people<00:18:14.050> that 00:18:14.220 --> 00:18:14.230 align:start position:0% about bringing these two people that 00:18:14.230 --> 00:18:16.230 align:start position:0% about bringing these two people that actually<00:18:14.410> need<00:18:14.740> it<00:18:14.920> so<00:18:15.430> you<00:18:15.550> go<00:18:15.700> to<00:18:15.820> Aragon<00:18:16.180> but 00:18:16.230 --> 00:18:16.240 align:start position:0% actually need it so you go to Aragon but 00:18:16.240 --> 00:18:17.910 align:start position:0% actually need it so you go to Aragon but one<00:18:16.450> it's<00:18:16.600> less<00:18:16.720> jobs<00:18:16.960> and<00:18:17.170> also<00:18:17.740> you<00:18:17.830> can 00:18:17.910 --> 00:18:17.920 align:start position:0% one it's less jobs and also you can 00:18:17.920 --> 00:18:20.510 align:start position:0% one it's less jobs and also you can check<00:18:18.040> out<00:18:18.130> their<00:18:18.250> own<00:18:18.460> website<00:18:18.760> so<00:18:19.210> thanks 00:18:20.510 --> 00:18:20.520 align:start position:0% check out their own website so thanks 00:18:20.520 --> 00:18:25.310 align:start position:0% check out their own website so thanks [Applause] 00:18:25.310 --> 00:18:25.320 align:start position:0% [Applause] 00:18:25.320 --> 00:18:27.930 align:start position:0% [Applause] and<00:18:26.320> actually<00:18:26.770> have<00:18:26.920> two<00:18:27.490> more<00:18:27.520> things<00:18:27.760> for 00:18:27.930 --> 00:18:27.940 align:start position:0% and actually have two more things for 00:18:27.940 --> 00:18:30.690 align:start position:0% and actually have two more things for today<00:18:28.090> so<00:18:28.690> one<00:18:29.020> of<00:18:29.050> them<00:18:29.260> is<00:18:29.500> I<00:18:30.160> reckon<00:18:30.610> is 00:18:30.690 --> 00:18:30.700 align:start position:0% today so one of them is I reckon is 00:18:30.700 --> 00:18:31.440 align:start position:0% today so one of them is I reckon is gonna<00:18:30.880> be<00:18:30.970> released<00:18:31.120> in<00:18:31.360> a<00:18:31.420> couple 00:18:31.440 --> 00:18:31.450 align:start position:0% gonna be released in a couple 00:18:31.450 --> 00:18:34.380 align:start position:0% gonna be released in a couple interesting<00:18:32.080> news<00:18:32.800> later<00:18:33.160> today<00:18:33.340> about<00:18:34.120> a 00:18:34.380 --> 00:18:34.390 align:start position:0% interesting news later today about a 00:18:34.390 --> 00:18:36.420 align:start position:0% interesting news later today about a couple<00:18:34.750> community<00:18:35.290> developments<00:18:36.250> that<00:18:36.340> are 00:18:36.420 --> 00:18:36.430 align:start position:0% couple community developments that are 00:18:36.430 --> 00:18:39.270 align:start position:0% couple community developments that are going<00:18:36.460> on<00:18:36.700> so<00:18:37.140> instead<00:18:38.140> a<00:18:38.350> stay<00:18:38.500> tuned<00:18:38.740> for<00:18:39.010> the 00:18:39.270 --> 00:18:39.280 align:start position:0% going on so instead a stay tuned for the 00:18:39.280 --> 00:18:42.090 align:start position:0% going on so instead a stay tuned for the era<00:18:40.030> news<00:18:40.360> during<00:18:40.780> the<00:18:40.900> day<00:18:41.050> and<00:18:41.260> then<00:18:42.010> a 00:18:42.090 --> 00:18:42.100 align:start position:0% era news during the day and then a 00:18:42.100 --> 00:18:44.850 align:start position:0% era news during the day and then a second<00:18:42.370> one<00:18:42.520> is<00:18:42.760> we<00:18:43.540> are<00:18:43.570> throwing<00:18:44.230> a<00:18:44.620> party 00:18:44.850 --> 00:18:44.860 align:start position:0% second one is we are throwing a party 00:18:44.860 --> 00:18:47.310 align:start position:0% second one is we are throwing a party and<00:18:45.190> so<00:18:45.610> we<00:18:45.730> are<00:18:45.820> throwing<00:18:46.000> a<00:18:46.240> doll<00:18:46.630> party<00:18:47.020> the 00:18:47.310 --> 00:18:47.320 align:start position:0% and so we are throwing a doll party the 00:18:47.320 --> 00:18:48.960 align:start position:0% and so we are throwing a doll party the equidistance<00:18:48.010> basically<00:18:48.430> focusing<00:18:48.820> on<00:18:48.850> the 00:18:48.960 --> 00:18:48.970 align:start position:0% equidistance basically focusing on the 00:18:48.970 --> 00:18:51.540 align:start position:0% equidistance basically focusing on the dico<00:18:49.360> model<00:18:49.690> and<00:18:49.870> the<00:18:50.380> upcoming<00:18:51.100> launch<00:18:51.460> of 00:18:51.540 --> 00:18:51.550 align:start position:0% dico model and the upcoming launch of 00:18:51.550 --> 00:18:53.760 align:start position:0% dico model and the upcoming launch of Aragon's<00:18:52.270> and<00:18:52.450> racing<00:18:52.750> that<00:18:52.870> would<00:18:53.020> allow<00:18:53.230> any 00:18:53.760 --> 00:18:53.770 align:start position:0% Aragon's and racing that would allow any 00:18:53.770 --> 00:18:55.050 align:start position:0% Aragon's and racing that would allow any dau<00:18:54.040> in<00:18:54.190> the<00:18:54.280> world<00:18:54.460> to<00:18:54.670> find<00:18:54.880> resolution 00:18:55.050 --> 00:18:55.060 align:start position:0% dau in the world to find resolution 00:18:55.060 --> 00:18:57.690 align:start position:0% dau in the world to find resolution bonding<00:18:55.660> parts<00:18:55.930> so<00:18:56.530> it's<00:18:56.920> very<00:18:57.160> cool<00:18:57.400> we're 00:18:57.690 --> 00:18:57.700 align:start position:0% bonding parts so it's very cool we're 00:18:57.700 --> 00:19:00.030 align:start position:0% bonding parts so it's very cool we're gonna<00:18:57.760> have<00:18:58.060> we're<00:18:58.900> gonna<00:18:58.990> have<00:18:59.110> actual<00:18:59.680> like 00:19:00.030 --> 00:19:00.040 align:start position:0% gonna have we're gonna have actual like 00:19:00.040 --> 00:19:02.460 align:start position:0% gonna have we're gonna have actual like sushi<00:19:00.640> there<00:19:01.120> for<00:19:01.870> the<00:19:01.960> first<00:19:02.110> people<00:19:02.350> that 00:19:02.460 --> 00:19:02.470 align:start position:0% sushi there for the first people that 00:19:02.470 --> 00:19:04.590 align:start position:0% sushi there for the first people that arrive<00:19:02.680> not<00:19:03.340> like<00:19:03.520> party<00:19:03.910> finger<00:19:04.120> food<00:19:04.300> some 00:19:04.590 --> 00:19:04.600 align:start position:0% arrive not like party finger food some 00:19:04.600 --> 00:19:07.020 align:start position:0% arrive not like party finger food some rehabilitate<00:19:05.140> and<00:19:05.920> I<00:19:06.040> invite<00:19:06.610> everyone<00:19:06.910> to 00:19:07.020 --> 00:19:07.030 align:start position:0% rehabilitate and I invite everyone to 00:19:07.030 --> 00:19:10.410 align:start position:0% rehabilitate and I invite everyone to use<00:19:07.300> sign<00:19:08.260> up<00:19:08.440> you<00:19:08.830> can<00:19:08.860> RSVP<00:19:09.280> just<00:19:10.150> go<00:19:10.300> into 00:19:10.410 --> 00:19:10.420 align:start position:0% use sign up you can RSVP just go into 00:19:10.420 --> 00:19:11.940 align:start position:0% use sign up you can RSVP just go into Oregon's<00:19:10.900> Twitter<00:19:11.140> and<00:19:11.410> there<00:19:11.590> is<00:19:11.680> a<00:19:11.710> link 00:19:11.940 --> 00:19:11.950 align:start position:0% Oregon's Twitter and there is a link 00:19:11.950 --> 00:19:13.890 align:start position:0% Oregon's Twitter and there is a link there<00:19:12.010> so<00:19:12.360> see<00:19:13.360> you<00:19:13.450> later 00:19:13.890 --> 00:19:13.900 align:start position:0% there so see you later 00:19:13.900 --> 00:19:16.350 align:start position:0% there so see you later and<00:19:14.140> how<00:19:14.350> we<00:19:14.470> can<00:19:14.620> enjoy<00:19:14.830> some<00:19:14.860> sushi<00:19:15.370> and<00:19:15.580> dial 00:19:16.350 --> 00:19:16.360 align:start position:0% and how we can enjoy some sushi and dial 00:19:16.360 --> 00:19:18.250 align:start position:0% and how we can enjoy some sushi and dial conversations<00:19:16.930> thank<00:19:17.410> you 00:19:18.250 --> 00:19:18.260 align:start position:0% conversations thank you 00:19:18.260 --> 00:19:27.700 align:start position:0% conversations thank you [Applause] 00:19:27.700 --> 00:19:27.710 align:start position:0% 00:19:27.710 --> 00:19:29.770 align:start position:0% you