WEBVTT Kind: captions Language: en 00:00:01.070 --> 00:00:11.900 align:start position:0% [Applause] 00:00:11.900 --> 00:00:11.910 align:start position:0% 00:00:11.910 --> 00:00:14.400 align:start position:0% it<00:00:12.910> was<00:00:13.000> intended<00:00:13.240> to<00:00:13.360> be<00:00:13.509> sort<00:00:13.750> of<00:00:13.809> a<00:00:13.959> workshop 00:00:14.400 --> 00:00:14.410 align:start position:0% it was intended to be sort of a workshop 00:00:14.410 --> 00:00:17.460 align:start position:0% it was intended to be sort of a workshop so<00:00:14.740> if<00:00:15.039> anyone<00:00:15.369> wants<00:00:15.699> to<00:00:15.730> at<00:00:16.209> the<00:00:16.359> like<00:00:17.200> sort 00:00:17.460 --> 00:00:17.470 align:start position:0% so if anyone wants to at the like sort 00:00:17.470 --> 00:00:19.679 align:start position:0% so if anyone wants to at the like sort of<00:00:17.500> halfway<00:00:17.680> through<00:00:18.130> we'll<00:00:19.060> be<00:00:19.180> doing<00:00:19.449> some 00:00:19.679 --> 00:00:19.689 align:start position:0% of halfway through we'll be doing some 00:00:19.689 --> 00:00:22.470 align:start position:0% of halfway through we'll be doing some coding<00:00:19.900> if<00:00:20.289> anyone<00:00:20.619> wants<00:00:20.919> to<00:00:21.150> take<00:00:22.150> out<00:00:22.300> their 00:00:22.470 --> 00:00:22.480 align:start position:0% coding if anyone wants to take out their 00:00:22.480 --> 00:00:25.380 align:start position:0% coding if anyone wants to take out their laptop<00:00:22.869> and<00:00:23.110> try<00:00:23.800> some<00:00:23.980> stuff<00:00:24.070> out<00:00:24.369> if<00:00:25.150> not 00:00:25.380 --> 00:00:25.390 align:start position:0% laptop and try some stuff out if not 00:00:25.390 --> 00:00:30.540 align:start position:0% laptop and try some stuff out if not that<00:00:25.839> worries<00:00:26.880> but<00:00:27.880> yeah<00:00:28.140> so<00:00:29.140> this<00:00:29.919> the 00:00:30.540 --> 00:00:30.550 align:start position:0% that worries but yeah so this the 00:00:30.550 --> 00:00:33.390 align:start position:0% that worries but yeah so this the workshop<00:00:31.119> overview<00:00:31.599> the<00:00:32.199> introduction<00:00:33.040> is 00:00:33.390 --> 00:00:33.400 align:start position:0% workshop overview the introduction is 00:00:33.400 --> 00:00:34.710 align:start position:0% workshop overview the introduction is just<00:00:33.820> a<00:00:34.000> little<00:00:34.269> bit<00:00:34.390> of<00:00:34.510> background 00:00:34.710 --> 00:00:34.720 align:start position:0% just a little bit of background 00:00:34.720 --> 00:00:38.250 align:start position:0% just a little bit of background amenities<00:00:35.790> for<00:00:36.790> those<00:00:36.940> of<00:00:37.449> you<00:00:37.660> who<00:00:37.809> aren't<00:00:38.019> as 00:00:38.250 --> 00:00:38.260 align:start position:0% amenities for those of you who aren't as 00:00:38.260 --> 00:00:40.290 align:start position:0% amenities for those of you who aren't as familiar<00:00:38.589> with<00:00:38.860> them<00:00:39.129> a<00:00:39.400> little<00:00:40.120> bit<00:00:40.210> of 00:00:40.290 --> 00:00:40.300 align:start position:0% familiar with them a little bit of 00:00:40.300 --> 00:00:43.650 align:start position:0% familiar with them a little bit of background<00:00:40.480> on<00:00:40.900> open<00:00:41.440> seat<00:00:41.940> and<00:00:42.940> then<00:00:43.120> the 00:00:43.650 --> 00:00:43.660 align:start position:0% background on open seat and then the 00:00:43.660 --> 00:00:45.840 align:start position:0% background on open seat and then the second<00:00:44.020> part<00:00:44.230> of<00:00:44.289> the<00:00:44.460> presentation<00:00:45.460> will<00:00:45.820> be 00:00:45.840 --> 00:00:45.850 align:start position:0% second part of the presentation will be 00:00:45.850 --> 00:00:48.810 align:start position:0% second part of the presentation will be the<00:00:46.690> develop<00:00:47.020> a<00:00:47.079> goal<00:00:47.260> of<00:00:47.530> deploying<00:00:48.309> a 00:00:48.810 --> 00:00:48.820 align:start position:0% the develop a goal of deploying a 00:00:48.820 --> 00:00:49.650 align:start position:0% the develop a goal of deploying a tradable 00:00:49.650 --> 00:00:49.660 align:start position:0% tradable 00:00:49.660 --> 00:00:53.849 align:start position:0% tradable nft<00:00:50.620> conference<00:00:51.160> ticket<00:00:51.930> with<00:00:52.930> the<00:00:53.170> sub<00:00:53.620> goals 00:00:53.849 --> 00:00:53.859 align:start position:0% nft conference ticket with the sub goals 00:00:53.859 --> 00:00:58.610 align:start position:0% nft conference ticket with the sub goals of<00:00:54.300> implanting<00:00:55.300> a<00:00:55.570> simple<00:00:56.199> GRC<00:00:56.739> 7.1<00:00:57.489> contract 00:00:58.610 --> 00:00:58.620 align:start position:0% of implanting a simple GRC 7.1 contract 00:00:58.620 --> 00:01:00.990 align:start position:0% of implanting a simple GRC 7.1 contract viewing<00:00:59.620> the<00:00:59.800> tickets<00:01:00.160> on<00:01:00.399> marketplace 00:01:00.990 --> 00:01:01.000 align:start position:0% viewing the tickets on marketplace 00:01:01.000 --> 00:01:03.000 align:start position:0% viewing the tickets on marketplace putting<00:01:01.390> them<00:01:01.480> on<00:01:01.600> sale<00:01:01.780> that<00:01:02.530> maybe<00:01:02.769> as<00:01:02.980> a 00:01:03.000 --> 00:01:03.010 align:start position:0% putting them on sale that maybe as a 00:01:03.010 --> 00:01:07.020 align:start position:0% putting them on sale that maybe as a take-home<00:01:03.850> task<00:01:05.070> programmatically<00:01:06.070> selling 00:01:07.020 --> 00:01:07.030 align:start position:0% take-home task programmatically selling 00:01:07.030 --> 00:01:10.260 align:start position:0% take-home task programmatically selling the<00:01:07.330> tickets<00:01:08.200> using<00:01:08.890> something<00:01:09.880> like<00:01:10.030> the 00:01:10.260 --> 00:01:10.270 align:start position:0% the tickets using something like the 00:01:10.270 --> 00:01:14.820 align:start position:0% the tickets using something like the open<00:01:10.509> sea<00:01:10.660> SDK<00:01:11.080> so<00:01:13.289> how<00:01:14.289> many<00:01:14.349> of<00:01:14.560> you<00:01:14.649> are 00:01:14.820 --> 00:01:14.830 align:start position:0% open sea SDK so how many of you are 00:01:14.830 --> 00:01:21.650 align:start position:0% open sea SDK so how many of you are familiar<00:01:15.459> with<00:01:16.179> GRC<00:01:16.929> 721<00:01:19.380> SS<00:01:20.410> majority<00:01:21.250> room 00:01:21.650 --> 00:01:21.660 align:start position:0% familiar with GRC 721 SS majority room 00:01:21.660 --> 00:01:25.219 align:start position:0% familiar with GRC 721 SS majority room so<00:01:22.660> this<00:01:23.349> is<00:01:23.590> probably<00:01:24.039> just<00:01:24.130> a<00:01:24.340> refresher<00:01:24.670> but 00:01:25.219 --> 00:01:25.229 align:start position:0% so this is probably just a refresher but 00:01:25.229 --> 00:01:29.010 align:start position:0% so this is probably just a refresher but the<00:01:26.229> ERC<00:01:26.590> 20<00:01:27.009> R<00:01:27.539> represents<00:01:28.539> what<00:01:28.720> are<00:01:28.810> called 00:01:29.010 --> 00:01:29.020 align:start position:0% the ERC 20 R represents what are called 00:01:29.020 --> 00:01:32.999 align:start position:0% the ERC 20 R represents what are called fungible<00:01:29.830> assets<00:01:30.310> so<00:01:30.899> currencies<00:01:31.899> and<00:01:32.380> ERC 00:01:32.999 --> 00:01:33.009 align:start position:0% fungible assets so currencies and ERC 00:01:33.009 --> 00:01:37.499 align:start position:0% fungible assets so currencies and ERC 721<00:01:33.670> was<00:01:34.450> designed<00:01:35.110> to<00:01:35.349> represent<00:01:36.030> unique<00:01:37.030> or 00:01:37.499 --> 00:01:37.509 align:start position:0% 721 was designed to represent unique or 00:01:37.509 --> 00:01:40.559 align:start position:0% 721 was designed to represent unique or non<00:01:37.929> fungible<00:01:38.560> digital<00:01:39.310> assets<00:01:39.640> so<00:01:39.880> each<00:01:40.179> one 00:01:40.559 --> 00:01:40.569 align:start position:0% non fungible digital assets so each one 00:01:40.569 --> 00:01:43.300 align:start position:0% non fungible digital assets so each one was<00:01:40.989> associated<00:01:41.590> with<00:01:41.739> a<00:01:42.009> unique 00:01:43.300 --> 00:01:43.310 align:start position:0% was associated with a unique 00:01:43.310 --> 00:01:47.590 align:start position:0% was associated with a unique fire<00:01:43.579> and<00:01:43.909> the<00:01:44.720> space<00:01:45.649> of<00:01:46.180> one<00:01:47.180> of<00:01:47.270> the<00:01:47.329> reasons 00:01:47.590 --> 00:01:47.600 align:start position:0% fire and the space of one of the reasons 00:01:47.600 --> 00:01:49.630 align:start position:0% fire and the space of one of the reasons we're<00:01:47.780> excited<00:01:48.079> about<00:01:48.259> non-financial<00:01:49.250> assets 00:01:49.630 --> 00:01:49.640 align:start position:0% we're excited about non-financial assets 00:01:49.640 --> 00:01:51.580 align:start position:0% we're excited about non-financial assets is<00:01:49.880> we<00:01:50.329> actually<00:01:50.450> think<00:01:50.720> that<00:01:50.960> the<00:01:51.290> number<00:01:51.560> of 00:01:51.580 --> 00:01:51.590 align:start position:0% is we actually think that the number of 00:01:51.590 --> 00:01:54.520 align:start position:0% is we actually think that the number of currencies<00:01:52.159> that<00:01:52.789> individuals<00:01:53.780> will<00:01:54.079> use<00:01:54.289> on 00:01:54.520 --> 00:01:54.530 align:start position:0% currencies that individuals will use on 00:01:54.530 --> 00:01:58.240 align:start position:0% currencies that individuals will use on a<00:01:54.560> day-to-day<00:01:54.950> basis<00:01:55.539> is<00:01:56.539> limited<00:01:56.990> to<00:01:57.259> maybe 00:01:58.240 --> 00:01:58.250 align:start position:0% a day-to-day basis is limited to maybe 00:01:58.250 --> 00:02:00.969 align:start position:0% a day-to-day basis is limited to maybe stable<00:01:58.670> plans<00:01:59.110> maybe<00:02:00.110> in-game<00:02:00.500> currencies 00:02:00.969 --> 00:02:00.979 align:start position:0% stable plans maybe in-game currencies 00:02:00.979 --> 00:02:03.219 align:start position:0% stable plans maybe in-game currencies it's<00:02:01.189> like<00:02:01.340> this<00:02:01.520> but<00:02:02.060> the<00:02:02.149> number<00:02:02.390> of<00:02:02.420> digital 00:02:03.219 --> 00:02:03.229 align:start position:0% it's like this but the number of digital 00:02:03.229 --> 00:02:05.289 align:start position:0% it's like this but the number of digital assets<00:02:03.500> that<00:02:03.619> we<00:02:03.740> already<00:02:04.159> use<00:02:04.399> day<00:02:05.090> to<00:02:05.119> day 00:02:05.289 --> 00:02:05.299 align:start position:0% assets that we already use day to day 00:02:05.299 --> 00:02:08.199 align:start position:0% assets that we already use day to day basis<00:02:05.720> it<00:02:05.899> is<00:02:06.409> very<00:02:06.649> wide<00:02:06.950> so<00:02:06.979> yeah<00:02:07.970> things 00:02:08.199 --> 00:02:08.209 align:start position:0% basis it is very wide so yeah things 00:02:08.209 --> 00:02:10.089 align:start position:0% basis it is very wide so yeah things like<00:02:08.269> game<00:02:08.539> items<00:02:08.899> things<00:02:09.319> like<00:02:09.530> domain<00:02:09.830> names 00:02:10.089 --> 00:02:10.099 align:start position:0% like game items things like domain names 00:02:10.099 --> 00:02:12.190 align:start position:0% like game items things like domain names include<00:02:10.610> event<00:02:10.880> tickets<00:02:11.239> and<00:02:11.540> then<00:02:11.660> when<00:02:12.140> you 00:02:12.190 --> 00:02:12.200 align:start position:0% include event tickets and then when you 00:02:12.200 --> 00:02:14.979 align:start position:0% include event tickets and then when you start<00:02:12.530> connecting<00:02:13.040> these<00:02:13.940> digital<00:02:14.390> assets<00:02:14.690> to 00:02:14.979 --> 00:02:14.989 align:start position:0% start connecting these digital assets to 00:02:14.989 --> 00:02:18.370 align:start position:0% start connecting these digital assets to the<00:02:15.819> real<00:02:16.819> world<00:02:17.060> you<00:02:17.299> have<00:02:17.510> you<00:02:18.110> know<00:02:18.230> things 00:02:18.370 --> 00:02:18.380 align:start position:0% the real world you have you know things 00:02:18.380 --> 00:02:20.320 align:start position:0% the real world you have you know things like<00:02:18.560> real<00:02:18.769> estate<00:02:18.799> or<00:02:19.340> physical<00:02:19.880> items<00:02:20.150> as 00:02:20.320 --> 00:02:20.330 align:start position:0% like real estate or physical items as 00:02:20.330 --> 00:02:22.270 align:start position:0% like real estate or physical items as well<00:02:20.480> that<00:02:20.660> could<00:02:20.750> be<00:02:20.890> represented<00:02:21.890> using 00:02:22.270 --> 00:02:22.280 align:start position:0% well that could be represented using 00:02:22.280 --> 00:02:27.340 align:start position:0% well that could be represented using this<00:02:22.519> standard<00:02:25.000> so<00:02:26.000> a<00:02:26.030> little<00:02:26.360> bit<00:02:26.510> of<00:02:26.630> history 00:02:27.340 --> 00:02:27.350 align:start position:0% this standard so a little bit of history 00:02:27.350 --> 00:02:31.990 align:start position:0% this standard so a little bit of history of<00:02:27.830> GRC<00:02:28.280> 7:21<00:02:29.060> so<00:02:29.900> 2017<00:02:30.830> has<00:02:31.400> anyone<00:02:31.700> heard<00:02:31.880> of 00:02:31.990 --> 00:02:32.000 align:start position:0% of GRC 7:21 so 2017 has anyone heard of 00:02:32.000 --> 00:02:35.920 align:start position:0% of GRC 7:21 so 2017 has anyone heard of crypto<00:02:32.390> punks<00:02:32.720> that<00:02:33.549> so<00:02:34.549> most<00:02:35.030> people<00:02:35.480> so 00:02:35.920 --> 00:02:35.930 align:start position:0% crypto punks that so most people so 00:02:35.930 --> 00:02:38.110 align:start position:0% crypto punks that so most people so Krypton<00:02:36.230> Punk's<00:02:36.500> was<00:02:36.680> sort<00:02:36.920> of<00:02:36.980> the<00:02:37.130> first<00:02:37.340> non 00:02:38.110 --> 00:02:38.120 align:start position:0% Krypton Punk's was sort of the first non 00:02:38.120 --> 00:02:40.320 align:start position:0% Krypton Punk's was sort of the first non fungible<00:02:38.599> asset<00:02:38.810> on<00:02:39.230> aetherium<00:02:39.830> there<00:02:40.130> were 00:02:40.320 --> 00:02:40.330 align:start position:0% fungible asset on aetherium there were 00:02:40.330 --> 00:02:43.720 align:start position:0% fungible asset on aetherium there were non-financial<00:02:41.330> assets<00:02:41.980> using<00:02:42.980> Bitcoin 00:02:43.720 --> 00:02:43.730 align:start position:0% non-financial assets using Bitcoin 00:02:43.730 --> 00:02:46.120 align:start position:0% non-financial assets using Bitcoin counterparty<00:02:44.390> but<00:02:45.170> it<00:02:45.500> was<00:02:45.680> sort<00:02:45.980> of<00:02:46.010> the 00:02:46.120 --> 00:02:46.130 align:start position:0% counterparty but it was sort of the 00:02:46.130 --> 00:02:49.360 align:start position:0% counterparty but it was sort of the first<00:02:46.340> one<00:02:46.870> that<00:02:47.870> you<00:02:48.650> know<00:02:48.769> was<00:02:48.950> the<00:02:49.070> idea<00:02:49.310> of 00:02:49.360 --> 00:02:49.370 align:start position:0% first one that you know was the idea of 00:02:49.370 --> 00:02:51.340 align:start position:0% first one that you know was the idea of a<00:02:49.549> crypto<00:02:49.880> collectible<00:02:50.359> and<00:02:50.450> ethereal<00:02:50.870> but 00:02:51.340 --> 00:02:51.350 align:start position:0% a crypto collectible and ethereal but 00:02:51.350 --> 00:02:53.830 align:start position:0% a crypto collectible and ethereal but there<00:02:51.470> was<00:02:51.560> no<00:02:51.680> standard<00:02:52.280> around<00:02:52.609> it<00:02:52.790> and<00:02:53.570> what 00:02:53.830 --> 00:02:53.840 align:start position:0% there was no standard around it and what 00:02:53.840 --> 00:02:55.509 align:start position:0% there was no standard around it and what crypto<00:02:54.140> kiddies<00:02:54.410> did<00:02:54.650> was<00:02:54.859> number<00:02:55.220> one<00:02:55.370> they 00:02:55.509 --> 00:02:55.519 align:start position:0% crypto kiddies did was number one they 00:02:55.519 --> 00:02:58.509 align:start position:0% crypto kiddies did was number one they built<00:02:55.760> a<00:02:56.000> game<00:02:56.900> around<00:02:57.500> these<00:02:57.680> assets<00:02:58.160> but 00:02:58.509 --> 00:02:58.519 align:start position:0% built a game around these assets but 00:02:58.519 --> 00:03:01.720 align:start position:0% built a game around these assets but they<00:02:58.640> also<00:02:59.079> pioneered<00:03:00.079> the<00:03:00.680> ERC<00:03:01.010> 7:21 00:03:01.720 --> 00:03:01.730 align:start position:0% they also pioneered the ERC 7:21 00:03:01.730 --> 00:03:04.449 align:start position:0% they also pioneered the ERC 7:21 standard<00:03:02.209> which<00:03:02.750> was<00:03:02.989> refined<00:03:03.859> by<00:03:04.400> the 00:03:04.449 --> 00:03:04.459 align:start position:0% standard which was refined by the 00:03:04.459 --> 00:03:06.970 align:start position:0% standard which was refined by the etherium<00:03:05.239> community<00:03:05.780> such<00:03:06.410> that<00:03:06.620> it<00:03:06.709> could<00:03:06.859> be 00:03:06.970 --> 00:03:06.980 align:start position:0% etherium community such that it could be 00:03:06.980 --> 00:03:09.910 align:start position:0% etherium community such that it could be leveraged<00:03:07.459> by<00:03:07.730> other<00:03:08.299> projects<00:03:09.019> so<00:03:09.739> one<00:03:09.890> of 00:03:09.910 --> 00:03:09.920 align:start position:0% leveraged by other projects so one of 00:03:09.920 --> 00:03:11.559 align:start position:0% leveraged by other projects so one of those<00:03:10.100> early<00:03:10.549> projects<00:03:11.060> was<00:03:11.209> a<00:03:11.239> project 00:03:11.559 --> 00:03:11.569 align:start position:0% those early projects was a project 00:03:11.569 --> 00:03:13.930 align:start position:0% those early projects was a project called<00:03:11.900> the<00:03:11.930> central<00:03:12.410> and<00:03:12.560> which<00:03:13.220> represented 00:03:13.930 --> 00:03:13.940 align:start position:0% called the central and which represented 00:03:13.940 --> 00:03:17.289 align:start position:0% called the central and which represented their<00:03:14.180> virtual<00:03:14.750> land<00:03:15.160> using<00:03:16.160> the<00:03:16.430> ERC<00:03:16.700> 7:21 00:03:17.289 --> 00:03:17.299 align:start position:0% their virtual land using the ERC 7:21 00:03:17.299 --> 00:03:20.949 align:start position:0% their virtual land using the ERC 7:21 standard<00:03:17.630> that<00:03:17.780> was<00:03:17.900> in<00:03:18.049> like<00:03:18.230> late<00:03:18.380> 2017<00:03:19.959> in 00:03:20.949 --> 00:03:20.959 align:start position:0% standard that was in like late 2017 in 00:03:20.959 --> 00:03:23.610 align:start position:0% standard that was in like late 2017 in early<00:03:21.319> 2018<00:03:21.590> we<00:03:22.069> sort<00:03:22.280> of<00:03:22.370> had<00:03:22.609> a<00:03:22.639> miniature 00:03:23.610 --> 00:03:23.620 align:start position:0% early 2018 we sort of had a miniature 00:03:23.620 --> 00:03:26.620 align:start position:0% early 2018 we sort of had a miniature cranes<00:03:24.620> around<00:03:25.100> non-clinical<00:03:26.090> tokens<00:03:26.569> that 00:03:26.620 --> 00:03:26.630 align:start position:0% cranes around non-clinical tokens that 00:03:26.630 --> 00:03:29.590 align:start position:0% cranes around non-clinical tokens that was<00:03:26.840> a<00:03:26.870> lot<00:03:27.109> more<00:03:27.139> isolated<00:03:28.010> to<00:03:28.519> the<00:03:29.269> early 00:03:29.590 --> 00:03:29.600 align:start position:0% was a lot more isolated to the early 00:03:29.600 --> 00:03:32.199 align:start position:0% was a lot more isolated to the early adopter<00:03:30.079> tech<00:03:30.410> enthusiasts<00:03:31.160> that<00:03:31.340> you<00:03:32.120> know 00:03:32.199 --> 00:03:32.209 align:start position:0% adopter tech enthusiasts that you know 00:03:32.209 --> 00:03:33.910 align:start position:0% adopter tech enthusiasts that you know relative<00:03:32.660> to<00:03:32.690> the<00:03:33.139> cranes<00:03:33.380> that<00:03:33.590> we<00:03:33.709> saw 00:03:33.910 --> 00:03:33.920 align:start position:0% relative to the cranes that we saw 00:03:33.920 --> 00:03:36.370 align:start position:0% relative to the cranes that we saw around<00:03:34.040> ICS<00:03:34.670> and<00:03:34.940> years<00:03:35.120> of<00:03:35.239> 20s<00:03:35.569> but<00:03:36.260> there 00:03:36.370 --> 00:03:36.380 align:start position:0% around ICS and years of 20s but there 00:03:36.380 --> 00:03:38.710 align:start position:0% around ICS and years of 20s but there were<00:03:36.470> a<00:03:36.500> lot<00:03:36.650> of<00:03:37.090> perpetuity<00:03:38.090> clones<00:03:38.359> like 00:03:38.710 --> 00:03:38.720 align:start position:0% were a lot of perpetuity clones like 00:03:38.720 --> 00:03:41.440 align:start position:0% were a lot of perpetuity clones like crypto<00:03:39.019> BOTS<00:03:39.230> crypto<00:03:39.620> fighters<00:03:39.950> and<00:03:40.910> there 00:03:41.440 --> 00:03:41.450 align:start position:0% crypto BOTS crypto fighters and there 00:03:41.450 --> 00:03:43.509 align:start position:0% crypto BOTS crypto fighters and there were<00:03:41.540> also<00:03:41.690> these<00:03:41.930> games<00:03:42.709> called<00:03:43.010> hot<00:03:43.190> potato 00:03:43.509 --> 00:03:43.519 align:start position:0% were also these games called hot potato 00:03:43.519 --> 00:03:46.360 align:start position:0% were also these games called hot potato games<00:03:43.819> which<00:03:44.180> were<00:03:44.440> kind<00:03:45.440> of<00:03:45.530> these<00:03:45.680> games 00:03:46.360 --> 00:03:46.370 align:start position:0% games which were kind of these games 00:03:46.370 --> 00:03:48.400 align:start position:0% games which were kind of these games where<00:03:46.549> you<00:03:46.670> would<00:03:46.850> buy<00:03:47.000> a<00:03:47.389> collectible<00:03:48.260> with 00:03:48.400 --> 00:03:48.410 align:start position:0% where you would buy a collectible with 00:03:48.410 --> 00:03:50.349 align:start position:0% where you would buy a collectible with the<00:03:48.530> intention<00:03:48.950> of<00:03:49.010> selling<00:03:49.790> it<00:03:50.000> at<00:03:50.150> a<00:03:50.209> higher 00:03:50.349 --> 00:03:50.359 align:start position:0% the intention of selling it at a higher 00:03:50.359 --> 00:03:52.570 align:start position:0% the intention of selling it at a higher price<00:03:50.660> so<00:03:51.019> it's<00:03:51.349> kind<00:03:51.500> of<00:03:51.560> this<00:03:51.709> you<00:03:52.310> know<00:03:52.400> even 00:03:52.570 --> 00:03:52.580 align:start position:0% price so it's kind of this you know even 00:03:52.580 --> 00:03:55.119 align:start position:0% price so it's kind of this you know even more<00:03:52.849> experimental<00:03:53.750> period<00:03:54.409> than<00:03:54.920> we're 00:03:55.119 --> 00:03:55.129 align:start position:0% more experimental period than we're 00:03:55.129 --> 00:03:57.250 align:start position:0% more experimental period than we're going<00:03:55.370> through<00:03:55.610> right<00:03:55.700> now<00:03:55.849> with<00:03:56.330> you<00:03:57.110> know<00:03:57.200> a 00:03:57.250 --> 00:03:57.260 align:start position:0% going through right now with you know a 00:03:57.260 --> 00:04:01.420 align:start position:0% going through right now with you know a lot<00:03:57.680> of<00:03:57.970> scamming<00:03:58.970> projects<00:03:59.360> as<00:03:59.450> well<00:03:59.950> in<00:04:00.950> mid 00:04:01.420 --> 00:04:01.430 align:start position:0% lot of scamming projects as well in mid 00:04:01.430 --> 00:04:05.710 align:start position:0% lot of scamming projects as well in mid 2018<00:04:02.140> we<00:04:03.140> started<00:04:03.950> seeing<00:04:04.189> higher<00:04:05.090> quality 00:04:05.710 --> 00:04:05.720 align:start position:0% 2018 we started seeing higher quality 00:04:05.720 --> 00:04:08.649 align:start position:0% 2018 we started seeing higher quality projects<00:04:06.500> enter<00:04:06.860> the<00:04:06.980> space<00:04:07.189> so<00:04:08.030> this<00:04:08.450> year 00:04:08.649 --> 00:04:08.659 align:start position:0% projects enter the space so this year 00:04:08.659 --> 00:04:10.929 align:start position:0% projects enter the space so this year right<00:04:08.750> there<00:04:08.810> and<00:04:09.319> there<00:04:09.620> were<00:04:09.709> a<00:04:09.739> lot<00:04:09.980> are 00:04:10.929 --> 00:04:10.939 align:start position:0% right there and there were a lot are 00:04:10.939 --> 00:04:12.880 align:start position:0% right there and there were a lot are gods<00:04:11.330> Unchained<00:04:11.840> which<00:04:12.019> is<00:04:12.200> a<00:04:12.230> trading<00:04:12.680> card 00:04:12.880 --> 00:04:12.890 align:start position:0% gods Unchained which is a trading card 00:04:12.890 --> 00:04:15.610 align:start position:0% gods Unchained which is a trading card game<00:04:13.099> that<00:04:13.370> used<00:04:13.610> the<00:04:14.150> ERC<00:04:14.329> 7:21<00:04:15.079> to<00:04:15.260> represent 00:04:15.610 --> 00:04:15.620 align:start position:0% game that used the ERC 7:21 to represent 00:04:15.620 --> 00:04:18.399 align:start position:0% game that used the ERC 7:21 to represent their<00:04:15.709> assets<00:04:16.039> and<00:04:16.250> then<00:04:17.030> MLB<00:04:17.750> crypto<00:04:18.200> which 00:04:18.399 --> 00:04:18.409 align:start position:0% their assets and then MLB crypto which 00:04:18.409 --> 00:04:20.710 align:start position:0% their assets and then MLB crypto which was<00:04:18.560> actually<00:04:18.890> an<00:04:18.979> officially<00:04:19.489> licensed<00:04:20.120> game 00:04:20.710 --> 00:04:20.720 align:start position:0% was actually an officially licensed game 00:04:20.720 --> 00:04:23.860 align:start position:0% was actually an officially licensed game from<00:04:21.140> the<00:04:21.289> Emily<00:04:21.820> that<00:04:22.820> that<00:04:23.510> have<00:04:23.690> these 00:04:23.860 --> 00:04:23.870 align:start position:0% from the Emily that that have these 00:04:23.870 --> 00:04:25.990 align:start position:0% from the Emily that that have these crypto<00:04:24.800> collectively<00:04:25.220> associated<00:04:25.729> with<00:04:25.849> them 00:04:25.990 --> 00:04:26.000 align:start position:0% crypto collectively associated with them 00:04:26.000 --> 00:04:28.600 align:start position:0% crypto collectively associated with them and<00:04:26.390> that<00:04:27.050> brings<00:04:27.289> us<00:04:27.470> to<00:04:27.500> 2019<00:04:28.190> we're 00:04:28.600 --> 00:04:28.610 align:start position:0% and that brings us to 2019 we're 00:04:28.610 --> 00:04:31.659 align:start position:0% and that brings us to 2019 we're actually<00:04:29.390> you<00:04:29.990> know<00:04:30.110> it's<00:04:30.710> less<00:04:31.130> of<00:04:31.159> a<00:04:31.460> well 00:04:31.659 --> 00:04:31.669 align:start position:0% actually you know it's less of a well 00:04:31.669 --> 00:04:35.740 align:start position:0% actually you know it's less of a well known<00:04:31.849> space<00:04:32.150> in<00:04:32.510> the<00:04:33.280> crypto<00:04:34.280> sphere<00:04:35.240> but 00:04:35.740 --> 00:04:35.750 align:start position:0% known space in the crypto sphere but 00:04:35.750 --> 00:04:36.969 align:start position:0% known space in the crypto sphere but there's<00:04:36.050> actually<00:04:36.349> quite<00:04:36.470> a<00:04:36.560> lot<00:04:36.770> of<00:04:36.800> activity 00:04:36.969 --> 00:04:36.979 align:start position:0% there's actually quite a lot of activity 00:04:36.979 --> 00:04:49.790 align:start position:0% there's actually quite a lot of activity happening<00:04:37.669> in<00:04:38.180> the<00:04:38.840> NFT<00:04:39.409> space<00:04:39.830> right<00:04:40.070> now<00:04:40.190> so 00:04:49.790 --> 00:04:49.800 align:start position:0% 00:04:49.800 --> 00:04:53.880 align:start position:0% so<00:04:50.800> a<00:04:51.550> Formula<00:04:52.330> One<00:04:52.360> recently<00:04:53.320> auctioned<00:04:53.770> off 00:04:53.880 --> 00:04:53.890 align:start position:0% so a Formula One recently auctioned off 00:04:53.890 --> 00:04:56.700 align:start position:0% so a Formula One recently auctioned off some<00:04:54.430> cars<00:04:54.720> using<00:04:55.720> our<00:04:55.840> marketplace<00:04:56.140> actually 00:04:56.700 --> 00:04:56.710 align:start position:0% some cars using our marketplace actually 00:04:56.710 --> 00:04:59.310 align:start position:0% some cars using our marketplace actually there's<00:04:57.640> a<00:04:58.000> couple<00:04:58.300> of<00:04:58.420> Japanese<00:04:58.810> games<00:04:59.050> that 00:04:59.310 --> 00:04:59.320 align:start position:0% there's a couple of Japanese games that 00:04:59.320 --> 00:05:01.170 align:start position:0% there's a couple of Japanese games that are<00:04:59.410> becoming<00:04:59.620> really<00:04:59.860> popular<00:05:00.030> there's<00:05:01.030> a 00:05:01.170 --> 00:05:01.180 align:start position:0% are becoming really popular there's a 00:05:01.180 --> 00:05:05.880 align:start position:0% are becoming really popular there's a space<00:05:01.660> game<00:05:02.700> that<00:05:03.700> is<00:05:04.570> kind<00:05:05.440> of<00:05:05.500> like<00:05:05.680> EVE 00:05:05.880 --> 00:05:05.890 align:start position:0% space game that is kind of like EVE 00:05:05.890 --> 00:05:07.560 align:start position:0% space game that is kind of like EVE Online<00:05:06.250> if<00:05:06.460> anyone's<00:05:06.760> played<00:05:06.970> that<00:05:07.150> and<00:05:07.450> then 00:05:07.560 --> 00:05:07.570 align:start position:0% Online if anyone's played that and then 00:05:07.570 --> 00:05:10.500 align:start position:0% Online if anyone's played that and then there<00:05:08.080> are<00:05:08.260> starting<00:05:08.500> to<00:05:08.650> be<00:05:09.180> assets<00:05:10.180> that<00:05:10.360> are 00:05:10.500 --> 00:05:10.510 align:start position:0% there are starting to be assets that are 00:05:10.510 --> 00:05:12.810 align:start position:0% there are starting to be assets that are not<00:05:10.660> in<00:05:10.990> just<00:05:11.530> collectibles<00:05:12.100> and<00:05:12.250> gaming<00:05:12.580> so 00:05:12.810 --> 00:05:12.820 align:start position:0% not in just collectibles and gaming so 00:05:12.820 --> 00:05:15.690 align:start position:0% not in just collectibles and gaming so ens<00:05:13.630> is<00:05:13.840> one<00:05:13.990> of<00:05:14.110> those<00:05:14.260> that<00:05:14.890> is<00:05:15.010> using<00:05:15.580> the 00:05:15.690 --> 00:05:15.700 align:start position:0% ens is one of those that is using the 00:05:15.700 --> 00:05:19.440 align:start position:0% ens is one of those that is using the ERC<00:05:15.910> 7:21<00:05:16.540> standard<00:05:16.960> to<00:05:17.260> allow<00:05:17.640> their<00:05:18.640> names 00:05:19.440 --> 00:05:19.450 align:start position:0% ERC 7:21 standard to allow their names 00:05:19.450 --> 00:05:24.540 align:start position:0% ERC 7:21 standard to allow their names to<00:05:19.780> be<00:05:19.930> tradable<00:05:21.870> so<00:05:22.870> one<00:05:23.770> question<00:05:23.980> one<00:05:24.370> might 00:05:24.540 --> 00:05:24.550 align:start position:0% to be tradable so one question one might 00:05:24.550 --> 00:05:27.390 align:start position:0% to be tradable so one question one might ask<00:05:24.730> is<00:05:24.970> like<00:05:25.210> why<00:05:25.450> why<00:05:26.290> is<00:05:26.350> gaming<00:05:26.980> kind<00:05:27.340> of 00:05:27.390 --> 00:05:27.400 align:start position:0% ask is like why why is gaming kind of 00:05:27.400 --> 00:05:30.240 align:start position:0% ask is like why why is gaming kind of the<00:05:27.580> leader<00:05:27.820> here<00:05:28.390> so<00:05:29.200> why<00:05:29.350> is<00:05:29.410> this<00:05:29.560> a<00:05:29.620> an 00:05:30.240 --> 00:05:30.250 align:start position:0% the leader here so why is this a an 00:05:30.250 --> 00:05:33.930 align:start position:0% the leader here so why is this a an interesting<00:05:30.850> fit<00:05:31.150> for<00:05:31.480> gaming<00:05:32.700> number<00:05:33.700> one<00:05:33.910> I 00:05:33.930 --> 00:05:33.940 align:start position:0% interesting fit for gaming number one I 00:05:33.940 --> 00:05:36.090 align:start position:0% interesting fit for gaming number one I think<00:05:34.300> gaming<00:05:34.780> is<00:05:34.960> often<00:05:35.500> done<00:05:35.680> like<00:05:35.860> a 00:05:36.090 --> 00:05:36.100 align:start position:0% think gaming is often done like a 00:05:36.100 --> 00:05:38.310 align:start position:0% think gaming is often done like a digital<00:05:36.430> sort<00:05:37.060> of<00:05:37.120> a<00:05:37.210> playground<00:05:37.750> for<00:05:37.930> any 00:05:38.310 --> 00:05:38.320 align:start position:0% digital sort of a playground for any 00:05:38.320 --> 00:05:40.680 align:start position:0% digital sort of a playground for any technology<00:05:38.680> we<00:05:39.430> saw<00:05:39.580> this<00:05:39.760> with<00:05:39.970> the<00:05:40.030> mobile 00:05:40.680 --> 00:05:40.690 align:start position:0% technology we saw this with the mobile 00:05:40.690 --> 00:05:41.040 align:start position:0% technology we saw this with the mobile phone 00:05:41.040 --> 00:05:41.050 align:start position:0% phone 00:05:41.050 --> 00:05:44.100 align:start position:0% phone we<00:05:41.860> saw<00:05:42.010> this<00:05:42.070> with<00:05:42.250> the<00:05:42.280> early<00:05:42.580> internet<00:05:43.110> but 00:05:44.100 --> 00:05:44.110 align:start position:0% we saw this with the early internet but 00:05:44.110 --> 00:05:46.710 align:start position:0% we saw this with the early internet but you<00:05:44.650> know<00:05:44.740> there's<00:05:44.980> the<00:05:45.280> shift<00:05:45.670> in<00:05:46.000> gaming 00:05:46.710 --> 00:05:46.720 align:start position:0% you know there's the shift in gaming 00:05:46.720 --> 00:05:48.960 align:start position:0% you know there's the shift in gaming that<00:05:46.930> you<00:05:47.500> know<00:05:47.590> folks<00:05:47.830> are<00:05:47.950> excited<00:05:48.370> about<00:05:48.430> is 00:05:48.960 --> 00:05:48.970 align:start position:0% that you know folks are excited about is 00:05:48.970 --> 00:05:51.450 align:start position:0% that you know folks are excited about is this<00:05:49.450> idea<00:05:49.660> that<00:05:50.110> as<00:05:50.320> a<00:05:50.350> game<00:05:50.650> developer<00:05:50.860> you 00:05:51.450 --> 00:05:51.460 align:start position:0% this idea that as a game developer you 00:05:51.460 --> 00:05:53.700 align:start position:0% this idea that as a game developer you sort<00:05:51.700> of<00:05:51.790> manage<00:05:52.150> every<00:05:52.840> piece<00:05:53.110> of<00:05:53.140> your 00:05:53.700 --> 00:05:53.710 align:start position:0% sort of manage every piece of your 00:05:53.710 --> 00:05:56.370 align:start position:0% sort of manage every piece of your economy<00:05:54.180> you<00:05:55.180> manage<00:05:55.660> the<00:05:55.750> supply<00:05:55.930> of<00:05:56.110> your 00:05:56.370 --> 00:05:56.380 align:start position:0% economy you manage the supply of your 00:05:56.380 --> 00:05:58.710 align:start position:0% economy you manage the supply of your items<00:05:56.740> you<00:05:57.400> usually<00:05:57.580> don't<00:05:57.970> allow<00:05:58.120> other 00:05:58.710 --> 00:05:58.720 align:start position:0% items you usually don't allow other 00:05:58.720 --> 00:06:00.440 align:start position:0% items you usually don't allow other items<00:05:59.110> to<00:05:59.260> be<00:05:59.350> imported<00:05:59.830> into<00:05:59.980> your<00:06:00.160> game 00:06:00.440 --> 00:06:00.450 align:start position:0% items to be imported into your game 00:06:00.450 --> 00:06:03.120 align:start position:0% items to be imported into your game there's<00:06:01.450> nothing<00:06:01.720> really<00:06:01.870> exported<00:06:02.860> from<00:06:02.950> the 00:06:03.120 --> 00:06:03.130 align:start position:0% there's nothing really exported from the 00:06:03.130 --> 00:06:06.230 align:start position:0% there's nothing really exported from the game<00:06:03.310> it's<00:06:03.730> sort<00:06:03.970> of<00:06:04.030> this<00:06:04.440> highly<00:06:05.440> controlled 00:06:06.230 --> 00:06:06.240 align:start position:0% game it's sort of this highly controlled 00:06:06.240 --> 00:06:09.600 align:start position:0% game it's sort of this highly controlled isolationist<00:06:07.240> economy<00:06:08.040> and<00:06:09.040> what's<00:06:09.370> exciting 00:06:09.600 --> 00:06:09.610 align:start position:0% isolationist economy and what's exciting 00:06:09.610 --> 00:06:13.470 align:start position:0% isolationist economy and what's exciting is<00:06:09.910> that<00:06:09.940> with<00:06:10.590> blockchains<00:06:11.590> and<00:06:12.480> digital 00:06:13.470 --> 00:06:13.480 align:start position:0% is that with blockchains and digital 00:06:13.480 --> 00:06:15.300 align:start position:0% is that with blockchains and digital ownership<00:06:13.960> you<00:06:14.410> could<00:06:14.560> have<00:06:14.680> an<00:06:14.800> open<00:06:14.919> economy 00:06:15.300 --> 00:06:15.310 align:start position:0% ownership you could have an open economy 00:06:15.310 --> 00:06:17.610 align:start position:0% ownership you could have an open economy where<00:06:15.820> you<00:06:16.570> know<00:06:16.690> you<00:06:16.960> could<00:06:17.110> export<00:06:17.410> things 00:06:17.610 --> 00:06:17.620 align:start position:0% where you know you could export things 00:06:17.620 --> 00:06:19.200 align:start position:0% where you know you could export things from<00:06:17.860> the<00:06:17.950> game<00:06:18.100> you<00:06:18.430> could<00:06:18.640> trade<00:06:18.850> them<00:06:19.030> on 00:06:19.200 --> 00:06:19.210 align:start position:0% from the game you could trade them on 00:06:19.210 --> 00:06:21.180 align:start position:0% from the game you could trade them on open<00:06:19.600> market<00:06:19.900> places<00:06:20.230> you<00:06:20.800> could<00:06:20.950> do<00:06:21.040> all 00:06:21.180 --> 00:06:21.190 align:start position:0% open market places you could do all 00:06:21.190 --> 00:06:23.190 align:start position:0% open market places you could do all these<00:06:21.340> interesting<00:06:21.790> things<00:06:22.000> and<00:06:22.810> so<00:06:22.930> this<00:06:23.080> is 00:06:23.190 --> 00:06:23.200 align:start position:0% these interesting things and so this is 00:06:23.200 --> 00:06:25.020 align:start position:0% these interesting things and so this is kind<00:06:23.440> of<00:06:23.470> the<00:06:23.680> shift<00:06:24.430> that<00:06:24.550> people<00:06:24.910> are 00:06:25.020 --> 00:06:25.030 align:start position:0% kind of the shift that people are 00:06:25.030 --> 00:06:30.750 align:start position:0% kind of the shift that people are excited<00:06:25.270> about<00:06:25.630> in<00:06:25.930> the<00:06:26.680> gaming<00:06:26.980> community<00:06:29.760> so 00:06:30.750 --> 00:06:30.760 align:start position:0% excited about in the gaming community so 00:06:30.760 --> 00:06:33.810 align:start position:0% excited about in the gaming community so a<00:06:30.790> little<00:06:31.150> background<00:06:31.419> on<00:06:31.870> open<00:06:32.590> sea<00:06:32.770> so<00:06:33.520> open 00:06:33.810 --> 00:06:33.820 align:start position:0% a little background on open sea so open 00:06:33.820 --> 00:06:37.970 align:start position:0% a little background on open sea so open sea<00:06:34.060> is<00:06:34.390> a<00:06:34.840> marketplace<00:06:35.500> or<00:06:36.130> all<00:06:36.940> of<00:06:37.000> these 00:06:37.970 --> 00:06:37.980 align:start position:0% sea is a marketplace or all of these 00:06:37.980 --> 00:06:40.830 align:start position:0% sea is a marketplace or all of these items<00:06:38.980> so<00:06:39.250> starting<00:06:39.700> with<00:06:39.820> the<00:06:39.910> year<00:06:40.000> -<00:06:40.150> 721 00:06:40.830 --> 00:06:40.840 align:start position:0% items so starting with the year - 721 00:06:40.840 --> 00:06:43.950 align:start position:0% items so starting with the year - 721 but<00:06:41.740> we<00:06:41.830> recently<00:06:42.010> did<00:06:42.340> a<00:06:42.400> support<00:06:43.060> for<00:06:43.300> a<00:06:43.630> new 00:06:43.950 --> 00:06:43.960 align:start position:0% but we recently did a support for a new 00:06:43.960 --> 00:06:47.220 align:start position:0% but we recently did a support for a new standard<00:06:44.290> called<00:06:44.590> 1155<00:06:45.750> we<00:06:46.750> have<00:06:46.900> around 00:06:47.220 --> 00:06:47.230 align:start position:0% standard called 1155 we have around 00:06:47.230 --> 00:06:50.280 align:start position:0% standard called 1155 we have around 700,000<00:06:48.220> monthly<00:06:48.760> volumes<00:06:49.120> they<00:06:49.960> on<00:06:50.169> the 00:06:50.280 --> 00:06:50.290 align:start position:0% 700,000 monthly volumes they on the 00:06:50.290 --> 00:06:53.960 align:start position:0% 700,000 monthly volumes they on the lower<00:06:50.470> side<00:06:50.830> of<00:06:51.900> centralized<00:06:52.900> exchanges<00:06:53.530> but 00:06:53.960 --> 00:06:53.970 align:start position:0% lower side of centralized exchanges but 00:06:53.970 --> 00:06:56.340 align:start position:0% lower side of centralized exchanges but you<00:06:54.970> know<00:06:55.060> this<00:06:55.210> is<00:06:55.360> volume<00:06:55.750> that<00:06:55.960> people<00:06:56.260> of 00:06:56.340 --> 00:06:56.350 align:start position:0% you know this is volume that people of 00:06:56.350 --> 00:06:59.070 align:start position:0% you know this is volume that people of this<00:06:56.530> is<00:06:56.680> actual<00:06:57.419> unique<00:06:58.419> digital<00:06:58.630> assets 00:06:59.070 --> 00:06:59.080 align:start position:0% this is actual unique digital assets 00:06:59.080 --> 00:07:00.440 align:start position:0% this is actual unique digital assets that<00:06:59.169> are<00:06:59.260> being<00:06:59.380> traded<00:06:59.650> it's<00:06:59.890> not<00:07:00.039> just 00:07:00.440 --> 00:07:00.450 align:start position:0% that are being traded it's not just 00:07:00.450 --> 00:07:03.180 align:start position:0% that are being traded it's not just token<00:07:01.450> which<00:07:01.690> there<00:07:02.260> is<00:07:02.410> a<00:07:02.440> lot<00:07:02.890> of<00:07:03.010> wash 00:07:03.180 --> 00:07:03.190 align:start position:0% token which there is a lot of wash 00:07:03.190 --> 00:07:06.659 align:start position:0% token which there is a lot of wash traded<00:07:03.640> for<00:07:03.960> we<00:07:04.960> also<00:07:05.110> provide<00:07:05.530> an<00:07:05.650> API<00:07:05.800> this 00:07:06.659 --> 00:07:06.669 align:start position:0% traded for we also provide an API this 00:07:06.669 --> 00:07:09.930 align:start position:0% traded for we also provide an API this is<00:07:06.820> more<00:07:07.030> of<00:07:07.120> a<00:07:07.180> convenience<00:07:07.890> for<00:07:08.940> wallets 00:07:09.930 --> 00:07:09.940 align:start position:0% is more of a convenience for wallets 00:07:09.940 --> 00:07:13.080 align:start position:0% is more of a convenience for wallets that<00:07:10.090> are<00:07:10.180> trying<00:07:10.390> to<00:07:10.510> show<00:07:10.840> GRC<00:07:11.590> 721<00:07:12.220> items<00:07:12.550> so 00:07:13.080 --> 00:07:13.090 align:start position:0% that are trying to show GRC 721 items so 00:07:13.090 --> 00:07:14.670 align:start position:0% that are trying to show GRC 721 items so this<00:07:13.180> is<00:07:13.330> used<00:07:13.479> by<00:07:13.630> coin<00:07:13.840> baseball<00:07:14.229> trust 00:07:14.670 --> 00:07:14.680 align:start position:0% this is used by coin baseball trust 00:07:14.680 --> 00:07:16.770 align:start position:0% this is used by coin baseball trust wallet<00:07:14.979> opera<00:07:15.400> and<00:07:15.580> maybe<00:07:16.300> 20<00:07:16.630> other 00:07:16.770 --> 00:07:16.780 align:start position:0% wallet opera and maybe 20 other 00:07:16.780 --> 00:07:20.370 align:start position:0% wallet opera and maybe 20 other different<00:07:17.229> well<00:07:17.350> that's<00:07:17.590> all<00:07:19.140> and<00:07:20.140> then<00:07:20.260> we 00:07:20.370 --> 00:07:20.380 align:start position:0% different well that's all and then we 00:07:20.380 --> 00:07:21.990 align:start position:0% different well that's all and then we partner<00:07:20.740> with<00:07:20.890> a<00:07:20.919> lot<00:07:21.070> of<00:07:21.160> games<00:07:21.370> to<00:07:21.610> build 00:07:21.990 --> 00:07:22.000 align:start position:0% partner with a lot of games to build 00:07:22.000 --> 00:07:25.880 align:start position:0% partner with a lot of games to build customized<00:07:23.340> white-label<00:07:24.340> of<00:07:24.580> market<00:07:24.850> places 00:07:25.880 --> 00:07:25.890 align:start position:0% customized white-label of market places 00:07:25.890 --> 00:07:28.230 align:start position:0% customized white-label of market places so<00:07:26.890> this<00:07:26.950> is<00:07:27.070> kind<00:07:27.220> of<00:07:27.250> what<00:07:27.460> open<00:07:27.760> C<00:07:28.030> looks 00:07:28.230 --> 00:07:28.240 align:start position:0% so this is kind of what open C looks 00:07:28.240 --> 00:07:31.440 align:start position:0% so this is kind of what open C looks like<00:07:28.450> the<00:07:29.380> moment<00:07:29.680> you<00:07:29.740> have<00:07:29.919> an<00:07:30.220> D<00:07:30.640> arcy<00:07:30.820> 7:21 00:07:31.440 --> 00:07:31.450 align:start position:0% like the moment you have an D arcy 7:21 00:07:31.450 --> 00:07:34.140 align:start position:0% like the moment you have an D arcy 7:21 item<00:07:31.780> you<00:07:31.990> can<00:07:32.260> put<00:07:32.950> it<00:07:33.070> on<00:07:33.160> sale<00:07:33.400> it's<00:07:33.940> kind<00:07:34.120> of 00:07:34.140 --> 00:07:34.150 align:start position:0% item you can put it on sale it's kind of 00:07:34.150 --> 00:07:39.300 align:start position:0% item you can put it on sale it's kind of like<00:07:34.330> eBay<00:07:36.120> trades<00:07:37.120> our<00:07:37.270> wallet<00:07:37.539> wallet<00:07:38.310> so 00:07:39.300 --> 00:07:39.310 align:start position:0% like eBay trades our wallet wallet so 00:07:39.310 --> 00:07:41.040 align:start position:0% like eBay trades our wallet wallet so they<00:07:39.700> never<00:07:40.030> leave<00:07:40.330> your<00:07:40.570> account<00:07:40.660> they're 00:07:41.040 --> 00:07:41.050 align:start position:0% they never leave your account they're 00:07:41.050 --> 00:07:45.390 align:start position:0% they never leave your account they're never<00:07:41.200> escrowed<00:07:42.210> and<00:07:43.210> we<00:07:43.990> also<00:07:44.140> provide<00:07:44.710> a<00:07:45.160> lot 00:07:45.390 --> 00:07:45.400 align:start position:0% never escrowed and we also provide a lot 00:07:45.400 --> 00:07:47.610 align:start position:0% never escrowed and we also provide a lot of<00:07:45.789> the<00:07:45.910> functionality<00:07:46.360> that<00:07:46.750> eBay<00:07:47.229> provides 00:07:47.610 --> 00:07:47.620 align:start position:0% of the functionality that eBay provides 00:07:47.620 --> 00:07:49.920 align:start position:0% of the functionality that eBay provides for<00:07:48.100> digital<00:07:48.910> assets<00:07:49.240> so<00:07:49.360> this<00:07:49.510> is<00:07:49.690> the 00:07:49.920 --> 00:07:49.930 align:start position:0% for digital assets so this is the 00:07:49.930 --> 00:07:52.710 align:start position:0% for digital assets so this is the Formula<00:07:50.800> One<00:07:50.830> car<00:07:51.280> museums<00:07:52.210> actually<00:07:52.510> last 00:07:52.710 --> 00:07:52.720 align:start position:0% Formula One car museums actually last 00:07:52.720 --> 00:07:54.330 align:start position:0% Formula One car museums actually last sold<00:07:53.050> for<00:07:53.350> 450 00:07:54.330 --> 00:07:54.340 align:start position:0% sold for 450 00:07:54.340 --> 00:07:58.170 align:start position:0% sold for 450 either<00:07:54.639> this<00:07:55.120> is<00:07:55.300> a<00:07:55.540> record<00:07:56.199> sale<00:07:56.610> in<00:07:57.610> NFC 00:07:58.170 --> 00:07:58.180 align:start position:0% either this is a record sale in NFC 00:07:58.180 --> 00:08:01.890 align:start position:0% either this is a record sale in NFC community<00:07:58.630> and<00:07:59.970> you<00:08:00.970> know<00:08:01.000> basically<00:08:01.240> we 00:08:01.890 --> 00:08:01.900 align:start position:0% community and you know basically we 00:08:01.900 --> 00:08:03.810 align:start position:0% community and you know basically we provide<00:08:02.080> an<00:08:02.380> interface<00:08:02.620> for<00:08:03.220> allowing<00:08:03.699> people 00:08:03.810 --> 00:08:03.820 align:start position:0% provide an interface for allowing people 00:08:03.820 --> 00:08:06.480 align:start position:0% provide an interface for allowing people to<00:08:04.000> do<00:08:04.330> you<00:08:04.630> Bay<00:08:04.780> style<00:08:05.050> auctions<00:08:05.650> for<00:08:05.919> these 00:08:06.480 --> 00:08:06.490 align:start position:0% to do you Bay style auctions for these 00:08:06.490 --> 00:08:13.500 align:start position:0% to do you Bay style auctions for these items<00:08:09.150> so<00:08:10.150> if<00:08:11.020> if<00:08:11.560> you<00:08:11.770> were<00:08:11.889> to<00:08:12.190> build<00:08:13.180> your 00:08:13.500 --> 00:08:13.510 align:start position:0% items so if if you were to build your 00:08:13.510 --> 00:08:16.200 align:start position:0% items so if if you were to build your own<00:08:13.570> marketplace<00:08:14.110> on<00:08:14.440> open<00:08:14.800> sea<00:08:15.210> essentially 00:08:16.200 --> 00:08:16.210 align:start position:0% own marketplace on open sea essentially 00:08:16.210 --> 00:08:17.939 align:start position:0% own marketplace on open sea essentially what<00:08:16.360> you<00:08:16.479> get<00:08:16.630> out<00:08:16.870> of<00:08:16.900> the<00:08:17.080> box<00:08:17.260> is<00:08:17.560> all<00:08:17.800> of 00:08:17.939 --> 00:08:17.949 align:start position:0% what you get out of the box is all of 00:08:17.949 --> 00:08:19.680 align:start position:0% what you get out of the box is all of the<00:08:18.040> functionality<00:08:18.430> that's<00:08:18.820> built<00:08:18.940> into<00:08:19.330> the 00:08:19.680 --> 00:08:19.690 align:start position:0% the functionality that's built into the 00:08:19.690 --> 00:08:22.110 align:start position:0% the functionality that's built into the ONC<00:08:19.960> website<00:08:20.470> every<00:08:21.400> single<00:08:21.729> open<00:08:21.970> sea 00:08:22.110 --> 00:08:22.120 align:start position:0% ONC website every single open sea 00:08:22.120 --> 00:08:25.620 align:start position:0% ONC website every single open sea feature<00:08:22.360> and<00:08:23.260> you<00:08:23.710> can<00:08:23.860> customize<00:08:24.340> it<00:08:24.580> and<00:08:25.389> I 00:08:25.620 --> 00:08:25.630 align:start position:0% feature and you can customize it and I 00:08:25.630 --> 00:08:28.700 align:start position:0% feature and you can customize it and I shall<00:08:26.050> talk<00:08:26.229> about<00:08:26.290> some<00:08:26.800> of<00:08:26.889> these<00:08:26.950> over<00:08:27.100> here 00:08:28.700 --> 00:08:28.710 align:start position:0% shall talk about some of these over here 00:08:28.710 --> 00:08:31.590 align:start position:0% shall talk about some of these over here so<00:08:29.710> this<00:08:29.800> is<00:08:29.860> what<00:08:30.580> it<00:08:30.669> looks<00:08:30.850> like<00:08:30.910> for<00:08:31.270> this 00:08:31.590 --> 00:08:31.600 align:start position:0% so this is what it looks like for this 00:08:31.600 --> 00:08:34.290 align:start position:0% so this is what it looks like for this game<00:08:31.900> from<00:08:32.560> two<00:08:32.710> space<00:08:32.919> commanders<00:08:33.400> you<00:08:34.029> have 00:08:34.290 --> 00:08:34.300 align:start position:0% game from two space commanders you have 00:08:34.300 --> 00:08:37.469 align:start position:0% game from two space commanders you have this<00:08:34.479> browser<00:08:34.779> view<00:08:35.469> of<00:08:35.890> your<00:08:36.190> items<00:08:36.520> you<00:08:37.029> can 00:08:37.469 --> 00:08:37.479 align:start position:0% this browser view of your items you can 00:08:37.479 --> 00:08:40.370 align:start position:0% this browser view of your items you can add<00:08:37.510> rich<00:08:38.110> metadata<00:08:38.650> to<00:08:38.979> them<00:08:39.159> to<00:08:39.729> kind<00:08:39.940> of 00:08:40.370 --> 00:08:40.380 align:start position:0% add rich metadata to them to kind of 00:08:40.380 --> 00:08:42.750 align:start position:0% add rich metadata to them to kind of control<00:08:41.380> how<00:08:41.680> they're<00:08:41.919> displayed<00:08:42.190> on<00:08:42.669> the 00:08:42.750 --> 00:08:42.760 align:start position:0% control how they're displayed on the 00:08:42.760 --> 00:08:46.800 align:start position:0% control how they're displayed on the marketplace<00:08:44.520> and<00:08:45.520> then<00:08:45.670> the<00:08:46.180> most<00:08:46.390> important 00:08:46.800 --> 00:08:46.810 align:start position:0% marketplace and then the most important 00:08:46.810 --> 00:08:49.920 align:start position:0% marketplace and then the most important element<00:08:47.740> of<00:08:47.830> this<00:08:47.890> model<00:08:48.370> is<00:08:48.580> that<00:08:48.630> we<00:08:49.630> allow 00:08:49.920 --> 00:08:49.930 align:start position:0% element of this model is that we allow 00:08:49.930 --> 00:08:53.190 align:start position:0% element of this model is that we allow the<00:08:49.990> developer<00:08:50.980> of<00:08:51.010> nmt<00:08:51.700> to<00:08:52.180> take<00:08:52.510> a<00:08:52.540> cut<00:08:52.930> of 00:08:53.190 --> 00:08:53.200 align:start position:0% the developer of nmt to take a cut of 00:08:53.200 --> 00:08:55.019 align:start position:0% the developer of nmt to take a cut of every<00:08:53.470> secondary<00:08:53.890> sale<00:08:54.279> on<00:08:54.730> their 00:08:55.019 --> 00:08:55.029 align:start position:0% every secondary sale on their 00:08:55.029 --> 00:08:57.720 align:start position:0% every secondary sale on their marketplace<00:08:55.390> so<00:08:56.140> our<00:08:56.770> model<00:08:57.160> right<00:08:57.190> now<00:08:57.430> is 00:08:57.720 --> 00:08:57.730 align:start position:0% marketplace so our model right now is 00:08:57.730 --> 00:08:59.250 align:start position:0% marketplace so our model right now is transaction<00:08:58.420> fee<00:08:58.540> based<00:08:58.750> that<00:08:58.930> might<00:08:59.080> change 00:08:59.250 --> 00:08:59.260 align:start position:0% transaction fee based that might change 00:08:59.260 --> 00:09:01.199 align:start position:0% transaction fee based that might change in<00:08:59.440> the<00:08:59.470> future<00:08:59.529> but<00:09:00.010> we<00:09:00.580> think<00:09:00.730> that<00:09:00.970> there 00:09:01.199 --> 00:09:01.209 align:start position:0% in the future but we think that there 00:09:01.209 --> 00:09:03.420 align:start position:0% in the future but we think that there should<00:09:01.240> be<00:09:01.390> an<00:09:01.570> incentive<00:09:01.839> for<00:09:02.400> developers<00:09:03.400> to 00:09:03.420 --> 00:09:03.430 align:start position:0% should be an incentive for developers to 00:09:03.430 --> 00:09:08.670 align:start position:0% should be an incentive for developers to promote<00:09:04.330> their<00:09:04.630> marketplace<00:09:07.560> we<00:09:08.560> also 00:09:08.670 --> 00:09:08.680 align:start position:0% promote their marketplace we also 00:09:08.680 --> 00:09:12.300 align:start position:0% promote their marketplace we also provide<00:09:09.190> a<00:09:09.550> tool<00:09:10.540> kit<00:09:10.779> for<00:09:10.839> which<00:09:11.770> we'll<00:09:11.950> talk 00:09:12.300 --> 00:09:12.310 align:start position:0% provide a tool kit for which we'll talk 00:09:12.310 --> 00:09:14.820 align:start position:0% provide a tool kit for which we'll talk a<00:09:12.339> little<00:09:12.490> bit<00:09:12.730> about<00:09:12.910> and<00:09:13.779> workshop<00:09:14.200> piece 00:09:14.820 --> 00:09:14.830 align:start position:0% a little bit about and workshop piece 00:09:14.830 --> 00:09:17.430 align:start position:0% a little bit about and workshop piece for<00:09:15.870> programmatically<00:09:16.870> creating 00:09:17.430 --> 00:09:17.440 align:start position:0% for programmatically creating 00:09:17.440 --> 00:09:19.920 align:start position:0% for programmatically creating marketplaces<00:09:18.160> so<00:09:18.940> this<00:09:19.089> is<00:09:19.240> a<00:09:19.270> marketplace 00:09:19.920 --> 00:09:19.930 align:start position:0% marketplaces so this is a marketplace 00:09:19.930 --> 00:09:23.130 align:start position:0% marketplaces so this is a marketplace created<00:09:20.709> by<00:09:21.150> aetherium<00:09:22.209> which<00:09:22.450> is<00:09:22.600> a<00:09:22.630> trading 00:09:23.130 --> 00:09:23.140 align:start position:0% created by aetherium which is a trading 00:09:23.140 --> 00:09:26.060 align:start position:0% created by aetherium which is a trading card<00:09:23.380> game<00:09:23.670> and<00:09:24.670> you<00:09:24.790> can<00:09:24.940> see<00:09:25.120> that<00:09:25.360> the 00:09:26.060 --> 00:09:26.070 align:start position:0% card game and you can see that the 00:09:26.070 --> 00:09:28.829 align:start position:0% card game and you can see that the marketplace<00:09:27.070> that<00:09:27.190> they've<00:09:27.370> created<00:09:27.610> and<00:09:28.180> the 00:09:28.829 --> 00:09:28.839 align:start position:0% marketplace that they've created and the 00:09:28.839 --> 00:09:30.420 align:start position:0% marketplace that they've created and the open<00:09:29.230> sea<00:09:29.380> marketplace<00:09:29.860> are<00:09:30.070> actually 00:09:30.420 --> 00:09:30.430 align:start position:0% open sea marketplace are actually 00:09:30.430 --> 00:09:32.820 align:start position:0% open sea marketplace are actually synchronized<00:09:31.000> such<00:09:31.330> that<00:09:31.570> every<00:09:31.959> sale<00:09:32.260> or 00:09:32.820 --> 00:09:32.830 align:start position:0% synchronized such that every sale or 00:09:32.830 --> 00:09:34.890 align:start position:0% synchronized such that every sale or every<00:09:33.310> auction<00:09:33.850> that<00:09:34.360> happens<00:09:34.690> on<00:09:34.779> their 00:09:34.890 --> 00:09:34.900 align:start position:0% every auction that happens on their 00:09:34.900 --> 00:09:37.290 align:start position:0% every auction that happens on their marketplace<00:09:35.200> also<00:09:36.089> happens 00:09:37.290 --> 00:09:37.300 align:start position:0% marketplace also happens 00:09:37.300 --> 00:09:40.080 align:start position:0% marketplace also happens see<00:09:37.600> it<00:09:37.720> shares<00:09:38.020> the<00:09:38.140> same<00:09:38.610> contracts<00:09:39.610> and<00:09:39.790> the 00:09:40.080 --> 00:09:40.090 align:start position:0% see it shares the same contracts and the 00:09:40.090 --> 00:09:46.320 align:start position:0% see it shares the same contracts and the same<00:09:40.300> order<00:09:40.630> books<00:09:43.230> so<00:09:44.230> a<00:09:44.260> couple<00:09:44.740> examples<00:09:45.580> of 00:09:46.320 --> 00:09:46.330 align:start position:0% same order books so a couple examples of 00:09:46.330 --> 00:09:48.120 align:start position:0% same order books so a couple examples of interesting<00:09:46.840> and<00:09:47.050> IT<00:09:47.290> projects<00:09:47.740> to<00:09:47.890> kind<00:09:48.010> of 00:09:48.120 --> 00:09:48.130 align:start position:0% interesting and IT projects to kind of 00:09:48.130 --> 00:09:51.950 align:start position:0% interesting and IT projects to kind of make<00:09:48.340> some<00:09:49.030> of<00:09:49.150> this<00:09:49.270> a<00:09:49.330> little<00:09:49.540> more<00:09:49.810> concrete 00:09:51.950 --> 00:09:51.960 align:start position:0% make some of this a little more concrete 00:09:51.960 --> 00:09:54.750 align:start position:0% make some of this a little more concrete so<00:09:52.960> this<00:09:53.290> is<00:09:53.410> the<00:09:53.530> project<00:09:53.740> called<00:09:54.190> crypto 00:09:54.750 --> 00:09:54.760 align:start position:0% so this is the project called crypto 00:09:54.760 --> 00:09:56.550 align:start position:0% so this is the project called crypto voxels<00:09:55.150> who<00:09:55.750> here<00:09:55.930> has<00:09:56.020> heard<00:09:56.140> of<00:09:56.260> crypto 00:09:56.550 --> 00:09:56.560 align:start position:0% voxels who here has heard of crypto 00:09:56.560 --> 00:09:59.610 align:start position:0% voxels who here has heard of crypto voxels<00:09:57.060> okay<00:09:58.060> so<00:09:58.120> not<00:09:58.390> not<00:09:58.750> that<00:09:59.110> many<00:09:59.290> people 00:09:59.610 --> 00:09:59.620 align:start position:0% voxels okay so not not that many people 00:09:59.620 --> 00:10:03.810 align:start position:0% voxels okay so not not that many people and<00:10:00.610> so<00:10:00.850> crypto<00:10:01.300> voxels<00:10:01.780> is<00:10:02.080> a<00:10:02.590> virtual<00:10:03.280> world 00:10:03.810 --> 00:10:03.820 align:start position:0% and so crypto voxels is a virtual world 00:10:03.820 --> 00:10:07.890 align:start position:0% and so crypto voxels is a virtual world where<00:10:04.750> the<00:10:05.140> land<00:10:05.590> is<00:10:06.130> represented<00:10:07.000> as<00:10:07.240> GRC 00:10:07.890 --> 00:10:07.900 align:start position:0% where the land is represented as GRC 00:10:07.900 --> 00:10:11.220 align:start position:0% where the land is represented as GRC 7:21<00:10:08.620> and<00:10:08.980> of<00:10:09.070> TS<00:10:09.340> and<00:10:09.750> it<00:10:10.750> actually<00:10:11.110> just 00:10:11.220 --> 00:10:11.230 align:start position:0% 7:21 and of TS and it actually just 00:10:11.230 --> 00:10:14.610 align:start position:0% 7:21 and of TS and it actually just started<00:10:11.590> as<00:10:11.740> one<00:10:11.950> developer<00:10:12.550> and<00:10:12.790> he<00:10:13.720> just 00:10:14.610 --> 00:10:14.620 align:start position:0% started as one developer and he just 00:10:14.620 --> 00:10:16.230 align:start position:0% started as one developer and he just started<00:10:14.950> selling<00:10:15.190> this<00:10:15.460> virtual<00:10:15.820> land<00:10:16.030> and<00:10:16.180> he 00:10:16.230 --> 00:10:16.240 align:start position:0% started selling this virtual land and he 00:10:16.240 --> 00:10:19.110 align:start position:0% started selling this virtual land and he sold<00:10:16.420> it<00:10:16.540> at<00:10:16.660> a<00:10:16.690> pretty<00:10:16.930> low<00:10:16.990> price<00:10:17.430> and<00:10:18.430> when 00:10:19.110 --> 00:10:19.120 align:start position:0% sold it at a pretty low price and when 00:10:19.120 --> 00:10:20.400 align:start position:0% sold it at a pretty low price and when you<00:10:19.240> own<00:10:19.390> this<00:10:19.570> land<00:10:19.750> is<00:10:20.020> kind<00:10:20.230> of<00:10:20.260> like 00:10:20.400 --> 00:10:20.410 align:start position:0% you own this land is kind of like 00:10:20.410 --> 00:10:22.200 align:start position:0% you own this land is kind of like minecraft<00:10:20.920> you<00:10:21.160> could<00:10:21.310> build<00:10:21.520> things<00:10:21.760> on<00:10:22.030> top 00:10:22.200 --> 00:10:22.210 align:start position:0% minecraft you could build things on top 00:10:22.210 --> 00:10:26.100 align:start position:0% minecraft you could build things on top of<00:10:22.390> it<00:10:22.510> so<00:10:23.820> here<00:10:24.820> the<00:10:25.540> other<00:10:25.690> interesting 00:10:26.100 --> 00:10:26.110 align:start position:0% of it so here the other interesting 00:10:26.110 --> 00:10:27.870 align:start position:0% of it so here the other interesting thing<00:10:26.380> the<00:10:26.710> developer<00:10:27.100> did<00:10:27.280> was<00:10:27.430> he<00:10:27.640> allowed 00:10:27.870 --> 00:10:27.880 align:start position:0% thing the developer did was he allowed 00:10:27.880 --> 00:10:30.570 align:start position:0% thing the developer did was he allowed you<00:10:28.120> to<00:10:28.180> pull<00:10:28.480> in<00:10:28.780> your<00:10:29.050> assets<00:10:29.740> into<00:10:30.160> this 00:10:30.570 --> 00:10:30.580 align:start position:0% you to pull in your assets into this 00:10:30.580 --> 00:10:33.810 align:start position:0% you to pull in your assets into this virtual<00:10:31.000> world<00:10:31.150> so<00:10:31.920> this<00:10:32.920> is<00:10:33.130> a<00:10:33.160> crypto 00:10:33.810 --> 00:10:33.820 align:start position:0% virtual world so this is a crypto 00:10:33.820 --> 00:10:36.420 align:start position:0% virtual world so this is a crypto Kitty's<00:10:34.150> museum<00:10:34.900> inside<00:10:35.470> of<00:10:35.680> Krypton<00:10:36.040> voxels 00:10:36.420 --> 00:10:36.430 align:start position:0% Kitty's museum inside of Krypton voxels 00:10:36.430 --> 00:10:38.370 align:start position:0% Kitty's museum inside of Krypton voxels where<00:10:37.210> you<00:10:37.300> can<00:10:37.450> actually<00:10:37.570> go<00:10:37.930> and<00:10:38.170> and 00:10:38.370 --> 00:10:38.380 align:start position:0% where you can actually go and and 00:10:38.380 --> 00:10:40.350 align:start position:0% where you can actually go and and purchase<00:10:39.010> these<00:10:39.190> crypto<00:10:39.520> kitties<00:10:39.790> inside<00:10:40.210> of 00:10:40.350 --> 00:10:40.360 align:start position:0% purchase these crypto kitties inside of 00:10:40.360 --> 00:10:43.880 align:start position:0% purchase these crypto kitties inside of the<00:10:40.420> virtual<00:10:40.570> world<00:10:41.580> it's<00:10:42.580> all<00:10:42.700> do<00:10:42.820> a<00:10:42.850> quick 00:10:43.880 --> 00:10:43.890 align:start position:0% the virtual world it's all do a quick 00:10:43.890 --> 00:10:52.230 align:start position:0% the virtual world it's all do a quick demo 00:10:52.230 --> 00:10:52.240 align:start position:0% 00:10:52.240 --> 00:10:56.110 align:start position:0% so<00:10:53.590> one<00:10:54.590> one<00:10:55.190> interesting<00:10:55.580> that<00:10:55.730> thing<00:10:56.000> that 00:10:56.110 --> 00:10:56.120 align:start position:0% so one one interesting that thing that 00:10:56.120 --> 00:10:59.260 align:start position:0% so one one interesting that thing that this<00:10:56.240> happened<00:10:56.630> is<00:10:56.870> there<00:10:57.710> are<00:10:58.130> now<00:10:58.400> folks<00:10:58.850> who 00:10:59.260 --> 00:10:59.270 align:start position:0% this happened is there are now folks who 00:10:59.270 --> 00:11:04.650 align:start position:0% this happened is there are now folks who are<00:10:59.830> curators<00:11:00.830> of<00:11:01.600> digital<00:11:02.600> collectibles<00:11:03.140> and 00:11:04.650 --> 00:11:04.660 align:start position:0% are curators of digital collectibles and 00:11:04.660 --> 00:11:10.240 align:start position:0% are curators of digital collectibles and they<00:11:05.660> have<00:11:05.900> started<00:11:07.870> creating<00:11:08.890> galleries<00:11:09.890> and 00:11:10.240 --> 00:11:10.250 align:start position:0% they have started creating galleries and 00:11:10.250 --> 00:11:13.510 align:start position:0% they have started creating galleries and crypto<00:11:10.580> voxels<00:11:11.030> to<00:11:11.390> explore<00:11:11.960> these<00:11:12.520> these 00:11:13.510 --> 00:11:13.520 align:start position:0% crypto voxels to explore these these 00:11:13.520 --> 00:11:16.080 align:start position:0% crypto voxels to explore these these artworks<00:11:13.850> so<00:11:14.180> this<00:11:14.300> is<00:11:14.450> a<00:11:14.480> gallery<00:11:15.140> from 00:11:16.080 --> 00:11:16.090 align:start position:0% artworks so this is a gallery from 00:11:16.090 --> 00:11:18.760 align:start position:0% artworks so this is a gallery from someone<00:11:17.090> you<00:11:17.720> know<00:11:17.810> who<00:11:17.990> basically<00:11:18.410> thinks<00:11:18.650> of 00:11:18.760 --> 00:11:18.770 align:start position:0% someone you know who basically thinks of 00:11:18.770 --> 00:11:22.330 align:start position:0% someone you know who basically thinks of themselves<00:11:18.920> as<00:11:19.490> a<00:11:19.850> digital<00:11:20.570> art<00:11:20.750> curator<00:11:21.340> and 00:11:22.330 --> 00:11:22.340 align:start position:0% themselves as a digital art curator and 00:11:22.340 --> 00:11:33.800 align:start position:0% themselves as a digital art curator and it's<00:11:22.490> sort<00:11:22.760> of<00:11:22.820> created<00:11:23.180> this<00:11:23.330> as<00:11:23.810> Museum 00:11:33.800 --> 00:11:33.810 align:start position:0% 00:11:33.810 --> 00:11:36.550 align:start position:0% another<00:11:34.410> interesting<00:11:34.740> NFT<00:11:35.490> project<00:11:35.970> was 00:11:36.550 --> 00:11:36.560 align:start position:0% another interesting NFT project was 00:11:36.560 --> 00:11:41.450 align:start position:0% another interesting NFT project was crypto<00:11:37.560> stamp<00:11:37.890> so<00:11:38.550> crypto<00:11:39.330> stamp<00:11:39.660> is<00:11:40.460> an 00:11:41.450 --> 00:11:41.460 align:start position:0% crypto stamp so crypto stamp is an 00:11:41.460 --> 00:11:43.820 align:start position:0% crypto stamp so crypto stamp is an interesting<00:11:41.730> one<00:11:42.090> because<00:11:42.360> it<00:11:43.230> was<00:11:43.410> actually 00:11:43.820 --> 00:11:43.830 align:start position:0% interesting one because it was actually 00:11:43.830 --> 00:11:47.300 align:start position:0% interesting one because it was actually coupled<00:11:44.400> to<00:11:44.700> a<00:11:44.730> physical<00:11:45.630> stamp<00:11:46.620> so<00:11:47.160> the 00:11:47.300 --> 00:11:47.310 align:start position:0% coupled to a physical stamp so the 00:11:47.310 --> 00:11:50.150 align:start position:0% coupled to a physical stamp so the Austrian<00:11:47.850> Postal<00:11:48.450> Service<00:11:49.160> basically 00:11:50.150 --> 00:11:50.160 align:start position:0% Austrian Postal Service basically 00:11:50.160 --> 00:11:52.370 align:start position:0% Austrian Postal Service basically created<00:11:50.520> this<00:11:50.640> line<00:11:51.150> of<00:11:51.510> collectible<00:11:51.960> stamps 00:11:52.370 --> 00:11:52.380 align:start position:0% created this line of collectible stamps 00:11:52.380 --> 00:11:55.160 align:start position:0% created this line of collectible stamps where<00:11:52.950> if<00:11:53.340> you<00:11:53.580> purchase<00:11:54.060> one<00:11:54.270> you<00:11:54.900> would<00:11:55.020> not 00:11:55.160 --> 00:11:55.170 align:start position:0% where if you purchase one you would not 00:11:55.170 --> 00:11:59.150 align:start position:0% where if you purchase one you would not only<00:11:55.350> get<00:11:55.620> a<00:11:55.950> real<00:11:56.520> useable<00:11:57.510> stamp<00:11:58.140> a<00:11:58.650> lot<00:11:59.070> of 00:11:59.150 --> 00:11:59.160 align:start position:0% only get a real useable stamp a lot of 00:11:59.160 --> 00:12:00.200 align:start position:0% only get a real useable stamp a lot of people<00:11:59.340> probably<00:11:59.460> don't<00:11:59.730> use<00:11:59.880> those<00:12:00.090> these 00:12:00.200 --> 00:12:00.210 align:start position:0% people probably don't use those these 00:12:00.210 --> 00:12:02.420 align:start position:0% people probably don't use those these days<00:12:00.390> but<00:12:00.660> you<00:12:00.960> would<00:12:01.350> get<00:12:01.470> a<00:12:01.500> Sam<00:12:01.770> and<00:12:02.070> then 00:12:02.420 --> 00:12:02.430 align:start position:0% days but you would get a Sam and then 00:12:02.430 --> 00:12:05.300 align:start position:0% days but you would get a Sam and then you'd<00:12:02.580> also<00:12:02.670> get<00:12:03.480> a<00:12:03.780> crypto<00:12:04.470> collectible<00:12:05.070> that 00:12:05.300 --> 00:12:05.310 align:start position:0% you'd also get a crypto collectible that 00:12:05.310 --> 00:12:07.580 align:start position:0% you'd also get a crypto collectible that you<00:12:05.460> could<00:12:05.700> trade<00:12:06.120> on<00:12:06.720> an<00:12:07.080> open<00:12:07.320> marketplace 00:12:07.580 --> 00:12:07.590 align:start position:0% you could trade on an open marketplace 00:12:07.590 --> 00:12:10.160 align:start position:0% you could trade on an open marketplace and<00:12:08.370> this<00:12:08.550> was<00:12:08.730> kind<00:12:08.910> of<00:12:08.940> an<00:12:09.090> interesting<00:12:09.180> way 00:12:10.160 --> 00:12:10.170 align:start position:0% and this was kind of an interesting way 00:12:10.170 --> 00:12:13.250 align:start position:0% and this was kind of an interesting way to<00:12:10.200> engage<00:12:10.770> an<00:12:11.130> existing<00:12:11.670> community<00:12:12.240> of<00:12:12.570> stamp 00:12:13.250 --> 00:12:13.260 align:start position:0% to engage an existing community of stamp 00:12:13.260 --> 00:12:16.490 align:start position:0% to engage an existing community of stamp collectors<00:12:13.770> in<00:12:14.100> digital<00:12:15.060> assets<00:12:15.720> and<00:12:16.410> we 00:12:16.490 --> 00:12:16.500 align:start position:0% collectors in digital assets and we 00:12:16.500 --> 00:12:18.290 align:start position:0% collectors in digital assets and we think<00:12:16.710> we'll<00:12:16.830> see<00:12:17.010> a<00:12:17.040> lot<00:12:17.130> of<00:12:17.340> that<00:12:17.730> kind<00:12:18.270> of 00:12:18.290 --> 00:12:18.300 align:start position:0% think we'll see a lot of that kind of 00:12:18.300 --> 00:12:23.120 align:start position:0% think we'll see a lot of that kind of tethering<00:12:19.700> these<00:12:21.350> virtual<00:12:22.350> assets<00:12:22.530> to<00:12:23.100> a 00:12:23.120 --> 00:12:23.130 align:start position:0% tethering these virtual assets to a 00:12:23.130 --> 00:12:29.180 align:start position:0% tethering these virtual assets to a real-life<00:12:23.580> physical<00:12:24.300> asset<00:12:27.680> and<00:12:28.680> then<00:12:28.860> of 00:12:29.180 --> 00:12:29.190 align:start position:0% real-life physical asset and then of 00:12:29.190 --> 00:12:33.410 align:start position:0% real-life physical asset and then of course<00:12:30.110> the<00:12:31.110> most<00:12:31.320> recent<00:12:31.680> one<00:12:31.830> is<00:12:32.220> the<00:12:32.640> ENS 00:12:33.410 --> 00:12:33.420 align:start position:0% course the most recent one is the ENS 00:12:33.420 --> 00:12:37.490 align:start position:0% course the most recent one is the ENS project<00:12:34.380> so<00:12:34.680> ENS<00:12:35.550> is<00:12:35.910> a<00:12:36.270> name<00:12:36.750> system<00:12:37.260> for 00:12:37.490 --> 00:12:37.500 align:start position:0% project so ENS is a name system for 00:12:37.500 --> 00:12:39.020 align:start position:0% project so ENS is a name system for Imperium<00:12:37.920> so<00:12:38.160> you<00:12:38.250> can<00:12:38.430> think<00:12:38.610> of<00:12:38.670> it<00:12:38.820> kind<00:12:38.850> of 00:12:39.020 --> 00:12:39.030 align:start position:0% Imperium so you can think of it kind of 00:12:39.030 --> 00:12:43.970 align:start position:0% Imperium so you can think of it kind of like<00:12:39.090> comms<00:12:39.900> and<00:12:41.780> right<00:12:42.780> now<00:12:42.990> these<00:12:43.440> assets 00:12:43.970 --> 00:12:43.980 align:start position:0% like comms and right now these assets 00:12:43.980 --> 00:12:46.940 align:start position:0% like comms and right now these assets are<00:12:44.190> tradable<00:12:44.910> as<00:12:45.120> er<00:12:45.510> c720<00:12:46.020> ones<00:12:46.320> most 00:12:46.940 --> 00:12:46.950 align:start position:0% are tradable as er c720 ones most 00:12:46.950 --> 00:12:49.460 align:start position:0% are tradable as er c720 ones most recently<00:12:47.430> we<00:12:47.840> collaborated<00:12:48.840> with<00:12:48.870> the<00:12:49.140> ENS 00:12:49.460 --> 00:12:49.470 align:start position:0% recently we collaborated with the ENS 00:12:49.470 --> 00:12:52.310 align:start position:0% recently we collaborated with the ENS team<00:12:49.800> on<00:12:50.190> doing<00:12:51.030> the<00:12:51.180> auctions<00:12:51.690> for<00:12:51.870> their 00:12:52.310 --> 00:12:52.320 align:start position:0% team on doing the auctions for their 00:12:52.320 --> 00:12:55.670 align:start position:0% team on doing the auctions for their short<00:12:52.680> name<00:12:52.890> and<00:12:53.930> so<00:12:54.930> these<00:12:55.140> were<00:12:55.320> basically 00:12:55.670 --> 00:12:55.680 align:start position:0% short name and so these were basically 00:12:55.680 --> 00:12:59.570 align:start position:0% short name and so these were basically names<00:12:55.980> like<00:12:56.340> set<00:12:57.090> eath<00:12:57.600> that<00:12:58.260> were<00:12:59.100> reserved 00:12:59.570 --> 00:12:59.580 align:start position:0% names like set eath that were reserved 00:12:59.580 --> 00:13:03.980 align:start position:0% names like set eath that were reserved for<00:13:00.320> an<00:13:01.320> auction<00:13:01.800> system<00:13:02.570> that'll<00:13:03.570> that<00:13:03.870> is 00:13:03.980 --> 00:13:03.990 align:start position:0% for an auction system that'll that is 00:13:03.990 --> 00:13:05.390 align:start position:0% for an auction system that'll that is actually<00:13:04.350> currently<00:13:04.800> taking<00:13:05.160> place<00:13:05.370> right 00:13:05.390 --> 00:13:05.400 align:start position:0% actually currently taking place right 00:13:05.400 --> 00:13:08.140 align:start position:0% actually currently taking place right now 00:13:08.140 --> 00:13:08.150 align:start position:0% 00:13:08.150 --> 00:13:12.160 align:start position:0% all<00:13:09.050> right<00:13:09.170> so<00:13:09.380> I<00:13:09.680> guess<00:13:09.890> any<00:13:10.339> questions<00:13:11.170> about 00:13:12.160 --> 00:13:12.170 align:start position:0% all right so I guess any questions about 00:13:12.170 --> 00:13:15.910 align:start position:0% all right so I guess any questions about NF<00:13:12.860> TS<00:13:13.100> or<00:13:13.400> years<00:13:13.610> so<00:13:13.730> 721<00:13:14.350> before<00:13:15.350> I<00:13:15.380> hop<00:13:15.680> into 00:13:15.910 --> 00:13:15.920 align:start position:0% NF TS or years so 721 before I hop into 00:13:15.920 --> 00:13:34.750 align:start position:0% NF TS or years so 721 before I hop into the<00:13:16.600> workshop<00:13:24.460> NFC<00:13:25.460> NYC<00:13:31.600> yep<00:13:33.640> what's<00:13:34.640> the 00:13:34.750 --> 00:13:34.760 align:start position:0% the workshop NFC NYC yep what's the 00:13:34.760 --> 00:13:40.990 align:start position:0% the workshop NFC NYC yep what's the growth<00:13:35.140> you've<00:13:36.140> seen<00:13:36.410> yeah<00:13:37.300> so<00:13:39.490> the<00:13:40.490> initial 00:13:40.990 --> 00:13:41.000 align:start position:0% growth you've seen yeah so the initial 00:13:41.000 --> 00:13:43.120 align:start position:0% growth you've seen yeah so the initial spike<00:13:41.690> and<00:13:42.080> usage<00:13:42.410> of<00:13:42.529> entities<00:13:42.920> of<00:13:43.040> those 00:13:43.120 --> 00:13:43.130 align:start position:0% spike and usage of entities of those 00:13:43.130 --> 00:13:45.700 align:start position:0% spike and usage of entities of those crypto<00:13:43.400> kiddies<00:13:43.670> and<00:13:44.089> you<00:13:44.870> know<00:13:44.960> you<00:13:45.350> probably 00:13:45.700 --> 00:13:45.710 align:start position:0% crypto kiddies and you know you probably 00:13:45.710 --> 00:13:48.070 align:start position:0% crypto kiddies and you know you probably remember<00:13:45.920> these<00:13:46.880> cats<00:13:47.510> selling<00:13:47.870> for<00:13:48.020> like 00:13:48.070 --> 00:13:48.080 align:start position:0% remember these cats selling for like 00:13:48.080 --> 00:13:50.590 align:start position:0% remember these cats selling for like fifty<00:13:48.380> thousand<00:13:48.680> dollars<00:13:48.920> each<00:13:49.120> and<00:13:50.120> nothing 00:13:50.590 --> 00:13:50.600 align:start position:0% fifty thousand dollars each and nothing 00:13:50.600 --> 00:13:54.240 align:start position:0% fifty thousand dollars each and nothing has<00:13:50.830> you<00:13:51.830> know<00:13:51.920> risen<00:13:52.550> to<00:13:52.760> that<00:13:52.790> level<00:13:53.240> of 00:13:54.240 --> 00:13:54.250 align:start position:0% has you know risen to that level of 00:13:54.250 --> 00:13:57.040 align:start position:0% has you know risen to that level of market<00:13:55.250> volume<00:13:55.580> but<00:13:55.970> I<00:13:56.000> think<00:13:56.240> that<00:13:56.360> was<00:13:56.510> you 00:13:57.040 --> 00:13:57.050 align:start position:0% market volume but I think that was you 00:13:57.050 --> 00:13:59.530 align:start position:0% market volume but I think that was you know<00:13:57.110> some<00:13:57.350> extent<00:13:57.620> anomaly<00:13:58.130> in<00:13:59.089> terms<00:13:59.360> of 00:13:59.530 --> 00:13:59.540 align:start position:0% know some extent anomaly in terms of 00:13:59.540 --> 00:14:02.980 align:start position:0% know some extent anomaly in terms of market<00:14:00.200> volume<00:14:00.470> growth<00:14:01.100> it's<00:14:01.820> sort<00:14:02.570> of<00:14:02.630> slow 00:14:02.980 --> 00:14:02.990 align:start position:0% market volume growth it's sort of slow 00:14:02.990 --> 00:14:05.050 align:start position:0% market volume growth it's sort of slow but<00:14:03.200> steady<00:14:03.380> linear<00:14:03.890> growth<00:14:04.250> at<00:14:04.610> the<00:14:04.670> moment 00:14:05.050 --> 00:14:05.060 align:start position:0% but steady linear growth at the moment 00:14:05.060 --> 00:14:07.870 align:start position:0% but steady linear growth at the moment so<00:14:05.270> we're<00:14:05.480> seeing<00:14:05.860> we're<00:14:06.860> seeing<00:14:06.890> high<00:14:07.520> growth 00:14:07.870 --> 00:14:07.880 align:start position:0% so we're seeing we're seeing high growth 00:14:07.880 --> 00:14:09.940 align:start position:0% so we're seeing we're seeing high growth in<00:14:08.120> the<00:14:08.240> number<00:14:08.570> of<00:14:08.690> projects<00:14:09.140> that<00:14:09.650> enter<00:14:09.860> the 00:14:09.940 --> 00:14:09.950 align:start position:0% in the number of projects that enter the 00:14:09.950 --> 00:14:13.000 align:start position:0% in the number of projects that enter the space<00:14:10.190> we're<00:14:10.940> seeing<00:14:11.180> sort<00:14:11.870> of<00:14:12.050> gradual 00:14:13.000 --> 00:14:13.010 align:start position:0% space we're seeing sort of gradual 00:14:13.010 --> 00:14:14.800 align:start position:0% space we're seeing sort of gradual growth<00:14:13.279> in<00:14:13.580> the<00:14:13.640> number<00:14:13.910> of<00:14:13.940> users<00:14:14.300> that<00:14:14.510> are 00:14:14.800 --> 00:14:14.810 align:start position:0% growth in the number of users that are 00:14:14.810 --> 00:14:16.240 align:start position:0% growth in the number of users that are trying<00:14:14.990> them<00:14:15.170> out<00:14:15.260> it's<00:14:15.560> a<00:14:15.650> lot<00:14:15.740> of<00:14:15.800> the<00:14:16.010> same 00:14:16.240 --> 00:14:16.250 align:start position:0% trying them out it's a lot of the same 00:14:16.250 --> 00:14:19.780 align:start position:0% trying them out it's a lot of the same early<00:14:17.120> adopter<00:14:17.570> tech<00:14:17.810> coders<00:14:18.250> who<00:14:19.250> are<00:14:19.370> like 00:14:19.780 --> 00:14:19.790 align:start position:0% early adopter tech coders who are like 00:14:19.790 --> 00:14:21.580 align:start position:0% early adopter tech coders who are like trying<00:14:20.120> these<00:14:20.240> out<00:14:20.420> and<00:14:20.690> you<00:14:21.260> know<00:14:21.350> it's<00:14:21.500> a 00:14:21.580 --> 00:14:21.590 align:start position:0% trying these out and you know it's a 00:14:21.590 --> 00:14:23.200 align:start position:0% trying these out and you know it's a variety<00:14:21.740> of<00:14:22.040> reasons<00:14:22.520> that's<00:14:22.730> the<00:14:22.850> case<00:14:23.000> the 00:14:23.200 --> 00:14:23.210 align:start position:0% variety of reasons that's the case the 00:14:23.210 --> 00:14:25.450 align:start position:0% variety of reasons that's the case the usability<00:14:24.010> scalability<00:14:25.010> of<00:14:25.190> this 00:14:25.450 --> 00:14:25.460 align:start position:0% usability scalability of this 00:14:25.460 --> 00:14:27.780 align:start position:0% usability scalability of this [Music] 00:14:27.780 --> 00:14:27.790 align:start position:0% [Music] 00:14:27.790 --> 00:14:31.300 align:start position:0% [Music] that's<00:14:28.790> all<00:14:29.000> in<00:14:29.150> gaming<00:14:29.450> pretty<00:14:29.900> much<00:14:30.310> this 00:14:31.300 --> 00:14:31.310 align:start position:0% that's all in gaming pretty much this 00:14:31.310 --> 00:14:32.470 align:start position:0% that's all in gaming pretty much this tomorrow 00:14:32.470 --> 00:14:32.480 align:start position:0% tomorrow 00:14:32.480 --> 00:14:35.950 align:start position:0% tomorrow it's<00:14:32.780> that<00:14:32.990> of<00:14:33.290> the<00:14:33.590> art<00:14:33.830> and<00:14:34.100> it<00:14:35.030> it's<00:14:35.540> also 00:14:35.950 --> 00:14:35.960 align:start position:0% it's that of the art and it it's also 00:14:35.960 --> 00:14:39.690 align:start position:0% it's that of the art and it it's also interesting<00:14:37.150> but<00:14:38.150> still<00:14:38.750> pretty<00:14:39.110> small<00:14:39.200> I 00:14:39.690 --> 00:14:39.700 align:start position:0% interesting but still pretty small I 00:14:39.700 --> 00:14:42.520 align:start position:0% interesting but still pretty small I think<00:14:40.700> like<00:14:40.910> for<00:14:41.420> art<00:14:41.690> the<00:14:41.960> biggest<00:14:42.260> thing<00:14:42.440> is 00:14:42.520 --> 00:14:42.530 align:start position:0% think like for art the biggest thing is 00:14:42.530 --> 00:14:44.890 align:start position:0% think like for art the biggest thing is having<00:14:42.770> a<00:14:42.980> place<00:14:43.250> to<00:14:43.550> display<00:14:44.000> the<00:14:44.420> art<00:14:44.570> so 00:14:44.890 --> 00:14:44.900 align:start position:0% having a place to display the art so 00:14:44.900 --> 00:14:46.900 align:start position:0% having a place to display the art so projects<00:14:45.440> like<00:14:45.590> Krypton<00:14:46.370> box'll<00:14:46.670> isn't 00:14:46.900 --> 00:14:46.910 align:start position:0% projects like Krypton box'll isn't 00:14:46.910 --> 00:14:49.180 align:start position:0% projects like Krypton box'll isn't essentially<00:14:47.360> a<00:14:47.390> kind<00:14:47.660> of<00:14:47.720> add<00:14:47.930> that<00:14:48.190> utility 00:14:49.180 --> 00:14:49.190 align:start position:0% essentially a kind of add that utility 00:14:49.190 --> 00:14:50.530 align:start position:0% essentially a kind of add that utility to<00:14:49.250> art<00:14:49.520> but<00:14:49.670> there<00:14:49.760> are<00:14:49.880> there<00:14:50.330> are<00:14:50.390> a<00:14:50.480> number 00:14:50.530 --> 00:14:50.540 align:start position:0% to art but there are there are a number 00:14:50.540 --> 00:14:55.150 align:start position:0% to art but there are there are a number of<00:14:50.750> crypto<00:14:51.470> artists<00:14:52.010> who<00:14:52.600> have<00:14:53.600> sold<00:14:53.960> works<00:14:54.800> or 00:14:55.150 --> 00:14:55.160 align:start position:0% of crypto artists who have sold works or 00:14:55.160 --> 00:14:57.400 align:start position:0% of crypto artists who have sold works or you<00:14:55.460> know<00:14:55.550> five<00:14:56.000> the<00:14:56.150> tenth<00:14:56.600> because<00:14:57.290> they 00:14:57.400 --> 00:14:57.410 align:start position:0% you know five the tenth because they 00:14:57.410 --> 00:15:00.790 align:start position:0% you know five the tenth because they have<00:14:57.560> such<00:14:57.770> a<00:14:57.800> solid<00:14:58.700> reputation<00:14:59.060> in<00:14:59.570> space<00:14:59.810> so 00:15:00.790 --> 00:15:00.800 align:start position:0% have such a solid reputation in space so 00:15:00.800 --> 00:15:07.690 align:start position:0% have such a solid reputation in space so it<00:15:00.860> is<00:15:00.980> starting<00:15:01.130> to<00:15:01.310> be<00:15:01.490> interested 00:15:07.690 --> 00:15:07.700 align:start position:0% 00:15:07.700 --> 00:15:11.750 align:start position:0% yeah<00:15:08.700> so<00:15:09.060> there<00:15:09.390> was<00:15:09.630> a<00:15:09.980> standard<00:15:10.980> called<00:15:11.250> ERC 00:15:11.750 --> 00:15:11.760 align:start position:0% yeah so there was a standard called ERC 00:15:11.760 --> 00:15:15.940 align:start position:0% yeah so there was a standard called ERC 998<00:15:12.420> that<00:15:12.900> did<00:15:13.590> that<00:15:13.790> I'm<00:15:14.790> not<00:15:15.030> aware<00:15:15.360> of<00:15:15.420> any 00:15:15.940 --> 00:15:15.950 align:start position:0% 998 that did that I'm not aware of any 00:15:15.950 --> 00:15:19.880 align:start position:0% 998 that did that I'm not aware of any like<00:15:16.950> easy-to-use<00:15:17.580> tools<00:15:18.150> that<00:15:18.840> allow<00:15:19.650> you<00:15:19.710> to 00:15:19.880 --> 00:15:19.890 align:start position:0% like easy-to-use tools that allow you to 00:15:19.890 --> 00:15:22.760 align:start position:0% like easy-to-use tools that allow you to like<00:15:20.460> button<00:15:21.180> well<00:15:21.810> so<00:15:22.080> we<00:15:22.200> have<00:15:22.290> bundles 00:15:22.760 --> 00:15:22.770 align:start position:0% like button well so we have bundles 00:15:22.770 --> 00:15:24.140 align:start position:0% like button well so we have bundles which<00:15:23.130> basically<00:15:23.370> allow<00:15:23.640> you<00:15:23.700> to<00:15:23.820> sell<00:15:24.120> a 00:15:24.140 --> 00:15:24.150 align:start position:0% which basically allow you to sell a 00:15:24.150 --> 00:15:25.610 align:start position:0% which basically allow you to sell a bunch<00:15:24.600> of<00:15:24.660> entities<00:15:25.050> at<00:15:25.140> the<00:15:25.230> same<00:15:25.350> time<00:15:25.530> but 00:15:25.610 --> 00:15:25.620 align:start position:0% bunch of entities at the same time but 00:15:25.620 --> 00:15:27.230 align:start position:0% bunch of entities at the same time but that's<00:15:25.770> a<00:15:25.830> little<00:15:25.890> bit<00:15:26.100> different<00:15:26.430> I<00:15:26.580> don't 00:15:27.230 --> 00:15:27.240 align:start position:0% that's a little bit different I don't 00:15:27.240 --> 00:15:29.450 align:start position:0% that's a little bit different I don't know<00:15:27.450> of<00:15:27.690> any<00:15:27.870> websites<00:15:28.380> at<00:15:28.740> the<00:15:28.860> moment<00:15:29.250> that 00:15:29.450 --> 00:15:29.460 align:start position:0% know of any websites at the moment that 00:15:29.460 --> 00:15:31.490 align:start position:0% know of any websites at the moment that are<00:15:29.490> making<00:15:30.240> it<00:15:30.360> really<00:15:30.480> easy<00:15:30.720> to<00:15:30.840> like<00:15:31.110> impose 00:15:31.490 --> 00:15:31.500 align:start position:0% are making it really easy to like impose 00:15:31.500 --> 00:15:33.980 align:start position:0% are making it really easy to like impose and<00:15:31.800> I've<00:15:31.860> teased<00:15:32.040> together<00:15:32.990> interesting 00:15:33.980 --> 00:15:33.990 align:start position:0% and I've teased together interesting 00:15:33.990 --> 00:15:36.260 align:start position:0% and I've teased together interesting projects<00:15:34.350> yeah<00:15:34.800> what<00:15:35.640> do<00:15:35.700> you<00:15:35.790> think<00:15:35.940> mister 00:15:36.260 --> 00:15:36.270 align:start position:0% projects yeah what do you think mister 00:15:36.270 --> 00:15:39.980 align:start position:0% projects yeah what do you think mister have<00:15:36.540> wonderful<00:15:37.050> we<00:15:37.140> can<00:15:37.320> see<00:15:37.530> like<00:15:37.860> most<00:15:38.070> roll 00:15:39.980 --> 00:15:39.990 align:start position:0% have wonderful we can see like most roll 00:15:39.990 --> 00:15:50.250 align:start position:0% have wonderful we can see like most roll before<00:15:40.990> we<00:15:41.110> see<00:15:45.540> yeah<00:15:48.300> that's<00:15:49.300> like<00:15:49.510> a<00:15:49.540> common 00:15:50.250 --> 00:15:50.260 align:start position:0% before we see yeah that's like a common 00:15:50.260 --> 00:15:52.380 align:start position:0% before we see yeah that's like a common question<00:15:50.710> I<00:15:50.830> think<00:15:50.890> right<00:15:51.339> for<00:15:51.700> everyone<00:15:51.940> in 00:15:52.380 --> 00:15:52.390 align:start position:0% question I think right for everyone in 00:15:52.390 --> 00:15:54.000 align:start position:0% question I think right for everyone in there<00:15:52.690> you<00:15:52.960> know<00:15:53.080> it's<00:15:53.200> fast<00:15:53.470> it<00:15:53.740> like<00:15:53.830> nearly 00:15:54.000 --> 00:15:54.010 align:start position:0% there you know it's fast it like nearly 00:15:54.010 --> 00:15:55.590 align:start position:0% there you know it's fast it like nearly every<00:15:54.279> panel<00:15:54.580> specific<00:15:55.060> wouldn't<00:15:55.300> have<00:15:55.390> to<00:15:55.540> do 00:15:55.590 --> 00:15:55.600 align:start position:0% every panel specific wouldn't have to do 00:15:55.600 --> 00:15:55.769 align:start position:0% every panel specific wouldn't have to do that 00:15:55.769 --> 00:15:55.779 align:start position:0% that 00:15:55.779 --> 00:16:00.269 align:start position:0% that yeah<00:15:56.620> for<00:15:56.800> nf2<00:15:57.040> use<00:15:57.250> I<00:15:57.430> think<00:15:58.500> maybe<00:15:59.500> a<00:15:59.920> couple 00:16:00.269 --> 00:16:00.279 align:start position:0% yeah for nf2 use I think maybe a couple 00:16:00.279 --> 00:16:04.170 align:start position:0% yeah for nf2 use I think maybe a couple different<00:16:00.790> axes<00:16:01.270> so<00:16:01.570> one<00:16:02.380> is<00:16:02.740> quality<00:16:03.670> of<00:16:03.940> the 00:16:04.170 --> 00:16:04.180 align:start position:0% different axes so one is quality of the 00:16:04.180 --> 00:16:06.750 align:start position:0% different axes so one is quality of the games<00:16:04.420> which<00:16:04.930> is<00:16:05.110> steadily<00:16:05.470> growing<00:16:06.010> but<00:16:06.310> the 00:16:06.750 --> 00:16:06.760 align:start position:0% games which is steadily growing but the 00:16:06.760 --> 00:16:08.670 align:start position:0% games which is steadily growing but the life<00:16:06.940> site<00:16:07.210> or<00:16:07.420> the<00:16:07.510> development<00:16:08.260> time<00:16:08.440> of<00:16:08.589> the 00:16:08.670 --> 00:16:08.680 align:start position:0% life site or the development time of the 00:16:08.680 --> 00:16:11.000 align:start position:0% life site or the development time of the game<00:16:08.830> is<00:16:08.950> actually<00:16:09.510> typically<00:16:10.510> pretty<00:16:10.779> long 00:16:11.000 --> 00:16:11.010 align:start position:0% game is actually typically pretty long 00:16:11.010 --> 00:16:13.890 align:start position:0% game is actually typically pretty long so<00:16:12.010> I<00:16:12.400> think<00:16:13.240> the<00:16:13.360> quality<00:16:13.720> of<00:16:13.779> the 00:16:13.890 --> 00:16:13.900 align:start position:0% so I think the quality of the 00:16:13.900 --> 00:16:15.720 align:start position:0% so I think the quality of the experiences<00:16:14.410> have<00:16:14.650> to<00:16:14.830> be<00:16:14.950> high<00:16:15.250> enough<00:16:15.520> for 00:16:15.720 --> 00:16:15.730 align:start position:0% experiences have to be high enough for 00:16:15.730 --> 00:16:17.700 align:start position:0% experiences have to be high enough for people<00:16:15.850> to<00:16:16.029> want<00:16:16.660> to<00:16:16.839> use<00:16:16.990> them<00:16:17.170> and<00:16:17.350> right<00:16:17.589> now 00:16:17.700 --> 00:16:17.710 align:start position:0% people to want to use them and right now 00:16:17.710 --> 00:16:19.560 align:start position:0% people to want to use them and right now they're<00:16:17.980> just<00:16:18.010> they're<00:16:18.940> getting<00:16:19.240> there<00:16:19.360> but 00:16:19.560 --> 00:16:19.570 align:start position:0% they're just they're getting there but 00:16:19.570 --> 00:16:22.890 align:start position:0% they're just they're getting there but they're<00:16:19.690> not<00:16:19.720> quite<00:16:20.020> there<00:16:20.170> and<00:16:20.380> then<00:16:21.900> use 00:16:22.890 --> 00:16:22.900 align:start position:0% they're not quite there and then use 00:16:22.900 --> 00:16:24.900 align:start position:0% they're not quite there and then use just<00:16:23.260> usability<00:16:23.890> of<00:16:23.920> the<00:16:24.100> network<00:16:24.430> in<00:16:24.550> general 00:16:24.900 --> 00:16:24.910 align:start position:0% just usability of the network in general 00:16:24.910 --> 00:16:29.760 align:start position:0% just usability of the network in general so<00:16:25.120> things<00:16:25.660> you<00:16:25.960> know<00:16:26.290> better<00:16:26.620> wallets<00:16:28.770> you 00:16:29.760 --> 00:16:29.770 align:start position:0% so things you know better wallets you 00:16:29.770 --> 00:16:32.430 align:start position:0% so things you know better wallets you know<00:16:29.880> potentially<00:16:30.880> better<00:16:31.779> blocked<00:16:32.140> chance 00:16:32.430 --> 00:16:32.440 align:start position:0% know potentially better blocked chance 00:16:32.440 --> 00:16:36.440 align:start position:0% know potentially better blocked chance for<00:16:33.160> people<00:16:33.279> to<00:16:33.460> build<00:16:33.580> these<00:16:33.760> assets<00:16:34.120> on 00:16:36.440 --> 00:16:36.450 align:start position:0% 00:16:36.450 --> 00:16:39.440 align:start position:0% existing<00:16:37.450> our<00:16:37.750> site<00:16:37.960> where<00:16:38.140> the<00:16:38.290> game 00:16:39.440 --> 00:16:39.450 align:start position:0% existing our site where the game 00:16:39.450 --> 00:16:44.930 align:start position:0% existing our site where the game I<00:16:40.640> think<00:16:41.640> the<00:16:42.770> main<00:16:43.770> thing<00:16:43.800> preventing<00:16:44.400> them 00:16:44.930 --> 00:16:44.940 align:start position:0% I think the main thing preventing them 00:16:44.940 --> 00:16:49.040 align:start position:0% I think the main thing preventing them is<00:16:45.590> well<00:16:46.590> I<00:16:46.680> guess<00:16:46.830> a<00:16:46.860> couple<00:16:47.130> things<00:16:47.430> one<00:16:48.180> is<00:16:48.750> I 00:16:49.040 --> 00:16:49.050 align:start position:0% is well I guess a couple things one is I 00:16:49.050 --> 00:16:51.440 align:start position:0% is well I guess a couple things one is I think<00:16:49.230> it's<00:16:49.350> kind<00:16:50.040> of<00:16:50.100> tricky<00:16:50.370> to<00:16:50.520> for<00:16:51.360> an 00:16:51.440 --> 00:16:51.450 align:start position:0% think it's kind of tricky to for an 00:16:51.450 --> 00:16:53.540 align:start position:0% think it's kind of tricky to for an existing<00:16:52.080> game<00:16:52.350> to<00:16:52.590> just<00:16:52.620> move<00:16:52.980> their<00:16:53.220> assets 00:16:53.540 --> 00:16:53.550 align:start position:0% existing game to just move their assets 00:16:53.550 --> 00:16:55.820 align:start position:0% existing game to just move their assets to<00:16:53.580> the<00:16:53.700> blockchain<00:16:53.910> right<00:16:54.650> especially<00:16:55.650> if<00:16:55.770> it 00:16:55.820 --> 00:16:55.830 align:start position:0% to the blockchain right especially if it 00:16:55.830 --> 00:16:57.830 align:start position:0% to the blockchain right especially if it was<00:16:55.920> a<00:16:55.980> really<00:16:56.190> big<00:16:56.430> game<00:16:56.670> and<00:16:57.060> they<00:16:57.450> wanted 00:16:57.830 --> 00:16:57.840 align:start position:0% was a really big game and they wanted 00:16:57.840 --> 00:17:01.160 align:start position:0% was a really big game and they wanted the<00:16:58.410> same<00:16:58.650> user<00:16:58.950> experience<00:16:59.840> you<00:17:00.840> know<00:17:00.930> they 00:17:01.160 --> 00:17:01.170 align:start position:0% the same user experience you know they 00:17:01.170 --> 00:17:03.020 align:start position:0% the same user experience you know they could<00:17:01.320> hide<00:17:01.530> away<00:17:01.770> all<00:17:01.920> the<00:17:02.400> theory<00:17:02.700> and<00:17:02.820> stuff 00:17:03.020 --> 00:17:03.030 align:start position:0% could hide away all the theory and stuff 00:17:03.030 --> 00:17:04.790 align:start position:0% could hide away all the theory and stuff but<00:17:03.390> then<00:17:03.570> you<00:17:04.319> know<00:17:04.410> they're<00:17:04.560> just<00:17:04.589> basically 00:17:04.790 --> 00:17:04.800 align:start position:0% but then you know they're just basically 00:17:04.800 --> 00:17:06.079 align:start position:0% but then you know they're just basically basically<00:17:05.310> using<00:17:05.579> a<00:17:05.640> really<00:17:05.850> expensive 00:17:06.079 --> 00:17:06.089 align:start position:0% basically using a really expensive 00:17:06.089 --> 00:17:10.610 align:start position:0% basically using a really expensive database<00:17:06.930> for<00:17:07.199> their<00:17:07.319> game<00:17:07.470> um<00:17:08.959> so<00:17:09.959> I<00:17:09.990> think<00:17:10.500> it 00:17:10.610 --> 00:17:10.620 align:start position:0% database for their game um so I think it 00:17:10.620 --> 00:17:11.689 align:start position:0% database for their game um so I think it I<00:17:10.829> think<00:17:11.010> the<00:17:11.130> games<00:17:11.310> that<00:17:11.459> are<00:17:11.520> most 00:17:11.689 --> 00:17:11.699 align:start position:0% I think the games that are most 00:17:11.699 --> 00:17:14.480 align:start position:0% I think the games that are most effective<00:17:12.150> have<00:17:12.329> to<00:17:12.449> be<00:17:12.569> new<00:17:12.839> games<00:17:13.140> and<00:17:13.500> those 00:17:14.480 --> 00:17:14.490 align:start position:0% effective have to be new games and those 00:17:14.490 --> 00:17:17.720 align:start position:0% effective have to be new games and those new<00:17:14.730> games<00:17:14.939> suffer<00:17:15.660> from<00:17:16.069> the<00:17:17.069> like 00:17:17.720 --> 00:17:17.730 align:start position:0% new games suffer from the like 00:17:17.730 --> 00:17:19.850 align:start position:0% new games suffer from the like onboarding<00:17:18.329> experience<00:17:18.449> of<00:17:19.199> getting<00:17:19.410> ether 00:17:19.850 --> 00:17:19.860 align:start position:0% onboarding experience of getting ether 00:17:19.860 --> 00:17:23.480 align:start position:0% onboarding experience of getting ether some<00:17:20.250> some<00:17:20.880> hide<00:17:21.150> it<00:17:21.360> but<00:17:22.140> then<00:17:22.350> you<00:17:23.339> know<00:17:23.430> you 00:17:23.480 --> 00:17:23.490 align:start position:0% some some hide it but then you know you 00:17:23.490 --> 00:17:26.000 align:start position:0% some some hide it but then you know you use<00:17:23.970> everything<00:17:24.270> and<00:17:24.780> then<00:17:25.020> they're<00:17:25.740> kind<00:17:25.890> of 00:17:26.000 --> 00:17:26.010 align:start position:0% use everything and then they're kind of 00:17:26.010 --> 00:17:28.490 align:start position:0% use everything and then they're kind of competing<00:17:26.430> with<00:17:26.520> every<00:17:26.730> other<00:17:26.850> game<00:17:27.410> but<00:17:28.410> if 00:17:28.490 --> 00:17:28.500 align:start position:0% competing with every other game but if 00:17:28.500 --> 00:17:29.900 align:start position:0% competing with every other game but if they<00:17:28.620> leverage<00:17:29.280> the<00:17:29.430> blocks<00:17:29.640> you<00:17:29.760> in<00:17:29.820> an 00:17:29.900 --> 00:17:29.910 align:start position:0% they leverage the blocks you in an 00:17:29.910 --> 00:17:32.630 align:start position:0% they leverage the blocks you in an interesting<00:17:30.180> way<00:17:30.510> then<00:17:31.340> you<00:17:32.340> know<00:17:32.400> there<00:17:32.550> are 00:17:32.630 --> 00:17:32.640 align:start position:0% interesting way then you know there are 00:17:32.640 --> 00:17:33.800 align:start position:0% interesting way then you know there are some<00:17:32.820> like<00:17:33.000> really<00:17:33.210> interesting<00:17:33.480> user 00:17:33.800 --> 00:17:33.810 align:start position:0% some like really interesting user 00:17:33.810 --> 00:17:35.330 align:start position:0% some like really interesting user benefits<00:17:34.260> like<00:17:34.440> trading<00:17:34.680> on<00:17:34.830> up<00:17:34.920> apartment 00:17:35.330 --> 00:17:35.340 align:start position:0% benefits like trading on up apartment 00:17:35.340 --> 00:17:37.500 align:start position:0% benefits like trading on up apartment leases 00:17:37.500 --> 00:17:37.510 align:start position:0% 00:17:37.510 --> 00:17:41.830 align:start position:0% we've<00:17:38.510> seen<00:17:38.750> any<00:17:39.110> adoption<00:17:39.770> from<00:17:40.840> virtual 00:17:41.830 --> 00:17:41.840 align:start position:0% we've seen any adoption from virtual 00:17:41.840 --> 00:17:46.410 align:start position:0% we've seen any adoption from virtual reality<00:17:42.730> these<00:17:43.730> days<00:17:44.090> or<00:17:44.390> augmented<00:17:45.050> reality 00:17:46.410 --> 00:17:46.420 align:start position:0% reality these days or augmented reality 00:17:46.420 --> 00:17:48.640 align:start position:0% reality these days or augmented reality producers<00:17:47.420> not<00:17:47.720> just<00:17:47.900> the<00:17:48.020> games<00:17:48.230> of<00:17:48.470> maybe 00:17:48.640 --> 00:17:48.650 align:start position:0% producers not just the games of maybe 00:17:48.650 --> 00:17:50.220 align:start position:0% producers not just the games of maybe even<00:17:48.770> like<00:17:49.070> interest<00:17:49.550> from<00:17:49.820> the 00:17:50.220 --> 00:17:50.230 align:start position:0% even like interest from the 00:17:50.230 --> 00:17:52.570 align:start position:0% even like interest from the manufacturers<00:17:51.230> of<00:17:51.320> the<00:17:51.620> headsets<00:17:52.070> and<00:17:52.400> such 00:17:52.570 --> 00:17:52.580 align:start position:0% manufacturers of the headsets and such 00:17:52.580 --> 00:17:55.000 align:start position:0% manufacturers of the headsets and such I'm<00:17:53.450> not<00:17:53.630> sure<00:17:53.840> yeah<00:17:54.230> I 00:17:55.000 --> 00:17:55.010 align:start position:0% I'm not sure yeah I 00:17:55.010 --> 00:17:57.130 align:start position:0% I'm not sure yeah I other<00:17:55.400> than<00:17:55.610> the<00:17:55.760> virtual<00:17:56.090> reality<00:17:56.240> projects 00:17:57.130 --> 00:17:57.140 align:start position:0% other than the virtual reality projects 00:17:57.140 --> 00:18:05.310 align:start position:0% other than the virtual reality projects I'm<00:17:57.470> not<00:17:57.710> I'm<00:17:58.130> not<00:17:58.309> sure 00:18:05.310 --> 00:18:05.320 align:start position:0% 00:18:05.320 --> 00:18:07.650 align:start position:0% it<00:18:05.380> seems<00:18:05.620> to<00:18:05.740> be<00:18:05.770> like<00:18:06.060> one<00:18:07.060> company<00:18:07.540> that 00:18:07.650 --> 00:18:07.660 align:start position:0% it seems to be like one company that 00:18:07.660 --> 00:18:08.940 align:start position:0% it seems to be like one company that they<00:18:07.750> have<00:18:07.960> is<00:18:08.140> that<00:18:08.260> their<00:18:08.410> unique 00:18:08.940 --> 00:18:08.950 align:start position:0% they have is that their unique 00:18:08.950 --> 00:18:12.210 align:start position:0% they have is that their unique individually<00:18:09.840> collectively<00:18:11.010> each<00:18:12.010> other 00:18:12.210 --> 00:18:12.220 align:start position:0% individually collectively each other 00:18:12.220 --> 00:18:15.390 align:start position:0% individually collectively each other because<00:18:12.550> of<00:18:12.640> my<00:18:12.790> collectibles<00:18:13.330> a<00:18:14.190> little<00:18:15.190> cost 00:18:15.390 --> 00:18:15.400 align:start position:0% because of my collectibles a little cost 00:18:15.400 --> 00:18:17.910 align:start position:0% because of my collectibles a little cost of<00:18:15.640> total<00:18:16.000> production<00:18:16.350> it's<00:18:17.350> really<00:18:17.620> easy<00:18:17.800> for 00:18:17.910 --> 00:18:17.920 align:start position:0% of total production it's really easy for 00:18:17.920 --> 00:18:19.500 align:start position:0% of total production it's really easy for lots<00:18:18.220> of<00:18:18.310> people<00:18:18.370> to<00:18:18.580> start<00:18:18.910> creating<00:18:19.360> these 00:18:19.500 --> 00:18:19.510 align:start position:0% lots of people to start creating these 00:18:19.510 --> 00:18:21.720 align:start position:0% lots of people to start creating these and<00:18:19.930> they<00:18:20.140> all<00:18:20.290> just<00:18:20.440> end<00:18:20.710> up<00:18:20.770> that<00:18:20.980> definitely 00:18:21.720 --> 00:18:21.730 align:start position:0% and they all just end up that definitely 00:18:21.730 --> 00:18:23.700 align:start position:0% and they all just end up that definitely needs<00:18:22.030> a<00:18:22.210> so<00:18:22.270> weird<00:18:22.780> is<00:18:22.870> where<00:18:23.320> you<00:18:23.410> think<00:18:23.620> the 00:18:23.700 --> 00:18:23.710 align:start position:0% needs a so weird is where you think the 00:18:23.710 --> 00:18:25.360 align:start position:0% needs a so weird is where you think the dynamism<00:18:24.100> is<00:18:24.790> it<00:18:24.940> like 00:18:25.360 --> 00:18:25.370 align:start position:0% dynamism is it like 00:18:25.370 --> 00:18:28.090 align:start position:0% dynamism is it like ability<00:18:26.150> to<00:18:26.210> be<00:18:26.360> on<00:18:26.450> i.t<00:18:26.770> because<00:18:27.770> you<00:18:27.860> can't 00:18:28.090 --> 00:18:28.100 align:start position:0% ability to be on i.t because you can't 00:18:28.100 --> 00:18:31.870 align:start position:0% ability to be on i.t because you can't pick<00:18:28.910> that<00:18:29.059> or<00:18:29.240> other<00:18:29.870> brands<00:18:30.260> like<00:18:30.470> I<00:18:31.460> think 00:18:31.870 --> 00:18:31.880 align:start position:0% pick that or other brands like I think 00:18:31.880 --> 00:18:35.980 align:start position:0% pick that or other brands like I think yeah<00:18:33.010> utility<00:18:34.010> and<00:18:34.220> provenance<00:18:34.780> and<00:18:35.780> maybe 00:18:35.980 --> 00:18:35.990 align:start position:0% yeah utility and provenance and maybe 00:18:35.990 --> 00:18:38.920 align:start position:0% yeah utility and provenance and maybe some<00:18:36.200> other<00:18:36.320> things<00:18:36.620> but<00:18:36.940> so<00:18:37.940> utility<00:18:38.540> of<00:18:38.600> NFC 00:18:38.920 --> 00:18:38.930 align:start position:0% some other things but so utility of NFC 00:18:38.930 --> 00:18:41.620 align:start position:0% some other things but so utility of NFC in<00:18:39.020> a<00:18:39.050> game<00:18:39.290> right<00:18:39.650> so<00:18:39.980> you<00:18:40.940> know<00:18:41.030> if<00:18:41.240> you<00:18:41.390> can 00:18:41.620 --> 00:18:41.630 align:start position:0% in a game right so you know if you can 00:18:41.630 --> 00:18:44.049 align:start position:0% in a game right so you know if you can just<00:18:42.559> if<00:18:42.800> you<00:18:42.920> can<00:18:43.070> with<00:18:43.370> statements<00:18:43.730> like<00:18:43.760> for 00:18:44.049 --> 00:18:44.059 align:start position:0% just if you can with statements like for 00:18:44.059 --> 00:18:45.160 align:start position:0% just if you can with statements like for tonight<00:18:44.240> right<00:18:44.270> if<00:18:44.480> you<00:18:44.570> can<00:18:44.720> wear<00:18:45.140> a 00:18:45.160 --> 00:18:45.170 align:start position:0% tonight right if you can wear a 00:18:45.170 --> 00:18:48.250 align:start position:0% tonight right if you can wear a legendary<00:18:45.770> or<00:18:46.100> the<00:18:46.250> well-known<00:18:46.970> skin<00:18:47.480> yeah 00:18:48.250 --> 00:18:48.260 align:start position:0% legendary or the well-known skin yeah 00:18:48.260 --> 00:18:49.660 align:start position:0% legendary or the well-known skin yeah that's<00:18:48.440> cool<00:18:48.830> and<00:18:49.100> you<00:18:49.160> can<00:18:49.220> show<00:18:49.460> it<00:18:49.550> off 00:18:49.660 --> 00:18:49.670 align:start position:0% that's cool and you can show it off 00:18:49.670 --> 00:18:52.630 align:start position:0% that's cool and you can show it off that's<00:18:50.420> sort<00:18:50.990> of<00:18:51.020> utility<00:18:51.590> and<00:18:52.490> then 00:18:52.630 --> 00:18:52.640 align:start position:0% that's sort of utility and then 00:18:52.640 --> 00:18:55.390 align:start position:0% that's sort of utility and then Providence<00:18:53.240> is<00:18:53.570> like<00:18:53.900> oh<00:18:54.170> this<00:18:54.530> was<00:18:54.740> the 00:18:55.390 --> 00:18:55.400 align:start position:0% Providence is like oh this was the 00:18:55.400 --> 00:18:58.060 align:start position:0% Providence is like oh this was the officially<00:18:56.150> endorsed<00:18:56.540> Disney<00:18:57.200> collectible 00:18:58.060 --> 00:18:58.070 align:start position:0% officially endorsed Disney collectible 00:18:58.070 --> 00:19:00.970 align:start position:0% officially endorsed Disney collectible and<00:18:58.340> hence<00:18:58.580> and<00:18:58.910> like<00:18:59.270> Disney<00:18:59.600> has<00:18:59.840> sang<00:19:00.830> she 00:19:00.970 --> 00:19:00.980 align:start position:0% and hence and like Disney has sang she 00:19:00.980 --> 00:19:02.860 align:start position:0% and hence and like Disney has sang she has<00:19:01.220> said<00:19:01.610> this<00:19:01.790> is<00:19:01.940> a<00:19:01.970> smart<00:19:02.210> contract<00:19:02.450> we're 00:19:02.860 --> 00:19:02.870 align:start position:0% has said this is a smart contract we're 00:19:02.870 --> 00:19:04.600 align:start position:0% has said this is a smart contract we're using<00:19:03.020> there<00:19:03.440> were<00:19:03.500> only<00:19:03.590> be<00:19:03.860> this<00:19:04.010> number<00:19:04.490> of 00:19:04.600 --> 00:19:04.610 align:start position:0% using there were only be this number of 00:19:04.610 --> 00:19:06.790 align:start position:0% using there were only be this number of them<00:19:04.730> I<00:19:04.880> think<00:19:05.059> that<00:19:05.270> it<00:19:06.050> kind<00:19:06.530> of<00:19:06.559> with<00:19:06.679> the 00:19:06.790 --> 00:19:06.800 align:start position:0% them I think that it kind of with the 00:19:06.800 --> 00:19:08.560 align:start position:0% them I think that it kind of with the Austrian<00:19:07.190> Postal<00:19:07.580> Service<00:19:08.090> right 00:19:08.560 --> 00:19:08.570 align:start position:0% Austrian Postal Service right 00:19:08.570 --> 00:19:11.290 align:start position:0% Austrian Postal Service right not<00:19:08.870> a<00:19:08.900> huge<00:19:09.140> brand<00:19:09.470> but<00:19:10.059> you<00:19:11.059> know<00:19:11.150> they 00:19:11.290 --> 00:19:11.300 align:start position:0% not a huge brand but you know they 00:19:11.300 --> 00:19:12.580 align:start position:0% not a huge brand but you know they basically<00:19:11.420> said<00:19:11.809> this<00:19:11.929> is<00:19:12.050> the<00:19:12.170> official 00:19:12.580 --> 00:19:12.590 align:start position:0% basically said this is the official 00:19:12.590 --> 00:19:14.890 align:start position:0% basically said this is the official crypto<00:19:13.370> stamp<00:19:13.670> for<00:19:14.030> the<00:19:14.179> Austrian<00:19:14.480> Postal 00:19:14.890 --> 00:19:14.900 align:start position:0% crypto stamp for the Austrian Postal 00:19:14.900 --> 00:19:17.710 align:start position:0% crypto stamp for the Austrian Postal Service<00:19:15.230> there's<00:19:15.800> only<00:19:15.980> five<00:19:16.460> like<00:19:17.390> red 00:19:17.710 --> 00:19:17.720 align:start position:0% Service there's only five like red 00:19:17.720 --> 00:19:21.010 align:start position:0% Service there's only five like red stamps<00:19:18.230> and<00:19:18.940> those<00:19:19.940> might<00:19:20.179> be<00:19:20.240> valuable<00:19:20.900> for 00:19:21.010 --> 00:19:21.020 align:start position:0% stamps and those might be valuable for 00:19:21.020 --> 00:19:33.160 align:start position:0% stamps and those might be valuable for collectors<00:19:30.100> yeah<00:19:31.100> so<00:19:31.429> there<00:19:31.820> have<00:19:32.059> been<00:19:32.330> a<00:19:32.870> lot 00:19:33.160 --> 00:19:33.170 align:start position:0% collectors yeah so there have been a lot 00:19:33.170 --> 00:19:35.890 align:start position:0% collectors yeah so there have been a lot of<00:19:33.200> like<00:19:33.679> swap<00:19:34.460> your<00:19:34.730> crypto<00:19:35.150> kitty<00:19:35.390> or<00:19:35.720> burn 00:19:35.890 --> 00:19:35.900 align:start position:0% of like swap your crypto kitty or burn 00:19:35.900 --> 00:19:38.980 align:start position:0% of like swap your crypto kitty or burn your<00:19:35.929> crypto<00:19:36.350> Katie<00:19:36.590> to<00:19:36.740> receive<00:19:37.070> I<00:19:37.929> think<00:19:38.929> it 00:19:38.980 --> 00:19:38.990 align:start position:0% your crypto Katie to receive I think it 00:19:38.990 --> 00:19:40.560 align:start position:0% your crypto Katie to receive I think it was<00:19:39.110> like<00:19:39.170> cryptid<00:19:39.530> strikers<00:19:39.920> that<00:19:40.160> did<00:19:40.340> this 00:19:40.560 --> 00:19:40.570 align:start position:0% was like cryptid strikers that did this 00:19:40.570 --> 00:19:43.630 align:start position:0% was like cryptid strikers that did this so<00:19:41.570> that<00:19:42.470> is<00:19:42.650> a<00:19:42.679> real<00:19:42.980> that's<00:19:43.190> a<00:19:43.309> really<00:19:43.520> good 00:19:43.630 --> 00:19:43.640 align:start position:0% so that is a real that's a really good 00:19:43.640 --> 00:19:46.950 align:start position:0% so that is a real that's a really good point<00:19:43.790> I<00:19:44.090> think<00:19:44.150> a<00:19:44.540> very<00:19:44.960> interesting<00:19:45.320> way<00:19:45.740> to 00:19:46.950 --> 00:19:46.960 align:start position:0% point I think a very interesting way to 00:19:46.960 --> 00:19:50.230 align:start position:0% point I think a very interesting way to to<00:19:47.960> engage<00:19:48.380> the<00:19:48.770> existing<00:19:49.280> community<00:19:49.520> is<00:19:50.030> to 00:19:50.230 --> 00:19:50.240 align:start position:0% to engage the existing community is to 00:19:50.240 --> 00:19:52.360 align:start position:0% to engage the existing community is to leverage<00:19:50.570> like<00:19:51.559> the<00:19:51.770> existing<00:19:52.010> set<00:19:52.340> of 00:19:52.360 --> 00:19:52.370 align:start position:0% leverage like the existing set of 00:19:52.370 --> 00:19:54.400 align:start position:0% leverage like the existing set of entities<00:19:52.580> right<00:19:53.030> so<00:19:53.300> go<00:19:53.750> to<00:19:53.780> cryptic<00:19:54.170> Cadiz 00:19:54.400 --> 00:19:54.410 align:start position:0% entities right so go to cryptic Cadiz 00:19:54.410 --> 00:19:55.630 align:start position:0% entities right so go to cryptic Cadiz and<00:19:54.470> say<00:19:54.679> oh<00:19:54.710> now<00:19:54.980> they're<00:19:55.160> useful<00:19:55.340> in<00:19:55.580> this 00:19:55.630 --> 00:19:55.640 align:start position:0% and say oh now they're useful in this 00:19:55.640 --> 00:19:57.940 align:start position:0% and say oh now they're useful in this other<00:19:55.820> game<00:19:55.970> or<00:19:56.360> you<00:19:56.929> can<00:19:57.230> trade<00:19:57.470> them<00:19:57.620> in<00:19:57.740> for 00:19:57.940 --> 00:19:57.950 align:start position:0% other game or you can trade them in for 00:19:57.950 --> 00:20:02.880 align:start position:0% other game or you can trade them in for our<00:19:58.520> game<00:19:58.760> asset<00:19:59.150> that's<00:19:59.330> better 00:20:02.880 --> 00:20:02.890 align:start position:0% 00:20:02.890 --> 00:20:04.590 align:start position:0% yeah<00:20:03.460> and<00:20:03.610> then<00:20:03.700> there's<00:20:03.880> there's<00:20:04.090> also<00:20:04.330> like 00:20:04.590 --> 00:20:04.600 align:start position:0% yeah and then there's there's also like 00:20:04.600 --> 00:20:08.000 align:start position:0% yeah and then there's there's also like NFT<00:20:05.080> airdrops<00:20:05.710> so<00:20:06.160> people<00:20:06.670> like<00:20:07.000> airdrop 00:20:08.000 --> 00:20:08.010 align:start position:0% NFT airdrops so people like airdrop 00:20:08.010 --> 00:20:09.990 align:start position:0% NFT airdrops so people like airdrop promotional<00:20:09.010> and<00:20:09.160> of<00:20:09.250> tea<00:20:09.400> in<00:20:09.610> your<00:20:09.730> yeah 00:20:09.990 --> 00:20:10.000 align:start position:0% promotional and of tea in your yeah 00:20:10.000 --> 00:20:12.540 align:start position:0% promotional and of tea in your yeah there's<00:20:10.600> like<00:20:10.690> tons<00:20:11.050> of<00:20:11.260> things<00:20:12.040> you<00:20:12.250> could<00:20:12.370> do 00:20:12.540 --> 00:20:12.550 align:start position:0% there's like tons of things you could do 00:20:12.550 --> 00:20:15.990 align:start position:0% there's like tons of things you could do it's<00:20:13.270> pretty<00:20:13.780> interesting 00:20:15.990 --> 00:20:16.000 align:start position:0% it's pretty interesting 00:20:16.000 --> 00:20:19.110 align:start position:0% it's pretty interesting have<00:20:16.240> you<00:20:16.330> seen<00:20:16.540> much<00:20:17.430> you<00:20:18.430> seen<00:20:18.580> anybody<00:20:18.760> kind 00:20:19.110 --> 00:20:19.120 align:start position:0% have you seen much you seen anybody kind 00:20:19.120 --> 00:20:21.870 align:start position:0% have you seen much you seen anybody kind of<00:20:19.180> use<00:20:19.360> an<00:20:19.510> empties<00:20:19.840> as<00:20:20.320> my<00:20:21.280> assistant 00:20:21.870 --> 00:20:21.880 align:start position:0% of use an empties as my assistant 00:20:21.880 --> 00:20:24.030 align:start position:0% of use an empties as my assistant like<00:20:22.150> I<00:20:22.270> have<00:20:22.540> this<00:20:22.720> path<00:20:22.960> set<00:20:23.260> so<00:20:23.560> therefore<00:20:24.010> I 00:20:24.030 --> 00:20:24.040 align:start position:0% like I have this path set so therefore I 00:20:24.040 --> 00:20:26.370 align:start position:0% like I have this path set so therefore I have<00:20:24.190> no<00:20:24.340> rights<00:20:24.700> to<00:20:24.880> do<00:20:24.970> this<00:20:25.150> yeah<00:20:25.990> so 00:20:26.370 --> 00:20:26.380 align:start position:0% have no rights to do this yeah so 00:20:26.380 --> 00:20:30.500 align:start position:0% have no rights to do this yeah so there's<00:20:27.070> the<00:20:27.550> unlock<00:20:28.030> protocol<00:20:28.750> which<00:20:29.560> is 00:20:30.500 --> 00:20:30.510 align:start position:0% there's the unlock protocol which is 00:20:30.510 --> 00:20:33.840 align:start position:0% there's the unlock protocol which is basically<00:20:31.510> sort<00:20:32.410> of<00:20:32.470> a<00:20:32.560> subscription<00:20:33.220> service 00:20:33.840 --> 00:20:33.850 align:start position:0% basically sort of a subscription service 00:20:33.850 --> 00:20:38.040 align:start position:0% basically sort of a subscription service that<00:20:35.670> you<00:20:36.670> you<00:20:36.940> buy<00:20:37.090> an<00:20:37.150> N<00:20:37.330> of<00:20:37.420> T<00:20:37.630> and<00:20:37.870> then<00:20:37.960> you 00:20:38.040 --> 00:20:38.050 align:start position:0% that you you buy an N of T and then you 00:20:38.050 --> 00:20:39.750 align:start position:0% that you you buy an N of T and then you get<00:20:38.230> access<00:20:38.530> to<00:20:38.740> content<00:20:39.220> or<00:20:39.490> something<00:20:39.700> like 00:20:39.750 --> 00:20:39.760 align:start position:0% get access to content or something like 00:20:39.760 --> 00:20:40.980 align:start position:0% get access to content or something like that<00:20:39.850> so<00:20:40.090> that's<00:20:40.240> not<00:20:40.330> what<00:20:40.630> they're<00:20:40.750> going 00:20:40.980 --> 00:20:40.990 align:start position:0% that so that's not what they're going 00:20:40.990 --> 00:20:42.750 align:start position:0% that so that's not what they're going after<00:20:41.200> is<00:20:41.470> they're<00:20:41.650> talking<00:20:42.100> to<00:20:42.310> publishers 00:20:42.750 --> 00:20:42.760 align:start position:0% after is they're talking to publishers 00:20:42.760 --> 00:20:46.290 align:start position:0% after is they're talking to publishers that<00:20:42.790> saying<00:20:43.230> it<00:20:44.230> was<00:20:44.350> for<00:20:44.500> that<00:20:44.650> also<00:20:45.550> a<00:20:45.700> Def 00:20:46.290 --> 00:20:46.300 align:start position:0% that saying it was for that also a Def 00:20:46.300 --> 00:20:50.250 align:start position:0% that saying it was for that also a Def Con<00:20:46.570> ticket<00:20:47.020> sold<00:20:47.410> on<00:20:47.590> and<00:20:47.770> upon<00:20:48.070> open<00:20:49.260> c-47s 00:20:50.250 --> 00:20:50.260 align:start position:0% Con ticket sold on and upon open c-47s 00:20:50.260 --> 00:20:53.220 align:start position:0% Con ticket sold on and upon open c-47s the<00:20:50.860> other<00:20:51.010> day<00:20:51.160> so<00:20:51.940> tickets<00:20:52.300> they're<00:20:52.870> kind<00:20:53.140> of 00:20:53.220 --> 00:20:53.230 align:start position:0% the other day so tickets they're kind of 00:20:53.230 --> 00:20:56.280 align:start position:0% the other day so tickets they're kind of a<00:20:53.290> commissioning<00:20:53.650> system<00:20:53.890> right<00:20:54.160> so<00:20:55.290> there's 00:20:56.280 --> 00:20:56.290 align:start position:0% a commissioning system right so there's 00:20:56.290 --> 00:21:01.610 align:start position:0% a commissioning system right so there's stuff<00:20:56.890> like<00:20:56.950> that 00:21:01.610 --> 00:21:01.620 align:start position:0% 00:21:01.620 --> 00:21:05.640 align:start position:0% all<00:21:02.620> right<00:21:02.740> so<00:21:03.010> now<00:21:03.430> digging<00:21:04.120> into<00:21:04.650> the 00:21:05.640 --> 00:21:05.650 align:start position:0% all right so now digging into the 00:21:05.650 --> 00:21:09.030 align:start position:0% all right so now digging into the nitty-gritty<00:21:06.720> so<00:21:07.720> if<00:21:07.930> anyone<00:21:08.290> has<00:21:08.320> their 00:21:09.030 --> 00:21:09.040 align:start position:0% nitty-gritty so if anyone has their 00:21:09.040 --> 00:21:11.760 align:start position:0% nitty-gritty so if anyone has their laptop<00:21:09.520> they<00:21:10.060> can<00:21:10.300> follow<00:21:11.110> along<00:21:11.350> your 00:21:11.760 --> 00:21:11.770 align:start position:0% laptop they can follow along your 00:21:11.770 --> 00:21:16.010 align:start position:0% laptop they can follow along your thought<00:21:12.660> just<00:21:13.660> watch<00:21:13.780> me<00:21:14.020> to<00:21:14.110> do<00:21:14.200> stuff<00:21:14.440> so 00:21:16.010 --> 00:21:16.020 align:start position:0% thought just watch me to do stuff so 00:21:16.020 --> 00:21:21.360 align:start position:0% thought just watch me to do stuff so this<00:21:17.020> is<00:21:17.200> the<00:21:17.500> ERC<00:21:18.190> 721<00:21:19.000> interface<00:21:20.370> it's 00:21:21.360 --> 00:21:21.370 align:start position:0% this is the ERC 721 interface it's 00:21:21.370 --> 00:21:27.860 align:start position:0% this is the ERC 721 interface it's basically<00:21:22.150> a<00:21:22.750> lot<00:21:23.290> like<00:21:24.150> ERC<00:21:25.260> 20<00:21:26.260> except<00:21:27.250> that 00:21:27.860 --> 00:21:27.870 align:start position:0% basically a lot like ERC 20 except that 00:21:27.870 --> 00:21:31.080 align:start position:0% basically a lot like ERC 20 except that the<00:21:28.870> key<00:21:29.170> method<00:21:29.740> is<00:21:29.920> sort<00:21:30.250> of<00:21:30.310> this<00:21:30.490> owner<00:21:30.760> of 00:21:31.080 --> 00:21:31.090 align:start position:0% the key method is sort of this owner of 00:21:31.090 --> 00:21:35.880 align:start position:0% the key method is sort of this owner of token<00:21:31.900> ID<00:21:32.050> right<00:21:32.680> so<00:21:33.070> the<00:21:33.850> token<00:21:34.420> I<00:21:34.510> think<00:21:34.890> of 00:21:35.880 --> 00:21:35.890 align:start position:0% token ID right so the token I think of 00:21:35.890 --> 00:21:39.030 align:start position:0% token ID right so the token I think of as<00:21:36.160> for<00:21:37.030> example<00:21:37.480> like<00:21:37.720> an<00:21:37.870> individual<00:21:38.410> crypto 00:21:39.030 --> 00:21:39.040 align:start position:0% as for example like an individual crypto 00:21:39.040 --> 00:21:41.880 align:start position:0% as for example like an individual crypto kitty<00:21:39.280> would<00:21:39.790> have<00:21:40.000> a<00:21:40.030> token<00:21:40.810> I<00:21:40.900> do<00:21:41.110> something 00:21:41.880 --> 00:21:41.890 align:start position:0% kitty would have a token I do something 00:21:41.890 --> 00:21:43.980 align:start position:0% kitty would have a token I do something and<00:21:42.100> to<00:21:42.760> check<00:21:42.970> who<00:21:43.180> owns<00:21:43.450> that<00:21:43.630> group<00:21:43.870> that 00:21:43.980 --> 00:21:43.990 align:start position:0% and to check who owns that group that 00:21:43.990 --> 00:21:46.580 align:start position:0% and to check who owns that group that could<00:21:44.080> either<00:21:44.230> you<00:21:44.440> call<00:21:44.650> owner<00:21:45.160> up<00:21:45.390> and<00:21:46.390> then 00:21:46.580 --> 00:21:46.590 align:start position:0% could either you call owner up and then 00:21:46.590 --> 00:21:49.050 align:start position:0% could either you call owner up and then maybe<00:21:47.590> some<00:21:47.860> of<00:21:47.980> you<00:21:48.100> are<00:21:48.250> familiar<00:21:48.460> with<00:21:48.850> the 00:21:49.050 --> 00:21:49.060 align:start position:0% maybe some of you are familiar with the 00:21:49.060 --> 00:21:52.260 align:start position:0% maybe some of you are familiar with the idea<00:21:49.270> of<00:21:49.540> proof<00:21:50.400> in<00:21:51.400> the<00:21:51.520> RFU<00:21:51.790> 20<00:21:52.060> but 00:21:52.260 --> 00:21:52.270 align:start position:0% idea of proof in the RFU 20 but 00:21:52.270 --> 00:21:55.140 align:start position:0% idea of proof in the RFU 20 but basically<00:21:52.630> this<00:21:52.870> is<00:21:53.050> a<00:21:53.080> way<00:21:53.200> for<00:21:54.150> an 00:21:55.140 --> 00:21:55.150 align:start position:0% basically this is a way for an 00:21:55.150 --> 00:21:57.540 align:start position:0% basically this is a way for an individual<00:21:55.900> to<00:21:56.140> say<00:21:56.320> I<00:21:56.350> approve<00:21:57.010> this<00:21:57.040> account 00:21:57.540 --> 00:21:57.550 align:start position:0% individual to say I approve this account 00:21:57.550 --> 00:22:01.710 align:start position:0% individual to say I approve this account to<00:21:57.850> transfer<00:21:58.780> my<00:21:59.110> item<00:22:00.040> so<00:22:00.760> for<00:22:01.180> exchange<00:22:01.510> is 00:22:01.710 --> 00:22:01.720 align:start position:0% to transfer my item so for exchange is 00:22:01.720 --> 00:22:05.580 align:start position:0% to transfer my item so for exchange is very<00:22:02.230> useful<00:22:02.530> because<00:22:02.680> you<00:22:03.070> can<00:22:03.550> approve<00:22:04.590> open 00:22:05.580 --> 00:22:05.590 align:start position:0% very useful because you can approve open 00:22:05.590 --> 00:22:08.280 align:start position:0% very useful because you can approve open and<00:22:05.680> see<00:22:05.830> are<00:22:06.190> actually<00:22:06.520> a<00:22:06.550> proxy<00:22:06.970> but<00:22:07.290> that's 00:22:08.280 --> 00:22:08.290 align:start position:0% and see are actually a proxy but that's 00:22:08.290 --> 00:22:11.790 align:start position:0% and see are actually a proxy but that's kind<00:22:08.470> of<00:22:08.500> a<00:22:08.620> detail<00:22:09.390> to<00:22:10.390> transfer<00:22:11.200> your<00:22:11.470> items 00:22:11.790 --> 00:22:11.800 align:start position:0% kind of a detail to transfer your items 00:22:11.800 --> 00:22:14.280 align:start position:0% kind of a detail to transfer your items in<00:22:12.670> the<00:22:12.820> event<00:22:13.090> of<00:22:13.300> a<00:22:13.420> sale<00:22:13.630> so<00:22:13.900> that<00:22:14.050> they 00:22:14.280 --> 00:22:14.290 align:start position:0% in the event of a sale so that they 00:22:14.290 --> 00:22:15.480 align:start position:0% in the event of a sale so that they don't<00:22:14.470> have<00:22:14.590> to<00:22:14.710> actually<00:22:14.770> leave<00:22:15.220> your<00:22:15.340> wallet 00:22:15.480 --> 00:22:15.490 align:start position:0% don't have to actually leave your wallet 00:22:15.490 --> 00:22:18.360 align:start position:0% don't have to actually leave your wallet while<00:22:16.000> they're<00:22:16.150> on<00:22:16.270> sale<00:22:17.100> and<00:22:18.100> then<00:22:18.220> this 00:22:18.360 --> 00:22:18.370 align:start position:0% while they're on sale and then this 00:22:18.370 --> 00:22:20.010 align:start position:0% while they're on sale and then this transfer<00:22:18.760> from<00:22:18.880> is<00:22:19.120> obviously<00:22:19.450> a<00:22:19.570> really<00:22:19.750> key 00:22:20.010 --> 00:22:20.020 align:start position:0% transfer from is obviously a really key 00:22:20.020 --> 00:22:22.080 align:start position:0% transfer from is obviously a really key one<00:22:20.200> this<00:22:20.710> is<00:22:20.860> basically<00:22:21.160> the<00:22:21.430> ability<00:22:21.580> to 00:22:22.080 --> 00:22:22.090 align:start position:0% one this is basically the ability to 00:22:22.090 --> 00:22:24.780 align:start position:0% one this is basically the ability to transfer<00:22:22.600> a<00:22:22.900> crypto<00:22:23.620> Kitty<00:22:23.800> or<00:22:24.250> what-have-you 00:22:24.780 --> 00:22:24.790 align:start position:0% transfer a crypto Kitty or what-have-you 00:22:24.790 --> 00:22:29.790 align:start position:0% transfer a crypto Kitty or what-have-you from<00:22:25.390> an<00:22:26.020> address<00:22:26.470> to<00:22:27.070> another<00:22:27.370> address<00:22:28.800> then 00:22:29.790 --> 00:22:29.800 align:start position:0% from an address to another address then 00:22:29.800 --> 00:22:32.870 align:start position:0% from an address to another address then the<00:22:30.130> kind<00:22:30.820> of<00:22:30.850> interesting<00:22:31.330> very<00:22:32.200> interesting 00:22:32.870 --> 00:22:32.880 align:start position:0% the kind of interesting very interesting 00:22:32.880 --> 00:22:37.230 align:start position:0% the kind of interesting very interesting part<00:22:33.880> of<00:22:34.180> ERC<00:22:35.110> 721<00:22:35.770> is<00:22:36.040> you<00:22:36.640> know<00:22:36.730> you<00:22:36.790> have 00:22:37.230 --> 00:22:37.240 align:start position:0% part of ERC 721 is you know you have 00:22:37.240 --> 00:22:39.780 align:start position:0% part of ERC 721 is you know you have these<00:22:37.540> token<00:22:38.410> ideas<00:22:38.770> but<00:22:39.160> how<00:22:39.640> do<00:22:39.700> you 00:22:39.780 --> 00:22:39.790 align:start position:0% these token ideas but how do you 00:22:39.790 --> 00:22:43.950 align:start position:0% these token ideas but how do you actually<00:22:40.470> represent<00:22:41.820> you<00:22:42.820> know<00:22:42.960> what 00:22:43.950 --> 00:22:43.960 align:start position:0% actually represent you know what 00:22:43.960 --> 00:22:46.590 align:start position:0% actually represent you know what encrypted<00:22:44.500> Kitty<00:22:44.680> is<00:22:44.890> which<00:22:45.280> is<00:22:45.490> you<00:22:46.330> know<00:22:46.420> has 00:22:46.590 --> 00:22:46.600 align:start position:0% encrypted Kitty is which is you know has 00:22:46.600 --> 00:22:47.160 align:start position:0% encrypted Kitty is which is you know has a<00:22:46.630> name 00:22:47.160 --> 00:22:47.170 align:start position:0% a name 00:22:47.170 --> 00:22:50.070 align:start position:0% a name as<00:22:47.470> an<00:22:47.650> image<00:22:48.070> as<00:22:48.460> the<00:22:49.030> description<00:22:49.390> has<00:22:49.780> to<00:22:49.930> be 00:22:50.070 --> 00:22:50.080 align:start position:0% as an image as the description has to be 00:22:50.080 --> 00:22:53.190 align:start position:0% as an image as the description has to be some<00:22:50.290> traits<00:22:50.560> so<00:22:51.130> where<00:22:51.700> does<00:22:51.910> that<00:22:51.940> live<00:22:52.390> and 00:22:53.190 --> 00:22:53.200 align:start position:0% some traits so where does that live and 00:22:53.200 --> 00:22:55.320 align:start position:0% some traits so where does that live and at<00:22:53.350> the<00:22:53.470> moment<00:22:53.890> all<00:22:54.340> of<00:22:54.640> that<00:22:54.790> lives<00:22:55.030> off 00:22:55.320 --> 00:22:55.330 align:start position:0% at the moment all of that lives off 00:22:55.330 --> 00:22:58.320 align:start position:0% at the moment all of that lives off chain<00:22:55.840> I<00:22:56.170> don't<00:22:56.980> think<00:22:57.130> there's<00:22:57.280> handling<00:22:58.240> of 00:22:58.320 --> 00:22:58.330 align:start position:0% chain I don't think there's handling of 00:22:58.330 --> 00:23:03.540 align:start position:0% chain I don't think there's handling of a<00:22:58.390> single<00:22:58.720> GRC<00:22:59.470> 7:21<00:23:00.130> that<00:23:00.310> has<00:23:00.430> put<00:23:01.110> a<00:23:02.340> lot<00:23:03.340> of 00:23:03.540 --> 00:23:03.550 align:start position:0% a single GRC 7:21 that has put a lot of 00:23:03.550 --> 00:23:05.460 align:start position:0% a single GRC 7:21 that has put a lot of data<00:23:03.730> on<00:23:03.880> chain<00:23:04.210> there<00:23:04.390> some<00:23:04.870> funny<00:23:05.080> ones<00:23:05.200> that 00:23:05.460 --> 00:23:05.470 align:start position:0% data on chain there some funny ones that 00:23:05.470 --> 00:23:07.530 align:start position:0% data on chain there some funny ones that put<00:23:05.650> some<00:23:05.860> data<00:23:06.070> on<00:23:06.280> chains<00:23:06.490> but<00:23:06.730> most<00:23:07.030> have 00:23:07.530 --> 00:23:07.540 align:start position:0% put some data on chains but most have 00:23:07.540 --> 00:23:09.780 align:start position:0% put some data on chains but most have some<00:23:07.870> off<00:23:08.080> chain<00:23:08.290> component<00:23:08.800> that's<00:23:09.550> where 00:23:09.780 --> 00:23:09.790 align:start position:0% some off chain component that's where 00:23:09.790 --> 00:23:12.840 align:start position:0% some off chain component that's where this<00:23:09.970> token<00:23:10.360> URI<00:23:10.660> comes<00:23:11.020> into<00:23:11.230> play<00:23:11.410> so<00:23:11.850> token 00:23:12.840 --> 00:23:12.850 align:start position:0% this token URI comes into play so token 00:23:12.850 --> 00:23:19.620 align:start position:0% this token URI comes into play so token URI<00:23:13.470> is<00:23:14.470> basically<00:23:15.360> a<00:23:16.360> way<00:23:17.170> for<00:23:17.200> the<00:23:18.100> ERC<00:23:18.820> 7:21 00:23:19.620 --> 00:23:19.630 align:start position:0% URI is basically a way for the ERC 7:21 00:23:19.630 --> 00:23:22.770 align:start position:0% URI is basically a way for the ERC 7:21 developer<00:23:20.350> to<00:23:20.560> say<00:23:21.150> this<00:23:22.150> is<00:23:22.360> where<00:23:22.540> you<00:23:22.630> can 00:23:22.770 --> 00:23:22.780 align:start position:0% developer to say this is where you can 00:23:22.780 --> 00:23:27.330 align:start position:0% developer to say this is where you can grab<00:23:22.990> all<00:23:23.380> the<00:23:23.590> data<00:23:23.620> for<00:23:24.370> my<00:23:25.200> item<00:23:26.200> so<00:23:27.130> this 00:23:27.330 --> 00:23:27.340 align:start position:0% grab all the data for my item so this 00:23:27.340 --> 00:23:30.810 align:start position:0% grab all the data for my item so this takes<00:23:27.520> in<00:23:27.670> a<00:23:27.730> token<00:23:28.000> ID<00:23:28.120> and<00:23:28.360> returns<00:23:28.660> a<00:23:28.990> URL<00:23:29.820> so 00:23:30.810 --> 00:23:30.820 align:start position:0% takes in a token ID and returns a URL so 00:23:30.820 --> 00:23:33.750 align:start position:0% takes in a token ID and returns a URL so here's<00:23:31.120> an<00:23:31.450> example<00:23:32.380> of<00:23:32.890> some<00:23:33.460> data<00:23:33.670> that 00:23:33.750 --> 00:23:33.760 align:start position:0% here's an example of some data that 00:23:33.760 --> 00:23:37.830 align:start position:0% here's an example of some data that would<00:23:34.030> be<00:23:34.090> returned<00:23:34.540> from<00:23:35.350> the<00:23:36.240> URL<00:23:37.240> when<00:23:37.750> you 00:23:37.830 --> 00:23:37.840 align:start position:0% would be returned from the URL when you 00:23:37.840 --> 00:23:42.120 align:start position:0% would be returned from the URL when you hit<00:23:38.050> it<00:23:38.200> that<00:23:39.420> represents<00:23:40.420> the<00:23:40.720> asset<00:23:41.320> so<00:23:41.620> this 00:23:42.120 --> 00:23:42.130 align:start position:0% hit it that represents the asset so this 00:23:42.130 --> 00:23:43.620 align:start position:0% hit it that represents the asset so this is<00:23:42.340> what's<00:23:42.610> actually<00:23:42.880> one<00:23:43.150> of<00:23:43.180> our<00:23:43.330> test 00:23:43.620 --> 00:23:43.630 align:start position:0% is what's actually one of our test 00:23:43.630 --> 00:23:46.280 align:start position:0% is what's actually one of our test assets<00:23:44.170> called<00:23:44.860> an<00:23:44.980> open<00:23:45.250> sea<00:23:45.430> creature<00:23:45.730> and 00:23:46.280 --> 00:23:46.290 align:start position:0% assets called an open sea creature and 00:23:46.290 --> 00:23:50.310 align:start position:0% assets called an open sea creature and you<00:23:47.290> can<00:23:47.710> see<00:23:47.860> it<00:23:47.980> has<00:23:48.130> a<00:23:48.160> description<00:23:48.520> a<00:23:49.320> image 00:23:50.310 --> 00:23:50.320 align:start position:0% you can see it has a description a image 00:23:50.320 --> 00:23:53.430 align:start position:0% you can see it has a description a image a<00:23:50.590> name<00:23:50.830> an<00:23:51.640> external<00:23:52.090> URL<00:23:52.240> and<00:23:52.840> these<00:23:53.200> all 00:23:53.430 --> 00:23:53.440 align:start position:0% a name an external URL and these all 00:23:53.440 --> 00:23:57.690 align:start position:0% a name an external URL and these all mapped<00:23:53.800> to<00:23:54.360> this<00:23:55.360> item<00:23:56.200> right<00:23:56.410> so<00:23:56.860> you<00:23:57.400> can<00:23:57.520> see 00:23:57.690 --> 00:23:57.700 align:start position:0% mapped to this item right so you can see 00:23:57.700 --> 00:24:01.950 align:start position:0% mapped to this item right so you can see the<00:23:58.710> the<00:23:59.710> image<00:24:00.010> this<00:24:00.670> view<00:24:01.420> on<00:24:01.570> open<00:24:01.840> sea 00:24:01.950 --> 00:24:01.960 align:start position:0% the the image this view on open sea 00:24:01.960 --> 00:24:04.770 align:start position:0% the the image this view on open sea creature<00:24:02.320> is<00:24:02.680> basically<00:24:03.190> the<00:24:03.520> external<00:24:04.450> URL 00:24:04.770 --> 00:24:04.780 align:start position:0% creature is basically the external URL 00:24:04.780 --> 00:24:07.260 align:start position:0% creature is basically the external URL that<00:24:04.990> you<00:24:05.110> would<00:24:05.260> kind<00:24:05.710> of<00:24:05.800> click<00:24:06.010> into<00:24:06.370> and 00:24:07.260 --> 00:24:07.270 align:start position:0% that you would kind of click into and 00:24:07.270 --> 00:24:09.750 align:start position:0% that you would kind of click into and then<00:24:07.450> it<00:24:07.690> has<00:24:07.840> these<00:24:08.050> properties<00:24:08.350> which<00:24:09.130> this 00:24:09.750 --> 00:24:09.760 align:start position:0% then it has these properties which this 00:24:09.760 --> 00:24:11.730 align:start position:0% then it has these properties which this is<00:24:09.910> kind<00:24:10.120> of<00:24:10.150> an<00:24:10.300> addition<00:24:10.720> that<00:24:10.990> open<00:24:11.560> sea 00:24:11.730 --> 00:24:11.740 align:start position:0% is kind of an addition that open sea 00:24:11.740 --> 00:24:14.630 align:start position:0% is kind of an addition that open sea made<00:24:12.550> up<00:24:12.730> to<00:24:13.270> allow<00:24:13.510> you<00:24:13.570> to<00:24:13.690> add 00:24:14.630 --> 00:24:14.640 align:start position:0% made up to allow you to add 00:24:14.640 --> 00:24:19.100 align:start position:0% made up to allow you to add rich<00:24:15.120> data<00:24:15.840> to<00:24:16.230> your<00:24:16.350> cigar<00:24:16.890> items<00:24:17.750> but<00:24:18.750> what's 00:24:19.100 --> 00:24:19.110 align:start position:0% rich data to your cigar items but what's 00:24:19.110 --> 00:24:20.720 align:start position:0% rich data to your cigar items but what's cool<00:24:19.260> is<00:24:19.320> that<00:24:19.530> you<00:24:20.010> know<00:24:20.100> as<00:24:20.190> long<00:24:20.400> as<00:24:20.460> you 00:24:20.720 --> 00:24:20.730 align:start position:0% cool is that you know as long as you 00:24:20.730 --> 00:24:24.350 align:start position:0% cool is that you know as long as you implement<00:24:21.180> the<00:24:21.420> token<00:24:21.750> URI<00:24:22.050> and<00:24:23.360> you've 00:24:24.350 --> 00:24:24.360 align:start position:0% implement the token URI and you've 00:24:24.360 --> 00:24:26.090 align:start position:0% implement the token URI and you've conformed<00:24:25.170> to<00:24:25.230> the<00:24:25.380> year<00:24:25.500> succesfully<00:24:25.950> but 00:24:26.090 --> 00:24:26.100 align:start position:0% conformed to the year succesfully but 00:24:26.100 --> 00:24:28.600 align:start position:0% conformed to the year succesfully but standard<00:24:26.400> you<00:24:26.970> kind<00:24:27.150> of<00:24:27.240> get<00:24:27.660> it<00:24:27.810> all<00:24:28.050> for<00:24:28.530> free 00:24:28.600 --> 00:24:28.610 align:start position:0% standard you kind of get it all for free 00:24:28.610 --> 00:24:30.800 align:start position:0% standard you kind of get it all for free and<00:24:29.610> as<00:24:29.760> you<00:24:29.910> can<00:24:30.060> see<00:24:30.120> like<00:24:30.450> this<00:24:30.630> is 00:24:30.800 --> 00:24:30.810 align:start position:0% and as you can see like this is 00:24:30.810 --> 00:24:32.810 align:start position:0% and as you can see like this is automatically<00:24:31.710> tradable<00:24:32.220> all<00:24:32.460> that<00:24:32.640> stuff 00:24:32.810 --> 00:24:32.820 align:start position:0% automatically tradable all that stuff 00:24:32.820 --> 00:24:36.040 align:start position:0% automatically tradable all that stuff because<00:24:33.120> it<00:24:33.270> is<00:24:33.540> here<00:24:34.470> since<00:24:34.710> definitely 00:24:36.040 --> 00:24:36.050 align:start position:0% because it is here since definitely 00:24:36.050 --> 00:24:38.510 align:start position:0% because it is here since definitely and<00:24:37.050> then<00:24:37.200> what<00:24:37.890> the<00:24:38.250> other<00:24:38.370> interesting 00:24:38.510 --> 00:24:38.520 align:start position:0% and then what the other interesting 00:24:38.520 --> 00:24:40.820 align:start position:0% and then what the other interesting thing<00:24:38.790> is<00:24:39.090> this<00:24:39.270> is<00:24:39.450> also<00:24:39.990> what<00:24:40.350> is<00:24:40.380> allowing 00:24:40.820 --> 00:24:40.830 align:start position:0% thing is this is also what is allowing 00:24:40.830 --> 00:24:43.130 align:start position:0% thing is this is also what is allowing for<00:24:41.070> limited<00:24:42.030> degrees<00:24:42.390> of<00:24:42.510> interoperability 00:24:43.130 --> 00:24:43.140 align:start position:0% for limited degrees of interoperability 00:24:43.140 --> 00:24:47.000 align:start position:0% for limited degrees of interoperability so<00:24:43.590> this<00:24:44.190> is<00:24:44.370> that<00:24:45.060> same<00:24:45.500> of<00:24:46.500> a<00:24:46.650> sea<00:24:46.830> creature 00:24:47.000 --> 00:24:47.010 align:start position:0% so this is that same of a sea creature 00:24:47.010 --> 00:24:50.000 align:start position:0% so this is that same of a sea creature inside<00:24:47.610> of<00:24:47.820> that<00:24:48.690> crypto<00:24:49.110> voxels<00:24:49.560> game<00:24:49.830> that 00:24:50.000 --> 00:24:50.010 align:start position:0% inside of that crypto voxels game that 00:24:50.010 --> 00:24:53.480 align:start position:0% inside of that crypto voxels game that is<00:24:50.100> mentioning<00:24:50.610> right<00:24:50.760> so<00:24:51.680> now<00:24:52.680> because<00:24:52.950> that 00:24:53.480 --> 00:24:53.490 align:start position:0% is mentioning right so now because that 00:24:53.490 --> 00:24:56.450 align:start position:0% is mentioning right so now because that metadata<00:24:54.000> is<00:24:54.540> standardized<00:24:55.100> crypto<00:24:56.100> box<00:24:56.280> hole 00:24:56.450 --> 00:24:56.460 align:start position:0% metadata is standardized crypto box hole 00:24:56.460 --> 00:24:58.460 align:start position:0% metadata is standardized crypto box hole or<00:24:56.700> whatever<00:24:56.790> site<00:24:57.240> it<00:24:57.360> can<00:24:57.600> go<00:24:57.810> and<00:24:58.080> pull<00:24:58.290> it 00:24:58.460 --> 00:24:58.470 align:start position:0% or whatever site it can go and pull it 00:24:58.470 --> 00:25:00.860 align:start position:0% or whatever site it can go and pull it or<00:24:58.860> use<00:24:59.070> those<00:24:59.280> fancy<00:24:59.580> api<00:24:59.880> which<00:25:00.240> makes<00:25:00.450> it<00:25:00.630> a 00:25:00.860 --> 00:25:00.870 align:start position:0% or use those fancy api which makes it a 00:25:00.870 --> 00:25:04.010 align:start position:0% or use those fancy api which makes it a little<00:25:01.080> more<00:25:01.230> convenient<00:25:01.940> to<00:25:02.940> grab<00:25:03.600> this 00:25:04.010 --> 00:25:04.020 align:start position:0% little more convenient to grab this 00:25:04.020 --> 00:25:06.410 align:start position:0% little more convenient to grab this assets<00:25:04.740> and<00:25:05.040> display<00:25:05.520> it<00:25:05.670> in<00:25:05.910> the<00:25:06.120> virtual 00:25:06.410 --> 00:25:06.420 align:start position:0% assets and display it in the virtual 00:25:06.420 --> 00:25:10.850 align:start position:0% assets and display it in the virtual world<00:25:08.300> and<00:25:09.300> ethers<00:25:10.080> can<00:25:10.260> as<00:25:10.410> well<00:25:10.590> has 00:25:10.850 --> 00:25:10.860 align:start position:0% world and ethers can as well has 00:25:10.860 --> 00:25:13.040 align:start position:0% world and ethers can as well has actually<00:25:11.370> recently<00:25:11.580> just<00:25:11.850> started<00:25:12.390> listing 00:25:13.040 --> 00:25:13.050 align:start position:0% actually recently just started listing 00:25:13.050 --> 00:25:15.980 align:start position:0% actually recently just started listing all<00:25:13.650> the<00:25:14.040> inventory<00:25:14.340> of<00:25:14.850> GRC<00:25:15.480> seven<00:25:15.810> twenty 00:25:15.980 --> 00:25:15.990 align:start position:0% all the inventory of GRC seven twenty 00:25:15.990 --> 00:25:17.390 align:start position:0% all the inventory of GRC seven twenty ones<00:25:16.200> which<00:25:16.350> i<00:25:16.410> think<00:25:16.470> is<00:25:16.710> that<00:25:16.860> there's<00:25:17.250> an 00:25:17.390 --> 00:25:17.400 align:start position:0% ones which i think is that there's an 00:25:17.400 --> 00:25:19.220 align:start position:0% ones which i think is that there's an interesting<00:25:17.610> sign<00:25:18.060> that<00:25:18.360> these<00:25:18.810> are<00:25:18.960> sort<00:25:19.170> of 00:25:19.220 --> 00:25:19.230 align:start position:0% interesting sign that these are sort of 00:25:19.230 --> 00:25:21.940 align:start position:0% interesting sign that these are sort of starting<00:25:19.470> to<00:25:19.860> achieve<00:25:20.280> the<00:25:20.460> same<00:25:20.670> level<00:25:21.510> of 00:25:21.940 --> 00:25:21.950 align:start position:0% starting to achieve the same level of 00:25:21.950 --> 00:25:26.120 align:start position:0% starting to achieve the same level of significance<00:25:22.950> as<00:25:23.750> year<00:25:24.750> c<00:25:24.990> twenty<00:25:25.290> which<00:25:25.470> you 00:25:26.120 --> 00:25:26.130 align:start position:0% significance as year c twenty which you 00:25:26.130 --> 00:25:28.130 align:start position:0% significance as year c twenty which you know<00:25:26.220> has<00:25:26.460> had<00:25:26.670> a<00:25:26.700> nice<00:25:27.120> either<00:25:27.810> scan 00:25:28.130 --> 00:25:28.140 align:start position:0% know has had a nice either scan 00:25:28.140 --> 00:25:30.470 align:start position:0% know has had a nice either scan interface<00:25:28.590> for<00:25:28.740> a<00:25:28.830> while<00:25:28.950> we've<00:25:29.820> crypto 00:25:30.470 --> 00:25:30.480 align:start position:0% interface for a while we've crypto 00:25:30.480 --> 00:25:32.080 align:start position:0% interface for a while we've crypto awesome<00:25:30.810> he<00:25:30.930> kind<00:25:31.440> of 00:25:32.080 --> 00:25:32.090 align:start position:0% awesome he kind of 00:25:32.090 --> 00:25:33.610 align:start position:0% awesome he kind of I<00:25:32.120> think<00:25:32.390> your<00:25:32.510> either<00:25:32.660> display<00:25:33.020> is<00:25:33.320> that<00:25:33.500> any 00:25:33.610 --> 00:25:33.620 align:start position:0% I think your either display is that any 00:25:33.620 --> 00:25:37.720 align:start position:0% I think your either display is that any any<00:25:34.370> kind<00:25:34.640> of<00:25:34.700> control<00:25:35.180> over<00:25:35.210> look<00:25:35.990> at<00:25:36.110> it<00:25:36.730> and 00:25:37.720 --> 00:25:37.730 align:start position:0% any kind of control over look at it and 00:25:37.730 --> 00:25:42.460 align:start position:0% any kind of control over look at it and they<00:25:37.850> don't<00:25:38.140> write<00:25:39.220> so<00:25:40.930> they<00:25:41.930> did<00:25:42.110> not<00:25:42.290> need 00:25:42.460 --> 00:25:42.470 align:start position:0% they don't write so they did not need 00:25:42.470 --> 00:25:45.940 align:start position:0% they don't write so they did not need permission<00:25:43.040> to<00:25:43.540> like<00:25:44.540> check<00:25:45.320> who<00:25:45.590> the<00:25:45.740> owner 00:25:45.940 --> 00:25:45.950 align:start position:0% permission to like check who the owner 00:25:45.950 --> 00:25:48.250 align:start position:0% permission to like check who the owner of<00:25:46.220> that<00:25:46.370> if<00:25:46.610> he<00:25:46.730> is<00:25:46.840> they<00:25:47.840> didn't<00:25:48.140> need 00:25:48.250 --> 00:25:48.260 align:start position:0% of that if he is they didn't need 00:25:48.260 --> 00:25:50.620 align:start position:0% of that if he is they didn't need permission<00:25:48.440> to<00:25:48.710> call<00:25:49.040> the<00:25:49.220> API<00:25:49.310> to<00:25:50.210> get<00:25:50.390> the 00:25:50.620 --> 00:25:50.630 align:start position:0% permission to call the API to get the 00:25:50.630 --> 00:25:53.920 align:start position:0% permission to call the API to get the data<00:25:50.840> in<00:25:51.640> crypto<00:25:52.640> voxels<00:25:53.000> case<00:25:53.150> they<00:25:53.360> use<00:25:53.630> our 00:25:53.920 --> 00:25:53.930 align:start position:0% data in crypto voxels case they use our 00:25:53.930 --> 00:25:56.380 align:start position:0% data in crypto voxels case they use our API<00:25:54.230> it's<00:25:54.800> like<00:25:55.040> I'm<00:25:55.250> a<00:25:55.280> convenience<00:25:55.850> thing<00:25:56.180> we 00:25:56.380 --> 00:25:56.390 align:start position:0% API it's like I'm a convenience thing we 00:25:56.390 --> 00:25:59.380 align:start position:0% API it's like I'm a convenience thing we kind<00:25:56.900> of<00:25:56.960> create<00:25:57.800> some<00:25:57.980> data<00:25:58.130> nicely<00:25:58.670> but<00:25:59.270> ya 00:25:59.380 --> 00:25:59.390 align:start position:0% kind of create some data nicely but ya 00:25:59.390 --> 00:26:04.420 align:start position:0% kind of create some data nicely but ya know<00:25:59.540> they<00:25:59.630> don't<00:25:59.780> question<00:26:02.530> five<00:26:03.530> points<00:26:03.980> URI 00:26:04.420 --> 00:26:04.430 align:start position:0% know they don't question five points URI 00:26:04.430 --> 00:26:09.880 align:start position:0% know they don't question five points URI right<00:26:06.910> yeah<00:26:07.910> so<00:26:08.630> we'll<00:26:08.780> see<00:26:08.960> if<00:26:09.290> I<00:26:09.410> got<00:26:09.560> the 00:26:09.880 --> 00:26:09.890 align:start position:0% right yeah so we'll see if I got the 00:26:09.890 --> 00:26:12.970 align:start position:0% right yeah so we'll see if I got the work<00:26:10.310> for<00:26:10.670> the<00:26:10.820> coding<00:26:11.210> part<00:26:11.450> of<00:26:11.600> this<00:26:11.750> that<00:26:12.050> it 00:26:12.970 --> 00:26:12.980 align:start position:0% work for the coding part of this that it 00:26:12.980 --> 00:26:15.730 align:start position:0% work for the coding part of this that it can<00:26:13.250> be<00:26:13.550> changed<00:26:14.300> depending<00:26:15.020> on<00:26:15.410> where<00:26:15.590> it's 00:26:15.730 --> 00:26:15.740 align:start position:0% can be changed depending on where it's 00:26:15.740 --> 00:26:18.730 align:start position:0% can be changed depending on where it's hosted<00:26:16.130> so<00:26:16.400> if<00:26:16.940> you<00:26:17.060> hosted<00:26:17.450> on<00:26:17.570> an<00:26:17.810> HTTP 00:26:18.730 --> 00:26:18.740 align:start position:0% hosted so if you hosted on an HTTP 00:26:18.740 --> 00:26:20.890 align:start position:0% hosted so if you hosted on an HTTP server<00:26:19.120> you<00:26:20.120> know<00:26:20.210> you<00:26:20.330> can't<00:26:20.510> really<00:26:20.660> change 00:26:20.890 --> 00:26:20.900 align:start position:0% server you know you can't really change 00:26:20.900 --> 00:26:23.050 align:start position:0% server you know you can't really change it<00:26:21.140> there's<00:26:22.010> not<00:26:22.130> really<00:26:22.430> good<00:26:22.670> standard 00:26:23.050 --> 00:26:23.060 align:start position:0% it there's not really good standard 00:26:23.060 --> 00:26:24.850 align:start position:0% it there's not really good standard around<00:26:23.240> like<00:26:23.480> you<00:26:24.200> know<00:26:24.290> the<00:26:24.410> metadata<00:26:24.740> is 00:26:24.850 --> 00:26:24.860 align:start position:0% around like you know the metadata is 00:26:24.860 --> 00:26:27.070 align:start position:0% around like you know the metadata is changing<00:26:25.370> and<00:26:25.490> then<00:26:25.640> everything<00:26:26.450> updating<00:26:26.930> or 00:26:27.070 --> 00:26:27.080 align:start position:0% changing and then everything updating or 00:26:27.080 --> 00:26:30.040 align:start position:0% changing and then everything updating or I'm<00:26:27.230> just<00:26:27.410> like<00:26:27.530> whole<00:26:28.210> but<00:26:29.210> if<00:26:29.570> you<00:26:29.690> post<00:26:29.930> it 00:26:30.040 --> 00:26:30.050 align:start position:0% I'm just like whole but if you post it 00:26:30.050 --> 00:26:33.610 align:start position:0% I'm just like whole but if you post it on<00:26:30.110> some<00:26:30.550> decentralized<00:26:32.260> immutable<00:26:33.260> file 00:26:33.610 --> 00:26:33.620 align:start position:0% on some decentralized immutable file 00:26:33.620 --> 00:26:36.750 align:start position:0% on some decentralized immutable file storage<00:26:33.980> statement 00:26:36.750 --> 00:26:36.760 align:start position:0% 00:26:36.760 --> 00:26:52.600 align:start position:0% yep 00:26:52.600 --> 00:26:52.610 align:start position:0% 00:26:52.610 --> 00:26:55.300 align:start position:0% [Music] 00:26:55.300 --> 00:26:55.310 align:start position:0% [Music] 00:26:55.310 --> 00:26:58.030 align:start position:0% [Music] yeah<00:26:55.940> so<00:26:56.150> you<00:26:56.210> could<00:26:56.510> well<00:26:57.320> so<00:26:57.470> before<00:26:57.800> it<00:26:57.890> gets 00:26:58.030 --> 00:26:58.040 align:start position:0% yeah so you could well so before it gets 00:26:58.040 --> 00:27:02.600 align:start position:0% yeah so you could well so before it gets old<00:26:58.220> can<00:26:58.430> you<00:26:58.460> transfer<00:26:58.820> it 00:27:02.600 --> 00:27:02.610 align:start position:0% 00:27:02.610 --> 00:27:09.230 align:start position:0% [Music] 00:27:09.230 --> 00:27:09.240 align:start position:0% 00:27:09.240 --> 00:27:14.450 align:start position:0% oh<00:27:09.270> yeah<00:27:10.140> so<00:27:10.409> um<00:27:10.799> like<00:27:11.730> if<00:27:12.630> I<00:27:13.020> put<00:27:13.350> a<00:27:13.409> sale<00:27:13.860> up<00:27:14.190> on 00:27:14.450 --> 00:27:14.460 align:start position:0% oh yeah so um like if I put a sale up on 00:27:14.460 --> 00:27:17.210 align:start position:0% oh yeah so um like if I put a sale up on open<00:27:14.909> sea<00:27:15.120> for<00:27:15.149> example<00:27:15.470> that<00:27:16.470> says<00:27:16.740> I'm<00:27:17.100> gonna 00:27:17.210 --> 00:27:17.220 align:start position:0% open sea for example that says I'm gonna 00:27:17.220 --> 00:27:20.029 align:start position:0% open sea for example that says I'm gonna sell<00:27:17.490> this<00:27:17.669> but<00:27:18.029> then<00:27:18.210> I<00:27:18.240> but<00:27:18.840> then<00:27:18.960> I<00:27:19.380> transfer 00:27:20.029 --> 00:27:20.039 align:start position:0% sell this but then I but then I transfer 00:27:20.039 --> 00:27:24.110 align:start position:0% sell this but then I but then I transfer it<00:27:20.070> somewhere<00:27:20.880> else<00:27:20.940> then<00:27:21.799> that<00:27:22.799> sale<00:27:23.700> will<00:27:23.909> be 00:27:24.110 --> 00:27:24.120 align:start position:0% it somewhere else then that sale will be 00:27:24.120 --> 00:27:26.510 align:start position:0% it somewhere else then that sale will be kind<00:27:24.570> of<00:27:24.600> cancelled<00:27:25.049> by<00:27:25.260> us<00:27:25.529> or<00:27:26.010> like<00:27:26.340> we'll 00:27:26.510 --> 00:27:26.520 align:start position:0% kind of cancelled by us or like we'll 00:27:26.520 --> 00:27:28.760 align:start position:0% kind of cancelled by us or like we'll keep<00:27:26.640> track<00:27:26.909> of<00:27:27.120> like<00:27:27.240> is<00:27:27.600> a<00:27:27.779> sale<00:27:28.140> valid<00:27:28.529> and 00:27:28.760 --> 00:27:28.770 align:start position:0% keep track of like is a sale valid and 00:27:28.770 --> 00:27:33.320 align:start position:0% keep track of like is a sale valid and then<00:27:29.039> there's<00:27:29.250> the<00:27:29.460> maybe<00:27:30.210> the<00:27:30.450> more<00:27:32.149> or<00:27:33.149> if<00:27:33.240> an 00:27:33.320 --> 00:27:33.330 align:start position:0% then there's the maybe the more or if an 00:27:33.330 --> 00:27:34.850 align:start position:0% then there's the maybe the more or if an attack<00:27:33.630> is<00:27:33.870> like<00:27:34.080> transferring<00:27:34.649> it<00:27:34.710> right 00:27:34.850 --> 00:27:34.860 align:start position:0% attack is like transferring it right 00:27:34.860 --> 00:27:36.289 align:start position:0% attack is like transferring it right before<00:27:34.980> it<00:27:35.700> gets<00:27:35.880> bought 00:27:36.289 --> 00:27:36.299 align:start position:0% before it gets bought 00:27:36.299 --> 00:27:38.960 align:start position:0% before it gets bought so<00:27:36.960> in<00:27:37.049> that<00:27:37.140> case<00:27:37.320> like<00:27:37.559> the<00:27:37.950> the<00:27:38.370> sale 00:27:38.960 --> 00:27:38.970 align:start position:0% so in that case like the the sale 00:27:38.970 --> 00:27:41.870 align:start position:0% so in that case like the the sale transaction<00:27:39.960> would<00:27:40.080> fail<00:27:40.320> right<00:27:40.740> because<00:27:41.100> it 00:27:41.870 --> 00:27:41.880 align:start position:0% transaction would fail right because it 00:27:41.880 --> 00:27:43.279 align:start position:0% transaction would fail right because it would<00:27:42.029> try<00:27:42.179> to<00:27:42.240> transfer<00:27:42.720> something<00:27:42.899> that<00:27:43.169> no 00:27:43.279 --> 00:27:43.289 align:start position:0% would try to transfer something that no 00:27:43.289 --> 00:27:45.470 align:start position:0% would try to transfer something that no longer<00:27:43.470> is<00:27:43.649> in<00:27:43.890> that<00:27:44.070> account<00:27:44.340> so<00:27:45.059> that<00:27:45.179> it's 00:27:45.470 --> 00:27:45.480 align:start position:0% longer is in that account so that it's 00:27:45.480 --> 00:27:47.990 align:start position:0% longer is in that account so that it's an<00:27:45.630> atomic<00:27:45.870> swap<00:27:46.350> right<00:27:46.620> so<00:27:46.890> there's<00:27:47.520> no<00:27:47.730> sort 00:27:47.990 --> 00:27:48.000 align:start position:0% an atomic swap right so there's no sort 00:27:48.000 --> 00:27:49.639 align:start position:0% an atomic swap right so there's no sort of<00:27:48.059> scenario<00:27:48.480> we're<00:27:48.690> like<00:27:48.840> in<00:27:49.020> the<00:27:49.140> middle<00:27:49.169> of 00:27:49.639 --> 00:27:49.649 align:start position:0% of scenario we're like in the middle of 00:27:49.649 --> 00:27:52.039 align:start position:0% of scenario we're like in the middle of the<00:27:50.309> sale<00:27:50.520> transaction<00:27:51.240> something<00:27:51.929> gets 00:27:52.039 --> 00:27:52.049 align:start position:0% the sale transaction something gets 00:27:52.049 --> 00:27:53.919 align:start position:0% the sale transaction something gets transferred<00:27:52.440> because<00:27:52.770> this<00:27:52.950> is<00:27:53.100> like 00:27:53.919 --> 00:27:53.929 align:start position:0% transferred because this is like 00:27:53.929 --> 00:28:01.830 align:start position:0% transferred because this is like watching 00:28:01.830 --> 00:28:01.840 align:start position:0% 00:28:01.840 --> 00:28:08.350 align:start position:0% so<00:28:04.030> didn't<00:28:05.030> open<00:28:05.600> them<00:28:06.080> do<00:28:06.320> them<00:28:06.760> yeah<00:28:07.760> so<00:28:08.030> if 00:28:08.350 --> 00:28:08.360 align:start position:0% so didn't open them do them yeah so if 00:28:08.360 --> 00:28:11.980 align:start position:0% so didn't open them do them yeah so if anyone<00:28:08.660> wants<00:28:08.990> to<00:28:09.020> try<00:28:10.010> out<00:28:10.040> deploying<00:28:10.910> any<00:28:11.540> RC 00:28:11.980 --> 00:28:11.990 align:start position:0% anyone wants to try out deploying any RC 00:28:11.990 --> 00:28:13.240 align:start position:0% anyone wants to try out deploying any RC 721<00:28:12.560> contract 00:28:13.240 --> 00:28:13.250 align:start position:0% 721 contract 00:28:13.250 --> 00:28:19.110 align:start position:0% 721 contract I<00:28:13.340> made<00:28:14.060> a<00:28:14.770> starter<00:28:15.770> repo<00:28:16.100> that<00:28:16.400> Forks<00:28:17.270> are 00:28:19.110 --> 00:28:19.120 align:start position:0% I made a starter repo that Forks are 00:28:19.120 --> 00:28:23.800 align:start position:0% I made a starter repo that Forks are basic<00:28:20.120> like<00:28:20.420> you<00:28:21.050> know<00:28:21.110> demo<00:28:21.500> repo<00:28:22.570> for<00:28:23.570> folks 00:28:23.800 --> 00:28:23.810 align:start position:0% basic like you know demo repo for folks 00:28:23.810 --> 00:28:28.260 align:start position:0% basic like you know demo repo for folks who<00:28:24.050> are<00:28:24.260> not<00:28:24.530> technical<00:28:25.720> we<00:28:26.720> we<00:28:27.260> also<00:28:27.410> have<00:28:27.770> a 00:28:28.260 --> 00:28:28.270 align:start position:0% who are not technical we we also have a 00:28:28.270 --> 00:28:31.000 align:start position:0% who are not technical we we also have a there's<00:28:29.270> plenty<00:28:29.870> there's<00:28:30.110> tons<00:28:30.290> of<00:28:30.410> ways<00:28:30.590> to 00:28:31.000 --> 00:28:31.010 align:start position:0% there's plenty there's tons of ways to 00:28:31.010 --> 00:28:34.600 align:start position:0% there's plenty there's tons of ways to mint<00:28:31.870> entities<00:28:32.870> which<00:28:33.740> I<00:28:33.950> encourage<00:28:34.460> you<00:28:34.580> to 00:28:34.600 --> 00:28:34.610 align:start position:0% mint entities which I encourage you to 00:28:34.610 --> 00:28:38.140 align:start position:0% mint entities which I encourage you to recommend<00:28:35.120> or<00:28:35.330> encourage<00:28:36.140> you<00:28:36.320> to<00:28:36.620> try<00:28:37.340> out<00:28:37.490> so 00:28:38.140 --> 00:28:38.150 align:start position:0% recommend or encourage you to try out so 00:28:38.150 --> 00:28:44.620 align:start position:0% recommend or encourage you to try out so one<00:28:38.420> example<00:28:38.600> here<00:28:39.560> is<00:28:40.570> a<00:28:41.570> rinkeby<00:28:43.630> instance 00:28:44.620 --> 00:28:44.630 align:start position:0% one example here is a rinkeby instance 00:28:44.630 --> 00:28:46.380 align:start position:0% one example here is a rinkeby instance of<00:28:44.780> open<00:28:44.990> sea<00:28:45.140> which<00:28:45.290> is<00:28:45.410> basically<00:28:45.680> kind<00:28:46.010> of<00:28:46.070> a 00:28:46.380 --> 00:28:46.390 align:start position:0% of open sea which is basically kind of a 00:28:46.390 --> 00:28:49.180 align:start position:0% of open sea which is basically kind of a playground<00:28:47.390> for<00:28:47.690> creating<00:28:48.470> enough<00:28:48.680> tees<00:28:48.920> and 00:28:49.180 --> 00:28:49.190 align:start position:0% playground for creating enough tees and 00:28:49.190 --> 00:28:52.060 align:start position:0% playground for creating enough tees and you<00:28:50.000> can<00:28:50.180> go<00:28:50.360> in<00:28:50.720> our<00:28:50.840> storefront<00:28:51.110> manager<00:28:51.770> and 00:28:52.060 --> 00:28:52.070 align:start position:0% you can go in our storefront manager and 00:28:52.070 --> 00:28:53.830 align:start position:0% you can go in our storefront manager and like<00:28:52.280> you<00:28:52.910> know<00:28:53.000> actually<00:28:53.330> deploying<00:28:53.660> a 00:28:53.830 --> 00:28:53.840 align:start position:0% like you know actually deploying a 00:28:53.840 --> 00:28:57.670 align:start position:0% like you know actually deploying a contract<00:28:54.760> and<00:28:55.760> then<00:28:56.630> mint<00:28:56.900> NM<00:28:57.200> tees 00:28:57.670 --> 00:28:57.680 align:start position:0% contract and then mint NM tees 00:28:57.680 --> 00:28:59.890 align:start position:0% contract and then mint NM tees there's<00:28:57.920> also<00:28:58.070> in<00:28:58.790> space<00:28:59.090> I<00:28:59.270> think<00:28:59.450> I<00:28:59.540> saw<00:28:59.690> in 00:28:59.890 --> 00:28:59.900 align:start position:0% there's also in space I think I saw in 00:28:59.900 --> 00:29:02.230 align:start position:0% there's also in space I think I saw in the<00:28:59.960> video<00:29:00.230> you<00:29:00.580> midbass<00:29:01.580> which<00:29:01.850> is<00:29:01.970> a<00:29:02.000> much 00:29:02.230 --> 00:29:02.240 align:start position:0% the video you midbass which is a much 00:29:02.240 --> 00:29:05.370 align:start position:0% the video you midbass which is a much better<00:29:02.450> tool<00:29:02.780> for<00:29:03.550> deploying 00:29:05.370 --> 00:29:05.380 align:start position:0% better tool for deploying 00:29:05.380 --> 00:29:08.140 align:start position:0% better tool for deploying networking<00:29:06.380> here<00:29:06.440> I<00:29:06.560> see<00:29:06.620> yeah<00:29:06.980> and<00:29:07.250> they<00:29:07.940> say 00:29:08.140 --> 00:29:08.150 align:start position:0% networking here I see yeah and they say 00:29:08.150 --> 00:29:12.850 align:start position:0% networking here I see yeah and they say oh<00:29:08.180> it's<00:29:08.630> right<00:29:08.750> there<00:29:08.860> for<00:29:10.450> ya<00:29:11.450> so<00:29:11.810> my<00:29:12.380> base<00:29:12.590> is 00:29:12.850 --> 00:29:12.860 align:start position:0% oh it's right there for ya so my base is 00:29:12.860 --> 00:29:17.050 align:start position:0% oh it's right there for ya so my base is like<00:29:13.010> a<00:29:13.870> much<00:29:14.870> more<00:29:15.410> feature-rich<00:29:16.160> way<00:29:16.730> of 00:29:17.050 --> 00:29:17.060 align:start position:0% like a much more feature-rich way of 00:29:17.060 --> 00:29:19.630 align:start position:0% like a much more feature-rich way of deploying<00:29:17.660> interesting<00:29:18.170> entities<00:29:18.640> our 00:29:19.630 --> 00:29:19.640 align:start position:0% deploying interesting entities our 00:29:19.640 --> 00:29:21.580 align:start position:0% deploying interesting entities our storefront<00:29:20.030> manager<00:29:20.720> just<00:29:21.140> like<00:29:21.290> kind<00:29:21.500> of 00:29:21.580 --> 00:29:21.590 align:start position:0% storefront manager just like kind of 00:29:21.590 --> 00:29:23.770 align:start position:0% storefront manager just like kind of this<00:29:22.430> is<00:29:22.580> one<00:29:22.730> of<00:29:22.760> the<00:29:22.850> day<00:29:22.940> was<00:29:23.090> deploying 00:29:23.770 --> 00:29:23.780 align:start position:0% this is one of the day was deploying 00:29:23.780 --> 00:29:26.320 align:start position:0% this is one of the day was deploying earlier<00:29:24.140> this<00:29:24.260> morning<00:29:24.410> but<00:29:25.150> you<00:29:26.150> know<00:29:26.210> I'm 00:29:26.320 --> 00:29:26.330 align:start position:0% earlier this morning but you know I'm 00:29:26.330 --> 00:29:28.330 align:start position:0% earlier this morning but you know I'm pretending<00:29:26.690> that<00:29:26.990> these<00:29:27.170> are<00:29:27.410> being<00:29:27.650> taken 00:29:28.330 --> 00:29:28.340 align:start position:0% pretending that these are being taken 00:29:28.340 --> 00:29:33.010 align:start position:0% pretending that these are being taken for<00:29:28.610> an<00:29:28.760> FTM<00:29:29.150> I<00:29:29.330> see<00:29:29.770> and<00:29:31.270> you<00:29:32.270> guys<00:29:32.420> for<00:29:32.930> the 00:29:33.010 --> 00:29:33.020 align:start position:0% for an FTM I see and you guys for the 00:29:33.020 --> 00:29:36.030 align:start position:0% for an FTM I see and you guys for the non-technical<00:29:33.500> folks<00:29:33.710> you<00:29:34.580> can<00:29:34.760> go<00:29:34.910> to<00:29:35.020> the 00:29:36.030 --> 00:29:36.040 align:start position:0% non-technical folks you can go to the 00:29:36.040 --> 00:29:39.000 align:start position:0% non-technical folks you can go to the development<00:29:37.040> new<00:29:37.160> storefront<00:29:37.880> manager<00:29:38.540> and 00:29:39.000 --> 00:29:39.010 align:start position:0% development new storefront manager and 00:29:39.010 --> 00:29:42.070 align:start position:0% development new storefront manager and sort<00:29:40.010> of<00:29:40.040> go<00:29:40.220> through<00:29:40.250> the<00:29:40.490> process<00:29:40.880> with<00:29:41.080> with 00:29:42.070 --> 00:29:42.080 align:start position:0% sort of go through the process with with 00:29:42.080 --> 00:29:45.580 align:start position:0% sort of go through the process with with meta<00:29:42.320> mass<00:29:42.530> for<00:29:43.040> deploying<00:29:43.970> a<00:29:44.330> year<00:29:44.840> to<00:29:45.020> 7:21 00:29:45.580 --> 00:29:45.590 align:start position:0% meta mass for deploying a year to 7:21 00:29:45.590 --> 00:29:47.500 align:start position:0% meta mass for deploying a year to 7:21 with<00:29:45.830> like<00:29:46.130> an<00:29:46.250> image<00:29:46.490> and<00:29:46.820> name<00:29:47.300> and 00:29:47.500 --> 00:29:47.510 align:start position:0% with like an image and name and 00:29:47.510 --> 00:29:51.310 align:start position:0% with like an image and name and description<00:29:49.180> but<00:29:50.180> if<00:29:50.360> you<00:29:50.570> were<00:29:50.750> so<00:29:51.050> what's 00:29:51.310 --> 00:29:51.320 align:start position:0% description but if you were so what's 00:29:51.320 --> 00:29:55.120 align:start position:0% description but if you were so what's interesting<00:29:51.530> about<00:29:51.800> this<00:29:52.160> is<00:29:53.410> you<00:29:54.410> know<00:29:54.470> you 00:29:55.120 --> 00:29:55.130 align:start position:0% interesting about this is you know you 00:29:55.130 --> 00:29:59.800 align:start position:0% interesting about this is you know you can<00:29:55.430> deploy<00:29:55.970> a<00:29:56.950> GRC<00:29:57.950> 731<00:29:58.640> using<00:29:59.390> any<00:29:59.600> of<00:29:59.690> these 00:29:59.800 --> 00:29:59.810 align:start position:0% can deploy a GRC 731 using any of these 00:29:59.810 --> 00:30:02.260 align:start position:0% can deploy a GRC 731 using any of these tools<00:29:59.870> and<00:30:00.620> they're<00:30:00.860> all<00:30:01.100> like<00:30:01.610> compatible 00:30:02.260 --> 00:30:02.270 align:start position:0% tools and they're all like compatible 00:30:02.270 --> 00:30:03.250 align:start position:0% tools and they're all like compatible with<00:30:02.390> each<00:30:02.510> other<00:30:02.630> so<00:30:02.900> it<00:30:02.990> doesn't<00:30:03.200> really 00:30:03.250 --> 00:30:03.260 align:start position:0% with each other so it doesn't really 00:30:03.260 --> 00:30:05.410 align:start position:0% with each other so it doesn't really matter<00:30:03.560> you<00:30:03.890> know<00:30:04.340> if<00:30:04.400> you<00:30:04.550> use<00:30:04.670> open<00:30:04.850> C<00:30:05.180> to 00:30:05.410 --> 00:30:05.420 align:start position:0% matter you know if you use open C to 00:30:05.420 --> 00:30:07.780 align:start position:0% matter you know if you use open C to deploy<00:30:05.690> it<00:30:05.900> use<00:30:06.500> midbass<00:30:06.890> or<00:30:07.250> if<00:30:07.490> you<00:30:07.580> do<00:30:07.670> it 00:30:07.780 --> 00:30:07.790 align:start position:0% deploy it use midbass or if you do it 00:30:07.790 --> 00:30:08.260 align:start position:0% deploy it use midbass or if you do it yourself 00:30:08.260 --> 00:30:08.270 align:start position:0% yourself 00:30:08.270 --> 00:30:12.820 align:start position:0% yourself and<00:30:08.710> for<00:30:09.710> the<00:30:09.800> developers<00:30:10.720> I'll<00:30:11.720> go<00:30:12.500> into<00:30:12.800> a 00:30:12.820 --> 00:30:12.830 align:start position:0% and for the developers I'll go into a 00:30:12.830 --> 00:30:16.690 align:start position:0% and for the developers I'll go into a little<00:30:12.920> bit<00:30:13.280> of<00:30:13.400> code<00:30:13.760> to<00:30:14.690> show<00:30:15.580> what<00:30:16.580> this 00:30:16.690 --> 00:30:16.700 align:start position:0% little bit of code to show what this 00:30:16.700 --> 00:30:21.320 align:start position:0% little bit of code to show what this would<00:30:16.880> actually<00:30:17.000> look<00:30:17.570> like 00:30:21.320 --> 00:30:21.330 align:start position:0% 00:30:21.330 --> 00:30:35.690 align:start position:0% and<00:30:22.490> so<00:30:23.780> this<00:30:24.780> is<00:30:25.850> people<00:30:26.850> go<00:30:27.030> yeah 00:30:35.690 --> 00:30:35.700 align:start position:0% 00:30:35.700 --> 00:30:40.760 align:start position:0% so<00:30:36.700> very<00:30:37.180> technical<00:30:37.680> so<00:30:38.680> this<00:30:38.890> is<00:30:39.070> a<00:30:39.370> example 00:30:40.760 --> 00:30:40.770 align:start position:0% so very technical so this is a example 00:30:40.770 --> 00:30:44.370 align:start position:0% so very technical so this is a example tradable<00:30:41.770> ERC<00:30:42.250> 721<00:30:42.790> token<00:30:43.120> it<00:30:43.840> tradable 00:30:44.370 --> 00:30:44.380 align:start position:0% tradable ERC 721 token it tradable 00:30:44.380 --> 00:30:46.380 align:start position:0% tradable ERC 721 token it tradable you're<00:30:44.560> so<00:30:44.740> sometime<00:30:45.100> token<00:30:45.460> isn't 00:30:46.380 --> 00:30:46.390 align:start position:0% you're so sometime token isn't 00:30:46.390 --> 00:30:47.730 align:start position:0% you're so sometime token isn't don't<00:30:46.750> think<00:30:46.870> of<00:30:47.020> it<00:30:47.080> as<00:30:47.230> anything<00:30:47.470> really 00:30:47.730 --> 00:30:47.740 align:start position:0% don't think of it as anything really 00:30:47.740 --> 00:30:50.910 align:start position:0% don't think of it as anything really special<00:30:48.270> we<00:30:49.270> just<00:30:49.480> added<00:30:49.660> some<00:30:49.840> like<00:30:50.320> utility 00:30:50.910 --> 00:30:50.920 align:start position:0% special we just added some like utility 00:30:50.920 --> 00:30:58.220 align:start position:0% special we just added some like utility functions<00:30:51.370> oh<00:30:52.110> sorry<00:30:53.110> yeah<00:30:54.780> so<00:30:55.780> also<00:30:56.500> my<00:30:56.770> like 00:30:58.220 --> 00:30:58.230 align:start position:0% functions oh sorry yeah so also my like 00:30:58.230 --> 00:31:05.040 align:start position:0% functions oh sorry yeah so also my like linters<00:31:01.770> but<00:31:02.770> the<00:31:03.670> so<00:31:04.090> you<00:31:04.660> know<00:31:04.750> just<00:31:04.870> let 00:31:05.040 --> 00:31:05.050 align:start position:0% linters but the so you know just let 00:31:05.050 --> 00:31:07.410 align:start position:0% linters but the so you know just let simple<00:31:05.380> way<00:31:05.470> to<00:31:05.500> mint<00:31:05.830> if<00:31:06.700> you<00:31:07.090> go<00:31:07.210> to<00:31:07.270> our 00:31:07.410 --> 00:31:07.420 align:start position:0% simple way to mint if you go to our 00:31:07.420 --> 00:31:08.550 align:start position:0% simple way to mint if you go to our documentation<00:31:07.570> you'll<00:31:08.110> also<00:31:08.230> see<00:31:08.530> some 00:31:08.550 --> 00:31:08.560 align:start position:0% documentation you'll also see some 00:31:08.560 --> 00:31:11.100 align:start position:0% documentation you'll also see some special<00:31:09.310> stuff<00:31:09.700> we<00:31:09.880> do<00:31:10.000> with<00:31:10.240> pre<00:31:10.630> approving 00:31:11.100 --> 00:31:11.110 align:start position:0% special stuff we do with pre approving 00:31:11.110 --> 00:31:15.240 align:start position:0% special stuff we do with pre approving tokens<00:31:11.590> for<00:31:11.800> trading<00:31:13.230> but<00:31:14.230> basically<00:31:15.010> it's 00:31:15.240 --> 00:31:15.250 align:start position:0% tokens for trading but basically it's 00:31:15.250 --> 00:31:17.610 align:start position:0% tokens for trading but basically it's just<00:31:15.310> an<00:31:15.550> ear<00:31:15.700> see<00:31:15.850> 721<00:31:16.510> and<00:31:16.840> heritage<00:31:17.350> from 00:31:17.610 --> 00:31:17.620 align:start position:0% just an ear see 721 and heritage from 00:31:17.620 --> 00:31:21.630 align:start position:0% just an ear see 721 and heritage from the<00:31:18.040> open<00:31:18.370> Zeppelin<00:31:18.930> PRC<00:31:19.930> 721<00:31:20.500> full<00:31:20.800> which<00:31:21.430> has 00:31:21.630 --> 00:31:21.640 align:start position:0% the open Zeppelin PRC 721 full which has 00:31:21.640 --> 00:31:25.050 align:start position:0% the open Zeppelin PRC 721 full which has all<00:31:22.180> sorts<00:31:22.450> of<00:31:22.800> nice<00:31:23.800> things<00:31:23.830> associated<00:31:24.730> with 00:31:25.050 --> 00:31:25.060 align:start position:0% all sorts of nice things associated with 00:31:25.060 --> 00:31:30.360 align:start position:0% all sorts of nice things associated with it<00:31:25.300> it<00:31:25.780> has<00:31:26.430> like<00:31:27.430> token<00:31:28.150> URI<00:31:28.770> it<00:31:29.770> has<00:31:29.920> like 00:31:30.360 --> 00:31:30.370 align:start position:0% it it has like token URI it has like 00:31:30.370 --> 00:31:33.240 align:start position:0% it it has like token URI it has like easy<00:31:30.550> ways<00:31:30.760> to<00:31:30.790> mint<00:31:31.210> easy<00:31:31.600> ways<00:31:31.810> to<00:31:31.960> burn<00:31:32.250> all 00:31:33.240 --> 00:31:33.250 align:start position:0% easy ways to mint easy ways to burn all 00:31:33.250 --> 00:31:37.050 align:start position:0% easy ways to mint easy ways to burn all that<00:31:33.310> stuff<00:31:33.820> so<00:31:34.570> it's<00:31:34.810> now<00:31:35.230> I<00:31:36.130> mean<00:31:36.250> it's<00:31:36.700> very 00:31:37.050 --> 00:31:37.060 align:start position:0% that stuff so it's now I mean it's very 00:31:37.060 --> 00:31:40.500 align:start position:0% that stuff so it's now I mean it's very simple<00:31:37.720> to<00:31:38.250> deploy<00:31:39.250> something<00:31:40.000> you<00:31:40.270> know<00:31:40.360> I'm 00:31:40.500 --> 00:31:40.510 align:start position:0% simple to deploy something you know I'm 00:31:40.510 --> 00:31:44.100 align:start position:0% simple to deploy something you know I'm not<00:31:40.600> a<00:31:40.660> coder<00:31:40.900> but<00:31:41.200> even<00:31:42.010> as<00:31:42.130> a<00:31:42.160> coder<00:31:42.870> you<00:31:43.870> can 00:31:44.100 --> 00:31:44.110 align:start position:0% not a coder but even as a coder you can 00:31:44.110 --> 00:32:02.689 align:start position:0% not a coder but even as a coder you can do<00:31:44.770> it<00:31:44.890> pretty<00:31:45.010> easily<00:31:45.480> so<00:31:46.480> I<00:31:46.900> will<00:31:47.530> attempt<00:31:48.460> to 00:32:02.689 --> 00:32:02.699 align:start position:0% 00:32:02.699 --> 00:32:07.679 align:start position:0% so<00:32:03.699> um<00:32:04.209> I<00:32:05.639> won't<00:32:06.639> like<00:32:07.209> trying<00:32:07.509> to<00:32:07.569> have 00:32:07.679 --> 00:32:07.689 align:start position:0% so um I won't like trying to have 00:32:07.689 --> 00:32:08.969 align:start position:0% so um I won't like trying to have everyone<00:32:08.049> do<00:32:08.199> it<00:32:08.229> because<00:32:08.559> I<00:32:08.589> never<00:32:08.739> thought 00:32:08.969 --> 00:32:08.979 align:start position:0% everyone do it because I never thought 00:32:08.979 --> 00:32:11.519 align:start position:0% everyone do it because I never thought that<00:32:09.219> time<00:32:09.459> but<00:32:09.759> basically<00:32:10.299> you<00:32:10.869> could<00:32:11.019> create 00:32:11.519 --> 00:32:11.529 align:start position:0% that time but basically you could create 00:32:11.529 --> 00:32:17.389 align:start position:0% that time but basically you could create a<00:32:11.829> dot<00:32:12.549> end<00:32:12.849> file<00:32:14.069> and<00:32:15.069> that<00:32:15.759> would<00:32:16.329> sort<00:32:16.599> of 00:32:17.389 --> 00:32:17.399 align:start position:0% a dot end file and that would sort of 00:32:17.399 --> 00:32:21.119 align:start position:0% a dot end file and that would sort of configure<00:32:18.399> all<00:32:18.639> the<00:32:18.909> accounts<00:32:19.449> that<00:32:19.959> you<00:32:20.679> want 00:32:21.119 --> 00:32:21.129 align:start position:0% configure all the accounts that you want 00:32:21.129 --> 00:32:26.669 align:start position:0% configure all the accounts that you want to<00:32:21.459> use<00:32:21.819> to<00:32:22.389> deploy<00:32:23.019> your<00:32:24.389> contract<00:32:25.389> so<00:32:26.349> it 00:32:26.669 --> 00:32:26.679 align:start position:0% to use to deploy your contract so it 00:32:26.679 --> 00:32:29.519 align:start position:0% to use to deploy your contract so it also<00:32:26.829> sets<00:32:27.189> up<00:32:27.339> a<00:32:27.639> figure<00:32:28.299> or<00:32:28.719> you<00:32:28.959> can<00:32:29.319> get<00:32:29.409> in 00:32:29.519 --> 00:32:29.529 align:start position:0% also sets up a figure or you can get in 00:32:29.529 --> 00:32:34.609 align:start position:0% also sets up a figure or you can get in a<00:32:29.559> fury<00:32:29.799> key<00:32:30.069> and<00:32:30.989> inject<00:32:31.989> it<00:32:32.139> in<00:32:32.469> there<00:32:33.509> and 00:32:34.609 --> 00:32:34.619 align:start position:0% a fury key and inject it in there and 00:32:34.619 --> 00:32:38.669 align:start position:0% a fury key and inject it in there and then<00:32:35.619> if<00:32:36.099> you<00:32:36.219> run<00:32:36.459> the<00:32:37.089> minting<00:32:37.659> scripts<00:32:38.379> or 00:32:38.669 --> 00:32:38.679 align:start position:0% then if you run the minting scripts or 00:32:38.679 --> 00:32:47.760 align:start position:0% then if you run the minting scripts or sorry<00:32:38.859> if<00:32:38.949> you<00:32:39.039> run<00:32:39.159> the<00:32:39.249> deployment<00:32:39.729> script 00:32:47.760 --> 00:32:47.770 align:start position:0% 00:32:47.770 --> 00:32:50.250 align:start position:0% then<00:32:48.309> in<00:32:48.610> theory<00:32:48.850> this<00:32:49.360> will<00:32:49.540> give<00:32:49.720> you<00:32:49.900> a<00:32:49.929> new 00:32:50.250 --> 00:32:50.260 align:start position:0% then in theory this will give you a new 00:32:50.260 --> 00:32:56.880 align:start position:0% then in theory this will give you a new yearís<00:32:50.980> at<00:32:51.160> 7:21<00:32:52.440> contract<00:32:55.530> and<00:32:56.530> one<00:32:56.710> cool 00:32:56.880 --> 00:32:56.890 align:start position:0% yearís at 7:21 contract and one cool 00:32:56.890 --> 00:32:59.280 align:start position:0% yearís at 7:21 contract and one cool thing<00:32:56.920> is<00:32:57.400> that<00:32:57.429> open<00:32:58.360> sea<00:32:58.660> will<00:32:58.900> actually 00:32:59.280 --> 00:32:59.290 align:start position:0% thing is that open sea will actually 00:32:59.290 --> 00:33:01.740 align:start position:0% thing is that open sea will actually pick<00:32:59.590> up<00:32:59.710> it<00:33:00.280> kind<00:33:00.490> of<00:33:00.520> like<00:33:00.700> ether<00:33:00.970> skin<00:33:01.210> will 00:33:01.740 --> 00:33:01.750 align:start position:0% pick up it kind of like ether skin will 00:33:01.750 --> 00:33:04.049 align:start position:0% pick up it kind of like ether skin will pick<00:33:01.929> up<00:33:02.050> any<00:33:02.260> new<00:33:02.350> air<00:33:02.950> 7:21<00:33:03.700> so<00:33:03.910> they're 00:33:04.049 --> 00:33:04.059 align:start position:0% pick up any new air 7:21 so they're 00:33:04.059 --> 00:33:07.169 align:start position:0% pick up any new air 7:21 so they're deployed<00:33:04.360> and<00:33:05.140> so<00:33:05.320> once<00:33:05.559> we<00:33:05.710> mint<00:33:06.160> our<00:33:06.490> first 00:33:07.169 --> 00:33:07.179 align:start position:0% deployed and so once we mint our first 00:33:07.179 --> 00:33:10.950 align:start position:0% deployed and so once we mint our first asset<00:33:08.050> on<00:33:08.320> this<00:33:08.559> year<00:33:08.800> so<00:33:08.950> 71<00:33:09.429> contract<00:33:09.970> will 00:33:10.950 --> 00:33:10.960 align:start position:0% asset on this year so 71 contract will 00:33:10.960 --> 00:33:13.440 align:start position:0% asset on this year so 71 contract will automatically<00:33:11.880> it'll<00:33:12.880> automatically<00:33:13.270> show 00:33:13.440 --> 00:33:13.450 align:start position:0% automatically it'll automatically show 00:33:13.450 --> 00:33:15.900 align:start position:0% automatically it'll automatically show up<00:33:13.480> but<00:33:13.690> I<00:33:13.809> can<00:33:13.960> see<00:33:14.170> and<00:33:15.070> you<00:33:15.220> could<00:33:15.370> don't 00:33:15.900 --> 00:33:15.910 align:start position:0% up but I can see and you could don't 00:33:15.910 --> 00:33:19.110 align:start position:0% up but I can see and you could don't trade<00:33:16.150> it<00:33:16.300> so<00:33:17.040> we<00:33:18.040> go<00:33:18.130> to<00:33:18.160> the<00:33:18.400> contract 00:33:19.110 --> 00:33:19.120 align:start position:0% trade it so we go to the contract 00:33:19.120 --> 00:33:45.110 align:start position:0% trade it so we go to the contract employed 00:33:45.110 --> 00:33:45.120 align:start position:0% 00:33:45.120 --> 00:33:47.900 align:start position:0% in<00:33:45.600> the<00:33:45.720> meantime<00:33:45.960> I<00:33:46.770> can<00:33:47.310> start<00:33:47.730> talking 00:33:47.900 --> 00:33:47.910 align:start position:0% in the meantime I can start talking 00:33:47.910 --> 00:33:58.269 align:start position:0% in the meantime I can start talking about<00:33:48.150> the<00:33:49.070> minting<00:33:50.070> scripts 00:33:58.269 --> 00:33:58.279 align:start position:0% 00:33:58.279 --> 00:34:10.630 align:start position:0% so<00:33:59.279> here's<00:33:59.759> our<00:33:59.970> contract 00:34:10.630 --> 00:34:10.640 align:start position:0% 00:34:10.640 --> 00:34:13.900 align:start position:0% and<00:34:11.140> so<00:34:12.140> the<00:34:12.500> minting<00:34:12.830> scripts<00:34:13.190> this<00:34:13.340> is<00:34:13.520> this 00:34:13.900 --> 00:34:13.910 align:start position:0% and so the minting scripts this is this 00:34:13.910 --> 00:34:19.210 align:start position:0% and so the minting scripts this is this kind<00:34:14.240> of<00:34:14.300> where<00:34:14.540> the<00:34:16.390> token<00:34:17.390> URI<00:34:18.220> immutable 00:34:19.210 --> 00:34:19.220 align:start position:0% kind of where the token URI immutable 00:34:19.220 --> 00:34:22.170 align:start position:0% kind of where the token URI immutable versus<00:34:20.120> not<00:34:20.300> immutable<00:34:20.780> data<00:34:21.160> storage 00:34:22.170 --> 00:34:22.180 align:start position:0% versus not immutable data storage 00:34:22.180 --> 00:34:25.630 align:start position:0% versus not immutable data storage becomes<00:34:23.180> kind<00:34:23.510> of<00:34:23.570> interesting<00:34:23.990> so<00:34:24.640> this 00:34:25.630 --> 00:34:25.640 align:start position:0% becomes kind of interesting so this 00:34:25.640 --> 00:34:28.890 align:start position:0% becomes kind of interesting so this minting<00:34:26.060> script<00:34:26.420> I<00:34:26.600> made<00:34:27.020> earlier<00:34:27.530> today<00:34:28.010> and 00:34:28.890 --> 00:34:28.900 align:start position:0% minting script I made earlier today and 00:34:28.900 --> 00:34:32.650 align:start position:0% minting script I made earlier today and it<00:34:29.900> basically<00:34:30.020> just<00:34:30.290> uses<00:34:30.860> some<00:34:31.460> JSON<00:34:32.120> storage 00:34:32.650 --> 00:34:32.660 align:start position:0% it basically just uses some JSON storage 00:34:32.660 --> 00:34:36.850 align:start position:0% it basically just uses some JSON storage site<00:34:33.470> that<00:34:33.650> I<00:34:33.740> found<00:34:33.980> so<00:34:34.760> if<00:34:34.820> we<00:34:34.940> go<00:34:35.090> to<00:34:35.150> this<00:34:35.860> I 00:34:36.850 --> 00:34:36.860 align:start position:0% site that I found so if we go to this I 00:34:36.860 --> 00:34:44.500 align:start position:0% site that I found so if we go to this I just<00:34:37.460> literally<00:34:38.120> just<00:34:38.800> like<00:34:39.800> I<00:34:43.150> just<00:34:44.150> created 00:34:44.500 --> 00:34:44.510 align:start position:0% just literally just like I just created 00:34:44.510 --> 00:34:46.960 align:start position:0% just literally just like I just created a<00:34:44.750> little<00:34:44.960> bit<00:34:45.080> of<00:34:45.170> JSON<00:34:45.350> right<00:34:45.800> so<00:34:46.100> named 00:34:46.960 --> 00:34:46.970 align:start position:0% a little bit of JSON right so named 00:34:46.970 --> 00:34:50.410 align:start position:0% a little bit of JSON right so named hello<00:34:47.680> description<00:34:48.680> hi<00:34:49.040> there<00:34:49.280> I'm<00:34:50.120> in<00:34:50.240> an 00:34:50.410 --> 00:34:50.420 align:start position:0% hello description hi there I'm in an 00:34:50.420 --> 00:34:53.440 align:start position:0% hello description hi there I'm in an image<00:34:50.960> and<00:34:51.200> this<00:34:51.710> is<00:34:51.860> really<00:34:52.160> good<00:34:52.790> enough<00:34:53.090> for 00:34:53.440 --> 00:34:53.450 align:start position:0% image and this is really good enough for 00:34:53.450 --> 00:34:56.380 align:start position:0% image and this is really good enough for the<00:34:54.050> metadata<00:34:54.440> standard<00:34:54.830> technically<00:34:55.280> but<00:34:56.030> it 00:34:56.380 --> 00:34:56.390 align:start position:0% the metadata standard technically but it 00:34:56.390 --> 00:34:59.200 align:start position:0% the metadata standard technically but it to<00:34:56.930> point<00:34:57.200> back<00:34:57.380> there<00:34:57.650> I<00:34:57.980> can<00:34:58.640> go<00:34:58.790> and<00:34:59.000> like 00:34:59.200 --> 00:34:59.210 align:start position:0% to point back there I can go and like 00:34:59.210 --> 00:35:01.690 align:start position:0% to point back there I can go and like modify<00:34:59.960> this<00:35:00.170> right<00:35:00.380> so<00:35:00.620> if<00:35:00.830> you're<00:35:01.010> trying<00:35:01.640> to 00:35:01.690 --> 00:35:01.700 align:start position:0% modify this right so if you're trying to 00:35:01.700 --> 00:35:05.350 align:start position:0% modify this right so if you're trying to create<00:35:02.120> an<00:35:02.330> N<00:35:02.450> of<00:35:02.570> T<00:35:02.780> that<00:35:03.170> is<00:35:03.580> immutably<00:35:04.580> like 00:35:05.350 --> 00:35:05.360 align:start position:0% create an N of T that is immutably like 00:35:05.360 --> 00:35:07.930 align:start position:0% create an N of T that is immutably like has<00:35:05.780> a<00:35:06.080> mutable<00:35:06.620> image<00:35:07.040> associated<00:35:07.460> with<00:35:07.700> it 00:35:07.930 --> 00:35:07.940 align:start position:0% has a mutable image associated with it 00:35:07.940 --> 00:35:10.570 align:start position:0% has a mutable image associated with it it's<00:35:08.210> always<00:35:08.540> the<00:35:09.260> same<00:35:09.440> name<00:35:09.710> etc<00:35:10.340> then 00:35:10.570 --> 00:35:10.580 align:start position:0% it's always the same name etc then 00:35:10.580 --> 00:35:12.850 align:start position:0% it's always the same name etc then you'll<00:35:11.120> probably<00:35:11.300> want<00:35:11.840> to<00:35:11.960> look<00:35:12.590> into 00:35:12.850 --> 00:35:12.860 align:start position:0% you'll probably want to look into 00:35:12.860 --> 00:35:15.910 align:start position:0% you'll probably want to look into something<00:35:13.040> like<00:35:13.310> a<00:35:13.580> TFS<00:35:14.360> so<00:35:15.200> that<00:35:15.380> you<00:35:15.860> know 00:35:15.910 --> 00:35:15.920 align:start position:0% something like a TFS so that you know 00:35:15.920 --> 00:35:18.790 align:start position:0% something like a TFS so that you know your<00:35:16.240> customers<00:35:17.240> can<00:35:17.510> have<00:35:17.570> this<00:35:17.870> guarantee 00:35:18.790 --> 00:35:18.800 align:start position:0% your customers can have this guarantee 00:35:18.800 --> 00:35:19.670 align:start position:0% your customers can have this guarantee that<00:35:19.070> there 00:35:19.670 --> 00:35:19.680 align:start position:0% that there 00:35:19.680 --> 00:35:28.460 align:start position:0% that there don't<00:35:20.070> be<00:35:20.160> changed<00:35:26.480> it<00:35:27.480> seems<00:35:27.630> like<00:35:27.900> most<00:35:28.170> for 00:35:28.460 --> 00:35:28.470 align:start position:0% don't be changed it seems like most for 00:35:28.470 --> 00:35:35.900 align:start position:0% don't be changed it seems like most for usin<00:35:28.770> URLs<00:35:29.220> yep<00:35:31.880> our<00:35:32.880> most<00:35:33.890> liked<00:35:34.890> readers<00:35:35.550> of 00:35:35.900 --> 00:35:35.910 align:start position:0% usin URLs yep our most liked readers of 00:35:35.910 --> 00:35:43.520 align:start position:0% usin URLs yep our most liked readers of MFT<00:35:36.840> s<00:35:37.050> fingertip<00:35:37.890> over<00:35:38.130> the<00:35:38.310> URL<00:35:38.730> or<00:35:41.660> -<00:35:42.660> yeah 00:35:43.520 --> 00:35:43.530 align:start position:0% MFT s fingertip over the URL or - yeah 00:35:43.530 --> 00:35:45.470 align:start position:0% MFT s fingertip over the URL or - yeah so<00:35:43.770> certainly<00:35:44.100> like<00:35:44.430> we<00:35:44.610> have<00:35:44.820> support<00:35:45.210> for 00:35:45.470 --> 00:35:45.480 align:start position:0% so certainly like we have support for 00:35:45.480 --> 00:35:50.450 align:start position:0% so certainly like we have support for IVFs<00:35:46.470> um<00:35:47.540> there's<00:35:48.540> not<00:35:48.690> that<00:35:48.960> many<00:35:49.170> like<00:35:49.560> nf2 00:35:50.450 --> 00:35:50.460 align:start position:0% IVFs um there's not that many like nf2 00:35:50.460 --> 00:35:52.640 align:start position:0% IVFs um there's not that many like nf2 readers<00:35:51.030> they<00:35:51.420> all<00:35:51.630> like<00:35:52.110> most<00:35:52.350> of<00:35:52.440> them<00:35:52.530> use 00:35:52.640 --> 00:35:52.650 align:start position:0% readers they all like most of them use 00:35:52.650 --> 00:35:55.370 align:start position:0% readers they all like most of them use our<00:35:52.770> API<00:35:53.010> because<00:35:53.940> they're<00:35:54.870> in<00:35:55.140> their<00:35:55.350> early 00:35:55.370 --> 00:35:55.380 align:start position:0% our API because they're in their early 00:35:55.380 --> 00:35:57.050 align:start position:0% our API because they're in their early days<00:35:55.830> like<00:35:56.100> with<00:35:56.250> crypto<00:35:56.520> kiddies<00:35:56.760> there<00:35:56.970> was 00:35:57.050 --> 00:35:57.060 align:start position:0% days like with crypto kiddies there was 00:35:57.060 --> 00:35:59.150 align:start position:0% days like with crypto kiddies there was actually<00:35:57.360> no<00:35:57.480> token<00:35:57.960> or<00:35:58.050> a<00:35:58.080> standard<00:35:58.650> and<00:35:58.980> so 00:35:59.150 --> 00:35:59.160 align:start position:0% actually no token or a standard and so 00:35:59.160 --> 00:36:00.320 align:start position:0% actually no token or a standard and so everyone<00:35:59.580> just<00:35:59.700> had<00:35:59.820> their<00:35:59.940> own<00:36:00.090> like<00:36:00.300> weird 00:36:00.320 --> 00:36:00.330 align:start position:0% everyone just had their own like weird 00:36:00.330 --> 00:36:04.190 align:start position:0% everyone just had their own like weird API<00:36:01.020> right<00:36:01.590> like<00:36:01.890> that<00:36:02.630> showed<00:36:03.630> data<00:36:03.840> in<00:36:04.020> some 00:36:04.190 --> 00:36:04.200 align:start position:0% API right like that showed data in some 00:36:04.200 --> 00:36:06.350 align:start position:0% API right like that showed data in some random<00:36:04.560> and<00:36:04.830> people<00:36:05.130> still<00:36:05.340> deploy<00:36:05.790> your 00:36:06.350 --> 00:36:06.360 align:start position:0% random and people still deploy your 00:36:06.360 --> 00:36:07.940 align:start position:0% random and people still deploy your simply<00:36:06.870> minds<00:36:07.050> without<00:36:07.200> conforming<00:36:07.620> to<00:36:07.800> the 00:36:07.940 --> 00:36:07.950 align:start position:0% simply minds without conforming to the 00:36:07.950 --> 00:36:10.700 align:start position:0% simply minds without conforming to the meditative<00:36:08.310> standard<00:36:08.610> so<00:36:09.240> a<00:36:09.630> lot<00:36:10.320> of<00:36:10.350> folks 00:36:10.700 --> 00:36:10.710 align:start position:0% meditative standard so a lot of folks 00:36:10.710 --> 00:36:14.270 align:start position:0% meditative standard so a lot of folks use<00:36:10.950> our<00:36:11.250> API<00:36:11.690> which<00:36:12.690> is<00:36:12.810> not<00:36:12.960> you<00:36:13.560> know<00:36:13.590> a<00:36:13.680> very 00:36:14.270 --> 00:36:14.280 align:start position:0% use our API which is not you know a very 00:36:14.280 --> 00:36:15.950 align:start position:0% use our API which is not you know a very good<00:36:14.370> thing<00:36:14.760> like<00:36:14.970> we<00:36:15.300> don't<00:36:15.450> want<00:36:15.630> to<00:36:15.690> be<00:36:15.810> the 00:36:15.950 --> 00:36:15.960 align:start position:0% good thing like we don't want to be the 00:36:15.960 --> 00:36:19.400 align:start position:0% good thing like we don't want to be the central<00:36:16.770> point 00:36:19.400 --> 00:36:19.410 align:start position:0% 00:36:19.410 --> 00:36:22.979 align:start position:0% but<00:36:20.430> but<00:36:21.430> yeah<00:36:21.579> if<00:36:21.729> you<00:36:21.759> were<00:36:21.939> building<00:36:22.150> a<00:36:22.630> like 00:36:22.979 --> 00:36:22.989 align:start position:0% but but yeah if you were building a like 00:36:22.989 --> 00:36:27.029 align:start position:0% but but yeah if you were building a like open-source<00:36:23.680> nft<00:36:25.259> aggregator<00:36:26.259> you<00:36:26.920> would 00:36:27.029 --> 00:36:27.039 align:start position:0% open-source nft aggregator you would 00:36:27.039 --> 00:36:28.380 align:start position:0% open-source nft aggregator you would definitely<00:36:27.249> want<00:36:27.519> to<00:36:27.670> support<00:36:27.969> or<00:36:28.209> something 00:36:28.380 --> 00:36:28.390 align:start position:0% definitely want to support or something 00:36:28.390 --> 00:36:37.620 align:start position:0% definitely want to support or something like<00:36:28.599> IVFs<00:36:33.390> so<00:36:34.390> yeah<00:36:34.779> so<00:36:35.219> time<00:36:36.219> for<00:36:37.059> bed 00:36:37.620 --> 00:36:37.630 align:start position:0% like IVFs so yeah so time for bed 00:36:37.630 --> 00:36:43.140 align:start position:0% like IVFs so yeah so time for bed so<00:36:38.589> we<00:36:38.920> do<00:36:39.099> have<00:36:39.369> our<00:36:39.670> GRC<00:36:40.420> 721<00:36:41.170> contract<00:36:42.150> we 00:36:43.140 --> 00:36:43.150 align:start position:0% so we do have our GRC 721 contract we 00:36:43.150 --> 00:36:46.759 align:start position:0% so we do have our GRC 721 contract we can<00:36:43.329> go<00:36:43.539> on<00:36:44.519> rinkeby 00:36:46.759 --> 00:36:46.769 align:start position:0% can go on rinkeby 00:36:46.769 --> 00:36:50.910 align:start position:0% can go on rinkeby ether<00:36:47.769> scan<00:36:48.069> and<00:36:49.059> check<00:36:49.559> it<00:36:50.559> out 00:36:50.910 --> 00:36:50.920 align:start position:0% ether scan and check it out 00:36:50.920 --> 00:36:58.019 align:start position:0% ether scan and check it out I<00:36:50.949> do<00:36:51.339> that<00:36:51.519> exciting<00:36:53.339> and<00:36:55.769> then<00:36:56.819> we<00:36:57.819> could 00:36:58.019 --> 00:36:58.029 align:start position:0% I do that exciting and then we could 00:36:58.029 --> 00:37:03.479 align:start position:0% I do that exciting and then we could admit<00:36:58.269> some<00:36:58.539> items<00:36:58.959> on<00:36:59.109> here<00:36:59.999> so<00:37:02.219> don't<00:37:03.219> worry 00:37:03.479 --> 00:37:03.489 align:start position:0% admit some items on here so don't worry 00:37:03.489 --> 00:37:06.050 align:start position:0% admit some items on here so don't worry this<00:37:03.640> like<00:37:04.259> stuff<00:37:05.259> is<00:37:05.380> not 00:37:06.050 --> 00:37:06.060 align:start position:0% this like stuff is not 00:37:06.060 --> 00:37:12.900 align:start position:0% this like stuff is not go<00:37:06.960> away<00:37:08.690> and 00:37:12.900 --> 00:37:12.910 align:start position:0% 00:37:12.910 --> 00:37:19.590 align:start position:0% so<00:37:13.910> I'm<00:37:14.000> gonna<00:37:14.180> replace<00:37:14.600> this<00:37:14.900> address<00:37:15.380> here 00:37:19.590 --> 00:37:19.600 align:start position:0% 00:37:19.600 --> 00:37:25.570 align:start position:0% and<00:37:20.800> then<00:37:22.960> hopefully<00:37:23.960> if<00:37:24.680> I<00:37:24.830> run<00:37:25.100> the<00:37:25.250> minting 00:37:25.570 --> 00:37:25.580 align:start position:0% and then hopefully if I run the minting 00:37:25.580 --> 00:37:33.600 align:start position:0% and then hopefully if I run the minting script<00:37:30.670> it'll<00:37:31.670> meet<00:37:31.820> some<00:37:32.330> items<00:37:32.690> with<00:37:32.870> that 00:37:33.600 --> 00:37:33.610 align:start position:0% script it'll meet some items with that 00:37:33.610 --> 00:37:41.310 align:start position:0% script it'll meet some items with that metadata<00:37:34.610> that<00:37:34.790> I<00:37:35.030> showed<00:37:35.330> you 00:37:41.310 --> 00:37:41.320 align:start position:0% 00:37:41.320 --> 00:37:46.320 align:start position:0% and<00:37:42.150> after<00:37:43.150> it's<00:37:43.330> done<00:37:43.540> that<00:37:43.830> you<00:37:44.830> can<00:37:45.070> view<00:37:45.880> an 00:37:46.320 --> 00:37:46.330 align:start position:0% and after it's done that you can view an 00:37:46.330 --> 00:37:49.230 align:start position:0% and after it's done that you can view an item<00:37:46.510> on<00:37:47.260> open<00:37:47.590> sea<00:37:47.770> if<00:37:48.340> you<00:37:48.790> just<00:37:49.000> use<00:37:49.210> a 00:37:49.230 --> 00:37:49.240 align:start position:0% item on open sea if you just use a 00:37:49.240 --> 00:37:55.370 align:start position:0% item on open sea if you just use a little<00:37:49.360> bit<00:37:49.600> of<00:37:50.010> URL<00:37:51.900> wizardry<00:37:52.900> by<00:37:53.680> hitting 00:37:55.370 --> 00:37:55.380 align:start position:0% little bit of URL wizardry by hitting 00:37:55.380 --> 00:38:00.060 align:start position:0% little bit of URL wizardry by hitting slash<00:37:56.410> assets<00:37:57.120> slash<00:37:58.410> address<00:37:59.410> slightly 00:38:00.060 --> 00:38:00.070 align:start position:0% slash assets slash address slightly 00:38:00.070 --> 00:38:02.370 align:start position:0% slash assets slash address slightly token<00:38:00.460> I<00:38:00.490> eat<00:38:00.700> I<00:38:00.940> think<00:38:01.660> good<00:38:01.780> to<00:38:01.900> wait<00:38:02.050> for<00:38:02.290> it 00:38:02.370 --> 00:38:02.380 align:start position:0% token I eat I think good to wait for it 00:38:02.380 --> 00:38:22.820 align:start position:0% token I eat I think good to wait for it to<00:38:02.410> deploy<00:38:03.250> so<00:38:03.610> it<00:38:04.360> has<00:38:04.480> minted<00:38:04.870> an<00:38:04.990> item 00:38:22.820 --> 00:38:22.830 align:start position:0% 00:38:22.830 --> 00:38:26.220 align:start position:0% and<00:38:23.830> so<00:38:24.520> it<00:38:25.150> has<00:38:25.300> meant<00:38:25.540> it<00:38:25.690> took<00:38:25.870> an<00:38:25.960> ID<00:38:26.110> number 00:38:26.220 --> 00:38:26.230 align:start position:0% and so it has meant it took an ID number 00:38:26.230 --> 00:38:32.880 align:start position:0% and so it has meant it took an ID number one<00:38:26.740> and<00:38:28.260> now<00:38:29.260> we<00:38:30.040> can<00:38:30.220> go<00:38:30.430> to<00:38:31.740> rinkeby 00:38:32.880 --> 00:38:32.890 align:start position:0% one and now we can go to rinkeby 00:38:32.890 --> 00:38:36.840 align:start position:0% one and now we can go to rinkeby slash<00:38:33.430> one<00:38:33.700> and<00:38:34.120> hopefully<00:38:34.570> it<00:38:35.350> shows<00:38:35.710> show<00:38:36.700> up 00:38:36.840 --> 00:38:36.850 align:start position:0% slash one and hopefully it shows show up 00:38:36.850 --> 00:38:39.900 align:start position:0% slash one and hopefully it shows show up yeah<00:38:37.210> so<00:38:37.450> that's<00:38:37.630> the<00:38:37.810> image<00:38:37.960> I<00:38:38.110> use<00:38:38.670> it<00:38:39.670> was 00:38:39.900 --> 00:38:39.910 align:start position:0% yeah so that's the image I use it was 00:38:39.910 --> 00:38:42.240 align:start position:0% yeah so that's the image I use it was called<00:38:40.120> hello<00:38:40.740> and<00:38:41.740> then<00:38:41.890> some<00:38:42.130> other 00:38:42.240 --> 00:38:42.250 align:start position:0% called hello and then some other 00:38:42.250 --> 00:38:43.620 align:start position:0% called hello and then some other interesting<00:38:42.700> things<00:38:42.880> you<00:38:43.000> can<00:38:43.030> do<00:38:43.210> here<00:38:43.240> are 00:38:43.620 --> 00:38:43.630 align:start position:0% interesting things you can do here are 00:38:43.630 --> 00:38:45.060 align:start position:0% interesting things you can do here are you<00:38:44.050> can<00:38:44.170> immediately<00:38:44.290> put<00:38:44.620> this<00:38:44.740> on<00:38:44.920> sale 00:38:45.060 --> 00:38:45.070 align:start position:0% you can immediately put this on sale 00:38:45.070 --> 00:38:47.990 align:start position:0% you can immediately put this on sale both<00:38:45.910> through<00:38:46.810> the<00:38:46.990> open<00:38:47.170> cui<00:38:47.470> or 00:38:47.990 --> 00:38:48.000 align:start position:0% both through the open cui or 00:38:48.000 --> 00:38:50.460 align:start position:0% both through the open cui or programmatically<00:38:49.000> through<00:38:49.120> our<00:38:49.330> SDK<00:38:49.720> you<00:38:50.320> can 00:38:50.460 --> 00:38:50.470 align:start position:0% programmatically through our SDK you can 00:38:50.470 --> 00:38:53.160 align:start position:0% programmatically through our SDK you can sell<00:38:50.680> it<00:38:50.830> in<00:38:50.950> a<00:38:51.010> different<00:38:51.160> token<00:38:51.610> on<00:38:52.480> on<00:38:52.960> main 00:38:53.160 --> 00:38:53.170 align:start position:0% sell it in a different token on on main 00:38:53.170 --> 00:38:55.140 align:start position:0% sell it in a different token on on main that<00:38:53.320> we<00:38:53.500> support<00:38:53.860> stable<00:38:54.370> point<00:38:54.580> sounds<00:38:55.030> like 00:38:55.140 --> 00:38:55.150 align:start position:0% that we support stable point sounds like 00:38:55.150 --> 00:38:57.060 align:start position:0% that we support stable point sounds like that<00:38:55.330> on<00:38:55.870> test<00:38:56.290> night<00:38:56.440> we<00:38:56.530> use<00:38:56.650> it<00:38:56.800> for<00:38:56.950> this 00:38:57.060 --> 00:38:57.070 align:start position:0% that on test night we use it for this 00:38:57.070 --> 00:38:59.970 align:start position:0% that on test night we use it for this test<00:38:57.400> token<00:38:57.870> you<00:38:58.870> could<00:38:59.050> create<00:38:59.500> sort<00:38:59.800> of<00:38:59.860> a 00:38:59.970 --> 00:38:59.980 align:start position:0% test token you could create sort of a 00:38:59.980 --> 00:39:01.800 align:start position:0% test token you could create sort of a Dutch<00:39:00.190> auction<00:39:00.460> where<00:39:00.940> you<00:39:01.060> started<00:39:01.570> at<00:39:01.780> a 00:39:01.800 --> 00:39:01.810 align:start position:0% Dutch auction where you started at a 00:39:01.810 --> 00:39:04.140 align:start position:0% Dutch auction where you started at a certain<00:39:02.200> price<00:39:02.380> ended<00:39:02.800> another<00:39:03.010> price<00:39:03.310> you 00:39:04.140 --> 00:39:04.150 align:start position:0% certain price ended another price you 00:39:04.150 --> 00:39:06.690 align:start position:0% certain price ended another price you could<00:39:04.300> create<00:39:04.480> a<00:39:04.600> private<00:39:04.960> sale<00:39:05.400> eBay<00:39:06.400> style 00:39:06.690 --> 00:39:06.700 align:start position:0% could create a private sale eBay style 00:39:06.700 --> 00:39:09.210 align:start position:0% could create a private sale eBay style auction<00:39:07.210> you<00:39:07.780> can<00:39:07.930> bundle<00:39:08.140> it<00:39:08.350> together<00:39:08.440> with 00:39:09.210 --> 00:39:09.220 align:start position:0% auction you can bundle it together with 00:39:09.220 --> 00:39:14.130 align:start position:0% auction you can bundle it together with other<00:39:09.940> entities<00:39:12.270> any<00:39:13.270> even<00:39:13.690> from<00:39:13.960> other 00:39:14.130 --> 00:39:14.140 align:start position:0% other entities any even from other 00:39:14.140 --> 00:39:16.010 align:start position:0% other entities any even from other contracts<00:39:14.740> and<00:39:15.070> things<00:39:15.340> like<00:39:15.430> that 00:39:16.010 --> 00:39:16.020 align:start position:0% contracts and things like that 00:39:16.020 --> 00:39:18.480 align:start position:0% contracts and things like that so<00:39:17.020> there's<00:39:17.200> all<00:39:17.320> these<00:39:17.440> things<00:39:17.770> you<00:39:18.430> can 00:39:18.480 --> 00:39:18.490 align:start position:0% so there's all these things you can 00:39:18.490 --> 00:39:21.540 align:start position:0% so there's all these things you can immediately<00:39:18.760> do<00:39:19.600> with<00:39:19.750> it<00:39:19.900> and<00:39:20.080> you<00:39:21.040> can<00:39:21.280> see 00:39:21.540 --> 00:39:21.550 align:start position:0% immediately do with it and you can see 00:39:21.550 --> 00:39:24.750 align:start position:0% immediately do with it and you can see the<00:39:21.730> history<00:39:22.120> for<00:39:22.900> it<00:39:23.050> so<00:39:23.320> it<00:39:23.920> was<00:39:24.070> born<00:39:24.370> a 00:39:24.750 --> 00:39:24.760 align:start position:0% the history for it so it was born a 00:39:24.760 --> 00:39:30.600 align:start position:0% the history for it so it was born a minute<00:39:25.360> ago<00:39:25.570> to<00:39:25.810> my<00:39:26.650> accountant<00:39:27.210> and<00:39:29.250> lastly<00:39:30.250> I 00:39:30.600 --> 00:39:30.610 align:start position:0% minute ago to my accountant and lastly I 00:39:30.610 --> 00:39:33.270 align:start position:0% minute ago to my accountant and lastly I think<00:39:31.270> I'm<00:39:31.480> running<00:39:31.570> out<00:39:31.690> of<00:39:31.780> time 00:39:33.270 --> 00:39:33.280 align:start position:0% think I'm running out of time 00:39:33.280 --> 00:39:36.390 align:start position:0% think I'm running out of time you<00:39:33.730> can<00:39:34.000> configure<00:39:34.810> this<00:39:35.320> so<00:39:35.650> you<00:39:35.710> get<00:39:35.980> a<00:39:36.010> free 00:39:36.390 --> 00:39:36.400 align:start position:0% you can configure this so you get a free 00:39:36.400 --> 00:39:38.370 align:start position:0% you can configure this so you get a free storefront<00:39:36.970> so<00:39:37.210> deployed<00:39:38.020> a<00:39:38.050> lot<00:39:38.260> of 00:39:38.370 --> 00:39:38.380 align:start position:0% storefront so deployed a lot of 00:39:38.380 --> 00:39:41.460 align:start position:0% storefront so deployed a lot of contracts<00:39:38.890> called<00:39:39.100> creature<00:39:39.340> but<00:39:40.470> assets 00:39:41.460 --> 00:39:41.470 align:start position:0% contracts called creature but assets 00:39:41.470 --> 00:39:44.370 align:start position:0% contracts called creature but assets slash<00:39:41.680> creature<00:39:42.040> -<00:39:42.280> 49<00:39:42.930> and<00:39:43.930> you<00:39:44.110> can<00:39:44.260> actually 00:39:44.370 --> 00:39:44.380 align:start position:0% slash creature - 49 and you can actually 00:39:44.380 --> 00:39:46.830 align:start position:0% slash creature - 49 and you can actually edit<00:39:44.920> this<00:39:45.190> storefront<00:39:45.430> and<00:39:45.880> what's<00:39:46.210> what's 00:39:46.830 --> 00:39:46.840 align:start position:0% edit this storefront and what's what's 00:39:46.840 --> 00:39:48.420 align:start position:0% edit this storefront and what's what's interesting<00:39:47.020> here<00:39:47.380> is<00:39:47.440> we<00:39:47.680> use<00:39:47.890> the<00:39:48.100> ownable 00:39:48.420 --> 00:39:48.430 align:start position:0% interesting here is we use the ownable 00:39:48.430 --> 00:39:53.610 align:start position:0% interesting here is we use the ownable owner<00:39:48.880> of<00:39:49.320> the<00:39:50.320> contract<00:39:51.040> to<00:39:52.260> permission<00:39:53.260> who 00:39:53.610 --> 00:39:53.620 align:start position:0% owner of the contract to permission who 00:39:53.620 --> 00:39:56.160 align:start position:0% owner of the contract to permission who can<00:39:53.830> edit<00:39:53.980> their<00:39:54.340> storefront<00:39:55.240> so<00:39:55.510> I<00:39:55.780> gotta 00:39:56.160 --> 00:39:56.170 align:start position:0% can edit their storefront so I gotta 00:39:56.170 --> 00:39:58.540 align:start position:0% can edit their storefront so I gotta edit<00:39:56.290> storefront 00:39:58.540 --> 00:39:58.550 align:start position:0% edit storefront 00:39:58.550 --> 00:40:02.410 align:start position:0% edit storefront I<00:39:58.580> can<00:39:58.820> add<00:39:59.120> a<00:39:59.420> image<00:40:00.200> for<00:40:00.710> the<00:40:00.830> storefront<00:40:01.420> and 00:40:02.410 --> 00:40:02.420 align:start position:0% I can add a image for the storefront and 00:40:02.420 --> 00:40:05.620 align:start position:0% I can add a image for the storefront and description<00:40:03.200> and<00:40:03.500> then<00:40:03.980> my<00:40:04.850> marketplace<00:40:05.210> fees 00:40:05.620 --> 00:40:05.630 align:start position:0% description and then my marketplace fees 00:40:05.630 --> 00:40:07.240 align:start position:0% description and then my marketplace fees which<00:40:05.960> are<00:40:06.200> basically<00:40:06.470> whenever<00:40:06.830> something 00:40:07.240 --> 00:40:07.250 align:start position:0% which are basically whenever something 00:40:07.250 --> 00:40:11.050 align:start position:0% which are basically whenever something sells<00:40:08.290> I'll<00:40:09.290> take<00:40:09.560> that<00:40:09.710> a<00:40:09.770> cut<00:40:10.040> of<00:40:10.310> the<00:40:10.670> sales 00:40:11.050 --> 00:40:11.060 align:start position:0% sells I'll take that a cut of the sales 00:40:11.060 --> 00:40:14.470 align:start position:0% sells I'll take that a cut of the sales to<00:40:11.480> group<00:40:11.990> a<00:40:12.140> payout<00:40:12.530> address<00:40:13.060> and<00:40:14.060> a<00:40:14.240> little 00:40:14.470 --> 00:40:14.480 align:start position:0% to group a payout address and a little 00:40:14.480 --> 00:40:24.760 align:start position:0% to group a payout address and a little bit<00:40:14.600> around<00:40:15.340> how<00:40:16.340> the<00:40:16.400> items<00:40:16.910> are<00:40:17.060> displayed 00:40:24.760 --> 00:40:24.770 align:start position:0% 00:40:24.770 --> 00:40:33.440 align:start position:0% any<00:40:25.770> any<00:40:26.280> last<00:40:26.550> minute<00:40:26.700> questions 00:40:33.440 --> 00:40:33.450 align:start position:0% 00:40:33.450 --> 00:40:37.450 align:start position:0% all<00:40:33.930> right<00:40:34.079> thanks<00:40:34.319> so<00:40:34.380> much 00:40:37.450 --> 00:40:37.460 align:start position:0% 00:40:37.460 --> 00:40:43.789 align:start position:0% [Applause]