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:22.609 align:start position:0% [Music] 00:00:22.609 --> 00:00:22.619 align:start position:0% 00:00:22.619 --> 00:00:24.410 align:start position:0% I<00:00:23.039> also<00:00:23.220> can't<00:00:23.400> see<00:00:23.580> the<00:00:23.760> slide<00:00:23.939> so<00:00:24.180> I'm<00:00:24.300> gonna 00:00:24.410 --> 00:00:24.420 align:start position:0% I also can't see the slide so I'm gonna 00:00:24.420 --> 00:00:26.090 align:start position:0% I also can't see the slide so I'm gonna like 00:00:26.090 --> 00:00:26.100 align:start position:0% like 00:00:26.100 --> 00:00:28.070 align:start position:0% like also<00:00:26.580> attack<00:00:26.699> us<00:00:27.000> on<00:00:27.180> the<00:00:27.240> trailer<00:00:27.420> okay<00:00:27.779> so 00:00:28.070 --> 00:00:28.080 align:start position:0% also attack us on the trailer okay so 00:00:28.080 --> 00:00:29.990 align:start position:0% also attack us on the trailer okay so I'm<00:00:28.380> going<00:00:28.500> to<00:00:28.619> talk<00:00:28.740> a<00:00:28.859> bit<00:00:28.980> about<00:00:29.220> how<00:00:29.580> we<00:00:29.760> got 00:00:29.990 --> 00:00:30.000 align:start position:0% I'm going to talk a bit about how we got 00:00:30.000 --> 00:00:32.450 align:start position:0% I'm going to talk a bit about how we got to<00:00:30.480> where<00:00:30.779> we<00:00:30.960> are<00:00:31.080> today<00:00:31.260> with<00:00:31.560> you<00:00:31.740> all 00:00:32.450 --> 00:00:32.460 align:start position:0% to where we are today with you all 00:00:32.460 --> 00:00:35.510 align:start position:0% to where we are today with you all uh<00:00:33.120> by<00:00:33.300> going<00:00:33.540> through<00:00:33.780> at<00:00:34.200> least<00:00:34.399> timeline<00:00:35.399> of 00:00:35.510 --> 00:00:35.520 align:start position:0% uh by going through at least timeline of 00:00:35.520 --> 00:00:40.069 align:start position:0% uh by going through at least timeline of events<00:00:36.360> uh<00:00:37.260> in<00:00:37.500> June<00:00:37.860> 2019<00:00:38.460> I<00:00:39.300> introduced<00:00:39.840> the 00:00:40.069 --> 00:00:40.079 align:start position:0% events uh in June 2019 I introduced the 00:00:40.079 --> 00:00:42.290 align:start position:0% events uh in June 2019 I introduced the optimistic<00:00:40.739> raw<00:00:41.040> design<00:00:41.219> Paradigm<00:00:41.879> under<00:00:42.120> the 00:00:42.290 --> 00:00:42.300 align:start position:0% optimistic raw design Paradigm under the 00:00:42.300 --> 00:00:44.090 align:start position:0% optimistic raw design Paradigm under the title<00:00:42.600> of<00:00:42.660> minimal<00:00:43.020> viable<00:00:43.320> emerging<00:00:43.739> census 00:00:44.090 --> 00:00:44.100 align:start position:0% title of minimal viable emerging census 00:00:44.100 --> 00:00:46.250 align:start position:0% title of minimal viable emerging census and<00:00:44.820> this<00:00:45.000> kind<00:00:45.239> of<00:00:45.300> kicked<00:00:45.719> off<00:00:45.780> the<00:00:46.079> whole 00:00:46.250 --> 00:00:46.260 align:start position:0% and this kind of kicked off the whole 00:00:46.260 --> 00:00:48.470 align:start position:0% and this kind of kicked off the whole idea<00:00:46.620> that<00:00:47.399> you<00:00:47.579> can<00:00:47.700> have<00:00:47.940> some<00:00:48.180> sort<00:00:48.360> of 00:00:48.470 --> 00:00:48.480 align:start position:0% idea that you can have some sort of 00:00:48.480 --> 00:00:50.810 align:start position:0% idea that you can have some sort of scalable<00:00:48.960> execution<00:00:49.559> system<00:00:49.860> anchored<00:00:50.640> into 00:00:50.810 --> 00:00:50.820 align:start position:0% scalable execution system anchored into 00:00:50.820 --> 00:00:53.690 align:start position:0% scalable execution system anchored into ethereum<00:00:51.300> for<00:00:51.480> security 00:00:53.690 --> 00:00:53.700 align:start position:0% ethereum for security 00:00:53.700 --> 00:00:56.270 align:start position:0% ethereum for security uh 00:00:56.270 --> 00:00:56.280 align:start position:0% uh 00:00:56.280 --> 00:01:00.350 align:start position:0% uh moving<00:00:56.879> on<00:00:57.000> uh<00:00:57.840> to<00:00:58.079> December<00:00:58.800> 2020. 00:01:00.350 --> 00:01:00.360 align:start position:0% moving on uh to December 2020. 00:01:00.360 --> 00:01:02.090 align:start position:0% moving on uh to December 2020. this<00:01:00.840> was<00:01:01.079> you<00:01:01.320> know<00:01:01.379> right<00:01:01.620> at<00:01:01.800> the<00:01:01.920> end<00:01:02.039> of 00:01:02.090 --> 00:01:02.100 align:start position:0% this was you know right at the end of 00:01:02.100 --> 00:01:05.390 align:start position:0% this was you know right at the end of the<00:01:02.219> year<00:01:02.340> but<00:01:02.879> still<00:01:03.180> in<00:01:03.359> 2020<00:01:04.100> we<00:01:05.100> did<00:01:05.220> a 00:01:05.390 --> 00:01:05.400 align:start position:0% the year but still in 2020 we did a 00:01:05.400 --> 00:01:07.730 align:start position:0% the year but still in 2020 we did a Mainland<00:01:05.760> launch<00:01:06.000> of<00:01:06.180> fuel<00:01:06.420> V1<00:01:06.840> as<00:01:07.260> the<00:01:07.560> first 00:01:07.730 --> 00:01:07.740 align:start position:0% Mainland launch of fuel V1 as the first 00:01:07.740 --> 00:01:10.070 align:start position:0% Mainland launch of fuel V1 as the first optimistic<00:01:08.280> rollout<00:01:08.700> on<00:01:08.939> Main<00:01:09.119> and<00:01:09.299> ethereum 00:01:10.070 --> 00:01:10.080 align:start position:0% optimistic rollout on Main and ethereum 00:01:10.080 --> 00:01:11.750 align:start position:0% optimistic rollout on Main and ethereum and<00:01:10.560> through<00:01:10.740> the<00:01:10.979> style<00:01:11.100> is<00:01:11.280> actually<00:01:11.460> the 00:01:11.750 --> 00:01:11.760 align:start position:0% and through the style is actually the 00:01:11.760 --> 00:01:14.210 align:start position:0% and through the style is actually the still<00:01:12.540> the<00:01:13.140> only<00:01:13.200> system<00:01:13.560> that<00:01:13.920> could<00:01:14.100> be 00:01:14.210 --> 00:01:14.220 align:start position:0% still the only system that could be 00:01:14.220 --> 00:01:16.370 align:start position:0% still the only system that could be considered<00:01:14.640> a<00:01:14.760> true<00:01:15.060> roller<00:01:16.020> that<00:01:16.200> is 00:01:16.370 --> 00:01:16.380 align:start position:0% considered a true roller that is 00:01:16.380 --> 00:01:19.010 align:start position:0% considered a true roller that is trustless<00:01:16.760> and<00:01:17.760> permissionless 00:01:19.010 --> 00:01:19.020 align:start position:0% trustless and permissionless 00:01:19.020 --> 00:01:23.210 align:start position:0% trustless and permissionless uh<00:01:19.860> since<00:01:20.460> then<00:01:20.659> uh<00:01:21.659> up<00:01:21.840> until<00:01:22.020> January<00:01:22.560> 2022 00:01:23.210 --> 00:01:23.220 align:start position:0% uh since then uh up until January 2022 00:01:23.220 --> 00:01:24.770 align:start position:0% uh since then uh up until January 2022 we<00:01:23.580> were<00:01:23.759> essentially<00:01:24.060> heads<00:01:24.360> down<00:01:24.479> building 00:01:24.770 --> 00:01:24.780 align:start position:0% we were essentially heads down building 00:01:24.780 --> 00:01:28.490 align:start position:0% we were essentially heads down building out<00:01:25.080> uh<00:01:25.799> fuel<00:01:25.979> V2<00:01:26.540> which<00:01:27.540> was<00:01:27.780> an<00:01:27.960> evolution<00:01:28.200> of 00:01:28.490 --> 00:01:28.500 align:start position:0% out uh fuel V2 which was an evolution of 00:01:28.500 --> 00:01:29.929 align:start position:0% out uh fuel V2 which was an evolution of the<00:01:28.619> protocol<00:01:28.860> from<00:01:29.280> a<00:01:29.460> payments<00:01:29.880> only 00:01:29.929 --> 00:01:29.939 align:start position:0% the protocol from a payments only 00:01:29.939 --> 00:01:31.910 align:start position:0% the protocol from a payments only platform<00:01:30.360> to<00:01:30.720> a<00:01:30.960> general<00:01:31.200> purpose<00:01:31.680> smart 00:01:31.910 --> 00:01:31.920 align:start position:0% platform to a general purpose smart 00:01:31.920 --> 00:01:34.609 align:start position:0% platform to a general purpose smart contract<00:01:32.340> execution<00:01:33.180> platform<00:01:33.600> so<00:01:34.500> we 00:01:34.609 --> 00:01:34.619 align:start position:0% contract execution platform so we 00:01:34.619 --> 00:01:36.710 align:start position:0% contract execution platform so we published<00:01:34.979> our<00:01:35.100> code<00:01:35.280> and<00:01:35.460> GitHub<00:01:35.759> since<00:01:36.479> then 00:01:36.710 --> 00:01:36.720 align:start position:0% published our code and GitHub since then 00:01:36.720 --> 00:01:39.230 align:start position:0% published our code and GitHub since then the<00:01:37.140> code<00:01:37.320> has<00:01:37.619> been<00:01:37.799> developed<00:01:38.340> it<00:01:38.939> has<00:01:39.119> been 00:01:39.230 --> 00:01:39.240 align:start position:0% the code has been developed it has been 00:01:39.240 --> 00:01:40.969 align:start position:0% the code has been developed it has been open<00:01:39.420> source<00:01:39.780> and<00:01:39.960> entirely<00:01:40.380> developed 00:01:40.969 --> 00:01:40.979 align:start position:0% open source and entirely developed 00:01:40.979 --> 00:01:44.749 align:start position:0% open source and entirely developed planned<00:01:41.640> and<00:01:42.659> Etc<00:01:42.780> all<00:01:43.619> in<00:01:43.920> public 00:01:44.749 --> 00:01:44.759 align:start position:0% planned and Etc all in public 00:01:44.759 --> 00:01:46.550 align:start position:0% planned and Etc all in public not<00:01:45.299> a<00:01:45.540> lot<00:01:45.600> of<00:01:45.659> projects<00:01:45.960> I<00:01:46.140> should<00:01:46.320> do<00:01:46.439> this 00:01:46.550 --> 00:01:46.560 align:start position:0% not a lot of projects I should do this 00:01:46.560 --> 00:01:48.469 align:start position:0% not a lot of projects I should do this entirely<00:01:46.920> in<00:01:47.040> public<00:01:47.280> we<00:01:47.880> ask<00:01:48.000> you<00:01:48.119> to<00:01:48.240> all<00:01:48.360> our 00:01:48.469 --> 00:01:48.479 align:start position:0% entirely in public we ask you to all our 00:01:48.479 --> 00:01:49.670 align:start position:0% entirely in public we ask you to all our development 00:01:49.670 --> 00:01:49.680 align:start position:0% development 00:01:49.680 --> 00:01:52.670 align:start position:0% development in<00:01:50.159> public 00:01:52.670 --> 00:01:52.680 align:start position:0% 00:01:52.680 --> 00:01:59.210 align:start position:0% uh 00:01:59.210 --> 00:01:59.220 align:start position:0% 00:01:59.220 --> 00:02:00.770 align:start position:0% uh<00:01:59.939> then 00:02:00.770 --> 00:02:00.780 align:start position:0% uh then 00:02:00.780 --> 00:02:04.609 align:start position:0% uh then um June<00:02:01.200> of<00:02:01.320> 2022<00:02:01.979> we<00:02:02.759> launched<00:02:03.600> a<00:02:03.960> sway<00:02:04.200> swamp 00:02:04.609 --> 00:02:04.619 align:start position:0% um June of 2022 we launched a sway swamp 00:02:04.619 --> 00:02:06.770 align:start position:0% um June of 2022 we launched a sway swamp demo<00:02:04.920> sway<00:02:05.340> swap<00:02:05.640> is<00:02:05.880> a<00:02:06.060> part<00:02:06.180> of<00:02:06.360> Junior<00:02:06.479> soft 00:02:06.770 --> 00:02:06.780 align:start position:0% demo sway swap is a part of Junior soft 00:02:06.780 --> 00:02:08.930 align:start position:0% demo sway swap is a part of Junior soft V1<00:02:07.200> to<00:02:07.619> sway<00:02:07.979> which<00:02:08.340> is<00:02:08.399> the<00:02:08.520> high-level 00:02:08.930 --> 00:02:08.940 align:start position:0% V1 to sway which is the high-level 00:02:08.940 --> 00:02:10.430 align:start position:0% V1 to sway which is the high-level language<00:02:09.179> that<00:02:09.420> I<00:02:09.599> imagine<00:02:09.660> most<00:02:10.020> of<00:02:10.200> you<00:02:10.259> are 00:02:10.430 --> 00:02:10.440 align:start position:0% language that I imagine most of you are 00:02:10.440 --> 00:02:12.290 align:start position:0% language that I imagine most of you are here<00:02:10.860> excited<00:02:11.340> about 00:02:12.290 --> 00:02:12.300 align:start position:0% here excited about 00:02:12.300 --> 00:02:15.830 align:start position:0% here excited about uh<00:02:13.200> and<00:02:13.560> a<00:02:13.800> lot<00:02:13.920> of<00:02:13.980> the<00:02:14.099> private<00:02:14.340> tests<00:02:14.640> now 00:02:15.830 --> 00:02:15.840 align:start position:0% uh and a lot of the private tests now 00:02:15.840 --> 00:02:19.490 align:start position:0% uh and a lot of the private tests now and<00:02:16.560> then<00:02:16.800> in<00:02:17.520> September<00:02:18.120> of<00:02:18.300> 2022<00:02:18.900> so<00:02:19.140> just<00:02:19.379> a 00:02:19.490 --> 00:02:19.500 align:start position:0% and then in September of 2022 so just a 00:02:19.500 --> 00:02:23.390 align:start position:0% and then in September of 2022 so just a short<00:02:19.680> month<00:02:19.860> ago<00:02:20.160> we<00:02:20.879> we<00:02:21.239> released<00:02:22.080> the<00:02:22.500> beta 00:02:23.390 --> 00:02:23.400 align:start position:0% short month ago we we released the beta 00:02:23.400 --> 00:02:25.850 align:start position:0% short month ago we we released the beta one<00:02:23.520> public<00:02:23.760> testing<00:02:24.300> of<00:02:25.080> the<00:02:25.260> fuel<00:02:25.560> protocol 00:02:25.850 --> 00:02:25.860 align:start position:0% one public testing of the fuel protocol 00:02:25.860 --> 00:02:27.050 align:start position:0% one public testing of the fuel protocol this<00:02:26.459> is<00:02:26.580> actually<00:02:26.700> completely 00:02:27.050 --> 00:02:27.060 align:start position:0% this is actually completely 00:02:27.060 --> 00:02:28.910 align:start position:0% this is actually completely permissionless<00:02:27.540> anyone<00:02:28.020> can<00:02:28.260> use<00:02:28.560> that<00:02:28.739> to 00:02:28.910 --> 00:02:28.920 align:start position:0% permissionless anyone can use that to 00:02:28.920 --> 00:02:31.250 align:start position:0% permissionless anyone can use that to buy<00:02:29.040> smart<00:02:29.220> contract<00:02:29.580> run<00:02:29.879> transaction<00:02:30.420> and 00:02:31.250 --> 00:02:31.260 align:start position:0% buy smart contract run transaction and 00:02:31.260 --> 00:02:32.750 align:start position:0% buy smart contract run transaction and you<00:02:31.379> can<00:02:31.500> use<00:02:31.620> it<00:02:31.739> today 00:02:32.750 --> 00:02:32.760 align:start position:0% you can use it today 00:02:32.760 --> 00:02:36.949 align:start position:0% you can use it today and<00:02:33.480> now<00:02:34.080> we're<00:02:34.260> here<00:02:34.500> uh.com<00:02:35.280> October<00:02:35.959> 2022 00:02:36.949 --> 00:02:36.959 align:start position:0% and now we're here uh.com October 2022 00:02:36.959 --> 00:02:39.290 align:start position:0% and now we're here uh.com October 2022 and<00:02:37.560> what<00:02:38.160> do<00:02:38.400> we<00:02:38.520> have<00:02:38.640> and<00:02:38.819> where<00:02:39.120> are<00:02:39.239> we 00:02:39.290 --> 00:02:39.300 align:start position:0% and what do we have and where are we 00:02:39.300 --> 00:02:41.030 align:start position:0% and what do we have and where are we going<00:02:39.420> to<00:02:39.480> go 00:02:41.030 --> 00:02:41.040 align:start position:0% going to go 00:02:41.040 --> 00:02:42.890 align:start position:0% going to go let's<00:02:41.459> talk<00:02:41.640> about<00:02:41.819> the<00:02:42.060> three<00:02:42.180> pillars<00:02:42.599> of 00:02:42.890 --> 00:02:42.900 align:start position:0% let's talk about the three pillars of 00:02:42.900 --> 00:02:46.369 align:start position:0% let's talk about the three pillars of fuel<00:02:43.260> and<00:02:43.980> what<00:02:44.519> makes<00:02:44.760> the<00:02:45.239> protocol<00:02:45.720> so 00:02:46.369 --> 00:02:46.379 align:start position:0% fuel and what makes the protocol so 00:02:46.379 --> 00:02:49.790 align:start position:0% fuel and what makes the protocol so great<00:02:46.620> to<00:02:47.400> use<00:02:47.700> and<00:02:48.000> to<00:02:48.120> build<00:02:48.300> with<00:02:48.959> Etc 00:02:49.790 --> 00:02:49.800 align:start position:0% great to use and to build with Etc 00:02:49.800 --> 00:02:52.550 align:start position:0% great to use and to build with Etc so<00:02:50.400> we<00:02:50.700> have<00:02:50.879> three<00:02:51.239> fundamental<00:02:51.840> pillars<00:02:52.200> one 00:02:52.550 --> 00:02:52.560 align:start position:0% so we have three fundamental pillars one 00:02:52.560 --> 00:02:54.710 align:start position:0% so we have three fundamental pillars one of<00:02:52.680> them<00:02:52.860> is<00:02:53.160> performance 00:02:54.710 --> 00:02:54.720 align:start position:0% of them is performance 00:02:54.720 --> 00:02:57.110 align:start position:0% of them is performance uh<00:02:55.620> performance<00:02:56.340> through<00:02:56.580> parallel 00:02:57.110 --> 00:02:57.120 align:start position:0% uh performance through parallel 00:02:57.120 --> 00:02:59.089 align:start position:0% uh performance through parallel transaction<00:02:57.480> execution<00:02:58.019> the<00:02:58.440> second<00:02:58.620> one<00:02:58.860> is 00:02:59.089 --> 00:02:59.099 align:start position:0% transaction execution the second one is 00:02:59.099 --> 00:03:01.190 align:start position:0% transaction execution the second one is flexibility<00:02:59.640> and<00:02:59.879> waste<00:03:00.180> reduction<00:03:00.480> through 00:03:01.190 --> 00:03:01.200 align:start position:0% flexibility and waste reduction through 00:03:01.200 --> 00:03:03.229 align:start position:0% flexibility and waste reduction through the<00:03:01.440> fuel<00:03:01.680> virtual<00:03:01.980> machine<00:03:02.160> and<00:03:02.640> the<00:03:02.760> last<00:03:02.879> is 00:03:03.229 --> 00:03:03.239 align:start position:0% the fuel virtual machine and the last is 00:03:03.239 --> 00:03:05.990 align:start position:0% the fuel virtual machine and the last is a<00:03:03.599> superior<00:03:04.080> intact<00:03:04.920> unmatched<00:03:05.459> development 00:03:05.990 --> 00:03:06.000 align:start position:0% a superior intact unmatched development 00:03:06.000 --> 00:03:09.530 align:start position:0% a superior intact unmatched development experience<00:03:06.420> through<00:03:07.260> Sway<00:03:08.040> and<00:03:08.340> fork<00:03:09.120> and<00:03:09.420> I'm 00:03:09.530 --> 00:03:09.540 align:start position:0% experience through Sway and fork and I'm 00:03:09.540 --> 00:03:10.910 align:start position:0% experience through Sway and fork and I'm going<00:03:09.720> to<00:03:09.780> be<00:03:09.900> expanding<00:03:10.319> unusual<00:03:10.680> these 00:03:10.910 --> 00:03:10.920 align:start position:0% going to be expanding unusual these 00:03:10.920 --> 00:03:13.369 align:start position:0% going to be expanding unusual these colors<00:03:11.159> in<00:03:11.340> the<00:03:11.459> coming<00:03:11.519> slides 00:03:13.369 --> 00:03:13.379 align:start position:0% colors in the coming slides 00:03:13.379 --> 00:03:15.290 align:start position:0% colors in the coming slides so<00:03:13.860> let's<00:03:14.340> start<00:03:14.519> with<00:03:14.700> the<00:03:14.940> first<00:03:15.060> one 00:03:15.290 --> 00:03:15.300 align:start position:0% so let's start with the first one 00:03:15.300 --> 00:03:17.570 align:start position:0% so let's start with the first one performance<00:03:16.260> through<00:03:16.680> parallel<00:03:17.159> transaction 00:03:17.570 --> 00:03:17.580 align:start position:0% performance through parallel transaction 00:03:17.580 --> 00:03:18.649 align:start position:0% performance through parallel transaction attribution 00:03:18.649 --> 00:03:18.659 align:start position:0% attribution 00:03:18.659 --> 00:03:21.350 align:start position:0% attribution this<00:03:19.140> one<00:03:19.319> is<00:03:19.440> actually<00:03:19.800> going<00:03:20.159> to<00:03:20.280> be<00:03:20.580> the 00:03:21.350 --> 00:03:21.360 align:start position:0% this one is actually going to be the 00:03:21.360 --> 00:03:22.970 align:start position:0% this one is actually going to be the shortest<00:03:21.720> of<00:03:21.900> the<00:03:22.019> three<00:03:22.080> floors<00:03:22.440> of<00:03:22.560> Calvert 00:03:22.970 --> 00:03:22.980 align:start position:0% shortest of the three floors of Calvert 00:03:22.980 --> 00:03:24.649 align:start position:0% shortest of the three floors of Calvert because<00:03:23.099> it's<00:03:23.340> actually<00:03:23.659> fairly 00:03:24.649 --> 00:03:24.659 align:start position:0% because it's actually fairly 00:03:24.659 --> 00:03:26.210 align:start position:0% because it's actually fairly straightforward<00:03:25.200> to<00:03:25.319> explain<00:03:25.500> which<00:03:25.920> is<00:03:25.980> that 00:03:26.210 --> 00:03:26.220 align:start position:0% straightforward to explain which is that 00:03:26.220 --> 00:03:29.509 align:start position:0% straightforward to explain which is that you<00:03:26.700> can<00:03:26.819> see<00:03:26.940> from<00:03:27.120> the<00:03:27.239> start<00:03:27.360> here<00:03:28.140> uh<00:03:29.040> the 00:03:29.509 --> 00:03:29.519 align:start position:0% you can see from the start here uh the 00:03:29.519 --> 00:03:31.790 align:start position:0% you can see from the start here uh the well<00:03:29.760> the<00:03:30.000> number<00:03:30.120> of<00:03:30.300> transistors<00:03:31.080> on<00:03:31.379> CPUs 00:03:31.790 --> 00:03:31.800 align:start position:0% well the number of transistors on CPUs 00:03:31.800 --> 00:03:33.649 align:start position:0% well the number of transistors on CPUs has<00:03:32.220> been<00:03:32.400> increasing<00:03:32.879> exponentially<00:03:33.420> over 00:03:33.649 --> 00:03:33.659 align:start position:0% has been increasing exponentially over 00:03:33.659 --> 00:03:35.770 align:start position:0% has been increasing exponentially over the<00:03:33.840> years<00:03:33.959> you<00:03:34.319> know<00:03:34.440> this<00:03:34.560> is<00:03:34.680> Moore's<00:03:35.040> law 00:03:35.770 --> 00:03:35.780 align:start position:0% the years you know this is Moore's law 00:03:35.780 --> 00:03:38.630 align:start position:0% the years you know this is Moore's law these<00:03:36.780> single<00:03:37.140> threaded<00:03:37.620> performance<00:03:38.040> in<00:03:38.400> the 00:03:38.630 --> 00:03:38.640 align:start position:0% these single threaded performance in the 00:03:38.640 --> 00:03:41.809 align:start position:0% these single threaded performance in the last<00:03:38.879> you<00:03:39.420> know<00:03:39.480> 10<00:03:40.019> plus<00:03:40.319> years<00:03:40.819> hasn't 00:03:41.809 --> 00:03:41.819 align:start position:0% last you know 10 plus years hasn't 00:03:41.819 --> 00:03:43.490 align:start position:0% last you know 10 plus years hasn't increased<00:03:42.299> exponentially<00:03:42.840> it's<00:03:43.080> kind<00:03:43.379> of 00:03:43.490 --> 00:03:43.500 align:start position:0% increased exponentially it's kind of 00:03:43.500 --> 00:03:46.250 align:start position:0% increased exponentially it's kind of stalled<00:03:43.920> it's<00:03:44.220> basically<00:03:44.700> leveled<00:03:45.120> off<00:03:45.780> what 00:03:46.250 --> 00:03:46.260 align:start position:0% stalled it's basically leveled off what 00:03:46.260 --> 00:03:48.170 align:start position:0% stalled it's basically leveled off what has<00:03:46.620> increased<00:03:47.099> exponentially<00:03:47.640> however<00:03:48.000> over 00:03:48.170 --> 00:03:48.180 align:start position:0% has increased exponentially however over 00:03:48.180 --> 00:03:51.050 align:start position:0% has increased exponentially however over the<00:03:48.420> years<00:03:48.480> has<00:03:48.780> been<00:03:49.019> the<00:03:49.739> number<00:03:49.920> of<00:03:50.099> cores 00:03:51.050 --> 00:03:51.060 align:start position:0% the years has been the number of cores 00:03:51.060 --> 00:03:53.930 align:start position:0% the years has been the number of cores right<00:03:51.260> so<00:03:52.260> if<00:03:52.680> you<00:03:52.799> have<00:03:52.980> a<00:03:53.220> system<00:03:53.459> that<00:03:53.819> is 00:03:53.930 --> 00:03:53.940 align:start position:0% right so if you have a system that is 00:03:53.940 --> 00:03:55.789 align:start position:0% right so if you have a system that is sequential<00:03:54.420> that<00:03:54.599> can<00:03:54.780> only<00:03:54.900> leverage<00:03:55.319> a 00:03:55.789 --> 00:03:55.799 align:start position:0% sequential that can only leverage a 00:03:55.799 --> 00:03:58.009 align:start position:0% sequential that can only leverage a single<00:03:56.099> core<00:03:56.280> it's<00:03:57.180> like<00:03:57.420> you're<00:03:57.599> running<00:03:57.780> it 00:03:58.009 --> 00:03:58.019 align:start position:0% single core it's like you're running it 00:03:58.019 --> 00:04:00.229 align:start position:0% single core it's like you're running it on<00:03:58.200> a<00:03:58.260> 10<00:03:58.440> year<00:03:58.560> old<00:03:58.680> computer<00:03:58.980> right<00:03:59.760> it's<00:04:00.000> not 00:04:00.229 --> 00:04:00.239 align:start position:0% on a 10 year old computer right it's not 00:04:00.239 --> 00:04:02.270 align:start position:0% on a 10 year old computer right it's not it's<00:04:00.720> not<00:04:00.900> exactly<00:04:01.260> a<00:04:01.500> very<00:04:01.620> good<00:04:01.799> place<00:04:01.980> to<00:04:02.159> be 00:04:02.270 --> 00:04:02.280 align:start position:0% it's not exactly a very good place to be 00:04:02.280 --> 00:04:03.770 align:start position:0% it's not exactly a very good place to be when<00:04:02.519> you're<00:04:02.640> trying<00:04:02.760> to<00:04:02.940> build<00:04:03.060> a<00:04:03.420> Global 00:04:03.770 --> 00:04:03.780 align:start position:0% when you're trying to build a Global 00:04:03.780 --> 00:04:05.930 align:start position:0% when you're trying to build a Global Financial<00:04:04.440> access 00:04:05.930 --> 00:04:05.940 align:start position:0% Financial access 00:04:05.940 --> 00:04:07.550 align:start position:0% Financial access Etc<00:04:06.060> system 00:04:07.550 --> 00:04:07.560 align:start position:0% Etc system 00:04:07.560 --> 00:04:09.350 align:start position:0% Etc system right<00:04:08.040> you<00:04:08.340> really<00:04:08.519> want<00:04:08.700> to<00:04:08.819> leverage<00:04:09.060> the 00:04:09.350 --> 00:04:09.360 align:start position:0% right you really want to leverage the 00:04:09.360 --> 00:04:11.089 align:start position:0% right you really want to leverage the same<00:04:09.540> that<00:04:09.900> is<00:04:10.080> increasing<00:04:10.560> exponentially 00:04:11.089 --> 00:04:11.099 align:start position:0% same that is increasing exponentially 00:04:11.099 --> 00:04:13.670 align:start position:0% same that is increasing exponentially year<00:04:11.340> over<00:04:11.459> year<00:04:11.700> and<00:04:12.420> that<00:04:12.599> is<00:04:12.840> this<00:04:13.260> parallel 00:04:13.670 --> 00:04:13.680 align:start position:0% year over year and that is this parallel 00:04:13.680 --> 00:04:16.550 align:start position:0% year over year and that is this parallel execution<00:04:14.159> multi-core<00:04:14.879> uh<00:04:15.540> multiple<00:04:16.260> cores 00:04:16.550 --> 00:04:16.560 align:start position:0% execution multi-core uh multiple cores 00:04:16.560 --> 00:04:18.530 align:start position:0% execution multi-core uh multiple cores multiple<00:04:16.859> threads<00:04:17.220> running<00:04:17.340> in<00:04:17.519> parallel 00:04:18.530 --> 00:04:18.540 align:start position:0% multiple threads running in parallel 00:04:18.540 --> 00:04:21.530 align:start position:0% multiple threads running in parallel uh<00:04:19.139> the<00:04:19.320> fuel<00:04:19.620> virtual<00:04:19.979> machine<00:04:20.160> is<00:04:20.820> designed 00:04:21.530 --> 00:04:21.540 align:start position:0% uh the fuel virtual machine is designed 00:04:21.540 --> 00:04:23.510 align:start position:0% uh the fuel virtual machine is designed and<00:04:21.900> the<00:04:22.079> fuel<00:04:22.199> protocol<00:04:22.500> is<00:04:22.740> designed<00:04:23.040> to<00:04:23.160> be 00:04:23.510 --> 00:04:23.520 align:start position:0% and the fuel protocol is designed to be 00:04:23.520 --> 00:04:25.909 align:start position:0% and the fuel protocol is designed to be able<00:04:23.759> to<00:04:23.940> run<00:04:24.180> transactions<00:04:25.080> in<00:04:25.199> parallel<00:04:25.620> as 00:04:25.909 --> 00:04:25.919 align:start position:0% able to run transactions in parallel as 00:04:25.919 --> 00:04:28.370 align:start position:0% able to run transactions in parallel as opposed<00:04:26.160> to<00:04:26.220> evm<00:04:26.880> which<00:04:27.600> unfortunately<00:04:28.080> can 00:04:28.370 --> 00:04:28.380 align:start position:0% opposed to evm which unfortunately can 00:04:28.380 --> 00:04:30.590 align:start position:0% opposed to evm which unfortunately can only<00:04:28.500> run<00:04:28.740> transactions<00:04:29.340> sequentially<00:04:29.759> this 00:04:30.590 --> 00:04:30.600 align:start position:0% only run transactions sequentially this 00:04:30.600 --> 00:04:32.210 align:start position:0% only run transactions sequentially this will<00:04:30.780> lead<00:04:30.900> to<00:04:31.080> a<00:04:31.440> vast<00:04:31.680> increase<00:04:31.919> in 00:04:32.210 --> 00:04:32.220 align:start position:0% will lead to a vast increase in 00:04:32.220 --> 00:04:34.550 align:start position:0% will lead to a vast increase in throughput<00:04:32.639> all<00:04:32.940> of<00:04:33.120> us<00:04:33.240> being<00:04:33.360> equal<00:04:33.600> not 00:04:34.550 --> 00:04:34.560 align:start position:0% throughput all of us being equal not 00:04:34.560 --> 00:04:35.689 align:start position:0% throughput all of us being equal not because<00:04:34.800> you<00:04:35.040> need<00:04:35.220> a<00:04:35.340> more<00:04:35.400> powerful 00:04:35.689 --> 00:04:35.699 align:start position:0% because you need a more powerful 00:04:35.699 --> 00:04:37.490 align:start position:0% because you need a more powerful computer<00:04:35.940> but<00:04:36.300> just<00:04:36.419> because<00:04:36.600> you're<00:04:37.080> using 00:04:37.490 --> 00:04:37.500 align:start position:0% computer but just because you're using 00:04:37.500 --> 00:04:39.890 align:start position:0% computer but just because you're using all<00:04:37.800> the<00:04:37.979> resources<00:04:38.639> of<00:04:39.120> your<00:04:39.300> computer<00:04:39.419> that 00:04:39.890 --> 00:04:39.900 align:start position:0% all the resources of your computer that 00:04:39.900 --> 00:04:42.290 align:start position:0% all the resources of your computer that in<00:04:40.800> in<00:04:41.160> the<00:04:41.280> VMware<00:04:41.699> just<00:04:41.940> kind<00:04:42.000> of<00:04:42.120> sitting 00:04:42.290 --> 00:04:42.300 align:start position:0% in in the VMware just kind of sitting 00:04:42.300 --> 00:04:43.490 align:start position:0% in in the VMware just kind of sitting there<00:04:42.419> wasted 00:04:43.490 --> 00:04:43.500 align:start position:0% there wasted 00:04:43.500 --> 00:04:46.390 align:start position:0% there wasted so<00:04:44.040> that's<00:04:44.460> the<00:04:45.240> again 00:04:46.390 --> 00:04:46.400 align:start position:0% so that's the again 00:04:46.400 --> 00:04:48.170 align:start position:0% so that's the again that's<00:04:47.400> really<00:04:47.520> all<00:04:47.639> there<00:04:47.759> is<00:04:47.940> to<00:04:48.060> it 00:04:48.170 --> 00:04:48.180 align:start position:0% that's really all there is to it 00:04:48.180 --> 00:04:50.510 align:start position:0% that's really all there is to it parallel<00:04:48.840> transaction<00:04:49.139> execution<00:04:49.620> massive 00:04:50.510 --> 00:04:50.520 align:start position:0% parallel transaction execution massive 00:04:50.520 --> 00:04:53.870 align:start position:0% parallel transaction execution massive increase<00:04:50.639> in<00:04:50.880> Drupal<00:04:51.720> now<00:04:52.380> on<00:04:52.860> to<00:04:53.040> waste 00:04:53.870 --> 00:04:53.880 align:start position:0% increase in Drupal now on to waste 00:04:53.880 --> 00:04:56.710 align:start position:0% increase in Drupal now on to waste production<00:04:54.199> uh<00:04:55.199> an<00:04:55.620> increased<00:04:56.220> performance 00:04:56.710 --> 00:04:56.720 align:start position:0% production uh an increased performance 00:04:56.720 --> 00:04:59.689 align:start position:0% production uh an increased performance on<00:04:57.720> the<00:04:57.840> single<00:04:58.139> threaded<00:04:58.560> model<00:04:58.800> oh<00:04:59.280> I<00:04:59.580> guess 00:04:59.689 --> 00:04:59.699 align:start position:0% on the single threaded model oh I guess 00:04:59.699 --> 00:05:02.810 align:start position:0% on the single threaded model oh I guess I<00:04:59.820> didn't<00:04:59.940> collect<00:05:00.479> this<00:05:00.600> and<00:05:01.320> on<00:05:02.100> laser 00:05:02.810 --> 00:05:02.820 align:start position:0% I didn't collect this and on laser 00:05:02.820 --> 00:05:04.670 align:start position:0% I didn't collect this and on laser function<00:05:03.000> and<00:05:03.180> improved<00:05:03.600> reference<00:05:03.960> within<00:05:04.560> a 00:05:04.670 --> 00:05:04.680 align:start position:0% function and improved reference within a 00:05:04.680 --> 00:05:06.830 align:start position:0% function and improved reference within a single<00:05:04.919> thread<00:05:05.220> through<00:05:05.820> the<00:05:06.000> fuel<00:05:06.479> virtual 00:05:06.830 --> 00:05:06.840 align:start position:0% single thread through the fuel virtual 00:05:06.840 --> 00:05:08.570 align:start position:0% single thread through the fuel virtual machine 00:05:08.570 --> 00:05:08.580 align:start position:0% machine 00:05:08.580 --> 00:05:11.629 align:start position:0% machine so<00:05:09.120> there's<00:05:09.540> also<00:05:09.840> some<00:05:10.080> QR<00:05:10.620> codes<00:05:10.919> uh<00:05:11.520> here 00:05:11.629 --> 00:05:11.639 align:start position:0% so there's also some QR codes uh here 00:05:11.639 --> 00:05:13.490 align:start position:0% so there's also some QR codes uh here that<00:05:11.880> you<00:05:12.060> guys<00:05:12.180> can<00:05:12.360> scan<00:05:12.600> if<00:05:12.900> you<00:05:13.020> so<00:05:13.199> wish 00:05:13.490 --> 00:05:13.500 align:start position:0% that you guys can scan if you so wish 00:05:13.500 --> 00:05:15.350 align:start position:0% that you guys can scan if you so wish that<00:05:13.860> link<00:05:14.100> to<00:05:14.340> some<00:05:14.520> of<00:05:14.699> our<00:05:14.759> documentation 00:05:15.350 --> 00:05:15.360 align:start position:0% that link to some of our documentation 00:05:15.360 --> 00:05:17.450 align:start position:0% that link to some of our documentation around<00:05:15.660> these<00:05:15.960> things<00:05:16.080> just<00:05:16.740> in<00:05:17.040> the<00:05:17.220> slides 00:05:17.450 --> 00:05:17.460 align:start position:0% around these things just in the slides 00:05:17.460 --> 00:05:19.070 align:start position:0% around these things just in the slides will<00:05:17.580> all<00:05:17.699> be<00:05:17.820> posted<00:05:18.120> later<00:05:18.300> on<00:05:18.479> so<00:05:18.780> if<00:05:18.840> we 00:05:19.070 --> 00:05:19.080 align:start position:0% will all be posted later on so if we 00:05:19.080 --> 00:05:20.390 align:start position:0% will all be posted later on so if we don't<00:05:19.259> if<00:05:19.620> we<00:05:19.800> don't<00:05:19.860> want<00:05:19.979> to<00:05:20.040> scan<00:05:20.280> them 00:05:20.390 --> 00:05:20.400 align:start position:0% don't if we don't want to scan them 00:05:20.400 --> 00:05:22.249 align:start position:0% don't if we don't want to scan them right<00:05:20.520> now<00:05:20.639> they'll<00:05:20.940> obviously<00:05:21.240> be<00:05:21.360> available 00:05:22.249 --> 00:05:22.259 align:start position:0% right now they'll obviously be available 00:05:22.259 --> 00:05:25.969 align:start position:0% right now they'll obviously be available uh<00:05:22.860> the<00:05:23.039> fuel<00:05:23.220> VM<00:05:23.759> is<00:05:24.479> fundamentally<00:05:25.139> the<00:05:25.500> evm 00:05:25.969 --> 00:05:25.979 align:start position:0% uh the fuel VM is fundamentally the evm 00:05:25.979 --> 00:05:27.230 align:start position:0% uh the fuel VM is fundamentally the evm but<00:05:26.160> improved 00:05:27.230 --> 00:05:27.240 align:start position:0% but improved 00:05:27.240 --> 00:05:29.390 align:start position:0% but improved one<00:05:27.960> amazing<00:05:28.320> thing<00:05:28.440> you<00:05:28.560> can<00:05:28.680> do<00:05:28.800> in<00:05:28.919> rollups 00:05:29.390 --> 00:05:29.400 align:start position:0% one amazing thing you can do in rollups 00:05:29.400 --> 00:05:31.610 align:start position:0% one amazing thing you can do in rollups is<00:05:29.639> experiment<00:05:30.300> with<00:05:30.840> improvements 00:05:31.610 --> 00:05:31.620 align:start position:0% is experiment with improvements 00:05:31.620 --> 00:05:33.650 align:start position:0% is experiment with improvements enhancements<00:05:32.639> Etc 00:05:33.650 --> 00:05:33.660 align:start position:0% enhancements Etc 00:05:33.660 --> 00:05:36.230 align:start position:0% enhancements Etc and<00:05:34.139> there<00:05:34.380> have<00:05:34.500> been<00:05:34.680> many<00:05:35.039> many<00:05:35.100> erps<00:05:35.880> and 00:05:36.230 --> 00:05:36.240 align:start position:0% and there have been many many erps and 00:05:36.240 --> 00:05:38.090 align:start position:0% and there have been many many erps and just<00:05:36.419> ideas<00:05:36.720> that<00:05:37.259> that<00:05:37.440> didn't<00:05:37.620> even<00:05:37.740> make<00:05:37.979> it 00:05:38.090 --> 00:05:38.100 align:start position:0% just ideas that that didn't even make it 00:05:38.100 --> 00:05:40.610 align:start position:0% just ideas that that didn't even make it to<00:05:38.220> erps<00:05:38.639> that<00:05:39.360> have<00:05:39.539> been<00:05:39.720> proposed<00:05:40.199> over<00:05:40.380> the 00:05:40.610 --> 00:05:40.620 align:start position:0% to erps that have been proposed over the 00:05:40.620 --> 00:05:43.490 align:start position:0% to erps that have been proposed over the years<00:05:40.800> for<00:05:41.639> ethereum<00:05:42.120> but<00:05:42.960> that<00:05:43.199> could<00:05:43.380> never 00:05:43.490 --> 00:05:43.500 align:start position:0% years for ethereum but that could never 00:05:43.500 --> 00:05:46.010 align:start position:0% years for ethereum but that could never be<00:05:43.740> implemented<00:05:44.280> because<00:05:44.639> of<00:05:45.300> a<00:05:45.600> need<00:05:45.780> for 00:05:46.010 --> 00:05:46.020 align:start position:0% be implemented because of a need for 00:05:46.020 --> 00:05:48.950 align:start position:0% be implemented because of a need for backwards<00:05:46.580> compatibility<00:05:47.580> also<00:05:48.419> limited 00:05:48.950 --> 00:05:48.960 align:start position:0% backwards compatibility also limited 00:05:48.960 --> 00:05:50.810 align:start position:0% backwards compatibility also limited developer<00:05:49.380> resources<00:05:49.919> you<00:05:50.400> know<00:05:50.520> just 00:05:50.810 --> 00:05:50.820 align:start position:0% developer resources you know just 00:05:50.820 --> 00:05:53.090 align:start position:0% developer resources you know just worries<00:05:51.360> of<00:05:51.660> too<00:05:52.080> too<00:05:52.259> much<00:05:52.440> change<00:05:52.560> too<00:05:52.919> fast 00:05:53.090 --> 00:05:53.100 align:start position:0% worries of too too much change too fast 00:05:53.100 --> 00:05:55.370 align:start position:0% worries of too too much change too fast might<00:05:53.400> be<00:05:53.520> risky<00:05:53.820> if<00:05:54.000> you<00:05:54.180> have<00:05:54.300> a<00:05:54.600> large<00:05:55.080> code 00:05:55.370 --> 00:05:55.380 align:start position:0% might be risky if you have a large code 00:05:55.380 --> 00:05:57.950 align:start position:0% might be risky if you have a large code based<00:05:55.740> on<00:05:55.800> Randy<00:05:56.160> with<00:05:56.220> a<00:05:56.340> lot<00:05:56.400> of<00:05:56.460> tech<00:05:56.580> debts 00:05:57.950 --> 00:05:57.960 align:start position:0% based on Randy with a lot of tech debts 00:05:57.960 --> 00:06:00.110 align:start position:0% based on Randy with a lot of tech debts all<00:05:58.680> right<00:05:58.860> but<00:05:59.280> people<00:05:59.460> still<00:05:59.699> want<00:05:59.940> these 00:06:00.110 --> 00:06:00.120 align:start position:0% all right but people still want these 00:06:00.120 --> 00:06:02.029 align:start position:0% all right but people still want these changes<00:06:00.360> they've<00:06:00.660> been<00:06:00.780> proposed<00:06:01.259> uh<00:06:01.919> you 00:06:02.029 --> 00:06:02.039 align:start position:0% changes they've been proposed uh you 00:06:02.039 --> 00:06:03.710 align:start position:0% changes they've been proposed uh you know<00:06:02.160> if<00:06:02.220> you<00:06:02.340> take<00:06:02.520> a<00:06:02.639> roll<00:06:02.759> up<00:06:03.000> and<00:06:03.419> you<00:06:03.600> know 00:06:03.710 --> 00:06:03.720 align:start position:0% know if you take a roll up and you know 00:06:03.720 --> 00:06:05.090 align:start position:0% know if you take a roll up and you know you<00:06:03.780> might<00:06:03.900> say<00:06:04.020> oh<00:06:04.139> okay<00:06:04.380> I'm<00:06:04.620> an<00:06:04.800> evm 00:06:05.090 --> 00:06:05.100 align:start position:0% you might say oh okay I'm an evm 00:06:05.100 --> 00:06:06.650 align:start position:0% you might say oh okay I'm an evm equivalent<00:06:05.400> roll<00:06:05.639> up<00:06:05.820> I<00:06:06.000> want<00:06:06.120> to<00:06:06.180> improve<00:06:06.539> it 00:06:06.650 --> 00:06:06.660 align:start position:0% equivalent roll up I want to improve it 00:06:06.660 --> 00:06:08.390 align:start position:0% equivalent roll up I want to improve it I'm<00:06:06.780> going<00:06:06.900> to<00:06:07.020> start<00:06:07.080> implementing<00:06:07.560> eips<00:06:07.919> to 00:06:08.390 --> 00:06:08.400 align:start position:0% I'm going to start implementing eips to 00:06:08.400 --> 00:06:09.710 align:start position:0% I'm going to start implementing eips to improve<00:06:08.759> it<00:06:08.820> right<00:06:09.060> I'm<00:06:09.240> going<00:06:09.360> to<00:06:09.419> add<00:06:09.539> a 00:06:09.710 --> 00:06:09.720 align:start position:0% improve it right I'm going to add a 00:06:09.720 --> 00:06:10.909 align:start position:0% improve it right I'm going to add a counter<00:06:09.960> traction<00:06:10.199> number<00:06:10.380> we're<00:06:10.680> going<00:06:10.800> to 00:06:10.909 --> 00:06:10.919 align:start position:0% counter traction number we're going to 00:06:10.919 --> 00:06:13.070 align:start position:0% counter traction number we're going to add<00:06:11.100> parallel<00:06:11.880> transaction<00:06:12.240> execution<00:06:12.900> Etc 00:06:13.070 --> 00:06:13.080 align:start position:0% add parallel transaction execution Etc 00:06:13.080 --> 00:06:16.010 align:start position:0% add parallel transaction execution Etc that's<00:06:14.039> fuel<00:06:14.400> right<00:06:15.120> the<00:06:15.300> fuel<00:06:15.419> of<00:06:15.539> M<00:06:15.720> is<00:06:15.900> the 00:06:16.010 --> 00:06:16.020 align:start position:0% that's fuel right the fuel of M is the 00:06:16.020 --> 00:06:17.990 align:start position:0% that's fuel right the fuel of M is the evm<00:06:16.380> but<00:06:16.560> improved<00:06:16.979> so<00:06:17.460> if<00:06:17.639> you're<00:06:17.820> looking 00:06:17.990 --> 00:06:18.000 align:start position:0% evm but improved so if you're looking 00:06:18.000 --> 00:06:20.450 align:start position:0% evm but improved so if you're looking for<00:06:18.240> the<00:06:18.479> evm<00:06:19.020> of<00:06:19.259> five<00:06:19.440> years<00:06:19.620> from<00:06:19.860> now<00:06:20.039> that 00:06:20.450 --> 00:06:20.460 align:start position:0% for the evm of five years from now that 00:06:20.460 --> 00:06:24.409 align:start position:0% for the evm of five years from now that is<00:06:20.639> the<00:06:20.759> fuel<00:06:20.940> VM 00:06:24.409 --> 00:06:24.419 align:start position:0% 00:06:24.419 --> 00:06:27.590 align:start position:0% next<00:06:24.960> one<00:06:25.139> uh<00:06:25.919> stateless<00:06:26.280> account<00:06:26.460> attention 00:06:27.590 --> 00:06:27.600 align:start position:0% next one uh stateless account attention 00:06:27.600 --> 00:06:29.510 align:start position:0% next one uh stateless account attention some<00:06:28.139> other<00:06:28.319> projects<00:06:28.740> give<00:06:28.919> like<00:06:29.160> an<00:06:29.340> entire 00:06:29.510 --> 00:06:29.520 align:start position:0% some other projects give like an entire 00:06:29.520 --> 00:06:31.129 align:start position:0% some other projects give like an entire talks<00:06:29.880> about<00:06:30.000> this<00:06:30.180> one<00:06:30.360> topic<00:06:30.660> but<00:06:30.840> this<00:06:31.020> is 00:06:31.129 --> 00:06:31.139 align:start position:0% talks about this one topic but this is 00:06:31.139 --> 00:06:33.230 align:start position:0% talks about this one topic but this is just<00:06:31.259> one<00:06:31.440> of<00:06:31.680> the<00:06:31.860> many<00:06:32.039> things<00:06:32.400> you<00:06:32.819> get<00:06:33.000> in 00:06:33.230 --> 00:06:33.240 align:start position:0% just one of the many things you get in 00:06:33.240 --> 00:06:35.689 align:start position:0% just one of the many things you get in fuel<00:06:33.419> so<00:06:33.600> it<00:06:33.720> just<00:06:33.840> gets<00:06:34.020> one<00:06:34.080> side<00:06:34.740> uh<00:06:35.400> fuel 00:06:35.689 --> 00:06:35.699 align:start position:0% fuel so it just gets one side uh fuel 00:06:35.699 --> 00:06:37.430 align:start position:0% fuel so it just gets one side uh fuel supports<00:06:36.240> account<00:06:36.539> of<00:06:36.780> traction<00:06:37.080> but 00:06:37.430 --> 00:06:37.440 align:start position:0% supports account of traction but 00:06:37.440 --> 00:06:39.529 align:start position:0% supports account of traction but statelessly<00:06:38.160> uh<00:06:38.819> State<00:06:39.060> full<00:06:39.360> account 00:06:39.529 --> 00:06:39.539 align:start position:0% statelessly uh State full account 00:06:39.539 --> 00:06:41.150 align:start position:0% statelessly uh State full account attraction<00:06:39.960> is<00:06:40.199> actually<00:06:40.440> a<00:06:40.620> denial<00:06:40.919> service 00:06:41.150 --> 00:06:41.160 align:start position:0% attraction is actually a denial service 00:06:41.160 --> 00:06:44.330 align:start position:0% attraction is actually a denial service Vector<00:06:41.639> so<00:06:42.539> be<00:06:43.020> wary<00:06:43.380> if<00:06:43.620> any<00:06:43.800> project<00:06:44.039> that 00:06:44.330 --> 00:06:44.340 align:start position:0% Vector so be wary if any project that 00:06:44.340 --> 00:06:45.770 align:start position:0% Vector so be wary if any project that says<00:06:44.580> it<00:06:44.819> has<00:06:45.000> state<00:06:45.240> state<00:06:45.419> full<00:06:45.600> account 00:06:45.770 --> 00:06:45.780 align:start position:0% says it has state state full account 00:06:45.780 --> 00:06:47.749 align:start position:0% says it has state state full account abstraction<00:06:46.199> we<00:06:46.919> have<00:06:47.100> State<00:06:47.280> lost<00:06:47.580> account 00:06:47.749 --> 00:06:47.759 align:start position:0% abstraction we have State lost account 00:06:47.759 --> 00:06:49.790 align:start position:0% abstraction we have State lost account abstraction<00:06:48.240> what<00:06:48.840> does<00:06:49.080> it<00:06:49.199> allow<00:06:49.440> you<00:06:49.500> to<00:06:49.680> do 00:06:49.790 --> 00:06:49.800 align:start position:0% abstraction what does it allow you to do 00:06:49.800 --> 00:06:51.050 align:start position:0% abstraction what does it allow you to do well<00:06:49.979> like<00:06:50.220> any<00:06:50.340> account<00:06:50.520> abstraction 00:06:51.050 --> 00:06:51.060 align:start position:0% well like any account abstraction 00:06:51.060 --> 00:06:53.210 align:start position:0% well like any account abstraction protocol<00:06:51.419> it<00:06:52.319> allows<00:06:52.680> you<00:06:52.740> to<00:06:52.979> Define 00:06:53.210 --> 00:06:53.220 align:start position:0% protocol it allows you to Define 00:06:53.220 --> 00:06:55.550 align:start position:0% protocol it allows you to Define conditions<00:06:54.120> under<00:06:54.419> which<00:06:54.660> a<00:06:54.900> transaction<00:06:55.319> is 00:06:55.550 --> 00:06:55.560 align:start position:0% conditions under which a transaction is 00:06:55.560 --> 00:06:59.150 align:start position:0% conditions under which a transaction is valid<00:06:56.039> not<00:06:57.000> conditions<00:06:57.900> you<00:06:58.440> know<00:06:58.560> not<00:06:58.800> logic 00:06:59.150 --> 00:06:59.160 align:start position:0% valid not conditions you know not logic 00:06:59.160 --> 00:07:00.529 align:start position:0% valid not conditions you know not logic of<00:06:59.340> what<00:06:59.460> the<00:06:59.580> transaction<00:06:59.880> will<00:07:00.120> do<00:07:00.360> but 00:07:00.529 --> 00:07:00.539 align:start position:0% of what the transaction will do but 00:07:00.539 --> 00:07:01.969 align:start position:0% of what the transaction will do but actually<00:07:00.720> conditions<00:07:01.380> under<00:07:01.560> which<00:07:01.800> the 00:07:01.969 --> 00:07:01.979 align:start position:0% actually conditions under which the 00:07:01.979 --> 00:07:04.090 align:start position:0% actually conditions under which the transaction<00:07:02.520> is<00:07:02.759> valid<00:07:03.120> or<00:07:03.300> not 00:07:04.090 --> 00:07:04.100 align:start position:0% transaction is valid or not 00:07:04.100 --> 00:07:07.070 align:start position:0% transaction is valid or not uh<00:07:05.100> you<00:07:05.460> know<00:07:05.580> the<00:07:05.880> most<00:07:06.240> obvious<00:07:06.600> case<00:07:06.840> one 00:07:07.070 --> 00:07:07.080 align:start position:0% uh you know the most obvious case one 00:07:07.080 --> 00:07:08.510 align:start position:0% uh you know the most obvious case one thing<00:07:07.259> you<00:07:07.380> could<00:07:07.500> do<00:07:07.620> is<00:07:07.740> use<00:07:07.979> a<00:07:08.280> different 00:07:08.510 --> 00:07:08.520 align:start position:0% thing you could do is use a different 00:07:08.520 --> 00:07:12.110 align:start position:0% thing you could do is use a different signature<00:07:09.180> scheme<00:07:09.960> I<00:07:10.740> uh<00:07:11.340> you<00:07:11.400> know<00:07:11.580> use<00:07:11.819> snore 00:07:12.110 --> 00:07:12.120 align:start position:0% signature scheme I uh you know use snore 00:07:12.120 --> 00:07:13.610 align:start position:0% signature scheme I uh you know use snore signatures<00:07:12.600> if<00:07:12.720> you<00:07:12.840> want<00:07:12.960> to<00:07:13.080> and<00:07:13.259> this<00:07:13.500> is 00:07:13.610 --> 00:07:13.620 align:start position:0% signatures if you want to and this is 00:07:13.620 --> 00:07:16.309 align:start position:0% signatures if you want to and this is actually<00:07:13.860> what<00:07:14.460> enables<00:07:14.940> us<00:07:15.120> to<00:07:15.780> use<00:07:16.020> any 00:07:16.309 --> 00:07:16.319 align:start position:0% actually what enables us to use any 00:07:16.319 --> 00:07:18.710 align:start position:0% actually what enables us to use any wallet<00:07:16.800> whatsoever<00:07:17.340> for<00:07:17.759> fuel<00:07:18.000> right 00:07:18.710 --> 00:07:18.720 align:start position:0% wallet whatsoever for fuel right 00:07:18.720 --> 00:07:20.450 align:start position:0% wallet whatsoever for fuel right obviously<00:07:19.259> you<00:07:19.440> know<00:07:19.560> we're<00:07:19.740> building<00:07:19.979> a 00:07:20.450 --> 00:07:20.460 align:start position:0% obviously you know we're building a 00:07:20.460 --> 00:07:22.490 align:start position:0% obviously you know we're building a native<00:07:20.880> wallet<00:07:21.419> that<00:07:21.660> has<00:07:21.780> all<00:07:21.960> the<00:07:22.080> bells<00:07:22.380> and 00:07:22.490 --> 00:07:22.500 align:start position:0% native wallet that has all the bells and 00:07:22.500 --> 00:07:23.990 align:start position:0% native wallet that has all the bells and whistles<00:07:22.800> uh<00:07:23.340> you<00:07:23.460> know<00:07:23.580> things<00:07:23.759> like 00:07:23.990 --> 00:07:24.000 align:start position:0% whistles uh you know things like 00:07:24.000 --> 00:07:27.589 align:start position:0% whistles uh you know things like transaction<00:07:24.720> simulation<00:07:25.460> you<00:07:26.460> know<00:07:26.580> and<00:07:26.819> uh<00:07:27.120> a 00:07:27.589 --> 00:07:27.599 align:start position:0% transaction simulation you know and uh a 00:07:27.599 --> 00:07:30.110 align:start position:0% transaction simulation you know and uh a mode<00:07:27.900> where<00:07:28.080> you<00:07:28.199> can<00:07:28.319> like<00:07:28.500> log<00:07:28.680> into<00:07:29.120> pretend 00:07:30.110 --> 00:07:30.120 align:start position:0% mode where you can like log into pretend 00:07:30.120 --> 00:07:32.510 align:start position:0% mode where you can like log into pretend to<00:07:30.180> be<00:07:30.360> in<00:07:30.479> any<00:07:30.720> public<00:07:31.020> key<00:07:31.319> or<00:07:31.440> any<00:07:31.620> address 00:07:32.510 --> 00:07:32.520 align:start position:0% to be in any public key or any address 00:07:32.520 --> 00:07:34.430 align:start position:0% to be in any public key or any address Etc<00:07:32.699> but<00:07:33.599> you<00:07:33.960> know<00:07:34.020> maybe<00:07:34.199> if<00:07:34.319> someone 00:07:34.430 --> 00:07:34.440 align:start position:0% Etc but you know maybe if someone 00:07:34.440 --> 00:07:35.629 align:start position:0% Etc but you know maybe if someone doesn't<00:07:34.680> want<00:07:34.860> to<00:07:34.979> install<00:07:35.039> a<00:07:35.280> new<00:07:35.400> attention 00:07:35.629 --> 00:07:35.639 align:start position:0% doesn't want to install a new attention 00:07:35.639 --> 00:07:37.430 align:start position:0% doesn't want to install a new attention because<00:07:36.000> they<00:07:36.180> use<00:07:36.360> Solana<00:07:36.780> right<00:07:37.199> and<00:07:37.319> they 00:07:37.430 --> 00:07:37.440 align:start position:0% because they use Solana right and they 00:07:37.440 --> 00:07:39.770 align:start position:0% because they use Solana right and they have<00:07:37.560> assign<00:07:37.800> a<00:07:38.039> lot<00:07:38.220> or<00:07:38.819> they<00:07:39.060> use<00:07:39.360> ethereum 00:07:39.770 --> 00:07:39.780 align:start position:0% have assign a lot or they use ethereum 00:07:39.780 --> 00:07:42.469 align:start position:0% have assign a lot or they use ethereum they<00:07:40.080> have<00:07:40.199> metamask<00:07:40.620> right<00:07:41.280> you<00:07:41.580> can<00:07:41.699> use<00:07:42.000> any 00:07:42.469 --> 00:07:42.479 align:start position:0% they have metamask right you can use any 00:07:42.479 --> 00:07:44.029 align:start position:0% they have metamask right you can use any of<00:07:42.720> these<00:07:42.960> things 00:07:44.029 --> 00:07:44.039 align:start position:0% of these things 00:07:44.039 --> 00:07:47.570 align:start position:0% of these things enzyme<00:07:44.880> transaction<00:07:45.120> on<00:07:45.360> fuel<00:07:45.660> because 00:07:47.570 --> 00:07:47.580 align:start position:0% enzyme transaction on fuel because 00:07:47.580 --> 00:07:49.490 align:start position:0% enzyme transaction on fuel because of<00:07:48.300> a<00:07:48.360> kind<00:07:48.479> of<00:07:48.599> traction<00:07:48.840> that<00:07:49.020> allows<00:07:49.319> you<00:07:49.380> to 00:07:49.490 --> 00:07:49.500 align:start position:0% of a kind of traction that allows you to 00:07:49.500 --> 00:07:52.249 align:start position:0% of a kind of traction that allows you to define<00:07:49.620> the<00:07:49.919> validity<00:07:50.880> conditions<00:07:51.539> that<00:07:52.139> are 00:07:52.249 --> 00:07:52.259 align:start position:0% define the validity conditions that are 00:07:52.259 --> 00:07:54.710 align:start position:0% define the validity conditions that are basically<00:07:52.500> well<00:07:52.800> whatever<00:07:53.479> signed<00:07:54.479> message 00:07:54.710 --> 00:07:54.720 align:start position:0% basically well whatever signed message 00:07:54.720 --> 00:07:58.670 align:start position:0% basically well whatever signed message whatever<00:07:55.500> log<00:07:55.979> you<00:07:56.699> want<00:07:56.880> will<00:07:57.660> do<00:07:58.080> it<00:07:58.380> checks 00:07:58.670 --> 00:07:58.680 align:start position:0% whatever log you want will do it checks 00:07:58.680 --> 00:08:01.370 align:start position:0% whatever log you want will do it checks out<00:07:58.740> for<00:07:58.919> validity<00:07:59.340> and<00:08:00.240> users<00:08:00.780> are<00:08:01.020> the<00:08:01.139> ones 00:08:01.370 --> 00:08:01.380 align:start position:0% out for validity and users are the ones 00:08:01.380 --> 00:08:03.350 align:start position:0% out for validity and users are the ones that<00:08:01.800> Define<00:08:02.160> the<00:08:02.520> spending<00:08:02.880> conditions<00:08:03.180> the 00:08:03.350 --> 00:08:03.360 align:start position:0% that Define the spending conditions the 00:08:03.360 --> 00:08:05.270 align:start position:0% that Define the spending conditions the validity<00:08:03.780> conditions<00:08:04.199> of<00:08:04.319> this<00:08:04.500> not<00:08:05.039> the 00:08:05.270 --> 00:08:05.280 align:start position:0% validity conditions of this not the 00:08:05.280 --> 00:08:07.309 align:start position:0% validity conditions of this not the protocol<00:08:05.639> not<00:08:06.300> those<00:08:06.539> anyone<00:08:06.960> in<00:08:07.139> the<00:08:07.199> world 00:08:07.309 --> 00:08:07.319 align:start position:0% protocol not those anyone in the world 00:08:07.319 --> 00:08:09.529 align:start position:0% protocol not those anyone in the world can<00:08:07.740> go<00:08:07.979> in<00:08:08.099> and<00:08:08.819> just<00:08:09.000> Define<00:08:09.120> some<00:08:09.419> new 00:08:09.529 --> 00:08:09.539 align:start position:0% can go in and just Define some new 00:08:09.539 --> 00:08:11.510 align:start position:0% can go in and just Define some new condition<00:08:09.780> and<00:08:10.500> you<00:08:10.680> know<00:08:10.800> it'll<00:08:11.099> work<00:08:11.220> with<00:08:11.340> a 00:08:11.510 --> 00:08:11.520 align:start position:0% condition and you know it'll work with a 00:08:11.520 --> 00:08:13.129 align:start position:0% condition and you know it'll work with a new<00:08:11.580> blockchain<00:08:11.940> just<00:08:12.539> like<00:08:12.720> that<00:08:12.900> no 00:08:13.129 --> 00:08:13.139 align:start position:0% new blockchain just like that no 00:08:13.139 --> 00:08:15.230 align:start position:0% new blockchain just like that no protocol<00:08:13.440> change<00:08:13.800> is<00:08:13.979> required<00:08:14.340> required<00:08:15.120> no 00:08:15.230 --> 00:08:15.240 align:start position:0% protocol change is required required no 00:08:15.240 --> 00:08:17.570 align:start position:0% protocol change is required required no governance<00:08:15.599> required<00:08:16.020> just<00:08:16.800> as<00:08:17.099> a<00:08:17.220> user<00:08:17.460> you 00:08:17.570 --> 00:08:17.580 align:start position:0% governance required just as a user you 00:08:17.580 --> 00:08:21.430 align:start position:0% governance required just as a user you just<00:08:17.699> write<00:08:17.819> it<00:08:18.000> and<00:08:18.240> you're<00:08:18.360> done 00:08:21.430 --> 00:08:21.440 align:start position:0% 00:08:21.440 --> 00:08:23.749 align:start position:0% uh<00:08:22.440> we<00:08:22.620> all<00:08:22.740> know<00:08:22.860> that<00:08:23.039> transferring<00:08:23.460> tokens 00:08:23.749 --> 00:08:23.759 align:start position:0% uh we all know that transferring tokens 00:08:23.759 --> 00:08:26.749 align:start position:0% uh we all know that transferring tokens are<00:08:24.599> a<00:08:24.900> really<00:08:25.139> painful<00:08:25.560> thing<00:08:25.800> right<00:08:26.460> there's 00:08:26.749 --> 00:08:26.759 align:start position:0% are a really painful thing right there's 00:08:26.759 --> 00:08:28.790 align:start position:0% are a really painful thing right there's like<00:08:27.060> super<00:08:27.300> extremely<00:08:27.900> actually<00:08:28.259> for<00:08:28.680> real 00:08:28.790 --> 00:08:28.800 align:start position:0% like super extremely actually for real 00:08:28.800 --> 00:08:32.690 align:start position:0% like super extremely actually for real this<00:08:29.039> time<00:08:29.220> safe<00:08:29.580> transfer<00:08:30.539> from<00:08:30.900> right<00:08:31.800> uh 00:08:32.690 --> 00:08:32.700 align:start position:0% this time safe transfer from right uh 00:08:32.700 --> 00:08:34.250 align:start position:0% this time safe transfer from right uh needed<00:08:33.120> because<00:08:33.300> there's<00:08:33.659> so<00:08:33.839> many<00:08:33.959> there's 00:08:34.250 --> 00:08:34.260 align:start position:0% needed because there's so many there's 00:08:34.260 --> 00:08:35.570 align:start position:0% needed because there's so many there's so<00:08:34.380> many<00:08:34.440> vulnerabilities<00:08:34.919> and<00:08:35.159> something<00:08:35.339> as 00:08:35.570 --> 00:08:35.580 align:start position:0% so many vulnerabilities and something as 00:08:35.580 --> 00:08:37.430 align:start position:0% so many vulnerabilities and something as simple<00:08:35.760> as<00:08:36.000> just<00:08:36.539> transferring<00:08:37.020> a<00:08:37.140> token 00:08:37.430 --> 00:08:37.440 align:start position:0% simple as just transferring a token 00:08:37.440 --> 00:08:39.769 align:start position:0% simple as just transferring a token properly<00:08:38.219> uh<00:08:38.820> fuel<00:08:39.060> supports<00:08:39.479> multiple 00:08:39.769 --> 00:08:39.779 align:start position:0% properly uh fuel supports multiple 00:08:39.779 --> 00:08:42.230 align:start position:0% properly uh fuel supports multiple multiple<00:08:40.380> assets<00:08:40.740> multiple<00:08:41.279> assets<00:08:41.760> natively 00:08:42.230 --> 00:08:42.240 align:start position:0% multiple assets multiple assets natively 00:08:42.240 --> 00:08:46.070 align:start position:0% multiple assets multiple assets natively so<00:08:42.659> every<00:08:42.839> token<00:08:43.380> is<00:08:44.159> a<00:08:44.339> native<00:08:44.520> asset<00:08:44.940> uh<00:08:45.899> so 00:08:46.070 --> 00:08:46.080 align:start position:0% so every token is a native asset uh so 00:08:46.080 --> 00:08:47.930 align:start position:0% so every token is a native asset uh so you<00:08:46.200> have<00:08:46.440> like<00:08:46.620> a<00:08:46.800> die<00:08:47.100> as<00:08:47.279> a<00:08:47.399> native<00:08:47.580> asset 00:08:47.930 --> 00:08:47.940 align:start position:0% you have like a die as a native asset 00:08:47.940 --> 00:08:49.310 align:start position:0% you have like a die as a native asset you<00:08:48.120> could<00:08:48.240> have<00:08:48.360> used<00:08:48.600> to<00:08:48.839> see<00:08:48.899> as<00:08:49.019> a<00:08:49.140> native 00:08:49.310 --> 00:08:49.320 align:start position:0% you could have used to see as a native 00:08:49.320 --> 00:08:51.050 align:start position:0% you could have used to see as a native asset<00:08:49.620> you<00:08:49.800> could<00:08:49.980> have<00:08:50.160> well<00:08:50.820> either 00:08:51.050 --> 00:08:51.060 align:start position:0% asset you could have well either 00:08:51.060 --> 00:08:53.630 align:start position:0% asset you could have well either obviously<00:08:51.480> is<00:08:51.540> a<00:08:51.720> native<00:08:51.839> asset<00:08:52.620> uh<00:08:53.279> and<00:08:53.459> this 00:08:53.630 --> 00:08:53.640 align:start position:0% obviously is a native asset uh and this 00:08:53.640 --> 00:08:55.610 align:start position:0% obviously is a native asset uh and this these<00:08:53.940> native<00:08:54.060> assets<00:08:54.420> can<00:08:54.660> be<00:08:54.779> pushed<00:08:55.260> with 00:08:55.610 --> 00:08:55.620 align:start position:0% these native assets can be pushed with 00:08:55.620 --> 00:08:57.710 align:start position:0% these native assets can be pushed with contract<00:08:55.980> calls<00:08:56.760> which<00:08:57.180> means<00:08:57.420> you<00:08:57.540> don't 00:08:57.710 --> 00:08:57.720 align:start position:0% contract calls which means you don't 00:08:57.720 --> 00:08:59.630 align:start position:0% contract calls which means you don't need<00:08:58.019> the<00:08:58.380> notion<00:08:58.620> of<00:08:58.740> token<00:08:59.040> approvals<00:08:59.459> you 00:08:59.630 --> 00:08:59.640 align:start position:0% need the notion of token approvals you 00:08:59.640 --> 00:09:01.190 align:start position:0% need the notion of token approvals you can<00:08:59.820> push<00:08:59.940> them<00:09:00.120> their<00:09:00.480> first<00:09:00.600> class<00:09:00.779> citizens 00:09:01.190 --> 00:09:01.200 align:start position:0% can push them their first class citizens 00:09:01.200 --> 00:09:02.810 align:start position:0% can push them their first class citizens just<00:09:01.620> like<00:09:01.800> how<00:09:01.920> in<00:09:02.100> ethereum<00:09:02.459> you<00:09:02.640> can<00:09:02.760> push 00:09:02.810 --> 00:09:02.820 align:start position:0% just like how in ethereum you can push 00:09:02.820 --> 00:09:04.790 align:start position:0% just like how in ethereum you can push ether<00:09:03.240> with<00:09:03.420> a<00:09:03.540> contract<00:09:03.779> call 00:09:04.790 --> 00:09:04.800 align:start position:0% ether with a contract call 00:09:04.800 --> 00:09:07.370 align:start position:0% ether with a contract call Noah<00:09:05.339> token<00:09:05.580> approvals<00:09:06.120> so<00:09:06.600> not<00:09:07.019> only<00:09:07.200> are<00:09:07.320> you 00:09:07.370 --> 00:09:07.380 align:start position:0% Noah token approvals so not only are you 00:09:07.380 --> 00:09:08.870 align:start position:0% Noah token approvals so not only are you getting<00:09:07.500> better<00:09:07.740> security<00:09:07.980> from<00:09:08.339> not<00:09:08.519> needing 00:09:08.870 --> 00:09:08.880 align:start position:0% getting better security from not needing 00:09:08.880 --> 00:09:11.389 align:start position:0% getting better security from not needing you<00:09:09.060> know<00:09:09.600> some<00:09:10.080> sort<00:09:10.260> of<00:09:10.380> safe<00:09:10.560> it's<00:09:11.160> not 00:09:11.389 --> 00:09:11.399 align:start position:0% you know some sort of safe it's not 00:09:11.399 --> 00:09:13.430 align:start position:0% you know some sort of safe it's not transfer<00:09:11.820> from<00:09:12.000> function<00:09:12.480> transfer<00:09:13.260> from 00:09:13.430 --> 00:09:13.440 align:start position:0% transfer from function transfer from 00:09:13.440 --> 00:09:15.170 align:start position:0% transfer from function transfer from function<00:09:13.740> we<00:09:14.339> also<00:09:14.580> don't<00:09:14.700> need<00:09:14.940> token 00:09:15.170 --> 00:09:15.180 align:start position:0% function we also don't need token 00:09:15.180 --> 00:09:16.370 align:start position:0% function we also don't need token approvals<00:09:15.600> and<00:09:15.720> this<00:09:15.839> is<00:09:15.959> actually<00:09:16.080> a<00:09:16.260> really 00:09:16.370 --> 00:09:16.380 align:start position:0% approvals and this is actually a really 00:09:16.380 --> 00:09:18.650 align:start position:0% approvals and this is actually a really big<00:09:16.560> thing<00:09:16.740> for<00:09:16.980> users<00:09:17.339> not<00:09:18.060> developers 00:09:18.650 --> 00:09:18.660 align:start position:0% big thing for users not developers 00:09:18.660 --> 00:09:21.410 align:start position:0% big thing for users not developers because<00:09:19.380> as<00:09:20.220> users<00:09:20.519> you<00:09:20.820> know<00:09:20.940> that<00:09:21.120> token 00:09:21.410 --> 00:09:21.420 align:start position:0% because as users you know that token 00:09:21.420 --> 00:09:24.110 align:start position:0% because as users you know that token approvals<00:09:21.899> are<00:09:22.019> a<00:09:22.260> really<00:09:22.380> big<00:09:22.800> ux<00:09:23.339> pain<00:09:23.880> point 00:09:24.110 --> 00:09:24.120 align:start position:0% approvals are a really big ux pain point 00:09:24.120 --> 00:09:26.389 align:start position:0% approvals are a really big ux pain point right<00:09:24.420> it's<00:09:25.080> due<00:09:25.320> to<00:09:25.500> approve<00:09:25.920> the<00:09:26.100> exact 00:09:26.389 --> 00:09:26.399 align:start position:0% right it's due to approve the exact 00:09:26.399 --> 00:09:28.490 align:start position:0% right it's due to approve the exact amount<00:09:26.760> you<00:09:26.880> want<00:09:27.000> to<00:09:27.120> spend<00:09:27.300> if<00:09:27.959> you<00:09:28.080> do<00:09:28.260> then 00:09:28.490 --> 00:09:28.500 align:start position:0% amount you want to spend if you do then 00:09:28.500 --> 00:09:29.630 align:start position:0% amount you want to spend if you do then you<00:09:28.680> have<00:09:28.800> to<00:09:28.920> always<00:09:29.040> add<00:09:29.339> a<00:09:29.519> second 00:09:29.630 --> 00:09:29.640 align:start position:0% you have to always add a second 00:09:29.640 --> 00:09:31.190 align:start position:0% you have to always add a second transaction<00:09:30.180> every<00:09:30.600> time<00:09:30.779> before<00:09:31.019> you 00:09:31.190 --> 00:09:31.200 align:start position:0% transaction every time before you 00:09:31.200 --> 00:09:32.810 align:start position:0% transaction every time before you interact<00:09:31.500> with<00:09:31.560> the<00:09:31.740> protocol<00:09:31.980> it's<00:09:32.580> more 00:09:32.810 --> 00:09:32.820 align:start position:0% interact with the protocol it's more 00:09:32.820 --> 00:09:35.150 align:start position:0% interact with the protocol it's more expensive<00:09:33.180> it's<00:09:33.420> slower<00:09:33.600> it's<00:09:33.839> worse<00:09:34.080> ux<00:09:34.440> if 00:09:35.150 --> 00:09:35.160 align:start position:0% expensive it's slower it's worse ux if 00:09:35.160 --> 00:09:36.829 align:start position:0% expensive it's slower it's worse ux if you<00:09:35.220> do<00:09:35.339> internet<00:09:35.580> approvals<00:09:36.240> now<00:09:36.600> the 00:09:36.829 --> 00:09:36.839 align:start position:0% you do internet approvals now the 00:09:36.839 --> 00:09:39.110 align:start position:0% you do internet approvals now the protocol<00:09:37.200> has<00:09:37.560> a<00:09:37.740> bug<00:09:37.920> they<00:09:38.580> can<00:09:38.760> train<00:09:38.940> all 00:09:39.110 --> 00:09:39.120 align:start position:0% protocol has a bug they can train all 00:09:39.120 --> 00:09:41.030 align:start position:0% protocol has a bug they can train all your<00:09:39.300> tokens<00:09:39.540> all<00:09:39.839> the<00:09:40.080> time<00:09:40.140> I<00:09:40.680> mean<00:09:40.800> whatever 00:09:41.030 --> 00:09:41.040 align:start position:0% your tokens all the time I mean whatever 00:09:41.040 --> 00:09:43.310 align:start position:0% your tokens all the time I mean whatever whatever<00:09:41.399> you<00:09:41.700> infinite<00:09:42.120> approved<00:09:42.420> right 00:09:43.310 --> 00:09:43.320 align:start position:0% whatever you infinite approved right 00:09:43.320 --> 00:09:45.769 align:start position:0% whatever you infinite approved right with<00:09:43.920> us<00:09:44.160> normally<00:09:44.580> for<00:09:44.760> NATO<00:09:45.060> approvals<00:09:45.600> I 00:09:45.769 --> 00:09:45.779 align:start position:0% with us normally for NATO approvals I 00:09:45.779 --> 00:09:47.150 align:start position:0% with us normally for NATO approvals I have<00:09:45.959> no<00:09:46.019> need<00:09:46.140> for<00:09:46.320> token<00:09:46.620> approvals<00:09:46.980> because 00:09:47.150 --> 00:09:47.160 align:start position:0% have no need for token approvals because 00:09:47.160 --> 00:09:50.389 align:start position:0% have no need for token approvals because you<00:09:47.459> just<00:09:47.640> push<00:09:48.180> the<00:09:48.360> native<00:09:48.600> asset 00:09:50.389 --> 00:09:50.399 align:start position:0% you just push the native asset 00:09:50.399 --> 00:09:52.250 align:start position:0% you just push the native asset that<00:09:50.820> way 00:09:52.250 --> 00:09:52.260 align:start position:0% that way 00:09:52.260 --> 00:09:55.250 align:start position:0% that way next<00:09:52.860> is<00:09:53.220> NATO<00:09:54.120> state<00:09:54.420> math<00:09:54.660> because<00:09:55.019> then<00:09:55.140> you 00:09:55.250 --> 00:09:55.260 align:start position:0% next is NATO state math because then you 00:09:55.260 --> 00:09:57.710 align:start position:0% next is NATO state math because then you show<00:09:55.380> them<00:09:55.500> on<00:09:55.560> the<00:09:55.680> right<00:09:55.740> track<00:09:55.920> uh<00:09:56.760> there's 00:09:57.710 --> 00:09:57.720 align:start position:0% show them on the right track uh there's 00:09:57.720 --> 00:10:00.110 align:start position:0% show them on the right track uh there's no<00:09:57.899> need<00:09:58.080> for<00:09:58.380> a<00:09:58.620> safe<00:09:58.860> math<00:09:59.100> Library<00:09:59.399> there's 00:10:00.110 --> 00:10:00.120 align:start position:0% no need for a safe math Library there's 00:10:00.120 --> 00:10:02.750 align:start position:0% no need for a safe math Library there's no<00:10:00.360> need<00:10:00.600> for<00:10:00.959> some<00:10:01.200> runtime<00:10:01.800> overhead<00:10:02.339> or 00:10:02.750 --> 00:10:02.760 align:start position:0% no need for some runtime overhead or 00:10:02.760 --> 00:10:05.389 align:start position:0% no need for some runtime overhead or like<00:10:03.000> add<00:10:03.360> extra<00:10:03.660> byte<00:10:04.140> code<00:10:04.320> to<00:10:05.100> check<00:10:05.279> for 00:10:05.389 --> 00:10:05.399 align:start position:0% like add extra byte code to check for 00:10:05.399 --> 00:10:07.790 align:start position:0% like add extra byte code to check for Save<00:10:05.640> math<00:10:05.940> the<00:10:06.240> virtual<00:10:06.540> machine<00:10:06.720> itself 00:10:07.790 --> 00:10:07.800 align:start position:0% Save math the virtual machine itself 00:10:07.800 --> 00:10:10.130 align:start position:0% Save math the virtual machine itself support<00:10:08.220> safe<00:10:08.580> math<00:10:08.940> natively<00:10:09.540> by<00:10:09.779> default 00:10:10.130 --> 00:10:10.140 align:start position:0% support safe math natively by default 00:10:10.140 --> 00:10:12.410 align:start position:0% support safe math natively by default which<00:10:11.100> means<00:10:11.279> you<00:10:11.399> get<00:10:11.580> overflow<00:10:12.060> protection 00:10:12.410 --> 00:10:12.420 align:start position:0% which means you get overflow protection 00:10:12.420 --> 00:10:16.610 align:start position:0% which means you get overflow protection for<00:10:12.899> free 00:10:16.610 --> 00:10:16.620 align:start position:0% 00:10:16.620 --> 00:10:19.670 align:start position:0% uh<00:10:17.399> cross<00:10:17.640> call<00:10:17.940> shared<00:10:18.300> memory<00:10:18.600> uh<00:10:19.440> again 00:10:19.670 --> 00:10:19.680 align:start position:0% uh cross call shared memory uh again 00:10:19.680 --> 00:10:22.070 align:start position:0% uh cross call shared memory uh again this<00:10:19.980> isn't<00:10:20.220> like<00:10:20.399> all<00:10:21.300> these<00:10:21.600> things<00:10:21.720> are 00:10:22.070 --> 00:10:22.080 align:start position:0% this isn't like all these things are 00:10:22.080 --> 00:10:24.230 align:start position:0% this isn't like all these things are either<00:10:22.320> eips<00:10:22.740> directly<00:10:23.339> or<00:10:23.519> like<00:10:23.760> variations 00:10:24.230 --> 00:10:24.240 align:start position:0% either eips directly or like variations 00:10:24.240 --> 00:10:26.690 align:start position:0% either eips directly or like variations or<00:10:24.540> inspired<00:10:25.019> by<00:10:25.140> EVS<00:10:25.800> if<00:10:26.220> you<00:10:26.459> guys<00:10:26.580> have 00:10:26.690 --> 00:10:26.700 align:start position:0% or inspired by EVS if you guys have 00:10:26.700 --> 00:10:28.310 align:start position:0% or inspired by EVS if you guys have heard<00:10:26.820> of<00:10:27.000> transient<00:10:27.420> storage<00:10:27.779> right 00:10:28.310 --> 00:10:28.320 align:start position:0% heard of transient storage right 00:10:28.320 --> 00:10:30.769 align:start position:0% heard of transient storage right transient<00:10:28.800> storage<00:10:29.040> is<00:10:29.399> storage<00:10:30.300> that 00:10:30.769 --> 00:10:30.779 align:start position:0% transient storage is storage that 00:10:30.779 --> 00:10:32.870 align:start position:0% transient storage is storage that persists<00:10:31.260> across<00:10:31.740> contract<00:10:32.160> calls<00:10:32.459> within<00:10:32.760> a 00:10:32.870 --> 00:10:32.880 align:start position:0% persists across contract calls within a 00:10:32.880 --> 00:10:33.949 align:start position:0% persists across contract calls within a single<00:10:33.060> transaction 00:10:33.949 --> 00:10:33.959 align:start position:0% single transaction 00:10:33.959 --> 00:10:36.170 align:start position:0% single transaction that's<00:10:34.320> what<00:10:34.440> this<00:10:34.620> is<00:10:34.800> right<00:10:35.220> it's<00:10:35.760> some 00:10:36.170 --> 00:10:36.180 align:start position:0% that's what this is right it's some 00:10:36.180 --> 00:10:38.389 align:start position:0% that's what this is right it's some piece<00:10:36.540> of<00:10:36.660> memory<00:10:36.959> that<00:10:37.800> is<00:10:37.920> accessible 00:10:38.389 --> 00:10:38.399 align:start position:0% piece of memory that is accessible 00:10:38.399 --> 00:10:41.329 align:start position:0% piece of memory that is accessible across<00:10:39.360> contract<00:10:39.720> calls<00:10:40.140> uh<00:10:40.920> the<00:10:41.160> fuel 00:10:41.329 --> 00:10:41.339 align:start position:0% across contract calls uh the fuel 00:10:41.339 --> 00:10:43.850 align:start position:0% across contract calls uh the fuel virtual<00:10:41.760> machine<00:10:42.000> all<00:10:42.720> contract<00:10:43.260> call<00:10:43.500> frames 00:10:43.850 --> 00:10:43.860 align:start position:0% virtual machine all contract call frames 00:10:43.860 --> 00:10:45.949 align:start position:0% virtual machine all contract call frames share<00:10:44.279> this<00:10:44.459> Dynamic<00:10:44.940> which<00:10:45.420> allows<00:10:45.779> you<00:10:45.839> to 00:10:45.949 --> 00:10:45.959 align:start position:0% share this Dynamic which allows you to 00:10:45.959 --> 00:10:47.870 align:start position:0% share this Dynamic which allows you to do<00:10:46.140> things<00:10:46.320> like<00:10:46.620> a<00:10:46.920> completely<00:10:47.220> in-memory 00:10:47.870 --> 00:10:47.880 align:start position:0% do things like a completely in-memory 00:10:47.880 --> 00:10:50.210 align:start position:0% do things like a completely in-memory re-entrancy<00:10:48.779> card<00:10:48.959> you<00:10:49.620> don't<00:10:49.680> have<00:10:49.860> to<00:10:49.980> set<00:10:50.100> a 00:10:50.210 --> 00:10:50.220 align:start position:0% re-entrancy card you don't have to set a 00:10:50.220 --> 00:10:52.069 align:start position:0% re-entrancy card you don't have to set a storage<00:10:50.399> slot<00:10:50.820> for<00:10:51.060> re-entracy<00:10:51.720> card<00:10:51.839> you<00:10:51.959> can 00:10:52.069 --> 00:10:52.079 align:start position:0% storage slot for re-entracy card you can 00:10:52.079 --> 00:10:53.810 align:start position:0% storage slot for re-entracy card you can do<00:10:52.140> an<00:10:52.260> entirely<00:10:52.560> in<00:10:52.680> memory<00:10:52.980> and<00:10:53.579> in<00:10:53.640> fact 00:10:53.810 --> 00:10:53.820 align:start position:0% do an entirely in memory and in fact 00:10:53.820 --> 00:10:55.850 align:start position:0% do an entirely in memory and in fact this<00:10:54.180> is<00:10:54.360> already<00:10:54.540> implemented<00:10:55.200> in<00:10:55.560> the<00:10:55.680> sway 00:10:55.850 --> 00:10:55.860 align:start position:0% this is already implemented in the sway 00:10:55.860 --> 00:10:57.410 align:start position:0% this is already implemented in the sway standard<00:10:56.279> Library<00:10:56.459> it<00:10:56.700> was<00:10:56.820> a<00:10:56.940> function<00:10:57.120> to<00:10:57.300> do 00:10:57.410 --> 00:10:57.420 align:start position:0% standard Library it was a function to do 00:10:57.420 --> 00:10:59.030 align:start position:0% standard Library it was a function to do an<00:10:57.540> in-memory<00:10:57.839> reaction<00:10:58.140> zero<00:10:58.560> so<00:10:58.800> it's<00:10:58.920> not 00:10:59.030 --> 00:10:59.040 align:start position:0% an in-memory reaction zero so it's not 00:10:59.040 --> 00:11:00.230 align:start position:0% an in-memory reaction zero so it's not just<00:10:59.100> theoretical 00:11:00.230 --> 00:11:00.240 align:start position:0% just theoretical 00:11:00.240 --> 00:11:02.870 align:start position:0% just theoretical it<00:11:00.899> also<00:11:01.140> allows<00:11:01.380> you<00:11:01.500> to<00:11:01.680> pass<00:11:01.980> large<00:11:02.399> data 00:11:02.870 --> 00:11:02.880 align:start position:0% it also allows you to pass large data 00:11:02.880 --> 00:11:04.850 align:start position:0% it also allows you to pass large data around<00:11:03.060> with<00:11:03.480> contract<00:11:04.079> calls<00:11:04.440> so<00:11:04.620> if<00:11:04.740> you 00:11:04.850 --> 00:11:04.860 align:start position:0% around with contract calls so if you 00:11:04.860 --> 00:11:07.490 align:start position:0% around with contract calls so if you happen<00:11:05.040> to<00:11:05.220> do<00:11:05.399> some<00:11:05.760> data<00:11:06.480> data<00:11:06.959> computation 00:11:07.490 --> 00:11:07.500 align:start position:0% happen to do some data data computation 00:11:07.500 --> 00:11:09.889 align:start position:0% happen to do some data data computation intensive<00:11:08.100> tasks<00:11:08.820> you<00:11:09.240> can<00:11:09.300> do<00:11:09.420> it<00:11:09.540> just<00:11:09.720> by 00:11:09.889 --> 00:11:09.899 align:start position:0% intensive tasks you can do it just by 00:11:09.899 --> 00:11:13.310 align:start position:0% intensive tasks you can do it just by passing<00:11:10.260> a<00:11:10.320> pointer<00:11:10.560> to<00:11:10.920> the<00:11:11.100> data 00:11:13.310 --> 00:11:13.320 align:start position:0% passing a pointer to the data 00:11:13.320 --> 00:11:17.090 align:start position:0% passing a pointer to the data the<00:11:13.680> next<00:11:13.920> one<00:11:14.040> is<00:11:14.700> transaction<00:11:15.360> scripts<00:11:16.100> uh 00:11:17.090 --> 00:11:17.100 align:start position:0% the next one is transaction scripts uh 00:11:17.100 --> 00:11:19.130 align:start position:0% the next one is transaction scripts uh one<00:11:18.000> of<00:11:18.120> the<00:11:18.240> pain<00:11:18.360> points<00:11:18.720> of<00:11:18.779> a<00:11:18.959> proven 00:11:19.130 --> 00:11:19.140 align:start position:0% one of the pain points of a proven 00:11:19.140 --> 00:11:20.630 align:start position:0% one of the pain points of a proven transfer<00:11:19.560> from<00:11:19.680> in<00:11:19.920> addition<00:11:20.160> to<00:11:20.339> you<00:11:20.519> know 00:11:20.630 --> 00:11:20.640 align:start position:0% transfer from in addition to you know 00:11:20.640 --> 00:11:22.670 align:start position:0% transfer from in addition to you know which<00:11:20.820> the<00:11:21.000> proves<00:11:21.240> being<00:11:21.480> painful<00:11:21.839> is<00:11:22.500> they 00:11:22.670 --> 00:11:22.680 align:start position:0% which the proves being painful is they 00:11:22.680 --> 00:11:25.370 align:start position:0% which the proves being painful is they have<00:11:22.800> to<00:11:22.920> be<00:11:23.040> done<00:11:23.339> in<00:11:23.760> two<00:11:23.940> transactions<00:11:25.019> you 00:11:25.370 --> 00:11:25.380 align:start position:0% have to be done in two transactions you 00:11:25.380 --> 00:11:27.410 align:start position:0% have to be done in two transactions you need<00:11:25.560> a<00:11:25.680> transaction<00:11:25.980> first<00:11:26.279> to<00:11:26.519> approve 00:11:27.410 --> 00:11:27.420 align:start position:0% need a transaction first to approve 00:11:27.420 --> 00:11:29.990 align:start position:0% need a transaction first to approve make<00:11:27.899> a<00:11:28.079> complete<00:11:28.500> and<00:11:28.980> then<00:11:29.160> transfer<00:11:29.640> fund 00:11:29.990 --> 00:11:30.000 align:start position:0% make a complete and then transfer fund 00:11:30.000 --> 00:11:31.069 align:start position:0% make a complete and then transfer fund and<00:11:30.180> it<00:11:30.300> has<00:11:30.420> to<00:11:30.540> be<00:11:30.660> done<00:11:30.839> in<00:11:30.959> two 00:11:31.069 --> 00:11:31.079 align:start position:0% and it has to be done in two 00:11:31.079 --> 00:11:33.170 align:start position:0% and it has to be done in two transactions<00:11:31.740> because<00:11:32.339> an<00:11:32.760> ethereum 00:11:33.170 --> 00:11:33.180 align:start position:0% transactions because an ethereum 00:11:33.180 --> 00:11:35.990 align:start position:0% transactions because an ethereum transaction<00:11:33.540> can<00:11:34.019> only<00:11:34.200> call<00:11:34.740> a<00:11:34.980> contract<00:11:35.339> it 00:11:35.990 --> 00:11:36.000 align:start position:0% transaction can only call a contract it 00:11:36.000 --> 00:11:37.850 align:start position:0% transaction can only call a contract it can't<00:11:36.180> call<00:11:36.420> two<00:11:36.600> contracts<00:11:37.140> or<00:11:37.440> call<00:11:37.620> two 00:11:37.850 --> 00:11:37.860 align:start position:0% can't call two contracts or call two 00:11:37.860 --> 00:11:40.250 align:start position:0% can't call two contracts or call two contracts<00:11:38.459> then<00:11:39.180> do<00:11:39.480> some<00:11:39.660> conditions<00:11:40.079> and 00:11:40.250 --> 00:11:40.260 align:start position:0% contracts then do some conditions and 00:11:40.260 --> 00:11:41.990 align:start position:0% contracts then do some conditions and call<00:11:40.440> a<00:11:40.560> third<00:11:40.680> contract<00:11:41.100> or<00:11:41.339> fourth<00:11:41.880> one 00:11:41.990 --> 00:11:42.000 align:start position:0% call a third contract or fourth one 00:11:42.000 --> 00:11:44.269 align:start position:0% call a third contract or fourth one depending<00:11:42.360> on<00:11:42.420> the<00:11:42.600> same<00:11:42.720> condition 00:11:44.269 --> 00:11:44.279 align:start position:0% depending on the same condition 00:11:44.279 --> 00:11:45.829 align:start position:0% depending on the same condition the<00:11:44.760> fuel<00:11:44.940> protocol<00:11:45.240> has<00:11:45.480> transaction 00:11:45.829 --> 00:11:45.839 align:start position:0% the fuel protocol has transaction 00:11:45.839 --> 00:11:47.990 align:start position:0% the fuel protocol has transaction scripts<00:11:46.320> which<00:11:46.500> are<00:11:46.680> basically<00:11:47.040> byte<00:11:47.880> code 00:11:47.990 --> 00:11:48.000 align:start position:0% scripts which are basically byte code 00:11:48.000 --> 00:11:50.509 align:start position:0% scripts which are basically byte code embedded<00:11:48.540> directly<00:11:48.899> in<00:11:49.079> the<00:11:49.200> transaction<00:11:49.519> and 00:11:50.509 --> 00:11:50.519 align:start position:0% embedded directly in the transaction and 00:11:50.519 --> 00:11:52.250 align:start position:0% embedded directly in the transaction and that<00:11:50.940> is<00:11:51.120> the<00:11:51.240> entry<00:11:51.540> point<00:11:51.660> for<00:11:51.839> execution 00:11:52.250 --> 00:11:52.260 align:start position:0% that is the entry point for execution 00:11:52.260 --> 00:11:54.590 align:start position:0% that is the entry point for execution not<00:11:52.860> the<00:11:53.040> contract<00:11:53.339> call<00:11:53.519> and<00:11:54.060> the<00:11:54.180> script<00:11:54.360> is 00:11:54.590 --> 00:11:54.600 align:start position:0% not the contract call and the script is 00:11:54.600 --> 00:11:56.630 align:start position:0% not the contract call and the script is by<00:11:54.839> code<00:11:55.140> it<00:11:55.320> can<00:11:55.440> do<00:11:55.500> anything<00:11:55.680> it<00:11:56.339> could<00:11:56.459> call 00:11:56.630 --> 00:11:56.640 align:start position:0% by code it can do anything it could call 00:11:56.640 --> 00:11:58.090 align:start position:0% by code it can do anything it could call one<00:11:56.820> contract<00:11:57.060> it<00:11:57.240> we<00:11:57.360> call<00:11:57.480> two<00:11:57.660> contract 00:11:58.090 --> 00:11:58.100 align:start position:0% one contract it we call two contract 00:11:58.100 --> 00:12:00.069 align:start position:0% one contract it we call two contract contracts<00:11:59.100> they<00:11:59.220> could<00:11:59.339> do<00:11:59.459> an<00:11:59.579> atomic 00:12:00.069 --> 00:12:00.079 align:start position:0% contracts they could do an atomic 00:12:00.079 --> 00:12:02.449 align:start position:0% contracts they could do an atomic approve<00:12:01.079> and<00:12:01.320> transfer<00:12:01.740> from 00:12:02.449 --> 00:12:02.459 align:start position:0% approve and transfer from 00:12:02.459 --> 00:12:04.370 align:start position:0% approve and transfer from obviously<00:12:03.000> for<00:12:03.240> fundable<00:12:03.600> assets<00:12:03.959> like<00:12:04.260> I 00:12:04.370 --> 00:12:04.380 align:start position:0% obviously for fundable assets like I 00:12:04.380 --> 00:12:05.930 align:start position:0% obviously for fundable assets like I said<00:12:04.500> before<00:12:04.680> those<00:12:05.160> you<00:12:05.459> know<00:12:05.579> multiple 00:12:05.930 --> 00:12:05.940 align:start position:0% said before those you know multiple 00:12:05.940 --> 00:12:07.310 align:start position:0% said before those you know multiple native<00:12:06.240> assets<00:12:06.600> so<00:12:06.779> you<00:12:06.959> don't<00:12:07.079> actually 00:12:07.310 --> 00:12:07.320 align:start position:0% native assets so you don't actually 00:12:07.320 --> 00:12:09.650 align:start position:0% native assets so you don't actually ironically<00:12:08.160> you<00:12:08.579> don't<00:12:08.700> need<00:12:09.120> this<00:12:09.300> for<00:12:09.540> a 00:12:09.650 --> 00:12:09.660 align:start position:0% ironically you don't need this for a 00:12:09.660 --> 00:12:11.090 align:start position:0% ironically you don't need this for a proven<00:12:10.019> transfer<00:12:10.320> from<00:12:10.440> atomically<00:12:10.920> for 00:12:11.090 --> 00:12:11.100 align:start position:0% proven transfer from atomically for 00:12:11.100 --> 00:12:13.250 align:start position:0% proven transfer from atomically for Native<00:12:11.339> assets<00:12:11.760> but<00:12:12.480> it<00:12:12.600> will<00:12:12.720> be<00:12:12.839> useful<00:12:13.079> for 00:12:13.250 --> 00:12:13.260 align:start position:0% Native assets but it will be useful for 00:12:13.260 --> 00:12:14.389 align:start position:0% Native assets but it will be useful for things<00:12:13.500> like 00:12:14.389 --> 00:12:14.399 align:start position:0% things like 00:12:14.399 --> 00:12:16.790 align:start position:0% things like if<00:12:14.880> you<00:12:15.060> have<00:12:15.120> a<00:12:15.240> non-fungible<00:12:15.720> token<00:12:16.140> that 00:12:16.790 --> 00:12:16.800 align:start position:0% if you have a non-fungible token that 00:12:16.800 --> 00:12:18.050 align:start position:0% if you have a non-fungible token that does<00:12:16.920> have<00:12:17.100> a<00:12:17.220> proven<00:12:17.399> transfer<00:12:17.760> from<00:12:17.820> then 00:12:18.050 --> 00:12:18.060 align:start position:0% does have a proven transfer from then 00:12:18.060 --> 00:12:20.630 align:start position:0% does have a proven transfer from then you<00:12:18.300> can<00:12:18.480> use<00:12:18.899> you<00:12:19.800> can<00:12:19.920> do<00:12:20.040> that<00:12:20.160> atomically 00:12:20.630 --> 00:12:20.640 align:start position:0% you can use you can do that atomically 00:12:20.640 --> 00:12:22.370 align:start position:0% you can use you can do that atomically in<00:12:20.820> a<00:12:21.000> single<00:12:21.180> transaction<00:12:21.480> thanks<00:12:22.140> to 00:12:22.370 --> 00:12:22.380 align:start position:0% in a single transaction thanks to 00:12:22.380 --> 00:12:24.110 align:start position:0% in a single transaction thanks to transaction<00:12:22.680> Scripts 00:12:24.110 --> 00:12:24.120 align:start position:0% transaction Scripts 00:12:24.120 --> 00:12:25.970 align:start position:0% transaction Scripts this<00:12:24.779> also<00:12:25.019> allows<00:12:25.200> you<00:12:25.260> to<00:12:25.380> do<00:12:25.500> things<00:12:25.740> like 00:12:25.970 --> 00:12:25.980 align:start position:0% this also allows you to do things like 00:12:25.980 --> 00:12:28.130 align:start position:0% this also allows you to do things like you<00:12:26.160> know<00:12:26.279> add<00:12:26.579> liquidity<00:12:27.120> to<00:12:27.480> a<00:12:27.600> pool<00:12:27.720> or<00:12:27.959> for 00:12:28.130 --> 00:12:28.140 align:start position:0% you know add liquidity to a pool or for 00:12:28.140 --> 00:12:30.410 align:start position:0% you know add liquidity to a pool or for two<00:12:28.260> different<00:12:28.380> tokens<00:12:29.160> Etc<00:12:29.339> so<00:12:30.060> basically 00:12:30.410 --> 00:12:30.420 align:start position:0% two different tokens Etc so basically 00:12:30.420 --> 00:12:32.389 align:start position:0% two different tokens Etc so basically anything<00:12:30.600> that<00:12:31.079> nowadays<00:12:31.920> you<00:12:32.040> would<00:12:32.220> need 00:12:32.389 --> 00:12:32.399 align:start position:0% anything that nowadays you would need 00:12:32.399 --> 00:12:34.970 align:start position:0% anything that nowadays you would need multiple<00:12:32.760> transactions<00:12:33.360> to<00:12:33.540> do<00:12:33.660> just<00:12:34.380> due<00:12:34.860> to 00:12:34.970 --> 00:12:34.980 align:start position:0% multiple transactions to do just due to 00:12:34.980 --> 00:12:37.250 align:start position:0% multiple transactions to do just due to the<00:12:35.100> nature<00:12:35.399> of<00:12:35.459> ethereum<00:12:36.360> only<00:12:36.480> processing<00:12:37.079> a 00:12:37.250 --> 00:12:37.260 align:start position:0% the nature of ethereum only processing a 00:12:37.260 --> 00:12:39.230 align:start position:0% the nature of ethereum only processing a single<00:12:37.440> contract<00:12:37.740> call<00:12:37.860> for<00:12:38.100> transaction<00:12:38.459> you 00:12:39.230 --> 00:12:39.240 align:start position:0% single contract call for transaction you 00:12:39.240 --> 00:12:41.630 align:start position:0% single contract call for transaction you could<00:12:39.300> do<00:12:39.480> it<00:12:39.600> in<00:12:39.839> a<00:12:39.959> single<00:12:40.200> transaction 00:12:41.630 --> 00:12:41.640 align:start position:0% could do it in a single transaction 00:12:41.640 --> 00:12:43.970 align:start position:0% could do it in a single transaction until 00:12:43.970 --> 00:12:43.980 align:start position:0% until 00:12:43.980 --> 00:12:46.009 align:start position:0% until uh<00:12:44.700> we're<00:12:44.820> getting<00:12:45.000> to<00:12:45.360> the<00:12:45.480> end<00:12:45.720> of<00:12:45.899> the 00:12:46.009 --> 00:12:46.019 align:start position:0% uh we're getting to the end of the 00:12:46.019 --> 00:12:48.710 align:start position:0% uh we're getting to the end of the section<00:12:46.260> and<00:12:47.220> last<00:12:47.459> but<00:12:47.639> not<00:12:47.760> least<00:12:47.940> to<00:12:48.540> reduce 00:12:48.710 --> 00:12:48.720 align:start position:0% section and last but not least to reduce 00:12:48.720 --> 00:12:50.810 align:start position:0% section and last but not least to reduce waste<00:12:49.260> the<00:12:49.680> virtual<00:12:49.980> machine<00:12:50.160> is<00:12:50.459> register 00:12:50.810 --> 00:12:50.820 align:start position:0% waste the virtual machine is register 00:12:50.820 --> 00:12:53.329 align:start position:0% waste the virtual machine is register based<00:12:51.240> and<00:12:51.540> it<00:12:51.660> uses<00:12:51.959> 64-bit<00:12:52.560> words 00:12:53.329 --> 00:12:53.339 align:start position:0% based and it uses 64-bit words 00:12:53.339 --> 00:12:56.569 align:start position:0% based and it uses 64-bit words uh<00:12:53.880> the<00:12:54.060> 64-bit<00:12:54.600> words<00:12:54.899> uh<00:12:55.560> instead<00:12:55.800> of<00:12:55.920> 256 00:12:56.569 --> 00:12:56.579 align:start position:0% uh the 64-bit words uh instead of 256 00:12:56.579 --> 00:12:58.970 align:start position:0% uh the 64-bit words uh instead of 256 bit<00:12:56.820> words<00:12:57.000> like<00:12:57.300> what<00:12:57.420> the<00:12:57.540> evm<00:12:57.959> has<00:12:58.139> means<00:12:58.860> a 00:12:58.970 --> 00:12:58.980 align:start position:0% bit words like what the evm has means a 00:12:58.980 --> 00:13:01.370 align:start position:0% bit words like what the evm has means a lot<00:12:59.100> less<00:12:59.279> waste<00:12:59.700> a<00:12:59.880> loss<00:13:00.240> a<00:13:00.600> lot<00:13:00.720> closer<00:13:01.260> to 00:13:01.370 --> 00:13:01.380 align:start position:0% lot less waste a loss a lot closer to 00:13:01.380 --> 00:13:03.470 align:start position:0% lot less waste a loss a lot closer to the<00:13:01.560> metal<00:13:01.680> when<00:13:01.980> it<00:13:02.100> executes<00:13:02.579> because<00:13:03.180> you 00:13:03.470 --> 00:13:03.480 align:start position:0% the metal when it executes because you 00:13:03.480 --> 00:13:05.509 align:start position:0% the metal when it executes because you don't<00:13:03.600> need<00:13:03.899> if<00:13:04.260> you<00:13:04.440> integer<00:13:04.920> math<00:13:05.220> every 00:13:05.509 --> 00:13:05.519 align:start position:0% don't need if you integer math every 00:13:05.519 --> 00:13:07.610 align:start position:0% don't need if you integer math every time<00:13:05.700> you<00:13:05.760> do<00:13:05.940> an<00:13:06.060> addition<00:13:06.300> you<00:13:07.019> can<00:13:07.139> just<00:13:07.320> add 00:13:07.610 --> 00:13:07.620 align:start position:0% time you do an addition you can just add 00:13:07.620 --> 00:13:09.769 align:start position:0% time you do an addition you can just add two<00:13:07.800> numbers<00:13:08.040> together<00:13:08.279> and<00:13:08.700> this<00:13:09.360> goes 00:13:09.769 --> 00:13:09.779 align:start position:0% two numbers together and this goes 00:13:09.779 --> 00:13:13.069 align:start position:0% two numbers together and this goes really<00:13:09.899> fast<00:13:10.339> uh<00:13:11.339> and<00:13:12.000> combining<00:13:12.779> these 00:13:13.069 --> 00:13:13.079 align:start position:0% really fast uh and combining these 00:13:13.079 --> 00:13:14.449 align:start position:0% really fast uh and combining these things<00:13:13.260> together<00:13:13.440> including<00:13:13.980> being<00:13:14.160> register 00:13:14.449 --> 00:13:14.459 align:start position:0% things together including being register 00:13:14.459 --> 00:13:17.210 align:start position:0% things together including being register based<00:13:14.940> means<00:13:15.779> that<00:13:15.899> you're<00:13:16.079> executing<00:13:16.680> a<00:13:17.040> lot 00:13:17.210 --> 00:13:17.220 align:start position:0% based means that you're executing a lot 00:13:17.220 --> 00:13:19.190 align:start position:0% based means that you're executing a lot fewer<00:13:17.700> instructions<00:13:18.300> to<00:13:18.540> do<00:13:18.660> the<00:13:18.839> same<00:13:18.959> work 00:13:19.190 --> 00:13:19.200 align:start position:0% fewer instructions to do the same work 00:13:19.200 --> 00:13:22.069 align:start position:0% fewer instructions to do the same work in<00:13:19.920> addition<00:13:20.160> to<00:13:20.399> just<00:13:20.579> executing<00:13:21.060> faster<00:13:21.420> and 00:13:22.069 --> 00:13:22.079 align:start position:0% in addition to just executing faster and 00:13:22.079 --> 00:13:24.110 align:start position:0% in addition to just executing faster and that<00:13:22.440> reducing<00:13:23.100> the<00:13:23.279> number<00:13:23.459> of<00:13:23.639> instructions 00:13:24.110 --> 00:13:24.120 align:start position:0% that reducing the number of instructions 00:13:24.120 --> 00:13:26.750 align:start position:0% that reducing the number of instructions executed<00:13:24.660> to<00:13:24.839> do<00:13:25.260> the<00:13:25.380> same<00:13:25.500> work<00:13:25.740> is<00:13:26.579> very 00:13:26.750 --> 00:13:26.760 align:start position:0% executed to do the same work is very 00:13:26.760 --> 00:13:28.730 align:start position:0% executed to do the same work is very important<00:13:27.120> because<00:13:27.600> gas<00:13:28.320> accounting 00:13:28.730 --> 00:13:28.740 align:start position:0% important because gas accounting 00:13:28.740 --> 00:13:31.310 align:start position:0% important because gas accounting overhead<00:13:29.160> is<00:13:30.120> a<00:13:30.360> huge<00:13:30.839> portion<00:13:31.079> of<00:13:31.200> the 00:13:31.310 --> 00:13:31.320 align:start position:0% overhead is a huge portion of the 00:13:31.320 --> 00:13:32.870 align:start position:0% overhead is a huge portion of the overhead<00:13:31.680> of<00:13:32.040> the<00:13:32.100> virtual<00:13:32.339> machine<00:13:32.519> it's 00:13:32.870 --> 00:13:32.880 align:start position:0% overhead of the virtual machine it's 00:13:32.880 --> 00:13:34.129 align:start position:0% overhead of the virtual machine it's like<00:13:33.120> enormous 00:13:34.129 --> 00:13:34.139 align:start position:0% like enormous 00:13:34.139 --> 00:13:36.230 align:start position:0% like enormous uh<00:13:34.980> and<00:13:35.220> you<00:13:35.339> want<00:13:35.519> to<00:13:35.639> reduce<00:13:35.700> that<00:13:35.940> overhead 00:13:36.230 --> 00:13:36.240 align:start position:0% uh and you want to reduce that overhead 00:13:36.240 --> 00:13:37.730 align:start position:0% uh and you want to reduce that overhead as<00:13:36.420> much<00:13:36.540> as<00:13:36.660> possible<00:13:36.959> to<00:13:37.200> squeeze<00:13:37.500> as<00:13:37.560> much 00:13:37.730 --> 00:13:37.740 align:start position:0% as much as possible to squeeze as much 00:13:37.740 --> 00:13:39.290 align:start position:0% as much as possible to squeeze as much throughput<00:13:38.100> as<00:13:38.339> you<00:13:38.459> can<00:13:38.579> on<00:13:39.000> the<00:13:39.180> same 00:13:39.290 --> 00:13:39.300 align:start position:0% throughput as you can on the same 00:13:39.300 --> 00:13:40.610 align:start position:0% throughput as you can on the same physical<00:13:39.540> Hardware 00:13:40.610 --> 00:13:40.620 align:start position:0% physical Hardware 00:13:40.620 --> 00:13:42.829 align:start position:0% physical Hardware so<00:13:40.860> by<00:13:41.100> being<00:13:41.279> registered<00:13:41.579> based<00:13:41.940> you<00:13:42.120> greatly 00:13:42.829 --> 00:13:42.839 align:start position:0% so by being registered based you greatly 00:13:42.839 --> 00:13:44.389 align:start position:0% so by being registered based you greatly reduce<00:13:43.019> that 00:13:44.389 --> 00:13:44.399 align:start position:0% reduce that 00:13:44.399 --> 00:13:47.389 align:start position:0% reduce that doesn't<00:13:45.000> really<00:13:45.180> affect<00:13:45.540> like<00:13:46.380> the<00:13:46.740> end<00:13:47.040> user 00:13:47.389 --> 00:13:47.399 align:start position:0% doesn't really affect like the end user 00:13:47.399 --> 00:13:48.949 align:start position:0% doesn't really affect like the end user at<00:13:47.519> all<00:13:47.639> because<00:13:47.820> you<00:13:48.000> know<00:13:48.060> you<00:13:48.360> as<00:13:48.540> a<00:13:48.660> user 00:13:48.949 --> 00:13:48.959 align:start position:0% at all because you know you as a user 00:13:48.959 --> 00:13:51.170 align:start position:0% at all because you know you as a user you<00:13:49.500> know<00:13:49.620> there's<00:13:49.800> medium<00:13:50.279> stack<00:13:50.700> based<00:13:51.060> but 00:13:51.170 --> 00:13:51.180 align:start position:0% you know there's medium stack based but 00:13:51.180 --> 00:13:53.090 align:start position:0% you know there's medium stack based but you<00:13:51.360> don't<00:13:51.480> care<00:13:51.839> those<00:13:52.200> Statics<00:13:52.680> if<00:13:52.920> you're<00:13:52.980> a 00:13:53.090 --> 00:13:53.100 align:start position:0% you don't care those Statics if you're a 00:13:53.100 --> 00:13:55.250 align:start position:0% you don't care those Statics if you're a user<00:13:53.459> or<00:13:53.579> a<00:13:53.700> developer<00:13:54.060> it<00:13:54.660> just<00:13:54.779> is<00:13:54.899> it<00:13:55.079> just 00:13:55.250 --> 00:13:55.260 align:start position:0% user or a developer it just is it just 00:13:55.260 --> 00:13:56.930 align:start position:0% user or a developer it just is it just works<00:13:55.560> right 00:13:56.930 --> 00:13:56.940 align:start position:0% works right 00:13:56.940 --> 00:13:59.509 align:start position:0% works right okay<00:13:57.360> on<00:13:57.660> just<00:13:57.899> Man<00:13:58.079> four<00:13:58.380> and<00:13:58.680> an<00:13:59.040> unmatched 00:13:59.509 --> 00:13:59.519 align:start position:0% okay on just Man four and an unmatched 00:13:59.519 --> 00:14:02.449 align:start position:0% okay on just Man four and an unmatched developer<00:14:00.060> experience 00:14:02.449 --> 00:14:02.459 align:start position:0% developer experience 00:14:02.459 --> 00:14:06.410 align:start position:0% developer experience uh<00:14:03.300> standard<00:14:03.720> Library<00:14:03.899> so<00:14:04.800> the<00:14:05.459> language<00:14:05.700> is 00:14:06.410 --> 00:14:06.420 align:start position:0% uh standard Library so the language is 00:14:06.420 --> 00:14:09.769 align:start position:0% uh standard Library so the language is very<00:14:06.899> minimal<00:14:07.980> a<00:14:08.579> lot<00:14:08.760> of<00:14:08.880> things<00:14:09.060> are<00:14:09.420> moved 00:14:09.769 --> 00:14:09.779 align:start position:0% very minimal a lot of things are moved 00:14:09.779 --> 00:14:12.710 align:start position:0% very minimal a lot of things are moved to<00:14:09.899> the<00:14:10.019> standard<00:14:10.320> Library<00:14:10.500> one<00:14:11.339> example<00:14:12.300> that 00:14:12.710 --> 00:14:12.720 align:start position:0% to the standard Library one example that 00:14:12.720 --> 00:14:15.769 align:start position:0% to the standard Library one example that we'll<00:14:12.899> reuse<00:14:13.320> and<00:14:13.560> subsequent<00:14:14.040> slides<00:14:14.339> is<00:14:14.779> the 00:14:15.769 --> 00:14:15.779 align:start position:0% we'll reuse and subsequent slides is the 00:14:15.779 --> 00:14:18.590 align:start position:0% we'll reuse and subsequent slides is the EC<00:14:16.079> recover<00:14:16.500> right<00:14:17.040> this<00:14:17.279> thing<00:14:17.459> here<00:14:17.700> will 00:14:18.590 --> 00:14:18.600 align:start position:0% EC recover right this thing here will 00:14:18.600 --> 00:14:22.690 align:start position:0% EC recover right this thing here will recover<00:14:19.139> the<00:14:19.860> public<00:14:20.639> key<00:14:20.940> or<00:14:21.120> the<00:14:21.300> address 00:14:22.690 --> 00:14:22.700 align:start position:0% recover the public key or the address 00:14:22.700 --> 00:14:25.310 align:start position:0% recover the public key or the address does<00:14:23.700> an<00:14:23.880> implementation<00:14:24.300> detail<00:14:24.720> from<00:14:25.079> a 00:14:25.310 --> 00:14:25.320 align:start position:0% does an implementation detail from a 00:14:25.320 --> 00:14:28.310 align:start position:0% does an implementation detail from a signature<00:14:25.800> and<00:14:25.920> a<00:14:26.100> message<00:14:26.279> hash<00:14:26.760> right<00:14:27.540> in 00:14:28.310 --> 00:14:28.320 align:start position:0% signature and a message hash right in 00:14:28.320 --> 00:14:31.129 align:start position:0% signature and a message hash right in solidity<00:14:29.060> this<00:14:30.060> is<00:14:30.300> part<00:14:30.600> of<00:14:30.779> the<00:14:30.959> language 00:14:31.129 --> 00:14:31.139 align:start position:0% solidity this is part of the language 00:14:31.139 --> 00:14:32.810 align:start position:0% solidity this is part of the language itself<00:14:31.680> in<00:14:31.980> other<00:14:32.100> words<00:14:32.220> the<00:14:32.399> compiler 00:14:32.810 --> 00:14:32.820 align:start position:0% itself in other words the compiler 00:14:32.820 --> 00:14:36.829 align:start position:0% itself in other words the compiler developers<00:14:33.420> need<00:14:34.139> to<00:14:34.380> go<00:14:34.620> in<00:14:34.860> and<00:14:35.459> add<00:14:36.120> some 00:14:36.829 --> 00:14:36.839 align:start position:0% developers need to go in and add some 00:14:36.839 --> 00:14:38.870 align:start position:0% developers need to go in and add some special<00:14:37.079> magic<00:14:37.440> method<00:14:37.920> into<00:14:38.160> the<00:14:38.399> compiler 00:14:38.870 --> 00:14:38.880 align:start position:0% special magic method into the compiler 00:14:38.880 --> 00:14:41.870 align:start position:0% special magic method into the compiler embed<00:14:39.480> it<00:14:39.600> into<00:14:39.720> the<00:14:39.899> compiler<00:14:40.740> easy<00:14:41.279> recovery 00:14:41.870 --> 00:14:41.880 align:start position:0% embed it into the compiler easy recovery 00:14:41.880 --> 00:14:43.009 align:start position:0% embed it into the compiler easy recovery right 00:14:43.009 --> 00:14:43.019 align:start position:0% right 00:14:43.019 --> 00:14:45.829 align:start position:0% right that<00:14:43.500> does<00:14:43.620> not<00:14:43.800> exist<00:14:44.100> in<00:14:44.220> swine<00:14:44.639> this<00:14:45.360> way 00:14:45.829 --> 00:14:45.839 align:start position:0% that does not exist in swine this way 00:14:45.839 --> 00:14:47.389 align:start position:0% that does not exist in swine this way you<00:14:45.959> compiler<00:14:46.380> and<00:14:46.560> the<00:14:46.680> sway<00:14:46.800> compiler<00:14:47.279> team 00:14:47.389 --> 00:14:47.399 align:start position:0% you compiler and the sway compiler team 00:14:47.399 --> 00:14:49.009 align:start position:0% you compiler and the sway compiler team don't<00:14:47.579> know<00:14:47.760> what<00:14:47.880> EC<00:14:48.180> recovery<00:14:48.600> is<00:14:48.720> this 00:14:49.009 --> 00:14:49.019 align:start position:0% don't know what EC recovery is this 00:14:49.019 --> 00:14:50.930 align:start position:0% don't know what EC recovery is this exists<00:14:49.380> in<00:14:49.680> the<00:14:49.860> standard<00:14:50.160> Library<00:14:50.399> which<00:14:50.820> is 00:14:50.930 --> 00:14:50.940 align:start position:0% exists in the standard Library which is 00:14:50.940 --> 00:14:52.430 align:start position:0% exists in the standard Library which is written<00:14:51.240> the<00:14:51.540> standard<00:14:51.899> library<00:14:52.019> is<00:14:52.260> better 00:14:52.430 --> 00:14:52.440 align:start position:0% written the standard library is better 00:14:52.440 --> 00:14:55.490 align:start position:0% written the standard library is better in<00:14:52.800> Suite<00:14:53.399> although<00:14:54.120> it's<00:14:54.300> software<00:14:54.899> not 00:14:55.490 --> 00:14:55.500 align:start position:0% in Suite although it's software not 00:14:55.500 --> 00:14:58.129 align:start position:0% in Suite although it's software not embedded<00:14:56.339> into<00:14:56.459> the<00:14:56.760> compiler 00:14:58.129 --> 00:14:58.139 align:start position:0% embedded into the compiler 00:14:58.139 --> 00:14:59.689 align:start position:0% embedded into the compiler um<00:14:58.199> here's<00:14:58.440> a<00:14:58.560> QR<00:14:58.800> code<00:14:58.920> I<00:14:59.100> think<00:14:59.160> to<00:14:59.339> link<00:14:59.519> to 00:14:59.689 --> 00:14:59.699 align:start position:0% um here's a QR code I think to link to 00:14:59.699 --> 00:15:01.850 align:start position:0% um here's a QR code I think to link to the<00:14:59.760> implementation<00:15:00.180> of<00:15:00.420> easier<00:15:00.720> government 00:15:01.850 --> 00:15:01.860 align:start position:0% the implementation of easier government 00:15:01.860 --> 00:15:04.129 align:start position:0% the implementation of easier government why<00:15:02.339> is<00:15:02.519> this<00:15:02.699> good<00:15:02.940> it's<00:15:03.540> good<00:15:03.720> because<00:15:03.899> it 00:15:04.129 --> 00:15:04.139 align:start position:0% why is this good it's good because it 00:15:04.139 --> 00:15:06.110 align:start position:0% why is this good it's good because it means<00:15:04.440> that<00:15:04.560> the<00:15:04.740> standard<00:15:05.160> Library<00:15:05.399> can<00:15:05.820> move 00:15:06.110 --> 00:15:06.120 align:start position:0% means that the standard Library can move 00:15:06.120 --> 00:15:08.689 align:start position:0% means that the standard Library can move very<00:15:06.540> fast<00:15:06.779> because<00:15:07.560> you<00:15:07.800> don't<00:15:07.980> have<00:15:08.160> to<00:15:08.519> get 00:15:08.689 --> 00:15:08.699 align:start position:0% very fast because you don't have to get 00:15:08.699 --> 00:15:10.310 align:start position:0% very fast because you don't have to get the<00:15:08.880> compiler<00:15:09.300> developers<00:15:09.779> to<00:15:09.959> do<00:15:10.079> something 00:15:10.310 --> 00:15:10.320 align:start position:0% the compiler developers to do something 00:15:10.320 --> 00:15:13.009 align:start position:0% the compiler developers to do something this<00:15:11.040> is<00:15:11.220> in<00:15:11.279> this<00:15:11.459> way<00:15:11.639> any<00:15:12.000> if<00:15:12.600> any<00:15:12.720> of<00:15:12.899> you 00:15:13.009 --> 00:15:13.019 align:start position:0% this is in this way any if any of you 00:15:13.019 --> 00:15:14.870 align:start position:0% this is in this way any if any of you can<00:15:13.199> write<00:15:13.260> solidity<00:15:13.740> right<00:15:14.100> you<00:15:14.459> and<00:15:14.639> you<00:15:14.820> can 00:15:14.870 --> 00:15:14.880 align:start position:0% can write solidity right you and you can 00:15:14.880 --> 00:15:16.970 align:start position:0% can write solidity right you and you can write<00:15:15.000> sway<00:15:15.300> you<00:15:16.139> can<00:15:16.260> just<00:15:16.440> add<00:15:16.560> stuff<00:15:16.800> to 00:15:16.970 --> 00:15:16.980 align:start position:0% write sway you can just add stuff to 00:15:16.980 --> 00:15:18.410 align:start position:0% write sway you can just add stuff to this<00:15:17.160> movement<00:15:17.459> submit<00:15:17.699> a<00:15:17.820> PR<00:15:17.880> and<00:15:18.120> just<00:15:18.240> add 00:15:18.410 --> 00:15:18.420 align:start position:0% this movement submit a PR and just add 00:15:18.420 --> 00:15:20.090 align:start position:0% this movement submit a PR and just add stuff<00:15:18.600> to<00:15:18.720> the<00:15:18.839> standard<00:15:19.079> Library<00:15:19.260> you<00:15:19.980> don't 00:15:20.090 --> 00:15:20.100 align:start position:0% stuff to the standard Library you don't 00:15:20.100 --> 00:15:21.530 align:start position:0% stuff to the standard Library you don't need<00:15:20.220> to<00:15:20.339> know<00:15:20.399> how<00:15:20.579> a<00:15:20.699> compiler<00:15:21.060> works<00:15:21.300> right 00:15:21.530 --> 00:15:21.540 align:start position:0% need to know how a compiler works right 00:15:21.540 --> 00:15:23.509 align:start position:0% need to know how a compiler works right you<00:15:21.779> just<00:15:21.899> might<00:15:22.139> swag<00:15:22.740> which<00:15:22.980> is<00:15:23.100> writing<00:15:23.399> the 00:15:23.509 --> 00:15:23.519 align:start position:0% you just might swag which is writing the 00:15:23.519 --> 00:15:26.509 align:start position:0% you just might swag which is writing the smart<00:15:23.699> contract<00:15:24.000> code<00:15:24.600> uh<00:15:25.440> so<00:15:25.620> it<00:15:25.800> allows<00:15:26.220> the 00:15:26.509 --> 00:15:26.519 align:start position:0% smart contract code uh so it allows the 00:15:26.519 --> 00:15:28.550 align:start position:0% smart contract code uh so it allows the language<00:15:27.300> to<00:15:27.660> move<00:15:27.779> quickly<00:15:28.079> because<00:15:28.260> it's 00:15:28.550 --> 00:15:28.560 align:start position:0% language to move quickly because it's 00:15:28.560 --> 00:15:30.350 align:start position:0% language to move quickly because it's lean<00:15:28.920> and<00:15:29.399> it<00:15:29.519> allows<00:15:29.760> the<00:15:29.940> standard<00:15:30.180> library 00:15:30.350 --> 00:15:30.360 align:start position:0% lean and it allows the standard library 00:15:30.360 --> 00:15:31.910 align:start position:0% lean and it allows the standard library to<00:15:30.660> move<00:15:30.779> quickly<00:15:31.079> because<00:15:31.380> it<00:15:31.560> doesn't<00:15:31.680> you 00:15:31.910 --> 00:15:31.920 align:start position:0% to move quickly because it doesn't you 00:15:31.920 --> 00:15:33.769 align:start position:0% to move quickly because it doesn't you don't<00:15:32.040> need<00:15:32.160> to<00:15:32.220> know<00:15:32.339> how<00:15:32.579> compiler<00:15:33.060> Works<00:15:33.360> uh 00:15:33.769 --> 00:15:33.779 align:start position:0% don't need to know how compiler Works uh 00:15:33.779 --> 00:15:35.750 align:start position:0% don't need to know how compiler Works uh to<00:15:33.959> contribute<00:15:34.320> to<00:15:34.440> the<00:15:34.560> standard<00:15:34.800> Library 00:15:35.750 --> 00:15:35.760 align:start position:0% to contribute to the standard Library 00:15:35.760 --> 00:15:38.269 align:start position:0% to contribute to the standard Library and<00:15:36.240> this<00:15:36.480> basically<00:15:37.139> almost<00:15:37.620> every<00:15:37.920> function 00:15:38.269 --> 00:15:38.279 align:start position:0% and this basically almost every function 00:15:38.279 --> 00:15:40.250 align:start position:0% and this basically almost every function that<00:15:38.519> isn't<00:15:38.760> actually<00:15:38.880> like<00:15:39.240> core<00:15:39.839> to<00:15:40.139> the 00:15:40.250 --> 00:15:40.260 align:start position:0% that isn't actually like core to the 00:15:40.260 --> 00:15:42.050 align:start position:0% that isn't actually like core to the language<00:15:40.380> itself<00:15:40.800> is<00:15:41.459> in<00:15:41.699> the<00:15:41.820> standard 00:15:42.050 --> 00:15:42.060 align:start position:0% language itself is in the standard 00:15:42.060 --> 00:15:44.990 align:start position:0% language itself is in the standard library<00:15:42.300> and<00:15:42.540> not<00:15:42.660> in<00:15:42.839> the<00:15:42.959> language<00:15:43.079> itself 00:15:44.990 --> 00:15:45.000 align:start position:0% library and not in the language itself 00:15:45.000 --> 00:15:46.069 align:start position:0% library and not in the language itself next 00:15:46.069 --> 00:15:46.079 align:start position:0% next 00:15:46.079 --> 00:15:49.930 align:start position:0% next uh<00:15:46.500> generics<00:15:46.860> in<00:15:47.040> some<00:15:47.160> types<00:15:47.820> uh<00:15:48.480> generics 00:15:49.930 --> 00:15:49.940 align:start position:0% uh generics in some types uh generics 00:15:49.940 --> 00:15:53.810 align:start position:0% uh generics in some types uh generics is<00:15:50.940> the<00:15:51.240> diagonal<00:15:52.019> brackets<00:15:52.320> right<00:15:52.639> so<00:15:53.639> you 00:15:53.810 --> 00:15:53.820 align:start position:0% is the diagonal brackets right so you 00:15:53.820 --> 00:15:56.449 align:start position:0% is the diagonal brackets right so you can<00:15:54.000> Define<00:15:54.480> the<00:15:54.899> type<00:15:55.019> of<00:15:55.199> assign<00:15:55.500> later 00:15:56.449 --> 00:15:56.459 align:start position:0% can Define the type of assign later 00:15:56.459 --> 00:16:00.110 align:start position:0% can Define the type of assign later uh<00:15:57.060> some<00:15:57.300> types<00:15:57.660> are<00:15:58.620> you<00:15:59.100> know<00:15:59.279> either<00:15:59.459> one<00:15:59.880> or 00:16:00.110 --> 00:16:00.120 align:start position:0% uh some types are you know either one or 00:16:00.120 --> 00:16:03.650 align:start position:0% uh some types are you know either one or the<00:16:00.360> other<00:16:00.480> uh<00:16:01.440> rather<00:16:01.800> kind<00:16:02.459> of<00:16:02.579> like<00:16:02.639> unions 00:16:03.650 --> 00:16:03.660 align:start position:0% the other uh rather kind of like unions 00:16:03.660 --> 00:16:07.009 align:start position:0% the other uh rather kind of like unions uh<00:16:04.459> combine<00:16:05.459> them<00:16:05.760> together<00:16:06.000> and<00:16:06.480> you<00:16:06.600> can<00:16:06.720> get 00:16:07.009 --> 00:16:07.019 align:start position:0% uh combine them together and you can get 00:16:07.019 --> 00:16:08.870 align:start position:0% uh combine them together and you can get things<00:16:07.440> like<00:16:07.740> a<00:16:07.980> result<00:16:08.160> for<00:16:08.459> instance<00:16:08.699> which 00:16:08.870 --> 00:16:08.880 align:start position:0% things like a result for instance which 00:16:08.880 --> 00:16:10.670 align:start position:0% things like a result for instance which we'll<00:16:09.060> talk<00:16:09.240> about<00:16:09.300> on<00:16:09.540> the<00:16:09.660> next<00:16:09.720> slide 00:16:10.670 --> 00:16:10.680 align:start position:0% we'll talk about on the next slide 00:16:10.680 --> 00:16:12.949 align:start position:0% we'll talk about on the next slide but<00:16:11.220> generics<00:16:11.699> are<00:16:11.820> very<00:16:11.940> good<00:16:12.120> because<00:16:12.600> they 00:16:12.949 --> 00:16:12.959 align:start position:0% but generics are very good because they 00:16:12.959 --> 00:16:15.530 align:start position:0% but generics are very good because they they<00:16:13.260> allow<00:16:13.920> you<00:16:14.040> to<00:16:14.220> reuse<00:16:14.579> code<00:16:15.000> to<00:16:15.240> reuse 00:16:15.530 --> 00:16:15.540 align:start position:0% they allow you to reuse code to reuse 00:16:15.540 --> 00:16:18.230 align:start position:0% they allow you to reuse code to reuse logic<00:16:15.959> without<00:16:16.680> having<00:16:17.040> to<00:16:17.220> duplicate<00:16:17.940> code 00:16:18.230 --> 00:16:18.240 align:start position:0% logic without having to duplicate code 00:16:18.240 --> 00:16:21.050 align:start position:0% logic without having to duplicate code right<00:16:18.779> there's<00:16:19.260> a<00:16:19.560> safe<00:16:19.740> math<00:16:20.040> library<00:16:20.399> right 00:16:21.050 --> 00:16:21.060 align:start position:0% right there's a safe math library right 00:16:21.060 --> 00:16:22.970 align:start position:0% right there's a safe math library right versatility<00:16:21.600> but<00:16:22.019> if<00:16:22.139> you<00:16:22.260> want<00:16:22.380> to<00:16:22.440> use<00:16:22.620> safe 00:16:22.970 --> 00:16:22.980 align:start position:0% versatility but if you want to use safe 00:16:22.980 --> 00:16:26.810 align:start position:0% versatility but if you want to use safe math<00:16:23.220> for<00:16:23.639> like<00:16:23.880> a<00:16:24.600> un<00:16:24.720> 64<00:16:25.380> instead<00:16:25.800> of<00:16:25.860> a<00:16:25.980> un256 00:16:26.810 --> 00:16:26.820 align:start position:0% math for like a un 64 instead of a un256 00:16:26.820 --> 00:16:28.850 align:start position:0% math for like a un 64 instead of a un256 you<00:16:27.000> just<00:16:27.120> have<00:16:27.240> to<00:16:27.360> like<00:16:27.600> copy<00:16:28.380> all<00:16:28.500> that<00:16:28.680> code 00:16:28.850 --> 00:16:28.860 align:start position:0% you just have to like copy all that code 00:16:28.860 --> 00:16:31.189 align:start position:0% you just have to like copy all that code and<00:16:29.220> change<00:16:29.519> the<00:16:29.760> type<00:16:29.940> right<00:16:30.600> if<00:16:30.899> you<00:16:31.079> have 00:16:31.189 --> 00:16:31.199 align:start position:0% and change the type right if you have 00:16:31.199 --> 00:16:32.329 align:start position:0% and change the type right if you have generics<00:16:31.560> you<00:16:31.800> don't<00:16:31.920> have<00:16:32.040> to<00:16:32.100> do<00:16:32.220> that 00:16:32.329 --> 00:16:32.339 align:start position:0% generics you don't have to do that 00:16:32.339 --> 00:16:34.069 align:start position:0% generics you don't have to do that because<00:16:32.519> you<00:16:32.820> can<00:16:32.940> just<00:16:33.060> make<00:16:33.240> logic<00:16:33.660> generic 00:16:34.069 --> 00:16:34.079 align:start position:0% because you can just make logic generic 00:16:34.079 --> 00:16:36.170 align:start position:0% because you can just make logic generic over<00:16:34.380> any<00:16:34.980> type<00:16:35.220> that<00:16:35.639> supports<00:16:36.000> some 00:16:36.170 --> 00:16:36.180 align:start position:0% over any type that supports some 00:16:36.180 --> 00:16:39.590 align:start position:0% over any type that supports some functions<00:16:36.540> like<00:16:36.720> say<00:16:36.959> an<00:16:37.139> addition<00:16:37.880> and<00:16:38.880> then 00:16:39.590 --> 00:16:39.600 align:start position:0% functions like say an addition and then 00:16:39.600 --> 00:16:41.689 align:start position:0% functions like say an addition and then you<00:16:40.019> know<00:16:40.139> instantiate<00:16:40.800> instantiated<00:16:41.579> with 00:16:41.689 --> 00:16:41.699 align:start position:0% you know instantiate instantiated with 00:16:41.699 --> 00:16:44.449 align:start position:0% you know instantiate instantiated with different<00:16:41.880> types<00:16:42.540> so<00:16:43.139> it<00:16:43.259> allows<00:16:43.620> much<00:16:43.980> easier 00:16:44.449 --> 00:16:44.459 align:start position:0% different types so it allows much easier 00:16:44.459 --> 00:16:47.449 align:start position:0% different types so it allows much easier code<00:16:44.639> reuse<00:16:45.139> without<00:16:46.139> having<00:16:46.440> to<00:16:46.680> well<00:16:47.100> it 00:16:47.449 --> 00:16:47.459 align:start position:0% code reuse without having to well it 00:16:47.459 --> 00:16:49.430 align:start position:0% code reuse without having to well it allows<00:16:47.759> it<00:16:47.880> allows<00:16:48.120> code<00:16:48.240> reviews<00:16:48.420> period<00:16:48.899> uh 00:16:49.430 --> 00:16:49.440 align:start position:0% allows it allows code reviews period uh 00:16:49.440 --> 00:16:50.990 align:start position:0% allows it allows code reviews period uh for<00:16:49.620> things<00:16:49.800> that<00:16:50.040> are<00:16:50.160> the<00:16:50.399> same<00:16:50.519> logic<00:16:50.820> but 00:16:50.990 --> 00:16:51.000 align:start position:0% for things that are the same logic but 00:16:51.000 --> 00:16:52.370 align:start position:0% for things that are the same logic but in<00:16:51.240> different<00:16:51.360> types 00:16:52.370 --> 00:16:52.380 align:start position:0% in different types 00:16:52.380 --> 00:16:54.590 align:start position:0% in different types uh<00:16:53.100> now<00:16:53.339> why<00:16:53.820> do<00:16:53.940> we<00:16:54.060> care<00:16:54.240> about<00:16:54.360> results 00:16:54.590 --> 00:16:54.600 align:start position:0% uh now why do we care about results 00:16:54.600 --> 00:16:58.310 align:start position:0% uh now why do we care about results specifically<00:16:55.380> and<00:16:56.220> why<00:16:56.459> is<00:16:56.579> this<00:16:56.759> important 00:16:58.310 --> 00:16:58.320 align:start position:0% specifically and why is this important 00:16:58.320 --> 00:17:00.050 align:start position:0% specifically and why is this important we're<00:16:58.680> going<00:16:58.860> to<00:16:58.920> go<00:16:59.100> back<00:16:59.279> to<00:16:59.519> our<00:16:59.759> example<00:17:00.000> of 00:17:00.050 --> 00:17:00.060 align:start position:0% we're going to go back to our example of 00:17:00.060 --> 00:17:01.430 align:start position:0% we're going to go back to our example of easy<00:17:00.240> recover 00:17:01.430 --> 00:17:01.440 align:start position:0% easy recover 00:17:01.440 --> 00:17:04.909 align:start position:0% easy recover on<00:17:02.279> ethereum<00:17:02.940> and<00:17:03.120> solidity<00:17:03.620> the<00:17:04.620> easier 00:17:04.909 --> 00:17:04.919 align:start position:0% on ethereum and solidity the easier 00:17:04.919 --> 00:17:06.949 align:start position:0% on ethereum and solidity the easier recover<00:17:05.400> function 00:17:06.949 --> 00:17:06.959 align:start position:0% recover function 00:17:06.959 --> 00:17:09.829 align:start position:0% recover function will<00:17:07.500> return<00:17:07.799> something<00:17:08.280> special<00:17:08.939> if<00:17:09.600> there's 00:17:09.829 --> 00:17:09.839 align:start position:0% will return something special if there's 00:17:09.839 --> 00:17:12.049 align:start position:0% will return something special if there's an<00:17:10.079> error<00:17:10.380> can<00:17:11.040> someone<00:17:11.220> yell<00:17:11.579> out<00:17:11.699> what<00:17:11.880> that 00:17:12.049 --> 00:17:12.059 align:start position:0% an error can someone yell out what that 00:17:12.059 --> 00:17:14.110 align:start position:0% an error can someone yell out what that something<00:17:12.179> special<00:17:12.480> is 00:17:14.110 --> 00:17:14.120 align:start position:0% something special is 00:17:14.120 --> 00:17:16.429 align:start position:0% something special is okay<00:17:15.120> someone<00:17:15.419> someone<00:17:15.720> says<00:17:16.020> zero<00:17:16.260> perfect 00:17:16.429 --> 00:17:16.439 align:start position:0% okay someone someone says zero perfect 00:17:16.439 --> 00:17:18.590 align:start position:0% okay someone someone says zero perfect right<00:17:16.799> so<00:17:17.220> if<00:17:17.520> the<00:17:17.640> signature<00:17:17.939> is<00:17:18.120> invalid 00:17:18.590 --> 00:17:18.600 align:start position:0% right so if the signature is invalid 00:17:18.600 --> 00:17:20.569 align:start position:0% right so if the signature is invalid then<00:17:19.199> easy<00:17:19.439> recover<00:17:19.799> will<00:17:20.040> return<00:17:20.220> a<00:17:20.459> magic 00:17:20.569 --> 00:17:20.579 align:start position:0% then easy recover will return a magic 00:17:20.579 --> 00:17:22.490 align:start position:0% then easy recover will return a magic value<00:17:20.819> of<00:17:21.059> zero<00:17:21.480> you<00:17:21.839> know<00:17:22.079> those<00:17:22.199> address 00:17:22.490 --> 00:17:22.500 align:start position:0% value of zero you know those address 00:17:22.500 --> 00:17:24.530 align:start position:0% value of zero you know those address zero<00:17:23.040> has<00:17:23.220> you<00:17:23.640> know<00:17:23.819> signed<00:17:24.120> over<00:17:24.240> this 00:17:24.530 --> 00:17:24.540 align:start position:0% zero has you know signed over this 00:17:24.540 --> 00:17:27.470 align:start position:0% zero has you know signed over this message<00:17:24.839> hash<00:17:25.260> with<00:17:25.500> a<00:17:25.620> signature<00:17:26.480> obviously 00:17:27.470 --> 00:17:27.480 align:start position:0% message hash with a signature obviously 00:17:27.480 --> 00:17:28.909 align:start position:0% message hash with a signature obviously that's<00:17:27.780> not<00:17:28.079> true<00:17:28.260> because<00:17:28.439> you<00:17:28.679> know<00:17:28.799> if 00:17:28.909 --> 00:17:28.919 align:start position:0% that's not true because you know if 00:17:28.919 --> 00:17:29.990 align:start position:0% that's not true because you know if you're<00:17:29.280> new<00:17:29.400> with<00:17:29.460> it<00:17:29.520> if<00:17:29.640> you<00:17:29.760> knew<00:17:29.940> the 00:17:29.990 --> 00:17:30.000 align:start position:0% you're new with it if you knew the 00:17:30.000 --> 00:17:31.370 align:start position:0% you're new with it if you knew the private<00:17:30.419> keys<00:17:30.660> of<00:17:30.720> the<00:17:30.780> address<00:17:30.900> zero<00:17:31.260> the 00:17:31.370 --> 00:17:31.380 align:start position:0% private keys of the address zero the 00:17:31.380 --> 00:17:33.289 align:start position:0% private keys of the address zero the things<00:17:31.500> would<00:17:31.679> be<00:17:31.799> very<00:17:31.919> bad<00:17:32.160> but<00:17:33.000> the<00:17:33.120> easy 00:17:33.289 --> 00:17:33.299 align:start position:0% things would be very bad but the easy 00:17:33.299 --> 00:17:35.289 align:start position:0% things would be very bad but the easy recover<00:17:33.660> doesn't<00:17:34.200> tell<00:17:34.740> you<00:17:34.860> anything 00:17:35.289 --> 00:17:35.299 align:start position:0% recover doesn't tell you anything 00:17:35.299 --> 00:17:37.370 align:start position:0% recover doesn't tell you anything explicitly<00:17:36.299> right<00:17:36.539> there's<00:17:36.780> this<00:17:37.080> magic 00:17:37.370 --> 00:17:37.380 align:start position:0% explicitly right there's this magic 00:17:37.380 --> 00:17:39.950 align:start position:0% explicitly right there's this magic value<00:17:37.740> and<00:17:38.520> if<00:17:38.700> you<00:17:38.940> don't<00:17:39.179> remember<00:17:39.419> to<00:17:39.720> check 00:17:39.950 --> 00:17:39.960 align:start position:0% value and if you don't remember to check 00:17:39.960 --> 00:17:42.169 align:start position:0% value and if you don't remember to check this<00:17:40.280> then<00:17:41.280> someone<00:17:41.520> can<00:17:41.760> pretend<00:17:42.059> they're 00:17:42.169 --> 00:17:42.179 align:start position:0% this then someone can pretend they're 00:17:42.179 --> 00:17:43.850 align:start position:0% this then someone can pretend they're from<00:17:42.360> address<00:17:42.539> zero<00:17:43.020> right<00:17:43.260> and<00:17:43.440> maybe<00:17:43.620> like 00:17:43.850 --> 00:17:43.860 align:start position:0% from address zero right and maybe like 00:17:43.860 --> 00:17:45.289 align:start position:0% from address zero right and maybe like do<00:17:44.039> a<00:17:44.160> bunch<00:17:44.280> of<00:17:44.340> nasty<00:17:44.640> stuff<00:17:44.760> and<00:17:44.940> in<00:17:45.120> fact 00:17:45.289 --> 00:17:45.299 align:start position:0% do a bunch of nasty stuff and in fact 00:17:45.299 --> 00:17:48.169 align:start position:0% do a bunch of nasty stuff and in fact just<00:17:46.020> a<00:17:46.200> few<00:17:46.380> months<00:17:46.559> ago<00:17:46.799> a<00:17:47.220> contract<00:17:47.580> forgot 00:17:48.169 --> 00:17:48.179 align:start position:0% just a few months ago a contract forgot 00:17:48.179 --> 00:17:50.390 align:start position:0% just a few months ago a contract forgot to<00:17:48.360> do<00:17:48.480> this<00:17:48.600> and<00:17:48.780> I<00:17:48.960> think<00:17:49.020> about<00:17:49.200> exploited 00:17:50.390 --> 00:17:50.400 align:start position:0% to do this and I think about exploited 00:17:50.400 --> 00:17:52.610 align:start position:0% to do this and I think about exploited or<00:17:51.000> maybe<00:17:51.240> it<00:17:51.419> wasn't<00:17:51.539> exploited<00:17:52.140> at<00:17:52.320> least<00:17:52.440> it 00:17:52.610 --> 00:17:52.620 align:start position:0% or maybe it wasn't exploited at least it 00:17:52.620 --> 00:17:55.610 align:start position:0% or maybe it wasn't exploited at least it was<00:17:52.799> still<00:17:52.980> there<00:17:53.280> as<00:17:53.520> a<00:17:53.700> bug<00:17:53.760> in<00:17:54.000> code<00:17:54.600> uh<00:17:55.380> with 00:17:55.610 --> 00:17:55.620 align:start position:0% was still there as a bug in code uh with 00:17:55.620 --> 00:17:59.870 align:start position:0% was still there as a bug in code uh with results<00:17:56.000> uh<00:17:57.000> you<00:17:57.419> can<00:17:57.539> actually<00:17:58.020> wrap<00:17:58.880> the 00:17:59.870 --> 00:17:59.880 align:start position:0% results uh you can actually wrap the 00:17:59.880 --> 00:18:02.690 align:start position:0% results uh you can actually wrap the return<00:18:00.179> of<00:18:00.660> things<00:18:00.960> so<00:18:01.440> easy<00:18:01.620> to<00:18:01.860> recover<00:18:02.100> in 00:18:02.690 --> 00:18:02.700 align:start position:0% return of things so easy to recover in 00:18:02.700 --> 00:18:04.070 align:start position:0% return of things so easy to recover in sway<00:18:03.000> which<00:18:03.360> again<00:18:03.480> the<00:18:03.720> standard<00:18:03.960> Library 00:18:04.070 --> 00:18:04.080 align:start position:0% sway which again the standard Library 00:18:04.080 --> 00:18:06.110 align:start position:0% sway which again the standard Library function<00:18:04.440> does<00:18:04.620> not<00:18:04.740> return<00:18:04.980> a<00:18:05.640> value<00:18:05.820> it 00:18:06.110 --> 00:18:06.120 align:start position:0% function does not return a value it 00:18:06.120 --> 00:18:08.630 align:start position:0% function does not return a value it returns<00:18:06.600> a<00:18:06.720> result<00:18:06.900> over<00:18:07.740> a<00:18:07.980> value<00:18:08.160> and<00:18:08.460> an 00:18:08.630 --> 00:18:08.640 align:start position:0% returns a result over a value and an 00:18:08.640 --> 00:18:12.470 align:start position:0% returns a result over a value and an error<00:18:09.240> right<00:18:09.720> so<00:18:10.200> if<00:18:10.740> the<00:18:11.460> if<00:18:11.940> the<00:18:12.120> signature 00:18:12.470 --> 00:18:12.480 align:start position:0% error right so if the if the signature 00:18:12.480 --> 00:18:15.049 align:start position:0% error right so if the if the signature is<00:18:12.600> invalid<00:18:13.140> is<00:18:13.620> not<00:18:13.860> going<00:18:14.039> to<00:18:14.220> return<00:18:14.400> zero 00:18:15.049 --> 00:18:15.059 align:start position:0% is invalid is not going to return zero 00:18:15.059 --> 00:18:17.510 align:start position:0% is invalid is not going to return zero it's<00:18:15.179> going<00:18:15.360> to<00:18:15.419> return<00:18:15.539> an<00:18:16.020> error<00:18:16.440> and<00:18:17.160> if<00:18:17.400> you 00:18:17.510 --> 00:18:17.520 align:start position:0% it's going to return an error and if you 00:18:17.520 --> 00:18:19.370 align:start position:0% it's going to return an error and if you want<00:18:17.640> to<00:18:17.760> actually<00:18:17.880> get<00:18:18.240> into<00:18:18.480> the<00:18:18.720> value<00:18:18.900> you 00:18:19.370 --> 00:18:19.380 align:start position:0% want to actually get into the value you 00:18:19.380 --> 00:18:22.010 align:start position:0% want to actually get into the value you have<00:18:19.500> to<00:18:19.740> unwrap<00:18:20.400> the<00:18:20.760> result<00:18:20.940> and<00:18:21.780> you<00:18:21.900> have 00:18:22.010 --> 00:18:22.020 align:start position:0% have to unwrap the result and you have 00:18:22.020 --> 00:18:24.850 align:start position:0% have to unwrap the result and you have to<00:18:22.140> do<00:18:22.260> this 00:18:24.850 --> 00:18:24.860 align:start position:0% 00:18:24.860 --> 00:18:27.590 align:start position:0% in<00:18:25.860> other<00:18:25.980> words<00:18:26.160> you<00:18:26.820> have<00:18:26.940> to<00:18:27.120> handle<00:18:27.419> that 00:18:27.590 --> 00:18:27.600 align:start position:0% in other words you have to handle that 00:18:27.600 --> 00:18:29.750 align:start position:0% in other words you have to handle that error<00:18:27.960> and<00:18:28.440> the<00:18:28.559> compiler<00:18:29.039> will<00:18:29.220> force<00:18:29.520> you<00:18:29.640> to 00:18:29.750 --> 00:18:29.760 align:start position:0% error and the compiler will force you to 00:18:29.760 --> 00:18:33.529 align:start position:0% error and the compiler will force you to handle<00:18:30.000> that<00:18:30.120> error<00:18:30.620> explicitly<00:18:31.880> uh<00:18:32.880> you<00:18:33.419> know 00:18:33.529 --> 00:18:33.539 align:start position:0% handle that error explicitly uh you know 00:18:33.539 --> 00:18:35.690 align:start position:0% handle that error explicitly uh you know in<00:18:33.840> solidity<00:18:34.440> that's<00:18:34.679> not<00:18:34.799> the<00:18:34.919> case<00:18:35.039> you<00:18:35.580> have 00:18:35.690 --> 00:18:35.700 align:start position:0% in solidity that's not the case you have 00:18:35.700 --> 00:18:37.430 align:start position:0% in solidity that's not the case you have to<00:18:35.820> actually<00:18:35.940> go<00:18:36.120> manually<00:18:36.480> remember<00:18:36.720> to 00:18:37.430 --> 00:18:37.440 align:start position:0% to actually go manually remember to 00:18:37.440 --> 00:18:39.770 align:start position:0% to actually go manually remember to check<00:18:37.620> the<00:18:37.799> zero<00:18:38.160> value<00:18:38.280> and<00:18:39.240> you<00:18:39.660> know 00:18:39.770 --> 00:18:39.780 align:start position:0% check the zero value and you know 00:18:39.780 --> 00:18:40.669 align:start position:0% check the zero value and you know there's<00:18:39.900> all<00:18:40.080> the<00:18:40.200> places<00:18:40.320> where<00:18:40.500> this 00:18:40.669 --> 00:18:40.679 align:start position:0% there's all the places where this 00:18:40.679 --> 00:18:42.830 align:start position:0% there's all the places where this happened<00:18:40.860> so<00:18:41.280> having<00:18:41.880> generic<00:18:42.419> in<00:18:42.600> some<00:18:42.660> types 00:18:42.830 --> 00:18:42.840 align:start position:0% happened so having generic in some types 00:18:42.840 --> 00:18:44.450 align:start position:0% happened so having generic in some types allows<00:18:43.260> us<00:18:43.380> to<00:18:43.500> have<00:18:43.620> results<00:18:43.740> along<00:18:44.100> with<00:18:44.340> all 00:18:44.450 --> 00:18:44.460 align:start position:0% allows us to have results along with all 00:18:44.460 --> 00:18:46.130 align:start position:0% allows us to have results along with all the<00:18:44.640> things<00:18:44.760> and<00:18:45.179> this<00:18:45.299> allows<00:18:45.600> for<00:18:45.720> explicit 00:18:46.130 --> 00:18:46.140 align:start position:0% the things and this allows for explicit 00:18:46.140 --> 00:18:48.169 align:start position:0% the things and this allows for explicit error<00:18:46.440> handling<00:18:46.740> which<00:18:47.280> means<00:18:47.520> safer<00:18:48.000> code 00:18:48.169 --> 00:18:48.179 align:start position:0% error handling which means safer code 00:18:48.179 --> 00:18:50.210 align:start position:0% error handling which means safer code because<00:18:48.480> the<00:18:48.720> compiler<00:18:49.080> tells<00:18:49.559> you<00:18:49.620> you<00:18:50.100> don't 00:18:50.210 --> 00:18:50.220 align:start position:0% because the compiler tells you you don't 00:18:50.220 --> 00:18:52.490 align:start position:0% because the compiler tells you you don't have<00:18:50.340> to<00:18:50.460> go<00:18:50.520> and<00:18:50.640> remember<00:18:50.760> yourself 00:18:52.490 --> 00:18:52.500 align:start position:0% have to go and remember yourself 00:18:52.500 --> 00:18:55.370 align:start position:0% have to go and remember yourself okay<00:18:52.919> next<00:18:53.280> one<00:18:53.460> type<00:18:54.059> in<00:18:54.299> front 00:18:55.370 --> 00:18:55.380 align:start position:0% okay next one type in front 00:18:55.380 --> 00:18:57.529 align:start position:0% okay next one type in front we<00:18:55.860> probably<00:18:56.220> all<00:18:56.460> hate<00:18:56.700> writing<00:18:57.179> types<00:18:57.480> of 00:18:57.529 --> 00:18:57.539 align:start position:0% we probably all hate writing types of 00:18:57.539 --> 00:18:59.090 align:start position:0% we probably all hate writing types of things<00:18:57.720> especially<00:18:58.320> when<00:18:58.559> those<00:18:58.679> types<00:18:58.980> are 00:18:59.090 --> 00:18:59.100 align:start position:0% things especially when those types are 00:18:59.100 --> 00:19:00.770 align:start position:0% things especially when those types are long<00:18:59.340> especially<00:18:59.940> relevant<00:19:00.299> when<00:19:00.539> you<00:19:00.660> have 00:19:00.770 --> 00:19:00.780 align:start position:0% long especially relevant when you have 00:19:00.780 --> 00:19:03.049 align:start position:0% long especially relevant when you have generics<00:19:01.440> uh 00:19:03.049 --> 00:19:03.059 align:start position:0% generics uh 00:19:03.059 --> 00:19:04.789 align:start position:0% generics uh there's<00:19:03.480> a<00:19:03.600> left<00:19:03.720> keyword 00:19:04.789 --> 00:19:04.799 align:start position:0% there's a left keyword 00:19:04.799 --> 00:19:06.770 align:start position:0% there's a left keyword now<00:19:05.340> an<00:19:05.700> alternative<00:19:06.059> would<00:19:06.299> have<00:19:06.419> been<00:19:06.480> a<00:19:06.660> VAR 00:19:06.770 --> 00:19:06.780 align:start position:0% now an alternative would have been a VAR 00:19:06.780 --> 00:19:08.510 align:start position:0% now an alternative would have been a VAR I<00:19:07.020> guess<00:19:07.200> but<00:19:07.740> you<00:19:07.919> know<00:19:08.039> there's<00:19:08.220> been<00:19:08.340> some 00:19:08.510 --> 00:19:08.520 align:start position:0% I guess but you know there's been some 00:19:08.520 --> 00:19:10.130 align:start position:0% I guess but you know there's been some bike<00:19:08.640> shedding<00:19:09.000> I<00:19:09.179> think<00:19:09.299> on<00:19:09.480> Twitter<00:19:09.660> I<00:19:09.840> saw<00:19:09.960> a 00:19:10.130 --> 00:19:10.140 align:start position:0% bike shedding I think on Twitter I saw a 00:19:10.140 --> 00:19:12.529 align:start position:0% bike shedding I think on Twitter I saw a fairly<00:19:10.500> recently<00:19:10.919> on<00:19:11.460> the<00:19:11.640> slack<00:19:11.880> keyword<00:19:12.179> so 00:19:12.529 --> 00:19:12.539 align:start position:0% fairly recently on the slack keyword so 00:19:12.539 --> 00:19:14.990 align:start position:0% fairly recently on the slack keyword so this<00:19:12.960> one<00:19:13.140> has<00:19:13.260> a<00:19:13.380> left<00:19:13.500> keyword<00:19:13.880> and<00:19:14.880> this 00:19:14.990 --> 00:19:15.000 align:start position:0% this one has a left keyword and this 00:19:15.000 --> 00:19:17.690 align:start position:0% this one has a left keyword and this allows<00:19:15.419> you<00:19:15.539> to<00:19:15.720> have<00:19:15.960> type<00:19:16.260> in<00:19:16.559> fronts<00:19:16.980> right 00:19:17.690 --> 00:19:17.700 align:start position:0% allows you to have type in fronts right 00:19:17.700 --> 00:19:20.150 align:start position:0% allows you to have type in fronts right we<00:19:17.940> use<00:19:18.120> the<00:19:18.240> same<00:19:18.360> type<00:19:18.600> system<00:19:18.900> as<00:19:19.140> rust<00:19:19.440> so 00:19:20.150 --> 00:19:20.160 align:start position:0% we use the same type system as rust so 00:19:20.160 --> 00:19:21.470 align:start position:0% we use the same type system as rust so you<00:19:20.340> can<00:19:20.460> just<00:19:20.580> you<00:19:20.820> know<00:19:20.940> whatever's<00:19:21.299> on<00:19:21.360> the 00:19:21.470 --> 00:19:21.480 align:start position:0% you can just you know whatever's on the 00:19:21.480 --> 00:19:23.810 align:start position:0% you can just you know whatever's on the right<00:19:21.539> it<00:19:21.720> can<00:19:21.900> be<00:19:21.960> inferred<00:19:22.620> uh<00:19:23.340> you<00:19:23.580> have<00:19:23.700> to 00:19:23.810 --> 00:19:23.820 align:start position:0% right it can be inferred uh you have to 00:19:23.820 --> 00:19:26.029 align:start position:0% right it can be inferred uh you have to actually<00:19:24.059> write<00:19:24.419> out<00:19:24.660> very<00:19:25.080> few<00:19:25.440> types<00:19:25.740> and<00:19:25.860> if 00:19:26.029 --> 00:19:26.039 align:start position:0% actually write out very few types and if 00:19:26.039 --> 00:19:27.590 align:start position:0% actually write out very few types and if you<00:19:26.100> look<00:19:26.220> at<00:19:26.340> our<00:19:26.460> standard<00:19:26.760> Library<00:19:27.000> I<00:19:27.480> think 00:19:27.590 --> 00:19:27.600 align:start position:0% you look at our standard Library I think 00:19:27.600 --> 00:19:28.970 align:start position:0% you look at our standard Library I think sniper<00:19:28.020> inference<00:19:28.320> is<00:19:28.500> used<00:19:28.620> quite<00:19:28.860> a<00:19:28.980> bit 00:19:28.970 --> 00:19:28.980 align:start position:0% sniper inference is used quite a bit 00:19:28.980 --> 00:19:30.710 align:start position:0% sniper inference is used quite a bit throughout<00:19:29.340> it<00:19:29.520> so<00:19:29.760> that<00:19:30.360> would<00:19:30.480> be<00:19:30.539> a<00:19:30.600> good 00:19:30.710 --> 00:19:30.720 align:start position:0% throughout it so that would be a good 00:19:30.720 --> 00:19:33.590 align:start position:0% throughout it so that would be a good example<00:19:31.020> of<00:19:31.200> how<00:19:31.799> how<00:19:32.700> you<00:19:33.179> don't<00:19:33.299> have<00:19:33.419> to 00:19:33.590 --> 00:19:33.600 align:start position:0% example of how how you don't have to 00:19:33.600 --> 00:19:37.490 align:start position:0% example of how how you don't have to write<00:19:33.720> that<00:19:33.900> many<00:19:34.020> types<00:19:34.380> everywhere 00:19:37.490 --> 00:19:37.500 align:start position:0% 00:19:37.500 --> 00:19:39.650 align:start position:0% and<00:19:38.220> onto 00:19:39.650 --> 00:19:39.660 align:start position:0% and onto 00:19:39.660 --> 00:19:42.529 align:start position:0% and onto okay<00:19:40.200> next<00:19:40.919> one<00:19:41.100> is<00:19:41.460> namespace<00:19:42.179> storage 00:19:42.529 --> 00:19:42.539 align:start position:0% okay next one is namespace storage 00:19:42.539 --> 00:19:46.070 align:start position:0% okay next one is namespace storage access<00:19:42.840> in<00:19:43.620> solidity<00:19:44.240> uh<00:19:45.240> storage<00:19:45.539> variables 00:19:46.070 --> 00:19:46.080 align:start position:0% access in solidity uh storage variables 00:19:46.080 --> 00:19:47.810 align:start position:0% access in solidity uh storage variables and<00:19:46.260> regular<00:19:46.559> variables<00:19:47.039> are<00:19:47.340> all<00:19:47.520> in<00:19:47.700> the 00:19:47.810 --> 00:19:47.820 align:start position:0% and regular variables are all in the 00:19:47.820 --> 00:19:50.029 align:start position:0% and regular variables are all in the same<00:19:48.000> namespace<00:19:48.660> and<00:19:49.260> if<00:19:49.440> you<00:19:49.740> have<00:19:49.799> a<00:19:49.919> storage 00:19:50.029 --> 00:19:50.039 align:start position:0% same namespace and if you have a storage 00:19:50.039 --> 00:19:52.130 align:start position:0% same namespace and if you have a storage variable<00:19:50.400> Foo<00:19:50.820> and<00:19:51.000> the<00:19:51.120> local<00:19:51.299> variable<00:19:51.660> Foo 00:19:52.130 --> 00:19:52.140 align:start position:0% variable Foo and the local variable Foo 00:19:52.140 --> 00:19:54.049 align:start position:0% variable Foo and the local variable Foo and<00:19:52.500> you<00:19:52.679> go<00:19:52.799> like<00:19:53.039> you<00:19:53.220> know<00:19:53.280> Foo<00:19:53.760> dot 00:19:54.049 --> 00:19:54.059 align:start position:0% and you go like you know Foo dot 00:19:54.059 --> 00:19:55.850 align:start position:0% and you go like you know Foo dot whatever<00:19:54.260> you<00:19:55.260> know<00:19:55.320> which<00:19:55.440> one<00:19:55.620> are<00:19:55.740> you 00:19:55.850 --> 00:19:55.860 align:start position:0% whatever you know which one are you 00:19:55.860 --> 00:19:57.830 align:start position:0% whatever you know which one are you accessing<00:19:56.340> right<00:19:56.700> likewise<00:19:57.240> what<00:19:57.480> happens<00:19:57.600> if 00:19:57.830 --> 00:19:57.840 align:start position:0% accessing right likewise what happens if 00:19:57.840 --> 00:20:00.590 align:start position:0% accessing right likewise what happens if you<00:19:58.020> have<00:19:58.200> two<00:19:59.039> variables<00:19:59.520> that<00:19:59.760> are<00:19:59.940> close<00:20:00.240> in 00:20:00.590 --> 00:20:00.600 align:start position:0% you have two variables that are close in 00:20:00.600 --> 00:20:02.750 align:start position:0% you have two variables that are close in name<00:20:00.840> right<00:20:01.200> you<00:20:01.440> have<00:20:01.559> like<00:20:01.740> you<00:20:01.919> know<00:20:02.100> count 00:20:02.750 --> 00:20:02.760 align:start position:0% name right you have like you know count 00:20:02.760 --> 00:20:05.870 align:start position:0% name right you have like you know count and<00:20:03.059> CMT<00:20:03.539> let's<00:20:03.900> say<00:20:04.140> right<00:20:04.500> you<00:20:05.400> can<00:20:05.520> use<00:20:05.640> the 00:20:05.870 --> 00:20:05.880 align:start position:0% and CMT let's say right you can use the 00:20:05.880 --> 00:20:07.490 align:start position:0% and CMT let's say right you can use the wrong<00:20:06.000> one<00:20:06.179> by<00:20:06.360> accident<00:20:06.539> right<00:20:06.900> you<00:20:07.080> intended 00:20:07.490 --> 00:20:07.500 align:start position:0% wrong one by accident right you intended 00:20:07.500 --> 00:20:09.350 align:start position:0% wrong one by accident right you intended to<00:20:07.860> increment<00:20:08.220> something<00:20:08.520> in<00:20:08.760> storage<00:20:09.000> but 00:20:09.350 --> 00:20:09.360 align:start position:0% to increment something in storage but 00:20:09.360 --> 00:20:10.850 align:start position:0% to increment something in storage but you<00:20:09.480> incremented<00:20:09.900> it<00:20:10.020> only<00:20:10.140> locally<00:20:10.500> or<00:20:10.679> vice 00:20:10.850 --> 00:20:10.860 align:start position:0% you incremented it only locally or vice 00:20:10.860 --> 00:20:14.270 align:start position:0% you incremented it only locally or vice versa<00:20:11.700> and<00:20:12.480> sway<00:20:12.840> storage<00:20:13.380> accesses<00:20:14.100> are 00:20:14.270 --> 00:20:14.280 align:start position:0% versa and sway storage accesses are 00:20:14.280 --> 00:20:16.330 align:start position:0% versa and sway storage accesses are namespaced<00:20:14.820> with<00:20:15.000> a<00:20:15.120> storage<00:20:15.240> dot<00:20:15.720> keyword 00:20:16.330 --> 00:20:16.340 align:start position:0% namespaced with a storage dot keyword 00:20:16.340 --> 00:20:18.650 align:start position:0% namespaced with a storage dot keyword which<00:20:17.340> means<00:20:17.580> if<00:20:17.760> you<00:20:17.880> want<00:20:18.120> to<00:20:18.240> access<00:20:18.419> a 00:20:18.650 --> 00:20:18.660 align:start position:0% which means if you want to access a 00:20:18.660 --> 00:20:19.850 align:start position:0% which means if you want to access a storage<00:20:18.840> variable<00:20:19.200> you<00:20:19.380> specifically<00:20:19.679> have 00:20:19.850 --> 00:20:19.860 align:start position:0% storage variable you specifically have 00:20:19.860 --> 00:20:21.409 align:start position:0% storage variable you specifically have to<00:20:19.980> write<00:20:20.100> out<00:20:20.220> storage<00:20:20.400> dot<00:20:20.820> this<00:20:21.120> means<00:20:21.360> you 00:20:21.409 --> 00:20:21.419 align:start position:0% to write out storage dot this means you 00:20:21.419 --> 00:20:22.730 align:start position:0% to write out storage dot this means you can<00:20:21.539> just<00:20:21.660> look<00:20:21.780> at<00:20:21.900> the<00:20:22.080> code 00:20:22.730 --> 00:20:22.740 align:start position:0% can just look at the code 00:20:22.740 --> 00:20:25.549 align:start position:0% can just look at the code typos<00:20:23.340> are<00:20:23.520> not<00:20:23.700> and<00:20:24.059> you<00:20:24.299> can<00:20:24.419> see<00:20:24.600> what<00:20:25.380> parts 00:20:25.549 --> 00:20:25.559 align:start position:0% typos are not and you can see what parts 00:20:25.559 --> 00:20:26.630 align:start position:0% typos are not and you can see what parts of<00:20:25.740> the<00:20:25.860> code<00:20:25.980> are<00:20:26.160> actually<00:20:26.280> touching 00:20:26.630 --> 00:20:26.640 align:start position:0% of the code are actually touching 00:20:26.640 --> 00:20:28.610 align:start position:0% of the code are actually touching storage<00:20:26.880> versus<00:20:27.480> not 00:20:28.610 --> 00:20:28.620 align:start position:0% storage versus not 00:20:28.620 --> 00:20:30.409 align:start position:0% storage versus not right<00:20:28.980> so<00:20:29.160> additional<00:20:29.520> explosiveness<00:20:30.120> and<00:20:30.299> it 00:20:30.409 --> 00:20:30.419 align:start position:0% right so additional explosiveness and it 00:20:30.419 --> 00:20:33.529 align:start position:0% right so additional explosiveness and it means<00:20:30.660> additional<00:20:30.960> safety 00:20:33.529 --> 00:20:33.539 align:start position:0% 00:20:33.539 --> 00:20:35.570 align:start position:0% next<00:20:34.020> one<00:20:34.140> is<00:20:34.380> exhaustive<00:20:34.980> pattern<00:20:35.220> matching 00:20:35.570 --> 00:20:35.580 align:start position:0% next one is exhaustive pattern matching 00:20:35.580 --> 00:20:38.510 align:start position:0% next one is exhaustive pattern matching this<00:20:36.360> one<00:20:36.539> was<00:20:36.840> implemented<00:20:37.500> quite<00:20:38.280> quickly 00:20:38.510 --> 00:20:38.520 align:start position:0% this one was implemented quite quickly 00:20:38.520 --> 00:20:40.250 align:start position:0% this one was implemented quite quickly by<00:20:38.880> one<00:20:39.059> information<00:20:39.299> compiler<00:20:39.960> Engineers 00:20:40.250 --> 00:20:40.260 align:start position:0% by one information compiler Engineers 00:20:40.260 --> 00:20:43.370 align:start position:0% by one information compiler Engineers Emily<00:20:40.820> uh<00:20:41.820> for<00:20:42.240> those<00:20:42.900> of<00:20:43.080> you<00:20:43.140> who<00:20:43.260> aren't 00:20:43.370 --> 00:20:43.380 align:start position:0% Emily uh for those of you who aren't 00:20:43.380 --> 00:20:44.750 align:start position:0% Emily uh for those of you who aren't familiar<00:20:43.740> with<00:20:43.860> pattern<00:20:44.160> matching<00:20:44.400> it's<00:20:44.580> a 00:20:44.750 --> 00:20:44.760 align:start position:0% familiar with pattern matching it's a 00:20:44.760 --> 00:20:46.970 align:start position:0% familiar with pattern matching it's a match<00:20:44.940> statement<00:20:45.360> right<00:20:46.080> and<00:20:46.440> it<00:20:46.500> allows<00:20:46.860> you 00:20:46.970 --> 00:20:46.980 align:start position:0% match statement right and it allows you 00:20:46.980 --> 00:20:49.370 align:start position:0% match statement right and it allows you to<00:20:47.100> exhaustively<00:20:47.940> enumerate<00:20:48.600> all<00:20:49.200> the 00:20:49.370 --> 00:20:49.380 align:start position:0% to exhaustively enumerate all the 00:20:49.380 --> 00:20:51.409 align:start position:0% to exhaustively enumerate all the possible<00:20:49.679> cases<00:20:50.160> so<00:20:50.940> let's<00:20:51.120> say<00:20:51.240> you're 00:20:51.409 --> 00:20:51.419 align:start position:0% possible cases so let's say you're 00:20:51.419 --> 00:20:53.270 align:start position:0% possible cases so let's say you're matching<00:20:51.840> in<00:20:52.020> a<00:20:52.140> Boolean<00:20:52.440> the<00:20:52.799> exhaustive 00:20:53.270 --> 00:20:53.280 align:start position:0% matching in a Boolean the exhaustive 00:20:53.280 --> 00:20:55.549 align:start position:0% matching in a Boolean the exhaustive cases<00:20:53.520> are<00:20:53.700> true<00:20:53.880> and<00:20:54.059> false<00:20:54.600> right<00:20:55.080> and<00:20:55.380> if 00:20:55.549 --> 00:20:55.559 align:start position:0% cases are true and false right and if 00:20:55.559 --> 00:20:57.529 align:start position:0% cases are true and false right and if you<00:20:55.799> only<00:20:55.919> matched<00:20:56.400> on<00:20:56.460> true<00:20:56.700> the<00:20:57.059> compiler 00:20:57.529 --> 00:20:57.539 align:start position:0% you only matched on true the compiler 00:20:57.539 --> 00:20:59.930 align:start position:0% you only matched on true the compiler would<00:20:57.660> tell<00:20:57.780> you<00:20:57.900> hey<00:20:58.220> you<00:20:59.220> haven't<00:20:59.460> matched 00:20:59.930 --> 00:20:59.940 align:start position:0% would tell you hey you haven't matched 00:20:59.940 --> 00:21:02.690 align:start position:0% would tell you hey you haven't matched exhaustively<00:21:01.080> uh<00:21:01.559> this<00:21:01.799> means<00:21:02.039> that<00:21:02.280> unlike 00:21:02.690 --> 00:21:02.700 align:start position:0% exhaustively uh this means that unlike 00:21:02.700 --> 00:21:04.010 align:start position:0% exhaustively uh this means that unlike in<00:21:02.880> solidity<00:21:03.240> where<00:21:03.419> you<00:21:03.539> have<00:21:03.600> to<00:21:03.720> do<00:21:03.780> an<00:21:03.900> if 00:21:04.010 --> 00:21:04.020 align:start position:0% in solidity where you have to do an if 00:21:04.020 --> 00:21:05.930 align:start position:0% in solidity where you have to do an if else<00:21:04.260> chain<00:21:04.559> and<00:21:04.799> hey<00:21:04.980> if<00:21:05.160> you<00:21:05.340> forget<00:21:05.580> to 00:21:05.930 --> 00:21:05.940 align:start position:0% else chain and hey if you forget to 00:21:05.940 --> 00:21:08.090 align:start position:0% else chain and hey if you forget to check<00:21:06.120> a<00:21:06.360> case<00:21:06.539> and<00:21:06.840> you're<00:21:07.020> in<00:21:07.679> the<00:21:07.860> in<00:21:07.980> your 00:21:08.090 --> 00:21:08.100 align:start position:0% check a case and you're in the in your 00:21:08.100 --> 00:21:10.310 align:start position:0% check a case and you're in the in your state<00:21:08.280> machine<00:21:08.520> right<00:21:08.880> uh<00:21:09.720> for<00:21:09.900> your<00:21:10.020> contract 00:21:10.310 --> 00:21:10.320 align:start position:0% state machine right uh for your contract 00:21:10.320 --> 00:21:11.690 align:start position:0% state machine right uh for your contract if<00:21:10.440> you<00:21:10.559> forget<00:21:10.679> to<00:21:10.860> check<00:21:11.039> your<00:21:11.160> case<00:21:11.340> well 00:21:11.690 --> 00:21:11.700 align:start position:0% if you forget to check your case well 00:21:11.700 --> 00:21:13.010 align:start position:0% if you forget to check your case well too<00:21:11.820> bad<00:21:11.940> so<00:21:12.120> sad<00:21:12.299> the<00:21:12.419> compiler<00:21:12.780> tells<00:21:12.960> you 00:21:13.010 --> 00:21:13.020 align:start position:0% too bad so sad the compiler tells you 00:21:13.020 --> 00:21:15.590 align:start position:0% too bad so sad the compiler tells you nothing<00:21:13.200> right<00:21:13.700> uh<00:21:14.700> with<00:21:14.940> exhaustive<00:21:15.419> magic 00:21:15.590 --> 00:21:15.600 align:start position:0% nothing right uh with exhaustive magic 00:21:15.600 --> 00:21:17.029 align:start position:0% nothing right uh with exhaustive magic Expressions<00:21:16.020> well<00:21:16.140> not<00:21:16.320> only<00:21:16.440> is<00:21:16.559> it<00:21:16.799> cleaner 00:21:17.029 --> 00:21:17.039 align:start position:0% Expressions well not only is it cleaner 00:21:17.039 --> 00:21:18.409 align:start position:0% Expressions well not only is it cleaner because<00:21:17.220> it's<00:21:17.520> all<00:21:17.700> like<00:21:17.820> in<00:21:17.940> a<00:21:18.059> single<00:21:18.299> thing 00:21:18.409 --> 00:21:18.419 align:start position:0% because it's all like in a single thing 00:21:18.419 --> 00:21:20.450 align:start position:0% because it's all like in a single thing instead<00:21:18.780> of<00:21:18.840> a<00:21:19.020> chain<00:21:19.140> and<00:21:19.980> it's<00:21:20.280> also 00:21:20.450 --> 00:21:20.460 align:start position:0% instead of a chain and it's also 00:21:20.460 --> 00:21:21.890 align:start position:0% instead of a chain and it's also exhaustive<00:21:20.820> and<00:21:21.000> the<00:21:21.179> compiler<00:21:21.600> will<00:21:21.780> tell 00:21:21.890 --> 00:21:21.900 align:start position:0% exhaustive and the compiler will tell 00:21:21.900 --> 00:21:25.430 align:start position:0% exhaustive and the compiler will tell you<00:21:22.020> if<00:21:22.260> you<00:21:22.380> missed<00:21:22.620> a<00:21:22.740> case 00:21:25.430 --> 00:21:25.440 align:start position:0% 00:21:25.440 --> 00:21:28.549 align:start position:0% next<00:21:25.980> one<00:21:26.160> is<00:21:26.460> zero<00:21:26.880> cost<00:21:27.000> obstructions<00:21:27.720> uh 00:21:28.549 --> 00:21:28.559 align:start position:0% next one is zero cost obstructions uh 00:21:28.559 --> 00:21:30.649 align:start position:0% next one is zero cost obstructions uh this<00:21:28.799> is<00:21:28.919> kind<00:21:29.220> of<00:21:29.340> a<00:21:29.520> first<00:21:29.700> class<00:21:29.940> notion<00:21:30.480> in 00:21:30.649 --> 00:21:30.659 align:start position:0% this is kind of a first class notion in 00:21:30.659 --> 00:21:31.970 align:start position:0% this is kind of a first class notion in this<00:21:30.840> way<00:21:30.960> language<00:21:31.140> and<00:21:31.440> this<00:21:31.500> way<00:21:31.679> combin 00:21:31.970 --> 00:21:31.980 align:start position:0% this way language and this way combin 00:21:31.980 --> 00:21:32.830 align:start position:0% this way language and this way combin binder 00:21:32.830 --> 00:21:32.840 align:start position:0% binder 00:21:32.840 --> 00:21:35.450 align:start position:0% binder uh<00:21:33.840> that<00:21:34.260> this<00:21:34.440> little<00:21:34.620> pilot<00:21:35.159> doesn't<00:21:35.340> really 00:21:35.450 --> 00:21:35.460 align:start position:0% uh that this little pilot doesn't really 00:21:35.460 --> 00:21:37.669 align:start position:0% uh that this little pilot doesn't really do<00:21:35.700> one<00:21:36.299> example<00:21:36.600> of<00:21:36.840> a<00:21:36.960> zero<00:21:37.140> cost<00:21:37.260> attraction 00:21:37.669 --> 00:21:37.679 align:start position:0% do one example of a zero cost attraction 00:21:37.679 --> 00:21:40.010 align:start position:0% do one example of a zero cost attraction there's<00:21:38.039> zero<00:21:38.520> cost<00:21:38.640> things<00:21:38.940> in<00:21:39.240> general<00:21:39.419> it 00:21:40.010 --> 00:21:40.020 align:start position:0% there's zero cost things in general it 00:21:40.020 --> 00:21:41.990 align:start position:0% there's zero cost things in general it means<00:21:40.260> moving<00:21:40.740> stuff<00:21:40.980> from<00:21:41.340> runtime<00:21:41.760> to 00:21:41.990 --> 00:21:42.000 align:start position:0% means moving stuff from runtime to 00:21:42.000 --> 00:21:43.490 align:start position:0% means moving stuff from runtime to compile<00:21:42.360> time<00:21:42.539> wherever<00:21:42.900> possible<00:21:43.260> that's 00:21:43.490 --> 00:21:43.500 align:start position:0% compile time wherever possible that's 00:21:43.500 --> 00:21:45.770 align:start position:0% compile time wherever possible that's what<00:21:43.740> the<00:21:43.980> ethos<00:21:44.340> is<00:21:44.580> really<00:21:44.700> about<00:21:44.880> one 00:21:45.770 --> 00:21:45.780 align:start position:0% what the ethos is really about one 00:21:45.780 --> 00:21:47.750 align:start position:0% what the ethos is really about one example<00:21:46.140> is<00:21:46.380> well<00:21:46.919> what<00:21:47.159> happens<00:21:47.280> if<00:21:47.580> you 00:21:47.750 --> 00:21:47.760 align:start position:0% example is well what happens if you 00:21:47.760 --> 00:21:51.169 align:start position:0% example is well what happens if you could<00:21:48.000> check<00:21:48.720> method<00:21:49.320> payability<00:21:49.860> at<00:21:50.820> compile 00:21:51.169 --> 00:21:51.179 align:start position:0% could check method payability at compile 00:21:51.179 --> 00:21:53.330 align:start position:0% could check method payability at compile time<00:21:51.419> instead<00:21:51.780> of<00:21:51.900> at<00:21:52.020> runtime<00:21:52.380> right<00:21:52.860> it's<00:21:53.220> a 00:21:53.330 --> 00:21:53.340 align:start position:0% time instead of at runtime right it's a 00:21:53.340 --> 00:21:54.950 align:start position:0% time instead of at runtime right it's a solidity<00:21:53.640> compiler<00:21:54.120> will<00:21:54.240> actually<00:21:54.419> inject 00:21:54.950 --> 00:21:54.960 align:start position:0% solidity compiler will actually inject 00:21:54.960 --> 00:21:58.310 align:start position:0% solidity compiler will actually inject some<00:21:55.860> runtime<00:21:56.340> code<00:21:56.640> into<00:21:56.940> every<00:21:57.240> method<00:21:57.720> that 00:21:58.310 --> 00:21:58.320 align:start position:0% some runtime code into every method that 00:21:58.320 --> 00:22:01.190 align:start position:0% some runtime code into every method that is<00:21:58.559> non-payable<00:21:59.340> right<00:22:00.179> this<00:22:00.720> is<00:22:00.900> a<00:22:00.960> runtime 00:22:01.190 --> 00:22:01.200 align:start position:0% is non-payable right this is a runtime 00:22:01.200 --> 00:22:03.230 align:start position:0% is non-payable right this is a runtime cost<00:22:01.440> it's<00:22:01.679> bad<00:22:01.919> and<00:22:02.159> that's<00:22:02.340> why<00:22:02.580> optimizers 00:22:03.230 --> 00:22:03.240 align:start position:0% cost it's bad and that's why optimizers 00:22:03.240 --> 00:22:04.909 align:start position:0% cost it's bad and that's why optimizers will<00:22:03.480> actually<00:22:03.659> just<00:22:03.960> add<00:22:04.140> payable<00:22:04.559> to<00:22:04.799> every 00:22:04.909 --> 00:22:04.919 align:start position:0% will actually just add payable to every 00:22:04.919 --> 00:22:07.490 align:start position:0% will actually just add payable to every public<00:22:05.400> method<00:22:05.820> uh<00:22:06.600> to<00:22:06.780> avoid<00:22:07.020> that<00:22:07.140> runtime 00:22:07.490 --> 00:22:07.500 align:start position:0% public method uh to avoid that runtime 00:22:07.500 --> 00:22:09.710 align:start position:0% public method uh to avoid that runtime cost<00:22:07.740> and<00:22:07.980> just<00:22:08.159> say<00:22:08.280> Okay<00:22:08.460> read<00:22:09.120> the<00:22:09.360> read<00:22:09.600> the 00:22:09.710 --> 00:22:09.720 align:start position:0% cost and just say Okay read the read the 00:22:09.720 --> 00:22:11.570 align:start position:0% cost and just say Okay read the read the documentation<00:22:10.260> right<00:22:10.679> read<00:22:10.919> the<00:22:11.100> docs<00:22:11.340> in<00:22:11.460> the 00:22:11.570 --> 00:22:11.580 align:start position:0% documentation right read the docs in the 00:22:11.580 --> 00:22:13.669 align:start position:0% documentation right read the docs in the function<00:22:11.700> and<00:22:12.120> then<00:22:12.179> don't<00:22:12.539> send<00:22:12.780> either<00:22:13.080> to 00:22:13.669 --> 00:22:13.679 align:start position:0% function and then don't send either to 00:22:13.679 --> 00:22:15.409 align:start position:0% function and then don't send either to this<00:22:13.860> to<00:22:14.039> this<00:22:14.280> method<00:22:14.520> right 00:22:15.409 --> 00:22:15.419 align:start position:0% this to this method right 00:22:15.419 --> 00:22:16.909 align:start position:0% this to this method right but<00:22:15.840> you<00:22:16.080> can<00:22:16.140> always<00:22:16.260> do<00:22:16.440> it<00:22:16.559> at<00:22:16.620> a<00:22:16.740> compile 00:22:16.909 --> 00:22:16.919 align:start position:0% but you can always do it at a compile 00:22:16.919 --> 00:22:18.710 align:start position:0% but you can always do it at a compile time<00:22:17.159> which<00:22:17.400> is<00:22:17.520> what<00:22:17.700> uh<00:22:18.059> display<00:22:18.240> will<00:22:18.600> do 00:22:18.710 --> 00:22:18.720 align:start position:0% time which is what uh display will do 00:22:18.720 --> 00:22:20.210 align:start position:0% time which is what uh display will do right<00:22:18.960> this<00:22:19.200> way<00:22:19.320> from<00:22:19.559> highlight<00:22:19.799> is<00:22:20.039> that 00:22:20.210 --> 00:22:20.220 align:start position:0% right this way from highlight is that 00:22:20.220 --> 00:22:22.190 align:start position:0% right this way from highlight is that you<00:22:20.700> actually<00:22:20.820> check<00:22:21.240> at<00:22:21.480> compile<00:22:21.840> time<00:22:21.960> but 00:22:22.190 --> 00:22:22.200 align:start position:0% you actually check at compile time but 00:22:22.200 --> 00:22:23.930 align:start position:0% you actually check at compile time but someone<00:22:22.320> trying<00:22:22.679> to<00:22:22.860> send<00:22:23.039> some<00:22:23.340> non-zero 00:22:23.930 --> 00:22:23.940 align:start position:0% someone trying to send some non-zero 00:22:23.940 --> 00:22:27.110 align:start position:0% someone trying to send some non-zero value<00:22:24.059> of<00:22:24.299> any<00:22:24.480> asset<00:22:24.840> not<00:22:25.140> just<00:22:25.320> ether<00:22:25.760> uh<00:22:26.760> to 00:22:27.110 --> 00:22:27.120 align:start position:0% value of any asset not just ether uh to 00:22:27.120 --> 00:22:30.250 align:start position:0% value of any asset not just ether uh to some<00:22:27.600> non-payable<00:22:28.380> method 00:22:30.250 --> 00:22:30.260 align:start position:0% some non-payable method 00:22:30.260 --> 00:22:34.789 align:start position:0% some non-payable method okay<00:22:31.260> uh<00:22:32.159> and<00:22:32.820> another<00:22:33.720> that's<00:22:34.140> not<00:22:34.380> least<00:22:34.559> I 00:22:34.789 --> 00:22:34.799 align:start position:0% okay uh and another that's not least I 00:22:34.799 --> 00:22:35.870 align:start position:0% okay uh and another that's not least I think<00:22:34.860> I'll<00:22:35.039> Zoom<00:22:35.220> through<00:22:35.340> since<00:22:35.520> I<00:22:35.700> have<00:22:35.820> one 00:22:35.870 --> 00:22:35.880 align:start position:0% think I'll Zoom through since I have one 00:22:35.880 --> 00:22:38.029 align:start position:0% think I'll Zoom through since I have one minute<00:22:36.000> left<00:22:36.240> is<00:22:36.480> reagency<00:22:37.039> reentions 00:22:38.029 --> 00:22:38.039 align:start position:0% minute left is reagency reentions 00:22:38.039 --> 00:22:40.250 align:start position:0% minute left is reagency reentions exploits<00:22:38.820> are<00:22:38.880> still<00:22:39.059> happening<00:22:39.419> to<00:22:39.780> this<00:22:40.020> day 00:22:40.250 --> 00:22:40.260 align:start position:0% exploits are still happening to this day 00:22:40.260 --> 00:22:43.010 align:start position:0% exploits are still happening to this day six<00:22:40.919> plus<00:22:41.100> years<00:22:41.340> later<00:22:41.520> after<00:22:41.760> the<00:22:42.000> dial 00:22:43.010 --> 00:22:43.020 align:start position:0% six plus years later after the dial 00:22:43.020 --> 00:22:45.409 align:start position:0% six plus years later after the dial tooling<00:22:43.980> should<00:22:44.460> pick<00:22:44.820> this<00:22:44.940> up<00:22:45.120> but<00:22:45.299> it 00:22:45.409 --> 00:22:45.419 align:start position:0% tooling should pick this up but it 00:22:45.419 --> 00:22:47.149 align:start position:0% tooling should pick this up but it doesn't<00:22:45.600> that's<00:22:45.960> why<00:22:46.140> compiler<00:22:46.679> will<00:22:46.799> warn 00:22:47.149 --> 00:22:47.159 align:start position:0% doesn't that's why compiler will warn 00:22:47.159 --> 00:22:50.390 align:start position:0% doesn't that's why compiler will warn you<00:22:47.280> if<00:22:48.000> your<00:22:48.240> contract<00:22:48.600> has<00:22:49.260> some<00:22:50.039> potential 00:22:50.390 --> 00:22:50.400 align:start position:0% you if your contract has some potential 00:22:50.400 --> 00:22:52.310 align:start position:0% you if your contract has some potential reaction<00:22:50.760> to<00:22:50.940> Golden<00:22:51.120> vulnerability<00:22:52.020> because 00:22:52.310 --> 00:22:52.320 align:start position:0% reaction to Golden vulnerability because 00:22:52.320 --> 00:22:53.570 align:start position:0% reaction to Golden vulnerability because it<00:22:52.559> violates<00:22:52.919> the<00:22:53.100> check<00:22:53.220> effects 00:22:53.570 --> 00:22:53.580 align:start position:0% it violates the check effects 00:22:53.580 --> 00:22:55.250 align:start position:0% it violates the check effects interaction<00:22:53.940> pattern<00:22:54.360> or<00:22:54.539> other<00:22:54.780> patterns 00:22:55.250 --> 00:22:55.260 align:start position:0% interaction pattern or other patterns 00:22:55.260 --> 00:22:57.649 align:start position:0% interaction pattern or other patterns this<00:22:55.980> way<00:22:56.159> to<00:22:56.280> Milo<00:22:56.580> will<00:22:56.700> actually<00:22:56.760> warn<00:22:57.120> you 00:22:57.649 --> 00:22:57.659 align:start position:0% this way to Milo will actually warn you 00:22:57.659 --> 00:23:00.110 align:start position:0% this way to Milo will actually warn you so<00:22:58.140> goodbye<00:22:58.500> other<00:22:58.740> days<00:22:58.980> of<00:22:59.340> re-entracy 00:23:00.110 --> 00:23:00.120 align:start position:0% so goodbye other days of re-entracy 00:23:00.120 --> 00:23:02.149 align:start position:0% so goodbye other days of re-entracy vulnerabilities<00:23:00.600> because<00:23:00.960> we<00:23:01.620> now<00:23:01.799> have<00:23:01.980> two 00:23:02.149 --> 00:23:02.159 align:start position:0% vulnerabilities because we now have two 00:23:02.159 --> 00:23:04.490 align:start position:0% vulnerabilities because we now have two of<00:23:02.340> them<00:23:02.400> that<00:23:02.520> can<00:23:02.760> warn<00:23:03.480> us<00:23:03.539> about<00:23:03.659> that<00:23:03.900> all 00:23:04.490 --> 00:23:04.500 align:start position:0% of them that can warn us about that all 00:23:04.500 --> 00:23:06.409 align:start position:0% of them that can warn us about that all right<00:23:04.679> and<00:23:05.039> last<00:23:05.280> but<00:23:05.520> not<00:23:05.640> least<00:23:05.760> on<00:23:06.240> the 00:23:06.409 --> 00:23:06.419 align:start position:0% right and last but not least on the 00:23:06.419 --> 00:23:08.510 align:start position:0% right and last but not least on the language<00:23:06.600> side<00:23:06.900> but<00:23:07.080> on<00:23:07.200> the<00:23:07.320> tooling<00:23:07.679> side<00:23:07.860> we 00:23:08.510 --> 00:23:08.520 align:start position:0% language side but on the tooling side we 00:23:08.520 --> 00:23:10.130 align:start position:0% language side but on the tooling side we have<00:23:08.640> Fork<00:23:08.940> the<00:23:09.120> fuel<00:23:09.299> orchestrator<00:23:09.720> which<00:23:10.020> is 00:23:10.130 --> 00:23:10.140 align:start position:0% have Fork the fuel orchestrator which is 00:23:10.140 --> 00:23:12.529 align:start position:0% have Fork the fuel orchestrator which is the<00:23:10.200> equivalent<00:23:10.559> of<00:23:10.740> Foundry<00:23:11.460> or<00:23:11.640> cargo<00:23:11.940> npm 00:23:12.529 --> 00:23:12.539 align:start position:0% the equivalent of Foundry or cargo npm 00:23:12.539 --> 00:23:14.810 align:start position:0% the equivalent of Foundry or cargo npm this<00:23:13.320> allows<00:23:13.679> you<00:23:13.740> to<00:23:13.919> do<00:23:14.100> a<00:23:14.460> variety<00:23:14.700> of 00:23:14.810 --> 00:23:14.820 align:start position:0% this allows you to do a variety of 00:23:14.820 --> 00:23:16.750 align:start position:0% this allows you to do a variety of things<00:23:15.059> including<00:23:15.659> building<00:23:15.900> deploying 00:23:16.750 --> 00:23:16.760 align:start position:0% things including building deploying 00:23:16.760 --> 00:23:18.340 align:start position:0% things including building deploying managing<00:23:17.760> dependencies 00:23:18.340 --> 00:23:18.350 align:start position:0% managing dependencies 00:23:18.350 --> 00:23:19.450 align:start position:0% managing dependencies [Music] 00:23:19.450 --> 00:23:19.460 align:start position:0% [Music] 00:23:19.460 --> 00:23:21.529 align:start position:0% [Music] thank<00:23:20.460> you<00:23:20.580> so<00:23:20.700> much<00:23:20.760> okay<00:23:20.940> it<00:23:21.120> allows<00:23:21.360> you<00:23:21.419> to 00:23:21.529 --> 00:23:21.539 align:start position:0% thank you so much okay it allows you to 00:23:21.539 --> 00:23:23.810 align:start position:0% thank you so much okay it allows you to build<00:23:21.659> apply<00:23:22.200> manage<00:23:22.919> dependencies<00:23:23.460> in<00:23:23.700> the 00:23:23.810 --> 00:23:23.820 align:start position:0% build apply manage dependencies in the 00:23:23.820 --> 00:23:25.610 align:start position:0% build apply manage dependencies in the same<00:23:23.880> way<00:23:24.000> cargo<00:23:24.360> does<00:23:24.539> so<00:23:24.720> no<00:23:24.960> weird<00:23:25.260> git 00:23:25.610 --> 00:23:25.620 align:start position:0% same way cargo does so no weird git 00:23:25.620 --> 00:23:27.830 align:start position:0% same way cargo does so no weird git modules<00:23:25.940> this<00:23:26.940> is<00:23:27.059> an<00:23:27.120> Australian<00:23:27.419> formatter 00:23:27.830 --> 00:23:27.840 align:start position:0% modules this is an Australian formatter 00:23:27.840 --> 00:23:30.350 align:start position:0% modules this is an Australian formatter test<00:23:28.440> a<00:23:28.980> language<00:23:29.340> server<00:23:29.700> we<00:23:29.880> actually<00:23:30.059> had<00:23:30.240> a 00:23:30.350 --> 00:23:30.360 align:start position:0% test a language server we actually had a 00:23:30.360 --> 00:23:32.770 align:start position:0% test a language server we actually had a language<00:23:30.480> server<00:23:30.840> before<00:23:31.159> uh 00:23:32.770 --> 00:23:32.780 align:start position:0% language server before uh 00:23:32.780 --> 00:23:35.870 align:start position:0% language server before uh so<00:23:33.780> if<00:23:34.080> you<00:23:34.200> want<00:23:34.380> to<00:23:34.559> there's<00:23:35.159> a<00:23:35.400> QR<00:23:35.580> code<00:23:35.700> to 00:23:35.870 --> 00:23:35.880 align:start position:0% so if you want to there's a QR code to 00:23:35.880 --> 00:23:37.610 align:start position:0% so if you want to there's a QR code to link<00:23:36.059> to<00:23:36.179> the<00:23:36.299> sway<00:23:36.480> book<00:23:36.720> if<00:23:37.260> you<00:23:37.380> want<00:23:37.500> to 00:23:37.610 --> 00:23:37.620 align:start position:0% link to the sway book if you want to 00:23:37.620 --> 00:23:40.130 align:start position:0% link to the sway book if you want to learn<00:23:37.740> how<00:23:37.919> to<00:23:38.039> write<00:23:38.159> Sway<00:23:38.520> and<00:23:38.820> dive<00:23:39.299> in<00:23:39.539> a 00:23:40.130 --> 00:23:40.140 align:start position:0% learn how to write Sway and dive in a 00:23:40.140 --> 00:23:41.630 align:start position:0% learn how to write Sway and dive in a head<00:23:40.320> first<00:23:40.559> this<00:23:40.919> will<00:23:41.100> take<00:23:41.220> you<00:23:41.340> straight 00:23:41.630 --> 00:23:41.640 align:start position:0% head first this will take you straight 00:23:41.640 --> 00:23:43.549 align:start position:0% head first this will take you straight there<00:23:42.360> I'm<00:23:42.720> gonna<00:23:42.840> leave<00:23:43.020> that<00:23:43.200> for<00:23:43.380> a<00:23:43.500> few 00:23:43.549 --> 00:23:43.559 align:start position:0% there I'm gonna leave that for a few 00:23:43.559 --> 00:23:44.510 align:start position:0% there I'm gonna leave that for a few more<00:23:43.679> seconds 00:23:44.510 --> 00:23:44.520 align:start position:0% more seconds 00:23:44.520 --> 00:23:46.789 align:start position:0% more seconds and<00:23:45.299> then<00:23:45.419> with<00:23:45.720> a<00:23:45.840> few<00:23:45.960> seconds<00:23:46.140> left<00:23:46.440> I<00:23:46.679> would 00:23:46.789 --> 00:23:46.799 align:start position:0% and then with a few seconds left I would 00:23:46.799 --> 00:23:49.130 align:start position:0% and then with a few seconds left I would like<00:23:46.919> to<00:23:47.039> close<00:23:47.159> out<00:23:47.400> the<00:23:47.640> slide<00:23:48.000> by<00:23:48.720> thanking 00:23:49.130 --> 00:23:49.140 align:start position:0% like to close out the slide by thanking 00:23:49.140 --> 00:23:51.049 align:start position:0% like to close out the slide by thanking not<00:23:49.500> only<00:23:49.679> you<00:23:49.919> guys<00:23:50.100> but<00:23:50.340> each<00:23:50.520> and<00:23:50.700> every<00:23:50.820> one 00:23:51.049 --> 00:23:51.059 align:start position:0% not only you guys but each and every one 00:23:51.059 --> 00:23:53.750 align:start position:0% not only you guys but each and every one after<00:23:51.419> using<00:23:51.840> 65<00:23:52.320> contributors<00:23:53.280> in<00:23:53.460> the<00:23:53.640> fuel 00:23:53.750 --> 00:23:53.760 align:start position:0% after using 65 contributors in the fuel 00:23:53.760 --> 00:23:55.430 align:start position:0% after using 65 contributors in the fuel Labs<00:23:54.120> team<00:23:54.299> that<00:23:54.600> has 00:23:55.430 --> 00:23:55.440 align:start position:0% Labs team that has 00:23:55.440 --> 00:23:58.370 align:start position:0% Labs team that has raw<00:23:55.980> fueled<00:23:56.340> where<00:23:56.520> it<00:23:56.640> is<00:23:56.760> today<00:23:56.940> thank<00:23:57.419> you 00:23:58.370 --> 00:23:58.380 align:start position:0% raw fueled where it is today thank you 00:23:58.380 --> 00:24:03.679 align:start position:0% raw fueled where it is today thank you [Applause]