WEBVTT Kind: captions Language: en 00:00:00.000 --> 00:00:04.350 align:start position:0% foreign 00:00:04.350 --> 00:00:04.360 align:start position:0% 00:00:04.360 --> 00:00:13.690 align:start position:0% [Music] 00:00:13.690 --> 00:00:13.700 align:start position:0% 00:00:13.700 --> 00:00:16.849 align:start position:0% and<00:00:14.700> I'm<00:00:15.179> the<00:00:15.360> founder<00:00:15.719> and<00:00:16.139> CEO<00:00:16.500> of<00:00:16.619> Empire 00:00:16.849 --> 00:00:16.859 align:start position:0% and I'm the founder and CEO of Empire 00:00:16.859 --> 00:00:20.029 align:start position:0% and I'm the founder and CEO of Empire wallet<00:00:17.900> and<00:00:18.900> I'm<00:00:19.080> going<00:00:19.260> to<00:00:19.500> tell<00:00:19.680> you<00:00:19.859> about 00:00:20.029 --> 00:00:20.039 align:start position:0% wallet and I'm going to tell you about 00:00:20.039 --> 00:00:22.010 align:start position:0% wallet and I'm going to tell you about the<00:00:20.520> future<00:00:20.640> of<00:00:20.820> ethereum<00:00:21.300> wallets<00:00:21.720> and 00:00:22.010 --> 00:00:22.020 align:start position:0% the future of ethereum wallets and 00:00:22.020 --> 00:00:25.609 align:start position:0% the future of ethereum wallets and ethereum<00:00:22.439> ux<00:00:23.240> and<00:00:24.240> two<00:00:24.480> technologies<00:00:25.019> are<00:00:25.380> at 00:00:25.609 --> 00:00:25.619 align:start position:0% ethereum ux and two technologies are at 00:00:25.619 --> 00:00:28.070 align:start position:0% ethereum ux and two technologies are at the<00:00:25.859> core<00:00:26.340> of<00:00:26.580> this<00:00:26.820> and<00:00:27.240> that's<00:00:27.599> a<00:00:27.900> smart 00:00:28.070 --> 00:00:28.080 align:start position:0% the core of this and that's a smart 00:00:28.080 --> 00:00:30.170 align:start position:0% the core of this and that's a smart contract<00:00:28.500> wallets<00:00:28.920> kind<00:00:29.460> of<00:00:29.580> also<00:00:29.880> known<00:00:30.000> as 00:00:30.170 --> 00:00:30.180 align:start position:0% contract wallets kind of also known as 00:00:30.180 --> 00:00:32.930 align:start position:0% contract wallets kind of also known as account<00:00:30.359> obstructions<00:00:31.140> and<00:00:31.679> MPC<00:00:32.460> otherwise 00:00:32.930 --> 00:00:32.940 align:start position:0% account obstructions and MPC otherwise 00:00:32.940 --> 00:00:35.810 align:start position:0% account obstructions and MPC otherwise known<00:00:33.180> as<00:00:33.360> smooth<00:00:33.600> party<00:00:33.899> computation<00:00:34.820> and 00:00:35.810 --> 00:00:35.820 align:start position:0% known as smooth party computation and 00:00:35.820 --> 00:00:37.190 align:start position:0% known as smooth party computation and sometimes<00:00:36.120> referred<00:00:36.540> to<00:00:36.600> as<00:00:36.719> threshold 00:00:37.190 --> 00:00:37.200 align:start position:0% sometimes referred to as threshold 00:00:37.200 --> 00:00:39.770 align:start position:0% sometimes referred to as threshold signatures<00:00:37.800> in<00:00:38.460> this<00:00:38.579> case<00:00:38.760> the<00:00:39.360> question<00:00:39.480> is 00:00:39.770 --> 00:00:39.780 align:start position:0% signatures in this case the question is 00:00:39.780 --> 00:00:41.990 align:start position:0% signatures in this case the question is can<00:00:40.020> self<00:00:40.320> custody<00:00:40.739> be<00:00:41.100> the<00:00:41.340> future<00:00:41.520> for<00:00:41.879> the 00:00:41.990 --> 00:00:42.000 align:start position:0% can self custody be the future for the 00:00:42.000 --> 00:00:43.850 align:start position:0% can self custody be the future for the next<00:00:42.120> billion<00:00:42.540> users<00:00:42.899> how<00:00:43.140> can<00:00:43.320> we<00:00:43.440> onboard 00:00:43.850 --> 00:00:43.860 align:start position:0% next billion users how can we onboard 00:00:43.860 --> 00:00:46.430 align:start position:0% next billion users how can we onboard the<00:00:44.100> next<00:00:44.219> billion<00:00:44.640> users<00:00:45.000> and<00:00:45.840> there<00:00:46.079> is<00:00:46.260> a 00:00:46.430 --> 00:00:46.440 align:start position:0% the next billion users and there is a 00:00:46.440 --> 00:00:48.590 align:start position:0% the next billion users and there is a big<00:00:46.500> myth<00:00:46.920> in<00:00:47.100> the<00:00:47.280> space<00:00:47.520> that<00:00:48.059> most<00:00:48.360> people 00:00:48.590 --> 00:00:48.600 align:start position:0% big myth in the space that most people 00:00:48.600 --> 00:00:51.590 align:start position:0% big myth in the space that most people are<00:00:48.899> not<00:00:49.020> ready<00:00:49.320> for<00:00:49.680> self-custody<00:00:50.420> but<00:00:51.420> the 00:00:51.590 --> 00:00:51.600 align:start position:0% are not ready for self-custody but the 00:00:51.600 --> 00:00:53.990 align:start position:0% are not ready for self-custody but the actual<00:00:51.780> reality<00:00:52.320> is<00:00:52.980> that<00:00:53.520> most 00:00:53.990 --> 00:00:54.000 align:start position:0% actual reality is that most 00:00:54.000 --> 00:00:56.389 align:start position:0% actual reality is that most self-custodial<00:00:54.780> wallets<00:00:55.260> are<00:00:55.559> not<00:00:55.739> ready<00:00:56.039> for 00:00:56.389 --> 00:00:56.399 align:start position:0% self-custodial wallets are not ready for 00:00:56.399 --> 00:00:59.510 align:start position:0% self-custodial wallets are not ready for the<00:00:56.699> users<00:00:57.000> not<00:00:57.239> the<00:00:57.480> other<00:00:57.600> way<00:00:57.780> around 00:00:59.510 --> 00:00:59.520 align:start position:0% the users not the other way around 00:00:59.520 --> 00:01:02.330 align:start position:0% the users not the other way around uh<00:01:00.420> and<00:01:00.840> uh<00:01:01.020> I'm<00:01:01.320> guessing<00:01:01.620> uh<00:01:01.800> can<00:01:01.980> I<00:01:02.160> get<00:01:02.219> a 00:01:02.330 --> 00:01:02.340 align:start position:0% uh and uh I'm guessing uh can I get a 00:01:02.340 --> 00:01:03.650 align:start position:0% uh and uh I'm guessing uh can I get a show<00:01:02.460> of<00:01:02.640> hands<00:01:03.000> who<00:01:03.180> saw<00:01:03.300> the<00:01:03.539> account 00:01:03.650 --> 00:01:03.660 align:start position:0% show of hands who saw the account 00:01:03.660 --> 00:01:05.630 align:start position:0% show of hands who saw the account obstruction<00:01:04.019> panel<00:01:04.559> yesterday<00:01:04.739> with<00:01:05.460> uh 00:01:05.630 --> 00:01:05.640 align:start position:0% obstruction panel yesterday with uh 00:01:05.640 --> 00:01:07.670 align:start position:0% obstruction panel yesterday with uh vitalik<00:01:06.240> cool<00:01:06.720> yeah 00:01:07.670 --> 00:01:07.680 align:start position:0% vitalik cool yeah 00:01:07.680 --> 00:01:09.710 align:start position:0% vitalik cool yeah um<00:01:07.740> so<00:01:07.920> you<00:01:08.100> all<00:01:08.220> know<00:01:08.400> that<00:01:08.580> sit<00:01:08.939> phrases<00:01:09.360> are 00:01:09.710 --> 00:01:09.720 align:start position:0% um so you all know that sit phrases are 00:01:09.720 --> 00:01:11.750 align:start position:0% um so you all know that sit phrases are absolutely<00:01:10.140> terrible<00:01:10.619> and<00:01:11.100> there<00:01:11.400> are<00:01:11.520> an 00:01:11.750 --> 00:01:11.760 align:start position:0% absolutely terrible and there are an 00:01:11.760 --> 00:01:13.969 align:start position:0% absolutely terrible and there are an absolutely<00:01:12.060> terrible<00:01:12.420> way<00:01:12.720> of 00:01:13.969 --> 00:01:13.979 align:start position:0% absolutely terrible way of 00:01:13.979 --> 00:01:16.490 align:start position:0% absolutely terrible way of um<00:01:14.040> backing<00:01:14.520> up<00:01:14.640> your<00:01:14.880> private<00:01:15.240> key<00:01:15.420> uh<00:01:16.260> and<00:01:16.380> we 00:01:16.490 --> 00:01:16.500 align:start position:0% um backing up your private key uh and we 00:01:16.500 --> 00:01:17.870 align:start position:0% um backing up your private key uh and we have<00:01:16.619> so<00:01:16.799> many<00:01:16.920> problems<00:01:17.340> in<00:01:17.520> the<00:01:17.640> industry 00:01:17.870 --> 00:01:17.880 align:start position:0% have so many problems in the industry 00:01:17.880 --> 00:01:20.390 align:start position:0% have so many problems in the industry with<00:01:18.180> compromised<00:01:18.780> Keys<00:01:19.320> software<00:01:19.979> wallets 00:01:20.390 --> 00:01:20.400 align:start position:0% with compromised Keys software wallets 00:01:20.400 --> 00:01:22.609 align:start position:0% with compromised Keys software wallets being<00:01:20.580> vulnerable<00:01:21.000> to<00:01:21.240> malware<00:01:21.720> and<00:01:22.259> to<00:01:22.439> come 00:01:22.609 --> 00:01:22.619 align:start position:0% being vulnerable to malware and to come 00:01:22.619 --> 00:01:25.249 align:start position:0% being vulnerable to malware and to come to<00:01:23.220> supply<00:01:23.460> chain<00:01:23.820> attacks<00:01:24.360> uh<00:01:24.960> which<00:01:25.200> is 00:01:25.249 --> 00:01:25.259 align:start position:0% to supply chain attacks uh which is 00:01:25.259 --> 00:01:27.050 align:start position:0% to supply chain attacks uh which is quite<00:01:25.439> scary<00:01:25.680> like<00:01:25.979> a<00:01:26.159> single<00:01:26.400> npm<00:01:26.820> Library 00:01:27.050 --> 00:01:27.060 align:start position:0% quite scary like a single npm Library 00:01:27.060 --> 00:01:29.450 align:start position:0% quite scary like a single npm Library can<00:01:27.659> like<00:01:28.320> completely<00:01:28.680> wreck<00:01:28.979> your<00:01:29.159> wallet 00:01:29.450 --> 00:01:29.460 align:start position:0% can like completely wreck your wallet 00:01:29.460 --> 00:01:31.730 align:start position:0% can like completely wreck your wallet security<00:01:29.900> and<00:01:30.900> of<00:01:31.080> course<00:01:31.200> you<00:01:31.380> know<00:01:31.439> we<00:01:31.560> have 00:01:31.730 --> 00:01:31.740 align:start position:0% security and of course you know we have 00:01:31.740 --> 00:01:33.710 align:start position:0% security and of course you know we have social<00:01:31.920> engineering<00:01:32.580> attacks<00:01:33.119> like<00:01:33.540> for 00:01:33.710 --> 00:01:33.720 align:start position:0% social engineering attacks like for 00:01:33.720 --> 00:01:37.190 align:start position:0% social engineering attacks like for example<00:01:33.960> with<00:01:34.259> board<00:01:34.680> dapes<00:01:35.600> and<00:01:36.600> generally 00:01:37.190 --> 00:01:37.200 align:start position:0% example with board dapes and generally 00:01:37.200 --> 00:01:40.210 align:start position:0% example with board dapes and generally all<00:01:37.619> of<00:01:37.860> those<00:01:38.159> things<00:01:38.400> can<00:01:38.700> be<00:01:38.880> solved<00:01:39.299> by 00:01:40.210 --> 00:01:40.220 align:start position:0% all of those things can be solved by 00:01:40.220 --> 00:01:44.090 align:start position:0% all of those things can be solved by multi-factor<00:01:41.220> authentication<00:01:41.900> and<00:01:42.920> on<00:01:43.920> on 00:01:44.090 --> 00:01:44.100 align:start position:0% multi-factor authentication and on on 00:01:44.100 --> 00:01:46.969 align:start position:0% multi-factor authentication and on on the<00:01:44.340> Chain<00:01:44.460> we<00:01:44.759> call<00:01:44.939> this<00:01:45.180> multisigs<00:01:46.380> and 00:01:46.969 --> 00:01:46.979 align:start position:0% the Chain we call this multisigs and 00:01:46.979 --> 00:01:49.730 align:start position:0% the Chain we call this multisigs and wire<00:01:47.280> multi-6<00:01:47.880> kind<00:01:48.119> of<00:01:48.240> a<00:01:48.360> silver<00:01:48.479> bullet<00:01:49.020> uh 00:01:49.730 --> 00:01:49.740 align:start position:0% wire multi-6 kind of a silver bullet uh 00:01:49.740 --> 00:01:51.770 align:start position:0% wire multi-6 kind of a silver bullet uh so<00:01:49.979> first<00:01:50.159> of<00:01:50.280> all<00:01:50.340> by<00:01:50.579> having<00:01:50.759> multiple<00:01:51.360> Keys 00:01:51.770 --> 00:01:51.780 align:start position:0% so first of all by having multiple Keys 00:01:51.780 --> 00:01:54.530 align:start position:0% so first of all by having multiple Keys uh<00:01:52.740> or<00:01:53.100> you<00:01:53.579> you<00:01:53.820> can<00:01:54.000> think<00:01:54.119> of<00:01:54.299> it<00:01:54.420> as 00:01:54.530 --> 00:01:54.540 align:start position:0% uh or you you can think of it as 00:01:54.540 --> 00:01:56.090 align:start position:0% uh or you you can think of it as multiple<00:01:54.899> shards<00:01:55.320> of<00:01:55.380> a<00:01:55.560> single<00:01:55.740> private<00:01:55.979> key 00:01:56.090 --> 00:01:56.100 align:start position:0% multiple shards of a single private key 00:01:56.100 --> 00:01:58.249 align:start position:0% multiple shards of a single private key but<00:01:56.280> it's<00:01:56.399> actually<00:01:56.640> multiple<00:01:57.119> Keys 00:01:58.249 --> 00:01:58.259 align:start position:0% but it's actually multiple Keys 00:01:58.259 --> 00:02:00.410 align:start position:0% but it's actually multiple Keys um<00:01:58.320> you<00:01:58.680> can<00:01:58.799> actually<00:01:59.040> onboard<00:01:59.939> users 00:02:00.410 --> 00:02:00.420 align:start position:0% um you can actually onboard users 00:02:00.420 --> 00:02:02.630 align:start position:0% um you can actually onboard users without<00:02:00.720> making<00:02:01.320> them<00:02:01.619> write<00:02:01.920> down<00:02:02.100> a<00:02:02.340> seed 00:02:02.630 --> 00:02:02.640 align:start position:0% without making them write down a seed 00:02:02.640 --> 00:02:04.550 align:start position:0% without making them write down a seed and<00:02:03.420> without<00:02:03.600> worrying<00:02:04.140> that<00:02:04.259> they<00:02:04.439> would 00:02:04.550 --> 00:02:04.560 align:start position:0% and without worrying that they would 00:02:04.560 --> 00:02:06.889 align:start position:0% and without worrying that they would lose<00:02:04.740> access<00:02:04.979> to<00:02:05.280> their<00:02:05.460> account<00:02:05.899> so 00:02:06.889 --> 00:02:06.899 align:start position:0% lose access to their account so 00:02:06.899 --> 00:02:08.990 align:start position:0% lose access to their account so basically<00:02:07.259> a<00:02:07.380> simple<00:02:07.560> example<00:02:07.979> would<00:02:08.220> be<00:02:08.399> uh 00:02:08.990 --> 00:02:09.000 align:start position:0% basically a simple example would be uh 00:02:09.000 --> 00:02:11.330 align:start position:0% basically a simple example would be uh to<00:02:09.300> have<00:02:09.420> a<00:02:09.599> key<00:02:09.720> on<00:02:09.959> your<00:02:10.080> laptop<00:02:10.380> or<00:02:10.739> ant<00:02:11.039> on 00:02:11.330 --> 00:02:11.340 align:start position:0% to have a key on your laptop or ant on 00:02:11.340 --> 00:02:13.610 align:start position:0% to have a key on your laptop or ant on your<00:02:11.459> phone<00:02:11.640> you<00:02:12.480> can<00:02:12.599> also<00:02:12.900> recover<00:02:13.319> your 00:02:13.610 --> 00:02:13.620 align:start position:0% your phone you can also recover your 00:02:13.620 --> 00:02:16.190 align:start position:0% your phone you can also recover your account<00:02:13.860> with<00:02:14.400> methods<00:02:15.239> like<00:02:15.480> social 00:02:16.190 --> 00:02:16.200 align:start position:0% account with methods like social 00:02:16.200 --> 00:02:18.530 align:start position:0% account with methods like social recovery<00:02:16.800> not<00:02:17.220> Argent<00:02:17.760> pioneered<00:02:18.300> but 00:02:18.530 --> 00:02:18.540 align:start position:0% recovery not Argent pioneered but 00:02:18.540 --> 00:02:21.110 align:start position:0% recovery not Argent pioneered but there's<00:02:18.660> also<00:02:18.900> other<00:02:19.200> ways<00:02:19.739> of<00:02:19.800> recovery<00:02:20.220> you 00:02:21.110 --> 00:02:21.120 align:start position:0% there's also other ways of recovery you 00:02:21.120 --> 00:02:22.610 align:start position:0% there's also other ways of recovery you can<00:02:21.239> also<00:02:21.480> generally<00:02:21.780> do<00:02:21.959> multi-factor 00:02:22.610 --> 00:02:22.620 align:start position:0% can also generally do multi-factor 00:02:22.620 --> 00:02:24.830 align:start position:0% can also generally do multi-factor authentication<00:02:23.160> which<00:02:24.000> is<00:02:24.180> way<00:02:24.300> more<00:02:24.480> secure 00:02:24.830 --> 00:02:24.840 align:start position:0% authentication which is way more secure 00:02:24.840 --> 00:02:27.170 align:start position:0% authentication which is way more secure and<00:02:25.020> prevents<00:02:25.379> you<00:02:25.500> from<00:02:25.680> malware<00:02:26.099> and<00:02:27.060> of 00:02:27.170 --> 00:02:27.180 align:start position:0% and prevents you from malware and of 00:02:27.180 --> 00:02:28.670 align:start position:0% and prevents you from malware and of course<00:02:27.300> you<00:02:27.480> have<00:02:27.599> resistance<00:02:28.020> to<00:02:28.200> hacks<00:02:28.560> and 00:02:28.670 --> 00:02:28.680 align:start position:0% course you have resistance to hacks and 00:02:28.680 --> 00:02:30.830 align:start position:0% course you have resistance to hacks and compromised<00:02:29.220> keys<00:02:29.580> for<00:02:30.300> example<00:02:30.480> we<00:02:30.660> have 00:02:30.830 --> 00:02:30.840 align:start position:0% compromised keys for example we have 00:02:30.840 --> 00:02:33.229 align:start position:0% compromised keys for example we have malware<00:02:31.200> on<00:02:31.440> one<00:02:31.620> of<00:02:31.680> the<00:02:31.800> devices<00:02:32.120> you<00:02:33.120> will 00:02:33.229 --> 00:02:33.239 align:start position:0% malware on one of the devices you will 00:02:33.239 --> 00:02:34.850 align:start position:0% malware on one of the devices you will not<00:02:33.360> be<00:02:33.540> that<00:02:33.780> vulnerable 00:02:34.850 --> 00:02:34.860 align:start position:0% not be that vulnerable 00:02:34.860 --> 00:02:36.470 align:start position:0% not be that vulnerable so 00:02:36.470 --> 00:02:36.480 align:start position:0% so 00:02:36.480 --> 00:02:37.850 align:start position:0% so um there<00:02:36.840> are<00:02:36.959> two<00:02:37.080> ways<00:02:37.379> to<00:02:37.500> achieve<00:02:37.739> a 00:02:37.850 --> 00:02:37.860 align:start position:0% um there are two ways to achieve a 00:02:37.860 --> 00:02:40.970 align:start position:0% um there are two ways to achieve a multicycle<00:02:38.459> on<00:02:38.940> an<00:02:39.060> evm<00:02:39.420> chain<00:02:39.620> uh<00:02:40.620> one<00:02:40.920> of 00:02:40.970 --> 00:02:40.980 align:start position:0% multicycle on an evm chain uh one of 00:02:40.980 --> 00:02:43.910 align:start position:0% multicycle on an evm chain uh one of them<00:02:41.160> is<00:02:41.819> smart<00:02:42.480> contract<00:02:42.840> wallets<00:02:43.260> and<00:02:43.680> a<00:02:43.800> lot 00:02:43.910 --> 00:02:43.920 align:start position:0% them is smart contract wallets and a lot 00:02:43.920 --> 00:02:45.050 align:start position:0% them is smart contract wallets and a lot of<00:02:43.980> you<00:02:44.160> have<00:02:44.459> heard<00:02:44.640> about<00:02:44.819> account 00:02:45.050 --> 00:02:45.060 align:start position:0% of you have heard about account 00:02:45.060 --> 00:02:46.790 align:start position:0% of you have heard about account obstructions<00:02:45.780> and<00:02:45.959> account<00:02:46.140> obstructions 00:02:46.790 --> 00:02:46.800 align:start position:0% obstructions and account obstructions 00:02:46.800 --> 00:02:48.890 align:start position:0% obstructions and account obstructions are<00:02:46.920> basically<00:02:47.220> a<00:02:47.459> way<00:02:47.640> uh<00:02:48.180> to<00:02:48.360> pave<00:02:48.540> the<00:02:48.720> way 00:02:48.890 --> 00:02:48.900 align:start position:0% are basically a way uh to pave the way 00:02:48.900 --> 00:02:51.290 align:start position:0% are basically a way uh to pave the way forward<00:02:49.080> for<00:02:49.500> smart<00:02:49.680> contract<00:02:50.099> wallets<00:02:50.519> but<00:02:50.819> I 00:02:51.290 --> 00:02:51.300 align:start position:0% forward for smart contract wallets but I 00:02:51.300 --> 00:02:53.509 align:start position:0% forward for smart contract wallets but I prefer<00:02:51.660> to<00:02:51.780> call<00:02:51.959> this<00:02:52.200> like<00:02:52.620> smart<00:02:53.040> smart 00:02:53.509 --> 00:02:53.519 align:start position:0% prefer to call this like smart smart 00:02:53.519 --> 00:02:55.130 align:start position:0% prefer to call this like smart smart contract<00:02:53.879> wallets<00:02:54.239> I<00:02:54.420> prefer<00:02:54.660> to<00:02:54.720> call<00:02:54.900> all 00:02:55.130 --> 00:02:55.140 align:start position:0% contract wallets I prefer to call all 00:02:55.140 --> 00:02:57.110 align:start position:0% contract wallets I prefer to call all these<00:02:55.620> Technologies<00:02:56.160> smart<00:02:56.700> contract 00:02:57.110 --> 00:02:57.120 align:start position:0% these Technologies smart contract 00:02:57.120 --> 00:02:59.330 align:start position:0% these Technologies smart contract wallets<00:02:57.420> or<00:02:57.540> smart<00:02:57.780> wallets<00:02:58.080> for<00:02:58.260> short<00:02:58.379> and 00:02:59.330 --> 00:02:59.340 align:start position:0% wallets or smart wallets for short and 00:02:59.340 --> 00:03:01.250 align:start position:0% wallets or smart wallets for short and this<00:02:59.580> is<00:02:59.700> basically<00:03:00.000> where<00:03:00.420> each<00:03:00.780> account<00:03:00.959> is 00:03:01.250 --> 00:03:01.260 align:start position:0% this is basically where each account is 00:03:01.260 --> 00:03:03.530 align:start position:0% this is basically where each account is a<00:03:01.440> smart<00:03:01.560> contract<00:03:02.040> which<00:03:02.640> allows<00:03:03.060> for<00:03:03.180> any 00:03:03.530 --> 00:03:03.540 align:start position:0% a smart contract which allows for any 00:03:03.540 --> 00:03:06.710 align:start position:0% a smart contract which allows for any custom<00:03:03.780> execution<00:03:04.379> logic<00:03:05.180> including<00:03:06.180> multi-6 00:03:06.710 --> 00:03:06.720 align:start position:0% custom execution logic including multi-6 00:03:06.720 --> 00:03:08.930 align:start position:0% custom execution logic including multi-6 of<00:03:06.959> course<00:03:07.080> and<00:03:07.379> then<00:03:07.560> MPC<00:03:08.519> refers<00:03:08.879> to 00:03:08.930 --> 00:03:08.940 align:start position:0% of course and then MPC refers to 00:03:08.940 --> 00:03:10.670 align:start position:0% of course and then MPC refers to multi-party<00:03:09.540> computation<00:03:09.959> and<00:03:10.319> in<00:03:10.500> the 00:03:10.670 --> 00:03:10.680 align:start position:0% multi-party computation and in the 00:03:10.680 --> 00:03:14.030 align:start position:0% multi-party computation and in the context<00:03:10.920> of<00:03:11.099> wallets<00:03:11.900> it<00:03:12.900> means<00:03:13.260> that<00:03:13.680> it 00:03:14.030 --> 00:03:14.040 align:start position:0% context of wallets it means that it 00:03:14.040 --> 00:03:16.430 align:start position:0% context of wallets it means that it allows<00:03:14.340> you<00:03:14.459> to<00:03:14.640> have<00:03:14.940> like<00:03:15.840> threshold 00:03:16.430 --> 00:03:16.440 align:start position:0% allows you to have like threshold 00:03:16.440 --> 00:03:19.850 align:start position:0% allows you to have like threshold signatures<00:03:16.980> so<00:03:17.580> you<00:03:18.300> can<00:03:18.360> sign<00:03:18.659> by<00:03:19.200> the 00:03:19.850 --> 00:03:19.860 align:start position:0% signatures so you can sign by the 00:03:19.860 --> 00:03:21.589 align:start position:0% signatures so you can sign by the signature<00:03:20.220> could<00:03:20.400> be<00:03:20.519> by<00:03:20.700> multiple<00:03:21.180> parties 00:03:21.589 --> 00:03:21.599 align:start position:0% signature could be by multiple parties 00:03:21.599 --> 00:03:23.630 align:start position:0% signature could be by multiple parties or<00:03:22.080> you<00:03:22.200> can<00:03:22.319> do<00:03:22.379> N<00:03:22.620> Out<00:03:22.800> of<00:03:22.920> them<00:03:23.040> so<00:03:23.280> like<00:03:23.459> two 00:03:23.630 --> 00:03:23.640 align:start position:0% or you can do N Out of them so like two 00:03:23.640 --> 00:03:26.869 align:start position:0% or you can do N Out of them so like two out<00:03:23.819> of<00:03:23.940> three<00:03:24.560> and<00:03:25.560> let's<00:03:26.040> start<00:03:26.280> by<00:03:26.459> boosting 00:03:26.869 --> 00:03:26.879 align:start position:0% out of three and let's start by boosting 00:03:26.879 --> 00:03:29.390 align:start position:0% out of three and let's start by boosting some<00:03:27.120> myths<00:03:27.659> about<00:03:27.780> smart<00:03:28.200> wallets<00:03:28.680> so<00:03:29.099> one<00:03:29.280> of 00:03:29.390 --> 00:03:29.400 align:start position:0% some myths about smart wallets so one of 00:03:29.400 --> 00:03:30.830 align:start position:0% some myths about smart wallets so one of them<00:03:29.519> is<00:03:29.640> that<00:03:29.879> smart<00:03:30.000> wallets<00:03:30.360> cannot<00:03:30.659> sign 00:03:30.830 --> 00:03:30.840 align:start position:0% them is that smart wallets cannot sign 00:03:30.840 --> 00:03:32.570 align:start position:0% them is that smart wallets cannot sign messages<00:03:31.080> and<00:03:31.440> I'm<00:03:31.620> sure<00:03:31.800> that<00:03:32.040> many<00:03:32.340> of<00:03:32.459> you 00:03:32.570 --> 00:03:32.580 align:start position:0% messages and I'm sure that many of you 00:03:32.580 --> 00:03:34.130 align:start position:0% messages and I'm sure that many of you have<00:03:32.760> heard<00:03:32.940> that<00:03:33.120> but<00:03:33.300> the<00:03:33.480> reality<00:03:33.720> is<00:03:33.840> that 00:03:34.130 --> 00:03:34.140 align:start position:0% have heard that but the reality is that 00:03:34.140 --> 00:03:36.050 align:start position:0% have heard that but the reality is that smartwatch<00:03:34.800> can<00:03:35.220> sign<00:03:35.400> messages<00:03:35.580> are<00:03:35.940> just 00:03:36.050 --> 00:03:36.060 align:start position:0% smartwatch can sign messages are just 00:03:36.060 --> 00:03:37.850 align:start position:0% smartwatch can sign messages are just fine<00:03:36.180> you<00:03:36.420> just<00:03:36.599> need<00:03:36.720> a<00:03:36.900> bit<00:03:37.019> of<00:03:37.200> custom<00:03:37.379> Logic 00:03:37.850 --> 00:03:37.860 align:start position:0% fine you just need a bit of custom Logic 00:03:37.860 --> 00:03:40.750 align:start position:0% fine you just need a bit of custom Logic for<00:03:37.980> verification<00:03:38.519> which<00:03:39.480> is<00:03:39.540> the<00:03:39.659> ip1271 00:03:40.750 --> 00:03:40.760 align:start position:0% for verification which is the ip1271 00:03:40.760 --> 00:03:43.490 align:start position:0% for verification which is the ip1271 then<00:03:41.760> another<00:03:41.940> one<00:03:42.299> is<00:03:42.540> that<00:03:42.840> smart<00:03:43.140> wallets 00:03:43.490 --> 00:03:43.500 align:start position:0% then another one is that smart wallets 00:03:43.500 --> 00:03:44.750 align:start position:0% then another one is that smart wallets and<00:03:43.620> I've<00:03:43.799> heard<00:03:43.920> that<00:03:44.099> in<00:03:44.280> the<00:03:44.340> past<00:03:44.459> that 00:03:44.750 --> 00:03:44.760 align:start position:0% and I've heard that in the past that 00:03:44.760 --> 00:03:46.309 align:start position:0% and I've heard that in the past that they<00:03:44.940> produce<00:03:45.239> different<00:03:45.480> address<00:03:45.780> for<00:03:46.140> each 00:03:46.309 --> 00:03:46.319 align:start position:0% they produce different address for each 00:03:46.319 --> 00:03:49.670 align:start position:0% they produce different address for each chain<00:03:46.560> so<00:03:47.099> it's<00:03:47.280> kind<00:03:47.519> of<00:03:47.700> tough<00:03:48.659> to<00:03:48.780> use<00:03:48.959> but 00:03:49.670 --> 00:03:49.680 align:start position:0% chain so it's kind of tough to use but 00:03:49.680 --> 00:03:51.350 align:start position:0% chain so it's kind of tough to use but that's<00:03:49.799> not<00:03:49.980> really<00:03:50.220> true<00:03:50.580> because<00:03:50.940> you<00:03:51.180> have 00:03:51.350 --> 00:03:51.360 align:start position:0% that's not really true because you have 00:03:51.360 --> 00:03:52.670 align:start position:0% that's not really true because you have create<00:03:51.540> two<00:03:51.900> now<00:03:52.140> and<00:03:52.319> you<00:03:52.440> can<00:03:52.560> create 00:03:52.670 --> 00:03:52.680 align:start position:0% create two now and you can create 00:03:52.680 --> 00:03:54.289 align:start position:0% create two now and you can create accounts<00:03:53.159> counter<00:03:53.459> factually<00:03:53.819> at<00:03:54.060> the<00:03:54.180> same 00:03:54.289 --> 00:03:54.299 align:start position:0% accounts counter factually at the same 00:03:54.299 --> 00:03:57.229 align:start position:0% accounts counter factually at the same address<00:03:54.480> on<00:03:54.900> all<00:03:55.080> evm<00:03:55.560> chains<00:03:55.980> again<00:03:56.879> it<00:03:57.120> was 00:03:57.229 --> 00:03:57.239 align:start position:0% address on all evm chains again it was 00:03:57.239 --> 00:03:59.089 align:start position:0% address on all evm chains again it was mentioned<00:03:57.540> in<00:03:57.720> the<00:03:57.900> panel<00:03:58.200> and<00:03:58.620> then<00:03:58.860> the 00:03:59.089 --> 00:03:59.099 align:start position:0% mentioned in the panel and then the 00:03:59.099 --> 00:04:01.070 align:start position:0% mentioned in the panel and then the other<00:03:59.159> one<00:03:59.340> is<00:03:59.519> the<00:03:59.640> gas<00:03:59.760> overhead<00:04:00.299> gas 00:04:01.070 --> 00:04:01.080 align:start position:0% other one is the gas overhead gas 00:04:01.080 --> 00:04:03.229 align:start position:0% other one is the gas overhead gas overhead<00:04:01.560> still<00:04:01.799> exists<00:04:02.220> but<00:04:02.340> it's<00:04:02.580> got<00:04:02.940> on<00:04:03.120> a 00:04:03.229 --> 00:04:03.239 align:start position:0% overhead still exists but it's got on a 00:04:03.239 --> 00:04:05.270 align:start position:0% overhead still exists but it's got on a lot<00:04:03.540> less<00:04:03.659> in<00:04:03.959> the<00:04:04.140> last<00:04:04.200> years<00:04:04.440> again<00:04:04.920> thanks 00:04:05.270 --> 00:04:05.280 align:start position:0% lot less in the last years again thanks 00:04:05.280 --> 00:04:10.309 align:start position:0% lot less in the last years again thanks to<00:04:05.900> thanks<00:04:06.900> to<00:04:07.260> proxies<00:04:08.040> minimal<00:04:08.760> proxies<00:04:09.319> and 00:04:10.309 --> 00:04:10.319 align:start position:0% to thanks to proxies minimal proxies and 00:04:10.319 --> 00:04:12.250 align:start position:0% to thanks to proxies minimal proxies and thanks<00:04:10.439> to<00:04:10.680> counter<00:04:10.980> factual<00:04:11.280> deployment 00:04:12.250 --> 00:04:12.260 align:start position:0% thanks to counter factual deployment 00:04:12.260 --> 00:04:15.589 align:start position:0% thanks to counter factual deployment unlike<00:04:13.260> NPC<00:04:13.739> smart<00:04:14.040> worlds<00:04:14.519> can<00:04:14.640> do<00:04:14.879> many<00:04:15.299> more 00:04:15.589 --> 00:04:15.599 align:start position:0% unlike NPC smart worlds can do many more 00:04:15.599 --> 00:04:18.229 align:start position:0% unlike NPC smart worlds can do many more things<00:04:15.840> than<00:04:16.139> just<00:04:16.500> multi-6<00:04:17.459> they<00:04:18.000> can<00:04:18.180> do 00:04:18.229 --> 00:04:18.239 align:start position:0% things than just multi-6 they can do 00:04:18.239 --> 00:04:20.030 align:start position:0% things than just multi-6 they can do time<00:04:18.479> logs<00:04:18.840> they<00:04:18.959> can<00:04:19.079> do<00:04:19.199> spending<00:04:19.560> limits 00:04:20.030 --> 00:04:20.040 align:start position:0% time logs they can do spending limits 00:04:20.040 --> 00:04:22.069 align:start position:0% time logs they can do spending limits again<00:04:20.820> something<00:04:21.120> that<00:04:21.359> was<00:04:21.479> fantastically 00:04:22.069 --> 00:04:22.079 align:start position:0% again something that was fantastically 00:04:22.079 --> 00:04:24.170 align:start position:0% again something that was fantastically covered<00:04:22.500> on<00:04:22.620> the<00:04:22.800> panel<00:04:23.160> and<00:04:23.759> this<00:04:23.940> also 00:04:24.170 --> 00:04:24.180 align:start position:0% covered on the panel and this also 00:04:24.180 --> 00:04:25.610 align:start position:0% covered on the panel and this also allows<00:04:24.479> for<00:04:24.600> Recovery<00:04:25.020> mechanisms<00:04:25.500> like 00:04:25.610 --> 00:04:25.620 align:start position:0% allows for Recovery mechanisms like 00:04:25.620 --> 00:04:27.010 align:start position:0% allows for Recovery mechanisms like social<00:04:25.860> recovery 00:04:27.010 --> 00:04:27.020 align:start position:0% social recovery 00:04:27.020 --> 00:04:31.070 align:start position:0% social recovery and<00:04:28.020> for<00:04:28.680> example<00:04:28.919> seedless<00:04:29.520> onboarding<00:04:30.180> like 00:04:31.070 --> 00:04:31.080 align:start position:0% and for example seedless onboarding like 00:04:31.080 --> 00:04:32.810 align:start position:0% and for example seedless onboarding like we<00:04:31.259> have<00:04:31.380> on<00:04:31.500> our<00:04:31.620> buyer<00:04:32.040> wallet<00:04:32.280> just<00:04:32.520> with<00:04:32.699> an 00:04:32.810 --> 00:04:32.820 align:start position:0% we have on our buyer wallet just with an 00:04:32.820 --> 00:04:34.189 align:start position:0% we have on our buyer wallet just with an email<00:04:32.940> and<00:04:33.180> a<00:04:33.360> password<00:04:33.479> while<00:04:33.900> not 00:04:34.189 --> 00:04:34.199 align:start position:0% email and a password while not 00:04:34.199 --> 00:04:36.230 align:start position:0% email and a password while not compromising<00:04:34.740> non-custodial<00:04:35.639> nature<00:04:36.000> of<00:04:36.120> the 00:04:36.230 --> 00:04:36.240 align:start position:0% compromising non-custodial nature of the 00:04:36.240 --> 00:04:39.230 align:start position:0% compromising non-custodial nature of the wallet<00:04:36.540> it's<00:04:37.320> also<00:04:37.620> mutable<00:04:38.040> which<00:04:39.000> means 00:04:39.230 --> 00:04:39.240 align:start position:0% wallet it's also mutable which means 00:04:39.240 --> 00:04:40.370 align:start position:0% wallet it's also mutable which means that<00:04:39.360> you<00:04:39.479> can<00:04:39.600> change<00:04:39.720> the<00:04:39.900> authentication 00:04:40.370 --> 00:04:40.380 align:start position:0% that you can change the authentication 00:04:40.380 --> 00:04:42.409 align:start position:0% that you can change the authentication scheme<00:04:40.800> like<00:04:40.860> you<00:04:41.160> can<00:04:41.280> start<00:04:41.580> with<00:04:42.000> with 00:04:42.409 --> 00:04:42.419 align:start position:0% scheme like you can start with with 00:04:42.419 --> 00:04:44.090 align:start position:0% scheme like you can start with with seedless<00:04:43.020> onboarding<00:04:43.560> account<00:04:43.680> where<00:04:43.919> you 00:04:44.090 --> 00:04:44.100 align:start position:0% seedless onboarding account where you 00:04:44.100 --> 00:04:45.770 align:start position:0% seedless onboarding account where you have<00:04:44.220> an<00:04:44.460> email<00:04:44.580> and<00:04:44.820> a<00:04:45.000> password<00:04:45.120> and<00:04:45.660> then 00:04:45.770 --> 00:04:45.780 align:start position:0% have an email and a password and then 00:04:45.780 --> 00:04:47.990 align:start position:0% have an email and a password and then also<00:04:46.080> become<00:04:46.320> more<00:04:46.440> versed<00:04:46.919> in<00:04:46.979> crypto<00:04:47.340> you 00:04:47.990 --> 00:04:48.000 align:start position:0% also become more versed in crypto you 00:04:48.000 --> 00:04:49.969 align:start position:0% also become more versed in crypto you can<00:04:48.060> upgrade<00:04:48.660> this<00:04:48.960> to<00:04:49.139> a<00:04:49.259> dresser<00:04:49.680> or<00:04:49.860> a 00:04:49.969 --> 00:04:49.979 align:start position:0% can upgrade this to a dresser or a 00:04:49.979 --> 00:04:53.510 align:start position:0% can upgrade this to a dresser or a ledger<00:04:50.419> and<00:04:51.419> you<00:04:51.720> can<00:04:52.160> you<00:04:53.160> can<00:04:53.280> set<00:04:53.400> the 00:04:53.510 --> 00:04:53.520 align:start position:0% ledger and you can you can set the 00:04:53.520 --> 00:04:54.830 align:start position:0% ledger and you can you can set the Tracer<00:04:53.880> and<00:04:54.000> The<00:04:54.120> Ledger<00:04:54.300> to<00:04:54.479> be<00:04:54.540> like<00:04:54.660> the 00:04:54.830 --> 00:04:54.840 align:start position:0% Tracer and The Ledger to be like the 00:04:54.840 --> 00:04:56.510 align:start position:0% Tracer and The Ledger to be like the sole<00:04:55.199> owner<00:04:55.560> of<00:04:55.800> the<00:04:55.919> account<00:04:56.040> without 00:04:56.510 --> 00:04:56.520 align:start position:0% sole owner of the account without 00:04:56.520 --> 00:04:58.490 align:start position:0% sole owner of the account without changing<00:04:57.000> the<00:04:57.180> address<00:04:57.300> without<00:04:58.020> having<00:04:58.320> to 00:04:58.490 --> 00:04:58.500 align:start position:0% changing the address without having to 00:04:58.500 --> 00:05:00.710 align:start position:0% changing the address without having to move<00:04:58.620> funds<00:04:59.040> which<00:04:59.160> is<00:04:59.280> amazing<00:04:59.699> then<00:05:00.540> you 00:05:00.710 --> 00:05:00.720 align:start position:0% move funds which is amazing then you 00:05:00.720 --> 00:05:02.749 align:start position:0% move funds which is amazing then you have<00:05:00.840> gas<00:05:01.020> obstructions<00:05:01.740> which<00:05:02.100> allows<00:05:02.460> which 00:05:02.749 --> 00:05:02.759 align:start position:0% have gas obstructions which allows which 00:05:02.759 --> 00:05:05.090 align:start position:0% have gas obstructions which allows which allow<00:05:03.060> you<00:05:03.180> to<00:05:03.479> pay<00:05:03.840> for<00:05:04.320> transactions<00:05:04.919> and 00:05:05.090 --> 00:05:05.100 align:start position:0% allow you to pay for transactions and 00:05:05.100 --> 00:05:07.189 align:start position:0% allow you to pay for transactions and stable<00:05:05.340> coins<00:05:05.759> so<00:05:06.419> like<00:05:06.600> if<00:05:06.780> you're<00:05:06.900> a<00:05:07.020> new 00:05:07.189 --> 00:05:07.199 align:start position:0% stable coins so like if you're a new 00:05:07.199 --> 00:05:10.129 align:start position:0% stable coins so like if you're a new user<00:05:07.440> on<00:05:07.620> boarding<00:05:08.040> on<00:05:08.460> crypto<00:05:08.820> to<00:05:09.419> crypto<00:05:09.780> you 00:05:10.129 --> 00:05:10.139 align:start position:0% user on boarding on crypto to crypto you 00:05:10.139 --> 00:05:12.110 align:start position:0% user on boarding on crypto to crypto you can<00:05:10.259> sign<00:05:10.740> up<00:05:10.919> with<00:05:11.400> an<00:05:11.520> email<00:05:11.639> and<00:05:11.820> a<00:05:12.000> password 00:05:12.110 --> 00:05:12.120 align:start position:0% can sign up with an email and a password 00:05:12.120 --> 00:05:14.749 align:start position:0% can sign up with an email and a password then<00:05:12.540> fund<00:05:13.139> your<00:05:13.199> account<00:05:13.380> with<00:05:13.860> an<00:05:14.220> on-ramp 00:05:14.749 --> 00:05:14.759 align:start position:0% then fund your account with an on-ramp 00:05:14.759 --> 00:05:16.670 align:start position:0% then fund your account with an on-ramp and<00:05:15.240> then<00:05:15.360> you<00:05:15.479> would<00:05:15.600> receive<00:05:15.840> usdt<00:05:16.380> and<00:05:16.560> you 00:05:16.670 --> 00:05:16.680 align:start position:0% and then you would receive usdt and you 00:05:16.680 --> 00:05:18.110 align:start position:0% and then you would receive usdt and you will<00:05:16.800> be<00:05:16.919> able<00:05:17.100> to<00:05:17.220> swap<00:05:17.520> that<00:05:17.699> for<00:05:17.880> example 00:05:18.110 --> 00:05:18.120 align:start position:0% will be able to swap that for example 00:05:18.120 --> 00:05:20.150 align:start position:0% will be able to swap that for example for<00:05:18.300> Rita<00:05:18.600> without<00:05:18.960> having<00:05:19.259> either<00:05:19.560> for<00:05:19.919> gas 00:05:20.150 --> 00:05:20.160 align:start position:0% for Rita without having either for gas 00:05:20.160 --> 00:05:22.430 align:start position:0% for Rita without having either for gas and<00:05:21.060> of<00:05:21.180> course<00:05:21.300> you<00:05:21.479> can<00:05:21.600> batch<00:05:21.780> transactions 00:05:22.430 --> 00:05:22.440 align:start position:0% and of course you can batch transactions 00:05:22.440 --> 00:05:24.230 align:start position:0% and of course you can batch transactions so<00:05:22.680> do<00:05:22.919> multiple<00:05:23.280> things<00:05:23.520> in<00:05:23.820> in<00:05:24.060> one 00:05:24.230 --> 00:05:24.240 align:start position:0% so do multiple things in in one 00:05:24.240 --> 00:05:26.749 align:start position:0% so do multiple things in in one transaction<00:05:24.600> again<00:05:25.560> a<00:05:25.860> fantastic<00:05:26.220> example 00:05:26.749 --> 00:05:26.759 align:start position:0% transaction again a fantastic example 00:05:26.759 --> 00:05:29.090 align:start position:0% transaction again a fantastic example from<00:05:27.120> Argent<00:05:27.720> was<00:05:27.960> the<00:05:28.199> nft<00:05:28.500> shopping<00:05:28.800> cart 00:05:29.090 --> 00:05:29.100 align:start position:0% from Argent was the nft shopping cart 00:05:29.100 --> 00:05:31.010 align:start position:0% from Argent was the nft shopping cart but<00:05:29.580> a<00:05:29.759> simple<00:05:29.880> example<00:05:30.300> would<00:05:30.479> be<00:05:30.600> on<00:05:30.720> uni 00:05:31.010 --> 00:05:31.020 align:start position:0% but a simple example would be on uni 00:05:31.020 --> 00:05:32.510 align:start position:0% but a simple example would be on uni swap<00:05:31.199> when<00:05:31.380> you<00:05:31.500> have<00:05:31.620> an<00:05:31.740> approval<00:05:32.160> the 00:05:32.510 --> 00:05:32.520 align:start position:0% swap when you have an approval the 00:05:32.520 --> 00:05:34.189 align:start position:0% swap when you have an approval the approval<00:05:32.880> would<00:05:33.000> get<00:05:33.180> batched<00:05:33.600> together<00:05:33.720> with 00:05:34.189 --> 00:05:34.199 align:start position:0% approval would get batched together with 00:05:34.199 --> 00:05:36.830 align:start position:0% approval would get batched together with with<00:05:34.680> transaction<00:05:35.280> so<00:05:35.759> you<00:05:36.419> wouldn't<00:05:36.539> have<00:05:36.720> to 00:05:36.830 --> 00:05:36.840 align:start position:0% with transaction so you wouldn't have to 00:05:36.840 --> 00:05:38.570 align:start position:0% with transaction so you wouldn't have to do<00:05:36.960> it<00:05:37.080> separately<00:05:37.440> and<00:05:38.160> there<00:05:38.340> are<00:05:38.460> more 00:05:38.570 --> 00:05:38.580 align:start position:0% do it separately and there are more 00:05:38.580 --> 00:05:41.050 align:start position:0% do it separately and there are more exotic<00:05:39.000> use<00:05:39.180> cases<00:05:39.479> like<00:05:39.720> for<00:05:39.960> example<00:05:40.199> custom 00:05:41.050 --> 00:05:41.060 align:start position:0% exotic use cases like for example custom 00:05:41.060 --> 00:05:43.490 align:start position:0% exotic use cases like for example custom cryptography<00:05:42.060> like<00:05:42.360> enabling<00:05:43.020> the<00:05:43.199> nist 00:05:43.490 --> 00:05:43.500 align:start position:0% cryptography like enabling the nist 00:05:43.500 --> 00:05:45.710 align:start position:0% cryptography like enabling the nist curve<00:05:43.800> which<00:05:44.580> would<00:05:44.759> allow<00:05:45.060> using<00:05:45.360> iOS 00:05:45.710 --> 00:05:45.720 align:start position:0% curve which would allow using iOS 00:05:45.720 --> 00:05:48.890 align:start position:0% curve which would allow using iOS Biometrics<00:05:46.440> and<00:05:46.620> web<00:05:46.800> authentication 00:05:48.890 --> 00:05:48.900 align:start position:0% Biometrics and web authentication 00:05:48.900 --> 00:05:50.270 align:start position:0% Biometrics and web authentication um<00:05:48.960> and<00:05:49.199> there<00:05:49.380> are<00:05:49.560> there<00:05:49.919> are<00:05:50.039> of<00:05:50.160> course 00:05:50.270 --> 00:05:50.280 align:start position:0% um and there are there are of course 00:05:50.280 --> 00:05:51.950 align:start position:0% um and there are there are of course some<00:05:50.460> drawbacks<00:05:51.000> of<00:05:51.120> smart<00:05:51.360> wallets<00:05:51.720> and<00:05:51.840> some 00:05:51.950 --> 00:05:51.960 align:start position:0% some drawbacks of smart wallets and some 00:05:51.960 --> 00:05:54.529 align:start position:0% some drawbacks of smart wallets and some adoption<00:05:52.380> challenges<00:05:52.800> like<00:05:53.759> you<00:05:53.940> have<00:05:54.120> gas 00:05:54.529 --> 00:05:54.539 align:start position:0% adoption challenges like you have gas 00:05:54.539 --> 00:05:55.870 align:start position:0% adoption challenges like you have gas overhead 00:05:55.870 --> 00:05:55.880 align:start position:0% overhead 00:05:55.880 --> 00:05:58.430 align:start position:0% overhead as<00:05:56.880> mentioned<00:05:57.240> as<00:05:57.660> mentioned<00:05:58.080> previously 00:05:58.430 --> 00:05:58.440 align:start position:0% as mentioned as mentioned previously 00:05:58.440 --> 00:06:01.010 align:start position:0% as mentioned as mentioned previously it's<00:05:58.620> not<00:05:58.860> so<00:05:59.039> much<00:05:59.220> as<00:05:59.400> people<00:05:59.639> think<00:06:00.060> you 00:06:01.010 --> 00:06:01.020 align:start position:0% it's not so much as people think you 00:06:01.020 --> 00:06:03.529 align:start position:0% it's not so much as people think you just<00:06:01.139> have<00:06:01.320> around<00:06:01.800> one<00:06:02.400> to<00:06:02.639> two<00:06:02.940> thousand<00:06:03.240> gas 00:06:03.529 --> 00:06:03.539 align:start position:0% just have around one to two thousand gas 00:06:03.539 --> 00:06:06.110 align:start position:0% just have around one to two thousand gas per<00:06:03.780> transaction<00:06:04.340> and<00:06:05.340> around<00:06:05.639> forty 00:06:06.110 --> 00:06:06.120 align:start position:0% per transaction and around forty 00:06:06.120 --> 00:06:07.670 align:start position:0% per transaction and around forty thousand<00:06:06.300> gas<00:06:06.479> for<00:06:06.780> deployment<00:06:07.199> which<00:06:07.560> is 00:06:07.670 --> 00:06:07.680 align:start position:0% thousand gas for deployment which is 00:06:07.680 --> 00:06:10.969 align:start position:0% thousand gas for deployment which is added<00:06:08.100> to<00:06:08.280> your<00:06:08.460> first<00:06:08.639> transaction<00:06:09.740> but<00:06:10.740> the 00:06:10.969 --> 00:06:10.979 align:start position:0% added to your first transaction but the 00:06:10.979 --> 00:06:14.330 align:start position:0% added to your first transaction but the main<00:06:11.160> challenge<00:06:11.400> is<00:06:12.199> DAP<00:06:13.199> adoption<00:06:13.620> so<00:06:13.860> a<00:06:14.220> lot 00:06:14.330 --> 00:06:14.340 align:start position:0% main challenge is DAP adoption so a lot 00:06:14.340 --> 00:06:16.550 align:start position:0% main challenge is DAP adoption so a lot of<00:06:14.460> Dubs<00:06:14.940> either<00:06:15.360> block<00:06:15.780> smart<00:06:16.080> contracts 00:06:16.550 --> 00:06:16.560 align:start position:0% of Dubs either block smart contracts 00:06:16.560 --> 00:06:18.230 align:start position:0% of Dubs either block smart contracts intentionally<00:06:17.100> because<00:06:17.460> they<00:06:17.759> believe<00:06:17.940> that 00:06:18.230 --> 00:06:18.240 align:start position:0% intentionally because they believe that 00:06:18.240 --> 00:06:20.749 align:start position:0% intentionally because they believe that that's<00:06:18.600> not<00:06:19.020> a<00:06:19.199> wallet<00:06:19.560> and<00:06:19.979> it's<00:06:20.160> some<00:06:20.580> sort 00:06:20.749 --> 00:06:20.759 align:start position:0% that's not a wallet and it's some sort 00:06:20.759 --> 00:06:23.270 align:start position:0% that's not a wallet and it's some sort of<00:06:20.880> automation<00:06:21.440> that's<00:06:22.440> basically<00:06:22.800> what<00:06:22.979> nft 00:06:23.270 --> 00:06:23.280 align:start position:0% of automation that's basically what nft 00:06:23.280 --> 00:06:25.129 align:start position:0% of automation that's basically what nft means<00:06:23.639> and<00:06:24.060> the<00:06:24.180> other<00:06:24.300> thing<00:06:24.479> is<00:06:24.600> many<00:06:24.780> dabs 00:06:25.129 --> 00:06:25.139 align:start position:0% means and the other thing is many dabs 00:06:25.139 --> 00:06:26.390 align:start position:0% means and the other thing is many dabs just<00:06:25.259> don't<00:06:25.380> Implement<00:06:25.800> smart<00:06:26.039> contract 00:06:26.390 --> 00:06:26.400 align:start position:0% just don't Implement smart contract 00:06:26.400 --> 00:06:29.330 align:start position:0% just don't Implement smart contract signing<00:06:26.819> but<00:06:27.000> this<00:06:27.180> is<00:06:27.360> quite<00:06:27.539> easy<00:06:27.720> to<00:06:27.960> fix<00:06:28.340> so 00:06:29.330 --> 00:06:29.340 align:start position:0% signing but this is quite easy to fix so 00:06:29.340 --> 00:06:31.610 align:start position:0% signing but this is quite easy to fix so when<00:06:29.580> would<00:06:29.759> you<00:06:29.940> want<00:06:30.120> to<00:06:30.240> use<00:06:30.479> MPC<00:06:31.259> wallets 00:06:31.610 --> 00:06:31.620 align:start position:0% when would you want to use MPC wallets 00:06:31.620 --> 00:06:34.010 align:start position:0% when would you want to use MPC wallets so<00:06:31.860> one<00:06:32.220> of<00:06:32.340> the<00:06:32.520> benefits<00:06:33.000> of<00:06:33.120> NPC<00:06:33.539> wallets<00:06:33.840> is 00:06:34.010 --> 00:06:34.020 align:start position:0% so one of the benefits of NPC wallets is 00:06:34.020 --> 00:06:36.110 align:start position:0% so one of the benefits of NPC wallets is off<00:06:34.259> chain<00:06:34.500> recovery<00:06:35.039> which<00:06:35.460> is<00:06:35.639> cheaper<00:06:36.000> and 00:06:36.110 --> 00:06:36.120 align:start position:0% off chain recovery which is cheaper and 00:06:36.120 --> 00:06:38.930 align:start position:0% off chain recovery which is cheaper and easier<00:06:36.479> but<00:06:36.960> not<00:06:37.259> as<00:06:37.440> flexible<00:06:37.860> then<00:06:38.759> the 00:06:38.930 --> 00:06:38.940 align:start position:0% easier but not as flexible then the 00:06:38.940 --> 00:06:40.909 align:start position:0% easier but not as flexible then the other<00:06:39.060> thing<00:06:39.419> is<00:06:39.960> they're<00:06:40.440> truly<00:06:40.740> cross 00:06:40.909 --> 00:06:40.919 align:start position:0% other thing is they're truly cross 00:06:40.919 --> 00:06:43.249 align:start position:0% other thing is they're truly cross chains<00:06:41.340> so<00:06:41.460> there's<00:06:41.580> no<00:06:41.819> dependence<00:06:42.240> on<00:06:42.780> Smart 00:06:43.249 --> 00:06:43.259 align:start position:0% chains so there's no dependence on Smart 00:06:43.259 --> 00:06:45.050 align:start position:0% chains so there's no dependence on Smart contracts<00:06:43.919> so<00:06:44.160> for<00:06:44.340> example<00:06:44.580> you<00:06:44.819> can<00:06:44.940> support 00:06:45.050 --> 00:06:45.060 align:start position:0% contracts so for example you can support 00:06:45.060 --> 00:06:47.629 align:start position:0% contracts so for example you can support Bitcoin<00:06:45.720> or<00:06:46.080> you<00:06:46.199> can<00:06:46.319> support<00:06:46.560> basically<00:06:47.340> any 00:06:47.629 --> 00:06:47.639 align:start position:0% Bitcoin or you can support basically any 00:06:47.639 --> 00:06:49.909 align:start position:0% Bitcoin or you can support basically any chain<00:06:47.940> that<00:06:48.300> uses<00:06:48.600> elliptical<00:06:49.199> signatures 00:06:49.909 --> 00:06:49.919 align:start position:0% chain that uses elliptical signatures 00:06:49.919 --> 00:06:53.689 align:start position:0% chain that uses elliptical signatures there's<00:06:50.759> no<00:06:51.000> gas<00:06:51.180> overhead<00:06:51.800> and<00:06:52.800> there's<00:06:52.979> no 00:06:53.689 --> 00:06:53.699 align:start position:0% there's no gas overhead and there's no 00:06:53.699 --> 00:06:55.670 align:start position:0% there's no gas overhead and there's no kind<00:06:54.300> of<00:06:54.419> drama<00:06:54.720> with<00:06:55.020> the<00:06:55.139> signatures<00:06:55.440> like 00:06:55.670 --> 00:06:55.680 align:start position:0% kind of drama with the signatures like 00:06:55.680 --> 00:06:58.249 align:start position:0% kind of drama with the signatures like signatures<00:06:56.340> just<00:06:56.520> work<00:06:56.759> with<00:06:56.940> any<00:06:57.060> dab<00:06:57.419> but 00:06:58.249 --> 00:06:58.259 align:start position:0% signatures just work with any dab but 00:06:58.259 --> 00:07:00.469 align:start position:0% signatures just work with any dab but there<00:06:58.319> are<00:06:58.500> some<00:06:58.560> problems<00:06:58.860> with<00:06:58.979> MPC<00:06:59.520> and<00:07:00.180> one 00:07:00.469 --> 00:07:00.479 align:start position:0% there are some problems with MPC and one 00:07:00.479 --> 00:07:02.450 align:start position:0% there are some problems with MPC and one of<00:07:00.600> those<00:07:00.780> is<00:07:01.259> that<00:07:01.500> they<00:07:01.919> require<00:07:02.100> custom 00:07:02.450 --> 00:07:02.460 align:start position:0% of those is that they require custom 00:07:02.460 --> 00:07:05.090 align:start position:0% of those is that they require custom cryptography<00:07:03.259> and<00:07:04.259> there<00:07:04.500> are<00:07:04.680> not<00:07:04.740> that<00:07:04.919> many 00:07:05.090 --> 00:07:05.100 align:start position:0% cryptography and there are not that many 00:07:05.100 --> 00:07:07.370 align:start position:0% cryptography and there are not that many libraries<00:07:05.639> so<00:07:06.000> far<00:07:06.180> and<00:07:06.539> they're<00:07:06.720> not<00:07:06.960> that 00:07:07.370 --> 00:07:07.380 align:start position:0% libraries so far and they're not that 00:07:07.380 --> 00:07:09.950 align:start position:0% libraries so far and they're not that well<00:07:08.100> battle<00:07:08.340> tested<00:07:08.819> as<00:07:09.120> normal<00:07:09.300> electrical 00:07:09.950 --> 00:07:09.960 align:start position:0% well battle tested as normal electrical 00:07:09.960 --> 00:07:11.809 align:start position:0% well battle tested as normal electrical signature<00:07:10.380> libraries<00:07:10.800> and<00:07:11.340> it's<00:07:11.520> kind<00:07:11.639> of<00:07:11.759> an 00:07:11.809 --> 00:07:11.819 align:start position:0% signature libraries and it's kind of an 00:07:11.819 --> 00:07:13.790 align:start position:0% signature libraries and it's kind of an experimental<00:07:12.360> technology<00:07:12.780> but<00:07:13.440> then<00:07:13.620> the 00:07:13.790 --> 00:07:13.800 align:start position:0% experimental technology but then the 00:07:13.800 --> 00:07:15.830 align:start position:0% experimental technology but then the main<00:07:14.039> problem<00:07:14.280> I<00:07:14.880> think<00:07:15.000> is<00:07:15.240> the<00:07:15.419> immutable 00:07:15.830 --> 00:07:15.840 align:start position:0% main problem I think is the immutable 00:07:15.840 --> 00:07:17.990 align:start position:0% main problem I think is the immutable authentication<00:07:16.620> rules<00:07:17.039> which<00:07:17.699> basically 00:07:17.990 --> 00:07:18.000 align:start position:0% authentication rules which basically 00:07:18.000 --> 00:07:19.189 align:start position:0% authentication rules which basically means<00:07:18.240> that<00:07:18.360> when<00:07:18.479> you<00:07:18.600> create<00:07:18.780> like<00:07:18.960> for 00:07:19.189 --> 00:07:19.199 align:start position:0% means that when you create like for 00:07:19.199 --> 00:07:20.870 align:start position:0% means that when you create like for example<00:07:19.440> two<00:07:19.740> out<00:07:19.860> of<00:07:20.039> three<00:07:20.160> multisig<00:07:20.699> you 00:07:20.870 --> 00:07:20.880 align:start position:0% example two out of three multisig you 00:07:20.880 --> 00:07:22.490 align:start position:0% example two out of three multisig you cannot<00:07:21.060> just<00:07:21.180> swap<00:07:21.479> out<00:07:21.599> one<00:07:21.900> of<00:07:22.020> the<00:07:22.080> signers 00:07:22.490 --> 00:07:22.500 align:start position:0% cannot just swap out one of the signers 00:07:22.500 --> 00:07:25.010 align:start position:0% cannot just swap out one of the signers you<00:07:23.220> cannot<00:07:23.400> make<00:07:23.580> it<00:07:23.699> like<00:07:23.940> two<00:07:24.539> out<00:07:24.660> of<00:07:24.840> four 00:07:25.010 --> 00:07:25.020 align:start position:0% you cannot make it like two out of four 00:07:25.020 --> 00:07:26.450 align:start position:0% you cannot make it like two out of four or<00:07:25.259> you<00:07:25.380> cannot<00:07:25.620> make<00:07:25.740> it<00:07:25.860> like<00:07:26.039> a<00:07:26.160> three<00:07:26.280> out 00:07:26.450 --> 00:07:26.460 align:start position:0% or you cannot make it like a three out 00:07:26.460 --> 00:07:28.070 align:start position:0% or you cannot make it like a three out of<00:07:26.580> four<00:07:26.699> it's<00:07:26.940> just<00:07:27.060> immutable<00:07:27.479> once<00:07:28.020> you 00:07:28.070 --> 00:07:28.080 align:start position:0% of four it's just immutable once you 00:07:28.080 --> 00:07:30.110 align:start position:0% of four it's just immutable once you create<00:07:28.259> it<00:07:28.500> that's<00:07:28.680> it<00:07:28.919> which<00:07:29.580> also<00:07:29.880> creates 00:07:30.110 --> 00:07:30.120 align:start position:0% create it that's it which also creates 00:07:30.120 --> 00:07:32.089 align:start position:0% create it that's it which also creates some<00:07:30.300> problems<00:07:30.539> with<00:07:30.720> recovery<00:07:31.199> right<00:07:31.500> so<00:07:31.979> you 00:07:32.089 --> 00:07:32.099 align:start position:0% some problems with recovery right so you 00:07:32.099 --> 00:07:33.770 align:start position:0% some problems with recovery right so you can<00:07:32.280> recover<00:07:32.580> the<00:07:32.759> account<00:07:32.940> once<00:07:33.479> but<00:07:33.660> then 00:07:33.770 --> 00:07:33.780 align:start position:0% can recover the account once but then 00:07:33.780 --> 00:07:35.210 align:start position:0% can recover the account once but then you<00:07:33.960> can<00:07:34.080> change<00:07:34.259> one<00:07:34.500> of<00:07:34.620> the<00:07:34.740> keys<00:07:34.979> so<00:07:35.039> like 00:07:35.210 --> 00:07:35.220 align:start position:0% you can change one of the keys so like 00:07:35.220 --> 00:07:37.249 align:start position:0% you can change one of the keys so like if<00:07:35.400> you<00:07:35.520> lost<00:07:35.699> the<00:07:35.940> key<00:07:36.120> then<00:07:36.780> it's<00:07:36.960> kind<00:07:37.139> of 00:07:37.249 --> 00:07:37.259 align:start position:0% if you lost the key then it's kind of 00:07:37.259 --> 00:07:38.510 align:start position:0% if you lost the key then it's kind of bad 00:07:38.510 --> 00:07:38.520 align:start position:0% bad 00:07:38.520 --> 00:07:41.330 align:start position:0% bad um<00:07:38.580> and<00:07:39.300> it's<00:07:39.660> also<00:07:39.900> limited<00:07:40.259> to<00:07:40.440> multi6<00:07:40.919> you 00:07:41.330 --> 00:07:41.340 align:start position:0% um and it's also limited to multi6 you 00:07:41.340 --> 00:07:43.249 align:start position:0% um and it's also limited to multi6 you don't<00:07:41.460> have<00:07:41.580> time<00:07:41.759> logs<00:07:42.180> so<00:07:42.419> that<00:07:42.539> a<00:07:42.840> lot<00:07:42.960> that 00:07:43.249 --> 00:07:43.259 align:start position:0% don't have time logs so that a lot that 00:07:43.259 --> 00:07:45.230 align:start position:0% don't have time logs so that a lot that limits<00:07:43.800> you<00:07:43.860> a<00:07:44.039> lot<00:07:44.160> as<00:07:44.340> well<00:07:44.460> there's<00:07:44.880> no<00:07:45.060> gas 00:07:45.230 --> 00:07:45.240 align:start position:0% limits you a lot as well there's no gas 00:07:45.240 --> 00:07:47.089 align:start position:0% limits you a lot as well there's no gas obstructions<00:07:45.900> but<00:07:46.199> that's<00:07:46.380> not<00:07:46.620> in<00:07:46.800> the<00:07:46.919> slide 00:07:47.089 --> 00:07:47.099 align:start position:0% obstructions but that's not in the slide 00:07:47.099 --> 00:07:48.409 align:start position:0% obstructions but that's not in the slide because<00:07:47.220> it's<00:07:47.400> more<00:07:47.580> of<00:07:47.699> a<00:07:47.819> benefit<00:07:47.940> of<00:07:48.240> smart 00:07:48.409 --> 00:07:48.419 align:start position:0% because it's more of a benefit of smart 00:07:48.419 --> 00:07:51.290 align:start position:0% because it's more of a benefit of smart contract<00:07:48.900> wallets<00:07:49.259> and<00:07:50.039> finally<00:07:50.340> the<00:07:50.639> also<00:07:51.180> a 00:07:51.290 --> 00:07:51.300 align:start position:0% contract wallets and finally the also a 00:07:51.300 --> 00:07:52.850 align:start position:0% contract wallets and finally the also a very<00:07:51.419> big<00:07:51.599> thing<00:07:51.780> you<00:07:52.020> cannot<00:07:52.259> use<00:07:52.380> it<00:07:52.560> with<00:07:52.740> a 00:07:52.850 --> 00:07:52.860 align:start position:0% very big thing you cannot use it with a 00:07:52.860 --> 00:07:54.650 align:start position:0% very big thing you cannot use it with a hardware<00:07:53.039> wallet<00:07:53.580> at<00:07:53.940> least<00:07:54.060> not<00:07:54.479> before 00:07:54.650 --> 00:07:54.660 align:start position:0% hardware wallet at least not before 00:07:54.660 --> 00:07:56.809 align:start position:0% hardware wallet at least not before those<00:07:55.020> Hardware<00:07:55.199> wallets<00:07:55.620> recommend<00:07:56.160> that<00:07:56.400> of 00:07:56.809 --> 00:07:56.819 align:start position:0% those Hardware wallets recommend that of 00:07:56.819 --> 00:07:58.010 align:start position:0% those Hardware wallets recommend that of course<00:07:56.940> you<00:07:57.120> can<00:07:57.240> argue<00:07:57.479> that<00:07:57.660> you<00:07:57.780> can<00:07:57.900> pull 00:07:58.010 --> 00:07:58.020 align:start position:0% course you can argue that you can pull 00:07:58.020 --> 00:07:59.450 align:start position:0% course you can argue that you can pull requests<00:07:58.440> to<00:07:58.500> those<00:07:58.620> Hardware<00:07:58.860> wallets<00:07:59.340> but 00:07:59.450 --> 00:07:59.460 align:start position:0% requests to those Hardware wallets but 00:07:59.460 --> 00:08:02.390 align:start position:0% requests to those Hardware wallets but at<00:07:59.639> the<00:07:59.759> moment<00:07:59.880> you<00:08:00.120> can't<00:08:00.440> and<00:08:01.440> as<00:08:02.220> a 00:08:02.390 --> 00:08:02.400 align:start position:0% at the moment you can't and as a 00:08:02.400 --> 00:08:03.589 align:start position:0% at the moment you can't and as a conclusion<00:08:02.759> I<00:08:02.940> would<00:08:03.060> say<00:08:03.180> that<00:08:03.360> smart 00:08:03.589 --> 00:08:03.599 align:start position:0% conclusion I would say that smart 00:08:03.599 --> 00:08:05.510 align:start position:0% conclusion I would say that smart contracts<00:08:04.259> and<00:08:04.440> account<00:08:04.740> obstructions<00:08:05.400> are 00:08:05.510 --> 00:08:05.520 align:start position:0% contracts and account obstructions are 00:08:05.520 --> 00:08:08.210 align:start position:0% contracts and account obstructions are the<00:08:05.699> way<00:08:05.819> to<00:08:05.940> go<00:08:06.120> uh<00:08:06.840> does<00:08:07.139> the<00:08:07.440> future<00:08:07.620> proof 00:08:08.210 --> 00:08:08.220 align:start position:0% the way to go uh does the future proof 00:08:08.220 --> 00:08:10.249 align:start position:0% the way to go uh does the future proof way<00:08:08.460> of<00:08:08.759> doing<00:08:08.940> accounts<00:08:09.419> on<00:08:09.539> ethereum<00:08:09.960> and<00:08:10.139> on 00:08:10.249 --> 00:08:10.259 align:start position:0% way of doing accounts on ethereum and on 00:08:10.259 --> 00:08:12.610 align:start position:0% way of doing accounts on ethereum and on other<00:08:10.380> evm<00:08:10.860> chains<00:08:11.220> on<00:08:11.340> layer<00:08:11.639> tools<00:08:12.000> and<00:08:12.180> Etc 00:08:12.610 --> 00:08:12.620 align:start position:0% other evm chains on layer tools and Etc 00:08:12.620 --> 00:08:15.230 align:start position:0% other evm chains on layer tools and Etc but<00:08:13.620> mood<00:08:13.979> Parts<00:08:14.160> computation<00:08:14.759> can<00:08:15.060> be 00:08:15.230 --> 00:08:15.240 align:start position:0% but mood Parts computation can be 00:08:15.240 --> 00:08:17.809 align:start position:0% but mood Parts computation can be fantastic<00:08:15.599> for<00:08:16.020> like<00:08:16.199> some<00:08:16.979> temporary<00:08:17.520> use 00:08:17.809 --> 00:08:17.819 align:start position:0% fantastic for like some temporary use 00:08:17.819 --> 00:08:20.390 align:start position:0% fantastic for like some temporary use cases<00:08:18.120> before<00:08:18.539> dubs<00:08:19.440> kind<00:08:19.680> of<00:08:19.800> get<00:08:20.220> their 00:08:20.390 --> 00:08:20.400 align:start position:0% cases before dubs kind of get their 00:08:20.400 --> 00:08:22.070 align:start position:0% cases before dubs kind of get their stuff<00:08:20.639> together 00:08:22.070 --> 00:08:22.080 align:start position:0% stuff together 00:08:22.080 --> 00:08:23.930 align:start position:0% stuff together um<00:08:22.139> but<00:08:22.500> yeah<00:08:22.620> definitely<00:08:23.099> smart<00:08:23.460> contract 00:08:23.930 --> 00:08:23.940 align:start position:0% um but yeah definitely smart contract 00:08:23.940 --> 00:08:27.589 align:start position:0% um but yeah definitely smart contract wallets<00:08:24.660> are<00:08:25.400> way<00:08:26.400> better<00:08:26.520> for<00:08:26.819> the<00:08:26.940> future<00:08:27.120> so 00:08:27.589 --> 00:08:27.599 align:start position:0% wallets are way better for the future so 00:08:27.599 --> 00:08:31.129 align:start position:0% wallets are way better for the future so that's<00:08:28.440> it<00:08:28.680> so<00:08:29.340> one<00:08:30.120> of<00:08:30.300> the<00:08:30.419> critiques<00:08:30.840> for 00:08:31.129 --> 00:08:31.139 align:start position:0% that's it so one of the critiques for 00:08:31.139 --> 00:08:33.110 align:start position:0% that's it so one of the critiques for the<00:08:31.379> smart<00:08:31.860> contract<00:08:32.219> wallets<00:08:32.640> right<00:08:32.880> now<00:08:33.000> is 00:08:33.110 --> 00:08:33.120 align:start position:0% the smart contract wallets right now is 00:08:33.120 --> 00:08:35.269 align:start position:0% the smart contract wallets right now is that<00:08:33.300> in<00:08:33.599> the<00:08:33.719> end<00:08:33.839> you<00:08:34.200> still<00:08:34.440> need<00:08:34.680> a<00:08:34.979> wallet 00:08:35.269 --> 00:08:35.279 align:start position:0% that in the end you still need a wallet 00:08:35.279 --> 00:08:37.550 align:start position:0% that in the end you still need a wallet with<00:08:35.459> a<00:08:35.640> private<00:08:35.880> key<00:08:36.000> to<00:08:36.240> manage<00:08:36.479> it<00:08:37.020> yeah 00:08:37.550 --> 00:08:37.560 align:start position:0% with a private key to manage it yeah 00:08:37.560 --> 00:08:39.949 align:start position:0% with a private key to manage it yeah yeah<00:08:38.039> both<00:08:38.580> in<00:08:38.760> Taos<00:08:39.060> and<00:08:39.180> multi-six<00:08:39.599> so<00:08:39.839> how 00:08:39.949 --> 00:08:39.959 align:start position:0% yeah both in Taos and multi-six so how 00:08:39.959 --> 00:08:42.110 align:start position:0% yeah both in Taos and multi-six so how do<00:08:40.080> I<00:08:40.260> mean<00:08:40.380> any<00:08:40.620> any<00:08:40.800> ideas<00:08:41.099> of<00:08:41.399> how<00:08:41.520> of<00:08:41.820> how<00:08:42.060> to 00:08:42.110 --> 00:08:42.120 align:start position:0% do I mean any any ideas of how of how to 00:08:42.120 --> 00:08:43.909 align:start position:0% do I mean any any ideas of how of how to overcome<00:08:42.479> it<00:08:42.659> well<00:08:43.020> that's<00:08:43.260> completely<00:08:43.620> true 00:08:43.909 --> 00:08:43.919 align:start position:0% overcome it well that's completely true 00:08:43.919 --> 00:08:45.590 align:start position:0% overcome it well that's completely true but<00:08:44.159> like<00:08:44.279> on<00:08:44.520> a<00:08:44.700> fundamental<00:08:45.180> level<00:08:45.360> you 00:08:45.590 --> 00:08:45.600 align:start position:0% but like on a fundamental level you 00:08:45.600 --> 00:08:47.449 align:start position:0% but like on a fundamental level you cannot<00:08:45.839> get<00:08:45.959> away<00:08:46.080> from<00:08:46.440> the<00:08:46.620> secret<00:08:46.860> right<00:08:47.220> in 00:08:47.449 --> 00:08:47.459 align:start position:0% cannot get away from the secret right in 00:08:47.459 --> 00:08:49.130 align:start position:0% cannot get away from the secret right in any<00:08:47.640> form<00:08:47.820> of<00:08:47.940> authentication<00:08:48.540> you<00:08:48.779> have<00:08:48.899> some 00:08:49.130 --> 00:08:49.140 align:start position:0% any form of authentication you have some 00:08:49.140 --> 00:08:50.870 align:start position:0% any form of authentication you have some sort<00:08:49.320> of<00:08:49.440> a<00:08:49.620> secret<00:08:49.740> just<00:08:50.399> the<00:08:50.519> great<00:08:50.700> thing 00:08:50.870 --> 00:08:50.880 align:start position:0% sort of a secret just the great thing 00:08:50.880 --> 00:08:52.730 align:start position:0% sort of a secret just the great thing about<00:08:51.000> smart<00:08:51.300> contract<00:08:51.720> wallets<00:08:52.080> is<00:08:52.320> that<00:08:52.620> you 00:08:52.730 --> 00:08:52.740 align:start position:0% about smart contract wallets is that you 00:08:52.740 --> 00:08:54.410 align:start position:0% about smart contract wallets is that you can<00:08:52.920> manage<00:08:53.160> it<00:08:53.339> and<00:08:53.519> you<00:08:53.700> can<00:08:53.820> make<00:08:54.060> it<00:08:54.240> work 00:08:54.410 --> 00:08:54.420 align:start position:0% can manage it and you can make it work 00:08:54.420 --> 00:08:56.389 align:start position:0% can manage it and you can make it work not<00:08:54.899> like<00:08:55.080> as<00:08:55.260> a<00:08:55.500> single<00:08:55.680> private<00:08:56.040> key<00:08:56.160> which 00:08:56.389 --> 00:08:56.399 align:start position:0% not like as a single private key which 00:08:56.399 --> 00:08:57.949 align:start position:0% not like as a single private key which is<00:08:56.519> like<00:08:56.640> the<00:08:56.820> source<00:08:57.120> of<00:08:57.180> our<00:08:57.360> authentication 00:08:57.949 --> 00:08:57.959 align:start position:0% is like the source of our authentication 00:08:57.959 --> 00:08:59.449 align:start position:0% is like the source of our authentication and<00:08:58.200> like<00:08:58.380> the<00:08:58.620> one<00:08:58.800> true<00:08:58.980> point<00:08:59.279> of 00:08:59.449 --> 00:08:59.459 align:start position:0% and like the one true point of 00:08:59.459 --> 00:09:01.310 align:start position:0% and like the one true point of authentication<00:09:00.060> but<00:09:00.480> you<00:09:00.660> can<00:09:00.779> have<00:09:00.899> multiple 00:09:01.310 --> 00:09:01.320 align:start position:0% authentication but you can have multiple 00:09:01.320 --> 00:09:03.889 align:start position:0% authentication but you can have multiple of<00:09:01.560> those<00:09:01.740> Secrets<00:09:02.160> like<00:09:02.339> a<00:09:02.580> regular<00:09:03.000> uh<00:09:03.720> like 00:09:03.889 --> 00:09:03.899 align:start position:0% of those Secrets like a regular uh like 00:09:03.899 --> 00:09:05.509 align:start position:0% of those Secrets like a regular uh like like<00:09:04.140> you<00:09:04.380> have<00:09:04.560> on<00:09:04.740> for<00:09:04.980> example<00:09:05.160> on<00:09:05.279> Google 00:09:05.509 --> 00:09:05.519 align:start position:0% like you have on for example on Google 00:09:05.519 --> 00:09:07.490 align:start position:0% like you have on for example on Google or<00:09:05.820> on<00:09:06.000> Facebook<00:09:06.180> or<00:09:06.480> on<00:09:06.660> regular<00:09:07.019> like<00:09:07.260> human 00:09:07.490 --> 00:09:07.500 align:start position:0% or on Facebook or on regular like human 00:09:07.500 --> 00:09:10.310 align:start position:0% or on Facebook or on regular like human friendly<00:09:08.040> uh<00:09:08.580> authentication<00:09:09.120> scheme<00:09:09.540> so<00:09:09.720> it 00:09:10.310 --> 00:09:10.320 align:start position:0% friendly uh authentication scheme so it 00:09:10.320 --> 00:09:11.810 align:start position:0% friendly uh authentication scheme so it is<00:09:10.440> a<00:09:10.620> private<00:09:10.860> key<00:09:10.920> but<00:09:11.160> you<00:09:11.339> shouldn't<00:09:11.640> think 00:09:11.810 --> 00:09:11.820 align:start position:0% is a private key but you shouldn't think 00:09:11.820 --> 00:09:13.790 align:start position:0% is a private key but you shouldn't think of<00:09:12.000> it<00:09:12.180> as<00:09:12.300> a<00:09:12.480> private<00:09:12.720> key<00:09:12.839> because<00:09:13.080> eoa 00:09:13.790 --> 00:09:13.800 align:start position:0% of it as a private key because eoa 00:09:13.800 --> 00:09:16.250 align:start position:0% of it as a private key because eoa wallets<00:09:14.220> they're<00:09:14.940> the<00:09:15.180> private<00:09:15.420> Keys<00:09:15.720> King<00:09:15.959> is 00:09:16.250 --> 00:09:16.260 align:start position:0% wallets they're the private Keys King is 00:09:16.260 --> 00:09:18.470 align:start position:0% wallets they're the private Keys King is like<00:09:16.440> the<00:09:16.620> single<00:09:17.040> secret<00:09:17.640> number<00:09:18.060> where 00:09:18.470 --> 00:09:18.480 align:start position:0% like the single secret number where 00:09:18.480 --> 00:09:20.570 align:start position:0% like the single secret number where everything<00:09:18.779> comes<00:09:19.200> from<00:09:19.380> unlike<00:09:20.339> smart 00:09:20.570 --> 00:09:20.580 align:start position:0% everything comes from unlike smart 00:09:20.580 --> 00:09:23.360 align:start position:0% everything comes from unlike smart contract<00:09:21.000> wallets