WEBVTT Kind: captions Language: en 00:00:16.220 --> 00:00:19.160 align:start position:0% okay<00:00:17.220> so<00:00:17.279> this<00:00:18.210> is<00:00:18.390> the<00:00:18.539> standardization 00:00:19.160 --> 00:00:19.170 align:start position:0% okay so this is the standardization 00:00:19.170 --> 00:00:22.370 align:start position:0% okay so this is the standardization panel<00:00:19.590> with<00:00:19.770> a<00:00:20.270> bunch<00:00:21.270> of<00:00:21.390> brilliant<00:00:22.020> minds<00:00:22.289> up 00:00:22.370 --> 00:00:22.380 align:start position:0% panel with a bunch of brilliant minds up 00:00:22.380 --> 00:00:24.800 align:start position:0% panel with a bunch of brilliant minds up here<00:00:22.590> Gavin<00:00:23.100> would<00:00:23.250> Nikolai<00:00:23.810> vivillon 00:00:24.800 --> 00:00:24.810 align:start position:0% here Gavin would Nikolai vivillon 00:00:24.810 --> 00:00:28.279 align:start position:0% here Gavin would Nikolai vivillon vitalik<00:00:25.380> and<00:00:25.560> Christian<00:00:26.869> so<00:00:27.869> the<00:00:28.050> point<00:00:28.199> of 00:00:28.279 --> 00:00:28.289 align:start position:0% vitalik and Christian so the point of 00:00:28.289 --> 00:00:30.769 align:start position:0% vitalik and Christian so the point of this<00:00:28.349> panel<00:00:28.740> is<00:00:28.949> to<00:00:29.369> talk<00:00:30.029> about<00:00:30.240> current 00:00:30.769 --> 00:00:30.779 align:start position:0% this panel is to talk about current 00:00:30.779 --> 00:00:34.010 align:start position:0% this panel is to talk about current standards<00:00:31.199> and<00:00:31.969> potential<00:00:32.969> issues<00:00:33.300> that<00:00:33.750> we 00:00:34.010 --> 00:00:34.020 align:start position:0% standards and potential issues that we 00:00:34.020 --> 00:00:36.229 align:start position:0% standards and potential issues that we might<00:00:34.230> see<00:00:34.440> what<00:00:34.649> happen<00:00:35.010> how<00:00:35.640> can<00:00:36.000> we<00:00:36.030> as<00:00:36.210> a 00:00:36.229 --> 00:00:36.239 align:start position:0% might see what happen how can we as a 00:00:36.239 --> 00:00:38.479 align:start position:0% might see what happen how can we as a community<00:00:36.860> resolve<00:00:37.860> some<00:00:38.070> of<00:00:38.100> these<00:00:38.250> issues 00:00:38.479 --> 00:00:38.489 align:start position:0% community resolve some of these issues 00:00:38.489 --> 00:00:41.270 align:start position:0% community resolve some of these issues and<00:00:39.000> how<00:00:39.629> can<00:00:39.840> we<00:00:39.899> go<00:00:40.110> forward<00:00:40.410> to<00:00:40.649> maybe 00:00:41.270 --> 00:00:41.280 align:start position:0% and how can we go forward to maybe 00:00:41.280 --> 00:00:44.420 align:start position:0% and how can we go forward to maybe implement<00:00:41.930> it's<00:00:42.930> like<00:00:43.050> a<00:00:43.079> perhaps<00:00:43.829> a<00:00:43.950> process 00:00:44.420 --> 00:00:44.430 align:start position:0% implement it's like a perhaps a process 00:00:44.430 --> 00:00:47.330 align:start position:0% implement it's like a perhaps a process or<00:00:44.610> something<00:00:44.940> like<00:00:45.000> that<00:00:45.170> so<00:00:46.170> I<00:00:46.440> think<00:00:46.739> to 00:00:47.330 --> 00:00:47.340 align:start position:0% or something like that so I think to 00:00:47.340 --> 00:00:50.260 align:start position:0% or something like that so I think to start<00:00:47.910> off<00:00:48.149> with<00:00:48.390> I<00:00:48.719> think<00:00:48.989> will<00:00:49.140> be<00:00:49.230> great<00:00:49.440> too 00:00:50.260 --> 00:00:50.270 align:start position:0% start off with I think will be great too 00:00:50.270 --> 00:00:52.459 align:start position:0% start off with I think will be great too there<00:00:51.270> are<00:00:51.360> so<00:00:51.539> there<00:00:51.690> are<00:00:51.780> certain<00:00:52.079> standards 00:00:52.459 --> 00:00:52.469 align:start position:0% there are so there are certain standards 00:00:52.469 --> 00:00:55.400 align:start position:0% there are so there are certain standards that<00:00:52.770> have<00:00:52.800> already<00:00:53.070> been<00:00:53.250> defined<00:00:54.410> that 00:00:55.400 --> 00:00:55.410 align:start position:0% that have already been defined that 00:00:55.410 --> 00:00:57.529 align:start position:0% that have already been defined that people<00:00:55.890> are<00:00:56.010> using<00:00:56.039> and<00:00:56.579> want<00:00:56.789> to<00:00:56.910> use<00:00:57.120> such<00:00:57.420> as 00:00:57.529 --> 00:00:57.539 align:start position:0% people are using and want to use such as 00:00:57.539 --> 00:00:59.689 align:start position:0% people are using and want to use such as the<00:00:57.660> token<00:00:57.840> standards<00:00:58.710> registry<00:00:59.280> standards 00:00:59.689 --> 00:00:59.699 align:start position:0% the token standards registry standards 00:00:59.699 --> 00:01:03.770 align:start position:0% the token standards registry standards and<00:00:59.879> so<00:00:59.969> forth<00:01:00.620> in<00:01:01.620> your<00:01:02.370> area<00:01:03.270> which<00:01:03.539> are<00:01:03.719> the 00:01:03.770 --> 00:01:03.780 align:start position:0% and so forth in your area which are the 00:01:03.780 --> 00:01:06.109 align:start position:0% and so forth in your area which are the ones<00:01:03.989> that<00:01:04.199> you<00:01:04.619> currently<00:01:05.309> feel<00:01:05.549> the<00:01:05.909> most 00:01:06.109 --> 00:01:06.119 align:start position:0% ones that you currently feel the most 00:01:06.119 --> 00:01:08.600 align:start position:0% ones that you currently feel the most passionate<00:01:06.330> about<00:01:06.840> and<00:01:07.110> and<00:01:07.350> what<00:01:08.310> are<00:01:08.430> your 00:01:08.600 --> 00:01:08.610 align:start position:0% passionate about and and what are your 00:01:08.610 --> 00:01:11.480 align:start position:0% passionate about and and what are your thoughts<00:01:09.030> on<00:01:09.299> that<00:01:09.750> particular<00:01:10.350> standard<00:01:11.280> and 00:01:11.480 --> 00:01:11.490 align:start position:0% thoughts on that particular standard and 00:01:11.490 --> 00:01:14.420 align:start position:0% thoughts on that particular standard and going<00:01:12.240> forward<00:01:12.830> we<00:01:13.830> ever<00:01:13.950> wants<00:01:14.159> to<00:01:14.189> start 00:01:14.420 --> 00:01:14.430 align:start position:0% going forward we ever wants to start 00:01:14.430 --> 00:01:19.310 align:start position:0% going forward we ever wants to start Christian<00:01:15.409> yeah<00:01:16.409> so<00:01:16.799> I<00:01:17.330> think<00:01:18.330> for<00:01:18.840> me<00:01:18.869> it's 00:01:19.310 --> 00:01:19.320 align:start position:0% Christian yeah so I think for me it's 00:01:19.320 --> 00:01:24.140 align:start position:0% Christian yeah so I think for me it's probably<00:01:19.830> tokens<00:01:20.520> so<00:01:21.060> in<00:01:21.479> the<00:01:23.150> transacted 00:01:24.140 --> 00:01:24.150 align:start position:0% probably tokens so in the transacted 00:01:24.150 --> 00:01:30.520 align:start position:0% probably tokens so in the transacted grid<00:01:24.450> energy<00:01:25.580> trading<00:01:26.600> program<00:01:28.040> project<00:01:29.040> were 00:01:30.520 --> 00:01:30.530 align:start position:0% grid energy trading program project were 00:01:30.530 --> 00:01:36.670 align:start position:0% grid energy trading program project were right<00:01:31.530> now<00:01:31.799> we<00:01:31.860> have<00:01:32.310> our<00:01:32.610> own<00:01:32.750> custom<00:01:33.750> way<00:01:34.560> of 00:01:36.670 --> 00:01:36.680 align:start position:0% right now we have our own custom way of 00:01:36.680 --> 00:01:41.030 align:start position:0% right now we have our own custom way of tokenizing<00:01:38.689> energy<00:01:39.689> credits<00:01:40.320> renewable 00:01:41.030 --> 00:01:41.040 align:start position:0% tokenizing energy credits renewable 00:01:41.040 --> 00:01:43.429 align:start position:0% tokenizing energy credits renewable energy<00:01:41.130> credits<00:01:41.549> and<00:01:41.990> we<00:01:42.990> want<00:01:43.229> to<00:01:43.320> move 00:01:43.429 --> 00:01:43.439 align:start position:0% energy credits and we want to move 00:01:43.439 --> 00:01:46.850 align:start position:0% energy credits and we want to move towards<00:01:44.009> a<00:01:44.990> standard<00:01:45.990> token<00:01:46.290> solution<00:01:46.710> so 00:01:46.850 --> 00:01:46.860 align:start position:0% towards a standard token solution so 00:01:46.860 --> 00:01:48.440 align:start position:0% towards a standard token solution so that<00:01:46.890> it<00:01:47.070> can<00:01:47.220> may<00:01:47.310> integrate<00:01:47.610> it<00:01:47.939> with<00:01:48.119> with 00:01:48.440 --> 00:01:48.450 align:start position:0% that it can may integrate it with with 00:01:48.450 --> 00:01:51.760 align:start position:0% that it can may integrate it with with markets<00:01:49.439> such<00:01:49.649> as<00:01:49.710> ether<00:01:50.250> eggs<00:01:50.430> etc<00:01:50.670> and<00:01:51.180> so 00:01:51.760 --> 00:01:51.770 align:start position:0% markets such as ether eggs etc and so 00:01:51.770 --> 00:01:55.069 align:start position:0% markets such as ether eggs etc and so this<00:01:52.770> is<00:01:53.000> you<00:01:54.000> know<00:01:54.119> for<00:01:54.450> that<00:01:54.540> reason<00:01:54.600> very 00:01:55.069 --> 00:01:55.079 align:start position:0% this is you know for that reason very 00:01:55.079 --> 00:01:57.740 align:start position:0% this is you know for that reason very important<00:01:55.560> we're<00:01:56.430> also<00:01:56.579> i'm<00:01:57.390> also<00:01:57.630> using 00:01:57.740 --> 00:01:57.750 align:start position:0% important we're also i'm also using 00:01:57.750 --> 00:02:03.340 align:start position:0% important we're also i'm also using registries<00:01:58.560> in<00:01:58.729> various<00:02:00.890> tabs<00:02:01.890> but<00:02:02.640> i<00:02:02.670> think 00:02:03.340 --> 00:02:03.350 align:start position:0% registries in various tabs but i think 00:02:03.350 --> 00:02:08.350 align:start position:0% registries in various tabs but i think they're<00:02:04.350> it's<00:02:05.750> often<00:02:06.750> more<00:02:07.190> straightforward 00:02:08.350 --> 00:02:08.360 align:start position:0% they're it's often more straightforward 00:02:08.360 --> 00:02:11.120 align:start position:0% they're it's often more straightforward and 00:02:11.120 --> 00:02:11.130 align:start position:0% and 00:02:11.130 --> 00:02:15.810 align:start position:0% and it's<00:02:12.990> there<00:02:13.990> might<00:02:14.230> be<00:02:14.260> less<00:02:15.220> need<00:02:15.790> for 00:02:15.810 --> 00:02:15.820 align:start position:0% it's there might be less need for 00:02:15.820 --> 00:02:18.870 align:start position:0% it's there might be less need for interoperability<00:02:16.750> if<00:02:17.490> you<00:02:18.490> have<00:02:18.640> a<00:02:18.670> very 00:02:18.870 --> 00:02:18.880 align:start position:0% interoperability if you have a very 00:02:18.880 --> 00:02:21.450 align:start position:0% interoperability if you have a very targeted<00:02:19.210> system<00:02:19.840> so<00:02:20.440> I<00:02:20.470> think<00:02:20.590> for<00:02:20.890> me<00:02:20.920> tokens 00:02:21.450 --> 00:02:21.460 align:start position:0% targeted system so I think for me tokens 00:02:21.460 --> 00:02:26.850 align:start position:0% targeted system so I think for me tokens stuffing<00:02:24.600> tokens<00:02:25.600> and<00:02:25.840> registries<00:02:26.470> I<00:02:26.620> think 00:02:26.850 --> 00:02:26.860 align:start position:0% stuffing tokens and registries I think 00:02:26.860 --> 00:02:28.740 align:start position:0% stuffing tokens and registries I think probably<00:02:27.190> are<00:02:27.520> the<00:02:27.670> two<00:02:27.850> biggest<00:02:28.030> categories 00:02:28.740 --> 00:02:28.750 align:start position:0% probably are the two biggest categories 00:02:28.750 --> 00:02:31.800 align:start position:0% probably are the two biggest categories and<00:02:29.280> with<00:02:30.280> registry<00:02:30.910> is<00:02:30.970> there<00:02:31.270> are<00:02:31.420> there<00:02:31.780> are 00:02:31.800 --> 00:02:31.810 align:start position:0% and with registry is there are there are 00:02:31.810 --> 00:02:33.840 align:start position:0% and with registry is there are there are different<00:02:32.590> types<00:02:32.650> of<00:02:33.070> them<00:02:33.310> so<00:02:33.580> there<00:02:33.760> are 00:02:33.840 --> 00:02:33.850 align:start position:0% different types of them so there are 00:02:33.850 --> 00:02:35.430 align:start position:0% different types of them so there are some<00:02:34.030> registries<00:02:34.570> that<00:02:34.600> are<00:02:34.840> specifically 00:02:35.430 --> 00:02:35.440 align:start position:0% some registries that are specifically 00:02:35.440 --> 00:02:37.560 align:start position:0% some registries that are specifically kind<00:02:35.740> of<00:02:35.800> targeted<00:02:36.280> to<00:02:36.490> particular<00:02:37.090> types<00:02:37.390> of 00:02:37.560 --> 00:02:37.570 align:start position:0% kind of targeted to particular types of 00:02:37.570 --> 00:02:38.820 align:start position:0% kind of targeted to particular types of metadata<00:02:37.810> and<00:02:38.200> then<00:02:38.350> there's<00:02:38.530> other<00:02:38.740> things 00:02:38.820 --> 00:02:38.830 align:start position:0% metadata and then there's other things 00:02:38.830 --> 00:02:40.860 align:start position:0% metadata and then there's other things which<00:02:39.340> are<00:02:39.550> you<00:02:40.209> know<00:02:40.270> basically<00:02:40.480> named 00:02:40.860 --> 00:02:40.870 align:start position:0% which are you know basically named 00:02:40.870 --> 00:02:43.380 align:start position:0% which are you know basically named registries<00:02:41.410> and<00:02:41.440> they<00:02:41.800> have<00:02:41.980> a<00:02:42.360> lot<00:02:43.360> of 00:02:43.380 --> 00:02:43.390 align:start position:0% registries and they have a lot of 00:02:43.390 --> 00:02:44.850 align:start position:0% registries and they have a lot of different<00:02:43.510> requirements<00:02:44.470> though<00:02:44.620> in<00:02:44.830> some 00:02:44.850 --> 00:02:44.860 align:start position:0% different requirements though in some 00:02:44.860 --> 00:02:47.310 align:start position:0% different requirements though in some cases<00:02:45.370> kind<00:02:45.730> of<00:02:45.820> partially<00:02:46.330> or<00:02:46.510> entirely<00:02:47.080> the 00:02:47.310 --> 00:02:47.320 align:start position:0% cases kind of partially or entirely the 00:02:47.320 --> 00:02:50.250 align:start position:0% cases kind of partially or entirely the same<00:02:47.410> interface<00:02:48.300> aside<00:02:49.300> from<00:02:49.480> those<00:02:49.720> two<00:02:49.780> the 00:02:50.250 --> 00:02:50.260 align:start position:0% same interface aside from those two the 00:02:50.260 --> 00:02:52.890 align:start position:0% same interface aside from those two the third<00:02:50.560> category<00:02:50.860> would<00:02:51.550> be<00:02:51.940> different 00:02:52.890 --> 00:02:52.900 align:start position:0% third category would be different 00:02:52.900 --> 00:02:55.260 align:start position:0% third category would be different different<00:02:53.650> kinds<00:02:54.040> of<00:02:54.160> financial<00:02:54.580> financial 00:02:55.260 --> 00:02:55.270 align:start position:0% different kinds of financial financial 00:02:55.270 --> 00:02:57.840 align:start position:0% different kinds of financial financial contracts<00:02:56.050> exchanges<00:02:56.770> even<00:02:57.040> like<00:02:57.160> purchase 00:02:57.840 --> 00:02:57.850 align:start position:0% contracts exchanges even like purchase 00:02:57.850 --> 00:03:00.420 align:start position:0% contracts exchanges even like purchase offers<00:02:58.209> i<00:02:58.360> want<00:02:58.600> to<00:02:58.660> buy<00:02:58.830> excellence<00:02:59.830> of<00:02:59.920> a<00:03:00.040> 4y 00:03:00.420 --> 00:03:00.430 align:start position:0% offers i want to buy excellence of a 4y 00:03:00.430 --> 00:03:04.770 align:start position:0% offers i want to buy excellence of a 4y units<00:03:00.790> of<00:03:00.910> being<00:03:02.580> yeah<00:03:03.580> so<00:03:04.330> for<00:03:04.510> me<00:03:04.600> would<00:03:04.750> be 00:03:04.770 --> 00:03:04.780 align:start position:0% units of being yeah so for me would be 00:03:04.780 --> 00:03:09.150 align:start position:0% units of being yeah so for me would be like<00:03:06.630> proxy<00:03:07.630> contracts<00:03:08.230> contracts<00:03:08.980> were 00:03:09.150 --> 00:03:09.160 align:start position:0% like proxy contracts contracts were 00:03:09.160 --> 00:03:12.690 align:start position:0% like proxy contracts contracts were actually<00:03:10.080> would<00:03:11.080> hold<00:03:11.620> your<00:03:11.860> ether<00:03:12.220> and<00:03:12.430> send 00:03:12.690 --> 00:03:12.700 align:start position:0% actually would hold your ether and send 00:03:12.700 --> 00:03:14.460 align:start position:0% actually would hold your ether and send it<00:03:12.820> along<00:03:13.090> but<00:03:13.360> maybe<00:03:13.600> do<00:03:13.840> something<00:03:14.110> with<00:03:14.440> it 00:03:14.460 --> 00:03:14.470 align:start position:0% it along but maybe do something with it 00:03:14.470 --> 00:03:18.330 align:start position:0% it along but maybe do something with it maybe<00:03:15.340> like<00:03:15.870> send<00:03:16.870> our<00:03:17.049> chairs<00:03:17.560> to<00:03:17.980> other 00:03:18.330 --> 00:03:18.340 align:start position:0% maybe like send our chairs to other 00:03:18.340 --> 00:03:21.930 align:start position:0% maybe like send our chairs to other proxies<00:03:18.700> or<00:03:19.950> some<00:03:20.950> kind<00:03:21.100> of<00:03:21.160> voting<00:03:21.519> system 00:03:21.930 --> 00:03:21.940 align:start position:0% proxies or some kind of voting system 00:03:21.940 --> 00:03:24.000 align:start position:0% proxies or some kind of voting system based<00:03:22.150> on<00:03:22.360> whatever<00:03:22.840> you<00:03:23.019> pass<00:03:23.290> through<00:03:23.500> this 00:03:24.000 --> 00:03:24.010 align:start position:0% based on whatever you pass through this 00:03:24.010 --> 00:03:26.430 align:start position:0% based on whatever you pass through this would<00:03:24.220> be<00:03:24.400> interesting<00:03:25.390> me<00:03:25.480> and<00:03:25.720> also<00:03:26.049> tokens 00:03:26.430 --> 00:03:26.440 align:start position:0% would be interesting me and also tokens 00:03:26.440 --> 00:03:28.740 align:start position:0% would be interesting me and also tokens as<00:03:26.560> well<00:03:26.769> because<00:03:27.670> we<00:03:27.820> need<00:03:28.180> to<00:03:28.299> integrate<00:03:28.420> it 00:03:28.740 --> 00:03:28.750 align:start position:0% as well because we need to integrate it 00:03:28.750 --> 00:03:30.300 align:start position:0% as well because we need to integrate it in<00:03:28.900> the<00:03:28.989> wallet<00:03:29.170> or<00:03:29.410> we<00:03:29.500> did<00:03:29.680> already<00:03:29.920> and<00:03:30.190> we 00:03:30.300 --> 00:03:30.310 align:start position:0% in the wallet or we did already and we 00:03:30.310 --> 00:03:32.370 align:start position:0% in the wallet or we did already and we want<00:03:30.519> to<00:03:30.640> obviously<00:03:31.000> support<00:03:31.750> as<00:03:31.930> many<00:03:32.140> and 00:03:32.370 --> 00:03:32.380 align:start position:0% want to obviously support as many and 00:03:32.380 --> 00:03:34.979 align:start position:0% want to obviously support as many and talk<00:03:32.920> it<00:03:33.040> as<00:03:33.160> possible<00:03:33.690> can<00:03:34.690> can<00:03:34.959> you 00:03:34.979 --> 00:03:34.989 align:start position:0% talk it as possible can can you 00:03:34.989 --> 00:03:37.280 align:start position:0% talk it as possible can can you elaborate<00:03:35.320> more<00:03:35.380> on<00:03:35.590> the<00:03:35.799> proxy<00:03:36.430> contracts<00:03:36.880> I 00:03:37.280 --> 00:03:37.290 align:start position:0% elaborate more on the proxy contracts I 00:03:37.290 --> 00:03:39.780 align:start position:0% elaborate more on the proxy contracts I mean<00:03:38.290> the<00:03:38.739> current<00:03:39.010> wallet<00:03:39.160> for<00:03:39.340> example<00:03:39.640> is<00:03:39.700> a 00:03:39.780 --> 00:03:39.790 align:start position:0% mean the current wallet for example is a 00:03:39.790 --> 00:03:42.720 align:start position:0% mean the current wallet for example is a proxy<00:03:40.150> contract<00:03:40.570> but<00:03:41.500> ideally<00:03:42.070> you<00:03:42.340> should<00:03:42.370> be 00:03:42.720 --> 00:03:42.730 align:start position:0% proxy contract but ideally you should be 00:03:42.730 --> 00:03:44.310 align:start position:0% proxy contract but ideally you should be for<00:03:42.940> some<00:03:43.060> of<00:03:43.180> the<00:03:43.360> wallet<00:03:43.660> you<00:03:43.780> have<00:03:43.959> a<00:03:43.989> moiety 00:03:44.310 --> 00:03:44.320 align:start position:0% for some of the wallet you have a moiety 00:03:44.320 --> 00:03:49.259 align:start position:0% for some of the wallet you have a moiety sick<00:03:44.680> on<00:03:45.480> ether<00:03:47.850> ideally<00:03:48.850> you<00:03:48.970> can<00:03:49.120> have<00:03:49.239> a 00:03:49.259 --> 00:03:49.269 align:start position:0% sick on ether ideally you can have a 00:03:49.269 --> 00:03:50.819 align:start position:0% sick on ether ideally you can have a moralistic<00:03:49.540> on<00:03:49.750> everything<00:03:50.200> like<00:03:50.440> even<00:03:50.739> a 00:03:50.819 --> 00:03:50.829 align:start position:0% moralistic on everything like even a 00:03:50.829 --> 00:03:52.800 align:start position:0% moralistic on everything like even a multi<00:03:51.040> second<00:03:51.340> sending<00:03:51.940> your<00:03:52.060> custom<00:03:52.390> tokens 00:03:52.800 --> 00:03:52.810 align:start position:0% multi second sending your custom tokens 00:03:52.810 --> 00:03:56.819 align:start position:0% multi second sending your custom tokens or<00:03:53.019> whatever<00:03:53.320> so<00:03:53.769> you<00:03:53.799> can<00:03:54.370> use<00:03:55.170> these<00:03:56.170> proxies 00:03:56.819 --> 00:03:56.829 align:start position:0% or whatever so you can use these proxies 00:03:56.829 --> 00:03:58.350 align:start position:0% or whatever so you can use these proxies for<00:03:57.220> yeah<00:03:57.610> whatever<00:03:57.820> you<00:03:57.970> want<00:03:58.060> to<00:03:58.209> do<00:03:58.269> with 00:03:58.350 --> 00:03:58.360 align:start position:0% for yeah whatever you want to do with 00:03:58.360 --> 00:04:01.610 align:start position:0% for yeah whatever you want to do with any<00:03:58.570> other<00:03:58.720> contract<00:03:59.440> on<00:03:59.530> the<00:03:59.620> network<00:03:59.799> okay 00:04:01.610 --> 00:04:01.620 align:start position:0% any other contract on the network okay 00:04:01.620 --> 00:04:05.580 align:start position:0% any other contract on the network okay yeah<00:04:02.620> so<00:04:02.920> I<00:04:03.730> work<00:04:04.390> on<00:04:04.450> maker<00:04:04.690> and<00:04:05.049> obviously 00:04:05.580 --> 00:04:05.590 align:start position:0% yeah so I work on maker and obviously 00:04:05.590 --> 00:04:08.039 align:start position:0% yeah so I work on maker and obviously were<00:04:05.769> most<00:04:06.130> interested<00:04:06.370> in<00:04:06.610> the<00:04:06.760> under<00:04:07.390> token 00:04:08.039 --> 00:04:08.049 align:start position:0% were most interested in the under token 00:04:08.049 --> 00:04:12.240 align:start position:0% were most interested in the under token standard<00:04:08.620> also<00:04:09.329> and<00:04:10.329> I<00:04:11.290> guess<00:04:11.620> my<00:04:11.890> role<00:04:12.100> on 00:04:12.240 --> 00:04:12.250 align:start position:0% standard also and I guess my role on 00:04:12.250 --> 00:04:13.470 align:start position:0% standard also and I guess my role on this<00:04:12.340> panel<00:04:12.579> is<00:04:12.730> pretty<00:04:12.970> much<00:04:13.090> just<00:04:13.239> going<00:04:13.420> to 00:04:13.470 --> 00:04:13.480 align:start position:0% this panel is pretty much just going to 00:04:13.480 --> 00:04:15.390 align:start position:0% this panel is pretty much just going to be<00:04:13.540> I<00:04:13.840> think<00:04:14.260> it's<00:04:14.380> too<00:04:14.560> early<00:04:14.620> and<00:04:15.040> nothing 00:04:15.390 --> 00:04:15.400 align:start position:0% be I think it's too early and nothing 00:04:15.400 --> 00:04:17.039 align:start position:0% be I think it's too early and nothing seems<00:04:15.730> like<00:04:15.880> a<00:04:15.910> satisfying<00:04:16.419> solution<00:04:16.600> yet 00:04:17.039 --> 00:04:17.049 align:start position:0% seems like a satisfying solution yet 00:04:17.049 --> 00:04:23.160 align:start position:0% seems like a satisfying solution yet although<00:04:17.650> i<00:04:18.190> don't<00:04:18.310> have<00:04:18.519> anything<00:04:18.729> better<00:04:18.970> so 00:04:23.160 --> 00:04:23.170 align:start position:0% 00:04:23.170 --> 00:04:26.320 align:start position:0% so<00:04:24.170> I<00:04:24.410> think<00:04:24.530> identity<00:04:25.250> in<00:04:25.490> some<00:04:25.880> sense<00:04:26.090> is 00:04:26.320 --> 00:04:26.330 align:start position:0% so I think identity in some sense is 00:04:26.330 --> 00:04:29.620 align:start position:0% so I think identity in some sense is something<00:04:26.660> worth<00:04:27.070> considering<00:04:28.070> deeply<00:04:29.000> and 00:04:29.620 --> 00:04:29.630 align:start position:0% something worth considering deeply and 00:04:29.630 --> 00:04:32.050 align:start position:0% something worth considering deeply and how<00:04:29.810> we<00:04:29.870> can<00:04:30.250> try<00:04:31.250> and<00:04:31.400> make<00:04:31.580> all<00:04:31.760> of<00:04:31.790> the 00:04:32.050 --> 00:04:32.060 align:start position:0% how we can try and make all of the 00:04:32.060 --> 00:04:35.560 align:start position:0% how we can try and make all of the different<00:04:33.280> pieces<00:04:34.280> of<00:04:34.520> infrastructure<00:04:34.670> fit 00:04:35.560 --> 00:04:35.570 align:start position:0% different pieces of infrastructure fit 00:04:35.570 --> 00:04:38.590 align:start position:0% different pieces of infrastructure fit well<00:04:35.750> together<00:04:35.900> while<00:04:36.890> dealing<00:04:37.130> with<00:04:37.600> actual 00:04:38.590 --> 00:04:38.600 align:start position:0% well together while dealing with actual 00:04:38.600 --> 00:04:41.530 align:start position:0% well together while dealing with actual individuals<00:04:39.110> so<00:04:40.150> things<00:04:41.150> that<00:04:41.270> are<00:04:41.360> going<00:04:41.450> to 00:04:41.530 --> 00:04:41.540 align:start position:0% individuals so things that are going to 00:04:41.540 --> 00:04:44.760 align:start position:0% individuals so things that are going to fold<00:04:41.720> into<00:04:41.870> this<00:04:42.110> like<00:04:42.770> reputation 00:04:44.760 --> 00:04:44.770 align:start position:0% fold into this like reputation 00:04:44.770 --> 00:04:47.590 align:start position:0% fold into this like reputation potentially<00:04:45.770> stuff<00:04:46.760> to<00:04:46.910> do<00:04:47.030> with<00:04:47.210> the<00:04:47.300> outside 00:04:47.590 --> 00:04:47.600 align:start position:0% potentially stuff to do with the outside 00:04:47.600 --> 00:04:51.040 align:start position:0% potentially stuff to do with the outside world<00:04:48.580> my<00:04:49.580> email<00:04:49.880> address<00:04:50.180> my<00:04:50.210> website<00:04:50.750> and<00:04:50.930> so 00:04:51.040 --> 00:04:51.050 align:start position:0% world my email address my website and so 00:04:51.050 --> 00:04:54.310 align:start position:0% world my email address my website and so on<00:04:52.060> this<00:04:53.060> is<00:04:53.210> in<00:04:53.420> some<00:04:53.660> sense<00:04:53.870> already 00:04:54.310 --> 00:04:54.320 align:start position:0% on this is in some sense already 00:04:54.320 --> 00:04:56.260 align:start position:0% on this is in some sense already addressed<00:04:55.070> with<00:04:55.310> the<00:04:55.430> notion<00:04:55.580> of<00:04:55.850> like<00:04:56.090> this 00:04:56.260 --> 00:04:56.270 align:start position:0% addressed with the notion of like this 00:04:56.270 --> 00:04:58.120 align:start position:0% addressed with the notion of like this 160-bit<00:04:56.930> address<00:04:57.290> scheme<00:04:57.500> that<00:04:57.620> we<00:04:57.740> have<00:04:57.890> but 00:04:58.120 --> 00:04:58.130 align:start position:0% 160-bit address scheme that we have but 00:04:58.130 --> 00:05:01.330 align:start position:0% 160-bit address scheme that we have but I<00:04:58.430> think<00:04:59.260> yeah<00:05:00.260> it's<00:05:00.500> worth<00:05:00.740> considering<00:05:01.130> a 00:05:01.330 --> 00:05:01.340 align:start position:0% I think yeah it's worth considering a 00:05:01.340 --> 00:05:04.030 align:start position:0% I think yeah it's worth considering a bit<00:05:01.490> a<00:05:01.640> bit<00:05:01.850> deeper<00:05:02.000> and<00:05:02.240> how<00:05:02.450> this<00:05:02.600> might<00:05:03.040> feed 00:05:04.030 --> 00:05:04.040 align:start position:0% bit a bit deeper and how this might feed 00:05:04.040 --> 00:05:06.850 align:start position:0% bit a bit deeper and how this might feed back<00:05:04.340> into<00:05:04.370> things<00:05:04.880> like<00:05:05.380> avatars<00:05:06.380> that<00:05:06.590> go 00:05:06.850 --> 00:05:06.860 align:start position:0% back into things like avatars that go 00:05:06.860 --> 00:05:09.580 align:start position:0% back into things like avatars that go across<00:05:07.300> the<00:05:08.300> various<00:05:08.390> applications<00:05:09.230> within 00:05:09.580 --> 00:05:09.590 align:start position:0% across the various applications within 00:05:09.590 --> 00:05:11.470 align:start position:0% across the various applications within the<00:05:09.860> etherium<00:05:10.700> and<00:05:10.850> sort<00:05:11.000> of<00:05:11.060> web<00:05:11.210> three 00:05:11.470 --> 00:05:11.480 align:start position:0% the etherium and sort of web three 00:05:11.480 --> 00:05:14.560 align:start position:0% the etherium and sort of web three at-large<00:05:11.600> ecosystem<00:05:12.790> I'd<00:05:13.790> also<00:05:14.150> note<00:05:14.300> that 00:05:14.560 --> 00:05:14.570 align:start position:0% at-large ecosystem I'd also note that 00:05:14.570 --> 00:05:16.510 align:start position:0% at-large ecosystem I'd also note that the<00:05:14.810> other<00:05:14.930> thing<00:05:15.170> we<00:05:16.070> tend<00:05:16.280> to<00:05:16.310> think<00:05:16.370> about 00:05:16.510 --> 00:05:16.520 align:start position:0% the other thing we tend to think about 00:05:16.520 --> 00:05:18.160 align:start position:0% the other thing we tend to think about standard<00:05:17.120> is<00:05:17.240> something<00:05:17.540> that<00:05:17.660> you<00:05:17.810> know<00:05:17.930> that 00:05:18.160 --> 00:05:18.170 align:start position:0% standard is something that you know that 00:05:18.170 --> 00:05:21.340 align:start position:0% standard is something that you know that they<00:05:18.290> tend<00:05:18.500> to<00:05:18.530> be<00:05:18.650> kind<00:05:18.800> of<00:05:18.890> opt-in<00:05:19.310> and<00:05:20.350> we 00:05:21.340 --> 00:05:21.350 align:start position:0% they tend to be kind of opt-in and we 00:05:21.350 --> 00:05:22.960 align:start position:0% they tend to be kind of opt-in and we need<00:05:21.680> standards<00:05:22.280> in<00:05:22.580> order<00:05:22.670> to<00:05:22.880> have 00:05:22.960 --> 00:05:22.970 align:start position:0% need standards in order to have 00:05:22.970 --> 00:05:24.400 align:start position:0% need standards in order to have interoperability<00:05:23.330> right<00:05:23.990> different 00:05:24.400 --> 00:05:24.410 align:start position:0% interoperability right different 00:05:24.410 --> 00:05:25.810 align:start position:0% interoperability right different applications<00:05:24.920> implement<00:05:25.250> the<00:05:25.310> same<00:05:25.460> standard 00:05:25.810 --> 00:05:25.820 align:start position:0% applications implement the same standard 00:05:25.820 --> 00:05:27.220 align:start position:0% applications implement the same standard so<00:05:25.970> they<00:05:26.180> can<00:05:26.360> they<00:05:26.630> can<00:05:26.660> they<00:05:26.840> can<00:05:27.020> operate 00:05:27.220 --> 00:05:27.230 align:start position:0% so they can they can they can operate 00:05:27.230 --> 00:05:28.990 align:start position:0% so they can they can they can operate with<00:05:27.530> each<00:05:27.650> other<00:05:27.800> but<00:05:28.280> actually<00:05:28.730> one<00:05:28.880> of<00:05:28.910> the 00:05:28.990 --> 00:05:29.000 align:start position:0% with each other but actually one of the 00:05:29.000 --> 00:05:30.970 align:start position:0% with each other but actually one of the great<00:05:29.330> things<00:05:29.630> about<00:05:29.810> etherium<00:05:30.500> is<00:05:30.650> that<00:05:30.860> this 00:05:30.970 --> 00:05:30.980 align:start position:0% great things about etherium is that this 00:05:30.980 --> 00:05:34.210 align:start position:0% great things about etherium is that this is<00:05:31.220> a<00:05:32.590> fundamentally<00:05:33.590> programmatic 00:05:34.210 --> 00:05:34.220 align:start position:0% is a fundamentally programmatic 00:05:34.220 --> 00:05:37.930 align:start position:0% is a fundamentally programmatic infrastructure<00:05:34.760> so<00:05:35.060> we<00:05:35.810> have<00:05:36.400> the<00:05:37.400> notion<00:05:37.610> of 00:05:37.930 --> 00:05:37.940 align:start position:0% infrastructure so we have the notion of 00:05:37.940 --> 00:05:40.210 align:start position:0% infrastructure so we have the notion of objects<00:05:38.720> existing<00:05:39.170> within<00:05:39.530> the<00:05:39.740> system<00:05:40.100> and 00:05:40.210 --> 00:05:40.220 align:start position:0% objects existing within the system and 00:05:40.220 --> 00:05:43.240 align:start position:0% objects existing within the system and these<00:05:40.940> kind<00:05:41.840> of<00:05:41.990> already<00:05:42.350> enforce<00:05:43.070> standards 00:05:43.240 --> 00:05:43.250 align:start position:0% these kind of already enforce standards 00:05:43.250 --> 00:05:44.950 align:start position:0% these kind of already enforce standards because<00:05:43.580> they<00:05:43.760> have<00:05:43.850> an<00:05:43.940> API<00:05:44.210> and<00:05:44.540> if<00:05:44.690> you<00:05:44.780> want 00:05:44.950 --> 00:05:44.960 align:start position:0% because they have an API and if you want 00:05:44.960 --> 00:05:46.810 align:start position:0% because they have an API and if you want to<00:05:45.050> interact<00:05:45.290> with<00:05:45.530> this<00:05:45.770> with<00:05:46.190> this<00:05:46.220> object 00:05:46.810 --> 00:05:46.820 align:start position:0% to interact with this with this object 00:05:46.820 --> 00:05:48.430 align:start position:0% to interact with this with this object that<00:05:46.910> sits<00:05:47.120> at<00:05:47.240> the<00:05:47.270> center<00:05:47.330> of<00:05:47.690> subsystem 00:05:48.430 --> 00:05:48.440 align:start position:0% that sits at the center of subsystem 00:05:48.440 --> 00:05:49.570 align:start position:0% that sits at the center of subsystem that<00:05:48.470> you<00:05:48.710> that<00:05:48.890> you<00:05:48.980> do<00:05:49.100> want<00:05:49.280> to<00:05:49.340> operate 00:05:49.570 --> 00:05:49.580 align:start position:0% that you that you do want to operate 00:05:49.580 --> 00:05:51.970 align:start position:0% that you that you do want to operate with<00:05:49.880> then<00:05:50.090> you<00:05:50.570> just<00:05:50.810> use<00:05:51.140> the<00:05:51.290> API<00:05:51.560> and<00:05:51.890> the 00:05:51.970 --> 00:05:51.980 align:start position:0% with then you just use the API and the 00:05:51.980 --> 00:05:54.790 align:start position:0% with then you just use the API and the API<00:05:52.250> is<00:05:52.370> a<00:05:52.550> standard<00:05:53.090> it's<00:05:53.240> already<00:05:53.540> there<00:05:53.800> and 00:05:54.790 --> 00:05:54.800 align:start position:0% API is a standard it's already there and 00:05:54.800 --> 00:05:56.970 align:start position:0% API is a standard it's already there and there's<00:05:55.040> no<00:05:55.220> real<00:05:55.640> prejudice<00:05:56.270> because 00:05:56.970 --> 00:05:56.980 align:start position:0% there's no real prejudice because 00:05:56.980 --> 00:05:58.990 align:start position:0% there's no real prejudice because assuming<00:05:57.980> that<00:05:58.100> it's<00:05:58.220> been<00:05:58.370> implemented<00:05:58.910> in 00:05:58.990 --> 00:05:59.000 align:start position:0% assuming that it's been implemented in 00:05:59.000 --> 00:06:00.700 align:start position:0% assuming that it's been implemented in some<00:05:59.240> reasonably<00:05:59.780> fair<00:06:00.050> way<00:06:00.290> and<00:06:00.500> you<00:06:00.560> can 00:06:00.700 --> 00:06:00.710 align:start position:0% some reasonably fair way and you can 00:06:00.710 --> 00:06:03.060 align:start position:0% some reasonably fair way and you can check<00:06:00.890> because<00:06:01.100> there's<00:06:01.310> a<00:06:01.370> code<00:06:01.580> there<00:06:01.820> then 00:06:03.060 --> 00:06:03.070 align:start position:0% check because there's a code there then 00:06:03.070 --> 00:06:06.160 align:start position:0% check because there's a code there then we<00:06:04.070> can<00:06:04.250> already<00:06:04.430> kind<00:06:05.060> of<00:06:05.150> pre<00:06:05.510> agree<00:06:05.870> to<00:06:06.050> the 00:06:06.160 --> 00:06:06.170 align:start position:0% we can already kind of pre agree to the 00:06:06.170 --> 00:06:09.910 align:start position:0% we can already kind of pre agree to the standard<00:06:06.530> that<00:06:06.820> go<00:06:07.990> if<00:06:08.990> someone<00:06:09.350> makes<00:06:09.770> a 00:06:09.910 --> 00:06:09.920 align:start position:0% standard that go if someone makes a 00:06:09.920 --> 00:06:11.500 align:start position:0% standard that go if someone makes a token<00:06:10.250> that<00:06:10.370> doesn't<00:06:10.670> conform<00:06:10.940> to<00:06:11.180> the<00:06:11.270> normal 00:06:11.500 --> 00:06:11.510 align:start position:0% token that doesn't conform to the normal 00:06:11.510 --> 00:06:14.110 align:start position:0% token that doesn't conform to the normal standards<00:06:11.960> then<00:06:12.440> you<00:06:13.130> know<00:06:13.250> maybe<00:06:13.610> ether<00:06:13.940> X 00:06:14.110 --> 00:06:14.120 align:start position:0% standards then you know maybe ether X 00:06:14.120 --> 00:06:16.030 align:start position:0% standards then you know maybe ether X you<00:06:14.540> change<00:06:14.750> last<00:06:15.020> exchange<00:06:15.230> wouldn't<00:06:15.920> then 00:06:16.030 --> 00:06:16.040 align:start position:0% you change last exchange wouldn't then 00:06:16.040 --> 00:06:17.620 align:start position:0% you change last exchange wouldn't then be<00:06:16.160> able<00:06:16.400> to<00:06:16.550> use<00:06:16.730> those<00:06:16.940> tokens<00:06:17.210> but 00:06:17.620 --> 00:06:17.630 align:start position:0% be able to use those tokens but 00:06:17.630 --> 00:06:19.390 align:start position:0% be able to use those tokens but considering<00:06:18.530> that<00:06:18.560> the<00:06:18.800> code<00:06:18.950> is<00:06:18.980> open<00:06:19.220> source 00:06:19.390 --> 00:06:19.400 align:start position:0% considering that the code is open source 00:06:19.400 --> 00:06:22.090 align:start position:0% considering that the code is open source you<00:06:19.850> can<00:06:19.880> just<00:06:20.240> clone<00:06:21.110> either<00:06:21.320> X<00:06:21.590> and<00:06:21.770> making 00:06:22.090 --> 00:06:22.100 align:start position:0% you can just clone either X and making 00:06:22.100 --> 00:06:24.310 align:start position:0% you can just clone either X and making it<00:06:22.190> exchange<00:06:22.790> for<00:06:23.150> your<00:06:23.330> standard<00:06:23.750> as<00:06:23.900> well<00:06:24.050> so 00:06:24.310 --> 00:06:24.320 align:start position:0% it exchange for your standard as well so 00:06:24.320 --> 00:06:27.310 align:start position:0% it exchange for your standard as well so that's<00:06:24.590> it's<00:06:24.920> great<00:06:25.130> in<00:06:25.310> that<00:06:25.520> manner<00:06:25.760> the<00:06:26.510> the 00:06:27.310 --> 00:06:27.320 align:start position:0% that's it's great in that manner the the 00:06:27.320 --> 00:06:30.820 align:start position:0% that's it's great in that manner the the topic<00:06:27.620> of<00:06:27.770> my<00:06:27.890> identity<00:06:28.670> I<00:06:29.380> want<00:06:30.380> to<00:06:30.410> come<00:06:30.770> back 00:06:30.820 --> 00:06:30.830 align:start position:0% topic of my identity I want to come back 00:06:30.830 --> 00:06:32.560 align:start position:0% topic of my identity I want to come back to<00:06:31.070> that<00:06:31.100> I<00:06:31.250> think<00:06:31.520> it's<00:06:31.640> a<00:06:31.730> it's<00:06:31.970> an<00:06:32.180> important 00:06:32.560 --> 00:06:32.570 align:start position:0% to that I think it's a it's an important 00:06:32.570 --> 00:06:34.270 align:start position:0% to that I think it's a it's an important one<00:06:32.720> because 00:06:34.270 --> 00:06:34.280 align:start position:0% one because 00:06:34.280 --> 00:06:36.580 align:start position:0% one because as<00:06:34.610> far<00:06:35.030> as<00:06:35.060> I<00:06:35.210> know<00:06:35.330> it<00:06:35.420> hasn't<00:06:35.600> been<00:06:35.810> we 00:06:36.580 --> 00:06:36.590 align:start position:0% as far as I know it hasn't been we 00:06:36.590 --> 00:06:39.070 align:start position:0% as far as I know it hasn't been we haven't<00:06:36.620> specified<00:06:37.130> anything<00:06:38.030> yet<00:06:38.240> this<00:06:38.600> in 00:06:39.070 --> 00:06:39.080 align:start position:0% haven't specified anything yet this in 00:06:39.080 --> 00:06:41.680 align:start position:0% haven't specified anything yet this in what<00:06:39.500> like<00:06:40.160> how<00:06:40.340> it<00:06:40.400> should<00:06:40.790> work<00:06:40.820> and<00:06:41.210> are<00:06:41.270> the 00:06:41.680 --> 00:06:41.690 align:start position:0% what like how it should work and are the 00:06:41.690 --> 00:06:45.040 align:start position:0% what like how it should work and are the ideal<00:06:41.990> version<00:06:42.170> of<00:06:42.470> it<00:06:42.590> should<00:06:43.100> work<00:06:44.050> the 00:06:45.040 --> 00:06:45.050 align:start position:0% ideal version of it should work the 00:06:45.050 --> 00:06:47.800 align:start position:0% ideal version of it should work the Christian<00:06:45.410> you<00:06:45.620> yesterday<00:06:46.630> explain<00:06:47.630> more 00:06:47.800 --> 00:06:47.810 align:start position:0% Christian you yesterday explain more 00:06:47.810 --> 00:06:49.629 align:start position:0% Christian you yesterday explain more about<00:06:47.870> you<00:06:48.350> port<00:06:48.650> work<00:06:48.860> what's<00:06:49.190> the<00:06:49.370> sort<00:06:49.580> of 00:06:49.629 --> 00:06:49.639 align:start position:0% about you port work what's the sort of 00:06:49.639 --> 00:06:55.300 align:start position:0% about you port work what's the sort of the<00:06:50.560> the<00:06:51.820> idea<00:06:52.820> or<00:06:53.060> design<00:06:53.650> goal<00:06:54.650> of<00:06:54.830> that<00:06:55.040> is 00:06:55.300 --> 00:06:55.310 align:start position:0% the the idea or design goal of that is 00:06:55.310 --> 00:06:58.330 align:start position:0% the the idea or design goal of that is it<00:06:55.610> sort<00:06:56.090> of<00:06:56.150> the<00:06:56.330> idea<00:06:56.360> that<00:06:56.660> you<00:06:56.960> take<00:06:57.340> you 00:06:58.330 --> 00:06:58.340 align:start position:0% it sort of the idea that you take you 00:06:58.340 --> 00:07:00.070 align:start position:0% it sort of the idea that you take you keep<00:06:58.550> your<00:06:58.700> identity<00:06:59.150> in<00:06:59.419> the<00:06:59.570> browser<00:06:59.780> and 00:07:00.070 --> 00:07:00.080 align:start position:0% keep your identity in the browser and 00:07:00.080 --> 00:07:01.450 align:start position:0% keep your identity in the browser and then<00:07:00.200> you<00:07:00.290> move<00:07:00.470> it<00:07:00.590> between<00:07:00.889> certain<00:07:01.100> depth 00:07:01.450 --> 00:07:01.460 align:start position:0% then you move it between certain depth 00:07:01.460 --> 00:07:03.790 align:start position:0% then you move it between certain depth what<00:07:02.240> about<00:07:02.360> sort<00:07:02.810> of<00:07:02.870> examples<00:07:03.440> where<00:07:03.590> you 00:07:03.790 --> 00:07:03.800 align:start position:0% what about sort of examples where you 00:07:03.800 --> 00:07:06.640 align:start position:0% what about sort of examples where you have<00:07:03.919> a<00:07:03.980> phone<00:07:04.310> client<00:07:04.850> or<00:07:05.030> you<00:07:05.270> have<00:07:05.510> a<00:07:05.810> web 00:07:06.640 --> 00:07:06.650 align:start position:0% have a phone client or you have a web 00:07:06.650 --> 00:07:08.230 align:start position:0% have a phone client or you have a web browser<00:07:06.950> client<00:07:07.490> or<00:07:07.610> something<00:07:07.850> like<00:07:07.970> Minna 00:07:08.230 --> 00:07:08.240 align:start position:0% browser client or something like Minna 00:07:08.240 --> 00:07:10.540 align:start position:0% browser client or something like Minna mask<00:07:08.510> or<00:07:08.780> something<00:07:08.810> like<00:07:09.350> ha<00:07:09.560> what's<00:07:09.950> the<00:07:10.100> we 00:07:10.540 --> 00:07:10.550 align:start position:0% mask or something like ha what's the we 00:07:10.550 --> 00:07:12.640 align:start position:0% mask or something like ha what's the we think<00:07:10.760> is<00:07:10.820> most<00:07:10.970> ideal<00:07:11.360> way<00:07:11.570> to<00:07:11.600> just<00:07:12.440> swap 00:07:12.640 --> 00:07:12.650 align:start position:0% think is most ideal way to just swap 00:07:12.650 --> 00:07:14.940 align:start position:0% think is most ideal way to just swap identities<00:07:12.950> through<00:07:13.760> different<00:07:14.210> interfaces 00:07:14.940 --> 00:07:14.950 align:start position:0% identities through different interfaces 00:07:14.950 --> 00:07:19.870 align:start position:0% identities through different interfaces yeah<00:07:16.360> so<00:07:17.360> this<00:07:17.540> is<00:07:17.570> of<00:07:18.020> course<00:07:18.320> a<00:07:18.770> big<00:07:19.280> question 00:07:19.870 --> 00:07:19.880 align:start position:0% yeah so this is of course a big question 00:07:19.880 --> 00:07:25.090 align:start position:0% yeah so this is of course a big question and<00:07:20.830> the<00:07:21.830> the<00:07:22.370> notion<00:07:22.730> of<00:07:22.820> using<00:07:23.830> you<00:07:24.830> know<00:07:24.950> the 00:07:25.090 --> 00:07:25.100 align:start position:0% and the the notion of using you know the 00:07:25.100 --> 00:07:28.030 align:start position:0% and the the notion of using you know the same<00:07:25.310> identity<00:07:25.700> on<00:07:26.030> multiple<00:07:26.720> devices<00:07:27.040> that 00:07:28.030 --> 00:07:28.040 align:start position:0% same identity on multiple devices that 00:07:28.040 --> 00:07:30.520 align:start position:0% same identity on multiple devices that ultimately<00:07:29.000> comes<00:07:29.360> down<00:07:29.450> to<00:07:29.780> key<00:07:30.110> management 00:07:30.520 --> 00:07:30.530 align:start position:0% ultimately comes down to key management 00:07:30.530 --> 00:07:33.690 align:start position:0% ultimately comes down to key management which<00:07:31.220> is<00:07:31.430> you<00:07:32.120> know<00:07:32.150> might<00:07:32.479> be<00:07:32.510> one<00:07:32.960> of<00:07:32.990> the 00:07:33.690 --> 00:07:33.700 align:start position:0% which is you know might be one of the 00:07:33.700 --> 00:07:36.610 align:start position:0% which is you know might be one of the greatest<00:07:34.700> challenges<00:07:35.540> of<00:07:35.780> of<00:07:35.990> this<00:07:36.380> whole 00:07:36.610 --> 00:07:36.620 align:start position:0% greatest challenges of of this whole 00:07:36.620 --> 00:07:40.540 align:start position:0% greatest challenges of of this whole endeavor<00:07:38.050> how<00:07:39.050> to<00:07:39.110> have<00:07:39.470> key<00:07:39.740> management<00:07:40.100> with 00:07:40.540 --> 00:07:40.550 align:start position:0% endeavor how to have key management with 00:07:40.550 --> 00:07:47.469 align:start position:0% endeavor how to have key management with with<00:07:40.970> a<00:07:41.000> good<00:07:41.330> ux<00:07:42.729> i<00:07:44.320> think<00:07:45.700> yeah<00:07:46.700> I<00:07:46.729> identity 00:07:47.469 --> 00:07:47.479 align:start position:0% with a good ux i think yeah I identity 00:07:47.479 --> 00:07:52.570 align:start position:0% with a good ux i think yeah I identity is<00:07:47.570> of<00:07:47.750> course<00:07:48.880> very<00:07:49.880> important<00:07:50.539> and<00:07:50.840> and<00:07:51.580> I'm 00:07:52.570 --> 00:07:52.580 align:start position:0% is of course very important and and I'm 00:07:52.580 --> 00:07:58.360 align:start position:0% is of course very important and and I'm glad<00:07:54.310> I'm<00:07:55.310> glad<00:07:55.520> you<00:07:55.729> brought<00:07:55.940> it<00:07:56.150> up<00:07:57.370> an 00:07:58.360 --> 00:07:58.370 align:start position:0% glad I'm glad you brought it up an 00:07:58.370 --> 00:08:02.980 align:start position:0% glad I'm glad you brought it up an interesting<00:07:59.090> thing<00:07:59.360> there<00:07:59.600> is<00:07:59.890> so<00:08:01.960> when<00:08:02.960> I 00:08:02.980 --> 00:08:02.990 align:start position:0% interesting thing there is so when I 00:08:02.990 --> 00:08:05.080 align:start position:0% interesting thing there is so when I think<00:08:03.260> about<00:08:03.320> them<00:08:03.650> today<00:08:03.800> I<00:08:03.919> I<00:08:04.010> describe<00:08:04.700> the 00:08:05.080 --> 00:08:05.090 align:start position:0% think about them today I I describe the 00:08:05.090 --> 00:08:08.890 align:start position:0% think about them today I I describe the the<00:08:05.630> kind<00:08:06.200> of<00:08:06.350> general<00:08:06.950> outline<00:08:07.910> in<00:08:08.180> my<00:08:08.539> talk 00:08:08.890 --> 00:08:08.900 align:start position:0% the kind of general outline in my talk 00:08:08.900 --> 00:08:14.110 align:start position:0% the kind of general outline in my talk and<00:08:10.390> the<00:08:11.590> the<00:08:12.590> key<00:08:13.100> management<00:08:13.490> issue<00:08:13.760> is<00:08:13.970> very 00:08:14.110 --> 00:08:14.120 align:start position:0% and the the key management issue is very 00:08:14.120 --> 00:08:16.990 align:start position:0% and the the key management issue is very important<00:08:14.630> so<00:08:14.870> I<00:08:15.110> think<00:08:15.620> we<00:08:15.919> have<00:08:15.950> to<00:08:16.490> have<00:08:16.729> a 00:08:16.990 --> 00:08:17.000 align:start position:0% important so I think we have to have a 00:08:17.000 --> 00:08:20.940 align:start position:0% important so I think we have to have a system<00:08:17.720> of<00:08:17.900> identity<00:08:18.440> where<00:08:19.270> even<00:08:20.270> if<00:08:20.450> you 00:08:20.940 --> 00:08:20.950 align:start position:0% system of identity where even if you 00:08:20.950 --> 00:08:23.710 align:start position:0% system of identity where even if you even<00:08:21.950> if<00:08:22.039> you<00:08:22.160> lose<00:08:22.340> your<00:08:22.669> private<00:08:23.210> key<00:08:23.419> you 00:08:23.710 --> 00:08:23.720 align:start position:0% even if you lose your private key you 00:08:23.720 --> 00:08:25.990 align:start position:0% even if you lose your private key you don't<00:08:23.900> lose<00:08:24.050> your<00:08:24.260> identity<00:08:24.380> so<00:08:25.370> then<00:08:25.610> we<00:08:25.789> come 00:08:25.990 --> 00:08:26.000 align:start position:0% don't lose your identity so then we come 00:08:26.000 --> 00:08:29.320 align:start position:0% don't lose your identity so then we come into<00:08:26.210> a<00:08:26.979> the<00:08:27.979> fact<00:08:28.310> that<00:08:28.430> in<00:08:28.729> the<00:08:29.150> current 00:08:29.320 --> 00:08:29.330 align:start position:0% into a the fact that in the current 00:08:29.330 --> 00:08:34.270 align:start position:0% into a the fact that in the current system<00:08:30.580> contracts<00:08:31.580> always<00:08:32.030> interact<00:08:33.280> with 00:08:34.270 --> 00:08:34.280 align:start position:0% system contracts always interact with 00:08:34.280 --> 00:08:38.020 align:start position:0% system contracts always interact with keys<00:08:34.640> so<00:08:35.479> you<00:08:35.539> have<00:08:36.110> access<00:08:36.500> control<00:08:36.950> in<00:08:37.280> the 00:08:38.020 --> 00:08:38.030 align:start position:0% keys so you have access control in the 00:08:38.030 --> 00:08:40.959 align:start position:0% keys so you have access control in the form<00:08:38.330> of<00:08:38.510> you<00:08:39.380> know<00:08:39.500> if<00:08:39.740> message<00:08:40.280> tops<00:08:40.550> under 00:08:40.959 --> 00:08:40.969 align:start position:0% form of you know if message tops under 00:08:40.969 --> 00:08:43.659 align:start position:0% form of you know if message tops under equals<00:08:41.570> this<00:08:41.839> address<00:08:42.349> then<00:08:42.740> do<00:08:43.430> this 00:08:43.659 --> 00:08:43.669 align:start position:0% equals this address then do this 00:08:43.669 --> 00:08:46.100 align:start position:0% equals this address then do this otherwise<00:08:44.150> do<00:08:44.870> something<00:08:45.200> else 00:08:46.100 --> 00:08:46.110 align:start position:0% otherwise do something else 00:08:46.110 --> 00:08:51.590 align:start position:0% otherwise do something else and<00:08:46.760> that<00:08:48.680> that<00:08:49.680> works<00:08:50.130> in<00:08:50.610> the<00:08:50.790> context<00:08:51.480> of 00:08:51.590 --> 00:08:51.600 align:start position:0% and that that works in the context of 00:08:51.600 --> 00:08:53.569 align:start position:0% and that that works in the context of identity<00:08:52.110> because<00:08:52.529> you<00:08:52.680> can<00:08:52.860> have<00:08:53.070> a<00:08:53.100> look<00:08:53.190> up 00:08:53.569 --> 00:08:53.579 align:start position:0% identity because you can have a look up 00:08:53.579 --> 00:08:57.610 align:start position:0% identity because you can have a look up that<00:08:54.029> goes<00:08:54.329> from<00:08:54.600> from<00:08:55.350> key<00:08:55.649> to<00:08:55.980> to<00:08:56.850> identity 00:08:57.610 --> 00:08:57.620 align:start position:0% that goes from from key to to identity 00:08:57.620 --> 00:09:02.030 align:start position:0% that goes from from key to to identity but<00:08:58.620> it's<00:08:59.160> an<00:08:59.370> interesting<00:09:00.800> thing<00:09:01.800> to<00:09:01.829> think 00:09:02.030 --> 00:09:02.040 align:start position:0% but it's an interesting thing to think 00:09:02.040 --> 00:09:06.530 align:start position:0% but it's an interesting thing to think about<00:09:02.510> if<00:09:04.130> you<00:09:05.130> know<00:09:05.279> if<00:09:05.579> we<00:09:06.149> should<00:09:06.180> think 00:09:06.530 --> 00:09:06.540 align:start position:0% about if you know if we should think 00:09:06.540 --> 00:09:08.300 align:start position:0% about if you know if we should think about<00:09:06.660> an<00:09:06.870> access<00:09:07.170> control<00:09:07.290> system<00:09:08.040> that 00:09:08.300 --> 00:09:08.310 align:start position:0% about an access control system that 00:09:08.310 --> 00:09:10.730 align:start position:0% about an access control system that works<00:09:08.579> on<00:09:08.790> the<00:09:08.910> level<00:09:09.120> of<00:09:09.500> identities<00:09:10.500> rather 00:09:10.730 --> 00:09:10.740 align:start position:0% works on the level of identities rather 00:09:10.740 --> 00:09:14.449 align:start position:0% works on the level of identities rather than<00:09:10.980> keys<00:09:11.279> so<00:09:12.740> so<00:09:13.740> in<00:09:13.890> my<00:09:14.040> mind<00:09:14.070> and 00:09:14.449 --> 00:09:14.459 align:start position:0% than keys so so in my mind and 00:09:14.459 --> 00:09:16.610 align:start position:0% than keys so so in my mind and identities<00:09:14.970> is<00:09:15.329> kind<00:09:15.690> of<00:09:15.779> a<00:09:15.899> cryptographic 00:09:16.610 --> 00:09:16.620 align:start position:0% identities is kind of a cryptographic 00:09:16.620 --> 00:09:20.690 align:start position:0% identities is kind of a cryptographic identifier<00:09:17.430> so<00:09:17.820> maybe<00:09:18.089> a<00:09:18.769> 32<00:09:19.769> byte<00:09:20.130> hash<00:09:20.430> or 00:09:20.690 --> 00:09:20.700 align:start position:0% identifier so maybe a 32 byte hash or 00:09:20.700 --> 00:09:24.620 align:start position:0% identifier so maybe a 32 byte hash or something<00:09:21.029> and<00:09:21.180> then<00:09:21.810> the<00:09:22.370> the<00:09:23.630> contract 00:09:24.620 --> 00:09:24.630 align:start position:0% something and then the the contract 00:09:24.630 --> 00:09:27.730 align:start position:0% something and then the the contract could<00:09:25.560> say<00:09:26.160> ok<00:09:26.579> I'm<00:09:26.850> getting<00:09:27.029> this<00:09:27.209> message 00:09:27.730 --> 00:09:27.740 align:start position:0% could say ok I'm getting this message 00:09:27.740 --> 00:09:31.250 align:start position:0% could say ok I'm getting this message going<00:09:28.740> to<00:09:28.829> look<00:09:29.010> up<00:09:29.190> if<00:09:29.459> it's<00:09:29.670> you<00:09:30.660> know<00:09:30.779> maybe 00:09:31.250 --> 00:09:31.260 align:start position:0% going to look up if it's you know maybe 00:09:31.260 --> 00:09:35.150 align:start position:0% going to look up if it's you know maybe it's<00:09:31.529> just<00:09:31.620> the<00:09:31.769> key<00:09:32.100> then<00:09:32.459> do<00:09:32.910> this<00:09:33.149> if<00:09:33.529> I<00:09:34.529> if<00:09:34.769> I 00:09:35.150 --> 00:09:35.160 align:start position:0% it's just the key then do this if I if I 00:09:35.160 --> 00:09:38.120 align:start position:0% it's just the key then do this if I if I if<00:09:35.880> I<00:09:36.390> do<00:09:36.450> a<00:09:36.540> look<00:09:36.779> up<00:09:36.959> and<00:09:37.260> see<00:09:37.440> oh<00:09:37.620> this<00:09:38.010> is 00:09:38.120 --> 00:09:38.130 align:start position:0% if I do a look up and see oh this is 00:09:38.130 --> 00:09:40.220 align:start position:0% if I do a look up and see oh this is actually<00:09:38.430> an<00:09:38.490> identity<00:09:39.120> then<00:09:39.839> I<00:09:39.930> can<00:09:40.110> have 00:09:40.220 --> 00:09:40.230 align:start position:0% actually an identity then I can have 00:09:40.230 --> 00:09:41.870 align:start position:0% actually an identity then I can have access<00:09:40.560> control<00:09:41.010> on<00:09:41.220> the<00:09:41.339> level<00:09:41.519> of<00:09:41.670> that 00:09:41.870 --> 00:09:41.880 align:start position:0% access control on the level of that 00:09:41.880 --> 00:09:44.500 align:start position:0% access control on the level of that identity<00:09:42.060> and<00:09:42.690> so<00:09:42.930> then<00:09:43.140> you<00:09:43.740> can<00:09:43.860> keep<00:09:44.100> using 00:09:44.500 --> 00:09:44.510 align:start position:0% identity and so then you can keep using 00:09:44.510 --> 00:09:47.600 align:start position:0% identity and so then you can keep using these<00:09:45.510> contracts<00:09:46.320> even<00:09:46.980> if<00:09:47.070> you<00:09:47.160> rotate<00:09:47.579> your 00:09:47.600 --> 00:09:47.610 align:start position:0% these contracts even if you rotate your 00:09:47.610 --> 00:09:51.410 align:start position:0% these contracts even if you rotate your keys<00:09:48.000> for<00:09:48.329> your<00:09:48.450> identity<00:09:48.990> so<00:09:49.890> that's<00:09:50.420> that's 00:09:51.410 --> 00:09:51.420 align:start position:0% keys for your identity so that's that's 00:09:51.420 --> 00:09:53.480 align:start position:0% keys for your identity so that's that's something<00:09:52.079> to<00:09:52.110> think<00:09:52.230> about<00:09:52.560> and<00:09:52.980> that<00:09:53.220> of 00:09:53.480 --> 00:09:53.490 align:start position:0% something to think about and that of 00:09:53.490 --> 00:09:56.420 align:start position:0% something to think about and that of course<00:09:53.720> you<00:09:54.720> know<00:09:54.839> if<00:09:54.959> we<00:09:55.140> want<00:09:55.350> to<00:09:55.440> go<00:09:55.680> down<00:09:56.399> a 00:09:56.420 --> 00:09:56.430 align:start position:0% course you know if we want to go down a 00:09:56.430 --> 00:09:59.630 align:start position:0% course you know if we want to go down a path<00:09:56.640> like<00:09:57.029> that<00:09:57.300> it<00:09:57.779> requires<00:09:58.290> it<00:09:59.220> requires 00:09:59.630 --> 00:09:59.640 align:start position:0% path like that it requires it requires 00:09:59.640 --> 00:10:01.699 align:start position:0% path like that it requires it requires standardization<00:10:00.540> in<00:10:00.720> how<00:10:01.050> we<00:10:01.110> construct 00:10:01.699 --> 00:10:01.709 align:start position:0% standardization in how we construct 00:10:01.709 --> 00:10:05.810 align:start position:0% standardization in how we construct these<00:10:02.149> these<00:10:03.149> contracts<00:10:04.250> yeah<00:10:05.250> it<00:10:05.399> does<00:10:05.550> paint 00:10:05.810 --> 00:10:05.820 align:start position:0% these these contracts yeah it does paint 00:10:05.820 --> 00:10:10.370 align:start position:0% these these contracts yeah it does paint a<00:10:07.459> potential<00:10:08.459> issue<00:10:08.579> that<00:10:09.029> if<00:10:09.600> a<00:10:09.899> lot<00:10:10.079> of<00:10:10.230> that 00:10:10.370 --> 00:10:10.380 align:start position:0% a potential issue that if a lot of that 00:10:10.380 --> 00:10:12.290 align:start position:0% a potential issue that if a lot of that current<00:10:11.160> apps<00:10:11.339> are<00:10:11.490> going<00:10:11.640> to<00:10:11.699> use<00:10:11.910> the<00:10:12.149> normal 00:10:12.290 --> 00:10:12.300 align:start position:0% current apps are going to use the normal 00:10:12.300 --> 00:10:15.189 align:start position:0% current apps are going to use the normal account<00:10:12.690> system<00:10:12.990> and<00:10:13.320> not<00:10:13.440> a<00:10:13.620> more<00:10:14.550> safe 00:10:15.189 --> 00:10:15.199 align:start position:0% account system and not a more safe 00:10:15.199 --> 00:10:17.630 align:start position:0% account system and not a more safe identity<00:10:16.199> system<00:10:16.560> that<00:10:16.740> you<00:10:17.250> won't<00:10:17.459> be<00:10:17.579> able 00:10:17.630 --> 00:10:17.640 align:start position:0% identity system that you won't be able 00:10:17.640 --> 00:10:19.490 align:start position:0% identity system that you won't be able to<00:10:17.850> upgrade<00:10:17.970> all<00:10:18.360> the<00:10:18.510> previous<00:10:18.870> applications 00:10:19.490 --> 00:10:19.500 align:start position:0% to upgrade all the previous applications 00:10:19.500 --> 00:10:22.220 align:start position:0% to upgrade all the previous applications to<00:10:19.740> optionally<00:10:20.519> slot<00:10:20.880> into<00:10:21.120> an<00:10:21.360> ident<00:10:21.660> like<00:10:22.199> a 00:10:22.220 --> 00:10:22.230 align:start position:0% to optionally slot into an ident like a 00:10:22.230 --> 00:10:26.360 align:start position:0% to optionally slot into an ident like a more<00:10:22.940> flexible<00:10:23.940> identity<00:10:24.630> system<00:10:25.040> that's<00:10:26.040> one 00:10:26.360 --> 00:10:26.370 align:start position:0% more flexible identity system that's one 00:10:26.370 --> 00:10:27.560 align:start position:0% more flexible identity system that's one of<00:10:26.430> the<00:10:26.490> things<00:10:26.519> we<00:10:26.850> we<00:10:27.089> need<00:10:27.240> to<00:10:27.300> figure<00:10:27.480> out 00:10:27.560 --> 00:10:27.570 align:start position:0% of the things we we need to figure out 00:10:27.570 --> 00:10:31.310 align:start position:0% of the things we we need to figure out any<00:10:28.410> other<00:10:28.680> comments<00:10:28.949> on<00:10:29.279> the<00:10:29.550> medicine<00:10:30.329> in 00:10:31.310 --> 00:10:31.320 align:start position:0% any other comments on the medicine in 00:10:31.320 --> 00:10:33.380 align:start position:0% any other comments on the medicine in general<00:10:31.380> I<00:10:31.980> think<00:10:32.010> that<00:10:32.459> you<00:10:32.760> know<00:10:32.820> 20<00:10:33.240> bite 00:10:33.380 --> 00:10:33.390 align:start position:0% general I think that you know 20 bite 00:10:33.390 --> 00:10:35.420 align:start position:0% general I think that you know 20 bite addresses<00:10:33.959> are<00:10:34.110> pretty<00:10:34.440> wonderful<00:10:34.649> identity 00:10:35.420 --> 00:10:35.430 align:start position:0% addresses are pretty wonderful identity 00:10:35.430 --> 00:10:38.420 align:start position:0% addresses are pretty wonderful identity standards<00:10:35.850> themselves<00:10:35.970> just<00:10:36.660> because<00:10:37.430> like 00:10:38.420 --> 00:10:38.430 align:start position:0% standards themselves just because like 00:10:38.430 --> 00:10:40.220 align:start position:0% standards themselves just because like the<00:10:38.640> sort<00:10:38.880> of<00:10:38.910> really<00:10:39.360> important<00:10:39.779> property 00:10:40.220 --> 00:10:40.230 align:start position:0% the sort of really important property 00:10:40.230 --> 00:10:41.600 align:start position:0% the sort of really important property that<00:10:40.320> they<00:10:40.350> have<00:10:40.680> is<00:10:40.890> how<00:10:41.040> they're<00:10:41.220> good<00:10:41.490> at 00:10:41.600 --> 00:10:41.610 align:start position:0% that they have is how they're good at 00:10:41.610 --> 00:10:43.490 align:start position:0% that they have is how they're good at completely<00:10:42.089> separating<00:10:42.810> the<00:10:42.959> concept<00:10:43.410> of 00:10:43.490 --> 00:10:43.500 align:start position:0% completely separating the concept of 00:10:43.500 --> 00:10:45.259 align:start position:0% completely separating the concept of identity<00:10:44.010> to<00:10:44.220> the<00:10:44.250> concept<00:10:44.670> of<00:10:44.820> how<00:10:44.970> you<00:10:45.029> do 00:10:45.259 --> 00:10:45.269 align:start position:0% identity to the concept of how you do 00:10:45.269 --> 00:10:48.079 align:start position:0% identity to the concept of how you do access<00:10:45.660> control<00:10:46.019> for<00:10:46.230> the<00:10:46.350> identity<00:10:46.829> and<00:10:47.089> even 00:10:48.079 --> 00:10:48.089 align:start position:0% access control for the identity and even 00:10:48.089 --> 00:10:49.519 align:start position:0% access control for the identity and even you<00:10:48.180> know<00:10:48.269> we're<00:10:48.570> potentially<00:10:49.199> with<00:10:49.350> things 00:10:49.519 --> 00:10:49.529 align:start position:0% you know we're potentially with things 00:10:49.529 --> 00:10:51.110 align:start position:0% you know we're potentially with things like<00:10:49.620> registry<00:10:50.220> is<00:10:50.279> how<00:10:50.550> you<00:10:50.610> provide 00:10:51.110 --> 00:10:51.120 align:start position:0% like registry is how you provide 00:10:51.120 --> 00:10:53.460 align:start position:0% like registry is how you provide metadata<00:10:51.839> or<00:10:52.380> assert<00:10:53.010> a<00:10:53.160> shin 00:10:53.460 --> 00:10:53.470 align:start position:0% metadata or assert a shin 00:10:53.470 --> 00:10:57.360 align:start position:0% metadata or assert a shin about<00:10:53.590> that<00:10:53.710> identity<00:10:54.160> so<00:10:55.020> like<00:10:56.020> I<00:10:56.260> in<00:10:56.830> general 00:10:57.360 --> 00:10:57.370 align:start position:0% about that identity so like I in general 00:10:57.370 --> 00:10:59.520 align:start position:0% about that identity so like I in general you<00:10:57.460> know<00:10:57.550> I<00:10:57.580> do<00:10:57.700> think<00:10:58.180> that<00:10:58.240> you<00:10:58.990> know<00:10:59.110> access 00:10:59.520 --> 00:10:59.530 align:start position:0% you know I do think that you know access 00:10:59.530 --> 00:11:02.190 align:start position:0% you know I do think that you know access control<00:10:59.890> ism<00:11:00.100> is<00:11:00.250> a<00:11:00.280> problem<00:11:00.850> and<00:11:01.200> figuring 00:11:02.190 --> 00:11:02.200 align:start position:0% control ism is a problem and figuring 00:11:02.200 --> 00:11:03.720 align:start position:0% control ism is a problem and figuring out<00:11:02.320> how<00:11:02.500> to<00:11:02.560> like<00:11:02.710> switch<00:11:03.040> keys<00:11:03.280> around<00:11:03.520> as<00:11:03.700> a 00:11:03.720 --> 00:11:03.730 align:start position:0% out how to like switch keys around as a 00:11:03.730 --> 00:11:06.480 align:start position:0% out how to like switch keys around as a pro<00:11:03.910> Ellen<00:11:04.240> is<00:11:04.390> a<00:11:04.960> problem<00:11:05.560> but<00:11:05.830> all<00:11:06.040> of<00:11:06.340> those 00:11:06.480 --> 00:11:06.490 align:start position:0% pro Ellen is a problem but all of those 00:11:06.490 --> 00:11:10.380 align:start position:0% pro Ellen is a problem but all of those things<00:11:06.960> its<00:11:08.790> importance<00:11:09.790> to<00:11:09.910> kind<00:11:10.090> of<00:11:10.210> neat 00:11:10.380 --> 00:11:10.390 align:start position:0% things its importance to kind of neat 00:11:10.390 --> 00:11:12.540 align:start position:0% things its importance to kind of neat clean<00:11:10.630> we<00:11:10.810> separate<00:11:11.260> all<00:11:11.470> of<00:11:11.740> those<00:11:11.980> problems 00:11:12.540 --> 00:11:12.550 align:start position:0% clean we separate all of those problems 00:11:12.550 --> 00:11:14.400 align:start position:0% clean we separate all of those problems so<00:11:12.790> that<00:11:12.820> all<00:11:13.240> of<00:11:13.360> those<00:11:13.480> problems<00:11:14.020> can<00:11:14.200> side 00:11:14.400 --> 00:11:14.410 align:start position:0% so that all of those problems can side 00:11:14.410 --> 00:11:16.740 align:start position:0% so that all of those problems can side and<00:11:14.530> kind<00:11:14.860> of<00:11:14.920> be<00:11:15.130> sort<00:11:15.730> of<00:11:15.790> hidden<00:11:16.030> by<00:11:16.240> always 00:11:16.740 --> 00:11:16.750 align:start position:0% and kind of be sort of hidden by always 00:11:16.750 --> 00:11:18.030 align:start position:0% and kind of be sort of hidden by always from<00:11:16.960> the<00:11:16.990> point<00:11:17.140> of<00:11:17.230> view<00:11:17.290> of<00:11:17.380> applications 00:11:18.030 --> 00:11:18.040 align:start position:0% from the point of view of applications 00:11:18.040 --> 00:11:19.950 align:start position:0% from the point of view of applications hidden<00:11:18.340> behind<00:11:18.460> one<00:11:18.940> single<00:11:19.330> account<00:11:19.570> and 00:11:19.950 --> 00:11:19.960 align:start position:0% hidden behind one single account and 00:11:19.960 --> 00:11:21.810 align:start position:0% hidden behind one single account and then<00:11:20.590> you<00:11:20.800> know<00:11:20.920> people<00:11:21.250> can<00:11:21.400> basically<00:11:21.610> use 00:11:21.810 --> 00:11:21.820 align:start position:0% then you know people can basically use 00:11:21.820 --> 00:11:24.060 align:start position:0% then you know people can basically use whatever<00:11:22.240> solutions<00:11:22.810> they<00:11:22.960> want<00:11:23.260> because<00:11:23.410> you 00:11:24.060 --> 00:11:24.070 align:start position:0% whatever solutions they want because you 00:11:24.070 --> 00:11:25.230 align:start position:0% whatever solutions they want because you know<00:11:24.190> when<00:11:24.310> theory<00:11:24.610> people<00:11:24.910> have<00:11:25.090> the 00:11:25.230 --> 00:11:25.240 align:start position:0% know when theory people have the 00:11:25.240 --> 00:11:27.120 align:start position:0% know when theory people have the incentive<00:11:25.420> to<00:11:25.720> protect<00:11:26.050> your<00:11:26.170> own<00:11:26.260> see<00:11:26.470> their 00:11:27.120 --> 00:11:27.130 align:start position:0% incentive to protect your own see their 00:11:27.130 --> 00:11:29.040 align:start position:0% incentive to protect your own see their own<00:11:27.250> security<00:11:27.490> I<00:11:27.850> know<00:11:28.060> and<00:11:28.330> they'll<00:11:28.690> go<00:11:28.720> with 00:11:29.040 --> 00:11:29.050 align:start position:0% own security I know and they'll go with 00:11:29.050 --> 00:11:32.400 align:start position:0% own security I know and they'll go with what's<00:11:29.260> most<00:11:29.890> comfortable<00:11:30.040> for<00:11:30.400> them<00:11:30.670> I<00:11:31.410> think 00:11:32.400 --> 00:11:32.410 align:start position:0% what's most comfortable for them I think 00:11:32.410 --> 00:11:34.680 align:start position:0% what's most comfortable for them I think that<00:11:33.100> that's<00:11:33.370> what<00:11:33.610> proxy<00:11:33.940> contracts<00:11:34.390> can 00:11:34.680 --> 00:11:34.690 align:start position:0% that that's what proxy contracts can 00:11:34.690 --> 00:11:36.990 align:start position:0% that that's what proxy contracts can become<00:11:34.960> useful<00:11:35.170> in<00:11:35.410> that<00:11:35.440> regard<00:11:35.890> where<00:11:36.280> you 00:11:36.990 --> 00:11:37.000 align:start position:0% become useful in that regard where you 00:11:37.000 --> 00:11:40.190 align:start position:0% become useful in that regard where you essentially<00:11:37.360> you<00:11:38.320> you<00:11:38.710> navigate<00:11:39.250> your<00:11:39.280> your 00:11:40.190 --> 00:11:40.200 align:start position:0% essentially you you navigate your your 00:11:40.200 --> 00:11:42.420 align:start position:0% essentially you you navigate your your interaction<00:11:41.200> with<00:11:41.230> the<00:11:41.470> tricity<00:11:41.740> ecosystem 00:11:42.420 --> 00:11:42.430 align:start position:0% interaction with the tricity ecosystem 00:11:42.430 --> 00:11:44.160 align:start position:0% interaction with the tricity ecosystem through<00:11:42.610> like<00:11:42.760> a<00:11:42.790> personal<00:11:43.300> proxy<00:11:43.720> contract 00:11:44.160 --> 00:11:44.170 align:start position:0% through like a personal proxy contract 00:11:44.170 --> 00:11:46.590 align:start position:0% through like a personal proxy contract that's<00:11:44.350> your<00:11:44.830> sort<00:11:45.580> of<00:11:45.670> forwarder<00:11:46.180> to<00:11:46.480> the 00:11:46.590 --> 00:11:46.600 align:start position:0% that's your sort of forwarder to the 00:11:46.600 --> 00:11:52.980 align:start position:0% that's your sort of forwarder to the wrist<00:11:47.130> right<00:11:50.220> this<00:11:51.220> could<00:11:51.430> be<00:11:51.700> tied<00:11:52.450> into<00:11:52.690> any 00:11:52.980 --> 00:11:52.990 align:start position:0% wrist right this could be tied into any 00:11:52.990 --> 00:11:56.670 align:start position:0% wrist right this could be tied into any type<00:11:53.230> of<00:11:53.610> identity<00:11:54.610> system<00:11:55.000> potentially<00:11:55.900> so 00:11:56.670 --> 00:11:56.680 align:start position:0% type of identity system potentially so 00:11:56.680 --> 00:11:58.710 align:start position:0% type of identity system potentially so that<00:11:56.920> the<00:11:57.310> proxy<00:11:57.760> contract<00:11:58.240> then<00:11:58.450> would 00:11:58.710 --> 00:11:58.720 align:start position:0% that the proxy contract then would 00:11:58.720 --> 00:12:03.420 align:start position:0% that the proxy contract then would become<00:11:59.280> you<00:12:00.280> know<00:12:00.310> the<00:12:01.920> canonical<00:12:02.920> I<00:12:03.130> mean<00:12:03.310> the 00:12:03.420 --> 00:12:03.430 align:start position:0% become you know the canonical I mean the 00:12:03.430 --> 00:12:05.340 align:start position:0% become you know the canonical I mean the address<00:12:03.760> of<00:12:03.850> the<00:12:03.970> proxy<00:12:04.570> contracts<00:12:04.960> becomes 00:12:05.340 --> 00:12:05.350 align:start position:0% address of the proxy contracts becomes 00:12:05.350 --> 00:12:10.770 align:start position:0% address of the proxy contracts becomes the<00:12:05.670> canonical<00:12:06.840> identifier<00:12:07.840> for<00:12:09.270> for<00:12:10.270> you<00:12:10.480> and 00:12:10.770 --> 00:12:10.780 align:start position:0% the canonical identifier for for you and 00:12:10.780 --> 00:12:12.690 align:start position:0% the canonical identifier for for you and then<00:12:11.380> you<00:12:11.590> do<00:12:11.770> all<00:12:11.980> your<00:12:12.100> interactions 00:12:12.690 --> 00:12:12.700 align:start position:0% then you do all your interactions 00:12:12.700 --> 00:12:15.180 align:start position:0% then you do all your interactions through<00:12:12.880> that<00:12:13.120> but<00:12:13.450> you<00:12:13.570> can<00:12:13.750> have<00:12:13.980> multi<00:12:14.980> sig 00:12:15.180 --> 00:12:15.190 align:start position:0% through that but you can have multi sig 00:12:15.190 --> 00:12:17.880 align:start position:0% through that but you can have multi sig access<00:12:15.700> through<00:12:15.970> that<00:12:16.150> and<00:12:16.600> do<00:12:16.750> key<00:12:17.200> rotation 00:12:17.880 --> 00:12:17.890 align:start position:0% access through that and do key rotation 00:12:17.890 --> 00:12:20.370 align:start position:0% access through that and do key rotation for<00:12:18.160> access<00:12:18.520> to<00:12:18.550> the<00:12:18.730> proxy<00:12:19.120> contract<00:12:19.570> etc<00:12:19.690> so 00:12:20.370 --> 00:12:20.380 align:start position:0% for access to the proxy contract etc so 00:12:20.380 --> 00:12:27.350 align:start position:0% for access to the proxy contract etc so that<00:12:20.860> might<00:12:21.040> be<00:12:21.070> a<00:12:21.840> good<00:12:22.840> solution<00:12:24.360> if<00:12:25.470> early 00:12:27.350 --> 00:12:27.360 align:start position:0% that might be a good solution if early 00:12:27.360 --> 00:12:30.540 align:start position:0% that might be a good solution if early the<00:12:28.360> EVM<00:12:29.020> can<00:12:29.320> practically<00:12:29.800> be<00:12:30.010> expressive 00:12:30.540 --> 00:12:30.550 align:start position:0% the EVM can practically be expressive 00:12:30.550 --> 00:12:32.430 align:start position:0% the EVM can practically be expressive enough<00:12:30.640> especially<00:12:31.060> in<00:12:31.360> terms<00:12:31.480> in<00:12:32.050> terms<00:12:32.080> of 00:12:32.430 --> 00:12:32.440 align:start position:0% enough especially in terms in terms of 00:12:32.440 --> 00:12:34.650 align:start position:0% enough especially in terms in terms of cryptography<00:12:32.800> I<00:12:33.130> think<00:12:33.520> you<00:12:33.850> can<00:12:34.060> go<00:12:34.180> very<00:12:34.450> far 00:12:34.650 --> 00:12:34.660 align:start position:0% cryptography I think you can go very far 00:12:34.660 --> 00:12:36.990 align:start position:0% cryptography I think you can go very far with<00:12:34.810> boxxy<00:12:35.140> contracts<00:12:35.590> like<00:12:35.800> one<00:12:36.100> really 00:12:36.990 --> 00:12:37.000 align:start position:0% with boxxy contracts like one really 00:12:37.000 --> 00:12:38.460 align:start position:0% with boxxy contracts like one really far-out<00:12:37.270> thing<00:12:37.660> is<00:12:37.810> if<00:12:37.960> you<00:12:38.050> look<00:12:38.260> at 00:12:38.460 --> 00:12:38.470 align:start position:0% far-out thing is if you look at 00:12:38.470 --> 00:12:40.260 align:start position:0% far-out thing is if you look at something<00:12:38.770> like<00:12:38.950> the<00:12:39.280> Estonian<00:12:39.760> digital<00:12:40.120> ID 00:12:40.260 --> 00:12:40.270 align:start position:0% something like the Estonian digital ID 00:12:40.270 --> 00:12:42.780 align:start position:0% something like the Estonian digital ID standard<00:12:40.900> then<00:12:41.470> you<00:12:41.710> know<00:12:41.830> someone<00:12:42.310> with<00:12:42.520> an 00:12:42.780 --> 00:12:42.790 align:start position:0% standard then you know someone with an 00:12:42.790 --> 00:12:44.610 align:start position:0% standard then you know someone with an Estonian<00:12:43.330> digital<00:12:43.630> ID<00:12:43.780> you<00:12:44.110> should<00:12:44.380> is 00:12:44.610 --> 00:12:44.620 align:start position:0% Estonian digital ID you should is 00:12:44.620 --> 00:12:46.380 align:start position:0% Estonian digital ID you should is theoretically<00:12:45.520> able<00:12:45.790> to<00:12:45.940> create<00:12:46.240> digital 00:12:46.380 --> 00:12:46.390 align:start position:0% theoretically able to create digital 00:12:46.390 --> 00:12:48.300 align:start position:0% theoretically able to create digital signatures<00:12:47.020> with<00:12:47.230> that<00:12:47.440> and<00:12:47.710> you<00:12:47.800> could<00:12:48.070> even 00:12:48.300 --> 00:12:48.310 align:start position:0% signatures with that and you could even 00:12:48.310 --> 00:12:51.440 align:start position:0% signatures with that and you could even have<00:12:49.060> a<00:12:49.090> proxy<00:12:49.570> contract<00:12:49.960> and<00:12:50.110> verifies<00:12:50.500> those 00:12:51.440 --> 00:12:51.450 align:start position:0% have a proxy contract and verifies those 00:12:51.450 --> 00:12:55.620 align:start position:0% have a proxy contract and verifies those I<00:12:52.860> agree<00:12:53.860> that<00:12:53.890> proxy<00:12:54.790> contracts<00:12:55.180> work<00:12:55.420> very 00:12:55.620 --> 00:12:55.630 align:start position:0% I agree that proxy contracts work very 00:12:55.630 --> 00:12:57.330 align:start position:0% I agree that proxy contracts work very well<00:12:55.690> like<00:12:55.960> the<00:12:56.080> address<00:12:56.380> scheme<00:12:56.680> is<00:12:56.920> super 00:12:57.330 --> 00:12:57.340 align:start position:0% well like the address scheme is super 00:12:57.340 --> 00:12:59.580 align:start position:0% well like the address scheme is super general<00:12:57.670> in<00:12:57.760> it<00:12:58.180> I<00:12:58.420> mean<00:12:58.960> it<00:12:59.260> pretty<00:12:59.470> much 00:12:59.580 --> 00:12:59.590 align:start position:0% general in it I mean it pretty much 00:12:59.590 --> 00:13:01.230 align:start position:0% general in it I mean it pretty much solves<00:13:00.250> a<00:13:00.340> problem<00:13:00.370> like<00:13:00.670> you<00:13:00.820> described<00:13:01.120> but 00:13:01.230 --> 00:13:01.240 align:start position:0% solves a problem like you described but 00:13:01.240 --> 00:13:02.630 align:start position:0% solves a problem like you described but another<00:13:01.480> approach<00:13:01.840> you<00:13:01.990> could<00:13:02.140> do<00:13:02.260> is 00:13:02.630 --> 00:13:02.640 align:start position:0% another approach you could do is 00:13:02.640 --> 00:13:05.220 align:start position:0% another approach you could do is basically<00:13:03.640> you're<00:13:04.150> the<00:13:04.180> two<00:13:04.660> keys<00:13:04.930> are<00:13:05.140> the 00:13:05.220 --> 00:13:05.230 align:start position:0% basically you're the two keys are the 00:13:05.230 --> 00:13:06.060 align:start position:0% basically you're the two keys are the same<00:13:05.410> identity<00:13:05.770> if 00:13:06.060 --> 00:13:06.070 align:start position:0% same identity if 00:13:06.070 --> 00:13:08.190 align:start position:0% same identity if both<00:13:06.280> say<00:13:07.060> that<00:13:07.270> about<00:13:07.450> each<00:13:07.690> other<00:13:07.870> so<00:13:08.140> you 00:13:08.190 --> 00:13:08.200 align:start position:0% both say that about each other so you 00:13:08.200 --> 00:13:10.080 align:start position:0% both say that about each other so you have<00:13:08.350> one<00:13:08.500> contract<00:13:09.010> or<00:13:09.160> everyone<00:13:09.490> just<00:13:09.760> comes 00:13:10.080 --> 00:13:10.090 align:start position:0% have one contract or everyone just comes 00:13:10.090 --> 00:13:12.690 align:start position:0% have one contract or everyone just comes in<00:13:10.300> like<00:13:10.480> I<00:13:11.080> guess<00:13:11.380> wires<00:13:11.890> up<00:13:12.160> there<00:13:12.310> cluster 00:13:12.690 --> 00:13:12.700 align:start position:0% in like I guess wires up there cluster 00:13:12.700 --> 00:13:14.790 align:start position:0% in like I guess wires up there cluster of<00:13:12.940> keys<00:13:13.420> oh<00:13:13.660> and<00:13:13.960> also<00:13:14.080> a<00:13:14.200> contract<00:13:14.650> if<00:13:14.770> you 00:13:14.790 --> 00:13:14.800 align:start position:0% of keys oh and also a contract if you 00:13:14.800 --> 00:13:16.200 align:start position:0% of keys oh and also a contract if you can<00:13:14.980> force<00:13:15.220> it<00:13:15.310> to<00:13:15.460> do<00:13:15.550> a<00:13:15.580> particular<00:13:16.000> call 00:13:16.200 --> 00:13:16.210 align:start position:0% can force it to do a particular call 00:13:16.210 --> 00:13:17.550 align:start position:0% can force it to do a particular call it's<00:13:16.360> the<00:13:16.420> same<00:13:16.600> thing<00:13:16.630> and<00:13:16.930> then<00:13:17.410> your 00:13:17.550 --> 00:13:17.560 align:start position:0% it's the same thing and then your 00:13:17.560 --> 00:13:19.830 align:start position:0% it's the same thing and then your cluster<00:13:17.770> has<00:13:18.010> one<00:13:18.280> canonical<00:13:18.820> address<00:13:19.180> which 00:13:19.830 --> 00:13:19.840 align:start position:0% cluster has one canonical address which 00:13:19.840 --> 00:13:21.630 align:start position:0% cluster has one canonical address which you<00:13:19.870> use<00:13:20.320> you<00:13:20.530> know<00:13:20.560> when<00:13:21.250> you<00:13:21.340> check<00:13:21.520> the 00:13:21.630 --> 00:13:21.640 align:start position:0% you use you know when you check the 00:13:21.640 --> 00:13:23.190 align:start position:0% you use you know when you check the sender<00:13:21.910> you<00:13:22.090> look<00:13:22.270> up<00:13:22.420> the<00:13:22.510> canonical<00:13:22.960> address 00:13:23.190 --> 00:13:23.200 align:start position:0% sender you look up the canonical address 00:13:23.200 --> 00:13:25.560 align:start position:0% sender you look up the canonical address and<00:13:23.440> see<00:13:23.650> if<00:13:23.740> that's<00:13:23.860> authorized<00:13:24.430> and<00:13:25.420> then 00:13:25.560 --> 00:13:25.570 align:start position:0% and see if that's authorized and then 00:13:25.570 --> 00:13:26.790 align:start position:0% and see if that's authorized and then and<00:13:25.840> then<00:13:25.960> you<00:13:26.050> don't<00:13:26.110> have<00:13:26.200> to<00:13:26.380> then<00:13:26.590> then 00:13:26.790 --> 00:13:26.800 align:start position:0% and then you don't have to then then 00:13:26.800 --> 00:13:28.590 align:start position:0% and then you don't have to then then people<00:13:27.100> can<00:13:27.220> make<00:13:27.370> up<00:13:27.550> whatever<00:13:27.760> you<00:13:28.480> know 00:13:28.590 --> 00:13:28.600 align:start position:0% people can make up whatever you know 00:13:28.600 --> 00:13:30.540 align:start position:0% people can make up whatever you know they<00:13:29.410> can<00:13:29.530> even<00:13:29.620> merge<00:13:29.830> identities<00:13:30.340> if<00:13:30.460> you 00:13:30.540 --> 00:13:30.550 align:start position:0% they can even merge identities if you 00:13:30.550 --> 00:13:32.070 align:start position:0% they can even merge identities if you want<00:13:30.730> to<00:13:30.790> really<00:13:30.970> look<00:13:31.090> like<00:13:31.150> I<00:13:31.420> have<00:13:31.570> I<00:13:31.780> have 00:13:32.070 --> 00:13:32.080 align:start position:0% want to really look like I have I have 00:13:32.080 --> 00:13:33.300 align:start position:0% want to really look like I have I have two<00:13:32.320> identities<00:13:32.710> but<00:13:32.890> then<00:13:33.010> I<00:13:33.040> want<00:13:33.250> to 00:13:33.300 --> 00:13:33.310 align:start position:0% two identities but then I want to 00:13:33.310 --> 00:13:35.010 align:start position:0% two identities but then I want to combine<00:13:33.460> the<00:13:33.700> reputation<00:13:34.240> or<00:13:34.360> something<00:13:34.690> then 00:13:35.010 --> 00:13:35.020 align:start position:0% combine the reputation or something then 00:13:35.020 --> 00:13:37.260 align:start position:0% combine the reputation or something then I<00:13:35.290> can<00:13:35.680> link<00:13:36.340> them<00:13:36.490> together<00:13:36.670> and<00:13:36.940> now<00:13:37.060> they're 00:13:37.260 --> 00:13:37.270 align:start position:0% I can link them together and now they're 00:13:37.270 --> 00:13:43.410 align:start position:0% I can link them together and now they're one<00:13:39.060> yeah<00:13:40.060> that's<00:13:40.240> right<00:13:41.250> so<00:13:42.250> I<00:13:42.520> think<00:13:42.790> I<00:13:43.060> think 00:13:43.410 --> 00:13:43.420 align:start position:0% one yeah that's right so I think I think 00:13:43.420 --> 00:13:44.820 align:start position:0% one yeah that's right so I think I think one<00:13:43.570> of<00:13:43.600> the<00:13:43.750> we've<00:13:44.410> heard<00:13:44.590> a<00:13:44.680> lot<00:13:44.710> about 00:13:44.820 --> 00:13:44.830 align:start position:0% one of the we've heard a lot about 00:13:44.830 --> 00:13:49.950 align:start position:0% one of the we've heard a lot about tokens<00:13:46.350> through<00:13:47.350> the<00:13:47.440> past<00:13:47.650> few<00:13:47.890> days<00:13:48.960> it's 00:13:49.950 --> 00:13:49.960 align:start position:0% tokens through the past few days it's 00:13:49.960 --> 00:13:51.780 align:start position:0% tokens through the past few days it's definitely<00:13:50.140> one<00:13:50.440> of<00:13:50.470> the<00:13:50.620> more<00:13:50.980> pertinent 00:13:51.780 --> 00:13:51.790 align:start position:0% definitely one of the more pertinent 00:13:51.790 --> 00:13:55.080 align:start position:0% definitely one of the more pertinent things<00:13:52.180> to<00:13:52.720> to<00:13:53.350> think<00:13:53.620> about<00:13:53.860> and<00:13:54.070> I<00:13:54.130> think<00:13:54.400> as 00:13:55.080 --> 00:13:55.090 align:start position:0% things to to think about and I think as 00:13:55.090 --> 00:13:56.820 align:start position:0% things to to think about and I think as a<00:13:55.120> community<00:13:55.240> we've<00:13:55.780> come<00:13:55.990> to<00:13:56.140> very<00:13:56.320> close<00:13:56.590> to 00:13:56.820 --> 00:13:56.830 align:start position:0% a community we've come to very close to 00:13:56.830 --> 00:13:59.310 align:start position:0% a community we've come to very close to finding<00:13:57.310> a<00:13:57.490> pretty<00:13:58.120> good<00:13:58.360> decent<00:13:58.870> standard 00:13:59.310 --> 00:13:59.320 align:start position:0% finding a pretty good decent standard 00:13:59.320 --> 00:14:02.280 align:start position:0% finding a pretty good decent standard that's<00:13:59.680> not<00:14:00.070> ambiguous<00:14:00.400> and<00:14:00.940> people<00:14:01.780> can<00:14:01.990> can 00:14:02.280 --> 00:14:02.290 align:start position:0% that's not ambiguous and people can can 00:14:02.290 --> 00:14:05.700 align:start position:0% that's not ambiguous and people can can understand<00:14:02.710> I<00:14:03.490> think<00:14:04.060> the<00:14:04.150> next<00:14:04.780> the<00:14:05.200> next<00:14:05.350> big 00:14:05.700 --> 00:14:05.710 align:start position:0% understand I think the next the next big 00:14:05.710 --> 00:14:08.630 align:start position:0% understand I think the next the next big one<00:14:05.890> would<00:14:06.100> most<00:14:06.550> likely<00:14:06.850> be<00:14:07.150> registries<00:14:07.930> that 00:14:08.630 --> 00:14:08.640 align:start position:0% one would most likely be registries that 00:14:08.640 --> 00:14:10.680 align:start position:0% one would most likely be registries that it's<00:14:09.640> good<00:14:09.820> that<00:14:10.000> a<00:14:10.030> lot<00:14:10.090> of<00:14:10.180> people<00:14:10.300> are<00:14:10.540> going 00:14:10.680 --> 00:14:10.690 align:start position:0% it's good that a lot of people are going 00:14:10.690 --> 00:14:12.590 align:start position:0% it's good that a lot of people are going to<00:14:10.870> want<00:14:11.110> to<00:14:11.260> use<00:14:11.350> I'm<00:14:11.860> going<00:14:12.100> to<00:14:12.220> think<00:14:12.460> about 00:14:12.590 --> 00:14:12.600 align:start position:0% to want to use I'm going to think about 00:14:12.600 --> 00:14:15.860 align:start position:0% to want to use I'm going to think about I<00:14:13.600> know<00:14:13.990> there's<00:14:14.560> been<00:14:14.680> talk<00:14:15.070> about 00:14:15.860 --> 00:14:15.870 align:start position:0% I know there's been talk about 00:14:15.870 --> 00:14:18.960 align:start position:0% I know there's been talk about questioning<00:14:16.870> where<00:14:17.230> should<00:14:17.650> metadata<00:14:18.610> live 00:14:18.960 --> 00:14:18.970 align:start position:0% questioning where should metadata live 00:14:18.970 --> 00:14:20.490 align:start position:0% questioning where should metadata live it<00:14:19.360> should<00:14:19.630> it<00:14:19.720> be<00:14:19.870> in<00:14:19.960> the<00:14:19.990> contracts 00:14:20.490 --> 00:14:20.500 align:start position:0% it should it be in the contracts 00:14:20.500 --> 00:14:23.310 align:start position:0% it should it be in the contracts themselves<00:14:21.160> or<00:14:22.090> should<00:14:22.300> it<00:14:22.330> be<00:14:22.420> in<00:14:22.810> red<00:14:23.020> sheets 00:14:23.310 --> 00:14:23.320 align:start position:0% themselves or should it be in red sheets 00:14:23.320 --> 00:14:25.320 align:start position:0% themselves or should it be in red sheets Gavin<00:14:23.710> I<00:14:23.800> think<00:14:24.040> you<00:14:24.400> you<00:14:24.580> have<00:14:24.700> opinions<00:14:25.180> on 00:14:25.320 --> 00:14:25.330 align:start position:0% Gavin I think you you have opinions on 00:14:25.330 --> 00:14:32.100 align:start position:0% Gavin I think you you have opinions on that<00:14:25.480> you<00:14:25.990> want<00:14:26.170> to<00:14:26.200> share<00:14:26.910> sure<00:14:29.340> yeah<00:14:30.340> so<00:14:31.110> this 00:14:32.100 --> 00:14:32.110 align:start position:0% that you want to share sure yeah so this 00:14:32.110 --> 00:14:36.350 align:start position:0% that you want to share sure yeah so this is<00:14:32.320> a<00:14:32.350> question<00:14:32.860> concerning<00:14:33.070> whether<00:14:34.650> given<00:14:35.650> a 00:14:36.350 --> 00:14:36.360 align:start position:0% is a question concerning whether given a 00:14:36.360 --> 00:14:38.190 align:start position:0% is a question concerning whether given a contract<00:14:37.360> that<00:14:37.420> there's<00:14:37.720> some<00:14:37.930> particular 00:14:38.190 --> 00:14:38.200 align:start position:0% contract that there's some particular 00:14:38.200 --> 00:14:41.820 align:start position:0% contract that there's some particular thing<00:14:38.680> let's<00:14:38.950> assume<00:14:39.280> it's<00:14:39.640> a<00:14:40.590> some<00:14:41.590> sort<00:14:41.680> of 00:14:41.820 --> 00:14:41.830 align:start position:0% thing let's assume it's a some sort of 00:14:41.830 --> 00:14:44.280 align:start position:0% thing let's assume it's a some sort of token<00:14:42.190> contract<00:14:42.910> that's<00:14:43.690> recording<00:14:44.200> the 00:14:44.280 --> 00:14:44.290 align:start position:0% token contract that's recording the 00:14:44.290 --> 00:14:48.030 align:start position:0% token contract that's recording the balances<00:14:44.800> of<00:14:44.830> various<00:14:45.400> identities<00:14:46.860> should<00:14:47.860> it 00:14:48.030 --> 00:14:48.040 align:start position:0% balances of various identities should it 00:14:48.040 --> 00:14:51.030 align:start position:0% balances of various identities should it should<00:14:48.250> the<00:14:48.700> contract<00:14:48.880> itself<00:14:50.040> contain 00:14:51.030 --> 00:14:51.040 align:start position:0% should the contract itself contain 00:14:51.040 --> 00:14:54.000 align:start position:0% should the contract itself contain information<00:14:51.580> regarding<00:14:52.510> itself<00:14:52.900> or<00:14:53.080> should 00:14:54.000 --> 00:14:54.010 align:start position:0% information regarding itself or should 00:14:54.010 --> 00:14:55.830 align:start position:0% information regarding itself or should that<00:14:54.040> information<00:14:54.700> be<00:14:54.910> placed<00:14:55.180> elsewhere<00:14:55.420> on 00:14:55.830 --> 00:14:55.840 align:start position:0% that information be placed elsewhere on 00:14:55.840 --> 00:14:57.750 align:start position:0% that information be placed elsewhere on the<00:14:55.870> system<00:14:56.350> potentially<00:14:57.340> in<00:14:57.460> some<00:14:57.640> other 00:14:57.750 --> 00:14:57.760 align:start position:0% the system potentially in some other 00:14:57.760 --> 00:15:01.350 align:start position:0% the system potentially in some other contract<00:14:58.570> who's<00:14:59.440> res<00:15:00.310> on<00:15:00.490> debt<00:15:00.700> were<00:15:00.940> so<00:15:01.300> to 00:15:01.350 --> 00:15:01.360 align:start position:0% contract who's res on debt were so to 00:15:01.360 --> 00:15:04.010 align:start position:0% contract who's res on debt were so to speak<00:15:01.600> is<00:15:01.810> purely<00:15:02.710> to<00:15:03.040> retain<00:15:03.490> information 00:15:04.010 --> 00:15:04.020 align:start position:0% speak is purely to retain information 00:15:04.020 --> 00:15:07.880 align:start position:0% speak is purely to retain information concerning<00:15:05.020> for<00:15:05.650> example<00:15:06.070> token<00:15:06.430> contracts 00:15:07.880 --> 00:15:07.890 align:start position:0% concerning for example token contracts 00:15:07.890 --> 00:15:12.510 align:start position:0% concerning for example token contracts these<00:15:08.890> are<00:15:09.040> the<00:15:09.130> two<00:15:09.640> sort<00:15:09.940> of<00:15:10.170> options<00:15:11.520> it's 00:15:12.510 --> 00:15:12.520 align:start position:0% these are the two sort of options it's 00:15:12.520 --> 00:15:16.260 align:start position:0% these are the two sort of options it's my<00:15:12.730> opinion<00:15:12.940> that<00:15:14.430> because<00:15:15.430> we<00:15:15.700> live<00:15:15.970> because 00:15:16.260 --> 00:15:16.270 align:start position:0% my opinion that because we live because 00:15:16.270 --> 00:15:19.050 align:start position:0% my opinion that because we live because we<00:15:16.570> have<00:15:16.780> this<00:15:16.960> system<00:15:17.470> so<00:15:17.890> normally<00:15:18.430> i<00:15:18.730> would 00:15:19.050 --> 00:15:19.060 align:start position:0% we have this system so normally i would 00:15:19.060 --> 00:15:19.650 align:start position:0% we have this system so normally i would i<00:15:19.210> would 00:15:19.650 --> 00:15:19.660 align:start position:0% i would 00:15:19.660 --> 00:15:22.620 align:start position:0% i would I<00:15:20.260> would<00:15:20.740> place<00:15:20.980> the<00:15:21.310> information<00:15:21.880> in<00:15:22.120> with 00:15:22.620 --> 00:15:22.630 align:start position:0% I would place the information in with 00:15:22.630 --> 00:15:24.960 align:start position:0% I would place the information in with the<00:15:22.840> contract<00:15:23.290> that<00:15:23.710> is<00:15:23.830> actually<00:15:24.220> sort<00:15:24.910> of 00:15:24.960 --> 00:15:24.970 align:start position:0% the contract that is actually sort of 00:15:24.970 --> 00:15:29.010 align:start position:0% the contract that is actually sort of that<00:15:25.930> it<00:15:26.050> that<00:15:26.200> it<00:15:26.230> actually<00:15:26.880> refers<00:15:27.880> to<00:15:28.240> this 00:15:29.010 --> 00:15:29.020 align:start position:0% that it that it actually refers to this 00:15:29.020 --> 00:15:31.110 align:start position:0% that it that it actually refers to this is<00:15:29.170> mainly<00:15:29.410> because<00:15:29.650> in<00:15:30.340> the<00:15:30.670> in<00:15:30.820> the<00:15:30.850> real 00:15:31.110 --> 00:15:31.120 align:start position:0% is mainly because in the in the real 00:15:31.120 --> 00:15:34.890 align:start position:0% is mainly because in the in the real world<00:15:31.420> we<00:15:31.840> have<00:15:32.400> you<00:15:33.400> know<00:15:33.490> siloed<00:15:34.090> servers 00:15:34.890 --> 00:15:34.900 align:start position:0% world we have you know siloed servers 00:15:34.900 --> 00:15:36.570 align:start position:0% world we have you know siloed servers that<00:15:35.200> actually<00:15:35.560> have<00:15:35.680> system<00:15:36.040> admins<00:15:36.370> that 00:15:36.570 --> 00:15:36.580 align:start position:0% that actually have system admins that 00:15:36.580 --> 00:15:39.420 align:start position:0% that actually have system admins that can<00:15:36.700> actually<00:15:36.820> corrupt<00:15:37.270> data<00:15:37.480> and<00:15:38.100> and<00:15:39.100> and 00:15:39.420 --> 00:15:39.430 align:start position:0% can actually corrupt data and and and 00:15:39.430 --> 00:15:41.070 align:start position:0% can actually corrupt data and and and the<00:15:39.550> two<00:15:39.730> sort<00:15:40.030> of<00:15:40.180> systems<00:15:40.570> can<00:15:40.780> become 00:15:41.070 --> 00:15:41.080 align:start position:0% the two sort of systems can become 00:15:41.080 --> 00:15:44.730 align:start position:0% the two sort of systems can become disjoint<00:15:41.980> but<00:15:42.760> within<00:15:43.600> a<00:15:43.960> theorem<00:15:44.410> of<00:15:44.500> course 00:15:44.730 --> 00:15:44.740 align:start position:0% disjoint but within a theorem of course 00:15:44.740 --> 00:15:46.920 align:start position:0% disjoint but within a theorem of course we<00:15:45.190> don't<00:15:45.310> have<00:15:45.610> these<00:15:45.760> problems<00:15:45.910> and<00:15:46.420> we<00:15:46.720> can 00:15:46.920 --> 00:15:46.930 align:start position:0% we don't have these problems and we can 00:15:46.930 --> 00:15:53.040 align:start position:0% we don't have these problems and we can actually<00:15:47.140> have<00:15:47.910> nice<00:15:48.960> isolation<00:15:49.960> of<00:15:52.050> use 00:15:53.040 --> 00:15:53.050 align:start position:0% actually have nice isolation of use 00:15:53.050 --> 00:15:55.410 align:start position:0% actually have nice isolation of use cases<00:15:53.470> without<00:15:53.890> having<00:15:54.670> to<00:15:54.820> have<00:15:54.970> the<00:15:55.120> sort<00:15:55.330> of 00:15:55.410 --> 00:15:55.420 align:start position:0% cases without having to have the sort of 00:15:55.420 --> 00:15:57.870 align:start position:0% cases without having to have the sort of real-world<00:15:56.320> problems<00:15:57.160> that<00:15:57.430> isolation 00:15:57.870 --> 00:15:57.880 align:start position:0% real-world problems that isolation 00:15:57.880 --> 00:15:59.580 align:start position:0% real-world problems that isolation brings<00:15:58.300> such<00:15:58.630> as<00:15:58.810> the<00:15:58.930> fact<00:15:59.140> it's<00:15:59.290> thought<00:15:59.470> on 00:15:59.580 --> 00:15:59.590 align:start position:0% brings such as the fact it's thought on 00:15:59.590 --> 00:16:00.810 align:start position:0% brings such as the fact it's thought on a<00:15:59.650> different<00:15:59.950> computer<00:16:00.040> potentially<00:16:00.730> the 00:16:00.810 --> 00:16:00.820 align:start position:0% a different computer potentially the 00:16:00.820 --> 00:16:02.310 align:start position:0% a different computer potentially the different<00:16:01.150> isp<00:16:01.510> potentially<00:16:02.020> it's<00:16:02.110> going<00:16:02.260> to 00:16:02.310 --> 00:16:02.320 align:start position:0% different isp potentially it's going to 00:16:02.320 --> 00:16:04.530 align:start position:0% different isp potentially it's going to go<00:16:02.410> down<00:16:02.440> at<00:16:02.830> different<00:16:03.130> times<00:16:03.370> and<00:16:03.640> all<00:16:04.450> the 00:16:04.530 --> 00:16:04.540 align:start position:0% go down at different times and all the 00:16:04.540 --> 00:16:06.600 align:start position:0% go down at different times and all the rest<00:16:04.660> of<00:16:04.840> it<00:16:04.930> so<00:16:05.380> in<00:16:05.740> this<00:16:05.860> instance<00:16:05.920> I<00:16:06.430> would 00:16:06.600 --> 00:16:06.610 align:start position:0% rest of it so in this instance I would 00:16:06.610 --> 00:16:09.990 align:start position:0% rest of it so in this instance I would actually<00:16:06.700> prefer<00:16:07.150> to<00:16:07.570> have<00:16:07.780> a<00:16:08.550> nice<00:16:09.550> fair 00:16:09.990 --> 00:16:10.000 align:start position:0% actually prefer to have a nice fair 00:16:10.000 --> 00:16:12.240 align:start position:0% actually prefer to have a nice fair contract<00:16:10.480> that<00:16:10.780> actually<00:16:11.140> it's<00:16:11.530> resin<00:16:11.920> d'etre 00:16:12.240 --> 00:16:12.250 align:start position:0% contract that actually it's resin d'etre 00:16:12.250 --> 00:16:14.640 align:start position:0% contract that actually it's resin d'etre is<00:16:12.280> simply<00:16:12.730> to<00:16:12.850> store<00:16:13.090> metadata<00:16:13.300> about<00:16:13.900> other 00:16:14.640 --> 00:16:14.650 align:start position:0% is simply to store metadata about other 00:16:14.650 --> 00:16:17.550 align:start position:0% is simply to store metadata about other contracts<00:16:15.280> yeah<00:16:15.460> and<00:16:15.700> then<00:16:16.240> allow<00:16:17.080> the<00:16:17.140> coin 00:16:17.550 --> 00:16:17.560 align:start position:0% contracts yeah and then allow the coin 00:16:17.560 --> 00:16:19.050 align:start position:0% contracts yeah and then allow the coin contracts<00:16:18.250> and<00:16:18.400> all<00:16:18.490> the<00:16:18.580> rest<00:16:18.730> of<00:16:18.880> the<00:16:18.970> other 00:16:19.050 --> 00:16:19.060 align:start position:0% contracts and all the rest of the other 00:16:19.060 --> 00:16:21.510 align:start position:0% contracts and all the rest of the other all<00:16:19.300> the<00:16:19.390> token<00:16:19.720> contracts<00:16:20.230> etc<00:16:20.320> to<00:16:20.800> do<00:16:20.920> their 00:16:21.510 --> 00:16:21.520 align:start position:0% all the token contracts etc to do their 00:16:21.520 --> 00:16:23.790 align:start position:0% all the token contracts etc to do their thing<00:16:21.820> which<00:16:22.030> is<00:16:22.060> to<00:16:22.240> say<00:16:22.620> maintain<00:16:23.620> the 00:16:23.790 --> 00:16:23.800 align:start position:0% thing which is to say maintain the 00:16:23.800 --> 00:16:27.180 align:start position:0% thing which is to say maintain the balances<00:16:24.310> of<00:16:24.490> their<00:16:25.150> of<00:16:25.570> our<00:16:25.720> users<00:16:26.110> you<00:16:27.040> can 00:16:27.180 --> 00:16:27.190 align:start position:0% balances of their of our users you can 00:16:27.190 --> 00:16:29.100 align:start position:0% balances of their of our users you can you<00:16:27.520> explain<00:16:27.790> more<00:16:27.970> what<00:16:28.390> types<00:16:28.720> of<00:16:28.840> metadata 00:16:29.100 --> 00:16:29.110 align:start position:0% you explain more what types of metadata 00:16:29.110 --> 00:16:30.270 align:start position:0% you explain more what types of metadata you're<00:16:29.410> talking<00:16:29.740> about<00:16:29.860> because<00:16:30.040> that<00:16:30.130> can 00:16:30.270 --> 00:16:30.280 align:start position:0% you're talking about because that can 00:16:30.280 --> 00:16:33.030 align:start position:0% you're talking about because that can mean<00:16:30.400> stylish<00:16:30.730> sure<00:16:31.120> so<00:16:32.020> specifically<00:16:32.770> data 00:16:33.030 --> 00:16:33.040 align:start position:0% mean stylish sure so specifically data 00:16:33.040 --> 00:16:34.890 align:start position:0% mean stylish sure so specifically data concerning<00:16:33.520> the<00:16:33.730> contract<00:16:34.150> itself<00:16:34.300> rather 00:16:34.890 --> 00:16:34.900 align:start position:0% concerning the contract itself rather 00:16:34.900 --> 00:16:36.720 align:start position:0% concerning the contract itself rather than<00:16:35.050> containing<00:16:35.500> that<00:16:35.800> the<00:16:36.160> data<00:16:36.370> that<00:16:36.640> the 00:16:36.720 --> 00:16:36.730 align:start position:0% than containing that the data that the 00:16:36.730 --> 00:16:38.820 align:start position:0% than containing that the data that the contract<00:16:37.120> cares<00:16:37.360> about<00:16:37.570> so<00:16:37.840> in<00:16:38.080> this<00:16:38.410> case<00:16:38.620> the 00:16:38.820 --> 00:16:38.830 align:start position:0% contract cares about so in this case the 00:16:38.830 --> 00:16:40.950 align:start position:0% contract cares about so in this case the death<00:16:38.950> date<00:16:39.160> or<00:16:39.310> things<00:16:39.670> like<00:16:39.840> what's<00:16:40.840> the 00:16:40.950 --> 00:16:40.960 align:start position:0% death date or things like what's the 00:16:40.960 --> 00:16:45.800 align:start position:0% death date or things like what's the name<00:16:41.290> of<00:16:41.320> the<00:16:41.620> contract<00:16:42.930> maybe<00:16:43.930> the 00:16:45.800 --> 00:16:45.810 align:start position:0% name of the contract maybe the 00:16:45.810 --> 00:16:48.150 align:start position:0% name of the contract maybe the certificate<00:16:46.810> we<00:16:46.990> consider<00:16:47.380> them<00:16:47.500> like<00:16:47.620> static 00:16:48.150 --> 00:16:48.160 align:start position:0% certificate we consider them like static 00:16:48.160 --> 00:16:49.650 align:start position:0% certificate we consider them like static static<00:16:48.640> members<00:16:49.000> you<00:16:49.240> know<00:16:49.270> stuff<00:16:49.630> that 00:16:49.650 --> 00:16:49.660 align:start position:0% static members you know stuff that 00:16:49.660 --> 00:16:51.180 align:start position:0% static members you know stuff that doesn't<00:16:49.990> actually<00:16:50.230> change<00:16:50.500> with<00:16:50.890> the<00:16:50.980> state 00:16:51.180 --> 00:16:51.190 align:start position:0% doesn't actually change with the state 00:16:51.190 --> 00:16:52.860 align:start position:0% doesn't actually change with the state it's<00:16:51.430> just<00:16:51.670> to<00:16:51.760> do<00:16:51.880> with<00:16:52.030> the<00:16:52.150> actual<00:16:52.270> object 00:16:52.860 --> 00:16:52.870 align:start position:0% it's just to do with the actual object 00:16:52.870 --> 00:16:57.750 align:start position:0% it's just to do with the actual object itself<00:16:54.870> yeah<00:16:55.870> our<00:16:56.500> opinions<00:16:56.920> on<00:16:57.070> it<00:16:57.160> burner 00:16:57.750 --> 00:16:57.760 align:start position:0% itself yeah our opinions on it burner 00:16:57.760 --> 00:17:01.230 align:start position:0% itself yeah our opinions on it burner the<00:16:58.720> idea<00:16:59.080> is<00:16:59.140> basically<00:16:59.500> like<00:16:59.770> names<00:17:00.220> and<00:17:00.700> the 00:17:01.230 --> 00:17:01.240 align:start position:0% the idea is basically like names and the 00:17:01.240 --> 00:17:03.780 align:start position:0% the idea is basically like names and the token<00:17:01.990> symbol<00:17:02.380> or<00:17:02.650> like<00:17:02.980> how<00:17:03.130> much<00:17:03.250> decimal 00:17:03.780 --> 00:17:03.790 align:start position:0% token symbol or like how much decimal 00:17:03.790 --> 00:17:09.180 align:start position:0% token symbol or like how much decimal the<00:17:04.210> blazes<00:17:04.750> 1201<00:17:05.500> token<00:17:06.010> has<00:17:06.190> and<00:17:07.050> I<00:17:08.190> think 00:17:09.180 --> 00:17:09.190 align:start position:0% the blazes 1201 token has and I think 00:17:09.190 --> 00:17:10.920 align:start position:0% the blazes 1201 token has and I think it's<00:17:09.310> definitely<00:17:09.400> a<00:17:09.640> valid<00:17:09.910> approach<00:17:10.120> but<00:17:10.870> I 00:17:10.920 --> 00:17:10.930 align:start position:0% it's definitely a valid approach but I 00:17:10.930 --> 00:17:13.050 align:start position:0% it's definitely a valid approach but I could<00:17:11.350> also<00:17:11.500> imagine<00:17:11.860> that<00:17:12.130> a<00:17:12.250> lot<00:17:12.760> of<00:17:12.790> people 00:17:13.050 --> 00:17:13.060 align:start position:0% could also imagine that a lot of people 00:17:13.060 --> 00:17:14.550 align:start position:0% could also imagine that a lot of people may<00:17:13.330> want<00:17:13.660> to<00:17:13.750> have<00:17:13.810> told<00:17:14.080> us<00:17:14.140> which<00:17:14.290> are<00:17:14.380> not 00:17:14.550 --> 00:17:14.560 align:start position:0% may want to have told us which are not 00:17:14.560 --> 00:17:17.340 align:start position:0% may want to have told us which are not listed<00:17:14.800> in<00:17:15.100> any<00:17:15.220> kind<00:17:15.520> of<00:17:15.550> registry<00:17:16.090> and<00:17:16.350> as 00:17:17.340 --> 00:17:17.350 align:start position:0% listed in any kind of registry and as 00:17:17.350 --> 00:17:21.620 align:start position:0% listed in any kind of registry and as well<00:17:17.620> as<00:17:18.040> I<00:17:18.400> see<00:17:19.150> this<00:17:19.300> is<00:17:19.480> like<00:17:19.750> crowing<00:17:20.380> from 00:17:21.620 --> 00:17:21.630 align:start position:0% well as I see this is like crowing from 00:17:21.630 --> 00:17:25.230 align:start position:0% well as I see this is like crowing from simple<00:17:22.630> things<00:17:22.980> from<00:17:23.980> what<00:17:24.340> we<00:17:24.730> can<00:17:24.880> do<00:17:25.030> right 00:17:25.230 --> 00:17:25.240 align:start position:0% simple things from what we can do right 00:17:25.240 --> 00:17:27.390 align:start position:0% simple things from what we can do right now<00:17:25.300> what<00:17:25.870> we<00:17:25.990> can<00:17:26.140> add<00:17:26.470> for<00:17:26.950> example<00:17:26.980> to<00:17:27.310> the 00:17:27.390 --> 00:17:27.400 align:start position:0% now what we can add for example to the 00:17:27.400 --> 00:17:29.730 align:start position:0% now what we can add for example to the wallet<00:17:27.700> right<00:17:27.850> now<00:17:28.090> in<00:17:28.240> an<00:17:28.330> easy<00:17:28.510> way<00:17:28.690> and<00:17:29.050> what 00:17:29.730 --> 00:17:29.740 align:start position:0% wallet right now in an easy way and what 00:17:29.740 --> 00:17:30.900 align:start position:0% wallet right now in an easy way and what ideally<00:17:30.340> we<00:17:30.430> want<00:17:30.580> to 00:17:30.900 --> 00:17:30.910 align:start position:0% ideally we want to 00:17:30.910 --> 00:17:32.640 align:start position:0% ideally we want to some<00:17:31.090> point<00:17:31.330> in<00:17:31.480> the<00:17:31.570> future<00:17:31.600> at<00:17:32.320> some<00:17:32.440> point 00:17:32.640 --> 00:17:32.650 align:start position:0% some point in the future at some point 00:17:32.650 --> 00:17:34.110 align:start position:0% some point in the future at some point in<00:17:32.740> the<00:17:32.800> future<00:17:32.860> we<00:17:33.160> probably<00:17:33.400> have<00:17:33.730> I<00:17:33.970> can 00:17:34.110 --> 00:17:34.120 align:start position:0% in the future we probably have I can 00:17:34.120 --> 00:17:36.450 align:start position:0% in the future we probably have I can miss<00:17:34.300> many<00:17:34.930> depths<00:17:35.290> which<00:17:35.410> allow<00:17:35.650> you<00:17:35.710> to<00:17:35.830> look 00:17:36.450 --> 00:17:36.460 align:start position:0% miss many depths which allow you to look 00:17:36.460 --> 00:17:38.130 align:start position:0% miss many depths which allow you to look at<00:17:36.610> these<00:17:36.760> registries<00:17:37.360> to<00:17:37.720> modify<00:17:38.110> these 00:17:38.130 --> 00:17:38.140 align:start position:0% at these registries to modify these 00:17:38.140 --> 00:17:41.220 align:start position:0% at these registries to modify these registries<00:17:38.910> to<00:17:39.910> have<00:17:40.630> all<00:17:40.780> kind<00:17:40.960> of<00:17:41.020> search 00:17:41.220 --> 00:17:41.230 align:start position:0% registries to have all kind of search 00:17:41.230 --> 00:17:43.620 align:start position:0% registries to have all kind of search functionality<00:17:41.740> and<00:17:42.190> then<00:17:42.640> it's<00:17:42.880> very<00:17:43.180> useful 00:17:43.620 --> 00:17:43.630 align:start position:0% functionality and then it's very useful 00:17:43.630 --> 00:17:47.100 align:start position:0% functionality and then it's very useful to<00:17:43.750> have<00:17:43.840> these<00:17:44.610> registries<00:17:45.610> and<00:17:45.870> maybe<00:17:46.870> even 00:17:47.100 --> 00:17:47.110 align:start position:0% to have these registries and maybe even 00:17:47.110 --> 00:17:50.610 align:start position:0% to have these registries and maybe even exit<00:17:47.500> all<00:17:47.710> through<00:17:47.950> this<00:17:48.690> but<00:17:49.690> in<00:17:49.960> the<00:17:50.170> current 00:17:50.610 --> 00:17:50.620 align:start position:0% exit all through this but in the current 00:17:50.620 --> 00:17:52.530 align:start position:0% exit all through this but in the current state<00:17:51.010> I<00:17:51.040> see<00:17:51.340> it<00:17:51.400> more<00:17:51.490> like<00:17:51.850> a<00:17:51.880> lean<00:17:52.240> approach 00:17:52.530 --> 00:17:52.540 align:start position:0% state I see it more like a lean approach 00:17:52.540 --> 00:17:54.810 align:start position:0% state I see it more like a lean approach like<00:17:53.410> putting<00:17:53.890> the<00:17:54.010> things<00:17:54.250> where<00:17:54.550> they<00:17:54.640> are 00:17:54.810 --> 00:17:54.820 align:start position:0% like putting the things where they are 00:17:54.820 --> 00:17:57.690 align:start position:0% like putting the things where they are right<00:17:55.180> now<00:17:55.240> easy<00:17:55.780> accessible<00:17:56.530> and<00:17:56.740> easy<00:17:57.460> to 00:17:57.690 --> 00:17:57.700 align:start position:0% right now easy accessible and easy to 00:17:57.700 --> 00:17:59.340 align:start position:0% right now easy accessible and easy to understand<00:17:58.180> because<00:17:58.330> it's<00:17:58.480> also<00:17:58.750> from<00:17:59.110> the 00:17:59.340 --> 00:17:59.350 align:start position:0% understand because it's also from the 00:17:59.350 --> 00:18:02.280 align:start position:0% understand because it's also from the other<00:18:00.160> developers<00:18:00.850> who<00:18:00.940> use<00:18:01.540> these<00:18:01.780> contracts 00:18:02.280 --> 00:18:02.290 align:start position:0% other developers who use these contracts 00:18:02.290 --> 00:18:04.320 align:start position:0% other developers who use these contracts we<00:18:02.380> want<00:18:02.590> to<00:18:02.680> understand<00:18:03.160> them<00:18:03.430> they<00:18:03.700> have<00:18:04.150> to 00:18:04.320 --> 00:18:04.330 align:start position:0% we want to understand them they have to 00:18:04.330 --> 00:18:05.820 align:start position:0% we want to understand them they have to know<00:18:04.480> that<00:18:04.660> I<00:18:04.750> have<00:18:04.870> to<00:18:05.020> look<00:18:05.140> indigenous<00:18:05.710> and 00:18:05.820 --> 00:18:05.830 align:start position:0% know that I have to look indigenous and 00:18:05.830 --> 00:18:07.560 align:start position:0% know that I have to look indigenous and displaces<00:18:06.460> or<00:18:06.640> maybe<00:18:07.030> there's<00:18:07.240> two<00:18:07.390> different 00:18:07.560 --> 00:18:07.570 align:start position:0% displaces or maybe there's two different 00:18:07.570 --> 00:18:10.950 align:start position:0% displaces or maybe there's two different coin<00:18:07.990> registries<00:18:08.530> or<00:18:08.680> three<00:18:09.370> or<00:18:09.550> so<00:18:09.960> if 00:18:10.950 --> 00:18:10.960 align:start position:0% coin registries or three or so if 00:18:10.960 --> 00:18:12.750 align:start position:0% coin registries or three or so if they're<00:18:11.530> just<00:18:11.740> like<00:18:11.920> right<00:18:12.100> now<00:18:12.250> have<00:18:12.430> it<00:18:12.550> into 00:18:12.750 --> 00:18:12.760 align:start position:0% they're just like right now have it into 00:18:12.760 --> 00:18:14.190 align:start position:0% they're just like right now have it into place<00:18:12.940> where<00:18:13.150> they're<00:18:13.300> actually<00:18:13.660> expecting 00:18:14.190 --> 00:18:14.200 align:start position:0% place where they're actually expecting 00:18:14.200 --> 00:18:16.350 align:start position:0% place where they're actually expecting it<00:18:14.290> to<00:18:14.410> be<00:18:14.440> it's<00:18:15.040> easier<00:18:15.490> and<00:18:15.520> it's<00:18:15.760> like<00:18:15.940> we<00:18:16.330> I 00:18:16.350 --> 00:18:16.360 align:start position:0% it to be it's easier and it's like we I 00:18:16.360 --> 00:18:18.300 align:start position:0% it to be it's easier and it's like we I think<00:18:16.540> we<00:18:16.690> would<00:18:16.870> crow<00:18:17.110> in<00:18:17.380> that<00:18:17.530> direction<00:18:17.860> so 00:18:18.300 --> 00:18:18.310 align:start position:0% think we would crow in that direction so 00:18:18.310 --> 00:18:22.110 align:start position:0% think we would crow in that direction so we're<00:18:18.760> like<00:18:19.500> mature<00:18:20.500> over<00:18:20.890> time<00:18:21.160> and<00:18:21.490> this 00:18:22.110 --> 00:18:22.120 align:start position:0% we're like mature over time and this 00:18:22.120 --> 00:18:24.090 align:start position:0% we're like mature over time and this also<00:18:22.360> brings<00:18:22.510> me<00:18:22.720> to<00:18:22.840> the<00:18:22.930> point<00:18:22.960> of<00:18:23.350> of<00:18:23.620> the 00:18:24.090 --> 00:18:24.100 align:start position:0% also brings me to the point of of the 00:18:24.100 --> 00:18:26.490 align:start position:0% also brings me to the point of of the current<00:18:24.400> standards<00:18:24.910> so<00:18:25.690> I<00:18:25.870> don't<00:18:26.140> think<00:18:26.380> we 00:18:26.490 --> 00:18:26.500 align:start position:0% current standards so I don't think we 00:18:26.500 --> 00:18:28.110 align:start position:0% current standards so I don't think we can<00:18:26.680> make<00:18:26.830> up<00:18:27.070> a<00:18:27.220> standard<00:18:27.580> right<00:18:27.790> now<00:18:27.910> which 00:18:28.110 --> 00:18:28.120 align:start position:0% can make up a standard right now which 00:18:28.120 --> 00:18:29.550 align:start position:0% can make up a standard right now which fits<00:18:28.360> everything<00:18:28.660> for<00:18:28.960> the<00:18:29.050> next<00:18:29.290> course<00:18:29.440> I've 00:18:29.550 --> 00:18:29.560 align:start position:0% fits everything for the next course I've 00:18:29.560 --> 00:18:31.770 align:start position:0% fits everything for the next course I've had<00:18:29.680> five<00:18:29.860> years<00:18:30.160> or<00:18:30.340> so<00:18:30.520> it<00:18:31.030> will<00:18:31.270> probably<00:18:31.540> be 00:18:31.770 --> 00:18:31.780 align:start position:0% had five years or so it will probably be 00:18:31.780 --> 00:18:37.500 align:start position:0% had five years or so it will probably be many<00:18:32.320> iterations<00:18:32.650> and<00:18:33.310> i<00:18:34.800> think<00:18:36.270> one<00:18:37.270> major 00:18:37.500 --> 00:18:37.510 align:start position:0% many iterations and i think one major 00:18:37.510 --> 00:18:39.960 align:start position:0% many iterations and i think one major point<00:18:37.780> is<00:18:37.960> to<00:18:38.050> make<00:18:38.230> sure<00:18:38.260> that<00:18:38.530> we<00:18:38.980> have<00:18:39.190> some 00:18:39.960 --> 00:18:39.970 align:start position:0% point is to make sure that we have some 00:18:39.970 --> 00:18:43.290 align:start position:0% point is to make sure that we have some kind<00:18:40.210> of<00:18:40.300> up<00:18:40.650> credibility<00:18:41.650> strategy<00:18:42.220> so<00:18:42.940> what 00:18:43.290 --> 00:18:43.300 align:start position:0% kind of up credibility strategy so what 00:18:43.300 --> 00:18:47.040 align:start position:0% kind of up credibility strategy so what happens<00:18:43.720> if<00:18:43.960> like<00:18:44.260> standards<00:18:45.010> change<00:18:46.050> maybe 00:18:47.040 --> 00:18:47.050 align:start position:0% happens if like standards change maybe 00:18:47.050 --> 00:18:50.870 align:start position:0% happens if like standards change maybe we<00:18:47.290> can<00:18:47.470> use<00:18:47.710> proxies<00:18:48.670> in<00:18:48.700> front<00:18:49.330> of<00:18:49.480> others<00:18:49.810> or 00:18:50.870 --> 00:18:50.880 align:start position:0% we can use proxies in front of others or 00:18:50.880 --> 00:18:54.060 align:start position:0% we can use proxies in front of others or some<00:18:51.880> kind<00:18:52.120> of<00:18:52.270> like<00:18:52.630> via<00:18:52.960> proxies<00:18:53.560> we're<00:18:53.800> like 00:18:54.060 --> 00:18:54.070 align:start position:0% some kind of like via proxies we're like 00:18:54.070 --> 00:18:56.400 align:start position:0% some kind of like via proxies we're like you<00:18:54.280> can<00:18:54.460> change<00:18:54.790> the<00:18:55.030> api<00:18:55.420> of<00:18:55.720> your<00:18:55.930> token<00:18:56.320> in 00:18:56.400 --> 00:18:56.410 align:start position:0% you can change the api of your token in 00:18:56.410 --> 00:18:58.680 align:start position:0% you can change the api of your token in a<00:18:56.530> way<00:18:56.680> without<00:18:57.580> changing<00:18:58.300> the<00:18:58.390> actual 00:18:58.680 --> 00:18:58.690 align:start position:0% a way without changing the actual 00:18:58.690 --> 00:19:01.080 align:start position:0% a way without changing the actual contract<00:18:59.170> without<00:18:59.800> it<00:19:00.130> the<00:19:00.280> real<00:19:00.460> update<00:19:00.760> of 00:19:01.080 --> 00:19:01.090 align:start position:0% contract without it the real update of 00:19:01.090 --> 00:19:02.730 align:start position:0% contract without it the real update of the<00:19:01.240> contract<00:19:01.600> you<00:19:01.690> can<00:19:01.900> still<00:19:02.170> be<00:19:02.290> sure<00:19:02.500> it's 00:19:02.730 --> 00:19:02.740 align:start position:0% the contract you can still be sure it's 00:19:02.740 --> 00:19:04.770 align:start position:0% the contract you can still be sure it's to<00:19:02.920> steal<00:19:03.160> the<00:19:03.280> same<00:19:03.460> contract<00:19:03.970> just<00:19:04.420> now<00:19:04.630> it 00:19:04.770 --> 00:19:04.780 align:start position:0% to steal the same contract just now it 00:19:04.780 --> 00:19:07.740 align:start position:0% to steal the same contract just now it has<00:19:04.900> a<00:19:04.930> different<00:19:05.290> interface<00:19:06.540> with<00:19:07.540> things 00:19:07.740 --> 00:19:07.750 align:start position:0% has a different interface with things 00:19:07.750 --> 00:19:09.420 align:start position:0% has a different interface with things like<00:19:07.810> this<00:19:07.930> we<00:19:08.200> can<00:19:08.320> actually<00:19:08.470> rather 00:19:09.420 --> 00:19:09.430 align:start position:0% like this we can actually rather 00:19:09.430 --> 00:19:11.400 align:start position:0% like this we can actually rather flexible<00:19:09.820> even<00:19:10.420> if<00:19:10.570> we<00:19:10.720> have<00:19:10.900> to<00:19:10.930> make<00:19:11.200> changes 00:19:11.400 --> 00:19:11.410 align:start position:0% flexible even if we have to make changes 00:19:11.410 --> 00:19:13.650 align:start position:0% flexible even if we have to make changes in<00:19:11.710> the<00:19:11.770> future<00:19:11.920> and<00:19:12.390> one<00:19:13.390> other<00:19:13.420> thing 00:19:13.650 --> 00:19:13.660 align:start position:0% in the future and one other thing 00:19:13.660 --> 00:19:15.330 align:start position:0% in the future and one other thing towards<00:19:14.230> the<00:19:14.410> tokens<00:19:14.800> book<00:19:14.920> some<00:19:15.070> of<00:19:15.160> the<00:19:15.220> guys 00:19:15.330 --> 00:19:15.340 align:start position:0% towards the tokens book some of the guys 00:19:15.340 --> 00:19:16.830 align:start position:0% towards the tokens book some of the guys from<00:19:15.370> Colossus<00:19:15.940> have<00:19:16.090> that<00:19:16.240> issue<00:19:16.390> that<00:19:16.690> they 00:19:16.830 --> 00:19:16.840 align:start position:0% from Colossus have that issue that they 00:19:16.840 --> 00:19:18.570 align:start position:0% from Colossus have that issue that they want<00:19:17.080> to<00:19:17.230> not<00:19:17.380> only<00:19:17.500> have<00:19:17.710> one<00:19:18.040> contract<00:19:18.460> / 00:19:18.570 --> 00:19:18.580 align:start position:0% want to not only have one contract / 00:19:18.580 --> 00:19:21.210 align:start position:0% want to not only have one contract / token<00:19:19.030> but<00:19:19.450> I<00:19:19.480> have<00:19:19.660> a<00:19:19.740> token<00:19:20.740> contract<00:19:21.100> which 00:19:21.210 --> 00:19:21.220 align:start position:0% token but I have a token contract which 00:19:21.220 --> 00:19:23.550 align:start position:0% token but I have a token contract which holds<00:19:21.520> multiple<00:19:21.730> tokens<00:19:22.150> and<00:19:22.630> that's 00:19:23.550 --> 00:19:23.560 align:start position:0% holds multiple tokens and that's 00:19:23.560 --> 00:19:25.590 align:start position:0% holds multiple tokens and that's actually<00:19:23.770> something<00:19:24.130> were<00:19:24.460> thinking<00:19:24.970> of<00:19:25.150> how 00:19:25.590 --> 00:19:25.600 align:start position:0% actually something were thinking of how 00:19:25.600 --> 00:19:29.180 align:start position:0% actually something were thinking of how we<00:19:25.660> like<00:19:26.170> have<00:19:26.410> token<00:19:27.280> per<00:19:27.880> contract<00:19:28.510> or 00:19:29.180 --> 00:19:29.190 align:start position:0% we like have token per contract or 00:19:29.190 --> 00:19:31.230 align:start position:0% we like have token per contract or multiple<00:19:30.190> tokens<00:19:30.310> per<00:19:30.610> contract<00:19:30.970> and<00:19:31.120> how<00:19:31.180> we 00:19:31.230 --> 00:19:31.240 align:start position:0% multiple tokens per contract and how we 00:19:31.240 --> 00:19:33.840 align:start position:0% multiple tokens per contract and how we bring<00:19:31.540> this<00:19:31.630> into<00:19:31.810> one<00:19:32.020> standard<00:19:32.560> how<00:19:33.400> we<00:19:33.460> make 00:19:33.840 --> 00:19:33.850 align:start position:0% bring this into one standard how we make 00:19:33.850 --> 00:19:35.430 align:start position:0% bring this into one standard how we make this<00:19:34.060> readable<00:19:34.570> for<00:19:34.930> example<00:19:35.200> this<00:19:35.260> would 00:19:35.430 --> 00:19:35.440 align:start position:0% this readable for example this would 00:19:35.440 --> 00:19:37.470 align:start position:0% this readable for example this would require<00:19:35.620> not<00:19:36.130> only<00:19:36.160> having<00:19:36.580> a<00:19:36.640> coin<00:19:36.880> registry 00:19:37.470 --> 00:19:37.480 align:start position:0% require not only having a coin registry 00:19:37.480 --> 00:19:39.790 align:start position:0% require not only having a coin registry which<00:19:37.630> has<00:19:37.810> like<00:19:38.080> token<00:19:38.740> name<00:19:38.950> and<00:19:39.370> add 00:19:39.790 --> 00:19:39.800 align:start position:0% which has like token name and add 00:19:39.800 --> 00:19:41.860 align:start position:0% which has like token name and add but<00:19:40.070> wrong<00:19:40.520> name<00:19:40.760> address<00:19:40.970> an<00:19:41.270> identifier<00:19:41.840> of 00:19:41.860 --> 00:19:41.870 align:start position:0% but wrong name address an identifier of 00:19:41.870 --> 00:19:46.030 align:start position:0% but wrong name address an identifier of the<00:19:42.200> token<00:19:42.530> use<00:19:42.650> inside<00:19:43.010> and<00:19:44.500> so<00:19:45.500> I<00:19:45.710> really 00:19:46.030 --> 00:19:46.040 align:start position:0% the token use inside and so I really 00:19:46.040 --> 00:19:48.610 align:start position:0% the token use inside and so I really would<00:19:46.190> love<00:19:46.400> to<00:19:46.700> we<00:19:47.480> bring<00:19:47.840> the<00:19:47.960> community<00:19:48.140> and 00:19:48.610 --> 00:19:48.620 align:start position:0% would love to we bring the community and 00:19:48.620 --> 00:19:50.290 align:start position:0% would love to we bring the community and come<00:19:49.010> up<00:19:49.130> with<00:19:49.280> what<00:19:49.490> use<00:19:49.730> cases<00:19:49.970> they<00:19:50.270> have 00:19:50.290 --> 00:19:50.300 align:start position:0% come up with what use cases they have 00:19:50.300 --> 00:19:52.480 align:start position:0% come up with what use cases they have and<00:19:50.870> try<00:19:51.080> to<00:19:51.110> find<00:19:51.410> the<00:19:51.650> common<00:19:51.920> standard<00:19:52.340> and 00:19:52.480 --> 00:19:52.490 align:start position:0% and try to find the common standard and 00:19:52.490 --> 00:19:55.650 align:start position:0% and try to find the common standard and I<00:19:52.550> think<00:19:52.730> that's<00:19:52.880> more<00:19:53.030> right<00:19:53.240> a<00:19:53.270> process<00:19:54.250> yeah 00:19:55.650 --> 00:19:55.660 align:start position:0% I think that's more right a process yeah 00:19:55.660 --> 00:19:59.320 align:start position:0% I think that's more right a process yeah so<00:19:56.660> anything<00:19:56.980> regarding<00:19:58.150> standards<00:19:59.150> it's 00:19:59.320 --> 00:19:59.330 align:start position:0% so anything regarding standards it's 00:19:59.330 --> 00:20:01.860 align:start position:0% so anything regarding standards it's also<00:19:59.480> important<00:20:00.020> to<00:20:00.110> just<00:20:00.470> keep<00:20:00.980> in<00:20:01.160> mind<00:20:01.370> that 00:20:01.860 --> 00:20:01.870 align:start position:0% also important to just keep in mind that 00:20:01.870 --> 00:20:05.680 align:start position:0% also important to just keep in mind that module<00:20:02.870> modularity<00:20:03.940> fundamentally<00:20:04.940> is<00:20:05.150> about 00:20:05.680 --> 00:20:05.690 align:start position:0% module modularity fundamentally is about 00:20:05.690 --> 00:20:08.500 align:start position:0% module modularity fundamentally is about upgradeability<00:20:06.650> so<00:20:07.220> if<00:20:07.550> you<00:20:07.790> knew<00:20:08.060> that<00:20:08.090> you 00:20:08.500 --> 00:20:08.510 align:start position:0% upgradeability so if you knew that you 00:20:08.510 --> 00:20:10.780 align:start position:0% upgradeability so if you knew that you know<00:20:08.630> the<00:20:09.170> way<00:20:09.320> things<00:20:09.380> are<00:20:09.800> is<00:20:10.040> exactly<00:20:10.640> the 00:20:10.780 --> 00:20:10.790 align:start position:0% know the way things are is exactly the 00:20:10.790 --> 00:20:12.070 align:start position:0% know the way things are is exactly the way<00:20:10.880> things<00:20:11.060> are<00:20:11.270> going<00:20:11.300> to<00:20:11.510> be<00:20:11.570> forever<00:20:11.810> you 00:20:12.070 --> 00:20:12.080 align:start position:0% way things are going to be forever you 00:20:12.080 --> 00:20:13.180 align:start position:0% way things are going to be forever you might<00:20:12.230> as<00:20:12.350> well<00:20:12.530> just<00:20:12.710> write<00:20:12.890> the<00:20:13.040> whole<00:20:13.130> thing 00:20:13.180 --> 00:20:13.190 align:start position:0% might as well just write the whole thing 00:20:13.190 --> 00:20:15.640 align:start position:0% might as well just write the whole thing in<00:20:13.490> spaghetti<00:20:13.700> code<00:20:14.060> because<00:20:14.390> it's<00:20:14.570> faster<00:20:14.720> so 00:20:15.640 --> 00:20:15.650 align:start position:0% in spaghetti code because it's faster so 00:20:15.650 --> 00:20:19.930 align:start position:0% in spaghetti code because it's faster so the<00:20:17.350> when<00:20:18.350> you<00:20:18.470> have<00:20:18.740> questions<00:20:19.370> of<00:20:19.520> the<00:20:19.670> form 00:20:19.930 --> 00:20:19.940 align:start position:0% the when you have questions of the form 00:20:19.940 --> 00:20:22.810 align:start position:0% the when you have questions of the form you<00:20:20.150> know<00:20:20.270> should<00:20:20.600> X<00:20:20.900> be<00:20:21.200> lumped<00:20:22.070> into<00:20:22.310> object 00:20:22.810 --> 00:20:22.820 align:start position:0% you know should X be lumped into object 00:20:22.820 --> 00:20:24.490 align:start position:0% you know should X be lumped into object a<00:20:23.000> or<00:20:23.210> should<00:20:23.360> actually<00:20:23.510> lumped<00:20:23.930> into<00:20:24.050> object 00:20:24.490 --> 00:20:24.500 align:start position:0% a or should actually lumped into object 00:20:24.500 --> 00:20:26.710 align:start position:0% a or should actually lumped into object be<00:20:24.710> one<00:20:25.040> of<00:20:25.160> the<00:20:25.280> things<00:20:25.910> to<00:20:26.120> think<00:20:26.270> about<00:20:26.420> is 00:20:26.710 --> 00:20:26.720 align:start position:0% be one of the things to think about is 00:20:26.720 --> 00:20:29.140 align:start position:0% be one of the things to think about is you<00:20:26.900> know<00:20:26.930> what<00:20:27.260> what<00:20:28.130> category<00:20:28.940> of<00:20:29.030> those 00:20:29.140 --> 00:20:29.150 align:start position:0% you know what what category of those 00:20:29.150 --> 00:20:31.120 align:start position:0% you know what what category of those objects<00:20:29.630> do<00:20:29.810> you<00:20:29.930> expect<00:20:30.350> to<00:20:30.500> be<00:20:30.650> upgraded 00:20:31.120 --> 00:20:31.130 align:start position:0% objects do you expect to be upgraded 00:20:31.130 --> 00:20:32.560 align:start position:0% objects do you expect to be upgraded more<00:20:31.310> frequently<00:20:31.760> what<00:20:31.970> category<00:20:32.420> do<00:20:32.540> you 00:20:32.560 --> 00:20:32.570 align:start position:0% more frequently what category do you 00:20:32.570 --> 00:20:34.120 align:start position:0% more frequently what category do you expect<00:20:32.930> to<00:20:33.020> be<00:20:33.170> created<00:20:33.500> or<00:20:33.590> destroyed<00:20:33.650> more 00:20:34.120 --> 00:20:34.130 align:start position:0% expect to be created or destroyed more 00:20:34.130 --> 00:20:37.960 align:start position:0% expect to be created or destroyed more frequently<00:20:34.670> so<00:20:35.950> with<00:20:36.950> tokens<00:20:37.250> for<00:20:37.580> example 00:20:37.960 --> 00:20:37.970 align:start position:0% frequently so with tokens for example 00:20:37.970 --> 00:20:39.070 align:start position:0% frequently so with tokens for example we're<00:20:38.090> going<00:20:38.210> to<00:20:38.270> see<00:20:38.390> you<00:20:38.510> keep<00:20:38.720> on<00:20:38.870> seeing 00:20:39.070 --> 00:20:39.080 align:start position:0% we're going to see you keep on seeing 00:20:39.080 --> 00:20:41.530 align:start position:0% we're going to see you keep on seeing you<00:20:39.290> tokens<00:20:39.680> being<00:20:39.920> issued<00:20:40.040> over<00:20:40.310> time<00:20:40.670> you 00:20:41.530 --> 00:20:41.540 align:start position:0% you tokens being issued over time you 00:20:41.540 --> 00:20:42.670 align:start position:0% you tokens being issued over time you have<00:20:41.630> a<00:20:41.690> question<00:20:41.870> of<00:20:42.200> you<00:20:42.260> know<00:20:42.350> do<00:20:42.560> the 00:20:42.670 --> 00:20:42.680 align:start position:0% have a question of you know do the 00:20:42.680 --> 00:20:44.560 align:start position:0% have a question of you know do the existing<00:20:43.220> tokens<00:20:43.580> that<00:20:43.640> get<00:20:43.880> issued<00:20:44.210> are<00:20:44.420> they 00:20:44.560 --> 00:20:44.570 align:start position:0% existing tokens that get issued are they 00:20:44.570 --> 00:20:47.680 align:start position:0% existing tokens that get issued are they going<00:20:44.840> to<00:20:45.020> like<00:20:45.770> are<00:20:46.040> you<00:20:46.670> know<00:20:46.790> who<00:20:47.060> is<00:20:47.210> who<00:20:47.540> is 00:20:47.680 --> 00:20:47.690 align:start position:0% going to like are you know who is who is 00:20:47.690 --> 00:20:50.050 align:start position:0% going to like are you know who is who is going<00:20:47.870> to<00:20:48.080> be<00:20:48.230> upgrading<00:20:49.220> them<00:20:49.400> is<00:20:49.640> anyone 00:20:50.050 --> 00:20:50.060 align:start position:0% going to be upgrading them is anyone 00:20:50.060 --> 00:20:51.400 align:start position:0% going to be upgrading them is anyone supposed<00:20:50.420> to<00:20:50.540> like<00:20:50.690> have<00:20:50.870> ultimate<00:20:51.320> authority 00:20:51.400 --> 00:20:51.410 align:start position:0% supposed to like have ultimate authority 00:20:51.410 --> 00:20:52.690 align:start position:0% supposed to like have ultimate authority over<00:20:51.890> them<00:20:52.070> how<00:20:52.220> are<00:20:52.250> they<00:20:52.460> going<00:20:52.550> to<00:20:52.640> be 00:20:52.690 --> 00:20:52.700 align:start position:0% over them how are they going to be 00:20:52.700 --> 00:20:54.130 align:start position:0% over them how are they going to be upgraded<00:20:52.850> is<00:20:53.270> it<00:20:53.390> just<00:20:53.630> going<00:20:53.780> to<00:20:53.840> be<00:20:53.930> some 00:20:54.130 --> 00:20:54.140 align:start position:0% upgraded is it just going to be some 00:20:54.140 --> 00:20:56.800 align:start position:0% upgraded is it just going to be some religious<00:20:54.580> creating<00:20:55.580> new<00:20:55.910> proxy<00:20:56.180> contracts 00:20:56.800 --> 00:20:56.810 align:start position:0% religious creating new proxy contracts 00:20:56.810 --> 00:20:58.540 align:start position:0% religious creating new proxy contracts for<00:20:57.050> each<00:20:57.200> new<00:20:57.410> standard<00:20:57.860> might<00:20:58.100> actually<00:20:58.310> be 00:20:58.540 --> 00:20:58.550 align:start position:0% for each new standard might actually be 00:20:58.550 --> 00:21:01.620 align:start position:0% for each new standard might actually be a<00:20:58.580> pretty<00:20:58.640> ain't<00:20:58.970> pretty<00:20:59.200> decent<00:21:00.200> approach 00:21:01.620 --> 00:21:01.630 align:start position:0% a pretty ain't pretty decent approach 00:21:01.630 --> 00:21:04.810 align:start position:0% a pretty ain't pretty decent approach another<00:21:02.630> question<00:21:03.460> then<00:21:04.460> you<00:21:04.580> have<00:21:04.730> the 00:21:04.810 --> 00:21:04.820 align:start position:0% another question then you have the 00:21:04.820 --> 00:21:08.080 align:start position:0% another question then you have the question<00:21:05.180> of<00:21:05.360> you<00:21:05.570> know<00:21:05.690> when<00:21:05.960> when<00:21:06.620> are<00:21:07.090> what 00:21:08.080 --> 00:21:08.090 align:start position:0% question of you know when when are what 00:21:08.090 --> 00:21:10.390 align:start position:0% question of you know when when are what is<00:21:08.210> the<00:21:08.330> registry<00:21:08.870> going<00:21:09.650> to<00:21:09.710> be<00:21:09.800> upgraded<00:21:09.950> so 00:21:10.390 --> 00:21:10.400 align:start position:0% is the registry going to be upgraded so 00:21:10.400 --> 00:21:12.460 align:start position:0% is the registry going to be upgraded so for<00:21:10.610> example<00:21:10.670> right<00:21:11.030> now<00:21:11.210> we<00:21:12.200> know<00:21:12.440> that 00:21:12.460 --> 00:21:12.470 align:start position:0% for example right now we know that 00:21:12.470 --> 00:21:14.620 align:start position:0% for example right now we know that tokens<00:21:13.250> have<00:21:13.460> names<00:21:13.700> we<00:21:13.970> know<00:21:14.120> the<00:21:14.240> tokens 00:21:14.620 --> 00:21:14.630 align:start position:0% tokens have names we know the tokens 00:21:14.630 --> 00:21:16.990 align:start position:0% tokens have names we know the tokens might<00:21:14.840> have<00:21:15.020> you<00:21:15.110> know<00:21:15.140> decimal<00:21:15.650> places<00:21:16.000> well 00:21:16.990 --> 00:21:17.000 align:start position:0% might have you know decimal places well 00:21:17.000 --> 00:21:19.090 align:start position:0% might have you know decimal places well guess<00:21:17.390> what<00:21:17.600> ether<00:21:18.020> has<00:21:18.230> you<00:21:18.440> know<00:21:18.560> six<00:21:18.860> sub 00:21:19.090 --> 00:21:19.100 align:start position:0% guess what ether has you know six sub 00:21:19.100 --> 00:21:21.760 align:start position:0% guess what ether has you know six sub denominations<00:21:19.850> and<00:21:20.560> you<00:21:21.560> know<00:21:21.650> eventually 00:21:21.760 --> 00:21:21.770 align:start position:0% denominations and you know eventually 00:21:21.770 --> 00:21:23.080 align:start position:0% denominations and you know eventually people<00:21:22.250> are<00:21:22.430> going<00:21:22.520> to<00:21:22.640> decide<00:21:22.850> that<00:21:22.910> they 00:21:23.080 --> 00:21:23.090 align:start position:0% people are going to decide that they 00:21:23.090 --> 00:21:26.200 align:start position:0% people are going to decide that they want<00:21:23.120> logos<00:21:23.690> and<00:21:24.020> maybe<00:21:24.530> the<00:21:24.830> fad<00:21:25.010> in<00:21:25.310> 2017<00:21:26.030> is 00:21:26.200 --> 00:21:26.210 align:start position:0% want logos and maybe the fad in 2017 is 00:21:26.210 --> 00:21:27.910 align:start position:0% want logos and maybe the fad in 2017 is going<00:21:26.360> to<00:21:26.420> be<00:21:26.510> logos<00:21:26.960> that<00:21:26.990> are<00:21:27.260> in<00:21:27.350> it<00:21:27.440> in<00:21:27.620> the 00:21:27.910 --> 00:21:27.920 align:start position:0% going to be logos that are in it in the 00:21:27.920 --> 00:21:34.360 align:start position:0% going to be logos that are in it in the form<00:21:28.130> of<00:21:28.190> mp4<00:21:28.490> videos<00:21:29.060> so<00:21:30.790> them<00:21:32.740> it's<00:21:33.740> sort<00:21:34.250> of 00:21:34.360 --> 00:21:34.370 align:start position:0% form of mp4 videos so them it's sort of 00:21:34.370 --> 00:21:35.800 align:start position:0% form of mp4 videos so them it's sort of importance<00:21:35.000> to<00:21:35.150> figure<00:21:35.420> out<00:21:35.480> I<00:21:35.510> know<00:21:35.720> exactly 00:21:35.800 --> 00:21:35.810 align:start position:0% importance to figure out I know exactly 00:21:35.810 --> 00:21:38.200 align:start position:0% importance to figure out I know exactly whatever<00:21:36.650> standard<00:21:37.250> we<00:21:37.400> take<00:21:37.640> how<00:21:37.940> that's 00:21:38.200 --> 00:21:38.210 align:start position:0% whatever standard we take how that's 00:21:38.210 --> 00:21:41.740 align:start position:0% whatever standard we take how that's going<00:21:38.420> to<00:21:38.510> handle<00:21:38.780> those<00:21:38.870> kind<00:21:39.110> of<00:21:39.170> situations 00:21:41.740 --> 00:21:41.750 align:start position:0% 00:21:41.750 --> 00:21:45.830 align:start position:0% what<00:21:42.750> one<00:21:43.080> thing<00:21:43.110> that<00:21:43.700> touches<00:21:44.840> both 00:21:45.830 --> 00:21:45.840 align:start position:0% what one thing that touches both 00:21:45.840 --> 00:21:49.700 align:start position:0% what one thing that touches both registries<00:21:46.740> and<00:21:46.769> tokens<00:21:47.370> is<00:21:48.710> named 00:21:49.700 --> 00:21:49.710 align:start position:0% registries and tokens is named 00:21:49.710 --> 00:21:54.350 align:start position:0% registries and tokens is named registries<00:21:50.490> and<00:21:50.760> I<00:21:51.720> think<00:21:51.990> this<00:21:52.230> is<00:21:52.500> a<00:21:53.360> quite 00:21:54.350 --> 00:21:54.360 align:start position:0% registries and I think this is a quite 00:21:54.360 --> 00:21:58.159 align:start position:0% registries and I think this is a quite challenging<00:21:54.889> problem<00:21:55.889> because<00:21:56.750> whenever<00:21:57.750> you 00:21:58.159 --> 00:21:58.169 align:start position:0% challenging problem because whenever you 00:21:58.169 --> 00:22:02.060 align:start position:0% challenging problem because whenever you have<00:21:58.409> a<00:21:59.149> system<00:22:00.149> that<00:22:00.360> registers<00:22:01.070> human 00:22:02.060 --> 00:22:02.070 align:start position:0% have a system that registers human 00:22:02.070 --> 00:22:06.460 align:start position:0% have a system that registers human meaningful<00:22:02.899> strings<00:22:04.940> there's<00:22:05.940> gonna<00:22:06.210> be 00:22:06.460 --> 00:22:06.470 align:start position:0% meaningful strings there's gonna be 00:22:06.470 --> 00:22:09.860 align:start position:0% meaningful strings there's gonna be questions<00:22:07.470> about<00:22:07.950> economics<00:22:08.789> because<00:22:09.419> these 00:22:09.860 --> 00:22:09.870 align:start position:0% questions about economics because these 00:22:09.870 --> 00:22:12.049 align:start position:0% questions about economics because these things<00:22:10.260> have<00:22:10.799> value<00:22:10.830> they<00:22:11.700> have<00:22:11.850> different 00:22:12.049 --> 00:22:12.059 align:start position:0% things have value they have different 00:22:12.059 --> 00:22:14.269 align:start position:0% things have value they have different values<00:22:12.299> for<00:22:12.539> different<00:22:12.720> people<00:22:13.320> you<00:22:14.100> have 00:22:14.269 --> 00:22:14.279 align:start position:0% values for different people you have 00:22:14.279 --> 00:22:16.730 align:start position:0% values for different people you have things<00:22:14.490> like<00:22:14.580> name<00:22:15.389> squatting<00:22:16.110> which<00:22:16.470> is<00:22:16.590> a 00:22:16.730 --> 00:22:16.740 align:start position:0% things like name squatting which is a 00:22:16.740 --> 00:22:20.080 align:start position:0% things like name squatting which is a huge<00:22:16.980> problem<00:22:17.429> in<00:22:17.580> a<00:22:18.120> name<00:22:18.450> coin<00:22:18.750> for<00:22:19.049> instance 00:22:20.080 --> 00:22:20.090 align:start position:0% huge problem in a name coin for instance 00:22:20.090 --> 00:22:24.409 align:start position:0% huge problem in a name coin for instance so<00:22:21.090> so<00:22:21.570> this<00:22:21.950> this<00:22:22.950> is<00:22:23.190> something<00:22:23.370> that<00:22:23.820> you 00:22:24.409 --> 00:22:24.419 align:start position:0% so so this this is something that you 00:22:24.419 --> 00:22:25.460 align:start position:0% so so this this is something that you know<00:22:24.510> we<00:22:24.720> should<00:22:24.870> be<00:22:25.019> thinking<00:22:25.289> very 00:22:25.460 --> 00:22:25.470 align:start position:0% know we should be thinking very 00:22:25.470 --> 00:22:27.669 align:start position:0% know we should be thinking very carefully<00:22:25.679> about<00:22:25.980> and<00:22:26.639> I<00:22:26.700> think<00:22:26.940> you<00:22:27.299> Gavin 00:22:27.669 --> 00:22:27.679 align:start position:0% carefully about and I think you Gavin 00:22:27.679 --> 00:22:32.659 align:start position:0% carefully about and I think you Gavin have<00:22:28.679> thought<00:22:28.950> about<00:22:30.380> auctions<00:22:31.380> in<00:22:32.039> the 00:22:32.659 --> 00:22:32.669 align:start position:0% have thought about auctions in the 00:22:32.669 --> 00:22:37.669 align:start position:0% have thought about auctions in the context<00:22:33.330> of<00:22:34.700> registries<00:22:35.700> etc<00:22:36.299> and<00:22:36.510> so<00:22:36.679> just 00:22:37.669 --> 00:22:37.679 align:start position:0% context of registries etc and so just 00:22:37.679 --> 00:22:41.060 align:start position:0% context of registries etc and so just you<00:22:38.399> know<00:22:38.490> putting<00:22:39.419> it<00:22:39.539> up<00:22:39.630> in<00:22:40.070> registries 00:22:41.060 --> 00:22:41.070 align:start position:0% you know putting it up in registries 00:22:41.070 --> 00:22:42.889 align:start position:0% you know putting it up in registries they<00:22:41.580> serve<00:22:41.850> essentially<00:22:42.389> two<00:22:42.510> purposes 00:22:42.889 --> 00:22:42.899 align:start position:0% they serve essentially two purposes 00:22:42.899 --> 00:22:44.450 align:start position:0% they serve essentially two purposes which<00:22:43.350> is<00:22:43.529> providing<00:22:44.190> additional 00:22:44.450 --> 00:22:44.460 align:start position:0% which is providing additional 00:22:44.460 --> 00:22:46.940 align:start position:0% which is providing additional information<00:22:45.299> additional<00:22:45.990> metadata<00:22:46.139> but<00:22:46.649> also 00:22:46.940 --> 00:22:46.950 align:start position:0% information additional metadata but also 00:22:46.950 --> 00:22:49.310 align:start position:0% information additional metadata but also if<00:22:47.580> there<00:22:48.149> are<00:22:48.210> scenarios<00:22:48.510> where<00:22:48.929> he<00:22:48.990> wants 00:22:49.310 --> 00:22:49.320 align:start position:0% if there are scenarios where he wants 00:22:49.320 --> 00:22:51.549 align:start position:0% if there are scenarios where he wants something<00:22:49.500> like<00:22:49.740> a<00:22:49.769> namespace<00:22:50.279> for<00:22:50.700> certain 00:22:51.549 --> 00:22:51.559 align:start position:0% something like a namespace for certain 00:22:51.559 --> 00:22:54.680 align:start position:0% something like a namespace for certain things<00:22:52.559> to<00:22:52.769> exist<00:22:53.130> like<00:22:53.370> if<00:22:54.149> we<00:22:54.389> if<00:22:54.659> we 00:22:54.680 --> 00:22:54.690 align:start position:0% things to exist like if we if we 00:22:54.690 --> 00:22:58.549 align:start position:0% things to exist like if we if we eventually<00:22:55.139> want<00:22:55.669> a<00:22:56.669> system<00:22:57.299> where<00:22:57.510> like<00:22:58.169> one 00:22:58.549 --> 00:22:58.559 align:start position:0% eventually want a system where like one 00:22:58.559 --> 00:23:01.399 align:start position:0% eventually want a system where like one name<00:22:58.769> which<00:22:59.010> has<00:22:59.250> the<00:22:59.630> namespace<00:23:00.630> in<00:23:00.929> Bitcoin 00:23:01.399 --> 00:23:01.409 align:start position:0% name which has the namespace in Bitcoin 00:23:01.409 --> 00:23:03.289 align:start position:0% name which has the namespace in Bitcoin wallets<00:23:01.769> then<00:23:02.490> you<00:23:02.850> want<00:23:03.059> that 00:23:03.289 --> 00:23:03.299 align:start position:0% wallets then you want that 00:23:03.299 --> 00:23:05.149 align:start position:0% wallets then you want that interoperability<00:23:03.870> to<00:23:04.380> exist<00:23:04.649> in<00:23:04.769> all<00:23:04.950> the 00:23:05.149 --> 00:23:05.159 align:start position:0% interoperability to exist in all the 00:23:05.159 --> 00:23:07.250 align:start position:0% interoperability to exist in all the Bitcoin<00:23:05.519> wallets<00:23:05.880> so<00:23:06.090> then<00:23:06.600> there<00:23:06.960> needs<00:23:07.139> to 00:23:07.250 --> 00:23:07.260 align:start position:0% Bitcoin wallets so then there needs to 00:23:07.260 --> 00:23:10.159 align:start position:0% Bitcoin wallets so then there needs to be<00:23:07.350> like<00:23:07.679> a<00:23:08.480> community<00:23:09.480> decision<00:23:09.929> to 00:23:10.159 --> 00:23:10.169 align:start position:0% be like a community decision to 00:23:10.169 --> 00:23:12.259 align:start position:0% be like a community decision to gravitate<00:23:11.039> towards<00:23:11.429> a<00:23:11.490> certain<00:23:11.639> namespace 00:23:12.259 --> 00:23:12.269 align:start position:0% gravitate towards a certain namespace 00:23:12.269 --> 00:23:14.120 align:start position:0% gravitate towards a certain namespace for<00:23:12.299> certain<00:23:12.779> things<00:23:12.960> and<00:23:13.230> that's<00:23:13.950> probably 00:23:14.120 --> 00:23:14.130 align:start position:0% for certain things and that's probably 00:23:14.130 --> 00:23:15.950 align:start position:0% for certain things and that's probably more<00:23:14.519> difficult<00:23:15.000> thing<00:23:15.149> than<00:23:15.330> just<00:23:15.570> the<00:23:15.720> fact 00:23:15.950 --> 00:23:15.960 align:start position:0% more difficult thing than just the fact 00:23:15.960 --> 00:23:20.570 align:start position:0% more difficult thing than just the fact of<00:23:16.110> registering<00:23:16.860> metadata<00:23:19.370> in<00:23:20.370> one<00:23:20.549> of 00:23:20.570 --> 00:23:20.580 align:start position:0% of registering metadata in one of 00:23:20.580 --> 00:23:23.720 align:start position:0% of registering metadata in one of opinions<00:23:21.240> of<00:23:21.269> that<00:23:21.419> yeah<00:23:22.230> well<00:23:22.500> I<00:23:22.769> kinda<00:23:23.610> want 00:23:23.720 --> 00:23:23.730 align:start position:0% opinions of that yeah well I kinda want 00:23:23.730 --> 00:23:25.610 align:start position:0% opinions of that yeah well I kinda want to<00:23:23.760> go<00:23:23.880> inside<00:23:24.000> track<00:23:24.360> like<00:23:24.539> I<00:23:24.750> think<00:23:25.350> before 00:23:25.610 --> 00:23:25.620 align:start position:0% to go inside track like I think before 00:23:25.620 --> 00:23:26.990 align:start position:0% to go inside track like I think before we<00:23:25.649> can<00:23:25.860> start<00:23:25.889> talking<00:23:26.100> about<00:23:26.460> more<00:23:26.909> like 00:23:26.990 --> 00:23:27.000 align:start position:0% we can start talking about more like 00:23:27.000 --> 00:23:29.210 align:start position:0% we can start talking about more like application<00:23:27.630> level<00:23:27.809> standards<00:23:28.590> we<00:23:29.010> should 00:23:29.210 --> 00:23:29.220 align:start position:0% application level standards we should 00:23:29.220 --> 00:23:31.159 align:start position:0% application level standards we should resolve<00:23:29.639> things<00:23:29.880> like<00:23:30.179> what<00:23:30.690> is<00:23:30.779> the<00:23:30.899> correct 00:23:31.159 --> 00:23:31.169 align:start position:0% resolve things like what is the correct 00:23:31.169 --> 00:23:33.710 align:start position:0% resolve things like what is the correct way<00:23:31.350> to<00:23:31.380> deal<00:23:31.620> with<00:23:31.799> the<00:23:31.919> NS<00:23:32.220> because<00:23:33.179> in<00:23:33.570> the 00:23:33.710 --> 00:23:33.720 align:start position:0% way to deal with the NS because in the 00:23:33.720 --> 00:23:36.320 align:start position:0% way to deal with the NS because in the current<00:23:33.960> standard<00:23:34.320> it's<00:23:34.470> like<00:23:34.710> half<00:23:35.210> you<00:23:36.210> know 00:23:36.320 --> 00:23:36.330 align:start position:0% current standard it's like half you know 00:23:36.330 --> 00:23:38.000 align:start position:0% current standard it's like half you know return<00:23:36.659> value<00:23:37.019> vm<00:23:37.289> check<00:23:37.559> and<00:23:37.769> on<00:23:37.860> the<00:23:37.919> other 00:23:38.000 --> 00:23:38.010 align:start position:0% return value vm check and on the other 00:23:38.010 --> 00:23:39.289 align:start position:0% return value vm check and on the other half<00:23:38.279> don't<00:23:38.490> have<00:23:38.730> that<00:23:38.909> so<00:23:39.120> I'm<00:23:39.210> assuming 00:23:39.289 --> 00:23:39.299 align:start position:0% half don't have that so I'm assuming 00:23:39.299 --> 00:23:40.820 align:start position:0% half don't have that so I'm assuming there's<00:23:39.750> an<00:23:39.779> exception<00:23:40.049> being<00:23:40.380> thrown<00:23:40.649> there 00:23:40.820 --> 00:23:40.830 align:start position:0% there's an exception being thrown there 00:23:40.830 --> 00:23:43.220 align:start position:0% there's an exception being thrown there and<00:23:41.120> this<00:23:42.120> actually<00:23:42.269> is<00:23:42.539> i<00:23:42.690> think<00:23:42.899> in<00:23:42.990> all<00:23:43.110> the 00:23:43.220 --> 00:23:43.230 align:start position:0% and this actually is i think in all the 00:23:43.230 --> 00:23:44.840 align:start position:0% and this actually is i think in all the standard<00:23:43.620> or<00:23:43.799> all<00:23:44.130> the<00:23:44.250> proposed<00:23:44.519> standards 00:23:44.840 --> 00:23:44.850 align:start position:0% standard or all the proposed standards 00:23:44.850 --> 00:23:46.549 align:start position:0% standard or all the proposed standards right<00:23:44.940> now<00:23:45.090> so<00:23:45.630> something<00:23:45.960> like<00:23:45.990> that<00:23:46.289> and 00:23:46.549 --> 00:23:46.559 align:start position:0% right now so something like that and 00:23:46.559 --> 00:23:48.590 align:start position:0% right now so something like that and then<00:23:46.679> maybe<00:23:46.889> some<00:23:47.159> standard<00:23:47.580> design<00:23:48.000> patterns 00:23:48.590 --> 00:23:48.600 align:start position:0% then maybe some standard design patterns 00:23:48.600 --> 00:23:49.049 align:start position:0% then maybe some standard design patterns for<00:23:48.840> up 00:23:49.049 --> 00:23:49.059 align:start position:0% for up 00:23:49.059 --> 00:23:51.210 align:start position:0% for up ability<00:23:49.450> like<00:23:49.480> they<00:23:49.720> were<00:23:49.779> saying<00:23:50.139> once<00:23:51.100> we 00:23:51.210 --> 00:23:51.220 align:start position:0% ability like they were saying once we 00:23:51.220 --> 00:23:52.590 align:start position:0% ability like they were saying once we get<00:23:51.370> those<00:23:51.519> done<00:23:51.850> I<00:23:51.909> think<00:23:52.120> will<00:23:52.360> be<00:23:52.450> much 00:23:52.590 --> 00:23:52.600 align:start position:0% get those done I think will be much 00:23:52.600 --> 00:23:54.899 align:start position:0% get those done I think will be much simpler<00:23:52.990> like<00:23:53.289> I<00:23:53.559> think<00:23:54.279> the<00:23:54.429> standards<00:23:54.820> will 00:23:54.899 --> 00:23:54.909 align:start position:0% simpler like I think the standards will 00:23:54.909 --> 00:23:56.430 align:start position:0% simpler like I think the standards will just<00:23:55.090> emerge<00:23:55.450> naturally<00:23:55.690> like<00:23:56.080> a<00:23:56.110> couple<00:23:56.320> of 00:23:56.430 --> 00:23:56.440 align:start position:0% just emerge naturally like a couple of 00:23:56.440 --> 00:23:58.320 align:start position:0% just emerge naturally like a couple of people<00:23:56.649> will<00:23:56.769> make<00:23:56.919> some<00:23:57.460> great<00:23:57.610> wallets<00:23:58.029> with 00:23:58.320 --> 00:23:58.330 align:start position:0% people will make some great wallets with 00:23:58.330 --> 00:23:59.999 align:start position:0% people will make some great wallets with decent<00:23:58.990> standards<00:23:59.350> everyone<00:23:59.649> will<00:23:59.769> want<00:23:59.950> to 00:23:59.999 --> 00:24:00.009 align:start position:0% decent standards everyone will want to 00:24:00.009 --> 00:24:01.590 align:start position:0% decent standards everyone will want to be<00:24:00.249> compatible<00:24:00.700> with<00:24:00.730> that<00:24:00.909> wallet<00:24:01.269> and<00:24:01.450> that 00:24:01.590 --> 00:24:01.600 align:start position:0% be compatible with that wallet and that 00:24:01.600 --> 00:24:02.730 align:start position:0% be compatible with that wallet and that there<00:24:01.779> is<00:24:01.840> your<00:24:01.960> standard<00:24:02.259> like<00:24:02.440> it<00:24:02.529> won't 00:24:02.730 --> 00:24:02.740 align:start position:0% there is your standard like it won't 00:24:02.740 --> 00:24:03.989 align:start position:0% there is your standard like it won't change<00:24:02.950> until<00:24:03.190> someone<00:24:03.610> makes<00:24:03.639> a<00:24:03.850> better 00:24:03.989 --> 00:24:03.999 align:start position:0% change until someone makes a better 00:24:03.999 --> 00:24:07.680 align:start position:0% change until someone makes a better thing<00:24:04.299> I<00:24:05.249> really<00:24:06.249> agree<00:24:06.370> with<00:24:06.580> this<00:24:06.879> you<00:24:07.419> think 00:24:07.680 --> 00:24:07.690 align:start position:0% thing I really agree with this you think 00:24:07.690 --> 00:24:10.710 align:start position:0% thing I really agree with this you think it<00:24:07.840> will<00:24:08.019> evolve<00:24:08.409> naturally<00:24:08.740> like<00:24:09.720> Twitter 00:24:10.710 --> 00:24:10.720 align:start position:0% it will evolve naturally like Twitter 00:24:10.720 --> 00:24:12.659 align:start position:0% it will evolve naturally like Twitter took<00:24:11.019> on<00:24:11.169> other<00:24:11.499> things<00:24:11.860> to<00:24:12.039> run<00:24:12.159> if<00:24:12.340> somebody 00:24:12.659 --> 00:24:12.669 align:start position:0% took on other things to run if somebody 00:24:12.669 --> 00:24:13.980 align:start position:0% took on other things to run if somebody does<00:24:12.909> something<00:24:13.120> which<00:24:13.480> a<00:24:13.629> lot<00:24:13.809> of<00:24:13.840> people 00:24:13.980 --> 00:24:13.990 align:start position:0% does something which a lot of people 00:24:13.990 --> 00:24:16.139 align:start position:0% does something which a lot of people like<00:24:14.470> the<00:24:14.679> way<00:24:14.769> it's<00:24:14.950> done<00:24:15.159> they<00:24:15.639> will<00:24:15.850> adopt 00:24:16.139 --> 00:24:16.149 align:start position:0% like the way it's done they will adopt 00:24:16.149 --> 00:24:18.360 align:start position:0% like the way it's done they will adopt it<00:24:16.360> and<00:24:16.480> it<00:24:16.600> will<00:24:16.749> release<00:24:17.529> become<00:24:18.190> the 00:24:18.360 --> 00:24:18.370 align:start position:0% it and it will release become the 00:24:18.370 --> 00:24:21.810 align:start position:0% it and it will release become the standard<00:24:18.549> and<00:24:18.940> with<00:24:19.179> time<00:24:19.499> so<00:24:20.499> but<00:24:21.460> I<00:24:21.490> really 00:24:21.810 --> 00:24:21.820 align:start position:0% standard and with time so but I really 00:24:21.820 --> 00:24:23.279 align:start position:0% standard and with time so but I really would<00:24:21.970> like<00:24:22.119> for<00:24:22.179> now<00:24:22.539> because<00:24:22.809> we<00:24:23.019> are<00:24:23.049> very 00:24:23.279 --> 00:24:23.289 align:start position:0% would like for now because we are very 00:24:23.289 --> 00:24:26.730 align:start position:0% would like for now because we are very early<00:24:23.740> in<00:24:23.769> this<00:24:24.009> game<00:24:24.809> to<00:24:25.809> have<00:24:26.200> like<00:24:26.470> more 00:24:26.730 --> 00:24:26.740 align:start position:0% early in this game to have like more 00:24:26.740 --> 00:24:29.190 align:start position:0% early in this game to have like more community<00:24:27.369> approach<00:24:27.820> bringing<00:24:28.480> in<00:24:28.600> ideas<00:24:28.990> I 00:24:29.190 --> 00:24:29.200 align:start position:0% community approach bringing in ideas I 00:24:29.200 --> 00:24:30.749 align:start position:0% community approach bringing in ideas I mean<00:24:29.379> this<00:24:29.470> can<00:24:29.679> be<00:24:29.830> a<00:24:29.860> lengthy<00:24:30.039> process<00:24:30.249> and 00:24:30.749 --> 00:24:30.759 align:start position:0% mean this can be a lengthy process and 00:24:30.759 --> 00:24:33.989 align:start position:0% mean this can be a lengthy process and it<00:24:30.970> can't<00:24:30.999> be<00:24:31.330> like<00:24:31.509> a<00:24:31.539> like<00:24:32.999> discussing 00:24:33.989 --> 00:24:33.999 align:start position:0% it can't be like a like discussing 00:24:33.999 --> 00:24:35.730 align:start position:0% it can't be like a like discussing sometimes<00:24:34.570> take<00:24:34.779> time<00:24:35.049> and<00:24:35.080> maybe<00:24:35.499> they'll 00:24:35.730 --> 00:24:35.740 align:start position:0% sometimes take time and maybe they'll 00:24:35.740 --> 00:24:39.409 align:start position:0% sometimes take time and maybe they'll eat<00:24:35.919> somewhere<00:24:36.669> in<00:24:36.879> this<00:24:37.090> stuck<00:24:37.419> path<00:24:38.379> but 00:24:39.409 --> 00:24:39.419 align:start position:0% eat somewhere in this stuck path but 00:24:39.419 --> 00:24:41.759 align:start position:0% eat somewhere in this stuck path but it's<00:24:40.419> about<00:24:40.629> like<00:24:40.779> bringing<00:24:41.169> ideas<00:24:41.289> together 00:24:41.759 --> 00:24:41.769 align:start position:0% it's about like bringing ideas together 00:24:41.769 --> 00:24:44.220 align:start position:0% it's about like bringing ideas together and<00:24:42.249> because<00:24:42.850> so<00:24:43.450> many<00:24:43.570> things<00:24:43.869> we<00:24:43.990> can't 00:24:44.220 --> 00:24:44.230 align:start position:0% and because so many things we can't 00:24:44.230 --> 00:24:46.350 align:start position:0% and because so many things we can't think<00:24:44.470> of<00:24:44.649> even<00:24:44.860> yet<00:24:45.159> where<00:24:45.759> this<00:24:45.879> is<00:24:45.940> going 00:24:46.350 --> 00:24:46.360 align:start position:0% think of even yet where this is going 00:24:46.360 --> 00:24:48.840 align:start position:0% think of even yet where this is going what<00:24:46.570> all<00:24:46.779> will<00:24:46.960> be<00:24:47.110> necessary<00:24:47.289> so<00:24:48.249> everything 00:24:48.840 --> 00:24:48.850 align:start position:0% what all will be necessary so everything 00:24:48.850 --> 00:24:51.450 align:start position:0% what all will be necessary so everything we<00:24:48.940> come<00:24:49.149> up<00:24:49.269> probably<00:24:49.809> will<00:24:50.049> maybe<00:24:50.980> be<00:24:51.129> very 00:24:51.450 --> 00:24:51.460 align:start position:0% we come up probably will maybe be very 00:24:51.460 --> 00:24:53.220 align:start position:0% we come up probably will maybe be very simplistic<00:24:52.090> from<00:24:52.299> head<00:24:52.570> to<00:24:52.659> what<00:24:52.809> we<00:24:52.929> need<00:24:53.080> at 00:24:53.220 --> 00:24:53.230 align:start position:0% simplistic from head to what we need at 00:24:53.230 --> 00:24:57.330 align:start position:0% simplistic from head to what we need at some<00:24:53.379> point<00:24:53.700> yeah<00:24:54.700> I<00:24:55.379> think<00:24:56.379> one<00:24:56.679> of<00:24:56.710> the<00:24:56.919> one 00:24:57.330 --> 00:24:57.340 align:start position:0% some point yeah I think one of the one 00:24:57.340 --> 00:24:58.950 align:start position:0% some point yeah I think one of the one of<00:24:57.429> the<00:24:57.519> things<00:24:57.700> i<00:24:57.789> want<00:24:57.970> to<00:24:58.029> point<00:24:58.389> I<00:24:58.779> want<00:24:58.929> to 00:24:58.950 --> 00:24:58.960 align:start position:0% of the things i want to point I want to 00:24:58.960 --> 00:25:01.289 align:start position:0% of the things i want to point I want to make<00:24:59.019> on<00:24:59.230> that<00:24:59.350> is<00:24:59.649> the<00:25:00.340> way<00:25:00.879> the<00:25:01.029> current 00:25:01.289 --> 00:25:01.299 align:start position:0% make on that is the way the current 00:25:01.299 --> 00:25:03.749 align:start position:0% make on that is the way the current standards<00:25:01.720> work<00:25:02.230> is<00:25:02.470> whoever<00:25:02.860> edit<00:25:03.309> the<00:25:03.490> wiki 00:25:03.749 --> 00:25:03.759 align:start position:0% standards work is whoever edit the wiki 00:25:03.759 --> 00:25:08.430 align:start position:0% standards work is whoever edit the wiki the<00:25:04.240> last<00:25:04.539> time<00:25:04.869> and<00:25:05.529> I<00:25:05.649> think<00:25:06.539> if<00:25:07.539> it<00:25:07.690> was<00:25:07.779> very 00:25:08.430 --> 00:25:08.440 align:start position:0% the last time and I think if it was very 00:25:08.440 --> 00:25:10.200 align:start position:0% the last time and I think if it was very great<00:25:08.679> I<00:25:08.710> think<00:25:08.860> we<00:25:09.249> can<00:25:09.460> move<00:25:09.669> towards<00:25:10.059> just 00:25:10.200 --> 00:25:10.210 align:start position:0% great I think we can move towards just 00:25:10.210 --> 00:25:12.210 align:start position:0% great I think we can move towards just it<00:25:10.749> doesn't<00:25:11.169> have<00:25:11.230> to<00:25:11.320> be<00:25:11.440> very<00:25:11.740> complicated 00:25:12.210 --> 00:25:12.220 align:start position:0% it doesn't have to be very complicated 00:25:12.220 --> 00:25:14.669 align:start position:0% it doesn't have to be very complicated we<00:25:12.580> don't<00:25:12.730> have<00:25:12.850> to<00:25:12.940> put<00:25:13.059> up<00:25:13.320> mailing<00:25:14.320> lists 00:25:14.669 --> 00:25:14.679 align:start position:0% we don't have to put up mailing lists 00:25:14.679 --> 00:25:16.499 align:start position:0% we don't have to put up mailing lists and<00:25:14.860> like<00:25:15.100> get<00:25:15.460> a<00:25:15.490> committee<00:25:15.879> on<00:25:16.090> things<00:25:16.360> in 00:25:16.499 --> 00:25:16.509 align:start position:0% and like get a committee on things in 00:25:16.509 --> 00:25:17.700 align:start position:0% and like get a committee on things in whatever<00:25:16.779> but<00:25:17.080> I<00:25:17.110> think<00:25:17.379> it<00:25:17.440> would<00:25:17.529> be<00:25:17.590> great 00:25:17.700 --> 00:25:17.710 align:start position:0% whatever but I think it would be great 00:25:17.710 --> 00:25:20.940 align:start position:0% whatever but I think it would be great if<00:25:17.799> there's<00:25:18.070> a<00:25:18.480> sort<00:25:19.480> of<00:25:19.570> a<00:25:19.840> stamp<00:25:20.529> of<00:25:20.769> approval 00:25:20.940 --> 00:25:20.950 align:start position:0% if there's a sort of a stamp of approval 00:25:20.950 --> 00:25:23.070 align:start position:0% if there's a sort of a stamp of approval from<00:25:21.279> various<00:25:21.789> poor<00:25:21.999> people<00:25:22.330> that<00:25:22.509> this<00:25:22.659> this 00:25:23.070 --> 00:25:23.080 align:start position:0% from various poor people that this this 00:25:23.080 --> 00:25:24.659 align:start position:0% from various poor people that this this feels<00:25:23.409> like<00:25:23.590> the<00:25:23.740> best<00:25:24.009> approach<00:25:24.220> at<00:25:24.549> the 00:25:24.659 --> 00:25:24.669 align:start position:0% feels like the best approach at the 00:25:24.669 --> 00:25:27.960 align:start position:0% feels like the best approach at the moment<00:25:25.029> but<00:25:25.929> we<00:25:26.769> could<00:25:27.129> we<00:25:27.429> could<00:25:27.549> like<00:25:27.730> make<00:25:27.940> a 00:25:27.960 --> 00:25:27.970 align:start position:0% moment but we could we could like make a 00:25:27.970 --> 00:25:30.570 align:start position:0% moment but we could we could like make a discussion<00:25:28.779> on<00:25:29.019> read<00:25:29.230> it<00:25:29.259> and<00:25:29.470> get<00:25:29.830> a<00:25:30.039> lot<00:25:30.519> of 00:25:30.570 --> 00:25:30.580 align:start position:0% discussion on read it and get a lot of 00:25:30.580 --> 00:25:34.580 align:start position:0% discussion on read it and get a lot of people<00:25:30.879> involved<00:25:31.119> to<00:25:31.690> see<00:25:31.899> what<00:25:32.049> they<00:25:32.200> think 00:25:34.580 --> 00:25:34.590 align:start position:0% 00:25:34.590 --> 00:25:37.980 align:start position:0% so<00:25:35.590> so<00:25:36.340> having<00:25:36.730> actually<00:25:37.570> I<00:25:37.629> think<00:25:37.659> the<00:25:37.869> good 00:25:37.980 --> 00:25:37.990 align:start position:0% so so having actually I think the good 00:25:37.990 --> 00:25:39.210 align:start position:0% so so having actually I think the good idea<00:25:38.289> would<00:25:38.409> be<00:25:38.440> actually<00:25:38.740> using<00:25:38.980> gist 00:25:39.210 --> 00:25:39.220 align:start position:0% idea would be actually using gist 00:25:39.220 --> 00:25:41.009 align:start position:0% idea would be actually using gist because<00:25:39.730> in<00:25:39.879> this<00:25:39.999> you<00:25:40.179> can<00:25:40.330> comment<00:25:40.539> on<00:25:40.809> the 00:25:41.009 --> 00:25:41.019 align:start position:0% because in this you can comment on the 00:25:41.019 --> 00:25:43.889 align:start position:0% because in this you can comment on the gist<00:25:41.320> and<00:25:41.590> then<00:25:42.159> it<00:25:42.429> moves<00:25:42.730> to<00:25:42.909> a<00:25:42.970> wiki<00:25:43.269> right 00:25:43.889 --> 00:25:43.899 align:start position:0% gist and then it moves to a wiki right 00:25:43.899 --> 00:25:45.570 align:start position:0% gist and then it moves to a wiki right now<00:25:44.049> kind<00:25:44.289> of<00:25:44.409> like<00:25:44.559> it's<00:25:44.710> a<00:25:44.769> little<00:25:44.889> a<00:25:45.129> little 00:25:45.570 --> 00:25:45.580 align:start position:0% now kind of like it's a little a little 00:25:45.580 --> 00:25:49.019 align:start position:0% now kind of like it's a little a little bit<00:25:45.730> like<00:25:45.970> a<00:25:45.999> Wikipedia<00:25:46.769> edit<00:25:47.769> war<00:25:48.039> kind<00:25:48.909> of 00:25:49.019 --> 00:25:49.029 align:start position:0% bit like a Wikipedia edit war kind of 00:25:49.029 --> 00:25:51.720 align:start position:0% bit like a Wikipedia edit war kind of thing<00:25:49.210> not<00:25:49.419> not<00:25:49.749> that<00:25:49.929> much<00:25:50.169> but<00:25:50.519> bit<00:25:51.519> yeah 00:25:51.720 --> 00:25:51.730 align:start position:0% thing not not that much but bit yeah 00:25:51.730 --> 00:25:53.430 align:start position:0% thing not not that much but bit yeah this<00:25:52.210> is<00:25:52.330> definitely<00:25:52.450> having<00:25:52.869> places<00:25:53.289> where 00:25:53.430 --> 00:25:53.440 align:start position:0% this is definitely having places where 00:25:53.440 --> 00:25:56.100 align:start position:0% this is definitely having places where we<00:25:53.529> can<00:25:53.649> bring<00:25:54.009> together<00:25:54.399> examples<00:25:55.119> and<00:25:55.360> have 00:25:56.100 --> 00:25:56.110 align:start position:0% we can bring together examples and have 00:25:56.110 --> 00:25:59.320 align:start position:0% we can bring together examples and have to<00:25:56.289> have<00:25:56.499> these<00:25:56.649> talks 00:25:59.320 --> 00:25:59.330 align:start position:0% 00:25:59.330 --> 00:26:04.240 align:start position:0% okay<00:25:59.750> I<00:26:00.550> think<00:26:01.550> the<00:26:02.260> last<00:26:03.260> topic<00:26:03.560> before<00:26:03.800> I 00:26:04.240 --> 00:26:04.250 align:start position:0% okay I think the last topic before I 00:26:04.250 --> 00:26:06.730 align:start position:0% okay I think the last topic before I think<00:26:04.520> we<00:26:05.330> end<00:26:05.480> up<00:26:05.570> ten<00:26:05.810> parts<00:26:06.140> i<00:26:06.260> think<00:26:06.500> will 00:26:06.730 --> 00:26:06.740 align:start position:0% think we end up ten parts i think will 00:26:06.740 --> 00:26:08.080 align:start position:0% think we end up ten parts i think will be<00:26:06.830> I<00:26:07.040> think<00:26:07.280> they're<00:26:07.400> probably<00:26:07.520> people<00:26:07.940> have 00:26:08.080 --> 00:26:08.090 align:start position:0% be I think they're probably people have 00:26:08.090 --> 00:26:10.000 align:start position:0% be I think they're probably people have some<00:26:08.240> questions<00:26:08.630> so<00:26:08.690> I<00:26:08.780> think<00:26:09.020> one<00:26:09.740> last<00:26:09.890> thing 00:26:10.000 --> 00:26:10.010 align:start position:0% some questions so I think one last thing 00:26:10.010 --> 00:26:14.470 align:start position:0% some questions so I think one last thing i<00:26:10.130> want<00:26:10.280> to<00:26:10.310> touch<00:26:10.460> upon<00:26:10.640> is<00:26:12.460> do<00:26:13.460> we<00:26:14.000> feel<00:26:14.420> that 00:26:14.470 --> 00:26:14.480 align:start position:0% i want to touch upon is do we feel that 00:26:14.480 --> 00:26:18.580 align:start position:0% i want to touch upon is do we feel that there<00:26:15.140> should<00:26:15.200> be<00:26:15.740> a<00:26:16.570> more<00:26:17.570> like<00:26:17.750> formal 00:26:18.580 --> 00:26:18.590 align:start position:0% there should be a more like formal 00:26:18.590 --> 00:26:22.330 align:start position:0% there should be a more like formal process<00:26:19.130> for<00:26:19.460> defining<00:26:20.270> standards<00:26:20.810> and<00:26:21.340> maybe 00:26:22.330 --> 00:26:22.340 align:start position:0% process for defining standards and maybe 00:26:22.340 --> 00:26:24.010 align:start position:0% process for defining standards and maybe into<00:26:22.610> the<00:26:22.700> future<00:26:22.910> not<00:26:23.180> not<00:26:23.450> at<00:26:23.600> the<00:26:23.690> moment<00:26:23.810> i 00:26:24.010 --> 00:26:24.020 align:start position:0% into the future not not at the moment i 00:26:24.020 --> 00:26:25.240 align:start position:0% into the future not not at the moment i think<00:26:24.200> at<00:26:24.290> the<00:26:24.350> moment<00:26:24.380> it's<00:26:24.770> sort<00:26:25.190> of 00:26:25.240 --> 00:26:25.250 align:start position:0% think at the moment it's sort of 00:26:25.250 --> 00:26:28.450 align:start position:0% think at the moment it's sort of nebulous<00:26:25.910> and<00:26:26.390> and<00:26:26.660> and<00:26:27.110> and<00:26:27.740> growing 00:26:28.450 --> 00:26:28.460 align:start position:0% nebulous and and and and growing 00:26:28.460 --> 00:26:30.790 align:start position:0% nebulous and and and and growing organically<00:26:28.970> but<00:26:29.270> you<00:26:29.690> know<00:26:29.810> bitcoin<00:26:30.470> has<00:26:30.500> the 00:26:30.790 --> 00:26:30.800 align:start position:0% organically but you know bitcoin has the 00:26:30.800 --> 00:26:34.510 align:start position:0% organically but you know bitcoin has the improve<00:26:31.790> all<00:26:32.350> process<00:26:33.350> the<00:26:33.590> books<00:26:33.830> right<00:26:34.070> is 00:26:34.510 --> 00:26:34.520 align:start position:0% improve all process the books right is 00:26:34.520 --> 00:26:37.300 align:start position:0% improve all process the books right is there<00:26:34.970> something<00:26:35.390> that<00:26:35.600> currently<00:26:36.590> exists<00:26:37.070> in 00:26:37.300 --> 00:26:37.310 align:start position:0% there something that currently exists in 00:26:37.310 --> 00:26:39.940 align:start position:0% there something that currently exists in the<00:26:37.700> hearing<00:26:38.120> community<00:26:38.150> or<00:26:38.780> is<00:26:39.080> there<00:26:39.350> and<00:26:39.560> is 00:26:39.940 --> 00:26:39.950 align:start position:0% the hearing community or is there and is 00:26:39.950 --> 00:26:41.550 align:start position:0% the hearing community or is there and is this<00:26:40.100> something<00:26:40.250> we<00:26:40.460> need<00:26:40.670> to<00:26:40.700> consider<00:26:41.000> more 00:26:41.550 --> 00:26:41.560 align:start position:0% this something we need to consider more 00:26:41.560 --> 00:26:44.710 align:start position:0% this something we need to consider more yeah<00:26:42.560> so<00:26:42.860> there's<00:26:43.070> quite<00:26:43.970> recently<00:26:44.450> I<00:26:44.540> think 00:26:44.710 --> 00:26:44.720 align:start position:0% yeah so there's quite recently I think 00:26:44.720 --> 00:26:46.300 align:start position:0% yeah so there's quite recently I think it's<00:26:44.810> a<00:26:44.870> couple<00:26:45.050> of<00:26:45.110> weeks<00:26:45.230> ago<00:26:45.290> Martin<00:26:45.770> set 00:26:46.300 --> 00:26:46.310 align:start position:0% it's a couple of weeks ago Martin set 00:26:46.310 --> 00:26:50.890 align:start position:0% it's a couple of weeks ago Martin set out<00:26:46.460> the<00:26:46.640> eip<00:26:47.050> so<00:26:48.190> okay<00:26:49.190> great<00:26:49.310> yeah<00:26:49.640> and<00:26:50.540> and 00:26:50.890 --> 00:26:50.900 align:start position:0% out the eip so okay great yeah and and 00:26:50.900 --> 00:26:53.770 align:start position:0% out the eip so okay great yeah and and there's<00:26:51.650> a<00:26:51.710> wiki<00:26:51.980> for<00:26:52.280> its<00:26:52.400> well<00:26:52.780> information 00:26:53.770 --> 00:26:53.780 align:start position:0% there's a wiki for its well information 00:26:53.780 --> 00:26:56.500 align:start position:0% there's a wiki for its well information about<00:26:53.930> the<00:26:54.140> okay<00:26:54.950> well<00:26:55.610> that's<00:26:55.730> that's<00:26:56.240> that's 00:26:56.500 --> 00:26:56.510 align:start position:0% about the okay well that's that's that's 00:26:56.510 --> 00:27:00.790 align:start position:0% about the okay well that's that's that's great<00:26:56.630> then<00:26:59.050> this<00:27:00.050> is<00:27:00.170> read<00:27:00.380> about<00:27:00.650> the 00:27:00.790 --> 00:27:00.800 align:start position:0% great then this is read about the 00:27:00.800 --> 00:27:03.490 align:start position:0% great then this is read about the theorem<00:27:01.280> protocol<00:27:01.700> updates<00:27:02.120> but<00:27:02.810> one<00:27:03.320> can 00:27:03.490 --> 00:27:03.500 align:start position:0% theorem protocol updates but one can 00:27:03.500 --> 00:27:05.590 align:start position:0% theorem protocol updates but one can think<00:27:03.650> of<00:27:03.830> like<00:27:04.010> for<00:27:04.370> all<00:27:04.400> kind<00:27:04.640> of<00:27:04.730> things<00:27:04.790> but 00:27:05.590 --> 00:27:05.600 align:start position:0% think of like for all kind of things but 00:27:05.600 --> 00:27:07.240 align:start position:0% think of like for all kind of things but right<00:27:06.140> now<00:27:06.260> I<00:27:06.290> think<00:27:06.470> it's<00:27:06.680> like<00:27:06.920> you<00:27:07.040> say<00:27:07.220> it's 00:27:07.240 --> 00:27:07.250 align:start position:0% right now I think it's like you say it's 00:27:07.250 --> 00:27:09.880 align:start position:0% right now I think it's like you say it's very<00:27:07.490> early<00:27:07.880> stage<00:27:08.300> it's<00:27:08.570> very<00:27:09.440> much<00:27:09.680> or 00:27:09.880 --> 00:27:09.890 align:start position:0% very early stage it's very much or 00:27:09.890 --> 00:27:12.610 align:start position:0% very early stage it's very much or exploration<00:27:10.250> pace<00:27:10.760> so<00:27:11.090> I<00:27:11.120> would<00:27:11.450> it's<00:27:11.840> a<00:27:12.080> lot 00:27:12.610 --> 00:27:12.620 align:start position:0% exploration pace so I would it's a lot 00:27:12.620 --> 00:27:14.530 align:start position:0% exploration pace so I would it's a lot of<00:27:12.830> things<00:27:13.040> like<00:27:13.190> trying<00:27:13.550> things<00:27:13.880> out<00:27:14.060> and<00:27:14.330> and 00:27:14.530 --> 00:27:14.540 align:start position:0% of things like trying things out and and 00:27:14.540 --> 00:27:17.110 align:start position:0% of things like trying things out and and see<00:27:14.960> what<00:27:15.110> catches<00:27:15.380> on<00:27:15.710> maybe<00:27:16.310> it's<00:27:16.580> about<00:27:16.730> who 00:27:17.110 --> 00:27:17.120 align:start position:0% see what catches on maybe it's about who 00:27:17.120 --> 00:27:19.300 align:start position:0% see what catches on maybe it's about who I<00:27:17.480> mean<00:27:17.690> we<00:27:17.810> can<00:27:17.960> make<00:27:18.110> up<00:27:18.260> a<00:27:18.350> standard<00:27:18.770> if 00:27:19.300 --> 00:27:19.310 align:start position:0% I mean we can make up a standard if 00:27:19.310 --> 00:27:21.820 align:start position:0% I mean we can make up a standard if nobody<00:27:19.760> follows<00:27:20.150> is<00:27:20.300> that<00:27:20.510> systemic<00:27:21.200> written 00:27:21.820 --> 00:27:21.830 align:start position:0% nobody follows is that systemic written 00:27:21.830 --> 00:27:24.550 align:start position:0% nobody follows is that systemic written right<00:27:21.980> yeah<00:27:22.910> I<00:27:23.450> definitely<00:27:23.540> think<00:27:23.900> the<00:27:24.080> Darien 00:27:24.550 --> 00:27:24.560 align:start position:0% right yeah I definitely think the Darien 00:27:24.560 --> 00:27:26.260 align:start position:0% right yeah I definitely think the Darien foundations<00:27:25.100> role<00:27:25.370> should<00:27:25.640> be<00:27:25.700> like 00:27:26.260 --> 00:27:26.270 align:start position:0% foundations role should be like 00:27:26.270 --> 00:27:27.880 align:start position:0% foundations role should be like facilitating<00:27:26.930> discussions<00:27:26.960> and<00:27:27.650> all<00:27:27.740> this 00:27:27.880 --> 00:27:27.890 align:start position:0% facilitating discussions and all this 00:27:27.890 --> 00:27:29.410 align:start position:0% facilitating discussions and all this and<00:27:28.070> not<00:27:28.190> defining<00:27:28.790> standards<00:27:29.210> and 00:27:29.410 --> 00:27:29.420 align:start position:0% and not defining standards and 00:27:29.420 --> 00:27:32.830 align:start position:0% and not defining standards and definitely<00:27:29.960> not<00:27:30.110> like<00:27:30.490> creating<00:27:31.490> apps<00:27:31.840> then 00:27:32.830 --> 00:27:32.840 align:start position:0% definitely not like creating apps then 00:27:32.840 --> 00:27:34.330 align:start position:0% definitely not like creating apps then you<00:27:32.960> have<00:27:33.140> to<00:27:33.320> follow<00:27:33.710> those<00:27:33.920> standards 00:27:34.330 --> 00:27:34.340 align:start position:0% you have to follow those standards 00:27:34.340 --> 00:27:35.560 align:start position:0% you have to follow those standards because<00:27:34.460> that's<00:27:34.670> the<00:27:34.820> official<00:27:35.060> one<00:27:35.360> you<00:27:35.480> know 00:27:35.560 --> 00:27:35.570 align:start position:0% because that's the official one you know 00:27:35.570 --> 00:27:38.350 align:start position:0% because that's the official one you know like<00:27:35.780> yeah<00:27:36.470> again<00:27:37.280> there's<00:27:37.850> about<00:27:38.060> five 00:27:38.350 --> 00:27:38.360 align:start position:0% like yeah again there's about five 00:27:38.360 --> 00:27:40.510 align:start position:0% like yeah again there's about five minutes<00:27:38.990> left<00:27:39.230> I<00:27:39.380> think<00:27:39.590> we<00:27:39.740> open<00:27:40.310> up<00:27:40.340> some 00:27:40.510 --> 00:27:40.520 align:start position:0% minutes left I think we open up some 00:27:40.520 --> 00:27:44.500 align:start position:0% minutes left I think we open up some questions<00:27:40.880> over<00:27:41.510> there<00:27:43.060> 15<00:27:44.060> minutes<00:27:44.270> left 00:27:44.500 --> 00:27:44.510 align:start position:0% questions over there 15 minutes left 00:27:44.510 --> 00:28:09.700 align:start position:0% questions over there 15 minutes left okay<00:27:44.960> well<00:27:45.380> Viper 00:28:09.700 --> 00:28:09.710 align:start position:0% 00:28:09.710 --> 00:28:14.570 align:start position:0% some<00:28:10.710> other<00:28:10.860> address<00:28:11.450> yeah<00:28:13.250> basically<00:28:14.250> the 00:28:14.570 --> 00:28:14.580 align:start position:0% some other address yeah basically the 00:28:14.580 --> 00:28:15.770 align:start position:0% some other address yeah basically the fundamental<00:28:15.000> issue<00:28:15.150> here<00:28:15.390> is<00:28:15.480> that<00:28:15.510> caught 00:28:15.770 --> 00:28:15.780 align:start position:0% fundamental issue here is that caught 00:28:15.780 --> 00:28:18.650 align:start position:0% fundamental issue here is that caught the<00:28:15.900> call<00:28:16.080> code<00:28:16.320> operator<00:28:17.060> maintains<00:28:18.060> all<00:28:18.270> the 00:28:18.650 --> 00:28:18.660 align:start position:0% the call code operator maintains all the 00:28:18.660 --> 00:28:20.720 align:start position:0% the call code operator maintains all the same<00:28:18.810> state<00:28:19.020> except<00:28:19.560> for<00:28:19.710> the<00:28:19.800> sender<00:28:20.070> so<00:28:20.550> it 00:28:20.720 --> 00:28:20.730 align:start position:0% same state except for the sender so it 00:28:20.730 --> 00:28:22.850 align:start position:0% same state except for the sender so it sort<00:28:21.300> of<00:28:21.390> just<00:28:21.450> barely<00:28:21.930> doesn't<00:28:22.350> satisfy<00:28:22.530> the 00:28:22.850 --> 00:28:22.860 align:start position:0% sort of just barely doesn't satisfy the 00:28:22.860 --> 00:28:25.370 align:start position:0% sort of just barely doesn't satisfy the role<00:28:23.190> that<00:28:23.550> we<00:28:23.970> work<00:28:24.420> that<00:28:24.660> intuitively<00:28:25.170> it's 00:28:25.370 --> 00:28:25.380 align:start position:0% role that we work that intuitively it's 00:28:25.380 --> 00:28:28.160 align:start position:0% role that we work that intuitively it's supposed<00:28:25.650> to<00:28:25.740> yeah<00:28:26.780> something<00:28:27.780> also 00:28:28.160 --> 00:28:28.170 align:start position:0% supposed to yeah something also 00:28:28.170 --> 00:28:29.540 align:start position:0% supposed to yeah something also something<00:28:28.440> we<00:28:28.650> have<00:28:28.800> with<00:28:28.950> the<00:28:29.070> wallet<00:28:29.280> the 00:28:29.540 --> 00:28:29.550 align:start position:0% something we have with the wallet the 00:28:29.550 --> 00:28:31.180 align:start position:0% something we have with the wallet the wallet<00:28:29.700> currently<00:28:30.300> actually<00:28:30.780> uses 00:28:31.180 --> 00:28:31.190 align:start position:0% wallet currently actually uses 00:28:31.190 --> 00:28:34.180 align:start position:0% wallet currently actually uses subcontracts<00:28:32.190> so<00:28:32.520> it's<00:28:33.060> cheaper<00:28:33.390> to<00:28:33.570> deploy 00:28:34.180 --> 00:28:34.190 align:start position:0% subcontracts so it's cheaper to deploy 00:28:34.190 --> 00:28:37.850 align:start position:0% subcontracts so it's cheaper to deploy 120,000<00:28:35.190> gas<00:28:35.370> versus<00:28:35.850> 1.2<00:28:36.540> million<00:28:36.900> gas<00:28:37.110> so<00:28:37.680> we 00:28:37.850 --> 00:28:37.860 align:start position:0% 120,000 gas versus 1.2 million gas so we 00:28:37.860 --> 00:28:39.350 align:start position:0% 120,000 gas versus 1.2 million gas so we have<00:28:37.980> one<00:28:38.160> code<00:28:38.400> base<00:28:38.430> and<00:28:38.910> we<00:28:39.000> have<00:28:39.180> two 00:28:39.350 --> 00:28:39.360 align:start position:0% have one code base and we have two 00:28:39.360 --> 00:28:42.560 align:start position:0% have one code base and we have two subcontracts<00:28:40.200> they<00:28:40.620> use<00:28:40.830> core<00:28:41.130> code<00:28:41.370> and<00:28:41.670> the 00:28:42.560 --> 00:28:42.570 align:start position:0% subcontracts they use core code and the 00:28:42.570 --> 00:28:44.660 align:start position:0% subcontracts they use core code and the problem<00:28:42.900> is<00:28:43.020> inside<00:28:43.410> the<00:28:43.560> actual<00:28:43.800> wallet<00:28:44.460> it 00:28:44.660 --> 00:28:44.670 align:start position:0% problem is inside the actual wallet it 00:28:44.670 --> 00:28:48.110 align:start position:0% problem is inside the actual wallet it is<00:28:45.620> method<00:28:46.620> sender<00:28:47.070> is<00:28:47.190> actually<00:28:47.610> the<00:28:47.730> calling 00:28:48.110 --> 00:28:48.120 align:start position:0% is method sender is actually the calling 00:28:48.120 --> 00:28:49.790 align:start position:0% is method sender is actually the calling contract<00:28:48.600> and<00:28:48.780> not<00:28:48.930> the<00:28:49.080> one<00:28:49.290> who<00:28:49.620> actually 00:28:49.790 --> 00:28:49.800 align:start position:0% contract and not the one who actually 00:28:49.800 --> 00:28:52.600 align:start position:0% contract and not the one who actually initiated<00:28:50.490> it<00:28:50.760> or<00:28:51.030> the<00:28:51.210> one<00:28:51.360> proof<00:28:51.630> before<00:28:51.810> and 00:28:52.600 --> 00:28:52.610 align:start position:0% initiated it or the one proof before and 00:28:52.610 --> 00:28:54.920 align:start position:0% initiated it or the one proof before and this<00:28:53.610> basically<00:28:53.880> makes<00:28:54.240> call<00:28:54.540> code<00:28:54.750> not 00:28:54.920 --> 00:28:54.930 align:start position:0% this basically makes call code not 00:28:54.930 --> 00:28:57.500 align:start position:0% this basically makes call code not neutral<00:28:55.410> and<00:28:55.590> really<00:28:56.460> like<00:28:56.640> a<00:28:56.670> bit<00:28:57.060> destroys 00:28:57.500 --> 00:28:57.510 align:start position:0% neutral and really like a bit destroys 00:28:57.510 --> 00:28:59.480 align:start position:0% neutral and really like a bit destroys this<00:28:57.690> library<00:28:58.110> functionality<00:28:58.800> so<00:28:59.040> I<00:28:59.070> really 00:28:59.480 --> 00:28:59.490 align:start position:0% this library functionality so I really 00:28:59.490 --> 00:29:02.210 align:start position:0% this library functionality so I really would<00:28:59.640> love<00:28:59.880> to<00:29:00.120> see<00:29:00.300> change<00:29:00.630> here<00:29:00.990> um<00:29:01.410> so<00:29:02.040> one 00:29:02.210 --> 00:29:02.220 align:start position:0% would love to see change here um so one 00:29:02.220 --> 00:29:04.160 align:start position:0% would love to see change here um so one of<00:29:02.250> the<00:29:02.370> other<00:29:02.520> things<00:29:03.360> that's<00:29:03.600> currently<00:29:03.930> not 00:29:04.160 --> 00:29:04.170 align:start position:0% of the other things that's currently not 00:29:04.170 --> 00:29:05.810 align:start position:0% of the other things that's currently not possible<00:29:04.710> if<00:29:04.800> I<00:29:04.890> understand<00:29:05.310> correctly<00:29:05.340> is 00:29:05.810 --> 00:29:05.820 align:start position:0% possible if I understand correctly is 00:29:05.820 --> 00:29:08.510 align:start position:0% possible if I understand correctly is accessing<00:29:06.810> further<00:29:07.410> down<00:29:07.800> the<00:29:08.040> stack<00:29:08.280> of 00:29:08.510 --> 00:29:08.520 align:start position:0% accessing further down the stack of 00:29:08.520 --> 00:29:10.760 align:start position:0% accessing further down the stack of message<00:29:08.880> sender<00:29:09.210> is<00:29:09.930> that<00:29:10.200> an<00:29:10.380> option<00:29:10.560> for 00:29:10.760 --> 00:29:10.770 align:start position:0% message sender is that an option for 00:29:10.770 --> 00:29:12.920 align:start position:0% message sender is that an option for future<00:29:11.370> evm<00:29:11.760> upgrades<00:29:12.180> being<00:29:12.510> able<00:29:12.780> to 00:29:12.920 --> 00:29:12.930 align:start position:0% future evm upgrades being able to 00:29:12.930 --> 00:29:14.390 align:start position:0% future evm upgrades being able to actually<00:29:13.110> trace<00:29:13.530> your<00:29:13.680> way<00:29:13.830> all<00:29:14.010> the<00:29:14.130> way<00:29:14.160> back 00:29:14.390 --> 00:29:14.400 align:start position:0% actually trace your way all the way back 00:29:14.400 --> 00:29:18.020 align:start position:0% actually trace your way all the way back to<00:29:14.640> transaction<00:29:15.210> origin<00:29:16.160> yeah<00:29:17.160> it's<00:29:17.340> it's 00:29:18.020 --> 00:29:18.030 align:start position:0% to transaction origin yeah it's it's 00:29:18.030 --> 00:29:20.660 align:start position:0% to transaction origin yeah it's it's something<00:29:18.390> that<00:29:18.540> we're<00:29:18.660> looking<00:29:19.380> at<00:29:19.670> the 00:29:20.660 --> 00:29:20.670 align:start position:0% something that we're looking at the 00:29:20.670 --> 00:29:23.500 align:start position:0% something that we're looking at the argument<00:29:21.210> against<00:29:21.630> it<00:29:21.750> is<00:29:22.010> essentially 00:29:23.500 --> 00:29:23.510 align:start position:0% argument against it is essentially 00:29:23.510 --> 00:29:27.410 align:start position:0% argument against it is essentially isolation<00:29:24.510> there's<00:29:25.080> a<00:29:25.170> notion<00:29:25.380> that<00:29:25.740> you<00:29:26.550> know 00:29:27.410 --> 00:29:27.420 align:start position:0% isolation there's a notion that you know 00:29:27.420 --> 00:29:29.720 align:start position:0% isolation there's a notion that you know the<00:29:27.540> current<00:29:28.040> executing<00:29:29.040> frame<00:29:29.250> on<00:29:29.400> the<00:29:29.520> stack 00:29:29.720 --> 00:29:29.730 align:start position:0% the current executing frame on the stack 00:29:29.730 --> 00:29:33.470 align:start position:0% the current executing frame on the stack shouldn't<00:29:30.210> really<00:29:30.860> be<00:29:31.860> possibly<00:29:32.820> prejudiced 00:29:33.470 --> 00:29:33.480 align:start position:0% shouldn't really be possibly prejudiced 00:29:33.480 --> 00:29:35.690 align:start position:0% shouldn't really be possibly prejudiced by<00:29:33.720> previous<00:29:34.410> stack<00:29:34.800> frames<00:29:35.100> because<00:29:35.430> it 00:29:35.690 --> 00:29:35.700 align:start position:0% by previous stack frames because it 00:29:35.700 --> 00:29:38.720 align:start position:0% by previous stack frames because it breaks<00:29:35.880> the<00:29:36.540> notion<00:29:36.930> of<00:29:37.220> Irvine<00:29:38.220> capsulation 00:29:38.720 --> 00:29:38.730 align:start position:0% breaks the notion of Irvine capsulation 00:29:38.730 --> 00:29:41.300 align:start position:0% breaks the notion of Irvine capsulation shouldn't<00:29:39.630> transaction<00:29:40.170> origin<00:29:40.590> be<00:29:40.770> excluded 00:29:41.300 --> 00:29:41.310 align:start position:0% shouldn't transaction origin be excluded 00:29:41.310 --> 00:29:43.400 align:start position:0% shouldn't transaction origin be excluded and<00:29:41.400> in<00:29:41.550> principle<00:29:41.940> yes<00:29:42.300> but<00:29:42.900> there<00:29:43.230> is<00:29:43.380> a 00:29:43.400 --> 00:29:43.410 align:start position:0% and in principle yes but there is a 00:29:43.410 --> 00:29:44.960 align:start position:0% and in principle yes but there is a slight<00:29:43.800> difference<00:29:43.860> in<00:29:44.430> that<00:29:44.580> a<00:29:44.640> transaction 00:29:44.960 --> 00:29:44.970 align:start position:0% slight difference in that a transaction 00:29:44.970 --> 00:29:51.170 align:start position:0% slight difference in that a transaction is<00:29:45.450> different<00:29:45.810> to<00:29:45.900> a<00:29:45.930> message<00:29:46.200> so<00:29:50.180> other 00:29:51.170 --> 00:29:51.180 align:start position:0% is different to a message so other 00:29:51.180 --> 00:30:04.590 align:start position:0% is different to a message so other questions 00:30:04.590 --> 00:30:04.600 align:start position:0% 00:30:04.600 --> 00:30:09.930 align:start position:0% so<00:30:05.600> one<00:30:05.929> of<00:30:06.049> the<00:30:06.139> arguments<00:30:06.470> for<00:30:07.210> for<00:30:08.210> the 00:30:09.930 --> 00:30:09.940 align:start position:0% so one of the arguments for for the 00:30:09.940 --> 00:30:12.090 align:start position:0% so one of the arguments for for the registry<00:30:10.940> against<00:30:11.299> keeping<00:30:11.600> meta<00:30:11.899> data 00:30:12.090 --> 00:30:12.100 align:start position:0% registry against keeping meta data 00:30:12.100 --> 00:30:16.269 align:start position:0% registry against keeping meta data inside<00:30:13.100> contracts<00:30:13.850> is<00:30:13.990> really<00:30:14.990> how<00:30:15.619> does<00:30:16.070> the 00:30:16.269 --> 00:30:16.279 align:start position:0% inside contracts is really how does the 00:30:16.279 --> 00:30:19.720 align:start position:0% inside contracts is really how does the contract<00:30:16.879> we<00:30:17.269> will<00:30:17.450> register<00:30:18.049> itself<00:30:18.730> because 00:30:19.720 --> 00:30:19.730 align:start position:0% contract we will register itself because 00:30:19.730 --> 00:30:22.570 align:start position:0% contract we will register itself because either<00:30:20.029> we<00:30:20.570> have<00:30:20.779> to<00:30:21.019> register<00:30:21.409> on<00:30:21.830> the<00:30:21.860> contra 00:30:22.570 --> 00:30:22.580 align:start position:0% either we have to register on the contra 00:30:22.580 --> 00:30:24.460 align:start position:0% either we have to register on the contra when<00:30:22.909> the<00:30:23.029> contract<00:30:23.330> is<00:30:23.450> lunch<00:30:23.809> meaning<00:30:24.440> that 00:30:24.460 --> 00:30:24.470 align:start position:0% when the contract is lunch meaning that 00:30:24.470 --> 00:30:27.100 align:start position:0% when the contract is lunch meaning that if<00:30:24.980> you<00:30:25.429> have<00:30:25.700> a<00:30:25.730> register<00:30:26.240> that<00:30:26.389> exists<00:30:26.960> after 00:30:27.100 --> 00:30:27.110 align:start position:0% if you have a register that exists after 00:30:27.110 --> 00:30:29.019 align:start position:0% if you have a register that exists after the<00:30:27.590> Contra<00:30:27.830> has<00:30:28.129> launched<00:30:28.429> the<00:30:28.580> contract<00:30:28.909> can 00:30:29.019 --> 00:30:29.029 align:start position:0% the Contra has launched the contract can 00:30:29.029 --> 00:30:32.169 align:start position:0% the Contra has launched the contract can can't<00:30:29.659> register<00:30:29.869> itself<00:30:30.440> or<00:30:30.889> the<00:30:31.179> contract 00:30:32.169 --> 00:30:32.179 align:start position:0% can't register itself or the contract 00:30:32.179 --> 00:30:36.190 align:start position:0% can't register itself or the contract must<00:30:32.809> have<00:30:33.110> some<00:30:33.409> sort<00:30:33.769> of<00:30:34.009> way<00:30:34.369> to<00:30:35.330> pass<00:30:35.899> on 00:30:36.190 --> 00:30:36.200 align:start position:0% must have some sort of way to pass on 00:30:36.200 --> 00:30:38.950 align:start position:0% must have some sort of way to pass on arbitrary<00:30:37.129> messages<00:30:37.850> which<00:30:38.179> might<00:30:38.450> add<00:30:38.720> some 00:30:38.950 --> 00:30:38.960 align:start position:0% arbitrary messages which might add some 00:30:38.960 --> 00:30:41.049 align:start position:0% arbitrary messages which might add some complexity<00:30:39.740> that<00:30:39.919> something<00:30:40.369> like<00:30:40.490> a<00:30:40.549> token 00:30:41.049 --> 00:30:41.059 align:start position:0% complexity that something like a token 00:30:41.059 --> 00:30:43.509 align:start position:0% complexity that something like a token contract<00:30:41.570> minot<00:30:41.960> might<00:30:42.950> not<00:30:43.159> necessarily 00:30:43.509 --> 00:30:43.519 align:start position:0% contract minot might not necessarily 00:30:43.519 --> 00:30:46.239 align:start position:0% contract minot might not necessarily have<00:30:43.879> which<00:30:44.539> then<00:30:44.840> gives<00:30:45.440> you<00:30:45.679> have<00:30:46.070> the 00:30:46.239 --> 00:30:46.249 align:start position:0% have which then gives you have the 00:30:46.249 --> 00:30:48.879 align:start position:0% have which then gives you have the problem<00:30:46.639> of<00:30:46.820> who<00:30:47.480> has<00:30:47.840> the<00:30:48.049> right<00:30:48.320> to<00:30:48.679> pass 00:30:48.879 --> 00:30:48.889 align:start position:0% problem of who has the right to pass 00:30:48.889 --> 00:30:52.029 align:start position:0% problem of who has the right to pass arbitrary<00:30:49.519> messages<00:30:50.090> so<00:30:50.299> if<00:30:51.289> at<00:30:51.499> all<00:30:51.649> if<00:30:51.919> a 00:30:52.029 --> 00:30:52.039 align:start position:0% arbitrary messages so if at all if a 00:30:52.039 --> 00:30:54.430 align:start position:0% arbitrary messages so if at all if a token<00:30:52.490> I<00:30:52.789> mean<00:30:53.179> how<00:30:53.600> would<00:30:53.659> the<00:30:54.019> token 00:30:54.430 --> 00:30:54.440 align:start position:0% token I mean how would the token 00:30:54.440 --> 00:30:56.619 align:start position:0% token I mean how would the token register<00:30:54.980> itself<00:30:55.369> and<00:30:55.639> who<00:30:55.789> do<00:30:55.940> who<00:30:56.240> would 00:30:56.619 --> 00:30:56.629 align:start position:0% register itself and who do who would 00:30:56.629 --> 00:30:59.200 align:start position:0% register itself and who do who would have<00:30:56.960> would<00:30:57.710> be<00:30:57.740> owner<00:30:58.190> of<00:30:58.490> the<00:30:58.639> token<00:30:58.999> if<00:30:59.090> the 00:30:59.200 --> 00:30:59.210 align:start position:0% have would be owner of the token if the 00:30:59.210 --> 00:31:02.769 align:start position:0% have would be owner of the token if the token<00:30:59.509> has<00:30:59.659> no<00:30:59.809> owners<00:31:01.090> two<00:31:02.090> major<00:31:02.360> categories 00:31:02.769 --> 00:31:02.779 align:start position:0% token has no owners two major categories 00:31:02.779 --> 00:31:05.619 align:start position:0% token has no owners two major categories of<00:31:03.200> solution<00:31:03.740> of<00:31:03.919> ways<00:31:04.789> of<00:31:04.970> solving<00:31:05.210> this<00:31:05.480> I 00:31:05.619 --> 00:31:05.629 align:start position:0% of solution of ways of solving this I 00:31:05.629 --> 00:31:08.230 align:start position:0% of solution of ways of solving this I think<00:31:05.830> one<00:31:06.830> of<00:31:06.860> them<00:31:07.129> basically<00:31:07.519> is<00:31:07.820> to<00:31:08.029> say 00:31:08.230 --> 00:31:08.240 align:start position:0% think one of them basically is to say 00:31:08.240 --> 00:31:10.919 align:start position:0% think one of them basically is to say that<00:31:08.269> you<00:31:08.720> know<00:31:08.749> currency<00:31:09.679> is<00:31:09.740> just<00:31:10.159> earth 00:31:10.919 --> 00:31:10.929 align:start position:0% that you know currency is just earth 00:31:10.929 --> 00:31:13.960 align:start position:0% that you know currency is just earth tokens<00:31:11.929> have<00:31:12.289> to<00:31:12.559> build<00:31:12.889> in<00:31:13.039> some<00:31:13.369> mechanism 00:31:13.960 --> 00:31:13.970 align:start position:0% tokens have to build in some mechanism 00:31:13.970 --> 00:31:15.580 align:start position:0% tokens have to build in some mechanism it<00:31:14.090> doesn't<00:31:14.389> have<00:31:14.480> to<00:31:14.629> be<00:31:14.659> standardized<00:31:15.289> you 00:31:15.580 --> 00:31:15.590 align:start position:0% it doesn't have to be standardized you 00:31:15.590 --> 00:31:17.889 align:start position:0% it doesn't have to be standardized you know<00:31:15.710> in<00:31:16.249> order<00:31:16.429> to<00:31:16.580> allow<00:31:17.059> some<00:31:17.389> particular 00:31:17.889 --> 00:31:17.899 align:start position:0% know in order to allow some particular 00:31:17.899 --> 00:31:19.239 align:start position:0% know in order to allow some particular administrator<00:31:18.470> to<00:31:18.769> keep<00:31:19.070> on<00:31:19.220> updating 00:31:19.239 --> 00:31:19.249 align:start position:0% administrator to keep on updating 00:31:19.249 --> 00:31:23.049 align:start position:0% administrator to keep on updating registry<00:31:20.090> data<00:31:20.330> if<00:31:20.509> they<00:31:20.659> have<00:31:20.840> to<00:31:21.049> and<00:31:21.700> or<00:31:22.700> you 00:31:23.049 --> 00:31:23.059 align:start position:0% registry data if they have to and or you 00:31:23.059 --> 00:31:24.430 align:start position:0% registry data if they have to and or you know<00:31:23.179> all<00:31:23.330> alternatively<00:31:23.960> you<00:31:24.080> could<00:31:24.230> just 00:31:24.430 --> 00:31:24.440 align:start position:0% know all alternatively you could just 00:31:24.440 --> 00:31:29.350 align:start position:0% know all alternatively you could just say<00:31:24.619> that<00:31:24.919> the<00:31:25.869> the<00:31:27.070> token<00:31:28.070> just<00:31:28.279> calls<00:31:28.549> the 00:31:29.350 --> 00:31:29.360 align:start position:0% say that the the token just calls the 00:31:29.360 --> 00:31:31.330 align:start position:0% say that the the token just calls the method<00:31:30.049> once<00:31:30.320> an<00:31:30.499> insignia<00:31:30.830> code<00:31:31.070> and<00:31:31.249> it 00:31:31.330 --> 00:31:31.340 align:start position:0% method once an insignia code and it 00:31:31.340 --> 00:31:33.609 align:start position:0% method once an insignia code and it never<00:31:31.460> does<00:31:31.669> it<00:31:31.730> again<00:31:32.019> the<00:31:33.019> other<00:31:33.320> approach 00:31:33.609 --> 00:31:33.619 align:start position:0% never does it again the other approach 00:31:33.619 --> 00:31:35.889 align:start position:0% never does it again the other approach is<00:31:34.159> this<00:31:34.460> proxy<00:31:34.879> contract<00:31:35.330> route<00:31:35.600> which 00:31:35.889 --> 00:31:35.899 align:start position:0% is this proxy contract route which 00:31:35.899 --> 00:31:38.560 align:start position:0% is this proxy contract route which basically<00:31:36.320> means<00:31:37.070> that<00:31:37.340> you<00:31:38.090> know<00:31:38.210> you<00:31:38.299> start 00:31:38.560 --> 00:31:38.570 align:start position:0% basically means that you know you start 00:31:38.570 --> 00:31:40.239 align:start position:0% basically means that you know you start off<00:31:38.720> by<00:31:38.960> just<00:31:39.019> having<00:31:39.350> the<00:31:39.619> token<00:31:39.980> follow 00:31:40.239 --> 00:31:40.249 align:start position:0% off by just having the token follow 00:31:40.249 --> 00:31:42.279 align:start position:0% off by just having the token follow whatever<00:31:40.580> the<00:31:40.909> API<00:31:41.269> was<00:31:41.570> at<00:31:41.720> the<00:31:41.840> time<00:31:42.080> and 00:31:42.279 --> 00:31:42.289 align:start position:0% whatever the API was at the time and 00:31:42.289 --> 00:31:44.859 align:start position:0% whatever the API was at the time and then<00:31:42.860> if<00:31:43.190> a<00:31:43.399> new<00:31:43.610> standard<00:31:43.999> comes<00:31:44.269> along<00:31:44.600> or 00:31:44.859 --> 00:31:44.869 align:start position:0% then if a new standard comes along or 00:31:44.869 --> 00:31:46.269 align:start position:0% then if a new standard comes along or you<00:31:45.110> know<00:31:45.230> if<00:31:45.409> he<00:31:45.559> wants<00:31:45.830> to<00:31:45.860> update<00:31:46.039> the 00:31:46.269 --> 00:31:46.279 align:start position:0% you know if he wants to update the 00:31:46.279 --> 00:31:48.129 align:start position:0% you know if he wants to update the registry<00:31:46.669> information<00:31:46.940> then<00:31:47.840> the<00:31:47.960> way<00:31:48.080> you 00:31:48.129 --> 00:31:48.139 align:start position:0% registry information then the way you 00:31:48.139 --> 00:31:50.440 align:start position:0% registry information then the way you would<00:31:48.529> do<00:31:48.710> that<00:31:48.740> is<00:31:49.129> by<00:31:49.369> creating<00:31:49.700> a<00:31:49.970> new<00:31:50.149> token 00:31:50.440 --> 00:31:50.450 align:start position:0% would do that is by creating a new token 00:31:50.450 --> 00:31:52.840 align:start position:0% would do that is by creating a new token which<00:31:50.840> is<00:31:50.990> really<00:31:51.559> just<00:31:51.679> a<00:31:51.980> proxy<00:31:52.460> pointing 00:31:52.840 --> 00:31:52.850 align:start position:0% which is really just a proxy pointing 00:31:52.850 --> 00:31:55.359 align:start position:0% which is really just a proxy pointing back<00:31:53.059> to<00:31:53.240> the<00:31:53.330> first<00:31:53.539> token<00:31:53.779> and<00:31:54.169> then<00:31:54.830> all 00:31:55.359 --> 00:31:55.369 align:start position:0% back to the first token and then all 00:31:55.369 --> 00:31:57.340 align:start position:0% back to the first token and then all that<00:31:55.789> that<00:31:55.879> new<00:31:56.059> token<00:31:56.389> is<00:31:56.600> is<00:31:56.749> basically<00:31:56.990> the 00:31:57.340 --> 00:31:57.350 align:start position:0% that that new token is is basically the 00:31:57.350 --> 00:31:59.409 align:start position:0% that that new token is is basically the same<00:31:57.499> thing<00:31:57.559> as<00:31:58.039> the<00:31:58.159> original<00:31:58.580> one<00:31:58.789> except<00:31:59.269> it 00:31:59.409 --> 00:31:59.419 align:start position:0% same thing as the original one except it 00:31:59.419 --> 00:32:00.700 align:start position:0% same thing as the original one except it has<00:31:59.539> a<00:31:59.570> different<00:31:59.960> interface<00:32:00.169> and<00:32:00.529> maybe 00:32:00.700 --> 00:32:00.710 align:start position:0% has a different interface and maybe 00:32:00.710 --> 00:32:03.850 align:start position:0% has a different interface and maybe different<00:32:01.070> registry<00:32:01.460> data<00:32:01.669> to<00:32:01.879> it<00:32:02.059> so<00:32:02.990> that's 00:32:03.850 --> 00:32:03.860 align:start position:0% different registry data to it so that's 00:32:03.860 --> 00:32:06.009 align:start position:0% different registry data to it so that's like<00:32:04.279> one<00:32:04.639> potential<00:32:05.539> way<00:32:05.570> of<00:32:05.690> making<00:32:05.990> things 00:32:06.009 --> 00:32:06.019 align:start position:0% like one potential way of making things 00:32:06.019 --> 00:32:08.580 align:start position:0% like one potential way of making things more<00:32:06.320> modular 00:32:08.580 --> 00:32:08.590 align:start position:0% 00:32:08.590 --> 00:32:10.409 align:start position:0% it's<00:32:08.950> gonna<00:32:09.070> say<00:32:09.220> like<00:32:09.370> if<00:32:09.580> you<00:32:09.700> if<00:32:10.000> you<00:32:10.210> don't 00:32:10.409 --> 00:32:10.419 align:start position:0% it's gonna say like if you if you don't 00:32:10.419 --> 00:32:12.149 align:start position:0% it's gonna say like if you if you don't know<00:32:10.600> it<00:32:10.720> had<00:32:10.840> a<00:32:10.870> basic<00:32:11.860> there's<00:32:12.070> two 00:32:12.149 --> 00:32:12.159 align:start position:0% know it had a basic there's two 00:32:12.159 --> 00:32:13.860 align:start position:0% know it had a basic there's two categories<00:32:12.610> there's<00:32:12.789> like<00:32:12.909> immutable 00:32:13.860 --> 00:32:13.870 align:start position:0% categories there's like immutable 00:32:13.870 --> 00:32:15.419 align:start position:0% categories there's like immutable contracts<00:32:14.470> which<00:32:14.590> basically<00:32:14.799> know<00:32:15.010> exactly 00:32:15.419 --> 00:32:15.429 align:start position:0% contracts which basically know exactly 00:32:15.429 --> 00:32:16.409 align:start position:0% contracts which basically know exactly what<00:32:15.610> they're<00:32:15.700> supposed<00:32:16.000> to<00:32:16.059> do<00:32:16.210> ahead<00:32:16.299> of 00:32:16.409 --> 00:32:16.419 align:start position:0% what they're supposed to do ahead of 00:32:16.419 --> 00:32:17.880 align:start position:0% what they're supposed to do ahead of time<00:32:16.539> you<00:32:16.659> write<00:32:17.080> the<00:32:17.200> code<00:32:17.409> and<00:32:17.590> there's<00:32:17.710> no 00:32:17.880 --> 00:32:17.890 align:start position:0% time you write the code and there's no 00:32:17.890 --> 00:32:19.860 align:start position:0% time you write the code and there's no back<00:32:18.070> doors<00:32:18.340> or<00:32:18.520> anything<00:32:18.820> but<00:32:19.299> then<00:32:19.480> like<00:32:19.659> if 00:32:19.860 --> 00:32:19.870 align:start position:0% back doors or anything but then like if 00:32:19.870 --> 00:32:22.860 align:start position:0% back doors or anything but then like if you<00:32:19.990> have<00:32:20.350> even<00:32:20.620> one<00:32:21.360> use<00:32:22.360> case<00:32:22.600> where<00:32:22.809> you 00:32:22.860 --> 00:32:22.870 align:start position:0% you have even one use case where you 00:32:22.870 --> 00:32:25.470 align:start position:0% you have even one use case where you might<00:32:23.110> need<00:32:23.260> to<00:32:23.500> do<00:32:23.679> a<00:32:23.710> proxy<00:32:24.190> call<00:32:24.429> then<00:32:25.210> your 00:32:25.470 --> 00:32:25.480 align:start position:0% might need to do a proxy call then your 00:32:25.480 --> 00:32:27.690 align:start position:0% might need to do a proxy call then your contract<00:32:25.960> becomes<00:32:26.380> you<00:32:26.830> know<00:32:26.860> you<00:32:26.980> don't<00:32:27.250> it 00:32:27.690 --> 00:32:27.700 align:start position:0% contract becomes you know you don't it 00:32:27.700 --> 00:32:29.460 align:start position:0% contract becomes you know you don't it could<00:32:27.820> do<00:32:28.029> anything<00:32:28.270> and<00:32:28.539> so<00:32:28.690> then<00:32:28.870> it<00:32:29.049> needs<00:32:29.289> a 00:32:29.460 --> 00:32:29.470 align:start position:0% could do anything and so then it needs a 00:32:29.470 --> 00:32:32.490 align:start position:0% could do anything and so then it needs a got<00:32:29.620> a<00:32:30.309> governance<00:32:30.940> model<00:32:31.240> basically<00:32:31.510> so<00:32:32.320> the 00:32:32.490 --> 00:32:32.500 align:start position:0% got a governance model basically so the 00:32:32.500 --> 00:32:34.049 align:start position:0% got a governance model basically so the answer<00:32:32.529> to<00:32:32.740> that<00:32:32.860> is<00:32:33.010> like<00:32:33.279> if<00:32:33.460> your<00:32:33.730> if<00:32:34.029> your 00:32:34.049 --> 00:32:34.059 align:start position:0% answer to that is like if your if your 00:32:34.059 --> 00:32:36.450 align:start position:0% answer to that is like if your if your contract<00:32:34.840> is<00:32:34.990> doing<00:32:35.620> arbitrary<00:32:36.039> behaviors 00:32:36.450 --> 00:32:36.460 align:start position:0% contract is doing arbitrary behaviors 00:32:36.460 --> 00:32:38.700 align:start position:0% contract is doing arbitrary behaviors then<00:32:36.730> yes<00:32:36.970> like<00:32:37.390> it<00:32:37.690> you<00:32:38.110> need<00:32:38.260> a<00:32:38.289> governance 00:32:38.700 --> 00:32:38.710 align:start position:0% then yes like it you need a governance 00:32:38.710 --> 00:32:40.049 align:start position:0% then yes like it you need a governance thing<00:32:38.980> and<00:32:39.100> that's<00:32:39.220> a<00:32:39.340> separate<00:32:39.789> problem 00:32:40.049 --> 00:32:40.059 align:start position:0% thing and that's a separate problem 00:32:40.059 --> 00:32:44.700 align:start position:0% thing and that's a separate problem altogether<00:32:41.640> yeah<00:32:42.640> the<00:32:42.789> only<00:32:42.880> thing<00:32:43.000> I<00:32:43.240> that<00:32:43.710> if 00:32:44.700 --> 00:32:44.710 align:start position:0% altogether yeah the only thing I that if 00:32:44.710 --> 00:32:48.240 align:start position:0% altogether yeah the only thing I that if if<00:32:45.490> the<00:32:45.909> notion<00:32:46.840> that<00:32:47.010> actually<00:32:48.010> we're<00:32:48.130> going 00:32:48.240 --> 00:32:48.250 align:start position:0% if the notion that actually we're going 00:32:48.250 --> 00:32:49.740 align:start position:0% if the notion that actually we're going to<00:32:48.309> say<00:32:48.549> all<00:32:48.730> tokens<00:32:49.059> could<00:32:49.539> in<00:32:49.630> principle 00:32:49.740 --> 00:32:49.750 align:start position:0% to say all tokens could in principle 00:32:49.750 --> 00:32:52.769 align:start position:0% to say all tokens could in principle become<00:32:50.350> proxy<00:32:50.770> have<00:32:51.370> proxy<00:32:51.820> sort<00:32:52.360> of<00:32:52.450> facades 00:32:52.769 --> 00:32:52.779 align:start position:0% become proxy have proxy sort of facades 00:32:52.779 --> 00:32:54.810 align:start position:0% become proxy have proxy sort of facades in<00:32:53.080> front<00:32:53.289> of<00:32:53.409> them<00:32:53.500> and<00:32:53.649> this<00:32:54.159> can<00:32:54.370> be<00:32:54.490> added 00:32:54.810 --> 00:32:54.820 align:start position:0% in front of them and this can be added 00:32:54.820 --> 00:32:57.380 align:start position:0% in front of them and this can be added for<00:32:55.090> all<00:32:55.419> possible<00:32:55.870> all<00:32:56.350> eventual 00:32:57.380 --> 00:32:57.390 align:start position:0% for all possible all eventual 00:32:57.390 --> 00:32:59.940 align:start position:0% for all possible all eventual improvements<00:32:58.390> to<00:32:58.510> registries<00:32:59.020> then<00:32:59.649> we've 00:32:59.940 --> 00:32:59.950 align:start position:0% improvements to registries then we've 00:32:59.950 --> 00:33:02.279 align:start position:0% improvements to registries then we've got<00:32:59.980> like<00:33:00.370> this<00:33:00.700> order<00:33:01.270> n-squared<00:33:01.570> issue 00:33:02.279 --> 00:33:02.289 align:start position:0% got like this order n-squared issue 00:33:02.289 --> 00:33:05.789 align:start position:0% got like this order n-squared issue where<00:33:02.710> you're<00:33:03.549> forcing<00:33:03.850> all<00:33:04.149> tokens<00:33:04.809> to 00:33:05.789 --> 00:33:05.799 align:start position:0% where you're forcing all tokens to 00:33:05.799 --> 00:33:09.029 align:start position:0% where you're forcing all tokens to support<00:33:06.370> all<00:33:06.610> registries<00:33:07.299> whereas<00:33:08.230> so<00:33:08.890> you're 00:33:09.029 --> 00:33:09.039 align:start position:0% support all registries whereas so you're 00:33:09.039 --> 00:33:10.169 align:start position:0% support all registries whereas so you're going<00:33:09.130> to<00:33:09.220> end<00:33:09.340> up<00:33:09.429> with<00:33:09.490> like<00:33:09.669> N<00:33:09.789> squared 00:33:10.169 --> 00:33:10.179 align:start position:0% going to end up with like N squared 00:33:10.179 --> 00:33:13.730 align:start position:0% going to end up with like N squared facades<00:33:10.510> right<00:33:11.429> whereas<00:33:12.429> if<00:33:12.669> we<00:33:13.000> go<00:33:13.179> for<00:33:13.510> the 00:33:13.730 --> 00:33:13.740 align:start position:0% facades right whereas if we go for the 00:33:13.740 --> 00:33:15.899 align:start position:0% facades right whereas if we go for the the<00:33:14.740> route<00:33:14.950> of<00:33:15.070> saying<00:33:15.340> right<00:33:15.610> well<00:33:15.760> actually 00:33:15.899 --> 00:33:15.909 align:start position:0% the route of saying right well actually 00:33:15.909 --> 00:33:17.940 align:start position:0% the route of saying right well actually tokens<00:33:16.570> maybe<00:33:16.960> there<00:33:17.230> maybe<00:33:17.440> it's<00:33:17.649> the<00:33:17.799> case 00:33:17.940 --> 00:33:17.950 align:start position:0% tokens maybe there maybe it's the case 00:33:17.950 --> 00:33:20.850 align:start position:0% tokens maybe there maybe it's the case that<00:33:17.980> they<00:33:18.250> elect<00:33:18.700> to<00:33:19.000> a<00:33:19.029> registrar<00:33:19.860> some 00:33:20.850 --> 00:33:20.860 align:start position:0% that they elect to a registrar some 00:33:20.860 --> 00:33:22.680 align:start position:0% that they elect to a registrar some third-party<00:33:21.159> address<00:33:21.850> and<00:33:22.120> say<00:33:22.510> actually 00:33:22.680 --> 00:33:22.690 align:start position:0% third-party address and say actually 00:33:22.690 --> 00:33:24.269 align:start position:0% third-party address and say actually this<00:33:23.289> we're<00:33:23.649> not<00:33:23.770> going<00:33:23.950> to<00:33:24.010> execute 00:33:24.269 --> 00:33:24.279 align:start position:0% this we're not going to execute 00:33:24.279 --> 00:33:26.610 align:start position:0% this we're not going to execute arbitrary<00:33:24.640> transactions<00:33:25.480> in<00:33:25.779> the<00:33:26.080> future<00:33:26.409> but 00:33:26.610 --> 00:33:26.620 align:start position:0% arbitrary transactions in the future but 00:33:26.620 --> 00:33:29.519 align:start position:0% arbitrary transactions in the future but this<00:33:27.159> guy<00:33:27.370> can<00:33:27.730> actually<00:33:28.120> update<00:33:28.600> metadata<00:33:29.260> on 00:33:29.519 --> 00:33:29.529 align:start position:0% this guy can actually update metadata on 00:33:29.529 --> 00:33:32.220 align:start position:0% this guy can actually update metadata on our<00:33:29.740> behalf<00:33:30.010> which<00:33:30.760> massively<00:33:31.360> reduces<00:33:32.080> the 00:33:32.220 --> 00:33:32.230 align:start position:0% our behalf which massively reduces the 00:33:32.230 --> 00:33:34.830 align:start position:0% our behalf which massively reduces the attack<00:33:32.500> surface<00:33:32.740> and<00:33:33.330> it<00:33:34.330> could<00:33:34.600> in<00:33:34.690> principle 00:33:34.830 --> 00:33:34.840 align:start position:0% attack surface and it could in principle 00:33:34.840 --> 00:33:37.230 align:start position:0% attack surface and it could in principle be<00:33:35.200> like<00:33:35.380> a<00:33:35.409> multi-party<00:33:36.130> a<00:33:36.370> multi<00:33:36.820> sig<00:33:37.029> sort 00:33:37.230 --> 00:33:37.240 align:start position:0% be like a multi-party a multi sig sort 00:33:37.240 --> 00:33:38.820 align:start position:0% be like a multi-party a multi sig sort of<00:33:37.330> contract<00:33:37.630> multi-party<00:33:38.350> sort<00:33:38.559> of<00:33:38.649> stay 00:33:38.820 --> 00:33:38.830 align:start position:0% of contract multi-party sort of stay 00:33:38.830 --> 00:33:40.680 align:start position:0% of contract multi-party sort of stay call<00:33:39.039> the<00:33:39.159> thing<00:33:39.340> where<00:33:39.640> multiple<00:33:40.419> people 00:33:40.680 --> 00:33:40.690 align:start position:0% call the thing where multiple people 00:33:40.690 --> 00:33:42.750 align:start position:0% call the thing where multiple people actually<00:33:40.990> have<00:33:41.020> to<00:33:41.350> agree<00:33:41.799> that<00:33:41.950> yes<00:33:42.340> this<00:33:42.549> is 00:33:42.750 --> 00:33:42.760 align:start position:0% actually have to agree that yes this is 00:33:42.760 --> 00:33:44.669 align:start position:0% actually have to agree that yes this is this<00:33:43.390> isn't<00:33:43.690> just<00:33:43.899> you<00:33:44.110> know<00:33:44.230> some<00:33:44.470> dodgy 00:33:44.669 --> 00:33:44.679 align:start position:0% this isn't just you know some dodgy 00:33:44.679 --> 00:33:46.409 align:start position:0% this isn't just you know some dodgy troll<00:33:45.070> trying<00:33:45.399> to<00:33:45.520> change<00:33:46.000> your<00:33:46.210> name<00:33:46.390> to 00:33:46.409 --> 00:33:46.419 align:start position:0% troll trying to change your name to 00:33:46.419 --> 00:33:49.799 align:start position:0% troll trying to change your name to something<00:33:47.130> something<00:33:48.330> silly<00:33:49.330> it's<00:33:49.539> it's 00:33:49.799 --> 00:33:49.809 align:start position:0% something something silly it's it's 00:33:49.809 --> 00:33:52.380 align:start position:0% something something silly it's it's actually<00:33:50.200> a<00:33:50.230> reasonable<00:33:50.919> and<00:33:51.580> metadata 00:33:52.380 --> 00:33:52.390 align:start position:0% actually a reasonable and metadata 00:33:52.390 --> 00:34:04.539 align:start position:0% actually a reasonable and metadata upgrade<00:33:54.090> thank<00:33:55.090> you<00:33:55.179> any<00:33:55.330> more<00:33:55.450> questions 00:34:04.539 --> 00:34:04.549 align:start position:0% 00:34:04.549 --> 00:34:07.820 align:start position:0% so<00:34:05.549> how<00:34:06.090> much<00:34:06.240> do<00:34:06.830> standardization 00:34:07.820 --> 00:34:07.830 align:start position:0% so how much do standardization 00:34:07.830 --> 00:34:10.129 align:start position:0% so how much do standardization conversations<00:34:08.760> today<00:34:09.000> or<00:34:09.659> how<00:34:09.750> much<00:34:09.899> should 00:34:10.129 --> 00:34:10.139 align:start position:0% conversations today or how much should 00:34:10.139 --> 00:34:11.960 align:start position:0% conversations today or how much should they<00:34:10.260> be<00:34:10.379> influenced<00:34:10.950> by<00:34:11.100> scalability 00:34:11.960 --> 00:34:11.970 align:start position:0% they be influenced by scalability 00:34:11.970 --> 00:34:13.639 align:start position:0% they be influenced by scalability conversations<00:34:12.629> tomorrow<00:34:12.840> so<00:34:13.320> with<00:34:13.500> respect 00:34:13.639 --> 00:34:13.649 align:start position:0% conversations tomorrow so with respect 00:34:13.649 --> 00:34:16.129 align:start position:0% conversations tomorrow so with respect to<00:34:13.950> charting<00:34:14.369> if<00:34:14.970> we<00:34:15.149> take<00:34:15.629> some<00:34:15.810> approaches 00:34:16.129 --> 00:34:16.139 align:start position:0% to charting if we take some approaches 00:34:16.139 --> 00:34:18.560 align:start position:0% to charting if we take some approaches to<00:34:16.470> standardization<00:34:17.070> that<00:34:18.000> may<00:34:18.240> not<00:34:18.389> make 00:34:18.560 --> 00:34:18.570 align:start position:0% to standardization that may not make 00:34:18.570 --> 00:34:21.889 align:start position:0% to standardization that may not make sense<00:34:18.629> in<00:34:19.169> a<00:34:19.260> sharted<00:34:19.619> future<00:34:20.570> just<00:34:21.570> wondering 00:34:21.889 --> 00:34:21.899 align:start position:0% sense in a sharted future just wondering 00:34:21.899 --> 00:34:25.700 align:start position:0% sense in a sharted future just wondering that<00:34:23.540> that's<00:34:24.540> actually<00:34:24.750> good<00:34:25.050> questions<00:34:25.500> all 00:34:25.700 --> 00:34:25.710 align:start position:0% that that's actually good questions all 00:34:25.710 --> 00:34:27.560 align:start position:0% that that's actually good questions all like<00:34:26.250> if<00:34:26.490> you<00:34:26.580> have<00:34:26.669> to<00:34:26.790> register<00:34:26.940> you<00:34:27.270> have<00:34:27.450> to 00:34:27.560 --> 00:34:27.570 align:start position:0% like if you have to register you have to 00:34:27.570 --> 00:34:30.109 align:start position:0% like if you have to register you have to token<00:34:27.929> and<00:34:28.080> we<00:34:28.169> day<00:34:28.350> it<00:34:28.619> will<00:34:28.710> take<00:34:28.980> the<00:34:29.159> like 00:34:30.109 --> 00:34:30.119 align:start position:0% token and we day it will take the like 00:34:30.119 --> 00:34:32.149 align:start position:0% token and we day it will take the like the<00:34:30.270> basic<00:34:30.690> like<00:34:30.929> metadata<00:34:31.470> off<00:34:31.679> to<00:34:31.800> talk<00:34:31.980> now 00:34:32.149 --> 00:34:32.159 align:start position:0% the basic like metadata off to talk now 00:34:32.159 --> 00:34:34.520 align:start position:0% the basic like metadata off to talk now out<00:34:32.250> of<00:34:32.280> the<00:34:32.490> contract<00:34:32.760> to<00:34:32.970> a<00:34:33.320> registry<00:34:34.320> and 00:34:34.520 --> 00:34:34.530 align:start position:0% out of the contract to a registry and 00:34:34.530 --> 00:34:36.980 align:start position:0% out of the contract to a registry and down<00:34:34.740> in<00:34:34.919> different<00:34:35.190> charts<00:34:35.669> would<00:34:36.450> get<00:34:36.750> more 00:34:36.980 --> 00:34:36.990 align:start position:0% down in different charts would get more 00:34:36.990 --> 00:34:45.129 align:start position:0% down in different charts would get more complicated<00:34:39.200> yeah<00:34:40.200> I<00:34:40.230> mean<00:34:40.409> I<00:34:42.109> guess<00:34:43.399> today 00:34:45.129 --> 00:34:45.139 align:start position:0% complicated yeah I mean I guess today 00:34:45.139 --> 00:34:47.300 align:start position:0% complicated yeah I mean I guess today exactly<00:34:46.139> how<00:34:46.230> the<00:34:46.290> shouting<00:34:46.740> is<00:34:46.859> going<00:34:47.250> to 00:34:47.300 --> 00:34:47.310 align:start position:0% exactly how the shouting is going to 00:34:47.310 --> 00:34:48.950 align:start position:0% exactly how the shouting is going to work<00:34:47.460> exactly<00:34:47.820> how<00:34:48.030> sort<00:34:48.240> of<00:34:48.330> scalability<00:34:48.720> and 00:34:48.950 --> 00:34:48.960 align:start position:0% work exactly how sort of scalability and 00:34:48.960 --> 00:34:50.930 align:start position:0% work exactly how sort of scalability and 2.0<00:34:49.649> is<00:34:49.740> going<00:34:49.889> to<00:34:49.950> work<00:34:50.070> is<00:34:50.280> still<00:34:50.460> very<00:34:50.730> much 00:34:50.930 --> 00:34:50.940 align:start position:0% 2.0 is going to work is still very much 00:34:50.940 --> 00:34:53.330 align:start position:0% 2.0 is going to work is still very much a<00:34:51.000> question<00:34:51.419> of<00:34:51.659> research<00:34:51.990> we've<00:34:52.830> yet<00:34:53.010> to<00:34:53.070> do 00:34:53.330 --> 00:34:53.340 align:start position:0% a question of research we've yet to do 00:34:53.340 --> 00:34:56.570 align:start position:0% a question of research we've yet to do any<00:34:53.609> real<00:34:53.850> modeling<00:34:54.300> on<00:34:54.480> on<00:34:55.020> the<00:34:55.200> on<00:34:55.740> the<00:34:56.159> ideas 00:34:56.570 --> 00:34:56.580 align:start position:0% any real modeling on on the on the ideas 00:34:56.580 --> 00:34:57.920 align:start position:0% any real modeling on on the on the ideas that<00:34:56.609> we<00:34:56.850> have<00:34:57.060> and<00:34:57.240> then<00:34:57.330> of<00:34:57.480> course<00:34:57.690> there's 00:34:57.920 --> 00:34:57.930 align:start position:0% that we have and then of course there's 00:34:57.930 --> 00:35:00.320 align:start position:0% that we have and then of course there's still<00:34:58.369> feasibility<00:34:59.369> and<00:34:59.520> implementation<00:35:00.210> all 00:35:00.320 --> 00:35:00.330 align:start position:0% still feasibility and implementation all 00:35:00.330 --> 00:35:01.970 align:start position:0% still feasibility and implementation all the<00:35:00.420> rest<00:35:00.570> of<00:35:00.720> it<00:35:00.810> so<00:35:01.020> I<00:35:01.200> think<00:35:01.530> it's<00:35:01.770> still<00:35:01.830> a 00:35:01.970 --> 00:35:01.980 align:start position:0% the rest of it so I think it's still a 00:35:01.980 --> 00:35:03.980 align:start position:0% the rest of it so I think it's still a relatively<00:35:02.430> long<00:35:02.640> way<00:35:02.820> off<00:35:02.970> and<00:35:03.240> we<00:35:03.630> probably 00:35:03.980 --> 00:35:03.990 align:start position:0% relatively long way off and we probably 00:35:03.990 --> 00:35:05.720 align:start position:0% relatively long way off and we probably should<00:35:04.380> be<00:35:04.470> focusing<00:35:04.920> on<00:35:05.070> real<00:35:05.250> use<00:35:05.490> cases 00:35:05.720 --> 00:35:05.730 align:start position:0% should be focusing on real use cases 00:35:05.730 --> 00:35:08.359 align:start position:0% should be focusing on real use cases today<00:35:06.030> rather<00:35:06.480> than<00:35:06.630> put<00:35:07.380> you<00:35:07.590> know<00:35:07.710> presuming 00:35:08.359 --> 00:35:08.369 align:start position:0% today rather than put you know presuming 00:35:08.369 --> 00:35:10.370 align:start position:0% today rather than put you know presuming potential<00:35:09.240> architecture<00:35:09.840> decisions<00:35:10.260> that 00:35:10.370 --> 00:35:10.380 align:start position:0% potential architecture decisions that 00:35:10.380 --> 00:35:11.930 align:start position:0% potential architecture decisions that were<00:35:10.470> going<00:35:10.590> to<00:35:10.650> take<00:35:10.800> it<00:35:11.040> maybe<00:35:11.220> 12<00:35:11.700> years 00:35:11.930 --> 00:35:11.940 align:start position:0% were going to take it maybe 12 years 00:35:11.940 --> 00:35:17.109 align:start position:0% were going to take it maybe 12 years time<00:35:12.150> I<00:35:13.280> feel<00:35:14.280> like<00:35:14.430> it's<00:35:14.640> kind<00:35:15.000> of<00:35:15.119> a<00:35:15.240> case<00:35:15.420> of 00:35:17.109 --> 00:35:17.119 align:start position:0% time I feel like it's kind of a case of 00:35:17.119 --> 00:35:22.099 align:start position:0% time I feel like it's kind of a case of premature<00:35:18.119> optimization<00:35:19.220> like<00:35:20.220> you<00:35:20.940> know<00:35:21.109> we 00:35:22.099 --> 00:35:22.109 align:start position:0% premature optimization like you know we 00:35:22.109 --> 00:35:23.900 align:start position:0% premature optimization like you know we have<00:35:22.350> this<00:35:22.560> idea<00:35:22.770> that<00:35:23.070> oh<00:35:23.250> maybe<00:35:23.609> in<00:35:23.820> the 00:35:23.900 --> 00:35:23.910 align:start position:0% have this idea that oh maybe in the 00:35:23.910 --> 00:35:26.330 align:start position:0% have this idea that oh maybe in the future<00:35:24.119> they'll<00:35:24.630> be<00:35:24.810> different<00:35:25.200> short<00:35:25.470> so<00:35:25.890> I<00:35:25.920> I 00:35:26.330 --> 00:35:26.340 align:start position:0% future they'll be different short so I I 00:35:26.340 --> 00:35:30.080 align:start position:0% future they'll be different short so I I make<00:35:27.270> certain<00:35:27.690> decisions<00:35:27.720> now<00:35:28.670> that<00:35:29.670> that's 00:35:30.080 --> 00:35:30.090 align:start position:0% make certain decisions now that that's 00:35:30.090 --> 00:35:34.810 align:start position:0% make certain decisions now that that's probably<00:35:30.720> not<00:35:31.350> a<00:35:31.410> a<00:35:31.890> good<00:35:32.850> approach<00:35:33.210> and<00:35:33.570> I 00:35:34.810 --> 00:35:34.820 align:start position:0% probably not a a good approach and I 00:35:34.820 --> 00:35:45.430 align:start position:0% probably not a a good approach and I mean<00:35:35.820> I<00:35:36.920> think<00:35:37.920> with<00:35:38.670> any<00:35:39.000> future<00:35:42.440> upgrades<00:35:44.330> I 00:35:45.430 --> 00:35:45.440 align:start position:0% mean I think with any future upgrades I 00:35:45.440 --> 00:35:50.330 align:start position:0% mean I think with any future upgrades I guess<00:35:46.440> what<00:35:47.040> what<00:35:47.400> they<00:35:47.660> should<00:35:48.660> just<00:35:49.340> you 00:35:50.330 --> 00:35:50.340 align:start position:0% guess what what they should just you 00:35:50.340 --> 00:35:53.060 align:start position:0% guess what what they should just you know<00:35:50.400> we<00:35:51.060> can<00:35:51.180> probably<00:35:51.450> rely<00:35:51.960> on<00:35:52.200> future 00:35:53.060 --> 00:35:53.070 align:start position:0% know we can probably rely on future 00:35:53.070 --> 00:35:57.560 align:start position:0% know we can probably rely on future upgrade<00:35:53.960> not<00:35:55.430> directly<00:35:56.430> breaking<00:35:57.000> what<00:35:57.240> works 00:35:57.560 --> 00:35:57.570 align:start position:0% upgrade not directly breaking what works 00:35:57.570 --> 00:36:00.859 align:start position:0% upgrade not directly breaking what works now<00:35:57.960> and<00:35:58.290> so<00:35:58.830> you<00:35:59.580> know<00:35:59.640> if<00:35:59.820> we<00:36:00.240> create<00:36:00.450> stuff 00:36:00.859 --> 00:36:00.869 align:start position:0% now and so you know if we create stuff 00:36:00.869 --> 00:36:03.480 align:start position:0% now and so you know if we create stuff that<00:36:01.109> works<00:36:01.369> now<00:36:02.369> and 00:36:03.480 --> 00:36:03.490 align:start position:0% that works now and 00:36:03.490 --> 00:36:06.410 align:start position:0% that works now and and<00:36:04.150> make<00:36:04.510> sure<00:36:04.540> that<00:36:04.900> works<00:36:05.170> I<00:36:05.440> think<00:36:05.890> it's<00:36:06.070> I 00:36:06.410 --> 00:36:06.420 align:start position:0% and make sure that works I think it's I 00:36:06.420 --> 00:36:10.680 align:start position:0% and make sure that works I think it's I think<00:36:07.420> that's<00:36:07.780> good<00:36:08.520> so<00:36:09.520> yes<00:36:10.060> there's<00:36:10.420> always 00:36:10.680 --> 00:36:10.690 align:start position:0% think that's good so yes there's always 00:36:10.690 --> 00:36:12.359 align:start position:0% think that's good so yes there's always the<00:36:10.780> possibility<00:36:10.930> to<00:36:11.440> basically<00:36:11.890> copy<00:36:12.220> a 00:36:12.359 --> 00:36:12.369 align:start position:0% the possibility to basically copy a 00:36:12.369 --> 00:36:14.850 align:start position:0% the possibility to basically copy a contract<00:36:13.060> and<00:36:13.300> copy<00:36:13.630> it<00:36:13.810> storage<00:36:14.260> I<00:36:14.500> mean<00:36:14.710> it 00:36:14.850 --> 00:36:14.860 align:start position:0% contract and copy it storage I mean it 00:36:14.860 --> 00:36:16.770 align:start position:0% contract and copy it storage I mean it would<00:36:15.070> be<00:36:15.100> maybe<00:36:15.430> a<00:36:15.580> manual<00:36:15.940> process<00:36:16.000> or<00:36:16.600> but 00:36:16.770 --> 00:36:16.780 align:start position:0% would be maybe a manual process or but 00:36:16.780 --> 00:36:18.210 align:start position:0% would be maybe a manual process or but it<00:36:16.900> will<00:36:17.110> work<00:36:17.320> so<00:36:17.530> you<00:36:17.619> can<00:36:17.710> always<00:36:18.070> like 00:36:18.210 --> 00:36:18.220 align:start position:0% it will work so you can always like 00:36:18.220 --> 00:36:20.460 align:start position:0% it will work so you can always like basically<00:36:18.610> change<00:36:19.090> it<00:36:19.330> move<00:36:19.690> it<00:36:19.810> over<00:36:19.930> you 00:36:20.460 --> 00:36:20.470 align:start position:0% basically change it move it over you 00:36:20.470 --> 00:36:22.050 align:start position:0% basically change it move it over you just<00:36:20.710> have<00:36:20.860> to<00:36:20.890> point<00:36:21.130> interfaces<00:36:21.790> 10<00:36:21.940> to<00:36:22.030> the 00:36:22.050 --> 00:36:22.060 align:start position:0% just have to point interfaces 10 to the 00:36:22.060 --> 00:36:24.840 align:start position:0% just have to point interfaces 10 to the new<00:36:22.330> one<00:36:22.540> yeah<00:36:23.020> so<00:36:23.590> in<00:36:23.830> the<00:36:23.950> worst<00:36:24.190> case<00:36:24.490> kind 00:36:24.840 --> 00:36:24.850 align:start position:0% new one yeah so in the worst case kind 00:36:24.850 --> 00:36:27.930 align:start position:0% new one yeah so in the worst case kind of<00:36:25.260> the<00:36:26.260> contracts<00:36:26.650> contains<00:36:27.040> either<00:36:27.280> or<00:36:27.670> any 00:36:27.930 --> 00:36:27.940 align:start position:0% of the contracts contains either or any 00:36:27.940 --> 00:36:29.540 align:start position:0% of the contracts contains either or any other<00:36:28.119> assets<00:36:28.540> you<00:36:28.630> don't<00:36:28.810> control<00:36:29.080> right 00:36:29.540 --> 00:36:29.550 align:start position:0% other assets you don't control right 00:36:29.550 --> 00:36:34.430 align:start position:0% other assets you don't control right yeah<00:36:30.550> but<00:36:31.210> yeah<00:36:31.390> you<00:36:31.450> using<00:36:32.140> winners<00:36:32.740> into<00:36:33.430> two 00:36:34.430 --> 00:36:34.440 align:start position:0% yeah but yeah you using winners into two 00:36:34.440 --> 00:36:37.710 align:start position:0% yeah but yeah you using winners into two contracts<00:36:35.440> in<00:36:35.619> a<00:36:35.680> modular<00:36:35.860> fashion<00:36:36.310> is<00:36:36.730> good 00:36:37.710 --> 00:36:37.720 align:start position:0% contracts in a modular fashion is good 00:36:37.720 --> 00:36:39.930 align:start position:0% contracts in a modular fashion is good incidentally<00:36:38.500> those<00:36:38.680> less<00:36:39.310> particular 00:36:39.930 --> 00:36:39.940 align:start position:0% incidentally those less particular 00:36:39.940 --> 00:36:42.060 align:start position:0% incidentally those less particular argument<00:36:40.119> is<00:36:40.510> actually<00:36:41.290> a<00:36:41.320> very<00:36:41.560> good<00:36:41.890> reason 00:36:42.060 --> 00:36:42.070 align:start position:0% argument is actually a very good reason 00:36:42.070 --> 00:36:44.730 align:start position:0% argument is actually a very good reason why<00:36:42.460> you<00:36:42.520> might<00:36:42.790> a<00:36:42.850> very<00:36:43.750> good<00:36:44.140> argument<00:36:44.350> in 00:36:44.730 --> 00:36:44.740 align:start position:0% why you might a very good argument in 00:36:44.740 --> 00:36:46.560 align:start position:0% why you might a very good argument in favor<00:36:45.010> of<00:36:45.190> different<00:36:45.790> depths<00:36:46.119> basically 00:36:46.560 --> 00:36:46.570 align:start position:0% favor of different depths basically 00:36:46.570 --> 00:36:54.000 align:start position:0% favor of different depths basically creating<00:36:46.930> their<00:36:47.080> own<00:36:47.140> sub<00:36:47.440> tokens<00:36:52.650> I<00:36:53.650> think 00:36:54.000 --> 00:36:54.010 align:start position:0% creating their own sub tokens I think 00:36:54.010 --> 00:36:56.340 align:start position:0% creating their own sub tokens I think that's<00:36:54.580> it<00:36:54.730> for<00:36:54.760> this<00:36:55.150> panel<00:36:55.330> so<00:36:55.630> I<00:36:55.660> thank<00:36:56.170> all 00:36:56.340 --> 00:36:56.350 align:start position:0% that's it for this panel so I thank all 00:36:56.350 --> 00:37:00.060 align:start position:0% that's it for this panel so I thank all the<00:36:56.500> people<00:36:56.830> thank<00:36:57.790> you<00:36:57.850> very<00:36:57.880> much