WEBVTT Kind: captions Language: en 00:00:00.000 --> 00:00:04.350 align:start position:0% foreign 00:00:04.350 --> 00:00:04.360 align:start position:0% 00:00:04.360 --> 00:00:13.509 align:start position:0% [Music] 00:00:13.509 --> 00:00:13.519 align:start position:0% 00:00:13.519 --> 00:00:16.010 align:start position:0% Annette<00:00:14.519> is<00:00:14.820> currently<00:00:15.120> still<00:00:15.360> in<00:00:15.599> a<00:00:15.780> podcast 00:00:16.010 --> 00:00:16.020 align:start position:0% Annette is currently still in a podcast 00:00:16.020 --> 00:00:18.710 align:start position:0% Annette is currently still in a podcast interview<00:00:16.680> but<00:00:17.039> I<00:00:17.220> think<00:00:17.340> she<00:00:17.520> will<00:00:17.699> come<00:00:17.880> also 00:00:18.710 --> 00:00:18.720 align:start position:0% interview but I think she will come also 00:00:18.720 --> 00:00:19.689 align:start position:0% interview but I think she will come also later 00:00:19.689 --> 00:00:19.699 align:start position:0% later 00:00:19.699 --> 00:00:22.609 align:start position:0% later I'm<00:00:20.699> quickly<00:00:21.060> gonna<00:00:21.359> give<00:00:21.840> an<00:00:22.020> overview<00:00:22.320> of 00:00:22.609 --> 00:00:22.619 align:start position:0% I'm quickly gonna give an overview of 00:00:22.619 --> 00:00:25.189 align:start position:0% I'm quickly gonna give an overview of what's<00:00:23.279> going<00:00:23.520> to<00:00:23.640> happen<00:00:23.760> in<00:00:24.119> the<00:00:24.240> next<00:00:24.420> I 00:00:25.189 --> 00:00:25.199 align:start position:0% what's going to happen in the next I 00:00:25.199 --> 00:00:26.890 align:start position:0% what's going to happen in the next I think<00:00:25.380> we<00:00:25.680> have<00:00:25.800> like<00:00:25.980> one<00:00:26.160> and<00:00:26.340> a<00:00:26.519> half<00:00:26.519> hours 00:00:26.890 --> 00:00:26.900 align:start position:0% think we have like one and a half hours 00:00:26.900 --> 00:00:29.650 align:start position:0% think we have like one and a half hours you<00:00:27.900> can<00:00:27.960> already<00:00:28.140> see<00:00:28.500> a<00:00:28.680> bit<00:00:28.800> on<00:00:29.039> my<00:00:29.279> like 00:00:29.650 --> 00:00:29.660 align:start position:0% you can already see a bit on my like 00:00:29.660 --> 00:00:32.089 align:start position:0% you can already see a bit on my like drawn<00:00:30.660> slides<00:00:31.019> I<00:00:31.199> don't<00:00:31.320> like<00:00:31.439> PowerPoint 00:00:32.089 --> 00:00:32.099 align:start position:0% drawn slides I don't like PowerPoint 00:00:32.099 --> 00:00:33.650 align:start position:0% drawn slides I don't like PowerPoint that<00:00:32.340> much 00:00:33.650 --> 00:00:33.660 align:start position:0% that much 00:00:33.660 --> 00:00:36.830 align:start position:0% that much um<00:00:33.719> like<00:00:34.620> what<00:00:35.280> will<00:00:35.460> be<00:00:35.640> the<00:00:36.059> what<00:00:36.540> will<00:00:36.719> be 00:00:36.830 --> 00:00:36.840 align:start position:0% um like what will be the what will be 00:00:36.840 --> 00:00:39.170 align:start position:0% um like what will be the what will be essentially<00:00:37.200> like<00:00:37.440> the<00:00:37.680> the<00:00:37.980> the<00:00:38.520> content<00:00:39.000> of 00:00:39.170 --> 00:00:39.180 align:start position:0% essentially like the the the content of 00:00:39.180 --> 00:00:43.250 align:start position:0% essentially like the the the content of of<00:00:39.480> this<00:00:39.780> entire<00:00:40.079> session<00:00:40.520> we<00:00:41.520> have<00:00:41.840> uh<00:00:42.840> lined 00:00:43.250 --> 00:00:43.260 align:start position:0% of this entire session we have uh lined 00:00:43.260 --> 00:00:47.030 align:start position:0% of this entire session we have uh lined up<00:00:43.640> as<00:00:44.640> like<00:00:45.059> six<00:00:45.719> seven<00:00:45.960> speakers<00:00:46.320> including 00:00:47.030 --> 00:00:47.040 align:start position:0% up as like six seven speakers including 00:00:47.040 --> 00:00:48.290 align:start position:0% up as like six seven speakers including me 00:00:48.290 --> 00:00:48.300 align:start position:0% me 00:00:48.300 --> 00:00:51.049 align:start position:0% me um<00:00:48.360> we<00:00:49.200> are<00:00:49.500> going<00:00:49.680> to<00:00:49.920> Center<00:00:50.160> all<00:00:50.520> of<00:00:50.700> these 00:00:51.049 --> 00:00:51.059 align:start position:0% um we are going to Center all of these 00:00:51.059 --> 00:00:54.110 align:start position:0% um we are going to Center all of these talks<00:00:51.719> Around<00:00:51.899> The<00:00:52.320> ethereum<00:00:52.739> Magicians<00:00:53.340> and 00:00:54.110 --> 00:00:54.120 align:start position:0% talks Around The ethereum Magicians and 00:00:54.120 --> 00:00:57.590 align:start position:0% talks Around The ethereum Magicians and specifically<00:00:54.719> we're<00:00:55.500> going<00:00:55.680> to<00:00:55.800> talk<00:00:55.980> about 00:00:57.590 --> 00:00:57.600 align:start position:0% specifically we're going to talk about 00:00:57.600 --> 00:01:00.709 align:start position:0% specifically we're going to talk about um<00:00:57.660> ERC<00:00:58.440> proposals<00:00:59.219> so<00:00:59.399> ethereum<00:01:00.059> request<00:01:00.360> for 00:01:00.709 --> 00:01:00.719 align:start position:0% um ERC proposals so ethereum request for 00:01:00.719 --> 00:01:03.709 align:start position:0% um ERC proposals so ethereum request for uh<00:01:01.320> for<00:01:01.559> for<00:01:01.739> comments<00:01:02.340> right<00:01:02.520> so<00:01:02.940> basically 00:01:03.709 --> 00:01:03.719 align:start position:0% uh for for comments right so basically 00:01:03.719 --> 00:01:06.350 align:start position:0% uh for for comments right so basically everything<00:01:04.019> that<00:01:04.379> didn't<00:01:04.559> fit<00:01:04.920> into<00:01:05.360> uh 00:01:06.350 --> 00:01:06.360 align:start position:0% everything that didn't fit into uh 00:01:06.360 --> 00:01:09.530 align:start position:0% everything that didn't fit into uh Annette<00:01:06.840> and<00:01:07.080> Tim<00:01:07.380> bico's<00:01:08.159> earlier<00:01:08.820> session<00:01:09.180> I 00:01:09.530 --> 00:01:09.540 align:start position:0% Annette and Tim bico's earlier session I 00:01:09.540 --> 00:01:12.050 align:start position:0% Annette and Tim bico's earlier session I think<00:01:09.600> like<00:01:09.780> it<00:01:10.020> was<00:01:10.200> about<00:01:10.500> two<00:01:11.100> weeks<00:01:11.640> two 00:01:12.050 --> 00:01:12.060 align:start position:0% think like it was about two weeks two 00:01:12.060 --> 00:01:15.890 align:start position:0% think like it was about two weeks two days<00:01:12.240> ago<00:01:12.860> about<00:01:13.860> the<00:01:14.159> ethereum<00:01:14.640> core<00:01:14.939> roadmap 00:01:15.890 --> 00:01:15.900 align:start position:0% days ago about the ethereum core roadmap 00:01:15.900 --> 00:01:19.490 align:start position:0% days ago about the ethereum core roadmap so<00:01:16.680> how<00:01:17.580> this<00:01:17.760> works<00:01:18.119> each<00:01:18.780> speaker<00:01:19.020> has 00:01:19.490 --> 00:01:19.500 align:start position:0% so how this works each speaker has 00:01:19.500 --> 00:01:22.010 align:start position:0% so how this works each speaker has roughly<00:01:20.040> 15<00:01:20.759> minutes<00:01:21.060> and<00:01:21.299> then<00:01:21.479> we<00:01:21.659> have<00:01:21.780> a 00:01:22.010 --> 00:01:22.020 align:start position:0% roughly 15 minutes and then we have a 00:01:22.020 --> 00:01:24.109 align:start position:0% roughly 15 minutes and then we have a usually<00:01:22.619> like<00:01:22.799> a<00:01:22.979> five<00:01:23.159> minute<00:01:23.340> break<00:01:23.700> where 00:01:24.109 --> 00:01:24.119 align:start position:0% usually like a five minute break where 00:01:24.119 --> 00:01:26.289 align:start position:0% usually like a five minute break where we<00:01:24.600> can<00:01:24.659> set<00:01:24.840> up<00:01:25.020> the<00:01:25.140> next<00:01:25.259> speaker 00:01:26.289 --> 00:01:26.299 align:start position:0% we can set up the next speaker 00:01:26.299 --> 00:01:28.550 align:start position:0% we can set up the next speaker and<00:01:27.299> maybe<00:01:27.479> there's<00:01:27.720> even<00:01:28.020> like<00:01:28.200> time<00:01:28.380> for 00:01:28.550 --> 00:01:28.560 align:start position:0% and maybe there's even like time for 00:01:28.560 --> 00:01:31.609 align:start position:0% and maybe there's even like time for questions<00:01:28.799> I<00:01:29.159> guess<00:01:29.840> we<00:01:30.840> will<00:01:31.020> have<00:01:31.320> some 00:01:31.609 --> 00:01:31.619 align:start position:0% questions I guess we will have some 00:01:31.619 --> 00:01:35.030 align:start position:0% questions I guess we will have some talks<00:01:32.040> about<00:01:32.540> timestamps<00:01:33.540> in<00:01:33.960> ethereum<00:01:34.860> get 00:01:35.030 --> 00:01:35.040 align:start position:0% talks about timestamps in ethereum get 00:01:35.040 --> 00:01:37.609 align:start position:0% talks about timestamps in ethereum get locks<00:01:35.460> from<00:01:36.060> Ronin<00:01:36.659> that<00:01:36.900> just<00:01:37.200> entered<00:01:37.500> the 00:01:37.609 --> 00:01:37.619 align:start position:0% locks from Ronin that just entered the 00:01:37.619 --> 00:01:40.249 align:start position:0% locks from Ronin that just entered the room<00:01:37.740> by<00:01:37.979> chance<00:01:38.479> we<00:01:39.479> will<00:01:39.659> have<00:01:39.780> some<00:01:39.960> talks 00:01:40.249 --> 00:01:40.259 align:start position:0% room by chance we will have some talks 00:01:40.259 --> 00:01:44.270 align:start position:0% room by chance we will have some talks about<00:01:40.820> Soul<00:01:41.820> Bond<00:01:42.119> tokens<00:01:42.600> about<00:01:43.079> music<00:01:43.380> nfts 00:01:44.270 --> 00:01:44.280 align:start position:0% about Soul Bond tokens about music nfts 00:01:44.280 --> 00:01:47.929 align:start position:0% about Soul Bond tokens about music nfts about<00:01:45.119> yeah<00:01:45.420> d-soc<00:01:46.159> we<00:01:47.159> will<00:01:47.280> have<00:01:47.460> two<00:01:47.700> people 00:01:47.929 --> 00:01:47.939 align:start position:0% about yeah d-soc we will have two people 00:01:47.939 --> 00:01:50.990 align:start position:0% about yeah d-soc we will have two people speaking<00:01:48.360> about<00:01:48.500> the<00:01:49.500> the<00:01:49.619> problems<00:01:50.220> in<00:01:50.880> the 00:01:50.990 --> 00:01:51.000 align:start position:0% speaking about the the problems in the 00:01:51.000 --> 00:01:52.690 align:start position:0% speaking about the the problems in the web<00:01:51.180> 3<00:01:51.420> music<00:01:51.720> space 00:01:52.690 --> 00:01:52.700 align:start position:0% web 3 music space 00:01:52.700 --> 00:01:56.270 align:start position:0% web 3 music space about<00:01:53.700> content<00:01:54.180> types<00:01:54.540> in<00:01:54.780> in<00:01:55.079> nfts<00:01:55.860> and<00:01:56.100> then 00:01:56.270 --> 00:01:56.280 align:start position:0% about content types in in nfts and then 00:01:56.280 --> 00:02:00.130 align:start position:0% about content types in in nfts and then we'll<00:01:57.060> also<00:01:57.420> have<00:01:57.780> a<00:01:58.560> a<00:01:58.920> very<00:01:59.220> recent<00:01:59.520> EIP 00:02:00.130 --> 00:02:00.140 align:start position:0% we'll also have a a very recent EIP 00:02:00.140 --> 00:02:03.770 align:start position:0% we'll also have a a very recent EIP namely<00:02:01.140> I<00:02:01.680> think<00:02:01.799> it's<00:02:02.159> for<00:02:02.520> the<00:02:03.240> domain 00:02:03.770 --> 00:02:03.780 align:start position:0% namely I think it's for the domain 00:02:03.780 --> 00:02:09.469 align:start position:0% namely I think it's for the domain separator<00:02:04.500> in<00:02:05.040> EIP<00:02:06.200> 712<00:02:07.200> so 00:02:09.469 --> 00:02:09.479 align:start position:0% separator in EIP 712 so 00:02:09.479 --> 00:02:13.010 align:start position:0% separator in EIP 712 so um<00:02:09.500> I<00:02:10.500> I<00:02:10.679> wanna<00:02:10.979> I<00:02:11.160> Wanna<00:02:11.340> Give<00:02:11.599> before<00:02:12.599> like<00:02:12.840> we 00:02:13.010 --> 00:02:13.020 align:start position:0% um I I wanna I Wanna Give before like we 00:02:13.020 --> 00:02:14.690 align:start position:0% um I I wanna I Wanna Give before like we start<00:02:13.200> with<00:02:13.379> the<00:02:13.560> speakers<00:02:13.739> I<00:02:14.220> think<00:02:14.340> I<00:02:14.580> wanna 00:02:14.690 --> 00:02:14.700 align:start position:0% start with the speakers I think I wanna 00:02:14.700 --> 00:02:17.210 align:start position:0% start with the speakers I think I wanna I<00:02:15.000> Wanna<00:02:15.180> Give<00:02:15.420> a<00:02:15.660> quick<00:02:16.140> talk<00:02:16.379> myself<00:02:16.739> though 00:02:17.210 --> 00:02:17.220 align:start position:0% I Wanna Give a quick talk myself though 00:02:17.220 --> 00:02:18.770 align:start position:0% I Wanna Give a quick talk myself though kind<00:02:17.700> of<00:02:17.879> kind<00:02:18.000> of<00:02:18.120> like<00:02:18.239> my<00:02:18.480> own<00:02:18.599> like 00:02:18.770 --> 00:02:18.780 align:start position:0% kind of kind of like my own like 00:02:18.780 --> 00:02:21.949 align:start position:0% kind of kind of like my own like lightning<00:02:19.379> talk<00:02:19.560> and<00:02:20.400> and<00:02:20.640> it<00:02:20.879> I<00:02:21.300> want<00:02:21.420> to<00:02:21.599> make 00:02:21.949 --> 00:02:21.959 align:start position:0% lightning talk and and it I want to make 00:02:21.959 --> 00:02:24.530 align:start position:0% lightning talk and and it I want to make it<00:02:22.140> about<00:02:22.319> kind<00:02:23.160> of<00:02:23.280> this<00:02:23.580> weird<00:02:23.940> thing<00:02:24.180> that 00:02:24.530 --> 00:02:24.540 align:start position:0% it about kind of this weird thing that 00:02:24.540 --> 00:02:26.630 align:start position:0% it about kind of this weird thing that the<00:02:24.720> ercs<00:02:25.440> are<00:02:25.620> which<00:02:25.860> are<00:02:26.040> essentially<00:02:26.459> just 00:02:26.630 --> 00:02:26.640 align:start position:0% the ercs are which are essentially just 00:02:26.640 --> 00:02:29.030 align:start position:0% the ercs are which are essentially just like<00:02:27.060> immutable 00:02:29.030 --> 00:02:29.040 align:start position:0% like immutable 00:02:29.040 --> 00:02:31.850 align:start position:0% like immutable um<00:02:29.099> contracts<00:02:30.060> that<00:02:30.360> are<00:02:30.480> almost<00:02:30.780> like<00:02:31.260> as 00:02:31.850 --> 00:02:31.860 align:start position:0% um contracts that are almost like as 00:02:31.860 --> 00:02:34.670 align:start position:0% um contracts that are almost like as immutable<00:02:32.400> as<00:02:32.840> uh<00:02:33.840> a<00:02:34.140> transaction<00:02:34.440> in 00:02:34.670 --> 00:02:34.680 align:start position:0% immutable as uh a transaction in 00:02:34.680 --> 00:02:37.790 align:start position:0% immutable as uh a transaction in ethereum<00:02:35.160> and<00:02:36.060> uh<00:02:36.780> the<00:02:37.020> problem<00:02:37.200> that<00:02:37.560> comes 00:02:37.790 --> 00:02:37.800 align:start position:0% ethereum and uh the problem that comes 00:02:37.800 --> 00:02:40.610 align:start position:0% ethereum and uh the problem that comes with<00:02:37.920> it<00:02:38.040> which<00:02:38.400> is<00:02:38.580> that<00:02:39.300> like<00:02:40.260> we<00:02:40.500> don't 00:02:40.610 --> 00:02:40.620 align:start position:0% with it which is that like we don't 00:02:40.620 --> 00:02:43.550 align:start position:0% with it which is that like we don't really<00:02:40.860> know<00:02:41.040> how<00:02:41.280> to<00:02:41.459> upgrade<00:02:41.819> them<00:02:42.140> and<00:02:43.140> you 00:02:43.550 --> 00:02:43.560 align:start position:0% really know how to upgrade them and you 00:02:43.560 --> 00:02:46.250 align:start position:0% really know how to upgrade them and you know<00:02:43.620> throughout<00:02:44.280> this<00:02:44.580> whole<00:02:44.879> year<00:02:45.599> of<00:02:45.959> you 00:02:46.250 --> 00:02:46.260 align:start position:0% know throughout this whole year of you 00:02:46.260 --> 00:02:47.630 align:start position:0% know throughout this whole year of you know<00:02:46.319> bull<00:02:46.560> market<00:02:46.860> and<00:02:47.160> and<00:02:47.400> everything 00:02:47.630 --> 00:02:47.640 align:start position:0% know bull market and and everything 00:02:47.640 --> 00:02:50.869 align:start position:0% know bull market and and everything especially<00:02:48.239> in<00:02:48.480> the<00:02:48.660> uh<00:02:49.319> nft<00:02:49.620> eco<00:02:50.220> nft 00:02:50.869 --> 00:02:50.879 align:start position:0% especially in the uh nft eco nft 00:02:50.879 --> 00:02:54.050 align:start position:0% especially in the uh nft eco nft ecosystem<00:02:51.480> I<00:02:52.319> think<00:02:52.920> um<00:02:52.980> you<00:02:53.280> know<00:02:53.400> there<00:02:53.640> was 00:02:54.050 --> 00:02:54.060 align:start position:0% ecosystem I think um you know there was 00:02:54.060 --> 00:02:56.030 align:start position:0% ecosystem I think um you know there was a<00:02:54.239> there<00:02:54.599> there's<00:02:55.019> starting<00:02:55.319> to<00:02:55.560> be<00:02:55.800> this 00:02:56.030 --> 00:02:56.040 align:start position:0% a there there's starting to be this 00:02:56.040 --> 00:02:58.490 align:start position:0% a there there's starting to be this debate<00:02:56.459> basically<00:02:56.940> around<00:02:57.239> like<00:02:57.599> how<00:02:58.140> can<00:02:58.319> we 00:02:58.490 --> 00:02:58.500 align:start position:0% debate basically around like how can we 00:02:58.500 --> 00:03:01.070 align:start position:0% debate basically around like how can we actually<00:02:58.680> do<00:02:58.920> Innovation<00:02:59.480> with<00:03:00.480> these<00:03:00.840> uh 00:03:01.070 --> 00:03:01.080 align:start position:0% actually do Innovation with these uh 00:03:01.080 --> 00:03:02.449 align:start position:0% actually do Innovation with these uh contracts<00:03:01.500> if<00:03:01.620> you<00:03:01.800> cannot<00:03:02.040> change<00:03:02.220> them 00:03:02.449 --> 00:03:02.459 align:start position:0% contracts if you cannot change them 00:03:02.459 --> 00:03:04.850 align:start position:0% contracts if you cannot change them anymore<00:03:02.700> right<00:03:03.120> and<00:03:03.599> so<00:03:03.720> like<00:03:04.019> what<00:03:04.379> can<00:03:04.560> we<00:03:04.739> do 00:03:04.850 --> 00:03:04.860 align:start position:0% anymore right and so like what can we do 00:03:04.860 --> 00:03:07.190 align:start position:0% anymore right and so like what can we do about<00:03:05.040> it<00:03:05.340> and<00:03:05.940> I've<00:03:06.120> tried<00:03:06.420> to<00:03:06.599> kind<00:03:06.959> of<00:03:07.019> like 00:03:07.190 --> 00:03:07.200 align:start position:0% about it and I've tried to kind of like 00:03:07.200 --> 00:03:09.589 align:start position:0% about it and I've tried to kind of like Express<00:03:07.980> that<00:03:08.459> where<00:03:08.760> you<00:03:09.060> know<00:03:09.120> like<00:03:09.300> this 00:03:09.589 --> 00:03:09.599 align:start position:0% Express that where you know like this 00:03:09.599 --> 00:03:12.350 align:start position:0% Express that where you know like this contract<00:03:09.959> uh<00:03:10.920> this<00:03:11.159> this<00:03:11.519> document<00:03:12.120> this 00:03:12.350 --> 00:03:12.360 align:start position:0% contract uh this this document this 00:03:12.360 --> 00:03:15.170 align:start position:0% contract uh this this document this proposal<00:03:12.780> that<00:03:13.080> once<00:03:13.800> you<00:03:14.040> once<00:03:14.760> you<00:03:14.879> put<00:03:15.000> it 00:03:15.170 --> 00:03:15.180 align:start position:0% proposal that once you once you put it 00:03:15.180 --> 00:03:18.410 align:start position:0% proposal that once you once you put it into<00:03:15.360> the<00:03:15.720> the<00:03:16.319> final<00:03:16.620> status<00:03:17.099> then<00:03:17.640> it's 00:03:18.410 --> 00:03:18.420 align:start position:0% into the the final status then it's 00:03:18.420 --> 00:03:20.270 align:start position:0% into the the final status then it's really<00:03:18.599> like<00:03:18.900> locked<00:03:19.440> like<00:03:19.680> this<00:03:19.860> like<00:03:20.099> this 00:03:20.270 --> 00:03:20.280 align:start position:0% really like locked like this like this 00:03:20.280 --> 00:03:21.949 align:start position:0% really like locked like this like this locker<00:03:20.640> and<00:03:20.760> we<00:03:20.879> can't<00:03:21.060> really<00:03:21.300> unlock<00:03:21.659> it 00:03:21.949 --> 00:03:21.959 align:start position:0% locker and we can't really unlock it 00:03:21.959 --> 00:03:24.350 align:start position:0% locker and we can't really unlock it anymore<00:03:22.200> and<00:03:22.620> so<00:03:22.860> we<00:03:23.400> have<00:03:23.519> to<00:03:23.640> find<00:03:23.819> ways<00:03:24.180> of 00:03:24.350 --> 00:03:24.360 align:start position:0% anymore and so we have to find ways of 00:03:24.360 --> 00:03:25.070 align:start position:0% anymore and so we have to find ways of like 00:03:25.070 --> 00:03:25.080 align:start position:0% like 00:03:25.080 --> 00:03:27.229 align:start position:0% like still<00:03:25.500> upgrading<00:03:26.099> it<00:03:26.220> and<00:03:26.700> that's<00:03:26.879> that's 00:03:27.229 --> 00:03:27.239 align:start position:0% still upgrading it and that's that's 00:03:27.239 --> 00:03:30.229 align:start position:0% still upgrading it and that's that's what<00:03:27.540> I<00:03:27.720> I<00:03:28.200> want<00:03:29.099> to<00:03:29.280> try<00:03:29.400> to<00:03:29.580> motivate<00:03:30.060> that 00:03:30.229 --> 00:03:30.239 align:start position:0% what I I want to try to motivate that 00:03:30.239 --> 00:03:31.910 align:start position:0% what I I want to try to motivate that actually<00:03:30.480> and<00:03:30.780> I<00:03:30.900> want<00:03:31.019> to<00:03:31.200> try<00:03:31.440> to<00:03:31.620> make<00:03:31.739> like 00:03:31.910 --> 00:03:31.920 align:start position:0% actually and I want to try to make like 00:03:31.920 --> 00:03:33.290 align:start position:0% actually and I want to try to make like an<00:03:32.099> optimistic<00:03:32.580> case<00:03:32.760> for<00:03:33.000> what<00:03:33.180> it's 00:03:33.290 --> 00:03:33.300 align:start position:0% an optimistic case for what it's 00:03:33.300 --> 00:03:34.910 align:start position:0% an optimistic case for what it's actually<00:03:33.420> cool 00:03:34.910 --> 00:03:34.920 align:start position:0% actually cool 00:03:34.920 --> 00:03:36.589 align:start position:0% actually cool so 00:03:36.589 --> 00:03:36.599 align:start position:0% so 00:03:36.599 --> 00:03:38.630 align:start position:0% so but<00:03:37.319> first<00:03:37.620> of<00:03:37.800> all<00:03:37.920> I<00:03:38.099> think<00:03:38.220> we<00:03:38.340> have<00:03:38.459> to 00:03:38.630 --> 00:03:38.640 align:start position:0% but first of all I think we have to 00:03:38.640 --> 00:03:40.670 align:start position:0% but first of all I think we have to backtrack<00:03:39.180> a<00:03:39.420> bit<00:03:39.540> and<00:03:39.780> and<00:03:39.959> this<00:03:40.200> so<00:03:40.379> this<00:03:40.620> is 00:03:40.670 --> 00:03:40.680 align:start position:0% backtrack a bit and and this so this is 00:03:40.680 --> 00:03:43.729 align:start position:0% backtrack a bit and and this so this is a<00:03:40.799> comment<00:03:41.099> from<00:03:41.459> uh<00:03:42.299> I<00:03:42.599> believe<00:03:42.720> the<00:03:43.319> the 00:03:43.729 --> 00:03:43.739 align:start position:0% a comment from uh I believe the the 00:03:43.739 --> 00:03:48.949 align:start position:0% a comment from uh I believe the the GitHub<00:03:44.159> thread<00:03:44.640> on<00:03:45.360> Erp<00:03:46.340> 2612<00:03:47.340> the<00:03:47.940> uh<00:03:48.720> the<00:03:48.959> the 00:03:48.949 --> 00:03:48.959 align:start position:0% GitHub thread on Erp 2612 the uh the the 00:03:48.959 --> 00:03:51.289 align:start position:0% GitHub thread on Erp 2612 the uh the the permit<00:03:49.560> standard<00:03:50.220> that<00:03:50.819> allows<00:03:51.180> you 00:03:51.289 --> 00:03:51.299 align:start position:0% permit standard that allows you 00:03:51.299 --> 00:03:53.589 align:start position:0% permit standard that allows you basically<00:03:51.900> it's<00:03:52.080> like<00:03:52.319> a<00:03:52.440> replacement<00:03:52.680> for 00:03:53.589 --> 00:03:53.599 align:start position:0% basically it's like a replacement for 00:03:53.599 --> 00:03:56.630 align:start position:0% basically it's like a replacement for erp20<00:03:54.599> tokens<00:03:55.200> where<00:03:55.739> instead<00:03:56.159> of<00:03:56.220> sending 00:03:56.630 --> 00:03:56.640 align:start position:0% erp20 tokens where instead of sending 00:03:56.640 --> 00:03:59.570 align:start position:0% erp20 tokens where instead of sending the<00:03:56.819> approval<00:03:57.360> on<00:03:58.080> chain<00:03:58.319> and<00:03:58.620> like<00:03:58.860> kind<00:03:59.459> of 00:03:59.570 --> 00:03:59.580 align:start position:0% the approval on chain and like kind of 00:03:59.580 --> 00:04:01.670 align:start position:0% the approval on chain and like kind of like<00:03:59.700> wasting<00:04:00.180> all<00:04:00.360> of<00:04:00.540> the<00:04:00.720> scars<00:04:01.140> for<00:04:01.379> the 00:04:01.670 --> 00:04:01.680 align:start position:0% like wasting all of the scars for the 00:04:01.680 --> 00:04:04.130 align:start position:0% like wasting all of the scars for the transaction<00:04:02.280> envelope<00:04:02.879> you<00:04:03.239> you<00:04:03.780> technically 00:04:04.130 --> 00:04:04.140 align:start position:0% transaction envelope you you technically 00:04:04.140 --> 00:04:06.289 align:start position:0% transaction envelope you you technically could<00:04:04.440> sign<00:04:04.739> a<00:04:05.040> transaction<00:04:05.280> get<00:04:05.640> that<00:04:05.940> gives 00:04:06.289 --> 00:04:06.299 align:start position:0% could sign a transaction get that gives 00:04:06.299 --> 00:04:09.170 align:start position:0% could sign a transaction get that gives the<00:04:06.599> spending<00:04:07.379> contract<00:04:07.860> uh<00:04:08.640> the<00:04:08.819> permission 00:04:09.170 --> 00:04:09.180 align:start position:0% the spending contract uh the permission 00:04:09.180 --> 00:04:11.809 align:start position:0% the spending contract uh the permission with<00:04:09.480> your<00:04:09.659> signature<00:04:10.140> and<00:04:10.620> so<00:04:10.799> the<00:04:11.099> idea<00:04:11.640> I 00:04:11.809 --> 00:04:11.819 align:start position:0% with your signature and so the idea I 00:04:11.819 --> 00:04:13.789 align:start position:0% with your signature and so the idea I guess<00:04:11.939> would<00:04:12.180> have<00:04:12.299> been<00:04:12.420> that<00:04:12.720> new<00:04:13.319> use<00:04:13.560> cases 00:04:13.789 --> 00:04:13.799 align:start position:0% guess would have been that new use cases 00:04:13.799 --> 00:04:16.729 align:start position:0% guess would have been that new use cases are<00:04:14.099> kind<00:04:14.220> of<00:04:14.340> enabled<00:04:14.700> and<00:04:14.939> that<00:04:15.180> also 00:04:16.729 --> 00:04:16.739 align:start position:0% are kind of enabled and that also 00:04:16.739 --> 00:04:17.330 align:start position:0% are kind of enabled and that also um 00:04:17.330 --> 00:04:17.340 align:start position:0% um 00:04:17.340 --> 00:04:19.330 align:start position:0% um that<00:04:17.880> also<00:04:18.180> we<00:04:18.299> can<00:04:18.419> save<00:04:18.600> a<00:04:18.840> lot<00:04:18.900> of<00:04:19.019> gas 00:04:19.330 --> 00:04:19.340 align:start position:0% that also we can save a lot of gas 00:04:19.340 --> 00:04:22.490 align:start position:0% that also we can save a lot of gas especially<00:04:20.340> like<00:04:21.180> considering<00:04:21.780> that<00:04:22.139> you 00:04:22.490 --> 00:04:22.500 align:start position:0% especially like considering that you 00:04:22.500 --> 00:04:25.070 align:start position:0% especially like considering that you know<00:04:22.560> each<00:04:23.040> erp20<00:04:23.940> transfer<00:04:24.600> is<00:04:24.780> essentially 00:04:25.070 --> 00:04:25.080 align:start position:0% know each erp20 transfer is essentially 00:04:25.080 --> 00:04:27.770 align:start position:0% know each erp20 transfer is essentially like<00:04:25.380> two<00:04:25.680> transfers<00:04:26.160> right<00:04:26.400> today<00:04:26.639> and<00:04:27.419> so<00:04:27.540> if 00:04:27.770 --> 00:04:27.780 align:start position:0% like two transfers right today and so if 00:04:27.780 --> 00:04:29.629 align:start position:0% like two transfers right today and so if we<00:04:27.900> could<00:04:28.080> already<00:04:28.320> condense<00:04:28.919> that<00:04:29.100> to<00:04:29.280> one<00:04:29.460> I 00:04:29.629 --> 00:04:29.639 align:start position:0% we could already condense that to one I 00:04:29.639 --> 00:04:32.390 align:start position:0% we could already condense that to one I think<00:04:29.759> the<00:04:30.120> gas<00:04:30.300> savings<00:04:30.720> would<00:04:30.960> be<00:04:31.139> uh<00:04:32.100> quite 00:04:32.390 --> 00:04:32.400 align:start position:0% think the gas savings would be uh quite 00:04:32.400 --> 00:04:34.730 align:start position:0% think the gas savings would be uh quite significant<00:04:33.000> considering<00:04:33.900> like<00:04:34.080> how<00:04:34.380> much<00:04:34.500> we 00:04:34.730 --> 00:04:34.740 align:start position:0% significant considering like how much we 00:04:34.740 --> 00:04:37.790 align:start position:0% significant considering like how much we are<00:04:34.919> transacting<00:04:35.460> with<00:04:36.060> erp20<00:04:36.660> tokens 00:04:37.790 --> 00:04:37.800 align:start position:0% are transacting with erp20 tokens 00:04:37.800 --> 00:04:40.370 align:start position:0% are transacting with erp20 tokens so<00:04:38.340> this<00:04:38.580> comment<00:04:38.940> is<00:04:39.120> actually<00:04:39.300> a<00:04:39.900> critique 00:04:40.370 --> 00:04:40.380 align:start position:0% so this comment is actually a critique 00:04:40.380 --> 00:04:43.070 align:start position:0% so this comment is actually a critique though<00:04:40.620> on<00:04:41.340> that<00:04:41.520> standard<00:04:41.940> and<00:04:42.120> basically<00:04:42.840> it 00:04:43.070 --> 00:04:43.080 align:start position:0% though on that standard and basically it 00:04:43.080 --> 00:04:45.170 align:start position:0% though on that standard and basically it I<00:04:43.500> I<00:04:43.620> don't<00:04:43.800> even<00:04:43.979> like<00:04:44.280> fully<00:04:44.699> know<00:04:44.880> the 00:04:45.170 --> 00:04:45.180 align:start position:0% I I don't even like fully know the 00:04:45.180 --> 00:04:47.330 align:start position:0% I I don't even like fully know the entire<00:04:45.419> history<00:04:45.660> but<00:04:46.020> I<00:04:46.199> know<00:04:46.380> that<00:04:46.620> I<00:04:47.220> think 00:04:47.330 --> 00:04:47.340 align:start position:0% entire history but I know that I think 00:04:47.340 --> 00:04:49.249 align:start position:0% entire history but I know that I think the<00:04:47.699> the<00:04:47.820> standard<00:04:48.240> has<00:04:48.479> like<00:04:48.660> some<00:04:48.780> issues 00:04:49.249 --> 00:04:49.259 align:start position:0% the the standard has like some issues 00:04:49.259 --> 00:04:52.189 align:start position:0% the the standard has like some issues it's<00:04:49.680> not<00:04:49.979> really<00:04:50.220> in<00:04:50.639> in<00:04:51.240> final<00:04:51.540> mode<00:04:51.840> either 00:04:52.189 --> 00:04:52.199 align:start position:0% it's not really in in final mode either 00:04:52.199 --> 00:04:55.010 align:start position:0% it's not really in in final mode either and<00:04:52.560> then<00:04:52.740> you<00:04:53.460> know<00:04:53.520> like<00:04:53.759> many<00:04:54.120> uh<00:04:54.600> companies 00:04:55.010 --> 00:04:55.020 align:start position:0% and then you know like many uh companies 00:04:55.020 --> 00:04:56.930 align:start position:0% and then you know like many uh companies have<00:04:55.199> like<00:04:55.440> kind<00:04:55.860> of<00:04:55.979> diverged<00:04:56.460> from<00:04:56.580> it<00:04:56.759> and 00:04:56.930 --> 00:04:56.940 align:start position:0% have like kind of diverged from it and 00:04:56.940 --> 00:04:58.969 align:start position:0% have like kind of diverged from it and and<00:04:57.120> they're<00:04:57.360> like<00:04:57.680> non-compliant<00:04:58.680> and 00:04:58.969 --> 00:04:58.979 align:start position:0% and they're like non-compliant and 00:04:58.979 --> 00:05:00.530 align:start position:0% and they're like non-compliant and that's<00:04:59.220> like<00:04:59.520> I<00:04:59.759> think<00:04:59.820> with<00:05:00.000> this<00:05:00.240> standard 00:05:00.530 --> 00:05:00.540 align:start position:0% that's like I think with this standard 00:05:00.540 --> 00:05:03.770 align:start position:0% that's like I think with this standard so<00:05:00.780> it<00:05:01.380> kind<00:05:01.500> of<00:05:01.560> shows<00:05:01.860> I<00:05:01.979> think<00:05:02.160> maybe<00:05:02.699> a<00:05:03.240> a<00:05:03.540> a 00:05:03.770 --> 00:05:03.780 align:start position:0% so it kind of shows I think maybe a a a 00:05:03.780 --> 00:05:06.770 align:start position:0% so it kind of shows I think maybe a a a bear<00:05:04.320> bearish<00:05:04.979> case<00:05:05.220> for<00:05:05.520> for<00:05:05.820> this<00:05:06.120> kind<00:05:06.300> of 00:05:06.770 --> 00:05:06.780 align:start position:0% bear bearish case for for this kind of 00:05:06.780 --> 00:05:07.510 align:start position:0% bear bearish case for for this kind of um 00:05:07.510 --> 00:05:07.520 align:start position:0% um 00:05:07.520 --> 00:05:11.570 align:start position:0% um standardization<00:05:08.520> approach<00:05:08.940> and<00:05:09.900> then<00:05:10.560> um<00:05:11.040> the 00:05:11.570 --> 00:05:11.580 align:start position:0% standardization approach and then um the 00:05:11.580 --> 00:05:12.890 align:start position:0% standardization approach and then um the other<00:05:11.699> case<00:05:11.940> which<00:05:12.180> I<00:05:12.300> had<00:05:12.479> to<00:05:12.600> deal<00:05:12.720> with 00:05:12.890 --> 00:05:12.900 align:start position:0% other case which I had to deal with 00:05:12.900 --> 00:05:16.310 align:start position:0% other case which I had to deal with myself<00:05:13.380> uh<00:05:14.040> personally<00:05:14.400> because<00:05:14.759> I<00:05:15.120> I<00:05:15.540> crawl 00:05:16.310 --> 00:05:16.320 align:start position:0% myself uh personally because I I crawl 00:05:16.320 --> 00:05:20.830 align:start position:0% myself uh personally because I I crawl nfts<00:05:17.000> this<00:05:18.000> is<00:05:18.180> the<00:05:18.419> interface<00:05:18.960> for<00:05:19.440> the<00:05:20.160> Zora 00:05:20.830 --> 00:05:20.840 align:start position:0% nfts this is the interface for the Zora 00:05:20.840 --> 00:05:24.710 align:start position:0% nfts this is the interface for the Zora M<00:05:21.840> nft<00:05:22.259> contract<00:05:22.860> and<00:05:23.100> m<00:05:23.340> stands<00:05:23.880> for<00:05:23.940> media 00:05:24.710 --> 00:05:24.720 align:start position:0% M nft contract and m stands for media 00:05:24.720 --> 00:05:28.249 align:start position:0% M nft contract and m stands for media nft<00:05:25.100> and<00:05:26.100> you<00:05:26.580> know<00:05:26.759> I<00:05:27.419> I<00:05:27.600> think<00:05:27.840> my<00:05:28.139> first 00:05:28.249 --> 00:05:28.259 align:start position:0% nft and you know I I think my first 00:05:28.259 --> 00:05:29.990 align:start position:0% nft and you know I I think my first exposure<00:05:28.800> to<00:05:28.979> this<00:05:29.100> was<00:05:29.280> that<00:05:29.460> I<00:05:29.639> was<00:05:29.759> kind<00:05:29.940> of 00:05:29.990 --> 00:05:30.000 align:start position:0% exposure to this was that I was kind of 00:05:30.000 --> 00:05:32.629 align:start position:0% exposure to this was that I was kind of like<00:05:30.500> disappointed<00:05:31.500> because<00:05:32.100> essentially 00:05:32.629 --> 00:05:32.639 align:start position:0% like disappointed because essentially 00:05:32.639 --> 00:05:35.330 align:start position:0% like disappointed because essentially when<00:05:32.880> you<00:05:33.060> call<00:05:33.300> the<00:05:33.539> token<00:05:34.440> URI<00:05:34.860> like<00:05:35.160> the 00:05:35.330 --> 00:05:35.340 align:start position:0% when you call the token URI like the 00:05:35.340 --> 00:05:37.310 align:start position:0% when you call the token URI like the regular<00:05:35.699> token<00:05:36.060> URI<00:05:36.360> you<00:05:36.660> are<00:05:36.780> expecting<00:05:37.139> a 00:05:37.310 --> 00:05:37.320 align:start position:0% regular token URI you are expecting a 00:05:37.320 --> 00:05:40.129 align:start position:0% regular token URI you are expecting a Json<00:05:37.680> and<00:05:38.580> uh<00:05:39.000> but<00:05:39.300> what<00:05:39.479> I'm<00:05:39.600> getting<00:05:39.780> back<00:05:39.960> is 00:05:40.129 --> 00:05:40.139 align:start position:0% Json and uh but what I'm getting back is 00:05:40.139 --> 00:05:42.409 align:start position:0% Json and uh but what I'm getting back is a<00:05:40.320> media<00:05:40.620> file<00:05:40.919> and<00:05:41.580> so<00:05:41.699> I<00:05:41.880> have<00:05:42.000> to<00:05:42.120> actually 00:05:42.409 --> 00:05:42.419 align:start position:0% a media file and so I have to actually 00:05:42.419 --> 00:05:44.510 align:start position:0% a media file and so I have to actually have<00:05:43.020> to<00:05:43.199> actually<00:05:43.320> go<00:05:43.560> to<00:05:43.740> the<00:05:43.979> Token 00:05:44.510 --> 00:05:44.520 align:start position:0% have to actually go to the Token 00:05:44.520 --> 00:05:46.550 align:start position:0% have to actually go to the Token metadata<00:05:45.120> URI<00:05:45.539> and<00:05:45.960> that's<00:05:46.020> where<00:05:46.259> the 00:05:46.550 --> 00:05:46.560 align:start position:0% metadata URI and that's where the 00:05:46.560 --> 00:05:49.249 align:start position:0% metadata URI and that's where the metadata<00:05:47.280> is<00:05:47.400> right<00:05:47.520> I<00:05:47.759> mean<00:05:47.940> the<00:05:48.780> name<00:05:49.020> is 00:05:49.249 --> 00:05:49.259 align:start position:0% metadata is right I mean the name is 00:05:49.259 --> 00:05:51.529 align:start position:0% metadata is right I mean the name is descriptive<00:05:49.860> of<00:05:50.100> that<00:05:50.220> and<00:05:50.820> and<00:05:50.880> so<00:05:51.180> I<00:05:51.300> was<00:05:51.360> a 00:05:51.529 --> 00:05:51.539 align:start position:0% descriptive of that and and so I was a 00:05:51.539 --> 00:05:53.270 align:start position:0% descriptive of that and and so I was a bit<00:05:51.600> disappointed<00:05:52.380> because<00:05:52.620> I<00:05:52.860> couldn't<00:05:52.979> like 00:05:53.270 --> 00:05:53.280 align:start position:0% bit disappointed because I couldn't like 00:05:53.280 --> 00:05:55.370 align:start position:0% bit disappointed because I couldn't like I<00:05:53.580> had<00:05:53.699> to<00:05:53.820> basically<00:05:54.180> build<00:05:54.419> like<00:05:54.660> this<00:05:54.960> uh 00:05:55.370 --> 00:05:55.380 align:start position:0% I had to basically build like this uh 00:05:55.380 --> 00:05:57.710 align:start position:0% I had to basically build like this uh this<00:05:55.860> like<00:05:55.979> custom<00:05:56.220> logic<00:05:56.639> around<00:05:56.820> it<00:05:57.120> but<00:05:57.539> on 00:05:57.710 --> 00:05:57.720 align:start position:0% this like custom logic around it but on 00:05:57.720 --> 00:05:59.930 align:start position:0% this like custom logic around it but on the<00:05:57.840> other<00:05:57.960> hand<00:05:58.080> I'm<00:05:58.380> also<00:05:58.759> empathetic<00:05:59.759> with 00:05:59.930 --> 00:05:59.940 align:start position:0% the other hand I'm also empathetic with 00:05:59.940 --> 00:06:01.330 align:start position:0% the other hand I'm also empathetic with that<00:06:00.120> because 00:06:01.330 --> 00:06:01.340 align:start position:0% that because 00:06:01.340 --> 00:06:05.689 align:start position:0% that because uh<00:06:02.340> in<00:06:02.759> the<00:06:03.180> regular<00:06:03.419> nft<00:06:03.919> the<00:06:04.919> media<00:06:05.340> file 00:06:05.689 --> 00:06:05.699 align:start position:0% uh in the regular nft the media file 00:06:05.699 --> 00:06:08.810 align:start position:0% uh in the regular nft the media file which<00:06:06.060> has<00:06:06.720> been<00:06:06.900> like<00:06:07.380> traditionally<00:06:08.340> the 00:06:08.810 --> 00:06:08.820 align:start position:0% which has been like traditionally the 00:06:08.820 --> 00:06:12.170 align:start position:0% which has been like traditionally the image<00:06:09.180> is<00:06:09.720> literally<00:06:10.080> in<00:06:10.500> a<00:06:10.740> uh<00:06:11.520> Json<00:06:11.880> object 00:06:12.170 --> 00:06:12.180 align:start position:0% image is literally in a uh Json object 00:06:12.180 --> 00:06:16.010 align:start position:0% image is literally in a uh Json object that<00:06:12.419> we<00:06:12.539> call<00:06:12.660> metadata<00:06:13.500> so<00:06:14.160> I<00:06:15.120> I<00:06:15.180> mean<00:06:15.479> in<00:06:15.960> my 00:06:16.010 --> 00:06:16.020 align:start position:0% that we call metadata so I I mean in my 00:06:16.020 --> 00:06:18.710 align:start position:0% that we call metadata so I I mean in my opinion<00:06:16.320> that<00:06:16.560> says<00:06:16.979> a<00:06:17.100> lot<00:06:17.220> about<00:06:17.539> how<00:06:18.539> we 00:06:18.710 --> 00:06:18.720 align:start position:0% opinion that says a lot about how we 00:06:18.720 --> 00:06:21.469 align:start position:0% opinion that says a lot about how we think<00:06:18.840> about<00:06:19.020> nfts<00:06:19.740> and<00:06:19.919> that<00:06:20.160> we<00:06:20.880> see<00:06:21.180> the 00:06:21.469 --> 00:06:21.479 align:start position:0% think about nfts and that we see the 00:06:21.479 --> 00:06:23.570 align:start position:0% think about nfts and that we see the image<00:06:21.840> or<00:06:22.259> like<00:06:22.440> the<00:06:22.620> media<00:06:22.860> that<00:06:23.039> is<00:06:23.220> attached 00:06:23.570 --> 00:06:23.580 align:start position:0% image or like the media that is attached 00:06:23.580 --> 00:06:26.270 align:start position:0% image or like the media that is attached to<00:06:23.759> the<00:06:23.940> nft<00:06:24.180> kind<00:06:24.600> of<00:06:24.720> like<00:06:24.840> as<00:06:25.380> metadata<00:06:26.039> to 00:06:26.270 --> 00:06:26.280 align:start position:0% to the nft kind of like as metadata to 00:06:26.280 --> 00:06:28.969 align:start position:0% to the nft kind of like as metadata to something<00:06:26.639> that<00:06:27.360> is<00:06:27.479> the<00:06:27.600> nft<00:06:27.900> that<00:06:28.440> is<00:06:28.620> kind 00:06:28.969 --> 00:06:28.979 align:start position:0% something that is the nft that is kind 00:06:28.979 --> 00:06:30.710 align:start position:0% something that is the nft that is kind of<00:06:29.039> like<00:06:29.220> maybe<00:06:29.639> like<00:06:29.940> a<00:06:30.180> financial 00:06:30.710 --> 00:06:30.720 align:start position:0% of like maybe like a financial 00:06:30.720 --> 00:06:33.290 align:start position:0% of like maybe like a financial instrument<00:06:31.199> then<00:06:31.620> or<00:06:31.860> whatever<00:06:32.039> and<00:06:32.819> so<00:06:33.000> I<00:06:33.180> I 00:06:33.290 --> 00:06:33.300 align:start position:0% instrument then or whatever and so I I 00:06:33.300 --> 00:06:35.390 align:start position:0% instrument then or whatever and so I I think<00:06:33.479> it's<00:06:33.660> actually<00:06:33.900> beautiful<00:06:34.199> that<00:06:34.800> they 00:06:35.390 --> 00:06:35.400 align:start position:0% think it's actually beautiful that they 00:06:35.400 --> 00:06:36.890 align:start position:0% think it's actually beautiful that they that<00:06:35.580> you<00:06:35.819> know<00:06:35.880> that<00:06:36.060> they<00:06:36.360> made<00:06:36.539> the<00:06:36.720> case 00:06:36.890 --> 00:06:36.900 align:start position:0% that you know that they made the case 00:06:36.900 --> 00:06:39.409 align:start position:0% that you know that they made the case that<00:06:37.319> we<00:06:37.979> should<00:06:38.160> actually<00:06:38.400> use<00:06:38.819> the<00:06:39.060> token 00:06:39.409 --> 00:06:39.419 align:start position:0% that we should actually use the token 00:06:39.419 --> 00:06:42.950 align:start position:0% that we should actually use the token URI<00:06:39.840> to<00:06:40.800> embed<00:06:41.220> the<00:06:41.639> media<00:06:41.940> file<00:06:42.240> directly<00:06:42.600> and 00:06:42.950 --> 00:06:42.960 align:start position:0% URI to embed the media file directly and 00:06:42.960 --> 00:06:44.990 align:start position:0% URI to embed the media file directly and to<00:06:43.199> Center<00:06:43.560> really<00:06:43.979> the<00:06:44.160> nft<00:06:44.400> around<00:06:44.819> the 00:06:44.990 --> 00:06:45.000 align:start position:0% to Center really the nft around the 00:06:45.000 --> 00:06:48.110 align:start position:0% to Center really the nft around the media<00:06:45.300> file<00:06:45.539> and<00:06:46.199> not<00:06:46.440> uh<00:06:47.160> make<00:06:47.699> the<00:06:47.819> media 00:06:48.110 --> 00:06:48.120 align:start position:0% media file and not uh make the media 00:06:48.120 --> 00:06:53.150 align:start position:0% media file and not uh make the media file<00:06:48.479> a<00:06:48.780> mere<00:06:49.139> uh<00:06:49.880> metadata<00:06:50.880> field<00:06:51.000> so 00:06:53.150 --> 00:06:53.160 align:start position:0% file a mere uh metadata field so 00:06:53.160 --> 00:06:58.790 align:start position:0% file a mere uh metadata field so foreign 00:06:58.790 --> 00:06:58.800 align:start position:0% 00:06:58.800 --> 00:07:01.670 align:start position:0% and<00:06:59.539> apart<00:07:00.539> from<00:07:00.660> all<00:07:00.900> of<00:07:01.020> this<00:07:01.319> uh<00:07:01.560> like 00:07:01.670 --> 00:07:01.680 align:start position:0% and apart from all of this uh like 00:07:01.680 --> 00:07:03.050 align:start position:0% and apart from all of this uh like pessimism<00:07:02.220> I<00:07:02.520> think<00:07:02.639> there's<00:07:02.819> there's 00:07:03.050 --> 00:07:03.060 align:start position:0% pessimism I think there's there's 00:07:03.060 --> 00:07:05.210 align:start position:0% pessimism I think there's there's another<00:07:03.360> good<00:07:03.600> reason<00:07:03.840> for<00:07:04.319> uh<00:07:04.740> submitting 00:07:05.210 --> 00:07:05.220 align:start position:0% another good reason for uh submitting 00:07:05.220 --> 00:07:08.150 align:start position:0% another good reason for uh submitting and<00:07:05.759> and<00:07:05.940> being<00:07:06.539> active<00:07:06.840> on<00:07:07.080> this<00:07:07.199> forum<00:07:07.560> and 00:07:08.150 --> 00:07:08.160 align:start position:0% and and being active on this forum and 00:07:08.160 --> 00:07:10.670 align:start position:0% and and being active on this forum and it's<00:07:08.639> because<00:07:08.880> you<00:07:09.360> get<00:07:09.600> a<00:07:09.780> ton<00:07:09.900> of<00:07:10.080> exposure 00:07:10.670 --> 00:07:10.680 align:start position:0% it's because you get a ton of exposure 00:07:10.680 --> 00:07:14.870 align:start position:0% it's because you get a ton of exposure to<00:07:11.520> uh<00:07:12.060> to<00:07:12.300> your<00:07:12.479> ideals<00:07:12.960> so<00:07:13.199> this<00:07:13.800> is<00:07:13.919> a<00:07:14.340> thread 00:07:14.870 --> 00:07:14.880 align:start position:0% to uh to your ideals so this is a thread 00:07:14.880 --> 00:07:17.270 align:start position:0% to uh to your ideals so this is a thread here<00:07:15.060> that<00:07:15.300> I<00:07:15.419> made<00:07:15.600> I<00:07:16.440> think<00:07:16.500> around<00:07:16.740> in<00:07:17.100> in 00:07:17.270 --> 00:07:17.280 align:start position:0% here that I made I think around in in 00:07:17.280 --> 00:07:19.550 align:start position:0% here that I made I think around in in April<00:07:17.759> and<00:07:18.000> it's<00:07:18.120> about<00:07:18.360> uh<00:07:19.199> like<00:07:19.440> a 00:07:19.550 --> 00:07:19.560 align:start position:0% April and it's about uh like a 00:07:19.560 --> 00:07:21.710 align:start position:0% April and it's about uh like a specification<00:07:20.039> for<00:07:20.340> soul<00:07:20.580> bound<00:07:20.940> tokens<00:07:21.360> or 00:07:21.710 --> 00:07:21.720 align:start position:0% specification for soul bound tokens or 00:07:21.720 --> 00:07:23.930 align:start position:0% specification for soul bound tokens or we<00:07:22.319> now<00:07:22.560> call<00:07:22.740> them<00:07:22.919> account<00:07:23.160> bound<00:07:23.580> tokens 00:07:23.930 --> 00:07:23.940 align:start position:0% we now call them account bound tokens 00:07:23.940 --> 00:07:25.490 align:start position:0% we now call them account bound tokens and<00:07:24.479> this 00:07:25.490 --> 00:07:25.500 align:start position:0% and this 00:07:25.500 --> 00:07:28.670 align:start position:0% and this threat<00:07:26.220> has<00:07:26.340> gotten<00:07:26.759> 9000<00:07:27.539> views<00:07:27.960> and<00:07:28.259> if<00:07:28.500> you 00:07:28.670 --> 00:07:28.680 align:start position:0% threat has gotten 9000 views and if you 00:07:28.680 --> 00:07:30.529 align:start position:0% threat has gotten 9000 views and if you would<00:07:28.860> sort<00:07:29.340> by<00:07:29.520> the<00:07:29.759> replies<00:07:30.060> it's<00:07:30.360> actually 00:07:30.529 --> 00:07:30.539 align:start position:0% would sort by the replies it's actually 00:07:30.539 --> 00:07:34.309 align:start position:0% would sort by the replies it's actually the<00:07:30.900> top<00:07:31.220> uh<00:07:32.220> the<00:07:32.880> top<00:07:33.120> controversial<00:07:33.840> threat 00:07:34.309 --> 00:07:34.319 align:start position:0% the top uh the top controversial threat 00:07:34.319 --> 00:07:36.650 align:start position:0% the top uh the top controversial threat on<00:07:34.860> the<00:07:35.039> entire<00:07:35.280> forum<00:07:35.699> for<00:07:36.000> the<00:07:36.240> for<00:07:36.479> the 00:07:36.650 --> 00:07:36.660 align:start position:0% on the entire forum for the for the 00:07:36.660 --> 00:07:39.830 align:start position:0% on the entire forum for the for the entire<00:07:36.960> year<00:07:37.199> apparently<00:07:37.800> so<00:07:38.639> I<00:07:39.120> mean<00:07:39.240> while 00:07:39.830 --> 00:07:39.840 align:start position:0% entire year apparently so I mean while 00:07:39.840 --> 00:07:41.749 align:start position:0% entire year apparently so I mean while that<00:07:40.080> is<00:07:40.319> uh<00:07:40.560> concerning<00:07:41.220> to<00:07:41.400> me<00:07:41.520> because 00:07:41.749 --> 00:07:41.759 align:start position:0% that is uh concerning to me because 00:07:41.759 --> 00:07:43.850 align:start position:0% that is uh concerning to me because apparently<00:07:42.360> a<00:07:42.840> lot<00:07:43.020> of<00:07:43.139> people<00:07:43.199> have<00:07:43.440> opinions 00:07:43.850 --> 00:07:43.860 align:start position:0% apparently a lot of people have opinions 00:07:43.860 --> 00:07:46.689 align:start position:0% apparently a lot of people have opinions about<00:07:44.039> this<00:07:44.599> it's<00:07:45.599> also<00:07:45.960> on<00:07:46.139> the<00:07:46.259> other<00:07:46.380> hand 00:07:46.689 --> 00:07:46.699 align:start position:0% about this it's also on the other hand 00:07:46.699 --> 00:07:49.850 align:start position:0% about this it's also on the other hand it<00:07:47.699> was<00:07:47.819> a<00:07:48.000> like<00:07:48.240> a<00:07:48.419> beautiful<00:07:48.539> chance<00:07:49.020> of<00:07:49.560> of 00:07:49.850 --> 00:07:49.860 align:start position:0% it was a like a beautiful chance of of 00:07:49.860 --> 00:07:51.950 align:start position:0% it was a like a beautiful chance of of receiving<00:07:50.400> feedback<00:07:50.880> and<00:07:51.180> also<00:07:51.419> called<00:07:51.539> lack 00:07:51.950 --> 00:07:51.960 align:start position:0% receiving feedback and also called lack 00:07:51.960 --> 00:07:54.850 align:start position:0% receiving feedback and also called lack of<00:07:52.139> receiving<00:07:52.979> constructive<00:07:53.639> feedback 00:07:54.850 --> 00:07:54.860 align:start position:0% of receiving constructive feedback 00:07:54.860 --> 00:07:58.490 align:start position:0% of receiving constructive feedback which<00:07:55.860> with<00:07:56.220> which<00:07:56.460> without<00:07:57.120> that<00:07:57.539> this 00:07:58.490 --> 00:07:58.500 align:start position:0% which with which without that this 00:07:58.500 --> 00:07:59.809 align:start position:0% which with which without that this standard<00:07:58.979> wouldn't<00:07:59.160> wouldn't<00:07:59.340> have<00:07:59.639> gone 00:07:59.809 --> 00:07:59.819 align:start position:0% standard wouldn't wouldn't have gone 00:07:59.819 --> 00:08:02.029 align:start position:0% standard wouldn't wouldn't have gone where<00:08:00.060> where<00:08:00.360> it<00:08:00.539> went<00:08:00.660> today<00:08:00.900> so<00:08:01.380> I<00:08:01.620> initially 00:08:02.029 --> 00:08:02.039 align:start position:0% where where it went today so I initially 00:08:02.039 --> 00:08:04.969 align:start position:0% where where it went today so I initially started<00:08:02.520> this<00:08:03.360> um<00:08:03.419> as<00:08:04.020> a<00:08:04.259> non-transferable 00:08:04.969 --> 00:08:04.979 align:start position:0% started this um as a non-transferable 00:08:04.979 --> 00:08:06.050 align:start position:0% started this um as a non-transferable token 00:08:06.050 --> 00:08:06.060 align:start position:0% token 00:08:06.060 --> 00:08:09.589 align:start position:0% token uh<00:08:06.840> specification<00:08:07.560> and<00:08:08.220> basically<00:08:09.000> now<00:08:09.300> we 00:08:09.589 --> 00:08:09.599 align:start position:0% uh specification and basically now we 00:08:09.599 --> 00:08:11.089 align:start position:0% uh specification and basically now we have<00:08:09.720> can<00:08:09.960> we<00:08:10.319> have<00:08:10.440> like<00:08:10.620> moved<00:08:10.919> into 00:08:11.089 --> 00:08:11.099 align:start position:0% have can we have like moved into 00:08:11.099 --> 00:08:13.370 align:start position:0% have can we have like moved into consensual<00:08:11.819> minting 00:08:13.370 --> 00:08:13.380 align:start position:0% consensual minting 00:08:13.380 --> 00:08:15.950 align:start position:0% consensual minting um<00:08:13.440> and<00:08:14.160> into<00:08:14.400> like<00:08:14.759> yeah<00:08:15.360> basically<00:08:15.720> like 00:08:15.950 --> 00:08:15.960 align:start position:0% um and into like yeah basically like 00:08:15.960 --> 00:08:17.990 align:start position:0% um and into like yeah basically like having<00:08:16.199> the<00:08:16.560> the<00:08:16.800> signature<00:08:17.280> being<00:08:17.520> checked 00:08:17.990 --> 00:08:18.000 align:start position:0% having the the signature being checked 00:08:18.000 --> 00:08:20.629 align:start position:0% having the the signature being checked by<00:08:18.240> both<00:08:18.539> the<00:08:18.720> sender<00:08:19.139> and<00:08:19.259> the<00:08:19.440> receiver<00:08:19.740> and 00:08:20.629 --> 00:08:20.639 align:start position:0% by both the sender and the receiver and 00:08:20.639 --> 00:08:22.369 align:start position:0% by both the sender and the receiver and you<00:08:20.879> know<00:08:20.940> we<00:08:21.240> are<00:08:21.360> actively<00:08:21.840> talking<00:08:22.080> about 00:08:22.369 --> 00:08:22.379 align:start position:0% you know we are actively talking about 00:08:22.379 --> 00:08:24.830 align:start position:0% you know we are actively talking about all<00:08:22.740> of<00:08:22.860> the<00:08:23.039> Privacy<00:08:23.400> challenges<00:08:24.060> of<00:08:24.599> Soul 00:08:24.830 --> 00:08:24.840 align:start position:0% all of the Privacy challenges of Soul 00:08:24.840 --> 00:08:26.570 align:start position:0% all of the Privacy challenges of Soul Bond<00:08:25.139> tokens<00:08:25.500> and<00:08:25.680> so<00:08:25.860> this<00:08:26.280> has<00:08:26.400> really 00:08:26.570 --> 00:08:26.580 align:start position:0% Bond tokens and so this has really 00:08:26.580 --> 00:08:28.969 align:start position:0% Bond tokens and so this has really become<00:08:26.940> basically<00:08:27.479> like<00:08:27.720> a<00:08:27.960> space<00:08:28.379> where<00:08:28.740> this 00:08:28.969 --> 00:08:28.979 align:start position:0% become basically like a space where this 00:08:28.979 --> 00:08:32.209 align:start position:0% become basically like a space where this entire<00:08:29.900> standard<00:08:30.900> all<00:08:31.139> the<00:08:31.379> solar<00:08:31.800> token 00:08:32.209 --> 00:08:32.219 align:start position:0% entire standard all the solar token 00:08:32.219 --> 00:08:34.490 align:start position:0% entire standard all the solar token things<00:08:32.459> everything<00:08:33.000> is<00:08:33.240> like<00:08:33.539> very<00:08:33.779> verbosely 00:08:34.490 --> 00:08:34.500 align:start position:0% things everything is like very verbosely 00:08:34.500 --> 00:08:36.170 align:start position:0% things everything is like very verbosely documented<00:08:35.159> and<00:08:35.339> and<00:08:35.520> I<00:08:35.760> I<00:08:35.880> think<00:08:36.060> it's 00:08:36.170 --> 00:08:36.180 align:start position:0% documented and and I I think it's 00:08:36.180 --> 00:08:38.930 align:start position:0% documented and and I I think it's awesome<00:08:36.479> because<00:08:37.260> I<00:08:37.919> I<00:08:38.099> wouldn't<00:08:38.339> have<00:08:38.580> had 00:08:38.930 --> 00:08:38.940 align:start position:0% awesome because I I wouldn't have had 00:08:38.940 --> 00:08:41.510 align:start position:0% awesome because I I wouldn't have had these<00:08:39.539> ideal<00:08:39.899> ideas<00:08:40.140> by<00:08:40.560> myself<00:08:40.740> so<00:08:41.219> I<00:08:41.399> think 00:08:41.510 --> 00:08:41.520 align:start position:0% these ideal ideas by myself so I think 00:08:41.520 --> 00:08:43.370 align:start position:0% these ideal ideas by myself so I think this<00:08:41.640> is<00:08:41.820> like<00:08:41.880> a<00:08:42.060> community<00:08:42.240> effort<00:08:42.839> and<00:08:43.260> it's 00:08:43.370 --> 00:08:43.380 align:start position:0% this is like a community effort and it's 00:08:43.380 --> 00:08:44.690 align:start position:0% this is like a community effort and it's cool 00:08:44.690 --> 00:08:44.700 align:start position:0% cool 00:08:44.700 --> 00:08:45.590 align:start position:0% cool um 00:08:45.590 --> 00:08:45.600 align:start position:0% um 00:08:45.600 --> 00:08:47.570 align:start position:0% um and 00:08:47.570 --> 00:08:47.580 align:start position:0% and 00:08:47.580 --> 00:08:50.210 align:start position:0% and so<00:08:48.240> by<00:08:48.420> the<00:08:48.540> way<00:08:48.600> I'm<00:08:48.959> like<00:08:49.200> basically<00:08:49.860> these 00:08:50.210 --> 00:08:50.220 align:start position:0% so by the way I'm like basically these 00:08:50.220 --> 00:08:54.050 align:start position:0% so by the way I'm like basically these slides<00:08:50.580> are<00:08:51.000> all<00:08:51.360> a<00:08:52.200> um<00:08:52.320> Eve<00:08:52.740> magicians<00:08:53.339> blog 00:08:54.050 --> 00:08:54.060 align:start position:0% slides are all a um Eve magicians blog 00:08:54.060 --> 00:08:56.930 align:start position:0% slides are all a um Eve magicians blog post<00:08:54.180> essentially<00:08:54.920> and<00:08:55.920> uh<00:08:56.160> I<00:08:56.399> need<00:08:56.519> to<00:08:56.640> find<00:08:56.760> a 00:08:56.930 --> 00:08:56.940 align:start position:0% post essentially and uh I need to find a 00:08:56.940 --> 00:08:59.449 align:start position:0% post essentially and uh I need to find a bit<00:08:57.060> my<00:08:57.180> way<00:08:57.360> but<00:08:57.720> so<00:08:57.959> the<00:08:58.500> so<00:08:58.740> so<00:08:58.980> basically 00:08:59.449 --> 00:08:59.459 align:start position:0% bit my way but so the so so basically 00:08:59.459 --> 00:09:02.269 align:start position:0% bit my way but so the so so basically one<00:08:59.760> of<00:08:59.880> the<00:09:00.060> but<00:09:00.959> kind<00:09:01.560> of<00:09:01.620> like<00:09:01.740> one<00:09:02.100> of<00:09:02.220> the 00:09:02.269 --> 00:09:02.279 align:start position:0% one of the but kind of like one of the 00:09:02.279 --> 00:09:04.790 align:start position:0% one of the but kind of like one of the one<00:09:02.580> of<00:09:02.640> the<00:09:02.760> problems<00:09:03.060> of<00:09:03.240> the<00:09:03.360> EIP<00:09:03.800> uh 00:09:04.790 --> 00:09:04.800 align:start position:0% one of the problems of the EIP uh 00:09:04.800 --> 00:09:07.490 align:start position:0% one of the problems of the EIP uh standards<00:09:05.339> process<00:09:05.580> is<00:09:05.700> that<00:09:06.000> it's<00:09:06.120> it<00:09:06.899> it's 00:09:07.490 --> 00:09:07.500 align:start position:0% standards process is that it's it it's 00:09:07.500 --> 00:09:09.290 align:start position:0% standards process is that it's it it's it's<00:09:07.680> truly<00:09:08.100> permissionless<00:09:08.640> and<00:09:08.940> it's<00:09:09.120> open 00:09:09.290 --> 00:09:09.300 align:start position:0% it's truly permissionless and it's open 00:09:09.300 --> 00:09:12.050 align:start position:0% it's truly permissionless and it's open to<00:09:09.540> everyone<00:09:09.779> essentially<00:09:10.440> because<00:09:10.940> you<00:09:11.940> can 00:09:12.050 --> 00:09:12.060 align:start position:0% to everyone essentially because you can 00:09:12.060 --> 00:09:15.050 align:start position:0% to everyone essentially because you can just<00:09:12.300> go<00:09:12.540> to<00:09:12.779> like<00:09:13.019> the<00:09:13.440> uh<00:09:14.339> you<00:09:14.820> know<00:09:14.940> like 00:09:15.050 --> 00:09:15.060 align:start position:0% just go to like the uh you know like 00:09:15.060 --> 00:09:18.889 align:start position:0% just go to like the uh you know like github.com<00:09:16.220> ethereum<00:09:17.220> eips<00:09:18.060> and<00:09:18.600> you<00:09:18.779> can 00:09:18.889 --> 00:09:18.899 align:start position:0% github.com ethereum eips and you can 00:09:18.899 --> 00:09:21.170 align:start position:0% github.com ethereum eips and you can submit<00:09:19.260> your<00:09:19.440> own<00:09:19.620> EIP<00:09:20.040> and<00:09:20.339> as<00:09:20.519> long<00:09:20.700> as<00:09:20.760> you 00:09:21.170 --> 00:09:21.180 align:start position:0% submit your own EIP and as long as you 00:09:21.180 --> 00:09:24.889 align:start position:0% submit your own EIP and as long as you are<00:09:21.500> uh<00:09:22.500> complying<00:09:23.339> to<00:09:23.519> the<00:09:24.120> uh<00:09:24.660> the 00:09:24.889 --> 00:09:24.899 align:start position:0% are uh complying to the uh the 00:09:24.899 --> 00:09:26.930 align:start position:0% are uh complying to the uh the formatting<00:09:25.380> rules<00:09:25.680> and<00:09:25.920> you're<00:09:26.040> like<00:09:26.339> you 00:09:26.930 --> 00:09:26.940 align:start position:0% formatting rules and you're like you 00:09:26.940 --> 00:09:28.910 align:start position:0% formatting rules and you're like you know<00:09:27.000> you're<00:09:27.720> like<00:09:28.320> um 00:09:28.910 --> 00:09:28.920 align:start position:0% know you're like um 00:09:28.920 --> 00:09:31.850 align:start position:0% know you're like um receptive<00:09:29.820> to<00:09:30.120> the<00:09:30.420> to<00:09:30.899> the<00:09:31.200> feedback<00:09:31.500> of<00:09:31.740> the 00:09:31.850 --> 00:09:31.860 align:start position:0% receptive to the to the feedback of the 00:09:31.860 --> 00:09:34.070 align:start position:0% receptive to the to the feedback of the EIP<00:09:32.160> editors<00:09:32.700> and<00:09:33.000> you're<00:09:33.300> not<00:09:33.480> like<00:09:33.660> mean<00:09:33.899> to 00:09:34.070 --> 00:09:34.080 align:start position:0% EIP editors and you're not like mean to 00:09:34.080 --> 00:09:35.690 align:start position:0% EIP editors and you're not like mean to them<00:09:34.260> or<00:09:34.440> whatever<00:09:34.560> you<00:09:35.160> you<00:09:35.339> will<00:09:35.580> actually 00:09:35.690 --> 00:09:35.700 align:start position:0% them or whatever you you will actually 00:09:35.700 --> 00:09:37.790 align:start position:0% them or whatever you you will actually get<00:09:36.000> your<00:09:36.240> document<00:09:36.660> merged<00:09:37.140> and<00:09:37.620> that 00:09:37.790 --> 00:09:37.800 align:start position:0% get your document merged and that 00:09:37.800 --> 00:09:39.790 align:start position:0% get your document merged and that document<00:09:38.100> will<00:09:38.519> show<00:09:38.760> up<00:09:38.940> on 00:09:39.790 --> 00:09:39.800 align:start position:0% document will show up on 00:09:39.800 --> 00:09:42.710 align:start position:0% document will show up on eips.etherium.org<00:09:40.800> so<00:09:40.920> that's<00:09:41.100> really<00:09:41.339> cool 00:09:42.710 --> 00:09:42.720 align:start position:0% eips.etherium.org so that's really cool 00:09:42.720 --> 00:09:44.630 align:start position:0% eips.etherium.org so that's really cool um<00:09:42.839> and<00:09:43.260> that's<00:09:43.440> really<00:09:43.740> a<00:09:43.920> strength<00:09:44.279> but<00:09:44.459> it's 00:09:44.630 --> 00:09:44.640 align:start position:0% um and that's really a strength but it's 00:09:44.640 --> 00:09:48.050 align:start position:0% um and that's really a strength but it's also<00:09:44.820> a<00:09:44.940> weakness<00:09:45.300> and<00:09:46.080> I<00:09:46.320> think<00:09:46.500> this<00:09:46.920> uh<00:09:47.339> I 00:09:48.050 --> 00:09:48.060 align:start position:0% also a weakness and I think this uh I 00:09:48.060 --> 00:09:49.550 align:start position:0% also a weakness and I think this uh I guess<00:09:48.360> it's<00:09:48.540> like<00:09:48.779> a<00:09:48.899> bit<00:09:49.019> of<00:09:49.200> a<00:09:49.380> famous 00:09:49.550 --> 00:09:49.560 align:start position:0% guess it's like a bit of a famous 00:09:49.560 --> 00:09:51.530 align:start position:0% guess it's like a bit of a famous cartoon<00:09:50.339> in<00:09:50.760> the 00:09:51.530 --> 00:09:51.540 align:start position:0% cartoon in the 00:09:51.540 --> 00:09:54.350 align:start position:0% cartoon in the in<00:09:51.959> the<00:09:52.260> uh<00:09:52.680> in<00:09:53.100> these<00:09:53.279> standards<00:09:53.760> community 00:09:54.350 --> 00:09:54.360 align:start position:0% in the uh in these standards community 00:09:54.360 --> 00:09:56.630 align:start position:0% in the uh in these standards community at<00:09:54.779> least<00:09:54.839> where<00:09:55.080> you<00:09:55.320> know<00:09:55.380> like<00:09:55.620> the<00:09:56.399> there's 00:09:56.630 --> 00:09:56.640 align:start position:0% at least where you know like the there's 00:09:56.640 --> 00:09:59.690 align:start position:0% at least where you know like the there's like<00:09:56.880> the<00:09:57.120> this<00:09:57.300> XKCD<00:09:58.140> comic<00:09:58.500> uh<00:09:59.339> you<00:09:59.640> know 00:09:59.690 --> 00:09:59.700 align:start position:0% like the this XKCD comic uh you know 00:09:59.700 --> 00:10:01.250 align:start position:0% like the this XKCD comic uh you know where<00:09:59.880> there's<00:10:00.060> like<00:10:00.300> 14<00:10:00.540> competing 00:10:01.250 --> 00:10:01.260 align:start position:0% where there's like 14 competing 00:10:01.260 --> 00:10:02.810 align:start position:0% where there's like 14 competing standards<00:10:01.680> for<00:10:01.920> a<00:10:02.040> use<00:10:02.220> case<00:10:02.459> and<00:10:02.640> then 00:10:02.810 --> 00:10:02.820 align:start position:0% standards for a use case and then 00:10:02.820 --> 00:10:05.210 align:start position:0% standards for a use case and then there's<00:10:03.180> this<00:10:03.360> one<00:10:03.540> guy<00:10:03.720> saying<00:10:04.080> hey<00:10:04.320> that's 00:10:05.210 --> 00:10:05.220 align:start position:0% there's this one guy saying hey that's 00:10:05.220 --> 00:10:07.610 align:start position:0% there's this one guy saying hey that's crazy<00:10:05.700> like<00:10:06.000> why<00:10:06.420> do<00:10:06.600> we<00:10:06.720> need<00:10:06.839> 14<00:10:07.019> standards 00:10:07.610 --> 00:10:07.620 align:start position:0% crazy like why do we need 14 standards 00:10:07.620 --> 00:10:09.230 align:start position:0% crazy like why do we need 14 standards we<00:10:07.740> should<00:10:07.920> have<00:10:08.040> one<00:10:08.279> standard<00:10:08.700> that<00:10:08.820> has<00:10:09.060> all 00:10:09.230 --> 00:10:09.240 align:start position:0% we should have one standard that has all 00:10:09.240 --> 00:10:11.690 align:start position:0% we should have one standard that has all of<00:10:09.360> the<00:10:09.600> uh<00:10:09.959> that<00:10:10.500> addresses<00:10:11.040> of<00:10:11.220> the<00:10:11.399> use<00:10:11.519> case 00:10:11.690 --> 00:10:11.700 align:start position:0% of the uh that addresses of the use case 00:10:11.700 --> 00:10:14.870 align:start position:0% of the uh that addresses of the use case and<00:10:12.000> suddenly<00:10:12.899> we<00:10:13.260> have<00:10:13.380> like<00:10:13.560> 15<00:10:13.880> standards 00:10:14.870 --> 00:10:14.880 align:start position:0% and suddenly we have like 15 standards 00:10:14.880 --> 00:10:16.730 align:start position:0% and suddenly we have like 15 standards right<00:10:15.000> so<00:10:15.240> so<00:10:15.540> it's<00:10:15.779> kind<00:10:16.019> of<00:10:16.080> a<00:10:16.260> problem<00:10:16.440> in 00:10:16.730 --> 00:10:16.740 align:start position:0% right so so it's kind of a problem in 00:10:16.740 --> 00:10:19.370 align:start position:0% right so so it's kind of a problem in the<00:10:16.920> ERC<00:10:17.399> process<00:10:17.760> as<00:10:18.000> well<00:10:18.180> that<00:10:18.480> we<00:10:18.899> just 00:10:19.370 --> 00:10:19.380 align:start position:0% the ERC process as well that we just 00:10:19.380 --> 00:10:21.850 align:start position:0% the ERC process as well that we just have<00:10:19.560> like<00:10:19.740> a<00:10:19.920> lot<00:10:19.980> of<00:10:20.180> verbosity<00:10:21.180> and<00:10:21.540> and 00:10:21.850 --> 00:10:21.860 align:start position:0% have like a lot of verbosity and and 00:10:21.860 --> 00:10:25.190 align:start position:0% have like a lot of verbosity and and duplication<00:10:22.860> and<00:10:23.220> and<00:10:23.580> so<00:10:24.060> on<00:10:24.240> so<00:10:24.779> it's<00:10:25.019> like 00:10:25.190 --> 00:10:25.200 align:start position:0% duplication and and so on so it's like 00:10:25.200 --> 00:10:27.350 align:start position:0% duplication and and so on so it's like you<00:10:25.800> know<00:10:25.920> on<00:10:26.220> one<00:10:26.399> side<00:10:26.519> we<00:10:26.760> have<00:10:26.880> like<00:10:27.000> the 00:10:27.350 --> 00:10:27.360 align:start position:0% you know on one side we have like the 00:10:27.360 --> 00:10:30.650 align:start position:0% you know on one side we have like the strength<00:10:27.779> the<00:10:28.080> openness<00:10:28.500> and<00:10:28.920> also<00:10:29.580> this<00:10:29.760> like 00:10:30.650 --> 00:10:30.660 align:start position:0% strength the openness and also this like 00:10:30.660 --> 00:10:33.650 align:start position:0% strength the openness and also this like uh<00:10:31.620> yeah<00:10:32.519> it's<00:10:32.640> almost<00:10:32.820> like<00:10:33.000> a<00:10:33.180> Spam<00:10:33.420> problem 00:10:33.650 --> 00:10:33.660 align:start position:0% uh yeah it's almost like a Spam problem 00:10:33.660 --> 00:10:36.110 align:start position:0% uh yeah it's almost like a Spam problem or<00:10:33.899> whatever<00:10:34.080> but 00:10:36.110 --> 00:10:36.120 align:start position:0% or whatever but 00:10:36.120 --> 00:10:38.269 align:start position:0% or whatever but I<00:10:36.600> wanna<00:10:36.660> I<00:10:36.959> wanna<00:10:37.080> I<00:10:37.320> wanna<00:10:37.500> still<00:10:37.740> motivate 00:10:38.269 --> 00:10:38.279 align:start position:0% I wanna I wanna I wanna still motivate 00:10:38.279 --> 00:10:40.370 align:start position:0% I wanna I wanna I wanna still motivate and<00:10:38.640> I<00:10:38.760> wanna<00:10:38.880> I<00:10:39.180> wanna<00:10:39.360> say<00:10:39.540> that<00:10:39.720> I<00:10:39.959> I<00:10:40.140> find 00:10:40.370 --> 00:10:40.380 align:start position:0% and I wanna I wanna say that I I find 00:10:40.380 --> 00:10:42.290 align:start position:0% and I wanna I wanna say that I I find this<00:10:40.500> actually<00:10:40.680> awesome<00:10:40.980> and<00:10:41.940> I<00:10:42.060> find<00:10:42.180> it 00:10:42.290 --> 00:10:42.300 align:start position:0% this actually awesome and I find it 00:10:42.300 --> 00:10:44.630 align:start position:0% this actually awesome and I find it awesome<00:10:42.480> because<00:10:42.779> I<00:10:43.140> think<00:10:43.260> that<00:10:43.980> there's<00:10:44.399> a 00:10:44.630 --> 00:10:44.640 align:start position:0% awesome because I think that there's a 00:10:44.640 --> 00:10:47.030 align:start position:0% awesome because I think that there's a difference<00:10:44.820> between<00:10:45.240> a<00:10:45.959> a<00:10:46.380> temporarily 00:10:47.030 --> 00:10:47.040 align:start position:0% difference between a a temporarily 00:10:47.040 --> 00:10:50.329 align:start position:0% difference between a a temporarily emergent<00:10:47.820> consensus<00:10:48.420> and<00:10:49.140> a<00:10:49.380> consensus<00:10:49.860> that 00:10:50.329 --> 00:10:50.339 align:start position:0% emergent consensus and a consensus that 00:10:50.339 --> 00:10:52.490 align:start position:0% emergent consensus and a consensus that is<00:10:50.519> more<00:10:51.060> like<00:10:51.300> spontaneous<00:10:51.899> and<00:10:52.320> probably 00:10:52.490 --> 00:10:52.500 align:start position:0% is more like spontaneous and probably 00:10:52.500 --> 00:10:54.889 align:start position:0% is more like spontaneous and probably like<00:10:52.860> from<00:10:53.160> this<00:10:53.399> kind<00:10:53.579> of<00:10:53.700> like<00:10:53.820> uh<00:10:54.660> you<00:10:54.839> know 00:10:54.889 --> 00:10:54.899 align:start position:0% like from this kind of like uh you know 00:10:54.899 --> 00:10:57.710 align:start position:0% like from this kind of like uh you know like<00:10:55.019> group<00:10:55.320> or<00:10:55.560> a<00:10:56.100> committee<00:10:56.519> of<00:10:56.700> experts<00:10:57.240> and 00:10:57.710 --> 00:10:57.720 align:start position:0% like group or a committee of experts and 00:10:57.720 --> 00:11:00.290 align:start position:0% like group or a committee of experts and so<00:10:57.899> I<00:10:58.079> I've<00:10:58.320> tried<00:10:58.620> to<00:10:58.740> visualize<00:10:59.279> that<00:10:59.640> with 00:11:00.290 --> 00:11:00.300 align:start position:0% so I I've tried to visualize that with 00:11:00.300 --> 00:11:02.630 align:start position:0% so I I've tried to visualize that with the<00:11:00.480> two<00:11:00.720> different<00:11:00.959> kind<00:11:01.680> of<00:11:01.800> approaches<00:11:02.339> the 00:11:02.630 --> 00:11:02.640 align:start position:0% the two different kind of approaches the 00:11:02.640 --> 00:11:04.850 align:start position:0% the two different kind of approaches the two<00:11:03.120> different<00:11:03.300> extremes<00:11:03.959> so<00:11:04.140> to<00:11:04.320> say<00:11:04.500> where 00:11:04.850 --> 00:11:04.860 align:start position:0% two different extremes so to say where 00:11:04.860 --> 00:11:07.190 align:start position:0% two different extremes so to say where you<00:11:05.399> know<00:11:05.459> on<00:11:05.640> one<00:11:05.820> side<00:11:05.940> we<00:11:06.240> have<00:11:06.420> more<00:11:06.600> like<00:11:06.839> a 00:11:07.190 --> 00:11:07.200 align:start position:0% you know on one side we have more like a 00:11:07.200 --> 00:11:10.009 align:start position:0% you know on one side we have more like a market<00:11:08.040> driven<00:11:08.519> adoption<00:11:09.060> where<00:11:09.420> the 00:11:10.009 --> 00:11:10.019 align:start position:0% market driven adoption where the 00:11:10.019 --> 00:11:12.650 align:start position:0% market driven adoption where the individual<00:11:10.500> kind<00:11:10.860> of<00:11:11.040> uh<00:11:11.700> makes<00:11:12.180> the<00:11:12.360> decision 00:11:12.650 --> 00:11:12.660 align:start position:0% individual kind of uh makes the decision 00:11:12.660 --> 00:11:14.690 align:start position:0% individual kind of uh makes the decision by<00:11:12.959> themselves<00:11:13.380> they<00:11:13.800> they<00:11:14.100> do<00:11:14.339> all<00:11:14.459> of<00:11:14.579> the 00:11:14.690 --> 00:11:14.700 align:start position:0% by themselves they they do all of the 00:11:14.700 --> 00:11:16.730 align:start position:0% by themselves they they do all of the due<00:11:14.940> diligence<00:11:15.300> and<00:11:15.959> and<00:11:16.140> they<00:11:16.320> come<00:11:16.440> to<00:11:16.560> the 00:11:16.730 --> 00:11:16.740 align:start position:0% due diligence and and they come to the 00:11:16.740 --> 00:11:17.990 align:start position:0% due diligence and and they come to the conclusion<00:11:17.100> that<00:11:17.279> they<00:11:17.459> want<00:11:17.579> to<00:11:17.700> use<00:11:17.820> a 00:11:17.990 --> 00:11:18.000 align:start position:0% conclusion that they want to use a 00:11:18.000 --> 00:11:21.590 align:start position:0% conclusion that they want to use a standard<00:11:18.360> and<00:11:19.019> then<00:11:19.200> on<00:11:20.100> the<00:11:20.220> other<00:11:20.279> hand<00:11:20.600> and 00:11:21.590 --> 00:11:21.600 align:start position:0% standard and then on the other hand and 00:11:21.600 --> 00:11:24.889 align:start position:0% standard and then on the other hand and this<00:11:21.779> is<00:11:21.899> maybe<00:11:22.079> true<00:11:22.500> for<00:11:23.000> uh<00:11:24.000> yeah<00:11:24.360> like<00:11:24.600> more 00:11:24.889 --> 00:11:24.899 align:start position:0% this is maybe true for uh yeah like more 00:11:24.899 --> 00:11:27.050 align:start position:0% this is maybe true for uh yeah like more I<00:11:25.500> think<00:11:25.620> like<00:11:25.920> groups<00:11:26.519> that<00:11:26.640> have<00:11:26.820> to<00:11:26.940> make 00:11:27.050 --> 00:11:27.060 align:start position:0% I think like groups that have to make 00:11:27.060 --> 00:11:30.170 align:start position:0% I think like groups that have to make decisions<00:11:27.540> rather<00:11:28.200> quickly<00:11:28.740> and<00:11:29.040> and<00:11:29.220> like<00:11:29.700> uh 00:11:30.170 --> 00:11:30.180 align:start position:0% decisions rather quickly and and like uh 00:11:30.180 --> 00:11:32.210 align:start position:0% decisions rather quickly and and like uh yeah<00:11:30.420> like<00:11:30.899> close<00:11:31.140> to<00:11:31.380> time<00:11:31.560> I<00:11:31.800> think<00:11:31.920> you<00:11:32.100> have 00:11:32.210 --> 00:11:32.220 align:start position:0% yeah like close to time I think you have 00:11:32.220 --> 00:11:34.610 align:start position:0% yeah like close to time I think you have this<00:11:32.579> basically<00:11:33.240> this<00:11:33.600> this<00:11:33.779> spontaneous 00:11:34.610 --> 00:11:34.620 align:start position:0% this basically this this spontaneous 00:11:34.620 --> 00:11:37.310 align:start position:0% this basically this this spontaneous committee<00:11:35.220> consensus<00:11:36.000> where<00:11:36.480> you<00:11:36.720> know<00:11:36.839> 51 00:11:37.310 --> 00:11:37.320 align:start position:0% committee consensus where you know 51 00:11:37.320 --> 00:11:42.410 align:start position:0% committee consensus where you know 51 can<00:11:38.040> basically<00:11:38.779> overrule<00:11:39.779> the<00:11:40.019> uh<00:11:40.860> 49<00:11:41.279> and<00:11:42.240> I 00:11:42.410 --> 00:11:42.420 align:start position:0% can basically overrule the uh 49 and I 00:11:42.420 --> 00:11:45.170 align:start position:0% can basically overrule the uh 49 and I and<00:11:42.600> I<00:11:42.959> want<00:11:43.019> to<00:11:43.200> make<00:11:43.320> I<00:11:43.800> just<00:11:44.160> want<00:11:44.399> to<00:11:44.579> uh 00:11:45.170 --> 00:11:45.180 align:start position:0% and I want to make I just want to uh 00:11:45.180 --> 00:11:47.569 align:start position:0% and I want to make I just want to uh kind<00:11:45.660> of<00:11:45.779> make<00:11:45.959> this<00:11:46.200> argument<00:11:46.560> that<00:11:46.980> you<00:11:47.519> know 00:11:47.569 --> 00:11:47.579 align:start position:0% kind of make this argument that you know 00:11:47.579 --> 00:11:50.630 align:start position:0% kind of make this argument that you know I<00:11:47.880> I<00:11:48.120> believe<00:11:48.360> that<00:11:48.839> the<00:11:49.019> temporarily<00:11:49.740> uh 00:11:50.630 --> 00:11:50.640 align:start position:0% I I believe that the temporarily uh 00:11:50.640 --> 00:11:52.550 align:start position:0% I I believe that the temporarily uh continuously<00:11:51.300> emerging<00:11:51.839> consensus<00:11:52.380> is 00:11:52.550 --> 00:11:52.560 align:start position:0% continuously emerging consensus is 00:11:52.560 --> 00:11:54.590 align:start position:0% continuously emerging consensus is actually<00:11:52.740> the<00:11:53.100> the<00:11:53.339> cooler<00:11:53.760> one<00:11:53.880> the<00:11:54.120> the<00:11:54.300> one 00:11:54.590 --> 00:11:54.600 align:start position:0% actually the the cooler one the the one 00:11:54.600 --> 00:11:57.230 align:start position:0% actually the the cooler one the the one that<00:11:54.779> has<00:11:55.560> like<00:11:55.860> a<00:11:55.980> that<00:11:56.459> ends<00:11:56.760> up<00:11:56.820> having<00:11:57.000> like 00:11:57.230 --> 00:11:57.240 align:start position:0% that has like a that ends up having like 00:11:57.240 --> 00:12:00.050 align:start position:0% that has like a that ends up having like a<00:11:57.420> stronger<00:11:57.779> signal<00:11:58.079> over<00:11:58.740> time<00:11:59.040> and<00:11:59.880> that's 00:12:00.050 --> 00:12:00.060 align:start position:0% a stronger signal over time and that's 00:12:00.060 --> 00:12:02.030 align:start position:0% a stronger signal over time and that's because<00:12:00.300> I<00:12:00.720> I<00:12:00.839> mean<00:12:01.019> there's<00:12:01.200> one<00:12:01.440> hecky<00:12:01.860> way 00:12:02.030 --> 00:12:02.040 align:start position:0% because I I mean there's one hecky way 00:12:02.040 --> 00:12:04.490 align:start position:0% because I I mean there's one hecky way of<00:12:02.160> just<00:12:02.339> like<00:12:02.459> proving<00:12:02.880> that<00:12:03.060> and<00:12:03.480> that's<00:12:03.779> uh 00:12:04.490 --> 00:12:04.500 align:start position:0% of just like proving that and that's uh 00:12:04.500 --> 00:12:05.870 align:start position:0% of just like proving that and that's uh that<00:12:04.740> if<00:12:04.980> you<00:12:05.100> consider<00:12:05.399> like<00:12:05.640> how 00:12:05.870 --> 00:12:05.880 align:start position:0% that if you consider like how 00:12:05.880 --> 00:12:08.150 align:start position:0% that if you consider like how organizations<00:12:06.480> are<00:12:06.720> run<00:12:06.959> today<00:12:07.140> then<00:12:07.920> it's 00:12:08.150 --> 00:12:08.160 align:start position:0% organizations are run today then it's 00:12:08.160 --> 00:12:11.829 align:start position:0% organizations are run today then it's probably<00:12:08.399> mostly<00:12:08.820> in<00:12:09.000> like<00:12:09.240> this<00:12:09.420> 51<00:12:10.339> 51 00:12:11.829 --> 00:12:11.839 align:start position:0% probably mostly in like this 51 51 00:12:11.839 --> 00:12:14.750 align:start position:0% probably mostly in like this 51 51 consensus<00:12:12.839> style<00:12:13.140> right<00:12:13.800> and<00:12:14.279> then<00:12:14.399> on<00:12:14.640> the 00:12:14.750 --> 00:12:14.760 align:start position:0% consensus style right and then on the 00:12:14.760 --> 00:12:17.470 align:start position:0% consensus style right and then on the other<00:12:14.880> side<00:12:15.240> you<00:12:15.480> have<00:12:15.660> this<00:12:15.899> totally<00:12:16.620> chaotic 00:12:17.470 --> 00:12:17.480 align:start position:0% other side you have this totally chaotic 00:12:17.480 --> 00:12:19.970 align:start position:0% other side you have this totally chaotic evolutionary<00:12:18.480> kind<00:12:18.779> of<00:12:18.899> thing<00:12:19.019> that<00:12:19.380> that<00:12:19.680> is 00:12:19.970 --> 00:12:19.980 align:start position:0% evolutionary kind of thing that that is 00:12:19.980 --> 00:12:22.310 align:start position:0% evolutionary kind of thing that that is the<00:12:20.160> market<00:12:20.279> that<00:12:20.880> somehow<00:12:21.480> also<00:12:21.839> figures<00:12:22.200> out 00:12:22.310 --> 00:12:22.320 align:start position:0% the market that somehow also figures out 00:12:22.320 --> 00:12:23.990 align:start position:0% the market that somehow also figures out like<00:12:22.560> what<00:12:22.800> is<00:12:22.920> the<00:12:23.100> best<00:12:23.220> decision<00:12:23.579> but 00:12:23.990 --> 00:12:24.000 align:start position:0% like what is the best decision but 00:12:24.000 --> 00:12:26.750 align:start position:0% like what is the best decision but completely<00:12:24.959> different<00:12:25.320> and<00:12:25.800> not<00:12:26.339> by<00:12:26.579> talking 00:12:26.750 --> 00:12:26.760 align:start position:0% completely different and not by talking 00:12:26.760 --> 00:12:29.449 align:start position:0% completely different and not by talking to<00:12:27.000> each<00:12:27.120> other<00:12:27.240> and<00:12:27.720> so<00:12:27.899> I<00:12:28.079> I<00:12:28.320> think<00:12:28.620> and<00:12:29.160> I 00:12:29.449 --> 00:12:29.459 align:start position:0% to each other and so I I think and I 00:12:29.459 --> 00:12:31.069 align:start position:0% to each other and so I I think and I mean<00:12:29.579> by<00:12:29.760> no<00:12:29.940> means<00:12:30.120> is<00:12:30.360> this<00:12:30.600> uh<00:12:30.899> Financial 00:12:31.069 --> 00:12:31.079 align:start position:0% mean by no means is this uh Financial 00:12:31.079 --> 00:12:33.230 align:start position:0% mean by no means is this uh Financial advice<00:12:31.560> but<00:12:31.800> I<00:12:31.980> I<00:12:32.220> would<00:12:32.459> always<00:12:32.579> bet<00:12:32.880> on<00:12:33.120> the 00:12:33.230 --> 00:12:33.240 align:start position:0% advice but I I would always bet on the 00:12:33.240 --> 00:12:35.870 align:start position:0% advice but I I would always bet on the market<00:12:33.420> and<00:12:33.720> not<00:12:33.899> on<00:12:34.140> like<00:12:34.740> an<00:12:34.920> individual 00:12:35.870 --> 00:12:35.880 align:start position:0% market and not on like an individual 00:12:35.880 --> 00:12:39.889 align:start position:0% market and not on like an individual uh<00:12:37.040> committee<00:12:38.040> actually<00:12:38.339> and<00:12:39.060> and<00:12:39.240> so<00:12:39.540> I<00:12:39.720> I 00:12:39.889 --> 00:12:39.899 align:start position:0% uh committee actually and and so I I 00:12:39.899 --> 00:12:41.410 align:start position:0% uh committee actually and and so I I think<00:12:40.079> that's<00:12:40.380> that's<00:12:40.680> actually<00:12:40.980> the<00:12:41.160> better 00:12:41.410 --> 00:12:41.420 align:start position:0% think that's that's actually the better 00:12:41.420 --> 00:12:43.970 align:start position:0% think that's that's actually the better uh<00:12:42.420> the<00:12:42.540> better<00:12:42.779> approach 00:12:43.970 --> 00:12:43.980 align:start position:0% uh the better approach 00:12:43.980 --> 00:12:47.389 align:start position:0% uh the better approach and<00:12:44.760> and<00:12:45.079> also<00:12:46.079> I<00:12:46.260> mean<00:12:46.380> I<00:12:46.560> guess<00:12:46.920> it's<00:12:47.100> also 00:12:47.389 --> 00:12:47.399 align:start position:0% and and also I mean I guess it's also 00:12:47.399 --> 00:12:49.970 align:start position:0% and and also I mean I guess it's also the<00:12:47.459> reason<00:12:47.639> why<00:12:48.000> like<00:12:48.420> much<00:12:49.260> of<00:12:49.500> our<00:12:49.620> critical 00:12:49.970 --> 00:12:49.980 align:start position:0% the reason why like much of our critical 00:12:49.980 --> 00:12:52.069 align:start position:0% the reason why like much of our critical infrastructure<00:12:50.579> is<00:12:50.820> like<00:12:51.120> running<00:12:51.540> that<00:12:51.899> way 00:12:52.069 --> 00:12:52.079 align:start position:0% infrastructure is like running that way 00:12:52.079 --> 00:12:54.590 align:start position:0% infrastructure is like running that way like<00:12:52.380> I<00:12:52.920> don't<00:12:52.980> think<00:12:53.100> there's<00:12:53.339> like<00:12:53.639> a<00:12:53.940> you 00:12:54.590 --> 00:12:54.600 align:start position:0% like I don't think there's like a you 00:12:54.600 --> 00:12:56.389 align:start position:0% like I don't think there's like a you know<00:12:54.720> like<00:12:54.899> a<00:12:55.139> central<00:12:55.380> planning<00:12:55.920> for<00:12:56.160> the 00:12:56.389 --> 00:12:56.399 align:start position:0% know like a central planning for the 00:12:56.399 --> 00:12:59.030 align:start position:0% know like a central planning for the Food<00:12:56.579> Network<00:12:56.880> in<00:12:57.300> a<00:12:57.420> city<00:12:57.600> or<00:12:57.899> uh<00:12:58.620> stuff<00:12:58.860> like 00:12:59.030 --> 00:12:59.040 align:start position:0% Food Network in a city or uh stuff like 00:12:59.040 --> 00:13:00.470 align:start position:0% Food Network in a city or uh stuff like that 00:13:00.470 --> 00:13:00.480 align:start position:0% that 00:13:00.480 --> 00:13:04.069 align:start position:0% that um 00:13:04.069 --> 00:13:04.079 align:start position:0% 00:13:04.079 --> 00:13:06.530 align:start position:0% and<00:13:04.860> so 00:13:06.530 --> 00:13:06.540 align:start position:0% and so 00:13:06.540 --> 00:13:09.350 align:start position:0% and so so<00:13:06.959> the<00:13:07.500> question<00:13:07.680> is<00:13:07.920> though<00:13:08.160> like<00:13:08.459> how<00:13:09.120> how 00:13:09.350 --> 00:13:09.360 align:start position:0% so the question is though like how how 00:13:09.360 --> 00:13:11.389 align:start position:0% so the question is though like how how can<00:13:09.600> we<00:13:09.779> overcome<00:13:10.200> this<00:13:10.560> this<00:13:10.800> uh<00:13:11.160> this 00:13:11.389 --> 00:13:11.399 align:start position:0% can we overcome this this uh this 00:13:11.399 --> 00:13:13.550 align:start position:0% can we overcome this this uh this immutability<00:13:11.940> of<00:13:12.360> of<00:13:12.540> contracts<00:13:13.079> and<00:13:13.260> how<00:13:13.440> can 00:13:13.550 --> 00:13:13.560 align:start position:0% immutability of of contracts and how can 00:13:13.560 --> 00:13:15.829 align:start position:0% immutability of of contracts and how can we<00:13:13.740> actually<00:13:13.920> still<00:13:14.480> innovate<00:13:15.480> on<00:13:15.720> those 00:13:15.829 --> 00:13:15.839 align:start position:0% we actually still innovate on those 00:13:15.839 --> 00:13:17.629 align:start position:0% we actually still innovate on those standards<00:13:16.380> and<00:13:16.560> and<00:13:16.800> this<00:13:17.100> is<00:13:17.220> especially 00:13:17.629 --> 00:13:17.639 align:start position:0% standards and and this is especially 00:13:17.639 --> 00:13:20.930 align:start position:0% standards and and this is especially true<00:13:17.940> with<00:13:18.420> uh<00:13:18.959> with<00:13:19.380> all<00:13:19.620> of<00:13:19.740> the<00:13:20.040> like<00:13:20.700> this 00:13:20.930 --> 00:13:20.940 align:start position:0% true with uh with all of the like this 00:13:20.940 --> 00:13:23.569 align:start position:0% true with uh with all of the like this you<00:13:21.360> know<00:13:21.480> all<00:13:21.779> of<00:13:21.899> the<00:13:22.019> eyeballs<00:13:22.560> that<00:13:22.740> have 00:13:23.569 --> 00:13:23.579 align:start position:0% you know all of the eyeballs that have 00:13:23.579 --> 00:13:26.569 align:start position:0% you know all of the eyeballs that have have<00:13:23.880> like<00:13:24.120> went<00:13:24.360> into<00:13:24.660> the<00:13:24.959> nft<00:13:25.260> space<00:13:25.680> and 00:13:26.569 --> 00:13:26.579 align:start position:0% have like went into the nft space and 00:13:26.579 --> 00:13:29.389 align:start position:0% have like went into the nft space and and<00:13:26.820> you<00:13:27.300> know<00:13:27.360> kind<00:13:27.600> of<00:13:27.720> this<00:13:28.019> difficulty<00:13:28.980> of 00:13:29.389 --> 00:13:29.399 align:start position:0% and you know kind of this difficulty of 00:13:29.399 --> 00:13:32.150 align:start position:0% and you know kind of this difficulty of of<00:13:29.820> innovating<00:13:30.779> with<00:13:31.079> the<00:13:31.260> standard<00:13:31.620> and<00:13:31.920> and 00:13:32.150 --> 00:13:32.160 align:start position:0% of innovating with the standard and and 00:13:32.160 --> 00:13:34.190 align:start position:0% of innovating with the standard and and I<00:13:32.639> mean<00:13:32.760> sadly<00:13:33.120> also<00:13:33.480> with<00:13:33.779> being 00:13:34.190 --> 00:13:34.200 align:start position:0% I mean sadly also with being 00:13:34.200 --> 00:13:35.810 align:start position:0% I mean sadly also with being non-compliant<00:13:34.860> to<00:13:35.040> the<00:13:35.220> standard<00:13:35.519> and<00:13:35.700> just 00:13:35.810 --> 00:13:35.820 align:start position:0% non-compliant to the standard and just 00:13:35.820 --> 00:13:38.389 align:start position:0% non-compliant to the standard and just trying<00:13:36.060> to<00:13:36.180> grow<00:13:36.480> uh<00:13:37.380> externally<00:13:38.160> from 00:13:38.389 --> 00:13:38.399 align:start position:0% trying to grow uh externally from 00:13:38.399 --> 00:13:41.449 align:start position:0% trying to grow uh externally from standards<00:13:39.000> and<00:13:39.720> and<00:13:39.899> so<00:13:40.399> I<00:13:41.399> think 00:13:41.449 --> 00:13:41.459 align:start position:0% standards and and so I think 00:13:41.459 --> 00:13:43.870 align:start position:0% standards and and so I think immutability<00:13:42.240> does<00:13:42.600> not<00:13:42.839> necessarily<00:13:43.440> mean 00:13:43.870 --> 00:13:43.880 align:start position:0% immutability does not necessarily mean 00:13:43.880 --> 00:13:47.690 align:start position:0% immutability does not necessarily mean uh<00:13:44.959> stagnation<00:13:45.959> I<00:13:46.200> I<00:13:46.380> think<00:13:46.620> actually<00:13:46.800> there 00:13:47.690 --> 00:13:47.700 align:start position:0% uh stagnation I I think actually there 00:13:47.700 --> 00:13:50.530 align:start position:0% uh stagnation I I think actually there is<00:13:47.880> now<00:13:48.180> we<00:13:48.839> are<00:13:49.019> starting<00:13:49.380> to<00:13:49.620> see<00:13:49.860> a<00:13:50.160> pattern 00:13:50.530 --> 00:13:50.540 align:start position:0% is now we are starting to see a pattern 00:13:50.540 --> 00:13:52.910 align:start position:0% is now we are starting to see a pattern emerged<00:13:51.540> where<00:13:51.720> people<00:13:51.899> are<00:13:52.260> starting<00:13:52.680> to 00:13:52.910 --> 00:13:52.920 align:start position:0% emerged where people are starting to 00:13:52.920 --> 00:13:54.829 align:start position:0% emerged where people are starting to really<00:13:53.100> upgrade<00:13:53.519> the<00:13:53.700> standard<00:13:54.060> and<00:13:54.540> they<00:13:54.720> are 00:13:54.829 --> 00:13:54.839 align:start position:0% really upgrade the standard and they are 00:13:54.839 --> 00:13:56.690 align:start position:0% really upgrade the standard and they are doing<00:13:54.959> it<00:13:55.200> in<00:13:55.380> a<00:13:55.500> way<00:13:55.620> where<00:13:56.220> they<00:13:56.519> are 00:13:56.690 --> 00:13:56.700 align:start position:0% doing it in a way where they are 00:13:56.700 --> 00:13:58.430 align:start position:0% doing it in a way where they are basically<00:13:57.000> like 00:13:58.430 --> 00:13:58.440 align:start position:0% basically like 00:13:58.440 --> 00:14:00.949 align:start position:0% basically like um<00:13:58.500> yeah<00:13:58.920> basically<00:13:59.880> bolting 00:14:00.949 --> 00:14:00.959 align:start position:0% um yeah basically bolting 00:14:00.959 --> 00:14:03.590 align:start position:0% um yeah basically bolting um<00:14:01.500> kind<00:14:02.100> of<00:14:02.279> this<00:14:02.700> one<00:14:02.880> lock<00:14:03.060> to<00:14:03.300> the<00:14:03.540> other 00:14:03.590 --> 00:14:03.600 align:start position:0% um kind of this one lock to the other 00:14:03.600 --> 00:14:07.730 align:start position:0% um kind of this one lock to the other almost<00:14:03.899> like<00:14:04.260> a<00:14:04.920> like<00:14:05.760> like<00:14:05.760> in<00:14:06.360> a<00:14:07.079> I<00:14:07.620> don't 00:14:07.730 --> 00:14:07.740 align:start position:0% almost like a like like in a I don't 00:14:07.740 --> 00:14:09.350 align:start position:0% almost like a like like in a I don't know<00:14:07.860> on<00:14:08.040> these<00:14:08.279> bridges<00:14:08.639> that<00:14:08.880> sometimes<00:14:09.240> you 00:14:09.350 --> 00:14:09.360 align:start position:0% know on these bridges that sometimes you 00:14:09.360 --> 00:14:12.110 align:start position:0% know on these bridges that sometimes you can<00:14:09.540> see<00:14:09.660> as<00:14:09.959> a<00:14:10.139> tourist<00:14:10.560> kind<00:14:11.220> of<00:14:11.339> thing<00:14:11.459> so<00:14:11.760> so 00:14:12.110 --> 00:14:12.120 align:start position:0% can see as a tourist kind of thing so so 00:14:12.120 --> 00:14:15.050 align:start position:0% can see as a tourist kind of thing so so I<00:14:12.480> think<00:14:13.079> um<00:14:13.139> over<00:14:13.620> the<00:14:14.040> last<00:14:14.459> half<00:14:14.700> a<00:14:14.940> year 00:14:15.050 --> 00:14:15.060 align:start position:0% I think um over the last half a year 00:14:15.060 --> 00:14:17.870 align:start position:0% I think um over the last half a year that<00:14:15.480> has<00:14:15.600> really<00:14:15.839> happened<00:14:16.019> so<00:14:16.740> uh<00:14:17.639> for 00:14:17.870 --> 00:14:17.880 align:start position:0% that has really happened so uh for 00:14:17.880 --> 00:14:22.009 align:start position:0% that has really happened so uh for example<00:14:18.120> we<00:14:18.839> now<00:14:19.200> have<00:14:19.560> a<00:14:20.160> standard<00:14:20.720> uh<00:14:21.720> event 00:14:22.009 --> 00:14:22.019 align:start position:0% example we now have a standard uh event 00:14:22.019 --> 00:14:25.810 align:start position:0% example we now have a standard uh event for<00:14:22.560> emitting<00:14:23.279> a<00:14:23.880> uh<00:14:24.660> an<00:14:24.899> event<00:14:25.019> when<00:14:25.380> the 00:14:25.810 --> 00:14:25.820 align:start position:0% for emitting a uh an event when the 00:14:25.820 --> 00:14:28.610 align:start position:0% for emitting a uh an event when the metadata<00:14:26.820> is<00:14:27.000> updated<00:14:27.360> in<00:14:27.600> in<00:14:28.019> an<00:14:28.200> NLT 00:14:28.610 --> 00:14:28.620 align:start position:0% metadata is updated in in an NLT 00:14:28.620 --> 00:14:30.949 align:start position:0% metadata is updated in in an NLT standard<00:14:29.040> and<00:14:29.220> that's<00:14:29.459> uh<00:14:30.180> the<00:14:30.360> one<00:14:30.540> on<00:14:30.720> the 00:14:30.949 --> 00:14:30.959 align:start position:0% standard and that's uh the one on the 00:14:30.959 --> 00:14:34.970 align:start position:0% standard and that's uh the one on the top<00:14:31.500> right<00:14:31.680> it's<00:14:32.100> the<00:14:32.720> 4906<00:14:33.720> that<00:14:34.560> essentially 00:14:34.970 --> 00:14:34.980 align:start position:0% top right it's the 4906 that essentially 00:14:34.980 --> 00:14:37.810 align:start position:0% top right it's the 4906 that essentially just<00:14:35.220> emits<00:14:35.760> an<00:14:35.820> event<00:14:36.000> we<00:14:36.720> now<00:14:36.839> have<00:14:37.200> a<00:14:37.500> very 00:14:37.810 --> 00:14:37.820 align:start position:0% just emits an event we now have a very 00:14:37.820 --> 00:14:40.269 align:start position:0% just emits an event we now have a very uh<00:14:38.820> interesting 00:14:40.269 --> 00:14:40.279 align:start position:0% uh interesting 00:14:40.279 --> 00:14:43.730 align:start position:0% uh interesting standard<00:14:41.279> for<00:14:41.579> that<00:14:42.060> basically<00:14:42.540> splits<00:14:43.019> the 00:14:43.730 --> 00:14:43.740 align:start position:0% standard for that basically splits the 00:14:43.740 --> 00:14:45.710 align:start position:0% standard for that basically splits the user<00:14:44.100> and<00:14:44.339> the<00:14:44.519> owner<00:14:44.820> into<00:14:45.180> two<00:14:45.480> different 00:14:45.710 --> 00:14:45.720 align:start position:0% user and the owner into two different 00:14:45.720 --> 00:14:48.590 align:start position:0% user and the owner into two different groups<00:14:46.380> and<00:14:46.680> I<00:14:47.160> think<00:14:47.279> especially<00:14:47.760> with<00:14:48.060> you 00:14:48.590 --> 00:14:48.600 align:start position:0% groups and I think especially with you 00:14:48.600 --> 00:14:50.750 align:start position:0% groups and I think especially with you know<00:14:48.660> with<00:14:48.899> d-soc<00:14:49.440> kind<00:14:49.920> of<00:14:50.040> making<00:14:50.220> us<00:14:50.459> aware 00:14:50.750 --> 00:14:50.760 align:start position:0% know with d-soc kind of making us aware 00:14:50.760 --> 00:14:53.269 align:start position:0% know with d-soc kind of making us aware that<00:14:51.120> there<00:14:51.600> are<00:14:51.779> only<00:14:52.019> that<00:14:52.380> that<00:14:52.680> there<00:14:53.160> are 00:14:53.269 --> 00:14:53.279 align:start position:0% that there are only that that there are 00:14:53.279 --> 00:14:55.730 align:start position:0% that there are only that that there are like<00:14:53.459> subsets<00:14:53.940> of<00:14:54.180> ownership<00:14:54.540> where<00:14:55.380> kind<00:14:55.680> of 00:14:55.730 --> 00:14:55.740 align:start position:0% like subsets of ownership where kind of 00:14:55.740 --> 00:14:57.290 align:start position:0% like subsets of ownership where kind of ownership<00:14:56.100> represents<00:14:56.760> this<00:14:56.880> bucket<00:14:57.180> of 00:14:57.290 --> 00:14:57.300 align:start position:0% ownership represents this bucket of 00:14:57.300 --> 00:14:58.910 align:start position:0% ownership represents this bucket of right<00:14:57.480> and<00:14:57.720> then<00:14:57.899> you<00:14:58.440> know<00:14:58.500> you<00:14:58.740> can<00:14:58.860> have 00:14:58.910 --> 00:14:58.920 align:start position:0% right and then you know you can have 00:14:58.920 --> 00:15:01.730 align:start position:0% right and then you know you can have fructose<00:14:59.459> and<00:14:59.760> you're<00:14:59.940> kind<00:15:00.180> of<00:15:00.300> Usos<00:15:01.019> and 00:15:01.730 --> 00:15:01.740 align:start position:0% fructose and you're kind of Usos and 00:15:01.740 --> 00:15:04.009 align:start position:0% fructose and you're kind of Usos and abusers<00:15:02.639> and<00:15:02.940> so<00:15:03.060> on 00:15:04.009 --> 00:15:04.019 align:start position:0% abusers and so on 00:15:04.019 --> 00:15:05.750 align:start position:0% abusers and so on um<00:15:04.139> this<00:15:04.560> this<00:15:04.860> is<00:15:05.040> starting<00:15:05.220> to<00:15:05.399> become 00:15:05.750 --> 00:15:05.760 align:start position:0% um this this is starting to become 00:15:05.760 --> 00:15:07.610 align:start position:0% um this this is starting to become really<00:15:06.180> really<00:15:06.300> interesting<00:15:06.720> right<00:15:07.019> we<00:15:07.440> have 00:15:07.610 --> 00:15:07.620 align:start position:0% really really interesting right we have 00:15:07.620 --> 00:15:10.250 align:start position:0% really really interesting right we have like<00:15:07.740> different<00:15:08.300> kind<00:15:09.300> of<00:15:09.480> roles<00:15:09.839> that<00:15:10.139> could 00:15:10.250 --> 00:15:10.260 align:start position:0% like different kind of roles that could 00:15:10.260 --> 00:15:12.829 align:start position:0% like different kind of roles that could interact<00:15:10.680> with<00:15:10.980> the<00:15:11.279> nft<00:15:11.820> and<00:15:12.180> then<00:15:12.360> this 00:15:12.829 --> 00:15:12.839 align:start position:0% interact with the nft and then this 00:15:12.839 --> 00:15:14.990 align:start position:0% interact with the nft and then this could<00:15:13.019> have<00:15:13.260> like<00:15:13.740> different<00:15:13.980> economies<00:15:14.820> and 00:15:14.990 --> 00:15:15.000 align:start position:0% could have like different economies and 00:15:15.000 --> 00:15:16.790 align:start position:0% could have like different economies and so<00:15:15.180> that's<00:15:15.480> I<00:15:16.019> want<00:15:16.139> to<00:15:16.260> give<00:15:16.320> a<00:15:16.440> shout<00:15:16.680> out 00:15:16.790 --> 00:15:16.800 align:start position:0% so that's I want to give a shout out 00:15:16.800 --> 00:15:18.829 align:start position:0% so that's I want to give a shout out that's<00:15:17.160> 4907 00:15:18.829 --> 00:15:18.839 align:start position:0% that's 4907 00:15:18.839 --> 00:15:21.530 align:start position:0% that's 4907 and<00:15:19.320> then<00:15:19.440> I<00:15:19.620> guess<00:15:19.980> maybe<00:15:20.220> like<00:15:20.579> a<00:15:20.940> a<00:15:21.300> more 00:15:21.530 --> 00:15:21.540 align:start position:0% and then I guess maybe like a a more 00:15:21.540 --> 00:15:24.310 align:start position:0% and then I guess maybe like a a more Infamous<00:15:21.899> one<00:15:22.320> is<00:15:22.620> the<00:15:22.860> is<00:15:23.100> the<00:15:23.339> royalties<00:15:23.760> one 00:15:24.310 --> 00:15:24.320 align:start position:0% Infamous one is the is the royalties one 00:15:24.320 --> 00:15:27.350 align:start position:0% Infamous one is the is the royalties one and<00:15:25.320> it's<00:15:25.500> the<00:15:25.740> 2980 00:15:27.350 --> 00:15:27.360 align:start position:0% and it's the 2980 00:15:27.360 --> 00:15:32.110 align:start position:0% and it's the 2980 81<00:15:28.199> and<00:15:29.040> that's<00:15:29.339> basically<00:15:29.940> an<00:15:30.360> optional 00:15:32.110 --> 00:15:32.120 align:start position:0% 81 and that's basically an optional 00:15:32.120 --> 00:15:36.110 align:start position:0% 81 and that's basically an optional an<00:15:33.120> an<00:15:33.600> optional<00:15:34.279> royalties<00:15:35.279> location 00:15:36.110 --> 00:15:36.120 align:start position:0% an an optional royalties location 00:15:36.120 --> 00:15:38.990 align:start position:0% an an optional royalties location mechanism<00:15:36.779> for<00:15:37.019> nfts<00:15:37.680> that<00:15:38.160> is<00:15:38.339> implemented<00:15:38.760> I 00:15:38.990 --> 00:15:39.000 align:start position:0% mechanism for nfts that is implemented I 00:15:39.000 --> 00:15:42.230 align:start position:0% mechanism for nfts that is implemented I think<00:15:39.120> in<00:15:39.959> uh<00:15:40.320> in<00:15:40.560> many<00:15:40.680> nft<00:15:40.980> marketplaces<00:15:41.820> and 00:15:42.230 --> 00:15:42.240 align:start position:0% think in uh in many nft marketplaces and 00:15:42.240 --> 00:15:43.970 align:start position:0% think in uh in many nft marketplaces and and<00:15:42.360> again<00:15:42.839> I<00:15:43.079> I<00:15:43.199> just<00:15:43.440> want<00:15:43.560> to<00:15:43.680> highlight 00:15:43.970 --> 00:15:43.980 align:start position:0% and again I I just want to highlight 00:15:43.980 --> 00:15:45.650 align:start position:0% and again I I just want to highlight that<00:15:44.220> I<00:15:44.399> think<00:15:44.459> it<00:15:44.699> is<00:15:44.880> definitely<00:15:45.240> possible 00:15:45.650 --> 00:15:45.660 align:start position:0% that I think it is definitely possible 00:15:45.660 --> 00:15:48.290 align:start position:0% that I think it is definitely possible to<00:15:45.959> upgrade<00:15:46.380> uh<00:15:47.040> these<00:15:47.339> things<00:15:47.459> and<00:15:47.820> like<00:15:48.060> we 00:15:48.290 --> 00:15:48.300 align:start position:0% to upgrade uh these things and like we 00:15:48.300 --> 00:15:50.810 align:start position:0% to upgrade uh these things and like we are<00:15:48.480> we<00:15:48.839> are<00:15:48.959> doing<00:15:49.139> that<00:15:49.440> I<00:15:50.100> just<00:15:50.279> think<00:15:50.459> that 00:15:50.810 --> 00:15:50.820 align:start position:0% are we are doing that I just think that 00:15:50.820 --> 00:15:52.790 align:start position:0% are we are doing that I just think that probably<00:15:51.060> the<00:15:51.779> time<00:15:51.959> Horizon<00:15:52.320> that<00:15:52.680> we're 00:15:52.790 --> 00:15:52.800 align:start position:0% probably the time Horizon that we're 00:15:52.800 --> 00:15:55.370 align:start position:0% probably the time Horizon that we're looking<00:15:52.980> at<00:15:53.279> this<00:15:53.459> and<00:15:54.240> where<00:15:54.779> you<00:15:55.079> know<00:15:55.139> we're 00:15:55.370 --> 00:15:55.380 align:start position:0% looking at this and where you know we're 00:15:55.380 --> 00:15:57.350 align:start position:0% looking at this and where you know we're like<00:15:55.620> drawn<00:15:56.339> to<00:15:56.459> being<00:15:56.760> a<00:15:57.060> bit<00:15:57.120> more 00:15:57.350 --> 00:15:57.360 align:start position:0% like drawn to being a bit more 00:15:57.360 --> 00:16:00.710 align:start position:0% like drawn to being a bit more pessimistic<00:15:58.019> I<00:15:58.500> think<00:15:58.620> maybe<00:15:58.860> we<00:15:59.100> or<00:15:59.940> I<00:16:00.540> mean 00:16:00.710 --> 00:16:00.720 align:start position:0% pessimistic I think maybe we or I mean 00:16:00.720 --> 00:16:02.930 align:start position:0% pessimistic I think maybe we or I mean personally<00:16:01.079> maybe<00:16:01.620> I<00:16:01.980> have<00:16:02.100> to<00:16:02.339> be<00:16:02.579> more 00:16:02.930 --> 00:16:02.940 align:start position:0% personally maybe I have to be more 00:16:02.940 --> 00:16:04.910 align:start position:0% personally maybe I have to be more patient<00:16:03.360> and<00:16:03.779> just<00:16:04.139> like<00:16:04.260> trust<00:16:04.620> in<00:16:04.800> the 00:16:04.910 --> 00:16:04.920 align:start position:0% patient and just like trust in the 00:16:04.920 --> 00:16:09.110 align:start position:0% patient and just like trust in the process<00:16:05.220> and<00:16:06.660> um<00:16:07.139> yeah<00:16:07.680> I<00:16:07.980> guess<00:16:08.160> I<00:16:08.820> have<00:16:08.940> five 00:16:09.110 --> 00:16:09.120 align:start position:0% process and um yeah I guess I have five 00:16:09.120 --> 00:16:11.389 align:start position:0% process and um yeah I guess I have five more<00:16:09.300> minutes<00:16:09.540> so<00:16:10.079> I'm<00:16:10.199> also<00:16:10.500> gonna<00:16:10.680> uh<00:16:11.160> of 00:16:11.389 --> 00:16:11.399 align:start position:0% more minutes so I'm also gonna uh of 00:16:11.399 --> 00:16:13.790 align:start position:0% more minutes so I'm also gonna uh of course<00:16:11.519> I'm<00:16:11.760> gonna<00:16:11.880> shill<00:16:12.360> a<00:16:12.839> uh<00:16:13.260> a<00:16:13.500> standard 00:16:13.790 --> 00:16:13.800 align:start position:0% course I'm gonna shill a uh a standard 00:16:13.800 --> 00:16:16.189 align:start position:0% course I'm gonna shill a uh a standard that<00:16:13.920> I<00:16:14.100> did<00:16:14.339> myself<00:16:14.579> which<00:16:14.940> is<00:16:15.060> the<00:16:15.360> minimum 00:16:16.189 --> 00:16:16.199 align:start position:0% that I did myself which is the minimum 00:16:16.199 --> 00:16:18.350 align:start position:0% that I did myself which is the minimum uh<00:16:16.680> So<00:16:16.860> Gone<00:16:17.100> token<00:16:17.519> and<00:16:17.639> it<00:16:17.820> works<00:16:18.060> in<00:16:18.240> the 00:16:18.350 --> 00:16:18.360 align:start position:0% uh So Gone token and it works in the 00:16:18.360 --> 00:16:20.569 align:start position:0% uh So Gone token and it works in the exact<00:16:18.600> same<00:16:18.779> way<00:16:19.019> where<00:16:19.380> basically<00:16:20.100> we<00:16:20.399> are 00:16:20.569 --> 00:16:20.579 align:start position:0% exact same way where basically we are 00:16:20.579 --> 00:16:23.990 align:start position:0% exact same way where basically we are extending<00:16:21.120> and<00:16:21.420> even<00:16:21.600> breaking<00:16:22.139> the<00:16:22.680> EAP<00:16:23.100> 721 00:16:23.990 --> 00:16:24.000 align:start position:0% extending and even breaking the EAP 721 00:16:24.000 --> 00:16:27.290 align:start position:0% extending and even breaking the EAP 721 interface<00:16:24.959> and<00:16:25.740> essentially<00:16:26.220> uh<00:16:27.120> we're 00:16:27.290 --> 00:16:27.300 align:start position:0% interface and essentially uh we're 00:16:27.300 --> 00:16:30.590 align:start position:0% interface and essentially uh we're allowing<00:16:27.779> people<00:16:27.959> to<00:16:28.440> lock<00:16:29.040> an<00:16:29.279> nft<00:16:29.579> so<00:16:30.060> you 00:16:30.590 --> 00:16:30.600 align:start position:0% allowing people to lock an nft so you 00:16:30.600 --> 00:16:33.170 align:start position:0% allowing people to lock an nft so you can<00:16:30.720> emit<00:16:31.380> a<00:16:31.560> locked<00:16:31.860> event<00:16:32.040> and<00:16:32.579> an<00:16:32.699> unlocked 00:16:33.170 --> 00:16:33.180 align:start position:0% can emit a locked event and an unlocked 00:16:33.180 --> 00:16:37.069 align:start position:0% can emit a locked event and an unlocked event<00:16:33.320> depending<00:16:34.320> on<00:16:34.740> whether<00:16:35.459> the<00:16:36.079> transfer 00:16:37.069 --> 00:16:37.079 align:start position:0% event depending on whether the transfer 00:16:37.079 --> 00:16:39.410 align:start position:0% event depending on whether the transfer function<00:16:37.380> should<00:16:37.740> be<00:16:37.980> uh<00:16:38.880> should<00:16:39.300> be 00:16:39.410 --> 00:16:39.420 align:start position:0% function should be uh should be 00:16:39.420 --> 00:16:41.389 align:start position:0% function should be uh should be reverting<00:16:39.839> or<00:16:40.019> not<00:16:40.199> and<00:16:40.620> then<00:16:40.740> we<00:16:41.040> also<00:16:41.279> have 00:16:41.389 --> 00:16:41.399 align:start position:0% reverting or not and then we also have 00:16:41.399 --> 00:16:43.730 align:start position:0% reverting or not and then we also have this<00:16:41.759> view<00:16:42.180> function<00:16:42.600> that<00:16:43.199> allows<00:16:43.500> you<00:16:43.560> to 00:16:43.730 --> 00:16:43.740 align:start position:0% this view function that allows you to 00:16:43.740 --> 00:16:45.829 align:start position:0% this view function that allows you to always<00:16:43.920> check<00:16:44.279> whether<00:16:44.880> a<00:16:45.120> token<00:16:45.480> is<00:16:45.600> locked 00:16:45.829 --> 00:16:45.839 align:start position:0% always check whether a token is locked 00:16:45.839 --> 00:16:49.430 align:start position:0% always check whether a token is locked and<00:16:46.259> the<00:16:46.560> purpose<00:16:46.800> for<00:16:47.040> this<00:16:47.220> is<00:16:47.579> that<00:16:48.779> um 00:16:49.430 --> 00:16:49.440 align:start position:0% and the purpose for this is that um 00:16:49.440 --> 00:16:51.530 align:start position:0% and the purpose for this is that um that<00:16:50.100> if<00:16:50.339> you<00:16:50.459> were<00:16:50.579> if<00:16:50.759> you<00:16:50.940> were<00:16:51.060> to<00:16:51.180> just<00:16:51.360> use 00:16:51.530 --> 00:16:51.540 align:start position:0% that if you were if you were to just use 00:16:51.540 --> 00:16:53.269 align:start position:0% that if you were if you were to just use like<00:16:51.779> the<00:16:52.019> plane 00:16:53.269 --> 00:16:53.279 align:start position:0% like the plane 00:16:53.279 --> 00:16:53.889 align:start position:0% like the plane um 00:16:53.889 --> 00:16:53.899 align:start position:0% um 00:16:53.899 --> 00:16:56.269 align:start position:0% um 721<00:16:54.899> standard<00:16:55.380> which 00:16:56.269 --> 00:16:56.279 align:start position:0% 721 standard which 00:16:56.279 --> 00:16:58.790 align:start position:0% 721 standard which actually<00:16:56.820> it<00:16:57.120> has<00:16:57.300> a<00:16:57.720> kind<00:16:58.079> of<00:16:58.199> like<00:16:58.320> a<00:16:58.560> small 00:16:58.790 --> 00:16:58.800 align:start position:0% actually it has a kind of like a small 00:16:58.800 --> 00:17:01.490 align:start position:0% actually it has a kind of like a small uh<00:16:59.759> line<00:17:00.180> in<00:17:00.480> it<00:17:00.600> where<00:17:00.839> it<00:17:00.959> says<00:17:01.079> like<00:17:01.320> that 00:17:01.490 --> 00:17:01.500 align:start position:0% uh line in it where it says like that 00:17:01.500 --> 00:17:04.429 align:start position:0% uh line in it where it says like that these<00:17:02.339> uh<00:17:02.639> nfts<00:17:03.300> can<00:17:03.480> also<00:17:03.660> be<00:17:03.779> they<00:17:04.140> can<00:17:04.319> be 00:17:04.429 --> 00:17:04.439 align:start position:0% these uh nfts can also be they can be 00:17:04.439 --> 00:17:06.590 align:start position:0% these uh nfts can also be they can be used<00:17:04.620> as<00:17:04.799> a<00:17:05.040> reader<00:17:05.339> like<00:17:05.520> a<00:17:05.760> read-only 00:17:06.590 --> 00:17:06.600 align:start position:0% used as a reader like a read-only 00:17:06.600 --> 00:17:09.890 align:start position:0% used as a reader like a read-only registry<00:17:07.559> the<00:17:08.100> problem<00:17:08.220> is<00:17:08.459> that<00:17:08.819> indexes<00:17:09.660> and 00:17:09.890 --> 00:17:09.900 align:start position:0% registry the problem is that indexes and 00:17:09.900 --> 00:17:11.569 align:start position:0% registry the problem is that indexes and wallets<00:17:10.260> and<00:17:10.500> so<00:17:10.620> on<00:17:10.799> wouldn't<00:17:11.339> really 00:17:11.569 --> 00:17:11.579 align:start position:0% wallets and so on wouldn't really 00:17:11.579 --> 00:17:13.909 align:start position:0% wallets and so on wouldn't really recognize<00:17:12.120> it<00:17:12.360> because<00:17:12.600> a<00:17:13.079> computer<00:17:13.380> cannot 00:17:13.909 --> 00:17:13.919 align:start position:0% recognize it because a computer cannot 00:17:13.919 --> 00:17:16.309 align:start position:0% recognize it because a computer cannot reason<00:17:14.100> from<00:17:14.640> let's<00:17:14.880> say<00:17:15.120> you<00:17:15.839> know<00:17:15.959> the 00:17:16.309 --> 00:17:16.319 align:start position:0% reason from let's say you know the 00:17:16.319 --> 00:17:18.230 align:start position:0% reason from let's say you know the transfer<00:17:16.679> is<00:17:16.799> reverting<00:17:17.280> to 00:17:18.230 --> 00:17:18.240 align:start position:0% transfer is reverting to 00:17:18.240 --> 00:17:20.210 align:start position:0% transfer is reverting to you<00:17:18.720> know<00:17:18.839> this<00:17:19.260> thing<00:17:19.500> is<00:17:19.620> like<00:17:19.799> locked 00:17:20.210 --> 00:17:20.220 align:start position:0% you know this thing is like locked 00:17:20.220 --> 00:17:21.530 align:start position:0% you know this thing is like locked because<00:17:20.520> it<00:17:20.640> could<00:17:20.760> also<00:17:21.000> be<00:17:21.120> that<00:17:21.299> you<00:17:21.419> have 00:17:21.530 --> 00:17:21.540 align:start position:0% because it could also be that you have 00:17:21.540 --> 00:17:23.030 align:start position:0% because it could also be that you have done<00:17:21.720> like<00:17:21.900> something<00:17:22.079> else<00:17:22.380> like<00:17:22.740> something 00:17:23.030 --> 00:17:23.040 align:start position:0% done like something else like something 00:17:23.040 --> 00:17:24.770 align:start position:0% done like something else like something something<00:17:23.339> else<00:17:23.760> wrong<00:17:24.059> you<00:17:24.360> know<00:17:24.419> and<00:17:24.600> so 00:17:24.770 --> 00:17:24.780 align:start position:0% something else wrong you know and so 00:17:24.780 --> 00:17:27.169 align:start position:0% something else wrong you know and so therefore<00:17:25.140> the<00:17:25.380> error<00:17:25.860> might<00:17:26.100> be<00:17:26.760> referring 00:17:27.169 --> 00:17:27.179 align:start position:0% therefore the error might be referring 00:17:27.179 --> 00:17:28.970 align:start position:0% therefore the error might be referring to<00:17:27.240> something<00:17:27.480> else<00:17:27.720> so<00:17:27.900> I<00:17:28.140> I<00:17:28.620> personally 00:17:28.970 --> 00:17:28.980 align:start position:0% to something else so I I personally 00:17:28.980 --> 00:17:31.130 align:start position:0% to something else so I I personally think<00:17:29.280> that's<00:17:29.460> useful<00:17:29.880> and<00:17:30.360> that's<00:17:30.540> final<00:17:30.780> now 00:17:31.130 --> 00:17:31.140 align:start position:0% think that's useful and that's final now 00:17:31.140 --> 00:17:34.250 align:start position:0% think that's useful and that's final now also<00:17:31.559> and<00:17:32.340> it's<00:17:32.520> building<00:17:32.760> on<00:17:33.120> uh 00:17:34.250 --> 00:17:34.260 align:start position:0% also and it's building on uh 00:17:34.260 --> 00:17:38.570 align:start position:0% also and it's building on uh uh<00:17:35.100> 721<00:17:35.880> yeah<00:17:36.480> I<00:17:36.720> mean<00:17:37.080> now<00:17:37.260> I'm<00:17:37.500> at<00:17:37.740> uh<00:17:38.280> 17 00:17:38.570 --> 00:17:38.580 align:start position:0% uh 721 yeah I mean now I'm at uh 17 00:17:38.580 --> 00:17:41.090 align:start position:0% uh 721 yeah I mean now I'm at uh 17 minutes<00:17:39.000> the<00:17:39.539> next<00:17:39.720> we're<00:17:40.200> gonna<00:17:40.740> have<00:17:40.919> the 00:17:41.090 --> 00:17:41.100 align:start position:0% minutes the next we're gonna have the 00:17:41.100 --> 00:17:42.650 align:start position:0% minutes the next we're gonna have the next<00:17:41.220> speaker 00:17:42.650 --> 00:17:42.660 align:start position:0% next speaker 00:17:42.660 --> 00:17:44.450 align:start position:0% next speaker um thank<00:17:43.080> you<00:17:43.260> for<00:17:43.500> also<00:17:43.860> giving<00:17:43.980> me<00:17:44.280> the 00:17:44.450 --> 00:17:44.460 align:start position:0% um thank you for also giving me the 00:17:44.460 --> 00:17:47.870 align:start position:0% um thank you for also giving me the chance<00:17:44.700> to<00:17:45.000> give<00:17:45.419> this<00:17:45.600> little<00:17:45.780> talk<00:17:46.020> and<00:17:47.520> um<00:17:47.520> I 00:17:47.870 --> 00:17:47.880 align:start position:0% chance to give this little talk and um I 00:17:47.880 --> 00:17:52.630 align:start position:0% chance to give this little talk and um I want<00:17:48.000> to<00:17:48.240> ask<00:17:48.900> to<00:17:49.200> Stage<00:17:49.620> Ronan 00:17:52.630 --> 00:17:52.640 align:start position:0% 00:17:52.640 --> 00:17:55.130 align:start position:0% I<00:17:53.640> don't<00:17:53.700> know<00:17:53.880> the<00:17:54.120> exact<00:17:54.419> finances<00:17:54.840> thank 00:17:55.130 --> 00:17:55.140 align:start position:0% I don't know the exact finances thank 00:17:55.140 --> 00:17:58.850 align:start position:0% I don't know the exact finances thank you 00:17:58.850 --> 00:17:58.860 align:start position:0% 00:17:58.860 --> 00:18:01.130 align:start position:0% okay<00:17:59.160> thank<00:17:59.580> you<00:17:59.700> for<00:17:59.940> coming<00:18:00.120> here 00:18:01.130 --> 00:18:01.140 align:start position:0% okay thank you for coming here 00:18:01.140 --> 00:18:06.549 align:start position:0% okay thank you for coming here um 00:18:06.549 --> 00:18:06.559 align:start position:0% 00:18:06.559 --> 00:18:09.409 align:start position:0% and<00:18:07.559> kind<00:18:07.799> of<00:18:07.919> to<00:18:08.100> explain<00:18:08.400> it<00:18:08.760> I'm<00:18:09.059> not<00:18:09.299> too 00:18:09.409 --> 00:18:09.419 align:start position:0% and kind of to explain it I'm not too 00:18:09.419 --> 00:18:11.390 align:start position:0% and kind of to explain it I'm not too sure<00:18:09.600> demo<00:18:10.080> and<00:18:10.500> I<00:18:10.620> wanted<00:18:10.740> to<00:18:10.980> show<00:18:11.100> it<00:18:11.280> in 00:18:11.390 --> 00:18:11.400 align:start position:0% sure demo and I wanted to show it in 00:18:11.400 --> 00:18:14.570 align:start position:0% sure demo and I wanted to show it in real<00:18:11.580> time<00:18:11.880> but<00:18:12.299> the<00:18:12.960> Wi-Fi<00:18:13.320> made<00:18:13.799> me<00:18:13.980> so<00:18:14.160> made 00:18:14.570 --> 00:18:14.580 align:start position:0% real time but the Wi-Fi made me so made 00:18:14.580 --> 00:18:17.150 align:start position:0% real time but the Wi-Fi made me so made me<00:18:14.700> realize<00:18:15.059> that<00:18:15.240> I<00:18:15.720> should<00:18:15.900> probably<00:18:16.160> uh 00:18:17.150 --> 00:18:17.160 align:start position:0% me realize that I should probably uh 00:18:17.160 --> 00:18:19.310 align:start position:0% me realize that I should probably uh have<00:18:17.400> it<00:18:17.580> already<00:18:17.760> done<00:18:18.179> and<00:18:18.840> show<00:18:19.020> you<00:18:19.140> the 00:18:19.310 --> 00:18:19.320 align:start position:0% have it already done and show you the 00:18:19.320 --> 00:18:20.990 align:start position:0% have it already done and show you the result 00:18:20.990 --> 00:18:21.000 align:start position:0% result 00:18:21.000 --> 00:18:23.090 align:start position:0% result um so<00:18:21.480> basically<00:18:21.720> the<00:18:21.960> proposal<00:18:22.440> is<00:18:22.980> to 00:18:23.090 --> 00:18:23.100 align:start position:0% um so basically the proposal is to 00:18:23.100 --> 00:18:24.770 align:start position:0% um so basically the proposal is to improve<00:18:23.400> so<00:18:23.520> what<00:18:23.700> I'm<00:18:23.880> building<00:18:24.059> I'm 00:18:24.770 --> 00:18:24.780 align:start position:0% improve so what I'm building I'm 00:18:24.780 --> 00:18:25.909 align:start position:0% improve so what I'm building I'm building<00:18:25.080> a 00:18:25.909 --> 00:18:25.919 align:start position:0% building a 00:18:25.919 --> 00:18:28.970 align:start position:0% building a indexer<00:18:26.820> so<00:18:27.059> that<00:18:27.419> kind<00:18:27.600> of<00:18:28.200> take<00:18:28.559> all<00:18:28.799> the 00:18:28.970 --> 00:18:28.980 align:start position:0% indexer so that kind of take all the 00:18:28.980 --> 00:18:31.549 align:start position:0% indexer so that kind of take all the event<00:18:29.220> of<00:18:30.000> a<00:18:30.240> contract<00:18:30.600> and<00:18:30.900> contract<00:18:31.320> the 00:18:31.549 --> 00:18:31.559 align:start position:0% event of a contract and contract the 00:18:31.559 --> 00:18:34.070 align:start position:0% event of a contract and contract the state<00:18:31.799> which<00:18:32.280> is<00:18:32.400> our<00:18:33.059> most 00:18:34.070 --> 00:18:34.080 align:start position:0% state which is our most 00:18:34.080 --> 00:18:35.930 align:start position:0% state which is our most a<00:18:34.440> smart<00:18:34.620> contract<00:18:34.919> system 00:18:35.930 --> 00:18:35.940 align:start position:0% a smart contract system 00:18:35.940 --> 00:18:39.289 align:start position:0% a smart contract system under<00:18:36.480> State<00:18:37.200> for<00:18:37.919> the<00:18:38.100> client<00:18:38.280> for<00:18:38.760> yeah<00:18:39.059> for 00:18:39.289 --> 00:18:39.299 align:start position:0% under State for the client for yeah for 00:18:39.299 --> 00:18:42.650 align:start position:0% under State for the client for yeah for basically<00:18:39.539> having<00:18:39.799> data<00:18:40.799> about<00:18:40.919> it<00:18:41.280> and<00:18:42.120> most 00:18:42.650 --> 00:18:42.660 align:start position:0% basically having data about it and most 00:18:42.660 --> 00:18:43.909 align:start position:0% basically having data about it and most projects 00:18:43.909 --> 00:18:43.919 align:start position:0% projects 00:18:43.919 --> 00:18:47.330 align:start position:0% projects use<00:18:44.340> a<00:18:44.760> backend<00:18:45.059> which<00:18:45.720> is<00:18:45.900> at<00:18:46.320> odd<00:18:46.620> with<00:18:46.919> the 00:18:47.330 --> 00:18:47.340 align:start position:0% use a backend which is at odd with the 00:18:47.340 --> 00:18:50.450 align:start position:0% use a backend which is at odd with the vision<00:18:47.580> of<00:18:47.880> of<00:18:48.120> decentralized<00:18:48.840> application 00:18:50.450 --> 00:18:50.460 align:start position:0% vision of of decentralized application 00:18:50.460 --> 00:18:53.450 align:start position:0% vision of of decentralized application so<00:18:51.000> yeah<00:18:51.179> my<00:18:51.480> idea<00:18:51.780> was<00:18:51.960> simply<00:18:52.260> let's<00:18:52.980> index 00:18:53.450 --> 00:18:53.460 align:start position:0% so yeah my idea was simply let's index 00:18:53.460 --> 00:18:56.870 align:start position:0% so yeah my idea was simply let's index in<00:18:53.640> the<00:18:53.880> browser<00:18:54.720> and<00:18:55.320> of<00:18:55.440> course<00:18:55.620> uh<00:18:56.400> it 00:18:56.870 --> 00:18:56.880 align:start position:0% in the browser and of course uh it 00:18:56.880 --> 00:18:58.970 align:start position:0% in the browser and of course uh it doesn't<00:18:57.000> work<00:18:57.240> for<00:18:57.480> everything 00:18:58.970 --> 00:18:58.980 align:start position:0% doesn't work for everything 00:18:58.980 --> 00:19:01.490 align:start position:0% doesn't work for everything um<00:18:59.039> because<00:18:59.580> of<00:19:00.000> the<00:19:00.179> scale<00:19:00.539> of<00:19:00.840> some<00:19:01.020> of<00:19:01.140> these 00:19:01.490 --> 00:19:01.500 align:start position:0% um because of the scale of some of these 00:19:01.500 --> 00:19:03.289 align:start position:0% um because of the scale of some of these of<00:19:02.039> these<00:19:02.280> systems<00:19:02.580> so<00:19:02.700> for<00:19:02.880> example<00:19:03.120> if<00:19:03.179> you 00:19:03.289 --> 00:19:03.299 align:start position:0% of these systems so for example if you 00:19:03.299 --> 00:19:05.270 align:start position:0% of these systems so for example if you wanted<00:19:03.419> to<00:19:03.660> index<00:19:03.900> all<00:19:04.200> the<00:19:04.320> nft 00:19:05.270 --> 00:19:05.280 align:start position:0% wanted to index all the nft 00:19:05.280 --> 00:19:07.010 align:start position:0% wanted to index all the nft uh<00:19:05.880> you<00:19:06.059> could<00:19:06.120> do<00:19:06.240> in<00:19:06.360> the<00:19:06.480> browser<00:19:06.780> but<00:19:06.900> it 00:19:07.010 --> 00:19:07.020 align:start position:0% uh you could do in the browser but it 00:19:07.020 --> 00:19:08.570 align:start position:0% uh you could do in the browser but it will<00:19:07.140> take<00:19:07.260> a<00:19:07.380> while 00:19:08.570 --> 00:19:08.580 align:start position:0% will take a while 00:19:08.580 --> 00:19:10.310 align:start position:0% will take a while um<00:19:08.700> but<00:19:08.940> for<00:19:09.120> some<00:19:09.299> other<00:19:09.480> case<00:19:09.780> it<00:19:10.140> actually 00:19:10.310 --> 00:19:10.320 align:start position:0% um but for some other case it actually 00:19:10.320 --> 00:19:12.169 align:start position:0% um but for some other case it actually worked<00:19:10.740> very<00:19:10.799> well 00:19:12.169 --> 00:19:12.179 align:start position:0% worked very well 00:19:12.179 --> 00:19:14.150 align:start position:0% worked very well um<00:19:12.299> and<00:19:12.960> so<00:19:13.080> I<00:19:13.200> was<00:19:13.320> doing<00:19:13.500> so<00:19:13.799> I<00:19:13.919> have<00:19:14.039> this 00:19:14.150 --> 00:19:14.160 align:start position:0% um and so I was doing so I have this 00:19:14.160 --> 00:19:16.130 align:start position:0% um and so I was doing so I have this game<00:19:14.400> so<00:19:14.760> the<00:19:15.000> whole<00:19:15.179> state<00:19:15.419> of<00:19:15.600> the<00:19:15.720> game<00:19:15.840> is 00:19:16.130 --> 00:19:16.140 align:start position:0% game so the whole state of the game is 00:19:16.140 --> 00:19:17.330 align:start position:0% game so the whole state of the game is actually<00:19:16.320> here 00:19:17.330 --> 00:19:17.340 align:start position:0% actually here 00:19:17.340 --> 00:19:19.870 align:start position:0% actually here so<00:19:18.059> you<00:19:18.179> have<00:19:18.299> all<00:19:18.419> the<00:19:18.600> fleet 00:19:19.870 --> 00:19:19.880 align:start position:0% so you have all the fleet 00:19:19.880 --> 00:19:23.330 align:start position:0% so you have all the fleet is<00:19:20.880> gaming<00:19:21.780> space<00:19:22.020> you<00:19:22.500> have<00:19:22.620> planet<00:19:22.860> and 00:19:23.330 --> 00:19:23.340 align:start position:0% is gaming space you have planet and 00:19:23.340 --> 00:19:26.630 align:start position:0% is gaming space you have planet and Fleet<00:19:24.080> uh<00:19:25.080> you<00:19:25.260> can<00:19:25.380> there's<00:19:25.740> two<00:19:26.039> main<00:19:26.280> things 00:19:26.630 --> 00:19:26.640 align:start position:0% Fleet uh you can there's two main things 00:19:26.640 --> 00:19:28.430 align:start position:0% Fleet uh you can there's two main things and 00:19:28.430 --> 00:19:28.440 align:start position:0% and 00:19:28.440 --> 00:19:31.010 align:start position:0% and it's<00:19:29.039> like<00:19:29.280> I<00:19:29.520> think<00:19:29.700> this<00:19:29.880> state<00:19:30.120> is<00:19:30.360> around 00:19:31.010 --> 00:19:31.020 align:start position:0% it's like I think this state is around 00:19:31.020 --> 00:19:32.930 align:start position:0% it's like I think this state is around seven<00:19:31.500> megabyte<00:19:32.100> but<00:19:32.280> it's<00:19:32.460> not<00:19:32.580> actually<00:19:32.760> I 00:19:32.930 --> 00:19:32.940 align:start position:0% seven megabyte but it's not actually I 00:19:32.940 --> 00:19:35.210 align:start position:0% seven megabyte but it's not actually I didn't<00:19:33.059> implement<00:19:33.419> the<00:19:33.600> full<00:19:33.840> uh<00:19:34.620> so<00:19:34.980> I<00:19:35.100> have 00:19:35.210 --> 00:19:35.220 align:start position:0% didn't implement the full uh so I have 00:19:35.220 --> 00:19:37.370 align:start position:0% didn't implement the full uh so I have an<00:19:35.340> index<00:19:35.640> I<00:19:35.940> have<00:19:36.120> the<00:19:36.299> same<00:19:36.480> indexer<00:19:37.200> running 00:19:37.370 --> 00:19:37.380 align:start position:0% an index I have the same indexer running 00:19:37.380 --> 00:19:39.230 align:start position:0% an index I have the same indexer running on<00:19:37.679> the<00:19:37.799> graph 00:19:39.230 --> 00:19:39.240 align:start position:0% on the graph 00:19:39.240 --> 00:19:40.070 align:start position:0% on the graph um 00:19:40.070 --> 00:19:40.080 align:start position:0% um 00:19:40.080 --> 00:19:41.870 align:start position:0% um and<00:19:40.500> I<00:19:40.679> didn't<00:19:40.799> finish<00:19:41.100> to<00:19:41.400> implement<00:19:41.640> it 00:19:41.870 --> 00:19:41.880 align:start position:0% and I didn't finish to implement it 00:19:41.880 --> 00:19:43.610 align:start position:0% and I didn't finish to implement it fully<00:19:42.240> here<00:19:42.419> that's<00:19:42.720> what<00:19:42.900> I<00:19:43.020> expect<00:19:43.140> maybe<00:19:43.380> to 00:19:43.610 --> 00:19:43.620 align:start position:0% fully here that's what I expect maybe to 00:19:43.620 --> 00:19:46.490 align:start position:0% fully here that's what I expect maybe to get<00:19:43.799> to<00:19:43.980> 20<00:19:44.220> megabytes<00:19:44.940> of<00:19:45.120> State 00:19:46.490 --> 00:19:46.500 align:start position:0% get to 20 megabytes of State 00:19:46.500 --> 00:19:49.130 align:start position:0% get to 20 megabytes of State um<00:19:46.620> and<00:19:46.860> I<00:19:47.039> can<00:19:47.220> on<00:19:47.760> the<00:19:47.940> normal<00:19:48.240> Network<00:19:48.600> I 00:19:49.130 --> 00:19:49.140 align:start position:0% um and I can on the normal Network I 00:19:49.140 --> 00:19:51.770 align:start position:0% um and I can on the normal Network I don't<00:19:49.320> know<00:19:49.440> what<00:19:49.620> normal<00:19:49.919> means<00:19:50.400> but<00:19:50.780> it 00:19:51.770 --> 00:19:51.780 align:start position:0% don't know what normal means but it 00:19:51.780 --> 00:19:54.110 align:start position:0% don't know what normal means but it cannot<00:19:52.080> it<00:19:52.200> took<00:19:52.440> five<00:19:52.620> seconds<00:19:52.919> to<00:19:53.460> think<00:19:53.640> the 00:19:54.110 --> 00:19:54.120 align:start position:0% cannot it took five seconds to think the 00:19:54.120 --> 00:19:57.169 align:start position:0% cannot it took five seconds to think the whole<00:19:54.240> thing<00:19:54.539> and<00:19:55.080> if<00:19:55.200> you<00:19:55.440> can<00:19:55.559> obviously<00:19:56.400> um 00:19:57.169 --> 00:19:57.179 align:start position:0% whole thing and if you can obviously um 00:19:57.179 --> 00:20:01.430 align:start position:0% whole thing and if you can obviously um uh<00:19:57.960> but<00:19:58.260> I<00:19:58.500> made<00:19:58.620> an<00:19:58.799> assumption<00:19:59.280> that<00:20:00.200> uh<00:20:01.200> in 00:20:01.430 --> 00:20:01.440 align:start position:0% uh but I made an assumption that uh in 00:20:01.440 --> 00:20:03.470 align:start position:0% uh but I made an assumption that uh in my<00:20:01.559> in<00:20:01.799> my<00:20:02.039> game<00:20:02.160> there<00:20:02.760> is<00:20:02.880> this<00:20:03.000> notion<00:20:03.299> of 00:20:03.470 --> 00:20:03.480 align:start position:0% my in my game there is this notion of 00:20:03.480 --> 00:20:05.930 align:start position:0% my in my game there is this notion of time<00:20:03.660> so<00:20:03.960> every<00:20:04.200> event 00:20:05.930 --> 00:20:05.940 align:start position:0% time so every event 00:20:05.940 --> 00:20:06.529 align:start position:0% time so every event um 00:20:06.529 --> 00:20:06.539 align:start position:0% um 00:20:06.539 --> 00:20:09.350 align:start position:0% um so<00:20:07.020> the<00:20:07.320> state<00:20:07.620> the<00:20:08.039> the<00:20:08.220> contract<00:20:08.640> will<00:20:08.880> kind 00:20:09.350 --> 00:20:09.360 align:start position:0% so the state the the contract will kind 00:20:09.360 --> 00:20:11.510 align:start position:0% so the state the the contract will kind of<00:20:09.539> lazily<00:20:10.020> update<00:20:10.380> per<00:20:10.799> time<00:20:11.039> and<00:20:11.220> I<00:20:11.400> think 00:20:11.510 --> 00:20:11.520 align:start position:0% of lazily update per time and I think 00:20:11.520 --> 00:20:13.310 align:start position:0% of lazily update per time and I think it's<00:20:11.640> quite<00:20:11.940> a<00:20:12.179> common<00:20:12.360> thing<00:20:12.660> in<00:20:12.840> it's<00:20:13.140> my 00:20:13.310 --> 00:20:13.320 align:start position:0% it's quite a common thing in it's my 00:20:13.320 --> 00:20:16.310 align:start position:0% it's quite a common thing in it's my contract<00:20:13.700> and<00:20:14.700> unfortunately 00:20:16.310 --> 00:20:16.320 align:start position:0% contract and unfortunately 00:20:16.320 --> 00:20:18.110 align:start position:0% contract and unfortunately when<00:20:16.740> you<00:20:16.860> fetch<00:20:17.220> the<00:20:17.340> logs<00:20:17.640> which<00:20:17.880> is<00:20:18.000> a 00:20:18.110 --> 00:20:18.120 align:start position:0% when you fetch the logs which is a 00:20:18.120 --> 00:20:20.390 align:start position:0% when you fetch the logs which is a mechanism<00:20:18.480> by<00:20:18.720> which<00:20:18.900> you<00:20:19.080> index<00:20:19.440> and<00:20:19.919> manage 00:20:20.390 --> 00:20:20.400 align:start position:0% mechanism by which you index and manage 00:20:20.400 --> 00:20:22.490 align:start position:0% mechanism by which you index and manage to<00:20:20.520> get<00:20:20.700> back<00:20:20.880> the<00:20:21.059> state<00:20:21.299> all<00:20:21.900> this<00:20:22.200> event 00:20:22.490 --> 00:20:22.500 align:start position:0% to get back the state all this event 00:20:22.500 --> 00:20:24.110 align:start position:0% to get back the state all this event basically<00:20:23.039> which 00:20:24.110 --> 00:20:24.120 align:start position:0% basically which 00:20:24.120 --> 00:20:26.150 align:start position:0% basically which um you<00:20:24.960> don't<00:20:25.140> have<00:20:25.440> access<00:20:25.620> to<00:20:26.039> the 00:20:26.150 --> 00:20:26.160 align:start position:0% um you don't have access to the 00:20:26.160 --> 00:20:27.890 align:start position:0% um you don't have access to the timestamp<00:20:26.580> at<00:20:26.820> which<00:20:27.000> they<00:20:27.120> open 00:20:27.890 --> 00:20:27.900 align:start position:0% timestamp at which they open 00:20:27.900 --> 00:20:31.070 align:start position:0% timestamp at which they open it's<00:20:28.440> just<00:20:28.740> some<00:20:29.460> reason<00:20:29.640> uh<00:20:30.480> they<00:20:30.660> didn't<00:20:30.840> so 00:20:31.070 --> 00:20:31.080 align:start position:0% it's just some reason uh they didn't so 00:20:31.080 --> 00:20:32.930 align:start position:0% it's just some reason uh they didn't so to<00:20:31.260> add<00:20:31.440> that<00:20:31.620> so<00:20:31.799> there<00:20:31.980> is<00:20:32.160> a<00:20:32.280> blockage<00:20:32.700> the 00:20:32.930 --> 00:20:32.940 align:start position:0% to add that so there is a blockage the 00:20:32.940 --> 00:20:34.789 align:start position:0% to add that so there is a blockage the block<00:20:33.179> number<00:20:33.419> but<00:20:34.200> there<00:20:34.380> is<00:20:34.500> no<00:20:34.620> block 00:20:34.789 --> 00:20:34.799 align:start position:0% block number but there is no block 00:20:34.799 --> 00:20:38.230 align:start position:0% block number but there is no block timestamp<00:20:35.280> and<00:20:36.059> so<00:20:36.179> my<00:20:36.600> game<00:20:36.840> actually<00:20:37.020> when<00:20:37.440> I 00:20:38.230 --> 00:20:38.240 align:start position:0% timestamp and so my game actually when I 00:20:38.240 --> 00:20:42.169 align:start position:0% timestamp and so my game actually when I uh<00:20:39.240> I<00:20:39.480> need<00:20:39.600> the<00:20:39.780> timestamp<00:20:40.200> and 00:20:42.169 --> 00:20:42.179 align:start position:0% uh I need the timestamp and 00:20:42.179 --> 00:20:44.570 align:start position:0% uh I need the timestamp and so<00:20:42.840> because<00:20:43.260> I<00:20:43.500> don't<00:20:43.679> have<00:20:43.860> the<00:20:44.039> timestamp<00:20:44.400> in 00:20:44.570 --> 00:20:44.580 align:start position:0% so because I don't have the timestamp in 00:20:44.580 --> 00:20:47.150 align:start position:0% so because I don't have the timestamp in the<00:20:44.700> logs<00:20:45.059> I<00:20:45.600> get<00:20:45.720> like<00:20:45.900> 20<00:20:46.440> 000<00:20:46.559> events<00:20:46.980> here 00:20:47.150 --> 00:20:47.160 align:start position:0% the logs I get like 20 000 events here 00:20:47.160 --> 00:20:49.909 align:start position:0% the logs I get like 20 000 events here and<00:20:47.880> what<00:20:48.600> I<00:20:48.780> need<00:20:48.900> to<00:20:49.020> do<00:20:49.140> then<00:20:49.440> I<00:20:49.679> need<00:20:49.799> to 00:20:49.909 --> 00:20:49.919 align:start position:0% and what I need to do then I need to 00:20:49.919 --> 00:20:53.150 align:start position:0% and what I need to do then I need to request<00:20:50.340> 20<00:20:51.000> 000<00:20:51.120> times 00:20:53.150 --> 00:20:53.160 align:start position:0% request 20 000 times 00:20:53.160 --> 00:20:54.950 align:start position:0% request 20 000 times um<00:20:53.280> depending<00:20:53.880> I<00:20:54.120> mean<00:20:54.240> a<00:20:54.360> bit<00:20:54.539> less<00:20:54.660> because 00:20:54.950 --> 00:20:54.960 align:start position:0% um depending I mean a bit less because 00:20:54.960 --> 00:20:57.409 align:start position:0% um depending I mean a bit less because you<00:20:55.320> can<00:20:55.440> have<00:20:55.559> uh<00:20:56.280> same<00:20:56.460> even<00:20:56.700> an<00:20:57.000> event<00:20:57.179> in 00:20:57.409 --> 00:20:57.419 align:start position:0% you can have uh same even an event in 00:20:57.419 --> 00:20:59.150 align:start position:0% you can have uh same even an event in the<00:20:57.539> same<00:20:57.660> block<00:20:57.840> but<00:20:58.380> you<00:20:58.500> I<00:20:58.620> have<00:20:58.799> to<00:20:58.860> request 00:20:59.150 --> 00:20:59.160 align:start position:0% the same block but you I have to request 00:20:59.160 --> 00:21:01.669 align:start position:0% the same block but you I have to request that<00:20:59.340> on<00:20:59.460> top<00:21:00.120> and<00:21:00.720> because<00:21:01.020> it's<00:21:01.320> a<00:21:01.500> in 00:21:01.669 --> 00:21:01.679 align:start position:0% that on top and because it's a in 00:21:01.679 --> 00:21:04.390 align:start position:0% that on top and because it's a in browser<00:21:02.039> indexer<00:21:02.580> it<00:21:03.179> uses 00:21:04.390 --> 00:21:04.400 align:start position:0% browser indexer it uses 00:21:04.400 --> 00:21:06.710 align:start position:0% browser indexer it uses eip119393<00:21:05.400> which<00:21:05.640> is<00:21:05.820> like<00:21:06.000> the<00:21:06.179> the<00:21:06.360> wallet 00:21:06.710 --> 00:21:06.720 align:start position:0% eip119393 which is like the the wallet 00:21:06.720 --> 00:21:09.770 align:start position:0% eip119393 which is like the the wallet interface<00:21:07.679> and<00:21:08.580> I<00:21:08.820> cannot<00:21:09.059> do<00:21:09.179> batch<00:21:09.360> request 00:21:09.770 --> 00:21:09.780 align:start position:0% interface and I cannot do batch request 00:21:09.780 --> 00:21:12.409 align:start position:0% interface and I cannot do batch request I<00:21:10.320> have<00:21:10.440> to<00:21:10.620> do<00:21:10.919> all<00:21:11.460> these<00:21:11.760> requests<00:21:12.059> and<00:21:12.240> so 00:21:12.409 --> 00:21:12.419 align:start position:0% I have to do all these requests and so 00:21:12.419 --> 00:21:14.750 align:start position:0% I have to do all these requests and so uh<00:21:13.140> I<00:21:13.380> have<00:21:13.500> this<00:21:13.740> version<00:21:13.980> we<00:21:14.340> actually<00:21:14.520> is 00:21:14.750 --> 00:21:14.760 align:start position:0% uh I have this version we actually is 00:21:14.760 --> 00:21:16.730 align:start position:0% uh I have this version we actually is still<00:21:15.000> running<00:21:15.179> from<00:21:15.840> last<00:21:16.020> time<00:21:16.260> and 00:21:16.730 --> 00:21:16.740 align:start position:0% still running from last time and 00:21:16.740 --> 00:21:19.430 align:start position:0% still running from last time and sometime<00:21:17.039> here<00:21:17.220> or<00:21:17.520> out<00:21:17.580> because<00:21:18.240> the<00:21:18.960> RPC<00:21:19.320> is 00:21:19.430 --> 00:21:19.440 align:start position:0% sometime here or out because the RPC is 00:21:19.440 --> 00:21:21.590 align:start position:0% sometime here or out because the RPC is not<00:21:19.559> happy<00:21:19.799> that<00:21:20.039> I'm<00:21:20.400> so<00:21:20.880> the<00:21:21.059> RPC<00:21:21.419> of 00:21:21.590 --> 00:21:21.600 align:start position:0% not happy that I'm so the RPC of 00:21:21.600 --> 00:21:23.930 align:start position:0% not happy that I'm so the RPC of metamask<00:21:22.020> because<00:21:22.200> again<00:21:22.440> here<00:21:22.679> it's<00:21:23.460> a<00:21:23.640> juicy 00:21:23.930 --> 00:21:23.940 align:start position:0% metamask because again here it's a juicy 00:21:23.940 --> 00:21:26.630 align:start position:0% metamask because again here it's a juicy static<00:21:24.299> web<00:21:24.480> page<00:21:24.780> there<00:21:25.559> is<00:21:25.740> nothing<00:21:25.919> no 00:21:26.630 --> 00:21:26.640 align:start position:0% static web page there is nothing no 00:21:26.640 --> 00:21:28.010 align:start position:0% static web page there is nothing no back-end 00:21:28.010 --> 00:21:28.020 align:start position:0% back-end 00:21:28.020 --> 00:21:30.289 align:start position:0% back-end um and<00:21:28.679> it<00:21:28.860> all<00:21:29.039> only<00:21:29.280> rely<00:21:29.700> on<00:21:29.820> the<00:21:30.000> fact<00:21:30.120> that 00:21:30.289 --> 00:21:30.299 align:start position:0% um and it all only rely on the fact that 00:21:30.299 --> 00:21:31.930 align:start position:0% um and it all only rely on the fact that the<00:21:30.480> user<00:21:30.840> have<00:21:30.960> a 00:21:31.930 --> 00:21:31.940 align:start position:0% the user have a 00:21:31.940 --> 00:21:34.610 align:start position:0% the user have a eip1193<00:21:32.940> wallet<00:21:33.419> in<00:21:34.200> that<00:21:34.320> case<00:21:34.440> it's 00:21:34.610 --> 00:21:34.620 align:start position:0% eip1193 wallet in that case it's 00:21:34.620 --> 00:21:36.830 align:start position:0% eip1193 wallet in that case it's metamask<00:21:35.100> and<00:21:35.460> if<00:21:35.640> you<00:21:35.820> if<00:21:36.240> you<00:21:36.360> look<00:21:36.480> at<00:21:36.600> my 00:21:36.830 --> 00:21:36.840 align:start position:0% metamask and if you if you look at my 00:21:36.840 --> 00:21:39.529 align:start position:0% metamask and if you if you look at my settings<00:21:37.020> It's<00:21:37.679> actually<00:21:37.860> an<00:21:38.100> RPC<00:21:38.640> uh 00:21:39.529 --> 00:21:39.539 align:start position:0% settings It's actually an RPC uh 00:21:39.539 --> 00:21:40.850 align:start position:0% settings It's actually an RPC uh somewhere<00:21:39.900> else<00:21:40.020> but 00:21:40.850 --> 00:21:40.860 align:start position:0% somewhere else but 00:21:40.860 --> 00:21:44.510 align:start position:0% somewhere else but uh<00:21:41.820> so<00:21:42.480> it's<00:21:42.659> still<00:21:43.380> querying<00:21:43.980> all<00:21:44.159> of<00:21:44.340> these 00:21:44.510 --> 00:21:44.520 align:start position:0% uh so it's still querying all of these 00:21:44.520 --> 00:21:46.490 align:start position:0% uh so it's still querying all of these to<00:21:44.640> get<00:21:44.760> the<00:21:44.880> timestamp<00:21:45.360> while<00:21:46.020> the<00:21:46.200> other<00:21:46.320> one 00:21:46.490 --> 00:21:46.500 align:start position:0% to get the timestamp while the other one 00:21:46.500 --> 00:21:48.770 align:start position:0% to get the timestamp while the other one have<00:21:46.620> been<00:21:46.860> finished<00:21:47.039> a<00:21:47.520> long<00:21:47.700> time<00:21:47.880> ago<00:21:48.120> and 00:21:48.770 --> 00:21:48.780 align:start position:0% have been finished a long time ago and 00:21:48.780 --> 00:21:51.590 align:start position:0% have been finished a long time ago and only<00:21:48.900> actually<00:21:49.200> you<00:21:49.620> see<00:21:49.799> 580<00:21:50.520> request<00:21:51.000> is 00:21:51.590 --> 00:21:51.600 align:start position:0% only actually you see 580 request is 00:21:51.600 --> 00:21:53.570 align:start position:0% only actually you see 580 request is actually<00:21:51.780> 300<00:21:52.260> because<00:21:52.620> the<00:21:53.039> other<00:21:53.159> one<00:21:53.400> now 00:21:53.570 --> 00:21:53.580 align:start position:0% actually 300 because the other one now 00:21:53.580 --> 00:21:55.970 align:start position:0% actually 300 because the other one now is<00:21:53.820> just<00:21:54.000> to<00:21:54.480> get<00:21:54.539> the<00:21:54.720> latest<00:21:54.840> block<00:21:55.440> and 00:21:55.970 --> 00:21:55.980 align:start position:0% is just to get the latest block and 00:21:55.980 --> 00:21:57.470 align:start position:0% is just to get the latest block and nothing<00:21:56.100> is<00:21:56.460> really<00:21:56.580> happening<00:21:57.000> in<00:21:57.120> that<00:21:57.299> game 00:21:57.470 --> 00:21:57.480 align:start position:0% nothing is really happening in that game 00:21:57.480 --> 00:21:58.909 align:start position:0% nothing is really happening in that game right<00:21:57.720> now 00:21:58.909 --> 00:21:58.919 align:start position:0% right now 00:21:58.919 --> 00:22:01.430 align:start position:0% right now um<00:21:59.340> while<00:21:59.880> this<00:22:00.120> one<00:22:00.360> is<00:22:00.539> still<00:22:00.720> like<00:22:00.900> fetching 00:22:01.430 --> 00:22:01.440 align:start position:0% um while this one is still like fetching 00:22:01.440 --> 00:22:03.230 align:start position:0% um while this one is still like fetching the<00:22:01.679> the<00:22:01.799> state<00:22:02.159> so<00:22:02.400> it's<00:22:02.700> going<00:22:02.880> to<00:22:02.940> reach 00:22:03.230 --> 00:22:03.240 align:start position:0% the the state so it's going to reach 00:22:03.240 --> 00:22:05.149 align:start position:0% the the state so it's going to reach probably<00:22:03.419> 20<00:22:04.020> 000<00:22:04.140> to<00:22:04.320> sync<00:22:04.679> or<00:22:04.799> maybe<00:22:04.980> even 00:22:05.149 --> 00:22:05.159 align:start position:0% probably 20 000 to sync or maybe even 00:22:05.159 --> 00:22:06.770 align:start position:0% probably 20 000 to sync or maybe even more 00:22:06.770 --> 00:22:06.780 align:start position:0% more 00:22:06.780 --> 00:22:07.789 align:start position:0% more um 00:22:07.789 --> 00:22:07.799 align:start position:0% um 00:22:07.799 --> 00:22:10.310 align:start position:0% um um<00:22:07.980> yeah<00:22:08.400> so<00:22:08.580> so<00:22:09.059> the<00:22:09.240> proposal 00:22:10.310 --> 00:22:10.320 align:start position:0% um yeah so so the proposal 00:22:10.320 --> 00:22:12.289 align:start position:0% um yeah so so the proposal I<00:22:10.860> wanted<00:22:10.980> to<00:22:11.159> show<00:22:11.280> you<00:22:11.460> a<00:22:11.580> kind<00:22:11.700> of<00:22:11.880> a<00:22:12.000> really 00:22:12.289 --> 00:22:12.299 align:start position:0% I wanted to show you a kind of a really 00:22:12.299 --> 00:22:15.409 align:start position:0% I wanted to show you a kind of a really example<00:22:12.900> but<00:22:13.200> the<00:22:13.440> proposal<00:22:13.919> is 00:22:15.409 --> 00:22:15.419 align:start position:0% example but the proposal is 00:22:15.419 --> 00:22:17.870 align:start position:0% example but the proposal is um<00:22:15.480> is<00:22:15.840> basically<00:22:16.140> to<00:22:16.980> add 00:22:17.870 --> 00:22:17.880 align:start position:0% um is basically to add 00:22:17.880 --> 00:22:20.870 align:start position:0% um is basically to add this<00:22:18.600> to<00:22:19.260> the<00:22:19.440> Json<00:22:19.980> object<00:22:20.340> so<00:22:20.520> it's<00:22:20.640> a<00:22:20.760> very 00:22:20.870 --> 00:22:20.880 align:start position:0% this to the Json object so it's a very 00:22:20.880 --> 00:22:24.710 align:start position:0% this to the Json object so it's a very simple<00:22:21.000> change<00:22:21.240> you<00:22:21.480> can<00:22:21.600> do<00:22:22.220> in<00:22:23.220> a<00:22:24.000> in<00:22:24.419> your 00:22:24.710 --> 00:22:24.720 align:start position:0% simple change you can do in a in your 00:22:24.720 --> 00:22:28.010 align:start position:0% simple change you can do in a in your node<00:22:25.200> so<00:22:25.919> in<00:22:26.179> goatorium<00:22:27.179> or<00:22:27.539> what<00:22:27.780> whatever 00:22:28.010 --> 00:22:28.020 align:start position:0% node so in goatorium or what whatever 00:22:28.020 --> 00:22:31.010 align:start position:0% node so in goatorium or what whatever and<00:22:28.679> so<00:22:28.799> actually<00:22:29.039> finally<00:22:29.700> enough<00:22:30.240> uh<00:22:30.659> like 00:22:31.010 --> 00:22:31.020 align:start position:0% and so actually finally enough uh like 00:22:31.020 --> 00:22:33.830 align:start position:0% and so actually finally enough uh like team<00:22:31.200> pushed<00:22:31.679> me<00:22:31.799> to<00:22:31.980> go<00:22:32.159> to<00:22:32.340> the<00:22:32.700> core<00:22:33.539> Dev 00:22:33.830 --> 00:22:33.840 align:start position:0% team pushed me to go to the core Dev 00:22:33.840 --> 00:22:37.130 align:start position:0% team pushed me to go to the core Dev meeting<00:22:34.559> the<00:22:34.980> other<00:22:35.159> day<00:22:35.539> and<00:22:36.539> actually<00:22:36.840> I'm 00:22:37.130 --> 00:22:37.140 align:start position:0% meeting the other day and actually I'm 00:22:37.140 --> 00:22:39.409 align:start position:0% meeting the other day and actually I'm going<00:22:37.380> to<00:22:37.620> and<00:22:38.460> so<00:22:38.640> we<00:22:38.760> are<00:22:38.880> the<00:22:39.059> interesting 00:22:39.409 --> 00:22:39.419 align:start position:0% going to and so we are the interesting 00:22:39.419 --> 00:22:41.390 align:start position:0% going to and so we are the interesting discussion<00:22:39.840> about<00:22:40.080> it<00:22:40.320> but 00:22:41.390 --> 00:22:41.400 align:start position:0% discussion about it but 00:22:41.400 --> 00:22:42.830 align:start position:0% discussion about it but um<00:22:41.520> so<00:22:41.880> I<00:22:42.059> kind<00:22:42.179> of 00:22:42.830 --> 00:22:42.840 align:start position:0% um so I kind of 00:22:42.840 --> 00:22:44.750 align:start position:0% um so I kind of so<00:22:43.320> most<00:22:43.500> of<00:22:43.620> it<00:22:43.740> I<00:22:43.919> already<00:22:44.039> say<00:22:44.340> but<00:22:44.460> the<00:22:44.580> idea 00:22:44.750 --> 00:22:44.760 align:start position:0% so most of it I already say but the idea 00:22:44.760 --> 00:22:47.330 align:start position:0% so most of it I already say but the idea is<00:22:44.940> that<00:22:45.440> you<00:22:46.440> must 00:22:47.330 --> 00:22:47.340 align:start position:0% is that you must 00:22:47.340 --> 00:22:49.250 align:start position:0% is that you must so<00:22:47.820> what<00:22:48.120> I<00:22:48.240> could<00:22:48.360> do<00:22:48.480> is<00:22:48.600> that<00:22:48.720> I<00:22:48.900> could<00:22:48.960> add 00:22:49.250 --> 00:22:49.260 align:start position:0% so what I could do is that I could add 00:22:49.260 --> 00:22:52.130 align:start position:0% so what I could do is that I could add the<00:22:49.380> timestamp<00:22:49.799> to<00:22:50.039> the<00:22:50.220> to<00:22:50.400> the<00:22:50.580> event<00:22:50.700> itself 00:22:52.130 --> 00:22:52.140 align:start position:0% the timestamp to the to the event itself 00:22:52.140 --> 00:22:55.130 align:start position:0% the timestamp to the to the event itself uh<00:22:53.100> but<00:22:53.700> obviously<00:22:54.240> when<00:22:54.539> you<00:22:54.720> do<00:22:54.960> your 00:22:55.130 --> 00:22:55.140 align:start position:0% uh but obviously when you do your 00:22:55.140 --> 00:22:57.169 align:start position:0% uh but obviously when you do your contract<00:22:55.440> you<00:22:55.620> know<00:22:55.799> that<00:22:56.039> there<00:22:56.580> is<00:22:56.760> a<00:22:57.059> block 00:22:57.169 --> 00:22:57.179 align:start position:0% contract you know that there is a block 00:22:57.179 --> 00:22:59.510 align:start position:0% contract you know that there is a block information<00:22:57.480> so<00:22:58.080> there<00:22:58.740> is<00:22:58.919> no<00:22:58.980> need<00:22:59.159> to<00:22:59.280> add 00:22:59.510 --> 00:22:59.520 align:start position:0% information so there is no need to add 00:22:59.520 --> 00:23:01.190 align:start position:0% information so there is no need to add the<00:22:59.760> timestamp<00:23:00.120> to<00:23:00.360> the<00:23:00.480> event<00:23:00.659> it's<00:23:00.900> just<00:23:01.080> a 00:23:01.190 --> 00:23:01.200 align:start position:0% the timestamp to the event it's just a 00:23:01.200 --> 00:23:02.930 align:start position:0% the timestamp to the event it's just a waste<00:23:01.440> of<00:23:01.500> gas 00:23:02.930 --> 00:23:02.940 align:start position:0% waste of gas 00:23:02.940 --> 00:23:04.610 align:start position:0% waste of gas um and<00:23:03.240> time<00:23:03.539> is<00:23:03.720> an<00:23:03.840> important<00:23:04.140> aspect<00:23:04.440> of 00:23:04.610 --> 00:23:04.620 align:start position:0% um and time is an important aspect of 00:23:04.620 --> 00:23:06.830 align:start position:0% um and time is an important aspect of many<00:23:04.799> smart<00:23:05.100> contracts<00:23:05.640> and<00:23:06.299> block<00:23:06.539> number 00:23:06.830 --> 00:23:06.840 align:start position:0% many smart contracts and block number 00:23:06.840 --> 00:23:09.289 align:start position:0% many smart contracts and block number cannot<00:23:07.260> be<00:23:07.380> a<00:23:07.500> replacement<00:23:07.679> for<00:23:08.220> them<00:23:08.460> and<00:23:08.940> the 00:23:09.289 --> 00:23:09.299 align:start position:0% cannot be a replacement for them and the 00:23:09.299 --> 00:23:11.630 align:start position:0% cannot be a replacement for them and the reason<00:23:09.419> why<00:23:09.780> is<00:23:10.140> because<00:23:10.320> uh<00:23:11.100> block<00:23:11.340> number 00:23:11.630 --> 00:23:11.640 align:start position:0% reason why is because uh block number 00:23:11.640 --> 00:23:13.850 align:start position:0% reason why is because uh block number timings<00:23:12.179> can<00:23:12.480> change<00:23:12.659> across<00:23:13.140> chains<00:23:13.559> but 00:23:13.850 --> 00:23:13.860 align:start position:0% timings can change across chains but 00:23:13.860 --> 00:23:16.190 align:start position:0% timings can change across chains but also<00:23:14.820> there<00:23:15.000> is<00:23:15.120> no<00:23:15.240> guarantee<00:23:15.600> that<00:23:15.780> a<00:23:15.960> single 00:23:16.190 --> 00:23:16.200 align:start position:0% also there is no guarantee that a single 00:23:16.200 --> 00:23:18.350 align:start position:0% also there is no guarantee that a single chain<00:23:16.380> will<00:23:16.679> not<00:23:16.860> keep<00:23:17.580> it<00:23:17.760> and<00:23:18.000> you<00:23:18.240> could 00:23:18.350 --> 00:23:18.360 align:start position:0% chain will not keep it and you could 00:23:18.360 --> 00:23:21.830 align:start position:0% chain will not keep it and you could probably<00:23:18.600> emulate<00:23:19.559> an<00:23:20.520> average<00:23:20.760> block<00:23:21.539> time 00:23:21.830 --> 00:23:21.840 align:start position:0% probably emulate an average block time 00:23:21.840 --> 00:23:23.930 align:start position:0% probably emulate an average block time using<00:23:22.620> smart<00:23:22.799> contract<00:23:23.159> itself<00:23:23.520> but<00:23:23.820> it's 00:23:23.930 --> 00:23:23.940 align:start position:0% using smart contract itself but it's 00:23:23.940 --> 00:23:25.250 align:start position:0% using smart contract itself but it's kind<00:23:24.360> of<00:23:24.480> a 00:23:25.250 --> 00:23:25.260 align:start position:0% kind of a 00:23:25.260 --> 00:23:27.529 align:start position:0% kind of a ugly<00:23:25.380> work<00:23:25.620> around 00:23:27.529 --> 00:23:27.539 align:start position:0% ugly work around 00:23:27.539 --> 00:23:29.690 align:start position:0% ugly work around um<00:23:27.600> and<00:23:27.960> black<00:23:28.200> block<00:23:28.440> times<00:23:28.679> them<00:23:28.919> already 00:23:29.690 --> 00:23:29.700 align:start position:0% um and black block times them already 00:23:29.700 --> 00:23:31.730 align:start position:0% um and black block times them already easily<00:23:30.299> available<00:23:30.419> like<00:23:30.900> the<00:23:31.140> block<00:23:31.260> hash<00:23:31.620> or 00:23:31.730 --> 00:23:31.740 align:start position:0% easily available like the block hash or 00:23:31.740 --> 00:23:32.990 align:start position:0% easily available like the block hash or the<00:23:31.919> block<00:23:32.039> number 00:23:32.990 --> 00:23:33.000 align:start position:0% the block number 00:23:33.000 --> 00:23:36.590 align:start position:0% the block number and<00:23:33.860> another<00:23:34.860> so<00:23:35.820> I've<00:23:36.059> been<00:23:36.179> discussing 00:23:36.590 --> 00:23:36.600 align:start position:0% and another so I've been discussing 00:23:36.600 --> 00:23:39.409 align:start position:0% and another so I've been discussing about<00:23:36.780> a<00:23:37.620> few<00:23:37.679> people<00:23:37.799> readers<00:23:38.280> and<00:23:39.059> yeah<00:23:39.240> but 00:23:39.409 --> 00:23:39.419 align:start position:0% about a few people readers and yeah but 00:23:39.419 --> 00:23:41.870 align:start position:0% about a few people readers and yeah but this<00:23:39.539> is<00:23:39.659> extra<00:23:39.900> data<00:23:40.380> you<00:23:40.620> have<00:23:40.740> to<00:23:40.860> put<00:23:41.100> in<00:23:41.700> in 00:23:41.870 --> 00:23:41.880 align:start position:0% this is extra data you have to put in in 00:23:41.880 --> 00:23:45.049 align:start position:0% this is extra data you have to put in in the<00:23:42.059> log<00:23:42.240> object<00:23:42.740> but<00:23:43.740> it's<00:23:44.039> small<00:23:44.460> and<00:23:44.940> the 00:23:45.049 --> 00:23:45.059 align:start position:0% the log object but it's small and the 00:23:45.059 --> 00:23:47.090 align:start position:0% the log object but it's small and the alternative<00:23:45.480> is<00:23:45.720> to<00:23:45.960> to<00:23:46.260> fetch<00:23:46.679> all<00:23:46.740> of<00:23:46.919> these 00:23:47.090 --> 00:23:47.100 align:start position:0% alternative is to to fetch all of these 00:23:47.100 --> 00:23:48.529 align:start position:0% alternative is to to fetch all of these anyway 00:23:48.529 --> 00:23:48.539 align:start position:0% anyway 00:23:48.539 --> 00:23:50.270 align:start position:0% anyway um<00:23:48.659> so<00:23:49.080> of<00:23:49.260> course<00:23:49.380> for<00:23:49.679> the<00:23:49.799> one<00:23:49.980> we<00:23:50.100> don't 00:23:50.270 --> 00:23:50.280 align:start position:0% um so of course for the one we don't 00:23:50.280 --> 00:23:52.490 align:start position:0% um so of course for the one we don't care<00:23:50.460> about<00:23:50.640> timestamp<00:23:51.539> then<00:23:51.780> they<00:23:52.080> they<00:23:52.320> have 00:23:52.490 --> 00:23:52.500 align:start position:0% care about timestamp then they they have 00:23:52.500 --> 00:23:55.130 align:start position:0% care about timestamp then they they have an<00:23:52.679> extra<00:23:53.000> a<00:23:54.000> small<00:23:54.120> but<00:23:54.360> I<00:23:54.539> feel<00:23:54.659> it's<00:23:54.840> small 00:23:55.130 --> 00:23:55.140 align:start position:0% an extra a small but I feel it's small 00:23:55.140 --> 00:23:57.370 align:start position:0% an extra a small but I feel it's small enough 00:23:57.370 --> 00:23:57.380 align:start position:0% 00:23:57.380 --> 00:24:00.289 align:start position:0% alternative<00:23:58.380> but<00:23:58.860> I<00:23:59.039> would<00:23:59.220> not<00:23:59.400> consider<00:24:00.000> as 00:24:00.289 --> 00:24:00.299 align:start position:0% alternative but I would not consider as 00:24:00.299 --> 00:24:02.149 align:start position:0% alternative but I would not consider as alternative<00:24:00.780> actually<00:24:01.020> I<00:24:01.380> could<00:24:01.500> use<00:24:01.860> them<00:24:01.980> as 00:24:02.149 --> 00:24:02.159 align:start position:0% alternative actually I could use them as 00:24:02.159 --> 00:24:03.289 align:start position:0% alternative actually I could use them as complementary 00:24:03.289 --> 00:24:03.299 align:start position:0% complementary 00:24:03.299 --> 00:24:05.330 align:start position:0% complementary uh<00:24:04.020> so<00:24:04.260> when<00:24:04.500> I<00:24:04.620> mentioned<00:24:04.919> them<00:24:04.980> I'm<00:24:05.220> not 00:24:05.330 --> 00:24:05.340 align:start position:0% uh so when I mentioned them I'm not 00:24:05.340 --> 00:24:06.830 align:start position:0% uh so when I mentioned them I'm not saying<00:24:05.520> I<00:24:05.700> don't<00:24:05.820> want<00:24:05.940> them<00:24:06.120> actually<00:24:06.419> I<00:24:06.659> want 00:24:06.830 --> 00:24:06.840 align:start position:0% saying I don't want them actually I want 00:24:06.840 --> 00:24:07.850 align:start position:0% saying I don't want them actually I want them 00:24:07.850 --> 00:24:07.860 align:start position:0% them 00:24:07.860 --> 00:24:13.070 align:start position:0% them um<00:24:07.980> but<00:24:08.520> I<00:24:08.700> feel<00:24:08.940> they<00:24:09.480> they<00:24:09.960> will<00:24:10.320> not<00:24:10.500> replace 00:24:13.070 --> 00:24:13.080 align:start position:0% 00:24:13.080 --> 00:24:14.090 align:start position:0% you 00:24:14.090 --> 00:24:14.100 align:start position:0% you 00:24:14.100 --> 00:24:16.190 align:start position:0% you um<00:24:14.159> so<00:24:14.640> yeah<00:24:14.760> basically<00:24:15.120> when<00:24:15.419> alternative<00:24:15.900> is 00:24:16.190 --> 00:24:16.200 align:start position:0% um so yeah basically when alternative is 00:24:16.200 --> 00:24:18.470 align:start position:0% um so yeah basically when alternative is to<00:24:16.380> add<00:24:16.620> batch 00:24:18.470 --> 00:24:18.480 align:start position:0% to add batch 00:24:18.480 --> 00:24:21.950 align:start position:0% to add batch um<00:24:18.600> a<00:24:18.840> batch<00:24:19.080> API<00:24:19.620> for<00:24:19.860> Erp<00:24:20.640> 1193<00:24:21.360> it<00:24:21.780> was 00:24:21.950 --> 00:24:21.960 align:start position:0% um a batch API for Erp 1193 it was 00:24:21.960 --> 00:24:23.450 align:start position:0% um a batch API for Erp 1193 it was actually<00:24:22.140> part<00:24:22.740> of<00:24:22.860> the<00:24:22.980> conversation 00:24:23.450 --> 00:24:23.460 align:start position:0% actually part of the conversation 00:24:23.460 --> 00:24:25.970 align:start position:0% actually part of the conversation initially<00:24:24.000> but<00:24:24.179> it<00:24:24.360> was<00:24:24.419> dropped<00:24:24.900> but<00:24:25.440> I<00:24:25.860> think 00:24:25.970 --> 00:24:25.980 align:start position:0% initially but it was dropped but I think 00:24:25.980 --> 00:24:28.850 align:start position:0% initially but it was dropped but I think it's<00:24:26.100> it's<00:24:26.400> a<00:24:26.640> valid<00:24:26.940> one<00:24:27.120> to<00:24:27.299> have<00:24:27.480> and<00:24:28.260> but<00:24:28.620> my 00:24:28.850 --> 00:24:28.860 align:start position:0% it's it's a valid one to have and but my 00:24:28.860 --> 00:24:30.350 align:start position:0% it's it's a valid one to have and but my opinion<00:24:29.159> it<00:24:29.460> doesn't 00:24:30.350 --> 00:24:30.360 align:start position:0% opinion it doesn't 00:24:30.360 --> 00:24:33.110 align:start position:0% opinion it doesn't offer<00:24:31.260> the<00:24:31.679> same<00:24:31.799> Advantage<00:24:32.400> as<00:24:32.580> having<00:24:32.820> the 00:24:33.110 --> 00:24:33.120 align:start position:0% offer the same Advantage as having the 00:24:33.120 --> 00:24:35.570 align:start position:0% offer the same Advantage as having the box<00:24:33.299> timestamp<00:24:33.780> in<00:24:34.020> the<00:24:34.140> log 00:24:35.570 --> 00:24:35.580 align:start position:0% box timestamp in the log 00:24:35.580 --> 00:24:38.510 align:start position:0% box timestamp in the log um and<00:24:36.299> another<00:24:36.539> EIP<00:24:37.320> that<00:24:37.679> I<00:24:37.860> didn't<00:24:38.039> see<00:24:38.340> it 00:24:38.510 --> 00:24:38.520 align:start position:0% um and another EIP that I didn't see it 00:24:38.520 --> 00:24:43.549 align:start position:0% um and another EIP that I didn't see it yet<00:24:38.880> is<00:24:39.840> to<00:24:40.020> have<00:24:40.200> a<00:24:40.380> great<00:24:40.500> graphql<00:24:41.159> API<00:24:42.140> uh<00:24:43.140> so 00:24:43.549 --> 00:24:43.559 align:start position:0% yet is to have a great graphql API uh so 00:24:43.559 --> 00:24:46.250 align:start position:0% yet is to have a great graphql API uh so basically<00:24:43.980> an<00:24:44.100> alternative<00:24:44.460> to<00:24:44.780> eip1193<00:24:45.780> and 00:24:46.250 --> 00:24:46.260 align:start position:0% basically an alternative to eip1193 and 00:24:46.260 --> 00:24:48.529 align:start position:0% basically an alternative to eip1193 and with<00:24:46.740> graphql<00:24:47.280> you<00:24:47.580> can<00:24:47.640> ask<00:24:47.940> what<00:24:48.240> you<00:24:48.360> want 00:24:48.529 --> 00:24:48.539 align:start position:0% with graphql you can ask what you want 00:24:48.539 --> 00:24:51.230 align:start position:0% with graphql you can ask what you want which<00:24:49.080> make<00:24:49.380> it<00:24:49.559> more<00:24:49.740> efficient<00:24:50.159> as<00:24:50.520> well<00:24:50.700> uh 00:24:51.230 --> 00:24:51.240 align:start position:0% which make it more efficient as well uh 00:24:51.240 --> 00:24:52.669 align:start position:0% which make it more efficient as well uh for<00:24:51.480> transferring<00:24:51.960> data<00:24:52.200> so<00:24:52.320> if<00:24:52.440> you<00:24:52.559> don't 00:24:52.669 --> 00:24:52.679 align:start position:0% for transferring data so if you don't 00:24:52.679 --> 00:24:53.990 align:start position:0% for transferring data so if you don't care<00:24:52.799> about<00:24:52.919> the<00:24:53.159> timestamp<00:24:53.460> you<00:24:53.700> don't<00:24:53.820> need 00:24:53.990 --> 00:24:54.000 align:start position:0% care about the timestamp you don't need 00:24:54.000 --> 00:24:56.510 align:start position:0% care about the timestamp you don't need and<00:24:54.840> actually<00:24:54.960> this<00:24:55.320> one<00:24:55.500> could<00:24:55.740> really 00:24:56.510 --> 00:24:56.520 align:start position:0% and actually this one could really 00:24:56.520 --> 00:24:58.730 align:start position:0% and actually this one could really by<00:24:57.000> actually<00:24:57.240> solving<00:24:57.720> the<00:24:57.900> first<00:24:58.380> one<00:24:58.500> so 00:24:58.730 --> 00:24:58.740 align:start position:0% by actually solving the first one so 00:24:58.740 --> 00:25:00.950 align:start position:0% by actually solving the first one so this<00:24:59.159> one<00:24:59.340> is<00:24:59.460> really<00:24:59.640> an<00:24:59.880> alternative<00:25:00.240> but<00:25:00.659> uh 00:25:00.950 --> 00:25:00.960 align:start position:0% this one is really an alternative but uh 00:25:00.960 --> 00:25:03.169 align:start position:0% this one is really an alternative but uh I<00:25:01.440> don't<00:25:01.559> see<00:25:01.679> any<00:25:01.799> reason<00:25:01.980> to<00:25:02.280> just 00:25:03.169 --> 00:25:03.179 align:start position:0% I don't see any reason to just 00:25:03.179 --> 00:25:05.450 align:start position:0% I don't see any reason to just um<00:25:03.299> add<00:25:04.200> another<00:25:04.559> one<00:25:04.799> especially<00:25:05.159> I<00:25:05.340> think 00:25:05.450 --> 00:25:05.460 align:start position:0% um add another one especially I think 00:25:05.460 --> 00:25:07.730 align:start position:0% um add another one especially I think graphql<00:25:05.940> is<00:25:06.059> not<00:25:06.240> supported<00:25:06.659> in<00:25:07.320> all<00:25:07.440> the<00:25:07.559> node 00:25:07.730 --> 00:25:07.740 align:start position:0% graphql is not supported in all the node 00:25:07.740 --> 00:25:10.370 align:start position:0% graphql is not supported in all the node implementation<00:25:08.280> today 00:25:10.370 --> 00:25:10.380 align:start position:0% implementation today 00:25:10.380 --> 00:25:11.210 align:start position:0% implementation today um 00:25:11.210 --> 00:25:11.220 align:start position:0% um 00:25:11.220 --> 00:25:13.909 align:start position:0% um and<00:25:11.880> so<00:25:12.000> as<00:25:12.720> I<00:25:12.840> say<00:25:12.960> I<00:25:13.080> went<00:25:13.200> to<00:25:13.320> the<00:25:13.440> core<00:25:13.679> Dev 00:25:13.909 --> 00:25:13.919 align:start position:0% and so as I say I went to the core Dev 00:25:13.919 --> 00:25:15.770 align:start position:0% and so as I say I went to the core Dev and<00:25:14.220> we<00:25:14.520> had<00:25:14.640> the<00:25:14.880> feedback<00:25:15.179> and<00:25:15.480> the<00:25:15.659> main 00:25:15.770 --> 00:25:15.780 align:start position:0% and we had the feedback and the main 00:25:15.780 --> 00:25:19.850 align:start position:0% and we had the feedback and the main feedback<00:25:16.520> was<00:25:17.520> that<00:25:17.940> hey<00:25:18.600> there<00:25:19.440> is<00:25:19.559> no<00:25:19.679> point 00:25:19.850 --> 00:25:19.860 align:start position:0% feedback was that hey there is no point 00:25:19.860 --> 00:25:23.090 align:start position:0% feedback was that hey there is no point to<00:25:19.980> do<00:25:20.159> it<00:25:20.280> because<00:25:20.580> we<00:25:20.880> are<00:25:21.059> going<00:25:21.240> to<00:25:21.780> make<00:25:22.440> uh 00:25:23.090 --> 00:25:23.100 align:start position:0% to do it because we are going to make uh 00:25:23.100 --> 00:25:24.950 align:start position:0% to do it because we are going to make uh the<00:25:23.700> logs 00:25:24.950 --> 00:25:24.960 align:start position:0% the logs 00:25:24.960 --> 00:25:27.289 align:start position:0% the logs uh<00:25:25.679> not<00:25:25.860> being<00:25:26.039> accessible<00:25:26.520> after<00:25:27.000> a<00:25:27.179> certain 00:25:27.289 --> 00:25:27.299 align:start position:0% uh not being accessible after a certain 00:25:27.299 --> 00:25:30.049 align:start position:0% uh not being accessible after a certain time<00:25:27.659> and<00:25:28.440> so<00:25:28.559> the<00:25:28.740> argument<00:25:29.100> was<00:25:29.400> like<00:25:29.580> you 00:25:30.049 --> 00:25:30.059 align:start position:0% time and so the argument was like you 00:25:30.059 --> 00:25:31.730 align:start position:0% time and so the argument was like you will<00:25:30.179> never<00:25:30.299> have<00:25:30.539> that<00:25:30.720> many<00:25:30.900> log<00:25:31.140> and<00:25:31.500> so 00:25:31.730 --> 00:25:31.740 align:start position:0% will never have that many log and so 00:25:31.740 --> 00:25:34.190 align:start position:0% will never have that many log and so requesting<00:25:32.640> the<00:25:32.760> timestamp<00:25:33.240> anyway<00:25:33.720> won't 00:25:34.190 --> 00:25:34.200 align:start position:0% requesting the timestamp anyway won't 00:25:34.200 --> 00:25:38.210 align:start position:0% requesting the timestamp anyway won't matter<00:25:34.580> uh<00:25:35.580> and<00:25:35.880> so<00:25:36.059> my<00:25:36.179> reply<00:25:36.539> is<00:25:36.720> that<00:25:37.039> uh<00:25:38.039> so 00:25:38.210 --> 00:25:38.220 align:start position:0% matter uh and so my reply is that uh so 00:25:38.220 --> 00:25:40.250 align:start position:0% matter uh and so my reply is that uh so it's<00:25:38.460> an<00:25:38.700> easy<00:25:38.820> change 00:25:40.250 --> 00:25:40.260 align:start position:0% it's an easy change 00:25:40.260 --> 00:25:42.769 align:start position:0% it's an easy change uh<00:25:40.980> so<00:25:41.220> my<00:25:41.400> next<00:25:41.580> action<00:25:41.880> would<00:25:42.120> be<00:25:42.240> to<00:25:42.360> make<00:25:42.539> a 00:25:42.769 --> 00:25:42.779 align:start position:0% uh so my next action would be to make a 00:25:42.779 --> 00:25:45.470 align:start position:0% uh so my next action would be to make a PR<00:25:42.960> I<00:25:43.380> guess<00:25:43.440> for<00:25:43.740> goitream 00:25:45.470 --> 00:25:45.480 align:start position:0% PR I guess for goitream 00:25:45.480 --> 00:25:48.110 align:start position:0% PR I guess for goitream um<00:25:45.740> and<00:25:46.740> and<00:25:47.159> the<00:25:47.340> number<00:25:47.460> of<00:25:47.580> log<00:25:47.760> actually 00:25:48.110 --> 00:25:48.120 align:start position:0% um and and the number of log actually 00:25:48.120 --> 00:25:50.630 align:start position:0% um and and the number of log actually can<00:25:48.360> still<00:25:48.539> be<00:25:48.659> significant 00:25:50.630 --> 00:25:50.640 align:start position:0% can still be significant 00:25:50.640 --> 00:25:52.549 align:start position:0% can still be significant um<00:25:50.700> so<00:25:50.880> even<00:25:51.000> if<00:25:51.360> we 00:25:52.549 --> 00:25:52.559 align:start position:0% um so even if we 00:25:52.559 --> 00:25:54.830 align:start position:0% um so even if we remove<00:25:53.039> past<00:25:53.400> log<00:25:53.640> we<00:25:53.880> still<00:25:54.059> want<00:25:54.240> to<00:25:54.360> to<00:25:54.600> have 00:25:54.830 --> 00:25:54.840 align:start position:0% remove past log we still want to to have 00:25:54.840 --> 00:25:56.870 align:start position:0% remove past log we still want to to have access<00:25:55.140> to<00:25:55.440> them<00:25:55.559> but<00:25:56.039> actually<00:25:56.279> the<00:25:56.640> main 00:25:56.870 --> 00:25:56.880 align:start position:0% access to them but actually the main 00:25:56.880 --> 00:25:59.810 align:start position:0% access to them but actually the main issue<00:25:57.120> with<00:25:57.299> that<00:25:57.480> with<00:25:58.200> that<00:25:58.500> feedback<00:25:59.100> is 00:25:59.810 --> 00:25:59.820 align:start position:0% issue with that with that feedback is 00:25:59.820 --> 00:26:01.549 align:start position:0% issue with that with that feedback is that<00:26:00.059> we<00:26:00.120> need<00:26:00.299> to<00:26:00.419> really<00:26:00.600> think 00:26:01.549 --> 00:26:01.559 align:start position:0% that we need to really think 00:26:01.559 --> 00:26:05.269 align:start position:0% that we need to really think how<00:26:02.100> we<00:26:02.279> are<00:26:02.400> going<00:26:02.580> to<00:26:02.880> solve<00:26:03.659> the<00:26:04.620> state 00:26:05.269 --> 00:26:05.279 align:start position:0% how we are going to solve the state 00:26:05.279 --> 00:26:07.430 align:start position:0% how we are going to solve the state access<00:26:05.580> about 00:26:07.430 --> 00:26:07.440 align:start position:0% access about 00:26:07.440 --> 00:26:09.529 align:start position:0% access about um<00:26:07.500> if<00:26:08.159> we<00:26:08.279> we<00:26:08.460> don't<00:26:08.640> have<00:26:08.760> access<00:26:08.940> to<00:26:09.179> pass 00:26:09.529 --> 00:26:09.539 align:start position:0% um if we we don't have access to pass 00:26:09.539 --> 00:26:12.470 align:start position:0% um if we we don't have access to pass logs<00:26:10.020> how<00:26:10.500> do<00:26:10.620> we<00:26:10.740> are<00:26:10.860> going<00:26:10.980> to<00:26:11.100> index<00:26:11.460> uh<00:26:12.299> in 00:26:12.470 --> 00:26:12.480 align:start position:0% logs how do we are going to index uh in 00:26:12.480 --> 00:26:14.390 align:start position:0% logs how do we are going to index uh in a<00:26:12.539> decentralized<00:26:13.080> manner 00:26:14.390 --> 00:26:14.400 align:start position:0% a decentralized manner 00:26:14.400 --> 00:26:15.409 align:start position:0% a decentralized manner um<00:26:14.460> because<00:26:14.580> of<00:26:14.820> course<00:26:14.940> if<00:26:15.059> you<00:26:15.179> have<00:26:15.299> a 00:26:15.409 --> 00:26:15.419 align:start position:0% um because of course if you have a 00:26:15.419 --> 00:26:17.090 align:start position:0% um because of course if you have a backhand<00:26:15.720> you<00:26:16.260> know<00:26:16.380> you<00:26:16.500> solve<00:26:16.799> your<00:26:16.919> problem 00:26:17.090 --> 00:26:17.100 align:start position:0% backhand you know you solve your problem 00:26:17.100 --> 00:26:19.370 align:start position:0% backhand you know you solve your problem but<00:26:17.400> we<00:26:17.640> we<00:26:17.940> don't<00:26:18.480> want<00:26:18.600> to<00:26:18.779> have<00:26:18.900> a<00:26:19.080> back-end 00:26:19.370 --> 00:26:19.380 align:start position:0% but we we don't want to have a back-end 00:26:19.380 --> 00:26:21.409 align:start position:0% but we we don't want to have a back-end right<00:26:19.860> you<00:26:20.279> want<00:26:20.460> to<00:26:20.580> be<00:26:20.640> able<00:26:20.760> to<00:26:20.880> use<00:26:21.000> tornado 00:26:21.409 --> 00:26:21.419 align:start position:0% right you want to be able to use tornado 00:26:21.419 --> 00:26:24.110 align:start position:0% right you want to be able to use tornado cache<00:26:21.960> from<00:26:22.380> your<00:26:22.559> browser<00:26:22.980> without<00:26:23.460> relying 00:26:24.110 --> 00:26:24.120 align:start position:0% cache from your browser without relying 00:26:24.120 --> 00:26:27.250 align:start position:0% cache from your browser without relying with<00:26:25.020> only<00:26:25.320> relying<00:26:25.740> on<00:26:25.799> your<00:26:25.919> node 00:26:27.250 --> 00:26:27.260 align:start position:0% with only relying on your node 00:26:27.260 --> 00:26:30.890 align:start position:0% with only relying on your node and<00:26:28.260> so<00:26:28.520> so<00:26:29.520> I<00:26:29.820> think<00:26:29.940> I<00:26:30.299> don't<00:26:30.360> know<00:26:30.480> for<00:26:30.779> me 00:26:30.890 --> 00:26:30.900 align:start position:0% and so so I think I don't know for me 00:26:30.900 --> 00:26:33.289 align:start position:0% and so so I think I don't know for me that<00:26:31.260> I<00:26:31.860> would<00:26:31.980> like<00:26:32.159> to<00:26:32.279> to<00:26:32.580> have<00:26:32.820> discussion 00:26:33.289 --> 00:26:33.299 align:start position:0% that I would like to to have discussion 00:26:33.299 --> 00:26:35.810 align:start position:0% that I would like to to have discussion as<00:26:33.539> a<00:26:33.779> community<00:26:33.900> how<00:26:34.200> we<00:26:34.440> can<00:26:34.559> so<00:26:34.799> solve<00:26:35.640> that 00:26:35.810 --> 00:26:35.820 align:start position:0% as a community how we can so solve that 00:26:35.820 --> 00:26:38.390 align:start position:0% as a community how we can so solve that like<00:26:36.120> I<00:26:36.720> know<00:26:36.840> there<00:26:37.020> is<00:26:37.200> work<00:26:37.380> on<00:26:37.559> the<00:26:37.740> uh 00:26:38.390 --> 00:26:38.400 align:start position:0% like I know there is work on the uh 00:26:38.400 --> 00:26:40.370 align:start position:0% like I know there is work on the uh around<00:26:38.940> like<00:26:39.240> right<00:26:39.419> now<00:26:39.600> about<00:26:39.840> portal 00:26:40.370 --> 00:26:40.380 align:start position:0% around like right now about portal 00:26:40.380 --> 00:26:43.490 align:start position:0% around like right now about portal things<00:26:41.159> portal<00:26:41.580> Network 00:26:43.490 --> 00:26:43.500 align:start position:0% things portal Network 00:26:43.500 --> 00:26:46.850 align:start position:0% things portal Network um<00:26:43.620> and<00:26:44.039> so<00:26:44.159> but<00:26:44.760> I<00:26:44.940> think<00:26:45.059> it's<00:26:45.480> important<00:26:45.779> we 00:26:46.850 --> 00:26:46.860 align:start position:0% um and so but I think it's important we 00:26:46.860 --> 00:26:48.350 align:start position:0% um and so but I think it's important we um we<00:26:47.220> understand<00:26:47.340> like<00:26:47.700> the<00:26:47.880> point<00:26:48.120> of<00:26:48.240> view 00:26:48.350 --> 00:26:48.360 align:start position:0% um we understand like the point of view 00:26:48.360 --> 00:26:50.870 align:start position:0% um we understand like the point of view of<00:26:48.539> application<00:26:49.020> developer<00:26:49.620> that<00:26:50.279> don't<00:26:50.520> want 00:26:50.870 --> 00:26:50.880 align:start position:0% of application developer that don't want 00:26:50.880 --> 00:26:53.570 align:start position:0% of application developer that don't want to<00:26:51.419> be<00:26:51.659> involved<00:26:52.020> with<00:26:52.140> our<00:26:52.380> application<00:26:52.799> once 00:26:53.570 --> 00:26:53.580 align:start position:0% to be involved with our application once 00:26:53.580 --> 00:26:55.430 align:start position:0% to be involved with our application once it's<00:26:53.700> launched 00:26:55.430 --> 00:26:55.440 align:start position:0% it's launched 00:26:55.440 --> 00:26:56.029 align:start position:0% it's launched um 00:26:56.029 --> 00:26:56.039 align:start position:0% um 00:26:56.039 --> 00:26:59.510 align:start position:0% um and<00:26:57.000> another<00:26:57.840> thing 00:26:59.510 --> 00:26:59.520 align:start position:0% and another thing 00:26:59.520 --> 00:27:01.850 align:start position:0% and another thing yeah<00:27:00.000> so<00:27:00.120> I<00:27:00.360> mentioned<00:27:00.600> like<00:27:00.779> most<00:27:01.020> systems 00:27:01.850 --> 00:27:01.860 align:start position:0% yeah so I mentioned like most systems 00:27:01.860 --> 00:27:04.190 align:start position:0% yeah so I mentioned like most systems already<00:27:02.279> rely<00:27:02.760> on<00:27:02.880> the<00:27:03.000> log<00:27:03.179> events<00:27:03.600> we<00:27:04.080> need 00:27:04.190 --> 00:27:04.200 align:start position:0% already rely on the log events we need 00:27:04.200 --> 00:27:06.350 align:start position:0% already rely on the log events we need this<00:27:05.039> system<00:27:05.220> anyway 00:27:06.350 --> 00:27:06.360 align:start position:0% this system anyway 00:27:06.360 --> 00:27:09.470 align:start position:0% this system anyway and<00:27:06.779> even<00:27:06.900> some<00:27:07.140> EIP<00:27:07.440> have<00:27:08.100> been<00:27:08.279> using<00:27:08.640> it<00:27:08.820> to 00:27:09.470 --> 00:27:09.480 align:start position:0% and even some EIP have been using it to 00:27:09.480 --> 00:27:11.570 align:start position:0% and even some EIP have been using it to kind<00:27:09.600> of<00:27:09.720> speed<00:27:09.960> up<00:27:10.140> the 00:27:11.570 --> 00:27:11.580 align:start position:0% kind of speed up the 00:27:11.580 --> 00:27:14.090 align:start position:0% kind of speed up the the<00:27:11.820> needle<00:27:12.299> kind<00:27:12.600> of<00:27:12.720> minimize<00:27:13.620> the<00:27:13.740> gas<00:27:13.860> cost 00:27:14.090 --> 00:27:14.100 align:start position:0% the needle kind of minimize the gas cost 00:27:14.100 --> 00:27:17.210 align:start position:0% the needle kind of minimize the gas cost which<00:27:14.400> is<00:27:14.900> eip1155<00:27:15.900> like<00:27:16.320> you<00:27:16.740> can't<00:27:16.860> query 00:27:17.210 --> 00:27:17.220 align:start position:0% which is eip1155 like you can't query 00:27:17.220 --> 00:27:19.909 align:start position:0% which is eip1155 like you can't query the<00:27:17.520> balance<00:27:17.880> of<00:27:18.539> all<00:27:18.720> the<00:27:18.900> token<00:27:19.260> that<00:27:19.799> the 00:27:19.909 --> 00:27:19.919 align:start position:0% the balance of all the token that the 00:27:19.919 --> 00:27:22.070 align:start position:0% the balance of all the token that the user<00:27:20.279> owned<00:27:20.580> from<00:27:20.820> the<00:27:20.940> smart<00:27:21.120> contract<00:27:21.539> and 00:27:22.070 --> 00:27:22.080 align:start position:0% user owned from the smart contract and 00:27:22.080 --> 00:27:23.390 align:start position:0% user owned from the smart contract and so<00:27:22.200> you're<00:27:22.320> always<00:27:22.559> a<00:27:22.740> smart<00:27:22.860> contract<00:27:23.100> to<00:27:23.279> be 00:27:23.390 --> 00:27:23.400 align:start position:0% so you're always a smart contract to be 00:27:23.400 --> 00:27:26.090 align:start position:0% so you're always a smart contract to be more<00:27:23.520> efficient<00:27:23.940> and<00:27:24.840> it's<00:27:25.380> because<00:27:25.620> it<00:27:25.980> has 00:27:26.090 --> 00:27:26.100 align:start position:0% more efficient and it's because it has 00:27:26.100 --> 00:27:26.990 align:start position:0% more efficient and it's because it has been<00:27:26.220> the<00:27:26.400> result<00:27:26.520> of<00:27:26.820> everybody 00:27:26.990 --> 00:27:27.000 align:start position:0% been the result of everybody 00:27:27.000 --> 00:27:30.549 align:start position:0% been the result of everybody acknowledging<00:27:27.840> that<00:27:28.140> we<00:27:28.860> use<00:27:29.039> logs<00:27:29.940> and<00:27:30.120> event 00:27:30.549 --> 00:27:30.559 align:start position:0% acknowledging that we use logs and event 00:27:30.559 --> 00:27:34.130 align:start position:0% acknowledging that we use logs and event to<00:27:31.559> reconstruct<00:27:32.159> the<00:27:32.400> state 00:27:34.130 --> 00:27:34.140 align:start position:0% to reconstruct the state 00:27:34.140 --> 00:27:34.850 align:start position:0% to reconstruct the state um 00:27:34.850 --> 00:27:34.860 align:start position:0% um 00:27:34.860 --> 00:27:37.190 align:start position:0% um but<00:27:35.580> that<00:27:35.820> interestingly<00:27:36.360> one<00:27:36.900> of<00:27:36.960> the<00:27:37.080> things 00:27:37.190 --> 00:27:37.200 align:start position:0% but that interestingly one of the things 00:27:37.200 --> 00:27:38.750 align:start position:0% but that interestingly one of the things about<00:27:37.380> in<00:27:37.679> the<00:27:37.740> code<00:27:37.860> of<00:27:38.159> meeting<00:27:38.279> was<00:27:38.580> that 00:27:38.750 --> 00:27:38.760 align:start position:0% about in the code of meeting was that 00:27:38.760 --> 00:27:41.570 align:start position:0% about in the code of meeting was that that<00:27:39.419> was<00:27:39.659> not<00:27:39.840> the<00:27:40.020> vision<00:27:40.260> initially 00:27:41.570 --> 00:27:41.580 align:start position:0% that was not the vision initially 00:27:41.580 --> 00:27:45.230 align:start position:0% that was not the vision initially but<00:27:42.419> now<00:27:43.080> we<00:27:43.740> evolve<00:27:44.159> we<00:27:44.400> understand<00:27:44.640> what<00:27:45.059> we 00:27:45.230 --> 00:27:45.240 align:start position:0% but now we evolve we understand what we 00:27:45.240 --> 00:27:47.450 align:start position:0% but now we evolve we understand what we need<00:27:45.360> and<00:27:45.600> so<00:27:45.960> I<00:27:46.080> think<00:27:46.260> yeah<00:27:46.380> that<00:27:46.740> I<00:27:47.039> I<00:27:47.159> will 00:27:47.450 --> 00:27:47.460 align:start position:0% need and so I think yeah that I I will 00:27:47.460 --> 00:27:50.690 align:start position:0% need and so I think yeah that I I will end<00:27:47.700> with<00:27:48.059> uh<00:27:48.419> with<00:27:49.200> like<00:27:49.440> yeah<00:27:49.679> let's<00:27:50.100> discuss 00:27:50.690 --> 00:27:50.700 align:start position:0% end with uh with like yeah let's discuss 00:27:50.700 --> 00:27:52.909 align:start position:0% end with uh with like yeah let's discuss about<00:27:51.000> how<00:27:51.419> to<00:27:51.600> solve<00:27:51.960> this<00:27:52.140> being<00:27:52.620> able<00:27:52.799> to 00:27:52.909 --> 00:27:52.919 align:start position:0% about how to solve this being able to 00:27:52.919 --> 00:27:55.310 align:start position:0% about how to solve this being able to rebuild<00:27:53.400> uh<00:27:54.179> the<00:27:54.360> state<00:27:54.539> from<00:27:54.840> from<00:27:55.080> the 00:27:55.310 --> 00:27:55.320 align:start position:0% rebuild uh the state from from the 00:27:55.320 --> 00:27:57.890 align:start position:0% rebuild uh the state from from the client 00:27:57.890 --> 00:27:57.900 align:start position:0% 00:27:57.900 --> 00:28:00.890 align:start position:0% it's<00:27:58.260> kind<00:27:58.500> of<00:27:58.679> all<00:27:59.640> for<00:28:00.000> me<00:28:00.179> yeah<00:28:00.539> any 00:28:00.890 --> 00:28:00.900 align:start position:0% it's kind of all for me yeah any 00:28:00.900 --> 00:28:03.950 align:start position:0% it's kind of all for me yeah any question 00:28:03.950 --> 00:28:03.960 align:start position:0% 00:28:03.960 --> 00:28:06.710 align:start position:0% thank<00:28:04.440> you<00:28:04.559> thank<00:28:05.039> you<00:28:05.220> Ronan<00:28:05.760> thank<00:28:06.120> you<00:28:06.179> for 00:28:06.710 --> 00:28:06.720 align:start position:0% thank you thank you Ronan thank you for 00:28:06.720 --> 00:28:10.310 align:start position:0% thank you thank you Ronan thank you for close 00:28:10.310 --> 00:28:10.320 align:start position:0% 00:28:10.320 --> 00:28:13.190 align:start position:0% uh<00:28:11.159> do<00:28:11.340> so<00:28:11.700> we<00:28:12.000> have<00:28:12.120> uh<00:28:12.419> we<00:28:12.720> have<00:28:12.840> time<00:28:12.960> for 00:28:13.190 --> 00:28:13.200 align:start position:0% uh do so we have uh we have time for 00:28:13.200 --> 00:28:20.210 align:start position:0% uh do so we have uh we have time for questions<00:28:13.460> do<00:28:14.460> we<00:28:14.580> have<00:28:14.700> any<00:28:14.880> questions 00:28:20.210 --> 00:28:20.220 align:start position:0% 00:28:20.220 --> 00:28:22.310 align:start position:0% in<00:28:21.120> the<00:28:21.240> contract 00:28:22.310 --> 00:28:22.320 align:start position:0% in the contract 00:28:22.320 --> 00:28:24.049 align:start position:0% in the contract what<00:28:22.740> are<00:28:22.860> your<00:28:22.980> thoughts<00:28:23.220> on<00:28:23.340> using<00:28:23.640> Getters 00:28:24.049 --> 00:28:24.059 align:start position:0% what are your thoughts on using Getters 00:28:24.059 --> 00:28:26.269 align:start position:0% what are your thoughts on using Getters in<00:28:24.299> the<00:28:24.419> contract<00:28:24.720> as<00:28:25.020> opposed<00:28:25.320> to<00:28:25.380> events<00:28:26.039> to 00:28:26.269 --> 00:28:26.279 align:start position:0% in the contract as opposed to events to 00:28:26.279 --> 00:28:28.130 align:start position:0% in the contract as opposed to events to get<00:28:26.400> the<00:28:26.580> data<00:28:26.820> for<00:28:27.000> a<00:28:27.179> UI 00:28:28.130 --> 00:28:28.140 align:start position:0% get the data for a UI 00:28:28.140 --> 00:28:29.810 align:start position:0% get the data for a UI yeah<00:28:28.679> so 00:28:29.810 --> 00:28:29.820 align:start position:0% yeah so 00:28:29.820 --> 00:28:32.750 align:start position:0% yeah so so<00:28:30.240> far<00:28:30.480> I<00:28:30.900> I<00:28:31.200> can<00:28:31.500> talk<00:28:31.860> about<00:28:32.039> my<00:28:32.460> game 00:28:32.750 --> 00:28:32.760 align:start position:0% so far I I can talk about my game 00:28:32.760 --> 00:28:34.430 align:start position:0% so far I I can talk about my game actually<00:28:33.000> on<00:28:33.360> that<00:28:33.539> front<00:28:33.720> so<00:28:33.960> the<00:28:34.200> first 00:28:34.430 --> 00:28:34.440 align:start position:0% actually on that front so the first 00:28:34.440 --> 00:28:36.230 align:start position:0% actually on that front so the first version<00:28:34.740> I<00:28:35.100> really<00:28:35.279> wanted<00:28:35.520> to<00:28:35.820> launch<00:28:36.059> the 00:28:36.230 --> 00:28:36.240 align:start position:0% version I really wanted to launch the 00:28:36.240 --> 00:28:38.690 align:start position:0% version I really wanted to launch the first<00:28:36.480> version<00:28:36.659> without<00:28:36.960> any<00:28:37.380> back<00:28:37.799> end<00:28:38.039> so 00:28:38.690 --> 00:28:38.700 align:start position:0% first version without any back end so 00:28:38.700 --> 00:28:40.010 align:start position:0% first version without any back end so the<00:28:38.820> first<00:28:38.940> version<00:28:39.240> of<00:28:39.419> the<00:28:39.539> game<00:28:39.659> the<00:28:39.900> first 00:28:40.010 --> 00:28:40.020 align:start position:0% the first version of the game the first 00:28:40.020 --> 00:28:42.169 align:start position:0% the first version of the game the first Alpha<00:28:40.500> uh 00:28:42.169 --> 00:28:42.179 align:start position:0% Alpha uh 00:28:42.179 --> 00:28:44.510 align:start position:0% Alpha uh I<00:28:42.659> didn't<00:28:43.020> have<00:28:43.200> an<00:28:43.380> indexer<00:28:43.799> using<00:28:44.159> the<00:28:44.279> log 00:28:44.510 --> 00:28:44.520 align:start position:0% I didn't have an indexer using the log 00:28:44.520 --> 00:28:48.710 align:start position:0% I didn't have an indexer using the log and<00:28:45.120> I<00:28:45.419> was<00:28:45.600> fetching<00:28:46.080> all<00:28:46.559> the<00:28:46.799> data<00:28:47.159> and<00:28:47.720> it 00:28:48.710 --> 00:28:48.720 align:start position:0% and I was fetching all the data and it 00:28:48.720 --> 00:28:50.930 align:start position:0% and I was fetching all the data and it is<00:28:49.500> not<00:28:49.799> actually<00:28:50.039> it's<00:28:50.340> not<00:28:50.520> efficient 00:28:50.930 --> 00:28:50.940 align:start position:0% is not actually it's not efficient 00:28:50.940 --> 00:28:53.390 align:start position:0% is not actually it's not efficient either<00:28:51.240> because<00:28:51.659> uh<00:28:52.559> especially<00:28:53.039> list<00:28:53.220> of 00:28:53.390 --> 00:28:53.400 align:start position:0% either because uh especially list of 00:28:53.400 --> 00:28:56.330 align:start position:0% either because uh especially list of things<00:28:53.779> and<00:28:54.779> and<00:28:55.140> you<00:28:55.380> are<00:28:55.500> wasting<00:28:55.860> gas<00:28:56.039> to 00:28:56.330 --> 00:28:56.340 align:start position:0% things and and you are wasting gas to 00:28:56.340 --> 00:28:59.090 align:start position:0% things and and you are wasting gas to support<00:28:56.580> that<00:28:56.940> in<00:28:57.059> many<00:28:57.240> cases<00:28:57.659> like<00:28:58.260> so<00:28:58.860> this 00:28:59.090 --> 00:28:59.100 align:start position:0% support that in many cases like so this 00:28:59.100 --> 00:29:02.149 align:start position:0% support that in many cases like so this is<00:28:59.220> uh<00:28:59.460> what<00:28:59.700> I<00:28:59.820> mentioned<00:29:00.440> eip1155<00:29:01.440> not 00:29:02.149 --> 00:29:02.159 align:start position:0% is uh what I mentioned eip1155 not 00:29:02.159 --> 00:29:04.130 align:start position:0% is uh what I mentioned eip1155 not having<00:29:02.340> access<00:29:02.640> to<00:29:02.940> the<00:29:03.179> balance<00:29:03.539> and<00:29:03.960> we 00:29:04.130 --> 00:29:04.140 align:start position:0% having access to the balance and we 00:29:04.140 --> 00:29:06.049 align:start position:0% having access to the balance and we could<00:29:04.200> also<00:29:04.500> think<00:29:04.679> about 00:29:06.049 --> 00:29:06.059 align:start position:0% could also think about 00:29:06.059 --> 00:29:08.870 align:start position:0% could also think about um your<00:29:06.900> seven<00:29:07.260> to<00:29:07.440> one 00:29:08.870 --> 00:29:08.880 align:start position:0% um your seven to one 00:29:08.880 --> 00:29:11.390 align:start position:0% um your seven to one um<00:29:09.200> enumerable<00:29:10.200> extension<00:29:10.799> which<00:29:11.159> add 00:29:11.390 --> 00:29:11.400 align:start position:0% um enumerable extension which add 00:29:11.400 --> 00:29:14.090 align:start position:0% um enumerable extension which add actually<00:29:11.640> a<00:29:11.820> lot<00:29:11.880> of<00:29:12.000> gas<00:29:12.240> cost<00:29:12.480> overall 00:29:14.090 --> 00:29:14.100 align:start position:0% actually a lot of gas cost overall 00:29:14.100 --> 00:29:17.269 align:start position:0% actually a lot of gas cost overall um<00:29:14.640> so<00:29:15.419> I<00:29:15.720> and<00:29:16.020> I<00:29:16.200> think<00:29:16.380> from<00:29:16.679> what<00:29:16.980> we<00:29:17.159> have 00:29:17.269 --> 00:29:17.279 align:start position:0% um so I and I think from what we have 00:29:17.279 --> 00:29:20.630 align:start position:0% um so I and I think from what we have seen<00:29:17.539> everybody<00:29:18.539> like<00:29:19.080> even<00:29:19.559> to<00:29:19.980> to<00:29:20.220> do<00:29:20.460> that 00:29:20.630 --> 00:29:20.640 align:start position:0% seen everybody like even to to do that 00:29:20.640 --> 00:29:22.250 align:start position:0% seen everybody like even to to do that role<00:29:21.000> so<00:29:21.240> I<00:29:21.360> think 00:29:22.250 --> 00:29:22.260 align:start position:0% role so I think 00:29:22.260 --> 00:29:24.110 align:start position:0% role so I think that's<00:29:22.799> what<00:29:23.039> we<00:29:23.159> should<00:29:23.279> do<00:29:23.460> and<00:29:23.700> minimize 00:29:24.110 --> 00:29:24.120 align:start position:0% that's what we should do and minimize 00:29:24.120 --> 00:29:26.389 align:start position:0% that's what we should do and minimize the<00:29:24.299> role<00:29:24.600> of<00:29:24.720> the<00:29:24.960> yeah<00:29:25.679> minimize<00:29:26.100> the<00:29:26.220> gas 00:29:26.389 --> 00:29:26.399 align:start position:0% the role of the yeah minimize the gas 00:29:26.399 --> 00:29:28.250 align:start position:0% the role of the yeah minimize the gas cost<00:29:26.640> we<00:29:26.940> basically<00:29:27.240> that<00:29:27.480> was<00:29:27.600> when<00:29:27.779> we<00:29:27.960> Nima 00:29:28.250 --> 00:29:28.260 align:start position:0% cost we basically that was when we Nima 00:29:28.260 --> 00:29:29.690 align:start position:0% cost we basically that was when we Nima is<00:29:28.380> the<00:29:28.500> things<00:29:28.679> that<00:29:28.860> happen<00:29:29.039> on<00:29:29.399> the<00:29:29.520> Chain 00:29:29.690 --> 00:29:29.700 align:start position:0% is the things that happen on the Chain 00:29:29.700 --> 00:29:32.510 align:start position:0% is the things that happen on the Chain if<00:29:30.299> we<00:29:30.419> can<00:29:30.539> do<00:29:30.659> it<00:29:30.840> of<00:29:31.020> chain<00:29:31.260> but<00:29:31.860> it's<00:29:32.100> assume 00:29:32.510 --> 00:29:32.520 align:start position:0% if we can do it of chain but it's assume 00:29:32.520 --> 00:29:34.130 align:start position:0% if we can do it of chain but it's assume we<00:29:32.700> have<00:29:32.760> a<00:29:32.940> system<00:29:33.059> to<00:29:33.419> retrieve<00:29:33.840> it<00:29:33.899> that's 00:29:34.130 --> 00:29:34.140 align:start position:0% we have a system to retrieve it that's 00:29:34.140 --> 00:29:35.450 align:start position:0% we have a system to retrieve it that's why<00:29:34.260> I<00:29:34.380> think<00:29:34.500> it's<00:29:34.620> important<00:29:34.919> to<00:29:35.100> discuss 00:29:35.450 --> 00:29:35.460 align:start position:0% why I think it's important to discuss 00:29:35.460 --> 00:29:37.789 align:start position:0% why I think it's important to discuss because<00:29:36.299> maybe<00:29:36.539> the<00:29:36.779> conclusion<00:29:37.200> is<00:29:37.380> like<00:29:37.620> oh 00:29:37.789 --> 00:29:37.799 align:start position:0% because maybe the conclusion is like oh 00:29:37.799 --> 00:29:39.529 align:start position:0% because maybe the conclusion is like oh actually<00:29:37.980> we<00:29:38.340> cannot<00:29:38.640> and<00:29:38.940> we<00:29:39.120> have<00:29:39.240> to<00:29:39.360> pay 00:29:39.529 --> 00:29:39.539 align:start position:0% actually we cannot and we have to pay 00:29:39.539 --> 00:29:41.450 align:start position:0% actually we cannot and we have to pay gas<00:29:39.779> to<00:29:40.080> do<00:29:40.200> that<00:29:40.320> but<00:29:40.559> I<00:29:40.740> hope<00:29:40.860> it's<00:29:41.039> not<00:29:41.279> the 00:29:41.450 --> 00:29:41.460 align:start position:0% gas to do that but I hope it's not the 00:29:41.460 --> 00:29:44.029 align:start position:0% gas to do that but I hope it's not the case 00:29:44.029 --> 00:29:44.039 align:start position:0% 00:29:44.039 --> 00:29:47.450 align:start position:0% hello<00:29:44.940> everyone<00:29:45.559> I'm<00:29:46.559> gonna<00:29:46.799> start<00:29:47.039> my<00:29:47.279> timer 00:29:47.450 --> 00:29:47.460 align:start position:0% hello everyone I'm gonna start my timer 00:29:47.460 --> 00:29:51.529 align:start position:0% hello everyone I'm gonna start my timer so<00:29:47.820> I<00:29:48.000> have<00:29:48.120> a<00:29:48.419> reference<00:29:49.380> point<00:29:49.679> here<00:29:50.179> uh<00:29:51.179> yeah 00:29:51.529 --> 00:29:51.539 align:start position:0% so I have a reference point here uh yeah 00:29:51.539 --> 00:29:53.630 align:start position:0% so I have a reference point here uh yeah this<00:29:51.899> is<00:29:52.020> my<00:29:52.260> first<00:29:52.440> time<00:29:52.620> actually<00:29:52.919> talking 00:29:53.630 --> 00:29:53.640 align:start position:0% this is my first time actually talking 00:29:53.640 --> 00:29:56.269 align:start position:0% this is my first time actually talking at<00:29:53.940> Defcon<00:29:54.419> this<00:29:54.600> is<00:29:54.720> my<00:29:54.840> second<00:29:54.899> Devcon 00:29:56.269 --> 00:29:56.279 align:start position:0% at Defcon this is my second Devcon 00:29:56.279 --> 00:29:58.250 align:start position:0% at Defcon this is my second Devcon um<00:29:56.399> I'm<00:29:56.880> super<00:29:57.059> happy<00:29:57.360> to<00:29:57.539> be<00:29:57.659> contributing 00:29:58.250 --> 00:29:58.260 align:start position:0% um I'm super happy to be contributing 00:29:58.260 --> 00:30:00.769 align:start position:0% um I'm super happy to be contributing back<00:29:58.500> and<00:29:59.039> sharing<00:29:59.700> knowledge<00:30:00.059> and<00:30:00.539> the 00:30:00.769 --> 00:30:00.779 align:start position:0% back and sharing knowledge and the 00:30:00.779 --> 00:30:03.710 align:start position:0% back and sharing knowledge and the sparking<00:30:01.500> debate<00:30:01.860> and<00:30:02.039> ideas<00:30:02.220> so<00:30:02.820> thanks<00:30:03.539> for 00:30:03.710 --> 00:30:03.720 align:start position:0% sparking debate and ideas so thanks for 00:30:03.720 --> 00:30:05.690 align:start position:0% sparking debate and ideas so thanks for having<00:30:03.840> me<00:30:04.080> and<00:30:04.500> thanks<00:30:04.679> Tim<00:30:04.919> for<00:30:05.220> organizing 00:30:05.690 --> 00:30:05.700 align:start position:0% having me and thanks Tim for organizing 00:30:05.700 --> 00:30:07.909 align:start position:0% having me and thanks Tim for organizing this<00:30:05.880> as<00:30:06.120> well<00:30:06.299> and<00:30:06.779> it 00:30:07.909 --> 00:30:07.919 align:start position:0% this as well and it 00:30:07.919 --> 00:30:10.690 align:start position:0% this as well and it so<00:30:08.460> today<00:30:08.580> I<00:30:08.820> wanted<00:30:08.880> to<00:30:09.059> talk<00:30:09.240> about<00:30:09.419> uh 00:30:10.690 --> 00:30:10.700 align:start position:0% so today I wanted to talk about uh 00:30:10.700 --> 00:30:14.450 align:start position:0% so today I wanted to talk about uh eip4973<00:30:12.080> Badges<00:30:13.080> and<00:30:13.380> the<00:30:13.620> financializing 00:30:14.450 --> 00:30:14.460 align:start position:0% eip4973 Badges and the financializing 00:30:14.460 --> 00:30:18.169 align:start position:0% eip4973 Badges and the financializing towers<00:30:15.000> and<00:30:15.659> Beyond<00:30:15.960> as<00:30:16.260> well<00:30:16.580> uh<00:30:17.580> so<00:30:17.880> firstly 00:30:18.169 --> 00:30:18.179 align:start position:0% towers and Beyond as well uh so firstly 00:30:18.179 --> 00:30:19.909 align:start position:0% towers and Beyond as well uh so firstly a<00:30:18.360> little<00:30:18.419> bit<00:30:18.600> about<00:30:18.720> me<00:30:18.960> my<00:30:19.320> name<00:30:19.440> is<00:30:19.500> Rahul 00:30:19.909 --> 00:30:19.919 align:start position:0% a little bit about me my name is Rahul 00:30:19.919 --> 00:30:22.610 align:start position:0% a little bit about me my name is Rahul I'm<00:30:20.159> co-founder<00:30:20.820> of<00:30:21.240> this<00:30:21.840> little<00:30:22.020> baby 00:30:22.610 --> 00:30:22.620 align:start position:0% I'm co-founder of this little baby 00:30:22.620 --> 00:30:25.389 align:start position:0% I'm co-founder of this little baby company<00:30:23.399> that<00:30:23.820> we<00:30:23.940> started<00:30:24.240> called<00:30:24.419> autospace 00:30:25.389 --> 00:30:25.399 align:start position:0% company that we started called autospace 00:30:25.399 --> 00:30:29.510 align:start position:0% company that we started called autospace uh<00:30:26.399> and<00:30:27.120> I've<00:30:27.600> been<00:30:27.779> in<00:30:27.960> the<00:30:28.200> crypto<00:30:29.039> ecosystem 00:30:29.510 --> 00:30:29.520 align:start position:0% uh and I've been in the crypto ecosystem 00:30:29.520 --> 00:30:32.510 align:start position:0% uh and I've been in the crypto ecosystem since<00:30:29.880> 2016.<00:30:30.779> I<00:30:31.080> started<00:30:31.380> off<00:30:31.500> with<00:30:31.860> my 00:30:32.510 --> 00:30:32.520 align:start position:0% since 2016. I started off with my 00:30:32.520 --> 00:30:34.750 align:start position:0% since 2016. I started off with my journey<00:30:32.700> also<00:30:33.000> with<00:30:33.120> music<00:30:33.440> I<00:30:34.440> was<00:30:34.559> building 00:30:34.750 --> 00:30:34.760 align:start position:0% journey also with music I was building 00:30:34.760 --> 00:30:37.970 align:start position:0% journey also with music I was building nfts<00:30:35.760> to<00:30:35.940> assetize<00:30:36.659> music<00:30:36.899> royalties<00:30:37.500> back<00:30:37.799> in 00:30:37.970 --> 00:30:37.980 align:start position:0% nfts to assetize music royalties back in 00:30:37.980 --> 00:30:41.630 align:start position:0% nfts to assetize music royalties back in 2017<00:30:38.460> did<00:30:39.240> not<00:30:39.419> work<00:30:39.860> uh<00:30:40.860> they<00:30:41.100> moved<00:30:41.399> on<00:30:41.520> to 00:30:41.630 --> 00:30:41.640 align:start position:0% 2017 did not work uh they moved on to 00:30:41.640 --> 00:30:44.450 align:start position:0% 2017 did not work uh they moved on to SoundCloud<00:30:42.059> got<00:30:42.720> fomo<00:30:43.140> with<00:30:43.320> those<00:30:43.500> and<00:30:44.220> I<00:30:44.340> got 00:30:44.450 --> 00:30:44.460 align:start position:0% SoundCloud got fomo with those and I got 00:30:44.460 --> 00:30:47.029 align:start position:0% SoundCloud got fomo with those and I got back<00:30:44.640> to<00:30:44.820> crypto<00:30:45.360> full<00:30:45.779> time<00:30:46.020> now 00:30:47.029 --> 00:30:47.039 align:start position:0% back to crypto full time now 00:30:47.039 --> 00:30:50.750 align:start position:0% back to crypto full time now uh<00:30:48.080> so<00:30:49.080> I<00:30:49.500> think<00:30:49.620> I<00:30:49.860> want<00:30:49.919> to<00:30:50.039> start<00:30:50.159> with<00:30:50.520> uh 00:30:50.750 --> 00:30:50.760 align:start position:0% uh so I think I want to start with uh 00:30:50.760 --> 00:30:52.850 align:start position:0% uh so I think I want to start with uh how<00:30:51.120> this<00:30:51.240> year<00:30:51.419> had<00:30:51.779> started<00:30:52.080> actually<00:30:52.380> like 00:30:52.850 --> 00:30:52.860 align:start position:0% how this year had started actually like 00:30:52.860 --> 00:30:55.010 align:start position:0% how this year had started actually like uh<00:30:53.340> we<00:30:53.940> think<00:30:54.179> that<00:30:54.360> there's<00:30:54.600> this<00:30:54.779> paper 00:30:55.010 --> 00:30:55.020 align:start position:0% uh we think that there's this paper 00:30:55.020 --> 00:30:57.889 align:start position:0% uh we think that there's this paper called<00:30:55.260> decentralized<00:30:55.919> Society<00:30:56.480> uh<00:30:57.480> and<00:30:57.779> it 00:30:57.889 --> 00:30:57.899 align:start position:0% called decentralized Society uh and it 00:30:57.899 --> 00:30:59.570 align:start position:0% called decentralized Society uh and it centered<00:30:58.260> our<00:30:58.440> attention<00:30:58.740> on<00:30:59.039> this<00:30:59.220> notion 00:30:59.570 --> 00:30:59.580 align:start position:0% centered our attention on this notion 00:30:59.580 --> 00:31:02.269 align:start position:0% centered our attention on this notion that<00:30:59.940> web3<00:31:00.419> centers<00:31:00.840> around<00:31:01.279> expressing 00:31:02.269 --> 00:31:02.279 align:start position:0% that web3 centers around expressing 00:31:02.279 --> 00:31:04.190 align:start position:0% that web3 centers around expressing transferable<00:31:03.000> Financial<00:31:03.299> assets<00:31:03.840> rather 00:31:04.190 --> 00:31:04.200 align:start position:0% transferable Financial assets rather 00:31:04.200 --> 00:31:06.529 align:start position:0% transferable Financial assets rather than<00:31:04.320> encoding<00:31:05.039> social<00:31:05.419> relationships<00:31:06.419> of 00:31:06.529 --> 00:31:06.539 align:start position:0% than encoding social relationships of 00:31:06.539 --> 00:31:09.130 align:start position:0% than encoding social relationships of trust<00:31:07.320> uh<00:31:07.860> when<00:31:08.039> everything<00:31:08.159> is<00:31:08.520> transferable 00:31:09.130 --> 00:31:09.140 align:start position:0% trust uh when everything is transferable 00:31:09.140 --> 00:31:12.230 align:start position:0% trust uh when everything is transferable things<00:31:10.140> can<00:31:10.380> be<00:31:10.559> sold<00:31:11.279> to<00:31:11.460> the<00:31:11.640> highest<00:31:11.880> bidder 00:31:12.230 --> 00:31:12.240 align:start position:0% things can be sold to the highest bidder 00:31:12.240 --> 00:31:14.510 align:start position:0% things can be sold to the highest bidder so<00:31:12.720> you<00:31:13.260> know<00:31:13.320> we<00:31:13.559> wanted<00:31:13.740> to<00:31:13.980> challenge<00:31:14.100> that 00:31:14.510 --> 00:31:14.520 align:start position:0% so you know we wanted to challenge that 00:31:14.520 --> 00:31:17.630 align:start position:0% so you know we wanted to challenge that uh<00:31:15.179> and<00:31:15.899> that's<00:31:16.380> that's<00:31:16.679> what<00:31:17.039> that<00:31:17.399> problem 00:31:17.630 --> 00:31:17.640 align:start position:0% uh and that's that's what that problem 00:31:17.640 --> 00:31:20.269 align:start position:0% uh and that's that's what that problem is<00:31:17.940> what<00:31:18.179> gave<00:31:18.360> to<00:31:18.600> this<00:31:18.779> idea<00:31:19.080> and<00:31:20.039> working 00:31:20.269 --> 00:31:20.279 align:start position:0% is what gave to this idea and working 00:31:20.279 --> 00:31:23.690 align:start position:0% is what gave to this idea and working with<00:31:20.580> Tim<00:31:20.760> on<00:31:21.059> this<00:31:21.240> EIP<00:31:21.860> uh<00:31:22.860> what<00:31:23.279> we<00:31:23.520> call 00:31:23.690 --> 00:31:23.700 align:start position:0% with Tim on this EIP uh what we call 00:31:23.700 --> 00:31:27.169 align:start position:0% with Tim on this EIP uh what we call account<00:31:24.600> bound<00:31:25.020> tokens<00:31:25.520> not<00:31:26.520> to<00:31:26.640> be<00:31:26.820> confused 00:31:27.169 --> 00:31:27.179 align:start position:0% account bound tokens not to be confused 00:31:27.179 --> 00:31:30.830 align:start position:0% account bound tokens not to be confused with<00:31:27.419> sold<00:31:27.600> down<00:31:27.840> tokens<00:31:28.320> or<00:31:28.860> you<00:31:29.220> may<00:31:29.460> be<00:31:29.840> but 00:31:30.830 --> 00:31:30.840 align:start position:0% with sold down tokens or you may be but 00:31:30.840 --> 00:31:34.669 align:start position:0% with sold down tokens or you may be but semantically<00:31:31.679> speaking<00:31:32.159> we<00:31:32.640> kind<00:31:32.880> of<00:31:33.059> uh<00:31:33.899> you 00:31:34.669 --> 00:31:34.679 align:start position:0% semantically speaking we kind of uh you 00:31:34.679 --> 00:31:36.169 align:start position:0% semantically speaking we kind of uh you can<00:31:34.860> Define<00:31:34.919> this<00:31:35.220> as<00:31:35.399> non-transferable 00:31:36.169 --> 00:31:36.179 align:start position:0% can Define this as non-transferable 00:31:36.179 --> 00:31:39.830 align:start position:0% can Define this as non-transferable tokens<00:31:36.659> bound<00:31:37.440> to<00:31:37.559> an<00:31:37.799> account<00:31:38.419> and<00:31:39.419> then<00:31:39.539> our 00:31:39.830 --> 00:31:39.840 align:start position:0% tokens bound to an account and then our 00:31:39.840 --> 00:31:41.990 align:start position:0% tokens bound to an account and then our goal<00:31:40.140> here<00:31:40.260> was<00:31:40.559> to<00:31:40.740> really 00:31:41.990 --> 00:31:42.000 align:start position:0% goal here was to really 00:31:42.000 --> 00:31:44.750 align:start position:0% goal here was to really it's<00:31:42.480> very<00:31:42.779> semantic<00:31:43.380> based<00:31:43.740> again<00:31:43.860> like<00:31:44.340> to 00:31:44.750 --> 00:31:44.760 align:start position:0% it's very semantic based again like to 00:31:44.760 --> 00:31:47.090 align:start position:0% it's very semantic based again like to create<00:31:45.120> special<00:31:45.419> ownership<00:31:45.779> Deeds<00:31:46.320> or 00:31:47.090 --> 00:31:47.100 align:start position:0% create special ownership Deeds or 00:31:47.100 --> 00:31:49.130 align:start position:0% create special ownership Deeds or creating<00:31:47.460> like<00:31:47.700> permission<00:31:48.000> Primitives<00:31:48.539> but 00:31:49.130 --> 00:31:49.140 align:start position:0% creating like permission Primitives but 00:31:49.140 --> 00:31:50.389 align:start position:0% creating like permission Primitives but really<00:31:49.320> to<00:31:49.620> create<00:31:49.740> a<00:31:49.919> new<00:31:50.100> ownership 00:31:50.389 --> 00:31:50.399 align:start position:0% really to create a new ownership 00:31:50.399 --> 00:31:52.610 align:start position:0% really to create a new ownership experience<00:31:51.000> through<00:31:51.600> this<00:31:51.840> primitive<00:31:52.200> you 00:31:52.610 --> 00:31:52.620 align:start position:0% experience through this primitive you 00:31:52.620 --> 00:31:54.889 align:start position:0% experience through this primitive you can<00:31:52.679> read<00:31:52.860> more<00:31:53.100> about<00:31:53.279> this<00:31:53.640> uh<00:31:54.240> we<00:31:54.720> have 00:31:54.889 --> 00:31:54.899 align:start position:0% can read more about this uh we have 00:31:54.899 --> 00:31:58.909 align:start position:0% can read more about this uh we have written<00:31:55.559> a<00:31:55.679> more<00:31:55.919> extensive<00:31:56.539> uh<00:31:57.740> article<00:31:58.740> on 00:31:58.909 --> 00:31:58.919 align:start position:0% written a more extensive uh article on 00:31:58.919 --> 00:31:59.750 align:start position:0% written a more extensive uh article on this 00:31:59.750 --> 00:31:59.760 align:start position:0% this 00:31:59.760 --> 00:32:02.570 align:start position:0% this uh<00:32:00.299> however<00:32:00.659> ever<00:32:01.320> since<00:32:01.559> we<00:32:01.740> started<00:32:02.039> we<00:32:02.340> saw 00:32:02.570 --> 00:32:02.580 align:start position:0% uh however ever since we started we saw 00:32:02.580 --> 00:32:06.110 align:start position:0% uh however ever since we started we saw we<00:32:03.059> noticed<00:32:03.419> this<00:32:03.840> account<00:32:04.559> on<00:32:04.919> tokens<00:32:05.460> uh 00:32:06.110 --> 00:32:06.120 align:start position:0% we noticed this account on tokens uh 00:32:06.120 --> 00:32:08.510 align:start position:0% we noticed this account on tokens uh debate<00:32:06.539> had<00:32:06.840> kind<00:32:07.080> of<00:32:07.200> like<00:32:07.320> exploded<00:32:08.220> you 00:32:08.510 --> 00:32:08.520 align:start position:0% debate had kind of like exploded you 00:32:08.520 --> 00:32:09.950 align:start position:0% debate had kind of like exploded you know<00:32:08.580> there's<00:32:08.760> soul-bound<00:32:09.240> tokens<00:32:09.600> there<00:32:09.779> was 00:32:09.950 --> 00:32:09.960 align:start position:0% know there's soul-bound tokens there was 00:32:09.960 --> 00:32:12.049 align:start position:0% know there's soul-bound tokens there was Community<00:32:10.200> about<00:32:10.500> tokens<00:32:10.980> ens<00:32:11.520> name<00:32:11.760> bound 00:32:12.049 --> 00:32:12.059 align:start position:0% Community about tokens ens name bound 00:32:12.059 --> 00:32:15.230 align:start position:0% Community about tokens ens name bound tokens<00:32:12.480> now<00:32:13.020> human<00:32:13.320> bound<00:32:13.620> tokens<00:32:14.100> uh<00:32:15.000> what 00:32:15.230 --> 00:32:15.240 align:start position:0% tokens now human bound tokens uh what 00:32:15.240 --> 00:32:16.909 align:start position:0% tokens now human bound tokens uh what we're<00:32:15.360> actually<00:32:15.600> seeing<00:32:16.020> is<00:32:16.380> this 00:32:16.909 --> 00:32:16.919 align:start position:0% we're actually seeing is this 00:32:16.919 --> 00:32:19.010 align:start position:0% we're actually seeing is this non-transferable<00:32:17.760> tokens<00:32:18.240> is<00:32:18.480> a<00:32:18.659> spectrum 00:32:19.010 --> 00:32:19.020 align:start position:0% non-transferable tokens is a spectrum 00:32:19.020 --> 00:32:21.830 align:start position:0% non-transferable tokens is a spectrum and<00:32:19.620> you<00:32:20.340> you<00:32:20.520> can<00:32:20.760> Define<00:32:20.880> what<00:32:21.360> is<00:32:21.539> being 00:32:21.830 --> 00:32:21.840 align:start position:0% and you you can Define what is being 00:32:21.840 --> 00:32:23.570 align:start position:0% and you you can Define what is being bound<00:32:22.140> to<00:32:22.380> and<00:32:22.799> what<00:32:22.919> is<00:32:23.039> that<00:32:23.159> binding 00:32:23.570 --> 00:32:23.580 align:start position:0% bound to and what is that binding 00:32:23.580 --> 00:32:26.269 align:start position:0% bound to and what is that binding strategy<00:32:24.059> and<00:32:24.720> you<00:32:24.899> can<00:32:25.020> kind<00:32:25.200> of<00:32:25.380> uh<00:32:25.980> this<00:32:26.220> is 00:32:26.269 --> 00:32:26.279 align:start position:0% strategy and you can kind of uh this is 00:32:26.279 --> 00:32:28.310 align:start position:0% strategy and you can kind of uh this is this<00:32:26.520> is<00:32:26.580> where<00:32:26.760> the<00:32:26.880> explosion<00:32:27.299> of<00:32:27.419> ideas<00:32:27.659> are 00:32:28.310 --> 00:32:28.320 align:start position:0% this is where the explosion of ideas are 00:32:28.320 --> 00:32:30.590 align:start position:0% this is where the explosion of ideas are coming<00:32:28.500> and<00:32:28.860> as<00:32:28.980> a<00:32:29.100> builder<00:32:29.399> I<00:32:30.120> feel<00:32:30.240> like<00:32:30.360> some 00:32:30.590 --> 00:32:30.600 align:start position:0% coming and as a builder I feel like some 00:32:30.600 --> 00:32:34.130 align:start position:0% coming and as a builder I feel like some of<00:32:30.720> the<00:32:30.840> nfts<00:32:31.880> nft<00:32:32.880> spec<00:32:33.419> is<00:32:33.779> kind<00:32:33.960> of<00:32:34.020> over 00:32:34.130 --> 00:32:34.140 align:start position:0% of the nfts nft spec is kind of over 00:32:34.140 --> 00:32:35.870 align:start position:0% of the nfts nft spec is kind of over optimized<00:32:34.740> for<00:32:34.860> what<00:32:35.100> we<00:32:35.279> actually<00:32:35.460> express 00:32:35.870 --> 00:32:35.880 align:start position:0% optimized for what we actually express 00:32:35.880 --> 00:32:37.970 align:start position:0% optimized for what we actually express our<00:32:36.179> ideas<00:32:36.360> through<00:32:36.840> so<00:32:37.320> we're<00:32:37.500> kind<00:32:37.740> of<00:32:37.799> like 00:32:37.970 --> 00:32:37.980 align:start position:0% our ideas through so we're kind of like 00:32:37.980 --> 00:32:41.510 align:start position:0% our ideas through so we're kind of like craving<00:32:38.760> for<00:32:38.940> new<00:32:39.179> tools<00:32:39.539> and<00:32:39.840> new<00:32:40.260> uh<00:32:41.039> new 00:32:41.510 --> 00:32:41.520 align:start position:0% craving for new tools and new uh new 00:32:41.520 --> 00:32:43.909 align:start position:0% craving for new tools and new uh new instruments<00:32:41.880> to<00:32:42.059> kind<00:32:42.240> of<00:32:42.299> like<00:32:42.480> uh<00:32:42.960> build<00:32:43.679> our 00:32:43.909 --> 00:32:43.919 align:start position:0% instruments to kind of like uh build our 00:32:43.919 --> 00:32:48.169 align:start position:0% instruments to kind of like uh build our ideas<00:32:44.100> right<00:32:44.720> and<00:32:45.720> at<00:32:46.260> Auto<00:32:46.440> space<00:32:46.799> we<00:32:47.340> we<00:32:47.880> call 00:32:48.169 --> 00:32:48.179 align:start position:0% ideas right and at Auto space we we call 00:32:48.179 --> 00:32:50.269 align:start position:0% ideas right and at Auto space we we call something<00:32:48.600> smaller<00:32:49.320> something<00:32:49.679> simpler<00:32:50.100> we 00:32:50.269 --> 00:32:50.279 align:start position:0% something smaller something simpler we 00:32:50.279 --> 00:32:53.169 align:start position:0% something smaller something simpler we call<00:32:50.399> them<00:32:50.580> badges<00:32:51.200> which<00:32:52.200> is<00:32:52.380> powered<00:32:52.679> by 00:32:53.169 --> 00:32:53.179 align:start position:0% call them badges which is powered by 00:32:53.179 --> 00:32:57.529 align:start position:0% call them badges which is powered by eip4973<00:32:54.179> accountable<00:32:54.960> tokens 00:32:57.529 --> 00:32:57.539 align:start position:0% 00:32:57.539 --> 00:33:00.169 align:start position:0% so<00:32:58.320> uh<00:32:58.679> I<00:32:58.919> want<00:32:59.039> to<00:32:59.159> dive<00:32:59.279> right<00:32:59.460> into<00:32:59.700> it<00:32:59.940> like 00:33:00.169 --> 00:33:00.179 align:start position:0% so uh I want to dive right into it like 00:33:00.179 --> 00:33:02.570 align:start position:0% so uh I want to dive right into it like because<00:33:00.419> because<00:33:00.860> ever<00:33:01.860> since<00:33:02.100> Soul<00:33:02.340> bound 00:33:02.570 --> 00:33:02.580 align:start position:0% because because ever since Soul bound 00:33:02.580 --> 00:33:04.490 align:start position:0% because because ever since Soul bound tokens<00:33:03.000> was<00:33:03.360> kind<00:33:03.539> of<00:33:03.659> like<00:33:03.779> really<00:33:04.140> a<00:33:04.380> Hot 00:33:04.490 --> 00:33:04.500 align:start position:0% tokens was kind of like really a Hot 00:33:04.500 --> 00:33:07.850 align:start position:0% tokens was kind of like really a Hot Topic<00:33:04.860> it<00:33:05.159> kind<00:33:05.279> of<00:33:05.419> sparked<00:33:06.419> like<00:33:06.779> a<00:33:07.440> lot<00:33:07.679> of 00:33:07.850 --> 00:33:07.860 align:start position:0% Topic it kind of sparked like a lot of 00:33:07.860 --> 00:33:10.730 align:start position:0% Topic it kind of sparked like a lot of hot<00:33:08.399> debates<00:33:08.880> or<00:33:09.299> uh<00:33:09.659> and<00:33:09.840> it's<00:33:10.020> it's<00:33:10.200> debates 00:33:10.730 --> 00:33:10.740 align:start position:0% hot debates or uh and it's it's debates 00:33:10.740 --> 00:33:13.130 align:start position:0% hot debates or uh and it's it's debates are<00:33:10.919> great<00:33:11.100> like<00:33:11.399> because<00:33:11.659> uh<00:33:12.659> it<00:33:12.960> really 00:33:13.130 --> 00:33:13.140 align:start position:0% are great like because uh it really 00:33:13.140 --> 00:33:15.350 align:start position:0% are great like because uh it really helped<00:33:13.860> us<00:33:13.980> intellectually<00:33:14.640> navigate<00:33:14.940> the 00:33:15.350 --> 00:33:15.360 align:start position:0% helped us intellectually navigate the 00:33:15.360 --> 00:33:17.690 align:start position:0% helped us intellectually navigate the space<00:33:15.600> and<00:33:15.960> like<00:33:16.140> get<00:33:16.500> like<00:33:16.799> a<00:33:16.980> pluralistic 00:33:17.690 --> 00:33:17.700 align:start position:0% space and like get like a pluralistic 00:33:17.700 --> 00:33:21.230 align:start position:0% space and like get like a pluralistic opinion<00:33:18.240> uh<00:33:19.080> from<00:33:19.320> various<00:33:19.679> uh<00:33:19.919> parties<00:33:20.399> uh 00:33:21.230 --> 00:33:21.240 align:start position:0% opinion uh from various uh parties uh 00:33:21.240 --> 00:33:23.690 align:start position:0% opinion uh from various uh parties uh one<00:33:21.419> of<00:33:21.539> the<00:33:21.600> first<00:33:21.720> things<00:33:22.019> uh<00:33:22.559> or<00:33:23.039> concerns 00:33:23.690 --> 00:33:23.700 align:start position:0% one of the first things uh or concerns 00:33:23.700 --> 00:33:25.610 align:start position:0% one of the first things uh or concerns they<00:33:23.880> put<00:33:24.059> out<00:33:24.179> like<00:33:24.419> I<00:33:24.659> think<00:33:24.960> was<00:33:25.080> permanence 00:33:25.610 --> 00:33:25.620 align:start position:0% they put out like I think was permanence 00:33:25.620 --> 00:33:28.130 align:start position:0% they put out like I think was permanence you<00:33:25.799> know<00:33:25.919> what<00:33:26.519> if<00:33:26.700> I<00:33:26.880> don't<00:33:27.000> want<00:33:27.299> a<00:33:27.720> sold<00:33:27.899> out 00:33:28.130 --> 00:33:28.140 align:start position:0% you know what if I don't want a sold out 00:33:28.140 --> 00:33:29.930 align:start position:0% you know what if I don't want a sold out token<00:33:28.559> or<00:33:28.679> an<00:33:28.799> account<00:33:28.919> token<00:33:29.640> you<00:33:29.880> know 00:33:29.930 --> 00:33:29.940 align:start position:0% token or an account token you know 00:33:29.940 --> 00:33:30.710 align:start position:0% token or an account token you know anymore 00:33:30.710 --> 00:33:30.720 align:start position:0% anymore 00:33:30.720 --> 00:33:32.509 align:start position:0% anymore and<00:33:31.200> the<00:33:31.320> second<00:33:31.440> one<00:33:31.620> is<00:33:31.740> a<00:33:31.860> lack<00:33:32.039> of<00:33:32.159> consent 00:33:32.509 --> 00:33:32.519 align:start position:0% and the second one is a lack of consent 00:33:32.519 --> 00:33:35.750 align:start position:0% and the second one is a lack of consent what<00:33:32.760> if<00:33:32.940> I<00:33:33.120> get<00:33:33.440> an<00:33:34.440> nft<00:33:34.980> like<00:33:35.580> that's 00:33:35.750 --> 00:33:35.760 align:start position:0% what if I get an nft like that's 00:33:35.760 --> 00:33:37.909 align:start position:0% what if I get an nft like that's non-transferable<00:33:36.600> airdrop<00:33:37.140> to<00:33:37.320> be<00:33:37.440> with<00:33:37.620> my 00:33:37.909 --> 00:33:37.919 align:start position:0% non-transferable airdrop to be with my 00:33:37.919 --> 00:33:40.310 align:start position:0% non-transferable airdrop to be with my uh<00:33:38.460> personal<00:33:38.700> details<00:33:39.299> you<00:33:39.539> know<00:33:39.659> what<00:33:40.080> would 00:33:40.310 --> 00:33:40.320 align:start position:0% uh personal details you know what would 00:33:40.320 --> 00:33:42.649 align:start position:0% uh personal details you know what would happen<00:33:40.740> you<00:33:41.100> know<00:33:41.220> and<00:33:41.760> key<00:33:41.940> rotation<00:33:42.360> you 00:33:42.649 --> 00:33:42.659 align:start position:0% happen you know and key rotation you 00:33:42.659 --> 00:33:44.690 align:start position:0% happen you know and key rotation you know<00:33:42.779> like<00:33:43.019> I<00:33:43.500> I<00:33:43.679> what<00:33:43.919> if<00:33:44.039> I<00:33:44.159> lose<00:33:44.279> access<00:33:44.460> to 00:33:44.690 --> 00:33:44.700 align:start position:0% know like I I what if I lose access to 00:33:44.700 --> 00:33:47.090 align:start position:0% know like I I what if I lose access to my<00:33:44.880> key<00:33:45.000> wallet<00:33:45.419> yeah<00:33:45.720> I<00:33:46.260> want<00:33:46.380> to<00:33:46.500> like<00:33:46.799> I<00:33:46.980> mean 00:33:47.090 --> 00:33:47.100 align:start position:0% my key wallet yeah I want to like I mean 00:33:47.100 --> 00:33:48.529 align:start position:0% my key wallet yeah I want to like I mean uh<00:33:47.279> to<00:33:47.580> my<00:33:47.700> wallet<00:33:47.880> or<00:33:48.000> do<00:33:48.120> I<00:33:48.240> want<00:33:48.360> to<00:33:48.419> change 00:33:48.529 --> 00:33:48.539 align:start position:0% uh to my wallet or do I want to change 00:33:48.539 --> 00:33:51.350 align:start position:0% uh to my wallet or do I want to change my<00:33:48.779> wallet<00:33:49.080> and<00:33:49.620> lastly<00:33:50.039> this<00:33:50.880> more<00:33:51.120> popular 00:33:51.350 --> 00:33:51.360 align:start position:0% my wallet and lastly this more popular 00:33:51.360 --> 00:33:53.990 align:start position:0% my wallet and lastly this more popular active<00:33:51.960> debate<00:33:52.320> about<00:33:52.559> like<00:33:52.919> uh<00:33:53.460> verifiable 00:33:53.990 --> 00:33:54.000 align:start position:0% active debate about like uh verifiable 00:33:54.000 --> 00:33:56.029 align:start position:0% active debate about like uh verifiable credentials<00:33:54.539> and<00:33:54.720> abts<00:33:55.380> on<00:33:55.559> Chain<00:33:55.799> versus 00:33:56.029 --> 00:33:56.039 align:start position:0% credentials and abts on Chain versus 00:33:56.039 --> 00:33:59.470 align:start position:0% credentials and abts on Chain versus off-chain<00:33:56.760> identity<00:33:57.659> uh<00:33:58.620> so<00:33:58.799> lots<00:33:59.220> of<00:33:59.279> things 00:33:59.470 --> 00:33:59.480 align:start position:0% off-chain identity uh so lots of things 00:33:59.480 --> 00:34:03.590 align:start position:0% off-chain identity uh so lots of things uh<00:34:00.480> very<00:34:00.779> simply<00:34:01.080> put<00:34:01.320> uh<00:34:02.279> there<00:34:03.179> we've 00:34:03.590 --> 00:34:03.600 align:start position:0% uh very simply put uh there we've 00:34:03.600 --> 00:34:06.889 align:start position:0% uh very simply put uh there we've written<00:34:03.779> again<00:34:04.220> lots<00:34:05.220> of<00:34:05.340> uh<00:34:05.760> detail<00:34:06.539> on<00:34:06.720> this 00:34:06.889 --> 00:34:06.899 align:start position:0% written again lots of uh detail on this 00:34:06.899 --> 00:34:09.409 align:start position:0% written again lots of uh detail on this but<00:34:07.260> I<00:34:07.679> can<00:34:07.799> kind<00:34:07.919> of<00:34:08.040> summarize<00:34:08.460> this<00:34:08.760> uh 00:34:09.409 --> 00:34:09.419 align:start position:0% but I can kind of summarize this uh 00:34:09.419 --> 00:34:10.730 align:start position:0% but I can kind of summarize this uh these<00:34:09.720> were<00:34:09.780> the<00:34:09.960> design<00:34:10.080> decisions<00:34:10.500> that 00:34:10.730 --> 00:34:10.740 align:start position:0% these were the design decisions that 00:34:10.740 --> 00:34:14.389 align:start position:0% these were the design decisions that helped<00:34:11.040> us<00:34:11.359> input<00:34:12.359> into<00:34:12.859> erp4973<00:34:13.859> so 00:34:14.389 --> 00:34:14.399 align:start position:0% helped us input into erp4973 so 00:34:14.399 --> 00:34:16.790 align:start position:0% helped us input into erp4973 so permanence<00:34:14.879> when<00:34:15.179> we<00:34:15.359> talk<00:34:15.480> about<00:34:15.659> uh<00:34:16.500> in 00:34:16.790 --> 00:34:16.800 align:start position:0% permanence when we talk about uh in 00:34:16.800 --> 00:34:18.950 align:start position:0% permanence when we talk about uh in general<00:34:16.919> what<00:34:17.639> we<00:34:17.760> baked<00:34:18.060> into<00:34:18.179> it<00:34:18.419> is<00:34:18.659> uh 00:34:18.950 --> 00:34:18.960 align:start position:0% general what we baked into it is uh 00:34:18.960 --> 00:34:22.129 align:start position:0% general what we baked into it is uh burning<00:34:19.379> and<00:34:19.980> dissociation<00:34:20.639> from<00:34:21.060> the<00:34:21.240> so<00:34:21.599> the 00:34:22.129 --> 00:34:22.139 align:start position:0% burning and dissociation from the so the 00:34:22.139 --> 00:34:23.510 align:start position:0% burning and dissociation from the so the owner<00:34:22.320> of<00:34:22.440> the<00:34:22.560> Soul<00:34:22.679> bomb<00:34:22.919> token<00:34:23.280> or<00:34:23.399> account 00:34:23.510 --> 00:34:23.520 align:start position:0% owner of the Soul bomb token or account 00:34:23.520 --> 00:34:26.210 align:start position:0% owner of the Soul bomb token or account bomb<00:34:23.879> token<00:34:24.119> can<00:34:24.300> dissociate<00:34:24.780> from<00:34:25.139> uh<00:34:25.500> from 00:34:26.210 --> 00:34:26.220 align:start position:0% bomb token can dissociate from uh from 00:34:26.220 --> 00:34:27.589 align:start position:0% bomb token can dissociate from uh from the<00:34:26.339> token<00:34:26.639> itself<00:34:26.879> and<00:34:27.119> then<00:34:27.240> lack<00:34:27.480> of 00:34:27.589 --> 00:34:27.599 align:start position:0% the token itself and then lack of 00:34:27.599 --> 00:34:30.609 align:start position:0% the token itself and then lack of consent<00:34:28.020> uh 00:34:30.609 --> 00:34:30.619 align:start position:0% consent uh 00:34:30.619 --> 00:34:32.690 align:start position:0% consent uh non-transferable<00:34:31.619> tokens<00:34:32.040> through<00:34:32.280> organ 00:34:32.690 --> 00:34:32.700 align:start position:0% non-transferable tokens through organ 00:34:32.700 --> 00:34:35.089 align:start position:0% non-transferable tokens through organ tokens<00:34:33.480> cannot<00:34:33.839> be<00:34:33.960> air<00:34:34.139> dropped<00:34:34.560> you<00:34:34.800> need<00:34:34.980> to 00:34:35.089 --> 00:34:35.099 align:start position:0% tokens cannot be air dropped you need to 00:34:35.099 --> 00:34:37.190 align:start position:0% tokens cannot be air dropped you need to have<00:34:35.339> a<00:34:35.639> two-way<00:34:36.000> consent<00:34:36.419> which<00:34:36.599> I<00:34:36.780> will<00:34:36.960> dive 00:34:37.190 --> 00:34:37.200 align:start position:0% have a two-way consent which I will dive 00:34:37.200 --> 00:34:40.070 align:start position:0% have a two-way consent which I will dive into<00:34:37.440> a<00:34:38.159> little<00:34:38.339> bit<00:34:38.520> later<00:34:38.760> and<00:34:39.659> with<00:34:39.960> other 00:34:40.070 --> 00:34:40.080 align:start position:0% into a little bit later and with other 00:34:40.080 --> 00:34:41.470 align:start position:0% into a little bit later and with other space<00:34:40.379> we're<00:34:40.619> actually 00:34:41.470 --> 00:34:41.480 align:start position:0% space we're actually 00:34:41.480 --> 00:34:44.030 align:start position:0% space we're actually actively<00:34:42.480> looking<00:34:42.720> into<00:34:43.040> recovery 00:34:44.030 --> 00:34:44.040 align:start position:0% actively looking into recovery 00:34:44.040 --> 00:34:45.710 align:start position:0% actively looking into recovery mechanisms<00:34:44.460> like<00:34:44.639> Community<00:34:44.879> Based<00:34:45.359> recovery 00:34:45.710 --> 00:34:45.720 align:start position:0% mechanisms like Community Based recovery 00:34:45.720 --> 00:34:47.810 align:start position:0% mechanisms like Community Based recovery especially<00:34:46.440> if<00:34:46.619> you<00:34:46.740> lose<00:34:46.919> access<00:34:47.220> and<00:34:47.639> you 00:34:47.810 --> 00:34:47.820 align:start position:0% especially if you lose access and you 00:34:47.820 --> 00:34:49.669 align:start position:0% especially if you lose access and you have<00:34:47.940> all<00:34:48.119> these<00:34:48.419> non-transferable<00:34:49.260> tokens 00:34:49.669 --> 00:34:49.679 align:start position:0% have all these non-transferable tokens 00:34:49.679 --> 00:34:52.909 align:start position:0% have all these non-transferable tokens uh<00:34:50.460> and<00:34:50.700> lastly<00:34:51.080> avts<00:34:52.080> versus<00:34:52.260> verifiable 00:34:52.909 --> 00:34:52.919 align:start position:0% uh and lastly avts versus verifiable 00:34:52.919 --> 00:34:54.530 align:start position:0% uh and lastly avts versus verifiable credentials 00:34:54.530 --> 00:34:54.540 align:start position:0% credentials 00:34:54.540 --> 00:34:56.510 align:start position:0% credentials use<00:34:54.960> both<00:34:55.260> really<00:34:55.740> it's<00:34:55.980> not<00:34:56.159> mutually 00:34:56.510 --> 00:34:56.520 align:start position:0% use both really it's not mutually 00:34:56.520 --> 00:34:59.570 align:start position:0% use both really it's not mutually exclusive<00:34:57.060> uh<00:34:57.960> they<00:34:58.260> have<00:34:58.440> like<00:34:58.740> good<00:34:59.400> use 00:34:59.570 --> 00:34:59.580 align:start position:0% exclusive uh they have like good use 00:34:59.580 --> 00:35:02.390 align:start position:0% exclusive uh they have like good use cases<00:35:00.000> and<00:35:00.480> it's<00:35:00.900> really<00:35:01.080> we're<00:35:01.440> in<00:35:01.740> the<00:35:01.920> early 00:35:02.390 --> 00:35:02.400 align:start position:0% cases and it's really we're in the early 00:35:02.400 --> 00:35:04.250 align:start position:0% cases and it's really we're in the early stages<00:35:02.700> of<00:35:03.119> kind<00:35:03.420> of<00:35:03.540> like<00:35:03.599> the<00:35:03.780> debate<00:35:04.080> and 00:35:04.250 --> 00:35:04.260 align:start position:0% stages of kind of like the debate and 00:35:04.260 --> 00:35:06.290 align:start position:0% stages of kind of like the debate and application<00:35:04.800> so<00:35:05.160> I'm<00:35:05.580> kind<00:35:05.700> of<00:35:05.820> excited<00:35:06.060> of 00:35:06.290 --> 00:35:06.300 align:start position:0% application so I'm kind of excited of 00:35:06.300 --> 00:35:08.030 align:start position:0% application so I'm kind of excited of what<00:35:06.720> would<00:35:06.960> actually<00:35:07.140> come<00:35:07.560> out<00:35:07.740> of<00:35:07.859> this 00:35:08.030 --> 00:35:08.040 align:start position:0% what would actually come out of this 00:35:08.040 --> 00:35:09.650 align:start position:0% what would actually come out of this next<00:35:08.580> year 00:35:09.650 --> 00:35:09.660 align:start position:0% next year 00:35:09.660 --> 00:35:13.250 align:start position:0% next year uh<00:35:10.440> so<00:35:10.680> like<00:35:10.980> on<00:35:11.400> a<00:35:11.579> very<00:35:11.700> high<00:35:11.940> level<00:35:12.119> like<00:35:12.780> I'm 00:35:13.250 --> 00:35:13.260 align:start position:0% uh so like on a very high level like I'm 00:35:13.260 --> 00:35:14.990 align:start position:0% uh so like on a very high level like I'm oversimplifying<00:35:13.980> this<00:35:14.160> but<00:35:14.400> like<00:35:14.579> you<00:35:14.820> can 00:35:14.990 --> 00:35:15.000 align:start position:0% oversimplifying this but like you can 00:35:15.000 --> 00:35:16.609 align:start position:0% oversimplifying this but like you can see<00:35:15.119> the<00:35:15.240> key<00:35:15.420> differences<00:35:15.780> like<00:35:16.140> if<00:35:16.380> you<00:35:16.500> look 00:35:16.609 --> 00:35:16.619 align:start position:0% see the key differences like if you look 00:35:16.619 --> 00:35:19.430 align:start position:0% see the key differences like if you look at<00:35:16.740> like<00:35:16.980> various<00:35:17.400> uh<00:35:17.880> angles<00:35:18.540> or<00:35:18.839> various<00:35:19.200> uh 00:35:19.430 --> 00:35:19.440 align:start position:0% at like various uh angles or various uh 00:35:19.440 --> 00:35:20.810 align:start position:0% at like various uh angles or various uh Dimensions<00:35:19.980> right<00:35:20.160> if<00:35:20.400> you<00:35:20.520> look<00:35:20.700> at 00:35:20.810 --> 00:35:20.820 align:start position:0% Dimensions right if you look at 00:35:20.820 --> 00:35:23.650 align:start position:0% Dimensions right if you look at transferability<00:35:21.420> consent<00:35:22.200> removal<00:35:22.920> issuance 00:35:23.650 --> 00:35:23.660 align:start position:0% transferability consent removal issuance 00:35:23.660 --> 00:35:26.329 align:start position:0% transferability consent removal issuance expiration<00:35:24.660> and<00:35:24.839> fungibility<00:35:25.380> but<00:35:26.040> I<00:35:26.220> think 00:35:26.329 --> 00:35:26.339 align:start position:0% expiration and fungibility but I think 00:35:26.339 --> 00:35:28.910 align:start position:0% expiration and fungibility but I think uh<00:35:26.820> I<00:35:27.240> want<00:35:27.359> to<00:35:27.599> bring<00:35:28.079> Focus<00:35:28.440> to<00:35:28.680> where 00:35:28.910 --> 00:35:28.920 align:start position:0% uh I want to bring Focus to where 00:35:28.920 --> 00:35:31.250 align:start position:0% uh I want to bring Focus to where consent<00:35:29.760> and<00:35:29.940> issuance<00:35:30.359> uh<00:35:30.839> that's<00:35:31.079> that's 00:35:31.250 --> 00:35:31.260 align:start position:0% consent and issuance uh that's that's 00:35:31.260 --> 00:35:33.710 align:start position:0% consent and issuance uh that's that's really<00:35:31.619> what<00:35:32.339> we<00:35:32.460> wanted<00:35:32.640> to<00:35:32.880> like<00:35:33.119> did<00:35:33.540> not 00:35:33.710 --> 00:35:33.720 align:start position:0% really what we wanted to like did not 00:35:33.720 --> 00:35:35.990 align:start position:0% really what we wanted to like did not want<00:35:33.900> to<00:35:34.079> compromise<00:35:34.560> on<00:35:34.800> there<00:35:35.220> when<00:35:35.760> it<00:35:35.880> came 00:35:35.990 --> 00:35:36.000 align:start position:0% want to compromise on there when it came 00:35:36.000 --> 00:35:39.589 align:start position:0% want to compromise on there when it came to<00:35:36.180> a<00:35:36.900> non-transferable<00:35:37.619> token<00:35:38.099> design 00:35:39.589 --> 00:35:39.599 align:start position:0% to a non-transferable token design 00:35:39.599 --> 00:35:42.050 align:start position:0% to a non-transferable token design so<00:35:40.140> let's<00:35:40.380> Dive<00:35:40.680> Right<00:35:40.920> In<00:35:41.220> like<00:35:41.520> so<00:35:41.820> this<00:35:42.000> is 00:35:42.050 --> 00:35:42.060 align:start position:0% so let's Dive Right In like so this is 00:35:42.060 --> 00:35:45.650 align:start position:0% so let's Dive Right In like so this is the<00:35:42.619> erc4973<00:35:43.619> at<00:35:44.280> a<00:35:44.400> glance<00:35:44.640> you<00:35:44.880> could<00:35:45.000> just 00:35:45.650 --> 00:35:45.660 align:start position:0% the erc4973 at a glance you could just 00:35:45.660 --> 00:35:49.490 align:start position:0% the erc4973 at a glance you could just npm<00:35:46.560> install<00:35:46.740> that<00:35:47.160> very<00:35:47.760> easy<00:35:48.079> so<00:35:49.079> that's<00:35:49.260> a 00:35:49.490 --> 00:35:49.500 align:start position:0% npm install that very easy so that's a 00:35:49.500 --> 00:35:52.730 align:start position:0% npm install that very easy so that's a very<00:35:49.680> uh<00:35:50.280> very<00:35:50.880> light<00:35:51.180> interface<00:35:52.140> right<00:35:52.440> like 00:35:52.730 --> 00:35:52.740 align:start position:0% very uh very light interface right like 00:35:52.740 --> 00:35:54.589 align:start position:0% very uh very light interface right like it's<00:35:53.040> just<00:35:53.280> expresses<00:35:53.940> so<00:35:54.119> we<00:35:54.240> can<00:35:54.359> kind<00:35:54.480> of 00:35:54.589 --> 00:35:54.599 align:start position:0% it's just expresses so we can kind of 00:35:54.599 --> 00:35:57.410 align:start position:0% it's just expresses so we can kind of like<00:35:54.780> dive<00:35:55.500> into<00:35:55.680> what<00:35:56.339> this<00:35:56.640> uh<00:35:56.880> actually 00:35:57.410 --> 00:35:57.420 align:start position:0% like dive into what this uh actually 00:35:57.420 --> 00:36:00.470 align:start position:0% like dive into what this uh actually does<00:35:57.720> so<00:35:58.619> firstly<00:35:58.980> this<00:35:59.640> top<00:35:59.820> section<00:36:00.240> right 00:36:00.470 --> 00:36:00.480 align:start position:0% does so firstly this top section right 00:36:00.480 --> 00:36:02.750 align:start position:0% does so firstly this top section right this<00:36:00.839> transfer<00:36:01.380> event<00:36:01.560> balance<00:36:02.099> off<00:36:02.280> on<00:36:02.640> or 00:36:02.750 --> 00:36:02.760 align:start position:0% this transfer event balance off on or 00:36:02.760 --> 00:36:05.390 align:start position:0% this transfer event balance off on or off<00:36:02.940> this<00:36:03.780> is<00:36:03.900> this<00:36:04.140> was<00:36:04.380> mainly<00:36:04.800> to<00:36:05.099> ensure 00:36:05.390 --> 00:36:05.400 align:start position:0% off this is this was mainly to ensure 00:36:05.400 --> 00:36:07.010 align:start position:0% off this is this was mainly to ensure backward<00:36:05.820> compatibility<00:36:06.359> backward 00:36:07.010 --> 00:36:07.020 align:start position:0% backward compatibility backward 00:36:07.020 --> 00:36:09.470 align:start position:0% backward compatibility backward compatibility<00:36:07.500> to<00:36:07.800> nft<00:36:08.160> in<00:36:08.880> general<00:36:09.060> so<00:36:09.300> we 00:36:09.470 --> 00:36:09.480 align:start position:0% compatibility to nft in general so we 00:36:09.480 --> 00:36:12.589 align:start position:0% compatibility to nft in general so we actually<00:36:09.660> implement<00:36:10.079> the<00:36:10.260> ierc<00:36:11.180> 721<00:36:12.180> mm 00:36:12.589 --> 00:36:12.599 align:start position:0% actually implement the ierc 721 mm 00:36:12.599 --> 00:36:15.050 align:start position:0% actually implement the ierc 721 mm metadata<00:36:13.140> uh<00:36:14.040> so<00:36:14.460> one<00:36:14.579> of<00:36:14.700> the<00:36:14.760> things<00:36:14.820> that 00:36:15.050 --> 00:36:15.060 align:start position:0% metadata uh so one of the things that 00:36:15.060 --> 00:36:17.750 align:start position:0% metadata uh so one of the things that building<00:36:15.780> this<00:36:15.960> EIP<00:36:16.260> actually<00:36:16.560> it<00:36:17.339> was<00:36:17.520> super 00:36:17.750 --> 00:36:17.760 align:start position:0% building this EIP actually it was super 00:36:17.760 --> 00:36:20.390 align:start position:0% building this EIP actually it was super amazing<00:36:18.540> learning<00:36:18.900> experience<00:36:19.320> uh<00:36:20.160> we 00:36:20.390 --> 00:36:20.400 align:start position:0% amazing learning experience uh we 00:36:20.400 --> 00:36:21.710 align:start position:0% amazing learning experience uh we actually<00:36:20.520> didn't<00:36:20.760> have<00:36:20.940> the<00:36:21.119> transport<00:36:21.480> event 00:36:21.710 --> 00:36:21.720 align:start position:0% actually didn't have the transport event 00:36:21.720 --> 00:36:23.750 align:start position:0% actually didn't have the transport event first<00:36:22.079> and<00:36:22.440> then<00:36:22.619> we<00:36:22.859> were<00:36:23.040> kind<00:36:23.280> of<00:36:23.339> missing 00:36:23.750 --> 00:36:23.760 align:start position:0% first and then we were kind of missing 00:36:23.760 --> 00:36:26.510 align:start position:0% first and then we were kind of missing all<00:36:24.540> these<00:36:24.839> stuff<00:36:25.320> like<00:36:25.500> etherscan<00:36:26.220> was<00:36:26.339> not 00:36:26.510 --> 00:36:26.520 align:start position:0% all these stuff like etherscan was not 00:36:26.520 --> 00:36:28.250 align:start position:0% all these stuff like etherscan was not showing<00:36:26.820> the<00:36:27.000> log<00:36:27.119> events<00:36:27.660> for<00:36:27.780> example<00:36:28.020> or 00:36:28.250 --> 00:36:28.260 align:start position:0% showing the log events for example or 00:36:28.260 --> 00:36:31.130 align:start position:0% showing the log events for example or metamask<00:36:28.680> was<00:36:28.920> not<00:36:29.160> showing<00:36:29.460> the<00:36:30.119> uh<00:36:30.300> the<00:36:31.079> the 00:36:31.130 --> 00:36:31.140 align:start position:0% metamask was not showing the uh the the 00:36:31.140 --> 00:36:33.470 align:start position:0% metamask was not showing the uh the the interesting<00:36:31.800> metadata<00:36:32.280> so<00:36:32.700> we<00:36:32.820> we<00:36:33.000> actually 00:36:33.470 --> 00:36:33.480 align:start position:0% interesting metadata so we we actually 00:36:33.480 --> 00:36:34.910 align:start position:0% interesting metadata so we we actually started<00:36:33.780> using<00:36:34.020> the<00:36:34.140> transfer<00:36:34.560> event<00:36:34.680> which 00:36:34.910 --> 00:36:34.920 align:start position:0% started using the transfer event which 00:36:34.920 --> 00:36:36.589 align:start position:0% started using the transfer event which is<00:36:35.040> such<00:36:35.220> a<00:36:35.339> simple<00:36:35.460> change<00:36:35.760> everything 00:36:36.589 --> 00:36:36.599 align:start position:0% is such a simple change everything 00:36:36.599 --> 00:36:38.690 align:start position:0% is such a simple change everything started<00:36:37.140> working<00:36:37.260> automatically<00:36:38.160> you<00:36:38.640> know 00:36:38.690 --> 00:36:38.700 align:start position:0% started working automatically you know 00:36:38.700 --> 00:36:40.970 align:start position:0% started working automatically you know like<00:36:38.940> uh<00:36:39.359> the<00:36:39.900> support<00:36:40.020> the<00:36:40.380> interoperability 00:36:40.970 --> 00:36:40.980 align:start position:0% like uh the support the interoperability 00:36:40.980 --> 00:36:43.490 align:start position:0% like uh the support the interoperability actually<00:36:41.520> came<00:36:41.880> came<00:36:42.480> for<00:36:42.720> free<00:36:42.900> and<00:36:43.140> that's 00:36:43.490 --> 00:36:43.500 align:start position:0% actually came came for free and that's 00:36:43.500 --> 00:36:45.230 align:start position:0% actually came came for free and that's one<00:36:43.680> of<00:36:43.800> the<00:36:43.859> reasons<00:36:44.099> we<00:36:44.339> went<00:36:44.940> back<00:36:45.060> to<00:36:45.180> the 00:36:45.230 --> 00:36:45.240 align:start position:0% one of the reasons we went back to the 00:36:45.240 --> 00:36:47.150 align:start position:0% one of the reasons we went back to the transfer<00:36:45.599> that<00:36:46.140> although<00:36:46.619> in<00:36:46.980> a 00:36:47.150 --> 00:36:47.160 align:start position:0% transfer that although in a 00:36:47.160 --> 00:36:49.270 align:start position:0% transfer that although in a non-transferable<00:36:47.760> event 00:36:49.270 --> 00:36:49.280 align:start position:0% non-transferable event 00:36:49.280 --> 00:36:52.310 align:start position:0% non-transferable event token<00:36:50.280> you<00:36:50.700> can<00:36:50.820> argue<00:36:51.180> that<00:36:51.420> transfer<00:36:51.900> has<00:36:52.140> no 00:36:52.310 --> 00:36:52.320 align:start position:0% token you can argue that transfer has no 00:36:52.320 --> 00:36:55.010 align:start position:0% token you can argue that transfer has no makes<00:36:52.920> no<00:36:53.160> sense<00:36:53.339> but<00:36:54.000> this<00:36:54.540> was<00:36:54.660> one<00:36:54.839> of<00:36:54.960> the 00:36:55.010 --> 00:36:55.020 align:start position:0% makes no sense but this was one of the 00:36:55.020 --> 00:36:56.750 align:start position:0% makes no sense but this was one of the design<00:36:55.140> decisions<00:36:55.680> that<00:36:55.920> we<00:36:56.040> learned<00:36:56.339> like<00:36:56.520> to 00:36:56.750 --> 00:36:56.760 align:start position:0% design decisions that we learned like to 00:36:56.760 --> 00:36:58.970 align:start position:0% design decisions that we learned like to kind<00:36:56.940> of<00:36:57.060> Ensure<00:36:57.359> backward<00:36:57.720> compatibility 00:36:58.970 --> 00:36:58.980 align:start position:0% kind of Ensure backward compatibility 00:36:58.980 --> 00:37:01.730 align:start position:0% kind of Ensure backward compatibility uh<00:36:59.640> and<00:36:59.760> the<00:36:59.940> next<00:37:00.060> one<00:37:00.300> and<00:37:01.260> this<00:37:01.440> is<00:37:01.560> really 00:37:01.730 --> 00:37:01.740 align:start position:0% uh and the next one and this is really 00:37:01.740 --> 00:37:03.650 align:start position:0% uh and the next one and this is really the<00:37:01.980> where<00:37:02.220> the<00:37:02.400> consent<00:37:02.820> really<00:37:03.180> comes<00:37:03.540> into 00:37:03.650 --> 00:37:03.660 align:start position:0% the where the consent really comes into 00:37:03.660 --> 00:37:04.790 align:start position:0% the where the consent really comes into play 00:37:04.790 --> 00:37:04.800 align:start position:0% play 00:37:04.800 --> 00:37:07.069 align:start position:0% play so<00:37:05.160> if<00:37:05.280> you<00:37:05.400> see<00:37:05.520> the<00:37:05.700> function<00:37:06.000> there's<00:37:06.839> like 00:37:07.069 --> 00:37:07.079 align:start position:0% so if you see the function there's like 00:37:07.079 --> 00:37:09.230 align:start position:0% so if you see the function there's like three<00:37:07.440> three<00:37:07.920> parameters<00:37:08.460> right<00:37:08.700> like<00:37:08.940> the 00:37:09.230 --> 00:37:09.240 align:start position:0% three three parameters right like the 00:37:09.240 --> 00:37:12.109 align:start position:0% three three parameters right like the from<00:37:09.480> the<00:37:09.900> URI<00:37:10.380> and<00:37:10.859> the<00:37:11.040> signature 00:37:12.109 --> 00:37:12.119 align:start position:0% from the URI and the signature 00:37:12.119 --> 00:37:15.290 align:start position:0% from the URI and the signature so<00:37:12.540> we<00:37:12.660> call<00:37:12.839> this<00:37:13.020> a<00:37:13.140> take<00:37:13.320> flow<00:37:13.820> so<00:37:14.820> you 00:37:15.290 --> 00:37:15.300 align:start position:0% so we call this a take flow so you 00:37:15.300 --> 00:37:17.990 align:start position:0% so we call this a take flow so you cannot<00:37:15.599> actually<00:37:15.839> mint<00:37:16.740> an<00:37:17.400> account<00:37:17.640> bound 00:37:17.990 --> 00:37:18.000 align:start position:0% cannot actually mint an account bound 00:37:18.000 --> 00:37:20.030 align:start position:0% cannot actually mint an account bound token<00:37:18.359> unless<00:37:18.660> it's<00:37:18.960> two<00:37:19.320> parties<00:37:19.680> involved 00:37:20.030 --> 00:37:20.040 align:start position:0% token unless it's two parties involved 00:37:20.040 --> 00:37:21.470 align:start position:0% token unless it's two parties involved so<00:37:20.160> it's<00:37:20.280> like<00:37:20.400> a<00:37:20.520> peer-to-peer<00:37:21.180> fully 00:37:21.470 --> 00:37:21.480 align:start position:0% so it's like a peer-to-peer fully 00:37:21.480 --> 00:37:24.290 align:start position:0% so it's like a peer-to-peer fully mutually<00:37:21.839> consented<00:37:22.440> protocol<00:37:23.040> right<00:37:23.400> so<00:37:24.180> you 00:37:24.290 --> 00:37:24.300 align:start position:0% mutually consented protocol right so you 00:37:24.300 --> 00:37:25.910 align:start position:0% mutually consented protocol right so you can<00:37:24.420> think<00:37:24.540> about<00:37:24.720> this<00:37:24.960> as<00:37:25.140> like<00:37:25.260> okay<00:37:25.440> Alice 00:37:25.910 --> 00:37:25.920 align:start position:0% can think about this as like okay Alice 00:37:25.920 --> 00:37:28.790 align:start position:0% can think about this as like okay Alice designs<00:37:26.700> and<00:37:26.820> ABT<00:37:27.359> described<00:37:28.260> by<00:37:28.440> a<00:37:28.619> spec 00:37:28.790 --> 00:37:28.800 align:start position:0% designs and ABT described by a spec 00:37:28.800 --> 00:37:32.270 align:start position:0% designs and ABT described by a spec which<00:37:29.220> is<00:37:29.400> hosted<00:37:30.060> by<00:37:30.359> a<00:37:30.480> token<00:37:30.720> URI<00:37:31.560> Alice 00:37:32.270 --> 00:37:32.280 align:start position:0% which is hosted by a token URI Alice 00:37:32.280 --> 00:37:34.550 align:start position:0% which is hosted by a token URI Alice then<00:37:32.460> wants<00:37:32.760> to<00:37:32.820> issue<00:37:33.060> the<00:37:33.180> ABC<00:37:33.540> to<00:37:33.720> Bob 00:37:34.550 --> 00:37:34.560 align:start position:0% then wants to issue the ABC to Bob 00:37:34.560 --> 00:37:37.190 align:start position:0% then wants to issue the ABC to Bob uh<00:37:35.220> Alice<00:37:35.520> can<00:37:35.700> only<00:37:35.820> do<00:37:36.000> that<00:37:36.180> if<00:37:36.540> this<00:37:36.839> if<00:37:37.140> if 00:37:37.190 --> 00:37:37.200 align:start position:0% uh Alice can only do that if this if if 00:37:37.200 --> 00:37:40.010 align:start position:0% uh Alice can only do that if this if if he<00:37:37.619> signs<00:37:38.040> using<00:37:38.460> aip712<00:37:39.420> signature<00:37:39.839> and 00:37:40.010 --> 00:37:40.020 align:start position:0% he signs using aip712 signature and 00:37:40.020 --> 00:37:42.650 align:start position:0% he signs using aip712 signature and provide<00:37:40.380> that's<00:37:40.740> capturing<00:37:41.520> her<00:37:41.700> consent 00:37:42.650 --> 00:37:42.660 align:start position:0% provide that's capturing her consent 00:37:42.660 --> 00:37:44.630 align:start position:0% provide that's capturing her consent so<00:37:43.140> now<00:37:43.260> that<00:37:43.619> one<00:37:43.800> party<00:37:43.980> consent<00:37:44.460> is 00:37:44.630 --> 00:37:44.640 align:start position:0% so now that one party consent is 00:37:44.640 --> 00:37:47.450 align:start position:0% so now that one party consent is established<00:37:45.060> Bob<00:37:45.359> can<00:37:45.660> now<00:37:45.839> take<00:37:46.079> the<00:37:46.500> SBT<00:37:47.040> he 00:37:47.450 --> 00:37:47.460 align:start position:0% established Bob can now take the SBT he 00:37:47.460 --> 00:37:49.670 align:start position:0% established Bob can now take the SBT he would<00:37:47.880> then<00:37:48.060> basically<00:37:48.420> authenticate<00:37:49.380> by 00:37:49.670 --> 00:37:49.680 align:start position:0% would then basically authenticate by 00:37:49.680 --> 00:37:51.890 align:start position:0% would then basically authenticate by providing<00:37:50.099> the<00:37:50.400> circuit<00:37:50.880> URI<00:37:51.180> the<00:37:51.480> signature 00:37:51.890 --> 00:37:51.900 align:start position:0% providing the circuit URI the signature 00:37:51.900 --> 00:37:54.650 align:start position:0% providing the circuit URI the signature from<00:37:52.440> Alice<00:37:52.800> and<00:37:53.040> then<00:37:53.220> prove<00:37:53.640> that<00:37:53.940> I<00:37:54.540> can 00:37:54.650 --> 00:37:54.660 align:start position:0% from Alice and then prove that I can 00:37:54.660 --> 00:37:57.829 align:start position:0% from Alice and then prove that I can take<00:37:54.839> this<00:37:55.099> uh<00:37:56.099> so<00:37:56.400> this<00:37:56.640> is<00:37:56.820> uh<00:37:57.240> in<00:37:57.420> Auto<00:37:57.599> space 00:37:57.829 --> 00:37:57.839 align:start position:0% take this uh so this is uh in Auto space 00:37:57.839 --> 00:37:59.270 align:start position:0% take this uh so this is uh in Auto space we<00:37:58.020> actually<00:37:58.200> call<00:37:58.380> this<00:37:58.560> the<00:37:58.800> allow<00:37:59.099> list 00:37:59.270 --> 00:37:59.280 align:start position:0% we actually call this the allow list 00:37:59.280 --> 00:38:00.829 align:start position:0% we actually call this the allow list flow<00:37:59.579> so<00:37:59.700> I'm<00:37:59.760> just<00:37:59.940> like<00:38:00.000> adding<00:38:00.359> people<00:38:00.540> to 00:38:00.829 --> 00:38:00.839 align:start position:0% flow so I'm just like adding people to 00:38:00.839 --> 00:38:03.290 align:start position:0% flow so I'm just like adding people to an<00:38:00.960> allow<00:38:01.200> list<00:38:01.440> I'm<00:38:01.619> like<00:38:01.859> signing<00:38:02.280> uh<00:38:03.060> people 00:38:03.290 --> 00:38:03.300 align:start position:0% an allow list I'm like signing uh people 00:38:03.300 --> 00:38:07.370 align:start position:0% an allow list I'm like signing uh people uh<00:38:03.900> for<00:38:04.140> to<00:38:04.320> a<00:38:04.500> badge<00:38:05.180> and<00:38:06.180> the<00:38:06.599> give<00:38:06.900> flow<00:38:07.260> is 00:38:07.370 --> 00:38:07.380 align:start position:0% uh for to a badge and the give flow is 00:38:07.380 --> 00:38:10.550 align:start position:0% uh for to a badge and the give flow is actually<00:38:07.560> its<00:38:07.920> inverse<00:38:08.339> uh<00:38:09.180> it's<00:38:09.960> uh<00:38:10.140> it's 00:38:10.550 --> 00:38:10.560 align:start position:0% actually its inverse uh it's uh it's 00:38:10.560 --> 00:38:13.069 align:start position:0% actually its inverse uh it's uh it's when<00:38:10.740> the<00:38:10.980> when<00:38:11.339> Alice<00:38:11.700> designs<00:38:12.060> an<00:38:12.119> ABT<00:38:12.599> Bob 00:38:13.069 --> 00:38:13.079 align:start position:0% when the when Alice designs an ABT Bob 00:38:13.079 --> 00:38:16.490 align:start position:0% when the when Alice designs an ABT Bob wants<00:38:13.500> the<00:38:13.560> ABT<00:38:14.040> so<00:38:14.520> signs<00:38:14.940> it<00:38:15.119> and<00:38:15.660> then<00:38:15.839> Alice 00:38:16.490 --> 00:38:16.500 align:start position:0% wants the ABT so signs it and then Alice 00:38:16.500 --> 00:38:19.670 align:start position:0% wants the ABT so signs it and then Alice can<00:38:16.680> now<00:38:16.920> give<00:38:17.220> the<00:38:17.700> ABT<00:38:18.119> to<00:38:18.240> Bob<00:38:18.480> so<00:38:19.200> this<00:38:19.500> in 00:38:19.670 --> 00:38:19.680 align:start position:0% can now give the ABT to Bob so this in 00:38:19.680 --> 00:38:22.190 align:start position:0% can now give the ABT to Bob so this in order<00:38:19.800> space<00:38:20.099> we<00:38:20.339> call<00:38:20.460> it<00:38:20.640> the<00:38:21.480> airdrop<00:38:21.900> flow 00:38:22.190 --> 00:38:22.200 align:start position:0% order space we call it the airdrop flow 00:38:22.200 --> 00:38:24.650 align:start position:0% order space we call it the airdrop flow so<00:38:22.800> if<00:38:23.160> you<00:38:23.339> if<00:38:23.579> you<00:38:23.760> give<00:38:23.940> a<00:38:24.119> badge<00:38:24.420> you<00:38:24.540> can 00:38:24.650 --> 00:38:24.660 align:start position:0% so if you if you give a badge you can 00:38:24.660 --> 00:38:26.750 align:start position:0% so if you if you give a badge you can just<00:38:24.780> like<00:38:24.960> basically<00:38:25.320> I<00:38:25.800> want<00:38:26.040> this<00:38:26.280> and<00:38:26.579> 100 00:38:26.750 --> 00:38:26.760 align:start position:0% just like basically I want this and 100 00:38:26.760 --> 00:38:28.130 align:start position:0% just like basically I want this and 100 people<00:38:27.000> say<00:38:27.240> I<00:38:27.420> want<00:38:27.540> this<00:38:27.720> you<00:38:27.900> can<00:38:28.020> actually 00:38:28.130 --> 00:38:28.140 align:start position:0% people say I want this you can actually 00:38:28.140 --> 00:38:30.650 align:start position:0% people say I want this you can actually do<00:38:28.440> an<00:38:28.560> airdrop<00:38:29.040> through<00:38:29.460> uh<00:38:29.940> through<00:38:30.300> an 00:38:30.650 --> 00:38:30.660 align:start position:0% do an airdrop through uh through an 00:38:30.660 --> 00:38:32.210 align:start position:0% do an airdrop through uh through an account<00:38:30.839> token 00:38:32.210 --> 00:38:32.220 align:start position:0% account token 00:38:32.220 --> 00:38:34.910 align:start position:0% account token and<00:38:32.820> the<00:38:33.000> last<00:38:33.119> bit<00:38:33.300> is<00:38:33.660> this<00:38:33.900> one<00:38:34.020> it's<00:38:34.380> uh<00:38:34.680> the 00:38:34.910 --> 00:38:34.920 align:start position:0% and the last bit is this one it's uh the 00:38:34.920 --> 00:38:37.849 align:start position:0% and the last bit is this one it's uh the unequiv<00:38:35.400> this<00:38:36.180> basically<00:38:36.599> means<00:38:37.020> complete 00:38:37.849 --> 00:38:37.859 align:start position:0% unequiv this basically means complete 00:38:37.859 --> 00:38:39.950 align:start position:0% unequiv this basically means complete dissociation<00:38:38.400> from<00:38:38.880> the<00:38:39.180> account<00:38:39.599> bound 00:38:39.950 --> 00:38:39.960 align:start position:0% dissociation from the account bound 00:38:39.960 --> 00:38:41.750 align:start position:0% dissociation from the account bound token<00:38:40.260> so<00:38:40.380> only<00:38:40.500> the<00:38:40.740> owner<00:38:40.920> of<00:38:41.099> the<00:38:41.160> token<00:38:41.520> can 00:38:41.750 --> 00:38:41.760 align:start position:0% token so only the owner of the token can 00:38:41.760 --> 00:38:44.270 align:start position:0% token so only the owner of the token can dissociate<00:38:42.300> so<00:38:42.839> these<00:38:43.320> are<00:38:43.440> like<00:38:43.800> basically 00:38:44.270 --> 00:38:44.280 align:start position:0% dissociate so these are like basically 00:38:44.280 --> 00:38:46.550 align:start position:0% dissociate so these are like basically the<00:38:44.579> fundamental<00:38:45.240> building<00:38:45.720> blocks<00:38:46.260> that 00:38:46.550 --> 00:38:46.560 align:start position:0% the fundamental building blocks that 00:38:46.560 --> 00:38:49.790 align:start position:0% the fundamental building blocks that kind<00:38:46.800> of<00:38:46.920> like<00:38:47.040> help<00:38:47.280> this<00:38:47.720> uh<00:38:48.720> create<00:38:49.320> this 00:38:49.790 --> 00:38:49.800 align:start position:0% kind of like help this uh create this 00:38:49.800 --> 00:38:52.609 align:start position:0% kind of like help this uh create this very<00:38:50.520> bare<00:38:50.940> minimum<00:38:51.240> uh<00:38:51.839> very<00:38:52.079> simple<00:38:52.260> very 00:38:52.609 --> 00:38:52.619 align:start position:0% very bare minimum uh very simple very 00:38:52.619 --> 00:38:54.230 align:start position:0% very bare minimum uh very simple very it's<00:38:52.920> highly<00:38:53.520> functional<00:38:53.880> highly 00:38:54.230 --> 00:38:54.240 align:start position:0% it's highly functional highly 00:38:54.240 --> 00:38:58.010 align:start position:0% it's highly functional highly utilitarian<00:38:54.960> uh<00:38:55.619> EIP<00:38:56.119> 4973<00:38:57.119> and<00:38:57.300> then<00:38:57.420> Auto 00:38:58.010 --> 00:38:58.020 align:start position:0% utilitarian uh EIP 4973 and then Auto 00:38:58.020 --> 00:38:59.810 align:start position:0% utilitarian uh EIP 4973 and then Auto space<00:38:58.320> we<00:38:58.560> are<00:38:58.740> kind<00:38:58.920> of<00:38:58.980> like<00:38:59.099> uh<00:38:59.520> building 00:38:59.810 --> 00:38:59.820 align:start position:0% space we are kind of like uh building 00:38:59.820 --> 00:39:01.730 align:start position:0% space we are kind of like uh building more<00:39:00.240> flavors<00:39:00.599> or<00:39:00.839> more<00:39:01.020> layers<00:39:01.320> around<00:39:01.500> it 00:39:01.730 --> 00:39:01.740 align:start position:0% more flavors or more layers around it 00:39:01.740 --> 00:39:05.810 align:start position:0% more flavors or more layers around it but<00:39:02.040> this<00:39:02.599> all<00:39:03.599> the<00:39:03.780> what<00:39:04.740> this<00:39:04.859> had<00:39:05.099> serves<00:39:05.460> at 00:39:05.810 --> 00:39:05.820 align:start position:0% but this all the what this had serves at 00:39:05.820 --> 00:39:07.550 align:start position:0% but this all the what this had serves at the<00:39:06.000> fundamental<00:39:06.420> has<00:39:06.660> been<00:39:06.839> working<00:39:07.079> really 00:39:07.550 --> 00:39:07.560 align:start position:0% the fundamental has been working really 00:39:07.560 --> 00:39:10.390 align:start position:0% the fundamental has been working really good<00:39:07.800> for<00:39:07.980> us<00:39:08.099> so<00:39:08.400> far<00:39:08.520> and<00:39:09.480> I<00:39:09.780> also<00:39:10.020> call 00:39:10.390 --> 00:39:10.400 align:start position:0% good for us so far and I also call 00:39:10.400 --> 00:39:14.329 align:start position:0% good for us so far and I also call actively<00:39:11.400> contribute<00:39:11.880> to<00:39:12.180> the<00:39:12.540> EIP<00:39:13.040> and<00:39:14.040> uh 00:39:14.329 --> 00:39:14.339 align:start position:0% actively contribute to the EIP and uh 00:39:14.339 --> 00:39:16.190 align:start position:0% actively contribute to the EIP and uh yeah<00:39:14.640> it's<00:39:15.180> been<00:39:15.359> super<00:39:15.599> exciting<00:39:16.020> and 00:39:16.190 --> 00:39:16.200 align:start position:0% yeah it's been super exciting and 00:39:16.200 --> 00:39:17.750 align:start position:0% yeah it's been super exciting and learning<00:39:16.560> in<00:39:17.040> general 00:39:17.750 --> 00:39:17.760 align:start position:0% learning in general 00:39:17.760 --> 00:39:20.750 align:start position:0% learning in general so<00:39:18.480> moving<00:39:18.900> on<00:39:19.079> to<00:39:19.320> the<00:39:19.980> other<00:39:20.040> side<00:39:20.280> of<00:39:20.579> what 00:39:20.750 --> 00:39:20.760 align:start position:0% so moving on to the other side of what 00:39:20.760 --> 00:39:22.790 align:start position:0% so moving on to the other side of what that<00:39:21.180> the<00:39:21.300> topic<00:39:21.780> I<00:39:21.900> wanted<00:39:22.079> to<00:39:22.260> chat<00:39:22.440> about<00:39:22.560> as 00:39:22.790 --> 00:39:22.800 align:start position:0% that the topic I wanted to chat about as 00:39:22.800 --> 00:39:25.310 align:start position:0% that the topic I wanted to chat about as well<00:39:22.920> which<00:39:23.160> is<00:39:23.400> the<00:39:23.940> financialization<00:39:24.720> right 00:39:25.310 --> 00:39:25.320 align:start position:0% well which is the financialization right 00:39:25.320 --> 00:39:28.370 align:start position:0% well which is the financialization right at<00:39:25.980> outer<00:39:26.280> space<00:39:26.400> where<00:39:26.760> like<00:39:26.940> the<00:39:27.300> badges<00:39:27.660> we 00:39:28.370 --> 00:39:28.380 align:start position:0% at outer space where like the badges we 00:39:28.380 --> 00:39:30.710 align:start position:0% at outer space where like the badges we see<00:39:28.560> this<00:39:28.800> in<00:39:28.980> like<00:39:29.220> six<00:39:29.579> six<00:39:29.880> areas<00:39:30.300> how<00:39:30.540> we 00:39:30.710 --> 00:39:30.720 align:start position:0% see this in like six six areas how we 00:39:30.720 --> 00:39:33.290 align:start position:0% see this in like six six areas how we can<00:39:30.900> use<00:39:31.260> a<00:39:31.619> non-transferable<00:39:32.280> token<00:39:32.760> a 00:39:33.290 --> 00:39:33.300 align:start position:0% can use a non-transferable token a 00:39:33.300 --> 00:39:35.690 align:start position:0% can use a non-transferable token a membership<00:39:33.660> model<00:39:34.160> non-financial<00:39:35.160> rewards 00:39:35.690 --> 00:39:35.700 align:start position:0% membership model non-financial rewards 00:39:35.700 --> 00:39:38.270 align:start position:0% membership model non-financial rewards uh<00:39:36.359> and<00:39:36.480> recognition<00:39:36.960> onboarding<00:39:37.619> quests<00:39:38.040> to 00:39:38.270 --> 00:39:38.280 align:start position:0% uh and recognition onboarding quests to 00:39:38.280 --> 00:39:41.170 align:start position:0% uh and recognition onboarding quests to end<00:39:38.579> with<00:39:38.760> the<00:39:38.940> badge<00:39:39.380> assess<00:39:40.380> the<00:39:40.560> reputation 00:39:41.170 --> 00:39:41.180 align:start position:0% end with the badge assess the reputation 00:39:41.180 --> 00:39:43.910 align:start position:0% end with the badge assess the reputation uh<00:39:42.180> more<00:39:42.420> nuanced<00:39:42.839> governance<00:39:43.320> models<00:39:43.680> and 00:39:43.910 --> 00:39:43.920 align:start position:0% uh more nuanced governance models and 00:39:43.920 --> 00:39:45.950 align:start position:0% uh more nuanced governance models and then<00:39:44.040> unlock<00:39:44.280> access<00:39:44.700> permissions<00:39:45.300> of<00:39:45.780> these 00:39:45.950 --> 00:39:45.960 align:start position:0% then unlock access permissions of these 00:39:45.960 --> 00:39:47.270 align:start position:0% then unlock access permissions of these batch<00:39:46.140> holders 00:39:47.270 --> 00:39:47.280 align:start position:0% batch holders 00:39:47.280 --> 00:39:50.089 align:start position:0% batch holders but<00:39:48.000> I<00:39:48.359> want<00:39:48.480> to<00:39:48.660> bring<00:39:48.839> attention<00:39:49.260> to<00:39:49.680> this 00:39:50.089 --> 00:39:50.099 align:start position:0% but I want to bring attention to this 00:39:50.099 --> 00:39:51.890 align:start position:0% but I want to bring attention to this bit 00:39:51.890 --> 00:39:51.900 align:start position:0% bit 00:39:51.900 --> 00:39:55.910 align:start position:0% bit this<00:39:52.560> bit<00:39:52.859> of<00:39:53.339> uh<00:39:53.640> that's<00:39:54.060> non-financial<00:39:54.960> uh 00:39:55.910 --> 00:39:55.920 align:start position:0% this bit of uh that's non-financial uh 00:39:55.920 --> 00:39:57.890 align:start position:0% this bit of uh that's non-financial uh rewards<00:39:56.400> and<00:39:56.460> recognition<00:39:56.880> I<00:39:57.540> mean<00:39:57.660> I<00:39:57.780> think 00:39:57.890 --> 00:39:57.900 align:start position:0% rewards and recognition I mean I think 00:39:57.900 --> 00:40:00.230 align:start position:0% rewards and recognition I mean I think we<00:39:58.020> can<00:39:58.140> all<00:39:58.260> agree<00:39:58.560> that<00:39:58.980> uh<00:39:59.460> the<00:39:59.820> ecosystem 00:40:00.230 --> 00:40:00.240 align:start position:0% we can all agree that uh the ecosystem 00:40:00.240 --> 00:40:03.589 align:start position:0% we can all agree that uh the ecosystem is<00:40:00.900> like<00:40:01.079> hyper<00:40:01.500> financialized<00:40:02.240> uh<00:40:03.240> and<00:40:03.480> we 00:40:03.589 --> 00:40:03.599 align:start position:0% is like hyper financialized uh and we 00:40:03.599 --> 00:40:05.329 align:start position:0% is like hyper financialized uh and we want<00:40:03.780> to<00:40:03.900> challenge<00:40:04.079> that<00:40:04.380> status<00:40:04.619> quo<00:40:05.040> like 00:40:05.329 --> 00:40:05.339 align:start position:0% want to challenge that status quo like 00:40:05.339 --> 00:40:06.710 align:start position:0% want to challenge that status quo like you<00:40:05.460> know<00:40:05.579> you<00:40:05.760> if<00:40:05.940> you're<00:40:06.060> in<00:40:06.180> a<00:40:06.359> position<00:40:06.420> of 00:40:06.710 --> 00:40:06.720 align:start position:0% you know you if you're in a position of 00:40:06.720 --> 00:40:09.170 align:start position:0% you know you if you're in a position of wealth<00:40:07.020> and<00:40:07.140> influence<00:40:07.560> you<00:40:07.740> can<00:40:07.859> buy<00:40:08.180> tokens 00:40:09.170 --> 00:40:09.180 align:start position:0% wealth and influence you can buy tokens 00:40:09.180 --> 00:40:11.930 align:start position:0% wealth and influence you can buy tokens and<00:40:09.660> if<00:40:09.900> your<00:40:10.200> community<00:40:10.740> is<00:40:11.099> basically<00:40:11.640> to 00:40:11.930 --> 00:40:11.940 align:start position:0% and if your community is basically to 00:40:11.940 --> 00:40:14.270 align:start position:0% and if your community is basically to design<00:40:12.119> their<00:40:12.420> governance<00:40:13.079> on<00:40:13.320> a<00:40:13.560> one<00:40:13.920> token 00:40:14.270 --> 00:40:14.280 align:start position:0% design their governance on a one token 00:40:14.280 --> 00:40:16.849 align:start position:0% design their governance on a one token one<00:40:14.460> vote<00:40:14.700> system<00:40:14.940> so<00:40:15.720> person<00:40:16.079> of<00:40:16.380> influence 00:40:16.849 --> 00:40:16.859 align:start position:0% one vote system so person of influence 00:40:16.859 --> 00:40:18.410 align:start position:0% one vote system so person of influence can<00:40:17.099> basically<00:40:17.339> assert<00:40:17.880> their<00:40:18.060> entire 00:40:18.410 --> 00:40:18.420 align:start position:0% can basically assert their entire 00:40:18.420 --> 00:40:21.230 align:start position:0% can basically assert their entire influence<00:40:18.900> through<00:40:19.140> that<00:40:19.380> power 00:40:21.230 --> 00:40:21.240 align:start position:0% influence through that power 00:40:21.240 --> 00:40:24.650 align:start position:0% influence through that power it's<00:40:21.480> basically<00:40:21.839> plutocracy<00:40:22.619> right<00:40:23.220> so<00:40:24.060> we 00:40:24.650 --> 00:40:24.660 align:start position:0% it's basically plutocracy right so we 00:40:24.660 --> 00:40:26.450 align:start position:0% it's basically plutocracy right so we want<00:40:24.839> to<00:40:24.960> challenge<00:40:25.140> that<00:40:25.500> and<00:40:25.920> we<00:40:26.160> want<00:40:26.339> to 00:40:26.450 --> 00:40:26.460 align:start position:0% want to challenge that and we want to 00:40:26.460 --> 00:40:28.490 align:start position:0% want to challenge that and we want to move<00:40:26.700> towards<00:40:27.180> more<00:40:27.599> towards<00:40:27.960> the<00:40:28.140> one<00:40:28.320> human 00:40:28.490 --> 00:40:28.500 align:start position:0% move towards more towards the one human 00:40:28.500 --> 00:40:31.490 align:start position:0% move towards more towards the one human one<00:40:28.859> vote<00:40:29.099> but<00:40:29.940> uh<00:40:30.300> for<00:40:30.540> us<00:40:30.660> we<00:40:30.900> see<00:40:31.079> the<00:40:31.260> one 00:40:31.490 --> 00:40:31.500 align:start position:0% one vote but uh for us we see the one 00:40:31.500 --> 00:40:33.530 align:start position:0% one vote but uh for us we see the one account<00:40:31.680> one<00:40:31.920> vote<00:40:32.160> as<00:40:32.460> a<00:40:32.640> necessary<00:40:32.880> step<00:40:33.180> to 00:40:33.530 --> 00:40:33.540 align:start position:0% account one vote as a necessary step to 00:40:33.540 --> 00:40:36.589 align:start position:0% account one vote as a necessary step to kind<00:40:33.660> of<00:40:33.780> get<00:40:33.900> to<00:40:34.079> one<00:40:34.380> human<00:40:34.560> one<00:40:34.800> vote 00:40:36.589 --> 00:40:36.599 align:start position:0% kind of get to one human one vote 00:40:36.599 --> 00:40:38.810 align:start position:0% kind of get to one human one vote uh<00:40:37.140> and<00:40:37.320> then<00:40:37.380> this<00:40:37.680> is<00:40:37.859> really<00:40:38.220> Fresh<00:40:38.460> Off<00:40:38.640> The 00:40:38.810 --> 00:40:38.820 align:start position:0% uh and then this is really Fresh Off The 00:40:38.820 --> 00:40:40.130 align:start position:0% uh and then this is really Fresh Off The Grill<00:40:38.940> right<00:40:39.180> this<00:40:39.420> happened<00:40:39.599> like<00:40:39.900> a<00:40:40.020> few 00:40:40.130 --> 00:40:40.140 align:start position:0% Grill right this happened like a few 00:40:40.140 --> 00:40:43.190 align:start position:0% Grill right this happened like a few days<00:40:40.260> ago<00:40:40.619> uh<00:40:41.520> the<00:40:41.640> mango<00:40:42.000> markets<00:40:42.480> uh<00:40:43.079> the 00:40:43.190 --> 00:40:43.200 align:start position:0% days ago uh the mango markets uh the 00:40:43.200 --> 00:40:45.650 align:start position:0% days ago uh the mango markets uh the hacker<00:40:43.560> exploited<00:40:43.980> mango<00:40:44.460> for<00:40:44.640> 100<00:40:45.060> million 00:40:45.650 --> 00:40:45.660 align:start position:0% hacker exploited mango for 100 million 00:40:45.660 --> 00:40:49.130 align:start position:0% hacker exploited mango for 100 million hacker<00:40:46.380> turns<00:40:46.680> around<00:40:47.060> uh<00:40:48.060> offense<00:40:48.839> to<00:40:49.020> return 00:40:49.130 --> 00:40:49.140 align:start position:0% hacker turns around uh offense to return 00:40:49.140 --> 00:40:51.890 align:start position:0% hacker turns around uh offense to return the<00:40:49.380> funds<00:40:50.160> and<00:40:50.640> he<00:40:50.760> used<00:40:50.940> 32<00:40:51.359> million<00:40:51.720> of 00:40:51.890 --> 00:40:51.900 align:start position:0% the funds and he used 32 million of 00:40:51.900 --> 00:40:53.569 align:start position:0% the funds and he used 32 million of those<00:40:52.020> votes<00:40:52.500> to<00:40:52.740> say<00:40:52.920> yes<00:40:53.099> to<00:40:53.339> his<00:40:53.460> own 00:40:53.569 --> 00:40:53.579 align:start position:0% those votes to say yes to his own 00:40:53.579 --> 00:40:55.609 align:start position:0% those votes to say yes to his own proposal<00:40:54.060> because<00:40:54.660> he<00:40:54.960> hacked<00:40:55.260> those<00:40:55.380> and 00:40:55.609 --> 00:40:55.619 align:start position:0% proposal because he hacked those and 00:40:55.619 --> 00:40:59.329 align:start position:0% proposal because he hacked those and then<00:40:55.859> executed<00:40:56.579> that<00:40:56.760> proposal<00:40:57.240> and<00:40:58.220> I<00:40:59.220> think 00:40:59.329 --> 00:40:59.339 align:start position:0% then executed that proposal and I think 00:40:59.339 --> 00:41:01.190 align:start position:0% then executed that proposal and I think we<00:40:59.460> can<00:40:59.579> do<00:40:59.700> better<00:40:59.880> than<00:41:00.060> this<00:41:00.300> right<00:41:00.540> like<00:41:00.839> uh 00:41:01.190 --> 00:41:01.200 align:start position:0% we can do better than this right like uh 00:41:01.200 --> 00:41:03.950 align:start position:0% we can do better than this right like uh it's<00:41:01.800> a<00:41:02.040> that's<00:41:02.400> a<00:41:02.579> no-brainer<00:41:03.060> I<00:41:03.240> feel<00:41:03.359> but 00:41:03.950 --> 00:41:03.960 align:start position:0% it's a that's a no-brainer I feel but 00:41:03.960 --> 00:41:05.630 align:start position:0% it's a that's a no-brainer I feel but it's<00:41:04.140> really<00:41:04.320> the<00:41:04.560> takeaway<00:41:04.920> that<00:41:05.400> I<00:41:05.579> wanted 00:41:05.630 --> 00:41:05.640 align:start position:0% it's really the takeaway that I wanted 00:41:05.640 --> 00:41:08.930 align:start position:0% it's really the takeaway that I wanted to<00:41:05.880> kind<00:41:06.060> of<00:41:06.240> uh<00:41:07.020> here<00:41:07.200> have<00:41:07.680> here<00:41:07.920> is<00:41:08.220> uh<00:41:08.520> let's 00:41:08.930 --> 00:41:08.940 align:start position:0% to kind of uh here have here is uh let's 00:41:08.940 --> 00:41:10.849 align:start position:0% to kind of uh here have here is uh let's move<00:41:09.119> away<00:41:09.300> from<00:41:09.599> the<00:41:09.780> one<00:41:10.079> token<00:41:10.440> one<00:41:10.560> vote 00:41:10.849 --> 00:41:10.859 align:start position:0% move away from the one token one vote 00:41:10.859 --> 00:41:14.690 align:start position:0% move away from the one token one vote system<00:41:11.180> and<00:41:12.180> away<00:41:12.359> from<00:41:12.599> plutocracy<00:41:13.380> and<00:41:13.800> uh<00:41:14.160> I 00:41:14.690 --> 00:41:14.700 align:start position:0% system and away from plutocracy and uh I 00:41:14.700 --> 00:41:17.750 align:start position:0% system and away from plutocracy and uh I think<00:41:14.900> let's<00:41:15.900> let's<00:41:16.260> explore<00:41:17.040> new<00:41:17.339> forms<00:41:17.640> of 00:41:17.750 --> 00:41:17.760 align:start position:0% think let's let's explore new forms of 00:41:17.760 --> 00:41:19.130 align:start position:0% think let's let's explore new forms of governance<00:41:18.240> I<00:41:18.660> think<00:41:18.720> it<00:41:18.900> is<00:41:19.020> no 00:41:19.130 --> 00:41:19.140 align:start position:0% governance I think it is no 00:41:19.140 --> 00:41:21.710 align:start position:0% governance I think it is no one-size-fits-all<00:41:20.099> I<00:41:21.000> think<00:41:21.180> we're<00:41:21.359> in<00:41:21.540> a 00:41:21.710 --> 00:41:21.720 align:start position:0% one-size-fits-all I think we're in a 00:41:21.720 --> 00:41:23.569 align:start position:0% one-size-fits-all I think we're in a stage<00:41:21.900> where<00:41:22.079> the<00:41:22.260> ecosystem<00:41:22.680> is<00:41:22.980> growing<00:41:23.339> so 00:41:23.569 --> 00:41:23.579 align:start position:0% stage where the ecosystem is growing so 00:41:23.579 --> 00:41:26.390 align:start position:0% stage where the ecosystem is growing so so<00:41:23.880> fast<00:41:24.180> and<00:41:24.540> we<00:41:24.839> as<00:41:25.020> Builders<00:41:25.500> we<00:41:25.859> we 00:41:26.390 --> 00:41:26.400 align:start position:0% so fast and we as Builders we we 00:41:26.400 --> 00:41:28.609 align:start position:0% so fast and we as Builders we we definitely<00:41:26.760> need<00:41:27.000> more<00:41:27.300> uh<00:41:27.839> instruments<00:41:28.320> at 00:41:28.609 --> 00:41:28.619 align:start position:0% definitely need more uh instruments at 00:41:28.619 --> 00:41:31.010 align:start position:0% definitely need more uh instruments at our<00:41:28.740> toolkit<00:41:29.280> we<00:41:29.640> need<00:41:29.820> to<00:41:29.940> spark<00:41:30.240> debate<00:41:30.599> yeah 00:41:31.010 --> 00:41:31.020 align:start position:0% our toolkit we need to spark debate yeah 00:41:31.020 --> 00:41:34.609 align:start position:0% our toolkit we need to spark debate yeah apply<00:41:31.740> rigor<00:41:32.160> get<00:41:32.579> feedback<00:41:32.940> so<00:41:33.780> I'm<00:41:34.380> glad 00:41:34.609 --> 00:41:34.619 align:start position:0% apply rigor get feedback so I'm glad 00:41:34.619 --> 00:41:36.230 align:start position:0% apply rigor get feedback so I'm glad that<00:41:34.859> I'm<00:41:35.099> kind<00:41:35.220> of<00:41:35.339> like<00:41:35.400> getting<00:41:35.820> a<00:41:36.060> lot<00:41:36.119> of 00:41:36.230 --> 00:41:36.240 align:start position:0% that I'm kind of like getting a lot of 00:41:36.240 --> 00:41:40.370 align:start position:0% that I'm kind of like getting a lot of that<00:41:36.420> here<00:41:36.660> in<00:41:36.960> Devcon<00:41:37.460> so<00:41:38.599> that's<00:41:39.599> uh<00:41:39.900> that's 00:41:40.370 --> 00:41:40.380 align:start position:0% that here in Devcon so that's uh that's 00:41:40.380 --> 00:41:43.490 align:start position:0% that here in Devcon so that's uh that's a<00:41:40.500> lot<00:41:40.680> that's<00:41:41.400> it<00:41:41.640> and<00:41:42.300> that's<00:41:42.540> a<00:41:42.720> Dali<00:41:43.320> otter 00:41:43.490 --> 00:41:43.500 align:start position:0% a lot that's it and that's a Dali otter 00:41:43.500 --> 00:41:46.730 align:start position:0% a lot that's it and that's a Dali otter we<00:41:44.160> are<00:41:44.339> uh<00:41:45.240> we<00:41:45.900> don't<00:41:46.020> work<00:41:46.200> we<00:41:46.440> just<00:41:46.560> create 00:41:46.730 --> 00:41:46.740 align:start position:0% we are uh we don't work we just create 00:41:46.740 --> 00:41:49.310 align:start position:0% we are uh we don't work we just create these<00:41:47.040> Dolly<00:41:47.400> orders<00:41:47.700> most<00:41:48.060> of<00:41:48.180> the<00:41:48.300> time<00:41:48.480> if 00:41:49.310 --> 00:41:49.320 align:start position:0% these Dolly orders most of the time if 00:41:49.320 --> 00:41:51.050 align:start position:0% these Dolly orders most of the time if you're<00:41:49.619> as<00:41:49.859> surprising<00:41:50.099> my<00:41:50.700> team<00:41:50.820> is 00:41:51.050 --> 00:41:51.060 align:start position:0% you're as surprising my team is 00:41:51.060 --> 00:41:52.790 align:start position:0% you're as surprising my team is surprisingly<00:41:51.780> good<00:41:51.960> at<00:41:52.140> creating<00:41:52.500> daily 00:41:52.790 --> 00:41:52.800 align:start position:0% surprisingly good at creating daily 00:41:52.800 --> 00:41:55.849 align:start position:0% surprisingly good at creating daily orders<00:41:53.339> you<00:41:54.180> can<00:41:54.240> scan<00:41:54.540> this<00:41:54.780> it'll<00:41:55.619> give<00:41:55.740> you 00:41:55.849 --> 00:41:55.859 align:start position:0% orders you can scan this it'll give you 00:41:55.859 --> 00:41:58.670 align:start position:0% orders you can scan this it'll give you more<00:41:56.040> information<00:41:56.220> about<00:41:56.640> us<00:41:57.180> uh<00:41:57.780> yeah<00:41:58.200> that's 00:41:58.670 --> 00:41:58.680 align:start position:0% more information about us uh yeah that's 00:41:58.680 --> 00:42:02.569 align:start position:0% more information about us uh yeah that's that's<00:41:58.920> it 00:42:02.569 --> 00:42:02.579 align:start position:0% 00:42:02.579 --> 00:42:06.230 align:start position:0% thank<00:42:03.240> you<00:42:03.359> thank<00:42:03.960> you<00:42:04.140> Raul 00:42:06.230 --> 00:42:06.240 align:start position:0% thank you thank you Raul 00:42:06.240 --> 00:42:08.810 align:start position:0% thank you thank you Raul um<00:42:06.359> we<00:42:06.780> have<00:42:06.960> some<00:42:07.440> time<00:42:07.980> left<00:42:08.220> three<00:42:08.579> minutes 00:42:08.810 --> 00:42:08.820 align:start position:0% um we have some time left three minutes 00:42:08.820 --> 00:42:13.190 align:start position:0% um we have some time left three minutes do<00:42:09.480> we<00:42:09.660> have<00:42:09.720> questions<00:42:09.900> ah<00:42:10.440> yes<00:42:10.619> okay 00:42:13.190 --> 00:42:13.200 align:start position:0% 00:42:13.200 --> 00:42:14.390 align:start position:0% hey 00:42:14.390 --> 00:42:14.400 align:start position:0% hey 00:42:14.400 --> 00:42:16.069 align:start position:0% hey um can<00:42:14.820> you<00:42:14.940> elaborate<00:42:15.359> a<00:42:15.540> bit<00:42:15.660> on<00:42:15.900> the 00:42:16.069 --> 00:42:16.079 align:start position:0% um can you elaborate a bit on the 00:42:16.079 --> 00:42:20.210 align:start position:0% um can you elaborate a bit on the account<00:42:16.460> through<00:42:17.460> the<00:42:17.700> recovery<00:42:18.480> part 00:42:20.210 --> 00:42:20.220 align:start position:0% account through the recovery part 00:42:20.220 --> 00:42:23.089 align:start position:0% account through the recovery part yeah<00:42:20.820> absolutely<00:42:21.180> so<00:42:22.140> um 00:42:23.089 --> 00:42:23.099 align:start position:0% yeah absolutely so um 00:42:23.099 --> 00:42:24.829 align:start position:0% yeah absolutely so um so<00:42:23.640> one<00:42:23.880> of<00:42:24.180> the<00:42:24.300> things<00:42:24.420> with<00:42:24.660> account 00:42:24.829 --> 00:42:24.839 align:start position:0% so one of the things with account 00:42:24.839 --> 00:42:27.230 align:start position:0% so one of the things with account recovery<00:42:25.500> uh<00:42:25.920> it<00:42:26.460> actually<00:42:26.520> came<00:42:26.820> up<00:42:27.000> pretty 00:42:27.230 --> 00:42:27.240 align:start position:0% recovery uh it actually came up pretty 00:42:27.240 --> 00:42:29.630 align:start position:0% recovery uh it actually came up pretty actively<00:42:27.960> in<00:42:28.200> the<00:42:28.320> debate<00:42:28.560> like<00:42:28.859> hey<00:42:29.339> if<00:42:29.520> I 00:42:29.630 --> 00:42:29.640 align:start position:0% actively in the debate like hey if I 00:42:29.640 --> 00:42:31.370 align:start position:0% actively in the debate like hey if I have<00:42:29.760> badges<00:42:30.119> in<00:42:30.300> my<00:42:30.420> account<00:42:30.599> if<00:42:31.020> you<00:42:31.200> have 00:42:31.370 --> 00:42:31.380 align:start position:0% have badges in my account if you have 00:42:31.380 --> 00:42:34.550 align:start position:0% have badges in my account if you have non-transport<00:42:32.099> like<00:42:32.400> tokens<00:42:33.240> what<00:42:34.079> if<00:42:34.260> I<00:42:34.380> want 00:42:34.550 --> 00:42:34.560 align:start position:0% non-transport like tokens what if I want 00:42:34.560 --> 00:42:36.109 align:start position:0% non-transport like tokens what if I want to<00:42:34.619> rotate<00:42:34.920> my<00:42:35.160> keys 00:42:36.109 --> 00:42:36.119 align:start position:0% to rotate my keys 00:42:36.119 --> 00:42:39.170 align:start position:0% to rotate my keys uh<00:42:36.960> then<00:42:37.380> how<00:42:37.619> do<00:42:37.740> I<00:42:37.859> do<00:42:38.040> this<00:42:38.160> and<00:42:38.520> that's<00:42:38.940> one 00:42:39.170 --> 00:42:39.180 align:start position:0% uh then how do I do this and that's one 00:42:39.180 --> 00:42:40.550 align:start position:0% uh then how do I do this and that's one of<00:42:39.300> the<00:42:39.359> criticisms<00:42:39.839> that<00:42:40.020> were<00:42:40.140> pointed<00:42:40.440> at 00:42:40.550 --> 00:42:40.560 align:start position:0% of the criticisms that were pointed at 00:42:40.560 --> 00:42:42.890 align:start position:0% of the criticisms that were pointed at sold<00:42:40.740> down<00:42:40.920> tokensen<00:42:41.460> initially<00:42:41.820> uh<00:42:42.660> quite 00:42:42.890 --> 00:42:42.900 align:start position:0% sold down tokensen initially uh quite 00:42:42.900 --> 00:42:45.589 align:start position:0% sold down tokensen initially uh quite frankly<00:42:43.200> I<00:42:43.440> feel<00:42:43.560> this<00:42:43.920> is<00:42:44.099> a<00:42:44.460> this<00:42:45.180> is<00:42:45.300> not<00:42:45.420> a 00:42:45.589 --> 00:42:45.599 align:start position:0% frankly I feel this is a this is not a 00:42:45.599 --> 00:42:47.569 align:start position:0% frankly I feel this is a this is not a soul<00:42:45.720> bound<00:42:46.020> problem<00:42:46.320> or<00:42:46.740> a<00:42:46.859> soul<00:42:46.980> bound<00:42:47.220> token 00:42:47.569 --> 00:42:47.579 align:start position:0% soul bound problem or a soul bound token 00:42:47.579 --> 00:42:49.870 align:start position:0% soul bound problem or a soul bound token problem<00:42:47.700> this<00:42:48.000> is<00:42:48.180> a<00:42:48.420> entire<00:42:49.380> protocol 00:42:49.870 --> 00:42:49.880 align:start position:0% problem this is a entire protocol 00:42:49.880 --> 00:42:52.250 align:start position:0% problem this is a entire protocol ethereum<00:42:50.880> problem<00:42:51.060> and<00:42:51.359> I<00:42:51.599> feel<00:42:51.780> like<00:42:51.900> we<00:42:52.140> need 00:42:52.250 --> 00:42:52.260 align:start position:0% ethereum problem and I feel like we need 00:42:52.260 --> 00:42:53.870 align:start position:0% ethereum problem and I feel like we need to<00:42:52.380> wait<00:42:52.560> until<00:42:52.800> we<00:42:53.220> need<00:42:53.280> to<00:42:53.400> do<00:42:53.520> this<00:42:53.700> better 00:42:53.870 --> 00:42:53.880 align:start position:0% to wait until we need to do this better 00:42:53.880 --> 00:42:56.810 align:start position:0% to wait until we need to do this better and<00:42:54.180> then<00:42:54.300> we<00:42:54.540> can<00:42:54.660> absolutely<00:42:55.440> adopt<00:42:55.920> it<00:42:56.040> but 00:42:56.810 --> 00:42:56.820 align:start position:0% and then we can absolutely adopt it but 00:42:56.820 --> 00:42:58.849 align:start position:0% and then we can absolutely adopt it but we<00:42:57.180> are<00:42:57.300> looking<00:42:57.420> at<00:42:57.660> two<00:42:57.839> ways<00:42:58.200> of<00:42:58.319> recovery 00:42:58.849 --> 00:42:58.859 align:start position:0% we are looking at two ways of recovery 00:42:58.859 --> 00:43:00.530 align:start position:0% we are looking at two ways of recovery one<00:42:59.160> is<00:42:59.339> a<00:42:59.460> proactive<00:42:59.819> recovery<00:43:00.300> and<00:43:00.420> a 00:43:00.530 --> 00:43:00.540 align:start position:0% one is a proactive recovery and a 00:43:00.540 --> 00:43:02.390 align:start position:0% one is a proactive recovery and a reactive<00:43:00.960> recovery<00:43:01.380> but<00:43:01.619> we<00:43:01.800> are<00:43:01.920> offloading 00:43:02.390 --> 00:43:02.400 align:start position:0% reactive recovery but we are offloading 00:43:02.400 --> 00:43:04.309 align:start position:0% reactive recovery but we are offloading this<00:43:02.520> to<00:43:02.640> the<00:43:02.819> community<00:43:02.940> in<00:43:03.480> our<00:43:03.660> protocol<00:43:03.960> at 00:43:04.309 --> 00:43:04.319 align:start position:0% this to the community in our protocol at 00:43:04.319 --> 00:43:06.290 align:start position:0% this to the community in our protocol at least<00:43:04.440> so<00:43:04.980> it's<00:43:05.220> basically<00:43:05.520> like<00:43:05.760> moving<00:43:06.060> from 00:43:06.290 --> 00:43:06.300 align:start position:0% least so it's basically like moving from 00:43:06.300 --> 00:43:07.790 align:start position:0% least so it's basically like moving from moving<00:43:06.660> your<00:43:06.900> phone<00:43:07.260> like<00:43:07.560> if<00:43:07.680> you're 00:43:07.790 --> 00:43:07.800 align:start position:0% moving your phone like if you're 00:43:07.800 --> 00:43:10.370 align:start position:0% moving your phone like if you're importing<00:43:08.640> your<00:43:08.819> number<00:43:09.000> uh<00:43:09.780> from<00:43:10.020> one<00:43:10.200> phone 00:43:10.370 --> 00:43:10.380 align:start position:0% importing your number uh from one phone 00:43:10.380 --> 00:43:12.230 align:start position:0% importing your number uh from one phone to<00:43:10.560> the<00:43:10.680> other<00:43:10.800> so<00:43:11.280> you're<00:43:11.460> actually<00:43:11.819> doing<00:43:12.000> a 00:43:12.230 --> 00:43:12.240 align:start position:0% to the other so you're actually doing a 00:43:12.240 --> 00:43:14.089 align:start position:0% to the other so you're actually doing a proactive<00:43:12.660> action<00:43:12.900> so<00:43:13.200> you<00:43:13.560> have<00:43:13.680> to<00:43:13.800> kind<00:43:13.980> of 00:43:14.089 --> 00:43:14.099 align:start position:0% proactive action so you have to kind of 00:43:14.099 --> 00:43:15.770 align:start position:0% proactive action so you have to kind of like<00:43:14.220> prove<00:43:14.640> that<00:43:14.880> you<00:43:15.060> are<00:43:15.180> the<00:43:15.420> owner<00:43:15.599> of 00:43:15.770 --> 00:43:15.780 align:start position:0% like prove that you are the owner of 00:43:15.780 --> 00:43:17.150 align:start position:0% like prove that you are the owner of this<00:43:15.900> account<00:43:16.079> and<00:43:16.440> the<00:43:16.619> account<00:43:16.740> that<00:43:17.040> you're 00:43:17.150 --> 00:43:17.160 align:start position:0% this account and the account that you're 00:43:17.160 --> 00:43:18.829 align:start position:0% this account and the account that you're porting<00:43:17.520> over<00:43:17.640> to<00:43:17.880> but<00:43:18.420> the<00:43:18.540> way<00:43:18.720> we're 00:43:18.829 --> 00:43:18.839 align:start position:0% porting over to but the way we're 00:43:18.839 --> 00:43:20.870 align:start position:0% porting over to but the way we're thinking<00:43:19.200> about<00:43:19.319> this<00:43:19.680> is<00:43:19.920> uh<00:43:20.220> you<00:43:20.760> can't 00:43:20.870 --> 00:43:20.880 align:start position:0% thinking about this is uh you can't 00:43:20.880 --> 00:43:22.910 align:start position:0% thinking about this is uh you can't transfer<00:43:21.420> these<00:43:21.660> tokens<00:43:21.960> but<00:43:22.260> you<00:43:22.440> can<00:43:22.560> burn 00:43:22.910 --> 00:43:22.920 align:start position:0% transfer these tokens but you can burn 00:43:22.920 --> 00:43:25.069 align:start position:0% transfer these tokens but you can burn all<00:43:23.460> the<00:43:23.640> tokens<00:43:24.000> as<00:43:24.420> the<00:43:24.599> owner<00:43:24.839> of<00:43:24.960> the 00:43:25.069 --> 00:43:25.079 align:start position:0% all the tokens as the owner of the 00:43:25.079 --> 00:43:26.690 align:start position:0% all the tokens as the owner of the current<00:43:25.200> account<00:43:25.500> and<00:43:26.099> you<00:43:26.220> can<00:43:26.280> get<00:43:26.520> it 00:43:26.690 --> 00:43:26.700 align:start position:0% current account and you can get it 00:43:26.700 --> 00:43:29.870 align:start position:0% current account and you can get it reissued<00:43:27.359> through<00:43:27.960> the<00:43:28.680> the<00:43:28.980> issuing 00:43:29.870 --> 00:43:29.880 align:start position:0% reissued through the the issuing 00:43:29.880 --> 00:43:31.250 align:start position:0% reissued through the the issuing authority<00:43:30.300> which<00:43:30.599> is<00:43:30.720> generally<00:43:31.020> the 00:43:31.250 --> 00:43:31.260 align:start position:0% authority which is generally the 00:43:31.260 --> 00:43:33.829 align:start position:0% authority which is generally the communities<00:43:31.680> or<00:43:31.920> Davos<00:43:32.339> the<00:43:33.119> other<00:43:33.240> aspect<00:43:33.660> is 00:43:33.829 --> 00:43:33.839 align:start position:0% communities or Davos the other aspect is 00:43:33.839 --> 00:43:35.870 align:start position:0% communities or Davos the other aspect is reactive<00:43:34.440> recovery<00:43:35.160> which<00:43:35.339> is<00:43:35.460> where<00:43:35.579> like<00:43:35.760> I 00:43:35.870 --> 00:43:35.880 align:start position:0% reactive recovery which is where like I 00:43:35.880 --> 00:43:39.170 align:start position:0% reactive recovery which is where like I lost<00:43:36.060> everything<00:43:36.980> then<00:43:37.980> you<00:43:38.579> know<00:43:38.640> that's<00:43:38.880> a 00:43:39.170 --> 00:43:39.180 align:start position:0% lost everything then you know that's a 00:43:39.180 --> 00:43:40.790 align:start position:0% lost everything then you know that's a tricky<00:43:39.420> one<00:43:39.540> you<00:43:39.780> have<00:43:39.900> to<00:43:40.020> establish<00:43:40.380> with 00:43:40.790 --> 00:43:40.800 align:start position:0% tricky one you have to establish with 00:43:40.800 --> 00:43:43.430 align:start position:0% tricky one you have to establish with your<00:43:41.099> uh<00:43:41.520> like<00:43:41.700> your<00:43:41.880> Dao<00:43:42.240> for<00:43:42.420> example<00:43:42.720> that 00:43:43.430 --> 00:43:43.440 align:start position:0% your uh like your Dao for example that 00:43:43.440 --> 00:43:45.050 align:start position:0% your uh like your Dao for example that hey<00:43:43.619> I'm<00:43:43.800> the<00:43:44.040> same<00:43:44.160> person<00:43:44.339> behind<00:43:44.760> this<00:43:44.880> new 00:43:45.050 --> 00:43:45.060 align:start position:0% hey I'm the same person behind this new 00:43:45.060 --> 00:43:48.050 align:start position:0% hey I'm the same person behind this new wallet<00:43:45.480> like<00:43:45.900> you<00:43:46.079> have<00:43:46.260> to<00:43:46.500> re-issue<00:43:47.339> it<00:43:47.520> and 00:43:48.050 --> 00:43:48.060 align:start position:0% wallet like you have to re-issue it and 00:43:48.060 --> 00:43:49.490 align:start position:0% wallet like you have to re-issue it and one<00:43:48.240> of<00:43:48.359> the<00:43:48.420> models<00:43:48.900> we<00:43:49.020> are<00:43:49.140> looking<00:43:49.319> at 00:43:49.490 --> 00:43:49.500 align:start position:0% one of the models we are looking at 00:43:49.500 --> 00:43:51.109 align:start position:0% one of the models we are looking at there<00:43:49.740> is<00:43:49.920> reassurance<00:43:50.460> but<00:43:50.760> the<00:43:50.940> community 00:43:51.109 --> 00:43:51.119 align:start position:0% there is reassurance but the community 00:43:51.119 --> 00:43:54.470 align:start position:0% there is reassurance but the community perhaps<00:43:51.780> can<00:43:52.079> revoke<00:43:52.740> those<00:43:52.980> badges<00:43:53.480> so 00:43:54.470 --> 00:43:54.480 align:start position:0% perhaps can revoke those badges so 00:43:54.480 --> 00:43:55.790 align:start position:0% perhaps can revoke those badges so that's<00:43:54.599> that's<00:43:54.839> how<00:43:55.140> we're<00:43:55.260> kind<00:43:55.500> of<00:43:55.560> thinking 00:43:55.790 --> 00:43:55.800 align:start position:0% that's that's how we're kind of thinking 00:43:55.800 --> 00:43:58.390 align:start position:0% that's that's how we're kind of thinking about<00:43:55.920> it<00:43:56.160> thanks 00:43:58.390 --> 00:43:58.400 align:start position:0% about it thanks 00:43:58.400 --> 00:44:01.190 align:start position:0% about it thanks more<00:43:59.400> more<00:43:59.460> questions<00:43:59.940> we<00:44:00.359> have<00:44:00.480> time<00:44:00.720> for<00:44:01.020> one 00:44:01.190 --> 00:44:01.200 align:start position:0% more more questions we have time for one 00:44:01.200 --> 00:44:02.990 align:start position:0% more more questions we have time for one more<00:44:01.440> question<00:44:01.680> here 00:44:02.990 --> 00:44:03.000 align:start position:0% more question here 00:44:03.000 --> 00:44:06.890 align:start position:0% more question here oh 00:44:06.890 --> 00:44:06.900 align:start position:0% 00:44:06.900 --> 00:44:07.730 align:start position:0% um 00:44:07.730 --> 00:44:07.740 align:start position:0% um 00:44:07.740 --> 00:44:11.150 align:start position:0% um uh<00:44:08.460> just<00:44:08.760> a<00:44:08.880> quick<00:44:09.119> thing<00:44:09.359> regarding 00:44:11.150 --> 00:44:11.160 align:start position:0% uh just a quick thing regarding 00:44:11.160 --> 00:44:11.890 align:start position:0% uh just a quick thing regarding um 00:44:11.890 --> 00:44:11.900 align:start position:0% um 00:44:11.900 --> 00:44:14.870 align:start position:0% um uh<00:44:12.900> recovery<00:44:13.500> through<00:44:13.980> burning<00:44:14.579> and<00:44:14.760> then 00:44:14.870 --> 00:44:14.880 align:start position:0% uh recovery through burning and then 00:44:14.880 --> 00:44:16.910 align:start position:0% uh recovery through burning and then reissuing<00:44:15.540> it<00:44:15.960> would<00:44:16.079> be<00:44:16.260> awesome<00:44:16.440> if<00:44:16.740> there 00:44:16.910 --> 00:44:16.920 align:start position:0% reissuing it would be awesome if there 00:44:16.920 --> 00:44:18.710 align:start position:0% reissuing it would be awesome if there was<00:44:17.040> a<00:44:17.160> way<00:44:17.280> to<00:44:17.400> do<00:44:17.520> that<00:44:17.700> atomically<00:44:18.300> yeah 00:44:18.710 --> 00:44:18.720 align:start position:0% was a way to do that atomically yeah 00:44:18.720 --> 00:44:21.470 align:start position:0% was a way to do that atomically yeah right<00:44:19.500> but<00:44:20.099> the<00:44:20.280> other<00:44:20.339> question<00:44:20.700> was<00:44:20.940> what<00:44:21.300> is 00:44:21.470 --> 00:44:21.480 align:start position:0% right but the other question was what is 00:44:21.480 --> 00:44:24.950 align:start position:0% right but the other question was what is the<00:44:21.780> status<00:44:22.140> of<00:44:22.680> the<00:44:22.859> EIP<00:44:23.300> is<00:44:24.300> there<00:44:24.480> time<00:44:24.720> to 00:44:24.950 --> 00:44:24.960 align:start position:0% the status of the EIP is there time to 00:44:24.960 --> 00:44:27.710 align:start position:0% the status of the EIP is there time to still<00:44:25.200> make<00:44:25.500> breaking<00:44:26.339> changes<00:44:26.760> uh<00:44:27.240> or<00:44:27.480> is<00:44:27.599> it 00:44:27.710 --> 00:44:27.720 align:start position:0% still make breaking changes uh or is it 00:44:27.720 --> 00:44:29.510 align:start position:0% still make breaking changes uh or is it already<00:44:27.900> like<00:44:28.140> so<00:44:28.319> widely<00:44:28.680> adopted<00:44:29.040> and<00:44:29.400> this 00:44:29.510 --> 00:44:29.520 align:start position:0% already like so widely adopted and this 00:44:29.520 --> 00:44:30.670 align:start position:0% already like so widely adopted and this kind<00:44:29.640> of<00:44:29.760> relates<00:44:29.940> to<00:44:30.060> this<00:44:30.180> stagnation 00:44:30.670 --> 00:44:30.680 align:start position:0% kind of relates to this stagnation 00:44:30.680 --> 00:44:32.930 align:start position:0% kind of relates to this stagnation discussion<00:44:31.680> but<00:44:31.859> I<00:44:32.040> think<00:44:32.220> it's<00:44:32.339> yeah<00:44:32.760> that's 00:44:32.930 --> 00:44:32.940 align:start position:0% discussion but I think it's yeah that's 00:44:32.940 --> 00:44:34.130 align:start position:0% discussion but I think it's yeah that's a<00:44:33.119> good<00:44:33.240> question<00:44:33.359> I<00:44:33.599> should<00:44:33.780> have<00:44:33.900> actually 00:44:34.130 --> 00:44:34.140 align:start position:0% a good question I should have actually 00:44:34.140 --> 00:44:37.609 align:start position:0% a good question I should have actually uh<00:44:34.800> put<00:44:34.980> the<00:44:35.160> stats<00:44:35.520> on<00:44:35.579> it<00:44:35.760> I<00:44:36.359> mean<00:44:36.540> uh<00:44:37.140> people 00:44:37.609 --> 00:44:37.619 align:start position:0% uh put the stats on it I mean uh people 00:44:37.619 --> 00:44:40.190 align:start position:0% uh put the stats on it I mean uh people are<00:44:37.740> already<00:44:37.859> using<00:44:38.280> it<00:44:38.460> we've<00:44:39.180> seen<00:44:39.359> uh<00:44:40.020> I 00:44:40.190 --> 00:44:40.200 align:start position:0% are already using it we've seen uh I 00:44:40.200 --> 00:44:43.609 align:start position:0% are already using it we've seen uh I don't<00:44:40.260> know<00:44:40.380> maybe<00:44:40.619> like<00:44:41.099> a<00:44:41.760> 150<00:44:42.660> 300<00:44:43.079> hits<00:44:43.319> on 00:44:43.609 --> 00:44:43.619 align:start position:0% don't know maybe like a 150 300 hits on 00:44:43.619 --> 00:44:46.609 align:start position:0% don't know maybe like a 150 300 hits on probably<00:44:43.920> somewhere<00:44:44.400> on<00:44:44.880> GitHub<00:44:45.300> so<00:44:46.260> we<00:44:46.440> are 00:44:46.609 --> 00:44:46.619 align:start position:0% probably somewhere on GitHub so we are 00:44:46.619 --> 00:44:47.750 align:start position:0% probably somewhere on GitHub so we are actively<00:44:46.980> thinking<00:44:47.220> about<00:44:47.339> backward 00:44:47.750 --> 00:44:47.760 align:start position:0% actively thinking about backward 00:44:47.760 --> 00:44:49.309 align:start position:0% actively thinking about backward compatibility<00:44:48.300> when<00:44:48.599> we're<00:44:48.720> adding<00:44:49.020> but<00:44:49.200> the 00:44:49.309 --> 00:44:49.319 align:start position:0% compatibility when we're adding but the 00:44:49.319 --> 00:44:52.250 align:start position:0% compatibility when we're adding but the EIP<00:44:49.619> is<00:44:49.859> in<00:44:49.980> review<00:44:50.160> stage<00:44:50.579> at<00:44:50.760> the<00:44:50.880> moment<00:44:51.260> uh 00:44:52.250 --> 00:44:52.260 align:start position:0% EIP is in review stage at the moment uh 00:44:52.260 --> 00:44:54.710 align:start position:0% EIP is in review stage at the moment uh yeah<00:44:52.619> when<00:44:52.859> and<00:44:53.099> now<00:44:53.339> we're<00:44:53.579> kind<00:44:54.420> of<00:44:54.540> talking 00:44:54.710 --> 00:44:54.720 align:start position:0% yeah when and now we're kind of talking 00:44:54.720 --> 00:44:57.950 align:start position:0% yeah when and now we're kind of talking about<00:44:54.900> expiration<00:44:55.560> uh<00:44:56.280> as<00:44:56.579> a<00:44:56.760> as<00:44:57.359> to<00:44:57.480> be<00:44:57.660> baked 00:44:57.950 --> 00:44:57.960 align:start position:0% about expiration uh as a as to be baked 00:44:57.960 --> 00:44:59.870 align:start position:0% about expiration uh as a as to be baked into<00:44:58.079> a<00:44:58.319> badge<00:44:58.619> where<00:44:58.800> you<00:44:59.280> can<00:44:59.339> give<00:44:59.520> like<00:44:59.700> a 00:44:59.870 --> 00:44:59.880 align:start position:0% into a badge where you can give like a 00:44:59.880 --> 00:45:01.430 align:start position:0% into a badge where you can give like a 30-day<00:45:00.180> expiration<00:45:00.599> badge<00:45:01.020> for<00:45:01.200> example 00:45:01.430 --> 00:45:01.440 align:start position:0% 30-day expiration badge for example 00:45:01.440 --> 00:45:03.490 align:start position:0% 30-day expiration badge for example especially<00:45:01.920> if<00:45:02.099> you're<00:45:02.280> like 00:45:03.490 --> 00:45:03.500 align:start position:0% especially if you're like 00:45:03.500 --> 00:45:06.290 align:start position:0% especially if you're like joining<00:45:04.500> a<00:45:04.619> dial<00:45:04.800> you<00:45:05.220> get<00:45:05.339> guest<00:45:05.700> batch<00:45:06.060> for 00:45:06.290 --> 00:45:06.300 align:start position:0% joining a dial you get guest batch for 00:45:06.300 --> 00:45:07.430 align:start position:0% joining a dial you get guest batch for example<00:45:06.540> you<00:45:07.020> know<00:45:07.079> you<00:45:07.140> can<00:45:07.260> do<00:45:07.319> some 00:45:07.430 --> 00:45:07.440 align:start position:0% example you know you can do some 00:45:07.440 --> 00:45:09.530 align:start position:0% example you know you can do some interest<00:45:08.040> so<00:45:08.520> expiring<00:45:09.000> badge<00:45:09.300> is<00:45:09.300> something 00:45:09.530 --> 00:45:09.540 align:start position:0% interest so expiring badge is something 00:45:09.540 --> 00:45:12.589 align:start position:0% interest so expiring badge is something we're<00:45:09.720> looking<00:45:09.960> at<00:45:10.140> but<00:45:10.680> uh<00:45:11.579> yeah<00:45:11.880> like<00:45:12.180> we<00:45:12.420> are 00:45:12.589 --> 00:45:12.599 align:start position:0% we're looking at but uh yeah like we are 00:45:12.599 --> 00:45:14.030 align:start position:0% we're looking at but uh yeah like we are this<00:45:12.839> is<00:45:12.960> one<00:45:13.140> of<00:45:13.260> the<00:45:13.260> forums<00:45:13.619> we're<00:45:13.800> hoping 00:45:14.030 --> 00:45:14.040 align:start position:0% this is one of the forums we're hoping 00:45:14.040 --> 00:45:15.950 align:start position:0% this is one of the forums we're hoping to<00:45:14.220> get<00:45:14.579> feedback<00:45:14.880> on<00:45:15.060> like<00:45:15.359> you<00:45:15.540> know<00:45:15.599> where 00:45:15.950 --> 00:45:15.960 align:start position:0% to get feedback on like you know where 00:45:15.960 --> 00:45:17.690 align:start position:0% to get feedback on like you know where should<00:45:16.260> we<00:45:16.380> park<00:45:16.560> it<00:45:16.800> should<00:45:16.980> we<00:45:17.099> get<00:45:17.280> feedback 00:45:17.690 --> 00:45:17.700 align:start position:0% should we park it should we get feedback 00:45:17.700 --> 00:45:20.750 align:start position:0% should we park it should we get feedback or<00:45:17.940> have<00:45:18.180> invest<00:45:18.720> in<00:45:18.839> extensions<00:45:19.440> and<00:45:20.160> like<00:45:20.339> uh 00:45:20.750 --> 00:45:20.760 align:start position:0% or have invest in extensions and like uh 00:45:20.760 --> 00:45:22.250 align:start position:0% or have invest in extensions and like uh because<00:45:21.180> there's<00:45:21.359> a<00:45:21.480> lot<00:45:21.540> of<00:45:21.660> utility<00:45:21.900> this 00:45:22.250 --> 00:45:22.260 align:start position:0% because there's a lot of utility this 00:45:22.260 --> 00:45:24.170 align:start position:0% because there's a lot of utility this can<00:45:22.440> deliver<00:45:22.560> in<00:45:22.800> its<00:45:23.040> current<00:45:23.160> form<00:45:23.520> you<00:45:24.119> know 00:45:24.170 --> 00:45:24.180 align:start position:0% can deliver in its current form you know 00:45:24.180 --> 00:45:27.470 align:start position:0% can deliver in its current form you know and<00:45:24.420> then<00:45:24.599> uh<00:45:25.020> it<00:45:25.260> would<00:45:25.380> be<00:45:25.560> uh<00:45:26.280> strange<00:45:27.240> to 00:45:27.470 --> 00:45:27.480 align:start position:0% and then uh it would be uh strange to 00:45:27.480 --> 00:45:29.750 align:start position:0% and then uh it would be uh strange to perhaps<00:45:27.960> like<00:45:28.200> you<00:45:28.560> know<00:45:28.619> stretch<00:45:29.579> this 00:45:29.750 --> 00:45:29.760 align:start position:0% perhaps like you know stretch this 00:45:29.760 --> 00:45:31.730 align:start position:0% perhaps like you know stretch this timeline<00:45:30.180> because<00:45:30.420> I<00:45:30.839> think<00:45:30.960> uh<00:45:31.319> I've<00:45:31.560> seen 00:45:31.730 --> 00:45:31.740 align:start position:0% timeline because I think uh I've seen 00:45:31.740 --> 00:45:34.250 align:start position:0% timeline because I think uh I've seen aips<00:45:32.099> go<00:45:32.400> for<00:45:32.520> years 00:45:34.250 --> 00:45:34.260 align:start position:0% aips go for years 00:45:34.260 --> 00:45:37.790 align:start position:0% aips go for years thank<00:45:34.859> thank<00:45:35.099> you<00:45:35.339> Raul<00:45:35.780> uh<00:45:36.780> Applause<00:45:37.440> please 00:45:37.790 --> 00:45:37.800 align:start position:0% thank thank you Raul uh Applause please 00:45:37.800 --> 00:45:39.170 align:start position:0% thank thank you Raul uh Applause please thank<00:45:38.220> you 00:45:39.170 --> 00:45:39.180 align:start position:0% thank you 00:45:39.180 --> 00:45:42.290 align:start position:0% thank you uh 00:45:42.290 --> 00:45:42.300 align:start position:0% 00:45:42.300 --> 00:45:43.370 align:start position:0% yeah 00:45:43.370 --> 00:45:43.380 align:start position:0% yeah 00:45:43.380 --> 00:45:44.089 align:start position:0% yeah um 00:45:44.089 --> 00:45:44.099 align:start position:0% um 00:45:44.099 --> 00:45:46.910 align:start position:0% um I'm<00:45:44.700> just<00:45:45.060> gonna<00:45:45.300> while<00:45:45.900> the<00:45:46.440> next<00:45:46.619> speaker 00:45:46.910 --> 00:45:46.920 align:start position:0% I'm just gonna while the next speaker 00:45:46.920 --> 00:45:50.510 align:start position:0% I'm just gonna while the next speaker Sweetman<00:45:47.640> is<00:45:48.420> um<00:45:48.420> going<00:45:48.720> to<00:45:48.900> set<00:45:49.079> up<00:45:49.319> the<00:45:49.920> uh 00:45:50.510 --> 00:45:50.520 align:start position:0% Sweetman is um going to set up the uh 00:45:50.520 --> 00:45:52.790 align:start position:0% Sweetman is um going to set up the uh the<00:45:50.700> laptop<00:45:50.940> and<00:45:51.119> so<00:45:51.300> on<00:45:51.420> I'm<00:45:51.599> just<00:45:51.839> gonna<00:45:51.960> walk 00:45:52.790 --> 00:45:52.800 align:start position:0% the laptop and so on I'm just gonna walk 00:45:52.800 --> 00:45:54.890 align:start position:0% the laptop and so on I'm just gonna walk you<00:45:52.980> through<00:45:53.280> the<00:45:54.000> rest<00:45:54.119> of<00:45:54.300> our<00:45:54.480> timetable 00:45:54.890 --> 00:45:54.900 align:start position:0% you through the rest of our timetable 00:45:54.900 --> 00:45:58.190 align:start position:0% you through the rest of our timetable which<00:45:55.380> is<00:45:55.859> by<00:45:56.160> the<00:45:56.339> way<00:45:56.400> here<00:45:56.700> so<00:45:57.180> uh<00:45:57.839> next<00:45:58.079> up 00:45:58.190 --> 00:45:58.200 align:start position:0% which is by the way here so uh next up 00:45:58.200 --> 00:46:00.349 align:start position:0% which is by the way here so uh next up is<00:45:58.560> uh<00:45:58.819> sweetman.eath<00:45:59.819> and<00:46:00.000> he's<00:46:00.119> going<00:46:00.240> to 00:46:00.349 --> 00:46:00.359 align:start position:0% is uh sweetman.eath and he's going to 00:46:00.359 --> 00:46:03.050 align:start position:0% is uh sweetman.eath and he's going to talk<00:46:00.480> about<00:46:00.680> uh<00:46:01.680> music<00:46:02.099> the<00:46:02.460> music<00:46:02.700> nft 00:46:03.050 --> 00:46:03.060 align:start position:0% talk about uh music the music nft 00:46:03.060 --> 00:46:06.829 align:start position:0% talk about uh music the music nft engineer<00:46:03.859> then<00:46:04.859> we<00:46:05.040> have<00:46:05.220> Andres<00:46:05.819> who<00:46:06.720> is 00:46:06.829 --> 00:46:06.839 align:start position:0% engineer then we have Andres who is 00:46:06.839 --> 00:46:09.710 align:start position:0% engineer then we have Andres who is going<00:46:07.020> to<00:46:07.140> talk<00:46:07.319> about<00:46:07.560> uh<00:46:08.400> web3<00:46:08.880> the<00:46:09.300> web<00:46:09.480> 3 00:46:09.710 --> 00:46:09.720 align:start position:0% going to talk about uh web3 the web 3 00:46:09.720 --> 00:46:12.470 align:start position:0% going to talk about uh web3 the web 3 music<00:46:10.260> nft<00:46:10.740> multiplayer<00:46:11.700> problems<00:46:12.119> I'm<00:46:12.240> very 00:46:12.470 --> 00:46:12.480 align:start position:0% music nft multiplayer problems I'm very 00:46:12.480 --> 00:46:14.990 align:start position:0% music nft multiplayer problems I'm very excited<00:46:12.780> about<00:46:12.960> that<00:46:13.200> I<00:46:13.440> think<00:46:13.560> it's<00:46:13.800> uh<00:46:14.760> like 00:46:14.990 --> 00:46:15.000 align:start position:0% excited about that I think it's uh like 00:46:15.000 --> 00:46:17.349 align:start position:0% excited about that I think it's uh like it<00:46:15.119> comes<00:46:15.420> out<00:46:15.540> of<00:46:15.720> water<00:46:16.140> and<00:46:16.440> music<00:46:16.560> research 00:46:17.349 --> 00:46:17.359 align:start position:0% it comes out of water and music research 00:46:17.359 --> 00:46:20.569 align:start position:0% it comes out of water and music research then<00:46:18.359> we<00:46:18.540> have<00:46:18.660> Ian<00:46:19.079> who<00:46:19.859> is<00:46:19.980> going<00:46:20.220> to<00:46:20.400> talk 00:46:20.569 --> 00:46:20.579 align:start position:0% then we have Ian who is going to talk 00:46:20.579 --> 00:46:23.870 align:start position:0% then we have Ian who is going to talk about<00:46:20.819> uh<00:46:21.599> Rich<00:46:21.900> content<00:46:22.319> types<00:46:22.740> in<00:46:23.099> nfts<00:46:23.760> and 00:46:23.870 --> 00:46:23.880 align:start position:0% about uh Rich content types in nfts and 00:46:23.880 --> 00:46:26.690 align:start position:0% about uh Rich content types in nfts and then<00:46:24.060> finally<00:46:24.420> we<00:46:24.960> have<00:46:25.140> Francisco<00:46:25.579> who<00:46:26.579> is 00:46:26.690 --> 00:46:26.700 align:start position:0% then finally we have Francisco who is 00:46:26.700 --> 00:46:30.170 align:start position:0% then finally we have Francisco who is going<00:46:26.940> to<00:46:27.060> talk<00:46:27.300> about<00:46:27.980> a<00:46:28.980> uh<00:46:29.640> like<00:46:29.880> a<00:46:30.060> very 00:46:30.170 --> 00:46:30.180 align:start position:0% going to talk about a uh like a very 00:46:30.180 --> 00:46:32.050 align:start position:0% going to talk about a uh like a very recent<00:46:30.480> EIP<00:46:30.900> called 00:46:32.050 --> 00:46:32.060 align:start position:0% recent EIP called 00:46:32.060 --> 00:46:35.770 align:start position:0% recent EIP called 5267<00:46:33.260> I<00:46:34.260> think<00:46:34.319> which 00:46:35.770 --> 00:46:35.780 align:start position:0% 5267 I think which 00:46:35.780 --> 00:46:38.329 align:start position:0% 5267 I think which uh<00:46:36.780> I<00:46:37.079> think<00:46:37.260> it<00:46:37.380> defines<00:46:37.800> the<00:46:37.980> domain 00:46:38.329 --> 00:46:38.339 align:start position:0% uh I think it defines the domain 00:46:38.339 --> 00:46:41.050 align:start position:0% uh I think it defines the domain separator<00:46:38.819> of<00:46:39.240> EIP 00:46:41.050 --> 00:46:41.060 align:start position:0% separator of EIP 00:46:41.060 --> 00:46:44.690 align:start position:0% separator of EIP 712<00:46:42.060> so<00:46:42.680> yeah<00:46:43.680> if<00:46:43.859> you're<00:46:44.040> familiar<00:46:44.400> with<00:46:44.520> that 00:46:44.690 --> 00:46:44.700 align:start position:0% 712 so yeah if you're familiar with that 00:46:44.700 --> 00:46:46.550 align:start position:0% 712 so yeah if you're familiar with that I<00:46:44.940> guess<00:46:45.060> it's<00:46:45.300> you<00:46:45.900> you<00:46:46.079> kind<00:46:46.319> of<00:46:46.440> understand 00:46:46.550 --> 00:46:46.560 align:start position:0% I guess it's you you kind of understand 00:46:46.560 --> 00:46:49.430 align:start position:0% I guess it's you you kind of understand what<00:46:46.859> it<00:46:47.040> is<00:46:47.160> if<00:46:47.339> not<00:46:47.520> then<00:46:47.880> I<00:46:48.720> recommend<00:46:49.079> going 00:46:49.430 --> 00:46:49.440 align:start position:0% what it is if not then I recommend going 00:46:49.440 --> 00:46:50.770 align:start position:0% what it is if not then I recommend going to 00:46:50.770 --> 00:46:50.780 align:start position:0% to 00:46:50.780 --> 00:46:53.690 align:start position:0% to eips.etherium.org<00:46:51.780> and<00:46:51.900> reading<00:46:52.319> up<00:46:52.500> on<00:46:52.740> it 00:46:53.690 --> 00:46:53.700 align:start position:0% eips.etherium.org and reading up on it 00:46:53.700 --> 00:46:54.290 align:start position:0% eips.etherium.org and reading up on it um 00:46:54.290 --> 00:46:54.300 align:start position:0% um 00:46:54.300 --> 00:46:56.870 align:start position:0% um uh<00:46:54.960> yeah<00:46:55.140> okay<00:46:55.440> I<00:46:56.220> do<00:46:56.280> have<00:46:56.460> a<00:46:56.579> lot<00:46:56.640> of<00:46:56.760> music 00:46:56.870 --> 00:46:56.880 align:start position:0% uh yeah okay I do have a lot of music 00:46:56.880 --> 00:46:59.630 align:start position:0% uh yeah okay I do have a lot of music nfts<00:46:57.480> for<00:46:57.599> y'all<00:46:57.780> today<00:46:57.960> so<00:46:58.680> first<00:46:59.160> I'll<00:46:59.339> ask<00:46:59.520> a 00:46:59.630 --> 00:46:59.640 align:start position:0% nfts for y'all today so first I'll ask a 00:46:59.640 --> 00:47:03.170 align:start position:0% nfts for y'all today so first I'll ask a couple<00:46:59.700> questions<00:46:59.940> who<00:47:00.720> has<00:47:00.900> a<00:47:01.140> music<00:47:01.260> nft 00:47:03.170 --> 00:47:03.180 align:start position:0% couple questions who has a music nft 00:47:03.180 --> 00:47:07.790 align:start position:0% couple questions who has a music nft okay<00:47:04.079> who<00:47:04.680> owns<00:47:04.980> any<00:47:05.099> nfts<00:47:05.640> on<00:47:05.760> optimism 00:47:07.790 --> 00:47:07.800 align:start position:0% okay who owns any nfts on optimism 00:47:07.800 --> 00:47:11.510 align:start position:0% okay who owns any nfts on optimism who<00:47:08.520> owns<00:47:08.819> nfts<00:47:09.420> on<00:47:09.540> arbitrum 00:47:11.510 --> 00:47:11.520 align:start position:0% who owns nfts on arbitrum 00:47:11.520 --> 00:47:14.990 align:start position:0% who owns nfts on arbitrum who<00:47:11.940> owns<00:47:12.180> nfts<00:47:12.720> on<00:47:12.900> polygon 00:47:14.990 --> 00:47:15.000 align:start position:0% who owns nfts on polygon 00:47:15.000 --> 00:47:16.849 align:start position:0% who owns nfts on polygon my<00:47:15.540> goal<00:47:15.720> is<00:47:15.839> by<00:47:16.020> the<00:47:16.140> end<00:47:16.260> of<00:47:16.380> this<00:47:16.440> you<00:47:16.740> will 00:47:16.849 --> 00:47:16.859 align:start position:0% my goal is by the end of this you will 00:47:16.859 --> 00:47:18.589 align:start position:0% my goal is by the end of this you will have<00:47:16.980> your<00:47:17.099> hand<00:47:17.220> up<00:47:17.339> for<00:47:17.520> all<00:47:17.640> of<00:47:17.760> those 00:47:18.589 --> 00:47:18.599 align:start position:0% have your hand up for all of those 00:47:18.599 --> 00:47:21.470 align:start position:0% have your hand up for all of those hi<00:47:19.020> I'm<00:47:19.319> sweetman.ie<00:47:20.099> aka<00:47:20.760> the<00:47:20.940> music<00:47:21.060> nft 00:47:21.470 --> 00:47:21.480 align:start position:0% hi I'm sweetman.ie aka the music nft 00:47:21.480 --> 00:47:23.270 align:start position:0% hi I'm sweetman.ie aka the music nft engineer<00:47:22.140> and<00:47:22.500> today 00:47:23.270 --> 00:47:23.280 align:start position:0% engineer and today 00:47:23.280 --> 00:47:26.930 align:start position:0% engineer and today we're<00:47:23.579> going<00:47:23.700> to<00:47:23.760> talk<00:47:23.880> about<00:47:24.060> music<00:47:24.540> metadata 00:47:26.930 --> 00:47:26.940 align:start position:0% we're going to talk about music metadata 00:47:26.940 --> 00:47:29.030 align:start position:0% we're going to talk about music metadata first<00:47:27.240> the<00:47:27.540> problem<00:47:27.720> you're<00:47:28.260> going<00:47:28.440> to<00:47:28.500> see<00:47:28.619> QR 00:47:29.030 --> 00:47:29.040 align:start position:0% first the problem you're going to see QR 00:47:29.040 --> 00:47:31.309 align:start position:0% first the problem you're going to see QR codes<00:47:29.160> throughout<00:47:29.579> this<00:47:29.760> the<00:47:30.599> ones<00:47:30.839> on<00:47:31.140> that 00:47:31.309 --> 00:47:31.319 align:start position:0% codes throughout this the ones on that 00:47:31.319 --> 00:47:33.770 align:start position:0% codes throughout this the ones on that side<00:47:31.500> are<00:47:32.220> from<00:47:32.460> musicians<00:47:33.000> in<00:47:33.240> Latin<00:47:33.599> America 00:47:33.770 --> 00:47:33.780 align:start position:0% side are from musicians in Latin America 00:47:33.780 --> 00:47:36.170 align:start position:0% side are from musicians in Latin America if<00:47:34.680> you<00:47:34.800> want<00:47:34.980> to<00:47:35.099> support<00:47:35.339> creators<00:47:35.880> here<00:47:36.060> in 00:47:36.170 --> 00:47:36.180 align:start position:0% if you want to support creators here in 00:47:36.180 --> 00:47:38.890 align:start position:0% if you want to support creators here in Latin<00:47:36.480> America<00:47:36.619> scan<00:47:37.619> that<00:47:37.800> by<00:47:38.400> the<00:47:38.579> nft 00:47:38.890 --> 00:47:38.900 align:start position:0% Latin America scan that by the nft 00:47:38.900 --> 00:47:41.630 align:start position:0% Latin America scan that by the nft support<00:47:39.900> local<00:47:40.380> creators 00:47:41.630 --> 00:47:41.640 align:start position:0% support local creators 00:47:41.640 --> 00:47:45.290 align:start position:0% support local creators on<00:47:42.240> this<00:47:42.359> side<00:47:42.540> you'll<00:47:43.200> see<00:47:43.380> cc0<00:47:44.160> music<00:47:44.579> nfts 00:47:45.290 --> 00:47:45.300 align:start position:0% on this side you'll see cc0 music nfts 00:47:45.300 --> 00:47:49.250 align:start position:0% on this side you'll see cc0 music nfts 100<00:47:46.079> Freeman<00:47:46.920> on<00:47:47.640> different<00:47:47.760> chains<00:47:48.359> and<00:47:49.079> so 00:47:49.250 --> 00:47:49.260 align:start position:0% 100 Freeman on different chains and so 00:47:49.260 --> 00:47:50.809 align:start position:0% 100 Freeman on different chains and so they'll<00:47:49.500> be<00:47:49.619> scattered<00:47:49.920> throughout<00:47:50.220> if<00:47:50.700> you 00:47:50.809 --> 00:47:50.819 align:start position:0% they'll be scattered throughout if you 00:47:50.819 --> 00:47:52.550 align:start position:0% they'll be scattered throughout if you want<00:47:51.000> some<00:47:51.180> nfts 00:47:52.550 --> 00:47:52.560 align:start position:0% want some nfts 00:47:52.560 --> 00:47:53.930 align:start position:0% want some nfts momentum 00:47:53.930 --> 00:47:53.940 align:start position:0% momentum 00:47:53.940 --> 00:47:55.730 align:start position:0% momentum the<00:47:54.420> problem 00:47:55.730 --> 00:47:55.740 align:start position:0% the problem 00:47:55.740 --> 00:47:57.349 align:start position:0% the problem don't<00:47:56.160> worry<00:47:56.339> the<00:47:56.520> same<00:47:56.640> QR<00:47:56.940> codes<00:47:57.060> are<00:47:57.240> going 00:47:57.349 --> 00:47:57.359 align:start position:0% don't worry the same QR codes are going 00:47:57.359 --> 00:47:59.210 align:start position:0% don't worry the same QR codes are going to be<00:47:57.480> a<00:47:57.540> little<00:47:57.599> bit<00:47:57.720> hidden<00:47:57.960> in<00:47:58.079> here 00:47:59.210 --> 00:47:59.220 align:start position:0% to be a little bit hidden in here 00:47:59.220 --> 00:48:01.910 align:start position:0% to be a little bit hidden in here music<00:47:59.640> platforms<00:48:00.300> are<00:48:00.660> not<00:48:00.900> creating<00:48:01.380> music 00:48:01.910 --> 00:48:01.920 align:start position:0% music platforms are not creating music 00:48:01.920 --> 00:48:04.730 align:start position:0% music platforms are not creating music nfts<00:48:02.700> this<00:48:03.420> is<00:48:03.599> a<00:48:03.720> very<00:48:03.839> spicy<00:48:04.200> take<00:48:04.380> that<00:48:04.680> I 00:48:04.730 --> 00:48:04.740 align:start position:0% nfts this is a very spicy take that I 00:48:04.740 --> 00:48:07.730 align:start position:0% nfts this is a very spicy take that I like<00:48:04.859> to<00:48:04.980> hold<00:48:05.160> you'll<00:48:06.000> see<00:48:06.180> on<00:48:06.420> the<00:48:06.780> your<00:48:07.440> left 00:48:07.730 --> 00:48:07.740 align:start position:0% like to hold you'll see on the your left 00:48:07.740 --> 00:48:10.970 align:start position:0% like to hold you'll see on the your left side<00:48:07.920> these<00:48:08.880> are<00:48:08.940> metadata<00:48:09.599> from<00:48:09.960> the<00:48:10.319> top<00:48:10.500> nft 00:48:10.970 --> 00:48:10.980 align:start position:0% side these are metadata from the top nft 00:48:10.980 --> 00:48:12.290 align:start position:0% side these are metadata from the top nft platforms 00:48:12.290 --> 00:48:12.300 align:start position:0% platforms 00:48:12.300 --> 00:48:16.190 align:start position:0% platforms up<00:48:13.020> top<00:48:13.200> you've<00:48:13.920> got<00:48:14.160> Zora<00:48:14.819> creator<00:48:15.599> in<00:48:16.079> the 00:48:16.190 --> 00:48:16.200 align:start position:0% up top you've got Zora creator in the 00:48:16.200 --> 00:48:18.890 align:start position:0% up top you've got Zora creator in the middle<00:48:16.319> you've<00:48:17.160> got<00:48:17.339> catalog<00:48:18.060> and<00:48:18.599> down<00:48:18.780> at 00:48:18.890 --> 00:48:18.900 align:start position:0% middle you've got catalog and down at 00:48:18.900 --> 00:48:20.809 align:start position:0% middle you've got catalog and down at the<00:48:19.079> bottom<00:48:19.260> you've<00:48:19.859> got<00:48:19.980> sound 00:48:20.809 --> 00:48:20.819 align:start position:0% the bottom you've got sound 00:48:20.819 --> 00:48:22.250 align:start position:0% the bottom you've got sound you'll<00:48:21.240> notice<00:48:21.480> that<00:48:21.660> they<00:48:21.900> each<00:48:22.079> have 00:48:22.250 --> 00:48:22.260 align:start position:0% you'll notice that they each have 00:48:22.260 --> 00:48:25.069 align:start position:0% you'll notice that they each have different<00:48:22.560> metadata<00:48:23.220> but<00:48:24.119> honestly<00:48:24.839> there's 00:48:25.069 --> 00:48:25.079 align:start position:0% different metadata but honestly there's 00:48:25.079 --> 00:48:26.750 align:start position:0% different metadata but honestly there's no<00:48:25.260> real<00:48:25.380> differentiation<00:48:26.040> between<00:48:26.400> the 00:48:26.750 --> 00:48:26.760 align:start position:0% no real differentiation between the 00:48:26.760 --> 00:48:29.690 align:start position:0% no real differentiation between the metadata<00:48:27.180> of<00:48:27.359> a<00:48:27.540> music<00:48:27.660> nft<00:48:28.079> and<00:48:28.980> a<00:48:29.160> normal<00:48:29.339> nft 00:48:29.690 --> 00:48:29.700 align:start position:0% metadata of a music nft and a normal nft 00:48:29.700 --> 00:48:31.730 align:start position:0% metadata of a music nft and a normal nft in<00:48:30.359> most<00:48:30.480> cases 00:48:31.730 --> 00:48:31.740 align:start position:0% in most cases 00:48:31.740 --> 00:48:33.829 align:start position:0% in most cases over<00:48:32.099> here<00:48:32.220> on<00:48:32.400> this<00:48:32.579> side<00:48:32.760> you'll<00:48:33.480> see<00:48:33.660> the 00:48:33.829 --> 00:48:33.839 align:start position:0% over here on this side you'll see the 00:48:33.839 --> 00:48:35.630 align:start position:0% over here on this side you'll see the music<00:48:34.020> metadata<00:48:34.680> standard 00:48:35.630 --> 00:48:35.640 align:start position:0% music metadata standard 00:48:35.640 --> 00:48:39.050 align:start position:0% music metadata standard this<00:48:36.119> includes<00:48:36.599> the<00:48:37.260> same<00:48:37.640> attributes<00:48:38.640> as<00:48:38.880> a 00:48:39.050 --> 00:48:39.060 align:start position:0% this includes the same attributes as a 00:48:39.060 --> 00:48:41.569 align:start position:0% this includes the same attributes as a normal<00:48:39.180> nft<00:48:39.599> in<00:48:40.560> addition<00:48:40.800> to<00:48:41.040> attributes 00:48:41.569 --> 00:48:41.579 align:start position:0% normal nft in addition to attributes 00:48:41.579 --> 00:48:43.430 align:start position:0% normal nft in addition to attributes that<00:48:41.700> matter<00:48:41.880> for<00:48:42.119> music<00:48:42.319> attributes<00:48:43.319> like 00:48:43.430 --> 00:48:43.440 align:start position:0% that matter for music attributes like 00:48:43.440 --> 00:48:45.710 align:start position:0% that matter for music attributes like lossless<00:48:43.859> audio<00:48:44.060> attributes<00:48:45.060> like<00:48:45.180> BPM 00:48:45.710 --> 00:48:45.720 align:start position:0% lossless audio attributes like BPM 00:48:45.720 --> 00:48:48.170 align:start position:0% lossless audio attributes like BPM attributes<00:48:46.680> like<00:48:46.800> duration<00:48:47.160> these<00:48:48.119> are 00:48:48.170 --> 00:48:48.180 align:start position:0% attributes like duration these are 00:48:48.180 --> 00:48:49.370 align:start position:0% attributes like duration these are things<00:48:48.359> that<00:48:48.540> matter<00:48:48.720> when<00:48:49.020> we're<00:48:49.200> talking 00:48:49.370 --> 00:48:49.380 align:start position:0% things that matter when we're talking 00:48:49.380 --> 00:48:52.190 align:start position:0% things that matter when we're talking about<00:48:49.680> platforms<00:48:50.339> like<00:48:50.520> Spotify<00:48:50.880> or<00:48:51.720> Zora 00:48:52.190 --> 00:48:52.200 align:start position:0% about platforms like Spotify or Zora 00:48:52.200 --> 00:48:54.890 align:start position:0% about platforms like Spotify or Zora wanting<00:48:52.680> to<00:48:52.800> index<00:48:53.160> these<00:48:53.520> nfts<00:48:54.000> and<00:48:54.660> to<00:48:54.780> be 00:48:54.890 --> 00:48:54.900 align:start position:0% wanting to index these nfts and to be 00:48:54.900 --> 00:48:56.210 align:start position:0% wanting to index these nfts and to be able<00:48:54.960> to<00:48:55.079> differentiate<00:48:55.560> between<00:48:55.859> a<00:48:56.099> music 00:48:56.210 --> 00:48:56.220 align:start position:0% able to differentiate between a music 00:48:56.220 --> 00:48:58.069 align:start position:0% able to differentiate between a music nft<00:48:56.579> and<00:48:56.760> a<00:48:56.880> normal<00:48:57.000> nft 00:48:58.069 --> 00:48:58.079 align:start position:0% nft and a normal nft 00:48:58.079 --> 00:49:00.230 align:start position:0% nft and a normal nft why<00:48:58.680> does<00:48:58.800> this<00:48:58.980> matter 00:49:00.230 --> 00:49:00.240 align:start position:0% why does this matter 00:49:00.240 --> 00:49:03.050 align:start position:0% why does this matter when<00:49:00.780> we<00:49:00.960> talk<00:49:01.140> about<00:49:01.319> ethereum<00:49:02.099> congrats 00:49:03.050 --> 00:49:03.060 align:start position:0% when we talk about ethereum congrats 00:49:03.060 --> 00:49:05.089 align:start position:0% when we talk about ethereum congrats we're<00:49:03.420> in<00:49:03.599> the<00:49:03.720> ethereum<00:49:04.079> Wizards<00:49:04.560> room<00:49:04.680> we 00:49:05.089 --> 00:49:05.099 align:start position:0% we're in the ethereum Wizards room we 00:49:05.099 --> 00:49:07.490 align:start position:0% we're in the ethereum Wizards room we have<00:49:05.220> merged<00:49:05.700> and<00:49:06.420> so<00:49:06.599> now<00:49:06.720> the<00:49:07.079> next<00:49:07.200> kind<00:49:07.440> of 00:49:07.490 --> 00:49:07.500 align:start position:0% have merged and so now the next kind of 00:49:07.500 --> 00:49:09.170 align:start position:0% have merged and so now the next kind of goal<00:49:07.800> in<00:49:07.859> our<00:49:08.040> identity<00:49:08.400> crisis<00:49:08.819> as<00:49:09.000> a 00:49:09.170 --> 00:49:09.180 align:start position:0% goal in our identity crisis as a 00:49:09.180 --> 00:49:11.210 align:start position:0% goal in our identity crisis as a community<00:49:09.300> is<00:49:09.660> how<00:49:10.500> do<00:49:10.619> we<00:49:10.740> get<00:49:10.800> Global 00:49:11.210 --> 00:49:11.220 align:start position:0% community is how do we get Global 00:49:11.220 --> 00:49:12.410 align:start position:0% community is how do we get Global adoption 00:49:12.410 --> 00:49:12.420 align:start position:0% adoption 00:49:12.420 --> 00:49:15.770 align:start position:0% adoption I<00:49:12.720> see<00:49:12.900> music<00:49:13.079> nfts<00:49:13.740> as<00:49:13.980> the<00:49:14.160> Trojan<00:49:14.700> Horse<00:49:15.000> for 00:49:15.770 --> 00:49:15.780 align:start position:0% I see music nfts as the Trojan Horse for 00:49:15.780 --> 00:49:17.990 align:start position:0% I see music nfts as the Trojan Horse for ethereum<00:49:16.319> adoption<00:49:16.800> while<00:49:17.520> a<00:49:17.700> lot<00:49:17.819> of<00:49:17.880> people 00:49:17.990 --> 00:49:18.000 align:start position:0% ethereum adoption while a lot of people 00:49:18.000 --> 00:49:20.270 align:start position:0% ethereum adoption while a lot of people don't<00:49:18.180> care<00:49:18.359> about<00:49:18.480> nfts<00:49:19.200> most<00:49:19.800> people<00:49:19.980> do 00:49:20.270 --> 00:49:20.280 align:start position:0% don't care about nfts most people do 00:49:20.280 --> 00:49:22.670 align:start position:0% don't care about nfts most people do care<00:49:20.460> about<00:49:20.640> music<00:49:21.060> and<00:49:21.839> so<00:49:22.020> if<00:49:22.260> we<00:49:22.380> can<00:49:22.500> build 00:49:22.670 --> 00:49:22.680 align:start position:0% care about music and so if we can build 00:49:22.680 --> 00:49:24.829 align:start position:0% care about music and so if we can build platforms<00:49:23.220> that<00:49:23.400> allow<00:49:23.700> music<00:49:23.880> nfts<00:49:24.480> to<00:49:24.660> plug 00:49:24.829 --> 00:49:24.839 align:start position:0% platforms that allow music nfts to plug 00:49:24.839 --> 00:49:26.270 align:start position:0% platforms that allow music nfts to plug seamlessly<00:49:25.440> into<00:49:25.619> the<00:49:25.920> existing 00:49:26.270 --> 00:49:26.280 align:start position:0% seamlessly into the existing 00:49:26.280 --> 00:49:28.550 align:start position:0% seamlessly into the existing infrastructure<00:49:26.940> we<00:49:27.660> can<00:49:27.720> allow<00:49:28.020> for<00:49:28.200> more<00:49:28.440> and 00:49:28.550 --> 00:49:28.560 align:start position:0% infrastructure we can allow for more and 00:49:28.560 --> 00:49:30.230 align:start position:0% infrastructure we can allow for more and more<00:49:28.740> people<00:49:28.859> to<00:49:29.099> be<00:49:29.160> consuming<00:49:29.640> the<00:49:29.819> ethereum 00:49:30.230 --> 00:49:30.240 align:start position:0% more people to be consuming the ethereum 00:49:30.240 --> 00:49:32.690 align:start position:0% more people to be consuming the ethereum technology<00:49:30.660> that<00:49:30.960> we<00:49:31.140> know<00:49:31.319> and<00:49:31.500> love<00:49:31.740> but<00:49:32.520> the 00:49:32.690 --> 00:49:32.700 align:start position:0% technology that we know and love but the 00:49:32.700 --> 00:49:34.130 align:start position:0% technology that we know and love but the big<00:49:32.819> challenge<00:49:33.000> right<00:49:33.300> now<00:49:33.420> is<00:49:33.960> that 00:49:34.130 --> 00:49:34.140 align:start position:0% big challenge right now is that 00:49:34.140 --> 00:49:36.290 align:start position:0% big challenge right now is that musicians<00:49:34.619> are<00:49:34.740> using<00:49:35.040> these<00:49:35.220> platforms<00:49:35.760> that 00:49:36.290 --> 00:49:36.300 align:start position:0% musicians are using these platforms that 00:49:36.300 --> 00:49:37.730 align:start position:0% musicians are using these platforms that don't<00:49:36.480> really<00:49:36.660> differentiate<00:49:37.200> metadata 00:49:37.730 --> 00:49:37.740 align:start position:0% don't really differentiate metadata 00:49:37.740 --> 00:49:42.890 align:start position:0% don't really differentiate metadata between<00:49:37.920> normal<00:49:38.220> nfts<00:49:38.940> and<00:49:39.420> music<00:49:39.599> nfts 00:49:42.890 --> 00:49:42.900 align:start position:0% 00:49:42.900 --> 00:49:45.710 align:start position:0% next<00:49:43.680> the<00:49:44.339> opportunity 00:49:45.710 --> 00:49:45.720 align:start position:0% next the opportunity 00:49:45.720 --> 00:49:47.690 align:start position:0% next the opportunity another<00:49:46.200> set<00:49:46.440> of<00:49:46.560> nfts<00:49:46.980> oh<00:49:47.099> yeah<00:49:47.220> the<00:49:47.400> last<00:49:47.520> one 00:49:47.690 --> 00:49:47.700 align:start position:0% another set of nfts oh yeah the last one 00:49:47.700 --> 00:49:49.010 align:start position:0% another set of nfts oh yeah the last one I'm<00:49:48.000> sorry<00:49:48.119> I<00:49:48.300> didn't<00:49:48.420> I<00:49:48.599> didn't<00:49:48.720> shout<00:49:48.900> out 00:49:49.010 --> 00:49:49.020 align:start position:0% I'm sorry I didn't I didn't shout out 00:49:49.020 --> 00:49:51.109 align:start position:0% I'm sorry I didn't I didn't shout out the<00:49:49.140> Creator<00:49:49.380> so<00:49:49.920> the<00:49:50.099> last<00:49:50.220> Creator<00:49:50.579> this 00:49:51.109 --> 00:49:51.119 align:start position:0% the Creator so the last Creator this 00:49:51.119 --> 00:49:53.390 align:start position:0% the Creator so the last Creator this first<00:49:51.300> nft<00:49:51.599> is<00:49:51.839> caspiel<00:49:52.319> we've<00:49:52.859> got<00:49:52.980> Colombo 00:49:53.390 --> 00:49:53.400 align:start position:0% first nft is caspiel we've got Colombo 00:49:53.400 --> 00:49:54.470 align:start position:0% first nft is caspiel we've got Colombo in<00:49:53.579> the<00:49:53.700> audience 00:49:54.470 --> 00:49:54.480 align:start position:0% in the audience 00:49:54.480 --> 00:49:56.809 align:start position:0% in the audience um<00:49:54.540> manager<00:49:55.020> of<00:49:55.079> cast<00:49:55.260> peel<00:49:55.680> and<00:49:56.280> so<00:49:56.400> that<00:49:56.520> nft 00:49:56.809 --> 00:49:56.819 align:start position:0% um manager of cast peel and so that nft 00:49:56.819 --> 00:49:58.670 align:start position:0% um manager of cast peel and so that nft is<00:49:57.060> from<00:49:57.180> a<00:49:57.300> musician<00:49:57.599> named<00:49:57.839> caspiel<00:49:58.319> who 00:49:58.670 --> 00:49:58.680 align:start position:0% is from a musician named caspiel who 00:49:58.680 --> 00:50:00.950 align:start position:0% is from a musician named caspiel who dropped<00:49:58.920> on<00:49:59.040> Zora<00:49:59.520> Creator<00:49:59.819> and<00:50:00.480> that<00:50:00.660> is<00:50:00.720> a 00:50:00.950 --> 00:50:00.960 align:start position:0% dropped on Zora Creator and that is a 00:50:00.960 --> 00:50:02.630 align:start position:0% dropped on Zora Creator and that is a music<00:50:01.079> video<00:50:01.380> of<00:50:01.859> her<00:50:02.040> latest<00:50:02.160> music<00:50:02.400> video 00:50:02.630 --> 00:50:02.640 align:start position:0% music video of her latest music video 00:50:02.640 --> 00:50:05.870 align:start position:0% music video of her latest music video reflejo<00:50:03.780> and<00:50:04.319> uh<00:50:04.560> all<00:50:04.740> of<00:50:04.920> my<00:50:05.040> music<00:50:05.220> nfts<00:50:05.760> are 00:50:05.870 --> 00:50:05.880 align:start position:0% reflejo and uh all of my music nfts are 00:50:05.880 --> 00:50:08.089 align:start position:0% reflejo and uh all of my music nfts are cc0<00:50:06.359> from<00:50:06.540> a<00:50:06.720> musician<00:50:06.960> named<00:50:07.200> Sagrado<00:50:07.680> based 00:50:08.089 --> 00:50:08.099 align:start position:0% cc0 from a musician named Sagrado based 00:50:08.099 --> 00:50:10.130 align:start position:0% cc0 from a musician named Sagrado based out<00:50:08.160> of<00:50:08.280> Mexico<00:50:08.460> my<00:50:09.300> favorite<00:50:09.420> because<00:50:09.900> he 00:50:10.130 --> 00:50:10.140 align:start position:0% out of Mexico my favorite because he 00:50:10.140 --> 00:50:11.690 align:start position:0% out of Mexico my favorite because he does<00:50:10.319> everything<00:50:10.440> cc0 00:50:11.690 --> 00:50:11.700 align:start position:0% does everything cc0 00:50:11.700 --> 00:50:13.550 align:start position:0% does everything cc0 this<00:50:12.119> next<00:50:12.240> one<00:50:12.480> over<00:50:13.140> here<00:50:13.260> we've<00:50:13.500> got 00:50:13.550 --> 00:50:13.560 align:start position:0% this next one over here we've got 00:50:13.560 --> 00:50:15.710 align:start position:0% this next one over here we've got another<00:50:13.740> Zora<00:50:14.220> nft<00:50:14.460> I<00:50:15.300> think<00:50:15.420> we've<00:50:15.599> got 00:50:15.710 --> 00:50:15.720 align:start position:0% another Zora nft I think we've got 00:50:15.720 --> 00:50:17.150 align:start position:0% another Zora nft I think we've got tranky<00:50:16.200> in<00:50:16.319> the<00:50:16.440> audience<00:50:16.560> who<00:50:16.800> helped<00:50:17.040> a 00:50:17.150 --> 00:50:17.160 align:start position:0% tranky in the audience who helped a 00:50:17.160 --> 00:50:19.550 align:start position:0% tranky in the audience who helped a Buenos<00:50:17.579> Aires<00:50:17.940> Creator<00:50:18.240> named<00:50:18.660> uh<00:50:19.319> well 00:50:19.550 --> 00:50:19.560 align:start position:0% Buenos Aires Creator named uh well 00:50:19.560 --> 00:50:21.890 align:start position:0% Buenos Aires Creator named uh well created<00:50:19.859> a<00:50:20.040> platform<00:50:20.220> called<00:50:20.400> unun<00:50:20.880> and<00:50:21.599> so<00:50:21.720> if 00:50:21.890 --> 00:50:21.900 align:start position:0% created a platform called unun and so if 00:50:21.900 --> 00:50:23.210 align:start position:0% created a platform called unun and so if you<00:50:22.020> scan<00:50:22.260> this<00:50:22.440> it'll<00:50:22.740> take<00:50:22.859> you<00:50:22.920> over<00:50:23.040> to 00:50:23.210 --> 00:50:23.220 align:start position:0% you scan this it'll take you over to 00:50:23.220 --> 00:50:25.370 align:start position:0% you scan this it'll take you over to unun<00:50:23.520> to<00:50:23.819> Mint<00:50:24.000> some<00:50:24.240> music<00:50:24.359> nfts<00:50:25.020> from<00:50:25.200> local 00:50:25.370 --> 00:50:25.380 align:start position:0% unun to Mint some music nfts from local 00:50:25.380 --> 00:50:27.050 align:start position:0% unun to Mint some music nfts from local Buenos<00:50:25.859> Aires<00:50:26.160> creators 00:50:27.050 --> 00:50:27.060 align:start position:0% Buenos Aires creators 00:50:27.060 --> 00:50:28.970 align:start position:0% Buenos Aires creators and<00:50:27.480> this<00:50:27.599> one<00:50:27.720> is<00:50:27.839> another<00:50:27.960> one<00:50:28.200> from<00:50:28.440> Sagrado 00:50:28.970 --> 00:50:28.980 align:start position:0% and this one is another one from Sagrado 00:50:28.980 --> 00:50:30.829 align:start position:0% and this one is another one from Sagrado and<00:50:29.280> this<00:50:29.520> one<00:50:29.700> I<00:50:29.880> believe<00:50:30.000> is<00:50:30.180> on<00:50:30.359> polygon 00:50:30.829 --> 00:50:30.839 align:start position:0% and this one I believe is on polygon 00:50:30.839 --> 00:50:32.450 align:start position:0% and this one I believe is on polygon last<00:50:31.200> one<00:50:31.380> was<00:50:31.560> optimism<00:50:31.920> this<00:50:32.160> one's<00:50:32.400> on 00:50:32.450 --> 00:50:32.460 align:start position:0% last one was optimism this one's on 00:50:32.460 --> 00:50:34.010 align:start position:0% last one was optimism this one's on polygon 00:50:34.010 --> 00:50:34.020 align:start position:0% polygon 00:50:34.020 --> 00:50:35.930 align:start position:0% polygon the<00:50:34.380> opportunity<00:50:34.859> we<00:50:35.160> have<00:50:35.280> an<00:50:35.460> opportunity 00:50:35.930 --> 00:50:35.940 align:start position:0% the opportunity we have an opportunity 00:50:35.940 --> 00:50:38.870 align:start position:0% the opportunity we have an opportunity right<00:50:36.240> now<00:50:36.359> to<00:50:36.720> standardize<00:50:37.260> music<00:50:37.680> metadata 00:50:38.870 --> 00:50:38.880 align:start position:0% right now to standardize music metadata 00:50:38.880 --> 00:50:41.150 align:start position:0% right now to standardize music metadata right<00:50:39.540> now<00:50:39.720> it's<00:50:40.079> been<00:50:40.319> in<00:50:40.440> discussions<00:50:40.920> you 00:50:41.150 --> 00:50:41.160 align:start position:0% right now it's been in discussions you 00:50:41.160 --> 00:50:42.589 align:start position:0% right now it's been in discussions you might<00:50:41.280> have<00:50:41.400> heard<00:50:41.520> about<00:50:41.700> telegram<00:50:42.180> groups 00:50:42.589 --> 00:50:42.599 align:start position:0% might have heard about telegram groups 00:50:42.599 --> 00:50:44.089 align:start position:0% might have heard about telegram groups you<00:50:42.780> might<00:50:42.900> have<00:50:43.020> heard<00:50:43.200> about<00:50:43.380> different 00:50:44.089 --> 00:50:44.099 align:start position:0% you might have heard about different 00:50:44.099 --> 00:50:45.530 align:start position:0% you might have heard about different chats<00:50:44.579> that<00:50:44.700> are<00:50:44.760> scattered<00:50:45.060> amongst<00:50:45.480> the 00:50:45.530 --> 00:50:45.540 align:start position:0% chats that are scattered amongst the 00:50:45.540 --> 00:50:47.690 align:start position:0% chats that are scattered amongst the music<00:50:45.720> nft<00:50:46.020> ecosystems<00:50:46.800> maybe<00:50:47.220> you've<00:50:47.460> talked 00:50:47.690 --> 00:50:47.700 align:start position:0% music nft ecosystems maybe you've talked 00:50:47.700 --> 00:50:49.370 align:start position:0% music nft ecosystems maybe you've talked with<00:50:47.760> Hi-Fi<00:50:48.059> Labs<00:50:48.480> about<00:50:48.599> their<00:50:48.780> music<00:50:49.020> nft 00:50:49.370 --> 00:50:49.380 align:start position:0% with Hi-Fi Labs about their music nft 00:50:49.380 --> 00:50:51.349 align:start position:0% with Hi-Fi Labs about their music nft standards<00:50:49.920> maybe<00:50:50.339> you've<00:50:50.579> talked<00:50:50.819> with<00:50:50.940> Zora 00:50:51.349 --> 00:50:51.359 align:start position:0% standards maybe you've talked with Zora 00:50:51.359 --> 00:50:52.970 align:start position:0% standards maybe you've talked with Zora there's<00:50:51.540> a<00:50:51.720> lot<00:50:51.839> of<00:50:52.020> different<00:50:52.200> standards<00:50:52.740> out 00:50:52.970 --> 00:50:52.980 align:start position:0% there's a lot of different standards out 00:50:52.980 --> 00:50:54.470 align:start position:0% there's a lot of different standards out there<00:50:53.099> we<00:50:53.700> have<00:50:53.819> not<00:50:53.940> really<00:50:54.119> reached 00:50:54.470 --> 00:50:54.480 align:start position:0% there we have not really reached 00:50:54.480 --> 00:50:56.329 align:start position:0% there we have not really reached consensus<00:50:55.020> and<00:50:55.319> I<00:50:55.500> find<00:50:55.680> that<00:50:55.980> awesome 00:50:56.329 --> 00:50:56.339 align:start position:0% consensus and I find that awesome 00:50:56.339 --> 00:50:58.790 align:start position:0% consensus and I find that awesome because<00:50:57.119> there's<00:50:57.540> no<00:50:57.960> gatekeeper<00:50:58.619> there's 00:50:58.790 --> 00:50:58.800 align:start position:0% because there's no gatekeeper there's 00:50:58.800 --> 00:51:00.290 align:start position:0% because there's no gatekeeper there's nobody<00:50:59.099> that's<00:50:59.339> telling<00:50:59.640> us<00:50:59.700> this<00:50:59.940> is<00:51:00.059> how<00:51:00.180> it 00:51:00.290 --> 00:51:00.300 align:start position:0% nobody that's telling us this is how it 00:51:00.300 --> 00:51:03.109 align:start position:0% nobody that's telling us this is how it is<00:51:00.480> it's<00:51:00.960> very<00:51:01.140> much<00:51:01.260> a<00:51:01.440> bottom-up<00:51:01.940> what<00:51:02.940> does 00:51:03.109 --> 00:51:03.119 align:start position:0% is it's very much a bottom-up what does 00:51:03.119 --> 00:51:04.549 align:start position:0% is it's very much a bottom-up what does each<00:51:03.359> Creator<00:51:03.660> want<00:51:03.900> to<00:51:04.020> use<00:51:04.200> when<00:51:04.440> they're 00:51:04.549 --> 00:51:04.559 align:start position:0% each Creator want to use when they're 00:51:04.559 --> 00:51:06.829 align:start position:0% each Creator want to use when they're making<00:51:04.740> their<00:51:04.980> music<00:51:05.099> nfts 00:51:06.829 --> 00:51:06.839 align:start position:0% making their music nfts 00:51:06.839 --> 00:51:08.510 align:start position:0% making their music nfts um and<00:51:06.960> again<00:51:07.140> the<00:51:07.619> full<00:51:07.740> music<00:51:07.920> metadata 00:51:08.510 --> 00:51:08.520 align:start position:0% um and again the full music metadata 00:51:08.520 --> 00:51:11.870 align:start position:0% um and again the full music metadata standard<00:51:08.760> over<00:51:08.880> there<00:51:09.059> on<00:51:09.180> this<00:51:09.420> other<00:51:09.660> side 00:51:11.870 --> 00:51:11.880 align:start position:0% standard over there on this other side 00:51:11.880 --> 00:51:13.370 align:start position:0% standard over there on this other side how<00:51:12.359> you<00:51:12.480> can<00:51:12.599> help 00:51:13.370 --> 00:51:13.380 align:start position:0% how you can help 00:51:13.380 --> 00:51:16.250 align:start position:0% how you can help again<00:51:13.920> the<00:51:14.520> music<00:51:14.640> metadata<00:51:15.300> standard<00:51:15.660> is<00:51:15.900> not 00:51:16.250 --> 00:51:16.260 align:start position:0% again the music metadata standard is not 00:51:16.260 --> 00:51:18.530 align:start position:0% again the music metadata standard is not something<00:51:16.740> that<00:51:17.220> we're<00:51:17.579> gonna<00:51:17.700> have<00:51:17.880> Sony<00:51:18.240> or 00:51:18.530 --> 00:51:18.540 align:start position:0% something that we're gonna have Sony or 00:51:18.540 --> 00:51:20.270 align:start position:0% something that we're gonna have Sony or Warner<00:51:18.960> or<00:51:19.260> some<00:51:19.380> record<00:51:19.559> label<00:51:19.980> is<00:51:20.040> going<00:51:20.220> to 00:51:20.270 --> 00:51:20.280 align:start position:0% Warner or some record label is going to 00:51:20.280 --> 00:51:22.130 align:start position:0% Warner or some record label is going to come<00:51:20.400> down<00:51:20.520> and<00:51:20.700> say<00:51:20.819> this<00:51:21.059> is<00:51:21.180> how<00:51:21.300> it<00:51:21.420> is<00:51:21.599> it's 00:51:22.130 --> 00:51:22.140 align:start position:0% come down and say this is how it is it's 00:51:22.140 --> 00:51:23.990 align:start position:0% come down and say this is how it is it's going<00:51:22.319> to<00:51:22.380> be<00:51:22.500> bottom<00:51:22.800> up<00:51:22.980> from<00:51:23.520> the<00:51:23.640> engineers 00:51:23.990 --> 00:51:24.000 align:start position:0% going to be bottom up from the engineers 00:51:24.000 --> 00:51:25.430 align:start position:0% going to be bottom up from the engineers that<00:51:24.240> are<00:51:24.359> building<00:51:24.540> from<00:51:24.839> the<00:51:24.960> creators<00:51:25.319> that 00:51:25.430 --> 00:51:25.440 align:start position:0% that are building from the creators that 00:51:25.440 --> 00:51:26.870 align:start position:0% that are building from the creators that are<00:51:25.559> choosing<00:51:25.800> what<00:51:25.980> platforms<00:51:26.400> to<00:51:26.579> build<00:51:26.700> on 00:51:26.870 --> 00:51:26.880 align:start position:0% are choosing what platforms to build on 00:51:26.880 --> 00:51:29.150 align:start position:0% are choosing what platforms to build on each<00:51:27.420> of<00:51:27.480> us<00:51:27.599> as<00:51:27.780> individuals<00:51:28.380> is<00:51:28.680> choosing 00:51:29.150 --> 00:51:29.160 align:start position:0% each of us as individuals is choosing 00:51:29.160 --> 00:51:31.549 align:start position:0% each of us as individuals is choosing which<00:51:29.400> memes<00:51:29.819> we<00:51:30.000> want<00:51:30.180> to<00:51:30.359> propagate<00:51:30.900> in 00:51:31.549 --> 00:51:31.559 align:start position:0% which memes we want to propagate in 00:51:31.559 --> 00:51:33.589 align:start position:0% which memes we want to propagate in order<00:51:31.680> to<00:51:31.980> make<00:51:32.160> the<00:51:32.520> mess<00:51:32.700> the<00:51:33.000> best<00:51:33.119> metadata 00:51:33.589 --> 00:51:33.599 align:start position:0% order to make the mess the best metadata 00:51:33.599 --> 00:51:34.430 align:start position:0% order to make the mess the best metadata win 00:51:34.430 --> 00:51:34.440 align:start position:0% win 00:51:34.440 --> 00:51:37.190 align:start position:0% win the<00:51:35.099> final<00:51:35.220> set<00:51:35.520> of<00:51:35.700> nfts<00:51:36.180> we've<00:51:36.359> got<00:51:36.480> this<00:51:37.079> is 00:51:37.190 --> 00:51:37.200 align:start position:0% the final set of nfts we've got this is 00:51:37.200 --> 00:51:39.109 align:start position:0% the final set of nfts we've got this is a<00:51:37.380> catalog<00:51:37.680> nft<00:51:38.040> from<00:51:38.460> a<00:51:38.579> Creator<00:51:38.760> named<00:51:39.000> hey 00:51:39.109 --> 00:51:39.119 align:start position:0% a catalog nft from a Creator named hey 00:51:39.119 --> 00:51:41.150 align:start position:0% a catalog nft from a Creator named hey Bella<00:51:39.599> who<00:51:40.020> is<00:51:40.079> also<00:51:40.319> based<00:51:40.619> here<00:51:40.680> in<00:51:40.859> Colombia 00:51:41.150 --> 00:51:41.160 align:start position:0% Bella who is also based here in Colombia 00:51:41.160 --> 00:51:43.790 align:start position:0% Bella who is also based here in Colombia in<00:51:41.280> Medellin<00:51:42.119> and<00:51:42.660> this<00:51:42.900> one<00:51:43.020> is<00:51:43.200> an<00:51:43.380> arbitrum 00:51:43.790 --> 00:51:43.800 align:start position:0% in Medellin and this one is an arbitrum 00:51:43.800 --> 00:51:46.010 align:start position:0% in Medellin and this one is an arbitrum nft<00:51:44.040> the<00:51:44.520> same<00:51:44.640> nft 00:51:46.010 --> 00:51:46.020 align:start position:0% nft the same nft 00:51:46.020 --> 00:51:48.950 align:start position:0% nft the same nft um<00:51:46.079> by<00:51:46.500> Sagrado 00:51:48.950 --> 00:51:48.960 align:start position:0% um by Sagrado 00:51:48.960 --> 00:51:50.510 align:start position:0% um by Sagrado spread<00:51:49.440> the<00:51:49.500> memes 00:51:50.510 --> 00:51:50.520 align:start position:0% spread the memes 00:51:50.520 --> 00:51:52.250 align:start position:0% spread the memes all<00:51:50.940> the<00:51:51.059> ethereum<00:51:51.420> Wizards<00:51:51.839> all<00:51:52.079> of<00:51:52.200> you 00:51:52.250 --> 00:51:52.260 align:start position:0% all the ethereum Wizards all of you 00:51:52.260 --> 00:51:54.530 align:start position:0% all the ethereum Wizards all of you Builders<00:51:52.680> we<00:51:53.099> are<00:51:53.220> building 00:51:54.530 --> 00:51:54.540 align:start position:0% Builders we are building 00:51:54.540 --> 00:51:55.430 align:start position:0% Builders we are building um 00:51:55.430 --> 00:51:55.440 align:start position:0% um 00:51:55.440 --> 00:51:57.950 align:start position:0% um it's<00:51:55.859> important<00:51:56.099> that<00:51:56.220> we<00:51:56.400> propagate<00:51:56.960> proper 00:51:57.950 --> 00:51:57.960 align:start position:0% it's important that we propagate proper 00:51:57.960 --> 00:51:59.870 align:start position:0% it's important that we propagate proper music<00:51:58.140> metadata<00:51:58.680> when<00:51:58.859> we're<00:51:58.980> building<00:51:59.160> if 00:51:59.870 --> 00:51:59.880 align:start position:0% music metadata when we're building if 00:51:59.880 --> 00:52:01.490 align:start position:0% music metadata when we're building if we're<00:52:00.000> giving<00:52:00.180> these<00:52:00.540> musicians<00:52:01.079> poor 00:52:01.490 --> 00:52:01.500 align:start position:0% we're giving these musicians poor 00:52:01.500 --> 00:52:03.290 align:start position:0% we're giving these musicians poor metadata<00:52:02.040> we're<00:52:02.579> setting<00:52:02.940> them<00:52:03.059> up<00:52:03.119> for 00:52:03.290 --> 00:52:03.300 align:start position:0% metadata we're setting them up for 00:52:03.300 --> 00:52:05.510 align:start position:0% metadata we're setting them up for failure<00:52:03.599> in<00:52:03.720> the<00:52:03.839> long<00:52:03.960> term<00:52:04.140> as<00:52:04.619> Spotify<00:52:04.920> as 00:52:05.510 --> 00:52:05.520 align:start position:0% failure in the long term as Spotify as 00:52:05.520 --> 00:52:07.490 align:start position:0% failure in the long term as Spotify as iTunes<00:52:06.059> as<00:52:06.180> these<00:52:06.480> other<00:52:06.599> big<00:52:06.839> platforms<00:52:07.319> the 00:52:07.490 --> 00:52:07.500 align:start position:0% iTunes as these other big platforms the 00:52:07.500 --> 00:52:09.770 align:start position:0% iTunes as these other big platforms the future<00:52:07.680> tapes<00:52:08.040> the<00:52:08.160> spin<00:52:08.339> amps<00:52:08.700> our<00:52:09.300> indexing 00:52:09.770 --> 00:52:09.780 align:start position:0% future tapes the spin amps our indexing 00:52:09.780 --> 00:52:11.150 align:start position:0% future tapes the spin amps our indexing music<00:52:09.960> nfts 00:52:11.150 --> 00:52:11.160 align:start position:0% music nfts 00:52:11.160 --> 00:52:13.130 align:start position:0% music nfts if<00:52:11.700> we're<00:52:11.819> not<00:52:12.059> putting<00:52:12.300> beats<00:52:12.599> per<00:52:12.720> minute<00:52:12.900> if 00:52:13.130 --> 00:52:13.140 align:start position:0% if we're not putting beats per minute if 00:52:13.140 --> 00:52:14.750 align:start position:0% if we're not putting beats per minute if we're<00:52:13.260> not<00:52:13.440> putting<00:52:13.859> keys<00:52:14.339> if<00:52:14.460> we're<00:52:14.640> not 00:52:14.750 --> 00:52:14.760 align:start position:0% we're not putting keys if we're not 00:52:14.760 --> 00:52:16.730 align:start position:0% we're not putting keys if we're not putting<00:52:15.059> the<00:52:15.180> credits<00:52:15.660> on<00:52:15.900> chain<00:52:16.140> we're 00:52:16.730 --> 00:52:16.740 align:start position:0% putting the credits on chain we're 00:52:16.740 --> 00:52:18.109 align:start position:0% putting the credits on chain we're missing<00:52:17.099> out 00:52:18.109 --> 00:52:18.119 align:start position:0% missing out 00:52:18.119 --> 00:52:20.270 align:start position:0% missing out and<00:52:18.599> so<00:52:18.780> what<00:52:18.900> I've<00:52:19.079> been<00:52:19.200> working<00:52:19.380> on<00:52:19.619> is<00:52:20.099> I 00:52:20.270 --> 00:52:20.280 align:start position:0% and so what I've been working on is I 00:52:20.280 --> 00:52:22.370 align:start position:0% and so what I've been working on is I cloned<00:52:20.640> the<00:52:20.819> Zora<00:52:21.240> metadata<00:52:21.660> render<00:52:21.900> which<00:52:22.260> is 00:52:22.370 --> 00:52:22.380 align:start position:0% cloned the Zora metadata render which is 00:52:22.380 --> 00:52:23.630 align:start position:0% cloned the Zora metadata render which is an<00:52:22.500> architecture<00:52:22.980> that<00:52:23.099> allows<00:52:23.400> us<00:52:23.460> to 00:52:23.630 --> 00:52:23.640 align:start position:0% an architecture that allows us to 00:52:23.640 --> 00:52:27.589 align:start position:0% an architecture that allows us to decouple<00:52:24.180> the<00:52:24.420> erc721<00:52:25.380> the<00:52:25.760> erc1155<00:52:26.760> all<00:52:27.420> the 00:52:27.589 --> 00:52:27.599 align:start position:0% decouple the erc721 the erc1155 all the 00:52:27.599 --> 00:52:29.270 align:start position:0% decouple the erc721 the erc1155 all the tokens<00:52:27.839> we<00:52:28.020> know<00:52:28.140> and<00:52:28.260> love<00:52:28.440> from<00:52:29.160> the 00:52:29.270 --> 00:52:29.280 align:start position:0% tokens we know and love from the 00:52:29.280 --> 00:52:31.010 align:start position:0% tokens we know and love from the metadata<00:52:29.760> that<00:52:29.880> they<00:52:30.000> represent 00:52:31.010 --> 00:52:31.020 align:start position:0% metadata that they represent 00:52:31.020 --> 00:52:33.410 align:start position:0% metadata that they represent and<00:52:31.380> so<00:52:31.500> we<00:52:31.680> have<00:52:31.800> a<00:52:32.040> full<00:52:32.280> music<00:52:32.700> metadata 00:52:33.410 --> 00:52:33.420 align:start position:0% and so we have a full music metadata 00:52:33.420 --> 00:52:35.210 align:start position:0% and so we have a full music metadata standard<00:52:33.720> that's<00:52:33.900> fully<00:52:34.260> on<00:52:34.440> chain<00:52:34.619> deployed 00:52:35.210 --> 00:52:35.220 align:start position:0% standard that's fully on chain deployed 00:52:35.220 --> 00:52:37.549 align:start position:0% standard that's fully on chain deployed on<00:52:35.339> ethereum<00:52:35.700> mainnet<00:52:36.180> polygon<00:52:37.079> mainnet 00:52:37.549 --> 00:52:37.559 align:start position:0% on ethereum mainnet polygon mainnet 00:52:37.559 --> 00:52:40.370 align:start position:0% on ethereum mainnet polygon mainnet optimism<00:52:38.339> mainnet<00:52:38.880> arbitrim<00:52:39.780> mainnet<00:52:40.200> as 00:52:40.370 --> 00:52:40.380 align:start position:0% optimism mainnet arbitrim mainnet as 00:52:40.380 --> 00:52:41.930 align:start position:0% optimism mainnet arbitrim mainnet as well<00:52:40.559> as<00:52:40.619> test<00:52:40.859> nets<00:52:41.220> for<00:52:41.280> all<00:52:41.400> those<00:52:41.579> Chains 00:52:41.930 --> 00:52:41.940 align:start position:0% well as test nets for all those Chains 00:52:41.940 --> 00:52:43.970 align:start position:0% well as test nets for all those Chains It's<00:52:42.540> live<00:52:42.839> the<00:52:43.140> contracts<00:52:43.559> are<00:52:43.680> verified 00:52:43.970 --> 00:52:43.980 align:start position:0% It's live the contracts are verified 00:52:43.980 --> 00:52:46.190 align:start position:0% It's live the contracts are verified it's<00:52:44.700> fully<00:52:45.059> running<00:52:45.180> on<00:52:45.540> a<00:52:45.660> platform<00:52:45.900> that<00:52:46.079> I 00:52:46.190 --> 00:52:46.200 align:start position:0% it's fully running on a platform that I 00:52:46.200 --> 00:52:48.230 align:start position:0% it's fully running on a platform that I built<00:52:46.440> called<00:52:46.559> decent 00:52:48.230 --> 00:52:48.240 align:start position:0% built called decent 00:52:48.240 --> 00:52:49.910 align:start position:0% built called decent um and<00:52:48.960> so<00:52:49.079> what<00:52:49.260> I'd<00:52:49.380> like<00:52:49.500> to<00:52:49.619> ask<00:52:49.740> the 00:52:49.910 --> 00:52:49.920 align:start position:0% um and so what I'd like to ask the 00:52:49.920 --> 00:52:51.950 align:start position:0% um and so what I'd like to ask the community<00:52:50.099> here<00:52:50.880> I'm<00:52:51.420> not<00:52:51.540> very<00:52:51.720> familiar 00:52:51.950 --> 00:52:51.960 align:start position:0% community here I'm not very familiar 00:52:51.960 --> 00:52:53.390 align:start position:0% community here I'm not very familiar with<00:52:52.140> the<00:52:52.260> IPS<00:52:52.500> I'm<00:52:52.740> not<00:52:52.920> really<00:52:53.040> familiar 00:52:53.390 --> 00:52:53.400 align:start position:0% with the IPS I'm not really familiar 00:52:53.400 --> 00:52:55.130 align:start position:0% with the IPS I'm not really familiar with<00:52:53.700> what<00:52:54.119> we<00:52:54.240> do<00:52:54.420> as<00:52:54.599> a<00:52:54.720> community<00:52:54.839> the 00:52:55.130 --> 00:52:55.140 align:start position:0% with what we do as a community the 00:52:55.140 --> 00:52:56.450 align:start position:0% with what we do as a community the formal<00:52:55.440> way<00:52:55.619> I'm<00:52:55.800> really<00:52:55.980> used<00:52:56.160> to<00:52:56.280> building 00:52:56.450 --> 00:52:56.460 align:start position:0% formal way I'm really used to building 00:52:56.460 --> 00:52:58.670 align:start position:0% formal way I'm really used to building with<00:52:56.760> the<00:52:57.000> musicians<00:52:57.420> on<00:52:57.540> the<00:52:57.660> ground<00:52:57.780> I<00:52:58.619> don't 00:52:58.670 --> 00:52:58.680 align:start position:0% with the musicians on the ground I don't 00:52:58.680 --> 00:53:00.770 align:start position:0% with the musicians on the ground I don't know<00:52:58.800> if<00:52:58.859> we<00:52:59.040> need<00:52:59.099> an<00:52:59.280> EIP<00:52:59.579> for<00:52:59.940> like<00:53:00.420> proper 00:53:00.770 --> 00:53:00.780 align:start position:0% know if we need an EIP for like proper 00:53:00.780 --> 00:53:02.809 align:start position:0% know if we need an EIP for like proper music<00:53:00.960> metadata<00:53:01.440> for<00:53:01.619> us<00:53:01.740> to<00:53:01.800> get<00:53:01.920> aligned<00:53:02.280> I 00:53:02.809 --> 00:53:02.819 align:start position:0% music metadata for us to get aligned I 00:53:02.819 --> 00:53:04.069 align:start position:0% music metadata for us to get aligned I don't<00:53:02.880> know<00:53:03.000> if<00:53:03.059> we<00:53:03.240> just<00:53:03.359> need<00:53:03.480> to<00:53:03.660> talk<00:53:03.839> with 00:53:04.069 --> 00:53:04.079 align:start position:0% don't know if we just need to talk with 00:53:04.079 --> 00:53:06.589 align:start position:0% don't know if we just need to talk with the<00:53:04.260> Zoras<00:53:04.619> to<00:53:04.920> properly<00:53:05.280> plug<00:53:05.520> in<00:53:05.760> the<00:53:06.480> music 00:53:06.589 --> 00:53:06.599 align:start position:0% the Zoras to properly plug in the music 00:53:06.599 --> 00:53:09.109 align:start position:0% the Zoras to properly plug in the music metadata<00:53:07.319> render<00:53:07.740> into<00:53:08.099> the<00:53:08.339> Zora<00:53:08.700> stack<00:53:08.940> so 00:53:09.109 --> 00:53:09.119 align:start position:0% metadata render into the Zora stack so 00:53:09.119 --> 00:53:11.030 align:start position:0% metadata render into the Zora stack so that<00:53:09.180> musicians<00:53:09.660> can<00:53:09.780> use<00:53:09.900> it<00:53:10.079> maybe<00:53:10.800> it's 00:53:11.030 --> 00:53:11.040 align:start position:0% that musicians can use it maybe it's 00:53:11.040 --> 00:53:13.069 align:start position:0% that musicians can use it maybe it's just<00:53:11.220> me<00:53:11.339> writing<00:53:11.700> an<00:53:11.760> EIP<00:53:12.059> with<00:53:12.420> Hi-Fi<00:53:12.660> labs 00:53:13.069 --> 00:53:13.079 align:start position:0% just me writing an EIP with Hi-Fi labs 00:53:13.079 --> 00:53:14.630 align:start position:0% just me writing an EIP with Hi-Fi labs and<00:53:13.140> getting<00:53:13.319> it<00:53:13.440> plugged<00:53:13.740> in<00:53:13.800> there<00:53:13.980> there's 00:53:14.630 --> 00:53:14.640 align:start position:0% and getting it plugged in there there's 00:53:14.640 --> 00:53:16.130 align:start position:0% and getting it plugged in there there's a<00:53:14.819> lot<00:53:14.880> of<00:53:15.000> different<00:53:15.119> ways<00:53:15.420> we<00:53:15.540> can<00:53:15.660> propagate 00:53:16.130 --> 00:53:16.140 align:start position:0% a lot of different ways we can propagate 00:53:16.140 --> 00:53:18.710 align:start position:0% a lot of different ways we can propagate this<00:53:16.319> meme<00:53:16.500> out<00:53:16.859> into<00:53:17.040> the<00:53:17.220> ecosystem<00:53:17.660> I<00:53:18.660> don't 00:53:18.710 --> 00:53:18.720 align:start position:0% this meme out into the ecosystem I don't 00:53:18.720 --> 00:53:19.970 align:start position:0% this meme out into the ecosystem I don't really<00:53:18.900> know<00:53:19.020> what<00:53:19.200> to<00:53:19.319> do<00:53:19.440> and<00:53:19.559> I'm<00:53:19.740> not<00:53:19.800> going 00:53:19.970 --> 00:53:19.980 align:start position:0% really know what to do and I'm not going 00:53:19.980 --> 00:53:21.349 align:start position:0% really know what to do and I'm not going to<00:53:20.040> claim<00:53:20.280> that<00:53:20.400> I'm<00:53:20.579> like<00:53:20.760> the<00:53:20.940> king<00:53:21.059> of<00:53:21.240> all 00:53:21.349 --> 00:53:21.359 align:start position:0% to claim that I'm like the king of all 00:53:21.359 --> 00:53:23.630 align:start position:0% to claim that I'm like the king of all this<00:53:21.540> I<00:53:22.319> just<00:53:22.500> would<00:53:22.980> like<00:53:23.160> to<00:53:23.339> have<00:53:23.460> the 00:53:23.630 --> 00:53:23.640 align:start position:0% this I just would like to have the 00:53:23.640 --> 00:53:25.250 align:start position:0% this I just would like to have the conversation<00:53:24.059> more 00:53:25.250 --> 00:53:25.260 align:start position:0% conversation more 00:53:25.260 --> 00:53:26.690 align:start position:0% conversation more um<00:53:25.319> and<00:53:25.440> so<00:53:25.619> I'd<00:53:25.740> like<00:53:25.920> to<00:53:26.040> ask<00:53:26.160> for<00:53:26.400> help<00:53:26.520> in 00:53:26.690 --> 00:53:26.700 align:start position:0% um and so I'd like to ask for help in 00:53:26.700 --> 00:53:28.549 align:start position:0% um and so I'd like to ask for help in propagating<00:53:27.180> these<00:53:27.420> music<00:53:27.540> metadata<00:53:28.140> memes 00:53:28.549 --> 00:53:28.559 align:start position:0% propagating these music metadata memes 00:53:28.559 --> 00:53:31.250 align:start position:0% propagating these music metadata memes so<00:53:29.160> we<00:53:29.400> can<00:53:29.520> help<00:53:29.640> musicians<00:53:30.359> adopt<00:53:31.200> this 00:53:31.250 --> 00:53:31.260 align:start position:0% so we can help musicians adopt this 00:53:31.260 --> 00:53:33.770 align:start position:0% so we can help musicians adopt this technology<00:53:31.740> so<00:53:32.579> that<00:53:32.819> musicians<00:53:33.420> can<00:53:33.540> start 00:53:33.770 --> 00:53:33.780 align:start position:0% technology so that musicians can start 00:53:33.780 --> 00:53:36.829 align:start position:0% technology so that musicians can start leveraging<00:53:34.200> these<00:53:34.380> web3<00:53:34.800> rails<00:53:35.220> that<00:53:35.520> make<00:53:35.760> us 00:53:36.829 --> 00:53:36.839 align:start position:0% leveraging these web3 rails that make us 00:53:36.839 --> 00:53:38.630 align:start position:0% leveraging these web3 rails that make us and<00:53:37.380> the<00:53:37.559> technology<00:53:37.859> that<00:53:38.099> we<00:53:38.220> love<00:53:38.339> so 00:53:38.630 --> 00:53:38.640 align:start position:0% and the technology that we love so 00:53:38.640 --> 00:53:40.730 align:start position:0% and the technology that we love so powerful<00:53:39.000> and<00:53:39.240> groundbreaking<00:53:39.780> and<00:53:40.319> like 00:53:40.730 --> 00:53:40.740 align:start position:0% powerful and groundbreaking and like 00:53:40.740 --> 00:53:42.589 align:start position:0% powerful and groundbreaking and like fundamentally<00:53:41.339> changing<00:53:41.819> the<00:53:42.059> world<00:53:42.180> that<00:53:42.480> we 00:53:42.589 --> 00:53:42.599 align:start position:0% fundamentally changing the world that we 00:53:42.599 --> 00:53:44.150 align:start position:0% fundamentally changing the world that we know<00:53:42.660> and<00:53:42.839> love 00:53:44.150 --> 00:53:44.160 align:start position:0% know and love 00:53:44.160 --> 00:53:46.430 align:start position:0% know and love that's<00:53:44.579> it<00:53:44.700> Viva<00:53:45.119> La<00:53:45.240> Musica<00:53:45.720> these<00:53:46.260> are<00:53:46.319> all 00:53:46.430 --> 00:53:46.440 align:start position:0% that's it Viva La Musica these are all 00:53:46.440 --> 00:53:48.530 align:start position:0% that's it Viva La Musica these are all the<00:53:46.559> music<00:53:46.680> nfts<00:53:47.400> that<00:53:47.700> I<00:53:47.819> showed<00:53:48.180> throughout 00:53:48.530 --> 00:53:48.540 align:start position:0% the music nfts that I showed throughout 00:53:48.540 --> 00:53:50.270 align:start position:0% the music nfts that I showed throughout and<00:53:49.200> then<00:53:49.260> these<00:53:49.500> are<00:53:49.619> a<00:53:49.680> lot<00:53:49.800> of<00:53:49.859> musicians 00:53:50.270 --> 00:53:50.280 align:start position:0% and then these are a lot of musicians 00:53:50.280 --> 00:53:52.730 align:start position:0% and then these are a lot of musicians that<00:53:50.460> are<00:53:50.579> based<00:53:50.880> in<00:53:51.119> Argentina<00:53:51.660> and<00:53:52.200> Buenos 00:53:52.730 --> 00:53:52.740 align:start position:0% that are based in Argentina and Buenos 00:53:52.740 --> 00:53:55.010 align:start position:0% that are based in Argentina and Buenos Aires<00:53:53.160> in<00:53:53.760> Argentina<00:53:54.180> as<00:53:54.359> well<00:53:54.480> as<00:53:54.599> Colombia 00:53:55.010 --> 00:53:55.020 align:start position:0% Aires in Argentina as well as Colombia 00:53:55.020 --> 00:53:56.809 align:start position:0% Aires in Argentina as well as Colombia that<00:53:55.500> I<00:53:55.619> work<00:53:55.740> with<00:53:55.859> on<00:53:56.040> a<00:53:56.160> regular<00:53:56.339> basis<00:53:56.640> and 00:53:56.809 --> 00:53:56.819 align:start position:0% that I work with on a regular basis and 00:53:56.819 --> 00:53:58.430 align:start position:0% that I work with on a regular basis and so<00:53:56.940> if<00:53:57.059> you<00:53:57.180> want<00:53:57.300> to<00:53:57.420> talk<00:53:57.540> to<00:53:57.780> some<00:53:57.900> musicians 00:53:58.430 --> 00:53:58.440 align:start position:0% so if you want to talk to some musicians 00:53:58.440 --> 00:54:00.650 align:start position:0% so if you want to talk to some musicians that<00:53:58.980> are<00:53:59.099> based<00:53:59.339> here<00:53:59.400> in<00:53:59.579> Latin<00:53:59.880> America<00:54:00.000> and 00:54:00.650 --> 00:54:00.660 align:start position:0% that are based here in Latin America and 00:54:00.660 --> 00:54:01.910 align:start position:0% that are based here in Latin America and you<00:54:00.780> want<00:54:00.839> to<00:54:00.960> like<00:54:01.020> get<00:54:01.200> their<00:54:01.380> thoughts<00:54:01.740> or 00:54:01.910 --> 00:54:01.920 align:start position:0% you want to like get their thoughts or 00:54:01.920 --> 00:54:03.530 align:start position:0% you want to like get their thoughts or help<00:54:02.099> them<00:54:02.280> out<00:54:02.460> or<00:54:02.760> talk<00:54:03.000> to<00:54:03.119> them<00:54:03.240> about<00:54:03.359> the 00:54:03.530 --> 00:54:03.540 align:start position:0% help them out or talk to them about the 00:54:03.540 --> 00:54:05.270 align:start position:0% help them out or talk to them about the music<00:54:03.660> nfts<00:54:04.140> that<00:54:04.319> they're<00:54:04.440> making<00:54:04.619> I've 00:54:05.270 --> 00:54:05.280 align:start position:0% music nfts that they're making I've 00:54:05.280 --> 00:54:06.829 align:start position:0% music nfts that they're making I've attached<00:54:05.640> all<00:54:05.760> their<00:54:05.880> Twitter<00:54:06.059> handles<00:54:06.420> above 00:54:06.829 --> 00:54:06.839 align:start position:0% attached all their Twitter handles above 00:54:06.839 --> 00:54:08.750 align:start position:0% attached all their Twitter handles above so<00:54:07.440> please<00:54:07.619> reach<00:54:07.980> out<00:54:08.040> to<00:54:08.220> them<00:54:08.339> they<00:54:08.520> are<00:54:08.700> the 00:54:08.750 --> 00:54:08.760 align:start position:0% so please reach out to them they are the 00:54:08.760 --> 00:54:09.970 align:start position:0% so please reach out to them they are the people<00:54:08.880> that<00:54:09.059> are<00:54:09.180> on<00:54:09.240> the<00:54:09.359> ground<00:54:09.480> doing<00:54:09.720> this 00:54:09.970 --> 00:54:09.980 align:start position:0% people that are on the ground doing this 00:54:09.980 --> 00:54:13.010 align:start position:0% people that are on the ground doing this I<00:54:10.980> am<00:54:11.160> just<00:54:11.520> some<00:54:11.880> random<00:54:12.180> engineer<00:54:12.540> that's<00:54:12.780> up 00:54:13.010 --> 00:54:13.020 align:start position:0% I am just some random engineer that's up 00:54:13.020 --> 00:54:15.049 align:start position:0% I am just some random engineer that's up here<00:54:13.200> talking<00:54:13.380> to<00:54:13.619> y'all<00:54:13.800> so<00:54:14.280> uh<00:54:14.640> with<00:54:14.880> that 00:54:15.049 --> 00:54:15.059 align:start position:0% here talking to y'all so uh with that 00:54:15.059 --> 00:54:17.270 align:start position:0% here talking to y'all so uh with that we've<00:54:15.900> still<00:54:16.020> got<00:54:16.200> 10<00:54:16.440> minutes<00:54:16.619> so<00:54:16.920> I<00:54:17.040> kind<00:54:17.220> of 00:54:17.270 --> 00:54:17.280 align:start position:0% we've still got 10 minutes so I kind of 00:54:17.280 --> 00:54:19.190 align:start position:0% we've still got 10 minutes so I kind of zoomed<00:54:17.579> through<00:54:17.700> that<00:54:17.940> I<00:54:18.660> believe<00:54:18.780> the<00:54:19.020> rest 00:54:19.190 --> 00:54:19.200 align:start position:0% zoomed through that I believe the rest 00:54:19.200 --> 00:54:20.870 align:start position:0% zoomed through that I believe the rest of<00:54:19.319> the<00:54:19.380> time<00:54:19.500> open<00:54:19.680> to<00:54:19.980> any<00:54:20.160> questions<00:54:20.460> from 00:54:20.870 --> 00:54:20.880 align:start position:0% of the time open to any questions from 00:54:20.880 --> 00:54:22.430 align:start position:0% of the time open to any questions from the<00:54:21.059> community 00:54:22.430 --> 00:54:22.440 align:start position:0% the community 00:54:22.440 --> 00:54:24.950 align:start position:0% the community thank<00:54:22.980> you<00:54:23.099> sweet<00:54:23.339> man<00:54:23.520> hand<00:54:23.819> of<00:54:24.059> applause 00:54:24.950 --> 00:54:24.960 align:start position:0% thank you sweet man hand of applause 00:54:24.960 --> 00:54:29.089 align:start position:0% thank you sweet man hand of applause [Applause] 00:54:29.089 --> 00:54:29.099 align:start position:0% [Applause] 00:54:29.099 --> 00:54:31.490 align:start position:0% [Applause] so<00:54:29.760> do<00:54:30.059> we<00:54:30.180> have<00:54:30.300> any<00:54:30.540> questions<00:54:30.780> in<00:54:31.380> the 00:54:31.490 --> 00:54:31.500 align:start position:0% so do we have any questions in the 00:54:31.500 --> 00:54:33.049 align:start position:0% so do we have any questions in the audience 00:54:33.049 --> 00:54:33.059 align:start position:0% audience 00:54:33.059 --> 00:54:34.849 align:start position:0% audience raise<00:54:33.540> your<00:54:33.780> hand<00:54:33.960> if<00:54:34.260> you<00:54:34.440> have<00:54:34.559> any 00:54:34.849 --> 00:54:34.859 align:start position:0% raise your hand if you have any 00:54:34.859 --> 00:54:35.990 align:start position:0% raise your hand if you have any questions<00:54:35.040> yes 00:54:35.990 --> 00:54:36.000 align:start position:0% questions yes 00:54:36.000 --> 00:54:37.670 align:start position:0% questions yes hi 00:54:37.670 --> 00:54:37.680 align:start position:0% hi 00:54:37.680 --> 00:54:40.670 align:start position:0% hi um<00:54:37.740> I<00:54:38.099> was<00:54:38.220> wondering<00:54:38.460> like<00:54:38.819> uh<00:54:39.300> how<00:54:40.140> what<00:54:40.500> was 00:54:40.670 --> 00:54:40.680 align:start position:0% um I was wondering like uh how what was 00:54:40.680 --> 00:54:43.190 align:start position:0% um I was wondering like uh how what was your<00:54:40.920> process<00:54:41.339> in<00:54:41.579> navigating<00:54:42.000> to<00:54:42.480> the<00:54:42.839> EIP 00:54:43.190 --> 00:54:43.200 align:start position:0% your process in navigating to the EIP 00:54:43.200 --> 00:54:45.230 align:start position:0% your process in navigating to the EIP like<00:54:43.619> how<00:54:43.800> did<00:54:43.980> you<00:54:44.099> gather<00:54:44.339> information 00:54:45.230 --> 00:54:45.240 align:start position:0% like how did you gather information 00:54:45.240 --> 00:54:48.049 align:start position:0% like how did you gather information about<00:54:46.200> like<00:54:46.559> music<00:54:46.920> metadata<00:54:47.640> is<00:54:47.760> a<00:54:47.940> very 00:54:48.049 --> 00:54:48.059 align:start position:0% about like music metadata is a very 00:54:48.059 --> 00:54:50.750 align:start position:0% about like music metadata is a very complex<00:54:48.420> structure<00:54:49.200> right<00:54:49.380> like<00:54:49.740> uh<00:54:50.579> and 00:54:50.750 --> 00:54:50.760 align:start position:0% complex structure right like uh and 00:54:50.760 --> 00:54:53.210 align:start position:0% complex structure right like uh and there's<00:54:51.200> not<00:54:52.200> having<00:54:52.440> consensus<00:54:52.980> over 00:54:53.210 --> 00:54:53.220 align:start position:0% there's not having consensus over 00:54:53.220 --> 00:54:54.829 align:start position:0% there's not having consensus over metadata<00:54:53.940> just<00:54:54.180> sounds<00:54:54.300> like<00:54:54.540> a<00:54:54.720> classic 00:54:54.829 --> 00:54:54.839 align:start position:0% metadata just sounds like a classic 00:54:54.839 --> 00:54:58.010 align:start position:0% metadata just sounds like a classic music<00:54:55.140> industry<00:54:55.680> to<00:54:56.280> be<00:54:56.400> honest<00:54:56.880> so<00:54:57.780> I<00:54:57.960> was 00:54:58.010 --> 00:54:58.020 align:start position:0% music industry to be honest so I was 00:54:58.020 --> 00:54:59.329 align:start position:0% music industry to be honest so I was wondering<00:54:58.260> like<00:54:58.380> how<00:54:58.619> was<00:54:58.740> your<00:54:58.920> process<00:54:59.160> to 00:54:59.329 --> 00:54:59.339 align:start position:0% wondering like how was your process to 00:54:59.339 --> 00:55:01.910 align:start position:0% wondering like how was your process to getting<00:54:59.579> to<00:54:59.760> the<00:55:00.000> the<00:55:00.260> stage<00:55:01.260> and<00:55:01.440> the<00:55:01.680> EIP 00:55:01.910 --> 00:55:01.920 align:start position:0% getting to the the stage and the EIP 00:55:01.920 --> 00:55:04.490 align:start position:0% getting to the the stage and the EIP generally<00:55:02.520> to<00:55:03.300> be<00:55:03.420> clear<00:55:03.540> there<00:55:03.839> is<00:55:03.960> no<00:55:04.140> EIP 00:55:04.490 --> 00:55:04.500 align:start position:0% generally to be clear there is no EIP 00:55:04.500 --> 00:55:06.349 align:start position:0% generally to be clear there is no EIP right<00:55:04.859> now<00:55:05.040> this<00:55:05.520> is<00:55:05.640> this<00:55:05.880> is<00:55:06.000> a<00:55:06.119> bunch<00:55:06.240> of 00:55:06.349 --> 00:55:06.359 align:start position:0% right now this is this is a bunch of 00:55:06.359 --> 00:55:08.270 align:start position:0% right now this is this is a bunch of blank<00:55:06.660> data<00:55:06.960> I<00:55:07.140> copied<00:55:07.380> EI<00:55:07.800> I<00:55:08.099> took<00:55:08.220> a 00:55:08.270 --> 00:55:08.280 align:start position:0% blank data I copied EI I took a 00:55:08.280 --> 00:55:10.670 align:start position:0% blank data I copied EI I took a screenshot<00:55:08.579> of<00:55:08.780> eip721<00:55:09.780> and<00:55:10.140> I<00:55:10.260> blanked<00:55:10.619> out 00:55:10.670 --> 00:55:10.680 align:start position:0% screenshot of eip721 and I blanked out 00:55:10.680 --> 00:55:12.650 align:start position:0% screenshot of eip721 and I blanked out the<00:55:10.859> data<00:55:11.099> to<00:55:11.220> just<00:55:11.460> kind<00:55:11.640> of<00:55:11.760> like<00:55:11.940> put<00:55:12.540> the 00:55:12.650 --> 00:55:12.660 align:start position:0% the data to just kind of like put the 00:55:12.660 --> 00:55:13.910 align:start position:0% the data to just kind of like put the meme<00:55:12.780> in<00:55:13.020> your<00:55:13.140> head<00:55:13.260> as<00:55:13.380> something<00:55:13.559> that<00:55:13.800> we 00:55:13.910 --> 00:55:13.920 align:start position:0% meme in your head as something that we 00:55:13.920 --> 00:55:16.490 align:start position:0% meme in your head as something that we can<00:55:14.040> do<00:55:14.220> I<00:55:14.940> don't<00:55:15.059> question<00:55:15.720> back<00:55:16.020> to<00:55:16.200> you<00:55:16.319> do 00:55:16.490 --> 00:55:16.500 align:start position:0% can do I don't question back to you do 00:55:16.500 --> 00:55:17.690 align:start position:0% can do I don't question back to you do you<00:55:16.619> think<00:55:16.740> this<00:55:16.920> is<00:55:17.040> something<00:55:17.220> we<00:55:17.400> could<00:55:17.520> do 00:55:17.690 --> 00:55:17.700 align:start position:0% you think this is something we could do 00:55:17.700 --> 00:55:19.670 align:start position:0% you think this is something we could do with<00:55:17.819> an<00:55:17.940> EIP<00:55:18.240> or<00:55:18.720> does<00:55:18.900> this<00:55:19.079> feel<00:55:19.319> like<00:55:19.500> you 00:55:19.670 --> 00:55:19.680 align:start position:0% with an EIP or does this feel like you 00:55:19.680 --> 00:55:21.109 align:start position:0% with an EIP or does this feel like you say<00:55:19.859> like<00:55:20.040> the<00:55:20.220> music<00:55:20.339> industry<00:55:20.760> is<00:55:20.880> too 00:55:21.109 --> 00:55:21.119 align:start position:0% say like the music industry is too 00:55:21.119 --> 00:55:23.089 align:start position:0% say like the music industry is too decentralized<00:55:21.839> for<00:55:22.380> us<00:55:22.500> to<00:55:22.619> come<00:55:22.740> up<00:55:22.859> with<00:55:22.980> an 00:55:23.089 --> 00:55:23.099 align:start position:0% decentralized for us to come up with an 00:55:23.099 --> 00:55:26.270 align:start position:0% decentralized for us to come up with an eip4<00:55:23.640> music<00:55:23.940> metadata<00:55:24.480> standard 00:55:26.270 --> 00:55:26.280 align:start position:0% eip4 music metadata standard 00:55:26.280 --> 00:55:29.450 align:start position:0% eip4 music metadata standard I<00:55:26.760> think<00:55:26.940> yes<00:55:27.180> uh<00:55:28.079> there<00:55:28.500> is<00:55:28.680> one<00:55:28.920> part<00:55:29.099> that's 00:55:29.450 --> 00:55:29.460 align:start position:0% I think yes uh there is one part that's 00:55:29.460 --> 00:55:32.990 align:start position:0% I think yes uh there is one part that's probably<00:55:30.020> up<00:55:31.020> for<00:55:31.260> uh<00:55:32.160> like<00:55:32.400> off<00:55:32.579> Chain<00:55:32.819> versus 00:55:32.990 --> 00:55:33.000 align:start position:0% probably up for uh like off Chain versus 00:55:33.000 --> 00:55:34.490 align:start position:0% probably up for uh like off Chain versus own<00:55:33.300> chain<00:55:33.540> I<00:55:33.720> think<00:55:33.839> if<00:55:34.020> you<00:55:34.140> have<00:55:34.319> that 00:55:34.490 --> 00:55:34.500 align:start position:0% own chain I think if you have that 00:55:34.500 --> 00:55:37.069 align:start position:0% own chain I think if you have that perimeter<00:55:34.980> very<00:55:35.280> clearly<00:55:35.579> uh<00:55:36.540> I<00:55:36.720> think<00:55:36.780> this 00:55:37.069 --> 00:55:37.079 align:start position:0% perimeter very clearly uh I think this 00:55:37.079 --> 00:55:40.010 align:start position:0% perimeter very clearly uh I think this is<00:55:37.200> this<00:55:37.619> is<00:55:37.800> exciting<00:55:38.220> yeah<00:55:39.119> in<00:55:39.660> in<00:55:39.839> an 00:55:40.010 --> 00:55:40.020 align:start position:0% is this is exciting yeah in in an 00:55:40.020 --> 00:55:41.510 align:start position:0% is this is exciting yeah in in an attribute<00:55:40.319> I<00:55:40.500> didn't<00:55:40.619> talk<00:55:40.800> about<00:55:40.920> all<00:55:41.339> of 00:55:41.510 --> 00:55:41.520 align:start position:0% attribute I didn't talk about all of 00:55:41.520 --> 00:55:44.870 align:start position:0% attribute I didn't talk about all of these<00:55:41.819> uh<00:55:42.240> all<00:55:42.780> of<00:55:42.900> these<00:55:43.079> decent<00:55:43.380> nfts<00:55:43.920> 100<00:55:44.400> of 00:55:44.870 --> 00:55:44.880 align:start position:0% these uh all of these decent nfts 100 of 00:55:44.880 --> 00:55:47.210 align:start position:0% these uh all of these decent nfts 100 of them<00:55:45.000> metadata<00:55:45.420> is<00:55:45.540> on<00:55:45.780> chain<00:55:46.020> so<00:55:46.800> one<00:55:47.040> of<00:55:47.160> the 00:55:47.210 --> 00:55:47.220 align:start position:0% them metadata is on chain so one of the 00:55:47.220 --> 00:55:48.530 align:start position:0% them metadata is on chain so one of the awesome<00:55:47.339> Parts<00:55:47.579> about<00:55:47.760> l2s<00:55:48.300> is<00:55:48.420> it's 00:55:48.530 --> 00:55:48.540 align:start position:0% awesome Parts about l2s is it's 00:55:48.540 --> 00:55:50.450 align:start position:0% awesome Parts about l2s is it's incredibly<00:55:49.020> cheap<00:55:49.319> to<00:55:49.619> store<00:55:49.740> all<00:55:50.040> metadata 00:55:50.450 --> 00:55:50.460 align:start position:0% incredibly cheap to store all metadata 00:55:50.460 --> 00:55:52.730 align:start position:0% incredibly cheap to store all metadata on<00:55:50.640> chain<00:55:50.880> and<00:55:51.480> so<00:55:51.599> we<00:55:51.720> can<00:55:51.839> store<00:55:52.020> that<00:55:52.319> entire 00:55:52.730 --> 00:55:52.740 align:start position:0% on chain and so we can store that entire 00:55:52.740 --> 00:55:55.250 align:start position:0% on chain and so we can store that entire music<00:55:53.040> metadata<00:55:53.700> on<00:55:54.240> chain<00:55:54.420> for<00:55:54.780> less<00:55:54.900> than<00:55:55.079> a 00:55:55.250 --> 00:55:55.260 align:start position:0% music metadata on chain for less than a 00:55:55.260 --> 00:55:57.950 align:start position:0% music metadata on chain for less than a penny<00:55:55.559> and<00:55:56.280> so<00:55:56.520> musicians<00:55:57.359> that<00:55:57.540> are<00:55:57.660> based<00:55:57.900> in 00:55:57.950 --> 00:55:57.960 align:start position:0% penny and so musicians that are based in 00:55:57.960 --> 00:55:59.990 align:start position:0% penny and so musicians that are based in Latin<00:55:58.260> America<00:55:58.380> cannot<00:55:58.980> afford<00:55:59.400> to<00:55:59.819> do 00:55:59.990 --> 00:56:00.000 align:start position:0% Latin America cannot afford to do 00:56:00.000 --> 00:56:02.329 align:start position:0% Latin America cannot afford to do transactions<00:56:00.480> on<00:56:00.599> each<00:56:00.780> mainnet 00:56:02.329 --> 00:56:02.339 align:start position:0% transactions on each mainnet 00:56:02.339 --> 00:56:03.950 align:start position:0% transactions on each mainnet um<00:56:02.400> but<00:56:02.640> by<00:56:02.819> offering<00:56:03.119> them<00:56:03.300> these<00:56:03.480> rails<00:56:03.839> to 00:56:03.950 --> 00:56:03.960 align:start position:0% um but by offering them these rails to 00:56:03.960 --> 00:56:05.990 align:start position:0% um but by offering them these rails to be<00:56:04.079> able<00:56:04.140> to<00:56:04.319> create<00:56:04.500> music<00:56:04.859> metadata<00:56:05.520> we<00:56:05.880> can 00:56:05.990 --> 00:56:06.000 align:start position:0% be able to create music metadata we can 00:56:06.000 --> 00:56:07.370 align:start position:0% be able to create music metadata we can also<00:56:06.240> offer<00:56:06.480> them<00:56:06.540> the<00:56:06.720> opportunity<00:56:07.020> to<00:56:07.200> put 00:56:07.370 --> 00:56:07.380 align:start position:0% also offer them the opportunity to put 00:56:07.380 --> 00:56:08.870 align:start position:0% also offer them the opportunity to put it<00:56:07.500> fully<00:56:07.740> on<00:56:07.859> chain<00:56:08.099> so<00:56:08.339> that<00:56:08.520> there's<00:56:08.640> no 00:56:08.870 --> 00:56:08.880 align:start position:0% it fully on chain so that there's no 00:56:08.880 --> 00:56:11.569 align:start position:0% it fully on chain so that there's no trust<00:56:09.119> needed<00:56:09.540> in<00:56:10.200> apis<00:56:10.920> like<00:56:11.160> what<00:56:11.400> sound 00:56:11.569 --> 00:56:11.579 align:start position:0% trust needed in apis like what sound 00:56:11.579 --> 00:56:14.870 align:start position:0% trust needed in apis like what sound uses<00:56:12.119> or<00:56:12.780> even<00:56:13.440> like<00:56:13.800> the<00:56:14.099> delay<00:56:14.339> you<00:56:14.520> get<00:56:14.640> by 00:56:14.870 --> 00:56:14.880 align:start position:0% uses or even like the delay you get by 00:56:14.880 --> 00:56:16.670 align:start position:0% uses or even like the delay you get by uploading<00:56:15.240> to<00:56:15.359> ipfs<00:56:15.839> if<00:56:16.020> you're<00:56:16.140> not<00:56:16.260> using<00:56:16.500> a 00:56:16.670 --> 00:56:16.680 align:start position:0% uploading to ipfs if you're not using a 00:56:16.680 --> 00:56:18.109 align:start position:0% uploading to ipfs if you're not using a dedicated<00:56:16.920> Gateway<00:56:17.339> when<00:56:17.579> you<00:56:17.700> store<00:56:17.880> it<00:56:18.000> all 00:56:18.109 --> 00:56:18.119 align:start position:0% dedicated Gateway when you store it all 00:56:18.119 --> 00:56:19.250 align:start position:0% dedicated Gateway when you store it all on<00:56:18.240> chain<00:56:18.420> you<00:56:18.660> get<00:56:18.780> that<00:56:18.960> instant 00:56:19.250 --> 00:56:19.260 align:start position:0% on chain you get that instant 00:56:19.260 --> 00:56:20.930 align:start position:0% on chain you get that instant availability<00:56:19.619> that<00:56:19.920> you<00:56:20.040> get<00:56:20.160> on<00:56:20.339> optimism<00:56:20.700> of 00:56:20.930 --> 00:56:20.940 align:start position:0% availability that you get on optimism of 00:56:20.940 --> 00:56:23.210 align:start position:0% availability that you get on optimism of a<00:56:21.119> trim<00:56:21.300> polygon<00:56:21.660> and<00:56:21.780> the<00:56:21.900> other<00:56:21.960> l2s 00:56:23.210 --> 00:56:23.220 align:start position:0% a trim polygon and the other l2s 00:56:23.220 --> 00:56:25.849 align:start position:0% a trim polygon and the other l2s thank<00:56:23.700> you<00:56:23.819> more<00:56:24.480> we<00:56:25.140> have<00:56:25.260> more<00:56:25.500> time<00:56:25.680> for 00:56:25.849 --> 00:56:25.859 align:start position:0% thank you more we have more time for 00:56:25.859 --> 00:56:30.650 align:start position:0% thank you more we have more time for questions<00:56:26.160> if<00:56:26.760> there<00:56:26.940> are<00:56:27.119> yes 00:56:30.650 --> 00:56:30.660 align:start position:0% 00:56:30.660 --> 00:56:32.390 align:start position:0% um<00:56:30.720> it<00:56:30.900> wasn't<00:56:31.140> clear<00:56:31.440> do<00:56:31.859> you<00:56:32.040> want<00:56:32.160> to<00:56:32.280> write 00:56:32.390 --> 00:56:32.400 align:start position:0% um it wasn't clear do you want to write 00:56:32.400 --> 00:56:34.609 align:start position:0% um it wasn't clear do you want to write an<00:56:32.579> EIP<00:56:32.880> for<00:56:33.180> this<00:56:33.359> or<00:56:33.720> do<00:56:33.839> you<00:56:34.020> not<00:56:34.140> want<00:56:34.380> to<00:56:34.500> do 00:56:34.609 --> 00:56:34.619 align:start position:0% an EIP for this or do you not want to do 00:56:34.619 --> 00:56:36.770 align:start position:0% an EIP for this or do you not want to do it<00:56:34.740> I'm<00:56:35.280> very<00:56:35.460> open<00:56:35.640> to<00:56:35.880> it<00:56:36.059> I'm<00:56:36.300> I'm<00:56:36.480> here<00:56:36.660> in 00:56:36.770 --> 00:56:36.780 align:start position:0% it I'm very open to it I'm I'm here in 00:56:36.780 --> 00:56:38.930 align:start position:0% it I'm very open to it I'm I'm here in the<00:56:36.900> community<00:56:37.079> I<00:56:37.680> my<00:56:38.099> entire<00:56:38.280> life<00:56:38.460> is<00:56:38.700> music 00:56:38.930 --> 00:56:38.940 align:start position:0% the community I my entire life is music 00:56:38.940 --> 00:56:40.910 align:start position:0% the community I my entire life is music nfts<00:56:39.540> and<00:56:39.660> so<00:56:39.900> if<00:56:40.079> the<00:56:40.200> community<00:56:40.380> decides 00:56:40.910 --> 00:56:40.920 align:start position:0% nfts and so if the community decides 00:56:40.920 --> 00:56:43.970 align:start position:0% nfts and so if the community decides that<00:56:41.040> we<00:56:41.160> want<00:56:41.339> an<00:56:41.579> EIP<00:56:42.000> I'm<00:56:42.720> about<00:56:42.900> it 00:56:43.970 --> 00:56:43.980 align:start position:0% that we want an EIP I'm about it 00:56:43.980 --> 00:56:47.270 align:start position:0% that we want an EIP I'm about it um<00:56:44.099> I'm<00:56:44.579> I'm<00:56:44.819> very<00:56:45.059> much<00:56:45.240> of<00:56:45.420> the<00:56:45.599> belief<00:56:45.900> that 00:56:47.270 --> 00:56:47.280 align:start position:0% um I'm I'm very much of the belief that 00:56:47.280 --> 00:56:49.370 align:start position:0% um I'm I'm very much of the belief that I<00:56:47.700> don't<00:56:48.059> I<00:56:48.359> don't<00:56:48.480> want<00:56:48.599> to<00:56:48.720> say<00:56:48.839> like<00:56:49.020> this<00:56:49.319> is 00:56:49.370 --> 00:56:49.380 align:start position:0% I don't I don't want to say like this is 00:56:49.380 --> 00:56:51.349 align:start position:0% I don't I don't want to say like this is the<00:56:49.559> way<00:56:49.740> I<00:56:50.280> like<00:56:50.460> hearing<00:56:50.760> like<00:56:50.940> the<00:56:51.119> music 00:56:51.349 --> 00:56:51.359 align:start position:0% the way I like hearing like the music 00:56:51.359 --> 00:56:52.849 align:start position:0% the way I like hearing like the music metadata<00:56:51.839> standard<00:56:52.200> I<00:56:52.380> didn't<00:56:52.500> come<00:56:52.619> up<00:56:52.740> with 00:56:52.849 --> 00:56:52.859 align:start position:0% metadata standard I didn't come up with 00:56:52.859 --> 00:56:54.410 align:start position:0% metadata standard I didn't come up with that<00:56:53.040> that<00:56:53.220> came<00:56:53.460> out<00:56:53.579> a<00:56:53.700> catalog<00:56:54.059> and<00:56:54.300> I'm 00:56:54.410 --> 00:56:54.420 align:start position:0% that that came out a catalog and I'm 00:56:54.420 --> 00:56:55.910 align:start position:0% that that came out a catalog and I'm just<00:56:54.540> propagating<00:56:54.960> that<00:56:55.200> Meme<00:56:55.319> because<00:56:55.619> it's 00:56:55.910 --> 00:56:55.920 align:start position:0% just propagating that Meme because it's 00:56:55.920 --> 00:56:59.329 align:start position:0% just propagating that Meme because it's in<00:56:56.339> my<00:56:56.460> opinion<00:56:56.700> the<00:56:56.940> best<00:56:57.059> meme<00:56:57.300> yeah<00:56:57.980> no<00:56:58.980> I<00:56:59.160> I 00:56:59.329 --> 00:56:59.339 align:start position:0% in my opinion the best meme yeah no I I 00:56:59.339 --> 00:57:02.150 align:start position:0% in my opinion the best meme yeah no I I think<00:57:00.059> um<00:57:00.059> a<00:57:00.960> great<00:57:01.140> first<00:57:01.380> step<00:57:01.619> would<00:57:01.859> be<00:57:01.980> to 00:57:02.150 --> 00:57:02.160 align:start position:0% think um a great first step would be to 00:57:02.160 --> 00:57:03.710 align:start position:0% think um a great first step would be to public<00:57:02.460> like<00:57:02.819> it<00:57:02.940> seems<00:57:03.180> you've<00:57:03.359> done<00:57:03.480> a<00:57:03.660> lot 00:57:03.710 --> 00:57:03.720 align:start position:0% public like it seems you've done a lot 00:57:03.720 --> 00:57:05.510 align:start position:0% public like it seems you've done a lot of<00:57:03.839> research<00:57:04.140> to<00:57:04.440> publish<00:57:04.920> that<00:57:05.099> in<00:57:05.339> some 00:57:05.510 --> 00:57:05.520 align:start position:0% of research to publish that in some 00:57:05.520 --> 00:57:07.130 align:start position:0% of research to publish that in some written<00:57:06.000> form<00:57:06.180> maybe<00:57:06.480> in<00:57:06.660> The<00:57:06.780> ethereum 00:57:07.130 --> 00:57:07.140 align:start position:0% written form maybe in The ethereum 00:57:07.140 --> 00:57:10.069 align:start position:0% written form maybe in The ethereum Magicians<00:57:07.619> form<00:57:07.819> uh<00:57:08.819> to<00:57:08.940> just<00:57:09.180> kind<00:57:09.359> of<00:57:09.480> keep 00:57:10.069 --> 00:57:10.079 align:start position:0% Magicians form uh to just kind of keep 00:57:10.079 --> 00:57:12.470 align:start position:0% Magicians form uh to just kind of keep it<00:57:10.319> make<00:57:10.920> it<00:57:11.040> visible<00:57:11.400> and<00:57:11.760> someone<00:57:11.940> else<00:57:12.240> can 00:57:12.470 --> 00:57:12.480 align:start position:0% it make it visible and someone else can 00:57:12.480 --> 00:57:14.990 align:start position:0% it make it visible and someone else can then<00:57:12.720> maybe<00:57:12.960> pick<00:57:13.260> it<00:57:13.440> up<00:57:13.619> and<00:57:13.920> formalize<00:57:14.819> it 00:57:14.990 --> 00:57:15.000 align:start position:0% then maybe pick it up and formalize it 00:57:15.000 --> 00:57:16.490 align:start position:0% then maybe pick it up and formalize it and<00:57:15.180> they're<00:57:15.420> in<00:57:15.540> the<00:57:15.599> IP<00:57:15.839> that<00:57:16.020> would<00:57:16.140> be<00:57:16.260> very 00:57:16.490 --> 00:57:16.500 align:start position:0% and they're in the IP that would be very 00:57:16.500 --> 00:57:19.790 align:start position:0% and they're in the IP that would be very valuable<00:57:16.920> and<00:57:17.700> I<00:57:17.940> I<00:57:18.180> want<00:57:18.480> to<00:57:18.660> offer<00:57:19.079> a<00:57:19.380> counter 00:57:19.790 --> 00:57:19.800 align:start position:0% valuable and I I want to offer a counter 00:57:19.800 --> 00:57:22.910 align:start position:0% valuable and I I want to offer a counter I<00:57:20.099> don't<00:57:20.280> think<00:57:20.520> that<00:57:21.359> you 00:57:22.910 --> 00:57:22.920 align:start position:0% I don't think that you 00:57:22.920 --> 00:57:25.010 align:start position:0% I don't think that you specifying<00:57:23.880> something<00:57:24.119> and<00:57:24.359> standardizing 00:57:25.010 --> 00:57:25.020 align:start position:0% specifying something and standardizing 00:57:25.020 --> 00:57:27.290 align:start position:0% specifying something and standardizing something<00:57:25.200> would<00:57:25.740> be<00:57:25.920> like<00:57:26.160> imposing<00:57:26.940> your 00:57:27.290 --> 00:57:27.300 align:start position:0% something would be like imposing your 00:57:27.300 --> 00:57:28.670 align:start position:0% something would be like imposing your view<00:57:27.420> of<00:57:27.660> things<00:57:27.839> on<00:57:27.960> the<00:57:28.140> world<00:57:28.260> it's<00:57:28.559> just 00:57:28.670 --> 00:57:28.680 align:start position:0% view of things on the world it's just 00:57:28.680 --> 00:57:30.829 align:start position:0% view of things on the world it's just offering<00:57:29.099> an<00:57:29.280> option<00:57:29.579> right<00:57:29.819> and<00:57:30.480> whether 00:57:30.829 --> 00:57:30.839 align:start position:0% offering an option right and whether 00:57:30.839 --> 00:57:32.870 align:start position:0% offering an option right and whether that's<00:57:31.079> adopted<00:57:31.500> or<00:57:31.680> not<00:57:31.800> depends<00:57:32.220> on<00:57:32.339> on<00:57:32.579> the 00:57:32.870 --> 00:57:32.880 align:start position:0% that's adopted or not depends on on the 00:57:32.880 --> 00:57:35.870 align:start position:0% that's adopted or not depends on on the on<00:57:33.480> the<00:57:33.660> rest<00:57:33.839> like<00:57:34.260> you've<00:57:34.559> said<00:57:34.680> but<00:57:35.099> having 00:57:35.870 --> 00:57:35.880 align:start position:0% on the rest like you've said but having 00:57:35.880 --> 00:57:38.569 align:start position:0% on the rest like you've said but having an<00:57:36.180> option<00:57:36.480> that<00:57:36.900> is<00:57:37.079> uh<00:57:37.619> there<00:57:37.859> and<00:57:38.099> specified 00:57:38.569 --> 00:57:38.579 align:start position:0% an option that is uh there and specified 00:57:38.579 --> 00:57:41.390 align:start position:0% an option that is uh there and specified and<00:57:38.880> like<00:57:39.540> standardized<00:57:40.380> is<00:57:40.859> extremely 00:57:41.390 --> 00:57:41.400 align:start position:0% and like standardized is extremely 00:57:41.400 --> 00:57:44.150 align:start position:0% and like standardized is extremely powerful<00:57:41.819> and<00:57:42.180> I<00:57:42.300> don't<00:57:42.420> think<00:57:42.599> it's<00:57:43.160> imposing 00:57:44.150 --> 00:57:44.160 align:start position:0% powerful and I don't think it's imposing 00:57:44.160 --> 00:57:47.870 align:start position:0% powerful and I don't think it's imposing anything<00:57:44.339> in<00:57:44.700> any<00:57:44.819> way 00:57:47.870 --> 00:57:47.880 align:start position:0% 00:57:47.880 --> 00:57:49.190 align:start position:0% thank<00:57:48.240> you<00:57:48.420> do<00:57:48.599> you<00:57:48.780> want<00:57:48.839> to<00:57:48.960> take<00:57:49.020> more 00:57:49.190 --> 00:57:49.200 align:start position:0% thank you do you want to take more 00:57:49.200 --> 00:57:50.750 align:start position:0% thank you do you want to take more questions<00:57:49.380> we<00:57:49.740> have<00:57:49.859> more<00:57:49.980> time<00:57:50.220> love<00:57:50.579> to 00:57:50.750 --> 00:57:50.760 align:start position:0% questions we have more time love to 00:57:50.760 --> 00:57:54.470 align:start position:0% questions we have more time love to especially<00:57:51.180> if<00:57:51.300> it's<00:57:51.420> from<00:57:51.599> Dan 00:57:54.470 --> 00:57:54.480 align:start position:0% 00:57:54.480 --> 00:57:55.670 align:start position:0% hey 00:57:55.670 --> 00:57:55.680 align:start position:0% hey 00:57:55.680 --> 00:57:57.530 align:start position:0% hey um it's<00:57:56.099> quite<00:57:56.400> funny<00:57:56.640> because<00:57:57.059> obviously<00:57:57.420> I 00:57:57.530 --> 00:57:57.540 align:start position:0% um it's quite funny because obviously I 00:57:57.540 --> 00:57:58.549 align:start position:0% um it's quite funny because obviously I wrote<00:57:57.720> they<00:57:57.839> bought<00:57:58.020> a<00:57:58.200> music<00:57:58.319> report 00:57:58.549 --> 00:57:58.559 align:start position:0% wrote they bought a music report 00:57:58.559 --> 00:58:00.770 align:start position:0% wrote they bought a music report yesterday<00:57:58.980> they<00:57:59.819> came<00:58:00.000> out<00:58:00.119> on<00:58:00.300> this<00:58:00.480> subject 00:58:00.770 --> 00:58:00.780 align:start position:0% yesterday they came out on this subject 00:58:00.780 --> 00:58:02.450 align:start position:0% yesterday they came out on this subject have<00:58:01.200> you<00:58:01.319> not<00:58:01.440> read<00:58:01.559> it<00:58:01.680> yet<00:58:01.740> I<00:58:02.099> have<00:58:02.280> not 00:58:02.450 --> 00:58:02.460 align:start position:0% have you not read it yet I have not 00:58:02.460 --> 00:58:04.190 align:start position:0% have you not read it yet I have not interested<00:58:03.300> in<00:58:03.359> because<00:58:03.540> there's<00:58:03.780> definitely 00:58:04.190 --> 00:58:04.200 align:start position:0% interested in because there's definitely 00:58:04.200 --> 00:58:06.470 align:start position:0% interested in because there's definitely points<00:58:04.740> of<00:58:04.859> conflict<00:58:05.280> between<00:58:05.640> how<00:58:06.240> we're 00:58:06.470 --> 00:58:06.480 align:start position:0% points of conflict between how we're 00:58:06.480 --> 00:58:07.790 align:start position:0% points of conflict between how we're seeing<00:58:06.660> this 00:58:07.790 --> 00:58:07.800 align:start position:0% seeing this 00:58:07.800 --> 00:58:09.349 align:start position:0% seeing this um<00:58:07.859> and<00:58:08.220> for<00:58:08.520> me 00:58:09.349 --> 00:58:09.359 align:start position:0% um and for me 00:58:09.359 --> 00:58:11.809 align:start position:0% um and for me having<00:58:09.900> worked<00:58:10.380> like<00:58:10.740> the<00:58:10.980> whole<00:58:11.220> has<00:58:11.460> inside 00:58:11.809 --> 00:58:11.819 align:start position:0% having worked like the whole has inside 00:58:11.819 --> 00:58:13.549 align:start position:0% having worked like the whole has inside the<00:58:12.119> Beast<00:58:12.420> as<00:58:12.599> it<00:58:12.780> were 00:58:13.549 --> 00:58:13.559 align:start position:0% the Beast as it were 00:58:13.559 --> 00:58:14.569 align:start position:0% the Beast as it were um<00:58:13.619> one<00:58:13.800> of<00:58:13.859> the<00:58:13.920> biggest<00:58:13.980> issues<00:58:14.339> in<00:58:14.460> music 00:58:14.569 --> 00:58:14.579 align:start position:0% um one of the biggest issues in music 00:58:14.579 --> 00:58:16.490 align:start position:0% um one of the biggest issues in music industry<00:58:15.000> comes<00:58:15.599> around<00:58:15.720> multi-party 00:58:16.490 --> 00:58:16.500 align:start position:0% industry comes around multi-party 00:58:16.500 --> 00:58:18.950 align:start position:0% industry comes around multi-party consensus<00:58:17.160> around<00:58:17.460> data<00:58:18.000> points<00:58:18.300> and<00:58:18.660> also 00:58:18.950 --> 00:58:18.960 align:start position:0% consensus around data points and also 00:58:18.960 --> 00:58:20.270 align:start position:0% consensus around data points and also conflicts 00:58:20.270 --> 00:58:20.280 align:start position:0% conflicts 00:58:20.280 --> 00:58:23.030 align:start position:0% conflicts and<00:58:20.819> that's<00:58:21.059> always<00:58:21.300> been<00:58:21.599> my<00:58:22.140> assistance 00:58:23.030 --> 00:58:23.040 align:start position:0% and that's always been my assistance 00:58:23.040 --> 00:58:26.150 align:start position:0% and that's always been my assistance about<00:58:23.700> pulling<00:58:24.240> everything<00:58:24.720> on<00:58:25.020> chain 00:58:26.150 --> 00:58:26.160 align:start position:0% about pulling everything on chain 00:58:26.160 --> 00:58:27.349 align:start position:0% about pulling everything on chain um because 00:58:27.349 --> 00:58:27.359 align:start position:0% um because 00:58:27.359 --> 00:58:30.049 align:start position:0% um because it<00:58:28.140> it<00:58:28.140> makes<00:58:28.859> things<00:58:29.040> much<00:58:29.339> more<00:58:29.579> complicated 00:58:30.049 --> 00:58:30.059 align:start position:0% it it makes things much more complicated 00:58:30.059 --> 00:58:32.230 align:start position:0% it it makes things much more complicated to<00:58:30.420> and<00:58:31.079> it<00:58:31.319> also 00:58:32.230 --> 00:58:32.240 align:start position:0% to and it also 00:58:32.240 --> 00:58:34.609 align:start position:0% to and it also creates<00:58:33.240> friction<00:58:33.540> around<00:58:33.780> how<00:58:34.200> much<00:58:34.319> you<00:58:34.500> can 00:58:34.609 --> 00:58:34.619 align:start position:0% creates friction around how much you can 00:58:34.619 --> 00:58:36.710 align:start position:0% creates friction around how much you can actually<00:58:34.740> trust<00:58:35.160> something<00:58:35.339> versus<00:58:36.059> if<00:58:36.540> it's 00:58:36.710 --> 00:58:36.720 align:start position:0% actually trust something versus if it's 00:58:36.720 --> 00:58:38.690 align:start position:0% actually trust something versus if it's housed<00:58:37.260> somewhere<00:58:37.559> else<00:58:37.740> in<00:58:38.220> some<00:58:38.400> kind<00:58:38.579> of 00:58:38.690 --> 00:58:38.700 align:start position:0% housed somewhere else in some kind of 00:58:38.700 --> 00:58:41.750 align:start position:0% housed somewhere else in some kind of on-chain<00:58:39.119> registry<00:58:39.920> that<00:58:40.920> can<00:58:41.040> be<00:58:41.160> updated<00:58:41.460> by 00:58:41.750 --> 00:58:41.760 align:start position:0% on-chain registry that can be updated by 00:58:41.760 --> 00:58:44.450 align:start position:0% on-chain registry that can be updated by multi-parties<00:58:42.540> and<00:58:43.140> so<00:58:43.260> that's<00:58:43.440> why<00:58:43.799> my 00:58:44.450 --> 00:58:44.460 align:start position:0% multi-parties and so that's why my 00:58:44.460 --> 00:58:45.950 align:start position:0% multi-parties and so that's why my feeling<00:58:44.579> on<00:58:44.819> this<00:58:45.000> has<00:58:45.180> always<00:58:45.299> been<00:58:45.540> that 00:58:45.950 --> 00:58:45.960 align:start position:0% feeling on this has always been that 00:58:45.960 --> 00:58:48.530 align:start position:0% feeling on this has always been that music<00:58:46.619> nft<00:58:47.040> data<00:58:47.579> should<00:58:47.760> be<00:58:48.000> minimally 00:58:48.530 --> 00:58:48.540 align:start position:0% music nft data should be minimally 00:58:48.540 --> 00:58:52.130 align:start position:0% music nft data should be minimally viable<00:58:49.280> and<00:58:50.280> contextual<00:58:50.940> Rich<00:58:51.299> data<00:58:51.839> should 00:58:52.130 --> 00:58:52.140 align:start position:0% viable and contextual Rich data should 00:58:52.140 --> 00:58:55.789 align:start position:0% viable and contextual Rich data should be<00:58:52.319> kept<00:58:53.099> elsewhere<00:58:53.460> but<00:58:54.180> in<00:58:54.599> a<00:58:54.900> fair<00:58:55.079> way<00:58:55.380> if 00:58:55.789 --> 00:58:55.799 align:start position:0% be kept elsewhere but in a fair way if 00:58:55.799 --> 00:58:57.589 align:start position:0% be kept elsewhere but in a fair way if that<00:58:55.920> makes<00:58:56.099> sense<00:58:56.400> so<00:58:57.180> just<00:58:57.359> interesting 00:58:57.589 --> 00:58:57.599 align:start position:0% that makes sense so just interesting 00:58:57.599 --> 00:58:59.589 align:start position:0% that makes sense so just interesting what<00:58:57.839> you<00:58:58.020> think<00:58:58.079> about<00:58:58.200> that 00:58:59.589 --> 00:58:59.599 align:start position:0% what you think about that 00:58:59.599 --> 00:59:02.510 align:start position:0% what you think about that what<00:59:00.599> are<00:59:00.720> your<00:59:00.839> thoughts<00:59:01.079> on<00:59:01.260> the 00:59:02.510 --> 00:59:02.520 align:start position:0% what are your thoughts on the 00:59:02.520 --> 00:59:04.250 align:start position:0% what are your thoughts on the um<00:59:02.579> the<00:59:02.940> metadata<00:59:03.359> render<00:59:03.599> architecture<00:59:04.140> that 00:59:04.250 --> 00:59:04.260 align:start position:0% um the metadata render architecture that 00:59:04.260 --> 00:59:05.990 align:start position:0% um the metadata render architecture that zores<00:59:04.619> put<00:59:04.799> out<00:59:04.920> where<00:59:05.160> the<00:59:05.280> Creator<00:59:05.520> is<00:59:05.760> able 00:59:05.990 --> 00:59:06.000 align:start position:0% zores put out where the Creator is able 00:59:06.000 --> 00:59:08.630 align:start position:0% zores put out where the Creator is able to<00:59:06.180> there's<00:59:07.079> a<00:59:07.260> trusted<00:59:07.619> party<00:59:08.280> um<00:59:08.280> a<00:59:08.460> role 00:59:08.630 --> 00:59:08.640 align:start position:0% to there's a trusted party um a role 00:59:08.640 --> 00:59:09.950 align:start position:0% to there's a trusted party um a role that<00:59:08.760> is<00:59:08.880> able<00:59:09.059> to<00:59:09.119> go<00:59:09.240> back<00:59:09.359> in<00:59:09.540> and<00:59:09.660> update 00:59:09.950 --> 00:59:09.960 align:start position:0% that is able to go back in and update 00:59:09.960 --> 00:59:12.349 align:start position:0% that is able to go back in and update that<00:59:10.140> metadata<00:59:10.740> when<00:59:11.339> they<00:59:11.520> choose<00:59:11.760> does<00:59:11.940> that 00:59:12.349 --> 00:59:12.359 align:start position:0% that metadata when they choose does that 00:59:12.359 --> 00:59:13.609 align:start position:0% that metadata when they choose does that make<00:59:12.540> a<00:59:12.660> difference<00:59:12.780> or<00:59:13.020> you<00:59:13.140> still<00:59:13.260> think<00:59:13.440> the 00:59:13.609 --> 00:59:13.619 align:start position:0% make a difference or you still think the 00:59:13.619 --> 00:59:15.530 align:start position:0% make a difference or you still think the best<00:59:13.799> solution<00:59:14.220> is<00:59:14.400> fully<00:59:14.640> off<00:59:14.760> chain 00:59:15.530 --> 00:59:15.540 align:start position:0% best solution is fully off chain 00:59:15.540 --> 00:59:18.170 align:start position:0% best solution is fully off chain well<00:59:16.140> he<00:59:16.740> decides<00:59:17.099> who<00:59:17.220> the<00:59:17.339> trusted<00:59:17.700> party<00:59:17.880> is 00:59:18.170 --> 00:59:18.180 align:start position:0% well he decides who the trusted party is 00:59:18.180 --> 00:59:19.670 align:start position:0% well he decides who the trusted party is the<00:59:18.599> creator 00:59:19.670 --> 00:59:19.680 align:start position:0% the creator 00:59:19.680 --> 00:59:22.190 align:start position:0% the creator but<00:59:20.099> what<00:59:20.280> if<00:59:20.400> there's<00:59:20.579> multiple<00:59:21.000> creators 00:59:22.190 --> 00:59:22.200 align:start position:0% but what if there's multiple creators 00:59:22.200 --> 00:59:23.930 align:start position:0% but what if there's multiple creators I'm<00:59:22.559> excited<00:59:22.859> to<00:59:22.980> hear<00:59:23.099> Colombo's<00:59:23.640> talk<00:59:23.760> on 00:59:23.930 --> 00:59:23.940 align:start position:0% I'm excited to hear Colombo's talk on 00:59:23.940 --> 00:59:26.510 align:start position:0% I'm excited to hear Colombo's talk on that<00:59:24.119> yeah<00:59:24.920> this<00:59:25.920> is<00:59:25.980> the<00:59:26.099> challenge<00:59:26.280> right 00:59:26.510 --> 00:59:26.520 align:start position:0% that yeah this is the challenge right 00:59:26.520 --> 00:59:27.710 align:start position:0% that yeah this is the challenge right and<00:59:26.760> then<00:59:26.880> you've<00:59:27.000> got<00:59:27.059> differentiological 00:59:27.710 --> 00:59:27.720 align:start position:0% and then you've got differentiological 00:59:27.720 --> 00:59:31.190 align:start position:0% and then you've got differentiological buyers<00:59:28.400> Publishers<00:59:29.400> uh<00:59:29.819> producers 00:59:31.190 --> 00:59:31.200 align:start position:0% buyers Publishers uh producers 00:59:31.200 --> 00:59:33.170 align:start position:0% buyers Publishers uh producers um all<00:59:31.559> these<00:59:31.799> people<00:59:31.980> who<00:59:32.400> are<00:59:32.520> part<00:59:32.819> of<00:59:33.000> this 00:59:33.170 --> 00:59:33.180 align:start position:0% um all these people who are part of this 00:59:33.180 --> 00:59:35.450 align:start position:0% um all these people who are part of this Rich<00:59:33.359> soup<00:59:33.720> of 00:59:35.450 --> 00:59:35.460 align:start position:0% Rich soup of 00:59:35.460 --> 00:59:37.130 align:start position:0% Rich soup of um<00:59:35.579> influencer<00:59:36.180> creates<00:59:36.540> a<00:59:36.720> piece<00:59:36.900> of<00:59:36.960> art 00:59:37.130 --> 00:59:37.140 align:start position:0% um influencer creates a piece of art 00:59:37.140 --> 00:59:38.750 align:start position:0% um influencer creates a piece of art like<00:59:37.680> at<00:59:37.859> the<00:59:37.980> moment<00:59:38.099> the<00:59:38.220> music<00:59:38.400> entities 00:59:38.750 --> 00:59:38.760 align:start position:0% like at the moment the music entities 00:59:38.760 --> 00:59:40.849 align:start position:0% like at the moment the music entities were<00:59:39.240> in<00:59:39.720> a<00:59:39.900> pretty<00:59:40.020> nice<00:59:40.200> place<00:59:40.440> in<00:59:40.680> there 00:59:40.849 --> 00:59:40.859 align:start position:0% were in a pretty nice place in there 00:59:40.859 --> 00:59:42.530 align:start position:0% were in a pretty nice place in there it's<00:59:41.099> usually<00:59:41.339> been<00:59:41.520> one<00:59:41.940> person<00:59:42.119> putting 00:59:42.530 --> 00:59:42.540 align:start position:0% it's usually been one person putting 00:59:42.540 --> 00:59:43.730 align:start position:0% it's usually been one person putting something<00:59:42.660> out 00:59:43.730 --> 00:59:43.740 align:start position:0% something out 00:59:43.740 --> 00:59:45.770 align:start position:0% something out um<00:59:43.799> but<00:59:44.280> gets<00:59:44.579> complicated<00:59:45.059> as<00:59:45.480> soon<00:59:45.599> as 00:59:45.770 --> 00:59:45.780 align:start position:0% um but gets complicated as soon as 00:59:45.780 --> 00:59:48.170 align:start position:0% um but gets complicated as soon as like<00:59:46.079> that<00:59:46.920> expands<00:59:47.400> right 00:59:48.170 --> 00:59:48.180 align:start position:0% like that expands right 00:59:48.180 --> 00:59:49.309 align:start position:0% like that expands right um<00:59:48.240> and<00:59:48.420> I<00:59:48.540> think<00:59:48.660> like<00:59:48.839> it's<00:59:49.140> really 00:59:49.309 --> 00:59:49.319 align:start position:0% um and I think like it's really 00:59:49.319 --> 00:59:50.510 align:start position:0% um and I think like it's really important<00:59:49.619> that<00:59:49.799> as<00:59:49.980> we're<00:59:50.099> thinking<00:59:50.400> through 00:59:50.510 --> 00:59:50.520 align:start position:0% important that as we're thinking through 00:59:50.520 --> 00:59:52.430 align:start position:0% important that as we're thinking through this<00:59:50.700> we<00:59:50.880> need<00:59:51.059> to<00:59:51.180> be<00:59:51.299> you<00:59:51.839> know<00:59:51.960> thinking<00:59:52.260> for 00:59:52.430 --> 00:59:52.440 align:start position:0% this we need to be you know thinking for 00:59:52.440 --> 00:59:54.289 align:start position:0% this we need to be you know thinking for like<00:59:52.680> Mass<00:59:52.859> adoption<00:59:53.280> and<00:59:53.520> how<00:59:53.880> to<00:59:54.000> do<00:59:54.119> all 00:59:54.289 --> 00:59:54.299 align:start position:0% like Mass adoption and how to do all 00:59:54.299 --> 00:59:55.430 align:start position:0% like Mass adoption and how to do all that 00:59:55.430 --> 00:59:55.440 align:start position:0% that 00:59:55.440 --> 00:59:57.710 align:start position:0% that Point<00:59:55.920> well<00:59:56.220> taken 00:59:57.710 --> 00:59:57.720 align:start position:0% Point well taken 00:59:57.720 --> 01:00:00.410 align:start position:0% Point well taken nice<00:59:58.260> we<00:59:58.980> uh<00:59:59.460> yeah<00:59:59.640> if<00:59:59.819> you<00:59:59.940> are<01:00:00.059> taking<01:00:00.240> more 01:00:00.410 --> 01:00:00.420 align:start position:0% nice we uh yeah if you are taking more 01:00:00.420 --> 01:00:01.970 align:start position:0% nice we uh yeah if you are taking more questions<01:00:00.660> we<01:00:01.020> have<01:00:01.140> two<01:00:01.319> more<01:00:01.440> minutes<01:00:01.680> yes 01:00:01.970 --> 01:00:01.980 align:start position:0% questions we have two more minutes yes 01:00:01.980 --> 01:00:09.349 align:start position:0% questions we have two more minutes yes okay<01:00:02.220> yeah<01:00:02.520> tranky 01:00:09.349 --> 01:00:09.359 align:start position:0% 01:00:09.359 --> 01:00:11.049 align:start position:0% um<01:00:09.420> this<01:00:09.660> is<01:00:09.780> more<01:00:10.020> just<01:00:10.200> a<01:00:10.380> comment<01:00:10.680> about 01:00:11.049 --> 01:00:11.059 align:start position:0% um this is more just a comment about 01:00:11.059 --> 01:00:13.190 align:start position:0% um this is more just a comment about whether<01:00:12.059> or<01:00:12.359> not<01:00:12.480> you<01:00:12.660> want<01:00:12.780> to<01:00:12.900> do<01:00:12.960> like<01:00:13.079> an 01:00:13.190 --> 01:00:13.200 align:start position:0% whether or not you want to do like an 01:00:13.200 --> 01:00:14.630 align:start position:0% whether or not you want to do like an EIP<01:00:13.440> or<01:00:13.740> something<01:00:13.859> I<01:00:14.099> was<01:00:14.220> in<01:00:14.339> a<01:00:14.520> talk 01:00:14.630 --> 01:00:14.640 align:start position:0% EIP or something I was in a talk 01:00:14.640 --> 01:00:17.450 align:start position:0% EIP or something I was in a talk yesterday<01:00:15.200> that<01:00:16.200> was<01:00:16.500> like<01:00:16.740> see<01:00:17.040> something 01:00:17.450 --> 01:00:17.460 align:start position:0% yesterday that was like see something 01:00:17.460 --> 01:00:20.750 align:start position:0% yesterday that was like see something called<01:00:17.700> like<01:00:17.940> c<01:00:18.240> a<01:00:18.599> i<01:00:19.440> p<01:00:19.799> it<01:00:20.339> was<01:00:20.460> kind<01:00:20.579> of<01:00:20.640> over 01:00:20.750 --> 01:00:20.760 align:start position:0% called like c a i p it was kind of over 01:00:20.760 --> 01:00:22.430 align:start position:0% called like c a i p it was kind of over my<01:00:20.940> head<01:00:21.059> I'm<01:00:21.240> not<01:00:21.299> gonna<01:00:21.420> lie<01:00:21.599> like<01:00:22.200> Captain 01:00:22.430 --> 01:00:22.440 align:start position:0% my head I'm not gonna lie like Captain 01:00:22.440 --> 01:00:24.470 align:start position:0% my head I'm not gonna lie like Captain but<01:00:23.040> it<01:00:23.400> was<01:00:23.520> a<01:00:23.700> different<01:00:23.819> type<01:00:24.119> of<01:00:24.299> like 01:00:24.470 --> 01:00:24.480 align:start position:0% but it was a different type of like 01:00:24.480 --> 01:00:26.329 align:start position:0% but it was a different type of like Improvement<01:00:25.079> proposal<01:00:25.680> sort<01:00:26.099> of<01:00:26.160> like 01:00:26.329 --> 01:00:26.339 align:start position:0% Improvement proposal sort of like 01:00:26.339 --> 01:00:29.390 align:start position:0% Improvement proposal sort of like Coalition<01:00:26.940> about<01:00:27.680> self-related<01:00:28.680> like<01:00:28.859> l2s 01:00:29.390 --> 01:00:29.400 align:start position:0% Coalition about self-related like l2s 01:00:29.400 --> 01:00:31.789 align:start position:0% Coalition about self-related like l2s and<01:00:29.579> things<01:00:29.819> I<01:00:30.420> mean<01:00:30.599> and<01:00:30.780> addresses<01:00:31.200> so<01:00:31.680> it 01:00:31.789 --> 01:00:31.799 align:start position:0% and things I mean and addresses so it 01:00:31.799 --> 01:00:34.069 align:start position:0% and things I mean and addresses so it could<01:00:31.920> be<01:00:31.980> they<01:00:32.280> have<01:00:32.460> a<01:00:32.579> the<01:00:33.000> GitHub<01:00:33.599> that's 01:00:34.069 --> 01:00:34.079 align:start position:0% could be they have a the GitHub that's 01:00:34.079 --> 01:00:36.890 align:start position:0% could be they have a the GitHub that's like<01:00:34.260> set<01:00:34.440> up<01:00:34.619> so<01:00:35.339> I<01:00:35.700> think<01:00:35.819> an<01:00:36.540> initial 01:00:36.890 --> 01:00:36.900 align:start position:0% like set up so I think an initial 01:00:36.900 --> 01:00:38.870 align:start position:0% like set up so I think an initial interesting<01:00:37.500> step<01:00:37.680> could<01:00:37.980> just<01:00:38.160> be<01:00:38.280> forked<01:00:38.760> or 01:00:38.870 --> 01:00:38.880 align:start position:0% interesting step could just be forked or 01:00:38.880 --> 01:00:41.270 align:start position:0% interesting step could just be forked or GitHub<01:00:39.180> and<01:00:39.720> turn<01:00:39.960> it<01:00:40.079> into<01:00:40.200> like<01:00:40.559> a<01:00:41.040> music 01:00:41.270 --> 01:00:41.280 align:start position:0% GitHub and turn it into like a music 01:00:41.280 --> 01:00:43.670 align:start position:0% GitHub and turn it into like a music metadata<01:00:41.940> IP<01:00:42.480> thing 01:00:43.670 --> 01:00:43.680 align:start position:0% metadata IP thing 01:00:43.680 --> 01:00:46.549 align:start position:0% metadata IP thing mmip<01:00:44.640> or<01:00:45.000> something<01:00:45.119> I<01:00:45.359> don't<01:00:45.420> know<01:00:46.020> but<01:00:46.440> yeah 01:00:46.549 --> 01:00:46.559 align:start position:0% mmip or something I don't know but yeah 01:00:46.559 --> 01:00:47.930 align:start position:0% mmip or something I don't know but yeah just<01:00:46.799> a<01:00:46.920> suggestion 01:00:47.930 --> 01:00:47.940 align:start position:0% just a suggestion 01:00:47.940 --> 01:00:51.049 align:start position:0% just a suggestion yes<01:00:48.660> so<01:00:49.140> here's<01:00:49.500> the<01:00:49.680> catalog<01:00:50.040> standard 01:00:51.049 --> 01:00:51.059 align:start position:0% yes so here's the catalog standard 01:00:51.059 --> 01:00:52.370 align:start position:0% yes so here's the catalog standard um<01:00:51.119> and<01:00:51.240> you're<01:00:51.359> talking<01:00:51.540> about<01:00:51.660> cap<01:00:51.839> 19<01:00:52.140> is 01:00:52.370 --> 01:00:52.380 align:start position:0% um and you're talking about cap 19 is 01:00:52.380 --> 01:00:54.890 align:start position:0% um and you're talking about cap 19 is like<01:00:52.559> cross<01:00:52.859> chain<01:00:53.220> assets 01:00:54.890 --> 01:00:54.900 align:start position:0% like cross chain assets 01:00:54.900 --> 01:00:59.150 align:start position:0% like cross chain assets in<01:00:55.380> here<01:00:55.559> we<01:00:56.280> have<01:00:56.640> references<01:00:57.359> to<01:00:57.720> other<01:00:58.260> uh 01:00:59.150 --> 01:00:59.160 align:start position:0% in here we have references to other uh 01:00:59.160 --> 01:01:01.549 align:start position:0% in here we have references to other uh types<01:00:59.460> of<01:00:59.579> assets<01:00:59.940> and<01:01:00.420> so<01:01:00.599> you'll<01:01:00.960> see<01:01:01.200> in 01:01:01.549 --> 01:01:01.559 align:start position:0% types of assets and so you'll see in 01:01:01.559 --> 01:01:05.450 align:start position:0% types of assets and so you'll see in fields<01:01:02.040> like<01:01:02.339> artwork<01:01:02.839> you<01:01:03.839> have<01:01:03.960> a<01:01:04.140> URI<01:01:04.619> and<01:01:05.280> a 01:01:05.450 --> 01:01:05.460 align:start position:0% fields like artwork you have a URI and a 01:01:05.460 --> 01:01:07.370 align:start position:0% fields like artwork you have a URI and a mime<01:01:05.579> type<01:01:05.819> which<01:01:06.059> is<01:01:06.180> very<01:01:06.299> normal<01:01:06.540> but<01:01:07.260> then 01:01:07.370 --> 01:01:07.380 align:start position:0% mime type which is very normal but then 01:01:07.380 --> 01:01:09.770 align:start position:0% mime type which is very normal but then you<01:01:07.559> also<01:01:07.799> have<01:01:07.980> this<01:01:08.220> nft<01:01:08.640> field<01:01:09.180> which<01:01:09.599> can 01:01:09.770 --> 01:01:09.780 align:start position:0% you also have this nft field which can 01:01:09.780 --> 01:01:11.569 align:start position:0% you also have this nft field which can link<01:01:09.900> to<01:01:10.079> other<01:01:10.260> nfts<01:01:10.859> and<01:01:11.040> that<01:01:11.160> follows<01:01:11.460> the 01:01:11.569 --> 01:01:11.579 align:start position:0% link to other nfts and that follows the 01:01:11.579 --> 01:01:14.089 align:start position:0% link to other nfts and that follows the cap<01:01:11.700> 19<01:01:12.000> standard<01:01:12.599> of<01:01:12.720> cross<01:01:12.960> chain<01:01:13.260> so<01:01:13.980> you 01:01:14.089 --> 01:01:14.099 align:start position:0% cap 19 standard of cross chain so you 01:01:14.099 --> 01:01:16.490 align:start position:0% cap 19 standard of cross chain so you can<01:01:14.220> actually<01:01:14.400> link<01:01:14.819> different<01:01:15.420> nfts<01:01:16.079> if<01:01:16.200> like 01:01:16.490 --> 01:01:16.500 align:start position:0% can actually link different nfts if like 01:01:16.500 --> 01:01:18.170 align:start position:0% can actually link different nfts if like for<01:01:16.920> example<01:01:17.099> all<01:01:17.339> the<01:01:17.460> nfts<01:01:17.819> I<01:01:17.940> just<01:01:18.059> made 01:01:18.170 --> 01:01:18.180 align:start position:0% for example all the nfts I just made 01:01:18.180 --> 01:01:21.230 align:start position:0% for example all the nfts I just made from<01:01:18.299> Sagrado<01:01:18.780> are<01:01:19.740> derivative<01:01:20.160> nfts<01:01:20.880> of<01:01:21.119> an 01:01:21.230 --> 01:01:21.240 align:start position:0% from Sagrado are derivative nfts of an 01:01:21.240 --> 01:01:23.750 align:start position:0% from Sagrado are derivative nfts of an original<01:01:21.420> nft<01:01:21.920> I<01:01:22.920> did<01:01:23.040> not<01:01:23.220> link<01:01:23.460> the<01:01:23.640> original 01:01:23.750 --> 01:01:23.760 align:start position:0% original nft I did not link the original 01:01:23.760 --> 01:01:25.609 align:start position:0% original nft I did not link the original nft<01:01:24.180> and<01:01:24.480> that's<01:01:24.599> a<01:01:24.780> downside<01:01:25.020> on<01:01:25.200> me<01:01:25.380> and<01:01:25.500> I'm 01:01:25.609 --> 01:01:25.619 align:start position:0% nft and that's a downside on me and I'm 01:01:25.619 --> 01:01:26.870 align:start position:0% nft and that's a downside on me and I'm going<01:01:25.740> to<01:01:25.859> publicly<01:01:26.099> say<01:01:26.280> that<01:01:26.400> like<01:01:26.579> I<01:01:26.760> could 01:01:26.870 --> 01:01:26.880 align:start position:0% going to publicly say that like I could 01:01:26.880 --> 01:01:29.150 align:start position:0% going to publicly say that like I could obviously<01:01:27.240> do<01:01:27.359> better<01:01:27.540> but<01:01:28.260> the<01:01:28.740> standard<01:01:29.040> is 01:01:29.150 --> 01:01:29.160 align:start position:0% obviously do better but the standard is 01:01:29.160 --> 01:01:30.710 align:start position:0% obviously do better but the standard is already<01:01:29.339> up<01:01:29.520> to<01:01:29.640> date<01:01:29.700> so<01:01:29.880> that<01:01:30.059> if<01:01:30.240> we<01:01:30.359> want<01:01:30.540> to 01:01:30.710 --> 01:01:30.720 align:start position:0% already up to date so that if we want to 01:01:30.720 --> 01:01:32.690 align:start position:0% already up to date so that if we want to link<01:01:30.839> other<01:01:31.079> assets<01:01:31.440> within<01:01:31.740> our<01:01:31.920> nfts<01:01:32.400> we<01:01:32.579> can 01:01:32.690 --> 01:01:32.700 align:start position:0% link other assets within our nfts we can 01:01:32.700 --> 01:01:33.710 align:start position:0% link other assets within our nfts we can and<01:01:32.940> so<01:01:33.059> when<01:01:33.180> we're<01:01:33.359> thinking<01:01:33.599> about 01:01:33.710 --> 01:01:33.720 align:start position:0% and so when we're thinking about 01:01:33.720 --> 01:01:36.170 align:start position:0% and so when we're thinking about composing<01:01:34.260> nfts<01:01:34.859> is<01:01:35.040> music<01:01:35.280> that's<01:01:35.819> built<01:01:36.119> on 01:01:36.170 --> 01:01:36.180 align:start position:0% composing nfts is music that's built on 01:01:36.180 --> 01:01:38.030 align:start position:0% composing nfts is music that's built on top<01:01:36.359> of<01:01:36.480> stems<01:01:36.960> or<01:01:37.319> music<01:01:37.500> that's<01:01:37.680> built<01:01:37.920> on 01:01:38.030 --> 01:01:38.040 align:start position:0% top of stems or music that's built on 01:01:38.040 --> 01:01:39.349 align:start position:0% top of stems or music that's built on top<01:01:38.160> of<01:01:38.280> other<01:01:38.400> music<01:01:38.579> or<01:01:38.819> a<01:01:38.940> remix<01:01:39.059> that's 01:01:39.349 --> 01:01:39.359 align:start position:0% top of other music or a remix that's 01:01:39.359 --> 01:01:40.549 align:start position:0% top of other music or a remix that's built<01:01:39.599> on<01:01:39.660> top<01:01:39.780> of<01:01:39.900> music<01:01:40.020> that's<01:01:40.200> built<01:01:40.440> on 01:01:40.549 --> 01:01:40.559 align:start position:0% built on top of music that's built on 01:01:40.559 --> 01:01:42.890 align:start position:0% built on top of music that's built on top<01:01:40.680> of<01:01:40.799> stems<01:01:41.160> the<01:01:41.760> metadata<01:01:42.240> can<01:01:42.480> link<01:01:42.660> back 01:01:42.890 --> 01:01:42.900 align:start position:0% top of stems the metadata can link back 01:01:42.900 --> 01:01:44.930 align:start position:0% top of stems the metadata can link back to<01:01:43.140> those<01:01:43.380> underlying<01:01:44.220> works<01:01:44.460> so<01:01:44.579> that<01:01:44.700> we<01:01:44.819> can 01:01:44.930 --> 01:01:44.940 align:start position:0% to those underlying works so that we can 01:01:44.940 --> 01:01:46.430 align:start position:0% to those underlying works so that we can always<01:01:45.180> be<01:01:45.420> pointing<01:01:45.780> the<01:01:45.900> credit<01:01:46.020> back<01:01:46.260> to 01:01:46.430 --> 01:01:46.440 align:start position:0% always be pointing the credit back to 01:01:46.440 --> 01:01:48.530 align:start position:0% always be pointing the credit back to those<01:01:46.559> original<01:01:46.799> users<01:01:47.640> did<01:01:48.119> I<01:01:48.240> miss<01:01:48.359> the 01:01:48.530 --> 01:01:48.540 align:start position:0% those original users did I miss the 01:01:48.540 --> 01:01:49.849 align:start position:0% those original users did I miss the point<01:01:48.660> of<01:01:48.780> your<01:01:48.900> question<01:01:49.020> I<01:01:49.200> heard<01:01:49.380> cap<01:01:49.619> 19 01:01:49.849 --> 01:01:49.859 align:start position:0% point of your question I heard cap 19 01:01:49.859 --> 01:01:52.670 align:start position:0% point of your question I heard cap 19 and<01:01:50.160> I<01:01:50.339> wanted<01:01:50.400> to<01:01:50.579> show<01:01:50.700> this 01:01:52.670 --> 01:01:52.680 align:start position:0% and I wanted to show this 01:01:52.680 --> 01:01:54.230 align:start position:0% and I wanted to show this is<01:01:53.040> mainly<01:01:53.339> just 01:01:54.230 --> 01:01:54.240 align:start position:0% is mainly just 01:01:54.240 --> 01:01:56.150 align:start position:0% is mainly just mainly<01:01:54.900> referring<01:01:55.319> to<01:01:55.440> the<01:01:55.619> structure<01:01:55.980> they 01:01:56.150 --> 01:01:56.160 align:start position:0% mainly referring to the structure they 01:01:56.160 --> 01:01:58.250 align:start position:0% mainly referring to the structure they have<01:01:56.280> like<01:01:56.460> on<01:01:56.760> GitHub<01:01:57.059> for<01:01:57.359> like<01:01:57.599> organizing 01:01:58.250 --> 01:01:58.260 align:start position:0% have like on GitHub for like organizing 01:01:58.260 --> 01:02:00.170 align:start position:0% have like on GitHub for like organizing Community<01:01:58.680> like<01:01:59.040> input<01:01:59.460> so<01:01:59.760> I<01:01:59.880> think<01:02:00.000> just 01:02:00.170 --> 01:02:00.180 align:start position:0% Community like input so I think just 01:02:00.180 --> 01:02:01.910 align:start position:0% Community like input so I think just like<01:02:00.420> forking<01:02:00.900> the<01:02:01.079> GitHub<01:02:01.380> they<01:02:01.559> have<01:02:01.740> would 01:02:01.910 --> 01:02:01.920 align:start position:0% like forking the GitHub they have would 01:02:01.920 --> 01:02:03.170 align:start position:0% like forking the GitHub they have would be<01:02:02.040> a<01:02:02.160> great<01:02:02.280> place<01:02:02.460> to<01:02:02.579> start<01:02:02.700> if<01:02:03.000> you<01:02:03.059> were 01:02:03.170 --> 01:02:03.180 align:start position:0% be a great place to start if you were 01:02:03.180 --> 01:02:04.789 align:start position:0% be a great place to start if you were trying<01:02:03.299> to<01:02:03.420> like<01:02:03.540> start<01:02:04.020> the<01:02:04.319> process<01:02:04.619> of 01:02:04.789 --> 01:02:04.799 align:start position:0% trying to like start the process of 01:02:04.799 --> 01:02:07.309 align:start position:0% trying to like start the process of figuring<01:02:05.160> out<01:02:05.280> how<01:02:05.819> to<01:02:05.940> like<01:02:06.119> you<01:02:06.540> know 01:02:07.309 --> 01:02:07.319 align:start position:0% figuring out how to like you know 01:02:07.319 --> 01:02:08.809 align:start position:0% figuring out how to like you know just<01:02:07.680> like<01:02:07.799> coordinate<01:02:08.220> between<01:02:08.400> a<01:02:08.640> lot<01:02:08.700> of 01:02:08.809 --> 01:02:08.819 align:start position:0% just like coordinate between a lot of 01:02:08.819 --> 01:02:10.430 align:start position:0% just like coordinate between a lot of people<01:02:08.880> forking<01:02:09.599> their<01:02:09.660> repo<01:02:09.960> seems<01:02:10.319> like<01:02:10.380> a 01:02:10.430 --> 01:02:10.440 align:start position:0% people forking their repo seems like a 01:02:10.440 --> 01:02:11.809 align:start position:0% people forking their repo seems like a good<01:02:10.559> place<01:02:10.680> to<01:02:10.799> start<01:02:10.980> just<01:02:11.220> start<01:02:11.460> housing 01:02:11.809 --> 01:02:11.819 align:start position:0% good place to start just start housing 01:02:11.819 --> 01:02:14.870 align:start position:0% good place to start just start housing that<01:02:12.000> information<01:02:12.299> in<01:02:12.900> some<01:02:13.260> place 01:02:14.870 --> 01:02:14.880 align:start position:0% that information in some place 01:02:14.880 --> 01:02:16.670 align:start position:0% that information in some place thank<01:02:15.240> you<01:02:15.420> thank<01:02:15.599> you<01:02:15.780> thank<01:02:16.079> you<01:02:16.260> yeah 01:02:16.670 --> 01:02:16.680 align:start position:0% thank you thank you thank you yeah 01:02:16.680 --> 01:02:18.650 align:start position:0% thank you thank you thank you yeah that's<01:02:16.920> it<01:02:17.099> we<01:02:17.520> don't<01:02:17.640> have<01:02:17.819> more<01:02:18.059> time<01:02:18.359> so 01:02:18.650 --> 01:02:18.660 align:start position:0% that's it we don't have more time so 01:02:18.660 --> 01:02:22.250 align:start position:0% that's it we don't have more time so thank<01:02:19.020> you<01:02:19.140> very<01:02:19.260> much<01:02:19.380> Sweetman 01:02:22.250 --> 01:02:22.260 align:start position:0% 01:02:22.260 --> 01:02:25.270 align:start position:0% and<01:02:23.099> next<01:02:23.579> up<01:02:23.700> is<01:02:23.940> Andres 01:02:25.270 --> 01:02:25.280 align:start position:0% and next up is Andres 01:02:25.280 --> 01:02:29.210 align:start position:0% and next up is Andres and<01:02:26.280> uh<01:02:26.760> we<01:02:27.420> are<01:02:27.660> staying<01:02:28.619> actually<01:02:28.740> in<01:02:28.980> music 01:02:29.210 --> 01:02:29.220 align:start position:0% and uh we are staying actually in music 01:02:29.220 --> 01:02:31.670 align:start position:0% and uh we are staying actually in music and<01:02:29.700> now<01:02:29.880> we<01:02:30.119> are<01:02:30.240> talking<01:02:30.480> about 01:02:31.670 --> 01:02:31.680 align:start position:0% and now we are talking about 01:02:31.680 --> 01:02:35.630 align:start position:0% and now we are talking about um the<01:02:32.220> web<01:02:32.460> 3<01:02:33.140> uh<01:02:34.140> music<01:02:34.859> multiplayer 01:02:35.630 --> 01:02:35.640 align:start position:0% um the web 3 uh music multiplayer 01:02:35.640 --> 01:02:37.370 align:start position:0% um the web 3 uh music multiplayer problems<01:02:36.059> and<01:02:36.359> I'm<01:02:36.480> very<01:02:36.599> excited<01:02:36.900> about<01:02:37.079> that 01:02:37.370 --> 01:02:37.380 align:start position:0% problems and I'm very excited about that 01:02:37.380 --> 01:02:38.630 align:start position:0% problems and I'm very excited about that talk<01:02:37.559> as<01:02:37.859> well 01:02:38.630 --> 01:02:38.640 align:start position:0% talk as well 01:02:38.640 --> 01:02:40.370 align:start position:0% talk as well thanks<01:02:39.240> uh 01:02:40.370 --> 01:02:40.380 align:start position:0% thanks uh 01:02:40.380 --> 01:02:42.950 align:start position:0% thanks uh not<01:02:40.799> a<01:02:40.980> lot<01:02:41.040> of<01:02:41.220> experience<01:02:41.520> presenting<01:02:42.119> but 01:02:42.950 --> 01:02:42.960 align:start position:0% not a lot of experience presenting but 01:02:42.960 --> 01:02:43.750 align:start position:0% not a lot of experience presenting but um 01:02:43.750 --> 01:02:43.760 align:start position:0% um 01:02:43.760 --> 01:02:47.450 align:start position:0% um here<01:02:44.760> we<01:02:44.880> are<01:02:45.000> so<01:02:45.420> we<01:02:46.260> started<01:02:46.559> off<01:02:46.740> a<01:02:47.339> few 01:02:47.450 --> 01:02:47.460 align:start position:0% here we are so we started off a few 01:02:47.460 --> 01:02:49.190 align:start position:0% here we are so we started off a few months<01:02:47.760> ago<01:02:47.940> a 01:02:49.190 --> 01:02:49.200 align:start position:0% months ago a 01:02:49.200 --> 01:02:52.069 align:start position:0% months ago a in<01:02:49.799> the<01:02:49.920> whatever<01:02:50.099> music<01:02:50.520> Dao<01:02:51.119> researching 01:02:52.069 --> 01:02:52.079 align:start position:0% in the whatever music Dao researching 01:02:52.079 --> 01:02:55.130 align:start position:0% in the whatever music Dao researching about<01:02:52.319> splits<01:02:53.280> and<01:02:54.540> um 01:02:55.130 --> 01:02:55.140 align:start position:0% about splits and um 01:02:55.140 --> 01:02:56.809 align:start position:0% about splits and um we<01:02:55.619> basically<01:02:55.920> got<01:02:56.099> two<01:02:56.280> three<01:02:56.460> main 01:02:56.809 --> 01:02:56.819 align:start position:0% we basically got two three main 01:02:56.819 --> 01:02:58.069 align:start position:0% we basically got two three main conclusions<01:02:57.299> some<01:02:57.540> of<01:02:57.660> them<01:02:57.720> are<01:02:57.960> very 01:02:58.069 --> 01:02:58.079 align:start position:0% conclusions some of them are very 01:02:58.079 --> 01:03:00.829 align:start position:0% conclusions some of them are very obvious<01:02:58.440> some<01:02:59.400> probably<01:02:59.760> not<01:03:00.059> that<01:03:00.240> much<01:03:00.420> one 01:03:00.829 --> 01:03:00.839 align:start position:0% obvious some probably not that much one 01:03:00.839 --> 01:03:05.890 align:start position:0% obvious some probably not that much one is<01:03:01.020> that<01:03:01.260> a<01:03:02.160> blockchains<01:03:03.059> can<01:03:03.960> serve<01:03:04.380> as<01:03:04.500> a<01:03:04.859> a 01:03:05.890 --> 01:03:05.900 align:start position:0% is that a blockchains can serve as a a 01:03:05.900 --> 01:03:09.650 align:start position:0% is that a blockchains can serve as a a login<01:03:06.900> as<01:03:07.680> a<01:03:07.859> log<01:03:07.980> of<01:03:08.220> information<01:03:08.660> and 01:03:09.650 --> 01:03:09.660 align:start position:0% login as a log of information and 01:03:09.660 --> 01:03:12.650 align:start position:0% login as a log of information and hopefully<01:03:10.079> look<01:03:10.799> into<01:03:11.040> the<01:03:11.280> future<01:03:11.460> even<01:03:12.299> like 01:03:12.650 --> 01:03:12.660 align:start position:0% hopefully look into the future even like 01:03:12.660 --> 01:03:15.410 align:start position:0% hopefully look into the future even like a<01:03:12.900> global<01:03:13.260> jurisdiction<01:03:13.740> notary<01:03:14.339> system 01:03:15.410 --> 01:03:15.420 align:start position:0% a global jurisdiction notary system 01:03:15.420 --> 01:03:19.190 align:start position:0% a global jurisdiction notary system with<01:03:16.319> a<01:03:16.740> legal<01:03:17.339> validation 01:03:19.190 --> 01:03:19.200 align:start position:0% with a legal validation 01:03:19.200 --> 01:03:22.450 align:start position:0% with a legal validation the<01:03:19.680> second<01:03:19.799> one<01:03:20.040> is<01:03:20.280> that<01:03:20.520> a<01:03:21.380> blockchains 01:03:22.450 --> 01:03:22.460 align:start position:0% the second one is that a blockchains 01:03:22.460 --> 01:03:25.549 align:start position:0% the second one is that a blockchains have<01:03:23.460> uh<01:03:23.819> the<01:03:24.240> the<01:03:24.299> abduction<01:03:24.960> architecture 01:03:25.549 --> 01:03:25.559 align:start position:0% have uh the the abduction architecture 01:03:25.559 --> 01:03:29.750 align:start position:0% have uh the the abduction architecture is<01:03:26.299> based<01:03:27.299> on<01:03:27.420> a<01:03:27.599> single<01:03:27.960> a<01:03:28.200> singular<01:03:28.619> point<01:03:29.520> of 01:03:29.750 --> 01:03:29.760 align:start position:0% is based on a single a singular point of 01:03:29.760 --> 01:03:31.849 align:start position:0% is based on a single a singular point of a<01:03:30.119> connection<01:03:30.540> or<01:03:30.960> entry 01:03:31.849 --> 01:03:31.859 align:start position:0% a connection or entry 01:03:31.859 --> 01:03:35.750 align:start position:0% a connection or entry for<01:03:32.339> the<01:03:32.579> user<01:03:32.940> and<01:03:33.720> the<01:03:33.900> third<01:03:34.020> one<01:03:34.200> is<01:03:34.619> that<01:03:34.980> a 01:03:35.750 --> 01:03:35.760 align:start position:0% for the user and the third one is that a 01:03:35.760 --> 01:03:39.049 align:start position:0% for the user and the third one is that a split<01:03:36.440> protocols<01:03:37.440> as<01:03:37.920> we<01:03:38.160> understand<01:03:38.460> them<01:03:38.880> in 01:03:39.049 --> 01:03:39.059 align:start position:0% split protocols as we understand them in 01:03:39.059 --> 01:03:43.069 align:start position:0% split protocols as we understand them in blockchain<01:03:39.859> are<01:03:40.859> focused<01:03:41.640> on<01:03:42.079> distribution 01:03:43.069 --> 01:03:43.079 align:start position:0% blockchain are focused on distribution 01:03:43.079 --> 01:03:46.370 align:start position:0% blockchain are focused on distribution of<01:03:43.380> funds<01:03:43.740> but<01:03:44.460> us<01:03:44.940> creators<01:03:45.599> think<01:03:46.140> about 01:03:46.370 --> 01:03:46.380 align:start position:0% of funds but us creators think about 01:03:46.380 --> 01:03:51.530 align:start position:0% of funds but us creators think about splits<01:03:47.040> more<01:03:47.520> on<01:03:48.180> ownership<01:03:49.140> than<01:03:49.920> really<01:03:50.540> a 01:03:51.530 --> 01:03:51.540 align:start position:0% splits more on ownership than really a 01:03:51.540 --> 01:03:55.970 align:start position:0% splits more on ownership than really a about<01:03:52.099> it<01:03:53.099> being<01:03:53.339> a<01:03:53.819> financial 01:03:55.970 --> 01:03:55.980 align:start position:0% about it being a financial 01:03:55.980 --> 01:03:58.370 align:start position:0% about it being a financial so<01:03:56.700> what<01:03:57.059> is<01:03:57.180> the<01:03:57.359> problem 01:03:58.370 --> 01:03:58.380 align:start position:0% so what is the problem 01:03:58.380 --> 01:04:00.710 align:start position:0% so what is the problem the<01:03:58.920> problem<01:03:59.099> is<01:03:59.339> copyright<01:03:59.819> right<01:04:00.299> we<01:04:00.540> all 01:04:00.710 --> 01:04:00.720 align:start position:0% the problem is copyright right we all 01:04:00.720 --> 01:04:02.809 align:start position:0% the problem is copyright right we all know<01:04:00.900> it's 01:04:02.809 --> 01:04:02.819 align:start position:0% know it's 01:04:02.819 --> 01:04:05.510 align:start position:0% know it's the<01:04:03.420> problem<01:04:03.599> and<01:04:03.839> it<01:04:03.960> is<01:04:04.079> the<01:04:04.200> solution<01:04:04.619> and 01:04:05.510 --> 01:04:05.520 align:start position:0% the problem and it is the solution and 01:04:05.520 --> 01:04:07.849 align:start position:0% the problem and it is the solution and copyright<01:04:05.940> law<01:04:06.240> has<01:04:06.540> been<01:04:06.720> used<01:04:07.079> and<01:04:07.380> has<01:04:07.619> been 01:04:07.849 --> 01:04:07.859 align:start position:0% copyright law has been used and has been 01:04:07.859 --> 01:04:11.450 align:start position:0% copyright law has been used and has been abused<01:04:08.839> uh<01:04:09.839> but<01:04:10.140> it's<01:04:10.380> still 01:04:11.450 --> 01:04:11.460 align:start position:0% abused uh but it's still 01:04:11.460 --> 01:04:14.150 align:start position:0% abused uh but it's still the<01:04:12.180> only<01:04:12.359> a 01:04:14.150 --> 01:04:14.160 align:start position:0% the only a 01:04:14.160 --> 01:04:17.210 align:start position:0% the only a or<01:04:14.640> the<01:04:14.880> or<01:04:15.299> the<01:04:15.599> most<01:04:15.900> widely<01:04:16.319> used<01:04:16.559> form<01:04:16.980> of 01:04:17.210 --> 01:04:17.220 align:start position:0% or the or the most widely used form of 01:04:17.220 --> 01:04:19.010 align:start position:0% or the or the most widely used form of monetization<01:04:17.819> of<01:04:18.119> intellectual<01:04:18.480> property 01:04:19.010 --> 01:04:19.020 align:start position:0% monetization of intellectual property 01:04:19.020 --> 01:04:20.870 align:start position:0% monetization of intellectual property right<01:04:19.559> and<01:04:19.920> if<01:04:20.040> we're<01:04:20.160> looking<01:04:20.339> to<01:04:20.520> the<01:04:20.700> Future 01:04:20.870 --> 01:04:20.880 align:start position:0% right and if we're looking to the Future 01:04:20.880 --> 01:04:24.289 align:start position:0% right and if we're looking to the Future where<01:04:21.660> each<01:04:21.960> time<01:04:22.140> we<01:04:22.380> have<01:04:22.559> less<01:04:23.280> and<01:04:23.460> less<01:04:23.760> a 01:04:24.289 --> 01:04:24.299 align:start position:0% where each time we have less and less a 01:04:24.299 --> 01:04:26.690 align:start position:0% where each time we have less and less a jobs<01:04:24.839> available<01:04:25.140> we<01:04:25.740> have<01:04:25.920> a<01:04:26.099> growing<01:04:26.400> Creator 01:04:26.690 --> 01:04:26.700 align:start position:0% jobs available we have a growing Creator 01:04:26.700 --> 01:04:29.750 align:start position:0% jobs available we have a growing Creator class<01:04:26.940> we<01:04:27.359> need<01:04:27.480> to<01:04:27.720> keep<01:04:27.960> copyright<01:04:28.859> as<01:04:29.400> one 01:04:29.750 --> 01:04:29.760 align:start position:0% class we need to keep copyright as one 01:04:29.760 --> 01:04:32.990 align:start position:0% class we need to keep copyright as one of<01:04:29.940> those<01:04:30.119> essential<01:04:31.220> ways<01:04:32.220> of<01:04:32.400> monetization 01:04:32.990 --> 01:04:33.000 align:start position:0% of those essential ways of monetization 01:04:33.000 --> 01:04:35.450 align:start position:0% of those essential ways of monetization for<01:04:33.420> creators<01:04:33.900> and 01:04:35.450 --> 01:04:35.460 align:start position:0% for creators and 01:04:35.460 --> 01:04:38.450 align:start position:0% for creators and the<01:04:36.240> the<01:04:36.480> copyright<01:04:37.079> industry<01:04:37.559> is<01:04:37.920> big<01:04:38.099> is 01:04:38.450 --> 01:04:38.460 align:start position:0% the the copyright industry is big is 01:04:38.460 --> 01:04:41.089 align:start position:0% the the copyright industry is big is played<01:04:38.819> with<01:04:38.940> with<01:04:39.299> problems<01:04:39.900> but<01:04:40.559> to<01:04:40.740> narrow 01:04:41.089 --> 01:04:41.099 align:start position:0% played with with problems but to narrow 01:04:41.099 --> 01:04:43.549 align:start position:0% played with with problems but to narrow them<01:04:41.280> down<01:04:41.579> it<01:04:42.059> is<01:04:42.180> mainly<01:04:42.599> a<01:04:43.079> human<01:04:43.200> problem 01:04:43.549 --> 01:04:43.559 align:start position:0% them down it is mainly a human problem 01:04:43.559 --> 01:04:46.609 align:start position:0% them down it is mainly a human problem like<01:04:44.400> it<01:04:44.700> always<01:04:44.940> is<01:04:45.240> and<01:04:45.960> it<01:04:46.079> is<01:04:46.200> that<01:04:46.440> people 01:04:46.609 --> 01:04:46.619 align:start position:0% like it always is and it is that people 01:04:46.619 --> 01:04:48.289 align:start position:0% like it always is and it is that people do<01:04:46.980> not<01:04:47.160> register<01:04:47.520> their<01:04:47.819> intellectual 01:04:48.289 --> 01:04:48.299 align:start position:0% do not register their intellectual 01:04:48.299 --> 01:04:50.870 align:start position:0% do not register their intellectual property<01:04:48.839> as<01:04:49.799> close<01:04:50.040> to<01:04:50.280> the<01:04:50.460> moment<01:04:50.700> of 01:04:50.870 --> 01:04:50.880 align:start position:0% property as close to the moment of 01:04:50.880 --> 01:04:53.510 align:start position:0% property as close to the moment of Genesis<01:04:51.240> as<01:04:51.540> possible<01:04:51.900> which<01:04:52.619> is 01:04:53.510 --> 01:04:53.520 align:start position:0% Genesis as possible which is 01:04:53.520 --> 01:04:55.609 align:start position:0% Genesis as possible which is actually<01:04:54.180> the 01:04:55.609 --> 01:04:55.619 align:start position:0% actually the 01:04:55.619 --> 01:04:58.910 align:start position:0% actually the the<01:04:55.980> best<01:04:56.700> way<01:04:57.059> to<01:04:57.599> protect<01:04:58.020> intellectual 01:04:58.910 --> 01:04:58.920 align:start position:0% the best way to protect intellectual 01:04:58.920 --> 01:05:02.210 align:start position:0% the best way to protect intellectual property<01:04:59.460> and<01:05:00.960> um 01:05:02.210 --> 01:05:02.220 align:start position:0% property and um 01:05:02.220 --> 01:05:05.450 align:start position:0% property and um so<01:05:03.000> and<01:05:03.599> this<01:05:03.720> is<01:05:03.839> maybe<01:05:04.079> because<01:05:04.460> creators 01:05:05.450 --> 01:05:05.460 align:start position:0% so and this is maybe because creators 01:05:05.460 --> 01:05:08.870 align:start position:0% so and this is maybe because creators think<01:05:05.819> that<01:05:06.599> registering<01:05:07.319> or<01:05:07.799> then<01:05:08.040> speaking 01:05:08.870 --> 01:05:08.880 align:start position:0% think that registering or then speaking 01:05:08.880 --> 01:05:11.329 align:start position:0% think that registering or then speaking about<01:05:09.059> legal<01:05:09.660> aspects<01:05:10.200> in<01:05:10.799> the<01:05:10.920> moment<01:05:11.160> of 01:05:11.329 --> 01:05:11.339 align:start position:0% about legal aspects in the moment of 01:05:11.339 --> 01:05:14.829 align:start position:0% about legal aspects in the moment of creation<01:05:11.640> kills<01:05:12.240> the<01:05:12.359> Bible<01:05:12.540> so<01:05:13.500> uh 01:05:14.829 --> 01:05:14.839 align:start position:0% creation kills the Bible so uh 01:05:14.839 --> 01:05:17.870 align:start position:0% creation kills the Bible so uh that<01:05:15.839> actually<01:05:15.960> gives<01:05:16.920> birth<01:05:17.220> to<01:05:17.460> a<01:05:17.640> lot<01:05:17.760> of 01:05:17.870 --> 01:05:17.880 align:start position:0% that actually gives birth to a lot of 01:05:17.880 --> 01:05:20.210 align:start position:0% that actually gives birth to a lot of problems<01:05:18.299> I<01:05:18.540> like<01:05:19.140> I've<01:05:19.319> been<01:05:19.559> up<01:05:19.799> you<01:05:20.160> know 01:05:20.210 --> 01:05:20.220 align:start position:0% problems I like I've been up you know 01:05:20.220 --> 01:05:23.210 align:start position:0% problems I like I've been up you know like<01:05:20.339> I've<01:05:20.520> had<01:05:20.760> problems<01:05:21.180> with<01:05:21.480> uh 01:05:23.210 --> 01:05:23.220 align:start position:0% like I've had problems with uh 01:05:23.220 --> 01:05:26.270 align:start position:0% like I've had problems with uh um<01:05:23.420> processes<01:05:24.420> in<01:05:24.839> which<01:05:25.079> I<01:05:25.559> have<01:05:25.740> been<01:05:25.920> in<01:05:26.220> the 01:05:26.270 --> 01:05:26.280 align:start position:0% um processes in which I have been in the 01:05:26.280 --> 01:05:28.430 align:start position:0% um processes in which I have been in the studio<01:05:26.400> I'm<01:05:26.640> a<01:05:26.760> music<01:05:26.880> producer<01:05:27.420> so<01:05:28.079> I<01:05:28.319> have 01:05:28.430 --> 01:05:28.440 align:start position:0% studio I'm a music producer so I have 01:05:28.440 --> 01:05:32.089 align:start position:0% studio I'm a music producer so I have been<01:05:28.619> in<01:05:28.740> a<01:05:28.920> studio<01:05:29.540> uh<01:05:30.540> We've<01:05:31.440> made<01:05:31.680> a<01:05:31.980> hit 01:05:32.089 --> 01:05:32.099 align:start position:0% been in a studio uh We've made a hit 01:05:32.099 --> 01:05:35.210 align:start position:0% been in a studio uh We've made a hit song<01:05:32.400> everybody<01:05:33.240> is<01:05:33.660> super<01:05:33.900> excited<01:05:34.500> right 01:05:35.210 --> 01:05:35.220 align:start position:0% song everybody is super excited right 01:05:35.220 --> 01:05:40.510 align:start position:0% song everybody is super excited right the<01:05:36.000> process<01:05:36.780> as<01:05:37.200> it<01:05:37.380> is<01:05:37.559> done<01:05:38.339> it<01:05:39.000> is<01:05:39.119> that<01:05:39.839> um 01:05:40.510 --> 01:05:40.520 align:start position:0% the process as it is done it is that um 01:05:40.520 --> 01:05:43.549 align:start position:0% the process as it is done it is that um at<01:05:41.520> least<01:05:41.640> in<01:05:41.819> music<01:05:42.140> creators<01:05:43.140> get<01:05:43.380> together 01:05:43.549 --> 01:05:43.559 align:start position:0% at least in music creators get together 01:05:43.559 --> 01:05:46.730 align:start position:0% at least in music creators get together in<01:05:43.920> a<01:05:44.040> studio<01:05:44.220> and<01:05:45.119> uh<01:05:45.480> they<01:05:46.020> songwrite<01:05:46.559> they 01:05:46.730 --> 01:05:46.740 align:start position:0% in a studio and uh they songwrite they 01:05:46.740 --> 01:05:49.490 align:start position:0% in a studio and uh they songwrite they beat<01:05:46.920> make<01:05:47.220> they<01:05:47.700> record<01:05:47.880> and<01:05:48.780> then<01:05:48.900> they<01:05:49.200> they 01:05:49.490 --> 01:05:49.500 align:start position:0% beat make they record and then they they 01:05:49.500 --> 01:05:52.549 align:start position:0% beat make they record and then they they bounce<01:05:49.920> off<01:05:50.280> the<01:05:50.640> audio<01:05:50.760> program<01:05:51.299> which<01:05:51.900> is<01:05:52.140> a 01:05:52.549 --> 01:05:52.559 align:start position:0% bounce off the audio program which is a 01:05:52.559 --> 01:05:54.890 align:start position:0% bounce off the audio program which is a a<01:05:53.160> WAV<01:05:53.460> file<01:05:53.640> or<01:05:53.819> an<01:05:53.940> MP3 01:05:54.890 --> 01:05:54.900 align:start position:0% a WAV file or an MP3 01:05:54.900 --> 01:05:58.370 align:start position:0% a WAV file or an MP3 and<01:05:55.559> then<01:05:55.740> that<01:05:56.099> MP3<01:05:56.520> gets<01:05:56.880> shared<01:05:57.180> among<01:05:57.599> the 01:05:58.370 --> 01:05:58.380 align:start position:0% and then that MP3 gets shared among the 01:05:58.380 --> 01:06:01.370 align:start position:0% and then that MP3 gets shared among the the<01:05:58.619> co-creators<01:05:59.339> and<01:05:59.880> it's<01:06:00.599> either<01:06:00.839> emailed 01:06:01.370 --> 01:06:01.380 align:start position:0% the co-creators and it's either emailed 01:06:01.380 --> 01:06:04.970 align:start position:0% the co-creators and it's either emailed to<01:06:01.500> us<01:06:01.680> or<01:06:02.040> it's<01:06:02.280> uh<01:06:02.700> WhatsApp<01:06:03.380> and<01:06:04.380> we<01:06:04.799> can 01:06:04.970 --> 01:06:04.980 align:start position:0% to us or it's uh WhatsApp and we can 01:06:04.980 --> 01:06:08.150 align:start position:0% to us or it's uh WhatsApp and we can listen<01:06:05.339> to<01:06:05.819> the<01:06:06.420> music<01:06:06.599> or<01:06:07.319> what<01:06:07.559> we<01:06:07.740> made<01:06:07.920> and 01:06:08.150 --> 01:06:08.160 align:start position:0% listen to the music or what we made and 01:06:08.160 --> 01:06:11.270 align:start position:0% listen to the music or what we made and vibe<01:06:08.520> to<01:06:08.579> it<01:06:08.760> and<01:06:09.720> uh 01:06:11.270 --> 01:06:11.280 align:start position:0% vibe to it and uh 01:06:11.280 --> 01:06:13.730 align:start position:0% vibe to it and uh hopefully<01:06:11.760> the<01:06:11.940> next<01:06:12.119> day<01:06:12.359> know<01:06:12.660> if<01:06:13.140> what<01:06:13.619> we 01:06:13.730 --> 01:06:13.740 align:start position:0% hopefully the next day know if what we 01:06:13.740 --> 01:06:15.650 align:start position:0% hopefully the next day know if what we did<01:06:13.920> was<01:06:14.099> whack<01:06:14.400> or<01:06:14.880> if<01:06:15.000> it's<01:06:15.180> a<01:06:15.299> hit<01:06:15.420> record 01:06:15.650 --> 01:06:15.660 align:start position:0% did was whack or if it's a hit record 01:06:15.660 --> 01:06:17.030 align:start position:0% did was whack or if it's a hit record right 01:06:17.030 --> 01:06:17.040 align:start position:0% right 01:06:17.040 --> 01:06:17.809 align:start position:0% right um 01:06:17.809 --> 01:06:17.819 align:start position:0% um 01:06:17.819 --> 01:06:20.690 align:start position:0% um so 01:06:20.690 --> 01:06:20.700 align:start position:0% 01:06:20.700 --> 01:06:22.370 align:start position:0% personally<01:06:21.420> I<01:06:21.720> have<01:06:21.839> been<01:06:22.020> in<01:06:22.200> those 01:06:22.370 --> 01:06:22.380 align:start position:0% personally I have been in those 01:06:22.380 --> 01:06:24.829 align:start position:0% personally I have been in those situations<01:06:22.799> and<01:06:23.400> I<01:06:23.700> have<01:06:23.819> been<01:06:24.119> muscled<01:06:24.720> out 01:06:24.829 --> 01:06:24.839 align:start position:0% situations and I have been muscled out 01:06:24.839 --> 01:06:28.789 align:start position:0% situations and I have been muscled out or<01:06:25.020> cut<01:06:25.200> out<01:06:25.380> of<01:06:26.160> hit<01:06:26.819> records<01:06:27.420> because<01:06:27.799> the 01:06:28.789 --> 01:06:28.799 align:start position:0% or cut out of hit records because the 01:06:28.799 --> 01:06:32.150 align:start position:0% or cut out of hit records because the more<01:06:28.980> Savvy<01:06:29.520> people<01:06:29.720> will<01:06:30.720> head<01:06:31.619> out<01:06:31.799> and 01:06:32.150 --> 01:06:32.160 align:start position:0% more Savvy people will head out and 01:06:32.160 --> 01:06:35.349 align:start position:0% more Savvy people will head out and register<01:06:32.780> the<01:06:33.780> the<01:06:34.079> copyright<01:06:34.559> of<01:06:34.799> the<01:06:34.920> song 01:06:35.349 --> 01:06:35.359 align:start position:0% register the the copyright of the song 01:06:35.359 --> 01:06:38.930 align:start position:0% register the the copyright of the song and<01:06:36.359> this<01:06:37.079> is<01:06:37.200> a<01:06:37.380> story<01:06:37.559> that<01:06:37.980> kind<01:06:38.640> of<01:06:38.760> like 01:06:38.930 --> 01:06:38.940 align:start position:0% and this is a story that kind of like 01:06:38.940 --> 01:06:42.950 align:start position:0% and this is a story that kind of like repeats<01:06:39.720> itself<01:06:40.020> endlessly<01:06:40.799> in<01:06:42.240> um<01:06:42.299> in<01:06:42.839> music 01:06:42.950 --> 01:06:42.960 align:start position:0% repeats itself endlessly in um in music 01:06:42.960 --> 01:06:45.470 align:start position:0% repeats itself endlessly in um in music making<01:06:43.319> so<01:06:43.740> what<01:06:44.339> would<01:06:44.520> the<01:06:44.760> ideal<01:06:45.059> process 01:06:45.470 --> 01:06:45.480 align:start position:0% making so what would the ideal process 01:06:45.480 --> 01:06:47.029 align:start position:0% making so what would the ideal process be 01:06:47.029 --> 01:06:47.039 align:start position:0% be 01:06:47.039 --> 01:06:49.430 align:start position:0% be the<01:06:47.520> ideal<01:06:47.819> process<01:06:48.119> would<01:06:48.240> be<01:06:48.359> would<01:06:48.599> be<01:06:49.020> to 01:06:49.430 --> 01:06:49.440 align:start position:0% the ideal process would be would be to 01:06:49.440 --> 01:06:50.870 align:start position:0% the ideal process would be would be to register 01:06:50.870 --> 01:06:50.880 align:start position:0% register 01:06:50.880 --> 01:06:53.150 align:start position:0% register to<01:06:51.299> have<01:06:51.420> a<01:06:51.539> mechanism<01:06:51.900> to<01:06:52.200> register<01:06:52.500> the<01:06:52.859> IP 01:06:53.150 --> 01:06:53.160 align:start position:0% to have a mechanism to register the IP 01:06:53.160 --> 01:06:54.230 align:start position:0% to have a mechanism to register the IP as 01:06:54.230 --> 01:06:54.240 align:start position:0% as 01:06:54.240 --> 01:06:59.510 align:start position:0% as soon<01:06:54.839> as<01:06:55.020> possible<01:06:55.440> Right<01:06:56.039> in<01:06:56.880> a<01:06:57.059> nutshell<01:06:57.420> a 01:06:59.510 --> 01:06:59.520 align:start position:0% soon as possible Right in a nutshell a 01:06:59.520 --> 01:07:01.730 align:start position:0% soon as possible Right in a nutshell a in<01:06:59.880> a<01:07:00.119> nutshell<01:07:00.359> it<01:07:00.839> would<01:07:01.200> protect<01:07:01.559> the 01:07:01.730 --> 01:07:01.740 align:start position:0% in a nutshell it would protect the 01:07:01.740 --> 01:07:04.370 align:start position:0% in a nutshell it would protect the creators<01:07:02.220> and<01:07:02.880> hopefully 01:07:04.370 --> 01:07:04.380 align:start position:0% creators and hopefully 01:07:04.380 --> 01:07:06.230 align:start position:0% creators and hopefully in<01:07:04.920> consensus 01:07:06.230 --> 01:07:06.240 align:start position:0% in consensus 01:07:06.240 --> 01:07:08.990 align:start position:0% in consensus be<01:07:06.599> able<01:07:06.839> to<01:07:06.960> register<01:07:07.619> this<01:07:07.920> IP<01:07:08.220> in<01:07:08.460> consensus 01:07:08.990 --> 01:07:09.000 align:start position:0% be able to register this IP in consensus 01:07:09.000 --> 01:07:11.349 align:start position:0% be able to register this IP in consensus right<01:07:09.480> so 01:07:11.349 --> 01:07:11.359 align:start position:0% right so 01:07:11.359 --> 01:07:13.190 align:start position:0% right so we 01:07:13.190 --> 01:07:13.200 align:start position:0% we 01:07:13.200 --> 01:07:15.470 align:start position:0% we have<01:07:13.680> a<01:07:13.859> solution<01:07:14.160> right<01:07:14.700> we<01:07:15.000> have<01:07:15.119> temp 01:07:15.470 --> 01:07:15.480 align:start position:0% have a solution right we have temp 01:07:15.480 --> 01:07:19.069 align:start position:0% have a solution right we have temp temporarily<01:07:16.200> called<01:07:16.440> it<01:07:16.740> a<01:07:17.339> copyright<01:07:17.760> wallet 01:07:19.069 --> 01:07:19.079 align:start position:0% temporarily called it a copyright wallet 01:07:19.079 --> 01:07:21.710 align:start position:0% temporarily called it a copyright wallet and<01:07:19.799> a<01:07:19.980> copyright<01:07:20.339> wallet 01:07:21.710 --> 01:07:21.720 align:start position:0% and a copyright wallet 01:07:21.720 --> 01:07:24.710 align:start position:0% and a copyright wallet it<01:07:22.559> allows<01:07:23.039> it's<01:07:23.280> a<01:07:23.520> tool<01:07:23.819> basically<01:07:24.359> it's<01:07:24.539> a 01:07:24.710 --> 01:07:24.720 align:start position:0% it allows it's a tool basically it's a 01:07:24.720 --> 01:07:26.690 align:start position:0% it allows it's a tool basically it's a tool<01:07:24.960> that<01:07:25.140> is<01:07:25.319> inserted<01:07:25.859> in<01:07:26.099> the<01:07:26.220> job<01:07:26.339> to<01:07:26.579> be 01:07:26.690 --> 01:07:26.700 align:start position:0% tool that is inserted in the job to be 01:07:26.700 --> 01:07:28.789 align:start position:0% tool that is inserted in the job to be done<01:07:26.880> it's<01:07:27.180> a<01:07:27.480> you<01:07:27.900> know<01:07:27.960> like<01:07:28.079> a<01:07:28.260> small<01:07:28.380> sharp 01:07:28.789 --> 01:07:28.799 align:start position:0% done it's a you know like a small sharp 01:07:28.799 --> 01:07:31.190 align:start position:0% done it's a you know like a small sharp tool<01:07:29.099> that<01:07:29.280> is<01:07:29.400> inserted<01:07:29.819> in<01:07:29.940> a<01:07:30.240> job<01:07:30.660> CB<01:07:30.960> Dom 01:07:31.190 --> 01:07:31.200 align:start position:0% tool that is inserted in a job CB Dom 01:07:31.200 --> 01:07:35.270 align:start position:0% tool that is inserted in a job CB Dom process<01:07:31.500> and<01:07:31.740> it<01:07:31.980> allows<01:07:32.460> for<01:07:33.559> in<01:07:34.559> multiplayer 01:07:35.270 --> 01:07:35.280 align:start position:0% process and it allows for in multiplayer 01:07:35.280 --> 01:07:37.430 align:start position:0% process and it allows for in multiplayer mode<01:07:35.460> deploying 01:07:37.430 --> 01:07:37.440 align:start position:0% mode deploying 01:07:37.440 --> 01:07:40.190 align:start position:0% mode deploying uh<01:07:38.359> registry 01:07:40.190 --> 01:07:40.200 align:start position:0% uh registry 01:07:40.200 --> 01:07:42.349 align:start position:0% uh registry time<01:07:40.619> stamping<01:07:41.099> a<01:07:41.280> registry<01:07:41.700> on<01:07:42.180> the 01:07:42.349 --> 01:07:42.359 align:start position:0% time stamping a registry on the 01:07:42.359 --> 01:07:47.390 align:start position:0% time stamping a registry on the blockchain<01:07:42.720> of<01:07:43.619> that<01:07:43.799> intellectual<01:07:44.520> property 01:07:47.390 --> 01:07:47.400 align:start position:0% 01:07:47.400 --> 01:07:50.809 align:start position:0% so 01:07:50.809 --> 01:07:50.819 align:start position:0% 01:07:50.819 --> 01:07:53.809 align:start position:0% this<01:07:51.599> is<01:07:51.720> the<01:07:52.079> sign<01:07:52.260> coming<01:07:52.500> from<01:07:52.740> a<01:07:52.859> musician 01:07:53.809 --> 01:07:53.819 align:start position:0% this is the sign coming from a musician 01:07:53.819 --> 01:08:00.710 align:start position:0% this is the sign coming from a musician right<01:07:54.359> but<01:07:54.720> in<01:07:55.079> essence<01:07:55.319> what<01:07:55.559> it<01:07:55.680> is<01:07:55.799> is<01:07:56.039> a 01:08:00.710 --> 01:08:00.720 align:start position:0% 01:08:00.720 --> 01:08:03.470 align:start position:0% an<01:08:01.140> application<01:08:01.559> an<01:08:01.799> extension<01:08:02.280> an<01:08:03.000> extension 01:08:03.470 --> 01:08:03.480 align:start position:0% an application an extension an extension 01:08:03.480 --> 01:08:04.309 align:start position:0% an application an extension an extension app 01:08:04.309 --> 01:08:04.319 align:start position:0% app 01:08:04.319 --> 01:08:07.849 align:start position:0% app that<01:08:05.099> would<01:08:05.339> uh<01:08:05.640> register<01:08:06.059> the<01:08:06.539> title<01:08:06.900> of<01:08:07.680> the 01:08:07.849 --> 01:08:07.859 align:start position:0% that would uh register the title of the 01:08:07.859 --> 01:08:09.829 align:start position:0% that would uh register the title of the song<01:08:08.039> let's<01:08:08.339> say<01:08:08.520> in<01:08:08.700> this<01:08:08.880> case 01:08:09.829 --> 01:08:09.839 align:start position:0% song let's say in this case 01:08:09.839 --> 01:08:12.770 align:start position:0% song let's say in this case the<01:08:10.380> ownership<01:08:10.680> splits<01:08:11.640> of<01:08:11.880> the<01:08:12.180> participants 01:08:12.770 --> 01:08:12.780 align:start position:0% the ownership splits of the participants 01:08:12.780 --> 01:08:15.289 align:start position:0% the ownership splits of the participants and<01:08:13.680> a<01:08:13.859> mechanism<01:08:14.220> to<01:08:14.460> drag 01:08:15.289 --> 01:08:15.299 align:start position:0% and a mechanism to drag 01:08:15.299 --> 01:08:17.510 align:start position:0% and a mechanism to drag and<01:08:15.780> drop<01:08:15.960> the<01:08:16.259> media 01:08:17.510 --> 01:08:17.520 align:start position:0% and drop the media 01:08:17.520 --> 01:08:20.570 align:start position:0% and drop the media the<01:08:18.060> same<01:08:18.179> way<01:08:18.420> the<01:08:18.660> uh 01:08:20.570 --> 01:08:20.580 align:start position:0% the same way the uh 01:08:20.580 --> 01:08:24.590 align:start position:0% the same way the uh uh<01:08:21.359> a<01:08:21.480> a<01:08:21.920> chat<01:08:22.920> with<01:08:23.219> you<01:08:23.520> know<01:08:23.580> like<01:08:23.759> have 01:08:24.590 --> 01:08:24.600 align:start position:0% uh a a chat with you know like have 01:08:24.600 --> 01:08:27.709 align:start position:0% uh a a chat with you know like have access<01:08:24.839> to<01:08:25.140> to<01:08:25.880> listening<01:08:26.880> to<01:08:26.940> a<01:08:27.120> voicemail<01:08:27.420> or 01:08:27.709 --> 01:08:27.719 align:start position:0% access to to listening to a voicemail or 01:08:27.719 --> 01:08:30.470 align:start position:0% access to to listening to a voicemail or or<01:08:28.140> a<01:08:28.380> shared<01:08:28.620> audio<01:08:28.799> the<01:08:29.640> mobile<01:08:29.759> wallets<01:08:30.299> of 01:08:30.470 --> 01:08:30.480 align:start position:0% or a shared audio the mobile wallets of 01:08:30.480 --> 01:08:32.390 align:start position:0% or a shared audio the mobile wallets of the<01:08:30.600> participants<01:08:31.199> would<01:08:31.859> receive<01:08:32.160> that 01:08:32.390 --> 01:08:32.400 align:start position:0% the participants would receive that 01:08:32.400 --> 01:08:33.709 align:start position:0% the participants would receive that audio<01:08:32.580> and<01:08:33.060> they<01:08:33.239> will<01:08:33.359> receive<01:08:33.600> a 01:08:33.709 --> 01:08:33.719 align:start position:0% audio and they will receive a 01:08:33.719 --> 01:08:35.510 align:start position:0% audio and they will receive a notification<01:08:34.259> too 01:08:35.510 --> 01:08:35.520 align:start position:0% notification too 01:08:35.520 --> 01:08:37.789 align:start position:0% notification too accept<01:08:36.060> or<01:08:36.540> deny 01:08:37.789 --> 01:08:37.799 align:start position:0% accept or deny 01:08:37.799 --> 01:08:41.209 align:start position:0% accept or deny their<01:08:38.400> participation<01:08:39.000> in<01:08:39.359> the<01:08:39.600> in<01:08:40.500> the<01:08:40.739> in 01:08:41.209 --> 01:08:41.219 align:start position:0% their participation in the in the in 01:08:41.219 --> 01:08:43.490 align:start position:0% their participation in the in the in that<01:08:41.460> creative<01:08:41.880> process<01:08:42.359> and<01:08:43.020> if<01:08:43.199> there<01:08:43.380> is 01:08:43.490 --> 01:08:43.500 align:start position:0% that creative process and if there is 01:08:43.500 --> 01:08:47.090 align:start position:0% that creative process and if there is consensus<01:08:44.179> then<01:08:45.179> a<01:08:45.600> smart<01:08:45.839> contract<01:08:46.380> is 01:08:47.090 --> 01:08:47.100 align:start position:0% consensus then a smart contract is 01:08:47.100 --> 01:08:48.110 align:start position:0% consensus then a smart contract is deployed 01:08:48.110 --> 01:08:48.120 align:start position:0% deployed 01:08:48.120 --> 01:08:51.650 align:start position:0% deployed and<01:08:48.779> the<01:08:48.960> non-transferable<01:08:49.679> nft<01:08:50.040> is<01:08:50.400> minted 01:08:51.650 --> 01:08:51.660 align:start position:0% and the non-transferable nft is minted 01:08:51.660 --> 01:08:59.269 align:start position:0% and the non-transferable nft is minted as<01:08:52.319> registry 01:08:59.269 --> 01:08:59.279 align:start position:0% 01:08:59.279 --> 01:09:02.269 align:start position:0% so<01:08:59.940> and<01:09:00.660> before<01:09:00.839> we<01:09:01.080> go<01:09:01.319> to<01:09:01.440> Future<01:09:01.799> iterations 01:09:02.269 --> 01:09:02.279 align:start position:0% so and before we go to Future iterations 01:09:02.279 --> 01:09:04.789 align:start position:0% so and before we go to Future iterations I<01:09:02.580> would<01:09:02.699> like<01:09:02.880> to<01:09:03.000> obviously<01:09:03.960> uh<01:09:04.440> I<01:09:04.679> think 01:09:04.789 --> 01:09:04.799 align:start position:0% I would like to obviously uh I think 01:09:04.799 --> 01:09:07.669 align:start position:0% I would like to obviously uh I think this<01:09:05.100> is<01:09:05.219> time<01:09:05.819> better<01:09:06.120> spent<01:09:06.420> if<01:09:06.839> we<01:09:07.020> if<01:09:07.440> we 01:09:07.669 --> 01:09:07.679 align:start position:0% this is time better spent if we if we 01:09:07.679 --> 01:09:10.010 align:start position:0% this is time better spent if we if we open<01:09:07.739> up<01:09:08.040> a<01:09:08.819> discussions<01:09:09.299> because<01:09:09.540> I<01:09:09.900> mean 01:09:10.010 --> 01:09:10.020 align:start position:0% open up a discussions because I mean 01:09:10.020 --> 01:09:13.849 align:start position:0% open up a discussions because I mean this<01:09:10.199> could<01:09:10.380> be<01:09:10.699> a<01:09:11.699> a<01:09:12.239> tool<01:09:12.660> that<01:09:12.859> obviously 01:09:13.849 --> 01:09:13.859 align:start position:0% this could be a a tool that obviously 01:09:13.859 --> 01:09:16.309 align:start position:0% this could be a a tool that obviously expand<01:09:14.279> and<01:09:14.520> is<01:09:14.759> composed<01:09:15.299> on<01:09:15.779> but<01:09:16.080> I<01:09:16.259> would 01:09:16.309 --> 01:09:16.319 align:start position:0% expand and is composed on but I would 01:09:16.319 --> 01:09:19.189 align:start position:0% expand and is composed on but I would like<01:09:16.500> to<01:09:16.739> basically<01:09:17.580> just<01:09:18.299> open<01:09:18.480> the<01:09:18.779> floor<01:09:18.960> to 01:09:19.189 --> 01:09:19.199 align:start position:0% like to basically just open the floor to 01:09:19.199 --> 01:09:23.150 align:start position:0% like to basically just open the floor to questions<01:09:19.500> to<01:09:19.980> see<01:09:20.100> if<01:09:20.279> uh<01:09:21.179> if<01:09:21.719> uh 01:09:23.150 --> 01:09:23.160 align:start position:0% questions to see if uh if uh 01:09:23.160 --> 01:09:25.430 align:start position:0% questions to see if uh if uh if<01:09:23.640> we<01:09:23.819> can<01:09:23.940> get<01:09:24.120> to<01:09:24.299> a<01:09:24.600> technical<01:09:25.080> solution 01:09:25.430 --> 01:09:25.440 align:start position:0% if we can get to a technical solution 01:09:25.440 --> 01:09:27.410 align:start position:0% if we can get to a technical solution because<01:09:25.739> the<01:09:26.100> question<01:09:26.279> that<01:09:26.580> like<01:09:26.819> the 01:09:27.410 --> 01:09:27.420 align:start position:0% because the question that like the 01:09:27.420 --> 01:09:30.050 align:start position:0% because the question that like the questions<01:09:27.600> that<01:09:28.259> we<01:09:28.440> have<01:09:28.620> is<01:09:29.520> in<01:09:29.759> the<01:09:29.940> main 01:09:30.050 --> 01:09:30.060 align:start position:0% questions that we have is in the main 01:09:30.060 --> 01:09:32.630 align:start position:0% questions that we have is in the main question<01:09:30.239> we<01:09:30.779> have<01:09:30.900> is<01:09:31.380> does<01:09:32.100> this<01:09:32.460> really 01:09:32.630 --> 01:09:32.640 align:start position:0% question we have is does this really 01:09:32.640 --> 01:09:36.169 align:start position:0% question we have is does this really need<01:09:32.880> to<01:09:33.000> be<01:09:33.120> a<01:09:33.359> wallet<01:09:33.719> or<01:09:34.560> can<01:09:34.799> it<01:09:34.980> be 01:09:36.169 --> 01:09:36.179 align:start position:0% need to be a wallet or can it be 01:09:36.179 --> 01:09:37.370 align:start position:0% need to be a wallet or can it be a 01:09:37.370 --> 01:09:37.380 align:start position:0% a 01:09:37.380 --> 01:09:44.390 align:start position:0% a can<01:09:37.799> it<01:09:37.980> be<01:09:38.480> a<01:09:39.620> built<01:09:40.620> in<01:09:41.520> a<01:09:41.640> simpler<01:09:42.000> way 01:09:44.390 --> 01:09:44.400 align:start position:0% 01:09:44.400 --> 01:09:46.490 align:start position:0% so<01:09:44.940> thank<01:09:45.239> you<01:09:45.359> Andres 01:09:46.490 --> 01:09:46.500 align:start position:0% so thank you Andres 01:09:46.500 --> 01:09:49.070 align:start position:0% so thank you Andres um<01:09:46.620> do<01:09:47.160> we<01:09:47.339> have<01:09:47.460> questions<01:09:47.759> feedback<01:09:48.600> raise 01:09:49.070 --> 01:09:49.080 align:start position:0% um do we have questions feedback raise 01:09:49.080 --> 01:09:51.110 align:start position:0% um do we have questions feedback raise your<01:09:49.319> hand<01:09:49.440> please<01:09:49.739> yes 01:09:51.110 --> 01:09:51.120 align:start position:0% your hand please yes 01:09:51.120 --> 01:09:56.090 align:start position:0% your hand please yes see<01:09:51.600> you 01:09:56.090 --> 01:09:56.100 align:start position:0% 01:09:56.100 --> 01:09:57.350 align:start position:0% thanks 01:09:57.350 --> 01:09:57.360 align:start position:0% thanks 01:09:57.360 --> 01:09:59.330 align:start position:0% thanks um<01:09:57.960> maybe<01:09:58.500> we<01:09:58.679> could<01:09:58.800> go<01:09:58.980> back<01:09:59.100> to<01:09:59.219> the 01:09:59.330 --> 01:09:59.340 align:start position:0% um maybe we could go back to the 01:09:59.340 --> 01:10:00.709 align:start position:0% um maybe we could go back to the previous<01:09:59.520> slide<01:09:59.880> I<01:10:00.179> just<01:10:00.239> had<01:10:00.360> a<01:10:00.540> question 01:10:00.709 --> 01:10:00.719 align:start position:0% previous slide I just had a question 01:10:00.719 --> 01:10:02.270 align:start position:0% previous slide I just had a question about<01:10:01.080> like<01:10:01.440> what<01:10:01.679> you're<01:10:01.800> saying<01:10:02.100> in 01:10:02.270 --> 01:10:02.280 align:start position:0% about like what you're saying in 01:10:02.280 --> 01:10:03.830 align:start position:0% about like what you're saying in ownership<01:10:02.580> splits<01:10:03.179> and<01:10:03.480> it's<01:10:03.600> kind<01:10:03.780> of 01:10:03.830 --> 01:10:03.840 align:start position:0% ownership splits and it's kind of 01:10:03.840 --> 01:10:04.850 align:start position:0% ownership splits and it's kind of related<01:10:04.020> to<01:10:04.199> what<01:10:04.320> you<01:10:04.440> were<01:10:04.560> saying<01:10:04.679> where 01:10:04.850 --> 01:10:04.860 align:start position:0% related to what you were saying where 01:10:04.860 --> 01:10:07.010 align:start position:0% related to what you were saying where like<01:10:05.100> ownership<01:10:05.820> splits<01:10:06.300> are<01:10:06.420> more<01:10:06.600> than<01:10:06.780> just 01:10:07.010 --> 01:10:07.020 align:start position:0% like ownership splits are more than just 01:10:07.020 --> 01:10:09.350 align:start position:0% like ownership splits are more than just like<01:10:07.260> who's<01:10:08.100> getting<01:10:08.400> what<01:10:08.699> percentage<01:10:09.120> of 01:10:09.350 --> 01:10:09.360 align:start position:0% like who's getting what percentage of 01:10:09.360 --> 01:10:10.850 align:start position:0% like who's getting what percentage of like<01:10:09.600> mint<01:10:09.840> revenue<01:10:10.199> or<01:10:10.440> something<01:10:10.560> like<01:10:10.739> that 01:10:10.850 --> 01:10:10.860 align:start position:0% like mint revenue or something like that 01:10:10.860 --> 01:10:12.890 align:start position:0% like mint revenue or something like that it's<01:10:11.040> much<01:10:11.219> more<01:10:11.460> so<01:10:11.699> when<01:10:11.880> you're<01:10:12.060> in<01:10:12.719> that 01:10:12.890 --> 01:10:12.900 align:start position:0% it's much more so when you're in that 01:10:12.900 --> 01:10:14.750 align:start position:0% it's much more so when you're in that top<01:10:13.020> left<01:10:13.199> corner<01:10:13.560> when<01:10:13.679> you<01:10:13.860> say<01:10:14.040> ownership 01:10:14.750 --> 01:10:14.760 align:start position:0% top left corner when you say ownership 01:10:14.760 --> 01:10:17.090 align:start position:0% top left corner when you say ownership splits<01:10:15.300> are<01:10:15.840> you<01:10:16.020> already<01:10:16.140> like<01:10:16.500> envisioning 01:10:17.090 --> 01:10:17.100 align:start position:0% splits are you already like envisioning 01:10:17.100 --> 01:10:18.650 align:start position:0% splits are you already like envisioning this<01:10:17.219> like<01:10:17.460> breaking<01:10:18.060> down<01:10:18.179> into<01:10:18.360> like 01:10:18.650 --> 01:10:18.660 align:start position:0% this like breaking down into like 01:10:18.660 --> 01:10:20.870 align:start position:0% this like breaking down into like mechanical<01:10:19.320> and<01:10:19.560> like<01:10:19.739> publishing<01:10:20.159> royalties 01:10:20.870 --> 01:10:20.880 align:start position:0% mechanical and like publishing royalties 01:10:20.880 --> 01:10:23.570 align:start position:0% mechanical and like publishing royalties or<01:10:21.239> are<01:10:21.600> you<01:10:21.780> trying<01:10:21.900> to<01:10:22.020> not<01:10:22.280> necessarily<01:10:23.280> be 01:10:23.570 --> 01:10:23.580 align:start position:0% or are you trying to not necessarily be 01:10:23.580 --> 01:10:26.390 align:start position:0% or are you trying to not necessarily be skeuomorphic<01:10:24.420> and<01:10:24.719> instead<01:10:25.620> do<01:10:25.800> other<01:10:26.040> types 01:10:26.390 --> 01:10:26.400 align:start position:0% skeuomorphic and instead do other types 01:10:26.400 --> 01:10:28.370 align:start position:0% skeuomorphic and instead do other types of<01:10:26.460> ownership<01:10:26.699> splits<01:10:27.179> or<01:10:27.360> what's<01:10:27.840> what's<01:10:28.140> the 01:10:28.370 --> 01:10:28.380 align:start position:0% of ownership splits or what's what's the 01:10:28.380 --> 01:10:30.649 align:start position:0% of ownership splits or what's what's the idea<01:10:28.739> here<01:10:28.920> I<01:10:29.400> guess<01:10:29.699> a<01:10:29.940> greater<01:10:30.480> question 01:10:30.649 --> 01:10:30.659 align:start position:0% idea here I guess a greater question 01:10:30.659 --> 01:10:33.590 align:start position:0% idea here I guess a greater question that<01:10:30.960> just<01:10:31.320> how<01:10:31.800> much<01:10:31.920> of<01:10:32.100> the<01:10:32.280> current<01:10:32.600> music 01:10:33.590 --> 01:10:33.600 align:start position:0% that just how much of the current music 01:10:33.600 --> 01:10:35.570 align:start position:0% that just how much of the current music industry<01:10:34.080> are<01:10:34.260> we<01:10:34.440> trying<01:10:34.620> to<01:10:34.739> recreate<01:10:35.219> on 01:10:35.570 --> 01:10:35.580 align:start position:0% industry are we trying to recreate on 01:10:35.580 --> 01:10:37.910 align:start position:0% industry are we trying to recreate on Chain<01:10:35.820> versus<01:10:36.179> maybe<01:10:36.900> moving<01:10:37.320> to<01:10:37.500> stuff 01:10:37.910 --> 01:10:37.920 align:start position:0% Chain versus maybe moving to stuff 01:10:37.920 --> 01:10:39.770 align:start position:0% Chain versus maybe moving to stuff that's<01:10:38.100> better<01:10:38.460> in<01:10:38.940> some<01:10:39.060> way<01:10:39.179> not<01:10:39.540> that<01:10:39.659> I 01:10:39.770 --> 01:10:39.780 align:start position:0% that's better in some way not that I 01:10:39.780 --> 01:10:42.290 align:start position:0% that's better in some way not that I even<01:10:39.960> know<01:10:40.140> that's<01:10:40.440> better<01:10:40.739> but<01:10:40.980> yeah 01:10:42.290 --> 01:10:42.300 align:start position:0% even know that's better but yeah 01:10:42.300 --> 01:10:44.450 align:start position:0% even know that's better but yeah yeah<01:10:42.840> that's<01:10:43.080> a<01:10:43.260> good<01:10:43.380> question<01:10:43.560> and<01:10:43.860> and<01:10:44.219> the 01:10:44.450 --> 01:10:44.460 align:start position:0% yeah that's a good question and and the 01:10:44.460 --> 01:10:48.590 align:start position:0% yeah that's a good question and and the answer<01:10:44.640> would<01:10:45.300> be<01:10:45.560> a<01:10:46.560> either<01:10:46.980> we 01:10:48.590 --> 01:10:48.600 align:start position:0% answer would be a either we 01:10:48.600 --> 01:10:51.530 align:start position:0% answer would be a either we um<01:10:48.659> one<01:10:49.440> of<01:10:49.560> two<01:10:49.980> answers<01:10:50.219> it 01:10:51.530 --> 01:10:51.540 align:start position:0% um one of two answers it 01:10:51.540 --> 01:10:54.649 align:start position:0% um one of two answers it I'm<01:10:52.020> guessing<01:10:52.320> the<01:10:52.500> the<01:10:52.620> Dynamics<01:10:53.300> uh<01:10:54.300> the 01:10:54.649 --> 01:10:54.659 align:start position:0% I'm guessing the the Dynamics uh the 01:10:54.659 --> 01:10:56.570 align:start position:0% I'm guessing the the Dynamics uh the current<01:10:54.780> Dynamics<01:10:55.260> are<01:10:55.679> more<01:10:55.860> of<01:10:56.040> like<01:10:56.219> you 01:10:56.570 --> 01:10:56.580 align:start position:0% current Dynamics are more of like you 01:10:56.580 --> 01:10:59.630 align:start position:0% current Dynamics are more of like you songwrite<01:10:57.300> and<01:10:57.540> you<01:10:57.659> fixate<01:10:58.080> on<01:10:58.500> a<01:10:58.739> on<01:10:59.400> a 01:10:59.630 --> 01:10:59.640 align:start position:0% songwrite and you fixate on a on a 01:10:59.640 --> 01:11:02.390 align:start position:0% songwrite and you fixate on a on a recording<01:11:00.360> immediately<01:11:01.080> right<01:11:01.920> just<01:11:02.219> because 01:11:02.390 --> 01:11:02.400 align:start position:0% recording immediately right just because 01:11:02.400 --> 01:11:04.130 align:start position:0% recording immediately right just because the<01:11:02.640> tools<01:11:02.940> are<01:11:03.060> available<01:11:03.179> so<01:11:03.600> people<01:11:03.840> are 01:11:04.130 --> 01:11:04.140 align:start position:0% the tools are available so people are 01:11:04.140 --> 01:11:07.669 align:start position:0% the tools are available so people are not<01:11:04.800> writing<01:11:05.400> songs<01:11:06.239> with<01:11:06.780> their<01:11:06.960> guitar<01:11:07.199> but 01:11:07.669 --> 01:11:07.679 align:start position:0% not writing songs with their guitar but 01:11:07.679 --> 01:11:09.470 align:start position:0% not writing songs with their guitar but they<01:11:07.980> just<01:11:08.159> fixed<01:11:08.460> like<01:11:08.760> they<01:11:09.000> just<01:11:09.120> record 01:11:09.470 --> 01:11:09.480 align:start position:0% they just fixed like they just record 01:11:09.480 --> 01:11:11.750 align:start position:0% they just fixed like they just record them<01:11:09.900> immediately<01:11:10.440> and<01:11:11.159> that<01:11:11.340> is<01:11:11.460> just 01:11:11.750 --> 01:11:11.760 align:start position:0% them immediately and that is just 01:11:11.760 --> 01:11:14.270 align:start position:0% them immediately and that is just because<01:11:11.880> we<01:11:12.179> have<01:11:12.300> the<01:11:12.420> tools<01:11:12.719> to<01:11:12.840> do<01:11:12.960> it<01:11:13.280> uh 01:11:14.270 --> 01:11:14.280 align:start position:0% because we have the tools to do it uh 01:11:14.280 --> 01:11:15.950 align:start position:0% because we have the tools to do it uh unlike<01:11:14.640> before<01:11:14.880> we<01:11:15.239> used<01:11:15.420> to<01:11:15.540> like<01:11:15.659> Write 01:11:15.950 --> 01:11:15.960 align:start position:0% unlike before we used to like Write 01:11:15.960 --> 01:11:18.950 align:start position:0% unlike before we used to like Write Sheet<01:11:16.380> Music<01:11:16.620> or<01:11:17.100> or<01:11:17.400> write<01:11:17.880> song<01:11:18.239> there<01:11:18.600> a 01:11:18.950 --> 01:11:18.960 align:start position:0% Sheet Music or or write song there a 01:11:18.960 --> 01:11:20.649 align:start position:0% Sheet Music or or write song there a lyrics<01:11:19.440> on<01:11:19.800> paper 01:11:20.649 --> 01:11:20.659 align:start position:0% lyrics on paper 01:11:20.659 --> 01:11:24.410 align:start position:0% lyrics on paper uh<01:11:21.659> so<01:11:22.440> but<01:11:22.739> the<01:11:22.980> but<01:11:23.340> I<01:11:23.520> guess<01:11:23.640> the 01:11:24.410 --> 01:11:24.420 align:start position:0% uh so but the but I guess the 01:11:24.420 --> 01:11:26.810 align:start position:0% uh so but the but I guess the the<01:11:24.780> answer<01:11:25.080> to<01:11:25.320> that<01:11:25.500> would<01:11:25.679> be<01:11:25.800> we<01:11:26.100> could 01:11:26.810 --> 01:11:26.820 align:start position:0% the answer to that would be we could 01:11:26.820 --> 01:11:30.890 align:start position:0% the answer to that would be we could either<01:11:27.179> do<01:11:27.480> two<01:11:27.900> Registries<01:11:28.380> or<01:11:29.340> just<01:11:29.580> split 01:11:30.890 --> 01:11:30.900 align:start position:0% either do two Registries or just split 01:11:30.900 --> 01:11:34.250 align:start position:0% either do two Registries or just split uh<01:11:31.739> percentages<01:11:32.219> because<01:11:32.520> at<01:11:32.760> the<01:11:32.880> same<01:11:33.000> time 01:11:34.250 --> 01:11:34.260 align:start position:0% uh percentages because at the same time 01:11:34.260 --> 01:11:36.530 align:start position:0% uh percentages because at the same time you<01:11:34.679> know<01:11:34.739> like<01:11:34.920> writing<01:11:35.520> and<01:11:35.880> mastering<01:11:36.360> is 01:11:36.530 --> 01:11:36.540 align:start position:0% you know like writing and mastering is 01:11:36.540 --> 01:11:38.270 align:start position:0% you know like writing and mastering is basically<01:11:36.900> a<01:11:37.080> master<01:11:37.320> like<01:11:37.679> or<01:11:37.860> like 01:11:38.270 --> 01:11:38.280 align:start position:0% basically a master like or like 01:11:38.280 --> 01:11:40.430 align:start position:0% basically a master like or like recording<01:11:38.880> is 01:11:40.430 --> 01:11:40.440 align:start position:0% recording is 01:11:40.440 --> 01:11:43.430 align:start position:0% recording is like<01:11:40.860> a<01:11:40.980> 50<01:11:41.100> 50<01:11:41.340> Endeavor<01:11:41.820> right<01:11:42.120> so 01:11:43.430 --> 01:11:43.440 align:start position:0% like a 50 50 Endeavor right so 01:11:43.440 --> 01:11:46.970 align:start position:0% like a 50 50 Endeavor right so we<01:11:43.920> could<01:11:44.460> um<01:11:44.460> split<01:11:45.000> from<01:11:45.239> just<01:11:45.780> one<01:11:46.199> big 01:11:46.970 --> 01:11:46.980 align:start position:0% we could um split from just one big 01:11:46.980 --> 01:11:50.709 align:start position:0% we could um split from just one big chunk<01:11:47.280> of<01:11:47.460> 100<01:11:47.640> of<01:11:48.239> ownership<01:11:48.600> or 01:11:50.709 --> 01:11:50.719 align:start position:0% chunk of 100 of ownership or 01:11:50.719 --> 01:11:56.510 align:start position:0% chunk of 100 of ownership or mint<01:11:51.719> you<01:11:52.380> know<01:11:52.500> specifics 01:11:56.510 --> 01:11:56.520 align:start position:0% 01:11:56.520 --> 01:12:07.490 align:start position:0% any<01:11:57.480> more<01:11:57.840> feedback<01:11:58.260> we<01:11:58.560> have<01:11:58.739> more<01:11:58.860> time<01:11:59.100> yes 01:12:07.490 --> 01:12:07.500 align:start position:0% 01:12:07.500 --> 01:12:09.709 align:start position:0% so<01:12:08.100> is<01:12:08.340> is<01:12:08.580> the<01:12:08.760> biggest<01:12:08.880> reason<01:12:09.120> we<01:12:09.420> want<01:12:09.600> it 01:12:09.709 --> 01:12:09.719 align:start position:0% so is is the biggest reason we want it 01:12:09.719 --> 01:12:12.229 align:start position:0% so is is the biggest reason we want it to<01:12:09.840> be<01:12:09.900> a<01:12:10.080> wallet<01:12:10.440> so<01:12:10.679> that<01:12:10.920> we<01:12:11.340> can<01:12:11.460> have<01:12:11.760> that 01:12:12.229 --> 01:12:12.239 align:start position:0% to be a wallet so that we can have that 01:12:12.239 --> 01:12:14.330 align:start position:0% to be a wallet so that we can have that kind<01:12:12.659> of<01:12:12.719> signature<01:12:13.199> based<01:12:13.500> approval<01:12:13.860> like 01:12:14.330 --> 01:12:14.340 align:start position:0% kind of signature based approval like 01:12:14.340 --> 01:12:16.189 align:start position:0% kind of signature based approval like like<01:12:14.640> the<01:12:14.940> question<01:12:15.060> from<01:12:15.360> Dan<01:12:15.600> in<01:12:15.900> the<01:12:16.080> last 01:12:16.189 --> 01:12:16.199 align:start position:0% like the question from Dan in the last 01:12:16.199 --> 01:12:17.990 align:start position:0% like the question from Dan in the last talk<01:12:16.380> of<01:12:16.860> um 01:12:17.990 --> 01:12:18.000 align:start position:0% talk of um 01:12:18.000 --> 01:12:19.970 align:start position:0% talk of um deciding<01:12:18.659> when<01:12:18.900> the<01:12:19.080> metadata<01:12:19.560> would<01:12:19.739> get<01:12:19.860> to 01:12:19.970 --> 01:12:19.980 align:start position:0% deciding when the metadata would get to 01:12:19.980 --> 01:12:22.370 align:start position:0% deciding when the metadata would get to be<01:12:20.100> updated<01:12:20.460> or<01:12:21.120> if<01:12:21.480> a<01:12:21.600> piece<01:12:21.840> of<01:12:21.900> work<01:12:22.020> can<01:12:22.260> be 01:12:22.370 --> 01:12:22.380 align:start position:0% be updated or if a piece of work can be 01:12:22.380 --> 01:12:24.350 align:start position:0% be updated or if a piece of work can be included<01:12:22.679> into<01:12:22.860> a<01:12:23.100> movie<01:12:23.280> or<01:12:23.699> if<01:12:23.880> the<01:12:24.000> rights 01:12:24.350 --> 01:12:24.360 align:start position:0% included into a movie or if the rights 01:12:24.360 --> 01:12:25.790 align:start position:0% included into a movie or if the rights could<01:12:24.540> be<01:12:24.659> included<01:12:25.020> like<01:12:25.199> you<01:12:25.380> have<01:12:25.560> that 01:12:25.790 --> 01:12:25.800 align:start position:0% could be included like you have that 01:12:25.800 --> 01:12:27.590 align:start position:0% could be included like you have that signature<01:12:26.340> step<01:12:27.000> from<01:12:27.239> each<01:12:27.360> of<01:12:27.480> the 01:12:27.590 --> 01:12:27.600 align:start position:0% signature step from each of the 01:12:27.600 --> 01:12:29.689 align:start position:0% signature step from each of the participants<01:12:28.080> is<01:12:28.260> that<01:12:28.440> the<01:12:28.620> reason<01:12:28.800> kind<01:12:29.580> of 01:12:29.689 --> 01:12:29.699 align:start position:0% participants is that the reason kind of 01:12:29.699 --> 01:12:31.669 align:start position:0% participants is that the reason kind of thinking<01:12:30.000> of<01:12:30.120> it<01:12:30.300> as<01:12:30.540> a<01:12:30.780> wallet<01:12:31.020> or<01:12:31.320> what 01:12:31.669 --> 01:12:31.679 align:start position:0% thinking of it as a wallet or what 01:12:31.679 --> 01:12:34.430 align:start position:0% thinking of it as a wallet or what what's<01:12:32.219> the<01:12:32.460> reason<01:12:32.640> uh<01:12:33.239> to<01:12:33.600> have<01:12:33.719> a<01:12:33.900> wallet<01:12:34.199> be 01:12:34.430 --> 01:12:34.440 align:start position:0% what's the reason uh to have a wallet be 01:12:34.440 --> 01:12:36.890 align:start position:0% what's the reason uh to have a wallet be the<01:12:34.800> mechanism<01:12:35.159> for<01:12:35.400> controlling<01:12:35.820> the<01:12:35.940> rights 01:12:36.890 --> 01:12:36.900 align:start position:0% the mechanism for controlling the rights 01:12:36.900 --> 01:12:40.310 align:start position:0% the mechanism for controlling the rights so<01:12:37.440> that<01:12:37.679> is<01:12:37.800> one<01:12:38.040> reason<01:12:38.659> and<01:12:39.659> the<01:12:40.199> other 01:12:40.310 --> 01:12:40.320 align:start position:0% so that is one reason and the other 01:12:40.320 --> 01:12:42.649 align:start position:0% so that is one reason and the other reason<01:12:40.560> is<01:12:40.860> and<01:12:41.219> this<01:12:41.400> is<01:12:41.580> very<01:12:41.820> personal<01:12:42.060> you 01:12:42.649 --> 01:12:42.659 align:start position:0% reason is and this is very personal you 01:12:42.659 --> 01:12:44.689 align:start position:0% reason is and this is very personal you know<01:12:42.780> like<01:12:42.960> looking<01:12:43.320> into<01:12:43.560> the<01:12:43.800> future<01:12:43.980> what<01:12:44.460> I 01:12:44.689 --> 01:12:44.699 align:start position:0% know like looking into the future what I 01:12:44.699 --> 01:12:47.390 align:start position:0% know like looking into the future what I think<01:12:44.880> that<01:12:45.659> would<01:12:45.840> happen<01:12:46.020> or<01:12:46.800> would<01:12:47.159> would 01:12:47.390 --> 01:12:47.400 align:start position:0% think that would happen or would would 01:12:47.400 --> 01:12:49.669 align:start position:0% think that would happen or would would happen<01:12:47.699> or<01:12:48.360> would<01:12:48.600> make<01:12:48.780> sense<01:12:49.020> if<01:12:49.380> it<01:12:49.500> would 01:12:49.669 --> 01:12:49.679 align:start position:0% happen or would make sense if it would 01:12:49.679 --> 01:12:53.689 align:start position:0% happen or would make sense if it would happen<01:12:49.860> is<01:12:50.219> that<01:12:50.520> this<01:12:51.000> contract<01:12:51.560> is<01:12:52.560> like<01:12:53.400> the 01:12:53.689 --> 01:12:53.699 align:start position:0% happen is that this contract is like the 01:12:53.699 --> 01:12:56.330 align:start position:0% happen is that this contract is like the master<01:12:53.820> contract<01:12:54.480> of<01:12:54.900> all<01:12:55.080> the<01:12:55.260> IP<01:12:55.620> that<01:12:56.219> is 01:12:56.330 --> 01:12:56.340 align:start position:0% master contract of all the IP that is 01:12:56.340 --> 01:12:58.550 align:start position:0% master contract of all the IP that is derivative<01:12:56.760> from<01:12:57.360> this<01:12:57.659> original<01:12:57.840> registry 01:12:58.550 --> 01:12:58.560 align:start position:0% derivative from this original registry 01:12:58.560 --> 01:13:01.729 align:start position:0% derivative from this original registry so<01:12:59.460> from<01:13:00.179> this<01:13:00.420> original<01:13:00.600> registry<01:13:01.320> and<01:13:01.560> we 01:13:01.729 --> 01:13:01.739 align:start position:0% so from this original registry and we 01:13:01.739 --> 01:13:04.790 align:start position:0% so from this original registry and we spoke<01:13:01.920> about<01:13:02.040> it<01:13:02.340> briefly<01:13:02.699> on<01:13:03.000> Twitter<01:13:03.500> uh<01:13:04.500> we 01:13:04.790 --> 01:13:04.800 align:start position:0% spoke about it briefly on Twitter uh we 01:13:04.800 --> 01:13:08.090 align:start position:0% spoke about it briefly on Twitter uh we could<01:13:04.980> also<01:13:05.280> have<01:13:05.659> some<01:13:06.659> form<01:13:06.840> of<01:13:07.380> progress 01:13:08.090 --> 01:13:08.100 align:start position:0% could also have some form of progress 01:13:08.100 --> 01:13:10.729 align:start position:0% could also have some form of progress nfts<01:13:08.820> where<01:13:09.060> everybody<01:13:09.239> is<01:13:09.659> for<01:13:10.199> example<01:13:10.440> we 01:13:10.729 --> 01:13:10.739 align:start position:0% nfts where everybody is for example we 01:13:10.739 --> 01:13:12.290 align:start position:0% nfts where everybody is for example we go<01:13:10.860> into<01:13:10.980> the<01:13:11.219> studio<01:13:11.460> and<01:13:11.880> then<01:13:12.000> we 01:13:12.290 --> 01:13:12.300 align:start position:0% go into the studio and then we 01:13:12.300 --> 01:13:14.270 align:start position:0% go into the studio and then we somebody's<01:13:13.080> gonna<01:13:13.199> come<01:13:13.440> and<01:13:13.560> feature<01:13:13.860> a<01:13:14.040> song 01:13:14.270 --> 01:13:14.280 align:start position:0% somebody's gonna come and feature a song 01:13:14.280 --> 01:13:16.130 align:start position:0% somebody's gonna come and feature a song right<01:13:14.460> that<01:13:14.699> it<01:13:14.820> was<01:13:14.940> not<01:13:15.060> he<01:13:15.179> was<01:13:15.360> not<01:13:15.480> or<01:13:15.960> she 01:13:16.130 --> 01:13:16.140 align:start position:0% right that it was not he was not or she 01:13:16.140 --> 01:13:18.169 align:start position:0% right that it was not he was not or she was<01:13:16.260> not<01:13:16.500> in<01:13:16.800> the<01:13:16.920> studio<01:13:17.100> in<01:13:17.460> the<01:13:17.640> on<01:13:18.060> the 01:13:18.169 --> 01:13:18.179 align:start position:0% was not in the studio in the on the 01:13:18.179 --> 01:13:19.970 align:start position:0% was not in the studio in the on the first<01:13:18.300> day<01:13:18.420> of<01:13:18.540> the<01:13:18.659> recording<01:13:19.020> then<01:13:19.260> there's 01:13:19.970 --> 01:13:19.980 align:start position:0% first day of the recording then there's 01:13:19.980 --> 01:13:22.669 align:start position:0% first day of the recording then there's a<01:13:20.219> way<01:13:20.340> of<01:13:20.520> tracking<01:13:21.060> the<01:13:21.300> progress<01:13:21.719> of<01:13:22.500> the 01:13:22.669 --> 01:13:22.679 align:start position:0% a way of tracking the progress of the 01:13:22.679 --> 01:13:24.169 align:start position:0% a way of tracking the progress of the intellectual<01:13:23.219> property<01:13:23.640> obviously<01:13:24.060> you 01:13:24.169 --> 01:13:24.179 align:start position:0% intellectual property obviously you 01:13:24.179 --> 01:13:27.590 align:start position:0% intellectual property obviously you could<01:13:24.360> go<01:13:24.540> like<01:13:24.900> even<01:13:25.320> deeper<01:13:25.800> with<01:13:26.219> a<01:13:27.120> Content 01:13:27.590 --> 01:13:27.600 align:start position:0% could go like even deeper with a Content 01:13:27.600 --> 01:13:29.050 align:start position:0% could go like even deeper with a Content ID 01:13:29.050 --> 01:13:29.060 align:start position:0% ID 01:13:29.060 --> 01:13:32.209 align:start position:0% ID mechanisms<01:13:30.060> and<01:13:30.300> whatnot<01:13:30.659> but<01:13:30.900> but<01:13:31.380> I<01:13:32.100> think 01:13:32.209 --> 01:13:32.219 align:start position:0% mechanisms and whatnot but but I think 01:13:32.219 --> 01:13:34.550 align:start position:0% mechanisms and whatnot but but I think that<01:13:32.520> this<01:13:32.820> smart<01:13:33.060> contract 01:13:34.550 --> 01:13:34.560 align:start position:0% that this smart contract 01:13:34.560 --> 01:13:36.830 align:start position:0% that this smart contract would<01:13:35.460> probably<01:13:35.640> evolve<01:13:36.239> to<01:13:36.360> be<01:13:36.540> like<01:13:36.659> the 01:13:36.830 --> 01:13:36.840 align:start position:0% would probably evolve to be like the 01:13:36.840 --> 01:13:39.229 align:start position:0% would probably evolve to be like the master<01:13:36.960> contract<01:13:37.500> where<01:13:37.679> you<01:13:37.920> would<01:13:38.100> mint 01:13:39.229 --> 01:13:39.239 align:start position:0% master contract where you would mint 01:13:39.239 --> 01:13:42.290 align:start position:0% master contract where you would mint the<01:13:39.719> one<01:13:39.840> of<01:13:40.020> one<01:13:40.199> of<01:13:40.320> the<01:13:40.440> song<01:13:40.560> or<01:13:41.520> the<01:13:41.880> 10 01:13:42.290 --> 01:13:42.300 align:start position:0% the one of one of the song or the 10 01:13:42.300 --> 01:13:47.510 align:start position:0% the one of one of the song or the 10 editions<01:13:42.900> of<01:13:43.560> uh<01:13:44.659> the<01:13:45.659> the<01:13:45.840> video<01:13:46.380> and<01:13:47.219> all<01:13:47.340> the 01:13:47.510 --> 01:13:47.520 align:start position:0% editions of uh the the video and all the 01:13:47.520 --> 01:13:50.750 align:start position:0% editions of uh the the video and all the derivative<01:13:47.940> works<01:13:48.360> and<01:13:48.900> the<01:13:49.080> cruel<01:13:49.440> the<01:13:49.679> value 01:13:50.750 --> 01:13:50.760 align:start position:0% derivative works and the cruel the value 01:13:50.760 --> 01:13:56.570 align:start position:0% derivative works and the cruel the value in<01:13:51.239> one<01:13:51.480> contract<01:13:51.840> basically 01:13:56.570 --> 01:13:56.580 align:start position:0% 01:13:56.580 --> 01:13:57.709 align:start position:0% hey 01:13:57.709 --> 01:13:57.719 align:start position:0% hey 01:13:57.719 --> 01:13:59.030 align:start position:0% hey um 01:13:59.030 --> 01:13:59.040 align:start position:0% um 01:13:59.040 --> 01:14:01.610 align:start position:0% um something<01:13:59.580> I'm<01:14:00.060> very<01:14:00.540> interested<01:14:00.960> in<01:14:01.080> is 01:14:01.610 --> 01:14:01.620 align:start position:0% something I'm very interested in is 01:14:01.620 --> 01:14:04.370 align:start position:0% something I'm very interested in is easing<01:14:02.520> time<01:14:02.640> as<01:14:02.880> a<01:14:03.060> constraint<01:14:03.480> to<01:14:03.900> force 01:14:04.370 --> 01:14:04.380 align:start position:0% easing time as a constraint to force 01:14:04.380 --> 01:14:06.890 align:start position:0% easing time as a constraint to force kind<01:14:04.620> of<01:14:04.800> consensus<01:14:05.400> between<01:14:05.640> a<01:14:05.880> group 01:14:06.890 --> 01:14:06.900 align:start position:0% kind of consensus between a group 01:14:06.900 --> 01:14:08.270 align:start position:0% kind of consensus between a group um<01:14:07.020> and<01:14:07.199> this<01:14:07.380> feels<01:14:07.620> like<01:14:07.679> it<01:14:07.860> could<01:14:07.980> be<01:14:08.100> quite 01:14:08.270 --> 01:14:08.280 align:start position:0% um and this feels like it could be quite 01:14:08.280 --> 01:14:09.950 align:start position:0% um and this feels like it could be quite a<01:14:08.460> good<01:14:08.580> that<01:14:09.239> could<01:14:09.360> be<01:14:09.480> quite<01:14:09.659> interesting 01:14:09.950 --> 01:14:09.960 align:start position:0% a good that could be quite interesting 01:14:09.960 --> 01:14:11.330 align:start position:0% a good that could be quite interesting to<01:14:10.199> bring<01:14:10.320> into<01:14:10.440> this 01:14:11.330 --> 01:14:11.340 align:start position:0% to bring into this 01:14:11.340 --> 01:14:12.890 align:start position:0% to bring into this that<01:14:12.000> I<01:14:12.179> actually<01:14:12.360> wrote<01:14:12.540> something<01:14:12.719> about 01:14:12.890 --> 01:14:12.900 align:start position:0% that I actually wrote something about 01:14:12.900 --> 01:14:15.350 align:start position:0% that I actually wrote something about this<01:14:13.080> thing<01:14:13.260> like<01:14:13.440> February<01:14:14.040> or<01:14:14.280> something 01:14:15.350 --> 01:14:15.360 align:start position:0% this thing like February or something 01:14:15.360 --> 01:14:17.330 align:start position:0% this thing like February or something um about<01:14:15.540> making<01:14:16.260> multi-seq<01:14:16.860> wallets<01:14:17.100> in<01:14:17.219> a 01:14:17.330 --> 01:14:17.340 align:start position:0% um about making multi-seq wallets in a 01:14:17.340 --> 01:14:19.430 align:start position:0% um about making multi-seq wallets in a similar<01:14:17.640> sort<01:14:17.760> of<01:14:17.880> way<01:14:17.940> but<01:14:18.239> when<01:14:18.900> I<01:14:19.080> was<01:14:19.199> when 01:14:19.430 --> 01:14:19.440 align:start position:0% similar sort of way but when I was when 01:14:19.440 --> 01:14:22.189 align:start position:0% similar sort of way but when I was when I<01:14:19.620> did<01:14:19.679> that<01:14:19.860> design<01:14:20.100> I<01:14:20.520> was<01:14:20.699> I<01:14:21.420> proposed<01:14:21.960> that 01:14:22.189 --> 01:14:22.199 align:start position:0% I did that design I was I proposed that 01:14:22.199 --> 01:14:23.810 align:start position:0% I did that design I was I proposed that you<01:14:22.320> have<01:14:22.560> like<01:14:22.800> a<01:14:22.920> time<01:14:23.040> period<01:14:23.340> that<01:14:23.580> can<01:14:23.699> be 01:14:23.810 --> 01:14:23.820 align:start position:0% you have like a time period that can be 01:14:23.820 --> 01:14:25.970 align:start position:0% you have like a time period that can be defined<01:14:24.239> in<01:14:24.780> which<01:14:24.900> data<01:14:25.260> can<01:14:25.380> change<01:14:25.560> and<01:14:25.739> at 01:14:25.970 --> 01:14:25.980 align:start position:0% defined in which data can change and at 01:14:25.980 --> 01:14:27.350 align:start position:0% defined in which data can change and at that<01:14:26.100> point<01:14:26.159> it's<01:14:26.340> finalized<01:14:26.880> and<01:14:27.000> boom<01:14:27.300> it 01:14:27.350 --> 01:14:27.360 align:start position:0% that point it's finalized and boom it 01:14:27.360 --> 01:14:29.390 align:start position:0% that point it's finalized and boom it goes<01:14:27.659> and<01:14:27.840> that's<01:14:28.380> that 01:14:29.390 --> 01:14:29.400 align:start position:0% goes and that's that 01:14:29.400 --> 01:14:31.250 align:start position:0% goes and that's that how<01:14:29.760> do<01:14:30.060> you<01:14:30.179> feel<01:14:30.300> about<01:14:30.420> that<01:14:30.719> in<01:14:30.900> terms<01:14:31.140> of 01:14:31.250 --> 01:14:31.260 align:start position:0% how do you feel about that in terms of 01:14:31.260 --> 01:14:34.130 align:start position:0% how do you feel about that in terms of like<01:14:31.440> the<01:14:31.860> this<01:14:32.400> workflow<01:14:33.000> like 01:14:34.130 --> 01:14:34.140 align:start position:0% like the this workflow like 01:14:34.140 --> 01:14:36.050 align:start position:0% like the this workflow like um<01:14:34.260> you<01:14:34.440> know<01:14:34.560> do<01:14:34.920> you<01:14:35.100> see<01:14:35.280> that<01:14:35.580> you've<01:14:35.940> got 01:14:36.050 --> 01:14:36.060 align:start position:0% um you know do you see that you've got 01:14:36.060 --> 01:14:38.030 align:start position:0% um you know do you see that you've got multiple<01:14:36.540> parties<01:14:37.020> kind<01:14:37.380> of 01:14:38.030 --> 01:14:38.040 align:start position:0% multiple parties kind of 01:14:38.040 --> 01:14:39.770 align:start position:0% multiple parties kind of putting<01:14:38.699> their<01:14:38.820> information<01:14:39.060> in<01:14:39.420> do<01:14:39.659> you 01:14:39.770 --> 01:14:39.780 align:start position:0% putting their information in do you 01:14:39.780 --> 01:14:40.970 align:start position:0% putting their information in do you think<01:14:39.900> that<01:14:39.960> should<01:14:40.260> be<01:14:40.320> locked<01:14:40.620> down<01:14:40.679> at 01:14:40.970 --> 01:14:40.980 align:start position:0% think that should be locked down at 01:14:40.980 --> 01:14:43.610 align:start position:0% think that should be locked down at certain<01:14:41.159> point<01:14:41.400> or<01:14:42.199> how<01:14:43.199> are<01:14:43.320> you<01:14:43.380> thinking 01:14:43.610 --> 01:14:43.620 align:start position:0% certain point or how are you thinking 01:14:43.620 --> 01:14:46.070 align:start position:0% certain point or how are you thinking about<01:14:43.739> time<01:14:44.159> as<01:14:44.520> a<01:14:44.699> concept<01:14:44.940> within<01:14:45.420> uh<01:14:45.719> within 01:14:46.070 --> 01:14:46.080 align:start position:0% about time as a concept within uh within 01:14:46.080 --> 01:14:50.030 align:start position:0% about time as a concept within uh within this<01:14:46.260> kind<01:14:46.380> of<01:14:46.440> a<01:14:46.560> formalization 01:14:50.030 --> 01:14:50.040 align:start position:0% 01:14:50.040 --> 01:14:52.550 align:start position:0% I<01:14:50.640> think<01:14:50.820> Dan<01:14:51.060> I<01:14:51.420> think<01:14:51.540> the<01:14:51.960> the<01:14:52.199> ideal 01:14:52.550 --> 01:14:52.560 align:start position:0% I think Dan I think the the ideal 01:14:52.560 --> 01:14:55.430 align:start position:0% I think Dan I think the the ideal scenario<01:14:53.040> is<01:14:53.340> that<01:14:53.580> creatives<01:14:54.060> get<01:14:54.420> agree<01:14:55.199> on 01:14:55.430 --> 01:14:55.440 align:start position:0% scenario is that creatives get agree on 01:14:55.440 --> 01:14:59.030 align:start position:0% scenario is that creatives get agree on percentages<01:14:55.920> of<01:14:56.159> ownership<01:14:56.520> immediately 01:14:59.030 --> 01:14:59.040 align:start position:0% percentages of ownership immediately 01:14:59.040 --> 01:15:01.250 align:start position:0% percentages of ownership immediately I<01:14:59.460> wish<01:14:59.640> you<01:14:59.880> right<01:15:00.120> yeah 01:15:01.250 --> 01:15:01.260 align:start position:0% I wish you right yeah 01:15:01.260 --> 01:15:03.290 align:start position:0% I wish you right yeah we<01:15:01.679> wish<01:15:01.920> but<01:15:02.400> if<01:15:02.520> the<01:15:02.699> tool<01:15:02.940> is<01:15:03.060> available 01:15:03.290 --> 01:15:03.300 align:start position:0% we wish but if the tool is available 01:15:03.300 --> 01:15:06.770 align:start position:0% we wish but if the tool is available that<01:15:04.140> might<01:15:04.320> be<01:15:04.440> an<01:15:04.560> incentive<01:15:05.040> right<01:15:05.520> and<01:15:06.360> if 01:15:06.770 --> 01:15:06.780 align:start position:0% that might be an incentive right and if 01:15:06.780 --> 01:15:07.729 align:start position:0% that might be an incentive right and if we 01:15:07.729 --> 01:15:07.739 align:start position:0% we 01:15:07.739 --> 01:15:10.970 align:start position:0% we fulfill<01:15:08.340> the<01:15:08.580> promise<01:15:09.000> of<01:15:09.420> value<01:15:09.980> through 01:15:10.970 --> 01:15:10.980 align:start position:0% fulfill the promise of value through 01:15:10.980 --> 01:15:14.990 align:start position:0% fulfill the promise of value through these<01:15:11.640> a<01:15:12.480> specific<01:15:13.320> type<01:15:13.679> of<01:15:14.219> um 01:15:14.990 --> 01:15:15.000 align:start position:0% these a specific type of um 01:15:15.000 --> 01:15:19.070 align:start position:0% these a specific type of um a<01:15:15.719> creative<01:15:16.320> product<01:15:17.100> then<01:15:17.940> we<01:15:18.540> might<01:15:18.719> be<01:15:18.900> able 01:15:19.070 --> 01:15:19.080 align:start position:0% a creative product then we might be able 01:15:19.080 --> 01:15:20.750 align:start position:0% a creative product then we might be able to<01:15:19.199> take<01:15:19.440> it<01:15:19.620> a<01:15:19.800> step<01:15:19.920> further<01:15:20.280> because<01:15:20.460> right 01:15:20.750 --> 01:15:20.760 align:start position:0% to take it a step further because right 01:15:20.760 --> 01:15:23.630 align:start position:0% to take it a step further because right you<01:15:21.060> know<01:15:21.120> like<01:15:21.360> 20<01:15:22.020> years<01:15:22.260> ago<01:15:22.560> split<01:15:23.460> like 01:15:23.630 --> 01:15:23.640 align:start position:0% you know like 20 years ago split like 01:15:23.640 --> 01:15:26.030 align:start position:0% you know like 20 years ago split like splits<01:15:24.179> were<01:15:24.440> non-existent<01:15:25.440> basically 01:15:26.030 --> 01:15:26.040 align:start position:0% splits were non-existent basically 01:15:26.040 --> 01:15:27.950 align:start position:0% splits were non-existent basically Publishers<01:15:26.940> and<01:15:27.120> record<01:15:27.239> labels<01:15:27.659> were<01:15:27.840> the 01:15:27.950 --> 01:15:27.960 align:start position:0% Publishers and record labels were the 01:15:27.960 --> 01:15:30.530 align:start position:0% Publishers and record labels were the ones<01:15:28.140> actually<01:15:28.380> doing<01:15:28.620> the<01:15:28.860> paperwork<01:15:29.280> but<01:15:30.120> it 01:15:30.530 --> 01:15:30.540 align:start position:0% ones actually doing the paperwork but it 01:15:30.540 --> 01:15:32.810 align:start position:0% ones actually doing the paperwork but it has<01:15:30.780> evolved<01:15:31.260> in<01:15:31.380> the<01:15:31.560> creative<01:15:31.860> mind<01:15:32.100> that 01:15:32.810 --> 01:15:32.820 align:start position:0% has evolved in the creative mind that 01:15:32.820 --> 01:15:35.090 align:start position:0% has evolved in the creative mind that they<01:15:33.120> own<01:15:33.360> their<01:15:33.719> their<01:15:34.080> their<01:15:34.320> creation<01:15:34.860> said 01:15:35.090 --> 01:15:35.100 align:start position:0% they own their their their creation said 01:15:35.100 --> 01:15:37.189 align:start position:0% they own their their their creation said that<01:15:35.400> they<01:15:35.640> want<01:15:36.000> to<01:15:36.179> be<01:15:36.300> a<01:15:36.420> part<01:15:36.540> of<01:15:36.659> split<01:15:37.020> so 01:15:37.189 --> 01:15:37.199 align:start position:0% that they want to be a part of split so 01:15:37.199 --> 01:15:39.229 align:start position:0% that they want to be a part of split so more<01:15:37.620> and<01:15:37.739> more<01:15:37.920> you<01:15:38.159> see<01:15:38.340> like<01:15:38.520> producers<01:15:39.000> and 01:15:39.229 --> 01:15:39.239 align:start position:0% more and more you see like producers and 01:15:39.239 --> 01:15:41.030 align:start position:0% more and more you see like producers and artists<01:15:39.540> and<01:15:39.600> songwriters<01:15:40.140> be<01:15:40.320> like<01:15:40.500> okay 01:15:41.030 --> 01:15:41.040 align:start position:0% artists and songwriters be like okay 01:15:41.040 --> 01:15:42.590 align:start position:0% artists and songwriters be like okay like<01:15:41.280> let's<01:15:41.460> you<01:15:41.699> know<01:15:41.820> like<01:15:41.940> let's<01:15:42.179> show<01:15:42.420> me 01:15:42.590 --> 01:15:42.600 align:start position:0% like let's you know like let's show me 01:15:42.600 --> 01:15:44.750 align:start position:0% like let's you know like let's show me the<01:15:42.780> splits<01:15:43.140> right<01:15:43.679> or<01:15:43.920> let's<01:15:44.100> negotiate<01:15:44.580> the 01:15:44.750 --> 01:15:44.760 align:start position:0% the splits right or let's negotiate the 01:15:44.760 --> 01:15:47.270 align:start position:0% the splits right or let's negotiate the splits<01:15:45.239> hopefully<01:15:45.719> as<01:15:45.840> soon<01:15:46.020> as<01:15:46.080> possible<01:15:46.440> and 01:15:47.270 --> 01:15:47.280 align:start position:0% splits hopefully as soon as possible and 01:15:47.280 --> 01:15:49.310 align:start position:0% splits hopefully as soon as possible and this<01:15:47.699> is<01:15:47.880> kind<01:15:48.060> of<01:15:48.179> just<01:15:48.300> like<01:15:48.540> inserting<01:15:49.140> it 01:15:49.310 --> 01:15:49.320 align:start position:0% this is kind of just like inserting it 01:15:49.320 --> 01:15:51.770 align:start position:0% this is kind of just like inserting it in<01:15:49.620> that<01:15:49.860> moment<01:15:50.219> of<01:15:50.520> you<01:15:51.060> bounce<01:15:51.300> the<01:15:51.540> song 01:15:51.770 --> 01:15:51.780 align:start position:0% in that moment of you bounce the song 01:15:51.780 --> 01:15:54.950 align:start position:0% in that moment of you bounce the song you<01:15:52.440> share<01:15:52.620> it<01:15:52.800> is<01:15:53.040> there<01:15:53.280> consensus<01:15:53.840> how<01:15:54.840> do 01:15:54.950 --> 01:15:54.960 align:start position:0% you share it is there consensus how do 01:15:54.960 --> 01:15:56.570 align:start position:0% you share it is there consensus how do we<01:15:55.080> how<01:15:55.560> are<01:15:55.739> we<01:15:55.800> you<01:15:55.980> know<01:15:56.100> like<01:15:56.219> splitting 01:15:56.570 --> 01:15:56.580 align:start position:0% we how are we you know like splitting 01:15:56.580 --> 01:15:59.090 align:start position:0% we how are we you know like splitting the<01:15:56.699> ownership<01:15:56.940> of<01:15:57.179> this<01:15:57.420> let's<01:15:58.020> log<01:15:58.320> it<01:15:58.560> on 01:15:59.090 --> 01:15:59.100 align:start position:0% the ownership of this let's log it on 01:15:59.100 --> 01:16:02.149 align:start position:0% the ownership of this let's log it on the<01:15:59.219> blockchain<01:15:59.640> and<01:16:01.140> um 01:16:02.149 --> 01:16:02.159 align:start position:0% the blockchain and um 01:16:02.159 --> 01:16:06.290 align:start position:0% the blockchain and um and<01:16:02.940> it<01:16:03.480> should<01:16:04.199> serve<01:16:04.739> as<01:16:05.460> a<01:16:05.640> proof<01:16:05.940> of<01:16:06.000> work 01:16:06.290 --> 01:16:06.300 align:start position:0% and it should serve as a proof of work 01:16:06.300 --> 01:16:10.430 align:start position:0% and it should serve as a proof of work in<01:16:06.960> case<01:16:07.140> there's<01:16:07.440> like<01:16:07.739> legal<01:16:08.340> challenges<01:16:09.440> on 01:16:10.430 --> 01:16:10.440 align:start position:0% in case there's like legal challenges on 01:16:10.440 --> 01:16:13.990 align:start position:0% in case there's like legal challenges on on<01:16:10.860> on<01:16:11.460> the<01:16:11.760> process 01:16:13.990 --> 01:16:14.000 align:start position:0% on on the process 01:16:14.000 --> 01:16:16.729 align:start position:0% on on the process uh<01:16:15.000> yeah<01:16:15.179> I<01:16:15.420> have<01:16:15.540> a<01:16:15.719> question<01:16:15.900> so<01:16:16.380> I 01:16:16.729 --> 01:16:16.739 align:start position:0% uh yeah I have a question so I 01:16:16.739 --> 01:16:18.890 align:start position:0% uh yeah I have a question so I understand<01:16:16.860> this 01:16:18.890 --> 01:16:18.900 align:start position:0% understand this 01:16:18.900 --> 01:16:21.229 align:start position:0% understand this um<01:16:19.080> or<01:16:19.440> I<01:16:19.679> my<01:16:20.040> mind<01:16:20.219> tries<01:16:20.520> to<01:16:20.640> abstract<01:16:21.000> this 01:16:21.229 --> 01:16:21.239 align:start position:0% um or I my mind tries to abstract this 01:16:21.239 --> 01:16:22.010 align:start position:0% um or I my mind tries to abstract this like 01:16:22.010 --> 01:16:22.020 align:start position:0% like 01:16:22.020 --> 01:16:24.050 align:start position:0% like um<01:16:22.080> the<01:16:22.500> concept<01:16:22.739> of<01:16:22.920> self-sovereignty<01:16:23.699> in 01:16:24.050 --> 01:16:24.060 align:start position:0% um the concept of self-sovereignty in 01:16:24.060 --> 01:16:26.510 align:start position:0% um the concept of self-sovereignty in intellectual<01:16:24.600> property<01:16:25.080> but<01:16:25.800> then<01:16:25.980> I<01:16:26.280> see 01:16:26.510 --> 01:16:26.520 align:start position:0% intellectual property but then I see 01:16:26.520 --> 01:16:28.010 align:start position:0% intellectual property but then I see this<01:16:27.060> like 01:16:28.010 --> 01:16:28.020 align:start position:0% this like 01:16:28.020 --> 01:16:30.290 align:start position:0% this like conflict<01:16:28.739> between<01:16:28.980> the<01:16:29.280> existing<01:16:29.699> structures 01:16:30.290 --> 01:16:30.300 align:start position:0% conflict between the existing structures 01:16:30.300 --> 01:16:33.229 align:start position:0% conflict between the existing structures and<01:16:31.080> the<01:16:31.320> structures<01:16:31.739> the<01:16:32.520> social<01:16:32.699> structures 01:16:33.229 --> 01:16:33.239 align:start position:0% and the structures the social structures 01:16:33.239 --> 01:16:34.729 align:start position:0% and the structures the social structures basically<01:16:33.659> and<01:16:33.900> standards<01:16:34.320> that<01:16:34.500> would<01:16:34.620> have 01:16:34.729 --> 01:16:34.739 align:start position:0% basically and standards that would have 01:16:34.739 --> 01:16:38.209 align:start position:0% basically and standards that would have to<01:16:34.800> evolve<01:16:35.159> If<01:16:35.400> This<01:16:35.640> Were<01:16:35.820> to<01:16:36.260> actually<01:16:37.260> come 01:16:38.209 --> 01:16:38.219 align:start position:0% to evolve If This Were to actually come 01:16:38.219 --> 01:16:40.850 align:start position:0% to evolve If This Were to actually come and<01:16:38.699> have<01:16:38.940> any<01:16:39.179> chance<01:16:39.420> at<01:16:39.719> becoming<01:16:40.380> like<01:16:40.679> the 01:16:40.850 --> 01:16:40.860 align:start position:0% and have any chance at becoming like the 01:16:40.860 --> 01:16:44.390 align:start position:0% and have any chance at becoming like the dominant<01:16:41.219> form<01:16:41.460> of<01:16:41.940> of<01:16:42.719> um<01:16:42.780> you<01:16:43.020> know<01:16:43.080> managing 01:16:44.390 --> 01:16:44.400 align:start position:0% dominant form of of um you know managing 01:16:44.400 --> 01:16:47.870 align:start position:0% dominant form of of um you know managing um<01:16:44.460> creative<01:16:44.880> IP<01:16:45.360> I'm<01:16:46.320> wondering<01:16:46.679> how<01:16:47.400> you<01:16:47.640> see 01:16:47.870 --> 01:16:47.880 align:start position:0% um creative IP I'm wondering how you see 01:16:47.880 --> 01:16:49.790 align:start position:0% um creative IP I'm wondering how you see like<01:16:48.360> the<01:16:48.540> end<01:16:48.659> game<01:16:48.900> of<01:16:49.140> this<01:16:49.320> playing<01:16:49.620> out 01:16:49.790 --> 01:16:49.800 align:start position:0% like the end game of this playing out 01:16:49.800 --> 01:16:53.030 align:start position:0% like the end game of this playing out how<01:16:50.100> how<01:16:50.340> can<01:16:50.820> this<01:16:51.179> actually 01:16:53.030 --> 01:16:53.040 align:start position:0% how how can this actually 01:16:53.040 --> 01:16:55.070 align:start position:0% how how can this actually um went<01:16:53.400> out<01:16:53.580> over<01:16:53.820> the<01:16:54.000> structures<01:16:54.420> that<01:16:54.780> we 01:16:55.070 --> 01:16:55.080 align:start position:0% um went out over the structures that we 01:16:55.080 --> 01:16:56.750 align:start position:0% um went out over the structures that we have<01:16:55.199> right<01:16:55.380> now<01:16:55.560> which<01:16:55.920> are<01:16:56.340> very<01:16:56.580> strong 01:16:56.750 --> 01:16:56.760 align:start position:0% have right now which are very strong 01:16:56.760 --> 01:16:59.330 align:start position:0% have right now which are very strong power<01:16:57.000> structures 01:16:59.330 --> 01:16:59.340 align:start position:0% power structures 01:16:59.340 --> 01:17:03.229 align:start position:0% power structures well<01:17:00.300> the 01:17:03.229 --> 01:17:03.239 align:start position:0% well the 01:17:03.239 --> 01:17:09.590 align:start position:0% well the the grand<01:17:03.900> idea<01:17:04.560> would<01:17:05.460> be<01:17:05.580> to<01:17:05.940> finally<01:17:06.360> have 01:17:09.590 --> 01:17:09.600 align:start position:0% 01:17:09.600 --> 01:17:12.290 align:start position:0% a<01:17:09.960> global<01:17:10.260> copyright<01:17:10.679> database 01:17:12.290 --> 01:17:12.300 align:start position:0% a global copyright database 01:17:12.300 --> 01:17:14.750 align:start position:0% a global copyright database right<01:17:12.719> if<01:17:13.440> that<01:17:13.620> makes<01:17:13.800> sense<01:17:13.980> it<01:17:14.340> has<01:17:14.520> been 01:17:14.750 --> 01:17:14.760 align:start position:0% right if that makes sense it has been 01:17:14.760 --> 01:17:17.870 align:start position:0% right if that makes sense it has been tried<01:17:15.320> several<01:17:16.320> times<01:17:16.500> I<01:17:16.920> know<01:17:17.100> a<01:17:17.520> lot<01:17:17.760> of 01:17:17.870 --> 01:17:17.880 align:start position:0% tried several times I know a lot of 01:17:17.880 --> 01:17:20.450 align:start position:0% tried several times I know a lot of people<01:17:18.000> are<01:17:18.239> accepted<01:17:19.020> into<01:17:19.380> that<01:17:19.679> or<01:17:19.920> I<01:17:20.400> don't 01:17:20.450 --> 01:17:20.460 align:start position:0% people are accepted into that or I don't 01:17:20.460 --> 01:17:22.430 align:start position:0% people are accepted into that or I don't know<01:17:20.580> if<01:17:20.699> it<01:17:20.880> if<01:17:21.120> it<01:17:21.540> even<01:17:21.659> it's<01:17:21.900> a<01:17:22.080> good<01:17:22.140> idea 01:17:22.430 --> 01:17:22.440 align:start position:0% know if it if it even it's a good idea 01:17:22.440 --> 01:17:23.750 align:start position:0% know if it if it even it's a good idea but 01:17:23.750 --> 01:17:23.760 align:start position:0% but 01:17:23.760 --> 01:17:24.850 align:start position:0% but um 01:17:24.850 --> 01:17:24.860 align:start position:0% um 01:17:24.860 --> 01:17:27.350 align:start position:0% um but<01:17:25.860> there<01:17:26.040> has<01:17:26.159> been<01:17:26.340> efforts<01:17:26.820> in<01:17:27.060> you<01:17:27.239> know 01:17:27.350 --> 01:17:27.360 align:start position:0% but there has been efforts in you know 01:17:27.360 --> 01:17:29.410 align:start position:0% but there has been efforts in you know like<01:17:27.480> like<01:17:27.960> just<01:17:28.440> sharing<01:17:28.920> the<01:17:29.100> information 01:17:29.410 --> 01:17:29.420 align:start position:0% like like just sharing the information 01:17:29.420 --> 01:17:31.310 align:start position:0% like like just sharing the information but<01:17:30.420> the<01:17:30.600> power<01:17:30.719> struggle<01:17:31.199> between 01:17:31.310 --> 01:17:31.320 align:start position:0% but the power struggle between 01:17:31.320 --> 01:17:33.830 align:start position:0% but the power struggle between Corporation<01:17:32.159> makes<01:17:32.520> it<01:17:32.699> makes<01:17:33.239> it<01:17:33.420> impossible 01:17:33.830 --> 01:17:33.840 align:start position:0% Corporation makes it makes it impossible 01:17:33.840 --> 01:17:37.990 align:start position:0% Corporation makes it makes it impossible right<01:17:34.440> they<01:17:34.800> don't<01:17:34.920> want<01:17:35.100> to<01:17:35.280> uh<01:17:35.880> just<01:17:37.140> um 01:17:37.990 --> 01:17:38.000 align:start position:0% right they don't want to uh just um 01:17:38.000 --> 01:17:42.950 align:start position:0% right they don't want to uh just um have<01:17:39.000> that<01:17:39.179> be<01:17:39.420> one<01:17:40.159> entity<01:17:41.159> and<01:17:42.120> um<01:17:42.120> and 01:17:42.950 --> 01:17:42.960 align:start position:0% have that be one entity and um and 01:17:42.960 --> 01:17:44.750 align:start position:0% have that be one entity and um and that's<01:17:43.199> that<01:17:43.620> and<01:17:43.860> that's<01:17:44.040> where<01:17:44.159> the<01:17:44.340> efforts 01:17:44.750 --> 01:17:44.760 align:start position:0% that's that and that's where the efforts 01:17:44.760 --> 01:17:46.729 align:start position:0% that's that and that's where the efforts have<01:17:44.820> died 01:17:46.729 --> 01:17:46.739 align:start position:0% have died 01:17:46.739 --> 01:17:48.950 align:start position:0% have died is<01:17:47.340> it<01:17:47.520> good<01:17:47.640> or<01:17:47.760> is<01:17:47.940> it<01:17:48.060> bad<01:17:48.239> I<01:17:48.540> don't<01:17:48.600> know<01:17:48.719> I 01:17:48.950 --> 01:17:48.960 align:start position:0% is it good or is it bad I don't know I 01:17:48.960 --> 01:17:50.870 align:start position:0% is it good or is it bad I don't know I mean<01:17:49.080> a 01:17:50.870 --> 01:17:50.880 align:start position:0% mean a 01:17:50.880 --> 01:17:52.850 align:start position:0% mean a probably<01:17:51.540> haven't<01:17:51.719> thought<01:17:52.080> about<01:17:52.260> the<01:17:52.679> the 01:17:52.850 --> 01:17:52.860 align:start position:0% probably haven't thought about the the 01:17:52.860 --> 01:17:55.070 align:start position:0% probably haven't thought about the the the<01:17:52.940> consequences<01:17:53.940> but<01:17:54.300> just<01:17:54.540> transparency 01:17:55.070 --> 01:17:55.080 align:start position:0% the consequences but just transparency 01:17:55.080 --> 01:17:56.990 align:start position:0% the consequences but just transparency on<01:17:55.380> data<01:17:55.800> I<01:17:56.219> think<01:17:56.340> should<01:17:56.520> be<01:17:56.699> publicly 01:17:56.990 --> 01:17:57.000 align:start position:0% on data I think should be publicly 01:17:57.000 --> 01:17:59.330 align:start position:0% on data I think should be publicly available<01:17:57.239> and<01:17:57.659> should<01:17:57.840> be 01:17:59.330 --> 01:17:59.340 align:start position:0% available and should be 01:17:59.340 --> 01:18:01.729 align:start position:0% available and should be um<01:17:59.400> you<01:17:59.880> know<01:18:00.000> like<01:18:00.239> uh<01:18:01.080> just<01:18:01.320> like<01:18:01.500> a<01:18:01.620> public 01:18:01.729 --> 01:18:01.739 align:start position:0% um you know like uh just like a public 01:18:01.739 --> 01:18:04.010 align:start position:0% um you know like uh just like a public good 01:18:04.010 --> 01:18:04.020 align:start position:0% good 01:18:04.020 --> 01:18:11.630 align:start position:0% good last<01:18:04.679> question 01:18:11.630 --> 01:18:11.640 align:start position:0% 01:18:11.640 --> 01:18:13.430 align:start position:0% thank<01:18:12.120> you 01:18:13.430 --> 01:18:13.440 align:start position:0% thank you 01:18:13.440 --> 01:18:16.490 align:start position:0% thank you um<01:18:13.560> are<01:18:13.860> these<01:18:14.100> splits<01:18:14.659> renegotiatable<01:18:15.659> at<01:18:16.320> a 01:18:16.490 --> 01:18:16.500 align:start position:0% um are these splits renegotiatable at a 01:18:16.500 --> 01:18:19.250 align:start position:0% um are these splits renegotiatable at a certain<01:18:16.620> period<01:18:17.040> after<01:18:17.520> a<01:18:17.820> set<01:18:18.060> time 01:18:19.250 --> 01:18:19.260 align:start position:0% certain period after a set time 01:18:19.260 --> 01:18:20.630 align:start position:0% certain period after a set time um<01:18:19.320> what<01:18:19.560> does<01:18:19.679> that<01:18:19.800> look<01:18:19.920> like<01:18:20.100> what's<01:18:20.400> the 01:18:20.630 --> 01:18:20.640 align:start position:0% um what does that look like what's the 01:18:20.640 --> 01:18:22.669 align:start position:0% um what does that look like what's the current<01:18:20.760> kind<01:18:21.060> of<01:18:21.239> discourse<01:18:22.080> regarding<01:18:22.500> that 01:18:22.669 --> 01:18:22.679 align:start position:0% current kind of discourse regarding that 01:18:22.679 --> 01:18:26.270 align:start position:0% current kind of discourse regarding that yes<01:18:23.400> so<01:18:23.820> copyright<01:18:24.480> law<01:18:24.840> actually<01:18:25.800> states 01:18:26.270 --> 01:18:26.280 align:start position:0% yes so copyright law actually states 01:18:26.280 --> 01:18:28.390 align:start position:0% yes so copyright law actually states that<01:18:26.820> you're<01:18:27.000> right 01:18:28.390 --> 01:18:28.400 align:start position:0% that you're right 01:18:28.400 --> 01:18:34.010 align:start position:0% that you're right in<01:18:29.400> of<01:18:29.900> on<01:18:30.900> an<01:18:31.080> idea<01:18:31.500> is<01:18:32.460> immutable<01:18:33.060> nobody<01:18:33.659> can 01:18:34.010 --> 01:18:34.020 align:start position:0% in of on an idea is immutable nobody can 01:18:34.020 --> 01:18:36.830 align:start position:0% in of on an idea is immutable nobody can take<01:18:34.199> that<01:18:34.380> away<01:18:34.500> from<01:18:34.679> you<01:18:34.860> so<01:18:35.159> a<01:18:36.120> hypnosis 01:18:36.830 --> 01:18:36.840 align:start position:0% take that away from you so a hypnosis 01:18:36.840 --> 01:18:39.169 align:start position:0% take that away from you so a hypnosis can<01:18:37.080> buy<01:18:37.380> the<01:18:37.739> the<01:18:38.400> Bruce<01:18:38.760> Springsteen 01:18:39.169 --> 01:18:39.179 align:start position:0% can buy the the Bruce Springsteen 01:18:39.179 --> 01:18:41.030 align:start position:0% can buy the the Bruce Springsteen catalog<01:18:39.600> but<01:18:39.840> you<01:18:40.080> know<01:18:40.140> like<01:18:40.320> Merk<01:18:40.800> could 01:18:41.030 --> 01:18:41.040 align:start position:0% catalog but you know like Merk could 01:18:41.040 --> 01:18:43.370 align:start position:0% catalog but you know like Merk could never<01:18:41.159> say<01:18:41.340> he<01:18:41.520> sang<01:18:41.699> those<01:18:42.000> songs<01:18:42.239> right<01:18:42.780> even 01:18:43.370 --> 01:18:43.380 align:start position:0% never say he sang those songs right even 01:18:43.380 --> 01:18:45.189 align:start position:0% never say he sang those songs right even though<01:18:43.560> he<01:18:43.860> he<01:18:44.280> owns<01:18:44.699> the<01:18:44.880> financial 01:18:45.189 --> 01:18:45.199 align:start position:0% though he he owns the financial 01:18:45.199 --> 01:18:49.790 align:start position:0% though he he owns the financial exploitation<01:18:46.199> of<01:18:46.560> of<01:18:47.100> the<01:18:47.460> IP<01:18:47.840> so<01:18:48.840> and<01:18:49.260> that's 01:18:49.790 --> 01:18:49.800 align:start position:0% exploitation of of the IP so and that's 01:18:49.800 --> 01:18:52.750 align:start position:0% exploitation of of the IP so and that's like<01:18:50.520> a<01:18:50.699> like<01:18:51.000> maybe<01:18:51.179> a<01:18:51.420> super<01:18:51.780> example<01:18:52.320> but 01:18:52.750 --> 01:18:52.760 align:start position:0% like a like maybe a super example but 01:18:52.760 --> 01:18:56.630 align:start position:0% like a like maybe a super example but having<01:18:53.760> the<01:18:54.600> possibility<01:18:55.140> of<01:18:56.100> making<01:18:56.400> you 01:18:56.630 --> 01:18:56.640 align:start position:0% having the possibility of making you 01:18:56.640 --> 01:18:58.370 align:start position:0% having the possibility of making you like<01:18:56.820> the<01:18:57.060> immutable<01:18:57.480> having<01:18:57.780> the<01:18:57.960> immutable 01:18:58.370 --> 01:18:58.380 align:start position:0% like the immutable having the immutable 01:18:58.380 --> 01:19:01.310 align:start position:0% like the immutable having the immutable record<01:18:58.560> of<01:18:58.920> you<01:18:59.520> were<01:18:59.699> there<01:19:00.000> even<01:19:00.600> though<01:19:00.900> you 01:19:01.310 --> 01:19:01.320 align:start position:0% record of you were there even though you 01:19:01.320 --> 01:19:04.610 align:start position:0% record of you were there even though you might<01:19:01.560> see<01:19:02.340> the<01:19:02.699> financial<01:19:03.199> retribution<01:19:04.199> of 01:19:04.610 --> 01:19:04.620 align:start position:0% might see the financial retribution of 01:19:04.620 --> 01:19:07.030 align:start position:0% might see the financial retribution of that<01:19:04.980> IP<01:19:05.340> you<01:19:06.000> have<01:19:06.120> the<01:19:06.300> right<01:19:06.480> to<01:19:06.780> be 01:19:07.030 --> 01:19:07.040 align:start position:0% that IP you have the right to be 01:19:07.040 --> 01:19:11.350 align:start position:0% that IP you have the right to be credited<01:19:08.040> as<01:19:08.580> the<01:19:08.760> author 01:19:11.350 --> 01:19:11.360 align:start position:0% 01:19:11.360 --> 01:19:13.689 align:start position:0% thank<01:19:12.360> you<01:19:12.480> thank<01:19:12.780> you<01:19:12.900> Andre 01:19:13.689 --> 01:19:13.699 align:start position:0% thank you thank you Andre 01:19:13.699 --> 01:19:19.970 align:start position:0% thank you thank you Andre thank<01:19:14.699> you<01:19:14.760> for<01:19:14.940> the<01:19:15.120> talk 01:19:19.970 --> 01:19:19.980 align:start position:0% 01:19:19.980 --> 01:19:22.910 align:start position:0% I<01:19:20.580> think<01:19:20.699> I<01:19:21.120> really<01:19:21.360> liked<01:19:21.719> what<01:19:22.199> you<01:19:22.380> there 01:19:22.910 --> 01:19:22.920 align:start position:0% I think I really liked what you there 01:19:22.920 --> 01:19:24.350 align:start position:0% I think I really liked what you there was<01:19:23.100> like<01:19:23.280> this<01:19:23.400> one<01:19:23.640> quote<01:19:23.940> that<01:19:24.120> you<01:19:24.239> said 01:19:24.350 --> 01:19:24.360 align:start position:0% was like this one quote that you said 01:19:24.360 --> 01:19:27.050 align:start position:0% was like this one quote that you said like<01:19:24.540> copyright<01:19:24.960> is<01:19:25.199> immutable<01:19:25.679> that<01:19:26.100> uh<01:19:26.580> it's 01:19:27.050 --> 01:19:27.060 align:start position:0% like copyright is immutable that uh it's 01:19:27.060 --> 01:19:29.030 align:start position:0% like copyright is immutable that uh it's definitely<01:19:27.360> something<01:19:27.719> I<01:19:28.080> think<01:19:28.199> we<01:19:28.440> can<01:19:28.620> uh 01:19:29.030 --> 01:19:29.040 align:start position:0% definitely something I think we can uh 01:19:29.040 --> 01:19:31.070 align:start position:0% definitely something I think we can uh probably<01:19:29.760> all<01:19:30.060> take<01:19:30.300> home<01:19:30.540> and<01:19:30.719> think<01:19:30.900> about 01:19:31.070 --> 01:19:31.080 align:start position:0% probably all take home and think about 01:19:31.080 --> 01:19:35.050 align:start position:0% probably all take home and think about for<01:19:31.440> a<01:19:31.560> while<01:19:31.620> uh<01:19:32.460> next<01:19:32.699> up<01:19:32.880> is<01:19:33.420> uh<01:19:33.780> Ian 01:19:35.050 --> 01:19:35.060 align:start position:0% for a while uh next up is uh Ian 01:19:35.060 --> 01:19:38.030 align:start position:0% for a while uh next up is uh Ian and<01:19:36.060> Ian<01:19:36.540> is<01:19:36.719> going<01:19:36.900> to<01:19:37.020> talk<01:19:37.199> about<01:19:37.440> rich 01:19:38.030 --> 01:19:38.040 align:start position:0% and Ian is going to talk about rich 01:19:38.040 --> 01:19:42.770 align:start position:0% and Ian is going to talk about rich content<01:19:38.580> type<01:19:38.900> types<01:19:39.900> in<01:19:40.440> nfts 01:19:42.770 --> 01:19:42.780 align:start position:0% content type types in nfts 01:19:42.780 --> 01:19:46.310 align:start position:0% content type types in nfts and<01:19:43.500> yeah<01:19:43.800> if<01:19:44.280> you<01:19:44.460> are<01:19:44.699> new<01:19:45.000> here<01:19:45.360> basically 01:19:46.310 --> 01:19:46.320 align:start position:0% and yeah if you are new here basically 01:19:46.320 --> 01:19:48.890 align:start position:0% and yeah if you are new here basically what<01:19:46.679> we<01:19:46.860> are<01:19:46.980> doing<01:19:47.219> is<01:19:47.580> the<01:19:47.940> ERC<01:19:48.480> lightning 01:19:48.890 --> 01:19:48.900 align:start position:0% what we are doing is the ERC lightning 01:19:48.900 --> 01:19:53.510 align:start position:0% what we are doing is the ERC lightning talks<01:19:49.380> we<01:19:49.860> are<01:19:50.100> the<01:19:50.400> East<01:19:51.179> magicians<01:19:52.440> and<01:19:53.159> we 01:19:53.510 --> 01:19:53.520 align:start position:0% talks we are the East magicians and we 01:19:53.520 --> 01:19:55.970 align:start position:0% talks we are the East magicians and we are<01:19:53.640> talking<01:19:53.820> about<01:19:54.080> ethereum<01:19:55.080> requests<01:19:55.800> for 01:19:55.970 --> 01:19:55.980 align:start position:0% are talking about ethereum requests for 01:19:55.980 --> 01:19:59.689 align:start position:0% are talking about ethereum requests for comments<01:19:56.520> proposals<01:19:57.120> so<01:19:57.659> not<01:19:57.960> the<01:19:58.380> core<01:19:59.340> Dev 01:19:59.689 --> 01:19:59.699 align:start position:0% comments proposals so not the core Dev 01:19:59.699 --> 01:20:04.149 align:start position:0% comments proposals so not the core Dev consensus<01:20:00.540> layer<01:20:00.840> stuff<01:20:01.080> but<01:20:01.460> the<01:20:02.600> solidity 01:20:04.149 --> 01:20:04.159 align:start position:0% consensus layer stuff but the solidity 01:20:04.159 --> 01:20:06.890 align:start position:0% consensus layer stuff but the solidity interfaces<01:20:05.159> application 01:20:06.890 --> 01:20:06.900 align:start position:0% interfaces application 01:20:06.900 --> 01:20:07.610 align:start position:0% interfaces application um 01:20:07.610 --> 01:20:07.620 align:start position:0% um 01:20:07.620 --> 01:20:09.770 align:start position:0% um like<01:20:08.400> these<01:20:08.760> standards 01:20:09.770 --> 01:20:09.780 align:start position:0% like these standards 01:20:09.780 --> 01:20:12.350 align:start position:0% like these standards um<01:20:09.900> yeah<01:20:10.199> so<01:20:10.800> thanks<01:20:11.580> for<01:20:11.760> having<01:20:11.880> me<01:20:12.000> Tim<01:20:12.239> it 01:20:12.350 --> 01:20:12.360 align:start position:0% um yeah so thanks for having me Tim it 01:20:12.360 --> 01:20:15.110 align:start position:0% um yeah so thanks for having me Tim it was<01:20:12.480> wild<01:20:12.659> we<01:20:12.900> met<01:20:13.140> at<01:20:13.520> youth<01:20:14.520> Berlin<01:20:14.820> a<01:20:15.000> while 01:20:15.110 --> 01:20:15.120 align:start position:0% was wild we met at youth Berlin a while 01:20:15.120 --> 01:20:18.530 align:start position:0% was wild we met at youth Berlin a while back<01:20:15.360> and<01:20:15.840> see<01:20:16.140> you<01:20:16.320> back<01:20:16.440> in<01:20:16.620> the<01:20:16.739> space<01:20:16.920> yeah 01:20:18.530 --> 01:20:18.540 align:start position:0% back and see you back in the space yeah 01:20:18.540 --> 01:20:20.750 align:start position:0% back and see you back in the space yeah um<01:20:18.600> I'm<01:20:18.960> gonna<01:20:19.140> give<01:20:19.320> a<01:20:19.500> quick<01:20:19.679> talk<01:20:20.040> on 01:20:20.750 --> 01:20:20.760 align:start position:0% um I'm gonna give a quick talk on 01:20:20.760 --> 01:20:24.709 align:start position:0% um I'm gonna give a quick talk on canonical<01:20:21.360> media<01:20:21.840> and<01:20:22.440> EIP<01:20:22.860> content<01:20:23.400> type<01:20:23.719> so 01:20:24.709 --> 01:20:24.719 align:start position:0% canonical media and EIP content type so 01:20:24.719 --> 01:20:27.350 align:start position:0% canonical media and EIP content type so the<01:20:25.380> notes<01:20:25.860> are<01:20:26.219> basically<01:20:26.640> I'm<01:20:27.060> just<01:20:27.239> going 01:20:27.350 --> 01:20:27.360 align:start position:0% the notes are basically I'm just going 01:20:27.360 --> 01:20:29.510 align:start position:0% the notes are basically I'm just going to<01:20:27.480> flip<01:20:27.719> through<01:20:27.900> Json<01:20:28.199> and<01:20:28.500> talk<01:20:28.679> about<01:20:28.860> it 01:20:29.510 --> 01:20:29.520 align:start position:0% to flip through Json and talk about it 01:20:29.520 --> 01:20:32.570 align:start position:0% to flip through Json and talk about it uh<01:20:30.360> the<01:20:30.600> notes<01:20:30.960> in<01:20:31.080> Json<01:20:31.380> are<01:20:31.679> on<01:20:31.800> GitHub<01:20:32.159> if 01:20:32.570 --> 01:20:32.580 align:start position:0% uh the notes in Json are on GitHub if 01:20:32.580 --> 01:20:34.189 align:start position:0% uh the notes in Json are on GitHub if you<01:20:32.699> have<01:20:32.820> questions<01:20:33.060> beyond<01:20:33.659> the<01:20:33.840> talk<01:20:33.960> or 01:20:34.189 --> 01:20:34.199 align:start position:0% you have questions beyond the talk or 01:20:34.199 --> 01:20:35.390 align:start position:0% you have questions beyond the talk or you're<01:20:34.320> watching<01:20:34.560> it<01:20:34.679> recorded<01:20:35.040> make<01:20:35.280> a 01:20:35.390 --> 01:20:35.400 align:start position:0% you're watching it recorded make a 01:20:35.400 --> 01:20:37.490 align:start position:0% you're watching it recorded make a GitHub<01:20:35.699> issue<01:20:36.060> probably<01:20:36.659> the<01:20:36.840> easiest<01:20:37.140> way<01:20:37.320> to 01:20:37.490 --> 01:20:37.500 align:start position:0% GitHub issue probably the easiest way to 01:20:37.500 --> 01:20:40.010 align:start position:0% GitHub issue probably the easiest way to respond<01:20:38.000> and<01:20:39.000> I'm<01:20:39.300> just<01:20:39.480> going<01:20:39.600> to<01:20:39.659> open<01:20:39.780> a 01:20:40.010 --> 01:20:40.020 align:start position:0% respond and I'm just going to open a 01:20:40.020 --> 01:20:42.290 align:start position:0% respond and I'm just going to open a conversation<01:20:40.440> about<01:20:40.860> kind<01:20:41.580> of<01:20:41.699> what<01:20:42.000> we've 01:20:42.290 --> 01:20:42.300 align:start position:0% conversation about kind of what we've 01:20:42.300 --> 01:20:44.030 align:start position:0% conversation about kind of what we've done<01:20:42.600> previously<01:20:43.260> as<01:20:43.380> an<01:20:43.500> organization<01:20:43.860> at 01:20:44.030 --> 01:20:44.040 align:start position:0% done previously as an organization at 01:20:44.040 --> 01:20:46.250 align:start position:0% done previously as an organization at Zora<01:20:44.400> What<01:20:44.520> I've<01:20:44.640> Done<01:20:44.820> personally<01:20:45.300> for 01:20:46.250 --> 01:20:46.260 align:start position:0% Zora What I've Done personally for 01:20:46.260 --> 01:20:49.790 align:start position:0% Zora What I've Done personally for certain<01:20:46.800> nft<01:20:47.520> projects<01:20:48.239> and<01:20:48.900> rendering<01:20:49.380> so<01:20:49.620> if 01:20:49.790 --> 01:20:49.800 align:start position:0% certain nft projects and rendering so if 01:20:49.800 --> 01:20:53.390 align:start position:0% certain nft projects and rendering so if you<01:20:49.920> go<01:20:50.040> to<01:20:50.159> the<01:20:50.400> original<01:20:50.580> EIP<01:20:51.500> 721<01:20:52.500> the 01:20:53.390 --> 01:20:53.400 align:start position:0% you go to the original EIP 721 the 01:20:53.400 --> 01:20:54.770 align:start position:0% you go to the original EIP 721 the metadata<01:20:53.880> scheme<01:20:54.120> is<01:20:54.179> pretty<01:20:54.420> lightweight 01:20:54.770 --> 01:20:54.780 align:start position:0% metadata scheme is pretty lightweight 01:20:54.780 --> 01:20:56.630 align:start position:0% metadata scheme is pretty lightweight you<01:20:55.020> have<01:20:55.140> a<01:20:55.260> name<01:20:55.440> description<01:20:55.860> and<01:20:56.100> image<01:20:56.400> it 01:20:56.630 --> 01:20:56.640 align:start position:0% you have a name description and image it 01:20:56.640 --> 01:20:58.450 align:start position:0% you have a name description and image it was<01:20:56.760> designed<01:20:57.000> an<01:20:57.120> era<01:20:57.420> of<01:20:57.420> crypto<01:20:57.780> punks 01:20:58.450 --> 01:20:58.460 align:start position:0% was designed an era of crypto punks 01:20:58.460 --> 01:21:00.950 align:start position:0% was designed an era of crypto punks cryptokitties<01:20:59.460> where<01:21:00.000> you<01:21:00.600> tracked 01:21:00.950 --> 01:21:00.960 align:start position:0% cryptokitties where you tracked 01:21:00.960 --> 01:21:02.810 align:start position:0% cryptokitties where you tracked ownership<01:21:01.260> and<01:21:01.679> the<01:21:01.860> image<01:21:02.159> just<01:21:02.520> kind<01:21:02.699> of 01:21:02.810 --> 01:21:02.820 align:start position:0% ownership and the image just kind of 01:21:02.820 --> 01:21:06.649 align:start position:0% ownership and the image just kind of showed<01:21:03.440> a<01:21:04.440> cute<01:21:05.219> item<01:21:05.699> or<01:21:05.880> like<01:21:06.060> the<01:21:06.239> thing<01:21:06.420> and 01:21:06.649 --> 01:21:06.659 align:start position:0% showed a cute item or like the thing and 01:21:06.659 --> 01:21:08.390 align:start position:0% showed a cute item or like the thing and then<01:21:06.840> that<01:21:07.080> became<01:21:07.500> more<01:21:07.739> and<01:21:07.860> more<01:21:08.100> important 01:21:08.390 --> 01:21:08.400 align:start position:0% then that became more and more important 01:21:08.400 --> 01:21:10.850 align:start position:0% then that became more and more important with<01:21:08.699> time<01:21:09.000> I<01:21:09.960> think<01:21:10.080> it<01:21:10.199> was<01:21:10.380> left<01:21:10.500> pretty 01:21:10.850 --> 01:21:10.860 align:start position:0% with time I think it was left pretty 01:21:10.860 --> 01:21:13.850 align:start position:0% with time I think it was left pretty open-ended<01:21:11.580> for<01:21:11.880> people<01:21:12.060> to<01:21:12.480> build<01:21:12.960> out<01:21:13.320> from 01:21:13.850 --> 01:21:13.860 align:start position:0% open-ended for people to build out from 01:21:13.860 --> 01:21:15.830 align:start position:0% open-ended for people to build out from here<01:21:14.040> and<01:21:14.340> I<01:21:14.460> do<01:21:14.580> like<01:21:14.820> that<01:21:15.120> idea<01:21:15.420> of<01:21:15.600> a<01:21:15.780> very 01:21:15.830 --> 01:21:15.840 align:start position:0% here and I do like that idea of a very 01:21:15.840 --> 01:21:17.750 align:start position:0% here and I do like that idea of a very minimal<01:21:16.199> standard<01:21:16.620> and<01:21:17.100> then<01:21:17.280> people<01:21:17.400> can<01:21:17.580> run 01:21:17.750 --> 01:21:17.760 align:start position:0% minimal standard and then people can run 01:21:17.760 --> 01:21:19.970 align:start position:0% minimal standard and then people can run with<01:21:17.940> it<01:21:18.120> but<01:21:18.659> I<01:21:18.780> think<01:21:18.900> at<01:21:19.080> some<01:21:19.260> point<01:21:19.440> that 01:21:19.970 --> 01:21:19.980 align:start position:0% with it but I think at some point that 01:21:19.980 --> 01:21:23.209 align:start position:0% with it but I think at some point that standard<01:21:20.340> can<01:21:20.640> also<01:21:20.820> be<01:21:21.000> improved<01:21:21.480> so 01:21:23.209 --> 01:21:23.219 align:start position:0% standard can also be improved so 01:21:23.219 --> 01:21:25.250 align:start position:0% standard can also be improved so an<01:21:23.820> example<01:21:24.120> is<01:21:24.300> and<01:21:24.540> I've<01:21:24.719> had<01:21:24.840> co-workers 01:21:25.250 --> 01:21:25.260 align:start position:0% an example is and I've had co-workers 01:21:25.260 --> 01:21:26.990 align:start position:0% an example is and I've had co-workers ask<01:21:25.500> me<01:21:25.620> this<01:21:25.860> all<01:21:26.100> the<01:21:26.219> time<01:21:26.340> most<01:21:26.699> recently 01:21:26.990 --> 01:21:27.000 align:start position:0% ask me this all the time most recently 01:21:27.000 --> 01:21:28.189 align:start position:0% ask me this all the time most recently somebody<01:21:27.239> asked<01:21:27.600> how<01:21:27.719> do<01:21:27.780> I<01:21:27.900> made<01:21:28.020> a 01:21:28.189 --> 01:21:28.199 align:start position:0% somebody asked how do I made a 01:21:28.199 --> 01:21:29.209 align:start position:0% somebody asked how do I made a presentation 01:21:29.209 --> 01:21:29.219 align:start position:0% presentation 01:21:29.219 --> 01:21:31.310 align:start position:0% presentation and<01:21:29.940> the<01:21:30.239> easiest<01:21:30.420> thing<01:21:30.600> to<01:21:30.780> do<01:21:30.840> would<01:21:31.080> be<01:21:31.140> to 01:21:31.310 --> 01:21:31.320 align:start position:0% and the easiest thing to do would be to 01:21:31.320 --> 01:21:33.649 align:start position:0% and the easiest thing to do would be to export<01:21:31.560> your<01:21:31.920> keynote<01:21:32.219> or<01:21:32.460> figma<01:21:32.820> as<01:21:33.120> a<01:21:33.300> PDF 01:21:33.649 --> 01:21:33.659 align:start position:0% export your keynote or figma as a PDF 01:21:33.659 --> 01:21:35.530 align:start position:0% export your keynote or figma as a PDF and<01:21:34.080> then<01:21:34.199> mint<01:21:34.440> it<01:21:34.739> right<01:21:34.920> well 01:21:35.530 --> 01:21:35.540 align:start position:0% and then mint it right well 01:21:35.540 --> 01:21:38.689 align:start position:0% and then mint it right well unfortunately<01:21:36.679> the<01:21:37.679> metadata<01:21:38.219> standard<01:21:38.580> just 01:21:38.689 --> 01:21:38.699 align:start position:0% unfortunately the metadata standard just 01:21:38.699 --> 01:21:40.729 align:start position:0% unfortunately the metadata standard just says<01:21:38.880> image<01:21:39.179> so<01:21:39.600> what<01:21:40.140> people<01:21:40.320> have<01:21:40.560> done 01:21:40.729 --> 01:21:40.739 align:start position:0% says image so what people have done 01:21:40.739 --> 01:21:43.790 align:start position:0% says image so what people have done openc<01:21:41.340> kind<01:21:41.760> of<01:21:41.940> added<01:21:42.480> animation<01:21:42.960> URL<01:21:43.500> to 01:21:43.790 --> 01:21:43.800 align:start position:0% openc kind of added animation URL to 01:21:43.800 --> 01:21:45.229 align:start position:0% openc kind of added animation URL to show<01:21:43.980> an<01:21:44.100> animation<01:21:44.400> which<01:21:44.640> could<01:21:44.820> be<01:21:44.940> a<01:21:45.060> web 01:21:45.229 --> 01:21:45.239 align:start position:0% show an animation which could be a web 01:21:45.239 --> 01:21:49.189 align:start position:0% show an animation which could be a web page<01:21:45.440> gltf<01:21:46.880> audio<01:21:47.880> a<01:21:48.239> bunch<01:21:48.420> of<01:21:48.600> random<01:21:48.900> grab 01:21:49.189 --> 01:21:49.199 align:start position:0% page gltf audio a bunch of random grab 01:21:49.199 --> 01:21:50.930 align:start position:0% page gltf audio a bunch of random grab bag<01:21:49.380> of<01:21:49.620> content<01:21:49.920> and<01:21:50.400> the<01:21:50.520> great<01:21:50.640> part<01:21:50.820> about 01:21:50.930 --> 01:21:50.940 align:start position:0% bag of content and the great part about 01:21:50.940 --> 01:21:52.790 align:start position:0% bag of content and the great part about an<01:21:51.239> image<01:21:51.480> is<01:21:51.659> if<01:21:51.840> you<01:21:51.960> want<01:21:52.020> to<01:21:52.140> render<01:21:52.320> it<01:21:52.560> as 01:21:52.790 --> 01:21:52.800 align:start position:0% an image is if you want to render it as 01:21:52.800 --> 01:21:54.950 align:start position:0% an image is if you want to render it as a<01:21:52.980> consumer<01:21:53.340> you<01:21:53.640> just<01:21:53.699> pop<01:21:53.880> it<01:21:54.060> into<01:21:54.179> an<01:21:54.480> HTML 01:21:54.950 --> 01:21:54.960 align:start position:0% a consumer you just pop it into an HTML 01:21:54.960 --> 01:21:56.630 align:start position:0% a consumer you just pop it into an HTML image<01:21:55.199> tag<01:21:55.440> or<01:21:55.560> you<01:21:55.739> put<01:21:55.860> an<01:21:56.040> image<01:21:56.280> viewer 01:21:56.630 --> 01:21:56.640 align:start position:0% image tag or you put an image viewer 01:21:56.640 --> 01:21:58.490 align:start position:0% image tag or you put an image viewer images<01:21:57.060> are<01:21:57.420> pretty<01:21:57.540> well<01:21:57.719> defined<01:21:58.080> on<01:21:58.199> how<01:21:58.380> to 01:21:58.490 --> 01:21:58.500 align:start position:0% images are pretty well defined on how to 01:21:58.500 --> 01:22:01.850 align:start position:0% images are pretty well defined on how to render<01:21:58.699> animations<01:21:59.699> get<01:22:00.360> a<01:22:00.480> lot<01:22:00.600> more<01:22:00.719> complex 01:22:01.850 --> 01:22:01.860 align:start position:0% render animations get a lot more complex 01:22:01.860 --> 01:22:04.010 align:start position:0% render animations get a lot more complex what<01:22:02.400> we<01:22:02.520> could<01:22:02.699> do<01:22:02.880> is<01:22:03.179> we<01:22:03.420> could<01:22:03.480> convert<01:22:03.840> the 01:22:04.010 --> 01:22:04.020 align:start position:0% what we could do is we could convert the 01:22:04.020 --> 01:22:06.110 align:start position:0% what we could do is we could convert the presentation<01:22:04.380> into<01:22:04.679> an<01:22:04.920> HTML<01:22:05.460> viewer<01:22:05.880> and 01:22:06.110 --> 01:22:06.120 align:start position:0% presentation into an HTML viewer and 01:22:06.120 --> 01:22:08.090 align:start position:0% presentation into an HTML viewer and upload<01:22:06.360> the<01:22:06.540> HTML<01:22:06.960> viewer<01:22:07.320> that<01:22:07.679> becomes 01:22:08.090 --> 01:22:08.100 align:start position:0% upload the HTML viewer that becomes 01:22:08.100 --> 01:22:09.709 align:start position:0% upload the HTML viewer that becomes pretty<01:22:08.280> cumbersome<01:22:08.760> and<01:22:09.360> a<01:22:09.480> little<01:22:09.600> bit 01:22:09.709 --> 01:22:09.719 align:start position:0% pretty cumbersome and a little bit 01:22:09.719 --> 01:22:11.390 align:start position:0% pretty cumbersome and a little bit difficult<01:22:10.020> because<01:22:10.320> the<01:22:10.620> original<01:22:10.800> content 01:22:11.390 --> 01:22:11.400 align:start position:0% difficult because the original content 01:22:11.400 --> 01:22:15.709 align:start position:0% difficult because the original content is<01:22:11.640> the<01:22:11.760> PDF<01:22:12.179> it's<01:22:12.420> not<01:22:12.659> the<01:22:12.960> HTML<01:22:13.620> viewer 01:22:15.709 --> 01:22:15.719 align:start position:0% is the PDF it's not the HTML viewer 01:22:15.719 --> 01:22:18.050 align:start position:0% is the PDF it's not the HTML viewer and<01:22:16.320> the<01:22:16.620> way<01:22:16.739> Zora<01:22:17.280> approached<01:22:17.580> this<01:22:17.760> with 01:22:18.050 --> 01:22:18.060 align:start position:0% and the way Zora approached this with 01:22:18.060 --> 01:22:20.090 align:start position:0% and the way Zora approached this with the<01:22:18.239> Zora<01:22:18.600> protocol<01:22:18.840> in<01:22:19.140> 2020<01:22:19.560> that<01:22:19.860> I<01:22:20.040> didn't 01:22:20.090 --> 01:22:20.100 align:start position:0% the Zora protocol in 2020 that I didn't 01:22:20.100 --> 01:22:21.890 align:start position:0% the Zora protocol in 2020 that I didn't really<01:22:20.340> work<01:22:20.520> on<01:22:20.640> that<01:22:20.880> was<01:22:21.060> before<01:22:21.239> my<01:22:21.600> time 01:22:21.890 --> 01:22:21.900 align:start position:0% really work on that was before my time 01:22:21.900 --> 01:22:25.070 align:start position:0% really work on that was before my time was<01:22:22.679> to<01:22:22.980> separate<01:22:23.340> this<01:22:23.520> concept<01:22:23.820> of<01:22:24.000> metadata 01:22:25.070 --> 01:22:25.080 align:start position:0% was to separate this concept of metadata 01:22:25.080 --> 01:22:27.530 align:start position:0% was to separate this concept of metadata and<01:22:25.800> content<01:22:26.400> content<01:22:27.000> was<01:22:27.179> one<01:22:27.420> thing 01:22:27.530 --> 01:22:27.540 align:start position:0% and content content was one thing 01:22:27.540 --> 01:22:29.870 align:start position:0% and content content was one thing metadata<01:22:28.140> was<01:22:28.260> another<01:22:28.440> and<01:22:29.159> the<01:22:29.340> idea<01:22:29.580> here 01:22:29.870 --> 01:22:29.880 align:start position:0% metadata was another and the idea here 01:22:29.880 --> 01:22:32.209 align:start position:0% metadata was another and the idea here is<01:22:30.060> that<01:22:30.300> the<01:22:30.480> nft<01:22:30.739> represents<01:22:31.739> you<01:22:31.860> own<01:22:32.040> a 01:22:32.209 --> 01:22:32.219 align:start position:0% is that the nft represents you own a 01:22:32.219 --> 01:22:34.010 align:start position:0% is that the nft represents you own a particular<01:22:32.520> ID<01:22:32.820> and<01:22:33.239> that<01:22:33.420> particular<01:22:33.780> ID 01:22:34.010 --> 01:22:34.020 align:start position:0% particular ID and that particular ID 01:22:34.020 --> 01:22:36.709 align:start position:0% particular ID and that particular ID represents<01:22:34.860> a<01:22:35.340> canonical<01:22:35.760> off-chain<01:22:36.239> content 01:22:36.709 --> 01:22:36.719 align:start position:0% represents a canonical off-chain content 01:22:36.719 --> 01:22:39.709 align:start position:0% represents a canonical off-chain content so<01:22:37.199> I<01:22:37.440> highly<01:22:37.679> recommended<01:22:38.159> to<01:22:38.520> use<01:22:38.880> ipfs 01:22:39.709 --> 01:22:39.719 align:start position:0% so I highly recommended to use ipfs 01:22:39.719 --> 01:22:41.510 align:start position:0% so I highly recommended to use ipfs which<01:22:40.199> is<01:22:40.320> decentralized<01:22:41.100> distribution 01:22:41.510 --> 01:22:41.520 align:start position:0% which is decentralized distribution 01:22:41.520 --> 01:22:44.270 align:start position:0% which is decentralized distribution layer<01:22:42.000> but<01:22:42.480> as<01:22:42.780> a<01:22:42.960> future<01:22:43.140> proofing<01:22:43.679> also<01:22:44.159> used 01:22:44.270 --> 01:22:44.280 align:start position:0% layer but as a future proofing also used 01:22:44.280 --> 01:22:47.090 align:start position:0% layer but as a future proofing also used a<01:22:44.520> hash<01:22:44.760> function<01:22:45.060> shot<01:22:45.360> 256<01:22:46.080> which<01:22:46.679> fits 01:22:47.090 --> 01:22:47.100 align:start position:0% a hash function shot 256 which fits 01:22:47.100 --> 01:22:48.649 align:start position:0% a hash function shot 256 which fits really<01:22:47.159> well<01:22:47.460> into<01:22:47.640> a<01:22:47.940> standard<01:22:48.179> solidity 01:22:48.649 --> 01:22:48.659 align:start position:0% really well into a standard solidity 01:22:48.659 --> 01:22:50.270 align:start position:0% really well into a standard solidity data<01:22:48.960> type 01:22:50.270 --> 01:22:50.280 align:start position:0% data type 01:22:50.280 --> 01:22:53.149 align:start position:0% data type the<01:22:50.880> Azora<01:22:51.360> core<01:22:51.540> v0<01:22:52.020> solidity<01:22:52.860> has<01:22:53.040> a 01:22:53.149 --> 01:22:53.159 align:start position:0% the Azora core v0 solidity has a 01:22:53.159 --> 01:22:55.430 align:start position:0% the Azora core v0 solidity has a function<01:22:53.400> for<01:22:53.580> the<01:22:53.699> token<01:22:54.000> URI<01:22:54.420> which<01:22:54.840> is<01:22:55.260> not 01:22:55.430 --> 01:22:55.440 align:start position:0% function for the token URI which is not 01:22:55.440 --> 01:22:57.110 align:start position:0% function for the token URI which is not the<01:22:55.620> metadata<01:22:56.100> as<01:22:56.219> the<01:22:56.400> standard<01:22:56.640> defines<01:22:56.940> it 01:22:57.110 --> 01:22:57.120 align:start position:0% the metadata as the standard defines it 01:22:57.120 --> 01:22:58.610 align:start position:0% the metadata as the standard defines it breaks<01:22:57.420> the<01:22:57.540> standard<01:22:57.780> but<01:22:58.020> is<01:22:58.140> actually<01:22:58.320> the 01:22:58.610 --> 01:22:58.620 align:start position:0% breaks the standard but is actually the 01:22:58.620 --> 01:23:00.770 align:start position:0% breaks the standard but is actually the canonical<01:22:59.040> content<01:22:59.940> so<01:23:00.179> if<01:23:00.239> we<01:23:00.360> were<01:23:00.480> to<01:23:00.540> Mint 01:23:00.770 --> 01:23:00.780 align:start position:0% canonical content so if we were to Mint 01:23:00.780 --> 01:23:02.930 align:start position:0% canonical content so if we were to Mint a<01:23:00.900> presentation<01:23:01.260> it<01:23:01.500> would<01:23:01.560> be<01:23:01.679> the<01:23:01.800> PDF<01:23:02.219> and 01:23:02.930 --> 01:23:02.940 align:start position:0% a presentation it would be the PDF and 01:23:02.940 --> 01:23:04.550 align:start position:0% a presentation it would be the PDF and then<01:23:03.060> the<01:23:03.179> metadata<01:23:03.659> is<01:23:03.780> defined<01:23:04.140> also 01:23:04.550 --> 01:23:04.560 align:start position:0% then the metadata is defined also 01:23:04.560 --> 01:23:07.550 align:start position:0% then the metadata is defined also incredibly<01:23:04.980> simply<01:23:05.480> as<01:23:06.480> name<01:23:06.960> description 01:23:07.550 --> 01:23:07.560 align:start position:0% incredibly simply as name description 01:23:07.560 --> 01:23:09.950 align:start position:0% incredibly simply as name description mime<01:23:08.219> type<01:23:08.400> inversion<01:23:09.060> the<01:23:09.360> mime<01:23:09.540> type<01:23:09.780> is 01:23:09.950 --> 01:23:09.960 align:start position:0% mime type inversion the mime type is 01:23:09.960 --> 01:23:11.510 align:start position:0% mime type inversion the mime type is useful<01:23:10.199> for<01:23:10.380> rendering<01:23:10.739> as<01:23:10.860> I<01:23:10.980> said<01:23:11.100> you<01:23:11.340> need 01:23:11.510 --> 01:23:11.520 align:start position:0% useful for rendering as I said you need 01:23:11.520 --> 01:23:12.950 align:start position:0% useful for rendering as I said you need to<01:23:11.640> have<01:23:11.760> some<01:23:12.000> idea<01:23:12.360> of<01:23:12.480> what<01:23:12.659> you're<01:23:12.719> going 01:23:12.950 --> 01:23:12.960 align:start position:0% to have some idea of what you're going 01:23:12.960 --> 01:23:15.229 align:start position:0% to have some idea of what you're going to<01:23:13.080> render<01:23:13.320> before<01:23:13.620> and<01:23:14.520> fetching<01:23:15.000> it<01:23:15.120> from 01:23:15.229 --> 01:23:15.239 align:start position:0% to render before and fetching it from 01:23:15.239 --> 01:23:16.970 align:start position:0% to render before and fetching it from the<01:23:15.420> server<01:23:15.659> just<01:23:15.900> to<01:23:16.080> figure<01:23:16.199> out<01:23:16.500> what<01:23:16.860> the 01:23:16.970 --> 01:23:16.980 align:start position:0% the server just to figure out what the 01:23:16.980 --> 01:23:19.729 align:start position:0% the server just to figure out what the mime<01:23:17.159> type<01:23:17.400> is<01:23:17.640> is<01:23:18.239> a<01:23:18.420> little<01:23:18.480> bit<01:23:18.659> frustrating 01:23:19.729 --> 01:23:19.739 align:start position:0% mime type is is a little bit frustrating 01:23:19.739 --> 01:23:23.090 align:start position:0% mime type is is a little bit frustrating so<01:23:20.400> this<01:23:20.940> here<01:23:21.179> calls<01:23:22.020> the<01:23:22.140> token<01:23:22.440> URI<01:23:22.860> it 01:23:23.090 --> 01:23:23.100 align:start position:0% so this here calls the token URI it 01:23:23.100 --> 01:23:25.270 align:start position:0% so this here calls the token URI it returns<01:23:23.580> a<01:23:23.760> ipfs<01:23:24.420> file 01:23:25.270 --> 01:23:25.280 align:start position:0% returns a ipfs file 01:23:25.280 --> 01:23:29.630 align:start position:0% returns a ipfs file and<01:23:26.280> then<01:23:26.460> here<01:23:26.940> that<01:23:27.420> file<01:23:27.719> is<01:23:28.320> just<01:23:28.620> text<01:23:28.920> of 01:23:29.630 --> 01:23:29.640 align:start position:0% and then here that file is just text of 01:23:29.640 --> 01:23:31.130 align:start position:0% and then here that file is just text of these<01:23:29.880> two<01:23:30.000> icons 01:23:31.130 --> 01:23:31.140 align:start position:0% these two icons 01:23:31.140 --> 01:23:33.770 align:start position:0% these two icons the<01:23:31.380> token<01:23:31.620> metadata<01:23:32.219> URI<01:23:32.640> is<01:23:33.480> name 01:23:33.770 --> 01:23:33.780 align:start position:0% the token metadata URI is name 01:23:33.780 --> 01:23:35.870 align:start position:0% the token metadata URI is name description<01:23:34.140> mine<01:23:34.440> type<01:23:34.679> textplane<01:23:35.400> so<01:23:35.760> that 01:23:35.870 --> 01:23:35.880 align:start position:0% description mine type textplane so that 01:23:35.880 --> 01:23:38.870 align:start position:0% description mine type textplane so that tells<01:23:36.179> the<01:23:36.239> Zora<01:23:36.659> platform<01:23:37.020> to<01:23:37.800> render<01:23:38.040> a<01:23:38.699> text 01:23:38.870 --> 01:23:38.880 align:start position:0% tells the Zora platform to render a text 01:23:38.880 --> 01:23:42.410 align:start position:0% tells the Zora platform to render a text plane<01:23:39.360> image<01:23:39.780> of<01:23:40.560> that<01:23:40.800> per<01:23:41.040> text<01:23:41.640> plane<01:23:42.060> of 01:23:42.410 --> 01:23:42.420 align:start position:0% plane image of that per text plane of 01:23:42.420 --> 01:23:44.630 align:start position:0% plane image of that per text plane of that<01:23:42.540> nft<01:23:42.840> and<01:23:43.679> I<01:23:43.800> don't<01:23:43.980> think<01:23:44.280> there<01:23:44.520> have 01:23:44.630 --> 01:23:44.640 align:start position:0% that nft and I don't think there have 01:23:44.640 --> 01:23:46.010 align:start position:0% that nft and I don't think there have been<01:23:44.760> a<01:23:44.880> lot<01:23:44.940> of<01:23:45.060> platforms<01:23:45.540> that<01:23:45.719> support 01:23:46.010 --> 01:23:46.020 align:start position:0% been a lot of platforms that support 01:23:46.020 --> 01:23:47.630 align:start position:0% been a lot of platforms that support this<01:23:46.320> so<01:23:46.560> when<01:23:46.739> you<01:23:46.860> try<01:23:46.980> to<01:23:47.040> look<01:23:47.159> at<01:23:47.280> an<01:23:47.520> open 01:23:47.630 --> 01:23:47.640 align:start position:0% this so when you try to look at an open 01:23:47.640 --> 01:23:49.790 align:start position:0% this so when you try to look at an open C<01:23:48.000> good<01:23:48.480> luck 01:23:49.790 --> 01:23:49.800 align:start position:0% C good luck 01:23:49.800 --> 01:23:51.830 align:start position:0% C good luck um<01:23:50.340> and<01:23:50.820> that<01:23:50.940> brings<01:23:51.120> me<01:23:51.239> to<01:23:51.360> my<01:23:51.480> next<01:23:51.659> point 01:23:51.830 --> 01:23:51.840 align:start position:0% um and that brings me to my next point 01:23:51.840 --> 01:23:53.630 align:start position:0% um and that brings me to my next point of<01:23:52.140> thinking<01:23:52.500> about<01:23:52.620> going<01:23:53.219> back<01:23:53.460> in 01:23:53.630 --> 01:23:53.640 align:start position:0% of thinking about going back in 01:23:53.640 --> 01:23:55.490 align:start position:0% of thinking about going back in Computing<01:23:54.000> history<01:23:54.179> of<01:23:54.540> what<01:23:54.900> people<01:23:55.260> have 01:23:55.490 --> 01:23:55.500 align:start position:0% Computing history of what people have 01:23:55.500 --> 01:23:56.810 align:start position:0% Computing history of what people have done<01:23:55.679> to<01:23:55.800> solve<01:23:56.100> this<01:23:56.159> problem<01:23:56.280> this<01:23:56.580> is<01:23:56.699> a 01:23:56.810 --> 01:23:56.820 align:start position:0% done to solve this problem this is a 01:23:56.820 --> 01:23:59.149 align:start position:0% done to solve this problem this is a multi-part<01:23:57.300> form<01:23:57.540> data<01:23:58.080> it's<01:23:58.440> used<01:23:58.679> for<01:23:58.920> email 01:23:59.149 --> 01:23:59.159 align:start position:0% multi-part form data it's used for email 01:23:59.159 --> 01:24:01.669 align:start position:0% multi-part form data it's used for email kind<01:23:59.640> of<01:23:59.820> and<01:24:00.360> used<01:24:00.540> when<01:24:00.780> you<01:24:00.960> upload<01:24:01.260> files 01:24:01.669 --> 01:24:01.679 align:start position:0% kind of and used when you upload files 01:24:01.679 --> 01:24:03.830 align:start position:0% kind of and used when you upload files in<01:24:01.860> a<01:24:02.040> classic<01:24:02.159> web<01:24:02.460> form<01:24:02.699> it<01:24:03.360> has<01:24:03.480> content 01:24:03.830 --> 01:24:03.840 align:start position:0% in a classic web form it has content 01:24:03.840 --> 01:24:05.390 align:start position:0% in a classic web form it has content type<01:24:04.020> and<01:24:04.320> it<01:24:04.440> has<01:24:04.620> a<01:24:04.739> certain<01:24:05.040> set<01:24:05.219> of 01:24:05.390 --> 01:24:05.400 align:start position:0% type and it has a certain set of 01:24:05.400 --> 01:24:06.590 align:start position:0% type and it has a certain set of attachments<01:24:05.820> you<01:24:06.000> can<01:24:06.120> kind<01:24:06.239> of<01:24:06.300> think<01:24:06.420> of 01:24:06.590 --> 01:24:06.600 align:start position:0% attachments you can kind of think of 01:24:06.600 --> 01:24:08.450 align:start position:0% attachments you can kind of think of this<01:24:06.840> as<01:24:07.260> an<01:24:07.440> email<01:24:07.560> attachment<01:24:07.980> so<01:24:08.219> I<01:24:08.340> think 01:24:08.450 --> 01:24:08.460 align:start position:0% this as an email attachment so I think 01:24:08.460 --> 01:24:10.189 align:start position:0% this as an email attachment so I think having<01:24:08.640> content<01:24:09.120> type<01:24:09.360> is<01:24:09.600> quite<01:24:09.840> important 01:24:10.189 --> 01:24:10.199 align:start position:0% having content type is quite important 01:24:10.199 --> 01:24:12.110 align:start position:0% having content type is quite important content<01:24:10.920> like<01:24:11.040> maybe<01:24:11.400> we<01:24:11.760> can<01:24:11.880> talk<01:24:12.000> about 01:24:12.110 --> 01:24:12.120 align:start position:0% content like maybe we can talk about 01:24:12.120 --> 01:24:13.669 align:start position:0% content like maybe we can talk about that<01:24:12.360> a<01:24:12.480> little<01:24:12.540> bit<01:24:12.659> later<01:24:12.840> and<01:24:13.380> then<01:24:13.560> the 01:24:13.669 --> 01:24:13.679 align:start position:0% that a little bit later and then the 01:24:13.679 --> 01:24:16.610 align:start position:0% that a little bit later and then the body<01:24:13.860> of<01:24:14.159> that<01:24:14.280> exact<01:24:14.820> content 01:24:16.610 --> 01:24:16.620 align:start position:0% body of that exact content 01:24:16.620 --> 01:24:18.649 align:start position:0% body of that exact content here<01:24:17.100> you<01:24:17.280> have<01:24:17.400> an<01:24:17.520> example 01:24:18.649 --> 01:24:18.659 align:start position:0% here you have an example 01:24:18.659 --> 01:24:22.130 align:start position:0% here you have an example um<01:24:18.780> sorry<01:24:19.080> got<01:24:19.739> out<01:24:19.980> of<01:24:20.100> weight 01:24:22.130 --> 01:24:22.140 align:start position:0% um sorry got out of weight 01:24:22.140 --> 01:24:26.090 align:start position:0% um sorry got out of weight so<01:24:23.100> an<01:24:23.219> example<01:24:23.580> of<01:24:24.060> what<01:24:24.239> we<01:24:24.420> could<01:24:24.540> do<01:24:24.780> is<01:24:25.739> add 01:24:26.090 --> 01:24:26.100 align:start position:0% so an example of what we could do is add 01:24:26.100 --> 01:24:27.830 align:start position:0% so an example of what we could do is add a<01:24:26.280> new<01:24:26.460> field<01:24:26.640> to<01:24:27.000> the<01:24:27.120> metadata<01:24:27.540> standard 01:24:27.830 --> 01:24:27.840 align:start position:0% a new field to the metadata standard 01:24:27.840 --> 01:24:30.110 align:start position:0% a new field to the metadata standard either<01:24:28.199> through<01:24:28.560> a<01:24:29.219> secondary<01:24:29.580> proposal 01:24:30.110 --> 01:24:30.120 align:start position:0% either through a secondary proposal 01:24:30.120 --> 01:24:32.510 align:start position:0% either through a secondary proposal mechanism<01:24:30.540> or<01:24:30.840> the<01:24:30.960> EIP<01:24:31.260> standard<01:24:31.800> that 01:24:32.510 --> 01:24:32.520 align:start position:0% mechanism or the EIP standard that 01:24:32.520 --> 01:24:34.669 align:start position:0% mechanism or the EIP standard that represents<01:24:33.060> what<01:24:33.420> we<01:24:33.540> just<01:24:33.659> talked<01:24:33.960> about<01:24:34.020> and 01:24:34.669 --> 01:24:34.679 align:start position:0% represents what we just talked about and 01:24:34.679 --> 01:24:36.169 align:start position:0% represents what we just talked about and there's<01:24:34.800> a<01:24:34.980> lot<01:24:35.040> of<01:24:35.159> details<01:24:35.580> here<01:24:35.760> to<01:24:35.880> unpack 01:24:36.169 --> 01:24:36.179 align:start position:0% there's a lot of details here to unpack 01:24:36.179 --> 01:24:38.689 align:start position:0% there's a lot of details here to unpack so<01:24:36.420> one<01:24:36.659> of<01:24:36.780> them<01:24:36.900> is<01:24:37.620> maybe<01:24:37.920> you'll<01:24:38.400> want<01:24:38.580> to 01:24:38.689 --> 01:24:38.699 align:start position:0% so one of them is maybe you'll want to 01:24:38.699 --> 01:24:40.250 align:start position:0% so one of them is maybe you'll want to include<01:24:39.000> the<01:24:39.120> content<01:24:39.420> directly<01:24:39.840> should<01:24:40.080> it 01:24:40.250 --> 01:24:40.260 align:start position:0% include the content directly should it 01:24:40.260 --> 01:24:41.990 align:start position:0% include the content directly should it be<01:24:40.320> body<01:24:40.500> or<01:24:40.860> should<01:24:40.980> it<01:24:41.100> be<01:24:41.219> encoded<01:24:41.640> in<01:24:41.880> a 01:24:41.990 --> 01:24:42.000 align:start position:0% be body or should it be encoded in a 01:24:42.000 --> 01:24:43.850 align:start position:0% be body or should it be encoded in a data<01:24:42.300> URI<01:24:42.600> in<01:24:42.960> that<01:24:43.020> case<01:24:43.199> the<01:24:43.380> content<01:24:43.679> type 01:24:43.850 --> 01:24:43.860 align:start position:0% data URI in that case the content type 01:24:43.860 --> 01:24:46.250 align:start position:0% data URI in that case the content type is<01:24:44.100> redundant<01:24:44.940> but<01:24:45.540> when<01:24:45.780> you<01:24:45.900> have<01:24:46.020> an 01:24:46.250 --> 01:24:46.260 align:start position:0% is redundant but when you have an 01:24:46.260 --> 01:24:48.770 align:start position:0% is redundant but when you have an external<01:24:46.820> pinned<01:24:47.820> file<01:24:48.060> you<01:24:48.420> really<01:24:48.540> want 01:24:48.770 --> 01:24:48.780 align:start position:0% external pinned file you really want 01:24:48.780 --> 01:24:50.149 align:start position:0% external pinned file you really want that<01:24:48.900> content<01:24:49.199> type<01:24:49.380> for<01:24:49.560> rendering<01:24:49.860> it<01:24:50.040> just 01:24:50.149 --> 01:24:50.159 align:start position:0% that content type for rendering it just 01:24:50.159 --> 01:24:51.649 align:start position:0% that content type for rendering it just makes<01:24:50.280> life<01:24:50.460> so<01:24:50.760> much<01:24:50.880> easier<01:24:51.179> from<01:24:51.480> a 01:24:51.649 --> 01:24:51.659 align:start position:0% makes life so much easier from a 01:24:51.659 --> 01:24:53.689 align:start position:0% makes life so much easier from a platform<01:24:51.960> and<01:24:52.140> indexing<01:24:52.620> standpoint<01:24:53.040> if<01:24:53.640> you 01:24:53.689 --> 01:24:53.699 align:start position:0% platform and indexing standpoint if you 01:24:53.699 --> 01:24:55.310 align:start position:0% platform and indexing standpoint if you have<01:24:53.880> a<01:24:54.060> really<01:24:54.179> obscure<01:24:54.600> file<01:24:54.900> type<01:24:55.080> let's 01:24:55.310 --> 01:24:55.320 align:start position:0% have a really obscure file type let's 01:24:55.320 --> 01:24:56.870 align:start position:0% have a really obscure file type let's say<01:24:55.500> somebody<01:24:55.679> loves<01:24:56.040> to<01:24:56.159> upload<01:24:56.460> Illustrator 01:24:56.870 --> 01:24:56.880 align:start position:0% say somebody loves to upload Illustrator 01:24:56.880 --> 01:24:58.970 align:start position:0% say somebody loves to upload Illustrator files<01:24:57.300> you<01:24:57.900> could<01:24:57.960> use<01:24:58.140> an<01:24:58.380> indexer<01:24:58.739> to<01:24:58.920> find 01:24:58.970 --> 01:24:58.980 align:start position:0% files you could use an indexer to find 01:24:58.980 --> 01:25:01.010 align:start position:0% files you could use an indexer to find every<01:24:59.219> illustrator<01:24:59.699> file<01:25:00.060> with<01:25:00.719> a<01:25:00.900> very 01:25:01.010 --> 01:25:01.020 align:start position:0% every illustrator file with a very 01:25:01.020 --> 01:25:02.630 align:start position:0% every illustrator file with a very simple<01:25:01.199> content<01:25:01.679> standard 01:25:02.630 --> 01:25:02.640 align:start position:0% simple content standard 01:25:02.640 --> 01:25:04.850 align:start position:0% simple content standard and<01:25:03.120> I<01:25:03.239> think<01:25:03.420> the<01:25:03.780> idea<01:25:04.080> here<01:25:04.260> is<01:25:04.440> you<01:25:04.560> have<01:25:04.739> a 01:25:04.850 --> 01:25:04.860 align:start position:0% and I think the idea here is you have a 01:25:04.860 --> 01:25:07.189 align:start position:0% and I think the idea here is you have a token<01:25:05.159> ID<01:25:05.280> represented<01:25:05.940> by<01:25:06.120> a<01:25:06.300> file<01:25:06.600> and<01:25:07.080> the 01:25:07.189 --> 01:25:07.199 align:start position:0% token ID represented by a file and the 01:25:07.199 --> 01:25:09.050 align:start position:0% token ID represented by a file and the metadata<01:25:07.620> describes<01:25:08.040> that<01:25:08.159> file<01:25:08.460> is<01:25:08.640> but<01:25:08.820> that 01:25:09.050 --> 01:25:09.060 align:start position:0% metadata describes that file is but that 01:25:09.060 --> 01:25:10.970 align:start position:0% metadata describes that file is but that file<01:25:09.300> when<01:25:09.659> you<01:25:09.840> need<01:25:10.140> to<01:25:10.260> have<01:25:10.380> a<01:25:10.500> file<01:25:10.679> with 01:25:10.970 --> 01:25:10.980 align:start position:0% file when you need to have a file with 01:25:10.980 --> 01:25:14.570 align:start position:0% file when you need to have a file with your<01:25:11.100> nft<01:25:11.540> is<01:25:12.540> the<01:25:12.719> highest<01:25:13.080> resolution<01:25:13.580> the 01:25:14.570 --> 01:25:14.580 align:start position:0% your nft is the highest resolution the 01:25:14.580 --> 01:25:15.590 align:start position:0% your nft is the highest resolution the most 01:25:15.590 --> 01:25:15.600 align:start position:0% most 01:25:15.600 --> 01:25:16.430 align:start position:0% most um 01:25:16.430 --> 01:25:16.440 align:start position:0% um 01:25:16.440 --> 01:25:18.530 align:start position:0% um the<01:25:16.800> highest<01:25:17.040> resolution<01:25:17.420> the<01:25:18.420> most 01:25:18.530 --> 01:25:18.540 align:start position:0% the highest resolution the most 01:25:18.540 --> 01:25:20.930 align:start position:0% the highest resolution the most well-known<01:25:18.960> version<01:25:19.260> of<01:25:19.560> that<01:25:19.679> an<01:25:20.400> example<01:25:20.699> is 01:25:20.930 --> 01:25:20.940 align:start position:0% well-known version of that an example is 01:25:20.940 --> 01:25:24.649 align:start position:0% well-known version of that an example is Zora<01:25:21.480> was<01:25:22.040> brought<01:25:23.040> on<01:25:23.159> to<01:25:23.460> work<01:25:23.699> with 01:25:24.649 --> 01:25:24.659 align:start position:0% Zora was brought on to work with 01:25:24.659 --> 01:25:27.830 align:start position:0% Zora was brought on to work with the<01:25:25.320> Warhol<01:25:25.800> Foundation<01:25:26.280> to<01:25:26.760> Mint<01:25:26.940> one<01:25:27.420> of<01:25:27.540> the 01:25:27.830 --> 01:25:27.840 align:start position:0% the Warhol Foundation to Mint one of the 01:25:27.840 --> 01:25:31.010 align:start position:0% the Warhol Foundation to Mint one of the original<01:25:28.080> computer<01:25:29.060> nfts<01:25:30.060> and<01:25:30.659> it<01:25:30.780> was<01:25:30.840> made 01:25:31.010 --> 01:25:31.020 align:start position:0% original computer nfts and it was made 01:25:31.020 --> 01:25:33.770 align:start position:0% original computer nfts and it was made on<01:25:31.199> an<01:25:31.380> Amiga<01:25:31.920> with<01:25:32.340> a<01:25:32.699> beta<01:25:33.360> version<01:25:33.480> of 01:25:33.770 --> 01:25:33.780 align:start position:0% on an Amiga with a beta version of 01:25:33.780 --> 01:25:35.990 align:start position:0% on an Amiga with a beta version of software<01:25:34.140> an<01:25:34.980> art<01:25:35.100> collector<01:25:35.580> is<01:25:35.699> really 01:25:35.990 --> 01:25:36.000 align:start position:0% software an art collector is really 01:25:36.000 --> 01:25:39.050 align:start position:0% software an art collector is really frustrated<01:25:36.480> that<01:25:36.840> the<01:25:37.260> nft<01:25:37.920> was<01:25:38.340> a<01:25:38.520> tiff<01:25:38.699> file 01:25:39.050 --> 01:25:39.060 align:start position:0% frustrated that the nft was a tiff file 01:25:39.060 --> 01:25:40.850 align:start position:0% frustrated that the nft was a tiff file but<01:25:39.540> it<01:25:39.659> was<01:25:39.780> built<01:25:40.020> with<01:25:40.080> the<01:25:40.199> Zora<01:25:40.620> protocol 01:25:40.850 --> 01:25:40.860 align:start position:0% but it was built with the Zora protocol 01:25:40.860 --> 01:25:42.590 align:start position:0% but it was built with the Zora protocol meaning<01:25:41.159> it<01:25:41.580> did<01:25:41.699> support<01:25:41.820> Tiff<01:25:42.239> files 01:25:42.590 --> 01:25:42.600 align:start position:0% meaning it did support Tiff files 01:25:42.600 --> 01:25:45.050 align:start position:0% meaning it did support Tiff files however<01:25:43.440> nobody<01:25:43.800> else<01:25:43.980> did<01:25:44.219> so<01:25:44.699> what<01:25:44.760> we<01:25:44.940> had 01:25:45.050 --> 01:25:45.060 align:start position:0% however nobody else did so what we had 01:25:45.060 --> 01:25:47.090 align:start position:0% however nobody else did so what we had to<01:25:45.179> end<01:25:45.300> up<01:25:45.420> doing<01:25:45.600> is<01:25:45.840> use<01:25:46.020> the<01:25:46.199> external<01:25:46.620> URL 01:25:47.090 --> 01:25:47.100 align:start position:0% to end up doing is use the external URL 01:25:47.100 --> 01:25:49.189 align:start position:0% to end up doing is use the external URL which<01:25:47.280> is<01:25:47.400> an<01:25:47.580> openc<01:25:48.000> extension<01:25:48.540> to<01:25:48.780> link<01:25:48.960> to 01:25:49.189 --> 01:25:49.199 align:start position:0% which is an openc extension to link to 01:25:49.199 --> 01:25:51.890 align:start position:0% which is an openc extension to link to something<01:25:49.440> to<01:25:50.040> link<01:25:50.219> to<01:25:50.460> the<01:25:50.699> Tiff<01:25:51.000> and<01:25:51.780> then 01:25:51.890 --> 01:25:51.900 align:start position:0% something to link to the Tiff and then 01:25:51.900 --> 01:25:55.010 align:start position:0% something to link to the Tiff and then switch<01:25:52.199> the<01:25:52.500> image<01:25:52.800> URI<01:25:53.280> to<01:25:54.000> become<01:25:54.360> a<01:25:54.780> PNG 01:25:55.010 --> 01:25:55.020 align:start position:0% switch the image URI to become a PNG 01:25:55.020 --> 01:25:56.930 align:start position:0% switch the image URI to become a PNG that<01:25:55.440> renders<01:25:55.739> everywhere<01:25:56.100> and<01:25:56.699> this<01:25:56.820> is 01:25:56.930 --> 01:25:56.940 align:start position:0% that renders everywhere and this is 01:25:56.940 --> 01:25:58.610 align:start position:0% that renders everywhere and this is after<01:25:57.300> back<01:25:57.960> and<01:25:58.139> forth<01:25:58.380> with 01:25:58.610 --> 01:25:58.620 align:start position:0% after back and forth with 01:25:58.620 --> 01:26:00.290 align:start position:0% after back and forth with conservationist<01:25:59.400> and<01:25:59.760> with<01:26:00.000> different 01:26:00.290 --> 01:26:00.300 align:start position:0% conservationist and with different 01:26:00.300 --> 01:26:02.149 align:start position:0% conservationist and with different protocols<01:26:00.900> as<01:26:01.080> to<01:26:01.260> what<01:26:01.380> they<01:26:01.500> expect<01:26:01.679> the<01:26:01.920> nft 01:26:02.149 --> 01:26:02.159 align:start position:0% protocols as to what they expect the nft 01:26:02.159 --> 01:26:05.750 align:start position:0% protocols as to what they expect the nft to<01:26:02.460> be<01:26:03.000> now<01:26:03.659> if<01:26:04.080> we<01:26:04.199> were<01:26:04.380> to<01:26:04.500> use<01:26:04.920> the<01:26:05.460> content 01:26:05.750 --> 01:26:05.760 align:start position:0% to be now if we were to use the content 01:26:05.760 --> 01:26:07.850 align:start position:0% to be now if we were to use the content standard<01:26:06.120> we<01:26:06.659> could<01:26:06.780> Define<01:26:07.020> the<01:26:07.320> image<01:26:07.620> that 01:26:07.850 --> 01:26:07.860 align:start position:0% standard we could Define the image that 01:26:07.860 --> 01:26:10.610 align:start position:0% standard we could Define the image that renders<01:26:08.280> as<01:26:08.580> a<01:26:08.760> preview<01:26:09.060> with<01:26:09.540> ipfs<01:26:10.139> and<01:26:10.500> then 01:26:10.610 --> 01:26:10.620 align:start position:0% renders as a preview with ipfs and then 01:26:10.620 --> 01:26:12.830 align:start position:0% renders as a preview with ipfs and then we<01:26:10.800> could<01:26:10.920> use<01:26:11.159> the<01:26:11.400> Amica<01:26:11.760> mime<01:26:12.239> type<01:26:12.420> or<01:26:12.659> just 01:26:12.830 --> 01:26:12.840 align:start position:0% we could use the Amica mime type or just 01:26:12.840 --> 01:26:15.410 align:start position:0% we could use the Amica mime type or just a<01:26:13.020> binary<01:26:13.380> blob<01:26:13.800> with<01:26:14.520> some<01:26:14.639> notes<01:26:15.000> around<01:26:15.120> it 01:26:15.410 --> 01:26:15.420 align:start position:0% a binary blob with some notes around it 01:26:15.420 --> 01:26:18.410 align:start position:0% a binary blob with some notes around it in<01:26:16.080> the<01:26:16.260> description<01:26:16.580> to<01:26:17.580> refer<01:26:18.000> to<01:26:18.179> the 01:26:18.410 --> 01:26:18.420 align:start position:0% in the description to refer to the 01:26:18.420 --> 01:26:19.850 align:start position:0% in the description to refer to the original<01:26:18.600> media<01:26:19.139> and<01:26:19.320> I<01:26:19.440> think<01:26:19.500> that<01:26:19.679> would 01:26:19.850 --> 01:26:19.860 align:start position:0% original media and I think that would 01:26:19.860 --> 01:26:21.310 align:start position:0% original media and I think that would help 01:26:21.310 --> 01:26:21.320 align:start position:0% help 01:26:21.320 --> 01:26:23.689 align:start position:0% help conservationists<01:26:22.320> feel<01:26:22.500> better<01:26:22.860> that<01:26:23.460> the 01:26:23.689 --> 01:26:23.699 align:start position:0% conservationists feel better that the 01:26:23.699 --> 01:26:25.370 align:start position:0% conservationists feel better that the nft<01:26:23.940> is<01:26:24.300> representing<01:26:24.840> what<01:26:25.020> it<01:26:25.199> really 01:26:25.370 --> 01:26:25.380 align:start position:0% nft is representing what it really 01:26:25.380 --> 01:26:27.590 align:start position:0% nft is representing what it really represents<01:26:26.040> and<01:26:26.340> not<01:26:26.520> needed<01:26:27.060> to<01:26:27.360> be 01:26:27.590 --> 01:26:27.600 align:start position:0% represents and not needed to be 01:26:27.600 --> 01:26:34.070 align:start position:0% represents and not needed to be converted<01:26:28.380> into<01:26:28.739> a<01:26:28.980> new<01:26:29.100> format<01:26:29.520> to<01:26:29.940> be<01:26:30.060> an<01:26:30.179> nft 01:26:34.070 --> 01:26:34.080 align:start position:0% 01:26:34.080 --> 01:26:37.010 align:start position:0% and<01:26:34.620> a<01:26:34.800> second<01:26:35.040> example<01:26:35.460> of<01:26:35.699> this<01:26:35.940> is<01:26:36.540> mirror 01:26:37.010 --> 01:26:37.020 align:start position:0% and a second example of this is mirror 01:26:37.020 --> 01:26:39.470 align:start position:0% and a second example of this is mirror so<01:26:37.440> if<01:26:37.620> you<01:26:37.800> were<01:26:37.920> to<01:26:38.040> Mint<01:26:38.580> a<01:26:39.000> mirror 01:26:39.470 --> 01:26:39.480 align:start position:0% so if you were to Mint a mirror 01:26:39.480 --> 01:26:42.770 align:start position:0% so if you were to Mint a mirror Marketplace<01:26:40.320> essay<01:26:40.800> this<01:26:41.280> is<01:26:41.400> what<01:26:41.580> it<01:26:41.699> shows 01:26:42.770 --> 01:26:42.780 align:start position:0% Marketplace essay this is what it shows 01:26:42.780 --> 01:26:44.990 align:start position:0% Marketplace essay this is what it shows it<01:26:43.500> just<01:26:43.620> shows<01:26:43.980> a<01:26:44.159> cover<01:26:44.280> image<01:26:44.639> of<01:26:44.760> the<01:26:44.880> text 01:26:44.990 --> 01:26:45.000 align:start position:0% it just shows a cover image of the text 01:26:45.000 --> 01:26:47.209 align:start position:0% it just shows a cover image of the text of<01:26:45.239> the<01:26:45.360> title<01:26:45.719> a<01:26:46.380> description<01:26:46.679> which<01:26:46.980> is<01:26:47.100> a 01:26:47.209 --> 01:26:47.219 align:start position:0% of the title a description which is a 01:26:47.219 --> 01:26:50.450 align:start position:0% of the title a description which is a link<01:26:47.340> to<01:26:47.520> mirror<01:26:47.940> and<01:26:48.900> that's<01:26:49.320> it<01:26:49.560> I<01:26:50.340> think 01:26:50.450 --> 01:26:50.460 align:start position:0% link to mirror and that's it I think 01:26:50.460 --> 01:26:51.530 align:start position:0% link to mirror and that's it I think there<01:26:50.639> might<01:26:50.820> be<01:26:50.880> like<01:26:51.060> the<01:26:51.239> author 01:26:51.530 --> 01:26:51.540 align:start position:0% there might be like the author 01:26:51.540 --> 01:26:53.570 align:start position:0% there might be like the author information<01:26:51.719> in<01:26:52.139> the<01:26:52.320> properties 01:26:53.570 --> 01:26:53.580 align:start position:0% information in the properties 01:26:53.580 --> 01:26:55.310 align:start position:0% information in the properties but 01:26:55.310 --> 01:26:55.320 align:start position:0% but 01:26:55.320 --> 01:26:57.590 align:start position:0% but it<01:26:55.620> would<01:26:55.800> be<01:26:55.980> really<01:26:56.159> cool<01:26:56.460> if<01:26:56.760> quixotic<01:26:57.360> has 01:26:57.590 --> 01:26:57.600 align:start position:0% it would be really cool if quixotic has 01:26:57.600 --> 01:26:59.450 align:start position:0% it would be really cool if quixotic has a<01:26:57.780> relationship<01:26:58.080> with<01:26:58.320> mirror<01:26:58.860> and<01:26:59.340> they 01:26:59.450 --> 01:26:59.460 align:start position:0% a relationship with mirror and they 01:26:59.460 --> 01:27:01.010 align:start position:0% a relationship with mirror and they could<01:26:59.639> download<01:26:59.820> the<01:27:00.120> canonical<01:27:00.540> markdown 01:27:01.010 --> 01:27:01.020 align:start position:0% could download the canonical markdown 01:27:01.020 --> 01:27:03.050 align:start position:0% could download the canonical markdown file<01:27:01.380> and<01:27:01.739> start<01:27:01.920> rendering<01:27:02.400> it<01:27:02.580> on<01:27:02.880> their 01:27:03.050 --> 01:27:03.060 align:start position:0% file and start rendering it on their 01:27:03.060 --> 01:27:05.390 align:start position:0% file and start rendering it on their site<01:27:03.300> or<01:27:03.900> at<01:27:04.020> least<01:27:04.139> say<01:27:04.440> hey<01:27:04.800> there's<01:27:05.159> a 01:27:05.390 --> 01:27:05.400 align:start position:0% site or at least say hey there's a 01:27:05.400 --> 01:27:07.610 align:start position:0% site or at least say hey there's a canonical<01:27:05.820> markdown<01:27:06.360> file<01:27:06.659> associated<01:27:07.320> with 01:27:07.610 --> 01:27:07.620 align:start position:0% canonical markdown file associated with 01:27:07.620 --> 01:27:09.530 align:start position:0% canonical markdown file associated with this<01:27:07.860> and<01:27:08.400> like<01:27:08.520> GitHub<01:27:08.940> it<01:27:09.120> would<01:27:09.239> just<01:27:09.420> open 01:27:09.530 --> 01:27:09.540 align:start position:0% this and like GitHub it would just open 01:27:09.540 --> 01:27:12.890 align:start position:0% this and like GitHub it would just open a<01:27:09.840> markdown<01:27:10.320> viewer<01:27:10.679> if<01:27:10.800> it<01:27:10.920> understood<01:27:11.280> it 01:27:12.890 --> 01:27:12.900 align:start position:0% a markdown viewer if it understood it 01:27:12.900 --> 01:27:15.169 align:start position:0% a markdown viewer if it understood it and<01:27:13.320> we<01:27:13.440> can<01:27:13.560> take<01:27:13.679> a<01:27:13.800> look<01:27:13.860> at<01:27:14.040> the<01:27:14.159> Json<01:27:14.400> here 01:27:15.169 --> 01:27:15.179 align:start position:0% and we can take a look at the Json here 01:27:15.179 --> 01:27:18.470 align:start position:0% and we can take a look at the Json here so<01:27:15.780> if<01:27:16.080> mirror<01:27:16.800> currently<01:27:17.159> what<01:27:17.400> they<01:27:17.580> have<01:27:17.760> is 01:27:18.470 --> 01:27:18.480 align:start position:0% so if mirror currently what they have is 01:27:18.480 --> 01:27:20.570 align:start position:0% so if mirror currently what they have is they<01:27:18.659> have<01:27:18.900> a<01:27:19.080> Content<01:27:19.380> field<01:27:19.560> and<01:27:20.100> it<01:27:20.219> goes<01:27:20.460> to 01:27:20.570 --> 01:27:20.580 align:start position:0% they have a Content field and it goes to 01:27:20.580 --> 01:27:23.510 align:start position:0% they have a Content field and it goes to an<01:27:20.760> are<01:27:20.940> we<01:27:21.120> file<01:27:21.480> which<01:27:21.780> is<01:27:21.960> a<01:27:22.199> custom<01:27:22.520> content 01:27:23.510 --> 01:27:23.520 align:start position:0% an are we file which is a custom content 01:27:23.520 --> 01:27:26.209 align:start position:0% an are we file which is a custom content type<01:27:23.699> they've<01:27:24.060> defined<01:27:24.360> it's<01:27:24.780> quite<01:27:25.080> and<01:27:25.860> Rich 01:27:26.209 --> 01:27:26.219 align:start position:0% type they've defined it's quite and Rich 01:27:26.219 --> 01:27:28.490 align:start position:0% type they've defined it's quite and Rich has<01:27:26.639> a<01:27:26.820> lot<01:27:26.940> of<01:27:27.060> information<01:27:27.239> but<01:27:28.080> it<01:27:28.199> has<01:27:28.320> the 01:27:28.490 --> 01:27:28.500 align:start position:0% has a lot of information but it has the 01:27:28.500 --> 01:27:31.129 align:start position:0% has a lot of information but it has the body<01:27:28.679> the<01:27:29.040> author<01:27:29.460> information<01:27:30.139> signature 01:27:31.129 --> 01:27:31.139 align:start position:0% body the author information signature 01:27:31.139 --> 01:27:32.689 align:start position:0% body the author information signature information<01:27:31.320> and<01:27:31.860> stuff<01:27:32.040> they<01:27:32.219> use<01:27:32.400> to<01:27:32.580> run 01:27:32.689 --> 01:27:32.699 align:start position:0% information and stuff they use to run 01:27:32.699 --> 01:27:34.610 align:start position:0% information and stuff they use to run their<01:27:32.940> platform 01:27:34.610 --> 01:27:34.620 align:start position:0% their platform 01:27:34.620 --> 01:27:36.709 align:start position:0% their platform is<01:27:34.980> is<01:27:35.219> if<01:27:35.400> we're<01:27:35.580> coming<01:27:35.820> at<01:27:36.120> this<01:27:36.300> from<01:27:36.540> a 01:27:36.709 --> 01:27:36.719 align:start position:0% is is if we're coming at this from a 01:27:36.719 --> 01:27:38.750 align:start position:0% is is if we're coming at this from a perspective<01:27:37.080> of<01:27:37.440> an<01:27:37.679> indexer 01:27:38.750 --> 01:27:38.760 align:start position:0% perspective of an indexer 01:27:38.760 --> 01:27:41.270 align:start position:0% perspective of an indexer this<01:27:39.239> is<01:27:39.360> not<01:27:39.540> very<01:27:39.780> helpful<01:27:40.199> we<01:27:40.679> could<01:27:40.800> try<01:27:41.040> to 01:27:41.270 --> 01:27:41.280 align:start position:0% this is not very helpful we could try to 01:27:41.280 --> 01:27:43.850 align:start position:0% this is not very helpful we could try to expand<01:27:41.639> that<01:27:41.880> content<01:27:42.300> field<01:27:42.540> but<01:27:43.320> that<01:27:43.620> could 01:27:43.850 --> 01:27:43.860 align:start position:0% expand that content field but that could 01:27:43.860 --> 01:27:45.950 align:start position:0% expand that content field but that could be<01:27:44.159> any<01:27:44.520> file<01:27:44.760> type<01:27:45.000> as<01:27:45.179> I<01:27:45.360> said<01:27:45.480> before<01:27:45.659> it 01:27:45.950 --> 01:27:45.960 align:start position:0% be any file type as I said before it 01:27:45.960 --> 01:27:48.350 align:start position:0% be any file type as I said before it could<01:27:46.139> be<01:27:46.380> some<01:27:46.860> binary<01:27:47.280> blob<01:27:47.699> or<01:27:48.060> it<01:27:48.239> actually 01:27:48.350 --> 01:27:48.360 align:start position:0% could be some binary blob or it actually 01:27:48.360 --> 01:27:50.510 align:start position:0% could be some binary blob or it actually could<01:27:48.600> be<01:27:48.719> useful<01:27:49.020> Json<01:27:49.440> so<01:27:49.739> if<01:27:49.980> it's<01:27:50.159> defined 01:27:50.510 --> 01:27:50.520 align:start position:0% could be useful Json so if it's defined 01:27:50.520 --> 01:27:53.290 align:start position:0% could be useful Json so if it's defined as<01:27:50.699> Json<01:27:51.120> or<01:27:51.719> maybe<01:27:51.840> an<01:27:52.080> extension<01:27:52.440> to<01:27:52.560> Json 01:27:53.290 --> 01:27:53.300 align:start position:0% as Json or maybe an extension to Json 01:27:53.300 --> 01:27:55.910 align:start position:0% as Json or maybe an extension to Json you<01:27:54.300> could<01:27:54.360> use<01:27:54.540> that<01:27:54.840> but<01:27:55.199> the<01:27:55.380> ID<01:27:55.500> here<01:27:55.739> is 01:27:55.910 --> 01:27:55.920 align:start position:0% you could use that but the ID here is 01:27:55.920 --> 01:27:57.770 align:start position:0% you could use that but the ID here is would<01:27:56.159> be<01:27:56.340> the<01:27:56.460> markdown<01:27:56.760> and<01:27:57.120> if<01:27:57.239> Mirror<01:27:57.659> Has 01:27:57.770 --> 01:27:57.780 align:start position:0% would be the markdown and if Mirror Has 01:27:57.780 --> 01:27:59.270 align:start position:0% would be the markdown and if Mirror Has extra<01:27:57.960> information<01:27:58.199> they<01:27:58.739> could<01:27:58.860> use<01:27:59.040> their 01:27:59.270 --> 01:27:59.280 align:start position:0% extra information they could use their 01:27:59.280 --> 01:28:01.810 align:start position:0% extra information they could use their own<01:27:59.400> fields<01:27:59.940> to<01:28:00.480> refer<01:28:00.780> to<01:28:00.900> that<01:28:01.080> information 01:28:01.810 --> 01:28:01.820 align:start position:0% own fields to refer to that information 01:28:01.820 --> 01:28:04.310 align:start position:0% own fields to refer to that information within<01:28:02.820> the<01:28:02.940> content<01:28:03.300> file<01:28:03.600> or<01:28:04.020> outside 01:28:04.310 --> 01:28:04.320 align:start position:0% within the content file or outside 01:28:04.320 --> 01:28:05.990 align:start position:0% within the content file or outside there's<01:28:04.739> a<01:28:04.920> way<01:28:04.980> you<01:28:05.100> can<01:28:05.219> actually<01:28:05.400> add<01:28:05.639> Json 01:28:05.990 --> 01:28:06.000 align:start position:0% there's a way you can actually add Json 01:28:06.000 --> 01:28:08.149 align:start position:0% there's a way you can actually add Json headers<01:28:06.540> to<01:28:06.719> markdown<01:28:07.020> files<01:28:07.440> so<01:28:07.679> you<01:28:08.100> know 01:28:08.149 --> 01:28:08.159 align:start position:0% headers to markdown files so you know 01:28:08.159 --> 01:28:10.370 align:start position:0% headers to markdown files so you know the<01:28:08.580> file<01:28:08.820> itself<01:28:09.420> is<01:28:09.600> an<01:28:09.780> abstraction<01:28:10.139> is 01:28:10.370 --> 01:28:10.380 align:start position:0% the file itself is an abstraction is 01:28:10.380 --> 01:28:12.890 align:start position:0% the file itself is an abstraction is really<01:28:10.620> powerful<01:28:11.040> in<01:28:11.280> this<01:28:11.400> case 01:28:12.890 --> 01:28:12.900 align:start position:0% really powerful in this case 01:28:12.900 --> 01:28:14.510 align:start position:0% really powerful in this case but<01:28:13.320> if<01:28:13.440> you<01:28:13.560> were<01:28:13.679> to<01:28:13.739> rewrite<01:28:14.040> this<01:28:14.159> using 01:28:14.510 --> 01:28:14.520 align:start position:0% but if you were to rewrite this using 01:28:14.520 --> 01:28:17.149 align:start position:0% but if you were to rewrite this using content<01:28:14.820> you<01:28:15.540> could<01:28:15.719> use<01:28:15.840> text<01:28:16.020> markdown<01:28:16.500> and 01:28:17.149 --> 01:28:17.159 align:start position:0% content you could use text markdown and 01:28:17.159 --> 01:28:19.070 align:start position:0% content you could use text markdown and then<01:28:17.219> quixotic<01:28:17.880> could<01:28:18.179> easily<01:28:18.540> parse<01:28:18.900> that 01:28:19.070 --> 01:28:19.080 align:start position:0% then quixotic could easily parse that 01:28:19.080 --> 01:28:21.410 align:start position:0% then quixotic could easily parse that not<01:28:19.320> just<01:28:19.500> for<01:28:19.679> mirror<01:28:20.100> but<01:28:20.520> from<01:28:20.699> Zora<01:28:21.120> tools 01:28:21.410 --> 01:28:21.420 align:start position:0% not just for mirror but from Zora tools 01:28:21.420 --> 01:28:23.750 align:start position:0% not just for mirror but from Zora tools if<01:28:21.540> somebody<01:28:21.719> were<01:28:21.960> to<01:28:22.080> Mint<01:28:22.380> a<01:28:22.560> markdown<01:28:22.920> file 01:28:23.750 --> 01:28:23.760 align:start position:0% if somebody were to Mint a markdown file 01:28:23.760 --> 01:28:26.450 align:start position:0% if somebody were to Mint a markdown file and<01:28:24.480> this<01:28:24.960> has<01:28:25.080> happened<01:28:25.260> before<01:28:25.620> when 01:28:26.450 --> 01:28:26.460 align:start position:0% and this has happened before when 01:28:26.460 --> 01:28:28.970 align:start position:0% and this has happened before when Matthew<01:28:26.940> ball<01:28:27.300> wanted<01:28:27.840> to<01:28:28.080> Mint<01:28:28.320> his<01:28:28.800> original 01:28:28.970 --> 01:28:28.980 align:start position:0% Matthew ball wanted to Mint his original 01:28:28.980 --> 01:28:31.370 align:start position:0% Matthew ball wanted to Mint his original metaverse<01:28:29.699> essay<01:28:30.000> on<01:28:30.239> Zora 01:28:31.370 --> 01:28:31.380 align:start position:0% metaverse essay on Zora 01:28:31.380 --> 01:28:33.590 align:start position:0% metaverse essay on Zora but<01:28:31.860> we<01:28:32.219> wanted<01:28:32.400> compatibility<01:28:33.120> with<01:28:33.420> more 01:28:33.590 --> 01:28:33.600 align:start position:0% but we wanted compatibility with more 01:28:33.600 --> 01:28:36.290 align:start position:0% but we wanted compatibility with more marketplaces<01:28:34.380> and<01:28:34.860> we<01:28:35.159> wanted<01:28:35.340> parts<01:28:36.000> of<01:28:36.179> the 01:28:36.290 --> 01:28:36.300 align:start position:0% marketplaces and we wanted parts of the 01:28:36.300 --> 01:28:38.410 align:start position:0% marketplaces and we wanted parts of the metadata<01:28:36.719> to<01:28:36.840> be<01:28:36.960> fully<01:28:37.260> on<01:28:37.440> chain 01:28:38.410 --> 01:28:38.420 align:start position:0% metadata to be fully on chain 01:28:38.420 --> 01:28:40.910 align:start position:0% metadata to be fully on chain the<01:28:39.420> solidity<01:28:39.840> contract<01:28:40.260> renders<01:28:40.679> the 01:28:40.910 --> 01:28:40.920 align:start position:0% the solidity contract renders the 01:28:40.920 --> 01:28:44.270 align:start position:0% the solidity contract renders the metadata<01:28:41.400> Json<01:28:41.699> on<01:28:42.600> chain<01:28:42.840> but<01:28:43.560> it<01:28:43.739> links<01:28:44.100> to 01:28:44.270 --> 01:28:44.280 align:start position:0% metadata Json on chain but it links to 01:28:44.280 --> 01:28:47.689 align:start position:0% metadata Json on chain but it links to an<01:28:44.520> HTML<01:28:45.120> file<01:28:45.540> of<01:28:46.440> the<01:28:46.620> markdown<01:28:47.040> content 01:28:47.689 --> 01:28:47.699 align:start position:0% an HTML file of the markdown content 01:28:47.699 --> 01:28:50.149 align:start position:0% an HTML file of the markdown content because<01:28:48.300> that's<01:28:48.780> what<01:28:49.199> animation<01:28:49.679> URL 01:28:50.149 --> 01:28:50.159 align:start position:0% because that's what animation URL 01:28:50.159 --> 01:28:52.550 align:start position:0% because that's what animation URL supports<01:28:50.520> so<01:28:50.760> we're<01:28:50.880> having<01:28:51.060> to<01:28:51.420> change<01:28:51.780> the 01:28:52.550 --> 01:28:52.560 align:start position:0% supports so we're having to change the 01:28:52.560 --> 01:28:54.770 align:start position:0% supports so we're having to change the media<01:28:52.860> type<01:28:53.159> into<01:28:53.760> something<01:28:54.179> that<01:28:54.540> fits 01:28:54.770 --> 01:28:54.780 align:start position:0% media type into something that fits 01:28:54.780 --> 01:28:56.209 align:start position:0% media type into something that fits within<01:28:55.020> an<01:28:55.199> nft 01:28:56.209 --> 01:28:56.219 align:start position:0% within an nft 01:28:56.219 --> 01:28:59.990 align:start position:0% within an nft an<01:28:56.699> easy<01:28:56.880> way<01:28:57.060> to<01:28:57.239> avoid<01:28:57.540> that<01:28:57.840> and<01:28:58.800> also<01:28:59.520> if 01:28:59.990 --> 01:29:00.000 align:start position:0% an easy way to avoid that and also if 01:29:00.000 --> 01:29:02.629 align:start position:0% an easy way to avoid that and also if you<01:29:00.120> look<01:29:00.239> at<01:29:00.360> an<01:29:00.600> open<01:29:00.780> C<01:29:01.219> it<01:29:02.219> doesn't 01:29:02.629 --> 01:29:02.639 align:start position:0% you look at an open C it doesn't 01:29:02.639 --> 01:29:05.209 align:start position:0% you look at an open C it doesn't properly<01:29:03.239> parse<01:29:03.780> an<01:29:03.960> animation<01:29:04.320> URI<01:29:04.860> with<01:29:05.100> an 01:29:05.209 --> 01:29:05.219 align:start position:0% properly parse an animation URI with an 01:29:05.219 --> 01:29:08.090 align:start position:0% properly parse an animation URI with an ipfs<01:29:05.820> colon<01:29:06.239> slash<01:29:06.480> right<01:29:07.020> now<01:29:07.199> but<01:29:07.860> you<01:29:08.040> can 01:29:08.090 --> 01:29:08.100 align:start position:0% ipfs colon slash right now but you can 01:29:08.100 --> 01:29:09.649 align:start position:0% ipfs colon slash right now but you can see<01:29:08.219> the<01:29:08.400> metadata<01:29:08.820> is<01:29:08.940> getting<01:29:09.120> loaded<01:29:09.540> in 01:29:09.649 --> 01:29:09.659 align:start position:0% see the metadata is getting loaded in 01:29:09.659 --> 01:29:12.050 align:start position:0% see the metadata is getting loaded in but<01:29:10.260> the<01:29:10.440> essay<01:29:10.739> experience<01:29:11.219> being<01:29:11.520> a<01:29:11.760> tiny 01:29:12.050 --> 01:29:12.060 align:start position:0% but the essay experience being a tiny 01:29:12.060 --> 01:29:13.910 align:start position:0% but the essay experience being a tiny box<01:29:12.239> is<01:29:12.719> really<01:29:12.900> frustrating<01:29:13.320> and<01:29:13.620> links 01:29:13.910 --> 01:29:13.920 align:start position:0% box is really frustrating and links 01:29:13.920 --> 01:29:15.950 align:start position:0% box is really frustrating and links don't<01:29:14.100> work<01:29:14.280> for<01:29:14.520> security<01:29:14.699> reasons<01:29:15.300> here 01:29:15.950 --> 01:29:15.960 align:start position:0% don't work for security reasons here 01:29:15.960 --> 01:29:17.629 align:start position:0% don't work for security reasons here it's<01:29:16.139> slightly<01:29:16.440> better<01:29:16.620> but<01:29:16.920> also<01:29:17.219> links 01:29:17.629 --> 01:29:17.639 align:start position:0% it's slightly better but also links 01:29:17.639 --> 01:29:19.189 align:start position:0% it's slightly better but also links don't<01:29:17.760> work<01:29:17.940> due<01:29:18.179> to<01:29:18.300> security<01:29:18.480> reasons<01:29:18.960> the 01:29:19.189 --> 01:29:19.199 align:start position:0% don't work due to security reasons the 01:29:19.199 --> 01:29:20.750 align:start position:0% don't work due to security reasons the sandboxing<01:29:19.739> on<01:29:19.860> an<01:29:19.980> iframe<01:29:20.460> is<01:29:20.580> actually 01:29:20.750 --> 01:29:20.760 align:start position:0% sandboxing on an iframe is actually 01:29:20.760 --> 01:29:22.850 align:start position:0% sandboxing on an iframe is actually pretty<01:29:21.540> difficult<01:29:21.840> to<01:29:22.139> work<01:29:22.260> with<01:29:22.380> If<01:29:22.679> This 01:29:22.850 --> 01:29:22.860 align:start position:0% pretty difficult to work with If This 01:29:22.860 --> 01:29:24.290 align:start position:0% pretty difficult to work with If This Were<01:29:22.980> A<01:29:23.159> markdown<01:29:23.460> file<01:29:23.699> you<01:29:23.940> could<01:29:24.060> just<01:29:24.179> run 01:29:24.290 --> 01:29:24.300 align:start position:0% Were A markdown file you could just run 01:29:24.300 --> 01:29:26.629 align:start position:0% Were A markdown file you could just run it<01:29:24.480> through<01:29:24.780> whatever<01:29:25.320> markdown<01:29:25.860> renderer<01:29:26.340> or 01:29:26.629 --> 01:29:26.639 align:start position:0% it through whatever markdown renderer or 01:29:26.639 --> 01:29:28.430 align:start position:0% it through whatever markdown renderer or even<01:29:26.760> provide<01:29:27.480> a<01:29:27.600> link<01:29:27.719> and<01:29:27.960> just<01:29:28.139> show<01:29:28.260> the 01:29:28.430 --> 01:29:28.440 align:start position:0% even provide a link and just show the 01:29:28.440 --> 01:29:32.810 align:start position:0% even provide a link and just show the preview<01:29:28.739> image<01:29:29.159> associated<01:29:30.000> with<01:29:30.300> the<01:29:30.420> nft 01:29:32.810 --> 01:29:32.820 align:start position:0% 01:29:32.820 --> 01:29:35.750 align:start position:0% a<01:29:33.360> final<01:29:33.540> example<01:29:34.080> of<01:29:34.260> this<01:29:34.500> is<01:29:35.159> the<01:29:35.580> dead 01:29:35.750 --> 01:29:35.760 align:start position:0% a final example of this is the dead 01:29:35.760 --> 01:29:37.729 align:start position:0% a final example of this is the dead ringers 01:29:37.729 --> 01:29:37.739 align:start position:0% ringers 01:29:37.739 --> 01:29:40.490 align:start position:0% ringers um<01:29:37.800> it<01:29:38.520> is<01:29:38.760> a<01:29:39.120> part<01:29:39.239> of<01:29:39.420> the<01:29:39.600> Ringer's<01:29:40.080> art 01:29:40.490 --> 01:29:40.500 align:start position:0% um it is a part of the Ringer's art 01:29:40.500 --> 01:29:43.250 align:start position:0% um it is a part of the Ringer's art blocks<01:29:40.980> collection<01:29:41.520> and<01:29:42.060> it<01:29:42.300> is<01:29:42.480> a<01:29:42.780> follow-up 01:29:43.250 --> 01:29:43.260 align:start position:0% blocks collection and it is a follow-up 01:29:43.260 --> 01:29:46.610 align:start position:0% blocks collection and it is a follow-up limited<01:29:44.219> time<01:29:44.340> Edition<01:29:44.719> where<01:29:45.719> funds<01:29:46.320> went<01:29:46.440> to 01:29:46.610 --> 01:29:46.620 align:start position:0% limited time Edition where funds went to 01:29:46.620 --> 01:29:49.750 align:start position:0% limited time Edition where funds went to charity<01:29:46.920> and<01:29:47.460> it<01:29:47.580> was<01:29:47.699> a<01:29:48.000> very<01:29:48.239> large<01:29:48.900> SVG 01:29:49.750 --> 01:29:49.760 align:start position:0% charity and it was a very large SVG 01:29:49.760 --> 01:29:52.550 align:start position:0% charity and it was a very large SVG megabytes<01:29:50.760> and<01:29:50.940> megabytes<01:29:51.360> SVG 01:29:52.550 --> 01:29:52.560 align:start position:0% megabytes and megabytes SVG 01:29:52.560 --> 01:29:54.649 align:start position:0% megabytes and megabytes SVG and<01:29:53.159> I<01:29:53.460> believe<01:29:53.580> manifold<01:29:54.120> helped<01:29:54.420> with<01:29:54.480> the 01:29:54.649 --> 01:29:54.659 align:start position:0% and I believe manifold helped with the 01:29:54.659 --> 01:29:58.010 align:start position:0% and I believe manifold helped with the mint<01:29:55.040> and<01:29:56.040> the<01:29:56.880> original 01:29:58.010 --> 01:29:58.020 align:start position:0% mint and the original 01:29:58.020 --> 01:30:00.890 align:start position:0% mint and the original file<01:29:58.620> for<01:29:58.920> image<01:29:59.280> was<01:29:59.639> an<01:29:59.820> SVG 01:30:00.890 --> 01:30:00.900 align:start position:0% file for image was an SVG 01:30:00.900 --> 01:30:02.950 align:start position:0% file for image was an SVG but<01:30:01.320> that<01:30:01.560> SVG 01:30:02.950 --> 01:30:02.960 align:start position:0% but that SVG 01:30:02.960 --> 01:30:06.649 align:start position:0% but that SVG broke<01:30:03.960> wallets<01:30:04.500> and<01:30:05.340> people<01:30:05.580> were<01:30:05.820> not<01:30:06.360> happy 01:30:06.649 --> 01:30:06.659 align:start position:0% broke wallets and people were not happy 01:30:06.659 --> 01:30:09.830 align:start position:0% broke wallets and people were not happy because<01:30:07.380> an<01:30:07.620> SVG<01:30:08.159> is<01:30:08.460> text<01:30:08.699> and<01:30:09.420> for<01:30:09.600> you<01:30:09.719> to 01:30:09.830 --> 01:30:09.840 align:start position:0% because an SVG is text and for you to 01:30:09.840 --> 01:30:11.209 align:start position:0% because an SVG is text and for you to encode<01:30:10.139> text<01:30:10.380> you<01:30:10.620> actually<01:30:10.739> have<01:30:10.920> to<01:30:11.040> turn 01:30:11.209 --> 01:30:11.219 align:start position:0% encode text you actually have to turn 01:30:11.219 --> 01:30:14.570 align:start position:0% encode text you actually have to turn the<01:30:11.400> SVG<01:30:11.880> into<01:30:12.840> some<01:30:13.260> sort<01:30:13.500> of<01:30:13.560> bitmap<01:30:14.219> format 01:30:14.570 --> 01:30:14.580 align:start position:0% the SVG into some sort of bitmap format 01:30:14.580 --> 01:30:16.550 align:start position:0% the SVG into some sort of bitmap format and<01:30:14.820> then<01:30:14.940> convert<01:30:15.300> it<01:30:15.420> again<01:30:15.600> and<01:30:15.900> resize<01:30:16.320> it 01:30:16.550 --> 01:30:16.560 align:start position:0% and then convert it again and resize it 01:30:16.560 --> 01:30:18.470 align:start position:0% and then convert it again and resize it so<01:30:17.040> it's<01:30:17.159> really<01:30:17.400> difficult<01:30:17.699> to<01:30:18.000> resize<01:30:18.300> in 01:30:18.470 --> 01:30:18.480 align:start position:0% so it's really difficult to resize in 01:30:18.480 --> 01:30:20.209 align:start position:0% so it's really difficult to resize in SVG<01:30:18.900> and<01:30:19.080> most<01:30:19.199> marketplaces<01:30:19.800> pass<01:30:20.040> through 01:30:20.209 --> 01:30:20.219 align:start position:0% SVG and most marketplaces pass through 01:30:20.219 --> 01:30:23.030 align:start position:0% SVG and most marketplaces pass through the<01:30:20.400> SVG<01:30:20.820> but<01:30:21.420> this<01:30:21.719> particular<01:30:22.080> SVG<01:30:22.620> was<01:30:22.860> so 01:30:23.030 --> 01:30:23.040 align:start position:0% the SVG but this particular SVG was so 01:30:23.040 --> 01:30:25.189 align:start position:0% the SVG but this particular SVG was so large<01:30:23.219> it<01:30:23.400> started<01:30:23.760> breaking<01:30:24.120> stuff<01:30:24.300> so<01:30:25.080> what 01:30:25.189 --> 01:30:25.199 align:start position:0% large it started breaking stuff so what 01:30:25.199 --> 01:30:26.930 align:start position:0% large it started breaking stuff so what they<01:30:25.380> had<01:30:25.500> to<01:30:25.679> do<01:30:25.860> is<01:30:26.100> they<01:30:26.280> actually<01:30:26.460> had<01:30:26.760> to 01:30:26.930 --> 01:30:26.940 align:start position:0% they had to do is they actually had to 01:30:26.940 --> 01:30:31.129 align:start position:0% they had to do is they actually had to update<01:30:27.360> that<01:30:27.860> and<01:30:28.860> change<01:30:29.520> the<01:30:30.060> image<01:30:30.480> to<01:30:30.900> a 01:30:31.129 --> 01:30:31.139 align:start position:0% update that and change the image to a 01:30:31.139 --> 01:30:33.770 align:start position:0% update that and change the image to a PNG<01:30:31.440> that<01:30:31.920> did<01:30:32.100> render<01:30:32.340> well<01:30:32.639> but<01:30:33.000> it<01:30:33.120> was<01:30:33.239> a<01:30:33.480> 12 01:30:33.770 --> 01:30:33.780 align:start position:0% PNG that did render well but it was a 12 01:30:33.780 --> 01:30:38.390 align:start position:0% PNG that did render well but it was a 12 21<01:30:34.860> 000<01:30:34.980> by<01:30:35.280> 43<01:30:36.239> 000<01:30:36.360> pixel<01:30:37.080> PNG<01:30:37.440> which<01:30:38.159> also 01:30:38.390 --> 01:30:38.400 align:start position:0% 21 000 by 43 000 pixel PNG which also 01:30:38.400 --> 01:30:40.669 align:start position:0% 21 000 by 43 000 pixel PNG which also caused<01:30:38.699> some<01:30:38.760> problems<01:30:39.679> because 01:30:40.669 --> 01:30:40.679 align:start position:0% caused some problems because 01:30:40.679 --> 01:30:42.830 align:start position:0% caused some problems because marketplaces<01:30:41.460> taking<01:30:41.699> the<01:30:41.940> PNG<01:30:42.300> or<01:30:42.659> whatever 01:30:42.830 --> 01:30:42.840 align:start position:0% marketplaces taking the PNG or whatever 01:30:42.840 --> 01:30:44.750 align:start position:0% marketplaces taking the PNG or whatever image<01:30:43.260> file<01:30:43.440> resize<01:30:43.920> it<01:30:44.100> to<01:30:44.219> reasonable<01:30:44.580> size 01:30:44.750 --> 01:30:44.760 align:start position:0% image file resize it to reasonable size 01:30:44.760 --> 01:30:46.910 align:start position:0% image file resize it to reasonable size and<01:30:45.000> display<01:30:45.239> it<01:30:45.540> so<01:30:46.139> what<01:30:46.260> we<01:30:46.380> could<01:30:46.560> do<01:30:46.739> now 01:30:46.910 --> 01:30:46.920 align:start position:0% and display it so what we could do now 01:30:46.920 --> 01:30:48.950 align:start position:0% and display it so what we could do now with<01:30:47.280> this<01:30:47.639> particular<01:30:48.060> proposed<01:30:48.659> standard 01:30:48.950 --> 01:30:48.960 align:start position:0% with this particular proposed standard 01:30:48.960 --> 01:30:51.530 align:start position:0% with this particular proposed standard would<01:30:49.320> be<01:30:49.500> to<01:30:49.980> include<01:30:50.520> the<01:30:50.760> optimized<01:30:51.300> image 01:30:51.530 --> 01:30:51.540 align:start position:0% would be to include the optimized image 01:30:51.540 --> 01:30:54.110 align:start position:0% would be to include the optimized image that<01:30:51.780> renders<01:30:52.139> well<01:30:52.440> within<01:30:53.340> marketplaces 01:30:54.110 --> 01:30:54.120 align:start position:0% that renders well within marketplaces 01:30:54.120 --> 01:30:56.750 align:start position:0% that renders well within marketplaces and<01:30:54.780> then<01:30:54.900> have<01:30:55.139> the<01:30:55.380> canonical<01:30:55.800> content<01:30:56.400> be 01:30:56.750 --> 01:30:56.760 align:start position:0% and then have the canonical content be 01:30:56.760 --> 01:30:59.090 align:start position:0% and then have the canonical content be the<01:30:57.000> super<01:30:57.239> high<01:30:57.540> resolution<01:30:58.020> file<01:30:58.860> the 01:30:59.090 --> 01:30:59.100 align:start position:0% the super high resolution file the 01:30:59.100 --> 01:31:01.189 align:start position:0% the super high resolution file the artist<01:30:59.219> intended<01:30:59.880> so<01:31:00.120> if<01:31:00.239> you<01:31:00.360> own<01:31:00.480> that<01:31:00.840> to 01:31:01.189 --> 01:31:01.199 align:start position:0% artist intended so if you own that to 01:31:01.199 --> 01:31:03.110 align:start position:0% artist intended so if you own that to your<01:31:01.380> wish<01:31:01.560> to<01:31:01.739> display<01:31:01.920> it<01:31:02.219> you<01:31:02.820> can<01:31:02.940> then 01:31:03.110 --> 01:31:03.120 align:start position:0% your wish to display it you can then 01:31:03.120 --> 01:31:04.790 align:start position:0% your wish to display it you can then download<01:31:03.360> that<01:31:03.719> original<01:31:03.900> file<01:31:04.380> and<01:31:04.620> work 01:31:04.790 --> 01:31:04.800 align:start position:0% download that original file and work 01:31:04.800 --> 01:31:07.189 align:start position:0% download that original file and work with<01:31:04.980> it<01:31:05.100> as<01:31:05.340> you<01:31:05.520> will 01:31:07.189 --> 01:31:07.199 align:start position:0% with it as you will 01:31:07.199 --> 01:31:09.709 align:start position:0% with it as you will and<01:31:07.739> if<01:31:07.980> you<01:31:08.100> were<01:31:08.219> to<01:31:08.400> take<01:31:08.580> the<01:31:08.820> content<01:31:09.179> type 01:31:09.709 --> 01:31:09.719 align:start position:0% and if you were to take the content type 01:31:09.719 --> 01:31:13.669 align:start position:0% and if you were to take the content type you<01:31:10.080> could<01:31:10.139> then<01:31:10.380> encode<01:31:11.000> the<01:31:12.000> image<01:31:12.480> SVG<01:31:13.020> XML 01:31:13.669 --> 01:31:13.679 align:start position:0% you could then encode the image SVG XML 01:31:13.679 --> 01:31:16.070 align:start position:0% you could then encode the image SVG XML and<01:31:14.040> then<01:31:14.159> a<01:31:14.280> URI<01:31:14.760> and<01:31:15.540> then<01:31:15.659> optionally 01:31:16.070 --> 01:31:16.080 align:start position:0% and then a URI and then optionally 01:31:16.080 --> 01:31:19.430 align:start position:0% and then a URI and then optionally include<01:31:16.500> a<01:31:16.679> sha256<01:31:17.580> if<01:31:17.880> you're<01:31:18.060> using<01:31:18.480> airweed 01:31:19.430 --> 01:31:19.440 align:start position:0% include a sha256 if you're using airweed 01:31:19.440 --> 01:31:20.810 align:start position:0% include a sha256 if you're using airweed that's<01:31:19.620> actually<01:31:19.800> a<01:31:19.980> really<01:31:20.100> nice<01:31:20.460> way<01:31:20.639> of 01:31:20.810 --> 01:31:20.820 align:start position:0% that's actually a really nice way of 01:31:20.820 --> 01:31:22.430 align:start position:0% that's actually a really nice way of verifying<01:31:21.300> that<01:31:21.420> the<01:31:21.659> file<01:31:21.840> is<01:31:22.020> what<01:31:22.199> it<01:31:22.320> is 01:31:22.430 --> 01:31:22.440 align:start position:0% verifying that the file is what it is 01:31:22.440 --> 01:31:24.470 align:start position:0% verifying that the file is what it is because<01:31:23.040> airweave<01:31:23.639> doesn't<01:31:23.820> use<01:31:24.060> content 01:31:24.470 --> 01:31:24.480 align:start position:0% because airweave doesn't use content 01:31:24.480 --> 01:31:27.410 align:start position:0% because airweave doesn't use content addressable<01:31:25.080> hash<01:31:25.739> so<01:31:26.520> the 01:31:27.410 --> 01:31:27.420 align:start position:0% addressable hash so the 01:31:27.420 --> 01:31:30.229 align:start position:0% addressable hash so the the<01:31:28.260> link<01:31:28.500> to<01:31:28.800> ipfs<01:31:29.400> for<01:31:29.639> every<01:31:29.820> file<01:31:30.120> is 01:31:30.229 --> 01:31:30.239 align:start position:0% the link to ipfs for every file is 01:31:30.239 --> 01:31:32.330 align:start position:0% the link to ipfs for every file is unique<01:31:30.600> per<01:31:30.780> file<01:31:31.139> but<01:31:31.560> for<01:31:31.739> our<01:31:31.920> weave<01:31:32.219> it's 01:31:32.330 --> 01:31:32.340 align:start position:0% unique per file but for our weave it's 01:31:32.340 --> 01:31:35.149 align:start position:0% unique per file but for our weave it's different<01:31:32.520> so<01:31:33.000> the<01:31:33.480> idea<01:31:33.780> here<01:31:33.960> is<01:31:34.139> the<01:31:34.320> sha256 01:31:35.149 --> 01:31:35.159 align:start position:0% different so the idea here is the sha256 01:31:35.159 --> 01:31:37.310 align:start position:0% different so the idea here is the sha256 is<01:31:35.340> a<01:31:35.520> really<01:31:35.639> standard<01:31:36.000> way<01:31:36.239> for<01:31:36.900> a<01:31:37.020> very<01:31:37.139> long 01:31:37.310 --> 01:31:37.320 align:start position:0% is a really standard way for a very long 01:31:37.320 --> 01:31:39.410 align:start position:0% is a really standard way for a very long time<01:31:37.500> of<01:31:37.800> verifying<01:31:38.340> that<01:31:38.520> a<01:31:38.699> file<01:31:38.880> matches<01:31:39.239> a 01:31:39.410 --> 01:31:39.420 align:start position:0% time of verifying that a file matches a 01:31:39.420 --> 01:31:42.169 align:start position:0% time of verifying that a file matches a file<01:31:39.659> and<01:31:40.199> can<01:31:40.380> be<01:31:40.560> included<01:31:40.920> in<01:31:41.040> this<01:31:41.219> so 01:31:42.169 --> 01:31:42.179 align:start position:0% file and can be included in this so 01:31:42.179 --> 01:31:47.090 align:start position:0% file and can be included in this so overall 01:31:47.090 --> 01:31:47.100 align:start position:0% 01:31:47.100 --> 01:31:50.030 align:start position:0% the<01:31:47.880> idea<01:31:48.179> of<01:31:48.420> this<01:31:48.600> proposal<01:31:49.020> is<01:31:49.260> to<01:31:49.440> add<01:31:49.620> in<01:31:49.739> a 01:31:50.030 --> 01:31:50.040 align:start position:0% the idea of this proposal is to add in a 01:31:50.040 --> 01:31:52.790 align:start position:0% the idea of this proposal is to add in a Content<01:31:50.400> field<01:31:50.780> and<01:31:51.780> the<01:31:52.080> idea<01:31:52.320> with<01:31:52.500> content 01:31:52.790 --> 01:31:52.800 align:start position:0% Content field and the idea with content 01:31:52.800 --> 01:31:54.470 align:start position:0% Content field and the idea with content is<01:31:52.920> it's<01:31:53.100> quite<01:31:53.340> simple<01:31:53.580> it<01:31:53.880> doesn't<01:31:54.060> have<01:31:54.239> any 01:31:54.470 --> 01:31:54.480 align:start position:0% is it's quite simple it doesn't have any 01:31:54.480 --> 01:31:56.990 align:start position:0% is it's quite simple it doesn't have any underscores<01:31:55.260> and<01:31:56.040> it's<01:31:56.219> the<01:31:56.400> first<01:31:56.580> time<01:31:56.820> I 01:31:56.990 --> 01:31:57.000 align:start position:0% underscores and it's the first time I 01:31:57.000 --> 01:31:58.910 align:start position:0% underscores and it's the first time I think<01:31:57.120> there's<01:31:57.480> going<01:31:57.719> to<01:31:57.900> be<01:31:58.139> some<01:31:58.380> proposal 01:31:58.910 --> 01:31:58.920 align:start position:0% think there's going to be some proposal 01:31:58.920 --> 01:32:00.169 align:start position:0% think there's going to be some proposal or<01:31:59.040> thought<01:31:59.219> process<01:31:59.580> around<01:31:59.760> creating 01:32:00.169 --> 01:32:00.179 align:start position:0% or thought process around creating 01:32:00.179 --> 01:32:03.110 align:start position:0% or thought process around creating nested<01:32:00.659> structures<01:32:01.500> in<01:32:01.679> the<01:32:01.800> metadata<01:32:02.280> but<01:32:02.880> I 01:32:03.110 --> 01:32:03.120 align:start position:0% nested structures in the metadata but I 01:32:03.120 --> 01:32:04.729 align:start position:0% nested structures in the metadata but I think<01:32:03.179> it's<01:32:03.360> quite<01:32:03.600> useful<01:32:03.960> because<01:32:04.260> content 01:32:04.729 --> 01:32:04.739 align:start position:0% think it's quite useful because content 01:32:04.739 --> 01:32:06.350 align:start position:0% think it's quite useful because content underscore<01:32:05.159> type<01:32:05.460> content<01:32:05.880> it<01:32:06.060> just<01:32:06.239> doesn't 01:32:06.350 --> 01:32:06.360 align:start position:0% underscore type content it just doesn't 01:32:06.360 --> 01:32:08.270 align:start position:0% underscore type content it just doesn't like<01:32:06.719> we<01:32:06.960> already<01:32:07.080> have<01:32:07.260> Json<01:32:07.560> we<01:32:07.860> can<01:32:07.980> Nest 01:32:08.270 --> 01:32:08.280 align:start position:0% like we already have Json we can Nest 01:32:08.280 --> 01:32:09.649 align:start position:0% like we already have Json we can Nest this 01:32:09.649 --> 01:32:09.659 align:start position:0% this 01:32:09.659 --> 01:32:12.950 align:start position:0% this um<01:32:09.780> but<01:32:10.080> type<01:32:10.380> URI<01:32:10.980> shot<01:32:11.400> 256<01:32:12.060> and<01:32:12.480> potentially 01:32:12.950 --> 01:32:12.960 align:start position:0% um but type URI shot 256 and potentially 01:32:12.960 --> 01:32:16.729 align:start position:0% um but type URI shot 256 and potentially potentially<01:32:13.560> body<01:32:14.460> for<01:32:15.420> those<01:32:16.139> that<01:32:16.320> want<01:32:16.560> to 01:32:16.729 --> 01:32:16.739 align:start position:0% potentially body for those that want to 01:32:16.739 --> 01:32:19.070 align:start position:0% potentially body for those that want to directly<01:32:17.340> put<01:32:17.639> plain<01:32:18.000> text<01:32:18.179> in<01:32:18.480> but<01:32:18.840> I<01:32:18.960> feel 01:32:19.070 --> 01:32:19.080 align:start position:0% directly put plain text in but I feel 01:32:19.080 --> 01:32:22.370 align:start position:0% directly put plain text in but I feel like<01:32:19.260> a<01:32:19.860> URI<01:32:20.400> encoding<01:32:20.880> is<01:32:21.060> also<01:32:21.420> usually<01:32:22.139> a 01:32:22.370 --> 01:32:22.380 align:start position:0% like a URI encoding is also usually a 01:32:22.380 --> 01:32:24.169 align:start position:0% like a URI encoding is also usually a fine<01:32:22.500> option<01:32:22.920> I'd<01:32:23.159> love<01:32:23.340> to<01:32:23.520> hear<01:32:23.639> what 01:32:24.169 --> 01:32:24.179 align:start position:0% fine option I'd love to hear what 01:32:24.179 --> 01:32:26.870 align:start position:0% fine option I'd love to hear what different<01:32:24.719> creators<01:32:25.320> of<01:32:25.620> Standards<01:32:26.159> or<01:32:26.460> media 01:32:26.870 --> 01:32:26.880 align:start position:0% different creators of Standards or media 01:32:26.880 --> 01:32:28.189 align:start position:0% different creators of Standards or media have 01:32:28.189 --> 01:32:28.199 align:start position:0% have 01:32:28.199 --> 01:32:30.590 align:start position:0% have another<01:32:28.800> thought<01:32:29.159> was<01:32:29.460> you<01:32:29.880> could<01:32:30.000> have<01:32:30.360> some 01:32:30.590 --> 01:32:30.600 align:start position:0% another thought was you could have some 01:32:30.600 --> 01:32:32.689 align:start position:0% another thought was you could have some sort<01:32:30.780> of<01:32:30.900> attachments<01:32:31.679> Associated<01:32:32.159> say<01:32:32.460> you 01:32:32.689 --> 01:32:32.699 align:start position:0% sort of attachments Associated say you 01:32:32.699 --> 01:32:34.189 align:start position:0% sort of attachments Associated say you have<01:32:32.820> an<01:32:32.940> image<01:32:33.300> that<01:32:33.480> a<01:32:33.780> product<01:32:33.960> you're 01:32:34.189 --> 01:32:34.199 align:start position:0% have an image that a product you're 01:32:34.199 --> 01:32:36.410 align:start position:0% have an image that a product you're selling<01:32:34.560> as<01:32:34.679> an<01:32:34.800> nft<01:32:35.100> and<01:32:35.940> you<01:32:36.120> have<01:32:36.239> a 01:32:36.410 --> 01:32:36.420 align:start position:0% selling as an nft and you have a 01:32:36.420 --> 01:32:38.930 align:start position:0% selling as an nft and you have a slideshow<01:32:36.900> I<01:32:37.560> recently<01:32:37.980> worked<01:32:38.699> with<01:32:38.760> the 01:32:38.930 --> 01:32:38.940 align:start position:0% slideshow I recently worked with the 01:32:38.940 --> 01:32:40.729 align:start position:0% slideshow I recently worked with the team<01:32:39.060> to<01:32:39.239> show<01:32:39.480> a<01:32:39.659> product<01:32:39.840> and<01:32:40.199> the<01:32:40.380> slideshow 01:32:40.729 --> 01:32:40.739 align:start position:0% team to show a product and the slideshow 01:32:40.739 --> 01:32:42.229 align:start position:0% team to show a product and the slideshow had<01:32:40.860> five<01:32:41.040> images<01:32:41.280> you<01:32:41.639> could<01:32:41.760> theoretically 01:32:42.229 --> 01:32:42.239 align:start position:0% had five images you could theoretically 01:32:42.239 --> 01:32:44.930 align:start position:0% had five images you could theoretically include<01:32:42.540> those<01:32:42.659> as<01:32:42.840> attachments<01:32:43.440> in<01:32:43.739> your 01:32:44.930 --> 01:32:44.940 align:start position:0% include those as attachments in your 01:32:44.940 --> 01:32:46.550 align:start position:0% include those as attachments in your um<01:32:45.000> and<01:32:45.360> then<01:32:45.480> that<01:32:45.600> would<01:32:45.780> be<01:32:45.900> rendered<01:32:46.320> as 01:32:46.550 --> 01:32:46.560 align:start position:0% um and then that would be rendered as 01:32:46.560 --> 01:32:49.070 align:start position:0% um and then that would be rendered as like<01:32:46.800> a<01:32:46.920> generic<01:32:47.280> attachment<01:32:47.639> on<01:32:47.940> media<01:32:48.360> I 01:32:49.070 --> 01:32:49.080 align:start position:0% like a generic attachment on media I 01:32:49.080 --> 01:32:50.450 align:start position:0% like a generic attachment on media I think<01:32:49.320> that's<01:32:49.440> a<01:32:49.620> little<01:32:49.739> out<01:32:50.040> of<01:32:50.159> the<01:32:50.280> scope 01:32:50.450 --> 01:32:50.460 align:start position:0% think that's a little out of the scope 01:32:50.460 --> 01:32:52.850 align:start position:0% think that's a little out of the scope for<01:32:50.760> this<01:32:51.000> project<01:32:51.199> though<01:32:52.199> and<01:32:52.440> I<01:32:52.620> would<01:32:52.679> like 01:32:52.850 --> 01:32:52.860 align:start position:0% for this project though and I would like 01:32:52.860 --> 01:32:55.850 align:start position:0% for this project though and I would like to<01:32:53.159> kind<01:32:53.400> of<01:32:53.520> focus<01:32:53.880> on 01:32:55.850 --> 01:32:55.860 align:start position:0% to kind of focus on 01:32:55.860 --> 01:32:56.510 align:start position:0% to kind of focus on um 01:32:56.510 --> 01:32:56.520 align:start position:0% um 01:32:56.520 --> 01:32:58.610 align:start position:0% um I<01:32:57.060> would<01:32:57.179> like<01:32:57.300> to<01:32:57.420> focus<01:32:57.719> on<01:32:57.900> this<01:32:58.080> idea<01:32:58.320> of<01:32:58.500> a 01:32:58.610 --> 01:32:58.620 align:start position:0% I would like to focus on this idea of a 01:32:58.620 --> 01:33:01.189 align:start position:0% I would like to focus on this idea of a single<01:32:58.860> canonical<01:32:59.280> file<01:32:59.780> instead<01:33:00.780> of<01:33:00.900> a<01:33:01.080> set 01:33:01.189 --> 01:33:01.199 align:start position:0% single canonical file instead of a set 01:33:01.199 --> 01:33:03.110 align:start position:0% single canonical file instead of a set of<01:33:01.380> files<01:33:01.679> because<01:33:01.860> it<01:33:02.219> makes<01:33:02.400> sense<01:33:02.699> to<01:33:02.940> have 01:33:03.110 --> 01:33:03.120 align:start position:0% of files because it makes sense to have 01:33:03.120 --> 01:33:06.649 align:start position:0% of files because it makes sense to have a<01:33:03.300> single<01:33:03.600> file<01:33:03.920> and<01:33:04.920> a<01:33:05.219> single<01:33:05.460> nft<01:33:05.760> ID<01:33:06.120> relate 01:33:06.649 --> 01:33:06.659 align:start position:0% a single file and a single nft ID relate 01:33:06.659 --> 01:33:10.189 align:start position:0% a single file and a single nft ID relate to<01:33:06.840> each<01:33:07.020> other<01:33:07.460> and<01:33:08.460> to<01:33:09.060> not<01:33:09.300> really<01:33:09.540> focus<01:33:09.900> on 01:33:10.189 --> 01:33:10.199 align:start position:0% to each other and to not really focus on 01:33:10.199 --> 01:33:12.290 align:start position:0% to each other and to not really focus on banners<01:33:10.739> and<01:33:10.980> colors<01:33:11.340> and<01:33:11.580> multiple<01:33:11.940> sizes 01:33:12.290 --> 01:33:12.300 align:start position:0% banners and colors and multiple sizes 01:33:12.300 --> 01:33:14.570 align:start position:0% banners and colors and multiple sizes kind<01:33:12.600> of<01:33:12.659> on<01:33:12.900> the<01:33:13.139> side<01:33:13.500> of<01:33:13.739> open<01:33:13.920> graph<01:33:14.340> where 01:33:14.570 --> 01:33:14.580 align:start position:0% kind of on the side of open graph where 01:33:14.580 --> 01:33:16.490 align:start position:0% kind of on the side of open graph where you<01:33:14.760> have<01:33:14.940> this<01:33:15.120> media<01:33:15.480> how<01:33:15.780> do<01:33:15.900> you<01:33:16.020> render<01:33:16.260> it 01:33:16.490 --> 01:33:16.500 align:start position:0% you have this media how do you render it 01:33:16.500 --> 01:33:18.470 align:start position:0% you have this media how do you render it well<01:33:16.739> on<01:33:17.460> a<01:33:17.580> Marketplace<01:33:17.940> or<01:33:18.179> in<01:33:18.360> another 01:33:18.470 --> 01:33:18.480 align:start position:0% well on a Marketplace or in another 01:33:18.480 --> 01:33:20.750 align:start position:0% well on a Marketplace or in another context<01:33:19.020> I<01:33:19.320> think<01:33:19.440> that's<01:33:19.560> out<01:33:19.860> of<01:33:19.980> scope<01:33:20.280> for 01:33:20.750 --> 01:33:20.760 align:start position:0% context I think that's out of scope for 01:33:20.760 --> 01:33:23.090 align:start position:0% context I think that's out of scope for this<01:33:21.480> particular<01:33:21.780> Focus 01:33:23.090 --> 01:33:23.100 align:start position:0% this particular Focus 01:33:23.100 --> 01:33:23.870 align:start position:0% this particular Focus um 01:33:23.870 --> 01:33:23.880 align:start position:0% um 01:33:23.880 --> 01:33:26.629 align:start position:0% um and<01:33:24.780> the<01:33:25.260> meaning<01:33:25.320> of<01:33:25.500> canonicals<01:33:26.159> to<01:33:26.340> have<01:33:26.460> a 01:33:26.629 --> 01:33:26.639 align:start position:0% and the meaning of canonicals to have a 01:33:26.639 --> 01:33:28.669 align:start position:0% and the meaning of canonicals to have a standard<01:33:26.940> or<01:33:27.120> primary<01:33:27.480> authoritative<01:33:28.260> body 01:33:28.669 --> 01:33:28.679 align:start position:0% standard or primary authoritative body 01:33:28.679 --> 01:33:32.209 align:start position:0% standard or primary authoritative body on<01:33:29.040> a<01:33:29.219> subject<01:33:29.520> so<01:33:30.179> the<01:33:30.480> URL<01:33:31.260> is<01:33:31.500> the 01:33:32.209 --> 01:33:32.219 align:start position:0% on a subject so the URL is the 01:33:32.219 --> 01:33:35.090 align:start position:0% on a subject so the URL is the authoritative<01:33:33.000> idea<01:33:33.719> of<01:33:34.020> what<01:33:34.199> that<01:33:34.320> nft<01:33:34.679> is 01:33:35.090 --> 01:33:35.100 align:start position:0% authoritative idea of what that nft is 01:33:35.100 --> 01:33:37.129 align:start position:0% authoritative idea of what that nft is and<01:33:35.580> it's<01:33:35.699> left<01:33:35.880> up<01:33:36.060> to<01:33:36.239> interpretation<01:33:36.780> of 01:33:37.129 --> 01:33:37.139 align:start position:0% and it's left up to interpretation of 01:33:37.139 --> 01:33:39.410 align:start position:0% and it's left up to interpretation of the<01:33:37.320> Creator<01:33:37.679> or<01:33:38.280> the<01:33:38.520> platform<01:33:38.880> to<01:33:39.300> figure 01:33:39.410 --> 01:33:39.420 align:start position:0% the Creator or the platform to figure 01:33:39.420 --> 01:33:42.709 align:start position:0% the Creator or the platform to figure out<01:33:39.540> how<01:33:39.780> to<01:33:39.900> best<01:33:40.080> Express<01:33:40.320> that<01:33:40.679> and<01:33:40.920> use<01:33:41.159> it 01:33:42.709 --> 01:33:42.719 align:start position:0% out how to best Express that and use it 01:33:42.719 --> 01:33:44.990 align:start position:0% out how to best Express that and use it my<01:33:43.199> open<01:33:43.320> questions<01:33:43.739> are<01:33:44.280> should<01:33:44.580> this<01:33:44.699> be<01:33:44.880> an 01:33:44.990 --> 01:33:45.000 align:start position:0% my open questions are should this be an 01:33:45.000 --> 01:33:46.970 align:start position:0% my open questions are should this be an EIP<01:33:45.360> within<01:33:45.900> The<01:33:46.020> ethereum<01:33:46.380> Magicians<01:33:46.860> group 01:33:46.970 --> 01:33:46.980 align:start position:0% EIP within The ethereum Magicians group 01:33:46.980 --> 01:33:48.830 align:start position:0% EIP within The ethereum Magicians group chat<01:33:47.280> that's<01:33:47.460> a<01:33:47.699> pretty<01:33:47.940> widely<01:33:48.480> debated 01:33:48.830 --> 01:33:48.840 align:start position:0% chat that's a pretty widely debated 01:33:48.840 --> 01:33:51.709 align:start position:0% chat that's a pretty widely debated topic<01:33:49.380> of<01:33:49.860> metadata<01:33:50.760> is<01:33:50.940> included<01:33:51.360> in<01:33:51.540> the 01:33:51.709 --> 01:33:51.719 align:start position:0% topic of metadata is included in the 01:33:51.719 --> 01:33:55.010 align:start position:0% topic of metadata is included in the original<01:33:52.219> proposal<01:33:53.219> but<01:33:54.060> it's<01:33:54.480> not<01:33:54.780> really 01:33:55.010 --> 01:33:55.020 align:start position:0% original proposal but it's not really 01:33:55.020 --> 01:33:56.870 align:start position:0% original proposal but it's not really defined<01:33:55.560> beyond<01:33:55.980> that<01:33:56.159> and<01:33:56.340> it's<01:33:56.520> defined 01:33:56.870 --> 01:33:56.880 align:start position:0% defined beyond that and it's defined 01:33:56.880 --> 01:33:58.610 align:start position:0% defined beyond that and it's defined quite<01:33:57.120> Loosely<01:33:57.480> so<01:33:57.780> one<01:33:57.960> thing<01:33:58.080> I<01:33:58.199> like<01:33:58.320> to<01:33:58.440> do 01:33:58.610 --> 01:33:58.620 align:start position:0% quite Loosely so one thing I like to do 01:33:58.620 --> 01:34:00.770 align:start position:0% quite Loosely so one thing I like to do is<01:33:58.739> try<01:33:58.920> to<01:33:59.040> stick<01:33:59.280> to<01:33:59.460> proposals<01:34:00.060> and<01:34:00.659> I'll 01:34:00.770 --> 01:34:00.780 align:start position:0% is try to stick to proposals and I'll 01:34:00.780 --> 01:34:03.229 align:start position:0% is try to stick to proposals and I'll typically<01:34:01.139> use<01:34:01.500> the<01:34:01.920> Key<01:34:02.159> Properties<01:34:02.639> instead 01:34:03.229 --> 01:34:03.239 align:start position:0% typically use the Key Properties instead 01:34:03.239 --> 01:34:03.950 align:start position:0% typically use the Key Properties instead of 01:34:03.950 --> 01:34:03.960 align:start position:0% of 01:34:03.960 --> 01:34:06.050 align:start position:0% of whatever<01:34:04.679> has<01:34:05.219> been<01:34:05.340> defined<01:34:05.639> otherwise 01:34:06.050 --> 01:34:06.060 align:start position:0% whatever has been defined otherwise 01:34:06.060 --> 01:34:08.209 align:start position:0% whatever has been defined otherwise because<01:34:06.360> it's<01:34:06.540> in<01:34:06.719> the<01:34:06.840> 1155<01:34:07.440> spec<01:34:07.679> but<01:34:07.920> I<01:34:08.100> am 01:34:08.209 --> 01:34:08.219 align:start position:0% because it's in the 1155 spec but I am 01:34:08.219 --> 01:34:10.729 align:start position:0% because it's in the 1155 spec but I am mixing<01:34:08.580> the<01:34:08.699> 1155<01:34:09.480> spec<01:34:09.780> with<01:34:09.960> the<01:34:10.139> 720<01:34:10.440> ones 01:34:10.729 --> 01:34:10.739 align:start position:0% mixing the 1155 spec with the 720 ones 01:34:10.739 --> 01:34:12.770 align:start position:0% mixing the 1155 spec with the 720 ones back 01:34:12.770 --> 01:34:12.780 align:start position:0% back 01:34:12.780 --> 01:34:15.709 align:start position:0% back the<01:34:13.260> non<01:34:13.500> yet<01:34:13.800> and<01:34:14.219> then<01:34:14.400> multiple<01:34:14.940> files<01:34:15.360> just 01:34:15.709 --> 01:34:15.719 align:start position:0% the non yet and then multiple files just 01:34:15.719 --> 01:34:17.149 align:start position:0% the non yet and then multiple files just an<01:34:15.840> open<01:34:16.020> question 01:34:17.149 --> 01:34:17.159 align:start position:0% an open question 01:34:17.159 --> 01:34:19.550 align:start position:0% an open question so<01:34:17.639> I'm<01:34:17.940> going<01:34:18.120> to<01:34:18.239> wrap<01:34:18.480> up<01:34:18.659> if<01:34:19.440> you're 01:34:19.550 --> 01:34:19.560 align:start position:0% so I'm going to wrap up if you're 01:34:19.560 --> 01:34:23.030 align:start position:0% so I'm going to wrap up if you're interested<01:34:20.239> in<01:34:21.239> asking<01:34:22.139> questions<01:34:22.440> from<01:34:22.920> the 01:34:23.030 --> 01:34:23.040 align:start position:0% interested in asking questions from the 01:34:23.040 --> 01:34:24.890 align:start position:0% interested in asking questions from the recording<01:34:23.580> or<01:34:24.000> want<01:34:24.179> to<01:34:24.360> continue<01:34:24.600> the 01:34:24.890 --> 01:34:24.900 align:start position:0% recording or want to continue the 01:34:24.900 --> 01:34:26.570 align:start position:0% recording or want to continue the discussion 01:34:26.570 --> 01:34:26.580 align:start position:0% discussion 01:34:26.580 --> 01:34:29.570 align:start position:0% discussion um I<01:34:27.120> have<01:34:27.239> a<01:34:27.360> GitHub<01:34:27.719> of<01:34:27.960> these<01:34:28.320> files<01:34:29.040> and 01:34:29.570 --> 01:34:29.580 align:start position:0% um I have a GitHub of these files and 01:34:29.580 --> 01:34:31.370 align:start position:0% um I have a GitHub of these files and this<01:34:29.880> is<01:34:30.000> my<01:34:30.179> Twitter 01:34:31.370 --> 01:34:31.380 align:start position:0% this is my Twitter 01:34:31.380 --> 01:34:33.470 align:start position:0% this is my Twitter and<01:34:31.860> zoom<01:34:32.100> in<01:34:32.219> a<01:34:32.340> little<01:34:32.400> bit 01:34:33.470 --> 01:34:33.480 align:start position:0% and zoom in a little bit 01:34:33.480 --> 01:34:35.810 align:start position:0% and zoom in a little bit and<01:34:33.900> then<01:34:34.020> the<01:34:34.199> one<01:34:34.380> last<01:34:34.560> thing<01:34:34.800> is<01:34:35.219> there<01:34:35.639> was 01:34:35.810 --> 01:34:35.820 align:start position:0% and then the one last thing is there was 01:34:35.820 --> 01:34:38.930 align:start position:0% and then the one last thing is there was an<01:34:36.000> on-chain<01:34:36.480> version<01:34:36.780> of<01:34:37.080> this<01:34:37.320> EIP<01:34:38.280> content 01:34:38.930 --> 01:34:38.940 align:start position:0% an on-chain version of this EIP content 01:34:38.940 --> 01:34:42.530 align:start position:0% an on-chain version of this EIP content type<01:34:39.179> that<01:34:39.900> used<01:34:40.139> mime<01:34:40.679> content<01:34:41.219> URI<01:34:42.179> and<01:34:42.300> hash 01:34:42.530 --> 01:34:42.540 align:start position:0% type that used mime content URI and hash 01:34:42.540 --> 01:34:44.450 align:start position:0% type that used mime content URI and hash and<01:34:42.960> this<01:34:43.139> is<01:34:43.260> kind<01:34:43.440> of<01:34:43.560> the<01:34:43.739> inspiration<01:34:44.159> for 01:34:44.450 --> 01:34:44.460 align:start position:0% and this is kind of the inspiration for 01:34:44.460 --> 01:34:46.910 align:start position:0% and this is kind of the inspiration for the<01:34:44.639> off<01:34:44.880> chain<01:34:45.179> version<01:34:46.080> of<01:34:46.320> this<01:34:46.440> proposal 01:34:46.910 --> 01:34:46.920 align:start position:0% the off chain version of this proposal 01:34:46.920 --> 01:34:49.669 align:start position:0% the off chain version of this proposal Unchained<01:34:47.820> ideas<01:34:48.120> if<01:34:48.540> you<01:34:48.719> have<01:34:48.900> dynamically 01:34:49.669 --> 01:34:49.679 align:start position:0% Unchained ideas if you have dynamically 01:34:49.679 --> 01:34:51.530 align:start position:0% Unchained ideas if you have dynamically generated<01:34:50.100> SVG<01:34:50.520> it's<01:34:50.760> more<01:34:50.940> composable<01:34:51.300> it's 01:34:51.530 --> 01:34:51.540 align:start position:0% generated SVG it's more composable it's 01:34:51.540 --> 01:34:53.750 align:start position:0% generated SVG it's more composable it's easier<01:34:51.900> just<01:34:52.020> to<01:34:52.199> return<01:34:52.320> a<01:34:52.620> struct<01:34:52.920> but<01:34:53.580> I 01:34:53.750 --> 01:34:53.760 align:start position:0% easier just to return a struct but I 01:34:53.760 --> 01:34:56.270 align:start position:0% easier just to return a struct but I think<01:34:53.880> now<01:34:54.480> kind<01:34:55.080> of<01:34:55.199> working<01:34:55.800> on<01:34:56.040> more 01:34:56.270 --> 01:34:56.280 align:start position:0% think now kind of working on more 01:34:56.280 --> 01:34:58.430 align:start position:0% think now kind of working on more projects<01:34:56.760> and<01:34:56.940> finding<01:34:57.540> more<01:34:57.719> examples<01:34:58.080> the 01:34:58.430 --> 01:34:58.440 align:start position:0% projects and finding more examples the 01:34:58.440 --> 01:35:01.370 align:start position:0% projects and finding more examples the off<01:34:58.620> chain<01:34:59.179> example<01:35:00.179> is<01:35:00.360> more<01:35:00.659> compelling<01:35:01.080> and 01:35:01.370 --> 01:35:01.380 align:start position:0% off chain example is more compelling and 01:35:01.380 --> 01:35:03.770 align:start position:0% off chain example is more compelling and you<01:35:01.560> can<01:35:01.679> still<01:35:01.920> generate<01:35:02.520> a<01:35:02.760> Json<01:35:03.060> blob<01:35:03.480> on 01:35:03.770 --> 01:35:03.780 align:start position:0% you can still generate a Json blob on 01:35:03.780 --> 01:35:07.129 align:start position:0% you can still generate a Json blob on chain<01:35:04.020> including<01:35:04.800> the<01:35:05.460> content<01:35:05.820> field<01:35:06.120> so<01:35:06.840> it 01:35:07.129 --> 01:35:07.139 align:start position:0% chain including the content field so it 01:35:07.139 --> 01:35:08.810 align:start position:0% chain including the content field so it kind<01:35:07.320> of<01:35:07.380> works<01:35:07.739> both<01:35:07.980> ways<01:35:08.340> I<01:35:08.580> just<01:35:08.699> think 01:35:08.810 --> 01:35:08.820 align:start position:0% kind of works both ways I just think 01:35:08.820 --> 01:35:11.450 align:start position:0% kind of works both ways I just think this<01:35:09.060> is<01:35:09.179> a<01:35:09.360> better<01:35:09.540> start<01:35:10.320> to<01:35:10.560> the<01:35:10.800> approach<01:35:11.159> a 01:35:11.450 --> 01:35:11.460 align:start position:0% this is a better start to the approach a 01:35:11.460 --> 01:35:13.490 align:start position:0% this is a better start to the approach a way<01:35:11.820> to<01:35:11.940> approach<01:35:12.239> this<01:35:12.420> project<01:35:12.719> then 01:35:13.490 --> 01:35:13.500 align:start position:0% way to approach this project then 01:35:13.500 --> 01:35:16.370 align:start position:0% way to approach this project then including<01:35:14.340> a<01:35:14.580> new<01:35:14.699> getter<01:35:15.060> function<01:35:15.420> as<01:35:16.199> an 01:35:16.370 --> 01:35:16.380 align:start position:0% including a new getter function as an 01:35:16.380 --> 01:35:19.250 align:start position:0% including a new getter function as an EIP<01:35:16.880> within<01:35:17.880> the<01:35:18.179> solidity<01:35:18.540> world<01:35:18.780> this<01:35:19.139> is 01:35:19.250 --> 01:35:19.260 align:start position:0% EIP within the solidity world this is 01:35:19.260 --> 01:35:22.850 align:start position:0% EIP within the solidity world this is all<01:35:19.500> off-chain<01:35:20.300> metadata<01:35:21.679> we're<01:35:22.679> talking 01:35:22.850 --> 01:35:22.860 align:start position:0% all off-chain metadata we're talking 01:35:22.860 --> 01:35:24.590 align:start position:0% all off-chain metadata we're talking about 01:35:24.590 --> 01:35:24.600 align:start position:0% about 01:35:24.600 --> 01:35:27.110 align:start position:0% about I<01:35:25.080> have<01:35:25.260> a<01:35:25.380> little<01:35:25.500> bit<01:35:25.679> of<01:35:25.800> time<01:35:25.920> so<01:35:26.400> be<01:35:26.820> glad 01:35:27.110 --> 01:35:27.120 align:start position:0% I have a little bit of time so be glad 01:35:27.120 --> 01:35:29.570 align:start position:0% I have a little bit of time so be glad to<01:35:27.300> open<01:35:27.420> it<01:35:27.600> up<01:35:27.719> for<01:35:27.960> questions<01:35:28.199> yes<01:35:29.040> thank 01:35:29.570 --> 01:35:29.580 align:start position:0% to open it up for questions yes thank 01:35:29.580 --> 01:35:33.550 align:start position:0% to open it up for questions yes thank you<01:35:29.699> Ian<01:35:30.120> thank<01:35:30.840> you<01:35:31.020> round<01:35:31.679> of<01:35:31.920> applause 01:35:33.550 --> 01:35:33.560 align:start position:0% you Ian thank you round of applause 01:35:33.560 --> 01:35:36.950 align:start position:0% you Ian thank you round of applause [Applause] 01:35:36.950 --> 01:35:36.960 align:start position:0% [Applause] 01:35:36.960 --> 01:35:39.229 align:start position:0% [Applause] we<01:35:37.380> have<01:35:37.500> one<01:35:37.739> question 01:35:39.229 --> 01:35:39.239 align:start position:0% we have one question 01:35:39.239 --> 01:35:41.510 align:start position:0% we have one question hi<01:35:39.540> I'm<01:35:39.719> Marcus<01:35:40.020> nice<01:35:40.440> to<01:35:40.560> meet<01:35:40.620> you<01:35:41.219> um<01:35:41.280> if 01:35:41.510 --> 01:35:41.520 align:start position:0% hi I'm Marcus nice to meet you um if 01:35:41.520 --> 01:35:44.990 align:start position:0% hi I'm Marcus nice to meet you um if this<01:35:41.699> was<01:35:41.880> implemented<01:35:42.480> as<01:35:42.900> an<01:35:43.080> EIP<01:35:43.880> what<01:35:44.880> do 01:35:44.990 --> 01:35:45.000 align:start position:0% this was implemented as an EIP what do 01:35:45.000 --> 01:35:46.490 align:start position:0% this was implemented as an EIP what do you<01:35:45.060> think<01:35:45.179> the<01:35:45.360> second<01:35:45.600> and<01:35:45.960> third<01:35:46.199> order 01:35:46.490 --> 01:35:46.500 align:start position:0% you think the second and third order 01:35:46.500 --> 01:35:49.129 align:start position:0% you think the second and third order effects<01:35:47.040> of<01:35:47.159> this<01:35:47.340> would<01:35:47.520> be 01:35:49.129 --> 01:35:49.139 align:start position:0% effects of this would be 01:35:49.139 --> 01:35:51.709 align:start position:0% effects of this would be I<01:35:49.620> hope<01:35:49.860> the<01:35:50.159> very<01:35:50.520> first 01:35:51.709 --> 01:35:51.719 align:start position:0% I hope the very first 01:35:51.719 --> 01:35:54.590 align:start position:0% I hope the very first um<01:35:51.840> thing<01:35:52.320> is<01:35:52.739> indexers 01:35:54.590 --> 01:35:54.600 align:start position:0% um thing is indexers 01:35:54.600 --> 01:35:56.689 align:start position:0% um thing is indexers Pro<01:35:55.260> platforms<01:35:55.920> would<01:35:56.159> include<01:35:56.460> it<01:35:56.520> in 01:35:56.689 --> 01:35:56.699 align:start position:0% Pro platforms would include it in 01:35:56.699 --> 01:35:58.669 align:start position:0% Pro platforms would include it in minting<01:35:57.000> so<01:35:57.179> manifold<01:35:57.659> actually<01:35:57.900> does<01:35:58.260> really 01:35:58.669 --> 01:35:58.679 align:start position:0% minting so manifold actually does really 01:35:58.679 --> 01:36:01.669 align:start position:0% minting so manifold actually does really try<01:35:59.100> hard<01:35:59.460> to<01:36:00.239> include<01:36:00.600> a<01:36:00.960> lot<01:36:01.020> of<01:36:01.139> metadata 01:36:01.669 --> 01:36:01.679 align:start position:0% try hard to include a lot of metadata 01:36:01.679 --> 01:36:04.070 align:start position:0% try hard to include a lot of metadata they<01:36:01.800> do<01:36:01.980> image<01:36:02.280> image<01:36:02.699> underscore<01:36:03.179> URL<01:36:03.719> image 01:36:04.070 --> 01:36:04.080 align:start position:0% they do image image underscore URL image 01:36:04.080 --> 01:36:06.590 align:start position:0% they do image image underscore URL image includes<01:36:04.560> the<01:36:04.800> hash<01:36:05.040> and<01:36:05.460> the<01:36:05.639> URL<01:36:06.060> and<01:36:06.420> the 01:36:06.590 --> 01:36:06.600 align:start position:0% includes the hash and the URL and the 01:36:06.600 --> 01:36:08.510 align:start position:0% includes the hash and the URL and the content<01:36:06.840> type<01:36:07.020> and<01:36:07.199> some<01:36:07.380> other<01:36:07.500> data<01:36:07.920> so<01:36:08.400> I 01:36:08.510 --> 01:36:08.520 align:start position:0% content type and some other data so I 01:36:08.520 --> 01:36:09.649 align:start position:0% content type and some other data so I think<01:36:08.639> kind<01:36:08.820> of<01:36:08.880> thinking<01:36:09.179> with<01:36:09.300> them<01:36:09.420> to 01:36:09.649 --> 01:36:09.659 align:start position:0% think kind of thinking with them to 01:36:09.659 --> 01:36:12.410 align:start position:0% think kind of thinking with them to figure<01:36:09.780> out<01:36:09.960> what<01:36:10.260> their<01:36:10.440> needs<01:36:10.800> are<01:36:10.920> but<01:36:11.699> once 01:36:12.410 --> 01:36:12.420 align:start position:0% figure out what their needs are but once 01:36:12.420 --> 01:36:14.750 align:start position:0% figure out what their needs are but once you<01:36:12.540> start<01:36:12.780> having<01:36:13.199> stuff<01:36:13.739> minted<01:36:14.280> in<01:36:14.580> this 01:36:14.750 --> 01:36:14.760 align:start position:0% you start having stuff minted in this 01:36:14.760 --> 01:36:16.669 align:start position:0% you start having stuff minted in this format<01:36:15.300> I<01:36:16.080> think<01:36:16.199> it's<01:36:16.320> going<01:36:16.500> to<01:36:16.560> hit 01:36:16.669 --> 01:36:16.679 align:start position:0% format I think it's going to hit 01:36:16.679 --> 01:36:18.590 align:start position:0% format I think it's going to hit indexers<01:36:17.219> and<01:36:17.520> then<01:36:17.639> once<01:36:17.880> indexers<01:36:18.360> can 01:36:18.590 --> 01:36:18.600 align:start position:0% indexers and then once indexers can 01:36:18.600 --> 01:36:21.110 align:start position:0% indexers and then once indexers can understand<01:36:18.780> this<01:36:19.260> people<01:36:19.620> can<01:36:19.980> say<01:36:20.280> oh<01:36:20.760> I<01:36:21.000> can 01:36:21.110 --> 01:36:21.120 align:start position:0% understand this people can say oh I can 01:36:21.120 --> 01:36:23.709 align:start position:0% understand this people can say oh I can upload<01:36:21.420> Illustrator<01:36:21.840> files<01:36:22.260> I<01:36:22.560> can<01:36:22.739> upload 01:36:23.709 --> 01:36:23.719 align:start position:0% upload Illustrator files I can upload 01:36:23.719 --> 01:36:26.750 align:start position:0% upload Illustrator files I can upload webgl<01:36:24.719> shaders<01:36:25.260> I<01:36:25.500> can<01:36:25.620> upload<01:36:26.040> some<01:36:26.340> binary 01:36:26.750 --> 01:36:26.760 align:start position:0% webgl shaders I can upload some binary 01:36:26.760 --> 01:36:28.850 align:start position:0% webgl shaders I can upload some binary form<01:36:27.060> like<01:36:27.420> you<01:36:27.719> can<01:36:27.840> actually<01:36:28.080> now<01:36:28.380> mint<01:36:28.739> a 01:36:28.850 --> 01:36:28.860 align:start position:0% form like you can actually now mint a 01:36:28.860 --> 01:36:31.189 align:start position:0% form like you can actually now mint a solidity<01:36:29.280> contract<01:36:29.699> and<01:36:30.120> when<01:36:30.540> somebody<01:36:30.719> buys 01:36:31.189 --> 01:36:31.199 align:start position:0% solidity contract and when somebody buys 01:36:31.199 --> 01:36:32.930 align:start position:0% solidity contract and when somebody buys it<01:36:31.320> they'll<01:36:31.800> feel<01:36:32.040> more<01:36:32.340> assured<01:36:32.760> that 01:36:32.930 --> 01:36:32.940 align:start position:0% it they'll feel more assured that 01:36:32.940 --> 01:36:34.250 align:start position:0% it they'll feel more assured that they're<01:36:33.179> actually<01:36:33.360> buying<01:36:33.719> a<01:36:33.840> solidity 01:36:34.250 --> 01:36:34.260 align:start position:0% they're actually buying a solidity 01:36:34.260 --> 01:36:36.229 align:start position:0% they're actually buying a solidity contract<01:36:34.500> rather<01:36:34.800> than<01:36:34.980> somebody<01:36:35.159> sit<01:36:35.699> or<01:36:36.060> the 01:36:36.229 --> 01:36:36.239 align:start position:0% contract rather than somebody sit or the 01:36:36.239 --> 01:36:37.610 align:start position:0% contract rather than somebody sit or the file<01:36:36.420> of<01:36:36.600> a<01:36:36.659> selected<01:36:37.020> contract<01:36:37.260> rather<01:36:37.440> than 01:36:37.610 --> 01:36:37.620 align:start position:0% file of a selected contract rather than 01:36:37.620 --> 01:36:40.310 align:start position:0% file of a selected contract rather than somebody<01:36:37.800> saying<01:36:38.280> oh<01:36:38.580> here<01:36:39.420> is<01:36:39.659> a<01:36:39.900> solidity 01:36:40.310 --> 01:36:40.320 align:start position:0% somebody saying oh here is a solidity 01:36:40.320 --> 01:36:41.810 align:start position:0% somebody saying oh here is a solidity contract<01:36:40.679> and<01:36:40.980> what<01:36:41.100> I<01:36:41.280> typically<01:36:41.580> have 01:36:41.810 --> 01:36:41.820 align:start position:0% contract and what I typically have 01:36:41.820 --> 01:36:43.370 align:start position:0% contract and what I typically have advised<01:36:42.239> creators<01:36:42.600> to<01:36:42.780> do<01:36:42.960> is<01:36:43.139> actually 01:36:43.370 --> 01:36:43.380 align:start position:0% advised creators to do is actually 01:36:43.380 --> 01:36:45.830 align:start position:0% advised creators to do is actually explain<01:36:44.100> it<01:36:44.460> and<01:36:44.699> link<01:36:44.940> in<01:36:45.360> the<01:36:45.480> description 01:36:45.830 --> 01:36:45.840 align:start position:0% explain it and link in the description 01:36:45.840 --> 01:36:49.550 align:start position:0% explain it and link in the description the<01:36:46.679> ipfs<01:36:47.280> URL<01:36:47.820> of<01:36:48.239> the<01:36:48.360> canonical<01:36:48.780> media<01:36:49.260> it's 01:36:49.550 --> 01:36:49.560 align:start position:0% the ipfs URL of the canonical media it's 01:36:49.560 --> 01:36:52.910 align:start position:0% the ipfs URL of the canonical media it's Packy<01:36:50.159> but<01:36:50.580> it<01:36:50.699> seems<01:36:51.000> to<01:36:51.120> have<01:36:51.239> worked<01:36:51.920> and 01:36:52.910 --> 01:36:52.920 align:start position:0% Packy but it seems to have worked and 01:36:52.920 --> 01:36:54.229 align:start position:0% Packy but it seems to have worked and that<01:36:53.040> would<01:36:53.159> kind<01:36:53.340> of<01:36:53.400> remove<01:36:53.520> that<01:36:53.880> and<01:36:54.000> allow 01:36:54.229 --> 01:36:54.239 align:start position:0% that would kind of remove that and allow 01:36:54.239 --> 01:36:56.570 align:start position:0% that would kind of remove that and allow for<01:36:54.360> use<01:36:54.540> users<01:36:55.020> to<01:36:55.260> see<01:36:55.560> like<01:36:56.040> a<01:36:56.219> link<01:36:56.340> and 01:36:56.570 --> 01:36:56.580 align:start position:0% for use users to see like a link and 01:36:56.580 --> 01:36:58.010 align:start position:0% for use users to see like a link and I've<01:36:56.760> seen<01:36:57.000> artists<01:36:57.360> on<01:36:57.540> Twitter<01:36:57.659> talking 01:36:58.010 --> 01:36:58.020 align:start position:0% I've seen artists on Twitter talking 01:36:58.020 --> 01:37:00.290 align:start position:0% I've seen artists on Twitter talking about<01:36:58.199> using<01:36:58.620> unlockable<01:36:59.159> media<01:36:59.580> and<01:36:59.760> open<01:37:00.000> C 01:37:00.290 --> 01:37:00.300 align:start position:0% about using unlockable media and open C 01:37:00.300 --> 01:37:02.570 align:start position:0% about using unlockable media and open C to<01:37:00.659> include<01:37:00.900> the<01:37:01.139> source<01:37:01.500> files<01:37:01.800> and<01:37:02.340> if<01:37:02.460> the 01:37:02.570 --> 01:37:02.580 align:start position:0% to include the source files and if the 01:37:02.580 --> 01:37:03.770 align:start position:0% to include the source files and if the artist<01:37:02.699> is<01:37:03.000> comfortable<01:37:03.300> they<01:37:03.480> could<01:37:03.659> just 01:37:03.770 --> 01:37:03.780 align:start position:0% artist is comfortable they could just 01:37:03.780 --> 01:37:05.209 align:start position:0% artist is comfortable they could just include<01:37:04.020> the<01:37:04.139> source<01:37:04.440> files<01:37:04.739> and<01:37:04.860> it<01:37:04.980> would<01:37:05.100> be 01:37:05.209 --> 01:37:05.219 align:start position:0% include the source files and it would be 01:37:05.219 --> 01:37:07.490 align:start position:0% include the source files and it would be a<01:37:05.340> link<01:37:05.520> or<01:37:05.820> some<01:37:06.120> sort<01:37:06.300> of<01:37:06.420> description<01:37:07.080> on 01:37:07.490 --> 01:37:07.500 align:start position:0% a link or some sort of description on 01:37:07.500 --> 01:37:09.050 align:start position:0% a link or some sort of description on Plat<01:37:07.860> marketplaces<01:37:08.460> and<01:37:08.580> since<01:37:08.760> this<01:37:08.940> is 01:37:09.050 --> 01:37:09.060 align:start position:0% Plat marketplaces and since this is 01:37:09.060 --> 01:37:11.270 align:start position:0% Plat marketplaces and since this is relatively<01:37:09.480> easy<01:37:09.659> to<01:37:09.900> implement<01:37:10.260> once<01:37:11.040> a<01:37:11.159> few 01:37:11.270 --> 01:37:11.280 align:start position:0% relatively easy to implement once a few 01:37:11.280 --> 01:37:14.510 align:start position:0% relatively easy to implement once a few start<01:37:11.520> I<01:37:11.760> think<01:37:11.820> it<01:37:12.000> would<01:37:12.120> start<01:37:12.300> spreading 01:37:14.510 --> 01:37:14.520 align:start position:0% start I think it would start spreading 01:37:14.520 --> 01:37:17.510 align:start position:0% start I think it would start spreading thank<01:37:14.940> you<01:37:15.060> we<01:37:15.360> have<01:37:15.480> another<01:37:15.600> one<01:37:15.780> here 01:37:17.510 --> 01:37:17.520 align:start position:0% thank you we have another one here 01:37:17.520 --> 01:37:20.149 align:start position:0% thank you we have another one here hi<01:37:17.880> hello<01:37:18.060> congrats<01:37:18.719> for<01:37:18.840> the<01:37:19.080> project 01:37:20.149 --> 01:37:20.159 align:start position:0% hi hello congrats for the project 01:37:20.159 --> 01:37:23.689 align:start position:0% hi hello congrats for the project um<01:37:20.580> so<01:37:21.120> content<01:37:21.659> type<01:37:21.840> is<01:37:22.560> a<01:37:22.980> response<01:37:23.400> header 01:37:23.689 --> 01:37:23.699 align:start position:0% um so content type is a response header 01:37:23.699 --> 01:37:25.450 align:start position:0% um so content type is a response header an<01:37:23.820> attp<01:37:24.420> right 01:37:25.450 --> 01:37:25.460 align:start position:0% an attp right 01:37:25.460 --> 01:37:27.950 align:start position:0% an attp right thinking<01:37:26.460> about<01:37:26.639> you<01:37:27.239> know<01:37:27.300> the<01:37:27.480> second<01:37:27.719> order 01:37:27.950 --> 01:37:27.960 align:start position:0% thinking about you know the second order 01:37:27.960 --> 01:37:32.290 align:start position:0% thinking about you know the second order effects<01:37:28.880> have<01:37:29.880> you<01:37:30.120> thought<01:37:31.080> or<01:37:31.380> worked<01:37:31.860> on 01:37:32.290 --> 01:37:32.300 align:start position:0% effects have you thought or worked on 01:37:32.300 --> 01:37:35.810 align:start position:0% effects have you thought or worked on the<01:37:33.300> request<01:37:33.719> headers<01:37:34.380> equivalent<01:37:35.040> like<01:37:35.520> the 01:37:35.810 --> 01:37:35.820 align:start position:0% the request headers equivalent like the 01:37:35.820 --> 01:37:38.629 align:start position:0% the request headers equivalent like the accept<01:37:36.000> and<01:37:36.900> then<01:37:37.080> having<01:37:37.860> some<01:37:38.219> specific 01:37:38.629 --> 01:37:38.639 align:start position:0% accept and then having some specific 01:37:38.639 --> 01:37:41.930 align:start position:0% accept and then having some specific wild<01:37:39.000> cards<01:37:39.480> such<01:37:39.960> as<01:37:40.199> Text<01:37:40.620> slash<01:37:41.460> and<01:37:41.820> then 01:37:41.930 --> 01:37:41.940 align:start position:0% wild cards such as Text slash and then 01:37:41.940 --> 01:37:43.729 align:start position:0% wild cards such as Text slash and then wildcard 01:37:43.729 --> 01:37:43.739 align:start position:0% wildcard 01:37:43.739 --> 01:37:45.770 align:start position:0% wildcard so<01:37:44.219> the<01:37:44.400> one<01:37:44.580> problem<01:37:44.760> when<01:37:45.060> you're<01:37:45.239> indexing 01:37:45.770 --> 01:37:45.780 align:start position:0% so the one problem when you're indexing 01:37:45.780 --> 01:37:48.290 align:start position:0% so the one problem when you're indexing is<01:37:46.199> that<01:37:46.440> a<01:37:46.679> lot<01:37:46.800> of<01:37:46.920> times<01:37:47.100> ipfs<01:37:47.820> is<01:37:48.000> really 01:37:48.290 --> 01:37:48.300 align:start position:0% is that a lot of times ipfs is really 01:37:48.300 --> 01:37:51.770 align:start position:0% is that a lot of times ipfs is really slow<01:37:48.659> people's<01:37:49.260> servers<01:37:49.679> go<01:37:49.980> down<01:37:50.659> if<01:37:51.659> you're 01:37:51.770 --> 01:37:51.780 align:start position:0% slow people's servers go down if you're 01:37:51.780 --> 01:37:54.169 align:start position:0% slow people's servers go down if you're able<01:37:52.139> to<01:37:52.320> get<01:37:52.500> the<01:37:52.739> metadata<01:37:53.340> on<01:37:53.520> the<01:37:53.639> client<01:37:53.880> a 01:37:54.169 --> 01:37:54.179 align:start position:0% able to get the metadata on the client a 01:37:54.179 --> 01:37:55.970 align:start position:0% able to get the metadata on the client a lot<01:37:54.239> of<01:37:54.360> people<01:37:54.420> hot<01:37:54.780> link<01:37:55.020> directly<01:37:55.620> to<01:37:55.860> an 01:37:55.970 --> 01:37:55.980 align:start position:0% lot of people hot link directly to an 01:37:55.980 --> 01:37:58.490 align:start position:0% lot of people hot link directly to an ipfs<01:37:56.460> Gateway<01:37:56.880> and<01:37:57.600> pulling<01:37:58.020> the<01:37:58.199> content 01:37:58.490 --> 01:37:58.500 align:start position:0% ipfs Gateway and pulling the content 01:37:58.500 --> 01:38:00.890 align:start position:0% ipfs Gateway and pulling the content type<01:37:58.679> out<01:37:59.100> of<01:37:59.219> the<01:37:59.340> headers<01:37:59.699> really<01:38:00.480> allows 01:38:00.890 --> 01:38:00.900 align:start position:0% type out of the headers really allows 01:38:00.900 --> 01:38:03.830 align:start position:0% type out of the headers really allows for<01:38:01.380> a<01:38:02.280> better<01:38:02.520> set<01:38:02.820> of<01:38:03.000> expectations<01:38:03.480> when 01:38:03.830 --> 01:38:03.840 align:start position:0% for a better set of expectations when 01:38:03.840 --> 01:38:05.390 align:start position:0% for a better set of expectations when you're<01:38:03.960> indexing<01:38:04.380> and<01:38:04.560> rendering<01:38:04.920> the<01:38:05.100> nft 01:38:05.390 --> 01:38:05.400 align:start position:0% you're indexing and rendering the nft 01:38:05.400 --> 01:38:08.090 align:start position:0% you're indexing and rendering the nft but<01:38:06.239> your<01:38:06.540> question<01:38:06.659> is<01:38:06.900> to<01:38:07.139> kind<01:38:07.320> of<01:38:07.440> use<01:38:07.920> the 01:38:08.090 --> 01:38:08.100 align:start position:0% but your question is to kind of use the 01:38:08.100 --> 01:38:11.030 align:start position:0% but your question is to kind of use the HTTP<01:38:08.580> response<01:38:09.120> conversation<01:38:09.719> to<01:38:10.320> define<01:38:10.560> the 01:38:11.030 --> 01:38:11.040 align:start position:0% HTTP response conversation to define the 01:38:11.040 --> 01:38:12.770 align:start position:0% HTTP response conversation to define the Mind<01:38:11.400> type<01:38:11.699> rather<01:38:12.120> than<01:38:12.239> put<01:38:12.420> it<01:38:12.540> in<01:38:12.719> the 01:38:12.770 --> 01:38:12.780 align:start position:0% Mind type rather than put it in the 01:38:12.780 --> 01:38:14.990 align:start position:0% Mind type rather than put it in the metadata<01:38:13.320> yeah<01:38:13.739> sure<01:38:13.920> so<01:38:14.219> there<01:38:14.460> is<01:38:14.639> the 01:38:14.990 --> 01:38:15.000 align:start position:0% metadata yeah sure so there is the 01:38:15.000 --> 01:38:18.110 align:start position:0% metadata yeah sure so there is the content<01:38:15.840> negotiation<01:38:16.500> step<01:38:17.340> right<01:38:17.580> so<01:38:17.880> and 01:38:18.110 --> 01:38:18.120 align:start position:0% content negotiation step right so and 01:38:18.120 --> 01:38:22.310 align:start position:0% content negotiation step right so and then<01:38:18.540> you<01:38:18.960> have<01:38:19.139> from<01:38:19.500> the<01:38:19.920> accept 01:38:22.310 --> 01:38:22.320 align:start position:0% then you have from the accept 01:38:22.320 --> 01:38:25.610 align:start position:0% then you have from the accept request<01:38:23.159> header<01:38:23.699> and 01:38:25.610 --> 01:38:25.620 align:start position:0% request header and 01:38:25.620 --> 01:38:28.729 align:start position:0% request header and more<01:38:26.219> often<01:38:26.580> you<01:38:27.239> have<01:38:27.420> like<01:38:27.840> some<01:38:28.380> sort<01:38:28.620> of 01:38:28.729 --> 01:38:28.739 align:start position:0% more often you have like some sort of 01:38:28.739 --> 01:38:30.830 align:start position:0% more often you have like some sort of wild<01:38:28.980> card<01:38:29.219> there<01:38:29.520> right<01:38:29.880> so<01:38:30.300> that<01:38:30.480> can<01:38:30.600> help 01:38:30.830 --> 01:38:30.840 align:start position:0% wild card there right so that can help 01:38:30.840 --> 01:38:32.930 align:start position:0% wild card there right so that can help uh<01:38:31.260> you<01:38:31.440> know<01:38:31.500> more<01:38:31.620> generic<01:38:32.100> applications<01:38:32.580> to 01:38:32.930 --> 01:38:32.940 align:start position:0% uh you know more generic applications to 01:38:32.940 --> 01:38:36.129 align:start position:0% uh you know more generic applications to accept<01:38:33.179> let's<01:38:33.480> say<01:38:33.659> image<01:38:34.380> slash<01:38:35.219> column<01:38:35.639> uh 01:38:36.129 --> 01:38:36.139 align:start position:0% accept let's say image slash column uh 01:38:36.139 --> 01:38:38.689 align:start position:0% accept let's say image slash column uh wildcard<01:38:37.139> something<01:38:37.500> so<01:38:37.980> I<01:38:38.100> think<01:38:38.219> a<01:38:38.400> lot<01:38:38.580> of 01:38:38.689 --> 01:38:38.699 align:start position:0% wildcard something so I think a lot of 01:38:38.699 --> 01:38:41.450 align:start position:0% wildcard something so I think a lot of the<01:38:38.880> off<01:38:39.320> off-chain<01:38:40.320> nfts<01:38:40.860> go<01:38:41.159> through<01:38:41.280> a 01:38:41.450 --> 01:38:41.460 align:start position:0% the off off-chain nfts go through a 01:38:41.460 --> 01:38:43.490 align:start position:0% the off off-chain nfts go through a decentralized<01:38:42.060> Gateway<01:38:42.480> provider<01:38:42.960> and<01:38:43.320> those 01:38:43.490 --> 01:38:43.500 align:start position:0% decentralized Gateway provider and those 01:38:43.500 --> 01:38:45.770 align:start position:0% decentralized Gateway provider and those Gateway<01:38:43.800> providers<01:38:44.219> are<01:38:44.460> not<01:38:44.760> very<01:38:45.120> like 01:38:45.770 --> 01:38:45.780 align:start position:0% Gateway providers are not very like 01:38:45.780 --> 01:38:47.870 align:start position:0% Gateway providers are not very like you're<01:38:46.020> out<01:38:46.260> the<01:38:46.560> control<01:38:46.800> of<01:38:47.340> the<01:38:47.520> server 01:38:47.870 --> 01:38:47.880 align:start position:0% you're out the control of the server 01:38:47.880 --> 01:38:49.970 align:start position:0% you're out the control of the server retrieving<01:38:48.480> decentralized<01:38:49.199> media<01:38:49.500> is<01:38:49.620> out<01:38:49.860> of 01:38:49.970 --> 01:38:49.980 align:start position:0% retrieving decentralized media is out of 01:38:49.980 --> 01:38:52.189 align:start position:0% retrieving decentralized media is out of the<01:38:50.100> control<01:38:50.219> of<01:38:50.460> the<01:38:50.580> user<01:38:50.880> in<01:38:51.000> most<01:38:51.179> cases<01:38:51.540> so 01:38:52.189 --> 01:38:52.199 align:start position:0% the control of the user in most cases so 01:38:52.199 --> 01:38:53.930 align:start position:0% the control of the user in most cases so you<01:38:52.380> can't<01:38:52.500> rely<01:38:52.860> on<01:38:52.980> a<01:38:53.100> server<01:38:53.340> negotiation 01:38:53.930 --> 01:38:53.940 align:start position:0% you can't rely on a server negotiation 01:38:53.940 --> 01:38:56.450 align:start position:0% you can't rely on a server negotiation you're<01:38:54.840> thinking<01:38:55.199> of<01:38:55.320> a<01:38:55.500> world<01:38:55.620> maybe<01:38:55.920> where 01:38:56.450 --> 01:38:56.460 align:start position:0% you're thinking of a world maybe where 01:38:56.460 --> 01:38:58.850 align:start position:0% you're thinking of a world maybe where there's<01:38:57.179> a<01:38:57.480> server<01:38:57.780> that<01:38:58.080> is<01:38:58.260> connected<01:38:58.620> to 01:38:58.850 --> 01:38:58.860 align:start position:0% there's a server that is connected to 01:38:58.860 --> 01:39:01.550 align:start position:0% there's a server that is connected to the<01:38:59.219> URI<01:38:59.820> of<01:39:00.179> the<01:39:00.360> nft<01:39:00.600> and<01:39:00.900> that's<01:39:01.020> becoming<01:39:01.380> a 01:39:01.550 --> 01:39:01.560 align:start position:0% the URI of the nft and that's becoming a 01:39:01.560 --> 01:39:03.110 align:start position:0% the URI of the nft and that's becoming a lot<01:39:01.679> less<01:39:01.980> common<01:39:02.219> because<01:39:02.639> that<01:39:02.880> means 01:39:03.110 --> 01:39:03.120 align:start position:0% lot less common because that means 01:39:03.120 --> 01:39:04.850 align:start position:0% lot less common because that means you're<01:39:03.300> now<01:39:03.480> having<01:39:03.719> a<01:39:03.960> centralized<01:39:04.440> point<01:39:04.679> of 01:39:04.850 --> 01:39:04.860 align:start position:0% you're now having a centralized point of 01:39:04.860 --> 01:39:07.729 align:start position:0% you're now having a centralized point of failure<01:39:05.219> so<01:39:06.000> the<01:39:06.239> idea<01:39:06.540> here<01:39:06.719> is<01:39:06.900> if<01:39:07.380> you<01:39:07.560> put 01:39:07.729 --> 01:39:07.739 align:start position:0% failure so the idea here is if you put 01:39:07.739 --> 01:39:09.649 align:start position:0% failure so the idea here is if you put it<01:39:07.860> in<01:39:07.980> the<01:39:08.100> Json<01:39:08.400> there'll<01:39:09.179> at<01:39:09.239> least<01:39:09.300> be<01:39:09.480> some 01:39:09.649 --> 01:39:09.659 align:start position:0% it in the Json there'll at least be some 01:39:09.659 --> 01:39:11.629 align:start position:0% it in the Json there'll at least be some intentionality<01:39:10.260> if<01:39:10.620> you're<01:39:10.920> on<01:39:11.159> some<01:39:11.460> weird 01:39:11.629 --> 01:39:11.639 align:start position:0% intentionality if you're on some weird 01:39:11.639 --> 01:39:13.910 align:start position:0% intentionality if you're on some weird version<01:39:12.000> of<01:39:12.179> ipfs<01:39:12.780> like<01:39:13.020> node<01:39:13.440> that<01:39:13.739> doesn't 01:39:13.910 --> 01:39:13.920 align:start position:0% version of ipfs like node that doesn't 01:39:13.920 --> 01:39:15.770 align:start position:0% version of ipfs like node that doesn't understand<01:39:14.280> the<01:39:14.760> media<01:39:15.000> it's<01:39:15.179> serving<01:39:15.540> or 01:39:15.770 --> 01:39:15.780 align:start position:0% understand the media it's serving or 01:39:15.780 --> 01:39:17.750 align:start position:0% understand the media it's serving or there's<01:39:15.960> a<01:39:16.080> bug<01:39:16.199> in<01:39:16.440> it<01:39:16.620> you'll<01:39:17.219> still<01:39:17.460> have 01:39:17.750 --> 01:39:17.760 align:start position:0% there's a bug in it you'll still have 01:39:17.760 --> 01:39:19.250 align:start position:0% there's a bug in it you'll still have something<01:39:18.000> that<01:39:18.239> kind<01:39:18.420> of<01:39:18.540> works<01:39:18.840> or<01:39:18.960> have<01:39:19.139> an 01:39:19.250 --> 01:39:19.260 align:start position:0% something that kind of works or have an 01:39:19.260 --> 01:39:20.270 align:start position:0% something that kind of works or have an expectation<01:39:19.620> of<01:39:19.860> what<01:39:19.980> the<01:39:20.159> original 01:39:20.270 --> 01:39:20.280 align:start position:0% expectation of what the original 01:39:20.280 --> 01:39:23.510 align:start position:0% expectation of what the original intention<01:39:20.820> was 01:39:23.510 --> 01:39:23.520 align:start position:0% 01:39:23.520 --> 01:39:26.270 align:start position:0% thank<01:39:24.179> you<01:39:24.360> do<01:39:24.780> we<01:39:25.020> have<01:39:25.500> more<01:39:25.980> questions 01:39:26.270 --> 01:39:26.280 align:start position:0% thank you do we have more questions 01:39:26.280 --> 01:39:29.990 align:start position:0% thank you do we have more questions maybe<01:39:26.820> one<01:39:27.300> last<01:39:27.480> question 01:39:29.990 --> 01:39:30.000 align:start position:0% 01:39:30.000 --> 01:39:33.110 align:start position:0% okay<01:39:30.719> otherwise<01:39:31.500> ah<01:39:32.100> yes<01:39:32.280> okay 01:39:33.110 --> 01:39:33.120 align:start position:0% okay otherwise ah yes okay 01:39:33.120 --> 01:39:40.790 align:start position:0% okay otherwise ah yes okay we<01:39:33.540> have<01:39:33.719> fun 01:39:40.790 --> 01:39:40.800 align:start position:0% 01:39:40.800 --> 01:39:44.270 align:start position:0% you<01:39:41.400> hear<01:39:41.699> you<01:39:41.880> define<01:39:42.060> the<01:39:42.659> um<01:39:43.040> content<01:39:44.040> type 01:39:44.270 --> 01:39:44.280 align:start position:0% you hear you define the um content type 01:39:44.280 --> 01:39:46.430 align:start position:0% you hear you define the um content type inside<01:39:44.820> the<01:39:45.120> Json 01:39:46.430 --> 01:39:46.440 align:start position:0% inside the Json 01:39:46.440 --> 01:39:49.070 align:start position:0% inside the Json um<01:39:46.560> to<01:39:46.980> like<01:39:47.340> save<01:39:47.580> some<01:39:47.940> uploads<01:39:48.600> could<01:39:48.900> you 01:39:49.070 --> 01:39:49.080 align:start position:0% um to like save some uploads could you 01:39:49.080 --> 01:39:51.229 align:start position:0% um to like save some uploads could you define<01:39:49.320> the<01:39:49.620> data<01:39:50.159> in<01:39:50.280> the<01:39:50.460> collection<01:39:50.760> as 01:39:51.229 --> 01:39:51.239 align:start position:0% define the data in the collection as 01:39:51.239 --> 01:39:52.610 align:start position:0% define the data in the collection as well 01:39:52.610 --> 01:39:52.620 align:start position:0% well 01:39:52.620 --> 01:39:54.470 align:start position:0% well that's<01:39:53.159> actually<01:39:53.400> a<01:39:53.580> great<01:39:53.760> question<01:39:54.000> that<01:39:54.300> I 01:39:54.470 --> 01:39:54.480 align:start position:0% that's actually a great question that I 01:39:54.480 --> 01:39:57.110 align:start position:0% that's actually a great question that I didn't<01:39:54.659> have<01:39:54.900> time<01:39:55.080> to<01:39:55.320> address<01:39:55.440> but<01:39:56.219> mirror 01:39:57.110 --> 01:39:57.120 align:start position:0% didn't have time to address but mirror 01:39:57.120 --> 01:39:59.810 align:start position:0% didn't have time to address but mirror and<01:39:57.300> Zora<01:39:57.840> and<01:39:58.500> a<01:39:58.800> few<01:39:58.920> other<01:39:59.040> platforms<01:39:59.580> have 01:39:59.810 --> 01:39:59.820 align:start position:0% and Zora and a few other platforms have 01:39:59.820 --> 01:40:03.050 align:start position:0% and Zora and a few other platforms have editions<01:40:00.420> and<01:40:01.199> I<01:40:01.320> think<01:40:01.699> utilizing<01:40:02.699> a 01:40:03.050 --> 01:40:03.060 align:start position:0% editions and I think utilizing a 01:40:03.060 --> 01:40:05.570 align:start position:0% editions and I think utilizing a singular<01:40:03.420> nft<01:40:03.900> metadata<01:40:04.739> in<01:40:05.040> the<01:40:05.219> contract 01:40:05.570 --> 01:40:05.580 align:start position:0% singular nft metadata in the contract 01:40:05.580 --> 01:40:08.209 align:start position:0% singular nft metadata in the contract URI<01:40:06.060> which<01:40:06.239> is<01:40:06.360> an<01:40:06.480> openc<01:40:06.840> extension<01:40:07.380> is<01:40:08.040> a 01:40:08.209 --> 01:40:08.219 align:start position:0% URI which is an openc extension is a 01:40:08.219 --> 01:40:09.649 align:start position:0% URI which is an openc extension is a really<01:40:08.340> effective<01:40:08.760> way<01:40:08.940> to<01:40:09.060> handle<01:40:09.300> that<01:40:09.480> and 01:40:09.649 --> 01:40:09.659 align:start position:0% really effective way to handle that and 01:40:09.659 --> 01:40:12.830 align:start position:0% really effective way to handle that and right<01:40:09.900> now<01:40:10.159> I<01:40:11.159> know<01:40:11.340> most<01:40:11.639> platforms<01:40:12.360> that<01:40:12.600> do 01:40:12.830 --> 01:40:12.840 align:start position:0% right now I know most platforms that do 01:40:12.840 --> 01:40:16.250 align:start position:0% right now I know most platforms that do additions<01:40:13.560> support<01:40:13.920> the<01:40:14.580> contract<01:40:15.060> URI<01:40:15.659> so 01:40:16.250 --> 01:40:16.260 align:start position:0% additions support the contract URI so 01:40:16.260 --> 01:40:19.030 align:start position:0% additions support the contract URI so for<01:40:16.500> dead<01:40:16.739> ringers<01:40:17.280> and<01:40:17.880> for 01:40:19.030 --> 01:40:19.040 align:start position:0% for dead ringers and for 01:40:19.040 --> 01:40:21.410 align:start position:0% for dead ringers and for Zora<01:40:20.040> editions<01:40:20.400> the<01:40:20.580> contract<01:40:20.820> URI<01:40:21.300> is 01:40:21.410 --> 01:40:21.420 align:start position:0% Zora editions the contract URI is 01:40:21.420 --> 01:40:22.970 align:start position:0% Zora editions the contract URI is actually<01:40:21.540> generated<01:40:21.900> on<01:40:22.260> chain<01:40:22.500> and 01:40:22.970 --> 01:40:22.980 align:start position:0% actually generated on chain and 01:40:22.980 --> 01:40:24.890 align:start position:0% actually generated on chain and sometimes<01:40:23.340> we'll<01:40:23.520> put<01:40:23.760> an<01:40:23.940> ipfs<01:40:24.420> depending<01:40:24.780> on 01:40:24.890 --> 01:40:24.900 align:start position:0% sometimes we'll put an ipfs depending on 01:40:24.900 --> 01:40:27.169 align:start position:0% sometimes we'll put an ipfs depending on how<01:40:25.080> big<01:40:25.199> the<01:40:25.440> content<01:40:25.739> is<01:40:25.920> and<01:40:26.580> that<01:40:26.760> includes 01:40:27.169 --> 01:40:27.179 align:start position:0% how big the content is and that includes 01:40:27.179 --> 01:40:29.450 align:start position:0% how big the content is and that includes image<01:40:27.480> it<01:40:27.659> includes<01:40:28.020> animation<01:40:28.500> if<01:40:29.040> every 01:40:29.450 --> 01:40:29.460 align:start position:0% image it includes animation if every 01:40:29.460 --> 01:40:30.830 align:start position:0% image it includes animation if every single<01:40:29.699> thing<01:40:29.880> in<01:40:30.060> the<01:40:30.179> collection<01:40:30.420> is<01:40:30.659> the 01:40:30.830 --> 01:40:30.840 align:start position:0% single thing in the collection is the 01:40:30.840 --> 01:40:32.930 align:start position:0% single thing in the collection is the same<01:40:30.960> and<01:40:31.500> we<01:40:31.679> use<01:40:31.800> that<01:40:32.040> internally<01:40:32.460> in<01:40:32.760> our 01:40:32.930 --> 01:40:32.940 align:start position:0% same and we use that internally in our 01:40:32.940 --> 01:40:34.550 align:start position:0% same and we use that internally in our infrastructure<01:40:33.420> to<01:40:33.780> give<01:40:33.900> a<01:40:34.080> preview<01:40:34.320> if 01:40:34.550 --> 01:40:34.560 align:start position:0% infrastructure to give a preview if 01:40:34.560 --> 01:40:36.290 align:start position:0% infrastructure to give a preview if there's<01:40:34.679> no<01:40:34.860> mints<01:40:35.280> yet<01:40:35.400> or<01:40:35.699> like<01:40:35.880> what<01:40:36.120> that 01:40:36.290 --> 01:40:36.300 align:start position:0% there's no mints yet or like what that 01:40:36.300 --> 01:40:37.490 align:start position:0% there's no mints yet or like what that whole<01:40:36.420> collection's<01:40:37.080> supposed<01:40:37.199> to<01:40:37.380> be 01:40:37.490 --> 01:40:37.500 align:start position:0% whole collection's supposed to be 01:40:37.500 --> 01:40:39.350 align:start position:0% whole collection's supposed to be there's<01:40:37.980> no<01:40:38.219> standard<01:40:38.520> around<01:40:38.699> it<01:40:38.940> but<01:40:39.120> this 01:40:39.350 --> 01:40:39.360 align:start position:0% there's no standard around it but this 01:40:39.360 --> 01:40:41.629 align:start position:0% there's no standard around it but this would<01:40:39.540> also<01:40:39.840> slot<01:40:40.199> quite<01:40:40.500> well<01:40:40.739> within<01:40:41.520> the 01:40:41.629 --> 01:40:41.639 align:start position:0% would also slot quite well within the 01:40:41.639 --> 01:40:43.490 align:start position:0% would also slot quite well within the contract<01:40:41.940> metadata<01:40:42.659> if<01:40:43.020> you<01:40:43.139> wanted<01:40:43.260> to<01:40:43.440> have 01:40:43.490 --> 01:40:43.500 align:start position:0% contract metadata if you wanted to have 01:40:43.500 --> 01:40:45.350 align:start position:0% contract metadata if you wanted to have a<01:40:43.620> canonical<01:40:44.040> contract 01:40:45.350 --> 01:40:45.360 align:start position:0% a canonical contract 01:40:45.360 --> 01:40:48.950 align:start position:0% a canonical contract um<01:40:45.900> content<01:40:46.560> field<01:40:46.739> it<01:40:46.980> should<01:40:47.100> just<01:40:47.280> work 01:40:48.950 --> 01:40:48.960 align:start position:0% um content field it should just work 01:40:48.960 --> 01:40:51.770 align:start position:0% um content field it should just work thank<01:40:49.679> you<01:40:49.800> Ian<01:40:50.340> Round<01:40:50.639> of<01:40:50.880> Applause<01:40:51.239> thank 01:40:51.770 --> 01:40:51.780 align:start position:0% thank you Ian Round of Applause thank 01:40:51.780 --> 01:40:52.850 align:start position:0% thank you Ian Round of Applause thank you<01:40:51.840> very<01:40:51.960> much 01:40:52.850 --> 01:40:52.860 align:start position:0% you very much 01:40:52.860 --> 01:40:55.270 align:start position:0% you very much thank<01:40:53.280> you<01:40:53.340> everybody 01:40:55.270 --> 01:40:55.280 align:start position:0% thank you everybody 01:40:55.280 --> 01:40:59.530 align:start position:0% thank you everybody next<01:40:56.280> up<01:40:56.520> is<01:40:56.880> Francisco<01:40:57.239> from 01:40:59.530 --> 01:40:59.540 align:start position:0% next up is Francisco from 01:40:59.540 --> 01:41:03.169 align:start position:0% next up is Francisco from openc<01:41:00.540> thank<01:41:01.020> you<01:41:01.280> which<01:41:02.280> is<01:41:02.460> gonna<01:41:02.639> speak 01:41:03.169 --> 01:41:03.179 align:start position:0% openc thank you which is gonna speak 01:41:03.179 --> 01:41:05.470 align:start position:0% openc thank you which is gonna speak about<01:41:03.360> EIP 01:41:05.470 --> 01:41:05.480 align:start position:0% about EIP 01:41:05.480 --> 01:41:09.229 align:start position:0% about EIP 5267<01:41:06.560> and<01:41:07.560> I<01:41:08.100> have<01:41:08.219> been<01:41:08.400> saying<01:41:08.820> the<01:41:09.000> entire 01:41:09.229 --> 01:41:09.239 align:start position:0% 5267 and I have been saying the entire 01:41:09.239 --> 01:41:12.169 align:start position:0% 5267 and I have been saying the entire time<01:41:09.480> that<01:41:09.719> it's<01:41:09.900> a<01:41:10.139> it's<01:41:10.620> about<01:41:11.100> the<01:41:11.639> domain 01:41:12.169 --> 01:41:12.179 align:start position:0% time that it's a it's about the domain 01:41:12.179 --> 01:41:15.830 align:start position:0% time that it's a it's about the domain separator<01:41:12.780> so<01:41:13.739> yeah<01:41:13.920> okay<01:41:14.219> gladly 01:41:15.830 --> 01:41:15.840 align:start position:0% separator so yeah okay gladly 01:41:15.840 --> 01:41:17.629 align:start position:0% separator so yeah okay gladly um<01:41:15.900> yeah<01:41:16.080> so<01:41:16.320> sorry<01:41:16.620> we're<01:41:16.980> gonna<01:41:17.100> move<01:41:17.460> on 01:41:17.629 --> 01:41:17.639 align:start position:0% um yeah so sorry we're gonna move on 01:41:17.639 --> 01:41:20.090 align:start position:0% um yeah so sorry we're gonna move on from<01:41:17.880> nfts<01:41:18.600> now<01:41:19.260> um<01:41:19.320> it's<01:41:19.500> going<01:41:19.739> to<01:41:19.800> be<01:41:19.920> about 01:41:20.090 --> 01:41:20.100 align:start position:0% from nfts now um it's going to be about 01:41:20.100 --> 01:41:23.030 align:start position:0% from nfts now um it's going to be about erc20s<01:41:21.060> which<01:41:21.179> are<01:41:21.300> boring<01:41:21.600> now<01:41:21.780> but<01:41:21.960> okay 01:41:23.030 --> 01:41:23.040 align:start position:0% erc20s which are boring now but okay 01:41:23.040 --> 01:41:25.550 align:start position:0% erc20s which are boring now but okay um<01:41:23.100> I'm<01:41:23.520> correction<01:41:24.120> I'm<01:41:24.360> not<01:41:24.540> from<01:41:24.780> openc<01:41:25.260> I 01:41:25.550 --> 01:41:25.560 align:start position:0% um I'm correction I'm not from openc I 01:41:25.560 --> 01:41:27.830 align:start position:0% um I'm correction I'm not from openc I work<01:41:25.679> at<01:41:25.860> open<01:41:26.040> Zeppelin<01:41:26.639> uh<01:41:27.120> maintain<01:41:27.659> and 01:41:27.830 --> 01:41:27.840 align:start position:0% work at open Zeppelin uh maintain and 01:41:27.840 --> 01:41:29.470 align:start position:0% work at open Zeppelin uh maintain and develop<01:41:28.080> open<01:41:28.260> sampling<01:41:28.620> contracts<01:41:29.159> which 01:41:29.470 --> 01:41:29.480 align:start position:0% develop open sampling contracts which 01:41:29.480 --> 01:41:32.629 align:start position:0% develop open sampling contracts which obviously<01:41:30.480> maintains<01:41:31.440> many<01:41:32.159> ERC 01:41:32.629 --> 01:41:32.639 align:start position:0% obviously maintains many ERC 01:41:32.639 --> 01:41:35.510 align:start position:0% obviously maintains many ERC implementations<01:41:33.179> and<01:41:33.780> so<01:41:34.040> this<01:41:35.040> is<01:41:35.159> a<01:41:35.400> really 01:41:35.510 --> 01:41:35.520 align:start position:0% implementations and so this is a really 01:41:35.520 --> 01:41:37.609 align:start position:0% implementations and so this is a really important<01:41:35.760> topic<01:41:36.060> to<01:41:36.239> me 01:41:37.609 --> 01:41:37.619 align:start position:0% important topic to me 01:41:37.619 --> 01:41:38.229 align:start position:0% important topic to me um 01:41:38.229 --> 01:41:38.239 align:start position:0% um 01:41:38.239 --> 01:41:41.270 align:start position:0% um so<01:41:39.239> this<01:41:40.080> eib<01:41:40.440> that<01:41:40.739> I'm<01:41:40.860> going<01:41:40.980> to<01:41:41.040> be<01:41:41.100> talking 01:41:41.270 --> 01:41:41.280 align:start position:0% so this eib that I'm going to be talking 01:41:41.280 --> 01:41:44.030 align:start position:0% so this eib that I'm going to be talking about<01:41:41.460> is<01:41:41.880> really<01:41:42.179> quite<01:41:42.480> tiny 01:41:44.030 --> 01:41:44.040 align:start position:0% about is really quite tiny 01:41:44.040 --> 01:41:45.350 align:start position:0% about is really quite tiny um<01:41:44.159> but<01:41:44.340> I<01:41:44.460> want<01:41:44.520> to<01:41:44.639> use<01:41:44.699> it<01:41:44.880> more<01:41:45.000> as<01:41:45.179> an 01:41:45.350 --> 01:41:45.360 align:start position:0% um but I want to use it more as an 01:41:45.360 --> 01:41:46.970 align:start position:0% um but I want to use it more as an excuse<01:41:45.600> maybe<01:41:45.840> to<01:41:46.080> talk<01:41:46.260> about<01:41:46.380> the<01:41:46.679> process 01:41:46.970 --> 01:41:46.980 align:start position:0% excuse maybe to talk about the process 01:41:46.980 --> 01:41:49.490 align:start position:0% excuse maybe to talk about the process of<01:41:47.400> building<01:41:47.880> an<01:41:48.060> EIP<01:41:48.360> and<01:41:48.600> what<01:41:48.840> the<01:41:49.020> kind<01:41:49.380> of 01:41:49.490 --> 01:41:49.500 align:start position:0% of building an EIP and what the kind of 01:41:49.500 --> 01:41:51.709 align:start position:0% of building an EIP and what the kind of steps<01:41:49.800> that<01:41:49.980> I<01:41:50.159> think<01:41:50.340> uh<01:41:51.000> one<01:41:51.239> should<01:41:51.420> follow 01:41:51.709 --> 01:41:51.719 align:start position:0% steps that I think uh one should follow 01:41:51.719 --> 01:41:55.370 align:start position:0% steps that I think uh one should follow so<01:41:52.679> because<01:41:52.980> like<01:41:53.280> eip1<01:41:54.179> which<01:41:54.780> it's<01:41:55.020> not<01:41:55.199> here 01:41:55.370 --> 01:41:55.380 align:start position:0% so because like eip1 which it's not here 01:41:55.380 --> 01:41:57.470 align:start position:0% so because like eip1 which it's not here but<01:41:55.619> maybe<01:41:56.040> you've<01:41:56.340> all<01:41:56.460> seen<01:41:56.699> it<01:41:56.880> kind<01:41:57.360> of 01:41:57.470 --> 01:41:57.480 align:start position:0% but maybe you've all seen it kind of 01:41:57.480 --> 01:41:59.990 align:start position:0% but maybe you've all seen it kind of defines<01:41:57.900> the<01:41:58.080> series<01:41:58.260> of<01:41:58.500> stages<01:41:58.800> like<01:41:59.219> draft 01:41:59.990 --> 01:42:00.000 align:start position:0% defines the series of stages like draft 01:42:00.000 --> 01:42:02.330 align:start position:0% defines the series of stages like draft review<01:42:00.840> last<01:42:01.320> call<01:42:01.560> and<01:42:01.800> final<01:42:01.980> but<01:42:02.219> it 01:42:02.330 --> 01:42:02.340 align:start position:0% review last call and final but it 01:42:02.340 --> 01:42:04.129 align:start position:0% review last call and final but it doesn't<01:42:02.460> really<01:42:02.639> say<01:42:02.880> what<01:42:03.179> should<01:42:03.360> happen<01:42:03.600> in 01:42:04.129 --> 01:42:04.139 align:start position:0% doesn't really say what should happen in 01:42:04.139 --> 01:42:06.890 align:start position:0% doesn't really say what should happen in each<01:42:04.380> of<01:42:04.560> those<01:42:04.920> stages<01:42:05.760> so<01:42:06.300> I<01:42:06.540> want<01:42:06.600> to<01:42:06.780> share 01:42:06.890 --> 01:42:06.900 align:start position:0% each of those stages so I want to share 01:42:06.900 --> 01:42:09.950 align:start position:0% each of those stages so I want to share how<01:42:07.380> I<01:42:07.619> personally<01:42:07.980> I'm<01:42:08.760> thinking<01:42:09.420> about<01:42:09.600> that 01:42:09.950 --> 01:42:09.960 align:start position:0% how I personally I'm thinking about that 01:42:09.960 --> 01:42:17.510 align:start position:0% how I personally I'm thinking about that as<01:42:10.380> I<01:42:10.619> develop<01:42:11.040> an<01:42:11.880> EIP 01:42:17.510 --> 01:42:17.520 align:start position:0% 01:42:17.520 --> 01:42:22.490 align:start position:0% so<01:42:18.300> the<01:42:19.260> problem<01:42:19.500> at<01:42:19.800> hand<01:42:19.980> here<01:42:20.280> is<01:42:20.940> the<01:42:21.840> erc20 01:42:22.490 --> 01:42:22.500 align:start position:0% so the problem at hand here is the erc20 01:42:22.500 --> 01:42:26.030 align:start position:0% so the problem at hand here is the erc20 permits<01:42:23.280> anyone<01:42:24.119> that<01:42:24.300> has<01:42:24.540> used<01:42:24.719> a<01:42:25.020> amm<01:42:25.860> a 01:42:26.030 --> 01:42:26.040 align:start position:0% permits anyone that has used a amm a 01:42:26.040 --> 01:42:27.950 align:start position:0% permits anyone that has used a amm a decentralized<01:42:26.520> exchange<01:42:26.820> before<01:42:27.000> knows<01:42:27.780> that 01:42:27.950 --> 01:42:27.960 align:start position:0% decentralized exchange before knows that 01:42:27.960 --> 01:42:30.709 align:start position:0% decentralized exchange before knows that in<01:42:28.199> order<01:42:28.320> to<01:42:28.500> do<01:42:28.739> a<01:42:28.980> token<01:42:29.460> exchange<01:42:29.820> you<01:42:30.540> need 01:42:30.709 --> 01:42:30.719 align:start position:0% in order to do a token exchange you need 01:42:30.719 --> 01:42:34.010 align:start position:0% in order to do a token exchange you need to<01:42:31.460> approve<01:42:32.460> first<01:42:32.639> and<01:42:32.940> then<01:42:33.060> transfer<01:42:33.540> and 01:42:34.010 --> 01:42:34.020 align:start position:0% to approve first and then transfer and 01:42:34.020 --> 01:42:36.970 align:start position:0% to approve first and then transfer and this<01:42:34.380> EIP<01:42:35.300> permit 01:42:36.970 --> 01:42:36.980 align:start position:0% this EIP permit 01:42:36.980 --> 01:42:41.270 align:start position:0% this EIP permit is<01:42:37.980> one<01:42:38.340> way<01:42:38.520> of<01:42:39.619> foregoing<01:42:40.619> the<01:42:40.920> initial 01:42:41.270 --> 01:42:41.280 align:start position:0% is one way of foregoing the initial 01:42:41.280 --> 01:42:42.830 align:start position:0% is one way of foregoing the initial approved<01:42:41.760> transaction<01:42:42.060> and<01:42:42.360> replacing<01:42:42.719> it 01:42:42.830 --> 01:42:42.840 align:start position:0% approved transaction and replacing it 01:42:42.840 --> 01:42:44.629 align:start position:0% approved transaction and replacing it with<01:42:42.960> a<01:42:43.139> signature<01:42:43.619> that<01:42:44.100> allows<01:42:44.400> you<01:42:44.460> to 01:42:44.629 --> 01:42:44.639 align:start position:0% with a signature that allows you to 01:42:44.639 --> 01:42:46.850 align:start position:0% with a signature that allows you to allows<01:42:45.060> you<01:42:45.179> to<01:42:45.300> do<01:42:45.480> it<01:42:45.600> all<01:42:45.780> in<01:42:45.960> just<01:42:46.199> one 01:42:46.850 --> 01:42:46.860 align:start position:0% allows you to do it all in just one 01:42:46.860 --> 01:42:48.350 align:start position:0% allows you to do it all in just one transaction<01:42:47.219> by<01:42:47.580> just<01:42:47.760> including<01:42:48.179> the 01:42:48.350 --> 01:42:48.360 align:start position:0% transaction by just including the 01:42:48.360 --> 01:42:50.750 align:start position:0% transaction by just including the signature<01:42:48.780> in<01:42:49.139> the<01:42:49.320> first<01:42:49.440> transaction 01:42:50.750 --> 01:42:50.760 align:start position:0% signature in the first transaction 01:42:50.760 --> 01:42:52.570 align:start position:0% signature in the first transaction so 01:42:52.570 --> 01:42:52.580 align:start position:0% so 01:42:52.580 --> 01:42:55.609 align:start position:0% so this<01:42:53.580> saves<01:42:54.000> gas<01:42:54.179> it<01:42:54.840> is<01:42:55.199> one<01:42:55.440> less 01:42:55.609 --> 01:42:55.619 align:start position:0% this saves gas it is one less 01:42:55.619 --> 01:42:58.850 align:start position:0% this saves gas it is one less transactions<01:42:56.360> and<01:42:57.360> it<01:42:58.080> uses<01:42:58.440> the<01:42:58.560> signature 01:42:58.850 --> 01:42:58.860 align:start position:0% transactions and it uses the signature 01:42:58.860 --> 01:43:01.129 align:start position:0% transactions and it uses the signature instead<01:42:59.340> but<01:42:59.580> it's<01:43:00.060> kind<01:43:00.300> of<01:43:00.360> weird<01:43:00.600> if<01:43:00.960> you 01:43:01.129 --> 01:43:01.139 align:start position:0% instead but it's kind of weird if you 01:43:01.139 --> 01:43:04.070 align:start position:0% instead but it's kind of weird if you use<01:43:01.380> an<01:43:01.619> exchange<01:43:02.400> or<01:43:02.639> an<01:43:02.820> aggregator<01:43:03.300> you 01:43:04.070 --> 01:43:04.080 align:start position:0% use an exchange or an aggregator you 01:43:04.080 --> 01:43:05.510 align:start position:0% use an exchange or an aggregator you don't<01:43:04.199> really<01:43:04.380> see<01:43:04.560> this<01:43:04.739> being<01:43:04.980> used<01:43:05.219> very 01:43:05.510 --> 01:43:05.520 align:start position:0% don't really see this being used very 01:43:05.520 --> 01:43:08.810 align:start position:0% don't really see this being used very often<01:43:06.360> um<01:43:06.480> I<01:43:06.900> think<01:43:07.080> uh<01:43:07.619> main<01:43:07.860> maybe<01:43:08.219> it's<01:43:08.520> just 01:43:08.810 --> 01:43:08.820 align:start position:0% often um I think uh main maybe it's just 01:43:08.820 --> 01:43:12.109 align:start position:0% often um I think uh main maybe it's just for<01:43:08.940> like<01:43:09.179> usdc<01:43:10.080> uh<01:43:10.679> exchanges<01:43:11.219> supported<01:43:11.760> but 01:43:12.109 --> 01:43:12.119 align:start position:0% for like usdc uh exchanges supported but 01:43:12.119 --> 01:43:13.310 align:start position:0% for like usdc uh exchanges supported but there<01:43:12.239> are<01:43:12.360> many<01:43:12.420> other<01:43:12.600> tokens<01:43:12.960> that<01:43:13.139> have 01:43:13.310 --> 01:43:13.320 align:start position:0% there are many other tokens that have 01:43:13.320 --> 01:43:15.830 align:start position:0% there are many other tokens that have this<01:43:13.560> and<01:43:13.800> don't<01:43:14.040> so<01:43:14.699> the<01:43:15.300> question<01:43:15.540> that<01:43:15.659> was 01:43:15.830 --> 01:43:15.840 align:start position:0% this and don't so the question that was 01:43:15.840 --> 01:43:17.510 align:start position:0% this and don't so the question that was in<01:43:15.900> the<01:43:16.020> back<01:43:16.080> of<01:43:16.199> my<01:43:16.260> mind<01:43:16.440> is<01:43:16.560> like<01:43:16.800> why<01:43:17.340> is 01:43:17.510 --> 01:43:17.520 align:start position:0% in the back of my mind is like why is 01:43:17.520 --> 01:43:22.209 align:start position:0% in the back of my mind is like why is this<01:43:17.760> why<01:43:18.300> is<01:43:18.420> that<01:43:18.600> so<01:43:19.560> weird<01:43:19.739> so 01:43:22.209 --> 01:43:22.219 align:start position:0% this why is that so weird so 01:43:22.219 --> 01:43:28.010 align:start position:0% this why is that so weird so the<01:43:23.219> this<01:43:24.060> EIP<01:43:24.739> underneath<01:43:26.000> uses<01:43:27.000> uh<01:43:27.719> this 01:43:28.010 --> 01:43:28.020 align:start position:0% the this EIP underneath uses uh this 01:43:28.020 --> 01:43:32.450 align:start position:0% the this EIP underneath uses uh this other<01:43:28.139> EIP<01:43:28.619> 712 01:43:32.450 --> 01:43:32.460 align:start position:0% 01:43:32.460 --> 01:43:35.030 align:start position:0% which<01:43:32.880> is<01:43:32.940> a<01:43:33.179> special<01:43:33.360> kind<01:43:33.600> of<01:43:33.719> signature 01:43:35.030 --> 01:43:35.040 align:start position:0% which is a special kind of signature 01:43:35.040 --> 01:43:37.729 align:start position:0% which is a special kind of signature um it's<01:43:35.580> a<01:43:35.880> signature<01:43:36.360> not<01:43:36.659> of<01:43:36.840> a<01:43:37.080> blob<01:43:37.440> which 01:43:37.729 --> 01:43:37.739 align:start position:0% um it's a signature not of a blob which 01:43:37.739 --> 01:43:40.970 align:start position:0% um it's a signature not of a blob which is<01:43:37.860> what<01:43:38.040> we<01:43:38.280> see<01:43:39.179> uh<01:43:39.840> often<01:43:40.260> uh<01:43:40.800> most<01:43:40.920> most 01:43:40.970 --> 01:43:40.980 align:start position:0% is what we see uh often uh most most 01:43:40.980 --> 01:43:44.689 align:start position:0% is what we see uh often uh most most usually<01:43:41.760> but<01:43:42.659> of<01:43:42.780> a<01:43:43.020> kind<01:43:43.199> of<01:43:43.320> typed<01:43:43.739> data 01:43:44.689 --> 01:43:44.699 align:start position:0% usually but of a kind of typed data 01:43:44.699 --> 01:43:46.310 align:start position:0% usually but of a kind of typed data structure<01:43:45.060> so<01:43:45.420> it's<01:43:45.840> kind<01:43:45.960> of<01:43:46.080> important 01:43:46.310 --> 01:43:46.320 align:start position:0% structure so it's kind of important 01:43:46.320 --> 01:43:47.390 align:start position:0% structure so it's kind of important because<01:43:46.500> it<01:43:46.679> allows<01:43:46.920> you<01:43:46.980> to<01:43:47.100> give<01:43:47.219> more 01:43:47.390 --> 01:43:47.400 align:start position:0% because it allows you to give more 01:43:47.400 --> 01:43:49.310 align:start position:0% because it allows you to give more structure<01:43:47.820> to<01:43:48.000> it<01:43:48.119> in<01:43:48.600> the<01:43:48.719> case<01:43:48.780> of<01:43:48.960> permit 01:43:49.310 --> 01:43:49.320 align:start position:0% structure to it in the case of permit 01:43:49.320 --> 01:43:51.290 align:start position:0% structure to it in the case of permit you<01:43:49.500> will<01:43:49.619> include<01:43:49.980> the<01:43:50.639> amount<01:43:50.880> that<01:43:51.179> you're 01:43:51.290 --> 01:43:51.300 align:start position:0% you will include the amount that you're 01:43:51.300 --> 01:43:52.490 align:start position:0% you will include the amount that you're allowing 01:43:52.490 --> 01:43:52.500 align:start position:0% allowing 01:43:52.500 --> 01:43:55.250 align:start position:0% allowing um<01:43:52.560> you<01:43:52.980> will<01:43:53.100> include<01:43:53.400> and<01:43:54.000> expires<01:43:54.600> uh 01:43:55.250 --> 01:43:55.260 align:start position:0% um you will include and expires uh 01:43:55.260 --> 01:43:58.910 align:start position:0% um you will include and expires uh timestamp<01:43:56.100> and<01:43:56.460> a<01:43:56.580> nouns<01:43:56.940> and<01:43:57.179> so<01:43:57.300> on<01:43:57.840> and<01:43:58.560> this 01:43:58.910 --> 01:43:58.920 align:start position:0% timestamp and a nouns and so on and this 01:43:58.920 --> 01:44:00.590 align:start position:0% timestamp and a nouns and so on and this is<01:43:59.040> an<01:43:59.159> important<01:43:59.520> uh<01:43:59.880> standard<01:44:00.300> because 01:44:00.590 --> 01:44:00.600 align:start position:0% is an important uh standard because 01:44:00.600 --> 01:44:03.290 align:start position:0% is an important uh standard because wallets<01:44:01.500> can<01:44:01.739> Implement<01:44:02.159> support<01:44:02.460> for<01:44:02.880> it<01:44:03.000> and 01:44:03.290 --> 01:44:03.300 align:start position:0% wallets can Implement support for it and 01:44:03.300 --> 01:44:05.629 align:start position:0% wallets can Implement support for it and show<01:44:03.480> this<01:44:03.780> structured<01:44:04.199> data<01:44:04.560> to<01:44:04.920> the<01:44:05.100> user<01:44:05.400> in 01:44:05.629 --> 01:44:05.639 align:start position:0% show this structured data to the user in 01:44:05.639 --> 01:44:07.490 align:start position:0% show this structured data to the user in a<01:44:05.760> nice<01:44:05.880> way<01:44:06.119> one<01:44:06.840> of<01:44:06.960> the<01:44:07.020> important<01:44:07.320> things 01:44:07.490 --> 01:44:07.500 align:start position:0% a nice way one of the important things 01:44:07.500 --> 01:44:10.070 align:start position:0% a nice way one of the important things in<01:44:07.739> these<01:44:07.980> EAP 01:44:10.070 --> 01:44:10.080 align:start position:0% in these EAP 01:44:10.080 --> 01:44:15.169 align:start position:0% in these EAP is<01:44:10.800> the<01:44:11.460> notion<01:44:11.940> of<01:44:12.300> a<01:44:12.920> domains<01:44:13.920> so<01:44:14.520> when<01:44:15.000> you 01:44:15.169 --> 01:44:15.179 align:start position:0% is the notion of a domains so when you 01:44:15.179 --> 01:44:18.050 align:start position:0% is the notion of a domains so when you make<01:44:15.420> an<01:44:15.600> approval<01:44:16.020> for<01:44:16.380> say<01:44:16.619> usdc<01:44:17.460> you<01:44:17.940> don't 01:44:18.050 --> 01:44:18.060 align:start position:0% make an approval for say usdc you don't 01:44:18.060 --> 01:44:19.729 align:start position:0% make an approval for say usdc you don't want<01:44:18.179> an<01:44:18.360> attacker<01:44:18.780> to<01:44:18.900> take<01:44:19.020> that<01:44:19.260> signature 01:44:19.729 --> 01:44:19.739 align:start position:0% want an attacker to take that signature 01:44:19.739 --> 01:44:22.850 align:start position:0% want an attacker to take that signature and<01:44:20.280> kind<01:44:20.460> of<01:44:20.520> send<01:44:21.060> it<01:44:21.239> to<01:44:21.600> die<01:44:21.960> right<01:44:22.440> you 01:44:22.850 --> 01:44:22.860 align:start position:0% and kind of send it to die right you 01:44:22.860 --> 01:44:24.709 align:start position:0% and kind of send it to die right you don't<01:44:22.980> want<01:44:23.100> an<01:44:23.400> attacker<01:44:23.760> to<01:44:24.000> reuse<01:44:24.540> the 01:44:24.709 --> 01:44:24.719 align:start position:0% don't want an attacker to reuse the 01:44:24.719 --> 01:44:26.629 align:start position:0% don't want an attacker to reuse the signature<01:44:25.080> in<01:44:25.320> a<01:44:25.440> different<01:44:25.560> domain<01:44:26.040> so<01:44:26.400> every 01:44:26.629 --> 01:44:26.639 align:start position:0% signature in a different domain so every 01:44:26.639 --> 01:44:29.270 align:start position:0% signature in a different domain so every signature<01:44:27.179> has<01:44:27.480> this<01:44:27.840> domain<01:44:28.679> separator 01:44:29.270 --> 01:44:29.280 align:start position:0% signature has this domain separator 01:44:29.280 --> 01:44:31.490 align:start position:0% signature has this domain separator inside<01:44:29.639> of<01:44:29.940> it<01:44:30.060> that<01:44:30.780> makes<01:44:30.960> sure<01:44:31.139> that<01:44:31.320> the 01:44:31.490 --> 01:44:31.500 align:start position:0% inside of it that makes sure that the 01:44:31.500 --> 01:44:35.689 align:start position:0% inside of it that makes sure that the signature<01:44:31.860> is<01:44:31.980> only<01:44:32.100> valid<01:44:32.520> in<01:44:32.760> one<01:44:32.940> domain<01:44:33.840> so 01:44:35.689 --> 01:44:35.699 align:start position:0% signature is only valid in one domain so 01:44:35.699 --> 01:44:38.149 align:start position:0% signature is only valid in one domain so this<01:44:36.600> is<01:44:36.900> the 01:44:38.149 --> 01:44:38.159 align:start position:0% this is the 01:44:38.159 --> 01:44:40.790 align:start position:0% this is the um<01:44:38.360> right<01:44:39.360> so<01:44:39.719> the<01:44:39.960> decentralized<01:44:40.619> exchange 01:44:40.790 --> 01:44:40.800 align:start position:0% um right so the decentralized exchange 01:44:40.800 --> 01:44:43.490 align:start position:0% um right so the decentralized exchange has<01:44:41.159> no<01:44:41.460> way<01:44:41.699> of<01:44:42.119> knowing 01:44:43.490 --> 01:44:43.500 align:start position:0% has no way of knowing 01:44:43.500 --> 01:44:45.590 align:start position:0% has no way of knowing um<01:44:43.560> given<01:44:43.980> some<01:44:44.280> arbitrary<01:44:44.760> token<01:44:45.239> what 01:44:45.590 --> 01:44:45.600 align:start position:0% um given some arbitrary token what 01:44:45.600 --> 01:44:48.109 align:start position:0% um given some arbitrary token what domain<01:44:46.020> they<01:44:46.260> want<01:44:46.619> to<01:44:46.739> use 01:44:48.109 --> 01:44:48.119 align:start position:0% domain they want to use 01:44:48.119 --> 01:44:50.570 align:start position:0% domain they want to use um<01:44:48.179> and<01:44:48.659> I<01:44:49.619> think 01:44:50.570 --> 01:44:50.580 align:start position:0% um and I think 01:44:50.580 --> 01:44:54.290 align:start position:0% um and I think yeah<01:44:51.119> I<01:44:51.840> think<01:44:52.020> that<01:44:52.500> is<01:44:52.619> the<01:44:52.920> reason<01:44:53.159> why<01:44:53.760> this 01:44:54.290 --> 01:44:54.300 align:start position:0% yeah I think that is the reason why this 01:44:54.300 --> 01:44:56.930 align:start position:0% yeah I think that is the reason why this hasn't<01:44:54.659> been<01:44:54.840> really<01:44:55.260> adopted<01:44:55.920> so<01:44:56.460> you<01:44:56.820> will 01:44:56.930 --> 01:44:56.940 align:start position:0% hasn't been really adopted so you will 01:44:56.940 --> 01:44:58.189 align:start position:0% hasn't been really adopted so you will see<01:44:57.239> that 01:44:58.189 --> 01:44:58.199 align:start position:0% see that 01:44:58.199 --> 01:45:01.850 align:start position:0% see that um the<01:44:58.440> erc20<01:44:59.040> permit<01:44:59.580> ERC<01:45:00.320> defines<01:45:01.320> a<01:45:01.500> getter 01:45:01.850 --> 01:45:01.860 align:start position:0% um the erc20 permit ERC defines a getter 01:45:01.860 --> 01:45:04.310 align:start position:0% um the erc20 permit ERC defines a getter that<01:45:02.040> gives<01:45:02.219> you<01:45:02.400> the<01:45:02.639> hash<01:45:02.880> but<01:45:03.600> really<01:45:03.840> the 01:45:04.310 --> 01:45:04.320 align:start position:0% that gives you the hash but really the 01:45:04.320 --> 01:45:08.209 align:start position:0% that gives you the hash but really the 712<01:45:05.760> RPC<01:45:06.659> endpoint<01:45:07.080> requires<01:45:07.739> the<01:45:07.920> entire 01:45:08.209 --> 01:45:08.219 align:start position:0% 712 RPC endpoint requires the entire 01:45:08.219 --> 01:45:10.669 align:start position:0% 712 RPC endpoint requires the entire domain<01:45:08.699> object<01:45:09.060> and<01:45:09.540> there<01:45:09.960> is<01:45:10.080> really<01:45:10.199> no<01:45:10.440> way 01:45:10.669 --> 01:45:10.679 align:start position:0% domain object and there is really no way 01:45:10.679 --> 01:45:15.430 align:start position:0% domain object and there is really no way to<01:45:10.980> find<01:45:11.760> it<01:45:12.000> here<01:45:12.199> so<01:45:13.199> this<01:45:13.920> is<01:45:14.100> where 01:45:15.430 --> 01:45:15.440 align:start position:0% to find it here so this is where 01:45:15.440 --> 01:45:18.410 align:start position:0% to find it here so this is where eip5267<01:45:16.440> comes<01:45:17.280> in 01:45:18.410 --> 01:45:18.420 align:start position:0% eip5267 comes in 01:45:18.420 --> 01:45:20.149 align:start position:0% eip5267 comes in um now 01:45:20.149 --> 01:45:20.159 align:start position:0% um now 01:45:20.159 --> 01:45:22.189 align:start position:0% um now we<01:45:20.580> will<01:45:20.699> see<01:45:20.880> now<01:45:21.119> it's<01:45:21.480> a<01:45:21.719> very<01:45:21.900> simple 01:45:22.189 --> 01:45:22.199 align:start position:0% we will see now it's a very simple 01:45:22.199 --> 01:45:25.310 align:start position:0% we will see now it's a very simple function<01:45:23.060> that<01:45:24.060> literally<01:45:24.480> just<01:45:24.840> allows<01:45:25.260> you 01:45:25.310 --> 01:45:25.320 align:start position:0% function that literally just allows you 01:45:25.320 --> 01:45:28.490 align:start position:0% function that literally just allows you to<01:45:25.500> obtain<01:45:25.920> the<01:45:26.280> domain<01:45:26.840> this<01:45:27.840> is<01:45:27.960> the<01:45:28.139> domain 01:45:28.490 --> 01:45:28.500 align:start position:0% to obtain the domain this is the domain 01:45:28.500 --> 01:45:30.109 align:start position:0% to obtain the domain this is the domain object<01:45:28.800> that<01:45:28.980> you<01:45:29.159> will<01:45:29.219> need<01:45:29.400> to<01:45:29.520> pass<01:45:29.699> into 01:45:30.109 --> 01:45:30.119 align:start position:0% object that you will need to pass into 01:45:30.119 --> 01:45:35.030 align:start position:0% object that you will need to pass into the<01:45:30.600> 712<01:45:31.440> sign<01:45:32.219> RPC<01:45:32.880> call<01:45:33.380> and<01:45:34.380> and<01:45:34.500> as<01:45:34.800> you<01:45:34.980> can 01:45:35.030 --> 01:45:35.040 align:start position:0% the 712 sign RPC call and and as you can 01:45:35.040 --> 01:45:39.530 align:start position:0% the 712 sign RPC call and and as you can see<01:45:35.159> like<01:45:35.580> it's<01:45:36.139> extremely<01:45:37.139> simple<01:45:37.380> now 01:45:39.530 --> 01:45:39.540 align:start position:0% see like it's extremely simple now 01:45:39.540 --> 01:45:41.570 align:start position:0% see like it's extremely simple now what<01:45:40.020> was<01:45:40.260> also<01:45:40.500> at<01:45:40.679> the<01:45:40.860> back<01:45:40.920> of<01:45:41.100> my<01:45:41.219> mind<01:45:41.340> is 01:45:41.570 --> 01:45:41.580 align:start position:0% what was also at the back of my mind is 01:45:41.580 --> 01:45:44.390 align:start position:0% what was also at the back of my mind is that<01:45:41.880> this<01:45:42.600> was<01:45:42.780> this<01:45:43.199> is<01:45:43.380> not<01:45:43.560> also<01:45:43.800> a<01:45:44.040> failure 01:45:44.390 --> 01:45:44.400 align:start position:0% that this was this is not also a failure 01:45:44.400 --> 01:45:49.010 align:start position:0% that this was this is not also a failure of<01:45:44.699> the<01:45:45.000> spec<01:45:45.300> uh<01:45:46.199> 12<01:45:46.580> 2612<01:45:47.580> so<01:45:48.000> permit<01:45:48.480> but<01:45:48.900> it 01:45:49.010 --> 01:45:49.020 align:start position:0% of the spec uh 12 2612 so permit but it 01:45:49.020 --> 01:45:50.450 align:start position:0% of the spec uh 12 2612 so permit but it was<01:45:49.139> also<01:45:49.380> in<01:45:49.500> a<01:45:49.679> way<01:45:49.739> of<01:45:49.920> failure<01:45:50.159> of<01:45:50.340> the 01:45:50.450 --> 01:45:50.460 align:start position:0% was also in a way of failure of the 01:45:50.460 --> 01:45:53.750 align:start position:0% was also in a way of failure of the process<01:45:50.820> because<01:45:51.420> if<01:45:52.020> the<01:45:52.320> 2612<01:45:53.100> authors<01:45:53.460> had 01:45:53.750 --> 01:45:53.760 align:start position:0% process because if the 2612 authors had 01:45:53.760 --> 01:45:55.850 align:start position:0% process because if the 2612 authors had kind<01:45:54.000> of<01:45:54.119> gone<01:45:54.600> all<01:45:54.840> the<01:45:55.020> way<01:45:55.080> and<01:45:55.560> kind<01:45:55.739> of 01:45:55.850 --> 01:45:55.860 align:start position:0% kind of gone all the way and kind of 01:45:55.860 --> 01:45:58.370 align:start position:0% kind of gone all the way and kind of talked<01:45:56.280> to<01:45:56.780> decentralized<01:45:57.780> exchanges<01:45:58.199> and 01:45:58.370 --> 01:45:58.380 align:start position:0% talked to decentralized exchanges and 01:45:58.380 --> 01:46:00.350 align:start position:0% talked to decentralized exchanges and thought<01:45:58.560> through<01:45:58.800> uh<01:45:59.280> what<01:45:59.639> it<01:45:59.880> would<01:46:00.060> entail 01:46:00.350 --> 01:46:00.360 align:start position:0% thought through uh what it would entail 01:46:00.360 --> 01:46:02.209 align:start position:0% thought through uh what it would entail to<01:46:00.600> adopt<01:46:01.139> that<01:46:01.199> they<01:46:01.619> would<01:46:01.739> have<01:46:01.920> realized 01:46:02.209 --> 01:46:02.219 align:start position:0% to adopt that they would have realized 01:46:02.219 --> 01:46:04.370 align:start position:0% to adopt that they would have realized that<01:46:02.400> this<01:46:02.639> was<01:46:02.820> missing<01:46:03.179> so<01:46:03.600> I<01:46:04.020> didn't<01:46:04.139> only 01:46:04.370 --> 01:46:04.380 align:start position:0% that this was missing so I didn't only 01:46:04.380 --> 01:46:06.109 align:start position:0% that this was missing so I didn't only want<01:46:04.679> to<01:46:04.860> tackle<01:46:05.280> the<01:46:05.520> technical<01:46:05.820> problem 01:46:06.109 --> 01:46:06.119 align:start position:0% want to tackle the technical problem 01:46:06.119 --> 01:46:08.450 align:start position:0% want to tackle the technical problem here<01:46:06.420> but<01:46:06.719> also<01:46:06.960> think<01:46:07.139> about 01:46:08.450 --> 01:46:08.460 align:start position:0% here but also think about 01:46:08.460 --> 01:46:12.169 align:start position:0% here but also think about how<01:46:09.119> can<01:46:09.300> I<01:46:09.619> uh<01:46:10.619> carry<01:46:11.340> out<01:46:11.520> the<01:46:11.760> process<01:46:12.000> for 01:46:12.169 --> 01:46:12.179 align:start position:0% how can I uh carry out the process for 01:46:12.179 --> 01:46:15.649 align:start position:0% how can I uh carry out the process for the<01:46:12.300> CIP<01:46:12.600> to<01:46:13.020> make<01:46:13.139> sure<01:46:13.320> and<01:46:13.739> other<01:46:14.520> erc's<01:46:15.300> to 01:46:15.649 --> 01:46:15.659 align:start position:0% the CIP to make sure and other erc's to 01:46:15.659 --> 01:46:17.629 align:start position:0% the CIP to make sure and other erc's to make<01:46:15.840> sure<01:46:16.020> that<01:46:16.320> the<01:46:16.679> sort<01:46:16.860> of<01:46:17.040> failure<01:46:17.520> of 01:46:17.629 --> 01:46:17.639 align:start position:0% make sure that the sort of failure of 01:46:17.639 --> 01:46:22.030 align:start position:0% make sure that the sort of failure of the<01:46:17.760> process<01:46:18.000> doesn't<01:46:18.360> present<01:46:18.780> itself 01:46:22.030 --> 01:46:22.040 align:start position:0% 01:46:22.040 --> 01:46:25.609 align:start position:0% so<01:46:23.040> the<01:46:23.639> question<01:46:23.820> is<01:46:24.060> how<01:46:24.960> do<01:46:25.080> we<01:46:25.260> get<01:46:25.380> this 01:46:25.609 --> 01:46:25.619 align:start position:0% so the question is how do we get this 01:46:25.619 --> 01:46:28.609 align:start position:0% so the question is how do we get this now<01:46:25.860> which<01:46:26.460> is<01:46:26.639> in<01:46:26.880> a<01:46:27.119> review<01:46:27.360> stage<01:46:27.900> how<01:46:28.380> do<01:46:28.500> we 01:46:28.609 --> 01:46:28.619 align:start position:0% now which is in a review stage how do we 01:46:28.619 --> 01:46:30.470 align:start position:0% now which is in a review stage how do we get<01:46:28.739> it<01:46:28.860> now<01:46:28.980> to<01:46:29.219> final<01:46:29.460> what<01:46:29.940> needs<01:46:30.179> to<01:46:30.300> happen 01:46:30.470 --> 01:46:30.480 align:start position:0% get it now to final what needs to happen 01:46:30.480 --> 01:46:33.109 align:start position:0% get it now to final what needs to happen in<01:46:30.900> order<01:46:31.020> to<01:46:31.199> get<01:46:31.320> it<01:46:31.500> to<01:46:31.560> final<01:46:31.739> so<01:46:32.520> some<01:46:33.000> of 01:46:33.109 --> 01:46:33.119 align:start position:0% in order to get it to final so some of 01:46:33.119 --> 01:46:34.550 align:start position:0% in order to get it to final so some of the<01:46:33.179> things<01:46:33.300> that<01:46:33.480> I've<01:46:33.600> done 01:46:34.550 --> 01:46:34.560 align:start position:0% the things that I've done 01:46:34.560 --> 01:46:36.770 align:start position:0% the things that I've done um<01:46:34.619> and<01:46:34.800> that<01:46:34.980> I<01:46:35.280> would<01:46:35.520> recommend<01:46:36.000> you<01:46:36.420> all<01:46:36.540> do 01:46:36.770 --> 01:46:36.780 align:start position:0% um and that I would recommend you all do 01:46:36.780 --> 01:46:39.050 align:start position:0% um and that I would recommend you all do when<01:46:37.080> you<01:46:37.260> build<01:46:37.500> your<01:46:37.860> VIPs 01:46:39.050 --> 01:46:39.060 align:start position:0% when you build your VIPs 01:46:39.060 --> 01:46:40.550 align:start position:0% when you build your VIPs um<01:46:39.179> so<01:46:39.540> you<01:46:39.780> should<01:46:39.840> reach<01:46:40.139> out<01:46:40.199> to<01:46:40.380> all 01:46:40.550 --> 01:46:40.560 align:start position:0% um so you should reach out to all 01:46:40.560 --> 01:46:43.129 align:start position:0% um so you should reach out to all interested<01:46:41.040> parties<01:46:41.520> and<01:46:41.880> like<01:46:42.139> applications 01:46:43.129 --> 01:46:43.139 align:start position:0% interested parties and like applications 01:46:43.139 --> 01:46:46.189 align:start position:0% interested parties and like applications and<01:46:43.619> companies<01:46:44.100> and<01:46:44.940> uh<01:46:45.540> projects<01:46:45.900> that<01:46:46.080> you 01:46:46.189 --> 01:46:46.199 align:start position:0% and companies and uh projects that you 01:46:46.199 --> 01:46:48.290 align:start position:0% and companies and uh projects that you think<01:46:46.320> will<01:46:46.500> be<01:46:46.619> using<01:46:46.980> this<01:46:47.159> and<01:46:47.820> really<01:46:48.000> you 01:46:48.290 --> 01:46:48.300 align:start position:0% think will be using this and really you 01:46:48.300 --> 01:46:50.629 align:start position:0% think will be using this and really you should<01:46:48.480> be<01:46:48.600> kind<01:46:48.900> of<01:46:49.100> bothering<01:46:50.100> them<01:46:50.280> to<01:46:50.520> give 01:46:50.629 --> 01:46:50.639 align:start position:0% should be kind of bothering them to give 01:46:50.639 --> 01:46:52.129 align:start position:0% should be kind of bothering them to give you<01:46:50.820> feedback<01:46:51.179> to<01:46:51.420> look<01:46:51.540> at<01:46:51.659> it<01:46:51.780> and<01:46:51.840> give<01:46:52.020> you 01:46:52.129 --> 01:46:52.139 align:start position:0% you feedback to look at it and give you 01:46:52.139 --> 01:46:54.410 align:start position:0% you feedback to look at it and give you feedback<01:46:52.500> so<01:46:53.040> I've<01:46:53.159> reached<01:46:53.520> out<01:46:53.639> to<01:46:53.820> uh<01:46:54.179> one 01:46:54.410 --> 01:46:54.420 align:start position:0% feedback so I've reached out to uh one 01:46:54.420 --> 01:46:57.050 align:start position:0% feedback so I've reached out to uh one inch<01:46:54.780> and<01:46:54.960> unit<01:46:55.139> Swap<01:46:55.560> and<01:46:55.739> kind<01:46:55.920> of<01:46:56.040> seen<01:46:56.400> try 01:46:57.050 --> 01:46:57.060 align:start position:0% inch and unit Swap and kind of seen try 01:46:57.060 --> 01:46:59.270 align:start position:0% inch and unit Swap and kind of seen try to<01:46:57.239> get<01:46:57.360> from<01:46:57.659> them<01:46:57.900> is<01:46:58.500> this<01:46:58.619> useful<01:46:58.980> to<01:46:59.159> you 01:46:59.270 --> 01:46:59.280 align:start position:0% to get from them is this useful to you 01:46:59.280 --> 01:47:01.129 align:start position:0% to get from them is this useful to you would<01:46:59.520> it<01:46:59.699> does<01:47:00.179> this<01:47:00.300> solve<01:47:00.600> a<01:47:00.659> real<01:47:00.780> problem 01:47:01.129 --> 01:47:01.139 align:start position:0% would it does this solve a real problem 01:47:01.139 --> 01:47:04.189 align:start position:0% would it does this solve a real problem from<01:47:01.500> for<01:47:01.800> you 01:47:04.189 --> 01:47:04.199 align:start position:0% 01:47:04.199 --> 01:47:06.350 align:start position:0% um<01:47:04.320> and<01:47:04.920> generally<01:47:05.460> the<01:47:05.760> answer<01:47:05.880> in<01:47:06.060> this<01:47:06.239> case 01:47:06.350 --> 01:47:06.360 align:start position:0% um and generally the answer in this case 01:47:06.360 --> 01:47:08.030 align:start position:0% um and generally the answer in this case has<01:47:06.600> been<01:47:06.719> yes 01:47:08.030 --> 01:47:08.040 align:start position:0% has been yes 01:47:08.040 --> 01:47:11.090 align:start position:0% has been yes um<01:47:08.239> in<01:47:09.239> the<01:47:09.540> ethereum<01:47:10.320> magician<01:47:10.739> threat 01:47:11.090 --> 01:47:11.100 align:start position:0% um in the ethereum magician threat 01:47:11.100 --> 01:47:12.470 align:start position:0% um in the ethereum magician threat there's<01:47:11.340> also<01:47:11.639> been<01:47:11.820> a<01:47:12.239> couple<01:47:12.360> of 01:47:12.470 --> 01:47:12.480 align:start position:0% there's also been a couple of 01:47:12.480 --> 01:47:13.970 align:start position:0% there's also been a couple of interesting<01:47:12.960> comments<01:47:13.380> and<01:47:13.679> common 01:47:13.970 --> 01:47:13.980 align:start position:0% interesting comments and common 01:47:13.980 --> 01:47:15.950 align:start position:0% interesting comments and common questions<01:47:14.340> I<01:47:15.060> have<01:47:15.239> taken<01:47:15.540> some<01:47:15.719> of<01:47:15.840> the 01:47:15.950 --> 01:47:15.960 align:start position:0% questions I have taken some of the 01:47:15.960 --> 01:47:17.689 align:start position:0% questions I have taken some of the questions<01:47:16.139> and<01:47:16.500> documented<01:47:17.040> them<01:47:17.159> as<01:47:17.400> part<01:47:17.580> of 01:47:17.689 --> 01:47:17.699 align:start position:0% questions and documented them as part of 01:47:17.699 --> 01:47:21.890 align:start position:0% questions and documented them as part of the<01:47:17.820> EIP<01:47:18.119> as<01:47:18.540> well<01:47:18.980> and<01:47:19.980> also<01:47:20.219> some<01:47:20.460> concerns 01:47:21.890 --> 01:47:21.900 align:start position:0% the EIP as well and also some concerns 01:47:21.900 --> 01:47:25.070 align:start position:0% the EIP as well and also some concerns that<01:47:22.320> have<01:47:22.440> arised<01:47:22.980> uh 01:47:25.070 --> 01:47:25.080 align:start position:0% that have arised uh 01:47:25.080 --> 01:47:28.189 align:start position:0% that have arised uh so<01:47:25.560> many<01:47:26.460> of<01:47:26.639> those<01:47:26.820> concerns<01:47:27.420> in<01:47:27.780> the<01:47:27.900> case<01:47:28.020> of 01:47:28.189 --> 01:47:28.199 align:start position:0% so many of those concerns in the case of 01:47:28.199 --> 01:47:31.810 align:start position:0% so many of those concerns in the case of this<01:47:28.380> eifb<01:47:29.040> were<01:47:29.639> about<01:47:30.000> the 01:47:31.810 --> 01:47:31.820 align:start position:0% this eifb were about the 01:47:31.820 --> 01:47:35.209 align:start position:0% this eifb were about the backwards<01:47:32.820> compatibility<01:47:33.420> uh 01:47:35.209 --> 01:47:35.219 align:start position:0% backwards compatibility uh 01:47:35.219 --> 01:47:39.530 align:start position:0% backwards compatibility uh section<01:47:35.960> which<01:47:36.960> is<01:47:37.260> here<01:47:37.500> but<01:47:38.520> um 01:47:39.530 --> 01:47:39.540 align:start position:0% section which is here but um 01:47:39.540 --> 01:47:41.450 align:start position:0% section which is here but um most<01:47:40.320> of<01:47:40.440> the<01:47:40.560> discussion<01:47:40.860> of<01:47:41.040> The<01:47:41.159> ethereum 01:47:41.450 --> 01:47:41.460 align:start position:0% most of the discussion of The ethereum 01:47:41.460 --> 01:47:43.609 align:start position:0% most of the discussion of The ethereum Magicians<01:47:41.940> threat<01:47:42.239> made<01:47:42.600> me<01:47:42.719> realize<01:47:43.199> that 01:47:43.609 --> 01:47:43.619 align:start position:0% Magicians threat made me realize that 01:47:43.619 --> 01:47:45.830 align:start position:0% Magicians threat made me realize that even<01:47:44.280> though<01:47:44.520> I<01:47:44.699> wrote<01:47:44.940> this<01:47:45.119> section<01:47:45.360> kind<01:47:45.719> of 01:47:45.830 --> 01:47:45.840 align:start position:0% even though I wrote this section kind of 01:47:45.840 --> 01:47:47.510 align:start position:0% even though I wrote this section kind of thought<01:47:45.960> about<01:47:46.139> it<01:47:46.380> there<01:47:46.800> really<01:47:46.980> are<01:47:47.219> many 01:47:47.510 --> 01:47:47.520 align:start position:0% thought about it there really are many 01:47:47.520 --> 01:47:49.910 align:start position:0% thought about it there really are many more<01:47:47.880> unanswered<01:47:48.719> questions<01:47:48.960> so<01:47:49.500> I<01:47:49.619> wanted<01:47:49.739> to 01:47:49.910 --> 01:47:49.920 align:start position:0% more unanswered questions so I wanted to 01:47:49.920 --> 01:47:53.149 align:start position:0% more unanswered questions so I wanted to do<01:47:50.040> some<01:47:50.219> more<01:47:50.460> work<01:47:50.639> to<01:47:51.540> figure<01:47:51.900> out<01:47:52.260> the<01:47:52.920> real 01:47:53.149 --> 01:47:53.159 align:start position:0% do some more work to figure out the real 01:47:53.159 --> 01:47:55.490 align:start position:0% do some more work to figure out the real backward<01:47:54.060> compatibility<01:47:54.540> story<01:47:54.840> so<01:47:55.139> another 01:47:55.490 --> 01:47:55.500 align:start position:0% backward compatibility story so another 01:47:55.500 --> 01:47:57.470 align:start position:0% backward compatibility story so another another<01:47:56.340> thing<01:47:56.639> that<01:47:56.820> I've<01:47:56.940> started<01:47:57.239> doing 01:47:57.470 --> 01:47:57.480 align:start position:0% another thing that I've started doing 01:47:57.480 --> 01:47:59.149 align:start position:0% another thing that I've started doing which<01:47:57.960> I<01:47:58.080> think<01:47:58.199> is<01:47:58.320> a<01:47:58.500> really<01:47:58.619> good<01:47:58.800> exercise 01:47:59.149 --> 01:47:59.159 align:start position:0% which I think is a really good exercise 01:47:59.159 --> 01:48:03.410 align:start position:0% which I think is a really good exercise is<01:48:00.119> to<01:48:00.540> implement<01:48:01.139> it<01:48:01.580> and<01:48:02.580> not<01:48:02.760> only<01:48:02.940> like<01:48:03.239> the 01:48:03.410 --> 01:48:03.420 align:start position:0% is to implement it and not only like the 01:48:03.420 --> 01:48:05.750 align:start position:0% is to implement it and not only like the solidity<01:48:03.900> part<01:48:04.080> of<01:48:04.260> it<01:48:04.380> but<01:48:04.980> also<01:48:05.280> the<01:48:05.580> many 01:48:05.750 --> 01:48:05.760 align:start position:0% solidity part of it but also the many 01:48:05.760 --> 01:48:09.770 align:start position:0% solidity part of it but also the many parts<01:48:05.940> of<01:48:06.179> the<01:48:06.300> stack<01:48:06.480> again<01:48:06.840> so<01:48:07.679> I've<01:48:08.340> just 01:48:09.770 --> 01:48:09.780 align:start position:0% parts of the stack again so I've just 01:48:09.780 --> 01:48:13.370 align:start position:0% parts of the stack again so I've just uh<01:48:10.619> started<01:48:11.040> this<01:48:11.219> EI<01:48:11.639> uh<01:48:12.119> repository<01:48:12.900> with 01:48:13.370 --> 01:48:13.380 align:start position:0% uh started this EI uh repository with 01:48:13.380 --> 01:48:15.910 align:start position:0% uh started this EI uh repository with the<01:48:13.560> implementation<01:48:14.159> and<01:48:15.119> most<01:48:15.420> importantly 01:48:15.910 --> 01:48:15.920 align:start position:0% the implementation and most importantly 01:48:15.920 --> 01:48:19.310 align:start position:0% the implementation and most importantly a<01:48:16.920> little<01:48:17.159> app<01:48:17.639> which<01:48:18.360> is<01:48:18.480> just<01:48:18.719> a<01:48:18.960> front-end 01:48:19.310 --> 01:48:19.320 align:start position:0% a little app which is just a front-end 01:48:19.320 --> 01:48:22.490 align:start position:0% a little app which is just a front-end app<01:48:19.679> which<01:48:20.040> is<01:48:20.159> what<01:48:20.460> I<01:48:20.760> imagine 01:48:22.490 --> 01:48:22.500 align:start position:0% app which is what I imagine 01:48:22.500 --> 01:48:25.550 align:start position:0% app which is what I imagine that<01:48:23.400> a<01:48:24.060> the<01:48:24.239> central<01:48:24.420> X<01:48:24.659> exchange<01:48:25.020> will<01:48:25.320> kind 01:48:25.550 --> 01:48:25.560 align:start position:0% that a the central X exchange will kind 01:48:25.560 --> 01:48:27.530 align:start position:0% that a the central X exchange will kind of<01:48:25.619> be<01:48:25.739> doing<01:48:25.920> behind<01:48:26.400> the<01:48:26.520> scenes<01:48:26.820> and<01:48:27.300> here 01:48:27.530 --> 01:48:27.540 align:start position:0% of be doing behind the scenes and here 01:48:27.540 --> 01:48:29.689 align:start position:0% of be doing behind the scenes and here I'm<01:48:27.659> putting<01:48:27.960> myself<01:48:28.080> in<01:48:28.320> the<01:48:28.440> shoes<01:48:28.619> of 01:48:29.689 --> 01:48:29.699 align:start position:0% I'm putting myself in the shoes of 01:48:29.699 --> 01:48:32.689 align:start position:0% I'm putting myself in the shoes of I<01:48:30.360> am<01:48:30.540> the<01:48:31.199> UI<01:48:31.619> for<01:48:31.800> one<01:48:31.980> inch<01:48:32.340> and<01:48:32.460> this<01:48:32.639> is 01:48:32.689 --> 01:48:32.699 align:start position:0% I am the UI for one inch and this is 01:48:32.699 --> 01:48:34.669 align:start position:0% I am the UI for one inch and this is what<01:48:32.880> I'm<01:48:33.000> going<01:48:33.119> to<01:48:33.179> be<01:48:33.300> doing<01:48:33.420> and<01:48:34.199> just<01:48:34.440> kind 01:48:34.669 --> 01:48:34.679 align:start position:0% what I'm going to be doing and just kind 01:48:34.679 --> 01:48:37.669 align:start position:0% what I'm going to be doing and just kind of<01:48:34.800> really<01:48:35.280> figuring<01:48:35.880> out<01:48:36.060> if<01:48:36.480> it<01:48:36.659> works<01:48:37.020> if<01:48:37.500> I 01:48:37.669 --> 01:48:37.679 align:start position:0% of really figuring out if it works if I 01:48:37.679 --> 01:48:39.350 align:start position:0% of really figuring out if it works if I can<01:48:37.860> actually<01:48:38.040> produce<01:48:38.520> the<01:48:38.699> signatures<01:48:39.119> that 01:48:39.350 --> 01:48:39.360 align:start position:0% can actually produce the signatures that 01:48:39.360 --> 01:48:42.649 align:start position:0% can actually produce the signatures that they<01:48:39.480> will<01:48:39.600> need<01:48:39.780> to<01:48:39.900> produce<01:48:40.400> and<01:48:41.400> also 01:48:42.649 --> 01:48:42.659 align:start position:0% they will need to produce and also 01:48:42.659 --> 01:48:45.830 align:start position:0% they will need to produce and also to<01:48:43.260> use<01:48:43.440> this<01:48:43.739> to<01:48:44.159> figure<01:48:44.340> out<01:48:44.699> the<01:48:45.360> backwards 01:48:45.830 --> 01:48:45.840 align:start position:0% to use this to figure out the backwards 01:48:45.840 --> 01:48:48.470 align:start position:0% to use this to figure out the backwards compatibility<01:48:46.320> story<01:48:46.679> and<01:48:47.340> I<01:48:48.119> still<01:48:48.239> need<01:48:48.420> to 01:48:48.470 --> 01:48:48.480 align:start position:0% compatibility story and I still need to 01:48:48.480 --> 01:48:49.850 align:start position:0% compatibility story and I still need to develop<01:48:48.780> this<01:48:48.900> a<01:48:49.080> little<01:48:49.139> bit<01:48:49.260> further<01:48:49.560> but 01:48:49.850 --> 01:48:49.860 align:start position:0% develop this a little bit further but 01:48:49.860 --> 01:48:51.410 align:start position:0% develop this a little bit further but I'm<01:48:49.980> hoping<01:48:50.340> that<01:48:50.580> I'm<01:48:50.940> going<01:48:51.119> to<01:48:51.239> come<01:48:51.300> up 01:48:51.410 --> 01:48:51.420 align:start position:0% I'm hoping that I'm going to come up 01:48:51.420 --> 01:48:54.470 align:start position:0% I'm hoping that I'm going to come up with<01:48:51.600> a<01:48:51.840> good<01:48:52.500> and<01:48:52.800> kind<01:48:52.980> of<01:48:53.100> uh<01:48:53.940> comprehensive 01:48:54.470 --> 01:48:54.480 align:start position:0% with a good and kind of uh comprehensive 01:48:54.480 --> 01:48:56.090 align:start position:0% with a good and kind of uh comprehensive answer<01:48:54.719> then<01:48:55.080> I<01:48:55.199> can<01:48:55.320> then<01:48:55.440> go<01:48:55.619> back<01:48:55.800> in<01:48:55.980> the 01:48:56.090 --> 01:48:56.100 align:start position:0% answer then I can then go back in the 01:48:56.100 --> 01:48:58.149 align:start position:0% answer then I can then go back in the EIP<01:48:56.400> and<01:48:56.880> document<01:48:57.179> it<01:48:57.360> there 01:48:58.149 --> 01:48:58.159 align:start position:0% EIP and document it there 01:48:58.159 --> 01:49:00.890 align:start position:0% EIP and document it there to<01:48:59.159> make<01:48:59.280> sure<01:48:59.460> that<01:48:59.639> it<01:48:59.760> really<01:48:59.940> answers<01:49:00.659> the 01:49:00.890 --> 01:49:00.900 align:start position:0% to make sure that it really answers the 01:49:00.900 --> 01:49:01.910 align:start position:0% to make sure that it really answers the concerns 01:49:01.910 --> 01:49:01.920 align:start position:0% concerns 01:49:01.920 --> 01:49:03.590 align:start position:0% concerns that<01:49:02.400> were<01:49:02.580> raised<01:49:02.940> in<01:49:03.060> The<01:49:03.179> ethereum 01:49:03.590 --> 01:49:03.600 align:start position:0% that were raised in The ethereum 01:49:03.600 --> 01:49:07.609 align:start position:0% that were raised in The ethereum Magicians<01:49:04.080> thread<01:49:04.320> so 01:49:07.609 --> 01:49:07.619 align:start position:0% 01:49:07.619 --> 01:49:11.209 align:start position:0% I<01:49:08.219> think<01:49:08.340> uh<01:49:08.580> yeah<01:49:08.880> that's<01:49:09.780> it<01:49:10.020> again<01:49:10.860> it<01:49:11.100> was 01:49:11.209 --> 01:49:11.219 align:start position:0% I think uh yeah that's it again it was 01:49:11.219 --> 01:49:14.570 align:start position:0% I think uh yeah that's it again it was very<01:49:11.400> quick<01:49:11.639> but<01:49:12.420> these<01:49:13.380> are<01:49:13.440> some<01:49:13.679> of<01:49:13.800> the<01:49:14.580> um 01:49:14.570 --> 01:49:14.580 align:start position:0% very quick but these are some of the um 01:49:14.580 --> 01:49:16.609 align:start position:0% very quick but these are some of the um things<01:49:15.360> that<01:49:15.600> I've<01:49:15.719> been<01:49:15.900> experimenting<01:49:16.500> with 01:49:16.609 --> 01:49:16.619 align:start position:0% things that I've been experimenting with 01:49:16.619 --> 01:49:20.450 align:start position:0% things that I've been experimenting with in<01:49:16.980> order<01:49:17.159> to<01:49:17.340> get<01:49:17.580> this<01:49:17.820> to<01:49:18.179> a<01:49:18.360> final<01:49:18.600> stage<01:49:19.460> I 01:49:20.450 --> 01:49:20.460 align:start position:0% in order to get this to a final stage I 01:49:20.460 --> 01:49:24.590 align:start position:0% in order to get this to a final stage I think<01:49:20.639> uh<01:49:21.540> there<01:49:22.139> are<01:49:22.340> we<01:49:23.340> see<01:49:23.460> many<01:49:23.760> eaps<01:49:24.420> that 01:49:24.590 --> 01:49:24.600 align:start position:0% think uh there are we see many eaps that 01:49:24.600 --> 01:49:27.290 align:start position:0% think uh there are we see many eaps that take<01:49:24.780> more<01:49:25.020> of<01:49:25.139> a<01:49:25.320> fast<01:49:25.560> track<01:49:25.980> and<01:49:26.760> get<01:49:27.000> to<01:49:27.119> a 01:49:27.290 --> 01:49:27.300 align:start position:0% take more of a fast track and get to a 01:49:27.300 --> 01:49:29.570 align:start position:0% take more of a fast track and get to a final<01:49:27.480> stage<01:49:27.900> which<01:49:28.560> is<01:49:28.739> you<01:49:29.219> know<01:49:29.340> it's 01:49:29.570 --> 01:49:29.580 align:start position:0% final stage which is you know it's 01:49:29.580 --> 01:49:32.510 align:start position:0% final stage which is you know it's better<01:49:30.360> in<01:49:30.600> a<01:49:30.780> way<01:49:30.900> because<01:49:31.500> we<01:49:32.040> know<01:49:32.219> that 01:49:32.510 --> 01:49:32.520 align:start position:0% better in a way because we know that 01:49:32.520 --> 01:49:34.129 align:start position:0% better in a way because we know that these<01:49:32.940> processes<01:49:33.300> can<01:49:33.480> be<01:49:33.600> long<01:49:33.719> and<01:49:33.960> it's 01:49:34.129 --> 01:49:34.139 align:start position:0% these processes can be long and it's 01:49:34.139 --> 01:49:36.890 align:start position:0% these processes can be long and it's really<01:49:34.380> annoying<01:49:34.980> but<01:49:36.119> um 01:49:36.890 --> 01:49:36.900 align:start position:0% really annoying but um 01:49:36.900 --> 01:49:39.890 align:start position:0% really annoying but um then<01:49:37.500> you<01:49:37.739> get<01:49:37.920> to<01:49:38.040> a<01:49:38.219> final<01:49:38.340> stage<01:49:38.760> and<01:49:39.119> it 01:49:39.890 --> 01:49:39.900 align:start position:0% then you get to a final stage and it 01:49:39.900 --> 01:49:41.990 align:start position:0% then you get to a final stage and it doesn't<01:49:40.260> necessarily<01:49:40.739> mean<01:49:40.920> anything<01:49:41.219> if<01:49:41.940> it 01:49:41.990 --> 01:49:42.000 align:start position:0% doesn't necessarily mean anything if it 01:49:42.000 --> 01:49:43.669 align:start position:0% doesn't necessarily mean anything if it hasn't<01:49:42.300> been<01:49:42.420> thoroughly<01:49:42.780> tested<01:49:43.260> and<01:49:43.619> then 01:49:43.669 --> 01:49:43.679 align:start position:0% hasn't been thoroughly tested and then 01:49:43.679 --> 01:49:44.750 align:start position:0% hasn't been thoroughly tested and then you're<01:49:43.860> really<01:49:43.980> going<01:49:44.159> to<01:49:44.219> run<01:49:44.340> into<01:49:44.520> some 01:49:44.750 --> 01:49:44.760 align:start position:0% you're really going to run into some 01:49:44.760 --> 01:49:47.330 align:start position:0% you're really going to run into some issues<01:49:45.119> when<01:49:45.540> say<01:49:45.840> open<01:49:46.260> Zeppelin<01:49:46.800> implements 01:49:47.330 --> 01:49:47.340 align:start position:0% issues when say open Zeppelin implements 01:49:47.340 --> 01:49:49.310 align:start position:0% issues when say open Zeppelin implements it<01:49:47.400> and<01:49:47.580> people<01:49:47.820> start<01:49:48.119> deploying<01:49:48.659> it<01:49:48.780> and<01:49:49.199> you 01:49:49.310 --> 01:49:49.320 align:start position:0% it and people start deploying it and you 01:49:49.320 --> 01:49:51.410 align:start position:0% it and people start deploying it and you realize<01:49:49.679> oh<01:49:50.460> this<01:49:50.699> this<01:49:50.760> isn't<01:49:51.239> really 01:49:51.410 --> 01:49:51.420 align:start position:0% realize oh this this isn't really 01:49:51.420 --> 01:49:52.310 align:start position:0% realize oh this this isn't really enough 01:49:52.310 --> 01:49:52.320 align:start position:0% enough 01:49:52.320 --> 01:49:54.770 align:start position:0% enough um<01:49:52.380> so<01:49:53.580> um<01:49:53.580> then<01:49:53.940> you<01:49:54.119> need<01:49:54.239> to<01:49:54.300> start<01:49:54.480> thinking 01:49:54.770 --> 01:49:54.780 align:start position:0% um so um then you need to start thinking 01:49:54.780 --> 01:49:57.350 align:start position:0% um so um then you need to start thinking about<01:49:54.960> like<01:49:55.320> a<01:49:55.679> follow-up<01:49:56.040> EIP<01:49:56.460> and<01:49:56.940> it's<01:49:57.119> all 01:49:57.350 --> 01:49:57.360 align:start position:0% about like a follow-up EIP and it's all 01:49:57.360 --> 01:49:59.870 align:start position:0% about like a follow-up EIP and it's all uh<01:49:57.900> really<01:49:58.199> much<01:49:58.560> more<01:49:58.860> complicated<01:49:59.400> than<01:49:59.699> it 01:49:59.870 --> 01:49:59.880 align:start position:0% uh really much more complicated than it 01:49:59.880 --> 01:50:02.390 align:start position:0% uh really much more complicated than it should<01:50:00.060> be<01:50:00.179> if<01:50:00.840> we<01:50:01.020> do<01:50:01.199> things<01:50:01.500> better<01:50:01.800> before 01:50:02.390 --> 01:50:02.400 align:start position:0% should be if we do things better before 01:50:02.400 --> 01:50:04.430 align:start position:0% should be if we do things better before we<01:50:02.639> get<01:50:02.820> to<01:50:02.940> a<01:50:03.060> final<01:50:03.239> stage<01:50:03.600> so<01:50:03.900> anyway<01:50:04.020> those 01:50:04.430 --> 01:50:04.440 align:start position:0% we get to a final stage so anyway those 01:50:04.440 --> 01:50:06.950 align:start position:0% we get to a final stage so anyway those are<01:50:04.560> some<01:50:04.739> of<01:50:04.860> my<01:50:05.040> ideas<01:50:05.219> thank<01:50:05.880> you 01:50:06.950 --> 01:50:06.960 align:start position:0% are some of my ideas thank you 01:50:06.960 --> 01:50:09.109 align:start position:0% are some of my ideas thank you um happy<01:50:07.440> Tuesday<01:50:07.679> questions<01:50:08.040> if<01:50:08.340> any<01:50:08.460> yes 01:50:09.109 --> 01:50:09.119 align:start position:0% um happy Tuesday questions if any yes 01:50:09.119 --> 01:50:12.830 align:start position:0% um happy Tuesday questions if any yes thank<01:50:09.540> you<01:50:09.659> very<01:50:09.840> much 01:50:12.830 --> 01:50:12.840 align:start position:0% 01:50:12.840 --> 01:50:16.669 align:start position:0% do<01:50:13.679> we<01:50:13.920> have<01:50:14.100> questions<01:50:14.520> yes 01:50:16.669 --> 01:50:16.679 align:start position:0% do we have questions yes 01:50:16.679 --> 01:50:19.550 align:start position:0% do we have questions yes hey<01:50:17.219> really<01:50:17.520> cool<01:50:17.760> uh<01:50:18.420> first<01:50:18.719> uh<01:50:18.900> comment<01:50:19.260> it 01:50:19.550 --> 01:50:19.560 align:start position:0% hey really cool uh first uh comment it 01:50:19.560 --> 01:50:22.430 align:start position:0% hey really cool uh first uh comment it reminds<01:50:20.040> me<01:50:20.159> of<01:50:20.699> uh<01:50:21.119> like<01:50:21.540> the<01:50:21.780> Amazon<01:50:21.900> six 01:50:22.430 --> 01:50:22.440 align:start position:0% reminds me of uh like the Amazon six 01:50:22.440 --> 01:50:24.890 align:start position:0% reminds me of uh like the Amazon six page<01:50:22.739> written<01:50:23.100> narrative<01:50:23.400> way<01:50:23.639> of<01:50:24.119> you<01:50:24.719> have 01:50:24.890 --> 01:50:24.900 align:start position:0% page written narrative way of you have 01:50:24.900 --> 01:50:27.050 align:start position:0% page written narrative way of you have to<01:50:25.020> like<01:50:25.199> sharpen<01:50:25.619> your<01:50:25.980> point<01:50:26.460> or<01:50:26.699> your<01:50:26.880> case 01:50:27.050 --> 01:50:27.060 align:start position:0% to like sharpen your point or your case 01:50:27.060 --> 01:50:28.729 align:start position:0% to like sharpen your point or your case and<01:50:27.420> then<01:50:27.540> you<01:50:27.719> go<01:50:27.840> around<01:50:27.960> and<01:50:28.199> get<01:50:28.380> feedback 01:50:28.729 --> 01:50:28.739 align:start position:0% and then you go around and get feedback 01:50:28.739 --> 01:50:30.530 align:start position:0% and then you go around and get feedback from<01:50:28.920> people<01:50:29.100> and<01:50:29.400> then<01:50:29.460> incorporate<01:50:30.000> that<01:50:30.239> in 01:50:30.530 --> 01:50:30.540 align:start position:0% from people and then incorporate that in 01:50:30.540 --> 01:50:32.750 align:start position:0% from people and then incorporate that in a<01:50:30.719> fact<01:50:31.020> at<01:50:31.320> the<01:50:31.440> end<01:50:31.500> of<01:50:31.619> the<01:50:31.679> document<01:50:32.040> to 01:50:32.750 --> 01:50:32.760 align:start position:0% a fact at the end of the document to 01:50:32.760 --> 01:50:34.910 align:start position:0% a fact at the end of the document to like<01:50:33.179> because<01:50:34.020> you<01:50:34.260> know<01:50:34.380> other<01:50:34.500> people<01:50:34.679> have 01:50:34.910 --> 01:50:34.920 align:start position:0% like because you know other people have 01:50:34.920 --> 01:50:36.709 align:start position:0% like because you know other people have those<01:50:35.159> concerns<01:50:35.520> or<01:50:35.699> objections<01:50:36.179> so<01:50:36.420> that's 01:50:36.709 --> 01:50:36.719 align:start position:0% those concerns or objections so that's 01:50:36.719 --> 01:50:37.790 align:start position:0% those concerns or objections so that's really<01:50:36.900> awesome 01:50:37.790 --> 01:50:37.800 align:start position:0% really awesome 01:50:37.800 --> 01:50:39.470 align:start position:0% really awesome um<01:50:37.920> do<01:50:38.520> you<01:50:38.639> can<01:50:38.820> you<01:50:38.940> just<01:50:39.060> speak<01:50:39.239> a<01:50:39.360> little 01:50:39.470 --> 01:50:39.480 align:start position:0% um do you can you just speak a little 01:50:39.480 --> 01:50:40.970 align:start position:0% um do you can you just speak a little bit<01:50:39.600> more<01:50:39.719> about<01:50:39.900> that<01:50:40.320> process<01:50:40.619> and<01:50:40.800> how 01:50:40.970 --> 01:50:40.980 align:start position:0% bit more about that process and how 01:50:40.980 --> 01:50:42.709 align:start position:0% bit more about that process and how you've<01:50:41.159> followed<01:50:41.520> up<01:50:41.639> with<01:50:41.760> people<01:50:41.940> maybe<01:50:42.300> on 01:50:42.709 --> 01:50:42.719 align:start position:0% you've followed up with people maybe on 01:50:42.719 --> 01:50:44.149 align:start position:0% you've followed up with people maybe on this<01:50:42.900> one<01:50:43.020> or<01:50:43.260> something<01:50:43.440> in<01:50:43.619> the<01:50:43.739> past<01:50:43.860> so 01:50:44.149 --> 01:50:44.159 align:start position:0% this one or something in the past so 01:50:44.159 --> 01:50:46.370 align:start position:0% this one or something in the past so it's<01:50:44.460> one<01:50:44.639> thing<01:50:44.760> for<01:50:45.000> somebody<01:50:45.239> to 01:50:46.370 --> 01:50:46.380 align:start position:0% it's one thing for somebody to 01:50:46.380 --> 01:50:48.169 align:start position:0% it's one thing for somebody to say<01:50:46.920> it<01:50:47.100> looks<01:50:47.340> great<01:50:47.460> maybe<01:50:47.760> give<01:50:48.000> some 01:50:48.169 --> 01:50:48.179 align:start position:0% say it looks great maybe give some 01:50:48.179 --> 01:50:49.850 align:start position:0% say it looks great maybe give some feedback<01:50:48.540> on<01:50:48.719> The<01:50:48.900> ethereum<01:50:49.260> Magician's<01:50:49.739> post 01:50:49.850 --> 01:50:49.860 align:start position:0% feedback on The ethereum Magician's post 01:50:49.860 --> 01:50:53.270 align:start position:0% feedback on The ethereum Magician's post but<01:50:50.760> really<01:50:51.179> an<01:50:51.300> eip's<01:50:52.080> success<01:50:52.619> or<01:50:52.920> failure 01:50:53.270 --> 01:50:53.280 align:start position:0% but really an eip's success or failure 01:50:53.280 --> 01:50:55.729 align:start position:0% but really an eip's success or failure is<01:50:53.580> like<01:50:53.840> people<01:50:54.840> using<01:50:55.199> it<01:50:55.320> like<01:50:55.500> you<01:50:55.619> just 01:50:55.729 --> 01:50:55.739 align:start position:0% is like people using it like you just 01:50:55.739 --> 01:50:57.290 align:start position:0% is like people using it like you just spoke<01:50:55.920> to<01:50:56.040> so<01:50:56.280> have<01:50:56.580> you<01:50:56.699> have<01:50:56.880> a<01:50:57.000> good<01:50:57.060> example 01:50:57.290 --> 01:50:57.300 align:start position:0% spoke to so have you have a good example 01:50:57.300 --> 01:50:58.729 align:start position:0% spoke to so have you have a good example of<01:50:57.420> like<01:50:57.600> following<01:50:57.900> back<01:50:58.020> up<01:50:58.139> with<01:50:58.320> protocols 01:50:58.729 --> 01:50:58.739 align:start position:0% of like following back up with protocols 01:50:58.739 --> 01:50:59.870 align:start position:0% of like following back up with protocols and<01:50:58.860> actually<01:50:59.100> getting<01:50:59.280> them<01:50:59.460> to<01:50:59.639> implement 01:50:59.870 --> 01:50:59.880 align:start position:0% and actually getting them to implement 01:50:59.880 --> 01:51:02.930 align:start position:0% and actually getting them to implement the<01:51:00.119> EIP<01:51:00.480> as<01:51:01.020> part<01:51:01.199> of<01:51:01.380> your<01:51:01.619> uh<01:51:01.980> kind<01:51:02.159> of<01:51:02.280> Biz 01:51:02.930 --> 01:51:02.940 align:start position:0% the EIP as part of your uh kind of Biz 01:51:02.940 --> 01:51:06.050 align:start position:0% the EIP as part of your uh kind of Biz Dev<01:51:03.179> work<01:51:03.420> if<01:51:03.600> you<01:51:03.719> call<01:51:03.840> it<01:51:03.960> yeah<01:51:04.340> so<01:51:05.340> uh<01:51:05.820> good 01:51:06.050 --> 01:51:06.060 align:start position:0% Dev work if you call it yeah so uh good 01:51:06.060 --> 01:51:07.850 align:start position:0% Dev work if you call it yeah so uh good question<01:51:06.300> I<01:51:06.960> haven't<01:51:07.080> thought<01:51:07.320> about<01:51:07.500> that 01:51:07.850 --> 01:51:07.860 align:start position:0% question I haven't thought about that 01:51:07.860 --> 01:51:09.950 align:start position:0% question I haven't thought about that too<01:51:08.219> much<01:51:08.400> yet 01:51:09.950 --> 01:51:09.960 align:start position:0% too much yet 01:51:09.960 --> 01:51:11.450 align:start position:0% too much yet um<01:51:10.020> but 01:51:11.450 --> 01:51:11.460 align:start position:0% um but 01:51:11.460 --> 01:51:13.790 align:start position:0% um but um<01:51:11.520> one<01:51:12.420> of<01:51:12.540> the<01:51:12.600> things<01:51:12.719> that<01:51:12.960> I<01:51:13.199> I<01:51:13.440> personally 01:51:13.790 --> 01:51:13.800 align:start position:0% um one of the things that I I personally 01:51:13.800 --> 01:51:16.550 align:start position:0% um one of the things that I I personally struggle<01:51:14.760> with<01:51:14.880> is<01:51:15.360> that<01:51:15.659> I<01:51:15.840> feel<01:51:16.139> like<01:51:16.260> I'm<01:51:16.440> in 01:51:16.550 --> 01:51:16.560 align:start position:0% struggle with is that I feel like I'm in 01:51:16.560 --> 01:51:18.470 align:start position:0% struggle with is that I feel like I'm in a<01:51:16.739> bit<01:51:16.800> of<01:51:16.920> a<01:51:17.159> conflict<01:51:17.699> of<01:51:17.820> interest<01:51:18.000> position 01:51:18.470 --> 01:51:18.480 align:start position:0% a bit of a conflict of interest position 01:51:18.480 --> 01:51:20.090 align:start position:0% a bit of a conflict of interest position because<01:51:19.020> of<01:51:19.260> being<01:51:19.440> on<01:51:19.560> opens<01:51:19.920> up<01:51:20.040> and 01:51:20.090 --> 01:51:20.100 align:start position:0% because of being on opens up and 01:51:20.100 --> 01:51:21.530 align:start position:0% because of being on opens up and contracts<01:51:20.460> maintainer<01:51:20.760> it's<01:51:20.940> like<01:51:21.119> it's 01:51:21.530 --> 01:51:21.540 align:start position:0% contracts maintainer it's like it's 01:51:21.540 --> 01:51:23.149 align:start position:0% contracts maintainer it's like it's going<01:51:21.719> to<01:51:21.840> be<01:51:21.900> really<01:51:22.020> easy<01:51:22.199> for<01:51:22.500> me<01:51:22.619> to<01:51:22.860> put 01:51:23.149 --> 01:51:23.159 align:start position:0% going to be really easy for me to put 01:51:23.159 --> 01:51:24.770 align:start position:0% going to be really easy for me to put this<01:51:23.340> in<01:51:23.460> the<01:51:23.580> contract<01:51:23.820> and<01:51:24.060> make<01:51:24.239> people<01:51:24.480> use 01:51:24.770 --> 01:51:24.780 align:start position:0% this in the contract and make people use 01:51:24.780 --> 01:51:26.270 align:start position:0% this in the contract and make people use it<01:51:24.900> but<01:51:25.199> I<01:51:25.380> don't<01:51:25.440> want<01:51:25.560> to<01:51:25.679> force<01:51:25.980> it<01:51:26.100> down 01:51:26.270 --> 01:51:26.280 align:start position:0% it but I don't want to force it down 01:51:26.280 --> 01:51:29.450 align:start position:0% it but I don't want to force it down people<01:51:26.460> so<01:51:26.760> for<01:51:27.719> example<01:51:27.960> one<01:51:28.440> thing<01:51:28.619> that<01:51:28.980> I 01:51:29.450 --> 01:51:29.460 align:start position:0% people so for example one thing that I 01:51:29.460 --> 01:51:31.370 align:start position:0% people so for example one thing that I uh<01:51:30.119> could<01:51:30.360> do<01:51:30.540> and<01:51:30.780> now<01:51:30.900> that<01:51:31.020> I'm<01:51:31.139> thinking 01:51:31.370 --> 01:51:31.380 align:start position:0% uh could do and now that I'm thinking 01:51:31.380 --> 01:51:33.109 align:start position:0% uh could do and now that I'm thinking about<01:51:31.440> I<01:51:31.619> think<01:51:31.739> it<01:51:31.860> will<01:51:31.980> be<01:51:32.100> a<01:51:32.219> great<01:51:32.400> idea<01:51:32.760> is 01:51:33.109 --> 01:51:33.119 align:start position:0% about I think it will be a great idea is 01:51:33.119 --> 01:51:36.109 align:start position:0% about I think it will be a great idea is to<01:51:33.480> talk<01:51:34.080> to<01:51:34.320> this<01:51:34.560> one-inch<01:51:35.340> developer<01:51:35.940> that 01:51:36.109 --> 01:51:36.119 align:start position:0% to talk to this one-inch developer that 01:51:36.119 --> 01:51:39.609 align:start position:0% to talk to this one-inch developer that I<01:51:36.239> talked<01:51:36.480> about<01:51:36.540> and<01:51:37.219> maybe<01:51:38.219> uh 01:51:39.609 --> 01:51:39.619 align:start position:0% I talked about and maybe uh 01:51:39.619 --> 01:51:43.430 align:start position:0% I talked about and maybe uh try<01:51:40.619> to<01:51:40.739> get<01:51:40.860> them<01:51:40.980> to<01:51:41.219> to<01:51:41.540> walk<01:51:42.540> me<01:51:42.719> through<01:51:42.960> do 01:51:43.430 --> 01:51:43.440 align:start position:0% try to get them to to walk me through do 01:51:43.440 --> 01:51:46.490 align:start position:0% try to get them to to walk me through do they<01:51:43.619> really<01:51:43.800> see<01:51:44.040> do<01:51:44.520> they<01:51:44.760> like<01:51:45.000> really<01:51:45.840> see 01:51:46.490 --> 01:51:46.500 align:start position:0% they really see do they like really see 01:51:46.500 --> 01:51:48.530 align:start position:0% they really see do they like really see themselves<01:51:46.860> implementing<01:51:47.520> this<01:51:47.820> and<01:51:48.360> maybe 01:51:48.530 --> 01:51:48.540 align:start position:0% themselves implementing this and maybe 01:51:48.540 --> 01:51:50.149 align:start position:0% themselves implementing this and maybe what<01:51:48.780> is<01:51:48.960> the<01:51:49.080> timeline 01:51:50.149 --> 01:51:50.159 align:start position:0% what is the timeline 01:51:50.159 --> 01:51:52.070 align:start position:0% what is the timeline um<01:51:50.219> and<01:51:50.520> kind<01:51:50.699> of<01:51:50.820> yeah<01:51:51.420> just<01:51:51.659> trying<01:51:51.840> to<01:51:51.960> get 01:51:52.070 --> 01:51:52.080 align:start position:0% um and kind of yeah just trying to get 01:51:52.080 --> 01:51:54.109 align:start position:0% um and kind of yeah just trying to get more<01:51:52.320> concrete<01:51:52.739> data<01:51:53.159> on<01:51:53.400> on<01:51:53.520> their<01:51:53.699> plans<01:51:53.940> and 01:51:54.109 --> 01:51:54.119 align:start position:0% more concrete data on on their plans and 01:51:54.119 --> 01:51:56.689 align:start position:0% more concrete data on on their plans and try<01:51:54.300> to<01:51:54.480> try<01:51:54.960> to<01:51:55.080> get<01:51:55.260> them<01:51:55.380> to<01:51:55.560> commit 01:51:56.689 --> 01:51:56.699 align:start position:0% try to try to get them to commit 01:51:56.699 --> 01:52:00.649 align:start position:0% try to try to get them to commit um<01:51:56.760> maybe<01:51:57.000> that's<01:51:57.300> what<01:51:57.540> I<01:51:57.659> I<01:51:58.020> would<01:51:58.320> do 01:52:00.649 --> 01:52:00.659 align:start position:0% 01:52:00.659 --> 01:52:04.189 align:start position:0% thank<01:52:01.199> you<01:52:01.699> uh<01:52:02.699> more<01:52:02.940> questions<01:52:03.300> feedback 01:52:04.189 --> 01:52:04.199 align:start position:0% thank you uh more questions feedback 01:52:04.199 --> 01:52:08.090 align:start position:0% thank you uh more questions feedback maybe<01:52:05.300> uh<01:52:06.300> people<01:52:06.540> that<01:52:06.780> have<01:52:06.960> used<01:52:07.199> this<01:52:07.560> or 01:52:08.090 --> 01:52:08.100 align:start position:0% maybe uh people that have used this or 01:52:08.100 --> 01:52:12.410 align:start position:0% maybe uh people that have used this or or<01:52:08.760> 712 01:52:12.410 --> 01:52:12.420 align:start position:0% 01:52:12.420 --> 01:52:15.470 align:start position:0% raise<01:52:13.020> your<01:52:13.260> hand<01:52:13.440> if<01:52:13.920> you<01:52:14.040> have<01:52:14.159> a<01:52:14.280> question 01:52:15.470 --> 01:52:15.480 align:start position:0% raise your hand if you have a question 01:52:15.480 --> 01:52:19.010 align:start position:0% raise your hand if you have a question okay<01:52:16.460> then<01:52:17.460> thank<01:52:17.820> you<01:52:17.940> very<01:52:18.060> much<01:52:18.239> Francisco 01:52:19.010 --> 01:52:19.020 align:start position:0% okay then thank you very much Francisco 01:52:19.020 --> 01:52:24.890 align:start position:0% okay then thank you very much Francisco Round<01:52:19.619> of<01:52:19.800> Applause<01:52:20.040> thank<01:52:20.280> you<01:52:20.400> thank<01:52:20.760> you 01:52:24.890 --> 01:52:24.900 align:start position:0% 01:52:24.900 --> 01:52:27.470 align:start position:0% yeah<01:52:25.380> and<01:52:25.560> that's<01:52:25.800> essentially<01:52:26.219> it<01:52:26.520> that<01:52:27.000> was 01:52:27.470 --> 01:52:27.480 align:start position:0% yeah and that's essentially it that was 01:52:27.480 --> 01:52:30.169 align:start position:0% yeah and that's essentially it that was the<01:52:28.139> ERC<01:52:28.800> lightning<01:52:29.340> talks<01:52:29.760> from<01:52:30.000> The 01:52:30.169 --> 01:52:30.179 align:start position:0% the ERC lightning talks from The 01:52:30.179 --> 01:52:32.870 align:start position:0% the ERC lightning talks from The Magicians<01:52:30.659> I<01:52:30.840> hope<01:52:31.020> you<01:52:31.139> all<01:52:31.320> liked<01:52:31.679> it 01:52:32.870 --> 01:52:32.880 align:start position:0% Magicians I hope you all liked it 01:52:32.880 --> 01:52:35.149 align:start position:0% Magicians I hope you all liked it um<01:52:33.000> you<01:52:33.360> can<01:52:33.540> find<01:52:33.900> each<01:52:34.800> and<01:52:34.980> everyone 01:52:35.149 --> 01:52:35.159 align:start position:0% um you can find each and everyone 01:52:35.159 --> 01:52:38.149 align:start position:0% um you can find each and everyone hopefully<01:52:36.080> uh<01:52:37.080> on<01:52:37.260> the<01:52:37.380> East<01:52:37.500> magician's 01:52:38.149 --> 01:52:38.159 align:start position:0% hopefully uh on the East magician's 01:52:38.159 --> 01:52:42.290 align:start position:0% hopefully uh on the East magician's forum<01:52:38.659> and<01:52:39.659> I'm<01:52:39.900> looking<01:52:40.199> forward<01:52:40.619> to<01:52:41.119> all<01:52:42.119> of 01:52:42.290 --> 01:52:42.300 align:start position:0% forum and I'm looking forward to all of 01:52:42.300 --> 01:52:44.870 align:start position:0% forum and I'm looking forward to all of the<01:52:42.659> posts<01:52:43.440> that<01:52:43.560> are<01:52:43.739> coming<01:52:43.860> out<01:52:44.100> of<01:52:44.280> these 01:52:44.870 --> 01:52:44.880 align:start position:0% the posts that are coming out of these 01:52:44.880 --> 01:52:47.689 align:start position:0% the posts that are coming out of these discussions<01:52:45.300> I'm<01:52:45.600> I<01:52:46.139> want<01:52:46.380> to<01:52:46.560> thank<01:52:47.280> you<01:52:47.520> all 01:52:47.689 --> 01:52:47.699 align:start position:0% discussions I'm I want to thank you all 01:52:47.699 --> 01:52:51.590 align:start position:0% discussions I'm I want to thank you all for<01:52:48.260> participating<01:52:49.260> uh<01:52:49.980> like<01:52:50.280> so<01:52:50.639> much<01:52:51.300> in 01:52:51.590 --> 01:52:51.600 align:start position:0% for participating uh like so much in 01:52:51.600 --> 01:52:53.750 align:start position:0% for participating uh like so much in this<01:52:51.840> conversation<01:52:52.380> and<01:52:52.800> I<01:52:53.280> I<01:52:53.460> really 01:52:53.750 --> 01:52:53.760 align:start position:0% this conversation and I I really 01:52:53.760 --> 01:52:56.090 align:start position:0% this conversation and I I really appreciate<01:52:54.300> that<01:52:54.659> we<01:52:54.960> were<01:52:55.440> having<01:52:55.679> like<01:52:55.920> a 01:52:56.090 --> 01:52:56.100 align:start position:0% appreciate that we were having like a 01:52:56.100 --> 01:52:58.070 align:start position:0% appreciate that we were having like a back<01:52:56.219> and<01:52:56.400> forth<01:52:56.699> between<01:52:56.940> the<01:52:57.239> audience<01:52:57.540> and 01:52:58.070 --> 01:52:58.080 align:start position:0% back and forth between the audience and 01:52:58.080 --> 01:53:00.470 align:start position:0% back and forth between the audience and uh<01:52:58.380> and<01:52:59.100> the<01:52:59.219> presenters<01:52:59.639> and<01:52:59.880> so<01:53:00.000> on<01:53:00.119> and<01:53:00.300> yeah 01:53:00.470 --> 01:53:00.480 align:start position:0% uh and the presenters and so on and yeah 01:53:00.480 --> 01:53:03.830 align:start position:0% uh and the presenters and so on and yeah it<01:53:00.840> was<01:53:01.020> great<01:53:01.260> to<01:53:01.739> be<01:53:02.699> able<01:53:02.880> to<01:53:03.060> host<01:53:03.300> this<01:53:03.540> and 01:53:03.830 --> 01:53:03.840 align:start position:0% it was great to be able to host this and 01:53:03.840 --> 01:53:05.629 align:start position:0% it was great to be able to host this and yeah<01:53:04.080> thank<01:53:04.380> you<01:53:04.500> very<01:53:04.679> much<01:53:04.860> and<01:53:05.280> see<01:53:05.580> you 01:53:05.629 --> 01:53:05.639 align:start position:0% yeah thank you very much and see you 01:53:05.639 --> 01:53:06.730 align:start position:0% yeah thank you very much and see you around 01:53:06.730 --> 01:53:06.740 align:start position:0% around 01:53:06.740 --> 01:53:10.060 align:start position:0% around [Applause]