WEBVTT Kind: captions Language: en 00:00:00.000 --> 00:00:04.350 align:start position:0% foreign 00:00:04.350 --> 00:00:04.360 align:start position:0% 00:00:04.360 --> 00:00:15.849 align:start position:0% [Music] 00:00:15.849 --> 00:00:15.859 align:start position:0% 00:00:15.859 --> 00:00:18.890 align:start position:0% and<00:00:16.859> this<00:00:17.100> talks<00:00:17.520> talks<00:00:17.940> about<00:00:18.119> like<00:00:18.660> five 00:00:18.890 --> 00:00:18.900 align:start position:0% and this talks talks about like five 00:00:18.900 --> 00:00:20.570 align:start position:0% and this talks talks about like five smart<00:00:19.199> contract<00:00:19.560> pattern<00:00:19.920> but<00:00:20.220> that's 00:00:20.570 --> 00:00:20.580 align:start position:0% smart contract pattern but that's 00:00:20.580 --> 00:00:23.029 align:start position:0% smart contract pattern but that's actually<00:00:20.820> a<00:00:21.180> lie<00:00:21.420> the<00:00:22.140> real<00:00:22.320> thing<00:00:22.560> I<00:00:22.740> want<00:00:22.859> to 00:00:23.029 --> 00:00:23.039 align:start position:0% actually a lie the real thing I want to 00:00:23.039 --> 00:00:25.310 align:start position:0% actually a lie the real thing I want to discuss<00:00:23.400> is<00:00:23.820> what<00:00:24.240> I<00:00:24.480> think<00:00:24.600> are<00:00:24.840> it's<00:00:25.080> a<00:00:25.260> good 00:00:25.310 --> 00:00:25.320 align:start position:0% discuss is what I think are it's a good 00:00:25.320 --> 00:00:27.349 align:start position:0% discuss is what I think are it's a good mindset<00:00:25.800> when<00:00:25.980> writing<00:00:26.400> solidity<00:00:26.939> contract 00:00:27.349 --> 00:00:27.359 align:start position:0% mindset when writing solidity contract 00:00:27.359 --> 00:00:28.849 align:start position:0% mindset when writing solidity contract and<00:00:27.599> basically<00:00:27.960> the<00:00:28.199> pattern<00:00:28.439> I'm<00:00:28.619> going<00:00:28.740> to 00:00:28.849 --> 00:00:28.859 align:start position:0% and basically the pattern I'm going to 00:00:28.859 --> 00:00:31.130 align:start position:0% and basically the pattern I'm going to show<00:00:29.039> you<00:00:29.160> are<00:00:29.340> more<00:00:29.580> of<00:00:29.760> like<00:00:30.000> examples<00:00:30.779> of 00:00:31.130 --> 00:00:31.140 align:start position:0% show you are more of like examples of 00:00:31.140 --> 00:00:34.010 align:start position:0% show you are more of like examples of what<00:00:32.040> I<00:00:32.160> think<00:00:32.279> can<00:00:32.579> be<00:00:32.820> a<00:00:33.180> fun<00:00:33.480> development 00:00:34.010 --> 00:00:34.020 align:start position:0% what I think can be a fun development 00:00:34.020 --> 00:00:35.810 align:start position:0% what I think can be a fun development and<00:00:34.260> solidity<00:00:34.620> and<00:00:34.800> how<00:00:34.980> I<00:00:35.100> think<00:00:35.219> it<00:00:35.399> aligns 00:00:35.810 --> 00:00:35.820 align:start position:0% and solidity and how I think it aligns 00:00:35.820 --> 00:00:39.410 align:start position:0% and solidity and how I think it aligns with<00:00:35.940> the<00:00:36.180> good<00:00:36.420> good<00:00:36.960> development<00:00:37.860> practices 00:00:39.410 --> 00:00:39.420 align:start position:0% with the good good development practices 00:00:39.420 --> 00:00:41.930 align:start position:0% with the good good development practices wait 00:00:41.930 --> 00:00:41.940 align:start position:0% wait 00:00:41.940 --> 00:00:44.510 align:start position:0% wait distance<00:00:42.480> okay<00:00:43.140> yeah<00:00:43.500> so<00:00:43.800> I<00:00:43.920> think<00:00:44.040> one<00:00:44.280> of<00:00:44.399> the 00:00:44.510 --> 00:00:44.520 align:start position:0% distance okay yeah so I think one of the 00:00:44.520 --> 00:00:46.069 align:start position:0% distance okay yeah so I think one of the two<00:00:44.879> main<00:00:45.000> points<00:00:45.300> I<00:00:45.420> want<00:00:45.540> to<00:00:45.600> make<00:00:45.719> today<00:00:45.840> is 00:00:46.069 --> 00:00:46.079 align:start position:0% two main points I want to make today is 00:00:46.079 --> 00:00:48.290 align:start position:0% two main points I want to make today is that<00:00:46.200> a<00:00:46.320> lot<00:00:46.440> of<00:00:46.559> the<00:00:46.620> ecosystems<00:00:47.280> value<00:00:47.460> is<00:00:48.120> a 00:00:48.290 --> 00:00:48.300 align:start position:0% that a lot of the ecosystems value is a 00:00:48.300 --> 00:00:49.910 align:start position:0% that a lot of the ecosystems value is a result<00:00:48.480> of<00:00:48.719> smart<00:00:48.899> contract<00:00:49.200> composability 00:00:49.910 --> 00:00:49.920 align:start position:0% result of smart contract composability 00:00:49.920 --> 00:00:53.029 align:start position:0% result of smart contract composability uh<00:00:50.820> that's<00:00:51.239> particularly<00:00:51.660> true<00:00:51.840> of<00:00:52.020> defy<00:00:52.500> and 00:00:53.029 --> 00:00:53.039 align:start position:0% uh that's particularly true of defy and 00:00:53.039 --> 00:00:54.290 align:start position:0% uh that's particularly true of defy and the<00:00:53.219> first<00:00:53.340> thing<00:00:53.520> you<00:00:53.700> should<00:00:53.820> do<00:00:54.000> when 00:00:54.290 --> 00:00:54.300 align:start position:0% the first thing you should do when 00:00:54.300 --> 00:00:55.910 align:start position:0% the first thing you should do when writing<00:00:54.600> a<00:00:54.660> smart<00:00:54.840> contract<00:00:55.199> is<00:00:55.379> make<00:00:55.680> sure 00:00:55.910 --> 00:00:55.920 align:start position:0% writing a smart contract is make sure 00:00:55.920 --> 00:00:57.950 align:start position:0% writing a smart contract is make sure that<00:00:56.280> you<00:00:56.699> are<00:00:56.879> leveraging<00:00:57.300> as<00:00:57.780> much 00:00:57.950 --> 00:00:57.960 align:start position:0% that you are leveraging as much 00:00:57.960 --> 00:01:00.229 align:start position:0% that you are leveraging as much composability<00:00:58.739> as<00:00:59.100> possible<00:00:59.460> and<00:00:59.940> trying<00:01:00.120> to 00:01:00.229 --> 00:01:00.239 align:start position:0% composability as possible and trying to 00:01:00.239 --> 00:01:01.430 align:start position:0% composability as possible and trying to make<00:01:00.420> sure<00:01:00.600> that<00:01:00.840> your<00:01:00.960> contract<00:01:01.260> can 00:01:01.430 --> 00:01:01.440 align:start position:0% make sure that your contract can 00:01:01.440 --> 00:01:03.470 align:start position:0% make sure that your contract can interface<00:01:01.800> with<00:01:02.039> all<00:01:02.520> the<00:01:02.760> existing<00:01:03.120> tooling 00:01:03.470 --> 00:01:03.480 align:start position:0% interface with all the existing tooling 00:01:03.480 --> 00:01:05.690 align:start position:0% interface with all the existing tooling that<00:01:03.660> would<00:01:03.899> be<00:01:04.080> relevant<00:01:04.500> an<00:01:05.220> example<00:01:05.519> is 00:01:05.690 --> 00:01:05.700 align:start position:0% that would be relevant an example is 00:01:05.700 --> 00:01:07.670 align:start position:0% that would be relevant an example is people<00:01:05.939> always<00:01:06.299> ask<00:01:06.659> us<00:01:06.840> like<00:01:07.020> hey<00:01:07.260> can<00:01:07.560> we 00:01:07.670 --> 00:01:07.680 align:start position:0% people always ask us like hey can we 00:01:07.680 --> 00:01:10.190 align:start position:0% people always ask us like hey can we make<00:01:07.860> an<00:01:08.040> honorable<00:01:08.460> contract<00:01:09.000> payable<00:01:09.900> like 00:01:10.190 --> 00:01:10.200 align:start position:0% make an honorable contract payable like 00:01:10.200 --> 00:01:12.710 align:start position:0% make an honorable contract payable like someone<00:01:10.380> could<00:01:10.680> buy<00:01:11.040> it<00:01:11.220> and<00:01:12.060> this<00:01:12.540> makes 00:01:12.710 --> 00:01:12.720 align:start position:0% someone could buy it and this makes 00:01:12.720 --> 00:01:15.289 align:start position:0% someone could buy it and this makes really<00:01:12.960> no<00:01:13.380> sense<00:01:13.680> because<00:01:14.580> there<00:01:15.060> is<00:01:15.180> already 00:01:15.289 --> 00:01:15.299 align:start position:0% really no sense because there is already 00:01:15.299 --> 00:01:17.450 align:start position:0% really no sense because there is already a<00:01:15.540> lot<00:01:15.659> of<00:01:15.720> tooling<00:01:16.140> for<00:01:16.320> buying<00:01:16.680> assets<00:01:17.100> and 00:01:17.450 --> 00:01:17.460 align:start position:0% a lot of tooling for buying assets and 00:01:17.460 --> 00:01:20.030 align:start position:0% a lot of tooling for buying assets and that's<00:01:17.700> the<00:01:18.119> nft<00:01:18.479> space<00:01:18.900> in<00:01:19.439> the<00:01:19.500> nft<00:01:19.740> space 00:01:20.030 --> 00:01:20.040 align:start position:0% that's the nft space in the nft space 00:01:20.040 --> 00:01:22.190 align:start position:0% that's the nft space in the nft space you<00:01:20.220> can<00:01:20.340> just<00:01:20.520> buy<00:01:20.820> anything<00:01:21.119> from<00:01:21.479> openc<00:01:21.960> or 00:01:22.190 --> 00:01:22.200 align:start position:0% you can just buy anything from openc or 00:01:22.200 --> 00:01:24.469 align:start position:0% you can just buy anything from openc or variable<00:01:22.500> or<00:01:22.740> any<00:01:22.920> other<00:01:23.100> marketplaces<00:01:23.939> and 00:01:24.469 --> 00:01:24.479 align:start position:0% variable or any other marketplaces and 00:01:24.479 --> 00:01:26.390 align:start position:0% variable or any other marketplaces and we<00:01:24.659> don't<00:01:24.720> want<00:01:24.900> to<00:01:25.020> redeploy<00:01:25.500> that<00:01:25.740> for<00:01:26.100> for 00:01:26.390 --> 00:01:26.400 align:start position:0% we don't want to redeploy that for for 00:01:26.400 --> 00:01:28.490 align:start position:0% we don't want to redeploy that for for the<00:01:26.700> NF<00:01:27.000> for<00:01:27.299> the<00:01:27.420> ownable<00:01:27.720> contracts<00:01:28.259> that 00:01:28.490 --> 00:01:28.500 align:start position:0% the NF for the ownable contracts that 00:01:28.500 --> 00:01:31.010 align:start position:0% the NF for the ownable contracts that that<00:01:28.680> exists<00:01:29.159> so<00:01:29.700> the<00:01:29.880> idea<00:01:30.119> is<00:01:30.299> that<00:01:30.540> when<00:01:30.840> own 00:01:31.010 --> 00:01:31.020 align:start position:0% that exists so the idea is that when own 00:01:31.020 --> 00:01:34.010 align:start position:0% that exists so the idea is that when own ability<00:01:31.439> is<00:01:31.740> just<00:01:31.979> like<00:01:32.280> the<00:01:32.759> ownership<00:01:33.180> of<00:01:33.780> of 00:01:34.010 --> 00:01:34.020 align:start position:0% ability is just like the ownership of of 00:01:34.020 --> 00:01:36.289 align:start position:0% ability is just like the ownership of of a<00:01:34.259> contract<00:01:34.619> in<00:01:34.860> order<00:01:34.979> to<00:01:35.220> to<00:01:35.400> have<00:01:35.579> access<00:01:35.759> to 00:01:36.289 --> 00:01:36.299 align:start position:0% a contract in order to to have access to 00:01:36.299 --> 00:01:39.170 align:start position:0% a contract in order to to have access to it<00:01:36.600> to<00:01:37.020> some<00:01:37.259> admin<00:01:37.979> functions<00:01:38.460> well<00:01:39.000> you 00:01:39.170 --> 00:01:39.180 align:start position:0% it to some admin functions well you 00:01:39.180 --> 00:01:41.890 align:start position:0% it to some admin functions well you could<00:01:39.299> just<00:01:39.479> turn<00:01:39.659> that<00:01:39.840> into<00:01:40.020> an<00:01:40.200> erc721 00:01:41.890 --> 00:01:41.900 align:start position:0% could just turn that into an erc721 00:01:41.900 --> 00:01:44.450 align:start position:0% could just turn that into an erc721 and<00:01:42.900> and<00:01:43.200> this<00:01:43.500> is<00:01:43.560> how<00:01:43.799> you<00:01:43.979> would<00:01:44.100> do<00:01:44.280> it 00:01:44.450 --> 00:01:44.460 align:start position:0% and and this is how you would do it 00:01:44.460 --> 00:01:46.190 align:start position:0% and and this is how you would do it basically<00:01:44.880> you<00:01:45.119> can<00:01:45.240> very<00:01:45.479> simply<00:01:45.780> say<00:01:45.960> like 00:01:46.190 --> 00:01:46.200 align:start position:0% basically you can very simply say like 00:01:46.200 --> 00:01:49.969 align:start position:0% basically you can very simply say like hey<00:01:46.439> my<00:01:47.159> owner<00:01:47.520> is<00:01:47.939> just<00:01:48.240> the<00:01:48.900> owner<00:01:49.259> of<00:01:49.619> a 00:01:49.969 --> 00:01:49.979 align:start position:0% hey my owner is just the owner of a 00:01:49.979 --> 00:01:52.069 align:start position:0% hey my owner is just the owner of a specific<00:01:50.220> token<00:01:50.700> on<00:01:50.939> an<00:01:51.119> ownership<00:01:51.420> registry 00:01:52.069 --> 00:01:52.079 align:start position:0% specific token on an ownership registry 00:01:52.079 --> 00:01:54.770 align:start position:0% specific token on an ownership registry and<00:01:52.920> I<00:01:53.220> can<00:01:53.280> have<00:01:53.460> a<00:01:53.640> normal<00:01:53.759> owner<00:01:54.360> modifier 00:01:54.770 --> 00:01:54.780 align:start position:0% and I can have a normal owner modifier 00:01:54.780 --> 00:01:56.630 align:start position:0% and I can have a normal owner modifier for<00:01:55.079> that<00:01:55.259> and<00:01:55.740> when<00:01:55.860> I<00:01:56.040> want<00:01:56.100> to<00:01:56.220> transfer 00:01:56.630 --> 00:01:56.640 align:start position:0% for that and when I want to transfer 00:01:56.640 --> 00:01:58.190 align:start position:0% for that and when I want to transfer ownership<00:01:57.000> the<00:01:57.360> only<00:01:57.479> thing<00:01:57.659> I<00:01:57.780> will<00:01:57.899> have<00:01:58.079> to 00:01:58.190 --> 00:01:58.200 align:start position:0% ownership the only thing I will have to 00:01:58.200 --> 00:02:01.069 align:start position:0% ownership the only thing I will have to do<00:01:58.380> is<00:01:58.860> go<00:01:59.159> to<00:01:59.280> this<00:01:59.520> ownership<00:02:00.000> registry<00:02:00.600> and 00:02:01.069 --> 00:02:01.079 align:start position:0% do is go to this ownership registry and 00:02:01.079 --> 00:02:02.990 align:start position:0% do is go to this ownership registry and try<00:02:01.200> to<00:02:01.380> transfer<00:02:01.799> as<00:02:01.979> a<00:02:02.159> corresponding<00:02:02.640> token 00:02:02.990 --> 00:02:03.000 align:start position:0% try to transfer as a corresponding token 00:02:03.000 --> 00:02:05.990 align:start position:0% try to transfer as a corresponding token no<00:02:03.540> on<00:02:03.960> the<00:02:04.079> ownership<00:02:04.380> registry<00:02:05.040> you<00:02:05.820> would 00:02:05.990 --> 00:02:06.000 align:start position:0% no on the ownership registry you would 00:02:06.000 --> 00:02:07.429 align:start position:0% no on the ownership registry you would have<00:02:06.119> to<00:02:06.299> override<00:02:06.659> the<00:02:06.899> either<00:02:07.020> approval 00:02:07.429 --> 00:02:07.439 align:start position:0% have to override the either approval 00:02:07.439 --> 00:02:09.229 align:start position:0% have to override the either approval order<00:02:07.619> function<00:02:07.979> to<00:02:08.220> allow<00:02:08.520> that<00:02:08.700> but<00:02:08.880> that's 00:02:09.229 --> 00:02:09.239 align:start position:0% order function to allow that but that's 00:02:09.239 --> 00:02:11.570 align:start position:0% order function to allow that but that's very<00:02:09.780> easy<00:02:09.959> to<00:02:10.200> do<00:02:10.380> and<00:02:10.920> so<00:02:11.039> here<00:02:11.280> in<00:02:11.459> this 00:02:11.570 --> 00:02:11.580 align:start position:0% very easy to do and so here in this 00:02:11.580 --> 00:02:13.550 align:start position:0% very easy to do and so here in this example<00:02:11.879> you<00:02:12.060> have<00:02:12.180> a<00:02:12.300> basic<00:02:12.660> Factory<00:02:12.840> this<00:02:13.440> is 00:02:13.550 --> 00:02:13.560 align:start position:0% example you have a basic Factory this is 00:02:13.560 --> 00:02:14.990 align:start position:0% example you have a basic Factory this is actually<00:02:13.680> live<00:02:13.980> on<00:02:14.160> mainnet<00:02:14.640> and<00:02:14.760> when<00:02:14.879> you 00:02:14.990 --> 00:02:15.000 align:start position:0% actually live on mainnet and when you 00:02:15.000 --> 00:02:17.150 align:start position:0% actually live on mainnet and when you want<00:02:15.120> to<00:02:15.239> deploy<00:02:15.599> a<00:02:15.840> new<00:02:15.959> vesting<00:02:16.379> wallet<00:02:16.739> with 00:02:17.150 --> 00:02:17.160 align:start position:0% want to deploy a new vesting wallet with 00:02:17.160 --> 00:02:19.369 align:start position:0% want to deploy a new vesting wallet with a<00:02:17.459> beneficiary<00:02:17.940> for<00:02:18.180> it<00:02:18.360> well<00:02:18.840> here's<00:02:19.260> the 00:02:19.369 --> 00:02:19.379 align:start position:0% a beneficiary for it well here's the 00:02:19.379 --> 00:02:21.229 align:start position:0% a beneficiary for it well here's the beneficiary<00:02:19.800> it's<00:02:20.040> just<00:02:20.220> the<00:02:20.400> owner<00:02:20.760> of<00:02:21.060> the 00:02:21.229 --> 00:02:21.239 align:start position:0% beneficiary it's just the owner of the 00:02:21.239 --> 00:02:24.170 align:start position:0% beneficiary it's just the owner of the nft<00:02:21.540> on<00:02:22.200> this<00:02:22.379> Factory<00:02:22.620> and<00:02:23.280> when<00:02:23.400> I<00:02:23.580> deploy<00:02:23.879> a 00:02:24.170 --> 00:02:24.180 align:start position:0% nft on this Factory and when I deploy a 00:02:24.180 --> 00:02:26.270 align:start position:0% nft on this Factory and when I deploy a new<00:02:24.360> contractor<00:02:24.780> just<00:02:25.140> create<00:02:25.440> a<00:02:25.739> new<00:02:25.860> clone<00:02:26.099> I 00:02:26.270 --> 00:02:26.280 align:start position:0% new contractor just create a new clone I 00:02:26.280 --> 00:02:28.610 align:start position:0% new contractor just create a new clone I initialize<00:02:26.700> it<00:02:26.879> and<00:02:27.239> I<00:02:27.660> mean<00:02:27.780> the<00:02:27.959> token<00:02:28.260> and 00:02:28.610 --> 00:02:28.620 align:start position:0% initialize it and I mean the token and 00:02:28.620 --> 00:02:31.250 align:start position:0% initialize it and I mean the token and that's<00:02:28.800> the<00:02:29.040> equivalent<00:02:29.459> of<00:02:29.760> my<00:02:29.940> owner<00:02:30.360> if<00:02:30.959> the 00:02:31.250 --> 00:02:31.260 align:start position:0% that's the equivalent of my owner if the 00:02:31.260 --> 00:02:32.930 align:start position:0% that's the equivalent of my owner if the contracts<00:02:31.620> were<00:02:31.739> ownable<00:02:32.099> the<00:02:32.459> difference<00:02:32.700> is 00:02:32.930 --> 00:02:32.940 align:start position:0% contracts were ownable the difference is 00:02:32.940 --> 00:02:35.510 align:start position:0% contracts were ownable the difference is here<00:02:33.239> my<00:02:33.780> contract<00:02:34.140> show<00:02:34.319> up<00:02:34.500> on<00:02:34.620> openc<00:02:35.040> and<00:02:35.340> I 00:02:35.510 --> 00:02:35.520 align:start position:0% here my contract show up on openc and I 00:02:35.520 --> 00:02:37.430 align:start position:0% here my contract show up on openc and I can<00:02:35.700> basically<00:02:36.300> sell<00:02:36.599> it<00:02:36.780> or<00:02:36.900> transfer<00:02:37.260> it 00:02:37.430 --> 00:02:37.440 align:start position:0% can basically sell it or transfer it 00:02:37.440 --> 00:02:38.809 align:start position:0% can basically sell it or transfer it very<00:02:37.680> easily 00:02:38.809 --> 00:02:38.819 align:start position:0% very easily 00:02:38.819 --> 00:02:40.670 align:start position:0% very easily uh<00:02:39.420> if<00:02:39.599> you<00:02:39.720> want<00:02:39.780> to<00:02:39.900> go<00:02:39.959> a<00:02:40.080> bit<00:02:40.200> further<00:02:40.500> you 00:02:40.670 --> 00:02:40.680 align:start position:0% uh if you want to go a bit further you 00:02:40.680 --> 00:02:42.410 align:start position:0% uh if you want to go a bit further you can<00:02:40.860> even<00:02:40.980> have<00:02:41.220> like<00:02:41.400> a<00:02:41.580> universal<00:02:42.000> address 00:02:42.410 --> 00:02:42.420 align:start position:0% can even have like a universal address 00:02:42.420 --> 00:02:44.690 align:start position:0% can even have like a universal address ownership<00:02:43.080> registry<00:02:43.680> which<00:02:44.280> I<00:02:44.459> think<00:02:44.580> is 00:02:44.690 --> 00:02:44.700 align:start position:0% ownership registry which I think is 00:02:44.700 --> 00:02:46.490 align:start position:0% ownership registry which I think is pretty<00:02:44.940> fun<00:02:45.120> because<00:02:45.300> it<00:02:45.599> allows<00:02:46.080> you<00:02:46.140> to<00:02:46.319> get 00:02:46.490 --> 00:02:46.500 align:start position:0% pretty fun because it allows you to get 00:02:46.500 --> 00:02:49.309 align:start position:0% pretty fun because it allows you to get rid<00:02:46.739> of<00:02:46.980> the<00:02:47.580> minting<00:02:48.000> part<00:02:48.239> uh<00:02:48.900> by<00:02:49.140> just 00:02:49.309 --> 00:02:49.319 align:start position:0% rid of the minting part uh by just 00:02:49.319 --> 00:02:51.410 align:start position:0% rid of the minting part uh by just saying<00:02:49.560> that<00:02:49.680> hey<00:02:49.920> by<00:02:50.220> default<00:02:50.580> all<00:02:51.180> the 00:02:51.410 --> 00:02:51.420 align:start position:0% saying that hey by default all the 00:02:51.420 --> 00:02:53.750 align:start position:0% saying that hey by default all the tokens<00:02:51.780> are<00:02:52.019> already<00:02:52.319> minted<00:02:52.920> and<00:02:53.459> they<00:02:53.640> are 00:02:53.750 --> 00:02:53.760 align:start position:0% tokens are already minted and they are 00:02:53.760 --> 00:02:55.610 align:start position:0% tokens are already minted and they are owned<00:02:54.060> by<00:02:54.239> the<00:02:54.480> address<00:02:54.660> that<00:02:55.019> corresponds<00:02:55.500> to 00:02:55.610 --> 00:02:55.620 align:start position:0% owned by the address that corresponds to 00:02:55.620 --> 00:02:57.470 align:start position:0% owned by the address that corresponds to the<00:02:55.739> Token<00:02:56.040> ID<00:02:56.160> I<00:02:56.340> mean<00:02:56.459> all<00:02:56.700> the<00:02:56.879> token<00:02:57.300> ID 00:02:57.470 --> 00:02:57.480 align:start position:0% the Token ID I mean all the token ID 00:02:57.480 --> 00:02:59.449 align:start position:0% the Token ID I mean all the token ID that<00:02:57.840> matches<00:02:58.200> an<00:02:58.500> address<00:02:58.620> in<00:02:58.860> exactly<00:02:59.220> smart 00:02:59.449 --> 00:02:59.459 align:start position:0% that matches an address in exactly smart 00:02:59.459 --> 00:03:02.030 align:start position:0% that matches an address in exactly smart form<00:03:00.060> and<00:03:00.540> then<00:03:00.720> you<00:03:01.140> can<00:03:01.200> just<00:03:01.379> say<00:03:01.620> that<00:03:01.800> hey 00:03:02.030 --> 00:03:02.040 align:start position:0% form and then you can just say that hey 00:03:02.040 --> 00:03:03.530 align:start position:0% form and then you can just say that hey it's<00:03:02.220> not<00:03:02.400> possible<00:03:02.640> to<00:03:02.819> burn<00:03:03.000> them<00:03:03.180> you<00:03:03.360> would 00:03:03.530 --> 00:03:03.540 align:start position:0% it's not possible to burn them you would 00:03:03.540 --> 00:03:04.670 align:start position:0% it's not possible to burn them you would just<00:03:03.720> send<00:03:03.900> them<00:03:04.019> back<00:03:04.260> to<00:03:04.440> the<00:03:04.560> original 00:03:04.670 --> 00:03:04.680 align:start position:0% just send them back to the original 00:03:04.680 --> 00:03:07.009 align:start position:0% just send them back to the original owner<00:03:05.340> and<00:03:05.940> there<00:03:06.120> is<00:03:06.300> this<00:03:06.420> is<00:03:06.599> approval 00:03:07.009 --> 00:03:07.019 align:start position:0% owner and there is this is approval 00:03:07.019 --> 00:03:09.170 align:start position:0% owner and there is this is approval ownership<00:03:07.319> that<00:03:07.680> I'm<00:03:08.340> doing<00:03:08.459> some<00:03:08.700> fancy 00:03:09.170 --> 00:03:09.180 align:start position:0% ownership that I'm doing some fancy 00:03:09.180 --> 00:03:10.970 align:start position:0% ownership that I'm doing some fancy stuff<00:03:09.360> with<00:03:09.599> codes<00:03:09.959> but<00:03:10.319> you<00:03:10.500> don't<00:03:10.620> need<00:03:10.860> to 00:03:10.970 --> 00:03:10.980 align:start position:0% stuff with codes but you don't need to 00:03:10.980 --> 00:03:13.610 align:start position:0% stuff with codes but you don't need to care<00:03:11.099> about<00:03:11.280> that<00:03:11.519> and<00:03:11.700> and<00:03:12.060> this<00:03:12.300> can<00:03:12.540> just<00:03:13.080> be 00:03:13.610 --> 00:03:13.620 align:start position:0% care about that and and this can just be 00:03:13.620 --> 00:03:15.350 align:start position:0% care about that and and this can just be another<00:03:13.739> approach<00:03:14.280> I<00:03:14.519> think<00:03:14.640> it's<00:03:14.819> nice<00:03:15.060> and 00:03:15.350 --> 00:03:15.360 align:start position:0% another approach I think it's nice and 00:03:15.360 --> 00:03:17.210 align:start position:0% another approach I think it's nice and it<00:03:15.540> it<00:03:15.840> shows<00:03:16.200> creative<00:03:16.440> use<00:03:16.620> of<00:03:16.860> your<00:03:16.920> season 00:03:17.210 --> 00:03:17.220 align:start position:0% it it shows creative use of your season 00:03:17.220 --> 00:03:19.130 align:start position:0% it it shows creative use of your season 21s 00:03:19.130 --> 00:03:19.140 align:start position:0% 21s 00:03:19.140 --> 00:03:21.170 align:start position:0% 21s um<00:03:19.200> and<00:03:19.680> another<00:03:19.860> thing<00:03:20.280> we<00:03:20.459> use<00:03:20.580> is<00:03:20.819> that 00:03:21.170 --> 00:03:21.180 align:start position:0% um and another thing we use is that 00:03:21.180 --> 00:03:23.210 align:start position:0% um and another thing we use is that ownable<00:03:21.720> obviously<00:03:22.319> is<00:03:22.500> something<00:03:22.739> that<00:03:23.040> a 00:03:23.210 --> 00:03:23.220 align:start position:0% ownable obviously is something that a 00:03:23.220 --> 00:03:24.710 align:start position:0% ownable obviously is something that a lot<00:03:23.280> of<00:03:23.340> people<00:03:23.459> are<00:03:23.760> familiar<00:03:24.120> with<00:03:24.239> but<00:03:24.480> the 00:03:24.710 --> 00:03:24.720 align:start position:0% lot of people are familiar with but the 00:03:24.720 --> 00:03:27.290 align:start position:0% lot of people are familiar with but the granularity<00:03:25.319> is<00:03:25.560> really<00:03:25.980> bad<00:03:26.280> uh<00:03:27.060> sometimes 00:03:27.290 --> 00:03:27.300 align:start position:0% granularity is really bad uh sometimes 00:03:27.300 --> 00:03:28.550 align:start position:0% granularity is really bad uh sometimes you<00:03:27.480> have<00:03:27.659> different<00:03:27.720> admin<00:03:28.140> functions<00:03:28.440> in 00:03:28.550 --> 00:03:28.560 align:start position:0% you have different admin functions in 00:03:28.560 --> 00:03:29.570 align:start position:0% you have different admin functions in your<00:03:28.620> contract<00:03:28.920> that<00:03:29.099> you<00:03:29.220> want<00:03:29.340> to<00:03:29.459> have 00:03:29.570 --> 00:03:29.580 align:start position:0% your contract that you want to have 00:03:29.580 --> 00:03:31.610 align:start position:0% your contract that you want to have different<00:03:29.760> access<00:03:30.060> for<00:03:30.420> and<00:03:30.959> access<00:03:31.200> control 00:03:31.610 --> 00:03:31.620 align:start position:0% different access for and access control 00:03:31.620 --> 00:03:33.350 align:start position:0% different access for and access control does<00:03:32.040> that<00:03:32.280> pretty<00:03:32.459> well<00:03:32.640> access<00:03:32.879> control<00:03:33.120> is 00:03:33.350 --> 00:03:33.360 align:start position:0% does that pretty well access control is 00:03:33.360 --> 00:03:35.390 align:start position:0% does that pretty well access control is provided<00:03:33.720> by<00:03:33.900> open<00:03:34.019> Zeppelin<00:03:34.560> the<00:03:35.099> thing<00:03:35.280> is 00:03:35.390 --> 00:03:35.400 align:start position:0% provided by open Zeppelin the thing is 00:03:35.400 --> 00:03:38.390 align:start position:0% provided by open Zeppelin the thing is that<00:03:35.720> access<00:03:36.720> control<00:03:37.019> is<00:03:37.319> maybe<00:03:37.500> a<00:03:37.860> bit<00:03:38.040> more 00:03:38.390 --> 00:03:38.400 align:start position:0% that access control is maybe a bit more 00:03:38.400 --> 00:03:39.530 align:start position:0% that access control is maybe a bit more difficult<00:03:38.640> to<00:03:38.879> work<00:03:39.000> with<00:03:39.180> because<00:03:39.360> you 00:03:39.530 --> 00:03:39.540 align:start position:0% difficult to work with because you 00:03:39.540 --> 00:03:41.030 align:start position:0% difficult to work with because you cannot<00:03:39.780> transfer<00:03:40.200> a<00:03:40.379> world<00:03:40.560> you<00:03:40.799> need<00:03:40.920> to 00:03:41.030 --> 00:03:41.040 align:start position:0% cannot transfer a world you need to 00:03:41.040 --> 00:03:42.830 align:start position:0% cannot transfer a world you need to Grant<00:03:41.580> it<00:03:41.760> to<00:03:41.879> someone<00:03:42.060> else<00:03:42.299> and<00:03:42.599> then<00:03:42.659> either 00:03:42.830 --> 00:03:42.840 align:start position:0% Grant it to someone else and then either 00:03:42.840 --> 00:03:45.350 align:start position:0% Grant it to someone else and then either get<00:03:43.260> it<00:03:43.440> revoked<00:03:43.980> or<00:03:44.099> renounce<00:03:44.459> it 00:03:45.350 --> 00:03:45.360 align:start position:0% get it revoked or renounce it 00:03:45.360 --> 00:03:48.350 align:start position:0% get it revoked or renounce it and<00:03:45.959> so<00:03:46.200> it's<00:03:46.319> very<00:03:46.560> nice<00:03:46.799> for<00:03:47.040> some<00:03:47.280> users<00:03:47.640> but 00:03:48.350 --> 00:03:48.360 align:start position:0% and so it's very nice for some users but 00:03:48.360 --> 00:03:50.570 align:start position:0% and so it's very nice for some users but at<00:03:48.659> the<00:03:48.780> same<00:03:48.900> time<00:03:49.019> own<00:03:49.319> ability<00:03:49.739> has<00:03:50.340> some 00:03:50.570 --> 00:03:50.580 align:start position:0% at the same time own ability has some 00:03:50.580 --> 00:03:52.729 align:start position:0% at the same time own ability has some advantages<00:03:51.000> so<00:03:51.659> let's<00:03:51.900> just<00:03:52.140> combine<00:03:52.500> both 00:03:52.729 --> 00:03:52.739 align:start position:0% advantages so let's just combine both 00:03:52.739 --> 00:03:55.670 align:start position:0% advantages so let's just combine both let's<00:03:53.220> just<00:03:53.459> make<00:03:53.700> a<00:03:53.879> contract<00:03:54.239> that<00:03:54.659> as<00:03:55.500> an 00:03:55.670 --> 00:03:55.680 align:start position:0% let's just make a contract that as an 00:03:55.680 --> 00:03:58.009 align:start position:0% let's just make a contract that as an owner<00:03:56.040> and<00:03:56.580> the<00:03:56.819> owner<00:03:57.180> is<00:03:57.480> basically<00:03:57.840> the 00:03:58.009 --> 00:03:58.019 align:start position:0% owner and the owner is basically the 00:03:58.019 --> 00:03:59.809 align:start position:0% owner and the owner is basically the default<00:03:58.379> adminual<00:03:58.920> and<00:03:59.459> then<00:03:59.580> you<00:03:59.760> just 00:03:59.809 --> 00:03:59.819 align:start position:0% default adminual and then you just 00:03:59.819 --> 00:04:01.610 align:start position:0% default adminual and then you just cannot<00:04:00.120> Grant<00:04:00.540> or<00:04:00.659> revoke<00:04:01.019> this<00:04:01.319> default 00:04:01.610 --> 00:04:01.620 align:start position:0% cannot Grant or revoke this default 00:04:01.620 --> 00:04:03.710 align:start position:0% cannot Grant or revoke this default admin<00:04:01.980> order<00:04:02.159> because<00:04:02.400> that's<00:04:02.879> controlled<00:04:03.540> by 00:04:03.710 --> 00:04:03.720 align:start position:0% admin order because that's controlled by 00:04:03.720 --> 00:04:05.690 align:start position:0% admin order because that's controlled by the<00:04:03.900> ownership<00:04:04.200> part<00:04:04.500> but<00:04:05.040> the<00:04:05.220> owner<00:04:05.459> still 00:04:05.690 --> 00:04:05.700 align:start position:0% the ownership part but the owner still 00:04:05.700 --> 00:04:08.270 align:start position:0% the ownership part but the owner still is<00:04:05.879> the<00:04:06.060> admin<00:04:06.360> so<00:04:06.599> it<00:04:06.780> can<00:04:06.959> grant<00:04:07.799> any<00:04:08.040> other 00:04:08.270 --> 00:04:08.280 align:start position:0% is the admin so it can grant any other 00:04:08.280 --> 00:04:10.550 align:start position:0% is the admin so it can grant any other one<00:04:08.580> and<00:04:08.879> this<00:04:09.060> here<00:04:09.599> it's<00:04:09.840> ownable<00:04:10.200> but<00:04:10.439> it 00:04:10.550 --> 00:04:10.560 align:start position:0% one and this here it's ownable but it 00:04:10.560 --> 00:04:12.050 align:start position:0% one and this here it's ownable but it could<00:04:10.680> be<00:04:10.799> the<00:04:10.920> ownable<00:04:11.220> registry<00:04:11.640> official 00:04:12.050 --> 00:04:12.060 align:start position:0% could be the ownable registry official 00:04:12.060 --> 00:04:13.789 align:start position:0% could be the ownable registry official just<00:04:12.299> before<00:04:12.540> so<00:04:12.780> you<00:04:12.959> could<00:04:13.080> have<00:04:13.319> a<00:04:13.500> contract 00:04:13.789 --> 00:04:13.799 align:start position:0% just before so you could have a contract 00:04:13.799 --> 00:04:16.430 align:start position:0% just before so you could have a contract whereas<00:04:14.220> the<00:04:14.400> owner<00:04:14.640> is<00:04:14.879> the<00:04:15.120> nft<00:04:15.360> orders<00:04:15.900> and 00:04:16.430 --> 00:04:16.440 align:start position:0% whereas the owner is the nft orders and 00:04:16.440 --> 00:04:19.370 align:start position:0% whereas the owner is the nft orders and then<00:04:16.739> you<00:04:17.280> have<00:04:17.459> all<00:04:17.880> these<00:04:18.239> access<00:04:18.540> controls 00:04:19.370 --> 00:04:19.380 align:start position:0% then you have all these access controls 00:04:19.380 --> 00:04:21.590 align:start position:0% then you have all these access controls that<00:04:19.919> are<00:04:20.160> managed<00:04:20.519> in<00:04:20.699> that<00:04:20.880> way<00:04:21.000> or<00:04:21.239> you 00:04:21.590 --> 00:04:21.600 align:start position:0% that are managed in that way or you 00:04:21.600 --> 00:04:24.050 align:start position:0% that are managed in that way or you could<00:04:21.720> be<00:04:21.900> creative<00:04:22.199> and<00:04:22.440> use<00:04:22.560> ERC<00:04:22.979> 1155s<00:04:23.880> here 00:04:24.050 --> 00:04:24.060 align:start position:0% could be creative and use ERC 1155s here 00:04:24.060 --> 00:04:26.330 align:start position:0% could be creative and use ERC 1155s here and<00:04:24.300> so<00:04:24.780> yeah<00:04:24.900> that's<00:04:25.199> that's<00:04:25.500> just<00:04:25.860> some 00:04:26.330 --> 00:04:26.340 align:start position:0% and so yeah that's that's just some 00:04:26.340 --> 00:04:28.610 align:start position:0% and so yeah that's that's just some small<00:04:26.580> ideas<00:04:26.880> but<00:04:27.300> it's<00:04:27.840> not<00:04:28.020> very<00:04:28.259> complex 00:04:28.610 --> 00:04:28.620 align:start position:0% small ideas but it's not very complex 00:04:28.620 --> 00:04:29.930 align:start position:0% small ideas but it's not very complex good<00:04:28.860> I<00:04:29.040> think<00:04:29.160> everybody<00:04:29.400> can<00:04:29.759> understand 00:04:29.930 --> 00:04:29.940 align:start position:0% good I think everybody can understand 00:04:29.940 --> 00:04:31.370 align:start position:0% good I think everybody can understand that<00:04:30.180> but<00:04:30.360> the<00:04:30.540> point<00:04:30.720> I<00:04:30.900> really<00:04:31.020> want<00:04:31.139> to<00:04:31.259> make 00:04:31.370 --> 00:04:31.380 align:start position:0% that but the point I really want to make 00:04:31.380 --> 00:04:34.070 align:start position:0% that but the point I really want to make is<00:04:31.620> that<00:04:31.860> you<00:04:32.400> can<00:04:32.580> combine<00:04:33.120> tooling<00:04:33.780> together 00:04:34.070 --> 00:04:34.080 align:start position:0% is that you can combine tooling together 00:04:34.080 --> 00:04:36.290 align:start position:0% is that you can combine tooling together and<00:04:34.500> combine<00:04:34.860> contracts<00:04:35.460> to<00:04:35.820> make<00:04:35.940> sure<00:04:36.060> that 00:04:36.290 --> 00:04:36.300 align:start position:0% and combine contracts to make sure that 00:04:36.300 --> 00:04:37.670 align:start position:0% and combine contracts to make sure that everything<00:04:36.540> is<00:04:36.840> as 00:04:37.670 --> 00:04:37.680 align:start position:0% everything is as 00:04:37.680 --> 00:04:40.670 align:start position:0% everything is as basically<00:04:38.400> as<00:04:38.520> seamless<00:04:38.880> as<00:04:39.060> possible<00:04:39.780> the 00:04:40.670 --> 00:04:40.680 align:start position:0% basically as seamless as possible the 00:04:40.680 --> 00:04:42.110 align:start position:0% basically as seamless as possible the second<00:04:40.860> thing<00:04:41.160> I<00:04:41.340> want<00:04:41.520> to<00:04:41.639> to<00:04:41.820> present 00:04:42.110 --> 00:04:42.120 align:start position:0% second thing I want to to present 00:04:42.120 --> 00:04:44.749 align:start position:0% second thing I want to to present quickly<00:04:42.479> is<00:04:42.600> that<00:04:43.100> the<00:04:44.100> ecosystem<00:04:44.460> is 00:04:44.749 --> 00:04:44.759 align:start position:0% quickly is that the ecosystem is 00:04:44.759 --> 00:04:46.249 align:start position:0% quickly is that the ecosystem is constantly<00:04:45.060> changing<00:04:45.479> and<00:04:45.720> and<00:04:45.900> basically 00:04:46.249 --> 00:04:46.259 align:start position:0% constantly changing and and basically 00:04:46.259 --> 00:04:47.990 align:start position:0% constantly changing and and basically when<00:04:46.440> you<00:04:46.560> write<00:04:46.740> a<00:04:46.919> contract<00:04:47.280> I<00:04:47.580> mean<00:04:47.699> you<00:04:47.880> can 00:04:47.990 --> 00:04:48.000 align:start position:0% when you write a contract I mean you can 00:04:48.000 --> 00:04:49.550 align:start position:0% when you write a contract I mean you can make<00:04:48.120> your<00:04:48.300> contract<00:04:48.540> upgradable<00:04:49.080> but<00:04:49.320> even 00:04:49.550 --> 00:04:49.560 align:start position:0% make your contract upgradable but even 00:04:49.560 --> 00:04:51.770 align:start position:0% make your contract upgradable but even without<00:04:49.919> the<00:04:50.340> upgradability<00:04:50.880> part<00:04:51.180> you 00:04:51.770 --> 00:04:51.780 align:start position:0% without the upgradability part you 00:04:51.780 --> 00:04:54.590 align:start position:0% without the upgradability part you really<00:04:51.960> need<00:04:52.139> to<00:04:52.560> care<00:04:52.979> about<00:04:53.400> what<00:04:54.300> is<00:04:54.479> going 00:04:54.590 --> 00:04:54.600 align:start position:0% really need to care about what is going 00:04:54.600 --> 00:04:56.090 align:start position:0% really need to care about what is going to<00:04:54.660> be<00:04:54.780> the<00:04:54.900> life<00:04:55.080> cycle<00:04:55.259> of<00:04:55.500> my<00:04:55.620> contract<00:04:55.860> and 00:04:56.090 --> 00:04:56.100 align:start position:0% to be the life cycle of my contract and 00:04:56.100 --> 00:04:58.189 align:start position:0% to be the life cycle of my contract and are<00:04:56.580> there<00:04:56.820> Small<00:04:57.060> Tricks<00:04:57.540> that<00:04:57.780> I<00:04:57.900> could<00:04:58.020> use 00:04:58.189 --> 00:04:58.199 align:start position:0% are there Small Tricks that I could use 00:04:58.199 --> 00:05:01.070 align:start position:0% are there Small Tricks that I could use that<00:04:58.979> will<00:04:59.100> make<00:04:59.340> my<00:04:59.639> users<00:05:00.060> life<00:05:00.240> better<00:05:00.600> in 00:05:01.070 --> 00:05:01.080 align:start position:0% that will make my users life better in 00:05:01.080 --> 00:05:03.110 align:start position:0% that will make my users life better in the<00:05:01.199> long<00:05:01.320> run<00:05:01.500> and<00:05:02.100> that's<00:05:02.220> for<00:05:02.460> the<00:05:02.699> users 00:05:03.110 --> 00:05:03.120 align:start position:0% the long run and that's for the users 00:05:03.120 --> 00:05:05.330 align:start position:0% the long run and that's for the users but<00:05:03.300> also<00:05:03.600> for<00:05:03.720> like<00:05:03.900> the<00:05:04.080> UI<00:05:04.440> designers<00:05:04.979> or 00:05:05.330 --> 00:05:05.340 align:start position:0% but also for like the UI designers or 00:05:05.340 --> 00:05:07.670 align:start position:0% but also for like the UI designers or and<00:05:05.639> basically<00:05:06.000> anybody<00:05:06.300> in<00:05:06.479> this<00:05:06.660> space<00:05:06.840> so 00:05:07.670 --> 00:05:07.680 align:start position:0% and basically anybody in this space so 00:05:07.680 --> 00:05:10.010 align:start position:0% and basically anybody in this space so these<00:05:08.400> are<00:05:08.520> just<00:05:08.759> two<00:05:09.120> small<00:05:09.300> pieces<00:05:09.660> of<00:05:09.840> code 00:05:10.010 --> 00:05:10.020 align:start position:0% these are just two small pieces of code 00:05:10.020 --> 00:05:12.590 align:start position:0% these are just two small pieces of code like<00:05:10.320> 0.4s<00:05:11.040> and<00:05:11.100> five<00:05:11.220> that<00:05:11.580> I<00:05:12.000> came<00:05:12.240> up<00:05:12.419> with 00:05:12.590 --> 00:05:12.600 align:start position:0% like 0.4s and five that I came up with 00:05:12.600 --> 00:05:14.570 align:start position:0% like 0.4s and five that I came up with very<00:05:12.960> recently<00:05:13.440> and<00:05:13.680> I<00:05:13.919> think<00:05:14.040> that's<00:05:14.340> that's 00:05:14.570 --> 00:05:14.580 align:start position:0% very recently and I think that's that's 00:05:14.580 --> 00:05:16.969 align:start position:0% very recently and I think that's that's things<00:05:14.880> that<00:05:15.180> are<00:05:15.540> are<00:05:15.780> interesting<00:05:16.199> because 00:05:16.969 --> 00:05:16.979 align:start position:0% things that are are interesting because 00:05:16.979 --> 00:05:18.770 align:start position:0% things that are are interesting because we<00:05:17.340> never<00:05:17.520> expect<00:05:17.759> a<00:05:18.060> hard<00:05:18.180> Fork<00:05:18.540> to<00:05:18.660> happen 00:05:18.770 --> 00:05:18.780 align:start position:0% we never expect a hard Fork to happen 00:05:18.780 --> 00:05:21.110 align:start position:0% we never expect a hard Fork to happen until<00:05:19.500> it<00:05:19.860> actually<00:05:19.979> does<00:05:20.280> and<00:05:20.520> people<00:05:20.699> start 00:05:21.110 --> 00:05:21.120 align:start position:0% until it actually does and people start 00:05:21.120 --> 00:05:22.790 align:start position:0% until it actually does and people start trying<00:05:21.360> to<00:05:21.540> do<00:05:21.720> a<00:05:21.840> proof<00:05:22.080> of<00:05:22.139> work<00:05:22.380> blockchain 00:05:22.790 --> 00:05:22.800 align:start position:0% trying to do a proof of work blockchain 00:05:22.800 --> 00:05:25.370 align:start position:0% trying to do a proof of work blockchain and<00:05:23.460> then<00:05:23.580> the<00:05:23.820> bridges<00:05:24.240> that<00:05:24.900> are<00:05:25.080> on<00:05:25.259> this 00:05:25.370 --> 00:05:25.380 align:start position:0% and then the bridges that are on this 00:05:25.380 --> 00:05:27.770 align:start position:0% and then the bridges that are on this proof<00:05:25.680> of<00:05:25.740> work<00:05:25.979> chain<00:05:26.280> starts<00:05:26.699> breaking<00:05:27.180> and 00:05:27.770 --> 00:05:27.780 align:start position:0% proof of work chain starts breaking and 00:05:27.780 --> 00:05:29.029 align:start position:0% proof of work chain starts breaking and that's<00:05:27.960> a<00:05:28.199> pain 00:05:29.029 --> 00:05:29.039 align:start position:0% that's a pain 00:05:29.039 --> 00:05:31.370 align:start position:0% that's a pain so<00:05:29.699> you<00:05:30.000> could<00:05:30.120> imagine<00:05:30.300> having<00:05:30.720> this<00:05:31.199> very 00:05:31.370 --> 00:05:31.380 align:start position:0% so you could imagine having this very 00:05:31.380 --> 00:05:32.990 align:start position:0% so you could imagine having this very small<00:05:31.560> piece<00:05:31.919> of<00:05:31.979> code<00:05:32.100> here<00:05:32.460> that<00:05:32.699> basically 00:05:32.990 --> 00:05:33.000 align:start position:0% small piece of code here that basically 00:05:33.000 --> 00:05:35.749 align:start position:0% small piece of code here that basically takes<00:05:33.240> no<00:05:33.539> size<00:05:33.780> on<00:05:34.199> on<00:05:34.320> chain<00:05:34.800> that<00:05:35.580> just 00:05:35.749 --> 00:05:35.759 align:start position:0% takes no size on on chain that just 00:05:35.759 --> 00:05:38.270 align:start position:0% takes no size on on chain that just gives<00:05:36.000> you<00:05:36.120> two<00:05:36.360> modifier<00:05:36.960> that<00:05:37.800> verifies 00:05:38.270 --> 00:05:38.280 align:start position:0% gives you two modifier that verifies 00:05:38.280 --> 00:05:40.969 align:start position:0% gives you two modifier that verifies that<00:05:38.580> the<00:05:38.820> chain<00:05:39.000> ID<00:05:39.440> that<00:05:40.440> you're<00:05:40.560> currently 00:05:40.969 --> 00:05:40.979 align:start position:0% that the chain ID that you're currently 00:05:40.979 --> 00:05:44.270 align:start position:0% that the chain ID that you're currently using<00:05:41.580> is<00:05:41.940> the<00:05:42.120> one<00:05:42.300> that<00:05:42.600> was<00:05:42.979> registered<00:05:43.979> in 00:05:44.270 --> 00:05:44.280 align:start position:0% using is the one that was registered in 00:05:44.280 --> 00:05:46.189 align:start position:0% using is the one that was registered in immutable<00:05:44.759> storage<00:05:45.060> when<00:05:45.600> the<00:05:45.780> contract<00:05:46.020> was 00:05:46.189 --> 00:05:46.199 align:start position:0% immutable storage when the contract was 00:05:46.199 --> 00:05:48.469 align:start position:0% immutable storage when the contract was deployed<00:05:46.680> and<00:05:47.160> then<00:05:47.280> you<00:05:47.400> could<00:05:47.580> do<00:05:47.759> that<00:05:48.000> to 00:05:48.469 --> 00:05:48.479 align:start position:0% deployed and then you could do that to 00:05:48.479 --> 00:05:50.510 align:start position:0% deployed and then you could do that to create<00:05:48.900> some<00:05:49.199> kind<00:05:49.380> of<00:05:49.500> bridge<00:05:49.740> where 00:05:50.510 --> 00:05:50.520 align:start position:0% create some kind of bridge where 00:05:50.520 --> 00:05:52.730 align:start position:0% create some kind of bridge where actually<00:05:50.820> most<00:05:51.300> of<00:05:51.600> the<00:05:51.780> function<00:05:52.080> remains 00:05:52.730 --> 00:05:52.740 align:start position:0% actually most of the function remains 00:05:52.740 --> 00:05:54.950 align:start position:0% actually most of the function remains completely<00:05:53.100> trustless<00:05:53.699> with<00:05:54.539> this<00:05:54.780> only 00:05:54.950 --> 00:05:54.960 align:start position:0% completely trustless with this only 00:05:54.960 --> 00:05:57.830 align:start position:0% completely trustless with this only initial<00:05:55.380> chain<00:05:55.620> modifier<00:05:56.220> but<00:05:57.060> if<00:05:57.419> for<00:05:57.660> any 00:05:57.830 --> 00:05:57.840 align:start position:0% initial chain modifier but if for any 00:05:57.840 --> 00:06:00.770 align:start position:0% initial chain modifier but if for any reason<00:05:58.160> uh<00:05:59.160> there<00:05:59.520> were<00:05:59.699> to<00:05:59.820> be<00:05:59.940> hard<00:06:00.120> Fork<00:06:00.539> the 00:06:00.770 --> 00:06:00.780 align:start position:0% reason uh there were to be hard Fork the 00:06:00.780 --> 00:06:02.629 align:start position:0% reason uh there were to be hard Fork the version<00:06:00.960> of<00:06:01.139> the<00:06:01.320> bridge<00:06:01.440> that<00:06:01.800> is<00:06:02.100> on<00:06:02.460> the 00:06:02.629 --> 00:06:02.639 align:start position:0% version of the bridge that is on the 00:06:02.639 --> 00:06:05.330 align:start position:0% version of the bridge that is on the chain<00:06:03.180> that<00:06:03.479> changes<00:06:03.900> the<00:06:04.080> chain<00:06:04.259> ID<00:06:04.560> then<00:06:05.100> all 00:06:05.330 --> 00:06:05.340 align:start position:0% chain that changes the chain ID then all 00:06:05.340 --> 00:06:06.770 align:start position:0% chain that changes the chain ID then all those<00:06:05.520> would<00:06:05.759> be<00:06:05.880> automatically<00:06:06.240> disabled 00:06:06.770 --> 00:06:06.780 align:start position:0% those would be automatically disabled 00:06:06.780 --> 00:06:09.290 align:start position:0% those would be automatically disabled and<00:06:07.139> you<00:06:07.259> get<00:06:07.500> into<00:06:07.620> recovery<00:06:08.100> mode<00:06:08.400> when<00:06:09.000> some 00:06:09.290 --> 00:06:09.300 align:start position:0% and you get into recovery mode when some 00:06:09.300 --> 00:06:10.790 align:start position:0% and you get into recovery mode when some like<00:06:09.479> multisig<00:06:10.080> would<00:06:10.199> be<00:06:10.320> able<00:06:10.440> to<00:06:10.500> take<00:06:10.620> over 00:06:10.790 --> 00:06:10.800 align:start position:0% like multisig would be able to take over 00:06:10.800 --> 00:06:12.469 align:start position:0% like multisig would be able to take over and<00:06:11.039> this<00:06:11.160> multi-seek<00:06:11.639> is<00:06:11.759> not<00:06:11.880> a<00:06:12.000> threat<00:06:12.300> for 00:06:12.469 --> 00:06:12.479 align:start position:0% and this multi-seek is not a threat for 00:06:12.479 --> 00:06:14.510 align:start position:0% and this multi-seek is not a threat for the<00:06:12.600> user<00:06:12.900> on<00:06:13.080> the<00:06:13.199> legitimate<00:06:13.620> chain<00:06:13.919> because 00:06:14.510 --> 00:06:14.520 align:start position:0% the user on the legitimate chain because 00:06:14.520 --> 00:06:17.210 align:start position:0% the user on the legitimate chain because because<00:06:15.000> of<00:06:15.419> this<00:06:15.660> only<00:06:16.020> fork<00:06:16.500> chain<00:06:16.620> like 00:06:17.210 --> 00:06:17.220 align:start position:0% because of this only fork chain like 00:06:17.220 --> 00:06:19.249 align:start position:0% because of this only fork chain like this<00:06:17.460> admin<00:06:17.880> cannot<00:06:18.240> do<00:06:18.360> anything<00:06:18.600> nasty<00:06:19.139> to 00:06:19.249 --> 00:06:19.259 align:start position:0% this admin cannot do anything nasty to 00:06:19.259 --> 00:06:21.529 align:start position:0% this admin cannot do anything nasty to your<00:06:19.440> users<00:06:19.740> but<00:06:20.460> that's<00:06:20.699> that's<00:06:20.940> a<00:06:21.180> mixing 00:06:21.529 --> 00:06:21.539 align:start position:0% your users but that's that's a mixing 00:06:21.539 --> 00:06:23.330 align:start position:0% your users but that's that's a mixing point<00:06:21.720> that<00:06:21.960> would<00:06:22.199> have<00:06:22.380> saved<00:06:22.740> some<00:06:22.919> pain<00:06:23.100> I 00:06:23.330 --> 00:06:23.340 align:start position:0% point that would have saved some pain I 00:06:23.340 --> 00:06:24.830 align:start position:0% point that would have saved some pain I mean<00:06:23.400> it<00:06:23.699> wasn't<00:06:23.880> the<00:06:24.120> proof<00:06:24.300> of<00:06:24.419> work<00:06:24.600> chain 00:06:24.830 --> 00:06:24.840 align:start position:0% mean it wasn't the proof of work chain 00:06:24.840 --> 00:06:27.110 align:start position:0% mean it wasn't the proof of work chain so<00:06:25.080> maybe<00:06:25.319> we<00:06:25.620> don't<00:06:25.740> care<00:06:25.979> a<00:06:26.160> lot<00:06:26.340> but<00:06:26.580> who 00:06:27.110 --> 00:06:27.120 align:start position:0% so maybe we don't care a lot but who 00:06:27.120 --> 00:06:28.070 align:start position:0% so maybe we don't care a lot but who knows<00:06:27.300> maybe<00:06:27.479> there<00:06:27.720> will<00:06:27.900> be<00:06:27.960> more 00:06:28.070 --> 00:06:28.080 align:start position:0% knows maybe there will be more 00:06:28.080 --> 00:06:29.570 align:start position:0% knows maybe there will be more legitimate<00:06:28.560> Forks<00:06:28.800> at<00:06:28.860> some<00:06:28.979> point<00:06:29.400> in 00:06:29.570 --> 00:06:29.580 align:start position:0% legitimate Forks at some point in 00:06:29.580 --> 00:06:31.490 align:start position:0% legitimate Forks at some point in ethereum's<00:06:30.120> life<00:06:30.300> cycle 00:06:31.490 --> 00:06:31.500 align:start position:0% ethereum's life cycle 00:06:31.500 --> 00:06:33.230 align:start position:0% ethereum's life cycle and<00:06:32.039> another<00:06:32.160> one<00:06:32.460> is<00:06:32.639> that<00:06:32.819> that's<00:06:33.000> something 00:06:33.230 --> 00:06:33.240 align:start position:0% and another one is that that's something 00:06:33.240 --> 00:06:34.850 align:start position:0% and another one is that that's something we<00:06:33.479> provide<00:06:33.780> as<00:06:33.900> open<00:06:34.080> the<00:06:34.319> screen<00:06:34.440> and<00:06:34.680> that's 00:06:34.850 --> 00:06:34.860 align:start position:0% we provide as open the screen and that's 00:06:34.860 --> 00:06:36.890 align:start position:0% we provide as open the screen and that's what<00:06:35.220> we<00:06:35.340> call<00:06:35.460> the<00:06:35.639> multi-code<00:06:36.180> contract<00:06:36.600> and 00:06:36.890 --> 00:06:36.900 align:start position:0% what we call the multi-code contract and 00:06:36.900 --> 00:06:38.930 align:start position:0% what we call the multi-code contract and that's<00:06:37.080> very<00:06:37.440> simple<00:06:37.680> it's<00:06:37.979> just<00:06:38.340> one 00:06:38.930 --> 00:06:38.940 align:start position:0% that's very simple it's just one 00:06:38.940 --> 00:06:41.809 align:start position:0% that's very simple it's just one endpoint<00:06:39.360> one<00:06:39.539> small<00:06:39.780> functions<00:06:40.440> that<00:06:41.340> allows 00:06:41.809 --> 00:06:41.819 align:start position:0% endpoint one small functions that allows 00:06:41.819 --> 00:06:44.270 align:start position:0% endpoint one small functions that allows you<00:06:41.880> to<00:06:42.180> delegate<00:06:42.720> to<00:06:42.900> yourself<00:06:43.139> with<00:06:43.560> an<00:06:44.100> area 00:06:44.270 --> 00:06:44.280 align:start position:0% you to delegate to yourself with an area 00:06:44.280 --> 00:06:46.490 align:start position:0% you to delegate to yourself with an area of<00:06:44.580> data<00:06:44.940> and<00:06:45.360> that's<00:06:45.479> very<00:06:45.780> easy<00:06:46.020> for<00:06:46.259> you<00:06:46.380> to 00:06:46.490 --> 00:06:46.500 align:start position:0% of data and that's very easy for you to 00:06:46.500 --> 00:06:48.110 align:start position:0% of data and that's very easy for you to integrate<00:06:46.860> into<00:06:46.979> any<00:06:47.220> of<00:06:47.400> your<00:06:47.580> contract<00:06:47.940> and 00:06:48.110 --> 00:06:48.120 align:start position:0% integrate into any of your contract and 00:06:48.120 --> 00:06:49.490 align:start position:0% integrate into any of your contract and I<00:06:48.240> don't<00:06:48.419> think<00:06:48.600> there<00:06:48.780> is<00:06:48.960> there<00:06:49.319> is<00:06:49.440> any 00:06:49.490 --> 00:06:49.500 align:start position:0% I don't think there is there is any 00:06:49.500 --> 00:06:51.950 align:start position:0% I don't think there is there is any reason<00:06:49.740> not<00:06:50.039> to<00:06:50.280> do<00:06:50.460> it<00:06:50.639> and<00:06:51.479> the<00:06:51.780> way<00:06:51.840> it's 00:06:51.950 --> 00:06:51.960 align:start position:0% reason not to do it and the way it's 00:06:51.960 --> 00:06:53.570 align:start position:0% reason not to do it and the way it's being<00:06:52.199> done<00:06:52.319> is<00:06:52.560> earlier<00:06:52.919> we<00:06:53.160> saw<00:06:53.400> this 00:06:53.570 --> 00:06:53.580 align:start position:0% being done is earlier we saw this 00:06:53.580 --> 00:06:55.430 align:start position:0% being done is earlier we saw this example<00:06:53.940> here<00:06:54.240> and<00:06:54.840> here<00:06:55.080> you<00:06:55.199> have<00:06:55.319> this 00:06:55.430 --> 00:06:55.440 align:start position:0% example here and here you have this 00:06:55.440 --> 00:06:56.749 align:start position:0% example here and here you have this multiple<00:06:55.860> that<00:06:56.100> maybe<00:06:56.220> you<00:06:56.400> didn't<00:06:56.520> see 00:06:56.749 --> 00:06:56.759 align:start position:0% multiple that maybe you didn't see 00:06:56.759 --> 00:06:58.430 align:start position:0% multiple that maybe you didn't see because<00:06:56.940> it's<00:06:57.180> red<00:06:57.539> on<00:06:57.780> black<00:06:57.960> so<00:06:58.139> it's<00:06:58.319> not 00:06:58.430 --> 00:06:58.440 align:start position:0% because it's red on black so it's not 00:06:58.440 --> 00:07:00.350 align:start position:0% because it's red on black so it's not really<00:06:58.560> visible<00:06:58.919> but<00:06:59.460> what<00:06:59.639> it<00:06:59.880> allows<00:07:00.180> you<00:07:00.240> to 00:07:00.350 --> 00:07:00.360 align:start position:0% really visible but what it allows you to 00:07:00.360 --> 00:07:01.790 align:start position:0% really visible but what it allows you to do<00:07:00.479> is<00:07:00.600> when<00:07:00.840> you<00:07:00.960> went<00:07:01.080> to<00:07:01.259> create<00:07:01.440> a<00:07:01.740> new 00:07:01.790 --> 00:07:01.800 align:start position:0% do is when you went to create a new 00:07:01.800 --> 00:07:03.890 align:start position:0% do is when you went to create a new vesting<00:07:02.340> for<00:07:02.520> one<00:07:02.759> of<00:07:02.880> your<00:07:03.000> investors<00:07:03.479> or 00:07:03.890 --> 00:07:03.900 align:start position:0% vesting for one of your investors or 00:07:03.900 --> 00:07:05.990 align:start position:0% vesting for one of your investors or someone<00:07:04.259> when<00:07:04.919> if<00:07:05.220> you<00:07:05.340> have<00:07:05.460> 10<00:07:05.699> or<00:07:05.880> 20 00:07:05.990 --> 00:07:06.000 align:start position:0% someone when if you have 10 or 20 00:07:06.000 --> 00:07:07.550 align:start position:0% someone when if you have 10 or 20 investors<00:07:06.479> maybe<00:07:06.660> you<00:07:06.840> don't<00:07:06.960> want<00:07:07.139> to<00:07:07.259> do<00:07:07.319> 20 00:07:07.550 --> 00:07:07.560 align:start position:0% investors maybe you don't want to do 20 00:07:07.560 --> 00:07:10.370 align:start position:0% investors maybe you don't want to do 20 transaction<00:07:08.039> that<00:07:08.819> do<00:07:09.000> 20<00:07:09.240> calls<00:07:09.780> to<00:07:10.020> this<00:07:10.199> new 00:07:10.370 --> 00:07:10.380 align:start position:0% transaction that do 20 calls to this new 00:07:10.380 --> 00:07:12.710 align:start position:0% transaction that do 20 calls to this new wasting<00:07:10.800> function<00:07:11.100> so<00:07:11.699> what<00:07:11.880> you<00:07:12.000> do<00:07:12.180> is<00:07:12.539> just 00:07:12.710 --> 00:07:12.720 align:start position:0% wasting function so what you do is just 00:07:12.720 --> 00:07:15.110 align:start position:0% wasting function so what you do is just that<00:07:13.139> you<00:07:13.380> encode<00:07:14.160> like<00:07:14.400> you<00:07:14.580> have<00:07:14.699> a<00:07:14.819> map<00:07:14.940> of 00:07:15.110 --> 00:07:15.120 align:start position:0% that you encode like you have a map of 00:07:15.120 --> 00:07:17.570 align:start position:0% that you encode like you have a map of entry<00:07:15.539> and<00:07:15.960> you<00:07:16.080> record<00:07:16.259> the<00:07:16.620> function<00:07:16.860> using 00:07:17.570 --> 00:07:17.580 align:start position:0% entry and you record the function using 00:07:17.580 --> 00:07:20.450 align:start position:0% entry and you record the function using like<00:07:18.180> e<00:07:18.660> server.js<00:07:19.199> or<00:07:19.440> F3<00:07:19.740> of<00:07:19.919> whatever<00:07:20.099> you 00:07:20.450 --> 00:07:20.460 align:start position:0% like e server.js or F3 of whatever you 00:07:20.460 --> 00:07:22.249 align:start position:0% like e server.js or F3 of whatever you like<00:07:20.639> and<00:07:21.180> then<00:07:21.300> you<00:07:21.479> just<00:07:21.660> have<00:07:21.780> to<00:07:21.900> do<00:07:22.080> a 00:07:22.249 --> 00:07:22.259 align:start position:0% like and then you just have to do a 00:07:22.259 --> 00:07:23.809 align:start position:0% like and then you just have to do a single<00:07:22.500> call<00:07:22.620> so<00:07:22.919> there<00:07:23.099> is<00:07:23.280> a<00:07:23.580> single 00:07:23.809 --> 00:07:23.819 align:start position:0% single call so there is a single 00:07:23.819 --> 00:07:25.249 align:start position:0% single call so there is a single transaction<00:07:24.180> here<00:07:24.539> that<00:07:24.720> you<00:07:24.840> have<00:07:24.960> to<00:07:25.080> wait 00:07:25.249 --> 00:07:25.259 align:start position:0% transaction here that you have to wait 00:07:25.259 --> 00:07:28.390 align:start position:0% transaction here that you have to wait for<00:07:25.500> in<00:07:25.919> order<00:07:26.099> to<00:07:26.340> do<00:07:26.639> it<00:07:26.819> will<00:07:27.000> basically 00:07:28.390 --> 00:07:28.400 align:start position:0% for in order to do it will basically 00:07:28.400 --> 00:07:31.850 align:start position:0% for in order to do it will basically run<00:07:29.400> like<00:07:29.699> all<00:07:30.180> these<00:07:30.539> these<00:07:31.020> operations<00:07:31.199> so 00:07:31.850 --> 00:07:31.860 align:start position:0% run like all these these operations so 00:07:31.860 --> 00:07:33.710 align:start position:0% run like all these these operations so deploy<00:07:32.400> Trend<00:07:32.759> investing<00:07:33.120> at<00:07:33.180> a<00:07:33.300> time<00:07:33.419> or<00:07:33.539> you 00:07:33.710 --> 00:07:33.720 align:start position:0% deploy Trend investing at a time or you 00:07:33.720 --> 00:07:35.689 align:start position:0% deploy Trend investing at a time or you could<00:07:33.900> do<00:07:34.139> an<00:07:34.380> approve<00:07:34.800> and<00:07:35.099> some<00:07:35.460> something 00:07:35.689 --> 00:07:35.699 align:start position:0% could do an approve and some something 00:07:35.699 --> 00:07:38.450 align:start position:0% could do an approve and some something else<00:07:36.060> or<00:07:36.900> you<00:07:37.080> could<00:07:37.259> batch<00:07:37.800> transactions 00:07:38.450 --> 00:07:38.460 align:start position:0% else or you could batch transactions 00:07:38.460 --> 00:07:40.370 align:start position:0% else or you could batch transactions together<00:07:38.580> like<00:07:39.240> you<00:07:39.479> don't<00:07:39.599> need<00:07:39.780> to<00:07:39.960> wait<00:07:40.080> for 00:07:40.370 --> 00:07:40.380 align:start position:0% together like you don't need to wait for 00:07:40.380 --> 00:07:41.990 align:start position:0% together like you don't need to wait for Icon<00:07:40.620> abstraction<00:07:41.160> to<00:07:41.400> batch<00:07:41.580> transaction 00:07:41.990 --> 00:07:42.000 align:start position:0% Icon abstraction to batch transaction 00:07:42.000 --> 00:07:44.089 align:start position:0% Icon abstraction to batch transaction you<00:07:42.300> can<00:07:42.479> already<00:07:42.660> do<00:07:42.960> it<00:07:43.139> at<00:07:43.620> the<00:07:43.800> contract 00:07:44.089 --> 00:07:44.099 align:start position:0% you can already do it at the contract 00:07:44.099 --> 00:07:46.430 align:start position:0% you can already do it at the contract level<00:07:44.280> I<00:07:44.520> mean<00:07:45.120> providing<00:07:45.960> that<00:07:46.139> the<00:07:46.259> target 00:07:46.430 --> 00:07:46.440 align:start position:0% level I mean providing that the target 00:07:46.440 --> 00:07:47.930 align:start position:0% level I mean providing that the target is<00:07:46.740> the<00:07:46.860> same<00:07:47.039> contract<00:07:47.340> for<00:07:47.520> all<00:07:47.759> the 00:07:47.930 --> 00:07:47.940 align:start position:0% is the same contract for all the 00:07:47.940 --> 00:07:50.029 align:start position:0% is the same contract for all the subcodes<00:07:48.419> and<00:07:49.139> that's<00:07:49.380> as<00:07:49.620> simple<00:07:49.860> as 00:07:50.029 --> 00:07:50.039 align:start position:0% subcodes and that's as simple as 00:07:50.039 --> 00:07:52.790 align:start position:0% subcodes and that's as simple as including<00:07:50.460> that<00:07:50.639> so<00:07:51.000> yeah<00:07:51.419> it<00:07:52.139> keep<00:07:52.500> in<00:07:52.680> mind 00:07:52.790 --> 00:07:52.800 align:start position:0% including that so yeah it keep in mind 00:07:52.800 --> 00:07:54.350 align:start position:0% including that so yeah it keep in mind that<00:07:53.039> there<00:07:53.280> are<00:07:53.460> always<00:07:53.580> this<00:07:53.819> nice<00:07:53.940> tricks 00:07:54.350 --> 00:07:54.360 align:start position:0% that there are always this nice tricks 00:07:54.360 --> 00:07:55.969 align:start position:0% that there are always this nice tricks that<00:07:54.479> could<00:07:54.599> possibly<00:07:54.960> help<00:07:55.080> your<00:07:55.259> users<00:07:55.740> down 00:07:55.969 --> 00:07:55.979 align:start position:0% that could possibly help your users down 00:07:55.979 --> 00:07:58.309 align:start position:0% that could possibly help your users down the<00:07:56.160> line<00:07:56.280> and<00:07:57.240> I<00:07:57.419> think<00:07:57.539> it's<00:07:57.720> it's<00:07:57.960> important 00:07:58.309 --> 00:07:58.319 align:start position:0% the line and I think it's it's important 00:07:58.319 --> 00:07:59.390 align:start position:0% the line and I think it's it's important to<00:07:58.500> have<00:07:58.620> that<00:07:58.740> in<00:07:58.860> mind<00:07:58.979> when<00:07:59.220> building 00:07:59.390 --> 00:07:59.400 align:start position:0% to have that in mind when building 00:07:59.400 --> 00:08:02.270 align:start position:0% to have that in mind when building contracts<00:08:00.000> and<00:08:00.300> try<00:08:00.599> to<00:08:00.780> be<00:08:00.900> creative 00:08:02.270 --> 00:08:02.280 align:start position:0% contracts and try to be creative 00:08:02.280 --> 00:08:03.500 align:start position:0% contracts and try to be creative that's<00:08:02.819> it 00:08:03.500 --> 00:08:03.510 align:start position:0% that's it 00:08:03.510 --> 00:08:11.330 align:start position:0% that's it [Applause] 00:08:11.330 --> 00:08:11.340 align:start position:0% [Applause] 00:08:11.340 --> 00:08:12.830 align:start position:0% [Applause] yeah<00:08:11.759> so<00:08:11.880> I'm<00:08:12.060> going<00:08:12.240> to<00:08:12.300> repeat<00:08:12.419> the<00:08:12.720> question 00:08:12.830 --> 00:08:12.840 align:start position:0% yeah so I'm going to repeat the question 00:08:12.840 --> 00:08:15.350 align:start position:0% yeah so I'm going to repeat the question for<00:08:13.139> for<00:08:13.380> the<00:08:13.560> stream<00:08:13.740> and<00:08:14.039> the<00:08:14.400> live<00:08:14.520> and<00:08:14.819> uh 00:08:15.350 --> 00:08:15.360 align:start position:0% for for the stream and the live and uh 00:08:15.360 --> 00:08:16.969 align:start position:0% for for the stream and the live and uh the<00:08:15.599> question<00:08:15.780> was<00:08:15.960> about<00:08:16.139> like<00:08:16.440> can<00:08:16.800> access 00:08:16.969 --> 00:08:16.979 align:start position:0% the question was about like can access 00:08:16.979 --> 00:08:19.550 align:start position:0% the question was about like can access control<00:08:17.280> be<00:08:17.580> used<00:08:17.759> for<00:08:17.940> smart<00:08:18.180> toilets<00:08:19.139> is 00:08:19.550 --> 00:08:19.560 align:start position:0% control be used for smart toilets is 00:08:19.560 --> 00:08:22.189 align:start position:0% control be used for smart toilets is that<00:08:19.680> that's<00:08:19.919> it<00:08:20.160> basically<00:08:20.639> I<00:08:20.879> think<00:08:21.120> uh<00:08:21.840> well 00:08:22.189 --> 00:08:22.199 align:start position:0% that that's it basically I think uh well 00:08:22.199 --> 00:08:24.170 align:start position:0% that that's it basically I think uh well uh<00:08:22.919> it<00:08:23.160> really<00:08:23.280> depends<00:08:23.580> what's<00:08:23.819> kind<00:08:24.060> of 00:08:24.170 --> 00:08:24.180 align:start position:0% uh it really depends what's kind of 00:08:24.180 --> 00:08:26.330 align:start position:0% uh it really depends what's kind of Smartwatch<00:08:24.720> you<00:08:24.900> want<00:08:25.020> to<00:08:25.139> build 00:08:26.330 --> 00:08:26.340 align:start position:0% Smartwatch you want to build 00:08:26.340 --> 00:08:27.589 align:start position:0% Smartwatch you want to build um<00:08:26.460> there<00:08:26.759> are<00:08:26.940> different<00:08:27.060> kind<00:08:27.300> of<00:08:27.479> smart 00:08:27.589 --> 00:08:27.599 align:start position:0% um there are different kind of smart 00:08:27.599 --> 00:08:29.629 align:start position:0% um there are different kind of smart wallets<00:08:28.080> if<00:08:28.319> it's<00:08:28.500> just<00:08:28.680> something<00:08:28.860> that<00:08:29.099> QRS 00:08:29.629 --> 00:08:29.639 align:start position:0% wallets if it's just something that QRS 00:08:29.639 --> 00:08:32.630 align:start position:0% wallets if it's just something that QRS sole<00:08:30.240> owner<00:08:30.539> of<00:08:30.720> I'm<00:08:31.500> not<00:08:31.680> sure<00:08:31.919> it<00:08:32.159> brings 00:08:32.630 --> 00:08:32.640 align:start position:0% sole owner of I'm not sure it brings 00:08:32.640 --> 00:08:35.329 align:start position:0% sole owner of I'm not sure it brings anything<00:08:32.880> new<00:08:33.180> to<00:08:33.360> the<00:08:33.539> table<00:08:33.860> uh<00:08:34.860> but<00:08:35.099> if<00:08:35.219> you 00:08:35.329 --> 00:08:35.339 align:start position:0% anything new to the table uh but if you 00:08:35.339 --> 00:08:37.190 align:start position:0% anything new to the table uh but if you are<00:08:35.459> doing<00:08:35.580> a<00:08:35.820> multi-sig<00:08:36.360> maybe<00:08:36.659> it<00:08:36.899> will<00:08:37.020> be 00:08:37.190 --> 00:08:37.200 align:start position:0% are doing a multi-sig maybe it will be 00:08:37.200 --> 00:08:39.230 align:start position:0% are doing a multi-sig maybe it will be relevant<00:08:37.560> I<00:08:37.800> mean<00:08:37.919> my<00:08:38.279> opinion<00:08:38.580> is<00:08:38.760> that<00:08:38.940> a 00:08:39.230 --> 00:08:39.240 align:start position:0% relevant I mean my opinion is that a 00:08:39.240 --> 00:08:41.690 align:start position:0% relevant I mean my opinion is that a time<00:08:39.419> lock<00:08:39.599> for<00:08:40.020> example<00:08:40.260> is<00:08:40.919> a<00:08:41.219> kind<00:08:41.399> of<00:08:41.520> North 00:08:41.690 --> 00:08:41.700 align:start position:0% time lock for example is a kind of North 00:08:41.700 --> 00:08:43.730 align:start position:0% time lock for example is a kind of North wallet<00:08:42.180> because<00:08:42.419> it's<00:08:42.719> just<00:08:42.899> someone<00:08:43.440> that 00:08:43.730 --> 00:08:43.740 align:start position:0% wallet because it's just someone that 00:08:43.740 --> 00:08:45.949 align:start position:0% wallet because it's just someone that will<00:08:43.860> manage<00:08:44.279> asset<00:08:44.700> and<00:08:44.820> do<00:08:45.000> operation<00:08:45.420> with 00:08:45.949 --> 00:08:45.959 align:start position:0% will manage asset and do operation with 00:08:45.959 --> 00:08:48.530 align:start position:0% will manage asset and do operation with three<00:08:46.200> specific<00:08:46.560> rules<00:08:46.980> and<00:08:47.760> in<00:08:48.000> the<00:08:48.180> open<00:08:48.240> zip 00:08:48.530 --> 00:08:48.540 align:start position:0% three specific rules and in the open zip 00:08:48.540 --> 00:08:50.690 align:start position:0% three specific rules and in the open zip time<00:08:49.019> lock<00:08:49.200> we<00:08:49.500> use<00:08:49.740> Access<00:08:50.040> Control<00:08:50.399> to 00:08:50.690 --> 00:08:50.700 align:start position:0% time lock we use Access Control to 00:08:50.700 --> 00:08:52.850 align:start position:0% time lock we use Access Control to separate<00:08:51.120> the<00:08:51.300> role<00:08:51.600> of<00:08:51.779> the<00:08:52.019> proposers<00:08:52.560> from 00:08:52.850 --> 00:08:52.860 align:start position:0% separate the role of the proposers from 00:08:52.860 --> 00:08:55.070 align:start position:0% separate the role of the proposers from the<00:08:53.040> executors<00:08:53.700> from<00:08:54.240> the<00:08:54.420> admin<00:08:54.779> that<00:08:54.959> may 00:08:55.070 --> 00:08:55.080 align:start position:0% the executors from the admin that may 00:08:55.080 --> 00:08:57.710 align:start position:0% the executors from the admin that may have<00:08:55.260> the<00:08:55.380> right<00:08:55.560> to<00:08:55.740> cancel<00:08:56.040> potentially<00:08:56.880> so 00:08:57.710 --> 00:08:57.720 align:start position:0% have the right to cancel potentially so 00:08:57.720 --> 00:08:59.329 align:start position:0% have the right to cancel potentially so yes<00:08:57.959> if<00:08:58.200> you<00:08:58.260> are<00:08:58.380> building<00:08:58.560> a<00:08:58.740> multi-cig<00:08:59.220> and 00:08:59.329 --> 00:08:59.339 align:start position:0% yes if you are building a multi-cig and 00:08:59.339 --> 00:09:00.710 align:start position:0% yes if you are building a multi-cig and you<00:08:59.459> want<00:08:59.580> to<00:08:59.640> have<00:08:59.760> different<00:09:00.000> privileged 00:09:00.710 --> 00:09:00.720 align:start position:0% you want to have different privileged 00:09:00.720 --> 00:09:03.410 align:start position:0% you want to have different privileged access<00:09:00.959> maybe<00:09:01.260> I<00:09:01.800> think<00:09:01.920> an<00:09:02.040> overseer<00:09:02.640> that<00:09:03.300> is 00:09:03.410 --> 00:09:03.420 align:start position:0% access maybe I think an overseer that is 00:09:03.420 --> 00:09:06.110 align:start position:0% access maybe I think an overseer that is able<00:09:03.720> to<00:09:03.839> recover<00:09:04.200> in<00:09:04.500> case<00:09:04.740> of<00:09:04.920> of<00:09:05.160> issue 00:09:06.110 --> 00:09:06.120 align:start position:0% able to recover in case of of issue 00:09:06.120 --> 00:09:09.050 align:start position:0% able to recover in case of of issue having<00:09:06.839> signers<00:09:07.440> having<00:09:07.680> proposers<00:09:08.399> that 00:09:09.050 --> 00:09:09.060 align:start position:0% having signers having proposers that 00:09:09.060 --> 00:09:10.310 align:start position:0% having signers having proposers that basically<00:09:09.420> you're<00:09:09.600> turning<00:09:09.959> your<00:09:10.140> emergency 00:09:10.310 --> 00:09:10.320 align:start position:0% basically you're turning your emergency 00:09:10.320 --> 00:09:12.530 align:start position:0% basically you're turning your emergency into<00:09:10.860> some<00:09:11.220> governance<00:09:11.700> mechanism<00:09:12.180> which 00:09:12.530 --> 00:09:12.540 align:start position:0% into some governance mechanism which 00:09:12.540 --> 00:09:14.329 align:start position:0% into some governance mechanism which which<00:09:12.779> it<00:09:13.140> basically<00:09:13.440> is<00:09:13.620> what<00:09:13.920> time<00:09:14.040> will<00:09:14.160> see 00:09:14.329 --> 00:09:14.339 align:start position:0% which it basically is what time will see 00:09:14.339 --> 00:09:15.769 align:start position:0% which it basically is what time will see is<00:09:14.459> a<00:09:14.519> governance<00:09:14.820> mechanism<00:09:15.120> so<00:09:15.480> yes<00:09:15.600> you 00:09:15.769 --> 00:09:15.779 align:start position:0% is a governance mechanism so yes you 00:09:15.779 --> 00:09:19.370 align:start position:0% is a governance mechanism so yes you could<00:09:15.899> use<00:09:15.959> Access<00:09:16.140> Control 00:09:19.370 --> 00:09:19.380 align:start position:0% 00:09:19.380 --> 00:09:22.490 align:start position:0% uh<00:09:20.100> hey<00:09:20.580> uh<00:09:21.000> in<00:09:21.180> an<00:09:21.360> example<00:09:21.660> with<00:09:21.959> a<00:09:22.080> multico 00:09:22.490 --> 00:09:22.500 align:start position:0% uh hey uh in an example with a multico 00:09:22.500 --> 00:09:25.910 align:start position:0% uh hey uh in an example with a multico that<00:09:22.740> you've<00:09:22.980> shown<00:09:23.220> we<00:09:24.120> are<00:09:24.779> deploying<00:09:25.680> the 00:09:25.910 --> 00:09:25.920 align:start position:0% that you've shown we are deploying the 00:09:25.920 --> 00:09:28.190 align:start position:0% that you've shown we are deploying the same<00:09:26.160> method<00:09:26.580> like<00:09:27.120> a<00:09:27.300> byte<00:09:27.660> code<00:09:27.779> for<00:09:28.080> this 00:09:28.190 --> 00:09:28.200 align:start position:0% same method like a byte code for this 00:09:28.200 --> 00:09:30.170 align:start position:0% same method like a byte code for this method<00:09:28.620> in<00:09:28.920> every<00:09:29.040> contract 00:09:30.170 --> 00:09:30.180 align:start position:0% method in every contract 00:09:30.180 --> 00:09:32.509 align:start position:0% method in every contract wouldn't<00:09:30.600> it<00:09:30.779> be<00:09:30.959> better<00:09:31.260> if<00:09:31.680> we<00:09:31.920> have<00:09:32.339> it 00:09:32.509 --> 00:09:32.519 align:start position:0% wouldn't it be better if we have it 00:09:32.519 --> 00:09:34.730 align:start position:0% wouldn't it be better if we have it deployed<00:09:33.000> separately 00:09:34.730 --> 00:09:34.740 align:start position:0% deployed separately 00:09:34.740 --> 00:09:37.070 align:start position:0% deployed separately yes<00:09:35.279> it<00:09:35.580> would<00:09:35.760> but<00:09:36.120> it's<00:09:36.300> not<00:09:36.480> possible<00:09:36.779> right 00:09:37.070 --> 00:09:37.080 align:start position:0% yes it would but it's not possible right 00:09:37.080 --> 00:09:42.290 align:start position:0% yes it would but it's not possible right now<00:09:37.260> so<00:09:37.620> like<00:09:38.040> if<00:09:38.399> we<00:09:38.580> had<00:09:38.880> a<00:09:39.180> EIP<00:09:40.040> 3074<00:09:41.040> live<00:09:41.459> we 00:09:42.290 --> 00:09:42.300 align:start position:0% now so like if we had a EIP 3074 live we 00:09:42.300 --> 00:09:44.509 align:start position:0% now so like if we had a EIP 3074 live we could<00:09:42.480> just<00:09:42.660> have<00:09:43.019> this<00:09:43.320> make<00:09:43.500> use<00:09:43.800> this<00:09:44.040> OS 00:09:44.509 --> 00:09:44.519 align:start position:0% could just have this make use this OS 00:09:44.519 --> 00:09:46.430 align:start position:0% could just have this make use this OS and<00:09:44.700> oscore<00:09:45.120> mechanism<00:09:45.540> to<00:09:45.899> do<00:09:46.019> batching 00:09:46.430 --> 00:09:46.440 align:start position:0% and oscore mechanism to do batching 00:09:46.440 --> 00:09:48.769 align:start position:0% and oscore mechanism to do batching transaction<00:09:46.920> and<00:09:47.880> and<00:09:48.120> you<00:09:48.360> would<00:09:48.480> not<00:09:48.660> have 00:09:48.769 --> 00:09:48.779 align:start position:0% transaction and and you would not have 00:09:48.779 --> 00:09:50.990 align:start position:0% transaction and and you would not have to<00:09:48.899> include<00:09:49.200> that<00:09:49.320> in<00:09:49.560> your<00:09:49.680> contract<00:09:50.100> the 00:09:50.990 --> 00:09:51.000 align:start position:0% to include that in your contract the 00:09:51.000 --> 00:09:52.730 align:start position:0% to include that in your contract the thing<00:09:51.240> is<00:09:51.360> that<00:09:51.600> this<00:09:51.720> is<00:09:51.899> not<00:09:52.019> available<00:09:52.260> now 00:09:52.730 --> 00:09:52.740 align:start position:0% thing is that this is not available now 00:09:52.740 --> 00:09:54.949 align:start position:0% thing is that this is not available now it<00:09:53.160> will<00:09:53.279> not<00:09:53.459> be<00:09:53.640> available<00:09:53.820> until<00:09:54.240> at<00:09:54.779> least 00:09:54.949 --> 00:09:54.959 align:start position:0% it will not be available until at least 00:09:54.959 --> 00:09:57.130 align:start position:0% it will not be available until at least Shanghai<00:09:55.500> and<00:09:55.740> maybe<00:09:55.980> later 00:09:57.130 --> 00:09:57.140 align:start position:0% Shanghai and maybe later 00:09:57.140 --> 00:10:01.009 align:start position:0% Shanghai and maybe later so<00:09:58.140> I<00:09:58.740> think<00:09:58.860> the<00:09:59.519> bytecode<00:10:00.060> increase<00:10:00.360> is<00:10:00.779> is 00:10:01.009 --> 00:10:01.019 align:start position:0% so I think the bytecode increase is is 00:10:01.019 --> 00:10:02.990 align:start position:0% so I think the bytecode increase is is really<00:10:01.320> small<00:10:01.560> compared<00:10:02.040> to<00:10:02.160> the<00:10:02.519> the<00:10:02.760> value 00:10:02.990 --> 00:10:03.000 align:start position:0% really small compared to the the value 00:10:03.000 --> 00:10:06.050 align:start position:0% really small compared to the the value that<00:10:03.300> is<00:10:03.420> added<00:10:03.660> to<00:10:03.779> your<00:10:03.959> contract<00:10:04.260> right<00:10:04.500> now 00:10:06.050 --> 00:10:06.060 align:start position:0% that is added to your contract right now 00:10:06.060 --> 00:10:08.090 align:start position:0% that is added to your contract right now but<00:10:06.720> yeah<00:10:06.959> in<00:10:07.140> the<00:10:07.260> long<00:10:07.380> run<00:10:07.500> hopefully<00:10:07.920> we 00:10:08.090 --> 00:10:08.100 align:start position:0% but yeah in the long run hopefully we 00:10:08.100 --> 00:10:10.370 align:start position:0% but yeah in the long run hopefully we would<00:10:08.279> have<00:10:08.519> already<00:10:08.880> supported<00:10:09.600> at<00:10:10.019> the<00:10:10.140> at 00:10:10.370 --> 00:10:10.380 align:start position:0% would have already supported at the at 00:10:10.380 --> 00:10:13.130 align:start position:0% would have already supported at the at the<00:10:10.560> execution<00:10:10.980> level<00:10:11.279> later 00:10:13.130 --> 00:10:13.140 align:start position:0% the execution level later 00:10:13.140 --> 00:10:17.030 align:start position:0% the execution level later hey<00:10:13.800> uh<00:10:14.519> great<00:10:14.880> talk<00:10:15.060> by<00:10:15.720> the<00:10:15.839> way<00:10:15.899> uh<00:10:16.440> in<00:10:16.800> the 00:10:17.030 --> 00:10:17.040 align:start position:0% hey uh great talk by the way uh in the 00:10:17.040 --> 00:10:20.269 align:start position:0% hey uh great talk by the way uh in the ownable<00:10:17.700> ERC<00:10:18.660> 721<00:10:19.260> part<00:10:19.680> you<00:10:19.980> were<00:10:20.100> talking 00:10:20.269 --> 00:10:20.279 align:start position:0% ownable ERC 721 part you were talking 00:10:20.279 --> 00:10:23.030 align:start position:0% ownable ERC 721 part you were talking about<00:10:20.459> how<00:10:21.060> you<00:10:21.660> could<00:10:21.720> basically<00:10:22.080> ditch<00:10:22.680> the 00:10:23.030 --> 00:10:23.040 align:start position:0% about how you could basically ditch the 00:10:23.040 --> 00:10:25.910 align:start position:0% about how you could basically ditch the ownable<00:10:23.519> the<00:10:24.180> ownable<00:10:24.600> library<00:10:24.839> right<00:10:25.260> what 00:10:25.910 --> 00:10:25.920 align:start position:0% ownable the ownable library right what 00:10:25.920 --> 00:10:28.130 align:start position:0% ownable the ownable library right what what<00:10:26.220> advantage<00:10:26.940> I<00:10:27.300> I<00:10:27.540> kind<00:10:27.720> of<00:10:27.839> missed<00:10:28.080> the 00:10:28.130 --> 00:10:28.140 align:start position:0% what advantage I I kind of missed the 00:10:28.140 --> 00:10:30.650 align:start position:0% what advantage I I kind of missed the point<00:10:28.320> of<00:10:28.500> like<00:10:28.680> what's<00:10:28.980> the<00:10:29.220> advantage<00:10:29.760> of 00:10:30.650 --> 00:10:30.660 align:start position:0% point of like what's the advantage of 00:10:30.660 --> 00:10:32.570 align:start position:0% point of like what's the advantage of implementing<00:10:31.260> the<00:10:31.500> ownership 00:10:32.570 --> 00:10:32.580 align:start position:0% implementing the ownership 00:10:32.580 --> 00:10:35.990 align:start position:0% implementing the ownership inside<00:10:33.300> the<00:10:33.740> erc721<00:10:34.740> logic<00:10:35.339> instead<00:10:35.700> of<00:10:35.820> just 00:10:35.990 --> 00:10:36.000 align:start position:0% inside the erc721 logic instead of just 00:10:36.000 --> 00:10:37.970 align:start position:0% inside the erc721 logic instead of just bringing<00:10:36.300> ownable<00:10:36.660> is<00:10:36.899> it<00:10:37.080> just<00:10:37.200> like<00:10:37.440> byte 00:10:37.970 --> 00:10:37.980 align:start position:0% bringing ownable is it just like byte 00:10:37.980 --> 00:10:39.769 align:start position:0% bringing ownable is it just like byte code<00:10:38.100> size<00:10:38.519> or<00:10:39.120> is<00:10:39.240> there<00:10:39.420> any<00:10:39.540> other 00:10:39.769 --> 00:10:39.779 align:start position:0% code size or is there any other 00:10:39.779 --> 00:10:41.990 align:start position:0% code size or is there any other advantage<00:10:40.440> that<00:10:40.680> I'm<00:10:40.800> missing<00:10:41.040> no<00:10:41.459> the<00:10:41.760> weird 00:10:41.990 --> 00:10:42.000 align:start position:0% advantage that I'm missing no the weird 00:10:42.000 --> 00:10:44.269 align:start position:0% advantage that I'm missing no the weird advantages<00:10:42.480> in<00:10:42.899> in<00:10:43.140> composability<00:10:43.860> so 00:10:44.269 --> 00:10:44.279 align:start position:0% advantages in in composability so 00:10:44.279 --> 00:10:46.310 align:start position:0% advantages in in composability so examples<00:10:44.760> for<00:10:44.940> example<00:10:45.180> your<00:10:45.600> your<00:10:45.839> own<00:10:46.079> Apple 00:10:46.310 --> 00:10:46.320 align:start position:0% examples for example your your own Apple 00:10:46.320 --> 00:10:49.009 align:start position:0% examples for example your your own Apple contract<00:10:46.920> it<00:10:47.399> could<00:10:47.640> be<00:10:48.120> tied<00:10:48.420> to<00:10:48.660> assets 00:10:49.009 --> 00:10:49.019 align:start position:0% contract it could be tied to assets 00:10:49.019 --> 00:10:51.290 align:start position:0% contract it could be tied to assets maybe<00:10:49.260> you<00:10:49.620> would<00:10:49.800> want<00:10:49.920> to<00:10:50.100> consider<00:10:50.519> that<00:10:50.880> as 00:10:51.290 --> 00:10:51.300 align:start position:0% maybe you would want to consider that as 00:10:51.300 --> 00:10:53.750 align:start position:0% maybe you would want to consider that as a<00:10:51.600> class<00:10:51.720> of<00:10:52.019> its<00:10:52.320> own<00:10:52.380> that<00:10:52.800> you<00:10:52.920> would 00:10:53.750 --> 00:10:53.760 align:start position:0% a class of its own that you would 00:10:53.760 --> 00:10:56.750 align:start position:0% a class of its own that you would be<00:10:54.240> able<00:10:54.480> to<00:10:54.660> land<00:10:54.899> against<00:10:55.260> collateral<00:10:55.920> or 00:10:56.750 --> 00:10:56.760 align:start position:0% be able to land against collateral or 00:10:56.760 --> 00:10:59.509 align:start position:0% be able to land against collateral or maybe<00:10:56.880> it's<00:10:57.180> uh<00:10:57.480> maybe<00:10:57.899> it's<00:10:58.140> like<00:10:58.440> a<00:10:58.680> vessing 00:10:59.509 --> 00:10:59.519 align:start position:0% maybe it's uh maybe it's like a vessing 00:10:59.519 --> 00:11:01.970 align:start position:0% maybe it's uh maybe it's like a vessing wallet<00:10:59.760> that<00:10:59.940> is<00:11:00.120> basically<00:11:00.420> a<00:11:00.660> future<00:11:00.980> uh 00:11:01.970 --> 00:11:01.980 align:start position:0% wallet that is basically a future uh 00:11:01.980 --> 00:11:04.130 align:start position:0% wallet that is basically a future uh financial<00:11:02.640> future<00:11:03.060> that<00:11:03.660> you<00:11:03.720> want<00:11:03.839> to<00:11:03.959> sell 00:11:04.130 --> 00:11:04.140 align:start position:0% financial future that you want to sell 00:11:04.140 --> 00:11:06.829 align:start position:0% financial future that you want to sell on<00:11:04.380> unisa<00:11:04.800> on<00:11:05.100> openc<00:11:05.700> uh<00:11:06.360> right<00:11:06.540> now<00:11:06.660> you 00:11:06.829 --> 00:11:06.839 align:start position:0% on unisa on openc uh right now you 00:11:06.839 --> 00:11:08.509 align:start position:0% on unisa on openc uh right now you cannot<00:11:07.079> sell<00:11:07.200> a<00:11:07.380> non-able<00:11:07.680> contract<00:11:08.040> on<00:11:08.220> openc 00:11:08.509 --> 00:11:08.519 align:start position:0% cannot sell a non-able contract on openc 00:11:08.519 --> 00:11:11.030 align:start position:0% cannot sell a non-able contract on openc but<00:11:08.760> you<00:11:08.880> can<00:11:09.000> sell<00:11:09.180> an<00:11:09.360> nft<00:11:09.660> so<00:11:10.320> the<00:11:10.560> way<00:11:10.800> here 00:11:11.030 --> 00:11:11.040 align:start position:0% but you can sell an nft so the way here 00:11:11.040 --> 00:11:14.329 align:start position:0% but you can sell an nft so the way here is<00:11:11.399> to<00:11:11.820> make<00:11:12.300> sure<00:11:12.480> that<00:11:12.839> your<00:11:13.440> contract<00:11:13.860> is 00:11:14.329 --> 00:11:14.339 align:start position:0% is to make sure that your contract is 00:11:14.339 --> 00:11:16.130 align:start position:0% is to make sure that your contract is compatible<00:11:14.880> with<00:11:15.180> all<00:11:15.360> the<00:11:15.540> tooling<00:11:15.959> that 00:11:16.130 --> 00:11:16.140 align:start position:0% compatible with all the tooling that 00:11:16.140 --> 00:11:19.370 align:start position:0% compatible with all the tooling that exists<00:11:16.740> out<00:11:16.860> there<00:11:17.100> openc<00:11:17.700> and<00:11:18.300> others<00:11:18.839> also 00:11:19.370 --> 00:11:19.380 align:start position:0% exists out there openc and others also 00:11:19.380 --> 00:11:22.009 align:start position:0% exists out there openc and others also just<00:11:19.860> being<00:11:20.100> able<00:11:20.339> to<00:11:20.640> see<00:11:20.820> the<00:11:21.060> ownership<00:11:21.420> in 00:11:22.009 --> 00:11:22.019 align:start position:0% just being able to see the ownership in 00:11:22.019 --> 00:11:24.590 align:start position:0% just being able to see the ownership in your<00:11:22.200> zirion<00:11:22.860> or<00:11:23.220> any<00:11:23.820> palette<00:11:24.240> you'll<00:11:24.480> use 00:11:24.590 --> 00:11:24.600 align:start position:0% your zirion or any palette you'll use 00:11:24.600 --> 00:11:27.110 align:start position:0% your zirion or any palette you'll use that's<00:11:24.959> also<00:11:25.260> something<00:11:25.440> nice 00:11:27.110 --> 00:11:27.120 align:start position:0% that's also something nice 00:11:27.120 --> 00:11:29.930 align:start position:0% that's also something nice thanks 00:11:29.930 --> 00:11:29.940 align:start position:0% 00:11:29.940 --> 00:11:32.660 align:start position:0% thank<00:11:30.420> you