WEBVTT Kind: captions Language: en 00:00:01.070 --> 00:00:13.980 align:start position:0% [Applause] 00:00:13.980 --> 00:00:13.990 align:start position:0% 00:00:13.990 --> 00:00:16.690 align:start position:0% part<00:00:14.990> of<00:00:15.049> the<00:00:15.200> foundation<00:00:15.980> for<00:00:16.099> the<00:00:16.369> past 00:00:16.690 --> 00:00:16.700 align:start position:0% part of the foundation for the past 00:00:16.700 --> 00:00:19.450 align:start position:0% part of the foundation for the past three<00:00:17.090> years<00:00:17.119> or<00:00:17.509> so<00:00:17.750> and<00:00:18.050> for<00:00:19.040> two<00:00:19.279> years 00:00:19.450 --> 00:00:19.460 align:start position:0% three years or so and for two years 00:00:19.460 --> 00:00:22.240 align:start position:0% three years or so and for two years working<00:00:19.939> with<00:00:20.110> really<00:00:21.110> steep<00:00:21.410> and<00:00:21.770> for<00:00:22.130> the 00:00:22.240 --> 00:00:22.250 align:start position:0% working with really steep and for the 00:00:22.250 --> 00:00:24.909 align:start position:0% working with really steep and for the past<00:00:22.550> eight<00:00:22.880> months<00:00:22.910> between<00:00:23.650> working<00:00:24.650> on 00:00:24.909 --> 00:00:24.919 align:start position:0% past eight months between working on 00:00:24.919 --> 00:00:27.400 align:start position:0% past eight months between working on this<00:00:25.070> topic<00:00:25.279> how<00:00:25.789> to<00:00:25.820> make<00:00:26.119> doing<00:00:26.570> more<00:00:27.019> trust 00:00:27.400 --> 00:00:27.410 align:start position:0% this topic how to make doing more trust 00:00:27.410 --> 00:00:30.730 align:start position:0% this topic how to make doing more trust lists<00:00:27.800> so<00:00:28.789> I<00:00:29.000> will<00:00:29.150> show<00:00:29.330> you<00:00:29.390> what<00:00:29.779> we<00:00:30.289> see<00:00:30.529> as 00:00:30.730 --> 00:00:30.740 align:start position:0% lists so I will show you what we see as 00:00:30.740 --> 00:00:33.220 align:start position:0% lists so I will show you what we see as a<00:00:30.769> problem<00:00:31.070> and<00:00:31.550> then<00:00:32.090> hopefully<00:00:32.390> post<00:00:32.989> at 00:00:33.220 --> 00:00:33.230 align:start position:0% a problem and then hopefully post at 00:00:33.230 --> 00:00:36.340 align:start position:0% a problem and then hopefully post at your<00:00:33.410> includes<00:00:33.980> in<00:00:34.250> blue<00:00:34.519> but<00:00:34.790> you<00:00:35.000> see<00:00:35.290> as<00:00:36.290> a 00:00:36.340 --> 00:00:36.350 align:start position:0% your includes in blue but you see as a 00:00:36.350 --> 00:00:39.549 align:start position:0% your includes in blue but you see as a problem<00:00:36.620> and<00:00:37.070> how<00:00:37.430> what's<00:00:38.150> missing<00:00:38.600> you<00:00:39.350> maybe 00:00:39.549 --> 00:00:39.559 align:start position:0% problem and how what's missing you maybe 00:00:39.559 --> 00:00:42.549 align:start position:0% problem and how what's missing you maybe suggest<00:00:39.739> what<00:00:40.250> you<00:00:40.400> need<00:00:40.970> to<00:00:41.210> do<00:00:41.390> so<00:00:42.229> that<00:00:42.260> as<00:00:42.530> a 00:00:42.549 --> 00:00:42.559 align:start position:0% suggest what you need to do so that as a 00:00:42.559 --> 00:00:44.079 align:start position:0% suggest what you need to do so that as a community<00:00:42.830> we<00:00:43.250> bring<00:00:43.610> to<00:00:43.760> these<00:00:43.879> things 00:00:44.079 --> 00:00:44.089 align:start position:0% community we bring to these things 00:00:44.089 --> 00:00:58.479 align:start position:0% community we bring to these things forward<00:00:44.510> and<00:00:44.930> make<00:00:45.260> it<00:00:45.409> more<00:00:45.650> justice<00:00:57.430> okay<00:00:58.430> so 00:00:58.479 --> 00:00:58.489 align:start position:0% forward and make it more justice okay so 00:00:58.489 --> 00:01:00.609 align:start position:0% forward and make it more justice okay so that's<00:00:58.940> basically<00:00:59.540> just<00:00:59.930> a<00:01:00.229> small 00:01:00.609 --> 00:01:00.619 align:start position:0% that's basically just a small 00:01:00.619 --> 00:01:02.710 align:start position:0% that's basically just a small introduction<00:01:01.010> and<00:01:01.909> there<00:01:02.119> are<00:01:02.210> many<00:01:02.330> ways<00:01:02.479> to 00:01:02.710 --> 00:01:02.720 align:start position:0% introduction and there are many ways to 00:01:02.720 --> 00:01:04.270 align:start position:0% introduction and there are many ways to introduce<00:01:02.869> this<00:01:03.260> but<00:01:03.559> there<00:01:03.769> years<00:01:04.010> at<00:01:04.250> least 00:01:04.270 --> 00:01:04.280 align:start position:0% introduce this but there years at least 00:01:04.280 --> 00:01:07.060 align:start position:0% introduce this but there years at least represents<00:01:04.970> the<00:01:05.089> end<00:01:05.239> of<00:01:05.390> a<00:01:05.449> tab<00:01:05.720> and<00:01:05.960> you<00:01:06.890> can 00:01:07.060 --> 00:01:07.070 align:start position:0% represents the end of a tab and you can 00:01:07.070 --> 00:01:09.219 align:start position:0% represents the end of a tab and you can open<00:01:07.430> my<00:01:07.549> wallet<00:01:07.850> we<00:01:08.299> never<00:01:08.479> started<00:01:08.810> making 00:01:09.219 --> 00:01:09.229 align:start position:0% open my wallet we never started making 00:01:09.229 --> 00:01:11.350 align:start position:0% open my wallet we never started making an<00:01:09.320> interaction<00:01:09.890> and<00:01:10.100> of<00:01:10.670> course<00:01:10.700> if<00:01:11.150> you 00:01:11.350 --> 00:01:11.360 align:start position:0% an interaction and of course if you 00:01:11.360 --> 00:01:14.740 align:start position:0% an interaction and of course if you execute<00:01:11.960> contracts<00:01:12.770> the<00:01:12.950> way<00:01:13.149> it<00:01:14.149> does<00:01:14.359> and 00:01:14.740 --> 00:01:14.750 align:start position:0% execute contracts the way it does and 00:01:14.750 --> 00:01:17.349 align:start position:0% execute contracts the way it does and there<00:01:15.350> is<00:01:15.439> no<00:01:15.619> magic<00:01:16.399> administrator<00:01:17.000> like<00:01:17.179> you 00:01:17.349 --> 00:01:17.359 align:start position:0% there is no magic administrator like you 00:01:17.359 --> 00:01:18.669 align:start position:0% there is no magic administrator like you do<00:01:17.479> anything<00:01:17.719> about<00:01:17.929> it<00:01:18.079> but<00:01:18.350> the<00:01:18.469> thing<00:01:18.649> is 00:01:18.669 --> 00:01:18.679 align:start position:0% do anything about it but the thing is 00:01:18.679 --> 00:01:20.649 align:start position:0% do anything about it but the thing is still<00:01:18.979> as<00:01:19.100> a<00:01:19.130> user<00:01:19.429> when<00:01:20.060> you<00:01:20.149> direct<00:01:20.420> look<00:01:20.570> at 00:01:20.649 --> 00:01:20.659 align:start position:0% still as a user when you direct look at 00:01:20.659 --> 00:01:23.139 align:start position:0% still as a user when you direct look at that<00:01:21.520> then<00:01:22.520> yeah<00:01:22.700> you<00:01:22.789> have<00:01:23.000> some 00:01:23.139 --> 00:01:23.149 align:start position:0% that then yeah you have some 00:01:23.149 --> 00:01:25.090 align:start position:0% that then yeah you have some expectations<00:01:23.840> what<00:01:24.049> this<00:01:24.200> is<00:01:24.320> going<00:01:24.859> to<00:01:24.950> do 00:01:25.090 --> 00:01:25.100 align:start position:0% expectations what this is going to do 00:01:25.100 --> 00:01:26.709 align:start position:0% expectations what this is going to do and<00:01:25.340> what<00:01:25.429> the<00:01:25.579> conflict<00:01:25.909> is<00:01:26.119> all<00:01:26.299> about<00:01:26.539> but 00:01:26.709 --> 00:01:26.719 align:start position:0% and what the conflict is all about but 00:01:26.719 --> 00:01:28.209 align:start position:0% and what the conflict is all about but if<00:01:26.840> you<00:01:26.869> don't<00:01:27.109> have<00:01:27.200> a<00:01:27.350> source<00:01:27.590> there's<00:01:28.100> no 00:01:28.209 --> 00:01:28.219 align:start position:0% if you don't have a source there's no 00:01:28.219 --> 00:01:30.310 align:start position:0% if you don't have a source there's no way<00:01:28.340> of<00:01:28.460> easily<00:01:29.030> verified<00:01:29.479> it<00:01:29.630> may<00:01:29.810> be<00:01:29.869> your 00:01:30.310 --> 00:01:30.320 align:start position:0% way of easily verified it may be your 00:01:30.320 --> 00:01:32.139 align:start position:0% way of easily verified it may be your wallet<00:01:30.469> will<00:01:30.710> show<00:01:30.920> you<00:01:30.979> some<00:01:31.729> data<00:01:31.909> before 00:01:32.139 --> 00:01:32.149 align:start position:0% wallet will show you some data before 00:01:32.149 --> 00:01:33.999 align:start position:0% wallet will show you some data before you<00:01:32.329> confirm<00:01:32.749> the<00:01:32.869> transaction<00:01:33.079> but 00:01:33.999 --> 00:01:34.009 align:start position:0% you confirm the transaction but 00:01:34.009 --> 00:01:36.370 align:start position:0% you confirm the transaction but generally<00:01:34.399> it's<00:01:34.520> not<00:01:34.549> so<00:01:34.850> easy<00:01:35.119> to<00:01:35.270> say<00:01:35.659> is 00:01:36.370 --> 00:01:36.380 align:start position:0% generally it's not so easy to say is 00:01:36.380 --> 00:01:37.690 align:start position:0% generally it's not so easy to say is that<00:01:36.770> what<00:01:36.950> you<00:01:37.039> are<00:01:37.070> seeing<00:01:37.369> and<00:01:37.640> doing 00:01:37.690 --> 00:01:37.700 align:start position:0% that what you are seeing and doing 00:01:37.700 --> 00:01:40.840 align:start position:0% that what you are seeing and doing actually<00:01:38.890> what<00:01:39.890> is<00:01:40.009> happening<00:01:40.039> behind<00:01:40.609> the 00:01:40.840 --> 00:01:40.850 align:start position:0% actually what is happening behind the 00:01:40.850 --> 00:01:41.230 align:start position:0% actually what is happening behind the scenes 00:01:41.230 --> 00:01:41.240 align:start position:0% scenes 00:01:41.240 --> 00:01:43.809 align:start position:0% scenes and<00:01:41.390> even<00:01:42.289> if<00:01:42.350> you<00:01:42.439> do<00:01:42.590> whole<00:01:43.039> secures<00:01:43.490> it<00:01:43.700> has 00:01:43.809 --> 00:01:43.819 align:start position:0% and even if you do whole secures it has 00:01:43.819 --> 00:01:45.340 align:start position:0% and even if you do whole secures it has it<00:01:43.969> in<00:01:44.240> order<00:01:44.569> to<00:01:44.719> that<00:01:44.810> I<00:01:44.840> mean<00:01:44.869> there's<00:01:45.200> so 00:01:45.340 --> 00:01:45.350 align:start position:0% it in order to that I mean there's so 00:01:45.350 --> 00:01:45.680 align:start position:0% it in order to that I mean there's so many 00:01:45.680 --> 00:01:45.690 align:start position:0% many 00:01:45.690 --> 00:01:48.340 align:start position:0% many from<00:01:46.080> having<00:01:46.650> made<00:01:46.800> a<00:01:46.980> source<00:01:47.250> code<00:01:47.520> that<00:01:48.000> is 00:01:48.340 --> 00:01:48.350 align:start position:0% from having made a source code that is 00:01:48.350 --> 00:01:51.140 align:start position:0% from having made a source code that is verified<00:01:49.350> that<00:01:50.070> you<00:01:50.280> know<00:01:50.430> that<00:01:50.730> this<00:01:50.910> source 00:01:51.140 --> 00:01:51.150 align:start position:0% verified that you know that this source 00:01:51.150 --> 00:01:52.700 align:start position:0% verified that you know that this source post<00:01:51.390> is<00:01:51.510> actually<00:01:51.750> the<00:01:52.080> one<00:01:52.200> that<00:01:52.260> is<00:01:52.500> to 00:01:52.700 --> 00:01:52.710 align:start position:0% post is actually the one that is to 00:01:52.710 --> 00:01:54.470 align:start position:0% post is actually the one that is to contract<00:01:53.550> address<00:01:53.850> that<00:01:53.940> you<00:01:54.090> interact<00:01:54.390> with 00:01:54.470 --> 00:01:54.480 align:start position:0% contract address that you interact with 00:01:54.480 --> 00:01:57.440 align:start position:0% contract address that you interact with to<00:01:55.080> isn't<00:01:55.710> as<00:01:55.860> it<00:01:55.980> analyzes<00:01:56.550> in<00:01:56.940> audited<00:01:57.360> I 00:01:57.440 --> 00:01:57.450 align:start position:0% to isn't as it analyzes in audited I 00:01:57.450 --> 00:01:59.350 align:start position:0% to isn't as it analyzes in audited I mean<00:01:57.600> there's<00:01:57.780> many<00:01:58.080> different<00:01:58.230> levels<00:01:58.710> and 00:01:59.350 --> 00:01:59.360 align:start position:0% mean there's many different levels and 00:01:59.360 --> 00:02:03.230 align:start position:0% mean there's many different levels and the<00:02:00.360> situations<00:02:00.900> can<00:02:01.290> improve<00:02:02.220> to<00:02:02.520> over<00:02:03.060> what 00:02:03.230 --> 00:02:03.240 align:start position:0% the situations can improve to over what 00:02:03.240 --> 00:02:06.980 align:start position:0% the situations can improve to over what it<00:02:03.360> is<00:02:04.790> then<00:02:05.790> because<00:02:06.240> if<00:02:06.360> we<00:02:06.450> don't<00:02:06.570> do<00:02:06.780> that 00:02:06.980 --> 00:02:06.990 align:start position:0% it is then because if we don't do that 00:02:06.990 --> 00:02:09.139 align:start position:0% it is then because if we don't do that then<00:02:07.260> basically<00:02:07.650> you<00:02:07.890> could<00:02:08.160> use<00:02:08.460> aetherium 00:02:09.139 --> 00:02:09.149 align:start position:0% then basically you could use aetherium 00:02:09.149 --> 00:02:12.140 align:start position:0% then basically you could use aetherium as<00:02:09.740> an<00:02:10.740> alternative<00:02:11.250> hosting<00:02:11.640> solution<00:02:12.060> in 00:02:12.140 --> 00:02:12.150 align:start position:0% as an alternative hosting solution in 00:02:12.150 --> 00:02:14.480 align:start position:0% as an alternative hosting solution in AWS<00:02:12.780> I<00:02:13.020> have<00:02:13.170> my<00:02:13.380> back-end<00:02:13.620> I'm<00:02:13.950> using<00:02:14.190> it<00:02:14.370> as<00:02:14.460> a 00:02:14.480 --> 00:02:14.490 align:start position:0% AWS I have my back-end I'm using it as a 00:02:14.490 --> 00:02:17.540 align:start position:0% AWS I have my back-end I'm using it as a back-end<00:02:14.760> and<00:02:15.150> supposed<00:02:15.840> to<00:02:15.930> be<00:02:16.050> trustless<00:02:16.550> in 00:02:17.540 --> 00:02:17.550 align:start position:0% back-end and supposed to be trustless in 00:02:17.550 --> 00:02:20.110 align:start position:0% back-end and supposed to be trustless in the<00:02:17.760> end<00:02:17.880> you<00:02:18.000> actually<00:02:18.360> have<00:02:18.510> to<00:02:18.630> trust<00:02:19.070> then 00:02:20.110 --> 00:02:20.120 align:start position:0% the end you actually have to trust then 00:02:20.120 --> 00:02:23.000 align:start position:0% the end you actually have to trust then yeah<00:02:21.120> that's<00:02:21.420> that's<00:02:21.780> not<00:02:22.470> a<00:02:22.530> good<00:02:22.740> situation 00:02:23.000 --> 00:02:23.010 align:start position:0% yeah that's that's not a good situation 00:02:23.010 --> 00:02:27.320 align:start position:0% yeah that's that's not a good situation to<00:02:23.310> be<00:02:24.860> so<00:02:25.860> right<00:02:26.010> so<00:02:26.310> we<00:02:26.460> have<00:02:26.640> also<00:02:26.850> some 00:02:27.320 --> 00:02:27.330 align:start position:0% to be so right so we have also some 00:02:27.330 --> 00:02:29.030 align:start position:0% to be so right so we have also some numbers<00:02:27.720> and<00:02:28.020> we<00:02:28.290> have<00:02:28.440> the<00:02:28.530> suppose<00:02:28.740> there's 00:02:29.030 --> 00:02:29.040 align:start position:0% numbers and we have the suppose there's 00:02:29.040 --> 00:02:31.670 align:start position:0% numbers and we have the suppose there's or<00:02:29.370> basically<00:02:29.880> it<00:02:30.840> has<00:02:30.990> already<00:02:31.200> a<00:02:31.380> little<00:02:31.590> bit 00:02:31.670 --> 00:02:31.680 align:start position:0% or basically it has already a little bit 00:02:31.680 --> 00:02:34.970 align:start position:0% or basically it has already a little bit older<00:02:32.010> so<00:02:33.050> the<00:02:34.050> numbers<00:02:34.350> should<00:02:34.470> be<00:02:34.620> even 00:02:34.970 --> 00:02:34.980 align:start position:0% older so the numbers should be even 00:02:34.980 --> 00:02:36.140 align:start position:0% older so the numbers should be even higher<00:02:35.130> but<00:02:35.430> like<00:02:35.580> we<00:02:35.760> have<00:02:35.880> a<00:02:35.910> lot<00:02:36.060> of 00:02:36.140 --> 00:02:36.150 align:start position:0% higher but like we have a lot of 00:02:36.150 --> 00:02:38.540 align:start position:0% higher but like we have a lot of developers<00:02:36.660> that<00:02:36.900> come<00:02:37.440> in<00:02:37.530> touch<00:02:37.710> a<00:02:38.040> tryout 00:02:38.540 --> 00:02:38.550 align:start position:0% developers that come in touch a tryout 00:02:38.550 --> 00:02:41.000 align:start position:0% developers that come in touch a tryout learn<00:02:39.180> about<00:02:39.450> Ethier<00:02:40.410> in<00:02:40.680> the<00:02:40.800> broader 00:02:41.000 --> 00:02:41.010 align:start position:0% learn about Ethier in the broader 00:02:41.010 --> 00:02:44.600 align:start position:0% learn about Ethier in the broader ecosystem<00:02:41.390> everyone<00:02:42.740> $50,000<00:02:43.740> she<00:02:43.890> a<00:02:44.100> lot<00:02:44.520> of 00:02:44.600 --> 00:02:44.610 align:start position:0% ecosystem everyone $50,000 she a lot of 00:02:44.610 --> 00:02:47.900 align:start position:0% ecosystem everyone $50,000 she a lot of them<00:02:45.440> in<00:02:46.440> every<00:02:46.770> every<00:02:47.010> month<00:02:47.310> like<00:02:47.520> I<00:02:47.790> mean 00:02:47.900 --> 00:02:47.910 align:start position:0% them in every every month like I mean 00:02:47.910 --> 00:02:50.449 align:start position:0% them in every every month like I mean depends<00:02:48.660> it<00:02:48.810> changes<00:02:49.260> but<00:02:49.530> like<00:02:49.709> it's<00:02:49.890> 1.5 00:02:50.449 --> 00:02:50.459 align:start position:0% depends it changes but like it's 1.5 00:02:50.459 --> 00:02:52.160 align:start position:0% depends it changes but like it's 1.5 million<00:02:50.820> contractors<00:02:51.360> are<00:02:51.600> getting<00:02:51.840> deployed 00:02:52.160 --> 00:02:52.170 align:start position:0% million contractors are getting deployed 00:02:52.170 --> 00:02:56.780 align:start position:0% million contractors are getting deployed to<00:02:52.980> the<00:02:53.010> chain<00:02:53.310> and<00:02:54.890> 10<00:02:55.890> 10<00:02:56.370> more<00:02:56.550> than<00:02:56.640> 10 00:02:56.780 --> 00:02:56.790 align:start position:0% to the chain and 10 10 more than 10 00:02:56.790 --> 00:02:58.220 align:start position:0% to the chain and 10 10 more than 10 million<00:02:56.970> convicts<00:02:57.450> are<00:02:57.630> on<00:02:57.840> Chamberlain 00:02:58.220 --> 00:02:58.230 align:start position:0% million convicts are on Chamberlain 00:02:58.230 --> 00:03:00.560 align:start position:0% million convicts are on Chamberlain actually<00:02:58.830> it's<00:02:59.040> even<00:02:59.280> more<00:02:59.670> because<00:02:59.880> the 00:03:00.560 --> 00:03:00.570 align:start position:0% actually it's even more because the 00:03:00.570 --> 00:03:03.560 align:start position:0% actually it's even more because the latest<00:03:00.840> little<00:03:01.170> older<00:03:01.470> sole<00:03:02.570> convicts 00:03:03.560 --> 00:03:03.570 align:start position:0% latest little older sole convicts 00:03:03.570 --> 00:03:05.870 align:start position:0% latest little older sole convicts getting<00:03:04.380> comes<00:03:04.560> up<00:03:04.680> be<00:03:04.770> published<00:03:05.160> and<00:03:05.310> every 00:03:05.870 --> 00:03:05.880 align:start position:0% getting comes up be published and every 00:03:05.880 --> 00:03:08.690 align:start position:0% getting comes up be published and every day<00:03:06.060> also<00:03:06.780> those<00:03:07.080> numbers<00:03:07.440> are<00:03:07.700> fluctuating 00:03:08.690 --> 00:03:08.700 align:start position:0% day also those numbers are fluctuating 00:03:08.700 --> 00:03:12.199 align:start position:0% day also those numbers are fluctuating but<00:03:08.970> likely<00:03:09.180> 1.2<00:03:09.989> million<00:03:10.230> contract<00:03:11.209> calls 00:03:12.199 --> 00:03:12.209 align:start position:0% but likely 1.2 million contract calls 00:03:12.209 --> 00:03:15.979 align:start position:0% but likely 1.2 million contract calls per<00:03:12.720> day<00:03:12.750> so<00:03:13.680> that's<00:03:13.860> actually<00:03:14.070> a<00:03:14.280> lot<00:03:14.610> are<00:03:15.000> and 00:03:15.979 --> 00:03:15.989 align:start position:0% per day so that's actually a lot are and 00:03:15.989 --> 00:03:18.860 align:start position:0% per day so that's actually a lot are and the<00:03:16.080> thing<00:03:16.290> is<00:03:16.440> that<00:03:17.269> just<00:03:18.269> when<00:03:18.360> it<00:03:18.480> comes<00:03:18.660> to 00:03:18.860 --> 00:03:18.870 align:start position:0% the thing is that just when it comes to 00:03:18.870 --> 00:03:22.740 align:start position:0% the thing is that just when it comes to very<00:03:19.620> resourceful<00:03:20.360> there<00:03:21.360> are 00:03:22.740 --> 00:03:22.750 align:start position:0% very resourceful there are 00:03:22.750 --> 00:03:24.539 align:start position:0% very resourceful there are when<00:03:23.080> you<00:03:23.230> are<00:03:23.560> may<00:03:23.680> be<00:03:23.709> familiar<00:03:23.860> with<00:03:24.189> ether 00:03:24.539 --> 00:03:24.549 align:start position:0% when you are may be familiar with ether 00:03:24.549 --> 00:03:28.410 align:start position:0% when you are may be familiar with ether skin<00:03:24.819> but<00:03:25.450> generally<00:03:25.870> like<00:03:26.860> in<00:03:27.400> 2007<00:03:28.329> the 00:03:28.410 --> 00:03:28.420 align:start position:0% skin but generally like in 2007 the 00:03:28.420 --> 00:03:30.660 align:start position:0% skin but generally like in 2007 the millions<00:03:28.810> so<00:03:29.709> of<00:03:29.890> course<00:03:30.129> also<00:03:30.459> some 00:03:30.660 --> 00:03:30.670 align:start position:0% millions so of course also some 00:03:30.670 --> 00:03:33.929 align:start position:0% millions so of course also some contracts<00:03:31.470> deployed<00:03:32.470> many<00:03:32.680> times<00:03:32.980> over<00:03:33.370> but 00:03:33.929 --> 00:03:33.939 align:start position:0% contracts deployed many times over but 00:03:33.939 --> 00:03:36.030 align:start position:0% contracts deployed many times over but still<00:03:34.209> the<00:03:34.329> situation<00:03:34.750> is<00:03:34.840> not<00:03:35.049> really<00:03:35.769> as 00:03:36.030 --> 00:03:36.040 align:start position:0% still the situation is not really as 00:03:36.040 --> 00:03:39.509 align:start position:0% still the situation is not really as good<00:03:36.430> as<00:03:36.730> it<00:03:36.849> could<00:03:37.299> be<00:03:37.450> and<00:03:38.069> we<00:03:39.069> were<00:03:39.159> thinking 00:03:39.509 --> 00:03:39.519 align:start position:0% good as it could be and we were thinking 00:03:39.519 --> 00:03:42.960 align:start position:0% good as it could be and we were thinking what<00:03:39.670> we<00:03:39.819> maybe<00:03:40.239> can<00:03:40.599> do<00:03:41.200> audits<00:03:42.040> to<00:03:42.129> do<00:03:42.430> it<00:03:42.610> so 00:03:42.960 --> 00:03:42.970 align:start position:0% what we maybe can do audits to do it so 00:03:42.970 --> 00:03:47.699 align:start position:0% what we maybe can do audits to do it so the<00:03:43.120> thing<00:03:43.299> is<00:03:45.329> yeah<00:03:46.329> so<00:03:46.659> what<00:03:47.290> is<00:03:47.440> also<00:03:47.590> very 00:03:47.699 --> 00:03:47.709 align:start position:0% the thing is yeah so what is also very 00:03:47.709 --> 00:03:49.440 align:start position:0% the thing is yeah so what is also very important<00:03:48.370> here<00:03:48.549> like<00:03:48.909> we<00:03:49.030> have<00:03:49.209> all<00:03:49.329> these 00:03:49.440 --> 00:03:49.450 align:start position:0% important here like we have all these 00:03:49.450 --> 00:03:52.140 align:start position:0% important here like we have all these numbers<00:03:49.870> but<00:03:50.859> the<00:03:50.920> problem<00:03:51.190> is<00:03:51.310> that<00:03:51.519> apart 00:03:52.140 --> 00:03:52.150 align:start position:0% numbers but the problem is that apart 00:03:52.150 --> 00:03:54.750 align:start position:0% numbers but the problem is that apart from<00:03:52.239> either<00:03:52.510> scan<00:03:52.900> there<00:03:53.049> is<00:03:53.290> no<00:03:53.590> other<00:03:53.950> place 00:03:54.750 --> 00:03:54.760 align:start position:0% from either scan there is no other place 00:03:54.760 --> 00:03:58.259 align:start position:0% from either scan there is no other place where<00:03:55.209> we<00:03:55.329> could<00:03:55.480> explore<00:03:55.989> or<00:03:56.440> or<00:03:57.269> verify 00:03:58.259 --> 00:03:58.269 align:start position:0% where we could explore or or verify 00:03:58.269 --> 00:04:00.240 align:start position:0% where we could explore or or verify source<00:03:58.540> codes<00:03:58.780> so<00:03:59.349> that<00:03:59.379> means<00:03:59.739> that<00:03:59.950> it's 00:04:00.240 --> 00:04:00.250 align:start position:0% source codes so that means that it's 00:04:00.250 --> 00:04:03.059 align:start position:0% source codes so that means that it's port<00:04:00.579> on<00:04:00.819> a<00:04:00.849> centralized<00:04:01.420> place<00:04:01.629> and<00:04:02.319> if<00:04:02.920> they 00:04:03.059 --> 00:04:03.069 align:start position:0% port on a centralized place and if they 00:04:03.069 --> 00:04:09.420 align:start position:0% port on a centralized place and if they decide<00:04:03.190> to<00:04:05.849> open<00:04:06.849> that<00:04:06.940> means<00:04:07.780> we<00:04:08.400> have<00:04:09.400> a 00:04:09.420 --> 00:04:09.430 align:start position:0% decide to open that means we have a 00:04:09.430 --> 00:04:11.280 align:start position:0% decide to open that means we have a trusted<00:04:10.030> system<00:04:10.180> where<00:04:10.629> we<00:04:10.720> have<00:04:10.750> to<00:04:10.930> trust 00:04:11.280 --> 00:04:11.290 align:start position:0% trusted system where we have to trust 00:04:11.290 --> 00:04:13.289 align:start position:0% trusted system where we have to trust the<00:04:11.739> contracts<00:04:12.310> well<00:04:12.609> we<00:04:12.849> don't<00:04:12.970> have<00:04:13.030> access 00:04:13.289 --> 00:04:13.299 align:start position:0% the contracts well we don't have access 00:04:13.299 --> 00:04:17.400 align:start position:0% the contracts well we don't have access to<00:04:13.510> this<00:04:13.690> contract<00:04:14.579> and<00:04:15.840> we<00:04:16.840> have<00:04:17.049> to<00:04:17.169> ask 00:04:17.400 --> 00:04:17.410 align:start position:0% to this contract and we have to ask 00:04:17.410 --> 00:04:19.469 align:start position:0% to this contract and we have to ask ourselves<00:04:17.560> is<00:04:17.919> there<00:04:18.100> even<00:04:18.549> incentives<00:04:19.180> to 00:04:19.469 --> 00:04:19.479 align:start position:0% ourselves is there even incentives to 00:04:19.479 --> 00:04:21.449 align:start position:0% ourselves is there even incentives to share<00:04:19.900> this<00:04:20.079> religious<00:04:20.530> or<00:04:20.680> scope<00:04:20.949> or<00:04:21.130> what 00:04:21.449 --> 00:04:21.459 align:start position:0% share this religious or scope or what 00:04:21.459 --> 00:04:25.469 align:start position:0% share this religious or scope or what can<00:04:21.639> we<00:04:21.760> do<00:04:21.910> to<00:04:23.550> find<00:04:24.550> out<00:04:24.699> what<00:04:25.120> could<00:04:25.330> be<00:04:25.389> the 00:04:25.469 --> 00:04:25.479 align:start position:0% can we do to find out what could be the 00:04:25.479 --> 00:04:29.640 align:start position:0% can we do to find out what could be the incentive<00:04:26.699> and<00:04:27.699> as<00:04:28.240> you<00:04:29.020> mentioned<00:04:29.440> there<00:04:29.560> is 00:04:29.640 --> 00:04:29.650 align:start position:0% incentive and as you mentioned there is 00:04:29.650 --> 00:04:31.409 align:start position:0% incentive and as you mentioned there is only<00:04:29.830> a<00:04:29.979> couple<00:04:30.130> of<00:04:30.340> thousands<00:04:30.729> of<00:04:30.820> them<00:04:31.030> but 00:04:31.409 --> 00:04:31.419 align:start position:0% only a couple of thousands of them but 00:04:31.419 --> 00:04:33.810 align:start position:0% only a couple of thousands of them but we<00:04:31.900> have<00:04:31.930> like<00:04:32.349> over<00:04:32.740> 10<00:04:33.280> million<00:04:33.520> of 00:04:33.810 --> 00:04:33.820 align:start position:0% we have like over 10 million of 00:04:33.820 --> 00:04:35.550 align:start position:0% we have like over 10 million of contracts<00:04:34.210> currently<00:04:34.570> working<00:04:34.930> so<00:04:35.139> how<00:04:35.380> do<00:04:35.440> we 00:04:35.550 --> 00:04:35.560 align:start position:0% contracts currently working so how do we 00:04:35.560 --> 00:04:40.589 align:start position:0% contracts currently working so how do we get<00:04:35.710> more<00:04:35.770> rarefied<00:04:36.460> circles<00:04:37.650> and<00:04:39.599> sicinius 00:04:40.589 --> 00:04:40.599 align:start position:0% get more rarefied circles and sicinius 00:04:40.599 --> 00:04:42.210 align:start position:0% get more rarefied circles and sicinius we<00:04:40.870> were<00:04:40.990> thinking<00:04:41.320> maybe<00:04:41.500> if<00:04:41.770> we<00:04:41.919> have<00:04:42.039> like<00:04:42.160> a 00:04:42.210 --> 00:04:42.220 align:start position:0% we were thinking maybe if we have like a 00:04:42.220 --> 00:04:45.210 align:start position:0% we were thinking maybe if we have like a neutral<00:04:42.699> place<00:04:42.910> that<00:04:43.750> could<00:04:44.590> be<00:04:44.680> used<00:04:44.919> to 00:04:45.210 --> 00:04:45.220 align:start position:0% neutral place that could be used to 00:04:45.220 --> 00:04:47.520 align:start position:0% neutral place that could be used to explore<00:04:46.090> and<00:04:46.389> find<00:04:46.419> information<00:04:46.900> whether 00:04:47.520 --> 00:04:47.530 align:start position:0% explore and find information whether 00:04:47.530 --> 00:04:48.370 align:start position:0% explore and find information whether there<00:04:47.800> is 00:04:48.370 --> 00:04:48.380 align:start position:0% there is 00:04:48.380 --> 00:04:50.590 align:start position:0% there is this<00:04:48.740> verified<00:04:49.520> whether<00:04:50.060> it<00:04:50.240> has<00:04:50.390> been 00:04:50.590 --> 00:04:50.600 align:start position:0% this verified whether it has been 00:04:50.600 --> 00:04:53.320 align:start position:0% this verified whether it has been analyzed<00:04:51.410> whether<00:04:51.980> it<00:04:52.280> has<00:04:52.610> been<00:04:52.820> audited 00:04:53.320 --> 00:04:53.330 align:start position:0% analyzed whether it has been audited 00:04:53.330 --> 00:04:54.940 align:start position:0% analyzed whether it has been audited maybe<00:04:53.780> multiple<00:04:54.050> times<00:04:54.530> at<00:04:54.860> different 00:04:54.940 --> 00:04:54.950 align:start position:0% maybe multiple times at different 00:04:54.950 --> 00:04:58.270 align:start position:0% maybe multiple times at different parties<00:04:56.080> there's<00:04:57.080> so<00:04:57.290> many<00:04:57.410> so<00:04:58.070> many<00:04:58.160> things 00:04:58.270 --> 00:04:58.280 align:start position:0% parties there's so many so many things 00:04:58.280 --> 00:05:00.580 align:start position:0% parties there's so many so many things that<00:04:58.520> you<00:04:58.640> might<00:04:58.910> want<00:04:58.970> to<00:04:59.240> know<00:04:59.420> or<00:04:59.810> maybe 00:05:00.580 --> 00:05:00.590 align:start position:0% that you might want to know or maybe 00:05:00.590 --> 00:05:03.070 align:start position:0% that you might want to know or maybe you're<00:05:01.100> an<00:05:01.880> end-user<00:05:02.150> you<00:05:02.540> interact<00:05:02.870> with<00:05:02.930> the 00:05:03.070 --> 00:05:03.080 align:start position:0% you're an end-user you interact with the 00:05:03.080 --> 00:05:05.050 align:start position:0% you're an end-user you interact with the tap<00:05:03.290> and<00:05:03.470> it<00:05:03.530> uses<00:05:03.860> a<00:05:03.890> smart<00:05:04.220> contract<00:05:04.640> or<00:05:05.000> you 00:05:05.050 --> 00:05:05.060 align:start position:0% tap and it uses a smart contract or you 00:05:05.060 --> 00:05:07.420 align:start position:0% tap and it uses a smart contract or you multiple<00:05:05.630> ones<00:05:05.840> or<00:05:06.230> your<00:05:06.350> developer<00:05:06.890> and<00:05:07.280> you 00:05:07.420 --> 00:05:07.430 align:start position:0% multiple ones or your developer and you 00:05:07.430 --> 00:05:09.400 align:start position:0% multiple ones or your developer and you want<00:05:07.460> to<00:05:07.670> use<00:05:07.820> live<00:05:08.060> reason<00:05:08.540> maybe<00:05:08.810> those<00:05:09.170> legs 00:05:09.400 --> 00:05:09.410 align:start position:0% want to use live reason maybe those legs 00:05:09.410 --> 00:05:12.760 align:start position:0% want to use live reason maybe those legs that<00:05:09.680> we<00:05:09.830> ordered<00:05:10.130> it<00:05:10.220> or<00:05:10.370> not<00:05:11.140> maybe<00:05:12.140> the 00:05:12.760 --> 00:05:12.770 align:start position:0% that we ordered it or not maybe the 00:05:12.770 --> 00:05:14.230 align:start position:0% that we ordered it or not maybe the source<00:05:12.980> premier<00:05:13.190> everything<00:05:13.580> is<00:05:13.670> audit<00:05:13.970> about 00:05:14.230 --> 00:05:14.240 align:start position:0% source premier everything is audit about 00:05:14.240 --> 00:05:16.300 align:start position:0% source premier everything is audit about the<00:05:14.360> contract<00:05:14.810> itself<00:05:15.110> makes<00:05:15.500> calls<00:05:15.830> to<00:05:16.010> other 00:05:16.300 --> 00:05:16.310 align:start position:0% the contract itself makes calls to other 00:05:16.310 --> 00:05:18.430 align:start position:0% the contract itself makes calls to other contracts<00:05:17.060> so<00:05:17.480> it's<00:05:17.570> not<00:05:17.690> kind<00:05:17.990> of<00:05:18.020> disaster 00:05:18.430 --> 00:05:18.440 align:start position:0% contracts so it's not kind of disaster 00:05:18.440 --> 00:05:19.600 align:start position:0% contracts so it's not kind of disaster but<00:05:18.560> then<00:05:18.710> you<00:05:18.890> also<00:05:19.070> need<00:05:19.280> to<00:05:19.310> know<00:05:19.460> about 00:05:19.600 --> 00:05:19.610 align:start position:0% but then you also need to know about 00:05:19.610 --> 00:05:22.360 align:start position:0% but then you also need to know about those<00:05:19.880> contracts<00:05:20.450> and<00:05:20.830> there's<00:05:21.830> so<00:05:22.280> many 00:05:22.360 --> 00:05:22.370 align:start position:0% those contracts and there's so many 00:05:22.370 --> 00:05:26.080 align:start position:0% those contracts and there's so many different<00:05:22.790> situations<00:05:23.630> that<00:05:24.880> basically<00:05:25.880> that 00:05:26.080 --> 00:05:26.090 align:start position:0% different situations that basically that 00:05:26.090 --> 00:05:29.530 align:start position:0% different situations that basically that needs<00:05:26.600> a<00:05:26.720> political<00:05:27.170> system<00:05:27.320> of<00:05:28.390> projects<00:05:29.390> and 00:05:29.530 --> 00:05:29.540 align:start position:0% needs a political system of projects and 00:05:29.540 --> 00:05:31.930 align:start position:0% needs a political system of projects and organization<00:05:30.530> and<00:05:30.680> they<00:05:30.740> all<00:05:30.920> are<00:05:31.220> active<00:05:31.820> in 00:05:31.930 --> 00:05:31.940 align:start position:0% organization and they all are active in 00:05:31.940 --> 00:05:33.310 align:start position:0% organization and they all are active in slightly<00:05:32.150> different<00:05:32.270> fields<00:05:32.870> but<00:05:33.020> I<00:05:33.050> think 00:05:33.310 --> 00:05:33.320 align:start position:0% slightly different fields but I think 00:05:33.320 --> 00:05:34.540 align:start position:0% slightly different fields but I think they<00:05:33.470> all<00:05:33.650> need<00:05:33.680> to<00:05:33.860> work<00:05:33.980> together<00:05:34.190> because 00:05:34.540 --> 00:05:34.550 align:start position:0% they all need to work together because 00:05:34.550 --> 00:05:36.250 align:start position:0% they all need to work together because there's<00:05:34.970> a<00:05:35.030> lot<00:05:35.210> of<00:05:35.300> different<00:05:35.720> aspects<00:05:36.200> to 00:05:36.250 --> 00:05:36.260 align:start position:0% there's a lot of different aspects to 00:05:36.260 --> 00:05:42.850 align:start position:0% there's a lot of different aspects to this<00:05:36.470> problem<00:05:36.890> so<00:05:40.600> the<00:05:41.600> thing<00:05:41.780> is<00:05:41.810> so<00:05:42.620> that's 00:05:42.850 --> 00:05:42.860 align:start position:0% this problem so the thing is so that's 00:05:42.860 --> 00:05:44.830 align:start position:0% this problem so the thing is so that's the<00:05:42.980> noodle<00:05:43.280> is<00:05:43.460> so<00:05:43.910> crazy<00:05:44.330> we<00:05:44.630> need<00:05:44.750> to 00:05:44.830 --> 00:05:44.840 align:start position:0% the noodle is so crazy we need to 00:05:44.840 --> 00:05:48.700 align:start position:0% the noodle is so crazy we need to collaborate<00:05:45.500> and<00:05:46.900> there<00:05:47.900> is<00:05:47.990> many<00:05:48.230> ways<00:05:48.470> in 00:05:48.700 --> 00:05:48.710 align:start position:0% collaborate and there is many ways in 00:05:48.710 --> 00:05:50.500 align:start position:0% collaborate and there is many ways in which<00:05:48.830> we<00:05:48.980> can<00:05:49.130> do<00:05:49.280> it<00:05:49.400> one<00:05:49.640> way<00:05:49.850> in<00:05:49.910> which<00:05:50.300> we 00:05:50.500 --> 00:05:50.510 align:start position:0% which we can do it one way in which we 00:05:50.510 --> 00:05:51.880 align:start position:0% which we can do it one way in which we were<00:05:50.660> thinking<00:05:50.990> where<00:05:51.170> to<00:05:51.200> have<00:05:51.500> like<00:05:51.680> some 00:05:51.880 --> 00:05:51.890 align:start position:0% were thinking where to have like some 00:05:51.890 --> 00:05:56.050 align:start position:0% were thinking where to have like some kind<00:05:52.100> of<00:05:52.130> open<00:05:52.490> API<00:05:53.210> standards<00:05:54.080> in<00:05:54.860> in<00:05:55.820> ways 00:05:56.050 --> 00:05:56.060 align:start position:0% kind of open API standards in in ways 00:05:56.060 --> 00:06:01.240 align:start position:0% kind of open API standards in in ways that<00:05:56.890> we<00:05:57.890> can<00:05:58.130> basically<00:05:58.490> use<00:05:59.620> the<00:06:00.620> tool<00:06:00.890> to 00:06:01.240 --> 00:06:01.250 align:start position:0% that we can basically use the tool to 00:06:01.250 --> 00:06:04.060 align:start position:0% that we can basically use the tool to different<00:06:01.550> projects<00:06:02.290> services<00:06:03.290> or<00:06:03.500> libraries 00:06:04.060 --> 00:06:04.070 align:start position:0% different projects services or libraries 00:06:04.070 --> 00:06:06.520 align:start position:0% different projects services or libraries or<00:06:04.220> whatever<00:06:04.580> they<00:06:04.790> are<00:06:04.820> all<00:06:05.090> and<00:06:05.390> mesh<00:06:06.080> mesh 00:06:06.520 --> 00:06:06.530 align:start position:0% or whatever they are all and mesh mesh 00:06:06.530 --> 00:06:08.320 align:start position:0% or whatever they are all and mesh mesh them<00:06:06.740> and<00:06:06.950> to<00:06:07.610> improve<00:06:08.030> the<00:06:08.150> situation 00:06:08.320 --> 00:06:08.330 align:start position:0% them and to improve the situation 00:06:08.330 --> 00:06:11.230 align:start position:0% them and to improve the situation because<00:06:08.930> one<00:06:09.440> project<00:06:09.800> alone<00:06:10.010> it's<00:06:10.820> hard<00:06:11.060> for 00:06:11.230 --> 00:06:11.240 align:start position:0% because one project alone it's hard for 00:06:11.240 --> 00:06:13.570 align:start position:0% because one project alone it's hard for them<00:06:11.360> to<00:06:11.420> change<00:06:12.290> everything<00:06:13.010> like<00:06:13.280> ether 00:06:13.570 --> 00:06:13.580 align:start position:0% them to change everything like ether 00:06:13.580 --> 00:06:15.940 align:start position:0% them to change everything like ether scans<00:06:13.910> all<00:06:14.030> the<00:06:14.120> contracts<00:06:14.540> but<00:06:15.200> there's 00:06:15.940 --> 00:06:15.950 align:start position:0% scans all the contracts but there's 00:06:15.950 --> 00:06:17.620 align:start position:0% scans all the contracts but there's auditors<00:06:16.430> but<00:06:16.460> the<00:06:16.790> NIA<00:06:16.940> also<00:06:17.330> that 00:06:17.620 --> 00:06:17.630 align:start position:0% auditors but the NIA also that 00:06:17.630 --> 00:06:19.930 align:start position:0% auditors but the NIA also that developers<00:06:18.140> and<00:06:18.380> everyone<00:06:19.190> and<00:06:19.610> then<00:06:19.760> your 00:06:19.930 --> 00:06:19.940 align:start position:0% developers and everyone and then your 00:06:19.940 --> 00:06:22.830 align:start position:0% developers and everyone and then your auto<00:06:20.150> wallets<00:06:20.540> so<00:06:21.230> every<00:06:21.830> everyone<00:06:22.490> has 00:06:22.830 --> 00:06:22.840 align:start position:0% auto wallets so every everyone has 00:06:22.840 --> 00:06:24.090 align:start position:0% auto wallets so every everyone has the<00:06:22.930> user<00:06:23.110> basement<00:06:23.620> has<00:06:23.710> some<00:06:23.860> kind<00:06:24.070> of 00:06:24.090 --> 00:06:24.100 align:start position:0% the user basement has some kind of 00:06:24.100 --> 00:06:26.760 align:start position:0% the user basement has some kind of expertise<00:06:24.639> and<00:06:24.910> you<00:06:25.419> maybe<00:06:26.110> change<00:06:26.500> something 00:06:26.760 --> 00:06:26.770 align:start position:0% expertise and you maybe change something 00:06:26.770 --> 00:06:28.320 align:start position:0% expertise and you maybe change something you<00:06:26.950> have<00:06:27.100> like<00:06:27.250> a<00:06:27.280> standard<00:06:27.760> or<00:06:27.970> a<00:06:28.000> way<00:06:28.210> of 00:06:28.320 --> 00:06:28.330 align:start position:0% you have like a standard or a way of 00:06:28.330 --> 00:06:31.170 align:start position:0% you have like a standard or a way of Weasley's<00:06:28.889> across<00:06:29.889> those<00:06:30.220> different<00:06:30.580> kinds 00:06:31.170 --> 00:06:31.180 align:start position:0% Weasley's across those different kinds 00:06:31.180 --> 00:06:33.960 align:start position:0% Weasley's across those different kinds of<00:06:31.240> organizations<00:06:32.070> and<00:06:33.070> like<00:06:33.430> each<00:06:33.610> project 00:06:33.960 --> 00:06:33.970 align:start position:0% of organizations and like each project 00:06:33.970 --> 00:06:35.970 align:start position:0% of organizations and like each project alone<00:06:34.210> might<00:06:34.780> have<00:06:34.990> a<00:06:35.050> hard<00:06:35.260> time<00:06:35.500> doing<00:06:35.770> it 00:06:35.970 --> 00:06:35.980 align:start position:0% alone might have a hard time doing it 00:06:35.980 --> 00:06:37.830 align:start position:0% alone might have a hard time doing it because<00:06:36.130> it<00:06:36.430> requires<00:06:36.790> others<00:06:37.210> to<00:06:37.600> make<00:06:37.750> it 00:06:37.830 --> 00:06:37.840 align:start position:0% because it requires others to make it 00:06:37.840 --> 00:06:40.379 align:start position:0% because it requires others to make it also<00:06:37.990> change<00:06:38.340> so<00:06:39.340> let's<00:06:39.700> make<00:06:39.880> way<00:06:40.150> the 00:06:40.379 --> 00:06:40.389 align:start position:0% also change so let's make way the 00:06:40.389 --> 00:06:42.600 align:start position:0% also change so let's make way the straightness<00:06:40.900> but<00:06:41.710> as<00:06:41.830> good<00:06:41.980> as<00:06:42.130> it<00:06:42.280> could<00:06:42.430> be 00:06:42.600 --> 00:06:42.610 align:start position:0% straightness but as good as it could be 00:06:42.610 --> 00:06:47.220 align:start position:0% straightness but as good as it could be and<00:06:43.830> yeah<00:06:44.830> like<00:06:45.400> you<00:06:45.880> have<00:06:46.450> it<00:06:46.540> scalability 00:06:47.220 --> 00:06:47.230 align:start position:0% and yeah like you have it scalability 00:06:47.230 --> 00:06:53.220 align:start position:0% and yeah like you have it scalability centralized<00:06:51.540> this<00:06:52.540> is<00:06:52.660> where<00:06:52.810> you<00:06:52.900> started 00:06:53.220 --> 00:06:53.230 align:start position:0% centralized this is where you started 00:06:53.230 --> 00:06:54.870 align:start position:0% centralized this is where you started this<00:06:53.320> project<00:06:53.560> from<00:06:53.919> smart<00:06:54.280> control<00:06:54.610> codes 00:06:54.870 --> 00:06:54.880 align:start position:0% this project from smart control codes 00:06:54.880 --> 00:06:56.850 align:start position:0% this project from smart control codes which<00:06:55.810> is<00:06:56.020> basically<00:06:56.440> a<00:06:56.530> peer-to-peer 00:06:56.850 --> 00:06:56.860 align:start position:0% which is basically a peer-to-peer 00:06:56.860 --> 00:06:59.159 align:start position:0% which is basically a peer-to-peer database<00:06:57.550> and<00:06:57.940> a<00:06:58.360> search<00:06:58.600> engine<00:06:58.810> for 00:06:59.159 --> 00:06:59.169 align:start position:0% database and a search engine for 00:06:59.169 --> 00:07:04.650 align:start position:0% database and a search engine for verified<00:06:59.620> source<00:06:59.830> code<00:07:00.130> so<00:07:01.889> I<00:07:03.330> mean<00:07:04.330> let's 00:07:04.650 --> 00:07:04.660 align:start position:0% verified source code so I mean let's 00:07:04.660 --> 00:07:06.840 align:start position:0% verified source code so I mean let's just<00:07:05.080> go<00:07:05.229> over<00:07:05.560> quickly<00:07:05.740> so<00:07:06.040> here's<00:07:06.490> maybe 00:07:06.840 --> 00:07:06.850 align:start position:0% just go over quickly so here's maybe 00:07:06.850 --> 00:07:09.030 align:start position:0% just go over quickly so here's maybe this<00:07:07.540> could<00:07:07.750> be<00:07:07.810> a<00:07:07.930> point<00:07:08.229> where<00:07:08.440> we<00:07:08.560> can<00:07:08.710> try 00:07:09.030 --> 00:07:09.040 align:start position:0% this could be a point where we can try 00:07:09.040 --> 00:07:12.090 align:start position:0% this could be a point where we can try out<00:07:09.250> to<00:07:09.790> improve<00:07:10.030> the<00:07:10.150> situation<00:07:10.330> and<00:07:11.100> there 00:07:12.090 --> 00:07:12.100 align:start position:0% out to improve the situation and there 00:07:12.100 --> 00:07:13.920 align:start position:0% out to improve the situation and there are<00:07:12.160> multiple<00:07:12.520> aspects<00:07:12.880> to<00:07:13.060> this<00:07:13.150> like<00:07:13.419> one<00:07:13.630> is 00:07:13.920 --> 00:07:13.930 align:start position:0% are multiple aspects to this like one is 00:07:13.930 --> 00:07:19.710 align:start position:0% are multiple aspects to this like one is we<00:07:14.139> have<00:07:14.470> a<00:07:14.770> lot<00:07:15.250> of<00:07:16.950> data<00:07:17.950> that<00:07:18.160> is<00:07:18.460> I<00:07:18.940> mean<00:07:19.210> for 00:07:19.710 --> 00:07:19.720 align:start position:0% we have a lot of data that is I mean for 00:07:19.720 --> 00:07:21.090 align:start position:0% we have a lot of data that is I mean for example<00:07:20.080> for<00:07:20.200> the<00:07:20.260> server<00:07:20.470> for<00:07:20.800> the<00:07:20.860> source 00:07:21.090 --> 00:07:21.100 align:start position:0% example for the server for the source 00:07:21.100 --> 00:07:22.590 align:start position:0% example for the server for the source code<00:07:21.280> as<00:07:21.430> such<00:07:21.610> we<00:07:21.790> could<00:07:21.970> publish<00:07:22.300> them<00:07:22.479> and 00:07:22.590 --> 00:07:22.600 align:start position:0% code as such we could publish them and 00:07:22.600 --> 00:07:24.120 align:start position:0% code as such we could publish them and then<00:07:22.720> you<00:07:22.810> have<00:07:22.840> a<00:07:22.960> way<00:07:23.169> of<00:07:23.350> retrieving<00:07:23.830> them 00:07:24.120 --> 00:07:24.130 align:start position:0% then you have a way of retrieving them 00:07:24.130 --> 00:07:27.080 align:start position:0% then you have a way of retrieving them and<00:07:24.460> maybe<00:07:25.120> verifying<00:07:25.690> them<00:07:25.900> but<00:07:26.050> like<00:07:26.169> still 00:07:27.080 --> 00:07:27.090 align:start position:0% and maybe verifying them but like still 00:07:27.090 --> 00:07:30.810 align:start position:0% and maybe verifying them but like still there's<00:07:28.090> a<00:07:28.419> lot<00:07:28.750> of<00:07:28.840> auditors<00:07:29.260> and<00:07:29.590> also<00:07:30.370> the 00:07:30.810 --> 00:07:30.820 align:start position:0% there's a lot of auditors and also the 00:07:30.820 --> 00:07:32.670 align:start position:0% there's a lot of auditors and also the wallets<00:07:31.150> that<00:07:31.330> might<00:07:31.539> want<00:07:31.690> to<00:07:31.810> show<00:07:32.080> certain 00:07:32.670 --> 00:07:32.680 align:start position:0% wallets that might want to show certain 00:07:32.680 --> 00:07:34.800 align:start position:0% wallets that might want to show certain information<00:07:33.280> about<00:07:33.490> this<00:07:33.729> and<00:07:34.000> can<00:07:34.690> we 00:07:34.800 --> 00:07:34.810 align:start position:0% information about this and can we 00:07:34.810 --> 00:07:36.240 align:start position:0% information about this and can we publish<00:07:35.200> this<00:07:35.380> doesn't<00:07:35.770> need<00:07:35.830> to<00:07:35.979> be<00:07:36.070> updated 00:07:36.240 --> 00:07:36.250 align:start position:0% publish this doesn't need to be updated 00:07:36.250 --> 00:07:39.560 align:start position:0% publish this doesn't need to be updated maybe<00:07:36.729> a<00:07:36.910> certain<00:07:37.840> contract<00:07:38.470> is<00:07:38.590> updatable<00:07:39.250> or 00:07:39.560 --> 00:07:39.570 align:start position:0% maybe a certain contract is updatable or 00:07:39.570 --> 00:07:42.690 align:start position:0% maybe a certain contract is updatable or there's<00:07:40.770> multiple<00:07:41.770> bursts<00:07:42.010> and<00:07:42.220> one<00:07:42.370> has<00:07:42.550> been 00:07:42.690 --> 00:07:42.700 align:start position:0% there's multiple bursts and one has been 00:07:42.700 --> 00:07:44.610 align:start position:0% there's multiple bursts and one has been wanted<00:07:43.000> but<00:07:43.240> the<00:07:43.360> next<00:07:43.630> not<00:07:43.930> or<00:07:44.169> maybe<00:07:44.440> you 00:07:44.610 --> 00:07:44.620 align:start position:0% wanted but the next not or maybe you 00:07:44.620 --> 00:07:46.650 align:start position:0% wanted but the next not or maybe you don't<00:07:44.830> only<00:07:45.010> want<00:07:45.190> to<00:07:45.370> use<00:07:45.400> part<00:07:46.060> of<00:07:46.510> the 00:07:46.650 --> 00:07:46.660 align:start position:0% don't only want to use part of the 00:07:46.660 --> 00:07:48.120 align:start position:0% don't only want to use part of the contract<00:07:46.990> functionality<00:07:47.590> maybe<00:07:47.740> interact 00:07:48.120 --> 00:07:48.130 align:start position:0% contract functionality maybe interact 00:07:48.130 --> 00:07:50.279 align:start position:0% contract functionality maybe interact with<00:07:48.280> like<00:07:48.400> two<00:07:48.610> functions<00:07:49.090> and<00:07:49.240> those<00:07:50.050> maybe 00:07:50.279 --> 00:07:50.289 align:start position:0% with like two functions and those maybe 00:07:50.289 --> 00:07:51.719 align:start position:0% with like two functions and those maybe have<00:07:50.470> been<00:07:50.620> augmented<00:07:50.950> audited<00:07:51.400> even<00:07:51.639> though 00:07:51.719 --> 00:07:51.729 align:start position:0% have been augmented audited even though 00:07:51.729 --> 00:07:55.140 align:start position:0% have been augmented audited even though the<00:07:51.940> rest<00:07:52.090> has<00:07:52.330> been<00:07:52.570> updated<00:07:53.200> and<00:07:53.850> all<00:07:54.850> these 00:07:55.140 --> 00:07:55.150 align:start position:0% the rest has been updated and all these 00:07:55.150 --> 00:07:57.120 align:start position:0% the rest has been updated and all these things<00:07:55.419> we<00:07:55.900> need<00:07:56.050> to<00:07:56.139> do<00:07:56.260> and<00:07:56.590> because<00:07:56.950> the 00:07:57.120 --> 00:07:57.130 align:start position:0% things we need to do and because the 00:07:57.130 --> 00:07:58.440 align:start position:0% things we need to do and because the data<00:07:57.340> is<00:07:57.520> always<00:07:57.729> changing 00:07:58.440 --> 00:07:58.450 align:start position:0% data is always changing 00:07:58.450 --> 00:08:01.080 align:start position:0% data is always changing I<00:07:58.479> mean<00:07:59.250> when<00:08:00.250> you<00:08:00.370> defer<00:08:00.610> the<00:08:00.729> contract<00:08:01.060> that 00:08:01.080 --> 00:08:01.090 align:start position:0% I mean when you defer the contract that 00:08:01.090 --> 00:08:01.960 align:start position:0% I mean when you defer the contract that particular 00:08:01.960 --> 00:08:01.970 align:start position:0% particular 00:08:01.970 --> 00:08:03.670 align:start position:0% particular kissing<00:08:02.330> you<00:08:02.420> talk<00:08:02.630> about<00:08:02.930> the<00:08:03.140> whole<00:08:03.320> list<00:08:03.500> of 00:08:03.670 --> 00:08:03.680 align:start position:0% kissing you talk about the whole list of 00:08:03.680 --> 00:08:04.960 align:start position:0% kissing you talk about the whole list of conflicts<00:08:04.070> there<00:08:04.220> will<00:08:04.340> be<00:08:04.370> always<00:08:04.760> new 00:08:04.960 --> 00:08:04.970 align:start position:0% conflicts there will be always new 00:08:04.970 --> 00:08:07.180 align:start position:0% conflicts there will be always new contracts<00:08:05.510> and<00:08:05.660> also<00:08:06.230> maybe<00:08:06.500> new<00:08:06.710> versions<00:08:07.100> of 00:08:07.180 --> 00:08:07.190 align:start position:0% contracts and also maybe new versions of 00:08:07.190 --> 00:08:10.210 align:start position:0% contracts and also maybe new versions of contracts<00:08:07.700> so<00:08:08.360> in<00:08:08.690> order<00:08:08.930> to<00:08:09.350> get<00:08:09.800> all<00:08:10.070> the 00:08:10.210 --> 00:08:10.220 align:start position:0% contracts so in order to get all the 00:08:10.220 --> 00:08:12.640 align:start position:0% contracts so in order to get all the also<00:08:10.700> with<00:08:11.480> the<00:08:11.570> audits<00:08:11.900> that's<00:08:12.230> kind<00:08:12.470> of<00:08:12.530> the 00:08:12.640 --> 00:08:12.650 align:start position:0% also with the audits that's kind of the 00:08:12.650 --> 00:08:14.230 align:start position:0% also with the audits that's kind of the same<00:08:12.860> like<00:08:13.040> if<00:08:13.160> you<00:08:13.280> depart<00:08:13.700> it<00:08:13.820> may<00:08:13.970> be<00:08:14.030> the 00:08:14.230 --> 00:08:14.240 align:start position:0% same like if you depart it may be the 00:08:14.240 --> 00:08:15.460 align:start position:0% same like if you depart it may be the next<00:08:14.450> version<00:08:14.720> of<00:08:14.810> your<00:08:14.930> contract 00:08:15.460 --> 00:08:15.470 align:start position:0% next version of your contract 00:08:15.470 --> 00:08:17.530 align:start position:0% next version of your contract so<00:08:15.860> all<00:08:16.010> these<00:08:16.100> updates<00:08:16.370> need<00:08:17.270> like<00:08:17.510> a 00:08:17.530 --> 00:08:17.540 align:start position:0% so all these updates need like a 00:08:17.540 --> 00:08:19.380 align:start position:0% so all these updates need like a mechanism<00:08:18.050> that<00:08:18.260> you<00:08:18.380> can<00:08:18.560> also<00:08:18.770> easily 00:08:19.380 --> 00:08:19.390 align:start position:0% mechanism that you can also easily 00:08:19.390 --> 00:08:23.410 align:start position:0% mechanism that you can also easily update<00:08:20.390> and<00:08:20.720> interact<00:08:21.080> and<00:08:21.350> still<00:08:22.420> even 00:08:23.410 --> 00:08:23.420 align:start position:0% update and interact and still even 00:08:23.420 --> 00:08:25.690 align:start position:0% update and interact and still even though<00:08:23.600> updates<00:08:24.260> are<00:08:24.410> possible<00:08:24.890> you<00:08:25.400> want<00:08:25.550> to 00:08:25.690 --> 00:08:25.700 align:start position:0% though updates are possible you want to 00:08:25.700 --> 00:08:27.730 align:start position:0% though updates are possible you want to be<00:08:25.940> able<00:08:26.360> to<00:08:26.540> trust<00:08:26.780> or<00:08:27.080> have<00:08:27.230> it<00:08:27.320> as<00:08:27.380> trust 00:08:27.730 --> 00:08:27.740 align:start position:0% be able to trust or have it as trust 00:08:27.740 --> 00:08:31.960 align:start position:0% be able to trust or have it as trust business<00:08:27.890> possible<00:08:29.890> say<00:08:30.890> how<00:08:31.310> do<00:08:31.580> we<00:08:31.700> do<00:08:31.820> that 00:08:31.960 --> 00:08:31.970 align:start position:0% business possible say how do we do that 00:08:31.970 --> 00:08:34.180 align:start position:0% business possible say how do we do that like<00:08:32.240> that<00:08:32.270> the<00:08:33.050> idea<00:08:33.349> about<00:08:33.500> this<00:08:33.770> database 00:08:34.180 --> 00:08:34.190 align:start position:0% like that the idea about this database 00:08:34.190 --> 00:08:36.279 align:start position:0% like that the idea about this database is<00:08:34.580> that<00:08:34.610> we<00:08:34.940> have<00:08:35.150> first<00:08:35.960> of<00:08:36.050> all<00:08:36.140> like<00:08:36.229> a 00:08:36.279 --> 00:08:36.289 align:start position:0% is that we have first of all like a 00:08:36.289 --> 00:08:38.230 align:start position:0% is that we have first of all like a neutral<00:08:36.650> place<00:08:36.919> so<00:08:37.219> you<00:08:37.400> could<00:08:37.610> of<00:08:37.760> course<00:08:37.969> use 00:08:38.230 --> 00:08:38.240 align:start position:0% neutral place so you could of course use 00:08:38.240 --> 00:08:41.529 align:start position:0% neutral place so you could of course use the<00:08:38.690> peer-to-peer<00:08:39.229> network<00:08:39.490> to<00:08:40.490> retrieve<00:08:41.240> all 00:08:41.529 --> 00:08:41.539 align:start position:0% the peer-to-peer network to retrieve all 00:08:41.539 --> 00:08:43.420 align:start position:0% the peer-to-peer network to retrieve all these<00:08:41.690> kind<00:08:41.900> of<00:08:41.930> different<00:08:42.289> information<00:08:42.500> but 00:08:43.420 --> 00:08:43.430 align:start position:0% these kind of different information but 00:08:43.430 --> 00:08:45.010 align:start position:0% these kind of different information but also<00:08:43.640> if<00:08:43.909> you<00:08:43.940> ever<00:08:44.060> have<00:08:44.330> an<00:08:44.420> organization 00:08:45.010 --> 00:08:45.020 align:start position:0% also if you ever have an organization 00:08:45.020 --> 00:08:46.720 align:start position:0% also if you ever have an organization like<00:08:45.050> as<00:08:45.290> an<00:08:45.380> auditor<00:08:45.740> for<00:08:45.770> example<00:08:46.370> it<00:08:46.550> could 00:08:46.720 --> 00:08:46.730 align:start position:0% like as an auditor for example it could 00:08:46.730 --> 00:08:50.800 align:start position:0% like as an auditor for example it could have<00:08:47.660> your<00:08:47.810> own<00:08:47.870> copy<00:08:48.350> of<00:08:49.000> the<00:08:50.000> data<00:08:50.330> set<00:08:50.660> but 00:08:50.800 --> 00:08:50.810 align:start position:0% have your own copy of the data set but 00:08:50.810 --> 00:08:52.900 align:start position:0% have your own copy of the data set but penetrated<00:08:51.560> so<00:08:51.710> for<00:08:52.130> example<00:08:52.400> you<00:08:52.490> could<00:08:52.670> say 00:08:52.900 --> 00:08:52.910 align:start position:0% penetrated so for example you could say 00:08:52.910 --> 00:08:55.870 align:start position:0% penetrated so for example you could say these<00:08:53.510> are<00:08:53.690> all<00:08:53.810> the<00:08:53.900> ones<00:08:54.050> that<00:08:54.140> I<00:08:54.880> contracted 00:08:55.870 --> 00:08:55.880 align:start position:0% these are all the ones that I contracted 00:08:55.880 --> 00:08:57.760 align:start position:0% these are all the ones that I contracted be<00:08:56.090> audited<00:08:56.630> when<00:08:57.050> those<00:08:57.200> kind<00:08:57.410> of<00:08:57.470> under 00:08:57.760 --> 00:08:57.770 align:start position:0% be audited when those kind of under 00:08:57.770 --> 00:09:00.190 align:start position:0% be audited when those kind of under versions<00:08:58.100> and<00:08:58.280> then<00:08:58.850> this<00:08:58.970> information<00:08:59.300> could 00:09:00.190 --> 00:09:00.200 align:start position:0% versions and then this information could 00:09:00.200 --> 00:09:03.220 align:start position:0% versions and then this information could be<00:09:00.260> used<00:09:00.470> on<00:09:00.680> one<00:09:01.490> place<00:09:01.790> like<00:09:02.210> this<00:09:02.990> search 00:09:03.220 --> 00:09:03.230 align:start position:0% be used on one place like this search 00:09:03.230 --> 00:09:06.220 align:start position:0% be used on one place like this search interface<00:09:03.680> to<00:09:04.220> display<00:09:04.730> all<00:09:05.360> the<00:09:05.420> contracts 00:09:06.220 --> 00:09:06.230 align:start position:0% interface to display all the contracts 00:09:06.230 --> 00:09:08.650 align:start position:0% interface to display all the contracts that<00:09:06.260> have<00:09:06.500> been<00:09:06.680> audited<00:09:07.670> by<00:09:08.180> whom<00:09:08.360> they<00:09:08.510> have 00:09:08.650 --> 00:09:08.660 align:start position:0% that have been audited by whom they have 00:09:08.660 --> 00:09:11.050 align:start position:0% that have been audited by whom they have been<00:09:08.810> audited<00:09:08.990> to<00:09:09.290> which<00:09:09.410> versions<00:09:09.950> and<00:09:10.190> there 00:09:11.050 --> 00:09:11.060 align:start position:0% been audited to which versions and there 00:09:11.060 --> 00:09:12.460 align:start position:0% been audited to which versions and there might<00:09:11.210> be<00:09:11.240> updates<00:09:11.690> coming<00:09:11.960> to<00:09:12.110> this<00:09:12.230> but 00:09:12.460 --> 00:09:12.470 align:start position:0% might be updates coming to this but 00:09:12.470 --> 00:09:16.470 align:start position:0% might be updates coming to this but every<00:09:13.300> every<00:09:14.300> node<00:09:15.140> of<00:09:15.440> the<00:09:15.530> database<00:09:15.950> under 00:09:16.470 --> 00:09:16.480 align:start position:0% every every node of the database under 00:09:16.480 --> 00:09:19.120 align:start position:0% every every node of the database under hosted<00:09:17.480> by<00:09:17.600> one<00:09:17.900> particular<00:09:18.200> person 00:09:19.120 --> 00:09:19.130 align:start position:0% hosted by one particular person 00:09:19.130 --> 00:09:21.610 align:start position:0% hosted by one particular person organization<00:09:20.060> could<00:09:20.690> update<00:09:21.290> their 00:09:21.610 --> 00:09:21.620 align:start position:0% organization could update their 00:09:21.620 --> 00:09:23.650 align:start position:0% organization could update their annotations<00:09:22.310> and<00:09:22.550> all<00:09:22.820> these<00:09:22.970> different<00:09:23.270> data 00:09:23.650 --> 00:09:23.660 align:start position:0% annotations and all these different data 00:09:23.660 --> 00:09:29.110 align:start position:0% annotations and all these different data basically<00:09:24.400> is<00:09:25.400> merged<00:09:25.820> or<00:09:26.060> or<00:09:26.960> shown<00:09:27.320> in<00:09:28.120> like 00:09:29.110 --> 00:09:29.120 align:start position:0% basically is merged or or shown in like 00:09:29.120 --> 00:09:32.530 align:start position:0% basically is merged or or shown in like a<00:09:29.270> mixed<00:09:30.140> mixed<00:09:30.650> way<00:09:30.860> so<00:09:31.730> that's<00:09:31.970> why<00:09:32.180> we<00:09:32.360> also 00:09:32.530 --> 00:09:32.540 align:start position:0% a mixed mixed way so that's why we also 00:09:32.540 --> 00:09:36.100 align:start position:0% a mixed mixed way so that's why we also have<00:09:32.780> this<00:09:33.050> second<00:09:33.620> part<00:09:33.830> that<00:09:34.070> connect<00:09:35.110> maybe 00:09:36.100 --> 00:09:36.110 align:start position:0% have this second part that connect maybe 00:09:36.110 --> 00:09:38.090 align:start position:0% have this second part that connect maybe I<00:09:36.440> assume<00:09:36.950> that<00:09:36.980> many<00:09:37.310> of<00:09:37.430> you<00:09:37.520> might 00:09:38.090 --> 00:09:38.100 align:start position:0% I assume that many of you might 00:09:38.100 --> 00:09:42.139 align:start position:0% I assume that many of you might remix<00:09:38.550> as<00:09:38.819> a<00:09:39.110> in-browser<00:09:40.110> ide<00:09:40.769> and<00:09:41.160> it<00:09:41.759> happens 00:09:42.139 --> 00:09:42.149 align:start position:0% remix as a in-browser ide and it happens 00:09:42.149 --> 00:09:43.999 align:start position:0% remix as a in-browser ide and it happens not<00:09:42.540> the<00:09:42.630> only<00:09:42.839> project<00:09:43.019> but<00:09:43.319> they<00:09:43.410> have<00:09:43.620> this 00:09:43.999 --> 00:09:44.009 align:start position:0% not the only project but they have this 00:09:44.009 --> 00:09:47.269 align:start position:0% not the only project but they have this approach<00:09:44.430> of<00:09:44.550> having<00:09:44.699> plugins<00:09:45.560> and<00:09:46.560> we<00:09:47.009> want 00:09:47.269 --> 00:09:47.279 align:start position:0% approach of having plugins and we want 00:09:47.279 --> 00:09:49.879 align:start position:0% approach of having plugins and we want to<00:09:47.399> see<00:09:48.269> how<00:09:48.509> we<00:09:48.569> can<00:09:48.870> maybe<00:09:49.050> make<00:09:49.170> it<00:09:49.500> so<00:09:49.740> that 00:09:49.879 --> 00:09:49.889 align:start position:0% to see how we can maybe make it so that 00:09:49.889 --> 00:09:51.530 align:start position:0% to see how we can maybe make it so that all<00:09:50.279> these<00:09:50.579> different<00:09:50.759> like<00:09:51.209> whether<00:09:51.389> they 00:09:51.530 --> 00:09:51.540 align:start position:0% all these different like whether they 00:09:51.540 --> 00:09:53.809 align:start position:0% all these different like whether they are<00:09:51.600> wallets<00:09:51.990> or<00:09:52.350> whatever<00:09:52.949> is<00:09:53.160> their<00:09:53.339> app<00:09:53.610> or 00:09:53.809 --> 00:09:53.819 align:start position:0% are wallets or whatever is their app or 00:09:53.819 --> 00:09:55.129 align:start position:0% are wallets or whatever is their app or software<00:09:54.029> they're<00:09:54.449> using<00:09:54.480> that<00:09:54.839> we<00:09:54.959> can 00:09:55.129 --> 00:09:55.139 align:start position:0% software they're using that we can 00:09:55.139 --> 00:09:58.040 align:start position:0% software they're using that we can connect<00:09:56.009> them<00:09:56.160> together<00:09:56.509> in<00:09:57.509> a<00:09:57.630> way<00:09:57.660> that<00:09:57.750> like 00:09:58.040 --> 00:09:58.050 align:start position:0% connect them together in a way that like 00:09:58.050 --> 00:10:01.999 align:start position:0% connect them together in a way that like maybe<00:09:58.490> as<00:09:59.490> a<00:09:59.550> particular<00:09:59.880> app<00:10:00.329> or<00:10:00.720> or<00:10:01.470> whatever 00:10:01.999 --> 00:10:02.009 align:start position:0% maybe as a particular app or or whatever 00:10:02.009 --> 00:10:04.819 align:start position:0% maybe as a particular app or or whatever whatever<00:10:02.579> the<00:10:02.880> software<00:10:03.269> is<00:10:03.420> wants<00:10:04.019> to<00:10:04.199> reuse 00:10:04.819 --> 00:10:04.829 align:start position:0% whatever the software is wants to reuse 00:10:04.829 --> 00:10:07.340 align:start position:0% whatever the software is wants to reuse the<00:10:05.130> code<00:10:05.310> or<00:10:05.730> maybe<00:10:05.759> we<00:10:06.540> on<00:10:06.810> the<00:10:06.959> smart 00:10:07.340 --> 00:10:07.350 align:start position:0% the code or maybe we on the smart 00:10:07.350 --> 00:10:10.160 align:start position:0% the code or maybe we on the smart computer<00:10:07.680> phones<00:10:08.009> would<00:10:08.220> allow<00:10:09.170> the 00:10:10.160 --> 00:10:10.170 align:start position:0% computer phones would allow the 00:10:10.170 --> 00:10:12.499 align:start position:0% computer phones would allow the connection<00:10:10.410> or<00:10:10.740> embedded<00:10:11.279> suite<00:10:11.519> goes<00:10:12.029> both 00:10:12.499 --> 00:10:12.509 align:start position:0% connection or embedded suite goes both 00:10:12.509 --> 00:10:15.350 align:start position:0% connection or embedded suite goes both ways<00:10:12.540> when<00:10:13.350> plugin<00:10:13.850> usually<00:10:14.850> as<00:10:14.970> a<00:10:15.029> standalone 00:10:15.350 --> 00:10:15.360 align:start position:0% ways when plugin usually as a standalone 00:10:15.360 --> 00:10:17.389 align:start position:0% ways when plugin usually as a standalone thing<00:10:15.630> is<00:10:15.990> relatively<00:10:16.589> business<00:10:17.009> it<00:10:17.190> only 00:10:17.389 --> 00:10:17.399 align:start position:0% thing is relatively business it only 00:10:17.399 --> 00:10:19.730 align:start position:0% thing is relatively business it only works<00:10:17.639> as<00:10:17.850> a<00:10:18.149> plugin<00:10:18.540> for<00:10:18.569> something<00:10:19.139> but<00:10:19.620> we 00:10:19.730 --> 00:10:19.740 align:start position:0% works as a plugin for something but we 00:10:19.740 --> 00:10:21.920 align:start position:0% works as a plugin for something but we want<00:10:19.920> to<00:10:20.250> be<00:10:20.459> able<00:10:20.670> to<00:10:20.850> connect<00:10:21.389> things<00:10:21.630> so 00:10:21.920 --> 00:10:21.930 align:start position:0% want to be able to connect things so 00:10:21.930 --> 00:10:27.199 align:start position:0% want to be able to connect things so then<00:10:22.649> that<00:10:23.339> way<00:10:24.019> let's<00:10:25.019> say<00:10:25.139> a<00:10:25.579> monitor<00:10:26.579> that 00:10:27.199 --> 00:10:27.209 align:start position:0% then that way let's say a monitor that 00:10:27.209 --> 00:10:29.600 align:start position:0% then that way let's say a monitor that displays<00:10:28.110> their<00:10:28.380> audited<00:10:28.769> contracts<00:10:29.339> that 00:10:29.600 --> 00:10:29.610 align:start position:0% displays their audited contracts that 00:10:29.610 --> 00:10:33.590 align:start position:0% displays their audited contracts that could<00:10:30.199> retrieve<00:10:31.199> data<00:10:31.649> from<00:10:31.860> the<00:10:32.430> or<00:10:32.610> making 00:10:33.590 --> 00:10:33.600 align:start position:0% could retrieve data from the or making 00:10:33.600 --> 00:10:35.509 align:start position:0% could retrieve data from the or making their<00:10:33.779> tools<00:10:34.230> to<00:10:34.380> analyze<00:10:34.529> them<00:10:34.920> so<00:10:35.310> you<00:10:35.399> can 00:10:35.509 --> 00:10:35.519 align:start position:0% their tools to analyze them so you can 00:10:35.519 --> 00:10:37.730 align:start position:0% their tools to analyze them so you can use<00:10:35.550> the<00:10:35.759> database<00:10:36.149> to<00:10:36.329> import<00:10:37.139> that<00:10:37.259> data<00:10:37.319> to 00:10:37.730 --> 00:10:37.740 align:start position:0% use the database to import that data to 00:10:37.740 --> 00:10:39.439 align:start position:0% use the database to import that data to show<00:10:37.949> it<00:10:38.069> on<00:10:38.250> their<00:10:38.370> page<00:10:38.610> but<00:10:39.089> the<00:10:39.180> other<00:10:39.329> way 00:10:39.439 --> 00:10:39.449 align:start position:0% show it on their page but the other way 00:10:39.449 --> 00:10:40.970 align:start position:0% show it on their page but the other way around<00:10:39.660> is<00:10:39.779> also<00:10:40.019> possible<00:10:40.440> such<00:10:40.620> a<00:10:40.649> search 00:10:40.970 --> 00:10:40.980 align:start position:0% around is also possible such a search 00:10:40.980 --> 00:10:43.340 align:start position:0% around is also possible such a search engine<00:10:41.250> could<00:10:42.089> or<00:10:42.569> the<00:10:42.720> search<00:10:42.930> interface 00:10:43.340 --> 00:10:43.350 align:start position:0% engine could or the search interface 00:10:43.350 --> 00:10:46.550 align:start position:0% engine could or the search interface code<00:10:43.589> to<00:10:43.740> display<00:10:44.269> or<00:10:45.269> even<00:10:45.720> offer<00:10:45.870> those<00:10:46.199> kind 00:10:46.550 --> 00:10:46.560 align:start position:0% code to display or even offer those kind 00:10:46.560 --> 00:10:51.050 align:start position:0% code to display or even offer those kind of<00:10:46.620> services<00:10:46.860> to<00:10:47.550> to<00:10:49.250> to<00:10:50.250> for<00:10:50.399> example<00:10:50.490> analyze 00:10:51.050 --> 00:10:51.060 align:start position:0% of services to to to for example analyze 00:10:51.060 --> 00:10:54.170 align:start position:0% of services to to to for example analyze the<00:10:51.329> the<00:10:51.360> contracts<00:10:52.259> and<00:10:52.410> give<00:10:52.529> the<00:10:53.009> user<00:10:53.180> or 00:10:54.170 --> 00:10:54.180 align:start position:0% the the contracts and give the user or 00:10:54.180 --> 00:10:55.819 align:start position:0% the the contracts and give the user or even<00:10:54.240> offer<00:10:54.660> the<00:10:54.870> service<00:10:55.170> like<00:10:55.350> there's<00:10:55.589> an 00:10:55.819 --> 00:10:55.829 align:start position:0% even offer the service like there's an 00:10:55.829 --> 00:10:57.410 align:start position:0% even offer the service like there's an auditor<00:10:56.250> that<00:10:56.370> offers<00:10:56.670> a<00:10:56.759> certain<00:10:56.970> service 00:10:57.410 --> 00:10:57.420 align:start position:0% auditor that offers a certain service 00:10:57.420 --> 00:11:00.980 align:start position:0% auditor that offers a certain service and<00:10:57.569> it<00:10:57.630> could<00:10:57.810> be<00:10:59.420> because<00:11:00.420> it<00:11:00.600> could<00:11:00.720> be<00:11:00.959> a 00:11:00.980 --> 00:11:00.990 align:start position:0% and it could be because it could be a 00:11:00.990 --> 00:11:03.740 align:start position:0% and it could be because it could be a way<00:11:01.170> for<00:11:01.470> for<00:11:01.800> users<00:11:02.250> to<00:11:02.370> discover<00:11:02.750> audited 00:11:03.740 --> 00:11:03.750 align:start position:0% way for for users to discover audited 00:11:03.750 --> 00:11:13.400 align:start position:0% way for for users to discover audited contracts<00:11:04.319> and<00:11:05.060> the<00:11:06.060> way<00:11:10.880> and<00:11:12.050> because<00:11:13.050> we 00:11:13.400 --> 00:11:13.410 align:start position:0% contracts and the way and because we 00:11:13.410 --> 00:11:17.390 align:start position:0% contracts and the way and because we want<00:11:13.740> this<00:11:14.069> database<00:11:14.399> to<00:11:14.759> be<00:11:15.350> chewy<00:11:16.350> Center 00:11:17.390 --> 00:11:17.400 align:start position:0% want this database to be chewy Center 00:11:17.400 --> 00:11:20.780 align:start position:0% want this database to be chewy Center so<00:11:17.610> everyone<00:11:18.060> can<00:11:18.480> run<00:11:18.750> an<00:11:18.990> old<00:11:19.550> we're<00:11:20.550> using 00:11:20.780 --> 00:11:20.790 align:start position:0% so everyone can run an old we're using 00:11:20.790 --> 00:11:24.470 align:start position:0% so everyone can run an old we're using that<00:11:21.029> propellant<00:11:21.660> which<00:11:22.520> can<00:11:23.520> handle<00:11:23.910> dynamic 00:11:24.470 --> 00:11:24.480 align:start position:0% that propellant which can handle dynamic 00:11:24.480 --> 00:11:26.510 align:start position:0% that propellant which can handle dynamic data<00:11:24.810> sense<00:11:25.170> so<00:11:25.680> because<00:11:26.070> there<00:11:26.370> is<00:11:26.490> a 00:11:26.510 --> 00:11:26.520 align:start position:0% data sense so because there is a 00:11:26.520 --> 00:11:28.490 align:start position:0% data sense so because there is a database<00:11:27.390> that<00:11:27.450> and<00:11:27.990> we<00:11:28.110> are<00:11:28.200> constantly 00:11:28.490 --> 00:11:28.500 align:start position:0% database that and we are constantly 00:11:28.500 --> 00:11:31.670 align:start position:0% database that and we are constantly publishing<00:11:29.250> new<00:11:29.460> information<00:11:30.240> we<00:11:31.110> can<00:11:31.290> sadly 00:11:31.670 --> 00:11:31.680 align:start position:0% publishing new information we can sadly 00:11:31.680 --> 00:11:35.840 align:start position:0% publishing new information we can sadly not<00:11:31.830> use<00:11:32.750> IBF<00:11:33.750> expertise<00:11:34.290> or<00:11:34.560> it<00:11:35.370> doesn't<00:11:35.730> come 00:11:35.840 --> 00:11:35.850 align:start position:0% not use IBF expertise or it doesn't come 00:11:35.850 --> 00:11:39.470 align:start position:0% not use IBF expertise or it doesn't come out<00:11:36.000> of<00:11:36.150> the<00:11:36.240> box<00:11:36.560> but<00:11:37.560> as<00:11:38.520> Kristin<00:11:39.060> will<00:11:39.270> later 00:11:39.470 --> 00:11:39.480 align:start position:0% out of the box but as Kristin will later 00:11:39.480 --> 00:11:43.850 align:start position:0% out of the box but as Kristin will later show<00:11:39.660> the<00:11:40.110> the<00:11:41.810> source<00:11:42.810> codes<00:11:43.080> will<00:11:43.320> be<00:11:43.350> stored 00:11:43.850 --> 00:11:43.860 align:start position:0% show the the source codes will be stored 00:11:43.860 --> 00:11:44.930 align:start position:0% show the the source codes will be stored on<00:11:44.070> my<00:11:44.220> business 00:11:44.930 --> 00:11:44.940 align:start position:0% on my business 00:11:44.940 --> 00:11:49.970 align:start position:0% on my business probably<00:11:45.630> or<00:11:46.820> possible<00:11:47.820> solution<00:11:48.270> but<00:11:48.980> then 00:11:49.970 --> 00:11:49.980 align:start position:0% probably or possible solution but then 00:11:49.980 --> 00:11:52.460 align:start position:0% probably or possible solution but then we<00:11:50.520> convert<00:11:51.000> them<00:11:51.210> and<00:11:51.480> display<00:11:51.810> them<00:11:51.990> in<00:11:52.080> this 00:11:52.460 --> 00:11:52.470 align:start position:0% we convert them and display them in this 00:11:52.470 --> 00:11:55.160 align:start position:0% we convert them and display them in this database<00:11:53.250> for<00:11:53.580> everyone<00:11:53.940> yeah<00:11:54.540> this<00:11:54.839> is<00:11:54.960> like 00:11:55.160 --> 00:11:55.170 align:start position:0% database for everyone yeah this is like 00:11:55.170 --> 00:11:56.420 align:start position:0% database for everyone yeah this is like I<00:11:55.200> mentioned<00:11:55.560> well<00:11:55.710> it's<00:11:55.830> not<00:11:56.010> a<00:11:56.070> test<00:11:56.279> but 00:11:56.420 --> 00:11:56.430 align:start position:0% I mentioned well it's not a test but 00:11:56.430 --> 00:11:58.720 align:start position:0% I mentioned well it's not a test but also<00:11:56.580> of<00:11:56.790> course<00:11:56.839> developer<00:11:57.839> tools<00:11:58.230> if<00:11:58.380> they 00:11:58.720 --> 00:11:58.730 align:start position:0% also of course developer tools if they 00:11:58.730 --> 00:12:03.500 align:start position:0% also of course developer tools if they support<00:12:00.950> publishing<00:12:01.950> source<00:12:02.430> codes<00:12:02.700> like<00:12:03.120> as 00:12:03.500 --> 00:12:03.510 align:start position:0% support publishing source codes like as 00:12:03.510 --> 00:12:07.040 align:start position:0% support publishing source codes like as an<00:12:03.920> opt-in<00:12:04.920> or<00:12:05.250> maybe<00:12:06.060> ideally<00:12:06.480> as<00:12:06.600> an<00:12:06.690> opt-out 00:12:07.040 --> 00:12:07.050 align:start position:0% an opt-in or maybe ideally as an opt-out 00:12:07.050 --> 00:12:09.380 align:start position:0% an opt-in or maybe ideally as an opt-out mechanism<00:12:07.680> that<00:12:07.890> would<00:12:08.010> also<00:12:08.190> be<00:12:08.400> useful<00:12:08.430> so 00:12:09.380 --> 00:12:09.390 align:start position:0% mechanism that would also be useful so 00:12:09.390 --> 00:12:10.640 align:start position:0% mechanism that would also be useful so somebody<00:12:09.720> who<00:12:09.900> really<00:12:10.110> doesn't<00:12:10.230> want<00:12:10.589> to 00:12:10.640 --> 00:12:10.650 align:start position:0% somebody who really doesn't want to 00:12:10.650 --> 00:12:11.600 align:start position:0% somebody who really doesn't want to publish<00:12:10.980> their<00:12:11.160> source<00:12:11.370> code 00:12:11.600 --> 00:12:11.610 align:start position:0% publish their source code 00:12:11.610 --> 00:12:13.760 align:start position:0% publish their source code you<00:12:11.730> thought<00:12:11.910> you<00:12:12.060> could<00:12:12.089> always<00:12:12.560> put<00:12:13.560> in<00:12:13.680> the 00:12:13.760 --> 00:12:13.770 align:start position:0% you thought you could always put in the 00:12:13.770 --> 00:12:15.230 align:start position:0% you thought you could always put in the effort<00:12:13.890> to<00:12:14.070> T<00:12:14.279> compile<00:12:14.670> it<00:12:14.790> to<00:12:14.850> figure<00:12:15.089> out 00:12:15.230 --> 00:12:15.240 align:start position:0% effort to T compile it to figure out 00:12:15.240 --> 00:12:17.030 align:start position:0% effort to T compile it to figure out because<00:12:15.390> the<00:12:15.960> source<00:12:16.320> code<00:12:16.500> prevent<00:12:16.830> to<00:12:16.920> be 00:12:17.030 --> 00:12:17.040 align:start position:0% because the source code prevent to be 00:12:17.040 --> 00:12:19.070 align:start position:0% because the source code prevent to be small<00:12:17.310> because<00:12:17.610> anyway<00:12:18.270> expensive<00:12:18.779> we<00:12:18.900> have<00:12:18.960> a 00:12:19.070 --> 00:12:19.080 align:start position:0% small because anyway expensive we have a 00:12:19.080 --> 00:12:20.840 align:start position:0% small because anyway expensive we have a little<00:12:19.320> story<00:12:19.560> in<00:12:19.800> computation<00:12:20.100> going<00:12:20.520> on<00:12:20.730> in 00:12:20.840 --> 00:12:20.850 align:start position:0% little story in computation going on in 00:12:20.850 --> 00:12:23.269 align:start position:0% little story in computation going on in the<00:12:20.940> chain<00:12:21.350> that<00:12:22.350> would<00:12:22.470> be<00:12:22.589> of<00:12:22.800> course<00:12:23.040> very 00:12:23.269 --> 00:12:23.279 align:start position:0% the chain that would be of course very 00:12:23.279 --> 00:12:25.820 align:start position:0% the chain that would be of course very useful<00:12:23.640> to<00:12:23.760> know<00:12:24.050> we<00:12:25.050> just<00:12:25.170> picked<00:12:25.470> like<00:12:25.560> from 00:12:25.820 --> 00:12:25.830 align:start position:0% useful to know we just picked like from 00:12:25.830 --> 00:12:29.540 align:start position:0% useful to know we just picked like from each<00:12:25.950> category<00:12:26.250> that<00:12:26.610> we<00:12:26.760> see<00:12:27.000> a<00:12:27.690> few<00:12:28.410> I<00:12:28.740> mean 00:12:29.540 --> 00:12:29.550 align:start position:0% each category that we see a few I mean 00:12:29.550 --> 00:12:32.060 align:start position:0% each category that we see a few I mean not<00:12:30.209> random<00:12:30.600> but<00:12:30.660> like<00:12:30.839> almost<00:12:31.080> like<00:12:31.890> that 00:12:32.060 --> 00:12:32.070 align:start position:0% not random but like almost like that 00:12:32.070 --> 00:12:34.280 align:start position:0% not random but like almost like that there's<00:12:32.279> many<00:12:32.490> more<00:12:33.200> organizations<00:12:34.200> or 00:12:34.280 --> 00:12:34.290 align:start position:0% there's many more organizations or 00:12:34.290 --> 00:12:35.750 align:start position:0% there's many more organizations or projects<00:12:34.680> in<00:12:34.800> each<00:12:34.950> of<00:12:35.070> those<00:12:35.190> categories<00:12:35.430> but 00:12:35.750 --> 00:12:35.760 align:start position:0% projects in each of those categories but 00:12:35.760 --> 00:12:40.840 align:start position:0% projects in each of those categories but just<00:12:36.600> to<00:12:36.750> get<00:12:36.900> like<00:12:37.050> a<00:12:37.080> feeling<00:12:37.950> what<00:12:38.250> we<00:12:38.279> are 00:12:40.840 --> 00:12:40.850 align:start position:0% just to get like a feeling what we are 00:12:40.850 --> 00:12:45.050 align:start position:0% just to get like a feeling what we are what<00:12:41.850> are<00:12:41.970> all<00:12:42.150> the<00:12:42.390> different<00:12:43.790> players<00:12:44.790> in 00:12:45.050 --> 00:12:45.060 align:start position:0% what are all the different players in 00:12:45.060 --> 00:12:48.140 align:start position:0% what are all the different players in the<00:12:45.150> ecosystem<00:12:45.180> that<00:12:45.779> could<00:12:46.170> contribute<00:12:46.529> and 00:12:48.140 --> 00:12:48.150 align:start position:0% the ecosystem that could contribute and 00:12:48.150 --> 00:12:51.290 align:start position:0% the ecosystem that could contribute and to<00:12:48.210> improve<00:12:48.480> the<00:12:48.720> status<00:12:49.470> quo<00:12:50.180> but<00:12:51.180> yeah 00:12:51.290 --> 00:12:51.300 align:start position:0% to improve the status quo but yeah 00:12:51.300 --> 00:12:53.600 align:start position:0% to improve the status quo but yeah that's<00:12:51.660> we<00:12:51.990> would<00:12:52.140> love<00:12:52.290> to<00:12:52.350> discuss<00:12:52.590> to<00:12:53.130> to 00:12:53.600 --> 00:12:53.610 align:start position:0% that's we would love to discuss to to 00:12:53.610 --> 00:12:56.090 align:start position:0% that's we would love to discuss to to get<00:12:53.760> more<00:12:54.180> input<00:12:54.330> to<00:12:54.720> maybe<00:12:54.870> update<00:12:55.440> or<00:12:55.710> make 00:12:56.090 --> 00:12:56.100 align:start position:0% get more input to maybe update or make 00:12:56.100 --> 00:12:59.080 align:start position:0% get more input to maybe update or make the<00:12:56.450> perspective<00:12:57.450> of<00:12:57.570> this<00:12:57.630> a<00:12:57.690> little<00:12:57.900> broader 00:12:59.080 --> 00:12:59.090 align:start position:0% the perspective of this a little broader 00:12:59.090 --> 00:13:01.790 align:start position:0% the perspective of this a little broader yeah<00:13:00.090> so<00:13:00.300> there<00:13:00.450> are<00:13:00.480> CDC<00:13:00.990> developers<00:13:01.530> so 00:13:01.790 --> 00:13:01.800 align:start position:0% yeah so there are CDC developers so 00:13:01.800 --> 00:13:03.800 align:start position:0% yeah so there are CDC developers so people<00:13:02.070> could<00:13:02.190> eventually<00:13:02.430> decodes<00:13:03.240> then<00:13:03.660> you 00:13:03.800 --> 00:13:03.810 align:start position:0% people could eventually decodes then you 00:13:03.810 --> 00:13:06.020 align:start position:0% people could eventually decodes then you have<00:13:04.020> taps<00:13:04.260> basically<00:13:05.100> like<00:13:05.310> business<00:13:05.670> owners 00:13:06.020 --> 00:13:06.030 align:start position:0% have taps basically like business owners 00:13:06.030 --> 00:13:07.850 align:start position:0% have taps basically like business owners or<00:13:06.240> someone<00:13:06.600> who<00:13:06.750> makes<00:13:06.900> a<00:13:07.020> concept<00:13:07.440> of<00:13:07.650> how 00:13:07.850 --> 00:13:07.860 align:start position:0% or someone who makes a concept of how 00:13:07.860 --> 00:13:10.940 align:start position:0% or someone who makes a concept of how how<00:13:08.250> this<00:13:08.490> elliptical<00:13:09.150> truth<00:13:09.510> work<00:13:09.950> that 00:13:10.940 --> 00:13:10.950 align:start position:0% how this elliptical truth work that 00:13:10.950 --> 00:13:13.220 align:start position:0% how this elliptical truth work that tools<00:13:11.280> which<00:13:11.640> enable<00:13:12.000> publishing<00:13:12.780> to<00:13:13.110> the 00:13:13.220 --> 00:13:13.230 align:start position:0% tools which enable publishing to the 00:13:13.230 --> 00:13:15.860 align:start position:0% tools which enable publishing to the network<00:13:13.620> which<00:13:14.040> basically<00:13:14.910> they<00:13:15.330> could<00:13:15.540> also 00:13:15.860 --> 00:13:15.870 align:start position:0% network which basically they could also 00:13:15.870 --> 00:13:17.810 align:start position:0% network which basically they could also publish<00:13:16.350> to<00:13:16.560> the<00:13:16.710> database<00:13:17.160> and<00:13:17.310> then 00:13:17.810 --> 00:13:17.820 align:start position:0% publish to the database and then 00:13:17.820 --> 00:13:19.820 align:start position:0% publish to the database and then everybody<00:13:18.240> could<00:13:18.480> see<00:13:18.510> what<00:13:18.960> is<00:13:19.140> actually<00:13:19.290> the 00:13:19.820 --> 00:13:19.830 align:start position:0% everybody could see what is actually the 00:13:19.830 --> 00:13:22.480 align:start position:0% everybody could see what is actually the source<00:13:20.100> photo<00:13:20.430> of<00:13:20.640> the<00:13:20.820> that<00:13:21.510> they're<00:13:21.750> using 00:13:22.480 --> 00:13:22.490 align:start position:0% source photo of the that they're using 00:13:22.490 --> 00:13:25.010 align:start position:0% source photo of the that they're using security<00:13:23.490> auditors<00:13:24.090> of<00:13:24.120> course<00:13:24.480> taking<00:13:24.810> care 00:13:25.010 --> 00:13:25.020 align:start position:0% security auditors of course taking care 00:13:25.020 --> 00:13:28.730 align:start position:0% security auditors of course taking care of<00:13:26.240> that<00:13:27.240> the<00:13:27.450> contract<00:13:27.960> is<00:13:28.050> secure<00:13:28.500> because 00:13:28.730 --> 00:13:28.740 align:start position:0% of that the contract is secure because 00:13:28.740 --> 00:13:31.400 align:start position:0% of that the contract is secure because verified<00:13:29.490> means<00:13:29.820> only<00:13:30.330> then<00:13:30.630> it<00:13:30.900> does<00:13:31.140> that 00:13:31.400 --> 00:13:31.410 align:start position:0% verified means only then it does that 00:13:31.410 --> 00:13:32.930 align:start position:0% verified means only then it does that it's<00:13:31.560> supposed<00:13:31.800> to<00:13:31.980> do<00:13:32.160> but<00:13:32.310> it<00:13:32.490> doesn't<00:13:32.670> mean 00:13:32.930 --> 00:13:32.940 align:start position:0% it's supposed to do but it doesn't mean 00:13:32.940 --> 00:13:35.720 align:start position:0% it's supposed to do but it doesn't mean it<00:13:33.180> is<00:13:33.360> secure<00:13:34.290> so<00:13:34.950> it<00:13:35.040> can<00:13:35.190> still<00:13:35.370> have<00:13:35.580> some 00:13:35.720 --> 00:13:35.730 align:start position:0% it is secure so it can still have some 00:13:35.730 --> 00:13:38.300 align:start position:0% it is secure so it can still have some bugs<00:13:35.940> or<00:13:36.240> something<00:13:37.070> then<00:13:38.070> we<00:13:38.160> have 00:13:38.300 --> 00:13:38.310 align:start position:0% bugs or something then we have 00:13:38.310 --> 00:13:41.080 align:start position:0% bugs or something then we have infrastructure<00:13:38.940> projects<00:13:39.630> which<00:13:39.690> basically 00:13:41.080 --> 00:13:41.090 align:start position:0% infrastructure projects which basically 00:13:41.090 --> 00:13:42.610 align:start position:0% infrastructure projects which basically [Music] 00:13:42.610 --> 00:13:42.620 align:start position:0% [Music] 00:13:42.620 --> 00:13:47.030 align:start position:0% [Music] enable<00:13:44.120> that<00:13:45.120> this<00:13:45.420> whole<00:13:45.750> thing<00:13:45.930> exists<00:13:46.620> so 00:13:47.030 --> 00:13:47.040 align:start position:0% enable that this whole thing exists so 00:13:47.040 --> 00:13:50.260 align:start position:0% enable that this whole thing exists so to<00:13:47.760> search<00:13:47.970> for<00:13:48.240> for<00:13:48.570> things<00:13:48.750> and<00:13:49.110> to<00:13:49.740> publish 00:13:50.260 --> 00:13:50.270 align:start position:0% to search for for things and to publish 00:13:50.270 --> 00:13:55.840 align:start position:0% to search for for things and to publish and<00:13:51.270> broke<00:13:52.080> and<00:13:52.380> eight<00:13:53.010> explorers<00:13:53.400> which<00:13:54.680> are 00:13:55.840 --> 00:13:55.850 align:start position:0% and broke and eight explorers which are 00:13:55.850 --> 00:13:58.310 align:start position:0% and broke and eight explorers which are basically<00:13:56.850> running<00:13:57.090> notes<00:13:57.570> and<00:13:57.960> getting 00:13:58.310 --> 00:13:58.320 align:start position:0% basically running notes and getting 00:13:58.320 --> 00:13:59.250 align:start position:0% basically running notes and getting information 00:13:59.250 --> 00:13:59.260 align:start position:0% information 00:13:59.260 --> 00:14:01.110 align:start position:0% information boh-chan<00:13:59.590> because<00:13:59.920> every<00:14:00.400> one<00:14:00.550> of<00:14:00.580> us<00:14:00.820> wants 00:14:01.110 --> 00:14:01.120 align:start position:0% boh-chan because every one of us wants 00:14:01.120 --> 00:14:05.010 align:start position:0% boh-chan because every one of us wants to<00:14:01.270> get<00:14:01.480> this<00:14:01.570> information<00:14:02.070> it's<00:14:03.240> hard<00:14:04.240> so<00:14:04.810> we 00:14:05.010 --> 00:14:05.020 align:start position:0% to get this information it's hard so we 00:14:05.020 --> 00:14:06.810 align:start position:0% to get this information it's hard so we need<00:14:05.170> to<00:14:05.260> run<00:14:05.650> it<00:14:05.770> for<00:14:05.920> like<00:14:06.040> months<00:14:06.220> so<00:14:06.700> we 00:14:06.810 --> 00:14:06.820 align:start position:0% need to run it for like months so we 00:14:06.820 --> 00:14:08.760 align:start position:0% need to run it for like months so we have<00:14:07.000> of<00:14:07.120> course<00:14:07.150> like<00:14:07.630> Washington<00:14:08.200> student 00:14:08.760 --> 00:14:08.770 align:start position:0% have of course like Washington student 00:14:08.770 --> 00:14:11.130 align:start position:0% have of course like Washington student and<00:14:09.010> bullets<00:14:09.820> of<00:14:09.940> course<00:14:10.150> because<00:14:10.540> hasn't<00:14:11.020> be 00:14:11.130 --> 00:14:11.140 align:start position:0% and bullets of course because hasn't be 00:14:11.140 --> 00:14:12.870 align:start position:0% and bullets of course because hasn't be the<00:14:11.290> ones<00:14:11.580> displaying<00:14:12.580> this<00:14:12.820> information 00:14:12.870 --> 00:14:12.880 align:start position:0% the ones displaying this information 00:14:12.880 --> 00:14:19.920 align:start position:0% the ones displaying this information that<00:14:13.750> is<00:14:17.160> so<00:14:18.160> what<00:14:18.640> we<00:14:18.850> wanted<00:14:19.180> this<00:14:19.390> is<00:14:19.570> like<00:14:19.720> a 00:14:19.920 --> 00:14:19.930 align:start position:0% that is so what we wanted this is like a 00:14:19.930 --> 00:14:23.010 align:start position:0% that is so what we wanted this is like a short<00:14:20.260> introduction<00:14:20.770> but<00:14:21.760> we<00:14:21.910> do<00:14:22.060> and<00:14:22.480> how<00:14:22.990> we 00:14:23.010 --> 00:14:23.020 align:start position:0% short introduction but we do and how we 00:14:23.020 --> 00:14:25.410 align:start position:0% short introduction but we do and how we are<00:14:23.380> thinking<00:14:23.650> about<00:14:23.770> things<00:14:24.130> but<00:14:24.970> not<00:14:25.210> we 00:14:25.410 --> 00:14:25.420 align:start position:0% are thinking about things but not we 00:14:25.420 --> 00:14:27.780 align:start position:0% are thinking about things but not we would<00:14:25.570> like<00:14:25.720> to<00:14:26.070> hear<00:14:27.070> something<00:14:27.370> from<00:14:27.700> you 00:14:27.780 --> 00:14:27.790 align:start position:0% would like to hear something from you 00:14:27.790 --> 00:14:30.180 align:start position:0% would like to hear something from you like<00:14:28.300> I<00:14:28.570> don't<00:14:28.690> know<00:14:28.870> how<00:14:29.590> do<00:14:29.650> you<00:14:29.770> see<00:14:30.070> the 00:14:30.180 --> 00:14:30.190 align:start position:0% like I don't know how do you see the 00:14:30.190 --> 00:14:32.160 align:start position:0% like I don't know how do you see the ecosystem<00:14:30.370> maybe<00:14:31.000> we<00:14:31.180> didn't<00:14:31.450> even<00:14:31.600> manage<00:14:31.900> to 00:14:32.160 --> 00:14:32.170 align:start position:0% ecosystem maybe we didn't even manage to 00:14:32.170 --> 00:14:35.100 align:start position:0% ecosystem maybe we didn't even manage to capture<00:14:32.560> all<00:14:33.160> the<00:14:33.370> main<00:14:33.700> actors<00:14:34.180> and<00:14:34.510> we 00:14:35.100 --> 00:14:35.110 align:start position:0% capture all the main actors and we 00:14:35.110 --> 00:14:38.070 align:start position:0% capture all the main actors and we forgot<00:14:35.440> something<00:14:35.890> what<00:14:36.240> are<00:14:37.240> you<00:14:37.360> doing<00:14:37.780> in 00:14:38.070 --> 00:14:38.080 align:start position:0% forgot something what are you doing in 00:14:38.080 --> 00:14:40.670 align:start position:0% forgot something what are you doing in the<00:14:38.170> space<00:14:38.290> and<00:14:38.830> what<00:14:39.400> is<00:14:39.580> your<00:14:39.790> role<00:14:40.120> in 00:14:40.670 --> 00:14:40.680 align:start position:0% the space and what is your role in 00:14:40.680 --> 00:15:03.090 align:start position:0% the space and what is your role in mysteries<00:14:41.680> like<00:14:41.860> how<00:14:42.040> to<00:14:42.100> build<00:14:42.990> trust<00:14:43.990> so<00:15:02.100> I 00:15:03.090 --> 00:15:03.100 align:start position:0% mysteries like how to build trust so I 00:15:03.100 --> 00:15:06.900 align:start position:0% mysteries like how to build trust so I am<00:15:04.030> David<00:15:04.300> I<00:15:05.140> have<00:15:05.950> a<00:15:06.010> phone<00:15:06.280> that<00:15:06.310> transnih 00:15:06.900 --> 00:15:06.910 align:start position:0% am David I have a phone that transnih 00:15:06.910 --> 00:15:09.660 align:start position:0% am David I have a phone that transnih Joe<00:15:07.150> s<00:15:07.330> which<00:15:08.170> is<00:15:08.440> the<00:15:08.800> kind<00:15:09.280> of<00:15:09.400> open-source 00:15:09.660 --> 00:15:09.670 align:start position:0% Joe s which is the kind of open-source 00:15:09.670 --> 00:15:13.380 align:start position:0% Joe s which is the kind of open-source version<00:15:10.000> of<00:15:10.390> Android<00:15:10.810> so<00:15:11.770> I<00:15:12.310> use<00:15:12.610> Android 00:15:13.380 --> 00:15:13.390 align:start position:0% version of Android so I use Android 00:15:13.390 --> 00:15:16.440 align:start position:0% version of Android so I use Android applications<00:15:13.990> a<00:15:14.350> lot<00:15:14.530> but<00:15:15.010> I<00:15:15.100> want<00:15:16.060> to<00:15:16.150> use<00:15:16.270> a 00:15:16.440 --> 00:15:16.450 align:start position:0% applications a lot but I want to use a 00:15:16.450 --> 00:15:21.060 align:start position:0% applications a lot but I want to use a whole<00:15:17.020> that<00:15:17.610> crypto<00:15:18.610> wallet<00:15:18.880> and<00:15:19.530> a<00:15:20.530> lot<00:15:20.980> of 00:15:21.060 --> 00:15:21.070 align:start position:0% whole that crypto wallet and a lot of 00:15:21.070 --> 00:15:23.880 align:start position:0% whole that crypto wallet and a lot of times<00:15:21.310> I<00:15:21.670> can't<00:15:22.600> download<00:15:23.020> a<00:15:23.230> free<00:15:23.470> soul<00:15:23.680> that 00:15:23.880 --> 00:15:23.890 align:start position:0% times I can't download a free soul that 00:15:23.890 --> 00:15:27.410 align:start position:0% times I can't download a free soul that they<00:15:24.010> became<00:15:24.900> from<00:15:25.900> anywhere<00:15:26.350> else<00:15:26.500> only<00:15:26.860> from 00:15:27.410 --> 00:15:27.420 align:start position:0% they became from anywhere else only from 00:15:27.420 --> 00:15:31.360 align:start position:0% they became from anywhere else only from pirated<00:15:28.420> from<00:15:28.450> Google<00:15:29.140> Play<00:15:29.350> not<00:15:30.280> very<00:15:30.490> many 00:15:31.360 --> 00:15:31.370 align:start position:0% pirated from Google Play not very many 00:15:31.370 --> 00:15:36.280 align:start position:0% pirated from Google Play not very many publish<00:15:32.030> only<00:15:32.240> on<00:15:32.540> Google<00:15:32.870> Play<00:15:34.660> or<00:15:35.660> if<00:15:35.930> I<00:15:36.080> can 00:15:36.280 --> 00:15:36.290 align:start position:0% publish only on Google Play or if I can 00:15:36.290 --> 00:15:39.370 align:start position:0% publish only on Google Play or if I can get<00:15:36.500> the<00:15:36.650> apk<00:15:37.210> from<00:15:38.210> their<00:15:38.390> github<00:15:38.630> or<00:15:39.170> from 00:15:39.370 --> 00:15:39.380 align:start position:0% get the apk from their github or from 00:15:39.380 --> 00:15:40.000 align:start position:0% get the apk from their github or from someone<00:15:39.680> else 00:15:40.000 --> 00:15:40.010 align:start position:0% someone else 00:15:40.010 --> 00:15:42.850 align:start position:0% someone else the<00:15:40.490> UK<00:15:40.880> is<00:15:41.120> not<00:15:41.300> signed<00:15:41.810> with<00:15:42.080> the<00:15:42.200> duplicate 00:15:42.850 --> 00:15:42.860 align:start position:0% the UK is not signed with the duplicate 00:15:42.860 --> 00:15:45.820 align:start position:0% the UK is not signed with the duplicate they<00:15:43.010> don't<00:15:43.220> even<00:15:43.340> have<00:15:43.670> KGB<00:15:44.510> came<00:15:45.350> for<00:15:45.650> their 00:15:45.820 --> 00:15:45.830 align:start position:0% they don't even have KGB came for their 00:15:45.830 --> 00:15:48.610 align:start position:0% they don't even have KGB came for their releases<00:15:46.190> so<00:15:47.060> I<00:15:47.090> can't<00:15:47.450> really<00:15:47.570> verify<00:15:48.080> its 00:15:48.610 --> 00:15:48.620 align:start position:0% releases so I can't really verify its 00:15:48.620 --> 00:15:51.130 align:start position:0% releases so I can't really verify its really<00:15:48.950> whatever<00:15:49.880> that<00:15:50.270> download<00:15:50.690> is<00:15:50.810> really 00:15:51.130 --> 00:15:51.140 align:start position:0% really whatever that download is really 00:15:51.140 --> 00:15:52.870 align:start position:0% really whatever that download is really what<00:15:51.620> was<00:15:51.770> meant<00:15:51.980> to<00:15:52.040> be<00:15:52.130> installed<00:15:52.610> on<00:15:52.730> my 00:15:52.870 --> 00:15:52.880 align:start position:0% what was meant to be installed on my 00:15:52.880 --> 00:15:57.570 align:start position:0% what was meant to be installed on my phone<00:15:53.150> so<00:15:53.840> like<00:15:54.140> this<00:15:54.680> is<00:15:54.920> my<00:15:55.070> reach<00:15:55.280> out<00:15:55.520> my<00:15:56.410> my 00:15:57.570 --> 00:15:57.580 align:start position:0% phone so like this is my reach out my my 00:15:57.580 --> 00:16:01.930 align:start position:0% phone so like this is my reach out my my cry<00:15:58.580> of<00:15:58.760> cows<00:15:58.970> so<00:15:59.360> please<00:15:59.780> learn<00:16:00.680> a<00:16:00.920> GP<00:16:01.280> make<00:16:01.910> a 00:16:01.930 --> 00:16:01.940 align:start position:0% cry of cows so please learn a GP make a 00:16:01.940 --> 00:16:06.190 align:start position:0% cry of cows so please learn a GP make a PGP<00:16:02.450> signing<00:16:02.810> fee<00:16:03.190> and<00:16:04.600> always<00:16:05.600> sign<00:16:05.990> your 00:16:06.190 --> 00:16:06.200 align:start position:0% PGP signing fee and always sign your 00:16:06.200 --> 00:16:11.020 align:start position:0% PGP signing fee and always sign your releases<00:16:06.560> and<00:16:07.100> close<00:16:08.030> to<00:16:08.180> publish<00:16:08.600> a<00:16:09.760> post<00:16:10.760> of 00:16:11.020 --> 00:16:11.030 align:start position:0% releases and close to publish a post of 00:16:11.030 --> 00:16:13.750 align:start position:0% releases and close to publish a post of publish<00:16:11.270> a<00:16:11.420> pk's<00:16:11.900> on<00:16:12.890> github<00:16:13.340> like<00:16:13.640> this 00:16:13.750 --> 00:16:13.760 align:start position:0% publish a pk's on github like this 00:16:13.760 --> 00:16:17.380 align:start position:0% publish a pk's on github like this website<00:16:14.210> and<00:16:14.540> this<00:16:15.440> place<00:16:15.920> if<00:16:16.310> you<00:16:16.520> can<00:16:17.000> and 00:16:17.380 --> 00:16:17.390 align:start position:0% website and this place if you can and 00:16:17.390 --> 00:16:19.960 align:start position:0% website and this place if you can and have<00:16:18.140> the<00:16:18.410> bandwidth<00:16:18.980> for<00:16:19.220> it 00:16:19.960 --> 00:16:19.970 align:start position:0% have the bandwidth for it 00:16:19.970 --> 00:16:25.210 align:start position:0% have the bandwidth for it publish<00:16:20.810> your<00:16:21.790> application<00:16:22.790> on<00:16:23.180> f-droid<00:16:24.220> such 00:16:25.210 --> 00:16:25.220 align:start position:0% publish your application on f-droid such 00:16:25.220 --> 00:16:27.330 align:start position:0% publish your application on f-droid such as<00:16:25.400> my<00:16:25.520> friend<00:16:25.970> leaky<00:16:26.240> does<00:16:26.450> with<00:16:26.870> his<00:16:27.050> wallet 00:16:27.330 --> 00:16:27.340 align:start position:0% as my friend leaky does with his wallet 00:16:27.340 --> 00:16:32.800 align:start position:0% as my friend leaky does with his wallet police<00:16:29.380> because<00:16:30.380> like<00:16:31.070> when<00:16:31.730> I'm<00:16:32.210> thinking<00:16:32.480> of 00:16:32.800 --> 00:16:32.810 align:start position:0% police because like when I'm thinking of 00:16:32.810 --> 00:16:35.620 align:start position:0% police because like when I'm thinking of how<00:16:33.200> to<00:16:33.260> make<00:16:33.530> this<00:16:33.910> persistent<00:16:34.910> trustless<00:16:35.330> I 00:16:35.620 --> 00:16:35.630 align:start position:0% how to make this persistent trustless I 00:16:35.630 --> 00:16:40.270 align:start position:0% how to make this persistent trustless I believe<00:16:36.500> that<00:16:36.740> is<00:16:36.950> a<00:16:38.080> crucial<00:16:39.080> point<00:16:39.560> of<00:16:39.830> trust 00:16:40.270 --> 00:16:40.280 align:start position:0% believe that is a crucial point of trust 00:16:40.280 --> 00:16:42.370 align:start position:0% believe that is a crucial point of trust you<00:16:40.580> know<00:16:40.730> the<00:16:41.090> applications<00:16:41.870> that<00:16:41.960> you<00:16:42.200> put 00:16:42.370 --> 00:16:42.380 align:start position:0% you know the applications that you put 00:16:42.380 --> 00:16:44.940 align:start position:0% you know the applications that you put in<00:16:42.530> your<00:16:42.700> your<00:16:43.700> devices 00:16:44.940 --> 00:16:44.950 align:start position:0% in your your devices 00:16:44.950 --> 00:16:48.509 align:start position:0% in your your devices so<00:16:45.329> yeah<00:16:46.329> that's<00:16:46.990> what<00:16:47.110> I<00:16:47.230> wanted<00:16:47.470> to<00:16:47.560> say<00:16:48.339> and 00:16:48.509 --> 00:16:48.519 align:start position:0% so yeah that's what I wanted to say and 00:16:48.519 --> 00:16:56.690 align:start position:0% so yeah that's what I wanted to say and thank<00:16:49.029> you<00:16:49.089> for<00:16:49.240> attention 00:16:56.690 --> 00:16:56.700 align:start position:0% 00:16:56.700 --> 00:17:03.389 align:start position:0% like<00:16:57.700> many<00:16:58.300> more<00:17:00.959> everything<00:17:02.010> all<00:17:03.010> that<00:17:03.070> like 00:17:03.389 --> 00:17:03.399 align:start position:0% like many more everything all that like 00:17:03.399 --> 00:17:06.260 align:start position:0% like many more everything all that like all<00:17:03.579> the<00:17:03.670> software<00:17:04.089> that<00:17:04.179> enable<00:17:04.630> enables 00:17:06.260 --> 00:17:06.270 align:start position:0% all the software that enable enables 00:17:06.270 --> 00:17:08.520 align:start position:0% all the software that enable enables this<00:17:07.270> to<00:17:07.329> work<00:17:07.689> I<00:17:07.839> mean<00:17:07.990> many<00:17:08.140> things<00:17:08.380> are 00:17:08.520 --> 00:17:08.530 align:start position:0% this to work I mean many things are 00:17:08.530 --> 00:17:10.230 align:start position:0% this to work I mean many things are published<00:17:09.069> in<00:17:09.130> certain<00:17:09.520> to<00:17:09.760> the<00:17:09.880> app<00:17:10.000> stores 00:17:10.230 --> 00:17:10.240 align:start position:0% published in certain to the app stores 00:17:10.240 --> 00:17:11.730 align:start position:0% published in certain to the app stores but<00:17:10.449> of<00:17:10.569> course<00:17:10.780> ultimately<00:17:10.959> github<00:17:11.439> we<00:17:11.589> have 00:17:11.730 --> 00:17:11.740 align:start position:0% but of course ultimately github we have 00:17:11.740 --> 00:17:13.380 align:start position:0% but of course ultimately github we have a<00:17:11.799> lot<00:17:11.919> of<00:17:11.949> things<00:17:12.280> and<00:17:12.610> the<00:17:12.939> addition<00:17:13.299> of 00:17:13.380 --> 00:17:13.390 align:start position:0% a lot of things and the addition of 00:17:13.390 --> 00:17:16.740 align:start position:0% a lot of things and the addition of course<00:17:13.630> always<00:17:14.049> be<00:17:14.679> annually<00:17:15.520> signed<00:17:15.850> and<00:17:16.569> the 00:17:16.740 --> 00:17:16.750 align:start position:0% course always be annually signed and the 00:17:16.750 --> 00:17:19.289 align:start position:0% course always be annually signed and the keys<00:17:16.990> should<00:17:17.230> be<00:17:17.319> known<00:17:17.640> the<00:17:18.640> team<00:17:18.850> of<00:17:19.179> people 00:17:19.289 --> 00:17:19.299 align:start position:0% keys should be known the team of people 00:17:19.299 --> 00:17:21.569 align:start position:0% keys should be known the team of people that<00:17:19.620> publishes<00:17:20.620> so<00:17:20.770> that<00:17:20.890> they<00:17:21.069> can<00:17:21.250> actually 00:17:21.569 --> 00:17:21.579 align:start position:0% that publishes so that they can actually 00:17:21.579 --> 00:17:25.470 align:start position:0% that publishes so that they can actually verify<00:17:22.079> that<00:17:23.079> what<00:17:23.860> we<00:17:23.949> use<00:17:24.130> is<00:17:24.429> coming<00:17:25.329> from 00:17:25.470 --> 00:17:25.480 align:start position:0% verify that what we use is coming from 00:17:25.480 --> 00:17:30.930 align:start position:0% verify that what we use is coming from the<00:17:25.660> right<00:17:25.809> sources<00:17:26.140> and<00:17:26.439> this<00:17:27.030> working<00:17:29.940> just 00:17:30.930 --> 00:17:30.940 align:start position:0% the right sources and this working just 00:17:30.940 --> 00:17:32.370 align:start position:0% the right sources and this working just the<00:17:31.000> thing<00:17:31.179> I<00:17:31.270> think<00:17:31.330> that<00:17:31.630> basically<00:17:31.929> we 00:17:32.370 --> 00:17:32.380 align:start position:0% the thing I think that basically we 00:17:32.380 --> 00:17:34.260 align:start position:0% the thing I think that basically we cannot<00:17:33.100> do<00:17:33.250> this<00:17:33.429> with<00:17:33.580> a<00:17:33.610> microphone<00:17:34.090> because 00:17:34.260 --> 00:17:34.270 align:start position:0% cannot do this with a microphone because 00:17:34.270 --> 00:17:36.150 align:start position:0% cannot do this with a microphone because this<00:17:34.720> is<00:17:34.900> gonna<00:17:35.110> be<00:17:35.260> crazy<00:17:35.470> should<00:17:35.860> be<00:17:35.980> just 00:17:36.150 --> 00:17:36.160 align:start position:0% this is gonna be crazy should be just 00:17:36.160 --> 00:17:45.180 align:start position:0% this is gonna be crazy should be just like<00:17:36.250> start<00:17:37.030> I<00:17:41.160> think<00:17:42.160> the<00:17:42.820> single<00:17:44.190> most 00:17:45.180 --> 00:17:45.190 align:start position:0% like start I think the single most 00:17:45.190 --> 00:17:48.960 align:start position:0% like start I think the single most effective<00:17:45.460> thing<00:17:46.210> we<00:17:46.660> could<00:17:46.900> do<00:17:47.110> is<00:17:47.970> the 00:17:48.960 --> 00:17:48.970 align:start position:0% effective thing we could do is the 00:17:48.970 --> 00:17:53.440 align:start position:0% effective thing we could do is the compiler<00:17:50.370> publishing<00:17:51.370> the<00:17:51.520> source<00:17:51.790> codes 00:17:53.440 --> 00:17:53.450 align:start position:0% compiler publishing the source codes 00:17:53.450 --> 00:17:54.830 align:start position:0% compiler publishing the source codes [Music] 00:17:54.830 --> 00:17:54.840 align:start position:0% [Music] 00:17:54.840 --> 00:17:57.000 align:start position:0% [Music] what's<00:17:55.840> the<00:17:55.960> name<00:17:56.140> of<00:17:56.169> that<00:17:56.290> thing<00:17:56.740> you<00:17:56.919> were 00:17:57.000 --> 00:17:57.010 align:start position:0% what's the name of that thing you were 00:17:57.010 --> 00:17:59.730 align:start position:0% what's the name of that thing you were telling<00:17:57.160> me<00:17:57.280> about<00:17:57.340> the<00:17:57.700> swarm<00:17:58.299> hash<00:17:58.660> weed<00:17:59.410> and 00:17:59.730 --> 00:17:59.740 align:start position:0% telling me about the swarm hash weed and 00:17:59.740 --> 00:18:02.370 align:start position:0% telling me about the swarm hash weed and then<00:17:59.830> actually<00:18:00.520> publishing<00:18:01.150> the<00:18:01.299> source<00:18:01.570> to 00:18:02.370 --> 00:18:02.380 align:start position:0% then actually publishing the source to 00:18:02.380 --> 00:18:05.760 align:start position:0% then actually publishing the source to swim<00:18:02.910> without<00:18:03.910> as<00:18:04.870> a<00:18:04.929> default 00:18:05.760 --> 00:18:05.770 align:start position:0% swim without as a default 00:18:05.770 --> 00:18:07.530 align:start position:0% swim without as a default I<00:18:05.860> think<00:18:06.190> if<00:18:06.280> we've<00:18:06.429> made<00:18:06.640> that<00:18:06.910> the<00:18:07.120> default 00:18:07.530 --> 00:18:07.540 align:start position:0% I think if we've made that the default 00:18:07.540 --> 00:18:10.810 align:start position:0% I think if we've made that the default then<00:18:09.660> 99% 00:18:10.810 --> 00:18:10.820 align:start position:0% then 99% 00:18:10.820 --> 00:18:12.279 align:start position:0% then 99% these<00:18:10.940> pieces<00:18:11.419> of<00:18:11.630> source<00:18:11.870> code<00:18:12.110> will<00:18:12.259> be 00:18:12.279 --> 00:18:12.289 align:start position:0% these pieces of source code will be 00:18:12.289 --> 00:18:15.129 align:start position:0% these pieces of source code will be available<00:18:12.409> because<00:18:13.279> I'm<00:18:13.720> people<00:18:14.720> wouldn't 00:18:15.129 --> 00:18:15.139 align:start position:0% available because I'm people wouldn't 00:18:15.139 --> 00:18:18.009 align:start position:0% available because I'm people wouldn't turn<00:18:15.380> it<00:18:15.590> off<00:18:15.769> and<00:18:16.220> it<00:18:16.970> would<00:18:17.029> also<00:18:17.210> promote<00:18:17.659> an 00:18:18.009 --> 00:18:18.019 align:start position:0% turn it off and it would also promote an 00:18:18.019 --> 00:18:20.379 align:start position:0% turn it off and it would also promote an idea<00:18:18.470> that<00:18:18.919> we<00:18:19.100> should<00:18:19.370> all<00:18:19.580> be<00:18:19.759> publishing 00:18:20.379 --> 00:18:20.389 align:start position:0% idea that we should all be publishing 00:18:20.389 --> 00:18:22.269 align:start position:0% idea that we should all be publishing all<00:18:20.630> of<00:18:20.809> our<00:18:20.990> source<00:18:21.259> code<00:18:21.350> and<00:18:21.860> we<00:18:21.950> should<00:18:22.130> all 00:18:22.269 --> 00:18:22.279 align:start position:0% all of our source code and we should all 00:18:22.279 --> 00:18:24.310 align:start position:0% all of our source code and we should all be<00:18:22.460> interacting<00:18:23.269> with<00:18:23.299> smart<00:18:23.690> contracts<00:18:24.200> that 00:18:24.310 --> 00:18:24.320 align:start position:0% be interacting with smart contracts that 00:18:24.320 --> 00:18:26.889 align:start position:0% be interacting with smart contracts that have<00:18:24.380> published<00:18:25.070> source<00:18:25.370> code<00:18:25.669> so<00:18:26.509> we<00:18:26.659> make 00:18:26.889 --> 00:18:26.899 align:start position:0% have published source code so we make 00:18:26.899 --> 00:18:29.860 align:start position:0% have published source code so we make the<00:18:27.139> community<00:18:27.799> ethos<00:18:28.429> that<00:18:29.360> the<00:18:29.570> code<00:18:29.840> is 00:18:29.860 --> 00:18:29.870 align:start position:0% the community ethos that the code is 00:18:29.870 --> 00:18:32.350 align:start position:0% the community ethos that the code is there<00:18:30.409> and<00:18:30.740> if<00:18:31.250> somebody<00:18:31.549> wants<00:18:31.820> to<00:18:31.880> turn<00:18:32.210> it 00:18:32.350 --> 00:18:32.360 align:start position:0% there and if somebody wants to turn it 00:18:32.360 --> 00:18:34.269 align:start position:0% there and if somebody wants to turn it off<00:18:32.509> then<00:18:32.899> I<00:18:33.200> would<00:18:33.529> look<00:18:33.649> at<00:18:33.830> them<00:18:33.980> and<00:18:34.100> say 00:18:34.269 --> 00:18:34.279 align:start position:0% off then I would look at them and say 00:18:34.279 --> 00:18:36.820 align:start position:0% off then I would look at them and say why<00:18:34.490> did<00:18:34.700> you<00:18:34.730> turn<00:18:35.090> it<00:18:35.210> off<00:18:35.590> but<00:18:36.590> I<00:18:36.620> think 00:18:36.820 --> 00:18:36.830 align:start position:0% why did you turn it off but I think 00:18:36.830 --> 00:18:38.620 align:start position:0% why did you turn it off but I think that's<00:18:37.009> the<00:18:37.220> most<00:18:37.399> effective<00:18:37.820> by<00:18:38.120> far<00:18:38.419> I<00:18:38.450> think 00:18:38.620 --> 00:18:38.630 align:start position:0% that's the most effective by far I think 00:18:38.630 --> 00:18:41.049 align:start position:0% that's the most effective by far I think trying<00:18:38.960> to<00:18:39.049> get<00:18:39.200> people<00:18:39.529> to<00:18:39.559> volunteer<00:18:40.190> you're 00:18:41.049 --> 00:18:41.059 align:start position:0% trying to get people to volunteer you're 00:18:41.059 --> 00:18:44.490 align:start position:0% trying to get people to volunteer you're gonna<00:18:41.179> end<00:18:41.419> up<00:18:41.620> four<00:18:42.620> years<00:18:42.860> from<00:18:43.159> now<00:18:43.309> with 00:18:44.490 --> 00:18:44.500 align:start position:0% gonna end up four years from now with 00:18:44.500 --> 00:18:48.190 align:start position:0% gonna end up four years from now with 3,200<00:18:45.500> published<00:18:46.370> smart<00:18:46.909> contract<00:18:47.450> so 00:18:48.190 --> 00:18:48.200 align:start position:0% 3,200 published smart contract so 00:18:48.200 --> 00:18:52.330 align:start position:0% 3,200 published smart contract so priests<00:18:48.649> work<00:18:48.889> so<00:18:49.929> Chris<00:18:50.929> no<00:18:51.139> why<00:18:51.470> is<00:18:51.889> this<00:18:52.100> not 00:18:52.330 --> 00:18:52.340 align:start position:0% priests work so Chris no why is this not 00:18:52.340 --> 00:18:57.129 align:start position:0% priests work so Chris no why is this not a<00:18:52.370> people<00:18:52.879> what<00:18:53.539> are<00:18:53.690> the<00:18:53.720> obstacles<00:18:54.139> I<00:18:56.139> think 00:18:57.129 --> 00:18:57.139 align:start position:0% a people what are the obstacles I think 00:18:57.139 --> 00:18:59.549 align:start position:0% a people what are the obstacles I think the<00:18:57.289> compiler<00:18:58.070> is<00:18:58.370> unfortunate<00:18:59.029> the<00:18:59.059> right 00:18:59.549 --> 00:18:59.559 align:start position:0% the compiler is unfortunate the right 00:18:59.559 --> 00:19:02.919 align:start position:0% the compiler is unfortunate the right tool<00:19:00.559> to<00:19:00.740> do<00:19:01.100> this<00:19:01.399> and<00:19:01.700> the<00:19:02.149> main<00:19:02.360> reason<00:19:02.779> is 00:19:02.919 --> 00:19:02.929 align:start position:0% tool to do this and the main reason is 00:19:02.929 --> 00:19:06.009 align:start position:0% tool to do this and the main reason is first<00:19:03.860> you<00:19:04.610> do<00:19:04.789> not<00:19:04.909> know<00:19:05.149> whether<00:19:05.450> the<00:19:05.750> source 00:19:06.009 --> 00:19:06.019 align:start position:0% first you do not know whether the source 00:19:06.019 --> 00:19:07.930 align:start position:0% first you do not know whether the source code<00:19:06.289> that<00:19:06.320> is<00:19:06.620> currently<00:19:06.950> being<00:19:07.009> compiled<00:19:07.639> is 00:19:07.930 --> 00:19:07.940 align:start position:0% code that is currently being compiled is 00:19:07.940 --> 00:19:09.310 align:start position:0% code that is currently being compiled is the<00:19:08.120> final<00:19:08.480> thing<00:19:08.629> that<00:19:08.659> will<00:19:08.870> be<00:19:08.929> published 00:19:09.310 --> 00:19:09.320 align:start position:0% the final thing that will be published 00:19:09.320 --> 00:19:11.440 align:start position:0% the final thing that will be published or<00:19:09.470> some<00:19:10.309> random<00:19:10.580> people<00:19:10.700> are<00:19:10.909> just<00:19:11.059> testing 00:19:11.440 --> 00:19:11.450 align:start position:0% or some random people are just testing 00:19:11.450 --> 00:19:16.029 align:start position:0% or some random people are just testing some<00:19:11.629> stuff<00:19:11.840> and<00:19:12.370> second<00:19:14.110> the<00:19:15.110> compiler<00:19:15.470> may 00:19:16.029 --> 00:19:16.039 align:start position:0% some stuff and second the compiler may 00:19:16.039 --> 00:19:18.129 align:start position:0% some stuff and second the compiler may not<00:19:16.220> even<00:19:16.340> have<00:19:16.669> access<00:19:16.940> to<00:19:17.419> the<00:19:17.509> network<00:19:17.690> and 00:19:18.129 --> 00:19:18.139 align:start position:0% not even have access to the network and 00:19:18.139 --> 00:19:21.789 align:start position:0% not even have access to the network and the<00:19:19.100> results<00:19:19.549> might<00:19:19.759> be<00:19:20.440> the<00:19:21.440> compiler<00:19:21.740> is 00:19:21.789 --> 00:19:21.799 align:start position:0% the results might be the compiler is 00:19:21.799 --> 00:19:22.960 align:start position:0% the results might be the compiler is used<00:19:21.980> to<00:19:22.100> generate<00:19:22.220> bytecode<00:19:22.730> and<00:19:22.759> the 00:19:22.960 --> 00:19:22.970 align:start position:0% used to generate bytecode and the 00:19:22.970 --> 00:19:24.759 align:start position:0% used to generate bytecode and the bytecode<00:19:23.179> is<00:19:23.419> moved<00:19:23.990> somewhere<00:19:24.379> else<00:19:24.440> and 00:19:24.759 --> 00:19:24.769 align:start position:0% bytecode is moved somewhere else and 00:19:24.769 --> 00:19:27.159 align:start position:0% bytecode is moved somewhere else and then<00:19:24.889> published<00:19:25.340> is<00:19:25.519> okay<00:19:25.879> so<00:19:26.059> I<00:19:26.299> think<00:19:26.360> the 00:19:27.159 --> 00:19:27.169 align:start position:0% then published is okay so I think the 00:19:27.169 --> 00:19:29.379 align:start position:0% then published is okay so I think the tools<00:19:27.409> that<00:19:27.710> do<00:19:28.039> the<00:19:28.399> small<00:19:29.090> current 00:19:29.379 --> 00:19:29.389 align:start position:0% tools that do the small current 00:19:29.389 --> 00:19:32.230 align:start position:0% tools that do the small current deployment<00:19:29.659> should<00:19:30.019> do<00:19:30.169> that<00:19:30.350> I<00:19:30.789> think<00:19:31.789> it 00:19:32.230 --> 00:19:32.240 align:start position:0% deployment should do that I think it 00:19:32.240 --> 00:19:33.940 align:start position:0% deployment should do that I think it should<00:19:32.269> be<00:19:32.450> the<00:19:32.629> default<00:19:32.779> yes 00:19:33.940 --> 00:19:33.950 align:start position:0% should be the default yes 00:19:33.950 --> 00:19:36.460 align:start position:0% should be the default yes is<00:19:34.429> there<00:19:34.610> any<00:19:34.730> efforts<00:19:35.389> to<00:19:35.539> communicate<00:19:36.259> that 00:19:36.460 --> 00:19:36.470 align:start position:0% is there any efforts to communicate that 00:19:36.470 --> 00:19:38.080 align:start position:0% is there any efforts to communicate that to<00:19:36.529> the<00:19:36.860> people<00:19:37.190> that<00:19:37.279> are<00:19:37.429> writing<00:19:37.610> that<00:19:37.820> code 00:19:38.080 --> 00:19:38.090 align:start position:0% to the people that are writing that code 00:19:38.090 --> 00:19:42.749 align:start position:0% to the people that are writing that code I'm<00:19:38.299> talking<00:19:38.870> to<00:19:38.990> them<00:19:39.169> yes 00:19:42.749 --> 00:19:42.759 align:start position:0% 00:19:42.759 --> 00:20:17.009 align:start position:0% I<00:20:02.940> think<00:20:14.519> the<00:20:15.519> deployed<00:20:15.940> bytecode<00:20:16.389> of<00:20:16.539> every 00:20:17.009 --> 00:20:17.019 align:start position:0% I think the deployed bytecode of every 00:20:17.019 --> 00:20:21.419 align:start position:0% I think the deployed bytecode of every smart<00:20:17.289> contract<00:20:17.769> has<00:20:18.009> a<00:20:18.599> hash<00:20:19.599> of<00:20:19.989> a<00:20:20.409> JSON<00:20:21.159> file 00:20:21.419 --> 00:20:21.429 align:start position:0% smart contract has a hash of a JSON file 00:20:21.429 --> 00:20:25.699 align:start position:0% smart contract has a hash of a JSON file at<00:20:21.639> the<00:20:21.759> end<00:20:21.789> and<00:20:23.219> this<00:20:24.219> JSON<00:20:24.519> file<00:20:24.909> contains 00:20:25.699 --> 00:20:25.709 align:start position:0% at the end and this JSON file contains 00:20:25.709 --> 00:20:29.069 align:start position:0% at the end and this JSON file contains information<00:20:26.709> like<00:20:27.190> here<00:20:27.699> the<00:20:27.909> ABI<00:20:28.209> the 00:20:29.069 --> 00:20:29.079 align:start position:0% information like here the ABI the 00:20:29.079 --> 00:20:31.919 align:start position:0% information like here the ABI the compiler<00:20:29.469> that<00:20:29.529> was<00:20:29.769> used<00:20:29.979> to<00:20:30.489> to<00:20:31.449> compile<00:20:31.809> the 00:20:31.919 --> 00:20:31.929 align:start position:0% compiler that was used to to compile the 00:20:31.929 --> 00:20:35.699 align:start position:0% compiler that was used to to compile the source<00:20:32.109> code<00:20:32.379> and<00:20:32.589> also<00:20:33.869> yeah<00:20:34.869> link<00:20:35.229> hashes<00:20:35.679> to 00:20:35.699 --> 00:20:35.709 align:start position:0% source code and also yeah link hashes to 00:20:35.709 --> 00:20:38.459 align:start position:0% source code and also yeah link hashes to the<00:20:36.039> source<00:20:36.279> code<00:20:36.519> so<00:20:36.819> the<00:20:37.509> the<00:20:37.809> integrity<00:20:38.349> of 00:20:38.459 --> 00:20:38.469 align:start position:0% the source code so the the integrity of 00:20:38.469 --> 00:20:41.369 align:start position:0% the source code so the the integrity of all<00:20:38.769> this<00:20:39.059> is<00:20:40.059> not<00:20:40.359> the<00:20:40.509> problem<00:20:40.749> the<00:20:41.079> product 00:20:41.369 --> 00:20:41.379 align:start position:0% all this is not the problem the product 00:20:41.379 --> 00:20:44.819 align:start position:0% all this is not the problem the product is<00:20:41.469> the<00:20:41.589> data<00:20:41.769> availability<00:20:42.219> here<00:20:42.609> and<00:20:43.829> I 00:20:44.819 --> 00:20:44.829 align:start position:0% is the data availability here and I 00:20:44.829 --> 00:20:49.139 align:start position:0% is the data availability here and I think<00:20:45.069> if<00:20:45.279> if<00:20:45.699> we<00:20:47.519> could<00:20:48.519> get<00:20:48.759> to<00:20:48.879> a<00:20:48.909> point 00:20:49.139 --> 00:20:49.149 align:start position:0% think if if we could get to a point 00:20:49.149 --> 00:20:50.759 align:start position:0% think if if we could get to a point where<00:20:49.449> people<00:20:49.779> publish<00:20:50.079> that<00:20:50.199> information<00:20:50.679> at 00:20:50.759 --> 00:20:50.769 align:start position:0% where people publish that information at 00:20:50.769 --> 00:20:53.039 align:start position:0% where people publish that information at the<00:20:50.889> point<00:20:50.919> of<00:20:51.190> deployment<00:20:51.789> then<00:20:52.299> also<00:20:52.779> the 00:20:53.039 --> 00:20:53.049 align:start position:0% the point of deployment then also the 00:20:53.049 --> 00:20:55.199 align:start position:0% the point of deployment then also the user<00:20:53.469> experience<00:20:53.919> of<00:20:54.279> wallets<00:20:54.669> for<00:20:54.789> example 00:20:55.199 --> 00:20:55.209 align:start position:0% user experience of wallets for example 00:20:55.209 --> 00:20:56.879 align:start position:0% user experience of wallets for example would<00:20:55.299> greatly<00:20:55.659> improves<00:20:56.109> not<00:20:56.319> only<00:20:56.529> because 00:20:56.879 --> 00:20:56.889 align:start position:0% would greatly improves not only because 00:20:56.889 --> 00:20:58.889 align:start position:0% would greatly improves not only because you<00:20:57.159> have<00:20:57.579> access<00:20:57.849> to<00:20:57.879> the<00:20:58.029> source<00:20:58.209> code<00:20:58.329> but 00:20:58.889 --> 00:20:58.899 align:start position:0% you have access to the source code but 00:20:58.899 --> 00:21:00.839 align:start position:0% you have access to the source code but only<00:20:59.109> because<00:20:59.469> you<00:20:59.979> have<00:21:00.009> access<00:21:00.309> so<00:21:00.699> this 00:21:00.839 --> 00:21:00.849 align:start position:0% only because you have access so this 00:21:00.849 --> 00:21:04.489 align:start position:0% only because you have access so this this<00:21:01.659> JSON<00:21:01.899> file<00:21:02.229> contains<00:21:02.679> an<00:21:03.579> interpreted 00:21:04.489 --> 00:21:04.499 align:start position:0% this JSON file contains an interpreted 00:21:04.499 --> 00:21:08.869 align:start position:0% this JSON file contains an interpreted ABI<00:21:05.499> and<00:21:06.059> also<00:21:07.059> the<00:21:07.239> nut<00:21:07.899> spec<00:21:08.169> comments<00:21:08.589> of 00:21:08.869 --> 00:21:08.879 align:start position:0% ABI and also the nut spec comments of 00:21:08.879 --> 00:21:12.559 align:start position:0% ABI and also the nut spec comments of the<00:21:09.879> functions<00:21:10.329> so<00:21:10.809> whenever<00:21:10.989> you<00:21:11.409> have<00:21:11.859> a 00:21:12.559 --> 00:21:12.569 align:start position:0% the functions so whenever you have a 00:21:12.569 --> 00:21:15.569 align:start position:0% the functions so whenever you have a whenever<00:21:13.569> your<00:21:13.839> wallet<00:21:14.139> asks<00:21:14.679> you<00:21:14.889> to<00:21:15.339> confirm 00:21:15.569 --> 00:21:15.579 align:start position:0% whenever your wallet asks you to confirm 00:21:15.579 --> 00:21:18.589 align:start position:0% whenever your wallet asks you to confirm a<00:21:15.789> transaction<00:21:16.419> it<00:21:17.109> should<00:21:17.349> not<00:21:17.559> display<00:21:17.979> this 00:21:18.589 --> 00:21:18.599 align:start position:0% a transaction it should not display this 00:21:18.599 --> 00:21:22.139 align:start position:0% a transaction it should not display this garble<00:21:19.599> hex<00:21:19.779> string<00:21:19.869> of<00:21:20.289> data<00:21:20.909> it<00:21:21.909> should 00:21:22.139 --> 00:21:22.149 align:start position:0% garble hex string of data it should 00:21:22.149 --> 00:21:24.839 align:start position:0% garble hex string of data it should actually<00:21:22.809> fully<00:21:23.319> decode<00:21:23.889> all<00:21:24.309> the<00:21:24.519> function 00:21:24.839 --> 00:21:24.849 align:start position:0% actually fully decode all the function 00:21:24.849 --> 00:21:27.930 align:start position:0% actually fully decode all the function parameters<00:21:24.969> and<00:21:25.569> display<00:21:26.549> the<00:21:27.549> nut<00:21:27.699> spec 00:21:27.930 --> 00:21:27.940 align:start position:0% parameters and display the nut spec 00:21:27.940 --> 00:21:29.639 align:start position:0% parameters and display the nut spec comment<00:21:28.299> that<00:21:28.479> is<00:21:28.659> associated<00:21:29.049> with<00:21:29.409> this 00:21:29.639 --> 00:21:29.649 align:start position:0% comment that is associated with this 00:21:29.649 --> 00:21:32.870 align:start position:0% comment that is associated with this function<00:21:30.749> I<00:21:31.749> mean 00:21:32.870 --> 00:21:32.880 align:start position:0% function I mean 00:21:32.880 --> 00:21:35.240 align:start position:0% function I mean they<00:21:33.630> for<00:21:33.930> example<00:21:34.020> wallets<00:21:34.650> they<00:21:34.890> couldn't 00:21:35.240 --> 00:21:35.250 align:start position:0% they for example wallets they couldn't 00:21:35.250 --> 00:21:37.040 align:start position:0% they for example wallets they couldn't display<00:21:35.820> like<00:21:36.120> if<00:21:36.270> the<00:21:36.390> data<00:21:36.570> was<00:21:36.840> available 00:21:37.040 --> 00:21:37.050 align:start position:0% display like if the data was available 00:21:37.050 --> 00:21:41.300 align:start position:0% display like if the data was available so<00:21:37.410> if<00:21:37.800> tools<00:21:38.520> only<00:21:39.320> if<00:21:40.320> we<00:21:40.770> generally<00:21:41.220> like 00:21:41.300 --> 00:21:41.310 align:start position:0% so if tools only if we generally like 00:21:41.310 --> 00:21:43.400 align:start position:0% so if tools only if we generally like establish<00:21:41.880> this<00:21:42.030> as<00:21:42.180> a<00:21:42.210> like<00:21:42.450> a<00:21:42.600> mind<00:21:43.110> said 00:21:43.400 --> 00:21:43.410 align:start position:0% establish this as a like a mind said 00:21:43.410 --> 00:21:45.140 align:start position:0% establish this as a like a mind said that<00:21:43.560> it<00:21:43.650> would<00:21:43.770> be<00:21:43.800> better<00:21:44.070> for<00:21:44.430> everyone<00:21:44.730> if 00:21:45.140 --> 00:21:45.150 align:start position:0% that it would be better for everyone if 00:21:45.150 --> 00:21:47.510 align:start position:0% that it would be better for everyone if we<00:21:45.750> had<00:21:46.050> this<00:21:46.260> horse<00:21:46.500> tool<00:21:46.770> because<00:21:47.160> the 00:21:47.510 --> 00:21:47.520 align:start position:0% we had this horse tool because the 00:21:47.520 --> 00:21:49.610 align:start position:0% we had this horse tool because the theory<00:21:47.760> was<00:21:47.970> meant<00:21:48.150> to<00:21:48.180> be<00:21:48.300> trustless<00:21:48.750> that's 00:21:49.610 --> 00:21:49.620 align:start position:0% theory was meant to be trustless that's 00:21:49.620 --> 00:21:51.140 align:start position:0% theory was meant to be trustless that's kind<00:21:49.770> of<00:21:49.830> a<00:21:49.890> missing<00:21:50.220> link<00:21:50.370> and<00:21:50.610> if<00:21:50.820> we<00:21:51.000> don't 00:21:51.140 --> 00:21:51.150 align:start position:0% kind of a missing link and if we don't 00:21:51.150 --> 00:21:53.420 align:start position:0% kind of a missing link and if we don't do<00:21:51.300> that<00:21:51.510> and<00:21:51.690> why<00:21:51.870> we<00:21:52.290> do<00:21:52.830> all<00:21:53.010> this<00:21:53.190> in<00:21:53.340> the 00:21:53.420 --> 00:21:53.430 align:start position:0% do that and why we do all this in the 00:21:53.430 --> 00:21:55.640 align:start position:0% do that and why we do all this in the first<00:21:53.460> place<00:21:53.760> then<00:21:54.690> I<00:21:54.780> can<00:21:54.960> also<00:21:55.080> just<00:21:55.170> go<00:21:55.470> back 00:21:55.640 --> 00:21:55.650 align:start position:0% first place then I can also just go back 00:21:55.650 --> 00:21:59.330 align:start position:0% first place then I can also just go back to<00:21:55.830> how<00:21:56.340> things<00:21:56.370> always<00:21:56.790> work<00:21:57.800> but<00:21:58.800> ok<00:21:59.010> so<00:21:59.070> if 00:21:59.330 --> 00:21:59.340 align:start position:0% to how things always work but ok so if 00:21:59.340 --> 00:22:01.700 align:start position:0% to how things always work but ok so if we<00:21:59.520> if<00:21:59.730> we<00:21:59.760> have<00:22:00.120> that<00:22:00.330> and<00:22:00.570> we<00:22:00.810> maybe<00:22:01.320> have<00:22:01.590> the 00:22:01.700 --> 00:22:01.710 align:start position:0% we if we have that and we maybe have the 00:22:01.710 --> 00:22:03.140 align:start position:0% we if we have that and we maybe have the tools<00:22:01.980> publishing<00:22:02.370> business<00:22:02.610> we<00:22:02.730> are<00:22:02.760> getting 00:22:03.140 --> 00:22:03.150 align:start position:0% tools publishing business we are getting 00:22:03.150 --> 00:22:05.120 align:start position:0% tools publishing business we are getting more<00:22:03.270> source<00:22:03.540> code<00:22:03.750> and<00:22:04.260> this<00:22:04.410> is<00:22:04.560> also<00:22:04.770> pretty 00:22:05.120 --> 00:22:05.130 align:start position:0% more source code and this is also pretty 00:22:05.130 --> 00:22:07.220 align:start position:0% more source code and this is also pretty cool<00:22:05.430> because<00:22:05.610> then<00:22:05.910> wallets<00:22:06.600> could<00:22:07.110> of 00:22:07.220 --> 00:22:07.230 align:start position:0% cool because then wallets could of 00:22:07.230 --> 00:22:10.280 align:start position:0% cool because then wallets could of course<00:22:07.440> display<00:22:08.010> a<00:22:08.280> certain<00:22:09.030> transaction<00:22:09.720> is 00:22:10.280 --> 00:22:10.290 align:start position:0% course display a certain transaction is 00:22:10.290 --> 00:22:12.620 align:start position:0% course display a certain transaction is happening<00:22:10.800> with<00:22:11.250> like<00:22:11.460> a<00:22:11.490> contract<00:22:12.180> where<00:22:12.420> at 00:22:12.620 --> 00:22:12.630 align:start position:0% happening with like a contract where at 00:22:12.630 --> 00:22:15.980 align:start position:0% happening with like a contract where at least<00:22:12.990> the<00:22:13.410> source<00:22:13.620> code<00:22:13.830> is<00:22:13.920> known<00:22:14.810> but<00:22:15.810> then 00:22:15.980 --> 00:22:15.990 align:start position:0% least the source code is known but then 00:22:15.990 --> 00:22:19.760 align:start position:0% least the source code is known but then I<00:22:16.170> clearly<00:22:16.530> also<00:22:16.790> any<00:22:17.790> like<00:22:18.450> auditor<00:22:19.290> or<00:22:19.560> said 00:22:19.760 --> 00:22:19.770 align:start position:0% I clearly also any like auditor or said 00:22:19.770 --> 00:22:22.810 align:start position:0% I clearly also any like auditor or said any<00:22:20.040> any<00:22:20.520> security<00:22:21.060> related<00:22:21.330> project<00:22:21.870> could 00:22:22.810 --> 00:22:22.820 align:start position:0% any any security related project could 00:22:22.820 --> 00:22:25.220 align:start position:0% any any security related project could could<00:22:23.820> analyze<00:22:24.120> the<00:22:24.510> source<00:22:24.750> code<00:22:24.990> easier 00:22:25.220 --> 00:22:25.230 align:start position:0% could analyze the source code easier 00:22:25.230 --> 00:22:26.750 align:start position:0% could analyze the source code easier because<00:22:25.500> there's<00:22:25.800> many<00:22:25.980> of<00:22:26.130> innovative<00:22:26.580> or 00:22:26.750 --> 00:22:26.760 align:start position:0% because there's many of innovative or 00:22:26.760 --> 00:22:29.530 align:start position:0% because there's many of innovative or even<00:22:27.090> published<00:22:27.480> like<00:22:27.840> a<00:22:27.900> kind<00:22:28.320> of<00:22:28.380> annotation 00:22:29.530 --> 00:22:29.540 align:start position:0% even published like a kind of annotation 00:22:29.540 --> 00:22:32.270 align:start position:0% even published like a kind of annotation in<00:22:30.540> which<00:22:30.810> form<00:22:31.170> that's<00:22:31.680> the<00:22:31.860> question<00:22:32.190> but 00:22:32.270 --> 00:22:32.280 align:start position:0% in which form that's the question but 00:22:32.280 --> 00:22:33.680 align:start position:0% in which form that's the question but like<00:22:32.490> basically<00:22:32.880> having<00:22:33.180> an<00:22:33.270> opinion<00:22:33.660> that 00:22:33.680 --> 00:22:33.690 align:start position:0% like basically having an opinion that 00:22:33.690 --> 00:22:36.020 align:start position:0% like basically having an opinion that this<00:22:33.900> source<00:22:34.200> code<00:22:34.350> has<00:22:34.500> been<00:22:34.530> audited<00:22:35.160> and 00:22:36.020 --> 00:22:36.030 align:start position:0% this source code has been audited and 00:22:36.030 --> 00:22:37.760 align:start position:0% this source code has been audited and ideally<00:22:36.570> we<00:22:36.690> also<00:22:36.840> get<00:22:37.080> to<00:22:37.200> standards<00:22:37.650> like 00:22:37.760 --> 00:22:37.770 align:start position:0% ideally we also get to standards like 00:22:37.770 --> 00:22:39.890 align:start position:0% ideally we also get to standards like what<00:22:38.010> what<00:22:38.280> does<00:22:38.430> it<00:22:38.550> mean<00:22:38.730> level<00:22:39.210> of<00:22:39.450> auditing 00:22:39.890 --> 00:22:39.900 align:start position:0% what what does it mean level of auditing 00:22:39.900 --> 00:22:42.710 align:start position:0% what what does it mean level of auditing happened<00:22:40.320> and<00:22:40.940> was<00:22:41.940> abolished<00:22:42.240> by<00:22:42.510> one 00:22:42.710 --> 00:22:42.720 align:start position:0% happened and was abolished by one 00:22:42.720 --> 00:22:47.240 align:start position:0% happened and was abolished by one Morgan's<00:22:43.080> age<00:22:43.260> or<00:22:43.830> many<00:22:44.370> and<00:22:45.950> he<00:22:46.950> said<00:22:47.100> like 00:22:47.240 --> 00:22:47.250 align:start position:0% Morgan's age or many and he said like 00:22:47.250 --> 00:22:48.920 align:start position:0% Morgan's age or many and he said like even<00:22:47.460> at<00:22:47.910> the<00:22:48.000> break<00:22:48.150> even<00:22:48.420> is<00:22:48.570> so<00:22:48.750> many 00:22:48.920 --> 00:22:48.930 align:start position:0% even at the break even is so many 00:22:48.930 --> 00:22:52.970 align:start position:0% even at the break even is so many metadata<00:22:49.740> that<00:22:49.830> could<00:22:50.160> be<00:22:50.250> generated<00:22:51.980> that 00:22:52.970 --> 00:22:52.980 align:start position:0% metadata that could be generated that 00:22:52.980 --> 00:22:54.440 align:start position:0% metadata that could be generated that basically<00:22:53.370> have<00:22:53.880> like<00:22:53.910> additional 00:22:54.440 --> 00:22:54.450 align:start position:0% basically have like additional 00:22:54.450 --> 00:22:55.970 align:start position:0% basically have like additional information<00:22:54.540> because<00:22:55.230> the<00:22:55.470> source<00:22:55.680> for<00:22:55.890> the 00:22:55.970 --> 00:22:55.980 align:start position:0% information because the source for the 00:22:55.980 --> 00:22:59.830 align:start position:0% information because the source for the search<00:22:56.190> is<00:22:56.340> like<00:22:56.520> a<00:22:56.550> good<00:22:56.790> first<00:22:57.000> step<00:22:57.590> so 00:22:59.830 --> 00:22:59.840 align:start position:0% search is like a good first step so 00:22:59.840 --> 00:23:01.970 align:start position:0% search is like a good first step so they're<00:23:00.840> the<00:23:00.930> leases<00:23:01.200> for<00:23:01.350> the<00:23:01.440> future<00:23:01.800> what 00:23:01.970 --> 00:23:01.980 align:start position:0% they're the leases for the future what 00:23:01.980 --> 00:23:03.620 align:start position:0% they're the leases for the future what about<00:23:02.160> for<00:23:02.370> the<00:23:02.430> possible<00:23:02.850> were<00:23:02.970> to<00:23:03.120> working 00:23:03.620 --> 00:23:03.630 align:start position:0% about for the possible were to working 00:23:03.630 --> 00:23:12.850 align:start position:0% about for the possible were to working with<00:23:03.870> all<00:23:04.830> the<00:23:04.950> think<00:23:06.590> they're<00:23:07.590> like<00:23:11.000> yes<00:23:12.000> oh 00:23:12.850 --> 00:23:12.860 align:start position:0% with all the think they're like yes oh 00:23:12.860 --> 00:23:16.700 align:start position:0% with all the think they're like yes oh yeah<00:23:13.890> so<00:23:14.250> I'm<00:23:14.550> an<00:23:14.790> assault<00:23:15.300> we<00:23:15.930> are<00:23:16.140> security 00:23:16.700 --> 00:23:16.710 align:start position:0% yeah so I'm an assault we are security 00:23:16.710 --> 00:23:19.790 align:start position:0% yeah so I'm an assault we are security auditing<00:23:17.040> company<00:23:17.460> and<00:23:17.760> typically<00:23:18.800> the 00:23:19.790 --> 00:23:19.800 align:start position:0% auditing company and typically the 00:23:19.800 --> 00:23:22.280 align:start position:0% auditing company and typically the majority<00:23:19.950> of<00:23:20.370> clients<00:23:20.940> want<00:23:21.510> to<00:23:21.630> publish<00:23:22.140> the 00:23:22.280 --> 00:23:22.290 align:start position:0% majority of clients want to publish the 00:23:22.290 --> 00:23:24.260 align:start position:0% majority of clients want to publish the fact<00:23:22.530> that<00:23:22.590> they<00:23:22.830> have<00:23:22.980> partnered<00:23:23.430> on<00:23:23.640> it<00:23:23.820> and 00:23:24.260 --> 00:23:24.270 align:start position:0% fact that they have partnered on it and 00:23:24.270 --> 00:23:26.270 align:start position:0% fact that they have partnered on it and also<00:23:24.450> want<00:23:24.840> to<00:23:24.900> publish<00:23:25.260> a<00:23:25.290> full<00:23:25.590> audit<00:23:25.800> report 00:23:26.270 --> 00:23:26.280 align:start position:0% also want to publish a full audit report 00:23:26.280 --> 00:23:28.340 align:start position:0% also want to publish a full audit report right<00:23:26.490> which<00:23:26.700> is<00:23:26.880> uncommon<00:23:27.420> compared<00:23:28.140> to 00:23:28.340 --> 00:23:28.350 align:start position:0% right which is uncommon compared to 00:23:28.350 --> 00:23:33.740 align:start position:0% right which is uncommon compared to other<00:23:28.830> industries<00:23:29.130> and<00:23:29.990> so<00:23:30.990> it<00:23:31.680> would<00:23:31.950> I<00:23:32.750> think 00:23:33.740 --> 00:23:33.750 align:start position:0% other industries and so it would I think 00:23:33.750 --> 00:23:35.780 align:start position:0% other industries and so it would I think it<00:23:33.870> would<00:23:33.990> be<00:23:34.140> great<00:23:34.290> to<00:23:34.410> highlight<00:23:35.130> most 00:23:35.780 --> 00:23:35.790 align:start position:0% it would be great to highlight most 00:23:35.790 --> 00:23:38.840 align:start position:0% it would be great to highlight most positive<00:23:36.420> and<00:23:36.540> negative<00:23:36.930> examples<00:23:37.850> recently 00:23:38.840 --> 00:23:38.850 align:start position:0% positive and negative examples recently 00:23:38.850 --> 00:23:41.810 align:start position:0% positive and negative examples recently there<00:23:39.240> was<00:23:39.330> a<00:23:39.390> good<00:23:40.080> next<00:23:41.010> I<00:23:41.160> mean<00:23:41.400> the<00:23:41.610> famous 00:23:41.810 --> 00:23:41.820 align:start position:0% there was a good next I mean the famous 00:23:41.820 --> 00:23:44.210 align:start position:0% there was a good next I mean the famous negative<00:23:42.420> income<00:23:42.750> which<00:23:43.050> was<00:23:43.260> there<00:23:43.560> right 00:23:44.210 --> 00:23:44.220 align:start position:0% negative income which was there right 00:23:44.220 --> 00:23:48.020 align:start position:0% negative income which was there right where<00:23:44.550> people<00:23:46.130> looked<00:23:47.130> into<00:23:47.430> the<00:23:47.580> contract 00:23:48.020 --> 00:23:48.030 align:start position:0% where people looked into the contract 00:23:48.030 --> 00:23:49.670 align:start position:0% where people looked into the contract and<00:23:48.150> were<00:23:48.300> like<00:23:48.510> yes<00:23:49.020> definitely<00:23:49.650> a 00:23:49.670 --> 00:23:49.680 align:start position:0% and were like yes definitely a 00:23:49.680 --> 00:23:52.700 align:start position:0% and were like yes definitely a proposition<00:23:50.400> and<00:23:50.870> you<00:23:51.870> could<00:23:52.110> warn<00:23:52.410> the<00:23:52.680> user 00:23:52.700 --> 00:23:52.710 align:start position:0% proposition and you could warn the user 00:23:52.710 --> 00:23:55.700 align:start position:0% proposition and you could warn the user say<00:23:53.280> like<00:23:53.810> please<00:23:54.810> don't<00:23:54.990> put<00:23:55.230> any<00:23:55.440> more<00:23:55.650> money 00:23:55.700 --> 00:23:55.710 align:start position:0% say like please don't put any more money 00:23:55.710 --> 00:23:58.010 align:start position:0% say like please don't put any more money in<00:23:56.100> because<00:23:56.460> at<00:23:56.730> the<00:23:57.180> time<00:23:57.420> is<00:23:57.750> their 00:23:58.010 --> 00:23:58.020 align:start position:0% in because at the time is their 00:23:58.020 --> 00:24:00.440 align:start position:0% in because at the time is their vulnerability<00:23:58.950> square<00:23:59.190> population<00:23:59.760> people 00:24:00.440 --> 00:24:00.450 align:start position:0% vulnerability square population people 00:24:00.450 --> 00:24:03.650 align:start position:0% vulnerability square population people are<00:24:00.570> still<00:24:00.840> putting<00:24:01.080> more<00:24:01.410> money<00:24:01.440> in<00:24:02.660> like 00:24:03.650 --> 00:24:03.660 align:start position:0% are still putting more money in like 00:24:03.660 --> 00:24:05.510 align:start position:0% are still putting more money in like some<00:24:04.410> people<00:24:04.680> were<00:24:04.770> saying<00:24:04.980> it<00:24:05.100> was<00:24:05.160> money 00:24:05.510 --> 00:24:05.520 align:start position:0% some people were saying it was money 00:24:05.520 --> 00:24:08.110 align:start position:0% some people were saying it was money laundering<00:24:06.000> for<00:24:06.060> this<00:24:06.360> is<00:24:06.570> another<00:24:06.960> issue<00:24:07.260> and 00:24:08.110 --> 00:24:08.120 align:start position:0% laundering for this is another issue and 00:24:08.120 --> 00:24:11.090 align:start position:0% laundering for this is another issue and so<00:24:09.120> yeah<00:24:09.840> I<00:24:10.020> think<00:24:10.140> it<00:24:10.500> would<00:24:10.680> be<00:24:10.830> great<00:24:11.070> to 00:24:11.090 --> 00:24:11.100 align:start position:0% so yeah I think it would be great to 00:24:11.100 --> 00:24:13.730 align:start position:0% so yeah I think it would be great to kind<00:24:11.430> of<00:24:11.580> have<00:24:11.730> like<00:24:11.760> a<00:24:12.320> they<00:24:13.320> could<00:24:13.530> probably 00:24:13.730 --> 00:24:13.740 align:start position:0% kind of have like a they could probably 00:24:13.740 --> 00:24:16.760 align:start position:0% kind of have like a they could probably be<00:24:14.070> like<00:24:14.660> three<00:24:15.660> different<00:24:15.990> things<00:24:16.380> like<00:24:16.590> it 00:24:16.760 --> 00:24:16.770 align:start position:0% be like three different things like it 00:24:16.770 --> 00:24:19.220 align:start position:0% be like three different things like it would<00:24:16.920> be<00:24:17.040> like<00:24:17.220> a<00:24:17.250> check<00:24:17.610> mark<00:24:17.820> like<00:24:18.230> audit 00:24:19.220 --> 00:24:19.230 align:start position:0% would be like a check mark like audit 00:24:19.230 --> 00:24:20.900 align:start position:0% would be like a check mark like audit and<00:24:19.470> when<00:24:19.710> you<00:24:19.830> click<00:24:20.070> on<00:24:20.190> the<00:24:20.340> check<00:24:20.550> mark<00:24:20.580> you 00:24:20.900 --> 00:24:20.910 align:start position:0% and when you click on the check mark you 00:24:20.910 --> 00:24:23.210 align:start position:0% and when you click on the check mark you see<00:24:21.120> like<00:24:21.270> before<00:24:21.570> report<00:24:22.020> or<00:24:22.680> they<00:24:22.890> could<00:24:23.130> be 00:24:23.210 --> 00:24:23.220 align:start position:0% see like before report or they could be 00:24:23.220 --> 00:24:27.290 align:start position:0% see like before report or they could be like<00:24:23.400> a<00:24:23.850> warning<00:24:24.420> and<00:24:25.070> these<00:24:26.070> could<00:24:27.000> go<00:24:27.030> to 00:24:27.290 --> 00:24:27.300 align:start position:0% like a warning and these could go to 00:24:27.300 --> 00:24:29.300 align:start position:0% like a warning and these could go to different<00:24:27.780> sources<00:24:28.110> right<00:24:28.530> like<00:24:28.800> so<00:24:29.010> I<00:24:29.040> mean 00:24:29.300 --> 00:24:29.310 align:start position:0% different sources right like so I mean 00:24:29.310 --> 00:24:32.300 align:start position:0% different sources right like so I mean ideally<00:24:29.820> of<00:24:30.600> course<00:24:31.020> this<00:24:31.410> should<00:24:31.470> just<00:24:31.710> be<00:24:32.100> us 00:24:32.300 --> 00:24:32.310 align:start position:0% ideally of course this should just be us 00:24:32.310 --> 00:24:34.820 align:start position:0% ideally of course this should just be us enough<00:24:32.940> people<00:24:33.390> should<00:24:33.720> just<00:24:34.080> all<00:24:34.290> trust<00:24:34.620> us 00:24:34.820 --> 00:24:34.830 align:start position:0% enough people should just all trust us 00:24:34.830 --> 00:24:36.590 align:start position:0% enough people should just all trust us because<00:24:35.070> this<00:24:35.430> one's<00:24:35.670> the<00:24:35.940> idea<00:24:36.210> but<00:24:36.390> like 00:24:36.590 --> 00:24:36.600 align:start position:0% because this one's the idea but like 00:24:36.600 --> 00:24:41.500 align:start position:0% because this one's the idea but like would<00:24:37.290> be<00:24:37.410> great<00:24:37.650> anyway<00:24:38.630> so<00:24:39.630> yeah<00:24:39.810> like<00:24:40.110> any 00:24:41.500 --> 00:24:41.510 align:start position:0% would be great anyway so yeah like any 00:24:41.510 --> 00:24:44.180 align:start position:0% would be great anyway so yeah like any they<00:24:42.510> could<00:24:42.720> be<00:24:42.840> you<00:24:43.020> might<00:24:43.260> check<00:24:43.560> mark<00:24:43.890> and 00:24:44.180 --> 00:24:44.190 align:start position:0% they could be you might check mark and 00:24:44.190 --> 00:24:45.590 align:start position:0% they could be you might check mark and then<00:24:44.370> you<00:24:44.460> go<00:24:44.640> to<00:24:44.700> the<00:24:44.940> difference 00:24:45.590 --> 00:24:45.600 align:start position:0% then you go to the difference 00:24:45.600 --> 00:24:48.020 align:start position:0% then you go to the difference and<00:24:45.990> like<00:24:46.230> so<00:24:46.500> that<00:24:46.650> anyone<00:24:47.070> can<00:24:47.340> provide 00:24:48.020 --> 00:24:48.030 align:start position:0% and like so that anyone can provide 00:24:48.030 --> 00:24:50.960 align:start position:0% and like so that anyone can provide their<00:24:48.300> community<00:24:48.840> but<00:24:49.740> do<00:24:50.100> you<00:24:50.190> also<00:24:50.460> ordered' 00:24:50.960 --> 00:24:50.970 align:start position:0% their community but do you also ordered' 00:24:50.970 --> 00:24:52.820 align:start position:0% their community but do you also ordered' sometimes<00:24:51.420> like<00:24:51.660> some<00:24:51.840> calls<00:24:52.110> it<00:24:52.320> is<00:24:52.440> not<00:24:52.620> like 00:24:52.820 --> 00:24:52.830 align:start position:0% sometimes like some calls it is not like 00:24:52.830 --> 00:24:55.390 align:start position:0% sometimes like some calls it is not like coming<00:24:53.160> from<00:24:53.460> the<00:24:53.760> client<00:24:53.970> but<00:24:54.420> you<00:24:54.450> just 00:24:55.390 --> 00:24:55.400 align:start position:0% coming from the client but you just 00:24:55.400 --> 00:24:58.880 align:start position:0% coming from the client but you just analyze<00:24:56.400> it<00:24:56.820> anyway<00:24:57.150> yeah<00:24:57.540> so<00:24:57.840> we<00:24:58.410> often<00:24:58.800> have 00:24:58.880 --> 00:24:58.890 align:start position:0% analyze it anyway yeah so we often have 00:24:58.890 --> 00:25:01.790 align:start position:0% analyze it anyway yeah so we often have dependencies<00:24:59.610> that<00:25:00.000> are<00:25:00.930> already<00:25:01.320> existing 00:25:01.790 --> 00:25:01.800 align:start position:0% dependencies that are already existing 00:25:01.800 --> 00:25:05.240 align:start position:0% dependencies that are already existing right<00:25:02.460> so<00:25:02.670> like<00:25:03.120> some<00:25:03.990> client<00:25:04.410> code<00:25:04.590> is<00:25:04.800> using 00:25:05.240 --> 00:25:05.250 align:start position:0% right so like some client code is using 00:25:05.250 --> 00:25:08.690 align:start position:0% right so like some client code is using I<00:25:05.520> don't<00:25:05.850> know<00:25:06.110> compound<00:25:07.110> or<00:25:07.500> maker<00:25:08.280> or 00:25:08.690 --> 00:25:08.700 align:start position:0% I don't know compound or maker or 00:25:08.700 --> 00:25:11.090 align:start position:0% I don't know compound or maker or whatever<00:25:09.030> so<00:25:09.990> existing<00:25:10.470> dependencies 00:25:11.090 --> 00:25:11.100 align:start position:0% whatever so existing dependencies 00:25:11.100 --> 00:25:14.150 align:start position:0% whatever so existing dependencies between<00:25:11.250> them<00:25:11.610> both<00:25:11.730> edges<00:25:12.090> and<00:25:12.750> do<00:25:13.140> this<00:25:13.920> data 00:25:14.150 --> 00:25:14.160 align:start position:0% between them both edges and do this data 00:25:14.160 --> 00:25:26.140 align:start position:0% between them both edges and do this data anywhere<00:25:14.730> like<00:25:15.180> so<00:25:15.870> this<00:25:16.020> is<00:25:16.170> in<00:25:16.350> your<00:25:22.670> oh<00:25:24.980> I 00:25:26.140 --> 00:25:26.150 align:start position:0% anywhere like so this is in your oh I 00:25:26.150 --> 00:25:28.490 align:start position:0% anywhere like so this is in your oh I mean<00:25:27.150> we<00:25:27.390> were<00:25:27.510> thinking<00:25:27.870> like<00:25:28.050> if<00:25:28.200> there<00:25:28.350> was 00:25:28.490 --> 00:25:28.500 align:start position:0% mean we were thinking like if there was 00:25:28.500 --> 00:25:30.140 align:start position:0% mean we were thinking like if there was a<00:25:28.530> standard<00:25:29.100> I<00:25:29.280> mean<00:25:29.460> there's<00:25:29.850> only<00:25:29.940> one 00:25:30.140 --> 00:25:30.150 align:start position:0% a standard I mean there's only one 00:25:30.150 --> 00:25:32.060 align:start position:0% a standard I mean there's only one tender<00:25:30.480> like<00:25:30.750> butter 00:25:32.060 --> 00:25:32.070 align:start position:0% tender like butter 00:25:32.070 --> 00:25:34.879 align:start position:0% tender like butter I<00:25:32.100> have<00:25:32.369> a<00:25:32.399> model<00:25:32.759> in<00:25:32.850> what<00:25:33.119> levels<00:25:33.479> and<00:25:34.049> what 00:25:34.879 --> 00:25:34.889 align:start position:0% I have a model in what levels and what 00:25:34.889 --> 00:25:37.009 align:start position:0% I have a model in what levels and what does<00:25:35.009> that<00:25:35.039> what<00:25:35.399> kind<00:25:35.519> of<00:25:35.609> guarantees<00:25:35.899> does<00:25:36.899> I 00:25:37.009 --> 00:25:37.019 align:start position:0% does that what kind of guarantees does I 00:25:37.019 --> 00:25:40.340 align:start position:0% does that what kind of guarantees does I communicate<00:25:37.499> but<00:25:37.679> another<00:25:37.919> one<00:25:38.100> a<00:25:39.350> format 00:25:40.340 --> 00:25:40.350 align:start position:0% communicate but another one a format 00:25:40.350 --> 00:25:44.659 align:start position:0% communicate but another one a format like<00:25:40.379> the<00:25:40.619> data<00:25:40.799> is<00:25:41.279> standard<00:25:41.669> then<00:25:42.149> maybe<00:25:43.669> for 00:25:44.659 --> 00:25:44.669 align:start position:0% like the data is standard then maybe for 00:25:44.669 --> 00:25:46.340 align:start position:0% like the data is standard then maybe for example<00:25:44.789> I<00:25:45.299> mean<00:25:45.570> how<00:25:45.779> perfect<00:25:45.840> that<00:25:46.109> will<00:25:46.289> be 00:25:46.340 --> 00:25:46.350 align:start position:0% example I mean how perfect that will be 00:25:46.350 --> 00:25:47.869 align:start position:0% example I mean how perfect that will be useful<00:25:46.499> but<00:25:46.739> generally<00:25:47.190> wallets<00:25:47.519> could<00:25:47.729> use 00:25:47.869 --> 00:25:47.879 align:start position:0% useful but generally wallets could use 00:25:47.879 --> 00:25:49.039 align:start position:0% useful but generally wallets could use it<00:25:48.059> too 00:25:49.039 --> 00:25:49.049 align:start position:0% it too 00:25:49.049 --> 00:25:51.169 align:start position:0% it too just<00:25:49.950> like<00:25:50.100> the<00:25:50.309> basically<00:25:50.700> movie<00:25:50.999> as<00:25:51.149> the 00:25:51.169 --> 00:25:51.179 align:start position:0% just like the basically movie as the 00:25:51.179 --> 00:25:53.330 align:start position:0% just like the basically movie as the disposable<00:25:51.869> exists<00:25:52.289> but<00:25:52.440> like<00:25:52.769> what<00:25:53.309> about 00:25:53.330 --> 00:25:53.340 align:start position:0% disposable exists but like what about 00:25:53.340 --> 00:25:55.070 align:start position:0% disposable exists but like what about does<00:25:53.700> it<00:25:53.729> hit<00:25:53.940> that<00:25:53.970> doesn't<00:25:54.419> has<00:25:54.840> it<00:25:54.960> been 00:25:55.070 --> 00:25:55.080 align:start position:0% does it hit that doesn't has it been 00:25:55.080 --> 00:25:57.349 align:start position:0% does it hit that doesn't has it been audited<00:25:55.529> so<00:25:55.679> they<00:25:55.859> could<00:25:56.009> be<00:25:56.210> present<00:25:57.210> data 00:25:57.349 --> 00:25:57.359 align:start position:0% audited so they could be present data 00:25:57.359 --> 00:25:59.509 align:start position:0% audited so they could be present data from<00:25:57.690> and<00:25:58.139> a<00:25:58.200> notice<00:25:58.529> of<00:25:58.679> standardized<00:25:59.129> format 00:25:59.509 --> 00:25:59.519 align:start position:0% from and a notice of standardized format 00:25:59.519 --> 00:26:01.310 align:start position:0% from and a notice of standardized format so<00:25:59.639> they<00:25:59.729> can<00:25:59.909> display<00:26:00.149> that<00:26:00.570> and<00:26:00.779> hopefully 00:26:01.310 --> 00:26:01.320 align:start position:0% so they can display that and hopefully 00:26:01.320 --> 00:26:03.049 align:start position:0% so they can display that and hopefully all<00:26:01.710> the<00:26:01.830> wallets<00:26:02.129> which<00:26:02.609> was<00:26:02.759> the<00:26:02.879> same 00:26:03.049 --> 00:26:03.059 align:start position:0% all the wallets which was the same 00:26:03.059 --> 00:26:05.210 align:start position:0% all the wallets which was the same standards<00:26:03.450> our<00:26:03.570> users<00:26:03.840> used<00:26:04.289> to<00:26:04.440> this<00:26:04.919> is<00:26:05.099> how 00:26:05.210 --> 00:26:05.220 align:start position:0% standards our users used to this is how 00:26:05.220 --> 00:26:07.219 align:start position:0% standards our users used to this is how it<00:26:05.340> looks<00:26:05.519> and<00:26:06.269> that's<00:26:06.419> what<00:26:06.629> it<00:26:06.749> means<00:26:06.779> and 00:26:07.219 --> 00:26:07.229 align:start position:0% it looks and that's what it means and 00:26:07.229 --> 00:26:10.609 align:start position:0% it looks and that's what it means and maybe<00:26:07.639> believe<00:26:08.639> me<00:26:08.759> I<00:26:08.820> can<00:26:08.999> see<00:26:09.539> one<00:26:09.749> change<00:26:10.109> in 00:26:10.609 --> 00:26:10.619 align:start position:0% maybe believe me I can see one change in 00:26:10.619 --> 00:26:13.369 align:start position:0% maybe believe me I can see one change in any<00:26:10.950> maybe<00:26:11.639> Rock<00:26:11.940> Explorer<00:26:12.389> or<00:26:12.509> whatever<00:26:12.809> but 00:26:13.369 --> 00:26:13.379 align:start position:0% any maybe Rock Explorer or whatever but 00:26:13.379 --> 00:26:22.039 align:start position:0% any maybe Rock Explorer or whatever but this<00:26:13.950> is<00:26:14.099> how<00:26:14.659> expenditure<00:26:17.210> but<00:26:18.210> also<00:26:21.049> you 00:26:22.039 --> 00:26:22.049 align:start position:0% this is how expenditure but also you 00:26:22.049 --> 00:26:25.190 align:start position:0% this is how expenditure but also you know<00:26:22.580> version<00:26:23.580> published<00:26:24.299> source<00:26:24.690> compacted 00:26:25.190 --> 00:26:25.200 align:start position:0% know version published source compacted 00:26:25.200 --> 00:26:26.989 align:start position:0% know version published source compacted wallets<00:26:25.529> would<00:26:25.679> integrate<00:26:25.919> this<00:26:26.279> this<00:26:26.580> will 00:26:26.989 --> 00:26:26.999 align:start position:0% wallets would integrate this this will 00:26:26.999 --> 00:26:30.259 align:start position:0% wallets would integrate this this will also<00:26:27.269> create<00:26:27.570> another<00:26:28.190> like<00:26:29.190> pressure<00:26:29.609> to 00:26:30.259 --> 00:26:30.269 align:start position:0% also create another like pressure to 00:26:30.269 --> 00:26:32.719 align:start position:0% also create another like pressure to maybe<00:26:30.570> or<00:26:31.229> in<00:26:31.379> sensitization<00:26:31.830> to<00:26:32.369> publish 00:26:32.719 --> 00:26:32.729 align:start position:0% maybe or in sensitization to publish 00:26:32.729 --> 00:26:34.820 align:start position:0% maybe or in sensitization to publish source<00:26:32.999> because<00:26:33.509> of<00:26:33.629> users<00:26:33.960> every<00:26:34.499> time<00:26:34.679> they 00:26:34.820 --> 00:26:34.830 align:start position:0% source because of users every time they 00:26:34.830 --> 00:26:36.950 align:start position:0% source because of users every time they confirm<00:26:35.159> now<00:26:35.279> see<00:26:35.580> oh<00:26:35.789> I'm<00:26:36.299> interacting<00:26:36.570> with 00:26:36.950 --> 00:26:36.960 align:start position:0% confirm now see oh I'm interacting with 00:26:36.960 --> 00:26:39.049 align:start position:0% confirm now see oh I'm interacting with all<00:26:37.109> the<00:26:37.200> time<00:26:37.379> the<00:26:37.559> context<00:26:37.919> of<00:26:38.009> that<00:26:38.429> kind<00:26:38.970> of 00:26:39.049 --> 00:26:39.059 align:start position:0% all the time the context of that kind of 00:26:39.059 --> 00:26:40.580 align:start position:0% all the time the context of that kind of give<00:26:39.299> me<00:26:39.389> like<00:26:39.539> a<00:26:39.570> warning<00:26:40.049> or<00:26:40.169> something 00:26:40.580 --> 00:26:40.590 align:start position:0% give me like a warning or something 00:26:40.590 --> 00:26:42.619 align:start position:0% give me like a warning or something it<00:26:40.739> hasn't<00:26:40.950> been<00:26:41.179> take<00:26:42.179> the<00:26:42.299> source<00:26:42.539> that 00:26:42.619 --> 00:26:42.629 align:start position:0% it hasn't been take the source that 00:26:42.629 --> 00:26:44.239 align:start position:0% it hasn't been take the source that doesn't<00:26:42.779> even<00:26:42.929> exist<00:26:43.349> or<00:26:43.470> maybe<00:26:43.710> then<00:26:44.009> later 00:26:44.239 --> 00:26:44.249 align:start position:0% doesn't even exist or maybe then later 00:26:44.249 --> 00:26:47.389 align:start position:0% doesn't even exist or maybe then later on<00:26:44.690> okay<00:26:45.690> it<00:26:45.840> has<00:26:45.989> been<00:26:46.169> audited<00:26:46.590> but<00:26:46.830> what<00:26:47.190> do 00:26:47.389 --> 00:26:47.399 align:start position:0% on okay it has been audited but what do 00:26:47.399 --> 00:26:49.969 align:start position:0% on okay it has been audited but what do you<00:26:47.489> mean<00:26:47.669> is<00:26:47.820> it<00:26:47.849> like<00:26:47.970> how<00:26:48.299> how<00:26:48.929> in-depth<00:26:49.799> has 00:26:49.969 --> 00:26:49.979 align:start position:0% you mean is it like how how in-depth has 00:26:49.979 --> 00:26:52.099 align:start position:0% you mean is it like how how in-depth has it<00:26:50.099> been<00:26:50.249> audited<00:26:50.700> and<00:26:50.879> the<00:26:51.479> maybe<00:26:51.659> users<00:26:51.869> who 00:26:52.099 --> 00:26:52.109 align:start position:0% it been audited and the maybe users who 00:26:52.109 --> 00:26:54.229 align:start position:0% it been audited and the maybe users who changed<00:26:53.009> their<00:26:53.099> behavior<00:26:53.519> and<00:26:53.700> I<00:26:53.970> either 00:26:54.229 --> 00:26:54.239 align:start position:0% changed their behavior and I either 00:26:54.239 --> 00:26:58.580 align:start position:0% changed their behavior and I either demand<00:26:54.720> we<00:26:55.229> switch<00:26:55.649> to<00:26:56.369> alternatives<00:26:57.440> have<00:26:58.440> it 00:26:58.580 --> 00:26:58.590 align:start position:0% demand we switch to alternatives have it 00:26:58.590 --> 00:27:00.240 align:start position:0% demand we switch to alternatives have it better 00:27:00.240 --> 00:27:00.250 align:start position:0% better 00:27:00.250 --> 00:27:10.190 align:start position:0% better maybe<00:27:00.940> I'll<00:27:01.270> publish<00:27:01.600> or<00:27:02.169> get<00:27:02.320> an<00:27:02.440> audit<00:27:07.559> remix 00:27:10.190 --> 00:27:10.200 align:start position:0% maybe I'll publish or get an audit remix 00:27:10.200 --> 00:27:12.600 align:start position:0% maybe I'll publish or get an audit remix we<00:27:11.200> are<00:27:11.320> discussing<00:27:11.650> basically<00:27:12.159> like<00:27:12.340> what 00:27:12.600 --> 00:27:12.610 align:start position:0% we are discussing basically like what 00:27:12.610 --> 00:27:46.580 align:start position:0% we are discussing basically like what are<00:27:12.940> the<00:27:13.179> problems<00:27:18.480> in<00:27:39.750> the<00:27:40.750> moment<00:27:41.049> in<00:27:41.230> there 00:27:46.580 --> 00:27:46.590 align:start position:0% 00:27:46.590 --> 00:27:49.850 align:start position:0% do<00:27:47.100> you<00:27:47.190> have<00:27:47.370> any<00:27:47.669> ideas<00:27:48.419> why<00:27:48.720> to<00:27:48.779> be<00:27:49.590> better 00:27:49.850 --> 00:27:49.860 align:start position:0% do you have any ideas why to be better 00:27:49.860 --> 00:28:29.509 align:start position:0% do you have any ideas why to be better like<00:28:20.600> you<00:28:21.600> are<00:28:21.960> working<00:28:22.289> abroad<00:28:27.529> yeah<00:28:28.529> yeah<00:28:29.490> I 00:28:29.509 --> 00:28:29.519 align:start position:0% like you are working abroad yeah yeah I 00:28:29.519 --> 00:28:32.330 align:start position:0% like you are working abroad yeah yeah I also<00:28:30.119> feel<00:28:30.509> that<00:28:30.679> publishing<00:28:31.679> like<00:28:32.159> an 00:28:32.330 --> 00:28:32.340 align:start position:0% also feel that publishing like an 00:28:32.340 --> 00:28:36.049 align:start position:0% also feel that publishing like an opt-out<00:28:32.789> it<00:28:33.210> seems<00:28:33.600> a<00:28:33.749> bit<00:28:34.730> it's<00:28:35.730> a<00:28:35.789> large 00:28:36.049 --> 00:28:36.059 align:start position:0% opt-out it seems a bit it's a large 00:28:36.059 --> 00:28:36.919 align:start position:0% opt-out it seems a bit it's a large assumption<00:28:36.600> to<00:28:36.720> make 00:28:36.919 --> 00:28:36.929 align:start position:0% assumption to make 00:28:36.929 --> 00:28:39.470 align:start position:0% assumption to make yeah<00:28:37.369> it's<00:28:38.369> someone<00:28:38.669> working<00:28:38.850> on<00:28:39.119> and<00:28:39.360> on 00:28:39.470 --> 00:28:39.480 align:start position:0% yeah it's someone working on and on 00:28:39.480 --> 00:28:40.850 align:start position:0% yeah it's someone working on and on something<00:28:39.869> sensitive<00:28:40.230> the<00:28:40.409> truth<00:28:40.679> we 00:28:40.850 --> 00:28:40.860 align:start position:0% something sensitive the truth we 00:28:40.860 --> 00:28:43.879 align:start position:0% something sensitive the truth we published<00:28:41.279> and<00:28:41.490> you<00:28:42.080> just<00:28:43.080> push<00:28:43.470> it<00:28:43.619> because 00:28:43.879 --> 00:28:43.889 align:start position:0% published and you just push it because 00:28:43.889 --> 00:28:45.139 align:start position:0% published and you just push it because the<00:28:44.009> interesting<00:28:44.399> change<00:28:44.580> of<00:28:44.669> walks<00:28:44.909> that 00:28:45.139 --> 00:28:45.149 align:start position:0% the interesting change of walks that 00:28:45.149 --> 00:28:47.840 align:start position:0% the interesting change of walks that seems<00:28:45.419> a<00:28:45.539> bit<00:28:45.919> but<00:28:46.919> I<00:28:46.950> think<00:28:47.279> all<00:28:47.399> the<00:28:47.549> end<00:28:47.669> it's 00:28:47.840 --> 00:28:47.850 align:start position:0% seems a bit but I think all the end it's 00:28:47.850 --> 00:28:50.149 align:start position:0% seems a bit but I think all the end it's I<00:28:48.029> think<00:28:48.210> it's<00:28:48.299> a<00:28:48.389> great<00:28:48.480> idea<00:28:49.159> there's 00:28:50.149 --> 00:28:50.159 align:start position:0% I think it's a great idea there's 00:28:50.159 --> 00:28:52.399 align:start position:0% I think it's a great idea there's something<00:28:50.519> halfway<00:28:51.090> between<00:28:51.299> not<00:28:51.929> publishing 00:28:52.399 --> 00:28:52.409 align:start position:0% something halfway between not publishing 00:28:52.409 --> 00:28:54.799 align:start position:0% something halfway between not publishing and<00:28:52.740> publishing<00:28:53.279> the<00:28:53.429> source<00:28:53.759> you<00:28:54.659> can 00:28:54.799 --> 00:28:54.809 align:start position:0% and publishing the source you can 00:28:54.809 --> 00:28:58.989 align:start position:0% and publishing the source you can publish<00:28:55.200> the<00:28:55.669> function<00:28:56.669> signatures<00:28:57.629> and<00:28:57.929> the 00:28:58.989 --> 00:28:58.999 align:start position:0% publish the function signatures and the 00:28:58.999 --> 00:29:03.799 align:start position:0% publish the function signatures and the encoded<00:29:02.299> basically<00:29:03.299> the<00:29:03.389> thing<00:29:03.539> that<00:29:03.690> you 00:29:03.799 --> 00:29:03.809 align:start position:0% encoded basically the thing that you 00:29:03.809 --> 00:29:06.440 align:start position:0% encoded basically the thing that you would<00:29:03.929> get<00:29:04.139> from<00:29:04.350> the<00:29:04.379> API<00:29:04.529> I<00:29:05.220> you<00:29:06.210> don't<00:29:06.360> have 00:29:06.440 --> 00:29:06.450 align:start position:0% would get from the API I you don't have 00:29:06.450 --> 00:29:08.749 align:start position:0% would get from the API I you don't have to<00:29:06.570> publish<00:29:06.869> the<00:29:06.990> entire<00:29:07.259> source<00:29:07.759> just 00:29:08.749 --> 00:29:08.759 align:start position:0% to publish the entire source just 00:29:08.759 --> 00:29:11.149 align:start position:0% to publish the entire source just publish<00:29:09.090> the<00:29:09.210> API<00:29:09.480> just<00:29:09.960> the<00:29:10.169> strings<00:29:10.799> of<00:29:11.009> the 00:29:11.149 --> 00:29:11.159 align:start position:0% publish the API just the strings of the 00:29:11.159 --> 00:29:13.639 align:start position:0% publish the API just the strings of the function<00:29:11.639> and<00:29:11.820> their<00:29:12.179> corresponding<00:29:13.049> encoded 00:29:13.639 --> 00:29:13.649 align:start position:0% function and their corresponding encoded 00:29:13.649 --> 00:29:16.549 align:start position:0% function and their corresponding encoded value<00:29:13.889> to<00:29:14.279> four-fight<00:29:14.789> encoding<00:29:15.600> and<00:29:15.840> then 00:29:16.549 --> 00:29:16.559 align:start position:0% value to four-fight encoding and then 00:29:16.559 --> 00:29:18.769 align:start position:0% value to four-fight encoding and then that<00:29:16.799> way<00:29:16.980> they<00:29:17.369> could<00:29:17.580> be<00:29:17.700> a<00:29:17.970> wallet<00:29:18.480> could 00:29:18.769 --> 00:29:18.779 align:start position:0% that way they could be a wallet could 00:29:18.779 --> 00:29:22.070 align:start position:0% that way they could be a wallet could decode<00:29:19.230> the<00:29:19.470> function<00:29:20.450> but<00:29:21.450> you<00:29:21.570> want<00:29:21.809> you 00:29:22.070 --> 00:29:22.080 align:start position:0% decode the function but you want you 00:29:22.080 --> 00:29:24.049 align:start position:0% decode the function but you want you wouldn't<00:29:22.409> have<00:29:22.619> published<00:29:23.519> a<00:29:23.639> person<00:29:23.970> of 00:29:24.049 --> 00:29:24.059 align:start position:0% wouldn't have published a person of 00:29:24.059 --> 00:29:25.710 align:start position:0% wouldn't have published a person of source<00:29:24.269> code<00:29:24.539> but<00:29:24.659> not<00:29:24.809> the 00:29:25.710 --> 00:29:25.720 align:start position:0% source code but not the 00:29:25.720 --> 00:29:27.420 align:start position:0% source code but not the eventually<00:29:26.470> published<00:29:26.680> something<00:29:27.220> that's 00:29:27.420 --> 00:29:27.430 align:start position:0% eventually published something that's 00:29:27.430 --> 00:29:33.510 align:start position:0% eventually published something that's public<00:29:27.910> anyway<00:29:28.440> so<00:29:31.860> you<00:29:32.860> can<00:29:32.890> even<00:29:33.310> publish 00:29:33.510 --> 00:29:33.520 align:start position:0% public anyway so you can even publish 00:29:33.520 --> 00:29:35.130 align:start position:0% public anyway so you can even publish the<00:29:33.790> meat<00:29:33.940> identify<00:29:34.420> with<00:29:34.630> all<00:29:34.780> the<00:29:34.930> source 00:29:35.130 --> 00:29:35.140 align:start position:0% the meat identify with all the source 00:29:35.140 --> 00:29:36.420 align:start position:0% the meat identify with all the source code<00:29:35.220> yeah 00:29:36.420 --> 00:29:36.430 align:start position:0% code yeah 00:29:36.430 --> 00:29:38.190 align:start position:0% code yeah then<00:29:36.610> you<00:29:36.970> have<00:29:37.150> I<00:29:37.330> mean<00:29:37.360> that<00:29:37.630> also<00:29:37.870> includes 00:29:38.190 --> 00:29:38.200 align:start position:0% then you have I mean that also includes 00:29:38.200 --> 00:29:42.330 align:start position:0% then you have I mean that also includes net<00:29:38.380> spec<00:29:38.620> which<00:29:38.950> might<00:29:39.550> be<00:29:39.820> sensitive<00:29:41.160> yes<00:29:42.160> I 00:29:42.330 --> 00:29:42.340 align:start position:0% net spec which might be sensitive yes I 00:29:42.340 --> 00:29:44.550 align:start position:0% net spec which might be sensitive yes I mean<00:29:42.460> anything<00:29:43.180> is<00:29:43.330> elevated<00:29:43.870> you<00:29:43.990> just<00:29:44.200> go<00:29:44.410> in 00:29:44.550 --> 00:29:44.560 align:start position:0% mean anything is elevated you just go in 00:29:44.560 --> 00:29:46.320 align:start position:0% mean anything is elevated you just go in there<00:29:44.680> by<00:29:44.890> coding<00:29:45.370> you<00:29:45.520> look<00:29:45.760> at<00:29:45.880> the<00:29:45.970> function 00:29:46.320 --> 00:29:46.330 align:start position:0% there by coding you look at the function 00:29:46.330 --> 00:29:48.540 align:start position:0% there by coding you look at the function selector<00:29:46.810> so<00:29:47.080> we're<00:29:47.740> not<00:29:47.860> anyone 00:29:48.540 --> 00:29:48.550 align:start position:0% selector so we're not anyone 00:29:48.550 --> 00:29:52.350 align:start position:0% selector so we're not anyone I'm<00:29:49.540> very<00:29:50.260> technical<00:29:50.920> but<00:29:51.160> you'd<00:29:51.730> be<00:29:52.030> helping 00:29:52.350 --> 00:29:52.360 align:start position:0% I'm very technical but you'd be helping 00:29:52.360 --> 00:29:56.220 align:start position:0% I'm very technical but you'd be helping the<00:29:52.480> non<00:29:52.690> the<00:29:53.080> less<00:29:53.110> technical<00:29:54.960> is<00:29:55.960> there<00:29:56.200> a 00:29:56.220 --> 00:29:56.230 align:start position:0% the non the less technical is there a 00:29:56.230 --> 00:30:00.390 align:start position:0% the non the less technical is there a way<00:29:56.500> to<00:29:56.560> I<00:29:57.600> mean<00:29:58.600> if<00:29:59.320> the<00:29:59.590> deployment<00:29:59.980> process 00:30:00.390 --> 00:30:00.400 align:start position:0% way to I mean if the deployment process 00:30:00.400 --> 00:30:04.020 align:start position:0% way to I mean if the deployment process is<00:30:00.640> an<00:30:00.940> interactive<00:30:01.480> process<00:30:01.660> then<00:30:02.760> that<00:30:03.760> tool 00:30:04.020 --> 00:30:04.030 align:start position:0% is an interactive process then that tool 00:30:04.030 --> 00:30:05.940 align:start position:0% is an interactive process then that tool could<00:30:04.240> also<00:30:04.420> just<00:30:04.690> ask<00:30:04.990> where<00:30:05.350> you<00:30:05.470> have<00:30:05.710> to 00:30:05.940 --> 00:30:05.950 align:start position:0% could also just ask where you have to 00:30:05.950 --> 00:30:10.920 align:start position:0% could also just ask where you have to answer<00:30:06.340> with<00:30:06.430> yes<00:30:06.580> or<00:30:06.760> no<00:30:08.040> yeah<00:30:09.720> like<00:30:10.720> in<00:30:10.840> an 00:30:10.920 --> 00:30:10.930 align:start position:0% answer with yes or no yeah like in an 00:30:10.930 --> 00:30:12.750 align:start position:0% answer with yes or no yeah like in an interactive<00:30:11.410> process<00:30:11.560> yeah<00:30:11.950> but<00:30:12.220> it's<00:30:12.640> just 00:30:12.750 --> 00:30:12.760 align:start position:0% interactive process yeah but it's just 00:30:12.760 --> 00:30:18.030 align:start position:0% interactive process yeah but it's just scripting<00:30:13.570> and<00:30:13.690> dancer<00:30:14.200> burden<00:30:16.860> if<00:30:17.860> you're 00:30:18.030 --> 00:30:18.040 align:start position:0% scripting and dancer burden if you're 00:30:18.040 --> 00:30:19.980 align:start position:0% scripting and dancer burden if you're developing<00:30:18.370> something<00:30:18.880> sensible<00:30:19.540> and<00:30:19.900> you 00:30:19.980 --> 00:30:19.990 align:start position:0% developing something sensible and you 00:30:19.990 --> 00:30:22.380 align:start position:0% developing something sensible and you forget<00:30:20.440> to<00:30:20.620> check<00:30:21.040> the<00:30:21.190> box<00:30:21.490> probably 00:30:22.380 --> 00:30:22.390 align:start position:0% forget to check the box probably 00:30:22.390 --> 00:30:59.159 align:start position:0% forget to check the box probably shouldn't<00:30:22.960> be<00:30:23.140> developing<00:30:23.760> sensors 00:30:59.159 --> 00:30:59.169 align:start position:0% 00:30:59.169 --> 00:31:03.159 align:start position:0% reading<00:31:00.169> functional<00:31:00.710> stuff<00:31:00.980> I<00:31:01.929> couldn't 00:31:03.159 --> 00:31:03.169 align:start position:0% reading functional stuff I couldn't 00:31:03.169 --> 00:31:05.220 align:start position:0% reading functional stuff I couldn't I<00:31:03.289> think<00:31:03.470> you<00:31:03.530> should<00:31:03.679> just<00:31:03.830> pay<00:31:04.130> them 00:31:05.220 --> 00:31:05.230 align:start position:0% I think you should just pay them 00:31:05.230 --> 00:31:10.360 align:start position:0% I think you should just pay them security<00:31:06.230> we<00:31:06.350> would<00:31:06.440> play<00:31:06.650> everyone<00:31:09.370> but 00:31:10.360 --> 00:31:10.370 align:start position:0% security we would play everyone but 00:31:10.370 --> 00:31:11.680 align:start position:0% security we would play everyone but where<00:31:10.520> is<00:31:10.610> the<00:31:10.760> problem<00:31:10.970> I<00:31:11.210> mean<00:31:11.360> I<00:31:11.390> think 00:31:11.680 --> 00:31:11.690 align:start position:0% where is the problem I mean I think 00:31:11.690 --> 00:31:13.840 align:start position:0% where is the problem I mean I think that's<00:31:11.840> like<00:31:11.990> education<00:31:12.770> without<00:31:12.950> it<00:31:13.400> people 00:31:13.840 --> 00:31:13.850 align:start position:0% that's like education without it people 00:31:13.850 --> 00:31:16.419 align:start position:0% that's like education without it people just<00:31:14.240> knew<00:31:14.450> that<00:31:14.659> this<00:31:14.750> is<00:31:14.929> important<00:31:15.440> they 00:31:16.419 --> 00:31:16.429 align:start position:0% just knew that this is important they 00:31:16.429 --> 00:31:18.370 align:start position:0% just knew that this is important they could<00:31:16.640> win<00:31:16.850> it<00:31:17.059> or<00:31:17.270> it's<00:31:17.659> like<00:31:17.960> to<00:31:18.110> make<00:31:18.230> it 00:31:18.370 --> 00:31:18.380 align:start position:0% could win it or it's like to make it 00:31:18.380 --> 00:31:22.480 align:start position:0% could win it or it's like to make it easier<00:31:18.710> by<00:31:19.159> the<00:31:19.960> really<00:31:20.960> good<00:31:21.140> so<00:31:21.679> it's<00:31:22.250> just 00:31:22.480 --> 00:31:22.490 align:start position:0% easier by the really good so it's just 00:31:22.490 --> 00:31:23.980 align:start position:0% easier by the really good so it's just easier<00:31:22.850> because<00:31:23.030> people<00:31:23.539> have<00:31:23.630> a<00:31:23.720> lot<00:31:23.870> of 00:31:23.980 --> 00:31:23.990 align:start position:0% easier because people have a lot of 00:31:23.990 --> 00:31:27.310 align:start position:0% easier because people have a lot of things<00:31:24.200> to<00:31:24.350> do<00:31:24.440> I<00:31:24.500> understand<00:31:25.630> and<00:31:26.630> it's<00:31:27.110> just 00:31:27.310 --> 00:31:27.320 align:start position:0% things to do I understand and it's just 00:31:27.320 --> 00:31:29.680 align:start position:0% things to do I understand and it's just an<00:31:27.440> extra<00:31:27.799> step<00:31:27.830> and<00:31:28.280> they<00:31:29.000> were<00:31:29.299> kind<00:31:29.570> of 00:31:29.680 --> 00:31:29.690 align:start position:0% an extra step and they were kind of 00:31:29.690 --> 00:31:32.500 align:start position:0% an extra step and they were kind of finished<00:31:30.020> about<00:31:30.350> there's<00:31:30.620> an<00:31:30.740> extra<00:31:31.070> step<00:31:31.510> so 00:31:32.500 --> 00:31:32.510 align:start position:0% finished about there's an extra step so 00:31:32.510 --> 00:31:38.480 align:start position:0% finished about there's an extra step so it<00:31:32.570> would<00:31:32.720> be<00:31:32.870> nice<00:31:33.679> if<00:31:33.710> it<00:31:34.010> gets<00:31:34.220> just<00:31:34.490> easier 00:31:38.480 --> 00:31:38.490 align:start position:0% 00:31:38.490 --> 00:31:41.630 align:start position:0% and<00:31:39.120> ideally<00:31:39.560> that<00:31:40.560> give<00:31:40.800> up<00:31:40.980> our<00:31:41.220> soul 00:31:41.630 --> 00:31:41.640 align:start position:0% and ideally that give up our soul 00:31:41.640 --> 00:31:53.720 align:start position:0% and ideally that give up our soul medically<00:31:42.570> transition<00:31:43.080> phase<00:31:43.490> the<00:31:44.490> first<00:31:52.730> in 00:31:53.720 --> 00:31:53.730 align:start position:0% medically transition phase the first in 00:31:53.730 --> 00:31:56.600 align:start position:0% medically transition phase the first in the<00:31:53.850> content<00:31:54.270> like<00:31:54.860> everybody's<00:31:55.860> like<00:31:56.340> used 00:31:56.600 --> 00:31:56.610 align:start position:0% the content like everybody's like used 00:31:56.610 --> 00:31:58.400 align:start position:0% the content like everybody's like used to<00:31:56.730> that<00:31:56.850> like<00:31:57.030> allosteric<00:31:57.750> on<00:31:57.990> dislike 00:31:58.400 --> 00:31:58.410 align:start position:0% to that like allosteric on dislike 00:31:58.410 --> 00:32:01.430 align:start position:0% to that like allosteric on dislike playing<00:31:59.010> visible<00:31:59.760> but<00:32:00.000> like<00:32:00.150> when<00:32:00.390> comes<00:32:00.660> back 00:32:01.430 --> 00:32:01.440 align:start position:0% playing visible but like when comes back 00:32:01.440 --> 00:32:03.950 align:start position:0% playing visible but like when comes back ends<00:32:01.770> there<00:32:02.490> was<00:32:02.640> never<00:32:03.240> the<00:32:03.450> case 00:32:03.950 --> 00:32:03.960 align:start position:0% ends there was never the case 00:32:03.960 --> 00:32:07.700 align:start position:0% ends there was never the case and<00:32:04.280> now<00:32:05.280> not<00:32:06.270> changing<00:32:06.720> or<00:32:06.900> smart<00:32:07.230> contracts 00:32:07.700 --> 00:32:07.710 align:start position:0% and now not changing or smart contracts 00:32:07.710 --> 00:32:14.650 align:start position:0% and now not changing or smart contracts and<00:32:08.210> new 00:32:14.650 --> 00:32:14.660 align:start position:0% 00:32:14.660 --> 00:32:17.140 align:start position:0% we<00:32:15.410> mentioned<00:32:15.710> that<00:32:15.770> function<00:32:16.700> is<00:32:16.910> being 00:32:17.140 --> 00:32:17.150 align:start position:0% we mentioned that function is being 00:32:17.150 --> 00:32:21.220 align:start position:0% we mentioned that function is being displayed<00:32:17.530> there's<00:32:18.530> an<00:32:19.360> optimization<00:32:20.360> and 00:32:21.220 --> 00:32:21.230 align:start position:0% displayed there's an optimization and 00:32:21.230 --> 00:32:23.380 align:start position:0% displayed there's an optimization and compiler<00:32:21.620> which<00:32:21.830> will<00:32:21.980> just<00:32:22.160> reduce<00:32:22.309> the<00:32:23.090> size 00:32:23.380 --> 00:32:23.390 align:start position:0% compiler which will just reduce the size 00:32:23.390 --> 00:32:24.760 align:start position:0% compiler which will just reduce the size of<00:32:23.419> your<00:32:23.570> contract<00:32:23.960> by<00:32:24.080> taking<00:32:24.350> the<00:32:24.440> contract 00:32:24.760 --> 00:32:24.770 align:start position:0% of your contract by taking the contract 00:32:24.770 --> 00:32:26.470 align:start position:0% of your contract by taking the contract names<00:32:24.950> Act<00:32:25.160> that's<00:32:25.700> what<00:32:25.940> the<00:32:26.030> function<00:32:26.299> names 00:32:26.470 --> 00:32:26.480 align:start position:0% names Act that's what the function names 00:32:26.480 --> 00:32:29.049 align:start position:0% names Act that's what the function names are<00:32:26.660> so<00:32:27.410> people<00:32:28.160> start<00:32:28.429> turning<00:32:28.640> them<00:32:28.730> on<00:32:28.880> to 00:32:29.049 --> 00:32:29.059 align:start position:0% are so people start turning them on to 00:32:29.059 --> 00:32:31.450 align:start position:0% are so people start turning them on to save<00:32:29.210> on<00:32:29.360> gas<00:32:29.539> or<00:32:29.900> ugly<00:32:30.320> so<00:32:30.950> you<00:32:31.010> can't<00:32:31.340> really 00:32:31.450 --> 00:32:31.460 align:start position:0% save on gas or ugly so you can't really 00:32:31.460 --> 00:32:34.870 align:start position:0% save on gas or ugly so you can't really rely<00:32:31.730> on<00:32:32.049> was<00:32:33.049> a<00:32:33.309> function<00:32:34.309> in<00:32:34.400> support<00:32:34.730> of<00:32:34.760> the 00:32:34.870 --> 00:32:34.880 align:start position:0% rely on was a function in support of the 00:32:34.880 --> 00:32:36.930 align:start position:0% rely on was a function in support of the English<00:32:35.330> so<00:32:35.870> these<00:32:36.020> French<00:32:36.350> we<00:32:36.559> don't 00:32:36.930 --> 00:32:36.940 align:start position:0% English so these French we don't 00:32:36.940 --> 00:32:39.970 align:start position:0% English so these French we don't understand<00:32:37.940> it<00:32:38.299> comes<00:32:38.840> up<00:32:39.020> into<00:32:39.230> false<00:32:39.590> in<00:32:39.860> the 00:32:39.970 --> 00:32:39.980 align:start position:0% understand it comes up into false in the 00:32:39.980 --> 00:32:42.250 align:start position:0% understand it comes up into false in the end<00:32:40.130> like<00:32:40.340> what's<00:32:41.059> all<00:32:41.240> because<00:32:41.480> 90%<00:32:41.900> of 00:32:42.250 --> 00:32:42.260 align:start position:0% end like what's all because 90% of 00:32:42.260 --> 00:32:44.440 align:start position:0% end like what's all because 90% of people<00:32:42.410> probably<00:32:42.799> wouldn't<00:32:43.130> choose<00:32:44.030> to<00:32:44.059> do 00:32:44.440 --> 00:32:44.450 align:start position:0% people probably wouldn't choose to do 00:32:44.450 --> 00:32:46.270 align:start position:0% people probably wouldn't choose to do those<00:32:44.630> types<00:32:45.080> of<00:32:45.200> things<00:32:45.440> so<00:32:45.530> it<00:32:46.160> would 00:32:46.270 --> 00:32:46.280 align:start position:0% those types of things so it would 00:32:46.280 --> 00:32:47.710 align:start position:0% those types of things so it would improve<00:32:46.640> the<00:32:46.850> situation 00:32:47.710 --> 00:32:47.720 align:start position:0% improve the situation 00:32:47.720 --> 00:32:50.710 align:start position:0% improve the situation yeah<00:32:48.110> this<00:32:49.070> Way's<00:32:49.220> whatever<00:32:49.610> we're<00:32:50.539> not 00:32:50.710 --> 00:32:50.720 align:start position:0% yeah this Way's whatever we're not 00:32:50.720 --> 00:32:52.659 align:start position:0% yeah this Way's whatever we're not having<00:32:50.990> something<00:32:51.200> like<00:32:51.350> them<00:32:51.620> about<00:32:52.580> the 00:32:52.659 --> 00:32:52.669 align:start position:0% having something like them about the 00:32:52.669 --> 00:32:54.370 align:start position:0% having something like them about the secret<00:32:53.000> sauce<00:32:53.179> tackle<00:32:53.750> something<00:32:53.929> like<00:32:54.169> that 00:32:54.370 --> 00:32:54.380 align:start position:0% secret sauce tackle something like that 00:32:54.380 --> 00:32:56.850 align:start position:0% secret sauce tackle something like that where<00:32:54.650> when<00:32:55.250> you're<00:32:55.309> writing<00:32:55.520> the<00:32:55.669> code 00:32:56.850 --> 00:32:56.860 align:start position:0% where when you're writing the code 00:32:56.860 --> 00:32:58.799 align:start position:0% where when you're writing the code beause<00:32:57.280> this<00:32:57.850> money<00:32:58.120> in<00:32:58.240> the<00:32:58.330> secret<00:32:58.630> sauce 00:32:58.799 --> 00:32:58.809 align:start position:0% beause this money in the secret sauce 00:32:58.809 --> 00:33:02.549 align:start position:0% beause this money in the secret sauce okay<00:32:59.500> it's<00:33:00.040> it's<00:33:00.490> closed<00:33:00.850> yeah<00:33:01.630> it<00:33:01.900> has<00:33:02.049> I 00:33:02.549 --> 00:33:02.559 align:start position:0% okay it's it's closed yeah it has I 00:33:02.559 --> 00:33:04.680 align:start position:0% okay it's it's closed yeah it has I thought<00:33:02.770> we<00:33:02.860> can't<00:33:03.100> reveal<00:33:03.460> this<00:33:03.700> so<00:33:04.299> I<00:33:04.510> just 00:33:04.680 --> 00:33:04.690 align:start position:0% thought we can't reveal this so I just 00:33:04.690 --> 00:33:07.650 align:start position:0% thought we can't reveal this so I just wanna<00:33:04.990> see<00:33:05.170> what<00:33:05.320> sort<00:33:05.530> of<00:33:06.090> a<00:33:07.090> kind<00:33:07.360> of<00:33:07.420> a<00:33:07.480> whole 00:33:07.650 --> 00:33:07.660 align:start position:0% wanna see what sort of a kind of a whole 00:33:07.660 --> 00:33:19.020 align:start position:0% wanna see what sort of a kind of a whole contract<00:33:12.900> developer<00:33:17.429> observing<00:33:18.429> so<00:33:18.790> you<00:33:18.880> can 00:33:19.020 --> 00:33:19.030 align:start position:0% contract developer observing so you can 00:33:19.030 --> 00:33:24.990 align:start position:0% contract developer observing so you can actually<00:33:22.890> declared<00:33:23.890> as<00:33:24.190> there's<00:33:24.670> a<00:33:24.790> few 00:33:24.990 --> 00:33:25.000 align:start position:0% actually declared as there's a few 00:33:25.000 --> 00:33:42.430 align:start position:0% actually declared as there's a few reason<00:33:25.390> why<00:33:25.510> is<00:33:26.410> because<00:33:27.780> it's<00:33:28.780> amazing 00:33:42.430 --> 00:33:42.440 align:start position:0% 00:33:42.440 --> 00:34:03.519 align:start position:0% [Music] 00:34:03.519 --> 00:34:03.529 align:start position:0% 00:34:03.529 --> 00:34:07.070 align:start position:0% website<00:34:04.529> and<00:34:05.070> with<00:34:05.580> we<00:34:06.269> upload<00:34:06.869> to<00:34:06.899> the 00:34:07.070 --> 00:34:07.080 align:start position:0% website and with we upload to the 00:34:07.080 --> 00:34:15.649 align:start position:0% website and with we upload to the website<00:34:07.470> we<00:34:07.590> can<00:34:07.799> use<00:34:08.010> the<00:34:13.879> and<00:34:14.879> then<00:34:15.179> with<00:34:15.480> a 00:34:15.649 --> 00:34:15.659 align:start position:0% website we can use the and then with a 00:34:15.659 --> 00:34:18.649 align:start position:0% website we can use the and then with a decoy<00:34:16.169> and<00:34:16.470> they<00:34:16.919> can<00:34:17.220> they<00:34:17.940> also<00:34:18.119> use<00:34:18.450> the 00:34:18.649 --> 00:34:18.659 align:start position:0% decoy and they can they also use the 00:34:18.659 --> 00:34:24.139 align:start position:0% decoy and they can they also use the harm<00:34:18.899> the<00:34:19.169> harsh<00:34:20.690> and<00:34:22.639> detect<00:34:23.639> whether<00:34:23.909> the 00:34:24.139 --> 00:34:24.149 align:start position:0% harm the harsh and detect whether the 00:34:24.149 --> 00:34:26.030 align:start position:0% harm the harsh and detect whether the loan<00:34:24.359> nicole<00:34:24.869> has<00:34:25.020> been<00:34:25.230> published 00:34:26.030 --> 00:34:26.040 align:start position:0% loan nicole has been published 00:34:26.040 --> 00:34:29.359 align:start position:0% loan nicole has been published if<00:34:26.220> yes<00:34:26.639> we<00:34:26.970> can<00:34:27.179> say<00:34:27.419> where<00:34:28.319> you<00:34:28.530> you<00:34:28.980> can<00:34:29.190> use 00:34:29.359 --> 00:34:29.369 align:start position:0% if yes we can say where you you can use 00:34:29.369 --> 00:35:20.390 align:start position:0% if yes we can say where you you can use the<00:34:29.579> building<00:34:30.240> as<00:34:30.710> sent<00:34:31.710> to<00:34:31.889> the<00:34:32.899> smoke<00:34:33.899> option 00:35:20.390 --> 00:35:20.400 align:start position:0% 00:35:20.400 --> 00:35:24.260 align:start position:0% so<00:35:21.400> not<00:35:21.700> only<00:35:21.730> Jesus<00:35:22.240> can<00:35:22.450> help<00:35:22.690> sense<00:35:22.990> I 00:35:24.260 --> 00:35:24.270 align:start position:0% so not only Jesus can help sense I 00:35:24.270 --> 00:35:26.220 align:start position:0% so not only Jesus can help sense I suppose 00:35:26.220 --> 00:35:26.230 align:start position:0% suppose 00:35:26.230 --> 00:35:28.950 align:start position:0% suppose so<00:35:26.619> what<00:35:26.859> was<00:35:27.130> it<00:35:27.250> provides<00:35:27.609> for<00:35:27.819> users<00:35:28.180> we 00:35:28.950 --> 00:35:28.960 align:start position:0% so what was it provides for users we 00:35:28.960 --> 00:35:48.400 align:start position:0% so what was it provides for users we have<00:35:28.990> you 00:35:48.400 --> 00:35:48.410 align:start position:0% 00:35:48.410 --> 00:35:54.590 align:start position:0% and<00:35:49.640> so<00:35:51.440> we<00:35:52.440> and<00:35:53.060> compatibility<00:35:54.060> will<00:35:54.360> fight 00:35:54.590 --> 00:35:54.600 align:start position:0% and so we and compatibility will fight 00:35:54.600 --> 00:35:56.330 align:start position:0% and so we and compatibility will fight and<00:35:54.870> that<00:35:55.020> would<00:35:55.170> centralized<00:35:55.680> database<00:35:56.160> but 00:35:56.330 --> 00:35:56.340 align:start position:0% and that would centralized database but 00:35:56.340 --> 00:35:58.550 align:start position:0% and that would centralized database but what<00:35:56.550> is<00:35:56.670> more<00:35:56.880> important<00:35:57.420> we<00:35:57.780> have<00:35:58.380> been 00:35:58.550 --> 00:35:58.560 align:start position:0% what is more important we have been 00:35:58.560 --> 00:36:02.830 align:start position:0% what is more important we have been going<00:35:58.860> to<00:35:59.160> get<00:35:59.370> all<00:35:59.640> these<00:35:59.940> contracts<00:36:00.570> and<00:36:00.720> we 00:36:02.830 --> 00:36:02.840 align:start position:0% going to get all these contracts and we 00:36:02.840 --> 00:36:06.710 align:start position:0% going to get all these contracts and we have<00:36:03.840> no<00:36:03.990> records<00:36:04.590> so<00:36:05.390> this<00:36:06.390> means<00:36:06.630> that 00:36:06.710 --> 00:36:06.720 align:start position:0% have no records so this means that 00:36:06.720 --> 00:36:09.890 align:start position:0% have no records so this means that everyone<00:36:07.440> can<00:36:07.950> can<00:36:08.370> get<00:36:08.610> the<00:36:08.820> copy<00:36:09.120> of<00:36:09.510> works 00:36:09.890 --> 00:36:09.900 align:start position:0% everyone can can get the copy of works 00:36:09.900 --> 00:36:19.510 align:start position:0% everyone can can get the copy of works counted<00:36:10.530> get<00:36:10.920> verified<00:36:11.400> source<00:36:15.050> coronation 00:36:19.510 --> 00:36:19.520 align:start position:0% 00:36:19.520 --> 00:36:23.090 align:start position:0% ten<00:36:20.520> thousands<00:36:21.030> of<00:36:21.680> contract<00:36:22.680> something<00:36:22.830> like 00:36:23.090 --> 00:36:23.100 align:start position:0% ten thousands of contract something like 00:36:23.100 --> 00:36:28.370 align:start position:0% ten thousands of contract something like that<00:36:23.660> yes<00:36:25.730> and<00:36:26.730> everyone<00:36:27.120> is<00:36:27.840> in<00:36:27.990> one<00:36:28.140> part 00:36:28.370 --> 00:36:28.380 align:start position:0% that yes and everyone is in one part 00:36:28.380 --> 00:36:30.170 align:start position:0% that yes and everyone is in one part that<00:36:28.440> everyone<00:36:28.920> can<00:36:29.250> get<00:36:29.400> this<00:36:29.580> is<00:36:29.790> so<00:36:29.940> this<00:36:30.120> is 00:36:30.170 --> 00:36:30.180 align:start position:0% that everyone can get this is so this is 00:36:30.180 --> 00:36:33.530 align:start position:0% that everyone can get this is so this is our<00:36:30.690> current<00:36:31.650> vision<00:36:32.130> of<00:36:32.540> decimalisation 00:36:33.530 --> 00:36:33.540 align:start position:0% our current vision of decimalisation 00:36:33.540 --> 00:36:35.780 align:start position:0% our current vision of decimalisation right<00:36:33.810> so<00:36:34.080> everyone<00:36:34.800> can<00:36:35.070> physically<00:36:35.610> power 00:36:35.780 --> 00:36:35.790 align:start position:0% right so everyone can physically power 00:36:35.790 --> 00:36:39.140 align:start position:0% right so everyone can physically power database<00:36:36.300> so<00:36:37.430> but<00:36:38.430> what<00:36:38.610> it<00:36:38.760> was<00:36:38.910> we<00:36:39.030> would 00:36:39.140 --> 00:36:39.150 align:start position:0% database so but what it was we would 00:36:39.150 --> 00:36:57.380 align:start position:0% database so but what it was we would like<00:36:39.300> to<00:36:39.330> it 00:36:57.380 --> 00:36:57.390 align:start position:0% 00:36:57.390 --> 00:37:23.910 align:start position:0% in<00:36:58.390> order<00:36:58.930> to<00:36:59.109> increase<00:37:21.359> tourism<00:37:22.359> meet<00:37:23.349> you<00:37:23.619> on 00:37:23.910 --> 00:37:23.920 align:start position:0% in order to increase tourism meet you on 00:37:23.920 --> 00:37:26.640 align:start position:0% in order to increase tourism meet you on forums<00:37:24.339> somewhere<00:37:24.880> else<00:37:25.060> how<00:37:25.660> to<00:37:25.690> verify<00:37:26.140> how 00:37:26.640 --> 00:37:26.650 align:start position:0% forums somewhere else how to verify how 00:37:26.650 --> 00:37:30.240 align:start position:0% forums somewhere else how to verify how how<00:37:27.099> is<00:37:27.250> it<00:37:27.369> easy<00:37:28.080> what<00:37:29.099> instruments<00:37:30.099> we<00:37:30.220> can 00:37:30.240 --> 00:37:30.250 align:start position:0% how is it easy what instruments we can 00:37:30.250 --> 00:37:35.339 align:start position:0% how is it easy what instruments we can use<00:37:30.490> for<00:37:30.900> verification<00:37:31.900> the<00:37:32.830> second<00:37:33.190> one<00:37:34.349> is 00:37:35.339 --> 00:37:35.349 align:start position:0% use for verification the second one is 00:37:35.349 --> 00:37:37.170 align:start position:0% use for verification the second one is based<00:37:35.800> on<00:37:35.980> assumption<00:37:36.460> this<00:37:36.609> user<00:37:36.820> will 00:37:37.170 --> 00:37:37.180 align:start position:0% based on assumption this user will 00:37:37.180 --> 00:37:42.180 align:start position:0% based on assumption this user will always<00:37:37.900> forget<00:37:38.260> to<00:37:38.470> verify<00:37:38.950> says<00:37:41.010> thus<00:37:42.010> we 00:37:42.180 --> 00:37:42.190 align:start position:0% always forget to verify says thus we 00:37:42.190 --> 00:37:46.050 align:start position:0% always forget to verify says thus we need<00:37:42.339> to<00:37:42.839> somehow<00:37:43.839> to<00:37:44.080> invent<00:37:44.710> a<00:37:45.060> verification 00:37:46.050 --> 00:37:46.060 align:start position:0% need to somehow to invent a verification 00:37:46.060 --> 00:37:48.480 align:start position:0% need to somehow to invent a verification step<00:37:46.359> in<00:37:46.599> to<00:37:47.050> say<00:37:47.200> all<00:37:47.410> development<00:37:47.980> tools<00:37:48.220> we 00:37:48.480 --> 00:37:48.490 align:start position:0% step in to say all development tools we 00:37:48.490 --> 00:37:53.240 align:start position:0% step in to say all development tools we have<00:37:49.680> disco<00:37:50.680> publications<00:37:51.339> like<00:37:51.570> bangkok 00:37:53.240 --> 00:37:53.250 align:start position:0% have disco publications like bangkok 00:37:53.250 --> 00:37:57.750 align:start position:0% have disco publications like bangkok brahmam<00:37:54.480> reason<00:37:55.480> life<00:37:55.660> so<00:37:56.290> to<00:37:57.250> develop 00:37:57.750 --> 00:37:57.760 align:start position:0% brahmam reason life so to develop 00:37:57.760 --> 00:37:58.530 align:start position:0% brahmam reason life so to develop vacations 00:37:58.530 --> 00:37:58.540 align:start position:0% vacations 00:37:58.540 --> 00:38:11.240 align:start position:0% vacations release<00:37:58.900> a<00:37:59.320> right 00:38:11.240 --> 00:38:11.250 align:start position:0% 00:38:11.250 --> 00:38:14.670 align:start position:0% as<00:38:12.250> soon<00:38:12.580> as<00:38:12.850> you<00:38:13.120> publish<00:38:13.660> metadata<00:38:14.290> and 00:38:14.670 --> 00:38:14.680 align:start position:0% as soon as you publish metadata and 00:38:14.680 --> 00:38:17.010 align:start position:0% as soon as you publish metadata and source<00:38:14.920> code<00:38:15.210> verification<00:38:16.210> automatic 00:38:17.010 --> 00:38:17.020 align:start position:0% source code verification automatic 00:38:17.020 --> 00:38:23.460 align:start position:0% source code verification automatic you've<00:38:17.110> done<00:38:17.290> an<00:38:17.380> additional<00:38:17.740> seven<00:38:22.470> swarm 00:38:23.460 --> 00:38:23.470 align:start position:0% you've done an additional seven swarm 00:38:23.470 --> 00:38:29.490 align:start position:0% you've done an additional seven swarm and<00:38:23.590> ftfs<00:38:24.090> yes<00:38:25.860> and<00:38:27.510> that's<00:38:28.510> also<00:38:28.660> the<00:38:28.840> hope<00:38:29.260> so 00:38:29.490 --> 00:38:29.500 align:start position:0% and ftfs yes and that's also the hope so 00:38:29.500 --> 00:38:32.490 align:start position:0% and ftfs yes and that's also the hope so as<00:38:29.890> soon<00:38:30.040> as<00:38:30.160> we<00:38:30.280> publish<00:38:30.850> this<00:38:31.030> then<00:38:31.780> block 00:38:32.490 --> 00:38:32.500 align:start position:0% as soon as we publish this then block 00:38:32.500 --> 00:38:34.950 align:start position:0% as soon as we publish this then block explore<00:38:32.860> us<00:38:33.240> so<00:38:34.240> you<00:38:34.330> don't<00:38:34.360> need<00:38:34.690> to<00:38:34.780> go<00:38:34.900> to 00:38:34.950 --> 00:38:34.960 align:start position:0% explore us so you don't need to go to 00:38:34.960 --> 00:38:36.900 align:start position:0% explore us so you don't need to go to the<00:38:35.140> block<00:38:35.260> Explorer<00:38:35.590> to<00:38:35.710> verify<00:38:36.070> your 00:38:36.900 --> 00:38:36.910 align:start position:0% the block Explorer to verify your 00:38:36.910 --> 00:38:44.280 align:start position:0% the block Explorer to verify your contract<00:38:37.330> the<00:38:37.420> block<00:38:37.600> is<00:38:37.720> quite<00:38:43.170> sure<00:38:44.170> the 00:38:44.280 --> 00:38:44.290 align:start position:0% contract the block is quite sure the 00:38:44.290 --> 00:38:57.390 align:start position:0% contract the block is quite sure the tools<00:38:44.470> need<00:38:44.650> that<00:38:54.840> are<00:38:55.840> like<00:38:56.350> our<00:38:56.920> thing<00:38:57.190> isn't 00:38:57.390 --> 00:38:57.400 align:start position:0% tools need that are like our thing isn't 00:38:57.400 --> 00:39:03.110 align:start position:0% tools need that are like our thing isn't so<00:38:57.580> good<00:39:00.390> useful<00:39:01.390> for<00:39:01.630> lot<00:39:01.780> of<00:39:01.840> these<00:39:01.900> problems 00:39:03.110 --> 00:39:03.120 align:start position:0% so good useful for lot of these problems 00:39:03.120 --> 00:39:08.460 align:start position:0% so good useful for lot of these problems it's<00:39:04.120> just<00:39:04.180> like<00:39:04.540> standardized<00:39:05.320> data<00:39:05.650> format 00:39:08.460 --> 00:39:08.470 align:start position:0% 00:39:08.470 --> 00:39:12.540 align:start position:0% like<00:39:08.619> the<00:39:08.859> source<00:39:09.190> to<00:39:09.460> ApS<00:39:10.440> also<00:39:11.550> specifies 00:39:12.540 --> 00:39:12.550 align:start position:0% like the source to ApS also specifies 00:39:12.550 --> 00:39:16.370 align:start position:0% like the source to ApS also specifies like<00:39:13.119> deployment<00:39:13.750> data<00:39:13.930> so<00:39:14.079> you<00:39:15.040> can<00:39:15.190> also 00:39:16.370 --> 00:39:16.380 align:start position:0% like deployment data so you can also 00:39:16.380 --> 00:39:18.210 align:start position:0% like deployment data so you can also determines<00:39:17.380> getting<00:39:17.589> this<00:39:17.650> like<00:39:17.859> strong 00:39:18.210 --> 00:39:18.220 align:start position:0% determines getting this like strong 00:39:18.220 --> 00:39:19.920 align:start position:0% determines getting this like strong verification<00:39:18.940> you<00:39:19.000> can<00:39:19.150> add<00:39:19.329> like<00:39:19.540> watching 00:39:19.920 --> 00:39:19.930 align:start position:0% verification you can add like watching 00:39:19.930 --> 00:39:21.630 align:start position:0% verification you can add like watching deployments<00:39:20.560> seeing<00:39:21.369> that<00:39:21.460> you're 00:39:21.630 --> 00:39:21.640 align:start position:0% deployments seeing that you're 00:39:21.640 --> 00:39:24.420 align:start position:0% deployments seeing that you're interacting<00:39:21.880> with<00:39:22.150> like<00:39:22.450> the<00:39:23.319> die<00:39:23.530> is<00:39:24.040> missing 00:39:24.420 --> 00:39:24.430 align:start position:0% interacting with like the die is missing 00:39:24.430 --> 00:39:28.410 align:start position:0% interacting with like the die is missing after<00:39:24.640> like<00:39:25.030> whoever's<00:39:25.450> wallet<00:39:25.810> address<00:39:27.420> and 00:39:28.410 --> 00:39:28.420 align:start position:0% after like whoever's wallet address and 00:39:28.420 --> 00:39:30.870 align:start position:0% after like whoever's wallet address and so<00:39:28.569> yeah<00:39:28.750> check<00:39:29.319> out<00:39:29.440> EPM<00:39:29.859> we're<00:39:30.130> in<00:39:30.369> brownie 00:39:30.870 --> 00:39:30.880 align:start position:0% so yeah check out EPM we're in brownie 00:39:30.880 --> 00:39:33.300 align:start position:0% so yeah check out EPM we're in brownie we're<00:39:31.329> in<00:39:31.540> remix<00:39:32.140> people<00:39:32.440> plug-in<00:39:32.829> bring 00:39:33.300 --> 00:39:33.310 align:start position:0% we're in remix people plug-in bring 00:39:33.310 --> 00:39:35.880 align:start position:0% we're in remix people plug-in bring truffle<00:39:33.880> it's<00:39:34.839> just<00:39:34.990> like<00:39:35.109> a<00:39:35.140> very<00:39:35.470> good<00:39:35.710> way 00:39:35.880 --> 00:39:35.890 align:start position:0% truffle it's just like a very good way 00:39:35.890 --> 00:39:38.970 align:start position:0% truffle it's just like a very good way to<00:39:35.920> pass<00:39:36.430> around<00:39:37.230> safely<00:39:38.230> your<00:39:38.710> smart 00:39:38.970 --> 00:39:38.980 align:start position:0% to pass around safely your smart 00:39:38.980 --> 00:39:44.490 align:start position:0% to pass around safely your smart contracts<00:39:39.780> love<00:39:40.780> to<00:39:40.900> see<00:39:41.050> more<00:39:41.290> integration 00:39:44.490 --> 00:39:44.500 align:start position:0% 00:39:44.500 --> 00:39:47.370 align:start position:0% Oh<00:39:45.210> website<00:39:46.210> documentation<00:39:47.020> never 00:39:47.370 --> 00:39:47.380 align:start position:0% Oh website documentation never 00:39:47.380 --> 00:39:56.760 align:start position:0% Oh website documentation never registered<00:39:54.690> isn't<00:39:55.690> one<00:39:55.840> way<00:39:55.960> to<00:39:56.020> do<00:39:56.260> it<00:39:56.290> to 00:39:56.760 --> 00:39:56.770 align:start position:0% registered isn't one way to do it to 00:39:56.770 --> 00:39:59.310 align:start position:0% registered isn't one way to do it to actually<00:39:57.070> have<00:39:57.250> the<00:39:57.400> you<00:39:58.000> directly<00:39:58.330> if<00:39:59.200> I'm 00:39:59.310 --> 00:39:59.320 align:start position:0% actually have the you directly if I'm 00:39:59.320 --> 00:40:03.120 align:start position:0% actually have the you directly if I'm able<00:39:59.470> to<00:39:59.650> build<00:40:00.480> that's<00:40:01.480> contract<00:40:02.080> and<00:40:02.950> it's 00:40:03.120 --> 00:40:03.130 align:start position:0% able to build that's contract and it's 00:40:03.130 --> 00:40:04.770 align:start position:0% able to build that's contract and it's by<00:40:03.280> Brandon<00:40:03.760> to<00:40:03.880> or<00:40:04.030> with<00:40:04.180> what's<00:40:04.420> deployed 00:40:04.770 --> 00:40:04.780 align:start position:0% by Brandon to or with what's deployed 00:40:04.780 --> 00:40:06.210 align:start position:0% by Brandon to or with what's deployed there<00:40:05.050> whether<00:40:05.170> they're<00:40:05.800> everything<00:40:05.980> about 00:40:06.210 --> 00:40:06.220 align:start position:0% there whether they're everything about 00:40:06.220 --> 00:40:09.090 align:start position:0% there whether they're everything about it<00:40:06.430> I<00:40:06.490> know<00:40:06.550> all<00:40:06.820> the<00:40:07.590> dependencies<00:40:08.590> and<00:40:08.950> stuff 00:40:09.090 --> 00:40:09.100 align:start position:0% it I know all the dependencies and stuff 00:40:09.100 --> 00:40:11.460 align:start position:0% it I know all the dependencies and stuff like<00:40:09.250> that<00:40:09.460> so<00:40:09.700> I<00:40:09.730> do<00:40:10.480> anything<00:40:10.810> officer<00:40:11.350> to 00:40:11.460 --> 00:40:11.470 align:start position:0% like that so I do anything officer to 00:40:11.470 --> 00:40:14.220 align:start position:0% like that so I do anything officer to verify<00:40:11.890> to<00:40:11.950> run<00:40:12.250> all<00:40:12.370> the<00:40:12.460> tests<00:40:12.990> and<00:40:13.990> to<00:40:14.110> do 00:40:14.220 --> 00:40:14.230 align:start position:0% verify to run all the tests and to do 00:40:14.230 --> 00:40:18.210 align:start position:0% verify to run all the tests and to do that<00:40:15.990> you<00:40:16.990> know<00:40:17.110> the<00:40:17.290> project<00:40:17.710> and<00:40:17.980> they<00:40:18.040> get 00:40:18.210 --> 00:40:18.220 align:start position:0% that you know the project and they get 00:40:18.220 --> 00:40:20.700 align:start position:0% that you know the project and they get convinced<00:40:19.000> that<00:40:19.600> I<00:40:19.720> could<00:40:19.750> get<00:40:20.020> that<00:40:20.170> code<00:40:20.410> and 00:40:20.700 --> 00:40:20.710 align:start position:0% convinced that I could get that code and 00:40:20.710 --> 00:40:22.740 align:start position:0% convinced that I could get that code and I<00:40:20.770> can<00:40:20.830> build<00:40:21.100> it<00:40:21.340> and<00:40:21.790> it's<00:40:22.060> exactly<00:40:22.390> what's 00:40:22.740 --> 00:40:22.750 align:start position:0% I can build it and it's exactly what's 00:40:22.750 --> 00:40:25.770 align:start position:0% I can build it and it's exactly what's deployed<00:40:23.110> I<00:40:23.500> can<00:40:24.190> do<00:40:24.280> anything<00:40:24.490> that<00:40:24.640> I<00:40:24.790> like 00:40:25.770 --> 00:40:25.780 align:start position:0% deployed I can do anything that I like 00:40:25.780 --> 00:40:28.650 align:start position:0% deployed I can do anything that I like there<00:40:26.280> we<00:40:27.280> have<00:40:27.490> a<00:40:27.520> great<00:40:28.120> one<00:40:28.270> of<00:40:28.330> the<00:40:28.420> big 00:40:28.650 --> 00:40:28.660 align:start position:0% there we have a great one of the big 00:40:28.660 --> 00:40:30.150 align:start position:0% there we have a great one of the big points<00:40:28.810> that<00:40:29.350> we<00:40:29.470> were<00:40:29.590> really<00:40:29.800> worried<00:40:30.100> about 00:40:30.150 --> 00:40:30.160 align:start position:0% points that we were really worried about 00:40:30.160 --> 00:40:33.090 align:start position:0% points that we were really worried about the<00:40:30.550> dependency<00:40:31.150> tax<00:40:31.420> some<00:40:31.840> changes<00:40:32.470> one<00:40:32.980> of 00:40:33.090 --> 00:40:33.100 align:start position:0% the dependency tax some changes one of 00:40:33.100 --> 00:40:35.820 align:start position:0% the dependency tax some changes one of the<00:40:33.220> libraries<00:40:33.790> that<00:40:33.820> we<00:40:34.030> use<00:40:34.360> it<00:40:35.260> gets<00:40:35.470> into 00:40:35.820 --> 00:40:35.830 align:start position:0% the libraries that we use it gets into 00:40:35.830 --> 00:40:38.520 align:start position:0% the libraries that we use it gets into our<00:40:35.860> cable<00:40:36.370> in<00:40:37.000> stealin<00:40:37.420> it's<00:40:37.870> a<00:40:37.960> guy<00:40:38.110> brings<00:40:38.380> a 00:40:38.520 --> 00:40:38.530 align:start position:0% our cable in stealin it's a guy brings a 00:40:38.530 --> 00:40:40.320 align:start position:0% our cable in stealin it's a guy brings a little<00:40:38.620> verify<00:40:39.280> to<00:40:39.340> verify<00:40:39.460> on<00:40:40.090> all<00:40:40.180> that 00:40:40.320 --> 00:40:40.330 align:start position:0% little verify to verify on all that 00:40:40.330 --> 00:40:42.450 align:start position:0% little verify to verify on all that appendix<00:40:40.720> is<00:40:40.960> that<00:40:40.990> nobody<00:40:41.800> changed<00:40:42.220> anything 00:40:42.450 --> 00:40:42.460 align:start position:0% appendix is that nobody changed anything 00:40:42.460 --> 00:40:44.340 align:start position:0% appendix is that nobody changed anything without<00:40:42.850> our<00:40:43.090> knowledge<00:40:43.210> but<00:40:43.900> that's<00:40:44.110> in<00:40:44.260> the 00:40:44.340 --> 00:40:44.350 align:start position:0% without our knowledge but that's in the 00:40:44.350 --> 00:40:48.090 align:start position:0% without our knowledge but that's in the bill<00:40:44.530> tours<00:40:44.830> and<00:40:45.760> that's<00:40:46.440> that's<00:40:47.440> well<00:40:47.860> away 00:40:48.090 --> 00:40:48.100 align:start position:0% bill tours and that's that's well away 00:40:48.100 --> 00:40:50.550 align:start position:0% bill tours and that's that's well away from<00:40:48.130> what<00:40:48.910> their<00:40:49.090> users<00:40:49.300> on<00:40:49.570> the<00:40:49.630> scene<00:40:49.840> but 00:40:50.550 --> 00:40:50.560 align:start position:0% from what their users on the scene but 00:40:50.560 --> 00:40:52.260 align:start position:0% from what their users on the scene but if<00:40:50.680> you<00:40:50.800> couldn't<00:40:51.040> if<00:40:51.160> someone<00:40:51.550> rebuild<00:40:52.060> it 00:40:52.260 --> 00:40:52.270 align:start position:0% if you couldn't if someone rebuild it 00:40:52.270 --> 00:40:56.870 align:start position:0% if you couldn't if someone rebuild it and<00:40:52.600> you<00:40:52.750> get<00:40:52.900> identically<00:40:53.560> wants<00:40:53.890> deployed 00:40:56.870 --> 00:40:56.880 align:start position:0% 00:40:56.880 --> 00:41:02.509 align:start position:0% and<00:40:57.880> you<00:40:58.030> can<00:40:58.150> automate 00:41:02.509 --> 00:41:02.519 align:start position:0% 00:41:02.519 --> 00:41:10.019 align:start position:0% other<00:41:03.519> is<00:41:04.089> the<00:41:04.299> ability<00:41:04.960> of<00:41:08.700> dependency<00:41:09.700> and 00:41:10.019 --> 00:41:10.029 align:start position:0% other is the ability of dependency and 00:41:10.029 --> 00:41:13.469 align:start position:0% other is the ability of dependency and also<00:41:10.450> how<00:41:10.630> about<00:41:10.989> having<00:41:11.739> a<00:41:11.979> proxy<00:41:12.579> smart 00:41:13.469 --> 00:41:13.479 align:start position:0% also how about having a proxy smart 00:41:13.479 --> 00:41:27.410 align:start position:0% also how about having a proxy smart contract<00:41:14.079> and<00:41:14.819> changing<00:41:15.819> the<00:41:16.269> business<00:41:16.930> logic 00:41:27.410 --> 00:41:27.420 align:start position:0% 00:41:27.420 --> 00:41:30.960 align:start position:0% is<00:41:28.420> very<00:41:28.630> good<00:41:28.989> in<00:41:29.499> the<00:41:29.619> sense<00:41:29.829> of<00:41:29.979> like<00:41:30.160> it 00:41:30.960 --> 00:41:30.970 align:start position:0% is very good in the sense of like it 00:41:30.970 --> 00:41:37.559 align:start position:0% is very good in the sense of like it matches<00:41:31.210> actual<00:41:35.579> but<00:41:36.579> another<00:41:36.819> thing<00:41:37.089> is<00:41:37.210> yeah 00:41:37.559 --> 00:41:37.569 align:start position:0% matches actual but another thing is yeah 00:41:37.569 --> 00:41:39.210 align:start position:0% matches actual but another thing is yeah is<00:41:37.839> it<00:41:37.989> safe<00:41:38.229> and<00:41:38.529> all<00:41:38.710> this<00:41:38.859> additional 00:41:39.210 --> 00:41:39.220 align:start position:0% is it safe and all this additional 00:41:39.220 --> 00:41:43.140 align:start position:0% is it safe and all this additional information<00:41:39.999> or<00:41:40.869> is<00:41:41.799> it<00:41:41.920> using<00:41:42.190> Oracle's<00:41:42.789> and 00:41:43.140 --> 00:41:43.150 align:start position:0% information or is it using Oracle's and 00:41:43.150 --> 00:41:45.299 align:start position:0% information or is it using Oracle's and like<00:41:43.749> is<00:41:44.019> it<00:41:44.170> depending<00:41:44.529> on<00:41:44.650> Oracle's<00:41:45.099> so<00:41:45.190> that 00:41:45.299 --> 00:41:45.309 align:start position:0% like is it depending on Oracle's so that 00:41:45.309 --> 00:41:47.519 align:start position:0% like is it depending on Oracle's so that the<00:41:45.460> users<00:41:45.849> know<00:41:46.239> that<00:41:46.749> they're<00:41:46.869> interacting 00:41:47.519 --> 00:41:47.529 align:start position:0% the users know that they're interacting 00:41:47.529 --> 00:41:51.479 align:start position:0% the users know that they're interacting with<00:41:47.559> something<00:41:47.890> that<00:41:48.249> maybe<00:41:49.680> so<00:41:50.680> we<00:41:51.309> would 00:41:51.479 --> 00:41:51.489 align:start position:0% with something that maybe so we would 00:41:51.489 --> 00:41:53.489 align:start position:0% with something that maybe so we would like<00:41:51.670> to<00:41:51.729> be<00:41:52.029> able<00:41:52.210> to<00:41:52.390> I<00:41:52.809> mean<00:41:53.229> it's<00:41:53.349> not 00:41:53.489 --> 00:41:53.499 align:start position:0% like to be able to I mean it's not 00:41:53.499 --> 00:41:55.769 align:start position:0% like to be able to I mean it's not undergoes<00:41:53.979> is<00:41:54.249> just<00:41:54.549> an<00:41:54.670> interface<00:41:55.299> that<00:41:55.329> what 00:41:55.769 --> 00:41:55.779 align:start position:0% undergoes is just an interface that what 00:41:55.779 --> 00:41:57.960 align:start position:0% undergoes is just an interface that what we<00:41:55.960> want<00:41:56.440> to<00:41:56.619> focus<00:41:56.859> on<00:41:57.190> mainly<00:41:57.460> is<00:41:57.819> the 00:41:57.960 --> 00:41:57.970 align:start position:0% we want to focus on mainly is the 00:41:57.970 --> 00:42:05.489 align:start position:0% we want to focus on mainly is the database<00:41:59.009> so<00:42:00.009> the<00:42:03.210> source<00:42:04.210> code<00:42:04.420> but<00:42:05.019> now<00:42:05.200> such 00:42:05.489 --> 00:42:05.499 align:start position:0% database so the source code but now such 00:42:05.499 --> 00:42:13.160 align:start position:0% database so the source code but now such situation<00:42:06.489> changes<00:42:06.880> and 00:42:13.160 --> 00:42:13.170 align:start position:0% 00:42:13.170 --> 00:42:17.490 align:start position:0% publish<00:42:14.170> the<00:42:14.200> source<00:42:15.300> form<00:42:16.300> and<00:42:16.690> all<00:42:16.900> them<00:42:17.410> are 00:42:17.490 --> 00:42:17.500 align:start position:0% publish the source form and all them are 00:42:17.500 --> 00:42:19.560 align:start position:0% publish the source form and all them are available<00:42:17.650> now<00:42:18.640> the<00:42:18.670> question<00:42:19.090> is<00:42:19.120> where<00:42:19.480> do 00:42:19.560 --> 00:42:19.570 align:start position:0% available now the question is where do 00:42:19.570 --> 00:42:22.830 align:start position:0% available now the question is where do we<00:42:19.690> get<00:42:19.810> this<00:42:20.320> of<00:42:20.650> all<00:42:21.070> of<00:42:21.220> them<00:42:21.400> so<00:42:21.840> maybe 00:42:22.830 --> 00:42:22.840 align:start position:0% we get this of all of them so maybe 00:42:22.840 --> 00:42:24.330 align:start position:0% we get this of all of them so maybe there<00:42:23.140> can<00:42:23.260> also<00:42:23.440> be<00:42:23.560> a<00:42:23.650> solution<00:42:23.800> for<00:42:24.220> this 00:42:24.330 --> 00:42:24.340 align:start position:0% there can also be a solution for this 00:42:24.340 --> 00:42:26.580 align:start position:0% there can also be a solution for this and<00:42:24.580> then<00:42:24.850> you<00:42:25.000> can<00:42:25.210> start<00:42:25.540> annotating<00:42:25.930> memory 00:42:26.580 --> 00:42:26.590 align:start position:0% and then you can start annotating memory 00:42:26.590 --> 00:42:30.540 align:start position:0% and then you can start annotating memory because<00:42:27.070> once<00:42:27.280> we<00:42:28.800> do<00:42:29.800> better<00:42:30.130> if<00:42:30.250> you<00:42:30.310> got 00:42:30.540 --> 00:42:30.550 align:start position:0% because once we do better if you got 00:42:30.550 --> 00:42:42.320 align:start position:0% because once we do better if you got them<00:42:30.790> to<00:42:31.030> come<00:42:31.060> to<00:42:31.360> you<00:42:36.780> they<00:42:37.780> can<00:42:37.960> continue 00:42:42.320 --> 00:42:42.330 align:start position:0% 00:42:42.330 --> 00:42:47.180 align:start position:0% because<00:42:43.330> you<00:42:43.630> actors<00:42:43.990> say<00:42:44.940> so<00:42:45.940> then<00:42:46.090> it<00:42:46.180> says 00:42:47.180 --> 00:42:47.190 align:start position:0% because you actors say so then it says 00:42:47.190 --> 00:42:51.570 align:start position:0% because you actors say so then it says verify<00:42:48.190> this<00:42:49.440> I<00:42:50.440> can<00:42:50.860> see<00:42:51.010> you<00:42:51.130> marketers 00:42:51.570 --> 00:42:51.580 align:start position:0% verify this I can see you marketers 00:42:51.580 --> 00:42:54.660 align:start position:0% verify this I can see you marketers together<00:42:51.820> little<00:42:52.720> while<00:42:52.930> okay<00:42:53.770> big<00:42:54.130> apartment 00:42:54.660 --> 00:42:54.670 align:start position:0% together little while okay big apartment 00:42:54.670 --> 00:42:58.260 align:start position:0% together little while okay big apartment Cisco<00:42:55.180> have<00:42:55.360> to<00:42:55.450> be<00:42:55.540> here<00:42:55.720> in<00:42:56.760> my<00:42:57.760> office<00:42:57.790> do 00:42:58.260 --> 00:42:58.270 align:start position:0% Cisco have to be here in my office do 00:42:58.270 --> 00:43:06.440 align:start position:0% Cisco have to be here in my office do you<00:42:58.360> have<00:42:58.840> a<00:42:58.870> pencil<00:43:04.530> give<00:43:05.530> you<00:43:05.650> a<00:43:05.680> word<00:43:05.920> like 00:43:06.440 --> 00:43:06.450 align:start position:0% you have a pencil give you a word like 00:43:06.450 --> 00:43:09.270 align:start position:0% you have a pencil give you a word like our<00:43:07.450> database<00:43:08.050> that's<00:43:08.380> it<00:43:08.560> if<00:43:08.800> there's<00:43:09.130> one 00:43:09.270 --> 00:43:09.280 align:start position:0% our database that's it if there's one 00:43:09.280 --> 00:43:12.900 align:start position:0% our database that's it if there's one point<00:43:09.760> be<00:43:10.060> erased<00:43:10.360> videos<00:43:11.580> and<00:43:12.580> then<00:43:12.670> if<00:43:12.790> you 00:43:12.900 --> 00:43:12.910 align:start position:0% point be erased videos and then if you 00:43:12.910 --> 00:43:15.360 align:start position:0% point be erased videos and then if you run<00:43:13.090> your<00:43:13.390> note<00:43:13.660> you<00:43:13.900> can<00:43:14.350> add<00:43:14.560> more<00:43:14.830> data<00:43:15.010> and 00:43:15.360 --> 00:43:15.370 align:start position:0% run your note you can add more data and 00:43:15.370 --> 00:43:33.310 align:start position:0% run your note you can add more data and I<00:43:15.490> run<00:43:15.700> my<00:43:15.940> note<00:43:16.180> and<00:43:16.420> I<00:43:16.780> can<00:43:16.930> see<00:43:17.260> I<00:43:17.560> have<00:43:17.830> this 00:43:33.310 --> 00:43:33.320 align:start position:0% 00:43:33.320 --> 00:43:36.650 align:start position:0% you<00:43:34.320> incentivize<00:43:35.250> the<00:43:35.520> actors<00:43:36.000> within<00:43:36.360> it 00:43:36.650 --> 00:43:36.660 align:start position:0% you incentivize the actors within it 00:43:36.660 --> 00:43:38.570 align:start position:0% you incentivize the actors within it so<00:43:36.930> that<00:43:37.080> they<00:43:37.170> can<00:43:37.320> each<00:43:37.470> earn<00:43:37.770> money<00:43:38.070> right 00:43:38.570 --> 00:43:38.580 align:start position:0% so that they can each earn money right 00:43:38.580 --> 00:43:41.480 align:start position:0% so that they can each earn money right so<00:43:39.510> that<00:43:40.110> way<00:43:40.230> they<00:43:40.440> want<00:43:40.710> to<00:43:40.800> grow<00:43:40.980> the<00:43:41.190> system 00:43:41.480 --> 00:43:41.490 align:start position:0% so that way they want to grow the system 00:43:41.490 --> 00:43:43.640 align:start position:0% so that way they want to grow the system so<00:43:41.580> they<00:43:41.700> continue<00:43:42.090> to<00:43:42.210> get<00:43:42.420> ready<00:43:42.930> quite 00:43:43.640 --> 00:43:43.650 align:start position:0% so they continue to get ready quite 00:43:43.650 --> 00:43:46.490 align:start position:0% so they continue to get ready quite people<00:43:43.920> getting<00:43:45.230> requesting<00:43:46.230> wouldn't 00:43:46.490 --> 00:43:46.500 align:start position:0% people getting requesting wouldn't 00:43:46.500 --> 00:43:48.170 align:start position:0% people getting requesting wouldn't reports<00:43:46.860> and<00:43:47.250> so<00:43:47.460> they<00:43:47.580> can<00:43:47.700> charge<00:43:47.880> for<00:43:48.119> the 00:43:48.170 --> 00:43:48.180 align:start position:0% reports and so they can charge for the 00:43:48.180 --> 00:43:50.720 align:start position:0% reports and so they can charge for the order<00:43:48.420> yeah<00:43:48.930> so<00:43:49.140> that's<00:43:49.320> it<00:43:49.440> and<00:43:49.740> so<00:43:49.800> yeah<00:43:50.490> so 00:43:50.720 --> 00:43:50.730 align:start position:0% order yeah so that's it and so yeah so 00:43:50.730 --> 00:43:52.790 align:start position:0% order yeah so that's it and so yeah so that<00:43:51.270> gives<00:43:51.540> an<00:43:51.660> incentive<00:43:51.930> for<00:43:52.170> the<00:43:52.350> order<00:43:52.650> to 00:43:52.790 --> 00:43:52.800 align:start position:0% that gives an incentive for the order to 00:43:52.800 --> 00:43:54.859 align:start position:0% that gives an incentive for the order to write<00:43:53.160> notes<00:43:53.670> in<00:43:53.850> order<00:43:54.030> as<00:43:54.330> many<00:43:54.450> things<00:43:54.720> as 00:43:54.859 --> 00:43:54.869 align:start position:0% write notes in order as many things as 00:43:54.869 --> 00:43:57.440 align:start position:0% write notes in order as many things as possible<00:43:54.930> and<00:43:55.740> then<00:43:55.950> make<00:43:56.280> this<00:43:56.450> available 00:43:57.440 --> 00:43:57.450 align:start position:0% possible and then make this available 00:43:57.450 --> 00:43:59.150 align:start position:0% possible and then make this available and<00:43:57.840> also<00:43:57.990> the<00:43:58.200> people<00:43:58.380> who<00:43:58.530> wrote<00:43:58.740> the<00:43:58.800> small 00:43:59.150 --> 00:43:59.160 align:start position:0% and also the people who wrote the small 00:43:59.160 --> 00:44:01.640 align:start position:0% and also the people who wrote the small contracts<00:43:59.610> if<00:44:00.330> they<00:44:00.450> do<00:44:00.570> them<00:44:00.750> correctly<00:44:01.020> they 00:44:01.640 --> 00:44:01.650 align:start position:0% contracts if they do them correctly they 00:44:01.650 --> 00:44:04.760 align:start position:0% contracts if they do them correctly they get<00:44:01.980> a<00:44:02.010> share<00:44:02.250> of<00:44:02.550> the<00:44:02.790> reward<00:44:03.480> right<00:44:03.840> so 00:44:04.760 --> 00:44:04.770 align:start position:0% get a share of the reward right so 00:44:04.770 --> 00:44:06.109 align:start position:0% get a share of the reward right so that's<00:44:04.890> that's<00:44:05.100> another<00:44:05.369> challenge<00:44:05.670> but<00:44:06.030> it 00:44:06.109 --> 00:44:06.119 align:start position:0% that's that's another challenge but it 00:44:06.119 --> 00:44:07.910 align:start position:0% that's that's another challenge but it seems<00:44:06.330> for<00:44:06.510> example<00:44:06.900> see<00:44:07.080> this<00:44:07.110> even<00:44:07.500> in<00:44:07.680> all 00:44:07.910 --> 00:44:07.920 align:start position:0% seems for example see this even in all 00:44:07.920 --> 00:44:10.760 align:start position:0% seems for example see this even in all the<00:44:08.040> smart<00:44:08.310> contracts<00:44:08.700> per<00:44:09.050> for<00:44:10.050> example<00:44:10.440> but 00:44:10.760 --> 00:44:10.770 align:start position:0% the smart contracts per for example but 00:44:10.770 --> 00:44:13.100 align:start position:0% the smart contracts per for example but adding<00:44:11.700> something<00:44:11.970> to<00:44:12.119> the<00:44:12.240> developer<00:44:12.780> tools 00:44:13.100 --> 00:44:13.110 align:start position:0% adding something to the developer tools 00:44:13.110 --> 00:44:16.070 align:start position:0% adding something to the developer tools could<00:44:13.590> be<00:44:13.710> published<00:44:14.070> IPA<00:44:14.490> pesos<00:44:14.850> one<00:44:15.150> and<00:44:15.480> of 00:44:16.070 --> 00:44:16.080 align:start position:0% could be published IPA pesos one and of 00:44:16.080 --> 00:44:18.410 align:start position:0% could be published IPA pesos one and of course<00:44:16.320> unchain<00:44:16.830> we<00:44:17.010> have<00:44:17.190> and<00:44:17.880> of<00:44:18.030> course<00:44:18.330> the 00:44:18.410 --> 00:44:18.420 align:start position:0% course unchain we have and of course the 00:44:18.420 --> 00:44:19.820 align:start position:0% course unchain we have and of course the metadata<00:44:18.780> to<00:44:19.020> and<00:44:19.230> the<00:44:19.290> mum<00:44:19.470> chain<00:44:19.619> we<00:44:19.740> have 00:44:19.820 --> 00:44:19.830 align:start position:0% metadata to and the mum chain we have 00:44:19.830 --> 00:44:22.070 align:start position:0% metadata to and the mum chain we have like<00:44:20.010> a<00:44:20.040> hash<00:44:20.610> to<00:44:20.910> verify<00:44:21.570> that<00:44:21.600> this<00:44:21.869> is<00:44:21.930> the 00:44:22.070 --> 00:44:22.080 align:start position:0% like a hash to verify that this is the 00:44:22.080 --> 00:44:24.710 align:start position:0% like a hash to verify that this is the right<00:44:22.290> method<00:44:22.500> later<00:44:22.740> still<00:44:23.070> where<00:44:23.730> do<00:44:24.060> I<00:44:24.180> get 00:44:24.710 --> 00:44:24.720 align:start position:0% right method later still where do I get 00:44:24.720 --> 00:44:26.960 align:start position:0% right method later still where do I get the<00:44:24.930> best<00:44:25.140> of<00:44:25.260> all<00:44:25.470> of<00:44:25.530> them<00:44:25.800> so<00:44:26.369> we<00:44:26.760> will<00:44:26.910> be 00:44:26.960 --> 00:44:26.970 align:start position:0% the best of all of them so we will be 00:44:26.970 --> 00:44:30.200 align:start position:0% the best of all of them so we will be good<00:44:27.150> to<00:44:27.390> also<00:44:27.930> find<00:44:28.500> one<00:44:29.100> way<00:44:29.369> to<00:44:29.430> publish<00:44:30.030> the 00:44:30.200 --> 00:44:30.210 align:start position:0% good to also find one way to publish the 00:44:30.210 --> 00:44:40.330 align:start position:0% good to also find one way to publish the list<00:44:30.240> of<00:44:30.890> or<00:44:31.890> all<00:44:32.220> the<00:44:32.340> liens 00:44:40.330 --> 00:44:40.340 align:start position:0% 00:44:40.340 --> 00:45:20.350 align:start position:0% [Music] 00:45:20.350 --> 00:45:20.360 align:start position:0% 00:45:20.360 --> 00:45:23.450 align:start position:0% that<00:45:21.360> sort<00:45:21.660> of<00:45:21.780> language<00:45:21.930> like<00:45:22.290> and<00:45:22.590> figure 00:45:23.450 --> 00:45:23.460 align:start position:0% that sort of language like and figure 00:45:23.460 --> 00:45:25.490 align:start position:0% that sort of language like and figure out<00:45:23.610> the<00:45:23.760> address<00:45:24.090> but<00:45:24.690> then<00:45:24.810> I<00:45:24.900> publish<00:45:25.290> it<00:45:25.380> on 00:45:25.490 --> 00:45:25.500 align:start position:0% out the address but then I publish it on 00:45:25.500 --> 00:45:27.410 align:start position:0% out the address but then I publish it on the<00:45:25.530> chain<00:45:25.800> and<00:45:26.520> now<00:45:26.640> somebody<00:45:26.970> detects<00:45:27.330> that 00:45:27.410 --> 00:45:27.420 align:start position:0% the chain and now somebody detects that 00:45:27.420 --> 00:45:29.750 align:start position:0% the chain and now somebody detects that there's<00:45:27.600> a<00:45:27.750> new<00:45:27.900> contract<00:45:28.350> unchanged<00:45:28.800> but<00:45:29.460> how 00:45:29.750 --> 00:45:29.760 align:start position:0% there's a new contract unchanged but how 00:45:29.760 --> 00:45:32.570 align:start position:0% there's a new contract unchanged but how do<00:45:29.820> I<00:45:30.000> know<00:45:30.800> where<00:45:31.800> that<00:45:31.980> source<00:45:32.250> for<00:45:32.490> the 00:45:32.570 --> 00:45:32.580 align:start position:0% do I know where that source for the 00:45:32.580 --> 00:45:33.140 align:start position:0% do I know where that source for the sport 00:45:33.140 --> 00:45:33.150 align:start position:0% sport 00:45:33.150 --> 00:45:34.430 align:start position:0% sport I<00:45:33.180> mean<00:45:33.360> it's<00:45:33.510> start<00:45:33.720> now<00:45:33.870> and<00:45:33.930> if<00:45:34.110> I<00:45:34.200> have<00:45:34.320> the 00:45:34.430 --> 00:45:34.440 align:start position:0% I mean it's start now and if I have the 00:45:34.440 --> 00:45:35.840 align:start position:0% I mean it's start now and if I have the source<00:45:34.650> like<00:45:35.010> the<00:45:35.100> hope<00:45:35.220> is<00:45:35.430> that<00:45:35.460> the 00:45:35.840 --> 00:45:35.850 align:start position:0% source like the hope is that the 00:45:35.850 --> 00:45:37.970 align:start position:0% source like the hope is that the deployment<00:45:36.300> tools<00:45:36.720> publish<00:45:37.200> it<00:45:37.350> tools<00:45:37.590> for<00:45:37.830> my 00:45:37.970 --> 00:45:37.980 align:start position:0% deployment tools publish it tools for my 00:45:37.980 --> 00:45:40.820 align:start position:0% deployment tools publish it tools for my PFS<00:45:38.540> and<00:45:39.540> you<00:45:39.660> can<00:45:39.870> grab<00:45:40.590> it 00:45:40.820 --> 00:45:40.830 align:start position:0% PFS and you can grab it 00:45:40.830 --> 00:45:43.070 align:start position:0% PFS and you can grab it why<00:45:41.310> are<00:45:41.550> the<00:45:41.790> metadata<00:45:42.150> and<00:45:42.360> the<00:45:42.660> link<00:45:42.870> in<00:45:42.960> the 00:45:43.070 --> 00:45:43.080 align:start position:0% why are the metadata and the link in the 00:45:43.080 --> 00:45:45.950 align:start position:0% why are the metadata and the link in the metadata<00:45:43.440> and<00:45:43.800> then<00:45:44.190> keep<00:45:44.460> it<00:45:44.720> persistent<00:45:45.720> in 00:45:45.950 --> 00:45:45.960 align:start position:0% metadata and then keep it persistent in 00:45:45.960 --> 00:45:50.090 align:start position:0% metadata and then keep it persistent in that<00:45:46.230> big<00:45:46.470> day<00:45:46.620> like<00:45:47.040> me<00:45:47.550> today<00:45:48.080> from<00:45:49.080> the<00:45:49.410> hash 00:45:50.090 --> 00:45:50.100 align:start position:0% that big day like me today from the hash 00:45:50.100 --> 00:45:52.250 align:start position:0% that big day like me today from the hash link<00:45:50.370> in<00:45:50.610> the<00:45:50.760> back<00:45:50.940> room<00:45:51.150> uh-huh 00:45:52.250 --> 00:45:52.260 align:start position:0% link in the back room uh-huh 00:45:52.260 --> 00:45:53.810 align:start position:0% link in the back room uh-huh so<00:45:52.560> the<00:45:52.680> hash<00:45:52.830> thing<00:45:53.040> in<00:45:53.190> the<00:45:53.280> white<00:45:53.490> coat 00:45:53.810 --> 00:45:53.820 align:start position:0% so the hash thing in the white coat 00:45:53.820 --> 00:45:55.880 align:start position:0% so the hash thing in the white coat contains<00:45:54.540> the<00:45:54.630> address<00:45:54.780> of<00:45:55.170> swarm<00:45:55.680> or 00:45:55.880 --> 00:45:55.890 align:start position:0% contains the address of swarm or 00:45:55.890 --> 00:45:58.190 align:start position:0% contains the address of swarm or activist<00:45:56.340> for<00:45:57.060> the<00:45:57.120> me<00:45:57.330> turn<00:45:57.480> it<00:45:57.570> on<00:45:57.750> alright 00:45:58.190 --> 00:45:58.200 align:start position:0% activist for the me turn it on alright 00:45:58.200 --> 00:46:00.680 align:start position:0% activist for the me turn it on alright so<00:45:58.470> then<00:45:58.680> that<00:45:58.920> will<00:45:59.010> be<00:45:59.130> perfect<00:45:59.760> so<00:46:00.450> if<00:46:00.540> that 00:46:00.680 --> 00:46:00.690 align:start position:0% so then that will be perfect so if that 00:46:00.690 --> 00:46:02.540 align:start position:0% so then that will be perfect so if that happens<00:46:01.200> and<00:46:01.320> all<00:46:01.500> that<00:46:01.620> useful<00:46:01.890> published 00:46:02.540 --> 00:46:02.550 align:start position:0% happens and all that useful published 00:46:02.550 --> 00:46:03.800 align:start position:0% happens and all that useful published then 00:46:03.800 --> 00:46:03.810 align:start position:0% then 00:46:03.810 --> 00:46:07.100 align:start position:0% then go<00:46:04.580> watch<00:46:05.580> it<00:46:05.610> later<00:46:05.910> I<00:46:06.090> cannot<00:46:06.390> separate<00:46:06.810> and 00:46:07.100 --> 00:46:07.110 align:start position:0% go watch it later I cannot separate and 00:46:07.110 --> 00:46:08.960 align:start position:0% go watch it later I cannot separate and slowly<00:46:07.320> pull<00:46:07.920> them<00:46:08.070> all<00:46:08.220> into<00:46:08.400> them<00:46:08.670> into<00:46:08.850> one 00:46:08.960 --> 00:46:08.970 align:start position:0% slowly pull them all into them into one 00:46:08.970 --> 00:46:15.190 align:start position:0% slowly pull them all into them into one database<00:46:09.150> and<00:46:09.750> in<00:46:10.140> the<00:46:10.920> system<00:46:11.580> we<00:46:12.300> are<00:46:12.480> using 00:46:15.190 --> 00:46:15.200 align:start position:0% database and in the system we are using 00:46:15.200 --> 00:46:16.970 align:start position:0% database and in the system we are using virtual<00:46:16.200> controls 00:46:16.970 --> 00:46:16.980 align:start position:0% virtual controls 00:46:16.980 --> 00:46:19.790 align:start position:0% virtual controls torrent<00:46:17.390> systems<00:46:18.390> for<00:46:18.510> the<00:46:18.600> more<00:46:18.810> pious<00:46:19.200> they 00:46:19.790 --> 00:46:19.800 align:start position:0% torrent systems for the more pious they 00:46:19.800 --> 00:46:22.580 align:start position:0% torrent systems for the more pious they are<00:46:20.060> you<00:46:21.060> can<00:46:21.210> update<00:46:21.390> that<00:46:21.540> forever<00:46:22.290> doesn't 00:46:22.580 --> 00:46:22.590 align:start position:0% are you can update that forever doesn't 00:46:22.590 --> 00:46:24.590 align:start position:0% are you can update that forever doesn't change<00:46:22.890> so<00:46:23.400> for<00:46:23.550> example<00:46:23.820> auditors<00:46:24.210> could<00:46:24.420> run 00:46:24.590 --> 00:46:24.600 align:start position:0% change so for example auditors could run 00:46:24.600 --> 00:46:28.040 align:start position:0% change so for example auditors could run it<00:46:24.750> and<00:46:25.310> make<00:46:26.310> their<00:46:26.550> annotations<00:46:27.120> so<00:46:27.870> they 00:46:28.040 --> 00:46:28.050 align:start position:0% it and make their annotations so they 00:46:28.050 --> 00:46:29.810 align:start position:0% it and make their annotations so they can<00:46:28.230> say<00:46:28.410> okay<00:46:28.680> this<00:46:28.830> one<00:46:28.980> is<00:46:29.010> audited<00:46:29.490> up<00:46:29.700> to 00:46:29.810 --> 00:46:29.820 align:start position:0% can say okay this one is audited up to 00:46:29.820 --> 00:46:32.390 align:start position:0% can say okay this one is audited up to that<00:46:29.940> level<00:46:30.180> and<00:46:30.480> so<00:46:30.630> on<00:46:30.920> but<00:46:31.920> also<00:46:32.070> making 00:46:32.390 --> 00:46:32.400 align:start position:0% that level and so on but also making 00:46:32.400 --> 00:46:34.610 align:start position:0% that level and so on but also making other<00:46:32.640> organizations<00:46:33.300> could<00:46:33.450> start<00:46:33.720> saying<00:46:34.020> I 00:46:34.610 --> 00:46:34.620 align:start position:0% other organizations could start saying I 00:46:34.620 --> 00:46:38.260 align:start position:0% other organizations could start saying I am<00:46:35.160> a<00:46:35.280> change<00:46:35.550> this<00:46:35.850> contract<00:46:36.540> into<00:46:37.160> somebody 00:46:38.260 --> 00:46:38.270 align:start position:0% am a change this contract into somebody 00:46:38.270 --> 00:46:41.000 align:start position:0% am a change this contract into somebody somewhere<00:46:39.270> on<00:46:39.390> the<00:46:39.480> constant<00:46:39.960> contact<00:46:40.200> state 00:46:41.000 --> 00:46:41.010 align:start position:0% somewhere on the constant contact state 00:46:41.010 --> 00:46:44.050 align:start position:0% somewhere on the constant contact state some<00:46:41.520> money<00:46:41.700> because<00:46:42.420> they<00:46:42.690> want<00:46:42.900> an<00:46:42.990> audit 00:46:44.050 --> 00:46:44.060 align:start position:0% some money because they want an audit 00:46:44.060 --> 00:46:49.090 align:start position:0% some money because they want an audit but<00:46:45.060> maybe<00:46:45.720> I<00:46:45.840> was<00:46:46.050> too<00:46:46.970> expensive<00:46:47.970> so<00:46:48.330> maybe 00:46:49.090 --> 00:46:49.100 align:start position:0% but maybe I was too expensive so maybe 00:46:49.100 --> 00:46:51.620 align:start position:0% but maybe I was too expensive so maybe publish<00:46:50.100> that<00:46:50.280> then<00:46:50.520> it<00:46:50.850> could<00:46:51.060> retrieve<00:46:51.390> all 00:46:51.620 --> 00:46:51.630 align:start position:0% publish that then it could retrieve all 00:46:51.630 --> 00:46:53.780 align:start position:0% publish that then it could retrieve all these<00:46:51.780> data<00:46:51.990> and<00:46:52.320> see<00:46:52.800> how<00:46:52.920> there's<00:46:53.280> like<00:46:53.460> a 00:46:53.780 --> 00:46:53.790 align:start position:0% these data and see how there's like a 00:46:53.790 --> 00:46:55.370 align:start position:0% these data and see how there's like a lot<00:46:53.970> of<00:46:54.090> contracts<00:46:54.540> that<00:46:54.630> have<00:46:54.690> states<00:46:55.170> we 00:46:55.370 --> 00:46:55.380 align:start position:0% lot of contracts that have states we 00:46:55.380 --> 00:46:57.110 align:start position:0% lot of contracts that have states we just<00:46:55.590> show<00:46:55.770> those<00:46:55.980> and<00:46:56.280> make<00:46:56.760> a<00:46:56.790> little 00:46:57.110 --> 00:46:57.120 align:start position:0% just show those and make a little 00:46:57.120 --> 00:46:58.220 align:start position:0% just show those and make a little registration<00:46:57.660> think<00:46:57.810> that's<00:46:57.930> an<00:46:58.050> interesting 00:46:58.220 --> 00:46:58.230 align:start position:0% registration think that's an interesting 00:46:58.230 --> 00:47:00.500 align:start position:0% registration think that's an interesting come<00:46:58.980> back<00:46:59.130> with<00:46:59.250> a<00:46:59.460> library<00:46:59.880> that<00:47:00.150> has 00:47:00.500 --> 00:47:00.510 align:start position:0% come back with a library that has 00:47:00.510 --> 00:47:02.270 align:start position:0% come back with a library that has certain<00:47:00.870> things<00:47:00.960> that<00:47:01.560> we<00:47:01.680> produce<00:47:01.830> with 00:47:02.270 --> 00:47:02.280 align:start position:0% certain things that we produce with 00:47:02.280 --> 00:47:04.700 align:start position:0% certain things that we produce with other<00:47:02.610> smart<00:47:02.910> contracts<00:47:03.480> and<00:47:03.690> now<00:47:04.200> this<00:47:04.470> one 00:47:04.700 --> 00:47:04.710 align:start position:0% other smart contracts and now this one 00:47:04.710 --> 00:47:07.010 align:start position:0% other smart contracts and now this one seems<00:47:05.010> to<00:47:05.160> be<00:47:05.220> in<00:47:05.460> very<00:47:05.670> interesting<00:47:06.510> library 00:47:07.010 --> 00:47:07.020 align:start position:0% seems to be in very interesting library 00:47:07.020 --> 00:47:08.660 align:start position:0% seems to be in very interesting library let's<00:47:07.380> take<00:47:07.650> more<00:47:07.950> and<00:47:08.160> then<00:47:08.250> maybe<00:47:08.430> also 00:47:08.660 --> 00:47:08.670 align:start position:0% let's take more and then maybe also 00:47:08.670 --> 00:47:10.880 align:start position:0% let's take more and then maybe also auditors<00:47:09.150> could<00:47:09.390> use<00:47:09.540> that<00:47:09.720> to<00:47:10.110> bid<00:47:10.320> to 00:47:10.880 --> 00:47:10.890 align:start position:0% auditors could use that to bid to 00:47:10.890 --> 00:47:12.800 align:start position:0% auditors could use that to bid to actually<00:47:11.220> do<00:47:11.310> the<00:47:11.460> audit<00:47:11.610> and<00:47:11.880> then<00:47:11.970> get<00:47:12.600> paid 00:47:12.800 --> 00:47:12.810 align:start position:0% actually do the audit and then get paid 00:47:12.810 --> 00:47:15.200 align:start position:0% actually do the audit and then get paid from<00:47:13.020> that<00:47:13.200> and<00:47:13.470> so<00:47:13.980> that's<00:47:14.190> the<00:47:14.760> additional 00:47:15.200 --> 00:47:15.210 align:start position:0% from that and so that's the additional 00:47:15.210 --> 00:47:17.870 align:start position:0% from that and so that's the additional things<00:47:15.390> and<00:47:15.540> this<00:47:15.600> one<00:47:15.870> is<00:47:15.990> like<00:47:16.580> figuring<00:47:17.580> out 00:47:17.870 --> 00:47:17.880 align:start position:0% things and this one is like figuring out 00:47:17.880 --> 00:47:20.450 align:start position:0% things and this one is like figuring out if<00:47:18.720> somebody's<00:47:19.170> ready<00:47:19.410> to<00:47:19.680> sense<00:47:20.100> the<00:47:20.250> money 00:47:20.450 --> 00:47:20.460 align:start position:0% if somebody's ready to sense the money 00:47:20.460 --> 00:47:22.760 align:start position:0% if somebody's ready to sense the money to<00:47:20.820> pay<00:47:21.090> for<00:47:21.150> an<00:47:21.390> order<00:47:21.660> another<00:47:22.290> would<00:47:22.740> be 00:47:22.760 --> 00:47:22.770 align:start position:0% to pay for an order another would be 00:47:22.770 --> 00:47:27.010 align:start position:0% to pay for an order another would be publishing<00:47:23.640> like<00:47:23.850> author 00:47:27.010 --> 00:47:27.020 align:start position:0% 00:47:27.020 --> 00:48:09.500 align:start position:0% organization<00:48:07.430> they're<00:48:08.430> just<00:48:08.700> creating<00:48:09.480> like 00:48:09.500 --> 00:48:09.510 align:start position:0% organization they're just creating like 00:48:09.510 --> 00:48:16.010 align:start position:0% organization they're just creating like you<00:48:09.810> your<00:48:10.140> own<00:48:12.800> mattress<00:48:13.850> then<00:48:14.850> you<00:48:14.970> can<00:48:15.120> like 00:48:16.010 --> 00:48:16.020 align:start position:0% you your own mattress then you can like 00:48:16.020 --> 00:48:19.280 align:start position:0% you your own mattress then you can like different<00:48:16.710> like<00:48:17.060> this<00:48:18.060> contract<00:48:18.510> and<00:48:19.020> credo 00:48:19.280 --> 00:48:19.290 align:start position:0% different like this contract and credo 00:48:19.290 --> 00:48:21.200 align:start position:0% different like this contract and credo also<00:48:19.800> from<00:48:19.980> Network<00:48:20.310> paintings<00:48:20.760> actually 00:48:21.200 --> 00:48:21.210 align:start position:0% also from Network paintings actually 00:48:21.210 --> 00:48:24.470 align:start position:0% also from Network paintings actually device<00:48:22.070> without<00:48:23.070> the<00:48:23.340> leading<00:48:23.640> question 00:48:24.470 --> 00:48:24.480 align:start position:0% device without the leading question 00:48:24.480 --> 00:48:26.710 align:start position:0% device without the leading question about<00:48:24.870> staking 00:48:26.710 --> 00:48:26.720 align:start position:0% about staking 00:48:26.720 --> 00:48:29.809 align:start position:0% about staking like<00:48:27.720> Nikita<00:48:27.990> oh<00:48:28.170> I<00:48:28.650> I<00:48:28.680> built<00:48:29.130> this<00:48:29.339> convection 00:48:29.809 --> 00:48:29.819 align:start position:0% like Nikita oh I I built this convection 00:48:29.819 --> 00:48:32.329 align:start position:0% like Nikita oh I I built this convection oven<00:48:30.269> at<00:48:30.630> the<00:48:30.900> recall<00:48:31.410> all<00:48:31.680> the<00:48:31.799> contractor 00:48:32.329 --> 00:48:32.339 align:start position:0% oven at the recall all the contractor 00:48:32.339 --> 00:48:36.950 align:start position:0% oven at the recall all the contractor building<00:48:32.809> is<00:48:33.809> another<00:48:34.200> weapon<00:48:35.630> my<00:48:36.630> thought<00:48:36.839> is 00:48:36.950 --> 00:48:36.960 align:start position:0% building is another weapon my thought is 00:48:36.960 --> 00:48:40.390 align:start position:0% building is another weapon my thought is to<00:48:37.200> finish<00:48:37.619> everything<00:48:38.660> just<00:48:39.660> single 00:48:40.390 --> 00:48:40.400 align:start position:0% to finish everything just single 00:48:40.400 --> 00:49:08.450 align:start position:0% to finish everything just single building<00:49:03.259> on<00:49:04.259> rifle<00:49:05.160> what<00:49:06.559> a<00:49:07.559> huge<00:49:08.009> part<00:49:08.339> of 00:49:08.450 --> 00:49:08.460 align:start position:0% building on rifle what a huge part of 00:49:08.460 --> 00:49:10.009 align:start position:0% building on rifle what a huge part of our<00:49:08.609> effort<00:49:08.940> is<00:49:09.029> working<00:49:09.390> on<00:49:09.509> something<00:49:09.750> we 00:49:10.009 --> 00:49:10.019 align:start position:0% our effort is working on something we 00:49:10.019 --> 00:49:14.799 align:start position:0% our effort is working on something we call<00:49:10.259> tokens<00:49:10.710> with<00:49:10.970> is<00:49:11.970> it's<00:49:12.450> open<00:49:12.569> source<00:49:12.930> and 00:49:14.799 --> 00:49:14.809 align:start position:0% call tokens with is it's open source and 00:49:14.809 --> 00:49:17.230 align:start position:0% call tokens with is it's open source and mechanization<00:49:15.809> but<00:49:16.470> basically<00:49:16.740> is<00:49:17.130> a 00:49:17.230 --> 00:49:17.240 align:start position:0% mechanization but basically is a 00:49:17.240 --> 00:49:20.089 align:start position:0% mechanization but basically is a selenium<00:49:18.240> powerful<00:49:18.839> smart<00:49:19.170> contracts<00:49:19.650> so 00:49:20.089 --> 00:49:20.099 align:start position:0% selenium powerful smart contracts so 00:49:20.099 --> 00:49:24.009 align:start position:0% selenium powerful smart contracts so within<00:49:20.309> the<00:49:20.690> if<00:49:21.690> you<00:49:21.839> want<00:49:22.079> to<00:49:22.170> make<00:49:22.470> a<00:49:22.500> call 00:49:24.009 --> 00:49:24.019 align:start position:0% within the if you want to make a call 00:49:24.019 --> 00:49:30.170 align:start position:0% within the if you want to make a call right<00:49:27.529> by<00:49:28.529> inviting<00:49:28.859> it<00:49:29.160> by<00:49:29.309> declaring<00:49:29.730> in 00:49:30.170 --> 00:49:30.180 align:start position:0% right by inviting it by declaring in 00:49:30.180 --> 00:49:32.450 align:start position:0% right by inviting it by declaring in Excel<00:49:30.660> that<00:49:31.200> means<00:49:31.500> we<00:49:31.829> have<00:49:32.099> to<00:49:32.220> specify 00:49:32.450 --> 00:49:32.460 align:start position:0% Excel that means we have to specify 00:49:32.460 --> 00:49:33.930 align:start position:0% Excel that means we have to specify exactly<00:49:33.000> what<00:49:33.150> is<00:49:33.269> the<00:49:33.359> function<00:49:33.720> main 00:49:33.930 --> 00:49:33.940 align:start position:0% exactly what is the function main 00:49:33.940 --> 00:49:35.320 align:start position:0% exactly what is the function main [Music] 00:49:35.320 --> 00:49:35.330 align:start position:0% [Music] 00:49:35.330 --> 00:49:38.540 align:start position:0% [Music] so<00:49:36.330> one<00:49:36.840> thing<00:49:37.020> it<00:49:37.170> helps<00:49:37.470> is<00:49:37.740> when<00:49:38.010> the<00:49:38.400> user 00:49:38.540 --> 00:49:38.550 align:start position:0% so one thing it helps is when the user 00:49:38.550 --> 00:49:44.000 align:start position:0% so one thing it helps is when the user makes<00:49:38.850> a<00:49:41.630> within<00:49:42.630> the<00:49:42.780> wallet<00:49:43.110> which<00:49:43.380> supports 00:49:44.000 --> 00:49:44.010 align:start position:0% makes a within the wallet which supports 00:49:44.010 --> 00:49:46.100 align:start position:0% makes a within the wallet which supports eventually<00:49:44.460> we<00:49:45.000> can<00:49:45.120> display<00:49:45.510> the<00:49:45.540> function 00:49:46.100 --> 00:49:46.110 align:start position:0% eventually we can display the function 00:49:46.110 --> 00:49:51.440 align:start position:0% eventually we can display the function in<00:49:46.350> the<00:49:46.470> admins<00:49:46.970> what<00:49:47.970> if<00:49:48.060> that<00:49:48.210> so<00:49:48.540> you<00:49:50.450> can 00:49:51.440 --> 00:49:51.450 align:start position:0% in the admins what if that so you can 00:49:51.450 --> 00:49:54.290 align:start position:0% in the admins what if that so you can see<00:49:51.690> my<00:49:51.870> single<00:49:52.290> inactivity<00:49:53.190> which<00:49:53.610> is<00:49:53.820> what 00:49:54.290 --> 00:49:54.300 align:start position:0% see my single inactivity which is what 00:49:54.300 --> 00:49:56.170 align:start position:0% see my single inactivity which is what it<00:49:54.450> means<00:49:54.600> because<00:49:54.780> it<00:49:55.170> is<00:49:55.290> built<00:49:55.680> and 00:49:56.170 --> 00:49:56.180 align:start position:0% it means because it is built and 00:49:56.180 --> 00:49:59.900 align:start position:0% it means because it is built and transported<00:49:57.180> as<00:49:57.360> one<00:49:57.720> single<00:49:58.020> program<00:49:58.760> we<00:49:59.760> can 00:49:59.900 --> 00:49:59.910 align:start position:0% transported as one single program we can 00:49:59.910 --> 00:50:03.980 align:start position:0% transported as one single program we can let<00:50:00.180> author<00:50:00.960> of<00:50:01.320> the<00:50:01.440> XML<00:50:01.830> site<00:50:02.990> expression 00:50:03.980 --> 00:50:03.990 align:start position:0% let author of the XML site expression 00:50:03.990 --> 00:50:07.370 align:start position:0% let author of the XML site expression trust<00:50:04.550> Squad<00:50:05.550> contract<00:50:06.000> so<00:50:06.810> when<00:50:07.080> the<00:50:07.230> user 00:50:07.370 --> 00:50:07.380 align:start position:0% trust Squad contract so when the user 00:50:07.380 --> 00:50:10.340 align:start position:0% trust Squad contract so when the user use<00:50:07.770> it<00:50:07.980> you'll<00:50:08.160> be<00:50:08.310> like<00:50:08.490> using<00:50:08.640> a<00:50:09.350> web 00:50:10.340 --> 00:50:10.350 align:start position:0% use it you'll be like using a web 00:50:10.350 --> 00:50:12.350 align:start position:0% use it you'll be like using a web browser<00:50:10.380> in<00:50:10.890> visit<00:50:11.250> website<00:50:11.790> you<00:50:11.910> see<00:50:11.940> lock 00:50:12.350 --> 00:50:12.360 align:start position:0% browser in visit website you see lock 00:50:12.360 --> 00:50:14.210 align:start position:0% browser in visit website you see lock and<00:50:13.050> you<00:50:13.140> can<00:50:13.260> click<00:50:13.470> on<00:50:13.560> the<00:50:13.680> mark<00:50:13.890> and<00:50:14.040> see 00:50:14.210 --> 00:50:14.220 align:start position:0% and you can click on the mark and see 00:50:14.220 --> 00:50:16.250 align:start position:0% and you can click on the mark and see that<00:50:14.370> this<00:50:14.460> is<00:50:14.520> verified<00:50:15.090> by<00:50:15.120> you<00:50:15.390> and<00:50:15.900> this<00:50:16.050> is 00:50:16.250 --> 00:50:16.260 align:start position:0% that this is verified by you and this is 00:50:16.260 --> 00:50:25.820 align:start position:0% that this is verified by you and this is a<00:50:16.290> certificate<00:50:17.300> for<00:50:18.300> this<00:50:24.680> there<00:50:25.680> may<00:50:25.800> be 00:50:25.820 --> 00:50:25.830 align:start position:0% a certificate for this there may be 00:50:25.830 --> 00:50:27.110 align:start position:0% a certificate for this there may be standards<00:50:26.370> in<00:50:26.490> certain<00:50:26.760> ways<00:50:26.880> of<00:50:26.910> doing 00:50:27.110 --> 00:50:27.120 align:start position:0% standards in certain ways of doing 00:50:27.120 --> 00:50:38.300 align:start position:0% standards in certain ways of doing things<00:50:35.630> we<00:50:36.630> cannot<00:50:36.840> rely<00:50:37.200> on<00:50:37.230> any<00:50:37.650> centralized 00:50:38.300 --> 00:50:38.310 align:start position:0% things we cannot rely on any centralized 00:50:38.310 --> 00:50:40.760 align:start position:0% things we cannot rely on any centralized Authority<00:50:39.180> Google<00:50:39.540> say<00:50:39.720> is<00:50:39.960> it<00:50:40.080> certified<00:50:40.620> or 00:50:40.760 --> 00:50:40.770 align:start position:0% Authority Google say is it certified or 00:50:40.770 --> 00:50:43.220 align:start position:0% Authority Google say is it certified or not<00:50:41.010> no<00:50:41.400> this<00:50:41.970> is<00:50:42.120> based<00:50:42.420> on<00:50:42.570> a<00:50:42.600> chain<00:50:42.870> of<00:50:43.020> trust 00:50:43.220 --> 00:50:43.230 align:start position:0% not no this is based on a chain of trust 00:50:43.230 --> 00:50:45.950 align:start position:0% not no this is based on a chain of trust because<00:50:43.770> you<00:50:44.010> can<00:50:44.370> trust<00:50:44.670> that<00:50:44.850> the<00:50:45.180> signer<00:50:45.540> of 00:50:45.950 --> 00:50:45.960 align:start position:0% because you can trust that the signer of 00:50:45.960 --> 00:50:48.230 align:start position:0% because you can trust that the signer of this<00:50:46.320> Wow 00:50:48.230 --> 00:50:48.240 align:start position:0% this Wow 00:50:48.240 --> 00:50:50.750 align:start position:0% this Wow is<00:50:48.510> asserting<00:50:49.110> that<00:50:49.140> this<00:50:49.770> smart<00:50:50.370> contract 00:50:50.750 --> 00:50:50.760 align:start position:0% is asserting that this smart contract 00:50:50.760 --> 00:50:51.210 align:start position:0% is asserting that this smart contract can<00:50:50.940> be 00:50:51.210 --> 00:50:51.220 align:start position:0% can be 00:50:51.220 --> 00:50:53.640 align:start position:0% can be because<00:50:52.030> as<00:50:52.150> a<00:50:52.180> user<00:50:52.569> when<00:50:52.869> you<00:50:52.930> use<00:50:53.140> equality 00:50:53.640 --> 00:50:53.650 align:start position:0% because as a user when you use equality 00:50:53.650 --> 00:50:55.370 align:start position:0% because as a user when you use equality we're<00:50:53.920> not<00:50:54.040> going<00:50:54.220> to<00:50:54.339> get<00:50:54.730> the<00:50:54.910> sauce 00:50:55.370 --> 00:50:55.380 align:start position:0% we're not going to get the sauce 00:50:55.380 --> 00:50:58.950 align:start position:0% we're not going to get the sauce contract<00:50:56.380> it's<00:50:56.950> very<00:50:57.160> unlikely<00:50:57.780> source<00:50:58.780> code 00:50:58.950 --> 00:50:58.960 align:start position:0% contract it's very unlikely source code 00:50:58.960 --> 00:51:00.809 align:start position:0% contract it's very unlikely source code and<00:50:59.170> even<00:50:59.380> if<00:50:59.500> you<00:50:59.619> can<00:50:59.829> find<00:51:00.220> the<00:51:00.400> source<00:51:00.640> code 00:51:00.809 --> 00:51:00.819 align:start position:0% and even if you can find the source code 00:51:00.819 --> 00:51:03.059 align:start position:0% and even if you can find the source code for<00:51:01.000> expand<00:51:01.329> contract<00:51:01.540> how<00:51:02.170> do<00:51:02.230> you<00:51:02.440> associate 00:51:03.059 --> 00:51:03.069 align:start position:0% for expand contract how do you associate 00:51:03.069 --> 00:51:05.849 align:start position:0% for expand contract how do you associate that<00:51:03.609> back<00:51:03.940> to<00:51:04.210> the<00:51:04.329> button<00:51:04.660> is<00:51:04.869> really<00:51:04.990> key<00:51:05.380> is 00:51:05.849 --> 00:51:05.859 align:start position:0% that back to the button is really key is 00:51:05.859 --> 00:51:09.120 align:start position:0% that back to the button is really key is that<00:51:06.220> going<00:51:06.520> to<00:51:06.760> call<00:51:07.450> this<00:51:07.660> one<00:51:07.930> but<00:51:08.770> if<00:51:09.010> you 00:51:09.120 --> 00:51:09.130 align:start position:0% that going to call this one but if you 00:51:09.130 --> 00:51:10.890 align:start position:0% that going to call this one but if you see<00:51:09.280> a<00:51:09.310> lot<00:51:09.579> like<00:51:09.910> when<00:51:10.119> you<00:51:10.270> are<00:51:10.420> in<00:51:10.630> the<00:51:10.720> web 00:51:10.890 --> 00:51:10.900 align:start position:0% see a lot like when you are in the web 00:51:10.900 --> 00:51:13.349 align:start position:0% see a lot like when you are in the web browser<00:51:11.319> you<00:51:11.950> see<00:51:11.980> that<00:51:12.280> it<00:51:12.430> has<00:51:12.579> a<00:51:12.609> very<00:51:12.700> HD 00:51:13.349 --> 00:51:13.359 align:start position:0% browser you see that it has a very HD 00:51:13.359 --> 00:51:16.380 align:start position:0% browser you see that it has a very HD TLS<00:51:14.170> certificate<00:51:14.800> then<00:51:15.250> to<00:51:15.579> a<00:51:15.609> certain<00:51:15.970> extent 00:51:16.380 --> 00:51:16.390 align:start position:0% TLS certificate then to a certain extent 00:51:16.390 --> 00:51:18.510 align:start position:0% TLS certificate then to a certain extent because<00:51:16.569> we<00:51:17.260> know<00:51:17.440> that<00:51:17.470> this<00:51:17.829> certificate<00:51:18.069> is 00:51:18.510 --> 00:51:18.520 align:start position:0% because we know that this certificate is 00:51:18.520 --> 00:51:21.150 align:start position:0% because we know that this certificate is issued<00:51:18.730> by<00:51:19.060> say<00:51:19.270> very<00:51:19.690> signed<00:51:20.050> by<00:51:20.800> train<00:51:21.040> of 00:51:21.150 --> 00:51:21.160 align:start position:0% issued by say very signed by train of 00:51:21.160 --> 00:51:24.329 align:start position:0% issued by say very signed by train of trust<00:51:21.430> you<00:51:22.359> trust<00:51:22.630> that<00:51:22.869> this<00:51:23.380> website<00:51:23.829> they 00:51:24.329 --> 00:51:24.339 align:start position:0% trust you trust that this website they 00:51:24.339 --> 00:51:26.099 align:start position:0% trust you trust that this website they say<00:51:24.550> they<00:51:24.730> are<00:51:24.849> and<00:51:25.150> we<00:51:25.300> can<00:51:25.329> trust<00:51:25.690> anything 00:51:26.099 --> 00:51:26.109 align:start position:0% say they are and we can trust anything 00:51:26.109 --> 00:51:28.339 align:start position:0% say they are and we can trust anything by<00:51:26.349> product<00:51:26.920> for<00:51:27.130> this<00:51:27.310> website<00:51:27.550> using<00:51:28.030> your 00:51:28.339 --> 00:51:28.349 align:start position:0% by product for this website using your 00:51:28.349 --> 00:51:31.020 align:start position:0% by product for this website using your chain<00:51:29.349> of<00:51:29.470> trust<00:51:29.650> so<00:51:30.579> you<00:51:30.609> wouldn't<00:51:30.849> have<00:51:30.970> to 00:51:31.020 --> 00:51:31.030 align:start position:0% chain of trust so you wouldn't have to 00:51:31.030 --> 00:51:34.230 align:start position:0% chain of trust so you wouldn't have to use<00:51:31.270> you<00:51:31.839> know<00:51:31.960> regular<00:51:32.740> CSS<00:51:33.220> if<00:51:33.910> you've<00:51:34.060> got 00:51:34.230 --> 00:51:34.240 align:start position:0% use you know regular CSS if you've got 00:51:34.240 --> 00:51:39.720 align:start position:0% use you know regular CSS if you've got CCGs<00:51:36.329> elliptically<00:51:37.349> signing<00:51:38.349> up<00:51:38.670> seven<00:51:39.670> you 00:51:39.720 --> 00:51:39.730 align:start position:0% CCGs elliptically signing up seven you 00:51:39.730 --> 00:51:43.020 align:start position:0% CCGs elliptically signing up seven you just<00:51:39.940> sign<00:51:40.240> by<00:51:40.630> it<00:51:41.230> could<00:51:41.410> still<00:51:41.740> be<00:51:42.030> sued 00:51:43.020 --> 00:51:43.030 align:start position:0% just sign by it could still be sued 00:51:43.030 --> 00:51:45.809 align:start position:0% just sign by it could still be sued owners<00:51:43.300> like<00:51:44.170> there<00:51:44.380> if<00:51:45.010> you've<00:51:45.250> got<00:51:45.400> if<00:51:45.579> you 00:51:45.809 --> 00:51:45.819 align:start position:0% owners like there if you've got if you 00:51:45.819 --> 00:51:47.370 align:start position:0% owners like there if you've got if you control<00:51:46.210> an<00:51:46.329> address<00:51:46.630> and<00:51:46.930> there's<00:51:47.109> a<00:51:47.170> private 00:51:47.370 --> 00:51:47.380 align:start position:0% control an address and there's a private 00:51:47.380 --> 00:51:48.550 align:start position:0% control an address and there's a private key 00:51:48.550 --> 00:51:48.560 align:start position:0% key 00:51:48.560 --> 00:51:55.290 align:start position:0% key [Music] 00:51:55.290 --> 00:51:55.300 align:start position:0% 00:51:55.300 --> 00:52:21.130 align:start position:0% [Music] 00:52:21.130 --> 00:52:21.140 align:start position:0% 00:52:21.140 --> 00:52:40.930 align:start position:0% [Music] 00:52:40.930 --> 00:52:40.940 align:start position:0% 00:52:40.940 --> 00:52:44.839 align:start position:0% they're<00:52:41.940> pretty<00:52:42.510> but<00:52:43.440> we<00:52:44.099> also<00:52:44.369> have<00:52:44.670> like 00:52:44.839 --> 00:52:44.849 align:start position:0% they're pretty but we also have like 00:52:44.849 --> 00:52:49.010 align:start position:0% they're pretty but we also have like fire<00:52:45.540> also<00:52:46.579> but<00:52:47.579> what<00:52:47.820> we<00:52:47.910> focus<00:52:48.300> is<00:52:48.510> more 00:52:49.010 --> 00:52:49.020 align:start position:0% fire also but what we focus is more 00:52:49.020 --> 00:52:51.589 align:start position:0% fire also but what we focus is more developer-friendly<00:52:50.010> wait<00:52:50.490> the<00:52:51.150> reason<00:52:51.480> for 00:52:51.589 --> 00:52:51.599 align:start position:0% developer-friendly wait the reason for 00:52:51.599 --> 00:52:53.300 align:start position:0% developer-friendly wait the reason for that<00:52:51.660> is<00:52:51.960> actually<00:52:52.140> we<00:52:52.560> care<00:52:52.859> about<00:52:52.950> the 00:52:53.300 --> 00:52:53.310 align:start position:0% that is actually we care about the 00:52:53.310 --> 00:52:57.200 align:start position:0% that is actually we care about the privacy<00:52:53.819> so<00:52:54.650> what<00:52:55.650> we<00:52:55.829> have<00:52:56.220> was<00:52:56.579> like<00:52:56.880> we<00:52:57.089> have 00:52:57.200 --> 00:52:57.210 align:start position:0% privacy so what we have was like we have 00:52:57.210 --> 00:53:00.580 align:start position:0% privacy so what we have was like we have to<00:52:57.240> publish<00:52:57.690> all<00:52:57.869> the<00:52:57.900> source<00:52:58.290> code 00:53:00.580 --> 00:53:00.590 align:start position:0% 00:53:00.590 --> 00:53:04.580 align:start position:0% but<00:53:01.590> most<00:53:02.580> of<00:53:02.730> our<00:53:02.850> clients<00:53:03.270> you<00:53:04.260> might<00:53:04.440> be 00:53:04.580 --> 00:53:04.590 align:start position:0% but most of our clients you might be 00:53:04.590 --> 00:53:06.230 align:start position:0% but most of our clients you might be like<00:53:04.740> it's<00:53:05.010> pretty<00:53:05.340> immature<00:53:05.580> but<00:53:06.000> then<00:53:06.150> he 00:53:06.230 --> 00:53:06.240 align:start position:0% like it's pretty immature but then he 00:53:06.240 --> 00:53:08.240 align:start position:0% like it's pretty immature but then he doesn't<00:53:06.390> want<00:53:06.660> to<00:53:06.900> share<00:53:07.170> their<00:53:07.470> code<00:53:08.010> before 00:53:08.240 --> 00:53:08.250 align:start position:0% doesn't want to share their code before 00:53:08.250 --> 00:53:13.210 align:start position:0% doesn't want to share their code before publishers<00:53:09.210> because<00:53:10.730> yeah<00:53:11.730> so<00:53:12.210> we<00:53:12.780> have<00:53:12.960> to 00:53:13.210 --> 00:53:13.220 align:start position:0% publishers because yeah so we have to 00:53:13.220 --> 00:53:17.060 align:start position:0% publishers because yeah so we have to fill<00:53:14.220> some<00:53:14.520> technology<00:53:15.150> or<00:53:15.540> which<00:53:16.470> is<00:53:16.680> keeping 00:53:17.060 --> 00:53:17.070 align:start position:0% fill some technology or which is keeping 00:53:17.070 --> 00:53:20.030 align:start position:0% fill some technology or which is keeping liquid<00:53:17.520> crises<00:53:18.000> so<00:53:18.270> what<00:53:19.050> we<00:53:19.200> expect<00:53:19.740> from<00:53:19.830> the 00:53:20.030 --> 00:53:20.040 align:start position:0% liquid crises so what we expect from the 00:53:20.040 --> 00:53:22.700 align:start position:0% liquid crises so what we expect from the source<00:53:20.310> code<00:53:20.550> is<00:53:20.760> some<00:53:21.450> good<00:53:21.720> pattern<00:53:22.080> not 00:53:22.700 --> 00:53:22.710 align:start position:0% source code is some good pattern not 00:53:22.710 --> 00:53:24.920 align:start position:0% source code is some good pattern not just<00:53:22.920> source<00:53:23.130> good<00:53:23.340> exact<00:53:23.700> but<00:53:23.970> more<00:53:24.840> an 00:53:24.920 --> 00:53:24.930 align:start position:0% just source good exact but more an 00:53:24.930 --> 00:53:28.370 align:start position:0% just source good exact but more an abstracted<00:53:25.410> could<00:53:25.890> like<00:53:27.140> intervener<00:53:28.140> video 00:53:28.370 --> 00:53:28.380 align:start position:0% abstracted could like intervener video 00:53:28.380 --> 00:53:31.100 align:start position:0% abstracted could like intervener video like<00:53:28.860> uses<00:53:29.070> like<00:53:29.190> that<00:53:29.400> so<00:53:29.700> we<00:53:29.880> expect<00:53:30.780> it<00:53:30.960> and 00:53:31.100 --> 00:53:31.110 align:start position:0% like uses like that so we expect it and 00:53:31.110 --> 00:53:32.960 align:start position:0% like uses like that so we expect it and then<00:53:31.230> make<00:53:31.500> a<00:53:31.530> signature<00:53:31.950> of<00:53:32.100> that<00:53:32.220> and<00:53:32.790> then 00:53:32.960 --> 00:53:32.970 align:start position:0% then make a signature of that and then 00:53:32.970 --> 00:53:37.820 align:start position:0% then make a signature of that and then we<00:53:33.240> just<00:53:34.400> give<00:53:35.400> and<00:53:35.970> the<00:53:36.750> clients<00:53:37.140> it<00:53:37.320> just 00:53:37.820 --> 00:53:37.830 align:start position:0% we just give and the clients it just 00:53:37.830 --> 00:53:41.420 align:start position:0% we just give and the clients it just that<00:53:38.100> signature<00:53:38.580> so<00:53:39.420> based<00:53:40.050> on<00:53:40.170> our<00:53:40.430> database 00:53:41.420 --> 00:53:41.430 align:start position:0% that signature so based on our database 00:53:41.430 --> 00:53:43.670 align:start position:0% that signature so based on our database we<00:53:41.610> just<00:53:41.820> starts<00:53:42.060> from<00:53:42.180> academics<00:53:42.810> so<00:53:43.020> we<00:53:43.500> just 00:53:43.670 --> 00:53:43.680 align:start position:0% we just starts from academics so we just 00:53:43.680 --> 00:53:46.220 align:start position:0% we just starts from academics so we just need<00:53:43.920> with<00:53:44.370> no<00:53:44.490> source<00:53:44.760> code<00:53:44.970> so<00:53:45.660> it's<00:53:45.960> similar 00:53:46.220 --> 00:53:46.230 align:start position:0% need with no source code so it's similar 00:53:46.230 --> 00:53:48.620 align:start position:0% need with no source code so it's similar to<00:53:46.530> the<00:53:46.650> traditional<00:53:47.460> Java<00:53:47.730> software<00:53:48.000> and 00:53:48.620 --> 00:53:48.630 align:start position:0% to the traditional Java software and 00:53:48.630 --> 00:53:53.510 align:start position:0% to the traditional Java software and games<00:53:50.780> vulnerabilities<00:53:51.780> or<00:53:51.990> the<00:53:52.770> algorithm 00:53:53.510 --> 00:53:53.520 align:start position:0% games vulnerabilities or the algorithm 00:53:53.520 --> 00:53:56.390 align:start position:0% games vulnerabilities or the algorithm contact<00:53:54.300> so<00:53:54.930> it<00:53:55.050> could<00:53:55.230> be<00:53:55.260> achieved<00:53:55.770> more 00:53:56.390 --> 00:53:56.400 align:start position:0% contact so it could be achieved more 00:53:56.400 --> 00:54:09.950 align:start position:0% contact so it could be achieved more good<00:53:57.060> privacy<00:53:57.390> first<00:54:08.300> all<00:54:09.300> the<00:54:09.480> signature 00:54:09.950 --> 00:54:09.960 align:start position:0% good privacy first all the signature 00:54:09.960 --> 00:54:15.770 align:start position:0% good privacy first all the signature from<00:54:10.200> that<00:54:10.500> we<00:54:10.650> best<00:54:11.070> from<00:54:11.370> the<00:54:14.780> trust 00:54:15.770 --> 00:54:15.780 align:start position:0% from that we best from the trust 00:54:15.780 --> 00:54:17.060 align:start position:0% from that we best from the trust business<00:54:15.990> I<00:54:16.320> was<00:54:16.470> thinking<00:54:16.800> that<00:54:16.830> maybe 00:54:17.060 --> 00:54:17.070 align:start position:0% business I was thinking that maybe 00:54:17.070 --> 00:54:19.730 align:start position:0% business I was thinking that maybe offered<00:54:17.910> that<00:54:18.030> nobody<00:54:18.390> else's<00:54:19.170> like<00:54:19.200> focus<00:54:19.650> on 00:54:19.730 --> 00:54:19.740 align:start position:0% offered that nobody else's like focus on 00:54:19.740 --> 00:54:23.600 align:start position:0% offered that nobody else's like focus on this<00:54:19.860> more<00:54:20.130> or<00:54:20.520> more<00:54:21.380> decentralized<00:54:22.380> so<00:54:23.370> clear 00:54:23.600 --> 00:54:23.610 align:start position:0% this more or more decentralized so clear 00:54:23.610 --> 00:54:25.210 align:start position:0% this more or more decentralized so clear to<00:54:23.820> anyone 00:54:25.210 --> 00:54:25.220 align:start position:0% to anyone 00:54:25.220 --> 00:54:27.850 align:start position:0% to anyone I<00:54:25.250> mean<00:54:25.550> the<00:54:25.880> way<00:54:26.290> it's<00:54:27.290> it's<00:54:27.500> maybe<00:54:27.680> a<00:54:27.800> little 00:54:27.850 --> 00:54:27.860 align:start position:0% I mean the way it's it's maybe a little 00:54:27.860 --> 00:54:29.770 align:start position:0% I mean the way it's it's maybe a little early<00:54:28.340> but<00:54:28.370> like<00:54:28.700> the<00:54:29.090> way<00:54:29.120> we<00:54:29.330> were<00:54:29.510> thinking 00:54:29.770 --> 00:54:29.780 align:start position:0% early but like the way we were thinking 00:54:29.780 --> 00:54:33.070 align:start position:0% early but like the way we were thinking about<00:54:30.740> supporting<00:54:31.700> that<00:54:32.330> kind<00:54:32.540> of<00:54:32.660> keeps<00:54:32.840> kids 00:54:33.070 --> 00:54:33.080 align:start position:0% about supporting that kind of keeps kids 00:54:33.080 --> 00:54:35.470 align:start position:0% about supporting that kind of keeps kids like<00:54:33.260> if<00:54:33.650> you<00:54:33.740> want<00:54:33.920> to<00:54:34.010> publish<00:54:34.310> the<00:54:35.030> contract 00:54:35.470 --> 00:54:35.480 align:start position:0% like if you want to publish the contract 00:54:35.480 --> 00:54:37.210 align:start position:0% like if you want to publish the contract with<00:54:35.600> an<00:54:35.750> full<00:54:36.020> audit<00:54:36.380> or<00:54:36.530> maybe<00:54:36.740> you<00:54:37.190> just 00:54:37.210 --> 00:54:37.220 align:start position:0% with an full audit or maybe you just 00:54:37.220 --> 00:54:39.310 align:start position:0% with an full audit or maybe you just want<00:54:37.550> to<00:54:37.610> say<00:54:37.850> that<00:54:38.570> contract<00:54:38.870> that<00:54:38.930> is<00:54:39.080> behind 00:54:39.310 --> 00:54:39.320 align:start position:0% want to say that contract that is behind 00:54:39.320 --> 00:54:40.930 align:start position:0% want to say that contract that is behind an<00:54:39.440> ad<00:54:39.590> versus<00:54:39.860> private<00:54:40.220> but<00:54:40.340> we<00:54:40.460> have<00:54:40.580> an 00:54:40.930 --> 00:54:40.940 align:start position:0% an ad versus private but we have an 00:54:40.940 --> 00:54:44.050 align:start position:0% an ad versus private but we have an audit<00:54:41.300> department<00:54:41.900> that<00:54:42.470> we<00:54:42.620> share<00:54:42.860> fully<00:54:43.760> or 00:54:44.050 --> 00:54:44.060 align:start position:0% audit department that we share fully or 00:54:44.060 --> 00:54:46.000 align:start position:0% audit department that we share fully or or<00:54:44.300> just<00:54:44.330> like<00:54:44.720> parts<00:54:45.140> of<00:54:45.200> it<00:54:45.350> maybe<00:54:45.770> your 00:54:46.000 --> 00:54:46.010 align:start position:0% or just like parts of it maybe your 00:54:46.010 --> 00:54:47.890 align:start position:0% or just like parts of it maybe your future<00:54:46.130> you<00:54:46.490> want<00:54:46.610> to<00:54:46.790> share<00:54:47.030> more<00:54:47.240> or<00:54:47.720> you 00:54:47.890 --> 00:54:47.900 align:start position:0% future you want to share more or you 00:54:47.900 --> 00:54:51.250 align:start position:0% future you want to share more or you share<00:54:48.440> it<00:54:48.590> the<00:54:48.770> next<00:54:48.950> time<00:54:49.480> this<00:54:50.480> is<00:54:50.540> your 00:54:51.250 --> 00:54:51.260 align:start position:0% share it the next time this is your 00:54:51.260 --> 00:54:54.420 align:start position:0% share it the next time this is your database<00:54:51.530> no<00:54:51.910> it's<00:54:52.910> open<00:54:53.060> source<00:54:53.390> in<00:54:53.720> London 00:54:54.420 --> 00:54:54.430 align:start position:0% database no it's open source in London 00:54:54.430 --> 00:54:58.900 align:start position:0% database no it's open source in London you<00:54:55.430> have<00:54:56.590> global<00:54:57.590> public<00:54:58.310> address<00:54:58.670> as<00:54:58.880> a 00:54:58.900 --> 00:54:58.910 align:start position:0% you have global public address as a 00:54:58.910 --> 00:55:01.660 align:start position:0% you have global public address as a public<00:54:59.750> key<00:54:59.930> and<00:55:00.290> you<00:55:00.680> it's<00:55:01.010> a<00:55:01.160> it's<00:55:01.430> like<00:55:01.520> a 00:55:01.660 --> 00:55:01.670 align:start position:0% public key and you it's a it's like a 00:55:01.670 --> 00:55:04.930 align:start position:0% public key and you it's a it's like a torrent<00:55:02.150> which<00:55:02.990> means<00:55:03.260> you<00:55:03.890> can<00:55:04.100> start<00:55:04.700> adding 00:55:04.930 --> 00:55:04.940 align:start position:0% torrent which means you can start adding 00:55:04.940 --> 00:55:15.340 align:start position:0% torrent which means you can start adding all<00:55:05.480> this<00:55:05.750> information<00:55:06.680> so<00:55:07.160> that<00:55:14.350> but 00:55:15.340 --> 00:55:15.350 align:start position:0% all this information so that but 00:55:15.350 --> 00:55:17.380 align:start position:0% all this information so that but everyone<00:55:15.890> what's<00:55:16.640> are<00:55:16.790> running<00:55:17.090> the<00:55:17.210> same 00:55:17.380 --> 00:55:17.390 align:start position:0% everyone what's are running the same 00:55:17.390 --> 00:55:20.200 align:start position:0% everyone what's are running the same note<00:55:17.830> you<00:55:18.830> might<00:55:18.950> also<00:55:19.160> hear<00:55:19.460> auditors<00:55:20.000> or 00:55:20.200 --> 00:55:20.210 align:start position:0% note you might also hear auditors or 00:55:20.210 --> 00:55:39.870 align:start position:0% note you might also hear auditors or other<00:55:20.420> parties<00:55:20.870> that<00:55:21.080> can<00:55:21.320> do<00:55:21.650> the<00:55:21.740> same 00:55:39.870 --> 00:55:39.880 align:start position:0% 00:55:39.880 --> 00:55:48.160 align:start position:0% [Music] 00:55:48.160 --> 00:55:48.170 align:start position:0% 00:55:48.170 --> 00:56:21.049 align:start position:0% in<00:55:49.170> the<00:55:52.069> others<00:55:54.170> too<00:55:55.170> and<00:56:19.519> the<00:56:20.519> most<00:56:20.700> important 00:56:21.049 --> 00:56:21.059 align:start position:0% in the others too and the most important 00:56:21.059 --> 00:56:22.400 align:start position:0% in the others too and the most important thing<00:56:21.210> is<00:56:21.359> this<00:56:21.510> like<00:56:21.690> nobody<00:56:22.019> is<00:56:22.109> one 00:56:22.400 --> 00:56:22.410 align:start position:0% thing is this like nobody is one 00:56:22.410 --> 00:56:24.470 align:start position:0% thing is this like nobody is one maintainer<00:56:22.950> and<00:56:23.339> there<00:56:23.970> is<00:56:24.089> not<00:56:24.269> like 00:56:24.470 --> 00:56:24.480 align:start position:0% maintainer and there is not like 00:56:24.480 --> 00:56:27.079 align:start position:0% maintainer and there is not like database<00:56:25.260> of<00:56:25.740> everything<00:56:26.220> everywhere<00:56:26.819> but 00:56:27.079 --> 00:56:27.089 align:start position:0% database of everything everywhere but 00:56:27.089 --> 00:56:29.240 align:start position:0% database of everything everywhere but nobody<00:56:27.240> collects<00:56:27.900> them<00:56:28.079> or<00:56:28.380> if<00:56:28.619> they<00:56:28.799> do<00:56:29.009> then 00:56:29.240 --> 00:56:29.250 align:start position:0% nobody collects them or if they do then 00:56:29.250 --> 00:56:30.769 align:start position:0% nobody collects them or if they do then they<00:56:29.400> have<00:56:29.579> like<00:56:29.609> a<00:56:29.759> crazy<00:56:30.059> power<00:56:30.359> because 00:56:30.769 --> 00:56:30.779 align:start position:0% they have like a crazy power because 00:56:30.779 --> 00:56:33.470 align:start position:0% they have like a crazy power because then<00:56:30.960> they<00:56:31.109> have<00:56:31.619> all<00:56:31.769> the<00:56:31.890> data<00:56:32.089> so<00:56:33.089> this<00:56:33.240> kind 00:56:33.470 --> 00:56:33.480 align:start position:0% then they have all the data so this kind 00:56:33.480 --> 00:56:35.990 align:start position:0% then they have all the data so this kind of<00:56:33.539> system<00:56:33.750> will<00:56:34.140> help<00:56:34.410> us<00:56:34.619> that<00:56:34.769> we<00:56:34.950> all<00:56:35.220> share 00:56:35.990 --> 00:56:36.000 align:start position:0% of system will help us that we all share 00:56:36.000 --> 00:56:39.380 align:start position:0% of system will help us that we all share this<00:56:36.779> data<00:56:36.990> if<00:56:37.440> we<00:56:37.559> go<00:56:37.769> means<00:56:38.039> to<00:56:38.579> do<00:56:38.970> something 00:56:39.380 --> 00:56:39.390 align:start position:0% this data if we go means to do something 00:56:39.390 --> 00:56:41.210 align:start position:0% this data if we go means to do something like<00:56:39.480> this<00:56:39.660> or<00:56:39.900> you<00:56:40.380> can<00:56:40.529> find<00:56:40.740> better<00:56:40.890> ways 00:56:41.210 --> 00:56:41.220 align:start position:0% like this or you can find better ways 00:56:41.220 --> 00:56:43.039 align:start position:0% like this or you can find better ways thank<00:56:41.549> God<00:56:41.730> I<00:56:41.910> mean<00:56:42.059> but<00:56:42.329> this<00:56:42.599> is<00:56:42.660> an<00:56:42.900> our 00:56:43.039 --> 00:56:43.049 align:start position:0% thank God I mean but this is an our 00:56:43.049 --> 00:56:47.730 align:start position:0% thank God I mean but this is an our suggestion<00:56:43.769> so 00:56:47.730 --> 00:56:47.740 align:start position:0% 00:56:47.740 --> 00:56:50.430 align:start position:0% very<00:56:48.670> beginning<00:56:49.030> but<00:56:49.720> you<00:56:49.810> have<00:56:49.960> one<00:56:50.170> product 00:56:50.430 --> 00:56:50.440 align:start position:0% very beginning but you have one product 00:56:50.440 --> 00:56:52.260 align:start position:0% very beginning but you have one product in<00:56:50.770> your<00:56:50.890> delivery<00:56:51.160> of<00:56:51.520> that<00:56:51.640> contract<00:56:51.970> so<00:56:52.150> the 00:56:52.260 --> 00:56:52.270 align:start position:0% in your delivery of that contract so the 00:56:52.270 --> 00:56:54.089 align:start position:0% in your delivery of that contract so the author<00:56:52.480> could<00:56:53.109> pop<00:56:53.320> continuously<00:56:53.859> published 00:56:54.089 --> 00:56:54.099 align:start position:0% author could pop continuously published 00:56:54.099 --> 00:56:56.070 align:start position:0% author could pop continuously published two<00:56:54.400> different<00:56:54.730> versions<00:56:54.910> and<00:56:55.300> it<00:56:55.780> would<00:56:55.869> all 00:56:56.070 --> 00:56:56.080 align:start position:0% two different versions and it would all 00:56:56.080 --> 00:56:59.339 align:start position:0% two different versions and it would all be<00:56:56.109> available<00:56:57.480> version<00:56:58.480> controlled<00:56:58.869> through 00:56:59.339 --> 00:56:59.349 align:start position:0% be available version controlled through 00:56:59.349 --> 00:57:01.710 align:start position:0% be available version controlled through all<00:56:59.589> the<00:56:59.800> different<00:57:00.250> versions<00:57:00.760> over<00:57:01.450> the<00:57:01.570> life 00:57:01.710 --> 00:57:01.720 align:start position:0% all the different versions over the life 00:57:01.720 --> 00:57:04.020 align:start position:0% all the different versions over the life of<00:57:01.869> the<00:57:02.109> contract<00:57:02.320> and<00:57:02.710> because<00:57:03.670> they're<00:57:03.849> in 00:57:04.020 --> 00:57:04.030 align:start position:0% of the contract and because they're in 00:57:04.030 --> 00:57:07.440 align:start position:0% of the contract and because they're in that<00:57:04.150> same<00:57:04.420> standard<00:57:05.369> system<00:57:06.369> you<00:57:07.000> could<00:57:07.210> for 00:57:07.440 --> 00:57:07.450 align:start position:0% that same standard system you could for 00:57:07.450 --> 00:57:10.200 align:start position:0% that same standard system you could for example<00:57:07.480> not<00:57:07.930> publish<00:57:08.560> the<00:57:08.589> entire<00:57:09.210> source 00:57:10.200 --> 00:57:10.210 align:start position:0% example not publish the entire source 00:57:10.210 --> 00:57:12.930 align:start position:0% example not publish the entire source code<00:57:10.300> but<00:57:10.599> they<00:57:10.750> if<00:57:11.710> you<00:57:12.070> want<00:57:12.369> to<00:57:12.580> do<00:57:12.700> that<00:57:12.790> you 00:57:12.930 --> 00:57:12.940 align:start position:0% code but they if you want to do that you 00:57:12.940 --> 00:57:15.990 align:start position:0% code but they if you want to do that you could<00:57:13.089> basically<00:57:13.270> point<00:57:13.780> to<00:57:14.560> that<00:57:14.980> address<00:57:15.220> of 00:57:15.990 --> 00:57:16.000 align:start position:0% could basically point to that address of 00:57:16.000 --> 00:57:19.079 align:start position:0% could basically point to that address of that<00:57:16.240> source<00:57:16.570> code<00:57:16.810> and<00:57:17.940> annotated<00:57:18.940> and 00:57:19.079 --> 00:57:19.089 align:start position:0% that source code and annotated and 00:57:19.089 --> 00:57:21.270 align:start position:0% that source code and annotated and advantage<00:57:19.990> will<00:57:20.170> be<00:57:20.290> controlled<00:57:20.980> by<00:57:21.130> your 00:57:21.270 --> 00:57:21.280 align:start position:0% advantage will be controlled by your 00:57:21.280 --> 00:57:23.609 align:start position:0% advantage will be controlled by your private<00:57:21.670> key<00:57:21.820> well<00:57:22.300> update<00:57:22.900> of<00:57:23.260> the<00:57:23.380> source 00:57:23.609 --> 00:57:23.619 align:start position:0% private key well update of the source 00:57:23.619 --> 00:57:25.859 align:start position:0% private key well update of the source code<00:57:23.830> is<00:57:24.520> controlled<00:57:25.089> by<00:57:25.150> the<00:57:25.270> private<00:57:25.690> key<00:57:25.839> of 00:57:25.859 --> 00:57:25.869 align:start position:0% code is controlled by the private key of 00:57:25.869 --> 00:57:41.780 align:start position:0% code is controlled by the private key of the<00:57:26.470> author<00:57:26.650> and/or<00:57:27.570> organization<00:57:28.570> further 00:57:41.780 --> 00:57:41.790 align:start position:0% 00:57:41.790 --> 00:57:45.589 align:start position:0% [Music] 00:57:45.589 --> 00:57:45.599 align:start position:0% 00:57:45.599 --> 00:57:51.030 align:start position:0% offer<00:57:46.599> interactive<00:57:48.390> video<00:57:49.390> community<00:57:50.140> to 00:57:51.030 --> 00:57:51.040 align:start position:0% offer interactive video community to 00:57:51.040 --> 00:57:54.630 align:start position:0% offer interactive video community to development<00:57:52.000> the<00:57:52.380> solution<00:57:53.380> or<00:57:53.530> part<00:57:53.920> of<00:57:54.430> the 00:57:54.630 --> 00:57:54.640 align:start position:0% development the solution or part of the 00:57:54.640 --> 00:57:57.390 align:start position:0% development the solution or part of the solution<00:57:54.819> to<00:57:55.540> be<00:57:56.140> part<00:57:56.440> of<00:57:56.710> the<00:57:56.859> protocol 00:57:57.390 --> 00:57:57.400 align:start position:0% solution to be part of the protocol 00:57:57.400 --> 00:58:01.760 align:start position:0% solution to be part of the protocol itself<00:57:57.780> let<00:57:58.780> me<00:57:58.990> imagine<00:57:59.319> this<00:57:59.680> a<00:58:00.040> compiler 00:58:01.760 --> 00:58:01.770 align:start position:0% itself let me imagine this a compiler 00:58:01.770 --> 00:58:07.109 align:start position:0% itself let me imagine this a compiler the<00:58:02.770> compiler<00:58:03.220> is<00:58:03.930> standard<00:58:05.220> when<00:58:06.220> compiled<00:58:07.089> a 00:58:07.109 --> 00:58:07.119 align:start position:0% the compiler is standard when compiled a 00:58:07.119 --> 00:58:10.460 align:start position:0% the compiler is standard when compiled a small<00:58:07.690> ultra<00:58:08.230> it's<00:58:08.829> going<00:58:09.130> to<00:58:09.250> generate<00:58:09.400> a 00:58:10.460 --> 00:58:10.470 align:start position:0% small ultra it's going to generate a 00:58:10.470 --> 00:58:17.440 align:start position:0% small ultra it's going to generate a state<00:58:11.470> and<00:58:11.920> isn't<00:58:12.880> in<00:58:13.089> this<00:58:14.190> contract<00:58:15.190> is 00:58:17.440 --> 00:58:17.450 align:start position:0% state and isn't in this contract is 00:58:17.450 --> 00:58:20.020 align:start position:0% state and isn't in this contract is certified<00:58:18.380> or<00:58:18.740> not<00:58:18.980> available<00:58:19.849> at 00:58:20.020 --> 00:58:20.030 align:start position:0% certified or not available at 00:58:20.030 --> 00:58:24.940 align:start position:0% certified or not available at certification<00:58:21.010> /<00:58:22.299> -<00:58:23.299> embedded<00:58:24.170> functions 00:58:24.940 --> 00:58:24.950 align:start position:0% certification / - embedded functions 00:58:24.950 --> 00:58:27.670 align:start position:0% certification / - embedded functions out-of-the-box<00:58:25.910> coming<00:58:26.569> from<00:58:26.869> the<00:58:27.020> compiler 00:58:27.670 --> 00:58:27.680 align:start position:0% out-of-the-box coming from the compiler 00:58:27.680 --> 00:58:31.809 align:start position:0% out-of-the-box coming from the compiler that's<00:58:28.400> changed<00:58:29.359> the<00:58:29.420> state<00:58:29.869> of<00:58:30.470> the<00:58:31.339> level<00:58:31.670> of 00:58:31.809 --> 00:58:31.819 align:start position:0% that's changed the state of the level of 00:58:31.819 --> 00:58:34.539 align:start position:0% that's changed the state of the level of certification<00:58:32.270> so<00:58:33.140> this<00:58:33.349> is<00:58:33.530> in<00:58:33.710> the<00:58:33.829> protocol 00:58:34.539 --> 00:58:34.549 align:start position:0% certification so this is in the protocol 00:58:34.549 --> 00:58:39.970 align:start position:0% certification so this is in the protocol name<00:58:36.010> whatever<00:58:37.390> company<00:58:38.390> that's<00:58:39.260> benefits 00:58:39.970 --> 00:58:39.980 align:start position:0% name whatever company that's benefits 00:58:39.980 --> 00:58:52.870 align:start position:0% name whatever company that's benefits from<00:58:40.490> this<00:58:40.760> change<00:58:45.160> because<00:58:51.579> because<00:58:52.579> then<00:58:52.730> we 00:58:52.870 --> 00:58:52.880 align:start position:0% from this change because because then we 00:58:52.880 --> 00:58:55.120 align:start position:0% from this change because because then we have<00:58:52.910> to<00:58:53.059> trust<00:58:53.420> certain<00:58:53.930> parties<00:58:54.319> but<00:58:54.859> if<00:58:55.010> you 00:58:55.120 --> 00:58:55.130 align:start position:0% have to trust certain parties but if you 00:58:55.130 --> 00:58:58.240 align:start position:0% have to trust certain parties but if you mean<00:58:56.140> verification<00:58:57.140> in<00:58:57.380> the<00:58:57.500> sense<00:58:57.740> that<00:58:57.890> we 00:58:58.240 --> 00:58:58.250 align:start position:0% mean verification in the sense that we 00:58:58.250 --> 00:59:00.339 align:start position:0% mean verification in the sense that we have<00:58:58.430> accessed<00:58:59.150> that<00:58:59.450> this<00:58:59.630> address<00:59:00.170> we<00:59:00.319> can 00:59:00.339 --> 00:59:00.349 align:start position:0% have accessed that this address we can 00:59:00.349 --> 00:59:06.190 align:start position:0% have accessed that this address we can easily<00:59:01.869> forceful<00:59:02.869> these<00:59:04.030> eventually<00:59:05.030> as<00:59:06.020> you 00:59:06.190 --> 00:59:06.200 align:start position:0% easily forceful these eventually as you 00:59:06.200 --> 00:59:08.549 align:start position:0% easily forceful these eventually as you said<00:59:06.440> there<00:59:06.650> are<00:59:06.940> problems<00:59:07.940> like<00:59:08.089> first 00:59:08.549 --> 00:59:08.559 align:start position:0% said there are problems like first 00:59:08.559 --> 00:59:11.099 align:start position:0% said there are problems like first consolidate<00:59:09.559> availability<00:59:10.160> promise 00:59:11.099 --> 00:59:11.109 align:start position:0% consolidate availability promise 00:59:11.109 --> 00:59:13.390 align:start position:0% consolidate availability promise compiler<00:59:12.109> cannot<00:59:12.440> publish<00:59:12.859> it<00:59:13.069> doesn't 00:59:13.390 --> 00:59:13.400 align:start position:0% compiler cannot publish it doesn't 00:59:13.400 --> 00:59:17.470 align:start position:0% compiler cannot publish it doesn't believe<00:59:14.359> on<00:59:14.510> the<00:59:14.630> internet<00:59:15.430> so<00:59:16.430> it's<00:59:16.970> not<00:59:17.180> also 00:59:17.470 --> 00:59:17.480 align:start position:0% believe on the internet so it's not also 00:59:17.480 --> 00:59:22.120 align:start position:0% believe on the internet so it's not also practically<00:59:19.990> not<00:59:20.990> say<00:59:21.200> all<00:59:21.319> that<00:59:21.619> you<00:59:21.680> are 00:59:22.120 --> 00:59:22.130 align:start position:0% practically not say all that you are 00:59:22.130 --> 00:59:27.970 align:start position:0% practically not say all that you are gonna<00:59:22.990> generate<00:59:23.990> the<00:59:24.230> byte<00:59:24.470> code<00:59:26.410> are<00:59:27.410> showing 00:59:27.970 --> 00:59:27.980 align:start position:0% gonna generate the byte code are showing 00:59:27.980 --> 00:59:34.140 align:start position:0% gonna generate the byte code are showing out<00:59:28.430> of 00:59:34.140 --> 00:59:34.150 align:start position:0% 00:59:34.150 --> 01:00:43.870 align:start position:0% in<00:59:35.150> the<00:59:35.300> actual<01:00:10.150> practice<01:00:42.369> because<01:00:43.369> it's<01:00:43.550> much 01:00:43.870 --> 01:00:43.880 align:start position:0% in the actual practice because it's much 01:00:43.880 --> 01:00:49.700 align:start position:0% in the actual practice because it's much more 01:00:49.700 --> 01:00:49.710 align:start position:0% 01:00:49.710 --> 01:01:09.080 align:start position:0% [Music] 01:01:09.080 --> 01:01:09.090 align:start position:0% 01:01:09.090 --> 01:01:24.000 align:start position:0% yeah 01:01:24.000 --> 01:01:24.010 align:start position:0% 01:01:24.010 --> 01:01:30.340 align:start position:0% [Applause]