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.030 align:start position:0% [Music] 00:00:14.030 --> 00:00:14.040 align:start position:0% 00:00:14.040 --> 00:00:16.250 align:start position:0% I<00:00:14.580> thought<00:00:14.700> you<00:00:14.940> know<00:00:15.059> other<00:00:15.780> chains<00:00:16.199> have 00:00:16.250 --> 00:00:16.260 align:start position:0% I thought you know other chains have 00:00:16.260 --> 00:00:18.470 align:start position:0% I thought you know other chains have gone<00:00:16.440> before<00:00:16.619> ethereum<00:00:17.279> and<00:00:18.000> they've<00:00:18.300> done 00:00:18.470 --> 00:00:18.480 align:start position:0% gone before ethereum and they've done 00:00:18.480 --> 00:00:20.090 align:start position:0% gone before ethereum and they've done different<00:00:18.660> things<00:00:18.900> in<00:00:19.140> ethereum<00:00:19.560> and<00:00:19.920> we've 00:00:20.090 --> 00:00:20.100 align:start position:0% different things in ethereum and we've 00:00:20.100 --> 00:00:22.490 align:start position:0% different things in ethereum and we've adapted<00:00:20.520> things<00:00:20.760> and<00:00:21.660> so<00:00:21.779> is<00:00:21.960> ethereum<00:00:22.439> is 00:00:22.490 --> 00:00:22.500 align:start position:0% adapted things and so is ethereum is 00:00:22.500 --> 00:00:24.410 align:start position:0% adapted things and so is ethereum is moving<00:00:22.740> forward<00:00:22.920> we<00:00:23.820> should<00:00:23.939> look<00:00:24.060> and<00:00:24.240> see 00:00:24.410 --> 00:00:24.420 align:start position:0% moving forward we should look and see 00:00:24.420 --> 00:00:25.670 align:start position:0% moving forward we should look and see what's<00:00:24.539> worked<00:00:24.900> with<00:00:24.960> them<00:00:25.080> and<00:00:25.260> what<00:00:25.380> hasn't 00:00:25.670 --> 00:00:25.680 align:start position:0% what's worked with them and what hasn't 00:00:25.680 --> 00:00:27.470 align:start position:0% what's worked with them and what hasn't worked<00:00:25.920> with<00:00:25.980> them<00:00:26.160> so<00:00:26.699> the<00:00:26.880> thought<00:00:27.000> I<00:00:27.180> had<00:00:27.300> is 00:00:27.470 --> 00:00:27.480 align:start position:0% worked with them so the thought I had is 00:00:27.480 --> 00:00:28.790 align:start position:0% worked with them so the thought I had is some<00:00:27.660> of<00:00:27.720> these<00:00:27.840> changes<00:00:28.140> are<00:00:28.199> Trailblazers 00:00:28.790 --> 00:00:28.800 align:start position:0% some of these changes are Trailblazers 00:00:28.800 --> 00:00:30.230 align:start position:0% some of these changes are Trailblazers and<00:00:29.039> some<00:00:29.220> of<00:00:29.279> them<00:00:29.400> are<00:00:29.519> shipwrecks<00:00:30.060> as 00:00:30.230 --> 00:00:30.240 align:start position:0% and some of them are shipwrecks as 00:00:30.240 --> 00:00:31.970 align:start position:0% and some of them are shipwrecks as warnings<00:00:30.539> to<00:00:30.840> don't<00:00:31.019> go<00:00:31.199> there 00:00:31.970 --> 00:00:31.980 align:start position:0% warnings to don't go there 00:00:31.980 --> 00:00:34.729 align:start position:0% warnings to don't go there so<00:00:32.460> I<00:00:32.640> thought<00:00:32.759> I'd<00:00:32.940> ask<00:00:33.120> Dolly<00:00:33.719> to<00:00:34.020> the<00:00:34.320> AI 00:00:34.729 --> 00:00:34.739 align:start position:0% so I thought I'd ask Dolly to the AI 00:00:34.739 --> 00:00:37.190 align:start position:0% so I thought I'd ask Dolly to the AI generation<00:00:35.219> program<00:00:35.579> to<00:00:36.239> create<00:00:36.660> an<00:00:36.840> image<00:00:37.079> of 00:00:37.190 --> 00:00:37.200 align:start position:0% generation program to create an image of 00:00:37.200 --> 00:00:39.530 align:start position:0% generation program to create an image of me<00:00:37.320> of<00:00:37.860> a<00:00:37.980> covered<00:00:38.280> wagon<00:00:38.640> on<00:00:38.940> a<00:00:39.120> Seaside 00:00:39.530 --> 00:00:39.540 align:start position:0% me of a covered wagon on a Seaside 00:00:39.540 --> 00:00:41.930 align:start position:0% me of a covered wagon on a Seaside looking<00:00:40.140> out<00:00:40.440> over<00:00:40.620> a<00:00:40.860> shipwreck 00:00:41.930 --> 00:00:41.940 align:start position:0% looking out over a shipwreck 00:00:41.940 --> 00:00:43.430 align:start position:0% looking out over a shipwreck and<00:00:42.300> what<00:00:42.420> I<00:00:42.540> got<00:00:42.660> instead<00:00:43.079> was<00:00:43.200> something 00:00:43.430 --> 00:00:43.440 align:start position:0% and what I got instead was something 00:00:43.440 --> 00:00:45.049 align:start position:0% and what I got instead was something more<00:00:43.800> awesome 00:00:45.049 --> 00:00:45.059 align:start position:0% more awesome 00:00:45.059 --> 00:00:47.209 align:start position:0% more awesome I<00:00:45.420> got<00:00:45.540> this<00:00:45.780> over<00:00:46.260> here<00:00:46.440> you<00:00:46.620> see<00:00:46.800> a<00:00:47.040> broken 00:00:47.209 --> 00:00:47.219 align:start position:0% I got this over here you see a broken 00:00:47.219 --> 00:00:49.549 align:start position:0% I got this over here you see a broken down<00:00:47.579> wagon<00:00:48.180> that's<00:00:48.480> broken<00:00:48.780> this<00:00:49.320> is<00:00:49.440> the 00:00:49.549 --> 00:00:49.559 align:start position:0% down wagon that's broken this is the 00:00:49.559 --> 00:00:52.369 align:start position:0% down wagon that's broken this is the real<00:00:49.680> wreck<00:00:50.100> and<00:00:50.760> this<00:00:50.940> isn't<00:00:51.180> a<00:00:51.360> ship<00:00:51.539> this<00:00:52.260> is 00:00:52.369 --> 00:00:52.379 align:start position:0% real wreck and this isn't a ship this is 00:00:52.379 --> 00:00:54.770 align:start position:0% real wreck and this isn't a ship this is a<00:00:52.559> wagon<00:00:52.920> that's<00:00:53.399> converted<00:00:53.940> its<00:00:54.180> cover<00:00:54.360> into 00:00:54.770 --> 00:00:54.780 align:start position:0% a wagon that's converted its cover into 00:00:54.780 --> 00:00:57.170 align:start position:0% a wagon that's converted its cover into a<00:00:55.079> sail<00:00:55.379> so<00:00:55.860> this<00:00:56.100> isn't<00:00:56.340> the<00:00:56.520> East<00:00:56.699> Coast<00:00:56.879> if 00:00:57.170 --> 00:00:57.180 align:start position:0% a sail so this isn't the East Coast if 00:00:57.180 --> 00:00:59.029 align:start position:0% a sail so this isn't the East Coast if you're<00:00:57.300> heading<00:00:57.600> west<00:00:57.780> this<00:00:58.500> is<00:00:58.620> the<00:00:58.800> West 00:00:59.029 --> 00:00:59.039 align:start position:0% you're heading west this is the West 00:00:59.039 --> 00:01:01.369 align:start position:0% you're heading west this is the West Coast<00:00:59.280> they<00:01:00.180> made<00:01:00.360> it<00:01:00.539> to<00:01:00.719> their<00:01:00.899> destination 00:01:01.369 --> 00:01:01.379 align:start position:0% Coast they made it to their destination 00:01:01.379 --> 00:01:04.310 align:start position:0% Coast they made it to their destination but<00:01:02.100> this<00:01:02.280> wagon<00:01:02.760> is<00:01:03.180> learning<00:01:03.600> from<00:01:04.140> other 00:01:04.310 --> 00:01:04.320 align:start position:0% but this wagon is learning from other 00:01:04.320 --> 00:01:06.230 align:start position:0% but this wagon is learning from other systems<00:01:04.799> it<00:01:05.040> is<00:01:05.220> adapting<00:01:05.640> it<00:01:05.939> is<00:01:06.060> getting 00:01:06.230 --> 00:01:06.240 align:start position:0% systems it is adapting it is getting 00:01:06.240 --> 00:01:08.810 align:start position:0% systems it is adapting it is getting ready<00:01:06.420> to<00:01:06.720> set<00:01:06.960> sail<00:01:07.320> and<00:01:07.860> head<00:01:08.040> even<00:01:08.340> further 00:01:08.810 --> 00:01:08.820 align:start position:0% ready to set sail and head even further 00:01:08.820 --> 00:01:12.050 align:start position:0% ready to set sail and head even further west<00:01:09.060> so<00:01:10.560> um<00:01:10.560> how<00:01:11.159> to<00:01:11.340> read<00:01:11.460> this<00:01:11.640> presentation 00:01:12.050 --> 00:01:12.060 align:start position:0% west so um how to read this presentation 00:01:12.060 --> 00:01:13.550 align:start position:0% west so um how to read this presentation most<00:01:12.420> of<00:01:12.540> these<00:01:12.659> slides<00:01:12.900> are<00:01:13.020> going<00:01:13.140> to<00:01:13.260> be<00:01:13.320> in 00:01:13.550 --> 00:01:13.560 align:start position:0% most of these slides are going to be in 00:01:13.560 --> 00:01:15.730 align:start position:0% most of these slides are going to be in two<00:01:13.740> columns<00:01:14.220> on<00:01:14.880> the<00:01:15.000> left<00:01:15.119> is<00:01:15.299> going<00:01:15.479> to<00:01:15.659> be 00:01:15.730 --> 00:01:15.740 align:start position:0% two columns on the left is going to be 00:01:15.740 --> 00:01:18.410 align:start position:0% two columns on the left is going to be what<00:01:16.740> other<00:01:16.920> chains<00:01:17.400> do<00:01:17.640> in<00:01:18.060> some<00:01:18.240> of<00:01:18.360> the 00:01:18.410 --> 00:01:18.420 align:start position:0% what other chains do in some of the 00:01:18.420 --> 00:01:20.149 align:start position:0% what other chains do in some of the details<00:01:18.780> that<00:01:18.900> are<00:01:19.020> relevant<00:01:19.320> and<00:01:19.920> on<00:01:20.040> the 00:01:20.149 --> 00:01:20.159 align:start position:0% details that are relevant and on the 00:01:20.159 --> 00:01:23.149 align:start position:0% details that are relevant and on the right<00:01:20.420> is<00:01:21.420> what<00:01:21.900> ethereum<00:01:22.439> could<00:01:22.740> learn<00:01:22.920> from 00:01:23.149 --> 00:01:23.159 align:start position:0% right is what ethereum could learn from 00:01:23.159 --> 00:01:24.890 align:start position:0% right is what ethereum could learn from it<00:01:23.340> sometimes<00:01:24.180> we<00:01:24.360> learn<00:01:24.479> good<00:01:24.720> things 00:01:24.890 --> 00:01:24.900 align:start position:0% it sometimes we learn good things 00:01:24.900 --> 00:01:27.410 align:start position:0% it sometimes we learn good things sometimes<00:01:25.320> we<00:01:25.500> learn<00:01:26.040> things<00:01:26.220> not<00:01:26.400> to<00:01:26.580> do<00:01:26.700> and 00:01:27.410 --> 00:01:27.420 align:start position:0% sometimes we learn things not to do and 00:01:27.420 --> 00:01:29.030 align:start position:0% sometimes we learn things not to do and sometimes<00:01:27.840> that's<00:01:28.080> that's<00:01:28.320> just<00:01:28.619> a<00:01:28.799> neat 00:01:29.030 --> 00:01:29.040 align:start position:0% sometimes that's that's just a neat 00:01:29.040 --> 00:01:30.890 align:start position:0% sometimes that's that's just a neat thing<00:01:29.220> to<00:01:29.580> know<00:01:29.759> but<00:01:30.180> it<00:01:30.420> really<00:01:30.540> won't<00:01:30.720> work 00:01:30.890 --> 00:01:30.900 align:start position:0% thing to know but it really won't work 00:01:30.900 --> 00:01:33.890 align:start position:0% thing to know but it really won't work for<00:01:31.080> ethereum<00:01:31.560> and<00:01:32.520> I<00:01:33.299> kind<00:01:33.420> of<00:01:33.479> live<00:01:33.600> in<00:01:33.720> both 00:01:33.890 --> 00:01:33.900 align:start position:0% for ethereum and I kind of live in both 00:01:33.900 --> 00:01:36.109 align:start position:0% for ethereum and I kind of live in both worlds<00:01:34.259> on<00:01:34.439> this<00:01:34.619> the<00:01:35.220> reason<00:01:35.340> I<00:01:35.579> came<00:01:35.880> up<00:01:36.000> with 00:01:36.109 --> 00:01:36.119 align:start position:0% worlds on this the reason I came up with 00:01:36.119 --> 00:01:37.730 align:start position:0% worlds on this the reason I came up with the<00:01:36.240> idea<00:01:36.420> for<00:01:36.600> this<00:01:36.720> talk<00:01:36.900> was<00:01:37.140> I<00:01:37.439> work<00:01:37.560> at 00:01:37.730 --> 00:01:37.740 align:start position:0% the idea for this talk was I work at 00:01:37.740 --> 00:01:39.950 align:start position:0% the idea for this talk was I work at hedera<00:01:38.340> hashgraph<00:01:38.880> I<00:01:39.540> was<00:01:39.659> one<00:01:39.840> of<00:01:39.900> the 00:01:39.950 --> 00:01:39.960 align:start position:0% hedera hashgraph I was one of the 00:01:39.960 --> 00:01:41.690 align:start position:0% hedera hashgraph I was one of the maintainers<00:01:40.320> of<00:01:40.500> hyperledger<00:01:40.920> base<00:01:41.159> 2<00:01:41.400> and 00:01:41.690 --> 00:01:41.700 align:start position:0% maintainers of hyperledger base 2 and 00:01:41.700 --> 00:01:43.550 align:start position:0% maintainers of hyperledger base 2 and they<00:01:41.880> wanted<00:01:42.060> to<00:01:42.299> improve<00:01:42.659> their<00:01:43.200> ethereum 00:01:43.550 --> 00:01:43.560 align:start position:0% they wanted to improve their ethereum 00:01:43.560 --> 00:01:45.950 align:start position:0% they wanted to improve their ethereum compatibility<00:01:44.159> game<00:01:44.460> so<00:01:44.700> now<00:01:44.939> idea<00:01:45.479> was<00:01:45.659> well 00:01:45.950 --> 00:01:45.960 align:start position:0% compatibility game so now idea was well 00:01:45.960 --> 00:01:48.230 align:start position:0% compatibility game so now idea was well hedera's<00:01:46.860> Java<00:01:47.100> based<00:01:47.340> base<00:01:47.460> is<00:01:47.700> Java<00:01:48.000> based 00:01:48.230 --> 00:01:48.240 align:start position:0% hedera's Java based base is Java based 00:01:48.240 --> 00:01:50.149 align:start position:0% hedera's Java based base is Java based let's<00:01:48.360> just<00:01:48.600> complementize<00:01:49.320> out<00:01:49.560> their<00:01:49.740> evm 00:01:50.149 --> 00:01:50.159 align:start position:0% let's just complementize out their evm 00:01:50.159 --> 00:01:52.429 align:start position:0% let's just complementize out their evm and<00:01:50.520> bring<00:01:50.700> it<00:01:50.820> into<00:01:50.939> hedera<00:01:51.600> and<00:01:52.079> bring<00:01:52.259> that 00:01:52.429 --> 00:01:52.439 align:start position:0% and bring it into hedera and bring that 00:01:52.439 --> 00:01:54.289 align:start position:0% and bring it into hedera and bring that software<00:01:52.799> over<00:01:53.040> and<00:01:53.340> suddenly<00:01:53.700> boom<00:01:54.000> 100 00:01:54.289 --> 00:01:54.299 align:start position:0% software over and suddenly boom 100 00:01:54.299 --> 00:01:56.030 align:start position:0% software over and suddenly boom 100 evium<00:01:54.960> compatible 00:01:56.030 --> 00:01:56.040 align:start position:0% evium compatible 00:01:56.040 --> 00:01:58.310 align:start position:0% evium compatible it's<00:01:56.520> not<00:01:56.640> that<00:01:56.880> simple<00:01:57.540> there's<00:01:57.840> a<00:01:58.020> lot<00:01:58.140> more 00:01:58.310 --> 00:01:58.320 align:start position:0% it's not that simple there's a lot more 00:01:58.320 --> 00:01:59.749 align:start position:0% it's not that simple there's a lot more to<00:01:58.500> it<00:01:58.619> than<00:01:58.799> just<00:01:58.920> reading<00:01:59.159> byte<00:01:59.460> code<00:01:59.579> and 00:01:59.749 --> 00:01:59.759 align:start position:0% to it than just reading byte code and 00:01:59.759 --> 00:02:01.490 align:start position:0% to it than just reading byte code and executing<00:02:00.240> programs 00:02:01.490 --> 00:02:01.500 align:start position:0% executing programs 00:02:01.500 --> 00:02:02.630 align:start position:0% executing programs so<00:02:01.740> I'm<00:02:01.860> going<00:02:01.979> to<00:02:02.040> talk<00:02:02.159> about<00:02:02.280> three 00:02:02.630 --> 00:02:02.640 align:start position:0% so I'm going to talk about three 00:02:02.640 --> 00:02:04.789 align:start position:0% so I'm going to talk about three separate<00:02:03.060> areas<00:02:03.360> the<00:02:04.140> first<00:02:04.259> area<00:02:04.439> is<00:02:04.619> going 00:02:04.789 --> 00:02:04.799 align:start position:0% separate areas the first area is going 00:02:04.799 --> 00:02:06.709 align:start position:0% separate areas the first area is going to be<00:02:04.920> accounts<00:02:05.340> and<00:02:05.399> cryptography<00:02:06.000> then<00:02:06.600> I'm 00:02:06.709 --> 00:02:06.719 align:start position:0% to be accounts and cryptography then I'm 00:02:06.719 --> 00:02:07.850 align:start position:0% to be accounts and cryptography then I'm going<00:02:06.840> to<00:02:06.899> spend<00:02:07.079> a<00:02:07.200> little<00:02:07.320> bit<00:02:07.439> of<00:02:07.560> time<00:02:07.680> on 00:02:07.850 --> 00:02:07.860 align:start position:0% going to spend a little bit of time on 00:02:07.860 --> 00:02:09.589 align:start position:0% going to spend a little bit of time on the<00:02:07.979> evm<00:02:08.399> itself<00:02:08.700> and<00:02:09.179> then<00:02:09.239> I'm<00:02:09.360> going<00:02:09.539> to 00:02:09.589 --> 00:02:09.599 align:start position:0% the evm itself and then I'm going to 00:02:09.599 --> 00:02:11.630 align:start position:0% the evm itself and then I'm going to talk<00:02:09.720> about<00:02:09.899> transactions<00:02:10.860> and<00:02:11.280> and 00:02:11.630 --> 00:02:11.640 align:start position:0% talk about transactions and and 00:02:11.640 --> 00:02:14.030 align:start position:0% talk about transactions and and transacting<00:02:12.239> with<00:02:12.360> ethereum<00:02:12.900> which<00:02:13.140> is<00:02:13.860> is 00:02:14.030 --> 00:02:14.040 align:start position:0% transacting with ethereum which is is 00:02:14.040 --> 00:02:16.010 align:start position:0% transacting with ethereum which is is kind<00:02:14.340> of<00:02:14.459> an<00:02:14.580> important<00:02:14.940> thing<00:02:15.120> if<00:02:15.780> you<00:02:15.900> can't 00:02:16.010 --> 00:02:16.020 align:start position:0% kind of an important thing if you can't 00:02:16.020 --> 00:02:17.930 align:start position:0% kind of an important thing if you can't put<00:02:16.200> your<00:02:16.379> transaction<00:02:16.739> on<00:02:17.040> a<00:02:17.220> chain<00:02:17.340> the 00:02:17.930 --> 00:02:17.940 align:start position:0% put your transaction on a chain the 00:02:17.940 --> 00:02:19.670 align:start position:0% put your transaction on a chain the chain<00:02:18.120> may<00:02:18.360> as<00:02:18.540> well<00:02:18.660> not<00:02:18.840> exist 00:02:19.670 --> 00:02:19.680 align:start position:0% chain may as well not exist 00:02:19.680 --> 00:02:22.070 align:start position:0% chain may as well not exist so<00:02:20.160> the<00:02:20.340> first<00:02:20.459> thing<00:02:20.640> to<00:02:20.819> talk<00:02:20.940> about<00:02:21.120> on<00:02:21.840> on 00:02:22.070 --> 00:02:22.080 align:start position:0% so the first thing to talk about on on 00:02:22.080 --> 00:02:23.449 align:start position:0% so the first thing to talk about on on crypto<00:02:22.500> on<00:02:22.620> the<00:02:22.860> accounts<00:02:23.220> is<00:02:23.340> the 00:02:23.449 --> 00:02:23.459 align:start position:0% crypto on the accounts is the 00:02:23.459 --> 00:02:25.670 align:start position:0% crypto on the accounts is the cryptography<00:02:24.120> accounts<00:02:25.020> are<00:02:25.080> in<00:02:25.260> ethereum 00:02:25.670 --> 00:02:25.680 align:start position:0% cryptography accounts are in ethereum 00:02:25.680 --> 00:02:27.470 align:start position:0% cryptography accounts are in ethereum are<00:02:25.800> intrinsically<00:02:26.340> tied<00:02:26.640> to<00:02:27.120> your<00:02:27.300> public 00:02:27.470 --> 00:02:27.480 align:start position:0% are intrinsically tied to your public 00:02:27.480 --> 00:02:29.690 align:start position:0% are intrinsically tied to your public key<00:02:27.780> and<00:02:28.500> a<00:02:28.620> lot<00:02:28.739> of<00:02:28.800> other<00:02:28.980> operations<00:02:29.400> are 00:02:29.690 --> 00:02:29.700 align:start position:0% key and a lot of other operations are 00:02:29.700 --> 00:02:31.990 align:start position:0% key and a lot of other operations are intrinsically<00:02:30.660> tied<00:02:30.900> to<00:02:31.080> hashing<00:02:31.440> operations 00:02:31.990 --> 00:02:32.000 align:start position:0% intrinsically tied to hashing operations 00:02:32.000 --> 00:02:34.070 align:start position:0% intrinsically tied to hashing operations nearly<00:02:33.000> every<00:02:33.180> different<00:02:33.420> chain<00:02:33.660> out<00:02:33.900> there 00:02:34.070 --> 00:02:34.080 align:start position:0% nearly every different chain out there 00:02:34.080 --> 00:02:36.710 align:start position:0% nearly every different chain out there has<00:02:34.620> a<00:02:34.860> different<00:02:35.040> setup<00:02:35.459> for<00:02:35.940> the<00:02:36.239> encryption 00:02:36.710 --> 00:02:36.720 align:start position:0% has a different setup for the encryption 00:02:36.720 --> 00:02:38.210 align:start position:0% has a different setup for the encryption that<00:02:36.900> it<00:02:37.020> uses 00:02:38.210 --> 00:02:38.220 align:start position:0% that it uses 00:02:38.220 --> 00:02:42.050 align:start position:0% that it uses um<00:02:38.580> ethereum<00:02:39.300> uses<00:02:39.599> ecdsa<00:02:40.379> on<00:02:40.560> secp<00:02:41.160> 256k1 00:02:42.050 --> 00:02:42.060 align:start position:0% um ethereum uses ecdsa on secp 256k1 00:02:42.060 --> 00:02:45.410 align:start position:0% um ethereum uses ecdsa on secp 256k1 hedera<00:02:42.959> uses<00:02:43.200> Edwards<00:02:43.680> as<00:02:44.040> does<00:02:44.280> near<00:02:44.640> polka 00:02:45.410 --> 00:02:45.420 align:start position:0% hedera uses Edwards as does near polka 00:02:45.420 --> 00:02:47.630 align:start position:0% hedera uses Edwards as does near polka dot<00:02:45.599> uses<00:02:45.840> a<00:02:46.019> combination<00:02:46.260> of<00:02:46.440> schnor<00:02:47.040> and 00:02:47.630 --> 00:02:47.640 align:start position:0% dot uses a combination of schnor and 00:02:47.640 --> 00:02:50.210 align:start position:0% dot uses a combination of schnor and curve<00:02:48.019> 25519<00:02:49.019> which<00:02:49.319> is<00:02:49.440> pretty<00:02:49.680> unique<00:02:49.980> and 00:02:50.210 --> 00:02:50.220 align:start position:0% curve 25519 which is pretty unique and 00:02:50.220 --> 00:02:53.110 align:start position:0% curve 25519 which is pretty unique and insensible<00:02:51.120> and<00:02:51.720> the<00:02:51.840> consensus<00:02:52.260> layer<00:02:52.500> uses 00:02:53.110 --> 00:02:53.120 align:start position:0% insensible and the consensus layer uses 00:02:53.120 --> 00:02:55.850 align:start position:0% insensible and the consensus layer uses bls-12381<00:02:54.120> and<00:02:54.959> there's<00:02:55.080> a<00:02:55.319> lot<00:02:55.379> of<00:02:55.500> variation 00:02:55.850 --> 00:02:55.860 align:start position:0% bls-12381 and there's a lot of variation 00:02:55.860 --> 00:02:57.470 align:start position:0% bls-12381 and there's a lot of variation in<00:02:56.220> there<00:02:56.400> and<00:02:56.819> then<00:02:56.940> you<00:02:57.060> look<00:02:57.239> at<00:02:57.360> the 00:02:57.470 --> 00:02:57.480 align:start position:0% in there and then you look at the 00:02:57.480 --> 00:02:59.270 align:start position:0% in there and then you look at the hashing<00:02:57.840> algorithms<00:02:58.319> there's<00:02:58.800> an<00:02:59.040> older 00:02:59.270 --> 00:02:59.280 align:start position:0% hashing algorithms there's an older 00:02:59.280 --> 00:03:01.309 align:start position:0% hashing algorithms there's an older draft<00:02:59.459> of<00:02:59.760> of<00:03:00.000> shot<00:03:00.239> three<00:03:00.480> called<00:03:00.720> contract 00:03:01.309 --> 00:03:01.319 align:start position:0% draft of of shot three called contract 00:03:01.319 --> 00:03:03.170 align:start position:0% draft of of shot three called contract that<00:03:01.500> ethereum<00:03:01.860> uses<00:03:02.160> then<00:03:02.640> there's<00:03:02.819> actual 00:03:03.170 --> 00:03:03.180 align:start position:0% that ethereum uses then there's actual 00:03:03.180 --> 00:03:05.390 align:start position:0% that ethereum uses then there's actual shot<00:03:03.420> 3<00:03:03.660> which<00:03:03.840> hedera<00:03:04.379> uses<00:03:04.620> but<00:03:05.040> they<00:03:05.220> use 00:03:05.390 --> 00:03:05.400 align:start position:0% shot 3 which hedera uses but they use 00:03:05.400 --> 00:03:09.050 align:start position:0% shot 3 which hedera uses but they use more<00:03:05.580> bits<00:03:06.200> near<00:03:07.200> uses<00:03:07.620> shot<00:03:07.800> 256<00:03:08.400> as<00:03:08.640> as<00:03:08.879> the 00:03:09.050 --> 00:03:09.060 align:start position:0% more bits near uses shot 256 as as the 00:03:09.060 --> 00:03:11.030 align:start position:0% more bits near uses shot 256 as as the consensus<00:03:09.360> layer<00:03:09.720> and<00:03:09.959> polka<00:03:10.319> dot<00:03:10.500> uses<00:03:10.680> Blake 00:03:11.030 --> 00:03:11.040 align:start position:0% consensus layer and polka dot uses Blake 00:03:11.040 --> 00:03:12.710 align:start position:0% consensus layer and polka dot uses Blake 2. 00:03:12.710 --> 00:03:12.720 align:start position:0% 2. 00:03:12.720 --> 00:03:14.149 align:start position:0% 2. um<00:03:12.780> so<00:03:13.260> one<00:03:13.440> of<00:03:13.560> the<00:03:13.620> things<00:03:13.680> looking<00:03:13.860> at<00:03:14.040> this 00:03:14.149 --> 00:03:14.159 align:start position:0% um so one of the things looking at this 00:03:14.159 --> 00:03:15.410 align:start position:0% um so one of the things looking at this is<00:03:14.340> you<00:03:14.459> might<00:03:14.580> think<00:03:14.760> we<00:03:14.879> can<00:03:15.000> just<00:03:15.120> pick<00:03:15.239> one 00:03:15.410 --> 00:03:15.420 align:start position:0% is you might think we can just pick one 00:03:15.420 --> 00:03:18.170 align:start position:0% is you might think we can just pick one and<00:03:15.599> go<00:03:15.720> with<00:03:15.840> it<00:03:16.440> the<00:03:16.920> problem<00:03:17.099> is<00:03:17.400> need 00:03:18.170 --> 00:03:18.180 align:start position:0% and go with it the problem is need 00:03:18.180 --> 00:03:19.970 align:start position:0% and go with it the problem is need cryptography<00:03:18.900> needs<00:03:19.260> change<00:03:19.440> over<00:03:19.680> time 00:03:19.970 --> 00:03:19.980 align:start position:0% cryptography needs change over time 00:03:19.980 --> 00:03:22.190 align:start position:0% cryptography needs change over time attacks<00:03:20.940> against<00:03:21.060> cryptography<00:03:21.840> don't<00:03:22.080> get 00:03:22.190 --> 00:03:22.200 align:start position:0% attacks against cryptography don't get 00:03:22.200 --> 00:03:24.410 align:start position:0% attacks against cryptography don't get worse<00:03:22.560> they<00:03:22.920> only<00:03:23.099> get<00:03:23.340> better<00:03:23.519> new<00:03:23.819> ideas<00:03:24.060> get 00:03:24.410 --> 00:03:24.420 align:start position:0% worse they only get better new ideas get 00:03:24.420 --> 00:03:26.149 align:start position:0% worse they only get better new ideas get found<00:03:24.720> one<00:03:25.379> of<00:03:25.560> the<00:03:25.560> big<00:03:25.680> things<00:03:25.800> on<00:03:25.980> the 00:03:26.149 --> 00:03:26.159 align:start position:0% found one of the big things on the 00:03:26.159 --> 00:03:28.729 align:start position:0% found one of the big things on the horizon<00:03:26.400> is<00:03:26.640> quantum<00:03:27.120> resistance<00:03:27.720> if<00:03:28.500> we<00:03:28.620> want 00:03:28.729 --> 00:03:28.739 align:start position:0% horizon is quantum resistance if we want 00:03:28.739 --> 00:03:31.790 align:start position:0% horizon is quantum resistance if we want ethereum<00:03:29.220> to<00:03:29.400> last<00:03:29.640> 10<00:03:30.060> 20<00:03:30.300> 50<00:03:30.599> years<00:03:30.900> at<00:03:31.620> some 00:03:31.790 --> 00:03:31.800 align:start position:0% ethereum to last 10 20 50 years at some 00:03:31.800 --> 00:03:32.930 align:start position:0% ethereum to last 10 20 50 years at some point<00:03:31.920> we're<00:03:32.099> going<00:03:32.220> to<00:03:32.280> have<00:03:32.400> to<00:03:32.519> change<00:03:32.700> some 00:03:32.930 --> 00:03:32.940 align:start position:0% point we're going to have to change some 00:03:32.940 --> 00:03:34.790 align:start position:0% point we're going to have to change some of<00:03:33.120> these<00:03:33.239> algorithms<00:03:33.720> and<00:03:34.260> at<00:03:34.379> some<00:03:34.560> points 00:03:34.790 --> 00:03:34.800 align:start position:0% of these algorithms and at some points 00:03:34.800 --> 00:03:35.990 align:start position:0% of these algorithms and at some points we're<00:03:34.860> going<00:03:34.980> to<00:03:35.040> have<00:03:35.159> to<00:03:35.280> do<00:03:35.459> significant 00:03:35.990 --> 00:03:36.000 align:start position:0% we're going to have to do significant 00:03:36.000 --> 00:03:38.509 align:start position:0% we're going to have to do significant changes<00:03:36.480> so<00:03:37.260> we<00:03:37.440> should<00:03:37.620> continue<00:03:38.099> to<00:03:38.400> build 00:03:38.509 --> 00:03:38.519 align:start position:0% changes so we should continue to build 00:03:38.519 --> 00:03:39.710 align:start position:0% changes so we should continue to build with<00:03:38.700> this<00:03:38.879> in<00:03:39.000> mind<00:03:39.120> that<00:03:39.300> we're<00:03:39.480> going<00:03:39.599> to 00:03:39.710 --> 00:03:39.720 align:start position:0% with this in mind that we're going to 00:03:39.720 --> 00:03:41.089 align:start position:0% with this in mind that we're going to want<00:03:39.780> to<00:03:39.900> change<00:03:40.080> it<00:03:40.260> I<00:03:40.440> mean<00:03:40.560> as<00:03:40.680> it<00:03:40.799> is<00:03:40.920> right 00:03:41.089 --> 00:03:41.099 align:start position:0% want to change it I mean as it is right 00:03:41.099 --> 00:03:43.490 align:start position:0% want to change it I mean as it is right now<00:03:41.280> we<00:03:41.940> may<00:03:42.060> want<00:03:42.239> to<00:03:42.420> change<00:03:42.540> it<00:03:42.780> to<00:03:43.019> use<00:03:43.200> the 00:03:43.490 --> 00:03:43.500 align:start position:0% now we may want to change it to use the 00:03:43.500 --> 00:03:45.530 align:start position:0% now we may want to change it to use the wrong<00:03:43.920> button<00:03:44.280> this<00:03:44.400> is<00:03:44.519> the<00:03:44.640> laser<00:03:44.940> we<00:03:45.360> may 00:03:45.530 --> 00:03:45.540 align:start position:0% wrong button this is the laser we may 00:03:45.540 --> 00:03:48.470 align:start position:0% wrong button this is the laser we may want<00:03:45.720> to<00:03:45.780> use<00:03:45.900> BLS<00:03:46.500> 12<00:03:46.739> 381<00:03:47.400> for<00:03:48.000> some<00:03:48.239> of<00:03:48.360> our 00:03:48.470 --> 00:03:48.480 align:start position:0% want to use BLS 12 381 for some of our 00:03:48.480 --> 00:03:50.149 align:start position:0% want to use BLS 12 381 for some of our accounts<00:03:48.959> it's<00:03:49.319> not<00:03:49.500> just<00:03:49.680> useful<00:03:49.980> on 00:03:50.149 --> 00:03:50.159 align:start position:0% accounts it's not just useful on 00:03:50.159 --> 00:03:52.490 align:start position:0% accounts it's not just useful on ethereum<00:03:50.640> mainnet<00:03:51.060> on<00:03:51.420> ethereum<00:03:51.959> on<00:03:52.379> the 00:03:52.490 --> 00:03:52.500 align:start position:0% ethereum mainnet on ethereum on the 00:03:52.500 --> 00:03:54.350 align:start position:0% ethereum mainnet on ethereum on the consensus<00:03:52.920> layer<00:03:53.220> for<00:03:53.940> aggregating 00:03:54.350 --> 00:03:54.360 align:start position:0% consensus layer for aggregating 00:03:54.360 --> 00:03:56.570 align:start position:0% consensus layer for aggregating signatures<00:03:54.959> but<00:03:55.260> it's<00:03:55.440> useful<00:03:55.680> on<00:03:55.920> layer<00:03:56.220> Twos 00:03:56.570 --> 00:03:56.580 align:start position:0% signatures but it's useful on layer Twos 00:03:56.580 --> 00:03:58.070 align:start position:0% signatures but it's useful on layer Twos for<00:03:57.000> aggregating<00:03:57.480> all<00:03:57.720> of<00:03:57.900> their 00:03:58.070 --> 00:03:58.080 align:start position:0% for aggregating all of their 00:03:58.080 --> 00:04:00.229 align:start position:0% for aggregating all of their transactions<00:03:58.739> into<00:03:58.980> one<00:03:59.340> signed<00:03:59.819> transaction 00:04:00.229 --> 00:04:00.239 align:start position:0% transactions into one signed transaction 00:04:00.239 --> 00:04:03.430 align:start position:0% transactions into one signed transaction now<00:04:01.140> that<00:04:01.260> comes<00:04:01.500> along<00:04:01.620> with<00:04:01.799> some<00:04:01.980> problems 00:04:03.430 --> 00:04:03.440 align:start position:0% now that comes along with some problems 00:04:03.440 --> 00:04:06.410 align:start position:0% now that comes along with some problems BLS<00:04:04.440> and<00:04:04.739> Edwards<00:04:05.280> require<00:04:05.519> you<00:04:05.819> to<00:04:05.940> bring<00:04:06.120> the 00:04:06.410 --> 00:04:06.420 align:start position:0% BLS and Edwards require you to bring the 00:04:06.420 --> 00:04:07.789 align:start position:0% BLS and Edwards require you to bring the public<00:04:06.599> key<00:04:06.900> along<00:04:07.080> with<00:04:07.319> you<00:04:07.379> I<00:04:07.560> think<00:04:07.680> that's 00:04:07.789 --> 00:04:07.799 align:start position:0% public key along with you I think that's 00:04:07.799 --> 00:04:09.229 align:start position:0% public key along with you I think that's covered<00:04:08.099> by<00:04:08.159> the<00:04:08.280> next<00:04:08.400> slide 00:04:09.229 --> 00:04:09.239 align:start position:0% covered by the next slide 00:04:09.239 --> 00:04:13.429 align:start position:0% covered by the next slide so<00:04:10.019> the<00:04:10.560> the<00:04:10.760> BLS<00:04:11.760> and<00:04:12.360> Edwards<00:04:13.080> require<00:04:13.260> you 00:04:13.429 --> 00:04:13.439 align:start position:0% so the the BLS and Edwards require you 00:04:13.439 --> 00:04:15.410 align:start position:0% so the the BLS and Edwards require you to<00:04:13.560> bring<00:04:13.680> your<00:04:13.799> public<00:04:13.980> key<00:04:14.220> ecdsa<00:04:15.180> doesn't 00:04:15.410 --> 00:04:15.420 align:start position:0% to bring your public key ecdsa doesn't 00:04:15.420 --> 00:04:17.270 align:start position:0% to bring your public key ecdsa doesn't so<00:04:15.900> we<00:04:16.019> need<00:04:16.139> to<00:04:16.260> put<00:04:16.380> more<00:04:16.680> space<00:04:16.799> in<00:04:16.979> some<00:04:17.160> of 00:04:17.270 --> 00:04:17.280 align:start position:0% so we need to put more space in some of 00:04:17.280 --> 00:04:19.189 align:start position:0% so we need to put more space in some of these<00:04:17.400> transactions<00:04:18.000> and<00:04:18.600> normalize<00:04:18.959> the 00:04:19.189 --> 00:04:19.199 align:start position:0% these transactions and normalize the 00:04:19.199 --> 00:04:21.050 align:start position:0% these transactions and normalize the practice<00:04:19.320> of<00:04:19.560> sending<00:04:19.919> your<00:04:20.040> public<00:04:20.220> key<00:04:20.459> or 00:04:21.050 --> 00:04:21.060 align:start position:0% practice of sending your public key or 00:04:21.060 --> 00:04:22.189 align:start position:0% practice of sending your public key or your<00:04:21.180> ethereum<00:04:21.600> and<00:04:21.720> you<00:04:21.840> can't<00:04:21.900> send<00:04:22.079> your 00:04:22.189 --> 00:04:22.199 align:start position:0% your ethereum and you can't send your 00:04:22.199 --> 00:04:23.450 align:start position:0% your ethereum and you can't send your ethereum<00:04:22.560> address<00:04:22.680> you<00:04:22.979> actually<00:04:23.160> need<00:04:23.340> the 00:04:23.450 --> 00:04:23.460 align:start position:0% ethereum address you actually need the 00:04:23.460 --> 00:04:25.490 align:start position:0% ethereum address you actually need the public<00:04:23.639> key<00:04:23.820> for<00:04:24.000> the<00:04:24.120> cryptography<00:04:24.780> so<00:04:25.259> for 00:04:25.490 --> 00:04:25.500 align:start position:0% public key for the cryptography so for 00:04:25.500 --> 00:04:26.570 align:start position:0% public key for the cryptography so for some<00:04:25.620> of<00:04:25.740> these<00:04:25.800> signatures<00:04:26.220> we<00:04:26.340> would<00:04:26.460> need 00:04:26.570 --> 00:04:26.580 align:start position:0% some of these signatures we would need 00:04:26.580 --> 00:04:28.310 align:start position:0% some of these signatures we would need to<00:04:26.699> socialize<00:04:27.120> that 00:04:28.310 --> 00:04:28.320 align:start position:0% to socialize that 00:04:28.320 --> 00:04:30.110 align:start position:0% to socialize that so<00:04:28.620> the<00:04:28.860> next<00:04:29.040> interesting<00:04:29.460> issue<00:04:29.820> comes 00:04:30.110 --> 00:04:30.120 align:start position:0% so the next interesting issue comes 00:04:30.120 --> 00:04:32.330 align:start position:0% so the next interesting issue comes along<00:04:30.240> with<00:04:30.419> the<00:04:30.540> account<00:04:30.720> addresses<00:04:31.340> hedera 00:04:32.330 --> 00:04:32.340 align:start position:0% along with the account addresses hedera 00:04:32.340 --> 00:04:35.450 align:start position:0% along with the account addresses hedera uses<00:04:32.639> a<00:04:33.259> sequential<00:04:34.259> system<00:04:34.560> counting<00:04:35.340> up 00:04:35.450 --> 00:04:35.460 align:start position:0% uses a sequential system counting up 00:04:35.460 --> 00:04:37.310 align:start position:0% uses a sequential system counting up from<00:04:35.699> a<00:04:35.820> thousand 00:04:37.310 --> 00:04:37.320 align:start position:0% from a thousand 00:04:37.320 --> 00:04:39.710 align:start position:0% from a thousand um<00:04:37.380> hedera<00:04:38.340> is<00:04:38.460> interesting<00:04:38.820> an<00:04:39.240> alias<00:04:39.600> system 00:04:39.710 --> 00:04:39.720 align:start position:0% um hedera is interesting an alias system 00:04:39.720 --> 00:04:41.870 align:start position:0% um hedera is interesting an alias system and<00:04:39.960> some<00:04:40.139> of<00:04:40.259> its<00:04:40.440> accounts<00:04:40.740> to<00:04:41.160> support<00:04:41.340> some 00:04:41.870 --> 00:04:41.880 align:start position:0% and some of its accounts to support some 00:04:41.880 --> 00:04:44.090 align:start position:0% and some of its accounts to support some of<00:04:42.000> the<00:04:42.060> needs<00:04:42.479> of<00:04:42.840> of<00:04:43.139> ethereum<00:04:43.680> mainnet 00:04:44.090 --> 00:04:44.100 align:start position:0% of the needs of of ethereum mainnet 00:04:44.100 --> 00:04:46.070 align:start position:0% of the needs of of ethereum mainnet create<00:04:44.280> two<00:04:44.580> you<00:04:45.120> have<00:04:45.240> to<00:04:45.360> use<00:04:45.540> the<00:04:45.780> ethereum 00:04:46.070 --> 00:04:46.080 align:start position:0% create two you have to use the ethereum 00:04:46.080 --> 00:04:47.689 align:start position:0% create two you have to use the ethereum equivalent<00:04:46.500> address<00:04:46.680> or<00:04:47.340> things<00:04:47.520> like 00:04:47.689 --> 00:04:47.699 align:start position:0% equivalent address or things like 00:04:47.699 --> 00:04:50.510 align:start position:0% equivalent address or things like uniswap<00:04:48.300> just<00:04:48.540> won't<00:04:48.720> work<00:04:49.280> we're<00:04:50.280> also 00:04:50.510 --> 00:04:50.520 align:start position:0% uniswap just won't work we're also 00:04:50.520 --> 00:04:53.689 align:start position:0% uniswap just won't work we're also considering<00:04:50.880> multiple<00:04:51.300> accounts<00:04:51.840> per<00:04:52.740> model 00:04:53.689 --> 00:04:53.699 align:start position:0% considering multiple accounts per model 00:04:53.699 --> 00:04:55.490 align:start position:0% considering multiple accounts per model but<00:04:54.360> some<00:04:54.600> of<00:04:54.660> the<00:04:54.780> interesting<00:04:55.080> things<00:04:55.199> here 00:04:55.490 --> 00:04:55.500 align:start position:0% but some of the interesting things here 00:04:55.500 --> 00:04:57.230 align:start position:0% but some of the interesting things here is<00:04:55.740> that 00:04:57.230 --> 00:04:57.240 align:start position:0% is that 00:04:57.240 --> 00:04:59.030 align:start position:0% is that um<00:04:57.300> by<00:04:57.780> disconnecting<00:04:58.320> the<00:04:58.440> public<00:04:58.560> key<00:04:58.800> from 00:04:59.030 --> 00:04:59.040 align:start position:0% um by disconnecting the public key from 00:04:59.040 --> 00:05:00.710 align:start position:0% um by disconnecting the public key from the<00:04:59.160> address<00:04:59.280> you<00:04:59.940> can<00:05:00.000> do<00:05:00.180> things<00:05:00.360> such<00:05:00.540> as 00:05:00.710 --> 00:05:00.720 align:start position:0% the address you can do things such as 00:05:00.720 --> 00:05:02.330 align:start position:0% the address you can do things such as key<00:05:00.900> rotation<00:05:01.320> which<00:05:01.620> is<00:05:01.680> critical<00:05:01.979> to<00:05:02.160> some 00:05:02.330 --> 00:05:02.340 align:start position:0% key rotation which is critical to some 00:05:02.340 --> 00:05:04.430 align:start position:0% key rotation which is critical to some Enterprise<00:05:02.580> applications<00:05:03.240> but<00:05:04.080> right<00:05:04.259> now 00:05:04.430 --> 00:05:04.440 align:start position:0% Enterprise applications but right now 00:05:04.440 --> 00:05:06.830 align:start position:0% Enterprise applications but right now your<00:05:04.979> key<00:05:05.160> is<00:05:05.280> tied<00:05:05.520> to<00:05:05.699> your<00:05:05.940> address 00:05:06.830 --> 00:05:06.840 align:start position:0% your key is tied to your address 00:05:06.840 --> 00:05:09.469 align:start position:0% your key is tied to your address so<00:05:07.680> account<00:05:08.280> abstraction<00:05:08.759> is<00:05:08.940> a<00:05:09.060> way<00:05:09.180> to<00:05:09.300> solve 00:05:09.469 --> 00:05:09.479 align:start position:0% so account abstraction is a way to solve 00:05:09.479 --> 00:05:11.629 align:start position:0% so account abstraction is a way to solve this<00:05:09.540> I<00:05:09.720> think<00:05:09.840> will<00:05:09.960> be<00:05:10.139> a<00:05:10.199> great<00:05:10.380> way 00:05:11.629 --> 00:05:11.639 align:start position:0% this I think will be a great way 00:05:11.639 --> 00:05:13.129 align:start position:0% this I think will be a great way um<00:05:11.699> but<00:05:12.180> another<00:05:12.660> problem<00:05:12.900> with 00:05:13.129 --> 00:05:13.139 align:start position:0% um but another problem with 00:05:13.139 --> 00:05:14.749 align:start position:0% um but another problem with compatibility<00:05:13.680> is<00:05:13.979> if<00:05:14.160> we're<00:05:14.280> going<00:05:14.400> to<00:05:14.460> use<00:05:14.580> a 00:05:14.749 --> 00:05:14.759 align:start position:0% compatibility is if we're going to use a 00:05:14.759 --> 00:05:17.810 align:start position:0% compatibility is if we're going to use a different<00:05:15.020> Key<00:05:16.020> address<00:05:16.280> do<00:05:17.280> we<00:05:17.460> do<00:05:17.580> address 00:05:17.810 --> 00:05:17.820 align:start position:0% different Key address do we do address 00:05:17.820 --> 00:05:19.670 align:start position:0% different Key address do we do address translations<00:05:18.360> to<00:05:18.600> ethereum<00:05:19.020> do<00:05:19.440> we<00:05:19.560> have 00:05:19.670 --> 00:05:19.680 align:start position:0% translations to ethereum do we have 00:05:19.680 --> 00:05:21.350 align:start position:0% translations to ethereum do we have definitions<00:05:20.280> for<00:05:20.460> these<00:05:20.699> we'll<00:05:21.180> probably 00:05:21.350 --> 00:05:21.360 align:start position:0% definitions for these we'll probably 00:05:21.360 --> 00:05:22.790 align:start position:0% definitions for these we'll probably need<00:05:21.540> some<00:05:21.720> sort<00:05:21.840> of<00:05:21.960> a<00:05:22.080> definition<00:05:22.199> for<00:05:22.620> how 00:05:22.790 --> 00:05:22.800 align:start position:0% need some sort of a definition for how 00:05:22.800 --> 00:05:24.830 align:start position:0% need some sort of a definition for how you<00:05:22.860> would<00:05:23.039> take<00:05:23.100> a<00:05:23.280> BLS<00:05:23.699> 12<00:05:23.820> signature<00:05:24.360> into 00:05:24.830 --> 00:05:24.840 align:start position:0% you would take a BLS 12 signature into 00:05:24.840 --> 00:05:26.689 align:start position:0% you would take a BLS 12 signature into an<00:05:25.139> ethereum<00:05:25.500> address<00:05:25.620> if<00:05:26.340> we're<00:05:26.460> going<00:05:26.639> to 00:05:26.689 --> 00:05:26.699 align:start position:0% an ethereum address if we're going to 00:05:26.699 --> 00:05:29.450 align:start position:0% an ethereum address if we're going to adapt<00:05:26.940> that<00:05:27.120> for<00:05:27.300> for<00:05:27.539> various<00:05:28.020> uses 00:05:29.450 --> 00:05:29.460 align:start position:0% adapt that for for various uses 00:05:29.460 --> 00:05:31.430 align:start position:0% adapt that for for various uses um<00:05:29.820> and<00:05:30.360> their<00:05:30.479> biggest<00:05:30.660> problem<00:05:30.960> is<00:05:31.259> that 00:05:31.430 --> 00:05:31.440 align:start position:0% um and their biggest problem is that 00:05:31.440 --> 00:05:33.710 align:start position:0% um and their biggest problem is that ethers.js<00:05:32.400> and<00:05:32.820> some<00:05:33.000> of<00:05:33.060> the<00:05:33.180> other<00:05:33.300> tooling 00:05:33.710 --> 00:05:33.720 align:start position:0% ethers.js and some of the other tooling 00:05:33.720 --> 00:05:35.749 align:start position:0% ethers.js and some of the other tooling when<00:05:34.320> you<00:05:34.440> create<00:05:34.620> a<00:05:34.860> contract<00:05:35.160> from<00:05:35.580> an 00:05:35.749 --> 00:05:35.759 align:start position:0% when you create a contract from an 00:05:35.759 --> 00:05:37.249 align:start position:0% when you create a contract from an account<00:05:35.880> they<00:05:36.660> don't<00:05:36.780> check<00:05:36.960> the<00:05:37.139> return 00:05:37.249 --> 00:05:37.259 align:start position:0% account they don't check the return 00:05:37.259 --> 00:05:38.749 align:start position:0% account they don't check the return value<00:05:37.620> they<00:05:37.860> assume<00:05:38.280> that<00:05:38.340> you're<00:05:38.460> following 00:05:38.749 --> 00:05:38.759 align:start position:0% value they assume that you're following 00:05:38.759 --> 00:05:40.610 align:start position:0% value they assume that you're following proper<00:05:39.180> yellow<00:05:39.300> paper<00:05:39.600> definitions<00:05:40.259> which 00:05:40.610 --> 00:05:40.620 align:start position:0% proper yellow paper definitions which 00:05:40.620 --> 00:05:42.770 align:start position:0% proper yellow paper definitions which for<00:05:40.800> an<00:05:40.979> ethereum<00:05:41.280> tool<00:05:41.520> makes<00:05:41.699> sense<00:05:42.000> but 00:05:42.770 --> 00:05:42.780 align:start position:0% for an ethereum tool makes sense but 00:05:42.780 --> 00:05:44.330 align:start position:0% for an ethereum tool makes sense but with<00:05:42.960> it<00:05:43.139> with<00:05:43.500> the<00:05:43.620> possibility<00:05:44.039> on<00:05:44.220> the 00:05:44.330 --> 00:05:44.340 align:start position:0% with it with the possibility on the 00:05:44.340 --> 00:05:46.249 align:start position:0% with it with the possibility on the horizon<00:05:44.580> that<00:05:44.820> some<00:05:45.000> of<00:05:45.120> these<00:05:45.419> signature 00:05:46.249 --> 00:05:46.259 align:start position:0% horizon that some of these signature 00:05:46.259 --> 00:05:47.870 align:start position:0% horizon that some of these signature algorithms<00:05:46.860> might<00:05:47.039> be<00:05:47.160> changing<00:05:47.400> that's<00:05:47.639> not 00:05:47.870 --> 00:05:47.880 align:start position:0% algorithms might be changing that's not 00:05:47.880 --> 00:05:49.790 align:start position:0% algorithms might be changing that's not an<00:05:48.000> assumption<00:05:48.360> that<00:05:48.539> is<00:05:48.660> safe<00:05:48.900> anymore<00:05:49.080> for 00:05:49.790 --> 00:05:49.800 align:start position:0% an assumption that is safe anymore for 00:05:49.800 --> 00:05:51.409 align:start position:0% an assumption that is safe anymore for these<00:05:49.979> tools<00:05:50.280> to<00:05:50.460> make<00:05:50.580> they<00:05:51.000> should<00:05:51.240> believe 00:05:51.409 --> 00:05:51.419 align:start position:0% these tools to make they should believe 00:05:51.419 --> 00:05:53.810 align:start position:0% these tools to make they should believe what<00:05:51.720> the<00:05:51.900> what<00:05:52.380> the<00:05:52.440> RPC<00:05:52.800> tells<00:05:53.220> them<00:05:53.280> is<00:05:53.639> the 00:05:53.810 --> 00:05:53.820 align:start position:0% what the what the RPC tells them is the 00:05:53.820 --> 00:05:56.570 align:start position:0% what the what the RPC tells them is the new<00:05:53.940> address<00:05:54.060> when<00:05:54.360> it<00:05:54.479> comes<00:05:54.660> back<00:05:54.780> to<00:05:54.960> them 00:05:56.570 --> 00:05:56.580 align:start position:0% new address when it comes back to them 00:05:56.580 --> 00:05:59.090 align:start position:0% new address when it comes back to them another<00:05:57.180> problem<00:05:57.419> is<00:05:57.660> authorization<00:05:58.259> EC 00:05:59.090 --> 00:05:59.100 align:start position:0% another problem is authorization EC 00:05:59.100 --> 00:06:02.270 align:start position:0% another problem is authorization EC recover<00:05:59.520> is<00:06:00.180> used<00:06:00.360> by<00:06:00.539> a<00:06:00.720> lot<00:06:00.780> of<00:06:00.960> contracts<00:06:01.500> to 00:06:02.270 --> 00:06:02.280 align:start position:0% recover is used by a lot of contracts to 00:06:02.280 --> 00:06:04.550 align:start position:0% recover is used by a lot of contracts to authorize<00:06:02.639> messages<00:06:02.940> like<00:06:03.419> 0x<00:06:03.960> to<00:06:04.139> authorize 00:06:04.550 --> 00:06:04.560 align:start position:0% authorize messages like 0x to authorize 00:06:04.560 --> 00:06:07.490 align:start position:0% authorize messages like 0x to authorize the<00:06:04.740> trades<00:06:05.039> some<00:06:05.639> other<00:06:05.880> uh<00:06:06.419> some<00:06:07.020> other<00:06:07.080> Dows 00:06:07.490 --> 00:06:07.500 align:start position:0% the trades some other uh some other Dows 00:06:07.500 --> 00:06:08.870 align:start position:0% the trades some other uh some other Dows use<00:06:07.680> it<00:06:07.860> to<00:06:07.979> validate<00:06:08.340> votes<00:06:08.639> and<00:06:08.759> everything 00:06:08.870 --> 00:06:08.880 align:start position:0% use it to validate votes and everything 00:06:08.880 --> 00:06:10.909 align:start position:0% use it to validate votes and everything like<00:06:09.180> that<00:06:09.300> but<00:06:09.900> this<00:06:10.080> again<00:06:10.259> ties<00:06:10.680> the 00:06:10.909 --> 00:06:10.919 align:start position:0% like that but this again ties the 00:06:10.919 --> 00:06:13.189 align:start position:0% like that but this again ties the account<00:06:11.039> to<00:06:11.400> the<00:06:11.580> key<00:06:11.820> and<00:06:12.479> also<00:06:12.840> approved 00:06:13.189 --> 00:06:13.199 align:start position:0% account to the key and also approved 00:06:13.199 --> 00:06:15.469 align:start position:0% account to the key and also approved includes<00:06:13.560> key<00:06:13.800> rotation 00:06:15.469 --> 00:06:15.479 align:start position:0% includes key rotation 00:06:15.479 --> 00:06:17.570 align:start position:0% includes key rotation um<00:06:15.539> hedera<00:06:16.380> we<00:06:16.500> use<00:06:16.620> this<00:06:16.740> clinch<00:06:17.039> accounts 00:06:17.570 --> 00:06:17.580 align:start position:0% um hedera we use this clinch accounts 00:06:17.580 --> 00:06:18.590 align:start position:0% um hedera we use this clinch accounts which<00:06:17.639> doesn't<00:06:17.820> work<00:06:18.000> well<00:06:18.120> to<00:06:18.300> easily 00:06:18.590 --> 00:06:18.600 align:start position:0% which doesn't work well to easily 00:06:18.600 --> 00:06:20.450 align:start position:0% which doesn't work well to easily recover<00:06:18.840> we<00:06:19.020> have<00:06:19.199> to<00:06:19.259> map<00:06:19.380> in<00:06:19.620> it<00:06:19.800> addressed 00:06:20.450 --> 00:06:20.460 align:start position:0% recover we have to map in it addressed 00:06:20.460 --> 00:06:22.610 align:start position:0% recover we have to map in it addressed to<00:06:20.520> that<00:06:20.639> near<00:06:21.240> uses<00:06:21.720> usernames<00:06:22.319> that<00:06:22.500> you 00:06:22.610 --> 00:06:22.620 align:start position:0% to that near uses usernames that you 00:06:22.620 --> 00:06:24.290 align:start position:0% to that near uses usernames that you have<00:06:22.740> to<00:06:22.800> register<00:06:23.039> ahead<00:06:23.340> of<00:06:23.460> time<00:06:23.580> quite 00:06:24.290 --> 00:06:24.300 align:start position:0% have to register ahead of time quite 00:06:24.300 --> 00:06:26.510 align:start position:0% have to register ahead of time quite different<00:06:24.500> and<00:06:25.500> so<00:06:25.740> we<00:06:25.860> need<00:06:25.979> to<00:06:26.100> have<00:06:26.280> a 00:06:26.510 --> 00:06:26.520 align:start position:0% different and so we need to have a 00:06:26.520 --> 00:06:28.070 align:start position:0% different and so we need to have a different<00:06:26.580> approach<00:06:26.940> to<00:06:27.120> this<00:06:27.360> and<00:06:27.900> we 00:06:28.070 --> 00:06:28.080 align:start position:0% different approach to this and we 00:06:28.080 --> 00:06:30.110 align:start position:0% different approach to this and we probably<00:06:28.259> need<00:06:28.500> some<00:06:28.800> sort<00:06:29.039> of<00:06:29.160> a<00:06:29.460> an<00:06:29.880> account 00:06:30.110 --> 00:06:30.120 align:start position:0% probably need some sort of a an account 00:06:30.120 --> 00:06:32.749 align:start position:0% probably need some sort of a an account authorized<00:06:30.900> pre-compiled<00:06:31.740> to<00:06:32.460> be<00:06:32.520> brought 00:06:32.749 --> 00:06:32.759 align:start position:0% authorized pre-compiled to be brought 00:06:32.759 --> 00:06:34.790 align:start position:0% authorized pre-compiled to be brought into<00:06:32.940> ethereum<00:06:33.900> when<00:06:34.380> we<00:06:34.500> do<00:06:34.620> account 00:06:34.790 --> 00:06:34.800 align:start position:0% into ethereum when we do account 00:06:34.800 --> 00:06:36.350 align:start position:0% into ethereum when we do account abstractions<00:06:35.460> so<00:06:35.580> you<00:06:35.699> can<00:06:35.819> ask<00:06:35.940> a<00:06:36.120> question 00:06:36.350 --> 00:06:36.360 align:start position:0% abstractions so you can ask a question 00:06:36.360 --> 00:06:39.290 align:start position:0% abstractions so you can ask a question of<00:06:36.960> here's<00:06:37.380> a<00:06:37.560> address<00:06:37.800> here's<00:06:38.699> the<00:06:38.819> signature 00:06:39.290 --> 00:06:39.300 align:start position:0% of here's a address here's the signature 00:06:39.300 --> 00:06:42.230 align:start position:0% of here's a address here's the signature and<00:06:39.960> here's<00:06:40.259> the<00:06:40.380> here's<00:06:40.740> what<00:06:40.860> they<00:06:40.979> signed 00:06:42.230 --> 00:06:42.240 align:start position:0% and here's the here's what they signed 00:06:42.240 --> 00:06:44.450 align:start position:0% and here's the here's what they signed um is<00:06:42.960> it<00:06:43.080> authorized<00:06:43.620> and<00:06:43.979> then<00:06:44.100> just<00:06:44.280> return 00:06:44.450 --> 00:06:44.460 align:start position:0% um is it authorized and then just return 00:06:44.460 --> 00:06:46.550 align:start position:0% um is it authorized and then just return yes<00:06:44.759> or<00:06:44.940> no<00:06:45.120> so<00:06:45.780> I<00:06:45.900> think<00:06:46.020> you<00:06:46.199> know<00:06:46.259> that<00:06:46.440> would 00:06:46.550 --> 00:06:46.560 align:start position:0% yes or no so I think you know that would 00:06:46.560 --> 00:06:48.529 align:start position:0% yes or no so I think you know that would help<00:06:46.740> us<00:06:46.919> continue<00:06:47.220> to<00:06:47.520> keep<00:06:47.639> PC<00:06:47.940> recovery<00:06:48.300> as 00:06:48.529 --> 00:06:48.539 align:start position:0% help us continue to keep PC recovery as 00:06:48.539 --> 00:06:50.270 align:start position:0% help us continue to keep PC recovery as a<00:06:48.600> primitive<00:06:48.960> and<00:06:49.440> move<00:06:49.620> the<00:06:49.800> questions<00:06:49.919> about 00:06:50.270 --> 00:06:50.280 align:start position:0% a primitive and move the questions about 00:06:50.280 --> 00:06:52.850 align:start position:0% a primitive and move the questions about am<00:06:50.580> I<00:06:50.759> authorized<00:06:51.360> into<00:06:51.780> a<00:06:51.960> pre-compile<00:06:52.440> that 00:06:52.850 --> 00:06:52.860 align:start position:0% am I authorized into a pre-compile that 00:06:52.860 --> 00:06:55.309 align:start position:0% am I authorized into a pre-compile that has<00:06:53.039> deep<00:06:53.220> integration<00:06:53.639> with<00:06:53.880> the<00:06:54.000> system 00:06:55.309 --> 00:06:55.319 align:start position:0% has deep integration with the system 00:06:55.319 --> 00:06:57.560 align:start position:0% has deep integration with the system and<00:06:55.800> finally<00:06:56.160> account<00:06:56.340> abstraction 00:06:57.560 --> 00:06:57.570 align:start position:0% and finally account abstraction 00:06:57.570 --> 00:06:57.890 align:start position:0% and finally account abstraction [Music] 00:06:57.890 --> 00:06:57.900 align:start position:0% [Music] 00:06:57.900 --> 00:06:58.670 align:start position:0% [Music] um 00:06:58.670 --> 00:06:58.680 align:start position:0% um 00:06:58.680 --> 00:07:01.010 align:start position:0% um one<00:06:59.280> thing<00:06:59.460> I<00:06:59.699> we<00:07:00.000> should<00:07:00.180> learn<00:07:00.300> from<00:07:00.419> hedera 00:07:01.010 --> 00:07:01.020 align:start position:0% one thing I we should learn from hedera 00:07:01.020 --> 00:07:02.809 align:start position:0% one thing I we should learn from hedera on<00:07:01.080> this<00:07:01.259> is<00:07:01.740> hedera<00:07:02.220> counts<00:07:02.460> that<00:07:02.520> used<00:07:02.699> to 00:07:02.809 --> 00:07:02.819 align:start position:0% on this is hedera counts that used to 00:07:02.819 --> 00:07:04.430 align:start position:0% on this is hedera counts that used to have<00:07:02.880> to<00:07:03.000> create<00:07:03.120> them<00:07:03.479> before<00:07:04.020> you<00:07:04.319> could 00:07:04.430 --> 00:07:04.440 align:start position:0% have to create them before you could 00:07:04.440 --> 00:07:06.710 align:start position:0% have to create them before you could send<00:07:04.620> crypto<00:07:04.979> to<00:07:05.160> them<00:07:05.340> which<00:07:05.940> presented<00:07:06.419> lots 00:07:06.710 --> 00:07:06.720 align:start position:0% send crypto to them which presented lots 00:07:06.720 --> 00:07:08.809 align:start position:0% send crypto to them which presented lots of<00:07:06.780> problems<00:07:07.199> for<00:07:07.620> exchanges<00:07:08.400> creating<00:07:08.699> new 00:07:08.809 --> 00:07:08.819 align:start position:0% of problems for exchanges creating new 00:07:08.819 --> 00:07:10.189 align:start position:0% of problems for exchanges creating new accounts<00:07:09.180> for<00:07:09.300> customers<00:07:09.600> or<00:07:09.840> for<00:07:10.020> somebody 00:07:10.189 --> 00:07:10.199 align:start position:0% accounts for customers or for somebody 00:07:10.199 --> 00:07:12.350 align:start position:0% accounts for customers or for somebody saying<00:07:10.620> hey<00:07:10.740> send<00:07:11.340> it<00:07:11.520> to<00:07:11.639> this<00:07:11.759> send<00:07:12.060> it<00:07:12.240> to 00:07:12.350 --> 00:07:12.360 align:start position:0% saying hey send it to this send it to 00:07:12.360 --> 00:07:14.150 align:start position:0% saying hey send it to this send it to this<00:07:12.479> public<00:07:12.660> key<00:07:12.900> you'd<00:07:13.740> have<00:07:13.860> to<00:07:13.919> have<00:07:14.039> the 00:07:14.150 --> 00:07:14.160 align:start position:0% this public key you'd have to have the 00:07:14.160 --> 00:07:15.469 align:start position:0% this public key you'd have to have the account<00:07:14.280> created<00:07:14.699> before<00:07:14.880> anybody<00:07:15.300> could 00:07:15.469 --> 00:07:15.479 align:start position:0% account created before anybody could 00:07:15.479 --> 00:07:17.090 align:start position:0% account created before anybody could send<00:07:15.660> you<00:07:15.780> your<00:07:15.900> nfts<00:07:16.380> or<00:07:16.500> your<00:07:16.620> crypto<00:07:16.860> or 00:07:17.090 --> 00:07:17.100 align:start position:0% send you your nfts or your crypto or 00:07:17.100 --> 00:07:19.370 align:start position:0% send you your nfts or your crypto or anything<00:07:17.280> so<00:07:18.000> hedera<00:07:18.539> introduced<00:07:19.020> a<00:07:19.139> system 00:07:19.370 --> 00:07:19.380 align:start position:0% anything so hedera introduced a system 00:07:19.380 --> 00:07:21.290 align:start position:0% anything so hedera introduced a system where<00:07:20.039> you<00:07:20.160> could<00:07:20.280> have<00:07:20.460> an<00:07:20.639> aliasp<00:07:21.120> account 00:07:21.290 --> 00:07:21.300 align:start position:0% where you could have an aliasp account 00:07:21.300 --> 00:07:22.370 align:start position:0% where you could have an aliasp account and<00:07:21.599> we<00:07:21.660> would<00:07:21.720> create<00:07:21.900> the<00:07:22.020> account<00:07:22.139> under 00:07:22.370 --> 00:07:22.380 align:start position:0% and we would create the account under 00:07:22.380 --> 00:07:23.809 align:start position:0% and we would create the account under the<00:07:22.560> covers<00:07:22.800> for<00:07:22.919> you<00:07:23.039> late<00:07:23.280> the<00:07:23.520> moment<00:07:23.639> we 00:07:23.809 --> 00:07:23.819 align:start position:0% the covers for you late the moment we 00:07:23.819 --> 00:07:25.070 align:start position:0% the covers for you late the moment we need<00:07:23.940> it 00:07:25.070 --> 00:07:25.080 align:start position:0% need it 00:07:25.080 --> 00:07:26.570 align:start position:0% need it um and<00:07:25.680> the<00:07:25.800> lesson<00:07:26.039> here<00:07:26.160> is<00:07:26.280> from<00:07:26.460> the 00:07:26.570 --> 00:07:26.580 align:start position:0% um and the lesson here is from the 00:07:26.580 --> 00:07:28.610 align:start position:0% um and the lesson here is from the account<00:07:26.699> abstraction<00:07:27.240> this<00:07:28.199> was<00:07:28.319> a<00:07:28.500> bad 00:07:28.610 --> 00:07:28.620 align:start position:0% account abstraction this was a bad 00:07:28.620 --> 00:07:30.050 align:start position:0% account abstraction this was a bad experience<00:07:28.979> which<00:07:29.220> is<00:07:29.400> why<00:07:29.520> we<00:07:29.699> had<00:07:29.819> to<00:07:29.940> add 00:07:30.050 --> 00:07:30.060 align:start position:0% experience which is why we had to add 00:07:30.060 --> 00:07:32.210 align:start position:0% experience which is why we had to add the<00:07:30.300> aliases<00:07:30.900> if<00:07:31.800> we're<00:07:31.919> going<00:07:32.039> to<00:07:32.160> have 00:07:32.210 --> 00:07:32.220 align:start position:0% the aliases if we're going to have 00:07:32.220 --> 00:07:33.589 align:start position:0% the aliases if we're going to have account<00:07:32.340> abstractions<00:07:32.940> we<00:07:33.180> need<00:07:33.240> to<00:07:33.360> have<00:07:33.479> a 00:07:33.589 --> 00:07:33.599 align:start position:0% account abstractions we need to have a 00:07:33.599 --> 00:07:35.029 align:start position:0% account abstractions we need to have a mechanism<00:07:33.960> that<00:07:34.259> you<00:07:34.380> could<00:07:34.500> that<00:07:34.740> you<00:07:34.860> can't 00:07:35.029 --> 00:07:35.039 align:start position:0% mechanism that you could that you can't 00:07:35.039 --> 00:07:37.790 align:start position:0% mechanism that you could that you can't convert<00:07:35.580> an<00:07:36.060> existing<00:07:36.419> end<00:07:36.599> user<00:07:37.020> account<00:07:37.139> to 00:07:37.790 --> 00:07:37.800 align:start position:0% convert an existing end user account to 00:07:37.800 --> 00:07:39.469 align:start position:0% convert an existing end user account to an<00:07:37.919> account<00:07:38.099> abstraction<00:07:38.520> account<00:07:38.759> so<00:07:39.300> people 00:07:39.469 --> 00:07:39.479 align:start position:0% an account abstraction account so people 00:07:39.479 --> 00:07:41.089 align:start position:0% an account abstraction account so people can<00:07:39.720> still<00:07:39.900> send<00:07:40.139> you<00:07:40.259> stuff<00:07:40.500> ahead<00:07:40.860> of<00:07:40.979> time 00:07:41.089 --> 00:07:41.099 align:start position:0% can still send you stuff ahead of time 00:07:41.099 --> 00:07:43.490 align:start position:0% can still send you stuff ahead of time before<00:07:41.639> you<00:07:41.819> create<00:07:42.000> your<00:07:42.240> contract 00:07:43.490 --> 00:07:43.500 align:start position:0% before you create your contract 00:07:43.500 --> 00:07:45.170 align:start position:0% before you create your contract um hedera's<00:07:44.220> got<00:07:44.280> a<00:07:44.400> unique<00:07:44.699> process<00:07:44.940> called 00:07:45.170 --> 00:07:45.180 align:start position:0% um hedera's got a unique process called 00:07:45.180 --> 00:07:46.610 align:start position:0% um hedera's got a unique process called Hollow<00:07:45.539> accounts<00:07:45.960> that<00:07:46.020> we're<00:07:46.139> implementing 00:07:46.610 --> 00:07:46.620 align:start position:0% Hollow accounts that we're implementing 00:07:46.620 --> 00:07:48.350 align:start position:0% Hollow accounts that we're implementing here<00:07:46.740> shortly<00:07:47.099> where<00:07:47.699> you<00:07:47.819> can<00:07:47.940> just<00:07:48.060> set<00:07:48.180> it 00:07:48.350 --> 00:07:48.360 align:start position:0% here shortly where you can just set it 00:07:48.360 --> 00:07:50.029 align:start position:0% here shortly where you can just set it with<00:07:48.419> partial<00:07:48.780> information<00:07:48.960> and<00:07:49.740> then<00:07:49.860> fill 00:07:50.029 --> 00:07:50.039 align:start position:0% with partial information and then fill 00:07:50.039 --> 00:07:51.770 align:start position:0% with partial information and then fill it<00:07:50.220> out<00:07:50.340> later<00:07:50.580> and<00:07:51.120> that's<00:07:51.240> kind<00:07:51.479> of<00:07:51.599> what 00:07:51.770 --> 00:07:51.780 align:start position:0% it out later and that's kind of what 00:07:51.780 --> 00:07:52.790 align:start position:0% it out later and that's kind of what would<00:07:52.020> need<00:07:52.199> to<00:07:52.319> happen<00:07:52.440> in<00:07:52.680> account 00:07:52.790 --> 00:07:52.800 align:start position:0% would need to happen in account 00:07:52.800 --> 00:07:55.129 align:start position:0% would need to happen in account abstraction<00:07:53.340> so<00:07:53.819> I'm<00:07:54.000> a<00:07:54.120> draft<00:07:54.240> some<00:07:54.660> drafts 00:07:55.129 --> 00:07:55.139 align:start position:0% abstraction so I'm a draft some drafts 00:07:55.139 --> 00:07:57.050 align:start position:0% abstraction so I'm a draft some drafts have<00:07:55.259> this<00:07:55.440> feature<00:07:55.740> some<00:07:56.160> drafts<00:07:56.639> don't<00:07:56.880> have 00:07:57.050 --> 00:07:57.060 align:start position:0% have this feature some drafts don't have 00:07:57.060 --> 00:07:59.210 align:start position:0% have this feature some drafts don't have that<00:07:57.240> feature<00:07:57.660> of<00:07:57.900> account<00:07:58.080> abstractions<00:07:58.620> so 00:07:59.210 --> 00:07:59.220 align:start position:0% that feature of account abstractions so 00:07:59.220 --> 00:08:01.550 align:start position:0% that feature of account abstractions so whatever<00:07:59.699> approach<00:08:00.180> we<00:08:00.360> take<00:08:00.599> I<00:08:01.259> would<00:08:01.440> really 00:08:01.550 --> 00:08:01.560 align:start position:0% whatever approach we take I would really 00:08:01.560 --> 00:08:04.249 align:start position:0% whatever approach we take I would really want<00:08:01.919> to<00:08:02.039> be<00:08:02.580> able<00:08:02.699> to<00:08:02.880> convert<00:08:03.360> an<00:08:03.780> end<00:08:03.900> user 00:08:04.249 --> 00:08:04.259 align:start position:0% want to be able to convert an end user 00:08:04.259 --> 00:08:07.309 align:start position:0% want to be able to convert an end user account<00:08:04.440> into<00:08:05.479> an<00:08:06.479> existing<00:08:06.900> externally 00:08:07.309 --> 00:08:07.319 align:start position:0% account into an existing externally 00:08:07.319 --> 00:08:08.990 align:start position:0% account into an existing externally owned<00:08:07.620> account<00:08:07.740> into<00:08:08.220> an<00:08:08.880> account 00:08:08.990 --> 00:08:09.000 align:start position:0% owned account into an account 00:08:09.000 --> 00:08:10.189 align:start position:0% owned account into an account abstraction<00:08:09.479> account<00:08:09.720> rather<00:08:10.080> than 00:08:10.189 --> 00:08:10.199 align:start position:0% abstraction account rather than 00:08:10.199 --> 00:08:12.409 align:start position:0% abstraction account rather than requiring<00:08:10.620> them<00:08:10.800> always<00:08:11.039> to<00:08:11.340> start<00:08:11.520> from<00:08:11.880> a 00:08:12.409 --> 00:08:12.419 align:start position:0% requiring them always to start from a 00:08:12.419 --> 00:08:14.029 align:start position:0% requiring them always to start from a contract<00:08:12.720> deploy 00:08:14.029 --> 00:08:14.039 align:start position:0% contract deploy 00:08:14.039 --> 00:08:15.890 align:start position:0% contract deploy so<00:08:14.400> that<00:08:14.520> covers<00:08:14.819> it<00:08:15.000> mostly<00:08:15.240> for<00:08:15.419> accounts 00:08:15.890 --> 00:08:15.900 align:start position:0% so that covers it mostly for accounts 00:08:15.900 --> 00:08:18.230 align:start position:0% so that covers it mostly for accounts the<00:08:16.620> next<00:08:16.740> area<00:08:16.979> is<00:08:17.340> the<00:08:17.520> ethereum<00:08:17.880> virtual 00:08:18.230 --> 00:08:18.240 align:start position:0% the next area is the ethereum virtual 00:08:18.240 --> 00:08:19.790 align:start position:0% the next area is the ethereum virtual machine<00:08:18.479> even<00:08:19.080> though<00:08:19.259> you<00:08:19.379> bring<00:08:19.560> in<00:08:19.680> the 00:08:19.790 --> 00:08:19.800 align:start position:0% machine even though you bring in the 00:08:19.800 --> 00:08:21.290 align:start position:0% machine even though you bring in the same<00:08:19.919> Library<00:08:20.099> there's<00:08:20.460> always<00:08:20.699> rough<00:08:21.000> edges 00:08:21.290 --> 00:08:21.300 align:start position:0% same Library there's always rough edges 00:08:21.300 --> 00:08:23.089 align:start position:0% same Library there's always rough edges and<00:08:21.419> Corners<00:08:21.720> that<00:08:21.840> you<00:08:21.960> need<00:08:22.080> to<00:08:22.259> deal<00:08:22.379> with 00:08:23.089 --> 00:08:23.099 align:start position:0% and Corners that you need to deal with 00:08:23.099 --> 00:08:26.589 align:start position:0% and Corners that you need to deal with one<00:08:23.879> is<00:08:24.000> the<00:08:24.180> issue<00:08:25.020> of<00:08:25.139> ergonomics 00:08:26.589 --> 00:08:26.599 align:start position:0% one is the issue of ergonomics 00:08:26.599 --> 00:08:28.969 align:start position:0% one is the issue of ergonomics and<00:08:27.599> pre-compiled<00:08:28.259> contracts<00:08:28.560> is<00:08:28.740> the<00:08:28.860> way 00:08:28.969 --> 00:08:28.979 align:start position:0% and pre-compiled contracts is the way 00:08:28.979 --> 00:08:30.770 align:start position:0% and pre-compiled contracts is the way that<00:08:29.099> most<00:08:29.280> change<00:08:29.460> saw<00:08:29.759> this<00:08:30.000> issue<00:08:30.300> what<00:08:30.599> if 00:08:30.770 --> 00:08:30.780 align:start position:0% that most change saw this issue what if 00:08:30.780 --> 00:08:31.969 align:start position:0% that most change saw this issue what if you<00:08:30.840> need<00:08:30.960> to<00:08:31.080> do<00:08:31.199> stuff<00:08:31.379> that<00:08:31.560> you<00:08:31.680> can't<00:08:31.800> do 00:08:31.969 --> 00:08:31.979 align:start position:0% you need to do stuff that you can't do 00:08:31.979 --> 00:08:33.889 align:start position:0% you need to do stuff that you can't do inside<00:08:32.159> the<00:08:32.399> evm<00:08:32.820> what<00:08:33.000> if<00:08:33.120> you<00:08:33.180> need<00:08:33.300> a<00:08:33.479> queue 00:08:33.889 --> 00:08:33.899 align:start position:0% inside the evm what if you need a queue 00:08:33.899 --> 00:08:36.589 align:start position:0% inside the evm what if you need a queue up<00:08:33.959> a<00:08:34.320> layer<00:08:34.800> 2<00:08:34.919> withdrawal<00:08:35.580> what<00:08:36.120> if<00:08:36.300> you<00:08:36.419> need 00:08:36.589 --> 00:08:36.599 align:start position:0% up a layer 2 withdrawal what if you need 00:08:36.599 --> 00:08:38.029 align:start position:0% up a layer 2 withdrawal what if you need to<00:08:36.719> interact<00:08:37.140> with<00:08:37.260> your<00:08:37.440> native<00:08:37.620> token 00:08:38.029 --> 00:08:38.039 align:start position:0% to interact with your native token 00:08:38.039 --> 00:08:40.190 align:start position:0% to interact with your native token system<00:08:38.279> what<00:08:39.000> if<00:08:39.120> you<00:08:39.240> need<00:08:39.360> to<00:08:39.479> change<00:08:39.899> your 00:08:40.190 --> 00:08:40.200 align:start position:0% system what if you need to change your 00:08:40.200 --> 00:08:41.389 align:start position:0% system what if you need to change your account<00:08:40.320> information<00:08:40.680> from<00:08:41.099> a<00:08:41.279> smart 00:08:41.389 --> 00:08:41.399 align:start position:0% account information from a smart 00:08:41.399 --> 00:08:44.750 align:start position:0% account information from a smart contract<00:08:42.260> lots<00:08:43.260> of<00:08:43.320> lots<00:08:43.800> of<00:08:43.860> smart<00:08:44.159> contracts 00:08:44.750 --> 00:08:44.760 align:start position:0% contract lots of lots of smart contracts 00:08:44.760 --> 00:08:47.150 align:start position:0% contract lots of lots of smart contracts lots<00:08:45.240> of<00:08:45.360> uh<00:08:46.020> different<00:08:46.500> blockchains<00:08:47.100> have 00:08:47.150 --> 00:08:47.160 align:start position:0% lots of uh different blockchains have 00:08:47.160 --> 00:08:48.230 align:start position:0% lots of uh different blockchains have different<00:08:47.339> addresses<00:08:47.700> for<00:08:47.880> a<00:08:48.000> lot<00:08:48.060> of<00:08:48.120> their 00:08:48.230 --> 00:08:48.240 align:start position:0% different addresses for a lot of their 00:08:48.240 --> 00:08:50.570 align:start position:0% different addresses for a lot of their pre-compiles<00:08:48.959> an<00:08:49.860> interesting<00:08:50.220> one<00:08:50.339> down 00:08:50.570 --> 00:08:50.580 align:start position:0% pre-compiles an interesting one down 00:08:50.580 --> 00:08:52.670 align:start position:0% pre-compiles an interesting one down here<00:08:50.760> is<00:08:50.880> stello<00:08:51.300> this<00:08:52.080> is<00:08:52.140> actually<00:08:52.380> the 00:08:52.670 --> 00:08:52.680 align:start position:0% here is stello this is actually the 00:08:52.680 --> 00:08:54.470 align:start position:0% here is stello this is actually the pre-compile<00:08:53.160> that<00:08:53.399> was<00:08:53.519> the<00:08:53.640> BLS<00:08:54.000> signatures 00:08:54.470 --> 00:08:54.480 align:start position:0% pre-compile that was the BLS signatures 00:08:54.480 --> 00:08:56.329 align:start position:0% pre-compile that was the BLS signatures that<00:08:54.899> was<00:08:55.019> in<00:08:55.140> Berlin<00:08:55.500> before<00:08:55.680> it<00:08:55.860> was<00:08:56.040> removed 00:08:56.329 --> 00:08:56.339 align:start position:0% that was in Berlin before it was removed 00:08:56.339 --> 00:08:58.490 align:start position:0% that was in Berlin before it was removed before<00:08:56.459> we<00:08:56.700> shipped<00:08:56.940> it<00:08:57.060> to<00:08:57.120> test<00:08:57.300> Nets<00:08:57.779> they 00:08:58.490 --> 00:08:58.500 align:start position:0% before we shipped it to test Nets they 00:08:58.500 --> 00:09:00.290 align:start position:0% before we shipped it to test Nets they just<00:08:58.680> the<00:08:58.920> difference<00:08:59.100> is<00:08:59.339> there<00:08:59.640> they<00:09:00.060> put<00:09:00.180> it 00:09:00.290 --> 00:09:00.300 align:start position:0% just the difference is there they put it 00:09:00.300 --> 00:09:02.150 align:start position:0% just the difference is there they put it at<00:09:00.480> a<00:09:00.540> different<00:09:00.660> address<00:09:00.899> which<00:09:01.860> I<00:09:02.040> think 00:09:02.150 --> 00:09:02.160 align:start position:0% at a different address which I think 00:09:02.160 --> 00:09:04.070 align:start position:0% at a different address which I think underscores<00:09:02.760> what<00:09:03.000> the<00:09:03.180> what<00:09:03.420> my<00:09:03.600> main<00:09:03.779> ask 00:09:04.070 --> 00:09:04.080 align:start position:0% underscores what the what my main ask 00:09:04.080 --> 00:09:05.690 align:start position:0% underscores what the what my main ask here<00:09:04.320> is<00:09:04.800> that<00:09:04.980> we<00:09:05.100> probably<00:09:05.279> need<00:09:05.519> to 00:09:05.690 --> 00:09:05.700 align:start position:0% here is that we probably need to 00:09:05.700 --> 00:09:08.269 align:start position:0% here is that we probably need to organize<00:09:06.420> a<00:09:06.899> registry<00:09:07.320> of<00:09:07.620> pre-compiled 00:09:08.269 --> 00:09:08.279 align:start position:0% organize a registry of pre-compiled 00:09:08.279 --> 00:09:09.949 align:start position:0% organize a registry of pre-compiled contracts<00:09:08.640> that<00:09:08.820> all<00:09:09.000> chains<00:09:09.300> and<00:09:09.420> layer<00:09:09.600> 2<00:09:09.779> is 00:09:09.949 --> 00:09:09.959 align:start position:0% contracts that all chains and layer 2 is 00:09:09.959 --> 00:09:10.850 align:start position:0% contracts that all chains and layer 2 is used 00:09:10.850 --> 00:09:10.860 align:start position:0% used 00:09:10.860 --> 00:09:12.170 align:start position:0% used for<00:09:11.279> one<00:09:11.459> to<00:09:11.700> make<00:09:11.760> sure<00:09:11.880> there's<00:09:12.000> no 00:09:12.170 --> 00:09:12.180 align:start position:0% for one to make sure there's no 00:09:12.180 --> 00:09:14.329 align:start position:0% for one to make sure there's no collisions<00:09:12.600> and<00:09:12.839> for<00:09:13.019> two<00:09:13.200> to<00:09:13.740> give<00:09:13.980> proper 00:09:14.329 --> 00:09:14.339 align:start position:0% collisions and for two to give proper 00:09:14.339 --> 00:09:16.430 align:start position:0% collisions and for two to give proper documentation<00:09:14.880> and<00:09:15.180> utility<00:09:15.540> for<00:09:16.200> smart 00:09:16.430 --> 00:09:16.440 align:start position:0% documentation and utility for smart 00:09:16.440 --> 00:09:17.810 align:start position:0% documentation and utility for smart contract<00:09:16.800> writers<00:09:17.160> so<00:09:17.279> they<00:09:17.399> know<00:09:17.519> how<00:09:17.640> to 00:09:17.810 --> 00:09:17.820 align:start position:0% contract writers so they know how to 00:09:17.820 --> 00:09:19.370 align:start position:0% contract writers so they know how to call<00:09:17.940> these<00:09:18.180> contracts<00:09:18.540> within<00:09:18.839> it<00:09:19.019> in<00:09:19.260> kind 00:09:19.370 --> 00:09:19.380 align:start position:0% call these contracts within it in kind 00:09:19.380 --> 00:09:20.810 align:start position:0% call these contracts within it in kind of<00:09:19.500> a<00:09:19.560> centralized<00:09:19.980> place 00:09:20.810 --> 00:09:20.820 align:start position:0% of a centralized place 00:09:20.820 --> 00:09:22.790 align:start position:0% of a centralized place but<00:09:21.240> I<00:09:21.420> also<00:09:21.600> want<00:09:21.720> to<00:09:21.899> pitch<00:09:22.080> a<00:09:22.500> language 00:09:22.790 --> 00:09:22.800 align:start position:0% but I also want to pitch a language 00:09:22.800 --> 00:09:25.730 align:start position:0% but I also want to pitch a language change<00:09:23.220> as<00:09:24.000> for<00:09:24.360> these<00:09:24.600> contracts<00:09:25.080> there's 00:09:25.730 --> 00:09:25.740 align:start position:0% change as for these contracts there's 00:09:25.740 --> 00:09:26.750 align:start position:0% change as for these contracts there's going<00:09:25.980> to<00:09:25.980> be<00:09:26.100> a<00:09:26.160> difference<00:09:26.220> between<00:09:26.459> a 00:09:26.750 --> 00:09:26.760 align:start position:0% going to be a difference between a 00:09:26.760 --> 00:09:28.250 align:start position:0% going to be a difference between a pre-compiled<00:09:27.300> contract<00:09:27.660> which<00:09:27.959> is<00:09:28.019> a 00:09:28.250 --> 00:09:28.260 align:start position:0% pre-compiled contract which is a 00:09:28.260 --> 00:09:29.690 align:start position:0% pre-compiled contract which is a contract<00:09:28.560> that<00:09:28.860> you<00:09:29.220> could<00:09:29.279> do<00:09:29.459> everything 00:09:29.690 --> 00:09:29.700 align:start position:0% contract that you could do everything 00:09:29.700 --> 00:09:32.150 align:start position:0% contract that you could do everything within<00:09:30.120> the<00:09:30.240> evm<00:09:30.720> most<00:09:31.380> crypto<00:09:31.680> Primitives 00:09:32.150 --> 00:09:32.160 align:start position:0% within the evm most crypto Primitives 00:09:32.160 --> 00:09:33.949 align:start position:0% within the evm most crypto Primitives would<00:09:32.339> cover<00:09:32.519> into<00:09:32.700> this<00:09:33.000> you<00:09:33.600> just<00:09:33.720> can't<00:09:33.839> do 00:09:33.949 --> 00:09:33.959 align:start position:0% would cover into this you just can't do 00:09:33.959 --> 00:09:36.290 align:start position:0% would cover into this you just can't do it<00:09:34.080> efficiently<00:09:34.500> you<00:09:34.800> can't<00:09:34.920> do<00:09:35.160> it<00:09:35.339> the<00:09:36.000> speed 00:09:36.290 --> 00:09:36.300 align:start position:0% it efficiently you can't do it the speed 00:09:36.300 --> 00:09:38.150 align:start position:0% it efficiently you can't do it the speed wise<00:09:36.600> it<00:09:36.899> costs<00:09:37.200> too<00:09:37.380> much<00:09:37.560> so<00:09:37.980> you 00:09:38.150 --> 00:09:38.160 align:start position:0% wise it costs too much so you 00:09:38.160 --> 00:09:39.949 align:start position:0% wise it costs too much so you pre-compile<00:09:38.700> it<00:09:38.880> into<00:09:39.060> a<00:09:39.300> library<00:09:39.420> and<00:09:39.720> you<00:09:39.839> do 00:09:39.949 --> 00:09:39.959 align:start position:0% pre-compile it into a library and you do 00:09:39.959 --> 00:09:41.449 align:start position:0% pre-compile it into a library and you do it<00:09:40.080> cheaper<00:09:40.380> and<00:09:40.500> faster 00:09:41.449 --> 00:09:41.459 align:start position:0% it cheaper and faster 00:09:41.459 --> 00:09:43.130 align:start position:0% it cheaper and faster the<00:09:41.880> other<00:09:42.000> type<00:09:42.180> of<00:09:42.360> contract<00:09:42.720> would<00:09:42.899> be<00:09:43.019> a 00:09:43.130 --> 00:09:43.140 align:start position:0% the other type of contract would be a 00:09:43.140 --> 00:09:44.509 align:start position:0% the other type of contract would be a system<00:09:43.260> contract<00:09:43.740> where<00:09:43.980> you're<00:09:44.160> breaking 00:09:44.509 --> 00:09:44.519 align:start position:0% system contract where you're breaking 00:09:44.519 --> 00:09:46.550 align:start position:0% system contract where you're breaking the<00:09:44.640> layers<00:09:45.060> of<00:09:45.779> the<00:09:45.899> of<00:09:46.019> the<00:09:46.200> ethereum 00:09:46.550 --> 00:09:46.560 align:start position:0% the layers of the of the ethereum 00:09:46.560 --> 00:09:47.870 align:start position:0% the layers of the of the ethereum virtual<00:09:46.860> machine<00:09:47.040> and<00:09:47.279> going<00:09:47.459> and<00:09:47.640> doing 00:09:47.870 --> 00:09:47.880 align:start position:0% virtual machine and going and doing 00:09:47.880 --> 00:09:49.670 align:start position:0% virtual machine and going and doing things<00:09:48.240> into<00:09:48.899> different<00:09:49.200> parts<00:09:49.380> of<00:09:49.560> the 00:09:49.670 --> 00:09:49.680 align:start position:0% things into different parts of the 00:09:49.680 --> 00:09:51.829 align:start position:0% things into different parts of the system<00:09:49.860> that<00:09:50.160> you<00:09:50.279> can't<00:09:50.339> do<00:09:50.519> in<00:09:50.640> the<00:09:50.760> evm<00:09:51.180> so 00:09:51.829 --> 00:09:51.839 align:start position:0% system that you can't do in the evm so 00:09:51.839 --> 00:09:53.210 align:start position:0% system that you can't do in the evm so most<00:09:51.959> of<00:09:52.140> these<00:09:52.260> contracts<00:09:52.620> up<00:09:52.800> here<00:09:52.920> I<00:09:53.040> would 00:09:53.210 --> 00:09:53.220 align:start position:0% most of these contracts up here I would 00:09:53.220 --> 00:09:55.850 align:start position:0% most of these contracts up here I would call<00:09:53.339> system<00:09:53.580> contracts<00:09:54.240> and<00:09:54.959> only<00:09:55.200> the<00:09:55.560> the 00:09:55.850 --> 00:09:55.860 align:start position:0% call system contracts and only the the 00:09:55.860 --> 00:09:57.650 align:start position:0% call system contracts and only the the BLS<00:09:56.519> signatures<00:09:56.940> I<00:09:57.120> would<00:09:57.180> really<00:09:57.360> call<00:09:57.540> a 00:09:57.650 --> 00:09:57.660 align:start position:0% BLS signatures I would really call a 00:09:57.660 --> 00:10:00.530 align:start position:0% BLS signatures I would really call a pre-compiled<00:09:58.260> contract<00:09:58.560> on<00:09:58.740> this<00:09:58.920> list 00:10:00.530 --> 00:10:00.540 align:start position:0% pre-compiled contract on this list 00:10:00.540 --> 00:10:02.210 align:start position:0% pre-compiled contract on this list um a<00:10:00.720> little<00:10:00.779> bit<00:10:00.959> here<00:10:01.200> we<00:10:01.860> had<00:10:01.920> to<00:10:02.100> do 00:10:02.210 --> 00:10:02.220 align:start position:0% um a little bit here we had to do 00:10:02.220 --> 00:10:03.710 align:start position:0% um a little bit here we had to do something<00:10:02.339> different<00:10:02.580> instead<00:10:02.940> of<00:10:03.000> randow<00:10:03.540> we 00:10:03.710 --> 00:10:03.720 align:start position:0% something different instead of randow we 00:10:03.720 --> 00:10:05.389 align:start position:0% something different instead of randow we used<00:10:03.839> a<00:10:04.019> different<00:10:04.200> hash 00:10:05.389 --> 00:10:05.399 align:start position:0% used a different hash 00:10:05.399 --> 00:10:07.070 align:start position:0% used a different hash um<00:10:05.459> and<00:10:05.640> hedera<00:10:06.180> has<00:10:06.300> a<00:10:06.420> very<00:10:06.540> complex<00:10:06.779> P 00:10:07.070 --> 00:10:07.080 align:start position:0% um and hedera has a very complex P 00:10:07.080 --> 00:10:09.889 align:start position:0% um and hedera has a very complex P system<00:10:07.380> it<00:10:08.220> works<00:10:08.820> um<00:10:08.820> you<00:10:09.000> just<00:10:09.180> librarize<00:10:09.660> it 00:10:09.889 --> 00:10:09.899 align:start position:0% system it works um you just librarize it 00:10:09.899 --> 00:10:11.810 align:start position:0% system it works um you just librarize it gets<00:10:10.260> lots<00:10:10.500> of<00:10:10.560> tests 00:10:11.810 --> 00:10:11.820 align:start position:0% gets lots of tests 00:10:11.820 --> 00:10:13.190 align:start position:0% gets lots of tests um<00:10:11.880> and<00:10:12.060> the<00:10:12.180> takeaway<00:10:12.480> from<00:10:12.660> that<00:10:12.839> is<00:10:13.080> that 00:10:13.190 --> 00:10:13.200 align:start position:0% um and the takeaway from that is that 00:10:13.200 --> 00:10:15.949 align:start position:0% um and the takeaway from that is that multi-dimensional<00:10:13.860> 1559<00:10:14.580> much<00:10:15.480> simpler<00:10:15.839> than 00:10:15.949 --> 00:10:15.959 align:start position:0% multi-dimensional 1559 much simpler than 00:10:15.959 --> 00:10:17.990 align:start position:0% multi-dimensional 1559 much simpler than what<00:10:16.080> hedera<00:10:16.620> has<00:10:16.800> and<00:10:17.279> what<00:10:17.399> hedera<00:10:17.940> does 00:10:17.990 --> 00:10:18.000 align:start position:0% what hedera has and what hedera does 00:10:18.000 --> 00:10:19.610 align:start position:0% what hedera has and what hedera does isn't<00:10:18.420> too<00:10:18.660> scary<00:10:18.899> if<00:10:19.140> you<00:10:19.260> know<00:10:19.320> what's<00:10:19.440> going 00:10:19.610 --> 00:10:19.620 align:start position:0% isn't too scary if you know what's going 00:10:19.620 --> 00:10:20.810 align:start position:0% isn't too scary if you know what's going into<00:10:19.860> it 00:10:20.810 --> 00:10:20.820 align:start position:0% into it 00:10:20.820 --> 00:10:22.790 align:start position:0% into it um but<00:10:21.060> you<00:10:21.240> know<00:10:21.300> some<00:10:21.480> end<00:10:21.600> users<00:10:22.019> it's<00:10:22.620> not 00:10:22.790 --> 00:10:22.800 align:start position:0% um but you know some end users it's not 00:10:22.800 --> 00:10:24.350 align:start position:0% um but you know some end users it's not quite<00:10:23.040> as<00:10:23.160> simple<00:10:23.339> as<00:10:23.519> here's<00:10:23.820> one<00:10:23.940> price<00:10:24.120> and 00:10:24.350 --> 00:10:24.360 align:start position:0% quite as simple as here's one price and 00:10:24.360 --> 00:10:26.570 align:start position:0% quite as simple as here's one price and here's<00:10:24.540> one<00:10:24.720> meter<00:10:25.080> numbers<00:10:25.620> go<00:10:25.920> up<00:10:26.100> as<00:10:26.220> you<00:10:26.399> do 00:10:26.570 --> 00:10:26.580 align:start position:0% here's one meter numbers go up as you do 00:10:26.580 --> 00:10:28.070 align:start position:0% here's one meter numbers go up as you do more<00:10:26.760> so<00:10:27.420> I<00:10:27.540> think<00:10:27.660> the<00:10:27.899> the 00:10:28.070 --> 00:10:28.080 align:start position:0% more so I think the the 00:10:28.080 --> 00:10:30.530 align:start position:0% more so I think the the multi-dimensional<00:10:28.740> 1559<00:10:29.399> would<00:10:29.700> be<00:10:29.940> a<00:10:30.420> good 00:10:30.530 --> 00:10:30.540 align:start position:0% multi-dimensional 1559 would be a good 00:10:30.540 --> 00:10:31.690 align:start position:0% multi-dimensional 1559 would be a good value 00:10:31.690 --> 00:10:31.700 align:start position:0% value 00:10:31.700 --> 00:10:33.650 align:start position:0% value and<00:10:32.700> I<00:10:32.940> don't<00:10:33.060> think<00:10:33.240> we're<00:10:33.360> going<00:10:33.480> to<00:10:33.600> be 00:10:33.650 --> 00:10:33.660 align:start position:0% and I don't think we're going to be 00:10:33.660 --> 00:10:34.970 align:start position:0% and I don't think we're going to be charging<00:10:34.019> too<00:10:34.260> much<00:10:34.380> for<00:10:34.560> a<00:10:34.620> lot<00:10:34.680> of<00:10:34.800> our<00:10:34.860> gas 00:10:34.970 --> 00:10:34.980 align:start position:0% charging too much for a lot of our gas 00:10:34.980 --> 00:10:36.889 align:start position:0% charging too much for a lot of our gas features<00:10:35.399> but<00:10:35.519> if<00:10:35.640> we<00:10:35.760> do<00:10:35.940> we<00:10:36.420> should<00:10:36.540> consider 00:10:36.889 --> 00:10:36.899 align:start position:0% features but if we do we should consider 00:10:36.899 --> 00:10:39.410 align:start position:0% features but if we do we should consider letting<00:10:37.320> some<00:10:37.740> operations<00:10:38.220> be<00:10:38.519> charged<00:10:38.880> with 00:10:39.410 --> 00:10:39.420 align:start position:0% letting some operations be charged with 00:10:39.420 --> 00:10:41.810 align:start position:0% letting some operations be charged with ether<00:10:39.779> rather<00:10:40.620> than<00:10:40.740> charging<00:10:41.220> gas<00:10:41.459> because 00:10:41.810 --> 00:10:41.820 align:start position:0% ether rather than charging gas because 00:10:41.820 --> 00:10:44.210 align:start position:0% ether rather than charging gas because if<00:10:42.660> you're<00:10:42.720> just<00:10:42.899> going<00:10:43.019> to<00:10:43.200> store<00:10:43.320> its<00:10:43.680> store 00:10:44.210 --> 00:10:44.220 align:start position:0% if you're just going to store its store 00:10:44.220 --> 00:10:46.009 align:start position:0% if you're just going to store its store uh<00:10:44.640> take<00:10:44.940> up<00:10:45.060> a<00:10:45.180> lot<00:10:45.300> of<00:10:45.420> memory<00:10:45.600> space<00:10:45.779> that 00:10:46.009 --> 00:10:46.019 align:start position:0% uh take up a lot of memory space that 00:10:46.019 --> 00:10:47.269 align:start position:0% uh take up a lot of memory space that you're<00:10:46.140> not<00:10:46.260> doing<00:10:46.380> a<00:10:46.560> lot<00:10:46.620> of<00:10:46.740> compute<00:10:47.160> from 00:10:47.269 --> 00:10:47.279 align:start position:0% you're not doing a lot of compute from 00:10:47.279 --> 00:10:49.370 align:start position:0% you're not doing a lot of compute from there's<00:10:48.000> no<00:10:48.180> reason<00:10:48.360> to<00:10:48.600> keep<00:10:48.779> the<00:10:48.959> the<00:10:49.200> whole 00:10:49.370 --> 00:10:49.380 align:start position:0% there's no reason to keep the the whole 00:10:49.380 --> 00:10:51.590 align:start position:0% there's no reason to keep the the whole blockchain<00:10:49.860> shut<00:10:50.700> down<00:10:50.880> just<00:10:51.060> do<00:10:51.300> one<00:10:51.480> large 00:10:51.590 --> 00:10:51.600 align:start position:0% blockchain shut down just do one large 00:10:51.600 --> 00:10:54.050 align:start position:0% blockchain shut down just do one large operation<00:10:52.019> that<00:10:52.260> takes<00:10:52.380> no<00:10:52.560> compute 00:10:54.050 --> 00:10:54.060 align:start position:0% operation that takes no compute 00:10:54.060 --> 00:10:57.650 align:start position:0% operation that takes no compute um<00:10:54.120> not<00:10:54.600> too<00:10:54.720> big<00:10:54.839> of<00:10:54.959> an<00:10:55.140> issue 00:10:57.650 --> 00:10:57.660 align:start position:0% 00:10:57.660 --> 00:10:58.790 align:start position:0% um off<00:10:57.899> and<00:10:58.019> off<00:10:58.140> call<00:10:58.320> I<00:10:58.500> don't<00:10:58.560> know<00:10:58.680> that 00:10:58.790 --> 00:10:58.800 align:start position:0% um off and off call I don't know that 00:10:58.800 --> 00:11:00.829 align:start position:0% um off and off call I don't know that anybody<00:10:59.100> that<00:10:59.279> does<00:10:59.459> this<00:10:59.640> so<00:11:00.240> this<00:11:00.480> isn't<00:11:00.720> a 00:11:00.829 --> 00:11:00.839 align:start position:0% anybody that does this so this isn't a 00:11:00.839 --> 00:11:02.210 align:start position:0% anybody that does this so this isn't a fair<00:11:00.959> take<00:11:01.200> but<00:11:01.500> it<00:11:01.620> would<00:11:01.680> be<00:11:01.800> evidence<00:11:02.040> we 00:11:02.210 --> 00:11:02.220 align:start position:0% fair take but it would be evidence we 00:11:02.220 --> 00:11:03.829 align:start position:0% fair take but it would be evidence we shouldn't<00:11:02.459> do<00:11:02.640> it<00:11:02.760> I'll<00:11:03.240> come<00:11:03.420> back<00:11:03.600> to<00:11:03.720> this 00:11:03.829 --> 00:11:03.839 align:start position:0% shouldn't do it I'll come back to this 00:11:03.839 --> 00:11:05.210 align:start position:0% shouldn't do it I'll come back to this later<00:11:04.019> don't<00:11:04.320> worry 00:11:05.210 --> 00:11:05.220 align:start position:0% later don't worry 00:11:05.220 --> 00:11:06.949 align:start position:0% later don't worry the<00:11:05.760> next<00:11:05.880> thing<00:11:06.060> though<00:11:06.360> I'd<00:11:06.660> like<00:11:06.779> to<00:11:06.899> use 00:11:06.949 --> 00:11:06.959 align:start position:0% the next thing though I'd like to use 00:11:06.959 --> 00:11:09.170 align:start position:0% the next thing though I'd like to use this<00:11:07.140> as<00:11:07.320> a<00:11:07.440> little<00:11:07.500> example<00:11:07.980> I'll<00:11:08.760> tell<00:11:09.060> a 00:11:09.170 --> 00:11:09.180 align:start position:0% this as a little example I'll tell a 00:11:09.180 --> 00:11:10.910 align:start position:0% this as a little example I'll tell a little<00:11:09.240> parable<00:11:09.540> about<00:11:09.720> this 00:11:10.910 --> 00:11:10.920 align:start position:0% little parable about this 00:11:10.920 --> 00:11:11.990 align:start position:0% little parable about this um<00:11:10.980> and<00:11:11.339> a<00:11:11.459> lot<00:11:11.519> of<00:11:11.579> things<00:11:11.700> that<00:11:11.880> you're 00:11:11.990 --> 00:11:12.000 align:start position:0% um and a lot of things that you're 00:11:12.000 --> 00:11:13.970 align:start position:0% um and a lot of things that you're interacting<00:11:12.420> with<00:11:12.540> in<00:11:12.839> smart<00:11:13.079> contracts<00:11:13.620> and 00:11:13.970 --> 00:11:13.980 align:start position:0% interacting with in smart contracts and 00:11:13.980 --> 00:11:16.970 align:start position:0% interacting with in smart contracts and in<00:11:14.459> in<00:11:15.240> uh<00:11:15.839> blockchain 00:11:16.970 --> 00:11:16.980 align:start position:0% in in uh blockchain 00:11:16.980 --> 00:11:18.350 align:start position:0% in in uh blockchain sometimes<00:11:17.519> you<00:11:17.640> don't<00:11:17.820> know<00:11:17.940> if<00:11:18.060> it's<00:11:18.180> really 00:11:18.350 --> 00:11:18.360 align:start position:0% sometimes you don't know if it's really 00:11:18.360 --> 00:11:20.269 align:start position:0% sometimes you don't know if it's really going<00:11:18.540> on<00:11:18.660> anywhere<00:11:19.019> so<00:11:19.320> if<00:11:19.740> it's<00:11:19.920> going<00:11:20.100> on 00:11:20.269 --> 00:11:20.279 align:start position:0% going on anywhere so if it's going on 00:11:20.279 --> 00:11:23.090 align:start position:0% going on anywhere so if it's going on under<00:11:20.579> the<00:11:21.120> system<00:11:21.360> inside<00:11:21.779> inside<00:11:22.200> of<00:11:22.560> it<00:11:22.680> so 00:11:23.090 --> 00:11:23.100 align:start position:0% under the system inside inside of it so 00:11:23.100 --> 00:11:24.470 align:start position:0% under the system inside inside of it so here's<00:11:23.339> here's<00:11:23.640> a<00:11:23.760> little<00:11:23.820> scene<00:11:24.060> from 00:11:24.470 --> 00:11:24.480 align:start position:0% here's here's a little scene from 00:11:24.480 --> 00:11:26.810 align:start position:0% here's here's a little scene from Westworld<00:11:25.260> season<00:11:25.440> one<00:11:25.740> where<00:11:26.399> Billy<00:11:26.700> is 00:11:26.810 --> 00:11:26.820 align:start position:0% Westworld season one where Billy is 00:11:26.820 --> 00:11:29.269 align:start position:0% Westworld season one where Billy is going<00:11:27.000> in<00:11:27.120> and<00:11:27.300> says<00:11:27.540> like<00:11:27.720> are<00:11:28.079> you<00:11:28.200> real<00:11:28.380> and 00:11:29.269 --> 00:11:29.279 align:start position:0% going in and says like are you real and 00:11:29.279 --> 00:11:31.850 align:start position:0% going in and says like are you real and the<00:11:29.579> Very<00:11:30.180> pivot<00:11:31.140> comment<00:11:31.440> that<00:11:31.560> comes<00:11:31.800> out 00:11:31.850 --> 00:11:31.860 align:start position:0% the Very pivot comment that comes out 00:11:31.860 --> 00:11:33.170 align:start position:0% the Very pivot comment that comes out that<00:11:32.040> kind<00:11:32.220> of<00:11:32.339> shapes<00:11:32.700> the<00:11:32.880> rest<00:11:33.000> of<00:11:33.120> the 00:11:33.170 --> 00:11:33.180 align:start position:0% that kind of shapes the rest of the 00:11:33.180 --> 00:11:35.509 align:start position:0% that kind of shapes the rest of the series<00:11:33.360> is<00:11:33.720> well<00:11:34.019> if<00:11:34.200> you<00:11:34.380> can't<00:11:34.500> tell<00:11:34.740> does<00:11:35.339> it 00:11:35.509 --> 00:11:35.519 align:start position:0% series is well if you can't tell does it 00:11:35.519 --> 00:11:36.530 align:start position:0% series is well if you can't tell does it matter 00:11:36.530 --> 00:11:36.540 align:start position:0% matter 00:11:36.540 --> 00:11:38.150 align:start position:0% matter substance<00:11:37.320> that<00:11:37.500> you're<00:11:37.620> interacting<00:11:38.040> with 00:11:38.150 --> 00:11:38.160 align:start position:0% substance that you're interacting with 00:11:38.160 --> 00:11:40.550 align:start position:0% substance that you're interacting with doesn't<00:11:38.940> matter<00:11:39.240> nearly<00:11:39.600> as<00:11:39.720> much<00:11:39.899> as<00:11:40.380> the 00:11:40.550 --> 00:11:40.560 align:start position:0% doesn't matter nearly as much as the 00:11:40.560 --> 00:11:42.470 align:start position:0% doesn't matter nearly as much as the surface<00:11:40.860> you're<00:11:41.040> interacting<00:11:41.519> on 00:11:42.470 --> 00:11:42.480 align:start position:0% surface you're interacting on 00:11:42.480 --> 00:11:44.509 align:start position:0% surface you're interacting on so<00:11:43.019> this<00:11:43.260> is<00:11:43.500> something<00:11:43.620> that<00:11:43.860> we<00:11:43.980> did<00:11:44.100> in<00:11:44.399> this 00:11:44.509 --> 00:11:44.519 align:start position:0% so this is something that we did in this 00:11:44.519 --> 00:11:47.090 align:start position:0% so this is something that we did in this in<00:11:44.700> hedera<00:11:45.240> hedera<00:11:45.959> has<00:11:46.140> a<00:11:46.320> very<00:11:46.440> rich<00:11:46.620> token 00:11:47.090 --> 00:11:47.100 align:start position:0% in hedera hedera has a very rich token 00:11:47.100 --> 00:11:49.069 align:start position:0% in hedera hedera has a very rich token system<00:11:47.279> that<00:11:47.880> has<00:11:48.060> zero<00:11:48.420> connection<00:11:48.540> to<00:11:48.899> the 00:11:49.069 --> 00:11:49.079 align:start position:0% system that has zero connection to the 00:11:49.079 --> 00:11:50.810 align:start position:0% system that has zero connection to the smart<00:11:49.200> contract<00:11:49.680> system 00:11:50.810 --> 00:11:50.820 align:start position:0% smart contract system 00:11:50.820 --> 00:11:52.430 align:start position:0% smart contract system um this<00:11:51.000> is<00:11:51.120> how<00:11:51.300> they<00:11:51.420> get<00:11:51.600> their<00:11:51.660> 10<00:11:52.019> 000<00:11:52.079> TPS 00:11:52.430 --> 00:11:52.440 align:start position:0% um this is how they get their 10 000 TPS 00:11:52.440 --> 00:11:54.350 align:start position:0% um this is how they get their 10 000 TPS number<00:11:52.740> on<00:11:52.980> token<00:11:53.279> trades<00:11:53.579> is<00:11:54.000> they<00:11:54.180> just 00:11:54.350 --> 00:11:54.360 align:start position:0% number on token trades is they just 00:11:54.360 --> 00:11:56.569 align:start position:0% number on token trades is they just completely<00:11:54.660> bypass<00:11:55.140> the<00:11:55.320> evm<00:11:55.740> but<00:11:56.279> there's<00:11:56.459> a 00:11:56.569 --> 00:11:56.579 align:start position:0% completely bypass the evm but there's a 00:11:56.579 --> 00:11:58.009 align:start position:0% completely bypass the evm but there's a lot<00:11:56.700> of<00:11:56.820> use<00:11:56.940> cases<00:11:57.300> where<00:11:57.480> you<00:11:57.660> may<00:11:57.720> want<00:11:57.899> to 00:11:58.009 --> 00:11:58.019 align:start position:0% lot of use cases where you may want to 00:11:58.019 --> 00:11:59.870 align:start position:0% lot of use cases where you may want to interact<00:11:58.260> with<00:11:58.500> your<00:11:58.740> smart<00:11:58.920> contracts<00:11:59.459> to 00:11:59.870 --> 00:11:59.880 align:start position:0% interact with your smart contracts to 00:11:59.880 --> 00:12:02.030 align:start position:0% interact with your smart contracts to interact<00:12:00.240> with<00:12:00.420> your<00:12:00.540> native<00:12:00.660> hedera<00:12:01.260> tokens 00:12:02.030 --> 00:12:02.040 align:start position:0% interact with your native hedera tokens 00:12:02.040 --> 00:12:03.889 align:start position:0% interact with your native hedera tokens so<00:12:02.399> what<00:12:02.579> we<00:12:02.700> did<00:12:02.760> at<00:12:02.880> hedera<00:12:03.360> is<00:12:03.480> we<00:12:03.600> took<00:12:03.720> the 00:12:03.889 --> 00:12:03.899 align:start position:0% so what we did at hedera is we took the 00:12:03.899 --> 00:12:06.110 align:start position:0% so what we did at hedera is we took the addresses<00:12:04.320> of<00:12:04.680> the<00:12:04.860> tokens<00:12:05.220> and<00:12:05.760> we<00:12:05.820> made<00:12:06.000> a 00:12:06.110 --> 00:12:06.120 align:start position:0% addresses of the tokens and we made a 00:12:06.120 --> 00:12:07.790 align:start position:0% addresses of the tokens and we made a little<00:12:06.240> jumper<00:12:06.600> contract<00:12:06.959> you<00:12:07.140> call<00:12:07.380> into<00:12:07.560> it 00:12:07.790 --> 00:12:07.800 align:start position:0% little jumper contract you call into it 00:12:07.800 --> 00:12:09.949 align:start position:0% little jumper contract you call into it it'll<00:12:08.220> immediately<00:12:08.519> jump<00:12:08.820> you<00:12:09.000> into<00:12:09.180> the<00:12:09.360> HTS 00:12:09.949 --> 00:12:09.959 align:start position:0% it'll immediately jump you into the HTS 00:12:09.959 --> 00:12:11.870 align:start position:0% it'll immediately jump you into the HTS system<00:12:10.140> contract<00:12:10.680> and<00:12:11.279> do<00:12:11.459> whatever<00:12:11.579> you 00:12:11.870 --> 00:12:11.880 align:start position:0% system contract and do whatever you 00:12:11.880 --> 00:12:13.910 align:start position:0% system contract and do whatever you would<00:12:12.000> need<00:12:12.180> to<00:12:12.300> do<00:12:12.480> and<00:12:13.200> from<00:12:13.380> this<00:12:13.560> we<00:12:13.740> could 00:12:13.910 --> 00:12:13.920 align:start position:0% would need to do and from this we could 00:12:13.920 --> 00:12:16.370 align:start position:0% would need to do and from this we could make<00:12:14.160> our<00:12:14.459> HTS<00:12:15.000> tokens<00:12:15.360> look<00:12:15.899> like<00:12:16.079> you<00:12:16.200> had 00:12:16.370 --> 00:12:16.380 align:start position:0% make our HTS tokens look like you had 00:12:16.380 --> 00:12:18.610 align:start position:0% make our HTS tokens look like you had deployed<00:12:16.740> an<00:12:16.860> open<00:12:16.980> Zeppelin<00:12:17.459> erc20<00:12:18.060> or 00:12:18.610 --> 00:12:18.620 align:start position:0% deployed an open Zeppelin erc20 or 00:12:18.620 --> 00:12:21.590 align:start position:0% deployed an open Zeppelin erc20 or crc721<00:12:19.620> contract<00:12:20.100> and<00:12:20.820> it<00:12:20.940> worked<00:12:21.180> great<00:12:21.360> we 00:12:21.590 --> 00:12:21.600 align:start position:0% crc721 contract and it worked great we 00:12:21.600 --> 00:12:23.569 align:start position:0% crc721 contract and it worked great we plugged<00:12:21.959> in<00:12:22.019> some<00:12:22.260> some<00:12:22.500> unicorn<00:12:23.040> some 00:12:23.569 --> 00:12:23.579 align:start position:0% plugged in some some unicorn some 00:12:23.579 --> 00:12:26.509 align:start position:0% plugged in some some unicorn some uniswap<00:12:24.440> derivatives<00:12:25.440> we<00:12:25.680> plugged<00:12:25.980> in<00:12:26.100> zerox 00:12:26.509 --> 00:12:26.519 align:start position:0% uniswap derivatives we plugged in zerox 00:12:26.519 --> 00:12:29.090 align:start position:0% uniswap derivatives we plugged in zerox protocol<00:12:27.019> in<00:12:28.019> some<00:12:28.140> of<00:12:28.260> our<00:12:28.320> metamask<00:12:28.740> testing 00:12:29.090 --> 00:12:29.100 align:start position:0% protocol in some of our metamask testing 00:12:29.100 --> 00:12:31.009 align:start position:0% protocol in some of our metamask testing it<00:12:29.279> just<00:12:29.519> magically<00:12:30.060> worked<00:12:30.420> and<00:12:30.720> none<00:12:30.899> of 00:12:31.009 --> 00:12:31.019 align:start position:0% it just magically worked and none of 00:12:31.019 --> 00:12:33.650 align:start position:0% it just magically worked and none of this<00:12:31.140> was<00:12:31.560> running<00:12:31.800> evm<00:12:32.399> code 00:12:33.650 --> 00:12:33.660 align:start position:0% this was running evm code 00:12:33.660 --> 00:12:35.810 align:start position:0% this was running evm code um<00:12:33.720> so<00:12:34.380> the<00:12:34.620> takeaway<00:12:34.920> from<00:12:35.160> this<00:12:35.339> is<00:12:35.640> it's 00:12:35.810 --> 00:12:35.820 align:start position:0% um so the takeaway from this is it's 00:12:35.820 --> 00:12:37.250 align:start position:0% um so the takeaway from this is it's only<00:12:36.000> the<00:12:36.180> effects<00:12:36.480> of<00:12:36.600> what<00:12:36.720> happens<00:12:36.899> in<00:12:37.140> a 00:12:37.250 --> 00:12:37.260 align:start position:0% only the effects of what happens in a 00:12:37.260 --> 00:12:38.710 align:start position:0% only the effects of what happens in a lot<00:12:37.320> of<00:12:37.440> these<00:12:37.560> systems<00:12:37.920> that<00:12:38.160> matters 00:12:38.710 --> 00:12:38.720 align:start position:0% lot of these systems that matters 00:12:38.720 --> 00:12:40.730 align:start position:0% lot of these systems that matters clients<00:12:39.720> can<00:12:39.839> do<00:12:40.019> things<00:12:40.140> if<00:12:40.440> they<00:12:40.620> really 00:12:40.730 --> 00:12:40.740 align:start position:0% clients can do things if they really 00:12:40.740 --> 00:12:42.710 align:start position:0% clients can do things if they really wanted<00:12:40.980> to<00:12:41.220> they<00:12:41.760> could<00:12:41.940> pre-compile<00:12:42.480> the 00:12:42.710 --> 00:12:42.720 align:start position:0% wanted to they could pre-compile the 00:12:42.720 --> 00:12:44.990 align:start position:0% wanted to they could pre-compile the open<00:12:42.839> Zeppelin<00:12:43.320> contracts<00:12:43.860> if<00:12:44.399> speed<00:12:44.639> is<00:12:44.880> the 00:12:44.990 --> 00:12:45.000 align:start position:0% open Zeppelin contracts if speed is the 00:12:45.000 --> 00:12:46.250 align:start position:0% open Zeppelin contracts if speed is the issue 00:12:46.250 --> 00:12:46.260 align:start position:0% issue 00:12:46.260 --> 00:12:47.690 align:start position:0% issue um this<00:12:46.500> has<00:12:46.680> very<00:12:46.860> and<00:12:47.100> this<00:12:47.279> is<00:12:47.399> honestly 00:12:47.690 --> 00:12:47.700 align:start position:0% um this has very and this is honestly 00:12:47.700 --> 00:12:51.170 align:start position:0% um this has very and this is honestly what<00:12:47.899> zkevm<00:12:48.899> uh<00:12:49.740> proving<00:12:50.160> is<00:12:50.459> is<00:12:50.579> using<00:12:50.940> in<00:12:51.060> the 00:12:51.170 --> 00:12:51.180 align:start position:0% what zkevm uh proving is is using in the 00:12:51.180 --> 00:12:53.990 align:start position:0% what zkevm uh proving is is using in the system<00:12:51.360> and<00:12:51.779> you<00:12:51.959> know<00:12:52.079> it's<00:12:52.680> it's<00:12:52.980> uh<00:12:53.399> it's 00:12:53.990 --> 00:12:54.000 align:start position:0% system and you know it's it's uh it's 00:12:54.000 --> 00:12:55.490 align:start position:0% system and you know it's it's uh it's the<00:12:54.120> side<00:12:54.300> effects<00:12:54.600> that<00:12:54.720> matter<00:12:54.899> and<00:12:55.139> I<00:12:55.380> don't 00:12:55.490 --> 00:12:55.500 align:start position:0% the side effects that matter and I don't 00:12:55.500 --> 00:12:57.410 align:start position:0% the side effects that matter and I don't understand<00:12:55.620> the<00:12:56.040> math<00:12:56.160> but<00:12:56.760> the<00:12:56.880> math<00:12:57.000> checks 00:12:57.410 --> 00:12:57.420 align:start position:0% understand the math but the math checks 00:12:57.420 --> 00:12:59.030 align:start position:0% understand the math but the math checks out<00:12:57.600> and<00:12:58.139> so<00:12:58.260> you<00:12:58.500> can<00:12:58.620> take<00:12:58.740> that<00:12:58.860> same 00:12:59.030 --> 00:12:59.040 align:start position:0% out and so you can take that same 00:12:59.040 --> 00:13:00.290 align:start position:0% out and so you can take that same approach<00:12:59.279> to<00:12:59.399> the<00:12:59.519> evm<00:12:59.880> I<00:13:00.060> don't<00:13:00.240> understand 00:13:00.290 --> 00:13:00.300 align:start position:0% approach to the evm I don't understand 00:13:00.300 --> 00:13:02.389 align:start position:0% approach to the evm I don't understand the<00:13:00.600> evm<00:13:01.019> but<00:13:01.380> the<00:13:01.620> side<00:13:01.740> effects<00:13:02.040> check<00:13:02.220> out 00:13:02.389 --> 00:13:02.399 align:start position:0% the evm but the side effects check out 00:13:02.399 --> 00:13:04.190 align:start position:0% the evm but the side effects check out so<00:13:02.940> you<00:13:03.060> can<00:13:03.180> pull<00:13:03.300> this<00:13:03.480> in<00:13:03.600> later<00:13:03.839> on<00:13:04.019> all 00:13:04.190 --> 00:13:04.200 align:start position:0% so you can pull this in later on all 00:13:04.200 --> 00:13:06.230 align:start position:0% so you can pull this in later on all sorts<00:13:04.440> of<00:13:04.500> other<00:13:04.680> systems<00:13:05.639> finally 00:13:06.230 --> 00:13:06.240 align:start position:0% sorts of other systems finally 00:13:06.240 --> 00:13:08.030 align:start position:0% sorts of other systems finally transactions<00:13:07.019> and<00:13:07.139> transacting<00:13:07.680> this<00:13:07.860> is 00:13:08.030 --> 00:13:08.040 align:start position:0% transactions and transacting this is 00:13:08.040 --> 00:13:09.889 align:start position:0% transactions and transacting this is probably<00:13:08.220> the<00:13:08.459> last<00:13:08.639> hurdle<00:13:09.060> that<00:13:09.540> we<00:13:09.660> had<00:13:09.779> to 00:13:09.889 --> 00:13:09.899 align:start position:0% probably the last hurdle that we had to 00:13:09.899 --> 00:13:12.410 align:start position:0% probably the last hurdle that we had to overcome<00:13:10.320> to<00:13:10.740> really<00:13:10.860> up<00:13:11.339> our<00:13:11.519> game<00:13:11.639> at<00:13:11.820> hedera 00:13:12.410 --> 00:13:12.420 align:start position:0% overcome to really up our game at hedera 00:13:12.420 --> 00:13:14.690 align:start position:0% overcome to really up our game at hedera for<00:13:12.660> ethereum<00:13:13.079> compatibility 00:13:14.690 --> 00:13:14.700 align:start position:0% for ethereum compatibility 00:13:14.700 --> 00:13:16.790 align:start position:0% for ethereum compatibility um<00:13:14.760> we<00:13:15.000> had<00:13:15.180> to 00:13:16.790 --> 00:13:16.800 align:start position:0% um we had to 00:13:16.800 --> 00:13:19.730 align:start position:0% um we had to adapt<00:13:17.700> the<00:13:18.540> ethereum<00:13:18.899> transactions<00:13:19.560> into 00:13:19.730 --> 00:13:19.740 align:start position:0% adapt the ethereum transactions into 00:13:19.740 --> 00:13:21.410 align:start position:0% adapt the ethereum transactions into hedera<00:13:20.339> transactions<00:13:20.820> I'll<00:13:20.940> go<00:13:21.180> through<00:13:21.300> this 00:13:21.410 --> 00:13:21.420 align:start position:0% hedera transactions I'll go through this 00:13:21.420 --> 00:13:22.910 align:start position:0% hedera transactions I'll go through this in<00:13:21.540> some<00:13:21.660> of<00:13:21.779> the<00:13:21.839> slides 00:13:22.910 --> 00:13:22.920 align:start position:0% in some of the slides 00:13:22.920 --> 00:13:24.170 align:start position:0% in some of the slides um but<00:13:23.040> first<00:13:23.220> I<00:13:23.339> want<00:13:23.459> to<00:13:23.579> talk<00:13:23.700> about<00:13:23.820> before 00:13:24.170 --> 00:13:24.180 align:start position:0% um but first I want to talk about before 00:13:24.180 --> 00:13:26.150 align:start position:0% um but first I want to talk about before I<00:13:24.480> get<00:13:24.540> too<00:13:24.660> deep<00:13:24.779> into<00:13:24.959> the<00:13:25.139> transactions<00:13:25.680> a 00:13:26.150 --> 00:13:26.160 align:start position:0% I get too deep into the transactions a 00:13:26.160 --> 00:13:27.650 align:start position:0% I get too deep into the transactions a little<00:13:26.339> bit<00:13:26.459> about<00:13:26.579> hedera's<00:13:27.300> consensus 00:13:27.650 --> 00:13:27.660 align:start position:0% little bit about hedera's consensus 00:13:27.660 --> 00:13:29.030 align:start position:0% little bit about hedera's consensus mechanism<00:13:27.959> that<00:13:28.200> really<00:13:28.440> drives<00:13:28.740> a<00:13:28.860> lot<00:13:28.920> of 00:13:29.030 --> 00:13:29.040 align:start position:0% mechanism that really drives a lot of 00:13:29.040 --> 00:13:31.730 align:start position:0% mechanism that really drives a lot of its<00:13:29.220> features<00:13:29.660> hedera<00:13:30.660> uses<00:13:31.019> a<00:13:31.380> consensus 00:13:31.730 --> 00:13:31.740 align:start position:0% its features hedera uses a consensus 00:13:31.740 --> 00:13:34.129 align:start position:0% its features hedera uses a consensus mechanism<00:13:32.220> that<00:13:32.880> fully<00:13:33.180> separates<00:13:33.540> ordering 00:13:34.129 --> 00:13:34.139 align:start position:0% mechanism that fully separates ordering 00:13:34.139 --> 00:13:36.470 align:start position:0% mechanism that fully separates ordering from<00:13:34.380> execution<00:13:34.920> and<00:13:35.760> the<00:13:36.000> way<00:13:36.120> they<00:13:36.240> do<00:13:36.360> this 00:13:36.470 --> 00:13:36.480 align:start position:0% from execution and the way they do this 00:13:36.480 --> 00:13:37.790 align:start position:0% from execution and the way they do this is<00:13:36.660> because<00:13:36.779> of<00:13:37.019> the<00:13:37.139> nature<00:13:37.440> of<00:13:37.620> the 00:13:37.790 --> 00:13:37.800 align:start position:0% is because of the nature of the 00:13:37.800 --> 00:13:40.009 align:start position:0% is because of the nature of the asynchronous<00:13:38.399> bft<00:13:38.760> hashgraph<00:13:39.540> algorithm 00:13:40.009 --> 00:13:40.019 align:start position:0% asynchronous bft hashgraph algorithm 00:13:40.019 --> 00:13:42.590 align:start position:0% asynchronous bft hashgraph algorithm algorithm<00:13:40.800> the<00:13:41.579> algorithm<00:13:41.880> works<00:13:42.180> by<00:13:42.300> all<00:13:42.480> the 00:13:42.590 --> 00:13:42.600 align:start position:0% algorithm the algorithm works by all the 00:13:42.600 --> 00:13:44.569 align:start position:0% algorithm the algorithm works by all the nodes<00:13:42.839> gossiping<00:13:43.740> together<00:13:43.860> about<00:13:44.160> what 00:13:44.569 --> 00:13:44.579 align:start position:0% nodes gossiping together about what 00:13:44.579 --> 00:13:46.190 align:start position:0% nodes gossiping together about what transactions<00:13:45.120> they've<00:13:45.420> seen<00:13:45.600> and<00:13:46.079> they 00:13:46.190 --> 00:13:46.200 align:start position:0% transactions they've seen and they 00:13:46.200 --> 00:13:48.829 align:start position:0% transactions they've seen and they include<00:13:46.440> a<00:13:46.560> link<00:13:46.680> to<00:13:46.860> another<00:13:47.040> transaction<00:13:47.839> to 00:13:48.829 --> 00:13:48.839 align:start position:0% include a link to another transaction to 00:13:48.839 --> 00:13:50.690 align:start position:0% include a link to another transaction to another<00:13:49.019> to<00:13:49.380> another<00:13:49.560> node's<00:13:50.100> previous<00:13:50.279> hash 00:13:50.690 --> 00:13:50.700 align:start position:0% another to another node's previous hash 00:13:50.700 --> 00:13:53.690 align:start position:0% another to another node's previous hash in<00:13:51.000> Gossip<00:13:51.420> eventually<00:13:52.380> you<00:13:53.279> can<00:13:53.339> get<00:13:53.459> to<00:13:53.579> the 00:13:53.690 --> 00:13:53.700 align:start position:0% in Gossip eventually you can get to the 00:13:53.700 --> 00:13:54.889 align:start position:0% in Gossip eventually you can get to the point<00:13:53.880> where<00:13:54.120> you<00:13:54.240> know<00:13:54.420> what<00:13:54.600> all<00:13:54.720> the<00:13:54.839> other 00:13:54.889 --> 00:13:54.899 align:start position:0% point where you know what all the other 00:13:54.899 --> 00:13:56.210 align:start position:0% point where you know what all the other nodes<00:13:55.139> have<00:13:55.320> seen<00:13:55.500> and<00:13:55.680> what<00:13:55.800> they've<00:13:55.980> signed 00:13:56.210 --> 00:13:56.220 align:start position:0% nodes have seen and what they've signed 00:13:56.220 --> 00:13:58.129 align:start position:0% nodes have seen and what they've signed and<00:13:56.339> attested<00:13:56.760> to<00:13:56.940> and<00:13:57.420> you<00:13:57.600> can<00:13:57.660> come<00:13:57.839> to<00:13:58.019> a 00:13:58.129 --> 00:13:58.139 align:start position:0% and attested to and you can come to a 00:13:58.139 --> 00:13:59.949 align:start position:0% and attested to and you can come to a conclusion<00:13:58.500> about<00:13:58.740> when<00:13:59.220> transactions 00:13:59.949 --> 00:13:59.959 align:start position:0% conclusion about when transactions 00:13:59.959 --> 00:14:02.690 align:start position:0% conclusion about when transactions reached<00:14:00.959> the<00:14:01.320> the<00:14:01.500> majority<00:14:01.980> of<00:14:02.519> the<00:14:02.639> other 00:14:02.690 --> 00:14:02.700 align:start position:0% reached the the majority of the other 00:14:02.700 --> 00:14:04.730 align:start position:0% reached the the majority of the other nodes<00:14:03.060> and<00:14:03.720> you<00:14:03.899> can<00:14:04.019> take<00:14:04.139> an<00:14:04.380> average<00:14:04.500> of 00:14:04.730 --> 00:14:04.740 align:start position:0% nodes and you can take an average of 00:14:04.740 --> 00:14:06.710 align:start position:0% nodes and you can take an average of when<00:14:04.980> it<00:14:05.160> came<00:14:05.279> and<00:14:05.760> that's<00:14:06.000> your<00:14:06.180> time<00:14:06.300> stamp 00:14:06.710 --> 00:14:06.720 align:start position:0% when it came and that's your time stamp 00:14:06.720 --> 00:14:08.569 align:start position:0% when it came and that's your time stamp and<00:14:07.079> that's<00:14:07.200> your<00:14:07.500> Absolute<00:14:07.800> Total<00:14:08.160> ordering 00:14:08.569 --> 00:14:08.579 align:start position:0% and that's your Absolute Total ordering 00:14:08.579 --> 00:14:10.190 align:start position:0% and that's your Absolute Total ordering so<00:14:08.940> we<00:14:09.120> can<00:14:09.240> order<00:14:09.360> these<00:14:09.660> transactions 00:14:10.190 --> 00:14:10.200 align:start position:0% so we can order these transactions 00:14:10.200 --> 00:14:11.509 align:start position:0% so we can order these transactions without<00:14:10.380> even<00:14:10.680> seeing<00:14:10.980> what's<00:14:11.100> on<00:14:11.339> the<00:14:11.459> inside 00:14:11.509 --> 00:14:11.519 align:start position:0% without even seeing what's on the inside 00:14:11.519 --> 00:14:13.069 align:start position:0% without even seeing what's on the inside of<00:14:11.820> them 00:14:13.069 --> 00:14:13.079 align:start position:0% of them 00:14:13.079 --> 00:14:14.810 align:start position:0% of them now<00:14:13.620> one<00:14:13.920> of<00:14:14.040> the<00:14:14.100> great<00:14:14.220> things<00:14:14.399> about<00:14:14.579> this 00:14:14.810 --> 00:14:14.820 align:start position:0% now one of the great things about this 00:14:14.820 --> 00:14:16.490 align:start position:0% now one of the great things about this is<00:14:15.000> there<00:14:15.180> is<00:14:15.360> no<00:14:15.480> leader<00:14:15.899> that<00:14:16.019> comes<00:14:16.320> out<00:14:16.380> of 00:14:16.490 --> 00:14:16.500 align:start position:0% is there is no leader that comes out of 00:14:16.500 --> 00:14:18.410 align:start position:0% is there is no leader that comes out of this<00:14:16.620> process<00:14:16.920> so<00:14:17.399> so<00:14:17.820> when<00:14:18.120> people<00:14:18.240> say 00:14:18.410 --> 00:14:18.420 align:start position:0% this process so so when people say 00:14:18.420 --> 00:14:19.970 align:start position:0% this process so so when people say hedera<00:14:18.899> is<00:14:19.019> not<00:14:19.079> a<00:14:19.260> blockchain<00:14:19.500> it's<00:14:19.740> probably 00:14:19.970 --> 00:14:19.980 align:start position:0% hedera is not a blockchain it's probably 00:14:19.980 --> 00:14:21.650 align:start position:0% hedera is not a blockchain it's probably better<00:14:20.220> to<00:14:20.459> say<00:14:20.639> that<00:14:21.060> there's<00:14:21.240> no<00:14:21.420> block 00:14:21.650 --> 00:14:21.660 align:start position:0% better to say that there's no block 00:14:21.660 --> 00:14:23.930 align:start position:0% better to say that there's no block producers<00:14:22.260> in<00:14:22.440> hedera<00:14:23.040> we<00:14:23.399> don't<00:14:23.459> go<00:14:23.639> into<00:14:23.700> a 00:14:23.930 --> 00:14:23.940 align:start position:0% producers in hedera we don't go into a 00:14:23.940 --> 00:14:25.069 align:start position:0% producers in hedera we don't go into a memory<00:14:24.120> pool<00:14:24.300> and<00:14:24.480> pick<00:14:24.540> and<00:14:24.720> choose<00:14:24.899> our 00:14:25.069 --> 00:14:25.079 align:start position:0% memory pool and pick and choose our 00:14:25.079 --> 00:14:26.810 align:start position:0% memory pool and pick and choose our favorite<00:14:25.200> out<00:14:25.500> our<00:14:26.220> favorite<00:14:26.339> transactions 00:14:26.810 --> 00:14:26.820 align:start position:0% favorite out our favorite transactions 00:14:26.820 --> 00:14:28.490 align:start position:0% favorite out our favorite transactions and<00:14:27.000> put<00:14:27.120> them<00:14:27.180> in<00:14:27.300> there<00:14:27.420> you<00:14:28.019> get<00:14:28.200> the<00:14:28.320> order 00:14:28.490 --> 00:14:28.500 align:start position:0% and put them in there you get the order 00:14:28.500 --> 00:14:31.430 align:start position:0% and put them in there you get the order that<00:14:28.920> you<00:14:29.040> get<00:14:29.279> and<00:14:30.180> this<00:14:30.360> allows<00:14:30.720> us<00:14:30.839> to<00:14:31.139> and 00:14:31.430 --> 00:14:31.440 align:start position:0% that you get and this allows us to and 00:14:31.440 --> 00:14:33.290 align:start position:0% that you get and this allows us to and this<00:14:31.620> is<00:14:31.740> kind<00:14:31.920> of<00:14:31.980> the<00:14:32.100> trick<00:14:32.279> behind<00:14:32.639> how<00:14:33.180> we 00:14:33.290 --> 00:14:33.300 align:start position:0% this is kind of the trick behind how we 00:14:33.300 --> 00:14:35.329 align:start position:0% this is kind of the trick behind how we get<00:14:33.480> our<00:14:33.660> amazingly<00:14:34.320> High<00:14:34.500> TPS<00:14:34.920> numbers 00:14:35.329 --> 00:14:35.339 align:start position:0% get our amazingly High TPS numbers 00:14:35.339 --> 00:14:37.610 align:start position:0% get our amazingly High TPS numbers because<00:14:35.880> we're<00:14:36.120> running<00:14:36.360> the<00:14:36.540> evm<00:14:36.959> full-time 00:14:37.610 --> 00:14:37.620 align:start position:0% because we're running the evm full-time 00:14:37.620 --> 00:14:39.470 align:start position:0% because we're running the evm full-time you<00:14:38.339> know 00:14:39.470 --> 00:14:39.480 align:start position:0% you know 00:14:39.480 --> 00:14:41.689 align:start position:0% you know the<00:14:39.899> base<00:14:40.079> of<00:14:40.260> evm<00:14:40.620> is<00:14:40.740> not<00:14:40.860> the<00:14:41.040> fastest<00:14:41.339> that 00:14:41.689 --> 00:14:41.699 align:start position:0% the base of evm is not the fastest that 00:14:41.699 --> 00:14:44.030 align:start position:0% the base of evm is not the fastest that will<00:14:41.940> be<00:14:42.120> evm1<00:14:42.720> but<00:14:43.260> what<00:14:43.440> we're<00:14:43.560> running<00:14:43.740> is 00:14:44.030 --> 00:14:44.040 align:start position:0% will be evm1 but what we're running is 00:14:44.040 --> 00:14:45.650 align:start position:0% will be evm1 but what we're running is if<00:14:44.160> we<00:14:44.339> run<00:14:44.459> it<00:14:44.639> all<00:14:44.760> the<00:14:44.880> time<00:14:45.060> we<00:14:45.540> can 00:14:45.650 --> 00:14:45.660 align:start position:0% if we run it all the time we can 00:14:45.660 --> 00:14:47.569 align:start position:0% if we run it all the time we can overcome<00:14:46.019> a<00:14:46.139> lot<00:14:46.260> of<00:14:46.320> those<00:14:46.440> barriers<00:14:46.860> and<00:14:47.459> we 00:14:47.569 --> 00:14:47.579 align:start position:0% overcome a lot of those barriers and we 00:14:47.579 --> 00:14:49.129 align:start position:0% overcome a lot of those barriers and we can<00:14:47.699> get<00:14:47.880> that<00:14:48.000> transaction<00:14:48.420> and<00:14:48.660> that's<00:14:48.899> even 00:14:49.129 --> 00:14:49.139 align:start position:0% can get that transaction and that's even 00:14:49.139 --> 00:14:51.769 align:start position:0% can get that transaction and that's even 15<00:14:49.680> Mega<00:14:50.100> gas<00:14:50.279> per<00:14:50.519> second<00:14:50.699> is<00:14:51.420> even<00:14:51.600> us 00:14:51.769 --> 00:14:51.779 align:start position:0% 15 Mega gas per second is even us 00:14:51.779 --> 00:14:53.269 align:start position:0% 15 Mega gas per second is even us holding<00:14:52.079> back<00:14:52.199> and<00:14:52.380> having<00:14:52.620> some<00:14:52.860> safety 00:14:53.269 --> 00:14:53.279 align:start position:0% holding back and having some safety 00:14:53.279 --> 00:14:55.069 align:start position:0% holding back and having some safety features<00:14:54.240> in<00:14:54.360> there<00:14:54.540> in<00:14:54.660> case<00:14:54.839> we<00:14:55.019> get 00:14:55.069 --> 00:14:55.079 align:start position:0% features in there in case we get 00:14:55.079 --> 00:14:57.170 align:start position:0% features in there in case we get overloaded<00:14:55.560> in<00:14:55.680> other<00:14:55.800> parts<00:14:55.980> of<00:14:56.160> the<00:14:56.279> system 00:14:57.170 --> 00:14:57.180 align:start position:0% overloaded in other parts of the system 00:14:57.180 --> 00:14:58.790 align:start position:0% overloaded in other parts of the system now<00:14:58.199> um 00:14:58.790 --> 00:14:58.800 align:start position:0% now um 00:14:58.800 --> 00:15:00.590 align:start position:0% now um the<00:14:59.339> problem<00:14:59.399> is<00:14:59.639> this<00:14:59.820> really<00:15:00.060> doesn't<00:15:00.240> apply 00:15:00.590 --> 00:15:00.600 align:start position:0% the problem is this really doesn't apply 00:15:00.600 --> 00:15:02.210 align:start position:0% the problem is this really doesn't apply to<00:15:00.899> ethereum 00:15:02.210 --> 00:15:02.220 align:start position:0% to ethereum 00:15:02.220 --> 00:15:03.829 align:start position:0% to ethereum blockchains<00:15:03.000> never<00:15:03.180> changed<00:15:03.600> their 00:15:03.829 --> 00:15:03.839 align:start position:0% blockchains never changed their 00:15:03.839 --> 00:15:05.930 align:start position:0% blockchains never changed their consensus<00:15:04.380> algorithm<00:15:04.800> well<00:15:05.160> almost<00:15:05.639> never 00:15:05.930 --> 00:15:05.940 align:start position:0% consensus algorithm well almost never 00:15:05.940 --> 00:15:09.769 align:start position:0% consensus algorithm well almost never and<00:15:06.839> consent<00:15:07.260> and<00:15:07.560> uh<00:15:07.980> and<00:15:08.820> um<00:15:09.240> ethereum 00:15:09.769 --> 00:15:09.779 align:start position:0% and consent and uh and um ethereum 00:15:09.779 --> 00:15:11.389 align:start position:0% and consent and uh and um ethereum mainnet<00:15:10.139> just<00:15:10.320> changed<00:15:10.680> there<00:15:10.800> is<00:15:10.980> over<00:15:11.100> to 00:15:11.389 --> 00:15:11.399 align:start position:0% mainnet just changed there is over to 00:15:11.399 --> 00:15:13.670 align:start position:0% mainnet just changed there is over to proof<00:15:12.060> of<00:15:12.180> stake<00:15:12.480> and<00:15:13.079> a<00:15:13.199> lot<00:15:13.320> of<00:15:13.380> things<00:15:13.500> about 00:15:13.670 --> 00:15:13.680 align:start position:0% proof of stake and a lot of things about 00:15:13.680 --> 00:15:15.350 align:start position:0% proof of stake and a lot of things about the<00:15:13.860> culture<00:15:14.160> are<00:15:14.399> falling<00:15:14.699> out<00:15:14.820> from<00:15:15.180> this 00:15:15.350 --> 00:15:15.360 align:start position:0% the culture are falling out from this 00:15:15.360 --> 00:15:18.310 align:start position:0% the culture are falling out from this Mev<00:15:16.199> is<00:15:16.380> accepted<00:15:16.800> and<00:15:16.980> endorsed 00:15:18.310 --> 00:15:18.320 align:start position:0% Mev is accepted and endorsed 00:15:18.320 --> 00:15:20.090 align:start position:0% Mev is accepted and endorsed there's<00:15:19.320> talkative<00:15:19.620> and<00:15:19.800> surrounding 00:15:20.090 --> 00:15:20.100 align:start position:0% there's talkative and surrounding 00:15:20.100 --> 00:15:21.590 align:start position:0% there's talkative and surrounding proposer<00:15:20.519> Builder<00:15:20.820> separation<00:15:21.120> into<00:15:21.360> the 00:15:21.590 --> 00:15:21.600 align:start position:0% proposer Builder separation into the 00:15:21.600 --> 00:15:23.210 align:start position:0% proposer Builder separation into the protocol<00:15:21.899> so<00:15:22.440> some<00:15:22.680> of<00:15:22.800> these<00:15:22.920> base<00:15:23.040> level 00:15:23.210 --> 00:15:23.220 align:start position:0% protocol so some of these base level 00:15:23.220 --> 00:15:24.829 align:start position:0% protocol so some of these base level decisions<00:15:23.639> come<00:15:24.000> up<00:15:24.120> and<00:15:24.300> they<00:15:24.420> affect<00:15:24.660> the 00:15:24.829 --> 00:15:24.839 align:start position:0% decisions come up and they affect the 00:15:24.839 --> 00:15:26.389 align:start position:0% decisions come up and they affect the nature<00:15:25.079> of<00:15:25.199> the<00:15:25.260> ecosystem 00:15:26.389 --> 00:15:26.399 align:start position:0% nature of the ecosystem 00:15:26.399 --> 00:15:28.310 align:start position:0% nature of the ecosystem so<00:15:27.000> there's<00:15:27.300> you<00:15:27.600> know<00:15:27.660> not<00:15:27.899> much<00:15:28.019> to<00:15:28.199> be 00:15:28.310 --> 00:15:28.320 align:start position:0% so there's you know not much to be 00:15:28.320 --> 00:15:29.389 align:start position:0% so there's you know not much to be considered<00:15:28.680> about<00:15:28.740> this<00:15:28.920> this<00:15:29.040> is<00:15:29.220> kind<00:15:29.279> of 00:15:29.389 --> 00:15:29.399 align:start position:0% considered about this this is kind of 00:15:29.399 --> 00:15:30.769 align:start position:0% considered about this this is kind of neat<00:15:29.519> to<00:15:29.639> look<00:15:29.760> at<00:15:29.880> but<00:15:30.300> it's<00:15:30.480> not<00:15:30.600> something 00:15:30.769 --> 00:15:30.779 align:start position:0% neat to look at but it's not something 00:15:30.779 --> 00:15:31.910 align:start position:0% neat to look at but it's not something that<00:15:31.019> ethereum<00:15:31.380> is<00:15:31.440> going<00:15:31.560> to<00:15:31.620> be<00:15:31.680> able<00:15:31.800> to 00:15:31.910 --> 00:15:31.920 align:start position:0% that ethereum is going to be able to 00:15:31.920 --> 00:15:32.930 align:start position:0% that ethereum is going to be able to change 00:15:32.930 --> 00:15:32.940 align:start position:0% change 00:15:32.940 --> 00:15:34.850 align:start position:0% change the<00:15:33.480> next<00:15:33.600> thing<00:15:33.779> I<00:15:33.959> ran<00:15:34.139> into<00:15:34.199> was<00:15:34.560> an<00:15:34.680> issue 00:15:34.850 --> 00:15:34.860 align:start position:0% the next thing I ran into was an issue 00:15:34.860 --> 00:15:36.590 align:start position:0% the next thing I ran into was an issue with<00:15:34.980> transaction<00:15:35.339> announces<00:15:35.820> hedera 00:15:36.590 --> 00:15:36.600 align:start position:0% with transaction announces hedera 00:15:36.600 --> 00:15:38.689 align:start position:0% with transaction announces hedera doesn't<00:15:37.019> use<00:15:37.260> transaction<00:15:37.680> nonsense<00:15:38.220> they 00:15:38.689 --> 00:15:38.699 align:start position:0% doesn't use transaction nonsense they 00:15:38.699 --> 00:15:40.850 align:start position:0% doesn't use transaction nonsense they use<00:15:38.880> timestamps<00:15:39.600> and<00:15:39.720> you<00:15:39.899> can<00:15:40.019> do<00:15:40.260> neat 00:15:40.850 --> 00:15:40.860 align:start position:0% use timestamps and you can do neat 00:15:40.860 --> 00:15:42.470 align:start position:0% use timestamps and you can do neat little<00:15:40.980> tricks<00:15:41.279> with<00:15:41.459> your<00:15:41.639> valid<00:15:42.060> start<00:15:42.240> time 00:15:42.470 --> 00:15:42.480 align:start position:0% little tricks with your valid start time 00:15:42.480 --> 00:15:44.090 align:start position:0% little tricks with your valid start time and<00:15:42.720> valid<00:15:43.019> duration<00:15:43.260> down<00:15:43.800> to<00:15:43.980> the 00:15:44.090 --> 00:15:44.100 align:start position:0% and valid duration down to the 00:15:44.100 --> 00:15:46.009 align:start position:0% and valid duration down to the nanoseconds<00:15:44.760> to<00:15:45.120> ensure<00:15:45.420> uniqueness<00:15:45.899> for 00:15:46.009 --> 00:15:46.019 align:start position:0% nanoseconds to ensure uniqueness for 00:15:46.019 --> 00:15:47.810 align:start position:0% nanoseconds to ensure uniqueness for your<00:15:46.199> transactions 00:15:47.810 --> 00:15:47.820 align:start position:0% your transactions 00:15:47.820 --> 00:15:49.310 align:start position:0% your transactions um but<00:15:48.000> this<00:15:48.120> is<00:15:48.300> a<00:15:48.480> problem<00:15:48.600> that<00:15:48.839> ethereum 00:15:49.310 --> 00:15:49.320 align:start position:0% um but this is a problem that ethereum 00:15:49.320 --> 00:15:52.250 align:start position:0% um but this is a problem that ethereum very<00:15:49.920> strictly<00:15:50.220> uses<00:15:50.579> their<00:15:50.760> notes<00:15:51.240> and<00:15:51.959> they 00:15:52.250 --> 00:15:52.260 align:start position:0% very strictly uses their notes and they 00:15:52.260 --> 00:15:53.810 align:start position:0% very strictly uses their notes and they really<00:15:52.380> use<00:15:52.560> their<00:15:52.740> notes<00:15:53.100> as<00:15:53.220> sequence 00:15:53.810 --> 00:15:53.820 align:start position:0% really use their notes as sequence 00:15:53.820 --> 00:15:55.430 align:start position:0% really use their notes as sequence numbers<00:15:54.060> I<00:15:54.480> really<00:15:54.660> wish<00:15:54.899> that<00:15:55.139> when<00:15:55.320> they 00:15:55.430 --> 00:15:55.440 align:start position:0% numbers I really wish that when they 00:15:55.440 --> 00:15:57.050 align:start position:0% numbers I really wish that when they started<00:15:55.740> this<00:15:55.860> spec<00:15:56.100> instead<00:15:56.639> of<00:15:56.760> calling<00:15:57.000> it 00:15:57.050 --> 00:15:57.060 align:start position:0% started this spec instead of calling it 00:15:57.060 --> 00:15:58.490 align:start position:0% started this spec instead of calling it a<00:15:57.180> known<00:15:57.300> so<00:15:57.480> we<00:15:57.600> call<00:15:57.660> it<00:15:57.779> a<00:15:57.899> sequence<00:15:58.260> number 00:15:58.490 --> 00:15:58.500 align:start position:0% a known so we call it a sequence number 00:15:58.500 --> 00:16:00.650 align:start position:0% a known so we call it a sequence number but<00:15:59.160> unfortunately<00:15:59.579> that<00:15:59.820> ship<00:16:00.060> has<00:16:00.240> sailed 00:16:00.650 --> 00:16:00.660 align:start position:0% but unfortunately that ship has sailed 00:16:00.660 --> 00:16:02.569 align:start position:0% but unfortunately that ship has sailed in<00:16:01.199> nearly<00:16:01.560> every<00:16:01.740> blockchain<00:16:02.220> out<00:16:02.459> there 00:16:02.569 --> 00:16:02.579 align:start position:0% in nearly every blockchain out there 00:16:02.579 --> 00:16:04.129 align:start position:0% in nearly every blockchain out there when<00:16:02.760> you<00:16:02.880> see<00:16:03.000> notes<00:16:03.360> in<00:16:03.480> a<00:16:03.600> transaction<00:16:03.899> you 00:16:04.129 --> 00:16:04.139 align:start position:0% when you see notes in a transaction you 00:16:04.139 --> 00:16:06.350 align:start position:0% when you see notes in a transaction you know<00:16:04.260> it<00:16:04.440> seeks<00:16:04.740> its<00:16:04.980> sequence<00:16:05.220> number<00:16:05.880> except 00:16:06.350 --> 00:16:06.360 align:start position:0% know it seeks its sequence number except 00:16:06.360 --> 00:16:08.389 align:start position:0% know it seeks its sequence number except for<00:16:06.540> one<00:16:06.779> I<00:16:07.440> really<00:16:07.560> had<00:16:07.740> to<00:16:07.860> dig<00:16:07.980> deep<00:16:08.160> in<00:16:08.339> my 00:16:08.389 --> 00:16:08.399 align:start position:0% for one I really had to dig deep in my 00:16:08.399 --> 00:16:10.550 align:start position:0% for one I really had to dig deep in my memory<00:16:08.579> for<00:16:08.940> this<00:16:09.120> one<00:16:09.240> this<00:16:09.959> is<00:16:10.079> a<00:16:10.199> blockchain 00:16:10.550 --> 00:16:10.560 align:start position:0% memory for this one this is a blockchain 00:16:10.560 --> 00:16:13.250 align:start position:0% memory for this one this is a blockchain out<00:16:10.740> of<00:16:10.920> China<00:16:11.040> that's<00:16:11.279> very<00:16:11.519> ethereum-like 00:16:13.250 --> 00:16:13.260 align:start position:0% out of China that's very ethereum-like 00:16:13.260 --> 00:16:15.769 align:start position:0% out of China that's very ethereum-like um but<00:16:14.040> it<00:16:14.220> doesn't<00:16:14.940> um 00:16:15.769 --> 00:16:15.779 align:start position:0% um but it doesn't um 00:16:15.779 --> 00:16:17.870 align:start position:0% um but it doesn't um it<00:16:16.320> doesn't<00:16:16.500> do<00:16:16.740> the<00:16:16.980> transaction<00:16:17.399> sequence 00:16:17.870 --> 00:16:17.880 align:start position:0% it doesn't do the transaction sequence 00:16:17.880 --> 00:16:19.610 align:start position:0% it doesn't do the transaction sequence numbers<00:16:18.000> and<00:16:18.240> the<00:16:18.360> gnosis<00:16:18.660> it<00:16:19.440> actually 00:16:19.610 --> 00:16:19.620 align:start position:0% numbers and the gnosis it actually 00:16:19.620 --> 00:16:22.250 align:start position:0% numbers and the gnosis it actually treats<00:16:20.459> them<00:16:20.579> as<00:16:20.699> a<00:16:20.820> true<00:16:20.880> note<00:16:21.180> great<00:16:22.019> for 00:16:22.250 --> 00:16:22.260 align:start position:0% treats them as a true note great for 00:16:22.260 --> 00:16:24.230 align:start position:0% treats them as a true note great for performance<00:16:22.620> and<00:16:22.800> throughput<00:16:23.160> horrible<00:16:24.000> for 00:16:24.230 --> 00:16:24.240 align:start position:0% performance and throughput horrible for 00:16:24.240 --> 00:16:26.689 align:start position:0% performance and throughput horrible for memory<00:16:24.600> so<00:16:25.139> not<00:16:25.260> everyone<00:16:25.500> does<00:16:25.860> this<00:16:26.040> but<00:16:26.579> we 00:16:26.689 --> 00:16:26.699 align:start position:0% memory so not everyone does this but we 00:16:26.699 --> 00:16:28.370 align:start position:0% memory so not everyone does this but we had<00:16:26.880> to<00:16:27.000> adapt<00:16:27.240> announces 00:16:28.370 --> 00:16:28.380 align:start position:0% had to adapt announces 00:16:28.380 --> 00:16:31.129 align:start position:0% had to adapt announces the<00:16:28.800> next<00:16:28.920> issue<00:16:29.279> was<00:16:29.519> meta<00:16:29.940> transactions<00:16:30.480> we 00:16:31.129 --> 00:16:31.139 align:start position:0% the next issue was meta transactions we 00:16:31.139 --> 00:16:32.389 align:start position:0% the next issue was meta transactions we took<00:16:31.320> a<00:16:31.500> process<00:16:31.680> where<00:16:31.920> we<00:16:32.040> wrapped<00:16:32.339> the 00:16:32.389 --> 00:16:32.399 align:start position:0% took a process where we wrapped the 00:16:32.399 --> 00:16:34.550 align:start position:0% took a process where we wrapped the transactions<00:16:32.880> of<00:16:33.060> the<00:16:33.120> ethereum<00:16:33.420> rlp<00:16:33.839> inside 00:16:34.550 --> 00:16:34.560 align:start position:0% transactions of the ethereum rlp inside 00:16:34.560 --> 00:16:37.430 align:start position:0% transactions of the ethereum rlp inside of<00:16:35.279> a<00:16:35.399> hedera<00:16:35.880> transaction<00:16:36.240> and<00:16:37.019> we<00:16:37.139> started 00:16:37.430 --> 00:16:37.440 align:start position:0% of a hedera transaction and we started 00:16:37.440 --> 00:16:38.749 align:start position:0% of a hedera transaction and we started the<00:16:37.560> hedera<00:16:37.920> transaction<00:16:38.160> with<00:16:38.399> one<00:16:38.579> account 00:16:38.749 --> 00:16:38.759 align:start position:0% the hedera transaction with one account 00:16:38.759 --> 00:16:40.310 align:start position:0% the hedera transaction with one account and<00:16:39.300> the<00:16:39.420> inner<00:16:39.540> account<00:16:39.660> was<00:16:39.899> responsible 00:16:40.310 --> 00:16:40.320 align:start position:0% and the inner account was responsible 00:16:40.320 --> 00:16:42.230 align:start position:0% and the inner account was responsible for<00:16:40.500> it<00:16:40.680> this<00:16:41.100> is<00:16:41.220> you<00:16:41.459> know<00:16:41.519> plastic<00:16:41.880> protocol 00:16:42.230 --> 00:16:42.240 align:start position:0% for it this is you know plastic protocol 00:16:42.240 --> 00:16:44.509 align:start position:0% for it this is you know plastic protocol level<00:16:42.480> meta<00:16:43.320> transactions<00:16:43.800> there's<00:16:44.220> not<00:16:44.399> too 00:16:44.509 --> 00:16:44.519 align:start position:0% level meta transactions there's not too 00:16:44.519 --> 00:16:46.550 align:start position:0% level meta transactions there's not too much<00:16:44.639> fancy<00:16:45.000> stuff<00:16:45.180> going<00:16:45.420> on<00:16:45.540> with<00:16:45.720> it<00:16:45.899> and<00:16:46.440> it 00:16:46.550 --> 00:16:46.560 align:start position:0% much fancy stuff going on with it and it 00:16:46.560 --> 00:16:48.230 align:start position:0% much fancy stuff going on with it and it just<00:16:46.740> transparently<00:16:47.279> works 00:16:48.230 --> 00:16:48.240 align:start position:0% just transparently works 00:16:48.240 --> 00:16:49.730 align:start position:0% just transparently works um the<00:16:48.420> Relay<00:16:48.720> can<00:16:48.959> agree<00:16:49.139> to<00:16:49.259> pay<00:16:49.380> for<00:16:49.560> none 00:16:49.730 --> 00:16:49.740 align:start position:0% um the Relay can agree to pay for none 00:16:49.740 --> 00:16:51.230 align:start position:0% um the Relay can agree to pay for none of<00:16:49.800> the<00:16:49.920> gas<00:16:50.040> some<00:16:50.220> of<00:16:50.399> the<00:16:50.459> gas<00:16:50.579> or<00:16:50.759> all<00:16:51.000> of<00:16:51.120> the 00:16:51.230 --> 00:16:51.240 align:start position:0% of the gas some of the gas or all of the 00:16:51.240 --> 00:16:52.850 align:start position:0% of the gas some of the gas or all of the gas<00:16:51.360> and<00:16:51.959> the<00:16:52.139> transaction<00:16:52.440> on<00:16:52.680> the<00:16:52.800> inside 00:16:52.850 --> 00:16:52.860 align:start position:0% gas and the transaction on the inside 00:16:52.860 --> 00:16:54.769 align:start position:0% gas and the transaction on the inside was<00:16:53.220> responsible<00:16:53.639> for<00:16:53.759> the<00:16:53.940> rest<00:16:54.060> of<00:16:54.240> it<00:16:54.360> once 00:16:54.769 --> 00:16:54.779 align:start position:0% was responsible for the rest of it once 00:16:54.779 --> 00:16:56.930 align:start position:0% was responsible for the rest of it once we<00:16:54.899> map<00:16:55.079> that<00:16:55.320> transaction<00:16:55.620> to<00:16:55.860> a<00:16:55.980> user<00:16:56.279> and<00:16:56.759> if 00:16:56.930 --> 00:16:56.940 align:start position:0% we map that transaction to a user and if 00:16:56.940 --> 00:16:58.670 align:start position:0% we map that transaction to a user and if the<00:16:57.060> relayer<00:16:57.480> sends<00:16:57.779> garbage<00:16:58.019> into<00:16:58.259> the<00:16:58.500> into 00:16:58.670 --> 00:16:58.680 align:start position:0% the relayer sends garbage into the into 00:16:58.680 --> 00:17:00.710 align:start position:0% the relayer sends garbage into the into pedera<00:16:59.519> we<00:16:59.880> throw<00:17:00.000> it<00:17:00.180> away<00:17:00.240> and<00:17:00.480> we<00:17:00.600> just 00:17:00.710 --> 00:17:00.720 align:start position:0% pedera we throw it away and we just 00:17:00.720 --> 00:17:02.269 align:start position:0% pedera we throw it away and we just charge<00:17:00.839> the<00:17:01.079> relayer<00:17:01.500> for<00:17:01.680> the<00:17:01.920> garbage<00:17:02.160> that 00:17:02.269 --> 00:17:02.279 align:start position:0% charge the relayer for the garbage that 00:17:02.279 --> 00:17:04.069 align:start position:0% charge the relayer for the garbage that they<00:17:02.459> brought<00:17:02.579> into<00:17:02.699> the<00:17:02.940> system<00:17:03.120> and<00:17:03.839> it 00:17:04.069 --> 00:17:04.079 align:start position:0% they brought into the system and it 00:17:04.079 --> 00:17:05.510 align:start position:0% they brought into the system and it works<00:17:04.260> really<00:17:04.380> well<00:17:04.620> and<00:17:04.799> it<00:17:04.980> balances<00:17:05.339> great 00:17:05.510 --> 00:17:05.520 align:start position:0% works really well and it balances great 00:17:05.520 --> 00:17:07.970 align:start position:0% works really well and it balances great then<00:17:05.760> spins<00:17:06.059> like<00:17:06.240> a<00:17:06.419> top 00:17:07.970 --> 00:17:07.980 align:start position:0% then spins like a top 00:17:07.980 --> 00:17:10.970 align:start position:0% then spins like a top um<00:17:08.040> so<00:17:08.640> so<00:17:08.880> if<00:17:09.179> we<00:17:09.360> need<00:17:09.480> to<00:17:09.660> get<00:17:10.319> um<00:17:10.380> meta 00:17:10.970 --> 00:17:10.980 align:start position:0% um so so if we need to get um meta 00:17:10.980 --> 00:17:13.970 align:start position:0% um so so if we need to get um meta transactions<00:17:11.520> into<00:17:11.939> into<00:17:12.660> ethereum<00:17:13.500> mainnet 00:17:13.970 --> 00:17:13.980 align:start position:0% transactions into into ethereum mainnet 00:17:13.980 --> 00:17:16.549 align:start position:0% transactions into into ethereum mainnet the<00:17:14.339> way<00:17:14.520> to<00:17:14.699> do<00:17:14.819> it<00:17:14.939> would<00:17:15.120> be<00:17:15.179> through<00:17:15.540> uh<00:17:16.380> in 00:17:16.549 --> 00:17:16.559 align:start position:0% the way to do it would be through uh in 00:17:16.559 --> 00:17:17.990 align:start position:0% the way to do it would be through uh in shredding<00:17:16.980> in<00:17:17.160> the<00:17:17.280> protocol<00:17:17.459> would<00:17:17.760> be<00:17:17.880> the 00:17:17.990 --> 00:17:18.000 align:start position:0% shredding in the protocol would be the 00:17:18.000 --> 00:17:19.010 align:start position:0% shredding in the protocol would be the best<00:17:18.120> way 00:17:19.010 --> 00:17:19.020 align:start position:0% best way 00:17:19.020 --> 00:17:20.390 align:start position:0% best way um<00:17:19.079> what<00:17:19.260> we<00:17:19.439> have<00:17:19.559> right<00:17:19.740> now<00:17:19.860> with<00:17:20.220> the 00:17:20.390 --> 00:17:20.400 align:start position:0% um what we have right now with the 00:17:20.400 --> 00:17:22.130 align:start position:0% um what we have right now with the Cooperative<00:17:20.760> impersonation<00:17:21.360> going<00:17:21.600> on<00:17:21.780> is<00:17:22.020> is 00:17:22.130 --> 00:17:22.140 align:start position:0% Cooperative impersonation going on is is 00:17:22.140 --> 00:17:23.689 align:start position:0% Cooperative impersonation going on is is a<00:17:22.439> good<00:17:22.559> enough<00:17:22.679> way<00:17:22.919> for<00:17:23.160> people<00:17:23.339> that<00:17:23.520> want 00:17:23.689 --> 00:17:23.699 align:start position:0% a good enough way for people that want 00:17:23.699 --> 00:17:24.829 align:start position:0% a good enough way for people that want to<00:17:23.819> participate 00:17:24.829 --> 00:17:24.839 align:start position:0% to participate 00:17:24.839 --> 00:17:27.110 align:start position:0% to participate but<00:17:25.199> account<00:17:25.439> abstraction<00:17:25.980> also<00:17:26.459> has<00:17:26.939> the 00:17:27.110 --> 00:17:27.120 align:start position:0% but account abstraction also has the 00:17:27.120 --> 00:17:28.730 align:start position:0% but account abstraction also has the potential<00:17:27.419> to<00:17:27.540> solve<00:17:27.839> this<00:17:27.959> problem<00:17:28.199> of 00:17:28.730 --> 00:17:28.740 align:start position:0% potential to solve this problem of 00:17:28.740 --> 00:17:30.950 align:start position:0% potential to solve this problem of allowing<00:17:29.100> people<00:17:29.280> to<00:17:29.640> to<00:17:29.940> pay<00:17:30.240> in<00:17:30.480> one<00:17:30.780> account 00:17:30.950 --> 00:17:30.960 align:start position:0% allowing people to to pay in one account 00:17:30.960 --> 00:17:33.169 align:start position:0% allowing people to to pay in one account and<00:17:31.320> act<00:17:31.500> in<00:17:31.679> another 00:17:33.169 --> 00:17:33.179 align:start position:0% and act in another 00:17:33.179 --> 00:17:35.150 align:start position:0% and act in another now<00:17:33.600> I<00:17:33.660> promised<00:17:34.020> I'd<00:17:34.140> come<00:17:34.320> back<00:17:34.440> to<00:17:34.620> this<00:17:34.740> off 00:17:35.150 --> 00:17:35.160 align:start position:0% now I promised I'd come back to this off 00:17:35.160 --> 00:17:36.890 align:start position:0% now I promised I'd come back to this off and<00:17:35.340> off<00:17:35.460> call 00:17:36.890 --> 00:17:36.900 align:start position:0% and off call 00:17:36.900 --> 00:17:38.210 align:start position:0% and off call um<00:17:37.020> so<00:17:37.200> it's<00:17:37.380> not<00:17:37.500> just<00:17:37.679> that<00:17:37.860> other<00:17:38.039> people 00:17:38.210 --> 00:17:38.220 align:start position:0% um so it's not just that other people 00:17:38.220 --> 00:17:40.250 align:start position:0% um so it's not just that other people don't<00:17:38.460> do<00:17:38.640> it<00:17:38.820> it's<00:17:39.299> that<00:17:39.480> other<00:17:39.660> people<00:17:39.840> solve 00:17:40.250 --> 00:17:40.260 align:start position:0% don't do it it's that other people solve 00:17:40.260 --> 00:17:43.250 align:start position:0% don't do it it's that other people solve the<00:17:40.380> problems<00:17:40.799> directly<00:17:41.520> in<00:17:41.760> the<00:17:41.880> protocol<00:17:42.260> so 00:17:43.250 --> 00:17:43.260 align:start position:0% the problems directly in the protocol so 00:17:43.260 --> 00:17:45.770 align:start position:0% the problems directly in the protocol so I<00:17:43.380> think<00:17:43.559> that<00:17:43.919> the<00:17:44.760> people<00:17:44.940> don't<00:17:45.179> use<00:17:45.419> often 00:17:45.770 --> 00:17:45.780 align:start position:0% I think that the people don't use often 00:17:45.780 --> 00:17:48.110 align:start position:0% I think that the people don't use often off<00:17:45.960> call<00:17:46.200> is<00:17:46.559> their<00:17:46.860> solution<00:17:47.400> I<00:17:47.700> think<00:17:47.760> is<00:17:47.880> is 00:17:48.110 --> 00:17:48.120 align:start position:0% off call is their solution I think is is 00:17:48.120 --> 00:17:49.789 align:start position:0% off call is their solution I think is is stronger<00:17:48.539> evidence<00:17:48.840> and<00:17:49.080> I<00:17:49.200> think<00:17:49.260> on<00:17:49.440> balance 00:17:49.789 --> 00:17:49.799 align:start position:0% stronger evidence and I think on balance 00:17:49.799 --> 00:17:50.930 align:start position:0% stronger evidence and I think on balance is<00:17:49.919> going<00:17:50.100> to<00:17:50.160> come<00:17:50.220> by<00:17:50.340> even<00:17:50.520> if<00:17:50.640> you<00:17:50.760> take 00:17:50.930 --> 00:17:50.940 align:start position:0% is going to come by even if you take 00:17:50.940 --> 00:17:52.610 align:start position:0% is going to come by even if you take these<00:17:51.059> evidences<00:17:51.480> out<00:17:51.720> that<00:17:52.140> it's<00:17:52.320> not<00:17:52.440> worth 00:17:52.610 --> 00:17:52.620 align:start position:0% these evidences out that it's not worth 00:17:52.620 --> 00:17:53.810 align:start position:0% these evidences out that it's not worth the<00:17:52.799> risk 00:17:53.810 --> 00:17:53.820 align:start position:0% the risk 00:17:53.820 --> 00:17:55.250 align:start position:0% the risk um<00:17:53.880> maybe<00:17:54.120> we<00:17:54.299> should<00:17:54.419> examine<00:17:54.780> pay<00:17:55.140> your 00:17:55.250 --> 00:17:55.260 align:start position:0% um maybe we should examine pay your 00:17:55.260 --> 00:17:57.590 align:start position:0% um maybe we should examine pay your executor<00:17:55.799> splits<00:17:56.220> to<00:17:57.000> solve<00:17:57.240> some<00:17:57.419> of<00:17:57.480> these 00:17:57.590 --> 00:17:57.600 align:start position:0% executor splits to solve some of these 00:17:57.600 --> 00:17:59.630 align:start position:0% executor splits to solve some of these off<00:17:57.720> and<00:17:57.840> off<00:17:57.960> call<00:17:58.260> problems 00:17:59.630 --> 00:17:59.640 align:start position:0% off and off call problems 00:17:59.640 --> 00:18:02.390 align:start position:0% off and off call problems and<00:18:00.240> finally<00:18:00.480> there's<00:18:00.720> Json<00:18:01.020> RPC<00:18:01.559> this<00:18:02.280> is 00:18:02.390 --> 00:18:02.400 align:start position:0% and finally there's Json RPC this is 00:18:02.400 --> 00:18:04.070 align:start position:0% and finally there's Json RPC this is truly<00:18:02.760> the<00:18:03.000> last<00:18:03.179> mile<00:18:03.419> of<00:18:03.660> ethereum 00:18:04.070 --> 00:18:04.080 align:start position:0% truly the last mile of ethereum 00:18:04.080 --> 00:18:06.110 align:start position:0% truly the last mile of ethereum compatibility<00:18:04.679> if<00:18:05.280> you<00:18:05.460> don't<00:18:05.580> speak<00:18:05.760> Json 00:18:06.110 --> 00:18:06.120 align:start position:0% compatibility if you don't speak Json 00:18:06.120 --> 00:18:08.690 align:start position:0% compatibility if you don't speak Json RPC<00:18:06.720> all<00:18:07.380> the<00:18:07.500> masses<00:18:07.799> of<00:18:07.980> retail<00:18:08.280> tools<00:18:08.580> and 00:18:08.690 --> 00:18:08.700 align:start position:0% RPC all the masses of retail tools and 00:18:08.700 --> 00:18:10.610 align:start position:0% RPC all the masses of retail tools and developer<00:18:09.059> tools<00:18:09.419> will<00:18:09.960> not<00:18:10.080> talk<00:18:10.320> to<00:18:10.440> your 00:18:10.610 --> 00:18:10.620 align:start position:0% developer tools will not talk to your 00:18:10.620 --> 00:18:12.950 align:start position:0% developer tools will not talk to your blockchain<00:18:11.039> so<00:18:11.760> we<00:18:11.880> had<00:18:12.059> to<00:18:12.179> write<00:18:12.360> up<00:18:12.539> a<00:18:12.720> relay 00:18:12.950 --> 00:18:12.960 align:start position:0% blockchain so we had to write up a relay 00:18:12.960 --> 00:18:14.210 align:start position:0% blockchain so we had to write up a relay server<00:18:13.260> that<00:18:13.380> would<00:18:13.559> stand<00:18:13.679> up<00:18:13.860> in<00:18:13.980> the<00:18:14.100> middle 00:18:14.210 --> 00:18:14.220 align:start position:0% server that would stand up in the middle 00:18:14.220 --> 00:18:16.789 align:start position:0% server that would stand up in the middle take<00:18:14.820> those<00:18:15.059> RPC<00:18:15.539> calls<00:18:15.960> send<00:18:16.380> it<00:18:16.559> out<00:18:16.679> to 00:18:16.789 --> 00:18:16.799 align:start position:0% take those RPC calls send it out to 00:18:16.799 --> 00:18:18.590 align:start position:0% take those RPC calls send it out to consensus<00:18:17.220> layer<00:18:17.520> send<00:18:17.940> it<00:18:18.059> to<00:18:18.179> our<00:18:18.299> mirror 00:18:18.590 --> 00:18:18.600 align:start position:0% consensus layer send it to our mirror 00:18:18.600 --> 00:18:20.330 align:start position:0% consensus layer send it to our mirror node<00:18:18.840> and<00:18:19.260> this<00:18:19.380> looks<00:18:19.679> a<00:18:19.799> lot<00:18:19.919> like<00:18:20.100> the 00:18:20.330 --> 00:18:20.340 align:start position:0% node and this looks a lot like the 00:18:20.340 --> 00:18:22.430 align:start position:0% node and this looks a lot like the portal<00:18:20.640> Network<00:18:20.820> so<00:18:21.539> the<00:18:21.780> portal<00:18:22.020> Network's 00:18:22.430 --> 00:18:22.440 align:start position:0% portal Network so the portal Network's 00:18:22.440 --> 00:18:24.110 align:start position:0% portal Network so the portal Network's idea<00:18:22.740> of<00:18:22.919> having<00:18:23.100> a<00:18:23.280> proxy<00:18:23.640> that's<00:18:23.820> going<00:18:24.000> to 00:18:24.110 --> 00:18:24.120 align:start position:0% idea of having a proxy that's going to 00:18:24.120 --> 00:18:26.690 align:start position:0% idea of having a proxy that's going to go<00:18:24.179> through<00:18:24.360> and<00:18:24.600> talk<00:18:24.840> to<00:18:25.520> systems<00:18:26.520> that 00:18:26.690 --> 00:18:26.700 align:start position:0% go through and talk to systems that 00:18:26.700 --> 00:18:28.370 align:start position:0% go through and talk to systems that aren't<00:18:26.940> necessarily<00:18:27.360> live<00:18:27.660> but<00:18:28.200> have 00:18:28.370 --> 00:18:28.380 align:start position:0% aren't necessarily live but have 00:18:28.380 --> 00:18:30.289 align:start position:0% aren't necessarily live but have verifiable<00:18:28.980> information<00:18:29.220> it's<00:18:30.059> going<00:18:30.240> to 00:18:30.289 --> 00:18:30.299 align:start position:0% verifiable information it's going to 00:18:30.299 --> 00:18:32.930 align:start position:0% verifiable information it's going to work<00:18:30.419> great<00:18:30.660> it<00:18:30.960> works<00:18:31.140> great<00:18:31.260> for<00:18:31.500> us 00:18:32.930 --> 00:18:32.940 align:start position:0% work great it works great for us 00:18:32.940 --> 00:18:35.270 align:start position:0% work great it works great for us um<00:18:33.000> so<00:18:33.360> this<00:18:33.480> is<00:18:33.600> something<00:18:33.780> this<00:18:34.260> is 00:18:35.270 --> 00:18:35.280 align:start position:0% um so this is something this is 00:18:35.280 --> 00:18:36.409 align:start position:0% um so this is something this is um something<00:18:35.580> that<00:18:35.820> I<00:18:35.940> have<00:18:36.000> a<00:18:36.120> lot<00:18:36.179> of<00:18:36.299> Hope 00:18:36.409 --> 00:18:36.419 align:start position:0% um something that I have a lot of Hope 00:18:36.419 --> 00:18:37.789 align:start position:0% um something that I have a lot of Hope for<00:18:36.600> I've<00:18:36.720> been<00:18:36.840> following<00:18:37.140> Piper's<00:18:37.559> work<00:18:37.679> for 00:18:37.789 --> 00:18:37.799 align:start position:0% for I've been following Piper's work for 00:18:37.799 --> 00:18:39.830 align:start position:0% for I've been following Piper's work for quite<00:18:37.980> a<00:18:38.100> while<00:18:38.160> I<00:18:38.340> think<00:18:38.460> it's<00:18:38.580> great<00:18:38.940> I<00:18:39.780> think 00:18:39.830 --> 00:18:39.840 align:start position:0% quite a while I think it's great I think 00:18:39.840 --> 00:18:41.810 align:start position:0% quite a while I think it's great I think that<00:18:39.960> covers<00:18:40.260> most<00:18:40.380> oh<00:18:40.620> yeah<00:18:40.799> one<00:18:41.039> last<00:18:41.160> ax<00:18:41.580> ask 00:18:41.810 --> 00:18:41.820 align:start position:0% that covers most oh yeah one last ax ask 00:18:41.820 --> 00:18:45.110 align:start position:0% that covers most oh yeah one last ax ask this<00:18:42.179> is<00:18:42.419> this<00:18:42.900> is<00:18:43.020> my<00:18:43.320> uh<00:18:43.559> last<00:18:43.980> point 00:18:45.110 --> 00:18:45.120 align:start position:0% this is this is my uh last point 00:18:45.120 --> 00:18:47.210 align:start position:0% this is this is my uh last point can<00:18:45.539> we<00:18:45.720> get<00:18:45.900> an<00:18:46.020> RPC<00:18:46.440> system<00:18:46.679> that<00:18:47.039> doesn't 00:18:47.210 --> 00:18:47.220 align:start position:0% can we get an RPC system that doesn't 00:18:47.220 --> 00:18:49.190 align:start position:0% can we get an RPC system that doesn't put<00:18:47.580> everything<00:18:47.820> in<00:18:48.059> the<00:18:48.179> post<00:18:48.360> body<00:18:48.600> can<00:18:48.960> we 00:18:49.190 --> 00:18:49.200 align:start position:0% put everything in the post body can we 00:18:49.200 --> 00:18:52.610 align:start position:0% put everything in the post body can we please<00:18:49.679> get<00:18:50.039> arrest<00:18:50.280> like<00:18:50.640> Json<00:18:50.940> RPC<00:18:51.539> that<00:18:52.500> is 00:18:52.610 --> 00:18:52.620 align:start position:0% please get arrest like Json RPC that is 00:18:52.620 --> 00:18:54.830 align:start position:0% please get arrest like Json RPC that is this<00:18:52.860> has<00:18:53.160> huge<00:18:53.520> impacts<00:18:53.940> on<00:18:54.120> load<00:18:54.419> balancers 00:18:54.830 --> 00:18:54.840 align:start position:0% this has huge impacts on load balancers 00:18:54.840 --> 00:18:57.529 align:start position:0% this has huge impacts on load balancers huge<00:18:55.559> impacts<00:18:55.919> on<00:18:56.039> caching<00:18:56.520> and<00:18:57.120> all<00:18:57.240> sorts<00:18:57.480> of 00:18:57.529 --> 00:18:57.539 align:start position:0% huge impacts on caching and all sorts of 00:18:57.539 --> 00:18:58.970 align:start position:0% huge impacts on caching and all sorts of other<00:18:57.660> items<00:18:57.960> we<00:18:58.080> have<00:18:58.200> to<00:18:58.320> put<00:18:58.380> this<00:18:58.500> into<00:18:58.679> the 00:18:58.970 --> 00:18:58.980 align:start position:0% other items we have to put this into the 00:18:58.980 --> 00:19:01.190 align:start position:0% other items we have to put this into the application<00:18:59.340> we<00:18:59.640> can't<00:18:59.760> put<00:19:00.059> good<00:19:00.419> front<00:19:00.840> ends 00:19:01.190 --> 00:19:01.200 align:start position:0% application we can't put good front ends 00:19:01.200 --> 00:19:03.529 align:start position:0% application we can't put good front ends on<00:19:01.320> it<00:19:01.440> and<00:19:01.620> split<00:19:01.860> the<00:19:01.980> balance<00:19:02.340> easier<00:19:02.940> it's 00:19:03.529 --> 00:19:03.539 align:start position:0% on it and split the balance easier it's 00:19:03.539 --> 00:19:04.970 align:start position:0% on it and split the balance easier it's just<00:19:03.720> as<00:19:03.840> simple<00:19:04.020> as<00:19:04.140> putting<00:19:04.500> the<00:19:04.620> method 00:19:04.970 --> 00:19:04.980 align:start position:0% just as simple as putting the method 00:19:04.980 --> 00:19:08.450 align:start position:0% just as simple as putting the method name<00:19:05.220> in<00:19:05.700> the<00:19:05.820> URL<00:19:06.059> would<00:19:06.299> have<00:19:06.539> huge<00:19:06.960> impact 00:19:08.450 --> 00:19:08.460 align:start position:0% name in the URL would have huge impact 00:19:08.460 --> 00:19:09.529 align:start position:0% name in the URL would have huge impact um<00:19:08.580> and<00:19:08.760> so<00:19:08.880> that's<00:19:09.000> one<00:19:09.120> of<00:19:09.240> the<00:19:09.299> issues 00:19:09.529 --> 00:19:09.539 align:start position:0% um and so that's one of the issues 00:19:09.539 --> 00:19:12.049 align:start position:0% um and so that's one of the issues because<00:19:09.740> hedera<00:19:10.740> uses<00:19:10.860> grpc<00:19:11.520> and<00:19:11.700> it's<00:19:11.880> got 00:19:12.049 --> 00:19:12.059 align:start position:0% because hedera uses grpc and it's got 00:19:12.059 --> 00:19:15.169 align:start position:0% because hedera uses grpc and it's got amazing<00:19:12.480> load<00:19:12.840> balancing<00:19:13.260> implications 00:19:15.169 --> 00:19:15.179 align:start position:0% amazing load balancing implications 00:19:15.179 --> 00:19:16.789 align:start position:0% amazing load balancing implications um but<00:19:15.660> we<00:19:15.840> can't<00:19:15.960> quite<00:19:16.080> do<00:19:16.320> the<00:19:16.440> same<00:19:16.559> tricks 00:19:16.789 --> 00:19:16.799 align:start position:0% um but we can't quite do the same tricks 00:19:16.799 --> 00:19:19.190 align:start position:0% um but we can't quite do the same tricks that<00:19:16.919> we<00:19:17.039> do<00:19:17.160> with<00:19:17.340> uh<00:19:17.460> with<00:19:17.760> Json<00:19:18.059> RPC 00:19:19.190 --> 00:19:19.200 align:start position:0% that we do with uh with Json RPC 00:19:19.200 --> 00:19:21.350 align:start position:0% that we do with uh with Json RPC so<00:19:19.799> in<00:19:20.039> the<00:19:20.160> 25<00:19:20.280> minutes<00:19:20.640> that<00:19:20.820> I<00:19:21.000> had<00:19:21.120> to<00:19:21.240> talk 00:19:21.350 --> 00:19:21.360 align:start position:0% so in the 25 minutes that I had to talk 00:19:21.360 --> 00:19:23.390 align:start position:0% so in the 25 minutes that I had to talk or<00:19:21.720> the<00:19:21.900> 20<00:19:22.020> minutes<00:19:22.200> I<00:19:22.380> was<00:19:22.500> allocated 00:19:23.390 --> 00:19:23.400 align:start position:0% or the 20 minutes I was allocated 00:19:23.400 --> 00:19:25.190 align:start position:0% or the 20 minutes I was allocated um those<00:19:23.580> are<00:19:23.700> my<00:19:23.820> conclusions<00:19:24.299> of<00:19:24.600> of<00:19:24.960> what 00:19:25.190 --> 00:19:25.200 align:start position:0% um those are my conclusions of of what 00:19:25.200 --> 00:19:27.470 align:start position:0% um those are my conclusions of of what we<00:19:25.320> could<00:19:25.440> really<00:19:25.559> learn<00:19:25.740> from<00:19:25.980> from<00:19:26.160> ethereum 00:19:27.470 --> 00:19:27.480 align:start position:0% we could really learn from from ethereum 00:19:27.480 --> 00:19:28.850 align:start position:0% we could really learn from from ethereum um<00:19:27.600> from<00:19:27.960> from<00:19:28.080> other<00:19:28.320> networks<00:19:28.620> and<00:19:28.740> what 00:19:28.850 --> 00:19:28.860 align:start position:0% um from from other networks and what 00:19:28.860 --> 00:19:30.830 align:start position:0% um from from other networks and what ethereum<00:19:29.220> could<00:19:29.400> apply<00:19:29.880> I<00:19:30.539> think<00:19:30.660> account 00:19:30.830 --> 00:19:30.840 align:start position:0% ethereum could apply I think account 00:19:30.840 --> 00:19:32.690 align:start position:0% ethereum could apply I think account abstraction<00:19:31.380> has<00:19:31.679> great<00:19:31.980> future<00:19:32.160> potential 00:19:32.690 --> 00:19:32.700 align:start position:0% abstraction has great future potential 00:19:32.700 --> 00:19:34.730 align:start position:0% abstraction has great future potential to<00:19:32.880> solve<00:19:33.120> a<00:19:33.240> lot<00:19:33.299> of<00:19:33.419> these<00:19:33.600> problems 00:19:34.730 --> 00:19:34.740 align:start position:0% to solve a lot of these problems 00:19:34.740 --> 00:19:36.470 align:start position:0% to solve a lot of these problems um<00:19:34.860> the<00:19:34.980> evm 00:19:36.470 --> 00:19:36.480 align:start position:0% um the evm 00:19:36.480 --> 00:19:38.810 align:start position:0% um the evm um<00:19:36.600> if<00:19:37.260> a<00:19:37.740> chain<00:19:37.860> wants<00:19:38.280> to<00:19:38.340> really<00:19:38.460> run<00:19:38.640> the 00:19:38.810 --> 00:19:38.820 align:start position:0% um if a chain wants to really run the 00:19:38.820 --> 00:19:40.430 align:start position:0% um if a chain wants to really run the evm<00:19:39.240> they<00:19:39.480> will<00:19:39.600> do<00:19:39.780> the<00:19:39.900> changes<00:19:40.200> they<00:19:40.320> need 00:19:40.430 --> 00:19:40.440 align:start position:0% evm they will do the changes they need 00:19:40.440 --> 00:19:42.409 align:start position:0% evm they will do the changes they need to<00:19:40.559> there's<00:19:40.860> not<00:19:41.160> too<00:19:41.400> much<00:19:41.520> changes<00:19:41.880> the<00:19:42.059> evm 00:19:42.409 --> 00:19:42.419 align:start position:0% to there's not too much changes the evm 00:19:42.419 --> 00:19:44.990 align:start position:0% to there's not too much changes the evm needs<00:19:42.720> to<00:19:42.780> do<00:19:42.900> it's<00:19:43.440> the<00:19:43.620> user<00:19:43.919> tooling<00:19:44.340> that 00:19:44.990 --> 00:19:45.000 align:start position:0% needs to do it's the user tooling that 00:19:45.000 --> 00:19:46.850 align:start position:0% needs to do it's the user tooling that might<00:19:45.179> need<00:19:45.360> to<00:19:45.480> change<00:19:45.720> to<00:19:46.500> deal<00:19:46.620> with 00:19:46.850 --> 00:19:46.860 align:start position:0% might need to change to deal with 00:19:46.860 --> 00:19:48.890 align:start position:0% might need to change to deal with potential<00:19:47.520> changes<00:19:47.820> in<00:19:48.000> cryptography<00:19:48.780> that 00:19:48.890 --> 00:19:48.900 align:start position:0% potential changes in cryptography that 00:19:48.900 --> 00:19:50.210 align:start position:0% potential changes in cryptography that comes<00:19:49.140> ahead 00:19:50.210 --> 00:19:50.220 align:start position:0% comes ahead 00:19:50.220 --> 00:19:52.730 align:start position:0% comes ahead and<00:19:51.480> um<00:19:51.480> not<00:19:51.960> every<00:19:52.080> chain<00:19:52.260> is<00:19:52.440> going<00:19:52.559> to<00:19:52.559> be<00:19:52.620> a 00:19:52.730 --> 00:19:52.740 align:start position:0% and um not every chain is going to be a 00:19:52.740 --> 00:19:53.690 align:start position:0% and um not every chain is going to be a theory<00:19:52.919> mean<00:19:53.160> that<00:19:53.340> there's<00:19:53.460> going<00:19:53.580> to<00:19:53.640> be 00:19:53.690 --> 00:19:53.700 align:start position:0% theory mean that there's going to be 00:19:53.700 --> 00:19:55.669 align:start position:0% theory mean that there's going to be other<00:19:53.820> changes<00:19:54.179> that<00:19:54.299> do<00:19:54.419> cool<00:19:54.660> things<00:19:54.900> that 00:19:55.669 --> 00:19:55.679 align:start position:0% other changes that do cool things that 00:19:55.679 --> 00:19:57.169 align:start position:0% other changes that do cool things that aren't<00:19:55.860> compatible<00:19:56.220> with<00:19:56.340> ethereum<00:19:56.760> mainnet 00:19:57.169 --> 00:19:57.179 align:start position:0% aren't compatible with ethereum mainnet 00:19:57.179 --> 00:19:58.970 align:start position:0% aren't compatible with ethereum mainnet that's<00:19:57.840> fine<00:19:58.020> let<00:19:58.320> them<00:19:58.500> do<00:19:58.620> their<00:19:58.799> cool 00:19:58.970 --> 00:19:58.980 align:start position:0% that's fine let them do their cool 00:19:58.980 --> 00:20:01.549 align:start position:0% that's fine let them do their cool things<00:19:59.160> let<00:19:59.760> us<00:19:59.940> hear<00:20:00.120> be<00:20:00.299> ethereum 00:20:01.549 --> 00:20:01.559 align:start position:0% things let us hear be ethereum 00:20:01.559 --> 00:20:02.810 align:start position:0% things let us hear be ethereum and<00:20:01.980> if<00:20:02.039> you<00:20:02.160> have<00:20:02.280> any<00:20:02.400> questions<00:20:02.580> or 00:20:02.810 --> 00:20:02.820 align:start position:0% and if you have any questions or 00:20:02.820 --> 00:20:05.210 align:start position:0% and if you have any questions or comments<00:20:03.120> my<00:20:03.419> DMs<00:20:03.780> are<00:20:03.900> open 00:20:05.210 --> 00:20:05.220 align:start position:0% comments my DMs are open 00:20:05.220 --> 00:20:07.010 align:start position:0% comments my DMs are open um<00:20:05.340> just<00:20:05.760> don't<00:20:05.880> offer<00:20:06.179> me<00:20:06.299> a<00:20:06.419> pump<00:20:06.539> and<00:20:06.660> dump<00:20:06.780> I 00:20:07.010 --> 00:20:07.020 align:start position:0% um just don't offer me a pump and dump I 00:20:07.020 --> 00:20:08.390 align:start position:0% um just don't offer me a pump and dump I will<00:20:07.140> delete<00:20:07.260> you 00:20:08.390 --> 00:20:08.400 align:start position:0% will delete you 00:20:08.400 --> 00:20:14.509 align:start position:0% will delete you [Applause]