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:11.530 align:start position:0% [Music] 00:00:11.530 --> 00:00:11.540 align:start position:0% 00:00:11.540 --> 00:00:14.870 align:start position:0% this<00:00:12.540> is<00:00:12.599> Ryan<00:00:12.860> we're<00:00:13.860> with<00:00:14.040> openc<00:00:14.460> and<00:00:14.700> we're 00:00:14.870 --> 00:00:14.880 align:start position:0% this is Ryan we're with openc and we're 00:00:14.880 --> 00:00:16.550 align:start position:0% this is Ryan we're with openc and we're going<00:00:15.059> to<00:00:15.179> talk<00:00:15.299> about<00:00:15.480> the<00:00:16.139> seaport 00:00:16.550 --> 00:00:16.560 align:start position:0% going to talk about the seaport 00:00:16.560 --> 00:00:19.189 align:start position:0% going to talk about the seaport Marketplace<00:00:17.160> and<00:00:17.820> some<00:00:18.359> more<00:00:18.600> advanced 00:00:19.189 --> 00:00:19.199 align:start position:0% Marketplace and some more advanced 00:00:19.199 --> 00:00:21.769 align:start position:0% Marketplace and some more advanced techniques<00:00:19.740> for<00:00:19.980> how<00:00:20.220> to<00:00:20.340> utilize<00:00:21.000> it<00:00:21.180> and 00:00:21.769 --> 00:00:21.779 align:start position:0% techniques for how to utilize it and 00:00:21.779 --> 00:00:25.250 align:start position:0% techniques for how to utilize it and interact<00:00:22.439> with<00:00:22.619> it<00:00:22.800> and<00:00:23.100> build<00:00:23.340> on<00:00:23.520> top 00:00:25.250 --> 00:00:25.260 align:start position:0% interact with it and build on top 00:00:25.260 --> 00:00:29.509 align:start position:0% interact with it and build on top so<00:00:26.220> Seaport<00:00:27.060> is<00:00:27.300> a<00:00:27.420> beast<00:00:27.720> there's<00:00:28.439> a<00:00:29.099> single 00:00:29.509 --> 00:00:29.519 align:start position:0% so Seaport is a beast there's a single 00:00:29.519 --> 00:00:31.189 align:start position:0% so Seaport is a beast there's a single contract<00:00:29.880> but<00:00:30.060> there's<00:00:30.240> a<00:00:30.420> lot<00:00:30.480> going<00:00:30.720> on<00:00:30.900> and 00:00:31.189 --> 00:00:31.199 align:start position:0% contract but there's a lot going on and 00:00:31.199 --> 00:00:32.450 align:start position:0% contract but there's a lot going on and so<00:00:31.380> we're<00:00:31.560> gonna 00:00:32.450 --> 00:00:32.460 align:start position:0% so we're gonna 00:00:32.460 --> 00:00:34.430 align:start position:0% so we're gonna work<00:00:33.059> our<00:00:33.239> way<00:00:33.420> through<00:00:33.600> first<00:00:33.960> start<00:00:34.260> with 00:00:34.430 --> 00:00:34.440 align:start position:0% work our way through first start with 00:00:34.440 --> 00:00:38.150 align:start position:0% work our way through first start with some<00:00:34.680> of<00:00:34.800> the<00:00:35.040> high<00:00:35.640> level<00:00:36.020> uh<00:00:37.020> key<00:00:37.500> points<00:00:37.920> and 00:00:38.150 --> 00:00:38.160 align:start position:0% some of the high level uh key points and 00:00:38.160 --> 00:00:40.310 align:start position:0% some of the high level uh key points and then<00:00:38.280> from<00:00:38.640> there<00:00:38.820> we'll<00:00:39.300> we'll<00:00:39.960> get<00:00:40.200> into 00:00:40.310 --> 00:00:40.320 align:start position:0% then from there we'll we'll get into 00:00:40.320 --> 00:00:42.950 align:start position:0% then from there we'll we'll get into some<00:00:40.620> of<00:00:40.739> these<00:00:40.860> Advanced<00:00:41.219> Techniques 00:00:42.950 --> 00:00:42.960 align:start position:0% some of these Advanced Techniques 00:00:42.960 --> 00:00:44.209 align:start position:0% some of these Advanced Techniques so 00:00:44.209 --> 00:00:44.219 align:start position:0% so 00:00:44.219 --> 00:00:46.910 align:start position:0% so first<00:00:44.700> thing<00:00:44.820> to<00:00:45.000> understand<00:00:45.200> is<00:00:46.200> that<00:00:46.620> there 00:00:46.910 --> 00:00:46.920 align:start position:0% first thing to understand is that there 00:00:46.920 --> 00:00:51.709 align:start position:0% first thing to understand is that there are<00:00:47.300> two<00:00:48.500> arrays<00:00:49.500> that<00:00:50.160> dictate<00:00:50.579> the<00:00:51.120> basics 00:00:51.709 --> 00:00:51.719 align:start position:0% are two arrays that dictate the basics 00:00:51.719 --> 00:00:55.189 align:start position:0% are two arrays that dictate the basics of<00:00:51.899> A<00:00:52.079> C<00:00:52.260> Port<00:00:52.559> listing<00:00:53.399> or<00:00:53.640> offer<00:00:54.120> the<00:00:55.020> first 00:00:55.189 --> 00:00:55.199 align:start position:0% of A C Port listing or offer the first 00:00:55.199 --> 00:00:59.090 align:start position:0% of A C Port listing or offer the first is<00:00:55.440> the<00:00:55.739> offer<00:00:56.100> and<00:00:56.879> that's<00:00:57.000> all<00:00:57.420> of<00:00:57.600> the<00:00:57.899> items 00:00:59.090 --> 00:00:59.100 align:start position:0% is the offer and that's all of the items 00:00:59.100 --> 00:01:04.910 align:start position:0% is the offer and that's all of the items native<00:00:59.699> tokens<00:01:00.180> erc20<00:01:01.140> EOC<00:01:01.680> 721<00:01:02.480> 1155<00:01:03.480> but<00:01:04.440> you 00:01:04.910 --> 00:01:04.920 align:start position:0% native tokens erc20 EOC 721 1155 but you 00:01:04.920 --> 00:01:07.730 align:start position:0% native tokens erc20 EOC 721 1155 but you the<00:01:05.159> offerer<00:01:05.640> are<00:01:05.880> going<00:01:06.000> to<00:01:06.180> spend<00:01:06.420> then<00:01:07.380> on 00:01:07.730 --> 00:01:07.740 align:start position:0% the offerer are going to spend then on 00:01:07.740 --> 00:01:10.130 align:start position:0% the offerer are going to spend then on the<00:01:07.799> other<00:01:07.920> end<00:01:08.100> you<00:01:08.520> have<00:01:08.700> the<00:01:09.540> consideration 00:01:10.130 --> 00:01:10.140 align:start position:0% the other end you have the consideration 00:01:10.140 --> 00:01:13.190 align:start position:0% the other end you have the consideration which<00:01:11.100> is<00:01:11.280> everything<00:01:11.640> that<00:01:12.060> you<00:01:12.360> or<00:01:12.780> others 00:01:13.190 --> 00:01:13.200 align:start position:0% which is everything that you or others 00:01:13.200 --> 00:01:15.109 align:start position:0% which is everything that you or others are<00:01:13.320> going<00:01:13.439> to<00:01:13.619> get<00:01:13.799> back 00:01:15.109 --> 00:01:15.119 align:start position:0% are going to get back 00:01:15.119 --> 00:01:17.330 align:start position:0% are going to get back if<00:01:15.600> you<00:01:15.720> want<00:01:15.840> to<00:01:15.960> spend<00:01:16.200> the<00:01:16.439> offer<00:01:16.740> items<00:01:17.159> you 00:01:17.330 --> 00:01:17.340 align:start position:0% if you want to spend the offer items you 00:01:17.340 --> 00:01:21.289 align:start position:0% if you want to spend the offer items you gotta<00:01:18.000> get<00:01:18.479> the<00:01:18.659> consideration 00:01:21.289 --> 00:01:21.299 align:start position:0% 00:01:21.299 --> 00:01:24.230 align:start position:0% so<00:01:21.659> there's<00:01:21.780> also<00:01:22.259> this<00:01:22.740> idea<00:01:23.100> of<00:01:23.520> a<00:01:23.939> Zone 00:01:24.230 --> 00:01:24.240 align:start position:0% so there's also this idea of a Zone 00:01:24.240 --> 00:01:27.950 align:start position:0% so there's also this idea of a Zone every<00:01:24.840> Seaport<00:01:25.619> order<00:01:25.920> has<00:01:26.580> an<00:01:27.240> optional<00:01:27.600> Zone 00:01:27.950 --> 00:01:27.960 align:start position:0% every Seaport order has an optional Zone 00:01:27.960 --> 00:01:30.289 align:start position:0% every Seaport order has an optional Zone that<00:01:28.200> you<00:01:28.320> can<00:01:28.439> set<00:01:28.619> that's<00:01:28.979> a<00:01:29.280> contract<00:01:29.759> that 00:01:30.289 --> 00:01:30.299 align:start position:0% that you can set that's a contract that 00:01:30.299 --> 00:01:32.929 align:start position:0% that you can set that's a contract that gives<00:01:30.479> a<00:01:30.780> thumbs<00:01:31.080> up<00:01:31.140> or<00:01:31.380> a<00:01:31.560> thumbs<00:01:31.860> down<00:01:31.979> on 00:01:32.929 --> 00:01:32.939 align:start position:0% gives a thumbs up or a thumbs down on 00:01:32.939 --> 00:01:34.789 align:start position:0% gives a thumbs up or a thumbs down on whether<00:01:33.180> that<00:01:33.540> particular<00:01:34.020> order<00:01:34.259> is<00:01:34.560> still 00:01:34.789 --> 00:01:34.799 align:start position:0% whether that particular order is still 00:01:34.799 --> 00:01:35.990 align:start position:0% whether that particular order is still valid 00:01:35.990 --> 00:01:36.000 align:start position:0% valid 00:01:36.000 --> 00:01:38.410 align:start position:0% valid there's<00:01:36.420> also<00:01:36.780> a<00:01:37.020> concept<00:01:37.320> of<00:01:37.680> a<00:01:37.860> conduit 00:01:38.410 --> 00:01:38.420 align:start position:0% there's also a concept of a conduit 00:01:38.420 --> 00:01:42.170 align:start position:0% there's also a concept of a conduit which<00:01:39.420> is<00:01:39.680> a<00:01:40.680> it's<00:01:41.100> a<00:01:41.280> contract<00:01:41.640> that<00:01:41.939> you<00:01:42.060> can 00:01:42.170 --> 00:01:42.180 align:start position:0% which is a it's a contract that you can 00:01:42.180 --> 00:01:44.170 align:start position:0% which is a it's a contract that you can approve<00:01:42.780> to 00:01:44.170 --> 00:01:44.180 align:start position:0% approve to 00:01:44.180 --> 00:01:46.789 align:start position:0% approve to transfer<00:01:45.180> your<00:01:45.360> tokens<00:01:45.720> so<00:01:46.320> you<00:01:46.439> set<00:01:46.619> your 00:01:46.789 --> 00:01:46.799 align:start position:0% transfer your tokens so you set your 00:01:46.799 --> 00:01:49.730 align:start position:0% transfer your tokens so you set your approvals<00:01:47.159> on<00:01:47.220> the<00:01:47.340> Conduit<00:01:47.700> and<00:01:48.540> from<00:01:48.840> there 00:01:49.730 --> 00:01:49.740 align:start position:0% approvals on the Conduit and from there 00:01:49.740 --> 00:01:53.149 align:start position:0% approvals on the Conduit and from there uh<00:01:50.640> you<00:01:51.240> can<00:01:51.360> set<00:01:51.600> additional<00:01:52.200> marketplaces 00:01:53.149 --> 00:01:53.159 align:start position:0% uh you can set additional marketplaces 00:01:53.159 --> 00:01:55.490 align:start position:0% uh you can set additional marketplaces or<00:01:53.340> contracts<00:01:53.880> on<00:01:54.600> that<00:01:54.720> conduit<00:01:55.079> support 00:01:55.490 --> 00:01:55.500 align:start position:0% or contracts on that conduit support 00:01:55.500 --> 00:01:57.770 align:start position:0% or contracts on that conduit support multiple<00:01:55.979> marketplaces<00:01:56.939> migrate<00:01:57.420> to<00:01:57.540> new 00:01:57.770 --> 00:01:57.780 align:start position:0% multiple marketplaces migrate to new 00:01:57.780 --> 00:02:01.969 align:start position:0% multiple marketplaces migrate to new versions<00:01:58.200> of<00:01:58.439> Seaport<00:01:58.920> so<00:01:59.700> on<00:01:59.820> so<00:02:00.000> forth 00:02:01.969 --> 00:02:01.979 align:start position:0% versions of Seaport so on so forth 00:02:01.979 --> 00:02:04.850 align:start position:0% versions of Seaport so on so forth so<00:02:02.579> when<00:02:02.820> you<00:02:02.939> it<00:02:03.240> comes<00:02:03.540> time<00:02:03.659> to<00:02:04.020> create<00:02:04.380> an 00:02:04.850 --> 00:02:04.860 align:start position:0% so when you it comes time to create an 00:02:04.860 --> 00:02:07.630 align:start position:0% so when you it comes time to create an order<00:02:05.040> to<00:02:05.820> list<00:02:06.000> your<00:02:06.240> nft 00:02:07.630 --> 00:02:07.640 align:start position:0% order to list your nft 00:02:07.640 --> 00:02:10.669 align:start position:0% order to list your nft the<00:02:08.640> primary<00:02:09.119> way<00:02:09.420> to<00:02:09.539> do<00:02:09.720> it<00:02:09.840> is<00:02:10.319> you<00:02:10.500> just 00:02:10.669 --> 00:02:10.679 align:start position:0% the primary way to do it is you just 00:02:10.679 --> 00:02:13.430 align:start position:0% the primary way to do it is you just sign<00:02:11.160> an<00:02:11.640> off-chain<00:02:12.120> listing 00:02:13.430 --> 00:02:13.440 align:start position:0% sign an off-chain listing 00:02:13.440 --> 00:02:15.650 align:start position:0% sign an off-chain listing this<00:02:13.920> is<00:02:14.040> an<00:02:14.220> example<00:02:14.640> payload<00:02:15.420> that<00:02:15.540> you 00:02:15.650 --> 00:02:15.660 align:start position:0% this is an example payload that you 00:02:15.660 --> 00:02:17.510 align:start position:0% this is an example payload that you would<00:02:15.780> see<00:02:15.959> in<00:02:16.140> metamask<00:02:16.620> you're<00:02:17.160> gonna<00:02:17.280> have 00:02:17.510 --> 00:02:17.520 align:start position:0% would see in metamask you're gonna have 00:02:17.520 --> 00:02:18.229 align:start position:0% would see in metamask you're gonna have to 00:02:18.229 --> 00:02:18.239 align:start position:0% to 00:02:18.239 --> 00:02:20.449 align:start position:0% to pop<00:02:18.840> open<00:02:19.020> the<00:02:19.319> expanded<00:02:19.739> view<00:02:19.860> to<00:02:20.160> get<00:02:20.280> this 00:02:20.449 --> 00:02:20.459 align:start position:0% pop open the expanded view to get this 00:02:20.459 --> 00:02:24.430 align:start position:0% pop open the expanded view to get this whole<00:02:20.640> thing<00:02:20.819> but<00:02:21.599> it's<00:02:22.319> got<00:02:22.700> the<00:02:23.700> offer<00:02:24.060> array 00:02:24.430 --> 00:02:24.440 align:start position:0% whole thing but it's got the offer array 00:02:24.440 --> 00:02:26.990 align:start position:0% whole thing but it's got the offer array consideration<00:02:25.440> array<00:02:25.920> start<00:02:26.220> time<00:02:26.459> end<00:02:26.760> time 00:02:26.990 --> 00:02:27.000 align:start position:0% consideration array start time end time 00:02:27.000 --> 00:02:29.869 align:start position:0% consideration array start time end time zone<00:02:27.300> conduit 00:02:29.869 --> 00:02:29.879 align:start position:0% 00:02:29.879 --> 00:02:33.110 align:start position:0% then<00:02:30.959> another<00:02:31.620> method<00:02:32.099> you<00:02:32.340> can<00:02:32.459> use<00:02:32.700> to 00:02:33.110 --> 00:02:33.120 align:start position:0% then another method you can use to 00:02:33.120 --> 00:02:36.110 align:start position:0% then another method you can use to create<00:02:33.599> an<00:02:33.900> order<00:02:34.080> is<00:02:34.560> to<00:02:34.920> call<00:02:35.220> this<00:02:35.760> function 00:02:36.110 --> 00:02:36.120 align:start position:0% create an order is to call this function 00:02:36.120 --> 00:02:37.550 align:start position:0% create an order is to call this function validate 00:02:37.550 --> 00:02:37.560 align:start position:0% validate 00:02:37.560 --> 00:02:39.530 align:start position:0% validate and<00:02:37.620> that<00:02:38.099> means<00:02:38.459> you<00:02:39.000> don't<00:02:39.120> need<00:02:39.360> a 00:02:39.530 --> 00:02:39.540 align:start position:0% and that means you don't need a 00:02:39.540 --> 00:02:40.970 align:start position:0% and that means you don't need a signature<00:02:39.959> at<00:02:40.200> all 00:02:40.970 --> 00:02:40.980 align:start position:0% signature at all 00:02:40.980 --> 00:02:42.530 align:start position:0% signature at all you<00:02:41.700> just 00:02:42.530 --> 00:02:42.540 align:start position:0% you just 00:02:42.540 --> 00:02:45.530 align:start position:0% you just provide<00:02:43.260> the<00:02:43.560> order<00:02:43.680> and<00:02:44.340> it<00:02:44.519> gets<00:02:44.819> listed<00:02:45.300> on 00:02:45.530 --> 00:02:45.540 align:start position:0% provide the order and it gets listed on 00:02:45.540 --> 00:02:48.470 align:start position:0% provide the order and it gets listed on chain<00:02:45.840> so<00:02:46.440> to<00:02:46.620> speak 00:02:48.470 --> 00:02:48.480 align:start position:0% chain so to speak 00:02:48.480 --> 00:02:51.770 align:start position:0% chain so to speak the<00:02:49.019> interesting<00:02:49.500> thing<00:02:49.620> about<00:02:49.920> both<00:02:50.780> signing 00:02:51.770 --> 00:02:51.780 align:start position:0% the interesting thing about both signing 00:02:51.780 --> 00:02:53.930 align:start position:0% the interesting thing about both signing an<00:02:51.900> order<00:02:52.080> or<00:02:52.500> calling<00:02:52.860> validate<00:02:53.280> is<00:02:53.519> you<00:02:53.819> have 00:02:53.930 --> 00:02:53.940 align:start position:0% an order or calling validate is you have 00:02:53.940 --> 00:02:56.930 align:start position:0% an order or calling validate is you have to<00:02:54.120> explicitly<00:02:54.840> cancel<00:02:55.700> you<00:02:56.700> have<00:02:56.760> to 00:02:56.930 --> 00:02:56.940 align:start position:0% to explicitly cancel you have to 00:02:56.940 --> 00:02:59.570 align:start position:0% to explicitly cancel you have to actually<00:02:57.120> call<00:02:57.599> and<00:02:58.140> tell<00:02:58.379> Seaport<00:02:58.980> I'm<00:02:59.400> no 00:02:59.570 --> 00:02:59.580 align:start position:0% actually call and tell Seaport I'm no 00:02:59.580 --> 00:03:01.430 align:start position:0% actually call and tell Seaport I'm no longer<00:02:59.760> interested<00:03:00.120> in<00:03:00.300> filling<00:03:00.720> this 00:03:01.430 --> 00:03:01.440 align:start position:0% longer interested in filling this 00:03:01.440 --> 00:03:04.250 align:start position:0% longer interested in filling this yeah 00:03:04.250 --> 00:03:04.260 align:start position:0% 00:03:04.260 --> 00:03:07.550 align:start position:0% signatures<00:03:05.160> are<00:03:05.459> not<00:03:05.640> just<00:03:05.879> standard<00:03:06.560> ecdsa 00:03:07.550 --> 00:03:07.560 align:start position:0% signatures are not just standard ecdsa 00:03:07.560 --> 00:03:08.809 align:start position:0% signatures are not just standard ecdsa they're<00:03:07.920> also 00:03:08.809 --> 00:03:08.819 align:start position:0% they're also 00:03:08.819 --> 00:03:13.250 align:start position:0% they're also support<00:03:09.560> for<00:03:10.640> 1271<00:03:11.640> which<00:03:12.120> is<00:03:12.300> is<00:03:12.780> valid 00:03:13.250 --> 00:03:13.260 align:start position:0% support for 1271 which is is valid 00:03:13.260 --> 00:03:14.390 align:start position:0% support for 1271 which is is valid signature 00:03:14.390 --> 00:03:14.400 align:start position:0% signature 00:03:14.400 --> 00:03:17.270 align:start position:0% signature Seaport<00:03:15.000> will<00:03:15.239> give<00:03:15.420> the<00:03:15.900> offerer 00:03:17.270 --> 00:03:17.280 align:start position:0% Seaport will give the offerer 00:03:17.280 --> 00:03:22.369 align:start position:0% Seaport will give the offerer a<00:03:18.060> digest<00:03:18.739> basically<00:03:19.739> the<00:03:19.920> order<00:03:20.099> hash<00:03:20.840> and<00:03:21.840> a 00:03:22.369 --> 00:03:22.379 align:start position:0% a digest basically the order hash and a 00:03:22.379 --> 00:03:23.449 align:start position:0% a digest basically the order hash and a signature 00:03:23.449 --> 00:03:23.459 align:start position:0% signature 00:03:23.459 --> 00:03:26.030 align:start position:0% signature and<00:03:24.060> then<00:03:24.239> leave<00:03:24.840> it<00:03:24.959> up<00:03:25.080> to<00:03:25.200> the<00:03:25.379> contract<00:03:25.739> to 00:03:26.030 --> 00:03:26.040 align:start position:0% and then leave it up to the contract to 00:03:26.040 --> 00:03:28.850 align:start position:0% and then leave it up to the contract to say<00:03:26.280> yes<00:03:26.519> this<00:03:27.000> order<00:03:27.239> is<00:03:27.420> good<00:03:27.659> this<00:03:28.560> one's 00:03:28.850 --> 00:03:28.860 align:start position:0% say yes this order is good this one's 00:03:28.860 --> 00:03:30.290 align:start position:0% say yes this order is good this one's not 00:03:30.290 --> 00:03:30.300 align:start position:0% not 00:03:30.300 --> 00:03:32.750 align:start position:0% not and<00:03:30.840> that<00:03:30.959> works<00:03:31.260> with<00:03:31.560> both<00:03:32.040> traditional 00:03:32.750 --> 00:03:32.760 align:start position:0% and that works with both traditional 00:03:32.760 --> 00:03:35.570 align:start position:0% and that works with both traditional signatures<00:03:33.239> as<00:03:33.480> well<00:03:33.599> as<00:03:33.720> validations<00:03:34.580> and 00:03:35.570 --> 00:03:35.580 align:start position:0% signatures as well as validations and 00:03:35.580 --> 00:03:38.449 align:start position:0% signatures as well as validations and you<00:03:35.819> can<00:03:35.940> use<00:03:36.180> this<00:03:36.840> technique<00:03:37.200> to<00:03:37.680> list<00:03:37.980> from 00:03:38.449 --> 00:03:38.459 align:start position:0% you can use this technique to list from 00:03:38.459 --> 00:03:41.149 align:start position:0% you can use this technique to list from a<00:03:39.420> smart<00:03:39.599> wallet<00:03:40.019> or<00:03:40.260> a<00:03:40.379> multi-sig<00:03:40.860> without 00:03:41.149 --> 00:03:41.159 align:start position:0% a smart wallet or a multi-sig without 00:03:41.159 --> 00:03:43.130 align:start position:0% a smart wallet or a multi-sig without having<00:03:41.400> to<00:03:41.580> pay<00:03:41.760> cash 00:03:43.130 --> 00:03:43.140 align:start position:0% having to pay cash 00:03:43.140 --> 00:03:45.170 align:start position:0% having to pay cash but<00:03:43.500> you<00:03:43.560> can<00:03:43.739> also<00:03:44.040> and<00:03:44.519> here<00:03:44.700> we<00:03:44.819> start<00:03:45.000> to 00:03:45.170 --> 00:03:45.180 align:start position:0% but you can also and here we start to 00:03:45.180 --> 00:03:48.350 align:start position:0% but you can also and here we start to get<00:03:45.360> into<00:03:45.540> the<00:03:46.019> Advanced<00:03:46.860> Techniques<00:03:47.400> you<00:03:48.239> can 00:03:48.350 --> 00:03:48.360 align:start position:0% get into the Advanced Techniques you can 00:03:48.360 --> 00:03:50.869 align:start position:0% get into the Advanced Techniques you can utilize<00:03:48.900> 1271 00:03:50.869 --> 00:03:50.879 align:start position:0% utilize 1271 00:03:50.879 --> 00:03:55.610 align:start position:0% utilize 1271 to<00:03:51.659> do<00:03:52.340> Dynamic<00:03:53.340> orders<00:03:53.879> where<00:03:54.500> you<00:03:55.500> might 00:03:55.610 --> 00:03:55.620 align:start position:0% to do Dynamic orders where you might 00:03:55.620 --> 00:03:57.410 align:start position:0% to do Dynamic orders where you might have<00:03:55.799> a<00:03:55.980> contract<00:03:56.280> that's<00:03:56.459> willing<00:03:56.940> to<00:03:57.120> it 00:03:57.410 --> 00:03:57.420 align:start position:0% have a contract that's willing to it 00:03:57.420 --> 00:04:00.229 align:start position:0% have a contract that's willing to it wants<00:03:57.900> to<00:03:57.959> update<00:03:58.379> the<00:03:58.799> order<00:03:58.920> based<00:03:59.519> on<00:03:59.640> a 00:04:00.229 --> 00:04:00.239 align:start position:0% wants to update the order based on a 00:04:00.239 --> 00:04:01.850 align:start position:0% wants to update the order based on a price<00:04:00.420> that's<00:04:00.659> coming<00:04:00.900> back<00:04:01.080> from<00:04:01.319> an<00:04:01.500> oracle 00:04:01.850 --> 00:04:01.860 align:start position:0% price that's coming back from an oracle 00:04:01.860 --> 00:04:04.789 align:start position:0% price that's coming back from an oracle or<00:04:02.040> maybe<00:04:02.220> it's<00:04:02.459> implementing<00:04:03.140> a<00:04:04.140> bonding 00:04:04.789 --> 00:04:04.799 align:start position:0% or maybe it's implementing a bonding 00:04:04.799 --> 00:04:06.470 align:start position:0% or maybe it's implementing a bonding curve<00:04:05.099> or<00:04:05.280> it's<00:04:05.459> a<00:04:05.640> pool<00:04:05.760> something<00:04:06.060> to<00:04:06.299> that 00:04:06.470 --> 00:04:06.480 align:start position:0% curve or it's a pool something to that 00:04:06.480 --> 00:04:08.690 align:start position:0% curve or it's a pool something to that effect<00:04:06.680> so<00:04:07.680> what<00:04:07.860> you<00:04:07.980> do<00:04:08.159> is<00:04:08.340> instead<00:04:08.640> of 00:04:08.690 --> 00:04:08.700 align:start position:0% effect so what you do is instead of 00:04:08.700 --> 00:04:11.149 align:start position:0% effect so what you do is instead of giving<00:04:08.879> the<00:04:09.180> signature<00:04:09.780> for<00:04:10.260> 12.71<00:04:10.920> you 00:04:11.149 --> 00:04:11.159 align:start position:0% giving the signature for 12.71 you 00:04:11.159 --> 00:04:12.530 align:start position:0% giving the signature for 12.71 you actually<00:04:11.459> give 00:04:12.530 --> 00:04:12.540 align:start position:0% actually give 00:04:12.540 --> 00:04:16.250 align:start position:0% actually give the<00:04:13.260> order<00:04:13.439> itself<00:04:14.159> then 00:04:16.250 --> 00:04:16.260 align:start position:0% the order itself then 00:04:16.260 --> 00:04:19.430 align:start position:0% the order itself then and<00:04:16.799> this<00:04:17.100> there's<00:04:18.000> a<00:04:18.299> trick<00:04:18.720> you<00:04:18.840> can<00:04:18.959> do<00:04:19.139> here 00:04:19.430 --> 00:04:19.440 align:start position:0% and this there's a trick you can do here 00:04:19.440 --> 00:04:22.250 align:start position:0% and this there's a trick you can do here where<00:04:19.919> you<00:04:20.639> can<00:04:20.760> actually<00:04:21.000> Supply 00:04:22.250 --> 00:04:22.260 align:start position:0% where you can actually Supply 00:04:22.260 --> 00:04:25.629 align:start position:0% where you can actually Supply an<00:04:22.860> offset<00:04:23.220> to<00:04:23.759> call<00:04:23.940> data<00:04:24.419> that 00:04:25.629 --> 00:04:25.639 align:start position:0% an offset to call data that 00:04:25.639 --> 00:04:28.490 align:start position:0% an offset to call data that reuses<00:04:26.639> the<00:04:27.000> same<00:04:27.180> segment<00:04:27.600> of<00:04:27.780> call<00:04:28.020> data 00:04:28.490 --> 00:04:28.500 align:start position:0% reuses the same segment of call data 00:04:28.500 --> 00:04:31.310 align:start position:0% reuses the same segment of call data that<00:04:28.979> you<00:04:29.100> already<00:04:29.340> provided<00:04:29.880> with<00:04:30.300> the<00:04:30.479> order 00:04:31.310 --> 00:04:31.320 align:start position:0% that you already provided with the order 00:04:31.320 --> 00:04:33.830 align:start position:0% that you already provided with the order and<00:04:31.919> cut<00:04:32.160> down<00:04:32.400> on<00:04:32.699> the<00:04:33.000> overhead<00:04:33.300> of<00:04:33.660> doing 00:04:33.830 --> 00:04:33.840 align:start position:0% and cut down on the overhead of doing 00:04:33.840 --> 00:04:36.350 align:start position:0% and cut down on the overhead of doing this<00:04:34.020> but<00:04:34.320> then<00:04:34.440> what<00:04:34.740> the<00:04:35.520> offerer<00:04:36.180> that's 00:04:36.350 --> 00:04:36.360 align:start position:0% this but then what the offerer that's 00:04:36.360 --> 00:04:38.930 align:start position:0% this but then what the offerer that's getting<00:04:36.600> called<00:04:37.020> will<00:04:37.919> basically<00:04:38.340> have<00:04:38.520> to<00:04:38.699> do 00:04:38.930 --> 00:04:38.940 align:start position:0% getting called will basically have to do 00:04:38.940 --> 00:04:40.030 align:start position:0% getting called will basically have to do is 00:04:40.030 --> 00:04:40.040 align:start position:0% is 00:04:40.040 --> 00:04:43.610 align:start position:0% is rehash<00:04:41.040> the<00:04:41.340> order<00:04:41.540> derive<00:04:42.540> that<00:04:42.720> digest<00:04:43.199> and 00:04:43.610 --> 00:04:43.620 align:start position:0% rehash the order derive that digest and 00:04:43.620 --> 00:04:45.469 align:start position:0% rehash the order derive that digest and compare<00:04:43.919> it<00:04:44.100> to<00:04:44.280> the<00:04:44.400> one<00:04:44.580> that<00:04:44.880> was<00:04:45.060> supplied 00:04:45.469 --> 00:04:45.479 align:start position:0% compare it to the one that was supplied 00:04:45.479 --> 00:04:48.590 align:start position:0% compare it to the one that was supplied by<00:04:45.840> 1271<00:04:46.680> then<00:04:47.639> it<00:04:47.820> knows<00:04:48.120> that<00:04:48.240> the<00:04:48.479> order 00:04:48.590 --> 00:04:48.600 align:start position:0% by 1271 then it knows that the order 00:04:48.600 --> 00:04:51.770 align:start position:0% by 1271 then it knows that the order that<00:04:48.900> you<00:04:49.020> gave<00:04:49.199> is<00:04:49.500> the<00:04:49.800> signature<00:04:50.479> is<00:04:51.479> in 00:04:51.770 --> 00:04:51.780 align:start position:0% that you gave is the signature is in 00:04:51.780 --> 00:04:53.629 align:start position:0% that you gave is the signature is in fact<00:04:51.900> the<00:04:52.500> correct<00:04:52.740> order<00:04:52.919> that's<00:04:53.280> being 00:04:53.629 --> 00:04:53.639 align:start position:0% fact the correct order that's being 00:04:53.639 --> 00:04:55.510 align:start position:0% fact the correct order that's being filled<00:04:54.240> at<00:04:54.360> the<00:04:54.540> moment 00:04:55.510 --> 00:04:55.520 align:start position:0% filled at the moment 00:04:55.520 --> 00:04:58.249 align:start position:0% filled at the moment and<00:04:56.520> then<00:04:57.060> it<00:04:57.180> can<00:04:57.360> go<00:04:57.479> and<00:04:57.600> look<00:04:57.780> okay<00:04:58.020> let's 00:04:58.249 --> 00:04:58.259 align:start position:0% and then it can go and look okay let's 00:04:58.259 --> 00:05:00.170 align:start position:0% and then it can go and look okay let's check<00:04:58.500> out<00:04:58.740> this<00:04:59.160> offer<00:04:59.699> item<00:04:59.940> this 00:05:00.170 --> 00:05:00.180 align:start position:0% check out this offer item this 00:05:00.180 --> 00:05:03.110 align:start position:0% check out this offer item this consideration<00:05:00.720> item<00:05:01.160> and<00:05:02.160> make<00:05:02.639> sure<00:05:02.759> that 00:05:03.110 --> 00:05:03.120 align:start position:0% consideration item and make sure that 00:05:03.120 --> 00:05:06.050 align:start position:0% consideration item and make sure that they<00:05:03.479> match<00:05:03.960> whatever<00:05:04.320> the<00:05:04.740> the<00:05:04.919> latest 00:05:06.050 --> 00:05:06.060 align:start position:0% they match whatever the the latest 00:05:06.060 --> 00:05:08.629 align:start position:0% they match whatever the the latest state<00:05:06.479> that<00:05:06.780> we<00:05:06.900> expect<00:05:07.020> is 00:05:08.629 --> 00:05:08.639 align:start position:0% state that we expect is 00:05:08.639 --> 00:05:10.790 align:start position:0% state that we expect is so<00:05:09.360> that's<00:05:09.479> a<00:05:09.720> really<00:05:09.840> interesting<00:05:10.320> technique 00:05:10.790 --> 00:05:10.800 align:start position:0% so that's a really interesting technique 00:05:10.800 --> 00:05:13.850 align:start position:0% so that's a really interesting technique to<00:05:11.340> to<00:05:12.000> do<00:05:12.240> more<00:05:12.540> dynamic<00:05:13.080> or<00:05:13.259> you<00:05:13.620> got<00:05:13.740> a 00:05:13.850 --> 00:05:13.860 align:start position:0% to to do more dynamic or you got a 00:05:13.860 --> 00:05:16.310 align:start position:0% to to do more dynamic or you got a question 00:05:16.310 --> 00:05:16.320 align:start position:0% 00:05:16.320 --> 00:05:19.129 align:start position:0% so<00:05:16.680> this<00:05:16.800> is<00:05:16.979> not<00:05:17.160> zones<00:05:17.639> this<00:05:18.479> is<00:05:18.600> if<00:05:18.780> you<00:05:19.020> have 00:05:19.129 --> 00:05:19.139 align:start position:0% so this is not zones this is if you have 00:05:19.139 --> 00:05:22.550 align:start position:0% so this is not zones this is if you have a<00:05:19.500> contract<00:05:20.300> that<00:05:21.300> is<00:05:21.660> going<00:05:21.840> to<00:05:21.960> serve<00:05:22.259> as<00:05:22.320> an 00:05:22.550 --> 00:05:22.560 align:start position:0% a contract that is going to serve as an 00:05:22.560 --> 00:05:24.469 align:start position:0% a contract that is going to serve as an offer<00:05:22.919> and<00:05:23.520> so<00:05:23.699> it<00:05:23.820> could<00:05:23.940> have<00:05:24.120> its<00:05:24.419> own 00:05:24.469 --> 00:05:24.479 align:start position:0% offer and so it could have its own 00:05:24.479 --> 00:05:26.870 align:start position:0% offer and so it could have its own validation<00:05:24.960> Logic<00:05:25.440> on<00:05:25.919> the<00:05:26.039> contract<00:05:26.460> as<00:05:26.699> part 00:05:26.870 --> 00:05:26.880 align:start position:0% validation Logic on the contract as part 00:05:26.880 --> 00:05:29.210 align:start position:0% validation Logic on the contract as part of<00:05:27.060> this<00:05:27.240> but<00:05:27.780> it<00:05:27.900> could<00:05:28.020> also<00:05:28.259> utilize<00:05:28.740> a<00:05:28.919> zone 00:05:29.210 --> 00:05:29.220 align:start position:0% of this but it could also utilize a zone 00:05:29.220 --> 00:05:30.830 align:start position:0% of this but it could also utilize a zone right<00:05:29.699> that's 00:05:30.830 --> 00:05:30.840 align:start position:0% right that's 00:05:30.840 --> 00:05:33.409 align:start position:0% right that's very<00:05:31.440> much<00:05:31.620> a<00:05:31.860> something<00:05:32.220> that<00:05:32.520> it<00:05:32.699> could 00:05:33.409 --> 00:05:33.419 align:start position:0% very much a something that it could 00:05:33.419 --> 00:05:38.749 align:start position:0% very much a something that it could piggyback<00:05:34.199> on<00:05:35.039> validation<00:05:35.639> logic<00:05:36.000> in<00:05:36.120> his<00:05:36.300> own 00:05:38.749 --> 00:05:38.759 align:start position:0% 00:05:38.759 --> 00:05:40.010 align:start position:0% all<00:05:39.180> right 00:05:40.010 --> 00:05:40.020 align:start position:0% all right 00:05:40.020 --> 00:05:42.469 align:start position:0% all right so<00:05:40.380> that's<00:05:40.500> creating<00:05:40.919> orders 00:05:42.469 --> 00:05:42.479 align:start position:0% so that's creating orders 00:05:42.479 --> 00:05:44.749 align:start position:0% so that's creating orders let's<00:05:42.600> talk<00:05:42.840> about<00:05:42.960> fulfilling<00:05:43.560> them 00:05:44.749 --> 00:05:44.759 align:start position:0% let's talk about fulfilling them 00:05:44.759 --> 00:05:47.029 align:start position:0% let's talk about fulfilling them the<00:05:45.360> standard<00:05:45.720> method<00:05:46.080> for<00:05:46.380> fulfilling<00:05:46.860> an 00:05:47.029 --> 00:05:47.039 align:start position:0% the standard method for fulfilling an 00:05:47.039 --> 00:05:49.730 align:start position:0% the standard method for fulfilling an order<00:05:47.220> is<00:05:47.820> to<00:05:48.000> call<00:05:48.120> this<00:05:48.360> function<00:05:48.780> fulfill 00:05:49.730 --> 00:05:49.740 align:start position:0% order is to call this function fulfill 00:05:49.740 --> 00:05:51.350 align:start position:0% order is to call this function fulfill order 00:05:51.350 --> 00:05:51.360 align:start position:0% order 00:05:51.360 --> 00:05:54.230 align:start position:0% order and<00:05:52.080> or<00:05:52.380> fulfill<00:05:52.680> orders<00:05:53.100> is<00:05:53.759> the<00:05:53.940> actual 00:05:54.230 --> 00:05:54.240 align:start position:0% and or fulfill orders is the actual 00:05:54.240 --> 00:05:55.430 align:start position:0% and or fulfill orders is the actual function 00:05:55.430 --> 00:05:55.440 align:start position:0% function 00:05:55.440 --> 00:05:59.270 align:start position:0% function and<00:05:56.419> you<00:05:57.419> basically<00:05:57.840> just<00:05:58.139> give<00:05:58.500> this<00:05:59.160> whole 00:05:59.270 --> 00:05:59.280 align:start position:0% and you basically just give this whole 00:05:59.280 --> 00:06:01.189 align:start position:0% and you basically just give this whole payload<00:05:59.820> just<00:06:00.000> like<00:06:00.180> the<00:06:00.360> payload<00:06:00.840> that<00:06:01.080> you 00:06:01.189 --> 00:06:01.199 align:start position:0% payload just like the payload that you 00:06:01.199 --> 00:06:03.710 align:start position:0% payload just like the payload that you signed<00:06:01.620> you<00:06:02.039> provided<00:06:02.400> to<00:06:02.580> this<00:06:02.759> function 00:06:03.710 --> 00:06:03.720 align:start position:0% signed you provided to this function 00:06:03.720 --> 00:06:08.390 align:start position:0% signed you provided to this function and<00:06:04.560> it<00:06:04.919> creates<00:06:05.280> an<00:06:06.240> implied<00:06:06.780> second<00:06:07.380> order<00:06:07.860> a 00:06:08.390 --> 00:06:08.400 align:start position:0% and it creates an implied second order a 00:06:08.400 --> 00:06:11.150 align:start position:0% and it creates an implied second order a mirror<00:06:08.759> image<00:06:09.120> of<00:06:09.479> the<00:06:09.660> first<00:06:09.840> one<00:06:10.160> where 00:06:11.150 --> 00:06:11.160 align:start position:0% mirror image of the first one where 00:06:11.160 --> 00:06:14.390 align:start position:0% mirror image of the first one where every<00:06:11.699> item<00:06:12.479> that's<00:06:12.780> being<00:06:13.080> offered<00:06:13.800> on<00:06:14.280> the 00:06:14.390 --> 00:06:14.400 align:start position:0% every item that's being offered on the 00:06:14.400 --> 00:06:16.430 align:start position:0% every item that's being offered on the order<00:06:14.520> you're<00:06:14.759> fulfilling<00:06:15.180> you<00:06:15.419> just<00:06:15.600> say<00:06:15.780> all 00:06:16.430 --> 00:06:16.440 align:start position:0% order you're fulfilling you just say all 00:06:16.440 --> 00:06:19.490 align:start position:0% order you're fulfilling you just say all right<00:06:16.620> I<00:06:17.340> will<00:06:17.520> take<00:06:17.699> that<00:06:17.940> and<00:06:18.660> take<00:06:19.139> all<00:06:19.440> of 00:06:19.490 --> 00:06:19.500 align:start position:0% right I will take that and take all of 00:06:19.500 --> 00:06:21.110 align:start position:0% right I will take that and take all of those<00:06:19.680> items<00:06:19.979> those<00:06:20.220> are<00:06:20.340> your<00:06:20.520> consideration 00:06:21.110 --> 00:06:21.120 align:start position:0% those items those are your consideration 00:06:21.120 --> 00:06:23.150 align:start position:0% those items those are your consideration items<00:06:21.479> with<00:06:21.660> you<00:06:21.840> as<00:06:22.080> the<00:06:22.259> recipient<00:06:22.620> then 00:06:23.150 --> 00:06:23.160 align:start position:0% items with you as the recipient then 00:06:23.160 --> 00:06:25.370 align:start position:0% items with you as the recipient then look<00:06:24.000> at<00:06:24.120> all<00:06:24.300> those<00:06:24.419> consideration<00:06:24.960> items 00:06:25.370 --> 00:06:25.380 align:start position:0% look at all those consideration items 00:06:25.380 --> 00:06:29.029 align:start position:0% look at all those consideration items I'll<00:06:26.220> I'll<00:06:26.520> send<00:06:26.759> those<00:06:27.000> out<00:06:27.180> I'll<00:06:27.479> pay<00:06:27.660> them 00:06:29.029 --> 00:06:29.039 align:start position:0% I'll I'll send those out I'll pay them 00:06:29.039 --> 00:06:32.629 align:start position:0% I'll I'll send those out I'll pay them that's<00:06:29.639> the<00:06:29.940> the<00:06:30.180> basic<00:06:30.660> method 00:06:32.629 --> 00:06:32.639 align:start position:0% that's the the basic method 00:06:32.639 --> 00:06:36.050 align:start position:0% that's the the basic method but<00:06:33.180> there's<00:06:33.360> also<00:06:33.720> a<00:06:34.199> basic<00:06:34.740> method<00:06:35.220> which<00:06:35.880> is 00:06:36.050 --> 00:06:36.060 align:start position:0% but there's also a basic method which is 00:06:36.060 --> 00:06:40.909 align:start position:0% but there's also a basic method which is there's<00:06:36.660> a<00:06:36.960> small<00:06:37.259> subset<00:06:37.860> of<00:06:38.699> orders<00:06:39.120> that 00:06:40.909 --> 00:06:40.919 align:start position:0% there's a small subset of orders that 00:06:40.919 --> 00:06:44.330 align:start position:0% there's a small subset of orders that actually<00:06:41.580> constitute<00:06:42.300> a<00:06:42.660> pretty<00:06:43.259> wide<00:06:43.919> swath 00:06:44.330 --> 00:06:44.340 align:start position:0% actually constitute a pretty wide swath 00:06:44.340 --> 00:06:46.730 align:start position:0% actually constitute a pretty wide swath of<00:06:44.580> what<00:06:44.819> people<00:06:45.060> are<00:06:45.600> generally<00:06:45.960> doing<00:06:46.319> which 00:06:46.730 --> 00:06:46.740 align:start position:0% of what people are generally doing which 00:06:46.740 --> 00:06:49.370 align:start position:0% of what people are generally doing which is<00:06:46.919> I<00:06:47.639> want<00:06:47.759> to<00:06:47.940> buy<00:06:48.060> an<00:06:48.240> nft<00:06:48.479> I<00:06:49.080> want<00:06:49.139> to<00:06:49.259> sell 00:06:49.370 --> 00:06:49.380 align:start position:0% is I want to buy an nft I want to sell 00:06:49.380 --> 00:06:50.510 align:start position:0% is I want to buy an nft I want to sell an<00:06:49.620> nft 00:06:50.510 --> 00:06:50.520 align:start position:0% an nft 00:06:50.520 --> 00:06:53.930 align:start position:0% an nft and<00:06:51.240> maybe<00:06:51.680> pay<00:06:52.680> a<00:06:52.919> fee 00:06:53.930 --> 00:06:53.940 align:start position:0% and maybe pay a fee 00:06:53.940 --> 00:06:56.210 align:start position:0% and maybe pay a fee Port<00:06:54.479> doesn't<00:06:54.720> actually<00:06:54.900> have<00:06:55.139> a<00:06:55.319> notion<00:06:55.680> of 00:06:56.210 --> 00:06:56.220 align:start position:0% Port doesn't actually have a notion of 00:06:56.220 --> 00:06:59.450 align:start position:0% Port doesn't actually have a notion of fees<00:06:56.940> at<00:06:57.780> all<00:06:57.960> so<00:06:58.680> it's<00:06:58.800> everything<00:06:59.100> is<00:06:59.340> just 00:06:59.450 --> 00:06:59.460 align:start position:0% fees at all so it's everything is just 00:06:59.460 --> 00:07:02.629 align:start position:0% fees at all so it's everything is just another<00:06:59.699> item<00:07:00.120> but<00:07:00.720> if<00:07:01.680> you<00:07:02.039> have<00:07:02.220> one<00:07:02.520> of 00:07:02.629 --> 00:07:02.639 align:start position:0% another item but if you have one of 00:07:02.639 --> 00:07:05.990 align:start position:0% another item but if you have one of these<00:07:03.000> simple<00:07:03.720> subsets<00:07:04.440> you<00:07:05.220> got<00:07:05.460> a<00:07:05.639> single 00:07:05.990 --> 00:07:06.000 align:start position:0% these simple subsets you got a single 00:07:06.000 --> 00:07:07.249 align:start position:0% these simple subsets you got a single offer<00:07:06.360> item 00:07:07.249 --> 00:07:07.259 align:start position:0% offer item 00:07:07.259 --> 00:07:09.409 align:start position:0% offer item you've<00:07:07.800> got<00:07:07.979> one<00:07:08.580> or<00:07:08.759> more<00:07:08.880> consideration 00:07:09.409 --> 00:07:09.419 align:start position:0% you've got one or more consideration 00:07:09.419 --> 00:07:12.110 align:start position:0% you've got one or more consideration items<00:07:09.900> and<00:07:10.259> you<00:07:10.620> take<00:07:10.860> that<00:07:11.280> sum<00:07:11.580> total<00:07:11.819> of<00:07:11.940> all 00:07:12.110 --> 00:07:12.120 align:start position:0% items and you take that sum total of all 00:07:12.120 --> 00:07:14.029 align:start position:0% items and you take that sum total of all the<00:07:12.240> items<00:07:12.600> there's<00:07:12.900> one<00:07:13.139> nft 00:07:14.029 --> 00:07:14.039 align:start position:0% the items there's one nft 00:07:14.039 --> 00:07:17.150 align:start position:0% the items there's one nft that's<00:07:14.880> part<00:07:15.120> of<00:07:15.240> that<00:07:15.360> everything<00:07:16.080> else<00:07:16.380> is<00:07:16.800> a 00:07:17.150 --> 00:07:17.160 align:start position:0% that's part of that everything else is a 00:07:17.160 --> 00:07:18.290 align:start position:0% that's part of that everything else is a single 00:07:18.290 --> 00:07:18.300 align:start position:0% single 00:07:18.300 --> 00:07:21.890 align:start position:0% single item<00:07:19.020> type<00:07:19.259> it's<00:07:19.500> a<00:07:20.160> they're<00:07:20.639> all<00:07:21.000> Wes<00:07:21.479> or 00:07:21.890 --> 00:07:21.900 align:start position:0% item type it's a they're all Wes or 00:07:21.900 --> 00:07:24.249 align:start position:0% item type it's a they're all Wes or they're<00:07:22.080> all<00:07:22.380> die<00:07:22.919> or<00:07:23.460> something<00:07:23.639> like<00:07:24.000> that 00:07:24.249 --> 00:07:24.259 align:start position:0% they're all die or something like that 00:07:24.259 --> 00:07:26.510 align:start position:0% they're all die or something like that then<00:07:25.259> you<00:07:25.440> can<00:07:25.500> call<00:07:25.680> this<00:07:25.919> other<00:07:26.099> function 00:07:26.510 --> 00:07:26.520 align:start position:0% then you can call this other function 00:07:26.520 --> 00:07:29.350 align:start position:0% then you can call this other function and<00:07:27.259> performs<00:07:28.259> a<00:07:28.380> more<00:07:28.500> optimized 00:07:29.350 --> 00:07:29.360 align:start position:0% and performs a more optimized 00:07:29.360 --> 00:07:32.629 align:start position:0% and performs a more optimized fulfillment<00:07:30.360> less<00:07:31.259> call<00:07:31.500> data<00:07:31.979> you<00:07:32.340> just<00:07:32.460> need 00:07:32.629 --> 00:07:32.639 align:start position:0% fulfillment less call data you just need 00:07:32.639 --> 00:07:34.730 align:start position:0% fulfillment less call data you just need to<00:07:32.759> supply<00:07:33.300> a<00:07:33.599> subset 00:07:34.730 --> 00:07:34.740 align:start position:0% to supply a subset 00:07:34.740 --> 00:07:37.550 align:start position:0% to supply a subset like<00:07:35.280> give<00:07:35.699> all<00:07:35.940> the<00:07:36.180> additional<00:07:36.900> recipients 00:07:37.550 --> 00:07:37.560 align:start position:0% like give all the additional recipients 00:07:37.560 --> 00:07:39.650 align:start position:0% like give all the additional recipients which<00:07:37.860> spells<00:07:38.340> out 00:07:39.650 --> 00:07:39.660 align:start position:0% which spells out 00:07:39.660 --> 00:07:43.969 align:start position:0% which spells out um<00:07:39.720> usually<00:07:40.319> it's<00:07:40.560> used<00:07:40.740> for<00:07:40.979> fees<00:07:41.479> and<00:07:42.479> uh 00:07:43.969 --> 00:07:43.979 align:start position:0% um usually it's used for fees and uh 00:07:43.979 --> 00:07:46.670 align:start position:0% um usually it's used for fees and uh on<00:07:44.520> top<00:07:44.699> of<00:07:44.880> that<00:07:45.120> the<00:07:45.960> basic<00:07:46.259> fulfillment 00:07:46.670 --> 00:07:46.680 align:start position:0% on top of that the basic fulfillment 00:07:46.680 --> 00:07:50.270 align:start position:0% on top of that the basic fulfillment methods<00:07:47.160> have<00:07:47.580> a<00:07:48.000> slight<00:07:48.180> deviation<00:07:48.720> where<00:07:49.280> if 00:07:50.270 --> 00:07:50.280 align:start position:0% methods have a slight deviation where if 00:07:50.280 --> 00:07:55.490 align:start position:0% methods have a slight deviation where if the<00:07:50.759> offer<00:07:51.139> is<00:07:52.139> the<00:07:52.979> item<00:07:53.280> is<00:07:53.580> a<00:07:54.080> erc20<00:07:55.080> token 00:07:55.490 --> 00:07:55.500 align:start position:0% the offer is the item is a erc20 token 00:07:55.500 --> 00:07:59.870 align:start position:0% the offer is the item is a erc20 token or<00:07:56.220> native<00:07:56.580> token<00:07:57.479> then<00:07:58.020> it<00:07:58.199> will<00:07:58.380> be<00:07:58.620> used<00:07:58.919> to 00:07:59.870 --> 00:07:59.880 align:start position:0% or native token then it will be used to 00:07:59.880 --> 00:08:03.830 align:start position:0% or native token then it will be used to pay<00:08:00.120> for<00:08:00.860> all<00:08:01.860> the<00:08:02.099> non-nft<00:08:02.940> consideration 00:08:03.830 --> 00:08:03.840 align:start position:0% pay for all the non-nft consideration 00:08:03.840 --> 00:08:05.029 align:start position:0% pay for all the non-nft consideration items<00:08:04.199> so<00:08:04.319> you<00:08:04.440> don't<00:08:04.560> have<00:08:04.680> to<00:08:04.800> take 00:08:05.029 --> 00:08:05.039 align:start position:0% items so you don't have to take 00:08:05.039 --> 00:08:07.010 align:start position:0% items so you don't have to take everything<00:08:05.400> you<00:08:06.180> can<00:08:06.240> minimize<00:08:06.660> the<00:08:06.900> number 00:08:07.010 --> 00:08:07.020 align:start position:0% everything you can minimize the number 00:08:07.020 --> 00:08:09.110 align:start position:0% everything you can minimize the number of<00:08:07.139> transcripts<00:08:07.800> that<00:08:07.979> are<00:08:08.099> occurring 00:08:09.110 --> 00:08:09.120 align:start position:0% of transcripts that are occurring 00:08:09.120 --> 00:08:12.050 align:start position:0% of transcripts that are occurring that's<00:08:09.599> a<00:08:09.780> common<00:08:09.960> theme<00:08:10.319> with<00:08:11.039> uh<00:08:11.400> you'll<00:08:11.880> see 00:08:12.050 --> 00:08:12.060 align:start position:0% that's a common theme with uh you'll see 00:08:12.060 --> 00:08:14.930 align:start position:0% that's a common theme with uh you'll see uh<00:08:12.900> as<00:08:13.199> we<00:08:13.440> get<00:08:13.560> into<00:08:13.680> these<00:08:14.099> subsequent 00:08:14.930 --> 00:08:14.940 align:start position:0% uh as we get into these subsequent 00:08:14.940 --> 00:08:16.670 align:start position:0% uh as we get into these subsequent fulfillment<00:08:15.419> methods 00:08:16.670 --> 00:08:16.680 align:start position:0% fulfillment methods 00:08:16.680 --> 00:08:20.689 align:start position:0% fulfillment methods it's<00:08:16.979> all<00:08:17.220> about<00:08:17.340> cutting<00:08:18.000> down<00:08:18.180> on<00:08:18.720> the<00:08:19.440> top 00:08:20.689 --> 00:08:20.699 align:start position:0% it's all about cutting down on the top 00:08:20.699 --> 00:08:23.450 align:start position:0% it's all about cutting down on the top efficiency<00:08:21.419> gain<00:08:21.780> is<00:08:22.080> from<00:08:22.440> reducing<00:08:23.220> the 00:08:23.450 --> 00:08:23.460 align:start position:0% efficiency gain is from reducing the 00:08:23.460 --> 00:08:26.150 align:start position:0% efficiency gain is from reducing the number<00:08:23.639> of<00:08:24.000> transfers<00:08:24.599> right 00:08:26.150 --> 00:08:26.160 align:start position:0% number of transfers right 00:08:26.160 --> 00:08:28.490 align:start position:0% number of transfers right particularly<00:08:26.819> with<00:08:27.000> tokens 00:08:28.490 --> 00:08:28.500 align:start position:0% particularly with tokens 00:08:28.500 --> 00:08:30.350 align:start position:0% particularly with tokens native<00:08:29.099> tokens<00:08:29.460> a<00:08:29.699> little<00:08:29.759> different<00:08:29.879> but 00:08:30.350 --> 00:08:30.360 align:start position:0% native tokens a little different but 00:08:30.360 --> 00:08:32.570 align:start position:0% native tokens a little different but with<00:08:30.720> other<00:08:30.960> tokens<00:08:31.379> it<00:08:31.680> gets<00:08:31.919> very<00:08:32.099> expensive 00:08:32.570 --> 00:08:32.580 align:start position:0% with other tokens it gets very expensive 00:08:32.580 --> 00:08:35.269 align:start position:0% with other tokens it gets very expensive if<00:08:32.820> you're<00:08:32.940> doing<00:08:33.120> redundant<00:08:33.719> transfers 00:08:35.269 --> 00:08:35.279 align:start position:0% if you're doing redundant transfers 00:08:35.279 --> 00:08:37.250 align:start position:0% if you're doing redundant transfers so<00:08:35.700> when<00:08:35.880> you<00:08:36.060> want<00:08:36.240> to<00:08:36.419> buy 00:08:37.250 --> 00:08:37.260 align:start position:0% so when you want to buy 00:08:37.260 --> 00:08:39.350 align:start position:0% so when you want to buy five<00:08:37.680> nfts<00:08:38.339> you<00:08:38.520> want<00:08:38.640> to<00:08:38.760> sweep<00:08:39.000> the<00:08:39.180> floor 00:08:39.350 --> 00:08:39.360 align:start position:0% five nfts you want to sweep the floor 00:08:39.360 --> 00:08:41.409 align:start position:0% five nfts you want to sweep the floor right 00:08:41.409 --> 00:08:41.419 align:start position:0% right 00:08:41.419 --> 00:08:45.590 align:start position:0% right oftentimes<00:08:42.419> you'll<00:08:43.080> have<00:08:43.380> each<00:08:44.219> one<00:08:44.399> of<00:08:44.580> those 00:08:45.590 --> 00:08:45.600 align:start position:0% oftentimes you'll have each one of those 00:08:45.600 --> 00:08:47.930 align:start position:0% oftentimes you'll have each one of those has<00:08:46.200> a<00:08:46.440> fee<00:08:46.620> attached 00:08:47.930 --> 00:08:47.940 align:start position:0% has a fee attached 00:08:47.940 --> 00:08:50.630 align:start position:0% has a fee attached what<00:08:48.360> if<00:08:48.540> those<00:08:48.839> that<00:08:49.140> fee<00:08:49.440> recipient<00:08:49.860> is<00:08:50.339> the 00:08:50.630 --> 00:08:50.640 align:start position:0% what if those that fee recipient is the 00:08:50.640 --> 00:08:52.430 align:start position:0% what if those that fee recipient is the same<00:08:50.940> recipient 00:08:52.430 --> 00:08:52.440 align:start position:0% same recipient 00:08:52.440 --> 00:08:54.650 align:start position:0% same recipient you<00:08:52.800> don't<00:08:52.920> want<00:08:53.040> to<00:08:53.160> do<00:08:53.339> five<00:08:53.820> transfers<00:08:54.360> you 00:08:54.650 --> 00:08:54.660 align:start position:0% you don't want to do five transfers you 00:08:54.660 --> 00:08:57.590 align:start position:0% you don't want to do five transfers you want<00:08:54.720> to<00:08:54.839> do<00:08:54.959> one<00:08:55.260> so<00:08:56.160> we<00:08:56.339> use<00:08:56.640> this<00:08:57.180> fulfill 00:08:57.590 --> 00:08:57.600 align:start position:0% want to do one so we use this fulfill 00:08:57.600 --> 00:09:00.889 align:start position:0% want to do one so we use this fulfill available<00:08:58.080> orders<00:08:58.800> method<00:08:59.880> this<00:09:00.540> basically 00:09:00.889 --> 00:09:00.899 align:start position:0% available orders method this basically 00:09:00.899 --> 00:09:03.230 align:start position:0% available orders method this basically goes<00:09:01.380> through<00:09:01.500> each<00:09:01.800> order<00:09:01.980> and<00:09:02.279> says 00:09:03.230 --> 00:09:03.240 align:start position:0% goes through each order and says 00:09:03.240 --> 00:09:05.750 align:start position:0% goes through each order and says has<00:09:03.779> this<00:09:04.019> been<00:09:04.320> fulfilled<00:09:05.100> has<00:09:05.459> it<00:09:05.640> been 00:09:05.750 --> 00:09:05.760 align:start position:0% has this been fulfilled has it been 00:09:05.760 --> 00:09:09.530 align:start position:0% has this been fulfilled has it been canceled<00:09:06.120> if<00:09:07.019> it's<00:09:07.260> still<00:09:07.440> valid<00:09:07.920> then<00:09:08.820> we'll 00:09:09.530 --> 00:09:09.540 align:start position:0% canceled if it's still valid then we'll 00:09:09.540 --> 00:09:12.170 align:start position:0% canceled if it's still valid then we'll go<00:09:09.720> for<00:09:09.959> it<00:09:10.140> if<00:09:11.040> the<00:09:11.160> order<00:09:11.339> is<00:09:11.640> not<00:09:11.880> valid 00:09:12.170 --> 00:09:12.180 align:start position:0% go for it if the order is not valid 00:09:12.180 --> 00:09:13.550 align:start position:0% go for it if the order is not valid anymore<00:09:12.300> we'll<00:09:12.600> skip<00:09:12.839> it 00:09:13.550 --> 00:09:13.560 align:start position:0% anymore we'll skip it 00:09:13.560 --> 00:09:17.329 align:start position:0% anymore we'll skip it and<00:09:14.160> you<00:09:14.399> supply<00:09:15.200> the<00:09:16.200> you<00:09:16.680> basically<00:09:17.040> point 00:09:17.329 --> 00:09:17.339 align:start position:0% and you supply the you basically point 00:09:17.339 --> 00:09:19.730 align:start position:0% and you supply the you basically point to<00:09:17.580> okay<00:09:17.820> this<00:09:18.779> order 00:09:19.730 --> 00:09:19.740 align:start position:0% to okay this order 00:09:19.740 --> 00:09:23.389 align:start position:0% to okay this order this<00:09:20.339> item<00:09:20.700> that<00:09:21.540> order<00:09:21.779> that<00:09:22.380> item<00:09:22.680> these<00:09:23.220> all 00:09:23.389 --> 00:09:23.399 align:start position:0% this item that order that item these all 00:09:23.399 --> 00:09:27.050 align:start position:0% this item that order that item these all have<00:09:23.700> the<00:09:24.180> exact<00:09:24.540> same<00:09:24.980> item<00:09:25.980> type<00:09:26.160> they<00:09:26.880> all 00:09:27.050 --> 00:09:27.060 align:start position:0% have the exact same item type they all 00:09:27.060 --> 00:09:28.269 align:start position:0% have the exact same item type they all have<00:09:27.180> the<00:09:27.480> same 00:09:28.269 --> 00:09:28.279 align:start position:0% have the same 00:09:28.279 --> 00:09:33.050 align:start position:0% have the same uh<00:09:29.279> ID<00:09:30.000> if<00:09:30.540> you're<00:09:30.660> talking<00:09:30.839> about<00:09:31.019> 1155<00:09:31.920> token 00:09:33.050 --> 00:09:33.060 align:start position:0% uh ID if you're talking about 1155 token 00:09:33.060 --> 00:09:34.990 align:start position:0% uh ID if you're talking about 1155 token they<00:09:33.540> all<00:09:33.720> have<00:09:33.839> the<00:09:34.019> same<00:09:34.140> recipient 00:09:34.990 --> 00:09:35.000 align:start position:0% they all have the same recipient 00:09:35.000 --> 00:09:37.610 align:start position:0% they all have the same recipient effectively<00:09:36.000> they<00:09:36.360> can<00:09:36.480> be<00:09:36.660> condensed<00:09:37.140> into<00:09:37.380> a 00:09:37.610 --> 00:09:37.620 align:start position:0% effectively they can be condensed into a 00:09:37.620 --> 00:09:38.870 align:start position:0% effectively they can be condensed into a single<00:09:37.920> transfer 00:09:38.870 --> 00:09:38.880 align:start position:0% single transfer 00:09:38.880 --> 00:09:42.410 align:start position:0% single transfer cuts<00:09:39.540> down<00:09:39.660> a<00:09:40.080> lot<00:09:40.200> on<00:09:40.980> uh<00:09:41.940> the<00:09:42.120> number<00:09:42.240> of 00:09:42.410 --> 00:09:42.420 align:start position:0% cuts down a lot on uh the number of 00:09:42.420 --> 00:09:45.410 align:start position:0% cuts down a lot on uh the number of transfers<00:09:42.839> there 00:09:45.410 --> 00:09:45.420 align:start position:0% 00:09:45.420 --> 00:09:50.090 align:start position:0% then<00:09:45.959> you<00:09:46.680> have<00:09:46.860> this<00:09:47.220> method<00:09:47.600> match<00:09:48.600> orders 00:09:50.090 --> 00:09:50.100 align:start position:0% then you have this method match orders 00:09:50.100 --> 00:09:51.949 align:start position:0% then you have this method match orders when<00:09:50.459> you're<00:09:50.640> talking<00:09:50.880> about 00:09:51.949 --> 00:09:51.959 align:start position:0% when you're talking about 00:09:51.959 --> 00:09:55.730 align:start position:0% when you're talking about fulfill<00:09:52.620> orders<00:09:53.160> fulfill<00:09:53.700> available<00:09:54.060> orders 00:09:55.730 --> 00:09:55.740 align:start position:0% fulfill orders fulfill available orders 00:09:55.740 --> 00:09:57.290 align:start position:0% fulfill orders fulfill available orders seaport's<00:09:56.459> not<00:09:56.580> going<00:09:56.700> to<00:09:56.760> be<00:09:56.880> able<00:09:57.000> to<00:09:57.120> figure 00:09:57.290 --> 00:09:57.300 align:start position:0% seaport's not going to be able to figure 00:09:57.300 --> 00:10:00.110 align:start position:0% seaport's not going to be able to figure out<00:09:57.540> on<00:09:57.779> its<00:09:58.080> own<00:09:58.200> how<00:09:59.160> to<00:09:59.279> do<00:09:59.399> these<00:09:59.700> transfers 00:10:00.110 --> 00:10:00.120 align:start position:0% out on its own how to do these transfers 00:10:00.120 --> 00:10:02.930 align:start position:0% out on its own how to do these transfers the<00:10:00.839> way<00:10:00.959> that<00:10:01.080> it<00:10:01.260> works<00:10:01.680> is<00:10:02.459> you're<00:10:02.640> going<00:10:02.820> to 00:10:02.930 --> 00:10:02.940 align:start position:0% the way that it works is you're going to 00:10:02.940 --> 00:10:04.610 align:start position:0% the way that it works is you're going to walk<00:10:03.180> through<00:10:03.420> every<00:10:03.839> single<00:10:04.140> fulfillment 00:10:04.610 --> 00:10:04.620 align:start position:0% walk through every single fulfillment 00:10:04.620 --> 00:10:07.070 align:start position:0% walk through every single fulfillment and<00:10:04.920> it's<00:10:05.100> the<00:10:05.339> same<00:10:05.459> idea<00:10:05.940> as<00:10:06.720> fulfill 00:10:07.070 --> 00:10:07.080 align:start position:0% and it's the same idea as fulfill 00:10:07.080 --> 00:10:10.190 align:start position:0% and it's the same idea as fulfill available<00:10:07.440> orders<00:10:08.120> here's<00:10:09.120> the<00:10:09.300> order<00:10:09.480> here's 00:10:10.190 --> 00:10:10.200 align:start position:0% available orders here's the order here's 00:10:10.200 --> 00:10:12.590 align:start position:0% available orders here's the order here's an<00:10:10.380> item<00:10:10.680> here's<00:10:11.519> another<00:10:11.700> item<00:10:12.180> here's 00:10:12.590 --> 00:10:12.600 align:start position:0% an item here's another item here's 00:10:12.600 --> 00:10:16.250 align:start position:0% an item here's another item here's another<00:10:12.720> item<00:10:13.200> let's<00:10:13.920> let's<00:10:15.019> aggregate<00:10:16.019> all 00:10:16.250 --> 00:10:16.260 align:start position:0% another item let's let's aggregate all 00:10:16.260 --> 00:10:17.690 align:start position:0% another item let's let's aggregate all these<00:10:16.440> together 00:10:17.690 --> 00:10:17.700 align:start position:0% these together 00:10:17.700 --> 00:10:19.430 align:start position:0% these together then 00:10:19.430 --> 00:10:19.440 align:start position:0% then 00:10:19.440 --> 00:10:21.410 align:start position:0% then we're<00:10:19.860> going<00:10:19.980> to<00:10:20.040> match<00:10:20.220> those<00:10:20.519> with<00:10:20.940> this 00:10:21.410 --> 00:10:21.420 align:start position:0% we're going to match those with this 00:10:21.420 --> 00:10:24.190 align:start position:0% we're going to match those with this item<00:10:21.720> this<00:10:22.019> item<00:10:22.320> this<00:10:22.620> item<00:10:22.920> on<00:10:23.580> these<00:10:23.820> orders 00:10:24.190 --> 00:10:24.200 align:start position:0% item this item this item on these orders 00:10:24.200 --> 00:10:27.769 align:start position:0% item this item this item on these orders on<00:10:25.200> the<00:10:25.320> consideration<00:10:25.800> side<00:10:26.160> then<00:10:27.120> that 00:10:27.769 --> 00:10:27.779 align:start position:0% on the consideration side then that 00:10:27.779 --> 00:10:30.710 align:start position:0% on the consideration side then that whole<00:10:28.200> group<00:10:28.640> gets<00:10:29.640> distilled<00:10:30.000> down<00:10:30.120> into<00:10:30.420> a 00:10:30.710 --> 00:10:30.720 align:start position:0% whole group gets distilled down into a 00:10:30.720 --> 00:10:34.550 align:start position:0% whole group gets distilled down into a single<00:10:30.959> transfer<00:10:31.860> so<00:10:32.459> this<00:10:32.760> method<00:10:33.180> is<00:10:33.660> it's 00:10:34.550 --> 00:10:34.560 align:start position:0% single transfer so this method is it's 00:10:34.560 --> 00:10:37.130 align:start position:0% single transfer so this method is it's not<00:10:34.860> utilized<00:10:35.519> as<00:10:35.700> often<00:10:36.120> if<00:10:36.779> you<00:10:36.839> just<00:10:37.019> want 00:10:37.130 --> 00:10:37.140 align:start position:0% not utilized as often if you just want 00:10:37.140 --> 00:10:38.810 align:start position:0% not utilized as often if you just want to<00:10:37.260> buy<00:10:37.380> an<00:10:37.560> nft 00:10:38.810 --> 00:10:38.820 align:start position:0% to buy an nft 00:10:38.820 --> 00:10:41.329 align:start position:0% to buy an nft this<00:10:39.420> is<00:10:39.540> what<00:10:39.899> you<00:10:40.440> really<00:10:40.620> want<00:10:40.860> to<00:10:40.980> reach 00:10:41.329 --> 00:10:41.339 align:start position:0% this is what you really want to reach 00:10:41.339 --> 00:10:45.530 align:start position:0% this is what you really want to reach for<00:10:41.600> in<00:10:42.600> the<00:10:42.839> power<00:10:43.200> use<00:10:43.920> cases<00:10:44.339> where<00:10:45.300> you 00:10:45.530 --> 00:10:45.540 align:start position:0% for in the power use cases where you 00:10:45.540 --> 00:10:48.110 align:start position:0% for in the power use cases where you have<00:10:45.839> your<00:10:46.680> maybe<00:10:46.920> you're<00:10:47.399> searching<00:10:47.880> like 00:10:48.110 --> 00:10:48.120 align:start position:0% have your maybe you're searching like 00:10:48.120 --> 00:10:50.769 align:start position:0% have your maybe you're searching like you're<00:10:48.420> looking<00:10:48.600> for<00:10:48.839> Mev<00:10:49.380> where<00:10:50.160> you<00:10:50.399> can 00:10:50.769 --> 00:10:50.779 align:start position:0% you're looking for Mev where you can 00:10:50.779 --> 00:10:55.250 align:start position:0% you're looking for Mev where you can find<00:10:51.779> a<00:10:52.260> price<00:10:52.920> mismatch<00:10:53.459> or<00:10:54.180> you<00:10:54.959> want<00:10:55.079> to 00:10:55.250 --> 00:10:55.260 align:start position:0% find a price mismatch or you want to 00:10:55.260 --> 00:10:58.670 align:start position:0% find a price mismatch or you want to compose<00:10:55.880> multiple<00:10:56.880> different<00:10:57.180> orders<00:10:57.720> with 00:10:58.670 --> 00:10:58.680 align:start position:0% compose multiple different orders with 00:10:58.680 --> 00:11:01.250 align:start position:0% compose multiple different orders with zones<00:10:59.100> and 00:11:01.250 --> 00:11:01.260 align:start position:0% zones and 00:11:01.260 --> 00:11:03.829 align:start position:0% zones and um get<00:11:01.920> them<00:11:02.100> all<00:11:02.339> to<00:11:02.459> all<00:11:02.760> fit<00:11:03.300> together<00:11:03.480> in<00:11:03.720> a 00:11:03.829 --> 00:11:03.839 align:start position:0% um get them all to all fit together in a 00:11:03.839 --> 00:11:05.389 align:start position:0% um get them all to all fit together in a neat<00:11:04.019> little<00:11:04.140> puzzle<00:11:04.560> piece 00:11:05.389 --> 00:11:05.399 align:start position:0% neat little puzzle piece 00:11:05.399 --> 00:11:07.610 align:start position:0% neat little puzzle piece big<00:11:06.120> big<00:11:06.420> thing<00:11:06.660> to<00:11:06.779> be<00:11:06.839> aware<00:11:07.019> of<00:11:07.200> with<00:11:07.380> this 00:11:07.610 --> 00:11:07.620 align:start position:0% big big thing to be aware of with this 00:11:07.620 --> 00:11:09.710 align:start position:0% big big thing to be aware of with this is<00:11:07.920> that<00:11:08.040> if<00:11:08.220> there's<00:11:08.459> a<00:11:08.700> problem 00:11:09.710 --> 00:11:09.720 align:start position:0% is that if there's a problem 00:11:09.720 --> 00:11:12.050 align:start position:0% is that if there's a problem after<00:11:10.200> you<00:11:10.500> supply<00:11:10.800> all<00:11:11.160> these<00:11:11.399> fulfillments 00:11:12.050 --> 00:11:12.060 align:start position:0% after you supply all these fulfillments 00:11:12.060 --> 00:11:13.610 align:start position:0% after you supply all these fulfillments it's<00:11:12.180> going<00:11:12.360> to<00:11:12.360> go<00:11:12.600> through<00:11:12.779> and<00:11:13.140> make<00:11:13.440> sure 00:11:13.610 --> 00:11:13.620 align:start position:0% it's going to go through and make sure 00:11:13.620 --> 00:11:17.030 align:start position:0% it's going to go through and make sure that<00:11:14.100> every<00:11:14.760> single<00:11:15.240> consideration<00:11:15.959> item<00:11:16.440> on 00:11:17.030 --> 00:11:17.040 align:start position:0% that every single consideration item on 00:11:17.040 --> 00:11:18.889 align:start position:0% that every single consideration item on every<00:11:17.220> single<00:11:17.579> order<00:11:17.760> has<00:11:18.420> been<00:11:18.600> fully 00:11:18.889 --> 00:11:18.899 align:start position:0% every single order has been fully 00:11:18.899 --> 00:11:21.769 align:start position:0% every single order has been fully credited<00:11:19.320> it's<00:11:19.560> got<00:11:19.800> to<00:11:19.920> be<00:11:20.040> zero<00:11:21.000> on<00:11:21.540> every 00:11:21.769 --> 00:11:21.779 align:start position:0% credited it's got to be zero on every 00:11:21.779 --> 00:11:24.350 align:start position:0% credited it's got to be zero on every single<00:11:22.079> one<00:11:22.320> or<00:11:23.279> else 00:11:24.350 --> 00:11:24.360 align:start position:0% single one or else 00:11:24.360 --> 00:11:27.889 align:start position:0% single one or else the<00:11:25.200> the<00:11:25.200> whole<00:11:25.980> batch<00:11:26.399> will<00:11:27.180> come<00:11:27.540> crashing 00:11:27.889 --> 00:11:27.899 align:start position:0% the the whole batch will come crashing 00:11:27.899 --> 00:11:29.449 align:start position:0% the the whole batch will come crashing down<00:11:28.079> it'll<00:11:28.440> revert 00:11:29.449 --> 00:11:29.459 align:start position:0% down it'll revert 00:11:29.459 --> 00:11:30.829 align:start position:0% down it'll revert so 00:11:30.829 --> 00:11:30.839 align:start position:0% so 00:11:30.839 --> 00:11:32.690 align:start position:0% so definitely<00:11:31.500> this<00:11:31.860> is<00:11:31.980> this<00:11:32.279> is<00:11:32.399> the<00:11:32.579> power 00:11:32.690 --> 00:11:32.700 align:start position:0% definitely this is this is the power 00:11:32.700 --> 00:11:37.069 align:start position:0% definitely this is this is the power feature<00:11:33.300> and<00:11:34.519> uh<00:11:35.540> the<00:11:36.540> first<00:11:36.600> thing<00:11:36.779> you<00:11:36.959> want 00:11:37.069 --> 00:11:37.079 align:start position:0% feature and uh the first thing you want 00:11:37.079 --> 00:11:39.670 align:start position:0% feature and uh the first thing you want to<00:11:37.200> reach<00:11:37.440> for<00:11:37.620> if<00:11:38.339> you're<00:11:38.880> looking<00:11:39.120> for 00:11:39.670 --> 00:11:39.680 align:start position:0% to reach for if you're looking for 00:11:39.680 --> 00:11:41.810 align:start position:0% to reach for if you're looking for searching<00:11:40.680> or 00:11:41.810 --> 00:11:41.820 align:start position:0% searching or 00:11:41.820 --> 00:11:42.410 align:start position:0% searching or um 00:11:42.410 --> 00:11:42.420 align:start position:0% um 00:11:42.420 --> 00:11:44.870 align:start position:0% um or<00:11:42.899> more<00:11:43.200> advanced<00:11:43.620> strategies 00:11:44.870 --> 00:11:44.880 align:start position:0% or more advanced strategies 00:11:44.880 --> 00:11:47.569 align:start position:0% or more advanced strategies okay<00:11:45.420> let's<00:11:45.839> talk<00:11:46.019> about<00:11:46.200> some<00:11:46.500> zones<00:11:46.860> zones 00:11:47.569 --> 00:11:47.579 align:start position:0% okay let's talk about some zones zones 00:11:47.579 --> 00:11:48.530 align:start position:0% okay let's talk about some zones zones is 00:11:48.530 --> 00:11:48.540 align:start position:0% is 00:11:48.540 --> 00:11:52.370 align:start position:0% is the<00:11:49.200> it's<00:11:49.620> the<00:11:50.160> main<00:11:50.579> mechanic<00:11:51.360> by<00:11:51.720> which<00:11:51.959> you 00:11:52.370 --> 00:11:52.380 align:start position:0% the it's the main mechanic by which you 00:11:52.380 --> 00:11:55.250 align:start position:0% the it's the main mechanic by which you would<00:11:52.560> extend<00:11:53.279> Seaport 00:11:55.250 --> 00:11:55.260 align:start position:0% would extend Seaport 00:11:55.260 --> 00:11:58.009 align:start position:0% would extend Seaport any<00:11:55.800> order<00:11:56.040> can<00:11:56.579> choose<00:11:57.060> its<00:11:57.300> own<00:11:57.360> Zone<00:11:57.720> and 00:11:58.009 --> 00:11:58.019 align:start position:0% any order can choose its own Zone and 00:11:58.019 --> 00:11:59.210 align:start position:0% any order can choose its own Zone and then<00:11:58.200> say 00:11:59.210 --> 00:11:59.220 align:start position:0% then say 00:11:59.220 --> 00:12:01.610 align:start position:0% then say I'm<00:11:59.700> a<00:11:59.940> restricted<00:12:00.420> order<00:12:00.660> except<00:12:01.140> the<00:12:01.500> type 00:12:01.610 --> 00:12:01.620 align:start position:0% I'm a restricted order except the type 00:12:01.620 --> 00:12:03.590 align:start position:0% I'm a restricted order except the type is<00:12:01.860> restricted<00:12:02.339> now<00:12:02.579> the<00:12:02.880> Zone<00:12:03.120> gets<00:12:03.480> to 00:12:03.590 --> 00:12:03.600 align:start position:0% is restricted now the Zone gets to 00:12:03.600 --> 00:12:06.829 align:start position:0% is restricted now the Zone gets to decide<00:12:04.079> whether<00:12:05.040> or<00:12:05.220> not<00:12:05.279> the<00:12:05.640> orders<00:12:06.000> good<00:12:06.660> or 00:12:06.829 --> 00:12:06.839 align:start position:0% decide whether or not the orders good or 00:12:06.839 --> 00:12:07.670 align:start position:0% decide whether or not the orders good or bad 00:12:07.670 --> 00:12:07.680 align:start position:0% bad 00:12:07.680 --> 00:12:09.230 align:start position:0% bad and 00:12:09.230 --> 00:12:09.240 align:start position:0% and 00:12:09.240 --> 00:12:13.490 align:start position:0% and in<00:12:09.779> addition<00:12:10.079> you<00:12:11.040> can<00:12:11.160> always<00:12:11.519> extend<00:12:12.500> the 00:12:13.490 --> 00:12:13.500 align:start position:0% in addition you can always extend the 00:12:13.500 --> 00:12:15.590 align:start position:0% in addition you can always extend the consideration<00:12:14.040> array<00:12:14.399> you<00:12:14.579> can<00:12:14.700> always<00:12:14.880> add 00:12:15.590 --> 00:12:15.600 align:start position:0% consideration array you can always add 00:12:15.600 --> 00:12:18.710 align:start position:0% consideration array you can always add items<00:12:16.260> as<00:12:16.860> the<00:12:17.579> fulfiller 00:12:18.710 --> 00:12:18.720 align:start position:0% items as the fulfiller 00:12:18.720 --> 00:12:21.769 align:start position:0% items as the fulfiller we<00:12:19.260> call<00:12:19.440> them<00:12:19.620> tips<00:12:20.180> this<00:12:21.180> is<00:12:21.300> it's<00:12:21.540> cool 00:12:21.769 --> 00:12:21.779 align:start position:0% we call them tips this is it's cool 00:12:21.779 --> 00:12:23.449 align:start position:0% we call them tips this is it's cool because<00:12:21.959> you<00:12:22.320> can<00:12:22.380> take<00:12:22.560> an<00:12:22.740> order<00:12:22.920> that<00:12:23.220> came 00:12:23.449 --> 00:12:23.459 align:start position:0% because you can take an order that came 00:12:23.459 --> 00:12:25.490 align:start position:0% because you can take an order that came from<00:12:23.760> One<00:12:24.120> Marketplace 00:12:25.490 --> 00:12:25.500 align:start position:0% from One Marketplace 00:12:25.500 --> 00:12:28.069 align:start position:0% from One Marketplace you<00:12:25.980> can<00:12:26.040> fulfill<00:12:26.459> it<00:12:26.579> on<00:12:26.760> another<00:12:26.940> and<00:12:27.720> apply 00:12:28.069 --> 00:12:28.079 align:start position:0% you can fulfill it on another and apply 00:12:28.079 --> 00:12:30.170 align:start position:0% you can fulfill it on another and apply a<00:12:28.200> tip<00:12:28.440> what<00:12:29.040> you<00:12:29.160> can<00:12:29.220> also<00:12:29.459> do<00:12:29.579> is<00:12:29.760> you<00:12:30.060> can 00:12:30.170 --> 00:12:30.180 align:start position:0% a tip what you can also do is you can 00:12:30.180 --> 00:12:33.650 align:start position:0% a tip what you can also do is you can use<00:12:30.779> logic<00:12:31.260> in<00:12:31.500> the<00:12:31.620> zones<00:12:32.000> to<00:12:33.000> ensure<00:12:33.360> that 00:12:33.650 --> 00:12:33.660 align:start position:0% use logic in the zones to ensure that 00:12:33.660 --> 00:12:36.410 align:start position:0% use logic in the zones to ensure that the<00:12:33.959> tip<00:12:34.200> that<00:12:34.800> got<00:12:35.040> supplied 00:12:36.410 --> 00:12:36.420 align:start position:0% the tip that got supplied 00:12:36.420 --> 00:12:39.410 align:start position:0% the tip that got supplied matches<00:12:37.140> whatever<00:12:37.440> it<00:12:37.920> is<00:12:38.040> that<00:12:38.579> that<00:12:39.120> you 00:12:39.410 --> 00:12:39.420 align:start position:0% matches whatever it is that that you 00:12:39.420 --> 00:12:42.949 align:start position:0% matches whatever it is that that you expect<00:12:39.600> it<00:12:39.899> to<00:12:40.140> maybe<00:12:40.640> that's<00:12:41.640> a<00:12:42.240> dynamic 00:12:42.949 --> 00:12:42.959 align:start position:0% expect it to maybe that's a dynamic 00:12:42.959 --> 00:12:46.730 align:start position:0% expect it to maybe that's a dynamic calculation<00:12:43.620> of<00:12:44.480> on-chain<00:12:45.480> royalties<00:12:46.019> right 00:12:46.730 --> 00:12:46.740 align:start position:0% calculation of on-chain royalties right 00:12:46.740 --> 00:12:48.650 align:start position:0% calculation of on-chain royalties right something<00:12:47.220> like<00:12:47.519> that<00:12:47.760> so<00:12:48.060> let's<00:12:48.180> talk<00:12:48.480> about 00:12:48.650 --> 00:12:48.660 align:start position:0% something like that so let's talk about 00:12:48.660 --> 00:12:51.769 align:start position:0% something like that so let's talk about a<00:12:48.959> couple<00:12:49.139> potential<00:12:50.060> zones<00:12:51.060> things<00:12:51.660> you 00:12:51.769 --> 00:12:51.779 align:start position:0% a couple potential zones things you 00:12:51.779 --> 00:12:53.210 align:start position:0% a couple potential zones things you could<00:12:51.899> use<00:12:52.079> them<00:12:52.320> for 00:12:53.210 --> 00:12:53.220 align:start position:0% could use them for 00:12:53.220 --> 00:12:56.269 align:start position:0% could use them for so<00:12:53.880> one<00:12:54.600> application<00:12:55.380> of<00:12:55.620> zones<00:12:55.860> is<00:12:56.100> for 00:12:56.269 --> 00:12:56.279 align:start position:0% so one application of zones is for 00:12:56.279 --> 00:12:59.870 align:start position:0% so one application of zones is for dynamic<00:12:56.880> nft<00:12:57.240> metadata 00:12:59.870 --> 00:12:59.880 align:start position:0% dynamic nft metadata 00:12:59.880 --> 00:13:01.790 align:start position:0% dynamic nft metadata certain<00:13:00.540> items 00:13:01.790 --> 00:13:01.800 align:start position:0% certain items 00:13:01.800 --> 00:13:04.910 align:start position:0% certain items in<00:13:02.279> Seaport<00:13:02.820> they're<00:13:03.420> called<00:13:03.920> criteria-based 00:13:04.910 --> 00:13:04.920 align:start position:0% in Seaport they're called criteria-based 00:13:04.920 --> 00:13:08.509 align:start position:0% in Seaport they're called criteria-based items<00:13:05.420> and<00:13:06.420> in<00:13:06.600> place<00:13:06.839> of<00:13:07.019> giving<00:13:07.320> a<00:13:07.980> token<00:13:08.399> ID 00:13:08.509 --> 00:13:08.519 align:start position:0% items and in place of giving a token ID 00:13:08.519 --> 00:13:12.230 align:start position:0% items and in place of giving a token ID an<00:13:09.060> identifier<00:13:09.980> you<00:13:10.980> instead<00:13:11.279> give<00:13:11.519> a<00:13:11.760> Merkle 00:13:12.230 --> 00:13:12.240 align:start position:0% an identifier you instead give a Merkle 00:13:12.240 --> 00:13:15.650 align:start position:0% an identifier you instead give a Merkle root<00:13:12.540> and<00:13:13.260> this<00:13:13.440> Merkle<00:13:13.860> root<00:13:14.160> is<00:13:15.000> comprised 00:13:15.650 --> 00:13:15.660 align:start position:0% root and this Merkle root is comprised 00:13:15.660 --> 00:13:16.389 align:start position:0% root and this Merkle root is comprised of 00:13:16.389 --> 00:13:16.399 align:start position:0% of 00:13:16.399 --> 00:13:20.090 align:start position:0% of all<00:13:17.399> the<00:13:17.639> token<00:13:18.000> IDs<00:13:18.420> that<00:13:18.720> are<00:13:18.959> valid<00:13:19.380> or<00:13:19.920> you 00:13:20.090 --> 00:13:20.100 align:start position:0% all the token IDs that are valid or you 00:13:20.100 --> 00:13:22.129 align:start position:0% all the token IDs that are valid or you can<00:13:20.160> give<00:13:20.279> an<00:13:20.459> empty<00:13:20.760> one<00:13:20.940> and<00:13:21.180> that<00:13:21.420> signifies 00:13:22.129 --> 00:13:22.139 align:start position:0% can give an empty one and that signifies 00:13:22.139 --> 00:13:24.110 align:start position:0% can give an empty one and that signifies it's<00:13:22.800> a<00:13:23.040> wild<00:13:23.160> card<00:13:23.339> you<00:13:23.700> can<00:13:23.760> pick<00:13:23.880> whatever 00:13:24.110 --> 00:13:24.120 align:start position:0% it's a wild card you can pick whatever 00:13:24.120 --> 00:13:26.750 align:start position:0% it's a wild card you can pick whatever token<00:13:24.720> ID<00:13:24.899> you<00:13:25.260> want 00:13:26.750 --> 00:13:26.760 align:start position:0% token ID you want 00:13:26.760 --> 00:13:28.430 align:start position:0% token ID you want but 00:13:28.430 --> 00:13:28.440 align:start position:0% but 00:13:28.440 --> 00:13:31.610 align:start position:0% but this<00:13:29.160> only<00:13:29.339> gives<00:13:29.700> you<00:13:29.940> so<00:13:30.779> much<00:13:30.839> granularity 00:13:31.610 --> 00:13:31.620 align:start position:0% this only gives you so much granularity 00:13:31.620 --> 00:13:33.949 align:start position:0% this only gives you so much granularity because<00:13:31.920> at<00:13:32.639> the<00:13:32.760> time<00:13:33.000> that<00:13:33.300> you<00:13:33.480> sign<00:13:33.660> the 00:13:33.949 --> 00:13:33.959 align:start position:0% because at the time that you sign the 00:13:33.959 --> 00:13:36.769 align:start position:0% because at the time that you sign the order<00:13:34.139> it<00:13:35.100> might<00:13:35.339> have 00:13:36.769 --> 00:13:36.779 align:start position:0% order it might have 00:13:36.779 --> 00:13:40.129 align:start position:0% order it might have certain<00:13:37.500> metadata<00:13:38.279> but<00:13:38.700> maybe<00:13:39.120> the<00:13:39.660> metadata 00:13:40.129 --> 00:13:40.139 align:start position:0% certain metadata but maybe the metadata 00:13:40.139 --> 00:13:42.889 align:start position:0% certain metadata but maybe the metadata gets<00:13:40.380> updated<00:13:40.680> right<00:13:41.459> so<00:13:41.760> the<00:13:42.000> traits<00:13:42.420> the 00:13:42.889 --> 00:13:42.899 align:start position:0% gets updated right so the traits the 00:13:42.899 --> 00:13:46.370 align:start position:0% gets updated right so the traits the attributes<00:13:43.380> that<00:13:44.279> that<00:13:44.720> this<00:13:45.720> had<00:13:45.899> with<00:13:46.139> the 00:13:46.370 --> 00:13:46.380 align:start position:0% attributes that that this had with the 00:13:46.380 --> 00:13:48.110 align:start position:0% attributes that that this had with the time<00:13:46.560> you<00:13:46.740> created<00:13:47.040> the<00:13:47.220> order<00:13:47.399> they've 00:13:48.110 --> 00:13:48.120 align:start position:0% time you created the order they've 00:13:48.120 --> 00:13:49.430 align:start position:0% time you created the order they've changed<00:13:48.540> now 00:13:49.430 --> 00:13:49.440 align:start position:0% changed now 00:13:49.440 --> 00:13:51.949 align:start position:0% changed now so<00:13:49.980> you<00:13:50.399> can<00:13:50.519> obviously 00:13:51.949 --> 00:13:51.959 align:start position:0% so you can obviously 00:13:51.959 --> 00:13:55.190 align:start position:0% so you can obviously leverage<00:13:52.620> zones<00:13:52.980> for<00:13:53.160> this<00:13:53.540> anytime<00:13:54.540> that<00:13:54.839> a 00:13:55.190 --> 00:13:55.200 align:start position:0% leverage zones for this anytime that a 00:13:55.200 --> 00:13:58.370 align:start position:0% leverage zones for this anytime that a creator<00:13:55.680> of<00:13:56.100> an<00:13:56.220> nft<00:13:56.519> updates<00:13:57.180> their<00:13:57.420> metadata 00:13:58.370 --> 00:13:58.380 align:start position:0% creator of an nft updates their metadata 00:13:58.380 --> 00:14:01.430 align:start position:0% creator of an nft updates their metadata they<00:13:58.920> go<00:13:59.220> and<00:13:59.639> they<00:14:00.000> update<00:14:00.480> the<00:14:00.660> zone 00:14:01.430 --> 00:14:01.440 align:start position:0% they go and they update the zone 00:14:01.440 --> 00:14:03.410 align:start position:0% they go and they update the zone registering<00:14:02.399> that 00:14:03.410 --> 00:14:03.420 align:start position:0% registering that 00:14:03.420 --> 00:14:07.250 align:start position:0% registering that hey<00:14:04.019> this<00:14:04.680> particular<00:14:05.240> Merkel<00:14:06.240> route<00:14:06.420> is 00:14:07.250 --> 00:14:07.260 align:start position:0% hey this particular Merkel route is 00:14:07.260 --> 00:14:10.310 align:start position:0% hey this particular Merkel route is actually<00:14:07.500> now<00:14:07.860> this<00:14:08.339> other<00:14:08.579> one<00:14:08.880> right<00:14:09.360> and 00:14:10.310 --> 00:14:10.320 align:start position:0% actually now this other one right and 00:14:10.320 --> 00:14:11.569 align:start position:0% actually now this other one right and you<00:14:10.500> can't<00:14:10.620> match 00:14:11.569 --> 00:14:11.579 align:start position:0% you can't match 00:14:11.579 --> 00:14:15.650 align:start position:0% you can't match the<00:14:12.060> tokens<00:14:12.480> that<00:14:12.720> have<00:14:12.899> changed 00:14:15.650 --> 00:14:15.660 align:start position:0% 00:14:15.660 --> 00:14:18.470 align:start position:0% another<00:14:16.200> potential<00:14:16.980> use<00:14:17.160> case<00:14:17.399> is<00:14:17.639> for 00:14:18.470 --> 00:14:18.480 align:start position:0% another potential use case is for 00:14:18.480 --> 00:14:20.690 align:start position:0% another potential use case is for compromised<00:14:19.320> nfts 00:14:20.690 --> 00:14:20.700 align:start position:0% compromised nfts 00:14:20.700 --> 00:14:22.190 align:start position:0% compromised nfts you<00:14:21.060> might<00:14:21.180> have 00:14:22.190 --> 00:14:22.200 align:start position:0% you might have 00:14:22.200 --> 00:14:26.150 align:start position:0% you might have an<00:14:22.500> nft<00:14:22.740> that<00:14:23.100> gets<00:14:23.399> stolen<00:14:24.120> and 00:14:26.150 --> 00:14:26.160 align:start position:0% an nft that gets stolen and 00:14:26.160 --> 00:14:27.650 align:start position:0% an nft that gets stolen and um<00:14:26.279> you<00:14:26.639> don't<00:14:26.760> want<00:14:26.880> to<00:14:27.000> be<00:14:27.060> able<00:14:27.180> to<00:14:27.300> trade<00:14:27.480> it 00:14:27.650 --> 00:14:27.660 align:start position:0% um you don't want to be able to trade it 00:14:27.660 --> 00:14:30.650 align:start position:0% um you don't want to be able to trade it anymore<00:14:27.779> and<00:14:28.579> that's<00:14:29.579> one<00:14:29.940> potential<00:14:30.480> use 00:14:30.650 --> 00:14:30.660 align:start position:0% anymore and that's one potential use 00:14:30.660 --> 00:14:32.449 align:start position:0% anymore and that's one potential use case<00:14:30.839> for<00:14:31.079> his<00:14:31.260> own<00:14:31.500> is<00:14:31.740> to 00:14:32.449 --> 00:14:32.459 align:start position:0% case for his own is to 00:14:32.459 --> 00:14:35.030 align:start position:0% case for his own is to just<00:14:33.120> check<00:14:33.360> and<00:14:33.540> make<00:14:33.720> sure<00:14:33.839> that<00:14:34.139> the<00:14:34.440> items 00:14:35.030 --> 00:14:35.040 align:start position:0% just check and make sure that the items 00:14:35.040 --> 00:14:37.610 align:start position:0% just check and make sure that the items that<00:14:35.279> are<00:14:35.459> part<00:14:35.880> of<00:14:36.120> the<00:14:36.540> order<00:14:36.720> are<00:14:37.200> no<00:14:37.380> longer 00:14:37.610 --> 00:14:37.620 align:start position:0% that are part of the order are no longer 00:14:37.620 --> 00:14:41.030 align:start position:0% that are part of the order are no longer fillable 00:14:41.030 --> 00:14:41.040 align:start position:0% 00:14:41.040 --> 00:14:43.490 align:start position:0% another<00:14:41.519> cool<00:14:41.820> potential<00:14:42.300> use<00:14:42.600> case 00:14:43.490 --> 00:14:43.500 align:start position:0% another cool potential use case 00:14:43.500 --> 00:14:46.629 align:start position:0% another cool potential use case is<00:14:43.980> for<00:14:44.279> front<00:14:44.579> running<00:14:44.820> resistance 00:14:46.629 --> 00:14:46.639 align:start position:0% is for front running resistance 00:14:46.639 --> 00:14:49.490 align:start position:0% is for front running resistance say<00:14:47.639> I<00:14:47.880> have<00:14:48.000> a<00:14:48.120> Zone<00:14:48.360> where<00:14:48.600> I<00:14:49.019> have<00:14:49.139> to<00:14:49.260> call 00:14:49.490 --> 00:14:49.500 align:start position:0% say I have a Zone where I have to call 00:14:49.500 --> 00:14:51.470 align:start position:0% say I have a Zone where I have to call five<00:14:49.860> minutes<00:14:50.040> ahead<00:14:50.399> of<00:14:50.519> time 00:14:51.470 --> 00:14:51.480 align:start position:0% five minutes ahead of time 00:14:51.480 --> 00:14:53.269 align:start position:0% five minutes ahead of time and<00:14:52.079> commit 00:14:53.269 --> 00:14:53.279 align:start position:0% and commit 00:14:53.279 --> 00:14:56.030 align:start position:0% and commit similar<00:14:53.820> to<00:14:53.940> how<00:14:54.240> you<00:14:54.420> would<00:14:54.540> do<00:14:54.660> it<00:14:54.779> with<00:14:55.500> um<00:14:55.500> I 00:14:56.030 --> 00:14:56.040 align:start position:0% similar to how you would do it with um I 00:14:56.040 --> 00:14:58.670 align:start position:0% similar to how you would do it with um I believe<00:14:56.220> ens<00:14:56.820> has<00:14:57.240> a<00:14:57.360> similar<00:14:57.660> thing 00:14:58.670 --> 00:14:58.680 align:start position:0% believe ens has a similar thing 00:14:58.680 --> 00:15:01.310 align:start position:0% believe ens has a similar thing you<00:14:59.100> register<00:14:59.459> ahead<00:14:59.760> of<00:14:59.880> time<00:14:59.940> and<00:15:00.180> say 00:15:01.310 --> 00:15:01.320 align:start position:0% you register ahead of time and say 00:15:01.320 --> 00:15:03.710 align:start position:0% you register ahead of time and say I<00:15:01.860> want<00:15:01.980> to<00:15:02.100> fill<00:15:02.220> this<00:15:02.459> then<00:15:03.060> you<00:15:03.240> wait<00:15:03.420> some 00:15:03.710 --> 00:15:03.720 align:start position:0% I want to fill this then you wait some 00:15:03.720 --> 00:15:06.829 align:start position:0% I want to fill this then you wait some period<00:15:04.019> of<00:15:04.199> time<00:15:04.380> and<00:15:05.279> then<00:15:05.399> you<00:15:05.579> reveal<00:15:06.000> you 00:15:06.829 --> 00:15:06.839 align:start position:0% period of time and then you reveal you 00:15:06.839 --> 00:15:09.410 align:start position:0% period of time and then you reveal you include<00:15:07.260> as<00:15:07.620> part<00:15:07.800> of<00:15:08.040> the<00:15:08.639> the<00:15:08.820> parameters 00:15:09.410 --> 00:15:09.420 align:start position:0% include as part of the the parameters 00:15:09.420 --> 00:15:11.930 align:start position:0% include as part of the the parameters called<00:15:09.839> extra<00:15:10.199> data<00:15:10.740> when<00:15:11.279> you're<00:15:11.399> fulfilling 00:15:11.930 --> 00:15:11.940 align:start position:0% called extra data when you're fulfilling 00:15:11.940 --> 00:15:14.629 align:start position:0% called extra data when you're fulfilling that<00:15:12.660> gets<00:15:12.959> passed<00:15:13.260> along<00:15:13.380> to<00:15:13.680> the<00:15:13.860> zone 00:15:14.629 --> 00:15:14.639 align:start position:0% that gets passed along to the zone 00:15:14.639 --> 00:15:17.810 align:start position:0% that gets passed along to the zone The<00:15:15.180> Zone<00:15:15.420> then<00:15:15.779> can<00:15:16.380> look<00:15:16.680> and<00:15:16.860> say<00:15:17.040> oh 00:15:17.810 --> 00:15:17.820 align:start position:0% The Zone then can look and say oh 00:15:17.820 --> 00:15:20.449 align:start position:0% The Zone then can look and say oh there's<00:15:18.360> a<00:15:18.480> commit<00:15:18.720> I'm<00:15:18.959> going<00:15:19.079> to<00:15:19.139> Hash<00:15:19.320> this 00:15:20.449 --> 00:15:20.459 align:start position:0% there's a commit I'm going to Hash this 00:15:20.459 --> 00:15:23.150 align:start position:0% there's a commit I'm going to Hash this looks<00:15:21.120> like<00:15:21.180> you<00:15:21.360> committed<00:15:21.779> to<00:15:22.260> being<00:15:23.040> able 00:15:23.150 --> 00:15:23.160 align:start position:0% looks like you committed to being able 00:15:23.160 --> 00:15:26.329 align:start position:0% looks like you committed to being able to<00:15:23.279> fulfill<00:15:23.519> this<00:15:23.699> order 00:15:26.329 --> 00:15:26.339 align:start position:0% 00:15:26.339 --> 00:15:28.490 align:start position:0% another<00:15:26.820> interesting<00:15:27.240> one<00:15:27.420> is<00:15:27.720> leveraging 00:15:28.490 --> 00:15:28.500 align:start position:0% another interesting one is leveraging 00:15:28.500 --> 00:15:29.629 align:start position:0% another interesting one is leveraging Oracles 00:15:29.629 --> 00:15:29.639 align:start position:0% Oracles 00:15:29.639 --> 00:15:32.750 align:start position:0% Oracles maybe<00:15:30.060> I<00:15:30.360> have<00:15:30.720> a<00:15:31.139> listing<00:15:31.440> I<00:15:32.160> don't<00:15:32.279> want<00:15:32.519> this 00:15:32.750 --> 00:15:32.760 align:start position:0% maybe I have a listing I don't want this 00:15:32.760 --> 00:15:34.430 align:start position:0% maybe I have a listing I don't want this listing<00:15:33.060> to<00:15:33.240> be<00:15:33.360> fulfillable<00:15:33.779> if<00:15:34.019> the<00:15:34.260> floor 00:15:34.430 --> 00:15:34.440 align:start position:0% listing to be fulfillable if the floor 00:15:34.440 --> 00:15:36.230 align:start position:0% listing to be fulfillable if the floor falls<00:15:34.800> out 00:15:36.230 --> 00:15:36.240 align:start position:0% falls out 00:15:36.240 --> 00:15:39.889 align:start position:0% falls out so<00:15:36.600> I<00:15:36.839> could<00:15:37.019> read<00:15:37.680> from<00:15:37.980> an<00:15:38.279> oracle<00:15:38.639> that<00:15:38.940> is 00:15:39.889 --> 00:15:39.899 align:start position:0% so I could read from an oracle that is 00:15:39.899 --> 00:15:41.569 align:start position:0% so I could read from an oracle that is periodically<00:15:40.440> updated<00:15:40.740> and<00:15:41.040> if<00:15:41.220> the<00:15:41.399> price 00:15:41.569 --> 00:15:41.579 align:start position:0% periodically updated and if the price 00:15:41.579 --> 00:15:44.389 align:start position:0% periodically updated and if the price drifts<00:15:42.000> too<00:15:42.240> much<00:15:42.420> then 00:15:44.389 --> 00:15:44.399 align:start position:0% drifts too much then 00:15:44.399 --> 00:15:46.370 align:start position:0% drifts too much then cancel<00:15:44.940> the<00:15:45.240> order<00:15:45.360> don't<00:15:45.899> let<00:15:46.079> it<00:15:46.260> be 00:15:46.370 --> 00:15:46.380 align:start position:0% cancel the order don't let it be 00:15:46.380 --> 00:15:49.850 align:start position:0% cancel the order don't let it be fulfilled<00:15:47.120> or<00:15:48.120> you<00:15:48.600> can<00:15:48.720> even<00:15:48.959> leverage<00:15:49.500> this 00:15:49.850 --> 00:15:49.860 align:start position:0% fulfilled or you can even leverage this 00:15:49.860 --> 00:15:53.350 align:start position:0% fulfilled or you can even leverage this along<00:15:50.639> with<00:15:51.000> that<00:15:51.300> trick<00:15:51.660> with<00:15:52.260> uh 00:15:53.350 --> 00:15:53.360 align:start position:0% along with that trick with uh 00:15:53.360 --> 00:15:56.569 align:start position:0% along with that trick with uh Dynamic<00:15:54.360> orders<00:15:54.720> with<00:15:55.019> 1271 00:15:56.569 --> 00:15:56.579 align:start position:0% Dynamic orders with 1271 00:15:56.579 --> 00:16:00.889 align:start position:0% Dynamic orders with 1271 to<00:15:57.540> create<00:15:58.199> a<00:15:58.440> strategy<00:15:58.860> that<00:15:59.279> will 00:16:00.889 --> 00:16:00.899 align:start position:0% to create a strategy that will 00:16:00.899 --> 00:16:04.370 align:start position:0% to create a strategy that will buy<00:16:01.320> nfts<00:16:01.980> below<00:16:02.639> the<00:16:02.760> floor<00:16:02.940> price<00:16:03.240> sell<00:16:03.779> nfts 00:16:04.370 --> 00:16:04.380 align:start position:0% buy nfts below the floor price sell nfts 00:16:04.380 --> 00:16:09.290 align:start position:0% buy nfts below the floor price sell nfts above<00:16:04.680> the<00:16:04.800> floor<00:16:04.980> price<00:16:05.279> that<00:16:05.820> kind<00:16:06.000> of<00:16:06.120> thing 00:16:09.290 --> 00:16:09.300 align:start position:0% 00:16:09.300 --> 00:16:11.050 align:start position:0% so<00:16:09.660> here's<00:16:09.899> some<00:16:10.019> links 00:16:11.050 --> 00:16:11.060 align:start position:0% so here's some links 00:16:11.060 --> 00:16:13.009 align:start position:0% so here's some links we've<00:16:12.060> got 00:16:13.009 --> 00:16:13.019 align:start position:0% we've got 00:16:13.019 --> 00:16:16.790 align:start position:0% we've got obviously<00:16:13.680> the<00:16:13.860> seaport<00:16:14.480> repo<00:16:15.480> itself<00:16:15.839> as 00:16:16.790 --> 00:16:16.800 align:start position:0% obviously the seaport repo itself as 00:16:16.800 --> 00:16:17.829 align:start position:0% obviously the seaport repo itself as well<00:16:16.980> as 00:16:17.829 --> 00:16:17.839 align:start position:0% well as 00:16:17.839 --> 00:16:20.990 align:start position:0% well as any<00:16:18.839> any<00:16:19.620> questions<00:16:19.980> or<00:16:20.399> do<00:16:20.639> you<00:16:20.760> want<00:16:20.820> to<00:16:20.880> get 00:16:20.990 --> 00:16:21.000 align:start position:0% any any questions or do you want to get 00:16:21.000 --> 00:16:25.009 align:start position:0% any any questions or do you want to get into<00:16:21.120> the<00:16:21.420> weeds<00:16:22.019> the<00:16:22.920> discussions<00:16:23.459> uh<00:16:24.360> there 00:16:25.009 --> 00:16:25.019 align:start position:0% into the weeds the discussions uh there 00:16:25.019 --> 00:16:25.790 align:start position:0% into the weeds the discussions uh there are 00:16:25.790 --> 00:16:25.800 align:start position:0% are 00:16:25.800 --> 00:16:29.689 align:start position:0% are great<00:16:26.399> place<00:16:26.579> for<00:16:26.820> that 00:16:29.689 --> 00:16:29.699 align:start position:0% 00:16:29.699 --> 00:16:32.569 align:start position:0% Seaport<00:16:30.240> JS<00:16:30.660> is<00:16:31.380> a<00:16:31.620> library<00:16:31.800> for<00:16:32.160> interacting 00:16:32.569 --> 00:16:32.579 align:start position:0% Seaport JS is a library for interacting 00:16:32.579 --> 00:16:34.730 align:start position:0% Seaport JS is a library for interacting with<00:16:32.760> Seaport<00:16:33.240> makes<00:16:33.899> a<00:16:34.079> lot<00:16:34.199> of<00:16:34.380> this<00:16:34.500> stuff 00:16:34.730 --> 00:16:34.740 align:start position:0% with Seaport makes a lot of this stuff 00:16:34.740 --> 00:16:37.610 align:start position:0% with Seaport makes a lot of this stuff much<00:16:35.220> more<00:16:35.820> straightforward 00:16:37.610 --> 00:16:37.620 align:start position:0% much more straightforward 00:16:37.620 --> 00:16:40.129 align:start position:0% much more straightforward one<00:16:38.160> thing<00:16:38.279> that<00:16:38.459> I<00:16:38.639> will<00:16:38.759> note 00:16:40.129 --> 00:16:40.139 align:start position:0% one thing that I will note 00:16:40.139 --> 00:16:42.290 align:start position:0% one thing that I will note is<00:16:40.620> that<00:16:40.860> much<00:16:41.339> of<00:16:41.459> the<00:16:41.639> match<00:16:41.880> orders 00:16:42.290 --> 00:16:42.300 align:start position:0% is that much of the match orders 00:16:42.300 --> 00:16:44.689 align:start position:0% is that much of the match orders functionality<00:16:42.899> is<00:16:43.380> a<00:16:43.740> little<00:16:43.860> more<00:16:44.220> rough 00:16:44.689 --> 00:16:44.699 align:start position:0% functionality is a little more rough 00:16:44.699 --> 00:16:46.249 align:start position:0% functionality is a little more rough around<00:16:44.940> the<00:16:45.240> edges 00:16:46.249 --> 00:16:46.259 align:start position:0% around the edges 00:16:46.259 --> 00:16:48.410 align:start position:0% around the edges would<00:16:46.680> love<00:16:46.860> any<00:16:47.220> contributions<00:16:47.759> if<00:16:48.000> anyone 00:16:48.410 --> 00:16:48.420 align:start position:0% would love any contributions if anyone 00:16:48.420 --> 00:16:53.870 align:start position:0% would love any contributions if anyone finds<00:16:49.079> themselves<00:16:49.320> working<00:16:49.620> on<00:16:49.920> that 00:16:53.870 --> 00:16:53.880 align:start position:0% 00:16:53.880 --> 00:16:57.350 align:start position:0% and<00:16:54.420> then<00:16:54.600> this<00:16:55.320> last<00:16:55.560> link<00:16:56.060> Seaport<00:16:57.060> order 00:16:57.350 --> 00:16:57.360 align:start position:0% and then this last link Seaport order 00:16:57.360 --> 00:17:00.290 align:start position:0% and then this last link Seaport order validator<00:16:58.040> this<00:16:59.040> is<00:16:59.220> a<00:16:59.399> contract<00:16:59.820> that<00:17:00.000> we<00:17:00.180> put 00:17:00.290 --> 00:17:00.300 align:start position:0% validator this is a contract that we put 00:17:00.300 --> 00:17:04.490 align:start position:0% validator this is a contract that we put together<00:17:00.860> to<00:17:01.860> make<00:17:02.100> it<00:17:02.279> easier<00:17:02.639> for<00:17:03.500> checking 00:17:04.490 --> 00:17:04.500 align:start position:0% together to make it easier for checking 00:17:04.500 --> 00:17:07.610 align:start position:0% together to make it easier for checking an<00:17:04.679> order<00:17:05.000> or<00:17:06.000> if<00:17:06.480> you<00:17:06.660> are<00:17:06.839> accepting<00:17:07.380> new 00:17:07.610 --> 00:17:07.620 align:start position:0% an order or if you are accepting new 00:17:07.620 --> 00:17:11.150 align:start position:0% an order or if you are accepting new orders<00:17:07.980> coming<00:17:08.220> in<00:17:08.480> there's<00:17:09.480> a<00:17:09.900> lot<00:17:10.140> there's<00:17:10.980> a 00:17:11.150 --> 00:17:11.160 align:start position:0% orders coming in there's a lot there's a 00:17:11.160 --> 00:17:12.710 align:start position:0% orders coming in there's a lot there's a lot<00:17:11.220> of<00:17:11.339> gotchas 00:17:12.710 --> 00:17:12.720 align:start position:0% lot of gotchas 00:17:12.720 --> 00:17:15.470 align:start position:0% lot of gotchas things<00:17:13.439> that<00:17:13.620> can<00:17:13.740> go<00:17:13.860> wrong 00:17:15.470 --> 00:17:15.480 align:start position:0% things that can go wrong 00:17:15.480 --> 00:17:18.949 align:start position:0% things that can go wrong um<00:17:15.540> and<00:17:16.199> it's<00:17:16.500> a<00:17:16.679> quick<00:17:16.799> way<00:17:17.040> to<00:17:17.339> say<00:17:17.520> oh<00:17:18.299> this 00:17:18.949 --> 00:17:18.959 align:start position:0% um and it's a quick way to say oh this 00:17:18.959 --> 00:17:21.110 align:start position:0% um and it's a quick way to say oh this order<00:17:19.140> looks<00:17:19.740> like<00:17:19.860> you're<00:17:20.640> not<00:17:20.880> actually 00:17:21.110 --> 00:17:21.120 align:start position:0% order looks like you're not actually 00:17:21.120 --> 00:17:23.150 align:start position:0% order looks like you're not actually getting<00:17:21.480> anything<00:17:21.780> from<00:17:22.500> the<00:17:22.679> order<00:17:22.799> right 00:17:23.150 --> 00:17:23.160 align:start position:0% getting anything from the order right 00:17:23.160 --> 00:17:25.490 align:start position:0% getting anything from the order right you're<00:17:23.459> not<00:17:23.699> set<00:17:24.000> as<00:17:24.660> one<00:17:24.839> of<00:17:24.959> the<00:17:25.020> recipients 00:17:25.490 --> 00:17:25.500 align:start position:0% you're not set as one of the recipients 00:17:25.500 --> 00:17:26.929 align:start position:0% you're not set as one of the recipients on<00:17:25.679> a<00:17:25.860> consideration<00:17:26.220> item<00:17:26.520> you<00:17:26.640> sure<00:17:26.819> you 00:17:26.929 --> 00:17:26.939 align:start position:0% on a consideration item you sure you 00:17:26.939 --> 00:17:28.309 align:start position:0% on a consideration item you sure you want<00:17:27.059> to<00:17:27.179> do<00:17:27.299> this 00:17:28.309 --> 00:17:28.319 align:start position:0% want to do this 00:17:28.319 --> 00:17:31.789 align:start position:0% want to do this there's<00:17:28.799> a<00:17:29.460> hundred<00:17:30.000> permutations<00:17:30.660> of 00:17:31.789 --> 00:17:31.799 align:start position:0% there's a hundred permutations of 00:17:31.799 --> 00:17:33.770 align:start position:0% there's a hundred permutations of things<00:17:32.340> that<00:17:32.640> can<00:17:32.820> be 00:17:33.770 --> 00:17:33.780 align:start position:0% things that can be 00:17:33.780 --> 00:17:34.370 align:start position:0% things that can be um 00:17:34.370 --> 00:17:34.380 align:start position:0% um 00:17:34.380 --> 00:17:37.190 align:start position:0% um maybe<00:17:35.160> a<00:17:35.400> warning<00:17:35.880> or<00:17:36.179> a<00:17:36.360> not<00:17:36.600> right<00:17:36.780> error 00:17:37.190 --> 00:17:37.200 align:start position:0% maybe a warning or a not right error 00:17:37.200 --> 00:17:40.430 align:start position:0% maybe a warning or a not right error right<00:17:37.559> so<00:17:38.340> it'll<00:17:38.580> check<00:17:38.960> uh<00:17:39.960> on<00:17:40.200> chain 00:17:40.430 --> 00:17:40.440 align:start position:0% right so it'll check uh on chain 00:17:40.440 --> 00:17:44.330 align:start position:0% right so it'll check uh on chain registry<00:17:41.400> for<00:17:41.900> uh<00:17:42.900> Creator<00:17:43.320> information<00:17:43.620> like 00:17:44.330 --> 00:17:44.340 align:start position:0% registry for uh Creator information like 00:17:44.340 --> 00:17:47.090 align:start position:0% registry for uh Creator information like make<00:17:45.299> sure<00:17:45.480> that<00:17:45.780> the<00:17:45.960> the<00:17:46.140> tokens<00:17:46.620> Implement 00:17:47.090 --> 00:17:47.100 align:start position:0% make sure that the the tokens Implement 00:17:47.100 --> 00:17:49.970 align:start position:0% make sure that the the tokens Implement EIP<00:17:47.640> 165<00:17:48.480> that<00:17:49.320> you're<00:17:49.500> not<00:17:49.620> trying<00:17:49.799> to 00:17:49.970 --> 00:17:49.980 align:start position:0% EIP 165 that you're not trying to 00:17:49.980 --> 00:17:52.669 align:start position:0% EIP 165 that you're not trying to pretend<00:17:50.340> like<00:17:50.700> one<00:17:51.600> one<00:17:51.960> token<00:17:52.440> that's 00:17:52.669 --> 00:17:52.679 align:start position:0% pretend like one one token that's 00:17:52.679 --> 00:17:56.450 align:start position:0% pretend like one one token that's actually<00:17:52.980> a<00:17:53.820> as<00:17:54.419> nfts<00:17:55.140> and<00:17:55.440> erc20<00:17:56.039> token 00:17:56.450 --> 00:17:56.460 align:start position:0% actually a as nfts and erc20 token 00:17:56.460 --> 00:17:58.010 align:start position:0% actually a as nfts and erc20 token something<00:17:56.760> like<00:17:57.000> that 00:17:58.010 --> 00:17:58.020 align:start position:0% something like that 00:17:58.020 --> 00:18:00.590 align:start position:0% something like that all<00:17:58.620> kinds<00:17:58.799> of<00:17:58.860> interesting<00:17:59.220> stuff<00:17:59.400> and<00:17:59.940> if 00:18:00.590 --> 00:18:00.600 align:start position:0% all kinds of interesting stuff and if 00:18:00.600 --> 00:18:03.650 align:start position:0% all kinds of interesting stuff and if you're<00:18:00.780> trying<00:18:01.020> to<00:18:01.380> just<00:18:02.100> piece<00:18:02.520> together<00:18:02.700> the 00:18:03.650 --> 00:18:03.660 align:start position:0% you're trying to just piece together the 00:18:03.660 --> 00:18:05.510 align:start position:0% you're trying to just piece together the potential<00:18:04.020> uh 00:18:05.510 --> 00:18:05.520 align:start position:0% potential uh 00:18:05.520 --> 00:18:07.070 align:start position:0% potential uh things<00:18:05.880> that<00:18:06.059> can<00:18:06.179> go<00:18:06.240> wrong<00:18:06.360> this<00:18:06.660> is<00:18:06.780> a<00:18:06.900> great 00:18:07.070 --> 00:18:07.080 align:start position:0% things that can go wrong this is a great 00:18:07.080 --> 00:18:09.590 align:start position:0% things that can go wrong this is a great resource 00:18:09.590 --> 00:18:09.600 align:start position:0% 00:18:09.600 --> 00:18:10.970 align:start position:0% so 00:18:10.970 --> 00:18:10.980 align:start position:0% so 00:18:10.980 --> 00:18:13.850 align:start position:0% so how<00:18:11.280> we<00:18:11.460> doing<00:18:11.580> on<00:18:11.820> time 00:18:13.850 --> 00:18:13.860 align:start position:0% how we doing on time 00:18:13.860 --> 00:18:16.810 align:start position:0% how we doing on time all<00:18:14.280> right<00:18:14.460> I<00:18:15.179> think<00:18:15.299> we<00:18:15.480> can<00:18:15.600> open<00:18:15.780> it<00:18:16.020> up<00:18:16.200> for 00:18:16.810 --> 00:18:16.820 align:start position:0% all right I think we can open it up for 00:18:16.820 --> 00:18:19.490 align:start position:0% all right I think we can open it up for discussion<00:18:17.820> first<00:18:18.240> off<00:18:18.480> if<00:18:18.780> anybody<00:18:19.080> is 00:18:19.490 --> 00:18:19.500 align:start position:0% discussion first off if anybody is 00:18:19.500 --> 00:18:22.930 align:start position:0% discussion first off if anybody is currently<00:18:20.039> building<00:18:21.000> on<00:18:21.480> top<00:18:21.600> of<00:18:21.840> Seaport 00:18:22.930 --> 00:18:22.940 align:start position:0% currently building on top of Seaport 00:18:22.940 --> 00:18:27.890 align:start position:0% currently building on top of Seaport and<00:18:23.940> has<00:18:24.900> a<00:18:25.200> a<00:18:25.740> sticking<00:18:26.220> point<00:18:26.400> or<00:18:26.760> a<00:18:26.940> question 00:18:27.890 --> 00:18:27.900 align:start position:0% and has a a sticking point or a question 00:18:27.900 --> 00:18:34.549 align:start position:0% and has a a sticking point or a question by<00:18:28.440> all<00:18:28.620> means<00:18:29.039> let's<00:18:30.000> let's<00:18:30.360> hear<00:18:30.660> them 00:18:34.549 --> 00:18:34.559 align:start position:0% 00:18:34.559 --> 00:18:40.130 align:start position:0% yeah<00:18:35.160> here<00:18:35.460> let<00:18:35.760> me<00:18:35.940> bring<00:18:36.299> Mike<00:18:36.539> over 00:18:40.130 --> 00:18:40.140 align:start position:0% 00:18:40.140 --> 00:18:41.930 align:start position:0% at<00:18:40.740> the<00:18:40.860> moment<00:18:40.980> but<00:18:41.160> I<00:18:41.280> do<00:18:41.340> have<00:18:41.460> a<00:18:41.580> question 00:18:41.930 --> 00:18:41.940 align:start position:0% at the moment but I do have a question 00:18:41.940 --> 00:18:44.630 align:start position:0% at the moment but I do have a question it's<00:18:42.240> great<00:18:42.600> yes 00:18:44.630 --> 00:18:44.640 align:start position:0% it's great yes 00:18:44.640 --> 00:18:45.950 align:start position:0% it's great yes um so 00:18:45.950 --> 00:18:45.960 align:start position:0% um so 00:18:45.960 --> 00:18:48.409 align:start position:0% um so certain<00:18:46.500> nfts<00:18:47.100> have<00:18:47.280> royalties<00:18:47.820> associated 00:18:48.409 --> 00:18:48.419 align:start position:0% certain nfts have royalties associated 00:18:48.419 --> 00:18:50.630 align:start position:0% certain nfts have royalties associated with<00:18:48.720> them<00:18:48.840> and<00:18:49.380> I<00:18:49.500> was<00:18:49.679> wondering<00:18:50.039> do<00:18:50.460> you 00:18:50.630 --> 00:18:50.640 align:start position:0% with them and I was wondering do you 00:18:50.640 --> 00:18:53.390 align:start position:0% with them and I was wondering do you include<00:18:51.120> the<00:18:51.660> royalties<00:18:52.260> in<00:18:52.799> the<00:18:53.039> orders 00:18:53.390 --> 00:18:53.400 align:start position:0% include the royalties in the orders 00:18:53.400 --> 00:18:55.490 align:start position:0% include the royalties in the orders themselves<00:18:53.880> or<00:18:54.419> does<00:18:54.600> that<00:18:54.840> get<00:18:55.080> handled 00:18:55.490 --> 00:18:55.500 align:start position:0% themselves or does that get handled 00:18:55.500 --> 00:18:57.529 align:start position:0% themselves or does that get handled somewhere<00:18:55.860> else<00:18:55.980> in<00:18:56.220> the<00:18:56.340> contract<00:18:56.640> and<00:18:57.179> if<00:18:57.360> so 00:18:57.529 --> 00:18:57.539 align:start position:0% somewhere else in the contract and if so 00:18:57.539 --> 00:18:59.690 align:start position:0% somewhere else in the contract and if so how<00:18:57.780> does<00:18:57.960> optimization<00:18:58.559> happen<00:18:58.980> on<00:18:59.580> that 00:18:59.690 --> 00:18:59.700 align:start position:0% how does optimization happen on that 00:18:59.700 --> 00:19:01.130 align:start position:0% how does optimization happen on that front 00:19:01.130 --> 00:19:01.140 align:start position:0% front 00:19:01.140 --> 00:19:03.650 align:start position:0% front yeah<00:19:01.679> so<00:19:01.980> the<00:19:02.100> basic<00:19:02.460> approach<00:19:02.880> as<00:19:03.480> I 00:19:03.650 --> 00:19:03.660 align:start position:0% yeah so the basic approach as I 00:19:03.660 --> 00:19:05.090 align:start position:0% yeah so the basic approach as I mentioned<00:19:03.840> earlier<00:19:04.140> Seaport<00:19:04.620> doesn't<00:19:04.860> have 00:19:05.090 --> 00:19:05.100 align:start position:0% mentioned earlier Seaport doesn't have 00:19:05.100 --> 00:19:08.029 align:start position:0% mentioned earlier Seaport doesn't have any<00:19:05.400> notion<00:19:05.880> of<00:19:06.480> fees<00:19:07.020> or<00:19:07.260> royalties<00:19:07.799> it's 00:19:08.029 --> 00:19:08.039 align:start position:0% any notion of fees or royalties it's 00:19:08.039 --> 00:19:11.630 align:start position:0% any notion of fees or royalties it's baked<00:19:08.580> in<00:19:08.640> it's<00:19:09.600> just<00:19:09.900> you<00:19:10.799> could<00:19:10.980> very<00:19:11.280> easily 00:19:11.630 --> 00:19:11.640 align:start position:0% baked in it's just you could very easily 00:19:11.640 --> 00:19:13.430 align:start position:0% baked in it's just you could very easily create<00:19:12.000> an<00:19:12.240> order<00:19:12.419> that<00:19:12.660> doesn't<00:19:12.900> include<00:19:13.260> any 00:19:13.430 --> 00:19:13.440 align:start position:0% create an order that doesn't include any 00:19:13.440 --> 00:19:15.590 align:start position:0% create an order that doesn't include any fees<00:19:13.860> or<00:19:13.980> royalties<00:19:14.340> whatsoever 00:19:15.590 --> 00:19:15.600 align:start position:0% fees or royalties whatsoever 00:19:15.600 --> 00:19:17.330 align:start position:0% fees or royalties whatsoever so<00:19:15.900> it's<00:19:16.020> really<00:19:16.200> up<00:19:16.440> to<00:19:16.559> the<00:19:16.799> discretion<00:19:17.160> of 00:19:17.330 --> 00:19:17.340 align:start position:0% so it's really up to the discretion of 00:19:17.340 --> 00:19:18.950 align:start position:0% so it's really up to the discretion of the<00:19:17.460> application<00:19:17.880> layer<00:19:18.240> whoever's<00:19:18.780> building 00:19:18.950 --> 00:19:18.960 align:start position:0% the application layer whoever's building 00:19:18.960 --> 00:19:20.690 align:start position:0% the application layer whoever's building on<00:19:19.260> top<00:19:19.440> of<00:19:19.559> it 00:19:20.690 --> 00:19:20.700 align:start position:0% on top of it 00:19:20.700 --> 00:19:22.190 align:start position:0% on top of it um 00:19:22.190 --> 00:19:22.200 align:start position:0% um 00:19:22.200 --> 00:19:24.830 align:start position:0% um one<00:19:23.160> approach<00:19:23.580> you<00:19:23.760> can<00:19:23.940> take<00:19:24.120> that<00:19:24.539> I<00:19:24.660> think 00:19:24.830 --> 00:19:24.840 align:start position:0% one approach you can take that I think 00:19:24.840 --> 00:19:28.610 align:start position:0% one approach you can take that I think is<00:19:25.140> a<00:19:25.500> pretty<00:19:25.620> good<00:19:25.860> one<00:19:26.160> is<00:19:27.120> to<00:19:27.780> just 00:19:28.610 --> 00:19:28.620 align:start position:0% is a pretty good one is to just 00:19:28.620 --> 00:19:30.770 align:start position:0% is a pretty good one is to just read<00:19:29.160> from<00:19:29.460> the<00:19:29.580> Registries<00:19:30.000> at<00:19:30.240> the<00:19:30.419> time<00:19:30.480> the 00:19:30.770 --> 00:19:30.780 align:start position:0% read from the Registries at the time the 00:19:30.780 --> 00:19:32.270 align:start position:0% read from the Registries at the time the order<00:19:30.900> is<00:19:31.140> created 00:19:32.270 --> 00:19:32.280 align:start position:0% order is created 00:19:32.280 --> 00:19:34.250 align:start position:0% order is created this<00:19:32.880> depending<00:19:33.299> on<00:19:33.419> your<00:19:33.600> perspective<00:19:34.020> is 00:19:34.250 --> 00:19:34.260 align:start position:0% this depending on your perspective is 00:19:34.260 --> 00:19:37.310 align:start position:0% this depending on your perspective is either<00:19:34.500> a<00:19:34.799> feature<00:19:35.160> or<00:19:35.580> a<00:19:35.700> bug<00:19:36.020> one<00:19:37.020> thing<00:19:37.140> that 00:19:37.310 --> 00:19:37.320 align:start position:0% either a feature or a bug one thing that 00:19:37.320 --> 00:19:40.789 align:start position:0% either a feature or a bug one thing that I<00:19:37.440> would<00:19:37.559> consider<00:19:37.919> a<00:19:38.100> bug<00:19:38.280> is<00:19:39.120> if<00:19:39.720> when<00:19:40.260> I<00:19:40.500> go 00:19:40.789 --> 00:19:40.799 align:start position:0% I would consider a bug is if when I go 00:19:40.799 --> 00:19:42.830 align:start position:0% I would consider a bug is if when I go to<00:19:40.980> create<00:19:41.340> a<00:19:41.700> listing 00:19:42.830 --> 00:19:42.840 align:start position:0% to create a listing 00:19:42.840 --> 00:19:45.529 align:start position:0% to create a listing the<00:19:43.320> royalty<00:19:43.740> is<00:19:43.919> five<00:19:44.160> percent<00:19:44.400> and<00:19:45.299> I'm<00:19:45.419> like 00:19:45.529 --> 00:19:45.539 align:start position:0% the royalty is five percent and I'm like 00:19:45.539 --> 00:19:47.630 align:start position:0% the royalty is five percent and I'm like okay<00:19:45.720> I<00:19:46.320> sign<00:19:46.559> my<00:19:46.799> listing 00:19:47.630 --> 00:19:47.640 align:start position:0% okay I sign my listing 00:19:47.640 --> 00:19:49.970 align:start position:0% okay I sign my listing now<00:19:48.240> the<00:19:48.539> Creator<00:19:48.780> goes<00:19:49.140> and<00:19:49.200> changes<00:19:49.559> that<00:19:49.799> to 00:19:49.970 --> 00:19:49.980 align:start position:0% now the Creator goes and changes that to 00:19:49.980 --> 00:19:50.770 align:start position:0% now the Creator goes and changes that to 50 00:19:50.770 --> 00:19:50.780 align:start position:0% 50 00:19:50.780 --> 00:19:53.210 align:start position:0% 50 that's<00:19:51.780> a<00:19:52.020> problem<00:19:52.260> and<00:19:52.559> I<00:19:52.740> might<00:19:52.860> not<00:19:52.980> have 00:19:53.210 --> 00:19:53.220 align:start position:0% that's a problem and I might not have 00:19:53.220 --> 00:19:54.650 align:start position:0% that's a problem and I might not have listed<00:19:53.640> it<00:19:53.760> if<00:19:53.940> I<00:19:54.059> knew<00:19:54.240> that<00:19:54.360> I<00:19:54.480> was<00:19:54.539> gonna 00:19:54.650 --> 00:19:54.660 align:start position:0% listed it if I knew that I was gonna 00:19:54.660 --> 00:19:56.750 align:start position:0% listed it if I knew that I was gonna have<00:19:54.780> to<00:19:54.900> pay<00:19:55.020> that<00:19:55.200> right 00:19:56.750 --> 00:19:56.760 align:start position:0% have to pay that right 00:19:56.760 --> 00:19:59.630 align:start position:0% have to pay that right then<00:19:57.360> there's<00:19:58.020> also<00:19:58.260> the<00:19:58.440> question<00:19:58.620> of<00:19:59.100> well 00:19:59.630 --> 00:19:59.640 align:start position:0% then there's also the question of well 00:19:59.640 --> 00:20:01.549 align:start position:0% then there's also the question of well what<00:19:59.880> if<00:20:00.000> they<00:20:00.179> just<00:20:00.360> want<00:20:00.539> to<00:20:00.720> tweak<00:20:01.380> the 00:20:01.549 --> 00:20:01.559 align:start position:0% what if they just want to tweak the 00:20:01.559 --> 00:20:02.990 align:start position:0% what if they just want to tweak the recipient<00:20:01.980> of<00:20:02.220> the<00:20:02.340> royalty<00:20:02.700> or<00:20:02.820> something 00:20:02.990 --> 00:20:03.000 align:start position:0% recipient of the royalty or something 00:20:03.000 --> 00:20:05.930 align:start position:0% recipient of the royalty or something like<00:20:03.360> that<00:20:03.539> for<00:20:04.380> those<00:20:04.620> cases<00:20:05.100> you<00:20:05.820> can 00:20:05.930 --> 00:20:05.940 align:start position:0% like that for those cases you can 00:20:05.940 --> 00:20:07.010 align:start position:0% like that for those cases you can Leverage 00:20:07.010 --> 00:20:07.020 align:start position:0% Leverage 00:20:07.020 --> 00:20:09.409 align:start position:0% Leverage tipping<00:20:07.799> right<00:20:08.160> so<00:20:08.640> I<00:20:08.820> mentioned<00:20:09.059> earlier 00:20:09.409 --> 00:20:09.419 align:start position:0% tipping right so I mentioned earlier 00:20:09.419 --> 00:20:11.990 align:start position:0% tipping right so I mentioned earlier that<00:20:09.660> you<00:20:09.840> can<00:20:09.960> always<00:20:10.200> add<00:20:10.740> additional 00:20:11.990 --> 00:20:12.000 align:start position:0% that you can always add additional 00:20:12.000 --> 00:20:14.570 align:start position:0% that you can always add additional items<00:20:12.660> to<00:20:12.840> the<00:20:13.020> consideration<00:20:13.500> array<00:20:14.340> you 00:20:14.570 --> 00:20:14.580 align:start position:0% items to the consideration array you 00:20:14.580 --> 00:20:16.190 align:start position:0% items to the consideration array you can't<00:20:14.700> add<00:20:14.940> them<00:20:15.059> to<00:20:15.179> the<00:20:15.299> offer<00:20:15.660> right<00:20:15.840> you 00:20:16.190 --> 00:20:16.200 align:start position:0% can't add them to the offer right you 00:20:16.200 --> 00:20:18.409 align:start position:0% can't add them to the offer right you can't<00:20:16.400> decide<00:20:17.400> that<00:20:17.640> the<00:20:17.760> offerer<00:20:18.179> is<00:20:18.299> going 00:20:18.409 --> 00:20:18.419 align:start position:0% can't decide that the offerer is going 00:20:18.419 --> 00:20:19.610 align:start position:0% can't decide that the offerer is going to<00:20:18.480> spend<00:20:18.660> more<00:20:18.780> than<00:20:19.020> they<00:20:19.260> originally 00:20:19.610 --> 00:20:19.620 align:start position:0% to spend more than they originally 00:20:19.620 --> 00:20:22.010 align:start position:0% to spend more than they originally agreed<00:20:19.980> to<00:20:20.100> that's<00:20:20.460> that's<00:20:21.240> a<00:20:21.539> very<00:20:21.660> important 00:20:22.010 --> 00:20:22.020 align:start position:0% agreed to that's that's a very important 00:20:22.020 --> 00:20:24.409 align:start position:0% agreed to that's that's a very important and<00:20:22.140> variant<00:20:22.440> not<00:20:22.620> to<00:20:22.799> break<00:20:22.980> but 00:20:24.409 --> 00:20:24.419 align:start position:0% and variant not to break but 00:20:24.419 --> 00:20:26.690 align:start position:0% and variant not to break but um<00:20:24.480> you<00:20:24.780> can<00:20:24.840> always<00:20:25.020> say<00:20:25.320> oh<00:20:25.500> yeah<00:20:25.740> I'll<00:20:25.980> I'll 00:20:26.690 --> 00:20:26.700 align:start position:0% um you can always say oh yeah I'll I'll 00:20:26.700 --> 00:20:28.549 align:start position:0% um you can always say oh yeah I'll I'll give<00:20:26.940> out<00:20:27.059> something<00:20:27.299> extra 00:20:28.549 --> 00:20:28.559 align:start position:0% give out something extra 00:20:28.559 --> 00:20:32.150 align:start position:0% give out something extra you<00:20:29.100> combine<00:20:29.400> that<00:20:29.840> with<00:20:30.840> call<00:20:31.320> it<00:20:31.559> a<00:20:31.799> a 00:20:32.150 --> 00:20:32.160 align:start position:0% you combine that with call it a a 00:20:32.160 --> 00:20:36.169 align:start position:0% you combine that with call it a a royalty<00:20:32.700> Zone<00:20:33.380> the<00:20:34.380> royalty<00:20:34.679> Zone<00:20:34.860> will<00:20:35.100> go<00:20:35.280> it 00:20:36.169 --> 00:20:36.179 align:start position:0% royalty Zone the royalty Zone will go it 00:20:36.179 --> 00:20:38.930 align:start position:0% royalty Zone the royalty Zone will go it will<00:20:36.360> read<00:20:36.780> from<00:20:37.200> in<00:20:38.039> real<00:20:38.160> time<00:20:38.400> from<00:20:38.760> the 00:20:38.930 --> 00:20:38.940 align:start position:0% will read from in real time from the 00:20:38.940 --> 00:20:40.370 align:start position:0% will read from in real time from the registry 00:20:40.370 --> 00:20:40.380 align:start position:0% registry 00:20:40.380 --> 00:20:43.730 align:start position:0% registry and<00:20:41.220> ensure<00:20:41.820> that<00:20:42.120> the<00:20:42.600> last<00:20:42.840> consideration 00:20:43.730 --> 00:20:43.740 align:start position:0% and ensure that the last consideration 00:20:43.740 --> 00:20:46.610 align:start position:0% and ensure that the last consideration item<00:20:44.100> this<00:20:44.280> tip<00:20:44.660> matches<00:20:45.660> what<00:20:46.140> the<00:20:46.260> registry 00:20:46.610 --> 00:20:46.620 align:start position:0% item this tip matches what the registry 00:20:46.620 --> 00:20:48.049 align:start position:0% item this tip matches what the registry has<00:20:46.919> on<00:20:47.160> file 00:20:48.049 --> 00:20:48.059 align:start position:0% has on file 00:20:48.059 --> 00:20:50.029 align:start position:0% has on file so<00:20:48.480> then<00:20:48.660> the<00:20:49.260> only<00:20:49.440> way<00:20:49.620> you're<00:20:49.740> going<00:20:49.860> to<00:20:49.860> be 00:20:50.029 --> 00:20:50.039 align:start position:0% so then the only way you're going to be 00:20:50.039 --> 00:20:52.190 align:start position:0% so then the only way you're going to be able<00:20:50.100> to<00:20:50.220> fulfill<00:20:50.520> it<00:20:50.700> is<00:20:51.360> to<00:20:51.600> supply<00:20:51.840> the 00:20:52.190 --> 00:20:52.200 align:start position:0% able to fulfill it is to supply the 00:20:52.200 --> 00:20:54.890 align:start position:0% able to fulfill it is to supply the correct<00:20:52.559> updated<00:20:53.039> information 00:20:54.890 --> 00:20:54.900 align:start position:0% correct updated information 00:20:54.900 --> 00:20:58.430 align:start position:0% correct updated information that's<00:20:55.320> sort<00:20:55.500> of<00:20:55.620> the<00:20:55.740> gist<00:20:56.280> cool<00:20:57.179> thank<00:20:57.539> you 00:20:58.430 --> 00:20:58.440 align:start position:0% that's sort of the gist cool thank you 00:20:58.440 --> 00:20:59.990 align:start position:0% that's sort of the gist cool thank you cool 00:20:59.990 --> 00:21:00.000 align:start position:0% cool 00:21:00.000 --> 00:21:03.529 align:start position:0% cool yes 00:21:03.529 --> 00:21:03.539 align:start position:0% 00:21:03.539 --> 00:21:05.270 align:start position:0% I<00:21:04.200> have<00:21:04.380> a<00:21:04.500> question<00:21:04.620> about<00:21:04.860> one<00:21:05.100> of<00:21:05.220> your 00:21:05.270 --> 00:21:05.280 align:start position:0% I have a question about one of your 00:21:05.280 --> 00:21:07.190 align:start position:0% I have a question about one of your earlier<00:21:05.520> slides<00:21:05.880> so<00:21:06.059> you<00:21:06.240> on<00:21:06.600> the<00:21:06.780> matching 00:21:07.190 --> 00:21:07.200 align:start position:0% earlier slides so you on the matching 00:21:07.200 --> 00:21:09.529 align:start position:0% earlier slides so you on the matching orders<00:21:07.620> slide<00:21:08.100> you<00:21:08.460> have<00:21:08.640> this<00:21:09.000> statement 00:21:09.529 --> 00:21:09.539 align:start position:0% orders slide you have this statement 00:21:09.539 --> 00:21:10.549 align:start position:0% orders slide you have this statement which<00:21:09.720> you<00:21:09.840> wrote<00:21:09.960> something<00:21:10.140> along<00:21:10.320> the 00:21:10.549 --> 00:21:10.559 align:start position:0% which you wrote something along the 00:21:10.559 --> 00:21:12.830 align:start position:0% which you wrote something along the lines<00:21:10.679> of<00:21:10.799> like<00:21:11.100> if<00:21:11.940> a<00:21:12.059> Searcher<00:21:12.419> identifies 00:21:12.830 --> 00:21:12.840 align:start position:0% lines of like if a Searcher identifies 00:21:12.840 --> 00:21:14.870 align:start position:0% lines of like if a Searcher identifies an<00:21:13.080> opportunity<00:21:13.559> there<00:21:14.100> it<00:21:14.280> is<00:21:14.400> so<00:21:14.580> search 00:21:14.870 --> 00:21:14.880 align:start position:0% an opportunity there it is so search 00:21:14.880 --> 00:21:16.070 align:start position:0% an opportunity there it is so search your<00:21:15.059> identifies<00:21:15.419> an<00:21:15.600> opportunity<00:21:15.840> you<00:21:15.960> can 00:21:16.070 --> 00:21:16.080 align:start position:0% your identifies an opportunity you can 00:21:16.080 --> 00:21:17.630 align:start position:0% your identifies an opportunity you can take<00:21:16.140> whatever<00:21:16.320> leftover<00:21:16.740> item<00:21:17.220> amounts<00:21:17.520> and 00:21:17.630 --> 00:21:17.640 align:start position:0% take whatever leftover item amounts and 00:21:17.640 --> 00:21:19.070 align:start position:0% take whatever leftover item amounts and match<00:21:17.820> them<00:21:18.059> to<00:21:18.179> a<00:21:18.299> new<00:21:18.419> consideration<00:21:18.780> item 00:21:19.070 --> 00:21:19.080 align:start position:0% match them to a new consideration item 00:21:19.080 --> 00:21:21.830 align:start position:0% match them to a new consideration item to<00:21:19.200> itself<00:21:19.820> so<00:21:20.820> I'm<00:21:21.120> a<00:21:21.240> little<00:21:21.299> confused 00:21:21.830 --> 00:21:21.840 align:start position:0% to itself so I'm a little confused 00:21:21.840 --> 00:21:23.570 align:start position:0% to itself so I'm a little confused because<00:21:22.200> my<00:21:22.980> understanding<00:21:23.280> of<00:21:23.460> the 00:21:23.570 --> 00:21:23.580 align:start position:0% because my understanding of the 00:21:23.580 --> 00:21:26.690 align:start position:0% because my understanding of the architecture<00:21:24.059> is<00:21:24.240> that<00:21:24.860> in<00:21:25.860> every<00:21:26.280> single 00:21:26.690 --> 00:21:26.700 align:start position:0% architecture is that in every single 00:21:26.700 --> 00:21:30.770 align:start position:0% architecture is that in every single type<00:21:27.480> of<00:21:27.840> order<00:21:28.140> or<00:21:28.679> function<00:21:29.039> call<00:21:29.220> you<00:21:29.460> make 00:21:30.770 --> 00:21:30.780 align:start position:0% type of order or function call you make 00:21:30.780 --> 00:21:33.830 align:start position:0% type of order or function call you make all<00:21:31.559> considerations<00:21:32.100> have<00:21:32.460> to<00:21:32.580> be<00:21:32.700> met<00:21:32.940> on<00:21:33.780> the 00:21:33.830 --> 00:21:33.840 align:start position:0% all considerations have to be met on the 00:21:33.840 --> 00:21:35.990 align:start position:0% all considerations have to be met on the other<00:21:33.960> side<00:21:34.200> so<00:21:34.919> I'm<00:21:35.039> a<00:21:35.220> little<00:21:35.280> confused<00:21:35.700> how 00:21:35.990 --> 00:21:36.000 align:start position:0% other side so I'm a little confused how 00:21:36.000 --> 00:21:40.010 align:start position:0% other side so I'm a little confused how like<00:21:36.419> like<00:21:36.480> in<00:21:37.380> the<00:21:37.500> in<00:21:37.679> the<00:21:37.860> case<00:21:37.980> of<00:21:38.220> like<00:21:39.020> the 00:21:40.010 --> 00:21:40.020 align:start position:0% like like in the in the case of like the 00:21:40.020 --> 00:21:42.830 align:start position:0% like like in the in the case of like the classic<00:21:40.140> case<00:21:40.440> of<00:21:40.620> Arbitrage<00:21:41.039> right<00:21:41.280> like 00:21:42.830 --> 00:21:42.840 align:start position:0% classic case of Arbitrage right like 00:21:42.840 --> 00:21:44.510 align:start position:0% classic case of Arbitrage right like there<00:21:43.200> has<00:21:43.380> to<00:21:43.440> be<00:21:43.559> an<00:21:43.679> opportunity<00:21:44.039> on<00:21:44.400> the 00:21:44.510 --> 00:21:44.520 align:start position:0% there has to be an opportunity on the 00:21:44.520 --> 00:21:46.669 align:start position:0% there has to be an opportunity on the table<00:21:44.640> for<00:21:44.880> the<00:21:45.000> arbitrager<00:21:45.539> to<00:21:45.720> take<00:21:45.900> and 00:21:46.669 --> 00:21:46.679 align:start position:0% table for the arbitrager to take and 00:21:46.679 --> 00:21:49.909 align:start position:0% table for the arbitrager to take and it's<00:21:46.860> not<00:21:47.280> clear<00:21:47.460> to<00:21:47.700> me<00:21:47.960> what<00:21:48.960> this<00:21:49.260> means<00:21:49.559> for 00:21:49.909 --> 00:21:49.919 align:start position:0% it's not clear to me what this means for 00:21:49.919 --> 00:21:52.190 align:start position:0% it's not clear to me what this means for for<00:21:50.340> an<00:21:50.760> opportunity<00:21:51.179> if<00:21:51.539> the<00:21:51.780> considerations 00:21:52.190 --> 00:21:52.200 align:start position:0% for an opportunity if the considerations 00:21:52.200 --> 00:21:54.529 align:start position:0% for an opportunity if the considerations are<00:21:52.500> always<00:21:52.820> evened<00:21:53.820> out 00:21:54.529 --> 00:21:54.539 align:start position:0% are always evened out 00:21:54.539 --> 00:21:57.770 align:start position:0% are always evened out or<00:21:55.020> yeah<00:21:55.440> it's<00:21:56.280> a<00:21:56.460> great<00:21:56.640> question<00:21:56.820> and<00:21:57.179> this 00:21:57.770 --> 00:21:57.780 align:start position:0% or yeah it's a great question and this 00:21:57.780 --> 00:21:59.870 align:start position:0% or yeah it's a great question and this is<00:21:57.960> actually<00:21:58.140> a<00:21:58.500> good<00:21:58.679> a<00:21:59.039> good<00:21:59.280> opportunity<00:21:59.640> to 00:21:59.870 --> 00:21:59.880 align:start position:0% is actually a good a good opportunity to 00:21:59.880 --> 00:22:02.210 align:start position:0% is actually a good a good opportunity to get<00:22:00.059> into<00:22:00.179> just<00:22:00.600> the<00:22:00.900> the<00:22:01.140> nitty-gritty<00:22:01.860> on 00:22:02.210 --> 00:22:02.220 align:start position:0% get into just the the nitty-gritty on 00:22:02.220 --> 00:22:04.149 align:start position:0% get into just the the nitty-gritty on how<00:22:02.460> this<00:22:02.700> would<00:22:02.880> look<00:22:03.059> let's<00:22:03.299> just<00:22:03.539> consider 00:22:04.149 --> 00:22:04.159 align:start position:0% how this would look let's just consider 00:22:04.159 --> 00:22:08.270 align:start position:0% how this would look let's just consider a<00:22:05.159> really<00:22:05.880> simple<00:22:06.120> stripped<00:22:06.780> down<00:22:06.900> case<00:22:07.280> where 00:22:08.270 --> 00:22:08.280 align:start position:0% a really simple stripped down case where 00:22:08.280 --> 00:22:09.409 align:start position:0% a really simple stripped down case where you<00:22:08.580> have 00:22:09.409 --> 00:22:09.419 align:start position:0% you have 00:22:09.419 --> 00:22:12.649 align:start position:0% you have one<00:22:10.320> listing<00:22:10.919> so<00:22:11.760> the<00:22:12.000> way<00:22:12.120> this<00:22:12.299> might<00:22:12.480> look 00:22:12.649 --> 00:22:12.659 align:start position:0% one listing so the way this might look 00:22:12.659 --> 00:22:17.950 align:start position:0% one listing so the way this might look is<00:22:12.960> I<00:22:13.500> want<00:22:13.620> to<00:22:13.740> sell<00:22:13.919> my<00:22:14.100> nft<00:22:14.400> right<00:22:15.440> so<00:22:16.440> I<00:22:17.159> have 00:22:17.950 --> 00:22:17.960 align:start position:0% is I want to sell my nft right so I have 00:22:17.960 --> 00:22:22.070 align:start position:0% is I want to sell my nft right so I have one<00:22:18.960> offer<00:22:19.500> item<00:22:19.860> Which<00:22:20.400> is<00:22:20.520> my<00:22:20.760> nft 00:22:22.070 --> 00:22:22.080 align:start position:0% one offer item Which is my nft 00:22:22.080 --> 00:22:25.090 align:start position:0% one offer item Which is my nft and<00:22:22.679> one<00:22:22.980> consideration<00:22:23.700> item<00:22:24.120> we'll<00:22:24.480> call<00:22:24.720> it 00:22:25.090 --> 00:22:25.100 align:start position:0% and one consideration item we'll call it 00:22:25.100 --> 00:22:28.610 align:start position:0% and one consideration item we'll call it five<00:22:26.100> what<00:22:26.580> okay 00:22:28.610 --> 00:22:28.620 align:start position:0% five what okay 00:22:28.620 --> 00:22:32.270 align:start position:0% five what okay with<00:22:29.220> the<00:22:29.340> recipient<00:22:29.760> being<00:22:30.179> me<00:22:31.140> the<00:22:31.799> offerer 00:22:32.270 --> 00:22:32.280 align:start position:0% with the recipient being me the offerer 00:22:32.280 --> 00:22:36.649 align:start position:0% with the recipient being me the offerer right<00:22:32.960> now<00:22:33.960> someone<00:22:34.260> else<00:22:34.620> likes<00:22:35.460> my<00:22:35.580> nft 00:22:36.649 --> 00:22:36.659 align:start position:0% right now someone else likes my nft 00:22:36.659 --> 00:22:38.570 align:start position:0% right now someone else likes my nft they<00:22:37.140> don't<00:22:37.320> realize<00:22:37.679> that<00:22:38.100> I've<00:22:38.400> already 00:22:38.570 --> 00:22:38.580 align:start position:0% they don't realize that I've already 00:22:38.580 --> 00:22:41.270 align:start position:0% they don't realize that I've already listed<00:22:38.940> it<00:22:39.059> for<00:22:39.179> five<00:22:39.360> what<00:22:39.659> okay 00:22:41.270 --> 00:22:41.280 align:start position:0% listed it for five what okay 00:22:41.280 --> 00:22:45.470 align:start position:0% listed it for five what okay they<00:22:42.179> put<00:22:42.539> out<00:22:42.720> an<00:22:43.320> offer<00:22:43.679> a<00:22:44.220> bid<00:22:44.880> on<00:22:45.120> the<00:22:45.240> nft 00:22:45.470 --> 00:22:45.480 align:start position:0% they put out an offer a bid on the nft 00:22:45.480 --> 00:22:47.149 align:start position:0% they put out an offer a bid on the nft to<00:22:45.960> buy<00:22:46.140> it 00:22:47.149 --> 00:22:47.159 align:start position:0% to buy it 00:22:47.159 --> 00:22:51.169 align:start position:0% to buy it and<00:22:48.000> they<00:22:48.720> offer<00:22:49.020> six<00:22:49.260> web<00:22:49.500> so<00:22:50.400> the<00:22:51.059> weight 00:22:51.169 --> 00:22:51.179 align:start position:0% and they offer six web so the weight 00:22:51.179 --> 00:22:53.149 align:start position:0% and they offer six web so the weight would<00:22:51.360> look<00:22:51.480> for<00:22:51.659> them<00:22:51.780> is 00:22:53.149 --> 00:22:53.159 align:start position:0% would look for them is 00:22:53.159 --> 00:22:55.010 align:start position:0% would look for them is I'm<00:22:53.760> offering 00:22:55.010 --> 00:22:55.020 align:start position:0% I'm offering 00:22:55.020 --> 00:22:58.130 align:start position:0% I'm offering six<00:22:55.559> weft<00:22:55.980> one<00:22:56.580> offer<00:22:57.120> item 00:22:58.130 --> 00:22:58.140 align:start position:0% six weft one offer item 00:22:58.140 --> 00:23:00.950 align:start position:0% six weft one offer item one<00:22:58.679> consideration<00:22:59.280> item<00:22:59.760> this<00:23:00.600> nft 00:23:00.950 --> 00:23:00.960 align:start position:0% one consideration item this nft 00:23:00.960 --> 00:23:05.029 align:start position:0% one consideration item this nft recipient<00:23:01.860> is<00:23:02.340> me<00:23:02.580> so<00:23:03.539> now 00:23:05.029 --> 00:23:05.039 align:start position:0% recipient is me so now 00:23:05.039 --> 00:23:07.070 align:start position:0% recipient is me so now person<00:23:05.460> number<00:23:05.820> three<00:23:06.059> Searcher<00:23:06.659> comes<00:23:06.960> along 00:23:07.070 --> 00:23:07.080 align:start position:0% person number three Searcher comes along 00:23:07.080 --> 00:23:09.890 align:start position:0% person number three Searcher comes along and<00:23:07.559> realizes<00:23:08.220> that<00:23:08.520> there's<00:23:08.700> this<00:23:09.179> uh 00:23:09.890 --> 00:23:09.900 align:start position:0% and realizes that there's this uh 00:23:09.900 --> 00:23:11.810 align:start position:0% and realizes that there's this uh mismatch 00:23:11.810 --> 00:23:11.820 align:start position:0% mismatch 00:23:11.820 --> 00:23:14.930 align:start position:0% mismatch they<00:23:12.360> call<00:23:12.539> match<00:23:12.840> orders<00:23:13.260> they<00:23:13.679> Supply<00:23:13.940> both 00:23:14.930 --> 00:23:14.940 align:start position:0% they call match orders they Supply both 00:23:14.940 --> 00:23:18.409 align:start position:0% they call match orders they Supply both of<00:23:15.120> these<00:23:15.419> orders<00:23:16.100> and<00:23:17.100> they<00:23:17.400> give<00:23:17.700> a 00:23:18.409 --> 00:23:18.419 align:start position:0% of these orders and they give a 00:23:18.419 --> 00:23:19.430 align:start position:0% of these orders and they give a fulfillment 00:23:19.430 --> 00:23:19.440 align:start position:0% fulfillment 00:23:19.440 --> 00:23:24.710 align:start position:0% fulfillment saying<00:23:20.220> Okay<00:23:20.460> order<00:23:21.120> zero<00:23:22.200> item<00:23:23.100> zero<00:23:23.700> is<00:23:24.360> the 00:23:24.710 --> 00:23:24.720 align:start position:0% saying Okay order zero item zero is the 00:23:24.720 --> 00:23:25.730 align:start position:0% saying Okay order zero item zero is the nft 00:23:25.730 --> 00:23:25.740 align:start position:0% nft 00:23:25.740 --> 00:23:30.049 align:start position:0% nft order<00:23:26.400> one<00:23:27.380> item<00:23:28.380> zero<00:23:29.159> on<00:23:29.340> the<00:23:29.520> consideration 00:23:30.049 --> 00:23:30.059 align:start position:0% order one item zero on the consideration 00:23:30.059 --> 00:23:33.890 align:start position:0% order one item zero on the consideration side<00:23:30.500> is<00:23:31.500> also<00:23:31.740> the<00:23:31.860> nft<00:23:32.159> these<00:23:32.880> match<00:23:33.120> that 00:23:33.890 --> 00:23:33.900 align:start position:0% side is also the nft these match that 00:23:33.900 --> 00:23:36.590 align:start position:0% side is also the nft these match that turns<00:23:34.320> into<00:23:34.440> a<00:23:34.740> single<00:23:35.100> transfer<00:23:35.580> from<00:23:36.360> the 00:23:36.590 --> 00:23:36.600 align:start position:0% turns into a single transfer from the 00:23:36.600 --> 00:23:41.690 align:start position:0% turns into a single transfer from the offerer<00:23:37.140> A<00:23:38.179> to<00:23:39.200> offerer<00:23:40.200> B<00:23:40.400> then<00:23:41.400> we<00:23:41.580> do 00:23:41.690 --> 00:23:41.700 align:start position:0% offerer A to offerer B then we do 00:23:41.700 --> 00:23:46.250 align:start position:0% offerer A to offerer B then we do another<00:23:42.299> match<00:23:43.140> fulfillment<00:23:44.100> order<00:23:45.059> zero 00:23:46.250 --> 00:23:46.260 align:start position:0% another match fulfillment order zero 00:23:46.260 --> 00:23:51.409 align:start position:0% another match fulfillment order zero item<00:23:47.179> I'm<00:23:48.179> sorry<00:23:48.360> order<00:23:48.780> one<00:23:49.380> item<00:23:49.919> zero<00:23:50.460> which 00:23:51.409 --> 00:23:51.419 align:start position:0% item I'm sorry order one item zero which 00:23:51.419 --> 00:23:54.289 align:start position:0% item I'm sorry order one item zero which is<00:23:51.740> the<00:23:52.740> six<00:23:53.280> weft 00:23:54.289 --> 00:23:54.299 align:start position:0% is the six weft 00:23:54.299 --> 00:23:57.230 align:start position:0% is the six weft order<00:23:54.960> 0<00:23:55.380> item<00:23:56.220> zero<00:23:56.520> on<00:23:56.640> the<00:23:56.760> consideration 00:23:57.230 --> 00:23:57.240 align:start position:0% order 0 item zero on the consideration 00:23:57.240 --> 00:24:00.409 align:start position:0% order 0 item zero on the consideration side<00:23:57.539> is<00:23:57.900> the<00:23:58.260> the<00:23:58.440> five<00:23:58.740> width<00:23:59.220> those<00:24:00.120> now 00:24:00.409 --> 00:24:00.419 align:start position:0% side is the the five width those now 00:24:00.419 --> 00:24:02.149 align:start position:0% side is the the five width those now match 00:24:02.149 --> 00:24:02.159 align:start position:0% match 00:24:02.159 --> 00:24:04.789 align:start position:0% match the<00:24:02.700> way<00:24:02.820> that<00:24:03.059> this<00:24:03.360> works<00:24:03.840> now<00:24:04.020> is<00:24:04.320> that<00:24:04.559> they 00:24:04.789 --> 00:24:04.799 align:start position:0% the way that this works now is that they 00:24:04.799 --> 00:24:08.390 align:start position:0% the way that this works now is that they get<00:24:05.039> the<00:24:05.880> the<00:24:06.120> five<00:24:06.360> weft<00:24:06.900> gets<00:24:07.380> credited<00:24:07.919> okay 00:24:08.390 --> 00:24:08.400 align:start position:0% get the the five weft gets credited okay 00:24:08.400 --> 00:24:12.549 align:start position:0% get the the five weft gets credited okay that's<00:24:08.700> been<00:24:09.000> accounted<00:24:09.960> for<00:24:10.340> the<00:24:11.340> six<00:24:11.640> weth 00:24:12.549 --> 00:24:12.559 align:start position:0% that's been accounted for the six weth 00:24:12.559 --> 00:24:17.330 align:start position:0% that's been accounted for the six weth gets<00:24:13.559> spent<00:24:13.919> there's<00:24:14.880> one<00:24:15.360> wealth<00:24:15.900> left 00:24:17.330 --> 00:24:17.340 align:start position:0% gets spent there's one wealth left 00:24:17.340 --> 00:24:20.029 align:start position:0% gets spent there's one wealth left you<00:24:17.880> can<00:24:18.000> actually<00:24:18.299> leave 00:24:20.029 --> 00:24:20.039 align:start position:0% you can actually leave 00:24:20.039 --> 00:24:23.029 align:start position:0% you can actually leave offer<00:24:20.820> item<00:24:21.120> amounts<00:24:21.480> on<00:24:21.780> the<00:24:21.900> table<00:24:22.080> there's 00:24:23.029 --> 00:24:23.039 align:start position:0% offer item amounts on the table there's 00:24:23.039 --> 00:24:24.830 align:start position:0% offer item amounts on the table there's not<00:24:23.280> there's<00:24:23.580> not<00:24:23.760> a<00:24:23.940> reason<00:24:24.059> that<00:24:24.360> you<00:24:24.600> have 00:24:24.830 --> 00:24:24.840 align:start position:0% not there's not a reason that you have 00:24:24.840 --> 00:24:28.130 align:start position:0% not there's not a reason that you have to<00:24:25.020> spend<00:24:25.380> all<00:24:26.159> of<00:24:26.340> the<00:24:26.520> offer<00:24:26.820> items<00:24:27.240> but<00:24:27.960> you 00:24:28.130 --> 00:24:28.140 align:start position:0% to spend all of the offer items but you 00:24:28.140 --> 00:24:29.990 align:start position:0% to spend all of the offer items but you do<00:24:28.320> have<00:24:28.500> to<00:24:28.679> credit<00:24:28.860> all<00:24:29.760> of<00:24:29.880> the 00:24:29.990 --> 00:24:30.000 align:start position:0% do have to credit all of the 00:24:30.000 --> 00:24:31.430 align:start position:0% do have to credit all of the consideration<00:24:30.419> items<00:24:30.780> so<00:24:30.900> we<00:24:31.020> could<00:24:31.080> leave<00:24:31.260> it 00:24:31.430 --> 00:24:31.440 align:start position:0% consideration items so we could leave it 00:24:31.440 --> 00:24:33.250 align:start position:0% consideration items so we could leave it at<00:24:31.620> that<00:24:31.740> you<00:24:31.980> could<00:24:32.159> match<00:24:32.400> those<00:24:32.700> two<00:24:32.820> orders 00:24:33.250 --> 00:24:33.260 align:start position:0% at that you could match those two orders 00:24:33.260 --> 00:24:37.549 align:start position:0% at that you could match those two orders and<00:24:34.260> the<00:24:34.620> original<00:24:34.740> or<00:24:35.640> the<00:24:35.880> the<00:24:36.539> order<00:24:37.140> be<00:24:37.380> the 00:24:37.549 --> 00:24:37.559 align:start position:0% and the original or the the order be the 00:24:37.559 --> 00:24:39.230 align:start position:0% and the original or the the order be the person<00:24:37.919> that<00:24:38.100> made<00:24:38.280> the<00:24:38.400> bid 00:24:39.230 --> 00:24:39.240 align:start position:0% person that made the bid 00:24:39.240 --> 00:24:41.690 align:start position:0% person that made the bid just<00:24:39.780> end<00:24:39.960> up<00:24:40.080> paying<00:24:40.440> five 00:24:41.690 --> 00:24:41.700 align:start position:0% just end up paying five 00:24:41.700 --> 00:24:44.930 align:start position:0% just end up paying five but<00:24:42.299> what<00:24:42.840> would<00:24:43.080> in<00:24:43.860> practice<00:24:44.400> what<00:24:44.760> would 00:24:44.930 --> 00:24:44.940 align:start position:0% but what would in practice what would 00:24:44.940 --> 00:24:48.529 align:start position:0% but what would in practice what would happen<00:24:45.059> is<00:24:45.659> that<00:24:47.100> this<00:24:47.640> the<00:24:48.059> person<00:24:48.299> who 00:24:48.529 --> 00:24:48.539 align:start position:0% happen is that this the person who 00:24:48.539 --> 00:24:50.750 align:start position:0% happen is that this the person who located<00:24:48.780> the<00:24:49.140> opportunity<00:24:49.500> might<00:24:49.860> say<00:24:50.159> I'm 00:24:50.750 --> 00:24:50.760 align:start position:0% located the opportunity might say I'm 00:24:50.760 --> 00:24:53.930 align:start position:0% located the opportunity might say I'm going<00:24:50.940> to<00:24:51.000> create<00:24:51.179> a<00:24:51.600> third<00:24:52.080> order<00:24:52.820> and<00:24:53.820> this 00:24:53.930 --> 00:24:53.940 align:start position:0% going to create a third order and this 00:24:53.940 --> 00:24:56.690 align:start position:0% going to create a third order and this third<00:24:54.179> order<00:24:54.360> I'm<00:24:55.320> offering<00:24:55.740> nothing 00:24:56.690 --> 00:24:56.700 align:start position:0% third order I'm offering nothing 00:24:56.700 --> 00:24:58.730 align:start position:0% third order I'm offering nothing it's<00:24:57.000> an<00:24:57.240> empty<00:24:57.600> array 00:24:58.730 --> 00:24:58.740 align:start position:0% it's an empty array 00:24:58.740 --> 00:25:02.090 align:start position:0% it's an empty array consideration<00:24:59.580> item<00:25:00.059> one<00:25:00.720> with 00:25:02.090 --> 00:25:02.100 align:start position:0% consideration item one with 00:25:02.100 --> 00:25:03.770 align:start position:0% consideration item one with recipient<00:25:02.760> is<00:25:03.000> me 00:25:03.770 --> 00:25:03.780 align:start position:0% recipient is me 00:25:03.780 --> 00:25:06.110 align:start position:0% recipient is me and<00:25:04.080> then<00:25:04.200> they<00:25:04.320> create<00:25:04.500> another<00:25:04.740> fulfillment 00:25:06.110 --> 00:25:06.120 align:start position:0% and then they create another fulfillment 00:25:06.120 --> 00:25:10.909 align:start position:0% and then they create another fulfillment that<00:25:07.020> you<00:25:07.860> know<00:25:07.980> matches<00:25:08.820> the<00:25:09.240> the<00:25:09.740> same<00:25:10.740> one 00:25:10.909 --> 00:25:10.919 align:start position:0% that you know matches the the same one 00:25:10.919 --> 00:25:13.250 align:start position:0% that you know matches the the same one that<00:25:11.220> we've<00:25:11.580> just<00:25:11.700> spent<00:25:11.940> five<00:25:12.240> from<00:25:12.539> with<00:25:13.020> the 00:25:13.250 --> 00:25:13.260 align:start position:0% that we've just spent five from with the 00:25:13.260 --> 00:25:15.770 align:start position:0% that we've just spent five from with the new<00:25:13.440> one<00:25:13.620> you<00:25:14.159> don't<00:25:14.280> even<00:25:14.460> have<00:25:14.760> to<00:25:14.940> create<00:25:15.179> a 00:25:15.770 --> 00:25:15.780 align:start position:0% new one you don't even have to create a 00:25:15.780 --> 00:25:18.710 align:start position:0% new one you don't even have to create a new<00:25:15.900> order<00:25:16.080> you<00:25:16.500> can<00:25:16.620> also<00:25:16.860> just<00:25:17.520> add<00:25:18.120> on<00:25:18.299> a<00:25:18.480> tip 00:25:18.710 --> 00:25:18.720 align:start position:0% new order you can also just add on a tip 00:25:18.720 --> 00:25:20.990 align:start position:0% new order you can also just add on a tip to<00:25:19.140> order<00:25:19.679> b<00:25:19.980> or<00:25:20.220> whatever 00:25:20.990 --> 00:25:21.000 align:start position:0% to order b or whatever 00:25:21.000 --> 00:25:23.570 align:start position:0% to order b or whatever and<00:25:21.659> use<00:25:21.960> that<00:25:22.200> to<00:25:22.320> match<00:25:22.440> to 00:25:23.570 --> 00:25:23.580 align:start position:0% and use that to match to 00:25:23.580 --> 00:25:25.850 align:start position:0% and use that to match to so<00:25:23.820> that's<00:25:24.000> the<00:25:24.240> idea<00:25:24.539> there 00:25:25.850 --> 00:25:25.860 align:start position:0% so that's the idea there 00:25:25.860 --> 00:25:30.409 align:start position:0% so that's the idea there other<00:25:26.340> questions 00:25:30.409 --> 00:25:30.419 align:start position:0% 00:25:30.419 --> 00:25:31.970 align:start position:0% okay<00:25:30.840> thanks 00:25:31.970 --> 00:25:31.980 align:start position:0% okay thanks 00:25:31.980 --> 00:25:32.570 align:start position:0% okay thanks um 00:25:32.570 --> 00:25:32.580 align:start position:0% um 00:25:32.580 --> 00:25:34.789 align:start position:0% um so<00:25:33.240> I<00:25:33.480> haven't<00:25:33.600> built<00:25:33.960> anything<00:25:34.020> on<00:25:34.260> C4<00:25:34.559> but 00:25:34.789 --> 00:25:34.799 align:start position:0% so I haven't built anything on C4 but 00:25:34.799 --> 00:25:36.710 align:start position:0% so I haven't built anything on C4 but I've<00:25:34.919> looked<00:25:35.100> into<00:25:35.159> it<00:25:35.400> a<00:25:35.520> little<00:25:35.520> bit<00:25:35.700> uh<00:25:36.360> just 00:25:36.710 --> 00:25:36.720 align:start position:0% I've looked into it a little bit uh just 00:25:36.720 --> 00:25:38.090 align:start position:0% I've looked into it a little bit uh just wondering 00:25:38.090 --> 00:25:38.100 align:start position:0% wondering 00:25:38.100 --> 00:25:41.210 align:start position:0% wondering uh<00:25:38.760> does<00:25:39.000> it<00:25:39.179> support<00:25:39.419> like<00:25:40.080> natively<00:25:40.620> partial 00:25:41.210 --> 00:25:41.220 align:start position:0% uh does it support like natively partial 00:25:41.220 --> 00:25:43.850 align:start position:0% uh does it support like natively partial fill<00:25:41.460> orders<00:25:41.940> like<00:25:42.179> is<00:25:42.299> it<00:25:42.419> possible<00:25:42.860> yes 00:25:43.850 --> 00:25:43.860 align:start position:0% fill orders like is it possible yes 00:25:43.860 --> 00:25:45.649 align:start position:0% fill orders like is it possible yes single<00:25:44.340> sign<00:25:44.460> message<00:25:44.760> with<00:25:45.059> like<00:25:45.240> multiple 00:25:45.649 --> 00:25:45.659 align:start position:0% single sign message with like multiple 00:25:45.659 --> 00:25:48.710 align:start position:0% single sign message with like multiple fulfillments<00:25:46.440> yeah<00:25:47.220> I'll<00:25:48.059> get<00:25:48.240> into<00:25:48.419> that<00:25:48.600> a 00:25:48.710 --> 00:25:48.720 align:start position:0% fulfillments yeah I'll get into that a 00:25:48.720 --> 00:25:50.409 align:start position:0% fulfillments yeah I'll get into that a little<00:25:48.840> bit<00:25:48.960> so 00:25:50.409 --> 00:25:50.419 align:start position:0% little bit so 00:25:50.419 --> 00:25:53.350 align:start position:0% little bit so if<00:25:51.419> the<00:25:52.020> offerer 00:25:53.350 --> 00:25:53.360 align:start position:0% if the offerer 00:25:53.360 --> 00:25:57.470 align:start position:0% if the offerer elects<00:25:54.360> to<00:25:54.539> to<00:25:54.960> support<00:25:55.320> partial<00:25:56.159> fills 00:25:57.470 --> 00:25:57.480 align:start position:0% elects to to support partial fills 00:25:57.480 --> 00:25:59.810 align:start position:0% elects to to support partial fills it's<00:25:58.200> specified<00:25:58.799> in<00:25:59.100> the<00:25:59.220> order<00:25:59.279> type<00:25:59.520> just 00:25:59.810 --> 00:25:59.820 align:start position:0% it's specified in the order type just 00:25:59.820 --> 00:26:03.190 align:start position:0% it's specified in the order type just like<00:26:00.000> a<00:26:00.179> restricted<00:26:00.600> order<00:26:00.720> when<00:26:01.200> the<00:26:01.380> Zone<00:26:01.620> uh 00:26:03.190 --> 00:26:03.200 align:start position:0% like a restricted order when the Zone uh 00:26:03.200 --> 00:26:06.470 align:start position:0% like a restricted order when the Zone uh requires<00:26:04.200> that<00:26:04.380> so<00:26:04.980> if<00:26:05.279> an<00:26:05.460> order 00:26:06.470 --> 00:26:06.480 align:start position:0% requires that so if an order 00:26:06.480 --> 00:26:08.810 align:start position:0% requires that so if an order supports<00:26:07.260> partial<00:26:07.620> fills<00:26:08.039> the<00:26:08.279> way<00:26:08.400> that<00:26:08.580> this 00:26:08.810 --> 00:26:08.820 align:start position:0% supports partial fills the way that this 00:26:08.820 --> 00:26:13.789 align:start position:0% supports partial fills the way that this works<00:26:09.679> is<00:26:10.679> that<00:26:10.980> you<00:26:11.400> can<00:26:11.580> supply<00:26:12.419> when<00:26:13.380> you 00:26:13.789 --> 00:26:13.799 align:start position:0% works is that you can supply when you 00:26:13.799 --> 00:26:16.730 align:start position:0% works is that you can supply when you call<00:26:13.980> a<00:26:14.220> normal<00:26:14.460> it's<00:26:15.120> like<00:26:15.360> fulfill<00:26:15.720> order 00:26:16.730 --> 00:26:16.740 align:start position:0% call a normal it's like fulfill order 00:26:16.740 --> 00:26:19.909 align:start position:0% call a normal it's like fulfill order uh<00:26:17.279> fulfill<00:26:17.520> available<00:26:17.820> orders<00:26:18.360> match<00:26:18.779> orders 00:26:19.909 --> 00:26:19.919 align:start position:0% uh fulfill available orders match orders 00:26:19.919 --> 00:26:21.950 align:start position:0% uh fulfill available orders match orders those<00:26:20.460> don't<00:26:20.640> do<00:26:20.820> partial<00:26:21.179> fills<00:26:21.539> but<00:26:21.659> there's 00:26:21.950 --> 00:26:21.960 align:start position:0% those don't do partial fills but there's 00:26:21.960 --> 00:26:23.330 align:start position:0% those don't do partial fills but there's an<00:26:22.260> also 00:26:23.330 --> 00:26:23.340 align:start position:0% an also 00:26:23.340 --> 00:26:26.630 align:start position:0% an also fulfill<00:26:24.120> Advanced<00:26:24.720> orders<00:26:25.500> uh<00:26:26.400> match 00:26:26.630 --> 00:26:26.640 align:start position:0% fulfill Advanced orders uh match 00:26:26.640 --> 00:26:28.310 align:start position:0% fulfill Advanced orders uh match Advanced<00:26:27.240> orders<00:26:27.600> fulfill<00:26:28.080> available 00:26:28.310 --> 00:26:28.320 align:start position:0% Advanced orders fulfill available 00:26:28.320 --> 00:26:31.850 align:start position:0% Advanced orders fulfill available Advanced<00:26:29.159> orders<00:26:29.520> those<00:26:30.120> you<00:26:31.080> give 00:26:31.850 --> 00:26:31.860 align:start position:0% Advanced orders those you give 00:26:31.860 --> 00:26:34.190 align:start position:0% Advanced orders those you give criteria<00:26:32.760> resolvers<00:26:33.480> basically<00:26:33.779> Merkle 00:26:34.190 --> 00:26:34.200 align:start position:0% criteria resolvers basically Merkle 00:26:34.200 --> 00:26:36.470 align:start position:0% criteria resolvers basically Merkle proofs<00:26:34.500> for<00:26:34.679> the<00:26:34.860> criteria-based<00:26:35.640> items<00:26:35.940> as 00:26:36.470 --> 00:26:36.480 align:start position:0% proofs for the criteria-based items as 00:26:36.480 --> 00:26:39.890 align:start position:0% proofs for the criteria-based items as well<00:26:36.659> as<00:26:36.840> fill<00:26:37.740> fraction<00:26:38.100> a<00:26:38.700> numerator<00:26:39.240> and<00:26:39.720> a 00:26:39.890 --> 00:26:39.900 align:start position:0% well as fill fraction a numerator and a 00:26:39.900 --> 00:26:41.390 align:start position:0% well as fill fraction a numerator and a denominator 00:26:41.390 --> 00:26:41.400 align:start position:0% denominator 00:26:41.400 --> 00:26:42.769 align:start position:0% denominator and 00:26:42.769 --> 00:26:42.779 align:start position:0% and 00:26:42.779 --> 00:26:46.190 align:start position:0% and the<00:26:43.440> the<00:26:43.620> heuristic<00:26:44.279> is<00:26:44.580> that<00:26:44.880> every<00:26:45.659> single 00:26:46.190 --> 00:26:46.200 align:start position:0% the the heuristic is that every single 00:26:46.200 --> 00:26:48.490 align:start position:0% the the heuristic is that every single assuming<00:26:47.100> that<00:26:47.220> the<00:26:47.460> order<00:26:47.640> supports<00:26:48.299> it 00:26:48.490 --> 00:26:48.500 align:start position:0% assuming that the order supports it 00:26:48.500 --> 00:26:51.350 align:start position:0% assuming that the order supports it every<00:26:49.500> single<00:26:49.919> offer<00:26:50.460> item 00:26:51.350 --> 00:26:51.360 align:start position:0% every single offer item 00:26:51.360 --> 00:26:54.649 align:start position:0% every single offer item and<00:26:52.080> every<00:26:52.320> single<00:26:52.620> consideration<00:26:53.220> item<00:26:54.120> is 00:26:54.649 --> 00:26:54.659 align:start position:0% and every single consideration item is 00:26:54.659 --> 00:26:57.610 align:start position:0% and every single consideration item is going<00:26:54.900> to<00:26:55.020> get<00:26:55.200> that<00:26:55.620> fraction<00:26:55.980> applied<00:26:56.820> to<00:26:57.120> it 00:26:57.610 --> 00:26:57.620 align:start position:0% going to get that fraction applied to it 00:26:57.620 --> 00:27:01.070 align:start position:0% going to get that fraction applied to it and<00:26:58.620> then<00:26:58.799> once<00:26:59.400> the<00:26:59.520> order<00:26:59.640> is<00:26:59.940> fulfilled 00:27:01.070 --> 00:27:01.080 align:start position:0% and then once the order is fulfilled 00:27:01.080 --> 00:27:02.630 align:start position:0% and then once the order is fulfilled it's<00:27:01.620> just<00:27:01.740> going<00:27:01.860> to<00:27:01.980> update<00:27:02.220> with<00:27:02.460> the 00:27:02.630 --> 00:27:02.640 align:start position:0% it's just going to update with the 00:27:02.640 --> 00:27:04.010 align:start position:0% it's just going to update with the fraction<00:27:02.820> say<00:27:03.120> here's<00:27:03.419> how<00:27:03.480> much<00:27:03.659> it's<00:27:03.840> been 00:27:04.010 --> 00:27:04.020 align:start position:0% fraction say here's how much it's been 00:27:04.020 --> 00:27:05.390 align:start position:0% fraction say here's how much it's been fulfilled 00:27:05.390 --> 00:27:05.400 align:start position:0% fulfilled 00:27:05.400 --> 00:27:07.970 align:start position:0% fulfilled the<00:27:06.120> rule 00:27:07.970 --> 00:27:07.980 align:start position:0% the rule 00:27:07.980 --> 00:27:10.430 align:start position:0% the rule to<00:27:08.340> avoid<00:27:08.820> any<00:27:09.240> kind<00:27:09.480> of<00:27:09.659> weirdness<00:27:10.140> around 00:27:10.430 --> 00:27:10.440 align:start position:0% to avoid any kind of weirdness around 00:27:10.440 --> 00:27:13.370 align:start position:0% to avoid any kind of weirdness around grounding<00:27:11.039> errors<00:27:11.419> is<00:27:12.419> that 00:27:13.370 --> 00:27:13.380 align:start position:0% grounding errors is that 00:27:13.380 --> 00:27:15.590 align:start position:0% grounding errors is that every<00:27:13.919> single<00:27:14.220> one<00:27:14.400> of<00:27:14.520> those<00:27:14.700> fractions<00:27:15.360> has 00:27:15.590 --> 00:27:15.600 align:start position:0% every single one of those fractions has 00:27:15.600 --> 00:27:19.549 align:start position:0% every single one of those fractions has got<00:27:15.900> to<00:27:16.080> be<00:27:16.559> exact<00:27:17.520> it<00:27:18.480> there<00:27:18.960> can<00:27:19.140> be<00:27:19.260> no 00:27:19.549 --> 00:27:19.559 align:start position:0% got to be exact it there can be no 00:27:19.559 --> 00:27:22.549 align:start position:0% got to be exact it there can be no remainder<00:27:20.279> after<00:27:20.880> applying<00:27:21.419> the<00:27:21.539> fraction 00:27:22.549 --> 00:27:22.559 align:start position:0% remainder after applying the fraction 00:27:22.559 --> 00:27:25.490 align:start position:0% remainder after applying the fraction so<00:27:23.100> in<00:27:23.340> general<00:27:23.460> when<00:27:23.940> you're<00:27:24.500> constructing 00:27:25.490 --> 00:27:25.500 align:start position:0% so in general when you're constructing 00:27:25.500 --> 00:27:27.470 align:start position:0% so in general when you're constructing an<00:27:25.980> order<00:27:26.159> that<00:27:26.400> supports<00:27:26.760> partial<00:27:27.120> fills 00:27:27.470 --> 00:27:27.480 align:start position:0% an order that supports partial fills 00:27:27.480 --> 00:27:29.090 align:start position:0% an order that supports partial fills from<00:27:27.600> the<00:27:27.720> get-go 00:27:29.090 --> 00:27:29.100 align:start position:0% from the get-go 00:27:29.100 --> 00:27:31.850 align:start position:0% from the get-go the<00:27:29.760> easiest<00:27:30.120> way<00:27:30.360> to<00:27:30.539> do<00:27:30.659> it<00:27:30.840> is<00:27:31.440> to<00:27:31.679> start 00:27:31.850 --> 00:27:31.860 align:start position:0% the easiest way to do it is to start 00:27:31.860 --> 00:27:35.110 align:start position:0% the easiest way to do it is to start with<00:27:32.100> a<00:27:32.279> single<00:27:32.580> quantity<00:27:33.000> right<00:27:33.480> I<00:27:34.320> have 00:27:35.110 --> 00:27:35.120 align:start position:0% with a single quantity right I have 00:27:35.120 --> 00:27:39.110 align:start position:0% with a single quantity right I have some<00:27:36.120> ERC<00:27:36.779> 1155<00:27:37.440> tokens<00:27:37.860> that<00:27:38.100> I<00:27:38.220> want<00:27:38.340> to<00:27:38.520> sell 00:27:39.110 --> 00:27:39.120 align:start position:0% some ERC 1155 tokens that I want to sell 00:27:39.120 --> 00:27:44.029 align:start position:0% some ERC 1155 tokens that I want to sell for<00:27:39.900> one<00:27:40.860> eth<00:27:41.279> each<00:27:41.760> right<00:27:42.600> I<00:27:43.320> want<00:27:43.440> to<00:27:43.559> sell<00:27:43.679> 10 00:27:44.029 --> 00:27:44.039 align:start position:0% for one eth each right I want to sell 10 00:27:44.039 --> 00:27:46.130 align:start position:0% for one eth each right I want to sell 10 so<00:27:44.700> I'll<00:27:44.880> now<00:27:45.059> just<00:27:45.240> take<00:27:45.419> the<00:27:45.600> one<00:27:45.779> eighth 00:27:46.130 --> 00:27:46.140 align:start position:0% so I'll now just take the one eighth 00:27:46.140 --> 00:27:48.529 align:start position:0% so I'll now just take the one eighth multiply<00:27:46.860> that<00:27:46.980> by<00:27:47.159> 10.<00:27:47.580> take<00:27:47.940> all<00:27:48.120> the<00:27:48.240> fees 00:27:48.529 --> 00:27:48.539 align:start position:0% multiply that by 10. take all the fees 00:27:48.539 --> 00:27:49.970 align:start position:0% multiply that by 10. take all the fees that<00:27:48.840> were<00:27:48.960> already<00:27:49.140> calculated<00:27:49.500> multiply 00:27:49.970 --> 00:27:49.980 align:start position:0% that were already calculated multiply 00:27:49.980 --> 00:27:52.990 align:start position:0% that were already calculated multiply those<00:27:50.159> by<00:27:50.400> 10.<00:27:50.820> so<00:27:51.179> it'll<00:27:51.419> be<00:27:51.539> a<00:27:51.720> nice<00:27:51.900> even 00:27:52.990 --> 00:27:53.000 align:start position:0% those by 10. so it'll be a nice even 00:27:53.000 --> 00:27:56.149 align:start position:0% those by 10. so it'll be a nice even fraction<00:27:54.000> that's<00:27:54.360> applied<00:27:55.200> the<00:27:55.679> math<00:27:55.860> behind 00:27:56.149 --> 00:27:56.159 align:start position:0% fraction that's applied the math behind 00:27:56.159 --> 00:27:57.830 align:start position:0% fraction that's applied the math behind that<00:27:56.340> on<00:27:56.520> the<00:27:56.640> contract<00:27:56.940> is<00:27:57.179> also<00:27:57.480> pretty<00:27:57.659> cool 00:27:57.830 --> 00:27:57.840 align:start position:0% that on the contract is also pretty cool 00:27:57.840 --> 00:28:01.190 align:start position:0% that on the contract is also pretty cool the<00:27:58.200> uses<00:27:59.400> um<00:27:59.400> the<00:27:59.700> euclidean<00:28:00.120> algorithm<00:28:00.659> to 00:28:01.190 --> 00:28:01.200 align:start position:0% the uses um the euclidean algorithm to 00:28:01.200 --> 00:28:02.630 align:start position:0% the uses um the euclidean algorithm to ensure<00:28:01.620> that<00:28:01.860> there's 00:28:02.630 --> 00:28:02.640 align:start position:0% ensure that there's 00:28:02.640 --> 00:28:06.110 align:start position:0% ensure that there's uh<00:28:03.480> if<00:28:03.779> there's<00:28:03.960> an<00:28:04.140> overflow<00:28:04.559> we<00:28:04.740> can<00:28:04.860> all<00:28:05.120> uh 00:28:06.110 --> 00:28:06.120 align:start position:0% uh if there's an overflow we can all uh 00:28:06.120 --> 00:28:08.390 align:start position:0% uh if there's an overflow we can all uh be<00:28:06.659> rounded<00:28:07.500> down<00:28:07.679> to<00:28:07.860> the<00:28:07.980> greatest<00:28:08.100> common 00:28:08.390 --> 00:28:08.400 align:start position:0% be rounded down to the greatest common 00:28:08.400 --> 00:28:09.830 align:start position:0% be rounded down to the greatest common divisor<00:28:09.000> but<00:28:09.179> that's<00:28:09.299> that's<00:28:09.539> different 00:28:09.830 --> 00:28:09.840 align:start position:0% divisor but that's that's different 00:28:09.840 --> 00:28:13.010 align:start position:0% divisor but that's that's different topics<00:28:10.260> yes<00:28:10.559> there's<00:28:10.860> partial<00:28:11.220> fills<00:28:11.700> and<00:28:12.900> um 00:28:13.010 --> 00:28:13.020 align:start position:0% topics yes there's partial fills and um 00:28:13.020 --> 00:28:16.490 align:start position:0% topics yes there's partial fills and um and<00:28:13.980> once<00:28:14.340> the<00:28:14.520> basically<00:28:14.940> once<00:28:15.419> the<00:28:15.600> fraction 00:28:16.490 --> 00:28:16.500 align:start position:0% and once the basically once the fraction 00:28:16.500 --> 00:28:19.310 align:start position:0% and once the basically once the fraction The<00:28:16.919> Fill<00:28:17.100> fraction<00:28:17.520> is<00:28:17.760> applied<00:28:18.120> and<00:28:18.960> all<00:28:19.140> the 00:28:19.310 --> 00:28:19.320 align:start position:0% The Fill fraction is applied and all the 00:28:19.320 --> 00:28:22.070 align:start position:0% The Fill fraction is applied and all the criteria<00:28:19.919> resolvers<00:28:20.760> are<00:28:20.880> applied<00:28:21.179> and<00:28:21.900> it's 00:28:22.070 --> 00:28:22.080 align:start position:0% criteria resolvers are applied and it's 00:28:22.080 --> 00:28:24.110 align:start position:0% criteria resolvers are applied and it's all<00:28:22.260> the<00:28:22.440> exact<00:28:22.740> same<00:28:22.980> flow<00:28:23.400> as<00:28:23.700> with<00:28:23.880> the 00:28:24.110 --> 00:28:24.120 align:start position:0% all the exact same flow as with the 00:28:24.120 --> 00:28:26.330 align:start position:0% all the exact same flow as with the standard<00:28:24.960> stuff 00:28:26.330 --> 00:28:26.340 align:start position:0% standard stuff 00:28:26.340 --> 00:28:29.330 align:start position:0% standard stuff yeah 00:28:29.330 --> 00:28:29.340 align:start position:0% 00:28:29.340 --> 00:28:31.029 align:start position:0% yeah 00:28:31.029 --> 00:28:31.039 align:start position:0% yeah 00:28:31.039 --> 00:28:33.710 align:start position:0% yeah hey<00:28:32.039> there<00:28:32.340> can<00:28:33.000> you<00:28:33.179> talk<00:28:33.299> a<00:28:33.480> little<00:28:33.600> bit 00:28:33.710 --> 00:28:33.720 align:start position:0% hey there can you talk a little bit 00:28:33.720 --> 00:28:35.870 align:start position:0% hey there can you talk a little bit about<00:28:33.900> extra<00:28:34.620> cheap<00:28:34.980> signatures<00:28:35.520> and<00:28:35.700> when 00:28:35.870 --> 00:28:35.880 align:start position:0% about extra cheap signatures and when 00:28:35.880 --> 00:28:38.269 align:start position:0% about extra cheap signatures and when they<00:28:36.000> should<00:28:36.120> be<00:28:36.240> used<00:28:36.960> about<00:28:37.919> what 00:28:38.269 --> 00:28:38.279 align:start position:0% they should be used about what 00:28:38.279 --> 00:28:40.490 align:start position:0% they should be used about what signatures<00:28:38.700> extra<00:28:39.179> cheap<00:28:39.539> I<00:28:39.960> see<00:28:40.080> that's<00:28:40.320> a 00:28:40.490 --> 00:28:40.500 align:start position:0% signatures extra cheap I see that's a 00:28:40.500 --> 00:28:42.190 align:start position:0% signatures extra cheap I see that's a parameter<00:28:40.860> when<00:28:41.100> you're<00:28:41.279> creating<00:28:41.580> an<00:28:41.760> order 00:28:42.190 --> 00:28:42.200 align:start position:0% parameter when you're creating an order 00:28:42.200 --> 00:28:45.950 align:start position:0% parameter when you're creating an order and<00:28:43.200> I<00:28:43.500> think<00:28:43.679> you<00:28:43.799> use<00:28:43.980> EIP<00:28:44.480> 2098<00:28:45.480> in<00:28:45.779> that 00:28:45.950 --> 00:28:45.960 align:start position:0% and I think you use EIP 2098 in that 00:28:45.960 --> 00:28:49.510 align:start position:0% and I think you use EIP 2098 in that case<00:28:46.140> oh<00:28:47.039> yeah<00:28:47.279> yeah<00:28:47.580> so 00:28:49.510 --> 00:28:49.520 align:start position:0% case oh yeah yeah so 00:28:49.520 --> 00:28:55.130 align:start position:0% case oh yeah yeah so 2098<00:28:50.520> is<00:28:51.779> um<00:28:51.779> the<00:28:52.140> 64<00:28:52.620> byte<00:28:53.159> signatures 00:28:55.130 --> 00:28:55.140 align:start position:0% 2098 is um the 64 byte signatures 00:28:55.140 --> 00:28:57.190 align:start position:0% 2098 is um the 64 byte signatures so<00:28:55.500> a<00:28:55.860> standard 00:28:57.190 --> 00:28:57.200 align:start position:0% so a standard 00:28:57.200 --> 00:29:01.070 align:start position:0% so a standard ecdsa<00:28:58.200> in<00:28:58.620> ethereum<00:28:59.100> has<00:28:59.419> three<00:29:00.419> parameters 00:29:01.070 --> 00:29:01.080 align:start position:0% ecdsa in ethereum has three parameters 00:29:01.080 --> 00:29:03.409 align:start position:0% ecdsa in ethereum has three parameters right<00:29:01.380> v<00:29:01.860> r<00:29:02.100> and<00:29:02.400> s 00:29:03.409 --> 00:29:03.419 align:start position:0% right v r and s 00:29:03.419 --> 00:29:05.570 align:start position:0% right v r and s and 00:29:05.570 --> 00:29:05.580 align:start position:0% and 00:29:05.580 --> 00:29:08.690 align:start position:0% and um<00:29:05.700> turns<00:29:06.360> out<00:29:06.539> that<00:29:07.440> there's<00:29:08.100> there's<00:29:08.400> a 00:29:08.690 --> 00:29:08.700 align:start position:0% um turns out that there's there's a 00:29:08.700 --> 00:29:11.510 align:start position:0% um turns out that there's there's a parody<00:29:09.000> to<00:29:09.900> the<00:29:10.559> V<00:29:10.679> right<00:29:10.919> it's<00:29:11.100> almost<00:29:11.279> always 00:29:11.510 --> 00:29:11.520 align:start position:0% parody to the V right it's almost always 00:29:11.520 --> 00:29:15.409 align:start position:0% parody to the V right it's almost always 27<00:29:12.419> or<00:29:12.720> 28<00:29:13.200> right<00:29:13.799> and<00:29:14.039> there's<00:29:14.340> basically<00:29:15.240> a 00:29:15.409 --> 00:29:15.419 align:start position:0% 27 or 28 right and there's basically a 00:29:15.419 --> 00:29:18.110 align:start position:0% 27 or 28 right and there's basically a signature<00:29:15.900> malleability<00:29:16.760> concern<00:29:17.760> there 00:29:18.110 --> 00:29:18.120 align:start position:0% signature malleability concern there 00:29:18.120 --> 00:29:21.950 align:start position:0% signature malleability concern there where<00:29:18.480> you<00:29:19.440> have<00:29:19.559> two<00:29:20.340> exactly<00:29:20.880> identical 00:29:21.950 --> 00:29:21.960 align:start position:0% where you have two exactly identical 00:29:21.960 --> 00:29:24.049 align:start position:0% where you have two exactly identical or<00:29:22.440> the<00:29:22.740> the<00:29:22.860> signatures<00:29:23.399> are<00:29:23.580> different<00:29:23.700> but 00:29:24.049 --> 00:29:24.059 align:start position:0% or the the signatures are different but 00:29:24.059 --> 00:29:26.870 align:start position:0% or the the signatures are different but they<00:29:24.240> resolve<00:29:24.600> to<00:29:24.720> the<00:29:24.960> same<00:29:25.159> uh<00:29:26.159> record<00:29:26.580> they 00:29:26.870 --> 00:29:26.880 align:start position:0% they resolve to the same uh record they 00:29:26.880 --> 00:29:30.110 align:start position:0% they resolve to the same uh record they recover<00:29:27.120> to<00:29:27.299> the<00:29:27.480> same<00:29:27.600> signer 00:29:30.110 --> 00:29:30.120 align:start position:0% recover to the same signer 00:29:30.120 --> 00:29:33.049 align:start position:0% recover to the same signer well<00:29:30.600> the<00:29:30.840> trick<00:29:31.140> is<00:29:31.320> basically<00:29:31.679> to<00:29:31.919> say<00:29:32.100> what 00:29:33.049 --> 00:29:33.059 align:start position:0% well the trick is basically to say what 00:29:33.059 --> 00:29:35.269 align:start position:0% well the trick is basically to say what if<00:29:33.240> we<00:29:33.480> just<00:29:33.840> always 00:29:35.269 --> 00:29:35.279 align:start position:0% if we just always 00:29:35.279 --> 00:29:37.970 align:start position:0% if we just always flip<00:29:35.760> the<00:29:35.880> parody<00:29:36.240> right<00:29:37.020> so<00:29:37.320> you<00:29:37.559> can<00:29:37.679> take 00:29:37.970 --> 00:29:37.980 align:start position:0% flip the parody right so you can take 00:29:37.980 --> 00:29:41.029 align:start position:0% flip the parody right so you can take any<00:29:38.340> 65<00:29:39.179> byte<00:29:39.779> signature 00:29:41.029 --> 00:29:41.039 align:start position:0% any 65 byte signature 00:29:41.039 --> 00:29:44.690 align:start position:0% any 65 byte signature and<00:29:41.700> you<00:29:42.299> compress<00:29:42.779> you<00:29:43.140> flip<00:29:43.679> it<00:29:43.799> so<00:29:44.279> that<00:29:44.460> the 00:29:44.690 --> 00:29:44.700 align:start position:0% and you compress you flip it so that the 00:29:44.700 --> 00:29:46.490 align:start position:0% and you compress you flip it so that the parity<00:29:45.059> is<00:29:45.299> always 00:29:46.490 --> 00:29:46.500 align:start position:0% parity is always 00:29:46.500 --> 00:29:48.370 align:start position:0% parity is always I<00:29:46.919> think<00:29:46.980> 27 00:29:48.370 --> 00:29:48.380 align:start position:0% I think 27 00:29:48.380 --> 00:29:52.490 align:start position:0% I think 27 and<00:29:49.380> then<00:29:49.760> you<00:29:50.760> also<00:29:51.539> can 00:29:52.490 --> 00:29:52.500 align:start position:0% and then you also can 00:29:52.500 --> 00:29:55.610 align:start position:0% and then you also can because<00:29:53.039> when<00:29:53.399> the<00:29:53.520> parody<00:29:53.820> is<00:29:54.059> that<00:29:54.299> 27<00:29:54.840> then 00:29:55.610 --> 00:29:55.620 align:start position:0% because when the parody is that 27 then 00:29:55.620 --> 00:29:58.190 align:start position:0% because when the parody is that 27 then the<00:29:55.919> S<00:29:56.100> value<00:29:56.460> won't<00:29:57.419> use<00:29:57.720> the<00:29:58.020> most 00:29:58.190 --> 00:29:58.200 align:start position:0% the S value won't use the most 00:29:58.200 --> 00:30:01.570 align:start position:0% the S value won't use the most significant<00:29:58.740> bit<00:29:59.360> so<00:30:00.360> then<00:30:00.539> you<00:30:00.720> can<00:30:00.840> compress 00:30:01.570 --> 00:30:01.580 align:start position:0% significant bit so then you can compress 00:30:01.580 --> 00:30:06.710 align:start position:0% significant bit so then you can compress V<00:30:02.580> and<00:30:02.880> S<00:30:03.120> into<00:30:03.779> a<00:30:04.140> single<00:30:04.520> word<00:30:05.520> you<00:30:06.360> basically 00:30:06.710 --> 00:30:06.720 align:start position:0% V and S into a single word you basically 00:30:06.720 --> 00:30:09.289 align:start position:0% V and S into a single word you basically take<00:30:07.020> what<00:30:07.260> was<00:30:07.440> once<00:30:07.919> three<00:30:08.220> now<00:30:08.880> it's<00:30:09.059> just 00:30:09.289 --> 00:30:09.299 align:start position:0% take what was once three now it's just 00:30:09.299 --> 00:30:11.930 align:start position:0% take what was once three now it's just two<00:30:09.659> words<00:30:10.080> so<00:30:10.679> you<00:30:10.860> cut<00:30:10.980> down<00:30:11.159> on<00:30:11.399> a<00:30:11.580> word<00:30:11.700> of 00:30:11.930 --> 00:30:11.940 align:start position:0% two words so you cut down on a word of 00:30:11.940 --> 00:30:17.090 align:start position:0% two words so you cut down on a word of call<00:30:12.120> data<00:30:12.799> in<00:30:13.820> standard<00:30:14.820> API<00:30:15.480> encoding<00:30:16.100> which 00:30:17.090 --> 00:30:17.100 align:start position:0% call data in standard API encoding which 00:30:17.100 --> 00:30:20.409 align:start position:0% call data in standard API encoding which you<00:30:17.820> know<00:30:17.940> you're<00:30:18.059> looking<00:30:18.240> at<00:30:18.559> what 00:30:20.409 --> 00:30:20.419 align:start position:0% you know you're looking at what 00:30:20.419 --> 00:30:25.130 align:start position:0% you know you're looking at what 130<00:30:21.419> bytes<00:30:22.020> or<00:30:22.559> 130<00:30:23.100> gas<00:30:23.279> for<00:30:23.880> those<00:30:24.059> bytes 00:30:25.130 --> 00:30:25.140 align:start position:0% 130 bytes or 130 gas for those bytes 00:30:25.140 --> 00:30:26.930 align:start position:0% 130 bytes or 130 gas for those bytes and<00:30:25.980> uh 00:30:26.930 --> 00:30:26.940 align:start position:0% and uh 00:30:26.940 --> 00:30:30.529 align:start position:0% and uh just<00:30:27.600> a<00:30:27.720> minor<00:30:28.700> optimization<00:30:29.700> that<00:30:30.120> that<00:30:30.299> you 00:30:30.529 --> 00:30:30.539 align:start position:0% just a minor optimization that that you 00:30:30.539 --> 00:30:32.810 align:start position:0% just a minor optimization that that you can<00:30:30.659> employ<00:30:30.840> that's<00:30:31.620> the<00:30:31.799> idea<00:30:32.100> nice<00:30:32.520> thank 00:30:32.810 --> 00:30:32.820 align:start position:0% can employ that's the idea nice thank 00:30:32.820 --> 00:30:39.370 align:start position:0% can employ that's the idea nice thank you 00:30:39.370 --> 00:30:39.380 align:start position:0% 00:30:39.380 --> 00:30:43.310 align:start position:0% great<00:30:40.380> questions<00:30:40.620> everybody 00:30:43.310 --> 00:30:43.320 align:start position:0% 00:30:43.320 --> 00:30:44.930 align:start position:0% hey<00:30:43.799> hi 00:30:44.930 --> 00:30:44.940 align:start position:0% hey hi 00:30:44.940 --> 00:30:47.330 align:start position:0% hey hi so<00:30:45.360> I<00:30:45.600> assume<00:30:46.080> I'm<00:30:46.260> trying<00:30:46.620> to<00:30:46.860> do<00:30:46.919> like<00:30:47.100> a 00:30:47.330 --> 00:30:47.340 align:start position:0% so I assume I'm trying to do like a 00:30:47.340 --> 00:30:51.409 align:start position:0% so I assume I'm trying to do like a searching<00:30:47.700> strategy<00:30:48.299> right<00:30:48.539> so<00:30:49.320> uh<00:30:49.880> to<00:30:50.880> help 00:30:51.409 --> 00:30:51.419 align:start position:0% searching strategy right so uh to help 00:30:51.419 --> 00:30:54.950 align:start position:0% searching strategy right so uh to help users<00:30:52.020> with<00:30:52.440> a<00:30:52.919> gas<00:30:53.279> uh<00:30:53.940> you<00:30:54.240> may<00:30:54.360> take<00:30:54.600> like 00:30:54.950 --> 00:30:54.960 align:start position:0% users with a gas uh you may take like 00:30:54.960 --> 00:30:57.590 align:start position:0% users with a gas uh you may take like signed<00:30:55.500> orders<00:30:55.980> right<00:30:56.279> and<00:30:57.059> those<00:30:57.299> are<00:30:57.480> not 00:30:57.590 --> 00:30:57.600 align:start position:0% signed orders right and those are not 00:30:57.600 --> 00:30:59.210 align:start position:0% signed orders right and those are not visible<00:30:58.020> on<00:30:58.260> chain 00:30:59.210 --> 00:30:59.220 align:start position:0% visible on chain 00:30:59.220 --> 00:31:01.789 align:start position:0% visible on chain so<00:30:59.940> for<00:31:00.299> a<00:31:00.480> Searcher<00:31:00.899> to<00:31:01.080> like<00:31:01.260> look<00:31:01.559> through 00:31:01.789 --> 00:31:01.799 align:start position:0% so for a Searcher to like look through 00:31:01.799 --> 00:31:05.149 align:start position:0% so for a Searcher to like look through all<00:31:02.220> the<00:31:02.399> possibilities<00:31:02.940> of<00:31:03.659> uh<00:31:04.559> orders<00:31:04.980> out 00:31:05.149 --> 00:31:05.159 align:start position:0% all the possibilities of uh orders out 00:31:05.159 --> 00:31:07.549 align:start position:0% all the possibilities of uh orders out there<00:31:05.340> that<00:31:05.580> I<00:31:05.820> could<00:31:06.000> possibly<00:31:06.480> fill<00:31:06.779> with<00:31:07.380> a 00:31:07.549 --> 00:31:07.559 align:start position:0% there that I could possibly fill with a 00:31:07.559 --> 00:31:10.549 align:start position:0% there that I could possibly fill with a match<00:31:07.740> order<00:31:08.059> where<00:31:09.059> would<00:31:09.480> I<00:31:09.659> get<00:31:09.840> a<00:31:10.080> list<00:31:10.320> of 00:31:10.549 --> 00:31:10.559 align:start position:0% match order where would I get a list of 00:31:10.559 --> 00:31:13.310 align:start position:0% match order where would I get a list of all<00:31:11.100> the<00:31:11.279> orders<00:31:11.640> that<00:31:12.000> are<00:31:12.240> not<00:31:12.720> on<00:31:13.080> chain 00:31:13.310 --> 00:31:13.320 align:start position:0% all the orders that are not on chain 00:31:13.320 --> 00:31:16.010 align:start position:0% all the orders that are not on chain like<00:31:13.860> is<00:31:14.039> there<00:31:14.220> a<00:31:14.460> HTTP<00:31:15.059> API<00:31:15.539> that<00:31:15.779> I<00:31:15.899> could 00:31:16.010 --> 00:31:16.020 align:start position:0% like is there a HTTP API that I could 00:31:16.020 --> 00:31:17.330 align:start position:0% like is there a HTTP API that I could call 00:31:17.330 --> 00:31:17.340 align:start position:0% call 00:31:17.340 --> 00:31:19.070 align:start position:0% call ah<00:31:18.120> so 00:31:19.070 --> 00:31:19.080 align:start position:0% ah so 00:31:19.080 --> 00:31:21.529 align:start position:0% ah so this<00:31:19.740> this<00:31:19.740> really 00:31:21.529 --> 00:31:21.539 align:start position:0% this this really 00:31:21.539 --> 00:31:22.190 align:start position:0% this this really um 00:31:22.190 --> 00:31:22.200 align:start position:0% um 00:31:22.200 --> 00:31:25.490 align:start position:0% um it<00:31:22.679> delves<00:31:22.980> into<00:31:23.159> less<00:31:23.940> of<00:31:24.179> how<00:31:24.720> does<00:31:25.140> Seaport 00:31:25.490 --> 00:31:25.500 align:start position:0% it delves into less of how does Seaport 00:31:25.500 --> 00:31:28.070 align:start position:0% it delves into less of how does Seaport do<00:31:25.679> it<00:31:25.860> and<00:31:26.460> more<00:31:26.640> all<00:31:27.179> right<00:31:27.360> what<00:31:27.720> about<00:31:27.840> the 00:31:28.070 --> 00:31:28.080 align:start position:0% do it and more all right what about the 00:31:28.080 --> 00:31:29.630 align:start position:0% do it and more all right what about the marketplaces<00:31:28.679> they're<00:31:28.980> built<00:31:29.279> on<00:31:29.399> top<00:31:29.520> of 00:31:29.630 --> 00:31:29.640 align:start position:0% marketplaces they're built on top of 00:31:29.640 --> 00:31:32.450 align:start position:0% marketplaces they're built on top of Seaport<00:31:30.120> right<00:31:30.419> we<00:31:30.720> work<00:31:30.840> at<00:31:31.020> openc<00:31:31.440> we<00:31:32.399> have 00:31:32.450 --> 00:31:32.460 align:start position:0% Seaport right we work at openc we have 00:31:32.460 --> 00:31:34.970 align:start position:0% Seaport right we work at openc we have an<00:31:32.580> API<00:31:33.000> if<00:31:33.840> you<00:31:33.960> have<00:31:34.080> access<00:31:34.260> to<00:31:34.500> the<00:31:34.620> API 00:31:34.970 --> 00:31:34.980 align:start position:0% an API if you have access to the API 00:31:34.980 --> 00:31:37.549 align:start position:0% an API if you have access to the API then<00:31:35.220> you<00:31:35.399> can<00:31:35.520> read<00:31:35.640> from<00:31:35.880> the<00:31:36.059> API<00:31:36.419> and<00:31:36.779> and 00:31:37.549 --> 00:31:37.559 align:start position:0% then you can read from the API and and 00:31:37.559 --> 00:31:39.830 align:start position:0% then you can read from the API and and get<00:31:38.460> a<00:31:38.700> sense<00:31:38.940> of<00:31:39.059> yours<00:31:39.360> there<00:31:39.600> are<00:31:39.659> also 00:31:39.830 --> 00:31:39.840 align:start position:0% get a sense of yours there are also 00:31:39.840 --> 00:31:41.389 align:start position:0% get a sense of yours there are also other<00:31:40.020> marketplaces<00:31:40.740> they're<00:31:40.980> built<00:31:41.220> on<00:31:41.279> top 00:31:41.389 --> 00:31:41.399 align:start position:0% other marketplaces they're built on top 00:31:41.399 --> 00:31:42.830 align:start position:0% other marketplaces they're built on top of<00:31:41.520> Seaport<00:31:41.940> you<00:31:42.059> might<00:31:42.179> want<00:31:42.360> to<00:31:42.480> be<00:31:42.539> pulling 00:31:42.830 --> 00:31:42.840 align:start position:0% of Seaport you might want to be pulling 00:31:42.840 --> 00:31:43.850 align:start position:0% of Seaport you might want to be pulling from<00:31:43.080> those 00:31:43.850 --> 00:31:43.860 align:start position:0% from those 00:31:43.860 --> 00:31:47.330 align:start position:0% from those but<00:31:44.340> it<00:31:44.520> does<00:31:44.700> get<00:31:44.940> more<00:31:45.240> complicated<00:31:45.980> to<00:31:46.980> find 00:31:47.330 --> 00:31:47.340 align:start position:0% but it does get more complicated to find 00:31:47.340 --> 00:31:50.090 align:start position:0% but it does get more complicated to find all<00:31:47.520> of<00:31:47.700> that<00:31:47.820> you<00:31:48.120> can<00:31:48.299> listen<00:31:48.779> on<00:31:49.080> chain<00:31:49.320> for 00:31:50.090 --> 00:31:50.100 align:start position:0% all of that you can listen on chain for 00:31:50.100 --> 00:31:52.430 align:start position:0% all of that you can listen on chain for the<00:31:50.399> validate<00:31:50.820> events<00:31:51.179> right<00:31:51.539> which<00:31:52.200> is<00:31:52.260> one 00:31:52.430 --> 00:31:52.440 align:start position:0% the validate events right which is one 00:31:52.440 --> 00:31:53.990 align:start position:0% the validate events right which is one way<00:31:52.620> to<00:31:52.740> do<00:31:52.860> it<00:31:52.980> you<00:31:53.399> can<00:31:53.520> listen<00:31:53.640> in<00:31:53.880> the 00:31:53.990 --> 00:31:54.000 align:start position:0% way to do it you can listen in the 00:31:54.000 --> 00:31:57.409 align:start position:0% way to do it you can listen in the mempool<00:31:54.419> there's<00:31:55.140> another<00:31:55.380> way<00:31:55.679> right<00:31:56.039> so 00:31:57.409 --> 00:31:57.419 align:start position:0% mempool there's another way right so 00:31:57.419 --> 00:31:59.570 align:start position:0% mempool there's another way right so um<00:31:57.899> but<00:31:58.500> there<00:31:58.740> is 00:31:59.570 --> 00:31:59.580 align:start position:0% um but there is 00:31:59.580 --> 00:32:03.110 align:start position:0% um but there is I<00:32:00.120> think<00:32:00.240> it's<00:32:00.840> it's<00:32:01.080> definitely<00:32:01.700> an<00:32:02.700> area<00:32:02.880> of 00:32:03.110 --> 00:32:03.120 align:start position:0% I think it's it's definitely an area of 00:32:03.120 --> 00:32:05.870 align:start position:0% I think it's it's definitely an area of active<00:32:03.419> investigation<00:32:03.960> to<00:32:04.559> figure<00:32:05.159> out<00:32:05.399> how 00:32:05.870 --> 00:32:05.880 align:start position:0% active investigation to figure out how 00:32:05.880 --> 00:32:07.610 align:start position:0% active investigation to figure out how to<00:32:06.059> best 00:32:07.610 --> 00:32:07.620 align:start position:0% to best 00:32:07.620 --> 00:32:10.549 align:start position:0% to best um<00:32:07.679> democratize<00:32:08.399> that<00:32:09.120> search<00:32:09.419> okay<00:32:10.200> thank 00:32:10.549 --> 00:32:10.559 align:start position:0% um democratize that search okay thank 00:32:10.559 --> 00:32:19.370 align:start position:0% um democratize that search okay thank you 00:32:19.370 --> 00:32:19.380 align:start position:0% 00:32:19.380 --> 00:32:21.710 align:start position:0% I<00:32:19.860> guess<00:32:19.980> two<00:32:20.159> questions<00:32:20.340> on<00:32:20.640> my<00:32:20.760> end<00:32:20.940> uh<00:32:21.539> one 00:32:21.710 --> 00:32:21.720 align:start position:0% I guess two questions on my end uh one 00:32:21.720 --> 00:32:24.409 align:start position:0% I guess two questions on my end uh one great<00:32:22.340> one<00:32:23.340> is<00:32:23.580> uh<00:32:23.700> the<00:32:23.880> seaport<00:32:24.240> support 00:32:24.409 --> 00:32:24.419 align:start position:0% great one is uh the seaport support 00:32:24.419 --> 00:32:27.830 align:start position:0% great one is uh the seaport support swaps<00:32:25.080> of<00:32:25.500> nfts<00:32:26.340> uh<00:32:26.940> today 00:32:27.830 --> 00:32:27.840 align:start position:0% swaps of nfts uh today 00:32:27.840 --> 00:32:31.430 align:start position:0% swaps of nfts uh today absolutely<00:32:28.700> so<00:32:29.700> when<00:32:30.419> you<00:32:30.539> look<00:32:30.659> at<00:32:30.840> an<00:32:31.020> offer 00:32:31.430 --> 00:32:31.440 align:start position:0% absolutely so when you look at an offer 00:32:31.440 --> 00:32:34.070 align:start position:0% absolutely so when you look at an offer consideration<00:32:32.340> the<00:32:32.640> items 00:32:34.070 --> 00:32:34.080 align:start position:0% consideration the items 00:32:34.080 --> 00:32:38.930 align:start position:0% consideration the items eth<00:32:34.980> or<00:32:35.340> native<00:32:35.580> tokens<00:32:36.000> erc20<00:32:36.720> 721<00:32:37.320> 1155 00:32:38.930 --> 00:32:38.940 align:start position:0% eth or native tokens erc20 721 1155 00:32:38.940 --> 00:32:41.630 align:start position:0% eth or native tokens erc20 721 1155 any<00:32:39.720> combo<00:32:40.020> of<00:32:40.200> those<00:32:40.380> Seaport<00:32:41.100> is<00:32:41.340> totally 00:32:41.630 --> 00:32:41.640 align:start position:0% any combo of those Seaport is totally 00:32:41.640 --> 00:32:43.310 align:start position:0% any combo of those Seaport is totally fine<00:32:42.240> with 00:32:43.310 --> 00:32:43.320 align:start position:0% fine with 00:32:43.320 --> 00:32:45.950 align:start position:0% fine with the<00:32:43.380> exception<00:32:44.340> is<00:32:45.059> the<00:32:45.179> fulfilled<00:32:45.659> basic 00:32:45.950 --> 00:32:45.960 align:start position:0% the exception is the fulfilled basic 00:32:45.960 --> 00:32:49.090 align:start position:0% the exception is the fulfilled basic order<00:32:46.140> method<00:32:46.620> does<00:32:47.159> have<00:32:47.460> more<00:32:48.179> opinionated 00:32:49.090 --> 00:32:49.100 align:start position:0% order method does have more opinionated 00:32:49.100 --> 00:32:52.549 align:start position:0% order method does have more opinionated uh<00:32:50.100> subset<00:32:50.940> of<00:32:51.539> the<00:32:51.659> possible<00:32:52.020> orders<00:32:52.380> that 00:32:52.549 --> 00:32:52.559 align:start position:0% uh subset of the possible orders that 00:32:52.559 --> 00:32:53.750 align:start position:0% uh subset of the possible orders that it's<00:32:52.679> going<00:32:52.860> to<00:32:52.980> support 00:32:53.750 --> 00:32:53.760 align:start position:0% it's going to support 00:32:53.760 --> 00:32:57.409 align:start position:0% it's going to support but<00:32:54.480> yeah<00:32:54.779> Seaport<00:32:55.320> was<00:32:55.500> built<00:32:55.860> with<00:32:56.640> this 00:32:57.409 --> 00:32:57.419 align:start position:0% but yeah Seaport was built with this 00:32:57.419 --> 00:33:01.549 align:start position:0% but yeah Seaport was built with this idea<00:32:57.779> of<00:32:58.020> barter<00:32:58.500> like<00:32:58.919> nft<00:32:59.880> for<00:33:00.240> nft<00:33:00.600> as<00:33:01.440> a 00:33:01.549 --> 00:33:01.559 align:start position:0% idea of barter like nft for nft as a 00:33:01.559 --> 00:33:02.990 align:start position:0% idea of barter like nft for nft as a first<00:33:01.679> classes 00:33:02.990 --> 00:33:03.000 align:start position:0% first classes 00:33:03.000 --> 00:33:04.850 align:start position:0% first classes yeah<00:33:03.480> I<00:33:03.659> guess<00:33:03.840> the<00:33:04.020> second<00:33:04.260> question<00:33:04.500> I<00:33:04.740> have 00:33:04.850 --> 00:33:04.860 align:start position:0% yeah I guess the second question I have 00:33:04.860 --> 00:33:07.610 align:start position:0% yeah I guess the second question I have might<00:33:05.159> be<00:33:05.279> a<00:33:05.399> little<00:33:05.460> bit<00:33:06.059> um<00:33:06.480> yeah<00:33:07.020> of<00:33:07.320> a 00:33:07.610 --> 00:33:07.620 align:start position:0% might be a little bit um yeah of a 00:33:07.620 --> 00:33:10.669 align:start position:0% might be a little bit um yeah of a comparison<00:33:08.580> question<00:33:08.940> so<00:33:09.600> uh<00:33:09.960> we<00:33:10.200> we're<00:33:10.440> right 00:33:10.669 --> 00:33:10.679 align:start position:0% comparison question so uh we we're right 00:33:10.679 --> 00:33:13.430 align:start position:0% comparison question so uh we we're right now<00:33:10.799> integrated<00:33:11.159> with<00:33:11.340> like<00:33:11.460> Xerox<00:33:11.880> V3<00:33:12.360> for<00:33:13.260> uh 00:33:13.430 --> 00:33:13.440 align:start position:0% now integrated with like Xerox V3 for uh 00:33:13.440 --> 00:33:14.870 align:start position:0% now integrated with like Xerox V3 for uh awesome<00:33:13.679> for<00:33:13.980> private<00:33:14.220> Marketplace<00:33:14.580> so<00:33:14.760> I'm 00:33:14.870 --> 00:33:14.880 align:start position:0% awesome for private Marketplace so I'm 00:33:14.880 --> 00:33:16.789 align:start position:0% awesome for private Marketplace so I'm just<00:33:15.000> curious<00:33:15.299> uh<00:33:15.720> I<00:33:16.019> mean<00:33:16.140> maybe<00:33:16.559> you<00:33:16.679> can 00:33:16.789 --> 00:33:16.799 align:start position:0% just curious uh I mean maybe you can 00:33:16.799 --> 00:33:18.169 align:start position:0% just curious uh I mean maybe you can speak<00:33:16.980> to<00:33:17.159> like<00:33:17.399> some<00:33:17.580> of<00:33:17.700> the<00:33:17.760> differences 00:33:18.169 --> 00:33:18.179 align:start position:0% speak to like some of the differences 00:33:18.179 --> 00:33:20.450 align:start position:0% speak to like some of the differences between<00:33:18.600> C<00:33:19.019> port<00:33:19.260> and<00:33:19.440> Xerox<00:33:19.679> V3<00:33:19.980> does<00:33:20.279> any 00:33:20.450 --> 00:33:20.460 align:start position:0% between C port and Xerox V3 does any 00:33:20.460 --> 00:33:25.070 align:start position:0% between C port and Xerox V3 does any yeah<00:33:20.779> yeah<00:33:21.860> so<00:33:23.179> first<00:33:24.179> off<00:33:24.299> Xerox<00:33:24.720> is<00:33:24.899> really 00:33:25.070 --> 00:33:25.080 align:start position:0% yeah yeah so first off Xerox is really 00:33:25.080 --> 00:33:27.830 align:start position:0% yeah yeah so first off Xerox is really cool<00:33:25.260> they<00:33:25.980> are<00:33:26.279> definite<00:33:26.880> innovators<00:33:27.360> in<00:33:27.720> the 00:33:27.830 --> 00:33:27.840 align:start position:0% cool they are definite innovators in the 00:33:27.840 --> 00:33:28.549 align:start position:0% cool they are definite innovators in the space 00:33:28.549 --> 00:33:28.559 align:start position:0% space 00:33:28.559 --> 00:33:32.230 align:start position:0% space um<00:33:28.980> 0x<00:33:29.940> is<00:33:30.299> more<00:33:30.539> geared<00:33:31.019> around 00:33:32.230 --> 00:33:32.240 align:start position:0% um 0x is more geared around 00:33:32.240 --> 00:33:36.909 align:start position:0% um 0x is more geared around single<00:33:33.260> nft<00:33:34.260> like<00:33:35.100> buy<00:33:35.399> an<00:33:35.640> nft<00:33:35.940> sell<00:33:36.299> an<00:33:36.480> nft 00:33:36.909 --> 00:33:36.919 align:start position:0% single nft like buy an nft sell an nft 00:33:36.919 --> 00:33:39.409 align:start position:0% single nft like buy an nft sell an nft and<00:33:37.919> it's<00:33:38.279> it's<00:33:38.640> actually<00:33:38.940> a<00:33:39.120> very<00:33:39.240> good 00:33:39.409 --> 00:33:39.419 align:start position:0% and it's it's actually a very good 00:33:39.419 --> 00:33:42.110 align:start position:0% and it's it's actually a very good protocol<00:33:39.840> for<00:33:40.080> that<00:33:40.200> Seaport<00:33:40.980> is<00:33:41.340> more<00:33:41.760> geared 00:33:42.110 --> 00:33:42.120 align:start position:0% protocol for that Seaport is more geared 00:33:42.120 --> 00:33:43.310 align:start position:0% protocol for that Seaport is more geared around 00:33:43.310 --> 00:33:43.320 align:start position:0% around 00:33:43.320 --> 00:33:45.950 align:start position:0% around uh<00:33:44.039> how<00:33:44.460> do<00:33:44.580> you<00:33:44.640> how<00:33:45.120> do<00:33:45.240> you<00:33:45.299> grow<00:33:45.480> out<00:33:45.720> from 00:33:45.950 --> 00:33:45.960 align:start position:0% uh how do you how do you grow out from 00:33:45.960 --> 00:33:48.409 align:start position:0% uh how do you how do you grow out from that<00:33:46.140> there's<00:33:46.799> less 00:33:48.409 --> 00:33:48.419 align:start position:0% that there's less 00:33:48.419 --> 00:33:50.870 align:start position:0% that there's less um less<00:33:48.779> opinionated 00:33:50.870 --> 00:33:50.880 align:start position:0% um less opinionated 00:33:50.880 --> 00:33:53.269 align:start position:0% um less opinionated um<00:33:50.940> on<00:33:51.600> this<00:33:51.779> what<00:33:52.080> the<00:33:52.320> exact<00:33:52.559> structure<00:33:52.980> of<00:33:53.159> a 00:33:53.269 --> 00:33:53.279 align:start position:0% um on this what the exact structure of a 00:33:53.279 --> 00:33:55.549 align:start position:0% um on this what the exact structure of a listing<00:33:53.580> looks<00:33:53.880> like<00:33:54.200> basically<00:33:55.200> for<00:33:55.440> the 00:33:55.549 --> 00:33:55.559 align:start position:0% listing looks like basically for the 00:33:55.559 --> 00:33:57.230 align:start position:0% listing looks like basically for the exact<00:33:55.799> reasons<00:33:56.220> that<00:33:56.340> we're<00:33:56.519> just<00:33:56.760> discussing 00:33:57.230 --> 00:33:57.240 align:start position:0% exact reasons that we're just discussing 00:33:57.240 --> 00:34:00.470 align:start position:0% exact reasons that we're just discussing is<00:33:57.539> a<00:33:57.779> top<00:33:58.500> one 00:34:00.470 --> 00:34:00.480 align:start position:0% is a top one 00:34:00.480 --> 00:34:03.230 align:start position:0% is a top one um<00:34:00.539> another<00:34:01.200> thing<00:34:01.679> that<00:34:02.220> is<00:34:02.399> different<00:34:02.640> is 00:34:03.230 --> 00:34:03.240 align:start position:0% um another thing that is different is 00:34:03.240 --> 00:34:06.110 align:start position:0% um another thing that is different is that<00:34:03.960> Seaport<00:34:04.679> is<00:34:05.039> totally 00:34:06.110 --> 00:34:06.120 align:start position:0% that Seaport is totally 00:34:06.120 --> 00:34:08.690 align:start position:0% that Seaport is totally unowned<00:34:06.960> and<00:34:07.260> permissionless<00:34:07.860> there's<00:34:08.280> no 00:34:08.690 --> 00:34:08.700 align:start position:0% unowned and permissionless there's no 00:34:08.700 --> 00:34:13.070 align:start position:0% unowned and permissionless there's no special<00:34:09.599> notion<00:34:10.020> of<00:34:10.320> like<00:34:10.820> a<00:34:11.820> protocol<00:34:12.179> token 00:34:13.070 --> 00:34:13.080 align:start position:0% special notion of like a protocol token 00:34:13.080 --> 00:34:15.050 align:start position:0% special notion of like a protocol token or<00:34:13.379> a<00:34:13.560> protocol<00:34:13.859> fee<00:34:14.280> that<00:34:14.399> could<00:34:14.580> be<00:34:14.700> turned 00:34:15.050 --> 00:34:15.060 align:start position:0% or a protocol fee that could be turned 00:34:15.060 --> 00:34:17.869 align:start position:0% or a protocol fee that could be turned on<00:34:15.179> it's<00:34:15.899> just<00:34:16.139> meant<00:34:16.379> to<00:34:16.440> serve<00:34:16.740> as<00:34:16.859> a 00:34:17.869 --> 00:34:17.879 align:start position:0% on it's just meant to serve as a 00:34:17.879 --> 00:34:19.430 align:start position:0% on it's just meant to serve as a permissionless<00:34:18.659> piece<00:34:19.080> of<00:34:19.200> public 00:34:19.430 --> 00:34:19.440 align:start position:0% permissionless piece of public 00:34:19.440 --> 00:34:21.409 align:start position:0% permissionless piece of public infrastructure<00:34:20.399> on<00:34:20.580> chain 00:34:21.409 --> 00:34:21.419 align:start position:0% infrastructure on chain 00:34:21.419 --> 00:34:23.389 align:start position:0% infrastructure on chain so<00:34:21.780> that<00:34:21.899> is<00:34:22.080> a<00:34:22.200> difference 00:34:23.389 --> 00:34:23.399 align:start position:0% so that is a difference 00:34:23.399 --> 00:34:27.169 align:start position:0% so that is a difference um<00:34:23.460> and<00:34:24.419> but<00:34:25.200> yeah<00:34:25.379> big<00:34:25.919> fans<00:34:26.220> of<00:34:26.520> what<00:34:27.060> the 00:34:27.169 --> 00:34:27.179 align:start position:0% um and but yeah big fans of what the 00:34:27.179 --> 00:34:30.950 align:start position:0% um and but yeah big fans of what the Xerox<00:34:27.480> team<00:34:27.720> has<00:34:27.839> been<00:34:27.960> able<00:34:28.139> to<00:34:28.260> do<00:34:28.440> thanks 00:34:30.950 --> 00:34:30.960 align:start position:0% Xerox team has been able to do thanks 00:34:30.960 --> 00:34:35.169 align:start position:0% Xerox team has been able to do thanks positions 00:34:35.169 --> 00:34:35.179 align:start position:0% 00:34:35.179 --> 00:34:40.190 align:start position:0% over<00:34:36.179> here 00:34:40.190 --> 00:34:40.200 align:start position:0% 00:34:40.200 --> 00:34:42.530 align:start position:0% I<00:34:40.800> was<00:34:40.859> wondering<00:34:41.220> if<00:34:41.639> like<00:34:41.940> currently<00:34:42.359> on 00:34:42.530 --> 00:34:42.540 align:start position:0% I was wondering if like currently on 00:34:42.540 --> 00:34:44.990 align:start position:0% I was wondering if like currently on open<00:34:42.720> seat<00:34:43.080> using<00:34:43.500> Seaport<00:34:43.980> do<00:34:44.399> they<00:34:44.580> utilize 00:34:44.990 --> 00:34:45.000 align:start position:0% open seat using Seaport do they utilize 00:34:45.000 --> 00:34:48.290 align:start position:0% open seat using Seaport do they utilize any<00:34:45.300> like<00:34:45.599> interesting<00:34:46.200> zones<00:34:46.619> currently<00:34:47.280> or 00:34:48.290 --> 00:34:48.300 align:start position:0% any like interesting zones currently or 00:34:48.300 --> 00:34:49.790 align:start position:0% any like interesting zones currently or um<00:34:48.359> do<00:34:48.720> you<00:34:48.899> have<00:34:49.020> to<00:34:49.139> like<00:34:49.260> Define<00:34:49.500> that 00:34:49.790 --> 00:34:49.800 align:start position:0% um do you have to like Define that 00:34:49.800 --> 00:34:53.510 align:start position:0% um do you have to like Define that yourself<00:34:50.060> as<00:34:51.060> like<00:34:51.359> a<00:34:52.260> someone<00:34:52.500> who<00:34:52.859> like 00:34:53.510 --> 00:34:53.520 align:start position:0% yourself as like a someone who like 00:34:53.520 --> 00:34:56.510 align:start position:0% yourself as like a someone who like creates<00:34:54.119> a<00:34:54.240> listing<00:34:54.599> on<00:34:54.899> openc 00:34:56.510 --> 00:34:56.520 align:start position:0% creates a listing on openc 00:34:56.520 --> 00:34:57.950 align:start position:0% creates a listing on openc so<00:34:57.119> uh 00:34:57.950 --> 00:34:57.960 align:start position:0% so uh 00:34:57.960 --> 00:35:00.589 align:start position:0% so uh I<00:34:58.440> can't<00:34:58.560> speak<00:34:58.800> too<00:34:59.040> directly<00:34:59.460> for<00:34:59.760> openc<00:35:00.240> I'm 00:35:00.589 --> 00:35:00.599 align:start position:0% I can't speak too directly for openc I'm 00:35:00.599 --> 00:35:04.250 align:start position:0% I can't speak too directly for openc I'm I'm<00:35:00.960> one<00:35:01.260> of<00:35:01.380> many<00:35:01.560> uh<00:35:01.920> but<00:35:02.580> what<00:35:03.420> I<00:35:03.599> can<00:35:03.720> say<00:35:03.960> is 00:35:04.250 --> 00:35:04.260 align:start position:0% I'm one of many uh but what I can say is 00:35:04.260 --> 00:35:05.230 align:start position:0% I'm one of many uh but what I can say is that 00:35:05.230 --> 00:35:05.240 align:start position:0% that 00:35:05.240 --> 00:35:08.750 align:start position:0% that for<00:35:06.240> at<00:35:06.839> least<00:35:06.960> a<00:35:07.380> couple<00:35:07.500> of<00:35:07.680> months<00:35:08.160> after 00:35:08.750 --> 00:35:08.760 align:start position:0% for at least a couple of months after 00:35:08.760 --> 00:35:11.510 align:start position:0% for at least a couple of months after Seaport<00:35:09.420> first<00:35:09.900> went<00:35:10.140> live 00:35:11.510 --> 00:35:11.520 align:start position:0% Seaport first went live 00:35:11.520 --> 00:35:14.630 align:start position:0% Seaport first went live it<00:35:12.180> was<00:35:12.359> a<00:35:12.780> brand<00:35:13.020> new<00:35:13.260> protocol<00:35:13.680> used<00:35:14.160> a<00:35:14.520> lot 00:35:14.630 --> 00:35:14.640 align:start position:0% it was a brand new protocol used a lot 00:35:14.640 --> 00:35:17.630 align:start position:0% it was a brand new protocol used a lot of<00:35:14.760> assembly<00:35:15.240> and<00:35:15.660> and<00:35:16.200> so<00:35:16.500> we<00:35:16.800> we<00:35:17.160> kept<00:35:17.460> guard 00:35:17.630 --> 00:35:17.640 align:start position:0% of assembly and and so we we kept guard 00:35:17.640 --> 00:35:21.470 align:start position:0% of assembly and and so we we kept guard rails<00:35:18.119> on<00:35:18.240> we<00:35:18.599> used<00:35:18.780> a<00:35:19.320> global<00:35:20.160> plausible<00:35:21.000> Zone 00:35:21.470 --> 00:35:21.480 align:start position:0% rails on we used a global plausible Zone 00:35:21.480 --> 00:35:24.290 align:start position:0% rails on we used a global plausible Zone and<00:35:22.020> required<00:35:22.500> that<00:35:22.680> all<00:35:23.220> orders<00:35:23.640> that<00:35:24.000> were 00:35:24.290 --> 00:35:24.300 align:start position:0% and required that all orders that were 00:35:24.300 --> 00:35:28.310 align:start position:0% and required that all orders that were sent<00:35:24.480> to<00:35:24.780> open<00:35:25.140> sea<00:35:25.740> had<00:35:26.579> this<00:35:26.940> Zone<00:35:27.540> set<00:35:27.839> on 00:35:28.310 --> 00:35:28.320 align:start position:0% sent to open sea had this Zone set on 00:35:28.320 --> 00:35:31.870 align:start position:0% sent to open sea had this Zone set on them<00:35:28.520> and<00:35:29.520> it<00:35:29.640> would<00:35:29.760> allow<00:35:30.119> for<00:35:30.480> us<00:35:30.599> to 00:35:31.870 --> 00:35:31.880 align:start position:0% them and it would allow for us to 00:35:31.880 --> 00:35:35.569 align:start position:0% them and it would allow for us to basically<00:35:32.880> hit<00:35:33.420> the<00:35:33.660> panic<00:35:33.960> button<00:35:34.320> and<00:35:34.800> just 00:35:35.569 --> 00:35:35.579 align:start position:0% basically hit the panic button and just 00:35:35.579 --> 00:35:37.849 align:start position:0% basically hit the panic button and just cancel<00:35:35.880> every<00:35:36.359> single<00:35:36.660> order<00:35:36.780> if<00:35:37.440> there<00:35:37.619> was<00:35:37.740> a 00:35:37.849 --> 00:35:37.859 align:start position:0% cancel every single order if there was a 00:35:37.859 --> 00:35:39.829 align:start position:0% cancel every single order if there was a problem<00:35:38.040> with<00:35:38.339> the<00:35:38.460> marketplace 00:35:39.829 --> 00:35:39.839 align:start position:0% problem with the marketplace 00:35:39.839 --> 00:35:42.770 align:start position:0% problem with the marketplace it's<00:35:40.680> now<00:35:40.980> been<00:35:41.339> long<00:35:41.760> enough 00:35:42.770 --> 00:35:42.780 align:start position:0% it's now been long enough 00:35:42.780 --> 00:35:45.109 align:start position:0% it's now been long enough and<00:35:43.560> there<00:35:43.859> are<00:35:43.980> enough<00:35:44.160> interesting<00:35:44.880> use 00:35:45.109 --> 00:35:45.119 align:start position:0% and there are enough interesting use 00:35:45.119 --> 00:35:47.450 align:start position:0% and there are enough interesting use cases<00:35:45.480> for<00:35:45.720> zones<00:35:46.020> that 00:35:47.450 --> 00:35:47.460 align:start position:0% cases for zones that 00:35:47.460 --> 00:35:49.910 align:start position:0% cases for zones that um<00:35:47.579> efforts<00:35:48.359> are<00:35:48.480> underway<00:35:49.020> to<00:35:49.440> really<00:35:49.680> open 00:35:49.910 --> 00:35:49.920 align:start position:0% um efforts are underway to really open 00:35:49.920 --> 00:35:52.510 align:start position:0% um efforts are underway to really open that<00:35:50.160> up<00:35:50.339> other<00:35:50.700> other<00:35:51.300> chains<00:35:51.900> off<00:35:52.079> of 00:35:52.510 --> 00:35:52.520 align:start position:0% that up other other chains off of 00:35:52.520 --> 00:35:56.030 align:start position:0% that up other other chains off of mainnet<00:35:53.520> don't<00:35:54.359> currently<00:35:54.660> use<00:35:54.900> its<00:35:55.200> own 00:35:56.030 --> 00:35:56.040 align:start position:0% mainnet don't currently use its own 00:35:56.040 --> 00:35:57.890 align:start position:0% mainnet don't currently use its own so 00:35:57.890 --> 00:35:57.900 align:start position:0% so 00:35:57.900 --> 00:36:01.730 align:start position:0% so stay<00:35:58.320> tuned<00:35:58.619> stay<00:35:59.220> tuned<00:35:59.400> on<00:35:59.640> that<00:35:59.820> and<00:36:00.200> uh<00:36:01.200> I 00:36:01.730 --> 00:36:01.740 align:start position:0% stay tuned stay tuned on that and uh I 00:36:01.740 --> 00:36:04.010 align:start position:0% stay tuned stay tuned on that and uh I will<00:36:01.920> also<00:36:02.460> say<00:36:02.760> that<00:36:03.060> if<00:36:03.300> anyone<00:36:03.660> is 00:36:04.010 --> 00:36:04.020 align:start position:0% will also say that if anyone is 00:36:04.020 --> 00:36:06.770 align:start position:0% will also say that if anyone is authoring<00:36:04.500> zones<00:36:04.800> or<00:36:05.040> working<00:36:05.280> on<00:36:05.579> them 00:36:06.770 --> 00:36:06.780 align:start position:0% authoring zones or working on them 00:36:06.780 --> 00:36:09.710 align:start position:0% authoring zones or working on them get<00:36:07.380> in<00:36:07.560> touch<00:36:07.740> let<00:36:08.400> us<00:36:08.579> know<00:36:08.760> we'll 00:36:09.710 --> 00:36:09.720 align:start position:0% get in touch let us know we'll 00:36:09.720 --> 00:36:12.710 align:start position:0% get in touch let us know we'll definitely<00:36:10.140> it<00:36:11.040> would<00:36:11.460> go<00:36:11.700> a<00:36:11.880> long<00:36:12.000> way<00:36:12.240> to 00:36:12.710 --> 00:36:12.720 align:start position:0% definitely it would go a long way to 00:36:12.720 --> 00:36:13.910 align:start position:0% definitely it would go a long way to help 00:36:13.910 --> 00:36:13.920 align:start position:0% help 00:36:13.920 --> 00:36:15.650 align:start position:0% help um<00:36:13.980> see<00:36:14.400> what<00:36:14.579> zones<00:36:14.820> people<00:36:15.060> are<00:36:15.240> coming<00:36:15.420> up 00:36:15.650 --> 00:36:15.660 align:start position:0% um see what zones people are coming up 00:36:15.660 --> 00:36:17.030 align:start position:0% um see what zones people are coming up with<00:36:15.839> and 00:36:17.030 --> 00:36:17.040 align:start position:0% with and 00:36:17.040 --> 00:36:20.450 align:start position:0% with and um<00:36:17.480> and<00:36:18.480> that<00:36:18.900> will<00:36:19.079> definitely<00:36:19.380> inform<00:36:19.859> the 00:36:20.450 --> 00:36:20.460 align:start position:0% um and that will definitely inform the 00:36:20.460 --> 00:36:23.450 align:start position:0% um and that will definitely inform the discussion<00:36:20.940> and<00:36:21.660> efforts 00:36:23.450 --> 00:36:23.460 align:start position:0% discussion and efforts 00:36:23.460 --> 00:36:31.609 align:start position:0% discussion and efforts foreign 00:36:31.609 --> 00:36:31.619 align:start position:0% 00:36:31.619 --> 00:36:34.490 align:start position:0% we're<00:36:32.220> having<00:36:32.460> issues<00:36:33.060> with<00:36:33.540> signature 00:36:34.490 --> 00:36:34.500 align:start position:0% we're having issues with signature 00:36:34.500 --> 00:36:37.490 align:start position:0% we're having issues with signature verification<00:36:35.240> where<00:36:36.240> recovered<00:36:36.900> signatures 00:36:37.490 --> 00:36:37.500 align:start position:0% verification where recovered signatures 00:36:37.500 --> 00:36:40.670 align:start position:0% verification where recovered signatures match<00:36:38.099> the<00:36:38.400> original<00:36:38.579> signer<00:36:39.359> but<00:36:40.140> orders 00:36:40.670 --> 00:36:40.680 align:start position:0% match the original signer but orders 00:36:40.680 --> 00:36:42.050 align:start position:0% match the original signer but orders fail 00:36:42.050 --> 00:36:42.060 align:start position:0% fail 00:36:42.060 --> 00:36:46.510 align:start position:0% fail interesting<00:36:43.020> okay<00:36:43.380> and<00:36:44.339> it's<00:36:44.940> I've<00:36:45.660> it's<00:36:46.200> been 00:36:46.510 --> 00:36:46.520 align:start position:0% interesting okay and it's I've it's been 00:36:46.520 --> 00:36:49.609 align:start position:0% interesting okay and it's I've it's been unsolvable<00:36:47.520> for<00:36:47.820> me<00:36:48.000> so<00:36:48.839> what<00:36:49.020> are<00:36:49.200> reasons 00:36:49.609 --> 00:36:49.619 align:start position:0% unsolvable for me so what are reasons 00:36:49.619 --> 00:36:51.650 align:start position:0% unsolvable for me so what are reasons this<00:36:49.800> could<00:36:49.980> be<00:36:50.160> okay 00:36:51.650 --> 00:36:51.660 align:start position:0% this could be okay 00:36:51.660 --> 00:36:54.530 align:start position:0% this could be okay so<00:36:52.260> if<00:36:52.619> you<00:36:52.920> have<00:36:53.099> if<00:36:53.640> you<00:36:53.820> have<00:36:54.000> an<00:36:54.240> order 00:36:54.530 --> 00:36:54.540 align:start position:0% so if you have if you have an order 00:36:54.540 --> 00:36:58.310 align:start position:0% so if you have if you have an order that's<00:36:55.280> signed<00:36:56.280> and<00:36:56.760> the<00:36:57.240> signature<00:36:57.720> is<00:36:57.839> valid 00:36:58.310 --> 00:36:58.320 align:start position:0% that's signed and the signature is valid 00:36:58.320 --> 00:37:00.230 align:start position:0% that's signed and the signature is valid right<00:36:58.680> like<00:36:58.859> you<00:36:59.160> can<00:36:59.339> recover<00:36:59.640> the<00:36:59.880> signature 00:37:00.230 --> 00:37:00.240 align:start position:0% right like you can recover the signature 00:37:00.240 --> 00:37:01.310 align:start position:0% right like you can recover the signature and<00:37:00.359> it<00:37:00.540> works 00:37:01.310 --> 00:37:01.320 align:start position:0% and it works 00:37:01.320 --> 00:37:04.490 align:start position:0% and it works there<00:37:02.099> are<00:37:02.339> a<00:37:02.880> number<00:37:03.060> of<00:37:03.300> potential<00:37:04.200> things 00:37:04.490 --> 00:37:04.500 align:start position:0% there are a number of potential things 00:37:04.500 --> 00:37:06.650 align:start position:0% there are a number of potential things that<00:37:04.800> you<00:37:04.920> could<00:37:05.040> look<00:37:05.220> into<00:37:05.400> the<00:37:06.180> first<00:37:06.359> would 00:37:06.650 --> 00:37:06.660 align:start position:0% that you could look into the first would 00:37:06.660 --> 00:37:09.410 align:start position:0% that you could look into the first would be<00:37:06.839> checking<00:37:07.680> the<00:37:07.920> order<00:37:08.099> validator<00:37:08.820> right 00:37:09.410 --> 00:37:09.420 align:start position:0% be checking the order validator right 00:37:09.420 --> 00:37:12.470 align:start position:0% be checking the order validator right that's<00:37:10.320> that's<00:37:11.040> going<00:37:11.339> to<00:37:11.520> scan<00:37:12.000> through<00:37:12.240> and 00:37:12.470 --> 00:37:12.480 align:start position:0% that's that's going to scan through and 00:37:12.480 --> 00:37:14.930 align:start position:0% that's that's going to scan through and give<00:37:12.780> you<00:37:12.900> a<00:37:13.320> number<00:37:13.500> of<00:37:13.680> potential<00:37:14.220> problems 00:37:14.930 --> 00:37:14.940 align:start position:0% give you a number of potential problems 00:37:14.940 --> 00:37:17.150 align:start position:0% give you a number of potential problems when<00:37:15.599> you<00:37:15.720> go<00:37:15.839> to<00:37:15.960> try<00:37:16.140> and<00:37:16.260> fulfill<00:37:16.560> it<00:37:16.800> and 00:37:17.150 --> 00:37:17.160 align:start position:0% when you go to try and fulfill it and 00:37:17.160 --> 00:37:19.550 align:start position:0% when you go to try and fulfill it and that's<00:37:17.339> actually<00:37:17.599> it's<00:37:18.599> a<00:37:18.839> very<00:37:19.020> important 00:37:19.550 --> 00:37:19.560 align:start position:0% that's actually it's a very important 00:37:19.560 --> 00:37:23.030 align:start position:0% that's actually it's a very important thing<00:37:20.160> if<00:37:20.460> you<00:37:20.760> are<00:37:21.119> maintaining<00:37:21.780> uh<00:37:22.680> listings 00:37:23.030 --> 00:37:23.040 align:start position:0% thing if you are maintaining uh listings 00:37:23.040 --> 00:37:25.670 align:start position:0% thing if you are maintaining uh listings and<00:37:23.280> offers<00:37:23.660> you<00:37:24.660> have<00:37:24.780> to<00:37:25.020> ensure<00:37:25.440> that 00:37:25.670 --> 00:37:25.680 align:start position:0% and offers you have to ensure that 00:37:25.680 --> 00:37:29.030 align:start position:0% and offers you have to ensure that you're<00:37:25.920> not<00:37:26.160> putting<00:37:27.000> listings<00:37:27.480> out<00:37:28.040> that 00:37:29.030 --> 00:37:29.040 align:start position:0% you're not putting listings out that 00:37:29.040 --> 00:37:32.390 align:start position:0% you're not putting listings out that aren't<00:37:29.460> fulfillable<00:37:29.940> right<00:37:30.480> so 00:37:32.390 --> 00:37:32.400 align:start position:0% aren't fulfillable right so 00:37:32.400 --> 00:37:34.250 align:start position:0% aren't fulfillable right so um<00:37:32.460> that's<00:37:32.700> one<00:37:33.000> thing<00:37:33.180> to<00:37:33.480> try<00:37:33.660> another 00:37:34.250 --> 00:37:34.260 align:start position:0% um that's one thing to try another 00:37:34.260 --> 00:37:37.670 align:start position:0% um that's one thing to try another Seaport<00:37:35.220> has<00:37:35.460> this<00:37:35.640> notion<00:37:35.940> of<00:37:36.300> a<00:37:36.540> counter 00:37:37.670 --> 00:37:37.680 align:start position:0% Seaport has this notion of a counter 00:37:37.680 --> 00:37:38.930 align:start position:0% Seaport has this notion of a counter so 00:37:38.930 --> 00:37:38.940 align:start position:0% so 00:37:38.940 --> 00:37:41.990 align:start position:0% so every<00:37:39.780> single<00:37:40.200> offerer<00:37:40.859> has<00:37:41.339> a<00:37:41.579> counter 00:37:41.990 --> 00:37:42.000 align:start position:0% every single offerer has a counter 00:37:42.000 --> 00:37:44.750 align:start position:0% every single offerer has a counter that's<00:37:42.560> tracked<00:37:43.560> independent<00:37:44.220> of<00:37:44.460> all<00:37:44.579> of 00:37:44.750 --> 00:37:44.760 align:start position:0% that's tracked independent of all of 00:37:44.760 --> 00:37:47.510 align:start position:0% that's tracked independent of all of their<00:37:44.880> orders<00:37:45.380> and<00:37:46.380> at<00:37:46.680> any<00:37:46.920> point<00:37:47.160> you<00:37:47.460> can 00:37:47.510 --> 00:37:47.520 align:start position:0% their orders and at any point you can 00:37:47.520 --> 00:37:49.670 align:start position:0% their orders and at any point you can just<00:37:47.700> call<00:37:48.000> increment<00:37:48.839> counter<00:37:49.260> and<00:37:49.500> that 00:37:49.670 --> 00:37:49.680 align:start position:0% just call increment counter and that 00:37:49.680 --> 00:37:52.430 align:start position:0% just call increment counter and that serves<00:37:49.980> as<00:37:50.280> an<00:37:50.940> eject<00:37:51.180> button<00:37:51.599> where<00:37:51.960> all<00:37:52.260> the 00:37:52.430 --> 00:37:52.440 align:start position:0% serves as an eject button where all the 00:37:52.440 --> 00:37:55.130 align:start position:0% serves as an eject button where all the orders<00:37:52.680> that<00:37:52.920> are<00:37:53.040> signed<00:37:53.400> with<00:37:53.579> that<00:37:53.820> counter 00:37:55.130 --> 00:37:55.140 align:start position:0% orders that are signed with that counter 00:37:55.140 --> 00:37:58.270 align:start position:0% orders that are signed with that counter are<00:37:55.859> now<00:37:56.220> invalid 00:37:58.270 --> 00:37:58.280 align:start position:0% are now invalid 00:37:58.280 --> 00:38:01.190 align:start position:0% are now invalid interestingly<00:37:59.280> though 00:38:01.190 --> 00:38:01.200 align:start position:0% interestingly though 00:38:01.200 --> 00:38:03.770 align:start position:0% interestingly though you<00:38:01.859> don't<00:38:02.040> Supply<00:38:02.400> the<00:38:02.880> counter<00:38:03.240> as<00:38:03.540> an 00:38:03.770 --> 00:38:03.780 align:start position:0% you don't Supply the counter as an 00:38:03.780 --> 00:38:06.290 align:start position:0% you don't Supply the counter as an explicit<00:38:04.260> argument<00:38:04.680> it's<00:38:05.160> an<00:38:05.520> implied 00:38:06.290 --> 00:38:06.300 align:start position:0% explicit argument it's an implied 00:38:06.300 --> 00:38:07.550 align:start position:0% explicit argument it's an implied argument 00:38:07.550 --> 00:38:07.560 align:start position:0% argument 00:38:07.560 --> 00:38:11.170 align:start position:0% argument so<00:38:08.339> if<00:38:08.820> you<00:38:09.000> have<00:38:09.300> two<00:38:10.079> identical<00:38:10.619> orders 00:38:11.170 --> 00:38:11.180 align:start position:0% so if you have two identical orders 00:38:11.180 --> 00:38:14.329 align:start position:0% so if you have two identical orders except<00:38:12.180> one<00:38:12.420> has<00:38:12.660> counter<00:38:13.079> zero<00:38:13.560> one<00:38:14.099> has 00:38:14.329 --> 00:38:14.339 align:start position:0% except one has counter zero one has 00:38:14.339 --> 00:38:16.550 align:start position:0% except one has counter zero one has counter<00:38:14.820> one<00:38:15.000> they'll<00:38:15.839> have<00:38:16.020> different<00:38:16.200> order 00:38:16.550 --> 00:38:16.560 align:start position:0% counter one they'll have different order 00:38:16.560 --> 00:38:19.790 align:start position:0% counter one they'll have different order hashes<00:38:17.160> but<00:38:18.119> the<00:38:18.660> call<00:38:18.839> is<00:38:19.140> the<00:38:19.380> same<00:38:19.500> so 00:38:19.790 --> 00:38:19.800 align:start position:0% hashes but the call is the same so 00:38:19.800 --> 00:38:22.970 align:start position:0% hashes but the call is the same so that's<00:38:19.980> one<00:38:20.520> potential<00:38:21.060> area<00:38:21.300> that 00:38:22.970 --> 00:38:22.980 align:start position:0% that's one potential area that 00:38:22.980 --> 00:38:24.890 align:start position:0% that's one potential area that um you<00:38:23.280> can<00:38:23.400> run<00:38:23.520> into<00:38:23.700> issues 00:38:24.890 --> 00:38:24.900 align:start position:0% um you can run into issues 00:38:24.900 --> 00:38:28.849 align:start position:0% um you can run into issues the<00:38:25.560> last<00:38:25.740> thing<00:38:26.099> I<00:38:26.400> will<00:38:26.520> say<00:38:26.760> is<00:38:27.300> that<00:38:28.200> cases 00:38:28.849 --> 00:38:28.859 align:start position:0% the last thing I will say is that cases 00:38:28.859 --> 00:38:30.829 align:start position:0% the last thing I will say is that cases where<00:38:29.099> there's<00:38:29.460> something<00:38:29.760> really<00:38:30.180> sticky 00:38:30.829 --> 00:38:30.839 align:start position:0% where there's something really sticky 00:38:30.839 --> 00:38:34.190 align:start position:0% where there's something really sticky that's<00:38:31.440> just<00:38:31.800> like<00:38:32.040> confusing<00:38:32.820> and<00:38:33.119> not 00:38:34.190 --> 00:38:34.200 align:start position:0% that's just like confusing and not 00:38:34.200 --> 00:38:36.410 align:start position:0% that's just like confusing and not um<00:38:34.320> not<00:38:34.920> making<00:38:35.040> sense 00:38:36.410 --> 00:38:36.420 align:start position:0% um not making sense 00:38:36.420 --> 00:38:38.750 align:start position:0% um not making sense I<00:38:36.960> would<00:38:37.140> really<00:38:37.380> encourage<00:38:38.040> you<00:38:38.160> to<00:38:38.400> go<00:38:38.520> to 00:38:38.750 --> 00:38:38.760 align:start position:0% I would really encourage you to go to 00:38:38.760 --> 00:38:40.750 align:start position:0% I would really encourage you to go to this<00:38:39.000> discussions<00:38:39.599> board 00:38:40.750 --> 00:38:40.760 align:start position:0% this discussions board 00:38:40.760 --> 00:38:43.730 align:start position:0% this discussions board both<00:38:41.760> for<00:38:42.180> it's<00:38:42.780> a<00:38:43.020> great 00:38:43.730 --> 00:38:43.740 align:start position:0% both for it's a great 00:38:43.740 --> 00:38:47.450 align:start position:0% both for it's a great Forum<00:38:44.460> to<00:38:44.940> lay<00:38:45.359> out<00:38:45.540> all<00:38:45.660> the<00:38:45.900> information<00:38:46.460> and 00:38:47.450 --> 00:38:47.460 align:start position:0% Forum to lay out all the information and 00:38:47.460 --> 00:38:50.329 align:start position:0% Forum to lay out all the information and also<00:38:48.240> for<00:38:48.480> others<00:38:48.900> to<00:38:49.200> then<00:38:49.380> benefit<00:38:49.740> from 00:38:50.329 --> 00:38:50.339 align:start position:0% also for others to then benefit from 00:38:50.339 --> 00:38:53.630 align:start position:0% also for others to then benefit from figuring<00:38:51.300> it<00:38:51.480> out<00:38:51.599> and<00:38:52.560> so<00:38:52.920> I'd<00:38:53.099> encourage<00:38:53.460> you 00:38:53.630 --> 00:38:53.640 align:start position:0% figuring it out and so I'd encourage you 00:38:53.640 --> 00:38:56.270 align:start position:0% figuring it out and so I'd encourage you to<00:38:53.880> to<00:38:54.300> do<00:38:54.599> that<00:38:54.839> but 00:38:56.270 --> 00:38:56.280 align:start position:0% to to do that but 00:38:56.280 --> 00:38:59.349 align:start position:0% to to do that but um<00:38:56.339> yeah<00:38:56.940> signatures<00:38:57.540> are<00:38:57.900> are<00:38:58.380> notoriously 00:38:59.349 --> 00:38:59.359 align:start position:0% um yeah signatures are are notoriously 00:38:59.359 --> 00:39:03.170 align:start position:0% um yeah signatures are are notoriously finicky<00:39:00.359> to<00:39:00.540> work<00:39:00.660> with<00:39:00.839> and<00:39:01.320> it<00:39:02.280> every<00:39:02.760> every 00:39:03.170 --> 00:39:03.180 align:start position:0% finicky to work with and it every every 00:39:03.180 --> 00:39:06.349 align:start position:0% finicky to work with and it every every developer<00:39:03.780> that's<00:39:04.079> that's<00:39:04.560> had<00:39:04.920> to<00:39:05.220> work<00:39:06.119> with 00:39:06.349 --> 00:39:06.359 align:start position:0% developer that's that's had to work with 00:39:06.359 --> 00:39:08.510 align:start position:0% developer that's that's had to work with them<00:39:06.560> that<00:39:07.560> there's<00:39:07.859> always<00:39:07.980> a<00:39:08.220> sense<00:39:08.339> of 00:39:08.510 --> 00:39:08.520 align:start position:0% them that there's always a sense of 00:39:08.520 --> 00:39:09.770 align:start position:0% them that there's always a sense of relief<00:39:08.760> when<00:39:09.000> you<00:39:09.180> finally<00:39:09.420> get<00:39:09.660> your 00:39:09.770 --> 00:39:09.780 align:start position:0% relief when you finally get your 00:39:09.780 --> 00:39:12.109 align:start position:0% relief when you finally get your workflow<00:39:10.200> figured<00:39:10.619> out<00:39:10.740> and<00:39:11.220> and<00:39:11.880> the 00:39:12.109 --> 00:39:12.119 align:start position:0% workflow figured out and and the 00:39:12.119 --> 00:39:14.750 align:start position:0% workflow figured out and and the signatures<00:39:12.599> are<00:39:12.960> working<00:39:13.200> because<00:39:13.560> it<00:39:14.520> can<00:39:14.640> be 00:39:14.750 --> 00:39:14.760 align:start position:0% signatures are working because it can be 00:39:14.760 --> 00:39:17.870 align:start position:0% signatures are working because it can be quite<00:39:15.000> opaque<00:39:15.660> why<00:39:16.140> things<00:39:16.320> are<00:39:16.500> going<00:39:16.680> wrong 00:39:17.870 --> 00:39:17.880 align:start position:0% quite opaque why things are going wrong 00:39:17.880 --> 00:39:20.329 align:start position:0% quite opaque why things are going wrong the<00:39:18.480> counters<00:39:18.900> though<00:39:19.200> uh<00:39:19.680> they<00:39:19.980> only<00:39:20.099> get 00:39:20.329 --> 00:39:20.339 align:start position:0% the counters though uh they only get 00:39:20.339 --> 00:39:22.730 align:start position:0% the counters though uh they only get incremented<00:39:20.940> when<00:39:21.240> you<00:39:21.420> cancel<00:39:21.599> an<00:39:21.960> order 00:39:22.730 --> 00:39:22.740 align:start position:0% incremented when you cancel an order 00:39:22.740 --> 00:39:25.430 align:start position:0% incremented when you cancel an order so<00:39:23.339> it's<00:39:23.760> actually<00:39:24.060> not<00:39:24.420> related<00:39:24.780> to 00:39:25.430 --> 00:39:25.440 align:start position:0% so it's actually not related to 00:39:25.440 --> 00:39:29.089 align:start position:0% so it's actually not related to canceling<00:39:26.339> when<00:39:27.180> I<00:39:27.480> call<00:39:27.720> cancel<00:39:28.320> on<00:39:28.740> an<00:39:28.920> order 00:39:29.089 --> 00:39:29.099 align:start position:0% canceling when I call cancel on an order 00:39:29.099 --> 00:39:32.569 align:start position:0% canceling when I call cancel on an order that<00:39:30.000> cancels<00:39:30.480> a<00:39:31.020> specific<00:39:31.440> order<00:39:31.800> and<00:39:32.460> that's 00:39:32.569 --> 00:39:32.579 align:start position:0% that cancels a specific order and that's 00:39:32.579 --> 00:39:34.130 align:start position:0% that cancels a specific order and that's actually<00:39:32.820> one<00:39:33.000> of<00:39:33.119> the<00:39:33.180> only<00:39:33.300> times<00:39:33.540> you<00:39:33.900> do 00:39:34.130 --> 00:39:34.140 align:start position:0% actually one of the only times you do 00:39:34.140 --> 00:39:37.910 align:start position:0% actually one of the only times you do explicitly<00:39:34.980> provide<00:39:35.880> the<00:39:36.119> counter<00:39:37.020> so<00:39:37.560> it's 00:39:37.910 --> 00:39:37.920 align:start position:0% explicitly provide the counter so it's 00:39:37.920 --> 00:39:40.550 align:start position:0% explicitly provide the counter so it's saying<00:39:38.280> here's<00:39:38.880> a<00:39:39.060> particular<00:39:39.359> order<00:39:39.720> that<00:39:40.380> I 00:39:40.550 --> 00:39:40.560 align:start position:0% saying here's a particular order that I 00:39:40.560 --> 00:39:42.950 align:start position:0% saying here's a particular order that I want<00:39:40.740> to<00:39:40.980> cancel<00:39:41.220> when<00:39:42.060> you<00:39:42.240> call<00:39:42.420> increment 00:39:42.950 --> 00:39:42.960 align:start position:0% want to cancel when you call increment 00:39:42.960 --> 00:39:45.589 align:start position:0% want to cancel when you call increment counter<00:39:43.380> you<00:39:43.560> don't<00:39:43.680> provide<00:39:44.040> any<00:39:44.339> arguments 00:39:45.589 --> 00:39:45.599 align:start position:0% counter you don't provide any arguments 00:39:45.599 --> 00:39:48.349 align:start position:0% counter you don't provide any arguments you<00:39:46.200> just<00:39:46.320> call<00:39:46.560> increment<00:39:46.980> counter<00:39:47.400> and<00:39:48.119> it 00:39:48.349 --> 00:39:48.359 align:start position:0% you just call increment counter and it 00:39:48.359 --> 00:39:50.990 align:start position:0% you just call increment counter and it cancels<00:39:49.099> all<00:39:50.099> of<00:39:50.220> your<00:39:50.400> orders<00:39:50.640> that<00:39:50.880> were 00:39:50.990 --> 00:39:51.000 align:start position:0% cancels all of your orders that were 00:39:51.000 --> 00:39:53.030 align:start position:0% cancels all of your orders that were signed<00:39:51.300> with<00:39:51.480> that<00:39:51.720> counter 00:39:53.030 --> 00:39:53.040 align:start position:0% signed with that counter 00:39:53.040 --> 00:39:54.190 align:start position:0% signed with that counter yeah 00:39:54.190 --> 00:39:54.200 align:start position:0% yeah 00:39:54.200 --> 00:39:56.630 align:start position:0% yeah two<00:39:55.200> distinct<00:39:55.560> things 00:39:56.630 --> 00:39:56.640 align:start position:0% two distinct things 00:39:56.640 --> 00:40:00.349 align:start position:0% two distinct things thank<00:39:57.599> you 00:40:00.349 --> 00:40:00.359 align:start position:0% 00:40:00.359 --> 00:40:03.650 align:start position:0% other<00:40:00.780> questions 00:40:03.650 --> 00:40:03.660 align:start position:0% 00:40:03.660 --> 00:40:08.329 align:start position:0% okay<00:40:04.400> uh<00:40:05.400> how<00:40:06.359> are<00:40:06.480> we<00:40:06.540> doing<00:40:06.660> on<00:40:06.780> time 00:40:08.329 --> 00:40:08.339 align:start position:0% okay uh how are we doing on time 00:40:08.339 --> 00:40:11.030 align:start position:0% okay uh how are we doing on time all<00:40:08.820> right<00:40:09.000> uh 00:40:11.030 --> 00:40:11.040 align:start position:0% all right uh 00:40:11.040 --> 00:40:13.970 align:start position:0% all right uh well<00:40:11.960> I<00:40:12.960> guess 00:40:13.970 --> 00:40:13.980 align:start position:0% well I guess 00:40:13.980 --> 00:40:16.609 align:start position:0% well I guess we've<00:40:14.460> got<00:40:14.579> we<00:40:14.760> got<00:40:14.880> another<00:40:15.060> 10<00:40:15.359> minutes 00:40:16.609 --> 00:40:16.619 align:start position:0% we've got we got another 10 minutes 00:40:16.619 --> 00:40:18.650 align:start position:0% we've got we got another 10 minutes maybe<00:40:17.040> we<00:40:17.220> could<00:40:17.400> all<00:40:17.579> Workshop<00:40:18.000> oh<00:40:18.240> you<00:40:18.480> wanna 00:40:18.650 --> 00:40:18.660 align:start position:0% maybe we could all Workshop oh you wanna 00:40:18.660 --> 00:40:20.569 align:start position:0% maybe we could all Workshop oh you wanna you<00:40:18.839> have<00:40:19.020> another<00:40:19.079> question 00:40:20.569 --> 00:40:20.579 align:start position:0% you have another question 00:40:20.579 --> 00:40:22.730 align:start position:0% you have another question yeah<00:40:21.060> yeah 00:40:22.730 --> 00:40:22.740 align:start position:0% yeah yeah 00:40:22.740 --> 00:40:23.930 align:start position:0% yeah yeah um<00:40:22.859> I<00:40:23.160> think<00:40:23.280> this<00:40:23.400> might<00:40:23.579> be<00:40:23.700> a<00:40:23.760> little<00:40:23.820> bit 00:40:23.930 --> 00:40:23.940 align:start position:0% um I think this might be a little bit 00:40:23.940 --> 00:40:26.089 align:start position:0% um I think this might be a little bit unrelated<00:40:24.240> to<00:40:24.420> Seaport<00:40:24.780> but<00:40:25.020> more<00:40:25.320> on<00:40:25.500> the<00:40:25.619> API 00:40:26.089 --> 00:40:26.099 align:start position:0% unrelated to Seaport but more on the API 00:40:26.099 --> 00:40:28.730 align:start position:0% unrelated to Seaport but more on the API so<00:40:26.579> any<00:40:26.820> any<00:40:27.060> plans<00:40:27.420> on<00:40:27.660> your<00:40:27.780> end<00:40:27.960> to<00:40:28.380> I<00:40:28.619> guess 00:40:28.730 --> 00:40:28.740 align:start position:0% so any any plans on your end to I guess 00:40:28.740 --> 00:40:31.609 align:start position:0% so any any plans on your end to I guess make<00:40:28.920> the<00:40:29.099> API<00:40:29.880> more<00:40:30.119> Enterprise<00:40:30.420> grade<00:40:30.960> maybe 00:40:31.609 --> 00:40:31.619 align:start position:0% make the API more Enterprise grade maybe 00:40:31.619 --> 00:40:35.930 align:start position:0% make the API more Enterprise grade maybe like<00:40:31.920> a<00:40:32.099> higher<00:40:32.400> TPS<00:40:32.760> and<00:40:33.119> so<00:40:33.300> on<00:40:33.480> uh<00:40:34.200> we<00:40:35.040> are 00:40:35.930 --> 00:40:35.940 align:start position:0% like a higher TPS and so on uh we are 00:40:35.940 --> 00:40:39.589 align:start position:0% like a higher TPS and so on uh we are we're<00:40:36.599> just<00:40:36.900> focused<00:40:37.260> on<00:40:37.380> Seaport<00:40:37.920> but 00:40:39.589 --> 00:40:39.599 align:start position:0% we're just focused on Seaport but 00:40:39.599 --> 00:40:40.250 align:start position:0% we're just focused on Seaport but um 00:40:40.250 --> 00:40:40.260 align:start position:0% um 00:40:40.260 --> 00:40:42.829 align:start position:0% um definitely<00:40:41.040> get<00:40:41.520> we'll<00:40:41.880> we<00:40:42.240> can<00:40:42.420> put<00:40:42.540> you<00:40:42.660> in 00:40:42.829 --> 00:40:42.839 align:start position:0% definitely get we'll we can put you in 00:40:42.839 --> 00:40:46.010 align:start position:0% definitely get we'll we can put you in touch<00:40:43.020> with<00:40:43.380> the<00:40:43.500> API<00:40:43.859> team 00:40:46.010 --> 00:40:46.020 align:start position:0% touch with the API team 00:40:46.020 --> 00:40:48.290 align:start position:0% touch with the API team um<00:40:46.140> maybe<00:40:46.380> we<00:40:46.619> could<00:40:46.740> Workshop<00:40:47.220> uh 00:40:48.290 --> 00:40:48.300 align:start position:0% um maybe we could Workshop uh 00:40:48.300 --> 00:40:51.710 align:start position:0% um maybe we could Workshop uh an<00:40:48.720> interesting<00:40:49.079> Zone<00:40:49.380> something<00:40:50.099> that<00:40:50.940> uh 00:40:51.710 --> 00:40:51.720 align:start position:0% an interesting Zone something that uh 00:40:51.720 --> 00:40:55.069 align:start position:0% an interesting Zone something that uh that<00:40:52.500> would<00:40:52.740> add<00:40:53.579> some<00:40:53.760> new<00:40:54.000> capability<00:40:54.540> to 00:40:55.069 --> 00:40:55.079 align:start position:0% that would add some new capability to 00:40:55.079 --> 00:40:56.510 align:start position:0% that would add some new capability to the<00:40:55.500> seaport 00:40:56.510 --> 00:40:56.520 align:start position:0% the seaport 00:40:56.520 --> 00:41:01.490 align:start position:0% the seaport anyone<00:40:56.940> got<00:40:57.119> any<00:40:57.240> ideas 00:41:01.490 --> 00:41:01.500 align:start position:0% 00:41:01.500 --> 00:41:03.650 align:start position:0% something<00:41:01.859> you'd<00:41:02.160> like<00:41:02.280> to<00:41:02.400> see 00:41:03.650 --> 00:41:03.660 align:start position:0% something you'd like to see 00:41:03.660 --> 00:41:15.050 align:start position:0% something you'd like to see yeah 00:41:15.050 --> 00:41:15.060 align:start position:0% 00:41:15.060 --> 00:41:16.430 align:start position:0% um<00:41:15.119> I'm<00:41:15.359> coming<00:41:15.540> a<00:41:15.720> bit<00:41:15.839> late<00:41:15.900> so<00:41:16.079> I<00:41:16.200> suspect 00:41:16.430 --> 00:41:16.440 align:start position:0% um I'm coming a bit late so I suspect 00:41:16.440 --> 00:41:18.170 align:start position:0% um I'm coming a bit late so I suspect this<00:41:16.619> has<00:41:16.740> always<00:41:16.920> already<00:41:17.400> been<00:41:17.640> raised<00:41:18.000> but 00:41:18.170 --> 00:41:18.180 align:start position:0% this has always already been raised but 00:41:18.180 --> 00:41:20.450 align:start position:0% this has always already been raised but is<00:41:18.420> it<00:41:18.599> Poss<00:41:19.079> how<00:41:19.560> about 00:41:20.450 --> 00:41:20.460 align:start position:0% is it Poss how about 00:41:20.460 --> 00:41:23.210 align:start position:0% is it Poss how about a<00:41:21.240> Zone<00:41:21.540> where<00:41:21.900> it's<00:41:22.140> only<00:41:22.380> possible<00:41:22.800> to<00:41:22.980> make 00:41:23.210 --> 00:41:23.220 align:start position:0% a Zone where it's only possible to make 00:41:23.220 --> 00:41:26.390 align:start position:0% a Zone where it's only possible to make sales<00:41:23.700> to<00:41:24.060> certain<00:41:24.300> people 00:41:26.390 --> 00:41:26.400 align:start position:0% sales to certain people 00:41:26.400 --> 00:41:28.430 align:start position:0% sales to certain people or<00:41:27.180> I<00:41:27.359> suppose<00:41:27.540> certain<00:41:27.720> addresses<00:41:28.260> almost 00:41:28.430 --> 00:41:28.440 align:start position:0% or I suppose certain addresses almost 00:41:28.440 --> 00:41:30.470 align:start position:0% or I suppose certain addresses almost certainly<00:41:28.980> in<00:41:29.160> this<00:41:29.280> addresses<00:41:29.760> that's<00:41:30.240> very 00:41:30.470 --> 00:41:30.480 align:start position:0% certainly in this addresses that's very 00:41:30.480 --> 00:41:32.569 align:start position:0% certainly in this addresses that's very possible<00:41:30.960> yeah<00:41:31.980> um 00:41:32.569 --> 00:41:32.579 align:start position:0% possible yeah um 00:41:32.579 --> 00:41:34.730 align:start position:0% possible yeah um and<00:41:32.940> that<00:41:33.180> actually<00:41:33.359> reminds<00:41:34.020> me<00:41:34.140> of<00:41:34.440> an 00:41:34.730 --> 00:41:34.740 align:start position:0% and that actually reminds me of an 00:41:34.740 --> 00:41:35.930 align:start position:0% and that actually reminds me of an interesting 00:41:35.930 --> 00:41:35.940 align:start position:0% interesting 00:41:35.940 --> 00:41:38.930 align:start position:0% interesting Advanced<00:41:36.839> technique<00:41:37.500> that 00:41:38.930 --> 00:41:38.940 align:start position:0% Advanced technique that 00:41:38.940 --> 00:41:42.010 align:start position:0% Advanced technique that uh<00:41:39.900> is<00:41:40.440> used<00:41:40.920> for 00:41:42.010 --> 00:41:42.020 align:start position:0% uh is used for 00:41:42.020 --> 00:41:44.530 align:start position:0% uh is used for Private<00:41:43.020> Sales 00:41:44.530 --> 00:41:44.540 align:start position:0% Private Sales 00:41:44.540 --> 00:41:49.849 align:start position:0% Private Sales so<00:41:45.540> you<00:41:45.780> if<00:41:46.079> say<00:41:46.380> I<00:41:46.740> want<00:41:46.980> to<00:41:47.540> I<00:41:48.540> want<00:41:48.720> to<00:41:48.900> sell 00:41:49.849 --> 00:41:49.859 align:start position:0% so you if say I want to I want to sell 00:41:49.859 --> 00:41:53.390 align:start position:0% so you if say I want to I want to sell just<00:41:50.640> a<00:41:50.940> specific<00:41:51.180> nft<00:41:51.599> and<00:41:52.380> you<00:41:52.740> are<00:41:52.920> the<00:41:53.160> only 00:41:53.390 --> 00:41:53.400 align:start position:0% just a specific nft and you are the only 00:41:53.400 --> 00:41:55.790 align:start position:0% just a specific nft and you are the only person<00:41:53.760> that<00:41:54.060> can<00:41:54.180> buy<00:41:54.359> it 00:41:55.790 --> 00:41:55.800 align:start position:0% person that can buy it 00:41:55.800 --> 00:41:58.370 align:start position:0% person that can buy it what<00:41:56.339> does<00:41:56.520> that<00:41:56.700> look<00:41:57.240> like<00:41:57.480> right<00:41:57.900> how<00:41:58.200> would 00:41:58.370 --> 00:41:58.380 align:start position:0% what does that look like right how would 00:41:58.380 --> 00:42:01.190 align:start position:0% what does that look like right how would I<00:41:58.500> set<00:41:58.740> that<00:41:58.920> up 00:42:01.190 --> 00:42:01.200 align:start position:0% 00:42:01.200 --> 00:42:03.770 align:start position:0% one<00:42:02.040> kind<00:42:02.700> of<00:42:02.820> interesting<00:42:03.119> way<00:42:03.420> of<00:42:03.599> doing 00:42:03.770 --> 00:42:03.780 align:start position:0% one kind of interesting way of doing 00:42:03.780 --> 00:42:06.530 align:start position:0% one kind of interesting way of doing that<00:42:04.020> is<00:42:04.260> just<00:42:04.560> to<00:42:04.740> say<00:42:04.980> all<00:42:05.460> right<00:42:05.640> single 00:42:06.530 --> 00:42:06.540 align:start position:0% that is just to say all right single 00:42:06.540 --> 00:42:08.030 align:start position:0% that is just to say all right single offer<00:42:06.960> item 00:42:08.030 --> 00:42:08.040 align:start position:0% offer item 00:42:08.040 --> 00:42:09.770 align:start position:0% offer item my<00:42:08.520> nft 00:42:09.770 --> 00:42:09.780 align:start position:0% my nft 00:42:09.780 --> 00:42:15.349 align:start position:0% my nft consideration<00:42:10.560> item<00:42:11.099> one<00:42:11.900> is<00:42:12.900> eth<00:42:13.800> to<00:42:14.280> me 00:42:15.349 --> 00:42:15.359 align:start position:0% consideration item one is eth to me 00:42:15.359 --> 00:42:17.450 align:start position:0% consideration item one is eth to me consideration<00:42:16.079> item<00:42:16.560> two 00:42:17.450 --> 00:42:17.460 align:start position:0% consideration item two 00:42:17.460 --> 00:42:20.870 align:start position:0% consideration item two is<00:42:18.240> my<00:42:18.540> nft<00:42:18.900> to<00:42:19.800> you 00:42:20.870 --> 00:42:20.880 align:start position:0% is my nft to you 00:42:20.880 --> 00:42:23.470 align:start position:0% is my nft to you right<00:42:21.420> so 00:42:23.470 --> 00:42:23.480 align:start position:0% right so 00:42:23.480 --> 00:42:26.030 align:start position:0% right so I've<00:42:24.480> basically<00:42:24.780> just<00:42:25.079> set<00:42:25.320> it<00:42:25.440> all<00:42:25.560> up<00:42:25.740> but 00:42:26.030 --> 00:42:26.040 align:start position:0% I've basically just set it all up but 00:42:26.040 --> 00:42:29.450 align:start position:0% I've basically just set it all up but now<00:42:26.280> if<00:42:27.180> I<00:42:27.359> wanted<00:42:27.480> to<00:42:27.780> go<00:42:28.020> and<00:42:28.560> call<00:42:28.920> these 00:42:29.450 --> 00:42:29.460 align:start position:0% now if I wanted to go and call these 00:42:29.460 --> 00:42:32.329 align:start position:0% now if I wanted to go and call these implied<00:42:30.119> mirror<00:42:30.720> order<00:42:31.079> and<00:42:31.560> you<00:42:31.859> know<00:42:31.980> just 00:42:32.329 --> 00:42:32.339 align:start position:0% implied mirror order and you know just 00:42:32.339 --> 00:42:34.430 align:start position:0% implied mirror order and you know just fulfill<00:42:32.640> orders<00:42:33.060> on<00:42:33.300> that 00:42:34.430 --> 00:42:34.440 align:start position:0% fulfill orders on that 00:42:34.440 --> 00:42:37.130 align:start position:0% fulfill orders on that it's<00:42:34.980> not<00:42:35.220> going<00:42:35.400> to<00:42:35.579> work<00:42:35.700> because 00:42:37.130 --> 00:42:37.140 align:start position:0% it's not going to work because 00:42:37.140 --> 00:42:41.470 align:start position:0% it's not going to work because the<00:42:37.920> the<00:42:38.520> offer<00:42:39.119> item<00:42:39.540> from<00:42:40.440> me 00:42:41.470 --> 00:42:41.480 align:start position:0% the the offer item from me 00:42:41.480 --> 00:42:44.569 align:start position:0% the the offer item from me needs<00:42:42.480> to<00:42:42.599> actually<00:42:42.839> match<00:42:43.260> to<00:42:43.619> the<00:42:43.740> same 00:42:44.569 --> 00:42:44.579 align:start position:0% needs to actually match to the same 00:42:44.579 --> 00:42:46.849 align:start position:0% needs to actually match to the same order<00:42:45.060> right<00:42:45.540> the<00:42:45.780> consideration<00:42:46.260> item<00:42:46.619> on 00:42:46.849 --> 00:42:46.859 align:start position:0% order right the consideration item on 00:42:46.859 --> 00:42:48.950 align:start position:0% order right the consideration item on that<00:42:46.980> same<00:42:47.160> order<00:42:47.460> so<00:42:48.240> you<00:42:48.359> got<00:42:48.480> to<00:42:48.599> use<00:42:48.720> match 00:42:48.950 --> 00:42:48.960 align:start position:0% that same order so you got to use match 00:42:48.960 --> 00:42:51.470 align:start position:0% that same order so you got to use match orders<00:42:49.380> for<00:42:49.619> that<00:42:49.800> and<00:42:50.460> you<00:42:50.700> would<00:42:50.820> then<00:42:51.060> match 00:42:51.470 --> 00:42:51.480 align:start position:0% orders for that and you would then match 00:42:51.480 --> 00:42:53.630 align:start position:0% orders for that and you would then match it<00:42:51.660> with<00:42:51.900> an<00:42:52.020> order<00:42:52.200> from<00:42:52.560> you 00:42:53.630 --> 00:42:53.640 align:start position:0% it with an order from you 00:42:53.640 --> 00:42:57.829 align:start position:0% it with an order from you that<00:42:54.240> just<00:42:54.480> says<00:42:55.200> I'm<00:42:55.859> just<00:42:56.040> offering<00:42:56.640> the<00:42:57.480> eth 00:42:57.829 --> 00:42:57.839 align:start position:0% that just says I'm just offering the eth 00:42:57.839 --> 00:43:01.210 align:start position:0% that just says I'm just offering the eth and<00:42:58.560> there's<00:42:58.740> no<00:42:59.040> consideration<00:42:59.640> item<00:43:00.119> right 00:43:01.210 --> 00:43:01.220 align:start position:0% and there's no consideration item right 00:43:01.220 --> 00:43:04.970 align:start position:0% and there's no consideration item right so<00:43:02.220> I'm<00:43:02.520> basic<00:43:02.880> if<00:43:03.240> if<00:43:03.599> I<00:43:03.839> were<00:43:03.960> to<00:43:04.140> just 00:43:04.970 --> 00:43:04.980 align:start position:0% so I'm basic if if I were to just 00:43:04.980 --> 00:43:07.550 align:start position:0% so I'm basic if if I were to just take<00:43:05.400> that<00:43:05.640> order<00:43:05.819> and<00:43:06.480> sign<00:43:06.660> it 00:43:07.550 --> 00:43:07.560 align:start position:0% take that order and sign it 00:43:07.560 --> 00:43:10.370 align:start position:0% take that order and sign it then<00:43:08.040> it's<00:43:08.520> effectively<00:43:09.119> a<00:43:09.300> donation 00:43:10.370 --> 00:43:10.380 align:start position:0% then it's effectively a donation 00:43:10.380 --> 00:43:14.809 align:start position:0% then it's effectively a donation right<00:43:10.859> but<00:43:11.640> if<00:43:12.000> I<00:43:12.300> fulfill<00:43:13.020> it<00:43:13.200> alongside<00:43:13.859> this 00:43:14.809 --> 00:43:14.819 align:start position:0% right but if I fulfill it alongside this 00:43:14.819 --> 00:43:16.910 align:start position:0% right but if I fulfill it alongside this other<00:43:15.000> order<00:43:15.240> now<00:43:16.079> the<00:43:16.319> two<00:43:16.500> of<00:43:16.680> them<00:43:16.800> together 00:43:16.910 --> 00:43:16.920 align:start position:0% other order now the two of them together 00:43:16.920 --> 00:43:19.430 align:start position:0% other order now the two of them together make<00:43:17.460> a<00:43:17.640> complete<00:43:18.000> picture<00:43:18.180> so<00:43:19.079> that's<00:43:19.200> for 00:43:19.430 --> 00:43:19.440 align:start position:0% make a complete picture so that's for 00:43:19.440 --> 00:43:22.490 align:start position:0% make a complete picture so that's for just<00:43:19.619> a<00:43:19.740> single<00:43:19.980> private<00:43:20.339> sale<00:43:20.520> but<00:43:20.940> for 00:43:22.490 --> 00:43:22.500 align:start position:0% just a single private sale but for 00:43:22.500 --> 00:43:25.670 align:start position:0% just a single private sale but for say<00:43:23.040> I<00:43:23.280> only<00:43:23.400> want<00:43:23.700> to<00:43:23.880> sell<00:43:24.119> my<00:43:24.780> nft<00:43:25.020> if<00:43:25.560> you're 00:43:25.670 --> 00:43:25.680 align:start position:0% say I only want to sell my nft if you're 00:43:25.680 --> 00:43:28.130 align:start position:0% say I only want to sell my nft if you're on<00:43:25.920> this<00:43:26.099> allow<00:43:26.400> list<00:43:27.060> that's<00:43:27.660> easy<00:43:27.900> enough 00:43:28.130 --> 00:43:28.140 align:start position:0% on this allow list that's easy enough 00:43:28.140 --> 00:43:30.250 align:start position:0% on this allow list that's easy enough you<00:43:28.440> have<00:43:28.619> a<00:43:28.740> Zone<00:43:28.980> where<00:43:29.339> you<00:43:29.579> just<00:43:29.760> Supply 00:43:30.250 --> 00:43:30.260 align:start position:0% you have a Zone where you just Supply 00:43:30.260 --> 00:43:34.849 align:start position:0% you have a Zone where you just Supply okay<00:43:31.260> here<00:43:32.220> is<00:43:32.520> a<00:43:32.880> Merkel<00:43:33.359> proof<00:43:33.720> that<00:43:34.500> says 00:43:34.849 --> 00:43:34.859 align:start position:0% okay here is a Merkel proof that says 00:43:34.859 --> 00:43:38.870 align:start position:0% okay here is a Merkel proof that says that<00:43:35.099> the<00:43:35.760> fulfiller<00:43:36.300> the<00:43:36.540> caller<00:43:37.020> is 00:43:38.870 --> 00:43:38.880 align:start position:0% that the fulfiller the caller is 00:43:38.880 --> 00:43:41.870 align:start position:0% that the fulfiller the caller is in<00:43:39.599> the<00:43:39.780> root<00:43:40.079> right<00:43:40.560> they're<00:43:40.859> one<00:43:41.160> of<00:43:41.339> a<00:43:41.460> set 00:43:41.870 --> 00:43:41.880 align:start position:0% in the root right they're one of a set 00:43:41.880 --> 00:43:45.530 align:start position:0% in the root right they're one of a set of<00:43:42.180> people<00:43:42.480> or<00:43:42.780> I<00:43:43.560> could<00:43:43.680> check<00:43:44.040> and<00:43:44.280> see<00:43:44.520> like 00:43:45.530 --> 00:43:45.540 align:start position:0% of people or I could check and see like 00:43:45.540 --> 00:43:49.670 align:start position:0% of people or I could check and see like the<00:43:46.079> caller<00:43:46.560> has<00:43:47.339> a<00:43:47.579> balance<00:43:48.000> of<00:43:48.960> this 00:43:49.670 --> 00:43:49.680 align:start position:0% the caller has a balance of this 00:43:49.680 --> 00:43:51.109 align:start position:0% the caller has a balance of this particular<00:43:49.980> token<00:43:50.400> if<00:43:50.579> it<00:43:50.760> don't<00:43:50.819> want<00:43:50.940> it<00:43:51.060> to 00:43:51.109 --> 00:43:51.119 align:start position:0% particular token if it don't want it to 00:43:51.119 --> 00:43:52.730 align:start position:0% particular token if it don't want it to be<00:43:51.240> a<00:43:51.359> token<00:43:51.660> gated<00:43:51.900> thing<00:43:52.200> where<00:43:52.500> only 00:43:52.730 --> 00:43:52.740 align:start position:0% be a token gated thing where only 00:43:52.740 --> 00:43:55.190 align:start position:0% be a token gated thing where only someone<00:43:53.460> that<00:43:53.700> owns<00:43:54.000> this<00:43:54.119> token<00:43:54.480> can<00:43:54.780> buy<00:43:55.020> it 00:43:55.190 --> 00:43:55.200 align:start position:0% someone that owns this token can buy it 00:43:55.200 --> 00:43:57.230 align:start position:0% someone that owns this token can buy it from<00:43:55.380> me<00:43:55.560> or<00:43:55.740> something<00:43:55.980> like<00:43:56.220> that<00:43:56.819> well 00:43:57.230 --> 00:43:57.240 align:start position:0% from me or something like that well 00:43:57.240 --> 00:43:58.490 align:start position:0% from me or something like that well that's<00:43:57.420> all<00:43:57.660> actually<00:43:57.900> it's<00:43:58.260> pretty 00:43:58.490 --> 00:43:58.500 align:start position:0% that's all actually it's pretty 00:43:58.500 --> 00:44:02.030 align:start position:0% that's all actually it's pretty straightforward<00:43:59.040> to<00:43:59.579> do<00:43:59.819> with<00:43:59.940> his<00:44:00.180> own 00:44:02.030 --> 00:44:02.040 align:start position:0% straightforward to do with his own 00:44:02.040 --> 00:44:08.750 align:start position:0% straightforward to do with his own hey 00:44:08.750 --> 00:44:08.760 align:start position:0% 00:44:08.760 --> 00:44:12.650 align:start position:0% um<00:44:08.880> so<00:44:09.540> with<00:44:10.140> like<00:44:10.440> developing<00:44:11.099> new<00:44:11.339> zones 00:44:12.650 --> 00:44:12.660 align:start position:0% um so with like developing new zones 00:44:12.660 --> 00:44:14.270 align:start position:0% um so with like developing new zones um and<00:44:12.900> building<00:44:13.140> just<00:44:13.440> generally<00:44:13.800> on<00:44:13.980> top<00:44:14.160> of 00:44:14.270 --> 00:44:14.280 align:start position:0% um and building just generally on top of 00:44:14.280 --> 00:44:16.190 align:start position:0% um and building just generally on top of Seaport<00:44:14.640> like<00:44:14.880> a<00:44:15.000> new<00:44:15.119> Marketplace 00:44:16.190 --> 00:44:16.200 align:start position:0% Seaport like a new Marketplace 00:44:16.200 --> 00:44:18.530 align:start position:0% Seaport like a new Marketplace do<00:44:16.500> you<00:44:16.619> see<00:44:16.740> it<00:44:16.859> as<00:44:17.040> like 00:44:18.530 --> 00:44:18.540 align:start position:0% do you see it as like 00:44:18.540 --> 00:44:21.290 align:start position:0% do you see it as like um<00:44:19.079> like<00:44:19.500> what's<00:44:19.680> the<00:44:19.859> what<00:44:20.099> are<00:44:20.220> the<00:44:20.400> steps 00:44:21.290 --> 00:44:21.300 align:start position:0% um like what's the what are the steps 00:44:21.300 --> 00:44:23.150 align:start position:0% um like what's the what are the steps for<00:44:21.720> for<00:44:21.900> doing<00:44:22.079> that<00:44:22.260> is<00:44:22.440> that<00:44:22.560> like<00:44:22.680> create<00:44:22.920> a 00:44:23.150 --> 00:44:23.160 align:start position:0% for for doing that is that like create a 00:44:23.160 --> 00:44:25.670 align:start position:0% for for doing that is that like create a UI<00:44:23.520> that<00:44:24.119> signs<00:44:24.420> messages<00:44:24.599> and<00:44:25.079> then<00:44:25.260> create 00:44:25.670 --> 00:44:25.680 align:start position:0% UI that signs messages and then create 00:44:25.680 --> 00:44:28.190 align:start position:0% UI that signs messages and then create like<00:44:25.980> your<00:44:26.339> own<00:44:26.520> database<00:44:27.000> and<00:44:27.180> API<00:44:27.540> to<00:44:27.900> serve 00:44:28.190 --> 00:44:28.200 align:start position:0% like your own database and API to serve 00:44:28.200 --> 00:44:30.650 align:start position:0% like your own database and API to serve those<00:44:28.319> messages<00:44:29.000> uh<00:44:30.000> do<00:44:30.180> you<00:44:30.359> see<00:44:30.420> that 00:44:30.650 --> 00:44:30.660 align:start position:0% those messages uh do you see that 00:44:30.660 --> 00:44:32.210 align:start position:0% those messages uh do you see that happening<00:44:31.020> as<00:44:31.140> like<00:44:31.380> the<00:44:31.500> pattern<00:44:31.800> as<00:44:32.040> this 00:44:32.210 --> 00:44:32.220 align:start position:0% happening as like the pattern as this 00:44:32.220 --> 00:44:34.849 align:start position:0% happening as like the pattern as this scales<00:44:32.579> out<00:44:32.760> or<00:44:33.060> like<00:44:33.359> develop<00:44:34.200> the<00:44:34.380> zone<00:44:34.619> and 00:44:34.849 --> 00:44:34.859 align:start position:0% scales out or like develop the zone and 00:44:34.859 --> 00:44:37.010 align:start position:0% scales out or like develop the zone and then<00:44:35.040> like<00:44:35.339> work<00:44:35.520> with<00:44:35.700> openc<00:44:36.119> to<00:44:36.480> have<00:44:36.780> that 00:44:37.010 --> 00:44:37.020 align:start position:0% then like work with openc to have that 00:44:37.020 --> 00:44:39.170 align:start position:0% then like work with openc to have that zone<00:44:37.500> integrated<00:44:38.040> or<00:44:38.339> maybe<00:44:38.520> like<00:44:38.700> a<00:44:38.880> mix<00:44:39.000> of 00:44:39.170 --> 00:44:39.180 align:start position:0% zone integrated or maybe like a mix of 00:44:39.180 --> 00:44:43.370 align:start position:0% zone integrated or maybe like a mix of both<00:44:39.619> well<00:44:40.619> we<00:44:41.280> knew<00:44:41.700> that<00:44:42.540> the<00:44:42.900> place<00:44:43.140> to 00:44:43.370 --> 00:44:43.380 align:start position:0% both well we knew that the place to 00:44:43.380 --> 00:44:46.609 align:start position:0% both well we knew that the place to start<00:44:43.680> was<00:44:44.460> with<00:44:44.880> the<00:44:45.480> smart<00:44:45.599> contract<00:44:46.140> right 00:44:46.609 --> 00:44:46.619 align:start position:0% start was with the smart contract right 00:44:46.619 --> 00:44:48.349 align:start position:0% start was with the smart contract right the<00:44:47.160> marketplace 00:44:48.349 --> 00:44:48.359 align:start position:0% the marketplace 00:44:48.359 --> 00:44:49.849 align:start position:0% the marketplace that's 00:44:49.849 --> 00:44:49.859 align:start position:0% that's 00:44:49.859 --> 00:44:53.030 align:start position:0% that's it's<00:44:50.400> the<00:44:50.700> hardest<00:44:51.119> and<00:44:51.540> riskiest<00:44:52.020> thing<00:44:52.500> and 00:44:53.030 --> 00:44:53.040 align:start position:0% it's the hardest and riskiest thing and 00:44:53.040 --> 00:44:55.910 align:start position:0% it's the hardest and riskiest thing and most<00:44:53.220> expensive<00:44:53.760> to<00:44:54.180> get<00:44:54.359> audited<00:44:55.020> and<00:44:55.440> vetted 00:44:55.910 --> 00:44:55.920 align:start position:0% most expensive to get audited and vetted 00:44:55.920 --> 00:44:57.349 align:start position:0% most expensive to get audited and vetted and<00:44:56.280> all<00:44:56.520> of<00:44:56.640> that 00:44:57.349 --> 00:44:57.359 align:start position:0% and all of that 00:44:57.359 --> 00:45:00.670 align:start position:0% and all of that so<00:44:58.079> started<00:44:58.859> with<00:44:59.040> that<00:44:59.280> the<00:44:59.819> the<00:45:00.000> contract 00:45:00.670 --> 00:45:00.680 align:start position:0% so started with that the the contract 00:45:00.680 --> 00:45:04.750 align:start position:0% so started with that the the contract and<00:45:01.680> now<00:45:02.220> that<00:45:02.400> that's<00:45:02.579> in<00:45:02.819> place<00:45:03.260> really 00:45:04.750 --> 00:45:04.760 align:start position:0% and now that that's in place really 00:45:04.760 --> 00:45:07.730 align:start position:0% and now that that's in place really where<00:45:05.760> we<00:45:05.940> go<00:45:06.119> from<00:45:06.300> here<00:45:06.540> is 00:45:07.730 --> 00:45:07.740 align:start position:0% where we go from here is 00:45:07.740 --> 00:45:12.410 align:start position:0% where we go from here is is<00:45:08.220> uh<00:45:09.140> anyone's<00:45:10.140> guess<00:45:10.319> but<00:45:11.160> I<00:45:11.640> think<00:45:11.760> that<00:45:12.060> if 00:45:12.410 --> 00:45:12.420 align:start position:0% is uh anyone's guess but I think that if 00:45:12.420 --> 00:45:15.109 align:start position:0% is uh anyone's guess but I think that if it<00:45:13.079> really<00:45:13.619> depends<00:45:13.980> on<00:45:14.160> the<00:45:14.339> application<00:45:14.700> if 00:45:15.109 --> 00:45:15.119 align:start position:0% it really depends on the application if 00:45:15.119 --> 00:45:19.490 align:start position:0% it really depends on the application if you<00:45:15.359> have<00:45:15.599> a<00:45:16.440> particular<00:45:16.940> flavor<00:45:17.940> of<00:45:18.900> listing 00:45:19.490 --> 00:45:19.500 align:start position:0% you have a particular flavor of listing 00:45:19.500 --> 00:45:22.309 align:start position:0% you have a particular flavor of listing that<00:45:20.099> you<00:45:20.520> want<00:45:21.000> to<00:45:21.180> see<00:45:21.420> supported<00:45:21.960> in<00:45:22.140> other 00:45:22.309 --> 00:45:22.319 align:start position:0% that you want to see supported in other 00:45:22.319 --> 00:45:25.309 align:start position:0% that you want to see supported in other marketplaces<00:45:23.099> then<00:45:23.760> I<00:45:24.060> think<00:45:24.240> the<00:45:24.960> most 00:45:25.309 --> 00:45:25.319 align:start position:0% marketplaces then I think the most 00:45:25.319 --> 00:45:28.130 align:start position:0% marketplaces then I think the most expedient<00:45:25.980> route<00:45:26.460> to<00:45:26.760> do<00:45:26.940> that<00:45:27.119> would<00:45:27.420> be 00:45:28.130 --> 00:45:28.140 align:start position:0% expedient route to do that would be 00:45:28.140 --> 00:45:32.030 align:start position:0% expedient route to do that would be to<00:45:28.740> go<00:45:28.980> ahead<00:45:29.300> and<00:45:30.300> put<00:45:30.599> it<00:45:30.780> together<00:45:30.900> and<00:45:31.740> then 00:45:32.030 --> 00:45:32.040 align:start position:0% to go ahead and put it together and then 00:45:32.040 --> 00:45:34.730 align:start position:0% to go ahead and put it together and then shop<00:45:32.400> it<00:45:32.640> around<00:45:32.760> and<00:45:33.599> sort<00:45:34.380> of<00:45:34.440> like<00:45:34.560> I 00:45:34.730 --> 00:45:34.740 align:start position:0% shop it around and sort of like I 00:45:34.740 --> 00:45:37.190 align:start position:0% shop it around and sort of like I mentioned<00:45:35.040> earlier<00:45:35.460> you<00:45:36.060> know<00:45:36.180> I<00:45:36.540> would<00:45:36.720> we 00:45:37.190 --> 00:45:37.200 align:start position:0% mentioned earlier you know I would we 00:45:37.200 --> 00:45:40.130 align:start position:0% mentioned earlier you know I would we would<00:45:37.440> love<00:45:37.740> to<00:45:38.640> to<00:45:39.240> see<00:45:39.540> what<00:45:39.780> people<00:45:39.900> are 00:45:40.130 --> 00:45:40.140 align:start position:0% would love to to see what people are 00:45:40.140 --> 00:45:42.770 align:start position:0% would love to to see what people are working<00:45:40.319> on<00:45:40.619> zones<00:45:41.460> they're<00:45:41.640> creating<00:45:42.060> and 00:45:42.770 --> 00:45:42.780 align:start position:0% working on zones they're creating and 00:45:42.780 --> 00:45:44.329 align:start position:0% working on zones they're creating and that<00:45:43.020> would<00:45:43.200> really<00:45:43.380> help<00:45:43.619> expedite<00:45:44.220> the 00:45:44.329 --> 00:45:44.339 align:start position:0% that would really help expedite the 00:45:44.339 --> 00:45:46.069 align:start position:0% that would really help expedite the process<00:45:44.579> and<00:45:44.760> help<00:45:44.880> standardize<00:45:45.540> around 00:45:46.069 --> 00:45:46.079 align:start position:0% process and help standardize around 00:45:46.079 --> 00:45:48.650 align:start position:0% process and help standardize around certain<00:45:47.040> zones<00:45:47.400> that<00:45:47.700> do<00:45:48.000> specific<00:45:48.359> things 00:45:48.650 --> 00:45:48.660 align:start position:0% certain zones that do specific things 00:45:48.660 --> 00:45:50.510 align:start position:0% certain zones that do specific things really<00:45:48.960> well 00:45:50.510 --> 00:45:50.520 align:start position:0% really well 00:45:50.520 --> 00:45:52.510 align:start position:0% really well they're<00:45:50.700> creating<00:45:51.000> a<00:45:51.240> brand<00:45:51.599> new<00:45:51.780> Marketplace 00:45:52.510 --> 00:45:52.520 align:start position:0% they're creating a brand new Marketplace 00:45:52.520 --> 00:45:56.030 align:start position:0% they're creating a brand new Marketplace from<00:45:53.520> from<00:45:54.000> the<00:45:54.240> ground<00:45:54.359> up<00:45:54.660> I<00:45:55.500> think<00:45:55.619> that's 00:45:56.030 --> 00:45:56.040 align:start position:0% from from the ground up I think that's 00:45:56.040 --> 00:45:58.910 align:start position:0% from from the ground up I think that's it<00:45:56.640> there<00:45:56.880> still<00:45:57.119> is<00:45:57.300> very<00:45:57.540> much<00:45:57.920> a 00:45:58.910 --> 00:45:58.920 align:start position:0% it there still is very much a 00:45:58.920 --> 00:46:00.290 align:start position:0% it there still is very much a traditional 00:46:00.290 --> 00:46:00.300 align:start position:0% traditional 00:46:00.300 --> 00:46:00.890 align:start position:0% traditional um 00:46:00.890 --> 00:46:00.900 align:start position:0% um 00:46:00.900 --> 00:46:03.950 align:start position:0% um web<00:46:01.440> 2<00:46:01.740> component<00:46:02.220> to<00:46:02.400> it<00:46:02.579> that<00:46:03.359> would<00:46:03.540> need<00:46:03.720> to 00:46:03.950 --> 00:46:03.960 align:start position:0% web 2 component to it that would need to 00:46:03.960 --> 00:46:05.210 align:start position:0% web 2 component to it that would need to be 00:46:05.210 --> 00:46:05.220 align:start position:0% be 00:46:05.220 --> 00:46:07.609 align:start position:0% be um it<00:46:05.880> would<00:46:06.060> need<00:46:06.180> to<00:46:06.300> be<00:46:06.420> undertaken<00:46:07.200> at 00:46:07.609 --> 00:46:07.619 align:start position:0% um it would need to be undertaken at 00:46:07.619 --> 00:46:09.829 align:start position:0% um it would need to be undertaken at this<00:46:07.800> stage<00:46:08.099> but 00:46:09.829 --> 00:46:09.839 align:start position:0% this stage but 00:46:09.839 --> 00:46:10.970 align:start position:0% this stage but um 00:46:10.970 --> 00:46:10.980 align:start position:0% um 00:46:10.980 --> 00:46:14.210 align:start position:0% um I<00:46:11.460> imagine<00:46:11.640> that<00:46:12.000> that<00:46:12.420> too<00:46:12.839> will<00:46:13.079> become<00:46:13.500> more 00:46:14.210 --> 00:46:14.220 align:start position:0% I imagine that that too will become more 00:46:14.220 --> 00:46:25.069 align:start position:0% I imagine that that too will become more uh<00:46:14.940> accessible<00:46:15.359> to<00:46:15.599> all<00:46:15.780> soon<00:46:16.020> is<00:46:16.380> my<00:46:16.619> help 00:46:25.069 --> 00:46:25.079 align:start position:0% 00:46:25.079 --> 00:46:27.770 align:start position:0% so<00:46:25.619> you<00:46:25.980> spoke<00:46:26.220> a<00:46:26.339> little<00:46:26.400> bit<00:46:26.520> about<00:46:26.640> private 00:46:27.770 --> 00:46:27.780 align:start position:0% so you spoke a little bit about private 00:46:27.780 --> 00:46:30.349 align:start position:0% so you spoke a little bit about private um<00:46:27.839> trade<00:46:28.319> Private<00:46:28.680> Sales<00:46:28.800> just<00:46:29.520> now<00:46:29.700> I 00:46:30.349 --> 00:46:30.359 align:start position:0% um trade Private Sales just now I 00:46:30.359 --> 00:46:33.710 align:start position:0% um trade Private Sales just now I imagine<00:46:30.599> that<00:46:31.140> openc<00:46:31.560> is<00:46:31.920> not<00:46:32.359> spawning<00:46:33.359> new 00:46:33.710 --> 00:46:33.720 align:start position:0% imagine that openc is not spawning new 00:46:33.720 --> 00:46:35.870 align:start position:0% imagine that openc is not spawning new contracts<00:46:34.380> for<00:46:34.740> zones<00:46:35.099> every<00:46:35.400> time<00:46:35.640> someone 00:46:35.870 --> 00:46:35.880 align:start position:0% contracts for zones every time someone 00:46:35.880 --> 00:46:37.730 align:start position:0% contracts for zones every time someone does<00:46:36.240> a<00:46:36.540> private<00:46:36.839> sale<00:46:37.020> can<00:46:37.319> you<00:46:37.440> walk<00:46:37.560> us 00:46:37.730 --> 00:46:37.740 align:start position:0% does a private sale can you walk us 00:46:37.740 --> 00:46:39.230 align:start position:0% does a private sale can you walk us through<00:46:37.920> the<00:46:38.099> flow<00:46:38.400> of<00:46:38.520> a<00:46:38.700> private<00:46:38.880> sale<00:46:39.000> in 00:46:39.230 --> 00:46:39.240 align:start position:0% through the flow of a private sale in 00:46:39.240 --> 00:46:42.170 align:start position:0% through the flow of a private sale in open<00:46:39.359> seat<00:46:39.660> today<00:46:39.839> yeah<00:46:40.800> so<00:46:41.160> so<00:46:41.579> there's<00:46:41.880> no 00:46:42.170 --> 00:46:42.180 align:start position:0% open seat today yeah so so there's no 00:46:42.180 --> 00:46:44.870 align:start position:0% open seat today yeah so so there's no Zone<00:46:42.660> required<00:46:43.440> on<00:46:43.980> Private<00:46:44.339> Sales<00:46:44.460> that's 00:46:44.870 --> 00:46:44.880 align:start position:0% Zone required on Private Sales that's 00:46:44.880 --> 00:46:47.930 align:start position:0% Zone required on Private Sales that's basically<00:46:45.740> just<00:46:46.740> taking 00:46:47.930 --> 00:46:47.940 align:start position:0% basically just taking 00:46:47.940 --> 00:46:51.349 align:start position:0% basically just taking the<00:46:48.839> standard<00:46:49.500> order 00:46:51.349 --> 00:46:51.359 align:start position:0% the standard order 00:46:51.359 --> 00:46:54.109 align:start position:0% the standard order and<00:46:52.319> normally 00:46:54.109 --> 00:46:54.119 align:start position:0% and normally 00:46:54.119 --> 00:46:57.349 align:start position:0% and normally you'll<00:46:54.720> see<00:46:54.900> an<00:46:55.140> order<00:46:55.319> with<00:46:56.280> it's<00:46:56.819> like<00:46:57.119> the 00:46:57.349 --> 00:46:57.359 align:start position:0% you'll see an order with it's like the 00:46:57.359 --> 00:46:59.210 align:start position:0% you'll see an order with it's like the basic<00:46:57.660> order<00:46:57.839> you'll<00:46:58.200> have<00:46:58.319> a<00:46:58.500> single<00:46:58.800> offer 00:46:59.210 --> 00:46:59.220 align:start position:0% basic order you'll have a single offer 00:46:59.220 --> 00:47:02.089 align:start position:0% basic order you'll have a single offer item<00:46:59.819> that's<00:47:00.780> either 00:47:02.089 --> 00:47:02.099 align:start position:0% item that's either 00:47:02.099 --> 00:47:04.910 align:start position:0% item that's either the<00:47:02.640> the<00:47:02.640> tokens<00:47:03.359> that<00:47:03.780> you<00:47:03.900> want<00:47:04.079> to<00:47:04.260> spend<00:47:04.500> or 00:47:04.910 --> 00:47:04.920 align:start position:0% the the tokens that you want to spend or 00:47:04.920 --> 00:47:07.730 align:start position:0% the the tokens that you want to spend or the<00:47:05.160> nft<00:47:05.460> that<00:47:05.940> you<00:47:06.060> want<00:47:06.240> to<00:47:06.420> sell 00:47:07.730 --> 00:47:07.740 align:start position:0% the nft that you want to sell 00:47:07.740 --> 00:47:10.370 align:start position:0% the nft that you want to sell and<00:47:08.160> then<00:47:08.220> you'll<00:47:08.460> have<00:47:08.780> one<00:47:09.780> consideration 00:47:10.370 --> 00:47:10.380 align:start position:0% and then you'll have one consideration 00:47:10.380 --> 00:47:12.770 align:start position:0% and then you'll have one consideration item<00:47:10.740> the<00:47:10.980> first<00:47:11.160> one<00:47:11.460> by<00:47:11.880> convention<00:47:12.359> like<00:47:12.660> if 00:47:12.770 --> 00:47:12.780 align:start position:0% item the first one by convention like if 00:47:12.780 --> 00:47:14.870 align:start position:0% item the first one by convention like if you<00:47:12.900> use<00:47:13.079> the<00:47:13.260> order<00:47:13.380> validation<00:47:14.040> helper 00:47:14.870 --> 00:47:14.880 align:start position:0% you use the order validation helper 00:47:14.880 --> 00:47:15.829 align:start position:0% you use the order validation helper thing 00:47:15.829 --> 00:47:15.839 align:start position:0% thing 00:47:15.839 --> 00:47:18.530 align:start position:0% thing the<00:47:16.560> first<00:47:16.740> consideration<00:47:17.339> item<00:47:17.760> is<00:47:18.240> almost 00:47:18.530 --> 00:47:18.540 align:start position:0% the first consideration item is almost 00:47:18.540 --> 00:47:20.950 align:start position:0% the first consideration item is almost always<00:47:18.900> going<00:47:19.319> to<00:47:19.560> be 00:47:20.950 --> 00:47:20.960 align:start position:0% always going to be 00:47:20.960 --> 00:47:24.349 align:start position:0% always going to be something<00:47:21.960> coming<00:47:22.560> back<00:47:22.920> to<00:47:23.460> you<00:47:23.579> the<00:47:23.880> offerer 00:47:24.349 --> 00:47:24.359 align:start position:0% something coming back to you the offerer 00:47:24.359 --> 00:47:27.890 align:start position:0% something coming back to you the offerer right<00:47:24.960> and<00:47:25.920> then<00:47:26.040> it'll<00:47:26.280> be<00:47:26.400> followed<00:47:26.760> up<00:47:26.940> by 00:47:27.890 --> 00:47:27.900 align:start position:0% right and then it'll be followed up by 00:47:27.900 --> 00:47:31.730 align:start position:0% right and then it'll be followed up by usually<00:47:28.740> fees<00:47:29.460> like<00:47:30.300> here's<00:47:31.200> a<00:47:31.319> fee<00:47:31.560> to<00:47:31.619> the 00:47:31.730 --> 00:47:31.740 align:start position:0% usually fees like here's a fee to the 00:47:31.740 --> 00:47:35.329 align:start position:0% usually fees like here's a fee to the marketplace<00:47:32.160> here's<00:47:33.119> a<00:47:33.300> fee<00:47:33.599> to<00:47:33.839> the<00:47:34.020> Creator 00:47:35.329 --> 00:47:35.339 align:start position:0% marketplace here's a fee to the Creator 00:47:35.339 --> 00:47:38.030 align:start position:0% marketplace here's a fee to the Creator that's<00:47:35.940> the<00:47:36.240> standard<00:47:36.960> order<00:47:37.200> that<00:47:37.680> you<00:47:37.859> would 00:47:38.030 --> 00:47:38.040 align:start position:0% that's the standard order that you would 00:47:38.040 --> 00:47:38.870 align:start position:0% that's the standard order that you would see 00:47:38.870 --> 00:47:38.880 align:start position:0% see 00:47:38.880 --> 00:47:42.230 align:start position:0% see but<00:47:39.500> in<00:47:40.500> Private<00:47:40.980> Sales<00:47:41.220> one<00:47:41.640> way<00:47:41.819> you<00:47:42.000> can<00:47:42.060> do 00:47:42.230 --> 00:47:42.240 align:start position:0% but in Private Sales one way you can do 00:47:42.240 --> 00:47:45.230 align:start position:0% but in Private Sales one way you can do a<00:47:42.420> private<00:47:42.720> sale<00:47:42.960> is<00:47:43.859> you<00:47:44.040> deviate<00:47:44.520> from<00:47:44.880> that 00:47:45.230 --> 00:47:45.240 align:start position:0% a private sale is you deviate from that 00:47:45.240 --> 00:47:47.870 align:start position:0% a private sale is you deviate from that standard<00:47:45.960> a<00:47:46.140> little<00:47:46.260> bit<00:47:46.440> and<00:47:47.339> you<00:47:47.460> just<00:47:47.640> say 00:47:47.870 --> 00:47:47.880 align:start position:0% standard a little bit and you just say 00:47:47.880 --> 00:47:51.670 align:start position:0% standard a little bit and you just say I'm<00:47:48.720> actually<00:47:49.079> going<00:47:49.500> to<00:47:49.680> include 00:47:51.670 --> 00:47:51.680 align:start position:0% I'm actually going to include 00:47:51.680 --> 00:47:55.250 align:start position:0% I'm actually going to include the<00:47:52.680> the<00:47:53.280> recipient<00:47:53.819> the<00:47:54.420> person<00:47:54.540> that<00:47:54.900> I<00:47:55.140> want 00:47:55.250 --> 00:47:55.260 align:start position:0% the the recipient the person that I want 00:47:55.260 --> 00:47:57.410 align:start position:0% the the recipient the person that I want to<00:47:55.440> sell<00:47:55.680> this<00:47:56.040> item<00:47:56.400> to 00:47:57.410 --> 00:47:57.420 align:start position:0% to sell this item to 00:47:57.420 --> 00:48:01.550 align:start position:0% to sell this item to as<00:47:58.140> a<00:47:58.440> consideration<00:47:59.099> item<00:47:59.520> on<00:48:00.060> my<00:48:00.480> order 00:48:01.550 --> 00:48:01.560 align:start position:0% as a consideration item on my order 00:48:01.560 --> 00:48:03.349 align:start position:0% as a consideration item on my order if<00:48:01.859> that<00:48:02.099> makes<00:48:02.220> sense 00:48:03.349 --> 00:48:03.359 align:start position:0% if that makes sense 00:48:03.359 --> 00:48:06.349 align:start position:0% if that makes sense so<00:48:04.319> it's<00:48:04.740> like 00:48:06.349 --> 00:48:06.359 align:start position:0% so it's like 00:48:06.359 --> 00:48:08.510 align:start position:0% so it's like literally 00:48:08.510 --> 00:48:08.520 align:start position:0% literally 00:48:08.520 --> 00:48:10.910 align:start position:0% literally you<00:48:09.060> need<00:48:09.180> to<00:48:09.359> get<00:48:09.540> this<00:48:09.780> or<00:48:10.380> else<00:48:10.560> you<00:48:10.800> can't 00:48:10.910 --> 00:48:10.920 align:start position:0% you need to get this or else you can't 00:48:10.920 --> 00:48:13.609 align:start position:0% you need to get this or else you can't take<00:48:11.160> it<00:48:11.400> from<00:48:11.700> me<00:48:11.940> yeah 00:48:13.609 --> 00:48:13.619 align:start position:0% take it from me yeah 00:48:13.619 --> 00:48:22.450 align:start position:0% take it from me yeah that's<00:48:14.099> the<00:48:14.220> idea 00:48:22.450 --> 00:48:22.460 align:start position:0% 00:48:22.460 --> 00:48:24.109 align:start position:0% I<00:48:23.460> guess 00:48:24.109 --> 00:48:24.119 align:start position:0% I guess 00:48:24.119 --> 00:48:26.809 align:start position:0% I guess um<00:48:24.180> like<00:48:24.720> for<00:48:24.960> like<00:48:25.260> a<00:48:25.380> Zone<00:48:25.680> idea<00:48:26.099> is<00:48:26.579> that 00:48:26.809 --> 00:48:26.819 align:start position:0% um like for like a Zone idea is that 00:48:26.819 --> 00:48:29.450 align:start position:0% um like for like a Zone idea is that like<00:48:27.359> I<00:48:27.900> think<00:48:28.020> when<00:48:28.260> I<00:48:28.380> was<00:48:28.500> reading<00:48:28.859> the<00:48:29.220> like 00:48:29.450 --> 00:48:29.460 align:start position:0% like I think when I was reading the like 00:48:29.460 --> 00:48:31.609 align:start position:0% like I think when I was reading the like Open<00:48:29.700> Seas<00:48:30.180> like<00:48:30.300> wyvern<00:48:30.780> contracts<00:48:31.319> like 00:48:31.609 --> 00:48:31.619 align:start position:0% Open Seas like wyvern contracts like 00:48:31.619 --> 00:48:32.930 align:start position:0% Open Seas like wyvern contracts like there<00:48:31.800> was<00:48:31.920> support<00:48:32.099> for<00:48:32.460> just<00:48:32.579> Dutch 00:48:32.930 --> 00:48:32.940 align:start position:0% there was support for just Dutch 00:48:32.940 --> 00:48:35.329 align:start position:0% there was support for just Dutch auctions<00:48:33.420> and<00:48:33.780> pixel<00:48:34.260> or<00:48:34.619> fixed<00:48:34.920> price<00:48:35.040> sales 00:48:35.329 --> 00:48:35.339 align:start position:0% auctions and pixel or fixed price sales 00:48:35.339 --> 00:48:37.910 align:start position:0% auctions and pixel or fixed price sales and<00:48:36.000> they<00:48:36.180> had<00:48:36.300> like<00:48:36.540> a<00:48:36.960> comment<00:48:37.260> in<00:48:37.440> it<00:48:37.619> saying 00:48:37.910 --> 00:48:37.920 align:start position:0% and they had like a comment in it saying 00:48:37.920 --> 00:48:39.230 align:start position:0% and they had like a comment in it saying like<00:48:38.040> they<00:48:38.280> wanted<00:48:38.400> to<00:48:38.640> maybe<00:48:38.760> do<00:48:39.000> something 00:48:39.230 --> 00:48:39.240 align:start position:0% like they wanted to maybe do something 00:48:39.240 --> 00:48:41.150 align:start position:0% like they wanted to maybe do something more<00:48:39.480> advanced<00:48:39.900> or<00:48:40.079> like<00:48:40.319> English<00:48:40.560> auctions 00:48:41.150 --> 00:48:41.160 align:start position:0% more advanced or like English auctions 00:48:41.160 --> 00:48:43.250 align:start position:0% more advanced or like English auctions or<00:48:41.280> something<00:48:41.460> like<00:48:41.700> that<00:48:41.819> right<00:48:42.119> and<00:48:43.020> I 00:48:43.250 --> 00:48:43.260 align:start position:0% or something like that right and I 00:48:43.260 --> 00:48:45.290 align:start position:0% or something like that right and I remember<00:48:43.440> watching<00:48:44.040> one<00:48:44.280> of<00:48:44.339> your<00:48:44.460> like<00:48:44.700> I 00:48:45.290 --> 00:48:45.300 align:start position:0% remember watching one of your like I 00:48:45.300 --> 00:48:47.030 align:start position:0% remember watching one of your like I guess<00:48:45.420> it<00:48:45.599> was<00:48:45.780> like<00:48:45.960> an<00:48:46.079> East<00:48:46.260> Denver<00:48:46.440> talk<00:48:46.800> or 00:48:47.030 --> 00:48:47.040 align:start position:0% guess it was like an East Denver talk or 00:48:47.040 --> 00:48:49.609 align:start position:0% guess it was like an East Denver talk or something<00:48:47.280> like<00:48:47.579> that<00:48:47.760> and<00:48:48.180> you<00:48:48.420> said<00:48:48.660> that 00:48:49.609 --> 00:48:49.619 align:start position:0% something like that and you said that 00:48:49.619 --> 00:48:51.290 align:start position:0% something like that and you said that like<00:48:49.980> something<00:48:50.280> like<00:48:50.520> an<00:48:50.700> English<00:48:50.880> auction 00:48:51.290 --> 00:48:51.300 align:start position:0% like something like an English auction 00:48:51.300 --> 00:48:53.569 align:start position:0% like something like an English auction or<00:48:51.720> that<00:48:52.140> could<00:48:52.380> be<00:48:52.619> possible<00:48:52.920> using<00:48:53.400> the 00:48:53.569 --> 00:48:53.579 align:start position:0% or that could be possible using the 00:48:53.579 --> 00:48:56.930 align:start position:0% or that could be possible using the zones<00:48:54.079> uh<00:48:55.079> so<00:48:55.319> I<00:48:55.440> I<00:48:55.619> should<00:48:55.800> this<00:48:56.579> is<00:48:56.760> actually 00:48:56.930 --> 00:48:56.940 align:start position:0% zones uh so I I should this is actually 00:48:56.940 --> 00:48:58.550 align:start position:0% zones uh so I I should this is actually another<00:48:57.300> Advanced<00:48:57.900> technique<00:48:58.200> that<00:48:58.380> we 00:48:58.550 --> 00:48:58.560 align:start position:0% another Advanced technique that we 00:48:58.560 --> 00:48:59.809 align:start position:0% another Advanced technique that we haven't<00:48:58.680> really<00:48:58.859> touched<00:48:59.280> on<00:48:59.339> that<00:48:59.700> you 00:48:59.809 --> 00:48:59.819 align:start position:0% haven't really touched on that you 00:48:59.819 --> 00:49:03.770 align:start position:0% haven't really touched on that you reminded<00:49:00.300> me<00:49:00.420> of<00:49:00.599> and<00:49:01.079> that<00:49:01.319> is<00:49:01.760> every<00:49:02.760> item 00:49:03.770 --> 00:49:03.780 align:start position:0% reminded me of and that is every item 00:49:03.780 --> 00:49:07.730 align:start position:0% reminded me of and that is every item you<00:49:04.440> can<00:49:04.560> specify<00:49:05.099> a<00:49:05.640> start<00:49:05.819> amount<00:49:06.500> and<00:49:07.500> an 00:49:07.730 --> 00:49:07.740 align:start position:0% you can specify a start amount and an 00:49:07.740 --> 00:49:09.410 align:start position:0% you can specify a start amount and an end<00:49:08.040> amount 00:49:09.410 --> 00:49:09.420 align:start position:0% end amount 00:49:09.420 --> 00:49:12.530 align:start position:0% end amount so<00:49:10.020> when<00:49:10.260> you<00:49:10.440> do<00:49:10.619> that<00:49:10.880> it<00:49:11.880> will<00:49:12.000> look<00:49:12.180> at<00:49:12.359> the 00:49:12.530 --> 00:49:12.540 align:start position:0% so when you do that it will look at the 00:49:12.540 --> 00:49:14.690 align:start position:0% so when you do that it will look at the start<00:49:12.780> time<00:49:13.200> and<00:49:13.500> the<00:49:13.680> end<00:49:13.920> time 00:49:14.690 --> 00:49:14.700 align:start position:0% start time and the end time 00:49:14.700 --> 00:49:18.109 align:start position:0% start time and the end time on<00:49:15.420> that<00:49:15.720> particular<00:49:16.140> order<00:49:16.819> and<00:49:17.819> then<00:49:17.940> it 00:49:18.109 --> 00:49:18.119 align:start position:0% on that particular order and then it 00:49:18.119 --> 00:49:22.430 align:start position:0% on that particular order and then it does<00:49:18.359> it<00:49:18.960> a<00:49:19.380> linear<00:49:19.980> interpolation<00:49:20.819> and<00:49:21.720> we'll 00:49:22.430 --> 00:49:22.440 align:start position:0% does it a linear interpolation and we'll 00:49:22.440 --> 00:49:25.309 align:start position:0% does it a linear interpolation and we'll just<00:49:22.680> pick<00:49:23.220> out<00:49:23.400> okay<00:49:24.060> here's<00:49:24.660> the<00:49:25.020> current 00:49:25.309 --> 00:49:25.319 align:start position:0% just pick out okay here's the current 00:49:25.319 --> 00:49:29.030 align:start position:0% just pick out okay here's the current amount<00:49:26.220> based<00:49:26.880> on<00:49:26.940> where<00:49:27.780> we<00:49:27.960> are<00:49:28.140> along<00:49:28.500> the 00:49:29.030 --> 00:49:29.040 align:start position:0% amount based on where we are along the 00:49:29.040 --> 00:49:31.790 align:start position:0% amount based on where we are along the the<00:49:29.640> timeline<00:49:30.359> for<00:49:30.780> the<00:49:30.900> order 00:49:31.790 --> 00:49:31.800 align:start position:0% the timeline for the order 00:49:31.800 --> 00:49:33.109 align:start position:0% the timeline for the order so 00:49:33.109 --> 00:49:33.119 align:start position:0% so 00:49:33.119 --> 00:49:35.030 align:start position:0% so oftentimes<00:49:33.960> like<00:49:34.140> when<00:49:34.319> you<00:49:34.440> talk<00:49:34.560> about<00:49:34.740> a 00:49:35.030 --> 00:49:35.040 align:start position:0% oftentimes like when you talk about a 00:49:35.040 --> 00:49:36.650 align:start position:0% oftentimes like when you talk about a Dutch<00:49:35.280> auction<00:49:35.579> what<00:49:35.880> that<00:49:36.060> or<00:49:36.300> a<00:49:36.420> reverse 00:49:36.650 --> 00:49:36.660 align:start position:0% Dutch auction what that or a reverse 00:49:36.660 --> 00:49:39.170 align:start position:0% Dutch auction what that or a reverse Dutch<00:49:36.960> option<00:49:37.200> what<00:49:37.319> that<00:49:37.500> really<00:49:37.760> is<00:49:38.760> getting 00:49:39.170 --> 00:49:39.180 align:start position:0% Dutch option what that really is getting 00:49:39.180 --> 00:49:42.410 align:start position:0% Dutch option what that really is getting at<00:49:39.420> is<00:49:39.839> this<00:49:40.740> is<00:49:40.859> a<00:49:41.099> it's<00:49:41.400> a<00:49:41.579> sum<00:49:41.819> listing<00:49:42.180> where 00:49:42.410 --> 00:49:42.420 align:start position:0% at is this is a it's a sum listing where 00:49:42.420 --> 00:49:44.569 align:start position:0% at is this is a it's a sum listing where the<00:49:42.599> price<00:49:42.780> is<00:49:43.020> going<00:49:43.260> down<00:49:43.500> over<00:49:43.800> time<00:49:44.040> right 00:49:44.569 --> 00:49:44.579 align:start position:0% the price is going down over time right 00:49:44.579 --> 00:49:46.849 align:start position:0% the price is going down over time right or<00:49:45.060> the<00:49:45.240> price<00:49:45.359> is<00:49:45.540> going<00:49:45.720> up<00:49:45.960> over<00:49:46.140> time<00:49:46.440> it's 00:49:46.849 --> 00:49:46.859 align:start position:0% or the price is going up over time it's 00:49:46.859 --> 00:49:47.710 align:start position:0% or the price is going up over time it's not 00:49:47.710 --> 00:49:47.720 align:start position:0% not 00:49:47.720 --> 00:49:50.510 align:start position:0% not necessarily<00:49:48.720> an<00:49:49.079> auction<00:49:49.380> per<00:49:49.800> se 00:49:50.510 --> 00:49:50.520 align:start position:0% necessarily an auction per se 00:49:50.520 --> 00:49:52.450 align:start position:0% necessarily an auction per se now 00:49:52.450 --> 00:49:52.460 align:start position:0% now 00:49:52.460 --> 00:49:54.950 align:start position:0% now auctions<00:49:53.460> there's<00:49:54.060> a<00:49:54.240> couple<00:49:54.359> different<00:49:54.599> ways 00:49:54.950 --> 00:49:54.960 align:start position:0% auctions there's a couple different ways 00:49:54.960 --> 00:49:57.710 align:start position:0% auctions there's a couple different ways to<00:49:55.079> run<00:49:55.260> them<00:49:55.500> and<00:49:56.220> it<00:49:56.400> really<00:49:56.579> depends<00:49:57.240> on 00:49:57.710 --> 00:49:57.720 align:start position:0% to run them and it really depends on 00:49:57.720 --> 00:50:00.410 align:start position:0% to run them and it really depends on what<00:49:58.500> you're<00:49:58.800> trying<00:49:59.099> to<00:49:59.460> optimize<00:49:59.940> for<00:50:00.180> and 00:50:00.410 --> 00:50:00.420 align:start position:0% what you're trying to optimize for and 00:50:00.420 --> 00:50:04.010 align:start position:0% what you're trying to optimize for and what<00:50:00.720> your<00:50:00.839> trust<00:50:01.079> model<00:50:01.319> is<00:50:01.940> oftentimes<00:50:03.020> what 00:50:04.010 --> 00:50:04.020 align:start position:0% what your trust model is oftentimes what 00:50:04.020 --> 00:50:07.670 align:start position:0% what your trust model is oftentimes what it<00:50:04.200> really<00:50:04.760> comes<00:50:05.760> down<00:50:05.880> to<00:50:06.060> is<00:50:06.359> like 00:50:07.670 --> 00:50:07.680 align:start position:0% it really comes down to is like 00:50:07.680 --> 00:50:10.550 align:start position:0% it really comes down to is like I<00:50:08.099> have<00:50:08.160> a<00:50:08.339> reserve<00:50:08.760> price<00:50:09.000> and<00:50:09.960> I<00:50:10.140> want<00:50:10.380> that 00:50:10.550 --> 00:50:10.560 align:start position:0% I have a reserve price and I want that 00:50:10.560 --> 00:50:13.250 align:start position:0% I have a reserve price and I want that reserve<00:50:10.980> price<00:50:11.160> to<00:50:11.460> be<00:50:11.640> met<00:50:12.420> and<00:50:12.900> I<00:50:13.020> want<00:50:13.079> that 00:50:13.250 --> 00:50:13.260 align:start position:0% reserve price to be met and I want that 00:50:13.260 --> 00:50:18.050 align:start position:0% reserve price to be met and I want that reserve<00:50:13.680> price<00:50:13.800> to<00:50:14.099> be<00:50:14.220> secret<00:50:14.460> too<00:50:15.300> right<00:50:15.720> so 00:50:18.050 --> 00:50:18.060 align:start position:0% reserve price to be secret too right so 00:50:18.060 --> 00:50:18.770 align:start position:0% reserve price to be secret too right so um 00:50:18.770 --> 00:50:18.780 align:start position:0% um 00:50:18.780 --> 00:50:21.589 align:start position:0% um like<00:50:19.380> one<00:50:19.680> way<00:50:19.859> to<00:50:20.280> handle<00:50:20.700> an<00:50:21.359> auction 00:50:21.589 --> 00:50:21.599 align:start position:0% like one way to handle an auction 00:50:21.599 --> 00:50:23.809 align:start position:0% like one way to handle an auction assuming<00:50:22.560> you<00:50:22.859> have 00:50:23.809 --> 00:50:23.819 align:start position:0% assuming you have 00:50:23.819 --> 00:50:27.470 align:start position:0% assuming you have an<00:50:24.480> Auctioneer<00:50:25.020> that<00:50:25.920> is<00:50:26.640> a<00:50:26.880> someone<00:50:27.180> you 00:50:27.470 --> 00:50:27.480 align:start position:0% an Auctioneer that is a someone you 00:50:27.480 --> 00:50:30.829 align:start position:0% an Auctioneer that is a someone you trust<00:50:28.020> is<00:50:28.920> you<00:50:29.099> set<00:50:29.339> the<00:50:29.760> auction<00:50:30.180> the<00:50:30.540> runner 00:50:30.829 --> 00:50:30.839 align:start position:0% trust is you set the auction the runner 00:50:30.839 --> 00:50:34.450 align:start position:0% trust is you set the auction the runner of<00:50:30.960> the<00:50:31.140> auction<00:50:31.520> as<00:50:32.520> the<00:50:32.819> Zone<00:50:33.119> on<00:50:33.960> your<00:50:34.140> order 00:50:34.450 --> 00:50:34.460 align:start position:0% of the auction as the Zone on your order 00:50:34.460 --> 00:50:37.609 align:start position:0% of the auction as the Zone on your order zones<00:50:35.839> generally<00:50:36.839> the<00:50:37.079> way<00:50:37.200> that<00:50:37.319> we<00:50:37.500> would 00:50:37.609 --> 00:50:37.619 align:start position:0% zones generally the way that we would 00:50:37.619 --> 00:50:40.069 align:start position:0% zones generally the way that we would think<00:50:38.099> of<00:50:38.280> them<00:50:38.400> is<00:50:39.000> that<00:50:39.300> when<00:50:39.540> you<00:50:39.660> have<00:50:39.780> a 00:50:40.069 --> 00:50:40.079 align:start position:0% think of them is that when you have a 00:50:40.079 --> 00:50:41.750 align:start position:0% think of them is that when you have a restricted<00:50:40.560> order 00:50:41.750 --> 00:50:41.760 align:start position:0% restricted order 00:50:41.760 --> 00:50:44.329 align:start position:0% restricted order that<00:50:42.300> zone<00:50:42.599> you're<00:50:42.900> gonna<00:50:43.079> call<00:50:43.680> it<00:50:43.859> and<00:50:44.160> say 00:50:44.329 --> 00:50:44.339 align:start position:0% that zone you're gonna call it and say 00:50:44.339 --> 00:50:49.190 align:start position:0% that zone you're gonna call it and say is<00:50:45.180> this<00:50:45.300> a<00:50:45.540> valid<00:50:45.780> order<00:50:45.960> if<00:50:46.560> it<00:50:46.740> is<00:50:46.920> then 00:50:49.190 --> 00:50:49.200 align:start position:0% is this a valid order if it is then 00:50:49.200 --> 00:50:51.349 align:start position:0% is this a valid order if it is then um<00:50:49.260> it'll<00:50:49.500> give<00:50:49.680> back<00:50:49.920> a<00:50:50.160> magic<00:50:50.339> value<00:50:50.700> saying 00:50:51.349 --> 00:50:51.359 align:start position:0% um it'll give back a magic value saying 00:50:51.359 --> 00:50:53.270 align:start position:0% um it'll give back a magic value saying this<00:50:51.900> is<00:50:52.020> good<00:50:52.200> go<00:50:52.500> ahead 00:50:53.270 --> 00:50:53.280 align:start position:0% this is good go ahead 00:50:53.280 --> 00:50:57.349 align:start position:0% this is good go ahead but<00:50:53.700> another<00:50:53.940> way<00:50:54.180> you<00:50:54.359> can<00:50:54.420> do<00:50:54.660> it<00:50:54.920> is<00:50:55.920> that 00:50:57.349 --> 00:50:57.359 align:start position:0% but another way you can do it is that 00:50:57.359 --> 00:51:01.190 align:start position:0% but another way you can do it is that that<00:50:58.140> zone<00:50:58.380> can<00:50:58.859> actually<00:50:59.160> call<00:50:59.819> Seaport<00:51:00.420> if 00:51:01.190 --> 00:51:01.200 align:start position:0% that zone can actually call Seaport if 00:51:01.200 --> 00:51:04.370 align:start position:0% that zone can actually call Seaport if they<00:51:01.380> call<00:51:01.559> Seaport<00:51:02.099> that's<00:51:02.760> also<00:51:03.119> them<00:51:03.900> if 00:51:04.370 --> 00:51:04.380 align:start position:0% they call Seaport that's also them if 00:51:04.380 --> 00:51:05.630 align:start position:0% they call Seaport that's also them if they're<00:51:04.500> the<00:51:04.680> ones<00:51:04.859> that<00:51:05.040> are<00:51:05.160> fulfilling<00:51:05.520> the 00:51:05.630 --> 00:51:05.640 align:start position:0% they're the ones that are fulfilling the 00:51:05.640 --> 00:51:06.410 align:start position:0% they're the ones that are fulfilling the order 00:51:06.410 --> 00:51:06.420 align:start position:0% order 00:51:06.420 --> 00:51:08.390 align:start position:0% order that's<00:51:06.900> also<00:51:07.140> them<00:51:07.260> giving<00:51:07.559> explicit 00:51:08.390 --> 00:51:08.400 align:start position:0% that's also them giving explicit 00:51:08.400 --> 00:51:10.970 align:start position:0% that's also them giving explicit approval<00:51:09.240> per<00:51:09.599> se<00:51:09.780> right<00:51:10.260> their<00:51:10.680> message 00:51:10.970 --> 00:51:10.980 align:start position:0% approval per se right their message 00:51:10.980 --> 00:51:12.470 align:start position:0% approval per se right their message sender<00:51:11.520> so 00:51:12.470 --> 00:51:12.480 align:start position:0% sender so 00:51:12.480 --> 00:51:18.470 align:start position:0% sender so you<00:51:12.960> can<00:51:13.079> basically<00:51:13.940> sign<00:51:14.940> a<00:51:15.480> listing<00:51:16.020> that 00:51:18.470 --> 00:51:18.480 align:start position:0% you can basically sign a listing that 00:51:18.480 --> 00:51:21.589 align:start position:0% you can basically sign a listing that you<00:51:18.900> here's<00:51:19.319> my<00:51:19.500> my<00:51:19.859> reserve<00:51:20.460> price<00:51:20.700> that's 00:51:21.589 --> 00:51:21.599 align:start position:0% you here's my my reserve price that's 00:51:21.599 --> 00:51:23.690 align:start position:0% you here's my my reserve price that's the<00:51:21.839> consideration<00:51:22.319> item<00:51:22.740> to<00:51:22.920> me<00:51:23.099> I'm<00:51:23.520> going 00:51:23.690 --> 00:51:23.700 align:start position:0% the consideration item to me I'm going 00:51:23.700 --> 00:51:27.470 align:start position:0% the consideration item to me I'm going to<00:51:23.819> give<00:51:24.000> that<00:51:24.300> to<00:51:25.040> this<00:51:26.040> this<00:51:26.819> Auctioneer 00:51:27.470 --> 00:51:27.480 align:start position:0% to give that to this this Auctioneer 00:51:27.480 --> 00:51:30.230 align:start position:0% to give that to this this Auctioneer whatever<00:51:27.780> the<00:51:28.200> marketplace 00:51:30.230 --> 00:51:30.240 align:start position:0% whatever the marketplace 00:51:30.240 --> 00:51:32.809 align:start position:0% whatever the marketplace they're<00:51:30.780> going<00:51:30.900> to<00:51:31.020> keep<00:51:31.140> the<00:51:31.260> order<00:51:31.380> Secret 00:51:32.809 --> 00:51:32.819 align:start position:0% they're going to keep the order Secret 00:51:32.819 --> 00:51:36.109 align:start position:0% they're going to keep the order Secret and<00:51:33.420> then<00:51:33.599> they<00:51:34.500> have<00:51:34.680> to<00:51:34.859> be<00:51:35.040> the<00:51:35.280> one<00:51:35.460> to 00:51:36.109 --> 00:51:36.119 align:start position:0% and then they have to be the one to 00:51:36.119 --> 00:51:39.650 align:start position:0% and then they have to be the one to fulfill<00:51:36.480> it<00:51:36.660> right<00:51:37.619> it's<00:51:37.859> a<00:51:38.040> restricted<00:51:38.400> order 00:51:39.650 --> 00:51:39.660 align:start position:0% fulfill it right it's a restricted order 00:51:39.660 --> 00:51:44.210 align:start position:0% fulfill it right it's a restricted order and<00:51:40.200> they'll<00:51:40.440> apply<00:51:40.880> a<00:51:41.880> tip<00:51:42.260> on<00:51:43.260> that<00:51:43.440> based<00:51:44.099> on 00:51:44.210 --> 00:51:44.220 align:start position:0% and they'll apply a tip on that based on 00:51:44.220 --> 00:51:46.450 align:start position:0% and they'll apply a tip on that based on the<00:51:44.940> difference<00:51:45.059> between<00:51:45.420> the<00:51:45.660> reserve<00:51:46.079> price 00:51:46.450 --> 00:51:46.460 align:start position:0% the difference between the reserve price 00:51:46.460 --> 00:51:49.250 align:start position:0% the difference between the reserve price and<00:51:47.460> the<00:51:48.119> actual<00:51:48.359> price 00:51:49.250 --> 00:51:49.260 align:start position:0% and the actual price 00:51:49.260 --> 00:51:51.770 align:start position:0% and the actual price there<00:51:49.859> are<00:51:49.980> also<00:51:50.280> constructions<00:51:51.059> where<00:51:51.420> you 00:51:51.770 --> 00:51:51.780 align:start position:0% there are also constructions where you 00:51:51.780 --> 00:51:54.470 align:start position:0% there are also constructions where you can<00:51:51.960> do<00:51:52.380> stuff<00:51:53.280> like<00:51:53.520> the<00:51:53.700> commit<00:51:54.059> reveal 00:51:54.470 --> 00:51:54.480 align:start position:0% can do stuff like the commit reveal 00:51:54.480 --> 00:51:57.770 align:start position:0% can do stuff like the commit reveal pattern<00:51:55.020> for<00:51:55.800> hiding<00:51:56.220> the<00:51:56.339> reserve<00:51:56.819> price<00:51:57.180> you 00:51:57.770 --> 00:51:57.780 align:start position:0% pattern for hiding the reserve price you 00:51:57.780 --> 00:51:59.270 align:start position:0% pattern for hiding the reserve price you generally<00:51:58.020> have<00:51:58.200> to<00:51:58.319> bond<00:51:58.559> up<00:51:58.800> front<00:51:58.980> I<00:51:59.160> mean 00:51:59.270 --> 00:51:59.280 align:start position:0% generally have to bond up front I mean 00:51:59.280 --> 00:52:01.670 align:start position:0% generally have to bond up front I mean it<00:51:59.400> gets<00:51:59.700> it<00:52:00.119> gets<00:52:00.359> complicated<00:52:00.900> depending<00:52:01.440> on 00:52:01.670 --> 00:52:01.680 align:start position:0% it gets it gets complicated depending on 00:52:01.680 --> 00:52:04.549 align:start position:0% it gets it gets complicated depending on whether<00:52:02.339> you're<00:52:02.579> optimizing<00:52:03.180> for<00:52:03.559> the 00:52:04.549 --> 00:52:04.559 align:start position:0% whether you're optimizing for the 00:52:04.559 --> 00:52:07.490 align:start position:0% whether you're optimizing for the privacy<00:52:04.980> of<00:52:05.460> the<00:52:05.880> the 00:52:07.490 --> 00:52:07.500 align:start position:0% privacy of the the 00:52:07.500 --> 00:52:09.290 align:start position:0% privacy of the the um<00:52:07.619> person<00:52:08.099> that's<00:52:08.460> that's<00:52:08.880> trying<00:52:09.180> to 00:52:09.290 --> 00:52:09.300 align:start position:0% um person that's that's trying to 00:52:09.300 --> 00:52:10.809 align:start position:0% um person that's that's trying to auction<00:52:09.540> the<00:52:09.900> item 00:52:10.809 --> 00:52:10.819 align:start position:0% auction the item 00:52:10.819 --> 00:52:13.609 align:start position:0% auction the item or<00:52:11.819> if<00:52:12.240> you're<00:52:12.359> trying<00:52:12.540> to<00:52:12.720> optimize<00:52:13.200> for 00:52:13.609 --> 00:52:13.619 align:start position:0% or if you're trying to optimize for 00:52:13.619 --> 00:52:15.589 align:start position:0% or if you're trying to optimize for protecting<00:52:14.400> the<00:52:14.579> bidders<00:52:15.000> you<00:52:15.359> know<00:52:15.420> if<00:52:15.540> you 00:52:15.589 --> 00:52:15.599 align:start position:0% protecting the bidders you know if you 00:52:15.599 --> 00:52:17.329 align:start position:0% protecting the bidders you know if you don't<00:52:15.839> want<00:52:16.020> the<00:52:16.380> person<00:52:16.859> running<00:52:17.160> the 00:52:17.329 --> 00:52:17.339 align:start position:0% don't want the person running the 00:52:17.339 --> 00:52:19.069 align:start position:0% don't want the person running the auction<00:52:17.520> to<00:52:17.760> pull<00:52:17.880> out<00:52:18.059> of<00:52:18.240> the<00:52:18.420> auction<00:52:18.660> and 00:52:19.069 --> 00:52:19.079 align:start position:0% auction to pull out of the auction and 00:52:19.079 --> 00:52:20.870 align:start position:0% auction to pull out of the auction and cancel<00:52:19.380> it<00:52:19.619> and<00:52:19.800> pull<00:52:19.980> their<00:52:20.220> you<00:52:20.400> want<00:52:20.579> their 00:52:20.870 --> 00:52:20.880 align:start position:0% cancel it and pull their you want their 00:52:20.880 --> 00:52:23.809 align:start position:0% cancel it and pull their you want their assets<00:52:21.240> or<00:52:21.480> something<00:52:21.660> their<00:52:22.020> items 00:52:23.809 --> 00:52:23.819 align:start position:0% assets or something their items 00:52:23.819 --> 00:52:25.930 align:start position:0% assets or something their items um<00:52:23.940> there's<00:52:24.660> there's<00:52:25.020> a<00:52:25.260> number<00:52:25.380> of<00:52:25.619> different 00:52:25.930 --> 00:52:25.940 align:start position:0% um there's there's a number of different 00:52:25.940 --> 00:52:27.890 align:start position:0% um there's there's a number of different variables<00:52:26.940> to<00:52:27.119> control<00:52:27.240> for<00:52:27.480> but<00:52:27.599> that's<00:52:27.780> one 00:52:27.890 --> 00:52:27.900 align:start position:0% variables to control for but that's one 00:52:27.900 --> 00:52:29.290 align:start position:0% variables to control for but that's one thing<00:52:28.020> that<00:52:28.140> I<00:52:28.260> think<00:52:28.380> would<00:52:28.500> be<00:52:28.680> really<00:52:28.980> cool 00:52:29.290 --> 00:52:29.300 align:start position:0% thing that I think would be really cool 00:52:29.300 --> 00:52:33.530 align:start position:0% thing that I think would be really cool to<00:52:30.300> see<00:52:30.540> more<00:52:30.960> work<00:52:31.200> on<00:52:31.440> is<00:52:32.119> leveraging<00:52:33.119> zones 00:52:33.530 --> 00:52:33.540 align:start position:0% to see more work on is leveraging zones 00:52:33.540 --> 00:52:39.410 align:start position:0% to see more work on is leveraging zones to<00:52:34.020> run<00:52:34.380> different<00:52:35.339> kinds<00:52:35.760> of<00:52:35.880> auctions<00:52:36.540> yeah 00:52:39.410 --> 00:52:39.420 align:start position:0% to run different kinds of auctions yeah 00:52:39.420 --> 00:52:42.290 align:start position:0% to run different kinds of auctions yeah all<00:52:39.960> right<00:52:40.140> that's<00:52:40.800> time<00:52:41.099> thank<00:52:41.819> you<00:52:41.940> all<00:52:42.059> for 00:52:42.290 --> 00:52:42.300 align:start position:0% all right that's time thank you all for 00:52:42.300 --> 00:52:44.809 align:start position:0% all right that's time thank you all for coming<00:52:42.480> and<00:52:43.260> uh<00:52:43.619> can't<00:52:44.160> wait<00:52:44.339> to<00:52:44.460> see<00:52:44.579> what<00:52:44.700> you 00:52:44.809 --> 00:52:44.819 align:start position:0% coming and uh can't wait to see what you 00:52:44.819 --> 00:52:47.000 align:start position:0% coming and uh can't wait to see what you build