WEBVTT Kind: captions Language: en 00:00:00.000 --> 00:00:04.350 align:start position:0% foreign 00:00:04.350 --> 00:00:04.360 align:start position:0% 00:00:04.360 --> 00:00:14.709 align:start position:0% [Music] 00:00:14.709 --> 00:00:14.719 align:start position:0% 00:00:14.719 --> 00:00:19.490 align:start position:0% I'm<00:00:15.719> Eric<00:00:15.900> marks<00:00:16.880> I<00:00:17.880> am<00:00:18.060> the<00:00:18.600> lead<00:00:18.779> engineer<00:00:19.199> of 00:00:19.490 --> 00:00:19.500 align:start position:0% I'm Eric marks I am the lead engineer of 00:00:19.500 --> 00:00:22.310 align:start position:0% I'm Eric marks I am the lead engineer of metamask<00:00:20.220> snaps<00:00:20.820> at<00:00:21.480> this<00:00:21.720> Workshop<00:00:22.020> is 00:00:22.310 --> 00:00:22.320 align:start position:0% metamask snaps at this Workshop is 00:00:22.320 --> 00:00:24.109 align:start position:0% metamask snaps at this Workshop is called<00:00:22.560> getting<00:00:23.100> started<00:00:23.460> with<00:00:23.640> metamask 00:00:24.109 --> 00:00:24.119 align:start position:0% called getting started with metamask 00:00:24.119 --> 00:00:27.050 align:start position:0% called getting started with metamask snaps<00:00:24.660> I<00:00:25.140> realize<00:00:25.380> we<00:00:25.560> have<00:00:25.680> some<00:00:25.859> Wi-Fi<00:00:26.279> ishma 00:00:27.050 --> 00:00:27.060 align:start position:0% snaps I realize we have some Wi-Fi ishma 00:00:27.060 --> 00:00:30.650 align:start position:0% snaps I realize we have some Wi-Fi ishma since<00:00:27.420> 2018<00:00:28.160> uh<00:00:29.160> snaps<00:00:29.640> was<00:00:29.760> first<00:00:29.939> announced 00:00:30.650 --> 00:00:30.660 align:start position:0% since 2018 uh snaps was first announced 00:00:30.660 --> 00:00:33.170 align:start position:0% since 2018 uh snaps was first announced as<00:00:30.840> a<00:00:31.019> concept<00:00:31.380> uh<00:00:32.160> three<00:00:32.399> years<00:00:32.579> ago<00:00:32.880> at 00:00:33.170 --> 00:00:33.180 align:start position:0% as a concept uh three years ago at 00:00:33.180 --> 00:00:36.229 align:start position:0% as a concept uh three years ago at Devcon<00:00:33.660> in<00:00:34.020> Osaka<00:00:34.620> so<00:00:35.460> I<00:00:35.579> know<00:00:35.700> we<00:00:35.940> have<00:00:36.059> we 00:00:36.229 --> 00:00:36.239 align:start position:0% Devcon in Osaka so I know we have we 00:00:36.239 --> 00:00:38.030 align:start position:0% Devcon in Osaka so I know we have we have<00:00:36.420> some<00:00:36.540> returning<00:00:37.020> guests<00:00:37.320> with<00:00:37.739> us<00:00:37.860> today 00:00:38.030 --> 00:00:38.040 align:start position:0% have some returning guests with us today 00:00:38.040 --> 00:00:40.850 align:start position:0% have some returning guests with us today in<00:00:38.280> the<00:00:38.399> room<00:00:38.540> and<00:00:39.540> uh<00:00:40.140> you<00:00:40.379> know<00:00:40.440> since<00:00:40.680> then 00:00:40.850 --> 00:00:40.860 align:start position:0% in the room and uh you know since then 00:00:40.860 --> 00:00:42.470 align:start position:0% in the room and uh you know since then lots<00:00:41.340> of<00:00:41.399> things<00:00:41.520> happened<00:00:41.700> covet<00:00:42.360> happened 00:00:42.470 --> 00:00:42.480 align:start position:0% lots of things happened covet happened 00:00:42.480 --> 00:00:45.950 align:start position:0% lots of things happened covet happened 2020<00:00:43.020> happened<00:00:43.379> but<00:00:44.100> since<00:00:44.399> uh<00:00:44.640> 2021<00:00:45.239> we've 00:00:45.950 --> 00:00:45.960 align:start position:0% 2020 happened but since uh 2021 we've 00:00:45.960 --> 00:00:48.290 align:start position:0% 2020 happened but since uh 2021 we've been<00:00:46.020> working<00:00:46.200> on<00:00:46.379> snaps<00:00:46.800> full-time<00:00:47.280> uh<00:00:48.059> at 00:00:48.290 --> 00:00:48.300 align:start position:0% been working on snaps full-time uh at 00:00:48.300 --> 00:00:50.209 align:start position:0% been working on snaps full-time uh at metamask<00:00:48.780> and<00:00:49.320> since<00:00:49.440> the<00:00:49.620> beginning<00:00:49.739> of<00:00:50.039> this 00:00:50.209 --> 00:00:50.219 align:start position:0% metamask and since the beginning of this 00:00:50.219 --> 00:00:53.209 align:start position:0% metamask and since the beginning of this year<00:00:50.600> we<00:00:51.600> have<00:00:51.840> been<00:00:52.200> in<00:00:52.440> a<00:00:52.620> developer<00:00:52.980> release 00:00:53.209 --> 00:00:53.219 align:start position:0% year we have been in a developer release 00:00:53.219 --> 00:00:55.970 align:start position:0% year we have been in a developer release via<00:00:53.940> our<00:00:54.120> Canary<00:00:54.840> version<00:00:55.140> of<00:00:55.440> the<00:00:55.559> metamask 00:00:55.970 --> 00:00:55.980 align:start position:0% via our Canary version of the metamask 00:00:55.980 --> 00:01:00.590 align:start position:0% via our Canary version of the metamask extension<00:00:56.460> called<00:00:57.239> metamask<00:00:57.719> flask<00:00:58.559> uh<00:00:59.460> and 00:01:00.590 --> 00:01:00.600 align:start position:0% extension called metamask flask uh and 00:01:00.600 --> 00:01:03.110 align:start position:0% extension called metamask flask uh and um<00:01:00.719> this<00:01:01.500> Workshop<00:01:01.800> is<00:01:02.160> basically<00:01:02.699> like<00:01:02.940> the 00:01:03.110 --> 00:01:03.120 align:start position:0% um this Workshop is basically like the 00:01:03.120 --> 00:01:05.030 align:start position:0% um this Workshop is basically like the sort<00:01:03.239> of<00:01:03.300> snaps<00:01:03.660> 101<00:01:04.140> how<00:01:04.440> do<00:01:04.559> you<00:01:04.619> get<00:01:04.739> started 00:01:05.030 --> 00:01:05.040 align:start position:0% sort of snaps 101 how do you get started 00:01:05.040 --> 00:01:07.490 align:start position:0% sort of snaps 101 how do you get started like<00:01:05.400> developing<00:01:05.880> a<00:01:06.060> snap<00:01:06.240> at<00:01:06.900> using<00:01:07.260> one<00:01:07.380> of 00:01:07.490 --> 00:01:07.500 align:start position:0% like developing a snap at using one of 00:01:07.500 --> 00:01:09.710 align:start position:0% like developing a snap at using one of the<00:01:07.560> newer<00:01:07.799> apis<00:01:08.159> that<00:01:08.340> we<00:01:08.520> developed 00:01:09.710 --> 00:01:09.720 align:start position:0% the newer apis that we developed 00:01:09.720 --> 00:01:11.570 align:start position:0% the newer apis that we developed um<00:01:09.840> if<00:01:10.200> you<00:01:10.320> read<00:01:10.500> the<00:01:10.680> instructions<00:01:11.220> there's 00:01:11.570 --> 00:01:11.580 align:start position:0% um if you read the instructions there's 00:01:11.580 --> 00:01:13.130 align:start position:0% um if you read the instructions there's a<00:01:11.820> custom<00:01:11.939> build<00:01:12.180> of<00:01:12.360> metamask<00:01:12.780> to<00:01:13.020> download 00:01:13.130 --> 00:01:13.140 align:start position:0% a custom build of metamask to download 00:01:13.140 --> 00:01:15.830 align:start position:0% a custom build of metamask to download because<00:01:13.560> we<00:01:14.040> haven't<00:01:14.159> shipped<00:01:14.700> this<00:01:15.000> API<00:01:15.720> in 00:01:15.830 --> 00:01:15.840 align:start position:0% because we haven't shipped this API in 00:01:15.840 --> 00:01:17.450 align:start position:0% because we haven't shipped this API in production<00:01:16.140> yet<00:01:16.380> it's<00:01:16.560> coming<00:01:16.799> in<00:01:17.040> the<00:01:17.280> next 00:01:17.450 --> 00:01:17.460 align:start position:0% production yet it's coming in the next 00:01:17.460 --> 00:01:19.250 align:start position:0% production yet it's coming in the next few<00:01:17.640> weeks 00:01:19.250 --> 00:01:19.260 align:start position:0% few weeks 00:01:19.260 --> 00:01:21.770 align:start position:0% few weeks um<00:01:19.380> but<00:01:19.680> uh<00:01:20.040> before<00:01:20.280> continuing<00:01:20.880> uh<00:01:21.420> we<00:01:21.659> need 00:01:21.770 --> 00:01:21.780 align:start position:0% um but uh before continuing uh we need 00:01:21.780 --> 00:01:23.210 align:start position:0% um but uh before continuing uh we need to<00:01:21.900> talk<00:01:22.020> a<00:01:22.140> little<00:01:22.200> bit<00:01:22.380> about<00:01:22.560> what<00:01:23.100> is 00:01:23.210 --> 00:01:23.220 align:start position:0% to talk a little bit about what is 00:01:23.220 --> 00:01:25.969 align:start position:0% to talk a little bit about what is metamask<00:01:23.759> Maps<00:01:24.259> uh<00:01:25.259> and<00:01:25.439> we're<00:01:25.560> gonna<00:01:25.680> and 00:01:25.969 --> 00:01:25.979 align:start position:0% metamask Maps uh and we're gonna and 00:01:25.979 --> 00:01:27.410 align:start position:0% metamask Maps uh and we're gonna and we're<00:01:26.100> gonna<00:01:26.220> start<00:01:26.520> from<00:01:27.000> the<00:01:27.119> very<00:01:27.180> ground 00:01:27.410 --> 00:01:27.420 align:start position:0% we're gonna start from the very ground 00:01:27.420 --> 00:01:30.469 align:start position:0% we're gonna start from the very ground level<00:01:27.720> and<00:01:28.320> build<00:01:28.680> up<00:01:28.860> from<00:01:29.100> there<00:01:29.220> and<00:01:30.180> so 00:01:30.469 --> 00:01:30.479 align:start position:0% level and build up from there and so 00:01:30.479 --> 00:01:33.230 align:start position:0% level and build up from there and so metamask<00:01:31.020> uh<00:01:31.680> as<00:01:31.979> uh<00:01:32.640> all<00:01:32.820> of<00:01:32.939> you<00:01:33.060> probably 00:01:33.230 --> 00:01:33.240 align:start position:0% metamask uh as uh all of you probably 00:01:33.240 --> 00:01:35.690 align:start position:0% metamask uh as uh all of you probably know<00:01:33.600> uh<00:01:34.380> is<00:01:34.619> a<00:01:34.979> non-custodial 00:01:35.690 --> 00:01:35.700 align:start position:0% know uh is a non-custodial 00:01:35.700 --> 00:01:38.330 align:start position:0% know uh is a non-custodial cryptocurrency<00:01:36.420> wallet<00:01:36.840> for<00:01:36.960> ethereum<00:01:37.439> uh 00:01:38.330 --> 00:01:38.340 align:start position:0% cryptocurrency wallet for ethereum uh 00:01:38.340 --> 00:01:39.950 align:start position:0% cryptocurrency wallet for ethereum uh you<00:01:38.579> enter<00:01:38.700> your<00:01:38.939> secret<00:01:39.180> recovery<00:01:39.720> phrase 00:01:39.950 --> 00:01:39.960 align:start position:0% you enter your secret recovery phrase 00:01:39.960 --> 00:01:42.410 align:start position:0% you enter your secret recovery phrase into<00:01:40.079> metamask<00:01:40.619> you<00:01:41.040> can<00:01:41.100> derive<00:01:41.520> your<00:01:42.180> at 00:01:42.410 --> 00:01:42.420 align:start position:0% into metamask you can derive your at 00:01:42.420 --> 00:01:43.789 align:start position:0% into metamask you can derive your at your<00:01:42.600> keys<00:01:42.840> and<00:01:42.960> your<00:01:43.140> externally<00:01:43.439> owned 00:01:43.789 --> 00:01:43.799 align:start position:0% your keys and your externally owned 00:01:43.799 --> 00:01:46.249 align:start position:0% your keys and your externally owned accounts<00:01:44.180> and<00:01:45.180> uh<00:01:45.600> it<00:01:45.780> will<00:01:45.900> manage<00:01:46.140> those 00:01:46.249 --> 00:01:46.259 align:start position:0% accounts and uh it will manage those 00:01:46.259 --> 00:01:47.690 align:start position:0% accounts and uh it will manage those keys<00:01:46.560> for<00:01:46.740> you<00:01:46.860> encrypt<00:01:47.340> them<00:01:47.400> with<00:01:47.579> a 00:01:47.690 --> 00:01:47.700 align:start position:0% keys for you encrypt them with a 00:01:47.700 --> 00:01:48.590 align:start position:0% keys for you encrypt them with a password 00:01:48.590 --> 00:01:48.600 align:start position:0% password 00:01:48.600 --> 00:01:51.710 align:start position:0% password uh<00:01:49.560> metamask<00:01:50.159> allows<00:01:50.759> you<00:01:50.880> to<00:01:51.180> interact<00:01:51.479> with 00:01:51.710 --> 00:01:51.720 align:start position:0% uh metamask allows you to interact with 00:01:51.720 --> 00:01:55.190 align:start position:0% uh metamask allows you to interact with ethereum<00:01:52.140> via<00:01:52.500> an<00:01:52.560> RPC<00:01:53.040> uh<00:01:53.820> endpoint<00:01:54.479> by 00:01:55.190 --> 00:01:55.200 align:start position:0% ethereum via an RPC uh endpoint by 00:01:55.200 --> 00:01:56.630 align:start position:0% ethereum via an RPC uh endpoint by default<00:01:55.500> we<00:01:55.680> use<00:01:55.799> our<00:01:55.920> friends<00:01:56.040> at<00:01:56.280> inferior 00:01:56.630 --> 00:01:56.640 align:start position:0% default we use our friends at inferior 00:01:56.640 --> 00:01:58.490 align:start position:0% default we use our friends at inferior but<00:01:56.880> you<00:01:56.939> can<00:01:57.060> add<00:01:57.240> whichever<00:01:57.899> ones<00:01:58.200> that<00:01:58.320> you 00:01:58.490 --> 00:01:58.500 align:start position:0% but you can add whichever ones that you 00:01:58.500 --> 00:01:59.210 align:start position:0% but you can add whichever ones that you want 00:01:59.210 --> 00:01:59.220 align:start position:0% want 00:01:59.220 --> 00:02:01.730 align:start position:0% want and<00:01:59.700> that<00:02:00.000> allows<00:02:00.240> you<00:02:00.299> to<00:02:00.479> do<00:02:00.600> stuff<00:02:00.840> like<00:02:01.140> you 00:02:01.730 --> 00:02:01.740 align:start position:0% and that allows you to do stuff like you 00:02:01.740 --> 00:02:03.230 align:start position:0% and that allows you to do stuff like you know<00:02:01.860> send<00:02:02.100> transactions<00:02:02.640> from<00:02:02.820> account<00:02:02.939> one 00:02:03.230 --> 00:02:03.240 align:start position:0% know send transactions from account one 00:02:03.240 --> 00:02:04.609 align:start position:0% know send transactions from account one to<00:02:03.420> account<00:02:03.600> two 00:02:04.609 --> 00:02:04.619 align:start position:0% to account two 00:02:04.619 --> 00:02:07.130 align:start position:0% to account two uh<00:02:05.520> the<00:02:06.119> really<00:02:06.420> powerful<00:02:06.840> thing<00:02:07.020> about 00:02:07.130 --> 00:02:07.140 align:start position:0% uh the really powerful thing about 00:02:07.140 --> 00:02:08.870 align:start position:0% uh the really powerful thing about metamask<00:02:07.680> is<00:02:07.920> that<00:02:08.039> it<00:02:08.099> enables<00:02:08.520> you<00:02:08.640> to 00:02:08.870 --> 00:02:08.880 align:start position:0% metamask is that it enables you to 00:02:08.880 --> 00:02:11.690 align:start position:0% metamask is that it enables you to interact<00:02:09.300> with<00:02:09.479> ethereum<00:02:10.020> dapps<00:02:10.560> and<00:02:11.160> so<00:02:11.400> that 00:02:11.690 --> 00:02:11.700 align:start position:0% interact with ethereum dapps and so that 00:02:11.700 --> 00:02:14.930 align:start position:0% interact with ethereum dapps and so that is<00:02:11.819> through<00:02:12.060> our<00:02:13.040> window.ethereum<00:02:14.040> uh 00:02:14.930 --> 00:02:14.940 align:start position:0% is through our window.ethereum uh 00:02:14.940 --> 00:02:17.570 align:start position:0% is through our window.ethereum uh provider<00:02:15.599> object<00:02:15.900> that<00:02:16.260> we<00:02:16.379> inject<00:02:16.680> into<00:02:17.340> the 00:02:17.570 --> 00:02:17.580 align:start position:0% provider object that we inject into the 00:02:17.580 --> 00:02:19.850 align:start position:0% provider object that we inject into the web<00:02:17.700> page<00:02:18.000> and<00:02:18.840> that<00:02:19.080> is<00:02:19.200> what<00:02:19.379> all<00:02:19.500> the<00:02:19.620> apps 00:02:19.850 --> 00:02:19.860 align:start position:0% web page and that is what all the apps 00:02:19.860 --> 00:02:22.369 align:start position:0% web page and that is what all the apps use<00:02:20.040> in<00:02:20.340> order<00:02:20.459> to<00:02:20.700> submit<00:02:21.060> Json<00:02:21.360> RPC<00:02:21.840> requests 00:02:22.369 --> 00:02:22.379 align:start position:0% use in order to submit Json RPC requests 00:02:22.379 --> 00:02:24.589 align:start position:0% use in order to submit Json RPC requests that<00:02:23.340> are<00:02:23.459> either<00:02:23.640> handled<00:02:24.060> directly<00:02:24.420> by 00:02:24.589 --> 00:02:24.599 align:start position:0% that are either handled directly by 00:02:24.599 --> 00:02:27.770 align:start position:0% that are either handled directly by metamask<00:02:25.080> or<00:02:25.620> art<00:02:25.860> contract<00:02:26.220> accounts 00:02:27.770 --> 00:02:27.780 align:start position:0% metamask or art contract accounts 00:02:27.780 --> 00:02:30.229 align:start position:0% metamask or art contract accounts um<00:02:27.900> what<00:02:28.560> about<00:02:28.680> uh<00:02:29.220> you<00:02:29.400> know<00:02:29.520> zero<00:02:30.000> knowledge 00:02:30.229 --> 00:02:30.239 align:start position:0% um what about uh you know zero knowledge 00:02:30.239 --> 00:02:32.330 align:start position:0% um what about uh you know zero knowledge applications<00:02:30.780> and<00:02:31.440> non-etherium 00:02:32.330 --> 00:02:32.340 align:start position:0% applications and non-etherium 00:02:32.340 --> 00:02:33.830 align:start position:0% applications and non-etherium cryptography<00:02:32.940> so<00:02:33.060> like<00:02:33.300> things<00:02:33.480> that<00:02:33.720> use 00:02:33.830 --> 00:02:33.840 align:start position:0% cryptography so like things that use 00:02:33.840 --> 00:02:37.729 align:start position:0% cryptography so like things that use curves<00:02:34.260> other<00:02:34.500> than<00:02:34.800> SEC<00:02:35.360> p256k1<00:02:36.500> uh<00:02:37.500> and 00:02:37.729 --> 00:02:37.739 align:start position:0% curves other than SEC p256k1 uh and 00:02:37.739 --> 00:02:40.910 align:start position:0% curves other than SEC p256k1 uh and that's<00:02:37.860> just<00:02:38.160> like<00:02:38.340> a<00:02:39.120> a<00:02:39.360> sample<00:02:40.080> of<00:02:40.800> the 00:02:40.910 --> 00:02:40.920 align:start position:0% that's just like a a sample of the 00:02:40.920 --> 00:02:42.910 align:start position:0% that's just like a a sample of the things<00:02:41.160> that's<00:02:41.819> being<00:02:42.000> built<00:02:42.239> in<00:02:42.360> ethereum 00:02:42.910 --> 00:02:42.920 align:start position:0% things that's being built in ethereum 00:02:42.920 --> 00:02:46.009 align:start position:0% things that's being built in ethereum that<00:02:43.920> we<00:02:44.220> don't<00:02:44.760> support<00:02:45.000> out<00:02:45.300> of<00:02:45.420> the<00:02:45.480> box<00:02:45.660> and 00:02:46.009 --> 00:02:46.019 align:start position:0% that we don't support out of the box and 00:02:46.019 --> 00:02:47.089 align:start position:0% that we don't support out of the box and that<00:02:46.140> you<00:02:46.319> know<00:02:46.379> doesn't<00:02:46.620> even<00:02:46.800> get<00:02:46.980> into 00:02:47.089 --> 00:02:47.099 align:start position:0% that you know doesn't even get into 00:02:47.099 --> 00:02:49.430 align:start position:0% that you know doesn't even get into Cosmos<00:02:47.640> polka<00:02:48.180> dots<00:02:48.420> Avalanche<00:02:49.140> Solana 00:02:49.430 --> 00:02:49.440 align:start position:0% Cosmos polka dots Avalanche Solana 00:02:49.440 --> 00:02:50.570 align:start position:0% Cosmos polka dots Avalanche Solana whatever 00:02:50.570 --> 00:02:50.580 align:start position:0% whatever 00:02:50.580 --> 00:02:54.050 align:start position:0% whatever um<00:02:50.640> in<00:02:51.480> addition<00:02:51.660> to<00:02:52.080> uh<00:02:52.500> to<00:02:52.739> those<00:02:52.860> things<00:02:53.099> and 00:02:54.050 --> 00:02:54.060 align:start position:0% um in addition to uh to those things and 00:02:54.060 --> 00:02:57.050 align:start position:0% um in addition to uh to those things and so<00:02:54.360> uh<00:02:55.319> it<00:02:55.680> is<00:02:55.860> uh 00:02:57.050 --> 00:02:57.060 align:start position:0% so uh it is uh 00:02:57.060 --> 00:03:00.890 align:start position:0% so uh it is uh uh<00:02:57.840> we<00:02:58.200> believe<00:02:58.459> basically<00:02:59.459> impossible<00:03:00.060> and<00:03:00.540> I 00:03:00.890 --> 00:03:00.900 align:start position:0% uh we believe basically impossible and I 00:03:00.900 --> 00:03:02.390 align:start position:0% uh we believe basically impossible and I think<00:03:01.019> you<00:03:01.200> know<00:03:01.319> practically<00:03:01.739> uh<00:03:02.160> like 00:03:02.390 --> 00:03:02.400 align:start position:0% think you know practically uh like 00:03:02.400 --> 00:03:04.670 align:start position:0% think you know practically uh like empiric<00:03:03.300> like<00:03:03.599> I<00:03:03.720> observe<00:03:04.200> this<00:03:04.319> I<00:03:04.560> don't 00:03:04.670 --> 00:03:04.680 align:start position:0% empiric like I observe this I don't 00:03:04.680 --> 00:03:06.170 align:start position:0% empiric like I observe this I don't predict<00:03:04.920> it<00:03:05.040> it<00:03:05.220> is<00:03:05.400> impossible<00:03:05.819> for<00:03:06.060> any 00:03:06.170 --> 00:03:06.180 align:start position:0% predict it it is impossible for any 00:03:06.180 --> 00:03:08.809 align:start position:0% predict it it is impossible for any single<00:03:06.540> organization<00:03:07.080> to 00:03:08.809 --> 00:03:08.819 align:start position:0% single organization to 00:03:08.819 --> 00:03:11.449 align:start position:0% single organization to uh<00:03:09.599> add<00:03:09.840> support<00:03:10.080> to<00:03:10.379> develop<00:03:10.620> the<00:03:10.860> domain 00:03:11.449 --> 00:03:11.459 align:start position:0% uh add support to develop the domain 00:03:11.459 --> 00:03:13.610 align:start position:0% uh add support to develop the domain expertise<00:03:12.000> to<00:03:12.720> understand<00:03:12.900> all<00:03:13.379> of<00:03:13.500> these 00:03:13.610 --> 00:03:13.620 align:start position:0% expertise to understand all of these 00:03:13.620 --> 00:03:15.410 align:start position:0% expertise to understand all of these different<00:03:13.800> protocols<00:03:14.340> and<00:03:14.459> Primitives<00:03:14.879> and 00:03:15.410 --> 00:03:15.420 align:start position:0% different protocols and Primitives and 00:03:15.420 --> 00:03:16.970 align:start position:0% different protocols and Primitives and then<00:03:15.480> also<00:03:15.840> to<00:03:16.019> develop<00:03:16.319> the<00:03:16.500> code<00:03:16.680> and 00:03:16.970 --> 00:03:16.980 align:start position:0% then also to develop the code and 00:03:16.980 --> 00:03:19.490 align:start position:0% then also to develop the code and maintain<00:03:17.400> the<00:03:18.000> you<00:03:18.239> know<00:03:18.360> unimaginably<00:03:19.260> large 00:03:19.490 --> 00:03:19.500 align:start position:0% maintain the you know unimaginably large 00:03:19.500 --> 00:03:21.290 align:start position:0% maintain the you know unimaginably large code<00:03:19.739> base<00:03:19.920> that<00:03:20.220> it<00:03:20.340> would<00:03:20.459> take<00:03:20.580> to<00:03:21.060> actually 00:03:21.290 --> 00:03:21.300 align:start position:0% code base that it would take to actually 00:03:21.300 --> 00:03:23.149 align:start position:0% code base that it would take to actually create<00:03:21.659> user<00:03:22.200> experience<00:03:22.500> for<00:03:22.739> all<00:03:22.920> of<00:03:23.040> the 00:03:23.149 --> 00:03:23.159 align:start position:0% create user experience for all of the 00:03:23.159 --> 00:03:25.149 align:start position:0% create user experience for all of the things<00:03:23.280> that<00:03:23.400> are<00:03:23.519> being<00:03:23.700> built<00:03:24.000> in<00:03:24.239> web<00:03:24.420> 3. 00:03:25.149 --> 00:03:25.159 align:start position:0% things that are being built in web 3. 00:03:25.159 --> 00:03:29.089 align:start position:0% things that are being built in web 3. and<00:03:26.159> metamask<00:03:27.000> snaps<00:03:27.480> is<00:03:27.780> our<00:03:28.080> answer<00:03:28.620> to<00:03:28.920> this 00:03:29.089 --> 00:03:29.099 align:start position:0% and metamask snaps is our answer to this 00:03:29.099 --> 00:03:30.790 align:start position:0% and metamask snaps is our answer to this problem 00:03:30.790 --> 00:03:30.800 align:start position:0% problem 00:03:30.800 --> 00:03:33.710 align:start position:0% problem and<00:03:31.800> snaps<00:03:32.280> are<00:03:32.340> simply<00:03:32.640> sandbox<00:03:33.060> programs 00:03:33.710 --> 00:03:33.720 align:start position:0% and snaps are simply sandbox programs 00:03:33.720 --> 00:03:36.170 align:start position:0% and snaps are simply sandbox programs that<00:03:34.140> are<00:03:34.440> run<00:03:34.560> by<00:03:34.739> metamask<00:03:35.220> and<00:03:36.000> their 00:03:36.170 --> 00:03:36.180 align:start position:0% that are run by metamask and their 00:03:36.180 --> 00:03:38.089 align:start position:0% that are run by metamask and their purpose<00:03:36.480> is<00:03:36.780> to<00:03:37.019> create<00:03:37.200> new<00:03:37.739> user 00:03:38.089 --> 00:03:38.099 align:start position:0% purpose is to create new user 00:03:38.099 --> 00:03:40.009 align:start position:0% purpose is to create new user experiences<00:03:38.640> in<00:03:38.879> the<00:03:39.000> wallet<00:03:39.300> and<00:03:39.540> that<00:03:39.659> is<00:03:39.840> to 00:03:40.009 --> 00:03:40.019 align:start position:0% experiences in the wallet and that is to 00:03:40.019 --> 00:03:41.809 align:start position:0% experiences in the wallet and that is to say<00:03:40.140> that<00:03:40.739> the<00:03:40.920> purpose<00:03:41.159> is<00:03:41.220> for<00:03:41.400> them<00:03:41.519> to 00:03:41.809 --> 00:03:41.819 align:start position:0% say that the purpose is for them to 00:03:41.819 --> 00:03:45.410 align:start position:0% say that the purpose is for them to modify<00:03:42.360> the<00:03:43.080> wallet<00:03:43.379> in<00:03:43.739> some<00:03:43.920> useful<00:03:44.220> way 00:03:45.410 --> 00:03:45.420 align:start position:0% modify the wallet in some useful way 00:03:45.420 --> 00:03:48.470 align:start position:0% modify the wallet in some useful way and<00:03:46.080> uh<00:03:46.620> the<00:03:46.920> user<00:03:47.220> adds<00:03:47.640> snaps<00:03:47.940> to<00:03:48.060> the<00:03:48.180> wallet 00:03:48.470 --> 00:03:48.480 align:start position:0% and uh the user adds snaps to the wallet 00:03:48.480 --> 00:03:51.229 align:start position:0% and uh the user adds snaps to the wallet at<00:03:48.720> runtime<00:03:49.099> and<00:03:50.099> they<00:03:50.400> have<00:03:50.580> access<00:03:50.760> to 00:03:51.229 --> 00:03:51.239 align:start position:0% at runtime and they have access to 00:03:51.239 --> 00:03:52.850 align:start position:0% at runtime and they have access to special<00:03:51.780> permissions<00:03:52.379> that<00:03:52.620> are<00:03:52.680> not 00:03:52.850 --> 00:03:52.860 align:start position:0% special permissions that are not 00:03:52.860 --> 00:03:55.369 align:start position:0% special permissions that are not available<00:03:53.040> to<00:03:53.340> dapps<00:03:53.959> including<00:03:54.959> things<00:03:55.200> like 00:03:55.369 --> 00:03:55.379 align:start position:0% available to dapps including things like 00:03:55.379 --> 00:03:57.350 align:start position:0% available to dapps including things like key<00:03:55.560> management<00:03:55.799> and<00:03:56.760> that<00:03:56.940> makes<00:03:57.060> them 00:03:57.350 --> 00:03:57.360 align:start position:0% key management and that makes them 00:03:57.360 --> 00:04:00.170 align:start position:0% key management and that makes them uniquely<00:03:57.840> powerful<00:03:58.260> building<00:03:58.560> blocks<00:03:59.180> for 00:04:00.170 --> 00:04:00.180 align:start position:0% uniquely powerful building blocks for 00:04:00.180 --> 00:04:02.530 align:start position:0% uniquely powerful building blocks for web<00:04:00.360> 3<00:04:00.540> Developers 00:04:02.530 --> 00:04:02.540 align:start position:0% web 3 Developers 00:04:02.540 --> 00:04:05.390 align:start position:0% web 3 Developers and<00:04:03.540> so<00:04:03.959> using<00:04:04.260> this<00:04:04.379> simple<00:04:04.560> model<00:04:04.860> just<00:04:05.280> in 00:04:05.390 --> 00:04:05.400 align:start position:0% and so using this simple model just in 00:04:05.400 --> 00:04:08.030 align:start position:0% and so using this simple model just in the<00:04:05.580> past<00:04:05.640> week<00:04:06.000> over<00:04:06.720> the<00:04:06.959> course<00:04:07.140> of<00:04:07.379> eth 00:04:08.030 --> 00:04:08.040 align:start position:0% the past week over the course of eth 00:04:08.040 --> 00:04:10.910 align:start position:0% the past week over the course of eth Bogota<00:04:08.400> and<00:04:08.940> some<00:04:09.180> and<00:04:09.659> a<00:04:09.840> hacker<00:04:10.140> house<00:04:10.319> that 00:04:10.910 --> 00:04:10.920 align:start position:0% Bogota and some and a hacker house that 00:04:10.920 --> 00:04:13.670 align:start position:0% Bogota and some and a hacker house that uh<00:04:11.099> we<00:04:11.280> co-sponsored<00:04:11.939> uh<00:04:12.540> with<00:04:12.840> uh<00:04:13.080> bit<00:04:13.260> Dao<00:04:13.560> in 00:04:13.670 --> 00:04:13.680 align:start position:0% uh we co-sponsored uh with uh bit Dao in 00:04:13.680 --> 00:04:16.490 align:start position:0% uh we co-sponsored uh with uh bit Dao in game<00:04:13.799> seven<00:04:14.180> hackers<00:04:15.180> have<00:04:15.299> developed<00:04:15.780> a<00:04:16.079> CK 00:04:16.490 --> 00:04:16.500 align:start position:0% game seven hackers have developed a CK 00:04:16.500 --> 00:04:19.009 align:start position:0% game seven hackers have developed a CK nullifier<00:04:17.040> snap<00:04:17.400> uh<00:04:18.180> transaction<00:04:18.479> Securities 00:04:19.009 --> 00:04:19.019 align:start position:0% nullifier snap uh transaction Securities 00:04:19.019 --> 00:04:21.170 align:start position:0% nullifier snap uh transaction Securities map<00:04:19.380> an<00:04:19.919> account<00:04:20.160> account<00:04:20.519> activity 00:04:21.170 --> 00:04:21.180 align:start position:0% map an account account activity 00:04:21.180 --> 00:04:23.570 align:start position:0% map an account account activity notifications<00:04:21.780> and<00:04:22.560> a<00:04:22.979> smart<00:04:23.220> contract 00:04:23.570 --> 00:04:23.580 align:start position:0% notifications and a smart contract 00:04:23.580 --> 00:04:25.969 align:start position:0% notifications and a smart contract account<00:04:23.820> wallet<00:04:24.360> uh<00:04:24.960> or<00:04:25.139> a<00:04:25.259> smart<00:04:25.620> contract 00:04:25.969 --> 00:04:25.979 align:start position:0% account wallet uh or a smart contract 00:04:25.979 --> 00:04:28.310 align:start position:0% account wallet uh or a smart contract Account<00:04:26.220> Support<00:04:26.580> uh<00:04:27.300> all<00:04:27.479> in<00:04:27.540> metamask<00:04:27.960> all 00:04:28.310 --> 00:04:28.320 align:start position:0% Account Support uh all in metamask all 00:04:28.320 --> 00:04:31.550 align:start position:0% Account Support uh all in metamask all using<00:04:28.560> snaps<00:04:29.060> and<00:04:30.060> uh<00:04:30.540> and<00:04:30.840> snaps<00:04:31.259> currently 00:04:31.550 --> 00:04:31.560 align:start position:0% using snaps and uh and snaps currently 00:04:31.560 --> 00:04:34.070 align:start position:0% using snaps and uh and snaps currently in<00:04:31.919> developer<00:04:32.340> releases<00:04:32.759> include<00:04:33.240> uh 00:04:34.070 --> 00:04:34.080 align:start position:0% in developer releases include uh 00:04:34.080 --> 00:04:38.030 align:start position:0% in developer releases include uh starknet<00:04:34.680> filecoin<00:04:35.580> at<00:04:36.000> Bitcoin<00:04:36.540> R<00:04:36.840> weave<00:04:37.259> and 00:04:38.030 --> 00:04:38.040 align:start position:0% starknet filecoin at Bitcoin R weave and 00:04:38.040 --> 00:04:40.070 align:start position:0% starknet filecoin at Bitcoin R weave and many<00:04:38.160> more<00:04:38.340> and<00:04:38.699> so<00:04:39.000> and<00:04:39.419> here<00:04:39.780> I'll<00:04:39.960> just 00:04:40.070 --> 00:04:40.080 align:start position:0% many more and so and here I'll just 00:04:40.080 --> 00:04:42.290 align:start position:0% many more and so and here I'll just briefly<00:04:40.380> stop<00:04:40.500> to<00:04:40.740> say<00:04:40.860> that<00:04:41.040> like<00:04:41.340> we're<00:04:42.120> all 00:04:42.290 --> 00:04:42.300 align:start position:0% briefly stop to say that like we're all 00:04:42.300 --> 00:04:44.330 align:start position:0% briefly stop to say that like we're all uh<00:04:42.720> like<00:04:43.020> this<00:04:43.380> isn't<00:04:43.620> a<00:04:43.800> developer<00:04:44.160> release 00:04:44.330 --> 00:04:44.340 align:start position:0% uh like this isn't a developer release 00:04:44.340 --> 00:04:46.129 align:start position:0% uh like this isn't a developer release so<00:04:44.820> the<00:04:45.120> reason<00:04:45.240> we<00:04:45.479> keep<00:04:45.600> it<00:04:45.720> in<00:04:45.840> the<00:04:45.960> channel 00:04:46.129 --> 00:04:46.139 align:start position:0% so the reason we keep it in the channel 00:04:46.139 --> 00:04:48.890 align:start position:0% so the reason we keep it in the channel is<00:04:46.440> because<00:04:46.680> we<00:04:47.639> don't<00:04:47.759> it's<00:04:48.180> not<00:04:48.419> quite<00:04:48.660> ready 00:04:48.890 --> 00:04:48.900 align:start position:0% is because we don't it's not quite ready 00:04:48.900 --> 00:04:51.710 align:start position:0% is because we don't it's not quite ready to<00:04:49.199> be<00:04:49.320> pushed<00:04:49.620> for<00:04:49.860> it<00:04:50.100> to<00:04:50.280> be<00:04:50.400> pushed<00:04:50.699> to<00:04:50.820> uh 00:04:51.710 --> 00:04:51.720 align:start position:0% to be pushed for it to be pushed to uh 00:04:51.720 --> 00:04:53.270 align:start position:0% to be pushed for it to be pushed to uh you<00:04:51.900> know<00:04:51.960> the<00:04:52.080> tens<00:04:52.259> of<00:04:52.380> millions<00:04:52.740> of<00:04:52.919> people 00:04:53.270 --> 00:04:53.280 align:start position:0% you know the tens of millions of people 00:04:53.280 --> 00:04:55.850 align:start position:0% you know the tens of millions of people that<00:04:53.520> use<00:04:53.639> metamask<00:04:54.120> on<00:04:54.360> a<00:04:54.479> daily<00:04:54.540> basis<00:04:54.960> uh 00:04:55.850 --> 00:04:55.860 align:start position:0% that use metamask on a daily basis uh 00:04:55.860 --> 00:04:58.010 align:start position:0% that use metamask on a daily basis uh but<00:04:56.100> that<00:04:56.580> is<00:04:56.699> our<00:04:56.940> goal<00:04:57.300> in<00:04:57.600> the<00:04:57.660> upcoming 00:04:58.010 --> 00:04:58.020 align:start position:0% but that is our goal in the upcoming 00:04:58.020 --> 00:05:00.950 align:start position:0% but that is our goal in the upcoming year<00:04:58.199> and<00:04:58.440> we'll<00:04:58.560> get<00:04:58.740> to<00:04:58.860> that<00:04:59.040> in<00:04:59.580> a<00:04:59.699> bit 00:05:00.950 --> 00:05:00.960 align:start position:0% year and we'll get to that in a bit 00:05:00.960 --> 00:05:04.670 align:start position:0% year and we'll get to that in a bit uh<00:05:01.800> and<00:05:02.220> so<00:05:02.520> uh<00:05:03.300> we<00:05:03.780> and<00:05:03.960> so<00:05:04.259> we<00:05:04.380> believe<00:05:04.500> that 00:05:04.670 --> 00:05:04.680 align:start position:0% uh and so uh we and so we believe that 00:05:04.680 --> 00:05:06.350 align:start position:0% uh and so uh we and so we believe that this<00:05:04.860> illustrates<00:05:05.280> that<00:05:05.520> snaps<00:05:06.000> is<00:05:06.180> the 00:05:06.350 --> 00:05:06.360 align:start position:0% this illustrates that snaps is the 00:05:06.360 --> 00:05:08.330 align:start position:0% this illustrates that snaps is the gateway<00:05:06.660> to<00:05:06.900> all<00:05:07.020> of<00:05:07.139> web<00:05:07.320> 3.<00:05:07.740> by<00:05:07.919> turning<00:05:08.220> the 00:05:08.330 --> 00:05:08.340 align:start position:0% gateway to all of web 3. by turning the 00:05:08.340 --> 00:05:10.010 align:start position:0% gateway to all of web 3. by turning the wallet<00:05:08.699> itself<00:05:09.000> into<00:05:09.419> an<00:05:09.660> application 00:05:10.010 --> 00:05:10.020 align:start position:0% wallet itself into an application 00:05:10.020 --> 00:05:13.189 align:start position:0% wallet itself into an application platform<00:05:10.560> only<00:05:11.160> then<00:05:11.520> can<00:05:12.000> we<00:05:12.180> invite<00:05:12.600> the 00:05:13.189 --> 00:05:13.199 align:start position:0% platform only then can we invite the 00:05:13.199 --> 00:05:15.110 align:start position:0% platform only then can we invite the entire<00:05:13.440> community<00:05:13.680> in<00:05:14.160> in<00:05:14.639> order<00:05:14.820> to<00:05:14.940> bring 00:05:15.110 --> 00:05:15.120 align:start position:0% entire community in in order to bring 00:05:15.120 --> 00:05:17.090 align:start position:0% entire community in in order to bring their<00:05:15.360> domain<00:05:15.660> expertise<00:05:16.199> and<00:05:16.500> their<00:05:16.740> passion 00:05:17.090 --> 00:05:17.100 align:start position:0% their domain expertise and their passion 00:05:17.100 --> 00:05:19.189 align:start position:0% their domain expertise and their passion for<00:05:17.460> uh<00:05:18.060> the<00:05:18.240> specific<00:05:18.540> features<00:05:18.960> and 00:05:19.189 --> 00:05:19.199 align:start position:0% for uh the specific features and 00:05:19.199 --> 00:05:20.689 align:start position:0% for uh the specific features and functionality<00:05:19.740> that<00:05:20.040> they're<00:05:20.160> interested<00:05:20.580> in 00:05:20.689 --> 00:05:20.699 align:start position:0% functionality that they're interested in 00:05:20.699 --> 00:05:22.610 align:start position:0% functionality that they're interested in in<00:05:21.120> order<00:05:21.300> to<00:05:21.419> add<00:05:21.600> that<00:05:21.840> functionality<00:05:22.320> to 00:05:22.610 --> 00:05:22.620 align:start position:0% in order to add that functionality to 00:05:22.620 --> 00:05:25.610 align:start position:0% in order to add that functionality to the<00:05:22.740> wallet<00:05:23.100> and<00:05:23.520> make<00:05:23.699> it<00:05:23.880> available<00:05:24.139> to<00:05:25.139> all 00:05:25.610 --> 00:05:25.620 align:start position:0% the wallet and make it available to all 00:05:25.620 --> 00:05:27.490 align:start position:0% the wallet and make it available to all of<00:05:25.740> their<00:05:25.919> users 00:05:27.490 --> 00:05:27.500 align:start position:0% of their users 00:05:27.500 --> 00:05:30.469 align:start position:0% of their users and<00:05:28.500> uh<00:05:28.979> with<00:05:29.280> that<00:05:29.460> uh<00:05:30.060> we're<00:05:30.180> gonna<00:05:30.300> get 00:05:30.469 --> 00:05:30.479 align:start position:0% and uh with that uh we're gonna get 00:05:30.479 --> 00:05:34.070 align:start position:0% and uh with that uh we're gonna get started<00:05:30.919> uh<00:05:31.919> so<00:05:32.160> so<00:05:32.639> again<00:05:32.940> uh<00:05:33.600> there's<00:05:33.840> the 00:05:34.070 --> 00:05:34.080 align:start position:0% started uh so so again uh there's the 00:05:34.080 --> 00:05:36.529 align:start position:0% started uh so so again uh there's the hack<00:05:34.320> MD<00:05:34.620> link<00:05:34.919> uh<00:05:35.639> for<00:05:36.000> those<00:05:36.120> of<00:05:36.240> you<00:05:36.360> who<00:05:36.479> are 00:05:36.529 --> 00:05:36.539 align:start position:0% hack MD link uh for those of you who are 00:05:36.539 --> 00:05:41.210 align:start position:0% hack MD link uh for those of you who are able<00:05:36.900> to<00:05:37.080> access<00:05:37.979> that 00:05:41.210 --> 00:05:41.220 align:start position:0% 00:05:41.220 --> 00:05:46.490 align:start position:0% and<00:05:41.940> we're<00:05:42.120> going<00:05:42.240> to<00:05:42.360> start<00:05:42.539> here 00:05:46.490 --> 00:05:46.500 align:start position:0% 00:05:46.500 --> 00:05:51.469 align:start position:0% and<00:05:47.039> we're<00:05:47.220> actually<00:05:47.460> going<00:05:47.880> to 00:05:51.469 --> 00:05:51.479 align:start position:0% 00:05:51.479 --> 00:05:53.330 align:start position:0% I<00:05:51.840> was<00:05:51.960> I<00:05:52.139> was<00:05:52.320> too<00:05:52.440> busy<00:05:52.680> trying<00:05:52.860> to<00:05:53.039> get<00:05:53.160> my 00:05:53.330 --> 00:05:53.340 align:start position:0% I was I was too busy trying to get my 00:05:53.340 --> 00:05:55.610 align:start position:0% I was I was too busy trying to get my Wi-Fi<00:05:53.639> to<00:05:53.940> work<00:05:54.120> uh<00:05:54.720> to<00:05:54.900> clear<00:05:55.080> out<00:05:55.320> all<00:05:55.560> of 00:05:55.610 --> 00:05:55.620 align:start position:0% Wi-Fi to work uh to clear out all of 00:05:55.620 --> 00:05:56.629 align:start position:0% Wi-Fi to work uh to clear out all of this<00:05:55.800> stuff 00:05:56.629 --> 00:05:56.639 align:start position:0% this stuff 00:05:56.639 --> 00:05:59.029 align:start position:0% this stuff but<00:05:56.940> we'll<00:05:57.120> get<00:05:57.360> started<00:05:57.660> here<00:05:57.780> in<00:05:57.960> a<00:05:58.080> second 00:05:59.029 --> 00:05:59.039 align:start position:0% but we'll get started here in a second 00:05:59.039 --> 00:06:00.469 align:start position:0% but we'll get started here in a second and<00:05:59.580> so 00:06:00.469 --> 00:06:00.479 align:start position:0% and so 00:06:00.479 --> 00:06:02.570 align:start position:0% and so uh<00:06:01.259> so<00:06:01.380> as<00:06:01.560> I<00:06:01.680> mentioned<00:06:01.860> the<00:06:02.100> first<00:06:02.280> thing 00:06:02.570 --> 00:06:02.580 align:start position:0% uh so as I mentioned the first thing 00:06:02.580 --> 00:06:04.490 align:start position:0% uh so as I mentioned the first thing that<00:06:03.000> we<00:06:03.120> need<00:06:03.240> to<00:06:03.360> do 00:06:04.490 --> 00:06:04.500 align:start position:0% that we need to do 00:06:04.500 --> 00:06:08.870 align:start position:0% that we need to do is<00:06:04.860> add<00:06:05.699> a<00:06:06.300> custom<00:06:06.780> build<00:06:07.139> of<00:06:07.800> uh<00:06:08.280> metamask 00:06:08.870 --> 00:06:08.880 align:start position:0% is add a custom build of uh metamask 00:06:08.880 --> 00:06:12.050 align:start position:0% is add a custom build of uh metamask flask<00:06:09.300> to<00:06:10.080> the<00:06:10.380> browser 00:06:12.050 --> 00:06:12.060 align:start position:0% flask to the browser 00:06:12.060 --> 00:06:15.469 align:start position:0% flask to the browser and<00:06:12.900> uh<00:06:13.199> my<00:06:13.500> visibility<00:06:13.860> is<00:06:14.280> is<00:06:14.520> the<00:06:14.820> size<00:06:15.240> of 00:06:15.469 --> 00:06:15.479 align:start position:0% and uh my visibility is is the size of 00:06:15.479 --> 00:06:16.730 align:start position:0% and uh my visibility is is the size of like<00:06:15.600> the<00:06:15.780> editor<00:06:16.080> and<00:06:16.259> the<00:06:16.440> text<00:06:16.560> and 00:06:16.730 --> 00:06:16.740 align:start position:0% like the editor and the text and 00:06:16.740 --> 00:06:18.830 align:start position:0% like the editor and the text and everything<00:06:16.919> good<00:06:17.160> so<00:06:17.460> far<00:06:17.639> okay<00:06:18.300> yeah<00:06:18.600> please 00:06:18.830 --> 00:06:18.840 align:start position:0% everything good so far okay yeah please 00:06:18.840 --> 00:06:20.810 align:start position:0% everything good so far okay yeah please please<00:06:19.139> holler<00:06:19.560> at<00:06:19.680> me<00:06:19.800> if<00:06:20.039> not 00:06:20.810 --> 00:06:20.820 align:start position:0% please holler at me if not 00:06:20.820 --> 00:06:22.129 align:start position:0% please holler at me if not and 00:06:22.129 --> 00:06:22.139 align:start position:0% and 00:06:22.139 --> 00:06:25.730 align:start position:0% and um<00:06:22.460> uh<00:06:23.460> the<00:06:24.060> way<00:06:24.120> you<00:06:24.300> add<00:06:24.539> a<00:06:24.780> custom<00:06:24.900> build<00:06:25.199> uh 00:06:25.730 --> 00:06:25.740 align:start position:0% um uh the way you add a custom build uh 00:06:25.740 --> 00:06:29.390 align:start position:0% um uh the way you add a custom build uh to<00:06:25.919> Chrome<00:06:26.100> uh<00:06:26.880> is<00:06:27.060> you<00:06:27.419> simply<00:06:28.039> uh<00:06:29.039> get<00:06:29.220> your 00:06:29.390 --> 00:06:29.400 align:start position:0% to Chrome uh is you simply uh get your 00:06:29.400 --> 00:06:31.430 align:start position:0% to Chrome uh is you simply uh get your build<00:06:29.580> from<00:06:29.880> wherever<00:06:30.240> uh<00:06:30.960> from<00:06:31.199> wherever 00:06:31.430 --> 00:06:31.440 align:start position:0% build from wherever uh from wherever 00:06:31.440 --> 00:06:33.469 align:start position:0% build from wherever uh from wherever that<00:06:31.620> lives<00:06:31.979> and<00:06:32.460> you<00:06:32.639> just<00:06:32.819> drag<00:06:32.940> and<00:06:33.120> drop<00:06:33.300> it 00:06:33.469 --> 00:06:33.479 align:start position:0% that lives and you just drag and drop it 00:06:33.479 --> 00:06:35.390 align:start position:0% that lives and you just drag and drop it in<00:06:33.600> uh<00:06:34.440> your<00:06:34.680> browser<00:06:34.919> needs<00:06:35.160> to<00:06:35.220> be<00:06:35.280> in 00:06:35.390 --> 00:06:35.400 align:start position:0% in uh your browser needs to be in 00:06:35.400 --> 00:06:36.590 align:start position:0% in uh your browser needs to be in developer<00:06:35.880> mode 00:06:36.590 --> 00:06:36.600 align:start position:0% developer mode 00:06:36.600 --> 00:06:40.670 align:start position:0% developer mode uh<00:06:37.560> in<00:06:37.800> order<00:06:37.979> for<00:06:38.639> uh<00:06:39.060> that<00:06:39.240> to<00:06:39.419> work<00:06:39.600> uh<00:06:40.560> so 00:06:40.670 --> 00:06:40.680 align:start position:0% uh in order for uh that to work uh so 00:06:40.680 --> 00:06:42.350 align:start position:0% uh in order for uh that to work uh so and<00:06:40.860> be<00:06:41.039> advised<00:06:41.400> that<00:06:41.460> developer<00:06:41.880> mode<00:06:42.000> like 00:06:42.350 --> 00:06:42.360 align:start position:0% and be advised that developer mode like 00:06:42.360 --> 00:06:44.270 align:start position:0% and be advised that developer mode like exposes<00:06:42.840> your<00:06:43.020> extensions<00:06:43.440> to<00:06:43.740> certain<00:06:43.860> kinds 00:06:44.270 --> 00:06:44.280 align:start position:0% exposes your extensions to certain kinds 00:06:44.280 --> 00:06:47.629 align:start position:0% exposes your extensions to certain kinds of<00:06:44.340> malware<00:06:44.940> so<00:06:45.720> you<00:06:45.960> know<00:06:46.080> don't<00:06:46.259> put<00:06:46.560> your<00:06:47.039> uh 00:06:47.629 --> 00:06:47.639 align:start position:0% of malware so you know don't put your uh 00:06:47.639 --> 00:06:50.809 align:start position:0% of malware so you know don't put your uh don't<00:06:47.940> put<00:06:48.240> Main<00:06:48.479> in<00:06:48.840> developer<00:06:49.319> mode<00:06:49.819> and 00:06:50.809 --> 00:06:50.819 align:start position:0% don't put Main in developer mode and 00:06:50.819 --> 00:06:51.650 align:start position:0% don't put Main in developer mode and we're<00:06:51.060> just<00:06:51.240> going<00:06:51.360> to<00:06:51.419> go<00:06:51.539> through 00:06:51.650 --> 00:06:51.660 align:start position:0% we're just going to go through 00:06:51.660 --> 00:06:53.809 align:start position:0% we're just going to go through onboarding<00:06:52.199> here<00:06:52.380> super<00:06:52.560> quickly 00:06:53.809 --> 00:06:53.819 align:start position:0% onboarding here super quickly 00:06:53.819 --> 00:07:00.610 align:start position:0% onboarding here super quickly foreign 00:07:00.610 --> 00:07:00.620 align:start position:0% 00:07:00.620 --> 00:07:12.529 align:start position:0% for<00:07:01.620> that 00:07:12.529 --> 00:07:12.539 align:start position:0% 00:07:12.539 --> 00:07:15.469 align:start position:0% and<00:07:13.080> Wi-Fi<00:07:13.380> permitting<00:07:14.039> we<00:07:14.880> should<00:07:15.120> be<00:07:15.240> good 00:07:15.469 --> 00:07:15.479 align:start position:0% and Wi-Fi permitting we should be good 00:07:15.479 --> 00:07:16.909 align:start position:0% and Wi-Fi permitting we should be good to<00:07:15.660> go<00:07:15.720> okay<00:07:16.020> yes 00:07:16.909 --> 00:07:16.919 align:start position:0% to go okay yes 00:07:16.919 --> 00:07:18.890 align:start position:0% to go okay yes all<00:07:17.280> right<00:07:17.460> so<00:07:17.940> now<00:07:18.060> I've<00:07:18.240> set<00:07:18.419> up<00:07:18.539> a<00:07:18.720> version 00:07:18.890 --> 00:07:18.900 align:start position:0% all right so now I've set up a version 00:07:18.900 --> 00:07:21.170 align:start position:0% all right so now I've set up a version of<00:07:19.139> flask<00:07:19.380> and<00:07:19.620> so<00:07:19.800> the<00:07:19.979> only<00:07:20.099> thing<00:07:20.340> uh<00:07:20.880> you'll 00:07:21.170 --> 00:07:21.180 align:start position:0% of flask and so the only thing uh you'll 00:07:21.180 --> 00:07:22.850 align:start position:0% of flask and so the only thing uh you'll notice<00:07:21.479> that's<00:07:21.840> like<00:07:22.139> immediately<00:07:22.620> different 00:07:22.850 --> 00:07:22.860 align:start position:0% notice that's like immediately different 00:07:22.860 --> 00:07:24.409 align:start position:0% notice that's like immediately different with<00:07:23.160> flask<00:07:23.460> is<00:07:23.639> that<00:07:23.819> the<00:07:23.940> onboarding<00:07:24.300> is 00:07:24.409 --> 00:07:24.419 align:start position:0% with flask is that the onboarding is 00:07:24.419 --> 00:07:25.969 align:start position:0% with flask is that the onboarding is slightly<00:07:24.720> different<00:07:24.900> and<00:07:25.440> we<00:07:25.620> have<00:07:25.680> a<00:07:25.860> purple 00:07:25.969 --> 00:07:25.979 align:start position:0% slightly different and we have a purple 00:07:25.979 --> 00:07:28.129 align:start position:0% slightly different and we have a purple Fox<00:07:26.280> to<00:07:26.580> distinguish<00:07:27.060> it<00:07:27.240> from<00:07:27.479> the<00:07:27.780> uh 00:07:28.129 --> 00:07:28.139 align:start position:0% Fox to distinguish it from the uh 00:07:28.139 --> 00:07:30.710 align:start position:0% Fox to distinguish it from the uh regular<00:07:28.800> Orange<00:07:29.460> Box 00:07:30.710 --> 00:07:30.720 align:start position:0% regular Orange Box 00:07:30.720 --> 00:07:35.390 align:start position:0% regular Orange Box and<00:07:31.680> uh<00:07:32.580> the<00:07:32.880> next<00:07:33.000> thing<00:07:33.240> we're<00:07:33.840> gonna<00:07:34.020> do<00:07:34.740> is 00:07:35.390 --> 00:07:35.400 align:start position:0% and uh the next thing we're gonna do is 00:07:35.400 --> 00:07:37.790 align:start position:0% and uh the next thing we're gonna do is I've<00:07:35.699> already<00:07:35.940> done<00:07:36.180> this<00:07:36.479> but<00:07:36.960> uh<00:07:37.500> the<00:07:37.680> next 00:07:37.790 --> 00:07:37.800 align:start position:0% I've already done this but uh the next 00:07:37.800 --> 00:07:39.830 align:start position:0% I've already done this but uh the next step<00:07:37.979> is<00:07:38.220> to<00:07:38.639> create<00:07:39.240> a<00:07:39.479> new<00:07:39.539> GitHub 00:07:39.830 --> 00:07:39.840 align:start position:0% step is to create a new GitHub 00:07:39.840 --> 00:07:43.010 align:start position:0% step is to create a new GitHub repository<00:07:40.500> using<00:07:41.400> the<00:07:41.639> template<00:07:42.360> snap<00:07:42.539> mono 00:07:43.010 --> 00:07:43.020 align:start position:0% repository using the template snap mono 00:07:43.020 --> 00:07:43.909 align:start position:0% repository using the template snap mono repo 00:07:43.909 --> 00:07:43.919 align:start position:0% repo 00:07:43.919 --> 00:07:47.050 align:start position:0% repo so<00:07:44.699> this<00:07:45.000> uh<00:07:45.360> monorepo<00:07:46.020> is<00:07:46.139> as<00:07:46.380> a<00:07:46.620> template 00:07:47.050 --> 00:07:47.060 align:start position:0% so this uh monorepo is as a template 00:07:47.060 --> 00:07:51.469 align:start position:0% so this uh monorepo is as a template that<00:07:48.060> contains<00:07:48.479> two<00:07:48.660> things<00:07:48.919> a<00:07:49.919> uh<00:07:50.340> two<00:07:50.699> or<00:07:50.880> two 00:07:51.469 --> 00:07:51.479 align:start position:0% that contains two things a uh two or two 00:07:51.479 --> 00:07:53.450 align:start position:0% that contains two things a uh two or two sub-repositories<00:07:52.319> or<00:07:52.500> packages<00:07:52.800> a<00:07:53.099> website 00:07:53.450 --> 00:07:53.460 align:start position:0% sub-repositories or packages a website 00:07:53.460 --> 00:07:56.570 align:start position:0% sub-repositories or packages a website and<00:07:54.360> the<00:07:54.840> actual<00:07:55.080> snap<00:07:55.380> itself 00:07:56.570 --> 00:07:56.580 align:start position:0% and the actual snap itself 00:07:56.580 --> 00:07:59.150 align:start position:0% and the actual snap itself and<00:07:57.300> things<00:07:57.900> are<00:07:58.259> yeah<00:07:58.560> they're<00:07:58.919> kind<00:07:59.039> of 00:07:59.150 --> 00:07:59.160 align:start position:0% and things are yeah they're kind of 00:07:59.160 --> 00:08:00.469 align:start position:0% and things are yeah they're kind of loading 00:08:00.469 --> 00:08:00.479 align:start position:0% loading 00:08:00.479 --> 00:08:03.969 align:start position:0% loading um<00:08:00.539> but<00:08:01.500> um<00:08:01.560> once<00:08:02.220> you've<00:08:02.460> pulled<00:08:02.819> that<00:08:02.940> down 00:08:03.969 --> 00:08:03.979 align:start position:0% um but um once you've pulled that down 00:08:03.979 --> 00:08:07.210 align:start position:0% um but um once you've pulled that down uh<00:08:04.979> and<00:08:05.220> run<00:08:05.400> yarn<00:08:05.759> install 00:08:07.210 --> 00:08:07.220 align:start position:0% uh and run yarn install 00:08:07.220 --> 00:08:10.510 align:start position:0% uh and run yarn install we<00:08:08.220> can<00:08:08.340> see<00:08:08.580> here 00:08:10.510 --> 00:08:10.520 align:start position:0% we can see here 00:08:10.520 --> 00:08:13.670 align:start position:0% we can see here that<00:08:11.520> should<00:08:11.639> still<00:08:11.819> be<00:08:12.000> good<00:08:12.380> that<00:08:13.380> we<00:08:13.560> have 00:08:13.670 --> 00:08:13.680 align:start position:0% that should still be good that we have 00:08:13.680 --> 00:08:20.629 align:start position:0% that should still be good that we have in<00:08:13.860> our<00:08:14.039> packages 00:08:20.629 --> 00:08:20.639 align:start position:0% 00:08:20.639 --> 00:08:23.869 align:start position:0% we<00:08:21.000> have<00:08:21.120> the<00:08:21.240> website<00:08:21.720> and<00:08:22.560> the<00:08:22.740> snap 00:08:23.869 --> 00:08:23.879 align:start position:0% we have the website and the snap 00:08:23.879 --> 00:08:25.189 align:start position:0% we have the website and the snap and<00:08:24.240> I'm<00:08:24.360> just<00:08:24.479> going<00:08:24.599> to<00:08:24.660> make<00:08:24.780> sure<00:08:24.960> that 00:08:25.189 --> 00:08:25.199 align:start position:0% and I'm just going to make sure that 00:08:25.199 --> 00:08:26.930 align:start position:0% and I'm just going to make sure that we've<00:08:25.560> installed<00:08:26.160> and<00:08:26.280> everything<00:08:26.460> with<00:08:26.759> that 00:08:26.930 --> 00:08:26.940 align:start position:0% we've installed and everything with that 00:08:26.940 --> 00:08:28.010 align:start position:0% we've installed and everything with that is<00:08:27.060> good 00:08:28.010 --> 00:08:28.020 align:start position:0% is good 00:08:28.020 --> 00:08:30.650 align:start position:0% is good and<00:08:28.500> then<00:08:28.620> we're<00:08:28.860> gonna<00:08:29.120> kick<00:08:30.120> things<00:08:30.300> off<00:08:30.419> by 00:08:30.650 --> 00:08:30.660 align:start position:0% and then we're gonna kick things off by 00:08:30.660 --> 00:08:34.750 align:start position:0% and then we're gonna kick things off by running<00:08:30.780> yarn<00:08:31.139> start 00:08:34.750 --> 00:08:34.760 align:start position:0% 00:08:34.760 --> 00:08:37.070 align:start position:0% which<00:08:35.760> should<00:08:35.940> hopefully<00:08:36.240> not<00:08:36.539> need<00:08:36.719> too<00:08:36.899> much 00:08:37.070 --> 00:08:37.080 align:start position:0% which should hopefully not need too much 00:08:37.080 --> 00:08:38.990 align:start position:0% which should hopefully not need too much network<00:08:37.260> access<00:08:37.680> great 00:08:38.990 --> 00:08:39.000 align:start position:0% network access great 00:08:39.000 --> 00:08:40.430 align:start position:0% network access great thank<00:08:39.120> you 00:08:40.430 --> 00:08:40.440 align:start position:0% thank you 00:08:40.440 --> 00:08:44.050 align:start position:0% thank you and<00:08:41.159> so<00:08:41.399> this<00:08:41.940> is<00:08:42.180> the<00:08:42.719> uh<00:08:43.380> template<00:08:43.800> snap 00:08:44.050 --> 00:08:44.060 align:start position:0% and so this is the uh template snap 00:08:44.060 --> 00:08:47.570 align:start position:0% and so this is the uh template snap interface<00:08:45.140> and<00:08:46.140> so<00:08:46.500> you<00:08:46.680> see<00:08:46.800> we<00:08:47.040> have<00:08:47.160> it<00:08:47.279> we 00:08:47.570 --> 00:08:47.580 align:start position:0% interface and so you see we have it we 00:08:47.580 --> 00:08:49.490 align:start position:0% interface and so you see we have it we have<00:08:47.760> everything<00:08:47.880> hosted<00:08:48.300> on<00:08:48.420> localhost<00:08:48.839> and 00:08:49.490 --> 00:08:49.500 align:start position:0% have everything hosted on localhost and 00:08:49.500 --> 00:08:51.650 align:start position:0% have everything hosted on localhost and the<00:08:49.680> first<00:08:49.740> thing<00:08:49.920> we<00:08:50.100> need<00:08:50.220> to<00:08:50.339> do<00:08:50.459> is<00:08:51.120> uh 00:08:51.650 --> 00:08:51.660 align:start position:0% the first thing we need to do is uh 00:08:51.660 --> 00:08:54.230 align:start position:0% the first thing we need to do is uh connect<00:08:51.839> to<00:08:52.080> our<00:08:52.200> snap 00:08:54.230 --> 00:08:54.240 align:start position:0% connect to our snap 00:08:54.240 --> 00:08:56.630 align:start position:0% connect to our snap and<00:08:54.720> so<00:08:54.899> first<00:08:55.200> uh<00:08:55.740> when<00:08:55.980> you<00:08:56.100> install<00:08:56.220> a<00:08:56.459> snap 00:08:56.630 --> 00:08:56.640 align:start position:0% and so first uh when you install a snap 00:08:56.640 --> 00:08:59.030 align:start position:0% and so first uh when you install a snap you<00:08:56.880> get<00:08:57.000> a<00:08:57.120> permission<00:08:57.360> request<00:08:57.779> uh<00:08:58.560> from<00:08:58.800> the 00:08:59.030 --> 00:08:59.040 align:start position:0% you get a permission request uh from the 00:08:59.040 --> 00:09:00.889 align:start position:0% you get a permission request uh from the website<00:08:59.399> that<00:08:59.640> that<00:08:59.880> made<00:09:00.120> the<00:09:00.300> request<00:09:00.600> and 00:09:00.889 --> 00:09:00.899 align:start position:0% website that that made the request and 00:09:00.899 --> 00:09:02.870 align:start position:0% website that that made the request and it's<00:09:01.080> basically<00:09:01.500> saying<00:09:01.860> hey<00:09:02.279> I<00:09:02.580> have<00:09:02.820> the 00:09:02.870 --> 00:09:02.880 align:start position:0% it's basically saying hey I have the 00:09:02.880 --> 00:09:06.290 align:start position:0% it's basically saying hey I have the website<00:09:03.240> at<00:09:03.540> this<00:09:03.779> URL<00:09:04.500> wants<00:09:04.980> to<00:09:05.040> talk<00:09:05.220> to<00:09:05.399> at 00:09:06.290 --> 00:09:06.300 align:start position:0% website at this URL wants to talk to at 00:09:06.300 --> 00:09:08.449 align:start position:0% website at this URL wants to talk to at this<00:09:06.540> particular<00:09:06.779> snap<00:09:07.140> and<00:09:08.040> during<00:09:08.220> local 00:09:08.449 --> 00:09:08.459 align:start position:0% this particular snap and during local 00:09:08.459 --> 00:09:10.670 align:start position:0% this particular snap and during local development<00:09:09.060> Snaps<00:09:09.600> are<00:09:09.720> just<00:09:09.899> identified<00:09:10.380> by 00:09:10.670 --> 00:09:10.680 align:start position:0% development Snaps are just identified by 00:09:10.680 --> 00:09:12.650 align:start position:0% development Snaps are just identified by the<00:09:10.920> localhost<00:09:11.339> URL<00:09:11.940> where<00:09:12.120> they're<00:09:12.240> hosted 00:09:12.650 --> 00:09:12.660 align:start position:0% the localhost URL where they're hosted 00:09:12.660 --> 00:09:16.370 align:start position:0% the localhost URL where they're hosted uh<00:09:13.440> just<00:09:13.620> out<00:09:13.860> of<00:09:14.100> uh<00:09:14.580> convenience 00:09:16.370 --> 00:09:16.380 align:start position:0% uh just out of uh convenience 00:09:16.380 --> 00:09:18.650 align:start position:0% uh just out of uh convenience and<00:09:17.160> once<00:09:17.580> we've<00:09:17.820> accepted<00:09:18.180> that<00:09:18.360> permission 00:09:18.650 --> 00:09:18.660 align:start position:0% and once we've accepted that permission 00:09:18.660 --> 00:09:21.530 align:start position:0% and once we've accepted that permission request<00:09:19.080> then<00:09:19.740> metamask<00:09:20.339> will<00:09:20.580> go<00:09:20.760> and<00:09:21.120> fetch 00:09:21.530 --> 00:09:21.540 align:start position:0% request then metamask will go and fetch 00:09:21.540 --> 00:09:23.509 align:start position:0% request then metamask will go and fetch the<00:09:21.959> snap<00:09:22.080> source<00:09:22.560> code<00:09:22.680> and<00:09:22.920> it's<00:09:23.040> manifest 00:09:23.509 --> 00:09:23.519 align:start position:0% the snap source code and it's manifest 00:09:23.519 --> 00:09:26.810 align:start position:0% the snap source code and it's manifest and<00:09:24.420> then<00:09:24.839> ask<00:09:25.140> for<00:09:25.320> its<00:09:25.680> permissions<00:09:26.040> and<00:09:26.640> so 00:09:26.810 --> 00:09:26.820 align:start position:0% and then ask for its permissions and so 00:09:26.820 --> 00:09:28.610 align:start position:0% and then ask for its permissions and so here<00:09:27.000> we<00:09:27.180> see<00:09:27.300> that<00:09:27.600> this<00:09:27.959> snap<00:09:28.140> again 00:09:28.610 --> 00:09:28.620 align:start position:0% here we see that this snap again 00:09:28.620 --> 00:09:30.889 align:start position:0% here we see that this snap again identified<00:09:29.100> by<00:09:29.399> its<00:09:29.580> localhost<00:09:29.880> URL<00:09:30.420> that 00:09:30.889 --> 00:09:30.899 align:start position:0% identified by its localhost URL that 00:09:30.899 --> 00:09:32.750 align:start position:0% identified by its localhost URL that wants<00:09:31.260> to<00:09:31.320> display<00:09:31.500> confirmations<00:09:32.220> inside<00:09:32.519> of 00:09:32.750 --> 00:09:32.760 align:start position:0% wants to display confirmations inside of 00:09:32.760 --> 00:09:35.090 align:start position:0% wants to display confirmations inside of metamask<00:09:33.240> and<00:09:34.019> we're<00:09:34.200> going<00:09:34.320> to<00:09:34.440> say<00:09:34.560> okay<00:09:34.800> to 00:09:35.090 --> 00:09:35.100 align:start position:0% metamask and we're going to say okay to 00:09:35.100 --> 00:09:36.290 align:start position:0% metamask and we're going to say okay to that 00:09:36.290 --> 00:09:36.300 align:start position:0% that 00:09:36.300 --> 00:09:39.650 align:start position:0% that and<00:09:36.839> to<00:09:37.080> try<00:09:37.200> out<00:09:37.380> this<00:09:37.620> functionality 00:09:39.650 --> 00:09:39.660 align:start position:0% and to try out this functionality 00:09:39.660 --> 00:09:41.690 align:start position:0% and to try out this functionality oops 00:09:41.690 --> 00:09:41.700 align:start position:0% oops 00:09:41.700 --> 00:09:49.570 align:start position:0% oops excellent 00:09:49.570 --> 00:09:49.580 align:start position:0% 00:09:49.580 --> 00:09:52.790 align:start position:0% that's<00:09:50.580> it<00:09:50.700> that's<00:09:51.000> it<00:09:51.240> folks<00:09:51.660> a<00:09:52.019> snap<00:09:52.260> a<00:09:52.560> snap 00:09:52.790 --> 00:09:52.800 align:start position:0% that's it that's it folks a snap a snap 00:09:52.800 --> 00:09:54.949 align:start position:0% that's it that's it folks a snap a snap everyone<00:09:53.100> get<00:09:53.580> a<00:09:53.760> look<00:09:53.880> get<00:09:54.180> a<00:09:54.360> look<00:09:54.480> it's 00:09:54.949 --> 00:09:54.959 align:start position:0% everyone get a look get a look it's 00:09:54.959 --> 00:09:57.650 align:start position:0% everyone get a look get a look it's showing<00:09:55.320> a<00:09:55.440> confirmation<00:09:55.920> oh<00:09:56.459> goodness<00:09:56.820> yes 00:09:57.650 --> 00:09:57.660 align:start position:0% showing a confirmation oh goodness yes 00:09:57.660 --> 00:09:59.030 align:start position:0% showing a confirmation oh goodness yes yes<00:09:57.839> yes 00:09:59.030 --> 00:09:59.040 align:start position:0% yes yes 00:09:59.040 --> 00:10:01.550 align:start position:0% yes yes okay<00:09:59.640> it's<00:10:00.000> real<00:10:00.180> yeah<00:10:00.600> yeah<00:10:00.779> so<00:10:01.140> so<00:10:01.320> what 00:10:01.550 --> 00:10:01.560 align:start position:0% okay it's real yeah yeah so so what 00:10:01.560 --> 00:10:03.769 align:start position:0% okay it's real yeah yeah so so what happened<00:10:01.680> here<00:10:01.980> uh<00:10:02.940> is<00:10:03.060> I<00:10:03.240> was<00:10:03.420> gonna<00:10:03.540> do<00:10:03.660> a 00:10:03.769 --> 00:10:03.779 align:start position:0% happened here uh is I was gonna do a 00:10:03.779 --> 00:10:05.030 align:start position:0% happened here uh is I was gonna do a little<00:10:03.899> I<00:10:04.200> was<00:10:04.380> going<00:10:04.500> to<00:10:04.620> mess<00:10:04.680> around<00:10:04.860> with 00:10:05.030 --> 00:10:05.040 align:start position:0% little I was going to mess around with 00:10:05.040 --> 00:10:07.130 align:start position:0% little I was going to mess around with this<00:10:05.220> notification<00:10:05.700> a<00:10:05.940> little<00:10:06.060> bit<00:10:06.240> but<00:10:06.600> uh<00:10:06.959> or 00:10:07.130 --> 00:10:07.140 align:start position:0% this notification a little bit but uh or 00:10:07.140 --> 00:10:08.690 align:start position:0% this notification a little bit but uh or confirmation<00:10:07.620> rather<00:10:07.920> but<00:10:08.399> we're<00:10:08.459> not<00:10:08.580> gonna 00:10:08.690 --> 00:10:08.700 align:start position:0% confirmation rather but we're not gonna 00:10:08.700 --> 00:10:10.610 align:start position:0% confirmation rather but we're not gonna do<00:10:08.820> that<00:10:09.000> so<00:10:09.420> this<00:10:09.600> is<00:10:09.720> just<00:10:09.899> a<00:10:10.140> dummy 00:10:10.610 --> 00:10:10.620 align:start position:0% do that so this is just a dummy 00:10:10.620 --> 00:10:12.769 align:start position:0% do that so this is just a dummy notification<00:10:11.100> for<00:10:11.399> display<00:10:11.580> purposes<00:10:12.180> and 00:10:12.769 --> 00:10:12.779 align:start position:0% notification for display purposes and 00:10:12.779 --> 00:10:14.090 align:start position:0% notification for display purposes and we're<00:10:12.959> gonna<00:10:13.080> skip<00:10:13.320> right<00:10:13.560> to<00:10:13.680> the<00:10:13.800> source 00:10:14.090 --> 00:10:14.100 align:start position:0% we're gonna skip right to the source 00:10:14.100 --> 00:10:15.949 align:start position:0% we're gonna skip right to the source code<00:10:14.279> and<00:10:14.700> look<00:10:14.880> at<00:10:15.000> like<00:10:15.240> what<00:10:15.480> is<00:10:15.600> going<00:10:15.779> on 00:10:15.949 --> 00:10:15.959 align:start position:0% code and look at like what is going on 00:10:15.959 --> 00:10:18.230 align:start position:0% code and look at like what is going on and<00:10:16.440> what<00:10:16.620> is<00:10:16.740> the<00:10:16.860> anatomy<00:10:17.279> of<00:10:17.399> these<00:10:17.580> things 00:10:18.230 --> 00:10:18.240 align:start position:0% and what is the anatomy of these things 00:10:18.240 --> 00:10:19.790 align:start position:0% and what is the anatomy of these things and<00:10:18.660> we're<00:10:18.779> going<00:10:19.019> to<00:10:19.080> reject<00:10:19.320> that<00:10:19.560> and 00:10:19.790 --> 00:10:19.800 align:start position:0% and we're going to reject that and 00:10:19.800 --> 00:10:21.290 align:start position:0% and we're going to reject that and that's<00:10:19.920> totally<00:10:20.279> fine 00:10:21.290 --> 00:10:21.300 align:start position:0% that's totally fine 00:10:21.300 --> 00:10:25.190 align:start position:0% that's totally fine uh<00:10:22.380> uh<00:10:22.560> and<00:10:22.680> so<00:10:22.860> if<00:10:22.980> we<00:10:23.100> go<00:10:23.279> in<00:10:23.459> back<00:10:23.700> here 00:10:25.190 --> 00:10:25.200 align:start position:0% uh uh and so if we go in back here 00:10:25.200 --> 00:10:30.110 align:start position:0% uh uh and so if we go in back here uh<00:10:26.100> and<00:10:26.339> if<00:10:26.580> we<00:10:26.760> look<00:10:27.120> at<00:10:27.540> uh<00:10:29.040> see<00:10:29.640> we<00:10:29.940> have 00:10:30.110 --> 00:10:30.120 align:start position:0% uh and if we look at uh see we have 00:10:30.120 --> 00:10:33.410 align:start position:0% uh and if we look at uh see we have packages<00:10:30.860> snap<00:10:31.860> we<00:10:32.279> have<00:10:32.399> you<00:10:32.700> see<00:10:32.880> we<00:10:33.300> have 00:10:33.410 --> 00:10:33.420 align:start position:0% packages snap we have you see we have 00:10:33.420 --> 00:10:36.050 align:start position:0% packages snap we have you see we have like<00:10:33.660> in<00:10:33.899> the<00:10:34.019> snap<00:10:34.260> package<00:10:34.680> uh<00:10:35.640> there's<00:10:35.820> like 00:10:36.050 --> 00:10:36.060 align:start position:0% like in the snap package uh there's like 00:10:36.060 --> 00:10:37.910 align:start position:0% like in the snap package uh there's like some<00:10:36.240> regular<00:10:36.540> like<00:10:36.839> npm<00:10:37.320> stuff<00:10:37.620> going 00:10:37.910 --> 00:10:37.920 align:start position:0% some regular like npm stuff going 00:10:37.920 --> 00:10:40.610 align:start position:0% some regular like npm stuff going JavaScript<00:10:38.580> stuff<00:10:38.880> going<00:10:39.120> on<00:10:39.320> uh<00:10:40.320> but<00:10:40.500> you 00:10:40.610 --> 00:10:40.620 align:start position:0% JavaScript stuff going on uh but you 00:10:40.620 --> 00:10:42.410 align:start position:0% JavaScript stuff going on uh but you also<00:10:40.800> see<00:10:40.860> that<00:10:41.040> we<00:10:41.160> have<00:10:41.279> a<00:10:41.459> snap<00:10:41.640> config<00:10:42.120> and 00:10:42.410 --> 00:10:42.420 align:start position:0% also see that we have a snap config and 00:10:42.420 --> 00:10:44.690 align:start position:0% also see that we have a snap config and a<00:10:42.600> snap<00:10:42.720> manifest<00:10:43.260> and<00:10:43.860> then<00:10:43.980> a<00:10:44.160> source<00:10:44.459> file 00:10:44.690 --> 00:10:44.700 align:start position:0% a snap manifest and then a source file 00:10:44.700 --> 00:10:47.030 align:start position:0% a snap manifest and then a source file and<00:10:45.600> then<00:10:45.720> the<00:10:45.899> source<00:10:46.260> file<00:10:46.680> is<00:10:46.860> just 00:10:47.030 --> 00:10:47.040 align:start position:0% and then the source file is just 00:10:47.040 --> 00:10:48.889 align:start position:0% and then the source file is just index.ts 00:10:48.889 --> 00:10:48.899 align:start position:0% index.ts 00:10:48.899 --> 00:10:52.670 align:start position:0% index.ts and<00:10:49.500> so<00:10:50.100> looking<00:10:50.700> at<00:10:50.940> the<00:10:51.120> Manifest<00:10:51.540> here 00:10:52.670 --> 00:10:52.680 align:start position:0% and so looking at the Manifest here 00:10:52.680 --> 00:10:54.530 align:start position:0% and so looking at the Manifest here uh<00:10:53.579> you're<00:10:53.820> gonna<00:10:53.940> see<00:10:54.120> that<00:10:54.240> there's<00:10:54.360> a 00:10:54.530 --> 00:10:54.540 align:start position:0% uh you're gonna see that there's a 00:10:54.540 --> 00:10:56.090 align:start position:0% uh you're gonna see that there's a version<00:10:54.720> which<00:10:55.440> you<00:10:55.560> may<00:10:55.680> have<00:10:55.860> noticed 00:10:56.090 --> 00:10:56.100 align:start position:0% version which you may have noticed 00:10:56.100 --> 00:10:59.090 align:start position:0% version which you may have noticed matched<00:10:56.459> what<00:10:56.579> we<00:10:56.760> saw<00:10:57.000> in<00:10:57.360> the<00:10:57.540> application 00:10:59.090 --> 00:10:59.100 align:start position:0% matched what we saw in the application 00:10:59.100 --> 00:11:01.430 align:start position:0% matched what we saw in the application and<00:10:59.820> then<00:11:00.180> we<00:11:00.420> have<00:11:00.540> some<00:11:00.779> information<00:11:01.019> about 00:11:01.430 --> 00:11:01.440 align:start position:0% and then we have some information about 00:11:01.440 --> 00:11:05.329 align:start position:0% and then we have some information about the<00:11:01.740> source<00:11:02.160> so<00:11:02.279> a<00:11:02.459> sha<00:11:02.820> sum<00:11:03.060> of<00:11:03.779> the<00:11:03.899> bundle<00:11:04.339> uh 00:11:05.329 --> 00:11:05.339 align:start position:0% the source so a sha sum of the bundle uh 00:11:05.339 --> 00:11:08.030 align:start position:0% the source so a sha sum of the bundle uh and<00:11:05.880> uh<00:11:06.300> some<00:11:06.540> other<00:11:06.660> like<00:11:07.019> metadata<00:11:07.620> if<00:11:07.860> we 00:11:08.030 --> 00:11:08.040 align:start position:0% and uh some other like metadata if we 00:11:08.040 --> 00:11:11.269 align:start position:0% and uh some other like metadata if we were<00:11:08.220> to<00:11:08.399> publish<00:11:08.760> uh<00:11:09.480> the<00:11:09.720> snap<00:11:09.899> to<00:11:10.200> npm<00:11:10.620> which 00:11:11.269 --> 00:11:11.279 align:start position:0% were to publish uh the snap to npm which 00:11:11.279 --> 00:11:13.430 align:start position:0% were to publish uh the snap to npm which is<00:11:11.459> our<00:11:11.579> currently<00:11:12.000> supported<00:11:12.600> uh<00:11:13.260> like 00:11:13.430 --> 00:11:13.440 align:start position:0% is our currently supported uh like 00:11:13.440 --> 00:11:15.470 align:start position:0% is our currently supported uh like distribution<00:11:13.860> mechanism<00:11:14.339> and<00:11:14.880> we<00:11:15.180> have<00:11:15.240> plans 00:11:15.470 --> 00:11:15.480 align:start position:0% distribution mechanism and we have plans 00:11:15.480 --> 00:11:17.870 align:start position:0% distribution mechanism and we have plans for<00:11:15.720> others<00:11:16.079> and<00:11:16.860> then<00:11:16.980> finally<00:11:17.279> you<00:11:17.579> have<00:11:17.700> the 00:11:17.870 --> 00:11:17.880 align:start position:0% for others and then finally you have the 00:11:17.880 --> 00:11:21.110 align:start position:0% for others and then finally you have the permissions<00:11:18.300> here<00:11:18.600> and<00:11:19.320> snap<00:11:19.740> confirm<00:11:20.399> is<00:11:20.940> the 00:11:21.110 --> 00:11:21.120 align:start position:0% permissions here and snap confirm is the 00:11:21.120 --> 00:11:24.829 align:start position:0% permissions here and snap confirm is the actual<00:11:21.300> RPC<00:11:21.779> method<00:11:22.260> uh<00:11:22.860> that<00:11:23.160> gets<00:11:23.579> called<00:11:23.839> by 00:11:24.829 --> 00:11:24.839 align:start position:0% actual RPC method uh that gets called by 00:11:24.839 --> 00:11:26.750 align:start position:0% actual RPC method uh that gets called by the<00:11:25.019> snap<00:11:25.260> in<00:11:25.920> order<00:11:26.100> to<00:11:26.339> display<00:11:26.459> a 00:11:26.750 --> 00:11:26.760 align:start position:0% the snap in order to display a 00:11:26.760 --> 00:11:29.030 align:start position:0% the snap in order to display a confirmation<00:11:27.240> inside<00:11:27.600> of<00:11:27.899> metamask 00:11:29.030 --> 00:11:29.040 align:start position:0% confirmation inside of metamask 00:11:29.040 --> 00:11:30.590 align:start position:0% confirmation inside of metamask and<00:11:29.519> if<00:11:29.640> we<00:11:29.820> actually<00:11:29.940> look<00:11:30.180> at<00:11:30.300> the<00:11:30.420> snap 00:11:30.590 --> 00:11:30.600 align:start position:0% and if we actually look at the snap 00:11:30.600 --> 00:11:34.130 align:start position:0% and if we actually look at the snap source<00:11:31.019> code<00:11:31.459> you<00:11:32.459> see<00:11:32.640> here<00:11:33.060> that<00:11:33.360> it<00:11:33.540> exports 00:11:34.130 --> 00:11:34.140 align:start position:0% source code you see here that it exports 00:11:34.140 --> 00:11:37.970 align:start position:0% source code you see here that it exports a<00:11:34.680> this<00:11:35.100> on<00:11:35.579> RPC<00:11:36.180> request<00:11:36.660> uh<00:11:37.620> Handler 00:11:37.970 --> 00:11:37.980 align:start position:0% a this on RPC request uh Handler 00:11:37.980 --> 00:11:38.889 align:start position:0% a this on RPC request uh Handler function 00:11:38.889 --> 00:11:38.899 align:start position:0% function 00:11:38.899 --> 00:11:42.530 align:start position:0% function uh<00:11:39.899> and<00:11:40.440> uh<00:11:41.220> basically<00:11:41.640> the<00:11:41.820> way<00:11:41.940> that<00:11:42.120> looks 00:11:42.530 --> 00:11:42.540 align:start position:0% uh and uh basically the way that looks 00:11:42.540 --> 00:11:45.590 align:start position:0% uh and uh basically the way that looks the<00:11:42.899> way<00:11:43.079> that<00:11:43.260> looks<00:11:43.680> from<00:11:44.640> inside<00:11:45.000> of<00:11:45.420> the 00:11:45.590 --> 00:11:45.600 align:start position:0% the way that looks from inside of the 00:11:45.600 --> 00:11:47.930 align:start position:0% the way that looks from inside of the website<00:11:46.019> so<00:11:46.320> this<00:11:46.560> is<00:11:46.680> a<00:11:46.980> file<00:11:47.160> from<00:11:47.399> inside<00:11:47.700> of 00:11:47.930 --> 00:11:47.940 align:start position:0% website so this is a file from inside of 00:11:47.940 --> 00:11:49.069 align:start position:0% website so this is a file from inside of the<00:11:48.060> website 00:11:49.069 --> 00:11:49.079 align:start position:0% the website 00:11:49.079 --> 00:11:51.949 align:start position:0% the website uh<00:11:49.860> you<00:11:50.040> will<00:11:50.220> call<00:11:50.459> this<00:11:50.700> it's<00:11:50.940> an<00:11:51.120> RPC<00:11:51.540> method 00:11:51.949 --> 00:11:51.959 align:start position:0% uh you will call this it's an RPC method 00:11:51.959 --> 00:11:55.550 align:start position:0% uh you will call this it's an RPC method inside<00:11:52.320> of<00:11:52.620> an<00:11:52.740> RPC<00:11:53.160> method<00:11:53.579> uh<00:11:54.300> so<00:11:54.540> you<00:11:54.720> have<00:11:54.959> a 00:11:55.550 --> 00:11:55.560 align:start position:0% inside of an RPC method uh so you have a 00:11:55.560 --> 00:11:58.069 align:start position:0% inside of an RPC method uh so you have a wallet<00:11:55.980> invoke<00:11:56.279> snap<00:11:56.640> and<00:11:57.480> then<00:11:57.540> you<00:11:57.720> pass<00:11:57.899> it 00:11:58.069 --> 00:11:58.079 align:start position:0% wallet invoke snap and then you pass it 00:11:58.079 --> 00:11:59.949 align:start position:0% wallet invoke snap and then you pass it the<00:11:58.260> ID<00:11:58.380> of<00:11:58.620> the<00:11:58.740> snap<00:11:58.920> and<00:11:59.279> then<00:11:59.399> the<00:11:59.579> request 00:11:59.949 --> 00:11:59.959 align:start position:0% the ID of the snap and then the request 00:11:59.959 --> 00:12:03.110 align:start position:0% the ID of the snap and then the request that<00:12:00.959> you<00:12:01.079> want<00:12:01.200> to<00:12:01.260> pass<00:12:01.440> to<00:12:01.680> it<00:12:01.920> and<00:12:02.880> you<00:12:03.000> see 00:12:03.110 --> 00:12:03.120 align:start position:0% that you want to pass to it and you see 00:12:03.120 --> 00:12:04.610 align:start position:0% that you want to pass to it and you see that<00:12:03.240> the<00:12:03.420> method<00:12:03.660> is<00:12:03.779> hello 00:12:04.610 --> 00:12:04.620 align:start position:0% that the method is hello 00:12:04.620 --> 00:12:06.769 align:start position:0% that the method is hello if<00:12:05.040> we<00:12:05.160> go<00:12:05.339> back<00:12:05.519> to<00:12:05.640> the<00:12:05.760> snap<00:12:05.940> that<00:12:06.420> is<00:12:06.540> the 00:12:06.769 --> 00:12:06.779 align:start position:0% if we go back to the snap that is the 00:12:06.779 --> 00:12:09.230 align:start position:0% if we go back to the snap that is the only<00:12:06.959> method<00:12:07.920> that<00:12:08.100> we<00:12:08.220> support<00:12:08.399> and<00:12:09.060> that 00:12:09.230 --> 00:12:09.240 align:start position:0% only method that we support and that 00:12:09.240 --> 00:12:11.449 align:start position:0% only method that we support and that just<00:12:09.420> causes<00:12:09.839> this<00:12:10.260> uh<00:12:10.560> confirmation<00:12:11.160> to<00:12:11.339> be 00:12:11.449 --> 00:12:11.459 align:start position:0% just causes this uh confirmation to be 00:12:11.459 --> 00:12:12.889 align:start position:0% just causes this uh confirmation to be displayed 00:12:12.889 --> 00:12:12.899 align:start position:0% displayed 00:12:12.899 --> 00:12:16.490 align:start position:0% displayed now<00:12:13.680> if<00:12:14.040> things<00:12:14.279> uh<00:12:15.240> like<00:12:15.660> continue<00:12:15.839> working<00:12:16.260> a 00:12:16.490 --> 00:12:16.500 align:start position:0% now if things uh like continue working a 00:12:16.500 --> 00:12:17.569 align:start position:0% now if things uh like continue working a little<00:12:16.620> bit<00:12:16.740> better<00:12:16.860> than<00:12:17.160> they<00:12:17.339> were<00:12:17.399> doing 00:12:17.569 --> 00:12:17.579 align:start position:0% little bit better than they were doing 00:12:17.579 --> 00:12:19.730 align:start position:0% little bit better than they were doing some<00:12:17.820> minutes<00:12:18.000> ago<00:12:18.420> uh<00:12:19.019> we're<00:12:19.260> going<00:12:19.440> to<00:12:19.560> take 00:12:19.730 --> 00:12:19.740 align:start position:0% some minutes ago uh we're going to take 00:12:19.740 --> 00:12:22.850 align:start position:0% some minutes ago uh we're going to take this<00:12:20.540> uh<00:12:21.540> snap<00:12:21.779> and<00:12:22.140> turn<00:12:22.260> it<00:12:22.440> into<00:12:22.560> a 00:12:22.850 --> 00:12:22.860 align:start position:0% this uh snap and turn it into a 00:12:22.860 --> 00:12:25.190 align:start position:0% this uh snap and turn it into a transaction<00:12:23.399> Insight<00:12:24.000> snap 00:12:25.190 --> 00:12:25.200 align:start position:0% transaction Insight snap 00:12:25.200 --> 00:12:27.769 align:start position:0% transaction Insight snap and<00:12:25.860> if<00:12:26.220> we 00:12:27.769 --> 00:12:27.779 align:start position:0% and if we 00:12:27.779 --> 00:12:30.170 align:start position:0% and if we briefly<00:12:28.680> return 00:12:30.170 --> 00:12:30.180 align:start position:0% briefly return 00:12:30.180 --> 00:12:32.329 align:start position:0% briefly return here<00:12:30.720> so<00:12:31.200> we've<00:12:31.800> basically<00:12:32.040> we've 00:12:32.329 --> 00:12:32.339 align:start position:0% here so we've basically we've 00:12:32.339 --> 00:12:33.650 align:start position:0% here so we've basically we've demonstrated<00:12:32.760> like<00:12:33.000> we've<00:12:33.180> gotten<00:12:33.420> a<00:12:33.540> snap 00:12:33.650 --> 00:12:33.660 align:start position:0% demonstrated like we've gotten a snap 00:12:33.660 --> 00:12:35.389 align:start position:0% demonstrated like we've gotten a snap running<00:12:33.899> and<00:12:34.500> now<00:12:34.800> it's<00:12:34.920> time<00:12:35.100> to<00:12:35.279> like 00:12:35.389 --> 00:12:35.399 align:start position:0% running and now it's time to like 00:12:35.399 --> 00:12:38.870 align:start position:0% running and now it's time to like replace<00:12:35.720> its<00:12:36.720> confirmation<00:12:37.320> permission<00:12:37.880> with 00:12:38.870 --> 00:12:38.880 align:start position:0% replace its confirmation permission with 00:12:38.880 --> 00:12:41.569 align:start position:0% replace its confirmation permission with this<00:12:39.180> uh<00:12:39.720> transaction<00:12:40.140> Insight<00:12:40.680> permission 00:12:41.569 --> 00:12:41.579 align:start position:0% this uh transaction Insight permission 00:12:41.579 --> 00:12:44.629 align:start position:0% this uh transaction Insight permission and<00:12:42.300> all<00:12:42.480> that<00:12:42.720> this<00:12:43.139> permission<00:12:43.440> does<00:12:43.800> is<00:12:44.279> it 00:12:44.629 --> 00:12:44.639 align:start position:0% and all that this permission does is it 00:12:44.639 --> 00:12:48.170 align:start position:0% and all that this permission does is it tells<00:12:45.060> metamask<00:12:45.800> uh<00:12:46.800> that<00:12:47.040> like<00:12:47.220> oh<00:12:47.519> this<00:12:48.000> snap 00:12:48.170 --> 00:12:48.180 align:start position:0% tells metamask uh that like oh this snap 00:12:48.180 --> 00:12:52.430 align:start position:0% tells metamask uh that like oh this snap wants<00:12:48.779> to<00:12:49.019> provide<00:12:49.980> uh<00:12:50.639> transaction<00:12:51.000> insights 00:12:52.430 --> 00:12:52.440 align:start position:0% wants to provide uh transaction insights 00:12:52.440 --> 00:12:57.710 align:start position:0% wants to provide uh transaction insights uh<00:12:53.220> and<00:12:53.519> in<00:12:53.700> order<00:12:53.880> to<00:12:54.860> uh<00:12:55.860> do<00:12:56.820> so 00:12:57.710 --> 00:12:57.720 align:start position:0% uh and in order to uh do so 00:12:57.720 --> 00:13:00.110 align:start position:0% uh and in order to uh do so we're<00:12:58.320> just<00:12:58.560> gonna<00:12:58.680> nuke<00:12:59.100> the<00:12:59.639> contents<00:13:00.060> of 00:13:00.110 --> 00:13:00.120 align:start position:0% we're just gonna nuke the contents of 00:13:00.120 --> 00:13:02.269 align:start position:0% we're just gonna nuke the contents of this<00:13:00.300> file 00:13:02.269 --> 00:13:02.279 align:start position:0% this file 00:13:02.279 --> 00:13:03.949 align:start position:0% this file and<00:13:02.700> then<00:13:02.820> we're<00:13:02.940> going<00:13:03.060> to<00:13:03.180> go<00:13:03.360> ahead<00:13:03.600> and 00:13:03.949 --> 00:13:03.959 align:start position:0% and then we're going to go ahead and 00:13:03.959 --> 00:13:07.009 align:start position:0% and then we're going to go ahead and import<00:13:04.139> some<00:13:04.560> other<00:13:04.740> stuff 00:13:07.009 --> 00:13:07.019 align:start position:0% 00:13:07.019 --> 00:13:09.769 align:start position:0% namely<00:13:07.620> on<00:13:07.860> transaction<00:13:08.279> Handler 00:13:09.769 --> 00:13:09.779 align:start position:0% namely on transaction Handler 00:13:09.779 --> 00:13:12.129 align:start position:0% namely on transaction Handler we<00:13:10.380> are<00:13:10.500> going<00:13:10.800> to 00:13:12.129 --> 00:13:12.139 align:start position:0% we are going to 00:13:12.139 --> 00:13:14.829 align:start position:0% we are going to uh<00:13:13.139> add 00:13:14.829 --> 00:13:14.839 align:start position:0% uh add 00:13:14.839 --> 00:13:20.690 align:start position:0% uh add a<00:13:15.839> package<00:13:16.680> called<00:13:17.100> uh<00:13:18.060> utils 00:13:20.690 --> 00:13:20.700 align:start position:0% a package called uh utils 00:13:20.700 --> 00:13:22.490 align:start position:0% a package called uh utils and<00:13:21.180> we're<00:13:21.360> going<00:13:21.540> to<00:13:21.779> import<00:13:21.959> some<00:13:22.320> stuff 00:13:22.490 --> 00:13:22.500 align:start position:0% and we're going to import some stuff 00:13:22.500 --> 00:13:32.949 align:start position:0% and we're going to import some stuff from<00:13:22.740> that 00:13:32.949 --> 00:13:32.959 align:start position:0% 00:13:32.959 --> 00:13:36.710 align:start position:0% and<00:13:33.959> then<00:13:34.459> we<00:13:35.459> have 00:13:36.710 --> 00:13:36.720 align:start position:0% and then we have 00:13:36.720 --> 00:13:39.889 align:start position:0% and then we have this<00:13:37.320> Handler<00:13:37.680> that<00:13:37.980> we<00:13:38.100> need<00:13:38.220> to<00:13:38.399> specify<00:13:38.899> on 00:13:39.889 --> 00:13:39.899 align:start position:0% this Handler that we need to specify on 00:13:39.899 --> 00:13:41.690 align:start position:0% this Handler that we need to specify on transaction 00:13:41.690 --> 00:13:41.700 align:start position:0% transaction 00:13:41.700 --> 00:13:44.930 align:start position:0% transaction and<00:13:42.540> that<00:13:43.079> is<00:13:43.320> going<00:13:43.500> to<00:13:43.680> be 00:13:44.930 --> 00:13:44.940 align:start position:0% and that is going to be 00:13:44.940 --> 00:13:48.310 align:start position:0% and that is going to be foreign 00:13:48.310 --> 00:13:48.320 align:start position:0% 00:13:48.320 --> 00:13:51.290 align:start position:0% that<00:13:49.320> looks<00:13:49.620> something<00:13:49.740> like<00:13:50.100> this 00:13:51.290 --> 00:13:51.300 align:start position:0% that looks something like this 00:13:51.300 --> 00:13:53.269 align:start position:0% that looks something like this and<00:13:51.779> right<00:13:51.959> now<00:13:52.079> it's<00:13:52.380> a<00:13:52.560> sad<00:13:52.740> function 00:13:53.269 --> 00:13:53.279 align:start position:0% and right now it's a sad function 00:13:53.279 --> 00:13:55.550 align:start position:0% and right now it's a sad function because<00:13:53.940> it's<00:13:54.120> not<00:13:54.360> returning<00:13:54.899> at<00:13:55.260> what<00:13:55.440> it 00:13:55.550 --> 00:13:55.560 align:start position:0% because it's not returning at what it 00:13:55.560 --> 00:13:56.990 align:start position:0% because it's not returning at what it needs<00:13:55.800> to<00:13:55.860> return 00:13:56.990 --> 00:13:57.000 align:start position:0% needs to return 00:13:57.000 --> 00:14:00.170 align:start position:0% needs to return to<00:13:57.720> satisfy<00:13:58.200> its<00:13:58.500> type 00:14:00.170 --> 00:14:00.180 align:start position:0% to satisfy its type 00:14:00.180 --> 00:14:01.970 align:start position:0% to satisfy its type and<00:14:00.540> we're<00:14:00.660> just<00:14:00.899> going<00:14:01.019> to<00:14:01.079> return<00:14:01.260> some<00:14:01.680> like 00:14:01.970 --> 00:14:01.980 align:start position:0% and we're just going to return some like 00:14:01.980 --> 00:14:03.769 align:start position:0% and we're just going to return some like dummy 00:14:03.769 --> 00:14:03.779 align:start position:0% dummy 00:14:03.779 --> 00:14:06.590 align:start position:0% dummy uh<00:14:04.440> a<00:14:04.560> dummy<00:14:04.920> Trend<00:14:05.220> a 00:14:06.590 --> 00:14:06.600 align:start position:0% uh a dummy Trend a 00:14:06.600 --> 00:14:07.190 align:start position:0% uh a dummy Trend a um 00:14:07.190 --> 00:14:07.200 align:start position:0% um 00:14:07.200 --> 00:14:09.650 align:start position:0% um a dummy<00:14:07.980> insight<00:14:08.399> for<00:14:08.639> now 00:14:09.650 --> 00:14:09.660 align:start position:0% a dummy insight for now 00:14:09.660 --> 00:14:11.990 align:start position:0% a dummy insight for now and<00:14:10.079> I<00:14:10.380> think<00:14:10.440> we<00:14:10.680> also<00:14:10.860> need<00:14:11.040> it<00:14:11.220> to<00:14:11.399> be<00:14:11.459> async 00:14:11.990 --> 00:14:12.000 align:start position:0% and I think we also need it to be async 00:14:12.000 --> 00:14:13.190 align:start position:0% and I think we also need it to be async yes 00:14:13.190 --> 00:14:13.200 align:start position:0% yes 00:14:13.200 --> 00:14:14.269 align:start position:0% yes okay 00:14:14.269 --> 00:14:14.279 align:start position:0% okay 00:14:14.279 --> 00:14:16.370 align:start position:0% okay and<00:14:15.000> we're<00:14:15.300> also<00:14:15.600> just<00:14:15.779> going<00:14:15.899> to<00:14:15.959> add<00:14:16.200> a 00:14:16.370 --> 00:14:16.380 align:start position:0% and we're also just going to add a 00:14:16.380 --> 00:14:18.230 align:start position:0% and we're also just going to add a little<00:14:16.500> bit<00:14:16.620> of<00:14:16.740> validation<00:14:17.279> to<00:14:17.940> make<00:14:18.120> sure 00:14:18.230 --> 00:14:18.240 align:start position:0% little bit of validation to make sure 00:14:18.240 --> 00:14:20.210 align:start position:0% little bit of validation to make sure that<00:14:18.480> the<00:14:18.600> transaction<00:14:19.019> is<00:14:19.440> of<00:14:19.560> a<00:14:19.740> type<00:14:19.860> that 00:14:20.210 --> 00:14:20.220 align:start position:0% that the transaction is of a type that 00:14:20.220 --> 00:14:21.710 align:start position:0% that the transaction is of a type that we<00:14:20.339> can<00:14:20.459> understand<00:14:20.639> because<00:14:21.180> like<00:14:21.420> you<00:14:21.600> know 00:14:21.710 --> 00:14:21.720 align:start position:0% we can understand because like you know 00:14:21.720 --> 00:14:23.690 align:start position:0% we can understand because like you know we're<00:14:22.079> writing<00:14:22.440> a<00:14:22.620> specific<00:14:22.860> Insight<00:14:23.399> snap 00:14:23.690 --> 00:14:23.700 align:start position:0% we're writing a specific Insight snap 00:14:23.700 --> 00:14:25.850 align:start position:0% we're writing a specific Insight snap that<00:14:24.120> that<00:14:24.120> uses<00:14:24.660> our<00:14:24.959> particular<00:14:25.380> domain 00:14:25.850 --> 00:14:25.860 align:start position:0% that that uses our particular domain 00:14:25.860 --> 00:14:28.250 align:start position:0% that that uses our particular domain knowledge<00:14:26.279> and<00:14:26.880> so<00:14:27.180> we<00:14:27.660> need<00:14:27.779> the<00:14:27.959> transaction 00:14:28.250 --> 00:14:28.260 align:start position:0% knowledge and so we need the transaction 00:14:28.260 --> 00:14:32.990 align:start position:0% knowledge and so we need the transaction to<00:14:28.500> look<00:14:28.740> at<00:14:29.399> a<00:14:29.639> particular<00:14:29.940> way 00:14:32.990 --> 00:14:33.000 align:start position:0% 00:14:33.000 --> 00:14:37.310 align:start position:0% uh<00:14:33.959> so<00:14:34.380> if<00:14:34.680> it's<00:14:34.800> not<00:14:35.040> an<00:14:35.220> object<00:14:35.519> or 00:14:37.310 --> 00:14:37.320 align:start position:0% uh so if it's not an object or 00:14:37.320 --> 00:14:40.629 align:start position:0% uh so if it's not an object or if<00:14:37.740> it<00:14:38.040> doesn't<00:14:38.279> have 00:14:40.629 --> 00:14:40.639 align:start position:0% if it doesn't have 00:14:40.639 --> 00:14:43.550 align:start position:0% if it doesn't have the<00:14:41.639> property<00:14:42.120> data 00:14:43.550 --> 00:14:43.560 align:start position:0% the property data 00:14:43.560 --> 00:14:48.170 align:start position:0% the property data or<00:14:44.399> if 00:14:48.170 --> 00:14:48.180 align:start position:0% 00:14:48.180 --> 00:14:51.850 align:start position:0% the<00:14:48.660> data<00:14:48.899> is<00:14:49.079> not<00:14:49.260> a<00:14:49.620> string 00:14:51.850 --> 00:14:51.860 align:start position:0% the data is not a string 00:14:51.860 --> 00:14:54.050 align:start position:0% the data is not a string then<00:14:52.860> we're<00:14:53.040> going<00:14:53.220> to<00:14:53.279> say<00:14:53.459> oh<00:14:53.760> actually 00:14:54.050 --> 00:14:54.060 align:start position:0% then we're going to say oh actually 00:14:54.060 --> 00:14:56.350 align:start position:0% then we're going to say oh actually we're<00:14:54.360> going<00:14:54.480> to<00:14:54.540> do<00:14:54.660> this<00:14:54.959> first 00:14:56.350 --> 00:14:56.360 align:start position:0% we're going to do this first 00:14:56.360 --> 00:15:09.889 align:start position:0% we're going to do this first oh<00:14:57.360> wait<00:14:57.540> no 00:15:09.889 --> 00:15:09.899 align:start position:0% 00:15:09.899 --> 00:15:21.170 align:start position:0% foreign 00:15:21.170 --> 00:15:21.180 align:start position:0% 00:15:21.180 --> 00:15:24.769 align:start position:0% and<00:15:21.839> then<00:15:21.959> we're<00:15:22.139> gonna<00:15:22.320> say 00:15:24.769 --> 00:15:24.779 align:start position:0% and then we're gonna say 00:15:24.779 --> 00:15:27.230 align:start position:0% and then we're gonna say we're<00:15:25.199> going<00:15:25.320> to<00:15:25.380> import<00:15:25.560> this 00:15:27.230 --> 00:15:27.240 align:start position:0% we're going to import this 00:15:27.240 --> 00:15:35.290 align:start position:0% we're going to import this we're<00:15:27.660> going<00:15:27.779> to<00:15:27.839> import<00:15:28.019> this 00:15:35.290 --> 00:15:35.300 align:start position:0% 00:15:35.300 --> 00:15:38.870 align:start position:0% a<00:15:36.300> little<00:15:36.600> warning<00:15:37.079> for<00:15:37.380> sanity<00:15:37.800> in<00:15:38.220> case<00:15:38.459> I 00:15:38.870 --> 00:15:38.880 align:start position:0% a little warning for sanity in case I 00:15:38.880 --> 00:15:40.850 align:start position:0% a little warning for sanity in case I make<00:15:39.300> any<00:15:39.480> typos<00:15:39.899> here 00:15:40.850 --> 00:15:40.860 align:start position:0% make any typos here 00:15:40.860 --> 00:15:49.100 align:start position:0% make any typos here foreign 00:15:49.100 --> 00:15:49.110 align:start position:0% 00:15:49.110 --> 00:15:52.269 align:start position:0% [Music] 00:15:52.269 --> 00:15:52.279 align:start position:0% 00:15:52.279 --> 00:15:54.769 align:start position:0% and<00:15:53.279> we're<00:15:53.459> gonna<00:15:53.579> hide<00:15:53.880> that<00:15:54.120> and<00:15:54.420> then<00:15:54.540> we 00:15:54.769 --> 00:15:54.779 align:start position:0% and we're gonna hide that and then we 00:15:54.779 --> 00:15:57.889 align:start position:0% and we're gonna hide that and then we need<00:15:54.899> to<00:15:55.019> make<00:15:55.260> some<00:15:55.500> modifications<00:15:56.720> on<00:15:57.720> the 00:15:57.889 --> 00:15:57.899 align:start position:0% need to make some modifications on the 00:15:57.899 --> 00:16:00.769 align:start position:0% need to make some modifications on the front<00:15:58.199> end<00:15:58.440> as<00:15:58.800> well 00:16:00.769 --> 00:16:00.779 align:start position:0% front end as well 00:16:00.779 --> 00:16:03.110 align:start position:0% front end as well uh<00:16:01.380> and<00:16:01.500> on<00:16:01.620> the<00:16:01.800> front<00:16:01.920> end<00:16:02.160> as<00:16:02.519> the<00:16:02.820> front<00:16:03.000> end 00:16:03.110 --> 00:16:03.120 align:start position:0% uh and on the front end as the front end 00:16:03.120 --> 00:16:06.590 align:start position:0% uh and on the front end as the front end is<00:16:03.360> just<00:16:03.600> a<00:16:03.899> react<00:16:04.699> application<00:16:05.699> written<00:16:06.480> in 00:16:06.590 --> 00:16:06.600 align:start position:0% is just a react application written in 00:16:06.600 --> 00:16:09.050 align:start position:0% is just a react application written in typescript<00:16:06.959> nothing<00:16:07.560> fancy<00:16:08.040> going<00:16:08.220> on<00:16:08.399> there 00:16:09.050 --> 00:16:09.060 align:start position:0% typescript nothing fancy going on there 00:16:09.060 --> 00:16:13.430 align:start position:0% typescript nothing fancy going on there uh<00:16:10.320> although<00:16:11.040> it<00:16:11.220> certainly<00:16:11.519> looks<00:16:11.820> fancy 00:16:13.430 --> 00:16:13.440 align:start position:0% uh although it certainly looks fancy 00:16:13.440 --> 00:16:17.449 align:start position:0% uh although it certainly looks fancy um<00:16:13.500> and<00:16:14.420> I'm<00:16:15.420> going<00:16:15.779> to<00:16:16.079> snag 00:16:17.449 --> 00:16:17.459 align:start position:0% um and I'm going to snag 00:16:17.459 --> 00:16:19.910 align:start position:0% um and I'm going to snag a<00:16:18.120> little<00:16:18.240> snippet<00:16:18.720> here<00:16:18.959> with<00:16:19.380> some<00:16:19.560> useful 00:16:19.910 --> 00:16:19.920 align:start position:0% a little snippet here with some useful 00:16:19.920 --> 00:16:21.590 align:start position:0% a little snippet here with some useful constants 00:16:21.590 --> 00:16:21.600 align:start position:0% constants 00:16:21.600 --> 00:16:24.110 align:start position:0% constants that<00:16:22.199> we<00:16:22.620> are<00:16:22.740> going<00:16:23.040> to 00:16:24.110 --> 00:16:24.120 align:start position:0% that we are going to 00:16:24.120 --> 00:16:26.930 align:start position:0% that we are going to use<00:16:24.779> because<00:16:25.320> right<00:16:25.980> now 00:16:26.930 --> 00:16:26.940 align:start position:0% use because right now 00:16:26.940 --> 00:16:30.170 align:start position:0% use because right now our<00:16:27.720> problem<00:16:27.899> is<00:16:28.380> that<00:16:28.920> uh<00:16:29.639> let's<00:16:29.820> see<00:16:30.000> where 00:16:30.170 --> 00:16:30.180 align:start position:0% our problem is that uh let's see where 00:16:30.180 --> 00:16:33.050 align:start position:0% our problem is that uh let's see where do<00:16:30.360> we<00:16:30.480> have<00:16:30.540> send<00:16:30.839> flow<00:16:31.279> when<00:16:32.279> we<00:16:32.459> click<00:16:32.820> on 00:16:33.050 --> 00:16:33.060 align:start position:0% do we have send flow when we click on 00:16:33.060 --> 00:16:34.490 align:start position:0% do we have send flow when we click on the 00:16:34.490 --> 00:16:34.500 align:start position:0% the 00:16:34.500 --> 00:16:35.329 align:start position:0% the um 00:16:35.329 --> 00:16:35.339 align:start position:0% um 00:16:35.339 --> 00:16:38.829 align:start position:0% um on<00:16:35.699> this<00:16:35.940> button<00:16:36.240> here<00:16:36.620> uh<00:16:37.620> it<00:16:37.860> is<00:16:37.980> going<00:16:38.279> to 00:16:38.829 --> 00:16:38.839 align:start position:0% on this button here uh it is going to 00:16:38.839 --> 00:16:41.449 align:start position:0% on this button here uh it is going to call<00:16:39.839> this<00:16:40.079> Handler<00:16:40.500> which<00:16:40.920> is<00:16:41.040> going<00:16:41.220> to<00:16:41.279> call 00:16:41.449 --> 00:16:41.459 align:start position:0% call this Handler which is going to call 00:16:41.459 --> 00:16:44.150 align:start position:0% call this Handler which is going to call Santa<00:16:41.699> hello<00:16:42.139> which<00:16:43.139> calls<00:16:43.920> this<00:16:43.980> hello 00:16:44.150 --> 00:16:44.160 align:start position:0% Santa hello which calls this hello 00:16:44.160 --> 00:16:45.710 align:start position:0% Santa hello which calls this hello method<00:16:44.579> and<00:16:44.759> we<00:16:44.820> don't<00:16:44.940> even<00:16:45.060> have<00:16:45.240> an<00:16:45.300> RPC 00:16:45.710 --> 00:16:45.720 align:start position:0% method and we don't even have an RPC 00:16:45.720 --> 00:16:47.150 align:start position:0% method and we don't even have an RPC Handler<00:16:46.079> anymore<00:16:46.199> so<00:16:46.560> that's<00:16:46.740> not<00:16:46.920> going<00:16:47.040> to 00:16:47.150 --> 00:16:47.160 align:start position:0% Handler anymore so that's not going to 00:16:47.160 --> 00:16:48.050 align:start position:0% Handler anymore so that's not going to work 00:16:48.050 --> 00:16:48.060 align:start position:0% work 00:16:48.060 --> 00:16:50.930 align:start position:0% work so<00:16:48.480> we<00:16:48.660> need<00:16:48.779> to<00:16:48.899> delete<00:16:49.019> that 00:16:50.930 --> 00:16:50.940 align:start position:0% so we need to delete that 00:16:50.940 --> 00:16:53.749 align:start position:0% so we need to delete that delete<00:16:51.480> this 00:16:53.749 --> 00:16:53.759 align:start position:0% delete this 00:16:53.759 --> 00:16:59.269 align:start position:0% delete this and<00:16:54.480> then<00:16:54.839> at<00:16:55.380> rather 00:16:59.269 --> 00:16:59.279 align:start position:0% 00:16:59.279 --> 00:17:01.069 align:start position:0% than<00:16:59.699> doing<00:16:59.940> that<00:17:00.180> we're<00:17:00.480> first<00:17:00.720> going<00:17:00.899> to 00:17:01.069 --> 00:17:01.079 align:start position:0% than doing that we're first going to 00:17:01.079 --> 00:17:03.050 align:start position:0% than doing that we're first going to grab<00:17:01.380> some<00:17:01.680> accounts<00:17:02.279> because<00:17:02.579> we<00:17:02.940> need 00:17:03.050 --> 00:17:03.060 align:start position:0% grab some accounts because we need 00:17:03.060 --> 00:17:05.030 align:start position:0% grab some accounts because we need access<00:17:03.300> to<00:17:03.600> the<00:17:03.720> user's<00:17:04.199> accounts<00:17:04.740> in<00:17:04.980> order 00:17:05.030 --> 00:17:05.040 align:start position:0% access to the user's accounts in order 00:17:05.040 --> 00:17:18.049 align:start position:0% access to the user's accounts in order to<00:17:05.160> send<00:17:05.400> a<00:17:05.579> transaction 00:17:18.049 --> 00:17:18.059 align:start position:0% 00:17:18.059 --> 00:17:20.809 align:start position:0% I<00:17:18.480> do<00:17:18.540> need<00:17:18.720> an<00:17:18.900> await<00:17:19.260> thank<00:17:19.559> you<00:17:19.740> sir 00:17:20.809 --> 00:17:20.819 align:start position:0% I do need an await thank you sir 00:17:20.819 --> 00:17:29.930 align:start position:0% I do need an await thank you sir foreign 00:17:29.930 --> 00:17:29.940 align:start position:0% 00:17:29.940 --> 00:17:32.690 align:start position:0% we're<00:17:30.419> just<00:17:30.600> going<00:17:30.720> to<00:17:30.780> throw<00:17:30.960> an<00:17:31.200> error 00:17:32.690 --> 00:17:32.700 align:start position:0% we're just going to throw an error 00:17:32.700 --> 00:17:36.770 align:start position:0% we're just going to throw an error thing<00:17:33.240> fail<00:17:33.840> to<00:17:34.200> get<00:17:34.380> accounts 00:17:36.770 --> 00:17:36.780 align:start position:0% thing fail to get accounts 00:17:36.780 --> 00:17:38.870 align:start position:0% thing fail to get accounts actually<00:17:37.140> that<00:17:37.440> should<00:17:37.620> even<00:17:37.919> request<00:17:38.400> if<00:17:38.700> it 00:17:38.870 --> 00:17:38.880 align:start position:0% actually that should even request if it 00:17:38.880 --> 00:17:41.810 align:start position:0% actually that should even request if it rejects<00:17:39.419> but<00:17:39.720> you<00:17:40.320> know<00:17:40.440> never<00:17:41.160> hurts<00:17:41.580> to<00:17:41.760> be 00:17:41.810 --> 00:17:41.820 align:start position:0% rejects but you know never hurts to be 00:17:41.820 --> 00:17:43.010 align:start position:0% rejects but you know never hurts to be defensive 00:17:43.010 --> 00:17:43.020 align:start position:0% defensive 00:17:43.020 --> 00:17:47.090 align:start position:0% defensive uh<00:17:43.919> and<00:17:44.280> then<00:17:44.520> once<00:17:45.299> we<00:17:45.419> have<00:17:45.539> done<00:17:45.780> that<00:17:46.140> we 00:17:47.090 --> 00:17:47.100 align:start position:0% uh and then once we have done that we 00:17:47.100 --> 00:17:49.970 align:start position:0% uh and then once we have done that we are<00:17:47.220> going<00:17:47.460> to<00:17:47.940> then<00:17:48.480> we<00:17:48.720> have<00:17:48.840> an<00:17:49.020> account<00:17:49.200> and 00:17:49.970 --> 00:17:49.980 align:start position:0% are going to then we have an account and 00:17:49.980 --> 00:17:52.130 align:start position:0% are going to then we have an account and then<00:17:50.520> we're<00:17:50.700> going<00:17:51.000> to<00:17:51.360> just<00:17:51.600> send<00:17:51.900> a 00:17:52.130 --> 00:17:52.140 align:start position:0% then we're going to just send a 00:17:52.140 --> 00:17:53.390 align:start position:0% then we're going to just send a transaction 00:17:53.390 --> 00:17:53.400 align:start position:0% transaction 00:17:53.400 --> 00:17:57.070 align:start position:0% transaction uh<00:17:54.360> and<00:17:54.960> we're<00:17:55.200> gonna<00:17:55.320> do<00:17:55.679> again 00:17:57.070 --> 00:17:57.080 align:start position:0% uh and we're gonna do again 00:17:57.080 --> 00:17:59.510 align:start position:0% uh and we're gonna do again method<00:17:58.080> East 00:17:59.510 --> 00:17:59.520 align:start position:0% method East 00:17:59.520 --> 00:18:02.150 align:start position:0% method East send<00:17:59.940> transaction 00:18:02.150 --> 00:18:02.160 align:start position:0% send transaction 00:18:02.160 --> 00:18:05.090 align:start position:0% send transaction we're<00:18:02.640> going<00:18:02.820> to<00:18:02.880> have<00:18:03.000> some<00:18:03.240> params 00:18:05.090 --> 00:18:05.100 align:start position:0% we're going to have some params 00:18:05.100 --> 00:18:07.730 align:start position:0% we're going to have some params that<00:18:05.520> should<00:18:05.700> be<00:18:05.820> recognizable<00:18:06.419> to<00:18:06.960> many<00:18:07.559> of 00:18:07.730 --> 00:18:07.740 align:start position:0% that should be recognizable to many of 00:18:07.740 --> 00:18:09.830 align:start position:0% that should be recognizable to many of the<00:18:07.919> fine<00:18:08.039> folks<00:18:08.460> in<00:18:08.580> this<00:18:08.700> room 00:18:09.830 --> 00:18:09.840 align:start position:0% the fine folks in this room 00:18:09.840 --> 00:18:11.750 align:start position:0% the fine folks in this room so<00:18:10.080> we<00:18:10.200> have<00:18:10.320> a<00:18:10.440> from<00:18:10.559> address 00:18:11.750 --> 00:18:11.760 align:start position:0% so we have a from address 00:18:11.760 --> 00:18:14.470 align:start position:0% so we have a from address the<00:18:12.299> to<00:18:12.539> address 00:18:14.470 --> 00:18:14.480 align:start position:0% the to address 00:18:14.480 --> 00:18:16.190 align:start position:0% the to address is 00:18:16.190 --> 00:18:16.200 align:start position:0% is 00:18:16.200 --> 00:18:19.510 align:start position:0% is going<00:18:16.799> to<00:18:17.100> be 00:18:19.510 --> 00:18:19.520 align:start position:0% going to be 00:18:19.520 --> 00:18:22.250 align:start position:0% going to be uh<00:18:20.520> the<00:18:20.760> address<00:18:20.880> of<00:18:21.179> a<00:18:21.360> contract<00:18:21.660> that<00:18:21.960> is<00:18:22.140> in 00:18:22.250 --> 00:18:22.260 align:start position:0% uh the address of a contract that is in 00:18:22.260 --> 00:18:24.950 align:start position:0% uh the address of a contract that is in fact<00:18:22.380> deployed<00:18:22.860> to<00:18:22.980> mainnet<00:18:23.460> but<00:18:24.179> that<00:18:24.780> will 00:18:24.950 --> 00:18:24.960 align:start position:0% fact deployed to mainnet but that will 00:18:24.960 --> 00:18:26.570 align:start position:0% fact deployed to mainnet but that will reject<00:18:25.260> any<00:18:25.559> transaction<00:18:26.039> that<00:18:26.460> we 00:18:26.570 --> 00:18:26.580 align:start position:0% reject any transaction that we 00:18:26.580 --> 00:18:28.730 align:start position:0% reject any transaction that we accidentally<00:18:27.059> sent<00:18:27.299> to<00:18:27.539> it<00:18:27.660> I<00:18:28.260> just<00:18:28.380> happen<00:18:28.559> to 00:18:28.730 --> 00:18:28.740 align:start position:0% accidentally sent to it I just happen to 00:18:28.740 --> 00:18:30.529 align:start position:0% accidentally sent to it I just happen to know<00:18:28.919> this<00:18:29.100> to<00:18:29.280> be<00:18:29.400> the<00:18:29.520> case 00:18:30.529 --> 00:18:30.539 align:start position:0% know this to be the case 00:18:30.539 --> 00:18:33.049 align:start position:0% know this to be the case uh<00:18:31.200> we're<00:18:31.500> not<00:18:31.740> sending<00:18:32.100> it<00:18:32.160> anything 00:18:33.049 --> 00:18:33.059 align:start position:0% uh we're not sending it anything 00:18:33.059 --> 00:18:35.390 align:start position:0% uh we're not sending it anything in<00:18:33.660> terms<00:18:33.900> of<00:18:33.960> value 00:18:35.390 --> 00:18:35.400 align:start position:0% in terms of value 00:18:35.400 --> 00:18:37.610 align:start position:0% in terms of value and<00:18:36.000> then<00:18:36.059> the<00:18:36.419> data<00:18:36.840> that<00:18:37.320> we're<00:18:37.440> going<00:18:37.559> to 00:18:37.610 --> 00:18:37.620 align:start position:0% and then the data that we're going to 00:18:37.620 --> 00:18:39.590 align:start position:0% and then the data that we're going to send<00:18:37.799> it<00:18:38.039> to<00:18:38.220> start<00:18:38.340> with<00:18:38.580> is<00:18:39.000> just<00:18:39.240> going<00:18:39.360> to 00:18:39.590 --> 00:18:39.600 align:start position:0% send it to start with is just going to 00:18:39.600 --> 00:18:41.289 align:start position:0% send it to start with is just going to be<00:18:39.720> some<00:18:40.260> dummy 00:18:41.289 --> 00:18:41.299 align:start position:0% be some dummy 00:18:41.299 --> 00:18:44.870 align:start position:0% be some dummy uh<00:18:42.299> like<00:18:42.900> 0x1 00:18:44.870 --> 00:18:44.880 align:start position:0% uh like 0x1 00:18:44.880 --> 00:18:48.350 align:start position:0% uh like 0x1 and<00:18:45.419> that<00:18:45.900> is<00:18:46.140> basically<00:18:47.100> all<00:18:47.760> right<00:18:47.940> and<00:18:48.179> now 00:18:48.350 --> 00:18:48.360 align:start position:0% and that is basically all right and now 00:18:48.360 --> 00:18:49.850 align:start position:0% and that is basically all right and now we're<00:18:48.480> going<00:18:48.600> to<00:18:48.720> have 00:18:49.850 --> 00:18:49.860 align:start position:0% we're going to have 00:18:49.860 --> 00:18:51.350 align:start position:0% we're going to have now<00:18:50.220> I'm<00:18:50.280> gonna<00:18:50.460> have<00:18:50.640> a<00:18:50.820> little<00:18:50.880> fight<00:18:51.120> with 00:18:51.350 --> 00:18:51.360 align:start position:0% now I'm gonna have a little fight with 00:18:51.360 --> 00:18:54.950 align:start position:0% now I'm gonna have a little fight with prettier 00:18:54.950 --> 00:18:54.960 align:start position:0% 00:18:54.960 --> 00:18:57.289 align:start position:0% for<00:18:55.440> some<00:18:55.559> reason<00:18:55.799> the<00:18:56.280> eslint<00:18:56.940> prettier 00:18:57.289 --> 00:18:57.299 align:start position:0% for some reason the eslint prettier 00:18:57.299 --> 00:19:02.049 align:start position:0% for some reason the eslint prettier plugin<00:18:57.780> does<00:18:58.260> not<00:18:58.380> work<00:18:58.679> as<00:18:59.100> advertised 00:19:02.049 --> 00:19:02.059 align:start position:0% 00:19:02.059 --> 00:19:04.730 align:start position:0% We're<00:19:03.059> not<00:19:03.240> gonna<00:19:03.360> let<00:19:03.600> that<00:19:03.780> stop<00:19:04.020> us 00:19:04.730 --> 00:19:04.740 align:start position:0% We're not gonna let that stop us 00:19:04.740 --> 00:19:10.490 align:start position:0% We're not gonna let that stop us ha<00:19:05.340> ha 00:19:10.490 --> 00:19:10.500 align:start position:0% 00:19:10.500 --> 00:19:12.169 align:start position:0% excellent 00:19:12.169 --> 00:19:12.179 align:start position:0% excellent 00:19:12.179 --> 00:19:14.630 align:start position:0% excellent okay<00:19:12.780> now<00:19:13.500> I'm<00:19:13.799> going<00:19:13.980> to<00:19:14.100> try<00:19:14.160> to<00:19:14.280> reconnect 00:19:14.630 --> 00:19:14.640 align:start position:0% okay now I'm going to try to reconnect 00:19:14.640 --> 00:19:19.610 align:start position:0% okay now I'm going to try to reconnect and<00:19:15.000> it's<00:19:15.179> not<00:19:15.360> going<00:19:15.539> to<00:19:15.660> fail<00:19:15.780> to<00:19:15.960> install 00:19:19.610 --> 00:19:19.620 align:start position:0% 00:19:19.620 --> 00:19:21.289 align:start position:0% and<00:19:19.980> so<00:19:20.100> we<00:19:20.280> can<00:19:20.400> see<00:19:20.580> that<00:19:20.820> like<00:19:21.059> the 00:19:21.289 --> 00:19:21.299 align:start position:0% and so we can see that like the 00:19:21.299 --> 00:19:22.610 align:start position:0% and so we can see that like the permissions<00:19:21.660> that<00:19:21.960> we're<00:19:22.080> requesting<00:19:22.440> have 00:19:22.610 --> 00:19:22.620 align:start position:0% permissions that we're requesting have 00:19:22.620 --> 00:19:24.890 align:start position:0% permissions that we're requesting have changed<00:19:23.039> uh<00:19:23.700> because<00:19:23.940> we're<00:19:24.240> now<00:19:24.480> fetching 00:19:24.890 --> 00:19:24.900 align:start position:0% changed uh because we're now fetching 00:19:24.900 --> 00:19:26.570 align:start position:0% changed uh because we're now fetching and<00:19:25.020> displaying<00:19:25.440> transaction<00:19:25.980> insights 00:19:26.570 --> 00:19:26.580 align:start position:0% and displaying transaction insights 00:19:26.580 --> 00:19:28.850 align:start position:0% and displaying transaction insights that's<00:19:26.700> the<00:19:26.880> purpose<00:19:27.120> of<00:19:27.299> the<00:19:27.419> snap<00:19:27.600> now 00:19:28.850 --> 00:19:28.860 align:start position:0% that's the purpose of the snap now 00:19:28.860 --> 00:19:32.870 align:start position:0% that's the purpose of the snap now and<00:19:29.039> we're<00:19:29.220> going<00:19:29.400> to<00:19:29.460> improve<00:19:29.760> and<00:19:29.880> install 00:19:32.870 --> 00:19:32.880 align:start position:0% 00:19:32.880 --> 00:19:35.330 align:start position:0% and<00:19:33.600> I'm<00:19:33.840> going<00:19:34.200> to 00:19:35.330 --> 00:19:35.340 align:start position:0% and I'm going to 00:19:35.340 --> 00:19:37.669 align:start position:0% and I'm going to anxiously<00:19:36.240> look<00:19:36.480> at<00:19:36.720> the<00:19:36.900> background<00:19:37.200> console 00:19:37.669 --> 00:19:37.679 align:start position:0% anxiously look at the background console 00:19:37.679 --> 00:19:41.210 align:start position:0% anxiously look at the background console I<00:19:37.980> think<00:19:38.220> it<00:19:38.400> worked 00:19:41.210 --> 00:19:41.220 align:start position:0% 00:19:41.220 --> 00:19:42.470 align:start position:0% yes<00:19:41.580> it<00:19:41.760> did 00:19:42.470 --> 00:19:42.480 align:start position:0% yes it did 00:19:42.480 --> 00:19:46.549 align:start position:0% yes it did uh<00:19:43.020> so<00:19:43.140> now<00:19:43.260> it's<00:19:43.440> asking<00:19:43.740> for<00:19:43.860> accounts<00:19:44.400> uh 00:19:46.549 --> 00:19:46.559 align:start position:0% uh so now it's asking for accounts uh 00:19:46.559 --> 00:19:49.370 align:start position:0% uh so now it's asking for accounts uh that<00:19:47.039> should<00:19:47.220> be<00:19:47.340> familiar<00:19:47.700> and<00:19:48.240> here 00:19:49.370 --> 00:19:49.380 align:start position:0% that should be familiar and here 00:19:49.380 --> 00:19:51.770 align:start position:0% that should be familiar and here where<00:19:49.679> metamask<00:19:50.280> is<00:19:50.520> trying<00:19:50.700> to<00:19:50.880> estimate 00:19:51.770 --> 00:19:51.780 align:start position:0% where metamask is trying to estimate 00:19:51.780 --> 00:19:54.890 align:start position:0% where metamask is trying to estimate some<00:19:52.020> stuff<00:19:52.260> and<00:19:53.100> look<00:19:53.280> Fubar<00:19:54.000> okay<00:19:54.539> we're 00:19:54.890 --> 00:19:54.900 align:start position:0% some stuff and look Fubar okay we're 00:19:54.900 --> 00:19:56.750 align:start position:0% some stuff and look Fubar okay we're using<00:19:55.200> the<00:19:55.320> API<00:19:55.620> correctly<00:19:56.039> we're<00:19:56.280> slowly 00:19:56.750 --> 00:19:56.760 align:start position:0% using the API correctly we're slowly 00:19:56.760 --> 00:20:01.549 align:start position:0% using the API correctly we're slowly inching<00:19:57.179> towards<00:19:57.480> our<00:19:57.600> goal<00:19:57.900> uh 00:20:01.549 --> 00:20:01.559 align:start position:0% 00:20:01.559 --> 00:20:05.029 align:start position:0% you're<00:20:02.100> too<00:20:02.580> kind<00:20:02.760> you're<00:20:03.120> too<00:20:03.299> kind 00:20:05.029 --> 00:20:05.039 align:start position:0% you're too kind you're too kind 00:20:05.039 --> 00:20:06.890 align:start position:0% you're too kind you're too kind um<00:20:05.100> all<00:20:05.340> right<00:20:05.460> and<00:20:05.760> so<00:20:05.940> we<00:20:06.179> rejected<00:20:06.600> that<00:20:06.720> and 00:20:06.890 --> 00:20:06.900 align:start position:0% um all right and so we rejected that and 00:20:06.900 --> 00:20:08.150 align:start position:0% um all right and so we rejected that and there's<00:20:07.080> an<00:20:07.200> error<00:20:07.500> here<00:20:07.620> that's<00:20:07.860> totally 00:20:08.150 --> 00:20:08.160 align:start position:0% there's an error here that's totally 00:20:08.160 --> 00:20:10.549 align:start position:0% there's an error here that's totally fine<00:20:08.400> that's<00:20:08.820> expected<00:20:09.360> we<00:20:10.140> love<00:20:10.320> our 00:20:10.549 --> 00:20:10.559 align:start position:0% fine that's expected we love our 00:20:10.559 --> 00:20:12.770 align:start position:0% fine that's expected we love our expected<00:20:10.980> errors 00:20:12.770 --> 00:20:12.780 align:start position:0% expected errors 00:20:12.780 --> 00:20:15.590 align:start position:0% expected errors um<00:20:12.900> okay<00:20:13.500> uh<00:20:14.340> so<00:20:14.580> the<00:20:14.700> next<00:20:14.820> thing<00:20:15.059> so<00:20:15.360> the 00:20:15.590 --> 00:20:15.600 align:start position:0% um okay uh so the next thing so the 00:20:15.600 --> 00:20:17.570 align:start position:0% um okay uh so the next thing so the front<00:20:15.780> end<00:20:15.960> now<00:20:16.260> for<00:20:16.559> like<00:20:16.799> this<00:20:17.340> uh 00:20:17.570 --> 00:20:17.580 align:start position:0% front end now for like this uh 00:20:17.580 --> 00:20:19.549 align:start position:0% front end now for like this uh demonstration<00:20:18.179> is<00:20:18.539> basically<00:20:18.900> uh<00:20:19.380> is 00:20:19.549 --> 00:20:19.559 align:start position:0% demonstration is basically uh is 00:20:19.559 --> 00:20:20.870 align:start position:0% demonstration is basically uh is basically<00:20:19.860> done 00:20:20.870 --> 00:20:20.880 align:start position:0% basically done 00:20:20.880 --> 00:20:23.570 align:start position:0% basically done uh<00:20:21.419> and<00:20:21.539> we're<00:20:21.660> gonna<00:20:21.780> go<00:20:22.380> back<00:20:22.620> and<00:20:23.100> look<00:20:23.280> at 00:20:23.570 --> 00:20:23.580 align:start position:0% uh and we're gonna go back and look at 00:20:23.580 --> 00:20:25.010 align:start position:0% uh and we're gonna go back and look at our 00:20:25.010 --> 00:20:25.020 align:start position:0% our 00:20:25.020 --> 00:20:27.650 align:start position:0% our um<00:20:25.100> uh<00:20:26.100> snap<00:20:26.340> because<00:20:26.940> the<00:20:27.179> next<00:20:27.299> thing<00:20:27.480> is 00:20:27.650 --> 00:20:27.660 align:start position:0% um uh snap because the next thing is 00:20:27.660 --> 00:20:30.169 align:start position:0% um uh snap because the next thing is okay<00:20:27.960> so<00:20:28.440> we<00:20:28.860> managed<00:20:29.280> to<00:20:29.400> like<00:20:29.760> interact<00:20:30.059> with 00:20:30.169 --> 00:20:30.179 align:start position:0% okay so we managed to like interact with 00:20:30.179 --> 00:20:31.669 align:start position:0% okay so we managed to like interact with the<00:20:30.360> API<00:20:30.600> we've<00:20:30.960> demonstrated<00:20:31.260> that<00:20:31.440> we<00:20:31.620> can 00:20:31.669 --> 00:20:31.679 align:start position:0% the API we've demonstrated that we can 00:20:31.679 --> 00:20:33.650 align:start position:0% the API we've demonstrated that we can do<00:20:31.799> transaction<00:20:32.220> insights<00:20:32.880> but<00:20:33.299> now<00:20:33.480> let's 00:20:33.650 --> 00:20:33.660 align:start position:0% do transaction insights but now let's 00:20:33.660 --> 00:20:35.150 align:start position:0% do transaction insights but now let's actually<00:20:33.900> go<00:20:34.140> get<00:20:34.320> some<00:20:34.559> like<00:20:34.740> useful 00:20:35.150 --> 00:20:35.160 align:start position:0% actually go get some like useful 00:20:35.160 --> 00:20:38.870 align:start position:0% actually go get some like useful information<00:20:35.780> uh<00:20:36.780> and<00:20:37.080> see<00:20:37.260> if<00:20:37.559> we<00:20:37.860> can 00:20:38.870 --> 00:20:38.880 align:start position:0% information uh and see if we can 00:20:38.880 --> 00:20:41.750 align:start position:0% information uh and see if we can um<00:20:39.000> like<00:20:39.539> decode<00:20:40.160> uh<00:20:41.160> more<00:20:41.460> of<00:20:41.640> this 00:20:41.750 --> 00:20:41.760 align:start position:0% um like decode uh more of this 00:20:41.760 --> 00:20:44.390 align:start position:0% um like decode uh more of this transaction<00:20:42.240> than<00:20:42.840> we're<00:20:43.020> currently<00:20:43.440> doing 00:20:44.390 --> 00:20:44.400 align:start position:0% transaction than we're currently doing 00:20:44.400 --> 00:20:47.690 align:start position:0% transaction than we're currently doing uh<00:20:45.059> and<00:20:45.240> in<00:20:45.360> order<00:20:45.480> to<00:20:45.660> do<00:20:45.900> that 00:20:47.690 --> 00:20:47.700 align:start position:0% uh and in order to do that 00:20:47.700 --> 00:20:50.029 align:start position:0% uh and in order to do that we're<00:20:48.419> going<00:20:48.600> to<00:20:48.660> add<00:20:48.840> a<00:20:49.080> second<00:20:49.320> at 00:20:50.029 --> 00:20:50.039 align:start position:0% we're going to add a second at 00:20:50.039 --> 00:20:52.430 align:start position:0% we're going to add a second at permission<00:20:50.400> because<00:20:51.299> we<00:20:51.660> are<00:20:51.780> going<00:20:51.960> to<00:20:52.140> call 00:20:52.430 --> 00:20:52.440 align:start position:0% permission because we are going to call 00:20:52.440 --> 00:20:56.690 align:start position:0% permission because we are going to call the<00:20:53.280> four<00:20:53.460> byte<00:20:53.880> registry<00:20:54.299> API<00:20:55.160> and<00:20:56.160> snaps<00:20:56.580> do 00:20:56.690 --> 00:20:56.700 align:start position:0% the four byte registry API and snaps do 00:20:56.700 --> 00:20:59.930 align:start position:0% the four byte registry API and snaps do not<00:20:56.940> get<00:20:57.240> uh<00:20:57.720> network<00:20:58.020> access<00:20:58.320> by<00:20:58.740> default<00:20:59.100> uh 00:20:59.930 --> 00:20:59.940 align:start position:0% not get uh network access by default uh 00:20:59.940 --> 00:21:02.390 align:start position:0% not get uh network access by default uh so<00:21:00.240> they<00:21:00.539> cannot<00:21:01.260> just<00:21:01.500> like<00:21:01.620> call<00:21:01.919> out<00:21:02.100> to<00:21:02.280> the 00:21:02.390 --> 00:21:02.400 align:start position:0% so they cannot just like call out to the 00:21:02.400 --> 00:21:04.610 align:start position:0% so they cannot just like call out to the network<00:21:02.520> unless<00:21:03.240> they<00:21:03.539> are<00:21:03.660> granted<00:21:04.140> the 00:21:04.610 --> 00:21:04.620 align:start position:0% network unless they are granted the 00:21:04.620 --> 00:21:07.909 align:start position:0% network unless they are granted the permission<00:21:04.919> to<00:21:05.100> do<00:21:05.280> so<00:21:05.400> explicitly<00:21:06.320> and<00:21:07.320> that 00:21:07.909 --> 00:21:07.919 align:start position:0% permission to do so explicitly and that 00:21:07.919 --> 00:21:09.890 align:start position:0% permission to do so explicitly and that permission<00:21:08.220> is<00:21:08.460> simply<00:21:08.760> called<00:21:09.000> endowment 00:21:09.890 --> 00:21:09.900 align:start position:0% permission is simply called endowment 00:21:09.900 --> 00:21:12.610 align:start position:0% permission is simply called endowment network<00:21:10.559> access 00:21:12.610 --> 00:21:12.620 align:start position:0% network access 00:21:12.620 --> 00:21:16.789 align:start position:0% network access and<00:21:13.620> uh<00:21:14.580> we<00:21:15.179> are<00:21:15.360> going<00:21:15.480> to<00:21:15.660> call<00:21:15.960> as<00:21:16.559> I<00:21:16.740> said 00:21:16.789 --> 00:21:16.799 align:start position:0% and uh we are going to call as I said 00:21:16.799 --> 00:21:19.130 align:start position:0% and uh we are going to call as I said the<00:21:16.980> four<00:21:17.160> byte<00:21:17.520> API 00:21:19.130 --> 00:21:19.140 align:start position:0% the four byte API 00:21:19.140 --> 00:21:22.070 align:start position:0% the four byte API and<00:21:19.740> we<00:21:19.919> have<00:21:20.100> some<00:21:20.220> and<00:21:20.580> we<00:21:20.820> have<00:21:20.940> some<00:21:21.240> useful 00:21:22.070 --> 00:21:22.080 align:start position:0% and we have some and we have some useful 00:21:22.080 --> 00:21:29.289 align:start position:0% and we have some and we have some useful Snippets<00:21:22.620> here<00:21:22.980> uh<00:21:23.940> in<00:21:24.179> order<00:21:24.240> to<00:21:24.419> do<00:21:24.600> that 00:21:29.289 --> 00:21:29.299 align:start position:0% 00:21:29.299 --> 00:21:33.710 align:start position:0% and<00:21:30.299> so<00:21:30.600> here<00:21:31.380> the<00:21:32.280> this<00:21:32.520> API<00:21:33.000> endpoint<00:21:33.419> that's 00:21:33.710 --> 00:21:33.720 align:start position:0% and so here the this API endpoint that's 00:21:33.720 --> 00:21:37.070 align:start position:0% and so here the this API endpoint that's simply<00:21:34.080> just<00:21:34.440> like<00:21:34.679> the<00:21:35.400> um<00:21:35.520> uh<00:21:36.299> the<00:21:36.539> four<00:21:36.659> byte 00:21:37.070 --> 00:21:37.080 align:start position:0% simply just like the um uh the four byte 00:21:37.080 --> 00:21:39.529 align:start position:0% simply just like the um uh the four byte API<00:21:37.679> endpoint<00:21:37.980> that<00:21:38.159> we're<00:21:38.280> going<00:21:38.400> to<00:21:38.520> call<00:21:38.700> it 00:21:39.529 --> 00:21:39.539 align:start position:0% API endpoint that we're going to call it 00:21:39.539 --> 00:21:41.330 align:start position:0% API endpoint that we're going to call it has<00:21:39.659> a<00:21:39.840> single<00:21:40.080> query<00:21:40.320> parameter<00:21:40.860> which<00:21:41.100> is 00:21:41.330 --> 00:21:41.340 align:start position:0% has a single query parameter which is 00:21:41.340 --> 00:21:44.149 align:start position:0% has a single query parameter which is the<00:21:41.580> hexadecimal<00:21:42.480> like<00:21:43.020> four<00:21:43.320> byte<00:21:43.679> signature 00:21:44.149 --> 00:21:44.159 align:start position:0% the hexadecimal like four byte signature 00:21:44.159 --> 00:21:48.110 align:start position:0% the hexadecimal like four byte signature of<00:21:45.059> the<00:21:45.480> uh<00:21:46.320> of<00:21:46.740> the<00:21:46.919> contract<00:21:47.220> call<00:21:47.400> the<00:21:47.820> call 00:21:48.110 --> 00:21:48.120 align:start position:0% of the uh of the contract call the call 00:21:48.120 --> 00:21:51.409 align:start position:0% of the uh of the contract call the call data<00:21:48.780> and<00:21:49.620> then<00:21:49.860> we<00:21:50.400> have<00:21:50.580> just<00:21:50.760> a<00:21:50.880> useful<00:21:51.179> type 00:21:51.409 --> 00:21:51.419 align:start position:0% data and then we have just a useful type 00:21:51.419 --> 00:21:54.169 align:start position:0% data and then we have just a useful type that<00:21:52.320> we<00:21:52.559> will<00:21:52.799> use<00:21:53.220> when<00:21:53.520> we<00:21:53.700> parse<00:21:54.000> the 00:21:54.169 --> 00:21:54.179 align:start position:0% that we will use when we parse the 00:21:54.179 --> 00:21:56.990 align:start position:0% that we will use when we parse the results<00:21:54.299> once<00:21:54.900> once<00:21:55.320> we<00:21:55.440> get<00:21:55.559> them<00:21:55.760> uh<00:21:56.760> this 00:21:56.990 --> 00:21:57.000 align:start position:0% results once once we get them uh this 00:21:57.000 --> 00:21:58.430 align:start position:0% results once once we get them uh this network<00:21:57.179> permitting 00:21:58.430 --> 00:21:58.440 align:start position:0% network permitting 00:21:58.440 --> 00:22:02.090 align:start position:0% network permitting uh<00:21:59.220> and<00:21:59.580> so<00:22:00.000> uh<00:22:00.960> actually<00:22:01.080> before<00:22:01.380> I<00:22:01.620> forget<00:22:01.799> to 00:22:02.090 --> 00:22:02.100 align:start position:0% uh and so uh actually before I forget to 00:22:02.100 --> 00:22:03.289 align:start position:0% uh and so uh actually before I forget to do<00:22:02.280> this 00:22:03.289 --> 00:22:03.299 align:start position:0% do this 00:22:03.299 --> 00:22:07.190 align:start position:0% do this I'm<00:22:03.720> going<00:22:03.840> to<00:22:04.020> swap<00:22:04.320> out<00:22:04.620> this<00:22:04.980> dummy<00:22:05.520> value 00:22:07.190 --> 00:22:07.200 align:start position:0% I'm going to swap out this dummy value 00:22:07.200 --> 00:22:10.270 align:start position:0% I'm going to swap out this dummy value into<00:22:07.740> something<00:22:08.039> real 00:22:10.270 --> 00:22:10.280 align:start position:0% into something real 00:22:10.280 --> 00:22:15.470 align:start position:0% into something real uh<00:22:11.280> let's<00:22:11.400> see<00:22:11.640> transaction<00:22:12.240> constants<00:22:13.140> Dot 00:22:15.470 --> 00:22:15.480 align:start position:0% uh let's see transaction constants Dot 00:22:15.480 --> 00:22:17.450 align:start position:0% uh let's see transaction constants Dot update<00:22:16.140> withdrawal<00:22:16.679> account<00:22:16.860> so<00:22:17.159> these<00:22:17.400> are 00:22:17.450 --> 00:22:17.460 align:start position:0% update withdrawal account so these are 00:22:17.460 --> 00:22:18.710 align:start position:0% update withdrawal account so these are just<00:22:17.580> some<00:22:17.760> these<00:22:18.120> are<00:22:18.179> just<00:22:18.360> like<00:22:18.480> some 00:22:18.710 --> 00:22:18.720 align:start position:0% just some these are just like some 00:22:18.720 --> 00:22:21.710 align:start position:0% just some these are just like some encoded<00:22:19.380> contract<00:22:20.039> calls 00:22:21.710 --> 00:22:21.720 align:start position:0% encoded contract calls 00:22:21.720 --> 00:22:24.890 align:start position:0% encoded contract calls um<00:22:21.840> that<00:22:22.500> uh<00:22:23.100> we<00:22:23.460> to<00:22:23.820> save<00:22:24.000> time<00:22:24.240> we<00:22:24.480> encoded 00:22:24.890 --> 00:22:24.900 align:start position:0% um that uh we to save time we encoded 00:22:24.900 --> 00:22:26.570 align:start position:0% um that uh we to save time we encoded before<00:22:25.080> this<00:22:25.380> Workshop 00:22:26.570 --> 00:22:26.580 align:start position:0% before this Workshop 00:22:26.580 --> 00:22:29.169 align:start position:0% before this Workshop and<00:22:27.480> so<00:22:27.659> next<00:22:27.900> we<00:22:28.200> want<00:22:28.380> to 00:22:29.169 --> 00:22:29.179 align:start position:0% and so next we want to 00:22:29.179 --> 00:22:32.390 align:start position:0% and so next we want to fetch<00:22:30.179> data<00:22:30.480> from<00:22:30.659> four<00:22:30.960> bytes 00:22:32.390 --> 00:22:32.400 align:start position:0% fetch data from four bytes 00:22:32.400 --> 00:22:35.870 align:start position:0% fetch data from four bytes and<00:22:32.940> that<00:22:33.240> is<00:22:33.419> going<00:22:33.600> to<00:22:33.840> start<00:22:34.140> with<00:22:34.799> a<00:22:35.400> fetch 00:22:35.870 --> 00:22:35.880 align:start position:0% and that is going to start with a fetch 00:22:35.880 --> 00:22:37.450 align:start position:0% and that is going to start with a fetch call 00:22:37.450 --> 00:22:37.460 align:start position:0% call 00:22:37.460 --> 00:22:41.029 align:start position:0% call uh<00:22:38.460> await<00:22:39.000> fetch 00:22:41.029 --> 00:22:41.039 align:start position:0% uh await fetch 00:22:41.039 --> 00:22:43.070 align:start position:0% uh await fetch all<00:22:41.400> right<00:22:41.460> are<00:22:41.820> we<00:22:42.000> done<00:22:42.179> no<00:22:42.539> we're<00:22:42.720> not<00:22:42.900> done 00:22:43.070 --> 00:22:43.080 align:start position:0% all right are we done no we're not done 00:22:43.080 --> 00:22:44.870 align:start position:0% all right are we done no we're not done because<00:22:43.320> we<00:22:43.559> need<00:22:43.740> to 00:22:44.870 --> 00:22:44.880 align:start position:0% because we need to 00:22:44.880 --> 00:22:47.690 align:start position:0% because we need to uh<00:22:45.600> parse<00:22:46.020> the<00:22:46.200> transaction 00:22:47.690 --> 00:22:47.700 align:start position:0% uh parse the transaction 00:22:47.700 --> 00:22:50.169 align:start position:0% uh parse the transaction data<00:22:48.539> first 00:22:50.169 --> 00:22:50.179 align:start position:0% data first 00:22:50.179 --> 00:22:54.350 align:start position:0% data first and<00:22:51.179> we<00:22:51.840> are<00:22:51.960> going<00:22:52.200> to<00:22:52.500> do 00:22:54.350 --> 00:22:54.360 align:start position:0% and we are going to do 00:22:54.360 --> 00:22:56.390 align:start position:0% and we are going to do uh<00:22:55.260> let's<00:22:55.500> see 00:22:56.390 --> 00:22:56.400 align:start position:0% uh let's see 00:22:56.400 --> 00:22:59.210 align:start position:0% uh let's see function<00:22:57.240> signature 00:22:59.210 --> 00:22:59.220 align:start position:0% function signature 00:22:59.220 --> 00:23:02.930 align:start position:0% function signature is<00:23:00.120> going<00:23:00.419> to<00:23:00.539> be<00:23:00.780> equal<00:23:01.080> to 00:23:02.930 --> 00:23:02.940 align:start position:0% is going to be equal to 00:23:02.940 --> 00:23:04.549 align:start position:0% is going to be equal to all<00:23:03.480> right<00:23:03.600> first<00:23:03.840> we're<00:23:04.140> going<00:23:04.260> to<00:23:04.380> do 00:23:04.549 --> 00:23:04.559 align:start position:0% all right first we're going to do 00:23:04.559 --> 00:23:07.750 align:start position:0% all right first we're going to do transaction<00:23:05.520> data<00:23:06.120> actually 00:23:07.750 --> 00:23:07.760 align:start position:0% transaction data actually 00:23:07.760 --> 00:23:12.890 align:start position:0% transaction data actually equals<00:23:08.840> remove<00:23:10.340> 0x<00:23:11.340> so<00:23:11.760> we're<00:23:11.940> gonna<00:23:12.120> it's 00:23:12.890 --> 00:23:12.900 align:start position:0% equals remove 0x so we're gonna it's 00:23:12.900 --> 00:23:14.630 align:start position:0% equals remove 0x so we're gonna it's zero<00:23:13.320> X<00:23:13.500> prefixed<00:23:14.039> and<00:23:14.159> we're<00:23:14.280> going<00:23:14.400> to<00:23:14.520> strip 00:23:14.630 --> 00:23:14.640 align:start position:0% zero X prefixed and we're going to strip 00:23:14.640 --> 00:23:18.289 align:start position:0% zero X prefixed and we're going to strip that 00:23:18.289 --> 00:23:18.299 align:start position:0% 00:23:18.299 --> 00:23:19.970 align:start position:0% excellent 00:23:19.970 --> 00:23:19.980 align:start position:0% excellent 00:23:19.980 --> 00:23:22.370 align:start position:0% excellent and<00:23:20.340> then<00:23:20.400> the<00:23:20.580> function<00:23:20.880> signature<00:23:21.539> is<00:23:22.140> going 00:23:22.370 --> 00:23:22.380 align:start position:0% and then the function signature is going 00:23:22.380 --> 00:23:26.149 align:start position:0% and then the function signature is going to<00:23:22.740> be<00:23:23.220> at<00:23:23.940> the<00:23:24.360> first<00:23:24.600> eight<00:23:25.320> bytes<00:23:25.799> of<00:23:25.980> the 00:23:26.149 --> 00:23:26.159 align:start position:0% to be at the first eight bytes of the 00:23:26.159 --> 00:23:28.250 align:start position:0% to be at the first eight bytes of the transaction<00:23:26.520> data<00:23:27.000> or<00:23:27.179> sorry<00:23:27.419> the<00:23:27.659> first<00:23:27.840> four 00:23:28.250 --> 00:23:28.260 align:start position:0% transaction data or sorry the first four 00:23:28.260 --> 00:23:32.630 align:start position:0% transaction data or sorry the first four bytes<00:23:29.220> uh<00:23:30.179> which<00:23:30.539> will 00:23:32.630 --> 00:23:32.640 align:start position:0% bytes uh which will 00:23:32.640 --> 00:23:35.210 align:start position:0% bytes uh which will uh<00:23:33.480> let's<00:23:33.780> see 00:23:35.210 --> 00:23:35.220 align:start position:0% uh let's see 00:23:35.220 --> 00:23:39.890 align:start position:0% uh let's see transaction<00:23:35.880> data<00:23:36.480> dot<00:23:36.840> slice 00:23:39.890 --> 00:23:39.900 align:start position:0% 00:23:39.900 --> 00:23:41.330 align:start position:0% there<00:23:40.320> we<00:23:40.500> go 00:23:41.330 --> 00:23:41.340 align:start position:0% there we go 00:23:41.340 --> 00:23:43.029 align:start position:0% there we go uh<00:23:42.059> and<00:23:42.179> now<00:23:42.299> we<00:23:42.480> have<00:23:42.600> the<00:23:42.720> function 00:23:43.029 --> 00:23:43.039 align:start position:0% uh and now we have the function 00:23:43.039 --> 00:23:44.930 align:start position:0% uh and now we have the function signature<00:23:44.039> as<00:23:44.159> well 00:23:44.930 --> 00:23:44.940 align:start position:0% signature as well 00:23:44.940 --> 00:23:46.250 align:start position:0% signature as well and 00:23:46.250 --> 00:23:46.260 align:start position:0% and 00:23:46.260 --> 00:23:50.570 align:start position:0% and in<00:23:46.799> order<00:23:47.039> to<00:23:47.700> uh 00:23:50.570 --> 00:23:50.580 align:start position:0% in order to uh 00:23:50.580 --> 00:23:51.830 align:start position:0% in order to uh fetch 00:23:51.830 --> 00:23:51.840 align:start position:0% fetch 00:23:51.840 --> 00:23:55.190 align:start position:0% fetch uh<00:23:52.380> from<00:23:52.500> four<00:23:52.679> byte<00:23:53.100> we<00:23:53.460> need<00:23:53.640> to<00:23:53.940> do 00:23:55.190 --> 00:23:55.200 align:start position:0% uh from four byte we need to do 00:23:55.200 --> 00:23:57.710 align:start position:0% uh from four byte we need to do the<00:23:55.740> API<00:23:56.159> endpoints 00:23:57.710 --> 00:23:57.720 align:start position:0% the API endpoints 00:23:57.720 --> 00:24:00.350 align:start position:0% the API endpoints followed<00:23:58.440> by 00:24:00.350 --> 00:24:00.360 align:start position:0% followed by 00:24:00.360 --> 00:24:03.070 align:start position:0% followed by the 00:24:03.070 --> 00:24:03.080 align:start position:0% the 00:24:03.080 --> 00:24:09.409 align:start position:0% the function<00:24:04.080> signature<00:24:04.740> with<00:24:05.460> a<00:24:05.820> 0x<00:24:06.659> prefix 00:24:09.409 --> 00:24:09.419 align:start position:0% 00:24:09.419 --> 00:24:11.810 align:start position:0% and<00:24:09.960> then<00:24:10.140> we<00:24:10.440> have<00:24:10.620> some<00:24:10.799> parameters<00:24:11.400> to<00:24:11.640> give 00:24:11.810 --> 00:24:11.820 align:start position:0% and then we have some parameters to give 00:24:11.820 --> 00:24:16.190 align:start position:0% and then we have some parameters to give this<00:24:12.240> which<00:24:12.900> is<00:24:13.080> going<00:24:13.380> to<00:24:13.559> be 00:24:16.190 --> 00:24:16.200 align:start position:0% 00:24:16.200 --> 00:24:18.710 align:start position:0% uh<00:24:16.919> get 00:24:18.710 --> 00:24:18.720 align:start position:0% uh get 00:24:18.720 --> 00:24:22.250 align:start position:0% uh get and<00:24:19.380> we<00:24:19.679> have<00:24:19.860> just<00:24:20.100> some<00:24:20.220> basic<00:24:20.580> headers 00:24:22.250 --> 00:24:22.260 align:start position:0% and we have just some basic headers 00:24:22.260 --> 00:24:23.750 align:start position:0% and we have just some basic headers I<00:24:22.620> would<00:24:22.740> already<00:24:22.919> knew<00:24:23.159> what<00:24:23.340> I<00:24:23.460> was<00:24:23.580> going<00:24:23.700> to 00:24:23.750 --> 00:24:23.760 align:start position:0% I would already knew what I was going to 00:24:23.760 --> 00:24:25.549 align:start position:0% I would already knew what I was going to do 00:24:25.549 --> 00:24:25.559 align:start position:0% do 00:24:25.559 --> 00:24:28.130 align:start position:0% do boom 00:24:28.130 --> 00:24:28.140 align:start position:0% boom 00:24:28.140 --> 00:24:29.350 align:start position:0% boom sweet 00:24:29.350 --> 00:24:29.360 align:start position:0% sweet 00:24:29.360 --> 00:24:33.890 align:start position:0% sweet and<00:24:30.360> then<00:24:30.860> uh<00:24:31.860> if 00:24:33.890 --> 00:24:33.900 align:start position:0% and then uh if 00:24:33.900 --> 00:24:37.730 align:start position:0% and then uh if we<00:24:34.500> failed<00:24:34.919> to<00:24:35.039> do<00:24:35.220> that<00:24:35.460> we<00:24:36.240> are<00:24:36.600> going<00:24:37.080> to 00:24:37.730 --> 00:24:37.740 align:start position:0% we failed to do that we are going to 00:24:37.740 --> 00:24:40.909 align:start position:0% we failed to do that we are going to throw 00:24:40.909 --> 00:24:40.919 align:start position:0% 00:24:40.919 --> 00:24:45.710 align:start position:0% and<00:24:41.580> we're<00:24:42.000> going<00:24:42.179> to<00:24:42.299> say 00:24:45.710 --> 00:24:45.720 align:start position:0% 00:24:45.720 --> 00:24:49.789 align:start position:0% failed<00:24:46.620> to<00:24:46.860> fetch<00:24:47.400> from<00:24:48.059> four<00:24:48.659> bite 00:24:49.789 --> 00:24:49.799 align:start position:0% failed to fetch from four bite 00:24:49.799 --> 00:24:52.549 align:start position:0% failed to fetch from four bite registry 00:24:52.549 --> 00:24:52.559 align:start position:0% registry 00:24:52.559 --> 00:24:54.350 align:start position:0% registry but<00:24:53.039> otherwise 00:24:54.350 --> 00:24:54.360 align:start position:0% but otherwise 00:24:54.360 --> 00:24:57.350 align:start position:0% but otherwise uh<00:24:55.020> we<00:24:55.320> should<00:24:55.559> be<00:24:56.039> good<00:24:56.700> to<00:24:56.880> start<00:24:57.059> working 00:24:57.350 --> 00:24:57.360 align:start position:0% uh we should be good to start working 00:24:57.360 --> 00:24:59.110 align:start position:0% uh we should be good to start working with<00:24:57.659> this<00:24:57.840> data 00:24:59.110 --> 00:24:59.120 align:start position:0% with this data 00:24:59.120 --> 00:25:01.850 align:start position:0% with this data and<00:25:00.120> uh 00:25:01.850 --> 00:25:01.860 align:start position:0% and uh 00:25:01.860 --> 00:25:04.210 align:start position:0% and uh the<00:25:02.580> result 00:25:04.210 --> 00:25:04.220 align:start position:0% the result 00:25:04.220 --> 00:25:08.330 align:start position:0% the result is<00:25:05.220> going<00:25:05.460> to<00:25:05.640> look<00:25:05.880> something<00:25:06.179> like<00:25:06.600> this 00:25:08.330 --> 00:25:08.340 align:start position:0% is going to look something like this 00:25:08.340 --> 00:25:11.590 align:start position:0% is going to look something like this where<00:25:08.760> we<00:25:09.000> get<00:25:09.179> the<00:25:09.360> Json 00:25:11.590 --> 00:25:11.600 align:start position:0% where we get the Json 00:25:11.600 --> 00:25:17.649 align:start position:0% where we get the Json uh<00:25:12.600> oops 00:25:17.649 --> 00:25:17.659 align:start position:0% 00:25:17.659 --> 00:25:21.770 align:start position:0% and<00:25:18.659> that's<00:25:18.840> going<00:25:19.140> to<00:25:19.320> be<00:25:20.120> a<00:25:21.120> four<00:25:21.419> byte 00:25:21.770 --> 00:25:21.780 align:start position:0% and that's going to be a four byte 00:25:21.780 --> 00:25:23.810 align:start position:0% and that's going to be a four byte signature<00:25:22.320> an<00:25:22.620> array<00:25:22.919> of<00:25:23.280> four<00:25:23.460> byte 00:25:23.810 --> 00:25:23.820 align:start position:0% signature an array of four byte 00:25:23.820 --> 00:25:27.110 align:start position:0% signature an array of four byte signature<00:25:24.299> results 00:25:27.110 --> 00:25:27.120 align:start position:0% 00:25:27.120 --> 00:25:31.789 align:start position:0% and<00:25:28.020> uh 00:25:31.789 --> 00:25:31.799 align:start position:0% 00:25:31.799 --> 00:25:34.310 align:start position:0% then<00:25:32.340> once<00:25:32.700> we<00:25:32.820> have<00:25:33.000> that<00:25:33.539> result<00:25:33.779> so<00:25:34.080> the 00:25:34.310 --> 00:25:34.320 align:start position:0% then once we have that result so the 00:25:34.320 --> 00:25:35.630 align:start position:0% then once we have that result so the thing<00:25:34.440> there's<00:25:34.679> one<00:25:34.919> thing<00:25:35.100> we<00:25:35.220> have<00:25:35.340> to<00:25:35.460> deal 00:25:35.630 --> 00:25:35.640 align:start position:0% thing there's one thing we have to deal 00:25:35.640 --> 00:25:37.610 align:start position:0% thing there's one thing we have to deal with<00:25:35.880> we're<00:25:36.480> going<00:25:36.600> to<00:25:36.659> extract<00:25:37.020> the<00:25:37.320> actual 00:25:37.610 --> 00:25:37.620 align:start position:0% with we're going to extract the actual 00:25:37.620 --> 00:25:40.610 align:start position:0% with we're going to extract the actual text<00:25:37.980> signature<00:25:38.700> of<00:25:39.179> the<00:25:39.600> uh<00:25:40.020> of<00:25:40.200> the<00:25:40.380> function 00:25:40.610 --> 00:25:40.620 align:start position:0% text signature of the uh of the function 00:25:40.620 --> 00:25:44.870 align:start position:0% text signature of the uh of the function call<00:25:41.279> uh<00:25:42.179> and<00:25:42.600> uh<00:25:42.960> because<00:25:43.200> four<00:25:43.679> bytes<00:25:44.159> is<00:25:44.640> not 00:25:44.870 --> 00:25:44.880 align:start position:0% call uh and uh because four bytes is not 00:25:44.880 --> 00:25:46.610 align:start position:0% call uh and uh because four bytes is not a<00:25:45.120> very<00:25:45.179> big<00:25:45.360> space<00:25:45.659> there<00:25:46.260> are<00:25:46.380> a<00:25:46.440> lot<00:25:46.500> of 00:25:46.610 --> 00:25:46.620 align:start position:0% a very big space there are a lot of 00:25:46.620 --> 00:25:48.529 align:start position:0% a very big space there are a lot of collisions<00:25:47.039> so<00:25:47.400> it<00:25:47.580> might<00:25:47.700> return<00:25:47.880> multiple 00:25:48.529 --> 00:25:48.539 align:start position:0% collisions so it might return multiple 00:25:48.539 --> 00:25:50.570 align:start position:0% collisions so it might return multiple results<00:25:49.020> anyone<00:25:49.799> who's<00:25:49.919> dealt<00:25:50.279> with<00:25:50.340> this 00:25:50.570 --> 00:25:50.580 align:start position:0% results anyone who's dealt with this 00:25:50.580 --> 00:25:52.549 align:start position:0% results anyone who's dealt with this with<00:25:50.940> four<00:25:51.059> byte<00:25:51.480> in<00:25:51.539> practice<00:25:51.720> uh<00:25:52.380> is 00:25:52.549 --> 00:25:52.559 align:start position:0% with four byte in practice uh is 00:25:52.559 --> 00:25:54.950 align:start position:0% with four byte in practice uh is probably<00:25:52.679> familiar<00:25:53.340> with<00:25:53.580> this<00:25:53.760> problem<00:25:54.120> and 00:25:54.950 --> 00:25:54.960 align:start position:0% probably familiar with this problem and 00:25:54.960 --> 00:25:56.690 align:start position:0% probably familiar with this problem and we're<00:25:55.140> just<00:25:55.380> going<00:25:55.500> to<00:25:55.620> pick<00:25:55.799> the<00:25:56.039> oldest<00:25:56.460> one 00:25:56.690 --> 00:25:56.700 align:start position:0% we're just going to pick the oldest one 00:25:56.700 --> 00:26:00.230 align:start position:0% we're just going to pick the oldest one uh<00:25:57.659> because<00:25:57.840> we<00:25:58.080> need<00:25:58.140> to<00:25:58.260> pick<00:25:58.380> something 00:26:00.230 --> 00:26:00.240 align:start position:0% uh because we need to pick something 00:26:00.240 --> 00:26:03.950 align:start position:0% uh because we need to pick something and<00:26:00.960> so<00:26:01.500> we're<00:26:01.740> gonna<00:26:01.919> see 00:26:03.950 --> 00:26:03.960 align:start position:0% and so we're gonna see 00:26:03.960 --> 00:26:07.570 align:start position:0% and so we're gonna see function<00:26:04.679> text<00:26:05.580> signature 00:26:07.570 --> 00:26:07.580 align:start position:0% function text signature 00:26:07.580 --> 00:26:10.850 align:start position:0% function text signature is<00:26:08.580> going<00:26:09.000> to<00:26:09.240> be 00:26:10.850 --> 00:26:10.860 align:start position:0% is going to be 00:26:10.860 --> 00:26:15.370 align:start position:0% is going to be uh<00:26:11.880> let's<00:26:12.600> see<00:26:12.900> result 00:26:15.370 --> 00:26:15.380 align:start position:0% uh let's see result 00:26:15.380 --> 00:26:23.269 align:start position:0% uh let's see result uh<00:26:16.380> and<00:26:16.799> then<00:26:16.919> we're<00:26:17.100> going<00:26:17.400> to<00:26:18.120> sort 00:26:23.269 --> 00:26:23.279 align:start position:0% 00:26:23.279 --> 00:26:26.810 align:start position:0% create<00:26:23.820> an<00:26:24.120> ad<00:26:24.299> Locale<00:26:24.960> compare<00:26:25.559> B<00:26:26.220> dot 00:26:26.810 --> 00:26:26.820 align:start position:0% create an ad Locale compare B dot 00:26:26.820 --> 00:26:28.610 align:start position:0% create an ad Locale compare B dot created 00:26:28.610 --> 00:26:28.620 align:start position:0% created 00:26:28.620 --> 00:26:32.510 align:start position:0% created and<00:26:29.159> then<00:26:29.279> we're<00:26:29.520> just<00:26:29.760> gonna<00:26:30.059> map<00:26:30.600> that 00:26:32.510 --> 00:26:32.520 align:start position:0% and then we're just gonna map that 00:26:32.520 --> 00:26:38.830 align:start position:0% and then we're just gonna map that to 00:26:38.830 --> 00:26:38.840 align:start position:0% 00:26:38.840 --> 00:26:43.430 align:start position:0% value<00:26:39.840> dot<00:26:40.799> pick<00:26:41.760> signature 00:26:43.430 --> 00:26:43.440 align:start position:0% value dot pick signature 00:26:43.440 --> 00:26:48.110 align:start position:0% value dot pick signature and<00:26:44.279> so<00:26:44.580> and<00:26:45.120> if<00:26:45.299> there<00:26:45.659> is<00:26:46.159> no<00:26:47.159> function<00:26:47.820> tick 00:26:48.110 --> 00:26:48.120 align:start position:0% and so and if there is no function tick 00:26:48.120 --> 00:26:49.930 align:start position:0% and so and if there is no function tick signature 00:26:49.930 --> 00:26:49.940 align:start position:0% signature 00:26:49.940 --> 00:26:52.970 align:start position:0% signature then<00:26:50.940> uh<00:26:51.659> there<00:26:51.900> is<00:26:52.020> no<00:26:52.200> signature<00:26:52.620> for<00:26:52.799> this 00:26:52.970 --> 00:26:52.980 align:start position:0% then uh there is no signature for this 00:26:52.980 --> 00:26:55.850 align:start position:0% then uh there is no signature for this uh<00:26:53.580> and<00:26:53.700> so<00:26:53.880> we're<00:26:54.000> going<00:26:54.120> to<00:26:54.240> say 00:26:55.850 --> 00:26:55.860 align:start position:0% uh and so we're going to say 00:26:55.860 --> 00:26:58.669 align:start position:0% uh and so we're going to say um<00:26:55.919> no<00:26:56.760> function<00:26:57.240> signature 00:26:58.669 --> 00:26:58.679 align:start position:0% um no function signature 00:26:58.679 --> 00:27:01.210 align:start position:0% um no function signature or 00:27:01.210 --> 00:27:01.220 align:start position:0% 00:27:01.220 --> 00:27:05.029 align:start position:0% uh<00:27:02.240> no<00:27:03.240> function 00:27:05.029 --> 00:27:05.039 align:start position:0% uh no function 00:27:05.039 --> 00:27:09.169 align:start position:0% uh no function no<00:27:05.820> results<00:27:06.240> in<00:27:06.960> registry<00:27:07.740> for<00:27:08.640> function 00:27:09.169 --> 00:27:09.179 align:start position:0% no results in registry for function 00:27:09.179 --> 00:27:12.110 align:start position:0% no results in registry for function signature 00:27:12.110 --> 00:27:12.120 align:start position:0% signature 00:27:12.120 --> 00:27:13.850 align:start position:0% signature and<00:27:12.659> then<00:27:12.779> we're<00:27:12.960> going<00:27:13.140> to<00:27:13.200> do<00:27:13.559> an<00:27:13.740> early 00:27:13.850 --> 00:27:13.860 align:start position:0% and then we're going to do an early 00:27:13.860 --> 00:27:16.370 align:start position:0% and then we're going to do an early return 00:27:16.370 --> 00:27:16.380 align:start position:0% 00:27:16.380 --> 00:27:19.690 align:start position:0% but<00:27:17.279> in<00:27:17.940> the<00:27:18.059> happy<00:27:18.240> case 00:27:19.690 --> 00:27:19.700 align:start position:0% but in the happy case 00:27:19.700 --> 00:27:23.630 align:start position:0% but in the happy case we<00:27:20.700> are<00:27:21.000> going<00:27:21.360> to<00:27:21.779> have 00:27:23.630 --> 00:27:23.640 align:start position:0% we are going to have 00:27:23.640 --> 00:27:26.090 align:start position:0% we are going to have our<00:27:24.120> insights<00:27:24.840> Dot 00:27:26.090 --> 00:27:26.100 align:start position:0% our insights Dot 00:27:26.100 --> 00:27:28.210 align:start position:0% our insights Dot type 00:27:28.210 --> 00:27:28.220 align:start position:0% type 00:27:28.220 --> 00:27:33.049 align:start position:0% type and<00:27:29.220> we<00:27:29.820> are<00:27:29.940> going<00:27:30.120> to<00:27:30.360> give<00:27:30.600> that<00:27:31.400> uh<00:27:32.400> a<00:27:32.760> try 00:27:33.049 --> 00:27:33.059 align:start position:0% and we are going to give that uh a try 00:27:33.059 --> 00:27:34.850 align:start position:0% and we are going to give that uh a try next 00:27:34.850 --> 00:27:34.860 align:start position:0% next 00:27:34.860 --> 00:27:37.430 align:start position:0% next and<00:27:35.400> we're<00:27:35.640> actually<00:27:35.940> gonna 00:27:37.430 --> 00:27:37.440 align:start position:0% and we're actually gonna 00:27:37.440 --> 00:27:40.430 align:start position:0% and we're actually gonna link<00:27:37.980> as<00:27:38.400> well<00:27:38.520> just<00:27:38.880> to<00:27:39.059> ensure<00:27:39.539> we<00:27:40.080> have<00:27:40.260> no 00:27:40.430 --> 00:27:40.440 align:start position:0% link as well just to ensure we have no 00:27:40.440 --> 00:27:43.250 align:start position:0% link as well just to ensure we have no problems<00:27:40.860> with<00:27:41.100> that 00:27:43.250 --> 00:27:43.260 align:start position:0% problems with that 00:27:43.260 --> 00:27:48.049 align:start position:0% problems with that okay 00:27:48.049 --> 00:27:48.059 align:start position:0% 00:27:48.059 --> 00:27:51.169 align:start position:0% so<00:27:48.600> going<00:27:49.320> back<00:27:49.760> we're<00:27:50.760> going<00:27:50.880> to<00:27:50.940> need<00:27:51.059> to 00:27:51.169 --> 00:27:51.179 align:start position:0% so going back we're going to need to 00:27:51.179 --> 00:27:52.850 align:start position:0% so going back we're going to need to reconnect<00:27:51.480> because<00:27:51.840> we<00:27:52.140> modified<00:27:52.380> the<00:27:52.620> snap 00:27:52.850 --> 00:27:52.860 align:start position:0% reconnect because we modified the snap 00:27:52.860 --> 00:27:55.730 align:start position:0% reconnect because we modified the snap the<00:27:53.700> live<00:27:53.820> reload<00:27:54.360> unfortunately<00:27:55.080> doesn't<00:27:55.500> go 00:27:55.730 --> 00:27:55.740 align:start position:0% the live reload unfortunately doesn't go 00:27:55.740 --> 00:27:57.769 align:start position:0% the live reload unfortunately doesn't go all<00:27:55.919> the<00:27:56.100> way<00:27:56.159> into<00:27:56.520> the<00:27:56.760> extension<00:27:57.179> uh 00:27:57.769 --> 00:27:57.779 align:start position:0% all the way into the extension uh 00:27:57.779 --> 00:27:59.090 align:start position:0% all the way into the extension uh someday<00:27:58.200> we're<00:27:58.380> going<00:27:58.500> to<00:27:58.620> be<00:27:58.679> able<00:27:58.799> to<00:27:58.919> do 00:27:59.090 --> 00:27:59.100 align:start position:0% someday we're going to be able to do 00:27:59.100 --> 00:28:01.190 align:start position:0% someday we're going to be able to do that<00:27:59.279> but<00:28:00.179> now<00:28:00.360> we<00:28:00.480> see<00:28:00.600> that<00:28:00.779> the<00:28:00.900> permissions 00:28:01.190 --> 00:28:01.200 align:start position:0% that but now we see that the permissions 00:28:01.200 --> 00:28:02.690 align:start position:0% that but now we see that the permissions are<00:28:01.320> different<00:28:01.500> we<00:28:01.860> have<00:28:02.039> access<00:28:02.279> to<00:28:02.580> the 00:28:02.690 --> 00:28:02.700 align:start position:0% are different we have access to the 00:28:02.700 --> 00:28:05.029 align:start position:0% are different we have access to the internet<00:28:02.820> as<00:28:03.539> one<00:28:03.779> of<00:28:03.900> the<00:28:04.200> uh<00:28:04.620> permissions 00:28:05.029 --> 00:28:05.039 align:start position:0% internet as one of the uh permissions 00:28:05.039 --> 00:28:07.549 align:start position:0% internet as one of the uh permissions now<00:28:05.760> and<00:28:06.600> we're<00:28:06.900> going<00:28:07.140> to<00:28:07.200> go<00:28:07.320> ahead<00:28:07.440> and 00:28:07.549 --> 00:28:07.559 align:start position:0% now and we're going to go ahead and 00:28:07.559 --> 00:28:09.769 align:start position:0% now and we're going to go ahead and approve<00:28:07.919> and<00:28:08.039> install 00:28:09.769 --> 00:28:09.779 align:start position:0% approve and install 00:28:09.779 --> 00:28:11.930 align:start position:0% approve and install so<00:28:10.260> far<00:28:10.380> so<00:28:10.620> good 00:28:11.930 --> 00:28:11.940 align:start position:0% so far so good 00:28:11.940 --> 00:28:18.840 align:start position:0% so far so good and<00:28:12.480> then<00:28:12.600> let's<00:28:12.900> see<00:28:13.200> what<00:28:13.559> happens<00:28:13.740> now 00:28:18.840 --> 00:28:18.850 align:start position:0% 00:28:18.850 --> 00:28:27.529 align:start position:0% [Music] 00:28:27.529 --> 00:28:27.539 align:start position:0% 00:28:27.539 --> 00:28:28.690 align:start position:0% um 00:28:28.690 --> 00:28:28.700 align:start position:0% um 00:28:28.700 --> 00:28:32.690 align:start position:0% um this<00:28:29.700> may<00:28:30.240> be<00:28:30.360> a<00:28:30.539> lot<00:28:30.659> to<00:28:30.840> ask<00:28:31.140> uh<00:28:32.100> of<00:28:32.279> the<00:28:32.460> of 00:28:32.690 --> 00:28:32.700 align:start position:0% this may be a lot to ask uh of the of 00:28:32.700 --> 00:28:38.990 align:start position:0% this may be a lot to ask uh of the of the<00:28:32.880> network<00:28:33.059> at<00:28:33.419> the<00:28:33.539> moment 00:28:38.990 --> 00:28:39.000 align:start position:0% 00:28:39.000 --> 00:28:40.730 align:start position:0% yeah 00:28:40.730 --> 00:28:40.740 align:start position:0% yeah 00:28:40.740 --> 00:28:42.769 align:start position:0% yeah the<00:28:41.279> console<00:28:41.640> does<00:28:41.820> get<00:28:42.000> very<00:28:42.179> the<00:28:42.419> console 00:28:42.769 --> 00:28:42.779 align:start position:0% the console does get very the console 00:28:42.779 --> 00:28:45.230 align:start position:0% the console does get very the console there<00:28:42.960> is<00:28:43.140> we<00:28:43.740> probably<00:28:43.919> have<00:28:44.340> a<00:28:44.580> bug<00:28:44.700> where 00:28:45.230 --> 00:28:45.240 align:start position:0% there is we probably have a bug where 00:28:45.240 --> 00:28:47.570 align:start position:0% there is we probably have a bug where there<00:28:45.600> is<00:28:45.840> too<00:28:46.320> much<00:28:46.440> looping<00:28:46.919> happening<00:28:47.340> in 00:28:47.570 --> 00:28:47.580 align:start position:0% there is too much looping happening in 00:28:47.580 --> 00:28:48.649 align:start position:0% there is too much looping happening in the<00:28:47.700> background 00:28:48.649 --> 00:28:48.659 align:start position:0% the background 00:28:48.659 --> 00:28:50.810 align:start position:0% the background but<00:28:49.200> we<00:28:49.380> if<00:28:49.620> we<00:28:49.740> were<00:28:49.860> actually<00:28:49.980> if<00:28:50.400> I<00:28:50.520> reject 00:28:50.810 --> 00:28:50.820 align:start position:0% but we if we were actually if I reject 00:28:50.820 --> 00:28:52.130 align:start position:0% but we if we were actually if I reject this 00:28:52.130 --> 00:28:52.140 align:start position:0% this 00:28:52.140 --> 00:28:54.470 align:start position:0% this I<00:28:52.679> might<00:28:52.860> get<00:28:53.039> a<00:28:53.220> useful 00:28:54.470 --> 00:28:54.480 align:start position:0% I might get a useful 00:28:54.480 --> 00:28:57.470 align:start position:0% I might get a useful aha<00:28:55.080> okay<00:28:55.260> yeah<00:28:55.440> so<00:28:55.679> I<00:28:55.799> messed<00:28:56.100> it<00:28:56.159> up 00:28:57.470 --> 00:28:57.480 align:start position:0% aha okay yeah so I messed it up 00:28:57.480 --> 00:29:02.750 align:start position:0% aha okay yeah so I messed it up uh<00:28:58.320> and<00:28:58.620> let's<00:28:58.799> see<00:28:59.039> what<00:28:59.220> I<00:28:59.400> messed<00:28:59.700> up 00:29:02.750 --> 00:29:02.760 align:start position:0% 00:29:02.760 --> 00:29:11.110 align:start position:0% um 00:29:11.110 --> 00:29:11.120 align:start position:0% 00:29:11.120 --> 00:29:14.090 align:start position:0% yeah<00:29:12.120> no<00:29:12.600> the<00:29:12.840> thing<00:29:12.960> that<00:29:13.080> was<00:29:13.260> result<00:29:13.559> is<00:29:13.919> the 00:29:14.090 --> 00:29:14.100 align:start position:0% yeah no the thing that was result is the 00:29:14.100 --> 00:29:16.070 align:start position:0% yeah no the thing that was result is the thing<00:29:14.220> that<00:29:14.400> was<00:29:14.580> undefined 00:29:16.070 --> 00:29:16.080 align:start position:0% thing that was undefined 00:29:16.080 --> 00:29:23.769 align:start position:0% thing that was undefined uh<00:29:16.860> and<00:29:17.159> that<00:29:17.340> hasn't<00:29:17.700> happened<00:29:17.880> before 00:29:23.769 --> 00:29:23.779 align:start position:0% 00:29:23.779 --> 00:29:27.169 align:start position:0% I<00:29:24.779> shouldn't<00:29:25.140> no 00:29:27.169 --> 00:29:27.179 align:start position:0% I shouldn't no 00:29:27.179 --> 00:29:34.310 align:start position:0% I shouldn't no all<00:29:27.779> right<00:29:27.840> I'm<00:29:28.500> gonna<00:29:28.620> cheat 00:29:34.310 --> 00:29:34.320 align:start position:0% 00:29:34.320 --> 00:29:39.529 align:start position:0% let's<00:29:35.100> see 00:29:39.529 --> 00:29:39.539 align:start position:0% 00:29:39.539 --> 00:29:40.730 align:start position:0% oh 00:29:40.730 --> 00:29:40.740 align:start position:0% oh 00:29:40.740 --> 00:29:44.289 align:start position:0% oh ah 00:29:44.289 --> 00:29:44.299 align:start position:0% 00:29:44.299 --> 00:29:49.450 align:start position:0% thank<00:29:45.299> you 00:29:49.450 --> 00:29:49.460 align:start position:0% 00:29:49.460 --> 00:29:57.950 align:start position:0% thank<00:29:50.460> you<00:29:50.580> eagle-eyed<00:29:51.240> stranger 00:29:57.950 --> 00:29:57.960 align:start position:0% 00:29:57.960 --> 00:29:59.810 align:start position:0% yeah<00:29:58.440> if<00:29:58.620> I<00:29:58.860> were 00:29:59.810 --> 00:29:59.820 align:start position:0% yeah if I were 00:29:59.820 --> 00:30:02.330 align:start position:0% yeah if I were um<00:29:59.940> if<00:30:00.659> I<00:30:00.779> if<00:30:00.960> I<00:30:01.140> had<00:30:01.260> if<00:30:01.440> I'd<00:30:01.620> done<00:30:01.799> my<00:30:01.980> types 00:30:02.330 --> 00:30:02.340 align:start position:0% um if I if I had if I'd done my types 00:30:02.340 --> 00:30:03.590 align:start position:0% um if I if I had if I'd done my types better<00:30:02.460> this<00:30:02.820> wouldn't<00:30:02.940> have<00:30:03.120> been<00:30:03.299> a<00:30:03.480> problem 00:30:03.590 --> 00:30:03.600 align:start position:0% better this wouldn't have been a problem 00:30:03.600 --> 00:30:08.889 align:start position:0% better this wouldn't have been a problem would<00:30:03.960> that<00:30:04.080> be<00:30:04.260> a<00:30:04.380> lesson<00:30:04.740> to<00:30:05.100> everyone 00:30:08.889 --> 00:30:08.899 align:start position:0% 00:30:08.899 --> 00:30:20.149 align:start position:0% okay<00:30:09.899> now<00:30:10.740> we're<00:30:10.919> gonna<00:30:11.100> try<00:30:11.279> that<00:30:11.399> again 00:30:20.149 --> 00:30:20.159 align:start position:0% 00:30:20.159 --> 00:30:23.570 align:start position:0% hey<00:30:21.240> there<00:30:22.140> it<00:30:22.260> is<00:30:22.380> there<00:30:22.740> it<00:30:22.860> is<00:30:22.980> the<00:30:23.279> function 00:30:23.570 --> 00:30:23.580 align:start position:0% hey there it is there it is the function 00:30:23.580 --> 00:30:26.289 align:start position:0% hey there it is there it is the function signature<00:30:24.120> the<00:30:24.360> function<00:30:24.720> signature 00:30:26.289 --> 00:30:26.299 align:start position:0% signature the function signature 00:30:26.299 --> 00:30:29.750 align:start position:0% signature the function signature uh<00:30:27.299> and<00:30:28.140> uh<00:30:28.440> for<00:30:28.679> for<00:30:28.860> our<00:30:29.039> final<00:30:29.220> trick<00:30:29.580> we're 00:30:29.750 --> 00:30:29.760 align:start position:0% uh and uh for for our final trick we're 00:30:29.760 --> 00:30:31.490 align:start position:0% uh and uh for for our final trick we're going<00:30:29.880> to<00:30:29.940> get<00:30:30.120> a<00:30:30.360> little<00:30:30.480> bit<00:30:30.659> fancier<00:30:31.140> we're 00:30:31.490 --> 00:30:31.500 align:start position:0% going to get a little bit fancier we're 00:30:31.500 --> 00:30:33.110 align:start position:0% going to get a little bit fancier we're also<00:30:31.799> going<00:30:31.919> to<00:30:32.039> decode<00:30:32.399> the<00:30:32.820> actual 00:30:33.110 --> 00:30:33.120 align:start position:0% also going to decode the actual 00:30:33.120 --> 00:30:35.149 align:start position:0% also going to decode the actual parameters<00:30:33.779> that<00:30:34.260> are<00:30:34.380> encoded<00:30:34.740> in<00:30:34.919> the<00:30:35.039> call 00:30:35.149 --> 00:30:35.159 align:start position:0% parameters that are encoded in the call 00:30:35.159 --> 00:30:39.049 align:start position:0% parameters that are encoded in the call data<00:30:35.580> as<00:30:35.760> well<00:30:35.940> just<00:30:36.659> because<00:30:36.840> we<00:30:37.260> can 00:30:39.049 --> 00:30:39.059 align:start position:0% data as well just because we can 00:30:39.059 --> 00:30:39.710 align:start position:0% data as well just because we can um 00:30:39.710 --> 00:30:39.720 align:start position:0% um 00:30:39.720 --> 00:30:43.250 align:start position:0% um and<00:30:40.559> in<00:30:40.860> order<00:30:40.980> to<00:30:41.159> do<00:30:41.399> that 00:30:43.250 --> 00:30:43.260 align:start position:0% and in order to do that 00:30:43.260 --> 00:30:48.289 align:start position:0% and in order to do that we<00:30:44.039> are<00:30:44.159> going<00:30:44.340> to<00:30:44.460> add<00:30:44.880> a 00:30:48.289 --> 00:30:48.299 align:start position:0% 00:30:48.299 --> 00:30:50.870 align:start position:0% another<00:30:48.720> package 00:30:50.870 --> 00:30:50.880 align:start position:0% another package 00:30:50.880 --> 00:30:54.590 align:start position:0% another package called<00:30:51.799> Abi<00:30:52.799> utils 00:30:54.590 --> 00:30:54.600 align:start position:0% called Abi utils 00:30:54.600 --> 00:30:56.090 align:start position:0% called Abi utils uh 00:30:56.090 --> 00:30:56.100 align:start position:0% uh 00:30:56.100 --> 00:30:58.380 align:start position:0% uh to<00:30:56.640> our<00:30:56.820> snap 00:30:58.380 --> 00:30:58.390 align:start position:0% to our snap 00:30:58.390 --> 00:31:01.330 align:start position:0% to our snap [Music] 00:31:01.330 --> 00:31:01.340 align:start position:0% [Music] 00:31:01.340 --> 00:31:05.090 align:start position:0% [Music] spooky<00:31:02.340> Workshop 00:31:05.090 --> 00:31:05.100 align:start position:0% 00:31:05.100 --> 00:31:07.250 align:start position:0% and<00:31:05.820> that's<00:31:05.940> too<00:31:06.179> much<00:31:06.299> yeah<00:31:06.480> yeah<00:31:06.659> well<00:31:06.899> will 00:31:07.250 --> 00:31:07.260 align:start position:0% and that's too much yeah yeah well will 00:31:07.260 --> 00:31:08.930 align:start position:0% and that's too much yeah yeah well will it<00:31:07.500> someone<00:31:07.679> someone<00:31:07.980> will<00:31:08.279> no<00:31:08.460> doubt<00:31:08.760> figure 00:31:08.930 --> 00:31:08.940 align:start position:0% it someone someone will no doubt figure 00:31:08.940 --> 00:31:11.649 align:start position:0% it someone someone will no doubt figure out<00:31:09.179> the<00:31:09.419> right<00:31:09.600> level 00:31:11.649 --> 00:31:11.659 align:start position:0% out the right level 00:31:11.659 --> 00:31:17.990 align:start position:0% out the right level uh<00:31:12.659> and<00:31:13.020> we<00:31:13.200> have<00:31:13.320> another<00:31:13.500> snippet<00:31:14.220> uh<00:31:15.000> hey 00:31:17.990 --> 00:31:18.000 align:start position:0% uh and we have another snippet uh hey 00:31:18.000 --> 00:31:20.149 align:start position:0% uh and we have another snippet uh hey if<00:31:18.360> we<00:31:18.480> increase<00:31:18.720> the<00:31:19.320> frequency<00:31:19.679> there<00:31:19.980> a 00:31:20.149 --> 00:31:20.159 align:start position:0% if we increase the frequency there a 00:31:20.159 --> 00:31:21.769 align:start position:0% if we increase the frequency there a little<00:31:20.279> bit<00:31:20.399> like<00:31:20.760> we<00:31:21.000> can<00:31:21.179> really<00:31:21.419> create 00:31:21.769 --> 00:31:21.779 align:start position:0% little bit like we can really create 00:31:21.779 --> 00:31:25.090 align:start position:0% little bit like we can really create Magic<00:31:22.140> in<00:31:22.440> here 00:31:25.090 --> 00:31:25.100 align:start position:0% 00:31:25.100 --> 00:31:30.110 align:start position:0% uh<00:31:26.100> and<00:31:26.880> so<00:31:27.000> this<00:31:27.419> uh 00:31:30.110 --> 00:31:30.120 align:start position:0% 00:31:30.120 --> 00:31:34.010 align:start position:0% and<00:31:31.020> so<00:31:31.200> uh<00:31:31.860> this<00:31:32.399> uh<00:31:32.580> this<00:31:32.880> ABI<00:31:33.240> utils<00:31:33.720> package 00:31:34.010 --> 00:31:34.020 align:start position:0% and so uh this uh this ABI utils package 00:31:34.020 --> 00:31:35.690 align:start position:0% and so uh this uh this ABI utils package has<00:31:34.200> an<00:31:34.380> encode<00:31:34.740> and<00:31:34.919> a<00:31:35.039> decode<00:31:35.340> function 00:31:35.690 --> 00:31:35.700 align:start position:0% has an encode and a decode function 00:31:35.700 --> 00:31:38.330 align:start position:0% has an encode and a decode function which<00:31:36.000> allows<00:31:36.360> you<00:31:36.419> to<00:31:36.659> decode<00:31:37.440> and<00:31:37.559> encode<00:31:37.980> uh 00:31:38.330 --> 00:31:38.340 align:start position:0% which allows you to decode and encode uh 00:31:38.340 --> 00:31:41.870 align:start position:0% which allows you to decode and encode uh call<00:31:38.520> data<00:31:39.000> and<00:31:39.840> it<00:31:40.679> has 00:31:41.870 --> 00:31:41.880 align:start position:0% call data and it has 00:31:41.880 --> 00:31:44.630 align:start position:0% call data and it has uh<00:31:42.720> it<00:31:43.020> returns<00:31:43.440> values<00:31:43.740> that<00:31:43.919> are<00:31:44.039> not<00:31:44.220> Json 00:31:44.630 --> 00:31:44.640 align:start position:0% uh it returns values that are not Json 00:31:44.640 --> 00:31:47.990 align:start position:0% uh it returns values that are not Json serializable<00:31:45.899> and<00:31:46.679> that<00:31:47.399> doesn't<00:31:47.640> work 00:31:47.990 --> 00:31:48.000 align:start position:0% serializable and that doesn't work 00:31:48.000 --> 00:31:50.149 align:start position:0% serializable and that doesn't work because<00:31:48.360> the<00:31:48.899> transaction<00:31:49.260> insights<00:31:49.860> need<00:31:50.039> to 00:31:50.149 --> 00:31:50.159 align:start position:0% because the transaction insights need to 00:31:50.159 --> 00:31:52.430 align:start position:0% because the transaction insights need to be<00:31:50.220> Json<00:31:50.580> serializable<00:31:51.299> so<00:31:51.840> this<00:31:52.020> is<00:31:52.080> just<00:31:52.260> a 00:31:52.430 --> 00:31:52.440 align:start position:0% be Json serializable so this is just a 00:31:52.440 --> 00:31:54.529 align:start position:0% be Json serializable so this is just a function<00:31:52.679> that<00:31:52.980> handles<00:31:53.279> that<00:31:53.640> uh<00:31:54.240> and<00:31:54.419> we're 00:31:54.529 --> 00:31:54.539 align:start position:0% function that handles that uh and we're 00:31:54.539 --> 00:31:56.149 align:start position:0% function that handles that uh and we're not<00:31:54.720> going<00:31:54.840> to<00:31:54.960> worry<00:31:55.020> about<00:31:55.260> what<00:31:55.620> it<00:31:55.740> does<00:31:55.860> in 00:31:56.149 --> 00:31:56.159 align:start position:0% not going to worry about what it does in 00:31:56.159 --> 00:31:57.430 align:start position:0% not going to worry about what it does in detail 00:31:57.430 --> 00:31:57.440 align:start position:0% detail 00:31:57.440 --> 00:32:00.710 align:start position:0% detail at<00:31:58.440> the<00:31:59.039> code 00:32:00.710 --> 00:32:00.720 align:start position:0% at the code 00:32:00.720 --> 00:32:02.389 align:start position:0% at the code parameters 00:32:02.389 --> 00:32:02.399 align:start position:0% parameters 00:32:02.399 --> 00:32:04.930 align:start position:0% parameters and<00:32:03.000> so<00:32:03.179> we<00:32:03.419> are<00:32:03.539> going<00:32:03.720> to<00:32:03.899> import 00:32:04.930 --> 00:32:04.940 align:start position:0% and so we are going to import 00:32:04.940 --> 00:32:08.510 align:start position:0% and so we are going to import encode<00:32:05.940> from 00:32:08.510 --> 00:32:08.520 align:start position:0% encode from 00:32:08.520 --> 00:32:11.510 align:start position:0% encode from metamask<00:32:09.360> API<00:32:09.899> utils 00:32:11.510 --> 00:32:11.520 align:start position:0% metamask API utils 00:32:11.520 --> 00:32:17.510 align:start position:0% metamask API utils stupendous 00:32:17.510 --> 00:32:17.520 align:start position:0% 00:32:17.520 --> 00:32:20.090 align:start position:0% and<00:32:18.120> for<00:32:18.480> this<00:32:18.840> one 00:32:20.090 --> 00:32:20.100 align:start position:0% and for this one 00:32:20.100 --> 00:32:22.250 align:start position:0% and for this one we<00:32:20.700> need<00:32:20.940> to<00:32:21.179> now<00:32:21.539> we<00:32:21.779> need<00:32:21.899> to<00:32:21.960> do<00:32:22.080> some 00:32:22.250 --> 00:32:22.260 align:start position:0% we need to now we need to do some 00:32:22.260 --> 00:32:23.630 align:start position:0% we need to now we need to do some slicing 00:32:23.630 --> 00:32:23.640 align:start position:0% slicing 00:32:23.640 --> 00:32:26.630 align:start position:0% slicing because<00:32:24.539> first<00:32:24.960> we<00:32:25.260> need<00:32:25.500> to<00:32:25.799> extract<00:32:26.279> the 00:32:26.630 --> 00:32:26.640 align:start position:0% because first we need to extract the 00:32:26.640 --> 00:32:29.810 align:start position:0% because first we need to extract the actual<00:32:26.940> parameter<00:32:27.480> types<00:32:28.100> from<00:32:29.100> the<00:32:29.520> function 00:32:29.810 --> 00:32:29.820 align:start position:0% actual parameter types from the function 00:32:29.820 --> 00:32:31.669 align:start position:0% actual parameter types from the function text<00:32:30.120> signature<00:32:30.720> and<00:32:31.200> we're<00:32:31.260> going<00:32:31.440> to<00:32:31.559> do 00:32:31.669 --> 00:32:31.679 align:start position:0% text signature and we're going to do 00:32:31.679 --> 00:32:35.630 align:start position:0% text signature and we're going to do that<00:32:31.799> by<00:32:32.100> some<00:32:32.340> good<00:32:32.520> old-fashioned<00:32:33.360> uh 00:32:35.630 --> 00:32:35.640 align:start position:0% that by some good old-fashioned uh 00:32:35.640 --> 00:32:38.690 align:start position:0% that by some good old-fashioned uh a<00:32:36.179> string<00:32:36.539> parsing 00:32:38.690 --> 00:32:38.700 align:start position:0% a string parsing 00:32:38.700 --> 00:32:41.029 align:start position:0% a string parsing and<00:32:39.240> so<00:32:39.360> we<00:32:39.600> are<00:32:39.779> going<00:32:39.899> to<00:32:40.020> do<00:32:40.200> function<00:32:40.679> tick 00:32:41.029 --> 00:32:41.039 align:start position:0% and so we are going to do function tick 00:32:41.039 --> 00:32:42.710 align:start position:0% and so we are going to do function tick signature 00:32:42.710 --> 00:32:42.720 align:start position:0% signature 00:32:42.720 --> 00:32:45.470 align:start position:0% signature and<00:32:43.200> it's<00:32:43.320> going<00:32:43.559> to<00:32:43.620> be<00:32:43.740> a<00:32:43.980> slice<00:32:44.460> and<00:32:45.240> it's 00:32:45.470 --> 00:32:45.480 align:start position:0% and it's going to be a slice and it's 00:32:45.480 --> 00:32:48.169 align:start position:0% and it's going to be a slice and it's going<00:32:45.659> to<00:32:45.840> be<00:32:45.960> an<00:32:46.320> index<00:32:46.740> of<00:32:47.340> the<00:32:47.580> first 00:32:48.169 --> 00:32:48.179 align:start position:0% going to be an index of the first 00:32:48.179 --> 00:32:52.130 align:start position:0% going to be an index of the first parenthesis<00:32:48.840> plus<00:32:49.200> one<00:32:49.559> uh 00:32:52.130 --> 00:32:52.140 align:start position:0% parenthesis plus one uh 00:32:52.140 --> 00:32:54.470 align:start position:0% parenthesis plus one uh my<00:32:52.620> ID<00:32:52.799> is<00:32:53.100> leaking<00:32:53.460> that<00:32:53.700> I've<00:32:53.940> already<00:32:54.120> done 00:32:54.470 --> 00:32:54.480 align:start position:0% my ID is leaking that I've already done 00:32:54.480 --> 00:32:57.830 align:start position:0% my ID is leaking that I've already done this<00:32:54.659> earlier<00:32:55.140> today 00:32:57.830 --> 00:32:57.840 align:start position:0% 00:32:57.840 --> 00:33:02.529 align:start position:0% and<00:32:58.500> then<00:32:58.799> we<00:32:59.159> are<00:32:59.340> going<00:32:59.640> to<00:33:00.299> split 00:33:02.529 --> 00:33:02.539 align:start position:0% and then we are going to split 00:33:02.539 --> 00:33:04.389 align:start position:0% and then we are going to split uh 00:33:04.389 --> 00:33:04.399 align:start position:0% uh 00:33:04.399 --> 00:33:08.870 align:start position:0% uh right<00:33:05.399> because<00:33:05.700> if<00:33:06.120> you<00:33:06.860> uh<00:33:07.860> you'll<00:33:08.520> recall 00:33:08.870 --> 00:33:08.880 align:start position:0% right because if you uh you'll recall 00:33:08.880 --> 00:33:11.510 align:start position:0% right because if you uh you'll recall that<00:33:09.120> this<00:33:09.360> looks<00:33:09.659> something<00:33:09.840> like<00:33:10.520> a 00:33:11.510 --> 00:33:11.520 align:start position:0% that this looks something like a 00:33:11.520 --> 00:33:17.950 align:start position:0% that this looks something like a function<00:33:12.059> name<00:33:13.100> type<00:33:14.100> one<00:33:14.640> comma<00:33:15.539> type 00:33:17.950 --> 00:33:17.960 align:start position:0% 00:33:17.960 --> 00:33:20.330 align:start position:0% so<00:33:18.960> we're<00:33:19.080> just<00:33:19.200> going<00:33:19.320> to<00:33:19.500> extract<00:33:19.919> this 00:33:20.330 --> 00:33:20.340 align:start position:0% so we're just going to extract this 00:33:20.340 --> 00:33:22.190 align:start position:0% so we're just going to extract this substring<00:33:20.820> split<00:33:21.179> on<00:33:21.299> the<00:33:21.419> commas<00:33:21.720> and<00:33:22.140> then 00:33:22.190 --> 00:33:22.200 align:start position:0% substring split on the commas and then 00:33:22.200 --> 00:33:24.590 align:start position:0% substring split on the commas and then we're<00:33:22.380> going<00:33:22.440> to<00:33:22.559> have<00:33:22.679> the<00:33:22.799> parameter<00:33:23.159> types 00:33:24.590 --> 00:33:24.600 align:start position:0% we're going to have the parameter types 00:33:24.600 --> 00:33:26.450 align:start position:0% we're going to have the parameter types and<00:33:25.140> the<00:33:25.440> reason<00:33:25.500> we<00:33:25.740> need<00:33:25.919> that<00:33:26.039> is<00:33:26.279> because 00:33:26.450 --> 00:33:26.460 align:start position:0% and the reason we need that is because 00:33:26.460 --> 00:33:29.750 align:start position:0% and the reason we need that is because that<00:33:26.880> is<00:33:27.059> an<00:33:27.360> input<00:33:27.659> to<00:33:28.140> the<00:33:29.159> um 00:33:29.750 --> 00:33:29.760 align:start position:0% that is an input to the um 00:33:29.760 --> 00:33:31.909 align:start position:0% that is an input to the um decode<00:33:30.600> function 00:33:31.909 --> 00:33:31.919 align:start position:0% decode function 00:33:31.919 --> 00:33:34.730 align:start position:0% decode function so<00:33:32.519> then<00:33:32.640> we<00:33:32.820> are<00:33:33.000> going<00:33:33.179> to<00:33:33.480> decode 00:33:34.730 --> 00:33:34.740 align:start position:0% so then we are going to decode 00:33:34.740 --> 00:33:36.470 align:start position:0% so then we are going to decode [Music] 00:33:36.470 --> 00:33:36.480 align:start position:0% [Music] 00:33:36.480 --> 00:33:41.630 align:start position:0% [Music] uh<00:33:37.320> the<00:33:37.860> let's<00:33:38.460> see<00:33:38.700> parameter<00:33:39.419> types 00:33:41.630 --> 00:33:41.640 align:start position:0% uh the let's see parameter types 00:33:41.640 --> 00:33:43.690 align:start position:0% uh the let's see parameter types let's<00:33:42.179> see 00:33:43.690 --> 00:33:43.700 align:start position:0% let's see 00:33:43.700 --> 00:33:49.850 align:start position:0% let's see const<00:33:44.700> decoded<00:33:45.539> equals 00:33:49.850 --> 00:33:49.860 align:start position:0% 00:33:49.860 --> 00:33:56.169 align:start position:0% and<00:33:50.519> let's<00:33:50.760> see<00:33:51.000> the<00:33:51.299> next<00:33:51.419> thing<00:33:51.600> I<00:33:51.840> want<00:33:52.080> is 00:33:56.169 --> 00:33:56.179 align:start position:0% 00:33:56.179 --> 00:34:00.169 align:start position:0% yes<00:33:57.179> now<00:33:57.840> I<00:33:58.200> want<00:33:58.500> the<00:33:58.980> transaction<00:33:59.460> data 00:34:00.169 --> 00:34:00.179 align:start position:0% yes now I want the transaction data 00:34:00.179 --> 00:34:02.210 align:start position:0% yes now I want the transaction data without 00:34:02.210 --> 00:34:02.220 align:start position:0% without 00:34:02.220 --> 00:34:04.190 align:start position:0% without uh 00:34:04.190 --> 00:34:04.200 align:start position:0% uh 00:34:04.200 --> 00:34:06.710 align:start position:0% uh the<00:34:04.620> function<00:34:04.799> signature 00:34:06.710 --> 00:34:06.720 align:start position:0% the function signature 00:34:06.720 --> 00:34:09.829 align:start position:0% the function signature and<00:34:07.140> why<00:34:07.320> wouldn't<00:34:07.500> that<00:34:07.799> work 00:34:09.829 --> 00:34:09.839 align:start position:0% and why wouldn't that work 00:34:09.839 --> 00:34:19.849 align:start position:0% and why wouldn't that work no 00:34:19.849 --> 00:34:19.859 align:start position:0% 00:34:19.859 --> 00:34:30.950 align:start position:0% foreign 00:34:30.950 --> 00:34:30.960 align:start position:0% 00:34:30.960 --> 00:34:33.710 align:start position:0% okay<00:34:31.639> and<00:34:32.639> so<00:34:32.879> that's<00:34:33.000> going<00:34:33.240> to<00:34:33.300> give<00:34:33.359> us<00:34:33.480> the 00:34:33.710 --> 00:34:33.720 align:start position:0% okay and so that's going to give us the 00:34:33.720 --> 00:34:35.690 align:start position:0% okay and so that's going to give us the decoded<00:34:34.200> stuff 00:34:35.690 --> 00:34:35.700 align:start position:0% decoded stuff 00:34:35.700 --> 00:34:39.829 align:start position:0% decoded stuff and 00:34:39.829 --> 00:34:39.839 align:start position:0% 00:34:39.839 --> 00:34:42.050 align:start position:0% the<00:34:40.679> we're<00:34:41.040> going<00:34:41.159> to<00:34:41.220> decode<00:34:41.520> the<00:34:41.700> parameter 00:34:42.050 --> 00:34:42.060 align:start position:0% the we're going to decode the parameter 00:34:42.060 --> 00:34:44.149 align:start position:0% the we're going to decode the parameter types<00:34:42.359> out<00:34:42.599> of<00:34:42.720> the<00:34:42.839> transaction<00:34:43.320> uh<00:34:43.980> call 00:34:44.149 --> 00:34:44.159 align:start position:0% types out of the transaction uh call 00:34:44.159 --> 00:34:47.450 align:start position:0% types out of the transaction uh call data<00:34:44.700> and<00:34:45.419> just<00:34:45.599> to<00:34:45.780> make<00:34:46.020> sure<00:34:46.320> I'm<00:34:47.040> going<00:34:47.280> to 00:34:47.450 --> 00:34:47.460 align:start position:0% data and just to make sure I'm going to 00:34:47.460 --> 00:34:49.930 align:start position:0% data and just to make sure I'm going to cheat<00:34:47.700> again<00:34:48.119> really<00:34:48.599> quickly 00:34:49.930 --> 00:34:49.940 align:start position:0% cheat again really quickly 00:34:49.940 --> 00:34:52.909 align:start position:0% cheat again really quickly uh<00:34:50.940> normally<00:34:51.419> I<00:34:51.659> would<00:34:51.780> have<00:34:51.899> my<00:34:52.080> notes<00:34:52.440> off<00:34:52.679> to 00:34:52.909 --> 00:34:52.919 align:start position:0% uh normally I would have my notes off to 00:34:52.919 --> 00:34:54.950 align:start position:0% uh normally I would have my notes off to the<00:34:53.040> side<00:34:53.280> uh<00:34:54.179> so<00:34:54.300> you<00:34:54.480> wouldn't<00:34:54.599> know<00:34:54.780> that 00:34:54.950 --> 00:34:54.960 align:start position:0% the side uh so you wouldn't know that 00:34:54.960 --> 00:34:56.030 align:start position:0% the side uh so you wouldn't know that I'm<00:34:55.139> cheating 00:34:56.030 --> 00:34:56.040 align:start position:0% I'm cheating 00:34:56.040 --> 00:35:00.770 align:start position:0% I'm cheating uh<00:34:57.000> but<00:34:57.300> but<00:34:57.420> life<00:34:57.720> is<00:34:57.900> not<00:34:58.080> fair<00:34:58.320> sometimes 00:35:00.770 --> 00:35:00.780 align:start position:0% uh but but life is not fair sometimes 00:35:00.780 --> 00:35:02.710 align:start position:0% uh but but life is not fair sometimes and<00:35:01.260> then<00:35:01.320> we're<00:35:01.500> gonna<00:35:01.619> sit 00:35:02.710 --> 00:35:02.720 align:start position:0% and then we're gonna sit 00:35:02.720 --> 00:35:06.589 align:start position:0% and then we're gonna sit insights.params<00:35:03.720> to<00:35:04.020> decoded 00:35:06.589 --> 00:35:06.599 align:start position:0% insights.params to decoded 00:35:06.599 --> 00:35:08.690 align:start position:0% insights.params to decoded we're<00:35:06.900> going<00:35:07.080> to<00:35:07.140> map<00:35:07.440> that<00:35:07.800> with<00:35:08.220> our<00:35:08.460> value 00:35:08.690 --> 00:35:08.700 align:start position:0% we're going to map that with our value 00:35:08.700 --> 00:35:14.569 align:start position:0% we're going to map that with our value normalizer 00:35:14.569 --> 00:35:14.579 align:start position:0% 00:35:14.579 --> 00:35:20.210 align:start position:0% and<00:35:15.240> then<00:35:15.480> we<00:35:15.900> should<00:35:16.200> be 00:35:20.210 --> 00:35:20.220 align:start position:0% 00:35:20.220 --> 00:35:22.790 align:start position:0% now<00:35:20.579> we<00:35:20.880> should<00:35:21.000> be<00:35:21.119> in<00:35:21.240> good<00:35:21.480> shape 00:35:22.790 --> 00:35:22.800 align:start position:0% now we should be in good shape 00:35:22.800 --> 00:35:28.790 align:start position:0% now we should be in good shape foreign 00:35:28.790 --> 00:35:28.800 align:start position:0% 00:35:28.800 --> 00:35:39.550 align:start position:0% I<00:35:29.700> just<00:35:30.540> want<00:35:30.660> decode 00:35:39.550 --> 00:35:39.560 align:start position:0% 00:35:39.560 --> 00:35:44.270 align:start position:0% all<00:35:40.560> right 00:35:44.270 --> 00:35:44.280 align:start position:0% 00:35:44.280 --> 00:35:46.609 align:start position:0% now<00:35:44.640> we're<00:35:44.820> going<00:35:44.940> to<00:35:44.940> reconnect<00:35:45.300> again<00:35:45.619> so 00:35:46.609 --> 00:35:46.619 align:start position:0% now we're going to reconnect again so 00:35:46.619 --> 00:35:49.550 align:start position:0% now we're going to reconnect again so that<00:35:46.859> metamask<00:35:47.520> alerts<00:35:47.940> our<00:35:48.060> changes 00:35:49.550 --> 00:35:49.560 align:start position:0% that metamask alerts our changes 00:35:49.560 --> 00:35:52.790 align:start position:0% that metamask alerts our changes we're<00:35:49.859> going<00:35:49.980> to<00:35:50.040> send<00:35:50.220> a<00:35:50.400> message 00:35:52.790 --> 00:35:52.800 align:start position:0% 00:35:52.800 --> 00:35:56.829 align:start position:0% we're<00:35:53.099> going<00:35:53.160> to<00:35:53.280> open<00:35:53.460> this<00:35:53.700> up 00:35:56.829 --> 00:35:56.839 align:start position:0% 00:35:56.839 --> 00:35:59.630 align:start position:0% hey<00:35:57.839> parameters 00:35:59.630 --> 00:35:59.640 align:start position:0% hey parameters 00:35:59.640 --> 00:36:02.569 align:start position:0% hey parameters uh<00:36:00.359> address<00:36:00.540> and<00:36:01.140> Boolean<00:36:01.680> just<00:36:02.160> as<00:36:02.280> we<00:36:02.460> would 00:36:02.569 --> 00:36:02.579 align:start position:0% uh address and Boolean just as we would 00:36:02.579 --> 00:36:05.150 align:start position:0% uh address and Boolean just as we would expect<00:36:02.760> from<00:36:03.000> the<00:36:03.119> function<00:36:03.300> type<00:36:03.740> and<00:36:04.740> so<00:36:04.859> now 00:36:05.150 --> 00:36:05.160 align:start position:0% expect from the function type and so now 00:36:05.160 --> 00:36:07.010 align:start position:0% expect from the function type and so now and<00:36:05.520> so<00:36:05.700> this<00:36:06.000> is<00:36:06.119> so<00:36:06.420> obviously<00:36:06.720> like<00:36:06.839> we're 00:36:07.010 --> 00:36:07.020 align:start position:0% and so this is so obviously like we're 00:36:07.020 --> 00:36:08.270 align:start position:0% and so this is so obviously like we're not<00:36:07.140> going<00:36:07.260> super<00:36:07.500> deep<00:36:07.740> and<00:36:07.920> like<00:36:08.160> just 00:36:08.270 --> 00:36:08.280 align:start position:0% not going super deep and like just 00:36:08.280 --> 00:36:09.770 align:start position:0% not going super deep and like just seeing<00:36:08.579> the<00:36:08.700> parameters<00:36:09.000> here<00:36:09.240> is<00:36:09.359> not<00:36:09.599> super 00:36:09.770 --> 00:36:09.780 align:start position:0% seeing the parameters here is not super 00:36:09.780 --> 00:36:12.109 align:start position:0% seeing the parameters here is not super useful<00:36:10.200> but<00:36:10.380> the<00:36:10.500> but<00:36:10.800> the<00:36:10.920> point<00:36:11.099> that<00:36:11.760> that 00:36:12.109 --> 00:36:12.119 align:start position:0% useful but the but the point that that 00:36:12.119 --> 00:36:14.089 align:start position:0% useful but the but the point that that uh<00:36:12.720> we're<00:36:12.900> illustrating<00:36:13.260> here<00:36:13.500> is<00:36:13.680> that<00:36:13.920> like 00:36:14.089 --> 00:36:14.099 align:start position:0% uh we're illustrating here is that like 00:36:14.099 --> 00:36:16.790 align:start position:0% uh we're illustrating here is that like you<00:36:14.579> know<00:36:14.640> this<00:36:14.880> snap<00:36:15.060> is<00:36:15.359> pretty<00:36:15.540> much<00:36:15.800> aside 00:36:16.790 --> 00:36:16.800 align:start position:0% you know this snap is pretty much aside 00:36:16.800 --> 00:36:18.410 align:start position:0% you know this snap is pretty much aside from<00:36:16.920> hitting<00:36:17.220> four<00:36:17.339> byte<00:36:17.700> like<00:36:17.820> it's<00:36:17.940> a<00:36:18.180> it's 00:36:18.410 --> 00:36:18.420 align:start position:0% from hitting four byte like it's a it's 00:36:18.420 --> 00:36:20.210 align:start position:0% from hitting four byte like it's a it's self-contained<00:36:18.960> it<00:36:19.079> uses<00:36:19.380> like<00:36:19.560> very<00:36:19.800> basic 00:36:20.210 --> 00:36:20.220 align:start position:0% self-contained it uses like very basic 00:36:20.220 --> 00:36:21.829 align:start position:0% self-contained it uses like very basic like<00:36:20.400> Utilities<00:36:20.820> in<00:36:21.060> order<00:36:21.180> to<00:36:21.300> like<00:36:21.540> tell 00:36:21.829 --> 00:36:21.839 align:start position:0% like Utilities in order to like tell 00:36:21.839 --> 00:36:23.750 align:start position:0% like Utilities in order to like tell useful<00:36:22.260> information<00:36:22.500> and<00:36:22.859> obviously<00:36:23.280> we 00:36:23.750 --> 00:36:23.760 align:start position:0% useful information and obviously we 00:36:23.760 --> 00:36:26.329 align:start position:0% useful information and obviously we could<00:36:23.940> dig<00:36:24.420> deeper<00:36:24.900> into<00:36:25.500> the<00:36:25.740> call<00:36:25.859> data<00:36:26.220> it's 00:36:26.329 --> 00:36:26.339 align:start position:0% could dig deeper into the call data it's 00:36:26.339 --> 00:36:28.609 align:start position:0% could dig deeper into the call data it's like<00:36:26.520> yeah<00:36:26.640> like<00:36:26.880> if<00:36:27.060> we<00:36:27.180> wanted<00:36:27.359> to<00:36:27.599> or<00:36:28.380> like 00:36:28.609 --> 00:36:28.619 align:start position:0% like yeah like if we wanted to or like 00:36:28.619 --> 00:36:30.710 align:start position:0% like yeah like if we wanted to or like fetch<00:36:28.980> you<00:36:29.160> know<00:36:29.280> the<00:36:29.640> compiled<00:36:30.420> contract 00:36:30.710 --> 00:36:30.720 align:start position:0% fetch you know the compiled contract 00:36:30.720 --> 00:36:32.510 align:start position:0% fetch you know the compiled contract code<00:36:30.960> and<00:36:31.140> try<00:36:31.320> to<00:36:31.440> like<00:36:31.560> say<00:36:32.040> something<00:36:32.280> about 00:36:32.510 --> 00:36:32.520 align:start position:0% code and try to like say something about 00:36:32.520 --> 00:36:35.810 align:start position:0% code and try to like say something about that<00:36:32.820> and<00:36:33.480> so<00:36:33.599> I<00:36:33.720> mentioned<00:36:34.079> one<00:36:34.320> of<00:36:34.440> the<00:36:34.820> uh 00:36:35.810 --> 00:36:35.820 align:start position:0% that and so I mentioned one of the uh 00:36:35.820 --> 00:36:37.250 align:start position:0% that and so I mentioned one of the uh one<00:36:36.060> of<00:36:36.119> the<00:36:36.180> snaps<00:36:36.540> that<00:36:36.660> got<00:36:36.839> built<00:36:37.079> at<00:36:37.140> the 00:36:37.250 --> 00:36:37.260 align:start position:0% one of the snaps that got built at the 00:36:37.260 --> 00:36:39.050 align:start position:0% one of the snaps that got built at the hackathon<00:36:37.740> recently<00:36:38.339> and<00:36:38.520> we've<00:36:38.700> had<00:36:38.880> a 00:36:39.050 --> 00:36:39.060 align:start position:0% hackathon recently and we've had a 00:36:39.060 --> 00:36:41.510 align:start position:0% hackathon recently and we've had a couple<00:36:39.240> of<00:36:39.480> these<00:36:39.780> built<00:36:40.140> so<00:36:40.440> far<00:36:40.619> is<00:36:41.040> by<00:36:41.400> the 00:36:41.510 --> 00:36:41.520 align:start position:0% couple of these built so far is by the 00:36:41.520 --> 00:36:43.490 align:start position:0% couple of these built so far is by the community<00:36:41.700> which<00:36:42.240> is<00:36:42.359> just<00:36:42.540> like<00:36:42.720> snaps<00:36:43.380> that 00:36:43.490 --> 00:36:43.500 align:start position:0% community which is just like snaps that 00:36:43.500 --> 00:36:45.470 align:start position:0% community which is just like snaps that do<00:36:43.740> they<00:36:44.339> know<00:36:44.520> something<00:36:44.700> about<00:36:45.000> contract 00:36:45.470 --> 00:36:45.480 align:start position:0% do they know something about contract 00:36:45.480 --> 00:36:47.630 align:start position:0% do they know something about contract security<00:36:45.720> or<00:36:46.200> have<00:36:46.560> like<00:36:46.800> a<00:36:46.920> list<00:36:47.040> of<00:36:47.220> accounts 00:36:47.630 --> 00:36:47.640 align:start position:0% security or have like a list of accounts 00:36:47.640 --> 00:36:50.750 align:start position:0% security or have like a list of accounts or<00:36:47.880> addresses<00:36:48.420> that<00:36:48.540> are<00:36:48.660> unsafe<00:36:49.099> uh<00:36:50.099> and<00:36:50.400> will 00:36:50.750 --> 00:36:50.760 align:start position:0% or addresses that are unsafe uh and will 00:36:50.760 --> 00:36:52.910 align:start position:0% or addresses that are unsafe uh and will display<00:36:51.660> some<00:36:52.020> information<00:36:52.200> to<00:36:52.560> the<00:36:52.619> user 00:36:52.910 --> 00:36:52.920 align:start position:0% display some information to the user 00:36:52.920 --> 00:36:54.530 align:start position:0% display some information to the user when<00:36:53.040> they're<00:36:53.220> like<00:36:53.400> hey<00:36:53.820> like<00:36:54.119> this<00:36:54.300> isn't 00:36:54.530 --> 00:36:54.540 align:start position:0% when they're like hey like this isn't 00:36:54.540 --> 00:36:56.150 align:start position:0% when they're like hey like this isn't going<00:36:54.660> to<00:36:54.780> work<00:36:54.960> and<00:36:55.560> you<00:36:55.740> could<00:36:55.800> just<00:36:55.980> as 00:36:56.150 --> 00:36:56.160 align:start position:0% going to work and you could just as 00:36:56.160 --> 00:36:59.270 align:start position:0% going to work and you could just as easily<00:36:56.900> uh<00:36:57.900> imagine<00:36:58.260> like<00:36:58.859> you<00:36:59.160> could<00:36:59.220> even 00:36:59.270 --> 00:36:59.280 align:start position:0% easily uh imagine like you could even 00:36:59.280 --> 00:37:02.210 align:start position:0% easily uh imagine like you could even run<00:36:59.579> ganache<00:37:00.480> inside<00:37:00.660> of<00:37:01.380> a<00:37:01.619> snap<00:37:01.740> in<00:37:01.980> order<00:37:02.099> to 00:37:02.210 --> 00:37:02.220 align:start position:0% run ganache inside of a snap in order to 00:37:02.220 --> 00:37:05.390 align:start position:0% run ganache inside of a snap in order to simulate<00:37:02.640> the<00:37:02.820> transaction<00:37:03.380> or<00:37:04.380> like<00:37:04.800> hit<00:37:05.280> a 00:37:05.390 --> 00:37:05.400 align:start position:0% simulate the transaction or like hit a 00:37:05.400 --> 00:37:06.950 align:start position:0% simulate the transaction or like hit a tenderly<00:37:05.820> endpoint<00:37:06.180> or<00:37:06.480> whatever<00:37:06.660> like 00:37:06.950 --> 00:37:06.960 align:start position:0% tenderly endpoint or whatever like 00:37:06.960 --> 00:37:09.589 align:start position:0% tenderly endpoint or whatever like service<00:37:07.200> that<00:37:07.560> you<00:37:07.859> imagine<00:37:08.339> in<00:37:09.060> order<00:37:09.180> to<00:37:09.300> add 00:37:09.589 --> 00:37:09.599 align:start position:0% service that you imagine in order to add 00:37:09.599 --> 00:37:12.290 align:start position:0% service that you imagine in order to add like<00:37:09.839> useful<00:37:10.200> data<00:37:10.619> that<00:37:11.099> you<00:37:11.339> know<00:37:11.520> about<00:37:11.700> and 00:37:12.290 --> 00:37:12.300 align:start position:0% like useful data that you know about and 00:37:12.300 --> 00:37:15.470 align:start position:0% like useful data that you know about and that<00:37:12.660> metamask<00:37:13.140> does<00:37:13.680> not<00:37:13.859> know<00:37:14.040> about<00:37:14.220> uh<00:37:15.180> for 00:37:15.470 --> 00:37:15.480 align:start position:0% that metamask does not know about uh for 00:37:15.480 --> 00:37:18.069 align:start position:0% that metamask does not know about uh for any<00:37:15.599> given<00:37:16.020> contract<00:37:16.320> interaction 00:37:18.069 --> 00:37:18.079 align:start position:0% any given contract interaction 00:37:18.079 --> 00:37:21.950 align:start position:0% any given contract interaction and<00:37:19.079> that<00:37:19.680> is<00:37:19.859> a<00:37:20.099> wrap<00:37:20.400> for<00:37:20.820> the<00:37:21.000> workshop<00:37:21.420> and 00:37:21.950 --> 00:37:21.960 align:start position:0% and that is a wrap for the workshop and 00:37:21.960 --> 00:37:24.950 align:start position:0% and that is a wrap for the workshop and I<00:37:22.500> am<00:37:22.619> happy<00:37:22.800> to<00:37:22.980> take<00:37:23.400> uh<00:37:23.940> questions<00:37:24.180> for<00:37:24.720> the 00:37:24.950 --> 00:37:24.960 align:start position:0% I am happy to take uh questions for the 00:37:24.960 --> 00:37:27.200 align:start position:0% I am happy to take uh questions for the remaining<00:37:25.560> time<00:37:25.740> that<00:37:25.920> we<00:37:26.040> have 00:37:27.200 --> 00:37:27.210 align:start position:0% remaining time that we have 00:37:27.210 --> 00:37:28.000 align:start position:0% remaining time that we have [Applause] 00:37:28.000 --> 00:37:28.010 align:start position:0% [Applause] 00:37:28.010 --> 00:37:32.770 align:start position:0% [Applause] [Music] 00:37:32.770 --> 00:37:32.780 align:start position:0% 00:37:32.780 --> 00:37:35.950 align:start position:0% and<00:37:33.780> you<00:37:34.440> were<00:37:34.560> you<00:37:34.800> were<00:37:34.980> fast 00:37:35.950 --> 00:37:35.960 align:start position:0% and you were you were fast 00:37:35.960 --> 00:37:38.270 align:start position:0% and you were you were fast so<00:37:36.960> I<00:37:37.079> really<00:37:37.140> like<00:37:37.320> it<00:37:37.500> and<00:37:37.800> I<00:37:38.040> can<00:37:38.099> definitely 00:37:38.270 --> 00:37:38.280 align:start position:0% so I really like it and I can definitely 00:37:38.280 --> 00:37:40.190 align:start position:0% so I really like it and I can definitely see<00:37:38.520> a<00:37:38.640> lot<00:37:38.760> of<00:37:38.880> use<00:37:39.060> cases<00:37:39.359> where<00:37:39.780> I<00:37:39.960> would<00:37:40.079> use 00:37:40.190 --> 00:37:40.200 align:start position:0% see a lot of use cases where I would use 00:37:40.200 --> 00:37:42.589 align:start position:0% see a lot of use cases where I would use it<00:37:40.380> my<00:37:40.740> only<00:37:40.920> concern<00:37:41.400> is<00:37:42.000> that<00:37:42.119> I<00:37:42.300> often<00:37:42.540> have 00:37:42.589 --> 00:37:42.599 align:start position:0% it my only concern is that I often have 00:37:42.599 --> 00:37:44.270 align:start position:0% it my only concern is that I often have to<00:37:42.780> support<00:37:42.900> other<00:37:43.200> wallets<00:37:43.680> so<00:37:43.859> for<00:37:44.099> instance 00:37:44.270 --> 00:37:44.280 align:start position:0% to support other wallets so for instance 00:37:44.280 --> 00:37:46.370 align:start position:0% to support other wallets so for instance if<00:37:44.640> one<00:37:45.119> base<00:37:45.359> wallet<00:37:45.660> which<00:37:45.839> to<00:37:46.020> be<00:37:46.079> honest<00:37:46.260> I 00:37:46.370 --> 00:37:46.380 align:start position:0% if one base wallet which to be honest I 00:37:46.380 --> 00:37:47.750 align:start position:0% if one base wallet which to be honest I don't<00:37:46.500> like<00:37:46.619> as<00:37:46.800> much<00:37:46.980> because<00:37:47.160> it's<00:37:47.400> not<00:37:47.579> open 00:37:47.750 --> 00:37:47.760 align:start position:0% don't like as much because it's not open 00:37:47.760 --> 00:37:49.130 align:start position:0% don't like as much because it's not open source 00:37:49.130 --> 00:37:49.140 align:start position:0% source 00:37:49.140 --> 00:37:52.250 align:start position:0% source um<00:37:49.260> so<00:37:49.800> would<00:37:50.400> it<00:37:50.520> be<00:37:50.640> possible<00:37:51.060> or<00:37:51.780> do<00:37:51.960> you<00:37:52.079> see 00:37:52.250 --> 00:37:52.260 align:start position:0% um so would it be possible or do you see 00:37:52.260 --> 00:37:53.510 align:start position:0% um so would it be possible or do you see other<00:37:52.500> while<00:37:52.740> it's<00:37:52.920> implementing<00:37:53.400> anything 00:37:53.510 --> 00:37:53.520 align:start position:0% other while it's implementing anything 00:37:53.520 --> 00:37:55.730 align:start position:0% other while it's implementing anything like<00:37:53.880> this<00:37:54.000> or<00:37:54.300> do<00:37:54.540> you<00:37:54.660> see<00:37:54.780> any<00:37:55.020> support<00:37:55.260> from 00:37:55.730 --> 00:37:55.740 align:start position:0% like this or do you see any support from 00:37:55.740 --> 00:37:57.589 align:start position:0% like this or do you see any support from like<00:37:55.980> other<00:37:56.099> tooling<00:37:56.640> you<00:37:57.359> know<00:37:57.480> the 00:37:57.589 --> 00:37:57.599 align:start position:0% like other tooling you know the 00:37:57.599 --> 00:37:59.510 align:start position:0% like other tooling you know the community<00:37:57.780> uses<00:37:58.140> like<00:37:58.380> ethers<00:37:58.920> or<00:37:59.040> wasps 00:37:59.510 --> 00:37:59.520 align:start position:0% community uses like ethers or wasps 00:37:59.520 --> 00:38:02.210 align:start position:0% community uses like ethers or wasps support<00:38:00.240> this<00:38:00.540> or<00:38:00.900> maybe<00:38:01.140> in<00:38:01.320> a<00:38:01.500> way<00:38:01.560> that<00:38:01.859> if 00:38:02.210 --> 00:38:02.220 align:start position:0% support this or maybe in a way that if 00:38:02.220 --> 00:38:03.950 align:start position:0% support this or maybe in a way that if I'm<00:38:02.339> in<00:38:02.520> metamask<00:38:02.940> I<00:38:03.180> have<00:38:03.300> a<00:38:03.420> snap<00:38:03.540> but<00:38:03.780> in 00:38:03.950 --> 00:38:03.960 align:start position:0% I'm in metamask I have a snap but in 00:38:03.960 --> 00:38:05.890 align:start position:0% I'm in metamask I have a snap but in other<00:38:04.079> places<00:38:04.320> it's<00:38:04.619> not<00:38:04.800> broken<00:38:04.980> right<00:38:05.700> right 00:38:05.890 --> 00:38:05.900 align:start position:0% other places it's not broken right right 00:38:05.900 --> 00:38:10.310 align:start position:0% other places it's not broken right right and<00:38:06.900> so<00:38:07.339> the<00:38:08.339> uh<00:38:09.119> so<00:38:09.420> we<00:38:09.540> are<00:38:09.660> trying<00:38:09.900> to<00:38:10.079> create 00:38:10.310 --> 00:38:10.320 align:start position:0% and so the uh so we are trying to create 00:38:10.320 --> 00:38:13.310 align:start position:0% and so the uh so we are trying to create uh<00:38:11.220> specifications<00:38:11.820> for<00:38:12.540> like<00:38:12.720> the<00:38:12.900> Manifest 00:38:13.310 --> 00:38:13.320 align:start position:0% uh specifications for like the Manifest 00:38:13.320 --> 00:38:16.609 align:start position:0% uh specifications for like the Manifest and<00:38:13.500> the<00:38:13.619> apis<00:38:13.980> that<00:38:14.280> we<00:38:14.400> ship<00:38:14.640> and<00:38:15.599> so<00:38:15.720> on<00:38:15.900> uh 00:38:16.609 --> 00:38:16.619 align:start position:0% and the apis that we ship and so on uh 00:38:16.619 --> 00:38:17.930 align:start position:0% and the apis that we ship and so on uh we<00:38:16.800> have<00:38:16.920> a<00:38:16.980> lot<00:38:17.099> of<00:38:17.160> work<00:38:17.280> that<00:38:17.520> I<00:38:17.640> won't<00:38:17.700> have 00:38:17.930 --> 00:38:17.940 align:start position:0% we have a lot of work that I won't have 00:38:17.940 --> 00:38:19.550 align:start position:0% we have a lot of work that I won't have time<00:38:18.180> in<00:38:18.540> progress<00:38:18.780> that<00:38:19.020> I<00:38:19.140> won't<00:38:19.200> have<00:38:19.380> time 00:38:19.550 --> 00:38:19.560 align:start position:0% time in progress that I won't have time 00:38:19.560 --> 00:38:20.990 align:start position:0% time in progress that I won't have time to<00:38:19.800> talk<00:38:19.980> about 00:38:20.990 --> 00:38:21.000 align:start position:0% to talk about 00:38:21.000 --> 00:38:24.109 align:start position:0% to talk about um<00:38:21.060> but<00:38:21.839> like<00:38:22.140> using<00:38:23.040> something<00:38:23.579> like<00:38:23.820> wallet 00:38:24.109 --> 00:38:24.119 align:start position:0% um but like using something like wallet 00:38:24.119 --> 00:38:26.329 align:start position:0% um but like using something like wallet connect<00:38:24.300> V2<00:38:24.720> to<00:38:25.079> like 00:38:26.329 --> 00:38:26.339 align:start position:0% connect V2 to like 00:38:26.339 --> 00:38:29.270 align:start position:0% connect V2 to like um<00:38:26.400> you<00:38:26.820> know<00:38:26.940> are<00:38:27.359> just<00:38:27.599> like<00:38:27.780> the<00:38:28.680> the<00:38:28.740> dapple 00:38:29.270 --> 00:38:29.280 align:start position:0% um you know are just like the the dapple 00:38:29.280 --> 00:38:31.069 align:start position:0% um you know are just like the the dapple just<00:38:29.520> ask<00:38:29.700> for<00:38:30.000> the<00:38:30.119> network<00:38:30.240> that<00:38:30.660> it<00:38:30.780> wants 00:38:31.069 --> 00:38:31.079 align:start position:0% just ask for the network that it wants 00:38:31.079 --> 00:38:32.810 align:start position:0% just ask for the network that it wants and<00:38:31.320> then<00:38:31.440> metamask<00:38:31.920> will<00:38:32.099> go<00:38:32.280> and<00:38:32.400> find<00:38:32.579> the 00:38:32.810 --> 00:38:32.820 align:start position:0% and then metamask will go and find the 00:38:32.820 --> 00:38:35.089 align:start position:0% and then metamask will go and find the snap<00:38:32.940> that<00:38:33.240> supports<00:38:33.599> it<00:38:33.720> and<00:38:33.960> add<00:38:34.140> it<00:38:34.320> as<00:38:34.859> part 00:38:35.089 --> 00:38:35.099 align:start position:0% snap that supports it and add it as part 00:38:35.099 --> 00:38:37.670 align:start position:0% snap that supports it and add it as part of<00:38:35.220> like<00:38:35.400> the<00:38:35.579> connection<00:38:35.700> flow<00:38:36.320> uh<00:38:37.320> so<00:38:37.560> you 00:38:37.670 --> 00:38:37.680 align:start position:0% of like the connection flow uh so you 00:38:37.680 --> 00:38:39.770 align:start position:0% of like the connection flow uh so you don't<00:38:37.800> have<00:38:37.980> to<00:38:38.099> like<00:38:38.339> call<00:38:38.880> a<00:38:39.180> specific<00:38:39.480> snap 00:38:39.770 --> 00:38:39.780 align:start position:0% don't have to like call a specific snap 00:38:39.780 --> 00:38:41.569 align:start position:0% don't have to like call a specific snap in<00:38:40.020> order<00:38:40.140> to<00:38:40.260> interact<00:38:40.500> with<00:38:40.680> it<00:38:40.859> and<00:38:41.400> so 00:38:41.569 --> 00:38:41.579 align:start position:0% in order to interact with it and so 00:38:41.579 --> 00:38:42.950 align:start position:0% in order to interact with it and so we're<00:38:41.700> trying<00:38:41.880> to<00:38:42.060> create<00:38:42.240> specifications 00:38:42.950 --> 00:38:42.960 align:start position:0% we're trying to create specifications 00:38:42.960 --> 00:38:45.650 align:start position:0% we're trying to create specifications for<00:38:43.260> those<00:38:43.440> things<00:38:43.680> and<00:38:44.339> I<00:38:44.700> can't<00:38:44.880> talk<00:38:45.060> like 00:38:45.650 --> 00:38:45.660 align:start position:0% for those things and I can't talk like 00:38:45.660 --> 00:38:47.270 align:start position:0% for those things and I can't talk like really<00:38:45.900> about<00:38:46.079> concrete<00:38:46.680> plans<00:38:46.980> at<00:38:47.099> this 00:38:47.270 --> 00:38:47.280 align:start position:0% really about concrete plans at this 00:38:47.280 --> 00:38:49.550 align:start position:0% really about concrete plans at this point<00:38:47.400> but<00:38:47.760> uh<00:38:48.060> personally<00:38:48.480> like<00:38:48.839> my<00:38:49.200> I<00:38:49.440> would 00:38:49.550 --> 00:38:49.560 align:start position:0% point but uh personally like my I would 00:38:49.560 --> 00:38:52.310 align:start position:0% point but uh personally like my I would love<00:38:49.740> to<00:38:49.920> see<00:38:50.099> snaps<00:38:50.579> become<00:38:50.940> like<00:38:51.420> an<00:38:52.140> open 00:38:52.310 --> 00:38:52.320 align:start position:0% love to see snaps become like an open 00:38:52.320 --> 00:38:54.589 align:start position:0% love to see snaps become like an open standard<00:38:52.859> and<00:38:53.400> like<00:38:53.520> for<00:38:53.760> there<00:38:53.880> to<00:38:54.119> be<00:38:54.240> like 00:38:54.589 --> 00:38:54.599 align:start position:0% standard and like for there to be like 00:38:54.599 --> 00:38:58.190 align:start position:0% standard and like for there to be like an<00:38:54.839> open<00:38:54.960> source<00:38:55.440> like<00:38:55.680> wallet<00:38:56.339> kernel<00:38:56.820> uh<00:38:57.720> or 00:38:58.190 --> 00:38:58.200 align:start position:0% an open source like wallet kernel uh or 00:38:58.200 --> 00:38:59.990 align:start position:0% an open source like wallet kernel uh or something<00:38:58.440> that<00:38:58.859> like<00:38:59.040> others<00:38:59.400> can<00:38:59.520> build<00:38:59.760> on 00:38:59.990 --> 00:39:00.000 align:start position:0% something that like others can build on 00:39:00.000 --> 00:39:02.329 align:start position:0% something that like others can build on uh<00:39:00.420> in<00:39:00.660> the<00:39:00.780> future<00:39:00.900> yeah 00:39:02.329 --> 00:39:02.339 align:start position:0% uh in the future yeah 00:39:02.339 --> 00:39:06.700 align:start position:0% uh in the future yeah sure<00:39:02.880> and<00:39:03.540> I<00:39:03.780> think<00:39:03.960> I<00:39:04.680> saw<00:39:05.040> you<00:39:05.820> next<00:39:06.240> time 00:39:06.700 --> 00:39:06.710 align:start position:0% sure and I think I saw you next time 00:39:06.710 --> 00:39:14.750 align:start position:0% sure and I think I saw you next time [Music] 00:39:14.750 --> 00:39:14.760 align:start position:0% 00:39:14.760 --> 00:39:18.589 align:start position:0% yes<00:39:15.420> yes<00:39:15.480> correct 00:39:18.589 --> 00:39:18.599 align:start position:0% 00:39:18.599 --> 00:39:21.470 align:start position:0% uh<00:39:19.440> so<00:39:19.740> uh<00:39:20.099> there<00:39:20.339> is<00:39:20.460> so<00:39:20.760> there<00:39:20.940> is<00:39:21.060> no 00:39:21.470 --> 00:39:21.480 align:start position:0% uh so uh there is so there is no 00:39:21.480 --> 00:39:23.450 align:start position:0% uh so uh there is so there is no Marketplace<00:39:21.900> as<00:39:22.200> yet<00:39:22.440> if<00:39:22.800> anyone<00:39:23.099> wants<00:39:23.400> to 00:39:23.450 --> 00:39:23.460 align:start position:0% Marketplace as yet if anyone wants to 00:39:23.460 --> 00:39:25.190 align:start position:0% Marketplace as yet if anyone wants to build<00:39:23.640> their<00:39:23.880> Marketplace<00:39:24.300> we<00:39:24.660> would<00:39:24.780> love<00:39:24.960> to 00:39:25.190 --> 00:39:25.200 align:start position:0% build their Marketplace we would love to 00:39:25.200 --> 00:39:27.470 align:start position:0% build their Marketplace we would love to see<00:39:25.380> that<00:39:25.619> being<00:39:25.859> built<00:39:26.280> because<00:39:26.579> we<00:39:27.300> don't 00:39:27.470 --> 00:39:27.480 align:start position:0% see that being built because we don't 00:39:27.480 --> 00:39:29.390 align:start position:0% see that being built because we don't want<00:39:27.780> to<00:39:27.900> be<00:39:28.140> we<00:39:28.560> don't<00:39:28.680> want<00:39:28.859> to<00:39:28.980> have<00:39:29.099> an<00:39:29.220> app 00:39:29.390 --> 00:39:29.400 align:start position:0% want to be we don't want to have an app 00:39:29.400 --> 00:39:31.250 align:start position:0% want to be we don't want to have an app store<00:39:29.579> we<00:39:30.180> want<00:39:30.300> it<00:39:30.420> to<00:39:30.540> be<00:39:30.660> like<00:39:30.780> a<00:39:30.960> full<00:39:31.079> and 00:39:31.250 --> 00:39:31.260 align:start position:0% store we want it to be like a full and 00:39:31.260 --> 00:39:34.250 align:start position:0% store we want it to be like a full and open<00:39:31.500> open<00:39:31.579> permissionless<00:39:32.579> ecosystem<00:39:33.260> uh 00:39:34.250 --> 00:39:34.260 align:start position:0% open open permissionless ecosystem uh 00:39:34.260 --> 00:39:38.329 align:start position:0% open open permissionless ecosystem uh and<00:39:34.619> so<00:39:35.220> at<00:39:35.640> when<00:39:36.000> right<00:39:36.720> now<00:39:37.040> uh<00:39:38.040> the<00:39:38.160> way<00:39:38.280> it 00:39:38.329 --> 00:39:38.339 align:start position:0% and so at when right now uh the way it 00:39:38.339 --> 00:39:39.589 align:start position:0% and so at when right now uh the way it works<00:39:38.520> is<00:39:38.640> like<00:39:38.760> when<00:39:38.880> a<00:39:39.000> snap<00:39:39.119> is<00:39:39.300> published 00:39:39.589 --> 00:39:39.599 align:start position:0% works is like when a snap is published 00:39:39.599 --> 00:39:42.050 align:start position:0% works is like when a snap is published to<00:39:39.720> npm<00:39:40.140> like<00:39:40.800> if<00:39:41.040> you<00:39:41.160> have<00:39:41.220> metamask<00:39:41.700> flask 00:39:42.050 --> 00:39:42.060 align:start position:0% to npm like if you have metamask flask 00:39:42.060 --> 00:39:44.329 align:start position:0% to npm like if you have metamask flask you<00:39:42.359> can<00:39:42.480> install<00:39:42.599> and<00:39:42.900> run<00:39:43.079> that<00:39:43.320> snap<00:39:43.560> and 00:39:44.329 --> 00:39:44.339 align:start position:0% you can install and run that snap and 00:39:44.339 --> 00:39:46.130 align:start position:0% you can install and run that snap and any<00:39:44.579> website<00:39:44.940> that<00:39:45.180> like<00:39:45.359> knows<00:39:45.780> how<00:39:45.900> to<00:39:46.020> talk 00:39:46.130 --> 00:39:46.140 align:start position:0% any website that like knows how to talk 00:39:46.140 --> 00:39:49.430 align:start position:0% any website that like knows how to talk to<00:39:46.260> it<00:39:46.440> it<00:39:46.859> can<00:39:47.099> just<00:39:47.280> can<00:39:47.520> talk<00:39:47.820> to<00:39:47.940> it<00:39:48.480> uh<00:39:49.200> and 00:39:49.430 --> 00:39:49.440 align:start position:0% to it it can just can talk to it uh and 00:39:49.440 --> 00:39:52.430 align:start position:0% to it it can just can talk to it uh and so<00:39:49.619> and<00:39:49.920> once<00:39:50.220> we<00:39:50.339> get<00:39:50.460> to<00:39:50.520> stable<00:39:51.140> uh<00:39:52.140> they're 00:39:52.430 --> 00:39:52.440 align:start position:0% so and once we get to stable uh they're 00:39:52.440 --> 00:39:55.190 align:start position:0% so and once we get to stable uh they're like<00:39:52.859> they're<00:39:53.820> you<00:39:54.480> know<00:39:54.599> we're<00:39:54.780> gonna<00:39:54.900> we're 00:39:55.190 --> 00:39:55.200 align:start position:0% like they're you know we're gonna we're 00:39:55.200 --> 00:39:56.750 align:start position:0% like they're you know we're gonna we're gonna<00:39:55.320> have<00:39:55.500> like<00:39:55.740> a<00:39:55.980> essentially<00:39:56.400> like<00:39:56.640> a 00:39:56.750 --> 00:39:56.760 align:start position:0% gonna have like a essentially like a 00:39:56.760 --> 00:39:58.609 align:start position:0% gonna have like a essentially like a block<00:39:56.940> list<00:39:57.180> if<00:39:58.020> like<00:39:58.200> there<00:39:58.320> are<00:39:58.500> known 00:39:58.609 --> 00:39:58.619 align:start position:0% block list if like there are known 00:39:58.619 --> 00:39:59.870 align:start position:0% block list if like there are known malicious<00:39:59.040> snaps<00:39:59.339> and<00:39:59.460> things<00:39:59.579> of<00:39:59.760> that 00:39:59.870 --> 00:39:59.880 align:start position:0% malicious snaps and things of that 00:39:59.880 --> 00:40:01.849 align:start position:0% malicious snaps and things of that nature<00:40:00.240> but<00:40:00.720> really<00:40:00.900> in<00:40:01.200> order<00:40:01.320> for<00:40:01.560> this<00:40:01.680> to 00:40:01.849 --> 00:40:01.859 align:start position:0% nature but really in order for this to 00:40:01.859 --> 00:40:03.470 align:start position:0% nature but really in order for this to scale<00:40:02.160> there<00:40:02.579> is<00:40:02.760> going<00:40:02.880> to<00:40:02.940> need<00:40:03.060> to<00:40:03.180> be<00:40:03.300> like 00:40:03.470 --> 00:40:03.480 align:start position:0% scale there is going to need to be like 00:40:03.480 --> 00:40:06.290 align:start position:0% scale there is going to need to be like a<00:40:03.780> Yelp<00:40:04.140> for<00:40:04.440> snaps<00:40:04.859> essentially<00:40:05.339> uh<00:40:06.060> in<00:40:06.180> order 00:40:06.290 --> 00:40:06.300 align:start position:0% a Yelp for snaps essentially uh in order 00:40:06.300 --> 00:40:08.089 align:start position:0% a Yelp for snaps essentially uh in order for<00:40:06.480> people<00:40:06.599> to<00:40:06.839> like<00:40:07.200> be<00:40:07.500> able<00:40:07.619> to<00:40:07.740> establish 00:40:08.089 --> 00:40:08.099 align:start position:0% for people to like be able to establish 00:40:08.099 --> 00:40:11.210 align:start position:0% for people to like be able to establish trust<00:40:08.579> uh<00:40:09.000> in<00:40:09.240> them<00:40:09.420> uh<00:40:10.200> because<00:40:10.380> uh<00:40:10.800> we<00:40:10.980> do<00:40:11.099> not 00:40:11.210 --> 00:40:11.220 align:start position:0% trust uh in them uh because uh we do not 00:40:11.220 --> 00:40:13.130 align:start position:0% trust uh in them uh because uh we do not want<00:40:11.339> to<00:40:11.460> be<00:40:11.579> in<00:40:11.700> the<00:40:11.820> business<00:40:11.940> of<00:40:12.420> running<00:40:12.960> an 00:40:13.130 --> 00:40:13.140 align:start position:0% want to be in the business of running an 00:40:13.140 --> 00:40:14.990 align:start position:0% want to be in the business of running an app<00:40:13.320> store<00:40:13.500> because<00:40:13.920> it's<00:40:14.220> antithetical<00:40:14.820> to 00:40:14.990 --> 00:40:15.000 align:start position:0% app store because it's antithetical to 00:40:15.000 --> 00:40:17.630 align:start position:0% app store because it's antithetical to the<00:40:15.180> values<00:40:15.359> of<00:40:15.540> web3<00:40:15.900> and<00:40:16.560> also<00:40:16.800> it<00:40:17.099> sucks<00:40:17.280> as 00:40:17.630 --> 00:40:17.640 align:start position:0% the values of web3 and also it sucks as 00:40:17.640 --> 00:40:18.950 align:start position:0% the values of web3 and also it sucks as a<00:40:17.820> job 00:40:18.950 --> 00:40:18.960 align:start position:0% a job 00:40:18.960 --> 00:40:21.730 align:start position:0% a job um<00:40:19.280> uh<00:40:20.280> does<00:40:20.520> that<00:40:20.700> answer<00:40:20.820> your<00:40:21.060> question 00:40:21.730 --> 00:40:21.740 align:start position:0% um uh does that answer your question 00:40:21.740 --> 00:40:24.950 align:start position:0% um uh does that answer your question Splendid<00:40:22.740> and<00:40:23.460> I<00:40:23.640> I<00:40:23.940> think<00:40:24.180> you<00:40:24.480> were<00:40:24.780> next 00:40:24.950 --> 00:40:24.960 align:start position:0% Splendid and I I think you were next 00:40:24.960 --> 00:40:29.120 align:start position:0% Splendid and I I think you were next also 00:40:29.120 --> 00:40:29.130 align:start position:0% 00:40:29.130 --> 00:40:35.589 align:start position:0% [Music] 00:40:35.589 --> 00:40:35.599 align:start position:0% 00:40:35.599 --> 00:40:41.050 align:start position:0% yes<00:40:36.599> so<00:40:37.140> uh<00:40:37.560> so<00:40:37.800> that's<00:40:37.980> like<00:40:38.359> uh<00:40:39.380> so 00:40:41.050 --> 00:40:41.060 align:start position:0% yes so uh so that's like uh so 00:40:41.060 --> 00:40:44.810 align:start position:0% yes so uh so that's like uh so recently<00:40:42.060> if<00:40:42.660> you<00:40:42.960> uh<00:40:43.500> follow<00:40:43.859> uh<00:40:44.400> like<00:40:44.640> news 00:40:44.810 --> 00:40:44.820 align:start position:0% recently if you uh follow uh like news 00:40:44.820 --> 00:40:46.569 align:start position:0% recently if you uh follow uh like news about<00:40:45.000> app<00:40:45.240> stores<00:40:45.480> and<00:40:45.780> stuff 00:40:46.569 --> 00:40:46.579 align:start position:0% about app stores and stuff 00:40:46.579 --> 00:40:51.710 align:start position:0% about app stores and stuff uh<00:40:47.579> there<00:40:48.480> was<00:40:48.960> an<00:40:49.380> instance<00:40:49.740> where<00:40:50.540> uh<00:40:51.540> like 00:40:51.710 --> 00:40:51.720 align:start position:0% uh there was an instance where uh like 00:40:51.720 --> 00:40:52.910 align:start position:0% uh there was an instance where uh like there<00:40:51.900> are<00:40:52.020> essentially<00:40:52.200> two<00:40:52.440> philosophy 00:40:52.910 --> 00:40:52.920 align:start position:0% there are essentially two philosophy 00:40:52.920 --> 00:40:54.589 align:start position:0% there are essentially two philosophy philosophies<00:40:53.700> that<00:40:53.940> you<00:40:54.060> can<00:40:54.119> use<00:40:54.300> to 00:40:54.589 --> 00:40:54.599 align:start position:0% philosophies that you can use to 00:40:54.599 --> 00:40:56.210 align:start position:0% philosophies that you can use to approach<00:40:54.900> it<00:40:55.079> like<00:40:55.260> the<00:40:55.440> sort<00:40:55.740> of<00:40:55.859> wild<00:40:55.980> garden 00:40:56.210 --> 00:40:56.220 align:start position:0% approach it like the sort of wild garden 00:40:56.220 --> 00:40:57.890 align:start position:0% approach it like the sort of wild garden App<00:40:56.520> Store<00:40:56.700> approach<00:40:57.060> that<00:40:57.240> exists<00:40:57.540> right<00:40:57.720> now 00:40:57.890 --> 00:40:57.900 align:start position:0% App Store approach that exists right now 00:40:57.900 --> 00:40:59.870 align:start position:0% App Store approach that exists right now and<00:40:58.560> what<00:40:58.740> we<00:40:58.859> want<00:40:59.099> to<00:40:59.220> do<00:40:59.339> which<00:40:59.579> is<00:40:59.700> a 00:40:59.870 --> 00:40:59.880 align:start position:0% and what we want to do which is a 00:40:59.880 --> 00:41:02.150 align:start position:0% and what we want to do which is a permissionless<00:41:00.359> web<00:41:00.599> of<00:41:00.839> trust<00:41:01.140> model<00:41:01.380> and 00:41:02.150 --> 00:41:02.160 align:start position:0% permissionless web of trust model and 00:41:02.160 --> 00:41:04.609 align:start position:0% permissionless web of trust model and and<00:41:02.400> so<00:41:02.700> in<00:41:03.000> the<00:41:03.060> App<00:41:03.180> Store<00:41:03.359> model<00:41:03.720> it 00:41:04.609 --> 00:41:04.619 align:start position:0% and so in the App Store model it 00:41:04.619 --> 00:41:06.349 align:start position:0% and so in the App Store model it basically<00:41:04.859> relies<00:41:05.280> on<00:41:05.520> like<00:41:05.700> executive 00:41:06.349 --> 00:41:06.359 align:start position:0% basically relies on like executive 00:41:06.359 --> 00:41:08.510 align:start position:0% basically relies on like executive oversight<00:41:06.780> and<00:41:07.020> like<00:41:07.200> review<00:41:07.440> of<00:41:07.859> the<00:41:08.099> tenders 00:41:08.510 --> 00:41:08.520 align:start position:0% oversight and like review of the tenders 00:41:08.520 --> 00:41:10.670 align:start position:0% oversight and like review of the tenders of<00:41:08.760> the<00:41:08.880> wild<00:41:09.000> garden<00:41:09.240> like<00:41:09.720> for<00:41:09.960> scams<00:41:10.440> to<00:41:10.560> not 00:41:10.670 --> 00:41:10.680 align:start position:0% of the wild garden like for scams to not 00:41:10.680 --> 00:41:14.510 align:start position:0% of the wild garden like for scams to not be<00:41:10.859> presented<00:41:11.460> but<00:41:12.180> like<00:41:12.540> just<00:41:12.839> the<00:41:13.200> other<00:41:13.560> uh 00:41:14.510 --> 00:41:14.520 align:start position:0% be presented but like just the other uh 00:41:14.520 --> 00:41:18.290 align:start position:0% be presented but like just the other uh week<00:41:14.880> I<00:41:15.660> think<00:41:15.839> Facebook<00:41:16.880> reported<00:41:17.880> to<00:41:18.060> Google 00:41:18.290 --> 00:41:18.300 align:start position:0% week I think Facebook reported to Google 00:41:18.300 --> 00:41:20.630 align:start position:0% week I think Facebook reported to Google a<00:41:18.839> list<00:41:19.020> of<00:41:19.200> like<00:41:19.440> hundreds<00:41:19.980> of<00:41:20.099> malicious 00:41:20.630 --> 00:41:20.640 align:start position:0% a list of like hundreds of malicious 00:41:20.640 --> 00:41:22.790 align:start position:0% a list of like hundreds of malicious Android<00:41:20.940> apps<00:41:21.420> whose<00:41:21.780> only<00:41:21.900> purpose<00:41:22.320> was<00:41:22.560> to 00:41:22.790 --> 00:41:22.800 align:start position:0% Android apps whose only purpose was to 00:41:22.800 --> 00:41:25.970 align:start position:0% Android apps whose only purpose was to steal<00:41:23.099> Facebook<00:41:23.339> credentials<00:41:24.440> uh<00:41:25.440> and<00:41:25.740> so 00:41:25.970 --> 00:41:25.980 align:start position:0% steal Facebook credentials uh and so 00:41:25.980 --> 00:41:28.130 align:start position:0% steal Facebook credentials uh and so even<00:41:26.460> like<00:41:26.760> with<00:41:27.000> executive<00:41:27.540> and<00:41:27.720> oversight 00:41:28.130 --> 00:41:28.140 align:start position:0% even like with executive and oversight 00:41:28.140 --> 00:41:30.650 align:start position:0% even like with executive and oversight like<00:41:28.320> it's<00:41:28.560> it's<00:41:28.800> impossible<00:41:29.460> to<00:41:29.880> uh<00:41:30.119> to<00:41:30.420> fully 00:41:30.650 --> 00:41:30.660 align:start position:0% like it's it's impossible to uh to fully 00:41:30.660 --> 00:41:32.930 align:start position:0% like it's it's impossible to uh to fully prevent<00:41:30.960> scams<00:41:31.500> and<00:41:31.980> I<00:41:32.099> think<00:41:32.280> the<00:41:32.520> best<00:41:32.640> way 00:41:32.930 --> 00:41:32.940 align:start position:0% prevent scams and I think the best way 00:41:32.940 --> 00:41:34.790 align:start position:0% prevent scams and I think the best way that<00:41:33.180> even<00:41:33.300> in<00:41:33.420> an<00:41:33.540> app<00:41:33.720> store<00:41:34.140> model<00:41:34.440> that<00:41:34.740> you 00:41:34.790 --> 00:41:34.800 align:start position:0% that even in an app store model that you 00:41:34.800 --> 00:41:36.470 align:start position:0% that even in an app store model that you actually<00:41:34.980> establish<00:41:35.460> trust<00:41:35.880> in<00:41:36.000> something<00:41:36.180> as 00:41:36.470 --> 00:41:36.480 align:start position:0% actually establish trust in something as 00:41:36.480 --> 00:41:38.810 align:start position:0% actually establish trust in something as you<00:41:36.660> look<00:41:36.839> who<00:41:37.560> recommends<00:41:38.099> this<00:41:38.280> how<00:41:38.700> many 00:41:38.810 --> 00:41:38.820 align:start position:0% you look who recommends this how many 00:41:38.820 --> 00:41:40.730 align:start position:0% you look who recommends this how many reviews<00:41:39.060> does<00:41:39.420> it<00:41:39.540> have<00:41:39.720> how<00:41:40.140> many<00:41:40.260> how<00:41:40.560> long 00:41:40.730 --> 00:41:40.740 align:start position:0% reviews does it have how many how long 00:41:40.740 --> 00:41:44.630 align:start position:0% reviews does it have how many how long has<00:41:40.859> it<00:41:41.040> existed<00:41:41.400> and<00:41:42.240> so<00:41:42.540> uh<00:41:43.380> we<00:41:43.920> so<00:41:44.460> that's 00:41:44.630 --> 00:41:44.640 align:start position:0% has it existed and so uh we so that's 00:41:44.640 --> 00:41:47.030 align:start position:0% has it existed and so uh we so that's like<00:41:44.880> why<00:41:45.119> we<00:41:45.420> want<00:41:45.960> and<00:41:46.200> need<00:41:46.380> a<00:41:46.500> market<00:41:46.680> place 00:41:47.030 --> 00:41:47.040 align:start position:0% like why we want and need a market place 00:41:47.040 --> 00:41:49.310 align:start position:0% like why we want and need a market place to<00:41:47.220> exist<00:41:47.520> in<00:41:47.700> order<00:41:47.880> for<00:41:48.180> it<00:41:48.480> to<00:41:48.660> scale<00:41:49.079> to 00:41:49.310 --> 00:41:49.320 align:start position:0% to exist in order for it to scale to 00:41:49.320 --> 00:41:51.290 align:start position:0% to exist in order for it to scale to users<00:41:49.619> without<00:41:49.859> them<00:41:50.160> getting<00:41:50.339> scammed<00:41:50.820> and 00:41:51.290 --> 00:41:51.300 align:start position:0% users without them getting scammed and 00:41:51.300 --> 00:41:53.630 align:start position:0% users without them getting scammed and until<00:41:51.420> we<00:41:51.780> get<00:41:51.900> to<00:41:52.020> that<00:41:52.260> point<00:41:52.520> our<00:41:53.520> first 00:41:53.630 --> 00:41:53.640 align:start position:0% until we get to that point our first 00:41:53.640 --> 00:41:55.430 align:start position:0% until we get to that point our first release<00:41:53.880> is<00:41:54.240> probably<00:41:54.480> going<00:41:54.660> to<00:41:54.839> have<00:41:54.960> like<00:41:55.200> a 00:41:55.430 --> 00:41:55.440 align:start position:0% release is probably going to have like a 00:41:55.440 --> 00:41:58.010 align:start position:0% release is probably going to have like a finite<00:41:55.800> set<00:41:56.220> of<00:41:56.400> snaps<00:41:56.820> that<00:41:56.940> like<00:41:57.240> at<00:41:57.900> least 00:41:58.010 --> 00:41:58.020 align:start position:0% finite set of snaps that like at least 00:41:58.020 --> 00:42:01.190 align:start position:0% finite set of snaps that like at least uh<00:41:58.619> you<00:41:58.859> know<00:41:58.920> we<00:41:59.160> can<00:41:59.339> uh<00:42:00.119> we're<00:42:00.900> confident 00:42:01.190 --> 00:42:01.200 align:start position:0% uh you know we can uh we're confident 00:42:01.200 --> 00:42:02.990 align:start position:0% uh you know we can uh we're confident you<00:42:01.500> know<00:42:01.619> our<00:42:01.920> uh<00:42:02.520> you<00:42:02.700> know<00:42:02.760> we're 00:42:02.990 --> 00:42:03.000 align:start position:0% you know our uh you know we're 00:42:03.000 --> 00:42:04.730 align:start position:0% you know our uh you know we're implemented<00:42:03.540> rigorously<00:42:04.079> if<00:42:04.560> they're 00:42:04.730 --> 00:42:04.740 align:start position:0% implemented rigorously if they're 00:42:04.740 --> 00:42:07.310 align:start position:0% implemented rigorously if they're managing<00:42:05.160> keys<00:42:05.460> they<00:42:05.760> they<00:42:06.180> were<00:42:06.420> perhaps 00:42:07.310 --> 00:42:07.320 align:start position:0% managing keys they they were perhaps 00:42:07.320 --> 00:42:08.930 align:start position:0% managing keys they they were perhaps audited<00:42:07.740> and<00:42:08.160> like<00:42:08.339> we<00:42:08.460> know<00:42:08.640> they're<00:42:08.820> not 00:42:08.930 --> 00:42:08.940 align:start position:0% audited and like we know they're not 00:42:08.940 --> 00:42:10.569 align:start position:0% audited and like we know they're not like<00:42:09.119> outright<00:42:09.540> trying<00:42:09.720> to<00:42:09.839> steal<00:42:10.079> your<00:42:10.200> stuff 00:42:10.569 --> 00:42:10.579 align:start position:0% like outright trying to steal your stuff 00:42:10.579 --> 00:42:13.970 align:start position:0% like outright trying to steal your stuff uh<00:42:11.579> but<00:42:11.820> like<00:42:12.000> but<00:42:12.240> preventing<00:42:12.780> scams<00:42:13.260> in<00:42:13.680> a 00:42:13.970 --> 00:42:13.980 align:start position:0% uh but like but preventing scams in a 00:42:13.980 --> 00:42:15.230 align:start position:0% uh but like but preventing scams in a like<00:42:14.280> permissionless<00:42:14.820> application 00:42:15.230 --> 00:42:15.240 align:start position:0% like permissionless application 00:42:15.240 --> 00:42:17.810 align:start position:0% like permissionless application ecosystem<00:42:15.839> is<00:42:16.380> not<00:42:17.040> a<00:42:17.280> fully<00:42:17.520> solvable 00:42:17.810 --> 00:42:17.820 align:start position:0% ecosystem is not a fully solvable 00:42:17.820 --> 00:42:20.690 align:start position:0% ecosystem is not a fully solvable problem<00:42:18.180> uh<00:42:18.960> but<00:42:19.140> we<00:42:19.320> think<00:42:19.440> by<00:42:19.800> building<00:42:20.220> but 00:42:20.690 --> 00:42:20.700 align:start position:0% problem uh but we think by building but 00:42:20.700 --> 00:42:22.849 align:start position:0% problem uh but we think by building but I<00:42:20.880> but<00:42:21.180> but<00:42:21.240> by<00:42:22.079> investing<00:42:22.380> in<00:42:22.560> the<00:42:22.680> community 00:42:22.849 --> 00:42:22.859 align:start position:0% I but but by investing in the community 00:42:22.859 --> 00:42:26.569 align:start position:0% I but but by investing in the community and<00:42:23.460> then<00:42:23.640> like<00:42:23.940> a<00:42:24.420> Marketplace<00:42:25.280> uh<00:42:26.280> we<00:42:26.460> can 00:42:26.569 --> 00:42:26.579 align:start position:0% and then like a Marketplace uh we can 00:42:26.579 --> 00:42:29.950 align:start position:0% and then like a Marketplace uh we can get<00:42:26.760> there<00:42:27.300> foreign 00:42:29.950 --> 00:42:29.960 align:start position:0% 00:42:29.960 --> 00:42:34.370 align:start position:0% next<00:42:30.960> question 00:42:34.370 --> 00:42:34.380 align:start position:0% 00:42:34.380 --> 00:42:38.870 align:start position:0% uh<00:42:35.280> so<00:42:35.640> uh<00:42:36.119> mobile<00:42:36.420> uh<00:42:37.020> so<00:42:37.260> we've<00:42:37.500> mobile<00:42:38.099> is<00:42:38.520> a 00:42:38.870 --> 00:42:38.880 align:start position:0% uh so uh mobile uh so we've mobile is a 00:42:38.880 --> 00:42:41.210 align:start position:0% uh so uh mobile uh so we've mobile is a TBD<00:42:39.420> it's<00:42:39.960> it's<00:42:40.140> going<00:42:40.380> we're<00:42:40.740> uh<00:42:40.980> we're 00:42:41.210 --> 00:42:41.220 align:start position:0% TBD it's it's going we're uh we're 00:42:41.220 --> 00:42:42.829 align:start position:0% TBD it's it's going we're uh we're working<00:42:41.339> on<00:42:41.579> it<00:42:41.700> at<00:42:42.000> no<00:42:42.180> timelines<00:42:42.660> to 00:42:42.829 --> 00:42:42.839 align:start position:0% working on it at no timelines to 00:42:42.839 --> 00:42:45.050 align:start position:0% working on it at no timelines to announce<00:42:43.140> as<00:42:43.380> of<00:42:43.500> yet 00:42:45.050 --> 00:42:45.060 align:start position:0% announce as of yet 00:42:45.060 --> 00:42:48.710 align:start position:0% announce as of yet no<00:42:45.540> they<00:42:45.900> so<00:42:46.260> so<00:42:46.500> they<00:42:46.980> are<00:42:47.280> uh<00:42:48.119> like<00:42:48.480> the 00:42:48.710 --> 00:42:48.720 align:start position:0% no they so so they are uh like the 00:42:48.720 --> 00:42:50.329 align:start position:0% no they so so they are uh like the execution<00:42:49.140> environment<00:42:49.560> is<00:42:49.740> the<00:42:49.980> same<00:42:50.099> the 00:42:50.329 --> 00:42:50.339 align:start position:0% execution environment is the same the 00:42:50.339 --> 00:42:52.069 align:start position:0% execution environment is the same the goal<00:42:50.579> is<00:42:50.700> for<00:42:50.880> a<00:42:51.000> snap<00:42:51.119> to<00:42:51.420> be<00:42:51.480> unable<00:42:51.780> to<00:42:51.960> tell 00:42:52.069 --> 00:42:52.079 align:start position:0% goal is for a snap to be unable to tell 00:42:52.079 --> 00:42:54.650 align:start position:0% goal is for a snap to be unable to tell if<00:42:52.260> it's<00:42:52.380> executing<00:42:52.859> in<00:42:53.040> the<00:42:53.160> browser<00:42:53.520> uh<00:42:54.480> in 00:42:54.650 --> 00:42:54.660 align:start position:0% if it's executing in the browser uh in 00:42:54.660 --> 00:42:56.690 align:start position:0% if it's executing in the browser uh in the<00:42:54.839> server<00:42:55.079> on<00:42:55.320> a<00:42:55.440> mobile<00:42:55.619> device<00:42:55.920> on<00:42:56.520> an 00:42:56.690 --> 00:42:56.700 align:start position:0% the server on a mobile device on an 00:42:56.700 --> 00:42:59.630 align:start position:0% the server on a mobile device on an abacus<00:42:57.180> uh<00:42:57.599> like<00:42:57.780> shouldn't<00:42:58.140> matter 00:42:59.630 --> 00:42:59.640 align:start position:0% abacus uh like shouldn't matter 00:42:59.640 --> 00:43:06.530 align:start position:0% abacus uh like shouldn't matter yeah<00:43:00.240> that's<00:43:00.660> the<00:43:00.839> that's<00:43:01.079> the<00:43:01.200> guarantee<00:43:01.560> yes 00:43:06.530 --> 00:43:06.540 align:start position:0% 00:43:06.540 --> 00:43:09.050 align:start position:0% yeah<00:43:06.619> so<00:43:07.619> so<00:43:07.800> they<00:43:08.220> are<00:43:08.400> publicly<00:43:08.700> released 00:43:09.050 --> 00:43:09.060 align:start position:0% yeah so so they are publicly released 00:43:09.060 --> 00:43:11.030 align:start position:0% yeah so so they are publicly released right<00:43:09.240> now<00:43:09.359> on<00:43:09.540> a<00:43:09.720> developer<00:43:10.140> channel<00:43:10.319> so<00:43:10.740> like 00:43:11.030 --> 00:43:11.040 align:start position:0% right now on a developer channel so like 00:43:11.040 --> 00:43:12.829 align:start position:0% right now on a developer channel so like you<00:43:11.280> can<00:43:11.400> uh<00:43:11.700> download<00:43:11.880> metamask<00:43:12.359> flask<00:43:12.660> and 00:43:12.829 --> 00:43:12.839 align:start position:0% you can uh download metamask flask and 00:43:12.839 --> 00:43:14.450 align:start position:0% you can uh download metamask flask and just<00:43:12.960> like<00:43:13.079> get<00:43:13.200> started<00:43:13.500> with<00:43:13.740> the<00:43:13.859> ones<00:43:14.040> that 00:43:14.450 --> 00:43:14.460 align:start position:0% just like get started with the ones that 00:43:14.460 --> 00:43:16.430 align:start position:0% just like get started with the ones that exist<00:43:14.819> in<00:43:15.540> terms<00:43:15.720> of<00:43:15.780> release<00:43:15.960> to<00:43:16.200> stable 00:43:16.430 --> 00:43:16.440 align:start position:0% exist in terms of release to stable 00:43:16.440 --> 00:43:18.829 align:start position:0% exist in terms of release to stable we're<00:43:16.680> targeting<00:43:16.980> early<00:43:17.220> next<00:43:17.460> year 00:43:18.829 --> 00:43:18.839 align:start position:0% we're targeting early next year 00:43:18.839 --> 00:43:24.290 align:start position:0% we're targeting early next year uh<00:43:19.560> yes 00:43:24.290 --> 00:43:24.300 align:start position:0% 00:43:24.300 --> 00:43:27.730 align:start position:0% that<00:43:25.140> is<00:43:25.260> a<00:43:25.859> a<00:43:26.099> great<00:43:26.640> question<00:43:26.880> kind<00:43:27.240> stranger 00:43:27.730 --> 00:43:27.740 align:start position:0% that is a a great question kind stranger 00:43:27.740 --> 00:43:33.050 align:start position:0% that is a a great question kind stranger uh<00:43:28.740> and<00:43:29.640> so<00:43:30.119> we<00:43:30.839> have<00:43:30.960> like<00:43:31.200> in<00:43:31.619> the<00:43:31.859> uh<00:43:32.640> in<00:43:32.940> the 00:43:33.050 --> 00:43:33.060 align:start position:0% uh and so we have like in the uh in the 00:43:33.060 --> 00:43:35.150 align:start position:0% uh and so we have like in the uh in the hack<00:43:33.240> MD 00:43:35.150 --> 00:43:35.160 align:start position:0% hack MD 00:43:35.160 --> 00:43:37.309 align:start position:0% hack MD um<00:43:35.280> there<00:43:35.819> are<00:43:35.940> some<00:43:36.119> links<00:43:36.480> at<00:43:36.780> the<00:43:36.900> top<00:43:37.020> that 00:43:37.309 --> 00:43:37.319 align:start position:0% um there are some links at the top that 00:43:37.319 --> 00:43:38.890 align:start position:0% um there are some links at the top that lead<00:43:37.500> you<00:43:37.740> probably 00:43:38.890 --> 00:43:38.900 align:start position:0% lead you probably 00:43:38.900 --> 00:43:41.510 align:start position:0% lead you probably yeah<00:43:39.900> no<00:43:40.140> yeah<00:43:40.500> it's<00:43:40.740> locked<00:43:41.040> whatever<00:43:41.220> no 00:43:41.510 --> 00:43:41.520 align:start position:0% yeah no yeah it's locked whatever no 00:43:41.520 --> 00:43:42.950 align:start position:0% yeah no yeah it's locked whatever no it's<00:43:41.700> on<00:43:41.819> the<00:43:41.940> hack<00:43:42.119> MD<00:43:42.420> which<00:43:42.599> is<00:43:42.720> on<00:43:42.839> the 00:43:42.950 --> 00:43:42.960 align:start position:0% it's on the hack MD which is on the 00:43:42.960 --> 00:43:44.809 align:start position:0% it's on the hack MD which is on the slides<00:43:43.319> which<00:43:43.500> are<00:43:43.680> accessible<00:43:44.040> through<00:43:44.400> the 00:43:44.809 --> 00:43:44.819 align:start position:0% slides which are accessible through the 00:43:44.819 --> 00:43:48.109 align:start position:0% slides which are accessible through the schedule<00:43:45.240> like<00:43:45.660> on<00:43:45.900> on<00:43:46.079> Devcon<00:43:46.619> but<00:43:47.400> uh<00:43:47.819> that 00:43:48.109 --> 00:43:48.119 align:start position:0% schedule like on on Devcon but uh that 00:43:48.119 --> 00:43:50.450 align:start position:0% schedule like on on Devcon but uh that metamask<00:43:48.540> has<00:43:48.780> a<00:43:48.960> repository<00:43:49.380> called<00:43:49.800> snaps 00:43:50.450 --> 00:43:50.460 align:start position:0% metamask has a repository called snaps 00:43:50.460 --> 00:43:53.990 align:start position:0% metamask has a repository called snaps monorepo<00:43:51.180> that<00:43:51.720> snaps<00:43:52.140> Dash<00:43:52.500> mono<00:43:52.859> repo<00:43:53.220> uh 00:43:53.990 --> 00:43:54.000 align:start position:0% monorepo that snaps Dash mono repo uh 00:43:54.000 --> 00:43:55.910 align:start position:0% monorepo that snaps Dash mono repo uh and<00:43:54.180> the<00:43:54.300> discussions<00:43:54.720> in<00:43:55.079> there<00:43:55.319> are<00:43:55.680> a<00:43:55.800> great 00:43:55.910 --> 00:43:55.920 align:start position:0% and the discussions in there are a great 00:43:55.920 --> 00:43:59.030 align:start position:0% and the discussions in there are a great place<00:43:56.160> to<00:43:56.339> get<00:43:56.520> started<00:43:56.880> uh<00:43:57.780> we<00:43:58.020> also<00:43:58.260> have<00:43:58.500> a 00:43:59.030 --> 00:43:59.040 align:start position:0% place to get started uh we also have a 00:43:59.040 --> 00:44:02.690 align:start position:0% place to get started uh we also have a landing<00:43:59.819> page<00:44:00.180> on<00:44:00.720> our<00:44:00.900> website<00:44:01.200> uh<00:44:01.800> called 00:44:02.690 --> 00:44:02.700 align:start position:0% landing page on our website uh called 00:44:02.700 --> 00:44:03.790 align:start position:0% landing page on our website uh called um 00:44:03.790 --> 00:44:03.800 align:start position:0% um 00:44:03.800 --> 00:44:07.550 align:start position:0% um metamask.io<00:44:05.000> snaps<00:44:06.000> that<00:44:06.839> will<00:44:07.020> also<00:44:07.200> get<00:44:07.380> you 00:44:07.550 --> 00:44:07.560 align:start position:0% metamask.io snaps that will also get you 00:44:07.560 --> 00:44:10.250 align:start position:0% metamask.io snaps that will also get you to<00:44:07.740> a<00:44:08.040> lot<00:44:08.160> of<00:44:08.280> the<00:44:08.339> resources<00:44:08.839> but<00:44:09.839> the<00:44:09.960> GitHub 00:44:10.250 --> 00:44:10.260 align:start position:0% to a lot of the resources but the GitHub 00:44:10.260 --> 00:44:11.510 align:start position:0% to a lot of the resources but the GitHub discussions<00:44:10.619> is<00:44:10.800> a<00:44:10.920> great<00:44:11.040> place<00:44:11.220> to<00:44:11.400> get 00:44:11.510 --> 00:44:11.520 align:start position:0% discussions is a great place to get 00:44:11.520 --> 00:44:13.730 align:start position:0% discussions is a great place to get started<00:44:11.819> uh<00:44:12.780> yes 00:44:13.730 --> 00:44:13.740 align:start position:0% started uh yes 00:44:13.740 --> 00:44:22.480 align:start position:0% started uh yes congratulations 00:44:22.480 --> 00:44:22.490 align:start position:0% 00:44:22.490 --> 00:44:34.089 align:start position:0% [Music] 00:44:34.089 --> 00:44:34.099 align:start position:0% 00:44:34.099 --> 00:44:37.910 align:start position:0% yes<00:44:35.099> we<00:44:35.460> are<00:44:35.640> uh<00:44:36.359> we<00:44:36.839> are<00:44:37.440> in<00:44:37.619> touch<00:44:37.740> with 00:44:37.910 --> 00:44:37.920 align:start position:0% yes we are uh we are in touch with 00:44:37.920 --> 00:44:39.589 align:start position:0% yes we are uh we are in touch with Google<00:44:38.160> and<00:44:38.520> are<00:44:38.700> working<00:44:38.940> with<00:44:39.180> them<00:44:39.300> to 00:44:39.589 --> 00:44:39.599 align:start position:0% Google and are working with them to 00:44:39.599 --> 00:44:44.569 align:start position:0% Google and are working with them to ensure<00:44:39.960> that<00:44:40.319> uh<00:44:41.420> everybody<00:44:42.420> is<00:44:42.780> happy<00:44:43.280> and<00:44:44.280> we 00:44:44.569 --> 00:44:44.579 align:start position:0% ensure that uh everybody is happy and we 00:44:44.579 --> 00:44:45.890 align:start position:0% ensure that uh everybody is happy and we and<00:44:44.819> we<00:44:45.000> don't<00:44:45.119> get<00:44:45.240> banned<00:44:45.599> from<00:44:45.660> the<00:44:45.780> Chrome 00:44:45.890 --> 00:44:45.900 align:start position:0% and we don't get banned from the Chrome 00:44:45.900 --> 00:44:47.809 align:start position:0% and we don't get banned from the Chrome Store 00:44:47.809 --> 00:44:47.819 align:start position:0% Store 00:44:47.819 --> 00:44:50.990 align:start position:0% Store um how<00:44:48.599> how<00:44:49.020> much<00:44:49.260> all<00:44:50.160> right<00:44:50.280> I<00:44:50.579> I'm<00:44:50.819> being 00:44:50.990 --> 00:44:51.000 align:start position:0% um how how much all right I I'm being 00:44:51.000 --> 00:44:52.670 align:start position:0% um how how much all right I I'm being asked<00:44:51.300> to<00:44:51.420> stop<00:44:51.540> so<00:44:51.780> I'm<00:44:51.960> gonna<00:44:52.079> stop<00:44:52.319> but 00:44:52.670 --> 00:44:52.680 align:start position:0% asked to stop so I'm gonna stop but 00:44:52.680 --> 00:44:54.710 align:start position:0% asked to stop so I'm gonna stop but thank<00:44:52.920> you<00:44:53.040> thank<00:44:53.940> you<00:44:54.060> everyone<00:44:54.180> so<00:44:54.420> much<00:44:54.540> for 00:44:54.710 --> 00:44:54.720 align:start position:0% thank you thank you everyone so much for 00:44:54.720 --> 00:44:55.160 align:start position:0% thank you thank you everyone so much for attending 00:44:55.160 --> 00:44:55.170 align:start position:0% attending 00:44:55.170 --> 00:45:00.199 align:start position:0% attending [Applause]