WEBVTT Kind: captions Language: en 00:00:01.070 --> 00:00:08.990 align:start position:0% [Applause] 00:00:08.990 --> 00:00:09.000 align:start position:0% 00:00:09.000 --> 00:00:16.039 align:start position:0% oh<00:00:12.860> this<00:00:13.860> is<00:00:14.010> the<00:00:14.130> UX<00:00:14.460> prank<00:00:14.820> art<00:00:15.000> room<00:00:15.270> and 00:00:16.039 --> 00:00:16.049 align:start position:0% oh this is the UX prank art room and 00:00:16.049 --> 00:00:17.540 align:start position:0% oh this is the UX prank art room and it's<00:00:16.200> all<00:00:16.350> about<00:00:16.560> like<00:00:16.890> you<00:00:17.040> know<00:00:17.070> how<00:00:17.369> do<00:00:17.430> we 00:00:17.540 --> 00:00:17.550 align:start position:0% it's all about like you know how do we 00:00:17.550 --> 00:00:22.400 align:start position:0% it's all about like you know how do we do<00:00:17.820> blockchain<00:00:18.750> easier<00:00:19.170> and<00:00:19.320> better<00:00:19.500> I<00:00:21.410> think 00:00:22.400 --> 00:00:22.410 align:start position:0% do blockchain easier and better I think 00:00:22.410 --> 00:00:24.170 align:start position:0% do blockchain easier and better I think I<00:00:22.590> wouldn't<00:00:22.830> go<00:00:22.980> quickly<00:00:23.310> to<00:00:23.520> a<00:00:23.550> slice<00:00:23.880> because 00:00:24.170 --> 00:00:24.180 align:start position:0% I wouldn't go quickly to a slice because 00:00:24.180 --> 00:00:26.240 align:start position:0% I wouldn't go quickly to a slice because it's<00:00:24.330> not<00:00:24.450> that<00:00:24.570> complicated<00:00:24.900> as<00:00:25.560> most<00:00:25.919> people 00:00:26.240 --> 00:00:26.250 align:start position:0% it's not that complicated as most people 00:00:26.250 --> 00:00:27.740 align:start position:0% it's not that complicated as most people will<00:00:26.400> get<00:00:26.939> the<00:00:27.150> problem 00:00:27.740 --> 00:00:27.750 align:start position:0% will get the problem 00:00:27.750 --> 00:00:33.229 align:start position:0% will get the problem definitely<00:00:28.790> so<00:00:29.790> we<00:00:30.029> have<00:00:30.210> obviously<00:00:30.950> I<00:00:32.239> would 00:00:33.229 --> 00:00:33.239 align:start position:0% definitely so we have obviously I would 00:00:33.239 --> 00:00:36.710 align:start position:0% definitely so we have obviously I would start<00:00:33.480> with<00:00:33.590> two<00:00:34.590> statements<00:00:35.160> segment<00:00:36.120> one<00:00:36.480> is 00:00:36.710 --> 00:00:36.720 align:start position:0% start with two statements segment one is 00:00:36.720 --> 00:00:41.330 align:start position:0% start with two statements segment one is I<00:00:37.130> think<00:00:38.180> 2019<00:00:39.180> is<00:00:39.450> the<00:00:39.780> year<00:00:40.770> of<00:00:40.800> web<00:00:41.130> through 00:00:41.330 --> 00:00:41.340 align:start position:0% I think 2019 is the year of web through 00:00:41.340 --> 00:00:43.250 align:start position:0% I think 2019 is the year of web through UX<00:00:41.700> I<00:00:41.910> mean<00:00:42.060> that's<00:00:42.240> kind<00:00:42.450> of<00:00:42.600> most<00:00:42.840> people 00:00:43.250 --> 00:00:43.260 align:start position:0% UX I mean that's kind of most people 00:00:43.260 --> 00:00:45.950 align:start position:0% UX I mean that's kind of most people questions<00:00:43.680> we<00:00:43.860> had<00:00:44.040> so<00:00:44.820> far<00:00:45.090> in<00:00:45.300> the<00:00:45.420> last<00:00:45.540> few 00:00:45.950 --> 00:00:45.960 align:start position:0% questions we had so far in the last few 00:00:45.960 --> 00:00:47.810 align:start position:0% questions we had so far in the last few in<00:00:46.380> the<00:00:46.470> last<00:00:46.680> year<00:00:47.070> in<00:00:47.160> the<00:00:47.190> last<00:00:47.250> few<00:00:47.520> months 00:00:47.810 --> 00:00:47.820 align:start position:0% in the last year in the last few months 00:00:47.820 --> 00:00:49.940 align:start position:0% in the last year in the last few months was<00:00:47.940> can<00:00:48.180> how<00:00:48.300> can<00:00:48.330> we<00:00:48.570> make<00:00:48.780> this<00:00:49.380> work<00:00:49.680> three 00:00:49.940 --> 00:00:49.950 align:start position:0% was can how can we make this work three 00:00:49.950 --> 00:00:54.320 align:start position:0% was can how can we make this work three easier<00:00:50.430> in<00:00:50.670> better<00:00:50.910> and<00:00:51.330> a<00:00:52.140> lot<00:00:52.680> of<00:00:53.330> actually 00:00:54.320 --> 00:00:54.330 align:start position:0% easier in better and a lot of actually 00:00:54.330 --> 00:00:56.210 align:start position:0% easier in better and a lot of actually solutions<00:00:54.810> already<00:00:54.960> tried<00:00:55.380> onward<00:00:55.770> but<00:00:55.980> it 00:00:56.210 --> 00:00:56.220 align:start position:0% solutions already tried onward but it 00:00:56.220 --> 00:00:58.550 align:start position:0% solutions already tried onward but it doesn't<00:00:56.550> really<00:00:56.640> unify<00:00:57.180> in<00:00:57.510> a<00:00:57.630> very<00:00:58.020> common 00:00:58.550 --> 00:00:58.560 align:start position:0% doesn't really unify in a very common 00:00:58.560 --> 00:01:00.440 align:start position:0% doesn't really unify in a very common thing<00:00:58.740> people<00:00:59.070> use<00:00:59.400> and<00:00:59.790> to<00:01:00.000> make<00:01:00.150> it<00:01:00.180> better 00:01:00.440 --> 00:01:00.450 align:start position:0% thing people use and to make it better 00:01:00.450 --> 00:01:03.560 align:start position:0% thing people use and to make it better the<00:01:01.380> other<00:01:01.410> thing<00:01:01.770> is<00:01:01.920> I<00:01:02.190> guess<00:01:02.460> that's<00:01:03.390> my 00:01:03.560 --> 00:01:03.570 align:start position:0% the other thing is I guess that's my 00:01:03.570 --> 00:01:05.929 align:start position:0% the other thing is I guess that's my assumption<00:01:03.960> is<00:01:04.259> that<00:01:04.290> next<00:01:04.949> year<00:01:05.339> actually<00:01:05.580> we 00:01:05.929 --> 00:01:05.939 align:start position:0% assumption is that next year actually we 00:01:05.939 --> 00:01:07.490 align:start position:0% assumption is that next year actually we will<00:01:06.119> see<00:01:06.270> the<00:01:06.360> first<00:01:06.509> applications<00:01:07.200> that 00:01:07.490 --> 00:01:07.500 align:start position:0% will see the first applications that 00:01:07.500 --> 00:01:10.990 align:start position:0% will see the first applications that will<00:01:07.799> be<00:01:08.310> used<00:01:08.520> by<00:01:08.610> the<00:01:08.700> mainstream<00:01:09.110> where 00:01:10.990 --> 00:01:11.000 align:start position:0% will be used by the mainstream where 00:01:11.000 --> 00:01:13.580 align:start position:0% will be used by the mainstream where adoption<00:01:12.000> might<00:01:12.240> not<00:01:12.390> be<00:01:12.509> even<00:01:12.840> in<00:01:13.110> the<00:01:13.320> port 00:01:13.580 --> 00:01:13.590 align:start position:0% adoption might not be even in the port 00:01:13.590 --> 00:01:16.340 align:start position:0% adoption might not be even in the port front<00:01:13.890> and<00:01:14.390> will<00:01:15.390> not<00:01:15.510> be<00:01:15.659> about<00:01:15.960> blockchain 00:01:16.340 --> 00:01:16.350 align:start position:0% front and will not be about blockchain 00:01:16.350 --> 00:01:18.649 align:start position:0% front and will not be about blockchain it<00:01:16.860> will<00:01:17.040> be<00:01:17.130> about<00:01:17.280> some<00:01:17.850> cool<00:01:18.060> app<00:01:18.300> or<00:01:18.510> some 00:01:18.649 --> 00:01:18.659 align:start position:0% it will be about some cool app or some 00:01:18.659 --> 00:01:21.050 align:start position:0% it will be about some cool app or some cool<00:01:19.080> thing<00:01:19.230> to<00:01:19.409> do<00:01:19.560> and<00:01:19.800> by<00:01:20.550> the<00:01:20.610> way<00:01:20.790> you<00:01:20.850> also 00:01:21.050 --> 00:01:21.060 align:start position:0% cool thing to do and by the way you also 00:01:21.060 --> 00:01:24.170 align:start position:0% cool thing to do and by the way you also use<00:01:21.270> the<00:01:21.420> blockchain<00:01:21.659> to<00:01:21.900> some<00:01:22.050> degree<00:01:23.180> the 00:01:24.170 --> 00:01:24.180 align:start position:0% use the blockchain to some degree the 00:01:24.180 --> 00:01:28.670 align:start position:0% use the blockchain to some degree the big<00:01:24.330> problems<00:01:24.690> we<00:01:24.840> have<00:01:26.630> with<00:01:27.630> Bronx<00:01:28.020> doctrine 00:01:28.670 --> 00:01:28.680 align:start position:0% big problems we have with Bronx doctrine 00:01:28.680 --> 00:01:32.330 align:start position:0% big problems we have with Bronx doctrine UX<00:01:29.190> or<00:01:29.430> the<00:01:29.550> web<00:01:29.700> 3<00:01:29.970> UX<00:01:30.330> is<00:01:31.010> maybe<00:01:32.010> actually 00:01:32.330 --> 00:01:32.340 align:start position:0% UX or the web 3 UX is maybe actually 00:01:32.340 --> 00:01:34.190 align:start position:0% UX or the web 3 UX is maybe actually start<00:01:32.820> shortly<00:01:33.180> about<00:01:33.330> my<00:01:33.600> background<00:01:33.840> and 00:01:34.190 --> 00:01:34.200 align:start position:0% start shortly about my background and 00:01:34.200 --> 00:01:36.550 align:start position:0% start shortly about my background and everybody<00:01:34.860> knows<00:01:35.040> my<00:01:35.220> background<00:01:35.400> here<00:01:35.940> or 00:01:36.550 --> 00:01:36.560 align:start position:0% everybody knows my background here or 00:01:36.560 --> 00:01:45.350 align:start position:0% everybody knows my background here or again<00:01:37.560> who<00:01:37.890> does<00:01:38.340> not<00:01:39.740> okay<00:01:42.200> so<00:01:44.060> quickly<00:01:45.060> so<00:01:45.330> I 00:01:45.350 --> 00:01:45.360 align:start position:0% again who does not okay so quickly so I 00:01:45.360 --> 00:01:46.760 align:start position:0% again who does not okay so quickly so I actually<00:01:45.870> been<00:01:46.140> part<00:01:46.380> of<00:01:46.440> the<00:01:46.590> theme 00:01:46.760 --> 00:01:46.770 align:start position:0% actually been part of the theme 00:01:46.770 --> 00:01:50.810 align:start position:0% actually been part of the theme foundation<00:01:47.990> since<00:01:49.010> 2015<00:01:50.010> I<00:01:50.280> joined<00:01:50.640> in 00:01:50.810 --> 00:01:50.820 align:start position:0% foundation since 2015 I joined in 00:01:50.820 --> 00:01:54.190 align:start position:0% foundation since 2015 I joined in January<00:01:51.180> 2015<00:01:51.690> have<00:01:52.170> built<00:01:52.470> the<00:01:52.740> MIS<00:01:53.580> browser 00:01:54.190 --> 00:01:54.200 align:start position:0% January 2015 have built the MIS browser 00:01:54.200 --> 00:01:56.630 align:start position:0% January 2015 have built the MIS browser new<00:01:55.200> people<00:01:55.590> have<00:01:55.710> not<00:01:55.920> heard<00:01:56.100> about<00:01:56.159> that<00:01:56.460> but 00:01:56.630 --> 00:01:56.640 align:start position:0% new people have not heard about that but 00:01:56.640 --> 00:01:58.250 align:start position:0% new people have not heard about that but in<00:01:56.760> fact<00:01:56.790> in<00:01:57.299> the<00:01:57.390> day<00:01:57.540> it<00:01:57.720> was<00:01:57.869> the<00:01:57.900> first 00:01:58.250 --> 00:01:58.260 align:start position:0% in fact in the day it was the first 00:01:58.260 --> 00:02:01.219 align:start position:0% in fact in the day it was the first season<00:01:58.590> first<00:01:58.770> app<00:01:59.280> browser<00:01:59.970> we<00:02:00.930> kind<00:02:01.140> of 00:02:01.219 --> 00:02:01.229 align:start position:0% season first app browser we kind of 00:02:01.229 --> 00:02:04.460 align:start position:0% season first app browser we kind of coined<00:02:01.500> the<00:02:01.619> term<00:02:01.920> D<00:02:02.190> app<00:02:02.400> and<00:02:03.200> the<00:02:04.200> theme 00:02:04.460 --> 00:02:04.470 align:start position:0% coined the term D app and the theme 00:02:04.470 --> 00:02:07.460 align:start position:0% coined the term D app and the theme wallet<00:02:05.030> was<00:02:06.030> one<00:02:06.570> application<00:02:07.229> was<00:02:07.350> in 00:02:07.460 --> 00:02:07.470 align:start position:0% wallet was one application was in 00:02:07.470 --> 00:02:09.679 align:start position:0% wallet was one application was in dismiss<00:02:07.740> browser<00:02:08.009> and<00:02:08.399> I<00:02:08.610> have<00:02:08.789> worked<00:02:09.030> on<00:02:09.179> web 00:02:09.679 --> 00:02:09.689 align:start position:0% dismiss browser and I have worked on web 00:02:09.689 --> 00:02:11.300 align:start position:0% dismiss browser and I have worked on web switches<00:02:10.110> kind<00:02:10.530> of<00:02:10.590> like<00:02:10.739> the<00:02:10.830> JavaScript 00:02:11.300 --> 00:02:11.310 align:start position:0% switches kind of like the JavaScript 00:02:11.310 --> 00:02:11.949 align:start position:0% switches kind of like the JavaScript library 00:02:11.949 --> 00:02:11.959 align:start position:0% library 00:02:11.959 --> 00:02:15.580 align:start position:0% library I<00:02:11.989> guess<00:02:12.260> most<00:02:12.980> of<00:02:13.069> you<00:02:13.129> use<00:02:14.260> that<00:02:15.260> is<00:02:15.409> the 00:02:15.580 --> 00:02:15.590 align:start position:0% I guess most of you use that is the 00:02:15.590 --> 00:02:17.170 align:start position:0% I guess most of you use that is the library<00:02:15.950> kind<00:02:16.129> of<00:02:16.219> like<00:02:16.370> you<00:02:16.549> know<00:02:16.670> we<00:02:16.819> define 00:02:17.170 --> 00:02:17.180 align:start position:0% library kind of like you know we define 00:02:17.180 --> 00:02:19.660 align:start position:0% library kind of like you know we define like<00:02:17.209> the<00:02:17.540> first<00:02:17.750> way<00:02:17.959> of<00:02:18.650> how<00:02:19.129> you<00:02:19.189> interact 00:02:19.660 --> 00:02:19.670 align:start position:0% like the first way of how you interact 00:02:19.670 --> 00:02:23.459 align:start position:0% like the first way of how you interact with<00:02:20.090> so<00:02:20.870> much<00:02:20.959> contracts<00:02:21.409> and<00:02:21.560> one<00:02:21.799> chain<00:02:22.129> and 00:02:23.459 --> 00:02:23.469 align:start position:0% with so much contracts and one chain and 00:02:23.469 --> 00:02:25.809 align:start position:0% with so much contracts and one chain and guess<00:02:24.469> where<00:02:24.739> Fuji<00:02:24.950> is<00:02:25.040> is<00:02:25.280> one<00:02:25.430> of<00:02:25.459> the<00:02:25.670> first 00:02:25.809 --> 00:02:25.819 align:start position:0% guess where Fuji is is one of the first 00:02:25.819 --> 00:02:27.699 align:start position:0% guess where Fuji is is one of the first ones<00:02:26.120> that<00:02:26.239> made<00:02:26.420> like<00:02:26.599> building<00:02:27.530> on<00:02:27.620> the 00:02:27.699 --> 00:02:27.709 align:start position:0% ones that made like building on the 00:02:27.709 --> 00:02:28.059 align:start position:0% ones that made like building on the blockchain 00:02:28.059 --> 00:02:28.069 align:start position:0% blockchain 00:02:28.069 --> 00:02:32.830 align:start position:0% blockchain easy<00:02:29.060> and<00:02:29.269> more<00:02:29.840> fun<00:02:30.200> to<00:02:30.439> do<00:02:30.590> I<00:02:30.620> hope<00:02:31.569> so<00:02:32.569> my 00:02:32.830 --> 00:02:32.840 align:start position:0% easy and more fun to do I hope so my 00:02:32.840 --> 00:02:34.660 align:start position:0% easy and more fun to do I hope so my kind<00:02:33.049> of<00:02:33.139> like<00:02:33.530> bigger<00:02:33.829> work<00:02:34.129> besides<00:02:34.519> like 00:02:34.660 --> 00:02:34.670 align:start position:0% kind of like bigger work besides like 00:02:34.670 --> 00:02:36.399 align:start position:0% kind of like bigger work besides like being<00:02:34.969> in<00:02:35.269> there<00:02:35.420> were<00:02:35.510> three<00:02:35.750> teams<00:02:36.019> it's<00:02:36.319> a 00:02:36.399 --> 00:02:36.409 align:start position:0% being in there were three teams it's a 00:02:36.409 --> 00:02:39.009 align:start position:0% being in there were three teams it's a long<00:02:36.590> time<00:02:36.829> actually<00:02:37.159> was<00:02:37.459> the<00:02:37.790> 1.0<00:02:38.540> build 00:02:39.009 --> 00:02:39.019 align:start position:0% long time actually was the 1.0 build 00:02:39.019 --> 00:02:42.309 align:start position:0% long time actually was the 1.0 build which<00:02:39.620> was<00:02:39.799> recently<00:02:40.010> developed<00:02:40.790> released<00:02:41.719> so 00:02:42.309 --> 00:02:42.319 align:start position:0% which was recently developed released so 00:02:42.319 --> 00:02:43.569 align:start position:0% which was recently developed released so I<00:02:42.349> have<00:02:42.590> kind<00:02:42.799> of<00:02:42.859> like<00:02:42.920> you<00:02:43.159> know<00:02:43.250> came<00:02:43.430> up 00:02:43.569 --> 00:02:43.579 align:start position:0% I have kind of like you know came up 00:02:43.579 --> 00:02:45.729 align:start position:0% I have kind of like you know came up with<00:02:43.700> this<00:02:43.790> API<00:02:44.090> to<00:02:44.689> make<00:02:44.810> it<00:02:44.989> the<00:02:45.139> way<00:02:45.290> how 00:02:45.729 --> 00:02:45.739 align:start position:0% with this API to make it the way how 00:02:45.739 --> 00:02:56.550 align:start position:0% with this API to make it the way how this<00:02:45.980> and<00:02:46.220> I<00:02:46.280> hope<00:02:46.489> it's<00:02:46.669> intuitive<00:02:47.150> say<00:02:47.900> yes 00:02:56.550 --> 00:02:56.560 align:start position:0% 00:02:56.560 --> 00:03:00.520 align:start position:0% so<00:02:57.560> the<00:02:58.129> big<00:02:58.310> problem<00:02:58.459> actually<00:02:58.819> so<00:02:59.659> okay<00:02:59.989> okay 00:03:00.520 --> 00:03:00.530 align:start position:0% so the big problem actually so okay okay 00:03:00.530 --> 00:03:04.319 align:start position:0% so the big problem actually so okay okay it's<00:03:00.680> also<00:03:00.829> easy<00:03:01.370> xx<00:03:01.819> which<00:03:02.090> I<00:03:02.239> propose<00:03:02.540> 2015 00:03:04.319 --> 00:03:04.329 align:start position:0% it's also easy xx which I propose 2015 00:03:04.329 --> 00:03:06.909 align:start position:0% it's also easy xx which I propose 2015 that's<00:03:05.329> kind<00:03:05.629> of<00:03:05.689> like<00:03:05.840> what<00:03:06.019> then<00:03:06.560> the<00:03:06.709> non 00:03:06.909 --> 00:03:06.919 align:start position:0% that's kind of like what then the non 00:03:06.919 --> 00:03:11.800 align:start position:0% that's kind of like what then the non tech<00:03:07.189> people<00:03:07.430> know<00:03:09.040> and<00:03:10.269> also<00:03:11.269> something 00:03:11.800 --> 00:03:11.810 align:start position:0% tech people know and also something 00:03:11.810 --> 00:03:13.449 align:start position:0% tech people know and also something which<00:03:12.139> I<00:03:12.260> will<00:03:12.409> be<00:03:12.500> speaking<00:03:12.680> today<00:03:12.889> which<00:03:13.430> is 00:03:13.449 --> 00:03:13.459 align:start position:0% which I will be speaking today which is 00:03:13.459 --> 00:03:16.390 align:start position:0% which I will be speaking today which is is<00:03:13.760> a<00:03:13.879> seven<00:03:14.209> to<00:03:14.269> five<00:03:14.590> some<00:03:15.590> big<00:03:15.799> problems<00:03:16.190> all 00:03:16.390 --> 00:03:16.400 align:start position:0% is a seven to five some big problems all 00:03:16.400 --> 00:03:18.580 align:start position:0% is a seven to five some big problems all unchain<00:03:16.790> is<00:03:16.970> obviously<00:03:17.409> the<00:03:18.409> business 00:03:18.580 --> 00:03:18.590 align:start position:0% unchain is obviously the business 00:03:18.590 --> 00:03:21.250 align:start position:0% unchain is obviously the business probably<00:03:19.430> the<00:03:19.549> one<00:03:19.699> of<00:03:19.729> the<00:03:19.879> biggest<00:03:20.150> ones<00:03:20.419> you 00:03:21.250 --> 00:03:21.260 align:start position:0% probably the one of the biggest ones you 00:03:21.260 --> 00:03:23.050 align:start position:0% probably the one of the biggest ones you want<00:03:21.470> to<00:03:21.530> do<00:03:21.620> a<00:03:21.650> cool<00:03:21.889> app<00:03:22.099> which<00:03:22.819> uses 00:03:23.050 --> 00:03:23.060 align:start position:0% want to do a cool app which uses 00:03:23.060 --> 00:03:24.819 align:start position:0% want to do a cool app which uses blockchain<00:03:23.659> and<00:03:23.930> the<00:03:24.290> first<00:03:24.500> thing<00:03:24.680> people 00:03:24.819 --> 00:03:24.829 align:start position:0% blockchain and the first thing people 00:03:24.829 --> 00:03:29.619 align:start position:0% blockchain and the first thing people encounter<00:03:25.250> is<00:03:26.169> gas<00:03:27.169> and<00:03:28.209> especially<00:03:29.209> even<00:03:29.510> if 00:03:29.619 --> 00:03:29.629 align:start position:0% encounter is gas and especially even if 00:03:29.629 --> 00:03:31.330 align:start position:0% encounter is gas and especially even if you<00:03:29.720> get<00:03:29.900> you<00:03:30.199> even<00:03:30.620> if<00:03:30.769> you<00:03:30.859> come<00:03:31.040> from<00:03:31.189> the 00:03:31.330 --> 00:03:31.340 align:start position:0% you get you even if you come from the 00:03:31.340 --> 00:03:33.849 align:start position:0% you get you even if you come from the blockchain<00:03:31.699> of<00:03:32.090> Bitcoin<00:03:32.479> community<00:03:32.709> known<00:03:33.709> as 00:03:33.849 --> 00:03:33.859 align:start position:0% blockchain of Bitcoin community known as 00:03:33.859 --> 00:03:35.740 align:start position:0% blockchain of Bitcoin community known as the<00:03:34.010> areum<00:03:34.280> you're<00:03:34.849> totally<00:03:35.060> puzzled<00:03:35.359> what 00:03:35.740 --> 00:03:35.750 align:start position:0% the areum you're totally puzzled what 00:03:35.750 --> 00:03:38.319 align:start position:0% the areum you're totally puzzled what that<00:03:35.900> even<00:03:36.019> means<00:03:36.319> it's<00:03:37.099> got<00:03:37.400> an<00:03:37.579> extra<00:03:37.879> token 00:03:38.319 --> 00:03:38.329 align:start position:0% that even means it's got an extra token 00:03:38.329 --> 00:03:40.119 align:start position:0% that even means it's got an extra token and<00:03:38.569> now<00:03:39.019> if<00:03:39.169> the<00:03:39.290> gas<00:03:39.470> talking<00:03:39.859> actually 00:03:40.119 --> 00:03:40.129 align:start position:0% and now if the gas talking actually 00:03:40.129 --> 00:03:42.610 align:start position:0% and now if the gas talking actually people<00:03:40.340> think<00:03:40.669> it's<00:03:40.790> a<00:03:40.849> token<00:03:41.060> so<00:03:41.509> what<00:03:42.229> is<00:03:42.379> gas 00:03:42.610 --> 00:03:42.620 align:start position:0% people think it's a token so what is gas 00:03:42.620 --> 00:03:45.699 align:start position:0% people think it's a token so what is gas and<00:03:43.009> most<00:03:43.430> of<00:03:43.549> the<00:03:43.699> people<00:03:44.290> don't<00:03:45.290> know<00:03:45.470> why<00:03:45.680> I 00:03:45.699 --> 00:03:45.709 align:start position:0% and most of the people don't know why I 00:03:45.709 --> 00:03:47.920 align:start position:0% and most of the people don't know why I now<00:03:46.099> need<00:03:46.370> something<00:03:46.790> called<00:03:46.939> ether<00:03:47.359> just<00:03:47.750> to 00:03:47.920 --> 00:03:47.930 align:start position:0% now need something called ether just to 00:03:47.930 --> 00:03:51.330 align:start position:0% now need something called ether just to do<00:03:48.049> something<00:03:48.439> in<00:03:48.620> a<00:03:48.650> box<00:03:49.430> chain<00:03:49.549> based<00:03:49.849> app 00:03:51.330 --> 00:03:51.340 align:start position:0% do something in a box chain based app 00:03:51.340 --> 00:03:54.129 align:start position:0% do something in a box chain based app and<00:03:52.340> the<00:03:52.459> other<00:03:52.579> big<00:03:52.759> problem<00:03:53.150> is<00:03:53.329> everything 00:03:54.129 --> 00:03:54.139 align:start position:0% and the other big problem is everything 00:03:54.139 --> 00:03:56.949 align:start position:0% and the other big problem is everything is<00:03:54.439> stored<00:03:54.739> on<00:03:54.919> keys<00:03:55.250> today<00:03:55.759> so<00:03:56.540> the<00:03:56.659> way<00:03:56.810> of 00:03:56.949 --> 00:03:56.959 align:start position:0% is stored on keys today so the way of 00:03:56.959 --> 00:03:58.599 align:start position:0% is stored on keys today so the way of how<00:03:57.139> we<00:03:57.199> interact<00:03:57.500> with<00:03:57.769> the<00:03:57.889> blockchain<00:03:58.099> is 00:03:58.599 --> 00:03:58.609 align:start position:0% how we interact with the blockchain is 00:03:58.609 --> 00:04:01.330 align:start position:0% how we interact with the blockchain is we<00:03:59.479> generate<00:04:00.109> a<00:04:00.169> private<00:04:00.500> key<00:04:00.680> or<00:04:00.889> we<00:04:01.159> have<00:04:01.310> a 00:04:01.330 --> 00:04:01.340 align:start position:0% we generate a private key or we have a 00:04:01.340 --> 00:04:03.339 align:start position:0% we generate a private key or we have a private<00:04:01.759> key<00:04:01.879> of<00:04:01.909> some<00:04:02.120> water<00:04:02.329> and<00:04:02.599> this<00:04:03.139> one 00:04:03.339 --> 00:04:03.349 align:start position:0% private key of some water and this one 00:04:03.349 --> 00:04:04.839 align:start position:0% private key of some water and this one signs<00:04:03.650> the<00:04:03.799> transaction<00:04:04.099> and<00:04:04.489> we<00:04:04.549> send<00:04:04.729> it<00:04:04.790> to 00:04:04.839 --> 00:04:04.849 align:start position:0% signs the transaction and we send it to 00:04:04.849 --> 00:04:08.830 align:start position:0% signs the transaction and we send it to the<00:04:05.000> network<00:04:05.949> the<00:04:06.949> problem<00:04:07.310> with<00:04:07.459> this<00:04:07.579> is<00:04:07.840> we 00:04:08.830 --> 00:04:08.840 align:start position:0% the network the problem with this is we 00:04:08.840 --> 00:04:10.539 align:start position:0% the network the problem with this is we are<00:04:08.870> dealing<00:04:09.259> here<00:04:09.439> with<00:04:09.590> the<00:04:09.829> lowest<00:04:10.189> level 00:04:10.539 --> 00:04:10.549 align:start position:0% are dealing here with the lowest level 00:04:10.549 --> 00:04:12.339 align:start position:0% are dealing here with the lowest level component<00:04:11.209> of<00:04:11.329> how<00:04:11.479> you<00:04:11.540> can<00:04:11.810> interact<00:04:12.079> with<00:04:12.319> a 00:04:12.339 --> 00:04:12.349 align:start position:0% component of how you can interact with a 00:04:12.349 --> 00:04:14.199 align:start position:0% component of how you can interact with a blockchain<00:04:12.889> and<00:04:13.040> we<00:04:13.189> store<00:04:13.459> all<00:04:13.489> our<00:04:13.639> assets 00:04:14.199 --> 00:04:14.209 align:start position:0% blockchain and we store all our assets 00:04:14.209 --> 00:04:18.080 align:start position:0% blockchain and we store all our assets and<00:04:14.329> our<00:04:14.449> things<00:04:14.780> on<00:04:14.989> that<00:04:15.609> lowest<00:04:16.609> level 00:04:18.080 --> 00:04:18.090 align:start position:0% and our things on that lowest level 00:04:18.090 --> 00:04:22.129 align:start position:0% and our things on that lowest level a tool<00:04:18.570> or<00:04:18.989> access<00:04:19.560> point<00:04:19.859> by<00:04:20.850> doing<00:04:21.209> that<00:04:21.389> we 00:04:22.129 --> 00:04:22.139 align:start position:0% a tool or access point by doing that we 00:04:22.139 --> 00:04:25.430 align:start position:0% a tool or access point by doing that we run<00:04:22.320> in<00:04:22.500> a<00:04:22.590> few<00:04:22.800> problems<00:04:23.990> you<00:04:24.990> have<00:04:25.110> to<00:04:25.260> back 00:04:25.430 --> 00:04:25.440 align:start position:0% run in a few problems you have to back 00:04:25.440 --> 00:04:27.469 align:start position:0% run in a few problems you have to back them<00:04:25.590> up<00:04:25.710> you<00:04:26.250> know<00:04:26.370> you<00:04:26.610> have<00:04:26.790> to<00:04:26.970> actually 00:04:27.469 --> 00:04:27.479 align:start position:0% them up you know you have to actually 00:04:27.479 --> 00:04:30.170 align:start position:0% them up you know you have to actually ask<00:04:27.930> your<00:04:28.320> user<00:04:28.560> to<00:04:28.979> create<00:04:29.430> a<00:04:29.460> very<00:04:29.760> secure 00:04:30.170 --> 00:04:30.180 align:start position:0% ask your user to create a very secure 00:04:30.180 --> 00:04:32.540 align:start position:0% ask your user to create a very secure backup<00:04:30.449> which<00:04:31.290> in<00:04:31.560> today's<00:04:31.860> terms<00:04:32.220> means 00:04:32.540 --> 00:04:32.550 align:start position:0% backup which in today's terms means 00:04:32.550 --> 00:04:34.909 align:start position:0% backup which in today's terms means writing<00:04:33.090> down<00:04:33.270> words<00:04:33.570> on<00:04:34.050> paper<00:04:34.350> people<00:04:34.650> don't 00:04:34.909 --> 00:04:34.919 align:start position:0% writing down words on paper people don't 00:04:34.919 --> 00:04:37.520 align:start position:0% writing down words on paper people don't have<00:04:35.510> so<00:04:36.510> we<00:04:36.900> force<00:04:37.199> them<00:04:37.350> to<00:04:37.380> make 00:04:37.520 --> 00:04:37.530 align:start position:0% have so we force them to make 00:04:37.530 --> 00:04:39.680 align:start position:0% have so we force them to make screenshots<00:04:38.100> and<00:04:38.430> storing<00:04:38.940> in<00:04:39.030> iCloud<00:04:39.210> which 00:04:39.680 --> 00:04:39.690 align:start position:0% screenshots and storing in iCloud which 00:04:39.690 --> 00:04:43.939 align:start position:0% screenshots and storing in iCloud which is<00:04:39.900> the<00:04:39.990> worst<00:04:40.229> form<00:04:40.500> of<00:04:40.560> safety<00:04:42.530> just<00:04:43.530> in<00:04:43.680> case 00:04:43.939 --> 00:04:43.949 align:start position:0% is the worst form of safety just in case 00:04:43.949 --> 00:04:46.189 align:start position:0% is the worst form of safety just in case you<00:04:44.190> know<00:04:44.310> we<00:04:44.490> have<00:04:44.790> a<00:04:44.820> bit<00:04:45.090> more<00:04:45.270> security<00:04:45.630> the 00:04:46.189 --> 00:04:46.199 align:start position:0% you know we have a bit more security the 00:04:46.199 --> 00:04:48.860 align:start position:0% you know we have a bit more security the problem<00:04:46.590> is<00:04:46.850> you<00:04:47.850> know<00:04:47.970> you<00:04:48.210> make<00:04:48.389> people<00:04:48.720> go 00:04:48.860 --> 00:04:48.870 align:start position:0% problem is you know you make people go 00:04:48.870 --> 00:04:51.620 align:start position:0% problem is you know you make people go through<00:04:49.080> hurdles<00:04:49.470> and<00:04:49.949> complications<00:04:50.400> at<00:04:50.910> the 00:04:51.620 --> 00:04:51.630 align:start position:0% through hurdles and complications at the 00:04:51.630 --> 00:04:53.570 align:start position:0% through hurdles and complications at the time<00:04:51.900> where<00:04:52.110> they<00:04:52.200> don't<00:04:52.320> even<00:04:52.500> care<00:04:52.979> you<00:04:53.430> know 00:04:53.570 --> 00:04:53.580 align:start position:0% time where they don't even care you know 00:04:53.580 --> 00:04:55.760 align:start position:0% time where they don't even care you know or<00:04:53.850> nor<00:04:54.060> know<00:04:54.360> if<00:04:54.630> they<00:04:54.840> ever<00:04:55.139> one<00:04:55.410> day<00:04:55.500> you<00:04:55.620> see 00:04:55.760 --> 00:04:55.770 align:start position:0% or nor know if they ever one day you see 00:04:55.770 --> 00:04:59.320 align:start position:0% or nor know if they ever one day you see at<00:04:55.889> the<00:04:56.040> first<00:04:56.220> place<00:04:56.490> so<00:04:57.560> you<00:04:58.560> end<00:04:58.770> up<00:04:58.950> with 00:04:59.320 --> 00:04:59.330 align:start position:0% at the first place so you end up with 00:04:59.330 --> 00:05:02.180 align:start position:0% at the first place so you end up with basically<00:05:00.330> a<00:05:00.540> lot<00:05:00.720> of<00:05:00.750> leg<00:05:01.110> drops<00:05:01.380> out<00:05:01.620> right 00:05:02.180 --> 00:05:02.190 align:start position:0% basically a lot of leg drops out right 00:05:02.190 --> 00:05:03.050 align:start position:0% basically a lot of leg drops out right at<00:05:02.340> this<00:05:02.430> point<00:05:02.669> of<00:05:02.880> time 00:05:03.050 --> 00:05:03.060 align:start position:0% at this point of time 00:05:03.060 --> 00:05:06.020 align:start position:0% at this point of time so<00:05:03.930> only<00:05:04.380> the<00:05:04.740> tough<00:05:04.979> one<00:05:05.190> really<00:05:05.669> let<00:05:05.880> you 00:05:06.020 --> 00:05:06.030 align:start position:0% so only the tough one really let you 00:05:06.030 --> 00:05:07.820 align:start position:0% so only the tough one really let you know<00:05:06.150> what's<00:05:06.419> in<00:05:06.570> vests<00:05:06.960> or<00:05:07.110> to<00:05:07.380> something<00:05:07.620> in 00:05:07.820 --> 00:05:07.830 align:start position:0% know what's in vests or to something in 00:05:07.830 --> 00:05:09.290 align:start position:0% know what's in vests or to something in is<00:05:07.919> that<00:05:08.100> we'll<00:05:08.400> go<00:05:08.580> through<00:05:08.610> this<00:05:08.910> lengthy 00:05:09.290 --> 00:05:09.300 align:start position:0% is that we'll go through this lengthy 00:05:09.300 --> 00:05:11.719 align:start position:0% is that we'll go through this lengthy process<00:05:09.539> and<00:05:10.050> you<00:05:10.680> end<00:05:10.889> up<00:05:11.070> with<00:05:11.250> many<00:05:11.460> apps 00:05:11.719 --> 00:05:11.729 align:start position:0% process and you end up with many apps 00:05:11.729 --> 00:05:15.140 align:start position:0% process and you end up with many apps many<00:05:12.479> backup<00:05:12.900> keys<00:05:13.169> and<00:05:13.580> you<00:05:14.580> somehow<00:05:14.850> have<00:05:15.120> to 00:05:15.140 --> 00:05:15.150 align:start position:0% many backup keys and you somehow have to 00:05:15.150 --> 00:05:16.969 align:start position:0% many backup keys and you somehow have to manage<00:05:15.539> them<00:05:15.780> you<00:05:15.870> know<00:05:16.020> the<00:05:16.289> old<00:05:16.440> or<00:05:16.620> new<00:05:16.740> say 00:05:16.969 --> 00:05:16.979 align:start position:0% manage them you know the old or new say 00:05:16.979 --> 00:05:19.010 align:start position:0% manage them you know the old or new say guess<00:05:17.699> what<00:05:17.820> you<00:05:18.120> know<00:05:18.150> maybe<00:05:18.419> in<00:05:18.570> case<00:05:18.840> we 00:05:19.010 --> 00:05:19.020 align:start position:0% guess what you know maybe in case we 00:05:19.020 --> 00:05:21.050 align:start position:0% guess what you know maybe in case we have<00:05:19.169> some<00:05:19.199> some<00:05:20.070> value<00:05:20.460> in<00:05:20.520> the<00:05:20.610> future<00:05:20.760> on 00:05:21.050 --> 00:05:21.060 align:start position:0% have some some value in the future on 00:05:21.060 --> 00:05:23.629 align:start position:0% have some some value in the future on that<00:05:21.270> and<00:05:21.530> it<00:05:22.530> actually<00:05:22.680> happened<00:05:23.250> a<00:05:23.400> lot<00:05:23.580> of 00:05:23.629 --> 00:05:23.639 align:start position:0% that and it actually happened a lot of 00:05:23.639 --> 00:05:26.830 align:start position:0% that and it actually happened a lot of times<00:05:24.169> I<00:05:25.169> think<00:05:25.410> of<00:05:25.680> crypto<00:05:25.979> kitties<00:05:26.280> you<00:05:26.430> know 00:05:26.830 --> 00:05:26.840 align:start position:0% times I think of crypto kitties you know 00:05:26.840 --> 00:05:29.390 align:start position:0% times I think of crypto kitties you know whoever<00:05:27.840> thought<00:05:28.169> that<00:05:28.229> this<00:05:28.530> would<00:05:28.710> be<00:05:28.770> worth 00:05:29.390 --> 00:05:29.400 align:start position:0% whoever thought that this would be worth 00:05:29.400 --> 00:05:34.040 align:start position:0% whoever thought that this would be worth anything<00:05:29.810> until<00:05:30.810> it<00:05:30.930> did<00:05:32.479> so<00:05:33.479> used<00:05:33.750> to<00:05:33.780> seven 00:05:34.040 --> 00:05:34.050 align:start position:0% anything until it did so used to seven 00:05:34.050 --> 00:05:40.580 align:start position:0% anything until it did so used to seven to<00:05:34.110> five<00:05:34.289> kind<00:05:34.650> of<00:05:34.800> initially<00:05:35.520> was<00:05:35.760> in<00:05:39.560> 2017<00:05:40.560> or 00:05:40.580 --> 00:05:40.590 align:start position:0% to five kind of initially was in 2017 or 00:05:40.590 --> 00:05:43.400 align:start position:0% to five kind of initially was in 2017 or something<00:05:41.210> the<00:05:42.210> idea<00:05:42.479> okay<00:05:42.570> how<00:05:42.870> can<00:05:42.930> we<00:05:43.110> make 00:05:43.400 --> 00:05:43.410 align:start position:0% something the idea okay how can we make 00:05:43.410 --> 00:05:45.620 align:start position:0% something the idea okay how can we make basically<00:05:43.830> in<00:05:44.070> an<00:05:44.190> Unchained<00:05:44.760> account<00:05:45.389> or 00:05:45.620 --> 00:05:45.630 align:start position:0% basically in an Unchained account or 00:05:45.630 --> 00:05:47.779 align:start position:0% basically in an Unchained account or back<00:05:46.320> then<00:05:46.500> I<00:05:46.590> call<00:05:46.800> the<00:05:46.919> dungeon<00:05:47.250> identity 00:05:47.779 --> 00:05:47.789 align:start position:0% back then I call the dungeon identity 00:05:47.789 --> 00:05:49.730 align:start position:0% back then I call the dungeon identity until<00:05:48.240> the<00:05:48.389> whole<00:05:48.570> identity<00:05:48.750> community<00:05:49.500> like 00:05:49.730 --> 00:05:49.740 align:start position:0% until the whole identity community like 00:05:49.740 --> 00:05:51.770 align:start position:0% until the whole identity community like backslash<00:05:50.340> don't<00:05:50.610> need<00:05:50.729> Omega<00:05:51.090> RT<00:05:51.330> chemical 00:05:51.770 --> 00:05:51.780 align:start position:0% backslash don't need Omega RT chemical 00:05:51.780 --> 00:05:55.960 align:start position:0% backslash don't need Omega RT chemical edit<00:05:52.080> identity<00:05:53.060> and<00:05:54.410> basically<00:05:55.410> to<00:05:55.590> actually 00:05:55.960 --> 00:05:55.970 align:start position:0% edit identity and basically to actually 00:05:55.970 --> 00:05:58.520 align:start position:0% edit identity and basically to actually unify<00:05:56.970> this<00:05:57.210> whole<00:05:57.450> thing<00:05:57.750> of<00:05:58.020> like<00:05:58.260> how<00:05:58.500> I 00:05:58.520 --> 00:05:58.530 align:start position:0% unify this whole thing of like how I 00:05:58.530 --> 00:06:02.420 align:start position:0% unify this whole thing of like how I managed<00:05:59.190> ever<00:05:59.430> my<00:05:59.760> account<00:06:00.210> on<00:06:00.419> chain<00:06:00.780> and<00:06:01.430> how 00:06:02.420 --> 00:06:02.430 align:start position:0% managed ever my account on chain and how 00:06:02.430 --> 00:06:04.730 align:start position:0% managed ever my account on chain and how could<00:06:02.700> I<00:06:02.990> have<00:06:03.990> an<00:06:04.080> account<00:06:04.380> which<00:06:04.560> can 00:06:04.730 --> 00:06:04.740 align:start position:0% could I have an account which can 00:06:04.740 --> 00:06:06.140 align:start position:0% could I have an account which can receive<00:06:04.979> actually<00:06:05.310> information<00:06:05.820> and<00:06:06.030> this 00:06:06.140 --> 00:06:06.150 align:start position:0% receive actually information and this 00:06:06.150 --> 00:06:11.020 align:start position:0% receive actually information and this led<00:06:06.419> to<00:06:06.979> T<00:06:07.979> years<00:06:08.190> 75<00:06:08.760> proposal<00:06:09.630> which<00:06:09.750> was<00:06:09.930> in 00:06:11.020 --> 00:06:11.030 align:start position:0% led to T years 75 proposal which was in 00:06:11.030 --> 00:06:14.300 align:start position:0% led to T years 75 proposal which was in 2017<00:06:12.030> of<00:06:12.120> Touhou<00:06:12.330> actually<00:06:12.810> and<00:06:13.349> another 00:06:14.300 --> 00:06:14.310 align:start position:0% 2017 of Touhou actually and another 00:06:14.310 --> 00:06:16.159 align:start position:0% 2017 of Touhou actually and another thing<00:06:14.550> consider<00:06:15.090> the<00:06:15.240> seven<00:06:15.479> three<00:06:15.660> four 00:06:16.159 --> 00:06:16.169 align:start position:0% thing consider the seven three four 00:06:16.169 --> 00:06:19.310 align:start position:0% thing consider the seven three four it<00:06:16.560> was<00:06:16.830> rather<00:06:17.130> complex<00:06:17.639> but<00:06:18.570> I<00:06:18.630> think<00:06:18.780> what<00:06:19.289> I 00:06:19.310 --> 00:06:19.320 align:start position:0% it was rather complex but I think what I 00:06:19.320 --> 00:06:21.020 align:start position:0% it was rather complex but I think what I did<00:06:19.620> is<00:06:19.830> for<00:06:20.160> it<00:06:20.310> was<00:06:20.460> for<00:06:20.610> the<00:06:20.700> first<00:06:20.880> time 00:06:21.020 --> 00:06:21.030 align:start position:0% did is for it was for the first time 00:06:21.030 --> 00:06:22.940 align:start position:0% did is for it was for the first time showing<00:06:21.419> of<00:06:21.780> how<00:06:21.990> can<00:06:22.229> I<00:06:22.260> make<00:06:22.410> a<00:06:22.470> smartphone<00:06:22.830> a 00:06:22.940 --> 00:06:22.950 align:start position:0% showing of how can I make a smartphone a 00:06:22.950 --> 00:06:25.219 align:start position:0% showing of how can I make a smartphone a base<00:06:23.130> account<00:06:23.460> with<00:06:24.180> some<00:06:24.510> sort<00:06:24.780> of<00:06:24.960> key 00:06:25.219 --> 00:06:25.229 align:start position:0% base account with some sort of key 00:06:25.229 --> 00:06:27.600 align:start position:0% base account with some sort of key management<00:06:25.880> logic<00:06:26.880> in<00:06:27.090> some 00:06:27.600 --> 00:06:27.610 align:start position:0% management logic in some 00:06:27.610 --> 00:06:29.129 align:start position:0% management logic in some of<00:06:27.699> claims<00:06:28.120> that<00:06:28.419> can<00:06:28.599> attach<00:06:28.870> to<00:06:29.050> this 00:06:29.129 --> 00:06:29.139 align:start position:0% of claims that can attach to this 00:06:29.139 --> 00:06:31.559 align:start position:0% of claims that can attach to this account<00:06:29.409> and<00:06:29.819> it<00:06:30.819> kind<00:06:30.969> of<00:06:31.000> showed<00:06:31.270> the<00:06:31.389> full 00:06:31.559 --> 00:06:31.569 align:start position:0% account and it kind of showed the full 00:06:31.569 --> 00:06:33.360 align:start position:0% account and it kind of showed the full picture<00:06:31.840> of<00:06:31.990> how<00:06:32.319> can<00:06:32.590> this<00:06:32.740> look<00:06:32.979> like<00:06:33.159> in 00:06:33.360 --> 00:06:33.370 align:start position:0% picture of how can this look like in 00:06:33.370 --> 00:06:36.240 align:start position:0% picture of how can this look like in smart<00:06:33.669> enough<00:06:33.879> language<00:06:34.439> it<00:06:35.439> spurred<00:06:35.889> on<00:06:36.069> it 00:06:36.240 --> 00:06:36.250 align:start position:0% smart enough language it spurred on it 00:06:36.250 --> 00:06:37.379 align:start position:0% smart enough language it spurred on it kind<00:06:36.370> of<00:06:36.460> like<00:06:36.520> activated<00:06:37.180> the<00:06:37.270> whole 00:06:37.379 --> 00:06:37.389 align:start position:0% kind of like activated the whole 00:06:37.389 --> 00:06:39.029 align:start position:0% kind of like activated the whole discussion<00:06:37.719> around<00:06:38.080> our<00:06:38.439> identity 00:06:39.029 --> 00:06:39.039 align:start position:0% discussion around our identity 00:06:39.039 --> 00:06:41.219 align:start position:0% discussion around our identity blockchain<00:06:39.669> and<00:06:39.879> so<00:06:39.969> on<00:06:40.120> even<00:06:40.780> though<00:06:41.020> there 00:06:41.219 --> 00:06:41.229 align:start position:0% blockchain and so on even though there 00:06:41.229 --> 00:06:42.779 align:start position:0% blockchain and so on even though there were<00:06:41.379> pretty<00:06:41.710> set<00:06:41.800> I<00:06:41.979> was<00:06:42.219> like<00:06:42.370> you<00:06:42.520> fought<00:06:42.759> on 00:06:42.779 --> 00:06:42.789 align:start position:0% were pretty set I was like you fought on 00:06:42.789 --> 00:06:46.860 align:start position:0% were pretty set I was like you fought on others<00:06:43.180> who<00:06:43.840> did<00:06:44.259> that<00:06:44.409> before<00:06:44.800> me<00:06:45.009> I<00:06:45.810> kind<00:06:46.810> of 00:06:46.860 --> 00:06:46.870 align:start position:0% others who did that before me I kind of 00:06:46.870 --> 00:06:49.080 align:start position:0% others who did that before me I kind of like<00:06:47.050> proposed<00:06:47.560> this<00:06:47.770> out<00:06:48.009> of<00:06:48.400> the<00:06:48.550> feeling<00:06:48.939> of 00:06:49.080 --> 00:06:49.090 align:start position:0% like proposed this out of the feeling of 00:06:49.090 --> 00:06:51.600 align:start position:0% like proposed this out of the feeling of you<00:06:49.960> know<00:06:49.990> how<00:06:50.199> to<00:06:50.229> urge<00:06:50.560> to<00:06:50.860> do<00:06:51.009> it<00:06:51.129> like<00:06:51.400> I<00:06:51.490> had 00:06:51.600 --> 00:06:51.610 align:start position:0% you know how to urge to do it like I had 00:06:51.610 --> 00:06:54.119 align:start position:0% you know how to urge to do it like I had also<00:06:51.879> diverse<00:06:52.210> to<00:06:52.509> propose<00:06:53.080> you<00:06:53.199> see<00:06:53.379> 20<00:06:53.710> in<00:06:53.949> a 00:06:54.119 --> 00:06:54.129 align:start position:0% also diverse to propose you see 20 in a 00:06:54.129 --> 00:06:57.119 align:start position:0% also diverse to propose you see 20 in a more<00:06:54.340> public<00:06:54.550> place<00:06:55.349> rather<00:06:56.349> than<00:06:56.500> this<00:06:56.770> Vikki 00:06:57.119 --> 00:06:57.129 align:start position:0% more public place rather than this Vikki 00:06:57.129 --> 00:07:00.839 align:start position:0% more public place rather than this Vikki page<00:06:57.370> which<00:06:57.580> we<00:06:57.699> had<00:06:57.819> before<00:06:58.949> and<00:06:59.949> you<00:07:00.490> know<00:07:00.669> it 00:07:00.839 --> 00:07:00.849 align:start position:0% page which we had before and you know it 00:07:00.849 --> 00:07:02.279 align:start position:0% page which we had before and you know it kind<00:07:01.029> of<00:07:01.060> like<00:07:01.240> myself<00:07:01.599> the<00:07:01.689> right<00:07:01.779> timing<00:07:02.080> at 00:07:02.279 --> 00:07:02.289 align:start position:0% kind of like myself the right timing at 00:07:02.289 --> 00:07:05.179 align:start position:0% kind of like myself the right timing at the<00:07:02.379> time<00:07:02.590> and<00:07:02.800> it's<00:07:03.460> dirt<00:07:04.029> this<00:07:04.240> discussion 00:07:05.179 --> 00:07:05.189 align:start position:0% the time and it's dirt this discussion 00:07:05.189 --> 00:07:08.850 align:start position:0% the time and it's dirt this discussion so<00:07:06.189> all<00:07:07.090> of<00:07:07.360> this<00:07:07.509> came<00:07:07.870> you<00:07:08.020> know<00:07:08.050> people<00:07:08.710> say 00:07:08.850 --> 00:07:08.860 align:start position:0% so all of this came you know people say 00:07:08.860 --> 00:07:10.290 align:start position:0% so all of this came you know people say alright<00:07:09.159> right<00:07:09.430> there's<00:07:09.639> an<00:07:09.729> eternity<00:07:10.060> stand 00:07:10.290 --> 00:07:10.300 align:start position:0% alright right there's an eternity stand 00:07:10.300 --> 00:07:12.499 align:start position:0% alright right there's an eternity stand up<00:07:10.389> we<00:07:10.449> should<00:07:10.509> all<00:07:10.689> use<00:07:10.930> it<00:07:11.139> and<00:07:11.379> the<00:07:11.560> origin 00:07:12.499 --> 00:07:12.509 align:start position:0% up we should all use it and the origin 00:07:12.509 --> 00:07:15.719 align:start position:0% up we should all use it and the origin protocol<00:07:13.509> all<00:07:13.659> guys<00:07:13.960> launch<00:07:14.770> the<00:07:15.099> Alliance 00:07:15.719 --> 00:07:15.729 align:start position:0% protocol all guys launch the Alliance 00:07:15.729 --> 00:07:17.790 align:start position:0% protocol all guys launch the Alliance around<00:07:16.240> it<00:07:16.449> and<00:07:16.629> then<00:07:16.840> we<00:07:17.020> had<00:07:17.229> the<00:07:17.349> telecom 00:07:17.790 --> 00:07:17.800 align:start position:0% around it and then we had the telecom 00:07:17.800 --> 00:07:19.170 align:start position:0% around it and then we had the telecom channel<00:07:18.159> and<00:07:18.279> a<00:07:18.340> lot<00:07:18.490> of<00:07:18.610> people<00:07:18.849> join<00:07:19.029> this 00:07:19.170 --> 00:07:19.180 align:start position:0% channel and a lot of people join this 00:07:19.180 --> 00:07:22.339 align:start position:0% channel and a lot of people join this alliance<00:07:19.419> and<00:07:19.810> kind<00:07:20.650> of<00:07:20.710> everybody<00:07:21.159> like<00:07:21.279> an 00:07:22.339 --> 00:07:22.349 align:start position:0% alliance and kind of everybody like an 00:07:22.349 --> 00:07:27.659 align:start position:0% alliance and kind of everybody like an huddled<00:07:23.349> around<00:07:23.469> the<00:07:23.770> standard<00:07:24.960> but<00:07:26.669> not 00:07:27.659 --> 00:07:27.669 align:start position:0% huddled around the standard but not 00:07:27.669 --> 00:07:30.300 align:start position:0% huddled around the standard but not really<00:07:28.110> developed<00:07:29.110> it<00:07:29.199> further<00:07:29.500> or<00:07:29.889> actually 00:07:30.300 --> 00:07:30.310 align:start position:0% really developed it further or actually 00:07:30.310 --> 00:07:33.570 align:start position:0% really developed it further or actually started<00:07:30.789> to<00:07:30.939> use<00:07:31.150> it<00:07:31.180> so<00:07:31.900> one<00:07:32.860> thing<00:07:33.129> is<00:07:33.159> having 00:07:33.570 --> 00:07:33.580 align:start position:0% started to use it so one thing is having 00:07:33.580 --> 00:07:35.309 align:start position:0% started to use it so one thing is having a<00:07:33.729> standard<00:07:34.240> the<00:07:34.599> other<00:07:34.750> thing<00:07:34.960> is<00:07:35.050> having<00:07:35.199> an 00:07:35.309 --> 00:07:35.319 align:start position:0% a standard the other thing is having an 00:07:35.319 --> 00:07:37.320 align:start position:0% a standard the other thing is having an alliance<00:07:35.589> for<00:07:35.889> a<00:07:35.919> standard<00:07:36.370> but<00:07:37.180> they're 00:07:37.320 --> 00:07:37.330 align:start position:0% alliance for a standard but they're 00:07:37.330 --> 00:07:39.029 align:start position:0% alliance for a standard but they're actually<00:07:37.479> important<00:07:37.960> things<00:07:38.169> having<00:07:38.889> people 00:07:39.029 --> 00:07:39.039 align:start position:0% actually important things having people 00:07:39.039 --> 00:07:41.059 align:start position:0% actually important things having people use<00:07:39.279> it<00:07:39.490> you<00:07:39.699> know<00:07:39.819> and<00:07:40.060> make<00:07:40.360> sense<00:07:40.629> of<00:07:40.779> it 00:07:41.059 --> 00:07:41.069 align:start position:0% use it you know and make sense of it 00:07:41.069 --> 00:07:43.709 align:start position:0% use it you know and make sense of it there<00:07:42.069> are<00:07:42.250> also<00:07:42.490> problems<00:07:42.879> especially<00:07:43.360> with 00:07:43.709 --> 00:07:43.719 align:start position:0% there are also problems especially with 00:07:43.719 --> 00:07:45.510 align:start position:0% there are also problems especially with the<00:07:43.839> earlier<00:07:44.139> version<00:07:44.500> of<00:07:44.529> 7<00:07:44.830> to<00:07:44.919> 5<00:07:45.099> is<00:07:45.370> that 00:07:45.510 --> 00:07:45.520 align:start position:0% the earlier version of 7 to 5 is that 00:07:45.520 --> 00:07:47.820 align:start position:0% the earlier version of 7 to 5 is that it's<00:07:45.639> very<00:07:45.789> complex<00:07:46.060> and<00:07:46.569> it<00:07:47.199> is<00:07:47.440> very 00:07:47.820 --> 00:07:47.830 align:start position:0% it's very complex and it is very 00:07:47.830 --> 00:07:49.980 align:start position:0% it's very complex and it is very specific<00:07:48.639> also<00:07:49.029> and<00:07:49.270> how<00:07:49.419> you<00:07:49.479> do<00:07:49.779> key 00:07:49.980 --> 00:07:49.990 align:start position:0% specific also and how you do key 00:07:49.990 --> 00:07:51.420 align:start position:0% specific also and how you do key management<00:07:50.349> and<00:07:50.620> how<00:07:50.740> you<00:07:50.800> do<00:07:51.069> certain<00:07:51.279> things 00:07:51.420 --> 00:07:51.430 align:start position:0% management and how you do certain things 00:07:51.430 --> 00:07:54.089 align:start position:0% management and how you do certain things and<00:07:51.909> that<00:07:52.479> kind<00:07:52.690> of<00:07:52.779> led<00:07:53.080> a<00:07:53.110> little<00:07:53.409> bit<00:07:53.529> to<00:07:53.770> I 00:07:54.089 --> 00:07:54.099 align:start position:0% and that kind of led a little bit to I 00:07:54.099 --> 00:08:01.950 align:start position:0% and that kind of led a little bit to I would<00:07:55.060> say<00:07:56.550> a<00:07:57.550> stifled<00:07:59.219> progress<00:08:00.219> or<00:08:00.719> speed<00:08:01.719> of 00:08:01.950 --> 00:08:01.960 align:start position:0% would say a stifled progress or speed of 00:08:01.960 --> 00:08:05.969 align:start position:0% would say a stifled progress or speed of like<00:08:02.529> adopting<00:08:02.979> it<00:08:03.779> so<00:08:04.779> we<00:08:05.680> had<00:08:05.800> some 00:08:05.969 --> 00:08:05.979 align:start position:0% like adopting it so we had some 00:08:05.979 --> 00:08:08.070 align:start position:0% like adopting it so we had some discussions<00:08:06.669> with<00:08:06.819> people<00:08:07.300> there<00:08:07.449> we<00:08:07.750> came<00:08:07.930> up 00:08:08.070 --> 00:08:08.080 align:start position:0% discussions with people there we came up 00:08:08.080 --> 00:08:11.249 align:start position:0% discussions with people there we came up with<00:08:08.229> is<00:08:08.379> a<00:08:08.469> 7<00:08:08.770> to<00:08:08.860> 5<00:08:09.039> actually<00:08:09.580> Taylor<00:08:10.479> came 00:08:11.249 --> 00:08:11.259 align:start position:0% with is a 7 to 5 actually Taylor came 00:08:11.259 --> 00:08:13.110 align:start position:0% with is a 7 to 5 actually Taylor came that<00:08:11.740> to<00:08:11.919> me<00:08:12.039> is<00:08:12.159> that<00:08:12.279> hey<00:08:12.460> here<00:08:12.699> have<00:08:12.909> some 00:08:13.110 --> 00:08:13.120 align:start position:0% that to me is that hey here have some 00:08:13.120 --> 00:08:16.800 align:start position:0% that to me is that hey here have some ideas<00:08:13.479> and<00:08:13.599> let's<00:08:13.719> talk<00:08:13.870> about<00:08:13.930> it<00:08:14.610> and<00:08:15.810> that 00:08:16.800 --> 00:08:16.810 align:start position:0% ideas and let's talk about it and that 00:08:16.810 --> 00:08:20.670 align:start position:0% ideas and let's talk about it and that kind<00:08:16.990> of<00:08:17.110> led<00:08:17.409> to<00:08:17.680> the<00:08:18.069> year<00:08:18.550> 7<00:08:19.089> version<00:08:19.870> 5<00:08:20.259> by 00:08:20.670 --> 00:08:20.680 align:start position:0% kind of led to the year 7 version 5 by 00:08:20.680 --> 00:08:21.840 align:start position:0% kind of led to the year 7 version 5 by person 00:08:21.840 --> 00:08:21.850 align:start position:0% person 00:08:21.850 --> 00:08:25.500 align:start position:0% person -<00:08:22.590> and<00:08:23.639> the<00:08:24.639> interesting<00:08:24.970> thing<00:08:25.000> about<00:08:25.210> this 00:08:25.500 --> 00:08:25.510 align:start position:0% - and the interesting thing about this 00:08:25.510 --> 00:08:28.350 align:start position:0% - and the interesting thing about this it's<00:08:25.810> completely<00:08:26.080> made<00:08:26.650> it<00:08:26.860> simple<00:08:27.340> and<00:08:28.240> I 00:08:28.350 --> 00:08:28.360 align:start position:0% it's completely made it simple and I 00:08:28.360 --> 00:08:30.960 align:start position:0% it's completely made it simple and I think<00:08:28.630> you<00:08:28.750> know<00:08:28.870> what<00:08:29.080> if<00:08:29.230> one<00:08:29.620> thing<00:08:29.830> is<00:08:29.980> keys 00:08:30.960 --> 00:08:30.970 align:start position:0% think you know what if one thing is keys 00:08:30.970 --> 00:08:33.740 align:start position:0% think you know what if one thing is keys to<00:08:31.300> success<00:08:31.690> for<00:08:31.720> standard<00:08:32.409> it<00:08:32.620> is<00:08:33.190> simplicity 00:08:33.740 --> 00:08:33.750 align:start position:0% to success for standard it is simplicity 00:08:33.750 --> 00:08:36.959 align:start position:0% to success for standard it is simplicity so<00:08:34.750> easy<00:08:34.990> 20<00:08:35.440> was<00:08:35.710> kind<00:08:36.010> of<00:08:36.099> the<00:08:36.280> reason<00:08:36.640> why<00:08:36.909> it 00:08:36.959 --> 00:08:36.969 align:start position:0% so easy 20 was kind of the reason why it 00:08:36.969 --> 00:08:42.750 align:start position:0% so easy 20 was kind of the reason why it was<00:08:37.270> simple<00:08:38.310> to<00:08:39.310> use<00:08:39.520> and<00:08:40.380> is<00:08:41.380> 20<00:08:41.860> M<00:08:41.979> is<00:08:42.219> 75 00:08:42.750 --> 00:08:42.760 align:start position:0% was simple to use and is 20 M is 75 00:08:42.760 --> 00:08:45.210 align:start position:0% was simple to use and is 20 M is 75 version<00:08:43.090> -<00:08:43.240> in<00:08:43.360> my<00:08:43.539> opinion<00:08:43.690> is<00:08:44.200> also<00:08:44.740> key<00:08:45.040> of 00:08:45.210 --> 00:08:45.220 align:start position:0% version - in my opinion is also key of 00:08:45.220 --> 00:08:47.640 align:start position:0% version - in my opinion is also key of why<00:08:45.550> it<00:08:46.300> could<00:08:46.570> be<00:08:46.720> very<00:08:46.960> successful<00:08:47.170> because 00:08:47.640 --> 00:08:47.650 align:start position:0% why it could be very successful because 00:08:47.650 --> 00:08:51.570 align:start position:0% why it could be very successful because it's<00:08:47.980> so<00:08:48.130> simple<00:08:48.430> so<00:08:49.500> in<00:08:50.500> in<00:08:50.890> fact<00:08:51.190> of<00:08:51.430> what 00:08:51.570 --> 00:08:51.580 align:start position:0% it's so simple so in in fact of what 00:08:51.580 --> 00:08:52.980 align:start position:0% it's so simple so in in fact of what does<00:08:51.700> it<00:08:51.820> does<00:08:52.300> you<00:08:52.450> know<00:08:52.570> it's<00:08:52.660> like<00:08:52.780> okay 00:08:52.980 --> 00:08:52.990 align:start position:0% does it does you know it's like okay 00:08:52.990 --> 00:08:54.510 align:start position:0% does it does you know it's like okay this<00:08:53.170> is<00:08:53.470> a<00:08:53.500> smart<00:08:53.800> connect<00:08:54.100> which<00:08:54.250> has<00:08:54.400> an 00:08:54.510 --> 00:08:54.520 align:start position:0% this is a smart connect which has an 00:08:54.520 --> 00:08:56.310 align:start position:0% this is a smart connect which has an owner<00:08:54.760> and<00:08:55.000> it's<00:08:55.150> like<00:08:55.330> some<00:08:55.570> some<00:08:56.110> key<00:08:56.290> value 00:08:56.310 --> 00:08:56.320 align:start position:0% owner and it's like some some key value 00:08:56.320 --> 00:08:58.200 align:start position:0% owner and it's like some some key value store<00:08:56.890> in<00:08:57.040> there<00:08:57.280> and<00:08:57.520> there's<00:08:57.730> a<00:08:57.850> generic 00:08:58.200 --> 00:08:58.210 align:start position:0% store in there and there's a generic 00:08:58.210 --> 00:08:59.970 align:start position:0% store in there and there's a generic execute<00:08:58.690> function<00:08:58.870> so<00:08:59.290> it's<00:08:59.440> actually<00:08:59.620> not<00:08:59.920> a 00:08:59.970 --> 00:08:59.980 align:start position:0% execute function so it's actually not a 00:08:59.980 --> 00:09:03.900 align:start position:0% execute function so it's actually not a lot<00:09:00.250> of<00:09:00.280> things<00:09:02.430> text<00:09:03.430> part<00:09:03.700> is<00:09:03.820> actually 00:09:03.900 --> 00:09:03.910 align:start position:0% lot of things text part is actually 00:09:03.910 --> 00:09:06.210 align:start position:0% lot of things text part is actually important<00:09:04.570> because<00:09:05.020> that<00:09:05.410> allows<00:09:05.770> you<00:09:05.980> to<00:09:06.040> do 00:09:06.210 --> 00:09:06.220 align:start position:0% important because that allows you to do 00:09:06.220 --> 00:09:09.000 align:start position:0% important because that allows you to do a<00:09:06.250> lot<00:09:06.460> of<00:09:06.580> things<00:09:06.790> on<00:09:07.030> the<00:09:07.150> blockchain<00:09:07.860> so<00:09:08.860> but 00:09:09.000 --> 00:09:09.010 align:start position:0% a lot of things on the blockchain so but 00:09:09.010 --> 00:09:11.460 align:start position:0% a lot of things on the blockchain so but in<00:09:09.220> its<00:09:09.430> core<00:09:09.940> essence<00:09:10.480> what<00:09:10.780> is<00:09:10.930> years<00:09:11.290> in 00:09:11.460 --> 00:09:11.470 align:start position:0% in its core essence what is years in 00:09:11.470 --> 00:09:15.120 align:start position:0% in its core essence what is years in seven<00:09:11.830> to<00:09:12.010> five<00:09:12.250> and<00:09:12.700> not<00:09:13.690> forget<00:09:14.100> there<00:09:15.100> is 00:09:15.120 --> 00:09:15.130 align:start position:0% seven to five and not forget there is 00:09:15.130 --> 00:09:17.070 align:start position:0% seven to five and not forget there is more<00:09:15.550> to<00:09:15.880> standardize<00:09:16.360> on<00:09:16.390> top<00:09:16.780> of<00:09:16.930> that 00:09:17.070 --> 00:09:17.080 align:start position:0% more to standardize on top of that 00:09:17.080 --> 00:09:19.290 align:start position:0% more to standardize on top of that services<00:09:17.710> not<00:09:17.950> there<00:09:18.220> it's<00:09:18.460> not<00:09:18.610> they<00:09:18.790> all<00:09:19.120> in 00:09:19.290 --> 00:09:19.300 align:start position:0% services not there it's not they all in 00:09:19.300 --> 00:09:22.020 align:start position:0% services not there it's not they all in one<00:09:19.600> goal<00:09:20.020> the<00:09:20.170> solution<00:09:20.650> but<00:09:21.370> it<00:09:21.580> is<00:09:21.700> a<00:09:21.730> very 00:09:22.020 --> 00:09:22.030 align:start position:0% one goal the solution but it is a very 00:09:22.030 --> 00:09:24.120 align:start position:0% one goal the solution but it is a very key<00:09:22.240> piece<00:09:22.420> because<00:09:22.960> it<00:09:23.080> is<00:09:23.170> the<00:09:23.320> core<00:09:23.680> piece 00:09:24.120 --> 00:09:24.130 align:start position:0% key piece because it is the core piece 00:09:24.130 --> 00:09:29.579 align:start position:0% key piece because it is the core piece of<00:09:24.720> a<00:09:25.720> on<00:09:26.260> chain<00:09:26.530> account<00:09:27.390> so<00:09:28.390> basically<00:09:28.780> we 00:09:29.579 --> 00:09:29.589 align:start position:0% of a on chain account so basically we 00:09:29.589 --> 00:09:32.670 align:start position:0% of a on chain account so basically we store<00:09:29.860> everything<00:09:30.010> currently<00:09:30.760> on<00:09:31.000> keys<00:09:31.570> if<00:09:31.960> we 00:09:32.670 --> 00:09:32.680 align:start position:0% store everything currently on keys if we 00:09:32.680 --> 00:09:35.370 align:start position:0% store everything currently on keys if we replace<00:09:33.130> this<00:09:33.400> by<00:09:33.730> a<00:09:34.030> smart<00:09:34.930> kind<00:09:35.080> of<00:09:35.230> base 00:09:35.370 --> 00:09:35.380 align:start position:0% replace this by a smart kind of base 00:09:35.380 --> 00:09:37.829 align:start position:0% replace this by a smart kind of base account<00:09:35.890> we<00:09:36.370> can<00:09:36.400> add<00:09:36.880> a<00:09:36.910> few<00:09:37.030> properties 00:09:37.829 --> 00:09:37.839 align:start position:0% account we can add a few properties 00:09:37.839 --> 00:09:41.280 align:start position:0% account we can add a few properties which<00:09:38.500> we<00:09:38.650> didn't<00:09:38.950> have<00:09:39.160> before<00:09:39.370> and<00:09:40.080> one<00:09:41.080> is 00:09:41.280 --> 00:09:41.290 align:start position:0% which we didn't have before and one is 00:09:41.290 --> 00:09:44.040 align:start position:0% which we didn't have before and one is obviously<00:09:41.710> I<00:09:42.100> can<00:09:43.030> use<00:09:43.300> my<00:09:43.510> account<00:09:43.780> from 00:09:44.040 --> 00:09:44.050 align:start position:0% obviously I can use my account from 00:09:44.050 --> 00:09:46.920 align:start position:0% obviously I can use my account from different<00:09:44.530> places<00:09:45.339> which<00:09:46.030> is<00:09:46.060> exactly<00:09:46.660> right 00:09:46.920 --> 00:09:46.930 align:start position:0% different places which is exactly right 00:09:46.930 --> 00:09:49.230 align:start position:0% different places which is exactly right now<00:09:47.110> the<00:09:47.170> problem<00:09:47.650> so<00:09:48.250> we<00:09:48.400> all<00:09:48.580> end<00:09:48.820> up<00:09:48.940> having 00:09:49.230 --> 00:09:49.240 align:start position:0% now the problem so we all end up having 00:09:49.240 --> 00:09:51.390 align:start position:0% now the problem so we all end up having met<00:09:49.390> amassed<00:09:49.720> may<00:09:50.440> be<00:09:50.500> having<00:09:50.830> some<00:09:50.950> lecture 00:09:51.390 --> 00:09:51.400 align:start position:0% met amassed may be having some lecture 00:09:51.400 --> 00:09:53.910 align:start position:0% met amassed may be having some lecture maybe<00:09:52.089> having<00:09:52.450> some<00:09:52.630> other<00:09:52.780> five<00:09:53.170> apps<00:09:53.440> and 00:09:53.910 --> 00:09:53.920 align:start position:0% maybe having some other five apps and 00:09:53.920 --> 00:09:55.320 align:start position:0% maybe having some other five apps and what<00:09:54.339> happens<00:09:54.760> we<00:09:54.910> all<00:09:55.089> use<00:09:55.300> different 00:09:55.320 --> 00:09:55.330 align:start position:0% what happens we all use different 00:09:55.330 --> 00:09:57.030 align:start position:0% what happens we all use different accounts<00:09:56.110> and<00:09:56.230> all<00:09:56.320> of<00:09:56.440> them<00:09:56.620> have<00:09:56.890> different 00:09:57.030 --> 00:09:57.040 align:start position:0% accounts and all of them have different 00:09:57.040 --> 00:09:57.630 align:start position:0% accounts and all of them have different amounts 00:09:57.630 --> 00:09:57.640 align:start position:0% amounts 00:09:57.640 --> 00:10:00.030 align:start position:0% amounts ether<00:09:57.970> or<00:09:58.210> assets<00:09:58.660> on<00:09:58.780> all<00:09:58.960> of<00:09:59.020> them<00:09:59.230> and<00:09:59.500> some 00:10:00.030 --> 00:10:00.040 align:start position:0% ether or assets on all of them and some 00:10:00.040 --> 00:10:01.260 align:start position:0% ether or assets on all of them and some we<00:10:00.130> don't<00:10:00.310> even<00:10:00.430> know<00:10:00.580> that<00:10:00.760> anymore<00:10:00.970> that<00:10:01.180> we 00:10:01.260 --> 00:10:01.270 align:start position:0% we don't even know that anymore that we 00:10:01.270 --> 00:10:06.420 align:start position:0% we don't even know that anymore that we have<00:10:01.510> and<00:10:01.860> we<00:10:02.860> tend<00:10:03.130> to<00:10:03.250> be<00:10:03.460> not<00:10:04.240> use<00:10:04.600> our<00:10:05.430> own 00:10:06.420 --> 00:10:06.430 align:start position:0% have and we tend to be not use our own 00:10:06.430 --> 00:10:08.790 align:start position:0% have and we tend to be not use our own chain<00:10:06.940> accounts<00:10:07.420> often<00:10:07.870> right<00:10:08.230> you<00:10:08.620> basically 00:10:08.790 --> 00:10:08.800 align:start position:0% chain accounts often right you basically 00:10:08.800 --> 00:10:12.540 align:start position:0% chain accounts often right you basically have<00:10:09.100> one<00:10:09.220> account<00:10:09.580> per<00:10:09.700> app<00:10:10.000> which<00:10:10.870> can<00:10:11.550> be 00:10:12.540 --> 00:10:12.550 align:start position:0% have one account per app which can be 00:10:12.550 --> 00:10:14.850 align:start position:0% have one account per app which can be useful<00:10:12.700> it<00:10:13.270> can<00:10:13.540> be<00:10:13.660> very<00:10:13.930> hard<00:10:14.260> to<00:10:14.410> manage 00:10:14.850 --> 00:10:14.860 align:start position:0% useful it can be very hard to manage 00:10:14.860 --> 00:10:16.270 align:start position:0% useful it can be very hard to manage especially<00:10:15.070> when<00:10:15.490> it<00:10:15.610> comes<00:10:15.700> around 00:10:16.270 --> 00:10:16.280 align:start position:0% especially when it comes around 00:10:16.280 --> 00:10:18.190 align:start position:0% especially when it comes around dealing<00:10:16.760> with<00:10:16.790> a<00:10:17.030> different<00:10:17.390> type<00:10:17.420> of<00:10:17.600> games 00:10:18.190 --> 00:10:18.200 align:start position:0% dealing with a different type of games 00:10:18.200 --> 00:10:20.950 align:start position:0% dealing with a different type of games or<00:10:18.560> like<00:10:18.770> one<00:10:19.460> thing<00:10:19.550> to<00:10:19.730> access<00:10:19.910> your<00:10:20.210> your 00:10:20.950 --> 00:10:20.960 align:start position:0% or like one thing to access your your 00:10:20.960 --> 00:10:24.310 align:start position:0% or like one thing to access your your account<00:10:21.530> in<00:10:21.770> different<00:10:22.040> places<00:10:22.190> so<00:10:22.840> the<00:10:23.840> spot 00:10:24.310 --> 00:10:24.320 align:start position:0% account in different places so the spot 00:10:24.320 --> 00:10:26.770 align:start position:0% account in different places so the spot kinda<00:10:24.530> basic<00:10:24.860> challenge<00:10:25.360> basically<00:10:26.360> allows 00:10:26.770 --> 00:10:26.780 align:start position:0% kinda basic challenge basically allows 00:10:26.780 --> 00:10:29.800 align:start position:0% kinda basic challenge basically allows you<00:10:27.170> to<00:10:27.590> manage<00:10:27.890> it<00:10:28.280> because<00:10:29.210> it<00:10:29.540> has<00:10:29.630> this 00:10:29.800 --> 00:10:29.810 align:start position:0% you to manage it because it has this 00:10:29.810 --> 00:10:32.920 align:start position:0% you to manage it because it has this owner<00:10:30.110> address<00:10:30.620> so<00:10:31.160> owner<00:10:31.430> means<00:10:31.880> that<00:10:32.540> is<00:10:32.660> one 00:10:32.920 --> 00:10:32.930 align:start position:0% owner address so owner means that is one 00:10:32.930 --> 00:10:35.710 align:start position:0% owner address so owner means that is one address<00:10:33.380> that<00:10:33.560> can<00:10:33.740> control<00:10:34.130> this<00:10:34.720> account 00:10:35.710 --> 00:10:35.720 align:start position:0% address that can control this account 00:10:35.720 --> 00:10:38.770 align:start position:0% address that can control this account and<00:10:36.140> this<00:10:36.650> one<00:10:37.490> address<00:10:37.820> could<00:10:38.090> obviously<00:10:38.450> be 00:10:38.770 --> 00:10:38.780 align:start position:0% and this one address could obviously be 00:10:38.780 --> 00:10:41.500 align:start position:0% and this one address could obviously be a<00:10:38.810> simple<00:10:39.290> key<00:10:39.500> it<00:10:40.190> could<00:10:40.430> be<00:10:40.550> a<00:10:40.580> very<00:10:40.760> simple<00:10:41.030> a 00:10:41.500 --> 00:10:41.510 align:start position:0% a simple key it could be a very simple a 00:10:41.510 --> 00:10:43.720 align:start position:0% a simple key it could be a very simple a private<00:10:42.350> key<00:10:42.530> which<00:10:42.770> would<00:10:43.070> even<00:10:43.370> the<00:10:43.400> first 00:10:43.720 --> 00:10:43.730 align:start position:0% private key which would even the first 00:10:43.730 --> 00:10:45.910 align:start position:0% private key which would even the first one<00:10:44.000> you<00:10:44.120> generate<00:10:44.540> in<00:10:44.720> your<00:10:44.750> application<00:10:45.560> so 00:10:45.910 --> 00:10:45.920 align:start position:0% one you generate in your application so 00:10:45.920 --> 00:10:48.880 align:start position:0% one you generate in your application so think<00:10:46.280> of<00:10:46.430> application<00:10:47.420> starts<00:10:47.900> it<00:10:48.380> generates 00:10:48.880 --> 00:10:48.890 align:start position:0% think of application starts it generates 00:10:48.890 --> 00:10:50.800 align:start position:0% think of application starts it generates a<00:10:48.980> key<00:10:49.130> under<00:10:49.340> the<00:10:49.370> hood<00:10:49.610> this<00:10:50.240> key<00:10:50.420> does<00:10:50.630> not 00:10:50.800 --> 00:10:50.810 align:start position:0% a key under the hood this key does not 00:10:50.810 --> 00:10:52.630 align:start position:0% a key under the hood this key does not need<00:10:50.990> to<00:10:51.140> be<00:10:51.170> safe<00:10:51.500> because<00:10:52.010> it<00:10:52.400> is<00:10:52.550> a 00:10:52.630 --> 00:10:52.640 align:start position:0% need to be safe because it is a 00:10:52.640 --> 00:10:55.270 align:start position:0% need to be safe because it is a throwaway<00:10:53.030> key<00:10:53.510> you<00:10:53.870> just<00:10:54.140> use<00:10:54.380> initially<00:10:55.040> and 00:10:55.270 --> 00:10:55.280 align:start position:0% throwaway key you just use initially and 00:10:55.280 --> 00:10:59.560 align:start position:0% throwaway key you just use initially and the<00:10:56.000> moment<00:10:56.360> you<00:10:56.390> get<00:10:56.570> more<00:10:56.780> value<00:10:56.960> to<00:10:57.320> it<00:10:58.570> you 00:10:59.560 --> 00:10:59.570 align:start position:0% the moment you get more value to it you 00:10:59.570 --> 00:11:01.360 align:start position:0% the moment you get more value to it you can<00:10:59.750> add<00:10:59.870> more<00:11:00.020> make<00:11:00.260> it<00:11:00.290> more<00:11:00.560> secure<00:11:00.920> so<00:11:01.190> good 00:11:01.360 --> 00:11:01.370 align:start position:0% can add more make it more secure so good 00:11:01.370 --> 00:11:03.220 align:start position:0% can add more make it more secure so good you<00:11:01.550> could<00:11:01.670> even<00:11:01.910> think<00:11:02.060> of<00:11:02.360> taking<00:11:02.750> this<00:11:02.960> key 00:11:03.220 --> 00:11:03.230 align:start position:0% you could even think of taking this key 00:11:03.230 --> 00:11:05.710 align:start position:0% you could even think of taking this key and<00:11:03.410> send<00:11:03.710> it<00:11:03.890> via<00:11:03.920> email<00:11:04.520> as<00:11:04.850> a<00:11:05.330> backup 00:11:05.710 --> 00:11:05.720 align:start position:0% and send it via email as a backup 00:11:05.720 --> 00:11:08.650 align:start position:0% and send it via email as a backup process<00:11:06.530> so<00:11:07.070> that<00:11:07.340> in<00:11:07.430> case<00:11:07.640> you<00:11:07.910> look<00:11:08.060> loose 00:11:08.650 --> 00:11:08.660 align:start position:0% process so that in case you look loose 00:11:08.660 --> 00:11:10.450 align:start position:0% process so that in case you look loose yet<00:11:08.870> on<00:11:09.140> the<00:11:09.230> phone<00:11:09.470> in<00:11:09.770> the<00:11:09.890> next<00:11:10.100> few<00:11:10.280> days 00:11:10.450 --> 00:11:10.460 align:start position:0% yet on the phone in the next few days 00:11:10.460 --> 00:11:13.120 align:start position:0% yet on the phone in the next few days you<00:11:11.240> can<00:11:11.390> easily<00:11:11.630> reassociate<00:11:12.350> your<00:11:12.800> previous 00:11:13.120 --> 00:11:13.130 align:start position:0% you can easily reassociate your previous 00:11:13.130 --> 00:11:16.540 align:start position:0% you can easily reassociate your previous account<00:11:13.430> I<00:11:13.820> mean<00:11:14.480> if<00:11:15.260> we<00:11:15.440> think<00:11:15.470> about<00:11:15.740> it<00:11:15.890> we 00:11:16.540 --> 00:11:16.550 align:start position:0% account I mean if we think about it we 00:11:16.550 --> 00:11:18.700 align:start position:0% account I mean if we think about it we use<00:11:16.820> email<00:11:17.030> today<00:11:17.450> for<00:11:17.750> we<00:11:18.170> saw<00:11:18.350> as<00:11:18.470> setting 00:11:18.700 --> 00:11:18.710 align:start position:0% use email today for we saw as setting 00:11:18.710 --> 00:11:20.140 align:start position:0% use email today for we saw as setting our<00:11:18.800> password<00:11:19.190> all<00:11:19.310> the<00:11:19.400> time<00:11:19.610> right<00:11:19.910> that's 00:11:20.140 --> 00:11:20.150 align:start position:0% our password all the time right that's 00:11:20.150 --> 00:11:23.350 align:start position:0% our password all the time right that's our<00:11:20.390> security<00:11:20.750> measure<00:11:21.260> we<00:11:21.680> have<00:11:21.710> so<00:11:22.580> email 00:11:23.350 --> 00:11:23.360 align:start position:0% our security measure we have so email 00:11:23.360 --> 00:11:24.880 align:start position:0% our security measure we have so email it's<00:11:23.570> silly<00:11:23.870> if<00:11:24.020> you<00:11:24.110> have<00:11:24.200> access<00:11:24.470> to<00:11:24.500> emails 00:11:24.880 --> 00:11:24.890 align:start position:0% it's silly if you have access to emails 00:11:24.890 --> 00:11:26.800 align:start position:0% it's silly if you have access to emails you<00:11:25.130> have<00:11:25.190> access<00:11:25.670> to<00:11:25.760> everybody's<00:11:26.150> accounts 00:11:26.800 --> 00:11:26.810 align:start position:0% you have access to everybody's accounts 00:11:26.810 --> 00:11:29.320 align:start position:0% you have access to everybody's accounts the<00:11:27.589> email<00:11:27.830> is<00:11:27.950> the<00:11:28.070> username<00:11:28.460> and<00:11:28.790> the<00:11:29.150> way<00:11:29.270> to 00:11:29.320 --> 00:11:29.330 align:start position:0% the email is the username and the way to 00:11:29.330 --> 00:11:31.300 align:start position:0% the email is the username and the way to reset<00:11:29.630> the<00:11:29.839> password<00:11:30.020> that's<00:11:30.950> already<00:11:31.160> a 00:11:31.300 --> 00:11:31.310 align:start position:0% reset the password that's already a 00:11:31.310 --> 00:11:34.060 align:start position:0% reset the password that's already a funny<00:11:31.580> thing<00:11:32.500> so<00:11:33.500> that's<00:11:33.650> the<00:11:33.830> security 00:11:34.060 --> 00:11:34.070 align:start position:0% funny thing so that's the security 00:11:34.070 --> 00:11:35.800 align:start position:0% funny thing so that's the security measure<00:11:34.460> we<00:11:34.640> have<00:11:34.850> so<00:11:35.089> why<00:11:35.270> not<00:11:35.420> sending<00:11:35.720> a 00:11:35.800 --> 00:11:35.810 align:start position:0% measure we have so why not sending a 00:11:35.810 --> 00:11:37.990 align:start position:0% measure we have so why not sending a private<00:11:35.990> key<00:11:36.290> or<00:11:36.500> some<00:11:37.160> kind<00:11:37.400> of<00:11:37.460> generated 00:11:37.990 --> 00:11:38.000 align:start position:0% private key or some kind of generated 00:11:38.000 --> 00:11:41.380 align:start position:0% private key or some kind of generated link<00:11:38.210> or<00:11:38.450> so<00:11:39.250> directly<00:11:40.250> to<00:11:40.400> this<00:11:40.490> email<00:11:40.640> the 00:11:41.380 --> 00:11:41.390 align:start position:0% link or so directly to this email the 00:11:41.390 --> 00:11:43.210 align:start position:0% link or so directly to this email the moment<00:11:41.839> you<00:11:41.930> can<00:11:42.080> actually<00:11:42.230> value<00:11:42.890> on<00:11:43.040> your 00:11:43.210 --> 00:11:43.220 align:start position:0% moment you can actually value on your 00:11:43.220 --> 00:11:45.280 align:start position:0% moment you can actually value on your account<00:11:43.580> or<00:11:43.910> you<00:11:44.030> use<00:11:44.270> it<00:11:44.480> more<00:11:44.630> often<00:11:44.870> for 00:11:45.280 --> 00:11:45.290 align:start position:0% account or you use it more often for 00:11:45.290 --> 00:11:47.710 align:start position:0% account or you use it more often for something<00:11:45.800> then<00:11:46.550> you<00:11:46.730> can<00:11:46.940> actually<00:11:47.089> attach<00:11:47.540> a 00:11:47.710 --> 00:11:47.720 align:start position:0% something then you can actually attach a 00:11:47.720 --> 00:11:50.380 align:start position:0% something then you can actually attach a movie<00:11:47.900> sick<00:11:48.170> and<00:11:48.380> have<00:11:48.710> that<00:11:48.890> multi-sig<00:11:49.580> being 00:11:50.380 --> 00:11:50.390 align:start position:0% movie sick and have that multi-sig being 00:11:50.390 --> 00:11:52.960 align:start position:0% movie sick and have that multi-sig being the<00:11:51.110> control<00:11:51.530> of<00:11:51.560> the<00:11:51.830> account<00:11:52.100> and<00:11:52.520> that 00:11:52.960 --> 00:11:52.970 align:start position:0% the control of the account and that 00:11:52.970 --> 00:11:56.880 align:start position:0% the control of the account and that myristic<00:11:53.360> could<00:11:53.839> Ignasi<00:11:54.290> safe<00:11:54.650> it<00:11:55.400> could<00:11:55.640> be<00:11:55.850> a 00:11:56.880 --> 00:11:56.890 align:start position:0% myristic could Ignasi safe it could be a 00:11:56.890 --> 00:11:59.530 align:start position:0% myristic could Ignasi safe it could be a complex<00:11:57.890> permission<00:11:58.339> contract<00:11:58.850> that<00:11:59.180> allows 00:11:59.530 --> 00:11:59.540 align:start position:0% complex permission contract that allows 00:11:59.540 --> 00:12:01.720 align:start position:0% complex permission contract that allows certain<00:12:00.380> parties<00:12:01.010> to<00:12:01.220> do<00:12:01.339> certain<00:12:01.580> things 00:12:01.720 --> 00:12:01.730 align:start position:0% certain parties to do certain things 00:12:01.730 --> 00:12:03.790 align:start position:0% certain parties to do certain things through<00:12:02.540> this<00:12:02.690> seven<00:12:02.990> to<00:12:03.110> five<00:12:03.260> account<00:12:03.620> and 00:12:03.790 --> 00:12:03.800 align:start position:0% through this seven to five account and 00:12:03.800 --> 00:12:06.130 align:start position:0% through this seven to five account and others<00:12:04.100> not<00:12:04.730> so<00:12:04.970> think<00:12:05.390> of<00:12:05.540> like<00:12:05.780> you<00:12:05.960> are<00:12:06.110> a 00:12:06.130 --> 00:12:06.140 align:start position:0% others not so think of like you are a 00:12:06.140 --> 00:12:08.350 align:start position:0% others not so think of like you are a company<00:12:06.650> and<00:12:06.860> the<00:12:07.339> seven<00:12:07.640> to<00:12:07.730> five<00:12:07.940> is<00:12:08.210> your 00:12:08.350 --> 00:12:08.360 align:start position:0% company and the seven to five is your 00:12:08.360 --> 00:12:11.440 align:start position:0% company and the seven to five is your company's<00:12:08.870> official<00:12:09.290> address<00:12:09.740> if<00:12:10.460> you<00:12:11.030> have<00:12:11.240> a 00:12:11.440 --> 00:12:11.450 align:start position:0% company's official address if you have a 00:12:11.450 --> 00:12:13.000 align:start position:0% company's official address if you have a commissioned<00:12:11.930> contract<00:12:12.320> where<00:12:12.470> the<00:12:12.500> intern 00:12:13.000 --> 00:12:13.010 align:start position:0% commissioned contract where the intern 00:12:13.010 --> 00:12:14.950 align:start position:0% commissioned contract where the intern can<00:12:13.400> actually<00:12:13.820> talk<00:12:14.089> through<00:12:14.450> the<00:12:14.660> official 00:12:14.950 --> 00:12:14.960 align:start position:0% can actually talk through the official 00:12:14.960 --> 00:12:17.410 align:start position:0% can actually talk through the official address<00:12:15.380> but<00:12:16.280> only<00:12:16.640> can<00:12:16.820> talk<00:12:16.970> to<00:12:17.150> certain 00:12:17.410 --> 00:12:17.420 align:start position:0% address but only can talk to certain 00:12:17.420 --> 00:12:21.040 align:start position:0% address but only can talk to certain accounts<00:12:18.200> or<00:12:18.410> certain<00:12:19.270> smart<00:12:20.270> contracts<00:12:20.839> and 00:12:21.040 --> 00:12:21.050 align:start position:0% accounts or certain smart contracts and 00:12:21.050 --> 00:12:23.980 align:start position:0% accounts or certain smart contracts and call<00:12:22.040> only<00:12:22.280> certain<00:12:22.610> functions<00:12:23.060> you<00:12:23.720> can<00:12:23.870> have 00:12:23.980 --> 00:12:23.990 align:start position:0% call only certain functions you can have 00:12:23.990 --> 00:12:24.700 align:start position:0% call only certain functions you can have your<00:12:24.110> intern 00:12:24.700 --> 00:12:24.710 align:start position:0% your intern 00:12:24.710 --> 00:12:26.769 align:start position:0% your intern we<00:12:24.800> use<00:12:24.980> the<00:12:25.370> official<00:12:25.760> account<00:12:25.820> without<00:12:26.450> any 00:12:26.769 --> 00:12:26.779 align:start position:0% we use the official account without any 00:12:26.779 --> 00:12:30.310 align:start position:0% we use the official account without any kind<00:12:27.020> of<00:12:27.140> a<00:12:27.520> security<00:12:28.520> loss<00:12:28.670> or<00:12:29.630> it<00:12:30.050> could<00:12:30.200> be 00:12:30.310 --> 00:12:30.320 align:start position:0% kind of a security loss or it could be 00:12:30.320 --> 00:12:32.980 align:start position:0% kind of a security loss or it could be just<00:12:30.560> a<00:12:30.740> simple<00:12:30.920> would<00:12:31.190> be<00:12:31.310> sick<00:12:31.490> or<00:12:31.910> on<00:12:32.600> top<00:12:32.930> of 00:12:32.980 --> 00:12:32.990 align:start position:0% just a simple would be sick or on top of 00:12:32.990 --> 00:12:35.260 align:start position:0% just a simple would be sick or on top of this<00:12:33.260> this<00:12:33.620> disallows<00:12:34.250> also<00:12:34.700> social<00:12:35.000> recovery 00:12:35.260 --> 00:12:35.270 align:start position:0% this this disallows also social recovery 00:12:35.270 --> 00:12:36.940 align:start position:0% this this disallows also social recovery schemes<00:12:35.870> and<00:12:36.050> whatever<00:12:36.200> else<00:12:36.560> because 00:12:36.940 --> 00:12:36.950 align:start position:0% schemes and whatever else because 00:12:36.950 --> 00:12:39.220 align:start position:0% schemes and whatever else because whatever<00:12:37.130> we<00:12:37.430> come<00:12:37.610> up<00:12:37.670> with<00:12:37.970> better<00:12:38.810> ways<00:12:38.930> of 00:12:39.220 --> 00:12:39.230 align:start position:0% whatever we come up with better ways of 00:12:39.230 --> 00:12:41.889 align:start position:0% whatever we come up with better ways of managing<00:12:39.290> keys<00:12:40.220> we<00:12:40.820> can<00:12:40.850> attach<00:12:41.360> to<00:12:41.390> the<00:12:41.690> same 00:12:41.889 --> 00:12:41.899 align:start position:0% managing keys we can attach to the same 00:12:41.899 --> 00:12:43.810 align:start position:0% managing keys we can attach to the same existing<00:12:42.410> account<00:12:42.770> or<00:12:42.980> to<00:12:43.010> multiple<00:12:43.310> of<00:12:43.580> doors 00:12:43.810 --> 00:12:43.820 align:start position:0% existing account or to multiple of doors 00:12:43.820 --> 00:12:48.460 align:start position:0% existing account or to multiple of doors the<00:12:45.190> important<00:12:46.190> thing<00:12:46.370> also<00:12:46.550> is<00:12:46.940> we<00:12:47.810> can<00:12:48.170> have 00:12:48.460 --> 00:12:48.470 align:start position:0% the important thing also is we can have 00:12:48.470 --> 00:12:51.160 align:start position:0% the important thing also is we can have meta<00:12:49.250> transactions<00:12:49.940> we<00:12:50.270> can<00:12:50.480> use<00:12:50.720> the<00:12:50.990> gas 00:12:51.160 --> 00:12:51.170 align:start position:0% meta transactions we can use the gas 00:12:51.170 --> 00:12:52.930 align:start position:0% meta transactions we can use the gas station<00:12:51.589> network<00:12:51.950> or<00:12:52.160> other<00:12:52.399> related 00:12:52.930 --> 00:12:52.940 align:start position:0% station network or other related 00:12:52.940 --> 00:12:56.079 align:start position:0% station network or other related services<00:12:53.149> within<00:12:54.110> those<00:12:54.850> key<00:12:55.850> managed 00:12:56.079 --> 00:12:56.089 align:start position:0% services within those key managed 00:12:56.089 --> 00:12:58.870 align:start position:0% services within those key managed accounts<00:12:56.720> and<00:12:56.870> suddenly<00:12:57.589> completely<00:12:58.370> hide 00:12:58.870 --> 00:12:58.880 align:start position:0% accounts and suddenly completely hide 00:12:58.880 --> 00:13:01.920 align:start position:0% accounts and suddenly completely hide the<00:12:59.089> fact<00:12:59.330> that<00:12:59.420> a<00:12:59.660> server<00:12:59.990> a<00:13:00.440> fee<00:13:01.250> to<00:13:01.279> be<00:13:01.490> paid 00:13:01.920 --> 00:13:01.930 align:start position:0% the fact that a server a fee to be paid 00:13:01.930 --> 00:13:05.320 align:start position:0% the fact that a server a fee to be paid the<00:13:02.930> future<00:13:03.380> of<00:13:03.830> blockchain<00:13:04.490> should<00:13:04.910> be<00:13:05.120> the 00:13:05.320 --> 00:13:05.330 align:start position:0% the future of blockchain should be the 00:13:05.330 --> 00:13:07.199 align:start position:0% the future of blockchain should be the way<00:13:05.510> of<00:13:05.690> how<00:13:05.870> the<00:13:05.930> web<00:13:06.140> works<00:13:06.230> today 00:13:07.199 --> 00:13:07.209 align:start position:0% way of how the web works today 00:13:07.209 --> 00:13:10.150 align:start position:0% way of how the web works today meaning<00:13:08.209> the<00:13:08.779> application<00:13:09.290> developers<00:13:09.800> or 00:13:10.150 --> 00:13:10.160 align:start position:0% meaning the application developers or 00:13:10.160 --> 00:13:12.730 align:start position:0% meaning the application developers or the<00:13:10.220> company<00:13:10.880> who<00:13:10.970> does<00:13:11.149> it<00:13:11.330> should<00:13:11.630> build<00:13:12.080> the 00:13:12.730 --> 00:13:12.740 align:start position:0% the company who does it should build the 00:13:12.740 --> 00:13:16.389 align:start position:0% the company who does it should build the I<00:13:13.130> should<00:13:14.029> pay<00:13:14.270> for<00:13:14.500> the<00:13:15.500> usage<00:13:15.890> at<00:13:16.040> least<00:13:16.250> to 00:13:16.389 --> 00:13:16.399 align:start position:0% I should pay for the usage at least to 00:13:16.399 --> 00:13:19.800 align:start position:0% I should pay for the usage at least to some<00:13:16.580> degree<00:13:16.779> until<00:13:17.779> there's<00:13:18.200> a<00:13:18.260> way<00:13:18.470> to 00:13:19.800 --> 00:13:19.810 align:start position:0% some degree until there's a way to 00:13:19.810 --> 00:13:23.139 align:start position:0% some degree until there's a way to recoup<00:13:20.810> the<00:13:20.959> payment<00:13:21.380> I<00:13:21.620> mean<00:13:22.459> today<00:13:22.940> nobody 00:13:23.139 --> 00:13:23.149 align:start position:0% recoup the payment I mean today nobody 00:13:23.149 --> 00:13:25.090 align:start position:0% recoup the payment I mean today nobody is<00:13:23.450> paying<00:13:23.660> for<00:13:23.930> service<00:13:24.290> of<00:13:24.440> applications 00:13:25.090 --> 00:13:25.100 align:start position:0% is paying for service of applications 00:13:25.100 --> 00:13:27.190 align:start position:0% is paying for service of applications that<00:13:25.220> we<00:13:25.550> just<00:13:25.820> download<00:13:26.480> and<00:13:26.720> use<00:13:26.870> them<00:13:27.050> all 00:13:27.190 --> 00:13:27.200 align:start position:0% that we just download and use them all 00:13:27.200 --> 00:13:29.260 align:start position:0% that we just download and use them all the<00:13:27.230> time<00:13:27.290> it<00:13:28.279> should<00:13:28.580> be<00:13:28.610> the<00:13:28.760> same<00:13:28.910> with<00:13:29.120> web 00:13:29.260 --> 00:13:29.270 align:start position:0% the time it should be the same with web 00:13:29.270 --> 00:13:34.150 align:start position:0% the time it should be the same with web 3<00:13:31.420> the<00:13:32.420> relay<00:13:33.110> protection<00:13:33.470> service<00:13:34.070> is 00:13:34.150 --> 00:13:34.160 align:start position:0% 3 the relay protection service is 00:13:34.160 --> 00:13:36.240 align:start position:0% 3 the relay protection service is actually<00:13:34.430> the<00:13:34.550> key<00:13:34.760> piece<00:13:35.029> to<00:13:35.360> make<00:13:35.510> it<00:13:35.660> easy 00:13:36.240 --> 00:13:36.250 align:start position:0% actually the key piece to make it easy 00:13:36.250 --> 00:13:39.699 align:start position:0% actually the key piece to make it easy but<00:13:37.250> this<00:13:37.910> allows<00:13:38.180> a<00:13:38.480> lot<00:13:38.810> more<00:13:39.110> things<00:13:39.350> so 00:13:39.699 --> 00:13:39.709 align:start position:0% but this allows a lot more things so 00:13:39.709 --> 00:13:42.160 align:start position:0% but this allows a lot more things so this<00:13:40.040> in<00:13:40.279> the<00:13:41.000> first<00:13:41.240> instance<00:13:41.690> creates<00:13:42.050> a 00:13:42.160 --> 00:13:42.170 align:start position:0% this in the first instance creates a 00:13:42.170 --> 00:13:43.240 align:start position:0% this in the first instance creates a management<00:13:42.560> account 00:13:43.240 --> 00:13:43.250 align:start position:0% management account 00:13:43.250 --> 00:13:46.000 align:start position:0% management account so<00:13:43.700> now<00:13:43.880> I<00:13:43.910> all<00:13:44.240> not<00:13:44.510> only<00:13:44.690> have<00:13:44.810> one<00:13:45.020> key<00:13:45.260> but<00:13:45.980> I 00:13:46.000 --> 00:13:46.010 align:start position:0% so now I all not only have one key but I 00:13:46.010 --> 00:13:49.240 align:start position:0% so now I all not only have one key but I have<00:13:46.279> a<00:13:46.459> key<00:13:46.730> or<00:13:47.000> an<00:13:47.690> account<00:13:48.020> that<00:13:48.470> I<00:13:48.650> have<00:13:48.680> can 00:13:49.240 --> 00:13:49.250 align:start position:0% have a key or an account that I have can 00:13:49.250 --> 00:13:50.980 align:start position:0% have a key or an account that I have can manage<00:13:49.580> in<00:13:49.700> all<00:13:49.850> kind<00:13:50.089> of<00:13:50.180> ways<00:13:50.390> and<00:13:50.750> you<00:13:50.779> know 00:13:50.980 --> 00:13:50.990 align:start position:0% manage in all kind of ways and you know 00:13:50.990 --> 00:13:52.690 align:start position:0% manage in all kind of ways and you know we<00:13:51.140> can<00:13:51.290> amend<00:13:51.529> a<00:13:51.650> lot<00:13:51.800> of<00:13:51.890> new<00:13:52.100> things<00:13:52.130> on<00:13:52.580> how 00:13:52.690 --> 00:13:52.700 align:start position:0% we can amend a lot of new things on how 00:13:52.700 --> 00:13:55.930 align:start position:0% we can amend a lot of new things on how we<00:13:52.760> manage<00:13:52.970> doors<00:13:53.920> but<00:13:54.920> I<00:13:54.950> can<00:13:55.160> also<00:13:55.400> attach 00:13:55.930 --> 00:13:55.940 align:start position:0% we manage doors but I can also attach 00:13:55.940 --> 00:13:57.850 align:start position:0% we manage doors but I can also attach information<00:13:56.900> to<00:13:57.020> it<00:13:57.140> and<00:13:57.350> that's<00:13:57.500> what<00:13:57.680> this 00:13:57.850 --> 00:13:57.860 align:start position:0% information to it and that's what this 00:13:57.860 --> 00:14:01.090 align:start position:0% information to it and that's what this key<00:13:58.850> value<00:13:58.880> stores<00:13:59.510> for<00:13:59.870> so<00:14:00.529> the<00:14:00.650> key<00:14:00.830> value 00:14:01.090 --> 00:14:01.100 align:start position:0% key value stores for so the key value 00:14:01.100 --> 00:14:05.500 align:start position:0% key value stores for so the key value stores<00:14:01.400> by<00:14:02.270> 32<00:14:02.959> and<00:14:02.990> bytes<00:14:03.589> s<00:14:04.550> value<00:14:05.060> this 00:14:05.500 --> 00:14:05.510 align:start position:0% stores by 32 and bytes s value this 00:14:05.510 --> 00:14:07.600 align:start position:0% stores by 32 and bytes s value this means<00:14:05.839> it<00:14:06.380> can<00:14:06.440> come<00:14:06.770> up<00:14:06.890> with<00:14:06.920> all<00:14:07.250> kind<00:14:07.520> of 00:14:07.600 --> 00:14:07.610 align:start position:0% means it can come up with all kind of 00:14:07.610 --> 00:14:09.910 align:start position:0% means it can come up with all kind of things<00:14:07.670> that<00:14:08.180> we<00:14:08.690> allow<00:14:08.959> to<00:14:09.020> be<00:14:09.320> attached<00:14:09.620> to 00:14:09.910 --> 00:14:09.920 align:start position:0% things that we allow to be attached to 00:14:09.920 --> 00:14:13.440 align:start position:0% things that we allow to be attached to such<00:14:10.220> an<00:14:10.370> account<00:14:10.670> and<00:14:11.000> this<00:14:11.570> can<00:14:11.839> be 00:14:13.440 --> 00:14:13.450 align:start position:0% such an account and this can be 00:14:13.450 --> 00:14:16.180 align:start position:0% such an account and this can be completely<00:14:14.450> random<00:14:14.839> things<00:14:15.320> of<00:14:15.529> links<00:14:16.160> to 00:14:16.180 --> 00:14:16.190 align:start position:0% completely random things of links to 00:14:16.190 --> 00:14:18.400 align:start position:0% completely random things of links to reputation<00:14:16.579> systems<00:14:17.329> or<00:14:17.450> whatever<00:14:17.720> maybe 00:14:18.400 --> 00:14:18.410 align:start position:0% reputation systems or whatever maybe 00:14:18.410 --> 00:14:20.050 align:start position:0% reputation systems or whatever maybe from<00:14:18.560> something<00:14:18.860> you<00:14:18.920> could<00:14:19.070> simply<00:14:19.400> attach 00:14:20.050 --> 00:14:20.060 align:start position:0% from something you could simply attach 00:14:20.060 --> 00:14:22.630 align:start position:0% from something you could simply attach an<00:14:20.180> hour<00:14:20.270> talk<00:14:20.600> to<00:14:20.870> this<00:14:20.959> account<00:14:21.339> to<00:14:22.339> make<00:14:22.490> it 00:14:22.630 --> 00:14:22.640 align:start position:0% an hour talk to this account to make it 00:14:22.640 --> 00:14:25.580 align:start position:0% an hour talk to this account to make it somewhat<00:14:23.740> cooler<00:14:24.740> right 00:14:25.580 --> 00:14:25.590 align:start position:0% somewhat cooler right 00:14:25.590 --> 00:14:29.240 align:start position:0% somewhat cooler right or<00:14:25.800> the<00:14:26.190> company's<00:14:26.610> local<00:14:26.850> or<00:14:27.300> whatever<00:14:28.250> but 00:14:29.240 --> 00:14:29.250 align:start position:0% or the company's local or whatever but 00:14:29.250 --> 00:14:31.450 align:start position:0% or the company's local or whatever but you<00:14:29.340> can<00:14:29.460> also<00:14:29.640> link<00:14:30.000> to<00:14:30.210> all<00:14:30.390> kind<00:14:30.630> of<00:14:30.720> other 00:14:31.450 --> 00:14:31.460 align:start position:0% you can also link to all kind of other 00:14:31.460 --> 00:14:35.180 align:start position:0% you can also link to all kind of other obtain<00:14:32.460> more<00:14:33.140> identifiable<00:14:34.140> data<00:14:34.440> that<00:14:35.040> you 00:14:35.180 --> 00:14:35.190 align:start position:0% obtain more identifiable data that you 00:14:35.190 --> 00:14:37.400 align:start position:0% obtain more identifiable data that you don't<00:14:35.400> want<00:14:35.550> to<00:14:35.640> reveal<00:14:35.970> on<00:14:36.270> chain<00:14:36.600> but<00:14:37.260> that 00:14:37.400 --> 00:14:37.410 align:start position:0% don't want to reveal on chain but that 00:14:37.410 --> 00:14:39.650 align:start position:0% don't want to reveal on chain but that somehow<00:14:37.680> should<00:14:38.130> be<00:14:38.250> referenced<00:14:38.970> and<00:14:39.150> linked 00:14:39.650 --> 00:14:39.660 align:start position:0% somehow should be referenced and linked 00:14:39.660 --> 00:14:41.480 align:start position:0% somehow should be referenced and linked to<00:14:39.840> the<00:14:39.960> public<00:14:40.350> identity<00:14:40.860> or<00:14:41.010> the<00:14:41.100> public 00:14:41.480 --> 00:14:41.490 align:start position:0% to the public identity or the public 00:14:41.490 --> 00:14:44.450 align:start position:0% to the public identity or the public account<00:14:41.790> you<00:14:41.940> have<00:14:41.970> here<00:14:42.830> and<00:14:43.830> whatever<00:14:44.190> you 00:14:44.450 --> 00:14:44.460 align:start position:0% account you have here and whatever you 00:14:44.460 --> 00:14:46.519 align:start position:0% account you have here and whatever you come<00:14:44.550> up<00:14:44.670> with<00:14:44.880> you<00:14:45.089> know<00:14:45.150> batches<00:14:45.930> reputation 00:14:46.519 --> 00:14:46.529 align:start position:0% come up with you know batches reputation 00:14:46.529 --> 00:14:48.320 align:start position:0% come up with you know batches reputation systems<00:14:46.890> link<00:14:47.160> tokens<00:14:47.640> whatever<00:14:47.940> I<00:14:48.029> mean<00:14:48.210> you 00:14:48.320 --> 00:14:48.330 align:start position:0% systems link tokens whatever I mean you 00:14:48.330 --> 00:14:50.300 align:start position:0% systems link tokens whatever I mean you cannot<00:14:48.660> just<00:14:48.960> on<00:14:49.260> these<00:14:49.470> efforts<00:14:49.710> have<00:14:50.040> a<00:14:50.070> lot 00:14:50.300 --> 00:14:50.310 align:start position:0% cannot just on these efforts have a lot 00:14:50.310 --> 00:14:55.130 align:start position:0% cannot just on these efforts have a lot of<00:14:50.540> NFC<00:14:51.540> sitting<00:14:52.380> or<00:14:53.210> batches<00:14:54.210> whatever<00:14:54.870> but 00:14:55.130 --> 00:14:55.140 align:start position:0% of NFC sitting or batches whatever but 00:14:55.140 --> 00:14:58.370 align:start position:0% of NFC sitting or batches whatever but you<00:14:55.260> can<00:14:55.380> also<00:14:55.500> link<00:14:56.029> to<00:14:57.029> an<00:14:57.240> extra<00:14:57.839> reputation 00:14:58.370 --> 00:14:58.380 align:start position:0% you can also link to an extra reputation 00:14:58.380 --> 00:15:02.110 align:start position:0% you can also link to an extra reputation system<00:14:58.680> sitting<00:14:59.130> in<00:14:59.279> another<00:14:59.400> smart<00:14:59.880> contract 00:15:02.110 --> 00:15:02.120 align:start position:0% system sitting in another smart contract 00:15:02.120 --> 00:15:04.550 align:start position:0% system sitting in another smart contract that<00:15:03.120> allows<00:15:03.450> a<00:15:03.480> lot<00:15:03.690> of<00:15:03.720> flexibility<00:15:04.260> and 00:15:04.550 --> 00:15:04.560 align:start position:0% that allows a lot of flexibility and 00:15:04.560 --> 00:15:06.230 align:start position:0% that allows a lot of flexibility and because<00:15:05.040> there's<00:15:05.220> so<00:15:05.370> many<00:15:05.490> more<00:15:05.640> things<00:15:06.089> we 00:15:06.230 --> 00:15:06.240 align:start position:0% because there's so many more things we 00:15:06.240 --> 00:15:08.420 align:start position:0% because there's so many more things we don't<00:15:06.480> know<00:15:06.660> what<00:15:06.900> is<00:15:07.020> coming<00:15:07.260> having<00:15:08.160> a<00:15:08.250> key 00:15:08.420 --> 00:15:08.430 align:start position:0% don't know what is coming having a key 00:15:08.430 --> 00:15:10.430 align:start position:0% don't know what is coming having a key value<00:15:08.550> store<00:15:09.000> really<00:15:09.270> allows<00:15:09.690> for<00:15:09.990> all<00:15:10.140> kind 00:15:10.430 --> 00:15:10.440 align:start position:0% value store really allows for all kind 00:15:10.440 --> 00:15:11.870 align:start position:0% value store really allows for all kind of<00:15:10.500> new<00:15:10.680> things<00:15:11.010> you<00:15:11.190> know<00:15:11.310> we<00:15:11.490> don't<00:15:11.610> need<00:15:11.730> to 00:15:11.870 --> 00:15:11.880 align:start position:0% of new things you know we don't need to 00:15:11.880 --> 00:15:13.370 align:start position:0% of new things you know we don't need to think<00:15:12.089> about<00:15:12.180> everything<00:15:12.570> right<00:15:12.690> now<00:15:12.750> and 00:15:13.370 --> 00:15:13.380 align:start position:0% think about everything right now and 00:15:13.380 --> 00:15:15.950 align:start position:0% think about everything right now and having<00:15:13.980> to<00:15:14.100> find<00:15:14.339> these<00:15:14.910> five<00:15:15.240> things<00:15:15.570> you<00:15:15.779> can 00:15:15.950 --> 00:15:15.960 align:start position:0% having to find these five things you can 00:15:15.960 --> 00:15:18.620 align:start position:0% having to find these five things you can do<00:15:16.170> on<00:15:16.350> an<00:15:16.820> unguent<00:15:17.820> account<00:15:18.120> it's<00:15:18.510> an 00:15:18.620 --> 00:15:18.630 align:start position:0% do on an unguent account it's an 00:15:18.630 --> 00:15:26.000 align:start position:0% do on an unguent account it's an open-ended<00:15:19.200> system<00:15:24.140> so<00:15:25.140> that<00:15:25.620> actually 00:15:26.000 --> 00:15:26.010 align:start position:0% open-ended system so that actually 00:15:26.010 --> 00:15:28.430 align:start position:0% open-ended system so that actually creates<00:15:26.370> a<00:15:26.430> manageable<00:15:26.940> verified<00:15:27.420> account<00:15:27.839> so 00:15:28.430 --> 00:15:28.440 align:start position:0% creates a manageable verified account so 00:15:28.440 --> 00:15:31.340 align:start position:0% creates a manageable verified account so using<00:15:28.980> this<00:15:29.190> as<00:15:29.460> the<00:15:29.670> default<00:15:29.790> and<00:15:30.450> beauty 00:15:31.340 --> 00:15:31.350 align:start position:0% using this as the default and beauty 00:15:31.350 --> 00:15:32.930 align:start position:0% using this as the default and beauty here<00:15:31.560> is<00:15:31.589> you<00:15:31.860> can<00:15:32.010> start<00:15:32.339> out<00:15:32.460> with<00:15:32.490> a<00:15:32.670> key 00:15:32.930 --> 00:15:32.940 align:start position:0% here is you can start out with a key 00:15:32.940 --> 00:15:34.910 align:start position:0% here is you can start out with a key verification<00:15:33.780> the<00:15:34.260> moment<00:15:34.650> somebody 00:15:34.910 --> 00:15:34.920 align:start position:0% verification the moment somebody 00:15:34.920 --> 00:15:36.620 align:start position:0% verification the moment somebody purchased<00:15:35.370> something<00:15:35.610> or<00:15:36.060> doesn't<00:15:36.480> actually 00:15:36.620 --> 00:15:36.630 align:start position:0% purchased something or doesn't actually 00:15:36.630 --> 00:15:41.450 align:start position:0% purchased something or doesn't actually somehow<00:15:38.060> creates<00:15:39.060> value<00:15:39.300> or<00:15:39.839> money<00:15:40.410> spend<00:15:40.830> you 00:15:41.450 --> 00:15:41.460 align:start position:0% somehow creates value or money spend you 00:15:41.460 --> 00:15:44.210 align:start position:0% somehow creates value or money spend you can<00:15:41.670> on<00:15:41.940> the<00:15:42.120> fly<00:15:42.470> just<00:15:43.470> create<00:15:43.770> an<00:15:43.920> account 00:15:44.210 --> 00:15:44.220 align:start position:0% can on the fly just create an account 00:15:44.220 --> 00:15:47.540 align:start position:0% can on the fly just create an account for<00:15:44.430> him<00:15:44.490> where<00:15:45.360> this<00:15:45.570> key<00:15:45.839> is<00:15:45.990> the<00:15:46.170> owner<00:15:46.550> the 00:15:47.540 --> 00:15:47.550 align:start position:0% for him where this key is the owner the 00:15:47.550 --> 00:15:49.460 align:start position:0% for him where this key is the owner the beauty<00:15:47.880> is<00:15:48.000> that<00:15:48.270> now<00:15:48.720> this<00:15:48.900> person<00:15:49.290> could 00:15:49.460 --> 00:15:49.470 align:start position:0% beauty is that now this person could 00:15:49.470 --> 00:15:50.870 align:start position:0% beauty is that now this person could actually<00:15:49.620> take<00:15:49.950> this<00:15:50.040> account<00:15:50.339> and<00:15:50.610> take<00:15:50.760> it 00:15:50.870 --> 00:15:50.880 align:start position:0% actually take this account and take it 00:15:50.880 --> 00:15:52.820 align:start position:0% actually take this account and take it into<00:15:51.000> another<00:15:51.150> application<00:15:51.660> so<00:15:52.140> we<00:15:52.320> all<00:15:52.440> start 00:15:52.820 --> 00:15:52.830 align:start position:0% into another application so we all start 00:15:52.830 --> 00:15:55.550 align:start position:0% into another application so we all start to<00:15:52.980> use<00:15:53.160> the<00:15:53.339> same<00:15:53.660> default<00:15:54.660> account<00:15:54.990> standard 00:15:55.550 --> 00:15:55.560 align:start position:0% to use the same default account standard 00:15:55.560 --> 00:15:58.070 align:start position:0% to use the same default account standard you<00:15:56.339> can<00:15:56.520> take<00:15:56.760> your<00:15:57.000> account<00:15:57.330> across<00:15:57.690> all<00:15:57.839> of 00:15:58.070 --> 00:15:58.080 align:start position:0% you can take your account across all of 00:15:58.080 --> 00:16:00.260 align:start position:0% you can take your account across all of these<00:15:58.230> different<00:15:58.589> applications<00:15:58.680> and<00:15:59.339> it's<00:16:00.150> a 00:16:00.260 --> 00:16:00.270 align:start position:0% these different applications and it's a 00:16:00.270 --> 00:16:02.870 align:start position:0% these different applications and it's a lot<00:16:00.450> more<00:16:01.070> manageable<00:16:02.070> and<00:16:02.220> it's<00:16:02.550> a<00:16:02.610> lot<00:16:02.730> more 00:16:02.870 --> 00:16:02.880 align:start position:0% lot more manageable and it's a lot more 00:16:02.880 --> 00:16:04.579 align:start position:0% lot more manageable and it's a lot more easy<00:16:03.150> to<00:16:03.390> interact<00:16:03.660> with<00:16:03.810> one<00:16:04.020> chain<00:16:04.260> things 00:16:04.579 --> 00:16:04.589 align:start position:0% easy to interact with one chain things 00:16:04.589 --> 00:16:07.430 align:start position:0% easy to interact with one chain things so<00:16:05.550> that<00:16:05.820> can<00:16:06.030> be<00:16:06.180> rather<00:16:06.360> cheap<00:16:06.750> to<00:16:06.930> deploy<00:16:07.200> I 00:16:07.430 --> 00:16:07.440 align:start position:0% so that can be rather cheap to deploy I 00:16:07.440 --> 00:16:09.850 align:start position:0% so that can be rather cheap to deploy I mean<00:16:07.620> these<00:16:08.370> are<00:16:08.520> transactions<00:16:08.970> 21,000<00:16:09.660> gasps 00:16:09.850 --> 00:16:09.860 align:start position:0% mean these are transactions 21,000 gasps 00:16:09.860 --> 00:16:13.040 align:start position:0% mean these are transactions 21,000 gasps 32,000<00:16:10.860> for<00:16:11.070> deploying<00:16:11.730> a<00:16:11.790> library<00:16:12.180> that<00:16:12.360> can 00:16:13.040 --> 00:16:13.050 align:start position:0% 32,000 for deploying a library that can 00:16:13.050 --> 00:16:15.820 align:start position:0% 32,000 for deploying a library that can be<00:16:13.230> as<00:16:13.500> cheap<00:16:14.160> as<00:16:14.310> you<00:16:14.339> can<00:16:14.580> get<00:16:14.760> and<00:16:15.270> it's 00:16:15.820 --> 00:16:15.830 align:start position:0% be as cheap as you can get and it's 00:16:15.830 --> 00:16:18.340 align:start position:0% be as cheap as you can get and it's basically<00:16:16.830> it<00:16:17.040> could<00:16:17.370> be<00:16:17.550> a<00:16:17.580> long<00:16:17.820> lasting 00:16:18.340 --> 00:16:18.350 align:start position:0% basically it could be a long lasting 00:16:18.350 --> 00:16:21.199 align:start position:0% basically it could be a long lasting manageable<00:16:19.350> account<00:16:19.730> and<00:16:20.730> because<00:16:21.000> it's<00:16:21.150> a 00:16:21.199 --> 00:16:21.209 align:start position:0% manageable account and because it's a 00:16:21.209 --> 00:16:23.300 align:start position:0% manageable account and because it's a small<00:16:21.240> contract<00:16:21.810> and<00:16:22.020> smartphones<00:16:22.860> can<00:16:23.130> talk 00:16:23.300 --> 00:16:23.310 align:start position:0% small contract and smartphones can talk 00:16:23.310 --> 00:16:25.610 align:start position:0% small contract and smartphones can talk to<00:16:23.400> other<00:16:23.520> smart<00:16:23.850> contracts<00:16:24.330> that's<00:16:25.080> the<00:16:25.380> big 00:16:25.610 --> 00:16:25.620 align:start position:0% to other smart contracts that's the big 00:16:25.620 --> 00:16:27.380 align:start position:0% to other smart contracts that's the big big<00:16:25.860> magic<00:16:26.310> thing<00:16:26.580> which<00:16:26.790> I<00:16:26.940> guess<00:16:27.089> a<00:16:27.120> lot<00:16:27.360> of 00:16:27.380 --> 00:16:27.390 align:start position:0% big magic thing which I guess a lot of 00:16:27.390 --> 00:16:29.060 align:start position:0% big magic thing which I guess a lot of people<00:16:27.720> also<00:16:27.839> that<00:16:28.080> the<00:16:28.200> film<00:16:28.410> space<00:16:28.620> has<00:16:28.860> not 00:16:29.060 --> 00:16:29.070 align:start position:0% people also that the film space has not 00:16:29.070 --> 00:16:29.450 align:start position:0% people also that the film space has not have 00:16:29.450 --> 00:16:29.460 align:start position:0% have 00:16:29.460 --> 00:16:32.540 align:start position:0% have fully<00:16:29.760> understood<00:16:30.180> why<00:16:30.990> he<00:16:31.350> was<00:16:31.529> awesome<00:16:31.710> and 00:16:32.540 --> 00:16:32.550 align:start position:0% fully understood why he was awesome and 00:16:32.550 --> 00:16:35.480 align:start position:0% fully understood why he was awesome and the<00:16:32.970> evm<00:16:33.390> in<00:16:33.570> fact<00:16:33.839> is<00:16:34.080> because<00:16:34.830> of<00:16:34.980> that<00:16:35.130> fact 00:16:35.480 --> 00:16:35.490 align:start position:0% the evm in fact is because of that fact 00:16:35.490 --> 00:16:36.980 align:start position:0% the evm in fact is because of that fact that<00:16:35.670> you<00:16:36.029> can<00:16:36.210> talk<00:16:36.360> to<00:16:36.540> other<00:16:36.660> smart 00:16:36.980 --> 00:16:36.990 align:start position:0% that you can talk to other smart 00:16:36.990 --> 00:16:40.280 align:start position:0% that you can talk to other smart contracts<00:16:37.410> that<00:16:38.279> kind<00:16:38.610> of<00:16:38.700> makes<00:16:39.000> your<00:16:39.480> own 00:16:40.280 --> 00:16:40.290 align:start position:0% contracts that kind of makes your own 00:16:40.290 --> 00:16:43.400 align:start position:0% contracts that kind of makes your own shell<00:16:40.560> account<00:16:40.830> the<00:16:41.730> actor<00:16:42.240> on<00:16:42.420> chain<00:16:42.750> this 00:16:43.400 --> 00:16:43.410 align:start position:0% shell account the actor on chain this 00:16:43.410 --> 00:16:46.310 align:start position:0% shell account the actor on chain this means<00:16:43.710> for<00:16:44.610> other<00:16:44.850> systems<00:16:45.149> outside<00:16:45.540> it's<00:16:46.170> the 00:16:46.310 --> 00:16:46.320 align:start position:0% means for other systems outside it's the 00:16:46.320 --> 00:16:47.900 align:start position:0% means for other systems outside it's the same<00:16:46.560> like<00:16:46.740> before<00:16:46.770> you<00:16:47.310> know<00:16:47.430> if<00:16:47.550> a<00:16:47.640> key<00:16:47.880> is 00:16:47.900 --> 00:16:47.910 align:start position:0% same like before you know if a key is 00:16:47.910 --> 00:16:49.910 align:start position:0% same like before you know if a key is talking<00:16:48.300> to<00:16:48.420> you<00:16:48.600> or<00:16:49.050> smartphone<00:16:49.649> app<00:16:49.770> you 00:16:49.910 --> 00:16:49.920 align:start position:0% talking to you or smartphone app you 00:16:49.920 --> 00:16:52.190 align:start position:0% talking to you or smartphone app you don't<00:16:50.100> care<00:16:50.370> in<00:16:51.209> fact<00:16:51.540> here<00:16:51.810> you<00:16:51.839> can<00:16:52.050> even 00:16:52.190 --> 00:16:52.200 align:start position:0% don't care in fact here you can even 00:16:52.200 --> 00:16:54.620 align:start position:0% don't care in fact here you can even check<00:16:52.560> this<00:16:52.709> month<00:16:52.890> conduct<00:16:53.279> we<00:16:53.880> read<00:16:54.420> some 00:16:54.620 --> 00:16:54.630 align:start position:0% check this month conduct we read some 00:16:54.630 --> 00:16:56.870 align:start position:0% check this month conduct we read some information<00:16:55.010> you<00:16:56.010> need<00:16:56.250> maybe<00:16:56.670> some 00:16:56.870 --> 00:16:56.880 align:start position:0% information you need maybe some 00:16:56.880 --> 00:16:59.000 align:start position:0% information you need maybe some verification<00:16:57.600> or<00:16:57.870> maybe<00:16:58.140> some<00:16:58.350> attach<00:16:58.620> claims 00:16:59.000 --> 00:16:59.010 align:start position:0% verification or maybe some attach claims 00:16:59.010 --> 00:17:02.690 align:start position:0% verification or maybe some attach claims you<00:16:59.339> somehow<00:16:59.580> need<00:17:01.130> and<00:17:02.130> do<00:17:02.279> something<00:17:02.550> with 00:17:02.690 --> 00:17:02.700 align:start position:0% you somehow need and do something with 00:17:02.700 --> 00:17:06.770 align:start position:0% you somehow need and do something with them<00:17:03.050> so<00:17:04.970> message<00:17:05.970> sender<00:17:06.329> you<00:17:06.449> know<00:17:06.569> that's 00:17:06.770 --> 00:17:06.780 align:start position:0% them so message sender you know that's 00:17:06.780 --> 00:17:08.929 align:start position:0% them so message sender you know that's what<00:17:06.929> all<00:17:07.110> it<00:17:07.500> doesn't<00:17:08.280> necessarily<00:17:08.760> need<00:17:08.880> to 00:17:08.929 --> 00:17:08.939 align:start position:0% what all it doesn't necessarily need to 00:17:08.939 --> 00:17:11.660 align:start position:0% what all it doesn't necessarily need to be<00:17:09.030> your<00:17:09.240> person<00:17:09.720> this<00:17:10.110> could<00:17:10.380> be<00:17:10.589> one<00:17:11.189> account 00:17:11.660 --> 00:17:11.670 align:start position:0% be your person this could be one account 00:17:11.670 --> 00:17:13.910 align:start position:0% be your person this could be one account you<00:17:11.880> use<00:17:12.150> you<00:17:12.420> can<00:17:12.449> have<00:17:12.720> fifty<00:17:13.199> if<00:17:13.589> you<00:17:13.709> want 00:17:13.910 --> 00:17:13.920 align:start position:0% you use you can have fifty if you want 00:17:13.920 --> 00:17:16.150 align:start position:0% you use you can have fifty if you want to<00:17:14.100> I<00:17:14.130> guess<00:17:14.459> we<00:17:14.640> end<00:17:14.819> up<00:17:14.970> with<00:17:15.120> just<00:17:15.390> a<00:17:15.569> few<00:17:15.809> and 00:17:16.150 --> 00:17:16.160 align:start position:0% to I guess we end up with just a few and 00:17:16.160 --> 00:17:18.049 align:start position:0% to I guess we end up with just a few and but<00:17:17.160> you<00:17:17.280> can<00:17:17.429> use<00:17:17.610> them<00:17:17.850> for<00:17:17.880> different 00:17:18.049 --> 00:17:18.059 align:start position:0% but you can use them for different 00:17:18.059 --> 00:17:20.380 align:start position:0% but you can use them for different personas<00:17:18.839> you<00:17:19.410> don't<00:17:19.589> necessarily<00:17:19.709> need<00:17:20.100> to 00:17:20.380 --> 00:17:20.390 align:start position:0% personas you don't necessarily need to 00:17:20.390 --> 00:17:22.819 align:start position:0% personas you don't necessarily need to upload<00:17:21.390> your<00:17:21.689> picture<00:17:22.230> and<00:17:22.319> then<00:17:22.380> go<00:17:22.589> to<00:17:22.650> the 00:17:22.819 --> 00:17:22.829 align:start position:0% upload your picture and then go to the 00:17:22.829 --> 00:17:24.230 align:start position:0% upload your picture and then go to the government<00:17:23.100> and<00:17:23.429> put<00:17:23.520> the<00:17:23.640> poo<00:17:23.819> when<00:17:23.970> you<00:17:24.089> want 00:17:24.230 --> 00:17:24.240 align:start position:0% government and put the poo when you want 00:17:24.240 --> 00:17:25.970 align:start position:0% government and put the poo when you want an<00:17:24.390> account<00:17:24.689> just<00:17:24.870> to<00:17:25.170> prove<00:17:25.530> that<00:17:25.589> this<00:17:25.829> is 00:17:25.970 --> 00:17:25.980 align:start position:0% an account just to prove that this is 00:17:25.980 --> 00:17:28.340 align:start position:0% an account just to prove that this is your<00:17:26.250> account<00:17:26.520> and<00:17:26.790> then<00:17:26.910> go<00:17:26.939> everybody<00:17:27.569> show 00:17:28.340 --> 00:17:28.350 align:start position:0% your account and then go everybody show 00:17:28.350 --> 00:17:31.730 align:start position:0% your account and then go everybody show everybody<00:17:28.740> what<00:17:28.860> you<00:17:28.950> do<00:17:29.270> but<00:17:30.559> one<00:17:31.559> of<00:17:31.650> the 00:17:31.730 --> 00:17:31.740 align:start position:0% everybody what you do but one of the 00:17:31.740 --> 00:17:33.770 align:start position:0% everybody what you do but one of the biggest<00:17:32.010> pieces<00:17:32.220> in<00:17:32.580> our<00:17:32.880> society<00:17:33.570> is 00:17:33.770 --> 00:17:33.780 align:start position:0% biggest pieces in our society is 00:17:33.780 --> 00:17:36.080 align:start position:0% biggest pieces in our society is actually<00:17:34.050> transparency<00:17:34.980> we<00:17:35.370> are<00:17:35.610> on<00:17:35.820> Twitter 00:17:36.080 --> 00:17:36.090 align:start position:0% actually transparency we are on Twitter 00:17:36.090 --> 00:17:37.520 align:start position:0% actually transparency we are on Twitter and<00:17:36.450> on<00:17:36.570> Facebook<00:17:36.600> on<00:17:37.170> all<00:17:37.350> of<00:17:37.440> these 00:17:37.520 --> 00:17:37.530 align:start position:0% and on Facebook on all of these 00:17:37.530 --> 00:17:39.169 align:start position:0% and on Facebook on all of these platforms<00:17:37.710> because<00:17:38.370> we<00:17:38.520> want<00:17:38.760> to<00:17:38.880> express 00:17:39.169 --> 00:17:39.179 align:start position:0% platforms because we want to express 00:17:39.179 --> 00:17:42.640 align:start position:0% platforms because we want to express ourselves<00:17:39.770> so<00:17:40.770> that<00:17:40.800> expression<00:17:41.250> needs<00:17:41.640> a 00:17:42.640 --> 00:17:42.650 align:start position:0% ourselves so that expression needs a 00:17:42.650 --> 00:17:45.470 align:start position:0% ourselves so that expression needs a identity<00:17:43.650> you<00:17:43.770> can<00:17:43.830> actually<00:17:44.130> or<00:17:45.030> an<00:17:45.150> account 00:17:45.470 --> 00:17:45.480 align:start position:0% identity you can actually or an account 00:17:45.480 --> 00:17:48.290 align:start position:0% identity you can actually or an account an<00:17:45.720> extra<00:17:45.990> take<00:17:46.200> around<00:17:46.670> where<00:17:47.670> would<00:17:48.210> you 00:17:48.290 --> 00:17:48.300 align:start position:0% an extra take around where would you 00:17:48.300 --> 00:17:50.270 align:start position:0% an extra take around where would you correct<00:17:48.450> right<00:17:49.020> you<00:17:49.230> can<00:17:49.559> take<00:17:49.860> care<00:17:50.070> of<00:17:50.130> that 00:17:50.270 --> 00:17:50.280 align:start position:0% correct right you can take care of that 00:17:50.280 --> 00:17:52.360 align:start position:0% correct right you can take care of that whatever<00:17:50.580> is<00:17:50.700> on<00:17:50.880> there<00:17:51.090> is<00:17:51.240> what<00:17:51.480> we<00:17:51.780> want<00:17:52.050> to 00:17:52.360 --> 00:17:52.370 align:start position:0% whatever is on there is what we want to 00:17:52.370 --> 00:17:57.680 align:start position:0% whatever is on there is what we want to put<00:17:53.370> out<00:17:53.580> there<00:17:53.850> and<00:17:56.330> seventy-five<00:17:57.330> can<00:17:57.570> be 00:17:57.680 --> 00:17:57.690 align:start position:0% put out there and seventy-five can be 00:17:57.690 --> 00:18:00.380 align:start position:0% put out there and seventy-five can be done<00:17:57.900> also<00:17:58.770> for<00:17:59.280> companies<00:17:59.700> also<00:18:00.000> for 00:18:00.380 --> 00:18:00.390 align:start position:0% done also for companies also for 00:18:00.390 --> 00:18:02.570 align:start position:0% done also for companies also for organizations<00:18:01.100> technically<00:18:02.100> speaking<00:18:02.340> the 00:18:02.570 --> 00:18:02.580 align:start position:0% organizations technically speaking the 00:18:02.580 --> 00:18:04.340 align:start position:0% organizations technically speaking the if<00:18:02.670> your<00:18:02.790> foundation<00:18:02.970> should<00:18:03.480> have<00:18:03.660> a<00:18:03.809> 75 00:18:04.340 --> 00:18:04.350 align:start position:0% if your foundation should have a 75 00:18:04.350 --> 00:18:08.000 align:start position:0% if your foundation should have a 75 account<00:18:04.679> and<00:18:05.010> not<00:18:05.700> the<00:18:05.910> etherium<00:18:07.010> multi-sig 00:18:08.000 --> 00:18:08.010 align:start position:0% account and not the etherium multi-sig 00:18:08.010 --> 00:18:10.790 align:start position:0% account and not the etherium multi-sig from<00:18:08.700> three<00:18:09.000> years<00:18:09.179> ago<00:18:09.300> in<00:18:09.840> official<00:18:10.650> address 00:18:10.790 --> 00:18:10.800 align:start position:0% from three years ago in official address 00:18:10.800 --> 00:18:14.360 align:start position:0% from three years ago in official address which<00:18:11.670> we<00:18:11.820> all<00:18:11.910> look<00:18:12.090> at<00:18:12.210> right<00:18:13.070> so<00:18:14.070> it's<00:18:14.250> your 00:18:14.360 --> 00:18:14.370 align:start position:0% which we all look at right so it's your 00:18:14.370 --> 00:18:16.880 align:start position:0% which we all look at right so it's your Unchained<00:18:14.820> account<00:18:15.150> and<00:18:15.570> it<00:18:16.350> should<00:18:16.590> be<00:18:16.740> your 00:18:16.880 --> 00:18:16.890 align:start position:0% Unchained account and it should be your 00:18:16.890 --> 00:18:19.850 align:start position:0% Unchained account and it should be your gateway<00:18:17.220> to<00:18:17.250> decentralized<00:18:18.090> world<00:18:18.710> and<00:18:19.710> if 00:18:19.850 --> 00:18:19.860 align:start position:0% gateway to decentralized world and if 00:18:19.860 --> 00:18:21.500 align:start position:0% gateway to decentralized world and if you<00:18:19.890> want<00:18:20.130> to<00:18:20.220> do<00:18:20.340> an<00:18:20.460> energy<00:18:20.670> then<00:18:21.090> you<00:18:21.120> rather 00:18:21.500 --> 00:18:21.510 align:start position:0% you want to do an energy then you rather 00:18:21.510 --> 00:18:23.299 align:start position:0% you want to do an energy then you rather look<00:18:21.809> into<00:18:22.110> off<00:18:22.290> chain<00:18:22.620> solutions<00:18:23.130> like 00:18:23.299 --> 00:18:23.309 align:start position:0% look into off chain solutions like 00:18:23.309 --> 00:18:25.790 align:start position:0% look into off chain solutions like verifiable<00:18:23.910> claims<00:18:24.380> Doubletree<00:18:25.380> see<00:18:25.590> does 00:18:25.790 --> 00:18:25.800 align:start position:0% verifiable claims Doubletree see does 00:18:25.800 --> 00:18:27.290 align:start position:0% verifiable claims Doubletree see does great<00:18:26.040> work<00:18:26.250> on<00:18:26.429> that<00:18:26.640> and<00:18:26.850> it's<00:18:26.970> a<00:18:27.030> lot<00:18:27.150> of 00:18:27.290 --> 00:18:27.300 align:start position:0% great work on that and it's a lot of 00:18:27.300 --> 00:18:30.380 align:start position:0% great work on that and it's a lot of projects<00:18:28.200> like<00:18:28.520> three<00:18:29.520> quarks<00:18:29.790> and<00:18:30.030> item 00:18:30.380 --> 00:18:30.390 align:start position:0% projects like three quarks and item 00:18:30.390 --> 00:18:33.260 align:start position:0% projects like three quarks and item three<00:18:30.690> and<00:18:30.990> you<00:18:31.170> port<00:18:31.500> and<00:18:31.830> your<00:18:32.160> Lacan<00:18:32.460> which 00:18:33.260 --> 00:18:33.270 align:start position:0% three and you port and your Lacan which 00:18:33.270 --> 00:18:34.870 align:start position:0% three and you port and your Lacan which are<00:18:33.480> working<00:18:34.170> on 00:18:34.870 --> 00:18:34.880 align:start position:0% are working on 00:18:34.880 --> 00:18:37.720 align:start position:0% are working on it's<00:18:35.150> kind<00:18:35.360> of<00:18:35.390> like<00:18:36.040> real-world<00:18:37.040> identities 00:18:37.720 --> 00:18:37.730 align:start position:0% it's kind of like real-world identities 00:18:37.730 --> 00:18:40.210 align:start position:0% it's kind of like real-world identities work<00:18:38.150> which<00:18:38.780> are<00:18:39.110> not<00:18:39.530> necessarily<00:18:39.890> on<00:18:40.010> the 00:18:40.210 --> 00:18:40.220 align:start position:0% work which are not necessarily on the 00:18:40.220 --> 00:18:42.100 align:start position:0% work which are not necessarily on the blockchain<00:18:40.400> or<00:18:40.790> only<00:18:41.030> a<00:18:41.090> flex<00:18:41.360> light<00:18:41.600> Jesus<00:18:41.960> on 00:18:42.100 --> 00:18:42.110 align:start position:0% blockchain or only a flex light Jesus on 00:18:42.110 --> 00:18:45.640 align:start position:0% blockchain or only a flex light Jesus on the<00:18:42.200> blockchain<00:18:43.780> so<00:18:44.780> what<00:18:44.990> we<00:18:45.080> have<00:18:45.200> done<00:18:45.440> is 00:18:45.640 --> 00:18:45.650 align:start position:0% the blockchain so what we have done is 00:18:45.650 --> 00:18:48.010 align:start position:0% the blockchain so what we have done is this<00:18:45.830> the<00:18:46.040> Eastern<00:18:46.370> 75<00:18:46.850> Alliance<00:18:47.300> obviously 00:18:48.010 --> 00:18:48.020 align:start position:0% this the Eastern 75 Alliance obviously 00:18:48.020 --> 00:18:51.370 align:start position:0% this the Eastern 75 Alliance obviously that's<00:18:48.550> this<00:18:49.550> the<00:18:49.880> official<00:18:50.450> of<00:18:50.810> security 00:18:51.370 --> 00:18:51.380 align:start position:0% that's this the official of security 00:18:51.380 --> 00:18:53.860 align:start position:0% that's this the official of security implementation<00:18:51.980> up<00:18:52.040> to<00:18:52.160> 75<00:18:52.730> version<00:18:53.570> two<00:18:53.720> as 00:18:53.860 --> 00:18:53.870 align:start position:0% implementation up to 75 version two as 00:18:53.870 --> 00:18:56.440 align:start position:0% implementation up to 75 version two as well<00:18:54.280> they'll<00:18:55.280> always<00:18:55.430> it<00:18:55.610> the<00:18:55.730> issue<00:18:55.880> where 00:18:56.440 --> 00:18:56.450 align:start position:0% well they'll always it the issue where 00:18:56.450 --> 00:18:59.140 align:start position:0% well they'll always it the issue where we<00:18:56.540> discussed<00:18:56.960> because<00:18:57.670> currently<00:18:58.670> the<00:18:58.970> main 00:18:59.140 --> 00:18:59.150 align:start position:0% we discussed because currently the main 00:18:59.150 --> 00:19:03.700 align:start position:0% we discussed because currently the main thing<00:18:59.450> we<00:18:59.570> are<00:18:59.690> doing<00:19:01.570> analyzer<00:19:02.570> this<00:19:03.350> morning 00:19:03.700 --> 00:19:03.710 align:start position:0% thing we are doing analyzer this morning 00:19:03.710 --> 00:19:06.520 align:start position:0% thing we are doing analyzer this morning screen<00:19:03.920> so<00:19:04.820> the<00:19:05.030> standard<00:19:05.480> scenario<00:19:05.930> so<00:19:06.260> I'm 00:19:06.520 --> 00:19:06.530 align:start position:0% screen so the standard scenario so I'm 00:19:06.530 --> 00:19:09.190 align:start position:0% screen so the standard scenario so I'm working<00:19:06.800> on<00:19:07.100> this<00:19:07.490> project<00:19:07.760> lock<00:19:08.180> so<00:19:08.390> so<00:19:08.930> this 00:19:09.190 --> 00:19:09.200 align:start position:0% working on this project lock so so this 00:19:09.200 --> 00:19:11.590 align:start position:0% working on this project lock so so this is<00:19:09.260> a<00:19:09.440> blockchain<00:19:09.890> for<00:19:10.310> the<00:19:10.460> a<00:19:10.760> new<00:19:11.420> credit 00:19:11.590 --> 00:19:11.600 align:start position:0% is a blockchain for the a new credit 00:19:11.600 --> 00:19:13.210 align:start position:0% is a blockchain for the a new credit economies<00:19:12.170> how<00:19:12.290> we<00:19:12.350> call<00:19:12.620> it<00:19:12.740> all<00:19:12.950> for<00:19:13.160> the 00:19:13.210 --> 00:19:13.220 align:start position:0% economies how we call it all for the 00:19:13.220 --> 00:19:15.850 align:start position:0% economies how we call it all for the lifestyle<00:19:13.670> space<00:19:14.050> one<00:19:15.050> important<00:19:15.530> thing<00:19:15.560> here 00:19:15.850 --> 00:19:15.860 align:start position:0% lifestyle space one important thing here 00:19:15.860 --> 00:19:17.680 align:start position:0% lifestyle space one important thing here is<00:19:15.890> this<00:19:16.280> is<00:19:16.340> the<00:19:16.580> grameen<00:19:17.000> of<00:19:17.090> people<00:19:17.510> who 00:19:17.680 --> 00:19:17.690 align:start position:0% is this is the grameen of people who 00:19:17.690 --> 00:19:20.140 align:start position:0% is this is the grameen of people who does<00:19:17.900> not<00:19:18.080> know<00:19:18.290> tank<00:19:18.620> nor<00:19:19.160> one<00:19:19.460> to<00:19:19.670> understand 00:19:20.140 --> 00:19:20.150 align:start position:0% does not know tank nor one to understand 00:19:20.150 --> 00:19:21.940 align:start position:0% does not know tank nor one to understand book<00:19:20.330> chain<00:19:20.570> but<00:19:21.230> they<00:19:21.350> might<00:19:21.560> want<00:19:21.590> to<00:19:21.770> create 00:19:21.940 --> 00:19:21.950 align:start position:0% book chain but they might want to create 00:19:21.950 --> 00:19:23.800 align:start position:0% book chain but they might want to create tokens<00:19:22.460> or<00:19:22.670> own<00:19:22.850> things<00:19:23.180> physically<00:19:23.690> in 00:19:23.800 --> 00:19:23.810 align:start position:0% tokens or own things physically in 00:19:23.810 --> 00:19:26.320 align:start position:0% tokens or own things physically in digital<00:19:24.200> so<00:19:24.800> you<00:19:25.370> need<00:19:25.550> to<00:19:25.670> make<00:19:25.790> it<00:19:25.880> easy<00:19:26.090> for 00:19:26.320 --> 00:19:26.330 align:start position:0% digital so you need to make it easy for 00:19:26.330 --> 00:19:29.500 align:start position:0% digital so you need to make it easy for them<00:19:26.480> to<00:19:26.660> interact<00:19:26.750> with<00:19:27.140> the<00:19:27.260> blockchain<00:19:28.510> so 00:19:29.500 --> 00:19:29.510 align:start position:0% them to interact with the blockchain so 00:19:29.510 --> 00:19:31.600 align:start position:0% them to interact with the blockchain so we<00:19:29.720> are<00:19:29.870> developing<00:19:30.410> and<00:19:30.980> iterating<00:19:31.520> on 00:19:31.600 --> 00:19:31.610 align:start position:0% we are developing and iterating on 00:19:31.610 --> 00:19:33.700 align:start position:0% we are developing and iterating on standard<00:19:32.090> scenarios<00:19:32.720> means<00:19:33.020> like<00:19:33.290> different 00:19:33.700 --> 00:19:33.710 align:start position:0% standard scenarios means like different 00:19:33.710 --> 00:19:35.770 align:start position:0% standard scenarios means like different standards<00:19:34.160> like<00:19:34.310> seven<00:19:34.700> to<00:19:34.790> five<00:19:35.030> likely<00:19:35.600> to 00:19:35.770 --> 00:19:35.780 align:start position:0% standards like seven to five likely to 00:19:35.780 --> 00:19:38.850 align:start position:0% standards like seven to five likely to certificates<00:19:36.110> and<00:19:37.100> others 00:19:38.850 --> 00:19:38.860 align:start position:0% certificates and others 00:19:38.860 --> 00:19:41.230 align:start position:0% certificates and others we're<00:19:39.860> kind<00:19:40.100> of<00:19:40.130> like<00:19:40.250> trying<00:19:40.520> things<00:19:40.880> out<00:19:41.030> you 00:19:41.230 --> 00:19:41.240 align:start position:0% we're kind of like trying things out you 00:19:41.240 --> 00:19:42.910 align:start position:0% we're kind of like trying things out you know<00:19:41.360> how<00:19:41.690> it<00:19:41.810> is<00:19:41.930> could<00:19:42.140> work<00:19:42.530> in<00:19:42.650> the<00:19:42.740> whole 00:19:42.910 --> 00:19:42.920 align:start position:0% know how it is could work in the whole 00:19:42.920 --> 00:19:45.280 align:start position:0% know how it is could work in the whole flow<00:19:43.190> together<00:19:43.430> how<00:19:44.300> it<00:19:44.510> can<00:19:44.660> own<00:19:44.780> token 00:19:45.280 --> 00:19:45.290 align:start position:0% flow together how it can own token 00:19:45.290 --> 00:19:49.030 align:start position:0% flow together how it can own token there's<00:19:45.590> a<00:19:45.650> new<00:19:45.860> standard<00:19:46.280> we<00:19:46.400> proposed<00:19:48.040> which 00:19:49.030 --> 00:19:49.040 align:start position:0% there's a new standard we proposed which 00:19:49.040 --> 00:19:50.470 align:start position:0% there's a new standard we proposed which is<00:19:49.190> the<00:19:49.340> lowest<00:19:49.700> one<00:19:49.940> is<00:19:50.150> actually<00:19:50.330> a 00:19:50.470 --> 00:19:50.480 align:start position:0% is the lowest one is actually a 00:19:50.480 --> 00:19:52.660 align:start position:0% is the lowest one is actually a universal<00:19:50.870> receiver<00:19:51.410> standard<00:19:51.740> that 00:19:52.660 --> 00:19:52.670 align:start position:0% universal receiver standard that 00:19:52.670 --> 00:19:54.430 align:start position:0% universal receiver standard that probably<00:19:53.030> is<00:19:53.180> the<00:19:53.420> whole<00:19:53.660> discussion<00:19:53.960> itself 00:19:54.430 --> 00:19:54.440 align:start position:0% probably is the whole discussion itself 00:19:54.440 --> 00:19:56.800 align:start position:0% probably is the whole discussion itself but<00:19:54.830> we<00:19:55.040> have<00:19:55.250> very<00:19:56.090> short<00:19:56.300> we<00:19:56.540> have<00:19:56.690> this 00:19:56.800 --> 00:19:56.810 align:start position:0% but we have very short we have this 00:19:56.810 --> 00:19:59.590 align:start position:0% but we have very short we have this problem<00:19:57.110> of<00:19:57.350> many<00:19:57.740> tokens<00:19:58.600> implementing 00:19:59.590 --> 00:19:59.600 align:start position:0% problem of many tokens implementing 00:19:59.600 --> 00:20:02.230 align:start position:0% problem of many tokens implementing different<00:20:00.320> type<00:20:00.470> of<00:20:00.500> receiver<00:20:01.040> functions<00:20:01.610> so 00:20:02.230 --> 00:20:02.240 align:start position:0% different type of receiver functions so 00:20:02.240 --> 00:20:04.720 align:start position:0% different type of receiver functions so seven<00:20:02.690> seven<00:20:02.990> has<00:20:03.140> token<00:20:03.440> received<00:20:03.800> year<00:20:04.490> C 00:20:04.720 --> 00:20:04.730 align:start position:0% seven seven has token received year C 00:20:04.730 --> 00:20:06.820 align:start position:0% seven seven has token received year C two<00:20:04.880> to<00:20:05.030> three<00:20:05.240> has<00:20:05.420> I<00:20:05.690> think<00:20:06.230> also<00:20:06.650> something 00:20:06.820 --> 00:20:06.830 align:start position:0% two to three has I think also something 00:20:06.830 --> 00:20:08.530 align:start position:0% two to three has I think also something with<00:20:07.040> token<00:20:07.520> fallback<00:20:07.880> function<00:20:08.330> or<00:20:08.420> whatever 00:20:08.530 --> 00:20:08.540 align:start position:0% with token fallback function or whatever 00:20:08.540 --> 00:20:10.320 align:start position:0% with token fallback function or whatever I<00:20:08.720> call<00:20:08.990> so<00:20:09.470> everybody<00:20:09.890> has<00:20:10.070> different 00:20:10.320 --> 00:20:10.330 align:start position:0% I call so everybody has different 00:20:10.330 --> 00:20:12.340 align:start position:0% I call so everybody has different function<00:20:11.330> names<00:20:11.510> if<00:20:11.780> I<00:20:11.960> want<00:20:12.170> to<00:20:12.230> have<00:20:12.320> a 00:20:12.340 --> 00:20:12.350 align:start position:0% function names if I want to have a 00:20:12.350 --> 00:20:15.430 align:start position:0% function names if I want to have a generic<00:20:12.650> account<00:20:13.610> like<00:20:13.940> it<00:20:14.120> in<00:20:14.180> 75<00:20:14.690> I<00:20:14.900> run<00:20:15.200> into 00:20:15.430 --> 00:20:15.440 align:start position:0% generic account like it in 75 I run into 00:20:15.440 --> 00:20:17.050 align:start position:0% generic account like it in 75 I run into the<00:20:15.500> problem<00:20:15.830> that<00:20:15.860> that<00:20:16.520> I<00:20:16.640> have<00:20:16.850> to 00:20:17.050 --> 00:20:17.060 align:start position:0% the problem that that I have to 00:20:17.060 --> 00:20:18.400 align:start position:0% the problem that that I have to implement<00:20:17.510> at<00:20:17.600> least<00:20:17.780> like<00:20:17.930> five<00:20:18.140> different 00:20:18.400 --> 00:20:18.410 align:start position:0% implement at least like five different 00:20:18.410 --> 00:20:20.920 align:start position:0% implement at least like five different functions<00:20:18.980> to<00:20:19.220> receive<00:20:20.090> different<00:20:20.630> type<00:20:20.900> of 00:20:20.920 --> 00:20:20.930 align:start position:0% functions to receive different type of 00:20:20.930 --> 00:20:24.190 align:start position:0% functions to receive different type of tokens<00:20:21.410> or<00:20:21.590> entities<00:20:22.210> if<00:20:23.210> we<00:20:23.480> use<00:20:23.690> a<00:20:23.870> universal 00:20:24.190 --> 00:20:24.200 align:start position:0% tokens or entities if we use a universal 00:20:24.200 --> 00:20:28.320 align:start position:0% tokens or entities if we use a universal receiver<00:20:24.850> is<00:20:25.850> the<00:20:26.180> one<00:20:26.480> common<00:20:26.990> function<00:20:27.470> name 00:20:28.320 --> 00:20:28.330 align:start position:0% receiver is the one common function name 00:20:28.330 --> 00:20:29.970 align:start position:0% receiver is the one common function name the<00:20:28.390> type<00:20:28.659> and<00:20:28.899> some<00:20:29.019> data<00:20:29.200> you<00:20:29.380> passed<00:20:29.740> with 00:20:29.970 --> 00:20:29.980 align:start position:0% the type and some data you passed with 00:20:29.980 --> 00:20:33.930 align:start position:0% the type and some data you passed with it<00:20:30.510> you<00:20:31.510> can<00:20:31.890> be<00:20:32.890> you<00:20:33.220> are<00:20:33.309> able<00:20:33.580> to<00:20:33.610> receive 00:20:33.930 --> 00:20:33.940 align:start position:0% it you can be you are able to receive 00:20:33.940 --> 00:20:36.210 align:start position:0% it you can be you are able to receive everything<00:20:34.299> even<00:20:34.960> future<00:20:35.260> assets<00:20:35.769> because 00:20:36.210 --> 00:20:36.220 align:start position:0% everything even future assets because 00:20:36.220 --> 00:20:38.759 align:start position:0% everything even future assets because you<00:20:36.340> could<00:20:36.490> operate<00:20:36.669> either<00:20:37.120> this<00:20:37.419> part<00:20:37.779> that 00:20:38.759 --> 00:20:38.769 align:start position:0% you could operate either this part that 00:20:38.769 --> 00:20:41.399 align:start position:0% you could operate either this part that receive<00:20:39.159> stuff<00:20:39.519> or<00:20:40.269> just<00:20:40.750> let<00:20:40.929> your<00:20:41.049> interface 00:20:41.399 --> 00:20:41.409 align:start position:0% receive stuff or just let your interface 00:20:41.409 --> 00:20:44.039 align:start position:0% receive stuff or just let your interface deal<00:20:41.679> with<00:20:41.890> whatever<00:20:42.070> you<00:20:42.370> received<00:20:42.870> so<00:20:43.870> the 00:20:44.039 --> 00:20:44.049 align:start position:0% deal with whatever you received so the 00:20:44.049 --> 00:20:45.779 align:start position:0% deal with whatever you received so the universal<00:20:44.620> receiver<00:20:44.890> is<00:20:45.100> a<00:20:45.130> very<00:20:45.429> incremental 00:20:45.779 --> 00:20:45.789 align:start position:0% universal receiver is a very incremental 00:20:45.789 --> 00:20:48.539 align:start position:0% universal receiver is a very incremental piece<00:20:46.299> in<00:20:46.630> an<00:20:47.230> on<00:20:47.620> chain<00:20:47.799> account<00:20:48.100> for<00:20:48.309> example 00:20:48.539 --> 00:20:48.549 align:start position:0% piece in an on chain account for example 00:20:48.549 --> 00:20:50.370 align:start position:0% piece in an on chain account for example and<00:20:49.240> that's<00:20:49.419> something<00:20:49.659> we've<00:20:49.840> proposed<00:20:50.200> in 00:20:50.370 --> 00:20:50.380 align:start position:0% and that's something we've proposed in 00:20:50.380 --> 00:20:52.470 align:start position:0% and that's something we've proposed in our<00:20:50.500> standards<00:20:51.429> repository<00:20:52.000> because<00:20:52.360> it 00:20:52.470 --> 00:20:52.480 align:start position:0% our standards repository because it 00:20:52.480 --> 00:20:55.440 align:start position:0% our standards repository because it looks<00:20:52.990> our<00:20:53.200> standards<00:20:53.769> process<00:20:54.220> LSP<00:20:54.789> so 00:20:55.440 --> 00:20:55.450 align:start position:0% looks our standards process LSP so 00:20:55.450 --> 00:20:58.110 align:start position:0% looks our standards process LSP so that's<00:20:55.690> very<00:20:55.899> much<00:20:56.049> like<00:20:56.230> the<00:20:57.130> EIP<00:20:57.340> repository 00:20:58.110 --> 00:20:58.120 align:start position:0% that's very much like the EIP repository 00:20:58.120 --> 00:21:13.110 align:start position:0% that's very much like the EIP repository just<00:20:59.019> that<00:20:59.289> is<00:21:10.919> so<00:21:11.919> the<00:21:12.460> only<00:21:12.490> difference<00:21:13.000> is 00:21:13.110 --> 00:21:13.120 align:start position:0% just that is so the only difference is 00:21:13.120 --> 00:21:16.440 align:start position:0% just that is so the only difference is that<00:21:13.240> it's<00:21:13.419> a<00:21:14.130> it's<00:21:15.130> the<00:21:15.820> blockchain<00:21:16.059> around 00:21:16.440 --> 00:21:16.450 align:start position:0% that it's a it's the blockchain around 00:21:16.450 --> 00:21:18.269 align:start position:0% that it's a it's the blockchain around this<00:21:16.570> lifestyle<00:21:16.960> arena<00:21:17.350> so<00:21:17.559> we<00:21:17.679> can<00:21:17.860> discuss 00:21:18.269 --> 00:21:18.279 align:start position:0% this lifestyle arena so we can discuss 00:21:18.279 --> 00:21:20.610 align:start position:0% this lifestyle arena so we can discuss in<00:21:18.490> a<00:21:18.549> more<00:21:18.760> calm<00:21:19.000> space<00:21:19.330> and<00:21:19.630> it's<00:21:20.440> not 00:21:20.610 --> 00:21:20.620 align:start position:0% in a more calm space and it's not 00:21:20.620 --> 00:21:23.789 align:start position:0% in a more calm space and it's not already<00:21:20.919> so<00:21:21.130> totally<00:21:21.789> busy<00:21:22.320> with<00:21:23.320> a<00:21:23.529> lot<00:21:23.710> of 00:21:23.789 --> 00:21:23.799 align:start position:0% already so totally busy with a lot of 00:21:23.799 --> 00:21:25.980 align:start position:0% already so totally busy with a lot of competing<00:21:24.279> standards<00:21:24.940> we<00:21:25.450> are<00:21:25.630> in<00:21:25.779> these 00:21:25.980 --> 00:21:25.990 align:start position:0% competing standards we are in these 00:21:25.990 --> 00:21:28.289 align:start position:0% competing standards we are in these standards<00:21:26.440> warm<00:21:26.830> you<00:21:27.279> know<00:21:27.309> everybody<00:21:28.149> has 00:21:28.289 --> 00:21:28.299 align:start position:0% standards warm you know everybody has 00:21:28.299 --> 00:21:29.850 align:start position:0% standards warm you know everybody has the<00:21:28.480> better<00:21:28.659> centers<00:21:29.169> and<00:21:29.380> we<00:21:29.559> don't<00:21:29.740> talk 00:21:29.850 --> 00:21:29.860 align:start position:0% the better centers and we don't talk 00:21:29.860 --> 00:21:33.210 align:start position:0% the better centers and we don't talk anymore<00:21:29.919> about<00:21:30.960> more<00:21:31.960> complex<00:21:32.559> interaction 00:21:33.210 --> 00:21:33.220 align:start position:0% anymore about more complex interaction 00:21:33.220 --> 00:21:34.860 align:start position:0% anymore about more complex interaction models<00:21:33.580> and<00:21:33.820> the<00:21:34.389> thing<00:21:34.570> you<00:21:34.600> have<00:21:34.750> got<00:21:34.840> a 00:21:34.860 --> 00:21:34.870 align:start position:0% models and the thing you have got a 00:21:34.870 --> 00:21:36.750 align:start position:0% models and the thing you have got a standard<00:21:35.200> scenario<00:21:35.710> and<00:21:35.919> also<00:21:36.250> or<00:21:36.399> the<00:21:36.519> LS 00:21:36.750 --> 00:21:36.760 align:start position:0% standard scenario and also or the LS 00:21:36.760 --> 00:21:39.360 align:start position:0% standard scenario and also or the LS piece<00:21:37.000> we<00:21:37.179> promote<00:21:37.659> promote<00:21:38.080> here<00:21:38.529> is<00:21:38.679> that<00:21:39.220> we 00:21:39.360 --> 00:21:39.370 align:start position:0% piece we promote promote here is that we 00:21:39.370 --> 00:21:41.009 align:start position:0% piece we promote promote here is that we think<00:21:39.399> not<00:21:39.820> only<00:21:39.880> about<00:21:40.120> the<00:21:40.419> individual 00:21:41.009 --> 00:21:41.019 align:start position:0% think not only about the individual 00:21:41.019 --> 00:21:42.779 align:start position:0% think not only about the individual standards<00:21:41.559> but<00:21:41.830> how<00:21:42.039> this<00:21:42.220> works<00:21:42.460> in<00:21:42.610> concert 00:21:42.779 --> 00:21:42.789 align:start position:0% standards but how this works in concert 00:21:42.789 --> 00:21:45.659 align:start position:0% standards but how this works in concert you<00:21:43.450> know<00:21:43.600> how<00:21:44.139> can<00:21:44.440> I<00:21:44.470> make<00:21:44.620> sure<00:21:44.950> that<00:21:44.980> I<00:21:45.460> can 00:21:45.659 --> 00:21:45.669 align:start position:0% you know how can I make sure that I can 00:21:45.669 --> 00:21:47.549 align:start position:0% you know how can I make sure that I can easily<00:21:46.059> read<00:21:46.269> a<00:21:46.299> portfolio<00:21:46.960> of<00:21:46.990> a<00:21:47.320> given 00:21:47.549 --> 00:21:47.559 align:start position:0% easily read a portfolio of a given 00:21:47.559 --> 00:21:50.310 align:start position:0% easily read a portfolio of a given address<00:21:47.880> how<00:21:48.880> tokens<00:21:49.389> interactive<00:21:49.870> identity 00:21:50.310 --> 00:21:50.320 align:start position:0% address how tokens interactive identity 00:21:50.320 --> 00:21:52.230 align:start position:0% address how tokens interactive identity is<00:21:50.380> how<00:21:50.559> identities<00:21:51.100> can<00:21:51.309> receive<00:21:51.639> somewhat 00:21:52.230 --> 00:21:52.240 align:start position:0% is how identities can receive somewhat 00:21:52.240 --> 00:21:54.750 align:start position:0% is how identities can receive somewhat different<00:21:52.600> tokens<00:21:52.779> into<00:21:53.230> the<00:21:53.350> future<00:21:53.740> ones<00:21:53.950> so 00:21:54.750 --> 00:21:54.760 align:start position:0% different tokens into the future ones so 00:21:54.760 --> 00:21:56.190 align:start position:0% different tokens into the future ones so there's<00:21:54.940> a<00:21:54.970> lot<00:21:55.120> of<00:21:55.269> things<00:21:55.510> we<00:21:55.690> should<00:21:55.720> think 00:21:56.190 --> 00:21:56.200 align:start position:0% there's a lot of things we should think 00:21:56.200 --> 00:21:58.769 align:start position:0% there's a lot of things we should think more<00:21:56.380> about<00:21:56.559> how<00:21:56.889> stuff<00:21:57.490> works<00:21:57.519> together<00:21:58.000> and 00:21:58.769 --> 00:21:58.779 align:start position:0% more about how stuff works together and 00:21:58.779 --> 00:22:00.060 align:start position:0% more about how stuff works together and not<00:21:59.049> just<00:21:59.200> everybody<00:21:59.590> comes<00:21:59.799> up<00:21:59.889> with<00:22:00.039> that 00:22:00.060 --> 00:22:00.070 align:start position:0% not just everybody comes up with that 00:22:00.070 --> 00:22:02.370 align:start position:0% not just everybody comes up with that standard<00:22:00.429> now<00:22:01.419> we<00:22:01.480> have<00:22:01.720> one<00:22:01.960> little<00:22:02.230> more 00:22:02.370 --> 00:22:02.380 align:start position:0% standard now we have one little more 00:22:02.380 --> 00:22:05.850 align:start position:0% standard now we have one little more building<00:22:02.710> block<00:22:02.950> but<00:22:04.289> five<00:22:05.289> of<00:22:05.440> ten<00:22:05.649> you<00:22:05.830> know 00:22:05.850 --> 00:22:05.860 align:start position:0% building block but five of ten you know 00:22:05.860 --> 00:22:07.350 align:start position:0% building block but five of ten you know and<00:22:06.220> then<00:22:06.340> they<00:22:06.700> all<00:22:06.820> don't<00:22:06.970> work<00:22:07.179> together 00:22:07.350 --> 00:22:07.360 align:start position:0% and then they all don't work together 00:22:07.360 --> 00:22:10.289 align:start position:0% and then they all don't work together and<00:22:07.860> accounts<00:22:08.860> reading<00:22:09.399> talk<00:22:10.000> with<00:22:10.179> each 00:22:10.289 --> 00:22:10.299 align:start position:0% and accounts reading talk with each 00:22:10.299 --> 00:22:11.519 align:start position:0% and accounts reading talk with each other<00:22:10.450> super<00:22:10.809> complicated 00:22:11.519 --> 00:22:11.529 align:start position:0% other super complicated 00:22:11.529 --> 00:22:14.370 align:start position:0% other super complicated totally<00:22:12.490> hacky<00:22:12.929> so<00:22:13.929> we<00:22:14.049> wanna<00:22:14.260> have 00:22:14.370 --> 00:22:14.380 align:start position:0% totally hacky so we wanna have 00:22:14.380 --> 00:22:16.289 align:start position:0% totally hacky so we wanna have compatibility<00:22:15.130> means<00:22:15.519> we<00:22:15.820> need<00:22:16.000> standards 00:22:16.289 --> 00:22:16.299 align:start position:0% compatibility means we need standards 00:22:16.299 --> 00:22:19.950 align:start position:0% compatibility means we need standards that<00:22:16.690> kind<00:22:16.929> of<00:22:16.990> fit<00:22:17.620> together<00:22:18.779> that's<00:22:19.779> already 00:22:19.950 --> 00:22:19.960 align:start position:0% that kind of fit together that's already 00:22:19.960 --> 00:22:24.029 align:start position:0% that kind of fit together that's already a<00:22:20.080> question<00:22:20.440> here 00:22:24.029 --> 00:22:24.039 align:start position:0% 00:22:24.039 --> 00:22:28.019 align:start position:0% hi<00:22:25.169> we<00:22:26.169> can<00:22:26.409> say<00:22:26.679> real<00:22:26.979> words<00:22:27.029> applications 00:22:28.019 --> 00:22:28.029 align:start position:0% hi we can say real words applications 00:22:28.029 --> 00:22:40.379 align:start position:0% hi we can say real words applications and<00:22:28.629> posted<00:22:29.529> as<00:22:29.710> account<00:22:38.129> about<00:22:39.210> what<00:22:40.210> about 00:22:40.379 --> 00:22:40.389 align:start position:0% and posted as account about what about 00:22:40.389 --> 00:22:46.799 align:start position:0% and posted as account about what about doing<00:22:41.139> library 00:22:46.799 --> 00:22:46.809 align:start position:0% 00:22:46.809 --> 00:23:30.740 align:start position:0% but<00:22:47.050> it's<00:22:47.320> way<00:22:47.800> like<00:22:48.190> vacation 00:23:30.740 --> 00:23:30.750 align:start position:0% 00:23:30.750 --> 00:23:33.150 align:start position:0% so<00:23:31.750> basically<00:23:32.080> libraries<00:23:32.680> force<00:23:32.920> month 00:23:33.150 --> 00:23:33.160 align:start position:0% so basically libraries force month 00:23:33.160 --> 00:23:34.860 align:start position:0% so basically libraries force month contact<00:23:33.550> I<00:23:33.580> mean<00:23:33.730> open<00:23:34.000> setting<00:23:34.510> is<00:23:34.630> kind<00:23:34.840> of 00:23:34.860 --> 00:23:34.870 align:start position:0% contact I mean open setting is kind of 00:23:34.870 --> 00:23:37.340 align:start position:0% contact I mean open setting is kind of like<00:23:35.050> the<00:23:35.170> biggest<00:23:35.350> library<00:23:35.860> for 00:23:37.340 --> 00:23:37.350 align:start position:0% like the biggest library for 00:23:37.350 --> 00:23:39.300 align:start position:0% like the biggest library for standardized<00:23:38.350> smartphone<00:23:38.770> works<00:23:38.920> we<00:23:39.130> have 00:23:39.300 --> 00:23:39.310 align:start position:0% standardized smartphone works we have 00:23:39.310 --> 00:23:41.520 align:start position:0% standardized smartphone works we have and<00:23:40.090> I'm<00:23:40.210> really<00:23:40.240> understanding<00:23:41.080> question 00:23:41.520 --> 00:23:41.530 align:start position:0% and I'm really understanding question 00:23:41.530 --> 00:23:45.420 align:start position:0% and I'm really understanding question it's<00:23:42.370> something<00:23:42.850> like<00:23:43.000> an<00:23:43.090> open<00:23:43.390> source<00:23:44.430> I 00:23:45.420 --> 00:23:45.430 align:start position:0% it's something like an open source I 00:23:45.430 --> 00:23:48.150 align:start position:0% it's something like an open source I mean<00:23:46.440> something<00:23:47.440> is<00:23:47.500> kind<00:23:47.650> of<00:23:47.740> open<00:23:48.010> source 00:23:48.150 --> 00:23:48.160 align:start position:0% mean something is kind of open source 00:23:48.160 --> 00:23:51.030 align:start position:0% mean something is kind of open source but<00:23:49.110> you're<00:23:50.110> talking<00:23:50.350> about<00:23:50.440> like<00:23:50.680> how<00:23:50.830> can 00:23:51.030 --> 00:23:51.040 align:start position:0% but you're talking about like how can 00:23:51.040 --> 00:23:52.380 align:start position:0% but you're talking about like how can other<00:23:51.190> people<00:23:51.280> contribute<00:23:51.910> with<00:23:52.060> different 00:23:52.380 --> 00:23:52.390 align:start position:0% other people contribute with different 00:23:52.390 --> 00:23:55.760 align:start position:0% other people contribute with different pieces<00:23:52.570> or<00:23:52.810> how<00:23:53.200> do<00:23:53.260> you<00:23:53.380> have 00:23:55.760 --> 00:23:55.770 align:start position:0% 00:23:55.770 --> 00:24:17.300 align:start position:0% like<00:23:56.840> perturbation<00:23:57.840> in 00:24:17.300 --> 00:24:17.310 align:start position:0% 00:24:17.310 --> 00:24:20.130 align:start position:0% okay<00:24:18.340> so<00:24:19.060> if<00:24:19.180> you<00:24:19.270> want<00:24:19.450> to<00:24:19.480> kind<00:24:19.930> of<00:24:19.960> like 00:24:20.130 --> 00:24:20.140 align:start position:0% okay so if you want to kind of like 00:24:20.140 --> 00:24:21.870 align:start position:0% okay so if you want to kind of like attention<00:24:20.920> formation<00:24:21.370> like<00:24:21.430> this<00:24:21.640> it 00:24:21.870 --> 00:24:21.880 align:start position:0% attention formation like this it 00:24:21.880 --> 00:24:24.780 align:start position:0% attention formation like this it obviously<00:24:22.240> belongs<00:24:22.570> into<00:24:22.900> the<00:24:23.020> set<00:24:23.410> data<00:24:23.790> the 00:24:24.780 --> 00:24:24.790 align:start position:0% obviously belongs into the set data the 00:24:24.790 --> 00:24:27.030 align:start position:0% obviously belongs into the set data the key<00:24:24.910> value<00:24:25.180> store<00:24:25.620> if<00:24:26.620> you<00:24:26.740> want<00:24:26.890> to<00:24:26.950> have 00:24:27.030 --> 00:24:27.040 align:start position:0% key value store if you want to have 00:24:27.040 --> 00:24:29.190 align:start position:0% key value store if you want to have email<00:24:27.340> verification<00:24:27.940> you<00:24:28.720> always<00:24:28.960> have<00:24:29.080> to 00:24:29.190 --> 00:24:29.200 align:start position:0% email verification you always have to 00:24:29.200 --> 00:24:31.050 align:start position:0% email verification you always have to think<00:24:29.350> about<00:24:29.500> what<00:24:29.740> this<00:24:30.310> is<00:24:30.520> you<00:24:30.700> launch<00:24:30.880> an 00:24:31.050 --> 00:24:31.060 align:start position:0% think about what this is you launch an 00:24:31.060 --> 00:24:34.050 align:start position:0% think about what this is you launch an account<00:24:31.360> so<00:24:31.750> you<00:24:32.290> have<00:24:32.740> continued<00:24:33.250> teach<00:24:33.880> you 00:24:34.050 --> 00:24:34.060 align:start position:0% account so you have continued teach you 00:24:34.060 --> 00:24:35.820 align:start position:0% account so you have continued teach you you<00:24:34.150> know<00:24:34.270> so<00:24:34.450> of<00:24:34.600> what<00:24:35.200> they<00:24:35.410> shoe<00:24:35.530> that 00:24:35.820 --> 00:24:35.830 align:start position:0% you know so of what they shoe that 00:24:35.830 --> 00:24:37.860 align:start position:0% you know so of what they shoe that shouldn't<00:24:36.190> do<00:24:36.310> what<00:24:36.430> I<00:24:36.550> mean<00:24:36.730> for<00:24:37.360> couple 00:24:37.860 --> 00:24:37.870 align:start position:0% shouldn't do what I mean for couple 00:24:37.870 --> 00:24:39.480 align:start position:0% shouldn't do what I mean for couple through<00:24:38.110> interfaces<00:24:38.740> we<00:24:38.860> know<00:24:39.010> that<00:24:39.220> when<00:24:39.400> we 00:24:39.480 --> 00:24:39.490 align:start position:0% through interfaces we know that when we 00:24:39.490 --> 00:24:41.100 align:start position:0% through interfaces we know that when we post<00:24:39.730> something<00:24:39.970> Instagram<00:24:40.630> it's<00:24:40.870> pretty 00:24:41.100 --> 00:24:41.110 align:start position:0% post something Instagram it's pretty 00:24:41.110 --> 00:24:43.290 align:start position:0% post something Instagram it's pretty public<00:24:41.530> so<00:24:42.130> people<00:24:42.160> are<00:24:42.580> not<00:24:42.700> posting<00:24:43.150> their 00:24:43.290 --> 00:24:43.300 align:start position:0% public so people are not posting their 00:24:43.300 --> 00:24:46.500 align:start position:0% public so people are not posting their private<00:24:43.720> naked<00:24:44.260> pictures<00:24:44.670> so<00:24:45.670> here<00:24:46.240> we<00:24:46.390> have 00:24:46.500 --> 00:24:46.510 align:start position:0% private naked pictures so here we have 00:24:46.510 --> 00:24:48.030 align:start position:0% private naked pictures so here we have to<00:24:46.630> treat<00:24:46.810> it<00:24:46.840> the<00:24:46.990> same<00:24:47.020> you're<00:24:47.530> posting<00:24:47.920> it 00:24:48.030 --> 00:24:48.040 align:start position:0% to treat it the same you're posting it 00:24:48.040 --> 00:24:50.520 align:start position:0% to treat it the same you're posting it unchanged<00:24:48.490> so<00:24:48.760> it<00:24:49.090> could<00:24:49.330> potentially<00:24:50.170> be 00:24:50.520 --> 00:24:50.530 align:start position:0% unchanged so it could potentially be 00:24:50.530 --> 00:24:53.160 align:start position:0% unchanged so it could potentially be read<00:24:50.890> by<00:24:51.100> people<00:24:51.130> so<00:24:52.090> also<00:24:52.600> making<00:24:52.840> sure<00:24:52.930> that 00:24:53.160 --> 00:24:53.170 align:start position:0% read by people so also making sure that 00:24:53.170 --> 00:24:55.380 align:start position:0% read by people so also making sure that what<00:24:53.350> you<00:24:53.500> would<00:24:53.740> like<00:24:54.460> that<00:24:54.760> this<00:24:55.090> is<00:24:55.240> a 00:24:55.380 --> 00:24:55.390 align:start position:0% what you would like that this is a 00:24:55.390 --> 00:24:58.020 align:start position:0% what you would like that this is a public<00:24:55.690> persona<00:24:56.260> Ukrainian<00:24:57.100> here<00:24:57.400> versus 00:24:58.020 --> 00:24:58.030 align:start position:0% public persona Ukrainian here versus 00:24:58.030 --> 00:25:00.090 align:start position:0% public persona Ukrainian here versus maybe<00:24:58.210> a<00:24:58.300> private<00:24:58.540> persona<00:24:59.020> if<00:24:59.350> you<00:24:59.830> want<00:25:00.040> to 00:25:00.090 --> 00:25:00.100 align:start position:0% maybe a private persona if you want to 00:25:00.100 --> 00:25:01.830 align:start position:0% maybe a private persona if you want to verify<00:25:00.220> your<00:25:00.550> manifest<00:25:01.120> and<00:25:01.360> I<00:25:01.480> guess<00:25:01.660> this 00:25:01.830 --> 00:25:01.840 align:start position:0% verify your manifest and I guess this 00:25:01.840 --> 00:25:08.760 align:start position:0% verify your manifest and I guess this service<00:25:02.530> book<00:25:02.710> should<00:25:02.890> verify<00:25:03.250> that 00:25:08.760 --> 00:25:08.770 align:start position:0% 00:25:08.770 --> 00:25:11.760 align:start position:0% and<00:25:09.340> you<00:25:09.550> could<00:25:09.700> simply<00:25:09.970> attach<00:25:10.240> a<00:25:10.770> signed 00:25:11.760 --> 00:25:11.770 align:start position:0% and you could simply attach a signed 00:25:11.770 --> 00:25:14.010 align:start position:0% and you could simply attach a signed message<00:25:12.250> into<00:25:13.060> one<00:25:13.240> of<00:25:13.300> the<00:25:13.390> key<00:25:13.540> value<00:25:13.780> store 00:25:14.010 --> 00:25:14.020 align:start position:0% message into one of the key value store 00:25:14.020 --> 00:25:16.080 align:start position:0% message into one of the key value store which<00:25:14.320> says<00:25:14.560> okay<00:25:14.890> we<00:25:15.130> check<00:25:15.370> the<00:25:15.550> email<00:25:15.820> and 00:25:16.080 --> 00:25:16.090 align:start position:0% which says okay we check the email and 00:25:16.090 --> 00:25:18.720 align:start position:0% which says okay we check the email and SMS<00:25:16.330> play<00:25:17.020> yeah<00:25:17.560> that's<00:25:17.980> what<00:25:18.190> we<00:25:18.280> would<00:25:18.430> do<00:25:18.580> I 00:25:18.720 --> 00:25:18.730 align:start position:0% SMS play yeah that's what we would do I 00:25:18.730 --> 00:25:21.240 align:start position:0% SMS play yeah that's what we would do I mean<00:25:18.910> either<00:25:19.630> this<00:25:20.020> or<00:25:20.290> a<00:25:20.410> some<00:25:20.830> kind<00:25:21.010> of<00:25:21.070> like 00:25:21.240 --> 00:25:21.250 align:start position:0% mean either this or a some kind of like 00:25:21.250 --> 00:25:23.040 align:start position:0% mean either this or a some kind of like registry<00:25:21.790> which<00:25:22.180> does<00:25:22.450> like<00:25:22.630> a<00:25:22.660> verification 00:25:23.040 --> 00:25:23.050 align:start position:0% registry which does like a verification 00:25:23.050 --> 00:25:25.200 align:start position:0% registry which does like a verification someone<00:25:23.980> you<00:25:24.100> service<00:25:24.460> could<00:25:24.610> end<00:25:24.850> the<00:25:24.940> next 00:25:25.200 --> 00:25:25.210 align:start position:0% someone you service could end the next 00:25:25.210 --> 00:25:26.160 align:start position:0% someone you service could end the next rest<00:25:25.360> month<00:25:25.570> come<00:25:25.720> back<00:25:25.840> with<00:25:25.960> just 00:25:26.160 --> 00:25:26.170 align:start position:0% rest month come back with just 00:25:26.170 --> 00:25:28.560 align:start position:0% rest month come back with just verification<00:25:26.770> and<00:25:26.950> then<00:25:27.460> in<00:25:27.550> the<00:25:27.670> key<00:25:27.880> value 00:25:28.560 --> 00:25:28.570 align:start position:0% verification and then in the key value 00:25:28.570 --> 00:25:30.600 align:start position:0% verification and then in the key value store<00:25:28.780> you<00:25:28.900> simply<00:25:29.230> link<00:25:29.560> to<00:25:29.920> that<00:25:30.040> registry 00:25:30.600 --> 00:25:30.610 align:start position:0% store you simply link to that registry 00:25:30.610 --> 00:25:32.910 align:start position:0% store you simply link to that registry that<00:25:30.940> could<00:25:31.420> be<00:25:31.540> another<00:25:31.720> way<00:25:31.840> so<00:25:32.230> the<00:25:32.590> beauty 00:25:32.910 --> 00:25:32.920 align:start position:0% that could be another way so the beauty 00:25:32.920 --> 00:25:34.770 align:start position:0% that could be another way so the beauty of<00:25:32.950> this<00:25:33.220> key<00:25:33.370> value<00:25:33.400> stores<00:25:33.880> it<00:25:34.150> can<00:25:34.450> contain 00:25:34.770 --> 00:25:34.780 align:start position:0% of this key value stores it can contain 00:25:34.780 --> 00:25:36.570 align:start position:0% of this key value stores it can contain data<00:25:34.990> on<00:25:35.230> its<00:25:35.350> own<00:25:35.530> but<00:25:36.040> it<00:25:36.130> could<00:25:36.280> be<00:25:36.400> also 00:25:36.570 --> 00:25:36.580 align:start position:0% data on its own but it could be also 00:25:36.580 --> 00:25:38.640 align:start position:0% data on its own but it could be also simply<00:25:36.940> referencing<00:25:37.570> other<00:25:37.690> places<00:25:37.990> to<00:25:38.470> go 00:25:38.640 --> 00:25:38.650 align:start position:0% simply referencing other places to go 00:25:38.650 --> 00:25:40.860 align:start position:0% simply referencing other places to go look<00:25:38.860> and<00:25:39.070> if<00:25:40.060> we<00:25:40.240> standardize<00:25:40.720> these 00:25:40.860 --> 00:25:40.870 align:start position:0% look and if we standardize these 00:25:40.870 --> 00:25:44.670 align:start position:0% look and if we standardize these processes<00:25:41.530> we<00:25:41.920> exactly<00:25:42.280> know<00:25:42.750> what<00:25:43.750> to<00:25:43.900> do<00:25:44.020> now 00:25:44.670 --> 00:25:44.680 align:start position:0% processes we exactly know what to do now 00:25:44.680 --> 00:26:14.430 align:start position:0% processes we exactly know what to do now -<00:25:44.860> each<00:25:45.370> Kiba<00:25:45.910> store<00:25:53.130> that's<00:26:10.020> yes 00:26:14.430 --> 00:26:14.440 align:start position:0% 00:26:14.440 --> 00:26:17.230 align:start position:0% instead<00:26:15.440> of<00:26:15.559> just<00:26:15.679> happy<00:26:15.889> no<00:26:16.009> statement<00:26:16.789> the 00:26:17.230 --> 00:26:17.240 align:start position:0% instead of just happy no statement the 00:26:17.240 --> 00:26:19.470 align:start position:0% instead of just happy no statement the proxy<00:26:17.600> and<00:26:17.750> control<00:26:18.110> still<00:26:18.950> unchanged 00:26:19.470 --> 00:26:19.480 align:start position:0% proxy and control still unchanged 00:26:19.480 --> 00:26:22.960 align:start position:0% proxy and control still unchanged because<00:26:20.480> you<00:26:20.570> can<00:26:20.720> upgrade<00:26:21.019> your<00:26:21.769> new<00:26:22.639> key 00:26:22.960 --> 00:26:22.970 align:start position:0% because you can upgrade your new key 00:26:22.970 --> 00:26:27.700 align:start position:0% because you can upgrade your new key management<00:26:23.980> I<00:26:25.600> mean<00:26:26.600> you<00:26:26.720> can<00:26:26.870> build<00:26:27.019> it<00:26:27.259> then 00:26:27.700 --> 00:26:27.710 align:start position:0% management I mean you can build it then 00:26:27.710 --> 00:26:29.379 align:start position:0% management I mean you can build it then it's<00:26:27.860> all<00:26:28.009> in<00:26:28.159> one<00:26:28.340> contract<00:26:28.789> from<00:26:29.149> some<00:26:29.299> of 00:26:29.379 --> 00:26:29.389 align:start position:0% it's all in one contract from some of 00:26:29.389 --> 00:26:31.840 align:start position:0% it's all in one contract from some of the<00:26:29.450> own<00:26:29.570> address<00:26:29.779> could<00:26:30.049> be<00:26:30.230> itself<00:26:30.850> you 00:26:31.840 --> 00:26:31.850 align:start position:0% the own address could be itself you 00:26:31.850 --> 00:26:33.129 align:start position:0% the own address could be itself you could<00:26:32.029> make<00:26:32.240> enough<00:26:32.539> I<00:26:32.659> mean<00:26:32.779> actually 00:26:33.129 --> 00:26:33.139 align:start position:0% could make enough I mean actually 00:26:33.139 --> 00:26:37.029 align:start position:0% could make enough I mean actually happily<00:26:34.039> on<00:26:34.190> for<00:26:34.669> me<00:26:34.880> who<00:26:35.840> sooner<00:26:36.710> wallet 00:26:37.029 --> 00:26:37.039 align:start position:0% happily on for me who sooner wallet 00:26:37.039 --> 00:26:38.940 align:start position:0% happily on for me who sooner wallet build<00:26:37.399> exactly<00:26:37.909> a<00:26:37.940> seven<00:26:38.299> to<00:26:38.389> five 00:26:38.940 --> 00:26:38.950 align:start position:0% build exactly a seven to five 00:26:38.950 --> 00:26:41.169 align:start position:0% build exactly a seven to five upgradeable<00:26:39.950> contract<00:26:40.340> where<00:26:40.639> you<00:26:40.970> basically 00:26:41.169 --> 00:26:41.179 align:start position:0% upgradeable contract where you basically 00:26:41.179 --> 00:26:44.440 align:start position:0% upgradeable contract where you basically have<00:26:41.480> one<00:26:41.990> address<00:26:42.889> which<00:26:43.250> contains<00:26:43.820> the<00:26:44.090> key 00:26:44.440 --> 00:26:44.450 align:start position:0% have one address which contains the key 00:26:44.450 --> 00:26:47.320 align:start position:0% have one address which contains the key values<00:26:44.750> to<00:26:44.899> an<00:26:45.019> an<00:26:45.230> owner<00:26:45.500> and<00:26:45.860> an<00:26:46.669> additional 00:26:47.320 --> 00:26:47.330 align:start position:0% values to an an owner and an additional 00:26:47.330 --> 00:26:49.840 align:start position:0% values to an an owner and an additional like<00:26:47.809> management<00:26:48.200> keys<00:26:48.559> systems<00:26:49.549> you<00:26:49.759> can 00:26:49.840 --> 00:26:49.850 align:start position:0% like management keys systems you can 00:26:49.850 --> 00:26:52.119 align:start position:0% like management keys systems you can build<00:26:50.090> it<00:26:50.240> as<00:26:50.360> well<00:26:50.539> and<00:26:50.750> on<00:26:51.740> the<00:26:51.860> end<00:26:52.009> you 00:26:52.119 --> 00:26:52.129 align:start position:0% build it as well and on the end you 00:26:52.129 --> 00:26:53.649 align:start position:0% build it as well and on the end you wallet<00:26:52.429> only<00:26:52.610> needs<00:26:52.879> all<00:26:53.149> your<00:26:53.179> interface 00:26:53.649 --> 00:26:53.659 align:start position:0% wallet only needs all your interface 00:26:53.659 --> 00:26:55.869 align:start position:0% wallet only needs all your interface only<00:26:53.899> needs<00:26:54.049> to<00:26:54.169> know<00:26:54.200> gets<00:26:54.860> the<00:26:54.980> address<00:26:55.370> it's 00:26:55.869 --> 00:26:55.879 align:start position:0% only needs to know gets the address it's 00:26:55.879 --> 00:26:57.730 align:start position:0% only needs to know gets the address it's the<00:26:56.029> owner<00:26:56.210> is<00:26:56.690> the<00:26:57.019> same<00:26:57.200> Metro<00:26:57.470> so<00:26:57.590> what's 00:26:57.730 --> 00:26:57.740 align:start position:0% the owner is the same Metro so what's 00:26:57.740 --> 00:26:59.139 align:start position:0% the owner is the same Metro so what's the<00:26:57.860> different<00:26:58.129> address<00:26:58.429> and<00:26:58.639> then<00:26:58.789> it<00:26:58.909> has<00:26:59.029> to 00:26:59.139 --> 00:26:59.149 align:start position:0% the different address and then it has to 00:26:59.149 --> 00:27:00.730 align:start position:0% the different address and then it has to look<00:26:59.269> at<00:26:59.419> what<00:26:59.450> standard<00:26:59.929> this<00:27:00.110> is<00:27:00.320> you<00:27:00.620> know 00:27:00.730 --> 00:27:00.740 align:start position:0% look at what standard this is you know 00:27:00.740 --> 00:27:02.740 align:start position:0% look at what standard this is you know what<00:27:01.070> kind<00:27:01.250> of<00:27:01.279> commercial<00:27:01.580> thing<00:27:02.000> it<00:27:02.120> is<00:27:02.269> so 00:27:02.740 --> 00:27:02.750 align:start position:0% what kind of commercial thing it is so 00:27:02.750 --> 00:27:04.990 align:start position:0% what kind of commercial thing it is so you<00:27:02.840> can<00:27:02.870> deal<00:27:03.470> with<00:27:03.529> that<00:27:03.649> as<00:27:03.980> well<00:27:04.129> and<00:27:04.399> then 00:27:04.990 --> 00:27:05.000 align:start position:0% you can deal with that as well and then 00:27:05.000 --> 00:27:07.480 align:start position:0% you can deal with that as well and then you<00:27:05.029> can<00:27:05.120> interact<00:27:05.539> in<00:27:05.659> this<00:27:05.779> account<00:27:06.370> in<00:27:07.370> the 00:27:07.480 --> 00:27:07.490 align:start position:0% you can interact in this account in the 00:27:07.490 --> 00:27:09.430 align:start position:0% you can interact in this account in the simplest<00:27:07.820> form<00:27:07.940> is<00:27:08.269> just<00:27:08.450> a<00:27:08.600> key<00:27:08.750> you<00:27:09.320> know 00:27:09.430 --> 00:27:09.440 align:start position:0% simplest form is just a key you know 00:27:09.440 --> 00:27:13.570 align:start position:0% simplest form is just a key you know which<00:27:09.649> you<00:27:09.769> have<00:27:09.980> in<00:27:10.129> your<00:27:10.250> code<00:27:12.460> but<00:27:13.460> yeah 00:27:13.570 --> 00:27:13.580 align:start position:0% which you have in your code but yeah 00:27:13.580 --> 00:27:15.700 align:start position:0% which you have in your code but yeah could<00:27:13.850> be<00:27:13.879> in<00:27:14.179> the<00:27:14.330> same<00:27:14.480> account<00:27:14.809> I<00:27:15.169> think 00:27:15.700 --> 00:27:15.710 align:start position:0% could be in the same account I think 00:27:15.710 --> 00:27:17.470 align:start position:0% could be in the same account I think keeping<00:27:16.309> it<00:27:16.429> separate<00:27:16.730> makes<00:27:16.940> a<00:27:17.029> lot<00:27:17.149> of<00:27:17.240> sense 00:27:17.470 --> 00:27:17.480 align:start position:0% keeping it separate makes a lot of sense 00:27:17.480 --> 00:27:19.779 align:start position:0% keeping it separate makes a lot of sense because<00:27:17.860> what<00:27:18.860> I<00:27:18.889> see<00:27:19.190> is<00:27:19.309> happening<00:27:19.460> is<00:27:19.759> you 00:27:19.779 --> 00:27:19.789 align:start position:0% because what I see is happening is you 00:27:19.789 --> 00:27:21.460 align:start position:0% because what I see is happening is you have<00:27:19.970> and<00:27:20.210> I<00:27:20.509> know<00:27:20.570> what<00:27:20.750> the<00:27:20.870> time<00:27:21.019> is<00:27:21.049> up<00:27:21.230> and 00:27:21.460 --> 00:27:21.470 align:start position:0% have and I know what the time is up and 00:27:21.470 --> 00:27:24.610 align:start position:0% have and I know what the time is up and I'm<00:27:21.889> just<00:27:22.129> to<00:27:22.279> keep<00:27:22.700> the<00:27:22.820> short<00:27:23.500> this<00:27:24.500> is 00:27:24.610 --> 00:27:24.620 align:start position:0% I'm just to keep the short this is 00:27:24.620 --> 00:27:26.740 align:start position:0% I'm just to keep the short this is permanent<00:27:24.919> account<00:27:25.460> 175<00:27:26.179> is<00:27:26.419> probably 00:27:26.740 --> 00:27:26.750 align:start position:0% permanent account 175 is probably 00:27:26.750 --> 00:27:28.360 align:start position:0% permanent account 175 is probably something<00:27:27.110> we<00:27:27.230> want<00:27:27.440> to<00:27:27.500> keep<00:27:27.830> for<00:27:28.070> a<00:27:28.129> while 00:27:28.360 --> 00:27:28.370 align:start position:0% something we want to keep for a while 00:27:28.370 --> 00:27:31.090 align:start position:0% something we want to keep for a while and<00:27:28.759> use<00:27:29.330> it<00:27:29.509> in<00:27:29.690> maybe<00:27:30.289> some<00:27:30.620> games<00:27:30.919> or 00:27:31.090 --> 00:27:31.100 align:start position:0% and use it in maybe some games or 00:27:31.100 --> 00:27:33.009 align:start position:0% and use it in maybe some games or whatever<00:27:31.399> else<00:27:31.639> so<00:27:31.940> it's<00:27:32.450> a<00:27:32.539> permanent<00:27:32.990> thing 00:27:33.009 --> 00:27:33.019 align:start position:0% whatever else so it's a permanent thing 00:27:33.019 --> 00:27:35.799 align:start position:0% whatever else so it's a permanent thing we<00:27:33.259> want<00:27:33.470> to<00:27:33.529> be<00:27:33.649> secured<00:27:34.100> the<00:27:34.940> key<00:27:35.149> manager<00:27:35.570> is 00:27:35.799 --> 00:27:35.809 align:start position:0% we want to be secured the key manager is 00:27:35.809 --> 00:27:37.450 align:start position:0% we want to be secured the key manager is maybe<00:27:36.049> something<00:27:36.289> we<00:27:36.470> can<00:27:36.620> upgrade<00:27:36.769> over<00:27:37.250> time 00:27:37.450 --> 00:27:37.460 align:start position:0% maybe something we can upgrade over time 00:27:37.460 --> 00:27:38.889 align:start position:0% maybe something we can upgrade over time so<00:27:37.700> having<00:27:37.909> this<00:27:38.090> in<00:27:38.240> a<00:27:38.330> separate<00:27:38.629> smart 00:27:38.889 --> 00:27:38.899 align:start position:0% so having this in a separate smart 00:27:38.899 --> 00:27:42.129 align:start position:0% so having this in a separate smart contract<00:27:39.730> keeps<00:27:40.730> the<00:27:40.909> risk<00:27:41.090> lower<00:27:41.450> for 00:27:42.129 --> 00:27:42.139 align:start position:0% contract keeps the risk lower for 00:27:42.139 --> 00:27:43.899 align:start position:0% contract keeps the risk lower for example<00:27:42.470> the<00:27:42.559> universe<00:27:42.950> receiver<00:27:43.460> contract 00:27:43.899 --> 00:27:43.909 align:start position:0% example the universe receiver contract 00:27:43.909 --> 00:27:45.850 align:start position:0% example the universe receiver contract the<00:27:44.179> contract<00:27:44.539> which<00:27:44.659> knows<00:27:45.139> how<00:27:45.440> to<00:27:45.500> deal 00:27:45.850 --> 00:27:45.860 align:start position:0% the contract which knows how to deal 00:27:45.860 --> 00:27:48.070 align:start position:0% the contract which knows how to deal with<00:27:45.889> stuff<00:27:46.250> you<00:27:46.279> receive<00:27:46.759> should<00:27:47.450> also<00:27:47.690> be<00:27:48.049> a 00:27:48.070 --> 00:27:48.080 align:start position:0% with stuff you receive should also be a 00:27:48.080 --> 00:27:51.549 align:start position:0% with stuff you receive should also be a separate<00:27:48.470> module<00:27:48.679> because<00:27:49.580> I<00:27:49.789> assumed<00:27:50.559> people 00:27:51.549 --> 00:27:51.559 align:start position:0% separate module because I assumed people 00:27:51.559 --> 00:27:53.440 align:start position:0% separate module because I assumed people will<00:27:51.799> have<00:27:51.919> paid<00:27:52.129> that<00:27:52.250> very<00:27:52.549> frequently<00:27:52.820> and 00:27:53.440 --> 00:27:53.450 align:start position:0% will have paid that very frequently and 00:27:53.450 --> 00:27:55.509 align:start position:0% will have paid that very frequently and if<00:27:54.080> you<00:27:54.200> all<00:27:54.320> pack<00:27:54.529> into<00:27:54.679> one<00:27:54.769> account<00:27:55.159> then 00:27:55.509 --> 00:27:55.519 align:start position:0% if you all pack into one account then 00:27:55.519 --> 00:27:57.310 align:start position:0% if you all pack into one account then suddenly<00:27:55.850> all<00:27:56.120> of<00:27:56.149> this<00:27:56.360> code<00:27:56.659> can<00:27:56.929> buy<00:27:57.259> it 00:27:57.310 --> 00:27:57.320 align:start position:0% suddenly all of this code can buy it 00:27:57.320 --> 00:27:59.470 align:start position:0% suddenly all of this code can buy it into<00:27:57.710> the<00:27:57.830> same<00:27:58.039> slots<00:27:58.480> potentially 00:27:59.470 --> 00:27:59.480 align:start position:0% into the same slots potentially 00:27:59.480 --> 00:28:01.090 align:start position:0% into the same slots potentially overriding<00:27:59.929> all<00:28:00.200> of<00:28:00.320> the<00:28:00.440> importance 00:28:01.090 --> 00:28:01.100 align:start position:0% overriding all of the importance 00:28:01.100 --> 00:28:03.250 align:start position:0% overriding all of the importance in<00:28:01.400> there<00:28:01.610> so<00:28:02.120> keeping<00:28:02.450> this<00:28:02.600> in<00:28:02.660> separate 00:28:03.250 --> 00:28:03.260 align:start position:0% in there so keeping this in separate 00:28:03.260 --> 00:28:05.980 align:start position:0% in there so keeping this in separate addresses<00:28:03.669> which<00:28:04.669> cannot<00:28:05.120> really<00:28:05.330> do<00:28:05.600> things 00:28:05.980 --> 00:28:05.990 align:start position:0% addresses which cannot really do things 00:28:05.990 --> 00:28:08.799 align:start position:0% addresses which cannot really do things on<00:28:06.169> the<00:28:06.260> other<00:28:06.289> side<00:28:06.940> makes<00:28:07.940> it<00:28:08.120> more<00:28:08.270> safe<00:28:08.539> I 00:28:08.799 --> 00:28:08.809 align:start position:0% on the other side makes it more safe I 00:28:08.809 --> 00:28:10.990 align:start position:0% on the other side makes it more safe I mean<00:28:09.260> is<00:28:09.530> I<00:28:09.770> assume<00:28:10.160> there<00:28:10.309> will<00:28:10.400> be<00:28:10.460> a<00:28:10.549> future 00:28:10.990 --> 00:28:11.000 align:start position:0% mean is I assume there will be a future 00:28:11.000 --> 00:28:13.180 align:start position:0% mean is I assume there will be a future where<00:28:11.179> people<00:28:12.049> go<00:28:12.200> to<00:28:12.260> website<00:28:12.710> and<00:28:12.740> say<00:28:12.980> hey 00:28:13.180 --> 00:28:13.190 align:start position:0% where people go to website and say hey 00:28:13.190 --> 00:28:14.770 align:start position:0% where people go to website and say hey download<00:28:13.549> this<00:28:13.669> new<00:28:13.910> universe<00:28:14.240> would<00:28:14.480> receive 00:28:14.770 --> 00:28:14.780 align:start position:0% download this new universe would receive 00:28:14.780 --> 00:28:16.419 align:start position:0% download this new universe would receive our<00:28:14.960> contract<00:28:15.500> because<00:28:15.770> now<00:28:15.919> it's<00:28:16.070> portable 00:28:16.419 --> 00:28:16.429 align:start position:0% our contract because now it's portable 00:28:16.429 --> 00:28:18.940 align:start position:0% our contract because now it's portable at<00:28:17.030> the<00:28:17.150> bar<00:28:17.360> and<00:28:17.780> then<00:28:18.440> you<00:28:18.500> just<00:28:18.740> go<00:28:18.919> ahead 00:28:18.940 --> 00:28:18.950 align:start position:0% at the bar and then you just go ahead 00:28:18.950 --> 00:28:21.220 align:start position:0% at the bar and then you just go ahead and<00:28:19.460> upgrade<00:28:19.789> your<00:28:19.820> your<00:28:20.450> account<00:28:20.780> with<00:28:21.080> this 00:28:21.220 --> 00:28:21.230 align:start position:0% and upgrade your your account with this 00:28:21.230 --> 00:28:23.860 align:start position:0% and upgrade your your account with this and<00:28:21.669> if<00:28:22.669> this<00:28:22.820> would<00:28:23.000> be<00:28:23.030> the<00:28:23.299> same<00:28:23.510> account 00:28:23.860 --> 00:28:23.870 align:start position:0% and if this would be the same account 00:28:23.870 --> 00:28:25.960 align:start position:0% and if this would be the same account maybe<00:28:24.470> just<00:28:24.740> move<00:28:24.950> your<00:28:25.100> assets<00:28:25.460> around<00:28:25.549> or 00:28:25.960 --> 00:28:25.970 align:start position:0% maybe just move your assets around or 00:28:25.970 --> 00:28:29.020 align:start position:0% maybe just move your assets around or variety<00:28:26.960> of<00:28:27.020> storage<00:28:27.410> values<00:28:27.860> like<00:28:28.580> this<00:28:28.789> is 00:28:29.020 --> 00:28:29.030 align:start position:0% variety of storage values like this is 00:28:29.030 --> 00:28:30.669 align:start position:0% variety of storage values like this is the<00:28:29.570> worst<00:28:29.750> thing<00:28:29.870> you<00:28:29.960> can<00:28:30.110> do<00:28:30.230> is<00:28:30.380> notify 00:28:30.669 --> 00:28:30.679 align:start position:0% the worst thing you can do is notify 00:28:30.679 --> 00:28:33.520 align:start position:0% the worst thing you can do is notify your<00:28:30.919> interface<00:28:31.280> box<00:28:31.490> with<00:28:32.390> the<00:28:32.480> wrong<00:28:32.660> Locker 00:28:33.520 --> 00:28:33.530 align:start position:0% your interface box with the wrong Locker 00:28:33.530 --> 00:28:37.330 align:start position:0% your interface box with the wrong Locker so<00:28:33.710> practice<00:28:35.320> good<00:28:36.320> I<00:28:36.559> think<00:28:36.710> that's<00:28:36.950> it 00:28:37.330 --> 00:28:37.340 align:start position:0% so practice good I think that's it 00:28:37.340 --> 00:28:40.610 align:start position:0% so practice good I think that's it time's<00:28:37.549> up<00:28:37.730> thank<00:28:38.030> you<00:28:38.090> so<00:28:38.240> much 00:28:40.610 --> 00:28:40.620 align:start position:0% 00:28:40.620 --> 00:28:47.040 align:start position:0% [Applause]