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:16.570 align:start position:0% [Music] 00:00:16.570 --> 00:00:16.580 align:start position:0% 00:00:16.580 --> 00:00:19.189 align:start position:0% and<00:00:17.580> they<00:00:17.699> are<00:00:17.880> going<00:00:18.119> to<00:00:18.359> share<00:00:18.960> about 00:00:19.189 --> 00:00:19.199 align:start position:0% and they are going to share about 00:00:19.199 --> 00:00:21.710 align:start position:0% and they are going to share about azerite<00:00:19.980> obstructions<00:00:20.760> a<00:00:20.939> case<00:00:21.119> for<00:00:21.420> a<00:00:21.600> smart 00:00:21.710 --> 00:00:21.720 align:start position:0% azerite obstructions a case for a smart 00:00:21.720 --> 00:00:23.510 align:start position:0% azerite obstructions a case for a smart contract<00:00:22.199> wallets 00:00:23.510 --> 00:00:23.520 align:start position:0% contract wallets 00:00:23.520 --> 00:00:26.660 align:start position:0% contract wallets go<00:00:23.939> ahead 00:00:26.660 --> 00:00:26.670 align:start position:0% 00:00:26.670 --> 00:00:31.250 align:start position:0% [Applause] 00:00:31.250 --> 00:00:31.260 align:start position:0% 00:00:31.260 --> 00:00:33.290 align:start position:0% thanks<00:00:31.859> hey<00:00:32.279> everybody 00:00:33.290 --> 00:00:33.300 align:start position:0% thanks hey everybody 00:00:33.300 --> 00:00:36.049 align:start position:0% thanks hey everybody um<00:00:33.360> my<00:00:33.840> name<00:00:33.899> is<00:00:34.020> Joseph<00:00:34.140> this<00:00:34.559> is<00:00:34.680> neim<00:00:35.100> we<00:00:35.940> are 00:00:36.049 --> 00:00:36.059 align:start position:0% um my name is Joseph this is neim we are 00:00:36.059 --> 00:00:38.569 align:start position:0% um my name is Joseph this is neim we are from<00:00:36.239> Project<00:00:36.600> called<00:00:36.960> pawn<00:00:37.380> and<00:00:38.280> today<00:00:38.399> we 00:00:38.569 --> 00:00:38.579 align:start position:0% from Project called pawn and today we 00:00:38.579 --> 00:00:40.490 align:start position:0% from Project called pawn and today we are<00:00:38.700> not<00:00:38.820> going<00:00:38.940> to<00:00:39.059> talk<00:00:39.239> about<00:00:39.420> Pawn<00:00:39.719> but 00:00:40.490 --> 00:00:40.500 align:start position:0% are not going to talk about Pawn but 00:00:40.500 --> 00:00:41.990 align:start position:0% are not going to talk about Pawn but about<00:00:40.620> something<00:00:40.920> that<00:00:41.160> we<00:00:41.340> developed<00:00:41.700> for 00:00:41.990 --> 00:00:42.000 align:start position:0% about something that we developed for 00:00:42.000 --> 00:00:44.090 align:start position:0% about something that we developed for the<00:00:42.180> community<00:00:42.360> uh<00:00:43.079> because<00:00:43.260> it's<00:00:43.620> important 00:00:44.090 --> 00:00:44.100 align:start position:0% the community uh because it's important 00:00:44.100 --> 00:00:47.030 align:start position:0% the community uh because it's important to<00:00:44.340> us<00:00:44.460> and<00:00:44.700> to<00:00:44.879> our<00:00:45.059> cause<00:00:45.620> so<00:00:46.620> we<00:00:46.800> are<00:00:46.980> going 00:00:47.030 --> 00:00:47.040 align:start position:0% to us and to our cause so we are going 00:00:47.040 --> 00:00:48.770 align:start position:0% to us and to our cause so we are going to<00:00:47.160> talk<00:00:47.340> about<00:00:47.520> acid<00:00:48.120> rights<00:00:48.420> abstraction 00:00:48.770 --> 00:00:48.780 align:start position:0% to talk about acid rights abstraction 00:00:48.780 --> 00:00:52.020 align:start position:0% to talk about acid rights abstraction our<00:00:49.320> case<00:00:49.559> for<00:00:49.739> smart<00:00:49.980> contract<00:00:50.340> wallets<00:00:50.760> so 00:00:52.020 --> 00:00:52.030 align:start position:0% our case for smart contract wallets so 00:00:52.030 --> 00:00:53.330 align:start position:0% our case for smart contract wallets so [Music] 00:00:53.330 --> 00:00:53.340 align:start position:0% [Music] 00:00:53.340 --> 00:00:56.150 align:start position:0% [Music] I'm<00:00:53.820> a<00:00:54.059> CEO<00:00:54.300> of<00:00:54.480> Pawn<00:00:54.660> whatever<00:00:55.079> being<00:00:55.620> a<00:00:55.800> CEO 00:00:56.150 --> 00:00:56.160 align:start position:0% I'm a CEO of Pawn whatever being a CEO 00:00:56.160 --> 00:00:57.770 align:start position:0% I'm a CEO of Pawn whatever being a CEO means<00:00:56.399> name<00:00:56.579> is<00:00:56.760> a<00:00:56.879> smart<00:00:57.000> contract<00:00:57.360> app<00:00:57.600> so 00:00:57.770 --> 00:00:57.780 align:start position:0% means name is a smart contract app so 00:00:57.780 --> 00:00:59.450 align:start position:0% means name is a smart contract app so he's<00:00:57.899> the<00:00:58.140> he's<00:00:58.440> actually<00:00:58.680> the<00:00:58.920> guy<00:00:59.160> who<00:00:59.340> is 00:00:59.450 --> 00:00:59.460 align:start position:0% he's the he's actually the guy who is 00:00:59.460 --> 00:01:00.770 align:start position:0% he's the he's actually the guy who is going<00:00:59.640> to<00:00:59.699> tell<00:00:59.940> you<00:01:00.059> the<00:01:00.180> interesting<00:01:00.539> stuff 00:01:00.770 --> 00:01:00.780 align:start position:0% going to tell you the interesting stuff 00:01:00.780 --> 00:01:03.830 align:start position:0% going to tell you the interesting stuff I'm<00:01:01.020> here<00:01:01.379> just<00:01:01.620> as<00:01:01.860> a<00:01:02.160> staffing 00:01:03.830 --> 00:01:03.840 align:start position:0% I'm here just as a staffing 00:01:03.840 --> 00:01:06.230 align:start position:0% I'm here just as a staffing um<00:01:03.960> so<00:01:04.799> first<00:01:05.100> do<00:01:05.400> I 00:01:06.230 --> 00:01:06.240 align:start position:0% um so first do I 00:01:06.240 --> 00:01:06.890 align:start position:0% um so first do I um 00:01:06.890 --> 00:01:06.900 align:start position:0% um 00:01:06.900 --> 00:01:09.590 align:start position:0% um so<00:01:07.439> why<00:01:07.799> did<00:01:08.100> we<00:01:08.280> started<00:01:08.939> uh<00:01:09.360> start 00:01:09.590 --> 00:01:09.600 align:start position:0% so why did we started uh start 00:01:09.600 --> 00:01:11.570 align:start position:0% so why did we started uh start developing<00:01:10.020> a<00:01:10.140> smartphone<00:01:10.439> wallet<00:01:10.979> in<00:01:11.400> short 00:01:11.570 --> 00:01:11.580 align:start position:0% developing a smartphone wallet in short 00:01:11.580 --> 00:01:13.730 align:start position:0% developing a smartphone wallet in short Pawn<00:01:11.939> is<00:01:12.180> a<00:01:12.360> is<00:01:12.600> a<00:01:12.780> generalized<00:01:13.260> borrowing<00:01:13.619> and 00:01:13.730 --> 00:01:13.740 align:start position:0% Pawn is a is a generalized borrowing and 00:01:13.740 --> 00:01:15.230 align:start position:0% Pawn is a is a generalized borrowing and lending<00:01:13.979> protocol 00:01:15.230 --> 00:01:15.240 align:start position:0% lending protocol 00:01:15.240 --> 00:01:16.789 align:start position:0% lending protocol um<00:01:15.299> but<00:01:15.659> we<00:01:15.900> also<00:01:16.140> need<00:01:16.260> like<00:01:16.439> a<00:01:16.560> whole<00:01:16.680> bunch 00:01:16.789 --> 00:01:16.799 align:start position:0% um but we also need like a whole bunch 00:01:16.799 --> 00:01:18.109 align:start position:0% um but we also need like a whole bunch of<00:01:16.920> tooling<00:01:17.220> out<00:01:17.400> there<00:01:17.520> in<00:01:17.700> the<00:01:17.760> ecosystem 00:01:18.109 --> 00:01:18.119 align:start position:0% of tooling out there in the ecosystem 00:01:18.119 --> 00:01:20.570 align:start position:0% of tooling out there in the ecosystem and<00:01:19.020> since<00:01:19.200> it<00:01:19.439> wasn't<00:01:19.619> available<00:01:20.040> at<00:01:20.460> the 00:01:20.570 --> 00:01:20.580 align:start position:0% and since it wasn't available at the 00:01:20.580 --> 00:01:21.710 align:start position:0% and since it wasn't available at the time 00:01:21.710 --> 00:01:21.720 align:start position:0% time 00:01:21.720 --> 00:01:24.830 align:start position:0% time um<00:01:21.840> we<00:01:22.259> we<00:01:22.439> decided<00:01:22.799> to<00:01:22.920> develop<00:01:23.100> it<00:01:23.280> ourselves 00:01:24.830 --> 00:01:24.840 align:start position:0% um we we decided to develop it ourselves 00:01:24.840 --> 00:01:26.510 align:start position:0% um we we decided to develop it ourselves um<00:01:24.960> so 00:01:26.510 --> 00:01:26.520 align:start position:0% um so 00:01:26.520 --> 00:01:29.390 align:start position:0% um so Upon<00:01:27.479> Our<00:01:27.960> Kind<00:01:28.320> of<00:01:28.380> Holy<00:01:28.680> Grail<00:01:28.920> what<00:01:29.159> we<00:01:29.280> want 00:01:29.390 --> 00:01:29.400 align:start position:0% Upon Our Kind of Holy Grail what we want 00:01:29.400 --> 00:01:30.350 align:start position:0% Upon Our Kind of Holy Grail what we want to<00:01:29.460> see<00:01:29.580> what<00:01:29.700> we<00:01:29.820> want<00:01:29.939> to<00:01:30.000> build<00:01:30.119> in<00:01:30.240> the 00:01:30.350 --> 00:01:30.360 align:start position:0% to see what we want to build in the 00:01:30.360 --> 00:01:32.390 align:start position:0% to see what we want to build in the ecosystem<00:01:30.720> is 00:01:32.390 --> 00:01:32.400 align:start position:0% ecosystem is 00:01:32.400 --> 00:01:34.850 align:start position:0% ecosystem is um seeing<00:01:32.880> long-term<00:01:33.540> Loans<00:01:34.140> mortgage<00:01:34.680> type 00:01:34.850 --> 00:01:34.860 align:start position:0% um seeing long-term Loans mortgage type 00:01:34.860 --> 00:01:37.310 align:start position:0% um seeing long-term Loans mortgage type of<00:01:34.979> loans<00:01:35.280> are<00:01:35.640> being<00:01:35.820> issued<00:01:36.299> uh<00:01:36.780> on<00:01:36.900> chain<00:01:37.079> so 00:01:37.310 --> 00:01:37.320 align:start position:0% of loans are being issued uh on chain so 00:01:37.320 --> 00:01:40.670 align:start position:0% of loans are being issued uh on chain so we're<00:01:37.500> looking<00:01:37.680> at<00:01:37.860> like<00:01:37.979> 5<00:01:38.340> 10<00:01:38.640> 15<00:01:39.240> years<00:01:39.680> uh 00:01:40.670 --> 00:01:40.680 align:start position:0% we're looking at like 5 10 15 years uh 00:01:40.680 --> 00:01:42.710 align:start position:0% we're looking at like 5 10 15 years uh contracts<00:01:41.159> that<00:01:41.400> should<00:01:41.579> last<00:01:41.820> on<00:01:42.240> chain<00:01:42.479> and 00:01:42.710 --> 00:01:42.720 align:start position:0% contracts that should last on chain and 00:01:42.720 --> 00:01:44.330 align:start position:0% contracts that should last on chain and should<00:01:43.079> be<00:01:43.259> actually 00:01:44.330 --> 00:01:44.340 align:start position:0% should be actually 00:01:44.340 --> 00:01:46.789 align:start position:0% should be actually um<00:01:44.400> you<00:01:44.939> know<00:01:45.000> perceived<00:01:45.840> as<00:01:45.960> uh<00:01:46.500> as 00:01:46.789 --> 00:01:46.799 align:start position:0% um you know perceived as uh as 00:01:46.799 --> 00:01:48.469 align:start position:0% um you know perceived as uh as legitimate<00:01:47.220> like<00:01:47.400> today<00:01:47.640> what<00:01:47.880> we<00:01:48.000> see<00:01:48.060> in<00:01:48.180> D5 00:01:48.469 --> 00:01:48.479 align:start position:0% legitimate like today what we see in D5 00:01:48.479 --> 00:01:50.690 align:start position:0% legitimate like today what we see in D5 is<00:01:48.659> mostly<00:01:48.960> short<00:01:49.500> term<00:01:49.740> or<00:01:50.040> something<00:01:50.340> that 00:01:50.690 --> 00:01:50.700 align:start position:0% is mostly short term or something that 00:01:50.700 --> 00:01:52.850 align:start position:0% is mostly short term or something that will<00:01:50.880> you<00:01:51.600> know<00:01:51.659> get<00:01:51.840> set<00:01:52.020> up<00:01:52.200> and<00:01:52.380> can<00:01:52.619> be 00:01:52.850 --> 00:01:52.860 align:start position:0% will you know get set up and can be 00:01:52.860 --> 00:01:54.950 align:start position:0% will you know get set up and can be erased<00:01:53.520> like<00:01:53.640> 30<00:01:53.820> seconds<00:01:54.060> later 00:01:54.950 --> 00:01:54.960 align:start position:0% erased like 30 seconds later 00:01:54.960 --> 00:01:56.990 align:start position:0% erased like 30 seconds later uh<00:01:55.500> but<00:01:55.619> we<00:01:55.799> kind<00:01:55.920> of<00:01:56.040> want<00:01:56.100> to<00:01:56.220> get<00:01:56.399> us<00:01:56.579> to<00:01:56.820> the 00:01:56.990 --> 00:01:57.000 align:start position:0% uh but we kind of want to get us to the 00:01:57.000 --> 00:01:59.929 align:start position:0% uh but we kind of want to get us to the point<00:01:57.180> where<00:01:57.540> people<00:01:58.140> will<00:01:58.320> be<00:01:58.500> able<00:01:58.740> to<00:01:58.939> uh 00:01:59.929 --> 00:01:59.939 align:start position:0% point where people will be able to uh 00:01:59.939 --> 00:02:01.609 align:start position:0% point where people will be able to uh back<00:02:00.180> their<00:02:00.600> long-term<00:02:01.140> mortgages<00:02:01.380> with 00:02:01.609 --> 00:02:01.619 align:start position:0% back their long-term mortgages with 00:02:01.619 --> 00:02:04.249 align:start position:0% back their long-term mortgages with digital<00:02:01.860> assets<00:02:02.280> and<00:02:02.399> this<00:02:02.579> is<00:02:02.759> a<00:02:03.000> important 00:02:04.249 --> 00:02:04.259 align:start position:0% digital assets and this is a important 00:02:04.259 --> 00:02:06.050 align:start position:0% digital assets and this is a important piece<00:02:04.799> of<00:02:04.979> the<00:02:05.040> ecosystem<00:02:05.340> or<00:02:05.579> like<00:02:05.759> piece<00:02:06.000> of 00:02:06.050 --> 00:02:06.060 align:start position:0% piece of the ecosystem or like piece of 00:02:06.060 --> 00:02:07.850 align:start position:0% piece of the ecosystem or like piece of the<00:02:06.119> tooling<00:02:06.420> that<00:02:06.540> we<00:02:06.659> need 00:02:07.850 --> 00:02:07.860 align:start position:0% the tooling that we need 00:02:07.860 --> 00:02:09.169 align:start position:0% the tooling that we need um so 00:02:09.169 --> 00:02:09.179 align:start position:0% um so 00:02:09.179 --> 00:02:11.510 align:start position:0% um so we<00:02:09.840> decided<00:02:10.140> to<00:02:10.259> dive<00:02:10.500> into<00:02:10.679> into<00:02:11.039> smartphone 00:02:11.510 --> 00:02:11.520 align:start position:0% we decided to dive into into smartphone 00:02:11.520 --> 00:02:13.430 align:start position:0% we decided to dive into into smartphone wallets<00:02:12.060> and<00:02:12.239> kind<00:02:12.420> of<00:02:12.480> allow 00:02:13.430 --> 00:02:13.440 align:start position:0% wallets and kind of allow 00:02:13.440 --> 00:02:16.790 align:start position:0% wallets and kind of allow using<00:02:14.280> the<00:02:14.760> assets<00:02:15.060> that<00:02:15.239> you<00:02:15.420> that<00:02:15.660> you<00:02:15.840> own 00:02:16.790 --> 00:02:16.800 align:start position:0% using the assets that you that you own 00:02:16.800 --> 00:02:19.190 align:start position:0% using the assets that you that you own um<00:02:16.860> while<00:02:17.520> you're<00:02:17.819> using<00:02:18.239> them<00:02:18.420> to<00:02:18.720> to<00:02:18.900> back 00:02:19.190 --> 00:02:19.200 align:start position:0% um while you're using them to to back 00:02:19.200 --> 00:02:22.550 align:start position:0% um while you're using them to to back alone<00:02:19.440> uh<00:02:20.340> but<00:02:20.459> our<00:02:20.640> case<00:02:20.879> or<00:02:21.120> the<00:02:21.300> case<00:02:21.540> for<00:02:21.840> uh 00:02:22.550 --> 00:02:22.560 align:start position:0% alone uh but our case or the case for uh 00:02:22.560 --> 00:02:25.130 align:start position:0% alone uh but our case or the case for uh for<00:02:22.800> our<00:02:22.860> smart<00:02:23.040> wallet<00:02:23.640> is<00:02:23.760> is<00:02:24.000> much<00:02:24.300> wider<00:02:24.720> so 00:02:25.130 --> 00:02:25.140 align:start position:0% for our smart wallet is is much wider so 00:02:25.140 --> 00:02:28.190 align:start position:0% for our smart wallet is is much wider so uh<00:02:25.739> today<00:02:25.980> we<00:02:26.220> are<00:02:26.340> going<00:02:26.459> to<00:02:26.580> dive<00:02:26.760> into<00:02:26.940> that 00:02:28.190 --> 00:02:28.200 align:start position:0% uh today we are going to dive into that 00:02:28.200 --> 00:02:30.290 align:start position:0% uh today we are going to dive into that um<00:02:28.260> so<00:02:28.800> most<00:02:29.580> people<00:02:29.760> I<00:02:29.940> guess<00:02:30.060> know 00:02:30.290 --> 00:02:30.300 align:start position:0% um so most people I guess know 00:02:30.300 --> 00:02:32.089 align:start position:0% um so most people I guess know smartphone<00:02:30.780> wallets<00:02:31.200> as 00:02:32.089 --> 00:02:32.099 align:start position:0% smartphone wallets as 00:02:32.099 --> 00:02:33.890 align:start position:0% smartphone wallets as um<00:02:32.160> as<00:02:32.819> a<00:02:32.879> multi-sick<00:02:33.300> or<00:02:33.540> something<00:02:33.660> that 00:02:33.890 --> 00:02:33.900 align:start position:0% um as a multi-sick or something that 00:02:33.900 --> 00:02:35.869 align:start position:0% um as a multi-sick or something that allows<00:02:34.319> you<00:02:34.379> to<00:02:34.739> operate<00:02:35.099> a<00:02:35.280> wallet<00:02:35.580> or 00:02:35.869 --> 00:02:35.879 align:start position:0% allows you to operate a wallet or 00:02:35.879 --> 00:02:38.390 align:start position:0% allows you to operate a wallet or operate<00:02:36.360> an<00:02:36.540> account<00:02:36.720> as<00:02:37.560> uh<00:02:37.920> multiple 00:02:38.390 --> 00:02:38.400 align:start position:0% operate an account as uh multiple 00:02:38.400 --> 00:02:41.350 align:start position:0% operate an account as uh multiple multiple<00:02:38.819> users<00:02:39.260> but<00:02:40.260> there<00:02:40.379> is<00:02:40.500> much<00:02:40.620> more<00:02:40.800> so 00:02:41.350 --> 00:02:41.360 align:start position:0% multiple users but there is much more so 00:02:41.360 --> 00:02:44.570 align:start position:0% multiple users but there is much more so depending<00:02:42.360> on<00:02:42.480> your<00:02:42.660> level<00:02:42.959> of<00:02:43.319> uh<00:02:43.800> you<00:02:44.040> know 00:02:44.570 --> 00:02:44.580 align:start position:0% depending on your level of uh you know 00:02:44.580 --> 00:02:45.170 align:start position:0% depending on your level of uh you know um 00:02:45.170 --> 00:02:45.180 align:start position:0% um 00:02:45.180 --> 00:02:47.869 align:start position:0% um technical<00:02:45.840> knowledge<00:02:46.260> or<00:02:46.800> just<00:02:47.280> like<00:02:47.459> the<00:02:47.760> the 00:02:47.869 --> 00:02:47.879 align:start position:0% technical knowledge or just like the the 00:02:47.879 --> 00:02:49.910 align:start position:0% technical knowledge or just like the the time<00:02:48.120> you<00:02:48.239> spend<00:02:48.420> in<00:02:48.599> the<00:02:48.720> ecosystem<00:02:49.019> just<00:02:49.739> a 00:02:49.910 --> 00:02:49.920 align:start position:0% time you spend in the ecosystem just a 00:02:49.920 --> 00:02:51.410 align:start position:0% time you spend in the ecosystem just a quick<00:02:50.040> rundown<00:02:50.459> what<00:02:50.819> are<00:02:51.000> actual<00:02:51.239> smart 00:02:51.410 --> 00:02:51.420 align:start position:0% quick rundown what are actual smart 00:02:51.420 --> 00:02:54.290 align:start position:0% quick rundown what are actual smart growing<00:02:51.720> wallets<00:02:52.019> uh<00:02:52.920> so<00:02:53.220> contract<00:02:53.940> wallets 00:02:54.290 --> 00:02:54.300 align:start position:0% growing wallets uh so contract wallets 00:02:54.300 --> 00:02:56.690 align:start position:0% growing wallets uh so contract wallets are<00:02:54.540> essentially<00:02:54.959> smart<00:02:55.260> contracts<00:02:55.800> that<00:02:56.160> are 00:02:56.690 --> 00:02:56.700 align:start position:0% are essentially smart contracts that are 00:02:56.700 --> 00:02:58.550 align:start position:0% are essentially smart contracts that are creating<00:02:57.000> a<00:02:57.180> proxy 00:02:58.550 --> 00:02:58.560 align:start position:0% creating a proxy 00:02:58.560 --> 00:03:00.770 align:start position:0% creating a proxy um<00:02:58.620> between<00:02:59.340> a<00:02:59.580> user<00:02:59.819> or<00:02:59.940> like<00:03:00.120> an<00:03:00.300> end<00:03:00.420> user 00:03:00.770 --> 00:03:00.780 align:start position:0% um between a user or like an end user 00:03:00.780 --> 00:03:03.710 align:start position:0% um between a user or like an end user account<00:03:00.959> uh<00:03:01.739> and<00:03:01.920> another<00:03:02.160> contract<00:03:02.760> uh<00:03:03.480> with 00:03:03.710 --> 00:03:03.720 align:start position:0% account uh and another contract uh with 00:03:03.720 --> 00:03:05.630 align:start position:0% account uh and another contract uh with some<00:03:03.840> extra<00:03:03.959> logic<00:03:04.440> added<00:03:04.739> so<00:03:04.920> there<00:03:05.280> are<00:03:05.459> some 00:03:05.630 --> 00:03:05.640 align:start position:0% some extra logic added so there are some 00:03:05.640 --> 00:03:08.330 align:start position:0% some extra logic added so there are some some<00:03:06.300> examples<00:03:06.720> uh<00:03:07.319> why<00:03:07.500> would<00:03:07.620> you<00:03:07.739> use<00:03:07.860> it<00:03:08.040> so 00:03:08.330 --> 00:03:08.340 align:start position:0% some examples uh why would you use it so 00:03:08.340 --> 00:03:11.030 align:start position:0% some examples uh why would you use it so first<00:03:08.760> you<00:03:09.120> can<00:03:09.300> you<00:03:10.200> can<00:03:10.319> enable<00:03:10.620> you<00:03:10.920> can 00:03:11.030 --> 00:03:11.040 align:start position:0% first you can you can enable you can 00:03:11.040 --> 00:03:13.550 align:start position:0% first you can you can enable you can create<00:03:11.280> like<00:03:11.700> more<00:03:12.300> events<00:03:12.720> automations<00:03:13.140> or 00:03:13.550 --> 00:03:13.560 align:start position:0% create like more events automations or 00:03:13.560 --> 00:03:15.050 align:start position:0% create like more events automations or like<00:03:13.680> call<00:03:13.860> wrappers<00:03:14.400> around<00:03:14.700> multiple 00:03:15.050 --> 00:03:15.060 align:start position:0% like call wrappers around multiple 00:03:15.060 --> 00:03:17.570 align:start position:0% like call wrappers around multiple contracts<00:03:15.659> uh<00:03:16.260> and<00:03:16.440> do<00:03:16.560> like<00:03:16.739> more<00:03:16.980> things<00:03:17.280> in 00:03:17.570 --> 00:03:17.580 align:start position:0% contracts uh and do like more things in 00:03:17.580 --> 00:03:19.130 align:start position:0% contracts uh and do like more things in one<00:03:17.760> transaction<00:03:18.180> then<00:03:18.540> you<00:03:18.720> would<00:03:18.900> otherwise 00:03:19.130 --> 00:03:19.140 align:start position:0% one transaction then you would otherwise 00:03:19.140 --> 00:03:21.710 align:start position:0% one transaction then you would otherwise be<00:03:19.319> able<00:03:19.500> to<00:03:19.620> do<00:03:19.800> a<00:03:20.580> good<00:03:20.819> example<00:03:21.120> for<00:03:21.300> that<00:03:21.480> is 00:03:21.710 --> 00:03:21.720 align:start position:0% be able to do a good example for that is 00:03:21.720 --> 00:03:24.290 align:start position:0% be able to do a good example for that is you<00:03:22.019> know<00:03:22.200> this<00:03:22.379> is<00:03:22.500> safe<00:03:22.680> or<00:03:22.920> safe<00:03:23.280> uh<00:03:24.000> as<00:03:24.180> it 00:03:24.290 --> 00:03:24.300 align:start position:0% you know this is safe or safe uh as it 00:03:24.300 --> 00:03:26.449 align:start position:0% you know this is safe or safe uh as it was<00:03:24.480> recently<00:03:24.840> renamed<00:03:25.319> uh<00:03:25.800> which<00:03:25.980> uses<00:03:26.280> it 00:03:26.449 --> 00:03:26.459 align:start position:0% was recently renamed uh which uses it 00:03:26.459 --> 00:03:28.670 align:start position:0% was recently renamed uh which uses it for<00:03:26.640> multi-sync<00:03:27.360> interactions<00:03:27.780> or<00:03:28.500> another 00:03:28.670 --> 00:03:28.680 align:start position:0% for multi-sync interactions or another 00:03:28.680 --> 00:03:30.890 align:start position:0% for multi-sync interactions or another great<00:03:29.040> example<00:03:29.400> is<00:03:29.519> a<00:03:29.700> deviceaver 00:03:30.890 --> 00:03:30.900 align:start position:0% great example is a deviceaver 00:03:30.900 --> 00:03:33.229 align:start position:0% great example is a deviceaver um<00:03:31.319> smart<00:03:31.800> contract<00:03:32.159> wallet<00:03:32.519> which<00:03:32.760> makes<00:03:33.120> it 00:03:33.229 --> 00:03:33.239 align:start position:0% um smart contract wallet which makes it 00:03:33.239 --> 00:03:34.970 align:start position:0% um smart contract wallet which makes it easier<00:03:33.540> to<00:03:33.720> operate 00:03:34.970 --> 00:03:34.980 align:start position:0% easier to operate 00:03:34.980 --> 00:03:36.910 align:start position:0% easier to operate um<00:03:35.040> in<00:03:35.400> the<00:03:35.519> in<00:03:35.640> the<00:03:35.760> default<00:03:36.120> ecosystem 00:03:36.910 --> 00:03:36.920 align:start position:0% um in the in the default ecosystem 00:03:36.920 --> 00:03:39.290 align:start position:0% um in the in the default ecosystem another<00:03:37.920> example<00:03:38.280> would<00:03:38.519> be<00:03:38.700> just<00:03:39.120> general 00:03:39.290 --> 00:03:39.300 align:start position:0% another example would be just general 00:03:39.300 --> 00:03:41.570 align:start position:0% another example would be just general identities<00:03:39.900> uh<00:03:40.440> so<00:03:40.680> there's<00:03:40.920> a<00:03:41.159> lot<00:03:41.220> of<00:03:41.400> talk 00:03:41.570 --> 00:03:41.580 align:start position:0% identities uh so there's a lot of talk 00:03:41.580 --> 00:03:43.550 align:start position:0% identities uh so there's a lot of talk about<00:03:41.879> uh<00:03:42.599> decentralized<00:03:43.200> identity 00:03:43.550 --> 00:03:43.560 align:start position:0% about uh decentralized identity 00:03:43.560 --> 00:03:46.130 align:start position:0% about uh decentralized identity standards<00:03:44.099> uh<00:03:44.760> and<00:03:44.940> a<00:03:45.060> way<00:03:45.180> you<00:03:45.360> can<00:03:45.540> use 00:03:46.130 --> 00:03:46.140 align:start position:0% standards uh and a way you can use 00:03:46.140 --> 00:03:49.070 align:start position:0% standards uh and a way you can use multiple<00:03:46.560> keys<00:03:46.980> in<00:03:47.340> one<00:03:47.640> smart<00:03:47.940> contract<00:03:48.480> and 00:03:49.070 --> 00:03:49.080 align:start position:0% multiple keys in one smart contract and 00:03:49.080 --> 00:03:50.690 align:start position:0% multiple keys in one smart contract and essentially<00:03:49.560> like<00:03:49.739> use<00:03:49.980> the<00:03:50.159> contract<00:03:50.459> as 00:03:50.690 --> 00:03:50.700 align:start position:0% essentially like use the contract as 00:03:50.700 --> 00:03:53.630 align:start position:0% essentially like use the contract as your<00:03:51.060> on-chain<00:03:51.540> identity<00:03:52.280> there<00:03:53.280> is<00:03:53.459> a<00:03:53.580> whole 00:03:53.630 --> 00:03:53.640 align:start position:0% your on-chain identity there is a whole 00:03:53.640 --> 00:03:55.009 align:start position:0% your on-chain identity there is a whole bunch<00:03:53.819> of<00:03:53.940> whole<00:03:54.180> bunch<00:03:54.360> of<00:03:54.480> attempts<00:03:54.900> around 00:03:55.009 --> 00:03:55.019 align:start position:0% bunch of whole bunch of attempts around 00:03:55.019 --> 00:03:57.229 align:start position:0% bunch of whole bunch of attempts around the<00:03:55.319> did<00:03:55.560> or<00:03:56.280> there's<00:03:56.400> also<00:03:56.700> the<00:03:57.000> Urgent 00:03:57.229 --> 00:03:57.239 align:start position:0% the did or there's also the Urgent 00:03:57.239 --> 00:03:59.449 align:start position:0% the did or there's also the Urgent wallet<00:03:57.599> which<00:03:58.379> essentially<00:03:58.860> does<00:03:59.099> this<00:03:59.280> very 00:03:59.449 --> 00:03:59.459 align:start position:0% wallet which essentially does this very 00:03:59.459 --> 00:04:01.070 align:start position:0% wallet which essentially does this very similar<00:03:59.819> thing 00:04:01.070 --> 00:04:01.080 align:start position:0% similar thing 00:04:01.080 --> 00:04:03.830 align:start position:0% similar thing um<00:04:01.620> now<00:04:02.459> smartphone<00:04:03.060> wallets<00:04:03.659> aren't 00:04:03.830 --> 00:04:03.840 align:start position:0% um now smartphone wallets aren't 00:04:03.840 --> 00:04:05.509 align:start position:0% um now smartphone wallets aren't definitely<00:04:04.200> useful<00:04:04.799> for<00:04:04.980> for<00:04:05.280> everything 00:04:05.509 --> 00:04:05.519 align:start position:0% definitely useful for for everything 00:04:05.519 --> 00:04:08.030 align:start position:0% definitely useful for for everything they<00:04:05.879> have<00:04:06.060> they<00:04:06.420> have<00:04:06.599> some<00:04:06.840> downsides<00:04:07.620> so 00:04:08.030 --> 00:04:08.040 align:start position:0% they have they have some downsides so 00:04:08.040 --> 00:04:09.589 align:start position:0% they have they have some downsides so that's<00:04:08.400> especially<00:04:08.819> the<00:04:09.000> gas<00:04:09.180> overhead 00:04:09.589 --> 00:04:09.599 align:start position:0% that's especially the gas overhead 00:04:09.599 --> 00:04:11.929 align:start position:0% that's especially the gas overhead because<00:04:10.019> again<00:04:10.860> you<00:04:11.220> you're<00:04:11.400> using<00:04:11.700> extra 00:04:11.929 --> 00:04:11.939 align:start position:0% because again you you're using extra 00:04:11.939 --> 00:04:14.149 align:start position:0% because again you you're using extra proxy<00:04:12.480> you<00:04:12.720> have<00:04:12.900> to<00:04:12.959> do<00:04:13.140> more<00:04:13.319> computation<00:04:13.799> in 00:04:14.149 --> 00:04:14.159 align:start position:0% proxy you have to do more computation in 00:04:14.159 --> 00:04:16.129 align:start position:0% proxy you have to do more computation in every<00:04:14.400> single<00:04:14.700> transaction<00:04:15.060> that<00:04:15.420> you're<00:04:16.139> um 00:04:16.129 --> 00:04:16.139 align:start position:0% every single transaction that you're um 00:04:16.139 --> 00:04:19.069 align:start position:0% every single transaction that you're um you're<00:04:16.440> using<00:04:16.739> it<00:04:16.799> for<00:04:16.979> uh<00:04:17.820> and<00:04:18.000> secondary<00:04:18.419> uh 00:04:19.069 --> 00:04:19.079 align:start position:0% you're using it for uh and secondary uh 00:04:19.079 --> 00:04:20.990 align:start position:0% you're using it for uh and secondary uh you<00:04:19.260> may<00:04:19.500> require<00:04:19.739> some<00:04:20.579> level<00:04:20.820> of 00:04:20.990 --> 00:04:21.000 align:start position:0% you may require some level of 00:04:21.000 --> 00:04:23.810 align:start position:0% you may require some level of integration<00:04:21.419> so<00:04:21.720> EIP<00:04:22.079> 1271<00:04:22.979> for<00:04:23.280> sign 00:04:23.810 --> 00:04:23.820 align:start position:0% integration so EIP 1271 for sign 00:04:23.820 --> 00:04:25.430 align:start position:0% integration so EIP 1271 for sign messages<00:04:24.120> would<00:04:24.479> be<00:04:24.660> one<00:04:24.780> example<00:04:25.139> of<00:04:25.259> like 00:04:25.430 --> 00:04:25.440 align:start position:0% messages would be one example of like 00:04:25.440 --> 00:04:27.170 align:start position:0% messages would be one example of like what<00:04:25.620> everybody<00:04:25.860> everyone<00:04:26.400> else<00:04:26.699> has<00:04:26.940> to 00:04:27.170 --> 00:04:27.180 align:start position:0% what everybody everyone else has to 00:04:27.180 --> 00:04:29.450 align:start position:0% what everybody everyone else has to integrate<00:04:27.720> in<00:04:28.020> order<00:04:28.139> for<00:04:28.440> smart<00:04:29.040> contract 00:04:29.450 --> 00:04:29.460 align:start position:0% integrate in order for smart contract 00:04:29.460 --> 00:04:32.150 align:start position:0% integrate in order for smart contract wallets<00:04:29.820> to<00:04:30.060> work<00:04:30.720> just<00:04:31.020> as<00:04:31.199> like<00:04:31.680> a<00:04:31.860> user 00:04:32.150 --> 00:04:32.160 align:start position:0% wallets to work just as like a user 00:04:32.160 --> 00:04:34.430 align:start position:0% wallets to work just as like a user account<00:04:32.340> would 00:04:34.430 --> 00:04:34.440 align:start position:0% account would 00:04:34.440 --> 00:04:37.370 align:start position:0% account would um<00:04:34.500> so<00:04:34.979> in<00:04:35.520> our<00:04:35.699> specific<00:04:36.000> case<00:04:36.240> like<00:04:36.720> why<00:04:37.080> do 00:04:37.370 --> 00:04:37.380 align:start position:0% um so in our specific case like why do 00:04:37.380 --> 00:04:38.810 align:start position:0% um so in our specific case like why do we<00:04:37.500> want<00:04:37.620> to<00:04:37.800> mess<00:04:37.919> up<00:04:38.100> with<00:04:38.280> uh<00:04:38.639> with 00:04:38.810 --> 00:04:38.820 align:start position:0% we want to mess up with uh with 00:04:38.820 --> 00:04:40.610 align:start position:0% we want to mess up with uh with asteroids 00:04:40.610 --> 00:04:40.620 align:start position:0% asteroids 00:04:40.620 --> 00:04:42.350 align:start position:0% asteroids um<00:04:40.680> as<00:04:41.220> I<00:04:41.340> mentioned<00:04:41.580> we<00:04:41.820> want<00:04:41.940> to<00:04:42.060> allow<00:04:42.240> the 00:04:42.350 --> 00:04:42.360 align:start position:0% um as I mentioned we want to allow the 00:04:42.360 --> 00:04:45.290 align:start position:0% um as I mentioned we want to allow the case<00:04:42.540> where<00:04:42.960> you<00:04:43.620> kind<00:04:43.800> of<00:04:43.919> can<00:04:44.580> have<00:04:45.060> your 00:04:45.290 --> 00:04:45.300 align:start position:0% case where you kind of can have your 00:04:45.300 --> 00:04:47.749 align:start position:0% case where you kind of can have your cake<00:04:45.479> and<00:04:45.660> eat<00:04:45.840> it<00:04:45.960> too<00:04:46.080> where<00:04:46.320> you<00:04:46.500> can<00:04:46.620> have 00:04:47.749 --> 00:04:47.759 align:start position:0% cake and eat it too where you can have 00:04:47.759 --> 00:04:50.330 align:start position:0% cake and eat it too where you can have um Assets<00:04:48.180> in<00:04:48.600> your<00:04:48.720> custody<00:04:49.199> but<00:04:50.100> still 00:04:50.330 --> 00:04:50.340 align:start position:0% um Assets in your custody but still 00:04:50.340 --> 00:04:51.890 align:start position:0% um Assets in your custody but still create<00:04:50.580> some<00:04:50.880> sort<00:04:51.000> of<00:04:51.120> a<00:04:51.180> deed<00:04:51.419> some<00:04:51.600> sort<00:04:51.840> of 00:04:51.890 --> 00:04:51.900 align:start position:0% create some sort of a deed some sort of 00:04:51.900 --> 00:04:54.469 align:start position:0% create some sort of a deed some sort of a<00:04:52.020> right<00:04:52.199> uh<00:04:52.860> for<00:04:53.160> another<00:04:53.400> person<00:04:53.759> to 00:04:54.469 --> 00:04:54.479 align:start position:0% a right uh for another person to 00:04:54.479 --> 00:04:56.749 align:start position:0% a right uh for another person to eventually<00:04:55.320> be<00:04:55.919> able<00:04:56.100> to<00:04:56.220> access<00:04:56.400> those 00:04:56.749 --> 00:04:56.759 align:start position:0% eventually be able to access those 00:04:56.759 --> 00:04:59.150 align:start position:0% eventually be able to access those assets<00:04:57.120> and<00:04:57.479> and<00:04:57.660> kind<00:04:57.900> of<00:04:57.960> like<00:04:58.080> take<00:04:58.320> them 00:04:59.150 --> 00:04:59.160 align:start position:0% assets and and kind of like take them 00:04:59.160 --> 00:05:03.170 align:start position:0% assets and and kind of like take them um<00:04:59.280> take<00:04:59.820> them<00:05:00.180> with<00:05:00.360> them<00:05:00.960> so 00:05:03.170 --> 00:05:03.180 align:start position:0% um take them with them so 00:05:03.180 --> 00:05:03.770 align:start position:0% um take them with them so um 00:05:03.770 --> 00:05:03.780 align:start position:0% um 00:05:03.780 --> 00:05:05.870 align:start position:0% um the<00:05:04.320> very<00:05:04.680> basic<00:05:05.100> case<00:05:05.220> for<00:05:05.460> us<00:05:05.639> is 00:05:05.870 --> 00:05:05.880 align:start position:0% the very basic case for us is 00:05:05.880 --> 00:05:07.670 align:start position:0% the very basic case for us is essentially<00:05:06.419> creating<00:05:06.780> a<00:05:07.020> hook<00:05:07.199> in<00:05:07.500> the 00:05:07.670 --> 00:05:07.680 align:start position:0% essentially creating a hook in the 00:05:07.680 --> 00:05:09.770 align:start position:0% essentially creating a hook in the wallet<00:05:07.919> in<00:05:08.100> someone<00:05:08.280> else's<00:05:08.699> account<00:05:09.360> that 00:05:09.770 --> 00:05:09.780 align:start position:0% wallet in someone else's account that 00:05:09.780 --> 00:05:12.830 align:start position:0% wallet in someone else's account that allows<00:05:10.199> uh<00:05:10.979> you<00:05:11.220> to<00:05:11.580> essentially<00:05:12.360> drain<00:05:12.720> the 00:05:12.830 --> 00:05:12.840 align:start position:0% allows uh you to essentially drain the 00:05:12.840 --> 00:05:15.170 align:start position:0% allows uh you to essentially drain the wallet<00:05:13.199> uh<00:05:13.740> if<00:05:13.919> a<00:05:14.100> certain<00:05:14.280> criteria<00:05:14.880> is<00:05:15.060> met 00:05:15.170 --> 00:05:15.180 align:start position:0% wallet uh if a certain criteria is met 00:05:15.180 --> 00:05:16.249 align:start position:0% wallet uh if a certain criteria is met and<00:05:15.419> obviously<00:05:15.660> if<00:05:15.780> the<00:05:15.960> other<00:05:16.080> person 00:05:16.249 --> 00:05:16.259 align:start position:0% and obviously if the other person 00:05:16.259 --> 00:05:18.469 align:start position:0% and obviously if the other person consents<00:05:16.860> to<00:05:16.919> it<00:05:17.100> so<00:05:17.280> they<00:05:17.820> would<00:05:18.060> actually 00:05:18.469 --> 00:05:18.479 align:start position:0% consents to it so they would actually 00:05:18.479 --> 00:05:20.210 align:start position:0% consents to it so they would actually like<00:05:18.780> sign<00:05:19.139> up<00:05:19.320> for<00:05:19.500> that<00:05:19.620> in<00:05:19.860> another 00:05:20.210 --> 00:05:20.220 align:start position:0% like sign up for that in another 00:05:20.220 --> 00:05:21.830 align:start position:0% like sign up for that in another contract 00:05:21.830 --> 00:05:21.840 align:start position:0% contract 00:05:21.840 --> 00:05:22.430 align:start position:0% contract um 00:05:22.430 --> 00:05:22.440 align:start position:0% um 00:05:22.440 --> 00:05:24.890 align:start position:0% um why<00:05:22.800> is<00:05:22.979> this<00:05:23.100> what<00:05:24.060> is<00:05:24.120> it<00:05:24.300> good<00:05:24.419> for<00:05:24.479> is<00:05:24.780> that 00:05:24.890 --> 00:05:24.900 align:start position:0% why is this what is it good for is that 00:05:24.900 --> 00:05:26.990 align:start position:0% why is this what is it good for is that you<00:05:25.139> don't<00:05:25.320> actually<00:05:25.500> have<00:05:25.800> to<00:05:26.039> move<00:05:26.699> those 00:05:26.990 --> 00:05:27.000 align:start position:0% you don't actually have to move those 00:05:27.000 --> 00:05:28.850 align:start position:0% you don't actually have to move those assets<00:05:27.360> that<00:05:27.600> you<00:05:27.780> have<00:05:27.900> in<00:05:28.199> the<00:05:28.380> account<00:05:28.500> you 00:05:28.850 --> 00:05:28.860 align:start position:0% assets that you have in the account you 00:05:28.860 --> 00:05:31.790 align:start position:0% assets that you have in the account you can<00:05:28.919> just<00:05:29.039> create<00:05:29.280> this<00:05:29.520> like<00:05:29.900> uh<00:05:30.900> right<00:05:31.380> that 00:05:31.790 --> 00:05:31.800 align:start position:0% can just create this like uh right that 00:05:31.800 --> 00:05:33.170 align:start position:0% can just create this like uh right that will<00:05:31.919> allow<00:05:32.160> someone<00:05:32.340> else<00:05:32.520> to<00:05:32.699> access<00:05:32.880> those 00:05:33.170 --> 00:05:33.180 align:start position:0% will allow someone else to access those 00:05:33.180 --> 00:05:35.870 align:start position:0% will allow someone else to access those assets<00:05:33.539> uh<00:05:34.199> and<00:05:34.500> if<00:05:34.800> some<00:05:35.039> people<00:05:35.220> state<00:05:35.580> from 00:05:35.870 --> 00:05:35.880 align:start position:0% assets uh and if some people state from 00:05:35.880 --> 00:05:38.029 align:start position:0% assets uh and if some people state from the<00:05:36.000> previous<00:05:36.180> talk<00:05:36.479> uh<00:05:37.139> from<00:05:37.320> like<00:05:37.500> EA<00:05:37.860> or 00:05:38.029 --> 00:05:38.039 align:start position:0% the previous talk uh from like EA or 00:05:38.039 --> 00:05:39.590 align:start position:0% the previous talk uh from like EA or just<00:05:38.220> the<00:05:38.340> Enterprise<00:05:38.520> ecosystem<00:05:39.120> this<00:05:39.419> could 00:05:39.590 --> 00:05:39.600 align:start position:0% just the Enterprise ecosystem this could 00:05:39.600 --> 00:05:41.629 align:start position:0% just the Enterprise ecosystem this could be<00:05:39.720> useful<00:05:40.139> for<00:05:40.259> even<00:05:40.440> like<00:05:40.620> kyc'd<00:05:41.340> assets 00:05:41.629 --> 00:05:41.639 align:start position:0% be useful for even like kyc'd assets 00:05:41.639 --> 00:05:44.090 align:start position:0% be useful for even like kyc'd assets because<00:05:41.880> or<00:05:42.300> like<00:05:42.479> assets<00:05:43.020> that<00:05:43.199> require<00:05:43.380> kyc 00:05:44.090 --> 00:05:44.100 align:start position:0% because or like assets that require kyc 00:05:44.100 --> 00:05:45.770 align:start position:0% because or like assets that require kyc because<00:05:44.580> you<00:05:44.820> don't<00:05:44.940> have<00:05:45.060> to<00:05:45.180> move<00:05:45.360> them<00:05:45.600> from 00:05:45.770 --> 00:05:45.780 align:start position:0% because you don't have to move them from 00:05:45.780 --> 00:05:48.050 align:start position:0% because you don't have to move them from wallet<00:05:46.139> you<00:05:46.320> can<00:05:46.500> just<00:05:46.620> wait<00:05:46.860> until<00:05:47.220> the<00:05:47.820> point 00:05:48.050 --> 00:05:48.060 align:start position:0% wallet you can just wait until the point 00:05:48.060 --> 00:05:50.330 align:start position:0% wallet you can just wait until the point where<00:05:48.240> you<00:05:48.419> actually<00:05:48.600> have<00:05:48.900> to<00:05:49.199> move<00:05:49.620> them<00:05:49.860> uh 00:05:50.330 --> 00:05:50.340 align:start position:0% where you actually have to move them uh 00:05:50.340 --> 00:05:51.950 align:start position:0% where you actually have to move them uh and<00:05:50.520> that's<00:05:50.639> the<00:05:50.820> point<00:05:51.000> where<00:05:51.240> you<00:05:51.479> can<00:05:51.600> kind 00:05:51.950 --> 00:05:51.960 align:start position:0% and that's the point where you can kind 00:05:51.960 --> 00:05:53.749 align:start position:0% and that's the point where you can kind of<00:05:52.080> like<00:05:52.139> start<00:05:52.380> dealing<00:05:52.680> with<00:05:52.800> kyc<00:05:53.400> because 00:05:53.749 --> 00:05:53.759 align:start position:0% of like start dealing with kyc because 00:05:53.759 --> 00:05:55.969 align:start position:0% of like start dealing with kyc because the<00:05:54.060> actual<00:05:54.240> asset<00:05:54.660> didn't<00:05:54.840> you<00:05:55.259> know<00:05:55.380> didn't 00:05:55.969 --> 00:05:55.979 align:start position:0% the actual asset didn't you know didn't 00:05:55.979 --> 00:05:58.610 align:start position:0% the actual asset didn't you know didn't move<00:05:56.220> nothing<00:05:56.699> nothing<00:05:57.000> happened<00:05:57.300> to<00:05:57.539> it 00:05:58.610 --> 00:05:58.620 align:start position:0% move nothing nothing happened to it 00:05:58.620 --> 00:06:00.409 align:start position:0% move nothing nothing happened to it um<00:05:58.680> so<00:05:58.860> again<00:05:59.039> for<00:05:59.340> us<00:05:59.460> the<00:05:59.820> the<00:06:00.000> case<00:06:00.180> is<00:06:00.300> the 00:06:00.409 --> 00:06:00.419 align:start position:0% um so again for us the the case is the 00:06:00.419 --> 00:06:02.090 align:start position:0% um so again for us the the case is the D5<00:06:00.660> mortgage<00:06:01.020> where<00:06:01.199> we<00:06:01.500> just<00:06:01.620> want<00:06:01.740> to<00:06:01.860> allow 00:06:02.090 --> 00:06:02.100 align:start position:0% D5 mortgage where we just want to allow 00:06:02.100 --> 00:06:03.590 align:start position:0% D5 mortgage where we just want to allow someone<00:06:02.340> to 00:06:03.590 --> 00:06:03.600 align:start position:0% someone to 00:06:03.600 --> 00:06:06.409 align:start position:0% someone to um you<00:06:03.900> know<00:06:03.960> buy<00:06:04.199> a<00:06:04.380> piece<00:06:04.560> of<00:06:04.680> decentralized 00:06:06.409 --> 00:06:06.419 align:start position:0% um you know buy a piece of decentralized 00:06:06.419 --> 00:06:08.749 align:start position:0% um you know buy a piece of decentralized lock<00:06:06.900> it<00:06:07.139> as<00:06:07.259> collateral<00:06:07.680> keep<00:06:08.160> that<00:06:08.400> in<00:06:08.639> their 00:06:08.749 --> 00:06:08.759 align:start position:0% lock it as collateral keep that in their 00:06:08.759 --> 00:06:10.969 align:start position:0% lock it as collateral keep that in their custody<00:06:09.120> still<00:06:09.780> like<00:06:09.960> allow<00:06:10.320> them<00:06:10.440> to<00:06:10.620> use<00:06:10.800> it 00:06:10.969 --> 00:06:10.979 align:start position:0% custody still like allow them to use it 00:06:10.979 --> 00:06:14.330 align:start position:0% custody still like allow them to use it but<00:06:11.940> use<00:06:12.300> the<00:06:12.479> value<00:06:12.660> of<00:06:12.900> the<00:06:13.080> assets<00:06:13.380> asset<00:06:14.220> as 00:06:14.330 --> 00:06:14.340 align:start position:0% but use the value of the assets asset as 00:06:14.340 --> 00:06:16.790 align:start position:0% but use the value of the assets asset as a<00:06:14.460> backing<00:06:14.699> for<00:06:14.880> loan<00:06:15.240> another<00:06:16.199> example<00:06:16.620> would 00:06:16.790 --> 00:06:16.800 align:start position:0% a backing for loan another example would 00:06:16.800 --> 00:06:18.230 align:start position:0% a backing for loan another example would be<00:06:17.039> you<00:06:17.520> know 00:06:18.230 --> 00:06:18.240 align:start position:0% be you know 00:06:18.240 --> 00:06:20.270 align:start position:0% be you know like<00:06:18.660> Dow<00:06:18.900> voting<00:06:19.259> rights<00:06:19.620> again<00:06:19.860> like<00:06:20.160> you 00:06:20.270 --> 00:06:20.280 align:start position:0% like Dow voting rights again like you 00:06:20.280 --> 00:06:22.309 align:start position:0% like Dow voting rights again like you still<00:06:20.639> want<00:06:20.820> to<00:06:20.940> use<00:06:21.060> those<00:06:21.300> but<00:06:21.960> you<00:06:22.139> might 00:06:22.309 --> 00:06:22.319 align:start position:0% still want to use those but you might 00:06:22.319 --> 00:06:25.670 align:start position:0% still want to use those but you might want<00:06:22.560> to<00:06:22.680> utilize<00:06:23.280> the<00:06:23.699> the<00:06:24.240> value<00:06:24.600> or<00:06:25.199> that's 00:06:25.670 --> 00:06:25.680 align:start position:0% want to utilize the the value or that's 00:06:25.680 --> 00:06:27.650 align:start position:0% want to utilize the the value or that's that's<00:06:25.919> kind<00:06:26.220> of<00:06:26.340> backing<00:06:26.759> uh<00:06:27.120> the<00:06:27.240> particle 00:06:27.650 --> 00:06:27.660 align:start position:0% that's kind of backing uh the particle 00:06:27.660 --> 00:06:30.590 align:start position:0% that's kind of backing uh the particle token<00:06:28.080> the<00:06:28.380> same<00:06:28.500> goes<00:06:28.800> for<00:06:28.979> gaming<00:06:29.400> items<00:06:29.880> or 00:06:30.590 --> 00:06:30.600 align:start position:0% token the same goes for gaming items or 00:06:30.600 --> 00:06:34.610 align:start position:0% token the same goes for gaming items or ens<00:06:31.440> names<00:06:31.620> are<00:06:32.100> again<00:06:32.220> a<00:06:32.460> perfect<00:06:32.759> example 00:06:34.610 --> 00:06:34.620 align:start position:0% ens names are again a perfect example 00:06:34.620 --> 00:06:37.129 align:start position:0% ens names are again a perfect example um<00:06:34.740> another<00:06:35.220> useful<00:06:36.060> thing<00:06:36.300> is<00:06:36.780> that<00:06:36.900> you<00:06:37.020> can 00:06:37.129 --> 00:06:37.139 align:start position:0% um another useful thing is that you can 00:06:37.139 --> 00:06:39.950 align:start position:0% um another useful thing is that you can also<00:06:37.440> allow<00:06:37.940> asset<00:06:38.940> renting<00:06:39.300> you<00:06:39.600> can<00:06:39.720> just 00:06:39.950 --> 00:06:39.960 align:start position:0% also allow asset renting you can just 00:06:39.960 --> 00:06:41.570 align:start position:0% also allow asset renting you can just reverse<00:06:40.319> the<00:06:40.500> case<00:06:40.620> and<00:06:40.860> essentially<00:06:41.280> just 00:06:41.570 --> 00:06:41.580 align:start position:0% reverse the case and essentially just 00:06:41.580 --> 00:06:44.090 align:start position:0% reverse the case and essentially just give<00:06:42.180> someone<00:06:42.419> the<00:06:42.720> right<00:06:42.900> to<00:06:43.080> uh<00:06:43.979> like 00:06:44.090 --> 00:06:44.100 align:start position:0% give someone the right to uh like 00:06:44.100 --> 00:06:45.830 align:start position:0% give someone the right to uh like transfer<00:06:44.460> the<00:06:44.580> right<00:06:44.699> to<00:06:44.880> someone<00:06:45.000> else<00:06:45.240> but 00:06:45.830 --> 00:06:45.840 align:start position:0% transfer the right to someone else but 00:06:45.840 --> 00:06:47.990 align:start position:0% transfer the right to someone else but keep<00:06:46.139> the<00:06:46.440> token<00:06:46.979> transfer<00:06:47.340> right<00:06:47.520> and<00:06:47.759> keep 00:06:47.990 --> 00:06:48.000 align:start position:0% keep the token transfer right and keep 00:06:48.000 --> 00:06:50.510 align:start position:0% keep the token transfer right and keep the<00:06:48.240> ownership<00:06:48.539> of<00:06:49.080> the<00:06:49.259> asset 00:06:50.510 --> 00:06:50.520 align:start position:0% the ownership of the asset 00:06:50.520 --> 00:06:52.370 align:start position:0% the ownership of the asset um<00:06:50.639> and<00:06:51.000> withdraw<00:06:51.479> it<00:06:51.600> later<00:06:51.780> if<00:06:52.139> certain 00:06:52.370 --> 00:06:52.380 align:start position:0% um and withdraw it later if certain 00:06:52.380 --> 00:06:55.129 align:start position:0% um and withdraw it later if certain criteria<00:06:52.860> is<00:06:52.979> met<00:06:53.160> again<00:06:53.759> so<00:06:54.419> this<00:06:54.720> is<00:06:54.840> the 00:06:55.129 --> 00:06:55.139 align:start position:0% criteria is met again so this is the 00:06:55.139 --> 00:06:58.129 align:start position:0% criteria is met again so this is the basic<00:06:55.560> intro<00:06:55.979> and<00:06:56.520> now<00:06:56.699> finally<00:06:57.120> uh<00:06:57.720> now<00:06:57.960> is 00:06:58.129 --> 00:06:58.139 align:start position:0% basic intro and now finally uh now is 00:06:58.139 --> 00:07:00.469 align:start position:0% basic intro and now finally uh now is the<00:06:58.319> interesting<00:06:58.860> stuff<00:06:59.039> so<00:06:59.639> passing<00:07:00.360> the 00:07:00.469 --> 00:07:00.479 align:start position:0% the interesting stuff so passing the 00:07:00.479 --> 00:07:04.550 align:start position:0% the interesting stuff so passing the word<00:07:00.660> over<00:07:00.840> to<00:07:01.080> nine 00:07:04.550 --> 00:07:04.560 align:start position:0% 00:07:04.560 --> 00:07:07.370 align:start position:0% uh<00:07:05.280> thanks<00:07:05.460> Joseph<00:07:05.699> hi<00:07:06.180> guys<00:07:06.360> my<00:07:06.780> name<00:07:06.900> is<00:07:07.020> name 00:07:07.370 --> 00:07:07.380 align:start position:0% uh thanks Joseph hi guys my name is name 00:07:07.380 --> 00:07:10.129 align:start position:0% uh thanks Joseph hi guys my name is name uh<00:07:08.340> before<00:07:08.520> we<00:07:08.759> start<00:07:08.940> for<00:07:09.479> those<00:07:09.720> who<00:07:09.900> don't 00:07:10.129 --> 00:07:10.139 align:start position:0% uh before we start for those who don't 00:07:10.139 --> 00:07:13.070 align:start position:0% uh before we start for those who don't know<00:07:10.319> me<00:07:10.500> uh<00:07:11.100> beside<00:07:11.580> I'm<00:07:12.120> being<00:07:12.600> a<00:07:12.900> smart 00:07:13.070 --> 00:07:13.080 align:start position:0% know me uh beside I'm being a smart 00:07:13.080 --> 00:07:16.070 align:start position:0% know me uh beside I'm being a smart contract<00:07:13.520> I'm<00:07:14.520> also<00:07:14.880> a<00:07:15.180> contemporary<00:07:15.720> circus 00:07:16.070 --> 00:07:16.080 align:start position:0% contract I'm also a contemporary circus 00:07:16.080 --> 00:07:18.950 align:start position:0% contract I'm also a contemporary circus artist<00:07:16.319> so<00:07:17.100> I'm<00:07:17.580> even<00:07:18.180> though<00:07:18.360> I'm<00:07:18.660> used<00:07:18.840> to 00:07:18.950 --> 00:07:18.960 align:start position:0% artist so I'm even though I'm used to 00:07:18.960 --> 00:07:21.110 align:start position:0% artist so I'm even though I'm used to performing<00:07:19.380> in<00:07:19.620> front<00:07:19.740> of<00:07:19.919> people<00:07:20.099> I<00:07:20.759> am<00:07:20.940> not 00:07:21.110 --> 00:07:21.120 align:start position:0% performing in front of people I am not 00:07:21.120 --> 00:07:23.870 align:start position:0% performing in front of people I am not used<00:07:21.360> to<00:07:21.539> speaking<00:07:22.199> in<00:07:22.440> front<00:07:22.620> of<00:07:22.740> people<00:07:22.919> so 00:07:23.870 --> 00:07:23.880 align:start position:0% used to speaking in front of people so 00:07:23.880 --> 00:07:26.870 align:start position:0% used to speaking in front of people so I'm<00:07:24.180> super<00:07:24.419> nervous<00:07:24.900> now<00:07:25.160> and<00:07:26.160> uh<00:07:26.520> I<00:07:26.759> was 00:07:26.870 --> 00:07:26.880 align:start position:0% I'm super nervous now and uh I was 00:07:26.880 --> 00:07:29.749 align:start position:0% I'm super nervous now and uh I was thinking<00:07:27.120> how<00:07:27.300> can<00:07:27.479> I<00:07:27.660> like<00:07:27.900> make<00:07:28.620> me<00:07:28.800> less<00:07:29.039> uh 00:07:29.749 --> 00:07:29.759 align:start position:0% thinking how can I like make me less uh 00:07:29.759 --> 00:07:32.029 align:start position:0% thinking how can I like make me less uh nervous<00:07:30.120> so<00:07:30.720> I<00:07:30.900> decided<00:07:31.259> I<00:07:31.560> want<00:07:31.740> to<00:07:31.860> perform 00:07:32.029 --> 00:07:32.039 align:start position:0% nervous so I decided I want to perform 00:07:32.039 --> 00:07:34.309 align:start position:0% nervous so I decided I want to perform you<00:07:32.280> something<00:07:33.000> uh<00:07:33.599> unfortunately<00:07:34.020> I'm 00:07:34.309 --> 00:07:34.319 align:start position:0% you something uh unfortunately I'm 00:07:34.319 --> 00:07:35.990 align:start position:0% you something uh unfortunately I'm jumping<00:07:34.680> on<00:07:34.800> a<00:07:34.919> trampoline<00:07:35.340> which<00:07:35.639> is<00:07:35.759> uh 00:07:35.990 --> 00:07:36.000 align:start position:0% jumping on a trampoline which is uh 00:07:36.000 --> 00:07:38.510 align:start position:0% jumping on a trampoline which is uh which<00:07:36.240> cannot<00:07:36.479> be<00:07:36.599> fit<00:07:36.780> here<00:07:36.960> so<00:07:37.860> I'll<00:07:38.400> just 00:07:38.510 --> 00:07:38.520 align:start position:0% which cannot be fit here so I'll just 00:07:38.520 --> 00:07:40.309 align:start position:0% which cannot be fit here so I'll just show<00:07:38.699> you<00:07:38.819> a<00:07:38.940> video<00:07:39.120> of<00:07:39.479> me<00:07:39.599> being<00:07:39.900> shot<00:07:40.080> from 00:07:40.309 --> 00:07:40.319 align:start position:0% show you a video of me being shot from 00:07:40.319 --> 00:07:58.990 align:start position:0% show you a video of me being shot from your<00:07:40.440> human<00:07:40.560> cannon 00:07:58.990 --> 00:07:59.000 align:start position:0% 00:07:59.000 --> 00:08:02.089 align:start position:0% thanks<00:08:00.000> guys<00:08:00.240> yeah<00:08:00.599> it<00:08:00.960> helped<00:08:01.380> me<00:08:01.440> it<00:08:01.800> helped 00:08:02.089 --> 00:08:02.099 align:start position:0% thanks guys yeah it helped me it helped 00:08:02.099 --> 00:08:05.749 align:start position:0% thanks guys yeah it helped me it helped me<00:08:02.160> a<00:08:02.280> lot<00:08:02.400> so<00:08:02.940> back<00:08:03.900> to<00:08:04.080> the<00:08:04.259> topic<00:08:04.620> uh<00:08:05.340> let's 00:08:05.749 --> 00:08:05.759 align:start position:0% me a lot so back to the topic uh let's 00:08:05.759 --> 00:08:08.089 align:start position:0% me a lot so back to the topic uh let's define<00:08:06.000> some<00:08:06.360> requirements<00:08:06.840> for<00:08:07.139> this<00:08:07.319> uh<00:08:07.800> for 00:08:08.089 --> 00:08:08.099 align:start position:0% define some requirements for this uh for 00:08:08.099 --> 00:08:10.189 align:start position:0% define some requirements for this uh for this<00:08:08.220> contract<00:08:08.520> wallet<00:08:08.940> uh<00:08:09.360> obviously<00:08:09.720> it<00:08:10.080> has 00:08:10.189 --> 00:08:10.199 align:start position:0% this contract wallet uh obviously it has 00:08:10.199 --> 00:08:12.230 align:start position:0% this contract wallet uh obviously it has to<00:08:10.380> act<00:08:10.500> as<00:08:10.680> a<00:08:10.860> normal<00:08:10.979> contract<00:08:11.340> wallet<00:08:11.699> that 00:08:12.230 --> 00:08:12.240 align:start position:0% to act as a normal contract wallet that 00:08:12.240 --> 00:08:14.029 align:start position:0% to act as a normal contract wallet that means<00:08:12.539> that<00:08:12.780> you<00:08:12.960> have<00:08:13.139> to<00:08:13.319> be<00:08:13.440> able<00:08:13.680> to<00:08:13.860> call 00:08:14.029 --> 00:08:14.039 align:start position:0% means that you have to be able to call 00:08:14.039 --> 00:08:16.430 align:start position:0% means that you have to be able to call orbitrary<00:08:14.759> call<00:08:14.940> later<00:08:15.120> on<00:08:15.660> on<00:08:16.020> any<00:08:16.199> address 00:08:16.430 --> 00:08:16.440 align:start position:0% orbitrary call later on on any address 00:08:16.440 --> 00:08:19.670 align:start position:0% orbitrary call later on on any address basically<00:08:17.460> and<00:08:18.300> the<00:08:18.419> nice<00:08:18.840> feature<00:08:19.199> enabled 00:08:19.670 --> 00:08:19.680 align:start position:0% basically and the nice feature enabled 00:08:19.680 --> 00:08:22.790 align:start position:0% basically and the nice feature enabled tokenizing<00:08:20.400> asset<00:08:20.940> transfer<00:08:21.360> rights<00:08:21.780> we<00:08:22.680> want 00:08:22.790 --> 00:08:22.800 align:start position:0% tokenizing asset transfer rights we want 00:08:22.800 --> 00:08:24.710 align:start position:0% tokenizing asset transfer rights we want to<00:08:22.919> enable<00:08:23.160> tokenizing<00:08:23.879> these<00:08:24.180> rights<00:08:24.539> to 00:08:24.710 --> 00:08:24.720 align:start position:0% to enable tokenizing these rights to 00:08:24.720 --> 00:08:27.110 align:start position:0% to enable tokenizing these rights to fungible<00:08:25.139> non-fungible<00:08:25.800> and<00:08:26.460> semi-fungible 00:08:27.110 --> 00:08:27.120 align:start position:0% fungible non-fungible and semi-fungible 00:08:27.120 --> 00:08:28.010 align:start position:0% fungible non-fungible and semi-fungible assets 00:08:28.010 --> 00:08:28.020 align:start position:0% assets 00:08:28.020 --> 00:08:29.150 align:start position:0% assets uh 00:08:29.150 --> 00:08:29.160 align:start position:0% uh 00:08:29.160 --> 00:08:31.850 align:start position:0% uh uh<00:08:29.400> and<00:08:29.819> one<00:08:30.240> of<00:08:30.419> two<00:08:30.660> things<00:08:30.900> it<00:08:31.379> means<00:08:31.620> is 00:08:31.850 --> 00:08:31.860 align:start position:0% uh and one of two things it means is 00:08:31.860 --> 00:08:34.190 align:start position:0% uh and one of two things it means is actually<00:08:32.099> to<00:08:32.399> enable<00:08:32.640> the<00:08:33.000> ATR<00:08:33.360> token<00:08:33.779> holder 00:08:34.190 --> 00:08:34.200 align:start position:0% actually to enable the ATR token holder 00:08:34.200 --> 00:08:37.550 align:start position:0% actually to enable the ATR token holder to<00:08:34.680> transfer<00:08:35.219> uh<00:08:35.820> the<00:08:36.060> assets<00:08:36.360> from<00:08:37.020> owner's 00:08:37.550 --> 00:08:37.560 align:start position:0% to transfer uh the assets from owner's 00:08:37.560 --> 00:08:40.250 align:start position:0% to transfer uh the assets from owner's wallet<00:08:37.860> so<00:08:38.399> you<00:08:38.700> don't<00:08:38.820> own<00:08:39.060> the<00:08:39.240> asset<00:08:39.659> but 00:08:40.250 --> 00:08:40.260 align:start position:0% wallet so you don't own the asset but 00:08:40.260 --> 00:08:42.529 align:start position:0% wallet so you don't own the asset but you<00:08:40.440> are<00:08:40.560> able<00:08:40.800> to<00:08:40.979> actually<00:08:41.159> transfer<00:08:41.760> it<00:08:41.880> and 00:08:42.529 --> 00:08:42.539 align:start position:0% you are able to actually transfer it and 00:08:42.539 --> 00:08:44.089 align:start position:0% you are able to actually transfer it and the<00:08:42.659> second<00:08:42.779> part<00:08:43.020> of<00:08:43.140> it<00:08:43.260> is<00:08:43.500> prevent<00:08:43.919> the 00:08:44.089 --> 00:08:44.099 align:start position:0% the second part of it is prevent the 00:08:44.099 --> 00:08:47.170 align:start position:0% the second part of it is prevent the owner<00:08:44.459> without<00:08:45.180> the<00:08:45.660> ATR<00:08:45.959> token 00:08:47.170 --> 00:08:47.180 align:start position:0% owner without the ATR token 00:08:47.180 --> 00:08:50.930 align:start position:0% owner without the ATR token without<00:08:48.180> the<00:08:48.420> ATR<00:08:48.720> token<00:08:49.080> to<00:08:49.560> transfer<00:08:49.980> it<00:08:50.100> so 00:08:50.930 --> 00:08:50.940 align:start position:0% without the ATR token to transfer it so 00:08:50.940 --> 00:08:52.850 align:start position:0% without the ATR token to transfer it so yeah<00:08:51.660> you<00:08:51.839> are<00:08:51.959> not<00:08:52.080> screwed<00:08:52.380> if<00:08:52.500> you<00:08:52.620> are<00:08:52.740> a 00:08:52.850 --> 00:08:52.860 align:start position:0% yeah you are not screwed if you are a 00:08:52.860 --> 00:08:55.490 align:start position:0% yeah you are not screwed if you are a token<00:08:53.160> holder 00:08:55.490 --> 00:08:55.500 align:start position:0% 00:08:55.500 --> 00:08:59.769 align:start position:0% foreign 00:08:59.769 --> 00:08:59.779 align:start position:0% 00:08:59.779 --> 00:09:02.690 align:start position:0% first<00:09:00.779> after<00:09:01.140> some<00:09:01.380> prototypes<00:09:02.040> we<00:09:02.279> try<00:09:02.519> to 00:09:02.690 --> 00:09:02.700 align:start position:0% first after some prototypes we try to 00:09:02.700 --> 00:09:05.110 align:start position:0% first after some prototypes we try to implement<00:09:03.240> our<00:09:03.660> own<00:09:03.899> smart<00:09:04.260> contract<00:09:04.620> wallet 00:09:05.110 --> 00:09:05.120 align:start position:0% implement our own smart contract wallet 00:09:05.120 --> 00:09:07.550 align:start position:0% implement our own smart contract wallet uh<00:09:06.120> which 00:09:07.550 --> 00:09:07.560 align:start position:0% uh which 00:09:07.560 --> 00:09:10.490 align:start position:0% uh which is<00:09:08.160> something<00:09:08.580> we<00:09:09.480> realize<00:09:09.839> we<00:09:10.080> don't<00:09:10.260> want<00:09:10.380> to 00:09:10.490 --> 00:09:10.500 align:start position:0% is something we realize we don't want to 00:09:10.500 --> 00:09:12.110 align:start position:0% is something we realize we don't want to do<00:09:10.680> because<00:09:11.220> we'll<00:09:11.580> be<00:09:11.820> basically 00:09:12.110 --> 00:09:12.120 align:start position:0% do because we'll be basically 00:09:12.120 --> 00:09:14.870 align:start position:0% do because we'll be basically Reinventing<00:09:12.899> the<00:09:13.019> wheel<00:09:13.200> so<00:09:14.160> after<00:09:14.519> some 00:09:14.870 --> 00:09:14.880 align:start position:0% Reinventing the wheel so after some 00:09:14.880 --> 00:09:18.710 align:start position:0% Reinventing the wheel so after some research<00:09:15.420> uh<00:09:16.320> of<00:09:16.680> uh<00:09:16.920> gnosis<00:09:17.459> save<00:09:17.720> we 00:09:18.710 --> 00:09:18.720 align:start position:0% research uh of uh gnosis save we 00:09:18.720 --> 00:09:21.050 align:start position:0% research uh of uh gnosis save we realized<00:09:19.200> they<00:09:19.500> have<00:09:19.740> uh<00:09:20.160> two<00:09:20.640> very<00:09:20.880> nice 00:09:21.050 --> 00:09:21.060 align:start position:0% realized they have uh two very nice 00:09:21.060 --> 00:09:23.329 align:start position:0% realized they have uh two very nice components<00:09:21.660> one<00:09:22.320> is<00:09:22.500> guard<00:09:22.680> and<00:09:23.040> one<00:09:23.220> is 00:09:23.329 --> 00:09:23.339 align:start position:0% components one is guard and one is 00:09:23.339 --> 00:09:25.730 align:start position:0% components one is guard and one is module<00:09:23.820> for<00:09:24.600> those<00:09:24.779> of<00:09:24.959> you<00:09:25.080> who<00:09:25.320> don't<00:09:25.440> know 00:09:25.730 --> 00:09:25.740 align:start position:0% module for those of you who don't know 00:09:25.740 --> 00:09:29.329 align:start position:0% module for those of you who don't know uh<00:09:26.279> the<00:09:26.519> safe<00:09:26.700> ecosystem<00:09:27.240> that<00:09:27.660> well<00:09:27.899> guard<00:09:28.800> is 00:09:29.329 --> 00:09:29.339 align:start position:0% uh the safe ecosystem that well guard is 00:09:29.339 --> 00:09:31.490 align:start position:0% uh the safe ecosystem that well guard is a<00:09:29.580> is<00:09:29.940> a<00:09:30.060> contract<00:09:30.480> which<00:09:30.779> you<00:09:30.899> can<00:09:31.080> basically 00:09:31.490 --> 00:09:31.500 align:start position:0% a is a contract which you can basically 00:09:31.500 --> 00:09:34.670 align:start position:0% a is a contract which you can basically link<00:09:31.800> to<00:09:32.100> your<00:09:32.220> Save<00:09:32.459> which<00:09:33.300> will<00:09:33.480> check<00:09:33.839> every 00:09:34.670 --> 00:09:34.680 align:start position:0% link to your Save which will check every 00:09:34.680 --> 00:09:37.250 align:start position:0% link to your Save which will check every transaction<00:09:35.220> made<00:09:35.580> from<00:09:35.820> your<00:09:36.000> save<00:09:36.300> for<00:09:36.899> uh 00:09:37.250 --> 00:09:37.260 align:start position:0% transaction made from your save for uh 00:09:37.260 --> 00:09:39.410 align:start position:0% transaction made from your save for uh at<00:09:37.560> the<00:09:37.680> like<00:09:38.040> before<00:09:38.339> and<00:09:38.940> after<00:09:39.120> the 00:09:39.410 --> 00:09:39.420 align:start position:0% at the like before and after the 00:09:39.420 --> 00:09:42.769 align:start position:0% at the like before and after the transaction<00:09:39.839> in<00:09:40.740> our<00:09:40.860> context<00:09:41.360> uh<00:09:42.360> it's<00:09:42.600> a 00:09:42.769 --> 00:09:42.779 align:start position:0% transaction in our context uh it's a 00:09:42.779 --> 00:09:45.110 align:start position:0% transaction in our context uh it's a guard<00:09:42.959> which<00:09:43.440> will<00:09:43.620> basically<00:09:44.160> enforce<00:09:44.760> the 00:09:45.110 --> 00:09:45.120 align:start position:0% guard which will basically enforce the 00:09:45.120 --> 00:09:48.829 align:start position:0% guard which will basically enforce the transfer<00:09:45.540> rules<00:09:45.839> okay<00:09:46.440> so<00:09:47.339> uh<00:09:47.880> if<00:09:48.240> if<00:09:48.420> we<00:09:48.660> see 00:09:48.829 --> 00:09:48.839 align:start position:0% transfer rules okay so uh if if we see 00:09:48.839 --> 00:09:52.130 align:start position:0% transfer rules okay so uh if if we see that<00:09:49.200> the<00:09:49.560> the<00:09:49.860> safe<00:09:50.220> has<00:09:51.180> the<00:09:51.420> ATR<00:09:51.779> token 00:09:52.130 --> 00:09:52.140 align:start position:0% that the the safe has the ATR token 00:09:52.140 --> 00:09:54.290 align:start position:0% that the the safe has the ATR token minted<00:09:52.560> but<00:09:52.980> it's<00:09:53.279> not<00:09:53.399> the<00:09:53.580> holder<00:09:53.940> will 00:09:54.290 --> 00:09:54.300 align:start position:0% minted but it's not the holder will 00:09:54.300 --> 00:09:56.690 align:start position:0% minted but it's not the holder will basically<00:09:54.720> revert<00:09:55.200> the<00:09:55.320> the<00:09:55.680> transaction<00:09:56.399> and 00:09:56.690 --> 00:09:56.700 align:start position:0% basically revert the the transaction and 00:09:56.700 --> 00:09:58.430 align:start position:0% basically revert the the transaction and that's<00:09:56.820> the<00:09:57.060> responsibility<00:09:57.480> of<00:09:57.779> the<00:09:57.899> Guard 00:09:58.430 --> 00:09:58.440 align:start position:0% that's the responsibility of the Guard 00:09:58.440 --> 00:10:01.570 align:start position:0% that's the responsibility of the Guard uh<00:09:59.040> the<00:09:59.279> second<00:09:59.399> component<00:10:00.000> is<00:10:00.360> a<00:10:00.540> module 00:10:01.570 --> 00:10:01.580 align:start position:0% uh the second component is a module 00:10:01.580 --> 00:10:05.509 align:start position:0% uh the second component is a module this<00:10:02.580> enables<00:10:03.120> to<00:10:04.080> execute<00:10:04.920> the<00:10:05.100> transaction 00:10:05.509 --> 00:10:05.519 align:start position:0% this enables to execute the transaction 00:10:05.519 --> 00:10:09.350 align:start position:0% this enables to execute the transaction without<00:10:06.360> actually<00:10:07.019> reaching<00:10:07.920> the<00:10:08.640> owner's 00:10:09.350 --> 00:10:09.360 align:start position:0% without actually reaching the owner's 00:10:09.360 --> 00:10:11.630 align:start position:0% without actually reaching the owner's threshold<00:10:09.779> which<00:10:10.680> is<00:10:10.800> also<00:10:11.100> something<00:10:11.339> we 00:10:11.630 --> 00:10:11.640 align:start position:0% threshold which is also something we 00:10:11.640 --> 00:10:13.610 align:start position:0% threshold which is also something we really<00:10:11.820> want<00:10:12.120> because<00:10:12.480> we<00:10:12.959> want<00:10:13.080> the<00:10:13.260> ATR 00:10:13.610 --> 00:10:13.620 align:start position:0% really want because we want the ATR 00:10:13.620 --> 00:10:15.590 align:start position:0% really want because we want the ATR token<00:10:14.040> holder<00:10:14.339> which<00:10:14.580> is<00:10:14.700> not<00:10:14.940> the<00:10:15.180> owner<00:10:15.480> of 00:10:15.590 --> 00:10:15.600 align:start position:0% token holder which is not the owner of 00:10:15.600 --> 00:10:18.470 align:start position:0% token holder which is not the owner of the<00:10:15.779> save<00:10:15.899> to<00:10:16.440> be<00:10:16.560> able<00:10:16.800> to<00:10:17.160> transfer<00:10:17.700> or<00:10:18.240> start 00:10:18.470 --> 00:10:18.480 align:start position:0% the save to be able to transfer or start 00:10:18.480 --> 00:10:20.570 align:start position:0% the save to be able to transfer or start the<00:10:18.660> execution<00:10:19.080> of<00:10:19.380> the<00:10:19.500> transfer<00:10:19.920> from 00:10:20.570 --> 00:10:20.580 align:start position:0% the execution of the transfer from 00:10:20.580 --> 00:10:22.009 align:start position:0% the execution of the transfer from someone<00:10:20.760> else's<00:10:21.240> safe 00:10:22.009 --> 00:10:22.019 align:start position:0% someone else's safe 00:10:22.019 --> 00:10:24.650 align:start position:0% someone else's safe so<00:10:22.620> yeah<00:10:22.980> that's<00:10:23.279> cool<00:10:23.459> with<00:10:23.940> these<00:10:24.540> two 00:10:24.650 --> 00:10:24.660 align:start position:0% so yeah that's cool with these two 00:10:24.660 --> 00:10:27.050 align:start position:0% so yeah that's cool with these two components<00:10:25.320> which<00:10:25.740> I<00:10:25.920> was<00:10:26.100> like<00:10:26.339> very 00:10:27.050 --> 00:10:27.060 align:start position:0% components which I was like very 00:10:27.060 --> 00:10:29.690 align:start position:0% components which I was like very surprised<00:10:27.480> they<00:10:27.720> have<00:10:28.100> we<00:10:29.100> were<00:10:29.279> able<00:10:29.580> to 00:10:29.690 --> 00:10:29.700 align:start position:0% surprised they have we were able to 00:10:29.700 --> 00:10:32.110 align:start position:0% surprised they have we were able to build<00:10:30.300> this 00:10:32.110 --> 00:10:32.120 align:start position:0% build this 00:10:32.120 --> 00:10:34.790 align:start position:0% build this ATR<00:10:33.120> smart<00:10:33.420> contract<00:10:33.839> on<00:10:34.080> top<00:10:34.200> of<00:10:34.320> agnosis 00:10:34.790 --> 00:10:34.800 align:start position:0% ATR smart contract on top of agnosis 00:10:34.800 --> 00:10:38.269 align:start position:0% ATR smart contract on top of agnosis Save<00:10:35.040> which<00:10:35.580> is<00:10:35.820> really<00:10:36.300> great 00:10:38.269 --> 00:10:38.279 align:start position:0% Save which is really great 00:10:38.279 --> 00:10:40.670 align:start position:0% Save which is really great uh<00:10:39.180> we<00:10:39.540> encountered<00:10:40.080> obviously<00:10:40.440> some 00:10:40.670 --> 00:10:40.680 align:start position:0% uh we encountered obviously some 00:10:40.680 --> 00:10:42.829 align:start position:0% uh we encountered obviously some challenges<00:10:41.100> so<00:10:42.000> we<00:10:42.120> will<00:10:42.300> talk<00:10:42.420> about<00:10:42.540> them 00:10:42.829 --> 00:10:42.839 align:start position:0% challenges so we will talk about them 00:10:42.839 --> 00:10:45.829 align:start position:0% challenges so we will talk about them right<00:10:43.080> now 00:10:45.829 --> 00:10:45.839 align:start position:0% 00:10:45.839 --> 00:10:48.889 align:start position:0% uh<00:10:46.680> first<00:10:46.980> is<00:10:47.339> approval<00:10:47.820> issue<00:10:48.180> while<00:10:48.420> minting 00:10:48.889 --> 00:10:48.899 align:start position:0% uh first is approval issue while minting 00:10:48.899 --> 00:10:51.590 align:start position:0% uh first is approval issue while minting an<00:10:49.019> ATR<00:10:49.380> token<00:10:49.740> uh<00:10:50.519> it's<00:10:50.700> pretty<00:10:50.880> obvious<00:10:51.240> that 00:10:51.590 --> 00:10:51.600 align:start position:0% an ATR token uh it's pretty obvious that 00:10:51.600 --> 00:10:53.750 align:start position:0% an ATR token uh it's pretty obvious that you<00:10:51.899> don't<00:10:52.079> want<00:10:52.320> to<00:10:52.500> Mint<00:10:52.680> an<00:10:52.860> ATR<00:10:53.220> token<00:10:53.579> and 00:10:53.750 --> 00:10:53.760 align:start position:0% you don't want to Mint an ATR token and 00:10:53.760 --> 00:10:55.630 align:start position:0% you don't want to Mint an ATR token and have<00:10:53.940> approved<00:10:54.360> addresses<00:10:54.839> at<00:10:55.079> the<00:10:55.200> same<00:10:55.320> time 00:10:55.630 --> 00:10:55.640 align:start position:0% have approved addresses at the same time 00:10:55.640 --> 00:10:59.030 align:start position:0% have approved addresses at the same time uh<00:10:56.640> because<00:10:57.060> if<00:10:57.540> you<00:10:57.660> if<00:10:57.899> you<00:10:58.079> do<00:10:58.260> the<00:10:58.680> approved 00:10:59.030 --> 00:10:59.040 align:start position:0% uh because if you if you do the approved 00:10:59.040 --> 00:11:01.430 align:start position:0% uh because if you if you do the approved address<00:10:59.160> can<00:10:59.519> transfer<00:11:00.000> the<00:11:00.779> the<00:11:00.959> asset 00:11:01.430 --> 00:11:01.440 align:start position:0% address can transfer the the asset 00:11:01.440 --> 00:11:03.949 align:start position:0% address can transfer the the asset without<00:11:01.980> even<00:11:02.339> triggering<00:11:02.880> the<00:11:03.240> the<00:11:03.420> guard<00:11:03.660> or 00:11:03.949 --> 00:11:03.959 align:start position:0% without even triggering the the guard or 00:11:03.959 --> 00:11:06.710 align:start position:0% without even triggering the the guard or the<00:11:04.140> module<00:11:04.500> so<00:11:05.279> this<00:11:05.579> is<00:11:05.700> obvious<00:11:06.060> like<00:11:06.480> a 00:11:06.710 --> 00:11:06.720 align:start position:0% the module so this is obvious like a 00:11:06.720 --> 00:11:09.470 align:start position:0% the module so this is obvious like a thing<00:11:07.019> we<00:11:07.200> have<00:11:07.380> to<00:11:07.500> we<00:11:07.800> have<00:11:07.860> to<00:11:08.040> solve<00:11:08.820> uh 00:11:09.470 --> 00:11:09.480 align:start position:0% thing we have to we have to solve uh 00:11:09.480 --> 00:11:11.269 align:start position:0% thing we have to we have to solve uh next<00:11:09.720> is<00:11:09.959> something<00:11:10.200> we<00:11:10.500> called<00:11:10.680> stalking 00:11:11.269 --> 00:11:11.279 align:start position:0% next is something we called stalking 00:11:11.279 --> 00:11:13.910 align:start position:0% next is something we called stalking attack<00:11:11.720> it's<00:11:12.720> basically<00:11:13.200> a<00:11:13.500> type<00:11:13.620> of<00:11:13.740> attack 00:11:13.910 --> 00:11:13.920 align:start position:0% attack it's basically a type of attack 00:11:13.920 --> 00:11:17.690 align:start position:0% attack it's basically a type of attack where<00:11:14.820> uh<00:11:15.600> I<00:11:15.839> as<00:11:15.959> an<00:11:16.140> attacker<00:11:16.560> will<00:11:17.100> create<00:11:17.399> a 00:11:17.690 --> 00:11:17.700 align:start position:0% where uh I as an attacker will create a 00:11:17.700 --> 00:11:19.970 align:start position:0% where uh I as an attacker will create a malicious<00:11:18.060> asset<00:11:18.420> I<00:11:19.019> will<00:11:19.200> tokenize<00:11:19.680> its 00:11:19.970 --> 00:11:19.980 align:start position:0% malicious asset I will tokenize its 00:11:19.980 --> 00:11:22.730 align:start position:0% malicious asset I will tokenize its transfer<00:11:20.279> rights<00:11:20.640> I<00:11:21.240> will<00:11:21.420> transfer<00:11:21.899> it<00:11:22.019> to<00:11:22.560> my 00:11:22.730 --> 00:11:22.740 align:start position:0% transfer rights I will transfer it to my 00:11:22.740 --> 00:11:25.970 align:start position:0% transfer rights I will transfer it to my victim's<00:11:23.220> wallet<00:11:23.579> and<00:11:24.360> remove<00:11:25.019> it<00:11:25.380> with<00:11:25.800> some 00:11:25.970 --> 00:11:25.980 align:start position:0% victim's wallet and remove it with some 00:11:25.980 --> 00:11:28.190 align:start position:0% victim's wallet and remove it with some non-standard<00:11:26.579> way<00:11:26.820> so<00:11:27.360> let's<00:11:27.480> say<00:11:27.660> the<00:11:27.899> asset 00:11:28.190 --> 00:11:28.200 align:start position:0% non-standard way so let's say the asset 00:11:28.200 --> 00:11:30.470 align:start position:0% non-standard way so let's say the asset can<00:11:28.440> be<00:11:28.560> transferred<00:11:29.040> by<00:11:29.160> the<00:11:29.339> owner<00:11:29.640> I'll<00:11:30.180> I 00:11:30.470 --> 00:11:30.480 align:start position:0% can be transferred by the owner I'll I 00:11:30.480 --> 00:11:33.290 align:start position:0% can be transferred by the owner I'll I as<00:11:30.600> an<00:11:30.720> attacker<00:11:31.019> am<00:11:31.620> the<00:11:31.860> owner<00:11:32.160> so<00:11:32.820> I'll<00:11:33.120> be 00:11:33.290 --> 00:11:33.300 align:start position:0% as an attacker am the owner so I'll be 00:11:33.300 --> 00:11:35.630 align:start position:0% as an attacker am the owner so I'll be able<00:11:33.540> to<00:11:33.660> uh<00:11:34.200> to<00:11:34.440> withdraw<00:11:34.740> that 00:11:35.630 --> 00:11:35.640 align:start position:0% able to uh to withdraw that 00:11:35.640 --> 00:11:38.930 align:start position:0% able to uh to withdraw that in<00:11:36.300> that<00:11:36.480> case<00:11:36.720> the<00:11:37.320> victim's<00:11:37.740> wallet<00:11:38.160> goes 00:11:38.930 --> 00:11:38.940 align:start position:0% in that case the victim's wallet goes 00:11:38.940 --> 00:11:42.050 align:start position:0% in that case the victim's wallet goes into<00:11:39.380> uh<00:11:40.380> Interstate<00:11:40.980> where<00:11:41.339> every<00:11:41.579> execution 00:11:42.050 --> 00:11:42.060 align:start position:0% into uh Interstate where every execution 00:11:42.060 --> 00:11:45.350 align:start position:0% into uh Interstate where every execution will<00:11:42.300> fail<00:11:42.600> because<00:11:43.320> the<00:11:43.740> guard<00:11:43.860> will<00:11:44.360> not 00:11:45.350 --> 00:11:45.360 align:start position:0% will fail because the guard will not 00:11:45.360 --> 00:11:47.449 align:start position:0% will fail because the guard will not have<00:11:45.660> the<00:11:46.140> proper<00:11:46.740> like<00:11:46.980> sufficient 00:11:47.449 --> 00:11:47.459 align:start position:0% have the proper like sufficient 00:11:47.459 --> 00:11:50.329 align:start position:0% have the proper like sufficient tokenized<00:11:48.180> balance<00:11:48.480> so<00:11:49.260> it's<00:11:49.380> also<00:11:49.620> bad 00:11:50.329 --> 00:11:50.339 align:start position:0% tokenized balance so it's also bad 00:11:50.339 --> 00:11:53.150 align:start position:0% tokenized balance so it's also bad uh<00:11:50.940> then<00:11:51.120> we<00:11:51.300> have<00:11:51.420> challenges<00:11:51.779> like<00:11:51.959> EIP<00:11:52.320> 1271 00:11:53.150 --> 00:11:53.160 align:start position:0% uh then we have challenges like EIP 1271 00:11:53.160 --> 00:11:55.610 align:start position:0% uh then we have challenges like EIP 1271 where<00:11:53.940> the<00:11:54.300> input<00:11:54.540> of<00:11:54.720> the<00:11:54.899> function<00:11:55.200> is 00:11:55.610 --> 00:11:55.620 align:start position:0% where the input of the function is 00:11:55.620 --> 00:11:58.250 align:start position:0% where the input of the function is basically<00:11:55.860> just<00:11:56.040> hash<00:11:56.279> and<00:11:56.579> signature<00:11:57.000> so<00:11:57.839> we 00:11:58.250 --> 00:11:58.260 align:start position:0% basically just hash and signature so we 00:11:58.260 --> 00:12:01.130 align:start position:0% basically just hash and signature so we cannot<00:11:58.620> like<00:11:58.980> uh<00:11:59.820> enforce<00:12:00.300> the<00:12:00.480> rules<00:12:00.720> if<00:12:01.019> we 00:12:01.130 --> 00:12:01.140 align:start position:0% cannot like uh enforce the rules if we 00:12:01.140 --> 00:12:02.810 align:start position:0% cannot like uh enforce the rules if we don't<00:12:01.320> know<00:12:01.500> what<00:12:01.800> is<00:12:02.160> actually<00:12:02.459> like 00:12:02.810 --> 00:12:02.820 align:start position:0% don't know what is actually like 00:12:02.820 --> 00:12:05.569 align:start position:0% don't know what is actually like verifying<00:12:03.540> uh<00:12:04.500> then<00:12:04.800> there<00:12:05.100> is<00:12:05.279> a<00:12:05.399> gas 00:12:05.569 --> 00:12:05.579 align:start position:0% verifying uh then there is a gas 00:12:05.579 --> 00:12:07.550 align:start position:0% verifying uh then there is a gas overhead<00:12:06.060> it's<00:12:06.600> a<00:12:06.720> contract<00:12:07.019> wallet<00:12:07.380> it's 00:12:07.550 --> 00:12:07.560 align:start position:0% overhead it's a contract wallet it's 00:12:07.560 --> 00:12:09.650 align:start position:0% overhead it's a contract wallet it's always<00:12:07.800> will<00:12:08.160> be<00:12:08.339> there<00:12:08.940> always<00:12:09.060> will<00:12:09.360> be<00:12:09.480> some 00:12:09.650 --> 00:12:09.660 align:start position:0% always will be there always will be some 00:12:09.660 --> 00:12:11.389 align:start position:0% always will be there always will be some gas<00:12:09.779> overhead<00:12:10.260> plus<00:12:10.680> there<00:12:10.920> is<00:12:11.040> a<00:12:11.160> lot<00:12:11.220> of 00:12:11.389 --> 00:12:11.399 align:start position:0% gas overhead plus there is a lot of 00:12:11.399 --> 00:12:14.389 align:start position:0% gas overhead plus there is a lot of checks<00:12:11.880> for<00:12:12.360> every<00:12:12.540> execution<00:12:13.019> right 00:12:14.389 --> 00:12:14.399 align:start position:0% checks for every execution right 00:12:14.399 --> 00:12:17.110 align:start position:0% checks for every execution right uh<00:12:15.240> then<00:12:15.540> there<00:12:15.839> is<00:12:16.019> the<00:12:16.140> non-standard<00:12:16.680> assets 00:12:17.110 --> 00:12:17.120 align:start position:0% uh then there is the non-standard assets 00:12:17.120 --> 00:12:20.690 align:start position:0% uh then there is the non-standard assets uh<00:12:18.120> we<00:12:18.720> have<00:12:18.899> we<00:12:19.320> currently<00:12:19.740> support<00:12:20.040> just<00:12:20.519> the 00:12:20.690 --> 00:12:20.700 align:start position:0% uh we have we currently support just the 00:12:20.700 --> 00:12:21.769 align:start position:0% uh we have we currently support just the standards<00:12:21.060> we<00:12:21.420> cannot<00:12:21.660> support 00:12:21.769 --> 00:12:21.779 align:start position:0% standards we cannot support 00:12:21.779 --> 00:12:23.870 align:start position:0% standards we cannot support non-standards<00:12:22.620> asset<00:12:22.980> because<00:12:23.339> we<00:12:23.700> are 00:12:23.870 --> 00:12:23.880 align:start position:0% non-standards asset because we are 00:12:23.880 --> 00:12:25.910 align:start position:0% non-standards asset because we are actually<00:12:24.000> enforcing<00:12:24.600> the<00:12:24.779> the<00:12:25.079> the<00:12:25.140> transfer 00:12:25.910 --> 00:12:25.920 align:start position:0% actually enforcing the the the transfer 00:12:25.920 --> 00:12:29.269 align:start position:0% actually enforcing the the the transfer rules<00:12:26.339> right<00:12:26.660> uh<00:12:27.660> so<00:12:28.079> yeah<00:12:28.800> that's<00:12:28.980> one 00:12:29.269 --> 00:12:29.279 align:start position:0% rules right uh so yeah that's one 00:12:29.279 --> 00:12:30.110 align:start position:0% rules right uh so yeah that's one challenge 00:12:30.110 --> 00:12:30.120 align:start position:0% challenge 00:12:30.120 --> 00:12:33.949 align:start position:0% challenge and<00:12:30.959> not<00:12:31.440> possibly<00:12:32.180> not<00:12:33.180> possible<00:12:33.480> to<00:12:33.660> use<00:12:33.779> the 00:12:33.949 --> 00:12:33.959 align:start position:0% and not possibly not possible to use the 00:12:33.959 --> 00:12:35.810 align:start position:0% and not possibly not possible to use the delegates<00:12:34.380> goal<00:12:34.800> because<00:12:35.160> then<00:12:35.459> it<00:12:35.760> will 00:12:35.810 --> 00:12:35.820 align:start position:0% delegates goal because then it will 00:12:35.820 --> 00:12:37.490 align:start position:0% delegates goal because then it will alter<00:12:36.180> the<00:12:36.360> logic<00:12:36.660> of<00:12:36.779> the<00:12:36.899> smart<00:12:37.019> contract 00:12:37.490 --> 00:12:37.500 align:start position:0% alter the logic of the smart contract 00:12:37.500 --> 00:12:39.590 align:start position:0% alter the logic of the smart contract and<00:12:38.040> again<00:12:38.160> you<00:12:38.459> are<00:12:38.579> you<00:12:38.940> are<00:12:39.060> able<00:12:39.240> to<00:12:39.420> to 00:12:39.590 --> 00:12:39.600 align:start position:0% and again you are you are able to to 00:12:39.600 --> 00:12:41.329 align:start position:0% and again you are you are able to to transfer<00:12:40.200> it<00:12:40.320> or<00:12:40.440> do<00:12:40.560> whatever<00:12:40.740> you<00:12:41.040> want<00:12:41.160> with 00:12:41.329 --> 00:12:41.339 align:start position:0% transfer it or do whatever you want with 00:12:41.339 --> 00:12:42.769 align:start position:0% transfer it or do whatever you want with it 00:12:42.769 --> 00:12:42.779 align:start position:0% it 00:12:42.779 --> 00:12:46.910 align:start position:0% it so<00:12:43.200> let's<00:12:43.320> talk<00:12:43.500> about<00:12:43.680> the<00:12:43.980> first<00:12:44.100> one 00:12:46.910 --> 00:12:46.920 align:start position:0% 00:12:46.920 --> 00:12:48.829 align:start position:0% yeah<00:12:47.339> uh 00:12:48.829 --> 00:12:48.839 align:start position:0% yeah uh 00:12:48.839 --> 00:12:51.050 align:start position:0% yeah uh approval<00:12:49.260> issue<00:12:49.500> while<00:12:49.620> minting<00:12:49.980> ATR<00:12:50.339> token 00:12:51.050 --> 00:12:51.060 align:start position:0% approval issue while minting ATR token 00:12:51.060 --> 00:12:54.410 align:start position:0% approval issue while minting ATR token uh<00:12:51.899> uh<00:12:52.079> we<00:12:52.380> need<00:12:52.500> to<00:12:52.620> check<00:12:52.860> that<00:12:53.459> the<00:12:54.120> the 00:12:54.410 --> 00:12:54.420 align:start position:0% uh uh we need to check that the the 00:12:54.420 --> 00:12:57.470 align:start position:0% uh uh we need to check that the the asset<00:12:54.779> which<00:12:55.139> is<00:12:55.620> going<00:12:55.860> to<00:12:56.100> uh 00:12:57.470 --> 00:12:57.480 align:start position:0% asset which is going to uh 00:12:57.480 --> 00:12:59.569 align:start position:0% asset which is going to uh the<00:12:57.959> asset<00:12:58.200> which<00:12:58.380> ATR<00:12:58.920> is<00:12:59.220> going<00:12:59.339> to<00:12:59.459> be 00:12:59.569 --> 00:12:59.579 align:start position:0% the asset which ATR is going to be 00:12:59.579 --> 00:13:02.030 align:start position:0% the asset which ATR is going to be minted<00:13:00.019> uh<00:13:01.019> doesn't<00:13:01.260> have<00:13:01.500> the<00:13:01.620> approved 00:13:02.030 --> 00:13:02.040 align:start position:0% minted uh doesn't have the approved 00:13:02.040 --> 00:13:04.490 align:start position:0% minted uh doesn't have the approved address<00:13:02.420> currently<00:13:03.420> there<00:13:03.779> is<00:13:03.899> like<00:13:04.139> four 00:13:04.490 --> 00:13:04.500 align:start position:0% address currently there is like four 00:13:04.500 --> 00:13:07.310 align:start position:0% address currently there is like four types<00:13:04.860> of<00:13:04.980> of<00:13:05.339> approvals<00:13:06.000> for<00:13:06.240> erc20<00:13:06.839> it's 00:13:07.310 --> 00:13:07.320 align:start position:0% types of of approvals for erc20 it's 00:13:07.320 --> 00:13:10.790 align:start position:0% types of of approvals for erc20 it's approval<00:13:07.980> amount<00:13:08.459> for<00:13:08.940> ERC<00:13:09.360> 721<00:13:10.079> it's<00:13:10.380> a<00:13:10.560> proof 00:13:10.790 --> 00:13:10.800 align:start position:0% approval amount for ERC 721 it's a proof 00:13:10.800 --> 00:13:14.210 align:start position:0% approval amount for ERC 721 it's a proof ID<00:13:10.980> or<00:13:11.339> set<00:13:11.639> approval<00:13:12.060> for<00:13:12.180> all<00:13:12.420> and<00:13:13.380> for<00:13:13.740> ERC 00:13:14.210 --> 00:13:14.220 align:start position:0% ID or set approval for all and for ERC 00:13:14.220 --> 00:13:17.150 align:start position:0% ID or set approval for all and for ERC 1155<00:13:14.880> it's<00:13:15.300> that<00:13:15.600> you<00:13:15.779> just<00:13:16.380> set<00:13:16.560> approval<00:13:17.040> for 00:13:17.150 --> 00:13:17.160 align:start position:0% 1155 it's that you just set approval for 00:13:17.160 --> 00:13:19.550 align:start position:0% 1155 it's that you just set approval for all<00:13:17.339> only<00:13:18.180> one<00:13:18.480> of<00:13:18.660> these<00:13:18.839> approved<00:13:19.260> function 00:13:19.550 --> 00:13:19.560 align:start position:0% all only one of these approved function 00:13:19.560 --> 00:13:22.250 align:start position:0% all only one of these approved function has<00:13:20.040> actually<00:13:20.399> a<00:13:20.700> getter<00:13:21.060> for<00:13:21.300> the<00:13:21.480> address 00:13:22.250 --> 00:13:22.260 align:start position:0% has actually a getter for the address 00:13:22.260 --> 00:13:25.190 align:start position:0% has actually a getter for the address uh<00:13:22.920> so<00:13:23.160> it's<00:13:23.459> it<00:13:23.579> was<00:13:23.940> a<00:13:24.060> big<00:13:24.180> issue<00:13:24.420> at<00:13:24.600> first 00:13:25.190 --> 00:13:25.200 align:start position:0% uh so it's it was a big issue at first 00:13:25.200 --> 00:13:27.949 align:start position:0% uh so it's it was a big issue at first but<00:13:25.920> after<00:13:26.399> realizing<00:13:27.120> that<00:13:27.480> all<00:13:27.779> the 00:13:27.949 --> 00:13:27.959 align:start position:0% but after realizing that all the 00:13:27.959 --> 00:13:30.110 align:start position:0% but after realizing that all the approval<00:13:28.380> ex<00:13:28.620> or<00:13:29.040> all<00:13:29.459> the<00:13:29.579> transactions 00:13:30.110 --> 00:13:30.120 align:start position:0% approval ex or all the transactions 00:13:30.120 --> 00:13:32.870 align:start position:0% approval ex or all the transactions which<00:13:30.360> are<00:13:30.600> approving<00:13:31.200> the<00:13:31.440> the<00:13:31.800> assets<00:13:32.220> are 00:13:32.870 --> 00:13:32.880 align:start position:0% which are approving the the assets are 00:13:32.880 --> 00:13:35.269 align:start position:0% which are approving the the assets are done<00:13:33.120> through<00:13:33.600> the<00:13:33.839> wallet<00:13:34.139> then<00:13:34.920> we<00:13:35.160> can 00:13:35.269 --> 00:13:35.279 align:start position:0% done through the wallet then we can 00:13:35.279 --> 00:13:37.009 align:start position:0% done through the wallet then we can basically<00:13:35.639> just<00:13:35.880> track<00:13:36.120> all<00:13:36.480> the<00:13:36.660> all<00:13:36.899> the 00:13:37.009 --> 00:13:37.019 align:start position:0% basically just track all the all the 00:13:37.019 --> 00:13:40.009 align:start position:0% basically just track all the all the approved<00:13:37.380> addresses<00:13:37.860> and<00:13:38.700> uh<00:13:39.120> on<00:13:39.600> the<00:13:39.720> time<00:13:39.839> of 00:13:40.009 --> 00:13:40.019 align:start position:0% approved addresses and uh on the time of 00:13:40.019 --> 00:13:41.750 align:start position:0% approved addresses and uh on the time of minting<00:13:40.440> we<00:13:40.680> can<00:13:40.800> check<00:13:40.980> that<00:13:41.160> the<00:13:41.339> asset<00:13:41.579> is 00:13:41.750 --> 00:13:41.760 align:start position:0% minting we can check that the asset is 00:13:41.760 --> 00:13:44.870 align:start position:0% minting we can check that the asset is not<00:13:41.940> uh<00:13:42.660> doesn't<00:13:42.959> have<00:13:43.320> uh<00:13:44.160> An<00:13:44.459> approved 00:13:44.870 --> 00:13:44.880 align:start position:0% not uh doesn't have uh An approved 00:13:44.880 --> 00:13:48.290 align:start position:0% not uh doesn't have uh An approved address<00:13:45.079> so<00:13:46.079> yeah<00:13:46.620> cool<00:13:46.920> we<00:13:47.459> need<00:13:47.700> to<00:13:47.820> we<00:13:48.180> need 00:13:48.290 --> 00:13:48.300 align:start position:0% address so yeah cool we need to we need 00:13:48.300 --> 00:13:50.990 align:start position:0% address so yeah cool we need to we need to<00:13:48.420> check<00:13:48.540> the<00:13:48.720> approved<00:13:49.019> addresses 00:13:50.990 --> 00:13:51.000 align:start position:0% to check the approved addresses 00:13:51.000 --> 00:13:53.690 align:start position:0% to check the approved addresses the<00:13:51.480> stalking<00:13:51.839> attack<00:13:52.220> how<00:13:53.220> I<00:13:53.339> described 00:13:53.690 --> 00:13:53.700 align:start position:0% the stalking attack how I described 00:13:53.700 --> 00:13:56.389 align:start position:0% the stalking attack how I described previously<00:13:54.120> uh<00:13:54.959> it's<00:13:55.500> it's<00:13:55.860> the<00:13:56.040> malicious 00:13:56.389 --> 00:13:56.399 align:start position:0% previously uh it's it's the malicious 00:13:56.399 --> 00:13:57.889 align:start position:0% previously uh it's it's the malicious asset<00:13:56.820> which<00:13:57.060> is<00:13:57.180> transferred<00:13:57.600> from<00:13:57.720> the 00:13:57.889 --> 00:13:57.899 align:start position:0% asset which is transferred from the 00:13:57.899 --> 00:14:00.009 align:start position:0% asset which is transferred from the victim's<00:13:58.260> wallet<00:13:58.560> by<00:13:59.040> the<00:13:59.279> non-standard<00:13:59.820> way 00:14:00.009 --> 00:14:00.019 align:start position:0% victim's wallet by the non-standard way 00:14:00.019 --> 00:14:02.690 align:start position:0% victim's wallet by the non-standard way uh<00:14:01.019> it<00:14:01.200> would<00:14:01.320> revert<00:14:01.800> on<00:14:02.100> insufficient 00:14:02.690 --> 00:14:02.700 align:start position:0% uh it would revert on insufficient 00:14:02.700 --> 00:14:04.370 align:start position:0% uh it would revert on insufficient tokenized<00:14:03.180> balance 00:14:04.370 --> 00:14:04.380 align:start position:0% tokenized balance 00:14:04.380 --> 00:14:07.730 align:start position:0% tokenized balance and<00:14:05.100> but<00:14:05.339> we<00:14:05.639> don't<00:14:05.820> we<00:14:06.540> still<00:14:06.720> want<00:14:07.079> the<00:14:07.440> ATR 00:14:07.730 --> 00:14:07.740 align:start position:0% and but we don't we still want the ATR 00:14:07.740 --> 00:14:09.650 align:start position:0% and but we don't we still want the ATR token<00:14:08.100> holder<00:14:08.399> to<00:14:08.820> be<00:14:08.940> able<00:14:09.060> to<00:14:09.240> transfer<00:14:09.540> it 00:14:09.650 --> 00:14:09.660 align:start position:0% token holder to be able to transfer it 00:14:09.660 --> 00:14:10.970 align:start position:0% token holder to be able to transfer it to<00:14:09.839> any<00:14:09.959> asset 00:14:10.970 --> 00:14:10.980 align:start position:0% to any asset 00:14:10.980 --> 00:14:13.069 align:start position:0% to any asset so<00:14:11.399> because<00:14:11.579> of<00:14:11.760> that<00:14:11.940> we<00:14:12.180> need<00:14:12.300> to<00:14:12.600> basically 00:14:13.069 --> 00:14:13.079 align:start position:0% so because of that we need to basically 00:14:13.079 --> 00:14:15.590 align:start position:0% so because of that we need to basically divide<00:14:13.500> the<00:14:13.800> transfer<00:14:14.160> function<00:14:14.399> into<00:14:14.639> two<00:14:14.880> uh 00:14:15.590 --> 00:14:15.600 align:start position:0% divide the transfer function into two uh 00:14:15.600 --> 00:14:19.250 align:start position:0% divide the transfer function into two uh first<00:14:15.779> disclaim<00:14:16.339> where<00:14:17.339> uh<00:14:17.760> I<00:14:17.940> as<00:14:18.120> a<00:14:18.360> ATR<00:14:18.899> token 00:14:19.250 --> 00:14:19.260 align:start position:0% first disclaim where uh I as a ATR token 00:14:19.260 --> 00:14:21.410 align:start position:0% first disclaim where uh I as a ATR token holder<00:14:19.620> and<00:14:20.160> transferring<00:14:20.639> the<00:14:20.760> asset<00:14:21.060> to<00:14:21.240> my 00:14:21.410 --> 00:14:21.420 align:start position:0% holder and transferring the asset to my 00:14:21.420 --> 00:14:23.990 align:start position:0% holder and transferring the asset to my wallet<00:14:21.839> which<00:14:22.440> is<00:14:22.560> cool<00:14:22.740> there<00:14:23.700> is<00:14:23.820> no 00:14:23.990 --> 00:14:24.000 align:start position:0% wallet which is cool there is no 00:14:24.000 --> 00:14:26.389 align:start position:0% wallet which is cool there is no possibility<00:14:24.420> of<00:14:24.660> stocking<00:14:25.079> attacks<00:14:25.440> so<00:14:25.680> yeah 00:14:26.389 --> 00:14:26.399 align:start position:0% possibility of stocking attacks so yeah 00:14:26.399 --> 00:14:29.269 align:start position:0% possibility of stocking attacks so yeah we'll<00:14:27.180> let<00:14:27.360> you<00:14:27.480> do<00:14:27.600> that<00:14:27.720> and<00:14:28.380> the<00:14:28.500> second<00:14:28.680> is 00:14:29.269 --> 00:14:29.279 align:start position:0% we'll let you do that and the second is 00:14:29.279 --> 00:14:31.910 align:start position:0% we'll let you do that and the second is the<00:14:29.639> generic<00:14:30.120> transfer<00:14:30.540> to<00:14:30.839> any<00:14:31.019> address<00:14:31.260> but 00:14:31.910 --> 00:14:31.920 align:start position:0% the generic transfer to any address but 00:14:31.920 --> 00:14:34.490 align:start position:0% the generic transfer to any address but in<00:14:32.160> that<00:14:32.339> case<00:14:32.519> uh<00:14:33.180> we<00:14:33.420> require<00:14:33.600> the<00:14:34.139> recipient 00:14:34.490 --> 00:14:34.500 align:start position:0% in that case uh we require the recipient 00:14:34.500 --> 00:14:35.569 align:start position:0% in that case uh we require the recipient permission 00:14:35.569 --> 00:14:35.579 align:start position:0% permission 00:14:35.579 --> 00:14:40.009 align:start position:0% permission uh<00:14:36.420> in<00:14:36.899> this<00:14:37.019> permission<00:14:37.380> uh<00:14:38.339> the<00:14:39.180> uh<00:14:39.779> the 00:14:40.009 --> 00:14:40.019 align:start position:0% uh in this permission uh the uh the 00:14:40.019 --> 00:14:42.230 align:start position:0% uh in this permission uh the uh the recipient<00:14:40.320> can<00:14:40.680> actually<00:14:40.920> specify<00:14:41.519> what<00:14:42.060> type 00:14:42.230 --> 00:14:42.240 align:start position:0% recipient can actually specify what type 00:14:42.240 --> 00:14:44.269 align:start position:0% recipient can actually specify what type of<00:14:42.300> asset<00:14:42.720> is<00:14:42.899> going<00:14:43.079> to<00:14:43.139> be<00:14:43.260> transferred<00:14:43.740> by 00:14:44.269 --> 00:14:44.279 align:start position:0% of asset is going to be transferred by 00:14:44.279 --> 00:14:46.970 align:start position:0% of asset is going to be transferred by whom<00:14:44.600> uh<00:14:45.600> some<00:14:45.839> expiration<00:14:46.260> stuff<00:14:46.560> and<00:14:46.740> so<00:14:46.860> on 00:14:46.970 --> 00:14:46.980 align:start position:0% whom uh some expiration stuff and so on 00:14:46.980 --> 00:14:50.269 align:start position:0% whom uh some expiration stuff and so on and<00:14:47.100> so<00:14:47.220> on<00:14:47.339> so<00:14:48.120> it's<00:14:49.019> much<00:14:49.380> harder<00:14:49.800> for<00:14:50.100> an 00:14:50.269 --> 00:14:50.279 align:start position:0% and so on so it's much harder for an 00:14:50.279 --> 00:14:52.009 align:start position:0% and so on so it's much harder for an attacker<00:14:50.699> to<00:14:51.000> actually<00:14:51.180> execute<00:14:51.839> this 00:14:52.009 --> 00:14:52.019 align:start position:0% attacker to actually execute this 00:14:52.019 --> 00:14:54.410 align:start position:0% attacker to actually execute this stalking<00:14:52.380> attack<00:14:52.500> it's<00:14:53.339> still<00:14:53.579> possible<00:14:53.940> but 00:14:54.410 --> 00:14:54.420 align:start position:0% stalking attack it's still possible but 00:14:54.420 --> 00:14:57.350 align:start position:0% stalking attack it's still possible but it's<00:14:54.779> much<00:14:55.079> much<00:14:55.260> much<00:14:55.320> harder<00:14:56.399> uh<00:14:57.000> but<00:14:57.240> still 00:14:57.350 --> 00:14:57.360 align:start position:0% it's much much much harder uh but still 00:14:57.360 --> 00:14:59.150 align:start position:0% it's much much much harder uh but still because<00:14:57.660> it's<00:14:57.899> it's<00:14:58.019> possible<00:14:58.560> we<00:14:58.860> need<00:14:58.980> to 00:14:59.150 --> 00:14:59.160 align:start position:0% because it's it's possible we need to 00:14:59.160 --> 00:15:01.730 align:start position:0% because it's it's possible we need to implement<00:14:59.459> a<00:14:59.699> function<00:15:00.000> uh<00:15:00.540> to<00:15:00.779> recover<00:15:01.199> the 00:15:01.730 --> 00:15:01.740 align:start position:0% implement a function uh to recover the 00:15:01.740 --> 00:15:04.009 align:start position:0% implement a function uh to recover the safe<00:15:01.920> from<00:15:02.339> from<00:15:03.000> that<00:15:03.180> attack 00:15:04.009 --> 00:15:04.019 align:start position:0% safe from from that attack 00:15:04.019 --> 00:15:05.629 align:start position:0% safe from from that attack which<00:15:04.560> we<00:15:04.860> did 00:15:05.629 --> 00:15:05.639 align:start position:0% which we did 00:15:05.639 --> 00:15:07.970 align:start position:0% which we did that's<00:15:06.180> a<00:15:06.300> good<00:15:06.420> one 00:15:07.970 --> 00:15:07.980 align:start position:0% that's a good one 00:15:07.980 --> 00:15:11.449 align:start position:0% that's a good one so<00:15:08.820> uh<00:15:09.360> after<00:15:09.779> solving<00:15:10.199> some<00:15:10.380> challenges<00:15:10.860> uh 00:15:11.449 --> 00:15:11.459 align:start position:0% so uh after solving some challenges uh 00:15:11.459 --> 00:15:13.790 align:start position:0% so uh after solving some challenges uh the<00:15:11.760> the<00:15:12.000> final<00:15:12.240> design<00:15:12.480> looks<00:15:12.899> like<00:15:13.019> this 00:15:13.790 --> 00:15:13.800 align:start position:0% the the final design looks like this 00:15:13.800 --> 00:15:15.769 align:start position:0% the the final design looks like this we<00:15:14.699> actually 00:15:15.769 --> 00:15:15.779 align:start position:0% we actually 00:15:15.779 --> 00:15:18.889 align:start position:0% we actually uh<00:15:16.560> right<00:15:16.980> you<00:15:17.160> can<00:15:17.339> see<00:15:17.519> the<00:15:17.760> the<00:15:17.940> ATR<00:15:18.480> token 00:15:18.889 --> 00:15:18.899 align:start position:0% uh right you can see the the ATR token 00:15:18.899 --> 00:15:22.250 align:start position:0% uh right you can see the the ATR token or<00:15:19.199> the<00:15:19.320> ATR<00:15:19.740> module<00:15:20.220> uh<00:15:21.180> here<00:15:21.420> is<00:15:21.540> the<00:15:21.839> here's 00:15:22.250 --> 00:15:22.260 align:start position:0% or the ATR module uh here is the here's 00:15:22.260 --> 00:15:23.509 align:start position:0% or the ATR module uh here is the here's the<00:15:22.440> guard 00:15:23.509 --> 00:15:23.519 align:start position:0% the guard 00:15:23.519 --> 00:15:26.329 align:start position:0% the guard uh<00:15:23.940> it's<00:15:24.120> implemented<00:15:24.540> as<00:15:24.779> a<00:15:24.899> proxy<00:15:25.339> for 00:15:26.329 --> 00:15:26.339 align:start position:0% uh it's implemented as a proxy for 00:15:26.339 --> 00:15:29.689 align:start position:0% uh it's implemented as a proxy for basically<00:15:26.940> be<00:15:27.360> more<00:15:27.600> future<00:15:27.959> proof<00:15:28.440> If<00:15:29.339> there 00:15:29.689 --> 00:15:29.699 align:start position:0% basically be more future proof If there 00:15:29.699 --> 00:15:32.990 align:start position:0% basically be more future proof If there is<00:15:29.880> some<00:15:30.060> widely<00:15:30.480> adapted<00:15:30.899> ERC<00:15:31.639> which<00:15:32.639> we<00:15:32.820> want 00:15:32.990 --> 00:15:33.000 align:start position:0% is some widely adapted ERC which we want 00:15:33.000 --> 00:15:35.810 align:start position:0% is some widely adapted ERC which we want to<00:15:33.180> we<00:15:33.899> want<00:15:34.019> to<00:15:34.139> like<00:15:34.380> support<00:15:34.800> we<00:15:35.339> don't<00:15:35.519> want 00:15:35.810 --> 00:15:35.820 align:start position:0% to we want to like support we don't want 00:15:35.820 --> 00:15:39.170 align:start position:0% to we want to like support we don't want to<00:15:36.000> force<00:15:36.600> every<00:15:37.139> uh<00:15:37.680> like<00:15:37.980> safe<00:15:38.339> owner<00:15:38.820> to 00:15:39.170 --> 00:15:39.180 align:start position:0% to force every uh like safe owner to 00:15:39.180 --> 00:15:41.810 align:start position:0% to force every uh like safe owner to deploy<00:15:39.779> new<00:15:40.139> ones<00:15:40.380> will<00:15:40.860> will<00:15:41.220> basically<00:15:41.639> do 00:15:41.810 --> 00:15:41.820 align:start position:0% deploy new ones will will basically do 00:15:41.820 --> 00:15:44.090 align:start position:0% deploy new ones will will basically do like<00:15:42.060> a<00:15:42.360> force<00:15:42.779> update<00:15:43.079> for<00:15:43.320> them 00:15:44.090 --> 00:15:44.100 align:start position:0% like a force update for them 00:15:44.100 --> 00:15:46.370 align:start position:0% like a force update for them uh<00:15:45.060> then<00:15:45.300> you<00:15:45.480> can<00:15:45.600> see<00:15:45.720> the<00:15:45.899> operator's 00:15:46.370 --> 00:15:46.380 align:start position:0% uh then you can see the operator's 00:15:46.380 --> 00:15:48.050 align:start position:0% uh then you can see the operator's contacts<00:15:46.800> this<00:15:47.100> is<00:15:47.220> a<00:15:47.339> contract<00:15:47.639> responsible 00:15:48.050 --> 00:15:48.060 align:start position:0% contacts this is a contract responsible 00:15:48.060 --> 00:15:50.629 align:start position:0% contacts this is a contract responsible for<00:15:48.300> tracking<00:15:48.720> the<00:15:48.839> approved<00:15:49.260> addresses<00:15:49.740> uh 00:15:50.629 --> 00:15:50.639 align:start position:0% for tracking the approved addresses uh 00:15:50.639 --> 00:15:53.629 align:start position:0% for tracking the approved addresses uh per<00:15:50.880> safe<00:15:51.180> per<00:15:51.720> per<00:15:51.899> the<00:15:52.139> collection 00:15:53.629 --> 00:15:53.639 align:start position:0% per safe per per the collection 00:15:53.639 --> 00:15:59.269 align:start position:0% per safe per per the collection and<00:15:54.360> uh<00:15:54.899> our<00:15:55.139> Ponce<00:15:55.680> Factory<00:15:56.040> just<00:15:56.940> to<00:15:57.440> like<00:15:58.440> be 00:15:59.269 --> 00:15:59.279 align:start position:0% and uh our Ponce Factory just to like be 00:15:59.279 --> 00:16:01.189 align:start position:0% and uh our Ponce Factory just to like be sure<00:15:59.459> that<00:15:59.880> the<00:16:00.120> address<00:16:00.300> we<00:16:00.600> are<00:16:00.779> interacting 00:16:01.189 --> 00:16:01.199 align:start position:0% sure that the address we are interacting 00:16:01.199 --> 00:16:04.310 align:start position:0% sure that the address we are interacting with<00:16:01.380> is<00:16:02.160> actually<00:16:02.339> safe<00:16:02.760> and<00:16:03.660> then<00:16:03.839> there<00:16:04.139> is 00:16:04.310 --> 00:16:04.320 align:start position:0% with is actually safe and then there is 00:16:04.320 --> 00:16:07.250 align:start position:0% with is actually safe and then there is some<00:16:04.620> uh<00:16:05.160> some<00:16:05.639> like<00:16:05.760> agnosis<00:16:06.360> save<00:16:06.600> agnosis 00:16:07.250 --> 00:16:07.260 align:start position:0% some uh some like agnosis save agnosis 00:16:07.260 --> 00:16:09.530 align:start position:0% some uh some like agnosis save agnosis save<00:16:07.440> contract<00:16:07.800> and<00:16:08.579> uh<00:16:08.820> and<00:16:09.120> the<00:16:09.240> owner 00:16:09.530 --> 00:16:09.540 align:start position:0% save contract and uh and the owner 00:16:09.540 --> 00:16:13.970 align:start position:0% save contract and uh and the owner because<00:16:09.839> of<00:16:10.139> the<00:16:10.440> of<00:16:10.740> this<00:16:10.920> proxy 00:16:13.970 --> 00:16:13.980 align:start position:0% 00:16:13.980 --> 00:16:16.129 align:start position:0% still<00:16:14.639> we<00:16:15.060> didn't<00:16:15.240> solve<00:16:15.480> all<00:16:15.660> the<00:16:15.779> challenges 00:16:16.129 --> 00:16:16.139 align:start position:0% still we didn't solve all the challenges 00:16:16.139 --> 00:16:19.790 align:start position:0% still we didn't solve all the challenges so<00:16:16.500> open<00:16:16.740> challenges<00:16:17.399> are<00:16:17.880> enable<00:16:18.360> EIP<00:16:18.800> 1271. 00:16:19.790 --> 00:16:19.800 align:start position:0% so open challenges are enable EIP 1271. 00:16:19.800 --> 00:16:22.730 align:start position:0% so open challenges are enable EIP 1271. it<00:16:20.699> uh<00:16:20.940> will<00:16:21.300> be<00:16:21.480> possible<00:16:21.779> if<00:16:22.260> the<00:16:22.380> wallet 00:16:22.730 --> 00:16:22.740 align:start position:0% it uh will be possible if the wallet 00:16:22.740 --> 00:16:25.250 align:start position:0% it uh will be possible if the wallet basically<00:16:23.100> pre-approved<00:16:23.940> the<00:16:24.060> hash<00:16:24.240> in<00:16:25.139> that 00:16:25.250 --> 00:16:25.260 align:start position:0% basically pre-approved the hash in that 00:16:25.260 --> 00:16:27.110 align:start position:0% basically pre-approved the hash in that case<00:16:25.440> we<00:16:25.920> can<00:16:26.100> actually<00:16:26.339> check<00:16:26.699> what<00:16:26.940> is 00:16:27.110 --> 00:16:27.120 align:start position:0% case we can actually check what is 00:16:27.120 --> 00:16:29.990 align:start position:0% case we can actually check what is approved<00:16:27.540> and<00:16:28.260> if<00:16:28.620> if<00:16:28.980> it<00:16:29.220> doesn't<00:16:29.399> like<00:16:29.699> break 00:16:29.990 --> 00:16:30.000 align:start position:0% approved and if if it doesn't like break 00:16:30.000 --> 00:16:32.030 align:start position:0% approved and if if it doesn't like break any<00:16:30.300> transfer<00:16:30.779> rules<00:16:31.019> it'll<00:16:31.560> say<00:16:31.680> yeah<00:16:31.860> okay 00:16:32.030 --> 00:16:32.040 align:start position:0% any transfer rules it'll say yeah okay 00:16:32.040 --> 00:16:34.490 align:start position:0% any transfer rules it'll say yeah okay you<00:16:32.519> can<00:16:32.639> this<00:16:33.180> hash<00:16:33.360> is<00:16:33.540> approved<00:16:33.899> so<00:16:34.260> every 00:16:34.490 --> 00:16:34.500 align:start position:0% you can this hash is approved so every 00:16:34.500 --> 00:16:37.790 align:start position:0% you can this hash is approved so every call<00:16:34.800> for<00:16:35.279> the<00:16:35.519> uh<00:16:36.240> is<00:16:36.660> valid<00:16:37.019> signature<00:16:37.440> will 00:16:37.790 --> 00:16:37.800 align:start position:0% call for the uh is valid signature will 00:16:37.800 --> 00:16:40.850 align:start position:0% call for the uh is valid signature will return<00:16:38.040> to<00:16:38.579> or<00:16:38.820> the<00:16:39.000> magic<00:16:39.180> value<00:16:39.480> uh<00:16:40.380> for<00:16:40.620> for 00:16:40.850 --> 00:16:40.860 align:start position:0% return to or the magic value uh for for 00:16:40.860 --> 00:16:42.110 align:start position:0% return to or the magic value uh for for this<00:16:41.100> hash 00:16:42.110 --> 00:16:42.120 align:start position:0% this hash 00:16:42.120 --> 00:16:44.870 align:start position:0% this hash uh<00:16:42.959> guess<00:16:43.259> overhead<00:16:43.680> of<00:16:44.279> course<00:16:44.339> we<00:16:44.579> want<00:16:44.759> to 00:16:44.870 --> 00:16:44.880 align:start position:0% uh guess overhead of course we want to 00:16:44.880 --> 00:16:46.730 align:start position:0% uh guess overhead of course we want to have<00:16:45.120> a 00:16:46.730 --> 00:16:46.740 align:start position:0% have a 00:16:46.740 --> 00:16:49.189 align:start position:0% have a we<00:16:47.220> want<00:16:47.399> to<00:16:47.519> have<00:16:47.639> the<00:16:47.880> gas<00:16:48.000> cost<00:16:48.240> as<00:16:48.779> low<00:16:48.959> as 00:16:49.189 --> 00:16:49.199 align:start position:0% we want to have the gas cost as low as 00:16:49.199 --> 00:16:51.710 align:start position:0% we want to have the gas cost as low as possible<00:16:49.440> so<00:16:50.399> currently<00:16:50.820> minting<00:16:51.240> the<00:16:51.360> ATR 00:16:51.710 --> 00:16:51.720 align:start position:0% possible so currently minting the ATR 00:16:51.720 --> 00:16:53.810 align:start position:0% possible so currently minting the ATR token<00:16:52.079> has<00:16:52.259> a<00:16:52.380> constant<00:16:52.800> overhead<00:16:53.160> which<00:16:53.699> is 00:16:53.810 --> 00:16:53.820 align:start position:0% token has a constant overhead which is 00:16:53.820 --> 00:16:56.990 align:start position:0% token has a constant overhead which is night<00:16:54.060> which<00:16:54.720> is<00:16:54.839> nice<00:16:55.220> uh<00:16:56.220> and<00:16:56.459> transferring 00:16:56.990 --> 00:16:57.000 align:start position:0% night which is nice uh and transferring 00:16:57.000 --> 00:16:59.629 align:start position:0% night which is nice uh and transferring the<00:16:57.180> asset<00:16:57.420> via<00:16:57.779> the<00:16:57.899> ATR<00:16:58.199> token<00:16:58.680> has<00:16:58.980> linear 00:16:59.629 --> 00:16:59.639 align:start position:0% the asset via the ATR token has linear 00:16:59.639 --> 00:17:02.150 align:start position:0% the asset via the ATR token has linear overhead<00:17:00.060> because<00:17:00.779> it's<00:17:01.500> like<00:17:01.860> it's 00:17:02.150 --> 00:17:02.160 align:start position:0% overhead because it's like it's 00:17:02.160 --> 00:17:04.429 align:start position:0% overhead because it's like it's depending<00:17:02.639> on<00:17:02.880> number<00:17:03.060> of<00:17:03.300> tokenized<00:17:04.079> Assets 00:17:04.429 --> 00:17:04.439 align:start position:0% depending on number of tokenized Assets 00:17:04.439 --> 00:17:07.610 align:start position:0% depending on number of tokenized Assets in<00:17:04.919> the<00:17:05.040> in<00:17:05.339> the<00:17:05.520> safe<00:17:05.720> uh<00:17:06.720> because<00:17:06.900> we<00:17:07.260> need<00:17:07.439> to 00:17:07.610 --> 00:17:07.620 align:start position:0% in the in the safe uh because we need to 00:17:07.620 --> 00:17:10.130 align:start position:0% in the in the safe uh because we need to check<00:17:07.799> that<00:17:08.160> every<00:17:08.579> tokenized<00:17:09.240> asset<00:17:09.660> after 00:17:10.130 --> 00:17:10.140 align:start position:0% check that every tokenized asset after 00:17:10.140 --> 00:17:12.530 align:start position:0% check that every tokenized asset after the<00:17:10.380> execution<00:17:10.799> is<00:17:11.160> actually<00:17:11.400> there<00:17:11.699> and<00:17:12.299> that 00:17:12.530 --> 00:17:12.540 align:start position:0% the execution is actually there and that 00:17:12.540 --> 00:17:14.329 align:start position:0% the execution is actually there and that the<00:17:12.780> tokenized<00:17:13.500> balance<00:17:13.799> is<00:17:14.160> still 00:17:14.329 --> 00:17:14.339 align:start position:0% the tokenized balance is still 00:17:14.339 --> 00:17:16.069 align:start position:0% the tokenized balance is still sufficient 00:17:16.069 --> 00:17:16.079 align:start position:0% sufficient 00:17:16.079 --> 00:17:17.990 align:start position:0% sufficient uh<00:17:16.980> then<00:17:17.220> there<00:17:17.400> is<00:17:17.520> an<00:17:17.640> issue<00:17:17.880> with 00:17:17.990 --> 00:17:18.000 align:start position:0% uh then there is an issue with 00:17:18.000 --> 00:17:20.809 align:start position:0% uh then there is an issue with non-standard's<00:17:18.780> asset<00:17:19.140> I<00:17:19.799> think<00:17:19.980> this<00:17:20.520> this 00:17:20.809 --> 00:17:20.819 align:start position:0% non-standard's asset I think this this 00:17:20.819 --> 00:17:23.689 align:start position:0% non-standard's asset I think this this issue<00:17:21.120> will<00:17:21.299> be<00:17:21.419> there<00:17:21.600> like<00:17:21.839> forever<00:17:22.699> because 00:17:23.689 --> 00:17:23.699 align:start position:0% issue will be there like forever because 00:17:23.699 --> 00:17:26.510 align:start position:0% issue will be there like forever because uh<00:17:24.720> yeah<00:17:25.199> that's<00:17:25.380> like<00:17:25.679> we<00:17:25.980> can<00:17:26.160> work<00:17:26.339> only 00:17:26.510 --> 00:17:26.520 align:start position:0% uh yeah that's like we can work only 00:17:26.520 --> 00:17:28.270 align:start position:0% uh yeah that's like we can work only with<00:17:26.760> the<00:17:26.939> honest<00:17:27.179> assets 00:17:28.270 --> 00:17:28.280 align:start position:0% with the honest assets 00:17:28.280 --> 00:17:32.090 align:start position:0% with the honest assets uh<00:17:29.280> so<00:17:29.700> if<00:17:30.360> somebody<00:17:30.660> is<00:17:31.200> trying<00:17:31.440> to<00:17:31.620> give<00:17:31.919> you 00:17:32.090 --> 00:17:32.100 align:start position:0% uh so if somebody is trying to give you 00:17:32.100 --> 00:17:34.730 align:start position:0% uh so if somebody is trying to give you his<00:17:32.460> ATR<00:17:32.880> token<00:17:33.360> for<00:17:33.660> some<00:17:33.900> malicious<00:17:34.320> asset 00:17:34.730 --> 00:17:34.740 align:start position:0% his ATR token for some malicious asset 00:17:34.740 --> 00:17:36.650 align:start position:0% his ATR token for some malicious asset which<00:17:35.039> is<00:17:35.160> not<00:17:35.400> standard<00:17:35.820> they<00:17:36.240> find<00:17:36.480> some 00:17:36.650 --> 00:17:36.660 align:start position:0% which is not standard they find some 00:17:36.660 --> 00:17:38.270 align:start position:0% which is not standard they find some like<00:17:36.840> approved<00:17:37.320> functions<00:17:37.679> or<00:17:37.919> transfer 00:17:38.270 --> 00:17:38.280 align:start position:0% like approved functions or transfer 00:17:38.280 --> 00:17:39.950 align:start position:0% like approved functions or transfer functions<00:17:38.700> we<00:17:39.179> cannot<00:17:39.419> basically<00:17:39.720> like 00:17:39.950 --> 00:17:39.960 align:start position:0% functions we cannot basically like 00:17:39.960 --> 00:17:41.930 align:start position:0% functions we cannot basically like prevent<00:17:40.440> him<00:17:40.679> to<00:17:40.919> do<00:17:41.039> that<00:17:41.220> and<00:17:41.580> if<00:17:41.700> you<00:17:41.820> accept 00:17:41.930 --> 00:17:41.940 align:start position:0% prevent him to do that and if you accept 00:17:41.940 --> 00:17:44.750 align:start position:0% prevent him to do that and if you accept this<00:17:42.240> ATR<00:17:42.600> token<00:17:43.020> then<00:17:43.200> yeah<00:17:44.100> you're<00:17:44.340> screwed 00:17:44.750 --> 00:17:44.760 align:start position:0% this ATR token then yeah you're screwed 00:17:44.760 --> 00:17:46.250 align:start position:0% this ATR token then yeah you're screwed sorry 00:17:46.250 --> 00:17:46.260 align:start position:0% sorry 00:17:46.260 --> 00:17:48.890 align:start position:0% sorry and<00:17:47.100> the<00:17:47.640> possibility<00:17:48.000> of<00:17:48.179> using<00:17:48.480> delegate 00:17:48.890 --> 00:17:48.900 align:start position:0% and the possibility of using delegate 00:17:48.900 --> 00:17:51.710 align:start position:0% and the possibility of using delegate goals<00:17:49.320> uh<00:17:50.039> there<00:17:50.340> is<00:17:50.460> actually<00:17:50.640> an<00:17:50.880> option<00:17:51.240> to 00:17:51.710 --> 00:17:51.720 align:start position:0% goals uh there is actually an option to 00:17:51.720 --> 00:17:55.130 align:start position:0% goals uh there is actually an option to like<00:17:52.200> whitelist<00:17:53.160> some<00:17:53.520> addresses<00:17:54.059> uh<00:17:54.840> to<00:17:55.020> be 00:17:55.130 --> 00:17:55.140 align:start position:0% like whitelist some addresses uh to be 00:17:55.140 --> 00:17:56.990 align:start position:0% like whitelist some addresses uh to be able<00:17:55.320> to<00:17:55.440> use<00:17:55.620> the<00:17:55.799> delegate<00:17:56.160> call<00:17:56.340> or<00:17:56.640> to<00:17:56.820> call 00:17:56.990 --> 00:17:57.000 align:start position:0% able to use the delegate call or to call 00:17:57.000 --> 00:18:00.470 align:start position:0% able to use the delegate call or to call the<00:17:57.179> delegate<00:17:57.539> call<00:17:57.780> at<00:17:58.020> uh<00:17:59.400> but<00:17:59.940> we<00:18:00.120> cannot<00:18:00.360> do 00:18:00.470 --> 00:18:00.480 align:start position:0% the delegate call at uh but we cannot do 00:18:00.480 --> 00:18:03.049 align:start position:0% the delegate call at uh but we cannot do it<00:18:00.600> like<00:18:00.780> generally<00:18:01.500> we<00:18:01.860> cannot<00:18:02.100> say<00:18:02.280> hey<00:18:02.520> you 00:18:03.049 --> 00:18:03.059 align:start position:0% it like generally we cannot say hey you 00:18:03.059 --> 00:18:05.330 align:start position:0% it like generally we cannot say hey you can<00:18:03.179> you<00:18:03.419> can<00:18:03.600> call<00:18:03.720> delegate<00:18:04.200> colon<00:18:04.559> any<00:18:04.799> any 00:18:05.330 --> 00:18:05.340 align:start position:0% can you can call delegate colon any any 00:18:05.340 --> 00:18:07.610 align:start position:0% can you can call delegate colon any any address<00:18:05.640> because<00:18:06.360> then<00:18:06.660> it's<00:18:06.900> a<00:18:07.020> it's<00:18:07.260> a<00:18:07.440> huge 00:18:07.610 --> 00:18:07.620 align:start position:0% address because then it's a it's a huge 00:18:07.620 --> 00:18:10.669 align:start position:0% address because then it's a it's a huge security<00:18:07.740> issue<00:18:08.280> for<00:18:08.400> us 00:18:10.669 --> 00:18:10.679 align:start position:0% 00:18:10.679 --> 00:18:13.730 align:start position:0% yeah<00:18:11.220> and<00:18:11.400> I<00:18:11.640> think<00:18:11.760> that's<00:18:11.940> all<00:18:12.179> so<00:18:12.840> thank<00:18:13.559> you 00:18:13.730 --> 00:18:13.740 align:start position:0% yeah and I think that's all so thank you 00:18:13.740 --> 00:18:19.730 align:start position:0% yeah and I think that's all so thank you there<00:18:14.640> was<00:18:14.820> me<00:18:15.600> and<00:18:15.780> Joseph 00:18:19.730 --> 00:18:19.740 align:start position:0% 00:18:19.740 --> 00:18:22.250 align:start position:0% thank<00:18:20.340> you<00:18:20.460> so<00:18:20.640> much<00:18:20.760> naiman<00:18:21.539> Joseph<00:18:21.720> and 00:18:22.250 --> 00:18:22.260 align:start position:0% thank you so much naiman Joseph and 00:18:22.260 --> 00:18:23.990 align:start position:0% thank you so much naiman Joseph and thank<00:18:22.440> you<00:18:22.500> for<00:18:22.620> I<00:18:23.220> also<00:18:23.460> think<00:18:23.580> we<00:18:23.760> have<00:18:23.880> two 00:18:23.990 --> 00:18:24.000 align:start position:0% thank you for I also think we have two 00:18:24.000 --> 00:18:25.789 align:start position:0% thank you for I also think we have two more<00:18:24.240> thanks<00:18:24.600> to<00:18:24.840> shildo<00:18:25.380> there<00:18:25.559> are<00:18:25.679> two 00:18:25.789 --> 00:18:25.799 align:start position:0% more thanks to shildo there are two 00:18:25.799 --> 00:18:27.470 align:start position:0% more thanks to shildo there are two slides<00:18:26.160> where<00:18:26.400> yeah<00:18:26.700> two<00:18:26.940> more<00:18:27.059> slides<00:18:27.360> I'm 00:18:27.470 --> 00:18:27.480 align:start position:0% slides where yeah two more slides I'm 00:18:27.480 --> 00:18:38.210 align:start position:0% slides where yeah two more slides I'm sorry<00:18:27.660> yeah 00:18:38.210 --> 00:18:38.220 align:start position:0% 00:18:38.220 --> 00:18:39.770 align:start position:0% or<00:18:38.640> maybe<00:18:38.760> it's<00:18:38.940> stupid<00:18:39.059> to<00:18:39.299> put<00:18:39.480> two<00:18:39.660> more 00:18:39.770 --> 00:18:39.780 align:start position:0% or maybe it's stupid to put two more 00:18:39.780 --> 00:18:41.390 align:start position:0% or maybe it's stupid to put two more slides<00:18:40.080> after<00:18:40.200> a<00:18:40.440> thank<00:18:40.559> you<00:18:40.679> page<00:18:40.919> but<00:18:41.160> you 00:18:41.390 --> 00:18:41.400 align:start position:0% slides after a thank you page but you 00:18:41.400 --> 00:18:43.010 align:start position:0% slides after a thank you page but you know 00:18:43.010 --> 00:18:43.020 align:start position:0% know 00:18:43.020 --> 00:18:46.909 align:start position:0% know stuff<00:18:43.380> happens 00:18:46.909 --> 00:18:46.919 align:start position:0% 00:18:46.919 --> 00:18:49.610 align:start position:0% uh<00:18:47.580> if<00:18:47.700> you<00:18:47.880> can<00:18:48.000> go<00:18:48.179> to<00:18:48.299> thank<00:18:48.840> you<00:18:49.020> one<00:18:49.140> as 00:18:49.610 --> 00:18:49.620 align:start position:0% uh if you can go to thank you one as 00:18:49.620 --> 00:18:51.110 align:start position:0% uh if you can go to thank you one as actually 00:18:51.110 --> 00:18:51.120 align:start position:0% actually 00:18:51.120 --> 00:18:54.230 align:start position:0% actually oh 00:18:54.230 --> 00:18:54.240 align:start position:0% 00:18:54.240 --> 00:19:00.049 align:start position:0% yeah<00:18:54.780> number<00:18:55.260> 18. 00:19:00.049 --> 00:19:00.059 align:start position:0% 00:19:00.059 --> 00:19:02.930 align:start position:0% yeah 00:19:02.930 --> 00:19:02.940 align:start position:0% 00:19:02.940 --> 00:19:05.990 align:start position:0% cool<00:19:03.480> so<00:19:04.020> I<00:19:04.320> I<00:19:04.559> realized<00:19:04.980> like<00:19:05.220> maybe<00:19:05.460> some<00:19:05.880> of 00:19:05.990 --> 00:19:06.000 align:start position:0% cool so I I realized like maybe some of 00:19:06.000 --> 00:19:07.669 align:start position:0% cool so I I realized like maybe some of the<00:19:06.179> some<00:19:06.480> of<00:19:06.600> the<00:19:06.720> graphics<00:19:07.020> weren't<00:19:07.380> really 00:19:07.669 --> 00:19:07.679 align:start position:0% the some of the graphics weren't really 00:19:07.679 --> 00:19:10.549 align:start position:0% the some of the graphics weren't really visible<00:19:08.100> here<00:19:08.340> so<00:19:08.700> if<00:19:08.880> you<00:19:09.000> go<00:19:09.179> to<00:19:09.360> uh<00:19:10.080> Pawn<00:19:10.260> dot 00:19:10.549 --> 00:19:10.559 align:start position:0% visible here so if you go to uh Pawn dot 00:19:10.559 --> 00:19:12.830 align:start position:0% visible here so if you go to uh Pawn dot mirror.xyz<00:19:11.280> there<00:19:11.580> is<00:19:11.700> an<00:19:11.820> article<00:19:12.120> about<00:19:12.419> the 00:19:12.830 --> 00:19:12.840 align:start position:0% mirror.xyz there is an article about the 00:19:12.840 --> 00:19:14.810 align:start position:0% mirror.xyz there is an article about the the<00:19:12.960> pawn<00:19:13.200> safe<00:19:13.440> where<00:19:13.860> everything<00:19:14.400> should<00:19:14.640> be 00:19:14.810 --> 00:19:14.820 align:start position:0% the pawn safe where everything should be 00:19:14.820 --> 00:19:16.970 align:start position:0% the pawn safe where everything should be described<00:19:15.240> uh<00:19:15.960> also<00:19:16.200> you<00:19:16.320> can<00:19:16.500> just<00:19:16.620> check<00:19:16.799> out 00:19:16.970 --> 00:19:16.980 align:start position:0% described uh also you can just check out 00:19:16.980 --> 00:19:20.210 align:start position:0% described uh also you can just check out our<00:19:17.160> website<00:19:17.520> on<00:19:17.640> pawn.xyz<00:19:18.480> uh<00:19:19.380> where<00:19:19.620> you<00:19:20.100> can 00:19:20.210 --> 00:19:20.220 align:start position:0% our website on pawn.xyz uh where you can 00:19:20.220 --> 00:19:22.610 align:start position:0% our website on pawn.xyz uh where you can see<00:19:21.000> our<00:19:21.179> outage<00:19:21.600> see<00:19:21.720> our<00:19:21.900> repos<00:19:22.260> we<00:19:22.500> have<00:19:22.559> a 00:19:22.610 --> 00:19:22.620 align:start position:0% see our outage see our repos we have a 00:19:22.620 --> 00:19:25.490 align:start position:0% see our outage see our repos we have a bunch<00:19:22.740> of<00:19:22.860> documentation<00:19:23.460> uh<00:19:24.299> for<00:19:24.600> users<00:19:25.200> or 00:19:25.490 --> 00:19:25.500 align:start position:0% bunch of documentation uh for users or 00:19:25.500 --> 00:19:28.850 align:start position:0% bunch of documentation uh for users or or<00:19:25.740> developers<00:19:26.280> as<00:19:26.460> well<00:19:26.660> and<00:19:27.660> finally 00:19:28.850 --> 00:19:28.860 align:start position:0% or developers as well and finally 00:19:28.860 --> 00:19:33.350 align:start position:0% or developers as well and finally well<00:19:29.280> here's<00:19:29.580> our<00:19:29.700> pull-up 00:19:33.350 --> 00:19:33.360 align:start position:0% 00:19:33.360 --> 00:19:35.090 align:start position:0% yeah<00:19:33.780> thanks<00:19:33.960> for<00:19:34.140> coming<00:19:34.260> and<00:19:34.679> I<00:19:34.799> think<00:19:34.919> we 00:19:35.090 --> 00:19:35.100 align:start position:0% yeah thanks for coming and I think we 00:19:35.100 --> 00:19:36.590 align:start position:0% yeah thanks for coming and I think we have<00:19:35.220> six<00:19:35.400> more<00:19:35.580> minutes<00:19:35.760> for<00:19:36.059> questions<00:19:36.240> is 00:19:36.590 --> 00:19:36.600 align:start position:0% have six more minutes for questions is 00:19:36.600 --> 00:19:39.650 align:start position:0% have six more minutes for questions is it<00:19:36.780> right<00:19:36.900> yeah<00:19:37.500> so<00:19:38.220> if<00:19:38.580> any<00:19:38.880> of<00:19:39.059> you<00:19:39.299> have<00:19:39.539> a 00:19:39.650 --> 00:19:39.660 align:start position:0% it right yeah so if any of you have a 00:19:39.660 --> 00:19:44.230 align:start position:0% it right yeah so if any of you have a question 00:19:44.230 --> 00:19:44.240 align:start position:0% 00:19:44.240 --> 00:19:46.070 align:start position:0% anyone 00:19:46.070 --> 00:19:46.080 align:start position:0% anyone 00:19:46.080 --> 00:19:54.950 align:start position:0% anyone there<00:19:46.440> we<00:19:46.620> go 00:19:54.950 --> 00:19:54.960 align:start position:0% 00:19:54.960 --> 00:19:58.070 align:start position:0% yeah<00:19:55.380> thank<00:19:55.799> you<00:19:55.919> uh<00:19:56.700> good<00:19:56.880> afternoon<00:19:57.059> uh<00:19:57.780> how 00:19:58.070 --> 00:19:58.080 align:start position:0% yeah thank you uh good afternoon uh how 00:19:58.080 --> 00:20:00.830 align:start position:0% yeah thank you uh good afternoon uh how are<00:19:58.200> you<00:19:58.380> going<00:19:58.679> to<00:19:58.919> handle<00:19:59.340> the<00:19:59.940> I<00:20:00.720> don't 00:20:00.830 --> 00:20:00.840 align:start position:0% are you going to handle the I don't 00:20:00.840 --> 00:20:03.529 align:start position:0% are you going to handle the I don't remember<00:20:00.960> where<00:20:01.440> the<00:20:01.860> E<00:20:02.100> the<00:20:02.460> e<00:20:02.700> i<00:20:02.820> the<00:20:03.179> correct 00:20:03.529 --> 00:20:03.539 align:start position:0% remember where the E the e i the correct 00:20:03.539 --> 00:20:05.930 align:start position:0% remember where the E the e i the correct AIP<00:20:03.960> but<00:20:04.260> there<00:20:04.440> was<00:20:04.620> one<00:20:04.919> that<00:20:05.100> what<00:20:05.340> will 00:20:05.930 --> 00:20:05.940 align:start position:0% AIP but there was one that what will 00:20:05.940 --> 00:20:08.630 align:start position:0% AIP but there was one that what will allow<00:20:06.120> you<00:20:06.240> to<00:20:06.419> approve<00:20:06.960> and<00:20:07.559> transmit<00:20:08.280> at<00:20:08.460> the 00:20:08.630 --> 00:20:08.640 align:start position:0% allow you to approve and transmit at the 00:20:08.640 --> 00:20:10.909 align:start position:0% allow you to approve and transmit at the same<00:20:08.700> in<00:20:09.240> the<00:20:09.299> same<00:20:09.419> transaction 00:20:10.909 --> 00:20:10.919 align:start position:0% same in the same transaction 00:20:10.919 --> 00:20:12.830 align:start position:0% same in the same transaction have<00:20:11.400> you<00:20:11.520> any<00:20:11.700> plans<00:20:11.940> for<00:20:12.059> that<00:20:12.240> I<00:20:12.539> think<00:20:12.720> it 00:20:12.830 --> 00:20:12.840 align:start position:0% have you any plans for that I think it 00:20:12.840 --> 00:20:16.490 align:start position:0% have you any plans for that I think it was<00:20:13.020> 12.71<00:20:14.220> or<00:20:15.000> something<00:20:15.299> similar 00:20:16.490 --> 00:20:16.500 align:start position:0% was 12.71 or something similar 00:20:16.500 --> 00:20:18.470 align:start position:0% was 12.71 or something similar come<00:20:16.980> again<00:20:17.340> if<00:20:17.820> we<00:20:17.940> want<00:20:18.179> to<00:20:18.299> support 00:20:18.470 --> 00:20:18.480 align:start position:0% come again if we want to support 00:20:18.480 --> 00:20:21.289 align:start position:0% come again if we want to support standard<00:20:19.140> that<00:20:19.740> can<00:20:20.100> approve<00:20:20.640> and<00:20:20.820> call<00:20:21.000> in 00:20:21.289 --> 00:20:21.299 align:start position:0% standard that can approve and call in 00:20:21.299 --> 00:20:22.789 align:start position:0% standard that can approve and call in the<00:20:21.419> same<00:20:21.539> transaction 00:20:22.789 --> 00:20:22.799 align:start position:0% the same transaction 00:20:22.799 --> 00:20:25.370 align:start position:0% the same transaction yes<00:20:23.400> there<00:20:24.000> I<00:20:24.240> believe<00:20:24.480> there<00:20:24.780> was<00:20:24.900> one<00:20:25.140> of<00:20:25.260> the 00:20:25.370 --> 00:20:25.380 align:start position:0% yes there I believe there was one of the 00:20:25.380 --> 00:20:29.750 align:start position:0% yes there I believe there was one of the eip's<00:20:26.039> that<00:20:26.280> uh<00:20:26.580> that<00:20:27.260> allowed<00:20:28.260> you<00:20:28.380> to<00:20:28.559> sign<00:20:28.919> a 00:20:29.750 --> 00:20:29.760 align:start position:0% eip's that uh that allowed you to sign a 00:20:29.760 --> 00:20:32.810 align:start position:0% eip's that uh that allowed you to sign a transaction<00:20:30.179> at<00:20:30.660> several<00:20:31.220> same<00:20:32.220> several 00:20:32.810 --> 00:20:32.820 align:start position:0% transaction at several same several 00:20:32.820 --> 00:20:36.650 align:start position:0% transaction at several same several transactions<00:20:33.360> in<00:20:33.539> the<00:20:33.720> same<00:20:34.460> uh<00:20:35.460> in<00:20:36.059> at<00:20:36.480> the 00:20:36.650 --> 00:20:36.660 align:start position:0% transactions in the same uh in at the 00:20:36.660 --> 00:20:39.049 align:start position:0% transactions in the same uh in at the same<00:20:36.780> time 00:20:39.049 --> 00:20:39.059 align:start position:0% 00:20:39.059 --> 00:20:41.510 align:start position:0% if<00:20:39.539> I<00:20:39.720> understood<00:20:40.080> it<00:20:40.320> correctly<00:20:40.740> there<00:20:41.340> is 00:20:41.510 --> 00:20:41.520 align:start position:0% if I understood it correctly there is 00:20:41.520 --> 00:20:44.350 align:start position:0% if I understood it correctly there is one<00:20:41.700> EIP<00:20:42.059> I<00:20:42.539> think<00:20:42.660> it's 00:20:44.350 --> 00:20:44.360 align:start position:0% one EIP I think it's 00:20:44.360 --> 00:20:46.669 align:start position:0% one EIP I think it's 1373<00:20:45.360> something<00:20:45.600> like<00:20:45.840> that<00:20:45.960> it's<00:20:46.200> a<00:20:46.380> token 00:20:46.669 --> 00:20:46.679 align:start position:0% 1373 something like that it's a token 00:20:46.679 --> 00:20:49.310 align:start position:0% 1373 something like that it's a token standard<00:20:47.039> which<00:20:47.820> implements<00:20:48.480> another<00:20:48.840> set<00:20:49.140> of 00:20:49.310 --> 00:20:49.320 align:start position:0% standard which implements another set of 00:20:49.320 --> 00:20:51.710 align:start position:0% standard which implements another set of approved<00:20:49.799> functions<00:20:50.299> these<00:20:51.299> approved 00:20:51.710 --> 00:20:51.720 align:start position:0% approved functions these approved 00:20:51.720 --> 00:20:54.289 align:start position:0% approved functions these approved functions<00:20:52.140> can<00:20:52.500> basically<00:20:52.919> approve<00:20:53.880> and<00:20:54.059> call 00:20:54.289 --> 00:20:54.299 align:start position:0% functions can basically approve and call 00:20:54.299 --> 00:20:57.890 align:start position:0% functions can basically approve and call arbitrary<00:20:54.960> data<00:20:55.380> in<00:20:55.740> one<00:20:55.919> transaction<00:20:56.600> uh<00:20:57.600> we 00:20:57.890 --> 00:20:57.900 align:start position:0% arbitrary data in one transaction uh we 00:20:57.900 --> 00:21:00.650 align:start position:0% arbitrary data in one transaction uh we are<00:20:58.080> actually<00:20:58.320> supporting<00:20:59.100> that<00:20:59.340> so<00:21:00.000> beside 00:21:00.650 --> 00:21:00.660 align:start position:0% are actually supporting that so beside 00:21:00.660 --> 00:21:05.450 align:start position:0% are actually supporting that so beside these<00:21:01.260> well-known<00:21:02.039> 27<00:21:02.760> 721<00:21:03.600> 1155<00:21:04.440> we<00:21:05.100> are<00:21:05.280> also 00:21:05.450 --> 00:21:05.460 align:start position:0% these well-known 27 721 1155 we are also 00:21:05.460 --> 00:21:09.289 align:start position:0% these well-known 27 721 1155 we are also supporting<00:21:05.880> 777<00:21:06.600> and<00:21:07.080> these<00:21:07.880> 1363<00:21:08.880> I'm<00:21:09.120> not 00:21:09.289 --> 00:21:09.299 align:start position:0% supporting 777 and these 1363 I'm not 00:21:09.299 --> 00:21:11.810 align:start position:0% supporting 777 and these 1363 I'm not sure<00:21:09.480> about<00:21:09.660> the<00:21:09.900> number<00:21:10.080> now<00:21:10.380> so<00:21:10.919> I<00:21:11.280> hope<00:21:11.580> I 00:21:11.810 --> 00:21:11.820 align:start position:0% sure about the number now so I hope I 00:21:11.820 --> 00:21:13.490 align:start position:0% sure about the number now so I hope I answered<00:21:12.179> your<00:21:12.299> question<00:21:12.720> or<00:21:13.080> it<00:21:13.320> was 00:21:13.490 --> 00:21:13.500 align:start position:0% answered your question or it was 00:21:13.500 --> 00:21:15.770 align:start position:0% answered your question or it was something<00:21:13.860> else 00:21:15.770 --> 00:21:15.780 align:start position:0% something else 00:21:15.780 --> 00:21:30.850 align:start position:0% something else anyone<00:21:16.559> else 00:21:30.850 --> 00:21:30.860 align:start position:0% 00:21:30.860 --> 00:21:32.690 align:start position:0% thank<00:21:31.860> you 00:21:32.690 --> 00:21:32.700 align:start position:0% thank you 00:21:32.700 --> 00:21:33.490 align:start position:0% thank you um 00:21:33.490 --> 00:21:33.500 align:start position:0% um 00:21:33.500 --> 00:21:36.970 align:start position:0% um lending<00:21:34.500> out<00:21:34.559> nfts<00:21:35.220> is<00:21:35.400> always<00:21:35.640> a<00:21:36.059> bit<00:21:36.179> tricky 00:21:36.970 --> 00:21:36.980 align:start position:0% lending out nfts is always a bit tricky 00:21:36.980 --> 00:21:40.070 align:start position:0% lending out nfts is always a bit tricky and<00:21:37.980> you<00:21:38.880> mentioned<00:21:39.179> you<00:21:39.539> can<00:21:39.600> lend<00:21:39.840> it<00:21:39.960> out 00:21:40.070 --> 00:21:40.080 align:start position:0% and you mentioned you can lend it out 00:21:40.080 --> 00:21:43.390 align:start position:0% and you mentioned you can lend it out without<00:21:40.320> using<00:21:41.159> collateral<00:21:41.700> uh<00:21:42.659> how<00:21:42.900> is<00:21:43.080> that 00:21:43.390 --> 00:21:43.400 align:start position:0% without using collateral uh how is that 00:21:43.400 --> 00:21:46.250 align:start position:0% without using collateral uh how is that realized<00:21:44.400> and<00:21:44.700> is<00:21:45.000> that<00:21:45.120> compatible<00:21:45.600> with<00:21:45.900> any 00:21:46.250 --> 00:21:46.260 align:start position:0% realized and is that compatible with any 00:21:46.260 --> 00:21:48.649 align:start position:0% realized and is that compatible with any existing<00:21:46.860> uh<00:21:47.520> wallets<00:21:47.940> that<00:21:48.120> would<00:21:48.360> display 00:21:48.649 --> 00:21:48.659 align:start position:0% existing uh wallets that would display 00:21:48.659 --> 00:21:50.330 align:start position:0% existing uh wallets that would display nfts 00:21:50.330 --> 00:21:50.340 align:start position:0% nfts 00:21:50.340 --> 00:21:52.850 align:start position:0% nfts uh<00:21:51.059> well<00:21:51.360> the<00:21:51.600> idea<00:21:51.960> about<00:21:52.200> not<00:21:52.559> using 00:21:52.850 --> 00:21:52.860 align:start position:0% uh well the idea about not using 00:21:52.860 --> 00:21:54.529 align:start position:0% uh well the idea about not using collateral<00:21:53.340> is<00:21:53.700> that<00:21:53.940> you<00:21:54.240> will<00:21:54.360> use 00:21:54.529 --> 00:21:54.539 align:start position:0% collateral is that you will use 00:21:54.539 --> 00:21:57.110 align:start position:0% collateral is that you will use collateral<00:21:55.080> but<00:21:55.380> the<00:21:55.559> ATR<00:21:55.919> token<00:21:56.400> so 00:21:57.110 --> 00:21:57.120 align:start position:0% collateral but the ATR token so 00:21:57.120 --> 00:22:00.049 align:start position:0% collateral but the ATR token so basically<00:21:57.659> if<00:21:58.380> I<00:21:58.620> want<00:21:58.740> to<00:21:58.919> lend<00:21:59.280> you<00:21:59.460> some 00:22:00.049 --> 00:22:00.059 align:start position:0% basically if I want to lend you some 00:22:00.059 --> 00:22:03.169 align:start position:0% basically if I want to lend you some assets<00:22:00.419> some<00:22:00.780> whatever<00:22:01.500> asset<00:22:02.100> I<00:22:02.760> will<00:22:02.940> first 00:22:03.169 --> 00:22:03.179 align:start position:0% assets some whatever asset I will first 00:22:03.179 --> 00:22:06.049 align:start position:0% assets some whatever asset I will first tokenize<00:22:03.780> its<00:22:04.320> transfer<00:22:04.620> rights<00:22:04.980> I<00:22:05.640> will<00:22:05.820> send 00:22:06.049 --> 00:22:06.059 align:start position:0% tokenize its transfer rights I will send 00:22:06.059 --> 00:22:07.850 align:start position:0% tokenize its transfer rights I will send you<00:22:06.240> that<00:22:06.480> asset<00:22:06.900> and<00:22:07.140> I'll<00:22:07.320> keep<00:22:07.559> the 00:22:07.850 --> 00:22:07.860 align:start position:0% you that asset and I'll keep the 00:22:07.860 --> 00:22:10.130 align:start position:0% you that asset and I'll keep the transfer<00:22:08.159> Edge<00:22:08.400> to<00:22:08.580> myself<00:22:08.760> so<00:22:09.659> you<00:22:09.960> are 00:22:10.130 --> 00:22:10.140 align:start position:0% transfer Edge to myself so you are 00:22:10.140 --> 00:22:12.289 align:start position:0% transfer Edge to myself so you are stated<00:22:10.440> as<00:22:10.679> an<00:22:10.799> owner<00:22:11.100> of<00:22:11.220> that<00:22:11.400> asset<00:22:11.820> in<00:22:12.120> the 00:22:12.289 --> 00:22:12.299 align:start position:0% stated as an owner of that asset in the 00:22:12.299 --> 00:22:14.750 align:start position:0% stated as an owner of that asset in the whole<00:22:12.419> D5<00:22:12.840> ecosystem<00:22:13.380> but<00:22:14.039> if<00:22:14.280> you<00:22:14.460> stop 00:22:14.750 --> 00:22:14.760 align:start position:0% whole D5 ecosystem but if you stop 00:22:14.760 --> 00:22:16.730 align:start position:0% whole D5 ecosystem but if you stop paying<00:22:15.240> me<00:22:15.419> my<00:22:15.960> installments<00:22:16.500> or<00:22:16.620> whatever 00:22:16.730 --> 00:22:16.740 align:start position:0% paying me my installments or whatever 00:22:16.740 --> 00:22:19.669 align:start position:0% paying me my installments or whatever I'm<00:22:17.520> still<00:22:17.940> able<00:22:18.299> to<00:22:18.419> transfer<00:22:19.080> it<00:22:19.200> back<00:22:19.440> from 00:22:19.669 --> 00:22:19.679 align:start position:0% I'm still able to transfer it back from 00:22:19.679 --> 00:22:22.430 align:start position:0% I'm still able to transfer it back from you<00:22:19.860> even<00:22:20.159> though<00:22:20.520> normally<00:22:21.240> I'm<00:22:21.539> not<00:22:21.840> I<00:22:22.320> don't 00:22:22.430 --> 00:22:22.440 align:start position:0% you even though normally I'm not I don't 00:22:22.440 --> 00:22:25.130 align:start position:0% you even though normally I'm not I don't have<00:22:22.679> the<00:22:22.860> rights<00:22:23.220> to<00:22:23.340> do<00:22:23.460> that<00:22:23.640> so<00:22:24.360> it's<00:22:24.900> not 00:22:25.130 --> 00:22:25.140 align:start position:0% have the rights to do that so it's not 00:22:25.140 --> 00:22:27.950 align:start position:0% have the rights to do that so it's not like<00:22:25.760> uncollateralized<00:22:26.760> in<00:22:27.360> like<00:22:27.539> very 00:22:27.950 --> 00:22:27.960 align:start position:0% like uncollateralized in like very 00:22:27.960 --> 00:22:30.110 align:start position:0% like uncollateralized in like very technical<00:22:28.380> sense<00:22:28.620> but<00:22:29.340> you<00:22:29.520> are<00:22:29.700> not<00:22:29.820> using 00:22:30.110 --> 00:22:30.120 align:start position:0% technical sense but you are not using 00:22:30.120 --> 00:22:31.909 align:start position:0% technical sense but you are not using the<00:22:30.299> asset<00:22:30.600> itself<00:22:30.900> as<00:22:31.080> a<00:22:31.200> collateral<00:22:31.559> you<00:22:31.740> are 00:22:31.909 --> 00:22:31.919 align:start position:0% the asset itself as a collateral you are 00:22:31.919 --> 00:22:34.549 align:start position:0% the asset itself as a collateral you are using<00:22:32.100> the<00:22:32.220> transference<00:22:32.760> instead 00:22:34.549 --> 00:22:34.559 align:start position:0% using the transference instead 00:22:34.559 --> 00:22:39.250 align:start position:0% using the transference instead foreign 00:22:39.250 --> 00:22:39.260 align:start position:0% 00:22:39.260 --> 00:22:41.090 align:start position:0% else 00:22:41.090 --> 00:22:41.100 align:start position:0% else 00:22:41.100 --> 00:22:47.450 align:start position:0% else yep 00:22:47.450 --> 00:22:47.460 align:start position:0% 00:22:47.460 --> 00:22:49.370 align:start position:0% hey<00:22:48.000> guys<00:22:48.240> thank<00:22:48.480> you<00:22:48.600> so<00:22:49.080> would<00:22:49.260> you 00:22:49.370 --> 00:22:49.380 align:start position:0% hey guys thank you so would you 00:22:49.380 --> 00:22:50.930 align:start position:0% hey guys thank you so would you elaborate<00:22:49.799> a<00:22:49.919> little<00:22:50.039> bit<00:22:50.159> about<00:22:50.340> the<00:22:50.700> account 00:22:50.930 --> 00:22:50.940 align:start position:0% elaborate a little bit about the account 00:22:50.940 --> 00:22:53.450 align:start position:0% elaborate a little bit about the account rental<00:22:51.299> you<00:22:51.960> were<00:22:52.080> talking<00:22:52.260> about<00:22:52.559> the<00:22:52.980> the 00:22:53.450 --> 00:22:53.460 align:start position:0% rental you were talking about the the 00:22:53.460 --> 00:22:56.830 align:start position:0% rental you were talking about the the like<00:22:54.059> account<00:22:54.360> rental<00:22:54.659> or<00:22:55.080> so<00:22:55.280> and<00:22:56.280> the 00:22:56.830 --> 00:22:56.840 align:start position:0% like account rental or so and the 00:22:56.840 --> 00:22:59.090 align:start position:0% like account rental or so and the bribery<00:22:57.840> attack 00:22:59.090 --> 00:22:59.100 align:start position:0% bribery attack 00:22:59.100 --> 00:23:01.490 align:start position:0% bribery attack for<00:22:59.520> the<00:22:59.640> account<00:22:59.820> Trend<00:23:00.240> also<00:23:00.600> if<00:23:00.900> I<00:23:01.080> have<00:23:01.200> if 00:23:01.490 --> 00:23:01.500 align:start position:0% for the account Trend also if I have if 00:23:01.500 --> 00:23:04.669 align:start position:0% for the account Trend also if I have if I<00:23:01.679> understand<00:23:01.799> call<00:23:02.280> it<00:23:02.659> correctly<00:23:03.659> then<00:23:04.380> will 00:23:04.669 --> 00:23:04.679 align:start position:0% I understand call it correctly then will 00:23:04.679 --> 00:23:07.070 align:start position:0% I understand call it correctly then will will<00:23:04.980> be<00:23:05.220> allowed<00:23:05.580> to<00:23:05.880> rent<00:23:06.000> our<00:23:06.360> account<00:23:06.659> on 00:23:07.070 --> 00:23:07.080 align:start position:0% will be allowed to rent our account on 00:23:07.080 --> 00:23:11.210 align:start position:0% will be allowed to rent our account on their<00:23:07.260> usage<00:23:07.620> of<00:23:07.740> it<00:23:07.919> so<00:23:08.780> how<00:23:09.780> yeah<00:23:10.260> it<00:23:11.039> was 00:23:11.210 --> 00:23:11.220 align:start position:0% their usage of it so how yeah it was 00:23:11.220 --> 00:23:13.190 align:start position:0% their usage of it so how yeah it was about<00:23:11.340> specifically<00:23:12.000> the<00:23:12.240> assets<00:23:12.659> but<00:23:12.840> now<00:23:13.020> if 00:23:13.190 --> 00:23:13.200 align:start position:0% about specifically the assets but now if 00:23:13.200 --> 00:23:15.049 align:start position:0% about specifically the assets but now if you<00:23:13.320> want<00:23:13.440> to<00:23:13.500> take<00:23:13.679> that<00:23:13.860> one<00:23:14.039> as<00:23:14.280> a<00:23:14.460> printing 00:23:15.049 --> 00:23:15.059 align:start position:0% you want to take that one as a printing 00:23:15.059 --> 00:23:17.570 align:start position:0% you want to take that one as a printing case<00:23:15.179> all<00:23:15.419> right<00:23:15.539> well<00:23:15.720> so<00:23:16.340> essentially<00:23:17.340> what 00:23:17.570 --> 00:23:17.580 align:start position:0% case all right well so essentially what 00:23:17.580 --> 00:23:19.430 align:start position:0% case all right well so essentially what what<00:23:17.820> name<00:23:18.419> did<00:23:18.659> which<00:23:18.840> I<00:23:19.020> didn't<00:23:19.080> realize 00:23:19.430 --> 00:23:19.440 align:start position:0% what name did which I didn't realize 00:23:19.440 --> 00:23:21.350 align:start position:0% what name did which I didn't realize when<00:23:19.679> he<00:23:19.799> was<00:23:19.919> developing<00:23:20.220> it<00:23:20.400> uh<00:23:20.940> but<00:23:21.179> I 00:23:21.350 --> 00:23:21.360 align:start position:0% when he was developing it uh but I 00:23:21.360 --> 00:23:23.210 align:start position:0% when he was developing it uh but I thought<00:23:21.480> it<00:23:21.600> was<00:23:21.659> super<00:23:21.840> cool<00:23:22.020> is<00:23:22.320> that 00:23:23.210 --> 00:23:23.220 align:start position:0% thought it was super cool is that 00:23:23.220 --> 00:23:26.210 align:start position:0% thought it was super cool is that um within<00:23:23.820> within<00:23:24.360> the<00:23:24.600> realm<00:23:24.960> of 00:23:26.210 --> 00:23:26.220 align:start position:0% um within within the realm of 00:23:26.220 --> 00:23:27.830 align:start position:0% um within within the realm of um<00:23:26.280> the<00:23:26.520> the<00:23:26.640> sales<00:23:26.940> which<00:23:27.360> have<00:23:27.600> this 00:23:27.830 --> 00:23:27.840 align:start position:0% um the the sales which have this 00:23:27.840 --> 00:23:30.289 align:start position:0% um the the sales which have this particle<00:23:28.200> guard<00:23:28.440> and<00:23:28.679> module<00:23:29.039> enabled<00:23:29.460> uh 00:23:30.289 --> 00:23:30.299 align:start position:0% particle guard and module enabled uh 00:23:30.299 --> 00:23:31.850 align:start position:0% particle guard and module enabled uh because<00:23:30.480> you<00:23:30.780> generate<00:23:31.200> them<00:23:31.380> using<00:23:31.679> a 00:23:31.850 --> 00:23:31.860 align:start position:0% because you generate them using a 00:23:31.860 --> 00:23:34.730 align:start position:0% because you generate them using a specific<00:23:32.159> like<00:23:32.520> uh<00:23:32.880> Contra<00:23:33.299> Factory<00:23:33.440> uh<00:23:34.440> you 00:23:34.730 --> 00:23:34.740 align:start position:0% specific like uh Contra Factory uh you 00:23:34.740 --> 00:23:40.370 align:start position:0% specific like uh Contra Factory uh you can<00:23:34.919> still<00:23:35.640> uh<00:23:36.419> transfer<00:23:37.080> the<00:23:37.620> asset<00:23:38.299> uh<00:23:39.299> to 00:23:40.370 --> 00:23:40.380 align:start position:0% can still uh transfer the asset uh to 00:23:40.380 --> 00:23:42.770 align:start position:0% can still uh transfer the asset uh to essentially<00:23:41.039> like<00:23:41.220> any<00:23:41.520> safe<00:23:41.820> that's<00:23:42.419> that 00:23:42.770 --> 00:23:42.780 align:start position:0% essentially like any safe that's that 00:23:42.780 --> 00:23:45.710 align:start position:0% essentially like any safe that's that has<00:23:43.200> that<00:23:43.740> particular<00:23:44.100> Guardian<00:23:44.460> module<00:23:44.880> and 00:23:45.710 --> 00:23:45.720 align:start position:0% has that particular Guardian module and 00:23:45.720 --> 00:23:48.230 align:start position:0% has that particular Guardian module and the<00:23:45.840> asset<00:23:46.260> token<00:23:46.620> uh<00:23:46.980> the<00:23:47.280> the<00:23:47.460> ATR<00:23:47.880> token 00:23:48.230 --> 00:23:48.240 align:start position:0% the asset token uh the the ATR token 00:23:48.240 --> 00:23:50.450 align:start position:0% the asset token uh the the ATR token will<00:23:48.539> still<00:23:48.720> be<00:23:48.960> executable<00:23:49.620> and<00:23:50.039> you'll<00:23:50.220> be 00:23:50.450 --> 00:23:50.460 align:start position:0% will still be executable and you'll be 00:23:50.460 --> 00:23:52.070 align:start position:0% will still be executable and you'll be able<00:23:50.640> to<00:23:50.760> essentially<00:23:51.240> get<00:23:51.419> it<00:23:51.539> from<00:23:51.720> anyone 00:23:52.070 --> 00:23:52.080 align:start position:0% able to essentially get it from anyone 00:23:52.080 --> 00:23:55.549 align:start position:0% able to essentially get it from anyone anyone's<00:23:52.740> wallet<00:23:53.240> uh<00:23:54.240> within<00:23:54.659> within<00:23:55.140> that 00:23:55.549 --> 00:23:55.559 align:start position:0% anyone's wallet uh within within that 00:23:55.559 --> 00:23:56.930 align:start position:0% anyone's wallet uh within within that particle<00:23:55.980> realm<00:23:56.280> so<00:23:56.400> obviously<00:23:56.700> like<00:23:56.760> you 00:23:56.930 --> 00:23:56.940 align:start position:0% particle realm so obviously like you 00:23:56.940 --> 00:23:59.210 align:start position:0% particle realm so obviously like you have<00:23:57.120> to<00:23:57.240> you<00:23:57.419> have<00:23:57.659> to<00:23:57.840> be 00:23:59.210 --> 00:23:59.220 align:start position:0% have to you have to be 00:23:59.220 --> 00:24:01.970 align:start position:0% have to you have to be um<00:23:59.280> you<00:23:59.880> have<00:24:00.480> to<00:24:00.659> realize<00:24:01.200> like<00:24:01.440> the<00:24:01.620> particle 00:24:01.970 --> 00:24:01.980 align:start position:0% um you have to realize like the particle 00:24:01.980 --> 00:24:03.649 align:start position:0% um you have to realize like the particle asset<00:24:02.280> has<00:24:02.400> this<00:24:02.640> deed<00:24:02.940> created<00:24:03.179> around<00:24:03.419> it 00:24:03.649 --> 00:24:03.659 align:start position:0% asset has this deed created around it 00:24:03.659 --> 00:24:05.149 align:start position:0% asset has this deed created around it but<00:24:03.900> it's<00:24:04.080> essentially<00:24:04.440> the<00:24:04.679> same<00:24:04.799> as<00:24:04.980> like 00:24:05.149 --> 00:24:05.159 align:start position:0% but it's essentially the same as like 00:24:05.159 --> 00:24:06.950 align:start position:0% but it's essentially the same as like having<00:24:05.400> real<00:24:05.940> estate<00:24:06.120> property<00:24:06.600> and<00:24:06.780> like 00:24:06.950 --> 00:24:06.960 align:start position:0% having real estate property and like 00:24:06.960 --> 00:24:09.169 align:start position:0% having real estate property and like having<00:24:07.140> a<00:24:07.320> deed<00:24:07.559> on<00:24:07.740> that<00:24:07.860> property 00:24:09.169 --> 00:24:09.179 align:start position:0% having a deed on that property 00:24:09.179 --> 00:24:10.370 align:start position:0% having a deed on that property um<00:24:09.240> and 00:24:10.370 --> 00:24:10.380 align:start position:0% um and 00:24:10.380 --> 00:24:13.789 align:start position:0% um and um then<00:24:10.740> you<00:24:11.220> know<00:24:11.280> we<00:24:11.580> can<00:24:11.760> be<00:24:11.940> like<00:24:12.120> friends 00:24:13.789 --> 00:24:13.799 align:start position:0% um then you know we can be like friends 00:24:13.799 --> 00:24:15.770 align:start position:0% um then you know we can be like friends um<00:24:13.860> that<00:24:14.159> once<00:24:14.640> you<00:24:14.760> like<00:24:14.880> reuse<00:24:15.179> our<00:24:15.419> gaming 00:24:15.770 --> 00:24:15.780 align:start position:0% um that once you like reuse our gaming 00:24:15.780 --> 00:24:17.930 align:start position:0% um that once you like reuse our gaming assets<00:24:16.140> uh<00:24:16.799> we<00:24:16.919> can<00:24:17.039> have<00:24:17.159> the<00:24:17.340> asset<00:24:17.700> token 00:24:17.930 --> 00:24:17.940 align:start position:0% assets uh we can have the asset token 00:24:17.940 --> 00:24:20.690 align:start position:0% assets uh we can have the asset token regenerated<00:24:18.600> I<00:24:19.200> can<00:24:19.260> safely<00:24:19.620> like<00:24:19.980> give<00:24:20.400> my 00:24:20.690 --> 00:24:20.700 align:start position:0% regenerated I can safely like give my 00:24:20.700 --> 00:24:22.909 align:start position:0% regenerated I can safely like give my you<00:24:20.880> know<00:24:20.940> magic<00:24:21.240> swords<00:24:21.720> to<00:24:21.960> to<00:24:22.140> knives 00:24:22.909 --> 00:24:22.919 align:start position:0% you know magic swords to to knives 00:24:22.919 --> 00:24:26.330 align:start position:0% you know magic swords to to knives wallet<00:24:23.400> uh<00:24:24.360> I'll<00:24:24.600> tell<00:24:25.080> him<00:24:25.260> to<00:24:25.620> give<00:24:26.039> it<00:24:26.159> back 00:24:26.330 --> 00:24:26.340 align:start position:0% wallet uh I'll tell him to give it back 00:24:26.340 --> 00:24:28.430 align:start position:0% wallet uh I'll tell him to give it back to<00:24:26.460> me<00:24:26.580> in<00:24:26.700> 30<00:24:26.820> days<00:24:27.059> if<00:24:27.419> you<00:24:27.600> I<00:24:27.900> can<00:24:28.020> just<00:24:28.140> claim 00:24:28.430 --> 00:24:28.440 align:start position:0% to me in 30 days if you I can just claim 00:24:28.440 --> 00:24:30.409 align:start position:0% to me in 30 days if you I can just claim it<00:24:28.559> back 00:24:30.409 --> 00:24:30.419 align:start position:0% it back 00:24:30.419 --> 00:24:32.149 align:start position:0% it back and<00:24:30.960> obviously<00:24:31.320> you<00:24:31.440> can<00:24:31.559> you<00:24:31.740> can<00:24:31.919> put<00:24:32.039> it 00:24:32.149 --> 00:24:32.159 align:start position:0% and obviously you can you can put it 00:24:32.159 --> 00:24:35.149 align:start position:0% and obviously you can you can put it into<00:24:32.280> contract<00:24:32.820> you<00:24:33.059> can<00:24:33.299> set<00:24:33.780> your<00:24:34.140> uh<00:24:34.919> set 00:24:35.149 --> 00:24:35.159 align:start position:0% into contract you can set your uh set 00:24:35.159 --> 00:24:37.730 align:start position:0% into contract you can set your uh set kind<00:24:35.760> of<00:24:35.880> like<00:24:36.000> exact<00:24:36.900> parameters<00:24:37.380> on<00:24:37.559> like 00:24:37.730 --> 00:24:37.740 align:start position:0% kind of like exact parameters on like 00:24:37.740 --> 00:24:39.590 align:start position:0% kind of like exact parameters on like how<00:24:37.919> the<00:24:38.039> return<00:24:38.220> should<00:24:38.580> happen<00:24:38.820> but<00:24:39.480> the 00:24:39.590 --> 00:24:39.600 align:start position:0% how the return should happen but the 00:24:39.600 --> 00:24:41.690 align:start position:0% how the return should happen but the asset<00:24:39.960> token<00:24:40.260> the<00:24:40.559> the<00:24:40.799> HR<00:24:41.100> token<00:24:41.520> is 00:24:41.690 --> 00:24:41.700 align:start position:0% asset token the the HR token is 00:24:41.700 --> 00:24:43.549 align:start position:0% asset token the the HR token is basically<00:24:42.000> the<00:24:42.780> the<00:24:43.020> thing<00:24:43.200> that<00:24:43.380> will 00:24:43.549 --> 00:24:43.559 align:start position:0% basically the the thing that will 00:24:43.559 --> 00:24:47.990 align:start position:0% basically the the thing that will execute<00:24:43.860> a<00:24:44.039> transfer<00:24:44.340> later<00:24:44.520> on 00:24:47.990 --> 00:24:48.000 align:start position:0% 00:24:48.000 --> 00:24:50.029 align:start position:0% perfect<00:24:48.360> thank<00:24:48.600> you<00:24:48.720> so<00:24:49.260> much<00:24:49.260> name<00:24:49.740> and 00:24:50.029 --> 00:24:50.039 align:start position:0% perfect thank you so much name and 00:24:50.039 --> 00:24:52.220 align:start position:0% perfect thank you so much name and Joseph