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:18.790 align:start position:0% [Music] 00:00:18.790 --> 00:00:18.800 align:start position:0% 00:00:18.800 --> 00:00:21.230 align:start position:0% I<00:00:19.800> know<00:00:19.920> your<00:00:20.100> name 00:00:21.230 --> 00:00:21.240 align:start position:0% I know your name 00:00:21.240 --> 00:00:22.730 align:start position:0% I know your name and<00:00:21.600> we've<00:00:21.779> been<00:00:21.960> working<00:00:22.199> on<00:00:22.560> account 00:00:22.730 --> 00:00:22.740 align:start position:0% and we've been working on account 00:00:22.740 --> 00:00:25.670 align:start position:0% and we've been working on account abstraction<00:00:23.340> in<00:00:24.000> various<00:00:24.420> forms<00:00:24.840> for<00:00:25.380> a<00:00:25.500> few 00:00:25.670 --> 00:00:25.680 align:start position:0% abstraction in various forms for a few 00:00:25.680 --> 00:00:28.070 align:start position:0% abstraction in various forms for a few years<00:00:25.859> now<00:00:26.100> and<00:00:26.820> you<00:00:27.119> have<00:00:27.420> ice<00:00:27.599> who<00:00:27.900> is<00:00:27.960> not 00:00:28.070 --> 00:00:28.080 align:start position:0% years now and you have ice who is not 00:00:28.080 --> 00:00:29.929 align:start position:0% years now and you have ice who is not here<00:00:28.260> is<00:00:28.500> from<00:00:28.740> the<00:00:28.800> ethereum<00:00:29.220> foundation<00:00:29.580> and 00:00:29.929 --> 00:00:29.939 align:start position:0% here is from the ethereum foundation and 00:00:29.939 --> 00:00:32.450 align:start position:0% here is from the ethereum foundation and he<00:00:30.060> has<00:00:30.180> been<00:00:30.300> our<00:00:30.480> colleague<00:00:30.840> and 00:00:32.450 --> 00:00:32.460 align:start position:0% he has been our colleague and 00:00:32.460 --> 00:00:34.130 align:start position:0% he has been our colleague and um<00:00:32.520> yeah<00:00:32.700> we're<00:00:32.940> working<00:00:33.360> on<00:00:33.600> this<00:00:33.780> in 00:00:34.130 --> 00:00:34.140 align:start position:0% um yeah we're working on this in 00:00:34.140 --> 00:00:37.069 align:start position:0% um yeah we're working on this in collaboration<00:00:34.559> with<00:00:35.040> never<00:00:35.460> mind<00:00:36.079> and 00:00:37.069 --> 00:00:37.079 align:start position:0% collaboration with never mind and 00:00:37.079 --> 00:00:40.310 align:start position:0% collaboration with never mind and originally<00:00:37.800> we<00:00:38.760> were<00:00:38.880> working<00:00:39.120> as<00:00:40.020> the<00:00:40.260> open 00:00:40.310 --> 00:00:40.320 align:start position:0% originally we were working as the open 00:00:40.320 --> 00:00:43.729 align:start position:0% originally we were working as the open GSN<00:00:40.920> team<00:00:41.100> on<00:00:41.879> meta<00:00:42.300> transactions<00:00:42.780> and<00:00:43.200> all<00:00:43.559> of 00:00:43.729 --> 00:00:43.739 align:start position:0% GSN team on meta transactions and all of 00:00:43.739 --> 00:00:46.310 align:start position:0% GSN team on meta transactions and all of it<00:00:43.860> kind<00:00:44.040> of<00:00:44.160> merged<00:00:44.579> into<00:00:45.480> account 00:00:46.310 --> 00:00:46.320 align:start position:0% it kind of merged into account 00:00:46.320 --> 00:00:49.970 align:start position:0% it kind of merged into account abstraction<00:00:46.920> the<00:00:47.719> erc4337<00:00:48.719> standard<00:00:49.200> but 00:00:49.970 --> 00:00:49.980 align:start position:0% abstraction the erc4337 standard but 00:00:49.980 --> 00:00:52.010 align:start position:0% abstraction the erc4337 standard but we're<00:00:50.160> going<00:00:50.280> to<00:00:50.399> talk<00:00:50.579> about<00:00:50.899> how<00:00:51.899> account 00:00:52.010 --> 00:00:52.020 align:start position:0% we're going to talk about how account 00:00:52.020 --> 00:00:54.229 align:start position:0% we're going to talk about how account abstraction<00:00:52.620> is<00:00:52.980> generally<00:00:53.820> useful 00:00:54.229 --> 00:00:54.239 align:start position:0% abstraction is generally useful 00:00:54.239 --> 00:00:56.209 align:start position:0% abstraction is generally useful regardless<00:00:54.960> of<00:00:55.140> the<00:00:55.260> implementation<00:00:55.739> so 00:00:56.209 --> 00:00:56.219 align:start position:0% regardless of the implementation so 00:00:56.219 --> 00:00:59.330 align:start position:0% regardless of the implementation so let's<00:00:57.180> talk<00:00:57.360> a<00:00:57.480> little<00:00:57.600> bit<00:00:57.719> about<00:00:58.100> counts<00:00:59.100> and 00:00:59.330 --> 00:00:59.340 align:start position:0% let's talk a little bit about counts and 00:00:59.340 --> 00:01:01.369 align:start position:0% let's talk a little bit about counts and ethereum<00:00:59.820> So<00:01:00.120> Right<00:01:00.360> Now<00:01:00.539> the<00:01:01.079> default 00:01:01.369 --> 00:01:01.379 align:start position:0% ethereum So Right Now the default 00:01:01.379 --> 00:01:04.070 align:start position:0% ethereum So Right Now the default account<00:01:01.620> well<00:01:02.460> the<00:01:02.940> what<00:01:03.359> you<00:01:03.480> get<00:01:03.600> is<00:01:03.899> an 00:01:04.070 --> 00:01:04.080 align:start position:0% account well the what you get is an 00:01:04.080 --> 00:01:06.830 align:start position:0% account well the what you get is an externally<00:01:04.440> owned<00:01:04.799> account<00:01:04.920> and<00:01:05.880> it<00:01:06.060> is<00:01:06.299> a 00:01:06.830 --> 00:01:06.840 align:start position:0% externally owned account and it is a 00:01:06.840 --> 00:01:10.010 align:start position:0% externally owned account and it is a one-size-fits<00:01:07.740> all<00:01:07.799> EC<00:01:08.580> DSi<00:01:09.119> key<00:01:09.360> and<00:01:09.780> the 00:01:10.010 --> 00:01:10.020 align:start position:0% one-size-fits all EC DSi key and the 00:01:10.020 --> 00:01:12.350 align:start position:0% one-size-fits all EC DSi key and the other<00:01:10.140> option<00:01:10.439> you<00:01:10.619> have<00:01:10.860> if<00:01:11.340> you<00:01:11.880> um<00:01:11.880> if<00:01:12.240> you 00:01:12.350 --> 00:01:12.360 align:start position:0% other option you have if you um if you 00:01:12.360 --> 00:01:13.910 align:start position:0% other option you have if you um if you want<00:01:12.479> to<00:01:12.600> have<00:01:12.720> like<00:01:13.439> your<00:01:13.560> own<00:01:13.740> smart 00:01:13.910 --> 00:01:13.920 align:start position:0% want to have like your own smart 00:01:13.920 --> 00:01:15.830 align:start position:0% want to have like your own smart contract<00:01:14.340> that<00:01:15.000> would<00:01:15.119> be<00:01:15.299> controlled<00:01:15.659> by 00:01:15.830 --> 00:01:15.840 align:start position:0% contract that would be controlled by 00:01:15.840 --> 00:01:17.750 align:start position:0% contract that would be controlled by code<00:01:16.020> but<00:01:16.439> you<00:01:16.560> would<00:01:16.680> still<00:01:16.860> need<00:01:17.040> an<00:01:17.159> eoa<00:01:17.640> to 00:01:17.750 --> 00:01:17.760 align:start position:0% code but you would still need an eoa to 00:01:17.760 --> 00:01:20.270 align:start position:0% code but you would still need an eoa to interact<00:01:18.000> with<00:01:18.240> it<00:01:18.360> probably<00:01:19.100> your<00:01:20.100> current 00:01:20.270 --> 00:01:20.280 align:start position:0% interact with it probably your current 00:01:20.280 --> 00:01:22.789 align:start position:0% interact with it probably your current wallet<00:01:20.759> is<00:01:20.939> an<00:01:21.240> externally<00:01:21.960> owned<00:01:22.680> address 00:01:22.789 --> 00:01:22.799 align:start position:0% wallet is an externally owned address 00:01:22.799 --> 00:01:25.609 align:start position:0% wallet is an externally owned address there<00:01:23.640> are<00:01:23.759> some<00:01:23.880> limitations<00:01:24.299> with<00:01:24.659> that<00:01:24.840> the 00:01:25.609 --> 00:01:25.619 align:start position:0% there are some limitations with that the 00:01:25.619 --> 00:01:28.010 align:start position:0% there are some limitations with that the first<00:01:25.740> one<00:01:25.979> is<00:01:26.880> maybe<00:01:27.299> some<00:01:27.600> of<00:01:27.720> us<00:01:27.840> have 00:01:28.010 --> 00:01:28.020 align:start position:0% first one is maybe some of us have 00:01:28.020 --> 00:01:29.330 align:start position:0% first one is maybe some of us have gotten<00:01:28.259> used<00:01:28.380> to<00:01:28.500> it<00:01:28.619> by<00:01:28.740> now<00:01:28.920> but<00:01:29.100> Key 00:01:29.330 --> 00:01:29.340 align:start position:0% gotten used to it by now but Key 00:01:29.340 --> 00:01:31.850 align:start position:0% gotten used to it by now but Key Management<00:01:29.580> can<00:01:30.060> be<00:01:30.180> hard<00:01:30.500> and<00:01:31.500> there's<00:01:31.680> a 00:01:31.850 --> 00:01:31.860 align:start position:0% Management can be hard and there's a 00:01:31.860 --> 00:01:33.109 align:start position:0% Management can be hard and there's a little<00:01:31.920> bit<00:01:32.040> of<00:01:32.159> a<00:01:32.280> paradox<00:01:32.700> with<00:01:32.939> key 00:01:33.109 --> 00:01:33.119 align:start position:0% little bit of a paradox with key 00:01:33.119 --> 00:01:35.569 align:start position:0% little bit of a paradox with key management<00:01:33.360> intrinsically<00:01:34.320> because<00:01:34.680> there's 00:01:35.569 --> 00:01:35.579 align:start position:0% management intrinsically because there's 00:01:35.579 --> 00:01:36.649 align:start position:0% management intrinsically because there's a<00:01:35.820> secret 00:01:36.649 --> 00:01:36.659 align:start position:0% a secret 00:01:36.659 --> 00:01:39.890 align:start position:0% a secret that<00:01:37.200> you're<00:01:37.500> on<00:01:37.799> one<00:01:37.979> hand<00:01:38.220> trying<00:01:39.060> really 00:01:39.890 --> 00:01:39.900 align:start position:0% that you're on one hand trying really 00:01:39.900 --> 00:01:42.109 align:start position:0% that you're on one hand trying really hard<00:01:40.140> not<00:01:40.380> to<00:01:40.619> lose<00:01:40.799> because<00:01:41.340> if<00:01:41.579> you<00:01:41.759> lose<00:01:41.880> it 00:01:42.109 --> 00:01:42.119 align:start position:0% hard not to lose because if you lose it 00:01:42.119 --> 00:01:43.670 align:start position:0% hard not to lose because if you lose it you<00:01:42.420> can't<00:01:42.479> do<00:01:42.720> anything<00:01:42.960> with<00:01:43.320> your<00:01:43.500> account 00:01:43.670 --> 00:01:43.680 align:start position:0% you can't do anything with your account 00:01:43.680 --> 00:01:44.569 align:start position:0% you can't do anything with your account anymore 00:01:44.569 --> 00:01:44.579 align:start position:0% anymore 00:01:44.579 --> 00:01:45.649 align:start position:0% anymore and<00:01:45.060> when<00:01:45.180> you<00:01:45.299> don't<00:01:45.420> want<00:01:45.540> to<00:01:45.600> lose 00:01:45.649 --> 00:01:45.659 align:start position:0% and when you don't want to lose 00:01:45.659 --> 00:01:47.390 align:start position:0% and when you don't want to lose something<00:01:45.900> what<00:01:46.140> do<00:01:46.259> you<00:01:46.320> do<00:01:46.439> well<00:01:46.979> you<00:01:47.220> create 00:01:47.390 --> 00:01:47.400 align:start position:0% something what do you do well you create 00:01:47.400 --> 00:01:49.550 align:start position:0% something what do you do well you create many<00:01:47.640> copies<00:01:48.000> of<00:01:48.180> it<00:01:48.299> and<00:01:48.960> you<00:01:49.140> make<00:01:49.259> sure<00:01:49.380> the 00:01:49.550 --> 00:01:49.560 align:start position:0% many copies of it and you make sure the 00:01:49.560 --> 00:01:51.190 align:start position:0% many copies of it and you make sure the copies<00:01:49.860> don't<00:01:50.100> get<00:01:50.280> lost 00:01:51.190 --> 00:01:51.200 align:start position:0% copies don't get lost 00:01:51.200 --> 00:01:54.170 align:start position:0% copies don't get lost but<00:01:52.200> on<00:01:52.439> the<00:01:52.560> other<00:01:52.619> hand<00:01:52.799> you<00:01:53.759> also<00:01:54.000> don't 00:01:54.170 --> 00:01:54.180 align:start position:0% but on the other hand you also don't 00:01:54.180 --> 00:01:55.850 align:start position:0% but on the other hand you also don't want<00:01:54.360> the<00:01:54.479> key<00:01:54.600> to<00:01:54.780> be<00:01:54.899> stolen 00:01:55.850 --> 00:01:55.860 align:start position:0% want the key to be stolen 00:01:55.860 --> 00:01:57.530 align:start position:0% want the key to be stolen and<00:01:56.399> we<00:01:56.579> don't<00:01:56.759> want<00:01:56.880> something<00:01:57.060> to<00:01:57.180> be<00:01:57.240> stolen 00:01:57.530 --> 00:01:57.540 align:start position:0% and we don't want something to be stolen 00:01:57.540 --> 00:02:00.170 align:start position:0% and we don't want something to be stolen what<00:01:57.720> do<00:01:57.840> you<00:01:57.840> do<00:01:58.020> you<00:01:58.979> you<00:01:59.340> know<00:01:59.460> try<00:01:59.759> to<00:01:59.939> hide 00:02:00.170 --> 00:02:00.180 align:start position:0% what do you do you you know try to hide 00:02:00.180 --> 00:02:03.649 align:start position:0% what do you do you you know try to hide uh<00:02:01.079> h-prom<00:02:01.680> adversaries<00:02:02.579> uh<00:02:03.180> make<00:02:03.299> it<00:02:03.479> really 00:02:03.649 --> 00:02:03.659 align:start position:0% uh h-prom adversaries uh make it really 00:02:03.659 --> 00:02:06.469 align:start position:0% uh h-prom adversaries uh make it really hard<00:02:03.840> to<00:02:03.960> access<00:02:04.520> mini<00:02:05.520> minimize<00:02:06.000> how<00:02:06.360> many 00:02:06.469 --> 00:02:06.479 align:start position:0% hard to access mini minimize how many 00:02:06.479 --> 00:02:08.089 align:start position:0% hard to access mini minimize how many copies<00:02:06.840> there<00:02:07.079> are<00:02:07.259> to<00:02:07.439> be<00:02:07.560> still<00:02:07.740> in<00:02:07.920> the 00:02:08.089 --> 00:02:08.099 align:start position:0% copies there are to be still in the 00:02:08.099 --> 00:02:10.430 align:start position:0% copies there are to be still in the first<00:02:08.220> place<00:02:08.720> and<00:02:09.720> the<00:02:10.020> engineering 00:02:10.430 --> 00:02:10.440 align:start position:0% first place and the engineering 00:02:10.440 --> 00:02:12.170 align:start position:0% first place and the engineering strategies<00:02:10.860> when<00:02:11.220> you<00:02:11.400> just<00:02:11.520> have<00:02:11.700> this<00:02:11.940> one 00:02:12.170 --> 00:02:12.180 align:start position:0% strategies when you just have this one 00:02:12.180 --> 00:02:14.390 align:start position:0% strategies when you just have this one uh<00:02:12.840> key<00:02:13.080> that<00:02:13.440> you're<00:02:13.620> trying<00:02:13.860> both<00:02:14.160> to 00:02:14.390 --> 00:02:14.400 align:start position:0% uh key that you're trying both to 00:02:14.400 --> 00:02:16.490 align:start position:0% uh key that you're trying both to prevent<00:02:14.640> from<00:02:14.879> being<00:02:15.060> stolen<00:02:15.420> and<00:02:15.660> from<00:02:16.200> being 00:02:16.490 --> 00:02:16.500 align:start position:0% prevent from being stolen and from being 00:02:16.500 --> 00:02:18.710 align:start position:0% prevent from being stolen and from being lost<00:02:16.680> they're<00:02:17.459> kind<00:02:17.700> of<00:02:17.879> uh<00:02:18.360> mutually 00:02:18.710 --> 00:02:18.720 align:start position:0% lost they're kind of uh mutually 00:02:18.720 --> 00:02:20.510 align:start position:0% lost they're kind of uh mutually exclusive<00:02:19.260> or<00:02:19.560> they<00:02:19.739> they<00:02:19.980> pull<00:02:20.160> in<00:02:20.340> different 00:02:20.510 --> 00:02:20.520 align:start position:0% exclusive or they they pull in different 00:02:20.520 --> 00:02:22.670 align:start position:0% exclusive or they they pull in different directions<00:02:20.760> so<00:02:21.660> Key<00:02:21.900> Management<00:02:22.140> is<00:02:22.500> hard 00:02:22.670 --> 00:02:22.680 align:start position:0% directions so Key Management is hard 00:02:22.680 --> 00:02:24.530 align:start position:0% directions so Key Management is hard even<00:02:22.920> if<00:02:23.099> you<00:02:23.160> know<00:02:23.280> what<00:02:23.400> you're<00:02:23.520> doing<00:02:24.120> the 00:02:24.530 --> 00:02:24.540 align:start position:0% even if you know what you're doing the 00:02:24.540 --> 00:02:26.330 align:start position:0% even if you know what you're doing the other<00:02:24.660> big<00:02:24.900> limitation<00:02:25.319> of<00:02:25.500> EOS<00:02:25.800> is<00:02:26.160> just 00:02:26.330 --> 00:02:26.340 align:start position:0% other big limitation of EOS is just 00:02:26.340 --> 00:02:28.729 align:start position:0% other big limitation of EOS is just Access<00:02:26.580> Control<00:02:26.940> whether<00:02:27.900> you're<00:02:28.319> just 00:02:28.729 --> 00:02:28.739 align:start position:0% Access Control whether you're just 00:02:28.739 --> 00:02:31.490 align:start position:0% Access Control whether you're just playing<00:02:29.099> a<00:02:29.280> blockchain<00:02:29.640> game<00:02:30.020> or<00:02:31.020> you're<00:02:31.260> a 00:02:31.490 --> 00:02:31.500 align:start position:0% playing a blockchain game or you're a 00:02:31.500 --> 00:02:33.170 align:start position:0% playing a blockchain game or you're a multi-billion<00:02:32.040> dollar<00:02:32.160> Corporation<00:02:32.700> if 00:02:33.170 --> 00:02:33.180 align:start position:0% multi-billion dollar Corporation if 00:02:33.180 --> 00:02:35.150 align:start position:0% multi-billion dollar Corporation if you're<00:02:33.300> using<00:02:33.480> an<00:02:33.599> eua<00:02:34.020> it's<00:02:34.379> like<00:02:34.800> the<00:02:35.040> same 00:02:35.150 --> 00:02:35.160 align:start position:0% you're using an eua it's like the same 00:02:35.160 --> 00:02:37.610 align:start position:0% you're using an eua it's like the same Access<00:02:35.400> Control<00:02:35.760> policy 00:02:37.610 --> 00:02:37.620 align:start position:0% Access Control policy 00:02:37.620 --> 00:02:39.650 align:start position:0% Access Control policy so<00:02:38.160> that's<00:02:38.280> very<00:02:38.520> limiting<00:02:38.879> you<00:02:39.180> don't<00:02:39.300> have 00:02:39.650 --> 00:02:39.660 align:start position:0% so that's very limiting you don't have 00:02:39.660 --> 00:02:42.830 align:start position:0% so that's very limiting you don't have uh<00:02:40.440> granularity 00:02:42.830 --> 00:02:42.840 align:start position:0% uh granularity 00:02:42.840 --> 00:02:44.530 align:start position:0% uh granularity um<00:02:42.900> you<00:02:43.319> wouldn't<00:02:43.500> have<00:02:43.680> multi-sig<00:02:44.280> support 00:02:44.530 --> 00:02:44.540 align:start position:0% um you wouldn't have multi-sig support 00:02:44.540 --> 00:02:48.410 align:start position:0% um you wouldn't have multi-sig support there<00:02:45.540> is<00:02:45.660> no<00:02:45.780> ability<00:02:46.080> to<00:02:46.440> implement<00:02:46.739> roles 00:02:48.410 --> 00:02:48.420 align:start position:0% there is no ability to implement roles 00:02:48.420 --> 00:02:50.270 align:start position:0% there is no ability to implement roles um you<00:02:48.599> can't<00:02:48.720> have<00:02:48.900> spending<00:02:49.379> policies<00:02:49.860> it's 00:02:50.270 --> 00:02:50.280 align:start position:0% um you can't have spending policies it's 00:02:50.280 --> 00:02:52.309 align:start position:0% um you can't have spending policies it's just<00:02:50.519> one<00:02:51.000> size<00:02:51.180> fits<00:02:51.660> all 00:02:52.309 --> 00:02:52.319 align:start position:0% just one size fits all 00:02:52.319 --> 00:02:54.770 align:start position:0% just one size fits all mechanism<00:02:53.220> based<00:02:53.700> on<00:02:53.819> this<00:02:54.000> access<00:02:54.239> to<00:02:54.599> a 00:02:54.770 --> 00:02:54.780 align:start position:0% mechanism based on this access to a 00:02:54.780 --> 00:02:57.890 align:start position:0% mechanism based on this access to a secret<00:02:54.900> key<00:02:55.260> the<00:02:56.040> other<00:02:56.099> big<00:02:56.340> limitation<00:02:56.900> of 00:02:57.890 --> 00:02:57.900 align:start position:0% secret key the other big limitation of 00:02:57.900 --> 00:03:01.790 align:start position:0% secret key the other big limitation of EOS<00:02:58.379> is<00:02:58.680> Gas<00:02:58.980> payment<00:02:59.720> so<00:03:00.720> you're<00:03:01.319> paying<00:03:01.680> gas 00:03:01.790 --> 00:03:01.800 align:start position:0% EOS is Gas payment so you're paying gas 00:03:01.800 --> 00:03:04.910 align:start position:0% EOS is Gas payment so you're paying gas directly<00:03:02.400> from<00:03:02.580> the<00:03:02.700> eua<00:03:03.200> and<00:03:04.200> it<00:03:04.379> has<00:03:04.560> to<00:03:04.680> be 00:03:04.910 --> 00:03:04.920 align:start position:0% directly from the eua and it has to be 00:03:04.920 --> 00:03:08.809 align:start position:0% directly from the eua and it has to be an<00:03:05.340> East<00:03:05.580> the<00:03:06.360> native<00:03:06.599> token 00:03:08.809 --> 00:03:08.819 align:start position:0% an East the native token 00:03:08.819 --> 00:03:11.210 align:start position:0% an East the native token um<00:03:08.879> now<00:03:09.620> potentially<00:03:10.620> there<00:03:10.860> are<00:03:10.980> many<00:03:11.040> other 00:03:11.210 --> 00:03:11.220 align:start position:0% um now potentially there are many other 00:03:11.220 --> 00:03:12.890 align:start position:0% um now potentially there are many other ways<00:03:11.580> that<00:03:11.760> you<00:03:11.940> might<00:03:12.120> want<00:03:12.360> to<00:03:12.480> be<00:03:12.599> paying 00:03:12.890 --> 00:03:12.900 align:start position:0% ways that you might want to be paying 00:03:12.900 --> 00:03:14.509 align:start position:0% ways that you might want to be paying gas<00:03:13.019> if<00:03:13.319> you<00:03:13.440> hold<00:03:13.620> some<00:03:13.920> you<00:03:14.280> know<00:03:14.340> if<00:03:14.400> you're 00:03:14.509 --> 00:03:14.519 align:start position:0% gas if you hold some you know if you're 00:03:14.519 --> 00:03:16.790 align:start position:0% gas if you hold some you know if you're a<00:03:14.640> fan<00:03:14.760> of<00:03:14.940> dog<00:03:15.060> coins<00:03:15.480> maybe<00:03:16.260> you<00:03:16.500> want<00:03:16.620> to<00:03:16.680> pay 00:03:16.790 --> 00:03:16.800 align:start position:0% a fan of dog coins maybe you want to pay 00:03:16.800 --> 00:03:19.670 align:start position:0% a fan of dog coins maybe you want to pay gas<00:03:16.980> in<00:03:17.220> that<00:03:17.340> you<00:03:17.519> don't<00:03:17.640> want<00:03:17.700> to<00:03:17.819> hold<00:03:17.940> these 00:03:19.670 --> 00:03:19.680 align:start position:0% gas in that you don't want to hold these 00:03:19.680 --> 00:03:20.570 align:start position:0% gas in that you don't want to hold these um 00:03:20.570 --> 00:03:20.580 align:start position:0% um 00:03:20.580 --> 00:03:23.990 align:start position:0% um and<00:03:21.420> uh<00:03:22.379> the<00:03:22.560> other<00:03:22.680> limb<00:03:22.980> big<00:03:23.159> limitation<00:03:23.640> is 00:03:23.990 --> 00:03:24.000 align:start position:0% and uh the other limb big limitation is 00:03:24.000 --> 00:03:25.850 align:start position:0% and uh the other limb big limitation is that<00:03:24.360> well<00:03:24.720> if<00:03:24.900> you<00:03:25.019> do<00:03:25.140> have<00:03:25.260> to<00:03:25.440> maintain<00:03:25.739> an 00:03:25.850 --> 00:03:25.860 align:start position:0% that well if you do have to maintain an 00:03:25.860 --> 00:03:28.309 align:start position:0% that well if you do have to maintain an eat<00:03:26.040> balance<00:03:26.459> in<00:03:26.819> every<00:03:27.000> account<00:03:27.300> it's<00:03:28.140> hard 00:03:28.309 --> 00:03:28.319 align:start position:0% eat balance in every account it's hard 00:03:28.319 --> 00:03:29.750 align:start position:0% eat balance in every account it's hard to<00:03:28.440> split<00:03:28.680> up<00:03:28.739> your<00:03:28.920> activity<00:03:29.220> between<00:03:29.459> a<00:03:29.700> lot 00:03:29.750 --> 00:03:29.760 align:start position:0% to split up your activity between a lot 00:03:29.760 --> 00:03:31.369 align:start position:0% to split up your activity between a lot of<00:03:29.879> accounts<00:03:30.239> because<00:03:30.540> then<00:03:30.780> you<00:03:30.959> have<00:03:31.019> to<00:03:31.200> top 00:03:31.369 --> 00:03:31.379 align:start position:0% of accounts because then you have to top 00:03:31.379 --> 00:03:33.710 align:start position:0% of accounts because then you have to top off<00:03:31.620> faith<00:03:32.099> and<00:03:32.459> all<00:03:32.760> of<00:03:32.940> the<00:03:33.120> accounts<00:03:33.480> and 00:03:33.710 --> 00:03:33.720 align:start position:0% off faith and all of the accounts and 00:03:33.720 --> 00:03:35.449 align:start position:0% off faith and all of the accounts and the<00:03:33.959> eat<00:03:34.140> that<00:03:34.319> you<00:03:34.500> top<00:03:34.620> off<00:03:34.860> it<00:03:35.040> has<00:03:35.220> to<00:03:35.340> come 00:03:35.449 --> 00:03:35.459 align:start position:0% the eat that you top off it has to come 00:03:35.459 --> 00:03:38.089 align:start position:0% the eat that you top off it has to come from<00:03:35.640> somewhere<00:03:36.019> that's<00:03:37.019> probably<00:03:37.379> attached 00:03:38.089 --> 00:03:38.099 align:start position:0% from somewhere that's probably attached 00:03:38.099 --> 00:03:39.350 align:start position:0% from somewhere that's probably attached to<00:03:38.159> your<00:03:38.400> identity 00:03:39.350 --> 00:03:39.360 align:start position:0% to your identity 00:03:39.360 --> 00:03:42.830 align:start position:0% to your identity I<00:03:39.780> mean<00:03:39.980> kyc<00:03:40.980> at<00:03:41.280> exchanges 00:03:42.830 --> 00:03:42.840 align:start position:0% I mean kyc at exchanges 00:03:42.840 --> 00:03:44.750 align:start position:0% I mean kyc at exchanges um and<00:03:43.379> our<00:03:43.560> identity<00:03:43.920> is<00:03:44.099> known<00:03:44.280> to<00:03:44.459> at<00:03:44.640> least 00:03:44.750 --> 00:03:44.760 align:start position:0% um and our identity is known to at least 00:03:44.760 --> 00:03:47.149 align:start position:0% um and our identity is known to at least some<00:03:45.120> players<00:03:45.540> and<00:03:45.900> then<00:03:46.080> yeah<00:03:46.680> it's<00:03:46.860> not<00:03:47.040> too 00:03:47.149 --> 00:03:47.159 align:start position:0% some players and then yeah it's not too 00:03:47.159 --> 00:03:48.890 align:start position:0% some players and then yeah it's not too hard<00:03:47.340> to<00:03:47.459> track<00:03:47.700> and<00:03:47.940> even<00:03:48.239> if<00:03:48.420> we<00:03:48.540> split<00:03:48.840> up 00:03:48.890 --> 00:03:48.900 align:start position:0% hard to track and even if we split up 00:03:48.900 --> 00:03:50.930 align:start position:0% hard to track and even if we split up activity<00:03:49.379> oh<00:03:49.739> this<00:03:49.980> is<00:03:50.099> all<00:03:50.280> coming<00:03:50.459> from<00:03:50.760> One 00:03:50.930 --> 00:03:50.940 align:start position:0% activity oh this is all coming from One 00:03:50.940 --> 00:03:51.949 align:start position:0% activity oh this is all coming from One Source 00:03:51.949 --> 00:03:51.959 align:start position:0% Source 00:03:51.959 --> 00:03:55.070 align:start position:0% Source so<00:03:52.920> that's<00:03:53.340> a<00:03:53.519> privacy<00:03:53.879> problem<00:03:54.180> the<00:03:55.019> other 00:03:55.070 --> 00:03:55.080 align:start position:0% so that's a privacy problem the other 00:03:55.080 --> 00:03:57.710 align:start position:0% so that's a privacy problem the other big<00:03:55.319> limitation<00:03:55.799> of<00:03:55.980> EOS<00:03:56.340> is<00:03:57.000> just<00:03:57.239> in<00:03:57.480> terms 00:03:57.710 --> 00:03:57.720 align:start position:0% big limitation of EOS is just in terms 00:03:57.720 --> 00:03:58.990 align:start position:0% big limitation of EOS is just in terms of<00:03:57.780> efficiency 00:03:58.990 --> 00:03:59.000 align:start position:0% of efficiency 00:03:59.000 --> 00:04:02.170 align:start position:0% of efficiency many<00:04:00.000> times<00:04:00.299> what<00:04:00.959> you<00:04:01.140> actually<00:04:01.260> want<00:04:01.560> to<00:04:01.680> do 00:04:02.170 --> 00:04:02.180 align:start position:0% many times what you actually want to do 00:04:02.180 --> 00:04:05.449 align:start position:0% many times what you actually want to do it<00:04:03.180> spans<00:04:04.019> more<00:04:04.260> than<00:04:04.379> one<00:04:04.560> transaction<00:04:04.980> so 00:04:05.449 --> 00:04:05.459 align:start position:0% it spans more than one transaction so 00:04:05.459 --> 00:04:08.089 align:start position:0% it spans more than one transaction so let's<00:04:05.580> say<00:04:05.700> you<00:04:05.879> want<00:04:06.000> to<00:04:06.120> approve 00:04:08.089 --> 00:04:08.099 align:start position:0% let's say you want to approve 00:04:08.099 --> 00:04:10.130 align:start position:0% let's say you want to approve um<00:04:08.220> approve<00:04:08.819> and<00:04:09.120> then<00:04:09.299> you<00:04:09.480> want<00:04:09.659> to<00:04:09.780> transfer 00:04:10.130 --> 00:04:10.140 align:start position:0% um approve and then you want to transfer 00:04:10.140 --> 00:04:13.610 align:start position:0% um approve and then you want to transfer those<00:04:10.739> are<00:04:10.860> two<00:04:11.040> transactions<00:04:11.700> but 00:04:13.610 --> 00:04:13.620 align:start position:0% those are two transactions but 00:04:13.620 --> 00:04:15.530 align:start position:0% those are two transactions but um<00:04:13.680> really<00:04:14.040> you<00:04:14.459> you<00:04:14.519> are<00:04:15.060> thinking<00:04:15.299> of<00:04:15.360> them 00:04:15.530 --> 00:04:15.540 align:start position:0% um really you you are thinking of them 00:04:15.540 --> 00:04:17.750 align:start position:0% um really you you are thinking of them as<00:04:15.659> one<00:04:15.840> operation<00:04:16.260> with<00:04:16.859> the<00:04:17.040> OAS<00:04:17.400> you<00:04:17.699> would 00:04:17.750 --> 00:04:17.760 align:start position:0% as one operation with the OAS you would 00:04:17.760 --> 00:04:19.370 align:start position:0% as one operation with the OAS you would have<00:04:17.880> to<00:04:18.000> send<00:04:18.180> two<00:04:18.419> separate<00:04:18.780> transactions 00:04:19.370 --> 00:04:19.380 align:start position:0% have to send two separate transactions 00:04:19.380 --> 00:04:20.629 align:start position:0% have to send two separate transactions and 00:04:20.629 --> 00:04:20.639 align:start position:0% and 00:04:20.639 --> 00:04:23.150 align:start position:0% and um<00:04:20.699> you<00:04:21.060> know<00:04:21.120> that<00:04:21.299> that<00:04:21.479> might<00:04:21.720> not<00:04:21.840> work<00:04:22.079> out 00:04:23.150 --> 00:04:23.160 align:start position:0% um you know that that might not work out 00:04:23.160 --> 00:04:24.590 align:start position:0% um you know that that might not work out um<00:04:23.220> it<00:04:23.460> also<00:04:23.759> might<00:04:24.000> be<00:04:24.120> a<00:04:24.240> little<00:04:24.300> bit<00:04:24.419> more 00:04:24.590 --> 00:04:24.600 align:start position:0% um it also might be a little bit more 00:04:24.600 --> 00:04:26.749 align:start position:0% um it also might be a little bit more expensive<00:04:25.020> because<00:04:25.620> of<00:04:25.860> that<00:04:26.040> but<00:04:26.400> there's<00:04:26.580> no 00:04:26.749 --> 00:04:26.759 align:start position:0% expensive because of that but there's no 00:04:26.759 --> 00:04:28.790 align:start position:0% expensive because of that but there's no optimicity 00:04:28.790 --> 00:04:28.800 align:start position:0% optimicity 00:04:28.800 --> 00:04:29.390 align:start position:0% optimicity um 00:04:29.390 --> 00:04:29.400 align:start position:0% um 00:04:29.400 --> 00:04:33.890 align:start position:0% um um<00:04:29.580> built<00:04:30.540> in<00:04:30.600> and<00:04:31.259> if<00:04:31.800> there<00:04:31.979> is<00:04:32.160> a<00:04:33.000> revert<00:04:33.479> on 00:04:33.890 --> 00:04:33.900 align:start position:0% um built in and if there is a revert on 00:04:33.900 --> 00:04:36.650 align:start position:0% um built in and if there is a revert on chain<00:04:34.080> that's<00:04:34.380> pretty<00:04:34.620> expensive 00:04:36.650 --> 00:04:36.660 align:start position:0% chain that's pretty expensive 00:04:36.660 --> 00:04:38.390 align:start position:0% chain that's pretty expensive um<00:04:36.780> so<00:04:37.440> and<00:04:37.680> that<00:04:37.800> happens<00:04:37.979> sometimes 00:04:38.390 --> 00:04:38.400 align:start position:0% um so and that happens sometimes 00:04:38.400 --> 00:04:40.370 align:start position:0% um so and that happens sometimes especially<00:04:38.820> with<00:04:39.060> things<00:04:39.300> that<00:04:39.600> are<00:04:39.840> very 00:04:40.370 --> 00:04:40.380 align:start position:0% especially with things that are very 00:04:40.380 --> 00:04:41.689 align:start position:0% especially with things that are very time<00:04:40.620> sensitive 00:04:41.689 --> 00:04:41.699 align:start position:0% time sensitive 00:04:41.699 --> 00:04:44.330 align:start position:0% time sensitive so<00:04:42.419> what<00:04:43.139> is<00:04:43.259> the<00:04:43.440> alternative<00:04:43.800> what<00:04:44.220> is 00:04:44.330 --> 00:04:44.340 align:start position:0% so what is the alternative what is 00:04:44.340 --> 00:04:47.629 align:start position:0% so what is the alternative what is account<00:04:44.580> obstruction<00:04:45.139> well<00:04:46.460> basically<00:04:47.460> what 00:04:47.629 --> 00:04:47.639 align:start position:0% account obstruction well basically what 00:04:47.639 --> 00:04:51.170 align:start position:0% account obstruction well basically what we're<00:04:47.820> saying<00:04:48.120> is<00:04:48.300> you<00:04:48.600> know<00:04:48.720> eoas<00:04:49.320> are 00:04:51.170 --> 00:04:51.180 align:start position:0% we're saying is you know eoas are 00:04:51.180 --> 00:04:53.830 align:start position:0% we're saying is you know eoas are um<00:04:51.300> they're<00:04:52.020> the<00:04:52.199> one<00:04:52.500> size<00:04:52.740> fits<00:04:53.280> all<00:04:53.340> past 00:04:53.830 --> 00:04:53.840 align:start position:0% um they're the one size fits all past 00:04:53.840 --> 00:04:56.270 align:start position:0% um they're the one size fits all past and<00:04:54.840> we<00:04:55.080> want<00:04:55.259> to<00:04:55.320> move<00:04:55.440> Beyond<00:04:55.740> them<00:04:55.860> to<00:04:56.100> a 00:04:56.270 --> 00:04:56.280 align:start position:0% and we want to move Beyond them to a 00:04:56.280 --> 00:04:58.010 align:start position:0% and we want to move Beyond them to a world<00:04:56.400> where 00:04:58.010 --> 00:04:58.020 align:start position:0% world where 00:04:58.020 --> 00:05:00.469 align:start position:0% world where um<00:04:58.080> we<00:04:58.320> can<00:04:58.440> really<00:04:58.560> manage<00:04:59.040> the<00:04:59.460> logic<00:04:59.820> uh 00:05:00.469 --> 00:05:00.479 align:start position:0% um we can really manage the logic uh 00:05:00.479 --> 00:05:02.330 align:start position:0% um we can really manage the logic uh that<00:05:00.720> controls<00:05:01.139> our<00:05:01.259> account<00:05:01.440> and<00:05:01.979> the<00:05:02.100> logic 00:05:02.330 --> 00:05:02.340 align:start position:0% that controls our account and the logic 00:05:02.340 --> 00:05:05.090 align:start position:0% that controls our account and the logic can<00:05:02.520> be<00:05:02.639> pretty<00:05:02.759> arbitrary<00:05:03.860> and<00:05:04.860> then<00:05:04.979> that 00:05:05.090 --> 00:05:05.100 align:start position:0% can be pretty arbitrary and then that 00:05:05.100 --> 00:05:07.850 align:start position:0% can be pretty arbitrary and then that opens<00:05:05.400> up<00:05:05.520> a<00:05:05.639> lot<00:05:05.759> of<00:05:05.880> possibilities<00:05:06.360> and 00:05:07.850 --> 00:05:07.860 align:start position:0% opens up a lot of possibilities and 00:05:07.860 --> 00:05:09.950 align:start position:0% opens up a lot of possibilities and that<00:05:08.400> is<00:05:08.520> the<00:05:08.699> future<00:05:08.820> of<00:05:09.180> how<00:05:09.419> accounts<00:05:09.900> are 00:05:09.950 --> 00:05:09.960 align:start position:0% that is the future of how accounts are 00:05:09.960 --> 00:05:12.050 align:start position:0% that is the future of how accounts are going<00:05:10.139> to<00:05:10.320> work<00:05:10.500> so<00:05:11.160> what<00:05:11.340> are<00:05:11.460> the<00:05:11.580> use<00:05:11.699> cases 00:05:12.050 --> 00:05:12.060 align:start position:0% going to work so what are the use cases 00:05:12.060 --> 00:05:13.010 align:start position:0% going to work so what are the use cases for<00:05:12.240> this 00:05:13.010 --> 00:05:13.020 align:start position:0% for this 00:05:13.020 --> 00:05:14.270 align:start position:0% for this um<00:05:13.080> you<00:05:13.259> know<00:05:13.380> the<00:05:13.500> one<00:05:13.620> that's<00:05:13.740> been<00:05:13.979> talked 00:05:14.270 --> 00:05:14.280 align:start position:0% um you know the one that's been talked 00:05:14.280 --> 00:05:15.710 align:start position:0% um you know the one that's been talked about<00:05:14.340> since<00:05:14.940> the<00:05:15.120> beginning<00:05:15.240> of<00:05:15.540> social 00:05:15.710 --> 00:05:15.720 align:start position:0% about since the beginning of social 00:05:15.720 --> 00:05:16.850 align:start position:0% about since the beginning of social recovery 00:05:16.850 --> 00:05:16.860 align:start position:0% recovery 00:05:16.860 --> 00:05:19.430 align:start position:0% recovery like<00:05:17.220> let's<00:05:17.400> say<00:05:17.580> something<00:05:17.820> bad<00:05:18.120> happens 00:05:19.430 --> 00:05:19.440 align:start position:0% like let's say something bad happens 00:05:19.440 --> 00:05:20.990 align:start position:0% like let's say something bad happens um<00:05:19.560> to<00:05:19.740> that<00:05:19.919> secret<00:05:20.160> that<00:05:20.520> you're<00:05:20.639> trying<00:05:20.820> to 00:05:20.990 --> 00:05:21.000 align:start position:0% um to that secret that you're trying to 00:05:21.000 --> 00:05:22.969 align:start position:0% um to that secret that you're trying to both<00:05:21.240> prevent<00:05:21.900> from<00:05:22.080> being<00:05:22.259> lost<00:05:22.500> and<00:05:22.800> from 00:05:22.969 --> 00:05:22.979 align:start position:0% both prevent from being lost and from 00:05:22.979 --> 00:05:24.409 align:start position:0% both prevent from being lost and from being<00:05:23.220> stolen 00:05:24.409 --> 00:05:24.419 align:start position:0% being stolen 00:05:24.419 --> 00:05:27.529 align:start position:0% being stolen well<00:05:24.960> maybe<00:05:25.199> you<00:05:25.500> have<00:05:25.800> some<00:05:26.520> friends<00:05:26.820> that 00:05:27.529 --> 00:05:27.539 align:start position:0% well maybe you have some friends that 00:05:27.539 --> 00:05:30.409 align:start position:0% well maybe you have some friends that you<00:05:27.720> plugged<00:05:28.139> into<00:05:28.860> your<00:05:29.280> account<00:05:29.460> and<00:05:30.180> three 00:05:30.409 --> 00:05:30.419 align:start position:0% you plugged into your account and three 00:05:30.419 --> 00:05:32.830 align:start position:0% you plugged into your account and three out<00:05:30.600> of<00:05:30.780> five<00:05:30.900> of<00:05:31.080> them<00:05:31.259> can<00:05:31.740> help<00:05:31.979> you 00:05:32.830 --> 00:05:32.840 align:start position:0% out of five of them can help you 00:05:32.840 --> 00:05:36.350 align:start position:0% out of five of them can help you restore<00:05:33.840> your<00:05:34.560> wallet 00:05:36.350 --> 00:05:36.360 align:start position:0% restore your wallet 00:05:36.360 --> 00:05:38.090 align:start position:0% restore your wallet um<00:05:36.479> and<00:05:36.660> you<00:05:36.780> can<00:05:36.900> do<00:05:37.020> even<00:05:37.259> fancier<00:05:37.800> things 00:05:38.090 --> 00:05:38.100 align:start position:0% um and you can do even fancier things 00:05:38.100 --> 00:05:40.010 align:start position:0% um and you can do even fancier things let's<00:05:38.340> say<00:05:38.520> your<00:05:38.699> friends<00:05:38.880> suck 00:05:40.010 --> 00:05:40.020 align:start position:0% let's say your friends suck 00:05:40.020 --> 00:05:41.510 align:start position:0% let's say your friends suck and<00:05:40.380> they're<00:05:40.680> trying<00:05:40.860> to<00:05:40.979> steal<00:05:41.160> your<00:05:41.280> money 00:05:41.510 --> 00:05:41.520 align:start position:0% and they're trying to steal your money 00:05:41.520 --> 00:05:43.010 align:start position:0% and they're trying to steal your money well<00:05:41.759> you<00:05:41.940> could<00:05:42.060> have<00:05:42.180> a<00:05:42.360> delay<00:05:42.600> mechanism 00:05:43.010 --> 00:05:43.020 align:start position:0% well you could have a delay mechanism 00:05:43.020 --> 00:05:46.370 align:start position:0% well you could have a delay mechanism built<00:05:43.380> in<00:05:43.860> so<00:05:44.699> if<00:05:45.240> your<00:05:45.600> friend<00:05:45.780> suddenly<00:05:46.199> try 00:05:46.370 --> 00:05:46.380 align:start position:0% built in so if your friend suddenly try 00:05:46.380 --> 00:05:48.050 align:start position:0% built in so if your friend suddenly try to<00:05:46.560> recover<00:05:46.860> your<00:05:47.280> wallet<00:05:47.520> when<00:05:47.759> you<00:05:47.940> don't 00:05:48.050 --> 00:05:48.060 align:start position:0% to recover your wallet when you don't 00:05:48.060 --> 00:05:50.450 align:start position:0% to recover your wallet when you don't need<00:05:48.180> a<00:05:48.360> recovery<00:05:48.720> you<00:05:49.500> as<00:05:49.680> the<00:05:49.860> account<00:05:49.979> owner 00:05:50.450 --> 00:05:50.460 align:start position:0% need a recovery you as the account owner 00:05:50.460 --> 00:05:52.550 align:start position:0% need a recovery you as the account owner would<00:05:51.060> see<00:05:51.240> that<00:05:51.419> in<00:05:51.600> advance<00:05:51.780> and<00:05:52.320> the 00:05:52.550 --> 00:05:52.560 align:start position:0% would see that in advance and the 00:05:52.560 --> 00:05:55.129 align:start position:0% would see that in advance and the operation<00:05:52.919> wouldn't<00:05:53.419> happen<00:05:54.419> immediately<00:05:54.900> so 00:05:55.129 --> 00:05:55.139 align:start position:0% operation wouldn't happen immediately so 00:05:55.139 --> 00:05:56.810 align:start position:0% operation wouldn't happen immediately so you<00:05:55.320> would<00:05:55.380> have<00:05:55.560> time<00:05:55.800> let's<00:05:56.280> say<00:05:56.400> maybe<00:05:56.580> a 00:05:56.810 --> 00:05:56.820 align:start position:0% you would have time let's say maybe a 00:05:56.820 --> 00:05:57.529 align:start position:0% you would have time let's say maybe a week 00:05:57.529 --> 00:05:57.539 align:start position:0% week 00:05:57.539 --> 00:05:59.629 align:start position:0% week to<00:05:58.080> respond<00:05:58.380> to<00:05:58.500> that 00:05:59.629 --> 00:05:59.639 align:start position:0% to respond to that 00:05:59.639 --> 00:06:03.290 align:start position:0% to respond to that the<00:06:00.240> other<00:06:00.360> really<00:06:01.320> interesting<00:06:01.680> use<00:06:01.979> case<00:06:02.300> is 00:06:03.290 --> 00:06:03.300 align:start position:0% the other really interesting use case is 00:06:03.300 --> 00:06:05.450 align:start position:0% the other really interesting use case is a<00:06:03.900> dead<00:06:04.080> demand<00:06:04.380> switch 00:06:05.450 --> 00:06:05.460 align:start position:0% a dead demand switch 00:06:05.460 --> 00:06:09.350 align:start position:0% a dead demand switch nobody<00:06:06.180> lives<00:06:06.960> forever<00:06:07.320> unfortunately<00:06:08.360> and 00:06:09.350 --> 00:06:09.360 align:start position:0% nobody lives forever unfortunately and 00:06:09.360 --> 00:06:12.830 align:start position:0% nobody lives forever unfortunately and then<00:06:09.600> what<00:06:10.440> happens<00:06:10.620> if<00:06:11.220> what<00:06:12.060> happens<00:06:12.240> if<00:06:12.600> you 00:06:12.830 --> 00:06:12.840 align:start position:0% then what happens if what happens if you 00:06:12.840 --> 00:06:17.090 align:start position:0% then what happens if what happens if you know<00:06:12.960> you<00:06:13.820> you<00:06:14.820> need<00:06:15.120> to<00:06:15.300> to<00:06:15.720> pass<00:06:16.020> on 00:06:17.090 --> 00:06:17.100 align:start position:0% know you you need to to pass on 00:06:17.100 --> 00:06:19.010 align:start position:0% know you you need to to pass on um<00:06:17.160> your<00:06:17.820> your<00:06:18.000> crypto<00:06:18.419> but<00:06:18.780> you're<00:06:18.900> not 00:06:19.010 --> 00:06:19.020 align:start position:0% um your your crypto but you're not 00:06:19.020 --> 00:06:21.309 align:start position:0% um your your crypto but you're not around<00:06:19.199> to<00:06:19.500> help<00:06:19.800> do<00:06:20.039> that 00:06:21.309 --> 00:06:21.319 align:start position:0% around to help do that 00:06:21.319 --> 00:06:23.930 align:start position:0% around to help do that so<00:06:22.319> with<00:06:22.919> the<00:06:23.100> dead<00:06:23.220> man<00:06:23.400> switch<00:06:23.639> you<00:06:23.880> could 00:06:23.930 --> 00:06:23.940 align:start position:0% so with the dead man switch you could 00:06:23.940 --> 00:06:25.309 align:start position:0% so with the dead man switch you could have<00:06:24.060> a<00:06:24.240> mechanism<00:06:24.600> like<00:06:24.780> okay<00:06:25.020> if<00:06:25.199> you 00:06:25.309 --> 00:06:25.319 align:start position:0% have a mechanism like okay if you 00:06:25.319 --> 00:06:27.350 align:start position:0% have a mechanism like okay if you haven't<00:06:25.440> accessed<00:06:26.100> your<00:06:26.460> account<00:06:26.639> from<00:06:27.180> your 00:06:27.350 --> 00:06:27.360 align:start position:0% haven't accessed your account from your 00:06:27.360 --> 00:06:31.850 align:start position:0% haven't accessed your account from your main<00:06:27.539> key<00:06:27.840> for<00:06:28.560> the<00:06:28.740> last<00:06:28.919> year<00:06:29.479> then<00:06:30.860> another 00:06:31.850 --> 00:06:31.860 align:start position:0% main key for the last year then another 00:06:31.860 --> 00:06:34.670 align:start position:0% main key for the last year then another key<00:06:32.340> that<00:06:32.940> your<00:06:33.780> family<00:06:33.960> members<00:06:34.319> have<00:06:34.500> access 00:06:34.670 --> 00:06:34.680 align:start position:0% key that your family members have access 00:06:34.680 --> 00:06:36.770 align:start position:0% key that your family members have access to 00:06:36.770 --> 00:06:36.780 align:start position:0% to 00:06:36.780 --> 00:06:39.170 align:start position:0% to um<00:06:36.900> it<00:06:37.800> would<00:06:37.860> become<00:06:38.160> active<00:06:38.580> so<00:06:38.880> usually 00:06:39.170 --> 00:06:39.180 align:start position:0% um it would become active so usually 00:06:39.180 --> 00:06:40.730 align:start position:0% um it would become active so usually you're<00:06:39.360> in<00:06:39.600> control<00:06:39.780> full<00:06:40.139> control<00:06:40.380> of<00:06:40.620> your 00:06:40.730 --> 00:06:40.740 align:start position:0% you're in control full control of your 00:06:40.740 --> 00:06:43.909 align:start position:0% you're in control full control of your account<00:06:40.979> but<00:06:41.880> then<00:06:42.120> a<00:06:42.960> year<00:06:43.139> later<00:06:43.319> you 00:06:43.909 --> 00:06:43.919 align:start position:0% account but then a year later you 00:06:43.919 --> 00:06:45.710 align:start position:0% account but then a year later you haven't<00:06:44.100> been<00:06:44.400> active<00:06:44.699> something<00:06:45.360> wrong 00:06:45.710 --> 00:06:45.720 align:start position:0% haven't been active something wrong 00:06:45.720 --> 00:06:48.050 align:start position:0% haven't been active something wrong happened<00:06:46.220> your<00:06:47.220> account<00:06:47.460> automatically 00:06:48.050 --> 00:06:48.060 align:start position:0% happened your account automatically 00:06:48.060 --> 00:06:50.029 align:start position:0% happened your account automatically passes<00:06:48.539> to<00:06:48.840> multi-set<00:06:49.440> controlled<00:06:49.800> by<00:06:49.860> your 00:06:50.029 --> 00:06:50.039 align:start position:0% passes to multi-set controlled by your 00:06:50.039 --> 00:06:52.309 align:start position:0% passes to multi-set controlled by your family<00:06:50.220> I<00:06:51.000> just<00:06:51.240> one<00:06:51.360> thing<00:06:51.600> I<00:06:51.840> want<00:06:52.199> to 00:06:52.309 --> 00:06:52.319 align:start position:0% family I just one thing I want to 00:06:52.319 --> 00:06:55.129 align:start position:0% family I just one thing I want to explain<00:06:52.460> these<00:06:53.460> are<00:06:53.520> all<00:06:53.699> features<00:06:54.180> of<00:06:54.780> that 00:06:55.129 --> 00:06:55.139 align:start position:0% explain these are all features of that 00:06:55.139 --> 00:06:57.890 align:start position:0% explain these are all features of that account<00:06:55.319> abstraction<00:06:55.860> can<00:06:56.100> give<00:06:56.280> but<00:06:56.940> it<00:06:57.479> it's 00:06:57.890 --> 00:06:57.900 align:start position:0% account abstraction can give but it it's 00:06:57.900 --> 00:06:59.629 align:start position:0% account abstraction can give but it it's not<00:06:58.139> that<00:06:58.440> everything<00:06:58.680> is<00:06:58.919> Comfortably<00:06:59.340> baked 00:06:59.629 --> 00:06:59.639 align:start position:0% not that everything is Comfortably baked 00:06:59.639 --> 00:07:01.370 align:start position:0% not that everything is Comfortably baked in<00:06:59.759> these<00:07:00.300> are<00:07:00.419> counter<00:07:00.840> possession<00:07:01.080> or 00:07:01.370 --> 00:07:01.380 align:start position:0% in these are counter possession or 00:07:01.380 --> 00:07:04.430 align:start position:0% in these are counter possession or accountability<00:07:02.280> opens<00:07:02.880> the<00:07:03.180> the<00:07:03.479> door<00:07:03.780> for 00:07:04.430 --> 00:07:04.440 align:start position:0% accountability opens the the door for 00:07:04.440 --> 00:07:06.290 align:start position:0% accountability opens the the door for wallet<00:07:04.860> creators<00:07:05.280> to<00:07:05.699> add<00:07:05.880> all<00:07:06.180> those 00:07:06.290 --> 00:07:06.300 align:start position:0% wallet creators to add all those 00:07:06.300 --> 00:07:08.570 align:start position:0% wallet creators to add all those features<00:07:06.720> none<00:07:07.560> of<00:07:07.680> those<00:07:07.860> features<00:07:08.340> are 00:07:08.570 --> 00:07:08.580 align:start position:0% features none of those features are 00:07:08.580 --> 00:07:11.150 align:start position:0% features none of those features are something<00:07:08.759> that<00:07:09.360> will<00:07:09.720> be<00:07:09.900> on<00:07:10.500> day<00:07:10.620> one<00:07:10.800> maybe 00:07:11.150 --> 00:07:11.160 align:start position:0% something that will be on day one maybe 00:07:11.160 --> 00:07:14.570 align:start position:0% something that will be on day one maybe a<00:07:11.580> limited<00:07:11.940> set<00:07:12.060> these<00:07:12.780> are<00:07:12.900> options 00:07:14.570 --> 00:07:14.580 align:start position:0% a limited set these are options 00:07:14.580 --> 00:07:18.110 align:start position:0% a limited set these are options that<00:07:15.000> are<00:07:15.120> open<00:07:15.300> to<00:07:15.600> do<00:07:15.840> more<00:07:15.979> oh<00:07:16.979> now<00:07:17.580> we<00:07:17.759> can 00:07:18.110 --> 00:07:18.120 align:start position:0% that are open to do more oh now we can 00:07:18.120 --> 00:07:20.089 align:start position:0% that are open to do more oh now we can both<00:07:18.240> talk<00:07:18.419> even<00:07:18.660> if<00:07:18.960> we<00:07:19.319> can<00:07:19.500> talk<00:07:19.620> over<00:07:19.800> each 00:07:20.089 --> 00:07:20.099 align:start position:0% both talk even if we can talk over each 00:07:20.099 --> 00:07:21.529 align:start position:0% both talk even if we can talk over each other<00:07:20.160> if<00:07:20.400> we<00:07:20.520> need<00:07:20.639> to<00:07:20.699> okay 00:07:21.529 --> 00:07:21.539 align:start position:0% other if we need to okay 00:07:21.539 --> 00:07:23.990 align:start position:0% other if we need to okay that's<00:07:22.380> a<00:07:22.500> good<00:07:22.620> point<00:07:22.800> I<00:07:23.340> was<00:07:23.460> talking<00:07:23.639> to<00:07:23.880> you 00:07:23.990 --> 00:07:24.000 align:start position:0% that's a good point I was talking to you 00:07:24.000 --> 00:07:25.909 align:start position:0% that's a good point I was talking to you off<00:07:24.120> about<00:07:24.360> that<00:07:24.660> when<00:07:25.259> you're<00:07:25.380> preparing<00:07:25.800> for 00:07:25.909 --> 00:07:25.919 align:start position:0% off about that when you're preparing for 00:07:25.919 --> 00:07:27.650 align:start position:0% off about that when you're preparing for the<00:07:26.099> talk 00:07:27.650 --> 00:07:27.660 align:start position:0% the talk 00:07:27.660 --> 00:07:29.809 align:start position:0% the talk um<00:07:27.780> this<00:07:28.139> is<00:07:28.259> oh<00:07:28.680> yeah<00:07:28.860> maybe<00:07:29.099> that<00:07:29.580> would<00:07:29.699> be 00:07:29.809 --> 00:07:29.819 align:start position:0% um this is oh yeah maybe that would be 00:07:29.819 --> 00:07:30.469 align:start position:0% um this is oh yeah maybe that would be nice 00:07:30.469 --> 00:07:30.479 align:start position:0% nice 00:07:30.479 --> 00:07:32.990 align:start position:0% nice so<00:07:31.319> that's<00:07:31.560> a<00:07:31.740> really<00:07:31.860> good<00:07:32.039> point 00:07:32.990 --> 00:07:33.000 align:start position:0% so that's a really good point 00:07:33.000 --> 00:07:35.029 align:start position:0% so that's a really good point um<00:07:33.060> this<00:07:33.300> talk<00:07:33.479> is<00:07:33.900> intended<00:07:34.259> to<00:07:34.440> inspire<00:07:34.740> hey 00:07:35.029 --> 00:07:35.039 align:start position:0% um this talk is intended to inspire hey 00:07:35.039 --> 00:07:37.070 align:start position:0% um this talk is intended to inspire hey like<00:07:35.280> we<00:07:35.400> can<00:07:35.520> do<00:07:35.699> these<00:07:35.940> things<00:07:36.120> now 00:07:37.070 --> 00:07:37.080 align:start position:0% like we can do these things now 00:07:37.080 --> 00:07:38.450 align:start position:0% like we can do these things now um<00:07:37.139> but<00:07:37.259> we<00:07:37.440> have<00:07:37.620> this 00:07:38.450 --> 00:07:38.460 align:start position:0% um but we have this 00:07:38.460 --> 00:07:42.230 align:start position:0% um but we have this um<00:07:38.580> this<00:07:39.240> infrastructure<00:07:39.780> built<00:07:40.259> in<00:07:40.380> but 00:07:42.230 --> 00:07:42.240 align:start position:0% um this infrastructure built in but 00:07:42.240 --> 00:07:44.330 align:start position:0% um this infrastructure built in but um<00:07:42.300> this<00:07:42.960> all<00:07:43.080> depends<00:07:43.500> on<00:07:43.740> the<00:07:43.919> code<00:07:44.039> that's 00:07:44.330 --> 00:07:44.340 align:start position:0% um this all depends on the code that's 00:07:44.340 --> 00:07:45.770 align:start position:0% um this all depends on the code that's running 00:07:45.770 --> 00:07:45.780 align:start position:0% running 00:07:45.780 --> 00:07:49.370 align:start position:0% running um<00:07:45.960> your<00:07:46.199> your<00:07:46.740> your<00:07:46.860> smart<00:07:47.819> Wallet<00:07:48.240> account 00:07:49.370 --> 00:07:49.380 align:start position:0% um your your your smart Wallet account 00:07:49.380 --> 00:07:52.010 align:start position:0% um your your your smart Wallet account and<00:07:50.340> that's<00:07:50.759> up<00:07:50.940> to<00:07:51.060> wall<00:07:51.240> developers<00:07:51.720> that's 00:07:52.010 --> 00:07:52.020 align:start position:0% and that's up to wall developers that's 00:07:52.020 --> 00:07:55.330 align:start position:0% and that's up to wall developers that's up<00:07:52.319> to<00:07:52.580> anyone<00:07:53.580> that<00:07:53.759> wants<00:07:54.000> to<00:07:54.060> get<00:07:54.240> involved 00:07:55.330 --> 00:07:55.340 align:start position:0% up to anyone that wants to get involved 00:07:55.340 --> 00:08:00.110 align:start position:0% up to anyone that wants to get involved and<00:07:56.340> most<00:07:57.300> likely<00:07:57.599> there<00:07:57.780> are<00:07:57.900> many<00:07:58.020> use<00:07:58.259> cases 00:08:00.110 --> 00:08:00.120 align:start position:0% and most likely there are many use cases 00:08:00.120 --> 00:08:01.490 align:start position:0% and most likely there are many use cases um that<00:08:00.419> are<00:08:00.539> interesting<00:08:00.840> that<00:08:01.139> will<00:08:01.259> not<00:08:01.380> be 00:08:01.490 --> 00:08:01.500 align:start position:0% um that are interesting that will not be 00:08:01.500 --> 00:08:04.850 align:start position:0% um that are interesting that will not be covered<00:08:01.800> by<00:08:01.979> this<00:08:02.160> talk<00:08:02.539> so<00:08:03.539> use<00:08:04.020> you<00:08:04.620> know<00:08:04.740> the 00:08:04.850 --> 00:08:04.860 align:start position:0% covered by this talk so use you know the 00:08:04.860 --> 00:08:08.570 align:start position:0% covered by this talk so use you know the sky's<00:08:05.340> the<00:08:05.520> limit<00:08:05.639> in<00:08:05.819> terms<00:08:06.000> of<00:08:06.120> imagination 00:08:08.570 --> 00:08:08.580 align:start position:0% sky's the limit in terms of imagination 00:08:08.580 --> 00:08:10.490 align:start position:0% sky's the limit in terms of imagination um<00:08:08.699> but<00:08:09.000> we<00:08:09.120> would<00:08:09.300> like<00:08:09.479> to<00:08:09.660> talk<00:08:10.080> about<00:08:10.259> some 00:08:10.490 --> 00:08:10.500 align:start position:0% um but we would like to talk about some 00:08:10.500 --> 00:08:11.749 align:start position:0% um but we would like to talk about some of<00:08:10.620> the<00:08:10.680> use<00:08:10.860> cases<00:08:11.160> that<00:08:11.400> we've<00:08:11.580> been 00:08:11.749 --> 00:08:11.759 align:start position:0% of the use cases that we've been 00:08:11.759 --> 00:08:13.969 align:start position:0% of the use cases that we've been thinking<00:08:12.000> about<00:08:12.199> so<00:08:13.199> one<00:08:13.500> of<00:08:13.620> the<00:08:13.680> cool<00:08:13.800> things 00:08:13.969 --> 00:08:13.979 align:start position:0% thinking about so one of the cool things 00:08:13.979 --> 00:08:17.210 align:start position:0% thinking about so one of the cool things that<00:08:14.160> happened<00:08:14.340> uh<00:08:15.000> during<00:08:15.180> each<00:08:15.419> Bogota<00:08:16.220> is 00:08:17.210 --> 00:08:17.220 align:start position:0% that happened uh during each Bogota is 00:08:17.220 --> 00:08:19.070 align:start position:0% that happened uh during each Bogota is there<00:08:17.580> was<00:08:17.699> a<00:08:17.880> project<00:08:18.000> that<00:08:18.300> implemented<00:08:18.780> an 00:08:19.070 --> 00:08:19.080 align:start position:0% there was a project that implemented an 00:08:19.080 --> 00:08:21.170 align:start position:0% there was a project that implemented an idea<00:08:19.319> that<00:08:19.500> we've<00:08:20.220> um<00:08:20.220> I've<00:08:20.819> been<00:08:20.940> thinking 00:08:21.170 --> 00:08:21.180 align:start position:0% idea that we've um I've been thinking 00:08:21.180 --> 00:08:24.050 align:start position:0% idea that we've um I've been thinking would<00:08:21.360> be<00:08:21.479> pretty<00:08:21.660> cool<00:08:21.840> is 00:08:24.050 --> 00:08:24.060 align:start position:0% would be pretty cool is 00:08:24.060 --> 00:08:26.570 align:start position:0% would be pretty cool is um<00:08:24.120> well<00:08:24.360> there's<00:08:24.740> there's<00:08:25.740> this<00:08:26.039> signing 00:08:26.570 --> 00:08:26.580 align:start position:0% um well there's there's this signing 00:08:26.580 --> 00:08:28.909 align:start position:0% um well there's there's this signing mechanism<00:08:26.879> in<00:08:27.120> most<00:08:27.360> mobile<00:08:27.660> phones<00:08:28.199> the 00:08:28.909 --> 00:08:28.919 align:start position:0% mechanism in most mobile phones the 00:08:28.919 --> 00:08:30.529 align:start position:0% mechanism in most mobile phones the problem<00:08:29.099> is<00:08:29.340> the<00:08:29.520> signing<00:08:29.819> mechanism<00:08:30.240> doesn't 00:08:30.529 --> 00:08:30.539 align:start position:0% problem is the signing mechanism doesn't 00:08:30.539 --> 00:08:34.430 align:start position:0% problem is the signing mechanism doesn't support<00:08:31.159> ecdsa<00:08:32.159> curves<00:08:32.520> so<00:08:33.180> it's<00:08:33.539> it's<00:08:33.839> using 00:08:34.430 --> 00:08:34.440 align:start position:0% support ecdsa curves so it's it's using 00:08:34.440 --> 00:08:37.010 align:start position:0% support ecdsa curves so it's it's using some<00:08:34.620> other<00:08:34.800> mechanism 00:08:37.010 --> 00:08:37.020 align:start position:0% some other mechanism 00:08:37.020 --> 00:08:39.290 align:start position:0% some other mechanism um<00:08:37.140> but<00:08:37.620> because<00:08:37.860> account<00:08:38.820> obstruction 00:08:39.290 --> 00:08:39.300 align:start position:0% um but because account obstruction 00:08:39.300 --> 00:08:43.010 align:start position:0% um but because account obstruction doesn't<00:08:39.779> lock<00:08:40.260> in<00:08:40.440> ecdsa<00:08:41.339> as<00:08:42.300> the<00:08:42.599> only<00:08:42.659> way<00:08:42.839> to 00:08:43.010 --> 00:08:43.020 align:start position:0% doesn't lock in ecdsa as the only way to 00:08:43.020 --> 00:08:46.130 align:start position:0% doesn't lock in ecdsa as the only way to sign<00:08:43.200> what<00:08:43.680> you<00:08:43.860> can<00:08:43.979> do<00:08:44.240> is<00:08:45.240> you<00:08:45.720> can<00:08:45.839> have 00:08:46.130 --> 00:08:46.140 align:start position:0% sign what you can do is you can have 00:08:46.140 --> 00:08:48.949 align:start position:0% sign what you can do is you can have pair<00:08:46.680> device<00:08:46.980> Keys 00:08:48.949 --> 00:08:48.959 align:start position:0% pair device Keys 00:08:48.959 --> 00:08:51.410 align:start position:0% pair device Keys um<00:08:49.019> that<00:08:49.740> essentially<00:08:50.519> you<00:08:50.940> know<00:08:51.060> you<00:08:51.180> get 00:08:51.410 --> 00:08:51.420 align:start position:0% um that essentially you know you get 00:08:51.420 --> 00:08:53.509 align:start position:0% um that essentially you know you get your<00:08:51.600> phone<00:08:51.839> and<00:08:52.560> you<00:08:52.800> link<00:08:52.980> your<00:08:53.160> phone<00:08:53.339> to 00:08:53.509 --> 00:08:53.519 align:start position:0% your phone and you link your phone to 00:08:53.519 --> 00:08:55.910 align:start position:0% your phone and you link your phone to your<00:08:53.640> account<00:08:53.880> now<00:08:54.779> your<00:08:55.080> phone<00:08:55.320> can 00:08:55.910 --> 00:08:55.920 align:start position:0% your account now your phone can 00:08:55.920 --> 00:09:00.050 align:start position:0% your account now your phone can authorize<00:08:56.779> operations<00:08:57.779> on<00:08:58.080> your<00:08:58.260> account 00:09:00.050 --> 00:09:00.060 align:start position:0% authorize operations on your account 00:09:00.060 --> 00:09:02.090 align:start position:0% authorize operations on your account um<00:09:00.120> and<00:09:00.480> and<00:09:00.720> a<00:09:01.080> team<00:09:01.260> actually<00:09:01.500> implemented 00:09:02.090 --> 00:09:02.100 align:start position:0% um and and a team actually implemented 00:09:02.100 --> 00:09:04.310 align:start position:0% um and and a team actually implemented that<00:09:02.279> in<00:09:02.580> the<00:09:02.760> recent<00:09:02.940> hackathon<00:09:03.480> which<00:09:04.200> we 00:09:04.310 --> 00:09:04.320 align:start position:0% that in the recent hackathon which we 00:09:04.320 --> 00:09:06.470 align:start position:0% that in the recent hackathon which we thought<00:09:04.500> was<00:09:04.680> pretty<00:09:04.920> cool<00:09:05.180> multi-sig<00:09:06.180> is<00:09:06.360> a 00:09:06.470 --> 00:09:06.480 align:start position:0% thought was pretty cool multi-sig is a 00:09:06.480 --> 00:09:08.870 align:start position:0% thought was pretty cool multi-sig is a very<00:09:06.600> obvious<00:09:06.839> use<00:09:07.080> case<00:09:07.380> so 00:09:08.870 --> 00:09:08.880 align:start position:0% very obvious use case so 00:09:08.880 --> 00:09:10.730 align:start position:0% very obvious use case so you<00:09:09.300> know<00:09:09.420> now 00:09:10.730 --> 00:09:10.740 align:start position:0% you know now 00:09:10.740 --> 00:09:13.310 align:start position:0% you know now um<00:09:10.860> you'll<00:09:11.160> be<00:09:11.279> able<00:09:11.459> to<00:09:11.580> just 00:09:13.310 --> 00:09:13.320 align:start position:0% um you'll be able to just 00:09:13.320 --> 00:09:16.009 align:start position:0% um you'll be able to just um<00:09:13.380> get<00:09:13.920> that<00:09:14.100> out<00:09:14.279> of<00:09:14.399> the<00:09:14.519> box 00:09:16.009 --> 00:09:16.019 align:start position:0% um get that out of the box 00:09:16.019 --> 00:09:18.650 align:start position:0% um get that out of the box um<00:09:16.080> another<00:09:16.500> one<00:09:16.680> is<00:09:16.800> BLS<00:09:17.339> aggregation<00:09:18.120> which 00:09:18.650 --> 00:09:18.660 align:start position:0% um another one is BLS aggregation which 00:09:18.660 --> 00:09:21.170 align:start position:0% um another one is BLS aggregation which requires<00:09:19.080> a<00:09:19.200> little<00:09:19.320> bit<00:09:19.440> of<00:09:19.560> explanation<00:09:20.180> BLS 00:09:21.170 --> 00:09:21.180 align:start position:0% requires a little bit of explanation BLS 00:09:21.180 --> 00:09:24.949 align:start position:0% requires a little bit of explanation BLS is<00:09:21.360> a<00:09:21.480> mechanism<00:09:21.779> to<00:09:22.140> aggregate<00:09:22.620> signatures 00:09:24.949 --> 00:09:24.959 align:start position:0% is a mechanism to aggregate signatures 00:09:24.959 --> 00:09:27.769 align:start position:0% is a mechanism to aggregate signatures um<00:09:25.140> and<00:09:25.860> that's<00:09:26.640> cool<00:09:26.820> because<00:09:27.120> it<00:09:27.360> reduces 00:09:27.769 --> 00:09:27.779 align:start position:0% um and that's cool because it reduces 00:09:27.779 --> 00:09:30.290 align:start position:0% um and that's cool because it reduces your<00:09:28.019> gas<00:09:28.200> costs 00:09:30.290 --> 00:09:30.300 align:start position:0% your gas costs 00:09:30.300 --> 00:09:32.570 align:start position:0% your gas costs and<00:09:30.839> because<00:09:31.500> we<00:09:31.800> have<00:09:31.920> the<00:09:32.100> ability<00:09:32.279> to 00:09:32.570 --> 00:09:32.580 align:start position:0% and because we have the ability to 00:09:32.580 --> 00:09:34.550 align:start position:0% and because we have the ability to implement<00:09:32.820> any<00:09:33.600> signature<00:09:34.019> verification 00:09:34.550 --> 00:09:34.560 align:start position:0% implement any signature verification 00:09:34.560 --> 00:09:36.350 align:start position:0% implement any signature verification mechanism<00:09:35.040> in<00:09:35.399> the<00:09:35.580> account 00:09:36.350 --> 00:09:36.360 align:start position:0% mechanism in the account 00:09:36.360 --> 00:09:39.550 align:start position:0% mechanism in the account then<00:09:36.899> now<00:09:37.200> we<00:09:37.320> can<00:09:37.440> have<00:09:37.620> more<00:09:37.860> efficient 00:09:39.550 --> 00:09:39.560 align:start position:0% then now we can have more efficient 00:09:39.560 --> 00:09:42.610 align:start position:0% then now we can have more efficient signature<00:09:40.560> validation<00:09:40.980> and<00:09:41.700> save<00:09:41.940> some<00:09:42.180> costs 00:09:42.610 --> 00:09:42.620 align:start position:0% signature validation and save some costs 00:09:42.620 --> 00:09:45.769 align:start position:0% signature validation and save some costs the<00:09:43.620> other<00:09:43.680> big<00:09:43.920> one<00:09:44.100> is<00:09:44.339> eventually 00:09:45.769 --> 00:09:45.779 align:start position:0% the other big one is eventually 00:09:45.779 --> 00:09:47.930 align:start position:0% the other big one is eventually we<00:09:46.200> know<00:09:46.380> that<00:09:46.680> the<00:09:46.920> signature<00:09:47.339> mechanisms 00:09:47.930 --> 00:09:47.940 align:start position:0% we know that the signature mechanisms 00:09:47.940 --> 00:09:50.509 align:start position:0% we know that the signature mechanisms that<00:09:48.240> we're<00:09:48.360> using<00:09:48.860> are<00:09:49.860> going<00:09:50.040> to<00:09:50.160> be<00:09:50.339> broken 00:09:50.509 --> 00:09:50.519 align:start position:0% that we're using are going to be broken 00:09:50.519 --> 00:09:53.030 align:start position:0% that we're using are going to be broken it's<00:09:51.000> only<00:09:51.180> a<00:09:51.360> matter<00:09:51.480> of<00:09:51.660> time<00:09:52.040> Quantum 00:09:53.030 --> 00:09:53.040 align:start position:0% it's only a matter of time Quantum 00:09:53.040 --> 00:09:55.070 align:start position:0% it's only a matter of time Quantum Computing<00:09:53.519> is<00:09:53.820> making<00:09:54.300> uh<00:09:54.660> significant 00:09:55.070 --> 00:09:55.080 align:start position:0% Computing is making uh significant 00:09:55.080 --> 00:09:58.370 align:start position:0% Computing is making uh significant progress<00:09:55.440> it's<00:09:56.279> no<00:09:56.519> longer<00:09:56.820> theoretical<00:09:57.420> the 00:09:58.370 --> 00:09:58.380 align:start position:0% progress it's no longer theoretical the 00:09:58.380 --> 00:09:59.930 align:start position:0% progress it's no longer theoretical the qubits<00:09:58.860> are<00:09:58.920> getting<00:09:59.040> up<00:09:59.220> there<00:09:59.399> eventually 00:09:59.930 --> 00:09:59.940 align:start position:0% qubits are getting up there eventually 00:09:59.940 --> 00:10:04.430 align:start position:0% qubits are getting up there eventually we<00:10:00.839> will<00:10:01.500> I'll<00:10:02.040> have<00:10:02.279> to<00:10:02.399> stop<00:10:02.580> using<00:10:02.959> ecdsa 00:10:04.430 --> 00:10:04.440 align:start position:0% we will I'll have to stop using ecdsa 00:10:04.440 --> 00:10:07.190 align:start position:0% we will I'll have to stop using ecdsa but<00:10:05.160> there<00:10:05.279> are<00:10:05.399> alternatives 00:10:07.190 --> 00:10:07.200 align:start position:0% but there are alternatives 00:10:07.200 --> 00:10:08.990 align:start position:0% but there are alternatives um<00:10:07.260> and<00:10:07.800> hopefully<00:10:08.160> by<00:10:08.339> the<00:10:08.519> time<00:10:08.640> this 00:10:08.990 --> 00:10:09.000 align:start position:0% um and hopefully by the time this 00:10:09.000 --> 00:10:12.050 align:start position:0% um and hopefully by the time this becomes<00:10:09.480> you<00:10:10.440> know<00:10:10.500> a<00:10:10.680> pressing<00:10:11.100> problem<00:10:11.399> we 00:10:12.050 --> 00:10:12.060 align:start position:0% becomes you know a pressing problem we 00:10:12.060 --> 00:10:15.230 align:start position:0% becomes you know a pressing problem we will<00:10:12.300> just<00:10:12.480> be<00:10:12.660> able<00:10:12.899> to<00:10:13.080> use<00:10:13.820> any<00:10:14.820> Quantum 00:10:15.230 --> 00:10:15.240 align:start position:0% will just be able to use any Quantum 00:10:15.240 --> 00:10:18.350 align:start position:0% will just be able to use any Quantum resistant<00:10:15.720> signature<00:10:16.380> mechanism<00:10:17.240> that<00:10:18.240> we 00:10:18.350 --> 00:10:18.360 align:start position:0% resistant signature mechanism that we 00:10:18.360 --> 00:10:20.750 align:start position:0% resistant signature mechanism that we want<00:10:18.600> that<00:10:19.140> is<00:10:19.320> maybe<00:10:19.500> like<00:10:19.800> gas<00:10:20.279> efficient 00:10:20.750 --> 00:10:20.760 align:start position:0% want that is maybe like gas efficient 00:10:20.760 --> 00:10:23.269 align:start position:0% want that is maybe like gas efficient and<00:10:21.180> secure 00:10:23.269 --> 00:10:23.279 align:start position:0% and secure 00:10:23.279 --> 00:10:26.690 align:start position:0% and secure um<00:10:23.480> and<00:10:24.480> you<00:10:24.839> can<00:10:24.899> you<00:10:25.080> can<00:10:25.260> swap<00:10:25.500> that 00:10:26.690 --> 00:10:26.700 align:start position:0% um and you can you can swap that 00:10:26.700 --> 00:10:29.150 align:start position:0% um and you can you can swap that so<00:10:27.240> you<00:10:27.420> have<00:10:27.540> a<00:10:27.660> lot<00:10:27.779> of<00:10:27.899> flexibility 00:10:29.150 --> 00:10:29.160 align:start position:0% so you have a lot of flexibility 00:10:29.160 --> 00:10:30.949 align:start position:0% so you have a lot of flexibility once<00:10:29.700> you<00:10:29.820> abstract<00:10:30.240> away<00:10:30.420> how<00:10:30.720> you<00:10:30.839> do 00:10:30.949 --> 00:10:30.959 align:start position:0% once you abstract away how you do 00:10:30.959 --> 00:10:33.230 align:start position:0% once you abstract away how you do signatures<00:10:31.380> and<00:10:31.560> it's<00:10:31.740> not<00:10:31.860> hard<00:10:32.040> hard-coded 00:10:33.230 --> 00:10:33.240 align:start position:0% signatures and it's not hard hard-coded 00:10:33.240 --> 00:10:34.910 align:start position:0% signatures and it's not hard hard-coded so 00:10:34.910 --> 00:10:34.920 align:start position:0% so 00:10:34.920 --> 00:10:37.310 align:start position:0% so um<00:10:34.980> other<00:10:35.220> interesting<00:10:35.700> use<00:10:35.880> cases<00:10:36.320> are 00:10:37.310 --> 00:10:37.320 align:start position:0% um other interesting use cases are 00:10:37.320 --> 00:10:40.310 align:start position:0% um other interesting use cases are spending<00:10:37.860> limits<00:10:38.220> I<00:10:39.000> mean<00:10:39.180> you<00:10:39.899> know<00:10:39.959> if<00:10:40.140> you 00:10:40.310 --> 00:10:40.320 align:start position:0% spending limits I mean you know if you 00:10:40.320 --> 00:10:42.949 align:start position:0% spending limits I mean you know if you if<00:10:40.500> using<00:10:40.920> your<00:10:41.160> wallet<00:10:41.459> for<00:10:42.240> small 00:10:42.949 --> 00:10:42.959 align:start position:0% if using your wallet for small 00:10:42.959 --> 00:10:44.509 align:start position:0% if using your wallet for small day-to-day<00:10:43.500> things<00:10:43.740> maybe<00:10:44.040> you're<00:10:44.220> paying 00:10:44.509 --> 00:10:44.519 align:start position:0% day-to-day things maybe you're paying 00:10:44.519 --> 00:10:47.329 align:start position:0% day-to-day things maybe you're paying for<00:10:44.640> coffee<00:10:45.140> for<00:10:46.140> a<00:10:46.260> meal<00:10:46.560> or<00:10:46.800> for<00:10:46.980> something 00:10:47.329 --> 00:10:47.339 align:start position:0% for coffee for a meal or for something 00:10:47.339 --> 00:10:48.410 align:start position:0% for coffee for a meal or for something you<00:10:47.760> know 00:10:48.410 --> 00:10:48.420 align:start position:0% you know 00:10:48.420 --> 00:10:52.790 align:start position:0% you know um<00:10:48.540> that<00:10:49.200> is<00:10:49.380> not<00:10:50.339> usually<00:10:51.240> life-changing 00:10:52.790 --> 00:10:52.800 align:start position:0% um that is not usually life-changing 00:10:52.800 --> 00:10:55.670 align:start position:0% um that is not usually life-changing then<00:10:53.579> it<00:10:53.820> makes<00:10:54.000> sense<00:10:54.240> for<00:10:54.839> that<00:10:55.380> to<00:10:55.560> be 00:10:55.670 --> 00:10:55.680 align:start position:0% then it makes sense for that to be 00:10:55.680 --> 00:10:58.130 align:start position:0% then it makes sense for that to be something<00:10:55.800> that<00:10:56.040> you<00:10:56.100> can<00:10:56.220> do<00:10:56.339> very<00:10:56.579> easily 00:10:58.130 --> 00:10:58.140 align:start position:0% something that you can do very easily 00:10:58.140 --> 00:11:00.050 align:start position:0% something that you can do very easily um<00:10:58.200> that<00:10:58.440> shouldn't<00:10:58.740> be<00:10:58.800> too<00:10:59.040> hard<00:10:59.220> but<00:10:59.940> then 00:11:00.050 --> 00:11:00.060 align:start position:0% um that shouldn't be too hard but then 00:11:00.060 --> 00:11:01.370 align:start position:0% um that shouldn't be too hard but then if<00:11:00.300> you're<00:11:00.360> making<00:11:00.600> you<00:11:00.959> know<00:11:01.019> very<00:11:01.200> big 00:11:01.370 --> 00:11:01.380 align:start position:0% if you're making you know very big 00:11:01.380 --> 00:11:04.069 align:start position:0% if you're making you know very big investment 00:11:04.069 --> 00:11:04.079 align:start position:0% 00:11:04.079 --> 00:11:07.550 align:start position:0% um<00:11:04.200> then<00:11:04.860> you<00:11:05.399> want<00:11:05.579> you<00:11:06.060> you<00:11:06.060> might<00:11:06.540> want<00:11:06.899> to 00:11:07.550 --> 00:11:07.560 align:start position:0% um then you want you you might want to 00:11:07.560 --> 00:11:11.090 align:start position:0% um then you want you you might want to add<00:11:07.980> uh<00:11:08.880> add<00:11:09.480> like<00:11:09.720> a<00:11:09.899> more<00:11:10.079> uh<00:11:10.440> secure<00:11:10.740> way<00:11:10.920> of 00:11:11.090 --> 00:11:11.100 align:start position:0% add uh add like a more uh secure way of 00:11:11.100 --> 00:11:14.389 align:start position:0% add uh add like a more uh secure way of doing<00:11:11.220> that<00:11:11.459> so<00:11:12.000> you<00:11:12.120> go<00:11:12.240> get<00:11:12.420> your<00:11:12.600> Ledger 00:11:14.389 --> 00:11:14.399 align:start position:0% doing that so you go get your Ledger 00:11:14.399 --> 00:11:16.610 align:start position:0% doing that so you go get your Ledger um<00:11:14.519> really<00:11:14.820> depending<00:11:15.240> on<00:11:15.540> on<00:11:15.899> what<00:11:16.380> is<00:11:16.500> the 00:11:16.610 --> 00:11:16.620 align:start position:0% um really depending on on what is the 00:11:16.620 --> 00:11:17.690 align:start position:0% um really depending on on what is the spending<00:11:16.920> limit<00:11:17.040> that<00:11:17.339> you're<00:11:17.459> comfortable 00:11:17.690 --> 00:11:17.700 align:start position:0% spending limit that you're comfortable 00:11:17.700 --> 00:11:21.290 align:start position:0% spending limit that you're comfortable with<00:11:17.880> for<00:11:18.720> different<00:11:19.079> levels<00:11:19.500> of<00:11:19.620> security 00:11:21.290 --> 00:11:21.300 align:start position:0% with for different levels of security 00:11:21.300 --> 00:11:22.970 align:start position:0% with for different levels of security uh<00:11:21.839> and<00:11:21.959> you<00:11:22.079> can<00:11:22.200> you<00:11:22.500> would<00:11:22.620> be<00:11:22.740> able<00:11:22.860> to 00:11:22.970 --> 00:11:22.980 align:start position:0% uh and you can you would be able to 00:11:22.980 --> 00:11:24.470 align:start position:0% uh and you can you would be able to implement<00:11:23.279> that<00:11:23.459> because<00:11:23.700> again<00:11:24.120> you<00:11:24.300> can 00:11:24.470 --> 00:11:24.480 align:start position:0% implement that because again you can 00:11:24.480 --> 00:11:27.530 align:start position:0% implement that because again you can have<00:11:24.600> arbitrary<00:11:25.079> logic<00:11:25.560> inside 00:11:27.530 --> 00:11:27.540 align:start position:0% have arbitrary logic inside 00:11:27.540 --> 00:11:29.210 align:start position:0% have arbitrary logic inside um<00:11:27.600> inside<00:11:27.899> a<00:11:28.200> contract<00:11:28.500> that<00:11:28.740> is<00:11:28.860> controlling 00:11:29.210 --> 00:11:29.220 align:start position:0% um inside a contract that is controlling 00:11:29.220 --> 00:11:30.590 align:start position:0% um inside a contract that is controlling your<00:11:29.399> account 00:11:30.590 --> 00:11:30.600 align:start position:0% your account 00:11:30.600 --> 00:11:31.730 align:start position:0% your account um the<00:11:30.779> other<00:11:30.899> cool<00:11:31.079> thing<00:11:31.260> that<00:11:31.380> you<00:11:31.500> can<00:11:31.620> do 00:11:31.730 --> 00:11:31.740 align:start position:0% um the other cool thing that you can do 00:11:31.740 --> 00:11:34.790 align:start position:0% um the other cool thing that you can do is<00:11:31.980> well<00:11:32.339> you<00:11:32.579> can<00:11:32.700> have<00:11:32.940> you<00:11:33.779> can<00:11:33.839> have<00:11:34.079> uh 00:11:34.790 --> 00:11:34.800 align:start position:0% is well you can have you can have uh 00:11:34.800 --> 00:11:36.889 align:start position:0% is well you can have you can have uh different<00:11:35.040> roles<00:11:35.399> and<00:11:36.180> you<00:11:36.360> can<00:11:36.420> delegate 00:11:36.889 --> 00:11:36.899 align:start position:0% different roles and you can delegate 00:11:36.899 --> 00:11:40.389 align:start position:0% different roles and you can delegate specific<00:11:37.380> actions<00:11:37.980> uh<00:11:38.519> to<00:11:38.700> those<00:11:38.880> roles 00:11:40.389 --> 00:11:40.399 align:start position:0% specific actions uh to those roles 00:11:40.399 --> 00:11:43.970 align:start position:0% specific actions uh to those roles so<00:11:41.399> you<00:11:42.120> know<00:11:42.240> if<00:11:42.480> you're<00:11:42.720> if<00:11:43.079> the<00:11:43.500> account<00:11:43.620> is 00:11:43.970 --> 00:11:43.980 align:start position:0% so you know if you're if the account is 00:11:43.980 --> 00:11:46.970 align:start position:0% so you know if you're if the account is a<00:11:44.100> corporate<00:11:44.519> account<00:11:44.700> you<00:11:45.600> can<00:11:45.720> give<00:11:45.980> payroll 00:11:46.970 --> 00:11:46.980 align:start position:0% a corporate account you can give payroll 00:11:46.980 --> 00:11:49.790 align:start position:0% a corporate account you can give payroll uh<00:11:47.700> authorization 00:11:49.790 --> 00:11:49.800 align:start position:0% uh authorization 00:11:49.800 --> 00:11:51.610 align:start position:0% uh authorization um to<00:11:49.980> people<00:11:50.160> who<00:11:50.399> are<00:11:50.459> in<00:11:50.640> charge<00:11:50.760> of<00:11:50.940> that 00:11:51.610 --> 00:11:51.620 align:start position:0% um to people who are in charge of that 00:11:51.620 --> 00:11:56.210 align:start position:0% um to people who are in charge of that and<00:11:52.620> you<00:11:53.519> can<00:11:53.640> specify<00:11:54.060> the<00:11:54.300> spending<00:11:54.600> limits 00:11:56.210 --> 00:11:56.220 align:start position:0% and you can specify the spending limits 00:11:56.220 --> 00:11:58.490 align:start position:0% and you can specify the spending limits um<00:11:56.279> another<00:11:56.760> example<00:11:57.180> would<00:11:57.480> be 00:11:58.490 --> 00:11:58.500 align:start position:0% um another example would be 00:11:58.500 --> 00:12:02.150 align:start position:0% um another example would be if<00:11:59.040> you're<00:11:59.399> you<00:11:59.760> know<00:11:59.880> if<00:12:00.120> you're<00:12:00.839> um<00:12:01.100> you<00:12:02.100> have 00:12:02.150 --> 00:12:02.160 align:start position:0% if you're you know if you're um you have 00:12:02.160 --> 00:12:04.370 align:start position:0% if you're you know if you're um you have a<00:12:02.279> legal<00:12:02.579> department<00:12:02.720> or<00:12:03.720> you<00:12:04.019> just<00:12:04.140> want<00:12:04.260> to 00:12:04.370 --> 00:12:04.380 align:start position:0% a legal department or you just want to 00:12:04.380 --> 00:12:06.590 align:start position:0% a legal department or you just want to delegate<00:12:04.740> voting<00:12:05.100> power<00:12:05.279> for<00:12:05.940> certain<00:12:06.240> tokens 00:12:06.590 --> 00:12:06.600 align:start position:0% delegate voting power for certain tokens 00:12:06.600 --> 00:12:07.790 align:start position:0% delegate voting power for certain tokens you<00:12:06.779> could<00:12:06.839> do<00:12:06.959> that<00:12:07.079> in<00:12:07.200> a<00:12:07.320> way<00:12:07.380> that<00:12:07.560> still 00:12:07.790 --> 00:12:07.800 align:start position:0% you could do that in a way that still 00:12:07.800 --> 00:12:11.690 align:start position:0% you could do that in a way that still limits<00:12:08.279> your<00:12:08.579> exposure<00:12:09.060> just<00:12:09.959> to<00:12:10.140> that 00:12:11.690 --> 00:12:11.700 align:start position:0% limits your exposure just to that 00:12:11.700 --> 00:12:12.470 align:start position:0% limits your exposure just to that um 00:12:12.470 --> 00:12:12.480 align:start position:0% um 00:12:12.480 --> 00:12:14.690 align:start position:0% um so<00:12:13.440> they<00:12:13.740> would<00:12:13.860> be<00:12:13.980> able<00:12:14.100> to<00:12:14.220> vote<00:12:14.399> with<00:12:14.579> the 00:12:14.690 --> 00:12:14.700 align:start position:0% so they would be able to vote with the 00:12:14.700 --> 00:12:17.050 align:start position:0% so they would be able to vote with the tokens<00:12:15.060> and<00:12:15.720> perform<00:12:15.959> governance<00:12:16.560> actions 00:12:17.050 --> 00:12:17.060 align:start position:0% tokens and perform governance actions 00:12:17.060 --> 00:12:20.090 align:start position:0% tokens and perform governance actions but<00:12:18.060> not<00:12:18.600> you<00:12:18.899> know<00:12:19.019> like<00:12:19.260> transfer<00:12:19.920> the 00:12:20.090 --> 00:12:20.100 align:start position:0% but not you know like transfer the 00:12:20.100 --> 00:12:22.130 align:start position:0% but not you know like transfer the tokens<00:12:20.399> for<00:12:20.579> example 00:12:22.130 --> 00:12:22.140 align:start position:0% tokens for example 00:12:22.140 --> 00:12:22.990 align:start position:0% tokens for example um 00:12:22.990 --> 00:12:23.000 align:start position:0% um 00:12:23.000 --> 00:12:24.590 align:start position:0% um and 00:12:24.590 --> 00:12:24.600 align:start position:0% and 00:12:24.600 --> 00:12:27.170 align:start position:0% and uh<00:12:25.019> usually<00:12:25.320> in<00:12:25.500> companies<00:12:25.980> I<00:12:26.820> mean<00:12:26.880> this<00:12:27.060> is 00:12:27.170 --> 00:12:27.180 align:start position:0% uh usually in companies I mean this is 00:12:27.180 --> 00:12:28.430 align:start position:0% uh usually in companies I mean this is something<00:12:27.360> that's<00:12:27.540> very<00:12:27.779> common<00:12:28.019> in 00:12:28.430 --> 00:12:28.440 align:start position:0% something that's very common in 00:12:28.440 --> 00:12:30.530 align:start position:0% something that's very common in corporate<00:12:28.740> bank<00:12:28.920> accounts<00:12:29.399> you<00:12:29.700> give<00:12:29.940> you 00:12:30.530 --> 00:12:30.540 align:start position:0% corporate bank accounts you give you 00:12:30.540 --> 00:12:32.569 align:start position:0% corporate bank accounts you give you give<00:12:30.720> different<00:12:31.019> uh<00:12:31.560> roles<00:12:31.980> in<00:12:32.279> the<00:12:32.459> company 00:12:32.569 --> 00:12:32.579 align:start position:0% give different uh roles in the company 00:12:32.579 --> 00:12:36.050 align:start position:0% give different uh roles in the company different<00:12:32.940> powers<00:12:33.860> so<00:12:34.860> you<00:12:35.339> know<00:12:35.519> the<00:12:35.579> CFO 00:12:36.050 --> 00:12:36.060 align:start position:0% different powers so you know the CFO 00:12:36.060 --> 00:12:39.230 align:start position:0% different powers so you know the CFO might<00:12:36.480> be<00:12:36.600> able<00:12:36.839> to<00:12:37.399> transfer<00:12:38.399> a<00:12:38.579> larger<00:12:38.880> sum 00:12:39.230 --> 00:12:39.240 align:start position:0% might be able to transfer a larger sum 00:12:39.240 --> 00:12:42.590 align:start position:0% might be able to transfer a larger sum but<00:12:39.600> there's<00:12:39.720> still<00:12:39.959> a<00:12:40.079> 24-hour<00:12:40.500> delay 00:12:42.590 --> 00:12:42.600 align:start position:0% but there's still a 24-hour delay 00:12:42.600 --> 00:12:45.410 align:start position:0% but there's still a 24-hour delay um<00:12:42.779> and<00:12:43.139> then<00:12:43.320> you<00:12:43.740> know<00:12:43.800> maybe<00:12:43.920> other<00:12:44.420> c-level 00:12:45.410 --> 00:12:45.420 align:start position:0% um and then you know maybe other c-level 00:12:45.420 --> 00:12:48.170 align:start position:0% um and then you know maybe other c-level Executives<00:12:46.019> could<00:12:46.440> could<00:12:47.160> veto<00:12:47.760> that<00:12:47.940> if 00:12:48.170 --> 00:12:48.180 align:start position:0% Executives could could veto that if 00:12:48.180 --> 00:12:50.210 align:start position:0% Executives could could veto that if maybe<00:12:48.360> the<00:12:48.540> you<00:12:48.779> know<00:12:48.899> the<00:12:49.019> cfo's<00:12:49.680> key<00:12:49.800> was 00:12:50.210 --> 00:12:50.220 align:start position:0% maybe the you know the cfo's key was 00:12:50.220 --> 00:12:52.970 align:start position:0% maybe the you know the cfo's key was hacked<00:12:50.639> uh<00:12:51.420> or<00:12:51.540> their<00:12:51.720> computer 00:12:52.970 --> 00:12:52.980 align:start position:0% hacked uh or their computer 00:12:52.980 --> 00:12:55.190 align:start position:0% hacked uh or their computer um<00:12:53.100> was<00:12:53.339> hacked 00:12:55.190 --> 00:12:55.200 align:start position:0% um was hacked 00:12:55.200 --> 00:12:57.410 align:start position:0% um was hacked or<00:12:55.680> the<00:12:55.860> CFO<00:12:56.220> is<00:12:56.339> untrustworthy<00:12:57.120> for<00:12:57.240> some 00:12:57.410 --> 00:12:57.420 align:start position:0% or the CFO is untrustworthy for some 00:12:57.420 --> 00:12:59.690 align:start position:0% or the CFO is untrustworthy for some reason<00:12:57.600> but 00:12:59.690 --> 00:12:59.700 align:start position:0% reason but 00:12:59.700 --> 00:13:00.470 align:start position:0% reason but um 00:13:00.470 --> 00:13:00.480 align:start position:0% um 00:13:00.480 --> 00:13:03.170 align:start position:0% um another<00:13:00.899> example<00:13:01.380> would<00:13:01.560> be<00:13:01.860> well<00:13:02.760> you<00:13:03.000> you 00:13:03.170 --> 00:13:03.180 align:start position:0% another example would be well you you 00:13:03.180 --> 00:13:06.889 align:start position:0% another example would be well you you want<00:13:03.420> you<00:13:03.720> want<00:13:04.019> to<00:13:04.200> give<00:13:05.100> an<00:13:05.339> auditor 00:13:06.889 --> 00:13:06.899 align:start position:0% want you want to give an auditor 00:13:06.899 --> 00:13:10.430 align:start position:0% want you want to give an auditor um<00:13:06.959> the<00:13:07.260> power<00:13:07.440> to<00:13:07.980> monitor<00:13:08.660> payments<00:13:09.660> and 00:13:10.430 --> 00:13:10.440 align:start position:0% um the power to monitor payments and 00:13:10.440 --> 00:13:13.850 align:start position:0% um the power to monitor payments and then<00:13:10.620> the<00:13:11.100> auditor<00:13:11.519> has<00:13:12.000> responsibility<00:13:12.860> if 00:13:13.850 --> 00:13:13.860 align:start position:0% then the auditor has responsibility if 00:13:13.860 --> 00:13:15.170 align:start position:0% then the auditor has responsibility if if<00:13:14.100> something<00:13:14.339> you<00:13:14.639> know<00:13:14.820> they<00:13:14.940> have<00:13:15.060> the 00:13:15.170 --> 00:13:15.180 align:start position:0% if something you know they have the 00:13:15.180 --> 00:13:17.810 align:start position:0% if something you know they have the responsibility<00:13:15.660> to<00:13:16.079> reach<00:13:16.500> out<00:13:16.620> to<00:13:17.399> authorize 00:13:17.810 --> 00:13:17.820 align:start position:0% responsibility to reach out to authorize 00:13:17.820 --> 00:13:20.090 align:start position:0% responsibility to reach out to authorize parties<00:13:18.240> and<00:13:18.959> then<00:13:19.079> verify<00:13:19.620> that<00:13:19.860> what 00:13:20.090 --> 00:13:20.100 align:start position:0% parties and then verify that what 00:13:20.100 --> 00:13:22.009 align:start position:0% parties and then verify that what they're<00:13:20.220> seeing<00:13:20.459> happening<00:13:20.820> on<00:13:21.060> chain<00:13:21.240> is 00:13:22.009 --> 00:13:22.019 align:start position:0% they're seeing happening on chain is 00:13:22.019 --> 00:13:23.690 align:start position:0% they're seeing happening on chain is what<00:13:22.260> is<00:13:22.380> supposed<00:13:22.560> to<00:13:22.740> happen 00:13:23.690 --> 00:13:23.700 align:start position:0% what is supposed to happen 00:13:23.700 --> 00:13:26.449 align:start position:0% what is supposed to happen so<00:13:24.180> this<00:13:24.360> way<00:13:24.600> you<00:13:25.200> can<00:13:25.260> tap<00:13:25.620> like<00:13:25.980> maybe<00:13:26.100> like 00:13:26.449 --> 00:13:26.459 align:start position:0% so this way you can tap like maybe like 00:13:26.459 --> 00:13:27.829 align:start position:0% so this way you can tap like maybe like a<00:13:26.760> third<00:13:26.880> party 00:13:27.829 --> 00:13:27.839 align:start position:0% a third party 00:13:27.839 --> 00:13:30.590 align:start position:0% a third party accounting<00:13:28.560> firm<00:13:29.120> maybe<00:13:30.120> the<00:13:30.360> one<00:13:30.480> you 00:13:30.590 --> 00:13:30.600 align:start position:0% accounting firm maybe the one you 00:13:30.600 --> 00:13:33.110 align:start position:0% accounting firm maybe the one you already<00:13:30.779> work<00:13:31.019> with<00:13:31.200> say<00:13:32.040> hey<00:13:32.279> like<00:13:32.639> you<00:13:33.000> know 00:13:33.110 --> 00:13:33.120 align:start position:0% already work with say hey like you know 00:13:33.120 --> 00:13:35.810 align:start position:0% already work with say hey like you know we<00:13:33.660> we<00:13:34.200> owe<00:13:34.380> it<00:13:34.500> to<00:13:34.620> our<00:13:34.800> shareholders<00:13:35.279> at<00:13:35.579> our 00:13:35.810 --> 00:13:35.820 align:start position:0% we we owe it to our shareholders at our 00:13:35.820 --> 00:13:38.329 align:start position:0% we we owe it to our shareholders at our treasury<00:13:36.060> management 00:13:38.329 --> 00:13:38.339 align:start position:0% treasury management 00:13:38.339 --> 00:13:42.050 align:start position:0% treasury management um<00:13:38.459> it<00:13:38.940> doesn't<00:13:39.120> get<00:13:39.300> compromised<00:13:40.279> and<00:13:41.279> how 00:13:42.050 --> 00:13:42.060 align:start position:0% um it doesn't get compromised and how 00:13:42.060 --> 00:13:43.870 align:start position:0% um it doesn't get compromised and how about<00:13:42.240> like<00:13:42.480> we<00:13:42.660> plug<00:13:42.899> you<00:13:43.079> into 00:13:43.870 --> 00:13:43.880 align:start position:0% about like we plug you into 00:13:43.880 --> 00:13:47.150 align:start position:0% about like we plug you into our<00:13:44.880> our<00:13:45.540> treasury<00:13:46.019> in<00:13:46.260> a<00:13:46.440> way<00:13:46.500> where<00:13:46.740> yeah<00:13:46.920> you 00:13:47.150 --> 00:13:47.160 align:start position:0% our our treasury in a way where yeah you 00:13:47.160 --> 00:13:48.470 align:start position:0% our our treasury in a way where yeah you can't<00:13:47.279> you<00:13:47.579> can't<00:13:47.700> perform<00:13:47.880> you<00:13:48.180> don't<00:13:48.360> have 00:13:48.470 --> 00:13:48.480 align:start position:0% can't you can't perform you don't have 00:13:48.480 --> 00:13:49.310 align:start position:0% can't you can't perform you don't have to 00:13:49.310 --> 00:13:49.320 align:start position:0% to 00:13:49.320 --> 00:13:52.670 align:start position:0% to rely<00:13:50.040> on<00:13:50.700> maybe<00:13:51.120> your<00:13:51.540> computer<00:13:51.720> security<00:13:52.079> or 00:13:52.670 --> 00:13:52.680 align:start position:0% rely on maybe your computer security or 00:13:52.680 --> 00:13:54.829 align:start position:0% rely on maybe your computer security or your<00:13:53.279> staff<00:13:53.459> we<00:13:53.880> don't<00:13:54.060> have<00:13:54.240> we<00:13:54.360> want<00:13:54.600> to<00:13:54.660> you 00:13:54.829 --> 00:13:54.839 align:start position:0% your staff we don't have we want to you 00:13:54.839 --> 00:13:56.870 align:start position:0% your staff we don't have we want to you don't<00:13:54.899> want<00:13:55.019> exposure<00:13:55.560> from<00:13:56.040> to<00:13:56.279> them<00:13:56.639> in 00:13:56.870 --> 00:13:56.880 align:start position:0% don't want exposure from to them in 00:13:56.880 --> 00:13:58.850 align:start position:0% don't want exposure from to them in terms<00:13:57.060> of<00:13:57.180> being<00:13:57.420> able<00:13:57.720> to 00:13:58.850 --> 00:13:58.860 align:start position:0% terms of being able to 00:13:58.860 --> 00:14:01.129 align:start position:0% terms of being able to um<00:13:58.980> to<00:13:59.220> transfer<00:13:59.519> funds<00:13:59.880> but 00:14:01.129 --> 00:14:01.139 align:start position:0% um to transfer funds but 00:14:01.139 --> 00:14:02.509 align:start position:0% um to transfer funds but we<00:14:01.740> do<00:14:01.860> want<00:14:01.980> to<00:14:02.160> give<00:14:02.220> you<00:14:02.339> the 00:14:02.509 --> 00:14:02.519 align:start position:0% we do want to give you the 00:14:02.519 --> 00:14:04.190 align:start position:0% we do want to give you the responsibility<00:14:03.060> of<00:14:03.540> whatever<00:14:03.720> you<00:14:04.019> see 00:14:04.190 --> 00:14:04.200 align:start position:0% responsibility of whatever you see 00:14:04.200 --> 00:14:06.410 align:start position:0% responsibility of whatever you see happening<00:14:04.620> you<00:14:05.160> know<00:14:05.279> talk<00:14:05.579> to<00:14:05.820> the<00:14:06.240> people 00:14:06.410 --> 00:14:06.420 align:start position:0% happening you know talk to the people 00:14:06.420 --> 00:14:08.930 align:start position:0% happening you know talk to the people who<00:14:06.959> are<00:14:07.380> in<00:14:07.560> charge<00:14:07.740> make<00:14:08.220> sure<00:14:08.339> that<00:14:08.639> it<00:14:08.820> is 00:14:08.930 --> 00:14:08.940 align:start position:0% who are in charge make sure that it is 00:14:08.940 --> 00:14:10.670 align:start position:0% who are in charge make sure that it is an<00:14:09.180> authorized<00:14:09.660> action 00:14:10.670 --> 00:14:10.680 align:start position:0% an authorized action 00:14:10.680 --> 00:14:14.090 align:start position:0% an authorized action and<00:14:11.639> you<00:14:12.060> know<00:14:12.120> within<00:14:12.420> this<00:14:12.540> delay<00:14:12.839> limit<00:14:13.100> uh 00:14:14.090 --> 00:14:14.100 align:start position:0% and you know within this delay limit uh 00:14:14.100 --> 00:14:16.550 align:start position:0% and you know within this delay limit uh if<00:14:14.279> it<00:14:14.399> isn't<00:14:14.700> just<00:14:15.180> veto<00:14:15.720> it<00:14:15.899> just<00:14:16.320> like 00:14:16.550 --> 00:14:16.560 align:start position:0% if it isn't just veto it just like 00:14:16.560 --> 00:14:18.470 align:start position:0% if it isn't just veto it just like cancel<00:14:17.160> the<00:14:17.459> transaction<00:14:17.760> so<00:14:18.060> you<00:14:18.240> could<00:14:18.300> give 00:14:18.470 --> 00:14:18.480 align:start position:0% cancel the transaction so you could give 00:14:18.480 --> 00:14:19.610 align:start position:0% cancel the transaction so you could give them<00:14:18.600> the<00:14:18.720> power<00:14:18.899> to<00:14:19.079> cancel<00:14:19.200> but<00:14:19.500> not 00:14:19.610 --> 00:14:19.620 align:start position:0% them the power to cancel but not 00:14:19.620 --> 00:14:21.170 align:start position:0% them the power to cancel but not initiate<00:14:19.980> transactions 00:14:21.170 --> 00:14:21.180 align:start position:0% initiate transactions 00:14:21.180 --> 00:14:22.790 align:start position:0% initiate transactions and 00:14:22.790 --> 00:14:22.800 align:start position:0% and 00:14:22.800 --> 00:14:24.350 align:start position:0% and I<00:14:23.279> think<00:14:23.459> the<00:14:23.519> one<00:14:23.700> that's<00:14:23.820> going<00:14:24.000> to<00:14:24.060> be<00:14:24.180> like 00:14:24.350 --> 00:14:24.360 align:start position:0% I think the one that's going to be like 00:14:24.360 --> 00:14:29.110 align:start position:0% I think the one that's going to be like very<00:14:24.540> useful<00:14:24.899> very<00:14:25.620> soon<00:14:25.800> is<00:14:26.300> session<00:14:27.300> keys<00:14:27.779> so 00:14:29.110 --> 00:14:29.120 align:start position:0% very useful very soon is session keys so 00:14:29.120 --> 00:14:31.910 align:start position:0% very useful very soon is session keys so in<00:14:30.120> fact<00:14:30.240> I<00:14:30.720> think<00:14:30.959> this<00:14:31.079> is<00:14:31.200> something<00:14:31.380> Argent 00:14:31.910 --> 00:14:31.920 align:start position:0% in fact I think this is something Argent 00:14:31.920 --> 00:14:34.670 align:start position:0% in fact I think this is something Argent recently<00:14:32.339> implemented<00:14:32.760> for 00:14:34.670 --> 00:14:34.680 align:start position:0% recently implemented for 00:14:34.680 --> 00:14:37.129 align:start position:0% recently implemented for um<00:14:34.800> for<00:14:35.760> their<00:14:36.000> uh 00:14:37.129 --> 00:14:37.139 align:start position:0% um for their uh 00:14:37.139 --> 00:14:40.189 align:start position:0% um for their uh Stark<00:14:37.860> Stark<00:14:38.279> net<00:14:38.519> wallet 00:14:40.189 --> 00:14:40.199 align:start position:0% Stark Stark net wallet 00:14:40.199 --> 00:14:41.689 align:start position:0% Stark Stark net wallet so<00:14:40.620> the<00:14:40.740> idea<00:14:40.920> is 00:14:41.689 --> 00:14:41.699 align:start position:0% so the idea is 00:14:41.699 --> 00:14:43.250 align:start position:0% so the idea is well<00:14:42.240> you<00:14:42.420> want<00:14:42.540> to<00:14:42.660> play<00:14:42.720> some<00:14:42.899> blockchain 00:14:43.250 --> 00:14:43.260 align:start position:0% well you want to play some blockchain 00:14:43.260 --> 00:14:44.329 align:start position:0% well you want to play some blockchain game 00:14:44.329 --> 00:14:44.339 align:start position:0% game 00:14:44.339 --> 00:14:47.750 align:start position:0% game and<00:14:45.120> you<00:14:45.420> don't<00:14:45.600> want<00:14:45.779> to<00:14:45.899> have<00:14:46.199> to<00:14:46.860> to<00:14:47.519> click 00:14:47.750 --> 00:14:47.760 align:start position:0% and you don't want to have to to click 00:14:47.760 --> 00:14:50.269 align:start position:0% and you don't want to have to to click approve<00:14:48.360> every<00:14:48.959> time<00:14:49.199> like<00:14:49.500> a<00:14:49.680> message<00:14:49.800> needs 00:14:50.269 --> 00:14:50.279 align:start position:0% approve every time like a message needs 00:14:50.279 --> 00:14:52.910 align:start position:0% approve every time like a message needs to<00:14:50.339> be<00:14:50.519> signed<00:14:50.940> that<00:14:51.720> that<00:14:51.720> would<00:14:52.079> really<00:14:52.320> you 00:14:52.910 --> 00:14:52.920 align:start position:0% to be signed that that would really you 00:14:52.920 --> 00:14:55.310 align:start position:0% to be signed that that would really you know<00:14:53.240> destruct<00:14:54.240> from<00:14:54.480> the<00:14:54.600> gaming<00:14:54.899> experience 00:14:55.310 --> 00:14:55.320 align:start position:0% know destruct from the gaming experience 00:14:55.320 --> 00:14:58.790 align:start position:0% know destruct from the gaming experience but<00:14:56.279> you<00:14:56.459> also<00:14:56.639> don't<00:14:56.760> want<00:14:57.000> to<00:14:57.120> give<00:14:57.800> this 00:14:58.790 --> 00:14:58.800 align:start position:0% but you also don't want to give this 00:14:58.800 --> 00:15:00.110 align:start position:0% but you also don't want to give this this<00:14:59.040> game 00:15:00.110 --> 00:15:00.120 align:start position:0% this game 00:15:00.120 --> 00:15:01.910 align:start position:0% this game full<00:15:00.540> power<00:15:00.779> over<00:15:01.079> your<00:15:01.320> wallet<00:15:01.620> that<00:15:01.740> would 00:15:01.910 --> 00:15:01.920 align:start position:0% full power over your wallet that would 00:15:01.920 --> 00:15:03.590 align:start position:0% full power over your wallet that would be<00:15:02.040> crazy<00:15:02.160> like<00:15:02.760> you<00:15:02.880> know<00:15:03.000> what<00:15:03.060> if<00:15:03.240> there's<00:15:03.360> a 00:15:03.590 --> 00:15:03.600 align:start position:0% be crazy like you know what if there's a 00:15:03.600 --> 00:15:07.370 align:start position:0% be crazy like you know what if there's a security<00:15:03.779> bug<00:15:04.500> in<00:15:04.800> the<00:15:04.980> game<00:15:05.519> so<00:15:06.360> ideally<00:15:06.779> you 00:15:07.370 --> 00:15:07.380 align:start position:0% security bug in the game so ideally you 00:15:07.380 --> 00:15:08.810 align:start position:0% security bug in the game so ideally you want<00:15:07.500> to<00:15:07.680> create<00:15:07.860> a<00:15:08.040> session<00:15:08.160> key<00:15:08.459> and<00:15:08.699> the 00:15:08.810 --> 00:15:08.820 align:start position:0% want to create a session key and the 00:15:08.820 --> 00:15:11.509 align:start position:0% want to create a session key and the session<00:15:08.940> key<00:15:09.440> has<00:15:10.440> the<00:15:10.740> ability<00:15:10.980> to<00:15:11.339> do 00:15:11.509 --> 00:15:11.519 align:start position:0% session key has the ability to do 00:15:11.519 --> 00:15:13.910 align:start position:0% session key has the ability to do whatever<00:15:12.120> is<00:15:12.420> needed<00:15:12.660> but<00:15:12.899> limited<00:15:13.440> to<00:15:13.740> the 00:15:13.910 --> 00:15:13.920 align:start position:0% whatever is needed but limited to the 00:15:13.920 --> 00:15:16.370 align:start position:0% whatever is needed but limited to the gaming<00:15:14.339> contract<00:15:14.760> nothing<00:15:15.600> else<00:15:15.899> and<00:15:16.320> then 00:15:16.370 --> 00:15:16.380 align:start position:0% gaming contract nothing else and then 00:15:16.380 --> 00:15:17.750 align:start position:0% gaming contract nothing else and then the<00:15:16.680> worst<00:15:16.800> thing<00:15:16.920> that<00:15:17.040> can<00:15:17.220> happen<00:15:17.339> is<00:15:17.579> I 00:15:17.750 --> 00:15:17.760 align:start position:0% the worst thing that can happen is I 00:15:17.760 --> 00:15:19.610 align:start position:0% the worst thing that can happen is I don't<00:15:17.880> know<00:15:17.940> maybe<00:15:18.060> you're<00:15:18.240> like<00:15:18.480> your<00:15:19.260> your 00:15:19.610 --> 00:15:19.620 align:start position:0% don't know maybe you're like your your 00:15:19.620 --> 00:15:23.030 align:start position:0% don't know maybe you're like your your game<00:15:20.220> sword<00:15:20.699> your<00:15:21.240> nft<00:15:21.540> items<00:15:22.019> are<00:15:22.079> stolen 00:15:23.030 --> 00:15:23.040 align:start position:0% game sword your nft items are stolen 00:15:23.040 --> 00:15:24.769 align:start position:0% game sword your nft items are stolen if<00:15:23.399> the<00:15:23.579> game<00:15:23.639> gets<00:15:23.940> hacked<00:15:24.180> but<00:15:24.360> everything 00:15:24.769 --> 00:15:24.779 align:start position:0% if the game gets hacked but everything 00:15:24.779 --> 00:15:26.050 align:start position:0% if the game gets hacked but everything else<00:15:25.019> is<00:15:25.260> safe 00:15:26.050 --> 00:15:26.060 align:start position:0% else is safe 00:15:26.060 --> 00:15:28.550 align:start position:0% else is safe and<00:15:27.060> you<00:15:27.240> could<00:15:27.360> you<00:15:27.720> could<00:15:27.779> just<00:15:27.959> store<00:15:28.199> this 00:15:28.550 --> 00:15:28.560 align:start position:0% and you could you could just store this 00:15:28.560 --> 00:15:32.090 align:start position:0% and you could you could just store this this<00:15:28.800> key<00:15:29.100> inside<00:15:29.339> your<00:15:29.639> browser<00:15:30.500> so<00:15:31.500> as<00:15:31.920> soon 00:15:32.090 --> 00:15:32.100 align:start position:0% this key inside your browser so as soon 00:15:32.100 --> 00:15:34.250 align:start position:0% this key inside your browser so as soon as<00:15:32.279> you<00:15:32.579> you<00:15:33.000> authorize<00:15:33.480> this<00:15:33.720> as<00:15:33.839> soon<00:15:33.959> as<00:15:34.139> you 00:15:34.250 --> 00:15:34.260 align:start position:0% as you you authorize this as soon as you 00:15:34.260 --> 00:15:36.290 align:start position:0% as you you authorize this as soon as you generated<00:15:34.560> the<00:15:34.740> session<00:15:34.920> key 00:15:36.290 --> 00:15:36.300 align:start position:0% generated the session key 00:15:36.300 --> 00:15:37.970 align:start position:0% generated the session key um<00:15:36.420> from<00:15:36.600> that<00:15:36.779> point<00:15:36.899> onwards<00:15:37.500> you're<00:15:37.800> not 00:15:37.970 --> 00:15:37.980 align:start position:0% um from that point onwards you're not 00:15:37.980 --> 00:15:38.870 align:start position:0% um from that point onwards you're not even 00:15:38.870 --> 00:15:38.880 align:start position:0% even 00:15:38.880 --> 00:15:40.910 align:start position:0% even uh<00:15:39.660> you<00:15:39.839> don't<00:15:39.899> have<00:15:40.019> to<00:15:40.139> be<00:15:40.199> in<00:15:40.380> the<00:15:40.500> loop<00:15:40.680> in 00:15:40.910 --> 00:15:40.920 align:start position:0% uh you don't have to be in the loop in 00:15:40.920 --> 00:15:43.009 align:start position:0% uh you don't have to be in the loop in terms<00:15:41.100> of<00:15:41.160> authorizing<00:15:41.760> transactions<00:15:42.480> and 00:15:43.009 --> 00:15:43.019 align:start position:0% terms of authorizing transactions and 00:15:43.019 --> 00:15:45.710 align:start position:0% terms of authorizing transactions and just<00:15:43.260> becomes<00:15:43.680> transparent<00:15:44.220> so<00:15:44.760> that's<00:15:45.420> a 00:15:45.710 --> 00:15:45.720 align:start position:0% just becomes transparent so that's a 00:15:45.720 --> 00:15:48.710 align:start position:0% just becomes transparent so that's a really<00:15:45.839> nice<00:15:46.139> that's<00:15:46.620> a<00:15:46.740> really<00:15:46.860> nice<00:15:47.100> one 00:15:48.710 --> 00:15:48.720 align:start position:0% really nice that's a really nice one 00:15:48.720 --> 00:15:49.490 align:start position:0% really nice that's a really nice one um 00:15:49.490 --> 00:15:49.500 align:start position:0% um 00:15:49.500 --> 00:15:51.410 align:start position:0% um well<00:15:49.920> the<00:15:50.100> session<00:15:50.279> Keys<00:15:50.639> also<00:15:50.820> you<00:15:50.940> could<00:15:51.180> you 00:15:51.410 --> 00:15:51.420 align:start position:0% well the session Keys also you could you 00:15:51.420 --> 00:15:53.449 align:start position:0% well the session Keys also you could you can<00:15:51.540> mix<00:15:51.720> you<00:15:52.320> can<00:15:52.440> mix<00:15:52.620> what<00:15:53.100> we<00:15:53.220> were<00:15:53.339> talking 00:15:53.449 --> 00:15:53.459 align:start position:0% can mix you can mix what we were talking 00:15:53.459 --> 00:15:55.490 align:start position:0% can mix you can mix what we were talking about<00:15:53.579> before<00:15:53.880> so<00:15:54.420> you<00:15:54.899> could<00:15:55.019> have<00:15:55.199> a<00:15:55.380> session 00:15:55.490 --> 00:15:55.500 align:start position:0% about before so you could have a session 00:15:55.500 --> 00:15:58.970 align:start position:0% about before so you could have a session key<00:15:55.800> not<00:15:56.160> only<00:15:56.279> has<00:15:56.519> maybe<00:15:56.699> limited<00:15:57.180> access 00:15:58.970 --> 00:15:58.980 align:start position:0% key not only has maybe limited access 00:15:58.980 --> 00:16:02.810 align:start position:0% key not only has maybe limited access um<00:15:59.040> to<00:15:59.760> uh<00:16:00.480> to<00:16:00.720> a<00:16:00.839> specific<00:16:01.019> contract<00:16:01.500> but<00:16:02.399> you 00:16:02.810 --> 00:16:02.820 align:start position:0% um to uh to a specific contract but you 00:16:02.820 --> 00:16:05.870 align:start position:0% um to uh to a specific contract but you know<00:16:02.940> maybe<00:16:03.120> you<00:16:03.540> have<00:16:03.720> multiple<00:16:04.019> devices<00:16:04.880> and 00:16:05.870 --> 00:16:05.880 align:start position:0% know maybe you have multiple devices and 00:16:05.880 --> 00:16:10.310 align:start position:0% know maybe you have multiple devices and you<00:16:06.300> want<00:16:06.480> very<00:16:06.959> easy<00:16:07.139> things<00:16:07.820> to<00:16:08.820> be<00:16:09.120> uh<00:16:10.019> like 00:16:10.310 --> 00:16:10.320 align:start position:0% you want very easy things to be uh like 00:16:10.320 --> 00:16:13.310 align:start position:0% you want very easy things to be uh like very<00:16:10.620> not<00:16:11.399> not<00:16:11.639> secure<00:16:12.120> thing<00:16:12.420> things<00:16:13.139> that 00:16:13.310 --> 00:16:13.320 align:start position:0% very not not secure thing things that 00:16:13.320 --> 00:16:15.889 align:start position:0% very not not secure thing things that are<00:16:13.500> not<00:16:13.620> very<00:16:13.860> risky 00:16:15.889 --> 00:16:15.899 align:start position:0% are not very risky 00:16:15.899 --> 00:16:20.750 align:start position:0% are not very risky um<00:16:16.019> to<00:16:16.500> be<00:16:16.680> very<00:16:17.339> easy<00:16:17.519> from<00:16:18.240> your<00:16:18.420> computer<00:16:18.660> so 00:16:20.750 --> 00:16:20.760 align:start position:0% um to be very easy from your computer so 00:16:20.760 --> 00:16:22.189 align:start position:0% um to be very easy from your computer so um<00:16:20.820> maybe<00:16:21.000> if<00:16:21.120> you<00:16:21.240> just<00:16:21.660> want<00:16:21.779> to<00:16:21.839> sign<00:16:21.959> into 00:16:22.189 --> 00:16:22.199 align:start position:0% um maybe if you just want to sign into 00:16:22.199 --> 00:16:24.829 align:start position:0% um maybe if you just want to sign into an<00:16:22.500> event<00:16:22.680> or<00:16:23.279> or 00:16:24.829 --> 00:16:24.839 align:start position:0% an event or or 00:16:24.839 --> 00:16:25.970 align:start position:0% an event or or um you<00:16:25.079> know<00:16:25.139> something<00:16:25.320> that<00:16:25.560> doesn't<00:16:25.740> have 00:16:25.970 --> 00:16:25.980 align:start position:0% um you know something that doesn't have 00:16:25.980 --> 00:16:28.189 align:start position:0% um you know something that doesn't have world<00:16:26.459> changing<00:16:26.880> implications<00:16:27.360> if<00:16:28.079> your 00:16:28.189 --> 00:16:28.199 align:start position:0% world changing implications if your 00:16:28.199 --> 00:16:30.170 align:start position:0% world changing implications if your computer<00:16:28.440> gets<00:16:28.860> hacked<00:16:29.160> so<00:16:29.639> you<00:16:29.760> authorize 00:16:30.170 --> 00:16:30.180 align:start position:0% computer gets hacked so you authorize 00:16:30.180 --> 00:16:32.150 align:start position:0% computer gets hacked so you authorize your<00:16:30.300> browser 00:16:32.150 --> 00:16:32.160 align:start position:0% your browser 00:16:32.160 --> 00:16:35.629 align:start position:0% your browser um<00:16:32.420> and<00:16:33.420> you<00:16:34.199> you<00:16:34.320> would<00:16:34.560> still<00:16:34.860> you<00:16:35.339> you<00:16:35.339> know 00:16:35.629 --> 00:16:35.639 align:start position:0% um and you you would still you you know 00:16:35.639 --> 00:16:38.569 align:start position:0% um and you you would still you you know you<00:16:35.820> would<00:16:36.000> still<00:16:36.480> um<00:16:36.480> have<00:16:36.720> cap<00:16:36.959> control 00:16:38.569 --> 00:16:38.579 align:start position:0% you would still um have cap control 00:16:38.579 --> 00:16:40.249 align:start position:0% you would still um have cap control um<00:16:38.639> over<00:16:38.940> your<00:16:39.480> account<00:16:39.600> in<00:16:39.899> case<00:16:40.079> something 00:16:40.249 --> 00:16:40.259 align:start position:0% um over your account in case something 00:16:40.259 --> 00:16:42.889 align:start position:0% um over your account in case something goes<00:16:40.620> wrong<00:16:40.820> browsers<00:16:41.820> are<00:16:42.120> not<00:16:42.360> the<00:16:42.779> most 00:16:42.889 --> 00:16:42.899 align:start position:0% goes wrong browsers are not the most 00:16:42.899 --> 00:16:44.930 align:start position:0% goes wrong browsers are not the most secure<00:16:43.199> platforms 00:16:44.930 --> 00:16:44.940 align:start position:0% secure platforms 00:16:44.940 --> 00:16:46.550 align:start position:0% secure platforms um<00:16:45.000> but<00:16:45.240> you<00:16:45.360> could<00:16:45.480> just<00:16:45.600> limit<00:16:45.779> how<00:16:46.440> much 00:16:46.550 --> 00:16:46.560 align:start position:0% um but you could just limit how much 00:16:46.560 --> 00:16:49.129 align:start position:0% um but you could just limit how much power<00:16:46.740> the<00:16:47.040> browser<00:16:47.399> has<00:16:47.639> uh<00:16:48.600> over<00:16:48.899> your 00:16:49.129 --> 00:16:49.139 align:start position:0% power the browser has uh over your 00:16:49.139 --> 00:16:50.509 align:start position:0% power the browser has uh over your assets 00:16:50.509 --> 00:16:50.519 align:start position:0% assets 00:16:50.519 --> 00:16:52.069 align:start position:0% assets so 00:16:52.069 --> 00:16:52.079 align:start position:0% so 00:16:52.079 --> 00:16:55.189 align:start position:0% so um there's<00:16:52.320> also<00:16:52.620> a<00:16:52.800> big<00:16:52.980> ux<00:16:53.519> issue<00:16:53.940> with<00:16:54.240> gas 00:16:55.189 --> 00:16:55.199 align:start position:0% um there's also a big ux issue with gas 00:16:55.199 --> 00:16:58.249 align:start position:0% um there's also a big ux issue with gas where<00:16:55.980> you<00:16:56.279> know<00:16:56.339> the<00:16:56.459> traditional<00:16:57.000> web<00:16:57.720> tool 00:16:58.249 --> 00:16:58.259 align:start position:0% where you know the traditional web tool 00:16:58.259 --> 00:16:59.930 align:start position:0% where you know the traditional web tool world 00:16:59.930 --> 00:16:59.940 align:start position:0% world 00:16:59.940 --> 00:17:01.670 align:start position:0% world where<00:17:00.420> most<00:17:00.660> of<00:17:00.779> our<00:17:00.839> users<00:17:01.139> will<00:17:01.380> be<00:17:01.500> coming 00:17:01.670 --> 00:17:01.680 align:start position:0% where most of our users will be coming 00:17:01.680 --> 00:17:05.329 align:start position:0% where most of our users will be coming from<00:17:02.040> a<00:17:02.759> gas<00:17:03.000> is<00:17:03.240> not<00:17:03.420> really<00:17:03.600> a<00:17:03.779> concept<00:17:04.140> so<00:17:04.980> if 00:17:05.329 --> 00:17:05.339 align:start position:0% from a gas is not really a concept so if 00:17:05.339 --> 00:17:07.490 align:start position:0% from a gas is not really a concept so if you<00:17:05.520> have<00:17:05.760> a<00:17:06.059> server<00:17:06.959> you're<00:17:07.260> not<00:17:07.380> really 00:17:07.490 --> 00:17:07.500 align:start position:0% you have a server you're not really 00:17:07.500 --> 00:17:09.350 align:start position:0% you have a server you're not really thinking<00:17:07.799> about<00:17:07.919> who's<00:17:08.220> paying<00:17:08.640> to<00:17:09.000> run<00:17:09.240> the 00:17:09.350 --> 00:17:09.360 align:start position:0% thinking about who's paying to run the 00:17:09.360 --> 00:17:12.470 align:start position:0% thinking about who's paying to run the server<00:17:09.740> and<00:17:10.740> uh<00:17:11.100> how<00:17:11.339> do<00:17:11.459> I<00:17:11.579> share<00:17:12.179> in<00:17:12.299> the 00:17:12.470 --> 00:17:12.480 align:start position:0% server and uh how do I share in the 00:17:12.480 --> 00:17:15.350 align:start position:0% server and uh how do I share in the costs<00:17:12.720> it<00:17:12.959> just<00:17:13.199> somehow<00:17:13.500> works<00:17:14.400> behind<00:17:15.240> the 00:17:15.350 --> 00:17:15.360 align:start position:0% costs it just somehow works behind the 00:17:15.360 --> 00:17:18.049 align:start position:0% costs it just somehow works behind the scenes<00:17:15.860> and<00:17:16.860> users<00:17:17.339> who<00:17:17.520> are<00:17:17.640> new<00:17:17.760> to<00:17:17.939> the 00:17:18.049 --> 00:17:18.059 align:start position:0% scenes and users who are new to the 00:17:18.059 --> 00:17:20.809 align:start position:0% scenes and users who are new to the space<00:17:18.240> will<00:17:18.780> not<00:17:19.020> be<00:17:19.260> really<00:17:19.620> familiar 00:17:20.809 --> 00:17:20.819 align:start position:0% space will not be really familiar 00:17:20.819 --> 00:17:22.850 align:start position:0% space will not be really familiar um<00:17:20.880> with<00:17:21.059> the<00:17:21.179> concept<00:17:21.419> of<00:17:21.600> gas<00:17:21.839> and<00:17:22.500> it's<00:17:22.620> also 00:17:22.850 --> 00:17:22.860 align:start position:0% um with the concept of gas and it's also 00:17:22.860 --> 00:17:24.169 align:start position:0% um with the concept of gas and it's also a<00:17:22.919> hassle<00:17:23.220> even<00:17:23.400> for<00:17:23.640> people<00:17:23.819> who<00:17:24.059> are 00:17:24.169 --> 00:17:24.179 align:start position:0% a hassle even for people who are 00:17:24.179 --> 00:17:28.130 align:start position:0% a hassle even for people who are familiar<00:17:24.799> so<00:17:25.819> with<00:17:26.819> with<00:17:27.120> uh<00:17:27.600> abstract 00:17:28.130 --> 00:17:28.140 align:start position:0% familiar so with with uh abstract 00:17:28.140 --> 00:17:29.270 align:start position:0% familiar so with with uh abstract accounts 00:17:29.270 --> 00:17:29.280 align:start position:0% accounts 00:17:29.280 --> 00:17:29.990 align:start position:0% accounts um 00:17:29.990 --> 00:17:30.000 align:start position:0% um 00:17:30.000 --> 00:17:31.909 align:start position:0% um you<00:17:30.660> can<00:17:30.780> you<00:17:31.260> can<00:17:31.440> have<00:17:31.559> a<00:17:31.679> lot<00:17:31.799> more 00:17:31.909 --> 00:17:31.919 align:start position:0% you can you can have a lot more 00:17:31.919 --> 00:17:34.610 align:start position:0% you can you can have a lot more flexibility<00:17:32.340> in<00:17:32.640> how<00:17:32.820> you<00:17:32.940> handle<00:17:33.299> this<00:17:33.620> so 00:17:34.610 --> 00:17:34.620 align:start position:0% flexibility in how you handle this so 00:17:34.620 --> 00:17:36.710 align:start position:0% flexibility in how you handle this so for<00:17:34.980> example<00:17:35.220> if<00:17:35.640> you're<00:17:35.760> a<00:17:35.940> game 00:17:36.710 --> 00:17:36.720 align:start position:0% for example if you're a game 00:17:36.720 --> 00:17:39.289 align:start position:0% for example if you're a game especially<00:17:37.679> if<00:17:37.919> you're<00:17:38.039> running<00:17:38.280> on<00:17:38.940> a<00:17:39.059> cheap 00:17:39.289 --> 00:17:39.299 align:start position:0% especially if you're running on a cheap 00:17:39.299 --> 00:17:42.230 align:start position:0% especially if you're running on a cheap uh<00:17:40.020> cheaper<00:17:40.380> layer<00:17:40.740> 2<00:17:40.919> you<00:17:41.520> could<00:17:41.640> decide<00:17:41.940> hey 00:17:42.230 --> 00:17:42.240 align:start position:0% uh cheaper layer 2 you could decide hey 00:17:42.240 --> 00:17:44.930 align:start position:0% uh cheaper layer 2 you could decide hey it's<00:17:42.600> worth<00:17:43.080> worth<00:17:43.559> just<00:17:43.919> subsidizing<00:17:44.700> the 00:17:44.930 --> 00:17:44.940 align:start position:0% it's worth worth just subsidizing the 00:17:44.940 --> 00:17:48.409 align:start position:0% it's worth worth just subsidizing the transactions<00:17:45.660> as<00:17:46.559> part<00:17:46.860> of<00:17:46.980> my<00:17:47.419> onboarding 00:17:48.409 --> 00:17:48.419 align:start position:0% transactions as part of my onboarding 00:17:48.419 --> 00:17:50.450 align:start position:0% transactions as part of my onboarding process 00:17:50.450 --> 00:17:50.460 align:start position:0% process 00:17:50.460 --> 00:17:51.230 align:start position:0% process um 00:17:51.230 --> 00:17:51.240 align:start position:0% um 00:17:51.240 --> 00:17:55.850 align:start position:0% um it's<00:17:51.720> very<00:17:52.020> common<00:17:52.260> to<00:17:52.919> to<00:17:53.520> have<00:17:54.000> to<00:17:54.299> like 00:17:55.850 --> 00:17:55.860 align:start position:0% it's very common to to have to like 00:17:55.860 --> 00:17:57.950 align:start position:0% it's very common to to have to like um<00:17:55.919> budget<00:17:56.580> some<00:17:57.000> amount 00:17:57.950 --> 00:17:57.960 align:start position:0% um budget some amount 00:17:57.960 --> 00:18:02.330 align:start position:0% um budget some amount in<00:17:58.500> order<00:17:58.620> to<00:17:59.360> acquire<00:18:00.360> users<00:18:00.980> so<00:18:01.980> if<00:18:02.100> it's<00:18:02.220> not 00:18:02.330 --> 00:18:02.340 align:start position:0% in order to acquire users so if it's not 00:18:02.340 --> 00:18:05.090 align:start position:0% in order to acquire users so if it's not prohibitedly<00:18:03.000> expensive<00:18:03.660> maybe<00:18:04.080> you<00:18:04.860> want<00:18:04.980> to 00:18:05.090 --> 00:18:05.100 align:start position:0% prohibitedly expensive maybe you want to 00:18:05.100 --> 00:18:07.850 align:start position:0% prohibitedly expensive maybe you want to do<00:18:05.160> that<00:18:05.340> and<00:18:05.520> then<00:18:05.700> you<00:18:05.940> know<00:18:06.000> later 00:18:07.850 --> 00:18:07.860 align:start position:0% do that and then you know later 00:18:07.860 --> 00:18:10.730 align:start position:0% do that and then you know later um<00:18:07.980> that's<00:18:08.520> worth<00:18:08.760> your<00:18:08.940> while 00:18:10.730 --> 00:18:10.740 align:start position:0% um that's worth your while 00:18:10.740 --> 00:18:13.250 align:start position:0% um that's worth your while um<00:18:10.860> another<00:18:11.280> very<00:18:12.179> obvious<00:18:12.539> one<00:18:12.780> is<00:18:13.020> just 00:18:13.250 --> 00:18:13.260 align:start position:0% um another very obvious one is just 00:18:13.260 --> 00:18:16.549 align:start position:0% um another very obvious one is just being<00:18:13.620> able<00:18:13.860> to<00:18:14.039> pay<00:18:14.220> gas<00:18:14.520> in<00:18:15.419> any<00:18:15.539> erc20<00:18:16.200> token 00:18:16.549 --> 00:18:16.559 align:start position:0% being able to pay gas in any erc20 token 00:18:16.559 --> 00:18:18.169 align:start position:0% being able to pay gas in any erc20 token anything<00:18:16.740> that<00:18:17.039> has<00:18:17.160> value 00:18:18.169 --> 00:18:18.179 align:start position:0% anything that has value 00:18:18.179 --> 00:18:20.210 align:start position:0% anything that has value so<00:18:19.020> if<00:18:19.500> you're 00:18:20.210 --> 00:18:20.220 align:start position:0% so if you're 00:18:20.220 --> 00:18:22.730 align:start position:0% so if you're if I<00:18:20.760> pay<00:18:20.940> you<00:18:21.059> in<00:18:21.240> usdc 00:18:22.730 --> 00:18:22.740 align:start position:0% if I pay you in usdc 00:18:22.740 --> 00:18:25.070 align:start position:0% if I pay you in usdc there's<00:18:23.280> no<00:18:23.460> reason<00:18:23.700> that<00:18:24.120> I<00:18:24.600> would<00:18:24.720> also<00:18:24.960> need 00:18:25.070 --> 00:18:25.080 align:start position:0% there's no reason that I would also need 00:18:25.080 --> 00:18:27.830 align:start position:0% there's no reason that I would also need to<00:18:25.260> send<00:18:25.380> eth<00:18:25.860> into<00:18:26.460> your<00:18:26.640> account 00:18:27.830 --> 00:18:27.840 align:start position:0% to send eth into your account 00:18:27.840 --> 00:18:29.870 align:start position:0% to send eth into your account um<00:18:27.900> for<00:18:28.200> you<00:18:28.260> to<00:18:28.380> move<00:18:28.500> that<00:18:28.860> usdc<00:18:29.460> and<00:18:29.760> maybe 00:18:29.870 --> 00:18:29.880 align:start position:0% um for you to move that usdc and maybe 00:18:29.880 --> 00:18:31.450 align:start position:0% um for you to move that usdc and maybe pay<00:18:30.120> your<00:18:30.240> bills<00:18:30.539> with<00:18:30.720> it 00:18:31.450 --> 00:18:31.460 align:start position:0% pay your bills with it 00:18:31.460 --> 00:18:34.789 align:start position:0% pay your bills with it uh<00:18:32.460> it's<00:18:32.820> it's<00:18:33.120> nice<00:18:33.419> if<00:18:33.600> you<00:18:33.840> have<00:18:34.020> the<00:18:34.500> you 00:18:34.789 --> 00:18:34.799 align:start position:0% uh it's it's nice if you have the you 00:18:34.799 --> 00:18:37.250 align:start position:0% uh it's it's nice if you have the you know<00:18:34.860> if<00:18:35.039> you<00:18:35.160> have<00:18:35.280> an<00:18:35.460> account<00:18:35.780> you<00:18:36.780> whatever 00:18:37.250 --> 00:18:37.260 align:start position:0% know if you have an account you whatever 00:18:37.260 --> 00:18:40.190 align:start position:0% know if you have an account you whatever whatever<00:18:37.860> you<00:18:38.280> have<00:18:38.400> a<00:18:38.580> value<00:18:38.760> there 00:18:40.190 --> 00:18:40.200 align:start position:0% whatever you have a value there 00:18:40.200 --> 00:18:41.930 align:start position:0% whatever you have a value there um<00:18:40.320> like<00:18:40.500> when<00:18:40.740> you<00:18:40.860> know<00:18:41.100> someone<00:18:41.460> sends<00:18:41.880> you 00:18:41.930 --> 00:18:41.940 align:start position:0% um like when you know someone sends you 00:18:41.940 --> 00:18:43.909 align:start position:0% um like when you know someone sends you a<00:18:42.059> PayPal 00:18:43.909 --> 00:18:43.919 align:start position:0% a PayPal 00:18:43.919 --> 00:18:46.010 align:start position:0% a PayPal um<00:18:44.039> PayPal<00:18:44.520> transfer<00:18:45.059> they<00:18:45.660> don't<00:18:45.780> have<00:18:45.900> to 00:18:46.010 --> 00:18:46.020 align:start position:0% um PayPal transfer they don't have to 00:18:46.020 --> 00:18:48.470 align:start position:0% um PayPal transfer they don't have to send<00:18:46.200> you<00:18:46.320> like<00:18:46.500> some<00:18:46.799> other<00:18:47.039> PayPal<00:18:48.000> tokens 00:18:48.470 --> 00:18:48.480 align:start position:0% send you like some other PayPal tokens 00:18:48.480 --> 00:18:51.409 align:start position:0% send you like some other PayPal tokens so<00:18:48.900> you<00:18:49.020> can<00:18:49.140> move<00:18:49.440> you<00:18:50.280> know<00:18:50.340> your<00:18:50.640> US<00:18:50.880> dollars 00:18:51.409 --> 00:18:51.419 align:start position:0% so you can move you know your US dollars 00:18:51.419 --> 00:18:54.350 align:start position:0% so you can move you know your US dollars in<00:18:51.840> PayPal<00:18:52.200> to<00:18:52.559> somewhere<00:18:52.860> else 00:18:54.350 --> 00:18:54.360 align:start position:0% in PayPal to somewhere else 00:18:54.360 --> 00:18:57.289 align:start position:0% in PayPal to somewhere else um<00:18:54.419> so<00:18:54.600> payment<00:18:54.780> becomes<00:18:55.320> a<00:18:55.440> lot<00:18:55.559> easier 00:18:57.289 --> 00:18:57.299 align:start position:0% um so payment becomes a lot easier 00:18:57.299 --> 00:18:59.450 align:start position:0% um so payment becomes a lot easier um<00:18:57.360> but<00:18:57.900> also<00:18:58.260> you<00:18:58.860> know<00:18:58.980> maybe<00:18:59.220> you're 00:18:59.450 --> 00:18:59.460 align:start position:0% um but also you know maybe you're 00:18:59.460 --> 00:19:02.270 align:start position:0% um but also you know maybe you're participating<00:19:00.059> in<00:19:00.480> in<00:19:00.720> some<00:19:01.500> governance<00:19:01.919> and 00:19:02.270 --> 00:19:02.280 align:start position:0% participating in in some governance and 00:19:02.280 --> 00:19:04.250 align:start position:0% participating in in some governance and uh<00:19:03.059> the<00:19:03.240> the<00:19:03.419> governance<00:19:03.780> of<00:19:03.960> that<00:19:04.080> project 00:19:04.250 --> 00:19:04.260 align:start position:0% uh the the governance of that project 00:19:04.260 --> 00:19:05.870 align:start position:0% uh the the governance of that project doesn't<00:19:04.980> want<00:19:05.280> you<00:19:05.400> to<00:19:05.520> have<00:19:05.640> to<00:19:05.760> think 00:19:05.870 --> 00:19:05.880 align:start position:0% doesn't want you to have to think 00:19:05.880 --> 00:19:08.150 align:start position:0% doesn't want you to have to think whether<00:19:06.120> it's<00:19:06.360> worth<00:19:06.539> your<00:19:06.720> while<00:19:06.900> to<00:19:07.740> pay<00:19:07.919> the 00:19:08.150 --> 00:19:08.160 align:start position:0% whether it's worth your while to pay the 00:19:08.160 --> 00:19:11.210 align:start position:0% whether it's worth your while to pay the gas<00:19:08.340> for<00:19:08.820> the<00:19:08.940> interaction<00:19:09.240> or<00:19:09.539> not 00:19:11.210 --> 00:19:11.220 align:start position:0% gas for the interaction or not 00:19:11.220 --> 00:19:15.230 align:start position:0% gas for the interaction or not um<00:19:11.340> so<00:19:11.580> they<00:19:11.760> just<00:19:12.000> decide<00:19:12.360> to<00:19:12.480> subsidize<00:19:13.080> that 00:19:15.230 --> 00:19:15.240 align:start position:0% um so they just decide to subsidize that 00:19:15.240 --> 00:19:17.630 align:start position:0% um so they just decide to subsidize that um<00:19:15.360> or<00:19:15.660> you<00:19:15.780> could<00:19:15.960> maybe<00:19:16.559> you<00:19:17.220> know<00:19:17.280> you<00:19:17.460> have 00:19:17.630 --> 00:19:17.640 align:start position:0% um or you could maybe you know you have 00:19:17.640 --> 00:19:19.310 align:start position:0% um or you could maybe you know you have some<00:19:17.820> allotment<00:19:18.299> and<00:19:18.600> if<00:19:18.720> you<00:19:18.840> go<00:19:18.960> beyond<00:19:19.200> the 00:19:19.310 --> 00:19:19.320 align:start position:0% some allotment and if you go beyond the 00:19:19.320 --> 00:19:21.710 align:start position:0% some allotment and if you go beyond the allotment<00:19:19.620> you<00:19:19.860> have<00:19:19.980> to<00:19:20.100> pay<00:19:20.220> in<00:19:20.520> the<00:19:20.760> in<00:19:21.419> that 00:19:21.710 --> 00:19:21.720 align:start position:0% allotment you have to pay in the in that 00:19:21.720 --> 00:19:25.190 align:start position:0% allotment you have to pay in the in that uh<00:19:22.020> project<00:19:22.260> tokens 00:19:25.190 --> 00:19:25.200 align:start position:0% 00:19:25.200 --> 00:19:27.289 align:start position:0% the<00:19:25.860> nice<00:19:25.980> thing<00:19:26.160> about<00:19:26.400> being<00:19:26.880> able<00:19:27.059> to 00:19:27.289 --> 00:19:27.299 align:start position:0% the nice thing about being able to 00:19:27.299 --> 00:19:29.450 align:start position:0% the nice thing about being able to interact<00:19:27.660> with<00:19:28.559> uh<00:19:28.740> with<00:19:29.039> a<00:19:29.160> blockchain 00:19:29.450 --> 00:19:29.460 align:start position:0% interact with uh with a blockchain 00:19:29.460 --> 00:19:31.870 align:start position:0% interact with uh with a blockchain without<00:19:29.940> needing<00:19:30.360> eth<00:19:30.660> is<00:19:30.840> it<00:19:31.020> also<00:19:31.320> has<00:19:31.500> some 00:19:31.870 --> 00:19:31.880 align:start position:0% without needing eth is it also has some 00:19:31.880 --> 00:19:34.250 align:start position:0% without needing eth is it also has some privacy<00:19:32.880> bonuses 00:19:34.250 --> 00:19:34.260 align:start position:0% privacy bonuses 00:19:34.260 --> 00:19:37.130 align:start position:0% privacy bonuses so<00:19:35.100> because<00:19:35.520> if<00:19:36.360> you<00:19:36.480> go<00:19:36.600> through<00:19:36.780> the<00:19:36.900> usual 00:19:37.130 --> 00:19:37.140 align:start position:0% so because if you go through the usual 00:19:37.140 --> 00:19:39.770 align:start position:0% so because if you go through the usual kyc<00:19:37.679> process<00:19:38.039> someone<00:19:38.880> knows<00:19:39.240> who<00:19:39.419> you<00:19:39.539> are 00:19:39.770 --> 00:19:39.780 align:start position:0% kyc process someone knows who you are 00:19:39.780 --> 00:19:41.630 align:start position:0% kyc process someone knows who you are and<00:19:40.320> their<00:19:40.500> companies<00:19:40.919> that<00:19:41.100> are<00:19:41.280> dedicated 00:19:41.630 --> 00:19:41.640 align:start position:0% and their companies that are dedicated 00:19:41.640 --> 00:19:43.669 align:start position:0% and their companies that are dedicated to<00:19:41.880> linking<00:19:42.299> all<00:19:42.419> the<00:19:42.600> information 00:19:43.669 --> 00:19:43.679 align:start position:0% to linking all the information 00:19:43.679 --> 00:19:45.830 align:start position:0% to linking all the information uh<00:19:44.280> together 00:19:45.830 --> 00:19:45.840 align:start position:0% uh together 00:19:45.840 --> 00:19:47.510 align:start position:0% uh together um<00:19:45.960> so<00:19:46.140> you<00:19:46.320> don't<00:19:46.440> have<00:19:46.559> privacy 00:19:47.510 --> 00:19:47.520 align:start position:0% um so you don't have privacy 00:19:47.520 --> 00:19:49.610 align:start position:0% um so you don't have privacy but 00:19:49.610 --> 00:19:49.620 align:start position:0% but 00:19:49.620 --> 00:19:51.650 align:start position:0% but um<00:19:49.679> yeah<00:19:50.039> that<00:19:50.280> would<00:19:50.400> that<00:19:50.580> would<00:19:50.760> be<00:19:51.000> that 00:19:51.650 --> 00:19:51.660 align:start position:0% um yeah that would that would be that 00:19:51.660 --> 00:19:53.810 align:start position:0% um yeah that would that would be that wouldn't<00:19:51.840> be<00:19:52.020> an<00:19:52.140> issue<00:19:52.380> if<00:19:52.740> you<00:19:52.860> can<00:19:53.039> just 00:19:53.810 --> 00:19:53.820 align:start position:0% wouldn't be an issue if you can just 00:19:53.820 --> 00:19:56.690 align:start position:0% wouldn't be an issue if you can just um<00:19:54.020> receive<00:19:55.020> payment<00:19:55.320> in<00:19:55.679> any<00:19:55.860> token<00:19:56.220> and<00:19:56.400> also 00:19:56.690 --> 00:19:56.700 align:start position:0% um receive payment in any token and also 00:19:56.700 --> 00:19:59.390 align:start position:0% um receive payment in any token and also pay<00:19:56.820> for<00:19:57.000> the<00:19:57.120> gas<00:19:57.240> in<00:19:57.480> any<00:19:57.600> token<00:19:58.400> because 00:19:59.390 --> 00:19:59.400 align:start position:0% pay for the gas in any token because 00:19:59.400 --> 00:20:02.830 align:start position:0% pay for the gas in any token because let's<00:19:59.580> say<00:19:59.760> I'm<00:20:00.000> a<00:20:00.120> contractor<00:20:00.860> and<00:20:01.860> I<00:20:02.460> work 00:20:02.830 --> 00:20:02.840 align:start position:0% let's say I'm a contractor and I work 00:20:02.840 --> 00:20:05.990 align:start position:0% let's say I'm a contractor and I work online<00:20:03.840> for<00:20:04.260> you<00:20:04.440> and<00:20:04.980> I'm<00:20:05.280> pseudo<00:20:05.640> Anonymous 00:20:05.990 --> 00:20:06.000 align:start position:0% online for you and I'm pseudo Anonymous 00:20:06.000 --> 00:20:08.750 align:start position:0% online for you and I'm pseudo Anonymous I<00:20:06.660> do<00:20:06.780> the<00:20:06.900> work<00:20:07.140> I<00:20:07.500> give<00:20:07.679> you<00:20:07.799> an<00:20:07.980> address<00:20:08.100> you 00:20:08.750 --> 00:20:08.760 align:start position:0% I do the work I give you an address you 00:20:08.760 --> 00:20:11.510 align:start position:0% I do the work I give you an address you pay<00:20:08.940> me<00:20:09.440> and<00:20:10.440> you<00:20:10.740> know<00:20:10.799> I<00:20:10.919> would<00:20:11.039> be<00:20:11.220> able<00:20:11.400> to 00:20:11.510 --> 00:20:11.520 align:start position:0% pay me and you know I would be able to 00:20:11.520 --> 00:20:15.289 align:start position:0% pay me and you know I would be able to pay<00:20:11.940> my<00:20:12.419> bills<00:20:12.720> with<00:20:13.020> that<00:20:13.200> or<00:20:14.100> or<00:20:14.160> or<00:20:14.520> buy 00:20:15.289 --> 00:20:15.299 align:start position:0% pay my bills with that or or or buy 00:20:15.299 --> 00:20:18.350 align:start position:0% pay my bills with that or or or buy something<00:20:15.539> online<00:20:15.840> or<00:20:16.260> whatever<00:20:16.760> and<00:20:17.760> I 00:20:18.350 --> 00:20:18.360 align:start position:0% something online or whatever and I 00:20:18.360 --> 00:20:21.890 align:start position:0% something online or whatever and I wouldn't<00:20:18.480> need<00:20:18.840> to<00:20:19.320> also<00:20:19.980> acquire<00:20:20.340> eth 00:20:21.890 --> 00:20:21.900 align:start position:0% wouldn't need to also acquire eth 00:20:21.900 --> 00:20:23.270 align:start position:0% wouldn't need to also acquire eth um and<00:20:22.140> I<00:20:22.200> could<00:20:22.320> also<00:20:22.559> separate<00:20:22.980> let's<00:20:23.160> say 00:20:23.270 --> 00:20:23.280 align:start position:0% um and I could also separate let's say 00:20:23.280 --> 00:20:24.529 align:start position:0% um and I could also separate let's say I'm<00:20:23.400> working<00:20:23.580> with<00:20:23.940> with<00:20:24.240> different 00:20:24.529 --> 00:20:24.539 align:start position:0% I'm working with with different 00:20:24.539 --> 00:20:26.270 align:start position:0% I'm working with with different customers<00:20:25.020> I<00:20:25.320> could<00:20:25.440> give<00:20:25.620> each<00:20:25.860> of<00:20:26.039> them<00:20:26.100> a 00:20:26.270 --> 00:20:26.280 align:start position:0% customers I could give each of them a 00:20:26.280 --> 00:20:28.310 align:start position:0% customers I could give each of them a separate<00:20:26.580> address<00:20:26.780> and<00:20:27.780> the<00:20:27.960> customers 00:20:28.310 --> 00:20:28.320 align:start position:0% separate address and the customers 00:20:28.320 --> 00:20:30.049 align:start position:0% separate address and the customers wouldn't<00:20:28.559> necessarily<00:20:29.039> need<00:20:29.280> to<00:20:29.400> like<00:20:29.820> they 00:20:30.049 --> 00:20:30.059 align:start position:0% wouldn't necessarily need to like they 00:20:30.059 --> 00:20:31.669 align:start position:0% wouldn't necessarily need to like they don't<00:20:30.299> need<00:20:30.480> to<00:20:30.600> peek<00:20:30.900> into<00:20:31.080> my<00:20:31.320> bank<00:20:31.500> account 00:20:31.669 --> 00:20:31.679 align:start position:0% don't need to peek into my bank account 00:20:31.679 --> 00:20:33.590 align:start position:0% don't need to peek into my bank account or<00:20:32.280> my<00:20:32.460> equivalent<00:20:32.820> of<00:20:33.000> bank<00:20:33.120> account<00:20:33.240> and<00:20:33.480> see 00:20:33.590 --> 00:20:33.600 align:start position:0% or my equivalent of bank account and see 00:20:33.600 --> 00:20:36.409 align:start position:0% or my equivalent of bank account and see like<00:20:33.780> how<00:20:33.960> much<00:20:34.140> I'm<00:20:34.740> making<00:20:34.980> and<00:20:35.580> what<00:20:36.179> is<00:20:36.299> the 00:20:36.409 --> 00:20:36.419 align:start position:0% like how much I'm making and what is the 00:20:36.419 --> 00:20:37.970 align:start position:0% like how much I'm making and what is the balance<00:20:36.720> there<00:20:36.960> that's 00:20:37.970 --> 00:20:37.980 align:start position:0% balance there that's 00:20:37.980 --> 00:20:40.430 align:start position:0% balance there that's like<00:20:38.460> we're<00:20:38.760> we're<00:20:39.120> doing<00:20:39.419> that 00:20:40.430 --> 00:20:40.440 align:start position:0% like we're we're doing that 00:20:40.440 --> 00:20:42.590 align:start position:0% like we're we're doing that um<00:20:40.559> and<00:20:40.919> maybe<00:20:41.520> some<00:20:41.760> of<00:20:41.880> us<00:20:42.000> have<00:20:42.179> gone<00:20:42.360> used 00:20:42.590 --> 00:20:42.600 align:start position:0% um and maybe some of us have gone used 00:20:42.600 --> 00:20:44.630 align:start position:0% um and maybe some of us have gone used to<00:20:42.660> it<00:20:42.780> but<00:20:42.900> it's<00:20:43.020> really<00:20:43.200> weird<00:20:43.500> where<00:20:44.460> you're 00:20:44.630 --> 00:20:44.640 align:start position:0% to it but it's really weird where you're 00:20:44.640 --> 00:20:46.190 align:start position:0% to it but it's really weird where you're working<00:20:44.880> for<00:20:45.059> someone<00:20:45.240> and<00:20:45.600> you<00:20:45.720> you<00:20:45.900> give 00:20:46.190 --> 00:20:46.200 align:start position:0% working for someone and you you give 00:20:46.200 --> 00:20:47.990 align:start position:0% working for someone and you you give them<00:20:46.320> the<00:20:46.559> the<00:20:46.740> like<00:20:47.220> the<00:20:47.400> number<00:20:47.520> of<00:20:47.760> your 00:20:47.990 --> 00:20:48.000 align:start position:0% them the the like the number of your 00:20:48.000 --> 00:20:49.549 align:start position:0% them the the like the number of your bank<00:20:48.299> account<00:20:48.480> and<00:20:48.720> they<00:20:48.960> can<00:20:49.080> see<00:20:49.200> exactly 00:20:49.549 --> 00:20:49.559 align:start position:0% bank account and they can see exactly 00:20:49.559 --> 00:20:52.070 align:start position:0% bank account and they can see exactly what's<00:20:49.740> going<00:20:49.980> on<00:20:50.160> there 00:20:52.070 --> 00:20:52.080 align:start position:0% what's going on there 00:20:52.080 --> 00:20:54.770 align:start position:0% what's going on there um<00:20:52.200> that's<00:20:52.559> that's<00:20:52.860> not<00:20:53.100> very<00:20:53.280> private 00:20:54.770 --> 00:20:54.780 align:start position:0% um that's that's not very private 00:20:54.780 --> 00:20:55.370 align:start position:0% um that's that's not very private um 00:20:55.370 --> 00:20:55.380 align:start position:0% um 00:20:55.380 --> 00:20:58.070 align:start position:0% um and<00:20:56.039> and<00:20:56.340> once<00:20:56.880> we<00:20:56.940> have<00:20:57.120> once<00:20:57.660> we<00:20:57.780> have<00:20:57.900> gas 00:20:58.070 --> 00:20:58.080 align:start position:0% and and once we have once we have gas 00:20:58.080 --> 00:21:00.230 align:start position:0% and and once we have once we have gas abstraction<00:20:58.559> as<00:20:58.860> a<00:20:59.039> built-in<00:20:59.340> feature<00:20:59.760> then 00:21:00.230 --> 00:21:00.240 align:start position:0% abstraction as a built-in feature then 00:21:00.240 --> 00:21:01.549 align:start position:0% abstraction as a built-in feature then we<00:21:00.419> don't<00:21:00.539> have<00:21:00.660> really<00:21:00.840> have<00:21:01.080> to<00:21:01.200> worry<00:21:01.320> about 00:21:01.549 --> 00:21:01.559 align:start position:0% we don't have really have to worry about 00:21:01.559 --> 00:21:02.930 align:start position:0% we don't have really have to worry about that<00:21:01.799> anymore<00:21:01.980> because<00:21:02.460> we<00:21:02.640> could<00:21:02.820> just 00:21:02.930 --> 00:21:02.940 align:start position:0% that anymore because we could just 00:21:02.940 --> 00:21:04.789 align:start position:0% that anymore because we could just generate<00:21:03.299> easily<00:21:03.720> generate<00:21:04.080> new<00:21:04.320> addresses 00:21:04.789 --> 00:21:04.799 align:start position:0% generate easily generate new addresses 00:21:04.799 --> 00:21:07.190 align:start position:0% generate easily generate new addresses for<00:21:05.160> for<00:21:05.880> uh<00:21:06.240> everyone<00:21:06.480> that<00:21:06.780> we<00:21:06.900> interact 00:21:07.190 --> 00:21:07.200 align:start position:0% for for uh everyone that we interact 00:21:07.200 --> 00:21:09.710 align:start position:0% for for uh everyone that we interact with<00:21:07.380> if<00:21:07.740> we<00:21:07.860> wanted<00:21:07.980> to 00:21:09.710 --> 00:21:09.720 align:start position:0% with if we wanted to 00:21:09.720 --> 00:21:11.330 align:start position:0% with if we wanted to there's<00:21:10.140> also<00:21:10.320> an<00:21:10.440> interesting 00:21:11.330 --> 00:21:11.340 align:start position:0% there's also an interesting 00:21:11.340 --> 00:21:14.630 align:start position:0% there's also an interesting um interesting<00:21:12.299> uh<00:21:12.840> use<00:21:13.559> case<00:21:13.799> for<00:21:14.280> enabling 00:21:14.630 --> 00:21:14.640 align:start position:0% um interesting uh use case for enabling 00:21:14.640 --> 00:21:16.730 align:start position:0% um interesting uh use case for enabling cross<00:21:14.940> chain<00:21:15.179> operations<00:21:15.660> there<00:21:16.500> are<00:21:16.620> many 00:21:16.730 --> 00:21:16.740 align:start position:0% cross chain operations there are many 00:21:16.740 --> 00:21:19.010 align:start position:0% cross chain operations there are many ways<00:21:16.980> to<00:21:17.100> do<00:21:17.220> that 00:21:19.010 --> 00:21:19.020 align:start position:0% ways to do that 00:21:19.020 --> 00:21:20.029 align:start position:0% ways to do that um 00:21:20.029 --> 00:21:20.039 align:start position:0% um 00:21:20.039 --> 00:21:22.010 align:start position:0% um and<00:21:20.760> uh 00:21:22.010 --> 00:21:22.020 align:start position:0% and uh 00:21:22.020 --> 00:21:23.450 align:start position:0% and uh yeah<00:21:22.440> that's<00:21:22.679> just<00:21:22.799> something<00:21:22.980> that<00:21:23.100> becomes 00:21:23.450 --> 00:21:23.460 align:start position:0% yeah that's just something that becomes 00:21:23.460 --> 00:21:27.409 align:start position:0% yeah that's just something that becomes a<00:21:23.580> lot<00:21:23.700> easier<00:21:24.000> once<00:21:24.780> once<00:21:25.320> you<00:21:25.580> once<00:21:26.580> you<00:21:26.640> have 00:21:27.409 --> 00:21:27.419 align:start position:0% a lot easier once once you once you have 00:21:27.419 --> 00:21:29.390 align:start position:0% a lot easier once once you once you have um<00:21:27.480> this<00:21:28.320> functionality<00:21:28.740> built<00:21:29.159> into<00:21:29.220> the 00:21:29.390 --> 00:21:29.400 align:start position:0% um this functionality built into the 00:21:29.400 --> 00:21:33.289 align:start position:0% um this functionality built into the protocol 00:21:33.289 --> 00:21:33.299 align:start position:0% 00:21:33.299 --> 00:21:35.510 align:start position:0% um<00:21:33.360> there's<00:21:33.659> also<00:21:34.080> there's<00:21:34.740> also<00:21:35.039> uh<00:21:35.340> some 00:21:35.510 --> 00:21:35.520 align:start position:0% um there's also there's also uh some 00:21:35.520 --> 00:21:37.669 align:start position:0% um there's also there's also uh some savings<00:21:35.940> that<00:21:36.179> you<00:21:36.299> get<00:21:36.419> from<00:21:36.840> from<00:21:37.500> just 00:21:37.669 --> 00:21:37.679 align:start position:0% savings that you get from from just 00:21:37.679 --> 00:21:39.409 align:start position:0% savings that you get from from just being<00:21:37.860> able<00:21:38.039> to<00:21:38.280> batch<00:21:38.460> uh<00:21:39.240> different 00:21:39.409 --> 00:21:39.419 align:start position:0% being able to batch uh different 00:21:39.419 --> 00:21:41.570 align:start position:0% being able to batch uh different transactions<00:21:40.080> together 00:21:41.570 --> 00:21:41.580 align:start position:0% transactions together 00:21:41.580 --> 00:21:43.669 align:start position:0% transactions together um<00:21:41.700> also<00:21:42.059> from<00:21:42.480> being<00:21:42.780> able<00:21:42.960> to<00:21:43.200> guarantee 00:21:43.669 --> 00:21:43.679 align:start position:0% um also from being able to guarantee 00:21:43.679 --> 00:21:45.529 align:start position:0% um also from being able to guarantee that<00:21:44.159> the<00:21:44.400> transactions<00:21:45.000> are<00:21:45.179> going<00:21:45.360> to 00:21:45.529 --> 00:21:45.539 align:start position:0% that the transactions are going to 00:21:45.539 --> 00:21:49.490 align:start position:0% that the transactions are going to execute<00:21:46.020> uh<00:21:46.740> with<00:21:46.980> optimicity<00:21:47.580> so<00:21:48.480> for<00:21:49.320> some 00:21:49.490 --> 00:21:49.500 align:start position:0% execute uh with optimicity so for some 00:21:49.500 --> 00:21:50.450 align:start position:0% execute uh with optimicity so for some things 00:21:50.450 --> 00:21:50.460 align:start position:0% things 00:21:50.460 --> 00:21:52.570 align:start position:0% things it's<00:21:50.940> useful 00:21:52.570 --> 00:21:52.580 align:start position:0% it's useful 00:21:52.580 --> 00:21:56.570 align:start position:0% it's useful if<00:21:53.580> everything<00:21:54.120> happens<00:21:54.419> together<00:21:55.280> and<00:21:56.280> if 00:21:56.570 --> 00:21:56.580 align:start position:0% if everything happens together and if 00:21:56.580 --> 00:21:57.950 align:start position:0% if everything happens together and if everything<00:21:56.820> doesn't<00:21:57.120> happen<00:21:57.360> together<00:21:57.600> then 00:21:57.950 --> 00:21:57.960 align:start position:0% everything doesn't happen together then 00:21:57.960 --> 00:22:00.289 align:start position:0% everything doesn't happen together then you<00:21:58.080> don't<00:21:58.200> want<00:21:58.320> it<00:21:58.440> to<00:21:58.559> happen 00:22:00.289 --> 00:22:00.299 align:start position:0% you don't want it to happen 00:22:00.299 --> 00:22:02.029 align:start position:0% you don't want it to happen um<00:22:00.419> because<00:22:00.600> there<00:22:01.440> you<00:22:01.679> know<00:22:01.740> it<00:22:01.919> wouldn't 00:22:02.029 --> 00:22:02.039 align:start position:0% um because there you know it wouldn't 00:22:02.039 --> 00:22:04.549 align:start position:0% um because there you know it wouldn't make<00:22:02.280> sense<00:22:02.520> uh<00:22:03.120> for<00:22:03.360> the<00:22:03.480> transactions<00:22:04.140> to 00:22:04.549 --> 00:22:04.559 align:start position:0% make sense uh for the transactions to 00:22:04.559 --> 00:22:06.950 align:start position:0% make sense uh for the transactions to execute<00:22:05.039> separately 00:22:06.950 --> 00:22:06.960 align:start position:0% execute separately 00:22:06.960 --> 00:22:07.850 align:start position:0% execute separately um 00:22:07.850 --> 00:22:07.860 align:start position:0% um 00:22:07.860 --> 00:22:11.510 align:start position:0% um and<00:22:08.820> you<00:22:09.600> know<00:22:09.659> whether<00:22:09.840> this<00:22:10.200> happens 00:22:11.510 --> 00:22:11.520 align:start position:0% and you know whether this happens 00:22:11.520 --> 00:22:13.549 align:start position:0% and you know whether this happens um<00:22:12.000> whether<00:22:12.419> this<00:22:12.659> happens<00:22:12.780> like<00:22:13.080> in<00:22:13.200> a<00:22:13.320> gaming 00:22:13.549 --> 00:22:13.559 align:start position:0% um whether this happens like in a gaming 00:22:13.559 --> 00:22:17.029 align:start position:0% um whether this happens like in a gaming environment<00:22:14.059> or<00:22:15.059> you<00:22:15.659> know<00:22:15.780> there<00:22:15.960> are<00:22:16.200> some 00:22:17.029 --> 00:22:17.039 align:start position:0% environment or you know there are some 00:22:17.039 --> 00:22:19.250 align:start position:0% environment or you know there are some you<00:22:17.640> know<00:22:17.700> like<00:22:17.820> Financial<00:22:18.179> scenarios<00:22:18.900> I<00:22:19.140> mean 00:22:19.250 --> 00:22:19.260 align:start position:0% you know like Financial scenarios I mean 00:22:19.260 --> 00:22:20.870 align:start position:0% you know like Financial scenarios I mean imagine<00:22:19.440> the<00:22:19.980> simplest<00:22:20.280> one<00:22:20.400> would<00:22:20.640> be<00:22:20.700> you 00:22:20.870 --> 00:22:20.880 align:start position:0% imagine the simplest one would be you 00:22:20.880 --> 00:22:22.850 align:start position:0% imagine the simplest one would be you have<00:22:21.059> to<00:22:21.179> you<00:22:21.659> have<00:22:21.840> to<00:22:21.960> approve<00:22:22.320> you<00:22:22.500> have<00:22:22.679> to 00:22:22.850 --> 00:22:22.860 align:start position:0% have to you have to approve you have to 00:22:22.860 --> 00:22:25.310 align:start position:0% have to you have to approve you have to give<00:22:23.460> some<00:22:23.760> authorization<00:22:24.299> to<00:22:24.659> a<00:22:24.780> contract<00:22:25.080> to 00:22:25.310 --> 00:22:25.320 align:start position:0% give some authorization to a contract to 00:22:25.320 --> 00:22:28.430 align:start position:0% give some authorization to a contract to perform<00:22:25.500> an<00:22:25.799> action<00:22:26.039> on<00:22:26.220> your<00:22:26.340> behalf 00:22:28.430 --> 00:22:28.440 align:start position:0% perform an action on your behalf 00:22:28.440 --> 00:22:30.649 align:start position:0% perform an action on your behalf um<00:22:28.679> and<00:22:29.100> then<00:22:29.220> then<00:22:29.580> you<00:22:29.760> want<00:22:29.940> to<00:22:30.059> perform<00:22:30.179> you 00:22:30.649 --> 00:22:30.659 align:start position:0% um and then then you want to perform you 00:22:30.659 --> 00:22:31.789 align:start position:0% um and then then you want to perform you want<00:22:30.780> to<00:22:30.900> give<00:22:30.960> them<00:22:31.140> like<00:22:31.380> you<00:22:31.559> know<00:22:31.679> another 00:22:31.789 --> 00:22:31.799 align:start position:0% want to give them like you know another 00:22:31.799 --> 00:22:33.110 align:start position:0% want to give them like you know another transaction<00:22:32.220> to<00:22:32.460> actually<00:22:32.580> perform<00:22:32.880> the 00:22:33.110 --> 00:22:33.120 align:start position:0% transaction to actually perform the 00:22:33.120 --> 00:22:35.750 align:start position:0% transaction to actually perform the transaction<00:22:33.740> and<00:22:34.740> those<00:22:35.100> both<00:22:35.400> need<00:22:35.580> to 00:22:35.750 --> 00:22:35.760 align:start position:0% transaction and those both need to 00:22:35.760 --> 00:22:38.210 align:start position:0% transaction and those both need to execute<00:22:36.120> together 00:22:38.210 --> 00:22:38.220 align:start position:0% execute together 00:22:38.220 --> 00:22:42.710 align:start position:0% execute together otherwise<00:22:39.000> like<00:22:39.659> you<00:22:39.960> just<00:22:40.140> wasted<00:22:40.500> gas 00:22:42.710 --> 00:22:42.720 align:start position:0% 00:22:42.720 --> 00:22:44.390 align:start position:0% um<00:22:42.780> and<00:22:43.260> there<00:22:43.440> is 00:22:44.390 --> 00:22:44.400 align:start position:0% um and there is 00:22:44.400 --> 00:22:46.130 align:start position:0% um and there is there<00:22:45.000> there's 00:22:46.130 --> 00:22:46.140 align:start position:0% there there's 00:22:46.140 --> 00:22:48.289 align:start position:0% there there's um<00:22:46.159> there's<00:22:47.159> a<00:22:47.280> sort<00:22:47.520> of<00:22:47.640> General<00:22:47.820> use<00:22:48.120> case 00:22:48.289 --> 00:22:48.299 align:start position:0% um there's a sort of General use case 00:22:48.299 --> 00:22:50.930 align:start position:0% um there's a sort of General use case that's<00:22:48.600> interesting<00:22:49.020> where 00:22:50.930 --> 00:22:50.940 align:start position:0% that's interesting where 00:22:50.940 --> 00:22:53.690 align:start position:0% that's interesting where um<00:22:51.059> you<00:22:51.419> can<00:22:51.539> actually<00:22:51.840> uh<00:22:52.320> Implement<00:22:52.860> these 00:22:53.690 --> 00:22:53.700 align:start position:0% um you can actually uh Implement these 00:22:53.700 --> 00:22:54.350 align:start position:0% um you can actually uh Implement these um 00:22:54.350 --> 00:22:54.360 align:start position:0% um 00:22:54.360 --> 00:22:57.289 align:start position:0% um uh<00:22:54.840> time<00:22:55.020> time<00:22:55.080> delay<00:22:55.679> uh<00:22:56.520> flow<00:22:56.880> so<00:22:57.000> for 00:22:57.289 --> 00:22:57.299 align:start position:0% uh time time delay uh flow so for 00:22:57.299 --> 00:23:00.169 align:start position:0% uh time time delay uh flow so for example<00:22:57.480> let's<00:22:57.659> say<00:22:57.780> I<00:22:57.960> want<00:22:58.140> I<00:22:59.039> want<00:22:59.220> to<00:22:59.340> be 00:23:00.169 --> 00:23:00.179 align:start position:0% example let's say I want I want to be 00:23:00.179 --> 00:23:04.310 align:start position:0% example let's say I want I want to be um<00:23:00.720> I<00:23:00.720> want<00:23:01.080> to<00:23:01.260> be<00:23:01.440> uh<00:23:01.980> uh<00:23:03.299> selling<00:23:03.960> my<00:23:04.080> eth 00:23:04.310 --> 00:23:04.320 align:start position:0% um I want to be uh uh selling my eth 00:23:04.320 --> 00:23:07.610 align:start position:0% um I want to be uh uh selling my eth when<00:23:04.500> it<00:23:04.620> hits<00:23:04.740> uh<00:23:05.039> 5000<00:23:05.700> but<00:23:06.240> I<00:23:06.360> don't<00:23:06.480> wanna 00:23:07.610 --> 00:23:07.620 align:start position:0% when it hits uh 5000 but I don't wanna 00:23:07.620 --> 00:23:09.770 align:start position:0% when it hits uh 5000 but I don't wanna I<00:23:08.039> don't<00:23:08.100> know<00:23:08.520> when<00:23:09.059> that's<00:23:09.299> going<00:23:09.480> to<00:23:09.600> happen 00:23:09.770 --> 00:23:09.780 align:start position:0% I don't know when that's going to happen 00:23:09.780 --> 00:23:11.149 align:start position:0% I don't know when that's going to happen I<00:23:10.140> don't<00:23:10.320> want<00:23:10.440> to<00:23:10.559> sit<00:23:10.620> in<00:23:10.799> front<00:23:10.919> of<00:23:11.039> my 00:23:11.149 --> 00:23:11.159 align:start position:0% I don't want to sit in front of my 00:23:11.159 --> 00:23:12.590 align:start position:0% I don't want to sit in front of my computer 00:23:12.590 --> 00:23:12.600 align:start position:0% computer 00:23:12.600 --> 00:23:14.510 align:start position:0% computer um so<00:23:13.020> it<00:23:13.440> would<00:23:13.559> be<00:23:13.679> possible<00:23:13.980> for<00:23:14.220> me<00:23:14.340> to 00:23:14.510 --> 00:23:14.520 align:start position:0% um so it would be possible for me to 00:23:14.520 --> 00:23:17.029 align:start position:0% um so it would be possible for me to just<00:23:15.120> pre-create<00:23:15.840> the<00:23:15.960> transaction<00:23:16.320> but<00:23:16.860> make 00:23:17.029 --> 00:23:17.039 align:start position:0% just pre-create the transaction but make 00:23:17.039 --> 00:23:19.430 align:start position:0% just pre-create the transaction but make it<00:23:17.220> conditional<00:23:17.760> on<00:23:18.120> certain<00:23:18.480> certain<00:23:19.260> things 00:23:19.430 --> 00:23:19.440 align:start position:0% it conditional on certain certain things 00:23:19.440 --> 00:23:21.289 align:start position:0% it conditional on certain certain things happening<00:23:19.799> like<00:23:20.100> okay<00:23:20.340> only<00:23:20.700> if<00:23:20.940> the<00:23:21.059> price<00:23:21.179> of 00:23:21.289 --> 00:23:21.299 align:start position:0% happening like okay only if the price of 00:23:21.299 --> 00:23:23.870 align:start position:0% happening like okay only if the price of eighth<00:23:21.600> is<00:23:21.720> 5000<00:23:22.200> or<00:23:22.440> only<00:23:23.100> after<00:23:23.340> this<00:23:23.640> time 00:23:23.870 --> 00:23:23.880 align:start position:0% eighth is 5000 or only after this time 00:23:23.880 --> 00:23:27.890 align:start position:0% eighth is 5000 or only after this time or<00:23:24.360> whatever<00:23:24.600> the<00:23:24.900> condition<00:23:25.020> is<00:23:25.380> and 00:23:27.890 --> 00:23:27.900 align:start position:0% or whatever the condition is and 00:23:27.900 --> 00:23:29.870 align:start position:0% or whatever the condition is and um<00:23:28.020> so<00:23:28.679> my<00:23:28.919> wallet 00:23:29.870 --> 00:23:29.880 align:start position:0% um so my wallet 00:23:29.880 --> 00:23:32.990 align:start position:0% um so my wallet would<00:23:30.480> agree<00:23:30.840> to<00:23:31.559> execute<00:23:32.280> and<00:23:32.580> pay<00:23:32.700> for<00:23:32.880> the 00:23:32.990 --> 00:23:33.000 align:start position:0% would agree to execute and pay for the 00:23:33.000 --> 00:23:34.430 align:start position:0% would agree to execute and pay for the gas<00:23:33.120> for<00:23:33.299> that<00:23:33.480> transaction<00:23:33.840> and<00:23:34.080> also<00:23:34.320> maybe 00:23:34.430 --> 00:23:34.440 align:start position:0% gas for that transaction and also maybe 00:23:34.440 --> 00:23:36.470 align:start position:0% gas for that transaction and also maybe a<00:23:34.620> transaction<00:23:34.919> fee<00:23:35.340> and<00:23:35.820> you<00:23:35.940> would<00:23:36.120> put<00:23:36.299> that 00:23:36.470 --> 00:23:36.480 align:start position:0% a transaction fee and you would put that 00:23:36.480 --> 00:23:40.909 align:start position:0% a transaction fee and you would put that into<00:23:36.900> a<00:23:37.260> registry<00:23:38.120> and<00:23:39.120> or<00:23:39.539> the<00:23:39.840> registry<00:23:40.320> of 00:23:40.909 --> 00:23:40.919 align:start position:0% into a registry and or the registry of 00:23:40.919 --> 00:23:44.289 align:start position:0% into a registry and or the registry of uh<00:23:41.760> future<00:23:42.240> time<00:23:42.659> delayed<00:23:43.140> or<00:23:43.380> event<00:23:43.620> driven 00:23:44.289 --> 00:23:44.299 align:start position:0% uh future time delayed or event driven 00:23:44.299 --> 00:23:47.390 align:start position:0% uh future time delayed or event driven transactions<00:23:45.299> and<00:23:45.960> Searchers<00:23:46.500> they<00:23:47.100> would<00:23:47.220> be 00:23:47.390 --> 00:23:47.400 align:start position:0% transactions and Searchers they would be 00:23:47.400 --> 00:23:51.110 align:start position:0% transactions and Searchers they would be able<00:23:47.520> to<00:23:47.640> monitor<00:23:48.000> this<00:23:48.240> registry<00:23:48.720> and 00:23:51.110 --> 00:23:51.120 align:start position:0% able to monitor this registry and 00:23:51.120 --> 00:23:53.690 align:start position:0% able to monitor this registry and see<00:23:51.840> oh<00:23:52.080> like<00:23:52.320> these<00:23:52.559> are<00:23:52.679> transactions<00:23:53.340> that 00:23:53.690 --> 00:23:53.700 align:start position:0% see oh like these are transactions that 00:23:53.700 --> 00:23:55.430 align:start position:0% see oh like these are transactions that their<00:23:54.120> conditions<00:23:54.539> have<00:23:54.720> just<00:23:54.900> been<00:23:55.080> been<00:23:55.260> met 00:23:55.430 --> 00:23:55.440 align:start position:0% their conditions have just been been met 00:23:55.440 --> 00:23:57.590 align:start position:0% their conditions have just been been met so<00:23:55.679> they<00:23:55.860> can<00:23:55.980> compete<00:23:56.340> on<00:23:56.580> executing<00:23:57.120> it<00:23:57.360> for 00:23:57.590 --> 00:23:57.600 align:start position:0% so they can compete on executing it for 00:23:57.600 --> 00:23:58.970 align:start position:0% so they can compete on executing it for you 00:23:58.970 --> 00:23:58.980 align:start position:0% you 00:23:58.980 --> 00:24:01.010 align:start position:0% you um<00:23:59.100> and<00:23:59.280> that<00:23:59.340> opens<00:23:59.820> up<00:23:59.880> it<00:24:00.000> opens<00:24:00.360> up<00:24:00.480> a<00:24:00.720> whole 00:24:01.010 --> 00:24:01.020 align:start position:0% um and that opens up it opens up a whole 00:24:01.020 --> 00:24:05.090 align:start position:0% um and that opens up it opens up a whole range<00:24:01.380> of<00:24:01.620> of<00:24:02.400> uh<00:24:02.640> interesting<00:24:03.600> um<00:24:03.720> use<00:24:04.260> cases 00:24:05.090 --> 00:24:05.100 align:start position:0% range of of uh interesting um use cases 00:24:05.100 --> 00:24:07.430 align:start position:0% range of of uh interesting um use cases because<00:24:05.580> now<00:24:06.360> you<00:24:06.720> know<00:24:06.840> it<00:24:06.900> doesn't<00:24:07.080> have<00:24:07.320> to 00:24:07.430 --> 00:24:07.440 align:start position:0% because now you know it doesn't have to 00:24:07.440 --> 00:24:09.230 align:start position:0% because now you know it doesn't have to be<00:24:07.559> you<00:24:07.740> that<00:24:08.039> pulls<00:24:08.580> the<00:24:08.640> trigger<00:24:08.940> at<00:24:09.059> the 00:24:09.230 --> 00:24:09.240 align:start position:0% be you that pulls the trigger at the 00:24:09.240 --> 00:24:11.450 align:start position:0% be you that pulls the trigger at the exact<00:24:09.419> moment<00:24:09.720> the<00:24:09.900> conditions<00:24:10.260> are<00:24:10.380> met<00:24:10.620> and 00:24:11.450 --> 00:24:11.460 align:start position:0% exact moment the conditions are met and 00:24:11.460 --> 00:24:13.909 align:start position:0% exact moment the conditions are met and if<00:24:11.940> the<00:24:12.179> conditions<00:24:12.539> are<00:24:12.659> met 00:24:13.909 --> 00:24:13.919 align:start position:0% if the conditions are met 00:24:13.919 --> 00:24:15.890 align:start position:0% if the conditions are met um<00:24:14.039> the<00:24:14.280> transaction<00:24:14.700> will<00:24:15.120> be<00:24:15.299> executed<00:24:15.720> for 00:24:15.890 --> 00:24:15.900 align:start position:0% um the transaction will be executed for 00:24:15.900 --> 00:24:18.110 align:start position:0% um the transaction will be executed for you<00:24:15.960> by<00:24:16.140> Searchers<00:24:16.620> and<00:24:17.520> it<00:24:17.700> could<00:24:17.820> be<00:24:17.940> time 00:24:18.110 --> 00:24:18.120 align:start position:0% you by Searchers and it could be time 00:24:18.120 --> 00:24:20.149 align:start position:0% you by Searchers and it could be time delayed<00:24:18.659> it<00:24:18.960> could<00:24:19.080> be<00:24:19.200> based<00:24:19.559> on<00:24:19.679> essentially 00:24:20.149 --> 00:24:20.159 align:start position:0% delayed it could be based on essentially 00:24:20.159 --> 00:24:22.909 align:start position:0% delayed it could be based on essentially like<00:24:20.280> whatever<00:24:21.020> uh<00:24:22.020> whatever<00:24:22.260> the<00:24:22.500> conditions 00:24:22.909 --> 00:24:22.919 align:start position:0% like whatever uh whatever the conditions 00:24:22.919 --> 00:24:25.490 align:start position:0% like whatever uh whatever the conditions make<00:24:23.220> sense 00:24:25.490 --> 00:24:25.500 align:start position:0% make sense 00:24:25.500 --> 00:24:27.529 align:start position:0% make sense um maybe<00:24:25.740> another<00:24:25.980> example<00:24:26.400> would<00:24:26.640> be<00:24:26.880> you 00:24:27.529 --> 00:24:27.539 align:start position:0% um maybe another example would be you 00:24:27.539 --> 00:24:29.690 align:start position:0% um maybe another example would be you know<00:24:27.600> there's<00:24:27.780> an<00:24:27.960> nft<00:24:28.200> series<00:24:28.559> and<00:24:29.280> you<00:24:29.520> have 00:24:29.690 --> 00:24:29.700 align:start position:0% know there's an nft series and you have 00:24:29.700 --> 00:24:32.870 align:start position:0% know there's an nft series and you have to<00:24:29.820> be<00:24:30.000> or<00:24:30.960> I<00:24:31.380> don't<00:24:31.559> like<00:24:31.740> you 00:24:32.870 --> 00:24:32.880 align:start position:0% to be or I don't like you 00:24:32.880 --> 00:24:34.490 align:start position:0% to be or I don't like you um<00:24:32.940> an<00:24:33.240> event<00:24:33.419> that<00:24:33.720> you<00:24:33.840> have<00:24:33.900> to<00:24:34.020> subscribe 00:24:34.490 --> 00:24:34.500 align:start position:0% um an event that you have to subscribe 00:24:34.500 --> 00:24:38.570 align:start position:0% um an event that you have to subscribe to<00:24:35.220> for<00:24:35.520> in<00:24:35.940> a<00:24:36.059> certain<00:24:36.179> time<00:24:36.419> window 00:24:38.570 --> 00:24:38.580 align:start position:0% to for in a certain time window 00:24:38.580 --> 00:24:41.510 align:start position:0% to for in a certain time window um 00:24:41.510 --> 00:24:41.520 align:start position:0% 00:24:41.520 --> 00:24:46.070 align:start position:0% okay<00:24:41.940> so<00:24:42.240> a<00:24:42.360> little<00:24:42.480> bit<00:24:42.600> about<00:24:42.780> erc4337 00:24:46.070 --> 00:24:46.080 align:start position:0% 00:24:46.080 --> 00:24:49.490 align:start position:0% which<00:24:46.860> is<00:24:47.100> so<00:24:48.240> um<00:24:48.299> this<00:24:48.539> is<00:24:48.600> the<00:24:48.780> standard<00:24:49.140> that 00:24:49.490 --> 00:24:49.500 align:start position:0% which is so um this is the standard that 00:24:49.500 --> 00:24:52.310 align:start position:0% which is so um this is the standard that we<00:24:50.280> have<00:24:50.460> been<00:24:51.000> um<00:24:51.000> working<00:24:51.299> on 00:24:52.310 --> 00:24:52.320 align:start position:0% we have been um working on 00:24:52.320 --> 00:24:55.070 align:start position:0% we have been um working on and<00:24:53.159> uh 00:24:55.070 --> 00:24:55.080 align:start position:0% and uh 00:24:55.080 --> 00:24:57.289 align:start position:0% and uh Paul<00:24:55.620> here<00:24:55.919> is<00:24:56.100> is<00:24:56.340> the<00:24:56.520> guy<00:24:56.640> who<00:24:56.760> implemented 00:24:57.289 --> 00:24:57.299 align:start position:0% Paul here is is the guy who implemented 00:24:57.299 --> 00:25:00.590 align:start position:0% Paul here is is the guy who implemented the<00:24:57.600> the<00:24:58.020> contracts 00:25:00.590 --> 00:25:00.600 align:start position:0% the the contracts 00:25:00.600 --> 00:25:02.090 align:start position:0% the the contracts um<00:25:00.720> so 00:25:02.090 --> 00:25:02.100 align:start position:0% um so 00:25:02.100 --> 00:25:03.770 align:start position:0% um so yeah<00:25:02.520> please<00:25:02.760> if<00:25:03.000> there<00:25:03.240> are<00:25:03.360> any<00:25:03.419> technical 00:25:03.770 --> 00:25:03.780 align:start position:0% yeah please if there are any technical 00:25:03.780 --> 00:25:07.250 align:start position:0% yeah please if there are any technical mistakes<00:25:04.260> correct<00:25:04.919> me 00:25:07.250 --> 00:25:07.260 align:start position:0% 00:25:07.260 --> 00:25:09.529 align:start position:0% okay 00:25:09.529 --> 00:25:09.539 align:start position:0% okay 00:25:09.539 --> 00:25:12.289 align:start position:0% okay so<00:25:10.020> this<00:25:10.200> is<00:25:10.260> the<00:25:10.500> first<00:25:10.620> step 00:25:12.289 --> 00:25:12.299 align:start position:0% so this is the first step 00:25:12.299 --> 00:25:14.570 align:start position:0% so this is the first step um<00:25:12.419> towards<00:25:13.080> protocol<00:25:13.679> level<00:25:13.980> account<00:25:14.340> of 00:25:14.570 --> 00:25:14.580 align:start position:0% um towards protocol level account of 00:25:14.580 --> 00:25:16.070 align:start position:0% um towards protocol level account of distraction<00:25:14.820> the<00:25:15.120> nice<00:25:15.240> thing<00:25:15.419> about<00:25:15.659> our 00:25:16.070 --> 00:25:16.080 align:start position:0% distraction the nice thing about our 00:25:16.080 --> 00:25:19.010 align:start position:0% distraction the nice thing about our approach<00:25:16.500> is<00:25:17.400> that<00:25:17.580> it<00:25:17.760> doesn't<00:25:17.880> require<00:25:18.240> any 00:25:19.010 --> 00:25:19.020 align:start position:0% approach is that it doesn't require any 00:25:19.020 --> 00:25:21.649 align:start position:0% approach is that it doesn't require any change<00:25:19.500> to<00:25:19.860> the<00:25:20.039> rules<00:25:20.220> of<00:25:20.400> consensus<00:25:20.940> so<00:25:21.539> we 00:25:21.649 --> 00:25:21.659 align:start position:0% change to the rules of consensus so we 00:25:21.659 --> 00:25:24.830 align:start position:0% change to the rules of consensus so we can<00:25:21.840> kind<00:25:22.020> of<00:25:22.080> experiment<00:25:22.940> uh<00:25:23.940> for<00:25:24.179> free<00:25:24.419> and 00:25:24.830 --> 00:25:24.840 align:start position:0% can kind of experiment uh for free and 00:25:24.840 --> 00:25:27.289 align:start position:0% can kind of experiment uh for free and we<00:25:24.960> don't<00:25:25.080> have<00:25:25.260> to<00:25:25.320> solve<00:25:25.620> governance<00:25:26.299> in 00:25:27.289 --> 00:25:27.299 align:start position:0% we don't have to solve governance in 00:25:27.299 --> 00:25:28.730 align:start position:0% we don't have to solve governance in advance 00:25:28.730 --> 00:25:28.740 align:start position:0% advance 00:25:28.740 --> 00:25:31.190 align:start position:0% advance um the<00:25:28.919> way<00:25:29.039> we're<00:25:29.159> doing<00:25:29.340> it<00:25:29.580> is<00:25:30.240> okay<00:25:30.600> we 00:25:31.190 --> 00:25:31.200 align:start position:0% um the way we're doing it is okay we 00:25:31.200 --> 00:25:34.370 align:start position:0% um the way we're doing it is okay we essentially<00:25:31.919> create<00:25:32.220> a<00:25:33.059> mempool<00:25:33.600> new<00:25:34.080> type<00:25:34.200> of 00:25:34.370 --> 00:25:34.380 align:start position:0% essentially create a mempool new type of 00:25:34.380 --> 00:25:38.289 align:start position:0% essentially create a mempool new type of mempool<00:25:35.240> for<00:25:36.240> anyone<00:25:36.539> that<00:25:36.720> wants<00:25:37.080> to 00:25:38.289 --> 00:25:38.299 align:start position:0% mempool for anyone that wants to 00:25:38.299 --> 00:25:42.830 align:start position:0% mempool for anyone that wants to participate<00:25:39.299> in<00:25:39.480> this<00:25:40.100> and<00:25:41.120> uh<00:25:42.120> a<00:25:42.419> single<00:25:42.600> you 00:25:42.830 --> 00:25:42.840 align:start position:0% participate in this and uh a single you 00:25:42.840 --> 00:25:44.390 align:start position:0% participate in this and uh a single you don't<00:25:42.960> you<00:25:43.380> don't<00:25:43.500> need<00:25:43.620> more<00:25:43.860> than<00:25:43.980> a<00:25:44.100> single 00:25:44.390 --> 00:25:44.400 align:start position:0% don't you don't need more than a single 00:25:44.400 --> 00:25:48.529 align:start position:0% don't you don't need more than a single Network<00:25:44.900> this<00:25:45.900> this<00:25:46.200> mempool<00:25:46.860> it's 00:25:48.529 --> 00:25:48.539 align:start position:0% Network this this mempool it's 00:25:48.539 --> 00:25:53.930 align:start position:0% Network this this mempool it's um<00:25:48.980> uh<00:25:49.980> essentially<00:25:50.700> it<00:25:50.940> uh<00:25:51.860> accepts<00:25:52.940> it 00:25:53.930 --> 00:25:53.940 align:start position:0% um uh essentially it uh accepts it 00:25:53.940 --> 00:25:56.390 align:start position:0% um uh essentially it uh accepts it accepts<00:25:54.240> uh<00:25:54.600> something<00:25:55.200> that<00:25:55.559> is<00:25:55.980> essentially 00:25:56.390 --> 00:25:56.400 align:start position:0% accepts uh something that is essentially 00:25:56.400 --> 00:25:57.950 align:start position:0% accepts uh something that is essentially a<00:25:56.640> transaction<00:25:57.000> we're<00:25:57.240> calling<00:25:57.539> it<00:25:57.600> user 00:25:57.950 --> 00:25:57.960 align:start position:0% a transaction we're calling it user 00:25:57.960 --> 00:25:59.930 align:start position:0% a transaction we're calling it user operation<00:25:58.320> but<00:25:58.980> a<00:25:59.100> user<00:25:59.340> operation<00:25:59.700> is 00:25:59.930 --> 00:25:59.940 align:start position:0% operation but a user operation is 00:25:59.940 --> 00:26:02.390 align:start position:0% operation but a user operation is equivalent<00:26:00.299> to<00:26:00.419> a<00:26:00.600> transaction<00:26:01.020> but<00:26:01.919> it's<00:26:02.220> a 00:26:02.390 --> 00:26:02.400 align:start position:0% equivalent to a transaction but it's a 00:26:02.400 --> 00:26:06.169 align:start position:0% equivalent to a transaction but it's a it's<00:26:02.760> a<00:26:02.940> transaction<00:26:03.299> that<00:26:04.260> works<00:26:04.919> with<00:26:05.159> with 00:26:06.169 --> 00:26:06.179 align:start position:0% it's a transaction that works with with 00:26:06.179 --> 00:26:08.990 align:start position:0% it's a transaction that works with with um with<00:26:06.840> these<00:26:07.080> account<00:26:07.200> contracts 00:26:08.990 --> 00:26:09.000 align:start position:0% um with these account contracts 00:26:09.000 --> 00:26:09.710 align:start position:0% um with these account contracts um 00:26:09.710 --> 00:26:09.720 align:start position:0% um 00:26:09.720 --> 00:26:12.950 align:start position:0% um so<00:26:10.140> what<00:26:10.320> that<00:26:10.500> does<00:26:10.679> is<00:26:11.220> it<00:26:11.880> makes<00:26:12.120> a<00:26:12.539> contract 00:26:12.950 --> 00:26:12.960 align:start position:0% so what that does is it makes a contract 00:26:12.960 --> 00:26:16.370 align:start position:0% so what that does is it makes a contract wallets<00:26:13.380> a<00:26:13.620> first-class<00:26:13.980> Citizen<00:26:14.539> and<00:26:15.539> it 00:26:16.370 --> 00:26:16.380 align:start position:0% wallets a first-class Citizen and it 00:26:16.380 --> 00:26:17.690 align:start position:0% wallets a first-class Citizen and it totally<00:26:16.559> does<00:26:16.740> away<00:26:16.919> with<00:26:17.159> the<00:26:17.279> need<00:26:17.460> for 00:26:17.690 --> 00:26:17.700 align:start position:0% totally does away with the need for 00:26:17.700 --> 00:26:19.430 align:start position:0% totally does away with the need for having 00:26:19.430 --> 00:26:19.440 align:start position:0% having 00:26:19.440 --> 00:26:22.430 align:start position:0% having um<00:26:19.500> anyway<00:26:19.799> you<00:26:20.760> don't<00:26:20.820> need<00:26:20.940> a<00:26:21.059> new<00:26:21.240> way<00:26:21.480> to<00:26:22.200> uh 00:26:22.430 --> 00:26:22.440 align:start position:0% um anyway you don't need a new way to uh 00:26:22.440 --> 00:26:23.990 align:start position:0% um anyway you don't need a new way to uh to<00:26:23.159> control 00:26:23.990 --> 00:26:24.000 align:start position:0% to control 00:26:24.000 --> 00:26:26.810 align:start position:0% to control um to<00:26:24.240> control<00:26:24.419> this<00:26:24.720> this<00:26:25.020> account 00:26:26.810 --> 00:26:26.820 align:start position:0% um to control this this account 00:26:26.820 --> 00:26:27.769 align:start position:0% um to control this this account um 00:26:27.769 --> 00:26:27.779 align:start position:0% um 00:26:27.779 --> 00:26:29.269 align:start position:0% um and 00:26:29.269 --> 00:26:29.279 align:start position:0% and 00:26:29.279 --> 00:26:31.490 align:start position:0% and I<00:26:29.640> mean<00:26:29.760> the<00:26:29.880> way<00:26:30.240> the<00:26:30.480> way<00:26:30.659> that<00:26:30.779> works<00:26:31.140> about 00:26:31.490 --> 00:26:31.500 align:start position:0% I mean the way the way that works about 00:26:31.500 --> 00:26:34.610 align:start position:0% I mean the way the way that works about maybe<00:26:32.039> a<00:26:32.279> little<00:26:32.460> bit<00:26:32.640> about<00:26:32.760> how<00:26:33.000> that<00:26:33.120> works 00:26:34.610 --> 00:26:34.620 align:start position:0% maybe a little bit about how that works 00:26:34.620 --> 00:26:35.269 align:start position:0% maybe a little bit about how that works um 00:26:35.269 --> 00:26:35.279 align:start position:0% um 00:26:35.279 --> 00:26:38.149 align:start position:0% um you<00:26:35.940> have<00:26:36.120> it's<00:26:36.539> kind<00:26:36.840> of<00:26:36.900> similar<00:26:37.200> to<00:26:37.320> how<00:26:38.100> um 00:26:38.149 --> 00:26:38.159 align:start position:0% you have it's kind of similar to how um 00:26:38.159 --> 00:26:41.390 align:start position:0% you have it's kind of similar to how um uh<00:26:39.000> you<00:26:39.299> know<00:26:39.360> flashbots<00:26:39.900> Mev<00:26:40.500> private 00:26:41.390 --> 00:26:41.400 align:start position:0% uh you know flashbots Mev private 00:26:41.400 --> 00:26:44.149 align:start position:0% uh you know flashbots Mev private mempools<00:26:42.000> like<00:26:42.240> the<00:26:42.419> principal<00:26:42.779> behind<00:26:43.080> it<00:26:43.260> is 00:26:44.149 --> 00:26:44.159 align:start position:0% mempools like the principal behind it is 00:26:44.159 --> 00:26:46.310 align:start position:0% mempools like the principal behind it is you<00:26:44.760> can<00:26:44.820> have<00:26:45.000> a<00:26:45.120> mempool 00:26:46.310 --> 00:26:46.320 align:start position:0% you can have a mempool 00:26:46.320 --> 00:26:50.149 align:start position:0% you can have a mempool where<00:26:47.179> bundlers<00:26:48.200> they<00:26:49.200> are<00:26:49.500> provided<00:26:49.980> an 00:26:50.149 --> 00:26:50.159 align:start position:0% where bundlers they are provided an 00:26:50.159 --> 00:26:53.630 align:start position:0% where bundlers they are provided an incentive<00:26:50.779> to<00:26:51.779> submit<00:26:52.080> your<00:26:52.200> transaction 00:26:53.630 --> 00:26:53.640 align:start position:0% incentive to submit your transaction 00:26:53.640 --> 00:26:54.310 align:start position:0% incentive to submit your transaction um 00:26:54.310 --> 00:26:54.320 align:start position:0% um 00:26:54.320 --> 00:26:56.890 align:start position:0% um and 00:26:56.890 --> 00:26:56.900 align:start position:0% and 00:26:56.900 --> 00:27:00.169 align:start position:0% and essentially<00:26:57.980> uh<00:26:58.980> we're<00:26:59.279> just<00:26:59.400> we<00:26:59.640> took<00:27:00.000> that 00:27:00.169 --> 00:27:00.179 align:start position:0% essentially uh we're just we took that 00:27:00.179 --> 00:27:01.730 align:start position:0% essentially uh we're just we took that that<00:27:00.480> idea<00:27:00.779> or<00:27:00.960> originally<00:27:01.440> this<00:27:01.620> was 00:27:01.730 --> 00:27:01.740 align:start position:0% that idea or originally this was 00:27:01.740 --> 00:27:04.130 align:start position:0% that idea or originally this was vitalik's<00:27:02.400> idea<00:27:02.580> and<00:27:03.120> we<00:27:03.299> added<00:27:03.600> the<00:27:03.960> gas 00:27:04.130 --> 00:27:04.140 align:start position:0% vitalik's idea and we added the gas 00:27:04.140 --> 00:27:06.769 align:start position:0% vitalik's idea and we added the gas abstraction<00:27:04.620> part<00:27:04.860> to<00:27:05.100> it<00:27:05.279> to<00:27:05.940> make<00:27:06.059> it<00:27:06.299> a<00:27:06.539> more 00:27:06.769 --> 00:27:06.779 align:start position:0% abstraction part to it to make it a more 00:27:06.779 --> 00:27:10.149 align:start position:0% abstraction part to it to make it a more general<00:27:06.900> purpose<00:27:07.380> and 00:27:10.149 --> 00:27:10.159 align:start position:0% general purpose and 00:27:10.159 --> 00:27:13.190 align:start position:0% general purpose and then<00:27:11.159> the<00:27:11.279> bundlers<00:27:11.700> you<00:27:12.179> know<00:27:12.240> they<00:27:12.539> their 00:27:13.190 --> 00:27:13.200 align:start position:0% then the bundlers you know they their 00:27:13.200 --> 00:27:15.649 align:start position:0% then the bundlers you know they their their<00:27:13.380> job<00:27:13.620> is<00:27:13.860> to<00:27:14.100> just<00:27:14.340> uh<00:27:14.580> take<00:27:15.120> these<00:27:15.360> user 00:27:15.649 --> 00:27:15.659 align:start position:0% their job is to just uh take these user 00:27:15.659 --> 00:27:18.649 align:start position:0% their job is to just uh take these user operations<00:27:16.159> and<00:27:17.159> eventually<00:27:17.580> they<00:27:17.940> they<00:27:18.240> they 00:27:18.649 --> 00:27:18.659 align:start position:0% operations and eventually they they they 00:27:18.659 --> 00:27:20.210 align:start position:0% operations and eventually they they they bundle<00:27:19.200> them<00:27:19.320> together<00:27:19.500> and<00:27:19.740> they<00:27:19.860> submit 00:27:20.210 --> 00:27:20.220 align:start position:0% bundle them together and they submit 00:27:20.220 --> 00:27:21.769 align:start position:0% bundle them together and they submit them 00:27:21.769 --> 00:27:21.779 align:start position:0% them 00:27:21.779 --> 00:27:24.110 align:start position:0% them um<00:27:21.840> as<00:27:22.620> when<00:27:23.159> they're<00:27:23.340> creating<00:27:23.700> when<00:27:24.000> they're 00:27:24.110 --> 00:27:24.120 align:start position:0% um as when they're creating when they're 00:27:24.120 --> 00:27:25.010 align:start position:0% um as when they're creating when they're creating 00:27:25.010 --> 00:27:25.020 align:start position:0% creating 00:27:25.020 --> 00:27:26.330 align:start position:0% creating um 00:27:26.330 --> 00:27:26.340 align:start position:0% um 00:27:26.340 --> 00:27:29.750 align:start position:0% um um<00:27:26.520> uh<00:27:27.120> bundles<00:27:27.659> that<00:27:27.840> that<00:27:27.960> are<00:27:28.140> go<00:27:28.320> to<00:27:28.500> the<00:27:28.760> uh 00:27:29.750 --> 00:27:29.760 align:start position:0% um uh bundles that that are go to the uh 00:27:29.760 --> 00:27:32.810 align:start position:0% um uh bundles that that are go to the uh to<00:27:30.000> actual<00:27:30.299> uh<00:27:30.600> blocks 00:27:32.810 --> 00:27:32.820 align:start position:0% to actual uh blocks 00:27:32.820 --> 00:27:36.350 align:start position:0% to actual uh blocks okay<00:27:33.419> the<00:27:33.900> the<00:27:34.620> um<00:27:34.620> the<00:27:35.580> the<00:27:35.580> other<00:27:35.880> advantage 00:27:36.350 --> 00:27:36.360 align:start position:0% okay the the um the the other advantage 00:27:36.360 --> 00:27:38.649 align:start position:0% okay the the um the the other advantage of<00:27:37.020> doing<00:27:37.320> things<00:27:37.620> this<00:27:37.919> way 00:27:38.649 --> 00:27:38.659 align:start position:0% of doing things this way 00:27:38.659 --> 00:27:42.049 align:start position:0% of doing things this way is<00:27:39.659> that<00:27:40.620> we're<00:27:40.740> separating<00:27:41.159> validation<00:27:41.820> from 00:27:42.049 --> 00:27:42.059 align:start position:0% is that we're separating validation from 00:27:42.059 --> 00:27:43.070 align:start position:0% is that we're separating validation from execution 00:27:43.070 --> 00:27:43.080 align:start position:0% execution 00:27:43.080 --> 00:27:44.930 align:start position:0% execution so 00:27:44.930 --> 00:27:44.940 align:start position:0% so 00:27:44.940 --> 00:27:46.490 align:start position:0% so you<00:27:45.419> can<00:27:45.539> have 00:27:46.490 --> 00:27:46.500 align:start position:0% you can have 00:27:46.500 --> 00:27:47.560 align:start position:0% you can have you<00:27:46.919> can<00:27:47.039> have 00:27:47.560 --> 00:27:47.570 align:start position:0% you can have 00:27:47.570 --> 00:27:47.810 align:start position:0% you can have [Music] 00:27:47.810 --> 00:27:47.820 align:start position:0% [Music] 00:27:47.820 --> 00:27:48.830 align:start position:0% [Music] um 00:27:48.830 --> 00:27:48.840 align:start position:0% um 00:27:48.840 --> 00:27:51.830 align:start position:0% um so<00:27:49.200> so<00:27:49.200> if<00:27:49.559> I'm<00:27:49.679> if<00:27:49.799> I'm<00:27:50.039> a<00:27:50.159> bundler<00:27:50.460> and<00:27:51.240> I<00:27:51.659> am 00:27:51.830 --> 00:27:51.840 align:start position:0% so so if I'm if I'm a bundler and I am 00:27:51.840 --> 00:27:54.710 align:start position:0% so so if I'm if I'm a bundler and I am paying<00:27:52.500> for<00:27:52.799> the<00:27:52.919> gas<00:27:53.039> of<00:27:53.340> your<00:27:53.520> transaction 00:27:54.710 --> 00:27:54.720 align:start position:0% paying for the gas of your transaction 00:27:54.720 --> 00:27:57.350 align:start position:0% paying for the gas of your transaction there's<00:27:55.380> there's<00:27:55.620> some<00:27:55.860> risks<00:27:56.279> involved<00:27:56.760> for 00:27:57.350 --> 00:27:57.360 align:start position:0% there's there's some risks involved for 00:27:57.360 --> 00:27:59.510 align:start position:0% there's there's some risks involved for me<00:27:57.480> because 00:27:59.510 --> 00:27:59.520 align:start position:0% me because 00:27:59.520 --> 00:28:02.269 align:start position:0% me because um<00:27:59.580> you<00:27:59.880> know<00:27:59.940> what<00:28:00.600> happens<00:28:00.779> if<00:28:01.320> the<00:28:01.740> the<00:28:01.740> you 00:28:02.269 --> 00:28:02.279 align:start position:0% um you know what happens if the the you 00:28:02.279 --> 00:28:03.529 align:start position:0% um you know what happens if the the you know<00:28:02.340> like<00:28:02.580> you<00:28:02.880> know<00:28:03.000> if<00:28:03.059> you<00:28:03.120> don't<00:28:03.240> pay<00:28:03.419> me 00:28:03.529 --> 00:28:03.539 align:start position:0% know like you know if you don't pay me 00:28:03.539 --> 00:28:05.090 align:start position:0% know like you know if you don't pay me what<00:28:03.720> happens<00:28:03.900> if<00:28:04.140> I<00:28:04.320> execute<00:28:04.679> a<00:28:04.860> transaction 00:28:05.090 --> 00:28:05.100 align:start position:0% what happens if I execute a transaction 00:28:05.100 --> 00:28:07.490 align:start position:0% what happens if I execute a transaction on<00:28:05.400> chain<00:28:05.580> it<00:28:05.880> turns<00:28:06.059> out<00:28:06.179> that<00:28:06.360> it 00:28:07.490 --> 00:28:07.500 align:start position:0% on chain it turns out that it 00:28:07.500 --> 00:28:10.310 align:start position:0% on chain it turns out that it um<00:28:07.620> and<00:28:07.860> it<00:28:08.100> ends<00:28:08.460> up<00:28:08.580> uh 00:28:10.310 --> 00:28:10.320 align:start position:0% um and it ends up uh 00:28:10.320 --> 00:28:14.269 align:start position:0% um and it ends up uh um<00:28:10.500> you<00:28:10.799> know<00:28:11.400> um<00:28:12.000> ends<00:28:12.779> up<00:28:12.900> uh<00:28:13.380> well<00:28:13.980> at<00:28:14.159> the 00:28:14.269 --> 00:28:14.279 align:start position:0% um you know um ends up uh well at the 00:28:14.279 --> 00:28:15.890 align:start position:0% um you know um ends up uh well at the very<00:28:14.400> least<00:28:14.580> you<00:28:14.760> expect<00:28:14.940> to<00:28:15.179> be<00:28:15.299> repaid<00:28:15.600> in 00:28:15.890 --> 00:28:15.900 align:start position:0% very least you expect to be repaid in 00:28:15.900 --> 00:28:18.409 align:start position:0% very least you expect to be repaid in gas<00:28:16.080> because<00:28:17.039> otherwise 00:28:18.409 --> 00:28:18.419 align:start position:0% gas because otherwise 00:28:18.419 --> 00:28:19.549 align:start position:0% gas because otherwise um you<00:28:18.659> know<00:28:18.720> why<00:28:18.900> why<00:28:19.140> would<00:28:19.320> you 00:28:19.549 --> 00:28:19.559 align:start position:0% um you know why why would you 00:28:19.559 --> 00:28:22.010 align:start position:0% um you know why why would you participate<00:28:20.340> in<00:28:20.520> the<00:28:20.640> scheme 00:28:22.010 --> 00:28:22.020 align:start position:0% participate in the scheme 00:28:22.020 --> 00:28:25.789 align:start position:0% participate in the scheme um<00:28:22.140> so<00:28:22.919> to<00:28:23.340> make<00:28:23.520> it<00:28:24.120> make<00:28:24.539> it<00:28:24.720> very<00:28:24.900> safe 00:28:25.789 --> 00:28:25.799 align:start position:0% um so to make it make it very safe 00:28:25.799 --> 00:28:28.909 align:start position:0% um so to make it make it very safe for<00:28:26.159> bundlers<00:28:26.640> to<00:28:27.299> participate<00:28:27.900> what<00:28:28.679> we've 00:28:28.909 --> 00:28:28.919 align:start position:0% for bundlers to participate what we've 00:28:28.919 --> 00:28:31.490 align:start position:0% for bundlers to participate what we've done<00:28:29.100> is<00:28:29.400> we've<00:28:29.880> provided 00:28:31.490 --> 00:28:31.500 align:start position:0% done is we've provided 00:28:31.500 --> 00:28:33.409 align:start position:0% done is we've provided um<00:28:31.559> a<00:28:31.679> contract<00:28:31.980> level<00:28:32.159> guarantee 00:28:33.409 --> 00:28:33.419 align:start position:0% um a contract level guarantee 00:28:33.419 --> 00:28:36.610 align:start position:0% um a contract level guarantee that<00:28:34.200> you're<00:28:34.500> always<00:28:34.679> going<00:28:35.039> to<00:28:35.220> be<00:28:35.520> paid<00:28:36.059> back 00:28:36.610 --> 00:28:36.620 align:start position:0% that you're always going to be paid back 00:28:36.620 --> 00:28:39.649 align:start position:0% that you're always going to be paid back regardless<00:28:37.620> of<00:28:38.460> of<00:28:38.520> what<00:28:39.059> happens<00:28:39.240> with<00:28:39.480> your 00:28:39.649 --> 00:28:39.659 align:start position:0% regardless of of what happens with your 00:28:39.659 --> 00:28:41.649 align:start position:0% regardless of of what happens with your transaction<00:28:40.020> when<00:28:40.260> it's<00:28:40.380> executed<00:28:40.860> on<00:28:41.039> chain 00:28:41.649 --> 00:28:41.659 align:start position:0% transaction when it's executed on chain 00:28:41.659 --> 00:28:44.810 align:start position:0% transaction when it's executed on chain so<00:28:42.659> we've<00:28:43.320> separated<00:28:43.679> validation<00:28:44.580> from 00:28:44.810 --> 00:28:44.820 align:start position:0% so we've separated validation from 00:28:44.820 --> 00:28:46.970 align:start position:0% so we've separated validation from execution 00:28:46.970 --> 00:28:46.980 align:start position:0% execution 00:28:46.980 --> 00:28:48.649 align:start position:0% execution um<00:28:47.039> and<00:28:47.400> what<00:28:47.700> the<00:28:47.820> bundle<00:28:48.120> needs<00:28:48.360> to<00:28:48.419> do<00:28:48.480> when 00:28:48.649 --> 00:28:48.659 align:start position:0% um and what the bundle needs to do when 00:28:48.659 --> 00:28:50.570 align:start position:0% um and what the bundle needs to do when they<00:28:48.779> accept<00:28:48.900> the<00:28:49.140> transaction<00:28:49.500> they're<00:28:50.340> just 00:28:50.570 --> 00:28:50.580 align:start position:0% they accept the transaction they're just 00:28:50.580 --> 00:28:53.330 align:start position:0% they accept the transaction they're just verifying<00:28:51.240> that<00:28:52.080> they're<00:28:52.860> doing<00:28:53.039> this<00:28:53.159> off 00:28:53.330 --> 00:28:53.340 align:start position:0% verifying that they're doing this off 00:28:53.340 --> 00:28:55.310 align:start position:0% verifying that they're doing this off chain<00:28:53.580> initially<00:28:54.000> just<00:28:54.299> okay<00:28:54.539> if<00:28:54.779> I<00:28:54.960> if<00:28:55.140> I 00:28:55.310 --> 00:28:55.320 align:start position:0% chain initially just okay if I if I 00:28:55.320 --> 00:28:57.409 align:start position:0% chain initially just okay if I if I accept<00:28:55.440> your<00:28:55.679> transaction 00:28:57.409 --> 00:28:57.419 align:start position:0% accept your transaction 00:28:57.419 --> 00:29:00.190 align:start position:0% accept your transaction um<00:28:57.539> and<00:28:58.200> I'm<00:28:58.559> calling<00:28:59.100> this<00:28:59.220> huge<00:28:59.520> function 00:29:00.190 --> 00:29:00.200 align:start position:0% um and I'm calling this huge function 00:29:00.200 --> 00:29:05.570 align:start position:0% um and I'm calling this huge function and<00:29:01.220> uh<00:29:02.220> am<00:29:02.460> I<00:29:02.640> going<00:29:02.820> to<00:29:02.940> be<00:29:03.299> uh<00:29:04.140> paid<00:29:04.440> back<00:29:04.620> for 00:29:05.570 --> 00:29:05.580 align:start position:0% and uh am I going to be uh paid back for 00:29:05.580 --> 00:29:07.010 align:start position:0% and uh am I going to be uh paid back for the<00:29:05.700> guess<00:29:05.880> that's<00:29:06.480> that's<00:29:06.659> all<00:29:06.840> they're 00:29:07.010 --> 00:29:07.020 align:start position:0% the guess that's that's all they're 00:29:07.020 --> 00:29:08.690 align:start position:0% the guess that's that's all they're verifying<00:29:07.559> so<00:29:07.679> it's<00:29:07.860> it's<00:29:08.039> pretty<00:29:08.279> cheap<00:29:08.460> for 00:29:08.690 --> 00:29:08.700 align:start position:0% verifying so it's it's pretty cheap for 00:29:08.700 --> 00:29:09.950 align:start position:0% verifying so it's it's pretty cheap for them<00:29:08.820> to<00:29:08.940> do<00:29:09.059> that 00:29:09.950 --> 00:29:09.960 align:start position:0% them to do that 00:29:09.960 --> 00:29:12.890 align:start position:0% them to do that and 00:29:12.890 --> 00:29:12.900 align:start position:0% and 00:29:12.900 --> 00:29:13.970 align:start position:0% and um<00:29:13.020> later 00:29:13.970 --> 00:29:13.980 align:start position:0% um later 00:29:13.980 --> 00:29:15.409 align:start position:0% um later the<00:29:14.460> totally<00:29:14.760> separately<00:29:15.120> when<00:29:15.360> the 00:29:15.409 --> 00:29:15.419 align:start position:0% the totally separately when the 00:29:15.419 --> 00:29:16.850 align:start position:0% the totally separately when the transaction<00:29:15.779> is<00:29:16.020> submitted<00:29:16.440> and<00:29:16.500> gets 00:29:16.850 --> 00:29:16.860 align:start position:0% transaction is submitted and gets 00:29:16.860 --> 00:29:18.529 align:start position:0% transaction is submitted and gets executed<00:29:17.279> but<00:29:17.520> by<00:29:17.940> then<00:29:18.120> you<00:29:18.240> don't<00:29:18.360> really 00:29:18.529 --> 00:29:18.539 align:start position:0% executed but by then you don't really 00:29:18.539 --> 00:29:19.610 align:start position:0% executed but by then you don't really care 00:29:19.610 --> 00:29:19.620 align:start position:0% care 00:29:19.620 --> 00:29:21.830 align:start position:0% care um<00:29:19.679> as<00:29:19.860> a<00:29:19.980> bundler 00:29:21.830 --> 00:29:21.840 align:start position:0% um as a bundler 00:29:21.840 --> 00:29:23.570 align:start position:0% um as a bundler um<00:29:21.960> even<00:29:22.440> if<00:29:22.559> it<00:29:22.679> reverts<00:29:23.100> it's<00:29:23.220> your<00:29:23.340> problem 00:29:23.570 --> 00:29:23.580 align:start position:0% um even if it reverts it's your problem 00:29:23.580 --> 00:29:24.830 align:start position:0% um even if it reverts it's your problem just<00:29:23.820> like<00:29:23.940> with<00:29:24.120> a<00:29:24.240> normal<00:29:24.360> transaction 00:29:24.830 --> 00:29:24.840 align:start position:0% just like with a normal transaction 00:29:24.840 --> 00:29:27.230 align:start position:0% just like with a normal transaction because<00:29:25.140> you're<00:29:25.320> still<00:29:25.559> going<00:29:25.740> to<00:29:25.919> get<00:29:26.039> paid 00:29:27.230 --> 00:29:27.240 align:start position:0% because you're still going to get paid 00:29:27.240 --> 00:29:29.870 align:start position:0% because you're still going to get paid and<00:29:28.200> the<00:29:28.620> the 00:29:29.870 --> 00:29:29.880 align:start position:0% and the the 00:29:29.880 --> 00:29:31.250 align:start position:0% and the the you<00:29:30.299> know<00:29:30.360> without<00:29:30.480> this<00:29:30.720> it<00:29:30.960> wouldn't<00:29:31.140> really 00:29:31.250 --> 00:29:31.260 align:start position:0% you know without this it wouldn't really 00:29:31.260 --> 00:29:33.409 align:start position:0% you know without this it wouldn't really be<00:29:31.440> possible<00:29:31.799> to 00:29:33.409 --> 00:29:33.419 align:start position:0% be possible to 00:29:33.419 --> 00:29:34.669 align:start position:0% be possible to um 00:29:34.669 --> 00:29:34.679 align:start position:0% um 00:29:34.679 --> 00:29:36.130 align:start position:0% um um<00:29:34.860> the<00:29:35.159> crate 00:29:36.130 --> 00:29:36.140 align:start position:0% um the crate 00:29:36.140 --> 00:29:39.409 align:start position:0% um the crate a<00:29:37.140> permissionless<00:29:37.620> uh<00:29:38.279> pool<00:29:38.460> of<00:29:38.760> bundlers 00:29:39.409 --> 00:29:39.419 align:start position:0% a permissionless uh pool of bundlers 00:29:39.419 --> 00:29:41.510 align:start position:0% a permissionless uh pool of bundlers that<00:29:39.720> are<00:29:39.840> participating<00:29:40.320> in<00:29:40.620> in<00:29:40.919> this<00:29:41.520> um 00:29:41.510 --> 00:29:41.520 align:start position:0% that are participating in in this um 00:29:41.520 --> 00:29:44.029 align:start position:0% that are participating in in this um protocol<00:29:42.000> because<00:29:42.899> the<00:29:43.320> bundlers<00:29:43.679> would<00:29:43.799> have 00:29:44.029 --> 00:29:44.039 align:start position:0% protocol because the bundlers would have 00:29:44.039 --> 00:29:46.250 align:start position:0% protocol because the bundlers would have to<00:29:44.159> trust<00:29:44.399> that<00:29:45.720> um<00:29:45.720> they're<00:29:45.960> not<00:29:46.080> going<00:29:46.200> to 00:29:46.250 --> 00:29:46.260 align:start position:0% to trust that um they're not going to 00:29:46.260 --> 00:29:50.090 align:start position:0% to trust that um they're not going to get<00:29:46.380> cheated 00:29:50.090 --> 00:29:50.100 align:start position:0% 00:29:50.100 --> 00:29:51.409 align:start position:0% just<00:29:50.279> one 00:29:51.409 --> 00:29:51.419 align:start position:0% just one 00:29:51.419 --> 00:29:54.350 align:start position:0% just one we<00:29:51.659> use<00:29:51.840> the<00:29:52.020> term<00:29:52.080> brundler<00:29:52.559> which<00:29:53.460> I<00:29:53.940> node 00:29:54.350 --> 00:29:54.360 align:start position:0% we use the term brundler which I node 00:29:54.360 --> 00:29:56.029 align:start position:0% we use the term brundler which I node Valley<00:29:54.539> debtors<00:29:54.960> just<00:29:55.200> like<00:29:55.380> any<00:29:55.559> node<00:29:55.799> Valley 00:29:56.029 --> 00:29:56.039 align:start position:0% Valley debtors just like any node Valley 00:29:56.039 --> 00:29:58.490 align:start position:0% Valley debtors just like any node Valley that<00:29:56.220> also<00:29:56.880> supports<00:29:57.419> account<00:29:58.020> obstruction 00:29:58.490 --> 00:29:58.500 align:start position:0% that also supports account obstruction 00:29:58.500 --> 00:30:00.830 align:start position:0% that also supports account obstruction and<00:29:59.340> not<00:29:59.460> one<00:29:59.700> of<00:29:59.820> them<00:29:59.880> is<00:30:00.059> enough<00:30:00.179> to<00:30:00.480> run<00:30:00.659> a 00:30:00.830 --> 00:30:00.840 align:start position:0% and not one of them is enough to run a 00:30:00.840 --> 00:30:02.870 align:start position:0% and not one of them is enough to run a network<00:30:00.960> the<00:30:01.620> more<00:30:01.799> they<00:30:02.039> are<00:30:02.220> the<00:30:02.520> notebook 00:30:02.870 --> 00:30:02.880 align:start position:0% network the more they are the notebook 00:30:02.880 --> 00:30:05.870 align:start position:0% network the more they are the notebook is<00:30:03.059> more<00:30:03.620> resilient<00:30:04.620> to<00:30:04.799> a<00:30:05.039> censorship<00:30:05.520> and 00:30:05.870 --> 00:30:05.880 align:start position:0% is more resilient to a censorship and 00:30:05.880 --> 00:30:08.210 align:start position:0% is more resilient to a censorship and other<00:30:06.539> things<00:30:06.720> but<00:30:07.260> the<00:30:07.500> bundler<00:30:07.799> eventually 00:30:08.210 --> 00:30:08.220 align:start position:0% other things but the bundler eventually 00:30:08.220 --> 00:30:10.730 align:start position:0% other things but the bundler eventually and<00:30:08.700> eventually<00:30:09.120> all<00:30:09.600> validators<00:30:10.440> will 00:30:10.730 --> 00:30:10.740 align:start position:0% and eventually all validators will 00:30:10.740 --> 00:30:13.370 align:start position:0% and eventually all validators will hopefully<00:30:11.279> will<00:30:11.700> be<00:30:11.880> also<00:30:12.179> bundles<00:30:12.539> right<00:30:13.080> so 00:30:13.370 --> 00:30:13.380 align:start position:0% hopefully will be also bundles right so 00:30:13.380 --> 00:30:15.470 align:start position:0% hopefully will be also bundles right so the<00:30:13.620> right<00:30:13.980> now<00:30:14.100> we<00:30:14.340> have<00:30:14.520> so<00:30:14.940> exactly<00:30:15.299> you 00:30:15.470 --> 00:30:15.480 align:start position:0% the right now we have so exactly you 00:30:15.480 --> 00:30:16.850 align:start position:0% the right now we have so exactly you don't<00:30:15.600> need<00:30:15.779> a<00:30:15.960> consensus<00:30:16.320> change<00:30:16.559> you<00:30:16.740> don't 00:30:16.850 --> 00:30:16.860 align:start position:0% don't need a consensus change you don't 00:30:16.860 --> 00:30:19.789 align:start position:0% don't need a consensus change you don't need<00:30:16.980> like<00:30:17.279> 51<00:30:17.640> percent 00:30:19.789 --> 00:30:19.799 align:start position:0% need like 51 percent 00:30:19.799 --> 00:30:22.789 align:start position:0% need like 51 percent um<00:30:19.919> of<00:30:20.820> validators<00:30:21.539> participating<00:30:22.440> in<00:30:22.679> this 00:30:22.789 --> 00:30:22.799 align:start position:0% um of validators participating in this 00:30:22.799 --> 00:30:24.889 align:start position:0% um of validators participating in this scheme<00:30:23.159> because<00:30:23.820> ultimately<00:30:24.659> you're 00:30:24.889 --> 00:30:24.899 align:start position:0% scheme because ultimately you're 00:30:24.899 --> 00:30:27.470 align:start position:0% scheme because ultimately you're generating<00:30:25.380> just<00:30:26.100> uh 00:30:27.470 --> 00:30:27.480 align:start position:0% generating just uh 00:30:27.480 --> 00:30:29.930 align:start position:0% generating just uh um<00:30:27.600> Regular<00:30:28.020> legal<00:30:28.440> bucks 00:30:29.930 --> 00:30:29.940 align:start position:0% um Regular legal bucks 00:30:29.940 --> 00:30:32.269 align:start position:0% um Regular legal bucks um<00:30:30.000> and<00:30:30.299> we<00:30:30.480> have<00:30:30.659> we<00:30:30.960> have<00:30:31.080> another<00:30:31.200> mind 00:30:32.269 --> 00:30:32.279 align:start position:0% um and we have we have another mind 00:30:32.279 --> 00:30:34.669 align:start position:0% um and we have we have another mind um<00:30:32.340> as<00:30:32.580> as<00:30:32.820> an<00:30:33.059> implementation<00:30:33.539> that<00:30:34.500> is 00:30:34.669 --> 00:30:34.679 align:start position:0% um as as an implementation that is 00:30:34.679 --> 00:30:35.930 align:start position:0% um as as an implementation that is supporting<00:30:35.039> this 00:30:35.930 --> 00:30:35.940 align:start position:0% supporting this 00:30:35.940 --> 00:30:37.549 align:start position:0% supporting this um<00:30:36.059> the<00:30:36.419> more<00:30:36.539> the<00:30:36.840> more<00:30:37.020> clients<00:30:37.320> support 00:30:37.549 --> 00:30:37.559 align:start position:0% um the more the more clients support 00:30:37.559 --> 00:30:40.610 align:start position:0% um the more the more clients support this<00:30:37.860> the<00:30:38.820> faster<00:30:39.120> your<00:30:39.960> transactions<00:30:40.500> are 00:30:40.610 --> 00:30:40.620 align:start position:0% this the faster your transactions are 00:30:40.620 --> 00:30:43.430 align:start position:0% this the faster your transactions are going<00:30:40.740> to<00:30:40.860> get<00:30:41.279> executed<00:30:41.700> but 00:30:43.430 --> 00:30:43.440 align:start position:0% going to get executed but 00:30:43.440 --> 00:30:45.110 align:start position:0% going to get executed but um<00:30:43.500> yeah 00:30:45.110 --> 00:30:45.120 align:start position:0% um yeah 00:30:45.120 --> 00:30:48.169 align:start position:0% um yeah Okay<00:30:45.539> so 00:30:48.169 --> 00:30:48.179 align:start position:0% Okay so 00:30:48.179 --> 00:30:52.549 align:start position:0% Okay so so<00:30:48.539> with<00:30:49.820> erc4337<00:30:50.820> then<00:30:51.600> you<00:30:51.960> know<00:30:52.080> once<00:30:52.440> we 00:30:52.549 --> 00:30:52.559 align:start position:0% so with erc4337 then you know once we 00:30:52.559 --> 00:30:54.409 align:start position:0% so with erc4337 then you know once we have<00:30:52.679> this<00:30:52.919> scheme 00:30:54.409 --> 00:30:54.419 align:start position:0% have this scheme 00:30:54.419 --> 00:30:57.649 align:start position:0% have this scheme um<00:30:54.539> we<00:30:54.899> can<00:30:55.020> also<00:30:55.260> use<00:30:55.440> it<00:30:55.620> to<00:30:55.860> make<00:30:56.039> uh<00:30:56.940> uh 00:30:57.649 --> 00:30:57.659 align:start position:0% um we can also use it to make uh uh 00:30:57.659 --> 00:30:59.990 align:start position:0% um we can also use it to make uh uh Roll-Ups<00:30:58.320> cheaper<00:30:59.220> because<00:30:59.399> you<00:30:59.700> can<00:30:59.760> batch 00:30:59.990 --> 00:31:00.000 align:start position:0% Roll-Ups cheaper because you can batch 00:31:00.000 --> 00:31:02.510 align:start position:0% Roll-Ups cheaper because you can batch transaction<00:31:00.480> you<00:31:00.960> can<00:31:01.020> aggregate<00:31:01.919> signatures 00:31:02.510 --> 00:31:02.520 align:start position:0% transaction you can aggregate signatures 00:31:02.520 --> 00:31:05.269 align:start position:0% transaction you can aggregate signatures so 00:31:05.269 --> 00:31:05.279 align:start position:0% so 00:31:05.279 --> 00:31:05.990 align:start position:0% so um 00:31:05.990 --> 00:31:06.000 align:start position:0% um 00:31:06.000 --> 00:31:08.649 align:start position:0% um so<00:31:06.720> yeah<00:31:06.960> that's<00:31:07.200> that's<00:31:07.559> another<00:31:07.799> advantage 00:31:08.649 --> 00:31:08.659 align:start position:0% so yeah that's that's another advantage 00:31:08.659 --> 00:31:11.450 align:start position:0% so yeah that's that's another advantage and<00:31:09.659> like<00:31:09.960> I<00:31:10.140> said<00:31:10.320> it<00:31:10.740> doesn't<00:31:10.860> require<00:31:11.100> any 00:31:11.450 --> 00:31:11.460 align:start position:0% and like I said it doesn't require any 00:31:11.460 --> 00:31:15.590 align:start position:0% and like I said it doesn't require any protocol<00:31:11.820> changes<00:31:12.539> so<00:31:12.899> on<00:31:13.080> any<00:31:13.559> ebm<00:31:13.980> chain 00:31:15.590 --> 00:31:15.600 align:start position:0% protocol changes so on any ebm chain 00:31:15.600 --> 00:31:17.269 align:start position:0% protocol changes so on any ebm chain um<00:31:15.779> you<00:31:16.020> can<00:31:16.080> we<00:31:16.320> can<00:31:16.500> start<00:31:16.620> experimenting 00:31:17.269 --> 00:31:17.279 align:start position:0% um you can we can start experimenting 00:31:17.279 --> 00:31:18.889 align:start position:0% um you can we can start experimenting with<00:31:17.460> this 00:31:18.889 --> 00:31:18.899 align:start position:0% with this 00:31:18.899 --> 00:31:22.730 align:start position:0% with this is<00:31:19.620> there<00:31:19.799> anything<00:31:19.919> you<00:31:20.159> want<00:31:20.279> to<00:31:20.399> add 00:31:22.730 --> 00:31:22.740 align:start position:0% 00:31:22.740 --> 00:31:27.049 align:start position:0% yeah<00:31:22.860> okay<00:31:23.840> technically<00:31:25.039> a<00:31:26.039> bundler<00:31:26.520> can<00:31:26.880> run 00:31:27.049 --> 00:31:27.059 align:start position:0% yeah okay technically a bundler can run 00:31:27.059 --> 00:31:29.510 align:start position:0% yeah okay technically a bundler can run as<00:31:27.360> a<00:31:27.539> separate<00:31:27.779> entity<00:31:28.380> it<00:31:28.980> is<00:31:29.159> much<00:31:29.340> much 00:31:29.510 --> 00:31:29.520 align:start position:0% as a separate entity it is much much 00:31:29.520 --> 00:31:31.730 align:start position:0% as a separate entity it is much much better<00:31:29.760> for<00:31:30.120> you<00:31:30.240> to<00:31:30.360> be<00:31:30.419> a<00:31:30.539> node<00:31:30.779> to<00:31:31.020> be<00:31:31.260> more 00:31:31.730 --> 00:31:31.740 align:start position:0% better for you to be a node to be more 00:31:31.740 --> 00:31:33.769 align:start position:0% better for you to be a node to be more resilient<00:31:32.159> so<00:31:32.640> the<00:31:32.880> way<00:31:33.000> to<00:31:33.179> add<00:31:33.360> it<00:31:33.539> right<00:31:33.659> now 00:31:33.769 --> 00:31:33.779 align:start position:0% resilient so the way to add it right now 00:31:33.779 --> 00:31:36.230 align:start position:0% resilient so the way to add it right now the<00:31:34.140> way<00:31:34.260> we<00:31:34.440> currently<00:31:35.039> adding<00:31:35.399> it<00:31:35.580> ungirly 00:31:36.230 --> 00:31:36.240 align:start position:0% the way we currently adding it ungirly 00:31:36.240 --> 00:31:38.330 align:start position:0% the way we currently adding it ungirly because<00:31:36.360> it's<00:31:36.539> still<00:31:36.720> on<00:31:36.899> test<00:31:37.080> is<00:31:37.620> elegant<00:31:38.100> as 00:31:38.330 --> 00:31:38.340 align:start position:0% because it's still on test is elegant as 00:31:38.340 --> 00:31:39.830 align:start position:0% because it's still on test is elegant as a<00:31:38.580> separate<00:31:38.940> server 00:31:39.830 --> 00:31:39.840 align:start position:0% a separate server 00:31:39.840 --> 00:31:41.570 align:start position:0% a separate server a 00:31:41.570 --> 00:31:41.580 align:start position:0% a 00:31:41.580 --> 00:31:43.370 align:start position:0% a the<00:31:42.059> wallets<00:31:42.419> don't<00:31:42.659> care<00:31:42.899> it's 00:31:43.370 --> 00:31:43.380 align:start position:0% the wallets don't care it's 00:31:43.380 --> 00:31:45.769 align:start position:0% the wallets don't care it's implementation<00:31:43.980> in<00:31:44.700> order<00:31:44.820> to<00:31:45.000> be<00:31:45.360> highly 00:31:45.769 --> 00:31:45.779 align:start position:0% implementation in order to be highly 00:31:45.779 --> 00:31:47.750 align:start position:0% implementation in order to be highly scalable<00:31:46.140> and<00:31:46.440> to<00:31:46.559> be<00:31:46.679> able<00:31:46.799> to<00:31:46.919> batch<00:31:47.159> more<00:31:47.460> it 00:31:47.750 --> 00:31:47.760 align:start position:0% scalable and to be able to batch more it 00:31:47.760 --> 00:31:50.570 align:start position:0% scalable and to be able to batch more it has<00:31:47.880> to<00:31:48.059> be<00:31:48.299> a<00:31:48.659> node<00:31:49.559> in<00:31:49.740> the<00:31:49.860> network<00:31:50.039> Never 00:31:50.570 --> 00:31:50.580 align:start position:0% has to be a node in the network Never 00:31:50.580 --> 00:31:52.909 align:start position:0% has to be a node in the network Never mind<00:31:50.820> already<00:31:51.059> have<00:31:51.360> a<00:31:51.539> node<00:31:51.720> that<00:31:52.440> can<00:31:52.620> run<00:31:52.740> a 00:31:52.909 --> 00:31:52.919 align:start position:0% mind already have a node that can run a 00:31:52.919 --> 00:31:55.310 align:start position:0% mind already have a node that can run a nethermind<00:31:53.520> and<00:31:54.179> there's<00:31:54.360> a<00:31:54.539> work<00:31:54.720> to<00:31:54.960> edit 00:31:55.310 --> 00:31:55.320 align:start position:0% nethermind and there's a work to edit 00:31:55.320 --> 00:31:57.470 align:start position:0% nethermind and there's a work to edit also<00:31:55.919> with<00:31:56.100> a<00:31:56.340> get<00:31:56.520> code 00:31:57.470 --> 00:31:57.480 align:start position:0% also with a get code 00:31:57.480 --> 00:32:00.230 align:start position:0% also with a get code so<00:31:58.320> what's<00:31:58.860> what's<00:31:59.159> next 00:32:00.230 --> 00:32:00.240 align:start position:0% so what's what's next 00:32:00.240 --> 00:32:03.769 align:start position:0% so what's what's next well<00:32:00.779> yes<00:32:01.380> we<00:32:01.620> can<00:32:01.799> start<00:32:01.980> experimenting<00:32:02.880> and 00:32:03.769 --> 00:32:03.779 align:start position:0% well yes we can start experimenting and 00:32:03.779 --> 00:32:04.610 align:start position:0% well yes we can start experimenting and have 00:32:04.610 --> 00:32:04.620 align:start position:0% have 00:32:04.620 --> 00:32:06.889 align:start position:0% have um<00:32:04.679> account<00:32:05.039> abstraction<00:32:05.760> and<00:32:06.299> any<00:32:06.480> evm 00:32:06.889 --> 00:32:06.899 align:start position:0% um account abstraction and any evm 00:32:06.899 --> 00:32:08.810 align:start position:0% um account abstraction and any evm compatible<00:32:07.260> chain<00:32:07.559> without<00:32:08.220> consensus 00:32:08.810 --> 00:32:08.820 align:start position:0% compatible chain without consensus 00:32:08.820 --> 00:32:09.950 align:start position:0% compatible chain without consensus changes 00:32:09.950 --> 00:32:09.960 align:start position:0% changes 00:32:09.960 --> 00:32:14.450 align:start position:0% changes but<00:32:10.740> the<00:32:11.399> goal<00:32:11.640> is<00:32:12.140> to<00:32:13.140> do<00:32:13.559> away<00:32:13.679> with<00:32:13.980> the<00:32:14.100> OAS 00:32:14.450 --> 00:32:14.460 align:start position:0% but the goal is to do away with the OAS 00:32:14.460 --> 00:32:16.389 align:start position:0% but the goal is to do away with the OAS eventually<00:32:14.820> we<00:32:15.000> don't<00:32:15.179> we<00:32:15.480> don't<00:32:15.600> need<00:32:15.779> doas 00:32:16.389 --> 00:32:16.399 align:start position:0% eventually we don't we don't need doas 00:32:16.399 --> 00:32:18.710 align:start position:0% eventually we don't we don't need doas and<00:32:17.399> uh<00:32:17.640> we<00:32:17.880> know<00:32:18.000> we're<00:32:18.240> going<00:32:18.360> to<00:32:18.480> have<00:32:18.539> to 00:32:18.710 --> 00:32:18.720 align:start position:0% and uh we know we're going to have to 00:32:18.720 --> 00:32:20.450 align:start position:0% and uh we know we're going to have to move<00:32:19.020> away<00:32:19.200> from<00:32:19.440> them 00:32:20.450 --> 00:32:20.460 align:start position:0% move away from them 00:32:20.460 --> 00:32:22.250 align:start position:0% move away from them um<00:32:20.580> eventually<00:32:20.880> at<00:32:21.179> some<00:32:21.299> point 00:32:22.250 --> 00:32:22.260 align:start position:0% um eventually at some point 00:32:22.260 --> 00:32:24.110 align:start position:0% um eventually at some point and<00:32:22.860> there<00:32:22.980> are<00:32:23.159> various<00:32:23.340> ways<00:32:23.700> of<00:32:23.880> of 00:32:24.110 --> 00:32:24.120 align:start position:0% and there are various ways of of 00:32:24.120 --> 00:32:25.970 align:start position:0% and there are various ways of of thinking<00:32:24.539> about<00:32:24.659> this 00:32:25.970 --> 00:32:25.980 align:start position:0% thinking about this 00:32:25.980 --> 00:32:26.870 align:start position:0% thinking about this um 00:32:26.870 --> 00:32:26.880 align:start position:0% um 00:32:26.880 --> 00:32:29.210 align:start position:0% um so 00:32:29.210 --> 00:32:29.220 align:start position:0% so 00:32:29.220 --> 00:32:32.210 align:start position:0% so we<00:32:29.700> want<00:32:29.880> to<00:32:30.240> want<00:32:30.960> to<00:32:31.080> want<00:32:31.320> to<00:32:31.500> have<00:32:31.620> a<00:32:31.919> count 00:32:32.210 --> 00:32:32.220 align:start position:0% we want to want to want to have a count 00:32:32.220 --> 00:32:33.889 align:start position:0% we want to want to want to have a count of<00:32:32.340> abstraction 00:32:33.889 --> 00:32:33.899 align:start position:0% of abstraction 00:32:33.899 --> 00:32:35.870 align:start position:0% of abstraction um<00:32:34.320> as<00:32:34.620> a<00:32:34.860> basic<00:32:35.100> feature<00:32:35.340> of<00:32:35.399> the<00:32:35.520> protocol 00:32:35.870 --> 00:32:35.880 align:start position:0% um as a basic feature of the protocol 00:32:35.880 --> 00:32:38.210 align:start position:0% um as a basic feature of the protocol but<00:32:36.659> we<00:32:36.899> want<00:32:37.080> to<00:32:37.200> do<00:32:37.320> it<00:32:37.500> in<00:32:37.740> a<00:32:37.860> way<00:32:37.980> that 00:32:38.210 --> 00:32:38.220 align:start position:0% but we want to do it in a way that 00:32:38.220 --> 00:32:41.330 align:start position:0% but we want to do it in a way that doesn't<00:32:38.899> enshrine<00:32:39.899> any<00:32:40.559> particular<00:32:40.919> wallet 00:32:41.330 --> 00:32:41.340 align:start position:0% doesn't enshrine any particular wallet 00:32:41.340 --> 00:32:43.549 align:start position:0% doesn't enshrine any particular wallet or<00:32:41.640> gives<00:32:41.940> an<00:32:42.480> unfair<00:32:42.779> advantage<00:32:43.140> to<00:32:43.380> any 00:32:43.549 --> 00:32:43.559 align:start position:0% or gives an unfair advantage to any 00:32:43.559 --> 00:32:45.889 align:start position:0% or gives an unfair advantage to any particular<00:32:43.919> wallet 00:32:45.889 --> 00:32:45.899 align:start position:0% particular wallet 00:32:45.899 --> 00:32:49.070 align:start position:0% particular wallet um<00:32:45.960> and<00:32:46.799> because<00:32:46.919> the<00:32:47.220> eoas<00:32:47.700> are<00:32:48.299> effect 00:32:49.070 --> 00:32:49.080 align:start position:0% um and because the eoas are effect 00:32:49.080 --> 00:32:51.769 align:start position:0% um and because the eoas are effect and<00:32:49.740> they're<00:32:50.100> very<00:32:50.220> very<00:32:50.399> common<00:32:50.640> and<00:32:51.539> they 00:32:51.769 --> 00:32:51.779 align:start position:0% and they're very very common and they 00:32:51.779 --> 00:32:53.510 align:start position:0% and they're very very common and they probably<00:32:51.960> will<00:32:52.260> be 00:32:53.510 --> 00:32:53.520 align:start position:0% probably will be 00:32:53.520 --> 00:32:56.029 align:start position:0% probably will be um<00:32:53.580> until<00:32:53.880> we<00:32:54.299> uh<00:32:55.020> you<00:32:55.440> know<00:32:55.500> we<00:32:55.679> move<00:32:55.860> away 00:32:56.029 --> 00:32:56.039 align:start position:0% um until we uh you know we move away 00:32:56.039 --> 00:32:57.830 align:start position:0% um until we uh you know we move away from<00:32:56.279> them 00:32:57.830 --> 00:32:57.840 align:start position:0% from them 00:32:57.840 --> 00:33:00.470 align:start position:0% from them um<00:32:57.960> it<00:32:58.440> will<00:32:58.679> take<00:32:58.860> a<00:32:59.100> few<00:32:59.220> years 00:33:00.470 --> 00:33:00.480 align:start position:0% um it will take a few years 00:33:00.480 --> 00:33:04.310 align:start position:0% um it will take a few years we<00:33:00.840> need<00:33:00.960> a<00:33:01.140> way<00:33:01.320> to<00:33:01.740> convert<00:33:02.159> EOS<00:33:02.520> seamlessly 00:33:04.310 --> 00:33:04.320 align:start position:0% we need a way to convert EOS seamlessly 00:33:04.320 --> 00:33:07.370 align:start position:0% we need a way to convert EOS seamlessly um<00:33:04.860> to<00:33:05.159> smart<00:33:05.399> smart<00:33:05.760> contracts 00:33:07.370 --> 00:33:07.380 align:start position:0% um to smart smart contracts 00:33:07.380 --> 00:33:10.130 align:start position:0% um to smart smart contracts so<00:33:08.279> there<00:33:08.760> will<00:33:08.940> be 00:33:10.130 --> 00:33:10.140 align:start position:0% so there will be 00:33:10.140 --> 00:33:11.330 align:start position:0% so there will be there<00:33:10.440> will<00:33:10.620> be<00:33:10.740> some<00:33:10.919> default 00:33:11.330 --> 00:33:11.340 align:start position:0% there will be some default 00:33:11.340 --> 00:33:15.049 align:start position:0% there will be some default implementation<00:33:12.299> where<00:33:13.260> yes<00:33:14.159> everything<00:33:14.640> in 00:33:15.049 --> 00:33:15.059 align:start position:0% implementation where yes everything in 00:33:15.059 --> 00:33:17.169 align:start position:0% implementation where yes everything in the<00:33:15.179> future<00:33:15.299> is<00:33:15.960> an<00:33:16.200> abstract<00:33:16.500> account 00:33:17.169 --> 00:33:17.179 align:start position:0% the future is an abstract account 00:33:17.179 --> 00:33:20.210 align:start position:0% the future is an abstract account including<00:33:18.179> EOS<00:33:18.720> but<00:33:19.559> if<00:33:19.860> you<00:33:19.980> haven't 00:33:20.210 --> 00:33:20.220 align:start position:0% including EOS but if you haven't 00:33:20.220 --> 00:33:22.789 align:start position:0% including EOS but if you haven't upgraded<00:33:21.179> your<00:33:21.360> UA<00:33:21.840> if<00:33:22.019> you<00:33:22.080> have<00:33:22.200> an<00:33:22.380> inserted 00:33:22.789 --> 00:33:22.799 align:start position:0% upgraded your UA if you have an inserted 00:33:22.799 --> 00:33:25.430 align:start position:0% upgraded your UA if you have an inserted code<00:33:23.039> into<00:33:23.340> your<00:33:23.580> eoa<00:33:24.179> if<00:33:24.360> you<00:33:24.480> haven't<00:33:24.600> like 00:33:25.430 --> 00:33:25.440 align:start position:0% code into your eoa if you haven't like 00:33:25.440 --> 00:33:27.710 align:start position:0% code into your eoa if you haven't like activated<00:33:25.919> it<00:33:26.100> in<00:33:26.279> some<00:33:26.399> way<00:33:26.580> then<00:33:27.299> it<00:33:27.539> just 00:33:27.710 --> 00:33:27.720 align:start position:0% activated it in some way then it just 00:33:27.720 --> 00:33:30.110 align:start position:0% activated it in some way then it just you<00:33:28.080> know<00:33:28.140> behind<00:33:28.500> the<00:33:28.620> scenes 00:33:30.110 --> 00:33:30.120 align:start position:0% you know behind the scenes 00:33:30.120 --> 00:33:32.630 align:start position:0% you know behind the scenes um continues<00:33:30.779> behaving<00:33:31.260> like<00:33:31.500> in<00:33:31.919> your<00:33:32.159> way 00:33:32.630 --> 00:33:32.640 align:start position:0% um continues behaving like in your way 00:33:32.640 --> 00:33:36.769 align:start position:0% um continues behaving like in your way but<00:33:32.880> it<00:33:33.240> has<00:33:33.799> it<00:33:34.799> has<00:33:34.980> the 00:33:36.769 --> 00:33:36.779 align:start position:0% but it has it has the 00:33:36.779 --> 00:33:38.950 align:start position:0% but it has it has the um the<00:33:37.500> the<00:33:37.559> functionality<00:33:38.159> requiring 00:33:38.950 --> 00:33:38.960 align:start position:0% um the the functionality requiring 00:33:38.960 --> 00:33:42.289 align:start position:0% um the the functionality requiring allowing<00:33:39.960> you<00:33:40.080> to<00:33:40.380> to<00:33:40.679> upgrade<00:33:41.220> it<00:33:41.340> of<00:33:42.179> course 00:33:42.289 --> 00:33:42.299 align:start position:0% allowing you to to upgrade it of course 00:33:42.299 --> 00:33:43.930 align:start position:0% allowing you to to upgrade it of course this<00:33:42.539> would<00:33:42.659> require<00:33:42.840> a<00:33:43.140> consensus<00:33:43.620> change 00:33:43.930 --> 00:33:43.940 align:start position:0% this would require a consensus change 00:33:43.940 --> 00:33:47.690 align:start position:0% this would require a consensus change and<00:33:44.940> there<00:33:45.179> there's<00:33:45.840> various<00:33:46.620> ways<00:33:47.100> this<00:33:47.460> it 00:33:47.690 --> 00:33:47.700 align:start position:0% and there there's various ways this it 00:33:47.700 --> 00:33:50.509 align:start position:0% and there there's various ways this it can<00:33:47.880> be<00:33:48.000> achieved<00:33:48.419> we're 00:33:50.509 --> 00:33:50.519 align:start position:0% can be achieved we're 00:33:50.519 --> 00:33:52.549 align:start position:0% can be achieved we're um<00:33:50.580> we're<00:33:50.940> discussing 00:33:52.549 --> 00:33:52.559 align:start position:0% um we're discussing 00:33:52.559 --> 00:33:54.289 align:start position:0% um we're discussing um you<00:33:52.799> know<00:33:52.860> one<00:33:53.039> way<00:33:53.220> would<00:33:53.460> be<00:33:53.700> there's<00:33:54.059> if 00:33:54.289 --> 00:33:54.299 align:start position:0% um you know one way would be there's if 00:33:54.299 --> 00:33:56.509 align:start position:0% um you know one way would be there's if we<00:33:54.360> create<00:33:54.539> a<00:33:54.720> new<00:33:54.779> transaction<00:33:55.140> type<00:33:55.519> and 00:33:56.509 --> 00:33:56.519 align:start position:0% we create a new transaction type and 00:33:56.519 --> 00:33:59.269 align:start position:0% we create a new transaction type and then<00:33:56.760> you<00:33:57.419> can<00:33:57.600> set<00:33:58.380> the<00:33:58.559> code 00:33:59.269 --> 00:33:59.279 align:start position:0% then you can set the code 00:33:59.279 --> 00:34:01.490 align:start position:0% then you can set the code for<00:33:59.640> your<00:33:59.760> eoa<00:34:00.240> this<00:34:00.720> is 00:34:01.490 --> 00:34:01.500 align:start position:0% for your eoa this is 00:34:01.500 --> 00:34:02.810 align:start position:0% for your eoa this is this<00:34:02.039> is 00:34:02.810 --> 00:34:02.820 align:start position:0% this is 00:34:02.820 --> 00:34:03.590 align:start position:0% this is um 00:34:03.590 --> 00:34:03.600 align:start position:0% um 00:34:03.600 --> 00:34:04.970 align:start position:0% um this<00:34:03.960> is<00:34:04.019> now<00:34:04.140> the<00:34:04.320> code<00:34:04.440> that's<00:34:04.620> running<00:34:04.799> your 00:34:04.970 --> 00:34:04.980 align:start position:0% this is now the code that's running your 00:34:04.980 --> 00:34:06.769 align:start position:0% this is now the code that's running your UA 00:34:06.769 --> 00:34:06.779 align:start position:0% UA 00:34:06.779 --> 00:34:07.789 align:start position:0% UA um 00:34:07.789 --> 00:34:07.799 align:start position:0% um 00:34:07.799 --> 00:34:10.669 align:start position:0% um or<00:34:08.520> you<00:34:08.940> know<00:34:09.000> there's<00:34:09.179> also<00:34:09.540> I've<00:34:10.139> been<00:34:10.320> been 00:34:10.669 --> 00:34:10.679 align:start position:0% or you know there's also I've been been 00:34:10.679 --> 00:34:12.290 align:start position:0% or you know there's also I've been been a<00:34:11.099> suggestion 00:34:12.290 --> 00:34:12.300 align:start position:0% a suggestion 00:34:12.300 --> 00:34:15.770 align:start position:0% a suggestion um<00:34:12.379> EIP<00:34:13.379> 3074<00:34:14.339> maybe<00:34:14.879> that<00:34:15.300> in<00:34:15.480> combination 00:34:15.770 --> 00:34:15.780 align:start position:0% um EIP 3074 maybe that in combination 00:34:15.780 --> 00:34:19.430 align:start position:0% um EIP 3074 maybe that in combination with<00:34:16.080> another<00:34:16.260> EAP<00:34:16.760> we<00:34:17.760> could<00:34:17.879> also<00:34:18.119> set<00:34:18.440> uh 00:34:19.430 --> 00:34:19.440 align:start position:0% with another EAP we could also set uh 00:34:19.440 --> 00:34:23.329 align:start position:0% with another EAP we could also set uh default<00:34:19.740> proxy<00:34:20.159> contract<00:34:20.520> for<00:34:20.700> all<00:34:20.879> addresses 00:34:23.329 --> 00:34:23.339 align:start position:0% 00:34:23.339 --> 00:34:24.589 align:start position:0% um I<00:34:23.700> thought<00:34:23.760> you<00:34:24.060> want<00:34:24.179> to<00:34:24.240> add<00:34:24.419> anything 00:34:24.589 --> 00:34:24.599 align:start position:0% um I thought you want to add anything 00:34:24.599 --> 00:34:28.190 align:start position:0% um I thought you want to add anything Yeah<00:34:25.500> by<00:34:25.919> default<00:34:26.760> that<00:34:27.419> basically<00:34:27.899> two 00:34:28.190 --> 00:34:28.200 align:start position:0% Yeah by default that basically two 00:34:28.200 --> 00:34:30.649 align:start position:0% Yeah by default that basically two options<00:34:28.619> one<00:34:29.099> of<00:34:29.220> them<00:34:29.339> to<00:34:29.520> let<00:34:29.639> a<00:34:29.879> user<00:34:30.179> decide 00:34:30.649 --> 00:34:30.659 align:start position:0% options one of them to let a user decide 00:34:30.659 --> 00:34:34.070 align:start position:0% options one of them to let a user decide the<00:34:31.980> exact<00:34:32.580> point<00:34:32.820> of<00:34:33.000> time<00:34:33.179> where<00:34:33.720> he<00:34:33.899> wants 00:34:34.070 --> 00:34:34.080 align:start position:0% the exact point of time where he wants 00:34:34.080 --> 00:34:37.669 align:start position:0% the exact point of time where he wants to<00:34:34.139> upgrade<00:34:34.500> its<00:34:34.800> eoa<00:34:35.220> into<00:34:35.520> a<00:34:36.080> a<00:34:37.080> contract 00:34:37.669 --> 00:34:37.679 align:start position:0% to upgrade its eoa into a a contract 00:34:37.679 --> 00:34:38.869 align:start position:0% to upgrade its eoa into a a contract wallet 00:34:38.869 --> 00:34:38.879 align:start position:0% wallet 00:34:38.879 --> 00:34:40.849 align:start position:0% wallet either<00:34:39.300> using<00:34:39.720> the<00:34:39.839> transaction<00:34:40.080> type<00:34:40.320> or<00:34:40.619> new 00:34:40.849 --> 00:34:40.859 align:start position:0% either using the transaction type or new 00:34:40.859 --> 00:34:43.970 align:start position:0% either using the transaction type or new OP<00:34:41.220> codes<00:34:41.399> on<00:34:41.639> such<00:34:42.060> the<00:34:43.020> other<00:34:43.139> way<00:34:43.320> is<00:34:43.679> to 00:34:43.970 --> 00:34:43.980 align:start position:0% OP codes on such the other way is to 00:34:43.980 --> 00:34:46.270 align:start position:0% OP codes on such the other way is to decide<00:34:44.339> that<00:34:44.639> at<00:34:44.820> one<00:34:45.119> point<00:34:45.300> of<00:34:45.480> time 00:34:46.270 --> 00:34:46.280 align:start position:0% decide that at one point of time 00:34:46.280 --> 00:34:49.310 align:start position:0% decide that at one point of time all<00:34:47.280> Eos<00:34:47.760> start<00:34:48.480> using<00:34:48.839> some<00:34:49.020> default 00:34:49.310 --> 00:34:49.320 align:start position:0% all Eos start using some default 00:34:49.320 --> 00:34:51.310 align:start position:0% all Eos start using some default implementation<00:34:49.800> we've<00:34:50.220> deployed<00:34:50.580> and<00:34:50.879> tested 00:34:51.310 --> 00:34:51.320 align:start position:0% implementation we've deployed and tested 00:34:51.320 --> 00:34:53.990 align:start position:0% implementation we've deployed and tested thoroughly<00:34:52.320> before<00:34:52.560> which<00:34:53.099> behaves<00:34:53.520> exactly 00:34:53.990 --> 00:34:54.000 align:start position:0% thoroughly before which behaves exactly 00:34:54.000 --> 00:34:56.570 align:start position:0% thoroughly before which behaves exactly like<00:34:54.179> anyway<00:34:54.419> so<00:34:55.080> all<00:34:55.260> users<00:34:55.619> will<00:34:55.800> not<00:34:55.919> notice 00:34:56.570 --> 00:34:56.580 align:start position:0% like anyway so all users will not notice 00:34:56.580 --> 00:34:59.750 align:start position:0% like anyway so all users will not notice a<00:34:56.820> difference<00:34:57.020> except<00:34:58.020> that<00:34:58.200> from<00:34:58.560> now<00:34:58.760> they 00:34:59.750 --> 00:34:59.760 align:start position:0% a difference except that from now they 00:34:59.760 --> 00:35:01.930 align:start position:0% a difference except that from now they have<00:34:59.940> a<00:35:00.180> way<00:35:00.300> to<00:35:00.599> modify<00:35:01.080> the<00:35:01.260> replace<00:35:01.440> the 00:35:01.930 --> 00:35:01.940 align:start position:0% have a way to modify the replace the 00:35:01.940 --> 00:35:04.550 align:start position:0% have a way to modify the replace the actual<00:35:02.940> implementation<00:35:03.420> so<00:35:04.140> they<00:35:04.260> have<00:35:04.440> a 00:35:04.550 --> 00:35:04.560 align:start position:0% actual implementation so they have a 00:35:04.560 --> 00:35:06.589 align:start position:0% actual implementation so they have a smart<00:35:04.740> contract<00:35:05.220> that<00:35:05.460> just<00:35:05.760> behaves<00:35:06.180> exactly 00:35:06.589 --> 00:35:06.599 align:start position:0% smart contract that just behaves exactly 00:35:06.599 --> 00:35:10.190 align:start position:0% smart contract that just behaves exactly like<00:35:06.720> an<00:35:06.900> eoa<00:35:07.380> until<00:35:08.160> they<00:35:08.460> decide<00:35:08.760> otherwise 00:35:10.190 --> 00:35:10.200 align:start position:0% like an eoa until they decide otherwise 00:35:10.200 --> 00:35:12.890 align:start position:0% like an eoa until they decide otherwise right<00:35:10.800> yes<00:35:11.460> the<00:35:12.060> basic<00:35:12.300> Contour<00:35:12.660> doesn't 00:35:12.890 --> 00:35:12.900 align:start position:0% right yes the basic Contour doesn't 00:35:12.900 --> 00:35:16.930 align:start position:0% right yes the basic Contour doesn't offer<00:35:13.440> any<00:35:13.980> of<00:35:14.160> the<00:35:14.820> Advanced<00:35:15.720> features<00:35:16.020> we 00:35:16.930 --> 00:35:16.940 align:start position:0% offer any of the Advanced features we 00:35:16.940 --> 00:35:20.210 align:start position:0% offer any of the Advanced features we described<00:35:17.940> earlier<00:35:18.240> except<00:35:18.900> the<00:35:19.140> one<00:35:19.560> feature 00:35:20.210 --> 00:35:20.220 align:start position:0% described earlier except the one feature 00:35:20.220 --> 00:35:23.210 align:start position:0% described earlier except the one feature which<00:35:20.640> is<00:35:20.880> replace<00:35:21.480> implementation<00:35:22.260> the<00:35:22.980> user 00:35:23.210 --> 00:35:23.220 align:start position:0% which is replace implementation the user 00:35:23.220 --> 00:35:24.770 align:start position:0% which is replace implementation the user can<00:35:23.339> replace<00:35:23.520> implementation<00:35:24.180> once<00:35:24.540> it<00:35:24.660> is 00:35:24.770 --> 00:35:24.780 align:start position:0% can replace implementation once it is 00:35:24.780 --> 00:35:27.349 align:start position:0% can replace implementation once it is replaced<00:35:25.200> the<00:35:25.619> sky<00:35:25.800> is<00:35:25.980> the<00:35:26.040> limited<00:35:26.400> yeah<00:35:26.940> all 00:35:27.349 --> 00:35:27.359 align:start position:0% replaced the sky is the limited yeah all 00:35:27.359 --> 00:35:30.349 align:start position:0% replaced the sky is the limited yeah all the<00:35:28.260> use<00:35:28.320> cases<00:35:28.619> that<00:35:28.980> we've<00:35:29.220> yeah<00:35:29.579> use<00:35:30.000> cases 00:35:30.349 --> 00:35:30.359 align:start position:0% the use cases that we've yeah use cases 00:35:30.359 --> 00:35:32.150 align:start position:0% the use cases that we've yeah use cases in<00:35:30.540> it<00:35:30.780> all<00:35:31.200> the<00:35:31.380> uses<00:35:31.619> that<00:35:31.800> other<00:35:32.040> people 00:35:32.150 --> 00:35:32.160 align:start position:0% in it all the uses that other people 00:35:32.160 --> 00:35:36.470 align:start position:0% in it all the uses that other people really<00:35:32.400> try<00:35:32.700> to<00:35:32.820> find 00:35:36.470 --> 00:35:36.480 align:start position:0% 00:35:36.480 --> 00:35:38.390 align:start position:0% okay<00:35:36.839> okay<00:35:36.839> I<00:35:37.260> think<00:35:37.380> that<00:35:37.500> is<00:35:37.680> if<00:35:37.859> anyone<00:35:38.220> has 00:35:38.390 --> 00:35:38.400 align:start position:0% okay okay I think that is if anyone has 00:35:38.400 --> 00:35:41.150 align:start position:0% okay okay I think that is if anyone has questioned<00:35:38.880> well<00:35:39.660> we<00:35:40.260> still<00:35:40.440> now<00:35:40.859> we're<00:35:41.040> going 00:35:41.150 --> 00:35:41.160 align:start position:0% questioned well we still now we're going 00:35:41.160 --> 00:35:43.010 align:start position:0% questioned well we still now we're going to<00:35:41.280> talk<00:35:41.460> about<00:35:41.640> well<00:35:42.180> how<00:35:42.359> do<00:35:42.480> you<00:35:42.599> join<00:35:42.839> this 00:35:43.010 --> 00:35:43.020 align:start position:0% to talk about well how do you join this 00:35:43.020 --> 00:35:46.830 align:start position:0% to talk about well how do you join this okay<00:35:43.560> yeah<00:35:43.800> yeah<00:35:43.859> okay 00:35:46.830 --> 00:35:46.840 align:start position:0% 00:35:46.840 --> 00:35:47.210 align:start position:0% [Music] 00:35:47.210 --> 00:35:47.220 align:start position:0% [Music] 00:35:47.220 --> 00:35:48.050 align:start position:0% [Music] um 00:35:48.050 --> 00:35:48.060 align:start position:0% um 00:35:48.060 --> 00:35:50.089 align:start position:0% um so<00:35:48.599> how<00:35:48.720> do<00:35:48.839> you<00:35:48.960> join<00:35:49.260> this<00:35:49.619> account 00:35:50.089 --> 00:35:50.099 align:start position:0% so how do you join this account 00:35:50.099 --> 00:35:52.790 align:start position:0% so how do you join this account abstraction<00:35:50.700> Revolution 00:35:52.790 --> 00:35:52.800 align:start position:0% abstraction Revolution 00:35:52.800 --> 00:35:55.030 align:start position:0% abstraction Revolution you<00:35:53.520> can<00:35:53.640> start<00:35:53.760> experimenting<00:35:54.420> with<00:35:54.660> the 00:35:55.030 --> 00:35:55.040 align:start position:0% you can start experimenting with the 00:35:55.040 --> 00:35:56.930 align:start position:0% you can start experimenting with the rc4337<00:35:56.040> right<00:35:56.280> away 00:35:56.930 --> 00:35:56.940 align:start position:0% rc4337 right away 00:35:56.940 --> 00:36:00.109 align:start position:0% rc4337 right away and<00:35:57.720> uh<00:35:57.980> we<00:35:58.980> had<00:35:59.160> eight<00:35:59.760> wonderful 00:36:00.109 --> 00:36:00.119 align:start position:0% and uh we had eight wonderful 00:36:00.119 --> 00:36:01.730 align:start position:0% and uh we had eight wonderful submissions 00:36:01.730 --> 00:36:01.740 align:start position:0% submissions 00:36:01.740 --> 00:36:02.510 align:start position:0% submissions um 00:36:02.510 --> 00:36:02.520 align:start position:0% um 00:36:02.520 --> 00:36:05.750 align:start position:0% um and<00:36:03.300> uh<00:36:03.780> this<00:36:04.079> is<00:36:04.140> something<00:36:04.320> that's 00:36:05.750 --> 00:36:05.760 align:start position:0% and uh this is something that's 00:36:05.760 --> 00:36:07.190 align:start position:0% and uh this is something that's um<00:36:05.820> you<00:36:05.940> know<00:36:06.060> already<00:36:06.180> working 00:36:07.190 --> 00:36:07.200 align:start position:0% um you know already working 00:36:07.200 --> 00:36:10.550 align:start position:0% um you know already working so<00:36:08.160> you<00:36:08.339> don't<00:36:08.460> have<00:36:08.579> to<00:36:08.700> wait 00:36:10.550 --> 00:36:10.560 align:start position:0% so you don't have to wait 00:36:10.560 --> 00:36:11.270 align:start position:0% so you don't have to wait um 00:36:11.270 --> 00:36:11.280 align:start position:0% um 00:36:11.280 --> 00:36:13.490 align:start position:0% um you<00:36:11.579> can<00:36:11.640> add<00:36:11.880> useful<00:36:12.660> features<00:36:13.020> like<00:36:13.260> the<00:36:13.380> one 00:36:13.490 --> 00:36:13.500 align:start position:0% you can add useful features like the one 00:36:13.500 --> 00:36:15.410 align:start position:0% you can add useful features like the one we<00:36:13.680> discussed<00:36:14.339> you<00:36:14.579> know<00:36:14.700> batching<00:36:15.060> or<00:36:15.300> key 00:36:15.410 --> 00:36:15.420 align:start position:0% we discussed you know batching or key 00:36:15.420 --> 00:36:17.630 align:start position:0% we discussed you know batching or key recovery 00:36:17.630 --> 00:36:17.640 align:start position:0% recovery 00:36:17.640 --> 00:36:19.550 align:start position:0% recovery um or<00:36:18.119> any<00:36:18.240> any<00:36:18.540> of<00:36:18.720> the<00:36:18.780> things<00:36:18.900> that<00:36:19.260> that 00:36:19.550 --> 00:36:19.560 align:start position:0% um or any any of the things that that 00:36:19.560 --> 00:36:21.710 align:start position:0% um or any any of the things that that we've<00:36:20.160> been<00:36:20.280> talking<00:36:20.400> about 00:36:21.710 --> 00:36:21.720 align:start position:0% we've been talking about 00:36:21.720 --> 00:36:23.390 align:start position:0% we've been talking about you<00:36:22.320> could<00:36:22.500> build 00:36:23.390 --> 00:36:23.400 align:start position:0% you could build 00:36:23.400 --> 00:36:25.310 align:start position:0% you could build features<00:36:24.060> that<00:36:24.420> were<00:36:24.540> totally<00:36:24.839> not<00:36:25.020> possible 00:36:25.310 --> 00:36:25.320 align:start position:0% features that were totally not possible 00:36:25.320 --> 00:36:26.810 align:start position:0% features that were totally not possible with<00:36:25.500> the<00:36:25.619> uas<00:36:25.980> that<00:36:26.280> we<00:36:26.460> haven't<00:36:26.579> thought 00:36:26.810 --> 00:36:26.820 align:start position:0% with the uas that we haven't thought 00:36:26.820 --> 00:36:29.450 align:start position:0% with the uas that we haven't thought about<00:36:27.079> and<00:36:28.079> if<00:36:28.440> you<00:36:28.560> do<00:36:28.740> if<00:36:29.040> you<00:36:29.160> if<00:36:29.339> you're 00:36:29.450 --> 00:36:29.460 align:start position:0% about and if you do if you if you're 00:36:29.460 --> 00:36:31.490 align:start position:0% about and if you do if you if you're building<00:36:29.640> anything<00:36:29.940> cool 00:36:31.490 --> 00:36:31.500 align:start position:0% building anything cool 00:36:31.500 --> 00:36:32.750 align:start position:0% building anything cool um<00:36:31.560> then<00:36:31.740> you<00:36:31.920> should<00:36:32.040> definitely<00:36:32.280> apply<00:36:32.579> for 00:36:32.750 --> 00:36:32.760 align:start position:0% um then you should definitely apply for 00:36:32.760 --> 00:36:34.910 align:start position:0% um then you should definitely apply for an<00:36:32.880> EF<00:36:33.119> Grant<00:36:33.480> because<00:36:33.900> we<00:36:34.200> want<00:36:34.320> to<00:36:34.440> see<00:36:34.619> this 00:36:34.910 --> 00:36:34.920 align:start position:0% an EF Grant because we want to see this 00:36:34.920 --> 00:36:36.760 align:start position:0% an EF Grant because we want to see this we<00:36:35.880> want<00:36:36.060> to<00:36:36.180> see<00:36:36.300> this 00:36:36.760 --> 00:36:36.770 align:start position:0% we want to see this 00:36:36.770 --> 00:36:38.170 align:start position:0% we want to see this [Music] 00:36:38.170 --> 00:36:38.180 align:start position:0% [Music] 00:36:38.180 --> 00:36:42.290 align:start position:0% [Music] used<00:36:39.180> and<00:36:40.020> adopted<00:36:40.920> and<00:36:41.339> we<00:36:41.760> want<00:36:41.940> to<00:36:42.060> see<00:36:42.119> the 00:36:42.290 --> 00:36:42.300 align:start position:0% used and adopted and we want to see the 00:36:42.300 --> 00:36:44.690 align:start position:0% used and adopted and we want to see the experimentation<00:36:42.960> and<00:36:43.619> want<00:36:44.099> to<00:36:44.280> update<00:36:44.520> this 00:36:44.690 --> 00:36:44.700 align:start position:0% experimentation and want to update this 00:36:44.700 --> 00:36:46.370 align:start position:0% experimentation and want to update this presentation<00:36:45.060> with<00:36:45.420> more<00:36:45.720> interesting<00:36:46.140> use 00:36:46.370 --> 00:36:46.380 align:start position:0% presentation with more interesting use 00:36:46.380 --> 00:36:48.290 align:start position:0% presentation with more interesting use cases 00:36:48.290 --> 00:36:48.300 align:start position:0% cases 00:36:48.300 --> 00:36:51.770 align:start position:0% cases um<00:36:48.420> so<00:36:48.960> definitely<00:36:50.060> apply<00:36:51.060> for<00:36:51.180> an<00:36:51.300> EF<00:36:51.540> Grant 00:36:51.770 --> 00:36:51.780 align:start position:0% um so definitely apply for an EF Grant 00:36:51.780 --> 00:36:55.250 align:start position:0% um so definitely apply for an EF Grant if<00:36:51.960> you<00:36:52.079> have<00:36:52.200> a<00:36:52.800> cool<00:36:53.339> idea<00:36:53.640> that<00:36:53.880> builds<00:36:54.260> on 00:36:55.250 --> 00:36:55.260 align:start position:0% if you have a cool idea that builds on 00:36:55.260 --> 00:36:58.450 align:start position:0% if you have a cool idea that builds on ERC<00:36:55.800> on<00:36:56.280> the<00:36:56.400> CRC 00:36:58.450 --> 00:36:58.460 align:start position:0% ERC on the CRC 00:36:58.460 --> 00:37:00.890 align:start position:0% ERC on the CRC the<00:36:59.460> other<00:36:59.579> thing<00:36:59.760> is 00:37:00.890 --> 00:37:00.900 align:start position:0% the other thing is 00:37:00.900 --> 00:37:03.050 align:start position:0% the other thing is if<00:37:01.260> you<00:37:01.380> are<00:37:01.500> building<00:37:01.680> adapt<00:37:02.160> you<00:37:02.820> have<00:37:02.940> to 00:37:03.050 --> 00:37:03.060 align:start position:0% if you are building adapt you have to 00:37:03.060 --> 00:37:05.510 align:start position:0% if you are building adapt you have to think<00:37:03.119> about<00:37:03.300> a<00:37:03.540> future<00:37:03.859> where<00:37:04.859> contract 00:37:05.510 --> 00:37:05.520 align:start position:0% think about a future where contract 00:37:05.520 --> 00:37:08.210 align:start position:0% think about a future where contract wallets<00:37:05.940> are<00:37:06.359> first<00:37:06.540> class<00:37:06.780> citizens<00:37:07.800> I<00:37:08.099> mean 00:37:08.210 --> 00:37:08.220 align:start position:0% wallets are first class citizens I mean 00:37:08.220 --> 00:37:10.250 align:start position:0% wallets are first class citizens I mean contract<00:37:08.579> wallets<00:37:09.000> are<00:37:09.300> already 00:37:10.250 --> 00:37:10.260 align:start position:0% contract wallets are already 00:37:10.260 --> 00:37:14.329 align:start position:0% contract wallets are already pretty<00:37:10.680> common<00:37:10.920> especially<00:37:11.640> for<00:37:12.599> teams 00:37:14.329 --> 00:37:14.339 align:start position:0% pretty common especially for teams 00:37:14.339 --> 00:37:16.849 align:start position:0% pretty common especially for teams um<00:37:14.520> you<00:37:14.760> know<00:37:14.820> multi-cigs<00:37:15.599> are<00:37:16.380> an<00:37:16.560> example 00:37:16.849 --> 00:37:16.859 align:start position:0% um you know multi-cigs are an example 00:37:16.859 --> 00:37:19.370 align:start position:0% um you know multi-cigs are an example but<00:37:17.579> still<00:37:17.820> many<00:37:18.000> dapps<00:37:18.540> assume<00:37:19.140> that<00:37:19.200> they're 00:37:19.370 --> 00:37:19.380 align:start position:0% but still many dapps assume that they're 00:37:19.380 --> 00:37:22.329 align:start position:0% but still many dapps assume that they're going<00:37:19.619> to<00:37:19.740> be<00:37:19.920> interacting<00:37:20.339> with<00:37:20.579> an<00:37:20.700> eoa 00:37:22.329 --> 00:37:22.339 align:start position:0% going to be interacting with an eoa 00:37:22.339 --> 00:37:25.250 align:start position:0% going to be interacting with an eoa and<00:37:23.339> that 00:37:25.250 --> 00:37:25.260 align:start position:0% and that 00:37:25.260 --> 00:37:26.990 align:start position:0% and that that<00:37:25.920> is<00:37:26.099> just 00:37:26.990 --> 00:37:27.000 align:start position:0% that is just 00:37:27.000 --> 00:37:31.250 align:start position:0% that is just um<00:37:27.140> an<00:37:28.140> obstacle<00:37:28.560> for<00:37:29.280> us<00:37:29.400> to<00:37:29.760> move<00:37:29.940> forward<00:37:30.260> it 00:37:31.250 --> 00:37:31.260 align:start position:0% um an obstacle for us to move forward it 00:37:31.260 --> 00:37:33.290 align:start position:0% um an obstacle for us to move forward it means<00:37:31.500> your<00:37:31.680> adapt<00:37:32.099> already<00:37:32.339> can't<00:37:32.700> interact 00:37:33.290 --> 00:37:33.300 align:start position:0% means your adapt already can't interact 00:37:33.300 --> 00:37:35.030 align:start position:0% means your adapt already can't interact with<00:37:33.839> things<00:37:34.079> like<00:37:34.200> you<00:37:34.560> know<00:37:34.740> it's<00:37:34.859> a<00:37:34.920> safe 00:37:35.030 --> 00:37:35.040 align:start position:0% with things like you know it's a safe 00:37:35.040 --> 00:37:36.349 align:start position:0% with things like you know it's a safe wallet 00:37:36.349 --> 00:37:36.359 align:start position:0% wallet 00:37:36.359 --> 00:37:37.430 align:start position:0% wallet um<00:37:36.420> if<00:37:36.599> you're<00:37:36.660> assuming<00:37:37.079> you're<00:37:37.260> making 00:37:37.430 --> 00:37:37.440 align:start position:0% um if you're assuming you're making 00:37:37.440 --> 00:37:39.589 align:start position:0% um if you're assuming you're making assumptions<00:37:37.920> such<00:37:38.220> as 00:37:39.589 --> 00:37:39.599 align:start position:0% assumptions such as 00:37:39.599 --> 00:37:42.050 align:start position:0% assumptions such as um<00:37:39.720> you<00:37:40.079> know<00:37:40.140> the<00:37:40.440> the<00:37:40.680> the<00:37:40.859> like<00:37:41.700> you<00:37:42.000> know 00:37:42.050 --> 00:37:42.060 align:start position:0% um you know the the the like you know 00:37:42.060 --> 00:37:45.470 align:start position:0% um you know the the the like you know the<00:37:42.300> how<00:37:42.540> how<00:37:42.780> signatures<00:37:43.500> are<00:37:43.619> validated<00:37:44.480> so 00:37:45.470 --> 00:37:45.480 align:start position:0% the how how signatures are validated so 00:37:45.480 --> 00:37:48.290 align:start position:0% the how how signatures are validated so there<00:37:46.020> are<00:37:46.140> easy<00:37:46.260> ways<00:37:46.800> to<00:37:47.400> make<00:37:47.640> your<00:37:48.000> dap 00:37:48.290 --> 00:37:48.300 align:start position:0% there are easy ways to make your dap 00:37:48.300 --> 00:37:49.430 align:start position:0% there are easy ways to make your dap compatible 00:37:49.430 --> 00:37:49.440 align:start position:0% compatible 00:37:49.440 --> 00:37:53.030 align:start position:0% compatible both<00:37:49.980> with<00:37:50.460> smart<00:37:51.119> contracts<00:37:51.780> right<00:37:52.260> away<00:37:52.440> and 00:37:53.030 --> 00:37:53.040 align:start position:0% both with smart contracts right away and 00:37:53.040 --> 00:37:55.670 align:start position:0% both with smart contracts right away and account<00:37:53.460> abstract<00:37:54.420> accounts<00:37:54.839> in<00:37:54.960> the<00:37:55.079> future 00:37:55.670 --> 00:37:55.680 align:start position:0% account abstract accounts in the future 00:37:55.680 --> 00:37:58.150 align:start position:0% account abstract accounts in the future and<00:37:56.640> that's<00:37:56.880> ERC 00:37:58.150 --> 00:37:58.160 align:start position:0% and that's ERC 00:37:58.160 --> 00:38:00.829 align:start position:0% and that's ERC 1271<00:37:59.160> with<00:38:00.000> just 00:38:00.829 --> 00:38:00.839 align:start position:0% 1271 with just 00:38:00.839 --> 00:38:02.690 align:start position:0% 1271 with just it<00:38:01.320> checks 00:38:02.690 --> 00:38:02.700 align:start position:0% it checks 00:38:02.700 --> 00:38:04.970 align:start position:0% it checks um it<00:38:03.119> checks<00:38:03.480> if<00:38:03.540> the<00:38:03.720> caller<00:38:04.020> has<00:38:04.140> code<00:38:04.380> and 00:38:04.970 --> 00:38:04.980 align:start position:0% um it checks if the caller has code and 00:38:04.980 --> 00:38:06.530 align:start position:0% um it checks if the caller has code and then<00:38:05.099> there's<00:38:05.220> a<00:38:05.400> mechanism<00:38:05.760> where<00:38:06.240> it<00:38:06.359> can 00:38:06.530 --> 00:38:06.540 align:start position:0% then there's a mechanism where it can 00:38:06.540 --> 00:38:07.730 align:start position:0% then there's a mechanism where it can just<00:38:06.660> invoke 00:38:07.730 --> 00:38:07.740 align:start position:0% just invoke 00:38:07.740 --> 00:38:10.010 align:start position:0% just invoke uh<00:38:08.220> invoke<00:38:08.579> a<00:38:08.760> function<00:38:09.060> and<00:38:09.480> instead<00:38:09.900> of 00:38:10.010 --> 00:38:10.020 align:start position:0% uh invoke a function and instead of 00:38:10.020 --> 00:38:12.349 align:start position:0% uh invoke a function and instead of assuming<00:38:10.740> that<00:38:10.920> there's<00:38:11.160> they<00:38:11.820> can<00:38:12.000> rely<00:38:12.240> on 00:38:12.349 --> 00:38:12.359 align:start position:0% assuming that there's they can rely on 00:38:12.359 --> 00:38:16.490 align:start position:0% assuming that there's they can rely on this<00:38:12.540> EC<00:38:13.140> this<00:38:13.320> DC<00:38:13.859> DC<00:38:14.579> DSi<00:38:15.000> key 00:38:16.490 --> 00:38:16.500 align:start position:0% this EC this DC DC DSi key 00:38:16.500 --> 00:38:19.210 align:start position:0% this EC this DC DC DSi key the<00:38:16.980> other<00:38:17.099> one<00:38:17.420> is 00:38:19.210 --> 00:38:19.220 align:start position:0% the other one is 00:38:19.220 --> 00:38:21.650 align:start position:0% the other one is if<00:38:20.220> you<00:38:20.400> can<00:38:20.520> if<00:38:20.760> you<00:38:20.940> can 00:38:21.650 --> 00:38:21.660 align:start position:0% if you can if you can 00:38:21.660 --> 00:38:24.530 align:start position:0% if you can if you can um benefit<00:38:22.079> from<00:38:22.560> batching<00:38:23.099> in<00:38:24.000> your<00:38:24.180> user 00:38:24.530 --> 00:38:24.540 align:start position:0% um benefit from batching in your user 00:38:24.540 --> 00:38:27.710 align:start position:0% um benefit from batching in your user interface<00:38:25.339> and<00:38:26.339> many<00:38:26.460> many<00:38:26.700> dapps<00:38:27.359> especially 00:38:27.710 --> 00:38:27.720 align:start position:0% interface and many many dapps especially 00:38:27.720 --> 00:38:29.030 align:start position:0% interface and many many dapps especially games<00:38:28.020> can 00:38:29.030 --> 00:38:29.040 align:start position:0% games can 00:38:29.040 --> 00:38:30.650 align:start position:0% games can then<00:38:29.579> you<00:38:29.820> should<00:38:29.940> check<00:38:30.060> if<00:38:30.420> you're 00:38:30.650 --> 00:38:30.660 align:start position:0% then you should check if you're 00:38:30.660 --> 00:38:32.930 align:start position:0% then you should check if you're connected<00:38:31.320> to<00:38:31.980> a<00:38:32.160> contract<00:38:32.460> wallet<00:38:32.820> that 00:38:32.930 --> 00:38:32.940 align:start position:0% connected to a contract wallet that 00:38:32.940 --> 00:38:34.849 align:start position:0% connected to a contract wallet that supports<00:38:33.300> it 00:38:34.849 --> 00:38:34.859 align:start position:0% supports it 00:38:34.859 --> 00:38:37.370 align:start position:0% supports it um<00:38:34.920> and<00:38:35.160> that<00:38:35.339> will<00:38:35.579> that<00:38:36.000> will<00:38:36.180> create<00:38:37.140> a 00:38:37.370 --> 00:38:37.380 align:start position:0% um and that will that will create a 00:38:37.380 --> 00:38:38.750 align:start position:0% um and that will that will create a better<00:38:37.440> experience<00:38:37.800> for<00:38:37.980> your<00:38:38.099> users<00:38:38.339> it<00:38:38.579> will 00:38:38.750 --> 00:38:38.760 align:start position:0% better experience for your users it will 00:38:38.760 --> 00:38:42.829 align:start position:0% better experience for your users it will save<00:38:39.060> uh<00:38:40.079> uh<00:38:40.320> gas<00:38:40.560> costs 00:38:42.829 --> 00:38:42.839 align:start position:0% save uh uh gas costs 00:38:42.839 --> 00:38:45.470 align:start position:0% save uh uh gas costs the<00:38:43.260> other<00:38:43.380> thing<00:38:43.619> is 00:38:45.470 --> 00:38:45.480 align:start position:0% the other thing is 00:38:45.480 --> 00:38:47.750 align:start position:0% the other thing is um<00:38:45.660> with<00:38:46.079> how<00:38:46.260> gas<00:38:46.500> is<00:38:46.740> paid 00:38:47.750 --> 00:38:47.760 align:start position:0% um with how gas is paid 00:38:47.760 --> 00:38:49.670 align:start position:0% um with how gas is paid so<00:38:48.060> if<00:38:48.180> you<00:38:48.300> have<00:38:48.420> adapt 00:38:49.670 --> 00:38:49.680 align:start position:0% so if you have adapt 00:38:49.680 --> 00:38:53.150 align:start position:0% so if you have adapt you<00:38:50.040> should<00:38:50.160> think<00:38:50.339> about<00:38:51.079> different<00:38:52.160> types 00:38:53.150 --> 00:38:53.160 align:start position:0% you should think about different types 00:38:53.160 --> 00:38:54.130 align:start position:0% you should think about different types of 00:38:54.130 --> 00:38:54.140 align:start position:0% of 00:38:54.140 --> 00:38:56.990 align:start position:0% of uh<00:38:55.140> Gas<00:38:55.440> payment<00:38:55.619> models 00:38:56.990 --> 00:38:57.000 align:start position:0% uh Gas payment models 00:38:57.000 --> 00:38:59.870 align:start position:0% uh Gas payment models I<00:38:57.540> mean<00:38:57.720> you<00:38:58.140> know<00:38:58.200> a<00:38:58.320> big<00:38:58.440> an<00:38:58.740> easy<00:38:58.920> example<00:38:59.400> is 00:38:59.870 --> 00:38:59.880 align:start position:0% I mean you know a big an easy example is 00:38:59.880 --> 00:39:02.870 align:start position:0% I mean you know a big an easy example is if<00:39:00.420> you<00:39:00.540> have<00:39:00.660> a<00:39:00.839> token<00:39:01.619> then<00:39:02.280> it<00:39:02.520> makes<00:39:02.700> sense 00:39:02.870 --> 00:39:02.880 align:start position:0% if you have a token then it makes sense 00:39:02.880 --> 00:39:05.210 align:start position:0% if you have a token then it makes sense perhaps<00:39:03.359> that<00:39:03.900> your<00:39:04.020> users<00:39:04.380> should<00:39:04.859> be<00:39:04.980> able 00:39:05.210 --> 00:39:05.220 align:start position:0% perhaps that your users should be able 00:39:05.220 --> 00:39:08.150 align:start position:0% perhaps that your users should be able to<00:39:05.400> pay<00:39:05.660> uh<00:39:06.660> for<00:39:06.839> the<00:39:07.020> transactions<00:39:07.619> in<00:39:07.980> your 00:39:08.150 --> 00:39:08.160 align:start position:0% to pay uh for the transactions in your 00:39:08.160 --> 00:39:12.170 align:start position:0% to pay uh for the transactions in your token<00:39:08.460> when<00:39:08.700> you're<00:39:08.820> using<00:39:09.180> your<00:39:09.900> dap 00:39:12.170 --> 00:39:12.180 align:start position:0% token when you're using your dap 00:39:12.180 --> 00:39:16.250 align:start position:0% token when you're using your dap um<00:39:12.780> and<00:39:13.740> if<00:39:14.339> you<00:39:14.400> don't<00:39:14.520> have<00:39:14.640> a<00:39:14.820> token<00:39:15.180> or<00:39:15.960> you 00:39:16.250 --> 00:39:16.260 align:start position:0% um and if you don't have a token or you 00:39:16.260 --> 00:39:19.550 align:start position:0% um and if you don't have a token or you want<00:39:16.380> to<00:39:16.500> subsidize<00:39:17.300> your<00:39:18.300> users<00:39:18.660> that's 00:39:19.550 --> 00:39:19.560 align:start position:0% want to subsidize your users that's 00:39:19.560 --> 00:39:22.250 align:start position:0% want to subsidize your users that's easily<00:39:19.980> accomplished 00:39:22.250 --> 00:39:22.260 align:start position:0% easily accomplished 00:39:22.260 --> 00:39:25.010 align:start position:0% easily accomplished um<00:39:22.380> with<00:39:22.800> with<00:39:23.099> the<00:39:23.839> with<00:39:24.839> account 00:39:25.010 --> 00:39:25.020 align:start position:0% um with with the with account 00:39:25.020 --> 00:39:27.290 align:start position:0% um with with the with account abstraction 00:39:27.290 --> 00:39:27.300 align:start position:0% abstraction 00:39:27.300 --> 00:39:31.310 align:start position:0% abstraction um<00:39:27.420> you<00:39:27.960> you<00:39:28.040> set<00:39:29.040> up<00:39:29.220> yeah<00:39:29.900> you<00:39:30.900> know<00:39:30.960> you<00:39:31.140> set 00:39:31.310 --> 00:39:31.320 align:start position:0% um you you set up yeah you know you set 00:39:31.320 --> 00:39:35.569 align:start position:0% um you you set up yeah you know you set up<00:39:31.500> a<00:39:32.040> a<00:39:32.520> contract<00:39:33.119> that<00:39:33.980> authorizes<00:39:34.980> to 00:39:35.569 --> 00:39:35.579 align:start position:0% up a a contract that authorizes to 00:39:35.579 --> 00:39:36.650 align:start position:0% up a a contract that authorizes to reimburse 00:39:36.650 --> 00:39:36.660 align:start position:0% reimburse 00:39:36.660 --> 00:39:40.069 align:start position:0% reimburse your<00:39:37.260> users<00:39:37.740> for<00:39:38.400> whatever<00:39:38.940> criteria<00:39:39.839> you 00:39:40.069 --> 00:39:40.079 align:start position:0% your users for whatever criteria you 00:39:40.079 --> 00:39:41.270 align:start position:0% your users for whatever criteria you feel<00:39:40.260> comfortable<00:39:40.560> with<00:39:40.740> maybe<00:39:41.040> the 00:39:41.270 --> 00:39:41.280 align:start position:0% feel comfortable with maybe the 00:39:41.280 --> 00:39:43.790 align:start position:0% feel comfortable with maybe the onboarding<00:39:41.820> process<00:39:42.060> maybe<00:39:42.480> they<00:39:42.900> they<00:39:43.619> have 00:39:43.790 --> 00:39:43.800 align:start position:0% onboarding process maybe they they have 00:39:43.800 --> 00:39:47.870 align:start position:0% onboarding process maybe they they have to<00:39:43.920> perform<00:39:44.160> some<00:39:45.060> action<00:39:45.359> but 00:39:47.870 --> 00:39:47.880 align:start position:0% 00:39:47.880 --> 00:39:50.329 align:start position:0% um<00:39:48.060> it's<00:39:48.960> uh<00:39:49.260> it's<00:39:49.619> it's<00:39:49.680> something<00:39:50.099> that's 00:39:50.329 --> 00:39:50.339 align:start position:0% um it's uh it's it's something that's 00:39:50.339 --> 00:39:51.589 align:start position:0% um it's uh it's it's something that's possible<00:39:50.700> now 00:39:51.589 --> 00:39:51.599 align:start position:0% possible now 00:39:51.599 --> 00:39:53.930 align:start position:0% possible now and 00:39:53.930 --> 00:39:53.940 align:start position:0% and 00:39:53.940 --> 00:39:56.089 align:start position:0% and a<00:39:54.420> lot<00:39:54.540> of<00:39:54.720> the<00:39:54.900> a<00:39:55.200> lot<00:39:55.380> of<00:39:55.440> the<00:39:55.560> improvements 00:39:56.089 --> 00:39:56.099 align:start position:0% a lot of the a lot of the improvements 00:39:56.099 --> 00:39:58.970 align:start position:0% a lot of the a lot of the improvements that<00:39:56.400> we're<00:39:56.579> gonna<00:39:56.700> get<00:39:57.260> for<00:39:58.260> for<00:39:58.740> that 00:39:58.970 --> 00:39:58.980 align:start position:0% that we're gonna get for for that 00:39:58.980 --> 00:40:02.510 align:start position:0% that we're gonna get for for that usability<00:39:59.520> is<00:40:00.480> going<00:40:00.720> to<00:40:00.960> also<00:40:01.200> require<00:40:01.520> some 00:40:02.510 --> 00:40:02.520 align:start position:0% usability is going to also require some 00:40:02.520 --> 00:40:05.290 align:start position:0% usability is going to also require some you<00:40:03.119> know<00:40:03.240> wallet<00:40:03.599> support 00:40:05.290 --> 00:40:05.300 align:start position:0% you know wallet support 00:40:05.300 --> 00:40:09.950 align:start position:0% you know wallet support so<00:40:06.320> wallets<00:40:07.320> are<00:40:07.500> an<00:40:07.859> important<00:40:08.220> part 00:40:09.950 --> 00:40:09.960 align:start position:0% so wallets are an important part 00:40:09.960 --> 00:40:15.290 align:start position:0% so wallets are an important part um<00:40:10.020> of<00:40:10.859> uh<00:40:11.700> of<00:40:12.240> usability<00:40:12.720> for<00:40:13.200> depths<00:40:13.680> and<00:40:14.640> as 00:40:15.290 --> 00:40:15.300 align:start position:0% um of uh of usability for depths and as 00:40:15.300 --> 00:40:17.410 align:start position:0% um of uh of usability for depths and as a<00:40:15.420> depth<00:40:15.720> developer<00:40:16.140> you<00:40:16.800> have<00:40:16.980> some 00:40:17.410 --> 00:40:17.420 align:start position:0% a depth developer you have some 00:40:17.420 --> 00:40:19.970 align:start position:0% a depth developer you have some influence<00:40:18.420> by<00:40:18.839> collaborating<00:40:19.320> with<00:40:19.619> wallet 00:40:19.970 --> 00:40:19.980 align:start position:0% influence by collaborating with wallet 00:40:19.980 --> 00:40:22.250 align:start position:0% influence by collaborating with wallet Dev<00:40:20.099> saying<00:40:20.520> okay<00:40:20.640> this<00:40:21.000> is<00:40:21.599> this<00:40:22.140> is 00:40:22.250 --> 00:40:22.260 align:start position:0% Dev saying okay this is this is 00:40:22.260 --> 00:40:24.170 align:start position:0% Dev saying okay this is this is something<00:40:22.560> that<00:40:23.099> you<00:40:23.400> know<00:40:23.520> would<00:40:23.700> would<00:40:23.940> be 00:40:24.170 --> 00:40:24.180 align:start position:0% something that you know would would be 00:40:24.180 --> 00:40:26.089 align:start position:0% something that you know would would be beneficial<00:40:24.599> for<00:40:24.960> my<00:40:25.140> use<00:40:25.320> case 00:40:26.089 --> 00:40:26.099 align:start position:0% beneficial for my use case 00:40:26.099 --> 00:40:27.530 align:start position:0% beneficial for my use case uh 00:40:27.530 --> 00:40:27.540 align:start position:0% uh 00:40:27.540 --> 00:40:29.030 align:start position:0% uh um<00:40:27.660> and<00:40:28.079> you<00:40:28.260> can 00:40:29.030 --> 00:40:29.040 align:start position:0% um and you can 00:40:29.040 --> 00:40:31.730 align:start position:0% um and you can you<00:40:29.520> can<00:40:29.640> have<00:40:30.300> a<00:40:30.540> have<00:40:31.140> a<00:40:31.320> bit<00:40:31.500> of<00:40:31.619> an 00:40:31.730 --> 00:40:31.740 align:start position:0% you can have a have a bit of an 00:40:31.740 --> 00:40:34.550 align:start position:0% you can have a have a bit of an influence<00:40:32.160> by<00:40:33.060> just<00:40:33.300> saying<00:40:33.900> okay<00:40:34.079> this<00:40:34.440> is 00:40:34.550 --> 00:40:34.560 align:start position:0% influence by just saying okay this is 00:40:34.560 --> 00:40:36.710 align:start position:0% influence by just saying okay this is this<00:40:34.800> is<00:40:34.980> useful<00:40:35.280> for<00:40:35.460> me<00:40:35.579> I<00:40:36.300> need<00:40:36.540> this 00:40:36.710 --> 00:40:36.720 align:start position:0% this is useful for me I need this 00:40:36.720 --> 00:40:38.390 align:start position:0% this is useful for me I need this feature<00:40:37.079> in<00:40:37.200> the<00:40:37.380> wallet 00:40:38.390 --> 00:40:38.400 align:start position:0% feature in the wallet 00:40:38.400 --> 00:40:40.370 align:start position:0% feature in the wallet um<00:40:38.460> for<00:40:38.700> example<00:40:38.940> supporting<00:40:39.540> account 00:40:40.370 --> 00:40:40.380 align:start position:0% um for example supporting account 00:40:40.380 --> 00:40:45.790 align:start position:0% um for example supporting account abstraction 00:40:45.790 --> 00:40:45.800 align:start position:0% 00:40:45.800 --> 00:40:49.970 align:start position:0% so<00:40:46.880> other<00:40:47.880> than<00:40:48.119> talking<00:40:48.300> with<00:40:48.660> us 00:40:49.970 --> 00:40:49.980 align:start position:0% so other than talking with us 00:40:49.980 --> 00:40:51.710 align:start position:0% so other than talking with us um<00:40:50.099> we're<00:40:50.460> happy<00:40:50.700> to<00:40:50.880> help<00:40:51.060> anyone<00:40:51.480> that's 00:40:51.710 --> 00:40:51.720 align:start position:0% um we're happy to help anyone that's 00:40:51.720 --> 00:40:54.650 align:start position:0% um we're happy to help anyone that's implementing<00:40:52.500> uh<00:40:53.040> different<00:40:53.280> use<00:40:53.520> cases<00:40:53.820> we 00:40:54.650 --> 00:40:54.660 align:start position:0% implementing uh different use cases we 00:40:54.660 --> 00:40:56.270 align:start position:0% implementing uh different use cases we do<00:40:54.780> have<00:40:54.900> an<00:40:55.079> SDK<00:40:55.440> up 00:40:56.270 --> 00:40:56.280 align:start position:0% do have an SDK up 00:40:56.280 --> 00:40:59.329 align:start position:0% do have an SDK up uh<00:40:56.880> later<00:40:57.119> you<00:40:57.720> have<00:40:57.960> will<00:40:58.320> share<00:40:58.680> on<00:40:59.220> his 00:40:59.329 --> 00:40:59.339 align:start position:0% uh later you have will share on his 00:40:59.339 --> 00:41:01.190 align:start position:0% uh later you have will share on his Twitter 00:41:01.190 --> 00:41:01.200 align:start position:0% Twitter 00:41:01.200 --> 00:41:04.670 align:start position:0% Twitter um<00:41:01.320> the<00:41:01.740> the<00:41:01.920> links<00:41:02.400> but<00:41:03.300> there's<00:41:03.960> there's<00:41:04.260> a 00:41:04.670 --> 00:41:04.680 align:start position:0% um the the links but there's there's a 00:41:04.680 --> 00:41:06.410 align:start position:0% um the the links but there's there's a there's<00:41:05.099> an<00:41:05.280> SDK 00:41:06.410 --> 00:41:06.420 align:start position:0% there's an SDK 00:41:06.420 --> 00:41:08.569 align:start position:0% there's an SDK there's<00:41:06.780> an<00:41:06.960> SDK<00:41:07.380> you<00:41:07.619> can<00:41:07.800> come<00:41:07.920> up<00:41:08.040> to<00:41:08.220> us<00:41:08.400> and 00:41:08.569 --> 00:41:08.579 align:start position:0% there's an SDK you can come up to us and 00:41:08.579 --> 00:41:10.130 align:start position:0% there's an SDK you can come up to us and we'll<00:41:08.760> give<00:41:08.940> you<00:41:08.940> yeah<00:41:09.420> or<00:41:09.599> we'll<00:41:09.839> just<00:41:10.020> give 00:41:10.130 --> 00:41:10.140 align:start position:0% we'll give you yeah or we'll just give 00:41:10.140 --> 00:41:11.510 align:start position:0% we'll give you yeah or we'll just give you<00:41:10.260> but<00:41:10.440> I<00:41:10.560> can<00:41:10.680> I<00:41:10.800> think<00:41:10.920> I<00:41:11.040> think<00:41:11.160> I<00:41:11.339> just 00:41:11.510 --> 00:41:11.520 align:start position:0% you but I can I think I think I just 00:41:11.520 --> 00:41:12.890 align:start position:0% you but I can I think I think I just like<00:41:11.640> open<00:41:11.820> this<00:41:12.060> right<00:41:12.240> now<00:41:12.420> and<00:41:12.540> show<00:41:12.720> like 00:41:12.890 --> 00:41:12.900 align:start position:0% like open this right now and show like 00:41:12.900 --> 00:41:14.630 align:start position:0% like open this right now and show like where<00:41:13.140> this<00:41:13.260> is<00:41:13.440> pointing<00:41:13.740> to 00:41:14.630 --> 00:41:14.640 align:start position:0% where this is pointing to 00:41:14.640 --> 00:41:17.150 align:start position:0% where this is pointing to wait<00:41:14.880> this<00:41:15.359> is<00:41:15.480> very<00:41:15.660> small<00:41:15.900> why<00:41:16.740> is<00:41:16.920> it<00:41:17.040> so 00:41:17.150 --> 00:41:17.160 align:start position:0% wait this is very small why is it so 00:41:17.160 --> 00:41:18.410 align:start position:0% wait this is very small why is it so small 00:41:18.410 --> 00:41:18.420 align:start position:0% small 00:41:18.420 --> 00:41:21.770 align:start position:0% small yeah<00:41:19.380> yeah 00:41:21.770 --> 00:41:21.780 align:start position:0% 00:41:21.780 --> 00:41:26.270 align:start position:0% so<00:41:22.680> we<00:41:23.460> have<00:41:23.579> our<00:41:23.700> SDK<00:41:24.240> it's<00:41:24.960> on<00:41:25.200> GitHub<00:41:25.680> eth 00:41:26.270 --> 00:41:26.280 align:start position:0% so we have our SDK it's on GitHub eth 00:41:26.280 --> 00:41:28.730 align:start position:0% so we have our SDK it's on GitHub eth infinitism<00:41:26.820> account<00:41:27.060> obstruction<00:41:27.540> it's<00:41:28.500> not 00:41:28.730 --> 00:41:28.740 align:start position:0% infinitism account obstruction it's not 00:41:28.740 --> 00:41:31.790 align:start position:0% infinitism account obstruction it's not dedicated<00:41:29.220> contracts<00:41:30.000> oh<00:41:30.540> where<00:41:30.780> is<00:41:30.839> the<00:41:30.960> SDK 00:41:31.790 --> 00:41:31.800 align:start position:0% dedicated contracts oh where is the SDK 00:41:31.800 --> 00:41:34.190 align:start position:0% dedicated contracts oh where is the SDK is<00:41:32.220> infinity 00:41:34.190 --> 00:41:34.200 align:start position:0% is infinity 00:41:34.200 --> 00:41:36.589 align:start position:0% is infinity okay<00:41:34.800> oh<00:41:35.099> this<00:41:35.280> is<00:41:35.400> the<00:41:35.640> link<00:41:35.760> is<00:41:36.000> broken<00:41:36.359> then 00:41:36.589 --> 00:41:36.599 align:start position:0% okay oh this is the link is broken then 00:41:36.599 --> 00:41:42.230 align:start position:0% okay oh this is the link is broken then all<00:41:36.900> right<00:41:37.020> we'll<00:41:37.260> fix<00:41:37.440> that 00:41:42.230 --> 00:41:42.240 align:start position:0% 00:41:42.240 --> 00:41:44.810 align:start position:0% that<00:41:42.780> is<00:41:43.260> um 00:41:44.810 --> 00:41:44.820 align:start position:0% that is um 00:41:44.820 --> 00:41:48.410 align:start position:0% that is um okay<00:41:45.300> oh<00:41:46.020> this<00:41:46.200> this<00:41:46.380> is<00:41:46.560> the<00:41:46.680> SDK<00:41:47.280> okay<00:41:48.000> so<00:41:48.240> the 00:41:48.410 --> 00:41:48.420 align:start position:0% okay oh this this is the SDK okay so the 00:41:48.420 --> 00:41:49.670 align:start position:0% okay oh this this is the SDK okay so the reference<00:41:48.720> implementation<00:41:49.200> of<00:41:49.380> a<00:41:49.440> bundler 00:41:49.670 --> 00:41:49.680 align:start position:0% reference implementation of a bundler 00:41:49.680 --> 00:41:54.589 align:start position:0% reference implementation of a bundler simple<00:41:49.920> bundler<00:41:50.400> and<00:41:50.820> the<00:41:50.940> SDK<00:41:51.420> oh<00:41:51.900> cool<00:41:52.260> okay 00:41:54.589 --> 00:41:54.599 align:start position:0% simple bundler and the SDK oh cool okay 00:41:54.599 --> 00:41:57.170 align:start position:0% simple bundler and the SDK oh cool okay so<00:41:54.900> that's<00:41:54.960> the<00:41:55.140> SDK<00:41:55.619> we<00:41:56.280> will<00:41:56.460> fix<00:41:56.760> the<00:41:57.000> link 00:41:57.170 --> 00:41:57.180 align:start position:0% so that's the SDK we will fix the link 00:41:57.180 --> 00:41:58.910 align:start position:0% so that's the SDK we will fix the link later 00:41:58.910 --> 00:41:58.920 align:start position:0% later 00:41:58.920 --> 00:42:01.069 align:start position:0% later um<00:41:58.980> you<00:41:59.099> can<00:41:59.220> also<00:41:59.400> read<00:41:59.579> up<00:41:59.760> on<00:41:59.940> the<00:42:00.060> ERC 00:42:01.069 --> 00:42:01.079 align:start position:0% um you can also read up on the ERC 00:42:01.079 --> 00:42:04.730 align:start position:0% um you can also read up on the ERC uh 00:42:04.730 --> 00:42:04.740 align:start position:0% 00:42:04.740 --> 00:42:07.310 align:start position:0% and<00:42:05.460> oh<00:42:05.760> maybe<00:42:05.940> that's<00:42:06.180> the<00:42:06.359> right<00:42:06.480> link<00:42:06.660> no 00:42:07.310 --> 00:42:07.320 align:start position:0% and oh maybe that's the right link no 00:42:07.320 --> 00:42:10.069 align:start position:0% and oh maybe that's the right link no that's<00:42:07.619> that's<00:42:07.920> really<00:42:08.220> uh<00:42:08.640> yeah<00:42:09.300> that's<00:42:09.780> your 00:42:10.069 --> 00:42:10.079 align:start position:0% that's that's really uh yeah that's your 00:42:10.079 --> 00:42:11.630 align:start position:0% that's that's really uh yeah that's your seat<00:42:10.320> itself<00:42:10.560> yeah<00:42:10.859> yeah<00:42:10.980> it's<00:42:11.160> the<00:42:11.280> ERC 00:42:11.630 --> 00:42:11.640 align:start position:0% seat itself yeah yeah it's the ERC 00:42:11.640 --> 00:42:14.030 align:start position:0% seat itself yeah yeah it's the ERC itself<00:42:11.940> so<00:42:12.540> you<00:42:12.660> can<00:42:12.720> read<00:42:12.839> the<00:42:12.960> ERC<00:42:13.440> it's<00:42:13.859> very 00:42:14.030 --> 00:42:14.040 align:start position:0% itself so you can read the ERC it's very 00:42:14.040 --> 00:42:15.410 align:start position:0% itself so you can read the ERC it's very detailed 00:42:15.410 --> 00:42:15.420 align:start position:0% detailed 00:42:15.420 --> 00:42:17.870 align:start position:0% detailed uh<00:42:16.140> but<00:42:16.320> you<00:42:16.560> can<00:42:16.680> get<00:42:16.920> very<00:42:17.520> precise 00:42:17.870 --> 00:42:17.880 align:start position:0% uh but you can get very precise 00:42:17.880 --> 00:42:19.130 align:start position:0% uh but you can get very precise understanding<00:42:18.359> of<00:42:18.480> how<00:42:18.660> it<00:42:18.780> works<00:42:18.960> there's 00:42:19.130 --> 00:42:19.140 align:start position:0% understanding of how it works there's 00:42:19.140 --> 00:42:21.230 align:start position:0% understanding of how it works there's also<00:42:19.440> a<00:42:19.500> discussion<00:42:19.859> on<00:42:20.099> the<00:42:20.220> ethereum 00:42:21.230 --> 00:42:21.240 align:start position:0% also a discussion on the ethereum 00:42:21.240 --> 00:42:24.890 align:start position:0% also a discussion on the ethereum magician's<00:42:22.140> uh<00:42:22.560> forum 00:42:24.890 --> 00:42:24.900 align:start position:0% magician's uh forum 00:42:24.900 --> 00:42:27.230 align:start position:0% magician's uh forum and 00:42:27.230 --> 00:42:27.240 align:start position:0% and 00:42:27.240 --> 00:42:29.270 align:start position:0% and and<00:42:27.540> of<00:42:27.839> course 00:42:29.270 --> 00:42:29.280 align:start position:0% and of course 00:42:29.280 --> 00:42:31.190 align:start position:0% and of course um<00:42:29.339> it's<00:42:29.940> nice<00:42:30.180> to<00:42:30.300> be<00:42:30.420> able<00:42:30.540> to<00:42:30.780> talk<00:42:30.900> with 00:42:31.190 --> 00:42:31.200 align:start position:0% um it's nice to be able to talk with 00:42:31.200 --> 00:42:33.230 align:start position:0% um it's nice to be able to talk with people<00:42:31.320> so<00:42:31.859> we<00:42:32.040> have<00:42:32.160> a<00:42:32.280> Discord 00:42:33.230 --> 00:42:33.240 align:start position:0% people so we have a Discord 00:42:33.240 --> 00:42:36.710 align:start position:0% people so we have a Discord now<00:42:33.720> we<00:42:33.960> have<00:42:34.140> a<00:42:34.320> Discord<00:42:34.740> server<00:42:35.160> and<00:42:35.880> uh 00:42:36.710 --> 00:42:36.720 align:start position:0% now we have a Discord server and uh 00:42:36.720 --> 00:42:38.270 align:start position:0% now we have a Discord server and uh you're<00:42:36.960> very<00:42:37.079> welcome<00:42:37.260> to<00:42:37.500> join<00:42:37.859> and<00:42:38.099> ask 00:42:38.270 --> 00:42:38.280 align:start position:0% you're very welcome to join and ask 00:42:38.280 --> 00:42:39.770 align:start position:0% you're very welcome to join and ask questions<00:42:38.640> and 00:42:39.770 --> 00:42:39.780 align:start position:0% questions and 00:42:39.780 --> 00:42:42.170 align:start position:0% questions and even<00:42:40.500> after<00:42:40.800> this<00:42:41.160> event<00:42:41.339> like<00:42:41.820> if<00:42:42.000> there's 00:42:42.170 --> 00:42:42.180 align:start position:0% even after this event like if there's 00:42:42.180 --> 00:42:44.030 align:start position:0% even after this event like if there's something<00:42:42.420> that<00:42:42.780> you<00:42:43.320> don't<00:42:43.440> get<00:42:43.619> to<00:42:43.740> ask<00:42:43.859> us 00:42:44.030 --> 00:42:44.040 align:start position:0% something that you don't get to ask us 00:42:44.040 --> 00:42:46.670 align:start position:0% something that you don't get to ask us in<00:42:44.280> person 00:42:46.670 --> 00:42:46.680 align:start position:0% 00:42:46.680 --> 00:42:48.290 align:start position:0% um<00:42:46.800> and<00:42:47.040> yeah<00:42:47.160> maybe<00:42:47.339> now<00:42:47.579> we<00:42:47.760> will<00:42:47.940> just<00:42:48.119> take 00:42:48.290 --> 00:42:48.300 align:start position:0% um and yeah maybe now we will just take 00:42:48.300 --> 00:42:57.290 align:start position:0% um and yeah maybe now we will just take some<00:42:48.540> questions<00:42:48.800> yeah<00:42:49.800> yes<00:42:50.220> over<00:42:50.520> there 00:42:57.290 --> 00:42:57.300 align:start position:0% 00:42:57.300 --> 00:42:59.210 align:start position:0% okay<00:42:57.780> the 00:42:59.210 --> 00:42:59.220 align:start position:0% okay the 00:42:59.220 --> 00:43:01.490 align:start position:0% okay the internal<00:42:59.819> development<00:43:00.240> roadmap<00:43:00.780> what<00:43:01.260> we've 00:43:01.490 --> 00:43:01.500 align:start position:0% internal development roadmap what we've 00:43:01.500 --> 00:43:03.170 align:start position:0% internal development roadmap what we've developed<00:43:01.800> are<00:43:01.980> the<00:43:02.220> interfaces<00:43:02.640> and<00:43:03.000> the 00:43:03.170 --> 00:43:03.180 align:start position:0% developed are the interfaces and the 00:43:03.180 --> 00:43:05.210 align:start position:0% developed are the interfaces and the core<00:43:03.359> contract<00:43:04.140> that<00:43:04.560> performs<00:43:04.980> this<00:43:05.040> magic 00:43:05.210 --> 00:43:05.220 align:start position:0% core contract that performs this magic 00:43:05.220 --> 00:43:06.829 align:start position:0% core contract that performs this magic we<00:43:05.579> call<00:43:05.700> it<00:43:05.819> entry<00:43:06.119> point 00:43:06.829 --> 00:43:06.839 align:start position:0% we call it entry point 00:43:06.839 --> 00:43:09.050 align:start position:0% we call it entry point it<00:43:07.380> was<00:43:07.560> audited<00:43:07.980> but<00:43:08.160> then<00:43:08.280> was<00:43:08.460> extensively 00:43:09.050 --> 00:43:09.060 align:start position:0% it was audited but then was extensively 00:43:09.060 --> 00:43:11.930 align:start position:0% it was audited but then was extensively modified<00:43:09.540> to<00:43:09.780> support<00:43:09.960> the<00:43:10.319> l2s<00:43:11.099> that<00:43:11.520> is<00:43:11.700> not 00:43:11.930 --> 00:43:11.940 align:start position:0% modified to support the l2s that is not 00:43:11.940 --> 00:43:14.690 align:start position:0% modified to support the l2s that is not yet<00:43:12.300> audited<00:43:13.200> we<00:43:13.980> still<00:43:14.099> have<00:43:14.220> some<00:43:14.400> work<00:43:14.520> on 00:43:14.690 --> 00:43:14.700 align:start position:0% yet audited we still have some work on 00:43:14.700 --> 00:43:17.870 align:start position:0% yet audited we still have some work on it<00:43:15.319> the<00:43:16.319> API<00:43:16.680> probably<00:43:16.920> won't<00:43:17.160> change<00:43:17.339> so<00:43:17.640> a 00:43:17.870 --> 00:43:17.880 align:start position:0% it the API probably won't change so a 00:43:17.880 --> 00:43:19.790 align:start position:0% it the API probably won't change so a wallet<00:43:18.180> will<00:43:18.420> be<00:43:18.660> able<00:43:18.839> to<00:43:19.020> work<00:43:19.140> so<00:43:19.560> it's<00:43:19.680> not 00:43:19.790 --> 00:43:19.800 align:start position:0% wallet will be able to work so it's not 00:43:19.800 --> 00:43:21.950 align:start position:0% wallet will be able to work so it's not deployment<00:43:20.220> deploy<00:43:20.760> the<00:43:20.940> mainnet<00:43:21.359> only<00:43:21.720> on 00:43:21.950 --> 00:43:21.960 align:start position:0% deployment deploy the mainnet only on 00:43:21.960 --> 00:43:23.870 align:start position:0% deployment deploy the mainnet only on testnet<00:43:22.440> currently 00:43:23.870 --> 00:43:23.880 align:start position:0% testnet currently 00:43:23.880 --> 00:43:26.150 align:start position:0% testnet currently but<00:43:24.359> you<00:43:24.839> can<00:43:24.960> create<00:43:25.380> and<00:43:25.800> start 00:43:26.150 --> 00:43:26.160 align:start position:0% but you can create and start 00:43:26.160 --> 00:43:27.710 align:start position:0% but you can create and start experimenting<00:43:26.700> with<00:43:26.819> Wallets<00:43:27.180> on<00:43:27.480> top<00:43:27.599> of 00:43:27.710 --> 00:43:27.720 align:start position:0% experimenting with Wallets on top of 00:43:27.720 --> 00:43:29.750 align:start position:0% experimenting with Wallets on top of that<00:43:27.839> the<00:43:28.680> interface<00:43:29.040> of<00:43:29.160> a<00:43:29.339> wallet<00:43:29.520> the 00:43:29.750 --> 00:43:29.760 align:start position:0% that the interface of a wallet the 00:43:29.760 --> 00:43:31.130 align:start position:0% that the interface of a wallet the change<00:43:29.940> of<00:43:30.180> wallet<00:43:30.420> needs<00:43:30.660> to<00:43:30.720> be<00:43:30.780> it's<00:43:30.900> quite 00:43:31.130 --> 00:43:31.140 align:start position:0% change of wallet needs to be it's quite 00:43:31.140 --> 00:43:33.530 align:start position:0% change of wallet needs to be it's quite minimal<00:43:31.920> I<00:43:32.460> can<00:43:32.520> go<00:43:32.700> through<00:43:32.819> it<00:43:33.000> adding<00:43:33.420> a 00:43:33.530 --> 00:43:33.540 align:start position:0% minimal I can go through it adding a 00:43:33.540 --> 00:43:34.670 align:start position:0% minimal I can go through it adding a single<00:43:33.780> method 00:43:34.670 --> 00:43:34.680 align:start position:0% single method 00:43:34.680 --> 00:43:37.069 align:start position:0% single method or<00:43:35.099> two<00:43:35.400> uh 00:43:37.069 --> 00:43:37.079 align:start position:0% or two uh 00:43:37.079 --> 00:43:41.329 align:start position:0% or two uh yeah<00:43:37.740> we<00:43:38.400> have<00:43:38.579> a<00:43:38.760> sample<00:43:39.119> uh<00:43:39.560> yeah<00:43:40.560> a<00:43:40.859> sample 00:43:41.329 --> 00:43:41.339 align:start position:0% yeah we have a sample uh yeah a sample 00:43:41.339 --> 00:43:43.550 align:start position:0% yeah we have a sample uh yeah a sample that<00:43:41.579> uses<00:43:42.119> that<00:43:42.599> adds<00:43:42.960> account<00:43:43.140> attraction 00:43:43.550 --> 00:43:43.560 align:start position:0% that uses that adds account attraction 00:43:43.560 --> 00:43:45.230 align:start position:0% that uses that adds account attraction support<00:43:43.800> to<00:43:43.980> ignore<00:43:44.220> the<00:43:44.400> safe<00:43:44.520> you<00:43:44.940> add<00:43:45.060> the 00:43:45.230 --> 00:43:45.240 align:start position:0% support to ignore the safe you add the 00:43:45.240 --> 00:43:48.230 align:start position:0% support to ignore the safe you add the module<00:43:45.420> and<00:43:45.599> you<00:43:45.720> basically<00:43:46.020> get<00:43:46.920> make<00:43:47.280> a<00:43:47.579> okay 00:43:48.230 --> 00:43:48.240 align:start position:0% module and you basically get make a okay 00:43:48.240 --> 00:43:51.710 align:start position:0% module and you basically get make a okay a<00:43:48.599> single<00:43:48.900> owner<00:43:49.380> and<00:43:50.280> you<00:43:50.520> can<00:43:50.640> also<00:43:50.819> safe<00:43:51.060> and 00:43:51.710 --> 00:43:51.720 align:start position:0% a single owner and you can also safe and 00:43:51.720 --> 00:43:55.190 align:start position:0% a single owner and you can also safe and account<00:43:51.960> obstruct<00:43:52.500> the<00:43:53.099> compatible 00:43:55.190 --> 00:43:55.200 align:start position:0% account obstruct the compatible 00:43:55.200 --> 00:43:56.030 align:start position:0% account obstruct the compatible um 00:43:56.030 --> 00:43:56.040 align:start position:0% um 00:43:56.040 --> 00:43:58.309 align:start position:0% um so<00:43:56.460> yes<00:43:56.640> you<00:43:57.240> can<00:43:57.359> create 00:43:58.309 --> 00:43:58.319 align:start position:0% so yes you can create 00:43:58.319 --> 00:44:00.050 align:start position:0% so yes you can create and<00:43:58.740> there<00:43:58.920> are<00:43:59.040> some<00:43:59.220> work<00:43:59.460> on<00:43:59.640> creating 00:44:00.050 --> 00:44:00.060 align:start position:0% and there are some work on creating 00:44:00.060 --> 00:44:01.970 align:start position:0% and there are some work on creating wallets<00:44:00.540> today 00:44:01.970 --> 00:44:01.980 align:start position:0% wallets today 00:44:01.980 --> 00:44:04.370 align:start position:0% wallets today in<00:44:02.940> terms<00:44:03.119> of<00:44:03.180> applications<00:44:03.599> yes<00:44:04.140> it's 00:44:04.370 --> 00:44:04.380 align:start position:0% in terms of applications yes it's 00:44:04.380 --> 00:44:05.630 align:start position:0% in terms of applications yes it's chicken<00:44:04.619> and<00:44:04.859> egg<00:44:04.980> application<00:44:05.339> it's<00:44:05.520> a 00:44:05.630 --> 00:44:05.640 align:start position:0% chicken and egg application it's a 00:44:05.640 --> 00:44:08.030 align:start position:0% chicken and egg application it's a wallet<00:44:05.880> in<00:44:06.060> order<00:44:06.180> to<00:44:06.359> work<00:44:06.560> there<00:44:07.560> is<00:44:07.740> a<00:44:07.920> way 00:44:08.030 --> 00:44:08.040 align:start position:0% wallet in order to work there is a way 00:44:08.040 --> 00:44:10.550 align:start position:0% wallet in order to work there is a way no<00:44:08.339> it's<00:44:09.060> for<00:44:09.240> a<00:44:09.359> basically<00:44:09.599> a<00:44:09.900> hackathon<00:44:10.260> an 00:44:10.550 --> 00:44:10.560 align:start position:0% no it's for a basically a hackathon an 00:44:10.560 --> 00:44:12.170 align:start position:0% no it's for a basically a hackathon an application<00:44:10.980> can<00:44:11.220> work<00:44:11.460> without<00:44:11.640> a<00:44:11.940> wallet 00:44:12.170 --> 00:44:12.180 align:start position:0% application can work without a wallet 00:44:12.180 --> 00:44:13.430 align:start position:0% application can work without a wallet but<00:44:12.359> it's<00:44:12.540> not<00:44:12.780> something<00:44:12.900> else<00:44:13.140> you<00:44:13.319> want 00:44:13.430 --> 00:44:13.440 align:start position:0% but it's not something else you want 00:44:13.440 --> 00:44:16.790 align:start position:0% but it's not something else you want your<00:44:13.680> user<00:44:13.980> want<00:44:14.160> to<00:44:14.339> sign<00:44:15.000> blindly<00:44:15.480> a<00:44:15.660> hash 00:44:16.790 --> 00:44:16.800 align:start position:0% your user want to sign blindly a hash 00:44:16.800 --> 00:44:19.130 align:start position:0% your user want to sign blindly a hash if<00:44:17.460> you're<00:44:17.700> good<00:44:18.359> with<00:44:18.540> that<00:44:18.660> it's<00:44:18.900> also 00:44:19.130 --> 00:44:19.140 align:start position:0% if you're good with that it's also 00:44:19.140 --> 00:44:20.809 align:start position:0% if you're good with that it's also possible<00:44:19.380> to<00:44:19.500> with<00:44:19.740> an<00:44:20.160> application<00:44:20.460> can<00:44:20.700> work 00:44:20.809 --> 00:44:20.819 align:start position:0% possible to with an application can work 00:44:20.819 --> 00:44:23.270 align:start position:0% possible to with an application can work with<00:44:21.000> accountability<00:44:21.480> in<00:44:21.839> the<00:44:21.900> day 00:44:23.270 --> 00:44:23.280 align:start position:0% with accountability in the day 00:44:23.280 --> 00:44:25.609 align:start position:0% with accountability in the day the<00:44:23.760> way<00:44:23.880> gas<00:44:24.119> abstraction<00:44:24.540> works<00:44:25.020> is<00:44:25.319> that 00:44:25.609 --> 00:44:25.619 align:start position:0% the way gas abstraction works is that 00:44:25.619 --> 00:44:28.849 align:start position:0% the way gas abstraction works is that when<00:44:26.040> you<00:44:26.160> submit<00:44:26.460> a<00:44:26.579> user<00:44:26.819> up 00:44:28.849 --> 00:44:28.859 align:start position:0% when you submit a user up 00:44:28.859 --> 00:44:30.589 align:start position:0% when you submit a user up I<00:44:29.040> said<00:44:29.220> the<00:44:29.520> contract<00:44:29.819> itself<00:44:30.180> validates 00:44:30.589 --> 00:44:30.599 align:start position:0% I said the contract itself validates 00:44:30.599 --> 00:44:33.829 align:start position:0% I said the contract itself validates itself<00:44:30.960> the<00:44:31.260> signature<00:44:31.859> and<00:44:32.420> its<00:44:33.420> nonsense 00:44:33.829 --> 00:44:33.839 align:start position:0% itself the signature and its nonsense 00:44:33.839 --> 00:44:37.010 align:start position:0% itself the signature and its nonsense and<00:44:34.020> in<00:44:34.260> order<00:44:34.380> to<00:44:34.619> accept<00:44:35.099> the<00:44:35.520> request<00:44:36.420> but 00:44:37.010 --> 00:44:37.020 align:start position:0% and in order to accept the request but 00:44:37.020 --> 00:44:38.870 align:start position:0% and in order to accept the request but there's<00:44:37.140> also<00:44:37.500> a<00:44:37.680> pointer<00:44:37.980> to<00:44:38.220> what<00:44:38.520> we<00:44:38.640> call<00:44:38.760> a 00:44:38.870 --> 00:44:38.880 align:start position:0% there's also a pointer to what we call a 00:44:38.880 --> 00:44:40.970 align:start position:0% there's also a pointer to what we call a paymaster<00:44:39.300> a<00:44:39.900> payment<00:44:40.079> is<00:44:40.440> a<00:44:40.619> contract<00:44:40.800> that 00:44:40.970 --> 00:44:40.980 align:start position:0% paymaster a payment is a contract that 00:44:40.980 --> 00:44:43.010 align:start position:0% paymaster a payment is a contract that before<00:44:41.160> submitting<00:44:41.700> the<00:44:41.819> transaction<00:44:42.180> has<00:44:42.839> a 00:44:43.010 --> 00:44:43.020 align:start position:0% before submitting the transaction has a 00:44:43.020 --> 00:44:44.809 align:start position:0% before submitting the transaction has a chance<00:44:43.200> to<00:44:43.560> decide<00:44:43.980> whether<00:44:44.160> it<00:44:44.339> agrees<00:44:44.700> to 00:44:44.809 --> 00:44:44.819 align:start position:0% chance to decide whether it agrees to 00:44:44.819 --> 00:44:47.150 align:start position:0% chance to decide whether it agrees to pay<00:44:44.940> or<00:44:45.060> not<00:44:45.240> if<00:44:46.020> it<00:44:46.140> says<00:44:46.319> okay<00:44:46.500> that<00:44:46.859> is<00:44:46.980> it 00:44:47.150 --> 00:44:47.160 align:start position:0% pay or not if it says okay that is it 00:44:47.160 --> 00:44:50.030 align:start position:0% pay or not if it says okay that is it doesn't<00:44:47.280> revert<00:44:48.260> it<00:44:49.260> will<00:44:49.380> use<00:44:49.560> its<00:44:49.980> own 00:44:50.030 --> 00:44:50.040 align:start position:0% doesn't revert it will use its own 00:44:50.040 --> 00:44:52.609 align:start position:0% doesn't revert it will use its own balance<00:44:50.760> its<00:44:51.060> own<00:44:51.119> stake<00:44:51.420> and<00:44:51.660> everything<00:44:51.780> to 00:44:52.609 --> 00:44:52.619 align:start position:0% balance its own stake and everything to 00:44:52.619 --> 00:44:55.069 align:start position:0% balance its own stake and everything to pay<00:44:52.800> for<00:44:52.980> this<00:44:53.160> transaction<00:44:53.520> now<00:44:54.300> what<00:44:54.839> this 00:44:55.069 --> 00:44:55.079 align:start position:0% pay for this transaction now what this 00:44:55.079 --> 00:44:57.470 align:start position:0% pay for this transaction now what this payment<00:44:55.319> does<00:44:55.859> on<00:44:56.040> chain<00:44:56.280> depends<00:44:57.119> on<00:44:57.300> the 00:44:57.470 --> 00:44:57.480 align:start position:0% payment does on chain depends on the 00:44:57.480 --> 00:45:01.490 align:start position:0% payment does on chain depends on the paymaster<00:44:58.260> so<00:44:59.099> the<00:45:00.060> most<00:45:00.420> obvious<00:45:00.839> example<00:45:01.380> of 00:45:01.490 --> 00:45:01.500 align:start position:0% paymaster so the most obvious example of 00:45:01.500 --> 00:45:03.530 align:start position:0% paymaster so the most obvious example of a<00:45:01.619> paymaster<00:45:02.040> is<00:45:02.640> that<00:45:02.819> the<00:45:02.940> validation<00:45:03.300> will 00:45:03.530 --> 00:45:03.540 align:start position:0% a paymaster is that the validation will 00:45:03.540 --> 00:45:06.050 align:start position:0% a paymaster is that the validation will be<00:45:03.720> I<00:45:04.079> will<00:45:04.260> check<00:45:04.440> that<00:45:04.740> this<00:45:04.980> user<00:45:05.400> has<00:45:05.760> a 00:45:06.050 --> 00:45:06.060 align:start position:0% be I will check that this user has a 00:45:06.060 --> 00:45:09.230 align:start position:0% be I will check that this user has a balance<00:45:06.359> of<00:45:06.720> enough<00:45:06.960> die<00:45:07.460> and<00:45:08.460> has<00:45:08.819> approval 00:45:09.230 --> 00:45:09.240 align:start position:0% balance of enough die and has approval 00:45:09.240 --> 00:45:11.450 align:start position:0% balance of enough die and has approval for<00:45:09.420> me<00:45:09.599> to<00:45:09.839> use<00:45:10.200> this<00:45:10.380> die<00:45:10.560> and<00:45:10.800> I<00:45:10.980> will<00:45:11.099> grab 00:45:11.450 --> 00:45:11.460 align:start position:0% for me to use this die and I will grab 00:45:11.460 --> 00:45:14.270 align:start position:0% for me to use this die and I will grab enough<00:45:11.940> die<00:45:12.300> to<00:45:12.720> cover<00:45:12.839> this<00:45:13.079> transaction<00:45:13.500> so 00:45:14.270 --> 00:45:14.280 align:start position:0% enough die to cover this transaction so 00:45:14.280 --> 00:45:16.569 align:start position:0% enough die to cover this transaction so and<00:45:14.579> at<00:45:14.760> the<00:45:14.880> end<00:45:15.000> I<00:45:15.119> will<00:45:15.300> refund<00:45:15.720> it<00:45:15.839> with<00:45:16.079> the 00:45:16.569 --> 00:45:16.579 align:start position:0% and at the end I will refund it with the 00:45:16.579 --> 00:45:19.849 align:start position:0% and at the end I will refund it with the excess<00:45:17.579> So<00:45:18.180> eventually 00:45:19.849 --> 00:45:19.859 align:start position:0% excess So eventually 00:45:19.859 --> 00:45:23.750 align:start position:0% excess So eventually I<00:45:20.280> pay<00:45:20.460> the<00:45:20.880> user<00:45:21.180> pays<00:45:21.599> with<00:45:22.020> tokens<00:45:22.579> for<00:45:23.579> the 00:45:23.750 --> 00:45:23.760 align:start position:0% I pay the user pays with tokens for the 00:45:23.760 --> 00:45:26.510 align:start position:0% I pay the user pays with tokens for the transaction<00:45:24.060> this<00:45:24.839> models 00:45:26.510 --> 00:45:26.520 align:start position:0% transaction this models 00:45:26.520 --> 00:45:28.730 align:start position:0% transaction this models it's<00:45:27.480> most<00:45:27.720> obvious<00:45:28.020> use<00:45:28.319> case<00:45:28.500> of<00:45:28.619> a 00:45:28.730 --> 00:45:28.740 align:start position:0% it's most obvious use case of a 00:45:28.740 --> 00:45:30.290 align:start position:0% it's most obvious use case of a paymaster<00:45:29.099> but<00:45:29.339> there<00:45:29.460> are<00:45:29.579> other<00:45:29.640> use<00:45:29.940> cases 00:45:30.290 --> 00:45:30.300 align:start position:0% paymaster but there are other use cases 00:45:30.300 --> 00:45:32.990 align:start position:0% paymaster but there are other use cases if<00:45:31.020> you<00:45:31.200> want<00:45:31.380> a<00:45:31.859> voting<00:45:32.280> data<00:45:32.579> and<00:45:32.700> you<00:45:32.819> don't 00:45:32.990 --> 00:45:33.000 align:start position:0% if you want a voting data and you don't 00:45:33.000 --> 00:45:34.849 align:start position:0% if you want a voting data and you don't want<00:45:33.119> the<00:45:33.240> user<00:45:33.480> to<00:45:33.540> pay<00:45:33.660> anything<00:45:33.839> okay 00:45:34.849 --> 00:45:34.859 align:start position:0% want the user to pay anything okay 00:45:34.859 --> 00:45:36.589 align:start position:0% want the user to pay anything okay so<00:45:35.280> the<00:45:35.460> check<00:45:35.579> is<00:45:35.819> that<00:45:35.940> the<00:45:36.119> user<00:45:36.420> is 00:45:36.589 --> 00:45:36.599 align:start position:0% so the check is that the user is 00:45:36.599 --> 00:45:38.089 align:start position:0% so the check is that the user is eligible<00:45:37.079> to<00:45:37.319> vote 00:45:38.089 --> 00:45:38.099 align:start position:0% eligible to vote 00:45:38.099 --> 00:45:39.829 align:start position:0% eligible to vote if<00:45:38.400> a<00:45:38.520> user<00:45:38.760> is<00:45:38.819> eligible<00:45:39.180> to<00:45:39.359> vote<00:45:39.480> and<00:45:39.660> didn't 00:45:39.829 --> 00:45:39.839 align:start position:0% if a user is eligible to vote and didn't 00:45:39.839 --> 00:45:42.410 align:start position:0% if a user is eligible to vote and didn't vote<00:45:40.140> yet<00:45:40.319> I<00:45:40.920> agree<00:45:41.160> to<00:45:41.280> pay 00:45:42.410 --> 00:45:42.420 align:start position:0% vote yet I agree to pay 00:45:42.420 --> 00:45:44.450 align:start position:0% vote yet I agree to pay it's<00:45:42.900> an<00:45:43.020> another<00:45:43.440> example<00:45:43.859> of<00:45:43.980> a<00:45:44.099> paymaster 00:45:44.450 --> 00:45:44.460 align:start position:0% it's an another example of a paymaster 00:45:44.460 --> 00:45:47.990 align:start position:0% it's an another example of a paymaster other<00:45:45.000> examples<00:45:45.359> are<00:45:45.599> still<00:45:46.339> open<00:45:47.339> you<00:45:47.819> can 00:45:47.990 --> 00:45:48.000 align:start position:0% other examples are still open you can 00:45:48.000 --> 00:45:49.730 align:start position:0% other examples are still open you can write<00:45:48.119> whatever<00:45:48.300> you<00:45:48.599> like 00:45:49.730 --> 00:45:49.740 align:start position:0% write whatever you like 00:45:49.740 --> 00:45:52.130 align:start position:0% write whatever you like just<00:45:50.160> just<00:45:50.400> a<00:45:50.700> contrast<00:45:51.119> right<00:45:51.720> now<00:45:51.839> if<00:45:52.079> you're 00:45:52.130 --> 00:45:52.140 align:start position:0% just just a contrast right now if you're 00:45:52.140 --> 00:45:53.510 align:start position:0% just just a contrast right now if you're using<00:45:52.380> Nosa<00:45:52.859> safe 00:45:53.510 --> 00:45:53.520 align:start position:0% using Nosa safe 00:45:53.520 --> 00:45:56.030 align:start position:0% using Nosa safe then<00:45:54.180> someone<00:45:54.599> on<00:45:55.020> your<00:45:55.200> someone<00:45:55.619> on<00:45:55.920> your 00:45:56.030 --> 00:45:56.040 align:start position:0% then someone on your someone on your 00:45:56.040 --> 00:45:58.970 align:start position:0% then someone on your someone on your team<00:45:56.280> has<00:45:56.520> to<00:45:56.760> like<00:45:57.480> pay<00:45:57.839> from<00:45:58.680> their<00:45:58.800> account 00:45:58.970 --> 00:45:58.980 align:start position:0% team has to like pay from their account 00:45:58.980 --> 00:46:01.069 align:start position:0% team has to like pay from their account right<00:45:59.640> even<00:45:59.880> if<00:46:00.119> the<00:46:00.240> agnostic<00:46:00.720> safe<00:46:00.839> has 00:46:01.069 --> 00:46:01.079 align:start position:0% right even if the agnostic safe has 00:46:01.079 --> 00:46:02.990 align:start position:0% right even if the agnostic safe has plenty<00:46:01.500> of<00:46:01.560> ease 00:46:02.990 --> 00:46:03.000 align:start position:0% plenty of ease 00:46:03.000 --> 00:46:05.150 align:start position:0% plenty of ease um<00:46:03.119> someone<00:46:03.359> still<00:46:03.780> needs<00:46:04.140> to<00:46:04.260> like<00:46:04.800> pay<00:46:04.920> from 00:46:05.150 --> 00:46:05.160 align:start position:0% um someone still needs to like pay from 00:46:05.160 --> 00:46:06.710 align:start position:0% um someone still needs to like pay from their<00:46:05.339> own<00:46:05.460> accounts<00:46:05.819> just<00:46:06.060> to<00:46:06.180> have<00:46:06.359> that 00:46:06.710 --> 00:46:06.720 align:start position:0% their own accounts just to have that 00:46:06.720 --> 00:46:10.370 align:start position:0% their own accounts just to have that transaction<00:46:07.440> uh<00:46:08.280> finalized 00:46:10.370 --> 00:46:10.380 align:start position:0% transaction uh finalized 00:46:10.380 --> 00:46:12.890 align:start position:0% transaction uh finalized um<00:46:10.500> so<00:46:11.099> with<00:46:11.520> account<00:46:11.700> obstruction<00:46:12.119> that 00:46:12.890 --> 00:46:12.900 align:start position:0% um so with account obstruction that 00:46:12.900 --> 00:46:14.470 align:start position:0% um so with account obstruction that wouldn't<00:46:13.020> be<00:46:13.260> necessary 00:46:14.470 --> 00:46:14.480 align:start position:0% wouldn't be necessary 00:46:14.480 --> 00:46:16.490 align:start position:0% wouldn't be necessary your<00:46:15.480> account<00:46:15.599> will<00:46:15.839> be<00:46:15.960> able<00:46:16.079> to<00:46:16.200> pay<00:46:16.380> for 00:46:16.490 --> 00:46:16.500 align:start position:0% your account will be able to pay for 00:46:16.500 --> 00:46:17.930 align:start position:0% your account will be able to pay for yourself<00:46:16.680> and<00:46:17.099> this<00:46:17.220> doesn't<00:46:17.400> require<00:46:17.640> a 00:46:17.930 --> 00:46:17.940 align:start position:0% yourself and this doesn't require a 00:46:17.940 --> 00:46:20.329 align:start position:0% yourself and this doesn't require a paymaster<00:46:18.359> but<00:46:19.140> let's<00:46:19.319> say<00:46:19.560> you're<00:46:20.099> you're 00:46:20.329 --> 00:46:20.339 align:start position:0% paymaster but let's say you're you're 00:46:20.339 --> 00:46:22.190 align:start position:0% paymaster but let's say you're you're safe<00:46:20.880> for 00:46:22.190 --> 00:46:22.200 align:start position:0% safe for 00:46:22.200 --> 00:46:24.770 align:start position:0% safe for um going<00:46:22.680> back<00:46:22.800> to<00:46:22.980> the<00:46:23.099> safe<00:46:23.640> example<00:46:24.480> if 00:46:24.770 --> 00:46:24.780 align:start position:0% um going back to the safe example if 00:46:24.780 --> 00:46:27.710 align:start position:0% um going back to the safe example if ignosis<00:46:25.319> safe<00:46:25.560> doesn't<00:46:26.339> hold<00:46:26.520> any<00:46:26.760> heat<00:46:27.000> it 00:46:27.710 --> 00:46:27.720 align:start position:0% ignosis safe doesn't hold any heat it 00:46:27.720 --> 00:46:29.930 align:start position:0% ignosis safe doesn't hold any heat it doesn't<00:46:27.839> hold<00:46:28.140> sufficient<00:46:29.099> eth<00:46:29.400> where<00:46:29.819> you 00:46:29.930 --> 00:46:29.940 align:start position:0% doesn't hold sufficient eth where you 00:46:29.940 --> 00:46:31.010 align:start position:0% doesn't hold sufficient eth where you don't<00:46:30.000> want<00:46:30.119> to<00:46:30.240> have<00:46:30.300> to<00:46:30.420> care<00:46:30.540> about<00:46:30.720> the 00:46:31.010 --> 00:46:31.020 align:start position:0% don't want to have to care about the 00:46:31.020 --> 00:46:32.870 align:start position:0% don't want to have to care about the balance<00:46:31.319> and<00:46:31.619> continually<00:46:32.040> like<00:46:32.280> exchanging 00:46:32.870 --> 00:46:32.880 align:start position:0% balance and continually like exchanging 00:46:32.880 --> 00:46:35.450 align:start position:0% balance and continually like exchanging and<00:46:33.119> topping<00:46:33.599> it<00:46:33.720> off<00:46:34.260> and<00:46:34.680> whatever<00:46:34.859> you<00:46:35.280> have 00:46:35.450 --> 00:46:35.460 align:start position:0% and topping it off and whatever you have 00:46:35.460 --> 00:46:38.210 align:start position:0% and topping it off and whatever you have a<00:46:36.300> balance<00:46:36.720> of<00:46:36.900> assuming<00:46:37.380> it's<00:46:37.560> enough<00:46:37.859> to<00:46:38.099> pay 00:46:38.210 --> 00:46:38.220 align:start position:0% a balance of assuming it's enough to pay 00:46:38.220 --> 00:46:40.010 align:start position:0% a balance of assuming it's enough to pay for<00:46:38.400> the<00:46:38.520> gas 00:46:40.010 --> 00:46:40.020 align:start position:0% for the gas 00:46:40.020 --> 00:46:43.130 align:start position:0% for the gas um you<00:46:40.560> would<00:46:40.740> essentially<00:46:41.780> include<00:46:42.780> in<00:46:42.960> your 00:46:43.130 --> 00:46:43.140 align:start position:0% um you would essentially include in your 00:46:43.140 --> 00:46:45.290 align:start position:0% um you would essentially include in your transaction<00:46:43.500> a<00:46:43.800> reference<00:46:44.220> to<00:46:44.760> something 00:46:45.290 --> 00:46:45.300 align:start position:0% transaction a reference to something 00:46:45.300 --> 00:46:47.630 align:start position:0% transaction a reference to something we're<00:46:45.720> calling<00:46:46.079> a<00:46:46.200> token<00:46:46.440> paymaster<00:46:46.920> and 00:46:47.630 --> 00:46:47.640 align:start position:0% we're calling a token paymaster and 00:46:47.640 --> 00:46:49.370 align:start position:0% we're calling a token paymaster and token<00:46:48.000> paint<00:46:48.180> Master<00:46:48.420> can<00:46:48.780> be<00:46:48.960> completely 00:46:49.370 --> 00:46:49.380 align:start position:0% token paint Master can be completely 00:46:49.380 --> 00:46:51.609 align:start position:0% token paint Master can be completely autonomous<00:46:49.859> contract<00:46:50.520> on<00:46:50.819> chain 00:46:51.609 --> 00:46:51.619 align:start position:0% autonomous contract on chain 00:46:51.619 --> 00:46:56.569 align:start position:0% autonomous contract on chain that<00:46:52.619> it<00:46:53.040> just<00:46:53.579> um<00:46:53.579> it<00:46:53.940> accepts<00:46:54.240> tokens<00:46:54.859> it<00:46:55.859> and 00:46:56.569 --> 00:46:56.579 align:start position:0% that it just um it accepts tokens it and 00:46:56.579 --> 00:46:58.250 align:start position:0% that it just um it accepts tokens it and it<00:46:56.819> it<00:46:56.940> would<00:46:57.180> pay<00:46:57.359> for<00:46:57.540> the<00:46:57.720> transaction<00:46:58.020> in 00:46:58.250 --> 00:46:58.260 align:start position:0% it it would pay for the transaction in 00:46:58.260 --> 00:46:59.990 align:start position:0% it it would pay for the transaction in eth<00:46:58.560> and<00:46:58.800> then<00:46:58.859> it<00:46:59.040> would<00:46:59.160> settle<00:46:59.520> in<00:46:59.700> some<00:46:59.880> way 00:46:59.990 --> 00:47:00.000 align:start position:0% eth and then it would settle in some way 00:47:00.000 --> 00:47:03.770 align:start position:0% eth and then it would settle in some way so<00:47:00.720> well<00:47:01.619> an<00:47:02.339> old<00:47:02.460> reference<00:47:02.880> like<00:47:03.180> an<00:47:03.540> older 00:47:03.770 --> 00:47:03.780 align:start position:0% so well an old reference like an older 00:47:03.780 --> 00:47:05.150 align:start position:0% so well an old reference like an older reference<00:47:04.079> implementation<00:47:04.619> recreative 00:47:05.150 --> 00:47:05.160 align:start position:0% reference implementation recreative 00:47:05.160 --> 00:47:07.970 align:start position:0% reference implementation recreative which<00:47:05.400> is<00:47:05.520> using<00:47:05.880> swap<00:47:06.240> using<00:47:07.020> unit<00:47:07.200> Swap<00:47:07.619> and 00:47:07.970 --> 00:47:07.980 align:start position:0% which is using swap using unit Swap and 00:47:07.980 --> 00:47:09.950 align:start position:0% which is using swap using unit Swap and add<00:47:08.160> single<00:47:08.460> transaction<00:47:08.880> which<00:47:09.599> was<00:47:09.720> kind<00:47:09.900> of 00:47:09.950 --> 00:47:09.960 align:start position:0% add single transaction which was kind of 00:47:09.960 --> 00:47:11.569 align:start position:0% add single transaction which was kind of expensive<00:47:10.380> either<00:47:10.619> cheaper<00:47:11.160> ways<00:47:11.400> of<00:47:11.460> doing 00:47:11.569 --> 00:47:11.579 align:start position:0% expensive either cheaper ways of doing 00:47:11.579 --> 00:47:14.089 align:start position:0% expensive either cheaper ways of doing it<00:47:11.819> but<00:47:12.359> just<00:47:12.540> it's<00:47:13.079> like<00:47:13.319> very<00:47:13.560> simple<00:47:13.740> and 00:47:14.089 --> 00:47:14.099 align:start position:0% it but just it's like very simple and 00:47:14.099 --> 00:47:16.069 align:start position:0% it but just it's like very simple and one<00:47:14.400> single<00:47:14.700> Atomic<00:47:15.060> transaction 00:47:16.069 --> 00:47:16.079 align:start position:0% one single Atomic transaction 00:47:16.079 --> 00:47:19.849 align:start position:0% one single Atomic transaction it<00:47:16.500> gets<00:47:16.800> paid<00:47:17.040> it<00:47:17.400> gets<00:47:17.760> in<00:47:17.880> a<00:47:18.119> sort<00:47:18.420> of<00:47:18.859> an 00:47:19.849 --> 00:47:19.859 align:start position:0% it gets paid it gets in a sort of an 00:47:19.859 --> 00:47:23.210 align:start position:0% it gets paid it gets in a sort of an allowance<00:47:20.339> in<00:47:21.180> whatever<00:47:21.420> token<00:47:21.900> you<00:47:22.020> have<00:47:22.220> it 00:47:23.210 --> 00:47:23.220 align:start position:0% allowance in whatever token you have it 00:47:23.220 --> 00:47:25.010 align:start position:0% allowance in whatever token you have it pays<00:47:23.520> for<00:47:23.640> the<00:47:23.760> gas<00:47:23.940> it<00:47:24.300> charges<00:47:24.660> the 00:47:25.010 --> 00:47:25.020 align:start position:0% pays for the gas it charges the 00:47:25.020 --> 00:47:27.109 align:start position:0% pays for the gas it charges the transaction<00:47:25.380> fee 00:47:27.109 --> 00:47:27.119 align:start position:0% transaction fee 00:47:27.119 --> 00:47:29.569 align:start position:0% transaction fee um<00:47:27.240> and<00:47:27.540> then<00:47:27.660> it<00:47:27.960> gives<00:47:28.140> you<00:47:28.319> back<00:47:28.560> the<00:47:29.339> the 00:47:29.569 --> 00:47:29.579 align:start position:0% um and then it gives you back the the 00:47:29.579 --> 00:47:31.690 align:start position:0% um and then it gives you back the the remaining<00:47:30.119> uh<00:47:30.480> tokens 00:47:31.690 --> 00:47:31.700 align:start position:0% remaining uh tokens 00:47:31.700 --> 00:47:34.490 align:start position:0% remaining uh tokens so<00:47:32.700> with<00:47:33.119> account<00:47:33.240> abstraction<00:47:33.839> if<00:47:34.319> you<00:47:34.380> want 00:47:34.490 --> 00:47:34.500 align:start position:0% so with account abstraction if you want 00:47:34.500 --> 00:47:36.109 align:start position:0% so with account abstraction if you want to<00:47:34.619> use<00:47:34.740> if<00:47:35.040> you<00:47:35.160> want<00:47:35.280> to<00:47:35.400> use<00:47:35.520> that<00:47:35.700> for 00:47:36.109 --> 00:47:36.119 align:start position:0% to use if you want to use that for 00:47:36.119 --> 00:47:38.089 align:start position:0% to use if you want to use that for example<00:47:36.359> then<00:47:36.960> you<00:47:37.140> would<00:47:37.260> just<00:47:37.440> include<00:47:37.740> oh 00:47:38.089 --> 00:47:38.099 align:start position:0% example then you would just include oh 00:47:38.099 --> 00:47:40.069 align:start position:0% example then you would just include oh the 00:47:40.069 --> 00:47:40.079 align:start position:0% the 00:47:40.079 --> 00:47:41.930 align:start position:0% the um<00:47:40.200> The<00:47:40.560> Entity<00:47:40.800> that<00:47:41.160> is<00:47:41.280> paying<00:47:41.520> for<00:47:41.640> the<00:47:41.819> gas 00:47:41.930 --> 00:47:41.940 align:start position:0% um The Entity that is paying for the gas 00:47:41.940 --> 00:47:45.349 align:start position:0% um The Entity that is paying for the gas is<00:47:42.540> a<00:47:42.660> token<00:47:43.020> paymaster<00:47:43.500> but<00:47:44.400> there<00:47:44.579> is<00:47:44.760> a<00:47:45.240> way 00:47:45.349 --> 00:47:45.359 align:start position:0% is a token paymaster but there is a way 00:47:45.359 --> 00:47:49.010 align:start position:0% is a token paymaster but there is a way for<00:47:45.780> the<00:47:45.960> token<00:47:46.319> paymaster<00:47:46.859> you<00:47:47.819> know<00:47:47.880> to<00:47:48.540> to 00:47:49.010 --> 00:47:49.020 align:start position:0% for the token paymaster you know to to 00:47:49.020 --> 00:47:51.230 align:start position:0% for the token paymaster you know to to receive<00:47:49.440> a<00:47:49.560> commitment<00:47:49.920> from<00:47:50.579> your<00:47:51.000> account 00:47:51.230 --> 00:47:51.240 align:start position:0% receive a commitment from your account 00:47:51.240 --> 00:47:53.270 align:start position:0% receive a commitment from your account to<00:47:52.020> pay<00:47:52.200> it<00:47:52.380> back 00:47:53.270 --> 00:47:53.280 align:start position:0% to pay it back 00:47:53.280 --> 00:47:55.430 align:start position:0% to pay it back so<00:47:54.119> it's<00:47:54.359> not<00:47:54.480> just<00:47:54.660> subsidizing<00:47:55.319> the 00:47:55.430 --> 00:47:55.440 align:start position:0% so it's not just subsidizing the 00:47:55.440 --> 00:47:57.710 align:start position:0% so it's not just subsidizing the transaction<00:47:55.800> that's<00:47:56.280> also<00:47:56.640> possible<00:47:57.000> it 00:47:57.710 --> 00:47:57.720 align:start position:0% transaction that's also possible it 00:47:57.720 --> 00:47:59.750 align:start position:0% transaction that's also possible it makes<00:47:57.900> it<00:47:58.079> possible<00:47:58.380> right<00:47:58.740> now<00:47:58.920> you<00:47:59.579> have<00:47:59.640> to 00:47:59.750 --> 00:47:59.760 align:start position:0% makes it possible right now you have to 00:47:59.760 --> 00:48:01.069 align:start position:0% makes it possible right now you have to split 00:48:01.069 --> 00:48:01.079 align:start position:0% split 00:48:01.079 --> 00:48:03.470 align:start position:0% split different<00:48:01.380> concerns<00:48:02.339> if<00:48:02.579> you<00:48:02.880> need<00:48:03.180> some 00:48:03.470 --> 00:48:03.480 align:start position:0% different concerns if you need some 00:48:03.480 --> 00:48:05.870 align:start position:0% different concerns if you need some corporate<00:48:03.839> level<00:48:04.020> security<00:48:04.380> using<00:48:04.980> a<00:48:05.220> Galaxy 00:48:05.870 --> 00:48:05.880 align:start position:0% corporate level security using a Galaxy 00:48:05.880 --> 00:48:07.490 align:start position:0% corporate level security using a Galaxy safe<00:48:06.300> and<00:48:06.540> if<00:48:06.660> you<00:48:06.720> want<00:48:06.839> a<00:48:06.960> game<00:48:07.079> you<00:48:07.260> will<00:48:07.380> use 00:48:07.490 --> 00:48:07.500 align:start position:0% safe and if you want a game you will use 00:48:07.500 --> 00:48:08.990 align:start position:0% safe and if you want a game you will use this<00:48:07.619> metamask<00:48:08.040> and<00:48:08.220> fuse<00:48:08.460> your<00:48:08.640> private<00:48:08.819> you 00:48:08.990 --> 00:48:09.000 align:start position:0% this metamask and fuse your private you 00:48:09.000 --> 00:48:12.410 align:start position:0% this metamask and fuse your private you can<00:48:09.060> use<00:48:09.180> trezor<00:48:09.660> now<00:48:10.500> if<00:48:11.040> you<00:48:11.280> if<00:48:12.180> you<00:48:12.300> want 00:48:12.410 --> 00:48:12.420 align:start position:0% can use trezor now if you if you want 00:48:12.420 --> 00:48:13.970 align:start position:0% can use trezor now if you if you want them<00:48:12.599> all<00:48:12.780> in<00:48:12.900> the<00:48:13.020> same<00:48:13.140> single<00:48:13.560> address<00:48:13.619> yes 00:48:13.970 --> 00:48:13.980 align:start position:0% them all in the same single address yes 00:48:13.980 --> 00:48:15.170 align:start position:0% them all in the same single address yes you<00:48:14.099> will<00:48:14.220> be<00:48:14.280> able<00:48:14.400> to<00:48:14.460> do<00:48:14.579> it<00:48:14.700> with<00:48:14.819> a<00:48:14.940> counter 00:48:15.170 --> 00:48:15.180 align:start position:0% you will be able to do it with a counter 00:48:15.180 --> 00:48:16.010 align:start position:0% you will be able to do it with a counter fraction 00:48:16.010 --> 00:48:16.020 align:start position:0% fraction 00:48:16.020 --> 00:48:18.410 align:start position:0% fraction probably<00:48:16.500> you<00:48:16.859> still<00:48:17.400> might<00:48:17.579> have<00:48:17.760> multiple 00:48:18.410 --> 00:48:18.420 align:start position:0% probably you still might have multiple 00:48:18.420 --> 00:48:19.849 align:start position:0% probably you still might have multiple abstracted<00:48:19.140> accounts<00:48:19.500> for<00:48:19.740> different 00:48:19.849 --> 00:48:19.859 align:start position:0% abstracted accounts for different 00:48:19.859 --> 00:48:23.270 align:start position:0% abstracted accounts for different purposes<00:48:20.339> but<00:48:21.000> for<00:48:21.359> different<00:48:21.720> reasons<00:48:22.140> if<00:48:22.619> if 00:48:23.270 --> 00:48:23.280 align:start position:0% purposes but for different reasons if if 00:48:23.280 --> 00:48:24.829 align:start position:0% purposes but for different reasons if if the<00:48:23.520> reason<00:48:23.700> to<00:48:23.940> have<00:48:24.060> multiple<00:48:24.300> addresses<00:48:24.720> is 00:48:24.829 --> 00:48:24.839 align:start position:0% the reason to have multiple addresses is 00:48:24.839 --> 00:48:26.630 align:start position:0% the reason to have multiple addresses is only<00:48:25.020> security<00:48:25.319> then<00:48:25.920> yes<00:48:26.099> you<00:48:26.339> will<00:48:26.460> be<00:48:26.520> able 00:48:26.630 --> 00:48:26.640 align:start position:0% only security then yes you will be able 00:48:26.640 --> 00:48:29.210 align:start position:0% only security then yes you will be able to<00:48:26.760> use<00:48:26.880> a<00:48:27.599> abstracted<00:48:28.200> account 00:48:29.210 --> 00:48:29.220 align:start position:0% to use a abstracted account 00:48:29.220 --> 00:48:31.609 align:start position:0% to use a abstracted account to<00:48:29.640> find<00:48:29.760> something<00:48:30.000> that<00:48:30.480> can<00:48:30.599> cover<00:48:31.079> all<00:48:31.380> the 00:48:31.609 --> 00:48:31.619 align:start position:0% to find something that can cover all the 00:48:31.619 --> 00:48:33.410 align:start position:0% to find something that can cover all the all<00:48:31.920> bases<00:48:32.339> yeah<00:48:32.700> because<00:48:32.880> you<00:48:33.240> can<00:48:33.300> just 00:48:33.410 --> 00:48:33.420 align:start position:0% all bases yeah because you can just 00:48:33.420 --> 00:48:35.930 align:start position:0% all bases yeah because you can just limit<00:48:33.660> your<00:48:33.900> risk<00:48:34.260> exposure<00:48:34.680> to<00:48:35.520> each<00:48:35.700> device 00:48:35.930 --> 00:48:35.940 align:start position:0% limit your risk exposure to each device 00:48:35.940 --> 00:48:39.170 align:start position:0% limit your risk exposure to each device depending<00:48:36.599> on<00:48:36.660> how<00:48:36.900> much<00:48:36.960> you<00:48:37.140> trust<00:48:37.319> it<00:48:37.980> again 00:48:39.170 --> 00:48:39.180 align:start position:0% depending on how much you trust it again 00:48:39.180 --> 00:48:40.970 align:start position:0% depending on how much you trust it again I'm<00:48:39.660> not<00:48:39.780> saying<00:48:40.140> that<00:48:40.260> there<00:48:40.500> will<00:48:40.680> be<00:48:40.740> one 00:48:40.970 --> 00:48:40.980 align:start position:0% I'm not saying that there will be one 00:48:40.980 --> 00:48:42.470 align:start position:0% I'm not saying that there will be one wallet<00:48:41.339> it<00:48:41.460> will<00:48:41.579> give<00:48:41.819> you<00:48:41.940> all<00:48:42.119> these<00:48:42.359> use 00:48:42.470 --> 00:48:42.480 align:start position:0% wallet it will give you all these use 00:48:42.480 --> 00:48:45.170 align:start position:0% wallet it will give you all these use cases<00:48:42.780> you'll<00:48:43.500> find<00:48:43.740> a<00:48:44.040> wallet<00:48:44.400> that<00:48:44.640> give<00:48:45.000> you 00:48:45.170 --> 00:48:45.180 align:start position:0% cases you'll find a wallet that give you 00:48:45.180 --> 00:48:46.910 align:start position:0% cases you'll find a wallet that give you all<00:48:45.359> the<00:48:45.480> user's<00:48:45.780> case<00:48:45.900> you<00:48:46.079> need 00:48:46.910 --> 00:48:46.920 align:start position:0% all the user's case you need 00:48:46.920 --> 00:48:49.130 align:start position:0% all the user's case you need and<00:48:47.700> use<00:48:48.119> that 00:48:49.130 --> 00:48:49.140 align:start position:0% and use that 00:48:49.140 --> 00:48:51.170 align:start position:0% and use that and<00:48:49.619> you<00:48:49.800> always<00:48:49.980> can<00:48:50.220> switch 00:48:51.170 --> 00:48:51.180 align:start position:0% and you always can switch 00:48:51.180 --> 00:48:53.210 align:start position:0% and you always can switch I<00:48:51.540> think<00:48:51.599> the<00:48:51.720> the 00:48:53.210 --> 00:48:53.220 align:start position:0% I think the the 00:48:53.220 --> 00:48:56.089 align:start position:0% I think the the first<00:48:53.940> use<00:48:54.180> case<00:48:54.359> of<00:48:54.660> a<00:48:54.780> signature<00:48:55.260> is<00:48:55.740> chain 00:48:56.089 --> 00:48:56.099 align:start position:0% first use case of a signature is chain 00:48:56.099 --> 00:48:57.710 align:start position:0% first use case of a signature is chain signature<00:48:56.640> just<00:48:56.940> think<00:48:57.180> of<00:48:57.300> it<00:48:57.420> you<00:48:57.540> start 00:48:57.710 --> 00:48:57.720 align:start position:0% signature just think of it you start 00:48:57.720 --> 00:49:00.950 align:start position:0% signature just think of it you start using<00:48:58.079> metamask<00:48:58.700> and<00:48:59.700> after<00:49:00.000> a<00:49:00.300> few<00:49:00.480> years<00:49:00.660> you 00:49:00.950 --> 00:49:00.960 align:start position:0% using metamask and after a few years you 00:49:00.960 --> 00:49:02.510 align:start position:0% using metamask and after a few years you collected<00:49:01.319> a<00:49:01.440> lot<00:49:01.500> of<00:49:01.560> nfts<00:49:02.099> and<00:49:02.220> a<00:49:02.280> lot<00:49:02.400> of 00:49:02.510 --> 00:49:02.520 align:start position:0% collected a lot of nfts and a lot of 00:49:02.520 --> 00:49:04.849 align:start position:0% collected a lot of nfts and a lot of money<00:49:02.700> but<00:49:03.660> you<00:49:04.200> can't<00:49:04.319> change<00:49:04.560> the<00:49:04.680> security 00:49:04.849 --> 00:49:04.859 align:start position:0% money but you can't change the security 00:49:04.859 --> 00:49:06.170 align:start position:0% money but you can't change the security model 00:49:06.170 --> 00:49:06.180 align:start position:0% model 00:49:06.180 --> 00:49:09.050 align:start position:0% model your<00:49:06.780> browser<00:49:07.200> holds<00:49:07.800> your<00:49:07.980> private<00:49:08.280> key<00:49:08.460> so 00:49:09.050 --> 00:49:09.060 align:start position:0% your browser holds your private key so 00:49:09.060 --> 00:49:10.490 align:start position:0% your browser holds your private key so you<00:49:09.300> have<00:49:09.420> no<00:49:09.540> idea<00:49:09.780> if<00:49:09.900> anyone<00:49:10.140> hacked<00:49:10.440> into 00:49:10.490 --> 00:49:10.500 align:start position:0% you have no idea if anyone hacked into 00:49:10.500 --> 00:49:12.349 align:start position:0% you have no idea if anyone hacked into your<00:49:10.740> computer<00:49:10.859> and<00:49:11.160> grabbed<00:49:11.579> it<00:49:11.760> through<00:49:12.180> a 00:49:12.349 --> 00:49:12.359 align:start position:0% your computer and grabbed it through a 00:49:12.359 --> 00:49:14.270 align:start position:0% your computer and grabbed it through a copy<00:49:12.599> of<00:49:12.660> your<00:49:12.780> computer<00:49:12.960> without<00:49:13.800> changing 00:49:14.270 --> 00:49:14.280 align:start position:0% copy of your computer without changing 00:49:14.280 --> 00:49:15.470 align:start position:0% copy of your computer without changing the<00:49:14.460> address<00:49:14.579> you<00:49:14.880> can<00:49:15.000> change<00:49:15.119> the<00:49:15.300> security 00:49:15.470 --> 00:49:15.480 align:start position:0% the address you can change the security 00:49:15.480 --> 00:49:17.210 align:start position:0% the address you can change the security with<00:49:16.140> account<00:49:16.260> obstruction<00:49:16.680> with<00:49:16.920> single 00:49:17.210 --> 00:49:17.220 align:start position:0% with account obstruction with single 00:49:17.220 --> 00:49:20.870 align:start position:0% with account obstruction with single operation<00:49:17.520> of<00:49:18.060> change<00:49:18.720> owner<00:49:19.500> now<00:49:20.220> the<00:49:20.520> trays 00:49:20.870 --> 00:49:20.880 align:start position:0% operation of change owner now the trays 00:49:20.880 --> 00:49:23.990 align:start position:0% operation of change owner now the trays are<00:49:21.000> on<00:49:21.240> the<00:49:21.780> same<00:49:21.960> account<00:49:22.160> even<00:49:23.160> if<00:49:23.400> with<00:49:23.700> the 00:49:23.990 --> 00:49:24.000 align:start position:0% are on the same account even if with the 00:49:24.000 --> 00:49:26.390 align:start position:0% are on the same account even if with the basic<00:49:24.420> simple<00:49:24.720> account<00:49:25.200> I<00:49:25.619> just<00:49:25.859> changed<00:49:26.339> the 00:49:26.390 --> 00:49:26.400 align:start position:0% basic simple account I just changed the 00:49:26.400 --> 00:49:28.430 align:start position:0% basic simple account I just changed the owner<00:49:26.700> and<00:49:27.300> now<00:49:27.480> I<00:49:27.660> am<00:49:27.839> really<00:49:27.960> secured 00:49:28.430 --> 00:49:28.440 align:start position:0% owner and now I am really secured 00:49:28.440 --> 00:49:30.710 align:start position:0% owner and now I am really secured because<00:49:28.680> the<00:49:29.280> previous<00:49:29.460> private<00:49:30.240> key<00:49:30.359> is<00:49:30.480> no 00:49:30.710 --> 00:49:30.720 align:start position:0% because the previous private key is no 00:49:30.720 --> 00:49:32.690 align:start position:0% because the previous private key is no longer<00:49:30.960> relevant<00:49:31.440> yeah<00:49:31.800> even<00:49:31.980> before<00:49:32.220> you<00:49:32.520> get 00:49:32.690 --> 00:49:32.700 align:start position:0% longer relevant yeah even before you get 00:49:32.700 --> 00:49:34.910 align:start position:0% longer relevant yeah even before you get into<00:49:32.880> the<00:49:33.119> really<00:49:33.540> fancy<00:49:34.020> stuff<00:49:34.260> that<00:49:34.680> you<00:49:34.800> can 00:49:34.910 --> 00:49:34.920 align:start position:0% into the really fancy stuff that you can 00:49:34.920 --> 00:49:36.950 align:start position:0% into the really fancy stuff that you can do<00:49:34.980> with<00:49:35.220> the<00:49:35.400> abstract<00:49:35.819> account<00:49:36.480> abstraction 00:49:36.950 --> 00:49:36.960 align:start position:0% do with the abstract account abstraction 00:49:36.960 --> 00:49:40.550 align:start position:0% do with the abstract account abstraction the<00:49:37.740> basics<00:49:38.160> are<00:49:38.460> actually<00:49:38.880> pretty 00:49:40.550 --> 00:49:40.560 align:start position:0% the basics are actually pretty 00:49:40.560 --> 00:49:42.829 align:start position:0% the basics are actually pretty um<00:49:40.619> pretty<00:49:41.099> useful<00:49:41.940> just<00:49:42.240> by<00:49:42.420> themselves 00:49:42.829 --> 00:49:42.839 align:start position:0% um pretty useful just by themselves 00:49:42.839 --> 00:49:45.170 align:start position:0% um pretty useful just by themselves because<00:49:43.260> right<00:49:43.619> now<00:49:43.800> if<00:49:44.280> anything<00:49:44.460> goes<00:49:45.000> wrong 00:49:45.170 --> 00:49:45.180 align:start position:0% because right now if anything goes wrong 00:49:45.180 --> 00:49:47.210 align:start position:0% because right now if anything goes wrong then<00:49:45.960> it's<00:49:46.200> really<00:49:46.380> hard<00:49:46.560> to<00:49:46.800> transfer 00:49:47.210 --> 00:49:47.220 align:start position:0% then it's really hard to transfer 00:49:47.220 --> 00:49:49.609 align:start position:0% then it's really hard to transfer everything<00:49:47.460> from<00:49:47.940> from<00:49:48.359> one<00:49:48.720> eoa<00:49:49.260> to<00:49:49.440> another 00:49:49.609 --> 00:49:49.619 align:start position:0% everything from from one eoa to another 00:49:49.619 --> 00:49:52.510 align:start position:0% everything from from one eoa to another I<00:49:50.339> mean<00:49:50.520> you<00:49:50.640> would<00:49:50.760> have<00:49:50.880> to<00:49:51.180> create<00:49:51.540> separate 00:49:52.510 --> 00:49:52.520 align:start position:0% I mean you would have to create separate 00:49:52.520 --> 00:49:54.589 align:start position:0% I mean you would have to create separate transactions<00:49:53.520> for<00:49:53.819> each<00:49:53.940> asset<00:49:54.359> that<00:49:54.480> you 00:49:54.589 --> 00:49:54.599 align:start position:0% transactions for each asset that you 00:49:54.599 --> 00:49:57.170 align:start position:0% transactions for each asset that you hold<00:49:54.720> that<00:49:55.020> could<00:49:55.140> be<00:49:55.260> pretty<00:49:55.440> expensive 00:49:57.170 --> 00:49:57.180 align:start position:0% hold that could be pretty expensive 00:49:57.180 --> 00:49:59.270 align:start position:0% hold that could be pretty expensive um<00:49:57.240> and<00:49:57.599> if<00:49:58.079> your<00:49:58.260> computer<00:49:58.440> got<00:49:58.680> compromised 00:49:59.270 --> 00:49:59.280 align:start position:0% um and if your computer got compromised 00:49:59.280 --> 00:50:00.650 align:start position:0% um and if your computer got compromised you<00:49:59.400> might<00:49:59.579> need<00:49:59.700> to<00:49:59.819> do<00:49:59.940> that<00:50:00.119> in<00:50:00.300> a<00:50:00.420> huge 00:50:00.650 --> 00:50:00.660 align:start position:0% you might need to do that in a huge 00:50:00.660 --> 00:50:04.790 align:start position:0% you might need to do that in a huge hurry<00:50:01.500> you<00:50:02.040> know<00:50:02.420> so<00:50:03.420> it's<00:50:04.020> it's 00:50:04.790 --> 00:50:04.800 align:start position:0% hurry you know so it's it's 00:50:04.800 --> 00:50:06.410 align:start position:0% hurry you know so it's it's um it's<00:50:05.339> just<00:50:05.460> not<00:50:05.579> not<00:50:05.760> the<00:50:05.940> best<00:50:06.060> situation 00:50:06.410 --> 00:50:06.420 align:start position:0% um it's just not not the best situation 00:50:06.420 --> 00:50:09.230 align:start position:0% um it's just not not the best situation to<00:50:06.660> be<00:50:06.780> in<00:50:06.960> even<00:50:07.619> very<00:50:07.980> simple<00:50:08.280> improvements 00:50:09.230 --> 00:50:09.240 align:start position:0% to be in even very simple improvements 00:50:09.240 --> 00:50:12.380 align:start position:0% to be in even very simple improvements like<00:50:09.420> this<00:50:09.540> will<00:50:09.780> make<00:50:09.960> a<00:50:10.079> big<00:50:10.200> difference