WEBVTT Kind: captions Language: en 00:00:03.930 --> 00:00:06.809 align:start position:0% hey<00:00:04.930> hi<00:00:05.110> my<00:00:06.010> name<00:00:06.190> is<00:00:06.250> Joey 00:00:06.809 --> 00:00:06.819 align:start position:0% hey hi my name is Joey 00:00:06.819 --> 00:00:08.820 align:start position:0% hey hi my name is Joey Kanani<00:00:07.270> and<00:00:07.569> I'm<00:00:07.690> a<00:00:07.779> founder<00:00:08.140> and<00:00:08.290> CEO<00:00:08.500> at 00:00:08.820 --> 00:00:08.830 align:start position:0% Kanani and I'm a founder and CEO at 00:00:08.830 --> 00:00:13.680 align:start position:0% Kanani and I'm a founder and CEO at matok<00:00:10.349> basically<00:00:11.349> we<00:00:11.650> are<00:00:11.920> building<00:00:12.700> a<00:00:13.089> lair 00:00:13.680 --> 00:00:13.690 align:start position:0% matok basically we are building a lair 00:00:13.690 --> 00:00:17.070 align:start position:0% matok basically we are building a lair to<00:00:13.960> scalability<00:00:14.410> solutions<00:00:15.129> for<00:00:16.050> aetherium 00:00:17.070 --> 00:00:17.080 align:start position:0% to scalability solutions for aetherium 00:00:17.080 --> 00:00:21.780 align:start position:0% to scalability solutions for aetherium and<00:00:18.420> we<00:00:19.420> use<00:00:19.690> plasma<00:00:20.050> forever<00:00:20.620> to<00:00:21.010> secure<00:00:21.460> our 00:00:21.780 --> 00:00:21.790 align:start position:0% and we use plasma forever to secure our 00:00:21.790 --> 00:00:25.800 align:start position:0% and we use plasma forever to secure our valuable<00:00:22.660> assets<00:00:23.040> and<00:00:24.040> we<00:00:25.030> use<00:00:25.210> proof<00:00:25.660> of 00:00:25.800 --> 00:00:25.810 align:start position:0% valuable assets and we use proof of 00:00:25.810 --> 00:00:28.710 align:start position:0% valuable assets and we use proof of stake<00:00:26.130> for<00:00:27.130> work<00:00:27.370> incisors<00:00:27.670> mechanism<00:00:28.390> to 00:00:28.710 --> 00:00:28.720 align:start position:0% stake for work incisors mechanism to 00:00:28.720 --> 00:00:32.729 align:start position:0% stake for work incisors mechanism to validate<00:00:29.170> and<00:00:29.530> keep<00:00:30.460> the<00:00:30.580> chain<00:00:30.790> running<00:00:31.739> so 00:00:32.729 --> 00:00:32.739 align:start position:0% validate and keep the chain running so 00:00:32.739 --> 00:00:35.330 align:start position:0% validate and keep the chain running so basically<00:00:33.129> today<00:00:33.540> I'm<00:00:34.540> here<00:00:34.809> to<00:00:34.989> talk<00:00:35.110> about 00:00:35.330 --> 00:00:35.340 align:start position:0% basically today I'm here to talk about 00:00:35.340 --> 00:00:39.630 align:start position:0% basically today I'm here to talk about mostly<00:00:36.340> how<00:00:36.600> we<00:00:37.600> at<00:00:37.930> matok<00:00:38.640> thought 00:00:39.630 --> 00:00:39.640 align:start position:0% mostly how we at matok thought 00:00:39.640 --> 00:00:41.819 align:start position:0% mostly how we at matok thought differently<00:00:40.330> than<00:00:40.720> other<00:00:40.900> layer<00:00:41.140> 2<00:00:41.350> solutions 00:00:41.819 --> 00:00:41.829 align:start position:0% differently than other layer 2 solutions 00:00:41.829 --> 00:00:45.360 align:start position:0% differently than other layer 2 solutions and<00:00:42.480> created<00:00:43.480> a<00:00:43.540> way<00:00:43.750> to<00:00:43.810> create<00:00:44.500> a<00:00:44.530> solution 00:00:45.360 --> 00:00:45.370 align:start position:0% and created a way to create a solution 00:00:45.370 --> 00:00:50.250 align:start position:0% and created a way to create a solution adoptions<00:00:46.180> for<00:00:46.510> dabs<00:00:46.990> and<00:00:47.350> users<00:00:49.020> we<00:00:50.020> are 00:00:50.250 --> 00:00:50.260 align:start position:0% adoptions for dabs and users we are 00:00:50.260 --> 00:00:52.560 align:start position:0% adoptions for dabs and users we are going<00:00:50.410> to<00:00:50.470> share<00:00:50.710> this<00:00:51.010> story<00:00:51.460> with<00:00:51.970> how<00:00:52.510> we 00:00:52.560 --> 00:00:52.570 align:start position:0% going to share this story with how we 00:00:52.570 --> 00:00:56.510 align:start position:0% going to share this story with how we did<00:00:53.110> our<00:00:53.350> tag<00:00:53.710> and<00:00:54.120> the<00:00:55.120> usability<00:00:55.420> part<00:00:55.870> of<00:00:55.989> it 00:00:56.510 --> 00:00:56.520 align:start position:0% did our tag and the usability part of it 00:00:56.520 --> 00:01:01.560 align:start position:0% did our tag and the usability part of it with<00:00:57.520> mattock<00:00:57.910> and<00:00:58.120> so<00:00:58.930> yeah<00:00:59.079> so<00:00:59.410> this<00:01:00.570> so 00:01:01.560 --> 00:01:01.570 align:start position:0% with mattock and so yeah so this so 00:01:01.570 --> 00:01:04.170 align:start position:0% with mattock and so yeah so this so basically<00:01:02.200> in<00:01:03.010> general<00:01:03.670> in<00:01:03.850> the<00:01:03.940> blockchain 00:01:04.170 --> 00:01:04.180 align:start position:0% basically in general in the blockchain 00:01:04.180 --> 00:01:09.059 align:start position:0% basically in general in the blockchain ecosystem<00:01:06.719> what<00:01:07.719> we<00:01:08.350> all<00:01:08.499> want<00:01:08.829> right 00:01:09.059 --> 00:01:09.069 align:start position:0% ecosystem what we all want right 00:01:09.069 --> 00:01:11.629 align:start position:0% ecosystem what we all want right these<00:01:09.579> are<00:01:09.729> ultimate<00:01:10.210> questions<00:01:10.749> right<00:01:11.079> now 00:01:11.629 --> 00:01:11.639 align:start position:0% these are ultimate questions right now 00:01:11.639 --> 00:01:15.719 align:start position:0% these are ultimate questions right now do<00:01:12.639> we<00:01:12.789> do<00:01:13.210> we<00:01:13.299> need<00:01:13.450> scalability<00:01:14.460> do<00:01:15.460> we<00:01:15.579> need 00:01:15.719 --> 00:01:15.729 align:start position:0% do we do we need scalability do we need 00:01:15.729 --> 00:01:20.399 align:start position:0% do we do we need scalability do we need more<00:01:16.030> apps<00:01:17.490> no<00:01:18.490> basically<00:01:19.329> what<00:01:19.780> do<00:01:20.049> we<00:01:20.200> need 00:01:20.399 --> 00:01:20.409 align:start position:0% more apps no basically what do we need 00:01:20.409 --> 00:01:24.749 align:start position:0% more apps no basically what do we need is<00:01:20.649> users<00:01:21.280> more<00:01:21.759> and<00:01:22.060> more<00:01:22.479> users<00:01:22.990> and<00:01:23.340> in<00:01:24.340> any 00:01:24.749 --> 00:01:24.759 align:start position:0% is users more and more users and in any 00:01:24.759 --> 00:01:27.929 align:start position:0% is users more and more users and in any industry<00:01:25.270> if<00:01:25.509> you<00:01:25.689> if<00:01:25.990> you<00:01:26.139> take<00:01:26.759> taken<00:01:27.759> notice 00:01:27.929 --> 00:01:27.939 align:start position:0% industry if you if you take taken notice 00:01:27.939 --> 00:01:30.149 align:start position:0% industry if you if you take taken notice of<00:01:28.209> outside<00:01:28.749> decentralized<00:01:29.380> systems 00:01:30.149 --> 00:01:30.159 align:start position:0% of outside decentralized systems 00:01:30.159 --> 00:01:32.819 align:start position:0% of outside decentralized systems decentralized<00:01:30.880> market<00:01:31.090> you<00:01:31.600> will<00:01:31.840> see<00:01:32.109> growth 00:01:32.819 --> 00:01:32.829 align:start position:0% decentralized market you will see growth 00:01:32.829 --> 00:01:35.249 align:start position:0% decentralized market you will see growth is<00:01:33.100> very<00:01:33.310> important<00:01:33.939> for<00:01:34.090> any<00:01:34.299> any<00:01:34.749> industry 00:01:35.249 --> 00:01:35.259 align:start position:0% is very important for any any industry 00:01:35.259 --> 00:01:39.749 align:start position:0% is very important for any any industry right<00:01:35.499> and<00:01:36.459> what<00:01:37.389> we<00:01:37.779> are<00:01:38.079> targeting<00:01:38.649> is<00:01:39.130> just 00:01:39.749 --> 00:01:39.759 align:start position:0% right and what we are targeting is just 00:01:39.759 --> 00:01:43.830 align:start position:0% right and what we are targeting is just users<00:01:40.149> right<00:01:41.340> someone<00:01:42.340> said<00:01:42.549> like<00:01:42.729> when<00:01:43.659> you 00:01:43.830 --> 00:01:43.840 align:start position:0% users right someone said like when you 00:01:43.840 --> 00:01:46.289 align:start position:0% users right someone said like when you think<00:01:44.289> about<00:01:44.529> the<00:01:44.740> problem<00:01:45.130> you<00:01:45.310> think<00:01:45.340> about 00:01:46.289 --> 00:01:46.299 align:start position:0% think about the problem you think about 00:01:46.299 --> 00:01:49.980 align:start position:0% think about the problem you think about you<00:01:47.109> think<00:01:47.380> a<00:01:47.619> backward<00:01:48.189> and<00:01:48.399> work<00:01:48.819> forward<00:01:49.149> so 00:01:49.980 --> 00:01:49.990 align:start position:0% you think a backward and work forward so 00:01:49.990 --> 00:01:53.399 align:start position:0% you think a backward and work forward so in<00:01:50.349> here<00:01:51.099> also<00:01:51.340> we<00:01:51.969> are<00:01:52.209> when<00:01:52.990> we<00:01:53.139> think<00:01:53.259> about 00:01:53.399 --> 00:01:53.409 align:start position:0% in here also we are when we think about 00:01:53.409 --> 00:01:56.249 align:start position:0% in here also we are when we think about the<00:01:53.619> problems<00:01:53.799> we<00:01:54.310> think<00:01:55.179> about<00:01:55.270> users<00:01:55.929> and 00:01:56.249 --> 00:01:56.259 align:start position:0% the problems we think about users and 00:01:56.259 --> 00:01:59.580 align:start position:0% the problems we think about users and how<00:01:56.590> we<00:01:56.649> get<00:01:57.009> more<00:01:57.069> users<00:01:57.700> and<00:01:58.630> what<00:01:59.049> backward 00:01:59.580 --> 00:01:59.590 align:start position:0% how we get more users and what backward 00:01:59.590 --> 00:02:02.279 align:start position:0% how we get more users and what backward like<00:01:59.799> we<00:02:00.340> how<00:02:00.759> we<00:02:00.789> get<00:02:01.119> like<00:02:01.479> more<00:02:01.719> DAP 00:02:02.279 --> 00:02:02.289 align:start position:0% like we how we get like more DAP 00:02:02.289 --> 00:02:05.459 align:start position:0% like we how we get like more DAP developers<00:02:02.829> to<00:02:03.189> build<00:02:03.340> on<00:02:03.719> the<00:02:04.719> block<00:02:05.200> chains 00:02:05.459 --> 00:02:05.469 align:start position:0% developers to build on the block chains 00:02:05.469 --> 00:02:07.830 align:start position:0% developers to build on the block chains and<00:02:05.770> how<00:02:06.069> they<00:02:06.520> can<00:02:06.700> actually<00:02:06.880> get<00:02:07.329> more<00:02:07.659> and 00:02:07.830 --> 00:02:07.840 align:start position:0% and how they can actually get more and 00:02:07.840 --> 00:02:10.589 align:start position:0% and how they can actually get more and more<00:02:07.899> users<00:02:08.410> so<00:02:08.979> it<00:02:09.340> works<00:02:10.000> both<00:02:10.300> ways 00:02:10.589 --> 00:02:10.599 align:start position:0% more users so it works both ways 00:02:10.599 --> 00:02:12.809 align:start position:0% more users so it works both ways you<00:02:11.050> need<00:02:11.230> users<00:02:11.680> and<00:02:11.980> for<00:02:12.129> that<00:02:12.310> you<00:02:12.790> need 00:02:12.809 --> 00:02:12.819 align:start position:0% you need users and for that you need 00:02:12.819 --> 00:02:16.259 align:start position:0% you need users and for that you need more<00:02:13.329> and<00:02:13.510> more<00:02:13.689> dabs<00:02:14.230> and<00:02:14.590> for<00:02:15.010> that<00:02:15.239> you<00:02:16.239> need 00:02:16.259 --> 00:02:16.269 align:start position:0% more and more dabs and for that you need 00:02:16.269 --> 00:02:17.280 align:start position:0% more and more dabs and for that you need scalability 00:02:17.280 --> 00:02:17.290 align:start position:0% scalability 00:02:17.290 --> 00:02:19.649 align:start position:0% scalability so<00:02:17.620> that<00:02:17.920> how<00:02:18.159> we<00:02:18.220> like<00:02:18.790> that's<00:02:19.060> how<00:02:19.209> we<00:02:19.269> walk 00:02:19.649 --> 00:02:19.659 align:start position:0% so that how we like that's how we walk 00:02:19.659 --> 00:02:23.369 align:start position:0% so that how we like that's how we walk like<00:02:19.689> backward<00:02:21.510> think<00:02:22.510> bigger<00:02:22.840> and<00:02:22.989> walk 00:02:23.369 --> 00:02:23.379 align:start position:0% like backward think bigger and walk 00:02:23.379 --> 00:02:25.410 align:start position:0% like backward think bigger and walk forward<00:02:23.890> so<00:02:24.099> we<00:02:24.310> start<00:02:24.730> with<00:02:24.879> a<00:02:24.939> scalability 00:02:25.410 --> 00:02:25.420 align:start position:0% forward so we start with a scalability 00:02:25.420 --> 00:02:28.710 align:start position:0% forward so we start with a scalability in<00:02:25.689> how<00:02:25.900> it<00:02:26.519> it<00:02:27.519> actually<00:02:27.909> affects<00:02:28.299> and<00:02:28.540> more 00:02:28.710 --> 00:02:28.720 align:start position:0% in how it it actually affects and more 00:02:28.720 --> 00:02:33.509 align:start position:0% in how it it actually affects and more most<00:02:29.200> apps<00:02:29.560> in<00:02:30.340> general<00:02:30.780> so<00:02:31.780> so<00:02:32.290> for<00:02:32.920> for<00:02:33.340> that 00:02:33.509 --> 00:02:33.519 align:start position:0% most apps in general so so for for that 00:02:33.519 --> 00:02:38.880 align:start position:0% most apps in general so so for for that what<00:02:33.970> we<00:02:34.000> are<00:02:34.239> doing<00:02:34.480> is<00:02:34.810> that<00:02:34.870> we<00:02:36.299> scale<00:02:37.890> we 00:02:38.880 --> 00:02:38.890 align:start position:0% what we are doing is that we scale we 00:02:38.890 --> 00:02:41.430 align:start position:0% what we are doing is that we scale we provide<00:02:39.519> scalability<00:02:39.819> as<00:02:40.450> a<00:02:40.480> layer<00:02:40.720> to<00:02:40.989> using 00:02:41.430 --> 00:02:41.440 align:start position:0% provide scalability as a layer to using 00:02:41.440 --> 00:02:45.210 align:start position:0% provide scalability as a layer to using plasma<00:02:41.709> and<00:02:42.159> predicates<00:02:42.720> we<00:02:43.720> also<00:02:43.900> use<00:02:44.440> side 00:02:45.210 --> 00:02:45.220 align:start position:0% plasma and predicates we also use side 00:02:45.220 --> 00:02:47.580 align:start position:0% plasma and predicates we also use side chains<00:02:45.549> right<00:02:46.390> side<00:02:46.720> chains<00:02:46.959> is<00:02:47.140> a<00:02:47.170> simple 00:02:47.580 --> 00:02:47.590 align:start position:0% chains right side chains is a simple 00:02:47.590 --> 00:02:49.199 align:start position:0% chains right side chains is a simple because<00:02:47.920> there<00:02:48.250> are<00:02:48.340> multiple<00:02:48.459> layer<00:02:49.000> two 00:02:49.199 --> 00:02:49.209 align:start position:0% because there are multiple layer two 00:02:49.209 --> 00:02:51.059 align:start position:0% because there are multiple layer two solutions<00:02:49.629> like<00:02:49.870> straight<00:02:50.140> channels<00:02:50.500> other 00:02:51.059 --> 00:02:51.069 align:start position:0% solutions like straight channels other 00:02:51.069 --> 00:02:53.280 align:start position:0% solutions like straight channels other other<00:02:51.430> other<00:02:51.640> solutions<00:02:52.150> but<00:02:52.780> the<00:02:52.900> problem 00:02:53.280 --> 00:02:53.290 align:start position:0% other other solutions but the problem 00:02:53.290 --> 00:02:54.720 align:start position:0% other other solutions but the problem with<00:02:53.409> other<00:02:53.590> solutions<00:02:53.920> are<00:02:54.280> there<00:02:54.519> like 00:02:54.720 --> 00:02:54.730 align:start position:0% with other solutions are there like 00:02:54.730 --> 00:02:58.020 align:start position:0% with other solutions are there like there<00:02:55.060> is<00:02:55.120> a<00:02:55.209> trade-off<00:02:55.480> between<00:02:55.629> the<00:02:57.030> amount 00:02:58.020 --> 00:02:58.030 align:start position:0% there is a trade-off between the amount 00:02:58.030 --> 00:03:01.259 align:start position:0% there is a trade-off between the amount you<00:02:58.269> need<00:02:58.510> to<00:02:58.870> settle<00:02:59.530> your<00:02:59.819> so<00:03:00.819> settle<00:03:01.180> your 00:03:01.259 --> 00:03:01.269 align:start position:0% you need to settle your so settle your 00:03:01.269 --> 00:03:03.960 align:start position:0% you need to settle your so settle your transactions<00:03:01.930> and<00:03:02.590> make<00:03:03.280> your<00:03:03.459> transactions 00:03:03.960 --> 00:03:03.970 align:start position:0% transactions and make your transactions 00:03:03.970 --> 00:03:06.899 align:start position:0% transactions and make your transactions on<00:03:04.090> the<00:03:04.209> on<00:03:04.389> the<00:03:04.480> side<00:03:04.629> on<00:03:04.840> the<00:03:04.870> layer<00:03:05.290> to<00:03:05.909> what 00:03:06.899 --> 00:03:06.909 align:start position:0% on the on the side on the layer to what 00:03:06.909 --> 00:03:09.809 align:start position:0% on the on the side on the layer to what we<00:03:07.209> use<00:03:07.959> is<00:03:08.230> the<00:03:08.260> simple<00:03:08.799> side<00:03:09.040> chains<00:03:09.340> using 00:03:09.809 --> 00:03:09.819 align:start position:0% we use is the simple side chains using 00:03:09.819 --> 00:03:13.319 align:start position:0% we use is the simple side chains using plasmas<00:03:10.450> and<00:03:10.720> prop<00:03:11.200> stake<00:03:11.530> and<00:03:12.430> we<00:03:12.609> hide<00:03:12.909> all 00:03:13.319 --> 00:03:13.329 align:start position:0% plasmas and prop stake and we hide all 00:03:13.329 --> 00:03:16.160 align:start position:0% plasmas and prop stake and we hide all other<00:03:14.049> complexities<00:03:14.920> underneath<00:03:15.639> and<00:03:15.940> just 00:03:16.160 --> 00:03:16.170 align:start position:0% other complexities underneath and just 00:03:16.170 --> 00:03:19.920 align:start position:0% other complexities underneath and just provide<00:03:17.170> DAP<00:03:18.159> developers<00:03:18.670> what<00:03:18.909> they<00:03:19.060> need<00:03:19.269> so 00:03:19.920 --> 00:03:19.930 align:start position:0% provide DAP developers what they need so 00:03:19.930 --> 00:03:23.909 align:start position:0% provide DAP developers what they need so here<00:03:20.650> so<00:03:21.069> just<00:03:21.579> for<00:03:22.109> developers<00:03:23.109> if<00:03:23.530> you<00:03:23.739> if 00:03:23.909 --> 00:03:23.919 align:start position:0% here so just for developers if you if 00:03:23.919 --> 00:03:25.530 align:start position:0% here so just for developers if you if you<00:03:24.069> if<00:03:24.370> you<00:03:24.489> see<00:03:24.639> the<00:03:24.760> what<00:03:24.910> DEP<00:03:25.120> developers 00:03:25.530 --> 00:03:25.540 align:start position:0% you if you see the what DEP developers 00:03:25.540 --> 00:03:29.849 align:start position:0% you if you see the what DEP developers need<00:03:25.859> we<00:03:26.859> just<00:03:26.889> provide<00:03:27.519> easy<00:03:28.560> onboarding<00:03:29.560> for 00:03:29.849 --> 00:03:29.859 align:start position:0% need we just provide easy onboarding for 00:03:29.859 --> 00:03:34.229 align:start position:0% need we just provide easy onboarding for all<00:03:30.040> the<00:03:30.549> DAP<00:03:30.790> developers<00:03:32.190> we<00:03:33.190> provide<00:03:33.669> their 00:03:34.229 --> 00:03:34.239 align:start position:0% all the DAP developers we provide their 00:03:34.239 --> 00:03:37.879 align:start position:0% all the DAP developers we provide their valuable<00:03:34.930> assets<00:03:35.349> using<00:03:35.980> the<00:03:36.519> using<00:03:37.150> plasma 00:03:37.879 --> 00:03:37.889 align:start position:0% valuable assets using the using plasma 00:03:37.889 --> 00:03:42.300 align:start position:0% valuable assets using the using plasma and<00:03:39.239> for<00:03:40.239> them<00:03:40.419> we<00:03:40.449> need<00:03:40.900> also<00:03:41.650> provide<00:03:42.040> as 00:03:42.300 --> 00:03:42.310 align:start position:0% and for them we need also provide as 00:03:42.310 --> 00:03:44.819 align:start position:0% and for them we need also provide as easy<00:03:42.549> migrations<00:03:43.239> so<00:03:43.540> once<00:03:43.900> Joey<00:03:44.319> Krug<00:03:44.590> said 00:03:44.819 --> 00:03:44.829 align:start position:0% easy migrations so once Joey Krug said 00:03:44.829 --> 00:03:47.250 align:start position:0% easy migrations so once Joey Krug said if<00:03:45.459> someone<00:03:46.060> comes<00:03:46.269> to<00:03:46.329> me<00:03:46.419> and<00:03:46.569> asked<00:03:47.079> for 00:03:47.250 --> 00:03:47.260 align:start position:0% if someone comes to me and asked for 00:03:47.260 --> 00:03:49.619 align:start position:0% if someone comes to me and asked for let's<00:03:47.590> say<00:03:47.709> if<00:03:47.859> I<00:03:48.190> can<00:03:48.609> scale<00:03:48.910> your<00:03:48.940> dabs<00:03:49.299> in 00:03:49.619 --> 00:03:49.629 align:start position:0% let's say if I can scale your dabs in 00:03:49.629 --> 00:03:51.360 align:start position:0% let's say if I can scale your dabs in next<00:03:49.930> six<00:03:50.109> months 00:03:51.360 --> 00:03:51.370 align:start position:0% next six months 00:03:51.370 --> 00:03:53.640 align:start position:0% next six months we<00:03:52.120> gonna<00:03:52.389> we're<00:03:52.989> not<00:03:53.109> going<00:03:53.319> to<00:03:53.379> do<00:03:53.500> it 00:03:53.640 --> 00:03:53.650 align:start position:0% we gonna we're not going to do it 00:03:53.650 --> 00:03:55.890 align:start position:0% we gonna we're not going to do it because<00:03:53.919> it<00:03:54.250> takes<00:03:54.519> huge<00:03:55.090> amount<00:03:55.329> of<00:03:55.419> efforts 00:03:55.890 --> 00:03:55.900 align:start position:0% because it takes huge amount of efforts 00:03:55.900 --> 00:03:58.319 align:start position:0% because it takes huge amount of efforts and<00:03:56.230> time<00:03:56.410> and<00:03:56.739> money<00:03:56.919> to<00:03:57.280> migrate<00:03:57.669> from<00:03:57.699> one 00:03:58.319 --> 00:03:58.329 align:start position:0% and time and money to migrate from one 00:03:58.329 --> 00:04:00.869 align:start position:0% and time and money to migrate from one solution<00:03:59.169> to<00:03:59.319> other<00:03:59.440> solutions<00:03:59.949> just<00:04:00.250> to 00:04:00.869 --> 00:04:00.879 align:start position:0% solution to other solutions just to 00:04:00.879 --> 00:04:03.780 align:start position:0% solution to other solutions just to scale<00:04:01.150> your<00:04:01.329> dabs<00:04:01.599> instead<00:04:02.440> people<00:04:03.190> want<00:04:03.609> to 00:04:03.780 --> 00:04:03.790 align:start position:0% scale your dabs instead people want to 00:04:03.790 --> 00:04:06.030 align:start position:0% scale your dabs instead people want to focus<00:04:04.090> on<00:04:04.480> the<00:04:04.750> dabs<00:04:04.959> instead<00:04:05.440> of<00:04:05.530> focusing<00:04:05.739> on 00:04:06.030 --> 00:04:06.040 align:start position:0% focus on the dabs instead of focusing on 00:04:06.040 --> 00:04:08.670 align:start position:0% focus on the dabs instead of focusing on the<00:04:06.190> scalability<00:04:06.790> right<00:04:07.299> so<00:04:07.780> what<00:04:08.049> we<00:04:08.260> do<00:04:08.409> is 00:04:08.670 --> 00:04:08.680 align:start position:0% the scalability right so what we do is 00:04:08.680 --> 00:04:11.809 align:start position:0% the scalability right so what we do is that<00:04:09.040> we<00:04:09.099> just<00:04:09.519> provide<00:04:10.000> simple<00:04:10.840> and<00:04:11.260> easy 00:04:11.809 --> 00:04:11.819 align:start position:0% that we just provide simple and easy 00:04:11.819 --> 00:04:14.809 align:start position:0% that we just provide simple and easy migrations<00:04:12.819> and<00:04:13.120> testing<00:04:13.479> for<00:04:13.690> developers 00:04:14.809 --> 00:04:14.819 align:start position:0% migrations and testing for developers 00:04:14.819 --> 00:04:18.149 align:start position:0% migrations and testing for developers most<00:04:15.819> of<00:04:16.030> the<00:04:16.120> times<00:04:16.419> on<00:04:16.900> the<00:04:17.289> app<00:04:17.680> developers 00:04:18.149 --> 00:04:18.159 align:start position:0% most of the times on the app developers 00:04:18.159 --> 00:04:20.490 align:start position:0% most of the times on the app developers need<00:04:18.599> different<00:04:19.599> kind<00:04:19.930> of<00:04:19.989> three<00:04:20.289> models 00:04:20.490 --> 00:04:20.500 align:start position:0% need different kind of three models 00:04:20.500 --> 00:04:22.830 align:start position:0% need different kind of three models three<00:04:21.010> models<00:04:21.370> right<00:04:21.549> in<00:04:22.030> this<00:04:22.150> area<00:04:22.240> if<00:04:22.659> you 00:04:22.830 --> 00:04:22.840 align:start position:0% three models right in this area if you 00:04:22.840 --> 00:04:24.360 align:start position:0% three models right in this area if you if<00:04:23.139> you<00:04:23.260> want<00:04:23.440> to<00:04:23.530> make<00:04:23.770> a<00:04:23.800> transaction<00:04:24.190> you 00:04:24.360 --> 00:04:24.370 align:start position:0% if you want to make a transaction you 00:04:24.370 --> 00:04:27.450 align:start position:0% if you want to make a transaction you need<00:04:24.760> each<00:04:25.120> areum<00:04:25.450> or<00:04:25.919> maybe<00:04:26.919> you<00:04:27.130> need<00:04:27.280> to 00:04:27.450 --> 00:04:27.460 align:start position:0% need each areum or maybe you need to 00:04:27.460 --> 00:04:29.740 align:start position:0% need each areum or maybe you need to integrate<00:04:28.120> meta<00:04:28.630> transactions 00:04:29.740 --> 00:04:29.750 align:start position:0% integrate meta transactions 00:04:29.750 --> 00:04:33.130 align:start position:0% integrate meta transactions but<00:04:30.080> here<00:04:30.380> we<00:04:31.280> actually<00:04:31.550> provides<00:04:32.330> those<00:04:32.780> kind 00:04:33.130 --> 00:04:33.140 align:start position:0% but here we actually provides those kind 00:04:33.140 --> 00:04:37.990 align:start position:0% but here we actually provides those kind of<00:04:34.120> solutions<00:04:35.120> in<00:04:35.540> build<00:04:35.870> on<00:04:36.110> Matic<00:04:36.680> so<00:04:37.190> that 00:04:37.990 --> 00:04:38.000 align:start position:0% of solutions in build on Matic so that 00:04:38.000 --> 00:04:40.030 align:start position:0% of solutions in build on Matic so that paper<00:04:38.210> just<00:04:38.600> can<00:04:38.810> use<00:04:39.080> directly<00:04:39.530> on<00:04:39.860> the 00:04:40.030 --> 00:04:40.040 align:start position:0% paper just can use directly on the 00:04:40.040 --> 00:04:43.590 align:start position:0% paper just can use directly on the platform<00:04:40.490> and<00:04:40.730> just<00:04:41.060> run<00:04:41.480> that<00:04:41.630> apps<00:04:42.160> easily 00:04:43.590 --> 00:04:43.600 align:start position:0% platform and just run that apps easily 00:04:43.600 --> 00:04:46.090 align:start position:0% platform and just run that apps easily there<00:04:44.600> is<00:04:44.720> another<00:04:45.050> problem<00:04:45.290> in<00:04:45.710> the<00:04:45.860> whole 00:04:46.090 --> 00:04:46.100 align:start position:0% there is another problem in the whole 00:04:46.100 --> 00:04:49.150 align:start position:0% there is another problem in the whole ecosystem<00:04:46.430> is<00:04:46.880> a<00:04:46.910> UX<00:04:47.360> problem<00:04:47.720> right<00:04:47.930> so<00:04:48.140> if<00:04:48.770> we 00:04:49.150 --> 00:04:49.160 align:start position:0% ecosystem is a UX problem right so if we 00:04:49.160 --> 00:04:52.330 align:start position:0% ecosystem is a UX problem right so if we think<00:04:49.400> about<00:04:49.780> if<00:04:50.780> you<00:04:51.260> are<00:04:51.290> scaling<00:04:51.920> any 00:04:52.330 --> 00:04:52.340 align:start position:0% think about if you are scaling any 00:04:52.340 --> 00:04:55.480 align:start position:0% think about if you are scaling any theory<00:04:52.580> amande<00:04:53.350> simple<00:04:54.370> providing<00:04:55.370> a 00:04:55.480 --> 00:04:55.490 align:start position:0% theory amande simple providing a 00:04:55.490 --> 00:04:58.720 align:start position:0% theory amande simple providing a platform<00:04:56.000> for<00:04:56.560> developers<00:04:57.560> you<00:04:58.130> also<00:04:58.370> need<00:04:58.700> to 00:04:58.720 --> 00:04:58.730 align:start position:0% platform for developers you also need to 00:04:58.730 --> 00:05:01.150 align:start position:0% platform for developers you also need to make<00:04:59.000> sure<00:04:59.030> you<00:04:59.540> provide<00:04:59.780> a<00:04:59.990> pest<00:05:00.410> UX<00:05:00.920> in<00:05:01.070> the 00:05:01.150 --> 00:05:01.160 align:start position:0% make sure you provide a pest UX in the 00:05:01.160 --> 00:05:04.720 align:start position:0% make sure you provide a pest UX in the industry<00:05:01.580> so<00:05:02.510> people<00:05:02.810> can<00:05:02.960> just<00:05:03.140> move<00:05:03.550> to<00:05:04.550> the 00:05:04.720 --> 00:05:04.730 align:start position:0% industry so people can just move to the 00:05:04.730 --> 00:05:07.240 align:start position:0% industry so people can just move to the next<00:05:04.970> platform<00:05:05.270> right<00:05:05.600> if<00:05:06.320> you<00:05:06.560> see<00:05:06.800> that<00:05:06.980> the 00:05:07.240 --> 00:05:07.250 align:start position:0% next platform right if you see that the 00:05:07.250 --> 00:05:08.800 align:start position:0% next platform right if you see that the previous<00:05:07.610> markets<00:05:08.060> and<00:05:08.300> before<00:05:08.690> the 00:05:08.800 --> 00:05:08.810 align:start position:0% previous markets and before the 00:05:08.810 --> 00:05:11.680 align:start position:0% previous markets and before the decentralization<00:05:09.380> movement<00:05:10.270> wave<00:05:11.270> one<00:05:11.660> and 00:05:11.680 --> 00:05:11.690 align:start position:0% decentralization movement wave one and 00:05:11.690 --> 00:05:15.550 align:start position:0% decentralization movement wave one and wave<00:05:11.900> to<00:05:12.230> each<00:05:12.940> iteration<00:05:13.940> makes<00:05:14.660> your<00:05:15.050> users 00:05:15.550 --> 00:05:15.560 align:start position:0% wave to each iteration makes your users 00:05:15.560 --> 00:05:17.890 align:start position:0% wave to each iteration makes your users your<00:05:16.400> applications<00:05:17.210> very<00:05:17.420> user<00:05:17.780> friendly 00:05:17.890 --> 00:05:17.900 align:start position:0% your applications very user friendly 00:05:17.900 --> 00:05:20.620 align:start position:0% your applications very user friendly right<00:05:18.740> if<00:05:19.370> you<00:05:19.580> use<00:05:19.790> currently<00:05:20.360> if<00:05:20.450> you<00:05:20.570> are 00:05:20.620 --> 00:05:20.630 align:start position:0% right if you use currently if you are 00:05:20.630 --> 00:05:22.990 align:start position:0% right if you use currently if you are using<00:05:20.780> uber<00:05:21.169> before<00:05:21.950> they<00:05:22.190> you<00:05:22.400> are<00:05:22.430> using<00:05:22.760> it 00:05:22.990 --> 00:05:23.000 align:start position:0% using uber before they you are using it 00:05:23.000 --> 00:05:24.700 align:start position:0% using uber before they you are using it axis<00:05:23.330> right<00:05:23.510> see<00:05:24.080> the<00:05:24.230> difference<00:05:24.560> between 00:05:24.700 --> 00:05:24.710 align:start position:0% axis right see the difference between 00:05:24.710 --> 00:05:26.740 align:start position:0% axis right see the difference between the<00:05:24.980> user<00:05:25.160> experience<00:05:25.520> throughout<00:05:26.240> the<00:05:26.360> web 00:05:26.740 --> 00:05:26.750 align:start position:0% the user experience throughout the web 00:05:26.750 --> 00:05:31.960 align:start position:0% the user experience throughout the web involve<00:05:27.790> when<00:05:28.930> wave<00:05:29.930> 1<00:05:30.169> wave<00:05:30.200> 2<00:05:30.710> came<00:05:31.190> right<00:05:31.400> so 00:05:31.960 --> 00:05:31.970 align:start position:0% involve when wave 1 wave 2 came right so 00:05:31.970 --> 00:05:35.290 align:start position:0% involve when wave 1 wave 2 came right so when<00:05:32.180> we<00:05:32.419> talk<00:05:32.870> about<00:05:32.900> web<00:05:33.440> 3<00:05:33.680> we<00:05:34.400> should<00:05:34.640> think 00:05:35.290 --> 00:05:35.300 align:start position:0% when we talk about web 3 we should think 00:05:35.300 --> 00:05:37.780 align:start position:0% when we talk about web 3 we should think about<00:05:35.450> how<00:05:36.169> we<00:05:36.230> can<00:05:36.650> gonna<00:05:36.860> provide<00:05:37.280> better 00:05:37.780 --> 00:05:37.790 align:start position:0% about how we can gonna provide better 00:05:37.790 --> 00:05:39.520 align:start position:0% about how we can gonna provide better user<00:05:38.060> experience<00:05:38.600> for<00:05:38.690> our<00:05:38.930> users 00:05:39.520 --> 00:05:39.530 align:start position:0% user experience for our users 00:05:39.530 --> 00:05:43.720 align:start position:0% user experience for our users better<00:05:40.460> experience<00:05:41.000> for<00:05:41.120> our<00:05:42.460> developers<00:05:43.460> and 00:05:43.720 --> 00:05:43.730 align:start position:0% better experience for our developers and 00:05:43.730 --> 00:05:46.740 align:start position:0% better experience for our developers and for<00:05:44.240> that<00:05:44.360> we<00:05:44.630> also<00:05:44.780> have<00:05:45.229> multiple 00:05:46.740 --> 00:05:46.750 align:start position:0% for that we also have multiple 00:05:46.750 --> 00:05:50.680 align:start position:0% for that we also have multiple development<00:05:47.750> tools<00:05:48.320> as<00:05:48.530> well<00:05:48.910> as<00:05:49.910> which 00:05:50.680 --> 00:05:50.690 align:start position:0% development tools as well as which 00:05:50.690 --> 00:05:52.659 align:start position:0% development tools as well as which people<00:05:51.229> can<00:05:51.410> see<00:05:51.500> directly<00:05:51.860> integrate<00:05:52.370> and 00:05:52.659 --> 00:05:52.669 align:start position:0% people can see directly integrate and 00:05:52.669 --> 00:05:55.780 align:start position:0% people can see directly integrate and know<00:05:53.000> provide<00:05:53.450> kind<00:05:53.780> of<00:05:53.930> no<00:05:54.790> seamless 00:05:55.780 --> 00:05:55.790 align:start position:0% know provide kind of no seamless 00:05:55.790 --> 00:05:59.590 align:start position:0% know provide kind of no seamless experience<00:05:56.300> for<00:05:57.140> the<00:05:57.260> users<00:05:57.710> so<00:05:57.919> now<00:05:58.850> if<00:05:59.120> you 00:05:59.590 --> 00:05:59.600 align:start position:0% experience for the users so now if you 00:05:59.600 --> 00:06:02.950 align:start position:0% experience for the users so now if you think<00:05:59.630> about<00:05:59.930> the<00:06:00.850> what<00:06:01.850> we<00:06:02.120> as<00:06:02.419> a<00:06:02.510> Matic 00:06:02.950 --> 00:06:02.960 align:start position:0% think about the what we as a Matic 00:06:02.960 --> 00:06:07.060 align:start position:0% think about the what we as a Matic provide<00:06:03.610> to<00:06:04.690> developers<00:06:05.690> is<00:06:05.900> that<00:06:06.169> we<00:06:06.919> use 00:06:07.060 --> 00:06:07.070 align:start position:0% provide to developers is that we use 00:06:07.070 --> 00:06:10.900 align:start position:0% provide to developers is that we use plasma<00:06:07.580> so<00:06:07.790> basically<00:06:08.150> plus<00:06:09.020> in<00:06:09.890> our<00:06:10.430> plasma 00:06:10.900 --> 00:06:10.910 align:start position:0% plasma so basically plus in our plasma 00:06:10.910 --> 00:06:14.320 align:start position:0% plasma so basically plus in our plasma model<00:06:11.210> we<00:06:12.200> use<00:06:12.530> more<00:06:13.070> VP<00:06:13.460> there<00:06:13.820> are<00:06:13.910> multiple 00:06:14.320 --> 00:06:14.330 align:start position:0% model we use more VP there are multiple 00:06:14.330 --> 00:06:16.900 align:start position:0% model we use more VP there are multiple flavors<00:06:14.510> of<00:06:14.810> plasma<00:06:15.229> and<00:06:15.500> currently<00:06:16.190> but<00:06:16.669> we 00:06:16.900 --> 00:06:16.910 align:start position:0% flavors of plasma and currently but we 00:06:16.910 --> 00:06:20.940 align:start position:0% flavors of plasma and currently but we use<00:06:17.090> more<00:06:17.390> VP<00:06:17.810> plus<00:06:18.800> we<00:06:19.250> actually<00:06:19.850> use<00:06:20.120> EVM 00:06:20.940 --> 00:06:20.950 align:start position:0% use more VP plus we actually use EVM 00:06:20.950 --> 00:06:24.969 align:start position:0% use more VP plus we actually use EVM which<00:06:21.950> with<00:06:22.220> plasma<00:06:22.460> right<00:06:23.120> so<00:06:23.710> some<00:06:24.710> of<00:06:24.830> you 00:06:24.969 --> 00:06:24.979 align:start position:0% which with plasma right so some of you 00:06:24.979 --> 00:06:27.940 align:start position:0% which with plasma right so some of you know<00:06:25.130> that<00:06:25.160> it<00:06:25.640> is<00:06:26.000> not<00:06:26.360> viable<00:06:26.570> to<00:06:27.080> create<00:06:27.919> a 00:06:27.940 --> 00:06:27.950 align:start position:0% know that it is not viable to create a 00:06:27.950 --> 00:06:30.430 align:start position:0% know that it is not viable to create a plasma<00:06:28.460> which<00:06:28.669> is<00:06:28.820> general<00:06:29.660> computation<00:06:30.260> for 00:06:30.430 --> 00:06:30.440 align:start position:0% plasma which is general computation for 00:06:30.440 --> 00:06:32.860 align:start position:0% plasma which is general computation for Center<00:06:30.710> computations<00:06:31.250> but<00:06:31.790> for<00:06:32.270> now<00:06:32.450> we<00:06:32.510> are 00:06:32.860 --> 00:06:32.870 align:start position:0% Center computations but for now we are 00:06:32.870 --> 00:06:35.830 align:start position:0% Center computations but for now we are using<00:06:33.800> yessuh<00:06:34.250> -<00:06:34.430> we<00:06:35.210> have<00:06:35.360> like<00:06:35.600> kind<00:06:35.780> of 00:06:35.830 --> 00:06:35.840 align:start position:0% using yessuh - we have like kind of 00:06:35.840 --> 00:06:38.620 align:start position:0% using yessuh - we have like kind of solutions<00:06:36.350> where<00:06:36.650> you<00:06:36.860> can<00:06:37.040> use<00:06:37.310> es<00:06:37.640> a<00:06:37.760> 20s<00:06:38.599> a 00:06:38.620 --> 00:06:38.630 align:start position:0% solutions where you can use es a 20s a 00:06:38.630 --> 00:06:41.330 align:start position:0% solutions where you can use es a 20s a 71<00:06:39.520> indirectly 00:06:41.330 --> 00:06:41.340 align:start position:0% 71 indirectly 00:06:41.340 --> 00:06:44.420 align:start position:0% 71 indirectly and<00:06:41.550> directly<00:06:42.210> on<00:06:42.540> on<00:06:42.900> a<00:06:43.170> VM<00:06:43.470> so<00:06:43.980> basically 00:06:44.420 --> 00:06:44.430 align:start position:0% and directly on on a VM so basically 00:06:44.430 --> 00:06:47.570 align:start position:0% and directly on on a VM so basically what<00:06:45.330> we<00:06:45.450> did<00:06:45.480> is<00:06:45.660> like<00:06:45.930> we<00:06:46.110> changed<00:06:46.590> a<00:06:46.800> RC<00:06:47.190> 20 00:06:47.570 --> 00:06:47.580 align:start position:0% what we did is like we changed a RC 20 00:06:47.580 --> 00:06:49.880 align:start position:0% what we did is like we changed a RC 20 our<00:06:48.150> standard<00:06:48.750> a<00:06:48.870> little<00:06:49.170> bit<00:06:49.320> and<00:06:49.500> added 00:06:49.880 --> 00:06:49.890 align:start position:0% our standard a little bit and added 00:06:49.890 --> 00:06:53.270 align:start position:0% our standard a little bit and added receipts<00:06:50.510> extra<00:06:51.510> receipt<00:06:51.840> to<00:06:52.410> make<00:06:52.770> sure<00:06:52.980> like 00:06:53.270 --> 00:06:53.280 align:start position:0% receipts extra receipt to make sure like 00:06:53.280 --> 00:06:56.890 align:start position:0% receipts extra receipt to make sure like input<00:06:53.520> output<00:06:54.210> input<00:06:55.020> 1<00:06:55.380> input<00:06:55.560> out<00:06:55.890> output<00:06:56.430> 1 00:06:56.890 --> 00:06:56.900 align:start position:0% input output input 1 input out output 1 00:06:56.900 --> 00:06:59.720 align:start position:0% input output input 1 input out output 1 input<00:06:57.900> to<00:06:58.080> output<00:06:58.290> 2<00:06:58.620> some<00:06:58.800> kind<00:06:58.980> of<00:06:59.070> no<00:06:59.310> simple 00:06:59.720 --> 00:06:59.730 align:start position:0% input to output 2 some kind of no simple 00:06:59.730 --> 00:07:02.090 align:start position:0% input to output 2 some kind of no simple account<00:07:00.200> accounting<00:07:01.200> on<00:07:01.350> the<00:07:01.620> receipts<00:07:01.980> and 00:07:02.090 --> 00:07:02.100 align:start position:0% account accounting on the receipts and 00:07:02.100 --> 00:07:05.510 align:start position:0% account accounting on the receipts and it<00:07:02.550> it<00:07:03.210> actually<00:07:03.450> helped<00:07:03.840> us<00:07:04.020> to<00:07:04.490> create<00:07:05.490> a 00:07:05.510 --> 00:07:05.520 align:start position:0% it it actually helped us to create a 00:07:05.520 --> 00:07:07.370 align:start position:0% it it actually helped us to create a floor<00:07:05.820> proofs<00:07:06.090> when<00:07:06.360> you<00:07:06.540> exit<00:07:07.020> from<00:07:07.230> the 00:07:07.370 --> 00:07:07.380 align:start position:0% floor proofs when you exit from the 00:07:07.380 --> 00:07:10.340 align:start position:0% floor proofs when you exit from the plasma<00:07:07.620> framework<00:07:08.190> so<00:07:09.060> those<00:07:09.300> kind<00:07:09.630> of<00:07:09.720> little 00:07:10.340 --> 00:07:10.350 align:start position:0% plasma framework so those kind of little 00:07:10.350 --> 00:07:13.670 align:start position:0% plasma framework so those kind of little bit<00:07:10.680> tricks<00:07:11.370> and<00:07:11.730> tweaks<00:07:11.970> we<00:07:12.240> made<00:07:12.570> on<00:07:13.290> our 00:07:13.670 --> 00:07:13.680 align:start position:0% bit tricks and tweaks we made on our 00:07:13.680 --> 00:07:16.160 align:start position:0% bit tricks and tweaks we made on our plasma<00:07:14.130> model<00:07:14.400> to<00:07:14.580> create<00:07:14.730> a<00:07:14.970> seamless<00:07:15.330> AVM 00:07:16.160 --> 00:07:16.170 align:start position:0% plasma model to create a seamless AVM 00:07:16.170 --> 00:07:18.830 align:start position:0% plasma model to create a seamless AVM compatible<00:07:16.860> plasma<00:07:17.370> is<00:07:17.550> a<00:07:17.760> 20<00:07:18.120> and<00:07:18.300> in<00:07:18.420> 71 00:07:18.830 --> 00:07:18.840 align:start position:0% compatible plasma is a 20 and in 71 00:07:18.840 --> 00:07:21.530 align:start position:0% compatible plasma is a 20 and in 71 computations<00:07:19.740> and<00:07:20.610> if<00:07:20.820> you<00:07:21.000> think<00:07:21.270> about 00:07:21.530 --> 00:07:21.540 align:start position:0% computations and if you think about 00:07:21.540 --> 00:07:26.540 align:start position:0% computations and if you think about simple<00:07:21.870> a<00:07:22.680> RC<00:07:23.190> 20<00:07:23.520> and<00:07:24.080> 21<00:07:25.080> it's<00:07:25.920> just<00:07:26.190> a<00:07:26.250> simple 00:07:26.540 --> 00:07:26.550 align:start position:0% simple a RC 20 and 21 it's just a simple 00:07:26.550 --> 00:07:28.400 align:start position:0% simple a RC 20 and 21 it's just a simple computation<00:07:27.120> plus<00:07:27.360> or<00:07:27.510> minus<00:07:27.780> let's<00:07:27.960> say<00:07:28.050> if<00:07:28.200> I 00:07:28.400 --> 00:07:28.410 align:start position:0% computation plus or minus let's say if I 00:07:28.410 --> 00:07:30.680 align:start position:0% computation plus or minus let's say if I am<00:07:28.530> sending<00:07:28.980> it<00:07:29.100> then<00:07:29.700> it<00:07:29.970> died<00:07:30.180> to<00:07:30.240> someone 00:07:30.680 --> 00:07:30.690 align:start position:0% am sending it then it died to someone 00:07:30.690 --> 00:07:34.700 align:start position:0% am sending it then it died to someone else<00:07:30.900> it<00:07:31.740> just<00:07:31.880> subtract<00:07:32.880> the<00:07:33.480> amount<00:07:34.200> from<00:07:34.620> my 00:07:34.700 --> 00:07:34.710 align:start position:0% else it just subtract the amount from my 00:07:34.710 --> 00:07:37.700 align:start position:0% else it just subtract the amount from my account<00:07:35.340> and<00:07:35.700> add<00:07:35.910> so<00:07:36.120> the<00:07:36.240> opponent<00:07:37.170> account 00:07:37.700 --> 00:07:37.710 align:start position:0% account and add so the opponent account 00:07:37.710 --> 00:07:41.150 align:start position:0% account and add so the opponent account write<00:07:37.890> the<00:07:38.390> other<00:07:39.390> person's<00:07:39.810> account<00:07:40.080> but<00:07:40.860> if 00:07:41.150 --> 00:07:41.160 align:start position:0% write the other person's account but if 00:07:41.160 --> 00:07:43.700 align:start position:0% write the other person's account but if you<00:07:41.310> think<00:07:41.520> about<00:07:41.640> a<00:07:41.850> little<00:07:42.750> bit<00:07:42.930> of<00:07:43.170> complex 00:07:43.700 --> 00:07:43.710 align:start position:0% you think about a little bit of complex 00:07:43.710 --> 00:07:49.280 align:start position:0% you think about a little bit of complex complex<00:07:44.610> a<00:07:45.360> little<00:07:46.260> complex<00:07:47.240> state<00:07:48.240> you<00:07:48.900> may 00:07:49.280 --> 00:07:49.290 align:start position:0% complex a little complex state you may 00:07:49.290 --> 00:07:51.680 align:start position:0% complex a little complex state you may want<00:07:50.190> to<00:07:50.280> write<00:07:50.640> your<00:07:50.850> predicates<00:07:51.420> so 00:07:51.680 --> 00:07:51.690 align:start position:0% want to write your predicates so 00:07:51.690 --> 00:07:53.530 align:start position:0% want to write your predicates so predicates<00:07:52.170> basically<00:07:52.620> just<00:07:52.830> say<00:07:52.980> ok<00:07:53.250> hey 00:07:53.530 --> 00:07:53.540 align:start position:0% predicates basically just say ok hey 00:07:53.540 --> 00:07:55.940 align:start position:0% predicates basically just say ok hey let's<00:07:54.540> say<00:07:54.630> if<00:07:54.780> you<00:07:54.960> are<00:07:54.990> using<00:07:55.350> multi-sig 00:07:55.940 --> 00:07:55.950 align:start position:0% let's say if you are using multi-sig 00:07:55.950 --> 00:07:58.970 align:start position:0% let's say if you are using multi-sig wallet<00:07:56.310> right<00:07:56.820> when<00:07:57.780> you<00:07:57.990> when<00:07:58.380> you<00:07:58.500> move<00:07:58.740> your 00:07:58.970 --> 00:07:58.980 align:start position:0% wallet right when you when you move your 00:07:58.980 --> 00:08:01.190 align:start position:0% wallet right when you when you move your state<00:07:59.280> from<00:07:59.640> the<00:07:59.820> from<00:08:00.300> the<00:08:00.390> sidechain<00:08:00.600> to<00:08:01.170> a 00:08:01.190 --> 00:08:01.200 align:start position:0% state from the from the sidechain to a 00:08:01.200 --> 00:08:03.980 align:start position:0% state from the from the sidechain to a serum<00:08:01.470> chain<00:08:01.910> you<00:08:02.910> need<00:08:03.090> to<00:08:03.210> make<00:08:03.450> sure<00:08:03.480> only 00:08:03.980 --> 00:08:03.990 align:start position:0% serum chain you need to make sure only 00:08:03.990 --> 00:08:06.650 align:start position:0% serum chain you need to make sure only only<00:08:04.350> owners<00:08:05.070> of<00:08:05.310> the<00:08:05.460> multi-sig<00:08:05.970> wallet<00:08:06.270> only 00:08:06.650 --> 00:08:06.660 align:start position:0% only owners of the multi-sig wallet only 00:08:06.660 --> 00:08:10.100 align:start position:0% only owners of the multi-sig wallet only can<00:08:06.840> no<00:08:07.230> withdraw<00:08:07.650> your<00:08:07.910> with<00:08:08.910> tokens<00:08:09.480> or<00:08:09.660> exit 00:08:10.100 --> 00:08:10.110 align:start position:0% can no withdraw your with tokens or exit 00:08:10.110 --> 00:08:11.810 align:start position:0% can no withdraw your with tokens or exit your<00:08:10.230> tokens<00:08:10.590> from<00:08:10.710> which<00:08:10.920> theorem<00:08:11.160> sidechain 00:08:11.810 --> 00:08:11.820 align:start position:0% your tokens from which theorem sidechain 00:08:11.820 --> 00:08:13.880 align:start position:0% your tokens from which theorem sidechain to<00:08:12.060> each<00:08:12.150> same<00:08:12.270> chain<00:08:12.540> right<00:08:13.020> so<00:08:13.410> those<00:08:13.590> kind 00:08:13.880 --> 00:08:13.890 align:start position:0% to each same chain right so those kind 00:08:13.890 --> 00:08:16.730 align:start position:0% to each same chain right so those kind of<00:08:14.010> state<00:08:14.250> competition<00:08:14.850> you<00:08:15.030> can<00:08:15.180> write<00:08:15.740> using 00:08:16.730 --> 00:08:16.740 align:start position:0% of state competition you can write using 00:08:16.740 --> 00:08:19.400 align:start position:0% of state competition you can write using predicates<00:08:17.370> predicates<00:08:18.120> systems<00:08:18.510> right<00:08:19.230> now 00:08:19.400 --> 00:08:19.410 align:start position:0% predicates predicates systems right now 00:08:19.410 --> 00:08:22.550 align:start position:0% predicates predicates systems right now on<00:08:19.590> medic<00:08:19.920> but<00:08:20.730> for<00:08:21.150> us<00:08:21.360> a<00:08:21.450> 20<00:08:21.780> and<00:08:22.020> most<00:08:22.350> of<00:08:22.500> the 00:08:22.550 --> 00:08:22.560 align:start position:0% on medic but for us a 20 and most of the 00:08:22.560 --> 00:08:24.700 align:start position:0% on medic but for us a 20 and most of the standards<00:08:23.010> we<00:08:23.190> actually<00:08:23.550> provide<00:08:23.910> directly 00:08:24.700 --> 00:08:24.710 align:start position:0% standards we actually provide directly 00:08:24.710 --> 00:08:28.240 align:start position:0% standards we actually provide directly in<00:08:25.710> build<00:08:26.190> support<00:08:26.640> for<00:08:26.870> predicates<00:08:27.870> right 00:08:28.240 --> 00:08:28.250 align:start position:0% in build support for predicates right 00:08:28.250 --> 00:08:31.070 align:start position:0% in build support for predicates right there<00:08:29.250> is<00:08:29.340> a<00:08:29.370> there's<00:08:29.790> also<00:08:30.060> some<00:08:30.810> kind<00:08:30.930> of 00:08:31.070 --> 00:08:31.080 align:start position:0% there is a there's also some kind of 00:08:31.080 --> 00:08:33.770 align:start position:0% there is a there's also some kind of problems<00:08:31.620> in<00:08:31.950> in<00:08:32.250> plasma<00:08:32.820> where<00:08:33.090> you<00:08:33.210> exceed 00:08:33.770 --> 00:08:33.780 align:start position:0% problems in in plasma where you exceed 00:08:33.780 --> 00:08:36.590 align:start position:0% problems in in plasma where you exceed your<00:08:34.380> tokens<00:08:34.830> from<00:08:35.010> the<00:08:35.130> precise<00:08:36.000> chain<00:08:36.270> to 00:08:36.590 --> 00:08:36.600 align:start position:0% your tokens from the precise chain to 00:08:36.600 --> 00:08:39.500 align:start position:0% your tokens from the precise chain to same<00:08:36.930> chain<00:08:37.230> it<00:08:37.560> takes<00:08:37.860> seven<00:08:38.190> days<00:08:38.220> or<00:08:38.670> more 00:08:39.500 --> 00:08:39.510 align:start position:0% same chain it takes seven days or more 00:08:39.510 --> 00:08:42.920 align:start position:0% same chain it takes seven days or more because<00:08:40.160> you<00:08:41.160> need<00:08:41.310> to<00:08:41.430> make<00:08:41.640> sure<00:08:41.670> you<00:08:42.180> you 00:08:42.920 --> 00:08:42.930 align:start position:0% because you need to make sure you you 00:08:42.930 --> 00:08:44.960 align:start position:0% because you need to make sure you you don't<00:08:43.200> create<00:08:43.920> a<00:08:44.010> fraud<00:08:44.310> on<00:08:44.520> the<00:08:44.550> side<00:08:44.790> chain 00:08:44.960 --> 00:08:44.970 align:start position:0% don't create a fraud on the side chain 00:08:44.970 --> 00:08:47.810 align:start position:0% don't create a fraud on the side chain and<00:08:45.180> it's<00:08:45.300> exit<00:08:45.870> instantly<00:08:46.580> so<00:08:47.580> plasma 00:08:47.810 --> 00:08:47.820 align:start position:0% and it's exit instantly so plasma 00:08:47.820 --> 00:08:50.420 align:start position:0% and it's exit instantly so plasma framework<00:08:48.600> provides<00:08:49.020> you<00:08:49.410> a<00:08:49.440> way<00:08:49.800> to<00:08:49.830> create 00:08:50.420 --> 00:08:50.430 align:start position:0% framework provides you a way to create 00:08:50.430 --> 00:08:51.269 align:start position:0% framework provides you a way to create No 00:08:51.269 --> 00:08:51.279 align:start position:0% No 00:08:51.279 --> 00:08:52.889 align:start position:0% No have<00:08:51.639> a<00:08:51.670> like<00:08:51.819> priority<00:08:52.389> queue<00:08:52.629> when<00:08:52.810> you 00:08:52.889 --> 00:08:52.899 align:start position:0% have a like priority queue when you 00:08:52.899 --> 00:08:55.050 align:start position:0% have a like priority queue when you exceed<00:08:53.230> so<00:08:53.439> it<00:08:53.589> takes<00:08:53.829> kind<00:08:54.189> of<00:08:54.279> seven<00:08:54.819> days 00:08:55.050 --> 00:08:55.060 align:start position:0% exceed so it takes kind of seven days 00:08:55.060 --> 00:08:57.720 align:start position:0% exceed so it takes kind of seven days for<00:08:55.660> exit<00:08:55.959> but<00:08:56.560> what<00:08:56.769> we<00:08:56.920> do<00:08:57.100> is<00:08:57.370> that<00:08:57.399> we 00:08:57.720 --> 00:08:57.730 align:start position:0% for exit but what we do is that we 00:08:57.730 --> 00:09:01.470 align:start position:0% for exit but what we do is that we actually<00:08:58.180> sell<00:08:58.720> your<00:08:59.019> exit<00:08:59.500> in<00:09:00.459> directly<00:09:01.060> to 00:09:01.470 --> 00:09:01.480 align:start position:0% actually sell your exit in directly to 00:09:01.480 --> 00:09:04.619 align:start position:0% actually sell your exit in directly to know<00:09:02.100> where<00:09:03.100> the<00:09:03.279> buyer<00:09:03.490> and<00:09:03.819> you<00:09:04.089> get<00:09:04.269> the<00:09:04.449> X 00:09:04.619 --> 00:09:04.629 align:start position:0% know where the buyer and you get the X 00:09:04.629 --> 00:09:07.980 align:start position:0% know where the buyer and you get the X exit<00:09:05.230> instantly<00:09:05.740> but<00:09:05.949> you<00:09:06.160> pay<00:09:06.370> some<00:09:06.639> fees<00:09:06.990> for 00:09:07.980 --> 00:09:07.990 align:start position:0% exit instantly but you pay some fees for 00:09:07.990 --> 00:09:10.230 align:start position:0% exit instantly but you pay some fees for it<00:09:08.139> and<00:09:08.319> you<00:09:08.769> know<00:09:08.800> it's<00:09:09.129> kind<00:09:09.339> of<00:09:09.459> security 00:09:10.230 --> 00:09:10.240 align:start position:0% it and you know it's kind of security 00:09:10.240 --> 00:09:13.379 align:start position:0% it and you know it's kind of security with<00:09:11.139> which<00:09:11.500> kind<00:09:11.740> of<00:09:11.829> you<00:09:11.920> know<00:09:12.040> with<00:09:13.029> with 00:09:13.379 --> 00:09:13.389 align:start position:0% with which kind of you know with with 00:09:13.389 --> 00:09:16.920 align:start position:0% with which kind of you know with with probability<00:09:14.290> using<00:09:14.639> just<00:09:15.639> other<00:09:16.449> person<00:09:16.779> can 00:09:16.920 --> 00:09:16.930 align:start position:0% probability using just other person can 00:09:16.930 --> 00:09:19.199 align:start position:0% probability using just other person can just<00:09:17.079> prove<00:09:17.259> okay<00:09:17.439> hey<00:09:17.680> your<00:09:18.189> exit<00:09:18.550> is<00:09:18.670> valid 00:09:19.199 --> 00:09:19.209 align:start position:0% just prove okay hey your exit is valid 00:09:19.209 --> 00:09:21.420 align:start position:0% just prove okay hey your exit is valid you<00:09:19.420> can<00:09:19.750> exit<00:09:20.079> but<00:09:20.259> you<00:09:20.350> have<00:09:20.560> to<00:09:20.649> pay<00:09:20.860> let's 00:09:21.420 --> 00:09:21.430 align:start position:0% you can exit but you have to pay let's 00:09:21.430 --> 00:09:24.150 align:start position:0% you can exit but you have to pay let's say<00:09:21.579> point<00:09:22.240> a<00:09:22.449> point<00:09:22.629> zero<00:09:22.899> nine<00:09:23.230> die<00:09:23.439> for<00:09:23.949> one 00:09:24.150 --> 00:09:24.160 align:start position:0% say point a point zero nine die for one 00:09:24.160 --> 00:09:27.119 align:start position:0% say point a point zero nine die for one die<00:09:24.389> if<00:09:25.389> you<00:09:25.600> if<00:09:25.990> you<00:09:26.139> don't<00:09:26.319> want<00:09:26.500> to<00:09:26.620> wait<00:09:26.829> for 00:09:27.119 --> 00:09:27.129 align:start position:0% die if you if you don't want to wait for 00:09:27.129 --> 00:09:28.800 align:start position:0% die if you if you don't want to wait for like<00:09:27.279> seven<00:09:27.579> days<00:09:27.730> so<00:09:28.329> those<00:09:28.509> kind<00:09:28.720> of 00:09:28.800 --> 00:09:28.810 align:start position:0% like seven days so those kind of 00:09:28.810 --> 00:09:32.069 align:start position:0% like seven days so those kind of marketplace<00:09:29.350> we<00:09:29.620> are<00:09:29.860> a<00:09:30.189> building<00:09:30.660> for<00:09:31.660> faster 00:09:32.069 --> 00:09:32.079 align:start position:0% marketplace we are a building for faster 00:09:32.079 --> 00:09:35.970 align:start position:0% marketplace we are a building for faster exceeds<00:09:32.500> on<00:09:33.160> our<00:09:33.339> system<00:09:33.870> as<00:09:34.870> we<00:09:35.439> said<00:09:35.620> as<00:09:35.800> we 00:09:35.970 --> 00:09:35.980 align:start position:0% exceeds on our system as we said as we 00:09:35.980 --> 00:09:38.220 align:start position:0% exceeds on our system as we said as we said<00:09:36.129> like<00:09:36.310> we<00:09:36.490> also<00:09:36.699> provide<00:09:37.180> multiple<00:09:37.569> SDKs 00:09:38.220 --> 00:09:38.230 align:start position:0% said like we also provide multiple SDKs 00:09:38.230 --> 00:09:40.610 align:start position:0% said like we also provide multiple SDKs in<00:09:38.560> development<00:09:38.920> tools<00:09:39.100> to<00:09:39.430> just<00:09:39.670> to<00:09:39.879> onboard 00:09:40.610 --> 00:09:40.620 align:start position:0% in development tools to just to onboard 00:09:40.620 --> 00:09:45.119 align:start position:0% in development tools to just to onboard more<00:09:41.620> and<00:09:41.769> more<00:09:42.009> tap<00:09:42.610> developers<00:09:43.800> directly<00:09:44.800> on 00:09:45.119 --> 00:09:45.129 align:start position:0% more and more tap developers directly on 00:09:45.129 --> 00:09:49.499 align:start position:0% more and more tap developers directly on the<00:09:46.019> directly<00:09:47.019> on<00:09:47.230> our<00:09:47.589> systems<00:09:48.060> the<00:09:49.060> main 00:09:49.499 --> 00:09:49.509 align:start position:0% the directly on our systems the main 00:09:49.509 --> 00:09:52.379 align:start position:0% the directly on our systems the main thing<00:09:49.779> is<00:09:49.990> that<00:09:50.019> we<00:09:50.740> are<00:09:51.189> not<00:09:51.910> the<00:09:52.329> app 00:09:52.379 --> 00:09:52.389 align:start position:0% thing is that we are not the app 00:09:52.389 --> 00:09:55.350 align:start position:0% thing is that we are not the app specific<00:09:52.959> size<00:09:53.290> change<00:09:53.529> so<00:09:53.920> we<00:09:54.670> have<00:09:54.879> like<00:09:55.060> one 00:09:55.350 --> 00:09:55.360 align:start position:0% specific size change so we have like one 00:09:55.360 --> 00:09:57.090 align:start position:0% specific size change so we have like one public<00:09:55.750> side<00:09:55.930> chains<00:09:56.199> which<00:09:56.559> actually 00:09:57.090 --> 00:09:57.100 align:start position:0% public side chains which actually 00:09:57.100 --> 00:09:59.670 align:start position:0% public side chains which actually provides<00:09:57.519> you<00:09:58.139> composability<00:09:59.139> and<00:09:59.559> the 00:09:59.670 --> 00:09:59.680 align:start position:0% provides you composability and the 00:09:59.680 --> 00:10:01.290 align:start position:0% provides you composability and the network<00:10:00.009> effect<00:10:00.370> if<00:10:00.579> you<00:10:00.759> if<00:10:01.089> you<00:10:01.269> are 00:10:01.290 --> 00:10:01.300 align:start position:0% network effect if you if you are 00:10:01.300 --> 00:10:04.619 align:start position:0% network effect if you if you are building<00:10:02.110> on<00:10:02.500> layer<00:10:02.829> two<00:10:03.129> so<00:10:03.699> basically<00:10:04.300> let's 00:10:04.619 --> 00:10:04.629 align:start position:0% building on layer two so basically let's 00:10:04.629 --> 00:10:06.569 align:start position:0% building on layer two so basically let's say<00:10:04.689> if<00:10:04.899> you<00:10:05.050> have<00:10:05.259> an<00:10:05.439> app<00:10:05.680> specific<00:10:06.430> side 00:10:06.569 --> 00:10:06.579 align:start position:0% say if you have an app specific side 00:10:06.579 --> 00:10:08.280 align:start position:0% say if you have an app specific side chain<00:10:06.790> and<00:10:06.819> you<00:10:07.480> want<00:10:07.660> to<00:10:07.750> interact<00:10:08.079> with 00:10:08.280 --> 00:10:08.290 align:start position:0% chain and you want to interact with 00:10:08.290 --> 00:10:10.920 align:start position:0% chain and you want to interact with multiple<00:10:08.439> multiple<00:10:09.220> DAP<00:10:09.550> multiple<00:10:10.449> contracts 00:10:10.920 --> 00:10:10.930 align:start position:0% multiple multiple DAP multiple contracts 00:10:10.930 --> 00:10:14.280 align:start position:0% multiple multiple DAP multiple contracts like<00:10:11.199> defy<00:10:11.620> systems<00:10:12.069> you<00:10:12.670> need<00:10:12.819> to<00:10:13.259> make<00:10:14.259> a 00:10:14.280 --> 00:10:14.290 align:start position:0% like defy systems you need to make a 00:10:14.290 --> 00:10:16.019 align:start position:0% like defy systems you need to make a transactions<00:10:14.920> on<00:10:15.100> the<00:10:15.129> different<00:10:15.519> shard<00:10:15.730> or 00:10:16.019 --> 00:10:16.029 align:start position:0% transactions on the different shard or 00:10:16.029 --> 00:10:18.329 align:start position:0% transactions on the different shard or different<00:10:16.449> a<00:10:16.569> different<00:10:16.899> chain<00:10:17.110> to<00:10:17.680> make<00:10:18.189> this 00:10:18.329 --> 00:10:18.339 align:start position:0% different a different chain to make this 00:10:18.339 --> 00:10:21.090 align:start position:0% different a different chain to make this work<00:10:18.550> but<00:10:19.149> here<00:10:19.480> we<00:10:20.139> provide<00:10:20.860> like 00:10:21.090 --> 00:10:21.100 align:start position:0% work but here we provide like 00:10:21.100 --> 00:10:23.429 align:start position:0% work but here we provide like composability<00:10:21.550> out-of-the-box<00:10:22.389> and<00:10:22.750> these 00:10:23.429 --> 00:10:23.439 align:start position:0% composability out-of-the-box and these 00:10:23.439 --> 00:10:24.929 align:start position:0% composability out-of-the-box and these systems<00:10:23.860> actually<00:10:24.069> works<00:10:24.550> pretty<00:10:24.759> well 00:10:24.929 --> 00:10:24.939 align:start position:0% systems actually works pretty well 00:10:24.939 --> 00:10:28.139 align:start position:0% systems actually works pretty well because<00:10:25.870> it<00:10:26.379> derives<00:10:27.279> the<00:10:27.399> security<00:10:27.850> from<00:10:28.059> the 00:10:28.139 --> 00:10:28.149 align:start position:0% because it derives the security from the 00:10:28.149 --> 00:10:29.639 align:start position:0% because it derives the security from the etherium<00:10:28.569> if<00:10:28.959> something<00:10:29.259> goes<00:10:29.410> wrong<00:10:29.500> right 00:10:29.639 --> 00:10:29.649 align:start position:0% etherium if something goes wrong right 00:10:29.649 --> 00:10:33.449 align:start position:0% etherium if something goes wrong right so<00:10:30.279> for<00:10:30.970> security<00:10:31.290> hmm<00:10:32.290> is<00:10:32.379> there<00:10:32.589> and<00:10:32.920> we<00:10:33.430> just 00:10:33.449 --> 00:10:33.459 align:start position:0% so for security hmm is there and we just 00:10:33.459 --> 00:10:35.790 align:start position:0% so for security hmm is there and we just provide<00:10:33.910> a<00:10:33.939> partial<00:10:34.269> partial<00:10:35.139> confirmation 00:10:35.790 --> 00:10:35.800 align:start position:0% provide a partial partial confirmation 00:10:35.800 --> 00:10:39.299 align:start position:0% provide a partial partial confirmation directly<00:10:36.519> and<00:10:37.589> after<00:10:38.589> after<00:10:38.860> after<00:10:38.980> five 00:10:39.299 --> 00:10:39.309 align:start position:0% directly and after after after five 00:10:39.309 --> 00:10:40.980 align:start position:0% directly and after after after five minutes<00:10:39.579> or<00:10:39.670> so<00:10:39.850> you<00:10:39.879> get<00:10:40.360> this<00:10:40.569> simple 00:10:40.980 --> 00:10:40.990 align:start position:0% minutes or so you get this simple 00:10:40.990 --> 00:10:44.340 align:start position:0% minutes or so you get this simple finality<00:10:41.709> after<00:10:42.449> after<00:10:43.449> plasma<00:10:43.870> checkpoints 00:10:44.340 --> 00:10:44.350 align:start position:0% finality after after plasma checkpoints 00:10:44.350 --> 00:10:47.129 align:start position:0% finality after after plasma checkpoints goes<00:10:44.559> and<00:10:44.920> the<00:10:45.069> theorem<00:10:45.339> chain<00:10:45.579> so<00:10:46.569> those<00:10:46.779> kind 00:10:47.129 --> 00:10:47.139 align:start position:0% goes and the theorem chain so those kind 00:10:47.139 --> 00:10:50.340 align:start position:0% goes and the theorem chain so those kind of<00:10:47.259> tweaks<00:10:47.559> Antiques<00:10:47.920> help<00:10:48.879> us<00:10:49.059> know<00:10:49.660> make<00:10:50.319> it 00:10:50.340 --> 00:10:50.350 align:start position:0% of tweaks Antiques help us know make it 00:10:50.350 --> 00:10:53.610 align:start position:0% of tweaks Antiques help us know make it the<00:10:51.189> whole<00:10:51.399> system<00:10:51.610> smooth<00:10:52.209> and<00:10:52.449> for<00:10:53.079> for<00:10:53.529> of 00:10:53.610 --> 00:10:53.620 align:start position:0% the whole system smooth and for for of 00:10:53.620 --> 00:10:57.760 align:start position:0% the whole system smooth and for for of course<00:10:53.649> our<00:10:54.069> our<00:10:54.339> our<00:10:54.839> users<00:10:55.839> and<00:10:56.050> developers 00:10:57.760 --> 00:10:57.770 align:start position:0% course our our our users and developers 00:10:57.770 --> 00:11:01.330 align:start position:0% course our our our users and developers so<00:10:58.340> in<00:10:59.120> this<00:10:59.330> whole<00:10:59.390> whole<00:11:00.230> system<00:11:00.680> what<00:11:00.920> about 00:11:01.330 --> 00:11:01.340 align:start position:0% so in this whole whole system what about 00:11:01.340 --> 00:11:03.970 align:start position:0% so in this whole whole system what about end<00:11:01.640> users<00:11:01.940> right<00:11:02.180> how<00:11:02.480> and<00:11:02.960> users<00:11:03.560> actually 00:11:03.970 --> 00:11:03.980 align:start position:0% end users right how and users actually 00:11:03.980 --> 00:11:06.610 align:start position:0% end users right how and users actually interact<00:11:04.340> with<00:11:04.570> multiple<00:11:05.570> change<00:11:06.050> so<00:11:06.260> as<00:11:06.470> a 00:11:06.610 --> 00:11:06.620 align:start position:0% interact with multiple change so as a 00:11:06.620 --> 00:11:09.490 align:start position:0% interact with multiple change so as a layer<00:11:06.860> two<00:11:07.100> we<00:11:07.910> have<00:11:08.210> a<00:11:08.510> problem<00:11:09.020> with 00:11:09.490 --> 00:11:09.500 align:start position:0% layer two we have a problem with 00:11:09.500 --> 00:11:12.490 align:start position:0% layer two we have a problem with interacting<00:11:10.250> with<00:11:10.640> multiple<00:11:10.880> chains<00:11:11.420> in<00:11:12.170> one 00:11:12.490 --> 00:11:12.500 align:start position:0% interacting with multiple chains in one 00:11:12.500 --> 00:11:15.280 align:start position:0% interacting with multiple chains in one one<00:11:12.920> one<00:11:13.190> screen<00:11:13.580> right<00:11:13.760> so<00:11:14.240> if<00:11:14.540> you<00:11:14.750> use<00:11:15.020> kind 00:11:15.280 --> 00:11:15.290 align:start position:0% one one screen right so if you use kind 00:11:15.290 --> 00:11:17.380 align:start position:0% one one screen right so if you use kind of<00:11:15.410> you<00:11:15.770> know<00:11:15.890> use<00:11:16.280> meta<00:11:16.520> mask<00:11:16.820> you<00:11:17.150> need<00:11:17.270> to 00:11:17.380 --> 00:11:17.390 align:start position:0% of you know use meta mask you need to 00:11:17.390 --> 00:11:20.500 align:start position:0% of you know use meta mask you need to change<00:11:17.690> your<00:11:18.250> networks<00:11:19.250> or<00:11:19.610> your<00:11:19.670> user<00:11:20.030> has<00:11:20.150> to 00:11:20.500 --> 00:11:20.510 align:start position:0% change your networks or your user has to 00:11:20.510 --> 00:11:23.170 align:start position:0% change your networks or your user has to change<00:11:20.810> your<00:11:21.020> networks<00:11:21.400> very<00:11:22.400> frequently<00:11:22.940> so 00:11:23.170 --> 00:11:23.180 align:start position:0% change your networks very frequently so 00:11:23.180 --> 00:11:25.600 align:start position:0% change your networks very frequently so let<00:11:23.300> us<00:11:23.330> say<00:11:23.510> if<00:11:24.320> I<00:11:24.500> want<00:11:24.680> to<00:11:24.770> move<00:11:24.980> my<00:11:25.010> tokens 00:11:25.600 --> 00:11:25.610 align:start position:0% let us say if I want to move my tokens 00:11:25.610 --> 00:11:28.450 align:start position:0% let us say if I want to move my tokens from<00:11:25.820> the<00:11:26.320> ATM<00:11:27.320> to<00:11:27.470> layer<00:11:27.650> two<00:11:27.890> I<00:11:28.130> need<00:11:28.340> to 00:11:28.450 --> 00:11:28.460 align:start position:0% from the ATM to layer two I need to 00:11:28.460 --> 00:11:30.820 align:start position:0% from the ATM to layer two I need to deposit<00:11:28.820> I<00:11:29.240> make<00:11:29.600> a<00:11:29.690> deposit<00:11:29.930> I<00:11:30.230> need<00:11:30.380> to<00:11:30.440> make 00:11:30.820 --> 00:11:30.830 align:start position:0% deposit I make a deposit I need to make 00:11:30.830 --> 00:11:33.580 align:start position:0% deposit I make a deposit I need to make a<00:11:30.860> deposit<00:11:31.130> transaction<00:11:31.720> etherium<00:11:32.720> and<00:11:32.900> then 00:11:33.580 --> 00:11:33.590 align:start position:0% a deposit transaction etherium and then 00:11:33.590 --> 00:11:35.560 align:start position:0% a deposit transaction etherium and then after<00:11:33.950> that<00:11:34.070> I<00:11:34.310> can<00:11:34.460> make<00:11:34.640> transaction<00:11:35.210> on<00:11:35.360> the 00:11:35.560 --> 00:11:35.570 align:start position:0% after that I can make transaction on the 00:11:35.570 --> 00:11:38.410 align:start position:0% after that I can make transaction on the layer<00:11:35.750> two<00:11:35.930> right<00:11:36.260> but<00:11:37.160> here<00:11:37.460> let's<00:11:38.180> say<00:11:38.300> if 00:11:38.410 --> 00:11:38.420 align:start position:0% layer two right but here let's say if 00:11:38.420 --> 00:11:39.670 align:start position:0% layer two right but here let's say if you<00:11:38.540> are<00:11:38.660> using<00:11:38.840> meta<00:11:39.050> maths<00:11:39.350> or<00:11:39.470> something 00:11:39.670 --> 00:11:39.680 align:start position:0% you are using meta maths or something 00:11:39.680 --> 00:11:41.830 align:start position:0% you are using meta maths or something like<00:11:39.770> that<00:11:39.950> you<00:11:40.430> need<00:11:40.640> to<00:11:40.790> make<00:11:41.000> sure<00:11:41.030> you<00:11:41.750> know 00:11:41.830 --> 00:11:41.840 align:start position:0% like that you need to make sure you know 00:11:41.840 --> 00:11:45.040 align:start position:0% like that you need to make sure you know you<00:11:42.230> have<00:11:42.470> to<00:11:42.590> change<00:11:43.220> your<00:11:43.490> networks<00:11:44.240> once 00:11:45.040 --> 00:11:45.050 align:start position:0% you have to change your networks once 00:11:45.050 --> 00:11:48.160 align:start position:0% you have to change your networks once you<00:11:45.200> make<00:11:45.440> a<00:11:45.470> deposit<00:11:45.650> but<00:11:46.460> for<00:11:47.060> that<00:11:47.300> what<00:11:48.020> we 00:11:48.160 --> 00:11:48.170 align:start position:0% you make a deposit but for that what we 00:11:48.170 --> 00:11:51.270 align:start position:0% you make a deposit but for that what we are<00:11:48.260> doing<00:11:48.410> is<00:11:48.620> we<00:11:48.950> are<00:11:48.980> we<00:11:49.850> are<00:11:49.880> actually 00:11:51.270 --> 00:11:51.280 align:start position:0% are doing is we are we are actually 00:11:51.280 --> 00:11:53.350 align:start position:0% are doing is we are we are actually integrating<00:11:52.280> wallet<00:11:52.610> connect<00:11:52.880> protocol 00:11:53.350 --> 00:11:53.360 align:start position:0% integrating wallet connect protocol 00:11:53.360 --> 00:11:57.250 align:start position:0% integrating wallet connect protocol which<00:11:54.230> helped<00:11:54.650> us<00:11:54.860> to<00:11:55.360> was<00:11:56.360> which<00:11:56.630> help<00:11:56.900> us<00:11:56.990> our 00:11:57.250 --> 00:11:57.260 align:start position:0% which helped us to was which help us our 00:11:57.260 --> 00:11:59.770 align:start position:0% which helped us to was which help us our users<00:11:57.800> to<00:11:58.460> interact<00:11:58.880> with<00:11:59.120> multiple<00:11:59.300> chains 00:11:59.770 --> 00:11:59.780 align:start position:0% users to interact with multiple chains 00:11:59.780 --> 00:12:02.320 align:start position:0% users to interact with multiple chains directly<00:12:00.680> so<00:12:00.950> people<00:12:01.430> users<00:12:01.910> don't<00:12:02.090> have<00:12:02.210> to 00:12:02.320 --> 00:12:02.330 align:start position:0% directly so people users don't have to 00:12:02.330 --> 00:12:05.140 align:start position:0% directly so people users don't have to worry<00:12:02.720> about<00:12:03.020> multiple<00:12:03.290> chains<00:12:04.150> multiple 00:12:05.140 --> 00:12:05.150 align:start position:0% worry about multiple chains multiple 00:12:05.150 --> 00:12:08.290 align:start position:0% worry about multiple chains multiple deposits<00:12:05.420> or<00:12:05.900> exit<00:12:06.230> anything<00:12:07.040> right<00:12:07.300> also 00:12:08.290 --> 00:12:08.300 align:start position:0% deposits or exit anything right also 00:12:08.300 --> 00:12:11.920 align:start position:0% deposits or exit anything right also when<00:12:09.110> we<00:12:09.230> talk<00:12:09.260> about<00:12:09.880> simple<00:12:10.880> public<00:12:11.750> side 00:12:11.920 --> 00:12:11.930 align:start position:0% when we talk about simple public side 00:12:11.930 --> 00:12:14.770 align:start position:0% when we talk about simple public side chain<00:12:12.140> or<00:12:12.500> public<00:12:13.010> one<00:12:13.370> public<00:12:13.730> chain<00:12:13.940> people 00:12:14.770 --> 00:12:14.780 align:start position:0% chain or public one public chain people 00:12:14.780 --> 00:12:17.350 align:start position:0% chain or public one public chain people can<00:12:15.080> actually<00:12:15.260> use<00:12:15.770> enters<00:12:16.730> multiple 00:12:17.350 --> 00:12:17.360 align:start position:0% can actually use enters multiple 00:12:17.360 --> 00:12:20.470 align:start position:0% can actually use enters multiple multiple<00:12:18.020> contracts<00:12:18.650> when<00:12:18.980> they<00:12:19.130> want<00:12:19.310> if<00:12:20.240> you 00:12:20.470 --> 00:12:20.480 align:start position:0% multiple contracts when they want if you 00:12:20.480 --> 00:12:23.920 align:start position:0% multiple contracts when they want if you use<00:12:20.690> a<00:12:21.050> simple<00:12:21.700> simple<00:12:22.700> app<00:12:23.210> specifics<00:12:23.720> change 00:12:23.920 --> 00:12:23.930 align:start position:0% use a simple simple app specifics change 00:12:23.930 --> 00:12:26.680 align:start position:0% use a simple simple app specifics change you<00:12:24.350> have<00:12:24.620> to<00:12:24.800> your<00:12:25.070> user<00:12:25.280> help<00:12:25.580> to<00:12:25.700> move<00:12:25.970> one 00:12:26.680 --> 00:12:26.690 align:start position:0% you have to your user help to move one 00:12:26.690 --> 00:12:29.410 align:start position:0% you have to your user help to move one chain<00:12:26.930> to<00:12:27.140> second<00:12:27.740> of<00:12:28.040> the<00:12:28.130> chain<00:12:28.340> to<00:12:28.700> test 00:12:29.410 --> 00:12:29.420 align:start position:0% chain to second of the chain to test 00:12:29.420 --> 00:12:32.770 align:start position:0% chain to second of the chain to test your<00:12:29.740> test<00:12:30.740> your<00:12:30.980> applications<00:12:31.760> but<00:12:32.570> here 00:12:32.770 --> 00:12:32.780 align:start position:0% your test your applications but here 00:12:32.780 --> 00:12:37.360 align:start position:0% your test your applications but here your<00:12:33.410> user<00:12:33.590> can<00:12:33.860> anytime<00:12:34.840> trade<00:12:35.840> or<00:12:36.370> interact 00:12:37.360 --> 00:12:37.370 align:start position:0% your user can anytime trade or interact 00:12:37.370 --> 00:12:41.470 align:start position:0% your user can anytime trade or interact with<00:12:37.490> multiple<00:12:37.640> contracts<00:12:39.490> it<00:12:40.490> also<00:12:41.060> helped 00:12:41.470 --> 00:12:41.480 align:start position:0% with multiple contracts it also helped 00:12:41.480 --> 00:12:45.850 align:start position:0% with multiple contracts it also helped post<00:12:42.320> able<00:12:42.590> coins<00:12:42.890> on<00:12:43.340> the<00:12:43.610> chain<00:12:43.880> too<00:12:44.710> so<00:12:45.710> for 00:12:45.850 --> 00:12:45.860 align:start position:0% post able coins on the chain too so for 00:12:45.860 --> 00:12:48.700 align:start position:0% post able coins on the chain too so for users<00:12:46.250> and<00:12:46.640> apps<00:12:46.970> can<00:12:47.180> use<00:12:47.360> use<00:12:47.870> stable<00:12:48.410> coins 00:12:48.700 --> 00:12:48.710 align:start position:0% users and apps can use use stable coins 00:12:48.710 --> 00:12:51.700 align:start position:0% users and apps can use use stable coins in<00:12:49.250> payments<00:12:49.970> in<00:12:50.120> disinterred<00:12:50.870> exchanges<00:12:51.380> and 00:12:51.700 --> 00:12:51.710 align:start position:0% in payments in disinterred exchanges and 00:12:51.710 --> 00:12:53.950 align:start position:0% in payments in disinterred exchanges and you<00:12:51.920> know<00:12:52.010> multiple<00:12:52.520> at<00:12:52.910> multiple<00:12:53.300> ways<00:12:53.690> so 00:12:53.950 --> 00:12:53.960 align:start position:0% you know multiple at multiple ways so 00:12:53.960 --> 00:12:58.060 align:start position:0% you know multiple at multiple ways so those<00:12:54.800> those<00:12:55.250> kind<00:12:55.550> of<00:12:55.640> mechanism<00:12:56.330> we<00:12:56.660> are<00:12:57.070> we 00:12:58.060 --> 00:12:58.070 align:start position:0% those those kind of mechanism we are we 00:12:58.070 --> 00:13:01.450 align:start position:0% those those kind of mechanism we are we are<00:12:58.100> providing<00:12:59.200> for<00:13:00.200> our<00:13:00.260> end<00:13:00.590> users<00:13:00.920> so<00:13:00.950> also 00:13:01.450 --> 00:13:01.460 align:start position:0% are providing for our end users so also 00:13:01.460 --> 00:13:05.410 align:start position:0% are providing for our end users so also we<00:13:01.910> are<00:13:02.120> working<00:13:02.570> on<00:13:03.230> multiple<00:13:03.760> widgets<00:13:04.760> who 00:13:05.410 --> 00:13:05.420 align:start position:0% we are working on multiple widgets who 00:13:05.420 --> 00:13:08.050 align:start position:0% we are working on multiple widgets who developers<00:13:06.320> can<00:13:06.590> directly<00:13:06.920> integrate<00:13:07.280> for 00:13:08.050 --> 00:13:08.060 align:start position:0% developers can directly integrate for 00:13:08.060 --> 00:13:10.780 align:start position:0% developers can directly integrate for the<00:13:08.150> users<00:13:08.570> so<00:13:09.080> so<00:13:09.920> again<00:13:10.130> they<00:13:10.310> don't<00:13:10.430> have<00:13:10.610> to 00:13:10.780 --> 00:13:10.790 align:start position:0% the users so so again they don't have to 00:13:10.790 --> 00:13:11.990 align:start position:0% the users so so again they don't have to make 00:13:11.990 --> 00:13:12.000 align:start position:0% make 00:13:12.000 --> 00:13:15.500 align:start position:0% make deposits<00:13:12.690> and<00:13:12.960> exceeds<00:13:14.150> transactions<00:13:15.150> on<00:13:15.360> the 00:13:15.500 --> 00:13:15.510 align:start position:0% deposits and exceeds transactions on the 00:13:15.510 --> 00:13:19.400 align:start position:0% deposits and exceeds transactions on the on<00:13:15.779> the<00:13:15.900> layer<00:13:16.020> to<00:13:16.080> so<00:13:17.070> mostly<00:13:17.990> of<00:13:18.990> a<00:13:19.080> system 00:13:19.400 --> 00:13:19.410 align:start position:0% on the layer to so mostly of a system 00:13:19.410 --> 00:13:22.360 align:start position:0% on the layer to so mostly of a system like<00:13:19.440> if<00:13:19.980> such<00:13:20.610> kind<00:13:20.820> of<00:13:20.880> system<00:13:21.210> can<00:13:21.900> make 00:13:22.360 --> 00:13:22.370 align:start position:0% like if such kind of system can make 00:13:22.370 --> 00:13:25.160 align:start position:0% like if such kind of system can make users<00:13:23.370> and<00:13:23.640> developers<00:13:23.790> life<00:13:24.150> easy<00:13:24.330> and<00:13:24.690> for 00:13:25.160 --> 00:13:25.170 align:start position:0% users and developers life easy and for 00:13:25.170 --> 00:13:28.070 align:start position:0% users and developers life easy and for that<00:13:25.850> developers<00:13:26.850> can<00:13:27.120> actually<00:13:27.600> build<00:13:27.810> new 00:13:28.070 --> 00:13:28.080 align:start position:0% that developers can actually build new 00:13:28.080 --> 00:13:32.420 align:start position:0% that developers can actually build new markets<00:13:28.589> and<00:13:28.970> kind<00:13:29.970> of<00:13:30.260> defy<00:13:31.260> games<00:13:31.770> new<00:13:32.220> kind 00:13:32.420 --> 00:13:32.430 align:start position:0% markets and kind of defy games new kind 00:13:32.430 --> 00:13:35.050 align:start position:0% markets and kind of defy games new kind of<00:13:32.490> defy<00:13:33.060> which<00:13:33.300> actually<00:13:33.660> works<00:13:34.500> multiple 00:13:35.050 --> 00:13:35.060 align:start position:0% of defy which actually works multiple 00:13:35.060 --> 00:13:38.450 align:start position:0% of defy which actually works multiple works<00:13:36.060> with<00:13:36.210> multiple<00:13:36.390> contracts<00:13:37.190> games<00:13:38.190> who 00:13:38.450 --> 00:13:38.460 align:start position:0% works with multiple contracts games who 00:13:38.460 --> 00:13:42.290 align:start position:0% works with multiple contracts games who can<00:13:39.270> integrate<00:13:39.600> its<00:13:40.260> say<00:13:40.380> eunice<00:13:41.250> web<00:13:41.460> or 00:13:42.290 --> 00:13:42.300 align:start position:0% can integrate its say eunice web or 00:13:42.300 --> 00:13:44.750 align:start position:0% can integrate its say eunice web or multiple<00:13:42.900> decks<00:13:43.260> ease<00:13:43.440> or<00:13:43.770> simple<00:13:44.490> other 00:13:44.750 --> 00:13:44.760 align:start position:0% multiple decks ease or simple other 00:13:44.760 --> 00:13:46.490 align:start position:0% multiple decks ease or simple other other<00:13:45.000> games<00:13:45.270> as<00:13:45.450> well<00:13:45.660> other<00:13:45.870> games<00:13:46.140> contract 00:13:46.490 --> 00:13:46.500 align:start position:0% other games as well other games contract 00:13:46.500 --> 00:13:49.610 align:start position:0% other games as well other games contract as<00:13:46.589> well<00:13:46.770> and<00:13:47.120> so<00:13:48.120> yeah<00:13:48.240> those<00:13:48.839> zones<00:13:49.260> get<00:13:49.410> rid 00:13:49.610 --> 00:13:49.620 align:start position:0% as well and so yeah those zones get rid 00:13:49.620 --> 00:13:52.760 align:start position:0% as well and so yeah those zones get rid of<00:13:49.650> market<00:13:50.580> and<00:13:51.080> existing<00:13:52.080> market<00:13:52.440> we<00:13:52.620> can 00:13:52.760 --> 00:13:52.770 align:start position:0% of market and existing market we can 00:13:52.770 --> 00:13:55.250 align:start position:0% of market and existing market we can actually<00:13:53.070> target<00:13:53.250> on<00:13:53.640> when<00:13:54.330> we<00:13:54.450> have<00:13:54.660> such 00:13:55.250 --> 00:13:55.260 align:start position:0% actually target on when we have such 00:13:55.260 --> 00:13:59.200 align:start position:0% actually target on when we have such kind<00:13:55.380> of<00:13:55.529> system<00:13:56.420> so<00:13:57.420> so<00:13:57.900> yeah<00:13:57.990> yeah<00:13:58.560> and 00:13:59.200 --> 00:13:59.210 align:start position:0% kind of system so so yeah yeah and 00:13:59.210 --> 00:14:10.770 align:start position:0% kind of system so so yeah yeah and that's<00:14:00.210> it<00:14:00.360> thank<00:14:00.930> you 00:14:10.770 --> 00:14:10.780 align:start position:0% 00:14:10.780 --> 00:14:12.840 align:start position:0% you