WEBVTT Kind: captions Language: en 00:00:12.339 --> 00:00:16.119 align:start position:0% I'm<00:00:13.339> honored<00:00:13.700> to<00:00:13.879> be<00:00:13.969> here<00:00:14.409> i'm<00:00:15.409> jordan<00:00:15.860> valina 00:00:16.119 --> 00:00:16.129 align:start position:0% I'm honored to be here i'm jordan valina 00:00:16.129 --> 00:00:18.430 align:start position:0% I'm honored to be here i'm jordan valina I'm<00:00:16.430> a<00:00:16.640> developer<00:00:17.090> and<00:00:17.360> answering<00:00:17.900> fan<00:00:18.140> and 00:00:18.430 --> 00:00:18.440 align:start position:0% I'm a developer and answering fan and 00:00:18.440 --> 00:00:22.300 align:start position:0% I'm a developer and answering fan and founder<00:00:19.190> of<00:00:19.220> givethe<00:00:20.860> I'm<00:00:21.860> a<00:00:21.920> little 00:00:22.300 --> 00:00:22.310 align:start position:0% founder of givethe I'm a little 00:00:22.310 --> 00:00:24.730 align:start position:0% founder of givethe I'm a little distracted<00:00:22.850> today<00:00:22.880> because<00:00:23.750> just<00:00:23.780> now<00:00:24.410> in 00:00:24.730 --> 00:00:24.740 align:start position:0% distracted today because just now in 00:00:24.740 --> 00:00:27.100 align:start position:0% distracted today because just now in Catalonia<00:00:25.340> there<00:00:25.550> were<00:00:25.790> eight<00:00:26.210> members<00:00:26.750> of<00:00:26.960> my 00:00:27.100 --> 00:00:27.110 align:start position:0% Catalonia there were eight members of my 00:00:27.110 --> 00:00:29.200 align:start position:0% Catalonia there were eight members of my government<00:00:27.290> detain<00:00:28.280> it<00:00:28.490> for<00:00:28.700> defending 00:00:29.200 --> 00:00:29.210 align:start position:0% government detain it for defending 00:00:29.210 --> 00:00:31.930 align:start position:0% government detain it for defending democracy<00:00:29.330> and<00:00:29.990> my<00:00:30.200> people<00:00:30.590> right<00:00:31.580> of 00:00:31.930 --> 00:00:31.940 align:start position:0% democracy and my people right of 00:00:31.940 --> 00:00:34.360 align:start position:0% democracy and my people right of self-determination<00:00:32.680> we<00:00:33.680> have<00:00:33.890> a<00:00:33.920> huge 00:00:34.360 --> 00:00:34.370 align:start position:0% self-determination we have a huge 00:00:34.370 --> 00:00:36.400 align:start position:0% self-determination we have a huge opportunity<00:00:34.579> to<00:00:35.300> bring<00:00:35.780> the<00:00:35.930> center<00:00:36.230> lights 00:00:36.400 --> 00:00:36.410 align:start position:0% opportunity to bring the center lights 00:00:36.410 --> 00:00:40.260 align:start position:0% opportunity to bring the center lights tools<00:00:37.220> -<00:00:38.060> dreaming<00:00:38.329> catalonia<00:00:38.990> we<00:00:39.410> need<00:00:39.590> it 00:00:40.260 --> 00:00:40.270 align:start position:0% tools - dreaming catalonia we need it 00:00:40.270 --> 00:00:43.840 align:start position:0% tools - dreaming catalonia we need it but<00:00:41.270> I'm<00:00:41.780> here<00:00:42.440> to<00:00:42.620> share<00:00:42.950> a<00:00:43.160> bit<00:00:43.640> of<00:00:43.670> my 00:00:43.840 --> 00:00:43.850 align:start position:0% but I'm here to share a bit of my 00:00:43.850 --> 00:00:47.410 align:start position:0% but I'm here to share a bit of my passion<00:00:44.480> for<00:00:44.660> smart<00:00:45.590> contracts<00:00:46.149> in<00:00:47.149> this 00:00:47.410 --> 00:00:47.420 align:start position:0% passion for smart contracts in this 00:00:47.420 --> 00:00:50.680 align:start position:0% passion for smart contracts in this presentation<00:00:47.870> I<00:00:48.320> will<00:00:48.710> first<00:00:49.310> talk<00:00:49.730> about<00:00:50.060> the 00:00:50.680 --> 00:00:50.690 align:start position:0% presentation I will first talk about the 00:00:50.690 --> 00:00:54.340 align:start position:0% presentation I will first talk about the mini-me<00:00:51.020> token<00:00:51.620> contract<00:00:52.130> then<00:00:53.120> give<00:00:53.930> you 00:00:54.340 --> 00:00:54.350 align:start position:0% mini-me token contract then give you 00:00:54.350 --> 00:00:57.250 align:start position:0% mini-me token contract then give you some<00:00:54.770> highlights<00:00:55.100> on<00:00:55.579> how<00:00:56.149> I<00:00:56.180> see<00:00:56.540> the<00:00:57.050> future 00:00:57.250 --> 00:00:57.260 align:start position:0% some highlights on how I see the future 00:00:57.260 --> 00:01:00.490 align:start position:0% some highlights on how I see the future of<00:00:57.680> token<00:00:58.250> contracts<00:00:58.730> and<00:00:59.030> finally<00:00:59.809> I<00:01:00.020> will 00:01:00.490 --> 00:01:00.500 align:start position:0% of token contracts and finally I will 00:01:00.500 --> 00:01:04.060 align:start position:0% of token contracts and finally I will briefly<00:01:00.770> introduce<00:01:01.180> my<00:01:02.180> latest<00:01:03.070> development 00:01:04.060 --> 00:01:04.070 align:start position:0% briefly introduce my latest development 00:01:04.070 --> 00:01:06.460 align:start position:0% briefly introduce my latest development the<00:01:04.729> liquid<00:01:05.089> pledging<00:01:05.479> contract<00:01:05.930> which<00:01:06.290> we 00:01:06.460 --> 00:01:06.470 align:start position:0% the liquid pledging contract which we 00:01:06.470 --> 00:01:11.740 align:start position:0% the liquid pledging contract which we are<00:01:06.560> currently<00:01:06.799> using<00:01:07.159> at<00:01:07.430> givethe<00:01:10.750> let's 00:01:11.740 --> 00:01:11.750 align:start position:0% are currently using at givethe let's 00:01:11.750 --> 00:01:15.610 align:start position:0% are currently using at givethe let's start<00:01:12.200> with<00:01:12.920> the<00:01:13.070> mini-me<00:01:13.430> contrac<00:01:14.590> mini-me 00:01:15.610 --> 00:01:15.620 align:start position:0% start with the mini-me contrac mini-me 00:01:15.620 --> 00:01:18.730 align:start position:0% start with the mini-me contrac mini-me has<00:01:15.920> been<00:01:16.130> developed<00:01:16.610> a<00:01:16.820> year<00:01:17.060> ago<00:01:17.299> it<00:01:18.080> was<00:01:18.350> it 00:01:18.730 --> 00:01:18.740 align:start position:0% has been developed a year ago it was it 00:01:18.740 --> 00:01:21.100 align:start position:0% has been developed a year ago it was it follows<00:01:19.159> the<00:01:19.369> year<00:01:19.580> C<00:01:19.820> 20<00:01:20.240> token<00:01:20.630> a<00:01:20.690> standard 00:01:21.100 --> 00:01:21.110 align:start position:0% follows the year C 20 token a standard 00:01:21.110 --> 00:01:24.580 align:start position:0% follows the year C 20 token a standard and<00:01:21.290> has<00:01:21.830> been<00:01:22.040> used<00:01:22.340> extreme<00:01:22.960> extensively<00:01:23.960> by 00:01:24.580 --> 00:01:24.590 align:start position:0% and has been used extreme extensively by 00:01:24.590 --> 00:01:26.530 align:start position:0% and has been used extreme extensively by many<00:01:24.860> important<00:01:25.460> projects<00:01:25.909> in<00:01:26.090> the<00:01:26.270> interim 00:01:26.530 --> 00:01:26.540 align:start position:0% many important projects in the interim 00:01:26.540 --> 00:01:28.930 align:start position:0% many important projects in the interim space<00:01:26.869> here<00:01:27.770> you<00:01:27.920> can<00:01:28.100> see<00:01:28.310> some<00:01:28.580> of<00:01:28.610> these 00:01:28.930 --> 00:01:28.940 align:start position:0% space here you can see some of these 00:01:28.940 --> 00:01:32.679 align:start position:0% space here you can see some of these projects<00:01:29.510> from<00:01:30.470> City<00:01:30.740> Oregon<00:01:31.189> status<00:01:32.180> given 00:01:32.679 --> 00:01:32.689 align:start position:0% projects from City Oregon status given 00:01:32.689 --> 00:01:36.880 align:start position:0% projects from City Oregon status given district<00:01:33.229> 0x<00:01:33.619> and<00:01:33.890> many<00:01:34.159> others<00:01:35.619> so<00:01:36.619> what 00:01:36.880 --> 00:01:36.890 align:start position:0% district 0x and many others so what 00:01:36.890 --> 00:01:40.390 align:start position:0% district 0x and many others so what makes<00:01:37.100> mini-me<00:01:37.610> contract<00:01:38.090> different<00:01:39.400> it's 00:01:40.390 --> 00:01:40.400 align:start position:0% makes mini-me contract different it's 00:01:40.400 --> 00:01:43.690 align:start position:0% makes mini-me contract different it's more<00:01:40.729> than<00:01:40.909> just<00:01:40.970> a<00:01:41.420> simple<00:01:41.780> year<00:01:42.380> C<00:01:42.650> 20<00:01:43.040> token 00:01:43.690 --> 00:01:43.700 align:start position:0% more than just a simple year C 20 token 00:01:43.700 --> 00:01:47.109 align:start position:0% more than just a simple year C 20 token contract<00:01:44.350> the<00:01:45.350> token<00:01:45.820> has<00:01:46.820> many 00:01:47.109 --> 00:01:47.119 align:start position:0% contract the token has many 00:01:47.119 --> 00:01:49.840 align:start position:0% contract the token has many functionalities<00:01:47.960> that<00:01:48.229> any<00:01:48.740> tab<00:01:49.070> may<00:01:49.549> need 00:01:49.840 --> 00:01:49.850 align:start position:0% functionalities that any tab may need 00:01:49.850 --> 00:01:52.210 align:start position:0% functionalities that any tab may need these<00:01:50.450> functionalities<00:01:50.930> includes<00:01:51.619> creating 00:01:52.210 --> 00:01:52.220 align:start position:0% these functionalities includes creating 00:01:52.220 --> 00:01:54.160 align:start position:0% these functionalities includes creating and<00:01:52.340> destroying<00:01:52.670> tokens<00:01:53.119> black<00:01:53.810> or<00:01:53.960> white 00:01:54.160 --> 00:01:54.170 align:start position:0% and destroying tokens black or white 00:01:54.170 --> 00:01:56.410 align:start position:0% and destroying tokens black or white listing<00:01:54.650> addresses<00:01:55.220> freezing<00:01:55.939> transfers 00:01:56.410 --> 00:01:56.420 align:start position:0% listing addresses freezing transfers 00:01:56.420 --> 00:02:00.190 align:start position:0% listing addresses freezing transfers among<00:01:56.689> others<00:01:57.310> but<00:01:58.310> let's<00:01:58.549> get<00:01:59.270> to<00:01:59.570> the<00:01:59.900> real 00:02:00.190 --> 00:02:00.200 align:start position:0% among others but let's get to the real 00:02:00.200 --> 00:02:02.890 align:start position:0% among others but let's get to the real innovation<00:02:00.470> of<00:02:01.100> what<00:02:01.549> it<00:02:01.729> is<00:02:01.759> of<00:02:02.360> what<00:02:02.689> is<00:02:02.869> a 00:02:02.890 --> 00:02:02.900 align:start position:0% innovation of what it is of what is a 00:02:02.900 --> 00:02:06.969 align:start position:0% innovation of what it is of what is a smart<00:02:03.259> contract<00:02:04.450> the<00:02:05.450> contract<00:02:05.990> tracks<00:02:06.590> the 00:02:06.969 --> 00:02:06.979 align:start position:0% smart contract the contract tracks the 00:02:06.979 --> 00:02:08.800 align:start position:0% smart contract the contract tracks the token<00:02:07.430> distribution<00:02:08.060> history<00:02:08.509> on<00:02:08.689> the 00:02:08.800 --> 00:02:08.810 align:start position:0% token distribution history on the 00:02:08.810 --> 00:02:11.680 align:start position:0% token distribution history on the blockchain<00:02:09.160> this<00:02:10.160> property<00:02:10.729> is<00:02:10.940> what<00:02:11.450> makes 00:02:11.680 --> 00:02:11.690 align:start position:0% blockchain this property is what makes 00:02:11.690 --> 00:02:14.220 align:start position:0% blockchain this property is what makes mini-me<00:02:12.200> contract<00:02:12.709> different 00:02:14.220 --> 00:02:14.230 align:start position:0% mini-me contract different 00:02:14.230 --> 00:02:16.949 align:start position:0% mini-me contract different and<00:02:14.319> allows<00:02:14.830> this<00:02:15.489> token<00:02:15.970> to<00:02:16.360> be<00:02:16.510> cloneable 00:02:16.949 --> 00:02:16.959 align:start position:0% and allows this token to be cloneable 00:02:16.959 --> 00:02:23.160 align:start position:0% and allows this token to be cloneable for<00:02:17.890> cable<00:02:18.159> if<00:02:18.280> you<00:02:18.310> want<00:02:21.269> that<00:02:22.269> means<00:02:22.540> that 00:02:23.160 --> 00:02:23.170 align:start position:0% for cable if you want that means that 00:02:23.170 --> 00:02:25.800 align:start position:0% for cable if you want that means that you<00:02:23.319> can<00:02:23.560> create<00:02:23.890> a<00:02:23.980> new<00:02:24.280> token<00:02:24.549> whose<00:02:25.239> initial 00:02:25.800 --> 00:02:25.810 align:start position:0% you can create a new token whose initial 00:02:25.810 --> 00:02:27.869 align:start position:0% you can create a new token whose initial distribution<00:02:26.049> is<00:02:26.620> the<00:02:27.040> same<00:02:27.280> as<00:02:27.519> the<00:02:27.819> original 00:02:27.869 --> 00:02:27.879 align:start position:0% distribution is the same as the original 00:02:27.879 --> 00:02:32.670 align:start position:0% distribution is the same as the original token<00:02:28.569> this<00:02:29.349> clone<00:02:29.739> fork<00:02:30.930> can<00:02:31.930> be<00:02:32.080> done<00:02:32.290> at<00:02:32.470> any 00:02:32.670 --> 00:02:32.680 align:start position:0% token this clone fork can be done at any 00:02:32.680 --> 00:02:35.009 align:start position:0% token this clone fork can be done at any given<00:02:33.010> block<00:02:33.340> in<00:02:33.519> the<00:02:33.640> past<00:02:33.879> or<00:02:34.360> can<00:02:34.629> be<00:02:34.750> said 00:02:35.009 --> 00:02:35.019 align:start position:0% given block in the past or can be said 00:02:35.019 --> 00:02:38.309 align:start position:0% given block in the past or can be said for<00:02:35.230> the<00:02:35.500> future<00:02:36.000> after<00:02:37.000> the<00:02:37.030> fork<00:02:37.450> each<00:02:37.810> clone 00:02:38.309 --> 00:02:38.319 align:start position:0% for the future after the fork each clone 00:02:38.319 --> 00:02:42.750 align:start position:0% for the future after the fork each clone token<00:02:38.769> is<00:02:39.510> independent<00:02:40.510> of<00:02:41.170> each<00:02:41.799> other<00:02:42.040> much 00:02:42.750 --> 00:02:42.760 align:start position:0% token is independent of each other much 00:02:42.760 --> 00:02:46.470 align:start position:0% token is independent of each other much like<00:02:43.030> it<00:02:43.209> is<00:02:43.329> a<00:02:43.450> fork<00:02:43.720> or<00:02:43.930> BT<00:02:44.849> Bitcoin<00:02:45.849> cash<00:02:46.150> for 00:02:46.470 --> 00:02:46.480 align:start position:0% like it is a fork or BT Bitcoin cash for 00:02:46.480 --> 00:02:49.890 align:start position:0% like it is a fork or BT Bitcoin cash for it<00:02:46.860> all<00:02:47.860> these<00:02:48.430> properties<00:02:48.819> do<00:02:49.450> not<00:02:49.629> count<00:02:49.810> for 00:02:49.890 --> 00:02:49.900 align:start position:0% it all these properties do not count for 00:02:49.900 --> 00:02:52.319 align:start position:0% it all these properties do not count for free<00:02:50.200> and<00:02:50.410> the<00:02:51.069> main<00:02:51.489> disadvantage<00:02:52.150> of 00:02:52.319 --> 00:02:52.329 align:start position:0% free and the main disadvantage of 00:02:52.329 --> 00:02:54.720 align:start position:0% free and the main disadvantage of choosing<00:02:52.959> Minami<00:02:53.379> token<00:02:53.739> is<00:02:53.890> that<00:02:54.370> the<00:02:54.489> gas 00:02:54.720 --> 00:02:54.730 align:start position:0% choosing Minami token is that the gas 00:02:54.730 --> 00:02:57.660 align:start position:0% choosing Minami token is that the gas cost<00:02:55.120> of<00:02:55.359> each<00:02:55.870> transfers<00:02:56.410> is<00:02:56.769> a<00:02:56.829> little<00:02:57.489> bit 00:02:57.660 --> 00:02:57.670 align:start position:0% cost of each transfers is a little bit 00:02:57.670 --> 00:03:02.030 align:start position:0% cost of each transfers is a little bit higher<00:02:58.000> that<00:02:58.660> the<00:02:58.810> non<00:02:59.019> clone<00:02:59.260> of<00:02:59.379> all<00:02:59.470> ones 00:03:02.030 --> 00:03:02.040 align:start position:0% 00:03:02.040 --> 00:03:05.190 align:start position:0% all<00:03:03.040> these<00:03:03.549> functionalities<00:03:03.940> are<00:03:04.510> important 00:03:05.190 --> 00:03:05.200 align:start position:0% all these functionalities are important 00:03:05.200 --> 00:03:07.920 align:start position:0% all these functionalities are important for<00:03:05.349> the<00:03:05.500> next<00:03:05.769> use<00:03:05.920> cases<00:03:06.430> the<00:03:07.209> first<00:03:07.420> one<00:03:07.690> and 00:03:07.920 --> 00:03:07.930 align:start position:0% for the next use cases the first one and 00:03:07.930 --> 00:03:10.920 align:start position:0% for the next use cases the first one and one<00:03:08.620> of<00:03:08.739> the<00:03:08.859> most<00:03:09.069> important<00:03:09.549> one<00:03:09.730> is<00:03:09.970> the 00:03:10.920 --> 00:03:10.930 align:start position:0% one of the most important one is the 00:03:10.930 --> 00:03:14.160 align:start position:0% one of the most important one is the voting<00:03:11.769> application<00:03:12.420> use<00:03:13.420> it<00:03:13.629> in<00:03:13.840> many 00:03:14.160 --> 00:03:14.170 align:start position:0% voting application use it in many 00:03:14.170 --> 00:03:17.520 align:start position:0% voting application use it in many governance<00:03:15.069> systems<00:03:15.660> this<00:03:16.660> means<00:03:16.930> that<00:03:17.290> at 00:03:17.520 --> 00:03:17.530 align:start position:0% governance systems this means that at 00:03:17.530 --> 00:03:19.170 align:start position:0% governance systems this means that at the<00:03:17.650> beginning<00:03:18.010> of<00:03:18.099> a<00:03:18.250> voting<00:03:18.430> process<00:03:18.579> a 00:03:19.170 --> 00:03:19.180 align:start position:0% the beginning of a voting process a 00:03:19.180 --> 00:03:22.740 align:start position:0% the beginning of a voting process a clone<00:03:19.599> token<00:03:20.019> is<00:03:20.230> generated<00:03:21.040> and<00:03:21.450> born<00:03:22.450> after 00:03:22.740 --> 00:03:22.750 align:start position:0% clone token is generated and born after 00:03:22.750 --> 00:03:25.620 align:start position:0% clone token is generated and born after the<00:03:23.319> token<00:03:23.620> holder<00:03:24.310> boats<00:03:24.579> making<00:03:25.480> it 00:03:25.620 --> 00:03:25.630 align:start position:0% the token holder boats making it 00:03:25.630 --> 00:03:29.699 align:start position:0% the token holder boats making it impossible<00:03:25.989> for<00:03:26.349> him<00:03:26.530> to<00:03:26.739> vote<00:03:27.040> twice<00:03:28.709> using 00:03:29.699 --> 00:03:29.709 align:start position:0% impossible for him to vote twice using 00:03:29.709 --> 00:03:33.390 align:start position:0% impossible for him to vote twice using the<00:03:29.829> token<00:03:30.010> contract<00:03:31.109> this<00:03:32.109> way<00:03:32.440> prevents 00:03:33.390 --> 00:03:33.400 align:start position:0% the token contract this way prevents 00:03:33.400 --> 00:03:36.960 align:start position:0% the token contract this way prevents having<00:03:34.060> to<00:03:34.660> lock<00:03:34.930> the<00:03:35.410> mine<00:03:35.680> token<00:03:36.130> while<00:03:36.760> the 00:03:36.960 --> 00:03:36.970 align:start position:0% having to lock the mine token while the 00:03:36.970 --> 00:03:40.819 align:start position:0% having to lock the mine token while the boating<00:03:37.299> token<00:03:37.690> was<00:03:38.410> the<00:03:38.530> voting<00:03:38.680> takes<00:03:39.040> place 00:03:40.819 --> 00:03:40.829 align:start position:0% boating token was the voting takes place 00:03:40.829 --> 00:03:44.099 align:start position:0% boating token was the voting takes place another<00:03:41.829> interesting<00:03:42.370> application<00:03:42.489> is<00:03:43.209> the 00:03:44.099 --> 00:03:44.109 align:start position:0% another interesting application is the 00:03:44.109 --> 00:03:46.170 align:start position:0% another interesting application is the distribution<00:03:44.410> of<00:03:44.859> rewards<00:03:45.040> among<00:03:45.819> talking 00:03:46.170 --> 00:03:46.180 align:start position:0% distribution of rewards among talking 00:03:46.180 --> 00:03:48.539 align:start position:0% distribution of rewards among talking holders<00:03:46.620> when<00:03:47.620> you<00:03:47.739> want<00:03:47.950> to<00:03:48.069> distribute<00:03:48.370> your 00:03:48.539 --> 00:03:48.549 align:start position:0% holders when you want to distribute your 00:03:48.549 --> 00:03:51.809 align:start position:0% holders when you want to distribute your words<00:03:48.880> on<00:03:49.299> a<00:03:49.690> regular<00:03:50.139> basis<00:03:50.590> it's<00:03:51.190> possible 00:03:51.809 --> 00:03:51.819 align:start position:0% words on a regular basis it's possible 00:03:51.819 --> 00:03:54.390 align:start position:0% words on a regular basis it's possible that<00:03:52.030> you<00:03:52.150> ran<00:03:52.389> in<00:03:52.690> the<00:03:53.169> problem<00:03:53.620> that<00:03:54.160> the 00:03:54.390 --> 00:03:54.400 align:start position:0% that you ran in the problem that the 00:03:54.400 --> 00:03:57.089 align:start position:0% that you ran in the problem that the distribution<00:03:54.730> of<00:03:55.180> the<00:03:55.239> token<00:03:55.720> may<00:03:56.440> change<00:03:56.769> as 00:03:57.089 --> 00:03:57.099 align:start position:0% distribution of the token may change as 00:03:57.099 --> 00:04:01.229 align:start position:0% distribution of the token may change as token<00:03:57.639> holders<00:03:58.030> trade<00:03:58.930> the<00:03:59.139> coin<00:04:00.239> mini-me 00:04:01.229 --> 00:04:01.239 align:start position:0% token holders trade the coin mini-me 00:04:01.239 --> 00:04:05.129 align:start position:0% token holders trade the coin mini-me solve<00:04:01.930> this<00:04:02.470> problem<00:04:03.040> because<00:04:03.849> you<00:04:04.450> know<00:04:04.480> the 00:04:05.129 --> 00:04:05.139 align:start position:0% solve this problem because you know the 00:04:05.139 --> 00:04:07.680 align:start position:0% solve this problem because you know the balance<00:04:05.500> of<00:04:05.709> any<00:04:06.099> token<00:04:06.519> holder<00:04:06.879> at<00:04:07.060> any<00:04:07.389> time 00:04:07.680 --> 00:04:07.690 align:start position:0% balance of any token holder at any time 00:04:07.690 --> 00:04:10.500 align:start position:0% balance of any token holder at any time in<00:04:07.870> the<00:04:07.959> past<00:04:08.160> so<00:04:09.160> you<00:04:09.250> can<00:04:09.579> easily<00:04:09.790> create<00:04:10.120> a 00:04:10.500 --> 00:04:10.510 align:start position:0% in the past so you can easily create a 00:04:10.510 --> 00:04:12.509 align:start position:0% in the past so you can easily create a contract<00:04:11.169> that<00:04:11.500> distributes<00:04:12.010> rewards 00:04:12.509 --> 00:04:12.519 align:start position:0% contract that distributes rewards 00:04:12.519 --> 00:04:15.330 align:start position:0% contract that distributes rewards according<00:04:13.239> to<00:04:13.750> the<00:04:13.870> holdings<00:04:14.379> that<00:04:14.709> each 00:04:15.330 --> 00:04:15.340 align:start position:0% according to the holdings that each 00:04:15.340 --> 00:04:17.819 align:start position:0% according to the holdings that each token<00:04:15.609> holder<00:04:16.090> had<00:04:16.449> at<00:04:16.870> the<00:04:17.109> moment<00:04:17.470> its 00:04:17.819 --> 00:04:17.829 align:start position:0% token holder had at the moment its 00:04:17.829 --> 00:04:22.260 align:start position:0% token holder had at the moment its reward<00:04:18.280> both<00:04:18.489> issued<00:04:20.789> the<00:04:21.789> same<00:04:22.030> way<00:04:22.210> you 00:04:22.260 --> 00:04:22.270 align:start position:0% reward both issued the same way you 00:04:22.270 --> 00:04:24.330 align:start position:0% reward both issued the same way you create<00:04:22.690> a<00:04:22.719> boating<00:04:23.020> token<00:04:23.500> you<00:04:24.010> can<00:04:24.159> also 00:04:24.330 --> 00:04:24.340 align:start position:0% create a boating token you can also 00:04:24.340 --> 00:04:26.339 align:start position:0% create a boating token you can also create<00:04:24.669> many<00:04:25.000> functionalities<00:04:25.510> like<00:04:26.169> this 00:04:26.339 --> 00:04:26.349 align:start position:0% create many functionalities like this 00:04:26.349 --> 00:04:27.570 align:start position:0% create many functionalities like this cone<00:04:26.590> token<00:04:27.010> or 00:04:27.570 --> 00:04:27.580 align:start position:0% cone token or 00:04:27.580 --> 00:04:30.270 align:start position:0% cone token or rotation<00:04:27.939> token<00:04:28.330> a<00:04:28.539> disk<00:04:29.199> on<00:04:29.319> token<00:04:29.770> would 00:04:30.270 --> 00:04:30.280 align:start position:0% rotation token a disk on token would 00:04:30.280 --> 00:04:33.749 align:start position:0% rotation token a disk on token would work<00:04:30.490> this<00:04:30.669> way<00:04:31.470> the<00:04:32.470> disk<00:04:32.650> on<00:04:32.830> token<00:04:33.220> may<00:04:33.699> be 00:04:33.749 --> 00:04:33.759 align:start position:0% work this way the disk on token may be 00:04:33.759 --> 00:04:36.029 align:start position:0% work this way the disk on token may be used<00:04:34.090> to<00:04:34.330> buy<00:04:34.509> another<00:04:35.080> token<00:04:35.409> at<00:04:35.710> a<00:04:35.740> given 00:04:36.029 --> 00:04:36.039 align:start position:0% used to buy another token at a given 00:04:36.039 --> 00:04:39.179 align:start position:0% used to buy another token at a given discount<00:04:36.460> and<00:04:36.639> it<00:04:37.599> will<00:04:37.840> be<00:04:37.990> redeemed<00:04:38.289> when 00:04:39.179 --> 00:04:39.189 align:start position:0% discount and it will be redeemed when 00:04:39.189 --> 00:04:42.600 align:start position:0% discount and it will be redeemed when the<00:04:39.430> new<00:04:39.580> tokens<00:04:40.270> are<00:04:40.719> purchased<00:04:41.500> and<00:04:41.710> the 00:04:42.600 --> 00:04:42.610 align:start position:0% the new tokens are purchased and the 00:04:42.610 --> 00:04:47.700 align:start position:0% the new tokens are purchased and the discount<00:04:43.060> is<00:04:43.240> supplied<00:04:44.849> another<00:04:45.849> usage<00:04:46.300> is<00:04:46.710> to 00:04:47.700 --> 00:04:47.710 align:start position:0% discount is supplied another usage is to 00:04:47.710 --> 00:04:52.950 align:start position:0% discount is supplied another usage is to create<00:04:47.979> a<00:04:48.189> token<00:04:48.669> for<00:04:49.180> a<00:04:49.210> spin-off<00:04:49.509> down<00:04:51.960> the 00:04:52.950 --> 00:04:52.960 align:start position:0% create a token for a spin-off down the 00:04:52.960 --> 00:04:55.640 align:start position:0% create a token for a spin-off down the mini<00:04:53.169> token<00:04:53.949> also<00:04:54.490> makes<00:04:54.699> your<00:04:55.000> project 00:04:55.640 --> 00:04:55.650 align:start position:0% mini token also makes your project 00:04:55.650 --> 00:04:58.230 align:start position:0% mini token also makes your project future-proof<00:04:56.650> making<00:04:57.310> it<00:04:57.460> easy<00:04:57.759> to<00:04:58.120> upgrade 00:04:58.230 --> 00:04:58.240 align:start position:0% future-proof making it easy to upgrade 00:04:58.240 --> 00:05:01.350 align:start position:0% future-proof making it easy to upgrade to<00:04:59.050> a<00:04:59.080> new<00:04:59.229> version<00:04:59.289> of<00:04:59.800> the<00:04:59.919> contract<00:05:00.360> but 00:05:01.350 --> 00:05:01.360 align:start position:0% to a new version of the contract but 00:05:01.360 --> 00:05:03.869 align:start position:0% to a new version of the contract but probably<00:05:01.930> the<00:05:02.440> most<00:05:02.710> incredible<00:05:02.919> facet<00:05:03.759> of 00:05:03.869 --> 00:05:03.879 align:start position:0% probably the most incredible facet of 00:05:03.879 --> 00:05:07.439 align:start position:0% probably the most incredible facet of this<00:05:04.449> token<00:05:04.870> is<00:05:05.050> that<00:05:05.319> anyone<00:05:05.949> can<00:05:06.250> create<00:05:07.150> a 00:05:07.439 --> 00:05:07.449 align:start position:0% this token is that anyone can create a 00:05:07.449 --> 00:05:10.320 align:start position:0% this token is that anyone can create a clone<00:05:07.870> token<00:05:08.319> in<00:05:08.590> permissionless<00:05:09.219> way<00:05:09.610> so 00:05:10.320 --> 00:05:10.330 align:start position:0% clone token in permissionless way so 00:05:10.330 --> 00:05:12.450 align:start position:0% clone token in permissionless way so that<00:05:10.539> anyone<00:05:11.110> can<00:05:11.590> add<00:05:11.770> value<00:05:12.009> to<00:05:12.280> the 00:05:12.450 --> 00:05:12.460 align:start position:0% that anyone can add value to the 00:05:12.460 --> 00:05:19.320 align:start position:0% that anyone can add value to the community<00:05:16.530> let's<00:05:17.530> talk<00:05:17.830> now<00:05:18.069> a<00:05:18.430> little<00:05:18.909> bit 00:05:19.320 --> 00:05:19.330 align:start position:0% community let's talk now a little bit 00:05:19.330 --> 00:05:21.300 align:start position:0% community let's talk now a little bit about<00:05:19.569> the<00:05:19.719> future<00:05:19.900> of<00:05:20.289> the<00:05:20.680> token<00:05:20.979> smart 00:05:21.300 --> 00:05:21.310 align:start position:0% about the future of the token smart 00:05:21.310 --> 00:05:23.999 align:start position:0% about the future of the token smart contracts<00:05:21.789> the<00:05:22.629> future<00:05:23.050> clearly<00:05:23.349> points<00:05:23.979> to 00:05:23.999 --> 00:05:24.009 align:start position:0% contracts the future clearly points to 00:05:24.009 --> 00:05:26.869 align:start position:0% contracts the future clearly points to the<00:05:24.159> ERC<00:05:24.370> two<00:05:24.969> to<00:05:25.120> three<00:05:25.330> standard<00:05:25.810> proposal 00:05:26.869 --> 00:05:26.879 align:start position:0% the ERC two to three standard proposal 00:05:26.879 --> 00:05:29.760 align:start position:0% the ERC two to three standard proposal there<00:05:27.879> is<00:05:27.969> mainly<00:05:28.360> one<00:05:28.569> operation<00:05:29.319> in<00:05:29.620> this 00:05:29.760 --> 00:05:29.770 align:start position:0% there is mainly one operation in this 00:05:29.770 --> 00:05:32.129 align:start position:0% there is mainly one operation in this standard<00:05:30.189> that<00:05:30.849> operation<00:05:31.270> is<00:05:31.389> transfer<00:05:31.870> and 00:05:32.129 --> 00:05:32.139 align:start position:0% standard that operation is transfer and 00:05:32.139 --> 00:05:36.170 align:start position:0% standard that operation is transfer and with<00:05:33.099> this<00:05:33.250> transfer<00:05:33.729> you<00:05:34.090> can<00:05:34.300> attach<00:05:34.659> data 00:05:36.170 --> 00:05:36.180 align:start position:0% with this transfer you can attach data 00:05:36.180 --> 00:05:38.670 align:start position:0% with this transfer you can attach data once<00:05:37.180> the<00:05:37.300> transfer<00:05:37.599> is<00:05:37.779> done<00:05:37.810> if<00:05:38.259> the 00:05:38.670 --> 00:05:38.680 align:start position:0% once the transfer is done if the 00:05:38.680 --> 00:05:40.559 align:start position:0% once the transfer is done if the recipient<00:05:38.949> is<00:05:39.219> a<00:05:39.250> contract<00:05:39.819> the<00:05:40.210> token 00:05:40.559 --> 00:05:40.569 align:start position:0% recipient is a contract the token 00:05:40.569 --> 00:05:43.350 align:start position:0% recipient is a contract the token fallback<00:05:40.960> function<00:05:41.469> is<00:05:41.620> of<00:05:42.129> the<00:05:42.729> recipient<00:05:43.240> is 00:05:43.350 --> 00:05:43.360 align:start position:0% fallback function is of the recipient is 00:05:43.360 --> 00:05:46.649 align:start position:0% fallback function is of the recipient is called<00:05:43.719> with<00:05:44.409> this<00:05:44.770> extra<00:05:45.219> data<00:05:45.339> as<00:05:45.729> you<00:05:46.389> can 00:05:46.649 --> 00:05:46.659 align:start position:0% called with this extra data as you can 00:05:46.659 --> 00:05:49.079 align:start position:0% called with this extra data as you can see<00:05:46.900> the<00:05:47.289> mine<00:05:47.469> idea<00:05:47.800> of<00:05:47.949> this<00:05:48.129> standard<00:05:48.610> is<00:05:48.849> to 00:05:49.079 --> 00:05:49.089 align:start position:0% see the mine idea of this standard is to 00:05:49.089 --> 00:05:50.999 align:start position:0% see the mine idea of this standard is to work<00:05:49.300> very<00:05:49.539> much<00:05:49.629> like<00:05:50.110> either<00:05:50.349> works<00:05:50.740> right 00:05:50.999 --> 00:05:51.009 align:start position:0% work very much like either works right 00:05:51.009 --> 00:05:56.100 align:start position:0% work very much like either works right now<00:05:51.870> this<00:05:52.870> estándar<00:05:53.289> is<00:05:53.409> not<00:05:53.589> ready<00:05:53.889> yet<00:05:55.110> to 00:05:56.100 --> 00:05:56.110 align:start position:0% now this estándar is not ready yet to 00:05:56.110 --> 00:05:59.040 align:start position:0% now this estándar is not ready yet to get<00:05:56.319> there<00:05:56.610> the<00:05:57.610> two<00:05:57.819> main<00:05:58.029> points<00:05:58.330> that<00:05:58.839> needs 00:05:59.040 --> 00:05:59.050 align:start position:0% get there the two main points that needs 00:05:59.050 --> 00:06:02.490 align:start position:0% get there the two main points that needs to<00:05:59.199> be<00:05:59.229> resolved<00:05:59.889> our<00:06:00.719> first<00:06:01.719> backwards 00:06:02.490 --> 00:06:02.500 align:start position:0% to be resolved our first backwards 00:06:02.500 --> 00:06:05.010 align:start position:0% to be resolved our first backwards compatibility<00:06:03.330> which<00:06:04.330> I<00:06:04.509> think<00:06:04.810> it's 00:06:05.010 --> 00:06:05.020 align:start position:0% compatibility which I think it's 00:06:05.020 --> 00:06:07.320 align:start position:0% compatibility which I think it's solvable<00:06:05.469> for<00:06:06.279> example<00:06:06.789> you<00:06:06.969> can<00:06:07.180> always 00:06:07.320 --> 00:06:07.330 align:start position:0% solvable for example you can always 00:06:07.330 --> 00:06:08.969 align:start position:0% solvable for example you can always create<00:06:07.719> rubber<00:06:08.020> contracts<00:06:08.620> in<00:06:08.710> the<00:06:08.800> worst 00:06:08.969 --> 00:06:08.979 align:start position:0% create rubber contracts in the worst 00:06:08.979 --> 00:06:13.320 align:start position:0% create rubber contracts in the worst case<00:06:09.219> and<00:06:10.469> the<00:06:11.469> other<00:06:11.589> point<00:06:11.979> that<00:06:12.330> is 00:06:13.320 --> 00:06:13.330 align:start position:0% case and the other point that is 00:06:13.330 --> 00:06:16.800 align:start position:0% case and the other point that is necessary<00:06:14.289> in<00:06:14.440> my<00:06:14.589> opinion<00:06:15.099> is<00:06:15.520> to<00:06:16.210> define<00:06:16.569> a 00:06:16.800 --> 00:06:16.810 align:start position:0% necessary in my opinion is to define a 00:06:16.810 --> 00:06:20.459 align:start position:0% necessary in my opinion is to define a pseudo<00:06:17.379> introspection<00:06:18.099> stander<00:06:19.469> mainly 00:06:20.459 --> 00:06:20.469 align:start position:0% pseudo introspection stander mainly 00:06:20.469 --> 00:06:22.409 align:start position:0% pseudo introspection stander mainly through<00:06:20.680> the<00:06:20.710> introspection<00:06:21.310> means<00:06:21.729> that<00:06:22.270> you 00:06:22.409 --> 00:06:22.419 align:start position:0% through the introspection means that you 00:06:22.419 --> 00:06:24.719 align:start position:0% through the introspection means that you can<00:06:22.629> ask<00:06:22.839> to<00:06:23.259> a<00:06:23.289> smart<00:06:23.589> contract<00:06:24.099> about<00:06:24.310> the 00:06:24.719 --> 00:06:24.729 align:start position:0% can ask to a smart contract about the 00:06:24.729 --> 00:06:27.469 align:start position:0% can ask to a smart contract about the implementation<00:06:25.360> of<00:06:25.449> a<00:06:25.569> specific<00:06:25.990> interface 00:06:27.469 --> 00:06:27.479 align:start position:0% implementation of a specific interface 00:06:27.479 --> 00:06:30.869 align:start position:0% implementation of a specific interface to<00:06:28.479> standardize<00:06:28.930> this<00:06:29.349> we<00:06:30.039> currently<00:06:30.339> have 00:06:30.869 --> 00:06:30.879 align:start position:0% to standardize this we currently have 00:06:30.879 --> 00:06:34.920 align:start position:0% to standardize this we currently have two<00:06:31.240> very<00:06:31.509> different<00:06:31.810> proposals<00:06:32.699> JP<00:06:33.699> 165<00:06:34.599> and 00:06:34.920 --> 00:06:34.930 align:start position:0% two very different proposals JP 165 and 00:06:34.930 --> 00:06:39.520 align:start position:0% two very different proposals JP 165 and the<00:06:35.500> AAP<00:06:35.860> six<00:06:36.250> seven<00:06:36.580> to 00:06:39.520 --> 00:06:39.530 align:start position:0% 00:06:39.530 --> 00:06:42.760 align:start position:0% EAP<00:06:39.950> 165<00:06:40.880> is<00:06:41.150> very<00:06:41.540> straightforward<00:06:41.870> you<00:06:42.470> just 00:06:42.760 --> 00:06:42.770 align:start position:0% EAP 165 is very straightforward you just 00:06:42.770 --> 00:06:45.700 align:start position:0% EAP 165 is very straightforward you just define<00:06:43.160> a<00:06:43.400> support<00:06:44.150> interface<00:06:44.600> function<00:06:45.110> that 00:06:45.700 --> 00:06:45.710 align:start position:0% define a support interface function that 00:06:45.710 --> 00:06:50.830 align:start position:0% define a support interface function that is<00:06:46.040> the<00:06:46.940> smart<00:06:47.390> contract<00:06:47.990> may<00:06:48.380> implement<00:06:49.840> then 00:06:50.830 --> 00:06:50.840 align:start position:0% is the smart contract may implement then 00:06:50.840 --> 00:06:53.290 align:start position:0% is the smart contract may implement then anyone<00:06:51.620> can<00:06:51.830> use<00:06:52.040> this<00:06:52.190> function<00:06:52.610> to<00:06:52.640> query<00:06:53.000> if 00:06:53.290 --> 00:06:53.300 align:start position:0% anyone can use this function to query if 00:06:53.300 --> 00:06:55.000 align:start position:0% anyone can use this function to query if this<00:06:53.510> contract<00:06:53.750> implements<00:06:54.500> a<00:06:54.590> specific 00:06:55.000 --> 00:06:55.010 align:start position:0% this contract implements a specific 00:06:55.010 --> 00:06:57.450 align:start position:0% this contract implements a specific interface<00:06:55.430> or<00:06:55.640> not 00:06:57.450 --> 00:06:57.460 align:start position:0% interface or not 00:06:57.460 --> 00:07:01.480 align:start position:0% interface or not the<00:06:58.460> other<00:06:58.580> proposal<00:06:59.410> ip67<00:07:00.410> to<00:07:00.710> in<00:07:01.070> my<00:07:01.340> opinion 00:07:01.480 --> 00:07:01.490 align:start position:0% the other proposal ip67 to in my opinion 00:07:01.490 --> 00:07:04.390 align:start position:0% the other proposal ip67 to in my opinion makes<00:07:02.300> more<00:07:02.690> sense<00:07:03.110> and<00:07:03.350> it's<00:07:03.860> much<00:07:04.160> more 00:07:04.390 --> 00:07:04.400 align:start position:0% makes more sense and it's much more 00:07:04.400 --> 00:07:08.290 align:start position:0% makes more sense and it's much more scalable<00:07:04.750> the<00:07:05.750> idea<00:07:06.080> of<00:07:06.200> EAP<00:07:06.770> success<00:07:07.220> 6<00:07:07.850> 7<00:07:08.120> 2 00:07:08.290 --> 00:07:08.300 align:start position:0% scalable the idea of EAP success 6 7 2 00:07:08.300 --> 00:07:11.440 align:start position:0% scalable the idea of EAP success 6 7 2 is<00:07:08.720> to<00:07:09.050> use<00:07:09.260> reverse<00:07:09.800> ENS<00:07:10.490> to<00:07:10.880> keep<00:07:11.090> a<00:07:11.240> database 00:07:11.440 --> 00:07:11.450 align:start position:0% is to use reverse ENS to keep a database 00:07:11.450 --> 00:07:14.830 align:start position:0% is to use reverse ENS to keep a database of<00:07:12.020> interfaces<00:07:12.850> implemented<00:07:13.850> on<00:07:14.300> each 00:07:14.830 --> 00:07:14.840 align:start position:0% of interfaces implemented on each 00:07:14.840 --> 00:07:17.710 align:start position:0% of interfaces implemented on each existing<00:07:15.590> contract<00:07:16.210> let<00:07:17.210> me<00:07:17.330> give<00:07:17.510> you<00:07:17.630> an 00:07:17.710 --> 00:07:17.720 align:start position:0% existing contract let me give you an 00:07:17.720 --> 00:07:21.340 align:start position:0% existing contract let me give you an example<00:07:18.020> of<00:07:18.350> how<00:07:18.800> this<00:07:18.980> would<00:07:19.190> work<00:07:20.350> imagine 00:07:21.340 --> 00:07:21.350 align:start position:0% example of how this would work imagine 00:07:21.350 --> 00:07:23.170 align:start position:0% example of how this would work imagine that<00:07:21.530> a<00:07:21.560> contract<00:07:22.040> implements<00:07:22.520> a<00:07:22.700> token 00:07:23.170 --> 00:07:23.180 align:start position:0% that a contract implements a token 00:07:23.180 --> 00:07:26.440 align:start position:0% that a contract implements a token fallback<00:07:23.600> interface<00:07:24.850> and<00:07:25.850> the<00:07:25.940> constructor 00:07:26.440 --> 00:07:26.450 align:start position:0% fallback interface and the constructor 00:07:26.450 --> 00:07:30.250 align:start position:0% fallback interface and the constructor of<00:07:26.480> the<00:07:26.600> token<00:07:27.050> would<00:07:27.530> add<00:07:27.740> this<00:07:28.840> entry<00:07:29.840> in<00:07:30.080> the 00:07:30.250 --> 00:07:30.260 align:start position:0% of the token would add this entry in the 00:07:30.260 --> 00:07:34.870 align:start position:0% of the token would add this entry in the reverse<00:07:30.530> ENS<00:07:33.010> for<00:07:34.010> people<00:07:34.310> that<00:07:34.490> don't<00:07:34.730> know 00:07:34.870 --> 00:07:34.880 align:start position:0% reverse ENS for people that don't know 00:07:34.880 --> 00:07:38.080 align:start position:0% reverse ENS for people that don't know how<00:07:35.570> reverse<00:07:36.110> ENS<00:07:36.560> works<00:07:36.860> it<00:07:37.160> mainly<00:07:37.610> defines 00:07:38.080 --> 00:07:38.090 align:start position:0% how reverse ENS works it mainly defines 00:07:38.090 --> 00:07:41.470 align:start position:0% how reverse ENS works it mainly defines a<00:07:38.390> domain<00:07:38.900> for<00:07:39.560> each<00:07:39.740> address<00:07:40.270> normally<00:07:41.270> this 00:07:41.470 --> 00:07:41.480 align:start position:0% a domain for each address normally this 00:07:41.480 --> 00:07:43.390 align:start position:0% a domain for each address normally this address<00:07:41.870> is<00:07:42.080> assigned<00:07:42.590> to<00:07:42.740> a<00:07:42.830> human<00:07:43.190> readable 00:07:43.390 --> 00:07:43.400 align:start position:0% address is assigned to a human readable 00:07:43.400 --> 00:07:45.520 align:start position:0% address is assigned to a human readable name<00:07:43.760> so<00:07:44.180> you<00:07:44.270> can<00:07:44.570> set<00:07:44.810> a<00:07:44.840> name<00:07:45.110> for<00:07:45.350> your 00:07:45.520 --> 00:07:45.530 align:start position:0% name so you can set a name for your 00:07:45.530 --> 00:07:48.130 align:start position:0% name so you can set a name for your address<00:07:45.680> but<00:07:46.640> you<00:07:46.970> have<00:07:47.240> full<00:07:47.510> control<00:07:47.930> of 00:07:48.130 --> 00:07:48.140 align:start position:0% address but you have full control of 00:07:48.140 --> 00:07:51.670 align:start position:0% address but you have full control of this<00:07:48.590> special<00:07:49.220> domain<00:07:49.900> assigned<00:07:50.900> to<00:07:51.560> your 00:07:51.670 --> 00:07:51.680 align:start position:0% this special domain assigned to your 00:07:51.680 --> 00:07:55.180 align:start position:0% this special domain assigned to your address<00:07:51.860> so<00:07:52.640> you<00:07:52.700> can<00:07:52.970> create<00:07:53.270> subdomains<00:07:54.190> in 00:07:55.180 --> 00:07:55.190 align:start position:0% address so you can create subdomains in 00:07:55.190 --> 00:07:57.520 align:start position:0% address so you can create subdomains in our<00:07:55.400> case<00:07:55.669> we<00:07:56.419> define<00:07:56.810> a<00:07:56.840> subdomain 00:07:57.520 --> 00:07:57.530 align:start position:0% our case we define a subdomain 00:07:57.530 --> 00:07:59.560 align:start position:0% our case we define a subdomain with<00:07:58.100> the<00:07:58.250> interface<00:07:58.610> name<00:07:58.820> that<00:07:59.419> the 00:07:59.560 --> 00:07:59.570 align:start position:0% with the interface name that the 00:07:59.570 --> 00:08:02.890 align:start position:0% with the interface name that the contract<00:08:00.080> implements<00:08:00.800> and<00:08:01.040> make<00:08:01.880> it<00:08:02.090> point<00:08:02.479> to 00:08:02.890 --> 00:08:02.900 align:start position:0% contract implements and make it point to 00:08:02.900 --> 00:08:05.050 align:start position:0% contract implements and make it point to the<00:08:03.080> address<00:08:03.440> responsible<00:08:04.250> for<00:08:04.669> implementing 00:08:05.050 --> 00:08:05.060 align:start position:0% the address responsible for implementing 00:08:05.060 --> 00:08:08.020 align:start position:0% the address responsible for implementing the<00:08:05.240> interface<00:08:05.720> in<00:08:05.990> most<00:08:06.470> cases<00:08:06.820> this<00:08:07.820> will 00:08:08.020 --> 00:08:08.030 align:start position:0% the interface in most cases this will 00:08:08.030 --> 00:08:11.020 align:start position:0% the interface in most cases this will point<00:08:08.390> to<00:08:08.990> itself<00:08:09.350> if<00:08:09.830> the<00:08:10.640> contract 00:08:11.020 --> 00:08:11.030 align:start position:0% point to itself if the contract 00:08:11.030 --> 00:08:14.950 align:start position:0% point to itself if the contract implements<00:08:11.450> the<00:08:11.510> interface<00:08:13.390> but<00:08:14.390> that<00:08:14.660> not 00:08:14.950 --> 00:08:14.960 align:start position:0% implements the interface but that not 00:08:14.960 --> 00:08:17.320 align:start position:0% implements the interface but that not strictly<00:08:15.530> necessary<00:08:15.650> and<00:08:16.370> this<00:08:16.820> is<00:08:16.970> where<00:08:17.150> the 00:08:17.320 --> 00:08:17.330 align:start position:0% strictly necessary and this is where the 00:08:17.330 --> 00:08:21.790 align:start position:0% strictly necessary and this is where the standard<00:08:17.750> gets<00:08:17.990> interesting<00:08:19.840> this<00:08:20.840> entry<00:08:21.320> can 00:08:21.790 --> 00:08:21.800 align:start position:0% standard gets interesting this entry can 00:08:21.800 --> 00:08:24.180 align:start position:0% standard gets interesting this entry can point<00:08:22.100> to<00:08:22.340> a<00:08:22.370> different<00:08:22.580> proxy<00:08:23.240> contract 00:08:24.180 --> 00:08:24.190 align:start position:0% point to a different proxy contract 00:08:24.190 --> 00:08:29.159 align:start position:0% point to a different proxy contract think<00:08:25.190> about<00:08:25.340> it<00:08:26.169> this<00:08:27.169> allows<00:08:27.740> for<00:08:28.090> future 00:08:29.159 --> 00:08:29.169 align:start position:0% think about it this allows for future 00:08:29.169 --> 00:08:31.900 align:start position:0% think about it this allows for future functionalities<00:08:30.169> and<00:08:30.440> future<00:08:30.860> interface<00:08:31.370> to 00:08:31.900 --> 00:08:31.910 align:start position:0% functionalities and future interface to 00:08:31.910 --> 00:08:35.579 align:start position:0% functionalities and future interface to be<00:08:32.060> easily<00:08:32.570> supported<00:08:33.110> when<00:08:34.010> they<00:08:34.190> come 00:08:35.579 --> 00:08:35.589 align:start position:0% be easily supported when they come 00:08:35.589 --> 00:08:38.200 align:start position:0% be easily supported when they come coming<00:08:36.589> back<00:08:36.800> to<00:08:37.039> the<00:08:37.159> year<00:08:37.400> see<00:08:37.640> 2<00:08:37.849> to<00:08:37.969> 3 00:08:38.200 --> 00:08:38.210 align:start position:0% coming back to the year see 2 to 3 00:08:38.210 --> 00:08:40.899 align:start position:0% coming back to the year see 2 to 3 standard<00:08:38.690> one<00:08:39.289> of<00:08:39.320> the<00:08:39.469> biggest<00:08:39.919> shortcomings 00:08:40.899 --> 00:08:40.909 align:start position:0% standard one of the biggest shortcomings 00:08:40.909 --> 00:08:43.690 align:start position:0% standard one of the biggest shortcomings is<00:08:41.180> that<00:08:41.630> it<00:08:41.810> cannot<00:08:42.200> transfer<00:08:42.740> tokens<00:08:43.159> to<00:08:43.669> the 00:08:43.690 --> 00:08:43.700 align:start position:0% is that it cannot transfer tokens to the 00:08:43.700 --> 00:08:45.880 align:start position:0% is that it cannot transfer tokens to the current<00:08:44.120> multi-sig<00:08:44.570> implementation<00:08:45.320> because 00:08:45.880 --> 00:08:45.890 align:start position:0% current multi-sig implementation because 00:08:45.890 --> 00:08:48.010 align:start position:0% current multi-sig implementation because they<00:08:46.070> are<00:08:46.300> contracts<00:08:47.300> that<00:08:47.510> don't<00:08:47.720> implement 00:08:48.010 --> 00:08:48.020 align:start position:0% they are contracts that don't implement 00:08:48.020 --> 00:08:51.940 align:start position:0% they are contracts that don't implement the<00:08:48.650> token<00:08:49.070> fallback<00:08:49.459> function<00:08:50.709> to<00:08:51.709> work 00:08:51.940 --> 00:08:51.950 align:start position:0% the token fallback function to work 00:08:51.950 --> 00:08:53.199 align:start position:0% the token fallback function to work around<00:08:52.160> these 00:08:53.199 --> 00:08:53.209 align:start position:0% around these 00:08:53.209 --> 00:08:54.939 align:start position:0% around these a<00:08:53.240> new<00:08:53.449> version<00:08:53.660> of<00:08:53.990> the<00:08:54.139> multi-sig<00:08:54.619> should<00:08:54.829> be 00:08:54.939 --> 00:08:54.949 align:start position:0% a new version of the multi-sig should be 00:08:54.949 --> 00:08:59.350 align:start position:0% a new version of the multi-sig should be deployed<00:08:55.600> but<00:08:57.279> this<00:08:58.279> can<00:08:58.579> be<00:08:58.759> solved<00:08:59.179> easily 00:08:59.350 --> 00:08:59.360 align:start position:0% deployed but this can be solved easily 00:08:59.360 --> 00:09:04.600 align:start position:0% deployed but this can be solved easily with<00:09:00.290> a<00:09:00.699> ip67<00:09:01.699> -<00:09:02.059> by<00:09:02.720> creating<00:09:03.350> a<00:09:03.499> reverse<00:09:04.129> E&S 00:09:04.600 --> 00:09:04.610 align:start position:0% with a ip67 - by creating a reverse E&S 00:09:04.610 --> 00:09:07.269 align:start position:0% with a ip67 - by creating a reverse E&S entry<00:09:05.089> for<00:09:05.779> the<00:09:05.929> iTalk<00:09:06.379> and<00:09:06.860> fallback 00:09:07.269 --> 00:09:07.279 align:start position:0% entry for the iTalk and fallback 00:09:07.279 --> 00:09:09.309 align:start position:0% entry for the iTalk and fallback interface<00:09:07.790> that<00:09:08.420> points<00:09:08.839> to<00:09:08.959> a<00:09:08.990> proxy 00:09:09.309 --> 00:09:09.319 align:start position:0% interface that points to a proxy 00:09:09.319 --> 00:09:11.710 align:start position:0% interface that points to a proxy contract<00:09:09.949> that<00:09:10.279> just<00:09:10.579> accepts<00:09:11.149> the<00:09:11.240> transfer 00:09:11.710 --> 00:09:11.720 align:start position:0% contract that just accepts the transfer 00:09:11.720 --> 00:09:14.859 align:start position:0% contract that just accepts the transfer and<00:09:12.339> this<00:09:13.339> is<00:09:13.490> very<00:09:13.639> exciting<00:09:14.209> this<00:09:14.569> also 00:09:14.859 --> 00:09:14.869 align:start position:0% and this is very exciting this also 00:09:14.869 --> 00:09:18.040 align:start position:0% and this is very exciting this also gives<00:09:15.259> the<00:09:15.470> possibility<00:09:16.220> of<00:09:16.509> executing<00:09:17.509> some 00:09:18.040 --> 00:09:18.050 align:start position:0% gives the possibility of executing some 00:09:18.050 --> 00:09:20.919 align:start position:0% gives the possibility of executing some code<00:09:18.350> not<00:09:18.920> only<00:09:18.980> when<00:09:19.790> tokens<00:09:20.179> are<00:09:20.360> sent<00:09:20.720> to<00:09:20.809> a 00:09:20.919 --> 00:09:20.929 align:start position:0% code not only when tokens are sent to a 00:09:20.929 --> 00:09:23.769 align:start position:0% code not only when tokens are sent to a contract<00:09:21.499> but<00:09:21.889> also<00:09:22.189> when<00:09:22.910> tokens<00:09:23.269> are<00:09:23.449> sent 00:09:23.769 --> 00:09:23.779 align:start position:0% contract but also when tokens are sent 00:09:23.779 --> 00:09:27.790 align:start position:0% contract but also when tokens are sent to<00:09:23.839> a<00:09:23.990> regular<00:09:24.470> account<00:09:25.839> if<00:09:26.839> you<00:09:27.139> assign<00:09:27.470> a 00:09:27.790 --> 00:09:27.800 align:start position:0% to a regular account if you assign a 00:09:27.800 --> 00:09:31.359 align:start position:0% to a regular account if you assign a proxy<00:09:28.699> to<00:09:28.910> a<00:09:29.089> regular<00:09:29.540> account<00:09:29.929> you<00:09:30.559> can<00:09:30.829> for 00:09:31.359 --> 00:09:31.369 align:start position:0% proxy to a regular account you can for 00:09:31.369 --> 00:09:35.079 align:start position:0% proxy to a regular account you can for example<00:09:31.629> prevent<00:09:33.160> receiving<00:09:34.160> a<00:09:34.309> payment<00:09:34.610> you 00:09:35.079 --> 00:09:35.089 align:start position:0% example prevent receiving a payment you 00:09:35.089 --> 00:09:37.629 align:start position:0% example prevent receiving a payment you don't<00:09:35.300> want<00:09:35.540> or<00:09:35.959> trigger<00:09:36.649> any<00:09:37.009> code<00:09:37.399> you 00:09:37.629 --> 00:09:37.639 align:start position:0% don't want or trigger any code you 00:09:37.639 --> 00:09:39.939 align:start position:0% don't want or trigger any code you desire<00:09:38.059> when<00:09:38.480> regular<00:09:38.929> account<00:09:39.529> receives 00:09:39.939 --> 00:09:39.949 align:start position:0% desire when regular account receives 00:09:39.949 --> 00:09:48.970 align:start position:0% desire when regular account receives tokens<00:09:46.240> at<00:09:47.240> this<00:09:47.509> point<00:09:47.839> if<00:09:48.290> you<00:09:48.589> put<00:09:48.800> together 00:09:48.970 --> 00:09:48.980 align:start position:0% tokens at this point if you put together 00:09:48.980 --> 00:09:51.429 align:start position:0% tokens at this point if you put together all<00:09:49.490> the<00:09:49.819> minimal<00:09:50.179> functionality<00:09:50.329> and<00:09:51.079> the 00:09:51.429 --> 00:09:51.439 align:start position:0% all the minimal functionality and the 00:09:51.439 --> 00:09:55.509 align:start position:0% all the minimal functionality and the year<00:09:51.649> see<00:09:51.889> 2<00:09:52.100> to<00:09:52.249> 3<00:09:52.519> token<00:09:52.939> with<00:09:53.360> the<00:09:54.079> a<00:09:54.230> ip67<00:09:55.160> - 00:09:55.509 --> 00:09:55.519 align:start position:0% year see 2 to 3 token with the a ip67 - 00:09:55.519 --> 00:10:01.090 align:start position:0% year see 2 to 3 token with the a ip67 - we<00:09:56.119> get<00:09:56.420> a<00:09:56.660> super<00:09:57.499> flexible<00:09:57.939> contract<00:09:59.920> this<00:10:00.920> is 00:10:01.090 --> 00:10:01.100 align:start position:0% we get a super flexible contract this is 00:10:01.100 --> 00:10:04.179 align:start position:0% we get a super flexible contract this is the<00:10:01.910> new<00:10:02.119> token<00:10:02.480> contract<00:10:03.139> giveth<00:10:03.619> is<00:10:03.769> working 00:10:04.179 --> 00:10:04.189 align:start position:0% the new token contract giveth is working 00:10:04.189 --> 00:10:05.259 align:start position:0% the new token contract giveth is working on<00:10:04.369> right<00:10:04.850> now 00:10:05.259 --> 00:10:05.269 align:start position:0% on right now 00:10:05.269 --> 00:10:08.350 align:start position:0% on right now we<00:10:05.689> call<00:10:05.959> it<00:10:06.110> internally<00:10:06.860> yoga<00:10:07.339> token<00:10:07.699> you<00:10:08.179> can 00:10:08.350 --> 00:10:08.360 align:start position:0% we call it internally yoga token you can 00:10:08.360 --> 00:10:12.999 align:start position:0% we call it internally yoga token you can imagine<00:10:08.629> in<00:10:08.929> choir<00:10:09.670> in<00:10:10.689> my<00:10:11.689> opinion<00:10:12.049> this<00:10:12.679> yoga 00:10:12.999 --> 00:10:13.009 align:start position:0% imagine in choir in my opinion this yoga 00:10:13.009 --> 00:10:16.030 align:start position:0% imagine in choir in my opinion this yoga token<00:10:13.369> could<00:10:13.730> be<00:10:13.910> a<00:10:14.149> perfect<00:10:15.049> candidate<00:10:15.439> to<00:10:15.889> be 00:10:16.030 --> 00:10:16.040 align:start position:0% token could be a perfect candidate to be 00:10:16.040 --> 00:10:17.829 align:start position:0% token could be a perfect candidate to be considered<00:10:16.549> for<00:10:17.029> a<00:10:17.089> standard<00:10:17.509> aetherium 00:10:17.829 --> 00:10:17.839 align:start position:0% considered for a standard aetherium 00:10:17.839 --> 00:10:20.199 align:start position:0% considered for a standard aetherium token<00:10:18.170> especially<00:10:19.040> if<00:10:19.309> the<00:10:19.549> theory<00:10:19.759> on<00:10:19.939> base 00:10:20.199 --> 00:10:20.209 align:start position:0% token especially if the theory on base 00:10:20.209 --> 00:10:22.989 align:start position:0% token especially if the theory on base government<00:10:21.019> systems<00:10:21.470> like<00:10:22.249> carbon<00:10:22.610> boating 00:10:22.989 --> 00:10:22.999 align:start position:0% government systems like carbon boating 00:10:22.999 --> 00:10:25.230 align:start position:0% government systems like carbon boating or<00:10:23.119> protocol<00:10:23.569> voting<00:10:23.959> are<00:10:24.110> to<00:10:24.559> be<00:10:24.679> developed 00:10:25.230 --> 00:10:25.240 align:start position:0% or protocol voting are to be developed 00:10:25.240 --> 00:10:28.030 align:start position:0% or protocol voting are to be developed of<00:10:26.240> course<00:10:26.540> the<00:10:26.809> gas<00:10:26.990> problem<00:10:27.470> may<00:10:27.589> still<00:10:27.920> be 00:10:28.030 --> 00:10:28.040 align:start position:0% of course the gas problem may still be 00:10:28.040 --> 00:10:30.840 align:start position:0% of course the gas problem may still be an<00:10:28.129> issue<00:10:28.279> but<00:10:29.089> this<00:10:29.269> can<00:10:29.569> be<00:10:29.600> minimised<00:10:30.379> by 00:10:30.840 --> 00:10:30.850 align:start position:0% an issue but this can be minimised by 00:10:30.850 --> 00:10:33.819 align:start position:0% an issue but this can be minimised by enforcing<00:10:31.850> only<00:10:32.149> epoch<00:10:32.569> snapshots<00:10:33.290> instead 00:10:33.819 --> 00:10:33.829 align:start position:0% enforcing only epoch snapshots instead 00:10:33.829 --> 00:10:39.549 align:start position:0% enforcing only epoch snapshots instead of<00:10:34.069> blocking<00:10:34.670> up<00:10:34.850> shots<00:10:37.749> now<00:10:38.749> the<00:10:38.809> last<00:10:39.049> topics 00:10:39.549 --> 00:10:39.559 align:start position:0% of blocking up shots now the last topics 00:10:39.559 --> 00:10:42.669 align:start position:0% of blocking up shots now the last topics to<00:10:39.709> finish<00:10:40.009> this<00:10:40.160> talk<00:10:40.429> I<00:10:41.290> would<00:10:42.290> like<00:10:42.559> to 00:10:42.669 --> 00:10:42.679 align:start position:0% to finish this talk I would like to 00:10:42.679 --> 00:10:45.069 align:start position:0% to finish this talk I would like to introduce<00:10:42.829> liquid<00:10:43.279> pledging<00:10:43.819> this<00:10:44.569> is<00:10:44.689> one<00:10:44.899> of 00:10:45.069 --> 00:10:45.079 align:start position:0% introduce liquid pledging this is one of 00:10:45.079 --> 00:10:47.410 align:start position:0% introduce liquid pledging this is one of the<00:10:45.199> main<00:10:45.379> open-source<00:10:45.949> mark<00:10:46.339> contracts<00:10:46.819> that 00:10:47.410 --> 00:10:47.420 align:start position:0% the main open-source mark contracts that 00:10:47.420 --> 00:10:49.869 align:start position:0% the main open-source mark contracts that have<00:10:47.480> been<00:10:47.990> developed<00:10:48.379> at<00:10:48.589> givethe<00:10:49.009> well<00:10:49.670> not 00:10:49.869 --> 00:10:49.879 align:start position:0% have been developed at givethe well not 00:10:49.879 --> 00:10:52.269 align:start position:0% have been developed at givethe well not exactly<00:10:50.240> a<00:10:50.509> token<00:10:50.869> contract<00:10:51.319> it<00:10:51.589> extends<00:10:52.129> some 00:10:52.269 --> 00:10:52.279 align:start position:0% exactly a token contract it extends some 00:10:52.279 --> 00:10:54.280 align:start position:0% exactly a token contract it extends some powerful<00:10:52.790> functionality<00:10:53.209> that<00:10:53.929> can<00:10:54.170> be 00:10:54.280 --> 00:10:54.290 align:start position:0% powerful functionality that can be 00:10:54.290 --> 00:10:57.340 align:start position:0% powerful functionality that can be applied<00:10:54.589> to<00:10:54.889> any<00:10:55.279> token<00:10:55.869> what's<00:10:56.869> liquid 00:10:57.340 --> 00:10:57.350 align:start position:0% applied to any token what's liquid 00:10:57.350 --> 00:11:00.910 align:start position:0% applied to any token what's liquid pledging<00:10:57.740> about<00:10:58.779> liquid<00:10:59.779> pledging<00:11:00.259> is<00:11:00.410> where 00:11:00.910 --> 00:11:00.920 align:start position:0% pledging about liquid pledging is where 00:11:00.920 --> 00:11:04.350 align:start position:0% pledging about liquid pledging is where requite<00:11:01.279> democracy<00:11:01.850> meets<00:11:02.389> fund<00:11:03.199> management 00:11:04.350 --> 00:11:04.360 align:start position:0% requite democracy meets fund management 00:11:04.360 --> 00:11:06.240 align:start position:0% requite democracy meets fund management essentially<00:11:05.360> you<00:11:05.660> can 00:11:06.240 --> 00:11:06.250 align:start position:0% essentially you can 00:11:06.250 --> 00:11:09.420 align:start position:0% essentially you can your<00:11:06.370> tokens<00:11:06.820> or<00:11:07.120> let<00:11:07.990> someone<00:11:08.290> else<00:11:08.500> manage 00:11:09.420 --> 00:11:09.430 align:start position:0% your tokens or let someone else manage 00:11:09.430 --> 00:11:12.960 align:start position:0% your tokens or let someone else manage them<00:11:09.760> with<00:11:10.420> oversight<00:11:11.280> with<00:11:12.280> a<00:11:12.310> normal<00:11:12.730> wallet 00:11:12.960 --> 00:11:12.970 align:start position:0% them with oversight with a normal wallet 00:11:12.970 --> 00:11:15.000 align:start position:0% them with oversight with a normal wallet you<00:11:13.540> manage<00:11:13.870> your<00:11:13.960> tokens<00:11:14.440> you<00:11:14.800> have<00:11:14.980> a 00:11:15.000 --> 00:11:15.010 align:start position:0% you manage your tokens you have a 00:11:15.010 --> 00:11:16.890 align:start position:0% you manage your tokens you have a balance<00:11:15.430> you<00:11:15.730> have<00:11:15.910> transfer<00:11:16.390> functions 00:11:16.890 --> 00:11:16.900 align:start position:0% balance you have transfer functions 00:11:16.900 --> 00:11:19.680 align:start position:0% balance you have transfer functions inputs<00:11:17.680> outputs<00:11:17.860> and<00:11:18.490> that's<00:11:19.090> effectively 00:11:19.680 --> 00:11:19.690 align:start position:0% inputs outputs and that's effectively 00:11:19.690 --> 00:11:23.070 align:start position:0% inputs outputs and that's effectively all<00:11:19.990> with<00:11:20.920> liquid<00:11:21.280> pledging<00:11:21.790> not<00:11:22.000> only<00:11:22.930> you 00:11:23.070 --> 00:11:23.080 align:start position:0% all with liquid pledging not only you 00:11:23.080 --> 00:11:25.920 align:start position:0% all with liquid pledging not only you can<00:11:23.350> manage<00:11:23.620> your<00:11:23.980> own<00:11:24.220> tokens<00:11:24.760> but<00:11:25.480> you<00:11:25.720> can 00:11:25.920 --> 00:11:25.930 align:start position:0% can manage your own tokens but you can 00:11:25.930 --> 00:11:29.940 align:start position:0% can manage your own tokens but you can also<00:11:26.110> manage<00:11:26.560> someone<00:11:27.400> else's<00:11:27.760> tokens<00:11:28.770> you<00:11:29.770> do 00:11:29.940 --> 00:11:29.950 align:start position:0% also manage someone else's tokens you do 00:11:29.950 --> 00:11:33.090 align:start position:0% also manage someone else's tokens you do this<00:11:30.160> by<00:11:30.610> creating<00:11:30.670> a<00:11:31.390> hierarchical<00:11:32.290> chain<00:11:32.830> of 00:11:33.090 --> 00:11:33.100 align:start position:0% this by creating a hierarchical chain of 00:11:33.100 --> 00:11:35.550 align:start position:0% this by creating a hierarchical chain of delegation<00:11:33.730> you<00:11:33.910> can<00:11:34.360> give<00:11:34.600> the<00:11:34.810> authority<00:11:35.380> of 00:11:35.550 --> 00:11:35.560 align:start position:0% delegation you can give the authority of 00:11:35.560 --> 00:11:37.890 align:start position:0% delegation you can give the authority of the<00:11:35.920> tokens<00:11:36.280> to<00:11:36.700> a<00:11:36.730> delegate<00:11:37.210> the<00:11:37.480> delegate 00:11:37.890 --> 00:11:37.900 align:start position:0% the tokens to a delegate the delegate 00:11:37.900 --> 00:11:40.140 align:start position:0% the tokens to a delegate the delegate can<00:11:38.260> do<00:11:38.440> the<00:11:38.590> same<00:11:38.800> with<00:11:39.220> a<00:11:39.280> sub<00:11:39.520> delegate<00:11:39.910> and 00:11:40.140 --> 00:11:40.150 align:start position:0% can do the same with a sub delegate and 00:11:40.150 --> 00:11:45.150 align:start position:0% can do the same with a sub delegate and so<00:11:40.420> on<00:11:42.120> the<00:11:43.120> most<00:11:43.360> important<00:11:43.930> feature<00:11:44.200> is<00:11:44.740> that 00:11:45.150 --> 00:11:45.160 align:start position:0% so on the most important feature is that 00:11:45.160 --> 00:11:47.100 align:start position:0% so on the most important feature is that after<00:11:45.580> you<00:11:45.730> delegate<00:11:46.120> the<00:11:46.300> tokens<00:11:46.690> you<00:11:46.990> are 00:11:47.100 --> 00:11:47.110 align:start position:0% after you delegate the tokens you are 00:11:47.110 --> 00:11:49.370 align:start position:0% after you delegate the tokens you are still<00:11:47.530> empowered<00:11:48.100> to<00:11:48.460> make<00:11:49.030> decisions 00:11:49.370 --> 00:11:49.380 align:start position:0% still empowered to make decisions 00:11:49.380 --> 00:11:53.190 align:start position:0% still empowered to make decisions regarding<00:11:50.380> the<00:11:50.980> use<00:11:51.190> of<00:11:51.220> these<00:11:51.670> tokens<00:11:51.910> as<00:11:52.330> the 00:11:53.190 --> 00:11:53.200 align:start position:0% regarding the use of these tokens as the 00:11:53.200 --> 00:11:57.480 align:start position:0% regarding the use of these tokens as the owner<00:11:53.380> you<00:11:53.980> have<00:11:54.310> the<00:11:54.610> complete<00:11:55.000> oversight<00:11:56.490> to 00:11:57.480 --> 00:11:57.490 align:start position:0% owner you have the complete oversight to 00:11:57.490 --> 00:12:02.930 align:start position:0% owner you have the complete oversight to make<00:11:57.640> it<00:11:57.790> clear<00:11:58.030> let<00:11:58.570> me<00:11:58.690> give<00:11:58.900> you<00:11:59.050> an<00:11:59.290> example 00:12:02.930 --> 00:12:02.940 align:start position:0% 00:12:02.940 --> 00:12:06.200 align:start position:0% gap<00:12:03.940> is<00:12:04.300> a<00:12:04.360> community<00:12:05.230> member 00:12:06.200 --> 00:12:06.210 align:start position:0% gap is a community member 00:12:06.210 --> 00:12:09.240 align:start position:0% gap is a community member that's<00:12:07.210> very<00:12:07.510> concerned<00:12:08.050> for<00:12:08.560> security<00:12:09.100> in 00:12:09.240 --> 00:12:09.250 align:start position:0% that's very concerned for security in 00:12:09.250 --> 00:12:12.030 align:start position:0% that's very concerned for security in the<00:12:09.340> blockchain<00:12:09.550> and<00:12:09.970> once<00:12:10.480> to<00:12:10.570> the<00:12:10.660> Nate<00:12:11.040> 100 00:12:12.030 --> 00:12:12.040 align:start position:0% the blockchain and once to the Nate 100 00:12:12.040 --> 00:12:16.040 align:start position:0% the blockchain and once to the Nate 100 inner<00:12:13.260> two<00:12:14.260> projects<00:12:14.860> that<00:12:15.160> improve<00:12:15.310> security 00:12:16.040 --> 00:12:16.050 align:start position:0% inner two projects that improve security 00:12:16.050 --> 00:12:20.190 align:start position:0% inner two projects that improve security he<00:12:17.050> wants<00:12:17.410> to<00:12:17.560> do<00:12:18.040> good<00:12:18.360> but<00:12:19.360> he<00:12:19.630> is<00:12:19.690> very<00:12:19.780> busy 00:12:20.190 --> 00:12:20.200 align:start position:0% he wants to do good but he is very busy 00:12:20.200 --> 00:12:22.500 align:start position:0% he wants to do good but he is very busy person<00:12:20.470> and<00:12:20.830> don't<00:12:21.580> have<00:12:21.940> the<00:12:22.210> time<00:12:22.480> to 00:12:22.500 --> 00:12:22.510 align:start position:0% person and don't have the time to 00:12:22.510 --> 00:12:25.920 align:start position:0% person and don't have the time to analyze<00:12:22.870> all<00:12:23.470> the<00:12:23.860> projects<00:12:24.310> in<00:12:24.430> the<00:12:24.520> space<00:12:24.930> on 00:12:25.920 --> 00:12:25.930 align:start position:0% analyze all the projects in the space on 00:12:25.930 --> 00:12:28.980 align:start position:0% analyze all the projects in the space on the<00:12:26.380> other<00:12:26.470> hand<00:12:26.860> we<00:12:27.400> have<00:12:27.580> wookie<00:12:27.970> who<00:12:28.900> is 00:12:28.980 --> 00:12:28.990 align:start position:0% the other hand we have wookie who is 00:12:28.990 --> 00:12:30.840 align:start position:0% the other hand we have wookie who is very<00:12:29.170> active<00:12:29.410> member<00:12:29.980> of<00:12:30.010> the<00:12:30.130> community<00:12:30.250> and 00:12:30.840 --> 00:12:30.850 align:start position:0% very active member of the community and 00:12:30.850 --> 00:12:33.980 align:start position:0% very active member of the community and also<00:12:31.780> very<00:12:32.110> much<00:12:32.350> concerned<00:12:32.890> with<00:12:33.100> security 00:12:33.980 --> 00:12:33.990 align:start position:0% also very much concerned with security 00:12:33.990 --> 00:12:37.170 align:start position:0% also very much concerned with security he<00:12:34.990> has<00:12:35.230> complete<00:12:35.680> overs<00:12:35.980> overview<00:12:36.520> of<00:12:36.700> all 00:12:37.170 --> 00:12:37.180 align:start position:0% he has complete overs overview of all 00:12:37.180 --> 00:12:40.079 align:start position:0% he has complete overs overview of all the<00:12:37.330> projects<00:12:37.810> in<00:12:37.900> the<00:12:37.990> space<00:12:38.230> and<00:12:38.530> know<00:12:39.160> which 00:12:40.079 --> 00:12:40.089 align:start position:0% the projects in the space and know which 00:12:40.089 --> 00:12:43.470 align:start position:0% the projects in the space and know which key<00:12:40.450> projects<00:12:41.020> should<00:12:41.350> be<00:12:41.410> supported<00:12:42.480> with 00:12:43.470 --> 00:12:43.480 align:start position:0% key projects should be supported with 00:12:43.480 --> 00:12:46.470 align:start position:0% key projects should be supported with liquid<00:12:43.839> pledging<00:12:44.320> gap<00:12:44.860> can<00:12:45.310> delegate<00:12:45.880> the 00:12:46.470 --> 00:12:46.480 align:start position:0% liquid pledging gap can delegate the 00:12:46.480 --> 00:12:49.470 align:start position:0% liquid pledging gap can delegate the authority<00:12:46.710> over<00:12:47.710> his<00:12:47.950> 100th<00:12:48.640> ether<00:12:48.820> to<00:12:49.089> baki 00:12:49.470 --> 00:12:49.480 align:start position:0% authority over his 100th ether to baki 00:12:49.480 --> 00:12:52.860 align:start position:0% authority over his 100th ether to baki -<00:12:50.170> so<00:12:50.770> he<00:12:51.070> can<00:12:51.280> select<00:12:51.940> the<00:12:52.089> right<00:12:52.240> project 00:12:52.860 --> 00:12:52.870 align:start position:0% - so he can select the right project 00:12:52.870 --> 00:12:57.600 align:start position:0% - so he can select the right project boo-ki<00:12:53.800> decides<00:12:54.900> that<00:12:55.900> the<00:12:56.050> best<00:12:56.260> one<00:12:56.610> to 00:12:57.600 --> 00:12:57.610 align:start position:0% boo-ki decides that the best one to 00:12:57.610 --> 00:13:00.000 align:start position:0% boo-ki decides that the best one to support<00:12:58.030> is<00:12:58.270> the<00:12:59.050> two<00:12:59.260> factor<00:12:59.680> authentication 00:13:00.000 --> 00:13:00.010 align:start position:0% support is the two factor authentication 00:13:00.010 --> 00:13:03.420 align:start position:0% support is the two factor authentication frost<00:13:00.670> project<00:13:01.210> for<00:13:01.390> my<00:13:01.540> other<00:13:01.690> world<00:13:02.050> so<00:13:02.800> he 00:13:03.420 --> 00:13:03.430 align:start position:0% frost project for my other world so he 00:13:03.430 --> 00:13:08.250 align:start position:0% frost project for my other world so he pre-commit<00:13:03.970> the<00:13:04.570> aether<00:13:05.460> at<00:13:06.460> this<00:13:06.760> point<00:13:07.260> Deb 00:13:08.250 --> 00:13:08.260 align:start position:0% pre-commit the aether at this point Deb 00:13:08.260 --> 00:13:10.350 align:start position:0% pre-commit the aether at this point Deb has<00:13:08.560> three<00:13:09.040> days<00:13:09.250> or<00:13:09.640> any<00:13:09.910> time 00:13:10.350 --> 00:13:10.360 align:start position:0% has three days or any time 00:13:10.360 --> 00:13:13.860 align:start position:0% has three days or any time pre-configured<00:13:11.050> to<00:13:11.920> veto<00:13:12.250> if<00:13:12.790> he<00:13:13.570> done 00:13:13.860 --> 00:13:13.870 align:start position:0% pre-configured to veto if he done 00:13:13.870 --> 00:13:16.980 align:start position:0% pre-configured to veto if he done doesn't<00:13:14.530> if<00:13:15.100> he<00:13:15.310> does<00:13:15.459> not<00:13:15.640> agree<00:13:15.910> with<00:13:16.209> bogies 00:13:16.980 --> 00:13:16.990 align:start position:0% doesn't if he does not agree with bogies 00:13:16.990 --> 00:13:20.009 align:start position:0% doesn't if he does not agree with bogies choice<00:13:17.290> but<00:13:18.100> if<00:13:18.339> he<00:13:18.670> does<00:13:18.970> nothing 00:13:20.009 --> 00:13:20.019 align:start position:0% choice but if he does nothing 00:13:20.019 --> 00:13:21.689 align:start position:0% choice but if he does nothing my<00:13:20.170> the<00:13:20.230> wallet<00:13:20.739> project<00:13:21.160> is<00:13:21.309> a<00:13:21.579> great 00:13:21.689 --> 00:13:21.699 align:start position:0% my the wallet project is a great 00:13:21.699 --> 00:13:26.879 align:start position:0% my the wallet project is a great supporter<00:13:24.779> this<00:13:25.779> can<00:13:26.079> be<00:13:26.199> a<00:13:26.230> normal<00:13:26.410> account 00:13:26.879 --> 00:13:26.889 align:start position:0% supporter this can be a normal account 00:13:26.889 --> 00:13:29.040 align:start position:0% supporter this can be a normal account or<00:13:27.160> it<00:13:27.369> can<00:13:27.489> have<00:13:27.730> a<00:13:27.759> smart<00:13:28.119> contract<00:13:28.360> plug-in 00:13:29.040 --> 00:13:29.050 align:start position:0% or it can have a smart contract plug-in 00:13:29.050 --> 00:13:33.329 align:start position:0% or it can have a smart contract plug-in attached<00:13:29.470> where<00:13:30.220> a<00:13:30.249> reviewer<00:13:32.069> let's<00:13:33.069> call 00:13:33.329 --> 00:13:33.339 align:start position:0% attached where a reviewer let's call 00:13:33.339 --> 00:13:35.790 align:start position:0% attached where a reviewer let's call this<00:13:33.519> reviewer<00:13:33.910> grief<00:13:34.149> if<00:13:34.569> grief<00:13:35.290> decides 00:13:35.790 --> 00:13:35.800 align:start position:0% this reviewer grief if grief decides 00:13:35.800 --> 00:13:41.009 align:start position:0% this reviewer grief if grief decides that<00:13:36.339> the<00:13:37.149> work<00:13:37.360> is<00:13:37.569> done<00:13:37.600> the<00:13:38.439> ether<00:13:38.829> go<00:13:40.019> to 00:13:41.009 --> 00:13:41.019 align:start position:0% that the work is done the ether go to 00:13:41.019 --> 00:13:43.679 align:start position:0% that the work is done the ether go to tailor<00:13:41.679> for<00:13:42.279> successfully<00:13:43.059> implementing 00:13:43.679 --> 00:13:43.689 align:start position:0% tailor for successfully implementing 00:13:43.689 --> 00:13:47.970 align:start position:0% tailor for successfully implementing two-factor<00:13:44.230> authentication<00:13:45.869> but<00:13:46.869> if<00:13:47.199> the 00:13:47.970 --> 00:13:47.980 align:start position:0% two-factor authentication but if the 00:13:47.980 --> 00:13:50.160 align:start position:0% two-factor authentication but if the project<00:13:48.369> does<00:13:48.519> not<00:13:48.549> meet<00:13:48.910> the<00:13:49.089> conditions<00:13:49.600> it 00:13:50.160 --> 00:13:50.170 align:start position:0% project does not meet the conditions it 00:13:50.170 --> 00:13:52.470 align:start position:0% project does not meet the conditions it in<00:13:50.619> the<00:13:50.769> in<00:13:50.980> the<00:13:51.069> given<00:13:51.309> amount<00:13:51.489> of<00:13:51.699> time<00:13:51.759> he 00:13:52.470 --> 00:13:52.480 align:start position:0% in the in the given amount of time he 00:13:52.480 --> 00:13:55.710 align:start position:0% in the in the given amount of time he can<00:13:52.660> cancel<00:13:53.259> the<00:13:53.860> project<00:13:54.399> and<00:13:54.579> the<00:13:55.509> money 00:13:55.710 --> 00:13:55.720 align:start position:0% can cancel the project and the money 00:13:55.720 --> 00:14:00.600 align:start position:0% can cancel the project and the money goes<00:13:56.019> back<00:13:56.319> to<00:13:56.379> Buki<00:13:56.980> and<00:13:57.129> gap<00:13:57.819> and<00:13:59.309> gap<00:14:00.309> has 00:14:00.600 --> 00:14:00.610 align:start position:0% goes back to Buki and gap and gap has 00:14:00.610 --> 00:14:04.169 align:start position:0% goes back to Buki and gap and gap has again<00:14:00.970> oversight<00:14:01.929> over<00:14:02.739> how<00:14:02.980> the<00:14:03.309> 100<00:14:03.999> either 00:14:04.169 --> 00:14:04.179 align:start position:0% again oversight over how the 100 either 00:14:04.179 --> 00:14:09.229 align:start position:0% again oversight over how the 100 either can<00:14:04.509> be<00:14:04.629> used<00:14:06.299> as<00:14:07.299> you<00:14:07.540> can<00:14:07.720> see<00:14:07.959> this<00:14:08.439> contract 00:14:09.229 --> 00:14:09.239 align:start position:0% can be used as you can see this contract 00:14:09.239 --> 00:14:11.220 align:start position:0% can be used as you can see this contract has<00:14:10.239> many<00:14:10.509> advantages 00:14:11.220 --> 00:14:11.230 align:start position:0% has many advantages 00:14:11.230 --> 00:14:15.150 align:start position:0% has many advantages the<00:14:12.100> owner<00:14:12.249> has<00:14:13.089> full<00:14:13.420> control<00:14:13.959> of<00:14:14.110> the<00:14:14.769> tokens 00:14:15.150 --> 00:14:15.160 align:start position:0% the owner has full control of the tokens 00:14:15.160 --> 00:14:18.150 align:start position:0% the owner has full control of the tokens full<00:14:15.970> transparency<00:14:16.329> and<00:14:17.110> knowledge<00:14:17.679> of<00:14:17.860> where 00:14:18.150 --> 00:14:18.160 align:start position:0% full transparency and knowledge of where 00:14:18.160 --> 00:14:21.179 align:start position:0% full transparency and knowledge of where their<00:14:18.369> phones<00:14:18.639> go<00:14:18.850> I<00:14:19.259> want<00:14:20.259> to<00:14:20.319> mention<00:14:20.589> that 00:14:21.179 --> 00:14:21.189 align:start position:0% their phones go I want to mention that 00:14:21.189 --> 00:14:24.119 align:start position:0% their phones go I want to mention that this<00:14:21.369> contract<00:14:21.730> is<00:14:21.970> all<00:14:22.149> is<00:14:22.509> also<00:14:23.129> extensible 00:14:24.119 --> 00:14:24.129 align:start position:0% this contract is all is also extensible 00:14:24.129 --> 00:14:26.819 align:start position:0% this contract is all is also extensible contract<00:14:24.879> via<00:14:25.059> plugins<00:14:25.389> in<00:14:26.199> these<00:14:26.529> plugins 00:14:26.819 --> 00:14:26.829 align:start position:0% contract via plugins in these plugins 00:14:26.829 --> 00:14:29.129 align:start position:0% contract via plugins in these plugins you<00:14:27.399> can<00:14:27.429> add<00:14:27.850> a<00:14:27.879> specific<00:14:28.420> condition<00:14:28.600> like 00:14:29.129 --> 00:14:29.139 align:start position:0% you can add a specific condition like 00:14:29.139 --> 00:14:31.590 align:start position:0% you can add a specific condition like token<00:14:29.920> allocation<00:14:30.519> when<00:14:30.939> the<00:14:31.059> project<00:14:31.480> is 00:14:31.590 --> 00:14:31.600 align:start position:0% token allocation when the project is 00:14:31.600 --> 00:14:33.960 align:start position:0% token allocation when the project is phoned<00:14:31.839> or<00:14:32.069> setting<00:14:33.069> a<00:14:33.189> harp<00:14:33.459> at<00:14:33.639> for<00:14:33.850> a 00:14:33.960 --> 00:14:33.970 align:start position:0% phoned or setting a harp at for a 00:14:33.970 --> 00:14:36.410 align:start position:0% phoned or setting a harp at for a haircut<00:14:34.269> for<00:14:34.749> exceed<00:14:35.110> for<00:14:35.319> a<00:14:35.350> given<00:14:35.619> project 00:14:36.410 --> 00:14:36.420 align:start position:0% haircut for exceed for a given project 00:14:36.420 --> 00:14:39.179 align:start position:0% haircut for exceed for a given project the<00:14:37.420> liquid<00:14:37.749> pledge<00:14:37.959> account<00:14:38.439> the<00:14:38.889> liquid 00:14:39.179 --> 00:14:39.189 align:start position:0% the liquid pledge account the liquid 00:14:39.189 --> 00:14:41.730 align:start position:0% the liquid pledge account the liquid logic<00:14:39.490> contract<00:14:39.970> can<00:14:40.600> be<00:14:40.629> used<00:14:40.990> not<00:14:41.350> only<00:14:41.410> for 00:14:41.730 --> 00:14:41.740 align:start position:0% logic contract can be used not only for 00:14:41.740 --> 00:14:44.189 align:start position:0% logic contract can be used not only for donations<00:14:42.459> but<00:14:42.939> also<00:14:43.179> for<00:14:43.509> organizations 00:14:44.189 --> 00:14:44.199 align:start position:0% donations but also for organizations 00:14:44.199 --> 00:14:47.069 align:start position:0% donations but also for organizations management<00:14:44.799> in<00:14:45.220> an<00:14:45.369> organization<00:14:46.119> they<00:14:46.660> the 00:14:47.069 --> 00:14:47.079 align:start position:0% management in an organization they the 00:14:47.079 --> 00:14:49.289 align:start position:0% management in an organization they the investors<00:14:47.529> delegates<00:14:48.009> the<00:14:48.220> funds<00:14:48.490> to<00:14:48.639> Co<00:14:48.999> the 00:14:49.289 --> 00:14:49.299 align:start position:0% investors delegates the funds to Co the 00:14:49.299 --> 00:14:51.539 align:start position:0% investors delegates the funds to Co the CEO<00:14:49.660> soup<00:14:49.929> delegates<00:14:50.350> that<00:14:50.499> the<00:14:50.799> budget<00:14:51.429> to 00:14:51.539 --> 00:14:51.549 align:start position:0% CEO soup delegates that the budget to 00:14:51.549 --> 00:14:54.299 align:start position:0% CEO soup delegates that the budget to the<00:14:51.670> directors<00:14:52.420> the<00:14:52.929> city<00:14:53.170> of<00:14:53.410> delegates<00:14:54.040> to 00:14:54.299 --> 00:14:54.309 align:start position:0% the directors the city of delegates to 00:14:54.309 --> 00:14:56.970 align:start position:0% the directors the city of delegates to the<00:14:54.610> system<00:14:54.939> department<00:14:55.449> and<00:14:55.600> so<00:14:55.990> on<00:14:56.170> and<00:14:56.410> the 00:14:56.970 --> 00:14:56.980 align:start position:0% the system department and so on and the 00:14:56.980 --> 00:14:59.730 align:start position:0% the system department and so on and the investors<00:14:57.459> still<00:14:58.089> have<00:14:58.360> full<00:14:58.959> control<00:14:59.410> on 00:14:59.730 --> 00:14:59.740 align:start position:0% investors still have full control on 00:14:59.740 --> 00:15:02.539 align:start position:0% investors still have full control on where<00:15:00.160> the<00:15:00.309> funds<00:15:00.579> are<00:15:00.819> spent<00:15:01.119> and<00:15:01.569> invested 00:15:02.539 --> 00:15:02.549 align:start position:0% where the funds are spent and invested 00:15:02.549 --> 00:15:06.119 align:start position:0% where the funds are spent and invested the<00:15:03.549> same<00:15:03.790> idea<00:15:04.119> applies<00:15:04.839> in<00:15:05.259> fund<00:15:05.829> management 00:15:06.119 --> 00:15:06.129 align:start position:0% the same idea applies in fund management 00:15:06.129 --> 00:15:09.569 align:start position:0% the same idea applies in fund management where<00:15:06.970> a<00:15:07.240> delegate<00:15:08.230> pre<00:15:08.769> commits<00:15:09.160> the<00:15:09.309> ether 00:15:09.569 --> 00:15:09.579 align:start position:0% where a delegate pre commits the ether 00:15:09.579 --> 00:15:12.059 align:start position:0% where a delegate pre commits the ether to<00:15:09.759> a<00:15:09.819> specific<00:15:10.269> projects<00:15:10.809> and<00:15:10.990> the<00:15:11.619> investors 00:15:12.059 --> 00:15:12.069 align:start position:0% to a specific projects and the investors 00:15:12.069 --> 00:15:14.129 align:start position:0% to a specific projects and the investors has<00:15:12.369> the<00:15:12.610> last<00:15:12.790> word<00:15:13.059> on<00:15:13.209> where<00:15:13.809> the 00:15:14.129 --> 00:15:14.139 align:start position:0% has the last word on where the 00:15:14.139 --> 00:15:17.609 align:start position:0% has the last word on where the investment<00:15:14.740> goes<00:15:15.959> there<00:15:16.959> are<00:15:17.049> many<00:15:17.319> other 00:15:17.609 --> 00:15:17.619 align:start position:0% investment goes there are many other 00:15:17.619 --> 00:15:21.090 align:start position:0% investment goes there are many other great<00:15:18.429> ideas<00:15:18.730> one<00:15:19.509> that<00:15:19.749> I<00:15:19.779> like<00:15:20.169> a<00:15:20.199> lot<00:15:20.379> is 00:15:21.090 --> 00:15:21.100 align:start position:0% great ideas one that I like a lot is 00:15:21.100 --> 00:15:24.780 align:start position:0% great ideas one that I like a lot is liquid<00:15:21.939> lending<00:15:22.360> and<00:15:22.949> by<00:15:23.949> the<00:15:24.009> way<00:15:24.249> this<00:15:24.610> is 00:15:24.780 --> 00:15:24.790 align:start position:0% liquid lending and by the way this is 00:15:24.790 --> 00:15:27.449 align:start position:0% liquid lending and by the way this is done<00:15:24.999> from<00:15:25.689> a<00:15:25.899> startup<00:15:26.529> from<00:15:26.769> Mexico 00:15:27.449 --> 00:15:27.459 align:start position:0% done from a startup from Mexico 00:15:27.459 --> 00:15:30.869 align:start position:0% done from a startup from Mexico it's<00:15:27.730> called<00:15:28.059> Aurora<00:15:28.480> Libre<00:15:29.129> in<00:15:30.129> this<00:15:30.309> concept 00:15:30.869 --> 00:15:30.879 align:start position:0% it's called Aurora Libre in this concept 00:15:30.879 --> 00:15:34.230 align:start position:0% it's called Aurora Libre in this concept a<00:15:31.110> microcredit<00:15:32.110> is<00:15:32.740> made<00:15:33.100> via<00:15:33.519> a<00:15:33.759> higher 00:15:34.230 --> 00:15:34.240 align:start position:0% a microcredit is made via a higher 00:15:34.240 --> 00:15:41.130 align:start position:0% a microcredit is made via a higher akiko<00:15:34.570> delegation<00:15:35.260> chain<00:15:35.680> of<00:15:35.920> trust<00:15:39.899> to<00:15:40.899> wrap 00:15:41.130 --> 00:15:41.140 align:start position:0% akiko delegation chain of trust to wrap 00:15:41.140 --> 00:15:44.280 align:start position:0% akiko delegation chain of trust to wrap up<00:15:41.320> I<00:15:41.790> would<00:15:42.790> like<00:15:43.000> to<00:15:43.209> leave<00:15:43.360> you<00:15:43.390> with<00:15:43.870> three 00:15:44.280 --> 00:15:44.290 align:start position:0% up I would like to leave you with three 00:15:44.290 --> 00:15:49.680 align:start position:0% up I would like to leave you with three key<00:15:44.529> takeaways<00:15:45.990> first<00:15:47.970> if<00:15:48.970> you<00:15:49.390> need<00:15:49.540> an 00:15:49.680 --> 00:15:49.690 align:start position:0% key takeaways first if you need an 00:15:49.690 --> 00:15:52.170 align:start position:0% key takeaways first if you need an advance<00:15:49.990> talking<00:15:50.500> contract<00:15:51.070> consider<00:15:51.880> the 00:15:52.170 --> 00:15:52.180 align:start position:0% advance talking contract consider the 00:15:52.180 --> 00:15:54.060 align:start position:0% advance talking contract consider the mini-me<00:15:52.480> contract<00:15:53.020> which<00:15:53.410> has<00:15:53.649> been<00:15:53.830> fully 00:15:54.060 --> 00:15:54.070 align:start position:0% mini-me contract which has been fully 00:15:54.070 --> 00:15:58.320 align:start position:0% mini-me contract which has been fully tested<00:15:54.310> and<00:15:54.790> implemented<00:15:56.100> second<00:15:57.100> the<00:15:58.060> yoga 00:15:58.320 --> 00:15:58.330 align:start position:0% tested and implemented second the yoga 00:15:58.330 --> 00:16:01.350 align:start position:0% tested and implemented second the yoga token<00:15:58.690> it<00:15:59.230> brings<00:15:59.620> together<00:15:59.950> the<00:16:00.730> features<00:16:01.149> of 00:16:01.350 --> 00:16:01.360 align:start position:0% token it brings together the features of 00:16:01.360 --> 00:16:04.530 align:start position:0% token it brings together the features of mini-me<00:16:02.050> plus<00:16:02.440> the<00:16:02.680> year<00:16:02.860> C<00:16:03.100> 2<00:16:03.250> to<00:16:03.399> 3<00:16:03.670> with<00:16:04.120> with 00:16:04.530 --> 00:16:04.540 align:start position:0% mini-me plus the year C 2 to 3 with with 00:16:04.540 --> 00:16:08.790 align:start position:0% mini-me plus the year C 2 to 3 with with a<00:16:04.810> ip67<00:16:05.649> -<00:16:05.970> this<00:16:06.970> is<00:16:07.089> a<00:16:07.120> powerful<00:16:07.600> token<00:16:08.230> to<00:16:08.649> be 00:16:08.790 --> 00:16:08.800 align:start position:0% a ip67 - this is a powerful token to be 00:16:08.800 --> 00:16:10.980 align:start position:0% a ip67 - this is a powerful token to be considered<00:16:09.279> as<00:16:09.459> a<00:16:09.850> standard<00:16:10.390> for<00:16:10.600> the<00:16:10.660> theorem 00:16:10.980 --> 00:16:10.990 align:start position:0% considered as a standard for the theorem 00:16:10.990 --> 00:16:12.660 align:start position:0% considered as a standard for the theorem community<00:16:11.440> once<00:16:11.950> the<00:16:12.100> standards<00:16:12.520> are 00:16:12.660 --> 00:16:12.670 align:start position:0% community once the standards are 00:16:12.670 --> 00:16:16.320 align:start position:0% community once the standards are approved<00:16:13.170> and<00:16:14.170> third<00:16:14.980> the<00:16:15.550> liquid<00:16:15.910> pledging 00:16:16.320 --> 00:16:16.330 align:start position:0% approved and third the liquid pledging 00:16:16.330 --> 00:16:20.910 align:start position:0% approved and third the liquid pledging contract<00:16:17.070> could<00:16:18.070> be<00:16:18.130> ideal<00:16:19.029> I<00:16:19.440> could<00:16:20.440> be<00:16:20.560> ideal 00:16:20.910 --> 00:16:20.920 align:start position:0% contract could be ideal I could be ideal 00:16:20.920 --> 00:16:22.829 align:start position:0% contract could be ideal I could be ideal for<00:16:21.220> many<00:16:21.850> usages 00:16:22.829 --> 00:16:22.839 align:start position:0% for many usages 00:16:22.839 --> 00:16:26.940 align:start position:0% for many usages it's<00:16:23.380> especially<00:16:24.000> sweded<00:16:25.380> or<00:16:26.380> block<00:16:26.709> chain 00:16:26.940 --> 00:16:26.950 align:start position:0% it's especially sweded or block chain 00:16:26.950 --> 00:16:29.250 align:start position:0% it's especially sweded or block chain based<00:16:27.220> donation<00:16:27.730> systems<00:16:28.209> that<00:16:28.779> can<00:16:29.020> make<00:16:29.230> a 00:16:29.250 --> 00:16:29.260 align:start position:0% based donation systems that can make a 00:16:29.260 --> 00:16:31.800 align:start position:0% based donation systems that can make a world<00:16:29.560> a<00:16:29.740> better<00:16:29.830> place<00:16:30.010> but<00:16:30.790> it<00:16:31.270> could<00:16:31.570> also 00:16:31.800 --> 00:16:31.810 align:start position:0% world a better place but it could also 00:16:31.810 --> 00:16:34.380 align:start position:0% world a better place but it could also add<00:16:32.200> interesting<00:16:32.800> functionalities<00:16:33.700> for<00:16:33.940> many 00:16:34.380 --> 00:16:34.390 align:start position:0% add interesting functionalities for many 00:16:34.390 --> 00:16:40.319 align:start position:0% add interesting functionalities for many dubs<00:16:34.690> and<00:16:37.560> no<00:16:38.560> we<00:16:39.100> have<00:16:39.279> reached<00:16:39.550> the<00:16:40.000> end<00:16:40.180> of 00:16:40.319 --> 00:16:40.329 align:start position:0% dubs and no we have reached the end of 00:16:40.329 --> 00:16:43.650 align:start position:0% dubs and no we have reached the end of my<00:16:40.600> talk<00:16:40.870> I<00:16:41.370> welcome<00:16:42.370> comments<00:16:42.670> and<00:16:43.060> feedback 00:16:43.650 --> 00:16:43.660 align:start position:0% my talk I welcome comments and feedback 00:16:43.660 --> 00:16:47.519 align:start position:0% my talk I welcome comments and feedback please<00:16:44.410> feel<00:16:44.529> free<00:16:45.010> to<00:16:45.329> reach<00:16:46.329> out<00:16:46.660> to<00:16:46.810> me<00:16:47.170> to 00:16:47.519 --> 00:16:47.529 align:start position:0% please feel free to reach out to me to 00:16:47.529 --> 00:16:50.340 align:start position:0% please feel free to reach out to me to grieve<00:16:47.770> or<00:16:48.040> to<00:16:48.430> any<00:16:48.579> givethe<00:16:49.029> team<00:16:49.270> members<00:16:49.630> if 00:16:50.340 --> 00:16:50.350 align:start position:0% grieve or to any givethe team members if 00:16:50.350 --> 00:16:52.889 align:start position:0% grieve or to any givethe team members if you<00:16:50.800> want<00:16:51.040> to<00:16:51.310> learn<00:16:51.640> more<00:16:51.940> about<00:16:52.180> our<00:16:52.720> open 00:16:52.889 --> 00:16:52.899 align:start position:0% you want to learn more about our open 00:16:52.899 --> 00:16:55.199 align:start position:0% you want to learn more about our open source<00:16:53.230> contracts<00:16:53.770> you<00:16:54.160> can<00:16:54.370> always<00:16:54.610> you<00:16:55.180> can 00:16:55.199 --> 00:16:55.209 align:start position:0% source contracts you can always you can 00:16:55.209 --> 00:16:57.810 align:start position:0% source contracts you can always you can always<00:16:55.420> check<00:16:55.870> or<00:16:56.110> a<00:16:56.170> guy<00:16:56.770> giveth<00:16:57.370> dot<00:16:57.610> IO 00:16:57.810 --> 00:16:57.820 align:start position:0% always check or a guy giveth dot IO 00:16:57.820 --> 00:17:04.350 align:start position:0% always check or a guy giveth dot IO website<00:16:59.940> here<00:17:00.940> are<00:17:01.149> some<00:17:01.450> links<00:17:01.800> and<00:17:03.360> thank 00:17:04.350 --> 00:17:04.360 align:start position:0% website here are some links and thank 00:17:04.360 --> 00:17:06.150 align:start position:0% website here are some links and thank you<00:17:04.510> to<00:17:04.630> the<00:17:04.720> foundation<00:17:05.199> for<00:17:05.410> having<00:17:05.709> me<00:17:05.829> here 00:17:06.150 --> 00:17:06.160 align:start position:0% you to the foundation for having me here 00:17:06.160 --> 00:17:08.400 align:start position:0% you to the foundation for having me here and<00:17:06.339> thank<00:17:06.819> you<00:17:06.850> to<00:17:07.089> all<00:17:07.689> of<00:17:07.929> you<00:17:08.050> for<00:17:08.290> your 00:17:08.400 --> 00:17:08.410 align:start position:0% and thank you to all of you for your 00:17:08.410 --> 00:17:10.930 align:start position:0% and thank you to all of you for your attention 00:17:10.930 --> 00:17:10.940 align:start position:0% 00:17:10.940 --> 00:17:16.010 align:start position:0% [Applause] 00:17:16.010 --> 00:17:16.020 align:start position:0% 00:17:16.020 --> 00:17:17.140 align:start position:0% you 00:17:17.140 --> 00:17:17.150 align:start position:0% you 00:17:17.150 --> 00:17:24.729 align:start position:0% you [Music]