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:14.390 align:start position:0% [Music] 00:00:14.390 --> 00:00:14.400 align:start position:0% 00:00:14.400 --> 00:00:16.790 align:start position:0% itos<00:00:15.360> and<00:00:15.599> welcome<00:00:15.719> everybody<00:00:16.020> how's 00:00:16.790 --> 00:00:16.800 align:start position:0% itos and welcome everybody how's 00:00:16.800 --> 00:00:19.130 align:start position:0% itos and welcome everybody how's everyone<00:00:16.980> doing<00:00:17.279> today 00:00:19.130 --> 00:00:19.140 align:start position:0% everyone doing today 00:00:19.140 --> 00:00:21.410 align:start position:0% everyone doing today nice 00:00:21.410 --> 00:00:21.420 align:start position:0% nice 00:00:21.420 --> 00:00:22.790 align:start position:0% nice all<00:00:21.840> right 00:00:22.790 --> 00:00:22.800 align:start position:0% all right 00:00:22.800 --> 00:00:25.609 align:start position:0% all right I'm<00:00:23.220> Jacob<00:00:23.640> montowski<00:00:24.420> I'm<00:00:24.660> a<00:00:24.779> developer<00:00:25.140> on 00:00:25.609 --> 00:00:25.619 align:start position:0% I'm Jacob montowski I'm a developer on 00:00:25.619 --> 00:00:27.470 align:start position:0% I'm Jacob montowski I'm a developer on the<00:00:25.800> BLS<00:00:26.279> wallet<00:00:26.640> project<00:00:26.760> and<00:00:27.060> here<00:00:27.180> with<00:00:27.300> me 00:00:27.470 --> 00:00:27.480 align:start position:0% the BLS wallet project and here with me 00:00:27.480 --> 00:00:29.870 align:start position:0% the BLS wallet project and here with me today<00:00:27.660> is<00:00:28.019> James<00:00:28.260> Zacky<00:00:28.800> who<00:00:28.980> is<00:00:29.160> our<00:00:29.340> uh 00:00:29.870 --> 00:00:29.880 align:start position:0% today is James Zacky who is our uh 00:00:29.880 --> 00:00:32.389 align:start position:0% today is James Zacky who is our uh Project<00:00:30.300> Lead<00:00:30.740> and<00:00:31.740> we're<00:00:31.980> going<00:00:32.160> to<00:00:32.279> talk 00:00:32.389 --> 00:00:32.399 align:start position:0% Project Lead and we're going to talk 00:00:32.399 --> 00:00:34.910 align:start position:0% Project Lead and we're going to talk about<00:00:32.700> BLS<00:00:33.300> wallet 00:00:34.910 --> 00:00:34.920 align:start position:0% about BLS wallet 00:00:34.920 --> 00:00:36.530 align:start position:0% about BLS wallet anyways<00:00:35.640> what<00:00:35.820> we're<00:00:35.940> going<00:00:36.059> to<00:00:36.120> cover<00:00:36.239> today 00:00:36.530 --> 00:00:36.540 align:start position:0% anyways what we're going to cover today 00:00:36.540 --> 00:00:38.750 align:start position:0% anyways what we're going to cover today when<00:00:36.960> the<00:00:37.200> next<00:00:37.320> slide<00:00:37.620> pops<00:00:38.040> up<00:00:38.160> is<00:00:38.579> we're 00:00:38.750 --> 00:00:38.760 align:start position:0% when the next slide pops up is we're 00:00:38.760 --> 00:00:40.850 align:start position:0% when the next slide pops up is we're going<00:00:38.880> to<00:00:38.940> go<00:00:39.059> over<00:00:39.180> at<00:00:39.420> a<00:00:39.540> high<00:00:39.660> level<00:00:39.860> the 00:00:40.850 --> 00:00:40.860 align:start position:0% going to go over at a high level the 00:00:40.860 --> 00:00:42.889 align:start position:0% going to go over at a high level the team<00:00:40.980> and<00:00:41.219> project<00:00:41.460> outcomes<00:00:42.000> a<00:00:42.660> little<00:00:42.780> bit 00:00:42.889 --> 00:00:42.899 align:start position:0% team and project outcomes a little bit 00:00:42.899 --> 00:00:44.330 align:start position:0% team and project outcomes a little bit on<00:00:43.020> the<00:00:43.200> basics<00:00:43.440> in<00:00:43.680> a<00:00:43.739> high<00:00:43.860> level<00:00:43.980> overview 00:00:44.330 --> 00:00:44.340 align:start position:0% on the basics in a high level overview 00:00:44.340 --> 00:00:48.110 align:start position:0% on the basics in a high level overview of<00:00:44.520> BLS<00:00:44.940> signatures<00:00:45.360> and<00:00:45.540> aggregation 00:00:48.110 --> 00:00:48.120 align:start position:0% 00:00:48.120 --> 00:00:49.610 align:start position:0% we're<00:00:48.480> then<00:00:48.660> going<00:00:48.840> to<00:00:48.960> cover 00:00:49.610 --> 00:00:49.620 align:start position:0% we're then going to cover 00:00:49.620 --> 00:00:51.709 align:start position:0% we're then going to cover um where<00:00:49.800> BLS<00:00:50.280> wallet<00:00:50.579> is<00:00:50.760> today<00:00:51.000> with<00:00:51.539> some 00:00:51.709 --> 00:00:51.719 align:start position:0% um where BLS wallet is today with some 00:00:51.719 --> 00:00:53.209 align:start position:0% um where BLS wallet is today with some examples<00:00:52.140> and<00:00:52.440> some<00:00:52.620> of<00:00:52.680> the<00:00:52.800> features<00:00:53.039> we 00:00:53.209 --> 00:00:53.219 align:start position:0% examples and some of the features we 00:00:53.219 --> 00:00:54.590 align:start position:0% examples and some of the features we have<00:00:53.340> built<00:00:53.700> in 00:00:54.590 --> 00:00:54.600 align:start position:0% have built in 00:00:54.600 --> 00:00:56.510 align:start position:0% have built in and<00:00:54.719> then<00:00:55.140> we're<00:00:55.440> going<00:00:55.559> to<00:00:55.620> cover<00:00:55.920> where 00:00:56.510 --> 00:00:56.520 align:start position:0% and then we're going to cover where 00:00:56.520 --> 00:00:58.549 align:start position:0% and then we're going to cover where we're<00:00:56.640> going<00:00:56.820> next<00:00:57.059> with<00:00:57.360> the<00:00:57.480> project<00:00:57.660> and 00:00:58.549 --> 00:00:58.559 align:start position:0% we're going next with the project and 00:00:58.559 --> 00:01:00.110 align:start position:0% we're going next with the project and finally<00:00:58.800> we<00:00:59.039> should<00:00:59.160> have<00:00:59.280> ample<00:00:59.640> time<00:00:59.820> for 00:01:00.110 --> 00:01:00.120 align:start position:0% finally we should have ample time for 00:01:00.120 --> 00:01:03.650 align:start position:0% finally we should have ample time for questions 00:01:03.650 --> 00:01:03.660 align:start position:0% 00:01:03.660 --> 00:01:05.450 align:start position:0% so<00:01:04.199> we'll<00:01:04.440> kind<00:01:04.619> of<00:01:04.739> go<00:01:04.799> over<00:01:04.860> the<00:01:05.040> team<00:01:05.220> and 00:01:05.450 --> 00:01:05.460 align:start position:0% so we'll kind of go over the team and 00:01:05.460 --> 00:01:08.570 align:start position:0% so we'll kind of go over the team and some<00:01:05.580> project<00:01:05.760> outcomes<00:01:06.180> to<00:01:06.420> start 00:01:08.570 --> 00:01:08.580 align:start position:0% some project outcomes to start 00:01:08.580 --> 00:01:11.030 align:start position:0% some project outcomes to start this<00:01:09.119> is<00:01:09.299> our<00:01:09.540> wonderful<00:01:09.960> team 00:01:11.030 --> 00:01:11.040 align:start position:0% this is our wonderful team 00:01:11.040 --> 00:01:13.609 align:start position:0% this is our wonderful team right<00:01:11.340> here<00:01:11.520> off<00:01:12.240> of<00:01:12.479> it<00:01:12.600> off<00:01:13.140> little<00:01:13.380> that's 00:01:13.609 --> 00:01:13.619 align:start position:0% right here off of it off little that's 00:01:13.619 --> 00:01:15.410 align:start position:0% right here off of it off little that's okay 00:01:15.410 --> 00:01:15.420 align:start position:0% okay 00:01:15.420 --> 00:01:17.450 align:start position:0% okay um<00:01:15.540> we're<00:01:16.200> scattered<00:01:16.560> all<00:01:16.740> across<00:01:17.100> the<00:01:17.220> globe 00:01:17.450 --> 00:01:17.460 align:start position:0% um we're scattered all across the globe 00:01:17.460 --> 00:01:18.950 align:start position:0% um we're scattered all across the globe we're<00:01:17.760> part<00:01:17.939> of<00:01:18.060> the<00:01:18.119> privacy<00:01:18.420> and<00:01:18.600> scaling 00:01:18.950 --> 00:01:18.960 align:start position:0% we're part of the privacy and scaling 00:01:18.960 --> 00:01:20.630 align:start position:0% we're part of the privacy and scaling Explorations<00:01:19.500> Group<00:01:19.799> which<00:01:20.100> is<00:01:20.159> a<00:01:20.340> subgroup 00:01:20.630 --> 00:01:20.640 align:start position:0% Explorations Group which is a subgroup 00:01:20.640 --> 00:01:22.130 align:start position:0% Explorations Group which is a subgroup of<00:01:20.820> the<00:01:20.880> ethereum<00:01:21.299> foundation<00:01:21.659> we<00:01:22.020> work 00:01:22.130 --> 00:01:22.140 align:start position:0% of the ethereum foundation we work 00:01:22.140 --> 00:01:23.630 align:start position:0% of the ethereum foundation we work mainly<00:01:22.500> with<00:01:22.680> zero<00:01:22.920> knowledge<00:01:23.159> proofs<00:01:23.520> and 00:01:23.630 --> 00:01:23.640 align:start position:0% mainly with zero knowledge proofs and 00:01:23.640 --> 00:01:27.170 align:start position:0% mainly with zero knowledge proofs and layers<00:01:23.880> get<00:01:24.119> layer<00:01:24.960> 2<00:01:25.080> scaling<00:01:25.619> technology 00:01:27.170 --> 00:01:27.180 align:start position:0% layers get layer 2 scaling technology 00:01:27.180 --> 00:01:28.910 align:start position:0% layers get layer 2 scaling technology um<00:01:27.299> our<00:01:27.540> goal<00:01:27.780> is<00:01:27.840> to<00:01:28.020> bring<00:01:28.140> more<00:01:28.320> privacy<00:01:28.740> and 00:01:28.910 --> 00:01:28.920 align:start position:0% um our goal is to bring more privacy and 00:01:28.920 --> 00:01:30.710 align:start position:0% um our goal is to bring more privacy and scalability<00:01:29.400> to<00:01:29.640> the<00:01:29.820> ethereum<00:01:30.240> blockchain 00:01:30.710 --> 00:01:30.720 align:start position:0% scalability to the ethereum blockchain 00:01:30.720 --> 00:01:34.670 align:start position:0% scalability to the ethereum blockchain system 00:01:34.670 --> 00:01:34.680 align:start position:0% 00:01:34.680 --> 00:01:36.230 align:start position:0% so 00:01:36.230 --> 00:01:36.240 align:start position:0% so 00:01:36.240 --> 00:01:37.850 align:start position:0% so cut<00:01:36.600> some<00:01:36.840> of<00:01:36.960> the<00:01:37.020> outcomes<00:01:37.259> we<00:01:37.439> want<00:01:37.619> to<00:01:37.740> try 00:01:37.850 --> 00:01:37.860 align:start position:0% cut some of the outcomes we want to try 00:01:37.860 --> 00:01:40.429 align:start position:0% cut some of the outcomes we want to try to<00:01:37.979> reach<00:01:38.280> with<00:01:38.939> our<00:01:39.360> project<00:01:39.720> and<00:01:40.259> the 00:01:40.429 --> 00:01:40.439 align:start position:0% to reach with our project and the 00:01:40.439 --> 00:01:42.770 align:start position:0% to reach with our project and the primary<00:01:40.680> one<00:01:40.920> are<00:01:41.400> North<00:01:41.640> Star<00:01:41.939> or<00:01:42.479> here<00:01:42.659> in 00:01:42.770 --> 00:01:42.780 align:start position:0% primary one are North Star or here in 00:01:42.780 --> 00:01:43.850 align:start position:0% primary one are North Star or here in the<00:01:42.840> southern<00:01:42.960> hemisphere<00:01:43.439> the<00:01:43.740> Southern 00:01:43.850 --> 00:01:43.860 align:start position:0% the southern hemisphere the Southern 00:01:43.860 --> 00:01:47.330 align:start position:0% the southern hemisphere the Southern Cross<00:01:44.220> is<00:01:45.119> going<00:01:45.240> to<00:01:45.360> be<00:01:45.479> reduce<00:01:45.780> the<00:01:46.500> uh<00:01:47.040> the 00:01:47.330 --> 00:01:47.340 align:start position:0% Cross is going to be reduce the uh the 00:01:47.340 --> 00:01:50.149 align:start position:0% Cross is going to be reduce the uh the cost<00:01:47.520> of<00:01:47.820> L2<00:01:48.180> transactions<00:01:49.020> primarily<00:01:49.920> by 00:01:50.149 --> 00:01:50.159 align:start position:0% cost of L2 transactions primarily by 00:01:50.159 --> 00:01:52.429 align:start position:0% cost of L2 transactions primarily by reducing<00:01:50.640> the<00:01:51.060> amount<00:01:51.299> of<00:01:51.479> data<00:01:51.840> that<00:01:52.320> is 00:01:52.429 --> 00:01:52.439 align:start position:0% reducing the amount of data that is 00:01:52.439 --> 00:01:54.050 align:start position:0% reducing the amount of data that is rolled<00:01:52.740> up<00:01:52.799> into<00:01:52.979> l1s<00:01:53.579> by<00:01:53.700> reducing 00:01:54.050 --> 00:01:54.060 align:start position:0% rolled up into l1s by reducing 00:01:54.060 --> 00:01:57.770 align:start position:0% rolled up into l1s by reducing transaction<00:01:54.600> size 00:01:57.770 --> 00:01:57.780 align:start position:0% 00:01:57.780 --> 00:02:00.370 align:start position:0% currently<00:01:58.560> with<00:01:58.860> some<00:01:59.040> initial<00:01:59.520> numbers 00:02:00.370 --> 00:02:00.380 align:start position:0% currently with some initial numbers 00:02:00.380 --> 00:02:02.510 align:start position:0% currently with some initial numbers uh<00:02:01.380> which<00:02:01.619> are<00:02:01.680> a<00:02:01.799> little<00:02:01.860> difficult<00:02:02.159> to<00:02:02.340> see 00:02:02.510 --> 00:02:02.520 align:start position:0% uh which are a little difficult to see 00:02:02.520 --> 00:02:04.429 align:start position:0% uh which are a little difficult to see right<00:02:02.759> now<00:02:02.939> we've<00:02:03.720> essentially<00:02:04.020> simulated 00:02:04.429 --> 00:02:04.439 align:start position:0% right now we've essentially simulated 00:02:04.439 --> 00:02:07.249 align:start position:0% right now we've essentially simulated running<00:02:04.680> 150<00:02:05.460> erc20<00:02:06.180> transfers<00:02:06.780> both 00:02:07.249 --> 00:02:07.259 align:start position:0% running 150 erc20 transfers both 00:02:07.259 --> 00:02:10.070 align:start position:0% running 150 erc20 transfers both regularly<00:02:07.920> normally<00:02:08.340> on<00:02:08.700> a<00:02:08.940> roll-up<00:02:09.300> as<00:02:09.959> well 00:02:10.070 --> 00:02:10.080 align:start position:0% regularly normally on a roll-up as well 00:02:10.080 --> 00:02:11.750 align:start position:0% regularly normally on a roll-up as well as<00:02:10.200> bundling<00:02:10.619> them<00:02:10.860> all<00:02:10.979> together<00:02:11.160> into<00:02:11.459> a 00:02:11.750 --> 00:02:11.760 align:start position:0% as bundling them all together into a 00:02:11.760 --> 00:02:14.449 align:start position:0% as bundling them all together into a single<00:02:12.000> L2<00:02:12.420> transaction<00:02:12.959> using<00:02:13.560> BLS<00:02:13.980> wallet 00:02:14.449 --> 00:02:14.459 align:start position:0% single L2 transaction using BLS wallet 00:02:14.459 --> 00:02:16.610 align:start position:0% single L2 transaction using BLS wallet and<00:02:15.060> we've<00:02:15.239> gotten<00:02:15.599> it<00:02:15.720> down<00:02:15.900> the<00:02:16.319> transaction 00:02:16.610 --> 00:02:16.620 align:start position:0% and we've gotten it down the transaction 00:02:16.620 --> 00:02:19.490 align:start position:0% and we've gotten it down the transaction data<00:02:17.099> size<00:02:17.220> by<00:02:17.520> about<00:02:17.640> a<00:02:17.879> quarter 00:02:19.490 --> 00:02:19.500 align:start position:0% data size by about a quarter 00:02:19.500 --> 00:02:21.949 align:start position:0% data size by about a quarter um<00:02:19.620> we're<00:02:19.920> hoping<00:02:20.400> that<00:02:20.760> we<00:02:20.940> can<00:02:21.060> go<00:02:21.300> even 00:02:21.949 --> 00:02:21.959 align:start position:0% um we're hoping that we can go even 00:02:21.959 --> 00:02:24.830 align:start position:0% um we're hoping that we can go even further<00:02:22.379> than<00:02:22.620> that<00:02:23.060> uh<00:02:24.060> we<00:02:24.480> still<00:02:24.599> need<00:02:24.780> to 00:02:24.830 --> 00:02:24.840 align:start position:0% further than that uh we still need to 00:02:24.840 --> 00:02:26.270 align:start position:0% further than that uh we still need to measure<00:02:25.140> the<00:02:25.440> impact<00:02:25.739> that<00:02:25.920> we're<00:02:26.040> going<00:02:26.160> to 00:02:26.270 --> 00:02:26.280 align:start position:0% measure the impact that we're going to 00:02:26.280 --> 00:02:28.729 align:start position:0% measure the impact that we're going to have<00:02:26.400> on<00:02:26.940> layer<00:02:27.360> 1<00:02:27.480> gas<00:02:27.780> costs<00:02:28.140> to<00:02:28.319> see<00:02:28.440> how<00:02:28.620> the 00:02:28.729 --> 00:02:28.739 align:start position:0% have on layer 1 gas costs to see how the 00:02:28.739 --> 00:02:30.110 align:start position:0% have on layer 1 gas costs to see how the transactions<00:02:29.340> are<00:02:29.459> actually<00:02:29.640> going<00:02:29.879> to<00:02:30.000> be 00:02:30.110 --> 00:02:30.120 align:start position:0% transactions are actually going to be 00:02:30.120 --> 00:02:31.970 align:start position:0% transactions are actually going to be reduced 00:02:31.970 --> 00:02:31.980 align:start position:0% reduced 00:02:31.980 --> 00:02:34.670 align:start position:0% reduced um<00:02:32.040> but<00:02:32.640> our<00:02:33.060> team<00:02:33.239> likes<00:02:33.720> to<00:02:33.840> limbo<00:02:34.200> and<00:02:34.500> we 00:02:34.670 --> 00:02:34.680 align:start position:0% um but our team likes to limbo and we 00:02:34.680 --> 00:02:36.710 align:start position:0% um but our team likes to limbo and we want<00:02:34.800> to<00:02:34.920> see<00:02:35.040> how<00:02:35.340> low<00:02:35.520> can<00:02:35.760> we<00:02:35.940> go 00:02:36.710 --> 00:02:36.720 align:start position:0% want to see how low can we go 00:02:36.720 --> 00:02:38.330 align:start position:0% want to see how low can we go with<00:02:37.080> using<00:02:37.379> some<00:02:37.500> things<00:02:37.620> involving<00:02:38.099> address 00:02:38.330 --> 00:02:38.340 align:start position:0% with using some things involving address 00:02:38.340 --> 00:02:39.530 align:start position:0% with using some things involving address books 00:02:39.530 --> 00:02:39.540 align:start position:0% books 00:02:39.540 --> 00:02:40.790 align:start position:0% books um<00:02:39.599> as<00:02:39.720> well<00:02:39.840> as<00:02:39.959> some<00:02:40.080> other<00:02:40.260> indexing<00:02:40.680> things 00:02:40.790 --> 00:02:40.800 align:start position:0% um as well as some other indexing things 00:02:40.800 --> 00:02:43.130 align:start position:0% um as well as some other indexing things to<00:02:40.980> reduce<00:02:41.160> that<00:02:41.400> call<00:02:41.580> data<00:02:42.000> even<00:02:42.300> lower<00:02:42.599> than 00:02:43.130 --> 00:02:43.140 align:start position:0% to reduce that call data even lower than 00:02:43.140 --> 00:02:45.830 align:start position:0% to reduce that call data even lower than uh<00:02:43.440> where<00:02:43.680> it's<00:02:43.800> at<00:02:44.459> we'll<00:02:44.879> get<00:02:45.000> into<00:02:45.599> um<00:02:45.599> how 00:02:45.830 --> 00:02:45.840 align:start position:0% uh where it's at we'll get into um how 00:02:45.840 --> 00:02:49.550 align:start position:0% uh where it's at we'll get into um how we<00:02:45.959> reduce<00:02:46.260> that<00:02:46.620> size<00:02:46.860> in<00:02:47.160> a<00:02:47.280> moment 00:02:49.550 --> 00:02:49.560 align:start position:0% 00:02:49.560 --> 00:02:52.070 align:start position:0% so<00:02:50.040> another<00:02:50.340> outcome<00:02:50.700> we're<00:02:50.819> looking<00:02:51.060> for<00:02:51.300> is 00:02:52.070 --> 00:02:52.080 align:start position:0% so another outcome we're looking for is 00:02:52.080 --> 00:02:54.410 align:start position:0% so another outcome we're looking for is to<00:02:52.260> be<00:02:52.379> able<00:02:52.500> to<00:02:52.739> improve<00:02:53.099> wallets 00:02:54.410 --> 00:02:54.420 align:start position:0% to be able to improve wallets 00:02:54.420 --> 00:02:55.550 align:start position:0% to be able to improve wallets um one<00:02:54.660> of<00:02:54.720> the<00:02:54.840> features<00:02:55.080> with<00:02:55.260> that<00:02:55.440> is 00:02:55.550 --> 00:02:55.560 align:start position:0% um one of the features with that is 00:02:55.560 --> 00:02:57.229 align:start position:0% um one of the features with that is going<00:02:55.739> to<00:02:55.800> be<00:02:55.920> account<00:02:56.160> recovery<00:02:56.760> sometimes 00:02:57.229 --> 00:02:57.239 align:start position:0% going to be account recovery sometimes 00:02:57.239 --> 00:02:59.089 align:start position:0% going to be account recovery sometimes people<00:02:57.420> talk<00:02:57.660> about<00:02:57.720> a<00:02:57.959> social<00:02:58.140> recovery<00:02:58.680> so 00:02:59.089 --> 00:02:59.099 align:start position:0% people talk about a social recovery so 00:02:59.099 --> 00:03:01.250 align:start position:0% people talk about a social recovery so if<00:02:59.640> your<00:02:59.760> project<00:02:59.940> keys<00:03:00.360> are<00:03:00.480> compromised<00:03:01.019> is 00:03:01.250 --> 00:03:01.260 align:start position:0% if your project keys are compromised is 00:03:01.260 --> 00:03:02.990 align:start position:0% if your project keys are compromised is there<00:03:01.379> a<00:03:01.560> way<00:03:01.680> you<00:03:01.920> can<00:03:02.040> swap<00:03:02.400> to<00:03:02.760> a<00:03:02.940> more 00:03:02.990 --> 00:03:03.000 align:start position:0% there a way you can swap to a more 00:03:03.000 --> 00:03:05.509 align:start position:0% there a way you can swap to a more secure<00:03:03.300> set<00:03:03.540> of<00:03:03.780> private<00:03:04.200> keys<00:03:04.620> and<00:03:05.160> what<00:03:05.340> kind 00:03:05.509 --> 00:03:05.519 align:start position:0% secure set of private keys and what kind 00:03:05.519 --> 00:03:07.070 align:start position:0% secure set of private keys and what kind of<00:03:05.580> features<00:03:05.940> functionalities<00:03:06.540> and<00:03:06.840> security 00:03:07.070 --> 00:03:07.080 align:start position:0% of features functionalities and security 00:03:07.080 --> 00:03:08.690 align:start position:0% of features functionalities and security that<00:03:07.620> will<00:03:07.800> enable 00:03:08.690 --> 00:03:08.700 align:start position:0% that will enable 00:03:08.700 --> 00:03:10.610 align:start position:0% that will enable and<00:03:09.180> then<00:03:09.300> we<00:03:09.540> also<00:03:09.720> want<00:03:09.840> to<00:03:09.959> have<00:03:10.140> upgradable 00:03:10.610 --> 00:03:10.620 align:start position:0% and then we also want to have upgradable 00:03:10.620 --> 00:03:12.710 align:start position:0% and then we also want to have upgradable functionality<00:03:11.280> for<00:03:11.640> wallets<00:03:12.000> so<00:03:12.480> you<00:03:12.659> can 00:03:12.710 --> 00:03:12.720 align:start position:0% functionality for wallets so you can 00:03:12.720 --> 00:03:14.390 align:start position:0% functionality for wallets so you can change<00:03:13.019> what<00:03:13.319> features<00:03:13.620> and<00:03:13.800> things<00:03:13.980> it<00:03:14.220> has 00:03:14.390 --> 00:03:14.400 align:start position:0% change what features and things it has 00:03:14.400 --> 00:03:17.030 align:start position:0% change what features and things it has over<00:03:15.000> time<00:03:15.300> so<00:03:15.900> that<00:03:16.140> wallets<00:03:16.560> can<00:03:16.739> serve<00:03:16.980> a 00:03:17.030 --> 00:03:17.040 align:start position:0% over time so that wallets can serve a 00:03:17.040 --> 00:03:19.190 align:start position:0% over time so that wallets can serve a more<00:03:17.220> diverse<00:03:17.519> set<00:03:17.700> of<00:03:17.879> users<00:03:18.300> across<00:03:18.959> the 00:03:19.190 --> 00:03:19.200 align:start position:0% more diverse set of users across the 00:03:19.200 --> 00:03:21.949 align:start position:0% more diverse set of users across the entire<00:03:19.440> ecosystem 00:03:21.949 --> 00:03:21.959 align:start position:0% entire ecosystem 00:03:21.959 --> 00:03:24.350 align:start position:0% entire ecosystem and<00:03:22.500> finally<00:03:22.739> we<00:03:23.099> want<00:03:23.220> to<00:03:23.340> make<00:03:23.400> D<00:03:23.640> apps<00:03:24.060> a<00:03:24.239> lot 00:03:24.350 --> 00:03:24.360 align:start position:0% and finally we want to make D apps a lot 00:03:24.360 --> 00:03:26.149 align:start position:0% and finally we want to make D apps a lot easier<00:03:24.780> to<00:03:25.140> use 00:03:26.149 --> 00:03:26.159 align:start position:0% easier to use 00:03:26.159 --> 00:03:29.330 align:start position:0% easier to use and<00:03:26.700> so<00:03:27.140> part<00:03:28.140> of<00:03:28.260> that<00:03:28.319> is<00:03:28.440> by<00:03:28.620> having<00:03:28.800> a<00:03:29.040> baked 00:03:29.330 --> 00:03:29.340 align:start position:0% and so part of that is by having a baked 00:03:29.340 --> 00:03:31.130 align:start position:0% and so part of that is by having a baked in<00:03:29.519> multi-call 00:03:31.130 --> 00:03:31.140 align:start position:0% in multi-call 00:03:31.140 --> 00:03:33.170 align:start position:0% in multi-call um<00:03:31.200> or<00:03:31.560> we<00:03:31.739> call<00:03:31.860> it<00:03:32.040> multi-actions<00:03:32.819> where<00:03:33.000> you 00:03:33.170 --> 00:03:33.180 align:start position:0% um or we call it multi-actions where you 00:03:33.180 --> 00:03:35.330 align:start position:0% um or we call it multi-actions where you can<00:03:33.300> take<00:03:33.659> multiple<00:03:34.260> transactions<00:03:34.860> and<00:03:35.159> put 00:03:35.330 --> 00:03:35.340 align:start position:0% can take multiple transactions and put 00:03:35.340 --> 00:03:36.710 align:start position:0% can take multiple transactions and put them<00:03:35.459> into<00:03:35.640> one 00:03:36.710 --> 00:03:36.720 align:start position:0% them into one 00:03:36.720 --> 00:03:38.330 align:start position:0% them into one and<00:03:37.140> then<00:03:37.260> also<00:03:37.560> having<00:03:37.739> sponsored 00:03:38.330 --> 00:03:38.340 align:start position:0% and then also having sponsored 00:03:38.340 --> 00:03:39.830 align:start position:0% and then also having sponsored transactions<00:03:38.819> where<00:03:39.060> the<00:03:39.239> user<00:03:39.540> does<00:03:39.720> not 00:03:39.830 --> 00:03:39.840 align:start position:0% transactions where the user does not 00:03:39.840 --> 00:03:42.289 align:start position:0% transactions where the user does not have<00:03:40.080> to<00:03:40.260> pay<00:03:40.500> gas<00:03:41.040> on<00:03:41.519> their<00:03:41.640> end<00:03:41.819> and<00:03:42.060> the<00:03:42.180> D 00:03:42.289 --> 00:03:42.299 align:start position:0% have to pay gas on their end and the D 00:03:42.299 --> 00:03:44.509 align:start position:0% have to pay gas on their end and the D app<00:03:42.420> sponsors<00:03:42.840> it<00:03:43.019> instead<00:03:43.379> so<00:03:43.920> that<00:03:44.159> way<00:03:44.280> when 00:03:44.509 --> 00:03:44.519 align:start position:0% app sponsors it instead so that way when 00:03:44.519 --> 00:03:46.550 align:start position:0% app sponsors it instead so that way when users<00:03:44.879> first<00:03:45.120> come<00:03:45.360> in<00:03:45.540> to<00:03:45.959> try<00:03:46.140> at<00:03:46.319> the<00:03:46.440> app 00:03:46.550 --> 00:03:46.560 align:start position:0% users first come in to try at the app 00:03:46.560 --> 00:03:47.750 align:start position:0% users first come in to try at the app for<00:03:46.739> the<00:03:46.860> first<00:03:46.920> time<00:03:47.099> they<00:03:47.340> don't<00:03:47.459> have<00:03:47.580> to<00:03:47.700> go 00:03:47.750 --> 00:03:47.760 align:start position:0% for the first time they don't have to go 00:03:47.760 --> 00:03:49.729 align:start position:0% for the first time they don't have to go stay<00:03:48.000> tuned<00:03:48.180> exchange<00:03:48.599> to<00:03:48.840> buy<00:03:48.959> ethereum<00:03:49.500> so 00:03:49.729 --> 00:03:49.739 align:start position:0% stay tuned exchange to buy ethereum so 00:03:49.739 --> 00:03:54.289 align:start position:0% stay tuned exchange to buy ethereum so they<00:03:49.860> can<00:03:49.980> pay<00:03:50.099> gas<00:03:50.280> for<00:03:50.519> transactions 00:03:54.289 --> 00:03:54.299 align:start position:0% 00:03:54.299 --> 00:03:57.710 align:start position:0% so<00:03:55.080> to<00:03:55.620> start<00:03:55.739> off<00:03:55.980> we're<00:03:56.400> going<00:03:56.519> to<00:03:56.640> cover<00:03:57.120> Els 00:03:57.710 --> 00:03:57.720 align:start position:0% so to start off we're going to cover Els 00:03:57.720 --> 00:03:59.210 align:start position:0% so to start off we're going to cover Els signatures<00:03:58.140> and<00:03:58.319> aggregations<00:03:58.680> at<00:03:58.920> kind<00:03:59.099> of<00:03:59.159> a 00:03:59.210 --> 00:03:59.220 align:start position:0% signatures and aggregations at kind of a 00:03:59.220 --> 00:04:00.710 align:start position:0% signatures and aggregations at kind of a high<00:03:59.340> level 00:04:00.710 --> 00:04:00.720 align:start position:0% high level 00:04:00.720 --> 00:04:05.210 align:start position:0% high level uh<00:04:01.260> BLS<00:04:01.799> stands<00:04:02.220> for<00:04:02.340> bone<00:04:02.640> Lin<00:04:03.260> chacham<00:04:04.260> uh<00:04:04.920> is 00:04:05.210 --> 00:04:05.220 align:start position:0% uh BLS stands for bone Lin chacham uh is 00:04:05.220 --> 00:04:07.729 align:start position:0% uh BLS stands for bone Lin chacham uh is a<00:04:05.400> pairing<00:04:05.640> cryptography<00:04:06.360> based<00:04:07.200> uh 00:04:07.729 --> 00:04:07.739 align:start position:0% a pairing cryptography based uh 00:04:07.739 --> 00:04:09.649 align:start position:0% a pairing cryptography based uh signature<00:04:08.220> scheme<00:04:08.580> used<00:04:09.000> in<00:04:09.239> the<00:04:09.299> ethereum 00:04:09.649 --> 00:04:09.659 align:start position:0% signature scheme used in the ethereum 00:04:09.659 --> 00:04:11.690 align:start position:0% signature scheme used in the ethereum consensus<00:04:10.140> layer<00:04:10.439> zcash<00:04:11.159> and<00:04:11.340> a<00:04:11.459> number<00:04:11.580> of 00:04:11.690 --> 00:04:11.700 align:start position:0% consensus layer zcash and a number of 00:04:11.700 --> 00:04:13.009 align:start position:0% consensus layer zcash and a number of other<00:04:11.879> projects 00:04:13.009 --> 00:04:13.019 align:start position:0% other projects 00:04:13.019 --> 00:04:14.270 align:start position:0% other projects it<00:04:13.560> is 00:04:14.270 --> 00:04:14.280 align:start position:0% it is 00:04:14.280 --> 00:04:16.069 align:start position:0% it is um deterministic<00:04:15.000> for<00:04:15.239> a<00:04:15.360> given<00:04:15.599> public<00:04:15.780> key 00:04:16.069 --> 00:04:16.079 align:start position:0% um deterministic for a given public key 00:04:16.079 --> 00:04:17.810 align:start position:0% um deterministic for a given public key and<00:04:16.500> message 00:04:17.810 --> 00:04:17.820 align:start position:0% and message 00:04:17.820 --> 00:04:20.810 align:start position:0% and message um<00:04:17.880> validators<00:04:18.419> currently<00:04:18.900> are<00:04:19.320> using<00:04:19.680> BLS<00:04:20.220> uh 00:04:20.810 --> 00:04:20.820 align:start position:0% um validators currently are using BLS uh 00:04:20.820 --> 00:04:23.450 align:start position:0% um validators currently are using BLS uh signatures<00:04:21.299> specifically<00:04:21.780> on<00:04:22.079> the<00:04:22.460> bls-12381 00:04:23.450 --> 00:04:23.460 align:start position:0% signatures specifically on the bls-12381 00:04:23.460 --> 00:04:27.110 align:start position:0% signatures specifically on the bls-12381 curve<00:04:24.199> uh<00:04:25.199> two<00:04:25.680> uh<00:04:26.100> sign<00:04:26.340> messages<00:04:26.639> on<00:04:27.060> the 00:04:27.110 --> 00:04:27.120 align:start position:0% curve uh two uh sign messages on the 00:04:27.120 --> 00:04:28.610 align:start position:0% curve uh two uh sign messages on the consensus<00:04:27.540> layer 00:04:28.610 --> 00:04:28.620 align:start position:0% consensus layer 00:04:28.620 --> 00:04:30.230 align:start position:0% consensus layer um<00:04:28.740> and<00:04:28.919> then<00:04:28.979> inside<00:04:29.100> of<00:04:29.340> the<00:04:29.460> evm<00:04:29.820> execution 00:04:30.230 --> 00:04:30.240 align:start position:0% um and then inside of the evm execution 00:04:30.240 --> 00:04:33.050 align:start position:0% um and then inside of the evm execution layer<00:04:30.600> we<00:04:30.840> have<00:04:30.900> access<00:04:31.080> to<00:04:31.320> the<00:04:31.440> BN<00:04:31.800> 254<00:04:32.520> curve 00:04:33.050 --> 00:04:33.060 align:start position:0% layer we have access to the BN 254 curve 00:04:33.060 --> 00:04:36.770 align:start position:0% layer we have access to the BN 254 curve via<00:04:33.500> eip197<00:04:34.500> that<00:04:35.220> allows<00:04:35.639> us<00:04:35.759> to<00:04:36.360> um<00:04:36.360> which<00:04:36.600> we 00:04:36.770 --> 00:04:36.780 align:start position:0% via eip197 that allows us to um which we 00:04:36.780 --> 00:04:39.110 align:start position:0% via eip197 that allows us to um which we use<00:04:36.840> in<00:04:37.020> BLS<00:04:37.380> wallet<00:04:37.740> for<00:04:38.040> both<00:04:38.280> signing<00:04:38.940> and 00:04:39.110 --> 00:04:39.120 align:start position:0% use in BLS wallet for both signing and 00:04:39.120 --> 00:04:41.950 align:start position:0% use in BLS wallet for both signing and then<00:04:39.240> verifying<00:04:39.780> on<00:04:39.900> chain<00:04:40.259> the<00:04:40.440> transactions 00:04:41.950 --> 00:04:41.960 align:start position:0% then verifying on chain the transactions 00:04:41.960 --> 00:04:45.409 align:start position:0% then verifying on chain the transactions uh<00:04:42.960> we're<00:04:43.380> hoping<00:04:43.680> in<00:04:43.860> the<00:04:43.919> future<00:04:44.100> via<00:04:44.940> a 00:04:45.409 --> 00:04:45.419 align:start position:0% uh we're hoping in the future via a 00:04:45.419 --> 00:04:47.570 align:start position:0% uh we're hoping in the future via a newer<00:04:45.900> EIP<00:04:46.259> that<00:04:46.740> we<00:04:46.800> will<00:04:46.919> be<00:04:47.100> able<00:04:47.280> to 00:04:47.570 --> 00:04:47.580 align:start position:0% newer EIP that we will be able to 00:04:47.580 --> 00:04:49.370 align:start position:0% newer EIP that we will be able to actually<00:04:47.759> move<00:04:48.000> to<00:04:48.240> the<00:04:48.360> beacon<00:04:48.660> chain<00:04:48.840> uh 00:04:49.370 --> 00:04:49.380 align:start position:0% actually move to the beacon chain uh 00:04:49.380 --> 00:04:51.469 align:start position:0% actually move to the beacon chain uh curve<00:04:49.740> for<00:04:49.919> more<00:04:50.040> security<00:04:50.340> and<00:04:51.000> for<00:04:51.300> better 00:04:51.469 --> 00:04:51.479 align:start position:0% curve for more security and for better 00:04:51.479 --> 00:04:53.210 align:start position:0% curve for more security and for better access<00:04:51.840> to<00:04:52.080> Frameworks<00:04:52.560> that<00:04:52.740> the<00:04:52.860> beacon 00:04:53.210 --> 00:04:53.220 align:start position:0% access to Frameworks that the beacon 00:04:53.220 --> 00:04:54.950 align:start position:0% access to Frameworks that the beacon chain<00:04:53.340> is<00:04:53.520> using<00:04:53.880> uh<00:04:54.479> to<00:04:54.600> improve<00:04:54.840> that 00:04:54.950 --> 00:04:54.960 align:start position:0% chain is using uh to improve that 00:04:54.960 --> 00:04:57.530 align:start position:0% chain is using uh to improve that signature<00:04:55.259> but<00:04:56.220> the<00:04:56.880> most<00:04:56.940> important<00:04:57.360> thing 00:04:57.530 --> 00:04:57.540 align:start position:0% signature but the most important thing 00:04:57.540 --> 00:04:59.689 align:start position:0% signature but the most important thing for<00:04:57.840> us<00:04:58.020> is 00:04:59.689 --> 00:04:59.699 align:start position:0% for us is 00:04:59.699 --> 00:05:01.550 align:start position:0% for us is Central<00:05:00.180> aggregation 00:05:01.550 --> 00:05:01.560 align:start position:0% Central aggregation 00:05:01.560 --> 00:05:03.409 align:start position:0% Central aggregation and<00:05:01.919> what<00:05:02.040> we're<00:05:02.160> able<00:05:02.340> to<00:05:02.460> do<00:05:02.580> with<00:05:02.880> the<00:05:03.000> BLS 00:05:03.409 --> 00:05:03.419 align:start position:0% and what we're able to do with the BLS 00:05:03.419 --> 00:05:05.810 align:start position:0% and what we're able to do with the BLS signature<00:05:03.780> scheme<00:05:04.139> is<00:05:04.860> take<00:05:05.220> multiple 00:05:05.810 --> 00:05:05.820 align:start position:0% signature scheme is take multiple 00:05:05.820 --> 00:05:07.610 align:start position:0% signature scheme is take multiple signatures 00:05:07.610 --> 00:05:07.620 align:start position:0% signatures 00:05:07.620 --> 00:05:10.249 align:start position:0% signatures let's<00:05:07.979> work<00:05:08.280> yeah<00:05:08.520> and<00:05:09.180> merge<00:05:09.479> them<00:05:09.660> into<00:05:10.020> one 00:05:10.249 --> 00:05:10.259 align:start position:0% let's work yeah and merge them into one 00:05:10.259 --> 00:05:12.530 align:start position:0% let's work yeah and merge them into one signature<00:05:10.800> so<00:05:11.340> normally<00:05:11.759> with<00:05:12.060> the<00:05:12.180> signature 00:05:12.530 --> 00:05:12.540 align:start position:0% signature so normally with the signature 00:05:12.540 --> 00:05:14.210 align:start position:0% signature so normally with the signature space<00:05:12.660> you'd<00:05:13.020> have<00:05:13.139> taking<00:05:13.440> up<00:05:13.680> we<00:05:13.860> can<00:05:13.979> shrink 00:05:14.210 --> 00:05:14.220 align:start position:0% space you'd have taking up we can shrink 00:05:14.220 --> 00:05:16.490 align:start position:0% space you'd have taking up we can shrink it<00:05:14.340> into<00:05:14.460> just<00:05:14.820> one 00:05:16.490 --> 00:05:16.500 align:start position:0% it into just one 00:05:16.500 --> 00:05:19.129 align:start position:0% it into just one um<00:05:16.580> and<00:05:17.580> this<00:05:18.240> is<00:05:18.360> really<00:05:18.540> good<00:05:18.660> for<00:05:18.780> reducing 00:05:19.129 --> 00:05:19.139 align:start position:0% um and this is really good for reducing 00:05:19.139 --> 00:05:21.290 align:start position:0% um and this is really good for reducing uh<00:05:19.440> the<00:05:19.620> data<00:05:19.800> that<00:05:19.919> we<00:05:20.040> roll<00:05:20.160> up<00:05:20.340> into<00:05:20.520> an<00:05:20.880> L1 00:05:21.290 --> 00:05:21.300 align:start position:0% uh the data that we roll up into an L1 00:05:21.300 --> 00:05:23.390 align:start position:0% uh the data that we roll up into an L1 because<00:05:21.900> normally<00:05:22.259> when<00:05:22.500> a<00:05:22.680> rollup<00:05:23.039> goes<00:05:23.340> in 00:05:23.390 --> 00:05:23.400 align:start position:0% because normally when a rollup goes in 00:05:23.400 --> 00:05:25.550 align:start position:0% because normally when a rollup goes in it<00:05:23.820> takes<00:05:24.000> all<00:05:24.180> the<00:05:24.360> transaction<00:05:24.780> data<00:05:25.259> as 00:05:25.550 --> 00:05:25.560 align:start position:0% it takes all the transaction data as 00:05:25.560 --> 00:05:27.710 align:start position:0% it takes all the transaction data as well<00:05:25.740> as<00:05:25.860> the<00:05:26.100> signatures<00:05:26.639> for<00:05:27.300> each<00:05:27.479> of<00:05:27.600> those 00:05:27.710 --> 00:05:27.720 align:start position:0% well as the signatures for each of those 00:05:27.720 --> 00:05:30.050 align:start position:0% well as the signatures for each of those transactions<00:05:28.380> specifically<00:05:29.160> the<00:05:29.280> RS<00:05:29.639> and<00:05:29.880> V 00:05:30.050 --> 00:05:30.060 align:start position:0% transactions specifically the RS and V 00:05:30.060 --> 00:05:31.969 align:start position:0% transactions specifically the RS and V components<00:05:30.600> of<00:05:30.720> that<00:05:30.900> signature 00:05:31.969 --> 00:05:31.979 align:start position:0% components of that signature 00:05:31.979 --> 00:05:35.029 align:start position:0% components of that signature instead<00:05:32.759> we<00:05:33.300> can<00:05:33.419> use<00:05:33.840> one<00:05:34.080> BLS<00:05:34.620> signature 00:05:35.029 --> 00:05:35.039 align:start position:0% instead we can use one BLS signature 00:05:35.039 --> 00:05:37.010 align:start position:0% instead we can use one BLS signature across<00:05:35.520> all<00:05:35.699> of<00:05:35.820> those<00:05:35.940> transactions<00:05:36.539> plus 00:05:37.010 --> 00:05:37.020 align:start position:0% across all of those transactions plus 00:05:37.020 --> 00:05:40.129 align:start position:0% across all of those transactions plus one<00:05:37.259> is<00:05:37.440> ecsa<00:05:38.100> signature<00:05:38.639> and<00:05:39.600> save<00:05:39.780> on<00:05:40.020> that 00:05:40.129 --> 00:05:40.139 align:start position:0% one is ecsa signature and save on that 00:05:40.139 --> 00:05:41.570 align:start position:0% one is ecsa signature and save on that data<00:05:40.380> that<00:05:40.500> we<00:05:40.680> roll<00:05:40.740> up<00:05:40.919> and<00:05:41.160> that's<00:05:41.280> in<00:05:41.460> the 00:05:41.570 --> 00:05:41.580 align:start position:0% data that we roll up and that's in the 00:05:41.580 --> 00:05:43.670 align:start position:0% data that we roll up and that's in the example<00:05:41.820> we<00:05:42.000> saw<00:05:42.180> before<00:05:42.419> why<00:05:43.080> the<00:05:43.380> actual 00:05:43.670 --> 00:05:43.680 align:start position:0% example we saw before why the actual 00:05:43.680 --> 00:05:48.050 align:start position:0% example we saw before why the actual transaction<00:05:44.340> data<00:05:44.759> payload<00:05:45.120> is<00:05:45.240> much<00:05:45.419> smaller 00:05:48.050 --> 00:05:48.060 align:start position:0% 00:05:48.060 --> 00:05:49.490 align:start position:0% um<00:05:48.120> if<00:05:48.360> you're<00:05:48.539> interested<00:05:48.840> in<00:05:49.080> learning<00:05:49.320> a 00:05:49.490 --> 00:05:49.500 align:start position:0% um if you're interested in learning a 00:05:49.500 --> 00:05:52.550 align:start position:0% um if you're interested in learning a bit<00:05:49.620> more<00:05:49.860> about<00:05:50.520> the<00:05:51.240> underlying<00:05:51.780> of<00:05:51.960> pairing 00:05:52.550 --> 00:05:52.560 align:start position:0% bit more about the underlying of pairing 00:05:52.560 --> 00:05:54.110 align:start position:0% bit more about the underlying of pairing cryptography 00:05:54.110 --> 00:05:54.120 align:start position:0% cryptography 00:05:54.120 --> 00:05:55.310 align:start position:0% cryptography um there's<00:05:54.300> a<00:05:54.479> really<00:05:54.600> good<00:05:54.720> visual<00:05:54.960> guide<00:05:55.139> at 00:05:55.310 --> 00:05:55.320 align:start position:0% um there's a really good visual guide at 00:05:55.320 --> 00:05:57.170 align:start position:0% um there's a really good visual guide at cryptology<00:05:55.740> which<00:05:56.160> will<00:05:56.280> go<00:05:56.460> into<00:05:56.699> the<00:05:56.940> actual 00:05:57.170 --> 00:05:57.180 align:start position:0% cryptology which will go into the actual 00:05:57.180 --> 00:05:58.790 align:start position:0% cryptology which will go into the actual aggregation<00:05:57.660> and<00:05:57.960> more<00:05:58.139> about<00:05:58.320> the<00:05:58.560> actual 00:05:58.790 --> 00:05:58.800 align:start position:0% aggregation and more about the actual 00:05:58.800 --> 00:06:02.090 align:start position:0% aggregation and more about the actual BLS<00:05:59.340> signatures 00:06:02.090 --> 00:06:02.100 align:start position:0% BLS signatures 00:06:02.100 --> 00:06:04.070 align:start position:0% BLS signatures so<00:06:02.639> let's<00:06:03.000> get<00:06:03.180> into<00:06:03.300> where<00:06:03.539> we<00:06:03.720> are<00:06:03.840> today 00:06:04.070 --> 00:06:04.080 align:start position:0% so let's get into where we are today 00:06:04.080 --> 00:06:07.189 align:start position:0% so let's get into where we are today with<00:06:04.320> BLS<00:06:04.800> wallet 00:06:07.189 --> 00:06:07.199 align:start position:0% with BLS wallet 00:06:07.199 --> 00:06:10.490 align:start position:0% with BLS wallet so<00:06:07.740> at<00:06:08.460> a<00:06:08.580> high<00:06:08.639> level<00:06:08.820> as<00:06:09.419> per<00:06:09.660> most<00:06:09.960> normal<00:06:10.199> D 00:06:10.490 --> 00:06:10.500 align:start position:0% so at a high level as per most normal D 00:06:10.500 --> 00:06:12.170 align:start position:0% so at a high level as per most normal D app<00:06:10.680> usage<00:06:11.039> you're<00:06:11.160> going<00:06:11.340> to<00:06:11.400> have<00:06:11.520> a<00:06:11.759> browser 00:06:12.170 --> 00:06:12.180 align:start position:0% app usage you're going to have a browser 00:06:12.180 --> 00:06:14.810 align:start position:0% app usage you're going to have a browser that's<00:06:12.539> going<00:06:12.720> to<00:06:12.900> have<00:06:13.259> a<00:06:14.039> extension<00:06:14.520> usually 00:06:14.810 --> 00:06:14.820 align:start position:0% that's going to have a extension usually 00:06:14.820 --> 00:06:16.550 align:start position:0% that's going to have a extension usually in<00:06:15.120> the<00:06:15.240> wallet<00:06:15.539> and<00:06:16.020> that's<00:06:16.139> going<00:06:16.320> to<00:06:16.440> be 00:06:16.550 --> 00:06:16.560 align:start position:0% in the wallet and that's going to be 00:06:16.560 --> 00:06:18.950 align:start position:0% in the wallet and that's going to be communicating<00:06:17.039> to<00:06:17.400> some<00:06:17.520> RPC<00:06:18.000> node<00:06:18.419> and<00:06:18.840> we 00:06:18.950 --> 00:06:18.960 align:start position:0% communicating to some RPC node and we 00:06:18.960 --> 00:06:20.330 align:start position:0% communicating to some RPC node and we have<00:06:19.020> the<00:06:19.199> same<00:06:19.320> setup<00:06:19.620> in<00:06:19.800> our<00:06:19.979> example 00:06:20.330 --> 00:06:20.340 align:start position:0% have the same setup in our example 00:06:20.340 --> 00:06:22.309 align:start position:0% have the same setup in our example prototype<00:06:20.940> extension 00:06:22.309 --> 00:06:22.319 align:start position:0% prototype extension 00:06:22.319 --> 00:06:24.170 align:start position:0% prototype extension we're<00:06:22.800> then<00:06:22.979> going<00:06:23.160> to<00:06:23.340> in<00:06:23.580> our<00:06:23.759> case<00:06:23.940> though 00:06:24.170 --> 00:06:24.180 align:start position:0% we're then going to in our case though 00:06:24.180 --> 00:06:26.270 align:start position:0% we're then going to in our case though have<00:06:24.419> a<00:06:24.539> set<00:06:24.660> of<00:06:24.780> user<00:06:25.139> operations<00:06:25.560> that<00:06:25.979> we 00:06:26.270 --> 00:06:26.280 align:start position:0% have a set of user operations that we 00:06:26.280 --> 00:06:28.370 align:start position:0% have a set of user operations that we forward<00:06:26.580> to<00:06:27.000> an<00:06:27.300> aggregator<00:06:27.720> service<00:06:28.020> which 00:06:28.370 --> 00:06:28.380 align:start position:0% forward to an aggregator service which 00:06:28.380 --> 00:06:29.930 align:start position:0% forward to an aggregator service which is<00:06:28.500> going<00:06:28.680> to<00:06:28.800> take<00:06:28.979> many<00:06:29.280> to<00:06:29.520> separate 00:06:29.930 --> 00:06:29.940 align:start position:0% is going to take many to separate 00:06:29.940 --> 00:06:32.270 align:start position:0% is going to take many to separate operations<00:06:30.780> and<00:06:31.620> merge<00:06:31.860> them<00:06:31.979> all<00:06:32.160> together 00:06:32.270 --> 00:06:32.280 align:start position:0% operations and merge them all together 00:06:32.280 --> 00:06:34.610 align:start position:0% operations and merge them all together into<00:06:32.639> one<00:06:32.880> and<00:06:33.479> submit<00:06:33.720> them<00:06:33.780> to<00:06:33.900> an<00:06:34.020> L2<00:06:34.259> node 00:06:34.610 --> 00:06:34.620 align:start position:0% into one and submit them to an L2 node 00:06:34.620 --> 00:06:37.370 align:start position:0% into one and submit them to an L2 node which<00:06:35.100> then<00:06:35.280> will<00:06:35.520> execute<00:06:36.000> against<00:06:36.360> our<00:06:37.080> uh 00:06:37.370 --> 00:06:37.380 align:start position:0% which then will execute against our uh 00:06:37.380 --> 00:06:38.749 align:start position:0% which then will execute against our uh contracts<00:06:37.860> for<00:06:38.039> the<00:06:38.160> verification<00:06:38.520> of<00:06:38.699> the 00:06:38.749 --> 00:06:38.759 align:start position:0% contracts for the verification of the 00:06:38.759 --> 00:06:40.189 align:start position:0% contracts for the verification of the signatures<00:06:39.240> and<00:06:39.479> then<00:06:39.539> through<00:06:39.840> the<00:06:40.020> smart 00:06:40.189 --> 00:06:40.199 align:start position:0% signatures and then through the smart 00:06:40.199 --> 00:06:41.809 align:start position:0% signatures and then through the smart contract<00:06:40.620> wallet 00:06:41.809 --> 00:06:41.819 align:start position:0% contract wallet 00:06:41.819 --> 00:06:44.210 align:start position:0% contract wallet to<00:06:42.180> dive<00:06:42.300> into<00:06:42.479> that<00:06:42.660> a<00:06:42.780> little<00:06:42.900> bit<00:06:43.020> more 00:06:44.210 --> 00:06:44.220 align:start position:0% to dive into that a little bit more 00:06:44.220 --> 00:06:47.689 align:start position:0% to dive into that a little bit more at<00:06:45.000> a<00:06:45.120> high<00:06:45.240> level<00:06:45.479> we're<00:06:46.259> going<00:06:46.440> to<00:06:46.560> have<00:06:46.860> a<00:06:47.340> DF 00:06:47.689 --> 00:06:47.699 align:start position:0% at a high level we're going to have a DF 00:06:47.699 --> 00:06:48.710 align:start position:0% at a high level we're going to have a DF starting<00:06:47.880> out<00:06:48.060> by<00:06:48.240> generating<00:06:48.479> the 00:06:48.710 --> 00:06:48.720 align:start position:0% starting out by generating the 00:06:48.720 --> 00:06:50.570 align:start position:0% starting out by generating the operations<00:06:49.139> which<00:06:49.560> contain<00:06:49.919> a<00:06:50.340> set<00:06:50.460> of 00:06:50.570 --> 00:06:50.580 align:start position:0% operations which contain a set of 00:06:50.580 --> 00:06:51.770 align:start position:0% operations which contain a set of actions<00:06:50.940> and<00:06:51.120> we'll<00:06:51.240> go<00:06:51.360> into<00:06:51.419> what<00:06:51.660> that 00:06:51.770 --> 00:06:51.780 align:start position:0% actions and we'll go into what that 00:06:51.780 --> 00:06:53.570 align:start position:0% actions and we'll go into what that format<00:06:52.080> looks<00:06:52.319> like<00:06:52.440> in<00:06:52.620> a<00:06:52.740> second 00:06:53.570 --> 00:06:53.580 align:start position:0% format looks like in a second 00:06:53.580 --> 00:06:55.610 align:start position:0% format looks like in a second the<00:06:54.060> wallet<00:06:54.360> extension<00:06:54.720> will<00:06:54.960> then<00:06:55.139> use<00:06:55.380> the 00:06:55.610 --> 00:06:55.620 align:start position:0% the wallet extension will then use the 00:06:55.620 --> 00:06:57.890 align:start position:0% the wallet extension will then use the BLS<00:06:56.039> client<00:06:56.340> module<00:06:56.699> to<00:06:57.000> sign<00:06:57.240> all<00:06:57.539> of<00:06:57.660> those 00:06:57.890 --> 00:06:57.900 align:start position:0% BLS client module to sign all of those 00:06:57.900 --> 00:06:59.990 align:start position:0% BLS client module to sign all of those with<00:06:58.380> those<00:06:58.500> BLS<00:06:58.979> signatures 00:06:59.990 --> 00:07:00.000 align:start position:0% with those BLS signatures 00:07:00.000 --> 00:07:01.909 align:start position:0% with those BLS signatures those<00:07:00.360> are<00:07:00.539> then<00:07:00.660> submitted<00:07:01.139> into<00:07:01.500> this 00:07:01.909 --> 00:07:01.919 align:start position:0% those are then submitted into this 00:07:01.919 --> 00:07:05.629 align:start position:0% those are then submitted into this aggregator<00:07:02.400> service<00:07:02.940> to<00:07:03.660> create<00:07:03.979> a<00:07:04.979> single<00:07:05.280> a 00:07:05.629 --> 00:07:05.639 align:start position:0% aggregator service to create a single a 00:07:05.639 --> 00:07:07.969 align:start position:0% aggregator service to create a single a bundle<00:07:06.120> of<00:07:06.180> operations<00:07:06.660> with<00:07:07.259> one<00:07:07.500> aggregated 00:07:07.969 --> 00:07:07.979 align:start position:0% bundle of operations with one aggregated 00:07:07.979 --> 00:07:09.170 align:start position:0% bundle of operations with one aggregated signature 00:07:09.170 --> 00:07:09.180 align:start position:0% signature 00:07:09.180 --> 00:07:10.370 align:start position:0% signature then 00:07:10.370 --> 00:07:10.380 align:start position:0% then 00:07:10.380 --> 00:07:12.529 align:start position:0% then the<00:07:10.740> bundler<00:07:11.100> will<00:07:11.400> aggregator<00:07:11.940> will<00:07:12.240> take 00:07:12.529 --> 00:07:12.539 align:start position:0% the bundler will aggregator will take 00:07:12.539 --> 00:07:14.629 align:start position:0% the bundler will aggregator will take that<00:07:13.020> set<00:07:13.139> of<00:07:13.319> transactions<00:07:13.919> and<00:07:14.520> we'll 00:07:14.629 --> 00:07:14.639 align:start position:0% that set of transactions and we'll 00:07:14.639 --> 00:07:17.390 align:start position:0% that set of transactions and we'll submit<00:07:14.940> them<00:07:15.060> into<00:07:15.360> the<00:07:15.780> layer<00:07:16.080> 2<00:07:16.199> evm<00:07:16.740> where 00:07:17.390 --> 00:07:17.400 align:start position:0% submit them into the layer 2 evm where 00:07:17.400 --> 00:07:19.670 align:start position:0% submit them into the layer 2 evm where we<00:07:17.699> can<00:07:17.759> do<00:07:17.880> some<00:07:18.060> work<00:07:18.240> with<00:07:18.600> expansion<00:07:19.139> to 00:07:19.670 --> 00:07:19.680 align:start position:0% we can do some work with expansion to 00:07:19.680 --> 00:07:21.230 align:start position:0% we can do some work with expansion to expand<00:07:19.979> the<00:07:20.220> call<00:07:20.340> data<00:07:20.699> parameters<00:07:21.000> into 00:07:21.230 --> 00:07:21.240 align:start position:0% expand the call data parameters into 00:07:21.240 --> 00:07:25.070 align:start position:0% expand the call data parameters into more<00:07:21.599> uh<00:07:22.199> Advanced<00:07:23.039> or<00:07:23.280> more<00:07:23.639> verbose<00:07:24.120> data 00:07:25.070 --> 00:07:25.080 align:start position:0% more uh Advanced or more verbose data 00:07:25.080 --> 00:07:26.930 align:start position:0% more uh Advanced or more verbose data we<00:07:25.500> do<00:07:25.620> the<00:07:25.740> BLS<00:07:26.099> signature<00:07:26.460> verification 00:07:26.930 --> 00:07:26.940 align:start position:0% we do the BLS signature verification 00:07:26.940 --> 00:07:29.809 align:start position:0% we do the BLS signature verification across<00:07:27.419> those<00:07:27.680> and<00:07:28.680> then<00:07:28.860> finally<00:07:29.400> for<00:07:29.639> each 00:07:29.809 --> 00:07:29.819 align:start position:0% across those and then finally for each 00:07:29.819 --> 00:07:31.610 align:start position:0% across those and then finally for each of<00:07:29.880> those<00:07:30.000> operations<00:07:30.419> and<00:07:30.720> actions<00:07:31.139> we 00:07:31.610 --> 00:07:31.620 align:start position:0% of those operations and actions we 00:07:31.620 --> 00:07:34.189 align:start position:0% of those operations and actions we submit<00:07:31.919> it<00:07:32.039> to<00:07:32.220> the<00:07:32.400> actual<00:07:32.639> contract<00:07:33.120> wallets 00:07:34.189 --> 00:07:34.199 align:start position:0% submit it to the actual contract wallets 00:07:34.199 --> 00:07:37.129 align:start position:0% submit it to the actual contract wallets and<00:07:34.979> uh<00:07:35.580> that<00:07:36.000> is<00:07:36.060> then<00:07:36.240> executed<00:07:36.720> against<00:07:36.840> the 00:07:37.129 --> 00:07:37.139 align:start position:0% and uh that is then executed against the 00:07:37.139 --> 00:07:38.990 align:start position:0% and uh that is then executed against the actual<00:07:37.319> underlying<00:07:37.740> DF<00:07:38.039> code 00:07:38.990 --> 00:07:39.000 align:start position:0% actual underlying DF code 00:07:39.000 --> 00:07:40.550 align:start position:0% actual underlying DF code so<00:07:39.419> the<00:07:39.660> first<00:07:39.780> feature<00:07:40.020> we're<00:07:40.199> going<00:07:40.319> to<00:07:40.380> dive 00:07:40.550 --> 00:07:40.560 align:start position:0% so the first feature we're going to dive 00:07:40.560 --> 00:07:43.129 align:start position:0% so the first feature we're going to dive into<00:07:40.740> is<00:07:41.099> the<00:07:41.280> multi-caller<00:07:41.880> action 00:07:43.129 --> 00:07:43.139 align:start position:0% into is the multi-caller action 00:07:43.139 --> 00:07:45.710 align:start position:0% into is the multi-caller action um<00:07:43.199> for<00:07:43.440> this 00:07:45.710 --> 00:07:45.720 align:start position:0% 00:07:45.720 --> 00:07:47.870 align:start position:0% so<00:07:46.319> uh<00:07:47.039> this<00:07:47.220> is<00:07:47.340> a<00:07:47.400> library<00:07:47.520> that<00:07:47.759> our 00:07:47.870 --> 00:07:47.880 align:start position:0% so uh this is a library that our 00:07:47.880 --> 00:07:49.550 align:start position:0% so uh this is a library that our teammate<00:07:48.120> Andrew<00:07:48.300> helped<00:07:48.720> uh<00:07:48.960> right<00:07:49.080> if<00:07:49.440> you 00:07:49.550 --> 00:07:49.560 align:start position:0% teammate Andrew helped uh right if you 00:07:49.560 --> 00:07:50.990 align:start position:0% teammate Andrew helped uh right if you want<00:07:49.680> to<00:07:49.800> try<00:07:49.860> it<00:07:49.979> out<00:07:50.099> you<00:07:50.340> can<00:07:50.460> npm<00:07:50.819> install 00:07:50.990 --> 00:07:51.000 align:start position:0% want to try it out you can npm install 00:07:51.000 --> 00:07:55.129 align:start position:0% want to try it out you can npm install BLS<00:07:51.660> wallets<00:07:52.440> Dash<00:07:52.919> clients<00:07:53.720> still<00:07:54.720> keeps<00:07:55.020> in 00:07:55.129 --> 00:07:55.139 align:start position:0% BLS wallets Dash clients still keeps in 00:07:55.139 --> 00:07:57.050 align:start position:0% BLS wallets Dash clients still keeps in that<00:07:55.259> edge<00:07:55.380> of<00:07:55.500> that<00:07:55.620> stage 00:07:57.050 --> 00:07:57.060 align:start position:0% that edge of that stage 00:07:57.060 --> 00:07:58.730 align:start position:0% that edge of that stage um<00:07:57.120> in<00:07:57.660> there<00:07:57.780> we're<00:07:57.900> going<00:07:58.020> to<00:07:58.139> have<00:07:58.199> a<00:07:58.380> bundle 00:07:58.730 --> 00:07:58.740 align:start position:0% um in there we're going to have a bundle 00:07:58.740 --> 00:08:00.529 align:start position:0% um in there we're going to have a bundle that<00:07:59.220> we're<00:07:59.340> generating<00:07:59.699> and<00:08:00.000> the<00:08:00.120> wallet's 00:08:00.529 --> 00:08:00.539 align:start position:0% that we're generating and the wallet's 00:08:00.539 --> 00:08:02.809 align:start position:0% that we're generating and the wallet's going<00:08:00.599> to<00:08:00.720> sign<00:08:00.900> it<00:08:01.500> that<00:08:02.099> operation<00:08:02.460> is<00:08:02.639> going 00:08:02.809 --> 00:08:02.819 align:start position:0% going to sign it that operation is going 00:08:02.819 --> 00:08:04.309 align:start position:0% going to sign it that operation is going to<00:08:02.880> have<00:08:03.000> a<00:08:03.180> nonce<00:08:03.599> which<00:08:03.780> is<00:08:03.900> going<00:08:04.020> to<00:08:04.139> be<00:08:04.199> the 00:08:04.309 --> 00:08:04.319 align:start position:0% to have a nonce which is going to be the 00:08:04.319 --> 00:08:06.230 align:start position:0% to have a nonce which is going to be the current<00:08:04.440> wallet<00:08:04.860> nonst<00:08:05.280> for<00:08:05.639> if<00:08:05.819> the<00:08:05.940> wallet 00:08:06.230 --> 00:08:06.240 align:start position:0% current wallet nonst for if the wallet 00:08:06.240 --> 00:08:07.610 align:start position:0% current wallet nonst for if the wallet hasn't<00:08:06.479> been<00:08:06.599> created<00:08:06.960> yet<00:08:07.139> and<00:08:07.380> it's<00:08:07.500> going 00:08:07.610 --> 00:08:07.620 align:start position:0% hasn't been created yet and it's going 00:08:07.620 --> 00:08:09.770 align:start position:0% hasn't been created yet and it's going to<00:08:07.680> be<00:08:07.740> lazily<00:08:08.160> created<00:08:08.400> it'll<00:08:08.759> just<00:08:08.880> be<00:08:09.000> zero 00:08:09.770 --> 00:08:09.780 align:start position:0% to be lazily created it'll just be zero 00:08:09.780 --> 00:08:11.930 align:start position:0% to be lazily created it'll just be zero we<00:08:10.080> then<00:08:10.199> have<00:08:10.380> an<00:08:10.500> array<00:08:10.740> of<00:08:10.860> actions<00:08:11.340> where 00:08:11.930 --> 00:08:11.940 align:start position:0% we then have an array of actions where 00:08:11.940 --> 00:08:14.089 align:start position:0% we then have an array of actions where those<00:08:12.180> actions<00:08:12.539> are<00:08:12.660> Atomic<00:08:13.139> so<00:08:13.500> if<00:08:13.740> any<00:08:13.919> one 00:08:14.089 --> 00:08:14.099 align:start position:0% those actions are Atomic so if any one 00:08:14.099 --> 00:08:16.309 align:start position:0% those actions are Atomic so if any one of<00:08:14.220> these<00:08:14.520> actions<00:08:14.940> were<00:08:15.120> to<00:08:15.240> fail<00:08:15.539> then<00:08:16.139> they 00:08:16.309 --> 00:08:16.319 align:start position:0% of these actions were to fail then they 00:08:16.319 --> 00:08:17.990 align:start position:0% of these actions were to fail then they all<00:08:16.440> would<00:08:16.680> fail 00:08:17.990 --> 00:08:18.000 align:start position:0% all would fail 00:08:18.000 --> 00:08:19.790 align:start position:0% all would fail um<00:08:18.060> inside<00:08:18.300> of<00:08:18.539> that<00:08:18.660> you<00:08:18.960> can<00:08:19.080> specify<00:08:19.440> an<00:08:19.560> F 00:08:19.790 --> 00:08:19.800 align:start position:0% um inside of that you can specify an F 00:08:19.800 --> 00:08:21.650 align:start position:0% um inside of that you can specify an F value<00:08:20.039> as<00:08:20.280> part<00:08:20.460> of<00:08:20.580> that<00:08:20.699> the<00:08:21.300> contractor 00:08:21.650 --> 00:08:21.660 align:start position:0% value as part of that the contractor 00:08:21.660 --> 00:08:23.570 align:start position:0% value as part of that the contractor targeting<00:08:22.199> and<00:08:22.500> then<00:08:22.620> finally<00:08:22.919> the<00:08:23.099> encoded 00:08:23.570 --> 00:08:23.580 align:start position:0% targeting and then finally the encoded 00:08:23.580 --> 00:08:25.610 align:start position:0% targeting and then finally the encoded function<00:08:23.879> that<00:08:24.180> you'll<00:08:24.300> send<00:08:24.479> over 00:08:25.610 --> 00:08:25.620 align:start position:0% function that you'll send over 00:08:25.620 --> 00:08:27.710 align:start position:0% function that you'll send over in<00:08:26.220> the<00:08:26.340> case<00:08:26.460> of<00:08:26.639> the<00:08:26.819> example<00:08:27.120> we<00:08:27.360> have<00:08:27.479> up 00:08:27.710 --> 00:08:27.720 align:start position:0% in the case of the example we have up 00:08:27.720 --> 00:08:30.770 align:start position:0% in the case of the example we have up here<00:08:28.020> we're<00:08:28.860> doing<00:08:29.160> an<00:08:29.639> approve<00:08:30.120> and<00:08:30.300> a<00:08:30.479> swap 00:08:30.770 --> 00:08:30.780 align:start position:0% here we're doing an approve and a swap 00:08:30.780 --> 00:08:33.110 align:start position:0% here we're doing an approve and a swap on<00:08:31.020> a<00:08:31.139> simulated<00:08:31.500> decks<00:08:32.039> and<00:08:32.580> instead<00:08:32.940> of<00:08:33.000> it 00:08:33.110 --> 00:08:33.120 align:start position:0% on a simulated decks and instead of it 00:08:33.120 --> 00:08:34.670 align:start position:0% on a simulated decks and instead of it having<00:08:33.240> to<00:08:33.419> be<00:08:33.539> two<00:08:33.779> separate<00:08:34.140> transactions 00:08:34.670 --> 00:08:34.680 align:start position:0% having to be two separate transactions 00:08:34.680 --> 00:08:37.310 align:start position:0% having to be two separate transactions we<00:08:34.860> can<00:08:34.979> just<00:08:35.099> merge<00:08:35.399> it<00:08:35.459> into<00:08:35.700> one<00:08:36.080> via<00:08:37.080> that 00:08:37.310 --> 00:08:37.320 align:start position:0% we can just merge it into one via that 00:08:37.320 --> 00:08:39.350 align:start position:0% we can just merge it into one via that format 00:08:39.350 --> 00:08:39.360 align:start position:0% format 00:08:39.360 --> 00:08:41.089 align:start position:0% format um using<00:08:39.839> building<00:08:40.020> on<00:08:40.320> top<00:08:40.500> of<00:08:40.620> this<00:08:40.740> we've 00:08:41.089 --> 00:08:41.099 align:start position:0% um using building on top of this we've 00:08:41.099 --> 00:08:42.709 align:start position:0% um using building on top of this we've built<00:08:41.279> a<00:08:41.339> prototype<00:08:41.640> uh<00:08:42.000> browser<00:08:42.360> extension 00:08:42.709 --> 00:08:42.719 align:start position:0% built a prototype uh browser extension 00:08:42.719 --> 00:08:44.209 align:start position:0% built a prototype uh browser extension wallet<00:08:43.020> called<00:08:43.200> quill 00:08:44.209 --> 00:08:44.219 align:start position:0% wallet called quill 00:08:44.219 --> 00:08:46.310 align:start position:0% wallet called quill and 00:08:46.310 --> 00:08:46.320 align:start position:0% and 00:08:46.320 --> 00:08:49.070 align:start position:0% and fast<00:08:46.920> cool<00:08:47.399> called<00:08:47.880> quill<00:08:48.360> uh<00:08:48.779> with<00:08:48.899> Andrew 00:08:49.070 --> 00:08:49.080 align:start position:0% fast cool called quill uh with Andrew 00:08:49.080 --> 00:08:53.150 align:start position:0% fast cool called quill uh with Andrew and<00:08:49.320> katuk<00:08:49.740> and 00:08:53.150 --> 00:08:53.160 align:start position:0% 00:08:53.160 --> 00:08:55.610 align:start position:0% and<00:08:53.580> as<00:08:54.000> you<00:08:54.120> can<00:08:54.240> see<00:08:54.360> here<00:08:54.660> in<00:08:54.959> an<00:08:55.080> example<00:08:55.380> we 00:08:55.610 --> 00:08:55.620 align:start position:0% and as you can see here in an example we 00:08:55.620 --> 00:08:57.290 align:start position:0% and as you can see here in an example we have<00:08:55.740> a<00:08:55.860> standard<00:08:56.100> transaction<00:08:56.580> confirmation 00:08:57.290 --> 00:08:57.300 align:start position:0% have a standard transaction confirmation 00:08:57.300 --> 00:08:59.210 align:start position:0% have a standard transaction confirmation which<00:08:57.660> contains<00:08:58.140> three<00:08:58.380> actions<00:08:58.860> inside<00:08:58.980> of 00:08:59.210 --> 00:08:59.220 align:start position:0% which contains three actions inside of 00:08:59.220 --> 00:09:00.710 align:start position:0% which contains three actions inside of it<00:08:59.339> one<00:08:59.640> of<00:08:59.700> them<00:08:59.820> in<00:08:59.940> the<00:09:00.060> middle<00:09:00.180> being<00:09:00.480> an 00:09:00.710 --> 00:09:00.720 align:start position:0% it one of them in the middle being an 00:09:00.720 --> 00:09:02.990 align:start position:0% it one of them in the middle being an approved<00:09:01.200> so<00:09:01.800> instead<00:09:02.100> of<00:09:02.160> a<00:09:02.279> user<00:09:02.580> having<00:09:02.760> to 00:09:02.990 --> 00:09:03.000 align:start position:0% approved so instead of a user having to 00:09:03.000 --> 00:09:05.389 align:start position:0% approved so instead of a user having to go<00:09:03.240> in<00:09:03.540> and<00:09:04.320> separately<00:09:04.680> run<00:09:04.860> the<00:09:05.040> transaction 00:09:05.389 --> 00:09:05.399 align:start position:0% go in and separately run the transaction 00:09:05.399 --> 00:09:07.310 align:start position:0% go in and separately run the transaction for<00:09:05.640> approve<00:09:06.060> and<00:09:06.240> say<00:09:06.420> transfer<00:09:06.959> and 00:09:07.310 --> 00:09:07.320 align:start position:0% for approve and say transfer and 00:09:07.320 --> 00:09:08.870 align:start position:0% for approve and say transfer and something<00:09:07.500> else<00:09:07.800> we<00:09:08.100> can<00:09:08.220> do<00:09:08.339> it<00:09:08.459> all<00:09:08.580> in<00:09:08.700> one 00:09:08.870 --> 00:09:08.880 align:start position:0% something else we can do it all in one 00:09:08.880 --> 00:09:10.610 align:start position:0% something else we can do it all in one and<00:09:09.000> have<00:09:09.180> just<00:09:09.420> one<00:09:09.660> confirmation<00:09:10.140> dialogue 00:09:10.610 --> 00:09:10.620 align:start position:0% and have just one confirmation dialogue 00:09:10.620 --> 00:09:13.430 align:start position:0% and have just one confirmation dialogue pop<00:09:10.860> up<00:09:11.040> to<00:09:11.279> them 00:09:13.430 --> 00:09:13.440 align:start position:0% 00:09:13.440 --> 00:09:15.050 align:start position:0% um<00:09:13.500> if<00:09:13.740> you<00:09:13.860> want<00:09:13.980> to<00:09:14.040> learn<00:09:14.160> more<00:09:14.399> about<00:09:14.700> how 00:09:15.050 --> 00:09:15.060 align:start position:0% um if you want to learn more about how 00:09:15.060 --> 00:09:16.370 align:start position:0% um if you want to learn more about how we<00:09:15.180> have<00:09:15.420> this<00:09:15.600> set<00:09:15.779> up<00:09:15.899> and<00:09:16.019> how<00:09:16.200> you<00:09:16.320> can 00:09:16.370 --> 00:09:16.380 align:start position:0% we have this set up and how you can 00:09:16.380 --> 00:09:18.050 align:start position:0% we have this set up and how you can integrate<00:09:16.680> the<00:09:16.800> D<00:09:16.920> app<00:09:17.100> into<00:09:17.220> it<00:09:17.459> right<00:09:17.580> now<00:09:18.060> um 00:09:18.050 --> 00:09:18.060 align:start position:0% integrate the D app into it right now um 00:09:18.060 --> 00:09:19.430 align:start position:0% integrate the D app into it right now um You<00:09:18.180> can<00:09:18.300> find<00:09:18.420> out<00:09:18.540> more<00:09:18.720> of<00:09:18.839> the<00:09:19.019> link<00:09:19.140> below 00:09:19.430 --> 00:09:19.440 align:start position:0% You can find out more of the link below 00:09:19.440 --> 00:09:21.470 align:start position:0% You can find out more of the link below in<00:09:19.680> our<00:09:19.800> GitHub<00:09:20.220> repo<00:09:20.700> on<00:09:20.880> how<00:09:21.060> to<00:09:21.120> integrate 00:09:21.470 --> 00:09:21.480 align:start position:0% in our GitHub repo on how to integrate 00:09:21.480 --> 00:09:22.550 align:start position:0% in our GitHub repo on how to integrate that<00:09:21.600> in 00:09:22.550 --> 00:09:22.560 align:start position:0% that in 00:09:22.560 --> 00:09:24.350 align:start position:0% that in so<00:09:23.100> next<00:09:23.519> we'll<00:09:23.700> get<00:09:23.820> into<00:09:23.940> sponsor 00:09:24.350 --> 00:09:24.360 align:start position:0% so next we'll get into sponsor 00:09:24.360 --> 00:09:26.750 align:start position:0% so next we'll get into sponsor transactions 00:09:26.750 --> 00:09:26.760 align:start position:0% transactions 00:09:26.760 --> 00:09:29.090 align:start position:0% transactions so<00:09:27.420> right<00:09:27.959> now<00:09:28.080> the<00:09:28.260> pattern<00:09:28.560> we're<00:09:28.680> using<00:09:28.920> to 00:09:29.090 --> 00:09:29.100 align:start position:0% so right now the pattern we're using to 00:09:29.100 --> 00:09:31.490 align:start position:0% so right now the pattern we're using to have<00:09:29.220> these<00:09:29.459> sponsored<00:09:29.880> transactions<00:09:30.540> is<00:09:31.260> to 00:09:31.490 --> 00:09:31.500 align:start position:0% have these sponsored transactions is to 00:09:31.500 --> 00:09:33.230 align:start position:0% have these sponsored transactions is to have<00:09:31.740> our<00:09:31.980> normal<00:09:32.220> flow<00:09:32.580> but<00:09:32.880> in<00:09:33.000> the<00:09:33.120> middle 00:09:33.230 --> 00:09:33.240 align:start position:0% have our normal flow but in the middle 00:09:33.240 --> 00:09:34.970 align:start position:0% have our normal flow but in the middle we're<00:09:33.720> injecting<00:09:34.200> in<00:09:34.500> this<00:09:34.620> top<00:09:34.800> Center 00:09:34.970 --> 00:09:34.980 align:start position:0% we're injecting in this top Center 00:09:34.980 --> 00:09:36.650 align:start position:0% we're injecting in this top Center portion<00:09:35.399> the<00:09:35.580> aggregator<00:09:36.000> an<00:09:36.240> aggregator 00:09:36.650 --> 00:09:36.660 align:start position:0% portion the aggregator an aggregator 00:09:36.660 --> 00:09:38.690 align:start position:0% portion the aggregator an aggregator proxy<00:09:37.140> which<00:09:37.740> essentially<00:09:38.100> is<00:09:38.220> taking<00:09:38.399> those 00:09:38.690 --> 00:09:38.700 align:start position:0% proxy which essentially is taking those 00:09:38.700 --> 00:09:40.250 align:start position:0% proxy which essentially is taking those operations<00:09:39.120> we<00:09:39.420> would<00:09:39.540> normally<00:09:39.779> submit<00:09:40.080> to 00:09:40.250 --> 00:09:40.260 align:start position:0% operations we would normally submit to 00:09:40.260 --> 00:09:43.310 align:start position:0% operations we would normally submit to an<00:09:40.500> aggregator<00:09:41.060> and<00:09:42.060> is<00:09:42.480> instead<00:09:42.839> sending 00:09:43.310 --> 00:09:43.320 align:start position:0% an aggregator and is instead sending 00:09:43.320 --> 00:09:45.410 align:start position:0% an aggregator and is instead sending them<00:09:43.440> to<00:09:43.620> it<00:09:43.800> where<00:09:44.160> it<00:09:44.279> qualifies<00:09:44.760> to<00:09:45.060> see<00:09:45.240> if 00:09:45.410 --> 00:09:45.420 align:start position:0% them to it where it qualifies to see if 00:09:45.420 --> 00:09:48.829 align:start position:0% them to it where it qualifies to see if they're<00:09:45.660> uh<00:09:46.140> if<00:09:46.560> they<00:09:46.680> can<00:09:46.860> be<00:09:47.100> you<00:09:47.459> funded<00:09:48.000> uh 00:09:48.829 --> 00:09:48.839 align:start position:0% they're uh if they can be you funded uh 00:09:48.839 --> 00:09:51.470 align:start position:0% they're uh if they can be you funded uh for<00:09:49.260> free<00:09:49.500> gas<00:09:49.740> basically<00:09:50.279> and<00:09:51.000> so<00:09:51.120> then<00:09:51.300> that 00:09:51.470 --> 00:09:51.480 align:start position:0% for free gas basically and so then that 00:09:51.480 --> 00:09:53.030 align:start position:0% for free gas basically and so then that aggregator<00:09:51.899> proxy<00:09:52.380> will<00:09:52.500> add<00:09:52.680> that<00:09:52.860> payment 00:09:53.030 --> 00:09:53.040 align:start position:0% aggregator proxy will add that payment 00:09:53.040 --> 00:09:56.630 align:start position:0% aggregator proxy will add that payment bundle<00:09:53.640> in<00:09:54.140> on<00:09:55.140> uh<00:09:55.620> in<00:09:55.920> there<00:09:56.040> and<00:09:56.220> then<00:09:56.339> submit 00:09:56.630 --> 00:09:56.640 align:start position:0% bundle in on uh in there and then submit 00:09:56.640 --> 00:09:57.710 align:start position:0% bundle in on uh in there and then submit it<00:09:56.700> to<00:09:56.820> the<00:09:56.940> normal<00:09:57.060> aggregator<00:09:57.480> which 00:09:57.710 --> 00:09:57.720 align:start position:0% it to the normal aggregator which 00:09:57.720 --> 00:09:59.930 align:start position:0% it to the normal aggregator which requires<00:09:58.140> the<00:09:58.320> fee<00:09:58.620> and<00:09:59.220> this<00:09:59.279> allows<00:09:59.640> for<00:09:59.760> us 00:09:59.930 --> 00:09:59.940 align:start position:0% requires the fee and this allows for us 00:09:59.940 --> 00:10:03.410 align:start position:0% requires the fee and this allows for us to<00:10:00.120> have<00:10:00.300> those<00:10:00.660> gasless<00:10:01.140> transactions 00:10:03.410 --> 00:10:03.420 align:start position:0% to have those gasless transactions 00:10:03.420 --> 00:10:06.470 align:start position:0% to have those gasless transactions our<00:10:03.899> teammate<00:10:04.200> John<00:10:04.500> has<00:10:04.980> built<00:10:05.339> a<00:10:05.820> uh<00:10:06.240> very 00:10:06.470 --> 00:10:06.480 align:start position:0% our teammate John has built a uh very 00:10:06.480 --> 00:10:08.570 align:start position:0% our teammate John has built a uh very cool<00:10:06.600> demo<00:10:06.959> using<00:10:07.320> uh<00:10:07.620> scaffoldeth<00:10:08.279> for<00:10:08.459> the 00:10:08.570 --> 00:10:08.580 align:start position:0% cool demo using uh scaffoldeth for the 00:10:08.580 --> 00:10:10.610 align:start position:0% cool demo using uh scaffoldeth for the scaffoldeth<00:10:09.060> community<00:10:09.300> which<00:10:10.080> is<00:10:10.260> a<00:10:10.380> single 00:10:10.610 --> 00:10:10.620 align:start position:0% scaffoldeth community which is a single 00:10:10.620 --> 00:10:13.370 align:start position:0% scaffoldeth community which is a single pool<00:10:10.740> Dex<00:10:11.240> as<00:10:12.240> you<00:10:12.360> can<00:10:12.420> see<00:10:12.600> here<00:10:12.779> it's<00:10:13.019> a<00:10:13.200> just 00:10:13.370 --> 00:10:13.380 align:start position:0% pool Dex as you can see here it's a just 00:10:13.380 --> 00:10:15.470 align:start position:0% pool Dex as you can see here it's a just single<00:10:13.800> pool<00:10:14.040> decks<00:10:14.459> with<00:10:14.580> a<00:10:14.700> swap 00:10:15.470 --> 00:10:15.480 align:start position:0% single pool decks with a swap 00:10:15.480 --> 00:10:17.210 align:start position:0% single pool decks with a swap um<00:10:15.540> it<00:10:15.720> does<00:10:15.779> use<00:10:15.959> the<00:10:16.140> multi-action<00:10:16.740> as<00:10:17.100> well 00:10:17.210 --> 00:10:17.220 align:start position:0% um it does use the multi-action as well 00:10:17.220 --> 00:10:19.610 align:start position:0% um it does use the multi-action as well to<00:10:17.459> do<00:10:17.580> the<00:10:17.760> approve<00:10:18.240> and<00:10:18.600> the<00:10:18.779> swap<00:10:19.080> inside<00:10:19.320> of 00:10:19.610 --> 00:10:19.620 align:start position:0% to do the approve and the swap inside of 00:10:19.620 --> 00:10:21.889 align:start position:0% to do the approve and the swap inside of it<00:10:19.740> and<00:10:20.519> then<00:10:20.580> it<00:10:20.820> all<00:10:20.940> runs<00:10:21.240> inside<00:10:21.480> of<00:10:21.779> the 00:10:21.889 --> 00:10:21.899 align:start position:0% it and then it all runs inside of the 00:10:21.899 --> 00:10:24.530 align:start position:0% it and then it all runs inside of the browser<00:10:22.380> with<00:10:22.920> no<00:10:23.279> need<00:10:23.760> for<00:10:23.940> like<00:10:24.180> upfront 00:10:24.530 --> 00:10:24.540 align:start position:0% browser with no need for like upfront 00:10:24.540 --> 00:10:26.329 align:start position:0% browser with no need for like upfront gas<00:10:24.720> because<00:10:25.019> the<00:10:25.380> aggregator<00:10:25.800> proxy<00:10:26.160> is 00:10:26.329 --> 00:10:26.339 align:start position:0% gas because the aggregator proxy is 00:10:26.339 --> 00:10:28.430 align:start position:0% gas because the aggregator proxy is going<00:10:26.459> to<00:10:26.580> subsidize<00:10:27.120> it<00:10:27.300> and<00:10:27.899> so<00:10:28.080> that<00:10:28.200> allows 00:10:28.430 --> 00:10:28.440 align:start position:0% going to subsidize it and so that allows 00:10:28.440 --> 00:10:29.990 align:start position:0% going to subsidize it and so that allows for<00:10:28.500> free<00:10:28.680> transaction<00:10:29.100> you<00:10:29.580> can<00:10:29.700> find<00:10:29.820> out 00:10:29.990 --> 00:10:30.000 align:start position:0% for free transaction you can find out 00:10:30.000 --> 00:10:31.670 align:start position:0% for free transaction you can find out more<00:10:30.180> at<00:10:30.480> this<00:10:30.660> uh<00:10:30.779> the<00:10:30.959> GitHub<00:10:31.200> repo<00:10:31.560> below 00:10:31.670 --> 00:10:31.680 align:start position:0% more at this uh the GitHub repo below 00:10:31.680 --> 00:10:33.829 align:start position:0% more at this uh the GitHub repo below and<00:10:31.980> it<00:10:32.160> also<00:10:32.399> is<00:10:32.519> deployed<00:10:33.000> at<00:10:33.240> single<00:10:33.660> pool 00:10:33.829 --> 00:10:33.839 align:start position:0% and it also is deployed at single pool 00:10:33.839 --> 00:10:40.190 align:start position:0% and it also is deployed at single pool Dex<00:10:34.440> react<00:10:34.980> app.versel.app 00:10:40.190 --> 00:10:40.200 align:start position:0% 00:10:40.200 --> 00:10:41.630 align:start position:0% um we're<00:10:40.380> also<00:10:40.680> looking<00:10:40.860> into<00:10:41.100> doing<00:10:41.399> this 00:10:41.630 --> 00:10:41.640 align:start position:0% um we're also looking into doing this 00:10:41.640 --> 00:10:43.910 align:start position:0% um we're also looking into doing this directly<00:10:42.000> via<00:10:42.360> a<00:10:42.540> contract 00:10:43.910 --> 00:10:43.920 align:start position:0% directly via a contract 00:10:43.920 --> 00:10:45.050 align:start position:0% directly via a contract um the<00:10:44.100> way<00:10:44.160> the<00:10:44.279> aggregator<00:10:44.700> currently 00:10:45.050 --> 00:10:45.060 align:start position:0% um the way the aggregator currently 00:10:45.060 --> 00:10:47.329 align:start position:0% um the way the aggregator currently works<00:10:45.480> is<00:10:45.779> when<00:10:45.899> it<00:10:46.019> receives<00:10:46.320> a<00:10:46.560> bundle<00:10:46.920> it's 00:10:47.329 --> 00:10:47.339 align:start position:0% works is when it receives a bundle it's 00:10:47.339 --> 00:10:50.389 align:start position:0% works is when it receives a bundle it's going<00:10:47.579> to<00:10:47.700> actually<00:10:47.940> introspect<00:10:48.720> and<00:10:48.959> look<00:10:49.260> at 00:10:50.389 --> 00:10:50.399 align:start position:0% going to actually introspect and look at 00:10:50.399 --> 00:10:52.130 align:start position:0% going to actually introspect and look at um whether<00:10:50.760> when<00:10:51.060> it<00:10:51.180> stimulates<00:10:51.720> executing 00:10:52.130 --> 00:10:52.140 align:start position:0% um whether when it stimulates executing 00:10:52.140 --> 00:10:54.170 align:start position:0% um whether when it stimulates executing that<00:10:52.320> transaction<00:10:52.740> if<00:10:53.040> it<00:10:53.160> gets<00:10:53.459> paid<00:10:53.760> either 00:10:54.170 --> 00:10:54.180 align:start position:0% that transaction if it gets paid either 00:10:54.180 --> 00:10:57.410 align:start position:0% that transaction if it gets paid either in<00:10:54.420> F<00:10:54.660> or<00:10:55.140> we<00:10:55.260> also<00:10:55.500> allow<00:10:55.680> erc20<00:10:56.279> tokens 00:10:57.410 --> 00:10:57.420 align:start position:0% in F or we also allow erc20 tokens 00:10:57.420 --> 00:10:59.150 align:start position:0% in F or we also allow erc20 tokens if<00:10:57.779> it<00:10:57.899> sees<00:10:58.140> that<00:10:58.260> it<00:10:58.380> happens<00:10:58.560> it<00:10:59.040> will 00:10:59.150 --> 00:10:59.160 align:start position:0% if it sees that it happens it will 00:10:59.160 --> 00:11:00.949 align:start position:0% if it sees that it happens it will include<00:10:59.880> it<00:11:00.000> in<00:11:00.180> the<00:11:00.300> bundle<00:11:00.600> it's<00:11:00.720> going<00:11:00.839> to 00:11:00.949 --> 00:11:00.959 align:start position:0% include it in the bundle it's going to 00:11:00.959 --> 00:11:03.230 align:start position:0% include it in the bundle it's going to submit<00:11:01.200> to<00:11:01.320> layer<00:11:01.560> 2.<00:11:02.279> so<00:11:02.640> one<00:11:02.760> of<00:11:02.940> the<00:11:03.000> ways 00:11:03.230 --> 00:11:03.240 align:start position:0% submit to layer 2. so one of the ways 00:11:03.240 --> 00:11:04.610 align:start position:0% submit to layer 2. so one of the ways you<00:11:03.420> can<00:11:03.540> take<00:11:03.660> advantage<00:11:04.019> of<00:11:04.079> this<00:11:04.200> inside<00:11:04.380> of 00:11:04.610 --> 00:11:04.620 align:start position:0% you can take advantage of this inside of 00:11:04.620 --> 00:11:06.230 align:start position:0% you can take advantage of this inside of a<00:11:04.740> contract<00:11:05.100> is<00:11:05.519> just<00:11:05.700> have<00:11:05.880> it<00:11:06.060> pay 00:11:06.230 --> 00:11:06.240 align:start position:0% a contract is just have it pay 00:11:06.240 --> 00:11:07.970 align:start position:0% a contract is just have it pay transaction<00:11:06.720> origin 00:11:07.970 --> 00:11:07.980 align:start position:0% transaction origin 00:11:07.980 --> 00:11:10.970 align:start position:0% transaction origin and<00:11:08.579> then<00:11:08.760> the<00:11:08.940> every<00:11:09.060> year<00:11:09.300> will<00:11:09.480> get<00:11:09.600> paid 00:11:10.970 --> 00:11:10.980 align:start position:0% and then the every year will get paid 00:11:10.980 --> 00:11:12.710 align:start position:0% and then the every year will get paid um<00:11:11.040> you<00:11:11.459> can<00:11:11.519> also<00:11:11.760> do<00:11:12.000> things<00:11:12.240> potentially 00:11:12.710 --> 00:11:12.720 align:start position:0% um you can also do things potentially 00:11:12.720 --> 00:11:15.350 align:start position:0% um you can also do things potentially like<00:11:13.019> gate<00:11:13.440> this<00:11:13.920> payment<00:11:14.100> via<00:11:14.760> an<00:11:14.940> allow<00:11:15.180> list 00:11:15.350 --> 00:11:15.360 align:start position:0% like gate this payment via an allow list 00:11:15.360 --> 00:11:17.569 align:start position:0% like gate this payment via an allow list ownership<00:11:16.200> of<00:11:16.440> an<00:11:16.560> nft<00:11:16.800> or<00:11:17.100> potentially<00:11:17.399> even 00:11:17.569 --> 00:11:17.579 align:start position:0% ownership of an nft or potentially even 00:11:17.579 --> 00:11:19.970 align:start position:0% ownership of an nft or potentially even something<00:11:17.820> like<00:11:18.000> a<00:11:18.180> zkp<00:11:18.660> proof<00:11:19.440> so<00:11:19.740> that<00:11:19.860> you 00:11:19.970 --> 00:11:19.980 align:start position:0% something like a zkp proof so that you 00:11:19.980 --> 00:11:21.769 align:start position:0% something like a zkp proof so that you can<00:11:20.100> only<00:11:20.279> allow<00:11:20.700> certain<00:11:21.180> people<00:11:21.420> to<00:11:21.600> have 00:11:21.769 --> 00:11:21.779 align:start position:0% can only allow certain people to have 00:11:21.779 --> 00:11:24.949 align:start position:0% can only allow certain people to have access<00:11:21.959> to<00:11:22.200> that<00:11:22.640> this<00:11:23.640> also<00:11:23.940> allows<00:11:24.360> anyone 00:11:24.949 --> 00:11:24.959 align:start position:0% access to that this also allows anyone 00:11:24.959 --> 00:11:26.150 align:start position:0% access to that this also allows anyone potentially<00:11:25.320> to<00:11:25.500> be<00:11:25.560> a<00:11:25.680> bundler<00:11:25.980> and 00:11:26.150 --> 00:11:26.160 align:start position:0% potentially to be a bundler and 00:11:26.160 --> 00:11:27.949 align:start position:0% potentially to be a bundler and submitter<00:11:26.399> potentially<00:11:26.880> even<00:11:27.000> Mev<00:11:27.540> Bots<00:11:27.779> that 00:11:27.949 --> 00:11:27.959 align:start position:0% submitter potentially even Mev Bots that 00:11:27.959 --> 00:11:30.410 align:start position:0% submitter potentially even Mev Bots that are<00:11:28.079> looking<00:11:28.200> for<00:11:28.440> profits<00:11:28.980> and<00:11:29.579> be<00:11:29.760> able<00:11:29.940> to 00:11:30.410 --> 00:11:30.420 align:start position:0% are looking for profits and be able to 00:11:30.420 --> 00:11:31.610 align:start position:0% are looking for profits and be able to um submit<00:11:30.779> those<00:11:30.899> in<00:11:31.079> so<00:11:31.260> that<00:11:31.380> you<00:11:31.500> don't 00:11:31.610 --> 00:11:31.620 align:start position:0% um submit those in so that you don't 00:11:31.620 --> 00:11:33.290 align:start position:0% um submit those in so that you don't have<00:11:31.740> to<00:11:31.860> go<00:11:32.040> through<00:11:32.279> a<00:11:32.519> specific<00:11:32.700> aggregator 00:11:33.290 --> 00:11:33.300 align:start position:0% have to go through a specific aggregator 00:11:33.300 --> 00:11:35.210 align:start position:0% have to go through a specific aggregator and<00:11:33.600> you<00:11:33.720> could<00:11:33.839> submit<00:11:34.200> to<00:11:34.320> say<00:11:34.560> just<00:11:35.040> a 00:11:35.210 --> 00:11:35.220 align:start position:0% and you could submit to say just a 00:11:35.220 --> 00:11:38.690 align:start position:0% and you could submit to say just a general<00:11:35.399> say<00:11:35.700> bundle<00:11:36.120> mempool<00:11:36.540> going<00:11:37.200> on<00:11:37.440> top 00:11:38.690 --> 00:11:38.700 align:start position:0% general say bundle mempool going on top 00:11:38.700 --> 00:11:39.769 align:start position:0% general say bundle mempool going on top um<00:11:38.760> we<00:11:38.880> still<00:11:39.060> have<00:11:39.180> more<00:11:39.300> research<00:11:39.540> to<00:11:39.660> be 00:11:39.769 --> 00:11:39.779 align:start position:0% um we still have more research to be 00:11:39.779 --> 00:11:41.269 align:start position:0% um we still have more research to be done<00:11:39.899> to<00:11:40.140> figure<00:11:40.380> this<00:11:40.620> out<00:11:40.740> but<00:11:40.920> we<00:11:41.100> believe 00:11:41.269 --> 00:11:41.279 align:start position:0% done to figure this out but we believe 00:11:41.279 --> 00:11:42.889 align:start position:0% done to figure this out but we believe it<00:11:41.519> should<00:11:41.700> be<00:11:41.880> uh<00:11:42.120> pretty<00:11:42.360> feasible<00:11:42.779> and 00:11:42.889 --> 00:11:42.899 align:start position:0% it should be uh pretty feasible and 00:11:42.899 --> 00:11:46.310 align:start position:0% it should be uh pretty feasible and possible<00:11:43.260> to<00:11:43.500> do 00:11:46.310 --> 00:11:46.320 align:start position:0% 00:11:46.320 --> 00:11:47.509 align:start position:0% all<00:11:46.740> right<00:11:46.860> and<00:11:47.100> now<00:11:47.220> I'm<00:11:47.279> going<00:11:47.339> to<00:11:47.399> hand 00:11:47.509 --> 00:11:47.519 align:start position:0% all right and now I'm going to hand 00:11:47.519 --> 00:11:49.190 align:start position:0% all right and now I'm going to hand things<00:11:47.700> over<00:11:47.820> to<00:11:48.000> my<00:11:48.180> teammate<00:11:48.540> James<00:11:48.779> James 00:11:49.190 --> 00:11:49.200 align:start position:0% things over to my teammate James James 00:11:49.200 --> 00:11:51.530 align:start position:0% things over to my teammate James James thank<00:11:49.980> you<00:11:50.160> yeah<00:11:50.880> you've<00:11:51.120> done<00:11:51.240> pretty<00:11:51.420> well 00:11:51.530 --> 00:11:51.540 align:start position:0% thank you yeah you've done pretty well 00:11:51.540 --> 00:11:53.269 align:start position:0% thank you yeah you've done pretty well given<00:11:51.959> uh<00:11:52.260> the<00:11:52.500> slides<00:11:52.800> have<00:11:52.920> been<00:11:53.040> a<00:11:53.220> bit 00:11:53.269 --> 00:11:53.279 align:start position:0% given uh the slides have been a bit 00:11:53.279 --> 00:11:55.130 align:start position:0% given uh the slides have been a bit often<00:11:53.760> we've<00:11:54.000> just<00:11:54.120> lost<00:11:54.240> our<00:11:54.480> speaker<00:11:54.660> notes 00:11:55.130 --> 00:11:55.140 align:start position:0% often we've just lost our speaker notes 00:11:55.140 --> 00:11:56.750 align:start position:0% often we've just lost our speaker notes but<00:11:55.320> okay 00:11:56.750 --> 00:11:56.760 align:start position:0% but okay 00:11:56.760 --> 00:11:59.509 align:start position:0% but okay uh<00:11:57.360> yep<00:11:57.660> so<00:11:57.839> with<00:11:57.959> recovery<00:11:58.980> um<00:11:59.040> it's<00:11:59.279> kind<00:11:59.399> of 00:11:59.509 --> 00:11:59.519 align:start position:0% uh yep so with recovery um it's kind of 00:11:59.519 --> 00:12:01.550 align:start position:0% uh yep so with recovery um it's kind of catastrophic<00:12:00.060> with<00:12:00.300> an<00:12:00.420> AOA<00:12:00.839> uh<00:12:01.260> if<00:12:01.500> your 00:12:01.550 --> 00:12:01.560 align:start position:0% catastrophic with an AOA uh if your 00:12:01.560 --> 00:12:02.690 align:start position:0% catastrophic with an AOA uh if your private<00:12:01.860> key<00:12:01.920> is<00:12:02.100> compromised<00:12:02.579> you're 00:12:02.690 --> 00:12:02.700 align:start position:0% private key is compromised you're 00:12:02.700 --> 00:12:04.370 align:start position:0% private key is compromised you're basically<00:12:02.940> racing<00:12:03.300> against<00:12:03.420> an<00:12:03.720> attacker<00:12:04.140> to 00:12:04.370 --> 00:12:04.380 align:start position:0% basically racing against an attacker to 00:12:04.380 --> 00:12:06.470 align:start position:0% basically racing against an attacker to secure<00:12:04.680> your<00:12:04.800> assets<00:12:05.160> but<00:12:05.760> with<00:12:06.060> a<00:12:06.300> smart 00:12:06.470 --> 00:12:06.480 align:start position:0% secure your assets but with a smart 00:12:06.480 --> 00:12:07.970 align:start position:0% secure your assets but with a smart contract<00:12:06.779> wallet<00:12:07.079> we've<00:12:07.320> implemented<00:12:07.740> a 00:12:07.970 --> 00:12:07.980 align:start position:0% contract wallet we've implemented a 00:12:07.980 --> 00:12:10.490 align:start position:0% contract wallet we've implemented a recover<00:12:08.279> function<00:12:08.760> that<00:12:09.720> requires<00:12:10.140> basically 00:12:10.490 --> 00:12:10.500 align:start position:0% recover function that requires basically 00:12:10.500 --> 00:12:13.670 align:start position:0% recover function that requires basically setting<00:12:10.860> a<00:12:11.040> recovery<00:12:11.399> hash<00:12:11.760> from<00:12:12.420> that<00:12:12.540> hash 00:12:13.670 --> 00:12:13.680 align:start position:0% setting a recovery hash from that hash 00:12:13.680 --> 00:12:16.069 align:start position:0% setting a recovery hash from that hash yeah<00:12:14.100> we've<00:12:14.279> got<00:12:14.399> the<00:12:14.519> notes<00:12:14.820> now<00:12:15.360> behind<00:12:15.959> the 00:12:16.069 --> 00:12:16.079 align:start position:0% yeah we've got the notes now behind the 00:12:16.079 --> 00:12:16.970 align:start position:0% yeah we've got the notes now behind the timer 00:12:16.970 --> 00:12:16.980 align:start position:0% timer 00:12:16.980 --> 00:12:18.889 align:start position:0% timer um<00:12:17.100> yeah<00:12:17.220> so<00:12:17.399> with<00:12:17.579> a<00:12:17.760> recovery<00:12:18.120> hash<00:12:18.360> it<00:12:18.839> just 00:12:18.889 --> 00:12:18.899 align:start position:0% um yeah so with a recovery hash it just 00:12:18.899 --> 00:12:20.210 align:start position:0% um yeah so with a recovery hash it just consists<00:12:19.260> of<00:12:19.320> the<00:12:19.620> address<00:12:19.740> that<00:12:20.040> you're 00:12:20.210 --> 00:12:20.220 align:start position:0% consists of the address that you're 00:12:20.220 --> 00:12:22.610 align:start position:0% consists of the address that you're going<00:12:20.399> to<00:12:20.519> trust<00:12:20.760> to<00:12:21.420> call<00:12:22.019> the<00:12:22.260> recovery 00:12:22.610 --> 00:12:22.620 align:start position:0% going to trust to call the recovery 00:12:22.620 --> 00:12:23.750 align:start position:0% going to trust to call the recovery function 00:12:23.750 --> 00:12:23.760 align:start position:0% function 00:12:23.760 --> 00:12:25.670 align:start position:0% function um<00:12:23.880> and<00:12:24.240> the<00:12:24.600> the<00:12:24.779> hash<00:12:25.019> of<00:12:25.140> the<00:12:25.260> wall<00:12:25.380> the 00:12:25.670 --> 00:12:25.680 align:start position:0% um and the the hash of the wall the 00:12:25.680 --> 00:12:26.690 align:start position:0% um and the the hash of the wall the wallet's<00:12:26.100> public<00:12:26.160> key<00:12:26.399> that<00:12:26.579> you're 00:12:26.690 --> 00:12:26.700 align:start position:0% wallet's public key that you're 00:12:26.700 --> 00:12:29.269 align:start position:0% wallet's public key that you're addressing<00:12:27.240> and<00:12:27.480> some<00:12:27.600> salt<00:12:27.839> so<00:12:28.260> that<00:12:28.500> you 00:12:29.269 --> 00:12:29.279 align:start position:0% addressing and some salt so that you 00:12:29.279 --> 00:12:30.710 align:start position:0% addressing and some salt so that you um<00:12:29.339> so<00:12:29.459> that<00:12:29.820> an<00:12:30.000> attacker<00:12:30.300> can't<00:12:30.480> actually 00:12:30.710 --> 00:12:30.720 align:start position:0% um so that an attacker can't actually 00:12:30.720 --> 00:12:33.530 align:start position:0% um so that an attacker can't actually deduce<00:12:31.320> your<00:12:31.680> recovery<00:12:32.519> um<00:12:32.519> address<00:12:32.820> or<00:12:33.300> the 00:12:33.530 --> 00:12:33.540 align:start position:0% deduce your recovery um address or the 00:12:33.540 --> 00:12:34.910 align:start position:0% deduce your recovery um address or the wallet<00:12:33.720> that<00:12:33.839> we'll<00:12:33.959> call<00:12:34.140> that<00:12:34.320> so<00:12:34.680> when<00:12:34.800> you 00:12:34.910 --> 00:12:34.920 align:start position:0% wallet that we'll call that so when you 00:12:34.920 --> 00:12:36.110 align:start position:0% wallet that we'll call that so when you do<00:12:34.980> call<00:12:35.160> recovery<00:12:35.579> you<00:12:35.700> pass<00:12:35.820> in<00:12:36.000> those 00:12:36.110 --> 00:12:36.120 align:start position:0% do call recovery you pass in those 00:12:36.120 --> 00:12:37.970 align:start position:0% do call recovery you pass in those parameters<00:12:36.600> and<00:12:36.779> you<00:12:36.959> are<00:12:37.079> the<00:12:37.200> caller<00:12:37.620> itself 00:12:37.970 --> 00:12:37.980 align:start position:0% parameters and you are the caller itself 00:12:37.980 --> 00:12:40.490 align:start position:0% parameters and you are the caller itself then<00:12:38.339> you<00:12:38.579> can<00:12:38.700> immediately<00:12:39.060> reset<00:12:39.899> your<00:12:40.079> BLS 00:12:40.490 --> 00:12:40.500 align:start position:0% then you can immediately reset your BLS 00:12:40.500 --> 00:12:44.030 align:start position:0% then you can immediately reset your BLS key<00:12:40.680> and<00:12:41.640> uh<00:12:42.180> yes<00:12:42.420> basically<00:12:43.019> stop<00:12:43.560> the 00:12:44.030 --> 00:12:44.040 align:start position:0% key and uh yes basically stop the 00:12:44.040 --> 00:12:45.769 align:start position:0% key and uh yes basically stop the attacker<00:12:44.339> who's<00:12:44.519> Set<00:12:44.820> uh<00:12:45.360> who<00:12:45.540> may<00:12:45.660> have 00:12:45.769 --> 00:12:45.779 align:start position:0% attacker who's Set uh who may have 00:12:45.779 --> 00:12:46.850 align:start position:0% attacker who's Set uh who may have attempted<00:12:46.139> to 00:12:46.850 --> 00:12:46.860 align:start position:0% attempted to 00:12:46.860 --> 00:12:48.470 align:start position:0% attempted to um take<00:12:47.399> some<00:12:47.519> of<00:12:47.639> your<00:12:47.700> assets<00:12:47.940> or<00:12:48.120> set<00:12:48.300> some 00:12:48.470 --> 00:12:48.480 align:start position:0% um take some of your assets or set some 00:12:48.480 --> 00:12:50.569 align:start position:0% um take some of your assets or set some of<00:12:48.600> the<00:12:48.660> other<00:12:48.839> functions<00:12:49.380> so<00:12:49.800> if<00:12:50.040> an<00:12:50.220> attacker 00:12:50.569 --> 00:12:50.579 align:start position:0% of the other functions so if an attacker 00:12:50.579 --> 00:12:52.550 align:start position:0% of the other functions so if an attacker steals<00:12:50.940> your<00:12:51.060> key<00:12:51.240> and<00:12:51.720> tries<00:12:51.899> to<00:12:52.079> reset<00:12:52.380> your 00:12:52.550 --> 00:12:52.560 align:start position:0% steals your key and tries to reset your 00:12:52.560 --> 00:12:54.290 align:start position:0% steals your key and tries to reset your key<00:12:52.740> they<00:12:53.279> can't<00:12:53.459> do<00:12:53.639> that<00:12:53.760> because<00:12:53.940> there's<00:12:54.120> a 00:12:54.290 --> 00:12:54.300 align:start position:0% key they can't do that because there's a 00:12:54.300 --> 00:12:55.730 align:start position:0% key they can't do that because there's a one-week<00:12:54.600> delay<00:12:54.839> in<00:12:54.959> setting<00:12:55.260> that<00:12:55.320> parameter 00:12:55.730 --> 00:12:55.740 align:start position:0% one-week delay in setting that parameter 00:12:55.740 --> 00:12:57.170 align:start position:0% one-week delay in setting that parameter with<00:12:56.220> your<00:12:56.339> recovery<00:12:56.700> you<00:12:56.880> can<00:12:56.940> do<00:12:57.060> that 00:12:57.170 --> 00:12:57.180 align:start position:0% with your recovery you can do that 00:12:57.180 --> 00:12:59.090 align:start position:0% with your recovery you can do that straight<00:12:57.420> away<00:12:57.600> so<00:12:57.959> as<00:12:58.139> soon<00:12:58.260> as<00:12:58.380> you<00:12:58.500> see<00:12:58.740> a 00:12:59.090 --> 00:12:59.100 align:start position:0% straight away so as soon as you see a 00:12:59.100 --> 00:12:59.990 align:start position:0% straight away so as soon as you see a problem 00:12:59.990 --> 00:13:00.000 align:start position:0% problem 00:13:00.000 --> 00:13:01.250 align:start position:0% problem um<00:13:00.120> in<00:13:00.360> that<00:13:00.540> someone's<00:13:00.899> trying<00:13:01.019> to<00:13:01.139> set 00:13:01.250 --> 00:13:01.260 align:start position:0% um in that someone's trying to set 00:13:01.260 --> 00:13:02.750 align:start position:0% um in that someone's trying to set something<00:13:01.440> you<00:13:01.800> didn't<00:13:01.980> you<00:13:02.339> can<00:13:02.399> intercept 00:13:02.750 --> 00:13:02.760 align:start position:0% something you didn't you can intercept 00:13:02.760 --> 00:13:05.290 align:start position:0% something you didn't you can intercept it<00:13:02.880> with<00:13:03.060> this 00:13:05.290 --> 00:13:05.300 align:start position:0% 00:13:05.300 --> 00:13:08.329 align:start position:0% we<00:13:06.300> take<00:13:06.839> advantage<00:13:07.200> of<00:13:07.740> um<00:13:07.800> the<00:13:08.100> fact<00:13:08.220> that 00:13:08.329 --> 00:13:08.339 align:start position:0% we take advantage of um the fact that 00:13:08.339 --> 00:13:10.670 align:start position:0% we take advantage of um the fact that when<00:13:08.519> you<00:13:08.700> first<00:13:08.820> set<00:13:09.120> your<00:13:09.300> recovery<00:13:09.660> hash<00:13:09.959> it 00:13:10.670 --> 00:13:10.680 align:start position:0% when you first set your recovery hash it 00:13:10.680 --> 00:13:12.110 align:start position:0% when you first set your recovery hash it will<00:13:10.860> set<00:13:10.980> it<00:13:11.160> immediately<00:13:11.519> but<00:13:11.820> otherwise 00:13:12.110 --> 00:13:12.120 align:start position:0% will set it immediately but otherwise 00:13:12.120 --> 00:13:13.850 align:start position:0% will set it immediately but otherwise it's<00:13:12.300> a<00:13:12.480> secure<00:13:12.779> function<00:13:13.200> so<00:13:13.320> it<00:13:13.500> will<00:13:13.620> have<00:13:13.740> a 00:13:13.850 --> 00:13:13.860 align:start position:0% it's a secure function so it will have a 00:13:13.860 --> 00:13:16.009 align:start position:0% it's a secure function so it will have a delay<00:13:14.160> and<00:13:15.120> in<00:13:15.240> doing<00:13:15.360> that<00:13:15.540> you<00:13:15.720> can<00:13:15.839> do 00:13:16.009 --> 00:13:16.019 align:start position:0% delay and in doing that you can do 00:13:16.019 --> 00:13:18.530 align:start position:0% delay and in doing that you can do something<00:13:16.200> quite<00:13:16.620> fun<00:13:17.100> with<00:13:17.399> that<00:13:17.519> in<00:13:18.120> that<00:13:18.300> if 00:13:18.530 --> 00:13:18.540 align:start position:0% something quite fun with that in that if 00:13:18.540 --> 00:13:21.650 align:start position:0% something quite fun with that in that if you<00:13:18.600> want<00:13:18.839> to<00:13:19.160> onboard<00:13:20.160> your<00:13:20.459> users<00:13:20.880> you<00:13:21.540> can 00:13:21.650 --> 00:13:21.660 align:start position:0% you want to onboard your users you can 00:13:21.660 --> 00:13:24.530 align:start position:0% you want to onboard your users you can put<00:13:21.839> a<00:13:21.959> wallet<00:13:22.380> inside<00:13:22.560> the<00:13:22.800> browser<00:13:23.160> and<00:13:24.000> have 00:13:24.530 --> 00:13:24.540 align:start position:0% put a wallet inside the browser and have 00:13:24.540 --> 00:13:25.730 align:start position:0% put a wallet inside the browser and have them<00:13:24.660> use<00:13:24.839> that<00:13:25.019> you<00:13:25.200> can<00:13:25.320> send<00:13:25.440> them<00:13:25.560> some 00:13:25.730 --> 00:13:25.740 align:start position:0% them use that you can send them some 00:13:25.740 --> 00:13:27.710 align:start position:0% them use that you can send them some assets<00:13:26.100> like<00:13:26.579> give<00:13:26.760> them<00:13:26.880> basically<00:13:27.120> a<00:13:27.360> web<00:13:27.480> 2 00:13:27.710 --> 00:13:27.720 align:start position:0% assets like give them basically a web 2 00:13:27.720 --> 00:13:29.569 align:start position:0% assets like give them basically a web 2 usability<00:13:28.380> experience<00:13:28.800> but<00:13:29.160> you<00:13:29.399> they 00:13:29.569 --> 00:13:29.579 align:start position:0% usability experience but you they 00:13:29.579 --> 00:13:31.269 align:start position:0% usability experience but you they actually<00:13:29.760> have<00:13:29.940> web<00:13:30.120> free<00:13:30.360> assets<00:13:30.720> in<00:13:30.959> their 00:13:31.269 --> 00:13:31.279 align:start position:0% actually have web free assets in their 00:13:31.279 --> 00:13:33.710 align:start position:0% actually have web free assets in their browser<00:13:32.279> wallet<00:13:32.639> but<00:13:33.180> then<00:13:33.300> at<00:13:33.420> some<00:13:33.600> point 00:13:33.710 --> 00:13:33.720 align:start position:0% browser wallet but then at some point 00:13:33.720 --> 00:13:36.829 align:start position:0% browser wallet but then at some point they<00:13:34.019> may<00:13:34.200> say<00:13:34.440> they<00:13:35.399> may<00:13:35.579> wish<00:13:36.420> to<00:13:36.600> secure 00:13:36.829 --> 00:13:36.839 align:start position:0% they may say they may wish to secure 00:13:36.839 --> 00:13:38.990 align:start position:0% they may say they may wish to secure those<00:13:37.079> assets<00:13:37.620> further<00:13:37.980> so<00:13:38.519> you<00:13:38.700> have<00:13:38.880> the 00:13:38.990 --> 00:13:39.000 align:start position:0% those assets further so you have the 00:13:39.000 --> 00:13:40.850 align:start position:0% those assets further so you have the smart<00:13:39.180> contract<00:13:39.540> deployed<00:13:40.019> you<00:13:40.380> have<00:13:40.500> the<00:13:40.680> key 00:13:40.850 --> 00:13:40.860 align:start position:0% smart contract deployed you have the key 00:13:40.860 --> 00:13:42.170 align:start position:0% smart contract deployed you have the key inside<00:13:41.040> the<00:13:41.279> browser<00:13:41.579> but<00:13:41.700> that's<00:13:41.880> not<00:13:42.000> very 00:13:42.170 --> 00:13:42.180 align:start position:0% inside the browser but that's not very 00:13:42.180 --> 00:13:44.030 align:start position:0% inside the browser but that's not very secure<00:13:42.480> so<00:13:43.139> you<00:13:43.200> can<00:13:43.320> do<00:13:43.500> something<00:13:43.680> like 00:13:44.030 --> 00:13:44.040 align:start position:0% secure so you can do something like 00:13:44.040 --> 00:13:45.769 align:start position:0% secure so you can do something like suggested<00:13:44.760> the<00:13:44.940> user<00:13:45.180> that<00:13:45.300> they<00:13:45.480> set<00:13:45.660> the 00:13:45.769 --> 00:13:45.779 align:start position:0% suggested the user that they set the 00:13:45.779 --> 00:13:47.509 align:start position:0% suggested the user that they set the recovery<00:13:46.139> hash<00:13:46.380> of<00:13:46.620> their<00:13:46.800> browser<00:13:47.220> wallet 00:13:47.509 --> 00:13:47.519 align:start position:0% recovery hash of their browser wallet 00:13:47.519 --> 00:13:50.030 align:start position:0% recovery hash of their browser wallet and<00:13:47.940> you<00:13:48.060> can<00:13:48.120> do<00:13:48.240> that<00:13:48.420> via<00:13:48.720> the<00:13:48.839> DAP<00:13:49.079> and<00:13:49.860> then 00:13:50.030 --> 00:13:50.040 align:start position:0% and you can do that via the DAP and then 00:13:50.040 --> 00:13:52.190 align:start position:0% and you can do that via the DAP and then from<00:13:50.940> the<00:13:51.120> secure<00:13:51.420> wallet<00:13:51.779> that<00:13:51.899> you've 00:13:52.190 --> 00:13:52.200 align:start position:0% from the secure wallet that you've 00:13:52.200 --> 00:13:53.870 align:start position:0% from the secure wallet that you've prompted<00:13:52.620> them<00:13:52.740> to<00:13:52.920> install<00:13:53.040> like<00:13:53.459> if<00:13:53.639> it's 00:13:53.870 --> 00:13:53.880 align:start position:0% prompted them to install like if it's 00:13:53.880 --> 00:13:55.910 align:start position:0% prompted them to install like if it's our<00:13:54.120> prototype<00:13:54.600> extension<00:13:55.019> quill<00:13:55.260> you<00:13:55.800> can 00:13:55.910 --> 00:13:55.920 align:start position:0% our prototype extension quill you can 00:13:55.920 --> 00:13:59.509 align:start position:0% our prototype extension quill you can then<00:13:56.579> recover<00:13:57.120> the<00:13:58.019> wallet<00:13:58.380> that<00:13:59.040> was<00:13:59.279> in<00:13:59.459> the 00:13:59.509 --> 00:13:59.519 align:start position:0% then recover the wallet that was in the 00:13:59.519 --> 00:14:00.710 align:start position:0% then recover the wallet that was in the browser<00:13:59.880> and<00:14:00.180> what<00:14:00.360> you've<00:14:00.480> done<00:14:00.600> is 00:14:00.710 --> 00:14:00.720 align:start position:0% browser and what you've done is 00:14:00.720 --> 00:14:03.290 align:start position:0% browser and what you've done is effectively<00:14:01.200> set<00:14:01.440> a<00:14:01.620> private<00:14:01.980> key<00:14:02.100> to<00:14:02.820> the 00:14:03.290 --> 00:14:03.300 align:start position:0% effectively set a private key to the 00:14:03.300 --> 00:14:04.790 align:start position:0% effectively set a private key to the extension<00:14:03.720> key<00:14:03.899> rather<00:14:04.200> than<00:14:04.380> the<00:14:04.500> one<00:14:04.620> in<00:14:04.680> the 00:14:04.790 --> 00:14:04.800 align:start position:0% extension key rather than the one in the 00:14:04.800 --> 00:14:06.530 align:start position:0% extension key rather than the one in the browser<00:14:04.980> so<00:14:05.100> that<00:14:05.279> is<00:14:05.700> lost<00:14:05.940> and<00:14:06.360> you've 00:14:06.530 --> 00:14:06.540 align:start position:0% browser so that is lost and you've 00:14:06.540 --> 00:14:08.629 align:start position:0% browser so that is lost and you've secured<00:14:06.899> it 00:14:08.629 --> 00:14:08.639 align:start position:0% secured it 00:14:08.639 --> 00:14:10.310 align:start position:0% secured it we<00:14:09.060> find<00:14:09.180> that's<00:14:09.360> just<00:14:09.540> a<00:14:09.720> smooth<00:14:09.899> way<00:14:10.139> to 00:14:10.310 --> 00:14:10.320 align:start position:0% we find that's just a smooth way to 00:14:10.320 --> 00:14:12.710 align:start position:0% we find that's just a smooth way to onboard<00:14:10.560> people<00:14:10.800> so<00:14:11.579> where<00:14:11.820> to<00:14:12.000> next<00:14:12.240> so<00:14:12.600> let's 00:14:12.710 --> 00:14:12.720 align:start position:0% onboard people so where to next so let's 00:14:12.720 --> 00:14:15.530 align:start position:0% onboard people so where to next so let's sort<00:14:12.899> of<00:14:13.019> start<00:14:13.200> with<00:14:13.500> where<00:14:14.100> we<00:14:14.220> began<00:14:14.519> so<00:14:15.300> we 00:14:15.530 --> 00:14:15.540 align:start position:0% sort of start with where we began so we 00:14:15.540 --> 00:14:16.389 align:start position:0% sort of start with where we began so we were<00:14:15.660> looking 00:14:16.389 --> 00:14:16.399 align:start position:0% were looking 00:14:16.399 --> 00:14:18.350 align:start position:0% were looking primarily<00:14:17.399> at<00:14:17.519> aggregating<00:14:17.880> signatures 00:14:18.350 --> 00:14:18.360 align:start position:0% primarily at aggregating signatures 00:14:18.360 --> 00:14:20.110 align:start position:0% primarily at aggregating signatures obviously<00:14:18.779> to<00:14:18.959> reduce<00:14:19.139> the<00:14:19.380> call<00:14:19.560> data 00:14:20.110 --> 00:14:20.120 align:start position:0% obviously to reduce the call data 00:14:20.120 --> 00:14:23.090 align:start position:0% obviously to reduce the call data towards<00:14:21.120> layer<00:14:21.420> one<00:14:21.600> on<00:14:21.779> Roll-Ups<00:14:22.260> and<00:14:22.860> we 00:14:23.090 --> 00:14:23.100 align:start position:0% towards layer one on Roll-Ups and we 00:14:23.100 --> 00:14:25.430 align:start position:0% towards layer one on Roll-Ups and we wanted<00:14:23.220> to<00:14:23.519> I<00:14:24.060> don't<00:14:24.240> have<00:14:24.420> slides<00:14:24.720> here<00:14:24.899> so 00:14:25.430 --> 00:14:25.440 align:start position:0% wanted to I don't have slides here so 00:14:25.440 --> 00:14:26.750 align:start position:0% wanted to I don't have slides here so yeah<00:14:25.560> I<00:14:25.680> wanted<00:14:25.800> to<00:14:26.040> leverage<00:14:26.279> account 00:14:26.750 --> 00:14:26.760 align:start position:0% yeah I wanted to leverage account 00:14:26.760 --> 00:14:28.069 align:start position:0% yeah I wanted to leverage account abstraction<00:14:27.240> which<00:14:27.480> was<00:14:27.600> at<00:14:27.779> the<00:14:27.899> protocol 00:14:28.069 --> 00:14:28.079 align:start position:0% abstraction which was at the protocol 00:14:28.079 --> 00:14:31.490 align:start position:0% abstraction which was at the protocol layer<00:14:28.500> first<00:14:28.620> so<00:14:29.040> that<00:14:29.160> was<00:14:29.480> eip2938<00:14:30.500> with 00:14:31.490 --> 00:14:31.500 align:start position:0% layer first so that was eip2938 with 00:14:31.500 --> 00:14:32.870 align:start position:0% layer first so that was eip2938 with that<00:14:31.680> we<00:14:31.800> realized<00:14:32.100> there<00:14:32.220> could<00:14:32.399> be<00:14:32.519> some 00:14:32.870 --> 00:14:32.880 align:start position:0% that we realized there could be some 00:14:32.880 --> 00:14:34.490 align:start position:0% that we realized there could be some delay<00:14:33.360> for<00:14:33.540> that<00:14:33.660> and<00:14:33.779> also<00:14:34.019> that<00:14:34.139> seems<00:14:34.440> to 00:14:34.490 --> 00:14:34.500 align:start position:0% delay for that and also that seems to 00:14:34.500 --> 00:14:37.190 align:start position:0% delay for that and also that seems to have<00:14:34.680> paused<00:14:35.399> since<00:14:35.519> then<00:14:35.760> so<00:14:36.540> we<00:14:36.660> decided<00:14:37.019> at 00:14:37.190 --> 00:14:37.200 align:start position:0% have paused since then so we decided at 00:14:37.200 --> 00:14:39.350 align:start position:0% have paused since then so we decided at that<00:14:37.320> time<00:14:37.500> to<00:14:37.680> focus<00:14:37.920> on<00:14:38.339> a<00:14:38.700> BLS<00:14:39.180> only 00:14:39.350 --> 00:14:39.360 align:start position:0% that time to focus on a BLS only 00:14:39.360 --> 00:14:40.610 align:start position:0% that time to focus on a BLS only signature<00:14:39.839> scheme<00:14:40.139> because<00:14:40.199> that's<00:14:40.320> what<00:14:40.500> we 00:14:40.610 --> 00:14:40.620 align:start position:0% signature scheme because that's what we 00:14:40.620 --> 00:14:42.050 align:start position:0% signature scheme because that's what we needed<00:14:40.920> and<00:14:41.279> that<00:14:41.399> would<00:14:41.519> be<00:14:41.639> a<00:14:41.820> contract 00:14:42.050 --> 00:14:42.060 align:start position:0% needed and that would be a contract 00:14:42.060 --> 00:14:43.250 align:start position:0% needed and that would be a contract wallet 00:14:43.250 --> 00:14:43.260 align:start position:0% wallet 00:14:43.260 --> 00:14:45.170 align:start position:0% wallet uh<00:14:43.740> we<00:14:43.920> did<00:14:44.040> some<00:14:44.160> preliminary<00:14:44.579> optimizations 00:14:45.170 --> 00:14:45.180 align:start position:0% uh we did some preliminary optimizations 00:14:45.180 --> 00:14:47.750 align:start position:0% uh we did some preliminary optimizations like<00:14:45.600> parameter<00:14:46.139> deduplication<00:14:46.800> so<00:14:47.339> if<00:14:47.699> you 00:14:47.750 --> 00:14:47.760 align:start position:0% like parameter deduplication so if you 00:14:47.760 --> 00:14:48.949 align:start position:0% like parameter deduplication so if you have<00:14:47.880> a<00:14:48.060> bundle<00:14:48.300> with<00:14:48.480> a<00:14:48.600> lot<00:14:48.720> of<00:14:48.779> common 00:14:48.949 --> 00:14:48.959 align:start position:0% have a bundle with a lot of common 00:14:48.959 --> 00:14:50.810 align:start position:0% have a bundle with a lot of common parameters<00:14:49.500> you<00:14:50.100> can<00:14:50.220> effectively<00:14:50.639> like 00:14:50.810 --> 00:14:50.820 align:start position:0% parameters you can effectively like 00:14:50.820 --> 00:14:52.670 align:start position:0% parameters you can effectively like factorization<00:14:51.420> you<00:14:51.660> take<00:14:51.839> it<00:14:52.019> once<00:14:52.320> out<00:14:52.500> the 00:14:52.670 --> 00:14:52.680 align:start position:0% factorization you take it once out the 00:14:52.680 --> 00:14:54.710 align:start position:0% factorization you take it once out the front<00:14:52.800> and<00:14:53.220> fill<00:14:53.519> in<00:14:53.699> the<00:14:53.820> gaps<00:14:54.120> so<00:14:54.480> something 00:14:54.710 --> 00:14:54.720 align:start position:0% front and fill in the gaps so something 00:14:54.720 --> 00:14:56.930 align:start position:0% front and fill in the gaps so something like<00:14:54.959> an<00:14:55.079> airdrop<00:14:55.500> is<00:14:55.680> is<00:14:55.800> really<00:14:56.399> valuable<00:14:56.760> so 00:14:56.930 --> 00:14:56.940 align:start position:0% like an airdrop is is really valuable so 00:14:56.940 --> 00:14:58.069 align:start position:0% like an airdrop is is really valuable so if<00:14:57.060> someone<00:14:57.240> wants<00:14:57.420> to<00:14:57.480> do<00:14:57.540> an<00:14:57.660> airdrop<00:14:57.959> they 00:14:58.069 --> 00:14:58.079 align:start position:0% if someone wants to do an airdrop they 00:14:58.079 --> 00:14:59.930 align:start position:0% if someone wants to do an airdrop they can<00:14:58.260> send<00:14:58.380> a<00:14:58.500> bundle<00:14:58.740> of<00:14:58.860> transactions<00:14:59.459> they 00:14:59.930 --> 00:14:59.940 align:start position:0% can send a bundle of transactions they 00:14:59.940 --> 00:15:03.290 align:start position:0% can send a bundle of transactions they pass<00:15:00.180> in<00:15:00.500> one<00:15:01.500> contract<00:15:02.279> they're<00:15:02.519> interacting 00:15:03.290 --> 00:15:03.300 align:start position:0% pass in one contract they're interacting 00:15:03.300 --> 00:15:05.090 align:start position:0% pass in one contract they're interacting with<00:15:03.420> it's<00:15:03.899> one<00:15:04.139> sender<00:15:04.620> it's<00:15:04.740> one<00:15:04.920> address 00:15:05.090 --> 00:15:05.100 align:start position:0% with it's one sender it's one address 00:15:05.100 --> 00:15:07.310 align:start position:0% with it's one sender it's one address it's<00:15:05.339> calling<00:15:05.699> it<00:15:05.820> and<00:15:06.360> then 00:15:07.310 --> 00:15:07.320 align:start position:0% it's calling it and then 00:15:07.320 --> 00:15:08.689 align:start position:0% it's calling it and then um<00:15:07.380> yeah<00:15:07.680> some<00:15:07.920> of<00:15:08.040> the<00:15:08.100> parameters<00:15:08.459> are<00:15:08.579> the 00:15:08.689 --> 00:15:08.699 align:start position:0% um yeah some of the parameters are the 00:15:08.699 --> 00:15:10.370 align:start position:0% um yeah some of the parameters are the same<00:15:08.820> except<00:15:09.120> for<00:15:09.240> the<00:15:09.360> recipient<00:15:09.720> and<00:15:10.260> in 00:15:10.370 --> 00:15:10.380 align:start position:0% same except for the recipient and in 00:15:10.380 --> 00:15:11.569 align:start position:0% same except for the recipient and in that<00:15:10.500> case<00:15:10.620> you<00:15:10.800> can<00:15:10.920> effectively<00:15:11.399> yeah 00:15:11.569 --> 00:15:11.579 align:start position:0% that case you can effectively yeah 00:15:11.579 --> 00:15:14.150 align:start position:0% that case you can effectively yeah deduplicate<00:15:12.360> parameters<00:15:12.779> uh<00:15:13.260> there 00:15:14.150 --> 00:15:14.160 align:start position:0% deduplicate parameters uh there 00:15:14.160 --> 00:15:16.069 align:start position:0% deduplicate parameters uh there you've<00:15:14.699> got<00:15:14.760> to<00:15:15.000> ignore<00:15:15.420> that<00:15:15.540> screen<00:15:15.720> there 00:15:16.069 --> 00:15:16.079 align:start position:0% you've got to ignore that screen there 00:15:16.079 --> 00:15:18.350 align:start position:0% you've got to ignore that screen there we<00:15:16.199> go<00:15:16.740> uh<00:15:17.579> yeah<00:15:17.760> some<00:15:17.940> of<00:15:18.060> the<00:15:18.120> wallet 00:15:18.350 --> 00:15:18.360 align:start position:0% we go uh yeah some of the wallet 00:15:18.360 --> 00:15:20.150 align:start position:0% we go uh yeah some of the wallet features<00:15:18.600> we<00:15:18.779> then<00:15:18.899> focused<00:15:19.199> on<00:15:19.320> were<00:15:19.620> as<00:15:19.920> Jake 00:15:20.150 --> 00:15:20.160 align:start position:0% features we then focused on were as Jake 00:15:20.160 --> 00:15:21.590 align:start position:0% features we then focused on were as Jake described<00:15:20.639> sponsored<00:15:21.120> transactions 00:15:21.590 --> 00:15:21.600 align:start position:0% described sponsored transactions 00:15:21.600 --> 00:15:23.030 align:start position:0% described sponsored transactions multi-action<00:15:22.139> recoverability<00:15:22.740> and 00:15:23.030 --> 00:15:23.040 align:start position:0% multi-action recoverability and 00:15:23.040 --> 00:15:25.670 align:start position:0% multi-action recoverability and upgradability 00:15:25.670 --> 00:15:25.680 align:start position:0% 00:15:25.680 --> 00:15:28.250 align:start position:0% and<00:15:26.160> then<00:15:26.279> we<00:15:26.639> heard<00:15:26.820> about<00:15:27.079> eip4337<00:15:28.079> and 00:15:28.250 --> 00:15:28.260 align:start position:0% and then we heard about eip4337 and 00:15:28.260 --> 00:15:29.329 align:start position:0% and then we heard about eip4337 and started<00:15:28.560> getting<00:15:28.740> some<00:15:28.920> interest<00:15:29.160> in 00:15:29.329 --> 00:15:29.339 align:start position:0% started getting some interest in 00:15:29.339 --> 00:15:30.590 align:start position:0% started getting some interest in popularity 00:15:30.590 --> 00:15:30.600 align:start position:0% popularity 00:15:30.600 --> 00:15:31.910 align:start position:0% popularity um<00:15:30.660> and<00:15:30.899> at<00:15:31.019> that<00:15:31.139> time<00:15:31.260> our<00:15:31.440> contracts<00:15:31.800> were 00:15:31.910 --> 00:15:31.920 align:start position:0% um and at that time our contracts were 00:15:31.920 --> 00:15:32.870 align:start position:0% um and at that time our contracts were going<00:15:32.040> for<00:15:32.160> audit<00:15:32.399> so<00:15:32.519> we're<00:15:32.639> trying<00:15:32.820> to 00:15:32.870 --> 00:15:32.880 align:start position:0% going for audit so we're trying to 00:15:32.880 --> 00:15:34.250 align:start position:0% going for audit so we're trying to figure<00:15:33.000> out<00:15:33.120> do<00:15:33.360> we<00:15:33.600> just<00:15:33.660> finish<00:15:33.959> what<00:15:34.139> we're 00:15:34.250 --> 00:15:34.260 align:start position:0% figure out do we just finish what we're 00:15:34.260 --> 00:15:36.230 align:start position:0% figure out do we just finish what we're doing<00:15:34.380> or<00:15:34.620> look<00:15:34.980> at<00:15:35.100> that<00:15:35.220> so<00:15:35.519> then<00:15:35.639> we<00:15:35.760> decided 00:15:36.230 --> 00:15:36.240 align:start position:0% doing or look at that so then we decided 00:15:36.240 --> 00:15:37.850 align:start position:0% doing or look at that so then we decided to<00:15:36.480> yeah<00:15:36.779> look<00:15:37.019> towards<00:15:37.320> being<00:15:37.500> compatible 00:15:37.850 --> 00:15:37.860 align:start position:0% to yeah look towards being compatible 00:15:37.860 --> 00:15:39.949 align:start position:0% to yeah look towards being compatible with<00:15:38.040> four<00:15:38.160> through<00:15:38.399> the<00:15:38.579> seven<00:15:38.760> so<00:15:39.600> that's 00:15:39.949 --> 00:15:39.959 align:start position:0% with four through the seven so that's 00:15:39.959 --> 00:15:42.710 align:start position:0% with four through the seven so that's where<00:15:40.199> we<00:15:40.320> are<00:15:40.440> now<00:15:40.680> where<00:15:41.160> to<00:15:41.339> next<00:15:41.579> we 00:15:42.710 --> 00:15:42.720 align:start position:0% where we are now where to next we 00:15:42.720 --> 00:15:44.449 align:start position:0% where we are now where to next we still<00:15:43.199> focusing<00:15:43.500> on<00:15:43.680> aggregating<00:15:44.040> signatures 00:15:44.449 --> 00:15:44.459 align:start position:0% still focusing on aggregating signatures 00:15:44.459 --> 00:15:46.009 align:start position:0% still focusing on aggregating signatures for<00:15:44.639> the<00:15:44.760> lowest<00:15:45.000> cost<00:15:45.180> transactions<00:15:45.839> on 00:15:46.009 --> 00:15:46.019 align:start position:0% for the lowest cost transactions on 00:15:46.019 --> 00:15:49.610 align:start position:0% for the lowest cost transactions on Layer<00:15:46.260> Two<00:15:46.399> we<00:15:47.399> will<00:15:48.060> be<00:15:48.240> focusing<00:15:48.660> oh<00:15:49.019> my 00:15:49.610 --> 00:15:49.620 align:start position:0% Layer Two we will be focusing oh my 00:15:49.620 --> 00:15:50.930 align:start position:0% Layer Two we will be focusing oh my slides<00:15:49.980> moving<00:15:50.220> around 00:15:50.930 --> 00:15:50.940 align:start position:0% slides moving around 00:15:50.940 --> 00:15:52.370 align:start position:0% slides moving around yeah<00:15:51.360> still<00:15:51.600> focusing<00:15:51.899> on<00:15:52.019> aggregating 00:15:52.370 --> 00:15:52.380 align:start position:0% yeah still focusing on aggregating 00:15:52.380 --> 00:15:53.930 align:start position:0% yeah still focusing on aggregating signatures<00:15:52.800> and<00:15:53.100> then<00:15:53.160> we<00:15:53.519> are<00:15:53.639> working<00:15:53.760> on 00:15:53.930 --> 00:15:53.940 align:start position:0% signatures and then we are working on 00:15:53.940 --> 00:15:55.490 align:start position:0% signatures and then we are working on being<00:15:54.060> 437<00:15:54.720> compatible<00:15:55.079> one<00:15:55.380> of<00:15:55.440> our 00:15:55.490 --> 00:15:55.500 align:start position:0% being 437 compatible one of our 00:15:55.500 --> 00:15:57.050 align:start position:0% being 437 compatible one of our colleagues<00:15:55.800> is<00:15:55.920> almost<00:15:56.100> there<00:15:56.279> with<00:15:56.459> that<00:15:56.639> and 00:15:57.050 --> 00:15:57.060 align:start position:0% colleagues is almost there with that and 00:15:57.060 --> 00:15:58.310 align:start position:0% colleagues is almost there with that and I<00:15:57.240> noticed<00:15:57.480> that<00:15:57.660> draw<00:15:57.839> in<00:15:58.019> the<00:15:58.139> background 00:15:58.310 --> 00:15:58.320 align:start position:0% I noticed that draw in the background 00:15:58.320 --> 00:16:02.090 align:start position:0% I noticed that draw in the background say<00:15:58.920> hi<00:15:59.100> uh<00:16:00.000> so<00:16:00.120> he's<00:16:00.300> working<00:16:00.420> on<00:16:00.600> 4337 00:16:02.090 --> 00:16:02.100 align:start position:0% say hi uh so he's working on 4337 00:16:02.100 --> 00:16:04.250 align:start position:0% say hi uh so he's working on 4337 um what<00:16:02.760> I<00:16:02.880> should<00:16:03.000> explain<00:16:03.180> yeah<00:16:03.360> 4337<00:16:04.079> is 00:16:04.250 --> 00:16:04.260 align:start position:0% um what I should explain yeah 4337 is 00:16:04.260 --> 00:16:05.810 align:start position:0% um what I should explain yeah 4337 is doing<00:16:04.380> account<00:16:04.560> obstruction<00:16:04.980> on<00:16:05.220> chain<00:16:05.459> so 00:16:05.810 --> 00:16:05.820 align:start position:0% doing account obstruction on chain so 00:16:05.820 --> 00:16:07.490 align:start position:0% doing account obstruction on chain so they've<00:16:06.420> um<00:16:06.420> got<00:16:06.720> a<00:16:06.959> basically<00:16:07.260> a<00:16:07.380> smart 00:16:07.490 --> 00:16:07.500 align:start position:0% they've um got a basically a smart 00:16:07.500 --> 00:16:08.689 align:start position:0% they've um got a basically a smart contract<00:16:07.800> template<00:16:08.160> for<00:16:08.279> that<00:16:08.399> and<00:16:08.519> a 00:16:08.689 --> 00:16:08.699 align:start position:0% contract template for that and a 00:16:08.699 --> 00:16:10.250 align:start position:0% contract template for that and a structure<00:16:08.940> for<00:16:09.120> how<00:16:09.300> that<00:16:09.420> will<00:16:09.540> work<00:16:10.199> um 00:16:10.250 --> 00:16:10.260 align:start position:0% structure for how that will work um 00:16:10.260 --> 00:16:12.350 align:start position:0% structure for how that will work um regarding<00:16:10.620> paying<00:16:10.920> gas<00:16:11.040> as<00:16:11.279> well<00:16:11.399> the<00:16:12.120> way<00:16:12.240> we 00:16:12.350 --> 00:16:12.360 align:start position:0% regarding paying gas as well the way we 00:16:12.360 --> 00:16:13.790 align:start position:0% regarding paying gas as well the way we originally<00:16:12.660> did<00:16:12.839> it<00:16:12.899> as<00:16:13.079> Jake<00:16:13.199> described<00:16:13.620> is 00:16:13.790 --> 00:16:13.800 align:start position:0% originally did it as Jake described is 00:16:13.800 --> 00:16:15.889 align:start position:0% originally did it as Jake described is putting<00:16:14.339> in<00:16:14.399> a<00:16:14.519> reward<00:16:14.760> to<00:16:15.000> the<00:16:15.180> TX<00:16:15.420> origin<00:16:15.779> so 00:16:15.889 --> 00:16:15.899 align:start position:0% putting in a reward to the TX origin so 00:16:15.899 --> 00:16:17.810 align:start position:0% putting in a reward to the TX origin so that<00:16:16.019> Mev<00:16:16.380> Bots<00:16:16.620> can<00:16:16.920> process<00:16:17.579> the 00:16:17.810 --> 00:16:17.820 align:start position:0% that Mev Bots can process the 00:16:17.820 --> 00:16:19.610 align:start position:0% that Mev Bots can process the transactions<00:16:18.360> but<00:16:18.899> there's<00:16:19.019> also<00:16:19.260> the<00:16:19.440> way 00:16:19.610 --> 00:16:19.620 align:start position:0% transactions but there's also the way 00:16:19.620 --> 00:16:21.710 align:start position:0% transactions but there's also the way using<00:16:19.980> the<00:16:20.040> Altman<00:16:20.339> pool<00:16:20.579> that<00:16:20.760> 4357<00:16:21.300> proposes 00:16:21.710 --> 00:16:21.720 align:start position:0% using the Altman pool that 4357 proposes 00:16:21.720 --> 00:16:22.970 align:start position:0% using the Altman pool that 4357 proposes it<00:16:21.839> so<00:16:21.959> we<00:16:22.079> can<00:16:22.199> do<00:16:22.500> either<00:16:22.680> of<00:16:22.860> those 00:16:22.970 --> 00:16:22.980 align:start position:0% it so we can do either of those 00:16:22.980 --> 00:16:25.090 align:start position:0% it so we can do either of those depending<00:16:23.459> on<00:16:23.699> what<00:16:23.880> the<00:16:24.060> DAP<00:16:24.240> wants 00:16:25.090 --> 00:16:25.100 align:start position:0% depending on what the DAP wants 00:16:25.100 --> 00:16:28.550 align:start position:0% depending on what the DAP wants further<00:16:26.100> optimizations<00:16:26.699> the<00:16:27.480> 4337<00:16:28.260> user 00:16:28.550 --> 00:16:28.560 align:start position:0% further optimizations the 4337 user 00:16:28.560 --> 00:16:30.230 align:start position:0% further optimizations the 4337 user operation<00:16:28.860> contains<00:16:29.399> you<00:16:29.820> know<00:16:29.940> more<00:16:30.060> gas 00:16:30.230 --> 00:16:30.240 align:start position:0% operation contains you know more gas 00:16:30.240 --> 00:16:31.970 align:start position:0% operation contains you know more gas parameters<00:16:30.660> to<00:16:30.839> take<00:16:31.019> care<00:16:31.139> of<00:16:31.260> the<00:16:31.680> way<00:16:31.800> they 00:16:31.970 --> 00:16:31.980 align:start position:0% parameters to take care of the way they 00:16:31.980 --> 00:16:34.009 align:start position:0% parameters to take care of the way they do<00:16:32.100> that<00:16:32.279> but<00:16:32.820> for<00:16:33.120> when<00:16:33.420> we<00:16:33.540> want<00:16:33.720> to<00:16:33.839> do<00:16:33.899> it 00:16:34.009 --> 00:16:34.019 align:start position:0% do that but for when we want to do it 00:16:34.019 --> 00:16:35.810 align:start position:0% do that but for when we want to do it the<00:16:34.199> direct<00:16:34.320> payment<00:16:34.500> way<00:16:34.800> we<00:16:35.100> can<00:16:35.279> again 00:16:35.810 --> 00:16:35.820 align:start position:0% the direct payment way we can again 00:16:35.820 --> 00:16:37.310 align:start position:0% the direct payment way we can again optimize<00:16:36.300> those<00:16:36.480> parameters<00:16:36.839> out<00:16:37.019> by<00:16:37.139> not 00:16:37.310 --> 00:16:37.320 align:start position:0% optimize those parameters out by not 00:16:37.320 --> 00:16:39.050 align:start position:0% optimize those parameters out by not passing<00:16:37.620> them<00:16:37.800> in<00:16:37.980> having<00:16:38.339> a<00:16:38.579> preceding 00:16:39.050 --> 00:16:39.060 align:start position:0% passing them in having a preceding 00:16:39.060 --> 00:16:40.790 align:start position:0% passing them in having a preceding function<00:16:39.360> that<00:16:39.660> then<00:16:39.899> populates<00:16:40.500> them<00:16:40.680> with 00:16:40.790 --> 00:16:40.800 align:start position:0% function that then populates them with 00:16:40.800 --> 00:16:43.850 align:start position:0% function that then populates them with zeros<00:16:41.160> and<00:16:41.759> then<00:16:42.060> from<00:16:42.360> there<00:16:42.600> we<00:16:43.560> can<00:16:43.680> do 00:16:43.850 --> 00:16:43.860 align:start position:0% zeros and then from there we can do 00:16:43.860 --> 00:16:46.730 align:start position:0% zeros and then from there we can do public<00:16:44.279> key<00:16:44.519> mapping<00:16:45.000> so<00:16:45.360> we<00:16:45.779> have 00:16:46.730 --> 00:16:46.740 align:start position:0% public key mapping so we have 00:16:46.740 --> 00:16:49.189 align:start position:0% public key mapping so we have um<00:16:46.800> yeah<00:16:46.980> smaller<00:16:47.579> data<00:16:48.540> sent<00:16:48.660> in<00:16:48.839> for<00:16:49.079> the 00:16:49.189 --> 00:16:49.199 align:start position:0% um yeah smaller data sent in for the 00:16:49.199 --> 00:16:50.870 align:start position:0% um yeah smaller data sent in for the larger<00:16:49.380> addresses<00:16:49.860> sorry<00:16:50.399> larger<00:16:50.699> public 00:16:50.870 --> 00:16:50.880 align:start position:0% larger addresses sorry larger public 00:16:50.880 --> 00:16:52.730 align:start position:0% larger addresses sorry larger public keys<00:16:51.540> and<00:16:51.779> also<00:16:51.959> doing<00:16:52.079> things<00:16:52.259> like<00:16:52.440> floating 00:16:52.730 --> 00:16:52.740 align:start position:0% keys and also doing things like floating 00:16:52.740 --> 00:16:54.769 align:start position:0% keys and also doing things like floating points<00:16:53.100> so<00:16:53.160> if<00:16:53.699> a<00:16:53.820> bundle<00:16:54.180> has<00:16:54.360> a<00:16:54.540> lot<00:16:54.660> of 00:16:54.769 --> 00:16:54.779 align:start position:0% points so if a bundle has a lot of 00:16:54.779 --> 00:16:56.389 align:start position:0% points so if a bundle has a lot of variables<00:16:55.500> that<00:16:55.620> are<00:16:55.800> actually<00:16:55.860> within<00:16:56.279> a 00:16:56.389 --> 00:16:56.399 align:start position:0% variables that are actually within a 00:16:56.399 --> 00:16:58.370 align:start position:0% variables that are actually within a specific<00:16:56.639> range<00:16:56.940> we<00:16:57.360> don't<00:16:57.540> need<00:16:57.720> to<00:16:57.959> pass<00:16:58.199> in 00:16:58.370 --> 00:16:58.380 align:start position:0% specific range we don't need to pass in 00:16:58.380 --> 00:17:01.970 align:start position:0% specific range we don't need to pass in a<00:16:58.579> un256-bit<00:17:00.019> number<00:17:01.019> for<00:17:01.259> each<00:17:01.380> of<00:17:01.500> them<00:17:01.620> we 00:17:01.970 --> 00:17:01.980 align:start position:0% a un256-bit number for each of them we 00:17:01.980 --> 00:17:03.949 align:start position:0% a un256-bit number for each of them we can<00:17:02.100> actually<00:17:02.220> have<00:17:02.519> some<00:17:02.820> smaller<00:17:03.600> range<00:17:03.779> for 00:17:03.949 --> 00:17:03.959 align:start position:0% can actually have some smaller range for 00:17:03.959 --> 00:17:05.809 align:start position:0% can actually have some smaller range for those<00:17:04.140> so<00:17:04.679> saving<00:17:05.040> bytes<00:17:05.280> wherever<00:17:05.520> we<00:17:05.699> can 00:17:05.809 --> 00:17:05.819 align:start position:0% those so saving bytes wherever we can 00:17:05.819 --> 00:17:06.890 align:start position:0% those so saving bytes wherever we can there's<00:17:06.000> a<00:17:06.120> lot<00:17:06.179> of<00:17:06.240> things<00:17:06.360> we<00:17:06.540> want<00:17:06.660> to<00:17:06.780> do 00:17:06.890 --> 00:17:06.900 align:start position:0% there's a lot of things we want to do 00:17:06.900 --> 00:17:09.350 align:start position:0% there's a lot of things we want to do there<00:17:07.400> some<00:17:08.400> of<00:17:08.579> it<00:17:08.699> just<00:17:08.880> almost<00:17:09.059> like<00:17:09.240> it 00:17:09.350 --> 00:17:09.360 align:start position:0% there some of it just almost like it 00:17:09.360 --> 00:17:10.730 align:start position:0% there some of it just almost like it would<00:17:09.480> say<00:17:09.540> a<00:17:09.660> refactor<00:17:10.020> phase<00:17:10.199> we<00:17:10.380> want<00:17:10.559> to 00:17:10.730 --> 00:17:10.740 align:start position:0% would say a refactor phase we want to 00:17:10.740 --> 00:17:12.530 align:start position:0% would say a refactor phase we want to bring<00:17:11.400> some<00:17:11.579> of<00:17:11.699> the<00:17:11.760> stuff<00:17:11.939> we<00:17:12.059> have<00:17:12.179> in<00:17:12.360> our 00:17:12.530 --> 00:17:12.540 align:start position:0% bring some of the stuff we have in our 00:17:12.540 --> 00:17:14.270 align:start position:0% bring some of the stuff we have in our current<00:17:12.720> wallet<00:17:13.140> basically<00:17:13.559> into<00:17:13.679> modules<00:17:14.100> so 00:17:14.270 --> 00:17:14.280 align:start position:0% current wallet basically into modules so 00:17:14.280 --> 00:17:16.370 align:start position:0% current wallet basically into modules so we<00:17:14.459> may<00:17:14.699> consider<00:17:15.000> using<00:17:15.240> safe<00:17:15.419> for<00:17:15.660> that<00:17:15.839> and 00:17:16.370 --> 00:17:16.380 align:start position:0% we may consider using safe for that and 00:17:16.380 --> 00:17:20.449 align:start position:0% we may consider using safe for that and some<00:17:16.559> of<00:17:16.679> the<00:17:16.740> examples<00:17:17.280> in<00:17:17.880> 457<00:17:18.740> and<00:17:19.740> then<00:17:19.980> we 00:17:20.449 --> 00:17:20.459 align:start position:0% some of the examples in 457 and then we 00:17:20.459 --> 00:17:23.390 align:start position:0% some of the examples in 457 and then we will<00:17:20.720> inherently<00:17:21.720> benefit<00:17:21.900> from<00:17:22.260> 4844<00:17:23.040> which 00:17:23.390 --> 00:17:23.400 align:start position:0% will inherently benefit from 4844 which 00:17:23.400 --> 00:17:26.929 align:start position:0% will inherently benefit from 4844 which is<00:17:24.000> um<00:17:24.059> yeah<00:17:24.360> towards<00:17:24.720> dank<00:17:24.959> shutting 00:17:26.929 --> 00:17:26.939 align:start position:0% is um yeah towards dank shutting 00:17:26.939 --> 00:17:29.210 align:start position:0% is um yeah towards dank shutting so<00:17:27.720> when<00:17:28.199> we<00:17:28.319> take<00:17:28.500> a<00:17:28.620> step<00:17:28.740> back<00:17:28.919> what<00:17:29.100> we're 00:17:29.210 --> 00:17:29.220 align:start position:0% so when we take a step back what we're 00:17:29.220 --> 00:17:30.710 align:start position:0% so when we take a step back what we're doing<00:17:29.340> is<00:17:29.520> lowering<00:17:29.880> the<00:17:29.940> transaction<00:17:30.240> costs 00:17:30.710 --> 00:17:30.720 align:start position:0% doing is lowering the transaction costs 00:17:30.720 --> 00:17:32.690 align:start position:0% doing is lowering the transaction costs on<00:17:30.900> Layer<00:17:31.200> Two<00:17:31.320> and<00:17:31.799> when<00:17:32.040> you<00:17:32.160> do<00:17:32.280> that<00:17:32.400> it 00:17:32.690 --> 00:17:32.700 align:start position:0% on Layer Two and when you do that it 00:17:32.700 --> 00:17:33.950 align:start position:0% on Layer Two and when you do that it increases<00:17:33.120> the<00:17:33.299> number<00:17:33.419> of<00:17:33.600> viable 00:17:33.950 --> 00:17:33.960 align:start position:0% increases the number of viable 00:17:33.960 --> 00:17:35.630 align:start position:0% increases the number of viable applications<00:17:34.559> that<00:17:34.799> can<00:17:34.919> be<00:17:34.980> built<00:17:35.220> or<00:17:35.340> viable 00:17:35.630 --> 00:17:35.640 align:start position:0% applications that can be built or viable 00:17:35.640 --> 00:17:37.730 align:start position:0% applications that can be built or viable solutions<00:17:36.059> that<00:17:36.720> can<00:17:36.840> be<00:17:37.020> put<00:17:37.260> out<00:17:37.440> there<00:17:37.559> to 00:17:37.730 --> 00:17:37.740 align:start position:0% solutions that can be put out there to 00:17:37.740 --> 00:17:38.930 align:start position:0% solutions that can be put out there to solve<00:17:37.980> problems 00:17:38.930 --> 00:17:38.940 align:start position:0% solve problems 00:17:38.940 --> 00:17:40.490 align:start position:0% solve problems and<00:17:39.419> I'd<00:17:39.600> like<00:17:39.720> to<00:17:39.840> sort<00:17:40.020> of<00:17:40.080> visualize<00:17:40.380> it 00:17:40.490 --> 00:17:40.500 align:start position:0% and I'd like to sort of visualize it 00:17:40.500 --> 00:17:43.549 align:start position:0% and I'd like to sort of visualize it like<00:17:40.679> this<00:17:40.860> on<00:17:41.340> the<00:17:42.120> um<00:17:42.179> the<00:17:42.720> x-axis<00:17:43.140> we've<00:17:43.440> got 00:17:43.549 --> 00:17:43.559 align:start position:0% like this on the um the x-axis we've got 00:17:43.559 --> 00:17:45.289 align:start position:0% like this on the um the x-axis we've got transaction<00:17:43.919> costs<00:17:44.340> and<00:17:44.580> we<00:17:44.820> have<00:17:44.940> a<00:17:45.059> lot<00:17:45.179> of 00:17:45.289 --> 00:17:45.299 align:start position:0% transaction costs and we have a lot of 00:17:45.299 --> 00:17:47.450 align:start position:0% transaction costs and we have a lot of defy<00:17:45.840> things<00:17:46.200> going<00:17:46.440> on<00:17:46.559> and<00:17:46.860> that<00:17:47.100> works<00:17:47.340> on 00:17:47.450 --> 00:17:47.460 align:start position:0% defy things going on and that works on 00:17:47.460 --> 00:17:50.029 align:start position:0% defy things going on and that works on layer<00:17:47.700> one<00:17:47.820> even<00:17:48.240> if<00:17:48.480> it's<00:17:48.660> a<00:17:49.200> um<00:17:49.200> you<00:17:49.980> know 00:17:50.029 --> 00:17:50.039 align:start position:0% layer one even if it's a um you know 00:17:50.039 --> 00:17:52.250 align:start position:0% layer one even if it's a um you know during<00:17:50.160> a<00:17:50.400> busy<00:17:50.640> time<00:17:50.760> and<00:17:51.179> there's<00:17:51.660> uh<00:17:51.960> you 00:17:52.250 --> 00:17:52.260 align:start position:0% during a busy time and there's uh you 00:17:52.260 --> 00:17:54.590 align:start position:0% during a busy time and there's uh you know<00:17:52.320> high<00:17:52.799> gas<00:17:53.039> costs<00:17:53.460> a<00:17:53.880> high<00:17:54.059> value<00:17:54.179> Asset 00:17:54.590 --> 00:17:54.600 align:start position:0% know high gas costs a high value Asset 00:17:54.600 --> 00:17:56.090 align:start position:0% know high gas costs a high value Asset transfer<00:17:54.960> is<00:17:55.080> worth<00:17:55.260> it<00:17:55.440> you<00:17:55.620> will<00:17:55.740> pay<00:17:55.919> a 00:17:56.090 --> 00:17:56.100 align:start position:0% transfer is worth it you will pay a 00:17:56.100 --> 00:17:57.169 align:start position:0% transfer is worth it you will pay a hundred<00:17:56.280> dollars<00:17:56.460> a<00:17:56.580> transaction<00:17:56.820> to<00:17:57.059> move 00:17:57.169 --> 00:17:57.179 align:start position:0% hundred dollars a transaction to move 00:17:57.179 --> 00:17:59.090 align:start position:0% hundred dollars a transaction to move something<00:17:57.419> of<00:17:57.660> significant<00:17:58.020> value<00:17:58.260> similarly 00:17:59.090 --> 00:17:59.100 align:start position:0% something of significant value similarly 00:17:59.100 --> 00:18:00.409 align:start position:0% something of significant value similarly if<00:17:59.220> you're<00:17:59.340> there's<00:17:59.520> a<00:17:59.640> hyped<00:17:59.820> up<00:17:59.880> nft<00:18:00.179> drop 00:18:00.409 --> 00:18:00.419 align:start position:0% if you're there's a hyped up nft drop 00:18:00.419 --> 00:18:02.210 align:start position:0% if you're there's a hyped up nft drop people<00:18:00.660> will<00:18:00.900> spend<00:18:01.140> the<00:18:01.260> gas<00:18:01.380> to<00:18:01.620> do<00:18:01.740> it<00:18:01.860> but 00:18:02.210 --> 00:18:02.220 align:start position:0% people will spend the gas to do it but 00:18:02.220 --> 00:18:03.650 align:start position:0% people will spend the gas to do it but that's<00:18:02.340> not<00:18:02.520> everyone<00:18:02.640> that's<00:18:03.000> a<00:18:03.179> that's<00:18:03.480> kind 00:18:03.650 --> 00:18:03.660 align:start position:0% that's not everyone that's a that's kind 00:18:03.660 --> 00:18:06.049 align:start position:0% that's not everyone that's a that's kind of<00:18:03.780> I<00:18:03.900> would<00:18:04.020> say<00:18:04.140> very<00:18:04.380> small<00:18:04.700> set<00:18:05.700> of<00:18:05.820> a 00:18:06.049 --> 00:18:06.059 align:start position:0% of I would say very small set of a 00:18:06.059 --> 00:18:07.130 align:start position:0% of I would say very small set of a population 00:18:07.130 --> 00:18:07.140 align:start position:0% population 00:18:07.140 --> 00:18:08.210 align:start position:0% population um with<00:18:07.260> Roll-Ups<00:18:07.679> you<00:18:07.799> can<00:18:07.860> get<00:18:07.980> cheaper 00:18:08.210 --> 00:18:08.220 align:start position:0% um with Roll-Ups you can get cheaper 00:18:08.220 --> 00:18:10.310 align:start position:0% um with Roll-Ups you can get cheaper transactions<00:18:08.640> towards<00:18:09.000> tens<00:18:09.240> of<00:18:09.360> cents<00:18:09.720> or 00:18:10.310 --> 00:18:10.320 align:start position:0% transactions towards tens of cents or 00:18:10.320 --> 00:18:12.230 align:start position:0% transactions towards tens of cents or less<00:18:10.500> and<00:18:10.980> then<00:18:11.100> you<00:18:11.280> can<00:18:11.400> casual<00:18:11.760> gaming<00:18:12.059> at 00:18:12.230 --> 00:18:12.240 align:start position:0% less and then you can casual gaming at 00:18:12.240 --> 00:18:13.669 align:start position:0% less and then you can casual gaming at warrants<00:18:12.600> that<00:18:12.840> you<00:18:12.960> can<00:18:13.080> spend<00:18:13.320> tens<00:18:13.500> of 00:18:13.669 --> 00:18:13.679 align:start position:0% warrants that you can spend tens of 00:18:13.679 --> 00:18:15.110 align:start position:0% warrants that you can spend tens of cents<00:18:13.919> for<00:18:14.039> a<00:18:14.160> certain<00:18:14.280> type<00:18:14.520> of<00:18:14.640> interaction 00:18:15.110 --> 00:18:15.120 align:start position:0% cents for a certain type of interaction 00:18:15.120 --> 00:18:17.270 align:start position:0% cents for a certain type of interaction and<00:18:15.600> that<00:18:16.020> works<00:18:16.320> there<00:18:16.440> but<00:18:16.740> what<00:18:16.860> we<00:18:16.980> want<00:18:17.160> to 00:18:17.270 --> 00:18:17.280 align:start position:0% and that works there but what we want to 00:18:17.280 --> 00:18:19.850 align:start position:0% and that works there but what we want to do<00:18:17.400> is<00:18:17.880> go<00:18:18.299> towards<00:18:18.660> this<00:18:18.780> we<00:18:19.080> with<00:18:19.320> evm 00:18:19.850 --> 00:18:19.860 align:start position:0% do is go towards this we with evm 00:18:19.860 --> 00:18:22.669 align:start position:0% do is go towards this we with evm Roll-Ups<00:18:20.760> adding<00:18:21.720> the<00:18:21.780> BLS<00:18:22.140> signature<00:18:22.440> scheme 00:18:22.669 --> 00:18:22.679 align:start position:0% Roll-Ups adding the BLS signature scheme 00:18:22.679 --> 00:18:24.830 align:start position:0% Roll-Ups adding the BLS signature scheme gives<00:18:22.799> you<00:18:22.919> some<00:18:23.039> savings<00:18:23.460> and<00:18:24.179> obviously<00:18:24.720> all 00:18:24.830 --> 00:18:24.840 align:start position:0% gives you some savings and obviously all 00:18:24.840 --> 00:18:26.150 align:start position:0% gives you some savings and obviously all the<00:18:24.960> other<00:18:25.080> things<00:18:25.320> that<00:18:25.559> that<00:18:25.679> reduce<00:18:25.919> the 00:18:26.150 --> 00:18:26.160 align:start position:0% the other things that that reduce the 00:18:26.160 --> 00:18:28.250 align:start position:0% the other things that that reduce the layer<00:18:26.460> to<00:18:26.580> transaction<00:18:27.120> cost 00:18:28.250 --> 00:18:28.260 align:start position:0% layer to transaction cost 00:18:28.260 --> 00:18:30.710 align:start position:0% layer to transaction cost um<00:18:28.320> will<00:18:29.100> open<00:18:29.520> up<00:18:29.700> the<00:18:29.880> applications<00:18:30.179> towards 00:18:30.710 --> 00:18:30.720 align:start position:0% um will open up the applications towards 00:18:30.720 --> 00:18:33.590 align:start position:0% um will open up the applications towards a<00:18:30.900> microfinance<00:18:31.620> in<00:18:31.799> developing<00:18:32.220> economies 00:18:33.590 --> 00:18:33.600 align:start position:0% a microfinance in developing economies 00:18:33.600 --> 00:18:35.270 align:start position:0% a microfinance in developing economies so<00:18:34.020> this<00:18:34.200> is<00:18:34.320> where<00:18:34.440> we<00:18:34.559> are<00:18:34.679> now<00:18:34.860> we're<00:18:35.100> live 00:18:35.270 --> 00:18:35.280 align:start position:0% so this is where we are now we're live 00:18:35.280 --> 00:18:37.490 align:start position:0% so this is where we are now we're live on<00:18:35.460> arbitrim<00:18:35.940> nitrogioli<00:18:36.900> test<00:18:37.020> net<00:18:37.200> and 00:18:37.490 --> 00:18:37.500 align:start position:0% on arbitrim nitrogioli test net and 00:18:37.500 --> 00:18:38.810 align:start position:0% on arbitrim nitrogioli test net and we're<00:18:37.620> going<00:18:37.740> to<00:18:37.799> be<00:18:37.860> deploying<00:18:38.220> to<00:18:38.340> Arboretum 00:18:38.810 --> 00:18:38.820 align:start position:0% we're going to be deploying to Arboretum 00:18:38.820 --> 00:18:40.430 align:start position:0% we're going to be deploying to Arboretum and<00:18:38.940> optimism<00:18:39.240> after<00:18:39.419> some<00:18:39.720> autofixes<00:18:40.260> and 00:18:40.430 --> 00:18:40.440 align:start position:0% and optimism after some autofixes and 00:18:40.440 --> 00:18:43.010 align:start position:0% and optimism after some autofixes and other<00:18:40.620> layer<00:18:41.280> twos<00:18:41.520> that<00:18:41.640> evm<00:18:42.059> compatible<00:18:42.840> or 00:18:43.010 --> 00:18:43.020 align:start position:0% other layer twos that evm compatible or 00:18:43.020 --> 00:18:44.690 align:start position:0% other layer twos that evm compatible or equivalent 00:18:44.690 --> 00:18:44.700 align:start position:0% equivalent 00:18:44.700 --> 00:18:46.250 align:start position:0% equivalent we'll<00:18:45.120> seek<00:18:45.360> to<00:18:45.480> do<00:18:45.539> what 00:18:46.250 --> 00:18:46.260 align:start position:0% we'll seek to do what 00:18:46.260 --> 00:18:47.510 align:start position:0% we'll seek to do what um<00:18:46.320> basically<00:18:46.559> get<00:18:46.740> this<00:18:46.919> into<00:18:47.100> wallets 00:18:47.510 --> 00:18:47.520 align:start position:0% um basically get this into wallets 00:18:47.520 --> 00:18:49.490 align:start position:0% um basically get this into wallets currently<00:18:48.179> and<00:18:48.480> to<00:18:48.660> encourage<00:18:48.900> ducks<00:18:49.260> to<00:18:49.440> use 00:18:49.490 --> 00:18:49.500 align:start position:0% currently and to encourage ducks to use 00:18:49.500 --> 00:18:51.289 align:start position:0% currently and to encourage ducks to use it<00:18:49.679> so<00:18:50.039> we'll<00:18:50.220> first<00:18:50.520> Target<00:18:50.760> applications 00:18:51.289 --> 00:18:51.299 align:start position:0% it so we'll first Target applications 00:18:51.299 --> 00:18:53.330 align:start position:0% it so we'll first Target applications where<00:18:51.720> this<00:18:52.020> will<00:18:52.320> have<00:18:52.500> a<00:18:52.620> direct<00:18:52.740> benefit<00:18:52.980> to 00:18:53.330 --> 00:18:53.340 align:start position:0% where this will have a direct benefit to 00:18:53.340 --> 00:18:55.970 align:start position:0% where this will have a direct benefit to help<00:18:53.520> help<00:18:53.820> sort<00:18:54.360> of<00:18:54.419> priced<00:18:54.660> out<00:18:54.840> users<00:18:55.140> and 00:18:55.970 --> 00:18:55.980 align:start position:0% help help sort of priced out users and 00:18:55.980 --> 00:18:58.130 align:start position:0% help help sort of priced out users and of<00:18:56.400> course<00:18:56.580> support<00:18:56.820> regular<00:18:57.720> web<00:18:57.900> free 00:18:58.130 --> 00:18:58.140 align:start position:0% of course support regular web free 00:18:58.140 --> 00:19:00.470 align:start position:0% of course support regular web free wallets<00:18:58.500> with<00:18:58.980> integration<00:18:59.400> via<00:18:59.760> 4337 00:19:00.470 --> 00:19:00.480 align:start position:0% wallets with integration via 4337 00:19:00.480 --> 00:19:01.789 align:start position:0% wallets with integration via 4337 because<00:19:00.720> that<00:19:01.020> seems<00:19:01.380> to<00:19:01.440> be<00:19:01.500> where<00:19:01.620> the 00:19:01.789 --> 00:19:01.799 align:start position:0% because that seems to be where the 00:19:01.799 --> 00:19:03.830 align:start position:0% because that seems to be where the attention<00:19:02.039> is<00:19:02.280> with<00:19:02.760> wallets 00:19:03.830 --> 00:19:03.840 align:start position:0% attention is with wallets 00:19:03.840 --> 00:19:05.630 align:start position:0% attention is with wallets and<00:19:04.320> further<00:19:04.679> optimization<00:19:05.100> will<00:19:05.400> just<00:19:05.520> be 00:19:05.630 --> 00:19:05.640 align:start position:0% and further optimization will just be 00:19:05.640 --> 00:19:07.390 align:start position:0% and further optimization will just be ongoing<00:19:05.940> we'll<00:19:06.120> look<00:19:06.360> to<00:19:06.480> do<00:19:06.600> those<00:19:06.840> other 00:19:07.390 --> 00:19:07.400 align:start position:0% ongoing we'll look to do those other 00:19:07.400 --> 00:19:09.890 align:start position:0% ongoing we'll look to do those other optimizations<00:19:08.400> to<00:19:09.179> make<00:19:09.299> transactions 00:19:09.890 --> 00:19:09.900 align:start position:0% optimizations to make transactions 00:19:09.900 --> 00:19:11.690 align:start position:0% optimizations to make transactions cheaper<00:19:10.500> for<00:19:11.039> the<00:19:11.160> wallets<00:19:11.400> that<00:19:11.520> already 00:19:11.690 --> 00:19:11.700 align:start position:0% cheaper for the wallets that already 00:19:11.700 --> 00:19:14.630 align:start position:0% cheaper for the wallets that already have<00:19:11.940> it<00:19:12.120> integrated 00:19:14.630 --> 00:19:14.640 align:start position:0% 00:19:14.640 --> 00:19:15.710 align:start position:0% and<00:19:14.880> of<00:19:14.940> course<00:19:15.059> things<00:19:15.240> just<00:19:15.419> get<00:19:15.600> even 00:19:15.710 --> 00:19:15.720 align:start position:0% and of course things just get even 00:19:15.720 --> 00:19:17.930 align:start position:0% and of course things just get even better<00:19:15.900> when<00:19:16.380> when<00:19:16.919> uh<00:19:17.340> four<00:19:17.460> eight<00:19:17.640> four<00:19:17.880> four 00:19:17.930 --> 00:19:17.940 align:start position:0% better when when uh four eight four four 00:19:17.940 --> 00:19:20.270 align:start position:0% better when when uh four eight four four drops<00:19:18.900> so<00:19:19.260> this<00:19:19.380> is<00:19:19.440> how<00:19:19.559> it<00:19:19.679> feels<00:19:19.860> to<00:19:19.980> me<00:19:20.100> that 00:19:20.270 --> 00:19:20.280 align:start position:0% drops so this is how it feels to me that 00:19:20.280 --> 00:19:21.650 align:start position:0% drops so this is how it feels to me that we've<00:19:20.460> got<00:19:20.580> on<00:19:20.820> the<00:19:20.940> one<00:19:21.059> hand<00:19:21.179> a<00:19:21.360> lot<00:19:21.480> of<00:19:21.539> real 00:19:21.650 --> 00:19:21.660 align:start position:0% we've got on the one hand a lot of real 00:19:21.660 --> 00:19:24.110 align:start position:0% we've got on the one hand a lot of real world<00:19:21.840> problems<00:19:22.380> that<00:19:23.100> kind<00:19:23.640> of<00:19:23.700> a<00:19:23.820> cut<00:19:24.000> out 00:19:24.110 --> 00:19:24.120 align:start position:0% world problems that kind of a cut out 00:19:24.120 --> 00:19:25.789 align:start position:0% world problems that kind of a cut out from<00:19:24.360> the<00:19:24.539> web<00:19:24.720> free<00:19:24.960> Solutions<00:19:25.320> due<00:19:25.620> to<00:19:25.679> the 00:19:25.789 --> 00:19:25.799 align:start position:0% from the web free Solutions due to the 00:19:25.799 --> 00:19:28.909 align:start position:0% from the web free Solutions due to the cost<00:19:25.980> per<00:19:26.160> transaction<00:19:26.580> but<00:19:28.020> um 00:19:28.909 --> 00:19:28.919 align:start position:0% cost per transaction but um 00:19:28.919 --> 00:19:30.470 align:start position:0% cost per transaction but um we<00:19:29.340> hope<00:19:29.460> that<00:19:29.580> we<00:19:29.700> sort<00:19:29.820> of<00:19:29.940> once<00:19:30.120> that<00:19:30.240> joins 00:19:30.470 --> 00:19:30.480 align:start position:0% we hope that we sort of once that joins 00:19:30.480 --> 00:19:32.210 align:start position:0% we hope that we sort of once that joins in<00:19:30.600> that<00:19:30.780> we<00:19:30.960> will<00:19:31.200> get<00:19:31.440> these<00:19:31.799> real<00:19:32.039> world 00:19:32.210 --> 00:19:32.220 align:start position:0% in that we will get these real world 00:19:32.220 --> 00:19:33.950 align:start position:0% in that we will get these real world problems<00:19:32.580> being<00:19:32.820> solved<00:19:33.120> by<00:19:33.179> web3<00:19:33.539> Solutions 00:19:33.950 --> 00:19:33.960 align:start position:0% problems being solved by web3 Solutions 00:19:33.960 --> 00:19:36.650 align:start position:0% problems being solved by web3 Solutions and<00:19:34.740> uh<00:19:35.100> yeah<00:19:35.460> we<00:19:35.760> just<00:19:35.940> sort<00:19:36.240> of<00:19:36.360> are<00:19:36.480> looking 00:19:36.650 --> 00:19:36.660 align:start position:0% and uh yeah we just sort of are looking 00:19:36.660 --> 00:19:37.669 align:start position:0% and uh yeah we just sort of are looking forward<00:19:36.840> to<00:19:37.020> that<00:19:37.140> time<00:19:37.320> because<00:19:37.440> I<00:19:37.559> think 00:19:37.669 --> 00:19:37.679 align:start position:0% forward to that time because I think 00:19:37.679 --> 00:19:39.049 align:start position:0% forward to that time because I think that's<00:19:37.799> when<00:19:37.980> we'll<00:19:38.160> get<00:19:38.340> again<00:19:38.460> a<00:19:38.700> Resurgence 00:19:39.049 --> 00:19:39.059 align:start position:0% that's when we'll get again a Resurgence 00:19:39.059 --> 00:19:41.330 align:start position:0% that's when we'll get again a Resurgence of<00:19:39.299> a<00:19:40.140> lot<00:19:40.320> of<00:19:40.440> activity<00:19:40.740> we<00:19:40.919> have<00:19:41.100> a<00:19:41.160> lot<00:19:41.280> of 00:19:41.330 --> 00:19:41.340 align:start position:0% of a lot of activity we have a lot of 00:19:41.340 --> 00:19:42.710 align:start position:0% of a lot of activity we have a lot of users<00:19:41.640> will<00:19:42.000> actually<00:19:42.179> be<00:19:42.360> able<00:19:42.480> to<00:19:42.600> benefit 00:19:42.710 --> 00:19:42.720 align:start position:0% users will actually be able to benefit 00:19:42.720 --> 00:19:44.270 align:start position:0% users will actually be able to benefit from<00:19:43.080> The<00:19:43.260> Primitives<00:19:43.799> that<00:19:43.980> we're<00:19:44.160> building 00:19:44.270 --> 00:19:44.280 align:start position:0% from The Primitives that we're building 00:19:44.280 --> 00:19:46.850 align:start position:0% from The Primitives that we're building but<00:19:45.059> everyone's<00:19:45.419> building<00:19:45.600> in<00:19:45.780> the<00:19:46.080> community 00:19:46.850 --> 00:19:46.860 align:start position:0% but everyone's building in the community 00:19:46.860 --> 00:19:49.430 align:start position:0% but everyone's building in the community So<00:19:47.280> This<00:19:47.460> Is<00:19:47.580> Us<00:19:47.700> where<00:19:47.940> web<00:19:48.179> BLS<00:19:48.960> wallet<00:19:49.320> if 00:19:49.430 --> 00:19:49.440 align:start position:0% So This Is Us where web BLS wallet if 00:19:49.440 --> 00:19:51.289 align:start position:0% So This Is Us where web BLS wallet if you<00:19:49.620> want<00:19:49.679> to<00:19:49.799> learn<00:19:49.919> more<00:19:50.100> check<00:19:50.880> it<00:19:51.059> out<00:19:51.120> in 00:19:51.289 --> 00:19:51.299 align:start position:0% you want to learn more check it out in 00:19:51.299 --> 00:19:53.630 align:start position:0% you want to learn more check it out in browser<00:19:51.720> demo<00:19:52.020> it's<00:19:52.559> at<00:19:52.679> BLS<00:19:53.039> wallet.org 00:19:53.630 --> 00:19:53.640 align:start position:0% browser demo it's at BLS wallet.org 00:19:53.640 --> 00:19:54.950 align:start position:0% browser demo it's at BLS wallet.org maybe<00:19:53.820> don't<00:19:54.059> hit<00:19:54.179> it<00:19:54.360> all<00:19:54.480> at<00:19:54.539> once<00:19:54.720> in<00:19:54.840> case 00:19:54.950 --> 00:19:54.960 align:start position:0% maybe don't hit it all at once in case 00:19:54.960 --> 00:19:57.230 align:start position:0% maybe don't hit it all at once in case it<00:19:55.080> crashes<00:19:55.440> but<00:19:55.620> it'll<00:19:55.860> be<00:19:55.980> fine<00:19:56.160> check<00:19:57.120> it 00:19:57.230 --> 00:19:57.240 align:start position:0% it crashes but it'll be fine check it 00:19:57.240 --> 00:19:59.029 align:start position:0% it crashes but it'll be fine check it out<00:19:57.360> GitHub<00:19:57.660> there's<00:19:58.020> a<00:19:58.140> Discord<00:19:58.380> web3well 00:19:59.029 --> 00:19:59.039 align:start position:0% out GitHub there's a Discord web3well 00:19:59.039 --> 00:20:01.430 align:start position:0% out GitHub there's a Discord web3well and<00:19:59.640> um<00:19:59.640> yeah<00:19:59.820> are<00:19:59.940> there<00:20:00.059> any<00:20:00.120> questions 00:20:01.430 --> 00:20:01.440 align:start position:0% and um yeah are there any questions 00:20:01.440 --> 00:20:04.490 align:start position:0% and um yeah are there any questions okay<00:20:01.799> I<00:20:02.460> just<00:20:02.640> question<00:20:03.000> yeah<00:20:03.240> okay 00:20:04.490 --> 00:20:04.500 align:start position:0% okay I just question yeah okay 00:20:04.500 --> 00:20:06.529 align:start position:0% okay I just question yeah okay um again<00:20:04.740> uh<00:20:05.580> congratulations<00:20:06.000> for<00:20:06.360> the 00:20:06.529 --> 00:20:06.539 align:start position:0% um again uh congratulations for the 00:20:06.539 --> 00:20:08.570 align:start position:0% um again uh congratulations for the project<00:20:06.720> it's<00:20:07.020> very<00:20:07.380> it's<00:20:07.799> going<00:20:08.039> to<00:20:08.160> be<00:20:08.280> very 00:20:08.570 --> 00:20:08.580 align:start position:0% project it's very it's going to be very 00:20:08.580 --> 00:20:12.110 align:start position:0% project it's very it's going to be very useful<00:20:08.880> to<00:20:09.299> the<00:20:09.419> community<00:20:09.860> my<00:20:10.860> question<00:20:10.980> is 00:20:12.110 --> 00:20:12.120 align:start position:0% useful to the community my question is 00:20:12.120 --> 00:20:14.090 align:start position:0% useful to the community my question is um<00:20:12.179> when<00:20:12.600> you<00:20:12.720> create<00:20:12.900> the<00:20:13.200> wallet<00:20:13.559> and<00:20:13.799> make 00:20:14.090 --> 00:20:14.100 align:start position:0% um when you create the wallet and make 00:20:14.100 --> 00:20:16.669 align:start position:0% um when you create the wallet and make this<00:20:14.460> this<00:20:14.820> changes<00:20:15.419> you're<00:20:15.660> proposing<00:20:16.260> that 00:20:16.669 --> 00:20:16.679 align:start position:0% this this changes you're proposing that 00:20:16.679 --> 00:20:17.990 align:start position:0% this this changes you're proposing that is<00:20:16.919> great 00:20:17.990 --> 00:20:18.000 align:start position:0% is great 00:20:18.000 --> 00:20:20.810 align:start position:0% is great you<00:20:18.600> need<00:20:18.780> also<00:20:19.200> to<00:20:19.380> update<00:20:20.160> to<00:20:20.280> the<00:20:20.460> clients 00:20:20.810 --> 00:20:20.820 align:start position:0% you need also to update to the clients 00:20:20.820 --> 00:20:22.669 align:start position:0% you need also to update to the clients because<00:20:21.299> for<00:20:21.600> instance<00:20:21.780> to<00:20:22.080> support<00:20:22.320> the 00:20:22.669 --> 00:20:22.679 align:start position:0% because for instance to support the 00:20:22.679 --> 00:20:23.710 align:start position:0% because for instance to support the multiple 00:20:23.710 --> 00:20:23.720 align:start position:0% multiple 00:20:23.720 --> 00:20:26.150 align:start position:0% multiple transactions<00:20:24.720> they<00:20:25.140> want<00:20:25.380> to<00:20:25.440> sign<00:20:25.559> it<00:20:25.799> it's 00:20:26.150 --> 00:20:26.160 align:start position:0% transactions they want to sign it it's 00:20:26.160 --> 00:20:27.610 align:start position:0% transactions they want to sign it it's amazing<00:20:26.640> idea 00:20:27.610 --> 00:20:27.620 align:start position:0% amazing idea 00:20:27.620 --> 00:20:31.070 align:start position:0% amazing idea are<00:20:28.620> you<00:20:28.740> talking<00:20:29.039> to<00:20:29.760> the<00:20:30.240> I<00:20:30.539> don't<00:20:30.660> know<00:20:30.780> with 00:20:31.070 --> 00:20:31.080 align:start position:0% are you talking to the I don't know with 00:20:31.080 --> 00:20:34.970 align:start position:0% are you talking to the I don't know with execution<00:20:31.740> layer<00:20:32.160> clients<00:20:32.820> to<00:20:33.480> help<00:20:34.020> them<00:20:34.320> to 00:20:34.970 --> 00:20:34.980 align:start position:0% execution layer clients to help them to 00:20:34.980 --> 00:20:40.130 align:start position:0% execution layer clients to help them to adopt<00:20:35.700> their<00:20:36.179> clients<00:20:37.039> how<00:20:38.039> are<00:20:38.539> being<00:20:39.539> those 00:20:40.130 --> 00:20:40.140 align:start position:0% adopt their clients how are being those 00:20:40.140 --> 00:20:42.529 align:start position:0% adopt their clients how are being those conversations<00:20:40.679> absolutely<00:20:41.220> yeah<00:20:41.700> so 00:20:42.529 --> 00:20:42.539 align:start position:0% conversations absolutely yeah so 00:20:42.539 --> 00:20:44.450 align:start position:0% conversations absolutely yeah so um<00:20:42.600> quite<00:20:42.840> a<00:20:42.960> while<00:20:43.020> ago<00:20:43.320> we<00:20:43.559> we<00:20:43.799> started<00:20:44.280> that 00:20:44.450 --> 00:20:44.460 align:start position:0% um quite a while ago we we started that 00:20:44.460 --> 00:20:46.490 align:start position:0% um quite a while ago we we started that Journey<00:20:45.000> we<00:20:45.240> started<00:20:45.539> contacting<00:20:45.960> I<00:20:46.380> think 00:20:46.490 --> 00:20:46.500 align:start position:0% Journey we started contacting I think 00:20:46.500 --> 00:20:48.049 align:start position:0% Journey we started contacting I think there<00:20:46.679> was<00:20:46.860> even<00:20:47.039> end<00:20:47.400> of<00:20:47.520> last<00:20:47.700> year<00:20:47.880> I 00:20:48.049 --> 00:20:48.059 align:start position:0% there was even end of last year I 00:20:48.059 --> 00:20:49.970 align:start position:0% there was even end of last year I started<00:20:48.360> contacting<00:20:48.780> some<00:20:49.020> wallets<00:20:49.440> just<00:20:49.860> to 00:20:49.970 --> 00:20:49.980 align:start position:0% started contacting some wallets just to 00:20:49.980 --> 00:20:51.350 align:start position:0% started contacting some wallets just to see<00:20:50.160> which<00:20:50.400> ones<00:20:50.580> might<00:20:50.760> be<00:20:50.880> interested<00:20:51.120> how 00:20:51.350 --> 00:20:51.360 align:start position:0% see which ones might be interested how 00:20:51.360 --> 00:20:53.210 align:start position:0% see which ones might be interested how to<00:20:51.480> begin<00:20:51.600> that<00:20:51.900> conversation<00:20:52.320> and<00:20:52.860> so<00:20:52.980> it's<00:20:53.100> a 00:20:53.210 --> 00:20:53.220 align:start position:0% to begin that conversation and so it's a 00:20:53.220 --> 00:20:54.590 align:start position:0% to begin that conversation and so it's a very<00:20:53.340> good<00:20:53.460> question 00:20:54.590 --> 00:20:54.600 align:start position:0% very good question 00:20:54.600 --> 00:20:56.450 align:start position:0% very good question um we<00:20:55.140> had<00:20:55.440> some<00:20:55.620> interest<00:20:55.799> from<00:20:56.039> wallets 00:20:56.450 --> 00:20:56.460 align:start position:0% um we had some interest from wallets 00:20:56.460 --> 00:20:58.010 align:start position:0% um we had some interest from wallets certain<00:20:56.760> wallets<00:20:57.120> are<00:20:57.240> saying<00:20:57.419> yes<00:20:57.539> we<00:20:57.720> want 00:20:58.010 --> 00:20:58.020 align:start position:0% certain wallets are saying yes we want 00:20:58.020 --> 00:20:59.150 align:start position:0% certain wallets are saying yes we want to<00:20:58.140> do<00:20:58.200> this<00:20:58.260> it's<00:20:58.440> quite<00:20:58.620> interesting<00:20:58.919> but 00:20:59.150 --> 00:20:59.160 align:start position:0% to do this it's quite interesting but 00:20:59.160 --> 00:21:01.250 align:start position:0% to do this it's quite interesting but with<00:20:59.520> what<00:20:59.700> we<00:20:59.820> had<00:21:00.000> it<00:21:00.240> just<00:21:00.600> seemed<00:21:00.960> to<00:21:01.080> not 00:21:01.250 --> 00:21:01.260 align:start position:0% with what we had it just seemed to not 00:21:01.260 --> 00:21:03.049 align:start position:0% with what we had it just seemed to not get<00:21:01.620> integrated<00:21:01.980> so<00:21:02.400> there<00:21:02.520> was<00:21:02.640> a<00:21:02.760> bit<00:21:02.820> of<00:21:02.940> a 00:21:03.049 --> 00:21:03.059 align:start position:0% get integrated so there was a bit of a 00:21:03.059 --> 00:21:05.029 align:start position:0% get integrated so there was a bit of a delay<00:21:03.299> I<00:21:03.480> think<00:21:03.539> from<00:21:03.720> wallets<00:21:04.080> but<00:21:04.380> we<00:21:04.919> were 00:21:05.029 --> 00:21:05.039 align:start position:0% delay I think from wallets but we were 00:21:05.039 --> 00:21:07.190 align:start position:0% delay I think from wallets but we were also<00:21:05.340> not<00:21:05.520> live<00:21:05.760> yet<00:21:06.059> so<00:21:06.480> I<00:21:06.600> think<00:21:06.720> once<00:21:07.080> we're 00:21:07.190 --> 00:21:07.200 align:start position:0% also not live yet so I think once we're 00:21:07.200 --> 00:21:10.250 align:start position:0% also not live yet so I think once we're live<00:21:07.380> that<00:21:07.740> will<00:21:07.860> be<00:21:07.980> helpful<00:21:08.299> when<00:21:09.299> 4357<00:21:10.020> came 00:21:10.250 --> 00:21:10.260 align:start position:0% live that will be helpful when 4357 came 00:21:10.260 --> 00:21:11.570 align:start position:0% live that will be helpful when 4357 came about<00:21:10.380> which<00:21:10.919> is<00:21:11.039> the<00:21:11.160> on-chain<00:21:11.460> account 00:21:11.570 --> 00:21:11.580 align:start position:0% about which is the on-chain account 00:21:11.580 --> 00:21:13.190 align:start position:0% about which is the on-chain account abstraction<00:21:12.120> there<00:21:12.840> was<00:21:12.960> a<00:21:13.080> lot<00:21:13.140> of 00:21:13.190 --> 00:21:13.200 align:start position:0% abstraction there was a lot of 00:21:13.200 --> 00:21:14.390 align:start position:0% abstraction there was a lot of conversation<00:21:13.559> interest<00:21:13.919> around<00:21:14.160> that 00:21:14.390 --> 00:21:14.400 align:start position:0% conversation interest around that 00:21:14.400 --> 00:21:16.430 align:start position:0% conversation interest around that standard<00:21:14.820> and<00:21:15.120> so<00:21:15.299> maybe<00:21:15.539> the<00:21:15.840> wallets<00:21:16.140> will 00:21:16.430 --> 00:21:16.440 align:start position:0% standard and so maybe the wallets will 00:21:16.440 --> 00:21:18.590 align:start position:0% standard and so maybe the wallets will integrate<00:21:17.039> that<00:21:17.280> standard<00:21:17.640> sooner<00:21:18.120> and<00:21:18.539> then 00:21:18.590 --> 00:21:18.600 align:start position:0% integrate that standard sooner and then 00:21:18.600 --> 00:21:19.909 align:start position:0% integrate that standard sooner and then we<00:21:18.780> can<00:21:18.900> have<00:21:19.080> those<00:21:19.260> conversations<00:21:19.679> again 00:21:19.909 --> 00:21:19.919 align:start position:0% we can have those conversations again 00:21:19.919 --> 00:21:20.930 align:start position:0% we can have those conversations again and<00:21:20.100> to<00:21:20.220> say<00:21:20.340> look<00:21:20.460> here<00:21:20.640> is<00:21:20.760> an 00:21:20.930 --> 00:21:20.940 align:start position:0% and to say look here is an 00:21:20.940 --> 00:21:22.010 align:start position:0% and to say look here is an implementation<00:21:21.419> and<00:21:21.660> these<00:21:21.840> are<00:21:21.960> the 00:21:22.010 --> 00:21:22.020 align:start position:0% implementation and these are the 00:21:22.020 --> 00:21:23.270 align:start position:0% implementation and these are the features<00:21:22.260> of<00:21:22.380> this<00:21:22.500> one<00:21:22.679> and<00:21:22.980> I'm<00:21:23.100> sure 00:21:23.270 --> 00:21:23.280 align:start position:0% features of this one and I'm sure 00:21:23.280 --> 00:21:24.409 align:start position:0% features of this one and I'm sure there'll<00:21:23.460> be<00:21:23.520> other<00:21:23.700> implementations<00:21:24.179> for 00:21:24.409 --> 00:21:24.419 align:start position:0% there'll be other implementations for 00:21:24.419 --> 00:21:26.270 align:start position:0% there'll be other implementations for other<00:21:24.600> signature<00:21:25.020> schemes<00:21:25.380> so<00:21:25.740> there<00:21:25.919> will<00:21:26.100> be 00:21:26.270 --> 00:21:26.280 align:start position:0% other signature schemes so there will be 00:21:26.280 --> 00:21:28.549 align:start position:0% other signature schemes so there will be a<00:21:26.460> change<00:21:26.640> on<00:21:26.940> the<00:21:27.240> wallet<00:21:27.900> side<00:21:28.080> so<00:21:28.320> that<00:21:28.440> I 00:21:28.549 --> 00:21:28.559 align:start position:0% a change on the wallet side so that I 00:21:28.559 --> 00:21:29.750 align:start position:0% a change on the wallet side so that I have<00:21:28.679> to<00:21:28.740> sign<00:21:28.860> with<00:21:29.039> a<00:21:29.220> different<00:21:29.340> signature 00:21:29.750 --> 00:21:29.760 align:start position:0% have to sign with a different signature 00:21:29.760 --> 00:21:32.390 align:start position:0% have to sign with a different signature scheme<00:21:30.120> and<00:21:30.720> then<00:21:30.900> obviously<00:21:31.740> in<00:21:31.860> the<00:21:31.980> UI<00:21:32.220> and 00:21:32.390 --> 00:21:32.400 align:start position:0% scheme and then obviously in the UI and 00:21:32.400 --> 00:21:35.510 align:start position:0% scheme and then obviously in the UI and all<00:21:32.520> that<00:21:32.900> apart<00:21:33.900> from<00:21:34.140> the<00:21:34.500> quill<00:21:35.039> extension 00:21:35.510 --> 00:21:35.520 align:start position:0% all that apart from the quill extension 00:21:35.520 --> 00:21:37.690 align:start position:0% all that apart from the quill extension which<00:21:35.700> is<00:21:35.820> the<00:21:36.600> um<00:21:36.600> basically<00:21:36.960> a<00:21:37.140> reference 00:21:37.690 --> 00:21:37.700 align:start position:0% which is the um basically a reference 00:21:37.700 --> 00:21:41.029 align:start position:0% which is the um basically a reference browser<00:21:38.700> wallet<00:21:39.059> we've<00:21:39.840> also<00:21:40.020> gone<00:21:40.200> through<00:21:40.440> a 00:21:41.029 --> 00:21:41.039 align:start position:0% browser wallet we've also gone through a 00:21:41.039 --> 00:21:42.830 align:start position:0% browser wallet we've also gone through a large<00:21:41.460> design 00:21:42.830 --> 00:21:42.840 align:start position:0% large design 00:21:42.840 --> 00:21:44.630 align:start position:0% large design um<00:21:42.900> I<00:21:43.620> guess 00:21:44.630 --> 00:21:44.640 align:start position:0% um I guess 00:21:44.640 --> 00:21:46.310 align:start position:0% um I guess um yeah<00:21:45.000> a<00:21:45.299> large<00:21:45.419> design<00:21:45.659> a<00:21:45.900> set<00:21:46.020> of<00:21:46.140> design 00:21:46.310 --> 00:21:46.320 align:start position:0% um yeah a large design a set of design 00:21:46.320 --> 00:21:48.590 align:start position:0% um yeah a large design a set of design and<00:21:46.620> to<00:21:47.220> look<00:21:47.460> at<00:21:47.580> what<00:21:47.880> future<00:21:48.000> wallets<00:21:48.419> can 00:21:48.590 --> 00:21:48.600 align:start position:0% and to look at what future wallets can 00:21:48.600 --> 00:21:50.830 align:start position:0% and to look at what future wallets can look<00:21:48.780> like<00:21:48.900> so<00:21:49.380> these<00:21:49.620> can<00:21:49.740> form<00:21:49.919> a<00:21:50.100> bit<00:21:50.220> of<00:21:50.340> a 00:21:50.830 --> 00:21:50.840 align:start position:0% look like so these can form a bit of a 00:21:50.840 --> 00:21:52.850 align:start position:0% look like so these can form a bit of a you<00:21:51.840> know<00:21:51.900> a<00:21:52.020> bit<00:21:52.080> of<00:21:52.200> design<00:21:52.380> help<00:21:52.679> for 00:21:52.850 --> 00:21:52.860 align:start position:0% you know a bit of design help for 00:21:52.860 --> 00:21:54.409 align:start position:0% you know a bit of design help for wallets<00:21:53.220> as<00:21:53.400> well 00:21:54.409 --> 00:21:54.419 align:start position:0% wallets as well 00:21:54.419 --> 00:21:55.010 align:start position:0% wallets as well um 00:21:55.010 --> 00:21:55.020 align:start position:0% um 00:21:55.020 --> 00:21:57.169 align:start position:0% um oh<00:21:55.440> yeah 00:21:57.169 --> 00:21:57.179 align:start position:0% oh yeah 00:21:57.179 --> 00:22:00.409 align:start position:0% oh yeah okay 00:22:00.409 --> 00:22:00.419 align:start position:0% 00:22:00.419 --> 00:22:06.190 align:start position:0% oh 00:22:06.190 --> 00:22:06.200 align:start position:0% 00:22:06.200 --> 00:22:10.190 align:start position:0% uh<00:22:07.200> yeah<00:22:07.919> with<00:22:08.340> the<00:22:08.580> clients<00:22:08.940> like<00:22:09.179> Geth<00:22:09.720> or 00:22:10.190 --> 00:22:10.200 align:start position:0% uh yeah with the clients like Geth or 00:22:10.200 --> 00:22:13.310 align:start position:0% uh yeah with the clients like Geth or neighbors<00:22:10.860> are<00:22:11.400> you<00:22:11.580> talking<00:22:11.760> to<00:22:12.059> those<00:22:12.600> teams 00:22:13.310 --> 00:22:13.320 align:start position:0% neighbors are you talking to those teams 00:22:13.320 --> 00:22:15.909 align:start position:0% neighbors are you talking to those teams so<00:22:14.100> so<00:22:14.460> foreign 00:22:15.909 --> 00:22:15.919 align:start position:0% so so foreign 00:22:15.919 --> 00:22:18.529 align:start position:0% so so foreign maybe<00:22:16.919> shows<00:22:17.220> it<00:22:17.340> better 00:22:18.529 --> 00:22:18.539 align:start position:0% maybe shows it better 00:22:18.539 --> 00:22:20.390 align:start position:0% maybe shows it better um<00:22:18.600> this<00:22:19.080> is<00:22:19.200> a<00:22:19.260> bit<00:22:19.320> slow 00:22:20.390 --> 00:22:20.400 align:start position:0% um this is a bit slow 00:22:20.400 --> 00:22:22.070 align:start position:0% um this is a bit slow yeah<00:22:20.520> so<00:22:20.940> the 00:22:22.070 --> 00:22:22.080 align:start position:0% yeah so the 00:22:22.080 --> 00:22:24.289 align:start position:0% yeah so the the<00:22:22.140> nodes<00:22:22.740> don't<00:22:22.980> need<00:22:23.159> to<00:22:23.280> change<00:22:23.460> so<00:22:23.880> so<00:22:24.059> the 00:22:24.289 --> 00:22:24.299 align:start position:0% the nodes don't need to change so so the 00:22:24.299 --> 00:22:25.789 align:start position:0% the nodes don't need to change so so the clients<00:22:24.600> that<00:22:24.840> uh<00:22:25.020> the<00:22:25.500> um<00:22:25.500> say<00:22:25.679> the 00:22:25.789 --> 00:22:25.799 align:start position:0% clients that uh the um say the 00:22:25.799 --> 00:22:29.390 align:start position:0% clients that uh the um say the aggregators<00:22:26.280> here<00:22:26.520> we<00:22:26.700> go<00:22:26.820> uh<00:22:27.539> this<00:22:27.720> one<00:22:28.260> so<00:22:29.039> at 00:22:29.390 --> 00:22:29.400 align:start position:0% aggregators here we go uh this one so at 00:22:29.400 --> 00:22:30.830 align:start position:0% aggregators here we go uh this one so at the<00:22:29.460> moment<00:22:29.580> we<00:22:29.760> have<00:22:29.940> a<00:22:30.059> dedicated<00:22:30.419> server 00:22:30.830 --> 00:22:30.840 align:start position:0% the moment we have a dedicated server 00:22:30.840 --> 00:22:32.510 align:start position:0% the moment we have a dedicated server that<00:22:31.080> will<00:22:31.260> do<00:22:31.500> the<00:22:31.620> bundling<00:22:31.919> we've<00:22:32.400> already 00:22:32.510 --> 00:22:32.520 align:start position:0% that will do the bundling we've already 00:22:32.520 --> 00:22:35.029 align:start position:0% that will do the bundling we've already had<00:22:32.760> conversations<00:22:33.240> with<00:22:34.020> um<00:22:34.020> one<00:22:34.740> particular 00:22:35.029 --> 00:22:35.039 align:start position:0% had conversations with um one particular 00:22:35.039 --> 00:22:37.669 align:start position:0% had conversations with um one particular Layer<00:22:35.640> Two<00:22:35.760> about<00:22:36.059> this<00:22:36.360> to<00:22:36.600> say<00:22:36.780> that<00:22:37.440> they 00:22:37.669 --> 00:22:37.679 align:start position:0% Layer Two about this to say that they 00:22:37.679 --> 00:22:39.590 align:start position:0% Layer Two about this to say that they would<00:22:37.799> want<00:22:37.980> to<00:22:38.100> integrate<00:22:38.460> this<00:22:39.059> um<00:22:39.059> so<00:22:39.480> for 00:22:39.590 --> 00:22:39.600 align:start position:0% would want to integrate this um so for 00:22:39.600 --> 00:22:41.090 align:start position:0% would want to integrate this um so for us<00:22:39.720> that's<00:22:39.900> been<00:22:40.140> not<00:22:40.500> been<00:22:40.679> the<00:22:40.799> barrier 00:22:41.090 --> 00:22:41.100 align:start position:0% us that's been not been the barrier 00:22:41.100 --> 00:22:43.669 align:start position:0% us that's been not been the barrier we've<00:22:41.340> heard<00:22:41.760> great<00:22:42.120> enthusiasm<00:22:42.780> from 00:22:43.669 --> 00:22:43.679 align:start position:0% we've heard great enthusiasm from 00:22:43.679 --> 00:22:45.950 align:start position:0% we've heard great enthusiasm from um the<00:22:43.980> layer<00:22:44.280> 2<00:22:44.460> networks<00:22:44.940> to<00:22:45.299> say<00:22:45.419> as<00:22:45.840> soon 00:22:45.950 --> 00:22:45.960 align:start position:0% um the layer 2 networks to say as soon 00:22:45.960 --> 00:22:47.810 align:start position:0% um the layer 2 networks to say as soon as<00:22:46.080> wallets<00:22:46.380> are<00:22:46.559> doing<00:22:46.679> this<00:22:46.919> they're<00:22:47.640> going 00:22:47.810 --> 00:22:47.820 align:start position:0% as wallets are doing this they're going 00:22:47.820 --> 00:22:49.549 align:start position:0% as wallets are doing this they're going to<00:22:47.940> put<00:22:48.000> it<00:22:48.120> in<00:22:48.240> like<00:22:48.539> the<00:22:48.960> nodes<00:22:49.260> have<00:22:49.440> a 00:22:49.549 --> 00:22:49.559 align:start position:0% to put it in like the nodes have a 00:22:49.559 --> 00:22:52.070 align:start position:0% to put it in like the nodes have a vested<00:22:49.799> interest<00:22:49.980> to<00:22:50.280> reduce<00:22:50.460> their<00:22:50.820> costs 00:22:52.070 --> 00:22:52.080 align:start position:0% vested interest to reduce their costs 00:22:52.080 --> 00:22:53.990 align:start position:0% vested interest to reduce their costs so<00:22:52.500> so<00:22:52.500> that<00:22:52.919> like<00:22:53.100> for<00:22:53.340> us<00:22:53.460> that's<00:22:53.640> been<00:22:53.820> a 00:22:53.990 --> 00:22:54.000 align:start position:0% so so that like for us that's been a 00:22:54.000 --> 00:22:55.610 align:start position:0% so so that like for us that's been a like<00:22:54.240> that<00:22:54.360> was<00:22:54.480> I<00:22:54.659> did<00:22:54.780> an<00:22:54.900> early<00:22:55.020> litmus<00:22:55.440> test 00:22:55.610 --> 00:22:55.620 align:start position:0% like that was I did an early litmus test 00:22:55.620 --> 00:22:57.110 align:start position:0% like that was I did an early litmus test in<00:22:55.799> a<00:22:55.919> sense<00:22:56.039> to<00:22:56.220> talk<00:22:56.400> to<00:22:56.520> them<00:22:56.640> and<00:22:57.000> they're 00:22:57.110 --> 00:22:57.120 align:start position:0% in a sense to talk to them and they're 00:22:57.120 --> 00:22:58.789 align:start position:0% in a sense to talk to them and they're like<00:22:57.240> if<00:22:57.480> this<00:22:57.720> is<00:22:57.780> in<00:22:57.960> the<00:22:58.140> wallets<00:22:58.440> we'll<00:22:58.679> put 00:22:58.789 --> 00:22:58.799 align:start position:0% like if this is in the wallets we'll put 00:22:58.799 --> 00:23:00.890 align:start position:0% like if this is in the wallets we'll put it<00:22:58.919> in<00:22:58.980> the<00:22:59.100> next<00:22:59.220> day<00:22:59.400> almost<00:22:59.880> like<00:23:00.600> that<00:23:00.720> was 00:23:00.890 --> 00:23:00.900 align:start position:0% it in the next day almost like that was 00:23:00.900 --> 00:23:03.049 align:start position:0% it in the next day almost like that was the<00:23:01.080> the<00:23:01.320> signal<00:23:01.679> I<00:23:01.799> got<00:23:01.980> from<00:23:02.159> them<00:23:02.280> but<00:23:02.760> as<00:23:02.880> it 00:23:03.049 --> 00:23:03.059 align:start position:0% the the signal I got from them but as it 00:23:03.059 --> 00:23:05.750 align:start position:0% the the signal I got from them but as it stands<00:23:03.299> this<00:23:03.419> is<00:23:03.539> one<00:23:03.720> solution<00:23:04.559> um<00:23:04.620> the<00:23:04.980> 437 00:23:05.750 --> 00:23:05.760 align:start position:0% stands this is one solution um the 437 00:23:05.760 --> 00:23:07.010 align:start position:0% stands this is one solution um the 437 solution<00:23:06.120> is<00:23:06.240> a<00:23:06.360> little<00:23:06.480> different<00:23:06.659> because<00:23:06.840> I 00:23:07.010 --> 00:23:07.020 align:start position:0% solution is a little different because I 00:23:07.020 --> 00:23:08.990 align:start position:0% solution is a little different because I think<00:23:07.140> it's<00:23:07.260> an<00:23:07.440> alternative<00:23:07.799> mempool 00:23:08.990 --> 00:23:09.000 align:start position:0% think it's an alternative mempool 00:23:09.000 --> 00:23:10.250 align:start position:0% think it's an alternative mempool um<00:23:09.059> but<00:23:09.360> yeah<00:23:09.480> you<00:23:09.659> can<00:23:09.780> maybe<00:23:09.900> check<00:23:10.140> out 00:23:10.250 --> 00:23:10.260 align:start position:0% um but yeah you can maybe check out 00:23:10.260 --> 00:23:11.390 align:start position:0% um but yeah you can maybe check out their<00:23:10.380> talk<00:23:10.559> for<00:23:10.740> more<00:23:10.860> information<00:23:10.980> on<00:23:11.280> that 00:23:11.390 --> 00:23:11.400 align:start position:0% their talk for more information on that 00:23:11.400 --> 00:23:12.890 align:start position:0% their talk for more information on that we've<00:23:11.880> got<00:23:11.880> a<00:23:12.000> couple<00:23:12.120> of<00:23:12.240> questions<00:23:12.360> over<00:23:12.600> oh 00:23:12.890 --> 00:23:12.900 align:start position:0% we've got a couple of questions over oh 00:23:12.900 --> 00:23:14.630 align:start position:0% we've got a couple of questions over oh sorry<00:23:13.140> over<00:23:13.320> here<00:23:13.500> yep 00:23:14.630 --> 00:23:14.640 align:start position:0% sorry over here yep 00:23:14.640 --> 00:23:16.730 align:start position:0% sorry over here yep hey<00:23:15.179> Jesse<00:23:15.600> from<00:23:15.720> coinbase 00:23:16.730 --> 00:23:16.740 align:start position:0% hey Jesse from coinbase 00:23:16.740 --> 00:23:18.649 align:start position:0% hey Jesse from coinbase um two<00:23:16.919> questions<00:23:17.159> one<00:23:17.640> is<00:23:17.820> if<00:23:18.240> we're 00:23:18.649 --> 00:23:18.659 align:start position:0% um two questions one is if we're 00:23:18.659 --> 00:23:21.590 align:start position:0% um two questions one is if we're exploring<00:23:19.080> kind<00:23:19.320> of<00:23:19.380> eip3<00:23:20.179> 4337<00:23:21.179> is<00:23:21.419> there 00:23:21.590 --> 00:23:21.600 align:start position:0% exploring kind of eip3 4337 is there 00:23:21.600 --> 00:23:23.029 align:start position:0% exploring kind of eip3 4337 is there anything<00:23:21.720> specific<00:23:22.260> we<00:23:22.500> should<00:23:22.679> be<00:23:22.799> keeping 00:23:23.029 --> 00:23:23.039 align:start position:0% anything specific we should be keeping 00:23:23.039 --> 00:23:25.130 align:start position:0% anything specific we should be keeping in<00:23:23.159> mind<00:23:23.280> with<00:23:23.640> BS<00:23:24.000> BLS<00:23:24.539> to<00:23:24.840> make<00:23:24.900> sure<00:23:25.020> that 00:23:25.130 --> 00:23:25.140 align:start position:0% in mind with BS BLS to make sure that 00:23:25.140 --> 00:23:26.750 align:start position:0% in mind with BS BLS to make sure that there's<00:23:25.260> like<00:23:25.440> compatibility<00:23:26.039> there<00:23:26.340> just<00:23:26.640> on 00:23:26.750 --> 00:23:26.760 align:start position:0% there's like compatibility there just on 00:23:26.760 --> 00:23:28.250 align:start position:0% there's like compatibility there just on the<00:23:26.880> coinbase<00:23:27.240> side<00:23:27.419> and<00:23:27.900> then<00:23:27.960> the<00:23:28.140> second 00:23:28.250 --> 00:23:28.260 align:start position:0% the coinbase side and then the second 00:23:28.260 --> 00:23:30.470 align:start position:0% the coinbase side and then the second question<00:23:28.440> is<00:23:28.679> how<00:23:29.100> does<00:23:29.280> the<00:23:29.480> atomicity 00:23:30.470 --> 00:23:30.480 align:start position:0% question is how does the atomicity 00:23:30.480 --> 00:23:32.570 align:start position:0% question is how does the atomicity actually<00:23:31.080> work<00:23:31.500> in<00:23:31.799> the<00:23:31.919> user<00:23:32.220> operation 00:23:32.570 --> 00:23:32.580 align:start position:0% actually work in the user operation 00:23:32.580 --> 00:23:34.310 align:start position:0% actually work in the user operation transactions<00:23:33.299> how<00:23:33.960> is<00:23:34.080> that<00:23:34.200> actually 00:23:34.310 --> 00:23:34.320 align:start position:0% transactions how is that actually 00:23:34.320 --> 00:23:36.230 align:start position:0% transactions how is that actually implemented<00:23:34.799> and<00:23:35.039> like<00:23:35.280> executed<00:23:35.820> on<00:23:36.000> the 00:23:36.230 --> 00:23:36.240 align:start position:0% implemented and like executed on the 00:23:36.240 --> 00:23:39.169 align:start position:0% implemented and like executed on the actual<00:23:36.539> uh<00:23:36.960> layer<00:23:37.260> yeah<00:23:38.400> um<00:23:38.400> I<00:23:38.640> can<00:23:38.760> cover<00:23:38.940> for 00:23:39.169 --> 00:23:39.179 align:start position:0% actual uh layer yeah um I can cover for 00:23:39.179 --> 00:23:41.090 align:start position:0% actual uh layer yeah um I can cover for the<00:23:39.240> BLS<00:23:39.659> signatures 00:23:41.090 --> 00:23:41.100 align:start position:0% the BLS signatures 00:23:41.100 --> 00:23:42.770 align:start position:0% the BLS signatures um<00:23:41.159> both<00:23:41.400> the<00:23:41.700> the<00:23:41.940> current<00:23:42.179> I<00:23:42.360> think<00:23:42.419> it's<00:23:42.539> f 00:23:42.770 --> 00:23:42.780 align:start position:0% um both the the current I think it's f 00:23:42.780 --> 00:23:45.049 align:start position:0% um both the the current I think it's f inflatanism<00:23:43.440> is<00:23:43.860> the<00:23:43.980> repo 00:23:45.049 --> 00:23:45.059 align:start position:0% inflatanism is the repo 00:23:45.059 --> 00:23:46.730 align:start position:0% inflatanism is the repo um<00:23:45.120> and<00:23:45.299> our<00:23:45.480> wallet<00:23:45.780> under<00:23:46.020> the<00:23:46.200> covers<00:23:46.500> are 00:23:46.730 --> 00:23:46.740 align:start position:0% um and our wallet under the covers are 00:23:46.740 --> 00:23:48.770 align:start position:0% um and our wallet under the covers are using<00:23:47.039> the<00:23:47.280> same<00:23:47.460> BLS<00:23:48.000> verification<00:23:48.480> and 00:23:48.770 --> 00:23:48.780 align:start position:0% using the same BLS verification and 00:23:48.780 --> 00:23:50.390 align:start position:0% using the same BLS verification and solidity<00:23:49.200> and<00:23:49.559> also<00:23:49.799> the<00:23:49.919> same<00:23:50.100> client 00:23:50.390 --> 00:23:50.400 align:start position:0% solidity and also the same client 00:23:50.400 --> 00:23:51.890 align:start position:0% solidity and also the same client libraries<00:23:50.880> so<00:23:51.120> they<00:23:51.240> should<00:23:51.419> be<00:23:51.539> largely 00:23:51.890 --> 00:23:51.900 align:start position:0% libraries so they should be largely 00:23:51.900 --> 00:23:53.270 align:start position:0% libraries so they should be largely compatible 00:23:53.270 --> 00:23:53.280 align:start position:0% compatible 00:23:53.280 --> 00:23:56.090 align:start position:0% compatible um<00:23:53.340> for<00:23:53.580> that<00:23:53.820> yeah<00:23:54.539> and<00:23:54.840> and<00:23:55.140> yeah<00:23:55.740> regarding 00:23:56.090 --> 00:23:56.100 align:start position:0% um for that yeah and and yeah regarding 00:23:56.100 --> 00:23:57.890 align:start position:0% um for that yeah and and yeah regarding the<00:23:56.280> what's<00:23:56.520> required<00:23:57.000> on<00:23:57.480> your<00:23:57.600> side<00:23:57.780> it 00:23:57.890 --> 00:23:57.900 align:start position:0% the what's required on your side it 00:23:57.900 --> 00:23:58.909 align:start position:0% the what's required on your side it would<00:23:58.020> just<00:23:58.140> be<00:23:58.200> the<00:23:58.320> signing<00:23:58.679> like<00:23:58.740> the 00:23:58.909 --> 00:23:58.919 align:start position:0% would just be the signing like the 00:23:58.919 --> 00:24:00.110 align:start position:0% would just be the signing like the client<00:23:59.100> side<00:23:59.220> would<00:23:59.460> just<00:23:59.640> need<00:23:59.760> to<00:23:59.820> sign<00:24:00.000> the 00:24:00.110 --> 00:24:00.120 align:start position:0% client side would just need to sign the 00:24:00.120 --> 00:24:03.230 align:start position:0% client side would just need to sign the BLS<00:24:00.960> um<00:24:01.020> signature<00:24:01.740> for<00:24:02.340> that<00:24:02.460> pot<00:24:02.700> and<00:24:03.059> then 00:24:03.230 --> 00:24:03.240 align:start position:0% BLS um signature for that pot and then 00:24:03.240 --> 00:24:05.270 align:start position:0% BLS um signature for that pot and then uh<00:24:04.020> depending<00:24:04.380> on<00:24:04.440> which<00:24:04.799> way<00:24:04.980> you<00:24:05.100> go 00:24:05.270 --> 00:24:05.280 align:start position:0% uh depending on which way you go 00:24:05.280 --> 00:24:07.190 align:start position:0% uh depending on which way you go directly<00:24:05.640> or<00:24:05.760> via4337<00:24:06.659> it<00:24:06.840> will<00:24:06.960> just<00:24:07.080> be 00:24:07.190 --> 00:24:07.200 align:start position:0% directly or via4337 it will just be 00:24:07.200 --> 00:24:08.690 align:start position:0% directly or via4337 it will just be interacting<00:24:07.559> with<00:24:07.799> the<00:24:07.980> contract<00:24:08.400> wallets 00:24:08.690 --> 00:24:08.700 align:start position:0% interacting with the contract wallets 00:24:08.700 --> 00:24:11.570 align:start position:0% interacting with the contract wallets that<00:24:08.880> it<00:24:09.059> deploys<00:24:09.900> uh<00:24:10.740> the<00:24:11.100> second<00:24:11.280> question 00:24:11.570 --> 00:24:11.580 align:start position:0% that it deploys uh the second question 00:24:11.580 --> 00:24:15.110 align:start position:0% that it deploys uh the second question sorry<00:24:12.059> what<00:24:12.240> was<00:24:12.360> the<00:24:12.480> second<00:24:12.600> one<00:24:12.720> again<00:24:12.900> the 00:24:15.110 --> 00:24:15.120 align:start position:0% sorry what was the second one again the 00:24:15.120 --> 00:24:17.210 align:start position:0% sorry what was the second one again the oh<00:24:15.539> yeah<00:24:15.720> sorry<00:24:16.020> that's<00:24:16.500> right<00:24:16.620> so<00:24:16.860> for<00:24:17.039> the 00:24:17.210 --> 00:24:17.220 align:start position:0% oh yeah sorry that's right so for the 00:24:17.220 --> 00:24:19.669 align:start position:0% oh yeah sorry that's right so for the multi-actions<00:24:18.000> we<00:24:18.179> have<00:24:18.299> a<00:24:18.480> set<00:24:18.659> of 00:24:19.669 --> 00:24:19.679 align:start position:0% multi-actions we have a set of 00:24:19.679 --> 00:24:22.310 align:start position:0% multi-actions we have a set of um it's<00:24:20.520> basically<00:24:20.880> uh<00:24:21.360> an<00:24:21.600> array<00:24:21.840> of<00:24:22.020> actions 00:24:22.310 --> 00:24:22.320 align:start position:0% um it's basically uh an array of actions 00:24:22.320 --> 00:24:24.470 align:start position:0% um it's basically uh an array of actions inside<00:24:22.559> a<00:24:22.799> user<00:24:23.039> operation<00:24:23.400> and<00:24:24.000> and<00:24:24.120> I<00:24:24.360> think 00:24:24.470 --> 00:24:24.480 align:start position:0% inside a user operation and and I think 00:24:24.480 --> 00:24:26.270 align:start position:0% inside a user operation and and I think 457<00:24:25.080> has<00:24:25.200> done<00:24:25.380> the<00:24:25.500> same<00:24:25.620> thing<00:24:25.740> it's<00:24:26.100> it's 00:24:26.270 --> 00:24:26.280 align:start position:0% 457 has done the same thing it's it's 00:24:26.280 --> 00:24:27.649 align:start position:0% 457 has done the same thing it's it's the<00:24:26.520> same<00:24:26.640> format 00:24:27.649 --> 00:24:27.659 align:start position:0% the same format 00:24:27.659 --> 00:24:29.690 align:start position:0% the same format um<00:24:27.720> that<00:24:27.960> you<00:24:28.080> can<00:24:28.140> specify<00:24:28.620> a<00:24:29.039> set<00:24:29.280> of<00:24:29.400> actions 00:24:29.690 --> 00:24:29.700 align:start position:0% um that you can specify a set of actions 00:24:29.700 --> 00:24:31.810 align:start position:0% um that you can specify a set of actions I<00:24:29.880> use<00:24:30.120> a<00:24:31.020> um 00:24:31.810 --> 00:24:31.820 align:start position:0% I use a um 00:24:31.820 --> 00:24:34.010 align:start position:0% I use a um uh<00:24:32.820> so 00:24:34.010 --> 00:24:34.020 align:start position:0% uh so 00:24:34.020 --> 00:24:35.870 align:start position:0% uh so yeah<00:24:34.260> it's<00:24:34.500> kind<00:24:34.799> of<00:24:34.919> a<00:24:34.980> cascaded<00:24:35.460> function<00:24:35.700> so 00:24:35.870 --> 00:24:35.880 align:start position:0% yeah it's kind of a cascaded function so 00:24:35.880 --> 00:24:37.909 align:start position:0% yeah it's kind of a cascaded function so that<00:24:36.000> I<00:24:36.120> can<00:24:36.179> call<00:24:36.299> it<00:24:36.480> a<00:24:36.659> try<00:24:36.840> on<00:24:37.500> one<00:24:37.679> of<00:24:37.799> them 00:24:37.909 --> 00:24:37.919 align:start position:0% that I can call it a try on one of them 00:24:37.919 --> 00:24:40.370 align:start position:0% that I can call it a try on one of them and<00:24:38.340> so<00:24:38.520> if<00:24:38.760> one<00:24:39.000> of<00:24:39.120> the<00:24:39.179> actions<00:24:39.539> fails<00:24:39.900> then 00:24:40.370 --> 00:24:40.380 align:start position:0% and so if one of the actions fails then 00:24:40.380 --> 00:24:42.289 align:start position:0% and so if one of the actions fails then it<00:24:40.559> reverts<00:24:41.100> and<00:24:41.580> then<00:24:41.700> so<00:24:41.880> all<00:24:42.059> of<00:24:42.179> them 00:24:42.289 --> 00:24:42.299 align:start position:0% it reverts and then so all of them 00:24:42.299 --> 00:24:45.049 align:start position:0% it reverts and then so all of them revert<00:24:42.659> within<00:24:43.020> that<00:24:43.260> try<00:24:44.100> and<00:24:44.580> then<00:24:44.700> I<00:24:44.820> catch 00:24:45.049 --> 00:24:45.059 align:start position:0% revert within that try and then I catch 00:24:45.059 --> 00:24:46.130 align:start position:0% revert within that try and then I catch and<00:24:45.120> then<00:24:45.240> I<00:24:45.360> go<00:24:45.419> on<00:24:45.539> to<00:24:45.659> the<00:24:45.720> next<00:24:45.840> user 00:24:46.130 --> 00:24:46.140 align:start position:0% and then I go on to the next user 00:24:46.140 --> 00:24:48.110 align:start position:0% and then I go on to the next user operation<00:24:46.440> so<00:24:46.919> each<00:24:47.100> user<00:24:47.400> operation<00:24:47.700> is<00:24:47.880> in<00:24:48.000> a 00:24:48.110 --> 00:24:48.120 align:start position:0% operation so each user operation is in a 00:24:48.120 --> 00:24:50.690 align:start position:0% operation so each user operation is in a loop<00:24:48.360> and<00:24:49.140> within<00:24:49.799> there<00:24:49.980> it<00:24:50.159> calls<00:24:50.460> the<00:24:50.580> set 00:24:50.690 --> 00:24:50.700 align:start position:0% loop and within there it calls the set 00:24:50.700 --> 00:24:52.610 align:start position:0% loop and within there it calls the set of<00:24:50.880> actions<00:24:51.179> to<00:24:51.360> the<00:24:51.539> wallet<00:24:51.840> and<00:24:52.200> if<00:24:52.320> one<00:24:52.500> of 00:24:52.610 --> 00:24:52.620 align:start position:0% of actions to the wallet and if one of 00:24:52.620 --> 00:24:53.990 align:start position:0% of actions to the wallet and if one of the<00:24:52.679> actions<00:24:52.980> fails<00:24:53.280> only<00:24:53.520> the<00:24:53.760> user 00:24:53.990 --> 00:24:54.000 align:start position:0% the actions fails only the user 00:24:54.000 --> 00:24:55.730 align:start position:0% the actions fails only the user operation<00:24:54.299> is<00:24:54.480> reverted<00:24:54.900> not<00:24:55.200> the<00:24:55.380> rest<00:24:55.500> of<00:24:55.620> it 00:24:55.730 --> 00:24:55.740 align:start position:0% operation is reverted not the rest of it 00:24:55.740 --> 00:24:57.590 align:start position:0% operation is reverted not the rest of it because<00:24:55.919> of<00:24:56.159> the<00:24:56.340> try<00:24:56.460> catch<00:24:56.880> which<00:24:57.299> was<00:24:57.419> nice 00:24:57.590 --> 00:24:57.600 align:start position:0% because of the try catch which was nice 00:24:57.600 --> 00:24:59.930 align:start position:0% because of the try catch which was nice the<00:24:57.840> facility<00:24:58.140> has<00:24:58.500> that<00:24:58.620> now 00:24:59.930 --> 00:24:59.940 align:start position:0% the facility has that now 00:24:59.940 --> 00:25:01.730 align:start position:0% the facility has that now yep 00:25:01.730 --> 00:25:01.740 align:start position:0% yep 00:25:01.740 --> 00:25:03.470 align:start position:0% yep um<00:25:01.799> who<00:25:02.100> do<00:25:02.159> you<00:25:02.280> anticipate<00:25:02.640> running<00:25:02.940> these 00:25:03.470 --> 00:25:03.480 align:start position:0% um who do you anticipate running these 00:25:03.480 --> 00:25:05.149 align:start position:0% um who do you anticipate running these aggregated<00:25:03.900> proxies 00:25:05.149 --> 00:25:05.159 align:start position:0% aggregated proxies 00:25:05.159 --> 00:25:07.130 align:start position:0% aggregated proxies we<00:25:05.760> hope<00:25:05.880> that<00:25:06.000> they<00:25:06.179> get<00:25:06.299> merged<00:25:06.720> into<00:25:06.900> the 00:25:07.130 --> 00:25:07.140 align:start position:0% we hope that they get merged into the 00:25:07.140 --> 00:25:09.110 align:start position:0% we hope that they get merged into the nodes<00:25:07.320> into<00:25:07.679> their<00:25:07.919> later<00:25:08.100> nodes<00:25:08.520> yeah<00:25:08.880> to 00:25:09.110 --> 00:25:09.120 align:start position:0% nodes into their later nodes yeah to 00:25:09.120 --> 00:25:10.850 align:start position:0% nodes into their later nodes yeah to start<00:25:09.480> out<00:25:10.020> um<00:25:10.080> we<00:25:10.200> would<00:25:10.380> expect<00:25:10.500> like<00:25:10.679> the 00:25:10.850 --> 00:25:10.860 align:start position:0% start out um we would expect like the 00:25:10.860 --> 00:25:12.409 align:start position:0% start out um we would expect like the app<00:25:11.039> would<00:25:11.220> probably<00:25:11.340> run<00:25:11.520> its<00:25:11.880> own<00:25:11.940> aggregate 00:25:12.409 --> 00:25:12.419 align:start position:0% app would probably run its own aggregate 00:25:12.419 --> 00:25:14.270 align:start position:0% app would probably run its own aggregate proxy<00:25:12.900> just<00:25:13.140> to<00:25:13.320> kind<00:25:13.440> of<00:25:13.500> like<00:25:13.620> bootstrap<00:25:14.100> the 00:25:14.270 --> 00:25:14.280 align:start position:0% proxy just to kind of like bootstrap the 00:25:14.280 --> 00:25:16.310 align:start position:0% proxy just to kind of like bootstrap the process<00:25:14.520> eventually 00:25:16.310 --> 00:25:16.320 align:start position:0% process eventually 00:25:16.320 --> 00:25:19.130 align:start position:0% process eventually um<00:25:16.380> it<00:25:16.740> could<00:25:16.860> potentially<00:25:17.220> be<00:25:17.580> like<00:25:18.059> uh<00:25:18.600> a 00:25:19.130 --> 00:25:19.140 align:start position:0% um it could potentially be like uh a 00:25:19.140 --> 00:25:21.110 align:start position:0% um it could potentially be like uh a larger<00:25:19.500> swath<00:25:19.860> of<00:25:20.039> say<00:25:20.220> like<00:25:20.460> nodes<00:25:20.880> having 00:25:21.110 --> 00:25:21.120 align:start position:0% larger swath of say like nodes having 00:25:21.120 --> 00:25:22.970 align:start position:0% larger swath of say like nodes having compatibility<00:25:21.659> with<00:25:21.840> that<00:25:21.960> we<00:25:22.620> also<00:25:22.799> think 00:25:22.970 --> 00:25:22.980 align:start position:0% compatibility with that we also think 00:25:22.980 --> 00:25:24.830 align:start position:0% compatibility with that we also think that<00:25:23.580> um<00:25:23.580> if<00:25:23.880> we're<00:25:23.940> able<00:25:24.299> to<00:25:24.480> kind<00:25:24.600> of<00:25:24.659> move 00:25:24.830 --> 00:25:24.840 align:start position:0% that um if we're able to kind of move 00:25:24.840 --> 00:25:26.630 align:start position:0% that um if we're able to kind of move more<00:25:25.140> towards<00:25:25.440> that<00:25:25.559> like<00:25:25.799> contract<00:25:26.279> funding 00:25:26.630 --> 00:25:26.640 align:start position:0% more towards that like contract funding 00:25:26.640 --> 00:25:28.610 align:start position:0% more towards that like contract funding for<00:25:26.880> the<00:25:27.000> gas<00:25:27.179> that<00:25:27.840> will<00:25:27.960> make<00:25:28.080> it<00:25:28.200> so<00:25:28.320> it<00:25:28.500> does 00:25:28.610 --> 00:25:28.620 align:start position:0% for the gas that will make it so it does 00:25:28.620 --> 00:25:30.710 align:start position:0% for the gas that will make it so it does not<00:25:28.740> matter<00:25:29.039> kind<00:25:29.580> of<00:25:29.700> where<00:25:30.059> you<00:25:30.240> submit<00:25:30.600> it 00:25:30.710 --> 00:25:30.720 align:start position:0% not matter kind of where you submit it 00:25:30.720 --> 00:25:33.529 align:start position:0% not matter kind of where you submit it when<00:25:31.200> it<00:25:31.380> eventually<00:25:31.620> is<00:25:31.860> executed<00:25:32.340> on<00:25:32.640> chain 00:25:33.529 --> 00:25:33.539 align:start position:0% when it eventually is executed on chain 00:25:33.539 --> 00:25:34.850 align:start position:0% when it eventually is executed on chain um<00:25:33.600> that's<00:25:33.840> when<00:25:34.020> the<00:25:34.200> actual<00:25:34.440> like<00:25:34.679> payment 00:25:34.850 --> 00:25:34.860 align:start position:0% um that's when the actual like payment 00:25:34.860 --> 00:25:36.950 align:start position:0% um that's when the actual like payment subsidation<00:25:35.580> will<00:25:35.760> happen<00:25:35.940> and<00:25:36.539> so<00:25:36.659> then<00:25:36.779> it's 00:25:36.950 --> 00:25:36.960 align:start position:0% subsidation will happen and so then it's 00:25:36.960 --> 00:25:38.630 align:start position:0% subsidation will happen and so then it's less<00:25:37.200> important<00:25:37.620> but<00:25:37.799> just<00:25:38.100> to<00:25:38.279> start<00:25:38.460> out 00:25:38.630 --> 00:25:38.640 align:start position:0% less important but just to start out 00:25:38.640 --> 00:25:40.610 align:start position:0% less important but just to start out we're<00:25:39.299> having<00:25:39.600> that<00:25:39.900> kind<00:25:40.080> of<00:25:40.200> more<00:25:40.320> like 00:25:40.610 --> 00:25:40.620 align:start position:0% we're having that kind of more like 00:25:40.620 --> 00:25:42.230 align:start position:0% we're having that kind of more like centralized<00:25:41.220> service<00:25:41.460> just<00:25:41.820> kind<00:25:42.059> of<00:25:42.120> get 00:25:42.230 --> 00:25:42.240 align:start position:0% centralized service just kind of get 00:25:42.240 --> 00:25:43.310 align:start position:0% centralized service just kind of get things<00:25:42.360> going 00:25:43.310 --> 00:25:43.320 align:start position:0% things going 00:25:43.320 --> 00:25:45.350 align:start position:0% things going thanks<00:25:43.860> for<00:25:44.100> this<00:25:44.279> presentation<00:25:44.820> appreciate 00:25:45.350 --> 00:25:45.360 align:start position:0% thanks for this presentation appreciate 00:25:45.360 --> 00:25:46.010 align:start position:0% thanks for this presentation appreciate it 00:25:46.010 --> 00:25:46.020 align:start position:0% it 00:25:46.020 --> 00:25:49.250 align:start position:0% it does<00:25:46.799> quilt<00:25:47.279> have<00:25:47.940> any<00:25:48.179> sort<00:25:48.360> of<00:25:48.480> priority<00:25:48.840> on 00:25:49.250 --> 00:25:49.260 align:start position:0% does quilt have any sort of priority on 00:25:49.260 --> 00:25:53.269 align:start position:0% does quilt have any sort of priority on test<00:25:50.220> automation<00:25:50.760> for<00:25:51.120> end-to-end<00:25:51.720> testing 00:25:53.269 --> 00:25:53.279 align:start position:0% test automation for end-to-end testing 00:25:53.279 --> 00:25:55.730 align:start position:0% test automation for end-to-end testing um<00:25:53.400> you<00:25:53.640> know<00:25:53.700> usability<00:25:54.179> testing<00:25:54.779> seems<00:25:55.620> like 00:25:55.730 --> 00:25:55.740 align:start position:0% um you know usability testing seems like 00:25:55.740 --> 00:25:58.250 align:start position:0% um you know usability testing seems like wallets<00:25:56.700> right<00:25:57.179> now<00:25:57.360> don't<00:25:57.539> pay<00:25:57.779> very<00:25:58.080> much 00:25:58.250 --> 00:25:58.260 align:start position:0% wallets right now don't pay very much 00:25:58.260 --> 00:25:59.630 align:start position:0% wallets right now don't pay very much attention 00:25:59.630 --> 00:25:59.640 align:start position:0% attention 00:25:59.640 --> 00:26:01.970 align:start position:0% attention to<00:25:59.880> the<00:26:00.059> user<00:26:00.419> experience<00:26:00.600> yeah<00:26:01.200> because<00:26:01.559> what 00:26:01.970 --> 00:26:01.980 align:start position:0% to the user experience yeah because what 00:26:01.980 --> 00:26:03.409 align:start position:0% to the user experience yeah because what are<00:26:02.100> users<00:26:02.279> seeing<00:26:02.640> what<00:26:02.760> are<00:26:02.940> they<00:26:03.059> clicking 00:26:03.409 --> 00:26:03.419 align:start position:0% are users seeing what are they clicking 00:26:03.419 --> 00:26:04.370 align:start position:0% are users seeing what are they clicking on 00:26:04.370 --> 00:26:04.380 align:start position:0% on 00:26:04.380 --> 00:26:05.870 align:start position:0% on yeah<00:26:04.620> no<00:26:04.980> definitely<00:26:05.340> that's<00:26:05.520> a<00:26:05.640> very<00:26:05.760> good 00:26:05.870 --> 00:26:05.880 align:start position:0% yeah no definitely that's a very good 00:26:05.880 --> 00:26:08.390 align:start position:0% yeah no definitely that's a very good question<00:26:06.059> so<00:26:06.720> firstly<00:26:07.260> the<00:26:07.500> quill<00:26:07.799> isn't<00:26:08.400> um 00:26:08.390 --> 00:26:08.400 align:start position:0% question so firstly the quill isn't um 00:26:08.400 --> 00:26:09.769 align:start position:0% question so firstly the quill isn't um we<00:26:08.640> don't<00:26:08.760> want<00:26:08.880> to<00:26:09.000> release<00:26:09.120> Quail<00:26:09.539> as<00:26:09.659> a 00:26:09.769 --> 00:26:09.779 align:start position:0% we don't want to release Quail as a 00:26:09.779 --> 00:26:11.269 align:start position:0% we don't want to release Quail as a wallet<00:26:10.020> it's<00:26:10.260> meant<00:26:10.559> to<00:26:10.620> be<00:26:10.740> like<00:26:10.860> a<00:26:11.039> reference 00:26:11.269 --> 00:26:11.279 align:start position:0% wallet it's meant to be like a reference 00:26:11.279 --> 00:26:13.370 align:start position:0% wallet it's meant to be like a reference implementation<00:26:11.880> to<00:26:12.299> show<00:26:12.480> how<00:26:12.779> other<00:26:13.020> wallets 00:26:13.370 --> 00:26:13.380 align:start position:0% implementation to show how other wallets 00:26:13.380 --> 00:26:15.590 align:start position:0% implementation to show how other wallets can<00:26:13.559> integrate<00:26:13.860> the<00:26:13.980> client<00:26:14.360> we<00:26:15.360> had 00:26:15.590 --> 00:26:15.600 align:start position:0% can integrate the client we had 00:26:15.600 --> 00:26:17.870 align:start position:0% can integrate the client we had considered<00:26:16.080> spending<00:26:16.380> more<00:26:16.559> effort<00:26:16.919> making 00:26:17.870 --> 00:26:17.880 align:start position:0% considered spending more effort making 00:26:17.880 --> 00:26:19.909 align:start position:0% considered spending more effort making the<00:26:18.179> UI<00:26:18.480> match<00:26:18.720> the<00:26:19.020> designs<00:26:19.440> that<00:26:19.620> have<00:26:19.799> come 00:26:19.909 --> 00:26:19.919 align:start position:0% the UI match the designs that have come 00:26:19.919 --> 00:26:21.470 align:start position:0% the UI match the designs that have come about<00:26:20.039> so<00:26:20.400> the<00:26:20.520> designs<00:26:20.820> we<00:26:20.940> have<00:26:21.059> over<00:26:21.240> there 00:26:21.470 --> 00:26:21.480 align:start position:0% about so the designs we have over there 00:26:21.480 --> 00:26:23.630 align:start position:0% about so the designs we have over there so<00:26:21.600> if<00:26:21.720> you<00:26:21.840> go<00:26:21.960> to<00:26:22.080> our<00:26:22.260> Discord<00:26:23.159> I<00:26:23.400> think<00:26:23.520> in 00:26:23.630 --> 00:26:23.640 align:start position:0% so if you go to our Discord I think in 00:26:23.640 --> 00:26:25.370 align:start position:0% so if you go to our Discord I think in in<00:26:23.820> The<00:26:24.000> Design<00:26:24.120> Channel<00:26:24.419> we<00:26:24.779> have<00:26:24.900> a<00:26:25.020> link<00:26:25.140> to 00:26:25.370 --> 00:26:25.380 align:start position:0% in The Design Channel we have a link to 00:26:25.380 --> 00:26:27.710 align:start position:0% in The Design Channel we have a link to the<00:26:25.679> design<00:26:26.100> brief<00:26:26.820> that<00:26:27.000> was<00:26:27.120> done<00:26:27.299> or<00:26:27.539> does 00:26:27.710 --> 00:26:27.720 align:start position:0% the design brief that was done or does 00:26:27.720 --> 00:26:29.870 align:start position:0% the design brief that was done or does it<00:26:28.260> I<00:26:28.559> forget<00:26:28.620> what<00:26:28.860> we<00:26:28.860> call<00:26:29.100> it<00:26:29.159> as<00:26:29.279> a<00:26:29.760> whole 00:26:29.870 --> 00:26:29.880 align:start position:0% it I forget what we call it as a whole 00:26:29.880 --> 00:26:31.610 align:start position:0% it I forget what we call it as a whole but<00:26:30.059> there's<00:26:30.659> just<00:26:30.840> been<00:26:30.960> a<00:26:31.140> large<00:26:31.380> design 00:26:31.610 --> 00:26:31.620 align:start position:0% but there's just been a large design 00:26:31.620 --> 00:26:33.409 align:start position:0% but there's just been a large design process<00:26:32.039> done<00:26:32.279> to<00:26:32.460> look<00:26:32.640> at<00:26:32.760> what<00:26:32.940> wallets<00:26:33.299> of 00:26:33.409 --> 00:26:33.419 align:start position:0% process done to look at what wallets of 00:26:33.419 --> 00:26:34.870 align:start position:0% process done to look at what wallets of the<00:26:33.539> future<00:26:33.600> can<00:26:33.840> look<00:26:33.960> like<00:26:34.080> multi-chain 00:26:34.870 --> 00:26:34.880 align:start position:0% the future can look like multi-chain 00:26:34.880 --> 00:26:36.830 align:start position:0% the future can look like multi-chain multi-wallet<00:26:35.880> and<00:26:36.179> all<00:26:36.240> of<00:26:36.360> that<00:26:36.480> being<00:26:36.600> very 00:26:36.830 --> 00:26:36.840 align:start position:0% multi-wallet and all of that being very 00:26:36.840 --> 00:26:38.750 align:start position:0% multi-wallet and all of that being very usable<00:26:37.260> so<00:26:37.740> we've<00:26:37.919> done<00:26:38.100> that<00:26:38.159> as<00:26:38.340> more<00:26:38.520> of<00:26:38.640> an 00:26:38.750 --> 00:26:38.760 align:start position:0% usable so we've done that as more of an 00:26:38.760 --> 00:26:40.250 align:start position:0% usable so we've done that as more of an exercise<00:26:38.880> to<00:26:39.179> say<00:26:39.299> this<00:26:39.539> is<00:26:39.600> what<00:26:39.720> wallets<00:26:40.020> can 00:26:40.250 --> 00:26:40.260 align:start position:0% exercise to say this is what wallets can 00:26:40.260 --> 00:26:42.529 align:start position:0% exercise to say this is what wallets can do<00:26:40.440> but<00:26:40.799> again<00:26:40.980> we<00:26:41.580> had<00:26:41.940> considered<00:26:42.299> putting 00:26:42.529 --> 00:26:42.539 align:start position:0% do but again we had considered putting 00:26:42.539 --> 00:26:43.850 align:start position:0% do but again we had considered putting that<00:26:42.600> into<00:26:42.779> quill<00:26:43.080> but<00:26:43.380> because<00:26:43.559> we<00:26:43.799> don't 00:26:43.850 --> 00:26:43.860 align:start position:0% that into quill but because we don't 00:26:43.860 --> 00:26:45.169 align:start position:0% that into quill but because we don't want<00:26:44.039> to<00:26:44.159> necessarily<00:26:44.580> launch<00:26:44.700> it<00:26:44.880> we<00:26:45.059> leave 00:26:45.169 --> 00:26:45.179 align:start position:0% want to necessarily launch it we leave 00:26:45.179 --> 00:26:46.549 align:start position:0% want to necessarily launch it we leave them<00:26:45.360> there<00:26:45.539> as<00:26:45.659> reference<00:26:45.960> implementations 00:26:46.549 --> 00:26:46.559 align:start position:0% them there as reference implementations 00:26:46.559 --> 00:26:48.409 align:start position:0% them there as reference implementations quill<00:26:47.220> being<00:26:47.460> the<00:26:47.580> technical<00:26:47.820> one<00:26:48.059> and<00:26:48.299> the 00:26:48.409 --> 00:26:48.419 align:start position:0% quill being the technical one and the 00:26:48.419 --> 00:26:50.390 align:start position:0% quill being the technical one and the design<00:26:48.600> being<00:26:49.440> for<00:26:49.620> other<00:26:49.740> wallets<00:26:50.100> to<00:26:50.279> learn 00:26:50.390 --> 00:26:50.400 align:start position:0% design being for other wallets to learn 00:26:50.400 --> 00:26:52.490 align:start position:0% design being for other wallets to learn from<00:26:50.580> if<00:26:50.880> if<00:26:51.059> that's<00:26:51.240> a<00:26:51.419> value<00:26:51.600> so<00:26:52.260> there<00:26:52.380> was 00:26:52.490 --> 00:26:52.500 align:start position:0% from if if that's a value so there was 00:26:52.500 --> 00:26:53.690 align:start position:0% from if if that's a value so there was some<00:26:52.620> user<00:26:52.860> research<00:26:53.100> done<00:26:53.279> with<00:26:53.400> that<00:26:53.520> as 00:26:53.690 --> 00:26:53.700 align:start position:0% some user research done with that as 00:26:53.700 --> 00:26:55.789 align:start position:0% some user research done with that as well<00:26:53.820> and<00:26:54.059> yeah 00:26:55.789 --> 00:26:55.799 align:start position:0% well and yeah 00:26:55.799 --> 00:26:57.470 align:start position:0% well and yeah I<00:26:56.640> think<00:26:56.760> we<00:26:56.880> still<00:26:57.000> have<00:26:57.120> some<00:26:57.240> time<00:26:57.360> for 00:26:57.470 --> 00:26:57.480 align:start position:0% I think we still have some time for 00:26:57.480 --> 00:26:59.029 align:start position:0% I think we still have some time for questions<00:26:57.600> we've<00:26:57.900> got<00:26:57.960> another 00:26:59.029 --> 00:26:59.039 align:start position:0% questions we've got another 00:26:59.039 --> 00:27:01.970 align:start position:0% questions we've got another yep<00:26:59.520> we<00:26:59.700> go<00:26:59.820> question<00:27:00.120> up<00:27:00.360> the<00:27:00.600> front 00:27:01.970 --> 00:27:01.980 align:start position:0% yep we go question up the front 00:27:01.980 --> 00:27:04.130 align:start position:0% yep we go question up the front thank<00:27:02.460> you<00:27:02.580> so<00:27:02.700> much<00:27:02.820> this<00:27:03.059> is<00:27:03.179> amazing 00:27:04.130 --> 00:27:04.140 align:start position:0% thank you so much this is amazing 00:27:04.140 --> 00:27:07.549 align:start position:0% thank you so much this is amazing um<00:27:04.460> I'm<00:27:05.460> just<00:27:05.640> learning<00:27:05.940> about<00:27:06.059> BLS<00:27:06.600> so<00:27:07.020> don't 00:27:07.549 --> 00:27:07.559 align:start position:0% um I'm just learning about BLS so don't 00:27:07.559 --> 00:27:09.529 align:start position:0% um I'm just learning about BLS so don't mind<00:27:07.740> if<00:27:07.860> my<00:27:08.039> question<00:27:08.159> is<00:27:08.279> too<00:27:08.460> naive<00:27:08.760> but 00:27:09.529 --> 00:27:09.539 align:start position:0% mind if my question is too naive but 00:27:09.539 --> 00:27:12.409 align:start position:0% mind if my question is too naive but with<00:27:09.900> developments<00:27:10.799> like<00:27:11.039> ZK<00:27:11.520> evm<00:27:12.000> on<00:27:12.120> layer 00:27:12.409 --> 00:27:12.419 align:start position:0% with developments like ZK evm on layer 00:27:12.419 --> 00:27:13.789 align:start position:0% with developments like ZK evm on layer twos 00:27:13.789 --> 00:27:13.799 align:start position:0% twos 00:27:13.799 --> 00:27:15.950 align:start position:0% twos um<00:27:13.860> for<00:27:14.220> Signature<00:27:14.640> aggregations<00:27:15.120> uh<00:27:15.779> and 00:27:15.950 --> 00:27:15.960 align:start position:0% um for Signature aggregations uh and 00:27:15.960 --> 00:27:18.470 align:start position:0% um for Signature aggregations uh and atomicity<00:27:16.500> like<00:27:16.679> I<00:27:16.860> can<00:27:16.980> basically<00:27:17.340> do<00:27:18.240> like 00:27:18.470 --> 00:27:18.480 align:start position:0% atomicity like I can basically do like 00:27:18.480 --> 00:27:19.850 align:start position:0% atomicity like I can basically do like as<00:27:18.600> you<00:27:18.720> showed<00:27:18.960> like<00:27:19.080> approve<00:27:19.559> and<00:27:19.679> then 00:27:19.850 --> 00:27:19.860 align:start position:0% as you showed like approve and then 00:27:19.860 --> 00:27:22.070 align:start position:0% as you showed like approve and then transfer<00:27:20.340> like<00:27:20.640> bunch<00:27:20.880> of<00:27:21.000> things<00:27:21.179> what<00:27:21.900> do 00:27:22.070 --> 00:27:22.080 align:start position:0% transfer like bunch of things what do 00:27:22.080 --> 00:27:24.409 align:start position:0% transfer like bunch of things what do you<00:27:22.140> think<00:27:22.260> about<00:27:22.380> like<00:27:22.620> recursive<00:27:23.159> proofs<00:27:23.520> uh 00:27:24.409 --> 00:27:24.419 align:start position:0% you think about like recursive proofs uh 00:27:24.419 --> 00:27:26.269 align:start position:0% you think about like recursive proofs uh so<00:27:24.600> if<00:27:24.779> I've<00:27:24.960> I<00:27:25.380> I<00:27:25.559> have<00:27:25.860> like<00:27:25.980> multiple 00:27:26.269 --> 00:27:26.279 align:start position:0% so if I've I I have like multiple 00:27:26.279 --> 00:27:28.789 align:start position:0% so if I've I I have like multiple transactions<00:27:26.940> I<00:27:27.299> have<00:27:27.419> each<00:27:27.659> proof<00:27:28.080> and<00:27:28.440> I 00:27:28.789 --> 00:27:28.799 align:start position:0% transactions I have each proof and I 00:27:28.799 --> 00:27:30.590 align:start position:0% transactions I have each proof and I take<00:27:29.039> them<00:27:29.279> and<00:27:29.580> just<00:27:29.760> submit<00:27:30.120> recursive 00:27:30.590 --> 00:27:30.600 align:start position:0% take them and just submit recursive 00:27:30.600 --> 00:27:33.769 align:start position:0% take them and just submit recursive proofs<00:27:30.900> so<00:27:31.860> in<00:27:32.220> that<00:27:32.340> case<00:27:32.520> how<00:27:33.179> like<00:27:33.419> how<00:27:33.659> do 00:27:33.769 --> 00:27:33.779 align:start position:0% proofs so in that case how like how do 00:27:33.779 --> 00:27:36.649 align:start position:0% proofs so in that case how like how do we<00:27:33.900> think<00:27:34.080> about<00:27:34.760> developments<00:27:35.760> in<00:27:35.880> ZK<00:27:36.240> evm 00:27:36.649 --> 00:27:36.659 align:start position:0% we think about developments in ZK evm 00:27:36.659 --> 00:27:40.430 align:start position:0% we think about developments in ZK evm and<00:27:36.960> BLS<00:27:37.679> going<00:27:38.279> to<00:27:38.400> get<00:27:38.520> I'm<00:27:39.059> going<00:27:39.179> to<00:27:39.360> yeah<00:27:40.200> I 00:27:40.430 --> 00:27:40.440 align:start position:0% and BLS going to get I'm going to yeah I 00:27:40.440 --> 00:27:41.990 align:start position:0% and BLS going to get I'm going to yeah I think<00:27:40.860> um<00:27:40.860> and<00:27:41.039> you<00:27:41.159> might<00:27:41.340> have<00:27:41.580> some 00:27:41.990 --> 00:27:42.000 align:start position:0% think um and you might have some 00:27:42.000 --> 00:27:43.370 align:start position:0% think um and you might have some fastness<00:27:42.360> two<00:27:42.600> James 00:27:43.370 --> 00:27:43.380 align:start position:0% fastness two James 00:27:43.380 --> 00:27:45.289 align:start position:0% fastness two James um<00:27:43.440> I<00:27:43.559> think<00:27:43.740> we<00:27:44.580> haven't<00:27:44.700> really<00:27:45.000> fully 00:27:45.289 --> 00:27:45.299 align:start position:0% um I think we haven't really fully 00:27:45.299 --> 00:27:46.789 align:start position:0% um I think we haven't really fully looked<00:27:45.600> into<00:27:45.779> what<00:27:46.140> it's<00:27:46.320> going<00:27:46.440> to<00:27:46.500> look<00:27:46.620> like 00:27:46.789 --> 00:27:46.799 align:start position:0% looked into what it's going to look like 00:27:46.799 --> 00:27:49.430 align:start position:0% looked into what it's going to look like but<00:27:47.159> we<00:27:47.340> think<00:27:47.880> um<00:27:47.940> this<00:27:48.419> wallet<00:27:48.900> PLS<00:27:49.320> wall 00:27:49.430 --> 00:27:49.440 align:start position:0% but we think um this wallet PLS wall 00:27:49.440 --> 00:27:51.529 align:start position:0% but we think um this wallet PLS wall ecosystem<00:27:49.860> would<00:27:50.580> work<00:27:50.760> in<00:27:50.940> any<00:27:51.059> evm 00:27:51.529 --> 00:27:51.539 align:start position:0% ecosystem would work in any evm 00:27:51.539 --> 00:27:54.470 align:start position:0% ecosystem would work in any evm compatible<00:27:52.020> system<00:27:52.320> and<00:27:53.159> so<00:27:53.340> we<00:27:54.000> might<00:27:54.299> be 00:27:54.470 --> 00:27:54.480 align:start position:0% compatible system and so we might be 00:27:54.480 --> 00:27:55.970 align:start position:0% compatible system and so we might be able<00:27:54.600> to<00:27:54.720> even<00:27:54.840> reduce<00:27:55.140> some<00:27:55.500> of<00:27:55.559> the<00:27:55.679> data 00:27:55.970 --> 00:27:55.980 align:start position:0% able to even reduce some of the data 00:27:55.980 --> 00:27:57.769 align:start position:0% able to even reduce some of the data that<00:27:56.100> needs<00:27:56.340> to<00:27:56.400> be<00:27:56.520> proved<00:27:56.880> or<00:27:57.000> run<00:27:57.179> over<00:27:57.360> in 00:27:57.769 --> 00:27:57.779 align:start position:0% that needs to be proved or run over in 00:27:57.779 --> 00:28:00.350 align:start position:0% that needs to be proved or run over in those<00:27:57.900> eke<00:27:58.320> evm<00:27:58.679> setups<00:27:59.159> but<00:27:59.760> I<00:27:59.940> we<00:28:00.179> haven't 00:28:00.350 --> 00:28:00.360 align:start position:0% those eke evm setups but I we haven't 00:28:00.360 --> 00:28:03.350 align:start position:0% those eke evm setups but I we haven't done<00:28:00.720> a<00:28:00.900> ton<00:28:01.020> of<00:28:01.140> experimentation<00:28:01.679> yet 00:28:03.350 --> 00:28:03.360 align:start position:0% done a ton of experimentation yet 00:28:03.360 --> 00:28:05.630 align:start position:0% done a ton of experimentation yet but<00:28:04.080> there<00:28:04.500> is<00:28:04.679> the<00:28:04.980> possibility<00:28:05.220> that<00:28:05.460> it 00:28:05.630 --> 00:28:05.640 align:start position:0% but there is the possibility that it 00:28:05.640 --> 00:28:07.610 align:start position:0% but there is the possibility that it will<00:28:05.820> help 00:28:07.610 --> 00:28:07.620 align:start position:0% will help 00:28:07.620 --> 00:28:09.649 align:start position:0% will help at<00:28:07.919> South<00:28:08.100> China<00:28:08.340> that's<00:28:08.700> our<00:28:08.820> time<00:28:09.000> thank<00:28:09.539> you 00:28:09.649 --> 00:28:09.659 align:start position:0% at South China that's our time thank you 00:28:09.659 --> 00:28:10.690 align:start position:0% at South China that's our time thank you thanks<00:28:09.960> everyone 00:28:10.690 --> 00:28:10.700 align:start position:0% thanks everyone 00:28:10.700 --> 00:28:12.560 align:start position:0% thanks everyone [Applause] 00:28:12.560 --> 00:28:12.570 align:start position:0% [Applause] 00:28:12.570 --> 00:28:13.490 align:start position:0% [Applause] [Music] 00:28:13.490 --> 00:28:13.500 align:start position:0% [Music] 00:28:13.500 --> 00:28:18.409 align:start position:0% [Music] [Applause] 00:28:18.409 --> 00:28:18.419 align:start position:0% 00:28:18.419 --> 00:28:19.970 align:start position:0% all<00:28:18.779> right<00:28:18.960> thank<00:28:19.200> you<00:28:19.320> so<00:28:19.440> much<00:28:19.559> for<00:28:19.799> that 00:28:19.970 --> 00:28:19.980 align:start position:0% all right thank you so much for that 00:28:19.980 --> 00:28:23.630 align:start position:0% all right thank you so much for that next<00:28:20.820> up<00:28:21.120> is<00:28:21.539> a<00:28:21.659> talk<00:28:21.779> by<00:28:22.020> Patrick<00:28:22.340> who<00:28:23.340> claims 00:28:23.630 --> 00:28:23.640 align:start position:0% next up is a talk by Patrick who claims 00:28:23.640 --> 00:28:26.930 align:start position:0% next up is a talk by Patrick who claims to<00:28:23.760> be<00:28:23.940> an<00:28:24.539> intern<00:28:24.779> at<00:28:25.200> infuria<00:28:25.919> and<00:28:26.700> in<00:28:26.820> the 00:28:26.930 --> 00:28:26.940 align:start position:0% to be an intern at infuria and in the 00:28:26.940 --> 00:28:29.510 align:start position:0% to be an intern at infuria and in the past<00:28:27.059> has<00:28:27.360> been<00:28:27.539> an<00:28:27.779> assistant<00:28:27.960> professor<00:28:28.799> at 00:28:29.510 --> 00:28:29.520 align:start position:0% past has been an assistant professor at 00:28:29.520 --> 00:28:31.610 align:start position:0% past has been an assistant professor at many<00:28:29.700> universities<00:28:30.240> uh<00:28:31.200> please<00:28:31.440> welcome 00:28:31.610 --> 00:28:31.620 align:start position:0% many universities uh please welcome 00:28:31.620 --> 00:28:33.470 align:start position:0% many universities uh please welcome Patrick<00:28:31.980> for<00:28:32.340> his<00:28:32.460> talk<00:28:32.640> on<00:28:32.880> validating 00:28:33.470 --> 00:28:33.480 align:start position:0% Patrick for his talk on validating 00:28:33.480 --> 00:28:43.570 align:start position:0% Patrick for his talk on validating Bridges<00:28:34.260> Roll-Ups<00:28:34.860> and<00:28:34.919> plasmas 00:28:43.570 --> 00:28:43.580 align:start position:0% 00:28:43.580 --> 00:28:46.580 align:start position:0% thank<00:28:44.580> you