WEBVTT Kind: captions Language: en 00:00:00.000 --> 00:00:04.490 align:start position:0% foreign 00:00:04.490 --> 00:00:04.500 align:start position:0% 00:00:04.500 --> 00:00:15.550 align:start position:0% [Music] 00:00:15.550 --> 00:00:15.560 align:start position:0% 00:00:15.560 --> 00:00:19.130 align:start position:0% foundation<00:00:16.560> on<00:00:16.859> the<00:00:17.039> project<00:00:17.180> sourcify<00:00:18.180> and 00:00:19.130 --> 00:00:19.140 align:start position:0% foundation on the project sourcify and 00:00:19.140 --> 00:00:21.650 align:start position:0% foundation on the project sourcify and today<00:00:19.380> I<00:00:19.800> will<00:00:19.980> be<00:00:20.100> talking<00:00:20.400> about<00:00:20.580> how<00:00:21.119> we<00:00:21.480> can 00:00:21.650 --> 00:00:21.660 align:start position:0% today I will be talking about how we can 00:00:21.660 --> 00:00:23.330 align:start position:0% today I will be talking about how we can enable<00:00:22.080> more<00:00:22.439> human<00:00:22.619> friendly<00:00:23.100> contract 00:00:23.330 --> 00:00:23.340 align:start position:0% enable more human friendly contract 00:00:23.340 --> 00:00:25.189 align:start position:0% enable more human friendly contract interactions<00:00:23.880> using<00:00:24.300> source5<00:00:24.660> verification 00:00:25.189 --> 00:00:25.199 align:start position:0% interactions using source5 verification 00:00:25.199 --> 00:00:28.670 align:start position:0% interactions using source5 verification I'll<00:00:25.800> start<00:00:26.039> with<00:00:26.580> uh<00:00:27.779> showing<00:00:28.320> you<00:00:28.500> guys 00:00:28.670 --> 00:00:28.680 align:start position:0% I'll start with uh showing you guys 00:00:28.680 --> 00:00:31.910 align:start position:0% I'll start with uh showing you guys something<00:00:29.220> you're<00:00:29.820> all<00:00:30.060> familiar<00:00:30.420> with<00:00:30.920> I 00:00:31.910 --> 00:00:31.920 align:start position:0% something you're all familiar with I 00:00:31.920 --> 00:00:33.770 align:start position:0% something you're all familiar with I would<00:00:31.980> say<00:00:32.160> if<00:00:32.340> you're<00:00:32.460> a<00:00:32.640> web<00:00:32.820> 3<00:00:33.059> user<00:00:33.480> for<00:00:33.660> a 00:00:33.770 --> 00:00:33.780 align:start position:0% would say if you're a web 3 user for a 00:00:33.780 --> 00:00:35.330 align:start position:0% would say if you're a web 3 user for a while 00:00:35.330 --> 00:00:35.340 align:start position:0% while 00:00:35.340 --> 00:00:37.310 align:start position:0% while um just<00:00:35.880> a<00:00:36.000> normal<00:00:36.120> day<00:00:36.360> in<00:00:36.480> webtree<00:00:36.899> and<00:00:37.140> I 00:00:37.310 --> 00:00:37.320 align:start position:0% um just a normal day in webtree and I 00:00:37.320 --> 00:00:39.290 align:start position:0% um just a normal day in webtree and I guess<00:00:37.500> this<00:00:38.160> will<00:00:38.340> this<00:00:38.880> will<00:00:39.000> be<00:00:39.180> like 00:00:39.290 --> 00:00:39.300 align:start position:0% guess this will this will be like 00:00:39.300 --> 00:00:41.510 align:start position:0% guess this will this will be like something<00:00:39.480> you<00:00:39.719> see<00:00:39.899> every<00:00:40.079> day<00:00:40.260> and<00:00:40.500> you<00:00:41.219> see 00:00:41.510 --> 00:00:41.520 align:start position:0% something you see every day and you see 00:00:41.520 --> 00:00:43.610 align:start position:0% something you see every day and you see every<00:00:42.059> day<00:00:42.239> in<00:00:42.420> webg<00:00:42.780> you<00:00:43.020> see<00:00:43.200> things<00:00:43.440> like 00:00:43.610 --> 00:00:43.620 align:start position:0% every day in webg you see things like 00:00:43.620 --> 00:00:46.670 align:start position:0% every day in webg you see things like this<00:00:44.059> and<00:00:45.059> you<00:00:45.540> basically<00:00:45.899> have<00:00:46.140> no<00:00:46.379> idea 00:00:46.670 --> 00:00:46.680 align:start position:0% this and you basically have no idea 00:00:46.680 --> 00:00:47.990 align:start position:0% this and you basically have no idea you're<00:00:46.860> not<00:00:47.040> a<00:00:47.219> machine<00:00:47.399> you<00:00:47.879> don't 00:00:47.990 --> 00:00:48.000 align:start position:0% you're not a machine you don't 00:00:48.000 --> 00:00:50.209 align:start position:0% you're not a machine you don't understand<00:00:48.300> what's<00:00:48.719> going<00:00:48.960> on<00:00:49.140> you're<00:00:49.980> like 00:00:50.209 --> 00:00:50.219 align:start position:0% understand what's going on you're like 00:00:50.219 --> 00:00:52.430 align:start position:0% understand what's going on you're like trying<00:00:50.399> to<00:00:50.579> make<00:00:50.760> sense<00:00:50.940> of<00:00:51.180> it<00:00:51.360> am<00:00:52.079> I<00:00:52.260> doing 00:00:52.430 --> 00:00:52.440 align:start position:0% trying to make sense of it am I doing 00:00:52.440 --> 00:00:53.930 align:start position:0% trying to make sense of it am I doing the<00:00:52.620> right<00:00:52.739> thing<00:00:52.920> am<00:00:53.219> I<00:00:53.399> talking<00:00:53.579> to<00:00:53.820> the 00:00:53.930 --> 00:00:53.940 align:start position:0% the right thing am I talking to the 00:00:53.940 --> 00:00:55.910 align:start position:0% the right thing am I talking to the right<00:00:54.120> contract<00:00:54.539> is<00:00:55.199> this<00:00:55.440> doing<00:00:55.620> actually 00:00:55.910 --> 00:00:55.920 align:start position:0% right contract is this doing actually 00:00:55.920 --> 00:00:59.450 align:start position:0% right contract is this doing actually what<00:00:56.340> I<00:00:56.520> want<00:00:56.640> to<00:00:56.760> do<00:00:56.940> and<00:00:57.840> basically<00:00:58.280> what<00:00:59.280> you 00:00:59.450 --> 00:00:59.460 align:start position:0% what I want to do and basically what you 00:00:59.460 --> 00:01:02.090 align:start position:0% what I want to do and basically what you do<00:00:59.699> is<00:01:00.239> telling<00:01:01.140> them<00:01:01.260> to<00:01:01.500> like<00:01:01.620> shut<00:01:01.860> up<00:01:02.039> and 00:01:02.090 --> 00:01:02.100 align:start position:0% do is telling them to like shut up and 00:01:02.100 --> 00:01:03.950 align:start position:0% do is telling them to like shut up and take<00:01:02.219> your<00:01:02.340> money<00:01:02.579> like<00:01:02.760> you<00:01:02.940> have<00:01:03.180> no<00:01:03.660> idea 00:01:03.950 --> 00:01:03.960 align:start position:0% take your money like you have no idea 00:01:03.960 --> 00:01:05.210 align:start position:0% take your money like you have no idea what's<00:01:04.140> going<00:01:04.320> on<00:01:04.440> you're<00:01:04.680> just<00:01:04.860> giving<00:01:04.979> out 00:01:05.210 --> 00:01:05.220 align:start position:0% what's going on you're just giving out 00:01:05.220 --> 00:01:06.289 align:start position:0% what's going on you're just giving out your<00:01:05.400> money 00:01:06.289 --> 00:01:06.299 align:start position:0% your money 00:01:06.299 --> 00:01:10.130 align:start position:0% your money and<00:01:07.200> we<00:01:07.860> say<00:01:08.040> today<00:01:08.479> a<00:01:09.479> typical<00:01:09.900> web 00:01:10.130 --> 00:01:10.140 align:start position:0% and we say today a typical web 00:01:10.140 --> 00:01:12.289 align:start position:0% and we say today a typical web pre-interaction<00:01:10.860> is<00:01:11.220> still<00:01:11.700> a<00:01:12.000> yellow 00:01:12.289 --> 00:01:12.299 align:start position:0% pre-interaction is still a yellow 00:01:12.299 --> 00:01:14.570 align:start position:0% pre-interaction is still a yellow signing<00:01:12.920> nightmare<00:01:13.920> what<00:01:14.100> we<00:01:14.220> call<00:01:14.340> Yellow 00:01:14.570 --> 00:01:14.580 align:start position:0% signing nightmare what we call Yellow 00:01:14.580 --> 00:01:16.609 align:start position:0% signing nightmare what we call Yellow signing<00:01:15.119> it's<00:01:15.360> just<00:01:15.600> they<00:01:16.140> give<00:01:16.320> you<00:01:16.439> things 00:01:16.609 --> 00:01:16.619 align:start position:0% signing it's just they give you things 00:01:16.619 --> 00:01:18.890 align:start position:0% signing it's just they give you things to<00:01:16.799> sign<00:01:16.979> and<00:01:17.159> you<00:01:17.340> just<00:01:17.460> like<00:01:17.880> sign<00:01:18.299> and<00:01:18.600> hope 00:01:18.890 --> 00:01:18.900 align:start position:0% to sign and you just like sign and hope 00:01:18.900 --> 00:01:20.749 align:start position:0% to sign and you just like sign and hope for<00:01:19.140> the<00:01:19.260> best 00:01:20.749 --> 00:01:20.759 align:start position:0% for the best 00:01:20.759 --> 00:01:23.570 align:start position:0% for the best so<00:01:21.299> at<00:01:22.020> the<00:01:22.140> end<00:01:22.200> of<00:01:22.380> the<00:01:22.500> day<00:01:22.619> what<00:01:23.100> we<00:01:23.280> want<00:01:23.460> to 00:01:23.570 --> 00:01:23.580 align:start position:0% so at the end of the day what we want to 00:01:23.580 --> 00:01:26.690 align:start position:0% so at the end of the day what we want to have<00:01:23.820> is<00:01:24.619> more<00:01:25.619> to<00:01:25.920> do<00:01:26.159> something<00:01:26.280> on<00:01:26.580> the 00:01:26.690 --> 00:01:26.700 align:start position:0% have is more to do something on the 00:01:26.700 --> 00:01:28.429 align:start position:0% have is more to do something on the right<00:01:26.820> hand<00:01:27.000> side<00:01:27.180> from<00:01:27.540> left<00:01:27.900> hand<00:01:28.020> side<00:01:28.200> to 00:01:28.429 --> 00:01:28.439 align:start position:0% right hand side from left hand side to 00:01:28.439 --> 00:01:30.950 align:start position:0% right hand side from left hand side to right<00:01:28.619> hand<00:01:28.740> side<00:01:28.920> so<00:01:29.340> I<00:01:30.299> know<00:01:30.420> this<00:01:30.780> has 00:01:30.950 --> 00:01:30.960 align:start position:0% right hand side so I know this has 00:01:30.960 --> 00:01:33.530 align:start position:0% right hand side so I know this has changed<00:01:31.320> actually<00:01:31.500> for<00:01:32.100> many<00:01:32.820> wallets<00:01:33.240> so 00:01:33.530 --> 00:01:33.540 align:start position:0% changed actually for many wallets so 00:01:33.540 --> 00:01:36.469 align:start position:0% changed actually for many wallets so many<00:01:33.720> wallets<00:01:34.200> actually<00:01:34.439> started<00:01:35.040> to<00:01:35.479> decode 00:01:36.469 --> 00:01:36.479 align:start position:0% many wallets actually started to decode 00:01:36.479 --> 00:01:39.590 align:start position:0% many wallets actually started to decode things<00:01:36.780> like<00:01:37.259> metamask<00:01:37.799> using<00:01:38.220> truffle 00:01:39.590 --> 00:01:39.600 align:start position:0% things like metamask using truffle 00:01:39.600 --> 00:01:40.609 align:start position:0% things like metamask using truffle um 00:01:40.609 --> 00:01:40.619 align:start position:0% um 00:01:40.619 --> 00:01:43.789 align:start position:0% um and<00:01:41.159> decoding<00:01:41.700> API<00:01:42.119> but<00:01:42.720> still<00:01:42.960> we<00:01:43.500> have<00:01:43.680> a 00:01:43.789 --> 00:01:43.799 align:start position:0% and decoding API but still we have a 00:01:43.799 --> 00:01:45.890 align:start position:0% and decoding API but still we have a long<00:01:43.920> way<00:01:44.100> to<00:01:44.280> go<00:01:44.400> and<00:01:45.119> we<00:01:45.420> have<00:01:45.540> a<00:01:45.659> lot<00:01:45.780> of 00:01:45.890 --> 00:01:45.900 align:start position:0% long way to go and we have a lot of 00:01:45.900 --> 00:01:46.850 align:start position:0% long way to go and we have a lot of things 00:01:46.850 --> 00:01:46.860 align:start position:0% things 00:01:46.860 --> 00:01:49.249 align:start position:0% things that<00:01:47.340> we<00:01:47.520> can<00:01:47.640> improve<00:01:48.060> the<00:01:48.479> human<00:01:48.720> the<00:01:49.259> the 00:01:49.249 --> 00:01:49.259 align:start position:0% that we can improve the human the the 00:01:49.259 --> 00:01:50.749 align:start position:0% that we can improve the human the the user<00:01:49.799> experience 00:01:50.749 --> 00:01:50.759 align:start position:0% user experience 00:01:50.759 --> 00:01:52.130 align:start position:0% user experience so 00:01:52.130 --> 00:01:52.140 align:start position:0% so 00:01:52.140 --> 00:01:53.870 align:start position:0% so what<00:01:52.560> can<00:01:52.680> you<00:01:52.799> do<00:01:52.920> to<00:01:53.040> achieve<00:01:53.399> this<00:01:53.460> there 00:01:53.870 --> 00:01:53.880 align:start position:0% what can you do to achieve this there 00:01:53.880 --> 00:01:56.690 align:start position:0% what can you do to achieve this there are<00:01:54.060> two<00:01:54.360> sides<00:01:54.659> of<00:01:54.780> of<00:01:55.079> this<00:01:55.320> coin<00:01:55.619> so<00:01:56.280> you<00:01:56.520> can 00:01:56.690 --> 00:01:56.700 align:start position:0% are two sides of of this coin so you can 00:01:56.700 --> 00:01:58.069 align:start position:0% are two sides of of this coin so you can there<00:01:57.119> are<00:01:57.240> things<00:01:57.360> you<00:01:57.540> can<00:01:57.659> do<00:01:57.720> as<00:01:57.899> the 00:01:58.069 --> 00:01:58.079 align:start position:0% there are things you can do as the 00:01:58.079 --> 00:01:59.990 align:start position:0% there are things you can do as the wallet<00:01:58.380> developer<00:01:58.799> and<00:01:59.579> there<00:01:59.700> are<00:01:59.880> things 00:01:59.990 --> 00:02:00.000 align:start position:0% wallet developer and there are things 00:02:00.000 --> 00:02:02.690 align:start position:0% wallet developer and there are things you<00:02:00.180> can<00:02:00.299> do<00:02:00.479> as<00:02:01.020> the<00:02:01.860> um 00:02:02.690 --> 00:02:02.700 align:start position:0% you can do as the um 00:02:02.700 --> 00:02:04.550 align:start position:0% you can do as the um as<00:02:03.060> the<00:02:03.299> smart<00:02:03.540> contract<00:02:03.780> developer<00:02:04.320> so<00:02:04.439> let's 00:02:04.550 --> 00:02:04.560 align:start position:0% as the smart contract developer so let's 00:02:04.560 --> 00:02:06.590 align:start position:0% as the smart contract developer so let's dive<00:02:04.860> in<00:02:05.040> what<00:02:05.640> you<00:02:05.759> can<00:02:05.880> do<00:02:06.060> as<00:02:06.299> a<00:02:06.479> smart 00:02:06.590 --> 00:02:06.600 align:start position:0% dive in what you can do as a smart 00:02:06.600 --> 00:02:09.050 align:start position:0% dive in what you can do as a smart contract<00:02:06.960> developer 00:02:09.050 --> 00:02:09.060 align:start position:0% contract developer 00:02:09.060 --> 00:02:11.930 align:start position:0% contract developer the<00:02:09.959> first<00:02:10.080> thing<00:02:10.259> you<00:02:10.380> can<00:02:10.500> do<00:02:10.739> is<00:02:11.400> using<00:02:11.819> a 00:02:11.930 --> 00:02:11.940 align:start position:0% the first thing you can do is using a 00:02:11.940 --> 00:02:14.270 align:start position:0% the first thing you can do is using a nutspec<00:02:12.420> documentation<00:02:12.900> and<00:02:13.800> as<00:02:13.980> well<00:02:14.160> as 00:02:14.270 --> 00:02:14.280 align:start position:0% nutspec documentation and as well as 00:02:14.280 --> 00:02:15.770 align:start position:0% nutspec documentation and as well as doing<00:02:14.640> the<00:02:14.819> source<00:02:15.060> code<00:02:15.120> verification<00:02:15.599> on 00:02:15.770 --> 00:02:15.780 align:start position:0% doing the source code verification on 00:02:15.780 --> 00:02:16.910 align:start position:0% doing the source code verification on sourceify 00:02:16.910 --> 00:02:16.920 align:start position:0% sourceify 00:02:16.920 --> 00:02:18.890 align:start position:0% sourceify so<00:02:17.400> what<00:02:17.580> is<00:02:17.760> not<00:02:17.879> spec<00:02:18.120> documentation<00:02:18.660> not 00:02:18.890 --> 00:02:18.900 align:start position:0% so what is not spec documentation not 00:02:18.900 --> 00:02:21.290 align:start position:0% so what is not spec documentation not spec<00:02:19.140> documentation<00:02:19.800> is<00:02:20.459> what<00:02:20.879> is<00:02:21.060> called 00:02:21.290 --> 00:02:21.300 align:start position:0% spec documentation is what is called 00:02:21.300 --> 00:02:23.990 align:start position:0% spec documentation is what is called ethereum<00:02:22.200> natural<00:02:22.440> language<00:02:23.000> specification 00:02:23.990 --> 00:02:24.000 align:start position:0% ethereum natural language specification 00:02:24.000 --> 00:02:25.970 align:start position:0% ethereum natural language specification format<00:02:24.480> it's<00:02:24.959> actually<00:02:25.200> part<00:02:25.500> of<00:02:25.680> the 00:02:25.970 --> 00:02:25.980 align:start position:0% format it's actually part of the 00:02:25.980 --> 00:02:27.490 align:start position:0% format it's actually part of the solidity<00:02:26.400> spec 00:02:27.490 --> 00:02:27.500 align:start position:0% solidity spec 00:02:27.500 --> 00:02:30.229 align:start position:0% solidity spec and<00:02:28.500> probably<00:02:28.860> you<00:02:29.220> have<00:02:29.400> seen<00:02:29.580> this<00:02:29.819> if<00:02:30.120> you 00:02:30.229 --> 00:02:30.239 align:start position:0% and probably you have seen this if you 00:02:30.239 --> 00:02:32.690 align:start position:0% and probably you have seen this if you have<00:02:30.360> seen<00:02:30.599> a<00:02:30.780> contract<00:02:31.020> before<00:02:31.260> this<00:02:31.920> is<00:02:32.099> how 00:02:32.690 --> 00:02:32.700 align:start position:0% have seen a contract before this is how 00:02:32.700 --> 00:02:34.750 align:start position:0% have seen a contract before this is how it<00:02:32.819> looks<00:02:33.120> like<00:02:33.180> you<00:02:33.480> put 00:02:34.750 --> 00:02:34.760 align:start position:0% it looks like you put 00:02:34.760 --> 00:02:38.510 align:start position:0% it looks like you put the<00:02:35.760> comment<00:02:36.300> the<00:02:36.599> documentation<00:02:37.340> above<00:02:38.340> the 00:02:38.510 --> 00:02:38.520 align:start position:0% the comment the documentation above the 00:02:38.520 --> 00:02:40.970 align:start position:0% the comment the documentation above the function<00:02:38.879> and<00:02:39.720> you<00:02:39.959> have<00:02:40.140> the<00:02:40.379> developer 00:02:40.970 --> 00:02:40.980 align:start position:0% function and you have the developer 00:02:40.980 --> 00:02:43.490 align:start position:0% function and you have the developer documentation<00:02:41.599> you<00:02:42.599> have<00:02:42.840> the<00:02:43.260> user 00:02:43.490 --> 00:02:43.500 align:start position:0% documentation you have the user 00:02:43.500 --> 00:02:47.030 align:start position:0% documentation you have the user documentation<00:02:44.040> with<00:02:44.459> the<00:02:44.760> at<00:02:45.120> notice<00:02:46.040> field 00:02:47.030 --> 00:02:47.040 align:start position:0% documentation with the at notice field 00:02:47.040 --> 00:02:49.490 align:start position:0% documentation with the at notice field and<00:02:48.000> you<00:02:48.180> have<00:02:48.300> the<00:02:48.480> documentation<00:02:48.959> for<00:02:49.260> the 00:02:49.490 --> 00:02:49.500 align:start position:0% and you have the documentation for the 00:02:49.500 --> 00:02:51.170 align:start position:0% and you have the documentation for the parameters 00:02:51.170 --> 00:02:51.180 align:start position:0% parameters 00:02:51.180 --> 00:02:54.170 align:start position:0% parameters uh<00:02:52.019> so<00:02:52.260> another<00:02:52.500> nice<00:02:52.800> thing<00:02:53.040> about<00:02:53.340> nutspec 00:02:54.170 --> 00:02:54.180 align:start position:0% uh so another nice thing about nutspec 00:02:54.180 --> 00:02:57.770 align:start position:0% uh so another nice thing about nutspec is<00:02:54.540> it<00:02:55.379> has<00:02:55.620> the<00:02:56.340> specification<00:02:56.879> for<00:02:57.300> dynamic 00:02:57.770 --> 00:02:57.780 align:start position:0% is it has the specification for dynamic 00:02:57.780 --> 00:03:02.210 align:start position:0% is it has the specification for dynamic expression<00:02:58.200> so<00:02:58.920> the<00:02:59.640> field<00:03:00.300> you<00:03:00.720> see<00:03:00.900> here<00:03:01.220> the 00:03:02.210 --> 00:03:02.220 align:start position:0% expression so the field you see here the 00:03:02.220 --> 00:03:05.809 align:start position:0% expression so the field you see here the old<00:03:02.459> owner<00:03:02.879> and<00:03:03.000> new<00:03:03.180> owner<00:03:03.980> parameters<00:03:04.980> in 00:03:05.809 --> 00:03:05.819 align:start position:0% old owner and new owner parameters in 00:03:05.819 --> 00:03:07.330 align:start position:0% old owner and new owner parameters in back<00:03:06.000> quotes 00:03:07.330 --> 00:03:07.340 align:start position:0% back quotes 00:03:07.340 --> 00:03:10.190 align:start position:0% back quotes these<00:03:08.340> actually<00:03:08.519> can<00:03:09.060> be<00:03:09.300> filled<00:03:09.720> dynamically 00:03:10.190 --> 00:03:10.200 align:start position:0% these actually can be filled dynamically 00:03:10.200 --> 00:03:12.550 align:start position:0% these actually can be filled dynamically with<00:03:10.500> the<00:03:10.680> value<00:03:10.920> they<00:03:11.400> are<00:03:11.580> being<00:03:11.700> called<00:03:12.000> so 00:03:12.550 --> 00:03:12.560 align:start position:0% with the value they are being called so 00:03:12.560 --> 00:03:15.589 align:start position:0% with the value they are being called so this<00:03:13.560> replaces<00:03:14.340> the<00:03:14.580> owner 00:03:15.589 --> 00:03:15.599 align:start position:0% this replaces the owner 00:03:15.599 --> 00:03:18.770 align:start position:0% this replaces the owner the<00:03:16.560> address<00:03:16.739> gets<00:03:17.400> filled<00:03:17.760> can<00:03:18.120> get<00:03:18.360> filled 00:03:18.770 --> 00:03:18.780 align:start position:0% the address gets filled can get filled 00:03:18.780 --> 00:03:21.290 align:start position:0% the address gets filled can get filled and<00:03:19.560> the<00:03:19.800> new<00:03:19.920> one<00:03:20.099> can<00:03:20.340> also<00:03:20.519> get<00:03:20.640> filled<00:03:21.060> in 00:03:21.290 --> 00:03:21.300 align:start position:0% and the new one can also get filled in 00:03:21.300 --> 00:03:23.690 align:start position:0% and the new one can also get filled in in<00:03:21.540> the<00:03:21.780> parameters 00:03:23.690 --> 00:03:23.700 align:start position:0% in the parameters 00:03:23.700 --> 00:03:27.290 align:start position:0% in the parameters okay<00:03:24.300> so<00:03:24.720> you<00:03:25.200> you<00:03:25.379> did<00:03:25.620> you<00:03:26.280> did<00:03:26.400> your<00:03:26.580> job<00:03:26.760> you 00:03:27.290 --> 00:03:27.300 align:start position:0% okay so you you did you did your job you 00:03:27.300 --> 00:03:29.509 align:start position:0% okay so you you did you did your job you made<00:03:28.019> the<00:03:28.200> user<00:03:28.440> documentation<00:03:28.920> developer 00:03:29.509 --> 00:03:29.519 align:start position:0% made the user documentation developer 00:03:29.519 --> 00:03:31.009 align:start position:0% made the user documentation developer documentation<00:03:30.000> so<00:03:30.239> where<00:03:30.480> do<00:03:30.599> you<00:03:30.720> find<00:03:30.840> it 00:03:31.009 --> 00:03:31.019 align:start position:0% documentation so where do you find it 00:03:31.019 --> 00:03:35.210 align:start position:0% documentation so where do you find it then<00:03:31.200> why<00:03:32.040> can<00:03:32.159> I<00:03:32.280> can<00:03:33.000> find<00:03:33.239> it<00:03:33.420> it<00:03:34.019> is<00:03:34.379> uh<00:03:34.980> in 00:03:35.210 --> 00:03:35.220 align:start position:0% then why can I can find it it is uh in 00:03:35.220 --> 00:03:38.030 align:start position:0% then why can I can find it it is uh in the<00:03:35.340> solid<00:03:35.700> contract<00:03:36.060> metadata<00:03:36.840> so<00:03:37.680> who 00:03:38.030 --> 00:03:38.040 align:start position:0% the solid contract metadata so who 00:03:38.040 --> 00:03:40.009 align:start position:0% the solid contract metadata so who actually<00:03:38.280> knows<00:03:38.700> what<00:03:39.000> solidity<00:03:39.480> contract 00:03:40.009 --> 00:03:40.019 align:start position:0% actually knows what solidity contract 00:03:40.019 --> 00:03:41.690 align:start position:0% actually knows what solidity contract metadata<00:03:40.680> is 00:03:41.690 --> 00:03:41.700 align:start position:0% metadata is 00:03:41.700 --> 00:03:44.149 align:start position:0% metadata is anyone<00:03:42.299> just<00:03:42.900> a<00:03:43.140> few<00:03:43.260> people 00:03:44.149 --> 00:03:44.159 align:start position:0% anyone just a few people 00:03:44.159 --> 00:03:47.330 align:start position:0% anyone just a few people cool<00:03:44.659> that's<00:03:45.659> why<00:03:45.840> I'm<00:03:46.019> here 00:03:47.330 --> 00:03:47.340 align:start position:0% cool that's why I'm here 00:03:47.340 --> 00:03:50.750 align:start position:0% cool that's why I'm here um<00:03:47.459> so<00:03:48.120> contract<00:03:48.840> metadata<00:03:49.580> is<00:03:50.580> actually 00:03:50.750 --> 00:03:50.760 align:start position:0% um so contract metadata is actually 00:03:50.760 --> 00:03:54.229 align:start position:0% um so contract metadata is actually something<00:03:51.120> introduced<00:03:51.659> early<00:03:52.019> on<00:03:52.260> in<00:03:53.159> 2016<00:03:53.760> in 00:03:54.229 --> 00:03:54.239 align:start position:0% something introduced early on in 2016 in 00:03:54.239 --> 00:03:56.030 align:start position:0% something introduced early on in 2016 in the<00:03:54.360> earlier<00:03:54.599> versions<00:03:54.959> but<00:03:55.560> it<00:03:55.680> was<00:03:55.860> actually 00:03:56.030 --> 00:03:56.040 align:start position:0% the earlier versions but it was actually 00:03:56.040 --> 00:03:58.670 align:start position:0% the earlier versions but it was actually not<00:03:56.340> really<00:03:56.519> picked<00:03:56.879> up<00:03:56.940> by<00:03:57.120> the<00:03:57.239> community<00:03:57.680> it 00:03:58.670 --> 00:03:58.680 align:start position:0% not really picked up by the community it 00:03:58.680 --> 00:04:01.610 align:start position:0% not really picked up by the community it is<00:03:58.799> actually<00:03:58.980> a<00:03:59.280> Json<00:03:59.580> file<00:03:59.940> uh 00:04:01.610 --> 00:04:01.620 align:start position:0% is actually a Json file uh 00:04:01.620 --> 00:04:04.610 align:start position:0% is actually a Json file uh generated<00:04:02.340> by<00:04:02.580> the<00:04:02.700> compiler<00:04:03.180> itself<00:04:03.480> and<00:04:04.379> it 00:04:04.610 --> 00:04:04.620 align:start position:0% generated by the compiler itself and it 00:04:04.620 --> 00:04:07.369 align:start position:0% generated by the compiler itself and it contains<00:04:05.159> the<00:04:05.700> metadata<00:04:06.299> okay<00:04:06.840> but<00:04:07.019> what<00:04:07.260> is 00:04:07.369 --> 00:04:07.379 align:start position:0% contains the metadata okay but what is 00:04:07.379 --> 00:04:10.750 align:start position:0% contains the metadata okay but what is metadata<00:04:07.980> it<00:04:08.580> has<00:04:08.819> the<00:04:09.239> ABI<00:04:09.659> the<00:04:10.200> user<00:04:10.439> talk 00:04:10.750 --> 00:04:10.760 align:start position:0% metadata it has the ABI the user talk 00:04:10.760 --> 00:04:14.690 align:start position:0% metadata it has the ABI the user talk Dev<00:04:11.760> doc<00:04:12.180> as<00:04:13.140> well<00:04:13.260> as<00:04:13.379> compilation<00:04:13.920> info<00:04:14.400> and 00:04:14.690 --> 00:04:14.700 align:start position:0% Dev doc as well as compilation info and 00:04:14.700 --> 00:04:16.610 align:start position:0% Dev doc as well as compilation info and source<00:04:15.060> file<00:04:15.239> info 00:04:16.610 --> 00:04:16.620 align:start position:0% source file info 00:04:16.620 --> 00:04:19.430 align:start position:0% source file info so<00:04:17.579> the<00:04:18.299> first<00:04:18.419> two 00:04:19.430 --> 00:04:19.440 align:start position:0% so the first two 00:04:19.440 --> 00:04:23.030 align:start position:0% so the first two it<00:04:20.040> feels<00:04:20.459> actually<00:04:21.180> is<00:04:21.720> concerned<00:04:22.199> with<00:04:22.500> how 00:04:23.030 --> 00:04:23.040 align:start position:0% it feels actually is concerned with how 00:04:23.040 --> 00:04:24.950 align:start position:0% it feels actually is concerned with how to<00:04:23.160> interact<00:04:23.460> with<00:04:23.580> the<00:04:23.759> contract<00:04:24.120> so<00:04:24.600> how<00:04:24.840> to 00:04:24.950 --> 00:04:24.960 align:start position:0% to interact with the contract so how to 00:04:24.960 --> 00:04:26.629 align:start position:0% to interact with the contract so how to interface<00:04:25.320> with<00:04:25.560> the<00:04:25.740> contract 00:04:26.629 --> 00:04:26.639 align:start position:0% interface with the contract 00:04:26.639 --> 00:04:29.629 align:start position:0% interface with the contract and<00:04:27.120> then<00:04:27.240> the<00:04:27.419> second<00:04:27.600> two<00:04:27.840> is<00:04:28.320> about<00:04:28.620> how<00:04:29.520> to 00:04:29.629 --> 00:04:29.639 align:start position:0% and then the second two is about how to 00:04:29.639 --> 00:04:32.330 align:start position:0% and then the second two is about how to reproduce<00:04:30.120> a<00:04:30.660> contract<00:04:31.020> compilation<00:04:31.500> so<00:04:31.740> it's 00:04:32.330 --> 00:04:32.340 align:start position:0% reproduce a contract compilation so it's 00:04:32.340 --> 00:04:36.469 align:start position:0% reproduce a contract compilation so it's uh<00:04:33.240> embed<00:04:33.900> the<00:04:34.860> information<00:04:35.220> during<00:04:36.060> the 00:04:36.469 --> 00:04:36.479 align:start position:0% uh embed the information during the 00:04:36.479 --> 00:04:38.090 align:start position:0% uh embed the information during the contract<00:04:36.900> compilation<00:04:37.320> so<00:04:37.560> that<00:04:37.740> can<00:04:37.979> be 00:04:38.090 --> 00:04:38.100 align:start position:0% contract compilation so that can be 00:04:38.100 --> 00:04:39.770 align:start position:0% contract compilation so that can be reproduced 00:04:39.770 --> 00:04:39.780 align:start position:0% reproduced 00:04:39.780 --> 00:04:42.230 align:start position:0% reproduced the<00:04:40.380> file<00:04:40.500> looks<00:04:40.860> like<00:04:40.979> this<00:04:41.160> it's<00:04:41.880> a<00:04:42.000> Json 00:04:42.230 --> 00:04:42.240 align:start position:0% the file looks like this it's a Json 00:04:42.240 --> 00:04:44.930 align:start position:0% the file looks like this it's a Json file<00:04:42.660> it<00:04:43.020> has<00:04:43.199> a<00:04:43.800> set<00:04:43.979> it<00:04:44.220> says<00:04:44.340> compiler 00:04:44.930 --> 00:04:44.940 align:start position:0% file it has a set it says compiler 00:04:44.940 --> 00:04:47.090 align:start position:0% file it has a set it says compiler language<00:04:45.180> settings<00:04:45.860> source<00:04:46.860> file 00:04:47.090 --> 00:04:47.100 align:start position:0% language settings source file 00:04:47.100 --> 00:04:48.370 align:start position:0% language settings source file information 00:04:48.370 --> 00:04:48.380 align:start position:0% information 00:04:48.380 --> 00:04:51.469 align:start position:0% information and<00:04:49.380> here<00:04:49.680> for<00:04:49.979> example<00:04:50.160> in<00:04:50.400> the<00:04:50.520> output<00:04:50.820> you 00:04:51.469 --> 00:04:51.479 align:start position:0% and here for example in the output you 00:04:51.479 --> 00:04:53.930 align:start position:0% and here for example in the output you can<00:04:51.600> see<00:04:51.780> the<00:04:51.960> user<00:04:52.259> Doc<00:04:52.560> and<00:04:53.040> Dev<00:04:53.220> Dock<00:04:53.580> and<00:04:53.759> if 00:04:53.930 --> 00:04:53.940 align:start position:0% can see the user Doc and Dev Dock and if 00:04:53.940 --> 00:04:56.390 align:start position:0% can see the user Doc and Dev Dock and if we<00:04:54.060> open<00:04:54.300> that<00:04:55.020> field<00:04:55.500> those<00:04:55.919> fields<00:04:56.220> again 00:04:56.390 --> 00:04:56.400 align:start position:0% we open that field those fields again 00:04:56.400 --> 00:04:59.090 align:start position:0% we open that field those fields again you<00:04:57.300> have<00:04:57.479> the<00:04:57.660> methods<00:04:58.139> and<00:04:58.560> with<00:04:58.919> the 00:04:59.090 --> 00:04:59.100 align:start position:0% you have the methods and with the 00:04:59.100 --> 00:05:01.390 align:start position:0% you have the methods and with the methods<00:04:59.460> for<00:04:59.759> each<00:04:59.940> method<00:05:00.360> you<00:05:00.660> have<00:05:00.840> the 00:05:01.390 --> 00:05:01.400 align:start position:0% methods for each method you have the 00:05:01.400 --> 00:05:04.070 align:start position:0% methods for each method you have the notice<00:05:02.400> field<00:05:02.580> or<00:05:02.880> the<00:05:03.060> dev<00:05:03.240> doc<00:05:03.780> field<00:05:03.840> if 00:05:04.070 --> 00:05:04.080 align:start position:0% notice field or the dev doc field if 00:05:04.080 --> 00:05:06.290 align:start position:0% notice field or the dev doc field if there's<00:05:04.199> a<00:05:04.320> devdoc<00:05:04.740> and<00:05:05.699> you<00:05:05.820> have<00:05:05.940> the<00:05:06.060> for 00:05:06.290 --> 00:05:06.300 align:start position:0% there's a devdoc and you have the for 00:05:06.300 --> 00:05:08.330 align:start position:0% there's a devdoc and you have the for example<00:05:06.479> in<00:05:06.840> this<00:05:06.960> case<00:05:07.139> the<00:05:07.500> replaces<00:05:08.100> the 00:05:08.330 --> 00:05:08.340 align:start position:0% example in this case the replaces the 00:05:08.340 --> 00:05:11.090 align:start position:0% example in this case the replaces the new<00:05:08.460> owner<00:05:08.820> with<00:05:09.440> the<00:05:10.440> old<00:05:10.560> owner<00:05:10.860> with<00:05:10.979> new 00:05:11.090 --> 00:05:11.100 align:start position:0% new owner with the old owner with new 00:05:11.100 --> 00:05:14.150 align:start position:0% new owner with the old owner with new owner<00:05:11.460> the<00:05:11.940> comment<00:05:12.300> we<00:05:12.479> have<00:05:12.600> seen<00:05:12.780> before 00:05:14.150 --> 00:05:14.160 align:start position:0% owner the comment we have seen before 00:05:14.160 --> 00:05:18.050 align:start position:0% owner the comment we have seen before uh<00:05:15.120> you<00:05:15.479> can<00:05:15.660> get<00:05:16.380> the<00:05:16.620> con<00:05:16.860> the<00:05:17.220> metadata<00:05:17.820> with 00:05:18.050 --> 00:05:18.060 align:start position:0% uh you can get the con the metadata with 00:05:18.060 --> 00:05:21.469 align:start position:0% uh you can get the con the metadata with the<00:05:18.240> metadata<00:05:18.840> flag<00:05:19.020> on<00:05:19.800> the<00:05:19.919> compiler<00:05:20.400> itself 00:05:21.469 --> 00:05:21.479 align:start position:0% the metadata flag on the compiler itself 00:05:21.479 --> 00:05:24.710 align:start position:0% the metadata flag on the compiler itself uh<00:05:22.320> on<00:05:22.620> with<00:05:22.979> the<00:05:23.160> Frameworks<00:05:23.699> you<00:05:24.300> can<00:05:24.419> find 00:05:24.710 --> 00:05:24.720 align:start position:0% uh on with the Frameworks you can find 00:05:24.720 --> 00:05:28.310 align:start position:0% uh on with the Frameworks you can find it<00:05:25.020> inside<00:05:25.620> the<00:05:25.919> build<00:05:26.039> files<00:05:26.580> so<00:05:27.240> travel<00:05:27.539> for 00:05:28.310 --> 00:05:28.320 align:start position:0% it inside the build files so travel for 00:05:28.320 --> 00:05:30.230 align:start position:0% it inside the build files so travel for example<00:05:28.500> put<00:05:28.800> this<00:05:29.039> inside<00:05:29.340> the<00:05:30.120> build 00:05:30.230 --> 00:05:30.240 align:start position:0% example put this inside the build 00:05:30.240 --> 00:05:33.290 align:start position:0% example put this inside the build contracts<00:05:30.960> the<00:05:31.500> contract<00:05:31.800> name<00:05:31.979> Json<00:05:32.400> under 00:05:33.290 --> 00:05:33.300 align:start position:0% contracts the contract name Json under 00:05:33.300 --> 00:05:34.969 align:start position:0% contracts the contract name Json under that<00:05:33.539> you<00:05:33.720> can<00:05:33.840> find<00:05:34.020> the<00:05:34.199> metadata<00:05:34.680> fields 00:05:34.969 --> 00:05:34.979 align:start position:0% that you can find the metadata fields 00:05:34.979 --> 00:05:38.090 align:start position:0% that you can find the metadata fields and<00:05:35.280> the<00:05:35.580> the<00:05:36.120> metadata<00:05:36.660> is<00:05:36.780> there<00:05:37.020> hard<00:05:37.740> hat 00:05:38.090 --> 00:05:38.100 align:start position:0% and the the metadata is there hard hat 00:05:38.100 --> 00:05:41.810 align:start position:0% and the the metadata is there hard hat also<00:05:38.460> started<00:05:38.940> to<00:05:39.180> Output<00:05:39.660> metadata<00:05:40.820> for 00:05:41.810 --> 00:05:41.820 align:start position:0% also started to Output metadata for 00:05:41.820 --> 00:05:44.570 align:start position:0% also started to Output metadata for inside<00:05:42.360> the<00:05:42.660> build<00:05:42.840> file<00:05:43.680> again<00:05:43.919> you<00:05:44.280> can<00:05:44.400> find 00:05:44.570 --> 00:05:44.580 align:start position:0% inside the build file again you can find 00:05:44.580 --> 00:05:46.490 align:start position:0% inside the build file again you can find the<00:05:44.759> metadata 00:05:46.490 --> 00:05:46.500 align:start position:0% the metadata 00:05:46.500 --> 00:05:48.950 align:start position:0% the metadata here 00:05:48.950 --> 00:05:48.960 align:start position:0% here 00:05:48.960 --> 00:05:50.590 align:start position:0% here yeah yeah 00:05:50.590 --> 00:05:50.600 align:start position:0% yeah yeah 00:05:50.600 --> 00:05:53.629 align:start position:0% yeah yeah you<00:05:51.600> can<00:05:51.660> also<00:05:51.960> find<00:05:52.380> the<00:05:52.979> traces<00:05:53.340> of<00:05:53.520> the 00:05:53.629 --> 00:05:53.639 align:start position:0% you can also find the traces of the 00:05:53.639 --> 00:05:54.830 align:start position:0% you can also find the traces of the metadata 00:05:54.830 --> 00:05:54.840 align:start position:0% metadata 00:05:54.840 --> 00:05:57.430 align:start position:0% metadata in<00:05:55.500> inside<00:05:55.740> the<00:05:56.039> bytecode 00:05:57.430 --> 00:05:57.440 align:start position:0% in inside the bytecode 00:05:57.440 --> 00:06:00.230 align:start position:0% in inside the bytecode so<00:05:58.440> the<00:05:58.620> bytecode<00:05:59.100> this<00:05:59.460> is<00:05:59.580> an<00:05:59.940> example 00:06:00.230 --> 00:06:00.240 align:start position:0% so the bytecode this is an example 00:06:00.240 --> 00:06:03.469 align:start position:0% so the bytecode this is an example contract<00:06:00.660> byte<00:06:01.020> code<00:06:01.139> and<00:06:01.740> the<00:06:01.860> bytecode<00:06:02.479> has 00:06:03.469 --> 00:06:03.479 align:start position:0% contract byte code and the bytecode has 00:06:03.479 --> 00:06:05.330 align:start position:0% contract byte code and the bytecode has actually<00:06:03.780> a 00:06:05.330 --> 00:06:05.340 align:start position:0% actually a 00:06:05.340 --> 00:06:08.029 align:start position:0% actually a special<00:06:05.880> field<00:06:06.180> at<00:06:06.479> the<00:06:06.600> end<00:06:06.660> of<00:06:06.840> the<00:06:07.080> bytecode 00:06:08.029 --> 00:06:08.039 align:start position:0% special field at the end of the bytecode 00:06:08.039 --> 00:06:10.370 align:start position:0% special field at the end of the bytecode it<00:06:08.160> is<00:06:08.280> appended<00:06:08.940> by<00:06:09.060> the<00:06:09.240> compiler 00:06:10.370 --> 00:06:10.380 align:start position:0% it is appended by the compiler 00:06:10.380 --> 00:06:14.270 align:start position:0% it is appended by the compiler again<00:06:10.740> a<00:06:11.039> question<00:06:11.220> who<00:06:11.520> knows<00:06:11.699> what<00:06:11.880> this<00:06:12.000> is 00:06:14.270 --> 00:06:14.280 align:start position:0% 00:06:14.280 --> 00:06:16.490 align:start position:0% okay<00:06:14.759> again<00:06:15.120> just<00:06:15.479> a<00:06:15.600> few<00:06:15.720> people<00:06:15.960> and<00:06:16.320> again 00:06:16.490 --> 00:06:16.500 align:start position:0% okay again just a few people and again 00:06:16.500 --> 00:06:20.029 align:start position:0% okay again just a few people and again what's<00:06:16.800> that's<00:06:17.039> why<00:06:17.220> I'm<00:06:17.400> here<00:06:17.720> so<00:06:18.720> this<00:06:18.960> field 00:06:20.029 --> 00:06:20.039 align:start position:0% what's that's why I'm here so this field 00:06:20.039 --> 00:06:21.590 align:start position:0% what's that's why I'm here so this field uh 00:06:21.590 --> 00:06:21.600 align:start position:0% uh 00:06:21.600 --> 00:06:24.890 align:start position:0% uh the<00:06:22.199> compiler<00:06:22.620> actually<00:06:23.120> takes<00:06:24.120> the<00:06:24.360> ipfs 00:06:24.890 --> 00:06:24.900 align:start position:0% the compiler actually takes the ipfs 00:06:24.900 --> 00:06:27.050 align:start position:0% the compiler actually takes the ipfs hash<00:06:25.259> of<00:06:25.560> the<00:06:25.680> metadata<00:06:26.220> file<00:06:26.400> the<00:06:26.580> file<00:06:26.880> we 00:06:27.050 --> 00:06:27.060 align:start position:0% hash of the metadata file the file we 00:06:27.060 --> 00:06:30.650 align:start position:0% hash of the metadata file the file we saw<00:06:27.240> and<00:06:28.020> it<00:06:28.259> encodes<00:06:28.620> the<00:06:29.280> ipfs<00:06:29.759> hash<00:06:30.120> of<00:06:30.479> that 00:06:30.650 --> 00:06:30.660 align:start position:0% saw and it encodes the ipfs hash of that 00:06:30.660 --> 00:06:32.809 align:start position:0% saw and it encodes the ipfs hash of that file<00:06:31.020> here<00:06:31.500> alongside<00:06:32.400> some<00:06:32.699> other 00:06:32.809 --> 00:06:32.819 align:start position:0% file here alongside some other 00:06:32.819 --> 00:06:36.050 align:start position:0% file here alongside some other information<00:06:33.120> maybe<00:06:33.600> I'll<00:06:33.840> pull<00:06:34.020> this<00:06:34.500> as<00:06:34.680> well 00:06:36.050 --> 00:06:36.060 align:start position:0% information maybe I'll pull this as well 00:06:36.060 --> 00:06:38.510 align:start position:0% information maybe I'll pull this as well alongside<00:06:36.720> some<00:06:36.960> other<00:06:37.139> information 00:06:38.510 --> 00:06:38.520 align:start position:0% alongside some other information 00:06:38.520 --> 00:06:42.409 align:start position:0% alongside some other information and<00:06:39.360> yeah<00:06:39.660> you<00:06:40.020> can<00:06:40.199> see<00:06:41.039> how<00:06:41.340> this<00:06:41.520> works<00:06:41.880> in 00:06:42.409 --> 00:06:42.419 align:start position:0% and yeah you can see how this works in 00:06:42.419 --> 00:06:44.590 align:start position:0% and yeah you can see how this works in our<00:06:42.720> playground<00:06:43.020> playground<00:06:43.560> Source<00:06:43.919> Phi<00:06:44.100> Dev 00:06:44.590 --> 00:06:44.600 align:start position:0% our playground playground Source Phi Dev 00:06:44.600 --> 00:06:48.110 align:start position:0% our playground playground Source Phi Dev we<00:06:45.600> basically<00:06:45.960> show<00:06:46.280> how<00:06:47.280> the<00:06:47.520> encoding<00:06:47.940> is 00:06:48.110 --> 00:06:48.120 align:start position:0% we basically show how the encoding is 00:06:48.120 --> 00:06:50.150 align:start position:0% we basically show how the encoding is done<00:06:48.240> what<00:06:48.720> the<00:06:48.900> encoding<00:06:49.319> contains<00:06:49.800> and<00:06:50.039> we 00:06:50.150 --> 00:06:50.160 align:start position:0% done what the encoding contains and we 00:06:50.160 --> 00:06:52.309 align:start position:0% done what the encoding contains and we also<00:06:50.400> try<00:06:50.580> to<00:06:50.759> metadata<00:06:51.479> from<00:06:51.600> ipfs<00:06:52.139> it's 00:06:52.309 --> 00:06:52.319 align:start position:0% also try to metadata from ipfs it's 00:06:52.319 --> 00:06:55.850 align:start position:0% also try to metadata from ipfs it's already<00:06:52.500> there<00:06:52.800> so<00:06:53.639> it's<00:06:53.819> a<00:06:54.000> nice<00:06:54.180> tool<00:06:54.860> there 00:06:55.850 --> 00:06:55.860 align:start position:0% already there so it's a nice tool there 00:06:55.860 --> 00:06:57.770 align:start position:0% already there so it's a nice tool there are<00:06:55.979> some<00:06:56.100> example<00:06:56.460> contracts<00:06:57.000> you<00:06:57.419> can<00:06:57.479> click 00:06:57.770 --> 00:06:57.780 align:start position:0% are some example contracts you can click 00:06:57.780 --> 00:06:59.990 align:start position:0% are some example contracts you can click on<00:06:57.900> or<00:06:58.560> you<00:06:58.740> can<00:06:58.800> just<00:06:58.979> provide<00:06:59.340> us<00:06:59.520> with<00:06:59.880> the 00:06:59.990 --> 00:07:00.000 align:start position:0% on or you can just provide us with the 00:07:00.000 --> 00:07:01.610 align:start position:0% on or you can just provide us with the contract<00:07:00.300> address<00:07:00.479> or<00:07:01.080> just<00:07:01.199> paste<00:07:01.560> the 00:07:01.610 --> 00:07:01.620 align:start position:0% contract address or just paste the 00:07:01.620 --> 00:07:04.070 align:start position:0% contract address or just paste the contract<00:07:01.860> bytecode<00:07:02.400> and<00:07:03.000> we<00:07:03.240> will<00:07:03.600> try<00:07:03.900> to 00:07:04.070 --> 00:07:04.080 align:start position:0% contract bytecode and we will try to 00:07:04.080 --> 00:07:06.890 align:start position:0% contract bytecode and we will try to visualize<00:07:04.560> how<00:07:05.220> this<00:07:05.400> thing<00:07:05.580> works 00:07:06.890 --> 00:07:06.900 align:start position:0% visualize how this thing works 00:07:06.900 --> 00:07:10.070 align:start position:0% visualize how this thing works all<00:07:07.440> right<00:07:07.759> let's<00:07:08.759> let's<00:07:09.300> go<00:07:09.600> down<00:07:09.720> to<00:07:09.900> the 00:07:10.070 --> 00:07:10.080 align:start position:0% all right let's let's go down to the 00:07:10.080 --> 00:07:11.809 align:start position:0% all right let's let's go down to the second<00:07:10.380> thing<00:07:10.680> source<00:07:11.100> code<00:07:11.220> verification<00:07:11.639> on 00:07:11.809 --> 00:07:11.819 align:start position:0% second thing source code verification on 00:07:11.819 --> 00:07:13.070 align:start position:0% second thing source code verification on source5 00:07:13.070 --> 00:07:13.080 align:start position:0% source5 00:07:13.080 --> 00:07:14.390 align:start position:0% source5 but<00:07:13.500> before<00:07:13.680> what<00:07:13.919> is<00:07:14.100> source<00:07:14.340> code 00:07:14.390 --> 00:07:14.400 align:start position:0% but before what is source code 00:07:14.400 --> 00:07:16.129 align:start position:0% but before what is source code verification 00:07:16.129 --> 00:07:16.139 align:start position:0% verification 00:07:16.139 --> 00:07:19.909 align:start position:0% verification so<00:07:16.740> this<00:07:17.580> is<00:07:17.759> for<00:07:18.360> all<00:07:18.539> of<00:07:18.900> you<00:07:19.080> know<00:07:19.380> this<00:07:19.860> is 00:07:19.909 --> 00:07:19.919 align:start position:0% so this is for all of you know this is 00:07:19.919 --> 00:07:21.529 align:start position:0% so this is for all of you know this is like<00:07:20.099> you<00:07:20.520> probably<00:07:20.639> have<00:07:20.819> seen<00:07:21.000> this<00:07:21.180> if<00:07:21.360> you 00:07:21.529 --> 00:07:21.539 align:start position:0% like you probably have seen this if you 00:07:21.539 --> 00:07:24.170 align:start position:0% like you probably have seen this if you have<00:07:21.660> seen<00:07:21.900> a<00:07:22.080> contract<00:07:22.380> before<00:07:22.560> and<00:07:23.520> you<00:07:24.000> see 00:07:24.170 --> 00:07:24.180 align:start position:0% have seen a contract before and you see 00:07:24.180 --> 00:07:26.629 align:start position:0% have seen a contract before and you see a<00:07:24.300> green<00:07:24.539> check<00:07:24.720> mark<00:07:25.020> you're<00:07:25.860> happy<00:07:26.099> you<00:07:26.580> know 00:07:26.629 --> 00:07:26.639 align:start position:0% a green check mark you're happy you know 00:07:26.639 --> 00:07:27.890 align:start position:0% a green check mark you're happy you know the<00:07:26.880> contract 00:07:27.890 --> 00:07:27.900 align:start position:0% the contract 00:07:27.900 --> 00:07:29.390 align:start position:0% the contract right 00:07:29.390 --> 00:07:29.400 align:start position:0% right 00:07:29.400 --> 00:07:30.529 align:start position:0% right um 00:07:30.529 --> 00:07:30.539 align:start position:0% um 00:07:30.539 --> 00:07:33.170 align:start position:0% um okay<00:07:30.960> but<00:07:31.139> how<00:07:31.440> does<00:07:31.620> this<00:07:31.740> work 00:07:33.170 --> 00:07:33.180 align:start position:0% okay but how does this work 00:07:33.180 --> 00:07:36.589 align:start position:0% okay but how does this work um<00:07:33.240> maybe<00:07:33.479> before<00:07:33.840> that<00:07:34.139> like<00:07:34.440> it<00:07:34.680> is<00:07:35.060> uh<00:07:36.060> the 00:07:36.589 --> 00:07:36.599 align:start position:0% um maybe before that like it is uh the 00:07:36.599 --> 00:07:38.450 align:start position:0% um maybe before that like it is uh the reason<00:07:36.720> we<00:07:36.960> need<00:07:37.199> why<00:07:37.560> we<00:07:37.740> need<00:07:37.860> source<00:07:38.400> code 00:07:38.450 --> 00:07:38.460 align:start position:0% reason we need why we need source code 00:07:38.460 --> 00:07:41.089 align:start position:0% reason we need why we need source code verification<00:07:38.880> is<00:07:39.360> that<00:07:39.660> the<00:07:40.560> contracts 00:07:41.089 --> 00:07:41.099 align:start position:0% verification is that the contracts 00:07:41.099 --> 00:07:43.309 align:start position:0% verification is that the contracts actually<00:07:41.460> live<00:07:41.940> on<00:07:42.300> blockchain<00:07:42.720> as<00:07:42.960> byte 00:07:43.309 --> 00:07:43.319 align:start position:0% actually live on blockchain as byte 00:07:43.319 --> 00:07:45.230 align:start position:0% actually live on blockchain as byte codes<00:07:43.440> like<00:07:43.800> they<00:07:44.460> are 00:07:45.230 --> 00:07:45.240 align:start position:0% codes like they are 00:07:45.240 --> 00:07:47.809 align:start position:0% codes like they are we<00:07:45.840> write<00:07:46.080> the<00:07:46.440> humans<00:07:46.800> write<00:07:46.979> code<00:07:47.280> in<00:07:47.580> human 00:07:47.809 --> 00:07:47.819 align:start position:0% we write the humans write code in human 00:07:47.819 --> 00:07:51.110 align:start position:0% we write the humans write code in human language<00:07:48.180> but<00:07:49.080> the<00:07:49.380> machines<00:07:49.880> really<00:07:50.880> didn't 00:07:51.110 --> 00:07:51.120 align:start position:0% language but the machines really didn't 00:07:51.120 --> 00:07:54.110 align:start position:0% language but the machines really didn't bite<00:07:51.419> so<00:07:51.780> the<00:07:52.680> code<00:07:52.919> gets<00:07:53.340> compiled<00:07:53.819> and 00:07:54.110 --> 00:07:54.120 align:start position:0% bite so the code gets compiled and 00:07:54.120 --> 00:07:56.029 align:start position:0% bite so the code gets compiled and deployed<00:07:54.479> to<00:07:54.599> the<00:07:54.780> blockchain<00:07:55.560> and<00:07:55.860> this 00:07:56.029 --> 00:07:56.039 align:start position:0% deployed to the blockchain and this 00:07:56.039 --> 00:07:58.010 align:start position:0% deployed to the blockchain and this information<00:07:56.220> is<00:07:56.699> lost<00:07:56.880> in<00:07:57.180> the<00:07:57.300> process<00:07:57.539> so<00:07:57.780> we 00:07:58.010 --> 00:07:58.020 align:start position:0% information is lost in the process so we 00:07:58.020 --> 00:07:59.089 align:start position:0% information is lost in the process so we need<00:07:58.259> to 00:07:59.089 --> 00:07:59.099 align:start position:0% need to 00:07:59.099 --> 00:08:02.930 align:start position:0% need to somehow<00:07:59.699> make<00:08:00.060> sure<00:08:00.380> uh<00:08:01.380> just<00:08:01.620> a<00:08:01.740> random<00:08:02.039> code 00:08:02.930 --> 00:08:02.940 align:start position:0% somehow make sure uh just a random code 00:08:02.940 --> 00:08:05.089 align:start position:0% somehow make sure uh just a random code you<00:08:03.479> see<00:08:03.720> is<00:08:04.020> actually<00:08:04.199> the<00:08:04.440> same<00:08:04.620> the<00:08:04.979> code 00:08:05.089 --> 00:08:05.099 align:start position:0% you see is actually the same the code 00:08:05.099 --> 00:08:07.430 align:start position:0% you see is actually the same the code behind<00:08:05.520> the<00:08:05.699> contract<00:08:06.120> so<00:08:06.780> that's<00:08:07.139> the 00:08:07.430 --> 00:08:07.440 align:start position:0% behind the contract so that's the 00:08:07.440 --> 00:08:09.589 align:start position:0% behind the contract so that's the process<00:08:07.680> of<00:08:07.860> knowing<00:08:08.340> this<00:08:09.180> course<00:08:09.360> is 00:08:09.589 --> 00:08:09.599 align:start position:0% process of knowing this course is 00:08:09.599 --> 00:08:11.450 align:start position:0% process of knowing this course is actually<00:08:09.720> the<00:08:10.020> one<00:08:10.199> that<00:08:10.979> is<00:08:11.039> running<00:08:11.220> the 00:08:11.450 --> 00:08:11.460 align:start position:0% actually the one that is running the 00:08:11.460 --> 00:08:13.969 align:start position:0% actually the one that is running the contract<00:08:11.699> is<00:08:12.000> source<00:08:12.539> code<00:08:12.599> verification<00:08:13.560> so 00:08:13.969 --> 00:08:13.979 align:start position:0% contract is source code verification so 00:08:13.979 --> 00:08:17.710 align:start position:0% contract is source code verification so how<00:08:14.099> does<00:08:14.280> this<00:08:14.460> work<00:08:14.780> uh<00:08:15.780> you<00:08:16.199> have<00:08:16.580> the 00:08:17.710 --> 00:08:17.720 align:start position:0% how does this work uh you have the 00:08:17.720 --> 00:08:20.270 align:start position:0% how does this work uh you have the contracts<00:08:18.720> solidity<00:08:19.259> files<00:08:19.740> in<00:08:19.979> this<00:08:20.099> case 00:08:20.270 --> 00:08:20.280 align:start position:0% contracts solidity files in this case 00:08:20.280 --> 00:08:23.150 align:start position:0% contracts solidity files in this case you<00:08:20.819> have<00:08:20.940> a<00:08:21.060> Target<00:08:21.180> contract<00:08:21.720> you<00:08:22.620> also<00:08:22.979> have 00:08:23.150 --> 00:08:23.160 align:start position:0% you have a Target contract you also have 00:08:23.160 --> 00:08:24.950 align:start position:0% you have a Target contract you also have compilation<00:08:23.699> settings<00:08:24.000> like<00:08:24.479> the<00:08:24.780> version 00:08:24.950 --> 00:08:24.960 align:start position:0% compilation settings like the version 00:08:24.960 --> 00:08:27.610 align:start position:0% compilation settings like the version the<00:08:25.560> optimizer<00:08:26.099> settings<00:08:26.280> the<00:08:27.180> other<00:08:27.360> things 00:08:27.610 --> 00:08:27.620 align:start position:0% the optimizer settings the other things 00:08:27.620 --> 00:08:31.249 align:start position:0% the optimizer settings the other things and<00:08:28.620> we<00:08:29.220> feed<00:08:29.460> those<00:08:29.879> into<00:08:30.360> a<00:08:30.539> compiler<00:08:30.960> and<00:08:31.139> we 00:08:31.249 --> 00:08:31.259 align:start position:0% and we feed those into a compiler and we 00:08:31.259 --> 00:08:33.769 align:start position:0% and we feed those into a compiler and we recompile<00:08:31.800> the<00:08:31.979> contract<00:08:32.279> and<00:08:32.640> remember<00:08:32.820> this 00:08:33.769 --> 00:08:33.779 align:start position:0% recompile the contract and remember this 00:08:33.779 --> 00:08:36.350 align:start position:0% recompile the contract and remember this is<00:08:33.899> actually<00:08:34.080> when<00:08:34.500> the<00:08:35.159> second<00:08:35.520> part<00:08:35.760> of<00:08:36.000> the 00:08:36.350 --> 00:08:36.360 align:start position:0% is actually when the second part of the 00:08:36.360 --> 00:08:38.930 align:start position:0% is actually when the second part of the Meta<00:08:37.020> Meta<00:08:37.560> data<00:08:38.099> information<00:08:38.279> comes<00:08:38.880> in 00:08:38.930 --> 00:08:38.940 align:start position:0% Meta Meta data information comes in 00:08:38.940 --> 00:08:41.810 align:start position:0% Meta Meta data information comes in handy<00:08:39.300> so<00:08:39.599> we<00:08:39.839> use<00:08:40.020> this<00:08:40.440> compilation<00:08:41.099> info<00:08:41.520> to 00:08:41.810 --> 00:08:41.820 align:start position:0% handy so we use this compilation info to 00:08:41.820 --> 00:08:43.790 align:start position:0% handy so we use this compilation info to reproduce<00:08:42.300> the<00:08:42.719> compilation<00:08:43.440> of<00:08:43.680> the 00:08:43.790 --> 00:08:43.800 align:start position:0% reproduce the compilation of the 00:08:43.800 --> 00:08:45.470 align:start position:0% reproduce the compilation of the contract<00:08:44.099> again 00:08:45.470 --> 00:08:45.480 align:start position:0% contract again 00:08:45.480 --> 00:08:49.430 align:start position:0% contract again so<00:08:46.200> we<00:08:46.500> feed<00:08:47.220> this<00:08:47.399> into<00:08:47.640> the<00:08:48.000> compiler<00:08:48.660> and 00:08:49.430 --> 00:08:49.440 align:start position:0% so we feed this into the compiler and 00:08:49.440 --> 00:08:51.829 align:start position:0% so we feed this into the compiler and the<00:08:49.560> compiler<00:08:49.920> gives<00:08:50.040> us<00:08:50.220> a<00:08:50.339> byte<00:08:50.580> code 00:08:51.829 --> 00:08:51.839 align:start position:0% the compiler gives us a byte code 00:08:51.839 --> 00:08:55.130 align:start position:0% the compiler gives us a byte code and<00:08:52.620> we<00:08:53.100> also<00:08:53.399> have<00:08:53.700> the<00:08:54.240> contract<00:08:54.660> that<00:08:55.019> we 00:08:55.130 --> 00:08:55.140 align:start position:0% and we also have the contract that we 00:08:55.140 --> 00:08:59.750 align:start position:0% and we also have the contract that we want<00:08:55.380> to<00:08:55.760> verify<00:08:56.760> so<00:08:57.540> we<00:08:57.959> get<00:08:58.740> the<00:08:58.980> code<00:08:59.160> of<00:08:59.640> the 00:08:59.750 --> 00:08:59.760 align:start position:0% want to verify so we get the code of the 00:08:59.760 --> 00:09:01.970 align:start position:0% want to verify so we get the code of the contract<00:09:00.060> from<00:09:00.600> the<00:09:00.779> blockchain 00:09:01.970 --> 00:09:01.980 align:start position:0% contract from the blockchain 00:09:01.980 --> 00:09:03.710 align:start position:0% contract from the blockchain this<00:09:02.279> will<00:09:02.399> give<00:09:02.580> us<00:09:02.640> a<00:09:02.760> bytecode 00:09:03.710 --> 00:09:03.720 align:start position:0% this will give us a bytecode 00:09:03.720 --> 00:09:07.730 align:start position:0% this will give us a bytecode then<00:09:04.140> we'll<00:09:04.320> see<00:09:04.560> if<00:09:04.980> these<00:09:05.459> actually<00:09:05.640> match 00:09:07.730 --> 00:09:07.740 align:start position:0% then we'll see if these actually match 00:09:07.740 --> 00:09:11.269 align:start position:0% then we'll see if these actually match and<00:09:08.459> in<00:09:09.060> source5<00:09:09.839> you<00:09:10.080> also<00:09:10.380> have<00:09:10.620> two<00:09:10.980> types 00:09:11.269 --> 00:09:11.279 align:start position:0% and in source5 you also have two types 00:09:11.279 --> 00:09:14.030 align:start position:0% and in source5 you also have two types of<00:09:11.399> matches<00:09:11.820> we<00:09:12.240> have<00:09:12.420> the<00:09:12.779> partial<00:09:13.260> match 00:09:14.030 --> 00:09:14.040 align:start position:0% of matches we have the partial match 00:09:14.040 --> 00:09:16.070 align:start position:0% of matches we have the partial match when<00:09:14.459> bytecode<00:09:14.940> match<00:09:15.180> and<00:09:15.420> we<00:09:15.600> have<00:09:15.720> the<00:09:15.899> full 00:09:16.070 --> 00:09:16.080 align:start position:0% when bytecode match and we have the full 00:09:16.080 --> 00:09:19.670 align:start position:0% when bytecode match and we have the full match<00:09:16.339> when<00:09:17.339> both<00:09:17.820> the<00:09:18.060> byte<00:09:18.360> code<00:09:18.540> and<00:09:19.500> the 00:09:19.670 --> 00:09:19.680 align:start position:0% match when both the byte code and the 00:09:19.680 --> 00:09:22.370 align:start position:0% match when both the byte code and the metadata<00:09:20.160> field<00:09:20.339> field<00:09:20.399> match<00:09:20.940> so<00:09:21.360> in 00:09:22.370 --> 00:09:22.380 align:start position:0% metadata field field match so in 00:09:22.380 --> 00:09:24.710 align:start position:0% metadata field field match so in right<00:09:22.980> now<00:09:23.160> today<00:09:23.399> when<00:09:24.120> you<00:09:24.240> are<00:09:24.360> verifying 00:09:24.710 --> 00:09:24.720 align:start position:0% right now today when you are verifying 00:09:24.720 --> 00:09:26.889 align:start position:0% right now today when you are verifying on<00:09:24.839> YouTube<00:09:24.959> scan<00:09:25.380> or<00:09:25.860> any<00:09:26.160> other<00:09:26.339> verifier 00:09:26.889 --> 00:09:26.899 align:start position:0% on YouTube scan or any other verifier 00:09:26.899 --> 00:09:29.509 align:start position:0% on YouTube scan or any other verifier they<00:09:27.899> actually<00:09:28.200> ignore<00:09:28.860> this<00:09:29.100> field<00:09:29.279> like 00:09:29.509 --> 00:09:29.519 align:start position:0% they actually ignore this field like 00:09:29.519 --> 00:09:30.949 align:start position:0% they actually ignore this field like they<00:09:29.700> don't<00:09:29.820> make<00:09:30.060> use<00:09:30.240> of<00:09:30.420> this<00:09:30.540> field<00:09:30.720> they 00:09:30.949 --> 00:09:30.959 align:start position:0% they don't make use of this field they 00:09:30.959 --> 00:09:33.110 align:start position:0% they don't make use of this field they just<00:09:31.080> trim<00:09:31.320> it<00:09:31.500> out<00:09:31.740> and<00:09:32.339> actually<00:09:32.640> that<00:09:32.880> there 00:09:33.110 --> 00:09:33.120 align:start position:0% just trim it out and actually that there 00:09:33.120 --> 00:09:35.690 align:start position:0% just trim it out and actually that there have<00:09:33.300> been<00:09:33.420> cases<00:09:33.899> that<00:09:34.200> this<00:09:34.380> was 00:09:35.690 --> 00:09:35.700 align:start position:0% have been cases that this was 00:09:35.700 --> 00:09:37.550 align:start position:0% have been cases that this was um<00:09:35.760> exploited<00:09:36.360> so<00:09:36.839> it<00:09:36.959> wasn't<00:09:37.140> a<00:09:37.320> serious 00:09:37.550 --> 00:09:37.560 align:start position:0% um exploited so it wasn't a serious 00:09:37.560 --> 00:09:39.170 align:start position:0% um exploited so it wasn't a serious thing<00:09:37.680> but<00:09:37.860> this<00:09:38.160> could<00:09:38.339> this<00:09:38.760> wasn't<00:09:38.880> really 00:09:39.170 --> 00:09:39.180 align:start position:0% thing but this could this wasn't really 00:09:39.180 --> 00:09:41.990 align:start position:0% thing but this could this wasn't really doing<00:09:39.480> was<00:09:39.839> being<00:09:40.080> done<00:09:40.320> properly<00:09:41.459> but<00:09:41.820> yeah 00:09:41.990 --> 00:09:42.000 align:start position:0% doing was being done properly but yeah 00:09:42.000 --> 00:09:44.170 align:start position:0% doing was being done properly but yeah with<00:09:42.360> the<00:09:42.480> full<00:09:42.600> match<00:09:42.779> you<00:09:43.200> have<00:09:43.380> a 00:09:44.170 --> 00:09:44.180 align:start position:0% with the full match you have a 00:09:44.180 --> 00:09:47.690 align:start position:0% with the full match you have a complete<00:09:45.180> match<00:09:45.360> of<00:09:45.540> the<00:09:45.660> bytecode<00:09:46.279> uh<00:09:47.279> and 00:09:47.690 --> 00:09:47.700 align:start position:0% complete match of the bytecode uh and 00:09:47.700 --> 00:09:50.090 align:start position:0% complete match of the bytecode uh and here<00:09:47.820> the<00:09:48.060> metadata<00:09:48.600> actually<00:09:48.779> acts<00:09:49.500> as<00:09:49.860> a 00:09:50.090 --> 00:09:50.100 align:start position:0% here the metadata actually acts as a 00:09:50.100 --> 00:09:53.449 align:start position:0% here the metadata actually acts as a compilation<00:09:50.519> fingerprint<00:09:51.180> so<00:09:51.800> if<00:09:52.800> you<00:09:53.040> match 00:09:53.449 --> 00:09:53.459 align:start position:0% compilation fingerprint so if you match 00:09:53.459 --> 00:09:56.090 align:start position:0% compilation fingerprint so if you match the<00:09:53.700> metadata<00:09:54.240> as<00:09:54.360> well<00:09:54.480> the<00:09:55.440> compilation<00:09:55.800> is 00:09:56.090 --> 00:09:56.100 align:start position:0% the metadata as well the compilation is 00:09:56.100 --> 00:09:59.150 align:start position:0% the metadata as well the compilation is exactly<00:09:56.519> the<00:09:56.700> same<00:09:56.940> as<00:09:57.899> the<00:09:58.320> original 00:09:59.150 --> 00:09:59.160 align:start position:0% exactly the same as the original 00:09:59.160 --> 00:10:02.090 align:start position:0% exactly the same as the original or<00:09:59.760> as<00:10:00.000> when<00:10:00.240> the<00:10:00.480> contract<00:10:01.200> was<00:10:01.320> deployed<00:10:01.800> so 00:10:02.090 --> 00:10:02.100 align:start position:0% or as when the contract was deployed so 00:10:02.100 --> 00:10:04.430 align:start position:0% or as when the contract was deployed so and<00:10:02.880> the<00:10:03.060> full<00:10:03.180> matches<00:10:03.660> actually 00:10:04.430 --> 00:10:04.440 align:start position:0% and the full matches actually 00:10:04.440 --> 00:10:06.470 align:start position:0% and the full matches actually cryptographically<00:10:05.279> guarantee<00:10:05.880> that<00:10:06.300> the 00:10:06.470 --> 00:10:06.480 align:start position:0% cryptographically guarantee that the 00:10:06.480 --> 00:10:08.630 align:start position:0% cryptographically guarantee that the whole<00:10:06.660> compilation<00:10:07.200> is<00:10:08.040> exactly<00:10:08.339> the<00:10:08.519> same 00:10:08.630 --> 00:10:08.640 align:start position:0% whole compilation is exactly the same 00:10:08.640 --> 00:10:10.910 align:start position:0% whole compilation is exactly the same including<00:10:09.060> the<00:10:09.180> solidity<00:10:09.600> files<00:10:10.019> comments 00:10:10.910 --> 00:10:10.920 align:start position:0% including the solidity files comments 00:10:10.920 --> 00:10:13.130 align:start position:0% including the solidity files comments spaces<00:10:11.700> variable<00:10:12.180> names<00:10:12.360> anything<00:10:12.720> like<00:10:12.959> you 00:10:13.130 --> 00:10:13.140 align:start position:0% spaces variable names anything like you 00:10:13.140 --> 00:10:16.490 align:start position:0% spaces variable names anything like you even<00:10:13.260> if<00:10:13.500> you<00:10:13.680> change<00:10:13.940> a<00:10:14.940> space<00:10:15.660> a<00:10:16.140> variable 00:10:16.490 --> 00:10:16.500 align:start position:0% even if you change a space a variable 00:10:16.500 --> 00:10:18.350 align:start position:0% even if you change a space a variable name<00:10:16.680> it<00:10:16.920> will<00:10:17.040> break<00:10:17.220> the<00:10:17.459> match 00:10:18.350 --> 00:10:18.360 align:start position:0% name it will break the match 00:10:18.360 --> 00:10:20.690 align:start position:0% name it will break the match so<00:10:18.899> how<00:10:19.260> does<00:10:19.440> this<00:10:19.560> work<00:10:19.740> let's<00:10:19.980> see<00:10:20.220> how<00:10:20.459> this 00:10:20.690 --> 00:10:20.700 align:start position:0% so how does this work let's see how this 00:10:20.700 --> 00:10:22.190 align:start position:0% so how does this work let's see how this actually<00:10:20.880> works 00:10:22.190 --> 00:10:22.200 align:start position:0% actually works 00:10:22.200 --> 00:10:24.650 align:start position:0% actually works again<00:10:22.920> when<00:10:23.820> you<00:10:23.940> are<00:10:24.120> compiling<00:10:24.480> your 00:10:24.650 --> 00:10:24.660 align:start position:0% again when you are compiling your 00:10:24.660 --> 00:10:25.730 align:start position:0% again when you are compiling your contract 00:10:25.730 --> 00:10:25.740 align:start position:0% contract 00:10:25.740 --> 00:10:29.030 align:start position:0% contract the<00:10:26.279> compiler<00:10:26.820> takes<00:10:27.720> the<00:10:27.899> hash<00:10:28.080> of<00:10:28.500> each<00:10:28.740> file 00:10:29.030 --> 00:10:29.040 align:start position:0% the compiler takes the hash of each file 00:10:29.040 --> 00:10:31.310 align:start position:0% the compiler takes the hash of each file each<00:10:29.700> each<00:10:29.940> solidity<00:10:30.420> file 00:10:31.310 --> 00:10:31.320 align:start position:0% each each solidity file 00:10:31.320 --> 00:10:34.130 align:start position:0% each each solidity file than<00:10:31.860> the<00:10:32.100> hashes<00:10:32.519> of<00:10:32.760> these<00:10:33.060> files<00:10:33.480> are 00:10:34.130 --> 00:10:34.140 align:start position:0% than the hashes of these files are 00:10:34.140 --> 00:10:36.170 align:start position:0% than the hashes of these files are actually<00:10:34.380> embedded<00:10:35.160> inside<00:10:35.399> the<00:10:35.640> metadata 00:10:36.170 --> 00:10:36.180 align:start position:0% actually embedded inside the metadata 00:10:36.180 --> 00:10:38.870 align:start position:0% actually embedded inside the metadata file<00:10:36.360> or<00:10:36.779> the<00:10:37.620> the<00:10:37.620> metadata<00:10:38.339> file<00:10:38.519> that<00:10:38.700> we 00:10:38.870 --> 00:10:38.880 align:start position:0% file or the the metadata file that we 00:10:38.880 --> 00:10:41.090 align:start position:0% file or the the metadata file that we saw<00:10:39.480> as<00:10:39.959> well<00:10:40.080> as<00:10:40.200> the<00:10:40.380> other<00:10:40.440> sources<00:10:40.860> not 00:10:41.090 --> 00:10:41.100 align:start position:0% saw as well as the other sources not 00:10:41.100 --> 00:10:42.290 align:start position:0% saw as well as the other sources not just<00:10:41.279> one 00:10:42.290 --> 00:10:42.300 align:start position:0% just one 00:10:42.300 --> 00:10:46.130 align:start position:0% just one then<00:10:42.899> as<00:10:43.680> said<00:10:43.980> the<00:10:44.940> compiler<00:10:45.300> takes<00:10:45.480> the<00:10:45.660> ipfs 00:10:46.130 --> 00:10:46.140 align:start position:0% then as said the compiler takes the ipfs 00:10:46.140 --> 00:10:49.069 align:start position:0% then as said the compiler takes the ipfs hash<00:10:46.380> of<00:10:47.160> this<00:10:47.579> whole<00:10:47.820> file 00:10:49.069 --> 00:10:49.079 align:start position:0% hash of this whole file 00:10:49.079 --> 00:10:52.190 align:start position:0% hash of this whole file and<00:10:49.560> then<00:10:49.740> this<00:10:50.160> ipfs<00:10:50.700> hash<00:10:50.940> is<00:10:51.180> embedded<00:10:52.079> at 00:10:52.190 --> 00:10:52.200 align:start position:0% and then this ipfs hash is embedded at 00:10:52.200 --> 00:10:54.050 align:start position:0% and then this ipfs hash is embedded at the<00:10:52.260> end<00:10:52.380> of<00:10:52.440> the<00:10:52.560> bytecode 00:10:54.050 --> 00:10:54.060 align:start position:0% the end of the bytecode 00:10:54.060 --> 00:10:56.569 align:start position:0% the end of the bytecode and<00:10:54.420> then<00:10:54.540> we<00:10:54.720> see<00:10:54.959> if<00:10:55.380> these<00:10:55.800> match<00:10:56.160> if<00:10:56.399> it's 00:10:56.569 --> 00:10:56.579 align:start position:0% and then we see if these match if it's 00:10:56.579 --> 00:10:58.550 align:start position:0% and then we see if these match if it's say<00:10:56.760> full<00:10:57.180> match<00:10:57.480> it's<00:10:57.839> a<00:10:58.019> match<00:10:58.140> it's<00:10:58.320> a<00:10:58.440> full 00:10:58.550 --> 00:10:58.560 align:start position:0% say full match it's a match it's a full 00:10:58.560 --> 00:11:00.350 align:start position:0% say full match it's a match it's a full match<00:10:58.800> if<00:10:59.220> they<00:10:59.399> match 00:11:00.350 --> 00:11:00.360 align:start position:0% match if they match 00:11:00.360 --> 00:11:02.870 align:start position:0% match if they match and<00:11:01.200> let's<00:11:01.620> see<00:11:01.860> what<00:11:02.100> happens<00:11:02.279> when<00:11:02.700> you 00:11:02.870 --> 00:11:02.880 align:start position:0% and let's see what happens when you 00:11:02.880 --> 00:11:04.370 align:start position:0% and let's see what happens when you change<00:11:03.180> something<00:11:03.420> when<00:11:03.660> you<00:11:03.839> make<00:11:03.959> a<00:11:04.140> slight 00:11:04.370 --> 00:11:04.380 align:start position:0% change something when you make a slight 00:11:04.380 --> 00:11:06.350 align:start position:0% change something when you make a slight change<00:11:04.560> change<00:11:05.459> the<00:11:05.700> space<00:11:05.880> change<00:11:06.240> your 00:11:06.350 --> 00:11:06.360 align:start position:0% change change the space change your 00:11:06.360 --> 00:11:09.170 align:start position:0% change change the space change your variable<00:11:06.660> name<00:11:06.839> any<00:11:07.079> comments<00:11:07.980> so<00:11:08.519> we<00:11:08.760> have<00:11:08.940> it 00:11:09.170 --> 00:11:09.180 align:start position:0% variable name any comments so we have it 00:11:09.180 --> 00:11:11.509 align:start position:0% variable name any comments so we have it my<00:11:09.600> contract<00:11:09.899> diff<00:11:10.140> this<00:11:10.620> time 00:11:11.509 --> 00:11:11.519 align:start position:0% my contract diff this time 00:11:11.519 --> 00:11:14.269 align:start position:0% my contract diff this time so<00:11:12.000> the<00:11:12.180> hash<00:11:12.300> of<00:11:12.540> the<00:11:12.720> file<00:11:12.899> will<00:11:13.079> change 00:11:14.269 --> 00:11:14.279 align:start position:0% so the hash of the file will change 00:11:14.279 --> 00:11:16.610 align:start position:0% so the hash of the file will change then<00:11:14.700> the<00:11:14.940> hash<00:11:15.120> inside<00:11:15.720> the<00:11:15.899> metadata<00:11:16.440> will 00:11:16.610 --> 00:11:16.620 align:start position:0% then the hash inside the metadata will 00:11:16.620 --> 00:11:17.509 align:start position:0% then the hash inside the metadata will change 00:11:17.509 --> 00:11:17.519 align:start position:0% change 00:11:17.519 --> 00:11:20.810 align:start position:0% change and<00:11:18.180> in<00:11:18.540> in<00:11:18.600> turn<00:11:19.079> the<00:11:19.740> hash<00:11:19.860> of<00:11:20.160> the<00:11:20.279> metadata 00:11:20.810 --> 00:11:20.820 align:start position:0% and in in turn the hash of the metadata 00:11:20.820 --> 00:11:23.030 align:start position:0% and in in turn the hash of the metadata file<00:11:21.420> itself<00:11:21.720> will<00:11:21.959> change<00:11:22.200> so<00:11:22.800> this<00:11:22.920> field 00:11:23.030 --> 00:11:23.040 align:start position:0% file itself will change so this field 00:11:23.040 --> 00:11:25.610 align:start position:0% file itself will change so this field will<00:11:23.279> be<00:11:23.399> different<00:11:23.519> this<00:11:23.760> time<00:11:24.060> and<00:11:24.959> that 00:11:25.610 --> 00:11:25.620 align:start position:0% will be different this time and that 00:11:25.620 --> 00:11:28.490 align:start position:0% will be different this time and that means<00:11:26.040> this<00:11:26.820> will<00:11:27.000> not<00:11:27.120> be<00:11:27.300> a<00:11:27.480> full<00:11:27.660> match<00:11:27.899> and 00:11:28.490 --> 00:11:28.500 align:start position:0% means this will not be a full match and 00:11:28.500 --> 00:11:30.350 align:start position:0% means this will not be a full match and but<00:11:28.800> this<00:11:28.980> will<00:11:29.100> be<00:11:29.220> a<00:11:29.339> partial<00:11:29.579> match 00:11:30.350 --> 00:11:30.360 align:start position:0% but this will be a partial match 00:11:30.360 --> 00:11:32.449 align:start position:0% but this will be a partial match assuming<00:11:31.019> you<00:11:31.200> didn't<00:11:31.380> make<00:11:31.740> a<00:11:31.920> change<00:11:32.100> that 00:11:32.449 --> 00:11:32.459 align:start position:0% assuming you didn't make a change that 00:11:32.459 --> 00:11:33.889 align:start position:0% assuming you didn't make a change that will<00:11:32.579> change<00:11:32.820> the<00:11:33.060> functionality<00:11:33.600> of<00:11:33.779> the 00:11:33.889 --> 00:11:33.899 align:start position:0% will change the functionality of the 00:11:33.899 --> 00:11:37.190 align:start position:0% will change the functionality of the contract<00:11:34.140> just<00:11:34.380> a<00:11:34.680> comment<00:11:35.339> or<00:11:35.640> variable 00:11:37.190 --> 00:11:37.200 align:start position:0% contract just a comment or variable 00:11:37.200 --> 00:11:40.970 align:start position:0% contract just a comment or variable okay<00:11:37.680> but<00:11:37.980> then<00:11:38.519> how<00:11:38.700> to<00:11:38.880> verify<00:11:39.680> so<00:11:40.680> you<00:11:40.860> can 00:11:40.970 --> 00:11:40.980 align:start position:0% okay but then how to verify so you can 00:11:40.980 --> 00:11:44.329 align:start position:0% okay but then how to verify so you can use<00:11:41.339> the<00:11:41.519> source<00:11:41.880> file<00:11:42.180> UI<00:11:42.660> you<00:11:43.140> can<00:11:43.320> give<00:11:44.100> us 00:11:44.329 --> 00:11:44.339 align:start position:0% use the source file UI you can give us 00:11:44.339 --> 00:11:46.850 align:start position:0% use the source file UI you can give us the<00:11:44.880> source<00:11:45.420> code<00:11:45.540> and<00:11:45.839> the<00:11:45.959> metadata<00:11:46.440> file<00:11:46.680> we 00:11:46.850 --> 00:11:46.860 align:start position:0% the source code and the metadata file we 00:11:46.860 --> 00:11:48.470 align:start position:0% the source code and the metadata file we need<00:11:46.980> the<00:11:47.100> metadata<00:11:47.519> file<00:11:47.760> to<00:11:48.060> be<00:11:48.240> able<00:11:48.360> to 00:11:48.470 --> 00:11:48.480 align:start position:0% need the metadata file to be able to 00:11:48.480 --> 00:11:51.470 align:start position:0% need the metadata file to be able to verify<00:11:49.220> either<00:11:50.220> from<00:11:50.760> your<00:11:50.940> computer<00:11:51.120> or 00:11:51.470 --> 00:11:51.480 align:start position:0% verify either from your computer or 00:11:51.480 --> 00:11:53.630 align:start position:0% verify either from your computer or etherscan<00:11:52.140> remote<00:11:52.380> GitHub<00:11:52.920> however<00:11:53.220> you<00:11:53.459> like 00:11:53.630 --> 00:11:53.640 align:start position:0% etherscan remote GitHub however you like 00:11:53.640 --> 00:11:55.550 align:start position:0% etherscan remote GitHub however you like then<00:11:54.300> you<00:11:54.480> give<00:11:54.660> us<00:11:54.779> the<00:11:55.019> contract<00:11:55.320> address 00:11:55.550 --> 00:11:55.560 align:start position:0% then you give us the contract address 00:11:55.560 --> 00:11:58.009 align:start position:0% then you give us the contract address contract<00:11:56.100> chain<00:11:56.279> we<00:11:56.640> try<00:11:56.820> to<00:11:57.060> wait<00:11:57.180> file<00:11:57.480> you 00:11:58.009 --> 00:11:58.019 align:start position:0% contract chain we try to wait file you 00:11:58.019 --> 00:12:01.190 align:start position:0% contract chain we try to wait file you can<00:11:58.140> use<00:11:58.260> the<00:11:58.440> API<00:11:58.800> we<00:11:59.459> have<00:11:59.700> an<00:11:59.880> endpoint<00:12:00.540> and 00:12:01.190 --> 00:12:01.200 align:start position:0% can use the API we have an endpoint and 00:12:01.200 --> 00:12:03.710 align:start position:0% can use the API we have an endpoint and other<00:12:01.440> several<00:12:01.860> API<00:12:02.220> endpoints<00:12:02.760> as<00:12:02.940> well<00:12:03.120> you 00:12:03.710 --> 00:12:03.720 align:start position:0% other several API endpoints as well you 00:12:03.720 --> 00:12:07.250 align:start position:0% other several API endpoints as well you can<00:12:03.839> check<00:12:03.959> them<00:12:04.140> out<00:12:04.320> in<00:12:04.700> docs.ify<00:12:05.700> Dev<00:12:06.300> uh<00:12:06.959> we 00:12:07.250 --> 00:12:07.260 align:start position:0% can check them out in docs.ify Dev uh we 00:12:07.260 --> 00:12:09.230 align:start position:0% can check them out in docs.ify Dev uh we have<00:12:07.380> some<00:12:07.500> detailed<00:12:07.860> talks<00:12:08.220> about<00:12:08.339> this 00:12:09.230 --> 00:12:09.240 align:start position:0% have some detailed talks about this 00:12:09.240 --> 00:12:12.710 align:start position:0% have some detailed talks about this and<00:12:10.140> we<00:12:10.620> also<00:12:10.800> have<00:12:10.920> the<00:12:11.100> tooling<00:12:11.459> so<00:12:12.420> if<00:12:12.660> you 00:12:12.710 --> 00:12:12.720 align:start position:0% and we also have the tooling so if you 00:12:12.720 --> 00:12:14.690 align:start position:0% and we also have the tooling so if you are<00:12:12.839> using<00:12:13.079> hard<00:12:13.260> hat<00:12:13.620> there's<00:12:14.100> a<00:12:14.279> hard<00:12:14.399> hat 00:12:14.690 --> 00:12:14.700 align:start position:0% are using hard hat there's a hard hat 00:12:14.700 --> 00:12:18.050 align:start position:0% are using hard hat there's a hard hat deploy<00:12:14.940> plugin<00:12:15.360> and<00:12:16.260> with<00:12:16.680> the<00:12:16.800> plugin<00:12:17.220> when 00:12:18.050 --> 00:12:18.060 align:start position:0% deploy plugin and with the plugin when 00:12:18.060 --> 00:12:19.670 align:start position:0% deploy plugin and with the plugin when after<00:12:18.360> you<00:12:18.600> deploy<00:12:18.839> your<00:12:18.959> contract<00:12:19.260> you<00:12:19.560> can 00:12:19.670 --> 00:12:19.680 align:start position:0% after you deploy your contract you can 00:12:19.680 --> 00:12:20.569 align:start position:0% after you deploy your contract you can just 00:12:20.569 --> 00:12:20.579 align:start position:0% just 00:12:20.579 --> 00:12:23.030 align:start position:0% just pass<00:12:20.880> the<00:12:21.120> network<00:12:21.240> and<00:12:22.079> then<00:12:22.260> say<00:12:22.440> sourcify 00:12:23.030 --> 00:12:23.040 align:start position:0% pass the network and then say sourcify 00:12:23.040 --> 00:12:25.790 align:start position:0% pass the network and then say sourcify and<00:12:23.220> use<00:12:23.579> the<00:12:23.820> verify<00:12:24.420> your<00:12:24.540> contract<00:12:24.899> we<00:12:25.680> have 00:12:25.790 --> 00:12:25.800 align:start position:0% and use the verify your contract we have 00:12:25.800 --> 00:12:27.530 align:start position:0% and use the verify your contract we have the<00:12:25.920> remix<00:12:26.040> plugin<00:12:26.579> if<00:12:26.880> you<00:12:27.000> are<00:12:27.120> using<00:12:27.360> remix 00:12:27.530 --> 00:12:27.540 align:start position:0% the remix plugin if you are using remix 00:12:27.540 --> 00:12:28.910 align:start position:0% the remix plugin if you are using remix you<00:12:28.200> can 00:12:28.910 --> 00:12:28.920 align:start position:0% you can 00:12:28.920 --> 00:12:31.970 align:start position:0% you can provide<00:12:29.579> the<00:12:29.880> contract<00:12:30.420> address<00:12:30.660> the<00:12:31.079> chain 00:12:31.970 --> 00:12:31.980 align:start position:0% provide the contract address the chain 00:12:31.980 --> 00:12:35.389 align:start position:0% provide the contract address the chain when<00:12:32.339> we<00:12:32.579> will<00:12:32.700> verify<00:12:33.260> we<00:12:34.260> recently<00:12:34.620> have<00:12:34.920> a 00:12:35.389 --> 00:12:35.399 align:start position:0% when we will verify we recently have a 00:12:35.399 --> 00:12:36.710 align:start position:0% when we will verify we recently have a Foundry<00:12:35.820> support 00:12:36.710 --> 00:12:36.720 align:start position:0% Foundry support 00:12:36.720 --> 00:12:39.110 align:start position:0% Foundry support so<00:12:37.200> using<00:12:37.620> Foundry<00:12:38.040> you<00:12:38.220> can<00:12:38.339> also 00:12:39.110 --> 00:12:39.120 align:start position:0% so using Foundry you can also 00:12:39.120 --> 00:12:42.050 align:start position:0% so using Foundry you can also easily<00:12:39.779> verify<00:12:40.200> your<00:12:40.320> contracts 00:12:42.050 --> 00:12:42.060 align:start position:0% easily verify your contracts 00:12:42.060 --> 00:12:44.629 align:start position:0% easily verify your contracts and<00:12:42.660> we<00:12:42.899> also<00:12:43.139> have<00:12:43.440> some<00:12:44.160> automatic 00:12:44.629 --> 00:12:44.639 align:start position:0% and we also have some automatic 00:12:44.639 --> 00:12:48.350 align:start position:0% and we also have some automatic verification<00:12:45.060> so<00:12:45.720> what<00:12:45.959> we<00:12:46.139> call<00:12:46.320> monitor<00:12:47.360> so 00:12:48.350 --> 00:12:48.360 align:start position:0% verification so what we call monitor so 00:12:48.360 --> 00:12:50.329 align:start position:0% verification so what we call monitor so we<00:12:48.480> have<00:12:48.540> a<00:12:48.660> monitor<00:12:49.019> running<00:12:49.200> that<00:12:50.160> is 00:12:50.329 --> 00:12:50.339 align:start position:0% we have a monitor running that is 00:12:50.339 --> 00:12:53.389 align:start position:0% we have a monitor running that is listening<00:12:51.060> on<00:12:51.480> on<00:12:51.899> several<00:12:52.620> chains<00:12:53.040> we<00:12:53.220> are 00:12:53.389 --> 00:12:53.399 align:start position:0% listening on on several chains we are 00:12:53.399 --> 00:12:55.550 align:start position:0% listening on on several chains we are right<00:12:53.700> now<00:12:53.820> listening<00:12:54.240> to<00:12:54.540> ethereum<00:12:55.200> main<00:12:55.380> net 00:12:55.550 --> 00:12:55.560 align:start position:0% right now listening to ethereum main net 00:12:55.560 --> 00:12:58.790 align:start position:0% right now listening to ethereum main net test<00:12:55.740> Nets<00:12:56.220> as<00:12:56.880> well<00:12:57.000> as<00:12:57.180> some<00:12:57.540> Roll-Ups<00:12:58.200> out 00:12:58.790 --> 00:12:58.800 align:start position:0% test Nets as well as some Roll-Ups out 00:12:58.800 --> 00:13:01.850 align:start position:0% test Nets as well as some Roll-Ups out as<00:12:59.220> far<00:12:59.339> as<00:12:59.459> remember<00:12:59.839> so<00:13:00.839> the<00:13:01.019> monitor<00:13:01.380> what 00:13:01.850 --> 00:13:01.860 align:start position:0% as far as remember so the monitor what 00:13:01.860 --> 00:13:03.610 align:start position:0% as far as remember so the monitor what it<00:13:01.980> does<00:13:02.100> it<00:13:02.399> catches<00:13:02.820> contract<00:13:03.240> creations 00:13:03.610 --> 00:13:03.620 align:start position:0% it does it catches contract creations 00:13:03.620 --> 00:13:06.290 align:start position:0% it does it catches contract creations and<00:13:04.620> then<00:13:04.800> when<00:13:05.220> it<00:13:05.399> finds<00:13:05.820> a<00:13:05.940> contract 00:13:06.290 --> 00:13:06.300 align:start position:0% and then when it finds a contract 00:13:06.300 --> 00:13:08.230 align:start position:0% and then when it finds a contract creation<00:13:06.720> it<00:13:07.320> will 00:13:08.230 --> 00:13:08.240 align:start position:0% creation it will 00:13:08.240 --> 00:13:11.210 align:start position:0% creation it will fetch<00:13:09.240> the<00:13:09.420> metadata<00:13:10.079> as<00:13:10.560> you<00:13:10.680> remember<00:13:10.800> it's 00:13:11.210 --> 00:13:11.220 align:start position:0% fetch the metadata as you remember it's 00:13:11.220 --> 00:13:13.430 align:start position:0% fetch the metadata as you remember it's like<00:13:11.399> ipfs<00:13:11.880> hash<00:13:12.120> is<00:13:12.240> over<00:13:12.420> there<00:13:12.660> so<00:13:13.079> it<00:13:13.320> will 00:13:13.430 --> 00:13:13.440 align:start position:0% like ipfs hash is over there so it will 00:13:13.440 --> 00:13:16.430 align:start position:0% like ipfs hash is over there so it will get<00:13:13.920> the<00:13:14.040> ipfs<00:13:14.519> try<00:13:15.240> to<00:13:15.420> fetch<00:13:15.720> it<00:13:15.720> from<00:13:15.839> ipfs 00:13:16.430 --> 00:13:16.440 align:start position:0% get the ipfs try to fetch it from ipfs 00:13:16.440 --> 00:13:18.590 align:start position:0% get the ipfs try to fetch it from ipfs and<00:13:16.980> also<00:13:17.160> the<00:13:17.279> metadata<00:13:17.820> file<00:13:18.000> has<00:13:18.240> the 00:13:18.590 --> 00:13:18.600 align:start position:0% and also the metadata file has the 00:13:18.600 --> 00:13:20.930 align:start position:0% and also the metadata file has the source<00:13:19.079> hashes<00:13:19.440> source<00:13:19.920> ipfs<00:13:20.339> hashes<00:13:20.639> it<00:13:20.820> will 00:13:20.930 --> 00:13:20.940 align:start position:0% source hashes source ipfs hashes it will 00:13:20.940 --> 00:13:23.629 align:start position:0% source hashes source ipfs hashes it will try<00:13:21.060> to<00:13:21.180> get<00:13:21.300> the<00:13:21.420> source<00:13:21.720> files<00:13:22.019> from<00:13:22.459> ipfs<00:13:23.459> as 00:13:23.629 --> 00:13:23.639 align:start position:0% try to get the source files from ipfs as 00:13:23.639 --> 00:13:26.150 align:start position:0% try to get the source files from ipfs as well<00:13:23.820> if<00:13:24.420> it<00:13:24.540> finds<00:13:24.899> them<00:13:25.079> then<00:13:25.680> it<00:13:25.980> will 00:13:26.150 --> 00:13:26.160 align:start position:0% well if it finds them then it will 00:13:26.160 --> 00:13:29.269 align:start position:0% well if it finds them then it will automatically<00:13:26.700> compile<00:13:27.180> and<00:13:27.959> try<00:13:28.380> to<00:13:28.560> verify 00:13:29.269 --> 00:13:29.279 align:start position:0% automatically compile and try to verify 00:13:29.279 --> 00:13:31.129 align:start position:0% automatically compile and try to verify the<00:13:29.820> contract 00:13:31.129 --> 00:13:31.139 align:start position:0% the contract 00:13:31.139 --> 00:13:33.170 align:start position:0% the contract so<00:13:31.740> that<00:13:32.040> means<00:13:32.279> actually<00:13:32.459> the<00:13:32.820> Second<00:13:32.940> Step 00:13:33.170 --> 00:13:33.180 align:start position:0% so that means actually the Second Step 00:13:33.180 --> 00:13:35.030 align:start position:0% so that means actually the Second Step here<00:13:33.480> the<00:13:34.079> source<00:13:34.320> code<00:13:34.380> verification<00:13:34.800> on 00:13:35.030 --> 00:13:35.040 align:start position:0% here the source code verification on 00:13:35.040 --> 00:13:36.829 align:start position:0% here the source code verification on Source<00:13:35.339> Phi<00:13:35.579> has<00:13:36.000> become 00:13:36.829 --> 00:13:36.839 align:start position:0% Source Phi has become 00:13:36.839 --> 00:13:38.509 align:start position:0% Source Phi has become publishing<00:13:37.500> your<00:13:37.620> metadata<00:13:38.160> so<00:13:38.279> you<00:13:38.459> don't 00:13:38.509 --> 00:13:38.519 align:start position:0% publishing your metadata so you don't 00:13:38.519 --> 00:13:39.769 align:start position:0% publishing your metadata so you don't even<00:13:38.700> have<00:13:38.940> to 00:13:39.769 --> 00:13:39.779 align:start position:0% even have to 00:13:39.779 --> 00:13:41.990 align:start position:0% even have to take<00:13:40.200> the<00:13:40.320> extra<00:13:40.500> step<00:13:40.800> and<00:13:41.160> go<00:13:41.279> to<00:13:41.399> sourcify 00:13:41.990 --> 00:13:42.000 align:start position:0% take the extra step and go to sourcify 00:13:42.000 --> 00:13:43.970 align:start position:0% take the extra step and go to sourcify and<00:13:42.480> verify<00:13:42.959> your<00:13:43.079> contract<00:13:43.440> if<00:13:43.740> you<00:13:43.860> just 00:13:43.970 --> 00:13:43.980 align:start position:0% and verify your contract if you just 00:13:43.980 --> 00:13:47.569 align:start position:0% and verify your contract if you just publish<00:13:44.279> it<00:13:44.399> and<00:13:44.760> pin<00:13:44.940> it<00:13:45.620> on<00:13:46.620> ipfs<00:13:47.160> we'll<00:13:47.339> just 00:13:47.569 --> 00:13:47.579 align:start position:0% publish it and pin it on ipfs we'll just 00:13:47.579 --> 00:13:49.069 align:start position:0% publish it and pin it on ipfs we'll just do<00:13:47.700> it<00:13:47.820> for<00:13:47.940> you 00:13:49.069 --> 00:13:49.079 align:start position:0% do it for you 00:13:49.079 --> 00:13:51.530 align:start position:0% do it for you yeah 00:13:51.530 --> 00:13:51.540 align:start position:0% 00:13:51.540 --> 00:13:54.530 align:start position:0% um<00:13:51.660> so<00:13:52.200> we<00:13:52.380> have<00:13:52.800> this<00:13:53.160> contract<00:13:53.459> repo<00:13:53.940> of<00:13:54.360> all 00:13:54.530 --> 00:13:54.540 align:start position:0% um so we have this contract repo of all 00:13:54.540 --> 00:13:56.769 align:start position:0% um so we have this contract repo of all verified<00:13:54.839> contracts<00:13:55.500> it<00:13:56.100> is<00:13:56.279> served<00:13:56.639> over 00:13:56.769 --> 00:13:56.779 align:start position:0% verified contracts it is served over 00:13:56.779 --> 00:14:01.430 align:start position:0% verified contracts it is served over HTTP<00:13:57.779> and<00:13:58.019> ipfs<00:13:58.560> under<00:13:59.060> report.sourceify<00:14:00.060> Dev 00:14:01.430 --> 00:14:01.440 align:start position:0% HTTP and ipfs under report.sourceify Dev 00:14:01.440 --> 00:14:04.430 align:start position:0% HTTP and ipfs under report.sourceify Dev um so<00:14:01.920> we<00:14:02.279> pin<00:14:02.700> the<00:14:03.360> verified<00:14:03.839> Source 00:14:04.430 --> 00:14:04.440 align:start position:0% um so we pin the verified Source 00:14:04.440 --> 00:14:06.110 align:start position:0% um so we pin the verified Source verified<00:14:05.040> contract<00:14:05.399> source<00:14:05.700> file<00:14:05.820> and<00:14:06.060> the 00:14:06.110 --> 00:14:06.120 align:start position:0% verified contract source file and the 00:14:06.120 --> 00:14:08.629 align:start position:0% verified contract source file and the metadata<00:14:06.720> so<00:14:07.620> that<00:14:07.740> they<00:14:07.920> will<00:14:08.040> be<00:14:08.220> accessible 00:14:08.629 --> 00:14:08.639 align:start position:0% metadata so that they will be accessible 00:14:08.639 --> 00:14:11.030 align:start position:0% metadata so that they will be accessible by<00:14:09.420> decoding<00:14:09.839> the<00:14:09.959> bytecode<00:14:10.440> so<00:14:10.680> here 00:14:11.030 --> 00:14:11.040 align:start position:0% by decoding the bytecode so here 00:14:11.040 --> 00:14:13.970 align:start position:0% by decoding the bytecode so here remember<00:14:11.279> there<00:14:11.940> is<00:14:12.060> the<00:14:12.120> ipfs<00:14:12.540> high<00:14:12.779> here<00:14:13.139> and 00:14:13.970 --> 00:14:13.980 align:start position:0% remember there is the ipfs high here and 00:14:13.980 --> 00:14:16.069 align:start position:0% remember there is the ipfs high here and anyone<00:14:14.339> if<00:14:14.639> it's<00:14:14.940> verified<00:14:15.180> on<00:14:15.420> source5<00:14:15.839> we 00:14:16.069 --> 00:14:16.079 align:start position:0% anyone if it's verified on source5 we 00:14:16.079 --> 00:14:18.350 align:start position:0% anyone if it's verified on source5 we will<00:14:16.260> be<00:14:16.380> pinning<00:14:16.560> it<00:14:16.800> and<00:14:17.339> there<00:14:17.700> are<00:14:17.880> other 00:14:18.350 --> 00:14:18.360 align:start position:0% will be pinning it and there are other 00:14:18.360 --> 00:14:21.769 align:start position:0% will be pinning it and there are other people<00:14:18.980> uh<00:14:19.980> pinning<00:14:20.279> our<00:14:20.579> repo<00:14:21.000> as<00:14:21.120> well<00:14:21.300> so 00:14:21.769 --> 00:14:21.779 align:start position:0% people uh pinning our repo as well so 00:14:21.779 --> 00:14:23.210 align:start position:0% people uh pinning our repo as well so you<00:14:21.899> they<00:14:22.200> will<00:14:22.380> be<00:14:22.500> accessible<00:14:22.860> by<00:14:23.040> their 00:14:23.210 --> 00:14:23.220 align:start position:0% you they will be accessible by their 00:14:23.220 --> 00:14:26.210 align:start position:0% you they will be accessible by their ipfs<00:14:23.760> hash<00:14:24.000> and<00:14:24.779> yeah<00:14:24.959> we<00:14:25.320> also<00:14:25.560> served<00:14:25.800> repo 00:14:26.210 --> 00:14:26.220 align:start position:0% ipfs hash and yeah we also served repo 00:14:26.220 --> 00:14:30.430 align:start position:0% ipfs hash and yeah we also served repo under<00:14:26.459> an<00:14:26.700> ipns<00:14:27.180> name 00:14:30.430 --> 00:14:30.440 align:start position:0% 00:14:30.440 --> 00:14:32.990 align:start position:0% so<00:14:31.440> you<00:14:31.620> can<00:14:31.680> also<00:14:31.920> see<00:14:32.040> the<00:14:32.279> contract<00:14:32.519> repo 00:14:32.990 --> 00:14:33.000 align:start position:0% so you can also see the contract repo 00:14:33.000 --> 00:14:35.150 align:start position:0% so you can also see the contract repo and<00:14:33.480> see<00:14:33.839> the<00:14:34.079> files<00:14:34.380> access<00:14:34.560> all<00:14:34.920> of<00:14:35.040> them 00:14:35.150 --> 00:14:35.160 align:start position:0% and see the files access all of them 00:14:35.160 --> 00:14:38.090 align:start position:0% and see the files access all of them download<00:14:35.579> the<00:14:35.940> whole<00:14:36.180> repo<00:14:36.839> if<00:14:37.019> you<00:14:37.139> want<00:14:37.260> so 00:14:38.090 --> 00:14:38.100 align:start position:0% download the whole repo if you want so 00:14:38.100 --> 00:14:39.710 align:start position:0% download the whole repo if you want so yeah 00:14:39.710 --> 00:14:39.720 align:start position:0% yeah 00:14:39.720 --> 00:14:42.590 align:start position:0% yeah uh<00:14:40.440> okay<00:14:40.680> so<00:14:41.220> we<00:14:41.399> have<00:14:41.579> seen<00:14:41.760> what<00:14:42.240> you<00:14:42.300> can<00:14:42.480> do 00:14:42.590 --> 00:14:42.600 align:start position:0% uh okay so we have seen what you can do 00:14:42.600 --> 00:14:45.230 align:start position:0% uh okay so we have seen what you can do as<00:14:42.779> a<00:14:42.899> smart<00:14:43.019> contract<00:14:43.440> Dev<00:14:43.940> let's<00:14:44.940> see<00:14:45.120> what 00:14:45.230 --> 00:14:45.240 align:start position:0% as a smart contract Dev let's see what 00:14:45.240 --> 00:14:47.810 align:start position:0% as a smart contract Dev let's see what you<00:14:45.360> can<00:14:45.480> do<00:14:45.600> as<00:14:45.779> a<00:14:45.959> wallet<00:14:46.260> developer 00:14:47.810 --> 00:14:47.820 align:start position:0% you can do as a wallet developer 00:14:47.820 --> 00:14:51.350 align:start position:0% you can do as a wallet developer so<00:14:48.420> maybe<00:14:48.839> a<00:14:49.079> short<00:14:49.260> recap<00:14:50.060> what<00:14:51.060> we<00:14:51.180> are 00:14:51.350 --> 00:14:51.360 align:start position:0% so maybe a short recap what we are 00:14:51.360 --> 00:14:54.170 align:start position:0% so maybe a short recap what we are trying<00:14:51.540> to<00:14:51.660> do<00:14:51.779> again<00:14:52.079> so<00:14:52.980> we<00:14:53.519> have<00:14:53.760> a<00:14:53.880> contract 00:14:54.170 --> 00:14:54.180 align:start position:0% trying to do again so we have a contract 00:14:54.180 --> 00:14:56.870 align:start position:0% trying to do again so we have a contract call<00:14:54.360> we<00:14:54.899> are<00:14:55.079> talking<00:14:55.199> to<00:14:55.440> a<00:14:55.560> contract<00:14:55.920> and 00:14:56.870 --> 00:14:56.880 align:start position:0% call we are talking to a contract and 00:14:56.880 --> 00:14:59.810 align:start position:0% call we are talking to a contract and instead<00:14:57.240> of<00:14:57.300> showing<00:14:57.839> instead<00:14:58.380> of<00:14:58.500> this<00:14:58.820> byte 00:14:59.810 --> 00:14:59.820 align:start position:0% instead of showing instead of this byte 00:14:59.820 --> 00:15:01.670 align:start position:0% instead of showing instead of this byte string<00:15:00.060> we<00:15:00.300> want<00:15:00.480> to<00:15:00.600> show<00:15:00.779> something<00:15:01.380> more 00:15:01.670 --> 00:15:01.680 align:start position:0% string we want to show something more 00:15:01.680 --> 00:15:04.370 align:start position:0% string we want to show something more user<00:15:02.100> friendly<00:15:02.399> so<00:15:02.579> one<00:15:02.940> thing<00:15:03.660> to<00:15:03.839> do<00:15:04.019> is 00:15:04.370 --> 00:15:04.380 align:start position:0% user friendly so one thing to do is 00:15:04.380 --> 00:15:07.610 align:start position:0% user friendly so one thing to do is obviously<00:15:05.040> to<00:15:05.399> decode<00:15:05.940> this<00:15:06.839> call<00:15:07.019> the 00:15:07.610 --> 00:15:07.620 align:start position:0% obviously to decode this call the 00:15:07.620 --> 00:15:11.810 align:start position:0% obviously to decode this call the despite<00:15:07.980> string<00:15:08.399> call<00:15:08.779> via<00:15:09.779> the<00:15:09.959> API<00:15:10.320> Json<00:15:10.820> you 00:15:11.810 --> 00:15:11.820 align:start position:0% despite string call via the API Json you 00:15:11.820 --> 00:15:13.490 align:start position:0% despite string call via the API Json you can<00:15:11.880> show<00:15:12.060> the<00:15:12.240> function<00:15:12.540> name<00:15:12.720> the<00:15:13.139> variable 00:15:13.490 --> 00:15:13.500 align:start position:0% can show the function name the variable 00:15:13.500 --> 00:15:16.490 align:start position:0% can show the function name the variable names<00:15:13.920> Etc<00:15:14.100> and<00:15:14.760> then<00:15:14.880> you<00:15:15.240> want<00:15:15.420> to<00:15:15.540> show<00:15:15.779> some 00:15:16.490 --> 00:15:16.500 align:start position:0% names Etc and then you want to show some 00:15:16.500 --> 00:15:18.410 align:start position:0% names Etc and then you want to show some human<00:15:16.680> readable<00:15:17.100> description<00:15:17.519> of<00:15:18.000> what<00:15:18.300> the 00:15:18.410 --> 00:15:18.420 align:start position:0% human readable description of what the 00:15:18.420 --> 00:15:19.790 align:start position:0% human readable description of what the user<00:15:18.720> is<00:15:18.779> trying<00:15:18.959> to<00:15:19.139> do<00:15:19.260> if<00:15:19.560> you<00:15:19.680> have 00:15:19.790 --> 00:15:19.800 align:start position:0% user is trying to do if you have 00:15:19.800 --> 00:15:22.430 align:start position:0% user is trying to do if you have documented<00:15:20.399> your<00:15:20.519> code<00:15:20.760> well 00:15:22.430 --> 00:15:22.440 align:start position:0% documented your code well 00:15:22.440 --> 00:15:23.090 align:start position:0% documented your code well um 00:15:23.090 --> 00:15:23.100 align:start position:0% um 00:15:23.100 --> 00:15:25.009 align:start position:0% um so<00:15:23.760> what<00:15:23.880> you<00:15:24.000> what<00:15:24.240> you<00:15:24.360> can<00:15:24.480> do<00:15:24.600> as<00:15:24.720> a<00:15:24.839> vault 00:15:25.009 --> 00:15:25.019 align:start position:0% so what you what you can do as a vault 00:15:25.019 --> 00:15:27.410 align:start position:0% so what you what you can do as a vault developer<00:15:25.500> you<00:15:26.100> go<00:15:26.339> to<00:15:26.399> sourcify<00:15:27.000> your 00:15:27.410 --> 00:15:27.420 align:start position:0% developer you go to sourcify your 00:15:27.420 --> 00:15:30.050 align:start position:0% developer you go to sourcify your report.sourcify<00:15:28.320> Dev<00:15:28.500> you<00:15:29.220> get<00:15:29.339> a<00:15:29.519> chain<00:15:29.820> ID 00:15:30.050 --> 00:15:30.060 align:start position:0% report.sourcify Dev you get a chain ID 00:15:30.060 --> 00:15:33.110 align:start position:0% report.sourcify Dev you get a chain ID the<00:15:30.480> code<00:15:31.019> track<00:15:31.320> and<00:15:31.740> the<00:15:31.860> metadata 00:15:33.110 --> 00:15:33.120 align:start position:0% the code track and the metadata 00:15:33.120 --> 00:15:35.509 align:start position:0% the code track and the metadata no<00:15:33.720> please<00:15:34.199> don't<00:15:34.380> do<00:15:34.560> that<00:15:34.740> you<00:15:35.220> don't<00:15:35.339> come 00:15:35.509 --> 00:15:35.519 align:start position:0% no please don't do that you don't come 00:15:35.519 --> 00:15:37.009 align:start position:0% no please don't do that you don't come to<00:15:35.699> us<00:15:35.880> because 00:15:37.009 --> 00:15:37.019 align:start position:0% to us because 00:15:37.019 --> 00:15:40.670 align:start position:0% to us because it's<00:15:37.380> already<00:15:37.500> in<00:15:37.740> ipfs<00:15:39.060> and<00:15:39.540> it<00:15:39.720> is<00:15:39.899> the<00:15:40.440> neat 00:15:40.670 --> 00:15:40.680 align:start position:0% it's already in ipfs and it is the neat 00:15:40.680 --> 00:15:42.530 align:start position:0% it's already in ipfs and it is the neat thing<00:15:40.800> is<00:15:40.860> it<00:15:41.040> is<00:15:41.220> content<00:15:41.519> content<00:15:42.300> address 00:15:42.530 --> 00:15:42.540 align:start position:0% thing is it is content content address 00:15:42.540 --> 00:15:44.930 align:start position:0% thing is it is content content address so<00:15:43.079> you<00:15:43.320> know<00:15:43.500> the<00:15:44.100> file<00:15:44.279> you're<00:15:44.459> getting<00:15:44.699> is 00:15:44.930 --> 00:15:44.940 align:start position:0% so you know the file you're getting is 00:15:44.940 --> 00:15:47.810 align:start position:0% so you know the file you're getting is actually<00:15:45.180> the<00:15:45.420> right<00:15:45.540> file<00:15:45.899> so<00:15:46.440> you<00:15:47.100> just<00:15:47.279> your 00:15:47.810 --> 00:15:47.820 align:start position:0% actually the right file so you just your 00:15:47.820 --> 00:15:49.910 align:start position:0% actually the right file so you just your wallet<00:15:48.240> just<00:15:48.720> gets<00:15:49.139> the<00:15:49.199> byte<00:15:49.500> code<00:15:49.620> of<00:15:49.800> the 00:15:49.910 --> 00:15:49.920 align:start position:0% wallet just gets the byte code of the 00:15:49.920 --> 00:15:54.530 align:start position:0% wallet just gets the byte code of the contract<00:15:50.480> decodes<00:15:51.480> the<00:15:52.380> ipfs<00:15:53.160> hash<00:15:53.880> here<00:15:54.240> at 00:15:54.530 --> 00:15:54.540 align:start position:0% contract decodes the ipfs hash here at 00:15:54.540 --> 00:15:56.569 align:start position:0% contract decodes the ipfs hash here at the<00:15:54.660> end<00:15:54.720> of<00:15:54.839> the<00:15:54.959> bytecode 00:15:56.569 --> 00:15:56.579 align:start position:0% the end of the bytecode 00:15:56.579 --> 00:16:00.050 align:start position:0% the end of the bytecode fetched<00:15:57.300> metadata<00:15:58.339> that<00:15:59.339> we<00:15:59.459> pinned<00:15:59.760> it<00:15:59.880> for 00:16:00.050 --> 00:16:00.060 align:start position:0% fetched metadata that we pinned it for 00:16:00.060 --> 00:16:03.829 align:start position:0% fetched metadata that we pinned it for you<00:16:00.320> and<00:16:01.320> the<00:16:01.440> metadata<00:16:01.980> file<00:16:02.220> has<00:16:02.699> as<00:16:03.420> we<00:16:03.660> have 00:16:03.829 --> 00:16:03.839 align:start position:0% you and the metadata file has as we have 00:16:03.839 --> 00:16:07.550 align:start position:0% you and the metadata file has as we have seen<00:16:04.139> the<00:16:04.440> API<00:16:04.860> and<00:16:05.339> the<00:16:05.579> documentation 00:16:07.550 --> 00:16:07.560 align:start position:0% seen the API and the documentation 00:16:07.560 --> 00:16:10.490 align:start position:0% seen the API and the documentation yeah<00:16:08.040> this<00:16:08.579> is<00:16:08.699> where<00:16:09.060> the<00:16:09.480> first<00:16:09.779> two<00:16:10.079> Fields 00:16:10.490 --> 00:16:10.500 align:start position:0% yeah this is where the first two Fields 00:16:10.500 --> 00:16:12.530 align:start position:0% yeah this is where the first two Fields come<00:16:10.680> in<00:16:10.800> handy<00:16:11.100> how<00:16:11.579> to<00:16:11.699> interface<00:16:12.120> with<00:16:12.360> the 00:16:12.530 --> 00:16:12.540 align:start position:0% come in handy how to interface with the 00:16:12.540 --> 00:16:13.730 align:start position:0% come in handy how to interface with the contract 00:16:13.730 --> 00:16:13.740 align:start position:0% contract 00:16:13.740 --> 00:16:16.610 align:start position:0% contract and<00:16:14.279> then<00:16:14.459> decode<00:16:15.060> the<00:16:15.240> API<00:16:15.600> and<00:16:15.959> populate<00:16:16.380> the 00:16:16.610 --> 00:16:16.620 align:start position:0% and then decode the API and populate the 00:16:16.620 --> 00:16:18.829 align:start position:0% and then decode the API and populate the not<00:16:16.740> spec<00:16:16.980> comments<00:16:17.459> of<00:16:17.699> the<00:16:17.820> track 00:16:18.829 --> 00:16:18.839 align:start position:0% not spec comments of the track 00:16:18.839 --> 00:16:20.689 align:start position:0% not spec comments of the track so<00:16:19.320> hopefully<00:16:19.680> at<00:16:19.800> the<00:16:19.920> end<00:16:20.040> of<00:16:20.160> today<00:16:20.279> we<00:16:20.579> will 00:16:20.689 --> 00:16:20.699 align:start position:0% so hopefully at the end of today we will 00:16:20.699 --> 00:16:23.090 align:start position:0% so hopefully at the end of today we will have<00:16:20.880> something<00:16:21.180> more<00:16:22.139> on<00:16:22.380> the<00:16:22.500> right<00:16:22.620> rather 00:16:23.090 --> 00:16:23.100 align:start position:0% have something more on the right rather 00:16:23.100 --> 00:16:24.829 align:start position:0% have something more on the right rather than<00:16:23.220> something<00:16:23.459> on<00:16:23.699> the<00:16:23.820> left 00:16:24.829 --> 00:16:24.839 align:start position:0% than something on the left 00:16:24.839 --> 00:16:27.230 align:start position:0% than something on the left but<00:16:25.380> source<00:16:25.800> file<00:16:26.040> is<00:16:26.160> actually<00:16:26.339> not<00:16:26.940> the<00:16:27.120> only 00:16:27.230 --> 00:16:27.240 align:start position:0% but source file is actually not the only 00:16:27.240 --> 00:16:30.710 align:start position:0% but source file is actually not the only way<00:16:27.480> for<00:16:28.380> human<00:16:28.620> friendliness<00:16:29.480> the<00:16:30.480> idea 00:16:30.710 --> 00:16:30.720 align:start position:0% way for human friendliness the idea 00:16:30.720 --> 00:16:32.629 align:start position:0% way for human friendliness the idea behind<00:16:31.019> sourceify<00:16:31.560> is<00:16:31.800> to<00:16:31.980> have<00:16:32.279> human 00:16:32.629 --> 00:16:32.639 align:start position:0% behind sourceify is to have human 00:16:32.639 --> 00:16:35.110 align:start position:0% behind sourceify is to have human readable<00:16:33.120> descriptions<00:16:33.720> via<00:16:34.500> nut<00:16:34.740> spec 00:16:35.110 --> 00:16:35.120 align:start position:0% readable descriptions via nut spec 00:16:35.120 --> 00:16:38.210 align:start position:0% readable descriptions via nut spec comments<00:16:36.120> found<00:16:36.240> in<00:16:36.420> the<00:16:36.480> metadata<00:16:37.440> there<00:16:38.100> are 00:16:38.210 --> 00:16:38.220 align:start position:0% comments found in the metadata there are 00:16:38.220 --> 00:16:39.949 align:start position:0% comments found in the metadata there are other<00:16:38.459> ways<00:16:38.759> to<00:16:38.880> achieve<00:16:39.300> this<00:16:39.420> as<00:16:39.600> well<00:16:39.720> so 00:16:39.949 --> 00:16:39.959 align:start position:0% other ways to achieve this as well so 00:16:39.959 --> 00:16:42.769 align:start position:0% other ways to achieve this as well so one<00:16:40.440> is<00:16:40.620> for<00:16:40.860> example<00:16:41.040> these<00:16:41.339> two<00:16:41.459> eips<00:16:41.779> by 00:16:42.769 --> 00:16:42.779 align:start position:0% one is for example these two eips by 00:16:42.779 --> 00:16:44.329 align:start position:0% one is for example these two eips by Richard<00:16:42.959> Moore<00:16:43.320> and<00:16:43.380> Nick<00:16:43.500> Johnson<00:16:43.680> so<00:16:44.160> the 00:16:44.329 --> 00:16:44.339 align:start position:0% Richard Moore and Nick Johnson so the 00:16:44.339 --> 00:16:47.090 align:start position:0% Richard Moore and Nick Johnson so the idea<00:16:44.579> there<00:16:44.820> is<00:16:45.240> to<00:16:45.540> have<00:16:45.779> an<00:16:46.500> extra<00:16:46.620> function 00:16:47.090 --> 00:16:47.100 align:start position:0% idea there is to have an extra function 00:16:47.100 --> 00:16:49.850 align:start position:0% idea there is to have an extra function name<00:16:47.339> an<00:16:48.060> extra<00:16:48.480> function<00:16:48.899> a<00:16:49.380> described 00:16:49.850 --> 00:16:49.860 align:start position:0% name an extra function a described 00:16:49.860 --> 00:16:52.310 align:start position:0% name an extra function a described function<00:16:50.100> so<00:16:50.279> to<00:16:50.459> say<00:16:50.639> that<00:16:51.420> will<00:16:51.600> return<00:16:51.959> the 00:16:52.310 --> 00:16:52.320 align:start position:0% function so to say that will return the 00:16:52.320 --> 00:16:55.670 align:start position:0% function so to say that will return the user<00:16:52.680> something<00:16:53.180> unreadable<00:16:54.180> so<00:16:55.139> it<00:16:55.259> can<00:16:55.560> be 00:16:55.670 --> 00:16:55.680 align:start position:0% user something unreadable so it can be 00:16:55.680 --> 00:16:58.670 align:start position:0% user something unreadable so it can be anything<00:16:55.920> any<00:16:56.519> custom<00:16:56.940> any<00:16:57.839> custom<00:16:58.079> string 00:16:58.670 --> 00:16:58.680 align:start position:0% anything any custom any custom string 00:16:58.680 --> 00:17:02.150 align:start position:0% anything any custom any custom string and<00:16:59.639> uh<00:17:00.360> the<00:17:01.199> contract<00:17:01.500> will<00:17:01.680> return<00:17:01.920> the 00:17:02.150 --> 00:17:02.160 align:start position:0% and uh the contract will return the 00:17:02.160 --> 00:17:03.650 align:start position:0% and uh the contract will return the string<00:17:02.459> to<00:17:02.579> the<00:17:02.699> user<00:17:03.060> and<00:17:03.480> continue 00:17:03.650 --> 00:17:03.660 align:start position:0% string to the user and continue 00:17:03.660 --> 00:17:05.990 align:start position:0% string to the user and continue executing<00:17:04.319> the<00:17:04.559> executing<00:17:05.400> the<00:17:05.579> actual 00:17:05.990 --> 00:17:06.000 align:start position:0% executing the executing the actual 00:17:06.000 --> 00:17:07.069 align:start position:0% executing the executing the actual function 00:17:07.069 --> 00:17:07.079 align:start position:0% function 00:17:07.079 --> 00:17:09.650 align:start position:0% function and<00:17:07.860> here<00:17:08.339> the<00:17:08.579> nice<00:17:08.699> thing<00:17:08.880> is<00:17:09.000> it<00:17:09.179> can<00:17:09.299> decode 00:17:09.650 --> 00:17:09.660 align:start position:0% and here the nice thing is it can decode 00:17:09.660 --> 00:17:12.010 align:start position:0% and here the nice thing is it can decode things<00:17:09.959> like<00:17:10.140> ens<00:17:10.620> commit<00:17:10.980> that<00:17:11.339> is<00:17:11.520> normally 00:17:12.010 --> 00:17:12.020 align:start position:0% things like ens commit that is normally 00:17:12.020 --> 00:17:15.110 align:start position:0% things like ens commit that is normally uh<00:17:13.020> like<00:17:13.260> it's<00:17:13.740> it's<00:17:13.980> a<00:17:14.220> hash<00:17:14.400> commit<00:17:14.699> and<00:17:14.939> it 00:17:15.110 --> 00:17:15.120 align:start position:0% uh like it's it's a hash commit and it 00:17:15.120 --> 00:17:16.429 align:start position:0% uh like it's it's a hash commit and it doesn't<00:17:15.240> have<00:17:15.419> a<00:17:15.540> meaning<00:17:15.660> to<00:17:15.900> the<00:17:16.079> user<00:17:16.319> but 00:17:16.429 --> 00:17:16.439 align:start position:0% doesn't have a meaning to the user but 00:17:16.439 --> 00:17:19.010 align:start position:0% doesn't have a meaning to the user but you<00:17:16.620> can<00:17:16.740> add<00:17:16.919> actually<00:17:17.280> some<00:17:18.179> more<00:17:18.419> custom 00:17:19.010 --> 00:17:19.020 align:start position:0% you can add actually some more custom 00:17:19.020 --> 00:17:21.710 align:start position:0% you can add actually some more custom strings<00:17:19.620> custom<00:17:20.100> messages<00:17:20.400> to<00:17:20.760> the<00:17:20.880> user 00:17:21.710 --> 00:17:21.720 align:start position:0% strings custom messages to the user 00:17:21.720 --> 00:17:24.049 align:start position:0% strings custom messages to the user that<00:17:22.319> they<00:17:22.559> can<00:17:22.679> make<00:17:22.860> sense<00:17:22.980> of<00:17:23.160> it<00:17:23.339> but 00:17:24.049 --> 00:17:24.059 align:start position:0% that they can make sense of it but 00:17:24.059 --> 00:17:26.809 align:start position:0% that they can make sense of it but hopefully<00:17:24.540> this<00:17:24.780> discuss<00:17:25.260> extra<00:17:25.500> gas<00:17:25.860> uh<00:17:26.579> the 00:17:26.809 --> 00:17:26.819 align:start position:0% hopefully this discuss extra gas uh the 00:17:26.819 --> 00:17:29.450 align:start position:0% hopefully this discuss extra gas uh the other<00:17:26.880> one<00:17:27.120> is<00:17:27.419> the<00:17:27.660> other<00:17:27.900> MP<00:17:28.740> proposal<00:17:29.220> by 00:17:29.450 --> 00:17:29.460 align:start position:0% other one is the other MP proposal by 00:17:29.460 --> 00:17:33.350 align:start position:0% other one is the other MP proposal by Dan<00:17:29.700> Finley<00:17:30.120> the<00:17:30.840> there<00:17:31.080> the<00:17:31.380> idea<00:17:31.620> is<00:17:32.040> uh<00:17:32.940> to 00:17:33.350 --> 00:17:33.360 align:start position:0% Dan Finley the there the idea is uh to 00:17:33.360 --> 00:17:35.510 align:start position:0% Dan Finley the there the idea is uh to give<00:17:33.660> the<00:17:33.900> user<00:17:34.140> this<00:17:34.320> information<00:17:34.559> at<00:17:35.400> the 00:17:35.510 --> 00:17:35.520 align:start position:0% give the user this information at the 00:17:35.520 --> 00:17:38.330 align:start position:0% give the user this information at the first<00:17:35.640> point<00:17:35.820> of<00:17:36.000> contact<00:17:36.260> so<00:17:37.260> say<00:17:37.679> you<00:17:38.100> want 00:17:38.330 --> 00:17:38.340 align:start position:0% first point of contact so say you want 00:17:38.340 --> 00:17:40.850 align:start position:0% first point of contact so say you want to<00:17:38.520> do<00:17:39.419> an<00:17:39.600> exchange<00:17:39.900> for<00:17:40.200> the<00:17:40.380> first<00:17:40.500> time<00:17:40.620> in 00:17:40.850 --> 00:17:40.860 align:start position:0% to do an exchange for the first time in 00:17:40.860 --> 00:17:44.930 align:start position:0% to do an exchange for the first time in at<00:17:41.039> uniswap<00:17:41.720> uniswap<00:17:43.220> app.uniswap<00:17:44.220> will<00:17:44.700> give 00:17:44.930 --> 00:17:44.940 align:start position:0% at uniswap uniswap app.uniswap will give 00:17:44.940 --> 00:17:47.450 align:start position:0% at uniswap uniswap app.uniswap will give you<00:17:45.059> the<00:17:45.240> contract<00:17:45.539> metadata<00:17:46.220> your<00:17:47.220> Vault 00:17:47.450 --> 00:17:47.460 align:start position:0% you the contract metadata your Vault 00:17:47.460 --> 00:17:50.690 align:start position:0% you the contract metadata your Vault will<00:17:47.640> store<00:17:47.880> it<00:17:48.059> and<00:17:48.900> then<00:17:49.140> you<00:17:50.100> your<00:17:50.400> wallet 00:17:50.690 --> 00:17:50.700 align:start position:0% will store it and then you your wallet 00:17:50.700 --> 00:17:52.789 align:start position:0% will store it and then you your wallet will<00:17:50.940> have<00:17:51.059> the<00:17:51.179> API<00:17:51.480> and<00:17:51.720> the<00:17:51.840> describers<00:17:52.380> so 00:17:52.789 --> 00:17:52.799 align:start position:0% will have the API and the describers so 00:17:52.799 --> 00:17:55.370 align:start position:0% will have the API and the describers so that<00:17:53.100> it<00:17:53.820> can<00:17:54.000> show<00:17:54.299> you<00:17:54.480> some<00:17:54.660> something<00:17:55.080> more 00:17:55.370 --> 00:17:55.380 align:start position:0% that it can show you some something more 00:17:55.380 --> 00:17:58.970 align:start position:0% that it can show you some something more human<00:17:55.620> readable<00:17:56.539> uh<00:17:57.539> the<00:17:58.200> advantage<00:17:58.620> here<00:17:58.799> is 00:17:58.970 --> 00:17:58.980 align:start position:0% human readable uh the advantage here is 00:17:58.980 --> 00:18:01.490 align:start position:0% human readable uh the advantage here is it's<00:17:59.160> backwards<00:17:59.700> compatible<00:18:00.120> so<00:18:00.900> we<00:18:01.380> don't 00:18:01.490 --> 00:18:01.500 align:start position:0% it's backwards compatible so we don't 00:18:01.500 --> 00:18:02.990 align:start position:0% it's backwards compatible so we don't need<00:18:01.679> to<00:18:01.799> change<00:18:01.980> change<00:18:02.340> the<00:18:02.580> contracts 00:18:02.990 --> 00:18:03.000 align:start position:0% need to change change the contracts 00:18:03.000 --> 00:18:04.909 align:start position:0% need to change change the contracts right<00:18:03.600> now<00:18:03.780> most<00:18:04.020> of<00:18:04.200> the<00:18:04.260> contracts<00:18:04.679> don't 00:18:04.909 --> 00:18:04.919 align:start position:0% right now most of the contracts don't 00:18:04.919 --> 00:18:07.669 align:start position:0% right now most of the contracts don't have<00:18:05.220> any<00:18:05.940> documentation<00:18:06.600> or<00:18:06.840> anything<00:18:07.020> and 00:18:07.669 --> 00:18:07.679 align:start position:0% have any documentation or anything and 00:18:07.679 --> 00:18:10.610 align:start position:0% have any documentation or anything and or<00:18:07.919> they<00:18:08.220> are<00:18:08.400> not<00:18:08.520> actually<00:18:09.120> documented<00:18:09.780> with 00:18:10.610 --> 00:18:10.620 align:start position:0% or they are not actually documented with 00:18:10.620 --> 00:18:13.970 align:start position:0% or they are not actually documented with the<00:18:11.120> human<00:18:12.120> friendliness<00:18:12.780> in<00:18:13.020> mind<00:18:13.200> so<00:18:13.860> this 00:18:13.970 --> 00:18:13.980 align:start position:0% the human friendliness in mind so this 00:18:13.980 --> 00:18:15.770 align:start position:0% the human friendliness in mind so this will<00:18:14.160> be<00:18:14.340> backwards<00:18:14.820> compatible<00:18:15.179> but<00:18:15.419> at<00:18:15.660> the 00:18:15.770 --> 00:18:15.780 align:start position:0% will be backwards compatible but at the 00:18:15.780 --> 00:18:17.390 align:start position:0% will be backwards compatible but at the same<00:18:15.900> time<00:18:16.020> this<00:18:16.320> means<00:18:16.559> it's<00:18:16.679> mutable<00:18:17.100> so 00:18:17.390 --> 00:18:17.400 align:start position:0% same time this means it's mutable so 00:18:17.400 --> 00:18:21.230 align:start position:0% same time this means it's mutable so it's<00:18:17.580> like<00:18:17.820> it<00:18:18.660> can<00:18:18.840> be<00:18:18.960> changed<00:18:19.880> so<00:18:20.880> it's<00:18:21.059> a 00:18:21.230 --> 00:18:21.240 align:start position:0% it's like it can be changed so it's a 00:18:21.240 --> 00:18:23.150 align:start position:0% it's like it can be changed so it's a trade-off<00:18:21.539> but<00:18:21.780> yeah 00:18:23.150 --> 00:18:23.160 align:start position:0% trade-off but yeah 00:18:23.160 --> 00:18:25.370 align:start position:0% trade-off but yeah and<00:18:23.640> also<00:18:23.880> there<00:18:24.299> are<00:18:24.480> many<00:18:24.780> ways<00:18:25.020> to<00:18:25.140> better 00:18:25.370 --> 00:18:25.380 align:start position:0% and also there are many ways to better 00:18:25.380 --> 00:18:27.470 align:start position:0% and also there are many ways to better ux<00:18:25.799> so<00:18:26.100> we<00:18:26.280> can<00:18:26.460> actually<00:18:26.700> show<00:18:27.000> the<00:18:27.179> users 00:18:27.470 --> 00:18:27.480 align:start position:0% ux so we can actually show the users 00:18:27.480 --> 00:18:30.529 align:start position:0% ux so we can actually show the users many<00:18:27.720> things<00:18:27.900> so<00:18:28.200> is<00:18:28.559> it<00:18:28.880> you<00:18:29.880> can<00:18:29.940> decode<00:18:30.360> the 00:18:30.529 --> 00:18:30.539 align:start position:0% many things so is it you can decode the 00:18:30.539 --> 00:18:33.230 align:start position:0% many things so is it you can decode the contract<00:18:30.960> call<00:18:31.620> you<00:18:32.039> can<00:18:32.160> warn<00:18:32.640> if<00:18:32.820> the<00:18:33.000> user 00:18:33.230 --> 00:18:33.240 align:start position:0% contract call you can warn if the user 00:18:33.240 --> 00:18:35.590 align:start position:0% contract call you can warn if the user has<00:18:33.419> never<00:18:33.600> been<00:18:33.900> talked<00:18:34.679> to<00:18:34.740> this<00:18:35.039> contract 00:18:35.590 --> 00:18:35.600 align:start position:0% has never been talked to this contract 00:18:35.600 --> 00:18:38.090 align:start position:0% has never been talked to this contract uh<00:18:36.600> show<00:18:36.960> the<00:18:37.200> user<00:18:37.380> if<00:18:37.500> the<00:18:37.679> contract<00:18:37.919> is 00:18:38.090 --> 00:18:38.100 align:start position:0% uh show the user if the contract is 00:18:38.100 --> 00:18:41.470 align:start position:0% uh show the user if the contract is verified<00:18:38.539> uh<00:18:39.539> block<00:18:39.780> if<00:18:40.020> it's<00:18:40.200> a<00:18:40.320> scam<00:18:40.620> address 00:18:41.470 --> 00:18:41.480 align:start position:0% verified uh block if it's a scam address 00:18:41.480 --> 00:18:44.990 align:start position:0% verified uh block if it's a scam address many<00:18:42.480> things<00:18:42.720> as<00:18:43.020> well<00:18:43.200> as<00:18:43.580> other<00:18:44.580> types<00:18:44.880> of 00:18:44.990 --> 00:18:45.000 align:start position:0% many things as well as other types of 00:18:45.000 --> 00:18:46.909 align:start position:0% many things as well as other types of things<00:18:45.179> such<00:18:45.660> as<00:18:45.900> how<00:18:46.440> many<00:18:46.559> times<00:18:46.740> this 00:18:46.909 --> 00:18:46.919 align:start position:0% things such as how many times this 00:18:46.919 --> 00:18:48.770 align:start position:0% things such as how many times this contract<00:18:47.220> was<00:18:47.400> interacted<00:18:47.880> with<00:18:48.000> when<00:18:48.480> was<00:18:48.660> it 00:18:48.770 --> 00:18:48.780 align:start position:0% contract was interacted with when was it 00:18:48.780 --> 00:18:51.890 align:start position:0% contract was interacted with when was it deployed<00:18:49.380> because<00:18:49.980> a<00:18:50.460> scam<00:18:50.880> the<00:18:51.419> contract 00:18:51.890 --> 00:18:51.900 align:start position:0% deployed because a scam the contract 00:18:51.900 --> 00:18:54.049 align:start position:0% deployed because a scam the contract would<00:18:52.140> be<00:18:52.260> like<00:18:52.500> likely<00:18:53.039> more<00:18:53.280> recent<00:18:53.820> and 00:18:54.049 --> 00:18:54.059 align:start position:0% would be like likely more recent and 00:18:54.059 --> 00:18:56.090 align:start position:0% would be like likely more recent and less<00:18:54.240> interacted<00:18:54.780> with 00:18:56.090 --> 00:18:56.100 align:start position:0% less interacted with 00:18:56.100 --> 00:18:58.430 align:start position:0% less interacted with um<00:18:56.160> is<00:18:56.460> this<00:18:56.580> contract<00:18:56.940> audited<00:18:57.720> and<00:18:57.960> is<00:18:58.140> it<00:18:58.320> by 00:18:58.430 --> 00:18:58.440 align:start position:0% um is this contract audited and is it by 00:18:58.440 --> 00:19:00.710 align:start position:0% um is this contract audited and is it by audit<00:18:58.919> by<00:18:59.160> whom<00:18:59.400> so<00:19:00.000> there<00:19:00.299> are<00:19:00.419> actually<00:19:00.480> many 00:19:00.710 --> 00:19:00.720 align:start position:0% audit by whom so there are actually many 00:19:00.720 --> 00:19:02.690 align:start position:0% audit by whom so there are actually many ways<00:19:01.020> we<00:19:01.200> can<00:19:01.320> do<00:19:01.440> better 00:19:02.690 --> 00:19:02.700 align:start position:0% ways we can do better 00:19:02.700 --> 00:19:04.630 align:start position:0% ways we can do better so<00:19:03.120> as<00:19:03.240> I<00:19:03.419> recap<00:19:03.660> what<00:19:03.840> is<00:19:04.020> sourceify 00:19:04.630 --> 00:19:04.640 align:start position:0% so as I recap what is sourceify 00:19:04.640 --> 00:19:06.950 align:start position:0% so as I recap what is sourceify technically<00:19:05.640> it<00:19:06.120> is<00:19:06.240> an<00:19:06.419> open<00:19:06.539> source 00:19:06.950 --> 00:19:06.960 align:start position:0% technically it is an open source 00:19:06.960 --> 00:19:08.510 align:start position:0% technically it is an open source automatic<00:19:07.440> smart<00:19:07.620> contract<00:19:07.980> verification 00:19:08.510 --> 00:19:08.520 align:start position:0% automatic smart contract verification 00:19:08.520 --> 00:19:11.150 align:start position:0% automatic smart contract verification service<00:19:08.820> our<00:19:09.480> monitor<00:19:10.140> it's<00:19:10.740> a<00:19:10.919> user 00:19:11.150 --> 00:19:11.160 align:start position:0% service our monitor it's a user 00:19:11.160 --> 00:19:14.270 align:start position:0% service our monitor it's a user interface<00:19:11.640> server<00:19:12.440> API<00:19:13.440> and<00:19:13.679> tooling<00:19:14.039> to 00:19:14.270 --> 00:19:14.280 align:start position:0% interface server API and tooling to 00:19:14.280 --> 00:19:16.250 align:start position:0% interface server API and tooling to verify<00:19:14.640> contracts<00:19:15.000> manually 00:19:16.250 --> 00:19:16.260 align:start position:0% verify contracts manually 00:19:16.260 --> 00:19:18.230 align:start position:0% verify contracts manually it's<00:19:16.679> a<00:19:16.860> public<00:19:16.980> decentralized<00:19:17.700> content 00:19:18.230 --> 00:19:18.240 align:start position:0% it's a public decentralized content 00:19:18.240 --> 00:19:20.870 align:start position:0% it's a public decentralized content address<00:19:18.480> storage<00:19:19.080> of<00:19:19.980> verified<00:19:20.340> contracts 00:19:20.870 --> 00:19:20.880 align:start position:0% address storage of verified contracts 00:19:20.880 --> 00:19:23.870 align:start position:0% address storage of verified contracts our<00:19:21.120> repo<00:19:21.600> and<00:19:22.380> more<00:19:22.500> generally<00:19:22.860> we<00:19:23.460> are<00:19:23.640> a 00:19:23.870 --> 00:19:23.880 align:start position:0% our repo and more generally we are a 00:19:23.880 --> 00:19:26.210 align:start position:0% our repo and more generally we are a base<00:19:24.179> layer<00:19:24.660> and<00:19:25.320> a<00:19:25.440> public<00:19:25.620> good<00:19:25.860> for<00:19:26.100> other 00:19:26.210 --> 00:19:26.220 align:start position:0% base layer and a public good for other 00:19:26.220 --> 00:19:29.330 align:start position:0% base layer and a public good for other tools<00:19:26.640> to<00:19:26.760> build<00:19:26.940> on<00:19:27.600> top<00:19:27.660> of<00:19:27.840> us<00:19:28.039> and<00:19:29.039> we<00:19:29.160> are 00:19:29.330 --> 00:19:29.340 align:start position:0% tools to build on top of us and we are 00:19:29.340 --> 00:19:30.710 align:start position:0% tools to build on top of us and we are an<00:19:29.400> initiative<00:19:29.760> to<00:19:29.940> Foster<00:19:30.240> the<00:19:30.419> use<00:19:30.539> of 00:19:30.710 --> 00:19:30.720 align:start position:0% an initiative to Foster the use of 00:19:30.720 --> 00:19:33.590 align:start position:0% an initiative to Foster the use of solidity<00:19:31.020> metadata<00:19:31.700> nut<00:19:32.700> spec<00:19:33.000> and<00:19:33.480> full 00:19:33.590 --> 00:19:33.600 align:start position:0% solidity metadata nut spec and full 00:19:33.600 --> 00:19:35.750 align:start position:0% solidity metadata nut spec and full verification<00:19:34.080> and<00:19:34.860> as<00:19:34.980> well<00:19:35.100> as<00:19:35.220> we<00:19:35.460> are<00:19:35.580> an 00:19:35.750 --> 00:19:35.760 align:start position:0% verification and as well as we are an 00:19:35.760 --> 00:19:37.789 align:start position:0% verification and as well as we are an ongoing<00:19:36.120> effort<00:19:36.480> to<00:19:37.320> improve<00:19:37.620> smart 00:19:37.789 --> 00:19:37.799 align:start position:0% ongoing effort to improve smart 00:19:37.799 --> 00:19:41.150 align:start position:0% ongoing effort to improve smart contracts<00:19:38.220> UI<00:19:38.580> safety<00:19:39.000> and<00:19:39.179> transparency 00:19:41.150 --> 00:19:41.160 align:start position:0% contracts UI safety and transparency 00:19:41.160 --> 00:19:44.210 align:start position:0% contracts UI safety and transparency so<00:19:42.120> thank<00:19:42.480> you<00:19:42.600> for<00:19:42.720> listening<00:19:43.140> uh<00:19:43.980> if<00:19:44.160> you 00:19:44.210 --> 00:19:44.220 align:start position:0% so thank you for listening uh if you 00:19:44.220 --> 00:19:46.070 align:start position:0% so thank you for listening uh if you have<00:19:44.340> if<00:19:44.640> you're<00:19:44.760> interested<00:19:45.179> you<00:19:45.780> can<00:19:45.840> find 00:19:46.070 --> 00:19:46.080 align:start position:0% have if you're interested you can find 00:19:46.080 --> 00:19:49.549 align:start position:0% have if you're interested you can find us<00:19:46.320> in<00:19:46.679> Twitter<00:19:47.280> join<00:19:47.820> our<00:19:47.940> Matrix<00:19:48.299> chats<00:19:48.780> our 00:19:49.549 --> 00:19:49.559 align:start position:0% us in Twitter join our Matrix chats our 00:19:49.559 --> 00:19:52.490 align:start position:0% us in Twitter join our Matrix chats our code<00:19:49.860> is<00:19:50.039> also<00:19:50.340> at<00:19:50.520> here<00:19:50.940> it's<00:19:51.480> your<00:19:51.720> terms 00:19:52.490 --> 00:19:52.500 align:start position:0% code is also at here it's your terms 00:19:52.500 --> 00:19:55.669 align:start position:0% code is also at here it's your terms sourcify<00:19:53.220> visit<00:19:53.700> our<00:19:54.000> website<00:19:54.360> and<00:19:55.320> yeah<00:19:55.500> I'll 00:19:55.669 --> 00:19:55.679 align:start position:0% sourcify visit our website and yeah I'll 00:19:55.679 --> 00:19:57.230 align:start position:0% sourcify visit our website and yeah I'll be<00:19:55.799> happy<00:19:55.919> to<00:19:56.100> take<00:19:56.340> any<00:19:56.460> other<00:19:56.640> questions<00:19:56.880> if 00:19:57.230 --> 00:19:57.240 align:start position:0% be happy to take any other questions if 00:19:57.240 --> 00:19:59.210 align:start position:0% be happy to take any other questions if you<00:19:57.419> have<00:19:57.539> thank<00:19:58.020> you<00:19:58.140> I'm<00:19:58.620> wondering<00:19:58.919> how 00:19:59.210 --> 00:19:59.220 align:start position:0% you have thank you I'm wondering how 00:19:59.220 --> 00:20:01.070 align:start position:0% you have thank you I'm wondering how well<00:19:59.400> these<00:20:00.179> Solutions<00:20:00.480> can<00:20:00.720> handle 00:20:01.070 --> 00:20:01.080 align:start position:0% well these Solutions can handle 00:20:01.080 --> 00:20:03.049 align:start position:0% well these Solutions can handle translation<00:20:01.620> and<00:20:01.919> internationalizations<00:20:02.760> to 00:20:03.049 --> 00:20:03.059 align:start position:0% translation and internationalizations to 00:20:03.059 --> 00:20:04.610 align:start position:0% translation and internationalizations to provide<00:20:03.299> descriptions<00:20:03.720> in<00:20:04.020> multiple 00:20:04.610 --> 00:20:04.620 align:start position:0% provide descriptions in multiple 00:20:04.620 --> 00:20:07.130 align:start position:0% provide descriptions in multiple languages<00:20:04.919> yeah<00:20:05.539> uh<00:20:06.539> that's<00:20:06.720> also<00:20:07.020> one 00:20:07.130 --> 00:20:07.140 align:start position:0% languages yeah uh that's also one 00:20:07.140 --> 00:20:10.789 align:start position:0% languages yeah uh that's also one consideration<00:20:07.940> there<00:20:08.940> uh<00:20:09.660> we<00:20:10.140> have<00:20:10.260> the<00:20:10.440> idea 00:20:10.789 --> 00:20:10.799 align:start position:0% consideration there uh we have the idea 00:20:10.799 --> 00:20:15.049 align:start position:0% consideration there uh we have the idea of<00:20:11.340> maybe<00:20:12.000> having<00:20:12.299> a<00:20:13.140> custom<00:20:14.039> not<00:20:14.520> spec<00:20:14.820> field 00:20:15.049 --> 00:20:15.059 align:start position:0% of maybe having a custom not spec field 00:20:15.059 --> 00:20:17.150 align:start position:0% of maybe having a custom not spec field for<00:20:15.299> translations<00:20:15.720> and<00:20:16.200> in<00:20:16.440> that<00:20:16.559> field<00:20:16.740> you 00:20:17.150 --> 00:20:17.160 align:start position:0% for translations and in that field you 00:20:17.160 --> 00:20:19.789 align:start position:0% for translations and in that field you can<00:20:17.280> actually<00:20:18.200> link<00:20:19.200> to<00:20:19.559> another 00:20:19.789 --> 00:20:19.799 align:start position:0% can actually link to another 00:20:19.799 --> 00:20:23.029 align:start position:0% can actually link to another translations<00:20:20.580> file<00:20:21.480> so<00:20:22.140> that<00:20:22.740> would<00:20:22.919> be 00:20:23.029 --> 00:20:23.039 align:start position:0% translations file so that would be 00:20:23.039 --> 00:20:25.070 align:start position:0% translations file so that would be inside<00:20:23.220> the<00:20:23.520> metadata<00:20:24.000> for<00:20:24.120> example<00:20:24.360> the 00:20:25.070 --> 00:20:25.080 align:start position:0% inside the metadata for example the 00:20:25.080 --> 00:20:26.570 align:start position:0% inside the metadata for example the translations<00:20:25.559> file<00:20:25.860> and<00:20:26.100> that<00:20:26.340> will<00:20:26.460> be 00:20:26.570 --> 00:20:26.580 align:start position:0% translations file and that will be 00:20:26.580 --> 00:20:29.510 align:start position:0% translations file and that will be another<00:20:26.780> ipfs<00:20:27.780> hash<00:20:28.020> so<00:20:28.559> that<00:20:28.740> you<00:20:28.980> can<00:20:29.160> fetch 00:20:29.510 --> 00:20:29.520 align:start position:0% another ipfs hash so that you can fetch 00:20:29.520 --> 00:20:32.210 align:start position:0% another ipfs hash so that you can fetch it<00:20:29.580> and<00:20:30.000> you<00:20:30.600> can<00:20:30.660> have<00:20:30.780> other<00:20:31.020> languages<00:20:31.559> and 00:20:32.210 --> 00:20:32.220 align:start position:0% it and you can have other languages and 00:20:32.220 --> 00:20:35.230 align:start position:0% it and you can have other languages and translations<00:20:32.940> are<00:20:33.840> you<00:20:34.020> thinking<00:20:34.260> about 00:20:35.230 --> 00:20:35.240 align:start position:0% translations are you thinking about 00:20:35.240 --> 00:20:39.470 align:start position:0% translations are you thinking about ux<00:20:36.240> regression<00:20:37.140> testing<00:20:37.500> automation<00:20:37.980> somehow 00:20:39.470 --> 00:20:39.480 align:start position:0% ux regression testing automation somehow 00:20:39.480 --> 00:20:41.510 align:start position:0% ux regression testing automation somehow sorry 00:20:41.510 --> 00:20:41.520 align:start position:0% sorry 00:20:41.520 --> 00:20:44.529 align:start position:0% sorry um<00:20:41.580> are<00:20:42.360> you<00:20:42.480> thinking<00:20:42.720> about<00:20:43.220> end-to-end 00:20:44.529 --> 00:20:44.539 align:start position:0% um are you thinking about end-to-end 00:20:44.539 --> 00:20:47.150 align:start position:0% um are you thinking about end-to-end regression<00:20:45.539> testing<00:20:46.020> automation<00:20:46.620> with 00:20:47.150 --> 00:20:47.160 align:start position:0% regression testing automation with 00:20:47.160 --> 00:20:51.049 align:start position:0% regression testing automation with sourceify<00:20:47.820> so<00:20:48.299> being<00:20:48.480> able<00:20:48.720> to<00:20:48.960> include 00:20:51.049 --> 00:20:51.059 align:start position:0% sourceify so being able to include 00:20:51.059 --> 00:20:54.890 align:start position:0% sourceify so being able to include um<00:20:51.120> the<00:20:51.780> depths<00:20:52.700> in<00:20:53.700> the<00:20:54.000> whole<00:20:54.179> cycle<00:20:54.539> of 00:20:54.890 --> 00:20:54.900 align:start position:0% um the depths in the whole cycle of 00:20:54.900 --> 00:20:57.169 align:start position:0% um the depths in the whole cycle of testing<00:20:55.440> how<00:20:55.679> things<00:20:55.860> look<00:20:56.160> like<00:20:56.340> like<00:20:56.760> what 00:20:57.169 --> 00:20:57.179 align:start position:0% testing how things look like like what 00:20:57.179 --> 00:20:58.490 align:start position:0% testing how things look like like what can 00:20:58.490 --> 00:20:58.500 align:start position:0% can 00:20:58.500 --> 00:21:01.850 align:start position:0% can dabs<00:20:59.220> do<00:20:59.400> to<00:20:59.900> make<00:21:00.900> things 00:21:01.850 --> 00:21:01.860 align:start position:0% dabs do to make things 00:21:01.860 --> 00:21:05.210 align:start position:0% dabs do to make things easier<00:21:02.460> for<00:21:02.820> end<00:21:03.120> users<00:21:03.480> to<00:21:03.660> so<00:21:04.020> having<00:21:04.380> I'm 00:21:05.210 --> 00:21:05.220 align:start position:0% easier for end users to so having I'm 00:21:05.220 --> 00:21:08.690 align:start position:0% easier for end users to so having I'm sorry<00:21:05.400> is<00:21:05.700> it<00:21:05.880> having<00:21:06.299> the<00:21:07.220> sourceify<00:21:08.220> at<00:21:08.520> the 00:21:08.690 --> 00:21:08.700 align:start position:0% sorry is it having the sourceify at the 00:21:08.700 --> 00:21:11.570 align:start position:0% sorry is it having the sourceify at the whole<00:21:08.880> development<00:21:09.600> pipeline<00:21:10.200> you<00:21:10.380> mean<00:21:10.559> or 00:21:11.570 --> 00:21:11.580 align:start position:0% whole development pipeline you mean or 00:21:11.580 --> 00:21:14.390 align:start position:0% whole development pipeline you mean or I'm<00:21:11.880> not<00:21:12.000> sure<00:21:12.120> if<00:21:12.240> I<00:21:12.360> get<00:21:12.480> customers<00:21:12.840> correct 00:21:14.390 --> 00:21:14.400 align:start position:0% I'm not sure if I get customers correct 00:21:14.400 --> 00:21:15.350 align:start position:0% I'm not sure if I get customers correct um 00:21:15.350 --> 00:21:15.360 align:start position:0% um 00:21:15.360 --> 00:21:17.270 align:start position:0% um like<00:21:15.960> currently 00:21:17.270 --> 00:21:17.280 align:start position:0% like currently 00:21:17.280 --> 00:21:20.090 align:start position:0% like currently in<00:21:17.880> order<00:21:18.059> for 00:21:20.090 --> 00:21:20.100 align:start position:0% in order for 00:21:20.100 --> 00:21:22.669 align:start position:0% in order for a<00:21:20.640> developer<00:21:21.179> to<00:21:21.539> somehow<00:21:22.080> test<00:21:22.380> the 00:21:22.669 --> 00:21:22.679 align:start position:0% a developer to somehow test the 00:21:22.679 --> 00:21:24.430 align:start position:0% a developer to somehow test the end-to-end<00:21:23.100> user<00:21:23.460> experience 00:21:24.430 --> 00:21:24.440 align:start position:0% end-to-end user experience 00:21:24.440 --> 00:21:27.590 align:start position:0% end-to-end user experience it's<00:21:25.440> nearly<00:21:25.860> impossible<00:21:26.340> to<00:21:26.820> include<00:21:27.179> the 00:21:27.590 --> 00:21:27.600 align:start position:0% it's nearly impossible to include the 00:21:27.600 --> 00:21:31.010 align:start position:0% it's nearly impossible to include the web<00:21:28.080> app<00:21:28.440> and<00:21:29.039> the<00:21:29.280> wallet<00:21:29.640> interaction 00:21:31.010 --> 00:21:31.020 align:start position:0% web app and the wallet interaction 00:21:31.020 --> 00:21:35.830 align:start position:0% web app and the wallet interaction and<00:21:31.620> the<00:21:31.740> onshine<00:21:32.159> interactions 00:21:35.830 --> 00:21:35.840 align:start position:0% 00:21:35.840 --> 00:21:38.350 align:start position:0% I'm<00:21:36.840> not<00:21:36.960> sure<00:21:37.140> if<00:21:37.200> I<00:21:37.380> get<00:21:37.500> the<00:21:37.620> question 00:21:38.350 --> 00:21:38.360 align:start position:0% I'm not sure if I get the question 00:21:38.360 --> 00:21:42.289 align:start position:0% I'm not sure if I get the question correctly<00:21:39.360> but<00:21:40.020> we<00:21:40.559> are<00:21:40.799> more<00:21:40.980> like<00:21:41.280> a 00:21:42.289 --> 00:21:42.299 align:start position:0% correctly but we are more like a 00:21:42.299 --> 00:21:45.230 align:start position:0% correctly but we are more like a um<00:21:42.360> well<00:21:43.080> so<00:21:43.440> we're<00:21:43.620> not<00:21:43.860> we<00:21:44.520> just<00:21:44.640> say<00:21:44.820> people 00:21:45.230 --> 00:21:45.240 align:start position:0% um well so we're not we just say people 00:21:45.240 --> 00:21:47.690 align:start position:0% um well so we're not we just say people here<00:21:46.200> it<00:21:46.380> is<00:21:46.500> here<00:21:46.860> are<00:21:47.039> the<00:21:47.159> tools<00:21:47.400> here<00:21:47.520> are 00:21:47.690 --> 00:21:47.700 align:start position:0% here it is here are the tools here are 00:21:47.700 --> 00:21:50.029 align:start position:0% here it is here are the tools here are the<00:21:47.880> files<00:21:48.480> just<00:21:49.020> please<00:21:49.200> make<00:21:49.440> use<00:21:49.559> of<00:21:49.740> it<00:21:49.860> so 00:21:50.029 --> 00:21:50.039 align:start position:0% the files just please make use of it so 00:21:50.039 --> 00:21:54.350 align:start position:0% the files just please make use of it so we<00:21:50.220> don't<00:21:50.720> actively<00:21:51.720> get<00:21:52.500> involved<00:21:52.860> in<00:21:52.980> the<00:21:53.159> ux 00:21:54.350 --> 00:21:54.360 align:start position:0% we don't actively get involved in the ux 00:21:54.360 --> 00:21:57.770 align:start position:0% we don't actively get involved in the ux contract<00:21:55.039> interactions<00:21:56.039> or<00:21:56.520> that's<00:21:57.360> not<00:21:57.780> not 00:21:57.770 --> 00:21:57.780 align:start position:0% contract interactions or that's not not 00:21:57.780 --> 00:21:59.570 align:start position:0% contract interactions or that's not not in<00:21:58.140> your<00:21:58.320> complete<00:21:58.799> pipeline<00:21:59.159> I<00:21:59.340> would<00:21:59.460> say 00:21:59.570 --> 00:21:59.580 align:start position:0% in your complete pipeline I would say 00:21:59.580 --> 00:22:02.149 align:start position:0% in your complete pipeline I would say for<00:22:00.179> user<00:22:00.600> protection<00:22:01.140> am<00:22:01.620> I<00:22:01.799> right<00:22:01.919> in 00:22:02.149 --> 00:22:02.159 align:start position:0% for user protection am I right in 00:22:02.159 --> 00:22:05.210 align:start position:0% for user protection am I right in thinking<00:22:02.460> that<00:22:02.760> the<00:22:03.559> reputational<00:22:04.559> and 00:22:05.210 --> 00:22:05.220 align:start position:0% thinking that the reputational and 00:22:05.220 --> 00:22:06.890 align:start position:0% thinking that the reputational and statistical<00:22:05.760> characteristics<00:22:06.720> you 00:22:06.890 --> 00:22:06.900 align:start position:0% statistical characteristics you 00:22:06.900 --> 00:22:09.409 align:start position:0% statistical characteristics you mentioned<00:22:07.320> are<00:22:08.159> really<00:22:08.340> important 00:22:09.409 --> 00:22:09.419 align:start position:0% mentioned are really important 00:22:09.419 --> 00:22:12.710 align:start position:0% mentioned are really important um who's<00:22:10.200> talking<00:22:10.380> right<00:22:10.679> here<00:22:11.299> because<00:22:12.299> I'm 00:22:12.710 --> 00:22:12.720 align:start position:0% um who's talking right here because I'm 00:22:12.720 --> 00:22:14.270 align:start position:0% um who's talking right here because I'm just<00:22:12.840> thinking<00:22:13.260> and<00:22:13.679> correct<00:22:13.860> me<00:22:13.980> if<00:22:14.100> I'm 00:22:14.270 --> 00:22:14.280 align:start position:0% just thinking and correct me if I'm 00:22:14.280 --> 00:22:17.149 align:start position:0% just thinking and correct me if I'm wrong<00:22:14.400> but<00:22:14.640> I'm<00:22:14.760> malicious<00:22:15.380> deployer<00:22:16.380> could 00:22:17.149 --> 00:22:17.159 align:start position:0% wrong but I'm malicious deployer could 00:22:17.159 --> 00:22:20.210 align:start position:0% wrong but I'm malicious deployer could create<00:22:17.400> a<00:22:17.520> malicious<00:22:17.880> contract<00:22:18.539> this<00:22:19.020> uh 00:22:20.210 --> 00:22:20.220 align:start position:0% create a malicious contract this uh 00:22:20.220 --> 00:22:22.370 align:start position:0% create a malicious contract this uh describe<00:22:21.000> it<00:22:21.059> in<00:22:21.240> a<00:22:21.360> malicious<00:22:21.659> way<00:22:21.900> with<00:22:22.200> Matt 00:22:22.370 --> 00:22:22.380 align:start position:0% describe it in a malicious way with Matt 00:22:22.380 --> 00:22:24.770 align:start position:0% describe it in a malicious way with Matt Speck<00:22:22.919> and<00:22:23.280> then<00:22:23.460> yeah<00:22:23.700> take<00:22:24.360> advantage<00:22:24.600> of 00:22:24.770 --> 00:22:24.780 align:start position:0% Speck and then yeah take advantage of 00:22:24.780 --> 00:22:25.669 align:start position:0% Speck and then yeah take advantage of the<00:22:24.840> user 00:22:25.669 --> 00:22:25.679 align:start position:0% the user 00:22:25.679 --> 00:22:28.430 align:start position:0% the user yeah<00:22:26.640> um<00:22:26.700> I<00:22:27.000> mean<00:22:27.120> obviously<00:22:27.960> we<00:22:28.140> have<00:22:28.320> the 00:22:28.430 --> 00:22:28.440 align:start position:0% yeah um I mean obviously we have the 00:22:28.440 --> 00:22:31.250 align:start position:0% yeah um I mean obviously we have the assumption<00:22:28.919> that<00:22:29.640> the<00:22:29.940> contract<00:22:30.240> deployer<00:22:30.780> is 00:22:31.250 --> 00:22:31.260 align:start position:0% assumption that the contract deployer is 00:22:31.260 --> 00:22:35.810 align:start position:0% assumption that the contract deployer is uh<00:22:31.980> nine<00:22:32.520> it's<00:22:32.760> not<00:22:32.940> malicious<00:22:33.419> so<00:22:34.080> it's<00:22:34.340> uh<00:22:35.340> we 00:22:35.810 --> 00:22:35.820 align:start position:0% uh nine it's not malicious so it's uh we 00:22:35.820 --> 00:22:39.350 align:start position:0% uh nine it's not malicious so it's uh we verify<00:22:36.360> the<00:22:36.720> content<00:22:37.140> of<00:22:37.799> the<00:22:38.100> uh 00:22:39.350 --> 00:22:39.360 align:start position:0% verify the content of the uh 00:22:39.360 --> 00:22:41.870 align:start position:0% verify the content of the uh the<00:22:39.679> contract<00:22:40.679> but<00:22:41.159> there<00:22:41.340> are<00:22:41.520> as<00:22:41.640> I<00:22:41.760> said 00:22:41.870 --> 00:22:41.880 align:start position:0% the contract but there are as I said 00:22:41.880 --> 00:22:43.250 align:start position:0% the contract but there are as I said there<00:22:42.059> are<00:22:42.240> other<00:22:42.299> ways<00:22:42.659> to<00:22:42.840> do<00:22:42.960> that<00:22:43.140> for 00:22:43.250 --> 00:22:43.260 align:start position:0% there are other ways to do that for 00:22:43.260 --> 00:22:46.250 align:start position:0% there are other ways to do that for example<00:22:43.500> audits<00:22:44.100> scam<00:22:45.059> lists<00:22:45.419> so<00:22:45.960> this<00:22:46.200> is 00:22:46.250 --> 00:22:46.260 align:start position:0% example audits scam lists so this is 00:22:46.260 --> 00:22:47.990 align:start position:0% example audits scam lists so this is another<00:22:46.440> aspect<00:22:46.980> so<00:22:47.220> we<00:22:47.400> have<00:22:47.520> like<00:22:47.700> this 00:22:47.990 --> 00:22:48.000 align:start position:0% another aspect so we have like this 00:22:48.000 --> 00:22:50.330 align:start position:0% another aspect so we have like this neutral<00:22:48.419> eye<00:22:49.140> to<00:22:49.679> what's<00:22:49.860> inside<00:22:50.039> the 00:22:50.330 --> 00:22:50.340 align:start position:0% neutral eye to what's inside the 00:22:50.340 --> 00:22:52.010 align:start position:0% neutral eye to what's inside the contract<00:22:50.700> and<00:22:51.240> it's<00:22:51.419> up<00:22:51.600> to<00:22:51.720> the<00:22:51.900> community 00:22:52.010 --> 00:22:52.020 align:start position:0% contract and it's up to the community 00:22:52.020 --> 00:22:55.010 align:start position:0% contract and it's up to the community and<00:22:52.559> the<00:22:52.880> other<00:22:53.880> types<00:22:54.179> of<00:22:54.299> methods<00:22:54.780> to 00:22:55.010 --> 00:22:55.020 align:start position:0% and the other types of methods to 00:22:55.020 --> 00:22:57.710 align:start position:0% and the other types of methods to actually<00:22:55.260> see<00:22:55.559> it's<00:22:55.919> not<00:22:56.280> a<00:22:56.940> malicious 00:22:57.710 --> 00:22:57.720 align:start position:0% actually see it's not a malicious 00:22:57.720 --> 00:23:00.470 align:start position:0% actually see it's not a malicious contract<00:22:58.080> uh<00:22:58.620> thanks<00:22:58.860> for<00:22:59.039> the<00:22:59.220> talk<00:22:59.480> so 00:23:00.470 --> 00:23:00.480 align:start position:0% contract uh thanks for the talk so 00:23:00.480 --> 00:23:03.289 align:start position:0% contract uh thanks for the talk so question<00:23:00.720> I<00:23:01.020> had<00:23:01.200> was<00:23:01.620> for<00:23:02.220> contract<00:23:02.760> coverage 00:23:03.289 --> 00:23:03.299 align:start position:0% question I had was for contract coverage 00:23:03.299 --> 00:23:06.289 align:start position:0% question I had was for contract coverage like<00:23:04.140> what<00:23:04.440> is<00:23:04.559> it<00:23:04.740> like<00:23:05.159> is<00:23:05.280> it<00:23:05.460> limited<00:23:05.940> to 00:23:06.289 --> 00:23:06.299 align:start position:0% like what is it like is it limited to 00:23:06.299 --> 00:23:09.950 align:start position:0% like what is it like is it limited to what's<00:23:06.539> verified<00:23:07.140> on<00:23:07.500> ether<00:23:07.919> scan<00:23:08.400> or 00:23:09.950 --> 00:23:09.960 align:start position:0% what's verified on ether scan or 00:23:09.960 --> 00:23:12.770 align:start position:0% what's verified on ether scan or um<00:23:10.020> like<00:23:10.500> like<00:23:10.980> yeah<00:23:11.280> in<00:23:11.520> terms<00:23:11.760> of<00:23:11.820> like<00:23:12.000> abis 00:23:12.770 --> 00:23:12.780 align:start position:0% um like like yeah in terms of like abis 00:23:12.780 --> 00:23:15.049 align:start position:0% um like like yeah in terms of like abis that<00:23:13.200> might<00:23:13.380> not<00:23:13.500> be<00:23:13.679> fully<00:23:14.100> complete<00:23:14.520> like 00:23:15.049 --> 00:23:15.059 align:start position:0% that might not be fully complete like 00:23:15.059 --> 00:23:17.510 align:start position:0% that might not be fully complete like what<00:23:15.299> is<00:23:15.419> sourceify<00:23:16.080> fully<00:23:16.440> covered 00:23:17.510 --> 00:23:17.520 align:start position:0% what is sourceify fully covered 00:23:17.520 --> 00:23:19.850 align:start position:0% what is sourceify fully covered what<00:23:18.059> what<00:23:18.240> do<00:23:18.539> you<00:23:18.539> mean<00:23:18.659> by<00:23:18.780> cover<00:23:18.960> in<00:23:19.620> terms 00:23:19.850 --> 00:23:19.860 align:start position:0% what what do you mean by cover in terms 00:23:19.860 --> 00:23:21.409 align:start position:0% what what do you mean by cover in terms of<00:23:19.919> like<00:23:20.039> contract<00:23:20.400> coverage<00:23:20.760> like<00:23:21.059> if 00:23:21.409 --> 00:23:21.419 align:start position:0% of like contract coverage like if 00:23:21.419 --> 00:23:23.690 align:start position:0% of like contract coverage like if someone<00:23:21.600> deploys<00:23:22.140> a<00:23:22.380> new<00:23:22.500> contract<00:23:22.919> it's<00:23:23.520> not 00:23:23.690 --> 00:23:23.700 align:start position:0% someone deploys a new contract it's not 00:23:23.700 --> 00:23:26.330 align:start position:0% someone deploys a new contract it's not verified<00:23:24.120> on<00:23:24.360> either<00:23:24.659> scan<00:23:25.200> then<00:23:25.799> do<00:23:26.039> you<00:23:26.220> guys 00:23:26.330 --> 00:23:26.340 align:start position:0% verified on either scan then do you guys 00:23:26.340 --> 00:23:29.630 align:start position:0% verified on either scan then do you guys still<00:23:26.760> provide<00:23:27.480> the<00:23:28.440> human<00:23:28.500> readable<00:23:29.039> aspect 00:23:29.630 --> 00:23:29.640 align:start position:0% still provide the human readable aspect 00:23:29.640 --> 00:23:32.750 align:start position:0% still provide the human readable aspect or<00:23:30.179> yes<00:23:30.600> I<00:23:31.260> mean<00:23:31.380> source5<00:23:32.100> is<00:23:32.280> a<00:23:32.460> completely 00:23:32.750 --> 00:23:32.760 align:start position:0% or yes I mean source5 is a completely 00:23:32.760 --> 00:23:34.549 align:start position:0% or yes I mean source5 is a completely different<00:23:32.940> thing<00:23:33.179> than<00:23:33.360> eaterscan<00:23:33.960> if<00:23:34.380> the 00:23:34.549 --> 00:23:34.559 align:start position:0% different thing than eaterscan if the 00:23:34.559 --> 00:23:36.590 align:start position:0% different thing than eaterscan if the scan<00:23:34.860> is<00:23:35.039> both<00:23:35.220> a<00:23:35.460> verification<00:23:36.000> service<00:23:36.299> and 00:23:36.590 --> 00:23:36.600 align:start position:0% scan is both a verification service and 00:23:36.600 --> 00:23:38.570 align:start position:0% scan is both a verification service and a<00:23:36.720> block<00:23:36.900> Explorer<00:23:37.440> but<00:23:37.919> source<00:23:38.220> file<00:23:38.400> is<00:23:38.460> not 00:23:38.570 --> 00:23:38.580 align:start position:0% a block Explorer but source file is not 00:23:38.580 --> 00:23:40.610 align:start position:0% a block Explorer but source file is not a<00:23:38.640> block<00:23:38.760> Explorer<00:23:39.240> we<00:23:39.419> just<00:23:39.659> we<00:23:40.080> are<00:23:40.260> just<00:23:40.440> a 00:23:40.610 --> 00:23:40.620 align:start position:0% a block Explorer we just we are just a 00:23:40.620 --> 00:23:43.070 align:start position:0% a block Explorer we just we are just a contract<00:23:40.919> verification<00:23:41.400> service<00:23:41.720> and<00:23:42.720> I 00:23:43.070 --> 00:23:43.080 align:start position:0% contract verification service and I 00:23:43.080 --> 00:23:44.990 align:start position:0% contract verification service and I would<00:23:43.200> say<00:23:43.380> we<00:23:43.679> have<00:23:43.799> different<00:23:44.159> contract 00:23:44.990 --> 00:23:45.000 align:start position:0% would say we have different contract 00:23:45.000 --> 00:23:47.149 align:start position:0% would say we have different contract sets<00:23:45.419> than<00:23:45.900> it<00:23:46.080> can<00:23:46.440> so<00:23:46.679> you<00:23:46.980> can<00:23:47.039> actually 00:23:47.149 --> 00:23:47.159 align:start position:0% sets than it can so you can actually 00:23:47.159 --> 00:23:49.250 align:start position:0% sets than it can so you can actually import<00:23:47.460> but<00:23:48.179> it's<00:23:48.360> a<00:23:48.480> different<00:23:48.600> contract<00:23:49.020> set 00:23:49.250 --> 00:23:49.260 align:start position:0% import but it's a different contract set 00:23:49.260 --> 00:23:51.529 align:start position:0% import but it's a different contract set so<00:23:49.620> even<00:23:49.740> for<00:23:49.980> like<00:23:50.159> new<00:23:50.400> contracts<00:23:51.000> you<00:23:51.360> guys 00:23:51.529 --> 00:23:51.539 align:start position:0% so even for like new contracts you guys 00:23:51.539 --> 00:23:54.470 align:start position:0% so even for like new contracts you guys instantly<00:23:52.140> get<00:23:52.500> into<00:23:52.679> the<00:23:52.919> pipeline<00:23:53.480> verify 00:23:54.470 --> 00:23:54.480 align:start position:0% instantly get into the pipeline verify 00:23:54.480 --> 00:23:56.570 align:start position:0% instantly get into the pipeline verify and<00:23:54.840> then<00:23:54.900> make<00:23:55.080> it<00:23:55.260> readable<00:23:55.620> yeah<00:23:56.159> exactly 00:23:56.570 --> 00:23:56.580 align:start position:0% and then make it readable yeah exactly 00:23:56.580 --> 00:23:58.490 align:start position:0% and then make it readable yeah exactly gotcha<00:23:57.179> and<00:23:57.299> any<00:23:57.539> contract<00:23:57.900> that<00:23:58.080> is<00:23:58.200> deployed 00:23:58.490 --> 00:23:58.500 align:start position:0% gotcha and any contract that is deployed 00:23:58.500 --> 00:24:00.890 align:start position:0% gotcha and any contract that is deployed we<00:23:58.740> can<00:23:58.860> just<00:23:58.980> verify<00:23:59.460> okay<00:23:59.940> okay<00:24:00.360> and<00:24:00.780> even 00:24:00.890 --> 00:24:00.900 align:start position:0% we can just verify okay okay and even 00:24:00.900 --> 00:24:02.570 align:start position:0% we can just verify okay okay and even also<00:24:01.320> different<00:24:01.500> chains<00:24:01.919> like<00:24:02.039> we<00:24:02.159> don't<00:24:02.280> we 00:24:02.570 --> 00:24:02.580 align:start position:0% also different chains like we don't we 00:24:02.580 --> 00:24:05.090 align:start position:0% also different chains like we don't we have<00:24:02.700> I<00:24:02.940> think<00:24:03.059> like<00:24:03.360> 30<00:24:04.140> something<00:24:04.559> evm 00:24:05.090 --> 00:24:05.100 align:start position:0% have I think like 30 something evm 00:24:05.100 --> 00:24:07.789 align:start position:0% have I think like 30 something evm chains<00:24:05.460> right<00:24:05.640> now<00:24:05.760> so<00:24:06.720> you<00:24:06.900> can<00:24:07.020> even<00:24:07.140> verify 00:24:07.789 --> 00:24:07.799 align:start position:0% chains right now so you can even verify 00:24:07.799 --> 00:24:10.130 align:start position:0% chains right now so you can even verify contracts<00:24:08.460> on<00:24:08.580> other<00:24:08.760> chains<00:24:09.179> but<00:24:09.840> at<00:24:09.960> the<00:24:10.080> end 00:24:10.130 --> 00:24:10.140 align:start position:0% contracts on other chains but at the end 00:24:10.140 --> 00:24:12.169 align:start position:0% contracts on other chains but at the end of<00:24:10.260> the<00:24:10.320> day<00:24:10.500> actually<00:24:10.679> we<00:24:11.100> we<00:24:11.640> have<00:24:12.059> support 00:24:12.169 --> 00:24:12.179 align:start position:0% of the day actually we we have support 00:24:12.179 --> 00:24:13.610 align:start position:0% of the day actually we we have support for<00:24:12.419> different<00:24:12.600> chains<00:24:13.020> but<00:24:13.200> we<00:24:13.440> actually 00:24:13.610 --> 00:24:13.620 align:start position:0% for different chains but we actually 00:24:13.620 --> 00:24:15.169 align:start position:0% for different chains but we actually want<00:24:13.980> everyone 00:24:15.169 --> 00:24:15.179 align:start position:0% want everyone 00:24:15.179 --> 00:24:17.029 align:start position:0% want everyone at<00:24:15.780> some<00:24:15.900> point<00:24:16.020> to<00:24:16.260> run<00:24:16.440> their<00:24:16.620> own<00:24:16.740> source 00:24:17.029 --> 00:24:17.039 align:start position:0% at some point to run their own source 00:24:17.039 --> 00:24:19.130 align:start position:0% at some point to run their own source file<00:24:17.280> for<00:24:17.460> their<00:24:17.640> own<00:24:17.760> chains<00:24:18.179> cool<00:24:18.840> okay 00:24:19.130 --> 00:24:19.140 align:start position:0% file for their own chains cool okay 00:24:19.140 --> 00:24:21.049 align:start position:0% file for their own chains cool okay thank<00:24:19.500> you 00:24:21.049 --> 00:24:21.059 align:start position:0% thank you 00:24:21.059 --> 00:24:23.930 align:start position:0% thank you maybe<00:24:21.480> last<00:24:21.780> question 00:24:23.930 --> 00:24:23.940 align:start position:0% maybe last question 00:24:23.940 --> 00:24:26.930 align:start position:0% maybe last question um<00:24:24.000> is<00:24:24.419> it<00:24:24.539> in<00:24:24.720> the<00:24:25.020> scope<00:24:25.440> of<00:24:25.679> sortsify<00:24:26.520> to 00:24:26.930 --> 00:24:26.940 align:start position:0% um is it in the scope of sortsify to 00:24:26.940 --> 00:24:29.630 align:start position:0% um is it in the scope of sortsify to like<00:24:27.240> maintain<00:24:27.720> reputation<00:24:28.260> of<00:24:28.740> the<00:24:29.039> commands 00:24:29.630 --> 00:24:29.640 align:start position:0% like maintain reputation of the commands 00:24:29.640 --> 00:24:32.029 align:start position:0% like maintain reputation of the commands or<00:24:30.419> maybe<00:24:30.659> even<00:24:30.840> validate<00:24:31.380> the<00:24:31.500> comments 00:24:32.029 --> 00:24:32.039 align:start position:0% or maybe even validate the comments 00:24:32.039 --> 00:24:34.750 align:start position:0% or maybe even validate the comments actually<00:24:32.280> reflect<00:24:32.820> the<00:24:33.000> code 00:24:34.750 --> 00:24:34.760 align:start position:0% actually reflect the code 00:24:34.760 --> 00:24:37.789 align:start position:0% actually reflect the code like<00:24:35.760> sound<00:24:35.940> here<00:24:36.179> is<00:24:36.360> not<00:24:36.480> so<00:24:36.659> good<00:24:36.840> uh<00:24:37.380> is<00:24:37.620> it 00:24:37.789 --> 00:24:37.799 align:start position:0% like sound here is not so good uh is it 00:24:37.799 --> 00:24:41.090 align:start position:0% like sound here is not so good uh is it in<00:24:38.100> the<00:24:38.220> scope<00:24:38.460> of<00:24:38.640> source<00:24:39.179> if<00:24:39.299> I<00:24:39.480> to<00:24:40.320> uh 00:24:41.090 --> 00:24:41.100 align:start position:0% in the scope of source if I to uh 00:24:41.100 --> 00:24:43.669 align:start position:0% in the scope of source if I to uh maintain<00:24:41.760> like<00:24:42.120> a<00:24:42.360> reputation<00:24:42.840> scope<00:24:43.260> for<00:24:43.559> the 00:24:43.669 --> 00:24:43.679 align:start position:0% maintain like a reputation scope for the 00:24:43.679 --> 00:24:47.810 align:start position:0% maintain like a reputation scope for the comments<00:24:44.220> or<00:24:45.120> to<00:24:45.840> validate<00:24:46.380> if<00:24:46.620> the<00:24:47.039> comments 00:24:47.810 --> 00:24:47.820 align:start position:0% comments or to validate if the comments 00:24:47.820 --> 00:24:50.750 align:start position:0% comments or to validate if the comments reflect<00:24:48.480> the<00:24:48.659> code<00:24:48.900> the<00:24:49.799> application<00:24:50.220> commits 00:24:50.750 --> 00:24:50.760 align:start position:0% reflect the code the application commits 00:24:50.760 --> 00:24:53.990 align:start position:0% reflect the code the application commits you<00:24:50.940> say<00:24:51.059> yeah<00:24:51.600> the<00:24:51.900> comments<00:24:52.440> comments 00:24:53.990 --> 00:24:54.000 align:start position:0% you say yeah the comments comments 00:24:54.000 --> 00:24:56.510 align:start position:0% you say yeah the comments comments um<00:24:54.120> I<00:24:54.419> mean<00:24:54.480> no<00:24:54.659> we<00:24:55.020> just<00:24:55.380> as<00:24:55.679> I<00:24:55.860> said<00:24:55.919> we<00:24:56.220> are<00:24:56.400> a 00:24:56.510 --> 00:24:56.520 align:start position:0% um I mean no we just as I said we are a 00:24:56.520 --> 00:24:57.490 align:start position:0% um I mean no we just as I said we are a tool 00:24:57.490 --> 00:24:57.500 align:start position:0% tool 00:24:57.500 --> 00:25:00.169 align:start position:0% tool to<00:24:58.500> achieve<00:24:59.280> this<00:24:59.460> and<00:24:59.640> at<00:24:59.760> the<00:24:59.880> end<00:25:00.000> of<00:25:00.059> the 00:25:00.169 --> 00:25:00.179 align:start position:0% to achieve this and at the end of the 00:25:00.179 --> 00:25:02.210 align:start position:0% to achieve this and at the end of the day<00:25:00.299> the<00:25:00.480> developers<00:25:00.900> have<00:25:01.200> to 00:25:02.210 --> 00:25:02.220 align:start position:0% day the developers have to 00:25:02.220 --> 00:25:06.409 align:start position:0% day the developers have to document<00:25:03.059> and<00:25:03.360> comment<00:25:03.960> their<00:25:04.400> code<00:25:05.400> so<00:25:06.179> they 00:25:06.409 --> 00:25:06.419 align:start position:0% document and comment their code so they 00:25:06.419 --> 00:25:09.049 align:start position:0% document and comment their code so they have<00:25:06.600> to<00:25:06.659> keep<00:25:06.840> in<00:25:07.020> mind<00:25:07.200> that<00:25:08.159> this<00:25:08.460> will<00:25:08.640> this 00:25:09.049 --> 00:25:09.059 align:start position:0% have to keep in mind that this will this 00:25:09.059 --> 00:25:11.570 align:start position:0% have to keep in mind that this will this might<00:25:09.240> be<00:25:09.360> a<00:25:09.539> user-facing<00:25:10.200> method<00:25:10.580> and 00:25:11.570 --> 00:25:11.580 align:start position:0% might be a user-facing method and 00:25:11.580 --> 00:25:13.970 align:start position:0% might be a user-facing method and properly<00:25:12.539> document<00:25:12.900> it 00:25:13.970 --> 00:25:13.980 align:start position:0% properly document it 00:25:13.980 --> 00:25:15.529 align:start position:0% properly document it thanks<00:25:14.340> yeah 00:25:15.529 --> 00:25:15.539 align:start position:0% thanks yeah 00:25:15.539 --> 00:25:17.930 align:start position:0% thanks yeah um<00:25:15.659> I<00:25:15.900> think<00:25:15.960> we're<00:25:16.080> out<00:25:16.320> of<00:25:16.500> time<00:25:16.679> uh<00:25:17.640> just 00:25:17.930 --> 00:25:17.940 align:start position:0% um I think we're out of time uh just 00:25:17.940 --> 00:25:21.230 align:start position:0% um I think we're out of time uh just find<00:25:18.179> me<00:25:18.419> after<00:25:19.020> the<00:25:19.260> talk<00:25:19.500> or<00:25:20.340> also<00:25:20.880> you<00:25:21.059> can 00:25:21.230 --> 00:25:21.240 align:start position:0% find me after the talk or also you can 00:25:21.240 --> 00:25:23.630 align:start position:0% find me after the talk or also you can yeah<00:25:21.600> find<00:25:22.320> sourceify<00:25:22.919> and<00:25:23.039> reach<00:25:23.400> us<00:25:23.460> out 00:25:23.630 --> 00:25:23.640 align:start position:0% yeah find sourceify and reach us out 00:25:23.640 --> 00:25:26.539 align:start position:0% yeah find sourceify and reach us out there<00:25:23.820> thank<00:25:24.360> you