WEBVTT Kind: captions Language: en 00:00:00.030 --> 00:00:02.330 align:start position:0% those<00:00:00.780> of<00:00:00.960> you<00:00:01.050> who<00:00:01.230> are<00:00:01.290> here<00:00:01.500> last<00:00:01.770> year<00:00:01.920> and 00:00:02.330 --> 00:00:02.340 align:start position:0% those of you who are here last year and 00:00:02.340 --> 00:00:03.770 align:start position:0% those of you who are here last year and happened<00:00:02.760> to<00:00:02.850> come<00:00:03.030> to<00:00:03.149> our<00:00:03.210> talk<00:00:03.480> might 00:00:03.770 --> 00:00:03.780 align:start position:0% happened to come to our talk might 00:00:03.780 --> 00:00:06.710 align:start position:0% happened to come to our talk might recall<00:00:04.110> ether<00:00:04.529> meant<00:00:04.710> a<00:00:04.859> 1.0<00:00:05.580> well<00:00:06.270> we're<00:00:06.480> back 00:00:06.710 --> 00:00:06.720 align:start position:0% recall ether meant a 1.0 well we're back 00:00:06.720 --> 00:00:09.049 align:start position:0% recall ether meant a 1.0 well we're back in<00:00:07.080> ether<00:00:07.560> MIT<00:00:07.710> is<00:00:07.830> back<00:00:08.040> but<00:00:08.429> this<00:00:08.550> time<00:00:08.610> it's 00:00:09.049 --> 00:00:09.059 align:start position:0% in ether MIT is back but this time it's 00:00:09.059 --> 00:00:11.209 align:start position:0% in ether MIT is back but this time it's better<00:00:09.269> so<00:00:09.990> I'm<00:00:10.139> gonna<00:00:10.260> talk<00:00:10.530> about<00:00:10.559> ether<00:00:11.070> at 00:00:11.209 --> 00:00:11.219 align:start position:0% better so I'm gonna talk about ether at 00:00:11.219 --> 00:00:13.730 align:start position:0% better so I'm gonna talk about ether at 2.0<00:00:11.759> which<00:00:12.090> combines<00:00:12.509> the<00:00:12.750> best<00:00:12.960> features<00:00:13.080> we 00:00:13.730 --> 00:00:13.740 align:start position:0% 2.0 which combines the best features we 00:00:13.740 --> 00:00:16.129 align:start position:0% 2.0 which combines the best features we think<00:00:14.009> of<00:00:14.429> aetherium<00:00:14.820> the<00:00:15.210> EVM<00:00:15.570> and<00:00:15.900> the<00:00:15.960> best 00:00:16.129 --> 00:00:16.139 align:start position:0% think of aetherium the EVM and the best 00:00:16.139 --> 00:00:18.140 align:start position:0% think of aetherium the EVM and the best features<00:00:16.440> of<00:00:16.470> the<00:00:16.680> cosmos<00:00:17.070> SDK<00:00:17.580> and<00:00:17.820> tender 00:00:18.140 --> 00:00:18.150 align:start position:0% features of the cosmos SDK and tender 00:00:18.150 --> 00:00:21.560 align:start position:0% features of the cosmos SDK and tender mint<00:00:18.300> in<00:00:19.010> this<00:00:20.010> presentation<00:00:20.520> first<00:00:21.150> I'll 00:00:21.560 --> 00:00:21.570 align:start position:0% mint in this presentation first I'll 00:00:21.570 --> 00:00:23.750 align:start position:0% mint in this presentation first I'll give<00:00:22.050> a<00:00:22.080> quick<00:00:22.230> overview<00:00:22.619> of<00:00:22.740> cosmos<00:00:23.220> explain 00:00:23.750 --> 00:00:23.760 align:start position:0% give a quick overview of cosmos explain 00:00:23.760 --> 00:00:25.849 align:start position:0% give a quick overview of cosmos explain the<00:00:23.880> network<00:00:24.150> model<00:00:24.420> the<00:00:24.990> topology<00:00:25.289> why<00:00:25.740> we 00:00:25.849 --> 00:00:25.859 align:start position:0% the network model the topology why we 00:00:25.859 --> 00:00:27.800 align:start position:0% the network model the topology why we think<00:00:26.039> it<00:00:26.130> makes<00:00:26.279> sense<00:00:26.369> I'll<00:00:27.000> talk<00:00:27.420> about<00:00:27.449> the 00:00:27.800 --> 00:00:27.810 align:start position:0% think it makes sense I'll talk about the 00:00:27.810 --> 00:00:29.689 align:start position:0% think it makes sense I'll talk about the feature<00:00:28.019> set<00:00:28.320> of<00:00:28.349> the<00:00:28.470> cosmos<00:00:28.949> SDK<00:00:29.429> in 00:00:29.689 --> 00:00:29.699 align:start position:0% feature set of the cosmos SDK in 00:00:29.699 --> 00:00:31.700 align:start position:0% feature set of the cosmos SDK in particular<00:00:30.359> and<00:00:30.720> how<00:00:30.840> it<00:00:30.990> can<00:00:31.109> be<00:00:31.260> combined 00:00:31.700 --> 00:00:31.710 align:start position:0% particular and how it can be combined 00:00:31.710 --> 00:00:33.979 align:start position:0% particular and how it can be combined with<00:00:31.920> the<00:00:32.430> EVM<00:00:32.820> and<00:00:33.120> I'll<00:00:33.540> give<00:00:33.719> a<00:00:33.750> quick 00:00:33.979 --> 00:00:33.989 align:start position:0% with the EVM and I'll give a quick 00:00:33.989 --> 00:00:35.959 align:start position:0% with the EVM and I'll give a quick background<00:00:34.079> on<00:00:34.739> tournament<00:00:35.190> consensus<00:00:35.730> and 00:00:35.959 --> 00:00:35.969 align:start position:0% background on tournament consensus and 00:00:35.969 --> 00:00:37.940 align:start position:0% background on tournament consensus and how<00:00:36.059> it<00:00:36.180> facilitates<00:00:36.809> this<00:00:37.410> model<00:00:37.829> of 00:00:37.940 --> 00:00:37.950 align:start position:0% how it facilitates this model of 00:00:37.950 --> 00:00:39.229 align:start position:0% how it facilitates this model of interconnected<00:00:38.610> blockchains 00:00:39.229 --> 00:00:39.239 align:start position:0% interconnected blockchains 00:00:39.239 --> 00:00:42.229 align:start position:0% interconnected blockchains then<00:00:40.050> we'll<00:00:40.440> talk<00:00:40.620> all<00:00:40.860> about<00:00:40.890> Ethernet<00:00:41.700> 2.0 00:00:42.229 --> 00:00:42.239 align:start position:0% then we'll talk all about Ethernet 2.0 00:00:42.239 --> 00:00:44.420 align:start position:0% then we'll talk all about Ethernet 2.0 I'll<00:00:42.660> outline<00:00:43.140> the<00:00:43.320> architecture<00:00:43.980> the<00:00:44.190> chains 00:00:44.420 --> 00:00:44.430 align:start position:0% I'll outline the architecture the chains 00:00:44.430 --> 00:00:46.670 align:start position:0% I'll outline the architecture the chains will<00:00:44.610> be<00:00:44.640> made<00:00:44.940> from<00:00:45.149> ether<00:00:45.450> mint<00:00:45.629> 1.0<00:00:46.140> and<00:00:46.469> why 00:00:46.670 --> 00:00:46.680 align:start position:0% will be made from ether mint 1.0 and why 00:00:46.680 --> 00:00:49.369 align:start position:0% will be made from ether mint 1.0 and why I'll<00:00:47.129> talk<00:00:47.760> about<00:00:47.789> how<00:00:48.180> the<00:00:48.239> EVM<00:00:48.809> and<00:00:48.989> the<00:00:49.050> SDK 00:00:49.369 --> 00:00:49.379 align:start position:0% I'll talk about how the EVM and the SDK 00:00:49.379 --> 00:00:51.380 align:start position:0% I'll talk about how the EVM and the SDK can<00:00:49.649> work<00:00:49.829> together<00:00:50.010> to<00:00:50.489> give<00:00:50.910> you<00:00:51.059> native 00:00:51.380 --> 00:00:51.390 align:start position:0% can work together to give you native 00:00:51.390 --> 00:00:53.600 align:start position:0% can work together to give you native code<00:00:51.660> and<00:00:51.899> EVM<00:00:52.530> contracts<00:00:53.039> all<00:00:53.309> in<00:00:53.460> one 00:00:53.600 --> 00:00:53.610 align:start position:0% code and EVM contracts all in one 00:00:53.610 --> 00:00:56.840 align:start position:0% code and EVM contracts all in one blockchain<00:00:54.260> I'll<00:00:55.260> talk<00:00:55.530> about<00:00:55.559> finally<00:00:56.399> how 00:00:56.840 --> 00:00:56.850 align:start position:0% blockchain I'll talk about finally how 00:00:56.850 --> 00:00:59.150 align:start position:0% blockchain I'll talk about finally how you<00:00:56.910> can<00:00:57.239> move<00:00:57.480> your<00:00:57.930> DAPs<00:00:58.230> or<00:00:58.590> move<00:00:58.739> parts<00:00:59.039> of 00:00:59.150 --> 00:00:59.160 align:start position:0% you can move your DAPs or move parts of 00:00:59.160 --> 00:01:00.920 align:start position:0% you can move your DAPs or move parts of your<00:00:59.309> jobs<00:00:59.579> on<00:00:59.910> to<00:01:00.120> the<00:01:00.210> ether<00:01:00.510> mint<00:01:00.690> chain 00:01:00.920 --> 00:01:00.930 align:start position:0% your jobs on to the ether mint chain 00:01:00.930 --> 00:01:04.219 align:start position:0% your jobs on to the ether mint chain while<00:01:01.620> preserving<00:01:02.039> seamless<00:01:02.640> UX<00:01:03.149> and<00:01:03.510> I'll 00:01:04.219 --> 00:01:04.229 align:start position:0% while preserving seamless UX and I'll 00:01:04.229 --> 00:01:05.469 align:start position:0% while preserving seamless UX and I'll take<00:01:04.379> any<00:01:04.530> questions 00:01:05.469 --> 00:01:05.479 align:start position:0% take any questions 00:01:05.479 --> 00:01:09.859 align:start position:0% take any questions so<00:01:06.479> first<00:01:07.110> the<00:01:07.920> cosmos<00:01:08.400> model<00:01:08.939> envisions<00:01:09.600> a 00:01:09.859 --> 00:01:09.869 align:start position:0% so first the cosmos model envisions a 00:01:09.869 --> 00:01:11.570 align:start position:0% so first the cosmos model envisions a network<00:01:10.229> of<00:01:10.380> interconnected<00:01:10.680> block<00:01:11.280> chains 00:01:11.570 --> 00:01:11.580 align:start position:0% network of interconnected block chains 00:01:11.580 --> 00:01:13.670 align:start position:0% network of interconnected block chains in<00:01:11.909> many<00:01:12.600> ways<00:01:12.810> these<00:01:13.020> block<00:01:13.229> chains<00:01:13.470> will<00:01:13.619> be 00:01:13.670 --> 00:01:13.680 align:start position:0% in many ways these block chains will be 00:01:13.680 --> 00:01:15.230 align:start position:0% in many ways these block chains will be application-specific<00:01:14.340> they<00:01:14.820> will<00:01:14.970> do<00:01:15.060> lots 00:01:15.230 --> 00:01:15.240 align:start position:0% application-specific they will do lots 00:01:15.240 --> 00:01:16.580 align:start position:0% application-specific they will do lots of<00:01:15.360> different<00:01:15.479> things<00:01:15.869> but<00:01:16.080> talk<00:01:16.320> to<00:01:16.470> each 00:01:16.580 --> 00:01:16.590 align:start position:0% of different things but talk to each 00:01:16.590 --> 00:01:18.859 align:start position:0% of different things but talk to each other<00:01:16.799> in<00:01:17.460> order<00:01:17.610> to<00:01:17.820> facilitate<00:01:17.970> this<00:01:18.570> we 00:01:18.859 --> 00:01:18.869 align:start position:0% other in order to facilitate this we 00:01:18.869 --> 00:01:20.929 align:start position:0% other in order to facilitate this we need<00:01:19.020> to<00:01:19.140> make<00:01:19.259> it<00:01:19.409> really<00:01:19.710> easy<00:01:19.740> to<00:01:20.340> build<00:01:20.729> an 00:01:20.929 --> 00:01:20.939 align:start position:0% need to make it really easy to build an 00:01:20.939 --> 00:01:23.359 align:start position:0% need to make it really easy to build an application-specific<00:01:21.570> block<00:01:22.200> chain<00:01:22.439> to<00:01:23.250> do 00:01:23.359 --> 00:01:23.369 align:start position:0% application-specific block chain to do 00:01:23.369 --> 00:01:25.969 align:start position:0% application-specific block chain to do that<00:01:23.549> we've<00:01:23.850> built<00:01:24.060> the<00:01:24.270> cosmos<00:01:24.689> SDK<00:01:25.170> the 00:01:25.969 --> 00:01:25.979 align:start position:0% that we've built the cosmos SDK the 00:01:25.979 --> 00:01:27.740 align:start position:0% that we've built the cosmos SDK the cosmos<00:01:26.340> SDK<00:01:26.790> is<00:01:26.909> a<00:01:26.939> framework<00:01:27.330> for<00:01:27.720> building 00:01:27.740 --> 00:01:27.750 align:start position:0% cosmos SDK is a framework for building 00:01:27.750 --> 00:01:30.230 align:start position:0% cosmos SDK is a framework for building custom<00:01:28.380> state<00:01:28.619> machines<00:01:29.009> it<00:01:29.400> contains<00:01:30.000> all 00:01:30.230 --> 00:01:30.240 align:start position:0% custom state machines it contains all 00:01:30.240 --> 00:01:32.749 align:start position:0% custom state machines it contains all the<00:01:30.270> glue<00:01:31.079> library<00:01:31.680> code<00:01:31.890> of<00:01:32.070> blockchains 00:01:32.749 --> 00:01:32.759 align:start position:0% the glue library code of blockchains 00:01:32.759 --> 00:01:37.219 align:start position:0% the glue library code of blockchains AVL<00:01:33.540> trees<00:01:34.430> message<00:01:35.430> handlers<00:01:35.880> all<00:01:36.240> the<00:01:36.780> logic 00:01:37.219 --> 00:01:37.229 align:start position:0% AVL trees message handlers all the logic 00:01:37.229 --> 00:01:39.649 align:start position:0% AVL trees message handlers all the logic to<00:01:37.350> knit<00:01:37.530> modules<00:01:37.950> together<00:01:38.100> super<00:01:39.090> developer 00:01:39.649 --> 00:01:39.659 align:start position:0% to knit modules together super developer 00:01:39.659 --> 00:01:41.210 align:start position:0% to knit modules together super developer friendly<00:01:39.960> it's<00:01:40.200> written<00:01:40.409> in<00:01:40.560> golang<00:01:40.979> which 00:01:41.210 --> 00:01:41.220 align:start position:0% friendly it's written in golang which 00:01:41.220 --> 00:01:42.740 align:start position:0% friendly it's written in golang which many<00:01:41.430> of<00:01:41.520> you<00:01:41.640> are<00:01:41.790> probably<00:01:41.909> familiar<00:01:42.299> with 00:01:42.740 --> 00:01:42.750 align:start position:0% many of you are probably familiar with 00:01:42.750 --> 00:01:45.889 align:start position:0% many of you are probably familiar with it's<00:01:43.409> all<00:01:43.530> open<00:01:43.740> source<00:01:44.100> on<00:01:44.310> github<00:01:44.899> the 00:01:45.889 --> 00:01:45.899 align:start position:0% it's all open source on github the 00:01:45.899 --> 00:01:47.719 align:start position:0% it's all open source on github the Kosmos<00:01:46.200> sdk<00:01:46.560> is<00:01:46.590> designed<00:01:46.979> in<00:01:47.100> particular<00:01:47.549> to 00:01:47.719 --> 00:01:47.729 align:start position:0% Kosmos sdk is designed in particular to 00:01:47.729 --> 00:01:49.609 align:start position:0% Kosmos sdk is designed in particular to be<00:01:47.850> secure<00:01:48.270> to<00:01:48.540> make<00:01:48.659> it<00:01:48.780> easy<00:01:48.960> to<00:01:49.079> use 00:01:49.609 --> 00:01:49.619 align:start position:0% be secure to make it easy to use 00:01:49.619 --> 00:01:51.109 align:start position:0% be secure to make it easy to use different<00:01:49.979> modules<00:01:50.399> which<00:01:50.579> do<00:01:50.759> different 00:01:51.109 --> 00:01:51.119 align:start position:0% different modules which do different 00:01:51.119 --> 00:01:52.789 align:start position:0% different modules which do different things<00:01:51.149> which<00:01:52.049> can<00:01:52.229> interact<00:01:52.590> with<00:01:52.680> each 00:01:52.789 --> 00:01:52.799 align:start position:0% things which can interact with each 00:01:52.799 --> 00:01:55.399 align:start position:0% things which can interact with each other<00:01:53.040> but<00:01:53.759> where<00:01:54.030> you<00:01:54.149> can<00:01:54.360> control<00:01:54.780> the<00:01:55.229> ways 00:01:55.399 --> 00:01:55.409 align:start position:0% other but where you can control the ways 00:01:55.409 --> 00:01:57.319 align:start position:0% other but where you can control the ways in<00:01:55.649> which<00:01:55.680> they<00:01:55.920> interact<00:01:56.100> so<00:01:56.670> you<00:01:56.729> can 00:01:57.319 --> 00:01:57.329 align:start position:0% in which they interact so you can 00:01:57.329 --> 00:01:59.929 align:start position:0% in which they interact so you can mitigate<00:01:57.509> unintended<00:01:58.469> consequences<00:01:59.219> to<00:01:59.820> do 00:01:59.929 --> 00:01:59.939 align:start position:0% mitigate unintended consequences to do 00:01:59.939 --> 00:02:01.219 align:start position:0% mitigate unintended consequences to do this<00:02:00.119> we<00:02:00.299> use<00:02:00.479> something<00:02:00.719> called<00:02:00.840> least 00:02:01.219 --> 00:02:01.229 align:start position:0% this we use something called least 00:02:01.229 --> 00:02:03.170 align:start position:0% this we use something called least Authority<00:02:01.409> permissioning<00:02:02.250> so<00:02:02.880> you<00:02:02.939> pass 00:02:03.170 --> 00:02:03.180 align:start position:0% Authority permissioning so you pass 00:02:03.180 --> 00:02:05.300 align:start position:0% Authority permissioning so you pass around<00:02:03.420> keys<00:02:03.930> from<00:02:04.350> one<00:02:04.530> module<00:02:04.920> to<00:02:04.950> the<00:02:05.159> other 00:02:05.300 --> 00:02:05.310 align:start position:0% around keys from one module to the other 00:02:05.310 --> 00:02:07.580 align:start position:0% around keys from one module to the other keys<00:02:06.000> the<00:02:06.210> control<00:02:06.630> which<00:02:06.930> stores<00:02:07.259> can<00:02:07.560> be 00:02:07.580 --> 00:02:07.590 align:start position:0% keys the control which stores can be 00:02:07.590 --> 00:02:10.190 align:start position:0% keys the control which stores can be read<00:02:07.860> or<00:02:08.069> written<00:02:08.099> to<00:02:08.369> unlike<00:02:09.270> for<00:02:09.660> example<00:02:10.080> a 00:02:10.190 --> 00:02:10.200 align:start position:0% read or written to unlike for example a 00:02:10.200 --> 00:02:12.619 align:start position:0% read or written to unlike for example a call<00:02:10.410> between<00:02:10.590> contracts<00:02:11.190> in<00:02:11.340> the<00:02:11.430> EVM<00:02:11.819> a<00:02:12.120> call 00:02:12.619 --> 00:02:12.629 align:start position:0% call between contracts in the EVM a call 00:02:12.629 --> 00:02:13.820 align:start position:0% call between contracts in the EVM a call between<00:02:12.810> modules<00:02:13.319> and<00:02:13.500> the<00:02:13.560> cost 00:02:13.820 --> 00:02:13.830 align:start position:0% between modules and the cost 00:02:13.830 --> 00:02:16.460 align:start position:0% between modules and the cost that's<00:02:14.070> decay<00:02:14.340> can<00:02:14.610> only<00:02:14.870> execute<00:02:15.870> reads<00:02:16.290> or 00:02:16.460 --> 00:02:16.470 align:start position:0% that's decay can only execute reads or 00:02:16.470 --> 00:02:18.020 align:start position:0% that's decay can only execute reads or writes<00:02:16.500> to<00:02:16.920> the<00:02:17.010> stores<00:02:17.310> for<00:02:17.610> which<00:02:17.760> you<00:02:17.880> give 00:02:18.020 --> 00:02:18.030 align:start position:0% writes to the stores for which you give 00:02:18.030 --> 00:02:20.660 align:start position:0% writes to the stores for which you give it<00:02:18.150> permission<00:02:18.300> to<00:02:18.630> do<00:02:19.220> we're<00:02:20.220> trying<00:02:20.520> to 00:02:20.660 --> 00:02:20.670 align:start position:0% it permission to do we're trying to 00:02:20.670 --> 00:02:22.880 align:start position:0% it permission to do we're trying to model<00:02:20.820> the<00:02:21.120> SDK<00:02:21.600> as<00:02:21.810> a<00:02:21.840> sort<00:02:22.170> of<00:02:22.230> Ruby<00:02:22.680> on<00:02:22.860> Rails 00:02:22.880 --> 00:02:22.890 align:start position:0% model the SDK as a sort of Ruby on Rails 00:02:22.890 --> 00:02:25.880 align:start position:0% model the SDK as a sort of Ruby on Rails for<00:02:23.490> blockchains<00:02:24.030> a<00:02:24.330> way<00:02:24.750> to<00:02:24.810> take<00:02:25.170> existing 00:02:25.880 --> 00:02:25.890 align:start position:0% for blockchains a way to take existing 00:02:25.890 --> 00:02:28.700 align:start position:0% for blockchains a way to take existing modules<00:02:26.310> add<00:02:26.760> your<00:02:27.420> own<00:02:27.450> custom<00:02:27.930> flavor<00:02:28.410> for 00:02:28.700 --> 00:02:28.710 align:start position:0% modules add your own custom flavor for 00:02:28.710 --> 00:02:30.680 align:start position:0% modules add your own custom flavor for your<00:02:28.830> particular<00:02:29.100> application<00:02:29.400> and<00:02:30.090> end<00:02:30.540> up 00:02:30.680 --> 00:02:30.690 align:start position:0% your particular application and end up 00:02:30.690 --> 00:02:32.060 align:start position:0% your particular application and end up really<00:02:31.020> fast<00:02:31.290> for<00:02:31.620> something<00:02:31.830> that's 00:02:32.060 --> 00:02:32.070 align:start position:0% really fast for something that's 00:02:32.070 --> 00:02:36.680 align:start position:0% really fast for something that's production-ready<00:02:34.820> in<00:02:35.820> order<00:02:36.060> to<00:02:36.180> do<00:02:36.330> this<00:02:36.480> the 00:02:36.680 --> 00:02:36.690 align:start position:0% production-ready in order to do this the 00:02:36.690 --> 00:02:39.410 align:start position:0% production-ready in order to do this the SDK<00:02:37.140> needs<00:02:37.350> to<00:02:37.470> be<00:02:37.560> modular<00:02:38.100> we've<00:02:38.850> built<00:02:39.240> a 00:02:39.410 --> 00:02:39.420 align:start position:0% SDK needs to be modular we've built a 00:02:39.420 --> 00:02:41.420 align:start position:0% SDK needs to be modular we've built a system<00:02:39.600> by<00:02:39.960> which<00:02:40.020> we<00:02:40.470> can<00:02:40.680> build<00:02:40.890> particular 00:02:41.420 --> 00:02:41.430 align:start position:0% system by which we can build particular 00:02:41.430 --> 00:02:43.190 align:start position:0% system by which we can build particular components<00:02:42.300> that<00:02:42.420> you<00:02:42.510> might<00:02:42.690> want<00:02:42.900> in<00:02:43.050> your 00:02:43.190 --> 00:02:43.200 align:start position:0% components that you might want in your 00:02:43.200 --> 00:02:45.470 align:start position:0% components that you might want in your state<00:02:43.410> machine<00:02:43.740> as<00:02:43.950> modules<00:02:44.460> now<00:02:45.270> and 00:02:45.470 --> 00:02:45.480 align:start position:0% state machine as modules now and 00:02:45.480 --> 00:02:48.080 align:start position:0% state machine as modules now and eventually<00:02:45.720> not<00:02:46.260> only<00:02:46.320> us<00:02:46.890> we<00:02:47.250> hope<00:02:47.460> but<00:02:47.910> many 00:02:48.080 --> 00:02:48.090 align:start position:0% eventually not only us we hope but many 00:02:48.090 --> 00:02:49.370 align:start position:0% eventually not only us we hope but many other<00:02:48.330> people<00:02:48.690> who<00:02:48.840> are<00:02:48.930> building<00:02:49.290> these 00:02:49.370 --> 00:02:49.380 align:start position:0% other people who are building these 00:02:49.380 --> 00:02:51.530 align:start position:0% other people who are building these application<00:02:49.980> specific<00:02:50.400> block<00:02:50.610> chains<00:02:50.850> they 00:02:51.530 --> 00:02:51.540 align:start position:0% application specific block chains they 00:02:51.540 --> 00:02:53.480 align:start position:0% application specific block chains they can<00:02:51.780> build<00:02:52.050> modules<00:02:52.680> as<00:02:52.950> we've<00:02:53.130> built<00:02:53.400> for 00:02:53.480 --> 00:02:53.490 align:start position:0% can build modules as we've built for 00:02:53.490 --> 00:02:55.670 align:start position:0% can build modules as we've built for governance<00:02:53.970> staking<00:02:54.480> fee<00:02:54.959> distribution<00:02:55.530> and 00:02:55.670 --> 00:02:55.680 align:start position:0% governance staking fee distribution and 00:02:55.680 --> 00:02:57.410 align:start position:0% governance staking fee distribution and inter<00:02:55.890> blockchain<00:02:56.250> communication<00:02:56.910> they 00:02:57.410 --> 00:02:57.420 align:start position:0% inter blockchain communication they 00:02:57.420 --> 00:02:59.570 align:start position:0% inter blockchain communication they could<00:02:57.600> build<00:02:57.690> a<00:02:57.870> different<00:02:58.200> module<00:02:58.350> for<00:02:58.860> add<00:02:59.310> X 00:02:59.570 --> 00:02:59.580 align:start position:0% could build a different module for add X 00:02:59.580 --> 00:03:01.460 align:start position:0% could build a different module for add X or<00:02:59.910> a<00:02:59.940> different<00:03:00.390> module<00:03:00.510> for<00:03:00.990> a<00:03:01.020> different 00:03:01.460 --> 00:03:01.470 align:start position:0% or a different module for a different 00:03:01.470 --> 00:03:04.100 align:start position:0% or a different module for a different kind<00:03:01.560> of<00:03:01.709> proof<00:03:01.980> of<00:03:02.070> stake<00:03:02.310> algorithm<00:03:03.110> then 00:03:04.100 --> 00:03:04.110 align:start position:0% kind of proof of stake algorithm then 00:03:04.110 --> 00:03:06.920 align:start position:0% kind of proof of stake algorithm then you<00:03:04.620> can<00:03:04.830> using<00:03:05.280> the<00:03:05.370> cosmos<00:03:05.730> SDK<00:03:06.209> pick<00:03:06.690> and 00:03:06.920 --> 00:03:06.930 align:start position:0% you can using the cosmos SDK pick and 00:03:06.930 --> 00:03:08.690 align:start position:0% you can using the cosmos SDK pick and choose<00:03:07.140> which<00:03:07.500> modules<00:03:07.950> you<00:03:08.070> want<00:03:08.280> to<00:03:08.400> use<00:03:08.550> in 00:03:08.690 --> 00:03:08.700 align:start position:0% choose which modules you want to use in 00:03:08.700 --> 00:03:11.930 align:start position:0% choose which modules you want to use in your<00:03:08.820> blockchain<00:03:09.360> glue<00:03:10.050> them<00:03:10.260> together<00:03:10.940> and 00:03:11.930 --> 00:03:11.940 align:start position:0% your blockchain glue them together and 00:03:11.940 --> 00:03:13.670 align:start position:0% your blockchain glue them together and connect<00:03:12.360> them<00:03:12.540> using<00:03:13.020> the<00:03:13.080> least<00:03:13.230> authority 00:03:13.670 --> 00:03:13.680 align:start position:0% connect them using the least authority 00:03:13.680 --> 00:03:15.500 align:start position:0% connect them using the least authority permissioning<00:03:14.130> system<00:03:14.550> to<00:03:15.000> run<00:03:15.150> your<00:03:15.300> state 00:03:15.500 --> 00:03:15.510 align:start position:0% permissioning system to run your state 00:03:15.510 --> 00:03:17.690 align:start position:0% permissioning system to run your state machine<00:03:15.780> we<00:03:16.680> hope<00:03:16.920> then<00:03:17.250> when<00:03:17.430> you've<00:03:17.550> done 00:03:17.690 --> 00:03:17.700 align:start position:0% machine we hope then when you've done 00:03:17.700 --> 00:03:19.100 align:start position:0% machine we hope then when you've done this<00:03:17.910> and<00:03:18.180> when<00:03:18.570> you've<00:03:18.690> added<00:03:18.900> your 00:03:19.100 --> 00:03:19.110 align:start position:0% this and when you've added your 00:03:19.110 --> 00:03:21.500 align:start position:0% this and when you've added your application<00:03:19.800> specific<00:03:20.250> flavor<00:03:20.519> the<00:03:21.090> custom 00:03:21.500 --> 00:03:21.510 align:start position:0% application specific flavor the custom 00:03:21.510 --> 00:03:23.000 align:start position:0% application specific flavor the custom module<00:03:21.840> for<00:03:22.050> whatever<00:03:22.200> your<00:03:22.560> blockchain<00:03:22.980> is 00:03:23.000 --> 00:03:23.010 align:start position:0% module for whatever your blockchain is 00:03:23.010 --> 00:03:24.740 align:start position:0% module for whatever your blockchain is going<00:03:23.280> to<00:03:23.400> do<00:03:23.489> better<00:03:23.760> than<00:03:23.940> anyone<00:03:24.269> else<00:03:24.450> you 00:03:24.740 --> 00:03:24.750 align:start position:0% going to do better than anyone else you 00:03:24.750 --> 00:03:26.990 align:start position:0% going to do better than anyone else you will<00:03:25.350> share<00:03:25.590> that<00:03:25.739> or<00:03:26.220> share<00:03:26.459> parts<00:03:26.730> of<00:03:26.880> it 00:03:26.990 --> 00:03:27.000 align:start position:0% will share that or share parts of it 00:03:27.000 --> 00:03:29.150 align:start position:0% will share that or share parts of it upstream<00:03:27.780> so<00:03:28.170> that<00:03:28.290> people<00:03:28.620> upstream<00:03:29.010> and 00:03:29.150 --> 00:03:29.160 align:start position:0% upstream so that people upstream and 00:03:29.160 --> 00:03:31.310 align:start position:0% upstream so that people upstream and downstream<00:03:29.280> so<00:03:29.790> that<00:03:29.940> people<00:03:30.239> can<00:03:30.480> build<00:03:30.989> upon 00:03:31.310 --> 00:03:31.320 align:start position:0% downstream so that people can build upon 00:03:31.320 --> 00:03:33.290 align:start position:0% downstream so that people can build upon what<00:03:31.500> you've<00:03:31.650> done<00:03:31.860> improve<00:03:32.280> it<00:03:32.459> and<00:03:32.700> send<00:03:33.209> it 00:03:33.290 --> 00:03:33.300 align:start position:0% what you've done improve it and send it 00:03:33.300 --> 00:03:37.370 align:start position:0% what you've done improve it and send it back<00:03:34.730> in<00:03:35.730> order<00:03:35.970> to<00:03:36.090> facilitate<00:03:36.360> this<00:03:37.019> network 00:03:37.370 --> 00:03:37.380 align:start position:0% back in order to facilitate this network 00:03:37.380 --> 00:03:39.680 align:start position:0% back in order to facilitate this network of<00:03:37.530> interconnected<00:03:37.769> block<00:03:38.400> chains<00:03:38.700> we<00:03:39.300> need<00:03:39.510> a 00:03:39.680 --> 00:03:39.690 align:start position:0% of interconnected block chains we need a 00:03:39.690 --> 00:03:41.150 align:start position:0% of interconnected block chains we need a consensus<00:03:40.200> algorithm<00:03:40.500> with<00:03:40.830> particular 00:03:41.150 --> 00:03:41.160 align:start position:0% consensus algorithm with particular 00:03:41.160 --> 00:03:43.880 align:start position:0% consensus algorithm with particular properties<00:03:41.690> so<00:03:42.690> we've<00:03:43.110> built<00:03:43.260> tenement 00:03:43.880 --> 00:03:43.890 align:start position:0% properties so we've built tenement 00:03:43.890 --> 00:03:45.940 align:start position:0% properties so we've built tenement tender<00:03:44.640> mint<00:03:44.820> is<00:03:44.910> the<00:03:44.940> state<00:03:45.239> of<00:03:45.269> the<00:03:45.510> art 00:03:45.940 --> 00:03:45.950 align:start position:0% tender mint is the state of the art 00:03:45.950 --> 00:03:48.259 align:start position:0% tender mint is the state of the art generic<00:03:46.950> Byzantine<00:03:47.610> fault<00:03:47.850> tolerant 00:03:48.259 --> 00:03:48.269 align:start position:0% generic Byzantine fault tolerant 00:03:48.269 --> 00:03:50.479 align:start position:0% generic Byzantine fault tolerant blockchain<00:03:48.720> engine<00:03:49.140> it<00:03:49.620> encapsulates<00:03:49.950> the 00:03:50.479 --> 00:03:50.489 align:start position:0% blockchain engine it encapsulates the 00:03:50.489 --> 00:03:52.729 align:start position:0% blockchain engine it encapsulates the consensus<00:03:51.060> in<00:03:51.330> peer-to-peer<00:03:51.600> layer<00:03:52.050> coming 00:03:52.729 --> 00:03:52.739 align:start position:0% consensus in peer-to-peer layer coming 00:03:52.739 --> 00:03:54.890 align:start position:0% consensus in peer-to-peer layer coming to<00:03:52.920> consensus<00:03:53.459> on<00:03:53.640> which<00:03:54.060> transactions<00:03:54.720> ought 00:03:54.890 --> 00:03:54.900 align:start position:0% to consensus on which transactions ought 00:03:54.900 --> 00:03:56.870 align:start position:0% to consensus on which transactions ought to<00:03:55.050> be<00:03:55.170> applied<00:03:55.440> in<00:03:55.680> which<00:03:55.830> block<00:03:56.130> and<00:03:56.430> when<00:03:56.850> a 00:03:56.870 --> 00:03:56.880 align:start position:0% to be applied in which block and when a 00:03:56.880 --> 00:03:58.490 align:start position:0% to be applied in which block and when a block<00:03:57.150> needs<00:03:57.450> to<00:03:57.540> be<00:03:57.630> appended<00:03:58.080> to<00:03:58.110> the<00:03:58.290> chain 00:03:58.490 --> 00:03:58.500 align:start position:0% block needs to be appended to the chain 00:03:58.500 --> 00:04:01.370 align:start position:0% block needs to be appended to the chain and<00:03:58.769> it<00:03:59.519> provides<00:03:59.970> vertical<00:04:00.810> layer<00:04:01.110> one 00:04:01.370 --> 00:04:01.380 align:start position:0% and it provides vertical layer one 00:04:01.380 --> 00:04:03.500 align:start position:0% and it provides vertical layer one scaling<00:04:01.890> for<00:04:02.070> your<00:04:02.190> state<00:04:02.400> machine<00:04:02.700> superfast 00:04:03.500 --> 00:04:03.510 align:start position:0% scaling for your state machine superfast 00:04:03.510 --> 00:04:05.660 align:start position:0% scaling for your state machine superfast two-and-a-half<00:04:03.750> second<00:04:04.230> block<00:04:04.380> times<00:04:04.670> ten 00:04:05.660 --> 00:04:05.670 align:start position:0% two-and-a-half second block times ten 00:04:05.670 --> 00:04:07.250 align:start position:0% two-and-a-half second block times ten Dermot<00:04:05.910> is<00:04:06.030> fully<00:04:06.269> peer<00:04:06.570> reviewed<00:04:06.930> and<00:04:07.140> it 00:04:07.250 --> 00:04:07.260 align:start position:0% Dermot is fully peer reviewed and it 00:04:07.260 --> 00:04:09.590 align:start position:0% Dermot is fully peer reviewed and it offers<00:04:07.590> one<00:04:07.980> block<00:04:08.550> finality<00:04:09.150> as<00:04:09.269> soon<00:04:09.420> as<00:04:09.510> the 00:04:09.590 --> 00:04:09.600 align:start position:0% offers one block finality as soon as the 00:04:09.600 --> 00:04:10.910 align:start position:0% offers one block finality as soon as the block<00:04:09.750> is<00:04:09.930> confirmed<00:04:10.320> it<00:04:10.470> will<00:04:10.560> never<00:04:10.709> be 00:04:10.910 --> 00:04:10.920 align:start position:0% block is confirmed it will never be 00:04:10.920 --> 00:04:14.930 align:start position:0% block is confirmed it will never be reverted<00:04:12.110> most<00:04:13.110> importantly<00:04:13.680> for<00:04:14.310> this<00:04:14.459> model 00:04:14.930 --> 00:04:14.940 align:start position:0% reverted most importantly for this model 00:04:14.940 --> 00:04:16.550 align:start position:0% reverted most importantly for this model of<00:04:15.090> application<00:04:15.660> specific<00:04:16.109> block<00:04:16.290> chains 00:04:16.550 --> 00:04:16.560 align:start position:0% of application specific block chains 00:04:16.560 --> 00:04:18.740 align:start position:0% of application specific block chains tender<00:04:17.010> mint<00:04:17.160> is<00:04:17.280> generic<00:04:17.760> it<00:04:18.030> can<00:04:18.390> connect<00:04:18.690> to 00:04:18.740 --> 00:04:18.750 align:start position:0% tender mint is generic it can connect to 00:04:18.750 --> 00:04:21.170 align:start position:0% tender mint is generic it can connect to any<00:04:18.810> state<00:04:19.260> machine<00:04:19.560> you<00:04:19.769> could<00:04:20.250> write<00:04:20.459> using 00:04:21.170 --> 00:04:21.180 align:start position:0% any state machine you could write using 00:04:21.180 --> 00:04:23.659 align:start position:0% any state machine you could write using the<00:04:21.390> cosmos<00:04:21.720> SDK<00:04:22.169> or<00:04:22.440> using<00:04:22.830> a<00:04:22.919> different<00:04:23.250> SDK 00:04:23.659 --> 00:04:23.669 align:start position:0% the cosmos SDK or using a different SDK 00:04:23.669 --> 00:04:26.120 align:start position:0% the cosmos SDK or using a different SDK any<00:04:23.940> kind<00:04:24.630> of<00:04:24.780> state<00:04:25.410> machine<00:04:25.770> you<00:04:25.800> like 00:04:26.120 --> 00:04:26.130 align:start position:0% any kind of state machine you like 00:04:26.130 --> 00:04:27.080 align:start position:0% any kind of state machine you like operating<00:04:26.640> whatever 00:04:27.080 --> 00:04:27.090 align:start position:0% operating whatever 00:04:27.090 --> 00:04:28.610 align:start position:0% operating whatever sort<00:04:27.270> of<00:04:27.330> application<00:04:27.960> you<00:04:28.139> want<00:04:28.290> to<00:04:28.380> operate 00:04:28.610 --> 00:04:28.620 align:start position:0% sort of application you want to operate 00:04:28.620 --> 00:04:33.020 align:start position:0% sort of application you want to operate and<00:04:28.980> run<00:04:29.490> it<00:04:29.639> with<00:04:29.790> ten<00:04:30.030> durmand<00:04:31.639> so<00:04:32.639> here's<00:04:32.970> a 00:04:33.020 --> 00:04:33.030 align:start position:0% and run it with ten durmand so here's a 00:04:33.030 --> 00:04:34.730 align:start position:0% and run it with ten durmand so here's a picture<00:04:33.210> of<00:04:33.389> what<00:04:33.630> the<00:04:33.750> tenement<00:04:34.139> stack<00:04:34.380> looks 00:04:34.730 --> 00:04:34.740 align:start position:0% picture of what the tenement stack looks 00:04:34.740 --> 00:04:36.730 align:start position:0% picture of what the tenement stack looks like<00:04:34.949> so<00:04:35.460> you<00:04:35.550> can<00:04:35.610> see<00:04:35.880> this<00:04:36.030> in<00:04:36.210> visual<00:04:36.570> form 00:04:36.730 --> 00:04:36.740 align:start position:0% like so you can see this in visual form 00:04:36.740 --> 00:04:39.590 align:start position:0% like so you can see this in visual form the<00:04:37.740> large<00:04:38.130> green<00:04:38.400> rectangle<00:04:39.030> is<00:04:39.180> tournament 00:04:39.590 --> 00:04:39.600 align:start position:0% the large green rectangle is tournament 00:04:39.600 --> 00:04:42.320 align:start position:0% the large green rectangle is tournament consensus<00:04:40.169> and<00:04:40.440> each<00:04:40.710> of<00:04:40.949> the<00:04:41.160> circular<00:04:41.910> disks 00:04:42.320 --> 00:04:42.330 align:start position:0% consensus and each of the circular disks 00:04:42.330 --> 00:04:43.879 align:start position:0% consensus and each of the circular disks is<00:04:42.510> a<00:04:42.540> validator<00:04:43.050> participating<00:04:43.710> in<00:04:43.800> the 00:04:43.879 --> 00:04:43.889 align:start position:0% is a validator participating in the 00:04:43.889 --> 00:04:46.129 align:start position:0% is a validator participating in the consensus<00:04:44.370> algorithm<00:04:44.639> sending<00:04:45.570> messages<00:04:46.080> to 00:04:46.129 --> 00:04:46.139 align:start position:0% consensus algorithm sending messages to 00:04:46.139 --> 00:04:49.670 align:start position:0% consensus algorithm sending messages to each<00:04:46.320> other<00:04:46.620> to<00:04:46.860> vote<00:04:47.070> in<00:04:47.370> BFT<00:04:47.850> rounds<00:04:48.240> then<00:04:49.110> in 00:04:49.670 --> 00:04:49.680 align:start position:0% each other to vote in BFT rounds then in 00:04:49.680 --> 00:04:52.400 align:start position:0% each other to vote in BFT rounds then in smaller<00:04:50.610> blue<00:04:50.910> rectangle<00:04:51.540> we<00:04:51.690> have<00:04:51.870> the<00:04:51.990> ABC 00:04:52.400 --> 00:04:52.410 align:start position:0% smaller blue rectangle we have the ABC 00:04:52.410 --> 00:04:54.050 align:start position:0% smaller blue rectangle we have the ABC i--<00:04:52.440> allocation<00:04:53.160> that's<00:04:53.370> your<00:04:53.550> state<00:04:53.760> machine 00:04:54.050 --> 00:04:54.060 align:start position:0% i-- allocation that's your state machine 00:04:54.060 --> 00:04:56.420 align:start position:0% i-- allocation that's your state machine written<00:04:54.810> using<00:04:55.020> the<00:04:55.229> cosmos<00:04:55.560> SDK<00:04:56.010> and<00:04:56.190> perhaps 00:04:56.420 --> 00:04:56.430 align:start position:0% written using the cosmos SDK and perhaps 00:04:56.430 --> 00:04:59.090 align:start position:0% written using the cosmos SDK and perhaps featuring<00:04:57.180> the<00:04:57.300> EVM<00:04:57.660> which<00:04:58.350> is<00:04:58.500> talking<00:04:58.889> to 00:04:59.090 --> 00:04:59.100 align:start position:0% featuring the EVM which is talking to 00:04:59.100 --> 00:05:00.650 align:start position:0% featuring the EVM which is talking to and<00:04:59.250> from<00:04:59.400> ten<00:04:59.669> Derman<00:04:59.910> telling<00:05:00.270> ten<00:05:00.450> Dermot 00:05:00.650 --> 00:05:00.660 align:start position:0% and from ten Derman telling ten Dermot 00:05:00.660 --> 00:05:02.090 align:start position:0% and from ten Derman telling ten Dermot which<00:05:00.810> transactions<00:05:01.440> are<00:05:01.560> valid<00:05:01.889> and 00:05:02.090 --> 00:05:02.100 align:start position:0% which transactions are valid and 00:05:02.100 --> 00:05:04.070 align:start position:0% which transactions are valid and executing<00:05:03.000> the<00:05:03.090> transactions<00:05:03.660> once<00:05:03.900> they've 00:05:04.070 --> 00:05:04.080 align:start position:0% executing the transactions once they've 00:05:04.080 --> 00:05:08.990 align:start position:0% executing the transactions once they've been<00:05:04.169> confirmed<00:05:04.560> in<00:05:04.740> a<00:05:04.860> block<00:05:06.919> so<00:05:07.919> in<00:05:08.580> order<00:05:08.790> to 00:05:08.990 --> 00:05:09.000 align:start position:0% been confirmed in a block so in order to 00:05:09.000 --> 00:05:10.580 align:start position:0% been confirmed in a block so in order to make<00:05:09.150> it<00:05:09.270> as<00:05:09.419> easy<00:05:09.570> as<00:05:09.690> possible<00:05:09.780> for 00:05:10.580 --> 00:05:10.590 align:start position:0% make it as easy as possible for 00:05:10.590 --> 00:05:12.830 align:start position:0% make it as easy as possible for developers<00:05:10.650> to<00:05:11.220> start<00:05:11.280> working<00:05:11.850> on<00:05:12.060> full 00:05:12.830 --> 00:05:12.840 align:start position:0% developers to start working on full 00:05:12.840 --> 00:05:14.330 align:start position:0% developers to start working on full function<00:05:13.260> block<00:05:13.470> chains<00:05:13.740> using<00:05:14.040> the<00:05:14.220> SDK 00:05:14.330 --> 00:05:14.340 align:start position:0% function block chains using the SDK 00:05:14.340 --> 00:05:17.060 align:start position:0% function block chains using the SDK intendment<00:05:15.060> and<00:05:15.600> in<00:05:16.229> order<00:05:16.440> to<00:05:16.560> build<00:05:16.680> the 00:05:17.060 --> 00:05:17.070 align:start position:0% intendment and in order to build the 00:05:17.070 --> 00:05:18.529 align:start position:0% intendment and in order to build the particular<00:05:17.340> block<00:05:17.700> chain<00:05:17.910> we're<00:05:18.090> working<00:05:18.450> on 00:05:18.529 --> 00:05:18.539 align:start position:0% particular block chain we're working on 00:05:18.539 --> 00:05:20.570 align:start position:0% particular block chain we're working on the<00:05:18.750> cosmos<00:05:19.110> hub<00:05:19.320> we've<00:05:19.830> built<00:05:20.100> some<00:05:20.340> core 00:05:20.570 --> 00:05:20.580 align:start position:0% the cosmos hub we've built some core 00:05:20.580 --> 00:05:22.460 align:start position:0% the cosmos hub we've built some core modules<00:05:21.060> which<00:05:21.450> I'll<00:05:21.600> talk<00:05:21.720> about<00:05:22.020> now<00:05:22.200> the 00:05:22.460 --> 00:05:22.470 align:start position:0% modules which I'll talk about now the 00:05:22.470 --> 00:05:24.640 align:start position:0% modules which I'll talk about now the first<00:05:22.979> module<00:05:23.400> is<00:05:23.520> bonded<00:05:23.970> proof<00:05:24.180> of<00:05:24.360> stake 00:05:24.640 --> 00:05:24.650 align:start position:0% first module is bonded proof of stake 00:05:24.650 --> 00:05:27.500 align:start position:0% first module is bonded proof of stake bonded<00:05:25.650> proof<00:05:25.830> of<00:05:25.949> stake<00:05:26.220> is<00:05:26.580> the<00:05:26.610> proof<00:05:27.389> of 00:05:27.500 --> 00:05:27.510 align:start position:0% bonded proof of stake is the proof of 00:05:27.510 --> 00:05:29.000 align:start position:0% bonded proof of stake is the proof of stake<00:05:27.690> mechanism<00:05:28.289> which<00:05:28.470> will<00:05:28.620> be<00:05:28.710> used<00:05:28.919> by 00:05:29.000 --> 00:05:29.010 align:start position:0% stake mechanism which will be used by 00:05:29.010 --> 00:05:31.460 align:start position:0% stake mechanism which will be used by the<00:05:29.130> cosmos<00:05:29.550> hub<00:05:29.760> in<00:05:30.000> which<00:05:30.539> we<00:05:30.690> invite<00:05:31.080> any 00:05:31.460 --> 00:05:31.470 align:start position:0% the cosmos hub in which we invite any 00:05:31.470 --> 00:05:33.409 align:start position:0% the cosmos hub in which we invite any blockchains<00:05:32.039> in<00:05:32.220> the<00:05:32.310> cosmos<00:05:32.639> ecosystem<00:05:33.240> to 00:05:33.409 --> 00:05:33.419 align:start position:0% blockchains in the cosmos ecosystem to 00:05:33.419 --> 00:05:35.390 align:start position:0% blockchains in the cosmos ecosystem to use<00:05:33.570> themselves<00:05:34.110> with<00:05:34.590> their<00:05:34.889> own<00:05:34.919> staking 00:05:35.390 --> 00:05:35.400 align:start position:0% use themselves with their own staking 00:05:35.400 --> 00:05:37.490 align:start position:0% use themselves with their own staking token<00:05:35.700> if<00:05:35.820> they<00:05:35.940> like<00:05:36.120> bonded<00:05:36.930> proof<00:05:37.110> of<00:05:37.260> stake 00:05:37.490 --> 00:05:37.500 align:start position:0% token if they like bonded proof of stake 00:05:37.500 --> 00:05:39.980 align:start position:0% token if they like bonded proof of stake has<00:05:37.740> delegation<00:05:38.400> as<00:05:38.789> we<00:05:39.030> say<00:05:39.210> with<00:05:39.479> skin<00:05:39.870> in 00:05:39.980 --> 00:05:39.990 align:start position:0% has delegation as we say with skin in 00:05:39.990 --> 00:05:42.140 align:start position:0% has delegation as we say with skin in the<00:05:40.110> game<00:05:40.139> so<00:05:40.680> delegate<00:05:41.460> errs<00:05:41.580> are<00:05:41.729> liable 00:05:42.140 --> 00:05:42.150 align:start position:0% the game so delegate errs are liable 00:05:42.150 --> 00:05:43.370 align:start position:0% the game so delegate errs are liable have<00:05:42.360> their<00:05:42.510> valid<00:05:42.780> at<00:05:42.900> our<00:05:42.990> commits<00:05:43.289> a 00:05:43.370 --> 00:05:43.380 align:start position:0% have their valid at our commits a 00:05:43.380 --> 00:05:45.290 align:start position:0% have their valid at our commits a protocol<00:05:43.740> fault<00:05:44.039> they<00:05:44.580> validate<00:05:44.910> or<00:05:45.030> double 00:05:45.290 --> 00:05:45.300 align:start position:0% protocol fault they validate or double 00:05:45.300 --> 00:05:46.820 align:start position:0% protocol fault they validate or double signs<00:05:45.510> or<00:05:45.870> fails<00:05:46.110> to<00:05:46.289> participate<00:05:46.740> in 00:05:46.820 --> 00:05:46.830 align:start position:0% signs or fails to participate in 00:05:46.830 --> 00:05:49.010 align:start position:0% signs or fails to participate in consensus<00:05:47.340> for<00:05:47.550> too<00:05:47.669> long<00:05:47.849> the<00:05:48.539> delegate<00:05:48.900> errs 00:05:49.010 --> 00:05:49.020 align:start position:0% consensus for too long the delegate errs 00:05:49.020 --> 00:05:51.950 align:start position:0% consensus for too long the delegate errs too<00:05:49.260> can<00:05:49.620> be<00:05:49.740> slashed<00:05:50.419> bonded<00:05:51.419> proof<00:05:51.599> of<00:05:51.750> stake 00:05:51.950 --> 00:05:51.960 align:start position:0% too can be slashed bonded proof of stake 00:05:51.960 --> 00:05:53.659 align:start position:0% too can be slashed bonded proof of stake addresses<00:05:52.500> the<00:05:52.620> nothing<00:05:52.889> at<00:05:53.039> stake<00:05:53.070> problem 00:05:53.659 --> 00:05:53.669 align:start position:0% addresses the nothing at stake problem 00:05:53.669 --> 00:05:55.490 align:start position:0% addresses the nothing at stake problem with<00:05:53.849> a<00:05:53.880> nun<00:05:54.090> bonding<00:05:54.510> period<00:05:54.900> both 00:05:55.490 --> 00:05:55.500 align:start position:0% with a nun bonding period both 00:05:55.500 --> 00:05:57.260 align:start position:0% with a nun bonding period both validators<00:05:56.280> and<00:05:56.460> delegate<00:05:56.789> errs<00:05:56.910> when<00:05:57.180> they 00:05:57.260 --> 00:05:57.270 align:start position:0% validators and delegate errs when they 00:05:57.270 --> 00:05:59.240 align:start position:0% validators and delegate errs when they want<00:05:57.510> to<00:05:57.630> participate<00:05:57.900> to<00:05:58.380> vote<00:05:58.530> in<00:05:58.710> consensus 00:05:59.240 --> 00:05:59.250 align:start position:0% want to participate to vote in consensus 00:05:59.250 --> 00:06:01.850 align:start position:0% want to participate to vote in consensus have<00:05:59.520> to<00:05:59.639> lockup<00:06:00.030> tokens<00:06:00.510> for<00:06:01.320> it<00:06:01.650> will<00:06:01.740> be 00:06:01.850 --> 00:06:01.860 align:start position:0% have to lockup tokens for it will be 00:06:01.860 --> 00:06:04.010 align:start position:0% have to lockup tokens for it will be three<00:06:02.070> weeks<00:06:02.280> at<00:06:02.610> launch<00:06:02.880> for<00:06:03.180> the<00:06:03.240> cosmos<00:06:03.570> but 00:06:04.010 --> 00:06:04.020 align:start position:0% three weeks at launch for the cosmos but 00:06:04.020 --> 00:06:06.200 align:start position:0% three weeks at launch for the cosmos but for<00:06:04.229> a<00:06:04.260> configurable<00:06:04.680> amount<00:06:05.010> of<00:06:05.130> time<00:06:05.340> and<00:06:05.639> as 00:06:06.200 --> 00:06:06.210 align:start position:0% for a configurable amount of time and as 00:06:06.210 --> 00:06:07.879 align:start position:0% for a configurable amount of time and as long<00:06:06.360> as<00:06:06.389> those<00:06:06.630> tokens<00:06:06.840> are<00:06:07.110> locked<00:06:07.289> up<00:06:07.440> if<00:06:07.740> an 00:06:07.879 --> 00:06:07.889 align:start position:0% long as those tokens are locked up if an 00:06:07.889 --> 00:06:09.950 align:start position:0% long as those tokens are locked up if an infraction<00:06:08.190> is<00:06:08.550> discovered<00:06:09.060> they<00:06:09.660> can<00:06:09.810> be 00:06:09.950 --> 00:06:09.960 align:start position:0% infraction is discovered they can be 00:06:09.960 --> 00:06:12.980 align:start position:0% infraction is discovered they can be slashed<00:06:10.970> we've<00:06:11.970> tried<00:06:12.240> to<00:06:12.270> build<00:06:12.479> this<00:06:12.599> module 00:06:12.980 --> 00:06:12.990 align:start position:0% slashed we've tried to build this module 00:06:12.990 --> 00:06:15.409 align:start position:0% slashed we've tried to build this module module<00:06:13.470> to<00:06:13.860> be<00:06:14.010> batteries<00:06:14.639> included<00:06:15.150> but 00:06:15.409 --> 00:06:15.419 align:start position:0% module to be batteries included but 00:06:15.419 --> 00:06:18.170 align:start position:0% module to be batteries included but extensible<00:06:16.200> you<00:06:16.860> could<00:06:17.010> import<00:06:17.340> it<00:06:17.520> as<00:06:17.700> is<00:06:17.940> and 00:06:18.170 --> 00:06:18.180 align:start position:0% extensible you could import it as is and 00:06:18.180 --> 00:06:19.580 align:start position:0% extensible you could import it as is and have<00:06:18.330> a<00:06:18.360> fully<00:06:18.599> functional<00:06:19.110> proof<00:06:19.260> of<00:06:19.410> stake 00:06:19.580 --> 00:06:19.590 align:start position:0% have a fully functional proof of stake 00:06:19.590 --> 00:06:21.110 align:start position:0% have a fully functional proof of stake algorithm<00:06:20.160> for<00:06:20.370> whatever<00:06:20.610> state<00:06:20.849> machine 00:06:21.110 --> 00:06:21.120 align:start position:0% algorithm for whatever state machine 00:06:21.120 --> 00:06:23.510 align:start position:0% algorithm for whatever state machine you're<00:06:21.270> running<00:06:21.539> or<00:06:21.780> you<00:06:22.440> can<00:06:22.590> modify<00:06:22.860> it<00:06:23.010> you 00:06:23.510 --> 00:06:23.520 align:start position:0% you're running or you can modify it you 00:06:23.520 --> 00:06:25.339 align:start position:0% you're running or you can modify it you could<00:06:23.669> add<00:06:23.789> custom<00:06:24.270> slashing<00:06:24.720> conditions<00:06:25.139> for 00:06:25.339 --> 00:06:25.349 align:start position:0% could add custom slashing conditions for 00:06:25.349 --> 00:06:27.589 align:start position:0% could add custom slashing conditions for different<00:06:25.440> kinds<00:06:26.010> of<00:06:26.270> application<00:06:27.270> level 00:06:27.589 --> 00:06:27.599 align:start position:0% different kinds of application level 00:06:27.599 --> 00:06:30.110 align:start position:0% different kinds of application level guarantees<00:06:28.139> you<00:06:28.500> want<00:06:28.650> to<00:06:28.740> provide<00:06:29.010> or<00:06:29.370> you 00:06:30.110 --> 00:06:30.120 align:start position:0% guarantees you want to provide or you 00:06:30.120 --> 00:06:32.060 align:start position:0% guarantees you want to provide or you could<00:06:30.330> change<00:06:30.570> the<00:06:31.169> way<00:06:31.289> we've<00:06:31.470> parameterize 00:06:32.060 --> 00:06:32.070 align:start position:0% could change the way we've parameterize 00:06:32.070 --> 00:06:34.610 align:start position:0% could change the way we've parameterize our<00:06:32.520> slashing<00:06:33.030> and<00:06:33.150> staking<00:06:33.389> conditions<00:06:33.960> all 00:06:34.610 --> 00:06:34.620 align:start position:0% our slashing and staking conditions all 00:06:34.620 --> 00:06:36.500 align:start position:0% our slashing and staking conditions all total<00:06:35.010> object<00:06:35.280> of<00:06:35.400> delegation<00:06:36.000> or<00:06:36.180> punish 00:06:36.500 --> 00:06:36.510 align:start position:0% total object of delegation or punish 00:06:36.510 --> 00:06:38.029 align:start position:0% total object of delegation or punish people<00:06:36.659> differently<00:06:37.110> for<00:06:37.710> committing 00:06:38.029 --> 00:06:38.039 align:start position:0% people differently for committing 00:06:38.039 --> 00:06:39.850 align:start position:0% people differently for committing protocol<00:06:38.400> faults 00:06:39.850 --> 00:06:39.860 align:start position:0% protocol faults 00:06:39.860 --> 00:06:42.060 align:start position:0% protocol faults the<00:06:40.580> second<00:06:40.940> core<00:06:41.090> module<00:06:41.420> is<00:06:41.570> governance 00:06:42.060 --> 00:06:42.070 align:start position:0% the second core module is governance 00:06:42.070 --> 00:06:44.140 align:start position:0% the second core module is governance like<00:06:43.070> our<00:06:43.250> proof<00:06:43.460> of<00:06:43.580> stake<00:06:43.790> module 00:06:44.140 --> 00:06:44.150 align:start position:0% like our proof of stake module 00:06:44.150 --> 00:06:45.940 align:start position:0% like our proof of stake module government's<00:06:44.600> design<00:06:44.900> is<00:06:45.320> designed<00:06:45.710> to<00:06:45.860> be 00:06:45.940 --> 00:06:45.950 align:start position:0% government's design is designed to be 00:06:45.950 --> 00:06:47.890 align:start position:0% government's design is designed to be pretty<00:06:46.310> flexible<00:06:46.550> so<00:06:47.150> it<00:06:47.210> will<00:06:47.330> work<00:06:47.360> for<00:06:47.720> lots 00:06:47.890 --> 00:06:47.900 align:start position:0% pretty flexible so it will work for lots 00:06:47.900 --> 00:06:50.200 align:start position:0% pretty flexible so it will work for lots of<00:06:47.990> different<00:06:48.050> blockchains<00:06:48.800> our<00:06:49.760> governance 00:06:50.200 --> 00:06:50.210 align:start position:0% of different blockchains our governance 00:06:50.210 --> 00:06:51.850 align:start position:0% of different blockchains our governance module<00:06:50.570> has<00:06:50.720> different<00:06:51.080> kinds<00:06:51.320> of<00:06:51.440> what<00:06:51.770> we 00:06:51.850 --> 00:06:51.860 align:start position:0% module has different kinds of what we 00:06:51.860 --> 00:06:53.740 align:start position:0% module has different kinds of what we call<00:06:52.040> governance<00:06:52.460> proposals<00:06:53.060> proposals<00:06:53.600> to 00:06:53.740 --> 00:06:53.750 align:start position:0% call governance proposals proposals to 00:06:53.750 --> 00:06:56.380 align:start position:0% call governance proposals proposals to change<00:06:53.890> some<00:06:54.890> way<00:06:55.070> the<00:06:55.250> chain<00:06:55.460> works<00:06:55.760> the 00:06:56.380 --> 00:06:56.390 align:start position:0% change some way the chain works the 00:06:56.390 --> 00:06:58.660 align:start position:0% change some way the chain works the first<00:06:56.660> are<00:06:56.960> simply<00:06:57.320> text<00:06:57.590> proposals<00:06:58.100> they 00:06:58.660 --> 00:06:58.670 align:start position:0% first are simply text proposals they 00:06:58.670 --> 00:07:00.790 align:start position:0% first are simply text proposals they don't<00:06:58.910> do<00:06:59.240> anything<00:06:59.510> in<00:06:59.900> protocol<00:07:00.350> in<00:07:00.560> band 00:07:00.790 --> 00:07:00.800 align:start position:0% don't do anything in protocol in band 00:07:00.800 --> 00:07:02.920 align:start position:0% don't do anything in protocol in band but<00:07:01.310> rather<00:07:01.520> allow<00:07:01.850> for<00:07:02.270> the<00:07:02.330> network<00:07:02.600> to<00:07:02.780> come 00:07:02.920 --> 00:07:02.930 align:start position:0% but rather allow for the network to come 00:07:02.930 --> 00:07:05.620 align:start position:0% but rather allow for the network to come to<00:07:03.080> social<00:07:03.410> consensus<00:07:03.860> on<00:07:04.070> maybe<00:07:05.030> some<00:07:05.330> change 00:07:05.620 --> 00:07:05.630 align:start position:0% to social consensus on maybe some change 00:07:05.630 --> 00:07:07.600 align:start position:0% to social consensus on maybe some change to<00:07:05.840> make<00:07:05.990> in<00:07:06.170> a<00:07:06.260> future<00:07:06.560> software<00:07:06.920> upgrade<00:07:07.280> or 00:07:07.600 --> 00:07:07.610 align:start position:0% to make in a future software upgrade or 00:07:07.610 --> 00:07:10.030 align:start position:0% to make in a future software upgrade or on<00:07:08.240> some<00:07:08.720> way<00:07:08.930> in<00:07:09.200> which<00:07:09.230> we<00:07:09.500> want<00:07:09.680> to<00:07:09.740> change 00:07:10.030 --> 00:07:10.040 align:start position:0% on some way in which we want to change 00:07:10.040 --> 00:07:11.530 align:start position:0% on some way in which we want to change the<00:07:10.250> way<00:07:10.340> we're<00:07:10.520> operating<00:07:10.760> this<00:07:11.060> blockchain 00:07:11.530 --> 00:07:11.540 align:start position:0% the way we're operating this blockchain 00:07:11.540 --> 00:07:14.110 align:start position:0% the way we're operating this blockchain the<00:07:12.380> second<00:07:12.770> are<00:07:12.950> promising<00:07:13.520> parameter 00:07:14.110 --> 00:07:14.120 align:start position:0% the second are promising parameter 00:07:14.120 --> 00:07:16.780 align:start position:0% the second are promising parameter change<00:07:14.390> proposals<00:07:14.960> which<00:07:15.170> are<00:07:15.410> inbound<00:07:15.980> so<00:07:16.670> if 00:07:16.780 --> 00:07:16.790 align:start position:0% change proposals which are inbound so if 00:07:16.790 --> 00:07:18.460 align:start position:0% change proposals which are inbound so if a<00:07:16.880> parameter<00:07:17.300> change<00:07:17.570> proposal<00:07:18.110> is<00:07:18.230> passed 00:07:18.460 --> 00:07:18.470 align:start position:0% a parameter change proposal is passed 00:07:18.470 --> 00:07:21.040 align:start position:0% a parameter change proposal is passed that<00:07:19.100> might<00:07:19.340> change<00:07:19.640> the<00:07:20.240> amount<00:07:20.600> of<00:07:20.780> steak 00:07:21.040 --> 00:07:21.050 align:start position:0% that might change the amount of steak 00:07:21.050 --> 00:07:22.720 align:start position:0% that might change the amount of steak which<00:07:21.290> is<00:07:21.440> slashed<00:07:21.680> for<00:07:22.010> double<00:07:22.250> signing<00:07:22.580> or 00:07:22.720 --> 00:07:22.730 align:start position:0% which is slashed for double signing or 00:07:22.730 --> 00:07:24.790 align:start position:0% which is slashed for double signing or it<00:07:23.390> could<00:07:23.540> change<00:07:23.570> the<00:07:24.050> annual<00:07:24.530> network 00:07:24.790 --> 00:07:24.800 align:start position:0% it could change the annual network 00:07:24.800 --> 00:07:27.910 align:start position:0% it could change the annual network inflation<00:07:25.280> rate<00:07:25.780> third<00:07:26.780> and<00:07:27.110> finally<00:07:27.560> we<00:07:27.740> have 00:07:27.910 --> 00:07:27.920 align:start position:0% inflation rate third and finally we have 00:07:27.920 --> 00:07:29.710 align:start position:0% inflation rate third and finally we have software<00:07:28.370> upgrade<00:07:28.760> proposals<00:07:29.240> which 00:07:29.710 --> 00:07:29.720 align:start position:0% software upgrade proposals which 00:07:29.720 --> 00:07:31.750 align:start position:0% software upgrade proposals which actually<00:07:30.140> upgrade<00:07:30.620> the<00:07:30.950> state<00:07:31.160> machine<00:07:31.490> which 00:07:31.750 --> 00:07:31.760 align:start position:0% actually upgrade the state machine which 00:07:31.760 --> 00:07:33.760 align:start position:0% actually upgrade the state machine which is<00:07:31.850> the<00:07:31.970> chain<00:07:32.180> is<00:07:32.330> running<00:07:32.660> so<00:07:33.170> upgrade<00:07:33.590> in 00:07:33.760 --> 00:07:33.770 align:start position:0% is the chain is running so upgrade in 00:07:33.770 --> 00:07:35.170 align:start position:0% is the chain is running so upgrade in the<00:07:33.800> case<00:07:33.980> of<00:07:34.160> your<00:07:34.250> application<00:07:34.730> specific 00:07:35.170 --> 00:07:35.180 align:start position:0% the case of your application specific 00:07:35.180 --> 00:07:36.580 align:start position:0% the case of your application specific blockchain<00:07:35.600> may<00:07:35.780> be<00:07:35.900> the<00:07:36.020> logic<00:07:36.380> of<00:07:36.500> an 00:07:36.580 --> 00:07:36.590 align:start position:0% blockchain may be the logic of an 00:07:36.590 --> 00:07:40.540 align:start position:0% blockchain may be the logic of an exchange<00:07:38.170> once<00:07:39.220> everyone<00:07:40.220> has<00:07:40.250> come<00:07:40.460> to 00:07:40.540 --> 00:07:40.550 align:start position:0% exchange once everyone has come to 00:07:40.550 --> 00:07:41.740 align:start position:0% exchange once everyone has come to consensus<00:07:40.910> on<00:07:41.000> that<00:07:41.060> proposal<00:07:41.300> at<00:07:41.720> a 00:07:41.740 --> 00:07:41.750 align:start position:0% consensus on that proposal at a 00:07:41.750 --> 00:07:43.590 align:start position:0% consensus on that proposal at a particular<00:07:42.230> block<00:07:42.410> height<00:07:42.620> automatically 00:07:43.590 --> 00:07:43.600 align:start position:0% particular block height automatically 00:07:43.600 --> 00:07:45.850 align:start position:0% particular block height automatically for<00:07:44.600> governance<00:07:44.960> we've<00:07:45.200> elected<00:07:45.590> to<00:07:45.710> use 00:07:45.850 --> 00:07:45.860 align:start position:0% for governance we've elected to use 00:07:45.860 --> 00:07:48.760 align:start position:0% for governance we've elected to use liquid<00:07:46.130> democracy<00:07:46.540> so<00:07:47.540> in<00:07:47.930> tender<00:07:48.440> mint<00:07:48.620> block 00:07:48.760 --> 00:07:48.770 align:start position:0% liquid democracy so in tender mint block 00:07:48.770 --> 00:07:50.380 align:start position:0% liquid democracy so in tender mint block chains<00:07:49.070> there<00:07:49.310> will<00:07:49.400> be<00:07:49.430> a<00:07:49.520> few<00:07:49.790> hundred<00:07:50.150> or<00:07:50.270> so 00:07:50.380 --> 00:07:50.390 align:start position:0% chains there will be a few hundred or so 00:07:50.390 --> 00:07:52.510 align:start position:0% chains there will be a few hundred or so validators<00:07:51.080> those<00:07:51.620> validators<00:07:52.250> going<00:07:52.460> to 00:07:52.510 --> 00:07:52.520 align:start position:0% validators those validators going to 00:07:52.520 --> 00:07:54.580 align:start position:0% validators those validators going to vote<00:07:52.670> and<00:07:52.940> by<00:07:53.420> default<00:07:53.840> they<00:07:54.110> were<00:07:54.170> carry 00:07:54.580 --> 00:07:54.590 align:start position:0% vote and by default they were carry 00:07:54.590 --> 00:07:56.260 align:start position:0% vote and by default they were carry their<00:07:54.860> delegate<00:07:55.280> errs<00:07:55.370> vote<00:07:55.610> with<00:07:55.850> them<00:07:56.060> if 00:07:56.260 --> 00:07:56.270 align:start position:0% their delegate errs vote with them if 00:07:56.270 --> 00:07:58.690 align:start position:0% their delegate errs vote with them if your<00:07:56.780> validator<00:07:57.290> votes<00:07:57.530> for<00:07:57.830> in<00:07:58.220> favor<00:07:58.490> of<00:07:58.640> a 00:07:58.690 --> 00:07:58.700 align:start position:0% your validator votes for in favor of a 00:07:58.700 --> 00:08:00.940 align:start position:0% your validator votes for in favor of a proposal<00:07:59.000> and<00:07:59.360> you<00:07:59.510> as<00:07:59.660> a<00:07:59.690> delegator<00:08:00.140> elect<00:08:00.860> to 00:08:00.940 --> 00:08:00.950 align:start position:0% proposal and you as a delegator elect to 00:08:00.950 --> 00:08:02.800 align:start position:0% proposal and you as a delegator elect to do<00:08:01.040> nothing<00:08:01.400> your<00:08:01.850> vote<00:08:02.060> your<00:08:02.270> stake<00:08:02.570> will 00:08:02.800 --> 00:08:02.810 align:start position:0% do nothing your vote your stake will 00:08:02.810 --> 00:08:04.720 align:start position:0% do nothing your vote your stake will count<00:08:02.990> in<00:08:03.260> favor<00:08:03.470> of<00:08:03.620> the<00:08:03.710> proposal<00:08:04.220> but 00:08:04.720 --> 00:08:04.730 align:start position:0% count in favor of the proposal but 00:08:04.730 --> 00:08:07.030 align:start position:0% count in favor of the proposal but delegate<00:08:05.300> errs<00:08:05.390> can<00:08:05.600> also<00:08:05.780> elect<00:08:06.140> override<00:08:06.800> to 00:08:07.030 --> 00:08:07.040 align:start position:0% delegate errs can also elect override to 00:08:07.040 --> 00:08:08.760 align:start position:0% delegate errs can also elect override to vote<00:08:07.160> other<00:08:07.370> validators<00:08:07.850> if<00:08:08.060> they<00:08:08.270> disagree 00:08:08.760 --> 00:08:08.770 align:start position:0% vote other validators if they disagree 00:08:08.770 --> 00:08:12.250 align:start position:0% vote other validators if they disagree and<00:08:09.770> they<00:08:10.490> will<00:08:10.640> have<00:08:10.790> time<00:08:11.000> to<00:08:11.240> do<00:08:11.330> that<00:08:11.510> if 00:08:12.250 --> 00:08:12.260 align:start position:0% and they will have time to do that if 00:08:12.260 --> 00:08:13.900 align:start position:0% and they will have time to do that if they<00:08:12.410> see<00:08:12.470> what<00:08:12.980> the<00:08:13.070> reality<00:08:13.220> to<00:08:13.460> votes<00:08:13.670> for 00:08:13.900 --> 00:08:13.910 align:start position:0% they see what the reality to votes for 00:08:13.910 --> 00:08:16.720 align:start position:0% they see what the reality to votes for and<00:08:14.120> decide<00:08:14.510> they<00:08:14.630> don't<00:08:14.720> like<00:08:14.900> it<00:08:15.280> next<00:08:16.280> up<00:08:16.490> on 00:08:16.720 --> 00:08:16.730 align:start position:0% and decide they don't like it next up on 00:08:16.730 --> 00:08:18.220 align:start position:0% and decide they don't like it next up on the<00:08:16.820> list<00:08:16.940> of<00:08:17.090> core<00:08:17.270> modules<00:08:17.630> is<00:08:17.870> fee 00:08:18.220 --> 00:08:18.230 align:start position:0% the list of core modules is fee 00:08:18.230 --> 00:08:20.830 align:start position:0% the list of core modules is fee distribution<00:08:18.770> rewards<00:08:19.160> and<00:08:19.310> fees<00:08:19.490> we<00:08:20.480> have 00:08:20.830 --> 00:08:20.840 align:start position:0% distribution rewards and fees we have 00:08:20.840 --> 00:08:22.660 align:start position:0% distribution rewards and fees we have decided<00:08:21.110> that<00:08:21.290> we<00:08:21.470> need<00:08:21.680> to<00:08:21.830> use<00:08:22.040> a<00:08:22.310> pretty 00:08:22.660 --> 00:08:22.670 align:start position:0% decided that we need to use a pretty 00:08:22.670 --> 00:08:24.340 align:start position:0% decided that we need to use a pretty different<00:08:23.000> system<00:08:23.540> for<00:08:23.690> fee<00:08:23.810> distribution 00:08:24.340 --> 00:08:24.350 align:start position:0% different system for fee distribution 00:08:24.350 --> 00:08:26.740 align:start position:0% different system for fee distribution for<00:08:24.530> tender<00:08:24.800> mint<00:08:24.980> than<00:08:25.310> for<00:08:25.790> most<00:08:26.390> existing 00:08:26.740 --> 00:08:26.750 align:start position:0% for tender mint than for most existing 00:08:26.750 --> 00:08:29.020 align:start position:0% for tender mint than for most existing block<00:08:27.140> chains<00:08:27.410> we<00:08:27.920> can't<00:08:28.220> just<00:08:28.610> give<00:08:28.790> all<00:08:28.910> the 00:08:29.020 --> 00:08:29.030 align:start position:0% block chains we can't just give all the 00:08:29.030 --> 00:08:31.120 align:start position:0% block chains we can't just give all the fees<00:08:29.180> to<00:08:29.450> the<00:08:29.540> proposer<00:08:29.870> because<00:08:30.740> it<00:08:31.010> would 00:08:31.120 --> 00:08:31.130 align:start position:0% fees to the proposer because it would 00:08:31.130 --> 00:08:33.760 align:start position:0% fees to the proposer because it would make<00:08:31.280> it<00:08:31.460> too<00:08:31.700> much<00:08:31.880> of<00:08:32.090> a<00:08:32.380> incentive<00:08:33.380> to<00:08:33.560> bias 00:08:33.760 --> 00:08:33.770 align:start position:0% make it too much of a incentive to bias 00:08:33.770 --> 00:08:36.280 align:start position:0% make it too much of a incentive to bias proposer<00:08:34.280> election<00:08:34.850> or<00:08:35.150> das<00:08:35.660> the<00:08:35.990> current 00:08:36.280 --> 00:08:36.290 align:start position:0% proposer election or das the current 00:08:36.290 --> 00:08:39.370 align:start position:0% proposer election or das the current elected<00:08:36.650> proposer<00:08:37.010> so<00:08:37.790> we<00:08:38.210> just<00:08:38.450> distribute 00:08:39.370 --> 00:08:39.380 align:start position:0% elected proposer so we just distribute 00:08:39.380 --> 00:08:41.260 align:start position:0% elected proposer so we just distribute most<00:08:39.590> rewards<00:08:39.979> for<00:08:40.130> posting<00:08:40.520> proportionally 00:08:41.260 --> 00:08:41.270 align:start position:0% most rewards for posting proportionally 00:08:41.270 --> 00:08:43.420 align:start position:0% most rewards for posting proportionally to<00:08:41.300> stake<00:08:41.690> held<00:08:41.930> by<00:08:42.650> all<00:08:42.830> the<00:08:42.950> delegate<00:08:43.340> errs 00:08:43.420 --> 00:08:43.430 align:start position:0% to stake held by all the delegate errs 00:08:43.430 --> 00:08:46.600 align:start position:0% to stake held by all the delegate errs and<00:08:43.640> Vala<00:08:43.790> leaders<00:08:44.150> on<00:08:44.900> the<00:08:45.080> blockchain<00:08:45.610> like 00:08:46.600 --> 00:08:46.610 align:start position:0% and Vala leaders on the blockchain like 00:08:46.610 --> 00:08:48.040 align:start position:0% and Vala leaders on the blockchain like the<00:08:46.850> staking<00:08:47.180> module<00:08:47.480> and<00:08:47.660> the<00:08:47.720> governance 00:08:48.040 --> 00:08:48.050 align:start position:0% the staking module and the governance 00:08:48.050 --> 00:08:49.690 align:start position:0% the staking module and the governance module<00:08:48.440> our<00:08:48.650> fee<00:08:48.830> distribution<00:08:49.370> module 00:08:49.690 --> 00:08:49.700 align:start position:0% module our fee distribution module 00:08:49.700 --> 00:08:51.460 align:start position:0% module our fee distribution module supports<00:08:50.120> any<00:08:50.330> token<00:08:50.750> so<00:08:51.230> you<00:08:51.290> could 00:08:51.460 --> 00:08:51.470 align:start position:0% supports any token so you could 00:08:51.470 --> 00:08:52.450 align:start position:0% supports any token so you could integrate<00:08:51.860> it<00:08:51.980> into<00:08:52.130> your<00:08:52.220> application 00:08:52.450 --> 00:08:52.460 align:start position:0% integrate it into your application 00:08:52.460 --> 00:08:53.620 align:start position:0% integrate it into your application specific<00:08:53.270> block 00:08:53.620 --> 00:08:53.630 align:start position:0% specific block 00:08:53.630 --> 00:08:56.439 align:start position:0% specific block with<00:08:53.899> your<00:08:54.050> own<00:08:54.139> token<00:08:54.759> easy<00:08:55.759> peasy<00:08:56.209> just 00:08:56.439 --> 00:08:56.449 align:start position:0% with your own token easy peasy just 00:08:56.449 --> 00:08:59.499 align:start position:0% with your own token easy peasy just changed<00:08:56.660> one<00:08:56.810> string<00:08:57.190> and<00:08:58.190> it<00:08:58.940> also<00:08:59.089> supports 00:08:59.499 --> 00:08:59.509 align:start position:0% changed one string and it also supports 00:08:59.509 --> 00:09:02.949 align:start position:0% changed one string and it also supports multi<00:08:59.959> coin<00:09:00.259> fees<00:09:00.670> so<00:09:01.670> we<00:09:01.790> think<00:09:02.180> the<00:09:02.329> economic 00:09:02.949 --> 00:09:02.959 align:start position:0% multi coin fees so we think the economic 00:09:02.959 --> 00:09:05.230 align:start position:0% multi coin fees so we think the economic module<00:09:03.410> model<00:09:04.370> approves<00:09:04.699> take<00:09:04.940> may<00:09:05.089> be<00:09:05.209> a 00:09:05.230 --> 00:09:05.240 align:start position:0% module model approves take may be a 00:09:05.240 --> 00:09:07.120 align:start position:0% module model approves take may be a little<00:09:05.449> different<00:09:05.959> for<00:09:06.440> example<00:09:06.860> for<00:09:07.040> the 00:09:07.120 --> 00:09:07.130 align:start position:0% little different for example for the 00:09:07.130 --> 00:09:08.769 align:start position:0% little different for example for the cosmos<00:09:07.519> Club<00:09:07.790> we<00:09:08.000> plan<00:09:08.209> to<00:09:08.240> accept 00:09:08.769 --> 00:09:08.779 align:start position:0% cosmos Club we plan to accept 00:09:08.779 --> 00:09:10.780 align:start position:0% cosmos Club we plan to accept transactions<00:09:09.440> or<00:09:09.649> we<00:09:09.740> plan<00:09:09.949> to<00:09:10.160> encourage<00:09:10.670> the 00:09:10.780 --> 00:09:10.790 align:start position:0% transactions or we plan to encourage the 00:09:10.790 --> 00:09:12.519 align:start position:0% transactions or we plan to encourage the validator<00:09:11.180> set<00:09:11.360> of<00:09:11.449> the<00:09:11.509> cosmos<00:09:11.839> hub<00:09:12.019> to 00:09:12.519 --> 00:09:12.529 align:start position:0% validator set of the cosmos hub to 00:09:12.529 --> 00:09:14.710 align:start position:0% validator set of the cosmos hub to accept<00:09:12.829> transactions<00:09:13.430> which<00:09:13.970> pay<00:09:14.240> fees<00:09:14.480> and 00:09:14.710 --> 00:09:14.720 align:start position:0% accept transactions which pay fees and 00:09:14.720 --> 00:09:16.090 align:start position:0% accept transactions which pay fees and lots<00:09:14.870> of<00:09:14.959> different<00:09:15.319> denominations<00:09:15.410> they 00:09:16.090 --> 00:09:16.100 align:start position:0% lots of different denominations they 00:09:16.100 --> 00:09:20.319 align:start position:0% lots of different denominations they don't<00:09:16.279> need<00:09:16.399> to<00:09:16.550> be<00:09:16.670> atoms<00:09:18.790> the<00:09:19.790> final<00:09:20.149> core 00:09:20.319 --> 00:09:20.329 align:start position:0% don't need to be atoms the final core 00:09:20.329 --> 00:09:22.300 align:start position:0% don't need to be atoms the final core module<00:09:20.720> and<00:09:20.930> my<00:09:21.079> favorite<00:09:21.500> is<00:09:21.649> inter 00:09:22.300 --> 00:09:22.310 align:start position:0% module and my favorite is inter 00:09:22.310 --> 00:09:24.639 align:start position:0% module and my favorite is inter blockchain<00:09:22.790> communication<00:09:23.509> so<00:09:24.139> this<00:09:24.380> is<00:09:24.529> the 00:09:24.639 --> 00:09:24.649 align:start position:0% blockchain communication so this is the 00:09:24.649 --> 00:09:26.290 align:start position:0% blockchain communication so this is the key<00:09:24.829> part<00:09:25.130> of<00:09:25.339> what<00:09:25.399> makes<00:09:25.699> the<00:09:25.910> cosmos 00:09:26.290 --> 00:09:26.300 align:start position:0% key part of what makes the cosmos 00:09:26.300 --> 00:09:29.439 align:start position:0% key part of what makes the cosmos network<00:09:26.630> model<00:09:26.990> tick<00:09:27.230> we've<00:09:28.130> exposed<00:09:28.699> the<00:09:28.970> IBC 00:09:29.439 --> 00:09:29.449 align:start position:0% network model tick we've exposed the IBC 00:09:29.449 --> 00:09:31.509 align:start position:0% network model tick we've exposed the IBC interface<00:09:29.930> which<00:09:30.290> is<00:09:30.410> a<00:09:30.440> payload<00:09:30.889> agnostic 00:09:31.509 --> 00:09:31.519 align:start position:0% interface which is a payload agnostic 00:09:31.519 --> 00:09:34.480 align:start position:0% interface which is a payload agnostic way<00:09:31.699> of<00:09:32.000> sending<00:09:33.040> authenticated<00:09:34.040> messages 00:09:34.480 --> 00:09:34.490 align:start position:0% way of sending authenticated messages 00:09:34.490 --> 00:09:37.120 align:start position:0% way of sending authenticated messages exactly<00:09:35.120> once<00:09:35.389> to<00:09:35.690> another<00:09:35.899> blockchain<00:09:36.440> it's 00:09:37.120 --> 00:09:37.130 align:start position:0% exactly once to another blockchain it's 00:09:37.130 --> 00:09:39.910 align:start position:0% exactly once to another blockchain it's a<00:09:37.160> little<00:09:37.399> like<00:09:37.610> tcp/ip<00:09:38.600> for<00:09:39.170> block<00:09:39.350> chains<00:09:39.620> on 00:09:39.910 --> 00:09:39.920 align:start position:0% a little like tcp/ip for block chains on 00:09:39.920 --> 00:09:42.670 align:start position:0% a little like tcp/ip for block chains on top<00:09:40.610> of<00:09:40.790> this<00:09:40.970> authenticated<00:09:41.959> exactly<00:09:42.470> ones 00:09:42.670 --> 00:09:42.680 align:start position:0% top of this authenticated exactly ones 00:09:42.680 --> 00:09:44.680 align:start position:0% top of this authenticated exactly ones message<00:09:43.040> delivery<00:09:43.490> primitive<00:09:43.940> you<00:09:44.509> can 00:09:44.680 --> 00:09:44.690 align:start position:0% message delivery primitive you can 00:09:44.690 --> 00:09:46.660 align:start position:0% message delivery primitive you can implement<00:09:44.990> lots<00:09:45.380> of<00:09:45.560> different<00:09:45.980> application 00:09:46.660 --> 00:09:46.670 align:start position:0% implement lots of different application 00:09:46.670 --> 00:09:48.999 align:start position:0% implement lots of different application level<00:09:46.940> guarantees<00:09:47.089> you<00:09:48.019> can<00:09:48.170> implement<00:09:48.440> token 00:09:48.999 --> 00:09:49.009 align:start position:0% level guarantees you can implement token 00:09:49.009 --> 00:09:50.110 align:start position:0% level guarantees you can implement token transfer<00:09:49.459> which<00:09:49.699> means<00:09:49.880> that<00:09:50.029> you're 00:09:50.110 --> 00:09:50.120 align:start position:0% transfer which means that you're 00:09:50.120 --> 00:09:52.150 align:start position:0% transfer which means that you're conserving<00:09:50.660> supply<00:09:51.050> across<00:09:51.829> two<00:09:52.130> different 00:09:52.150 --> 00:09:52.160 align:start position:0% conserving supply across two different 00:09:52.160 --> 00:09:53.889 align:start position:0% conserving supply across two different block<00:09:52.639> chains<00:09:52.910> you<00:09:53.420> could<00:09:53.600> implement 00:09:53.889 --> 00:09:53.899 align:start position:0% block chains you could implement 00:09:53.899 --> 00:09:56.199 align:start position:0% block chains you could implement transfer<00:09:54.889> of<00:09:55.040> unique<00:09:55.370> tokens<00:09:55.819> which<00:09:56.000> mean 00:09:56.199 --> 00:09:56.209 align:start position:0% transfer of unique tokens which mean 00:09:56.209 --> 00:09:58.990 align:start position:0% transfer of unique tokens which mean you're<00:09:56.750> conserving<00:09:57.290> the<00:09:57.550> existence<00:09:58.550> of<00:09:58.819> the 00:09:58.990 --> 00:09:59.000 align:start position:0% you're conserving the existence of the 00:09:59.000 --> 00:10:01.150 align:start position:0% you're conserving the existence of the particularly<00:09:59.480> unique<00:09:59.630> token<00:10:00.139> on<00:10:00.319> only<00:10:00.949> one 00:10:01.150 --> 00:10:01.160 align:start position:0% particularly unique token on only one 00:10:01.160 --> 00:10:04.120 align:start position:0% particularly unique token on only one chain<00:10:01.430> in<00:10:02.389> only<00:10:02.720> one<00:10:02.870> account<00:10:03.079> at<00:10:03.350> a<00:10:03.439> time<00:10:03.620> you 00:10:04.120 --> 00:10:04.130 align:start position:0% chain in only one account at a time you 00:10:04.130 --> 00:10:05.590 align:start position:0% chain in only one account at a time you could<00:10:04.310> transfer<00:10:04.579> data<00:10:04.850> or<00:10:05.120> you<00:10:05.269> could<00:10:05.389> even 00:10:05.590 --> 00:10:05.600 align:start position:0% could transfer data or you could even 00:10:05.600 --> 00:10:07.449 align:start position:0% could transfer data or you could even transfer<00:10:05.959> code<00:10:06.230> parts<00:10:06.980> of<00:10:07.069> your<00:10:07.189> smart 00:10:07.449 --> 00:10:07.459 align:start position:0% transfer code parts of your smart 00:10:07.459 --> 00:10:11.590 align:start position:0% transfer code parts of your smart contracts<00:10:08.029> in<00:10:08.149> some<00:10:08.300> kind<00:10:08.480> of<00:10:08.540> sharding<00:10:10.600> then 00:10:11.590 --> 00:10:11.600 align:start position:0% contracts in some kind of sharding then 00:10:11.600 --> 00:10:13.660 align:start position:0% contracts in some kind of sharding then the<00:10:12.110> special<00:10:12.529> module<00:10:12.889> for<00:10:13.069> this<00:10:13.160> presentation 00:10:13.660 --> 00:10:13.670 align:start position:0% the special module for this presentation 00:10:13.670 --> 00:10:17.350 align:start position:0% the special module for this presentation is<00:10:14.060> the<00:10:14.540> EVF<00:10:15.079> so<00:10:15.829> in<00:10:16.100> ether<00:10:16.370> mint<00:10:16.550> 2.0<00:10:17.060> we've 00:10:17.350 --> 00:10:17.360 align:start position:0% is the EVF so in ether mint 2.0 we've 00:10:17.360 --> 00:10:19.240 align:start position:0% is the EVF so in ether mint 2.0 we've taken<00:10:17.630> the<00:10:17.810> e<00:10:17.839> via<00:10:18.139> in<00:10:18.319> the<00:10:18.410> etherium<00:10:18.860> virtual 00:10:19.240 --> 00:10:19.250 align:start position:0% taken the e via in the etherium virtual 00:10:19.250 --> 00:10:21.370 align:start position:0% taken the e via in the etherium virtual machine<00:10:19.579> which<00:10:19.790> is<00:10:19.910> the<00:10:19.939> core<00:10:20.689> part<00:10:20.930> of<00:10:21.110> the 00:10:21.370 --> 00:10:21.380 align:start position:0% machine which is the core part of the 00:10:21.380 --> 00:10:23.230 align:start position:0% machine which is the core part of the etherium<00:10:21.920> block<00:10:22.130> chain<00:10:22.370> that<00:10:22.550> runs<00:10:22.610> all<00:10:22.970> your 00:10:23.230 --> 00:10:23.240 align:start position:0% etherium block chain that runs all your 00:10:23.240 --> 00:10:25.689 align:start position:0% etherium block chain that runs all your smart<00:10:23.509> contracts<00:10:23.930> and<00:10:24.259> put<00:10:24.980> it<00:10:25.100> in<00:10:25.220> a<00:10:25.279> cosmos 00:10:25.689 --> 00:10:25.699 align:start position:0% smart contracts and put it in a cosmos 00:10:25.699 --> 00:10:28.120 align:start position:0% smart contracts and put it in a cosmos SDK<00:10:26.120> module<00:10:26.509> has<00:10:27.259> all<00:10:27.439> the<00:10:27.560> features<00:10:27.709> you're 00:10:28.120 --> 00:10:28.130 align:start position:0% SDK module has all the features you're 00:10:28.130 --> 00:10:29.920 align:start position:0% SDK module has all the features you're used<00:10:28.370> to<00:10:28.459> an<00:10:28.790> account<00:10:29.029> database<00:10:29.449> and<00:10:29.689> a<00:10:29.720> state 00:10:29.920 --> 00:10:29.930 align:start position:0% used to an account database and a state 00:10:29.930 --> 00:10:32.019 align:start position:0% used to an account database and a state tree<00:10:30.139> it<00:10:30.470> can<00:10:30.589> run<00:10:30.829> aetherium<00:10:31.399> transactions 00:10:32.019 --> 00:10:32.029 align:start position:0% tree it can run aetherium transactions 00:10:32.029 --> 00:10:33.790 align:start position:0% tree it can run aetherium transactions that's<00:10:32.569> how<00:10:32.660> we've<00:10:32.810> been<00:10:32.839> testing<00:10:33.319> our<00:10:33.410> EVM 00:10:33.790 --> 00:10:33.800 align:start position:0% that's how we've been testing our EVM 00:10:33.800 --> 00:10:35.110 align:start position:0% that's how we've been testing our EVM implementation<00:10:34.399> by<00:10:34.579> running<00:10:34.790> the<00:10:34.970> actual 00:10:35.110 --> 00:10:35.120 align:start position:0% implementation by running the actual 00:10:35.120 --> 00:10:38.559 align:start position:0% implementation by running the actual theorem<00:10:35.689> transaction<00:10:36.230> history<00:10:37.089> but<00:10:38.089> most 00:10:38.559 --> 00:10:38.569 align:start position:0% theorem transaction history but most 00:10:38.569 --> 00:10:41.050 align:start position:0% theorem transaction history but most interestingly<00:10:38.870> it<00:10:39.470> can<00:10:39.860> call<00:10:40.130> to<00:10:40.550> and<00:10:40.819> from 00:10:41.050 --> 00:10:41.060 align:start position:0% interestingly it can call to and from 00:10:41.060 --> 00:10:43.960 align:start position:0% interestingly it can call to and from cosmos<00:10:41.720> SDK<00:10:42.199> modules<00:10:42.680> so<00:10:43.339> if<00:10:43.639> you<00:10:43.790> have<00:10:43.939> a 00:10:43.960 --> 00:10:43.970 align:start position:0% cosmos SDK modules so if you have a 00:10:43.970 --> 00:10:45.819 align:start position:0% cosmos SDK modules so if you have a block<00:10:44.240> chain<00:10:44.509> with<00:10:44.689> the<00:10:44.779> EVM<00:10:45.139> module<00:10:45.560> with<00:10:45.740> the 00:10:45.819 --> 00:10:45.829 align:start position:0% block chain with the EVM module with the 00:10:45.829 --> 00:10:47.199 align:start position:0% block chain with the EVM module with the governance<00:10:46.220> module<00:10:46.610> with<00:10:46.759> the<00:10:46.790> staking 00:10:47.199 --> 00:10:47.209 align:start position:0% governance module with the staking 00:10:47.209 --> 00:10:49.600 align:start position:0% governance module with the staking module<00:10:47.569> contracts<00:10:48.470> you<00:10:48.649> write<00:10:48.889> for<00:10:49.130> the<00:10:49.220> EVM 00:10:49.600 --> 00:10:49.610 align:start position:0% module contracts you write for the EVM 00:10:49.610 --> 00:10:52.179 align:start position:0% module contracts you write for the EVM module<00:10:50.029> can<00:10:50.569> talk<00:10:51.050> to<00:10:51.380> the<00:10:51.500> staking<00:10:51.860> module 00:10:52.179 --> 00:10:52.189 align:start position:0% module can talk to the staking module 00:10:52.189 --> 00:10:53.889 align:start position:0% module can talk to the staking module maybe<00:10:52.730> they<00:10:52.910> could<00:10:53.089> delegate<00:10:53.480> maybe<00:10:53.750> they 00:10:53.889 --> 00:10:53.899 align:start position:0% maybe they could delegate maybe they 00:10:53.899 --> 00:10:55.420 align:start position:0% maybe they could delegate maybe they could<00:10:54.050> query<00:10:54.259> balances<00:10:54.949> maybe<00:10:55.160> they<00:10:55.279> could 00:10:55.420 --> 00:10:55.430 align:start position:0% could query balances maybe they could 00:10:55.430 --> 00:10:57.220 align:start position:0% could query balances maybe they could see<00:10:55.639> when<00:10:55.759> people<00:10:55.790> got<00:10:56.180> slashed<00:10:56.569> or<00:10:56.899> do<00:10:57.050> things 00:10:57.220 --> 00:10:57.230 align:start position:0% see when people got slashed or do things 00:10:57.230 --> 00:10:59.650 align:start position:0% see when people got slashed or do things when<00:10:57.439> that<00:10:57.589> happens<00:10:58.120> similar<00:10:59.120> for<00:10:59.329> governance 00:10:59.650 --> 00:10:59.660 align:start position:0% when that happens similar for governance 00:10:59.660 --> 00:11:02.590 align:start position:0% when that happens similar for governance for<00:10:59.899> fee<00:11:00.019> distribution<00:11:00.589> and<00:11:00.740> for<00:11:01.220> IBC<00:11:01.699> so<00:11:02.389> if 00:11:02.590 --> 00:11:02.600 align:start position:0% for fee distribution and for IBC so if 00:11:02.600 --> 00:11:04.990 align:start position:0% for fee distribution and for IBC so if you<00:11:02.750> have<00:11:02.959> an<00:11:03.319> EVM<00:11:03.920> contract<00:11:04.459> on<00:11:04.670> a<00:11:04.699> blockchain 00:11:04.990 --> 00:11:05.000 align:start position:0% you have an EVM contract on a blockchain 00:11:05.000 --> 00:11:07.150 align:start position:0% you have an EVM contract on a blockchain in<00:11:05.809> the<00:11:05.930> cosmos<00:11:06.199> SDK<00:11:06.680> along 00:11:07.150 --> 00:11:07.160 align:start position:0% in the cosmos SDK along 00:11:07.160 --> 00:11:10.030 align:start position:0% in the cosmos SDK along the<00:11:07.279> IBC<00:11:07.670> module<00:11:08.110> contracts<00:11:09.110> running<00:11:09.800> on<00:11:09.920> that 00:11:10.030 --> 00:11:10.040 align:start position:0% the IBC module contracts running on that 00:11:10.040 --> 00:11:13.449 align:start position:0% the IBC module contracts running on that EVM<00:11:10.459> module<00:11:10.879> can<00:11:11.480> make<00:11:11.870> calls<00:11:12.139> through<00:11:12.500> IBC<00:11:13.069> to 00:11:13.449 --> 00:11:13.459 align:start position:0% EVM module can make calls through IBC to 00:11:13.459 --> 00:11:16.300 align:start position:0% EVM module can make calls through IBC to and<00:11:13.639> from<00:11:13.790> other<00:11:13.970> blockchains<00:11:14.949> in<00:11:15.949> order<00:11:16.190> to 00:11:16.300 --> 00:11:16.310 align:start position:0% and from other blockchains in order to 00:11:16.310 --> 00:11:17.590 align:start position:0% and from other blockchains in order to enable<00:11:16.490> this<00:11:16.759> we<00:11:17.029> need<00:11:17.240> and<00:11:17.480> we<00:11:17.569> have 00:11:17.590 --> 00:11:17.600 align:start position:0% enable this we need and we have 00:11:17.600 --> 00:11:19.930 align:start position:0% enable this we need and we have implemented<00:11:18.019> a<00:11:18.290> shared<00:11:18.560> state<00:11:18.889> view<00:11:19.190> so<00:11:19.790> there 00:11:19.930 --> 00:11:19.940 align:start position:0% implemented a shared state view so there 00:11:19.940 --> 00:11:22.059 align:start position:0% implemented a shared state view so there is<00:11:20.060> one<00:11:20.300> token<00:11:20.779> or<00:11:21.019> only<00:11:21.589> needs<00:11:21.769> to<00:11:21.949> be<00:11:21.980> one 00:11:22.059 --> 00:11:22.069 align:start position:0% is one token or only needs to be one 00:11:22.069 --> 00:11:24.249 align:start position:0% is one token or only needs to be one token<00:11:22.639> on<00:11:22.759> this<00:11:22.940> blockchain<00:11:23.420> which<00:11:23.629> will<00:11:24.139> be 00:11:24.249 --> 00:11:24.259 align:start position:0% token on this blockchain which will be 00:11:24.259 --> 00:11:26.619 align:start position:0% token on this blockchain which will be either<00:11:24.470> quote<00:11:24.980> unquote<00:11:25.100> in<00:11:25.550> the<00:11:25.699> EVM<00:11:26.060> message 00:11:26.619 --> 00:11:26.629 align:start position:0% either quote unquote in the EVM message 00:11:26.629 --> 00:11:28.780 align:start position:0% either quote unquote in the EVM message dot<00:11:26.839> value<00:11:27.050> for<00:11:27.769> those<00:11:28.160> of<00:11:28.339> you<00:11:28.430> familiar<00:11:28.519> with 00:11:28.780 --> 00:11:28.790 align:start position:0% dot value for those of you familiar with 00:11:28.790 --> 00:11:31.480 align:start position:0% dot value for those of you familiar with solidity<00:11:29.209> but<00:11:30.050> which<00:11:30.259> will<00:11:30.470> be<00:11:30.649> the<00:11:30.920> token 00:11:31.480 --> 00:11:31.490 align:start position:0% solidity but which will be the token 00:11:31.490 --> 00:11:33.249 align:start position:0% solidity but which will be the token used<00:11:31.790> for<00:11:32.060> governance<00:11:32.449> possibly<00:11:32.959> for<00:11:33.110> proof 00:11:33.249 --> 00:11:33.259 align:start position:0% used for governance possibly for proof 00:11:33.259 --> 00:11:35.110 align:start position:0% used for governance possibly for proof of<00:11:33.350> stake<00:11:33.589> and<00:11:33.829> fee<00:11:33.920> distribution<00:11:34.459> and<00:11:34.730> the 00:11:35.110 --> 00:11:35.120 align:start position:0% of stake and fee distribution and the 00:11:35.120 --> 00:11:37.800 align:start position:0% of stake and fee distribution and the other<00:11:35.269> causing<00:11:35.600> assist<00:11:35.839> eke<00:11:35.959> eight<00:11:36.079> modules 00:11:37.800 --> 00:11:37.810 align:start position:0% other causing assist eke eight modules 00:11:37.810 --> 00:11:40.720 align:start position:0% other causing assist eke eight modules so<00:11:38.810> ether<00:11:39.800> meant<00:11:39.980> the<00:11:40.160> whole<00:11:40.310> package 00:11:40.720 --> 00:11:40.730 align:start position:0% so ether meant the whole package 00:11:40.730 --> 00:11:43.030 align:start position:0% so ether meant the whole package combines<00:11:41.269> the<00:11:41.449> cosmos<00:11:41.810> SDK<00:11:42.259> all<00:11:42.649> of<00:11:42.920> these 00:11:43.030 --> 00:11:43.040 align:start position:0% combines the cosmos SDK all of these 00:11:43.040 --> 00:11:45.670 align:start position:0% combines the cosmos SDK all of these core<00:11:43.310> modules<00:11:43.670> we've<00:11:43.819> built<00:11:44.060> the<00:11:44.839> EVM<00:11:45.259> module 00:11:45.670 --> 00:11:45.680 align:start position:0% core modules we've built the EVM module 00:11:45.680 --> 00:11:48.699 align:start position:0% core modules we've built the EVM module and<00:11:45.889> a<00:11:46.399> web<00:11:46.610> 3<00:11:46.850> API<00:11:47.180> layer<00:11:47.509> we<00:11:48.290> think<00:11:48.560> this 00:11:48.699 --> 00:11:48.709 align:start position:0% and a web 3 API layer we think this 00:11:48.709 --> 00:11:50.980 align:start position:0% and a web 3 API layer we think this provides<00:11:48.889> a<00:11:49.279> pretty<00:11:49.430> compelling<00:11:49.939> deal<00:11:50.420> you 00:11:50.980 --> 00:11:50.990 align:start position:0% provides a pretty compelling deal you 00:11:50.990 --> 00:11:52.509 align:start position:0% provides a pretty compelling deal you get<00:11:51.139> the<00:11:51.259> scalability<00:11:51.949> of<00:11:52.009> ten<00:11:52.250> durman's 00:11:52.509 --> 00:11:52.519 align:start position:0% get the scalability of ten durman's 00:11:52.519 --> 00:11:54.730 align:start position:0% get the scalability of ten durman's Byzantine<00:11:53.360> fault<00:11:53.600> tolerant<00:11:54.019> consensus<00:11:54.529> 2 00:11:54.730 --> 00:11:54.740 align:start position:0% Byzantine fault tolerant consensus 2 00:11:54.740 --> 00:11:56.679 align:start position:0% Byzantine fault tolerant consensus 2 second<00:11:55.129> block<00:11:55.279> latency<00:11:55.790> instant<00:11:56.240> finality 00:11:56.679 --> 00:11:56.689 align:start position:0% second block latency instant finality 00:11:56.689 --> 00:11:59.259 align:start position:0% second block latency instant finality the<00:11:57.230> power<00:11:57.410> of<00:11:57.680> the<00:11:57.800> cosmos<00:11:58.129> SDK<00:11:58.610> lease 00:11:59.259 --> 00:11:59.269 align:start position:0% the power of the cosmos SDK lease 00:11:59.269 --> 00:12:01.150 align:start position:0% the power of the cosmos SDK lease capabilities<00:11:59.959> security<00:12:00.470> the<00:12:00.680> ability<00:12:01.040> to 00:12:01.150 --> 00:12:01.160 align:start position:0% capabilities security the ability to 00:12:01.160 --> 00:12:02.740 align:start position:0% capabilities security the ability to integrate<00:12:01.370> all<00:12:01.819> these<00:12:02.089> modules<00:12:02.329> and 00:12:02.740 --> 00:12:02.750 align:start position:0% integrate all these modules and 00:12:02.750 --> 00:12:05.379 align:start position:0% integrate all these modules and contribute<00:12:03.139> downstream<00:12:03.620> and<00:12:04.040> the<00:12:04.389> existing 00:12:05.379 --> 00:12:05.389 align:start position:0% contribute downstream and the existing 00:12:05.389 --> 00:12:07.540 align:start position:0% contribute downstream and the existing ecosystem<00:12:05.569> of<00:12:06.259> etherion<00:12:06.829> contracts<00:12:07.310> and 00:12:07.540 --> 00:12:07.550 align:start position:0% ecosystem of etherion contracts and 00:12:07.550 --> 00:12:09.790 align:start position:0% ecosystem of etherion contracts and development<00:12:08.060> tooling<00:12:08.389> truffle<00:12:09.199> metamath 00:12:09.790 --> 00:12:09.800 align:start position:0% development tooling truffle metamath 00:12:09.800 --> 00:12:11.490 align:start position:0% development tooling truffle metamath solidity<00:12:10.370> you<00:12:10.670> name<00:12:10.850> it 00:12:11.490 --> 00:12:11.500 align:start position:0% solidity you name it 00:12:11.500 --> 00:12:14.319 align:start position:0% solidity you name it but<00:12:12.500> we've<00:12:12.649> even<00:12:12.889> done<00:12:13.009> more<00:12:13.250> than<00:12:13.399> that<00:12:13.519> not 00:12:14.319 --> 00:12:14.329 align:start position:0% but we've even done more than that not 00:12:14.329 --> 00:12:16.329 align:start position:0% but we've even done more than that not we<00:12:14.660> have<00:12:14.750> not<00:12:14.899> just<00:12:15.199> poured<00:12:15.500> it<00:12:15.620> as<00:12:15.800> an<00:12:15.980> ether 00:12:16.329 --> 00:12:16.339 align:start position:0% we have not just poured it as an ether 00:12:16.339 --> 00:12:19.660 align:start position:0% we have not just poured it as an ether mat<00:12:16.459> 1.0<00:12:17.000> the<00:12:17.540> evo<00:12:17.839> module<00:12:18.319> from<00:12:18.470> death<00:12:19.399> we've 00:12:19.660 --> 00:12:19.670 align:start position:0% mat 1.0 the evo module from death we've 00:12:19.670 --> 00:12:21.819 align:start position:0% mat 1.0 the evo module from death we've ported<00:12:20.000> the<00:12:20.060> Evo<00:12:20.329> module<00:12:20.779> from<00:12:21.110> turbo<00:12:21.620> goth 00:12:21.819 --> 00:12:21.829 align:start position:0% ported the Evo module from turbo goth 00:12:21.829 --> 00:12:24.689 align:start position:0% ported the Evo module from turbo goth which<00:12:22.610> Alexei<00:12:23.000> is<00:12:23.029> working<00:12:23.420> on<00:12:23.480> that<00:12:24.259> is 00:12:24.689 --> 00:12:24.699 align:start position:0% which Alexei is working on that is 00:12:24.699 --> 00:12:26.920 align:start position:0% which Alexei is working on that is features<00:12:25.699> a<00:12:25.730> lot<00:12:25.939> of<00:12:26.029> improvements<00:12:26.660> over<00:12:26.779> the 00:12:26.920 --> 00:12:26.930 align:start position:0% features a lot of improvements over the 00:12:26.930 --> 00:12:29.259 align:start position:0% features a lot of improvements over the base<00:12:27.170> EVM<00:12:27.709> it's<00:12:28.130> faster<00:12:28.610> we've<00:12:28.819> changed<00:12:29.029> up 00:12:29.259 --> 00:12:29.269 align:start position:0% base EVM it's faster we've changed up 00:12:29.269 --> 00:12:31.300 align:start position:0% base EVM it's faster we've changed up how<00:12:29.360> the<00:12:29.420> database<00:12:29.660> works<00:12:30.079> of<00:12:30.829> course<00:12:31.100> it 00:12:31.300 --> 00:12:31.310 align:start position:0% how the database works of course it 00:12:31.310 --> 00:12:32.889 align:start position:0% how the database works of course it connects<00:12:31.639> through<00:12:31.939> the<00:12:32.149> SDK<00:12:32.569> module 00:12:32.889 --> 00:12:32.899 align:start position:0% connects through the SDK module 00:12:32.899 --> 00:12:34.990 align:start position:0% connects through the SDK module interface<00:12:33.319> so<00:12:33.680> you<00:12:33.740> can<00:12:33.949> have<00:12:34.130> what<00:12:34.670> are<00:12:34.790> like 00:12:34.990 --> 00:12:35.000 align:start position:0% interface so you can have what are like 00:12:35.000 --> 00:12:36.850 align:start position:0% interface so you can have what are like pre<00:12:35.240> compiles<00:12:35.810> in<00:12:35.959> the<00:12:36.050> EVM<00:12:36.380> but<00:12:36.589> which<00:12:36.680> really 00:12:36.850 --> 00:12:36.860 align:start position:0% pre compiles in the EVM but which really 00:12:36.860 --> 00:12:39.819 align:start position:0% pre compiles in the EVM but which really call<00:12:37.399> in<00:12:37.579> to<00:12:37.699> other<00:12:37.850> cosmos<00:12:38.810> SDK<00:12:39.199> modules<00:12:39.620> or 00:12:39.819 --> 00:12:39.829 align:start position:0% call in to other cosmos SDK modules or 00:12:39.829 --> 00:12:44.199 align:start position:0% call in to other cosmos SDK modules or vice<00:12:40.009> versa<00:12:41.829> Turbo<00:12:42.829> goth<00:12:43.009> I<00:12:43.610> will<00:12:43.910> encourage 00:12:44.199 --> 00:12:44.209 align:start position:0% vice versa Turbo goth I will encourage 00:12:44.209 --> 00:12:46.720 align:start position:0% vice versa Turbo goth I will encourage you<00:12:44.449> to<00:12:44.630> take<00:12:44.870> a<00:12:44.930> stop<00:12:45.589> at<00:12:46.040> Alexie's<00:12:46.430> talk 00:12:46.720 --> 00:12:46.730 align:start position:0% you to take a stop at Alexie's talk 00:12:46.730 --> 00:12:49.030 align:start position:0% you to take a stop at Alexie's talk which<00:12:47.089> is<00:12:47.120> tomorrow<00:12:48.079> afternoon<00:12:48.259> same<00:12:48.829> time 00:12:49.030 --> 00:12:49.040 align:start position:0% which is tomorrow afternoon same time 00:12:49.040 --> 00:12:51.490 align:start position:0% which is tomorrow afternoon same time but<00:12:49.519> in<00:12:49.730> brief<00:12:50.029> a<00:12:50.360> turbo<00:12:50.720> gap<00:12:50.899> which<00:12:51.170> is<00:12:51.199> being 00:12:51.490 --> 00:12:51.500 align:start position:0% but in brief a turbo gap which is being 00:12:51.500 --> 00:12:53.170 align:start position:0% but in brief a turbo gap which is being developed<00:12:51.709> in<00:12:51.949> parallel<00:12:52.430> as<00:12:52.639> an<00:12:52.790> aetherium 00:12:53.170 --> 00:12:53.180 align:start position:0% developed in parallel as an aetherium 00:12:53.180 --> 00:12:55.660 align:start position:0% developed in parallel as an aetherium client<00:12:53.600> along<00:12:54.319> with<00:12:54.470> the<00:12:54.559> cosmos<00:12:54.860> sdk<00:12:55.250> module 00:12:55.660 --> 00:12:55.670 align:start position:0% client along with the cosmos sdk module 00:12:55.670 --> 00:12:58.660 align:start position:0% client along with the cosmos sdk module has<00:12:56.649> numerous<00:12:57.649> improvements<00:12:57.980> over<00:12:58.519> the 00:12:58.660 --> 00:12:58.670 align:start position:0% has numerous improvements over the 00:12:58.670 --> 00:13:01.540 align:start position:0% has numerous improvements over the current<00:12:58.939> available<00:12:59.809> EVM<00:13:00.139> implementations<00:13:00.889> it 00:13:01.540 --> 00:13:01.550 align:start position:0% current available EVM implementations it 00:13:01.550 --> 00:13:04.269 align:start position:0% current available EVM implementations it supports<00:13:01.970> any<00:13:02.120> binary<00:13:02.449> search<00:13:02.870> tree<00:13:03.279> has 00:13:04.269 --> 00:13:04.279 align:start position:0% supports any binary search tree has 00:13:04.279 --> 00:13:05.619 align:start position:0% supports any binary search tree has structure<00:13:04.730> preserving<00:13:05.240> custom 00:13:05.619 --> 00:13:05.629 align:start position:0% structure preserving custom 00:13:05.629 --> 00:13:08.019 align:start position:0% structure preserving custom serialization<00:13:06.319> as<00:13:06.589> opposed<00:13:06.860> to<00:13:06.889> our<00:13:07.069> LP<00:13:07.370> which 00:13:08.019 --> 00:13:08.029 align:start position:0% serialization as opposed to our LP which 00:13:08.029 --> 00:13:10.269 align:start position:0% serialization as opposed to our LP which is<00:13:08.149> much<00:13:08.269> faster<00:13:08.449> it<00:13:09.290> allows<00:13:09.529> you<00:13:09.709> to<00:13:09.769> use<00:13:10.069> the 00:13:10.269 --> 00:13:10.279 align:start position:0% is much faster it allows you to use the 00:13:10.279 --> 00:13:11.710 align:start position:0% is much faster it allows you to use the same<00:13:10.490> data<00:13:10.819> structure<00:13:11.089> for<00:13:11.300> database 00:13:11.710 --> 00:13:11.720 align:start position:0% same data structure for database 00:13:11.720 --> 00:13:14.230 align:start position:0% same data structure for database indexing<00:13:12.139> and<00:13:12.319> merggle<00:13:12.649> hosting<00:13:13.009> also<00:13:13.879> faster 00:13:14.230 --> 00:13:14.240 align:start position:0% indexing and merggle hosting also faster 00:13:14.240 --> 00:13:16.150 align:start position:0% indexing and merggle hosting also faster and<00:13:14.509> it<00:13:15.050> implements<00:13:15.500> a<00:13:15.589> new<00:13:15.709> caching 00:13:16.150 --> 00:13:16.160 align:start position:0% and it implements a new caching 00:13:16.160 --> 00:13:18.069 align:start position:0% and it implements a new caching strategies<00:13:16.699> in<00:13:17.029> particular<00:13:17.269> for<00:13:17.600> state<00:13:17.779> sync 00:13:18.069 --> 00:13:18.079 align:start position:0% strategies in particular for state sync 00:13:18.079 --> 00:13:19.630 align:start position:0% strategies in particular for state sync using<00:13:18.410> the<00:13:18.500> benefit<00:13:18.829> of<00:13:18.920> hindsight 00:13:19.630 --> 00:13:19.640 align:start position:0% using the benefit of hindsight 00:13:19.640 --> 00:13:21.430 align:start position:0% using the benefit of hindsight so<00:13:20.060> using<00:13:20.269> the<00:13:20.480> fact<00:13:20.690> that<00:13:20.779> you<00:13:20.930> know<00:13:21.140> what 00:13:21.430 --> 00:13:21.440 align:start position:0% so using the fact that you know what 00:13:21.440 --> 00:13:23.259 align:start position:0% so using the fact that you know what future<00:13:21.709> transactions<00:13:22.370> are<00:13:22.519> or<00:13:22.700> future<00:13:23.000> states 00:13:23.259 --> 00:13:23.269 align:start position:0% future transactions are or future states 00:13:23.269 --> 00:13:24.790 align:start position:0% future transactions are or future states when<00:13:23.810> you're<00:13:23.990> trying<00:13:24.140> to<00:13:24.260> sink<00:13:24.529> past 00:13:24.790 --> 00:13:24.800 align:start position:0% when you're trying to sink past 00:13:24.800 --> 00:13:28.930 align:start position:0% when you're trying to sink past transactions<00:13:25.339> and<00:13:25.519> verify<00:13:25.820> them<00:13:27.670> now<00:13:28.670> there 00:13:28.930 --> 00:13:28.940 align:start position:0% transactions and verify them now there 00:13:28.940 --> 00:13:31.060 align:start position:0% transactions and verify them now there are<00:13:29.000> two<00:13:29.240> ways<00:13:29.420> to<00:13:29.450> use<00:13:29.959> the<00:13:30.110> EVM<00:13:30.470> module<00:13:30.860> as 00:13:31.060 --> 00:13:31.070 align:start position:0% are two ways to use the EVM module as 00:13:31.070 --> 00:13:33.579 align:start position:0% are two ways to use the EVM module as I've<00:13:31.220> alluded<00:13:31.430> to<00:13:31.700> ether<00:13:32.630> mint<00:13:32.839> will<00:13:33.019> exist<00:13:33.380> as 00:13:33.579 --> 00:13:33.589 align:start position:0% I've alluded to ether mint will exist as 00:13:33.589 --> 00:13:36.069 align:start position:0% I've alluded to ether mint will exist as a<00:13:33.620> particular<00:13:34.220> block<00:13:34.490> chain<00:13:34.790> as<00:13:35.000> a<00:13:35.570> proof<00:13:35.959> of 00:13:36.069 --> 00:13:36.079 align:start position:0% a particular block chain as a proof of 00:13:36.079 --> 00:13:38.350 align:start position:0% a particular block chain as a proof of stake<00:13:36.320> chain<00:13:36.620> with<00:13:37.399> all<00:13:37.579> the<00:13:37.730> core<00:13:37.940> modules 00:13:38.350 --> 00:13:38.360 align:start position:0% stake chain with all the core modules 00:13:38.360 --> 00:13:40.000 align:start position:0% stake chain with all the core modules with<00:13:38.570> the<00:13:38.600> EBA<00:13:38.930> motto<00:13:39.200> and<00:13:39.440> with<00:13:39.560> a<00:13:39.589> web<00:13:39.800> 3 00:13:40.000 --> 00:13:40.010 align:start position:0% with the EBA motto and with a web 3 00:13:40.010 --> 00:13:42.160 align:start position:0% with the EBA motto and with a web 3 interface<00:13:40.250> for<00:13:41.120> running<00:13:41.450> smart<00:13:41.720> contracts 00:13:42.160 --> 00:13:42.170 align:start position:0% interface for running smart contracts 00:13:42.170 --> 00:13:44.500 align:start position:0% interface for running smart contracts but<00:13:42.980> the<00:13:43.100> EVM<00:13:43.399> ECHA<00:13:43.579> will<00:13:43.760> also<00:13:44.060> exist<00:13:44.269> as<00:13:44.480> a 00:13:44.500 --> 00:13:44.510 align:start position:0% but the EVM ECHA will also exist as a 00:13:44.510 --> 00:13:47.110 align:start position:0% but the EVM ECHA will also exist as a library<00:13:44.990> the<00:13:45.709> EVM<00:13:45.980> module<00:13:46.279> is<00:13:46.399> a<00:13:46.430> library<00:13:46.910> will 00:13:47.110 --> 00:13:47.120 align:start position:0% library the EVM module is a library will 00:13:47.120 --> 00:13:48.850 align:start position:0% library the EVM module is a library will allow<00:13:47.269> you<00:13:47.329> to<00:13:47.480> deploy<00:13:47.899> your<00:13:48.170> own<00:13:48.350> cosmos 00:13:48.850 --> 00:13:48.860 align:start position:0% allow you to deploy your own cosmos 00:13:48.860 --> 00:13:52.120 align:start position:0% allow you to deploy your own cosmos chain<00:13:49.130> with<00:13:49.760> EVM<00:13:50.240> support<00:13:50.660> add<00:13:51.140> in<00:13:51.380> other<00:13:51.560> SDK 00:13:52.120 --> 00:13:52.130 align:start position:0% chain with EVM support add in other SDK 00:13:52.130 --> 00:13:54.130 align:start position:0% chain with EVM support add in other SDK modules<00:13:52.550> in<00:13:52.910> whichever<00:13:53.149> combinations<00:13:53.870> and 00:13:54.130 --> 00:13:54.140 align:start position:0% modules in whichever combinations and 00:13:54.140 --> 00:13:56.980 align:start position:0% modules in whichever combinations and parameter<00:13:54.529> choices<00:13:54.980> you<00:13:55.100> like<00:13:55.570> and<00:13:56.570> choose 00:13:56.980 --> 00:13:56.990 align:start position:0% parameter choices you like and choose 00:13:56.990 --> 00:13:59.050 align:start position:0% parameter choices you like and choose whatever<00:13:57.350> token<00:13:57.890> in<00:13:58.130> economic<00:13:58.579> model<00:13:58.880> you 00:13:59.050 --> 00:13:59.060 align:start position:0% whatever token in economic model you 00:13:59.060 --> 00:14:02.769 align:start position:0% whatever token in economic model you want<00:14:00.399> the<00:14:01.399> e<00:14:01.430> thurman<00:14:01.850> chain<00:14:02.089> will<00:14:02.329> also<00:14:02.630> be 00:14:02.769 --> 00:14:02.779 align:start position:0% want the e thurman chain will also be 00:14:02.779 --> 00:14:04.240 align:start position:0% want the e thurman chain will also be launched<00:14:03.170> with<00:14:03.380> a<00:14:03.410> term<00:14:03.800> you<00:14:03.950> might<00:14:04.100> have 00:14:04.240 --> 00:14:04.250 align:start position:0% launched with a term you might have 00:14:04.250 --> 00:14:07.060 align:start position:0% launched with a term you might have heard<00:14:04.490> the<00:14:04.790> hard<00:14:05.120> spoon<00:14:05.750> what's<00:14:06.500> a<00:14:06.589> hard<00:14:06.769> spoon 00:14:07.060 --> 00:14:07.070 align:start position:0% heard the hard spoon what's a hard spoon 00:14:07.070 --> 00:14:10.030 align:start position:0% heard the hard spoon what's a hard spoon a<00:14:07.279> hard<00:14:07.910> spoon<00:14:08.180> is<00:14:08.450> to<00:14:08.690> copy<00:14:09.019> the<00:14:09.529> token 00:14:10.030 --> 00:14:10.040 align:start position:0% a hard spoon is to copy the token 00:14:10.040 --> 00:14:12.370 align:start position:0% a hard spoon is to copy the token distribution<00:14:10.730> including<00:14:11.120> multi<00:14:11.899> signatures 00:14:12.370 --> 00:14:12.380 align:start position:0% distribution including multi signatures 00:14:12.380 --> 00:14:15.730 align:start position:0% distribution including multi signatures from<00:14:13.190> another<00:14:13.579> chain<00:14:13.940> onto<00:14:14.240> a<00:14:14.450> new<00:14:14.690> chain<00:14:14.930> so 00:14:15.730 --> 00:14:15.740 align:start position:0% from another chain onto a new chain so 00:14:15.740 --> 00:14:17.290 align:start position:0% from another chain onto a new chain so in<00:14:15.920> particular<00:14:16.070> for<00:14:16.579> a<00:14:16.700> thurman<00:14:17.060> were 00:14:17.290 --> 00:14:17.300 align:start position:0% in particular for a thurman were 00:14:17.300 --> 00:14:19.720 align:start position:0% in particular for a thurman were planning<00:14:17.750> to<00:14:17.779> copy<00:14:18.170> balance<00:14:19.160> subject<00:14:19.610> to 00:14:19.720 --> 00:14:19.730 align:start position:0% planning to copy balance subject to 00:14:19.730 --> 00:14:21.699 align:start position:0% planning to copy balance subject to approval<00:14:20.000> by<00:14:20.209> cosmo<00:14:20.660> sub<00:14:20.839> governance<00:14:21.230> to<00:14:21.529> copy 00:14:21.699 --> 00:14:21.709 align:start position:0% approval by cosmo sub governance to copy 00:14:21.709 --> 00:14:24.069 align:start position:0% approval by cosmo sub governance to copy balances<00:14:22.370> from<00:14:22.640> the<00:14:23.300> etherium<00:14:23.779> chain 00:14:24.069 --> 00:14:24.079 align:start position:0% balances from the etherium chain 00:14:24.079 --> 00:14:26.319 align:start position:0% balances from the etherium chain possibly<00:14:24.980> also<00:14:25.160> atoms<00:14:25.640> from<00:14:25.880> the<00:14:25.970> cosmos 00:14:26.319 --> 00:14:26.329 align:start position:0% possibly also atoms from the cosmos 00:14:26.329 --> 00:14:28.990 align:start position:0% possibly also atoms from the cosmos chain<00:14:26.600> and<00:14:26.870> use<00:14:27.440> that<00:14:27.649> to<00:14:27.980> seed<00:14:28.279> the<00:14:28.579> photon 00:14:28.990 --> 00:14:29.000 align:start position:0% chain and use that to seed the photon 00:14:29.000 --> 00:14:31.150 align:start position:0% chain and use that to seed the photon token<00:14:29.510> which<00:14:29.899> will<00:14:30.170> be<00:14:30.260> the<00:14:30.380> native<00:14:30.560> token<00:14:31.010> on 00:14:31.150 --> 00:14:31.160 align:start position:0% token which will be the native token on 00:14:31.160 --> 00:14:33.939 align:start position:0% token which will be the native token on a<00:14:31.339> thurmond<00:14:31.690> ether<00:14:32.690> meant<00:14:32.870> we'll<00:14:33.019> have<00:14:33.199> we 00:14:33.939 --> 00:14:33.949 align:start position:0% a thurmond ether meant we'll have we 00:14:33.949 --> 00:14:36.220 align:start position:0% a thurmond ether meant we'll have we plan<00:14:34.220> shared<00:14:34.730> security<00:14:35.149> with<00:14:35.540> the<00:14:35.660> cosmos<00:14:35.990> hub 00:14:36.220 --> 00:14:36.230 align:start position:0% plan shared security with the cosmos hub 00:14:36.230 --> 00:14:38.350 align:start position:0% plan shared security with the cosmos hub meaning<00:14:37.040> that<00:14:37.190> anyone<00:14:37.579> who<00:14:37.760> wants<00:14:37.970> to<00:14:38.060> attack 00:14:38.350 --> 00:14:38.360 align:start position:0% meaning that anyone who wants to attack 00:14:38.360 --> 00:14:40.030 align:start position:0% meaning that anyone who wants to attack either<00:14:38.600> mint<00:14:38.930> would<00:14:39.380> have<00:14:39.560> to<00:14:39.680> pay<00:14:39.860> the 00:14:40.030 --> 00:14:40.040 align:start position:0% either mint would have to pay the 00:14:40.040 --> 00:14:41.710 align:start position:0% either mint would have to pay the combined<00:14:40.430> cost<00:14:40.730> of<00:14:41.000> attacking<00:14:41.269> two<00:14:41.540> block 00:14:41.710 --> 00:14:41.720 align:start position:0% combined cost of attacking two block 00:14:41.720 --> 00:14:44.259 align:start position:0% combined cost of attacking two block chains<00:14:42.339> of<00:14:43.339> course<00:14:43.610> this<00:14:43.760> will<00:14:43.910> all<00:14:44.000> need<00:14:44.180> to 00:14:44.259 --> 00:14:44.269 align:start position:0% chains of course this will all need to 00:14:44.269 --> 00:14:46.150 align:start position:0% chains of course this will all need to be<00:14:44.360> approved<00:14:44.660> by<00:14:44.930> cosmos<00:14:45.410> self<00:14:45.560> governance<00:14:45.920> so 00:14:46.150 --> 00:14:46.160 align:start position:0% be approved by cosmos self governance so 00:14:46.160 --> 00:14:48.189 align:start position:0% be approved by cosmos self governance so we're<00:14:46.279> focusing<00:14:46.730> on<00:14:47.000> building<00:14:47.750> the<00:14:48.019> software 00:14:48.189 --> 00:14:48.199 align:start position:0% we're focusing on building the software 00:14:48.199 --> 00:14:49.870 align:start position:0% we're focusing on building the software to<00:14:48.589> enable<00:14:48.890> heart<00:14:49.430> Spoons 00:14:49.870 --> 00:14:49.880 align:start position:0% to enable heart Spoons 00:14:49.880 --> 00:14:52.120 align:start position:0% to enable heart Spoons in<00:14:50.000> any<00:14:50.570> configuration<00:14:50.899> you<00:14:51.500> want<00:14:51.680> or<00:14:51.949> maybe 00:14:52.120 --> 00:14:52.130 align:start position:0% in any configuration you want or maybe 00:14:52.130 --> 00:14:54.639 align:start position:0% in any configuration you want or maybe even<00:14:52.220> a<00:14:52.610> hard<00:14:52.820> sport<00:14:53.180> which<00:14:53.750> dices<00:14:54.230> upstate 00:14:54.639 --> 00:14:54.649 align:start position:0% even a hard sport which dices upstate 00:14:54.649 --> 00:14:58.740 align:start position:0% even a hard sport which dices upstate and<00:14:54.890> rearranges<00:14:55.459> it<00:14:55.870> but<00:14:56.870> we<00:14:57.320> do<00:14:57.709> expect<00:14:58.130> to 00:14:58.740 --> 00:14:58.750 align:start position:0% and rearranges it but we do expect to 00:14:58.750 --> 00:15:01.060 align:start position:0% and rearranges it but we do expect to propose<00:14:59.750> this<00:14:59.959> particular<00:15:00.260> plan<00:15:00.649> and<00:15:00.980> we 00:15:01.060 --> 00:15:01.070 align:start position:0% propose this particular plan and we 00:15:01.070 --> 00:15:03.189 align:start position:0% propose this particular plan and we expect<00:15:01.459> photons<00:15:01.880> will<00:15:02.269> be<00:15:02.390> accepted<00:15:02.870> as<00:15:02.990> a<00:15:03.019> fee 00:15:03.189 --> 00:15:03.199 align:start position:0% expect photons will be accepted as a fee 00:15:03.199 --> 00:15:05.050 align:start position:0% expect photons will be accepted as a fee token<00:15:03.560> on<00:15:03.709> the<00:15:03.829> hub<00:15:04.010> which<00:15:04.640> is<00:15:04.670> super 00:15:05.050 --> 00:15:05.060 align:start position:0% token on the hub which is super 00:15:05.060 --> 00:15:07.120 align:start position:0% token on the hub which is super important<00:15:05.570> for<00:15:05.660> user<00:15:06.110> experience<00:15:06.440> as<00:15:06.980> I'll 00:15:07.120 --> 00:15:07.130 align:start position:0% important for user experience as I'll 00:15:07.130 --> 00:15:08.310 align:start position:0% important for user experience as I'll get<00:15:07.250> you<00:15:07.370> later 00:15:08.310 --> 00:15:08.320 align:start position:0% get you later 00:15:08.320 --> 00:15:10.630 align:start position:0% get you later so<00:15:09.320> either<00:15:09.560> where<00:15:09.769> does<00:15:09.890> a<00:15:09.920> blockchain<00:15:10.220> is 00:15:10.630 --> 00:15:10.640 align:start position:0% so either where does a blockchain is 00:15:10.640 --> 00:15:13.150 align:start position:0% so either where does a blockchain is designed<00:15:11.089> to<00:15:11.240> be<00:15:11.360> like<00:15:11.750> aetherium<00:15:12.260> one<00:15:12.860> chain 00:15:13.150 --> 00:15:13.160 align:start position:0% designed to be like aetherium one chain 00:15:13.160 --> 00:15:16.030 align:start position:0% designed to be like aetherium one chain for<00:15:13.490> many<00:15:13.670> EVM<00:15:14.149> applications<00:15:14.779> at<00:15:15.050> once<00:15:15.079> well 00:15:16.030 --> 00:15:16.040 align:start position:0% for many EVM applications at once well 00:15:16.040 --> 00:15:17.980 align:start position:0% for many EVM applications at once well hard<00:15:16.250> Spoon<00:15:16.459> account<00:15:16.790> balances<00:15:17.269> so<00:15:17.510> users<00:15:17.839> can 00:15:17.980 --> 00:15:17.990 align:start position:0% hard Spoon account balances so users can 00:15:17.990 --> 00:15:20.050 align:start position:0% hard Spoon account balances so users can start<00:15:18.199> out<00:15:18.380> with<00:15:18.709> tokens<00:15:19.370> to<00:15:19.490> start<00:15:19.699> using<00:15:19.850> the 00:15:20.050 --> 00:15:20.060 align:start position:0% start out with tokens to start using the 00:15:20.060 --> 00:15:21.699 align:start position:0% start out with tokens to start using the chain<00:15:20.329> ether<00:15:21.110> MIT<00:15:21.230> will<00:15:21.350> be<00:15:21.440> a<00:15:21.470> sovereign 00:15:21.699 --> 00:15:21.709 align:start position:0% chain ether MIT will be a sovereign 00:15:21.709 --> 00:15:23.829 align:start position:0% chain ether MIT will be a sovereign chain<00:15:22.130> having<00:15:22.940> photons<00:15:23.329> you<00:15:23.510> don't<00:15:23.690> need 00:15:23.829 --> 00:15:23.839 align:start position:0% chain having photons you don't need 00:15:23.839 --> 00:15:25.240 align:start position:0% chain having photons you don't need anything<00:15:24.050> other<00:15:24.260> than<00:15:24.410> photons<00:15:24.769> in<00:15:24.980> order<00:15:25.130> to 00:15:25.240 --> 00:15:25.250 align:start position:0% anything other than photons in order to 00:15:25.250 --> 00:15:27.280 align:start position:0% anything other than photons in order to use<00:15:25.339> ether<00:15:25.610> meant<00:15:25.790> it<00:15:26.360> will<00:15:26.510> also<00:15:26.690> have<00:15:27.019> the 00:15:27.280 --> 00:15:27.290 align:start position:0% use ether meant it will also have the 00:15:27.290 --> 00:15:29.139 align:start position:0% use ether meant it will also have the governance<00:15:27.709> staking<00:15:28.160> and<00:15:28.370> sashing<00:15:28.790> modules 00:15:29.139 --> 00:15:29.149 align:start position:0% governance staking and sashing modules 00:15:29.149 --> 00:15:30.869 align:start position:0% governance staking and sashing modules from<00:15:29.240> the<00:15:29.329> cosmos<00:15:29.690> SDK 00:15:30.869 --> 00:15:30.879 align:start position:0% from the cosmos SDK 00:15:30.879 --> 00:15:33.779 align:start position:0% from the cosmos SDK using<00:15:31.689> tenement<00:15:32.079> consensus<00:15:32.559> it<00:15:33.519> will<00:15:33.669> be 00:15:33.779 --> 00:15:33.789 align:start position:0% using tenement consensus it will be 00:15:33.789 --> 00:15:36.059 align:start position:0% using tenement consensus it will be fully<00:15:34.059> web<00:15:34.419> 3<00:15:34.689> compatible<00:15:35.319> so<00:15:35.559> you<00:15:35.649> can<00:15:35.829> use 00:15:36.059 --> 00:15:36.069 align:start position:0% fully web 3 compatible so you can use 00:15:36.069 --> 00:15:38.309 align:start position:0% fully web 3 compatible so you can use truffle<00:15:36.759> metamath<00:15:37.389> solidity<00:15:37.839> all<00:15:38.139> your 00:15:38.309 --> 00:15:38.319 align:start position:0% truffle metamath solidity all your 00:15:38.319 --> 00:15:39.929 align:start position:0% truffle metamath solidity all your existing<00:15:38.739> tooling<00:15:39.129> you<00:15:39.309> know<00:15:39.429> change<00:15:39.699> a 00:15:39.929 --> 00:15:39.939 align:start position:0% existing tooling you know change a 00:15:39.939 --> 00:15:41.939 align:start position:0% existing tooling you know change a drop-down<00:15:40.660> slider<00:15:40.899> and<00:15:41.259> madam<00:15:41.499> asked<00:15:41.649> can 00:15:41.939 --> 00:15:41.949 align:start position:0% drop-down slider and madam asked can 00:15:41.949 --> 00:15:44.159 align:start position:0% drop-down slider and madam asked can connect<00:15:42.160> to<00:15:42.279> ether<00:15:42.519> mint<00:15:42.699> instead<00:15:43.059> and<00:15:43.600> it 00:15:44.159 --> 00:15:44.169 align:start position:0% connect to ether mint instead and it 00:15:44.169 --> 00:15:46.019 align:start position:0% connect to ether mint instead and it will<00:15:44.259> have<00:15:44.379> IBC<00:15:44.889> connections<00:15:45.369> to<00:15:45.579> the<00:15:45.669> cosmos 00:15:46.019 --> 00:15:46.029 align:start position:0% will have IBC connections to the cosmos 00:15:46.029 --> 00:15:47.999 align:start position:0% will have IBC connections to the cosmos hub<00:15:46.269> into<00:15:46.629> future<00:15:46.959> zones<00:15:47.229> which<00:15:47.589> will<00:15:47.739> inhabit 00:15:47.999 --> 00:15:48.009 align:start position:0% hub into future zones which will inhabit 00:15:48.009 --> 00:15:53.099 align:start position:0% hub into future zones which will inhabit the<00:15:48.309> cosmos<00:15:48.609> network<00:15:51.059> the<00:15:52.059> VM<00:15:52.329> module<00:15:52.600> for<00:15:52.720> sdk 00:15:53.099 --> 00:15:53.109 align:start position:0% the cosmos network the VM module for sdk 00:15:53.109 --> 00:15:55.169 align:start position:0% the cosmos network the VM module for sdk zones<00:15:53.379> provides<00:15:54.039> different<00:15:54.429> trade-offs<00:15:54.879> so 00:15:55.169 --> 00:15:55.179 align:start position:0% zones provides different trade-offs so 00:15:55.179 --> 00:15:57.840 align:start position:0% zones provides different trade-offs so in<00:15:55.989> this<00:15:56.139> case<00:15:56.350> you<00:15:56.709> could<00:15:56.889> elect<00:15:57.369> to<00:15:57.429> deploy<00:15:57.819> a 00:15:57.840 --> 00:15:57.850 align:start position:0% in this case you could elect to deploy a 00:15:57.850 --> 00:16:00.779 align:start position:0% in this case you could elect to deploy a cosmos<00:15:58.389> chain<00:15:58.660> which<00:15:58.989> includes<00:15:59.549> some<00:16:00.549> of<00:16:00.609> our 00:16:00.779 --> 00:16:00.789 align:start position:0% cosmos chain which includes some of our 00:16:00.789 --> 00:16:02.249 align:start position:0% cosmos chain which includes some of our base<00:16:00.999> modules<00:16:01.479> and<00:16:01.689> some<00:16:01.839> modules<00:16:02.139> of<00:16:02.229> your 00:16:02.249 --> 00:16:02.259 align:start position:0% base modules and some modules of your 00:16:02.259 --> 00:16:05.819 align:start position:0% base modules and some modules of your own<00:16:02.379> and<00:16:03.129> also<00:16:03.549> an<00:16:03.819> EVO<00:16:04.089> module<00:16:04.679> you<00:16:05.679> could 00:16:05.819 --> 00:16:05.829 align:start position:0% own and also an EVO module you could 00:16:05.829 --> 00:16:07.859 align:start position:0% own and also an EVO module you could even<00:16:06.189> add<00:16:06.429> our<00:16:06.639> web<00:16:06.819> 3<00:16:07.059> interface<00:16:07.419> if<00:16:07.569> you<00:16:07.689> want 00:16:07.859 --> 00:16:07.869 align:start position:0% even add our web 3 interface if you want 00:16:07.869 --> 00:16:09.689 align:start position:0% even add our web 3 interface if you want this<00:16:08.439> means<00:16:08.709> you<00:16:08.919> can<00:16:09.069> utilize<00:16:09.220> existing 00:16:09.689 --> 00:16:09.699 align:start position:0% this means you can utilize existing 00:16:09.699 --> 00:16:11.849 align:start position:0% this means you can utilize existing solidity<00:16:10.329> contracts<00:16:10.839> as<00:16:11.049> part<00:16:11.289> of<00:16:11.410> the<00:16:11.499> logic 00:16:11.849 --> 00:16:11.859 align:start position:0% solidity contracts as part of the logic 00:16:11.859 --> 00:16:12.960 align:start position:0% solidity contracts as part of the logic on<00:16:11.979> your<00:16:12.160> new<00:16:12.279> application-specific 00:16:12.960 --> 00:16:12.970 align:start position:0% on your new application-specific 00:16:12.970 --> 00:16:15.539 align:start position:0% on your new application-specific blockchain<00:16:13.660> and<00:16:13.899> it<00:16:14.709> means<00:16:14.859> that<00:16:15.309> if<00:16:15.429> you're 00:16:15.539 --> 00:16:15.549 align:start position:0% blockchain and it means that if you're 00:16:15.549 --> 00:16:17.009 align:start position:0% blockchain and it means that if you're trying<00:16:15.699> to<00:16:15.789> port<00:16:16.059> an<00:16:16.149> application<00:16:16.689> which<00:16:16.869> is 00:16:17.009 --> 00:16:17.019 align:start position:0% trying to port an application which is 00:16:17.019 --> 00:16:19.679 align:start position:0% trying to port an application which is previously<00:16:17.319> targeted<00:16:18.009> towards<00:16:18.279> the<00:16:18.339> EVM<00:16:18.729> to 00:16:19.679 --> 00:16:19.689 align:start position:0% previously targeted towards the EVM to 00:16:19.689 --> 00:16:21.629 align:start position:0% previously targeted towards the EVM to an<00:16:19.989> application<00:16:20.379> specific<00:16:20.619> blockchain<00:16:21.399> you 00:16:21.629 --> 00:16:21.639 align:start position:0% an application specific blockchain you 00:16:21.639 --> 00:16:23.789 align:start position:0% an application specific blockchain you can<00:16:21.789> do<00:16:21.939> it<00:16:22.089> gradually<00:16:22.449> you<00:16:23.169> can<00:16:23.350> start<00:16:23.649> out 00:16:23.789 --> 00:16:23.799 align:start position:0% can do it gradually you can start out 00:16:23.799 --> 00:16:26.609 align:start position:0% can do it gradually you can start out with<00:16:24.189> your<00:16:24.879> solidity<00:16:25.419> code<00:16:25.749> perhaps<00:16:26.169> deployed 00:16:26.609 --> 00:16:26.619 align:start position:0% with your solidity code perhaps deployed 00:16:26.619 --> 00:16:29.129 align:start position:0% with your solidity code perhaps deployed to<00:16:26.829> an<00:16:26.919> EVM<00:16:27.249> module<00:16:27.699> and<00:16:27.879> you<00:16:28.269> can<00:16:28.419> replace<00:16:28.809> the 00:16:29.129 --> 00:16:29.139 align:start position:0% to an EVM module and you can replace the 00:16:29.139 --> 00:16:30.809 align:start position:0% to an EVM module and you can replace the performance<00:16:29.679> critical<00:16:30.100> parts<00:16:30.339> of<00:16:30.429> that<00:16:30.549> code 00:16:30.809 --> 00:16:30.819 align:start position:0% performance critical parts of that code 00:16:30.819 --> 00:16:33.479 align:start position:0% performance critical parts of that code one<00:16:31.149> at<00:16:31.269> a<00:16:31.359> time<00:16:31.569> out<00:16:32.109> with<00:16:32.350> native<00:16:32.679> code<00:16:32.709> maybe 00:16:33.479 --> 00:16:33.489 align:start position:0% one at a time out with native code maybe 00:16:33.489 --> 00:16:37.710 align:start position:0% one at a time out with native code maybe all<00:16:33.729> the<00:16:33.850> way<00:16:33.939> maybe<00:16:34.239> not<00:16:36.239> but<00:16:37.239> we<00:16:37.389> come<00:16:37.569> to<00:16:37.689> a 00:16:37.710 --> 00:16:37.720 align:start position:0% all the way maybe not but we come to a 00:16:37.720 --> 00:16:40.559 align:start position:0% all the way maybe not but we come to a problem<00:16:38.019> what<00:16:38.949> if<00:16:39.039> we<00:16:39.189> do<00:16:39.339> that<00:16:39.549> you<00:16:40.239> launch<00:16:40.479> a 00:16:40.559 --> 00:16:40.569 align:start position:0% problem what if we do that you launch a 00:16:40.569 --> 00:16:42.329 align:start position:0% problem what if we do that you launch a new<00:16:40.659> application<00:16:41.019> specific<00:16:41.559> blockchain<00:16:42.009> but 00:16:42.329 --> 00:16:42.339 align:start position:0% new application specific blockchain but 00:16:42.339 --> 00:16:44.939 align:start position:0% new application specific blockchain but now<00:16:42.489> your<00:16:43.089> users<00:16:43.419> are<00:16:43.569> split<00:16:43.839> or<00:16:44.350> your 00:16:44.939 --> 00:16:44.949 align:start position:0% now your users are split or your 00:16:44.949 --> 00:16:46.559 align:start position:0% now your users are split or your potential<00:16:45.369> users<00:16:45.489> are<00:16:45.819> split<00:16:46.029> some<00:16:46.299> people 00:16:46.559 --> 00:16:46.569 align:start position:0% potential users are split some people 00:16:46.569 --> 00:16:47.999 align:start position:0% potential users are split some people are<00:16:46.689> on<00:16:46.809> a<00:16:46.839> theorem<00:16:47.289> they<00:16:47.409> have<00:16:47.529> state<00:16:47.769> on 00:16:47.999 --> 00:16:48.009 align:start position:0% are on a theorem they have state on 00:16:48.009 --> 00:16:49.889 align:start position:0% are on a theorem they have state on ethereum<00:16:48.279> tokens<00:16:48.939> collect<00:16:49.449> crypto 00:16:49.889 --> 00:16:49.899 align:start position:0% ethereum tokens collect crypto 00:16:49.899 --> 00:16:51.989 align:start position:0% ethereum tokens collect crypto collectibles<00:16:50.470> and<00:16:50.709> some<00:16:51.369> people<00:16:51.639> want<00:16:51.909> to 00:16:51.989 --> 00:16:51.999 align:start position:0% collectibles and some people want to 00:16:51.999 --> 00:16:54.239 align:start position:0% collectibles and some people want to start<00:16:52.179> using<00:16:52.329> the<00:16:52.539> new<00:16:52.569> ether<00:16:52.899> and<00:16:53.079> chain<00:16:53.259> we 00:16:54.239 --> 00:16:54.249 align:start position:0% start using the new ether and chain we 00:16:54.249 --> 00:16:57.719 align:start position:0% start using the new ether and chain we need<00:16:54.399> a<00:16:54.429> way<00:16:54.609> to<00:16:54.639> connect<00:16:55.269> them<00:16:56.369> we<00:16:57.369> need<00:16:57.489> a<00:16:57.519> way 00:16:57.719 --> 00:16:57.729 align:start position:0% need a way to connect them we need a way 00:16:57.729 --> 00:17:00.539 align:start position:0% need a way to connect them we need a way to<00:16:57.789> transfer<00:16:58.449> state<00:16:58.839> and<00:16:59.199> assets<00:16:59.649> in<00:16:59.979> a 00:17:00.539 --> 00:17:00.549 align:start position:0% to transfer state and assets in a 00:17:00.549 --> 00:17:02.819 align:start position:0% to transfer state and assets in a two-way<00:17:01.059> bridge<00:17:01.389> where<00:17:01.929> it's<00:17:02.139> possible<00:17:02.649> both 00:17:02.819 --> 00:17:02.829 align:start position:0% two-way bridge where it's possible both 00:17:02.829 --> 00:17:05.610 align:start position:0% two-way bridge where it's possible both to<00:17:03.279> deposit<00:17:03.729> if<00:17:04.209> you<00:17:04.329> will<00:17:04.509> from<00:17:04.809> aetherium<00:17:05.409> on 00:17:05.610 --> 00:17:05.620 align:start position:0% to deposit if you will from aetherium on 00:17:05.620 --> 00:17:07.710 align:start position:0% to deposit if you will from aetherium on to<00:17:05.769> ether<00:17:06.039> mint<00:17:06.220> or<00:17:06.730> on<00:17:06.879> to<00:17:07.029> a<00:17:07.059> sovereign<00:17:07.329> zone 00:17:07.710 --> 00:17:07.720 align:start position:0% to ether mint or on to a sovereign zone 00:17:07.720 --> 00:17:10.110 align:start position:0% to ether mint or on to a sovereign zone with<00:17:07.959> the<00:17:07.990> via<00:17:08.289> module<00:17:08.709> and<00:17:08.889> to<00:17:09.129> withdraw<00:17:09.279> from 00:17:10.110 --> 00:17:10.120 align:start position:0% with the via module and to withdraw from 00:17:10.120 --> 00:17:11.879 align:start position:0% with the via module and to withdraw from the<00:17:10.299> sovereign<00:17:10.480> zone<00:17:10.870> back<00:17:11.199> to<00:17:11.379> the<00:17:11.470> etherium 00:17:11.879 --> 00:17:11.889 align:start position:0% the sovereign zone back to the etherium 00:17:11.889 --> 00:17:14.549 align:start position:0% the sovereign zone back to the etherium main<00:17:12.100> chain<00:17:12.360> then<00:17:13.360> you<00:17:13.389> can<00:17:13.750> select<00:17:14.230> which 00:17:14.549 --> 00:17:14.559 align:start position:0% main chain then you can select which 00:17:14.559 --> 00:17:16.919 align:start position:0% main chain then you can select which parts<00:17:14.860> of<00:17:14.919> your<00:17:15.069> logic<00:17:15.429> are<00:17:15.579> most<00:17:15.819> improved<00:17:16.299> by 00:17:16.919 --> 00:17:16.929 align:start position:0% parts of your logic are most improved by 00:17:16.929 --> 00:17:18.329 align:start position:0% parts of your logic are most improved by the<00:17:16.990> new<00:17:17.169> features<00:17:17.529> of<00:17:17.559> ten<00:17:17.829> Dermott's<00:17:18.100> in<00:17:18.189> the 00:17:18.329 --> 00:17:18.339 align:start position:0% the new features of ten Dermott's in the 00:17:18.339 --> 00:17:20.610 align:start position:0% the new features of ten Dermott's in the sdk<00:17:18.759> and<00:17:19.269> put<00:17:19.449> those<00:17:19.629> on<00:17:19.929> ether<00:17:20.230> mentor<00:17:20.470> put 00:17:20.610 --> 00:17:20.620 align:start position:0% sdk and put those on ether mentor put 00:17:20.620 --> 00:17:22.379 align:start position:0% sdk and put those on ether mentor put those<00:17:20.740> on<00:17:20.980> the<00:17:21.069> sovereign<00:17:21.399> chain<00:17:21.639> and<00:17:22.089> allow 00:17:22.379 --> 00:17:22.389 align:start position:0% those on the sovereign chain and allow 00:17:22.389 --> 00:17:24.509 align:start position:0% those on the sovereign chain and allow you<00:17:22.449> users<00:17:22.929> to<00:17:23.110> retain<00:17:23.439> assets<00:17:24.069> or<00:17:24.220> wallet 00:17:24.509 --> 00:17:24.519 align:start position:0% you users to retain assets or wallet 00:17:24.519 --> 00:17:26.159 align:start position:0% you users to retain assets or wallet balances<00:17:25.029> at<00:17:25.269> least<00:17:25.419> for<00:17:25.569> a<00:17:25.600> little<00:17:25.809> while<00:17:25.929> on 00:17:26.159 --> 00:17:26.169 align:start position:0% balances at least for a little while on 00:17:26.169 --> 00:17:29.879 align:start position:0% balances at least for a little while on theorem<00:17:27.329> how<00:17:28.329> do<00:17:28.389> we<00:17:28.539> do<00:17:28.690> this<00:17:28.889> we've 00:17:29.879 --> 00:17:29.889 align:start position:0% theorem how do we do this we've 00:17:29.889 --> 00:17:32.909 align:start position:0% theorem how do we do this we've developed<00:17:30.429> at<00:17:31.419> cosmos<00:17:31.990> a<00:17:32.230> technology<00:17:32.769> called 00:17:32.909 --> 00:17:32.919 align:start position:0% developed at cosmos a technology called 00:17:32.919 --> 00:17:34.440 align:start position:0% developed at cosmos a technology called inter<00:17:33.190> blockchain<00:17:33.610> communication<00:17:34.240> which 00:17:34.440 --> 00:17:34.450 align:start position:0% inter blockchain communication which 00:17:34.450 --> 00:17:36.119 align:start position:0% inter blockchain communication which allows<00:17:34.720> for<00:17:34.929> this<00:17:35.049> kind<00:17:35.259> of<00:17:35.320> generic<00:17:35.649> two-way 00:17:36.119 --> 00:17:36.129 align:start position:0% allows for this kind of generic two-way 00:17:36.129 --> 00:17:39.029 align:start position:0% allows for this kind of generic two-way bridge<00:17:36.419> in<00:17:37.419> order<00:17:37.600> to<00:17:37.929> bridge<00:17:38.259> ether<00:17:38.769> mint<00:17:38.919> to 00:17:39.029 --> 00:17:39.039 align:start position:0% bridge in order to bridge ether mint to 00:17:39.039 --> 00:17:41.519 align:start position:0% bridge in order to bridge ether mint to aetherium<00:17:39.399> we<00:17:39.789> need<00:17:39.940> to<00:17:40.269> separate<00:17:41.019> IBC 00:17:41.519 --> 00:17:41.529 align:start position:0% aetherium we need to separate IBC 00:17:41.529 --> 00:17:44.020 align:start position:0% aetherium we need to separate IBC connections<00:17:42.010> we<00:17:42.549> need<00:17:42.730> one<00:17:42.909> IBC<00:17:43.299> connection 00:17:44.020 --> 00:17:44.030 align:start position:0% connections we need one IBC connection 00:17:44.030 --> 00:17:46.300 align:start position:0% connections we need one IBC connection a<00:17:44.270> Thurmond<00:17:44.600> and<00:17:44.810> the<00:17:44.870> Kosmos<00:17:45.260> hub<00:17:45.500> which<00:17:46.130> is<00:17:46.280> a 00:17:46.300 --> 00:17:46.310 align:start position:0% a Thurmond and the Kosmos hub which is a 00:17:46.310 --> 00:17:48.130 align:start position:0% a Thurmond and the Kosmos hub which is a blockchain<00:17:46.580> that<00:17:46.940> we're<00:17:47.060> launching<00:17:47.240> soon<00:17:47.900> and 00:17:48.130 --> 00:17:48.140 align:start position:0% blockchain that we're launching soon and 00:17:48.140 --> 00:17:50.380 align:start position:0% blockchain that we're launching soon and we<00:17:48.770> need<00:17:48.800> another<00:17:49.070> IVC<00:17:49.670> connection<00:17:50.120> between 00:17:50.380 --> 00:17:50.390 align:start position:0% we need another IVC connection between 00:17:50.390 --> 00:17:52.960 align:start position:0% we need another IVC connection between the<00:17:50.630> cosmos<00:17:50.990> hub<00:17:51.170> and<00:17:51.440> etherium<00:17:51.890> then<00:17:52.490> tokens 00:17:52.960 --> 00:17:52.970 align:start position:0% the cosmos hub and etherium then tokens 00:17:52.970 --> 00:17:54.940 align:start position:0% the cosmos hub and etherium then tokens can<00:17:53.180> flow<00:17:53.480> through<00:17:53.810> those<00:17:54.110> two<00:17:54.410> connections 00:17:54.940 --> 00:17:54.950 align:start position:0% can flow through those two connections 00:17:54.950 --> 00:17:57.160 align:start position:0% can flow through those two connections so<00:17:55.490> someone<00:17:55.820> can<00:17:55.970> deposit<00:17:56.450> from<00:17:56.600> aetherium 00:17:57.160 --> 00:17:57.170 align:start position:0% so someone can deposit from aetherium 00:17:57.170 --> 00:17:59.800 align:start position:0% so someone can deposit from aetherium some<00:17:57.680> ether<00:17:57.890> that<00:17:58.250> ether<00:17:59.000> will<00:17:59.150> head<00:17:59.330> over<00:17:59.360> the 00:17:59.800 --> 00:17:59.810 align:start position:0% some ether that ether will head over the 00:17:59.810 --> 00:18:01.810 align:start position:0% some ether that ether will head over the IVC<00:18:00.230> connection<00:18:00.740> to<00:18:00.860> the<00:18:00.950> cosmos<00:18:01.340> hub<00:18:01.520> and 00:18:01.810 --> 00:18:01.820 align:start position:0% IVC connection to the cosmos hub and 00:18:01.820 --> 00:18:03.310 align:start position:0% IVC connection to the cosmos hub and then<00:18:02.240> it<00:18:02.360> will<00:18:02.450> be<00:18:02.540> bounced<00:18:02.930> on<00:18:03.050> from<00:18:03.260> the 00:18:03.310 --> 00:18:03.320 align:start position:0% then it will be bounced on from the 00:18:03.320 --> 00:18:05.020 align:start position:0% then it will be bounced on from the cosmos<00:18:03.680> hub<00:18:03.860> to<00:18:04.040> ether<00:18:04.280> mint<00:18:04.490> where<00:18:04.700> it<00:18:04.760> can<00:18:04.910> be 00:18:05.020 --> 00:18:05.030 align:start position:0% cosmos hub to ether mint where it can be 00:18:05.030 --> 00:18:07.630 align:start position:0% cosmos hub to ether mint where it can be used<00:18:05.270> in<00:18:05.600> smart<00:18:06.380> contracts<00:18:06.830> operating<00:18:07.460> on<00:18:07.550> the 00:18:07.630 --> 00:18:07.640 align:start position:0% used in smart contracts operating on the 00:18:07.640 --> 00:18:11.250 align:start position:0% used in smart contracts operating on the EVM<00:18:07.940> module<00:18:08.360> Ani<00:18:08.600> Thurmond 00:18:11.250 --> 00:18:11.260 align:start position:0% 00:18:11.260 --> 00:18:15.190 align:start position:0% what<00:18:12.260> is<00:18:12.380> this<00:18:12.470> IPC<00:18:12.950> bridge<00:18:13.160> allow<00:18:13.520> for<00:18:14.200> the 00:18:15.190 --> 00:18:15.200 align:start position:0% what is this IPC bridge allow for the 00:18:15.200 --> 00:18:17.470 align:start position:0% what is this IPC bridge allow for the answer<00:18:15.410> is<00:18:15.500> pretty<00:18:15.710> much<00:18:15.860> anything<00:18:16.450> IBC<00:18:17.450> is 00:18:17.470 --> 00:18:17.480 align:start position:0% answer is pretty much anything IBC is 00:18:17.480 --> 00:18:19.570 align:start position:0% answer is pretty much anything IBC is payload<00:18:17.900> agnostic<00:18:18.530> so<00:18:19.010> it<00:18:19.280> will<00:18:19.370> take<00:18:19.520> some 00:18:19.570 --> 00:18:19.580 align:start position:0% payload agnostic so it will take some 00:18:19.580 --> 00:18:21.610 align:start position:0% payload agnostic so it will take some byte<00:18:19.910> string<00:18:20.270> from<00:18:20.630> these<00:18:20.810> two<00:18:21.050> chip<00:18:21.230> from<00:18:21.470> one 00:18:21.610 --> 00:18:21.620 align:start position:0% byte string from these two chip from one 00:18:21.620 --> 00:18:23.620 align:start position:0% byte string from these two chip from one chain<00:18:21.860> to<00:18:22.040> another<00:18:22.280> or<00:18:22.550> from<00:18:22.580> two<00:18:22.970> across<00:18:23.480> two 00:18:23.620 --> 00:18:23.630 align:start position:0% chain to another or from two across two 00:18:23.630 --> 00:18:26.290 align:start position:0% chain to another or from two across two bridges<00:18:24.020> from<00:18:24.530> etherion<00:18:25.070> to<00:18:25.190> Thurmond<00:18:25.610> then 00:18:26.290 --> 00:18:26.300 align:start position:0% bridges from etherion to Thurmond then 00:18:26.300 --> 00:18:28.870 align:start position:0% bridges from etherion to Thurmond then IBC<00:18:26.960> modules<00:18:27.380> on<00:18:27.830> etherium<00:18:28.460> and<00:18:28.610> on<00:18:28.700> a 00:18:28.870 --> 00:18:28.880 align:start position:0% IBC modules on etherium and on a 00:18:28.880 --> 00:18:30.880 align:start position:0% IBC modules on etherium and on a Thurmond<00:18:29.210> will<00:18:29.360> expose<00:18:29.780> this<00:18:30.170> primitive<00:18:30.440> to 00:18:30.880 --> 00:18:30.890 align:start position:0% Thurmond will expose this primitive to 00:18:30.890 --> 00:18:32.710 align:start position:0% Thurmond will expose this primitive to contracts<00:18:31.340> so<00:18:32.060> that<00:18:32.330> you<00:18:32.420> can<00:18:32.570> write 00:18:32.710 --> 00:18:32.720 align:start position:0% contracts so that you can write 00:18:32.720 --> 00:18:34.750 align:start position:0% contracts so that you can write contracts<00:18:33.260> which<00:18:33.530> transfer<00:18:34.010> tokens<00:18:34.430> which 00:18:34.750 --> 00:18:34.760 align:start position:0% contracts which transfer tokens which 00:18:34.760 --> 00:18:36.820 align:start position:0% contracts which transfer tokens which transfer<00:18:35.150> assets<00:18:35.570> which<00:18:36.320> do<00:18:36.500> much<00:18:36.680> more 00:18:36.820 --> 00:18:36.830 align:start position:0% transfer assets which do much more 00:18:36.830 --> 00:18:38.650 align:start position:0% transfer assets which do much more complicated<00:18:37.100> thing<00:18:37.550> is<00:18:37.700> like<00:18:37.880> execute<00:18:38.420> cross 00:18:38.650 --> 00:18:38.660 align:start position:0% complicated thing is like execute cross 00:18:38.660 --> 00:18:40.900 align:start position:0% complicated thing is like execute cross chain<00:18:38.930> dependent<00:18:39.470> smart<00:18:39.710> contract<00:18:40.100> logic<00:18:40.460> or 00:18:40.900 --> 00:18:40.910 align:start position:0% chain dependent smart contract logic or 00:18:40.910 --> 00:18:44.590 align:start position:0% chain dependent smart contract logic or move<00:18:41.120> code<00:18:41.390> between<00:18:41.660> chains<00:18:43.360> hopefully<00:18:44.360> this 00:18:44.590 --> 00:18:44.600 align:start position:0% move code between chains hopefully this 00:18:44.600 --> 00:18:46.630 align:start position:0% move code between chains hopefully this will<00:18:44.720> allow<00:18:44.960> adapts<00:18:45.320> to<00:18:45.620> put<00:18:45.830> parts<00:18:46.250> of<00:18:46.460> their 00:18:46.630 --> 00:18:46.640 align:start position:0% will allow adapts to put parts of their 00:18:46.640 --> 00:18:49.240 align:start position:0% will allow adapts to put parts of their logic<00:18:47.210> that<00:18:47.360> are<00:18:47.480> most<00:18:47.750> fee<00:18:48.440> sensitive<00:18:48.950> or 00:18:49.240 --> 00:18:49.250 align:start position:0% logic that are most fee sensitive or 00:18:49.250 --> 00:18:51.820 align:start position:0% logic that are most fee sensitive or most<00:18:49.570> time-sensitive<00:18:50.570> and<00:18:51.080> execution<00:18:51.590> speed 00:18:51.820 --> 00:18:51.830 align:start position:0% most time-sensitive and execution speed 00:18:51.830 --> 00:18:54.280 align:start position:0% most time-sensitive and execution speed on<00:18:52.040> a<00:18:52.640> Thurmond<00:18:53.030> and<00:18:53.240> leave<00:18:53.600> some<00:18:53.810> parts<00:18:54.110> on 00:18:54.280 --> 00:18:54.290 align:start position:0% on a Thurmond and leave some parts on 00:18:54.290 --> 00:18:55.980 align:start position:0% on a Thurmond and leave some parts on aetherium 00:18:55.980 --> 00:18:55.990 align:start position:0% aetherium 00:18:55.990 --> 00:18:58.930 align:start position:0% aetherium for<00:18:56.990> existing<00:18:57.380> DOPS<00:18:57.620> we<00:18:58.160> think<00:18:58.400> like<00:18:58.640> I<00:18:58.760> said 00:18:58.930 --> 00:18:58.940 align:start position:0% for existing DOPS we think like I said 00:18:58.940 --> 00:19:00.760 align:start position:0% for existing DOPS we think like I said this<00:18:59.180> is<00:18:59.330> super<00:18:59.540> compelling<00:18:59.810> you<00:19:00.500> can<00:19:00.620> move 00:19:00.760 --> 00:19:00.770 align:start position:0% this is super compelling you can move 00:19:00.770 --> 00:19:02.260 align:start position:0% this is super compelling you can move parts<00:19:01.010> of<00:19:01.100> your<00:19:01.190> contract<00:19:01.520> logic<00:19:01.790> overtime 00:19:02.260 --> 00:19:02.270 align:start position:0% parts of your contract logic overtime 00:19:02.270 --> 00:19:04.570 align:start position:0% parts of your contract logic overtime when<00:19:03.080> you<00:19:03.350> need<00:19:03.560> to<00:19:03.650> execute<00:19:03.950> an<00:19:04.160> expensive 00:19:04.570 --> 00:19:04.580 align:start position:0% when you need to execute an expensive 00:19:04.580 --> 00:19:05.950 align:start position:0% when you need to execute an expensive transaction<00:19:05.090> you<00:19:05.270> shift<00:19:05.480> over<00:19:05.660> to<00:19:05.870> either 00:19:05.950 --> 00:19:05.960 align:start position:0% transaction you shift over to either 00:19:05.960 --> 00:19:08.890 align:start position:0% transaction you shift over to either mint<00:19:06.290> and<00:19:06.530> the<00:19:07.430> ux4<00:19:07.970> users<00:19:08.270> can<00:19:08.480> be<00:19:08.630> pretty 00:19:08.890 --> 00:19:08.900 align:start position:0% mint and the ux4 users can be pretty 00:19:08.900 --> 00:19:10.870 align:start position:0% mint and the ux4 users can be pretty seamless<00:19:09.380> abstracted<00:19:10.040> over<00:19:10.310> and<00:19:10.550> all<00:19:10.640> the<00:19:10.760> web 00:19:10.870 --> 00:19:10.880 align:start position:0% seamless abstracted over and all the web 00:19:10.880 --> 00:19:16.710 align:start position:0% seamless abstracted over and all the web 3<00:19:11.090> tooling<00:19:11.450> a<00:19:13.630> particular<00:19:14.630> example<00:19:15.220> would<00:19:16.220> be 00:19:16.710 --> 00:19:16.720 align:start position:0% 3 tooling a particular example would be 00:19:16.720 --> 00:19:19.570 align:start position:0% 3 tooling a particular example would be porting<00:19:17.720> a<00:19:17.780> Dex<00:19:18.110> porting<00:19:18.950> a<00:19:19.040> decentralized 00:19:19.570 --> 00:19:19.580 align:start position:0% porting a Dex porting a decentralized 00:19:19.580 --> 00:19:21.910 align:start position:0% porting a Dex porting a decentralized exchange<00:19:19.990> protocol<00:19:20.990> like<00:19:21.110> Xerox<00:19:21.350> or<00:19:21.560> wyvern 00:19:21.910 --> 00:19:21.920 align:start position:0% exchange protocol like Xerox or wyvern 00:19:21.920 --> 00:19:24.970 align:start position:0% exchange protocol like Xerox or wyvern to<00:19:22.550> an<00:19:22.850> ether<00:19:23.150> mint<00:19:23.330> zone<00:19:23.690> so<00:19:24.320> you<00:19:24.380> could<00:19:24.650> copy 00:19:24.970 --> 00:19:24.980 align:start position:0% to an ether mint zone so you could copy 00:19:24.980 --> 00:19:27.670 align:start position:0% to an ether mint zone so you could copy the<00:19:25.280> protocol<00:19:25.760> contracts<00:19:26.240> on<00:19:26.600> to<00:19:27.110> e<00:19:27.140> thurmond 00:19:27.670 --> 00:19:27.680 align:start position:0% the protocol contracts on to e thurmond 00:19:27.680 --> 00:19:30.040 align:start position:0% the protocol contracts on to e thurmond deploy<00:19:27.950> them<00:19:28.160> to<00:19:28.190> the<00:19:28.370> Evo<00:19:28.610> module<00:19:29.090> get<00:19:29.930> them 00:19:30.040 --> 00:19:30.050 align:start position:0% deploy them to the Evo module get them 00:19:30.050 --> 00:19:32.110 align:start position:0% deploy them to the Evo module get them running<00:19:30.170> then<00:19:30.800> allow<00:19:31.160> users<00:19:31.640> to<00:19:31.670> deposit 00:19:32.110 --> 00:19:32.120 align:start position:0% running then allow users to deposit 00:19:32.120 --> 00:19:35.350 align:start position:0% running then allow users to deposit tokens<00:19:32.720> over<00:19:33.200> the<00:19:33.320> IBC<00:19:33.770> bridge<00:19:33.980> or<00:19:34.850> even<00:19:35.210> non 00:19:35.350 --> 00:19:35.360 align:start position:0% tokens over the IBC bridge or even non 00:19:35.360 --> 00:19:38.230 align:start position:0% tokens over the IBC bridge or even non fungible<00:19:35.780> x'<00:19:35.840> from<00:19:36.440> aetherium<00:19:37.100> to<00:19:37.460> ether<00:19:37.850> mint 00:19:38.230 --> 00:19:38.240 align:start position:0% fungible x' from aetherium to ether mint 00:19:38.240 --> 00:19:40.180 align:start position:0% fungible x' from aetherium to ether mint once<00:19:38.840> they're<00:19:39.050> deposited<00:19:39.320> to<00:19:39.740> ether<00:19:39.980> mint 00:19:40.180 --> 00:19:40.190 align:start position:0% once they're deposited to ether mint 00:19:40.190 --> 00:19:41.530 align:start position:0% once they're deposited to ether mint they<00:19:40.310> can<00:19:40.460> be<00:19:40.580> used<00:19:40.850> and<00:19:41.060> traded<00:19:41.330> in<00:19:41.450> the 00:19:41.530 --> 00:19:41.540 align:start position:0% they can be used and traded in the 00:19:41.540 --> 00:19:43.150 align:start position:0% they can be used and traded in the stacks<00:19:41.810> and<00:19:42.020> kept<00:19:42.230> there<00:19:42.380> indefinitely<00:19:42.650> if 00:19:43.150 --> 00:19:43.160 align:start position:0% stacks and kept there indefinitely if 00:19:43.160 --> 00:19:45.580 align:start position:0% stacks and kept there indefinitely if you<00:19:43.280> like<00:19:43.490> and<00:19:43.760> if<00:19:44.330> users<00:19:44.660> want<00:19:44.690> or<00:19:45.350> want<00:19:45.530> to 00:19:45.580 --> 00:19:45.590 align:start position:0% you like and if users want or want to 00:19:45.590 --> 00:19:47.590 align:start position:0% you like and if users want or want to have<00:19:45.710> the<00:19:45.860> option<00:19:46.190> to<00:19:46.310> withdraw<00:19:46.430> back<00:19:47.330> to<00:19:47.390> the 00:19:47.590 --> 00:19:47.600 align:start position:0% have the option to withdraw back to the 00:19:47.600 --> 00:19:49.330 align:start position:0% have the option to withdraw back to the ethereum<00:19:47.990> main<00:19:48.170> chain<00:19:48.410> they<00:19:48.620> can<00:19:48.770> do<00:19:48.890> so<00:19:49.070> with 00:19:49.330 --> 00:19:49.340 align:start position:0% ethereum main chain they can do so with 00:19:49.340 --> 00:19:53.950 align:start position:0% ethereum main chain they can do so with no<00:19:49.490> permission<00:19:49.790> on<00:19:50.030> your<00:19:50.180> part<00:19:52.870> you<00:19:53.870> could 00:19:53.950 --> 00:19:53.960 align:start position:0% no permission on your part you could 00:19:53.960 --> 00:19:55.600 align:start position:0% no permission on your part you could also<00:19:54.140> implement<00:19:54.440> it<00:19:54.710> acts<00:19:54.890> as<00:19:55.160> a<00:19:55.220> sovereign 00:19:55.600 --> 00:19:55.610 align:start position:0% also implement it acts as a sovereign 00:19:55.610 --> 00:19:57.790 align:start position:0% also implement it acts as a sovereign zone<00:19:56.000> using<00:19:56.480> the<00:19:56.750> EVM<00:19:57.080> module 00:19:57.790 --> 00:19:57.800 align:start position:0% zone using the EVM module 00:19:57.800 --> 00:19:59.650 align:start position:0% zone using the EVM module with<00:19:58.070> the<00:19:58.190> same<00:19:58.400> initial<00:19:58.970> starting<00:19:59.300> procedure 00:19:59.650 --> 00:19:59.660 align:start position:0% with the same initial starting procedure 00:19:59.660 --> 00:20:03.130 align:start position:0% with the same initial starting procedure of<00:19:59.990> porting<00:20:00.860> the<00:20:01.040> contracts<00:20:01.490> from<00:20:02.210> solidity 00:20:03.130 --> 00:20:03.140 align:start position:0% of porting the contracts from solidity 00:20:03.140 --> 00:20:06.370 align:start position:0% of porting the contracts from solidity and<00:20:04.130> deploying<00:20:04.610> them<00:20:04.940> on<00:20:05.150> to<00:20:05.630> the<00:20:05.720> Evo<00:20:05.960> module 00:20:06.370 --> 00:20:06.380 align:start position:0% and deploying them on to the Evo module 00:20:06.380 --> 00:20:09.970 align:start position:0% and deploying them on to the Evo module on<00:20:06.560> the<00:20:06.650> sovereigns<00:20:07.040> own<00:20:08.140> but<00:20:09.140> then<00:20:09.350> you<00:20:09.770> could 00:20:09.970 --> 00:20:09.980 align:start position:0% on the sovereigns own but then you could 00:20:09.980 --> 00:20:12.550 align:start position:0% on the sovereigns own but then you could add<00:20:10.160> some<00:20:10.430> improvements<00:20:11.180> you<00:20:11.810> first<00:20:12.320> of<00:20:12.470> all 00:20:12.550 --> 00:20:12.560 align:start position:0% add some improvements you first of all 00:20:12.560 --> 00:20:14.530 align:start position:0% add some improvements you first of all you<00:20:12.860> would<00:20:13.310> have<00:20:13.430> no<00:20:13.610> competition<00:20:14.000> for<00:20:14.180> block 00:20:14.530 --> 00:20:14.540 align:start position:0% you would have no competition for block 00:20:14.540 --> 00:20:16.120 align:start position:0% you would have no competition for block space<00:20:14.840> so<00:20:15.140> if<00:20:15.200> you<00:20:15.320> run<00:20:15.440> a<00:20:15.500> sovereign<00:20:15.890> chain 00:20:16.120 --> 00:20:16.130 align:start position:0% space so if you run a sovereign chain 00:20:16.130 --> 00:20:17.230 align:start position:0% space so if you run a sovereign chain for<00:20:16.430> just<00:20:16.610> the<00:20:16.760> Dex 00:20:17.230 --> 00:20:17.240 align:start position:0% for just the Dex 00:20:17.240 --> 00:20:19.210 align:start position:0% for just the Dex only<00:20:17.840> your<00:20:17.990> Dex<00:20:18.200> is<00:20:18.380> transactions<00:20:18.950> would<00:20:19.070> be 00:20:19.210 --> 00:20:19.220 align:start position:0% only your Dex is transactions would be 00:20:19.220 --> 00:20:20.560 align:start position:0% only your Dex is transactions would be settled<00:20:19.550> there<00:20:19.700> you<00:20:19.850> could<00:20:20.000> prevent<00:20:20.300> anyone 00:20:20.560 --> 00:20:20.570 align:start position:0% settled there you could prevent anyone 00:20:20.570 --> 00:20:22.900 align:start position:0% settled there you could prevent anyone else<00:20:20.810> you<00:20:21.470> know<00:20:21.530> any<00:20:21.770> crypto<00:20:22.040> kitties<00:20:22.430> hit<00:20:22.820> of 00:20:22.900 --> 00:20:22.910 align:start position:0% else you know any crypto kitties hit of 00:20:22.910 --> 00:20:25.690 align:start position:0% else you know any crypto kitties hit of the<00:20:23.030> month<00:20:23.380> from<00:20:24.380> crowding<00:20:25.250> out<00:20:25.370> your<00:20:25.520> block 00:20:25.690 --> 00:20:25.700 align:start position:0% the month from crowding out your block 00:20:25.700 --> 00:20:27.610 align:start position:0% the month from crowding out your block space<00:20:25.970> and<00:20:26.210> making<00:20:26.450> it<00:20:26.570> expensive<00:20:27.290> for<00:20:27.500> your 00:20:27.610 --> 00:20:27.620 align:start position:0% space and making it expensive for your 00:20:27.620 --> 00:20:30.310 align:start position:0% space and making it expensive for your users<00:20:27.950> to<00:20:28.070> trade<00:20:28.420> you<00:20:29.420> could<00:20:29.570> also<00:20:29.720> start 00:20:30.310 --> 00:20:30.320 align:start position:0% users to trade you could also start 00:20:30.320 --> 00:20:31.990 align:start position:0% users to trade you could also start pointing<00:20:30.740> parts<00:20:31.040> of<00:20:31.160> the<00:20:31.250> Dex<00:20:31.430> protocol<00:20:31.880> I'll 00:20:31.990 --> 00:20:32.000 align:start position:0% pointing parts of the Dex protocol I'll 00:20:32.000 --> 00:20:34.360 align:start position:0% pointing parts of the Dex protocol I'll probably<00:20:32.240> trade<00:20:32.660> settlement<00:20:33.200> execution<00:20:33.860> the 00:20:34.360 --> 00:20:34.370 align:start position:0% probably trade settlement execution the 00:20:34.370 --> 00:20:36.070 align:start position:0% probably trade settlement execution the super<00:20:34.700> gas<00:20:34.850> expensive<00:20:35.360> parts<00:20:35.630> to<00:20:35.780> native<00:20:36.050> code 00:20:36.070 --> 00:20:36.080 align:start position:0% super gas expensive parts to native code 00:20:36.080 --> 00:20:38.500 align:start position:0% super gas expensive parts to native code as<00:20:36.470> SDK<00:20:36.860> modules<00:20:37.250> which<00:20:37.940> would<00:20:38.120> make<00:20:38.270> it<00:20:38.390> much 00:20:38.500 --> 00:20:38.510 align:start position:0% as SDK modules which would make it much 00:20:38.510 --> 00:20:41.920 align:start position:0% as SDK modules which would make it much cheaper<00:20:39.220> and<00:20:40.220> you<00:20:40.940> could<00:20:41.240> change<00:20:41.510> more 00:20:41.920 --> 00:20:41.930 align:start position:0% cheaper and you could change more 00:20:41.930 --> 00:20:43.630 align:start position:0% cheaper and you could change more complex<00:20:42.470> things<00:20:42.680> you<00:20:42.980> could<00:20:43.130> alter<00:20:43.370> sneaky 00:20:43.630 --> 00:20:43.640 align:start position:0% complex things you could alter sneaky 00:20:43.640 --> 00:20:45.610 align:start position:0% complex things you could alter sneaky mechanics<00:20:44.180> maybe<00:20:44.720> add<00:20:44.960> new<00:20:45.170> slashing 00:20:45.610 --> 00:20:45.620 align:start position:0% mechanics maybe add new slashing 00:20:45.620 --> 00:20:47.110 align:start position:0% mechanics maybe add new slashing conditions<00:20:46.040> to<00:20:46.160> prevent<00:20:46.250> front-running<00:20:46.820> or 00:20:47.110 --> 00:20:47.120 align:start position:0% conditions to prevent front-running or 00:20:47.120 --> 00:20:49.030 align:start position:0% conditions to prevent front-running or implement<00:20:47.630> alter<00:20:48.440> the<00:20:48.530> state<00:20:48.710> machine 00:20:49.030 --> 00:20:49.040 align:start position:0% implement alter the state machine 00:20:49.040 --> 00:20:51.100 align:start position:0% implement alter the state machine implement<00:20:49.520> threshold<00:20:50.300> decryption<00:20:50.750> so<00:20:50.990> that 00:20:51.100 --> 00:20:51.110 align:start position:0% implement threshold decryption so that 00:20:51.110 --> 00:20:53.020 align:start position:0% implement threshold decryption so that transactions<00:20:51.680> are<00:20:51.830> encrypted<00:20:52.370> when<00:20:52.880> they're 00:20:53.020 --> 00:20:53.030 align:start position:0% transactions are encrypted when they're 00:20:53.030 --> 00:20:54.550 align:start position:0% transactions are encrypted when they're submitted<00:20:53.360> to<00:20:53.420> the<00:20:53.540> blockchain<00:20:53.750> and<00:20:54.230> decrypt 00:20:54.550 --> 00:20:54.560 align:start position:0% submitted to the blockchain and decrypt 00:20:54.560 --> 00:20:56.740 align:start position:0% submitted to the blockchain and decrypt it<00:20:54.650> later<00:20:54.860> so<00:20:55.130> no<00:20:55.820> one<00:20:55.940> can<00:20:56.060> front<00:20:56.270> run<00:20:56.450> on<00:20:56.660> the 00:20:56.740 --> 00:20:56.750 align:start position:0% it later so no one can front run on the 00:20:56.750 --> 00:20:58.300 align:start position:0% it later so no one can front run on the Dex<00:20:56.930> all<00:20:57.170> of<00:20:57.290> this<00:20:57.380> is<00:20:57.530> possible<00:20:57.920> if<00:20:58.100> you<00:20:58.190> have 00:20:58.300 --> 00:20:58.310 align:start position:0% Dex all of this is possible if you have 00:20:58.310 --> 00:21:02.440 align:start position:0% Dex all of this is possible if you have a<00:20:58.340> sovereign<00:20:58.580> zone<00:21:00.250> so<00:21:01.250> what's<00:21:02.060> the<00:21:02.210> state<00:21:02.420> of 00:21:02.440 --> 00:21:02.450 align:start position:0% a sovereign zone so what's the state of 00:21:02.450 --> 00:21:03.100 align:start position:0% a sovereign zone so what's the state of all<00:21:02.630> of<00:21:02.750> this 00:21:03.100 --> 00:21:03.110 align:start position:0% all of this 00:21:03.110 --> 00:21:05.680 align:start position:0% all of this ether<00:21:03.920> mint<00:21:04.070> is<00:21:04.220> not<00:21:04.430> vaporware<00:21:05.120> you<00:21:05.270> can<00:21:05.420> find 00:21:05.680 --> 00:21:05.690 align:start position:0% ether mint is not vaporware you can find 00:21:05.690 --> 00:21:07.540 align:start position:0% ether mint is not vaporware you can find it<00:21:05.840> on<00:21:06.020> github<00:21:06.280> development<00:21:07.280> is<00:21:07.370> progressing 00:21:07.540 --> 00:21:07.550 align:start position:0% it on github development is progressing 00:21:07.550 --> 00:21:10.150 align:start position:0% it on github development is progressing exceptionally<00:21:08.420> quickly<00:21:08.660> worked<00:21:09.590> on<00:21:09.740> by<00:21:09.920> bears 00:21:10.150 --> 00:21:10.160 align:start position:0% exceptionally quickly worked on by bears 00:21:10.160 --> 00:21:11.410 align:start position:0% exceptionally quickly worked on by bears who's<00:21:10.430> sitting<00:21:10.670> in<00:21:10.760> the<00:21:10.820> audience<00:21:10.970> and<00:21:11.300> by 00:21:11.410 --> 00:21:11.420 align:start position:0% who's sitting in the audience and by 00:21:11.420 --> 00:21:12.370 align:start position:0% who's sitting in the audience and by Aleksey<00:21:11.780> who<00:21:11.930> will<00:21:12.020> be<00:21:12.080> giving<00:21:12.290> a<00:21:12.350> talk 00:21:12.370 --> 00:21:12.380 align:start position:0% Aleksey who will be giving a talk 00:21:12.380 --> 00:21:15.220 align:start position:0% Aleksey who will be giving a talk tomorrow<00:21:12.940> we're<00:21:13.940> anticipating<00:21:14.210> a<00:21:14.750> Developer 00:21:15.220 --> 00:21:15.230 align:start position:0% tomorrow we're anticipating a Developer 00:21:15.230 --> 00:21:16.780 align:start position:0% tomorrow we're anticipating a Developer Preview<00:21:15.440> release<00:21:16.040> which<00:21:16.400> will<00:21:16.610> have<00:21:16.760> a 00:21:16.780 --> 00:21:16.790 align:start position:0% Preview release which will have a 00:21:16.790 --> 00:21:20.350 align:start position:0% Preview release which will have a functional<00:21:17.480> or<00:21:17.950> 99.9%<00:21:18.950> functional<00:21:19.670> web<00:21:19.820> 3<00:21:20.060> API 00:21:20.350 --> 00:21:20.360 align:start position:0% functional or 99.9% functional web 3 API 00:21:20.360 --> 00:21:23.020 align:start position:0% functional or 99.9% functional web 3 API by<00:21:21.050> the<00:21:21.140> end<00:21:21.380> of<00:21:21.470> q4<00:21:21.890> this<00:21:22.100> year<00:21:22.370> and<00:21:22.550> which 00:21:23.020 --> 00:21:23.030 align:start position:0% by the end of q4 this year and which 00:21:23.030 --> 00:21:24.400 align:start position:0% by the end of q4 this year and which will<00:21:23.210> allow<00:21:23.330> you<00:21:23.390> to<00:21:23.510> deploy<00:21:23.870> solidity 00:21:24.400 --> 00:21:24.410 align:start position:0% will allow you to deploy solidity 00:21:24.410 --> 00:21:26.410 align:start position:0% will allow you to deploy solidity contracts<00:21:24.950> to<00:21:25.250> the<00:21:25.340> EBM<00:21:25.610> module<00:21:26.000> and<00:21:26.240> play 00:21:26.410 --> 00:21:26.420 align:start position:0% contracts to the EBM module and play 00:21:26.420 --> 00:21:29.290 align:start position:0% contracts to the EBM module and play around<00:21:26.570> with<00:21:26.780> either<00:21:26.960> mint<00:21:27.760> and<00:21:28.760> we<00:21:28.910> encourage 00:21:29.290 --> 00:21:29.300 align:start position:0% around with either mint and we encourage 00:21:29.300 --> 00:21:30.550 align:start position:0% around with either mint and we encourage you<00:21:29.330> to<00:21:29.630> check<00:21:29.780> it<00:21:29.930> out<00:21:30.020> send<00:21:30.260> us<00:21:30.410> feedback 00:21:30.550 --> 00:21:30.560 align:start position:0% you to check it out send us feedback 00:21:30.560 --> 00:21:32.590 align:start position:0% you to check it out send us feedback tell<00:21:31.040> us<00:21:31.130> what<00:21:31.280> you<00:21:31.400> would<00:21:31.490> like<00:21:31.670> tell<00:21:32.240> us<00:21:32.270> what 00:21:32.590 --> 00:21:32.600 align:start position:0% tell us what you would like tell us what 00:21:32.600 --> 00:21:34.720 align:start position:0% tell us what you would like tell us what the<00:21:32.780> challenge<00:21:33.350> is<00:21:33.470> facing<00:21:33.920> this<00:21:34.370> kind<00:21:34.610> of 00:21:34.720 --> 00:21:34.730 align:start position:0% the challenge is facing this kind of 00:21:34.730 --> 00:21:38.260 align:start position:0% the challenge is facing this kind of application<00:21:34.880> deployment<00:21:35.510> process<00:21:36.020> are<00:21:37.270> there 00:21:38.260 --> 00:21:38.270 align:start position:0% application deployment process are there 00:21:38.270 --> 00:21:39.790 align:start position:0% application deployment process are there of<00:21:38.420> course<00:21:38.600> many<00:21:39.020> questions<00:21:39.410> we<00:21:39.650> haven't 00:21:39.790 --> 00:21:39.800 align:start position:0% of course many questions we haven't 00:21:39.800 --> 00:21:42.250 align:start position:0% of course many questions we haven't answered<00:21:40.010> yet<00:21:40.310> we're<00:21:41.150> not<00:21:41.180> quite<00:21:41.510> sure<00:21:41.570> how 00:21:42.250 --> 00:21:42.260 align:start position:0% answered yet we're not quite sure how 00:21:42.260 --> 00:21:44.380 align:start position:0% answered yet we're not quite sure how contract<00:21:42.950> balances<00:21:43.490> ought<00:21:43.730> to<00:21:43.880> work<00:21:44.030> in<00:21:44.210> proof 00:21:44.380 --> 00:21:44.390 align:start position:0% contract balances ought to work in proof 00:21:44.390 --> 00:21:46.630 align:start position:0% contract balances ought to work in proof of<00:21:44.540> stake<00:21:44.780> there<00:21:45.410> are<00:21:45.470> lots<00:21:45.620> of<00:21:45.740> contracts<00:21:46.220> say 00:21:46.630 --> 00:21:46.640 align:start position:0% of stake there are lots of contracts say 00:21:46.640 --> 00:21:48.160 align:start position:0% of stake there are lots of contracts say on<00:21:46.820> the<00:21:46.910> etherium<00:21:47.390> main<00:21:47.570> chain<00:21:47.810> right<00:21:47.990> now 00:21:48.160 --> 00:21:48.170 align:start position:0% on the etherium main chain right now 00:21:48.170 --> 00:21:50.980 align:start position:0% on the etherium main chain right now which<00:21:48.710> hold<00:21:48.980> a<00:21:49.160> lot<00:21:49.310> of<00:21:49.340> ether<00:21:49.760> should<00:21:50.660> they<00:21:50.780> be 00:21:50.980 --> 00:21:50.990 align:start position:0% which hold a lot of ether should they be 00:21:50.990 --> 00:21:52.960 align:start position:0% which hold a lot of ether should they be able<00:21:51.080> to<00:21:51.200> delegate<00:21:51.650> what<00:21:52.430> happens<00:21:52.760> if<00:21:52.880> they 00:21:52.960 --> 00:21:52.970 align:start position:0% able to delegate what happens if they 00:21:52.970 --> 00:21:54.640 align:start position:0% able to delegate what happens if they get<00:21:53.090> slashed<00:21:53.420> what<00:21:53.810> happens<00:21:54.110> if<00:21:54.230> you<00:21:54.350> deposit 00:21:54.640 --> 00:21:54.650 align:start position:0% get slashed what happens if you deposit 00:21:54.650 --> 00:21:57.400 align:start position:0% get slashed what happens if you deposit your<00:21:55.010> tokens<00:21:55.580> to<00:21:55.820> to<00:21:55.970> a<00:21:56.000> Dax<00:21:56.240> contract<00:21:56.810> that 00:21:57.400 --> 00:21:57.410 align:start position:0% your tokens to to a Dax contract that 00:21:57.410 --> 00:21:58.990 align:start position:0% your tokens to to a Dax contract that Dex<00:21:57.650> contract<00:21:58.100> delegates<00:21:58.520> then<00:21:58.760> they<00:21:58.880> get 00:21:58.990 --> 00:21:59.000 align:start position:0% Dex contract delegates then they get 00:21:59.000 --> 00:22:01.660 align:start position:0% Dex contract delegates then they get slashed<00:21:59.300> are<00:21:59.840> you<00:21:59.990> responsible<00:22:00.320> maybe<00:22:00.830> we 00:22:01.660 --> 00:22:01.670 align:start position:0% slashed are you responsible maybe we 00:22:01.670 --> 00:22:03.340 align:start position:0% slashed are you responsible maybe we want<00:22:01.790> to<00:22:01.880> figure<00:22:02.060> that<00:22:02.210> out<00:22:02.270> we<00:22:02.570> haven't 00:22:03.340 --> 00:22:03.350 align:start position:0% want to figure that out we haven't 00:22:03.350 --> 00:22:05.920 align:start position:0% want to figure that out we haven't decided<00:22:03.560> what<00:22:03.890> the<00:22:04.070> exact<00:22:04.430> token<00:22:05.060> models<00:22:05.420> for 00:22:05.920 --> 00:22:05.930 align:start position:0% decided what the exact token models for 00:22:05.930 --> 00:22:07.990 align:start position:0% decided what the exact token models for fee-only<00:22:06.440> tokens<00:22:07.190> since<00:22:07.460> we<00:22:07.580> have<00:22:07.670> delegated 00:22:07.990 --> 00:22:08.000 align:start position:0% fee-only tokens since we have delegated 00:22:08.000 --> 00:22:11.080 align:start position:0% fee-only tokens since we have delegated security<00:22:08.570> ought<00:22:08.780> to<00:22:08.810> be<00:22:08.990> will<00:22:09.860> they<00:22:10.040> be 00:22:11.080 --> 00:22:11.090 align:start position:0% security ought to be will they be 00:22:11.090 --> 00:22:12.640 align:start position:0% security ought to be will they be the<00:22:11.240> same<00:22:11.510> or<00:22:11.780> similar<00:22:11.930> as<00:22:12.260> proof-of-work 00:22:12.640 --> 00:22:12.650 align:start position:0% the same or similar as proof-of-work 00:22:12.650 --> 00:22:14.680 align:start position:0% the same or similar as proof-of-work rewards<00:22:13.310> with<00:22:13.550> a<00:22:13.580> declining<00:22:13.940> exponential 00:22:14.680 --> 00:22:14.690 align:start position:0% rewards with a declining exponential 00:22:14.690 --> 00:22:17.410 align:start position:0% rewards with a declining exponential maybe<00:22:15.350> they<00:22:15.500> will<00:22:15.620> be<00:22:15.710> flat<00:22:16.010> 500<00:22:16.910> tokens<00:22:17.240> per 00:22:17.410 --> 00:22:17.420 align:start position:0% maybe they will be flat 500 tokens per 00:22:17.420 --> 00:22:19.380 align:start position:0% maybe they will be flat 500 tokens per hour<00:22:17.540> for<00:22:17.960> the<00:22:18.080> until<00:22:18.500> the<00:22:18.530> end<00:22:18.710> of<00:22:18.860> all<00:22:18.950> time 00:22:19.380 --> 00:22:19.390 align:start position:0% hour for the until the end of all time 00:22:19.390 --> 00:22:22.780 align:start position:0% hour for the until the end of all time lots<00:22:20.390> of<00:22:20.450> opportunities<00:22:21.020> to<00:22:21.140> experiment<00:22:21.790> of 00:22:22.780 --> 00:22:22.790 align:start position:0% lots of opportunities to experiment of 00:22:22.790 --> 00:22:24.550 align:start position:0% lots of opportunities to experiment of course<00:22:22.880> I<00:22:23.330> just<00:22:23.510> went<00:22:23.840> this<00:22:23.960> morning<00:22:23.990> to<00:22:24.320> the 00:22:24.550 --> 00:22:24.560 align:start position:0% course I just went this morning to the 00:22:24.560 --> 00:22:26.410 align:start position:0% course I just went this morning to the etherium<00:22:25.040> 2.0<00:22:25.490> talk<00:22:25.730> which<00:22:26.000> was<00:22:26.120> super 00:22:26.410 --> 00:22:26.420 align:start position:0% etherium 2.0 talk which was super 00:22:26.420 --> 00:22:28.690 align:start position:0% etherium 2.0 talk which was super interesting<00:22:26.900> and<00:22:27.380> I'd<00:22:28.040> haven't<00:22:28.370> had<00:22:28.460> a<00:22:28.490> chance 00:22:28.690 --> 00:22:28.700 align:start position:0% interesting and I'd haven't had a chance 00:22:28.700 --> 00:22:30.580 align:start position:0% interesting and I'd haven't had a chance to<00:22:28.820> update<00:22:29.150> this<00:22:29.270> slide<00:22:29.540> but<00:22:30.050> it<00:22:30.170> sounds<00:22:30.470> like 00:22:30.580 --> 00:22:30.590 align:start position:0% to update this slide but it sounds like 00:22:30.590 --> 00:22:31.900 align:start position:0% to update this slide but it sounds like they're<00:22:30.770> now<00:22:30.950> switching<00:22:31.250> to<00:22:31.400> a<00:22:31.490> version<00:22:31.700> of 00:22:31.900 --> 00:22:31.910 align:start position:0% they're now switching to a version of 00:22:31.910 --> 00:22:33.160 align:start position:0% they're now switching to a version of proof<00:22:32.090> of<00:22:32.210> stake<00:22:32.390> which<00:22:32.570> will<00:22:32.720> provide<00:22:32.900> very 00:22:33.160 --> 00:22:33.170 align:start position:0% proof of stake which will provide very 00:22:33.170 --> 00:22:35.050 align:start position:0% proof of stake which will provide very fast<00:22:33.560> finality<00:22:34.100> which<00:22:34.550> were<00:22:34.700> thrilled<00:22:34.970> about 00:22:35.050 --> 00:22:35.060 align:start position:0% fast finality which were thrilled about 00:22:35.060 --> 00:22:37.930 align:start position:0% fast finality which were thrilled about because<00:22:35.840> it<00:22:36.050> will<00:22:36.170> allow<00:22:36.440> even<00:22:36.920> faster<00:22:37.520> IBC 00:22:37.930 --> 00:22:37.940 align:start position:0% because it will allow even faster IBC 00:22:37.940 --> 00:22:40.450 align:start position:0% because it will allow even faster IBC connections<00:22:38.420> from<00:22:38.900> aetherium<00:22:39.350> 2.0<00:22:40.010> to<00:22:40.070> ether 00:22:40.450 --> 00:22:40.460 align:start position:0% connections from aetherium 2.0 to ether 00:22:40.460 --> 00:22:42.610 align:start position:0% connections from aetherium 2.0 to ether mint<00:22:40.640> to<00:22:40.760> cosmos<00:22:41.150> to<00:22:41.330> any<00:22:41.450> other<00:22:41.660> chains<00:22:41.960> which 00:22:42.610 --> 00:22:42.620 align:start position:0% mint to cosmos to any other chains which 00:22:42.620 --> 00:22:43.960 align:start position:0% mint to cosmos to any other chains which implement<00:22:43.040> this<00:22:43.130> kind<00:22:43.190> of<00:22:43.550> entertaining 00:22:43.960 --> 00:22:43.970 align:start position:0% implement this kind of entertaining 00:22:43.970 --> 00:22:50.320 align:start position:0% implement this kind of entertaining protocol<00:22:45.940> so<00:22:46.960> first<00:22:47.960> I<00:22:48.230> will<00:22:48.520> my<00:22:49.520> pitch<00:22:49.730> or<00:22:50.030> ask 00:22:50.320 --> 00:22:50.330 align:start position:0% protocol so first I will my pitch or ask 00:22:50.330 --> 00:22:51.940 align:start position:0% protocol so first I will my pitch or ask is<00:22:50.660> that<00:22:50.690> you<00:22:50.870> head<00:22:51.050> on<00:22:51.140> over<00:22:51.470> to<00:22:51.500> cosmos 00:22:51.940 --> 00:22:51.950 align:start position:0% is that you head on over to cosmos 00:22:51.950 --> 00:22:54.310 align:start position:0% is that you head on over to cosmos network<00:22:52.370> slash<00:22:52.610> DEFCON<00:22:53.060> 4 00:22:54.310 --> 00:22:54.320 align:start position:0% network slash DEFCON 4 00:22:54.320 --> 00:22:56.680 align:start position:0% network slash DEFCON 4 fill<00:22:54.920> out<00:22:55.070> the<00:22:55.250> survey<00:22:55.640> maybe<00:22:56.270> you<00:22:56.390> mentioned 00:22:56.680 --> 00:22:56.690 align:start position:0% fill out the survey maybe you mentioned 00:22:56.690 --> 00:22:58.240 align:start position:0% fill out the survey maybe you mentioned that<00:22:56.750> you<00:22:56.840> came<00:22:57.050> to<00:22:57.200> this<00:22:57.290> talk<00:22:57.560> ask<00:22:57.890> us<00:22:58.100> any 00:22:58.240 --> 00:22:58.250 align:start position:0% that you came to this talk ask us any 00:22:58.250 --> 00:23:00.010 align:start position:0% that you came to this talk ask us any questions<00:22:58.730> and<00:22:59.000> that<00:22:59.330> you<00:22:59.390> head<00:22:59.600> on<00:22:59.690> over<00:22:59.990> to 00:23:00.010 --> 00:23:00.020 align:start position:0% questions and that you head on over to 00:23:00.020 --> 00:23:03.280 align:start position:0% questions and that you head on over to our<00:23:00.170> booth<00:23:00.500> for<00:23:01.250> a<00:23:01.280> chance<00:23:01.640> to<00:23:01.760> win<00:23:02.090> a<00:23:02.450> sweet 00:23:03.280 --> 00:23:03.290 align:start position:0% our booth for a chance to win a sweet 00:23:03.290 --> 00:23:05.860 align:start position:0% our booth for a chance to win a sweet Cosmo<00:23:03.770> City<00:23:04.010> but<00:23:04.700> even<00:23:04.940> more<00:23:05.120> importantly<00:23:05.600> ask 00:23:05.860 --> 00:23:05.870 align:start position:0% Cosmo City but even more importantly ask 00:23:05.870 --> 00:23:07.960 align:start position:0% Cosmo City but even more importantly ask us<00:23:06.170> questions<00:23:06.590> about<00:23:06.770> ether<00:23:07.220> mint<00:23:07.370> how<00:23:07.910> you 00:23:07.960 --> 00:23:07.970 align:start position:0% us questions about ether mint how you 00:23:07.970 --> 00:23:10.060 align:start position:0% us questions about ether mint how you can<00:23:08.210> use<00:23:08.360> it<00:23:08.390> what<00:23:08.840> we're<00:23:08.990> up<00:23:09.020> to<00:23:09.140> how<00:23:09.770> we<00:23:09.830> can 00:23:10.060 --> 00:23:10.070 align:start position:0% can use it what we're up to how we can 00:23:10.070 --> 00:23:12.790 align:start position:0% can use it what we're up to how we can help<00:23:10.300> any<00:23:11.300> questions<00:23:11.660> thank<00:23:12.410> you<00:23:12.440> very<00:23:12.530> much 00:23:12.790 --> 00:23:12.800 align:start position:0% help any questions thank you very much 00:23:12.800 --> 00:23:22.880 align:start position:0% help any questions thank you very much we<00:23:12.980> have<00:23:13.070> five<00:23:13.280> minutes<00:23:13.460> for<00:23:13.730> questions 00:23:22.880 --> 00:23:22.890 align:start position:0% 00:23:22.890 --> 00:23:26.610 align:start position:0% when<00:23:23.890> is<00:23:24.040> the<00:23:24.220> tournament<00:23:24.580> going<00:23:24.820> life<00:23:25.620> when 00:23:26.610 --> 00:23:26.620 align:start position:0% when is the tournament going life when 00:23:26.620 --> 00:23:27.990 align:start position:0% when is the tournament going life when is<00:23:26.710> the<00:23:26.800> interment<00:23:27.100> going<00:23:27.280> live<00:23:27.460> excellent 00:23:27.990 --> 00:23:28.000 align:start position:0% is the interment going live excellent 00:23:28.000 --> 00:23:30.870 align:start position:0% is the interment going live excellent question<00:23:28.270> so<00:23:28.600> we<00:23:29.260> anticipate<00:23:29.880> Developer 00:23:30.870 --> 00:23:30.880 align:start position:0% question so we anticipate Developer 00:23:30.880 --> 00:23:33.930 align:start position:0% question so we anticipate Developer Preview<00:23:31.090> release<00:23:31.600> at<00:23:32.020> the<00:23:32.110> end<00:23:32.140> of<00:23:32.380> q4<00:23:32.940> and 00:23:33.930 --> 00:23:33.940 align:start position:0% Preview release at the end of q4 and 00:23:33.940 --> 00:23:36.060 align:start position:0% Preview release at the end of q4 and then<00:23:34.210> the<00:23:34.540> actual<00:23:35.050> deployment<00:23:35.230> of<00:23:35.710> interment 00:23:36.060 --> 00:23:36.070 align:start position:0% then the actual deployment of interment 00:23:36.070 --> 00:23:38.280 align:start position:0% then the actual deployment of interment will<00:23:36.220> be<00:23:36.310> up<00:23:36.460> to<00:23:36.610> Cosmo<00:23:36.940> sub<00:23:37.120> governance<00:23:37.630> so 00:23:38.280 --> 00:23:38.290 align:start position:0% will be up to Cosmo sub governance so 00:23:38.290 --> 00:23:44.040 align:start position:0% will be up to Cosmo sub governance so that<00:23:38.320> might<00:23:38.620> be<00:23:38.770> you<00:23:38.920> if<00:23:39.190> you're<00:23:39.370> voting<00:23:43.050> was 00:23:44.040 --> 00:23:44.050 align:start position:0% that might be you if you're voting was 00:23:44.050 --> 00:23:46.410 align:start position:0% that might be you if you're voting was the<00:23:44.260> status<00:23:44.800> or<00:23:45.220> was<00:23:45.460> the<00:23:45.580> state<00:23:45.850> of<00:23:46.060> the 00:23:46.410 --> 00:23:46.420 align:start position:0% the status or was the state of the 00:23:46.420 --> 00:23:49.080 align:start position:0% the status or was the state of the development<00:23:46.930> of<00:23:47.200> the<00:23:47.470> bridge<00:23:47.740> between<00:23:48.090> the 00:23:49.080 --> 00:23:49.090 align:start position:0% development of the bridge between the 00:23:49.090 --> 00:23:52.260 align:start position:0% development of the bridge between the Kosmos<00:23:49.390> hub<00:23:49.630> and<00:23:50.430> be<00:23:51.430> through<00:23:51.730> main<00:23:51.970> chain 00:23:52.260 --> 00:23:52.270 align:start position:0% Kosmos hub and be through main chain 00:23:52.270 --> 00:23:54.780 align:start position:0% Kosmos hub and be through main chain fully<00:23:53.230> specified<00:23:53.860> partially<00:23:54.430> implemented 00:23:54.780 --> 00:23:54.790 align:start position:0% fully specified partially implemented 00:23:54.790 --> 00:23:57.360 align:start position:0% fully specified partially implemented you<00:23:55.420> can<00:23:55.600> find<00:23:55.840> the<00:23:55.990> spec<00:23:56.230> on<00:23:56.470> the<00:23:56.620> cosmos<00:23:56.950> SDK 00:23:57.360 --> 00:23:57.370 align:start position:0% you can find the spec on the cosmos SDK 00:23:57.370 --> 00:23:59.460 align:start position:0% you can find the spec on the cosmos SDK github<00:23:57.700> repository<00:23:58.270> and<00:23:58.480> you<00:23:58.540> can<00:23:59.050> also<00:23:59.200> find 00:23:59.460 --> 00:23:59.470 align:start position:0% github repository and you can also find 00:23:59.470 --> 00:24:03.060 align:start position:0% github repository and you can also find a<00:23:59.680> prototype<00:24:00.100> implementation<00:24:01.920> are<00:24:02.920> you 00:24:03.060 --> 00:24:03.070 align:start position:0% a prototype implementation are you 00:24:03.070 --> 00:24:04.680 align:start position:0% a prototype implementation are you planning<00:24:03.430> to<00:24:03.550> support<00:24:03.670> inter<00:24:04.180> blockchain 00:24:04.680 --> 00:24:04.690 align:start position:0% planning to support inter blockchain 00:24:04.690 --> 00:24:06.510 align:start position:0% planning to support inter blockchain communication<00:24:05.380> with<00:24:05.770> with<00:24:06.070> chains<00:24:06.310> that<00:24:06.460> are 00:24:06.510 --> 00:24:06.520 align:start position:0% communication with with chains that are 00:24:06.520 --> 00:24:09.780 align:start position:0% communication with with chains that are not<00:24:06.790> part<00:24:07.090> of<00:24:07.150> cosmos<00:24:07.540> yes<00:24:08.380> absolutely<00:24:08.980> the 00:24:09.780 --> 00:24:09.790 align:start position:0% not part of cosmos yes absolutely the 00:24:09.790 --> 00:24:12.420 align:start position:0% not part of cosmos yes absolutely the spec<00:24:10.000> for<00:24:10.240> our<00:24:10.330> IBC<00:24:10.810> is<00:24:10.840> already<00:24:11.260> open<00:24:11.620> open 00:24:12.420 --> 00:24:12.430 align:start position:0% spec for our IBC is already open open 00:24:12.430 --> 00:24:13.620 align:start position:0% spec for our IBC is already open open source<00:24:12.640> and<00:24:12.910> we<00:24:12.970> encourage<00:24:13.270> anyone<00:24:13.510> to 00:24:13.620 --> 00:24:13.630 align:start position:0% source and we encourage anyone to 00:24:13.630 --> 00:24:16.110 align:start position:0% source and we encourage anyone to contribute<00:24:14.230> and<00:24:14.440> we<00:24:15.100> absolutely<00:24:15.610> encourage 00:24:16.110 --> 00:24:16.120 align:start position:0% contribute and we absolutely encourage 00:24:16.120 --> 00:24:18.030 align:start position:0% contribute and we absolutely encourage people<00:24:16.510> who<00:24:16.660> are<00:24:16.810> not<00:24:17.080> cosmos<00:24:17.470> teens<00:24:17.740> not 00:24:18.030 --> 00:24:18.040 align:start position:0% people who are not cosmos teens not 00:24:18.040 --> 00:24:20.070 align:start position:0% people who are not cosmos teens not using<00:24:18.340> tender<00:24:18.580> but<00:24:18.730> not<00:24:18.850> using<00:24:19.150> SDK<00:24:19.570> to 00:24:20.070 --> 00:24:20.080 align:start position:0% using tender but not using SDK to 00:24:20.080 --> 00:24:23.070 align:start position:0% using tender but not using SDK to implement<00:24:20.440> that<00:24:20.530> protocol<00:24:21.180> how<00:24:22.180> portable<00:24:22.840> is 00:24:23.070 --> 00:24:23.080 align:start position:0% implement that protocol how portable is 00:24:23.080 --> 00:24:25.440 align:start position:0% implement that protocol how portable is your<00:24:23.320> EVM<00:24:23.800> can<00:24:24.070> I<00:24:24.130> use<00:24:24.340> it<00:24:24.490> from<00:24:24.670> for<00:24:25.000> example<00:24:25.090> a 00:24:25.440 --> 00:24:25.450 align:start position:0% your EVM can I use it from for example a 00:24:25.450 --> 00:24:28.850 align:start position:0% your EVM can I use it from for example a hyper<00:24:25.660> ledger<00:24:25.930> project<00:24:26.680> or<00:24:26.860> something<00:24:27.130> else 00:24:28.850 --> 00:24:28.860 align:start position:0% hyper ledger project or something else 00:24:28.860 --> 00:24:31.410 align:start position:0% hyper ledger project or something else it<00:24:29.860> will<00:24:30.070> depend<00:24:30.460> a<00:24:30.550> little<00:24:30.670> on<00:24:30.910> the<00:24:31.000> project 00:24:31.410 --> 00:24:31.420 align:start position:0% it will depend a little on the project 00:24:31.420 --> 00:24:33.090 align:start position:0% it will depend a little on the project if<00:24:31.600> the<00:24:31.690> project<00:24:32.020> doesn't<00:24:32.170> go<00:24:32.500> it<00:24:32.860> will<00:24:32.980> be 00:24:33.090 --> 00:24:33.100 align:start position:0% if the project doesn't go it will be 00:24:33.100 --> 00:24:34.830 align:start position:0% if the project doesn't go it will be super<00:24:33.490> easy<00:24:33.520> if<00:24:34.000> the<00:24:34.060> project<00:24:34.390> is<00:24:34.450> not<00:24:34.570> a<00:24:34.630> go 00:24:34.830 --> 00:24:34.840 align:start position:0% super easy if the project is not a go 00:24:34.840 --> 00:24:36.120 align:start position:0% super easy if the project is not a go will<00:24:34.960> be<00:24:35.050> slightly<00:24:35.320> harder<00:24:35.560> but<00:24:35.920> still 00:24:36.120 --> 00:24:36.130 align:start position:0% will be slightly harder but still 00:24:36.130 --> 00:24:40.140 align:start position:0% will be slightly harder but still possible<00:24:36.900> if<00:24:37.900> you<00:24:38.140> deploy<00:24:38.380> a<00:24:38.410> EVM<00:24:39.160> module<00:24:39.670> it's 00:24:40.140 --> 00:24:40.150 align:start position:0% possible if you deploy a EVM module it's 00:24:40.150 --> 00:24:41.580 align:start position:0% possible if you deploy a EVM module it's the<00:24:40.270> idea<00:24:40.510> that<00:24:40.540> you<00:24:40.720> would<00:24:40.810> restrict<00:24:41.260> what 00:24:41.580 --> 00:24:41.590 align:start position:0% the idea that you would restrict what 00:24:41.590 --> 00:24:44.510 align:start position:0% the idea that you would restrict what contracts<00:24:42.280> can<00:24:42.520> be<00:24:42.550> deployed<00:24:42.970> into<00:24:43.630> that 00:24:44.510 --> 00:24:44.520 align:start position:0% contracts can be deployed into that 00:24:44.520 --> 00:24:46.380 align:start position:0% contracts can be deployed into that blockchain<00:24:45.520> essentially<00:24:46.000> so<00:24:46.180> you're<00:24:46.300> not 00:24:46.380 --> 00:24:46.390 align:start position:0% blockchain essentially so you're not 00:24:46.390 --> 00:24:48.630 align:start position:0% blockchain essentially so you're not competing<00:24:46.870> for<00:24:46.900> you<00:24:47.890> know<00:24:47.980> resources<00:24:48.310> with 00:24:48.630 --> 00:24:48.640 align:start position:0% competing for you know resources with 00:24:48.640 --> 00:24:50.300 align:start position:0% competing for you know resources with other<00:24:48.850> contracts<00:24:49.360> that<00:24:49.510> your<00:24:49.600> users<00:24:49.870> to<00:24:50.020> play 00:24:50.300 --> 00:24:50.310 align:start position:0% other contracts that your users to play 00:24:50.310 --> 00:24:52.650 align:start position:0% other contracts that your users to play yes<00:24:51.340> yes<00:24:51.640> so<00:24:51.790> you<00:24:51.880> could<00:24:52.000> deploy<00:24:52.210> an<00:24:52.330> EVM 00:24:52.650 --> 00:24:52.660 align:start position:0% yes yes so you could deploy an EVM 00:24:52.660 --> 00:24:54.150 align:start position:0% yes yes so you could deploy an EVM module<00:24:52.990> and<00:24:53.110> not<00:24:53.200> allow<00:24:53.380> contract<00:24:53.770> deployment 00:24:54.150 --> 00:24:54.160 align:start position:0% module and not allow contract deployment 00:24:54.160 --> 00:24:54.680 align:start position:0% module and not allow contract deployment at<00:24:54.250> all 00:24:54.680 --> 00:24:54.690 align:start position:0% at all 00:24:54.690 --> 00:24:56.370 align:start position:0% at all after<00:24:55.690> you've<00:24:55.810> like<00:24:55.990> launched<00:24:56.200> the 00:24:56.370 --> 00:24:56.380 align:start position:0% after you've like launched the 00:24:56.380 --> 00:24:57.750 align:start position:0% after you've like launched the blockchain<00:24:56.620> which<00:24:57.010> might<00:24:57.220> be<00:24:57.340> what<00:24:57.490> you<00:24:57.580> want 00:24:57.750 --> 00:24:57.760 align:start position:0% blockchain which might be what you want 00:24:57.760 --> 00:24:59.340 align:start position:0% blockchain which might be what you want to<00:24:57.820> do<00:24:57.910> in<00:24:58.030> a<00:24:58.090> sovereign<00:24:58.270> zone<00:24:58.660> or<00:24:59.110> you<00:24:59.200> could 00:24:59.340 --> 00:24:59.350 align:start position:0% to do in a sovereign zone or you could 00:24:59.350 --> 00:25:01.020 align:start position:0% to do in a sovereign zone or you could allow<00:24:59.530> limited<00:24:59.830> contract<00:25:00.400> appointment<00:25:00.850> to 00:25:01.020 --> 00:25:01.030 align:start position:0% allow limited contract appointment to 00:25:01.030 --> 00:25:02.160 align:start position:0% allow limited contract appointment to require<00:25:01.300> that<00:25:01.390> it<00:25:01.600> be<00:25:01.630> approved<00:25:01.960> by<00:25:02.140> the 00:25:02.160 --> 00:25:02.170 align:start position:0% require that it be approved by the 00:25:02.170 --> 00:25:04.580 align:start position:0% require that it be approved by the validator<00:25:02.590> side<00:25:02.800> or<00:25:03.040> something<00:25:03.280> like<00:25:03.340> that 00:25:04.580 --> 00:25:04.590 align:start position:0% validator side or something like that 00:25:04.590 --> 00:25:06.570 align:start position:0% validator side or something like that sorry<00:25:05.590> if<00:25:05.680> I<00:25:05.740> miss<00:25:05.920> this<00:25:06.010> but<00:25:06.160> like<00:25:06.280> can<00:25:06.490> you 00:25:06.570 --> 00:25:06.580 align:start position:0% sorry if I miss this but like can you 00:25:06.580 --> 00:25:09.900 align:start position:0% sorry if I miss this but like can you memorialize<00:25:07.390> the<00:25:07.890> internment<00:25:08.890> State<00:25:09.250> on<00:25:09.460> the 00:25:09.900 --> 00:25:09.910 align:start position:0% memorialize the internment State on the 00:25:09.910 --> 00:25:11.820 align:start position:0% memorialize the internment State on the route<00:25:10.120> chain<00:25:10.420> so<00:25:10.960> for<00:25:11.080> example<00:25:11.440> I<00:25:11.530> you<00:25:11.590> could 00:25:11.820 --> 00:25:11.830 align:start position:0% route chain so for example I you could 00:25:11.830 --> 00:25:14.060 align:start position:0% route chain so for example I you could use<00:25:11.950> like<00:25:12.130> the<00:25:12.250> so<00:25:12.430> IBM<00:25:12.760> to<00:25:13.060> invalidate<00:25:13.300> state 00:25:14.060 --> 00:25:14.070 align:start position:0% use like the so IBM to invalidate state 00:25:14.070 --> 00:25:16.770 align:start position:0% use like the so IBM to invalidate state transitions<00:25:15.070> on<00:25:15.220> the<00:25:15.250> route<00:25:15.430> chain<00:25:15.670> is<00:25:16.390> that 00:25:16.770 --> 00:25:16.780 align:start position:0% transitions on the route chain is that 00:25:16.780 --> 00:25:19.710 align:start position:0% transitions on the route chain is that possible<00:25:17.250> that<00:25:18.250> is<00:25:18.490> a<00:25:18.520> extremely<00:25:19.300> interesting 00:25:19.710 --> 00:25:19.720 align:start position:0% possible that is a extremely interesting 00:25:19.720 --> 00:25:23.880 align:start position:0% possible that is a extremely interesting question<00:25:20.050> in<00:25:20.970> principle<00:25:21.970> yes<00:25:22.270> the<00:25:23.140> cosmos<00:25:23.530> IBC 00:25:23.880 --> 00:25:23.890 align:start position:0% question in principle yes the cosmos IBC 00:25:23.890 --> 00:25:26.420 align:start position:0% question in principle yes the cosmos IBC model<00:25:24.190> doesn't<00:25:24.400> have<00:25:24.790> that<00:25:25.420> doesn't<00:25:25.960> need 00:25:26.420 --> 00:25:26.430 align:start position:0% model doesn't have that doesn't need 00:25:26.430 --> 00:25:28.890 align:start position:0% model doesn't have that doesn't need state<00:25:27.430> fraud<00:25:27.640> proofs<00:25:27.940> to<00:25:28.090> work<00:25:28.360> necessarily 00:25:28.890 --> 00:25:28.900 align:start position:0% state fraud proofs to work necessarily 00:25:28.900 --> 00:25:30.780 align:start position:0% state fraud proofs to work necessarily but<00:25:29.620> if<00:25:29.770> you<00:25:29.860> wanted<00:25:30.160> to<00:25:30.220> implement<00:25:30.430> something 00:25:30.780 --> 00:25:30.790 align:start position:0% but if you wanted to implement something 00:25:30.790 --> 00:25:32.220 align:start position:0% but if you wanted to implement something that<00:25:30.910> did<00:25:31.150> or<00:25:31.360> you<00:25:31.450> just<00:25:31.570> wanted<00:25:31.870> them<00:25:31.960> anyway 00:25:32.220 --> 00:25:32.230 align:start position:0% that did or you just wanted them anyway 00:25:32.230 --> 00:25:33.570 align:start position:0% that did or you just wanted them anyway for<00:25:32.260> extra<00:25:32.710> security 00:25:33.570 --> 00:25:33.580 align:start position:0% for extra security 00:25:33.580 --> 00:25:35.580 align:start position:0% for extra security think<00:25:33.760> that<00:25:33.880> wouldn't<00:25:34.060> be<00:25:34.150> too<00:25:34.300> hard<00:25:34.570> the<00:25:35.050> EVM 00:25:35.580 --> 00:25:35.590 align:start position:0% think that wouldn't be too hard the EVM 00:25:35.590 --> 00:25:37.560 align:start position:0% think that wouldn't be too hard the EVM is<00:25:35.770> inspect<00:25:36.310> compliant<00:25:36.820> so<00:25:37.210> if<00:25:37.360> you<00:25:37.450> have<00:25:37.540> a 00:25:37.560 --> 00:25:37.570 align:start position:0% is inspect compliant so if you have a 00:25:37.570 --> 00:25:39.180 align:start position:0% is inspect compliant so if you have a spec<00:25:37.810> compliant<00:25:37.930> interpreter<00:25:38.650> on<00:25:38.860> in 00:25:39.180 --> 00:25:39.190 align:start position:0% spec compliant interpreter on in 00:25:39.190 --> 00:25:42.830 align:start position:0% spec compliant interpreter on in solidity<00:25:39.610> on<00:25:39.850> the<00:25:40.360> etherium<00:25:40.720> a<00:25:40.810> chain<00:25:41.020> to<00:25:41.230> work 00:25:42.830 --> 00:25:42.840 align:start position:0% solidity on the etherium a chain to work 00:25:42.840 --> 00:25:45.720 align:start position:0% solidity on the etherium a chain to work hi<00:25:43.870> if<00:25:44.350> I<00:25:44.530> want<00:25:44.710> to<00:25:44.800> make<00:25:44.950> the<00:25:45.070> transaction 00:25:45.720 --> 00:25:45.730 align:start position:0% hi if I want to make the transaction 00:25:45.730 --> 00:25:47.610 align:start position:0% hi if I want to make the transaction between<00:25:46.120> two<00:25:46.480> block<00:25:46.780> chains<00:25:47.080> both<00:25:47.380> with 00:25:47.610 --> 00:25:47.620 align:start position:0% between two block chains both with 00:25:47.620 --> 00:25:51.990 align:start position:0% between two block chains both with cosmos<00:25:48.040> SDK<00:25:48.600> do<00:25:49.600> I<00:25:49.690> need<00:25:49.930> atoms<00:25:50.410> oh<00:25:51.000> right 00:25:51.990 --> 00:25:52.000 align:start position:0% cosmos SDK do I need atoms oh right 00:25:52.000 --> 00:25:53.760 align:start position:0% cosmos SDK do I need atoms oh right thank<00:25:52.390> you<00:25:52.450> I<00:25:52.570> alluded<00:25:53.350> to<00:25:53.380> it<00:25:53.590> and<00:25:53.680> then 00:25:53.760 --> 00:25:53.770 align:start position:0% thank you I alluded to it and then 00:25:53.770 --> 00:25:55.380 align:start position:0% thank you I alluded to it and then forgot<00:25:54.100> to<00:25:54.280> answer<00:25:54.640> that<00:25:54.730> question<00:25:54.880> so<00:25:55.240> thank 00:25:55.380 --> 00:25:55.390 align:start position:0% forgot to answer that question so thank 00:25:55.390 --> 00:25:56.730 align:start position:0% forgot to answer that question so thank you<00:25:55.480> for<00:25:55.600> asking<00:25:55.690> it<00:25:55.930> that's<00:25:56.350> one<00:25:56.590> of<00:25:56.680> the 00:25:56.730 --> 00:25:56.740 align:start position:0% you for asking it that's one of the 00:25:56.740 --> 00:25:58.230 align:start position:0% you for asking it that's one of the reasons<00:25:57.040> we<00:25:57.160> think<00:25:57.190> the<00:25:57.550> photon<00:25:57.820> hard<00:25:58.030> spoon 00:25:58.230 --> 00:25:58.240 align:start position:0% reasons we think the photon hard spoon 00:25:58.240 --> 00:25:59.610 align:start position:0% reasons we think the photon hard spoon is<00:25:58.420> super<00:25:58.660> compelling<00:25:58.930> because<00:25:59.170> it<00:25:59.380> will<00:25:59.500> make 00:25:59.610 --> 00:25:59.620 align:start position:0% is super compelling because it will make 00:25:59.620 --> 00:26:02.100 align:start position:0% is super compelling because it will make that<00:25:59.770> unnecessary<00:26:00.490> because<00:26:01.060> if<00:26:01.570> photons<00:26:01.960> are 00:26:02.100 --> 00:26:02.110 align:start position:0% that unnecessary because if photons are 00:26:02.110 --> 00:26:03.660 align:start position:0% that unnecessary because if photons are accepted<00:26:02.500> as<00:26:02.590> a<00:26:02.680> fee<00:26:02.830> token<00:26:03.160> on<00:26:03.250> the<00:26:03.370> hub<00:26:03.520> and 00:26:03.660 --> 00:26:03.670 align:start position:0% accepted as a fee token on the hub and 00:26:03.670 --> 00:26:06.060 align:start position:0% accepted as a fee token on the hub and on<00:26:03.790> a<00:26:03.940> Thurmond<00:26:04.270> then<00:26:04.810> users<00:26:05.260> can<00:26:05.560> transfer 00:26:06.060 --> 00:26:06.070 align:start position:0% on a Thurmond then users can transfer 00:26:06.070 --> 00:26:08.070 align:start position:0% on a Thurmond then users can transfer assets<00:26:06.460> over<00:26:06.760> both<00:26:06.940> of<00:26:06.970> those<00:26:07.180> IBC<00:26:07.660> bridges 00:26:08.070 --> 00:26:08.080 align:start position:0% assets over both of those IBC bridges 00:26:08.080 --> 00:26:10.200 align:start position:0% assets over both of those IBC bridges without<00:26:09.010> needing<00:26:09.430> to<00:26:09.550> acquire<00:26:09.850> any<00:26:10.090> new 00:26:10.200 --> 00:26:10.210 align:start position:0% without needing to acquire any new 00:26:10.210 --> 00:26:13.410 align:start position:0% without needing to acquire any new tokens<00:26:10.570> last<00:26:11.230> question<00:26:11.880> I'm<00:26:12.880> curious<00:26:13.210> what 00:26:13.410 --> 00:26:13.420 align:start position:0% tokens last question I'm curious what 00:26:13.420 --> 00:26:15.510 align:start position:0% tokens last question I'm curious what the<00:26:13.570> user<00:26:14.050> experience<00:26:14.740> is<00:26:14.920> like<00:26:15.160> when<00:26:15.400> you're 00:26:15.510 --> 00:26:15.520 align:start position:0% the user experience is like when you're 00:26:15.520 --> 00:26:17.910 align:start position:0% the user experience is like when you're moving<00:26:15.640> across<00:26:15.910> these<00:26:16.330> chains<00:26:16.630> we<00:26:17.440> hope<00:26:17.710> that 00:26:17.910 --> 00:26:17.920 align:start position:0% moving across these chains we hope that 00:26:17.920 --> 00:26:19.770 align:start position:0% moving across these chains we hope that it<00:26:18.040> will<00:26:18.130> be<00:26:18.250> seamless<00:26:18.670> it's<00:26:19.000> not<00:26:19.330> going<00:26:19.600> to<00:26:19.660> be 00:26:19.770 --> 00:26:19.780 align:start position:0% it will be seamless it's not going to be 00:26:19.780 --> 00:26:22.320 align:start position:0% it will be seamless it's not going to be seamless<00:26:20.200> at<00:26:20.350> first<00:26:20.740> but<00:26:21.490> it's<00:26:21.730> possible<00:26:22.180> in 00:26:22.320 --> 00:26:22.330 align:start position:0% seamless at first but it's possible in 00:26:22.330 --> 00:26:25.380 align:start position:0% seamless at first but it's possible in principle<00:26:22.510> to<00:26:23.110> abstract<00:26:23.470> over<00:26:24.150> most<00:26:25.150> of<00:26:25.300> the 00:26:25.380 --> 00:26:25.390 align:start position:0% principle to abstract over most of the 00:26:25.390 --> 00:26:27.480 align:start position:0% principle to abstract over most of the transactions<00:26:25.990> and<00:26:26.200> because<00:26:26.590> IBC<00:26:27.100> already 00:26:27.480 --> 00:26:27.490 align:start position:0% transactions and because IBC already 00:26:27.490 --> 00:26:29.400 align:start position:0% transactions and because IBC already provides<00:26:27.880> this<00:26:28.210> cross<00:26:28.480> chain<00:26:29.140> state 00:26:29.400 --> 00:26:29.410 align:start position:0% provides this cross chain state 00:26:29.410 --> 00:26:31.590 align:start position:0% provides this cross chain state verification<00:26:29.590> you<00:26:30.550> can<00:26:30.700> basically<00:26:30.850> pay<00:26:31.330> fees 00:26:31.590 --> 00:26:31.600 align:start position:0% verification you can basically pay fees 00:26:31.600 --> 00:26:41.600 align:start position:0% verification you can basically pay fees once<00:26:31.930> and<00:26:32.350> cover<00:26:32.830> all<00:26:32.920> of<00:26:33.220> the<00:26:33.310> transactions 00:26:41.600 --> 00:26:41.610 align:start position:0% 00:26:41.610 --> 00:26:43.670 align:start position:0% you