WEBVTT Kind: captions Language: en 00:00:01.070 --> 00:00:11.840 align:start position:0% [Applause] 00:00:11.840 --> 00:00:11.850 align:start position:0% 00:00:11.850 --> 00:00:16.350 align:start position:0% that's<00:00:14.970> all<00:00:15.970> right 00:00:16.350 --> 00:00:16.360 align:start position:0% that's all right 00:00:16.360 --> 00:00:19.019 align:start position:0% that's all right hi<00:00:16.630> everyone<00:00:16.840> I'm<00:00:17.170> Vincent<00:00:17.530> Jameson<00:00:18.130> I<00:00:18.369> work 00:00:19.019 --> 00:00:19.029 align:start position:0% hi everyone I'm Vincent Jameson I work 00:00:19.029 --> 00:00:21.269 align:start position:0% hi everyone I'm Vincent Jameson I work for<00:00:19.210> the<00:00:19.300> etherium<00:00:19.750> foundation<00:00:20.410> doing<00:00:20.950> some 00:00:21.269 --> 00:00:21.279 align:start position:0% for the etherium foundation doing some 00:00:21.279 --> 00:00:24.650 align:start position:0% for the etherium foundation doing some DevOps<00:00:21.700> core<00:00:22.630> developer<00:00:23.020> liaison<00:00:23.529> work 00:00:24.650 --> 00:00:24.660 align:start position:0% DevOps core developer liaison work 00:00:24.660 --> 00:00:27.569 align:start position:0% DevOps core developer liaison work actually<00:00:25.660> let's<00:00:26.020> go<00:00:26.169> I<00:00:26.470> guess<00:00:26.650> do<00:00:26.919> intros<00:00:27.369> real 00:00:27.569 --> 00:00:27.579 align:start position:0% actually let's go I guess do intros real 00:00:27.579 --> 00:00:29.819 align:start position:0% actually let's go I guess do intros real quick<00:00:27.759> and<00:00:27.939> then<00:00:28.060> I'll<00:00:28.509> get<00:00:28.660> started<00:00:28.900> on<00:00:29.169> kind 00:00:29.819 --> 00:00:29.829 align:start position:0% quick and then I'll get started on kind 00:00:29.829 --> 00:00:31.679 align:start position:0% quick and then I'll get started on kind of<00:00:29.860> an<00:00:29.980> overview<00:00:30.250> frog<00:00:30.640> pound<00:00:30.910> that<00:00:31.090> will<00:00:31.270> jump 00:00:31.679 --> 00:00:31.689 align:start position:0% of an overview frog pound that will jump 00:00:31.689 --> 00:00:34.319 align:start position:0% of an overview frog pound that will jump into<00:00:31.869> some<00:00:32.349> of<00:00:32.439> the<00:00:32.529> other<00:00:32.790> stuff<00:00:33.790> around<00:00:34.030> it 00:00:34.319 --> 00:00:34.329 align:start position:0% into some of the other stuff around it 00:00:34.329 --> 00:00:39.720 align:start position:0% into some of the other stuff around it so<00:00:34.660> that's<00:00:35.050> my<00:00:35.200> intro<00:00:36.420> hi<00:00:37.420> I'm<00:00:37.750> Melina<00:00:37.989> and<00:00:38.860> I 00:00:39.720 --> 00:00:39.730 align:start position:0% so that's my intro hi I'm Melina and I 00:00:39.730 --> 00:00:41.819 align:start position:0% so that's my intro hi I'm Melina and I work<00:00:39.970> as<00:00:40.630> a<00:00:40.690> programmer<00:00:41.170> on<00:00:41.410> the<00:00:41.530> guillotine 00:00:41.819 --> 00:00:41.829 align:start position:0% work as a programmer on the guillotine 00:00:41.829 --> 00:00:45.750 align:start position:0% work as a programmer on the guillotine and<00:00:42.190> I'm<00:00:42.850> also<00:00:43.470> the<00:00:44.470> security<00:00:44.770> lead<00:00:45.160> for<00:00:45.460> a 00:00:45.750 --> 00:00:45.760 align:start position:0% and I'm also the security lead for a 00:00:45.760 --> 00:00:47.940 align:start position:0% and I'm also the security lead for a foundation<00:00:46.480> in<00:00:46.630> regards<00:00:47.290> to<00:00:47.320> this<00:00:47.470> very<00:00:47.770> mean 00:00:47.940 --> 00:00:47.950 align:start position:0% foundation in regards to this very mean 00:00:47.950 --> 00:00:58.850 align:start position:0% foundation in regards to this very mean poster<00:00:48.220> I<00:00:51.660> had<00:00:52.660> no<00:00:52.900> authority 00:00:58.850 --> 00:00:58.860 align:start position:0% 00:00:58.860 --> 00:01:03.570 align:start position:0% I<00:01:01.350> just<00:01:02.350> Ina<00:01:02.560> Garten<00:01:02.830> all<00:01:03.040> centralized 00:01:03.570 --> 00:01:03.580 align:start position:0% I just Ina Garten all centralized 00:01:03.580 --> 00:01:09.420 align:start position:0% I just Ina Garten all centralized authority<00:01:06.570> all<00:01:07.570> right<00:01:07.930> so<00:01:08.530> how<00:01:09.130> many<00:01:09.310> of<00:01:09.369> you 00:01:09.420 --> 00:01:09.430 align:start position:0% authority all right so how many of you 00:01:09.430 --> 00:01:13.230 align:start position:0% authority all right so how many of you in<00:01:09.579> here<00:01:09.610> are<00:01:09.970> familiar<00:01:10.150> with<00:01:10.630> Prague<00:01:10.900> pal<00:01:12.240> is 00:01:13.230 --> 00:01:13.240 align:start position:0% in here are familiar with Prague pal is 00:01:13.240 --> 00:01:15.360 align:start position:0% in here are familiar with Prague pal is that<00:01:13.390> almost<00:01:13.509> almost<00:01:14.020> I've<00:01:14.290> okay<00:01:14.560> you<00:01:15.100> got<00:01:15.250> at 00:01:15.360 --> 00:01:15.370 align:start position:0% that almost almost I've okay you got at 00:01:15.370 --> 00:01:16.890 align:start position:0% that almost almost I've okay you got at least<00:01:15.460> one<00:01:15.760> person<00:01:16.150> so<00:01:16.240> I<00:01:16.300> want<00:01:16.510> to<00:01:16.600> explain<00:01:16.840> a 00:01:16.890 --> 00:01:16.900 align:start position:0% least one person so I want to explain a 00:01:16.900 --> 00:01:20.160 align:start position:0% least one person so I want to explain a bit<00:01:17.610> so<00:01:18.610> on<00:01:19.240> your<00:01:19.420> some<00:01:19.570> other<00:01:19.690> paper<00:01:19.870> coming 00:01:20.160 --> 00:01:20.170 align:start position:0% bit so on your some other paper coming 00:01:20.170 --> 00:01:24.330 align:start position:0% bit so on your some other paper coming in<00:01:20.850> so<00:01:21.850> Prague<00:01:22.840> Pal<00:01:23.200> is<00:01:23.530> stands<00:01:24.010> for 00:01:24.330 --> 00:01:24.340 align:start position:0% in so Prague Pal is stands for 00:01:24.340 --> 00:01:27.210 align:start position:0% in so Prague Pal is stands for programmatic<00:01:25.030> proof<00:01:25.570> of<00:01:25.720> work<00:01:25.900> and<00:01:26.229> basically 00:01:27.210 --> 00:01:27.220 align:start position:0% programmatic proof of work and basically 00:01:27.220 --> 00:01:30.690 align:start position:0% programmatic proof of work and basically in<00:01:28.180> the<00:01:28.990> etherium<00:01:29.620> white<00:01:29.860> paper<00:01:30.190> it<00:01:30.580> was 00:01:30.690 --> 00:01:30.700 align:start position:0% in the etherium white paper it was 00:01:30.700 --> 00:01:33.090 align:start position:0% in the etherium white paper it was mentioned<00:01:31.210> that<00:01:31.300> aetherium<00:01:32.050> was<00:01:32.409> designed<00:01:32.920> to 00:01:33.090 --> 00:01:33.100 align:start position:0% mentioned that aetherium was designed to 00:01:33.100 --> 00:01:37.150 align:start position:0% mentioned that aetherium was designed to be<00:01:33.310> Nasik<00:01:33.790> resistant<00:01:34.680> basically<00:01:35.680> a<00:01:35.710> special 00:01:37.150 --> 00:01:37.160 align:start position:0% be Nasik resistant basically a special 00:01:37.160 --> 00:01:40.150 align:start position:0% be Nasik resistant basically a special a<00:01:37.300> specialized<00:01:38.300> hardware<00:01:38.870> chip<00:01:39.200> that's<00:01:39.800> meant 00:01:40.150 --> 00:01:40.160 align:start position:0% a specialized hardware chip that's meant 00:01:40.160 --> 00:01:43.630 align:start position:0% a specialized hardware chip that's meant to<00:01:40.250> I<00:01:40.970> guess<00:01:41.870> in<00:01:42.020> the<00:01:42.110> cryptocurrency<00:01:42.410> world<00:01:43.010> - 00:01:43.630 --> 00:01:43.640 align:start position:0% to I guess in the cryptocurrency world - 00:01:43.640 --> 00:01:47.920 align:start position:0% to I guess in the cryptocurrency world - specific<00:01:44.240> cryptocurrency<00:01:45.020> algorithm<00:01:45.950> so<00:01:46.930> as 00:01:47.920 --> 00:01:47.930 align:start position:0% specific cryptocurrency algorithm so as 00:01:47.930 --> 00:01:49.420 align:start position:0% specific cryptocurrency algorithm so as supposed<00:01:48.140> to<00:01:48.230> be<00:01:48.350> a<00:01:48.440> resistance<00:01:48.860> so<00:01:49.250> there's 00:01:49.420 --> 00:01:49.430 align:start position:0% supposed to be a resistance so there's 00:01:49.430 --> 00:01:51.840 align:start position:0% supposed to be a resistance so there's this<00:01:49.610> thing<00:01:49.670> called<00:01:49.880> T<00:01:50.390> hash<00:01:50.600> or<00:01:50.990> at<00:01:51.440> Nash 00:01:51.840 --> 00:01:51.850 align:start position:0% this thing called T hash or at Nash 00:01:51.850 --> 00:01:54.550 align:start position:0% this thing called T hash or at Nash people<00:01:52.850> call<00:01:53.000> it<00:01:53.090> different<00:01:53.120> things<00:01:53.450> and<00:01:53.930> it 00:01:54.550 --> 00:01:54.560 align:start position:0% people call it different things and it 00:01:54.560 --> 00:01:59.680 align:start position:0% people call it different things and it is<00:01:55.840> the<00:01:57.550> proof-of-work<00:01:58.550> algorithm<00:01:59.450> that<00:01:59.570> is 00:01:59.680 --> 00:01:59.690 align:start position:0% is the proof-of-work algorithm that is 00:01:59.690 --> 00:02:01.750 align:start position:0% is the proof-of-work algorithm that is used<00:01:59.900> in<00:02:00.050> aetherium<00:02:00.590> so<00:02:00.890> what<00:02:01.070> a<00:02:01.100> 6<00:02:01.490> came 00:02:01.750 --> 00:02:01.760 align:start position:0% used in aetherium so what a 6 came 00:02:01.760 --> 00:02:02.230 align:start position:0% used in aetherium so what a 6 came online 00:02:02.230 --> 00:02:02.240 align:start position:0% online 00:02:02.240 --> 00:02:04.720 align:start position:0% online risa<00:02:02.870> there<00:02:03.050> in<00:02:03.530> the<00:02:03.680> last<00:02:03.860> year<00:02:04.220> I<00:02:04.250> guess<00:02:04.490> year 00:02:04.720 --> 00:02:04.730 align:start position:0% risa there in the last year I guess year 00:02:04.730 --> 00:02:07.630 align:start position:0% risa there in the last year I guess year and<00:02:04.850> a<00:02:04.880> half<00:02:05.530> starting<00:02:06.530> to<00:02:06.590> get<00:02:06.680> worried<00:02:07.190> some 00:02:07.630 --> 00:02:07.640 align:start position:0% and a half starting to get worried some 00:02:07.640 --> 00:02:11.110 align:start position:0% and a half starting to get worried some people<00:02:08.110> because<00:02:09.110> they<00:02:09.800> are<00:02:10.040> was<00:02:10.399> because 00:02:11.110 --> 00:02:11.120 align:start position:0% people because they are was because 00:02:11.120 --> 00:02:12.820 align:start position:0% people because they are was because Asics<00:02:11.660> were<00:02:11.780> originally<00:02:12.170> not<00:02:12.290> supposed<00:02:12.650> to<00:02:12.740> be 00:02:12.820 --> 00:02:12.830 align:start position:0% Asics were originally not supposed to be 00:02:12.830 --> 00:02:14.830 align:start position:0% Asics were originally not supposed to be on<00:02:12.920> the<00:02:13.010> network<00:02:13.160> and<00:02:13.670> there<00:02:14.540> was<00:02:14.690> some 00:02:14.830 --> 00:02:14.840 align:start position:0% on the network and there was some 00:02:14.840 --> 00:02:16.120 align:start position:0% on the network and there was some concerns<00:02:15.200> from<00:02:15.380> other<00:02:15.620> cryptocurrency 00:02:16.120 --> 00:02:16.130 align:start position:0% concerns from other cryptocurrency 00:02:16.130 --> 00:02:17.980 align:start position:0% concerns from other cryptocurrency communities<00:02:16.760> like<00:02:16.940> Banaras<00:02:17.420> the<00:02:17.660> cash<00:02:17.959> that 00:02:17.980 --> 00:02:17.990 align:start position:0% communities like Banaras the cash that 00:02:17.990 --> 00:02:21.400 align:start position:0% communities like Banaras the cash that Asics<00:02:18.680> would<00:02:19.150> join<00:02:20.150> the<00:02:20.360> network<00:02:20.750> in<00:02:21.050> a<00:02:21.230> way 00:02:21.400 --> 00:02:21.410 align:start position:0% Asics would join the network in a way 00:02:21.410 --> 00:02:24.520 align:start position:0% Asics would join the network in a way that<00:02:21.740> was<00:02:21.890> not<00:02:22.130> as<00:02:22.459> altruistic<00:02:23.300> as<00:02:23.570> GPU<00:02:24.110> mining 00:02:24.520 --> 00:02:24.530 align:start position:0% that was not as altruistic as GPU mining 00:02:24.530 --> 00:02:27.760 align:start position:0% that was not as altruistic as GPU mining pools<00:02:24.800> or<00:02:25.160> would<00:02:26.090> attack<00:02:26.420> the<00:02:26.600> network<00:02:26.780> or<00:02:27.260> for 00:02:27.760 --> 00:02:27.770 align:start position:0% pools or would attack the network or for 00:02:27.770 --> 00:02:30.940 align:start position:0% pools or would attack the network or for the<00:02:27.980> secret<00:02:28.459> you<00:02:28.760> know<00:02:28.880> mining<00:02:29.510> groups<00:02:29.950> and 00:02:30.940 --> 00:02:30.950 align:start position:0% the secret you know mining groups and 00:02:30.950 --> 00:02:33.400 align:start position:0% the secret you know mining groups and the<00:02:31.220> factor<00:02:31.610> that<00:02:31.730> it<00:02:31.970> would<00:02:32.120> push<00:02:32.450> GPU<00:02:32.990> miners 00:02:33.400 --> 00:02:33.410 align:start position:0% the factor that it would push GPU miners 00:02:33.410 --> 00:02:35.470 align:start position:0% the factor that it would push GPU miners out<00:02:33.530> of<00:02:33.680> the<00:02:33.740> ecosystems<00:02:34.490> GPU<00:02:35.000> miners<00:02:35.330> were 00:02:35.470 --> 00:02:35.480 align:start position:0% out of the ecosystems GPU miners were 00:02:35.480 --> 00:02:44.199 align:start position:0% out of the ecosystems GPU miners were pretty<00:02:41.830> so<00:02:42.830> that's<00:02:43.100> kind<00:02:43.760> of<00:02:43.820> what<00:02:44.000> pow-pow 00:02:44.199 --> 00:02:44.209 align:start position:0% pretty so that's kind of what pow-pow 00:02:44.209 --> 00:02:46.600 align:start position:0% pretty so that's kind of what pow-pow came<00:02:44.660> from<00:02:44.900> a<00:02:45.019> group<00:02:45.170> called<00:02:45.230> infidels 00:02:46.600 --> 00:02:46.610 align:start position:0% came from a group called infidels 00:02:46.610 --> 00:02:50.650 align:start position:0% came from a group called infidels it<00:02:46.970> was<00:02:47.150> semi-anonymous<00:02:48.010> created<00:02:49.010> pronto<00:02:49.660> the 00:02:50.650 --> 00:02:50.660 align:start position:0% it was semi-anonymous created pronto the 00:02:50.660 --> 00:02:53.199 align:start position:0% it was semi-anonymous created pronto the if<00:02:50.870> and<00:02:51.230> if<00:02:51.410> death<00:02:51.650> else<00:02:51.950> was<00:02:52.519> a<00:02:52.550> crystal 00:02:53.199 --> 00:02:53.209 align:start position:0% if and if death else was a crystal 00:02:53.209 --> 00:02:55.449 align:start position:0% if and if death else was a crystal applying<00:02:53.570> hand<00:02:53.900> who's<00:02:54.470> been<00:02:54.800> the<00:02:55.010> spokes 00:02:55.449 --> 00:02:55.459 align:start position:0% applying hand who's been the spokes 00:02:55.459 --> 00:03:00.699 align:start position:0% applying hand who's been the spokes person<00:02:56.360> for<00:02:56.600> prague<00:02:57.470> town<00:02:57.769> for<00:02:58.370> this<00:02:58.489> time<00:02:59.709> the 00:03:00.699 --> 00:03:00.709 align:start position:0% person for prague town for this time the 00:03:00.709 --> 00:03:03.520 align:start position:0% person for prague town for this time the other<00:03:01.120> developers<00:03:02.120> have<00:03:02.720> not<00:03:02.930> been<00:03:03.110> revealed 00:03:03.520 --> 00:03:03.530 align:start position:0% other developers have not been revealed 00:03:03.530 --> 00:03:05.229 align:start position:0% other developers have not been revealed since<00:03:04.400> then<00:03:04.610> there's<00:03:04.760> been<00:03:04.850> a<00:03:05.000> lot<00:03:05.209> of 00:03:05.229 --> 00:03:05.239 align:start position:0% since then there's been a lot of 00:03:05.239 --> 00:03:08.540 align:start position:0% since then there's been a lot of politics<00:03:05.920> and<00:03:06.920> some<00:03:07.370> technical 00:03:08.540 --> 00:03:08.550 align:start position:0% politics and some technical 00:03:08.550 --> 00:03:12.410 align:start position:0% politics and some technical on<00:03:08.760> Proc<00:03:09.150> Palin<00:03:09.600> general<00:03:11.120> including<00:03:12.120> some 00:03:12.410 --> 00:03:12.420 align:start position:0% on Proc Palin general including some 00:03:12.420 --> 00:03:15.650 align:start position:0% on Proc Palin general including some conspiracy<00:03:12.810> theories<00:03:13.500> some<00:03:13.770> fun<00:03:14.540> you<00:03:15.540> know 00:03:15.650 --> 00:03:15.660 align:start position:0% conspiracy theories some fun you know 00:03:15.660 --> 00:03:18.050 align:start position:0% conspiracy theories some fun you know listen<00:03:16.170> that<00:03:16.380> back<00:03:16.770> it's<00:03:16.980> worth<00:03:17.190> on<00:03:17.370> Twitter<00:03:17.700> a 00:03:18.050 --> 00:03:18.060 align:start position:0% listen that back it's worth on Twitter a 00:03:18.060 --> 00:03:21.680 align:start position:0% listen that back it's worth on Twitter a lot<00:03:18.570> of<00:03:19.010> research<00:03:20.010> has<00:03:20.160> been<00:03:20.220> done<00:03:20.400> on<00:03:21.120> proc 00:03:21.680 --> 00:03:21.690 align:start position:0% lot of research has been done on proc 00:03:21.690 --> 00:03:23.420 align:start position:0% lot of research has been done on proc pow<00:03:21.930> because<00:03:22.320> of<00:03:22.500> this<00:03:22.620> I<00:03:22.950> believe<00:03:23.220> it<00:03:23.340> was 00:03:23.420 --> 00:03:23.430 align:start position:0% pow because of this I believe it was 00:03:23.430 --> 00:03:26.690 align:start position:0% pow because of this I believe it was first<00:03:23.730> made<00:03:23.910> it<00:03:24.240> like<00:03:24.420> March<00:03:24.810> of<00:03:25.160> 2018<00:03:26.160> that 00:03:26.690 --> 00:03:26.700 align:start position:0% first made it like March of 2018 that 00:03:26.700 --> 00:03:28.490 align:start position:0% first made it like March of 2018 that your<00:03:27.030> purse<00:03:27.240> start<00:03:27.450> being<00:03:27.750> developed<00:03:28.260> and 00:03:28.490 --> 00:03:28.500 align:start position:0% your purse start being developed and 00:03:28.500 --> 00:03:34.280 align:start position:0% your purse start being developed and we're<00:03:28.800> here<00:03:29.550> now<00:03:29.580> and<00:03:30.060> I<00:03:30.690> guess<00:03:32.810> it's<00:03:33.810> November 00:03:34.280 --> 00:03:34.290 align:start position:0% we're here now and I guess it's November 00:03:34.290 --> 00:03:39.980 align:start position:0% we're here now and I guess it's November twenty<00:03:35.280> hi<00:03:35.430> to<00:03:35.570> October<00:03:37.160> and<00:03:38.810> we're<00:03:39.810> still 00:03:39.980 --> 00:03:39.990 align:start position:0% twenty hi to October and we're still 00:03:39.990 --> 00:03:42.080 align:start position:0% twenty hi to October and we're still talking<00:03:40.170> about<00:03:40.440> it<00:03:40.800> so<00:03:40.980> it's<00:03:41.160> very<00:03:41.430> I<00:03:41.910> would 00:03:42.080 --> 00:03:42.090 align:start position:0% talking about it so it's very I would 00:03:42.090 --> 00:03:43.640 align:start position:0% talking about it so it's very I would say<00:03:42.240> there's<00:03:42.390> a<00:03:42.630> contentious<00:03:43.110> topic<00:03:43.140> within 00:03:43.640 --> 00:03:43.650 align:start position:0% say there's a contentious topic within 00:03:43.650 --> 00:03:47.180 align:start position:0% say there's a contentious topic within the<00:03:43.830> etherion<00:03:44.220> community<00:03:45.590> back<00:03:46.590> when<00:03:47.070> the 00:03:47.180 --> 00:03:47.190 align:start position:0% the etherion community back when the 00:03:47.190 --> 00:03:48.800 align:start position:0% the etherion community back when the core<00:03:47.430> developers<00:03:47.850> were<00:03:48.030> deciding<00:03:48.510> whether<00:03:48.720> or 00:03:48.800 --> 00:03:48.810 align:start position:0% core developers were deciding whether or 00:03:48.810 --> 00:03:50.540 align:start position:0% core developers were deciding whether or not<00:03:48.930> to<00:03:49.050> implement<00:03:49.440> product<00:03:49.890> pal<00:03:50.040> once<00:03:50.310> it<00:03:50.460> was 00:03:50.540 --> 00:03:50.550 align:start position:0% not to implement product pal once it was 00:03:50.550 --> 00:03:53.060 align:start position:0% not to implement product pal once it was at<00:03:50.670> a<00:03:50.700> point<00:03:50.940> of<00:03:51.290> being<00:03:52.290> decided<00:03:52.740> for 00:03:53.060 --> 00:03:53.070 align:start position:0% at a point of being decided for 00:03:53.070 --> 00:03:55.580 align:start position:0% at a point of being decided for implementation<00:03:53.780> the<00:03:54.780> core<00:03:54.960> developers<00:03:55.410> made 00:03:55.580 --> 00:03:55.590 align:start position:0% implementation the core developers made 00:03:55.590 --> 00:03:57.650 align:start position:0% implementation the core developers made the<00:03:55.740> decision<00:03:56.160> to<00:03:56.580> implement<00:03:57.120> it<00:03:57.360> into<00:03:57.630> a 00:03:57.650 --> 00:03:57.660 align:start position:0% the decision to implement it into a 00:03:57.660 --> 00:04:00.410 align:start position:0% the decision to implement it into a future<00:03:58.080> hard<00:03:58.290> fork<00:03:58.650> but<00:03:59.460> because<00:04:00.120> there<00:04:00.300> was 00:04:00.410 --> 00:04:00.420 align:start position:0% future hard fork but because there was 00:04:00.420 --> 00:04:04.220 align:start position:0% future hard fork but because there was all<00:04:00.540> this<00:04:00.690> noise<00:04:00.990> around<00:04:02.390> the<00:04:03.390> development<00:04:04.020> be 00:04:04.220 --> 00:04:04.230 align:start position:0% all this noise around the development be 00:04:04.230 --> 00:04:07.790 align:start position:0% all this noise around the development be a<00:04:04.500> product<00:04:04.950> how<00:04:05.160> itself<00:04:05.640> the<00:04:06.600> back<00:04:06.960> of<00:04:07.140> January 00:04:07.790 --> 00:04:07.800 align:start position:0% a product how itself the back of January 00:04:07.800 --> 00:04:10.400 align:start position:0% a product how itself the back of January the<00:04:08.670> etherium<00:04:09.300> cat<00:04:09.540> herders<00:04:09.900> were<00:04:09.930> assigned 00:04:10.400 --> 00:04:10.410 align:start position:0% the etherium cat herders were assigned 00:04:10.410 --> 00:04:14.690 align:start position:0% the etherium cat herders were assigned to<00:04:11.360> have<00:04:12.360> some<00:04:12.720> audits<00:04:13.200> done<00:04:13.290> or<00:04:13.950> basically<00:04:14.370> to 00:04:14.690 --> 00:04:14.700 align:start position:0% to have some audits done or basically to 00:04:14.700 --> 00:04:17.720 align:start position:0% to have some audits done or basically to organize<00:04:15.209> audits<00:04:15.720> around<00:04:16.140> product<00:04:16.620> au<00:04:16.739> and<00:04:17.489> we 00:04:17.720 --> 00:04:17.730 align:start position:0% organize audits around product au and we 00:04:17.730 --> 00:04:20.150 align:start position:0% organize audits around product au and we selected<00:04:18.359> at<00:04:18.900> least<00:04:19.140> Authority<00:04:19.350> for<00:04:19.890> the 00:04:20.150 --> 00:04:20.160 align:start position:0% selected at least Authority for the 00:04:20.160 --> 00:04:22.730 align:start position:0% selected at least Authority for the primarily<00:04:20.730> software<00:04:21.239> part<00:04:21.510> of<00:04:21.570> the<00:04:21.630> ha<00:04:21.810> audit 00:04:22.730 --> 00:04:22.740 align:start position:0% primarily software part of the ha audit 00:04:22.740 --> 00:04:26.420 align:start position:0% primarily software part of the ha audit and<00:04:22.920> Bob<00:04:23.250> brow<00:04:23.520> as<00:04:23.940> the<00:04:25.010> person<00:04:26.010> doing<00:04:26.160> need 00:04:26.420 --> 00:04:26.430 align:start position:0% and Bob brow as the person doing need 00:04:26.430 --> 00:04:28.490 align:start position:0% and Bob brow as the person doing need more<00:04:26.820> Hardware<00:04:27.300> piece<00:04:27.540> of<00:04:27.780> the<00:04:27.900> audit<00:04:28.350> and 00:04:28.490 --> 00:04:28.500 align:start position:0% more Hardware piece of the audit and 00:04:28.500 --> 00:04:33.650 align:start position:0% more Hardware piece of the audit and those<00:04:29.100> were<00:04:29.280> completed<00:04:29.850> months<00:04:30.690> ago<00:04:30.930> and<00:04:32.660> yeah 00:04:33.650 --> 00:04:33.660 align:start position:0% those were completed months ago and yeah 00:04:33.660 --> 00:04:35.450 align:start position:0% those were completed months ago and yeah at<00:04:33.990> least<00:04:34.140> authority<00:04:34.620> I<00:04:34.650> used<00:04:34.950> to<00:04:35.040> talk<00:04:35.220> about 00:04:35.450 --> 00:04:35.460 align:start position:0% at least authority I used to talk about 00:04:35.460 --> 00:04:36.100 align:start position:0% at least authority I used to talk about there<00:04:35.700> and 00:04:36.100 --> 00:04:36.110 align:start position:0% there and 00:04:36.110 --> 00:04:40.330 align:start position:0% there and the<00:04:36.200> deal<00:04:36.350> and<00:04:37.690> Martin<00:04:38.690> has<00:04:39.020> been<00:04:39.340> helping 00:04:40.330 --> 00:04:40.340 align:start position:0% the deal and Martin has been helping 00:04:40.340 --> 00:04:42.040 align:start position:0% the deal and Martin has been helping with<00:04:40.400> the<00:04:40.670> get<00:04:40.850> the<00:04:41.030> pigmentation<00:04:41.450> of<00:04:41.810> it<00:04:41.930> and 00:04:42.040 --> 00:04:42.050 align:start position:0% with the get the pigmentation of it and 00:04:42.050 --> 00:04:44.290 align:start position:0% with the get the pigmentation of it and also<00:04:42.320> started<00:04:42.740> a<00:04:42.920> test<00:04:43.340> net<00:04:43.610> which<00:04:43.880> he<00:04:44.120> could 00:04:44.290 --> 00:04:44.300 align:start position:0% also started a test net which he could 00:04:44.300 --> 00:04:45.550 align:start position:0% also started a test net which he could talk<00:04:44.480> about<00:04:44.660> a<00:04:44.780> little<00:04:44.960> bit<00:04:45.200> I<00:04:45.260> think<00:04:45.380> it's 00:04:45.550 --> 00:04:45.560 align:start position:0% talk about a little bit I think it's 00:04:45.560 --> 00:04:49.210 align:start position:0% talk about a little bit I think it's called<00:04:45.740> Gangnam<00:04:46.150> right<00:04:47.150> just<00:04:47.930> net<00:04:48.200> for<00:04:48.950> Prague 00:04:49.210 --> 00:04:49.220 align:start position:0% called Gangnam right just net for Prague 00:04:49.220 --> 00:04:52.750 align:start position:0% called Gangnam right just net for Prague how<00:04:49.490> to<00:04:49.550> make<00:04:50.180> sure<00:04:50.390> that<00:04:50.660> it<00:04:50.780> is<00:04:50.900> viable<00:04:51.760> for 00:04:52.750 --> 00:04:52.760 align:start position:0% how to make sure that it is viable for 00:04:52.760 --> 00:04:55.750 align:start position:0% how to make sure that it is viable for the<00:04:52.850> network<00:04:53.240> so<00:04:54.190> we'll<00:04:55.190> get<00:04:55.340> into<00:04:55.460> some 00:04:55.750 --> 00:04:55.760 align:start position:0% the network so we'll get into some 00:04:55.760 --> 00:04:57.430 align:start position:0% the network so we'll get into some discussion<00:04:55.910> kind<00:04:56.480> of<00:04:56.630> around<00:04:56.870> a<00:04:57.170> little<00:04:57.260> bit 00:04:57.430 --> 00:04:57.440 align:start position:0% discussion kind of around a little bit 00:04:57.440 --> 00:04:58.570 align:start position:0% discussion kind of around a little bit of<00:04:57.530> the<00:04:57.590> technicals<00:04:58.070> a<00:04:58.130> little<00:04:58.340> bit<00:04:58.430> of<00:04:58.520> the 00:04:58.570 --> 00:04:58.580 align:start position:0% of the technicals a little bit of the 00:04:58.580 --> 00:05:00.940 align:start position:0% of the technicals a little bit of the politics<00:04:59.030> and<00:04:59.330> kind<00:04:59.540> of<00:04:59.630> like<00:05:00.410> reach<00:05:00.620> out<00:05:00.770> to 00:05:00.940 --> 00:05:00.950 align:start position:0% politics and kind of like reach out to 00:05:00.950 --> 00:05:06.190 align:start position:0% politics and kind of like reach out to you<00:05:01.100> all<00:05:01.190> to<00:05:01.460> see<00:05:01.990> who<00:05:02.990> is<00:05:04.330> ask<00:05:05.330> questions<00:05:05.390> and 00:05:06.190 --> 00:05:06.200 align:start position:0% you all to see who is ask questions and 00:05:06.200 --> 00:05:08.110 align:start position:0% you all to see who is ask questions and where<00:05:06.290> you<00:05:06.380> want<00:05:06.560> these<00:05:06.680> topics<00:05:07.100> to<00:05:07.250> go<00:05:07.370> so<00:05:08.030> on 00:05:08.110 --> 00:05:08.120 align:start position:0% where you want these topics to go so on 00:05:08.120 --> 00:05:09.820 align:start position:0% where you want these topics to go so on Thrones<00:05:08.360> at<00:05:08.510> least<00:05:08.660> Authority<00:05:08.840> and<00:05:09.350> then<00:05:09.470> they 00:05:09.820 --> 00:05:09.830 align:start position:0% Thrones at least Authority and then they 00:05:09.830 --> 00:05:11.230 align:start position:0% Thrones at least Authority and then they can<00:05:09.980> throw<00:05:10.130> it<00:05:10.190> to<00:05:10.280> Martin<00:05:10.700> and<00:05:10.730> then<00:05:10.940> we<00:05:11.090> can 00:05:11.230 --> 00:05:11.240 align:start position:0% can throw it to Martin and then we can 00:05:11.240 --> 00:05:17.950 align:start position:0% can throw it to Martin and then we can go<00:05:11.510> from<00:05:11.630> there<00:05:11.870> so<00:05:16.330> you<00:05:17.330> know<00:05:17.450> we<00:05:17.750> were 00:05:17.950 --> 00:05:17.960 align:start position:0% go from there so you know we were 00:05:17.960 --> 00:05:20.440 align:start position:0% go from there so you know we were selected<00:05:18.830> basically<00:05:19.250> to<00:05:19.430> do<00:05:19.580> this<00:05:19.700> audit<00:05:20.150> and 00:05:20.440 --> 00:05:20.450 align:start position:0% selected basically to do this audit and 00:05:20.450 --> 00:05:23.860 align:start position:0% selected basically to do this audit and we<00:05:21.440> know<00:05:21.560> that<00:05:21.800> sometimes<00:05:22.300> that<00:05:23.300> what<00:05:23.600> we<00:05:23.690> knew 00:05:23.860 --> 00:05:23.870 align:start position:0% we know that sometimes that what we knew 00:05:23.870 --> 00:05:25.330 align:start position:0% we know that sometimes that what we knew we<00:05:24.320> were<00:05:24.440> aware<00:05:24.650> this<00:05:24.860> is<00:05:24.920> a<00:05:25.100> pretty 00:05:25.330 --> 00:05:25.340 align:start position:0% we were aware this is a pretty 00:05:25.340 --> 00:05:28.390 align:start position:0% we were aware this is a pretty contentious<00:05:26.000> topic<00:05:26.450> but<00:05:26.750> we<00:05:27.500> do<00:05:27.920> see<00:05:28.100> arable 00:05:28.390 --> 00:05:28.400 align:start position:0% contentious topic but we do see arable 00:05:28.400 --> 00:05:31.720 align:start position:0% contentious topic but we do see arable as<00:05:28.760> auditors<00:05:29.270> to<00:05:29.870> just<00:05:30.260> look<00:05:31.100> and<00:05:31.310> report<00:05:31.640> on 00:05:31.720 --> 00:05:31.730 align:start position:0% as auditors to just look and report on 00:05:31.730 --> 00:05:34.090 align:start position:0% as auditors to just look and report on what<00:05:31.760> we<00:05:31.970> see<00:05:32.120> so<00:05:32.510> I'm<00:05:32.930> aware<00:05:33.410> we<00:05:33.740> can't<00:05:33.920> really 00:05:34.090 --> 00:05:34.100 align:start position:0% what we see so I'm aware we can't really 00:05:34.100 --> 00:05:36.310 align:start position:0% what we see so I'm aware we can't really offer<00:05:34.340> too<00:05:34.640> much<00:05:34.670> in<00:05:35.270> terms<00:05:35.480> of<00:05:35.780> what<00:05:36.230> the 00:05:36.310 --> 00:05:36.320 align:start position:0% offer too much in terms of what the 00:05:36.320 --> 00:05:37.990 align:start position:0% offer too much in terms of what the community<00:05:36.680> can<00:05:36.830> do<00:05:37.370> and<00:05:37.700> how<00:05:37.820> it<00:05:37.880> should 00:05:37.990 --> 00:05:38.000 align:start position:0% community can do and how it should 00:05:38.000 --> 00:05:39.760 align:start position:0% community can do and how it should handle<00:05:38.330> and<00:05:38.510> everything<00:05:38.600> but<00:05:39.080> it<00:05:39.410> was<00:05:39.560> more 00:05:39.760 --> 00:05:39.770 align:start position:0% handle and everything but it was more 00:05:39.770 --> 00:05:42.250 align:start position:0% handle and everything but it was more about<00:05:39.800> just<00:05:40.730> reflecting<00:05:41.660> on<00:05:41.720> what<00:05:41.960> we<00:05:42.050> found 00:05:42.250 --> 00:05:42.260 align:start position:0% about just reflecting on what we found 00:05:42.260 --> 00:05:45.460 align:start position:0% about just reflecting on what we found with<00:05:42.500> prop<00:05:42.740> pal<00:05:42.920> so<00:05:43.760> we<00:05:44.150> looked<00:05:44.930> at<00:05:45.050> it<00:05:45.110> for<00:05:45.440> I 00:05:45.460 --> 00:05:45.470 align:start position:0% with prop pal so we looked at it for I 00:05:45.470 --> 00:05:46.930 align:start position:0% with prop pal so we looked at it for I think<00:05:45.680> a<00:05:45.890> little<00:05:46.160> bit<00:05:46.340> over<00:05:46.580> a<00:05:46.610> month<00:05:46.670> I<00:05:46.910> think 00:05:46.930 --> 00:05:46.940 align:start position:0% think a little bit over a month I think 00:05:46.940 --> 00:05:48.940 align:start position:0% think a little bit over a month I think is<00:05:47.120> about<00:05:47.300> five<00:05:47.480> weeks<00:05:47.660> and<00:05:47.960> then<00:05:48.500> we<00:05:48.620> produced 00:05:48.940 --> 00:05:48.950 align:start position:0% is about five weeks and then we produced 00:05:48.950 --> 00:05:50.750 align:start position:0% is about five weeks and then we produced her<00:05:49.220> word 00:05:50.750 --> 00:05:50.760 align:start position:0% her word 00:05:50.760 --> 00:05:53.370 align:start position:0% her word got<00:05:51.760> populist<00:05:52.180> choice<00:05:52.450> and<00:05:52.720> of<00:05:52.840> August<00:05:53.140> or<00:05:53.350> in 00:05:53.370 --> 00:05:53.380 align:start position:0% got populist choice and of August or in 00:05:53.380 --> 00:05:56.130 align:start position:0% got populist choice and of August or in September<00:05:53.560> but<00:05:53.950> it's<00:05:54.310> public<00:05:54.610> now<00:05:54.760> so<00:05:55.480> that 00:05:56.130 --> 00:05:56.140 align:start position:0% September but it's public now so that 00:05:56.140 --> 00:05:57.510 align:start position:0% September but it's public now so that report<00:05:56.440> is<00:05:56.560> out<00:05:56.680> there<00:05:56.890> for<00:05:57.010> people<00:05:57.130> to<00:05:57.370> read 00:05:57.510 --> 00:05:57.520 align:start position:0% report is out there for people to read 00:05:57.520 --> 00:05:58.860 align:start position:0% report is out there for people to read some<00:05:58.120> of<00:05:58.150> the<00:05:58.270> feedback<00:05:58.450> that<00:05:58.720> we've<00:05:58.840> gotten 00:05:58.860 --> 00:05:58.870 align:start position:0% some of the feedback that we've gotten 00:05:58.870 --> 00:06:01.830 align:start position:0% some of the feedback that we've gotten report<00:05:59.650> is<00:05:59.920> that<00:05:59.950> people<00:06:00.820> understand<00:06:01.570> it<00:06:01.720> but 00:06:01.830 --> 00:06:01.840 align:start position:0% report is that people understand it but 00:06:01.840 --> 00:06:04.530 align:start position:0% report is that people understand it but kind<00:06:02.230> of<00:06:02.410> don't<00:06:02.620> understand<00:06:03.220> it<00:06:03.400> that<00:06:04.240> is<00:06:04.360> just 00:06:04.530 --> 00:06:04.540 align:start position:0% kind of don't understand it that is just 00:06:04.540 --> 00:06:06.000 align:start position:0% kind of don't understand it that is just because<00:06:04.690> it's<00:06:04.930> really<00:06:05.110> it's<00:06:05.440> really<00:06:05.710> we<00:06:05.890> had 00:06:06.000 --> 00:06:06.010 align:start position:0% because it's really it's really we had 00:06:06.010 --> 00:06:08.310 align:start position:0% because it's really it's really we had to<00:06:06.100> get<00:06:06.220> into<00:06:06.430> really<00:06:06.730> technical<00:06:07.180> stuff<00:06:07.390> when 00:06:08.310 --> 00:06:08.320 align:start position:0% to get into really technical stuff when 00:06:08.320 --> 00:06:09.510 align:start position:0% to get into really technical stuff when doing<00:06:08.590> the<00:06:08.680> security<00:06:08.830> on<00:06:09.220> it<00:06:09.250> it's<00:06:09.460> really 00:06:09.510 --> 00:06:09.520 align:start position:0% doing the security on it it's really 00:06:09.520 --> 00:06:11.430 align:start position:0% doing the security on it it's really just<00:06:10.000> like<00:06:10.180> dig<00:06:10.390> deep<00:06:10.630> and<00:06:10.780> try<00:06:10.960> to<00:06:10.990> figure<00:06:11.230> out 00:06:11.430 --> 00:06:11.440 align:start position:0% just like dig deep and try to figure out 00:06:11.440 --> 00:06:14.790 align:start position:0% just like dig deep and try to figure out what<00:06:11.560> exactly<00:06:11.890> what's<00:06:12.070> going<00:06:12.190> on<00:06:12.420> and<00:06:13.800> you 00:06:14.790 --> 00:06:14.800 align:start position:0% what exactly what's going on and you 00:06:14.800 --> 00:06:16.110 align:start position:0% what exactly what's going on and you know<00:06:14.890> we<00:06:15.010> report<00:06:15.340> things<00:06:15.520> on<00:06:15.670> a<00:06:15.700> high<00:06:15.760> level 00:06:16.110 --> 00:06:16.120 align:start position:0% know we report things on a high level 00:06:16.120 --> 00:06:18.060 align:start position:0% know we report things on a high level and<00:06:16.450> then<00:06:16.570> we<00:06:16.660> also<00:06:16.780> give<00:06:17.200> suggestions<00:06:17.830> of 00:06:18.060 --> 00:06:18.070 align:start position:0% and then we also give suggestions of 00:06:18.070 --> 00:06:20.100 align:start position:0% and then we also give suggestions of what<00:06:18.190> should<00:06:18.370> be<00:06:18.720> potentially<00:06:19.720> improved 00:06:20.100 --> 00:06:20.110 align:start position:0% what should be potentially improved 00:06:20.110 --> 00:06:22.440 align:start position:0% what should be potentially improved about<00:06:20.380> prog<00:06:20.650> Powell<00:06:20.920> but<00:06:21.220> I<00:06:21.460> mean<00:06:22.000> basically 00:06:22.440 --> 00:06:22.450 align:start position:0% about prog Powell but I mean basically 00:06:22.450 --> 00:06:24.840 align:start position:0% about prog Powell but I mean basically that<00:06:22.660> we<00:06:22.780> found<00:06:23.050> that<00:06:23.320> it<00:06:23.530> achieves<00:06:24.040> its<00:06:24.640> goal 00:06:24.840 --> 00:06:24.850 align:start position:0% that we found that it achieves its goal 00:06:24.850 --> 00:06:30.690 align:start position:0% that we found that it achieves its goal of<00:06:26.250> making<00:06:27.250> a<00:06:27.820> six<00:06:28.270> basic<00:06:28.630> we<00:06:28.860> need<00:06:29.860> to<00:06:30.130> be<00:06:30.280> like 00:06:30.690 --> 00:06:30.700 align:start position:0% of making a six basic we need to be like 00:06:30.700 --> 00:06:34.980 align:start position:0% of making a six basic we need to be like GPS<00:06:31.090> and<00:06:31.600> order<00:06:32.530> to<00:06:32.860> in<00:06:33.760> order<00:06:33.940> to<00:06:34.330> work<00:06:34.780> with 00:06:34.980 --> 00:06:34.990 align:start position:0% GPS and order to in order to work with 00:06:34.990 --> 00:06:38.070 align:start position:0% GPS and order to in order to work with it<00:06:35.110> and<00:06:35.140> so<00:06:35.500> that<00:06:35.530> really<00:06:36.280> disadvantaged<00:06:37.120> any 00:06:38.070 --> 00:06:38.080 align:start position:0% it and so that really disadvantaged any 00:06:38.080 --> 00:06:42.270 align:start position:0% it and so that really disadvantaged any kind<00:06:38.350> of<00:06:38.440> basic<00:06:39.150> production<00:06:40.290> to<00:06:41.290> a<00:06:41.320> basic 00:06:42.270 --> 00:06:42.280 align:start position:0% kind of basic production to a basic 00:06:42.280 --> 00:06:44.880 align:start position:0% kind of basic production to a basic advantage<00:06:43.000> when<00:06:43.660> they<00:06:43.810> were<00:06:43.900> produced<00:06:44.230> so<00:06:44.560> we 00:06:44.880 --> 00:06:44.890 align:start position:0% advantage when they were produced so we 00:06:44.890 --> 00:06:49.680 align:start position:0% advantage when they were produced so we also<00:06:45.130> looked<00:06:45.820> at<00:06:45.940> what<00:06:47.370> like<00:06:48.370> the<00:06:48.520> so<00:06:48.970> knowing 00:06:49.680 --> 00:06:49.690 align:start position:0% also looked at what like the so knowing 00:06:49.690 --> 00:06:51.900 align:start position:0% also looked at what like the so knowing that<00:06:49.720> we<00:06:50.260> also<00:06:50.860> wanted<00:06:51.340> to<00:06:51.370> really<00:06:51.730> analyze 00:06:51.900 --> 00:06:51.910 align:start position:0% that we also wanted to really analyze 00:06:51.910 --> 00:06:54.040 align:start position:0% that we also wanted to really analyze what<00:06:52.330> would<00:06:52.480> happen 00:06:54.040 --> 00:06:54.050 align:start position:0% what would happen 00:06:54.050 --> 00:06:57.010 align:start position:0% what would happen the<00:06:54.379> teacher<00:06:54.620> in<00:06:55.310> particular<00:06:55.849> ways<00:06:56.120> how<00:06:56.780> that 00:06:57.010 --> 00:06:57.020 align:start position:0% the teacher in particular ways how that 00:06:57.020 --> 00:06:58.689 align:start position:0% the teacher in particular ways how that would<00:06:57.139> be<00:06:57.169> so<00:06:57.409> impractical<00:06:57.650> felt<00:06:58.159> also<00:06:58.520> that 00:06:58.689 --> 00:06:58.699 align:start position:0% would be so impractical felt also that 00:06:58.699 --> 00:07:00.580 align:start position:0% would be so impractical felt also that kind<00:06:58.819> of<00:06:58.970> extend<00:06:59.539> the<00:06:59.690> life<00:06:59.870> of<00:07:00.080> the<00:07:00.259> audit 00:07:00.580 --> 00:07:00.590 align:start position:0% kind of extend the life of the audit 00:07:00.590 --> 00:07:02.020 align:start position:0% kind of extend the life of the audit information<00:07:00.830> that<00:07:01.340> we<00:07:01.430> provide<00:07:01.759> to<00:07:01.789> the 00:07:02.020 --> 00:07:02.030 align:start position:0% information that we provide to the 00:07:02.030 --> 00:07:05.140 align:start position:0% information that we provide to the community<00:07:02.240> so<00:07:03.789> because<00:07:04.789> you<00:07:04.909> know<00:07:04.940> there's 00:07:05.140 --> 00:07:05.150 align:start position:0% community so because you know there's 00:07:05.150 --> 00:07:06.399 align:start position:0% community so because you know there's only<00:07:05.240> so<00:07:05.360> much<00:07:05.509> you<00:07:05.569> can<00:07:05.750> write<00:07:05.990> about<00:07:06.199> like 00:07:06.399 --> 00:07:06.409 align:start position:0% only so much you can write about like 00:07:06.409 --> 00:07:08.770 align:start position:0% only so much you can write about like hey<00:07:06.590> this<00:07:06.860> is<00:07:06.919> just<00:07:07.129> how<00:07:07.280> it<00:07:07.370> works<00:07:07.430> I<00:07:07.699> so<00:07:08.690> we 00:07:08.770 --> 00:07:08.780 align:start position:0% hey this is just how it works I so we 00:07:08.780 --> 00:07:09.999 align:start position:0% hey this is just how it works I so we wanted<00:07:09.020> to<00:07:09.169> really<00:07:09.289> look<00:07:09.590> at<00:07:09.680> that<00:07:09.800> so<00:07:09.919> we 00:07:09.999 --> 00:07:10.009 align:start position:0% wanted to really look at that so we 00:07:10.009 --> 00:07:11.350 align:start position:0% wanted to really look at that so we tried<00:07:10.220> to<00:07:10.250> capture<00:07:10.729> some<00:07:10.909> things<00:07:11.120> in<00:07:11.270> the 00:07:11.350 --> 00:07:11.360 align:start position:0% tried to capture some things in the 00:07:11.360 --> 00:07:13.930 align:start position:0% tried to capture some things in the report<00:07:11.720> -<00:07:11.930> that<00:07:12.139> said<00:07:12.409> if<00:07:12.680> this<00:07:13.129> specific 00:07:13.930 --> 00:07:13.940 align:start position:0% report - that said if this specific 00:07:13.940 --> 00:07:15.730 align:start position:0% report - that said if this specific hardware<00:07:14.599> advancement<00:07:15.139> happens<00:07:15.500> in<00:07:15.650> the 00:07:15.730 --> 00:07:15.740 align:start position:0% hardware advancement happens in the 00:07:15.740 --> 00:07:17.740 align:start position:0% hardware advancement happens in the future<00:07:15.889> then<00:07:16.520> this<00:07:16.789> is<00:07:17.000> the<00:07:17.150> potential<00:07:17.569> issue 00:07:17.740 --> 00:07:17.750 align:start position:0% future then this is the potential issue 00:07:17.750 --> 00:07:19.839 align:start position:0% future then this is the potential issue that<00:07:17.990> might<00:07:18.139> result<00:07:18.409> in<00:07:18.680> them<00:07:18.889> more 00:07:19.839 --> 00:07:19.849 align:start position:0% that might result in them more 00:07:19.849 --> 00:07:22.749 align:start position:0% that might result in them more specifically<00:07:20.360> that<00:07:20.449> was<00:07:20.840> around<00:07:21.259> the<00:07:21.759> light 00:07:22.749 --> 00:07:22.759 align:start position:0% specifically that was around the light 00:07:22.759 --> 00:07:27.550 align:start position:0% specifically that was around the light evaluation<00:07:23.509> mining<00:07:24.699> and<00:07:25.699> then<00:07:25.940> we<00:07:26.599> also<00:07:26.719> had 00:07:27.550 --> 00:07:27.560 align:start position:0% evaluation mining and then we also had 00:07:27.560 --> 00:07:29.830 align:start position:0% evaluation mining and then we also had some<00:07:27.590> a<00:07:28.069> dissertation<00:07:28.340> or<00:07:28.699> catch<00:07:29.240> a<00:07:29.360> function 00:07:29.830 --> 00:07:29.840 align:start position:0% some a dissertation or catch a function 00:07:29.840 --> 00:07:31.719 align:start position:0% some a dissertation or catch a function -<00:07:30.020> and<00:07:30.259> those<00:07:30.710> two<00:07:30.740> items<00:07:31.219> seem<00:07:31.430> to<00:07:31.520> be<00:07:31.639> the 00:07:31.719 --> 00:07:31.729 align:start position:0% - and those two items seem to be the 00:07:31.729 --> 00:07:33.520 align:start position:0% - and those two items seem to be the ones<00:07:31.879> that<00:07:32.030> are<00:07:32.210> you<00:07:32.659> know<00:07:32.780> most<00:07:33.139> up<00:07:33.349> for 00:07:33.520 --> 00:07:33.530 align:start position:0% ones that are you know most up for 00:07:33.530 --> 00:07:35.469 align:start position:0% ones that are you know most up for discussion<00:07:33.680> areas<00:07:34.240> besides<00:07:35.240> that<00:07:35.360> we<00:07:35.449> also 00:07:35.469 --> 00:07:35.479 align:start position:0% discussion areas besides that we also 00:07:35.479 --> 00:07:37.240 align:start position:0% discussion areas besides that we also did<00:07:35.930> some<00:07:36.080> other<00:07:36.139> suggestions<00:07:36.650> that<00:07:37.009> are<00:07:37.039> the 00:07:37.240 --> 00:07:37.250 align:start position:0% did some other suggestions that are the 00:07:37.250 --> 00:07:39.070 align:start position:0% did some other suggestions that are the word<00:07:37.430> it's<00:07:37.849> about<00:07:38.030> the<00:07:38.180> documentation<00:07:38.719> and 00:07:39.070 --> 00:07:39.080 align:start position:0% word it's about the documentation and 00:07:39.080 --> 00:07:41.559 align:start position:0% word it's about the documentation and some<00:07:39.169> of<00:07:39.379> that<00:07:39.530> -<00:07:40.360> yeah 00:07:41.559 --> 00:07:41.569 align:start position:0% some of that - yeah 00:07:41.569 --> 00:07:43.029 align:start position:0% some of that - yeah so<00:07:41.690> you<00:07:41.990> all<00:07:42.080> can<00:07:42.110> read<00:07:42.379> the<00:07:42.500> report<00:07:42.800> for<00:07:42.919> more 00:07:43.029 --> 00:07:43.039 align:start position:0% so you all can read the report for more 00:07:43.039 --> 00:07:45.279 align:start position:0% so you all can read the report for more details<00:07:43.340> we're<00:07:43.550> also<00:07:43.729> here<00:07:44.210> to<00:07:44.240> talk<00:07:44.629> today<00:07:44.810> if 00:07:45.279 --> 00:07:45.289 align:start position:0% details we're also here to talk today if 00:07:45.289 --> 00:07:46.809 align:start position:0% details we're also here to talk today if there's<00:07:45.500> any<00:07:45.889> specific<00:07:46.099> questions<00:07:46.729> about 00:07:46.809 --> 00:07:46.819 align:start position:0% there's any specific questions about 00:07:46.819 --> 00:07:47.030 align:start position:0% there's any specific questions about that 00:07:47.030 --> 00:07:47.040 align:start position:0% that 00:07:47.040 --> 00:07:51.050 align:start position:0% that [Music] 00:07:51.050 --> 00:07:51.060 align:start position:0% 00:07:51.060 --> 00:07:55.820 align:start position:0% oh<00:07:52.490> really<00:07:53.490> I<00:07:53.970> can<00:07:54.960> just<00:07:54.990> mention<00:07:55.470> that<00:07:55.560> test 00:07:55.820 --> 00:07:55.830 align:start position:0% oh really I can just mention that test 00:07:55.830 --> 00:07:59.720 align:start position:0% oh really I can just mention that test them<00:07:56.040> so<00:07:57.410> there<00:07:58.410> was<00:07:58.590> a<00:07:58.620> test<00:07:58.890> that<00:07:58.980> started<00:07:59.550> a 00:07:59.720 --> 00:07:59.730 align:start position:0% them so there was a test that started a 00:07:59.730 --> 00:08:02.180 align:start position:0% them so there was a test that started a long<00:08:00.180> time<00:08:00.570> ago<00:08:00.930> I<00:08:01.140> can't<00:08:01.410> accept<00:08:01.680> to<00:08:01.830> remember 00:08:02.180 --> 00:08:02.190 align:start position:0% long time ago I can't accept to remember 00:08:02.190 --> 00:08:06.290 align:start position:0% long time ago I can't accept to remember when<00:08:02.730> it<00:08:02.820> was<00:08:03.860> it<00:08:04.860> was<00:08:05.040> based<00:08:05.370> on<00:08:05.700> in<00:08:06.000> Paris 00:08:06.290 --> 00:08:06.300 align:start position:0% when it was it was based on in Paris 00:08:06.300 --> 00:08:08.060 align:start position:0% when it was it was based on in Paris apparently<00:08:06.780> a<00:08:06.810> ton<00:08:07.020> on<00:08:07.170> implementation<00:08:07.500> which 00:08:08.060 --> 00:08:08.070 align:start position:0% apparently a ton on implementation which 00:08:08.070 --> 00:08:11.780 align:start position:0% apparently a ton on implementation which was<00:08:08.310> later<00:08:09.680> merged<00:08:10.680> into<00:08:11.070> the<00:08:11.280> pair<00:08:11.460> decline 00:08:11.780 --> 00:08:11.790 align:start position:0% was later merged into the pair decline 00:08:11.790 --> 00:08:14.750 align:start position:0% was later merged into the pair decline so<00:08:12.120> it<00:08:12.240> can<00:08:12.390> be<00:08:12.480> activated<00:08:12.840> by<00:08:13.320> a<00:08:13.350> genesis<00:08:13.860> for 00:08:14.750 --> 00:08:14.760 align:start position:0% so it can be activated by a genesis for 00:08:14.760 --> 00:08:15.230 align:start position:0% so it can be activated by a genesis for gif 00:08:15.230 --> 00:08:15.240 align:start position:0% gif 00:08:15.240 --> 00:08:18.070 align:start position:0% gif it<00:08:15.300> was<00:08:15.510> never<00:08:15.690> merged<00:08:16.020> into<00:08:16.470> the<00:08:16.590> client<00:08:17.070> so 00:08:18.070 --> 00:08:18.080 align:start position:0% it was never merged into the client so 00:08:18.080 --> 00:08:21.200 align:start position:0% it was never merged into the client so they<00:08:19.080> kept<00:08:19.500> lines<00:08:19.920> that<00:08:20.280> participated 00:08:21.200 --> 00:08:21.210 align:start position:0% they kept lines that participated 00:08:21.210 --> 00:08:24.530 align:start position:0% they kept lines that participated intestine<00:08:21.720> were<00:08:21.930> basically<00:08:22.320> based<00:08:23.100> of<00:08:23.540> guess 00:08:24.530 --> 00:08:24.540 align:start position:0% intestine were basically based of guess 00:08:24.540 --> 00:08:30.590 align:start position:0% intestine were basically based of guess a<00:08:24.840> PR<00:08:25.290> which<00:08:25.800> by<00:08:26.700> now<00:08:26.910> is<00:08:27.180> kind<00:08:27.450> of<00:08:27.570> staled<00:08:29.600> as 00:08:30.590 --> 00:08:30.600 align:start position:0% a PR which by now is kind of staled as 00:08:30.600 --> 00:08:32.090 align:start position:0% a PR which by now is kind of staled as far<00:08:30.840> as<00:08:30.900> I<00:08:30.990> know<00:08:31.140> the<00:08:31.410> Tesla<00:08:31.770> is<00:08:31.800> still 00:08:32.090 --> 00:08:32.100 align:start position:0% far as I know the Tesla is still 00:08:32.100 --> 00:08:35.090 align:start position:0% far as I know the Tesla is still operating<00:08:32.460> and<00:08:32.930> -<00:08:33.930> running<00:08:34.320> it<00:08:34.440> they<00:08:34.650> are<00:08:34.890> also 00:08:35.090 --> 00:08:35.100 align:start position:0% operating and - running it they are also 00:08:35.100 --> 00:08:41.960 align:start position:0% operating and - running it they are also running<00:08:35.550> it<00:08:35.760> on<00:08:37.910> dedicated<00:08:38.910> GPU<00:08:39.660> -<00:08:40.140> and<00:08:40.970> I 00:08:41.960 --> 00:08:41.970 align:start position:0% running it on dedicated GPU - and I 00:08:41.970 --> 00:08:44.630 align:start position:0% running it on dedicated GPU - and I don't<00:08:42.420> know<00:08:43.080> at<00:08:43.260> this<00:08:43.410> point<00:08:43.680> how<00:08:43.890> many<00:08:44.190> folks 00:08:44.630 --> 00:08:44.640 align:start position:0% don't know at this point how many folks 00:08:44.640 --> 00:08:47.030 align:start position:0% don't know at this point how many folks it<00:08:45.090> has<00:08:45.150> transitioned<00:08:45.750> through<00:08:46.200> but<00:08:46.770> it's 00:08:47.030 --> 00:08:47.040 align:start position:0% it has transitioned through but it's 00:08:47.040 --> 00:08:49.310 align:start position:0% it has transitioned through but it's quite<00:08:47.280> a<00:08:47.310> lot<00:08:47.580> and<00:08:47.880> as<00:08:48.570> far<00:08:48.810> as<00:08:48.900> I<00:08:48.960> know<00:08:49.080> there's 00:08:49.310 --> 00:08:49.320 align:start position:0% quite a lot and as far as I know there's 00:08:49.320 --> 00:08:56.320 align:start position:0% quite a lot and as far as I know there's no<00:08:50.600> problems<00:08:51.600> with<00:08:51.720> it 00:08:56.320 --> 00:08:56.330 align:start position:0% 00:08:56.330 --> 00:08:57.650 align:start position:0% great 00:08:57.650 --> 00:08:57.660 align:start position:0% great 00:08:57.660 --> 00:08:59.930 align:start position:0% great so<00:08:57.990> yeah<00:08:58.920> that's<00:08:59.100> how<00:08:59.190> I<00:08:59.280> understood<00:08:59.700> it<00:08:59.850> as 00:08:59.930 --> 00:08:59.940 align:start position:0% so yeah that's how I understood it as 00:08:59.940 --> 00:09:04.700 align:start position:0% so yeah that's how I understood it as well<00:09:00.180> so<00:09:02.180> diving<00:09:03.180> into<00:09:03.600> the<00:09:04.110> politics<00:09:04.590> a 00:09:04.700 --> 00:09:04.710 align:start position:0% well so diving into the politics a 00:09:04.710 --> 00:09:07.880 align:start position:0% well so diving into the politics a little<00:09:04.800> bit<00:09:05.100> the<00:09:05.760> latest<00:09:06.180> on<00:09:06.420> that<00:09:06.720> I<00:09:07.020> guess<00:09:07.410> or 00:09:07.880 --> 00:09:07.890 align:start position:0% little bit the latest on that I guess or 00:09:07.890 --> 00:09:10.960 align:start position:0% little bit the latest on that I guess or actually<00:09:08.430> maybe<00:09:08.700> even<00:09:08.910> a<00:09:08.970> background<00:09:09.180> so 00:09:10.960 --> 00:09:10.970 align:start position:0% actually maybe even a background so 00:09:10.970 --> 00:09:13.910 align:start position:0% actually maybe even a background so there<00:09:11.970> has<00:09:12.270> been<00:09:12.300> some<00:09:13.110> back-and-forth 00:09:13.910 --> 00:09:13.920 align:start position:0% there has been some back-and-forth 00:09:13.920 --> 00:09:15.920 align:start position:0% there has been some back-and-forth there's<00:09:14.820> a<00:09:14.910> kind<00:09:15.090> of<00:09:15.120> a<00:09:15.240> hair<00:09:15.390> that's<00:09:15.600> all<00:09:15.720> out 00:09:15.920 --> 00:09:15.930 align:start position:0% there's a kind of a hair that's all out 00:09:15.930 --> 00:09:16.940 align:start position:0% there's a kind of a hair that's all out there 00:09:16.940 --> 00:09:16.950 align:start position:0% there 00:09:16.950 --> 00:09:20.460 align:start position:0% there Christine<00:09:17.790> might<00:09:18.210> han<00:09:18.450> is<00:09:18.780> a<00:09:19.020> very 00:09:20.460 --> 00:09:20.470 align:start position:0% Christine might han is a very 00:09:20.470 --> 00:09:22.889 align:start position:0% Christine might han is a very sort<00:09:21.470> of<00:09:21.559> magnetic<00:09:21.709> figure<00:09:22.339> like<00:09:22.579> a 00:09:22.889 --> 00:09:22.899 align:start position:0% sort of magnetic figure like a 00:09:22.899 --> 00:09:24.999 align:start position:0% sort of magnetic figure like a controversial<00:09:23.899> figure<00:09:24.139> and<00:09:24.499> the<00:09:24.739> space 00:09:24.999 --> 00:09:25.009 align:start position:0% controversial figure and the space 00:09:25.009 --> 00:09:29.259 align:start position:0% controversial figure and the space because<00:09:25.670> of<00:09:26.059> her<00:09:26.540> past<00:09:26.809> affiliations<00:09:27.619> and<00:09:28.269> the 00:09:29.259 --> 00:09:29.269 align:start position:0% because of her past affiliations and the 00:09:29.269 --> 00:09:31.150 align:start position:0% because of her past affiliations and the way<00:09:29.389> she's<00:09:29.660> kind<00:09:29.899> of<00:09:29.929> handled<00:09:30.350> communications 00:09:31.150 --> 00:09:31.160 align:start position:0% way she's kind of handled communications 00:09:31.160 --> 00:09:33.100 align:start position:0% way she's kind of handled communications and<00:09:31.519> the<00:09:31.579> back-and-forth<00:09:31.759> that<00:09:32.689> they've<00:09:32.899> had 00:09:33.100 --> 00:09:33.110 align:start position:0% and the back-and-forth that they've had 00:09:33.110 --> 00:09:35.739 align:start position:0% and the back-and-forth that they've had with<00:09:33.290> these<00:09:33.980> and<00:09:34.189> manufacturers<00:09:34.910> which<00:09:35.629> I 00:09:35.739 --> 00:09:35.749 align:start position:0% with these and manufacturers which I 00:09:35.749 --> 00:09:37.509 align:start position:0% with these and manufacturers which I should<00:09:35.959> mention<00:09:35.989> these<00:09:36.350> if<00:09:36.619> manufacturers<00:09:37.339> at 00:09:37.509 --> 00:09:37.519 align:start position:0% should mention these if manufacturers at 00:09:37.519 --> 00:09:39.999 align:start position:0% should mention these if manufacturers at times<00:09:37.759> have<00:09:37.939> also<00:09:38.089> been<00:09:38.449> you<00:09:39.439> know<00:09:39.559> a<00:09:39.589> little 00:09:39.999 --> 00:09:40.009 align:start position:0% times have also been you know a little 00:09:40.009 --> 00:09:42.939 align:start position:0% times have also been you know a little bit<00:09:40.100> like<00:09:40.910> us<00:09:41.809> rowdy<00:09:42.170> with<00:09:42.679> their 00:09:42.939 --> 00:09:42.949 align:start position:0% bit like us rowdy with their 00:09:42.949 --> 00:09:45.579 align:start position:0% bit like us rowdy with their communication<00:09:43.850> as<00:09:44.299> far<00:09:44.329> as<00:09:44.660> being<00:09:44.839> anti<00:09:45.350> prog 00:09:45.579 --> 00:09:45.589 align:start position:0% communication as far as being anti prog 00:09:45.589 --> 00:09:47.319 align:start position:0% communication as far as being anti prog pal<00:09:45.860> obviously<00:09:46.549> because<00:09:46.819> they're<00:09:46.999> basic 00:09:47.319 --> 00:09:47.329 align:start position:0% pal obviously because they're basic 00:09:47.329 --> 00:09:49.030 align:start position:0% pal obviously because they're basic manufacturers<00:09:48.049> they<00:09:48.230> weren't<00:09:48.679> going<00:09:48.799> to<00:09:48.860> want 00:09:49.030 --> 00:09:49.040 align:start position:0% manufacturers they weren't going to want 00:09:49.040 --> 00:09:52.989 align:start position:0% manufacturers they weren't going to want it<00:09:49.189> so<00:09:50.059> I<00:09:51.220> don't<00:09:52.220> really<00:09:52.519> want<00:09:52.699> to<00:09:52.759> go<00:09:52.819> in<00:09:52.910> there 00:09:52.989 --> 00:09:52.999 align:start position:0% it so I don't really want to go in there 00:09:52.999 --> 00:09:55.929 align:start position:0% it so I don't really want to go in there like<00:09:53.089> super<00:09:53.660> detail<00:09:53.989> about<00:09:54.230> that<00:09:54.290> but<00:09:54.939> there's 00:09:55.929 --> 00:09:55.939 align:start position:0% like super detail about that but there's 00:09:55.939 --> 00:09:57.939 align:start position:0% like super detail about that but there's a<00:09:56.029> lot<00:09:56.119> of<00:09:56.540> interesting<00:09:57.019> articles<00:09:57.559> and<00:09:57.799> back 00:09:57.939 --> 00:09:57.949 align:start position:0% a lot of interesting articles and back 00:09:57.949 --> 00:09:59.859 align:start position:0% a lot of interesting articles and back and<00:09:58.160> forth<00:09:58.429> some<00:09:58.759> Twitter<00:09:58.999> conversations<00:09:59.660> we 00:09:59.859 --> 00:09:59.869 align:start position:0% and forth some Twitter conversations we 00:09:59.869 --> 00:10:02.079 align:start position:0% and forth some Twitter conversations we dive<00:10:00.049> into<00:10:00.290> to<00:10:00.980> get<00:10:01.309> more<00:10:01.489> information<00:10:01.939> on 00:10:02.079 --> 00:10:02.089 align:start position:0% dive into to get more information on 00:10:02.089 --> 00:10:07.059 align:start position:0% dive into to get more information on that<00:10:02.269> and<00:10:03.100> I<00:10:04.119> think<00:10:05.119> that<00:10:05.509> there<00:10:06.319> are<00:10:06.619> two 00:10:07.059 --> 00:10:07.069 align:start position:0% that and I think that there are two 00:10:07.069 --> 00:10:08.889 align:start position:0% that and I think that there are two sides<00:10:07.429> to<00:10:07.579> this<00:10:07.759> obviously<00:10:08.269> the<00:10:08.480> technical 00:10:08.889 --> 00:10:08.899 align:start position:0% sides to this obviously the technical 00:10:08.899 --> 00:10:10.479 align:start position:0% sides to this obviously the technical and<00:10:08.989> the<00:10:09.049> political<00:10:09.499> and<00:10:09.769> the<00:10:09.860> technical<00:10:10.309> has 00:10:10.479 --> 00:10:10.489 align:start position:0% and the political and the technical has 00:10:10.489 --> 00:10:13.479 align:start position:0% and the political and the technical has been<00:10:11.079> fleshed<00:10:12.079> out<00:10:12.290> using<00:10:12.589> the<00:10:12.799> audits<00:10:13.189> and 00:10:13.479 --> 00:10:13.489 align:start position:0% been fleshed out using the audits and 00:10:13.489 --> 00:10:15.069 align:start position:0% been fleshed out using the audits and technical<00:10:14.119> discussion<00:10:14.689> and<00:10:14.899> then<00:10:14.989> the 00:10:15.069 --> 00:10:15.079 align:start position:0% technical discussion and then the 00:10:15.079 --> 00:10:16.660 align:start position:0% technical discussion and then the political<00:10:15.470> side<00:10:15.649> has<00:10:15.829> not<00:10:15.980> been<00:10:16.189> fleshed<00:10:16.459> out 00:10:16.660 --> 00:10:16.670 align:start position:0% political side has not been fleshed out 00:10:16.670 --> 00:10:18.519 align:start position:0% political side has not been fleshed out because<00:10:17.449> there's<00:10:17.689> a<00:10:17.779> lot<00:10:17.839> of<00:10:18.110> very<00:10:18.410> strong 00:10:18.519 --> 00:10:18.529 align:start position:0% because there's a lot of very strong 00:10:18.529 --> 00:10:21.519 align:start position:0% because there's a lot of very strong opinions<00:10:19.249> from<00:10:19.579> certain<00:10:19.939> people<00:10:20.529> because 00:10:21.519 --> 00:10:21.529 align:start position:0% opinions from certain people because 00:10:21.529 --> 00:10:23.859 align:start position:0% opinions from certain people because there's<00:10:22.399> so<00:10:22.670> many<00:10:22.819> signs<00:10:23.149> of<00:10:23.329> the<00:10:23.449> day<00:10:23.629> it's 00:10:23.859 --> 00:10:23.869 align:start position:0% there's so many signs of the day it's 00:10:23.869 --> 00:10:25.600 align:start position:0% there's so many signs of the day it's even<00:10:24.019> a<00:10:24.199> debate<00:10:24.319> as<00:10:24.709> to<00:10:24.860> whether<00:10:25.309> the 00:10:25.600 --> 00:10:25.610 align:start position:0% even a debate as to whether the 00:10:25.610 --> 00:10:27.999 align:start position:0% even a debate as to whether the community<00:10:26.029> is<00:10:26.480> loud<00:10:26.929> about<00:10:27.230> it<00:10:27.410> or<00:10:27.829> whether 00:10:27.999 --> 00:10:28.009 align:start position:0% community is loud about it or whether 00:10:28.009 --> 00:10:30.659 align:start position:0% community is loud about it or whether it's<00:10:28.220> just<00:10:28.279> a<00:10:28.489> few<00:10:28.669> very<00:10:28.970> vocal<00:10:29.419> minority 00:10:30.659 --> 00:10:30.669 align:start position:0% it's just a few very vocal minority 00:10:30.669 --> 00:10:34.419 align:start position:0% it's just a few very vocal minority groups<00:10:31.669> that<00:10:32.019> are<00:10:33.019> just<00:10:33.259> really<00:10:33.649> loud<00:10:33.919> about 00:10:34.419 --> 00:10:34.429 align:start position:0% groups that are just really loud about 00:10:34.429 --> 00:10:37.960 align:start position:0% groups that are just really loud about it<00:10:34.610> in<00:10:34.699> general<00:10:34.910> so<00:10:36.009> it's<00:10:37.009> really<00:10:37.399> hard<00:10:37.669> to 00:10:37.960 --> 00:10:37.970 align:start position:0% it in general so it's really hard to 00:10:37.970 --> 00:10:41.739 align:start position:0% it in general so it's really hard to parse<00:10:38.269> that<00:10:38.540> it<00:10:38.720> goes<00:10:38.869> out<00:10:39.049> of<00:10:39.079> that<00:10:39.319> and<00:10:40.749> as 00:10:41.739 --> 00:10:41.749 align:start position:0% parse that it goes out of that and as 00:10:41.749 --> 00:10:43.720 align:start position:0% parse that it goes out of that and as someone<00:10:42.290> who's<00:10:42.470> kind<00:10:42.769> of<00:10:42.889> community<00:10:43.279> manager 00:10:43.720 --> 00:10:43.730 align:start position:0% someone who's kind of community manager 00:10:43.730 --> 00:10:45.249 align:start position:0% someone who's kind of community manager in<00:10:43.999> the<00:10:44.089> space<00:10:44.360> this<00:10:44.660> has<00:10:44.809> been<00:10:44.929> one<00:10:45.079> of<00:10:45.110> the 00:10:45.249 --> 00:10:45.259 align:start position:0% in the space this has been one of the 00:10:45.259 --> 00:10:49.780 align:start position:0% in the space this has been one of the hardest<00:10:45.669> things<00:10:46.669> to<00:10:47.499> reason<00:10:48.499> with<00:10:48.649> is<00:10:48.889> getting 00:10:49.780 --> 00:10:49.790 align:start position:0% hardest things to reason with is getting 00:10:49.790 --> 00:10:51.309 align:start position:0% hardest things to reason with is getting the<00:10:49.910> signals<00:10:50.119> from<00:10:50.509> the<00:10:50.600> community<00:10:51.169> about 00:10:51.309 --> 00:10:51.319 align:start position:0% the signals from the community about 00:10:51.319 --> 00:10:55.290 align:start position:0% the signals from the community about whether<00:10:51.769> or<00:10:52.100> not<00:10:52.600> Prague<00:10:53.600> palace<00:10:54.019> wanted 00:10:55.290 --> 00:10:55.300 align:start position:0% whether or not Prague palace wanted 00:10:55.300 --> 00:10:58.290 align:start position:0% whether or not Prague palace wanted or<00:10:55.630> things<00:10:56.200> like<00:10:56.440> that<00:10:57.610> we<00:10:57.880> know<00:10:58.000> the<00:10:58.120> GP 00:10:58.290 --> 00:10:58.300 align:start position:0% or things like that we know the GP 00:10:58.300 --> 00:11:00.810 align:start position:0% or things like that we know the GP minors<00:10:58.870> positions<00:10:59.380> we<00:11:00.190> know<00:11:00.430> some 00:11:00.810 --> 00:11:00.820 align:start position:0% minors positions we know some 00:11:00.820 --> 00:11:02.100 align:start position:0% minors positions we know some individuals<00:11:01.330> in<00:11:01.390> the<00:11:01.480> community<00:11:01.900> their 00:11:02.100 --> 00:11:02.110 align:start position:0% individuals in the community their 00:11:02.110 --> 00:11:04.620 align:start position:0% individuals in the community their positions<00:11:02.650> we<00:11:03.040> for<00:11:03.820> the<00:11:03.880> most<00:11:04.060> part<00:11:04.330> of<00:11:04.540> the 00:11:04.620 --> 00:11:04.630 align:start position:0% positions we for the most part of the 00:11:04.630 --> 00:11:08.280 align:start position:0% positions we for the most part of the core<00:11:04.870> developers<00:11:05.350> position<00:11:07.080> you<00:11:08.080> know<00:11:08.200> the 00:11:08.280 --> 00:11:08.290 align:start position:0% core developers position you know the 00:11:08.290 --> 00:11:11.040 align:start position:0% core developers position you know the ones<00:11:08.470> who<00:11:08.620> have<00:11:08.830> spoken<00:11:09.130> out<00:11:09.400> for<00:11:09.880> prog<00:11:10.450> pal<00:11:10.750> a 00:11:11.040 --> 00:11:11.050 align:start position:0% ones who have spoken out for prog pal a 00:11:11.050 --> 00:11:14.130 align:start position:0% ones who have spoken out for prog pal a lot<00:11:11.230> of<00:11:11.320> it<00:11:11.440> is<00:11:11.530> kind<00:11:11.770> of<00:11:12.540> abstaining<00:11:13.540> from<00:11:13.780> an 00:11:14.130 --> 00:11:14.140 align:start position:0% lot of it is kind of abstaining from an 00:11:14.140 --> 00:11:16.890 align:start position:0% lot of it is kind of abstaining from an opinion<00:11:14.350> as<00:11:14.680> well<00:11:14.920> which<00:11:15.460> is<00:11:15.490> a<00:11:15.790> choice<00:11:16.120> and<00:11:16.510> is 00:11:16.890 --> 00:11:16.900 align:start position:0% opinion as well which is a choice and is 00:11:16.900 --> 00:11:20.160 align:start position:0% opinion as well which is a choice and is something<00:11:17.170> that<00:11:17.410> is<00:11:17.710> important<00:11:18.430> in<00:11:19.170> being 00:11:20.160 --> 00:11:20.170 align:start position:0% something that is important in being 00:11:20.170 --> 00:11:21.480 align:start position:0% something that is important in being able<00:11:20.320> to<00:11:20.470> make<00:11:20.740> that<00:11:20.950> choice<00:11:21.130> of<00:11:21.370> that 00:11:21.480 --> 00:11:21.490 align:start position:0% able to make that choice of that 00:11:21.490 --> 00:11:24.260 align:start position:0% able to make that choice of that decision<00:11:21.970> when<00:11:22.150> you<00:11:22.300> are<00:11:22.710> deciding<00:11:23.710> something 00:11:24.260 --> 00:11:24.270 align:start position:0% decision when you are deciding something 00:11:24.270 --> 00:11:27.450 align:start position:0% decision when you are deciding something so<00:11:25.270> I<00:11:26.080> think<00:11:26.530> it<00:11:26.680> is<00:11:26.710> a<00:11:26.800> really<00:11:27.040> important 00:11:27.450 --> 00:11:27.460 align:start position:0% so I think it is a really important 00:11:27.460 --> 00:11:31.440 align:start position:0% so I think it is a really important discussion<00:11:27.640> I<00:11:28.180> think<00:11:28.270> that<00:11:30.090> front<00:11:31.090> love<00:11:31.300> you 00:11:31.440 --> 00:11:31.450 align:start position:0% discussion I think that front love you 00:11:31.450 --> 00:11:33.030 align:start position:0% discussion I think that front love you might<00:11:31.600> want<00:11:31.840> to<00:11:31.870> do<00:11:31.990> this<00:11:32.200> for<00:11:32.470> the<00:11:32.590> panel<00:11:32.920> we 00:11:33.030 --> 00:11:33.040 align:start position:0% might want to do this for the panel we 00:11:33.040 --> 00:11:34.860 align:start position:0% might want to do this for the panel we might<00:11:33.190> want<00:11:33.370> to<00:11:33.400> just<00:11:33.640> like<00:11:33.790> have<00:11:34.180> technical 00:11:34.860 --> 00:11:34.870 align:start position:0% might want to just like have technical 00:11:34.870 --> 00:11:36.570 align:start position:0% might want to just like have technical questions<00:11:34.900> from<00:11:35.470> the<00:11:35.620> audience<00:11:35.740> or<00:11:36.130> something 00:11:36.570 --> 00:11:36.580 align:start position:0% questions from the audience or something 00:11:36.580 --> 00:11:39.180 align:start position:0% questions from the audience or something and<00:11:36.940> discussion<00:11:37.720> and<00:11:37.900> then<00:11:38.470> people<00:11:38.890> want<00:11:39.130> to 00:11:39.180 --> 00:11:39.190 align:start position:0% and discussion and then people want to 00:11:39.190 --> 00:11:40.950 align:start position:0% and discussion and then people want to throw<00:11:39.310> in<00:11:39.460> some<00:11:39.640> politic<00:11:40.060> discussion<00:11:40.690> later 00:11:40.950 --> 00:11:40.960 align:start position:0% throw in some politic discussion later 00:11:40.960 --> 00:11:42.900 align:start position:0% throw in some politic discussion later which<00:11:41.740> will<00:11:41.890> probably<00:11:42.070> have<00:11:42.400> it<00:11:42.550> because<00:11:42.700> more 00:11:42.900 --> 00:11:42.910 align:start position:0% which will probably have it because more 00:11:42.910 --> 00:11:44.790 align:start position:0% which will probably have it because more people<00:11:42.940> are<00:11:43.390> more<00:11:43.750> familiar<00:11:43.900> with<00:11:44.290> that<00:11:44.350> side 00:11:44.790 --> 00:11:44.800 align:start position:0% people are more familiar with that side 00:11:44.800 --> 00:11:46.980 align:start position:0% people are more familiar with that side of<00:11:44.830> it<00:11:45.100> I<00:11:45.130> think<00:11:45.280> then<00:11:46.090> that<00:11:46.510> would<00:11:46.630> be<00:11:46.660> cool 00:11:46.980 --> 00:11:46.990 align:start position:0% of it I think then that would be cool 00:11:46.990 --> 00:11:51.180 align:start position:0% of it I think then that would be cool too<00:11:47.290> so<00:11:48.090> if<00:11:49.090> anyone<00:11:49.360> has<00:11:49.540> questions<00:11:49.660> on<00:11:50.350> or<00:11:50.890> the 00:11:51.180 --> 00:11:51.190 align:start position:0% too so if anyone has questions on or the 00:11:51.190 --> 00:11:54.030 align:start position:0% too so if anyone has questions on or the specifics<00:11:51.820> that<00:11:51.910> Liz<00:11:52.210> mentioned<00:11:52.710> or<00:11:53.710> any 00:11:54.030 --> 00:11:54.040 align:start position:0% specifics that Liz mentioned or any 00:11:54.040 --> 00:11:55.950 align:start position:0% specifics that Liz mentioned or any technical<00:11:54.430> questions<00:11:54.550> feel<00:11:55.330> free<00:11:55.360> and<00:11:55.810> add 00:11:55.950 --> 00:11:55.960 align:start position:0% technical questions feel free and add 00:11:55.960 --> 00:11:58.170 align:start position:0% technical questions feel free and add just<00:11:56.200> if<00:11:56.500> you<00:11:56.710> don't<00:11:57.250> mind<00:11:57.580> come<00:11:57.880> up<00:11:58.000> to<00:11:58.090> the 00:11:58.170 --> 00:11:58.180 align:start position:0% just if you don't mind come up to the 00:11:58.180 --> 00:12:00.780 align:start position:0% just if you don't mind come up to the microphone<00:11:58.690> so<00:11:58.900> it<00:11:59.020> can<00:11:59.140> be<00:11:59.260> on<00:11:59.380> the<00:11:59.790> recording 00:12:00.780 --> 00:12:00.790 align:start position:0% microphone so it can be on the recording 00:12:00.790 --> 00:12:02.430 align:start position:0% microphone so it can be on the recording or<00:12:01.090> whatever<00:12:01.390> you<00:12:01.870> not<00:12:02.020> to<00:12:02.140> show<00:12:02.260> your<00:12:02.290> face 00:12:02.430 --> 00:12:02.440 align:start position:0% or whatever you not to show your face 00:12:02.440 --> 00:12:05.340 align:start position:0% or whatever you not to show your face I'll<00:12:02.830> just<00:12:02.950> hit<00:12:03.100> the<00:12:03.220> microphone 00:12:05.340 --> 00:12:05.350 align:start position:0% I'll just hit the microphone 00:12:05.350 --> 00:12:08.450 align:start position:0% I'll just hit the microphone suddeniy<00:12:06.040> one<00:12:06.160> have<00:12:06.340> any<00:12:06.550> questions<00:12:06.970> yet<00:12:07.240> Jeff 00:12:08.450 --> 00:12:08.460 align:start position:0% suddeniy one have any questions yet Jeff 00:12:08.460 --> 00:12:15.150 align:start position:0% suddeniy one have any questions yet Jeff already<00:12:09.460> attitude<00:12:09.670> whatever<00:12:13.440> so<00:12:14.440> I<00:12:14.770> know<00:12:15.040> we 00:12:15.150 --> 00:12:15.160 align:start position:0% already attitude whatever so I know we 00:12:15.160 --> 00:12:17.610 align:start position:0% already attitude whatever so I know we can<00:12:15.310> read<00:12:15.490> the<00:12:15.840> report<00:12:16.840> from<00:12:17.050> this<00:12:17.260> is<00:12:17.380> already 00:12:17.610 --> 00:12:17.620 align:start position:0% can read the report from this is already 00:12:17.620 --> 00:12:19.380 align:start position:0% can read the report from this is already but<00:12:17.740> I<00:12:17.770> think<00:12:18.070> like<00:12:18.220> one<00:12:18.790> of<00:12:18.880> the<00:12:18.970> technical 00:12:19.380 --> 00:12:19.390 align:start position:0% but I think like one of the technical 00:12:19.390 --> 00:12:21.060 align:start position:0% but I think like one of the technical questions<00:12:19.540> that<00:12:20.140> I've<00:12:20.470> seen<00:12:20.680> coming<00:12:20.950> up<00:12:21.010> a 00:12:21.060 --> 00:12:21.070 align:start position:0% questions that I've seen coming up a 00:12:21.070 --> 00:12:25.590 align:start position:0% questions that I've seen coming up a couple<00:12:21.280> times<00:12:21.690> is<00:12:22.690> this<00:12:23.020> notion<00:12:23.290> of<00:12:23.610> like<00:12:24.610> if 00:12:25.590 --> 00:12:25.600 align:start position:0% couple times is this notion of like if 00:12:25.600 --> 00:12:27.480 align:start position:0% couple times is this notion of like if if<00:12:25.990> the<00:12:26.200> creators<00:12:26.590> of<00:12:26.650> our<00:12:26.770> cars<00:12:27.160> these 00:12:27.480 --> 00:12:27.490 align:start position:0% if the creators of our cars these 00:12:27.490 --> 00:12:29.310 align:start position:0% if the creators of our cars these shadowy<00:12:28.000> figures<00:12:28.330> like<00:12:28.540> what<00:12:28.810> there's<00:12:29.110> some 00:12:29.310 --> 00:12:29.320 align:start position:0% shadowy figures like what there's some 00:12:29.320 --> 00:12:31.950 align:start position:0% shadowy figures like what there's some secret<00:12:29.770> basic<00:12:30.130> ability<00:12:30.550> you<00:12:31.180> know<00:12:31.300> I<00:12:31.330> hear<00:12:31.690> and 00:12:31.950 --> 00:12:31.960 align:start position:0% secret basic ability you know I hear and 00:12:31.960 --> 00:12:33.890 align:start position:0% secret basic ability you know I hear and I<00:12:32.410> wonder<00:12:32.950> if<00:12:33.010> you<00:12:33.070> could<00:12:33.160> just<00:12:33.220> kind<00:12:33.400> of<00:12:33.490> like 00:12:33.890 --> 00:12:33.900 align:start position:0% I wonder if you could just kind of like 00:12:33.900 --> 00:12:36.540 align:start position:0% I wonder if you could just kind of like summarize<00:12:34.900> lately<00:12:35.350> like<00:12:35.650> basically<00:12:36.340> the 00:12:36.540 --> 00:12:36.550 align:start position:0% summarize lately like basically the 00:12:36.550 --> 00:12:37.950 align:start position:0% summarize lately like basically the rough<00:12:36.850> conclusion<00:12:37.270> of<00:12:37.330> the<00:12:37.390> report<00:12:37.510> on<00:12:37.840> this 00:12:37.950 --> 00:12:37.960 align:start position:0% rough conclusion of the report on this 00:12:37.960 --> 00:12:41.670 align:start position:0% rough conclusion of the report on this idea<00:12:38.350> of<00:12:38.650> like<00:12:39.420> is<00:12:40.420> it<00:12:40.630> possible<00:12:41.140> that<00:12:41.200> that 00:12:41.670 --> 00:12:41.680 align:start position:0% idea of like is it possible that that 00:12:41.680 --> 00:12:45.450 align:start position:0% idea of like is it possible that that the<00:12:43.530> developers<00:12:44.530> that<00:12:44.680> would<00:12:44.830> have<00:12:45.070> a<00:12:45.100> secret 00:12:45.450 --> 00:12:45.460 align:start position:0% the developers that would have a secret 00:12:45.460 --> 00:12:54.960 align:start position:0% the developers that would have a secret ASIC<00:12:45.760> up<00:12:45.910> their<00:12:46.090> sleeves<00:12:46.450> and<00:12:53.700> on<00:12:54.700> a<00:12:54.760> higher 00:12:54.960 --> 00:12:54.970 align:start position:0% ASIC up their sleeves and on a higher 00:12:54.970 --> 00:12:56.970 align:start position:0% ASIC up their sleeves and on a higher level<00:12:55.050> not<00:12:56.050> that<00:12:56.260> we<00:12:56.350> can<00:12:56.530> find 00:12:56.970 --> 00:12:56.980 align:start position:0% level not that we can find 00:12:56.980 --> 00:12:59.850 align:start position:0% level not that we can find I<00:12:57.160> mean<00:12:58.230> security<00:12:59.230> audits<00:12:59.500> aren't<00:12:59.650> a<00:12:59.710> perfect 00:12:59.850 --> 00:12:59.860 align:start position:0% I mean security audits aren't a perfect 00:12:59.860 --> 00:13:02.010 align:start position:0% I mean security audits aren't a perfect two<00:13:00.160> thing<00:13:00.340> we<00:13:00.790> look<00:13:01.270> if<00:13:01.480> we<00:13:01.510> spend<00:13:01.810> a<00:13:01.870> certain 00:13:02.010 --> 00:13:02.020 align:start position:0% two thing we look if we spend a certain 00:13:02.020 --> 00:13:03.570 align:start position:0% two thing we look if we spend a certain amount<00:13:02.200> of<00:13:02.320> time<00:13:02.500> and<00:13:02.650> we<00:13:02.680> look<00:13:02.830> as<00:13:03.100> hard<00:13:03.340> as<00:13:03.460> we 00:13:03.570 --> 00:13:03.580 align:start position:0% amount of time and we look as hard as we 00:13:03.580 --> 00:13:11.890 align:start position:0% amount of time and we look as hard as we can<00:13:03.810> also<00:13:04.810> Bob<00:13:05.170> spent<00:13:07.260> months<00:13:09.540> also 00:13:11.890 --> 00:13:11.900 align:start position:0% can also Bob spent months also 00:13:11.900 --> 00:13:14.110 align:start position:0% can also Bob spent months also who<00:13:12.110> was<00:13:12.230> looking<00:13:12.470> at<00:13:12.560> the<00:13:12.650> hardware<00:13:12.920> and<00:13:13.160> he 00:13:14.110 --> 00:13:14.120 align:start position:0% who was looking at the hardware and he 00:13:14.120 --> 00:13:16.360 align:start position:0% who was looking at the hardware and he really<00:13:14.660> liked<00:13:15.140> I<00:13:15.350> mean<00:13:15.589> our<00:13:15.950> team<00:13:15.980> was 00:13:16.360 --> 00:13:16.370 align:start position:0% really liked I mean our team was 00:13:16.370 --> 00:13:18.190 align:start position:0% really liked I mean our team was communicating<00:13:16.970> with<00:13:17.000> him<00:13:17.270> too<00:13:17.510> and<00:13:17.779> we<00:13:17.930> really 00:13:18.190 --> 00:13:18.200 align:start position:0% communicating with him too and we really 00:13:18.200 --> 00:13:19.570 align:start position:0% communicating with him too and we really dug<00:13:18.380> into<00:13:18.560> some<00:13:18.710> things<00:13:19.070> and<00:13:19.250> that's<00:13:19.400> how<00:13:19.520> we 00:13:19.570 --> 00:13:19.580 align:start position:0% dug into some things and that's how we 00:13:19.580 --> 00:13:22.540 align:start position:0% dug into some things and that's how we came<00:13:19.820> up<00:13:20.000> with<00:13:20.150> even<00:13:20.870> the<00:13:21.020> weight<00:13:21.589> evaluation 00:13:22.540 --> 00:13:22.550 align:start position:0% came up with even the weight evaluation 00:13:22.550 --> 00:13:51.000 align:start position:0% came up with even the weight evaluation from<00:13:22.720> that<00:13:23.720> one<00:13:49.029> supply<00:13:50.029> chain<00:13:50.450> attack 00:13:51.000 --> 00:13:51.010 align:start position:0% from that one supply chain attack 00:13:51.010 --> 00:13:55.540 align:start position:0% from that one supply chain attack manufacturing<00:13:52.010> side<00:13:52.279> attacks<00:13:54.010> if<00:13:55.010> we<00:13:55.160> can<00:13:55.339> do 00:13:55.540 --> 00:13:55.550 align:start position:0% manufacturing side attacks if we can do 00:13:55.550 --> 00:13:58.930 align:start position:0% manufacturing side attacks if we can do certain<00:13:55.820> things<00:13:56.000> but<00:13:57.310> experiment<00:13:58.310> this 00:13:58.930 --> 00:13:58.940 align:start position:0% certain things but experiment this 00:13:58.940 --> 00:14:02.050 align:start position:0% certain things but experiment this project<00:13:59.779> is<00:13:59.960> concerned<00:14:00.370> it<00:14:01.370> cannot<00:14:01.790> really 00:14:02.050 --> 00:14:02.060 align:start position:0% project is concerned it cannot really 00:14:02.060 --> 00:14:04.250 align:start position:0% project is concerned it cannot really affect<00:14:02.540> anything 00:14:04.250 --> 00:14:04.260 align:start position:0% affect anything 00:14:04.260 --> 00:14:10.150 align:start position:0% affect anything [Music] 00:14:10.150 --> 00:14:10.160 align:start position:0% 00:14:10.160 --> 00:14:13.730 align:start position:0% effect<00:14:11.060> anything<00:14:11.750> more<00:14:11.960> than<00:14:12.200> that 00:14:13.730 --> 00:14:13.740 align:start position:0% effect anything more than that 00:14:13.740 --> 00:14:33.440 align:start position:0% effect anything more than that [Music] 00:14:33.440 --> 00:14:33.450 align:start position:0% 00:14:33.450 --> 00:14:39.450 align:start position:0% [Music] 00:14:39.450 --> 00:14:39.460 align:start position:0% 00:14:39.460 --> 00:14:43.240 align:start position:0% [Music] 00:14:43.240 --> 00:14:43.250 align:start position:0% 00:14:43.250 --> 00:14:50.690 align:start position:0% that<00:14:44.250> is<00:14:45.180> like<00:14:45.450> currently<00:14:46.290> we<00:14:46.560> have<00:14:46.730> cash<00:14:49.700> from 00:14:50.690 --> 00:14:50.700 align:start position:0% that is like currently we have cash from 00:14:50.700 --> 00:15:01.340 align:start position:0% that is like currently we have cash from the<00:14:50.910> cash<00:14:55.160> so<00:14:56.160> cash<00:14:57.110> is<00:14:58.110> a<00:14:58.230> star<00:14:59.420> like<00:15:00.420> 30<00:15:00.900> and 00:15:01.340 --> 00:15:01.350 align:start position:0% the cash so cash is a star like 30 and 00:15:01.350 --> 00:15:04.579 align:start position:0% the cash so cash is a star like 30 and we<00:15:01.920> just<00:15:02.640> argued<00:15:03.029> and<00:15:03.180> disclosed<00:15:03.779> and 00:15:04.579 --> 00:15:04.589 align:start position:0% we just argued and disclosed and 00:15:04.589 --> 00:15:07.490 align:start position:0% we just argued and disclosed and technicality<00:15:05.370> damn<00:15:06.330> this<00:15:06.690> is<00:15:06.870> much<00:15:07.200> bigger 00:15:07.490 --> 00:15:07.500 align:start position:0% technicality damn this is much bigger 00:15:07.500 --> 00:15:11.510 align:start position:0% technicality damn this is much bigger like<00:15:08.160> 4gb<00:15:08.730> start<00:15:09.450> with<00:15:09.630> 1gb<00:15:10.620> of<00:15:10.980> something 00:15:11.510 --> 00:15:11.520 align:start position:0% like 4gb start with 1gb of something 00:15:11.520 --> 00:15:18.260 align:start position:0% like 4gb start with 1gb of something attempted<00:15:11.940> crows<00:15:12.210> or<00:15:12.540> dime<00:15:13.850> now<00:15:15.620> what<00:15:16.620> if<00:15:17.270> you 00:15:18.260 --> 00:15:18.270 align:start position:0% attempted crows or dime now what if you 00:15:18.270 --> 00:15:19.269 align:start position:0% attempted crows or dime now what if you can 00:15:19.269 --> 00:15:19.279 align:start position:0% can 00:15:19.279 --> 00:15:22.869 align:start position:0% can evaluate<00:15:20.209> the<00:15:20.569> tag<00:15:21.410> on<00:15:21.769> the<00:15:22.009> fly<00:15:22.250> so<00:15:22.310> currently 00:15:22.869 --> 00:15:22.879 align:start position:0% evaluate the tag on the fly so currently 00:15:22.879 --> 00:15:26.199 align:start position:0% evaluate the tag on the fly so currently the<00:15:23.120> bag<00:15:23.329> is<00:15:23.540> pre<00:15:23.810> and<00:15:24.050> later<00:15:24.319> before<00:15:24.980> a<00:15:25.459> period 00:15:26.199 --> 00:15:26.209 align:start position:0% the bag is pre and later before a period 00:15:26.209 --> 00:15:30.100 align:start position:0% the bag is pre and later before a period and<00:15:26.870> then<00:15:26.930> for<00:15:27.230> the<00:15:27.290> next<00:15:27.589> period<00:15:28.360> you<00:15:29.360> pre 00:15:30.100 --> 00:15:30.110 align:start position:0% and then for the next period you pre 00:15:30.110 --> 00:15:32.050 align:start position:0% and then for the next period you pre calculate<00:15:30.620> the<00:15:30.769> tag<00:15:30.980> and<00:15:31.189> switch<00:15:31.430> to<00:15:31.610> it<00:15:31.730> so 00:15:32.050 --> 00:15:32.060 align:start position:0% calculate the tag and switch to it so 00:15:32.060 --> 00:15:34.300 align:start position:0% calculate the tag and switch to it so that<00:15:32.209> you<00:15:32.509> don't<00:15:32.569> suffer<00:15:33.230> any<00:15:33.560> delay<00:15:33.829> since 00:15:34.300 --> 00:15:34.310 align:start position:0% that you don't suffer any delay since 00:15:34.310 --> 00:15:37.929 align:start position:0% that you don't suffer any delay since it's<00:15:34.639> the<00:15:34.819> new<00:15:34.970> video<00:15:35.329> so<00:15:36.199> now<00:15:36.579> what<00:15:37.579> if<00:15:37.730> you 00:15:37.929 --> 00:15:37.939 align:start position:0% it's the new video so now what if you 00:15:37.939 --> 00:15:41.319 align:start position:0% it's the new video so now what if you can<00:15:38.509> calculate<00:15:38.949> the<00:15:39.949> tag<00:15:40.220> on<00:15:40.459> the<00:15:40.819> fly<00:15:41.029> from 00:15:41.319 --> 00:15:41.329 align:start position:0% can calculate the tag on the fly from 00:15:41.329 --> 00:15:45.220 align:start position:0% can calculate the tag on the fly from the<00:15:41.810> cache<00:15:42.459> so<00:15:43.459> for<00:15:43.670> that<00:15:43.819> you<00:15:44.509> need<00:15:44.750> to<00:15:44.779> store 00:15:45.220 --> 00:15:45.230 align:start position:0% the cache so for that you need to store 00:15:45.230 --> 00:15:48.699 align:start position:0% the cache so for that you need to store these<00:15:45.560> and<00:15:45.860> dev<00:15:46.399> cash<00:15:46.870> or<00:15:47.870> check 00:15:48.699 --> 00:15:48.709 align:start position:0% these and dev cash or check 00:15:48.709 --> 00:15:51.790 align:start position:0% these and dev cash or check so<00:15:49.430> right<00:15:49.670> now<00:15:49.879> the<00:15:50.540> or<00:15:50.899> cheapness<00:15:51.170> Ram<00:15:51.589> is 00:15:51.790 --> 00:15:51.800 align:start position:0% so right now the or cheapness Ram is 00:15:51.800 --> 00:15:55.150 align:start position:0% so right now the or cheapness Ram is very<00:15:52.069> expensive<00:15:52.430> or<00:15:52.879> harder<00:15:53.709> so<00:15:54.709> it's<00:15:54.949> very 00:15:55.150 --> 00:15:55.160 align:start position:0% very expensive or harder so it's very 00:15:55.160 --> 00:15:59.110 align:start position:0% very expensive or harder so it's very expensive<00:15:55.720> I<00:15:56.720> am<00:15:57.339> right<00:15:58.339> now<00:15:58.370> you<00:15:58.550> see<00:15:58.910> the 00:15:59.110 --> 00:15:59.120 align:start position:0% expensive I am right now you see the 00:15:59.120 --> 00:16:01.869 align:start position:0% expensive I am right now you see the current<00:15:59.839> cpus<00:16:00.500> and<00:16:00.529> gpus<00:16:00.769> are<00:16:01.220> a<00:16:01.430> few 00:16:01.869 --> 00:16:01.879 align:start position:0% current cpus and gpus are a few 00:16:01.879 --> 00:16:12.309 align:start position:0% current cpus and gpus are a few kilobytes<00:16:05.560> there<00:16:06.560> is<00:16:06.680> also<00:16:07.449> the<00:16:08.449> power<00:16:11.319> memory 00:16:12.309 --> 00:16:12.319 align:start position:0% kilobytes there is also the power memory 00:16:12.319 --> 00:16:15.129 align:start position:0% kilobytes there is also the power memory much<00:16:12.740> higher<00:16:13.040> than<00:16:13.790> the<00:16:13.970> power<00:16:14.180> to<00:16:14.480> access<00:16:14.810> the 00:16:15.129 --> 00:16:15.139 align:start position:0% much higher than the power to access the 00:16:15.139 --> 00:16:16.569 align:start position:0% much higher than the power to access the internal<00:16:15.500> memory<00:16:15.860> so<00:16:16.069> there<00:16:16.220> is<00:16:16.310> a<00:16:16.339> big 00:16:16.569 --> 00:16:16.579 align:start position:0% internal memory so there is a big 00:16:16.579 --> 00:16:19.179 align:start position:0% internal memory so there is a big advantage<00:16:16.910> when<00:16:17.899> things<00:16:18.410> are<00:16:18.649> in<00:16:18.949> the 00:16:19.179 --> 00:16:19.189 align:start position:0% advantage when things are in the 00:16:19.189 --> 00:16:23.860 align:start position:0% advantage when things are in the internal<00:16:19.730> ram<00:16:20.410> so<00:16:21.410> now<00:16:22.060> according<00:16:23.060> to<00:16:23.329> Bob<00:16:23.509> who 00:16:23.860 --> 00:16:23.870 align:start position:0% internal ram so now according to Bob who 00:16:23.870 --> 00:16:28.179 align:start position:0% internal ram so now according to Bob who is<00:16:24.139> an<00:16:24.439> expert<00:16:24.649> in<00:16:24.800> hardware<00:16:26.889> after<00:16:27.889> few<00:16:28.160> years 00:16:28.179 --> 00:16:28.189 align:start position:0% is an expert in hardware after few years 00:16:28.189 --> 00:16:30.610 align:start position:0% is an expert in hardware after few years maybe<00:16:28.819> four<00:16:29.540> or<00:16:29.600> five<00:16:29.720> years<00:16:30.170> down<00:16:30.379> the<00:16:30.589> line 00:16:30.610 --> 00:16:30.620 align:start position:0% maybe four or five years down the line 00:16:30.620 --> 00:16:35.350 align:start position:0% maybe four or five years down the line maybe<00:16:30.949> 20<00:16:31.490> 23<00:16:31.970> 24<00:16:32.660> we<00:16:33.500> may<00:16:33.680> see<00:16:34.160> higher<00:16:35.059> and 00:16:35.350 --> 00:16:35.360 align:start position:0% maybe 20 23 24 we may see higher and 00:16:35.360 --> 00:16:36.200 align:start position:0% maybe 20 23 24 we may see higher and higher<00:16:35.569> capacity 00:16:36.200 --> 00:16:36.210 align:start position:0% higher capacity 00:16:36.210 --> 00:16:40.240 align:start position:0% higher capacity as<00:16:36.540> our<00:16:36.960> cheapest<00:16:37.410> trap<00:16:37.680> or<00:16:38.670> it<00:16:39.300> will<00:16:39.450> become 00:16:40.240 --> 00:16:40.250 align:start position:0% as our cheapest trap or it will become 00:16:40.250 --> 00:16:43.160 align:start position:0% as our cheapest trap or it will become cost-effective<00:16:41.250> to<00:16:41.430> put<00:16:41.670> SRAM<00:16:42.270> more<00:16:42.750> and<00:16:43.020> more 00:16:43.160 --> 00:16:43.170 align:start position:0% cost-effective to put SRAM more and more 00:16:43.170 --> 00:16:48.019 align:start position:0% cost-effective to put SRAM more and more as<00:16:43.380> our<00:16:43.890> disappeared<00:16:44.870> or<00:16:45.870> the<00:16:46.110> die<00:16:46.290> so<00:16:46.920> that<00:16:47.610> is 00:16:48.019 --> 00:16:48.029 align:start position:0% as our disappeared or the die so that is 00:16:48.029 --> 00:16:50.840 align:start position:0% as our disappeared or the die so that is probably<00:16:48.500> point<00:16:49.500> these<00:16:50.220> attacks<00:16:50.640> are<00:16:50.820> the 00:16:50.840 --> 00:16:50.850 align:start position:0% probably point these attacks are the 00:16:50.850 --> 00:16:52.850 align:start position:0% probably point these attacks are the more<00:16:51.089> practical<00:16:51.600> so<00:16:52.380> there<00:16:52.500> are<00:16:52.589> ways<00:16:52.800> to 00:16:52.850 --> 00:16:52.860 align:start position:0% more practical so there are ways to 00:16:52.860 --> 00:16:54.769 align:start position:0% more practical so there are ways to mitigate<00:16:53.190> that<00:16:53.670> you<00:16:53.820> can<00:16:54.000> equal<00:16:54.330> to<00:16:54.420> increase 00:16:54.769 --> 00:16:54.779 align:start position:0% mitigate that you can equal to increase 00:16:54.779 --> 00:16:56.690 align:start position:0% mitigate that you can equal to increase the<00:16:55.020> number<00:16:55.470> of<00:16:55.589> patterns<00:16:55.890> that<00:16:56.310> are<00:16:56.459> going 00:16:56.690 --> 00:16:56.700 align:start position:0% the number of patterns that are going 00:16:56.700 --> 00:16:59.269 align:start position:0% the number of patterns that are going into<00:16:56.820> the<00:16:57.000> bag<00:16:57.209> so<00:16:57.839> the<00:16:58.050> computation<00:16:58.500> part<00:16:59.010> of 00:16:59.269 --> 00:16:59.279 align:start position:0% into the bag so the computation part of 00:16:59.279 --> 00:17:02.260 align:start position:0% into the bag so the computation part of it<00:16:59.430> dominates<00:17:00.209> the<00:17:00.510> memory<00:17:01.200> part<00:17:01.500> of<00:17:01.680> it 00:17:02.260 --> 00:17:02.270 align:start position:0% it dominates the memory part of it 00:17:02.270 --> 00:17:04.400 align:start position:0% it dominates the memory part of it because<00:17:03.270> if<00:17:03.420> you're<00:17:03.779> also<00:17:03.899> doing<00:17:04.110> some 00:17:04.400 --> 00:17:04.410 align:start position:0% because if you're also doing some 00:17:04.410 --> 00:17:08.120 align:start position:0% because if you're also doing some computation<00:17:05.040> right<00:17:05.400> to<00:17:05.819> do<00:17:06.689> FMV<00:17:07.559> the<00:17:07.770> values 00:17:08.120 --> 00:17:08.130 align:start position:0% computation right to do FMV the values 00:17:08.130 --> 00:17:10.250 align:start position:0% computation right to do FMV the values together<00:17:08.490> and<00:17:08.699> attach<00:17:09.089> them<00:17:09.420> so<00:17:09.990> you<00:17:10.079> could 00:17:10.250 --> 00:17:10.260 align:start position:0% together and attach them so you could 00:17:10.260 --> 00:17:14.240 align:start position:0% together and attach them so you could increase<00:17:11.100> the<00:17:11.309> number<00:17:12.860> that<00:17:13.860> are<00:17:13.920> fetching 00:17:14.240 --> 00:17:14.250 align:start position:0% increase the number that are fetching 00:17:14.250 --> 00:17:18.890 align:start position:0% increase the number that are fetching blocks<00:17:14.970> from<00:17:15.360> the<00:17:15.689> cache<00:17:17.000> that's<00:17:18.000> one<00:17:18.329> way<00:17:18.510> to 00:17:18.890 --> 00:17:18.900 align:start position:0% blocks from the cache that's one way to 00:17:18.900 --> 00:17:23.030 align:start position:0% blocks from the cache that's one way to mitigate<00:17:19.800> that<00:17:19.829> and<00:17:20.329> also<00:17:21.329> the<00:17:21.839> size<00:17:22.079> of<00:17:22.470> the 00:17:23.030 --> 00:17:23.040 align:start position:0% mitigate that and also the size of the 00:17:23.040 --> 00:17:26.419 align:start position:0% mitigate that and also the size of the cache<00:17:23.250> and<00:17:23.579> the<00:17:23.730> tyrosine<00:17:24.650> so<00:17:25.650> that<00:17:26.069> would 00:17:26.419 --> 00:17:26.429 align:start position:0% cache and the tyrosine so that would 00:17:26.429 --> 00:17:28.309 align:start position:0% cache and the tyrosine so that would also<00:17:26.640> be<00:17:26.790> working<00:17:27.089> against<00:17:27.569> this<00:17:27.839> hardware 00:17:28.309 --> 00:17:28.319 align:start position:0% also be working against this hardware 00:17:28.319 --> 00:17:31.190 align:start position:0% also be working against this hardware advances<00:17:29.309> because<00:17:29.580> on<00:17:29.700> one<00:17:29.880> side<00:17:29.940> Hardware<00:17:30.660> is 00:17:31.190 --> 00:17:31.200 align:start position:0% advances because on one side Hardware is 00:17:31.200 --> 00:17:33.470 align:start position:0% advances because on one side Hardware is advancing<00:17:31.830> that<00:17:32.040> it<00:17:32.760> will<00:17:32.910> become<00:17:33.179> more<00:17:33.330> and 00:17:33.470 --> 00:17:33.480 align:start position:0% advancing that it will become more and 00:17:33.480 --> 00:17:36.230 align:start position:0% advancing that it will become more and more<00:17:33.540> feasible<00:17:33.929> to<00:17:34.230> put<00:17:34.350> memory<00:17:35.040> more<00:17:36.030> and 00:17:36.230 --> 00:17:36.240 align:start position:0% more feasible to put memory more and 00:17:36.240 --> 00:17:40.549 align:start position:0% more feasible to put memory more and more<00:17:36.390> memory<00:17:36.600> to<00:17:37.020> the<00:17:37.220> die<00:17:38.220> whereas<00:17:39.350> it<00:17:40.350> should 00:17:40.549 --> 00:17:40.559 align:start position:0% more memory to the die whereas it should 00:17:40.559 --> 00:17:43.180 align:start position:0% more memory to the die whereas it should increase<00:17:40.860> the<00:17:41.040> cache<00:17:41.760> size<00:17:42.030> for<00:17:42.300> example<00:17:42.330> say 00:17:43.180 --> 00:17:43.190 align:start position:0% increase the cache size for example say 00:17:43.190 --> 00:17:46.180 align:start position:0% increase the cache size for example say next<00:17:44.190> iteration<00:17:44.910> we<00:17:45.030> are<00:17:45.120> going<00:17:45.330> to<00:17:45.450> have<00:17:45.630> say 00:17:46.180 --> 00:17:46.190 align:start position:0% next iteration we are going to have say 00:17:46.190 --> 00:17:49.430 align:start position:0% next iteration we are going to have say 200<00:17:47.190> MB<00:17:47.540> it's<00:17:48.540> a<00:17:48.630> time<00:17:48.809> they<00:17:48.929> become<00:17:49.230> more 00:17:49.430 --> 00:17:49.440 align:start position:0% 200 MB it's a time they become more 00:17:49.440 --> 00:17:53.750 align:start position:0% 200 MB it's a time they become more difficult<00:17:50.220> to<00:17:50.780> put<00:17:51.780> that<00:17:52.040> cost<00:17:53.040> will<00:17:53.309> work<00:17:53.520> and 00:17:53.750 --> 00:17:53.760 align:start position:0% difficult to put that cost will work and 00:17:53.760 --> 00:17:58.320 align:start position:0% difficult to put that cost will work and yes<00:17:53.910> you<00:17:55.790> did<00:17:56.790> I 00:17:58.320 --> 00:17:58.330 align:start position:0% yes you did I 00:17:58.330 --> 00:18:03.500 align:start position:0% yes you did I it's<00:17:58.750> great<00:17:58.960> at<00:17:59.080> this 00:18:03.500 --> 00:18:03.510 align:start position:0% 00:18:03.510 --> 00:18:04.970 align:start position:0% okay<00:18:04.140> do<00:18:04.230> they<00:18:04.350> have<00:18:04.440> other<00:18:04.500> technical 00:18:04.970 --> 00:18:04.980 align:start position:0% okay do they have other technical 00:18:04.980 --> 00:18:09.250 align:start position:0% okay do they have other technical questions 00:18:09.250 --> 00:18:09.260 align:start position:0% 00:18:09.260 --> 00:18:11.350 align:start position:0% so<00:18:10.070> when<00:18:10.250> you<00:18:10.340> say<00:18:10.520> that<00:18:10.700> there's<00:18:11.030> a<00:18:11.060> light 00:18:11.350 --> 00:18:11.360 align:start position:0% so when you say that there's a light 00:18:11.360 --> 00:18:14.740 align:start position:0% so when you say that there's a light mining<00:18:11.780> attack<00:18:12.050> or<00:18:12.550> convenience<00:18:13.550> like<00:18:14.390> my<00:18:14.540> bio 00:18:14.740 --> 00:18:14.750 align:start position:0% mining attack or convenience like my bio 00:18:14.750 --> 00:18:16.810 align:start position:0% mining attack or convenience like my bio is<00:18:14.930> repeated<00:18:15.320> like<00:18:15.470> an<00:18:15.590> overview<00:18:16.070> or<00:18:16.250> was<00:18:16.700> that 00:18:16.810 --> 00:18:16.820 align:start position:0% is repeated like an overview or was that 00:18:16.820 --> 00:18:21.580 align:start position:0% is repeated like an overview or was that was<00:18:17.000> that<00:18:17.030> pretty<00:18:17.330> much<00:18:17.740> sustained<00:18:18.740> okay<00:18:20.590> yeah 00:18:21.580 --> 00:18:21.590 align:start position:0% was that pretty much sustained okay yeah 00:18:21.590 --> 00:18:24.660 align:start position:0% was that pretty much sustained okay yeah that'd<00:18:21.860> be<00:18:21.950> perfect 00:18:24.660 --> 00:18:24.670 align:start position:0% 00:18:24.670 --> 00:18:27.160 align:start position:0% I<00:18:25.670> guess<00:18:26.000> basically<00:18:26.210> what<00:18:26.600> that<00:18:26.630> means<00:18:26.750> right 00:18:27.160 --> 00:18:27.170 align:start position:0% I guess basically what that means right 00:18:27.170 --> 00:18:28.660 align:start position:0% I guess basically what that means right now<00:18:27.380> is<00:18:27.560> that<00:18:27.680> it's<00:18:27.830> not<00:18:27.950> possible<00:18:27.980> right<00:18:28.640> now 00:18:28.660 --> 00:18:28.670 align:start position:0% now is that it's not possible right now 00:18:28.670 --> 00:18:30.520 align:start position:0% now is that it's not possible right now that<00:18:29.450> we<00:18:29.540> think<00:18:29.570> it<00:18:29.810> could<00:18:29.960> be<00:18:30.050> possible<00:18:30.380> in 00:18:30.520 --> 00:18:30.530 align:start position:0% that we think it could be possible in 00:18:30.530 --> 00:18:32.560 align:start position:0% that we think it could be possible in five<00:18:30.710> four<00:18:30.920> to<00:18:31.040> five<00:18:31.190> years<00:18:31.460> but<00:18:32.210> there<00:18:32.390> is<00:18:32.540> a 00:18:32.560 --> 00:18:32.570 align:start position:0% five four to five years but there is a 00:18:32.570 --> 00:18:33.940 align:start position:0% five four to five years but there is a mitigation<00:18:32.960> strategy<00:18:33.140> that<00:18:33.770> can<00:18:33.860> be 00:18:33.940 --> 00:18:33.950 align:start position:0% mitigation strategy that can be 00:18:33.950 --> 00:18:37.150 align:start position:0% mitigation strategy that can be implemented<00:18:34.190> now<00:18:35.020> and<00:18:36.020> it<00:18:36.170> also<00:18:36.350> affects<00:18:36.590> - 00:18:37.150 --> 00:18:37.160 align:start position:0% implemented now and it also affects - 00:18:37.160 --> 00:18:44.800 align:start position:0% implemented now and it also affects - not<00:18:38.090> just<00:18:38.210> brought<00:18:38.450> about<00:18:38.630> the<00:18:38.810> key<00:18:38.930> -<00:18:39.170> to<00:18:43.810> pull 00:18:44.800 --> 00:18:44.810 align:start position:0% not just brought about the key - to pull 00:18:44.810 --> 00:18:49.480 align:start position:0% not just brought about the key - to pull anyone<00:18:45.110> else<00:18:47.560> yeah<00:18:48.560> sure 00:18:49.480 --> 00:18:49.490 align:start position:0% anyone else yeah sure 00:18:49.490 --> 00:18:57.810 align:start position:0% anyone else yeah sure I<00:18:49.520> mean<00:18:49.880> this<00:18:50.510> might<00:18:50.690> be<00:18:50.840> too<00:18:51.410> broad<00:18:51.620> but<00:18:52.900> like 00:18:57.810 --> 00:18:57.820 align:start position:0% 00:18:57.820 --> 00:19:18.120 align:start position:0% [Music] 00:19:18.120 --> 00:19:18.130 align:start position:0% 00:19:18.130 --> 00:19:22.810 align:start position:0% so<00:19:19.130> Rob<00:19:19.400> how<00:19:19.430> is<00:19:19.790> a<00:19:19.820> variation<00:19:20.150> of<00:19:20.390> you<00:19:20.510> -<00:19:21.820> it 00:19:22.810 --> 00:19:22.820 align:start position:0% so Rob how is a variation of you - it 00:19:22.820 --> 00:19:24.460 align:start position:0% so Rob how is a variation of you - it wasn't<00:19:23.030> it's<00:19:23.210> implemented<00:19:23.990> in<00:19:24.110> Java<00:19:24.320> it's 00:19:24.460 --> 00:19:24.470 align:start position:0% wasn't it's implemented in Java it's 00:19:24.470 --> 00:19:25.540 align:start position:0% wasn't it's implemented in Java it's been<00:19:24.590> a<00:19:24.620> few<00:19:24.770> months<00:19:24.920> of<00:19:25.100> some<00:19:25.220> of<00:19:25.280> this<00:19:25.340> may<00:19:25.490> be 00:19:25.540 --> 00:19:25.550 align:start position:0% been a few months of some of this may be 00:19:25.550 --> 00:19:29.730 align:start position:0% been a few months of some of this may be a<00:19:25.640> bit<00:19:25.820> rusty<00:19:26.060> remember<00:19:26.840> from<00:19:27.410> my<00:19:27.560> memory<00:19:28.090> but 00:19:29.730 --> 00:19:29.740 align:start position:0% a bit rusty remember from my memory but 00:19:29.740 --> 00:19:31.990 align:start position:0% a bit rusty remember from my memory but so<00:19:30.740> first<00:19:31.010> you<00:19:31.160> need<00:19:31.220> to<00:19:31.400> get<00:19:31.550> some<00:19:31.730> seed 00:19:31.990 --> 00:19:32.000 align:start position:0% so first you need to get some seed 00:19:32.000 --> 00:19:33.940 align:start position:0% so first you need to get some seed values<00:19:32.330> in<00:19:32.450> your<00:19:32.540> mixers<00:19:32.900> from<00:19:33.200> this<00:19:33.350> dag<00:19:33.650> and 00:19:33.940 --> 00:19:33.950 align:start position:0% values in your mixers from this dag and 00:19:33.950 --> 00:19:35.290 align:start position:0% values in your mixers from this dag and that's<00:19:34.160> where<00:19:34.310> the<00:19:34.400> main<00:19:34.610> memory<00:19:35.060> access 00:19:35.290 --> 00:19:35.300 align:start position:0% that's where the main memory access 00:19:35.300 --> 00:19:38.020 align:start position:0% that's where the main memory access comes<00:19:35.990> from<00:19:36.260> and<00:19:37.100> then<00:19:37.220> a<00:19:37.310> low<00:19:37.460> goes<00:19:37.640> up<00:19:37.850> and 00:19:38.020 --> 00:19:38.030 align:start position:0% comes from and then a low goes up and 00:19:38.030 --> 00:19:39.880 align:start position:0% comes from and then a low goes up and you<00:19:38.090> start<00:19:38.330> asking<00:19:38.450> 32<00:19:39.050> lanes<00:19:39.290> in<00:19:39.500> each<00:19:39.590> one<00:19:39.830> of 00:19:39.880 --> 00:19:39.890 align:start position:0% you start asking 32 lanes in each one of 00:19:39.890 --> 00:19:43.060 align:start position:0% you start asking 32 lanes in each one of those<00:19:40.040> lanes<00:19:40.340> there's<00:19:41.330> like<00:19:41.570> some<00:19:41.900> 16<00:19:42.410> or<00:19:42.650> 32 00:19:43.060 --> 00:19:43.070 align:start position:0% those lanes there's like some 16 or 32 00:19:43.070 --> 00:19:45.520 align:start position:0% those lanes there's like some 16 or 32 things<00:19:43.550> that<00:19:43.760> you<00:19:43.880> do<00:19:44.030> of<00:19:44.360> math<00:19:45.230> these 00:19:45.520 --> 00:19:45.530 align:start position:0% things that you do of math these 00:19:45.530 --> 00:19:46.840 align:start position:0% things that you do of math these parameters<00:19:45.980> change<00:19:46.190> all<00:19:46.340> the<00:19:46.460> time<00:19:46.610> so<00:19:46.790> I'm 00:19:46.840 --> 00:19:46.850 align:start position:0% parameters change all the time so I'm 00:19:46.850 --> 00:19:48.700 align:start position:0% parameters change all the time so I'm sure<00:19:47.000> anything<00:19:47.330> that<00:19:47.420> goes<00:19:47.510> wrong<00:19:47.600> but<00:19:48.590> with 00:19:48.700 --> 00:19:48.710 align:start position:0% sure anything that goes wrong but with 00:19:48.710 --> 00:19:51.040 align:start position:0% sure anything that goes wrong but with some<00:19:48.920> of<00:19:48.980> the<00:19:49.040> numbers<00:19:49.130> to<00:19:49.310> do<00:19:49.490> some<00:19:49.700> math<00:19:50.050> and 00:19:51.040 --> 00:19:51.050 align:start position:0% some of the numbers to do some math and 00:19:51.050 --> 00:19:53.530 align:start position:0% some of the numbers to do some math and to<00:19:51.410> do<00:19:51.560> that<00:19:51.740> math<00:19:51.950> you<00:19:52.250> also<00:19:52.580> take<00:19:52.850> in<00:19:53.330> each 00:19:53.530 --> 00:19:53.540 align:start position:0% to do that math you also take in each 00:19:53.540 --> 00:19:55.720 align:start position:0% to do that math you also take in each lane<00:19:53.840> stuff<00:19:54.230> from<00:19:54.650> various<00:19:55.070> parts<00:19:55.400> of<00:19:55.430> the<00:19:55.520> dag 00:19:55.720 --> 00:19:55.730 align:start position:0% lane stuff from various parts of the dag 00:19:55.730 --> 00:19:57.970 align:start position:0% lane stuff from various parts of the dag all<00:19:55.970> over<00:19:56.180> the<00:19:56.300> place<00:19:56.450> to<00:19:56.600> do<00:19:56.720> that<00:19:56.870> math<00:19:57.050> and 00:19:57.970 --> 00:19:57.980 align:start position:0% all over the place to do that math and 00:19:57.980 --> 00:19:59.590 align:start position:0% all over the place to do that math and you<00:19:58.100> do<00:19:58.250> this<00:19:58.400> some<00:19:58.640> number<00:19:58.880> of<00:19:58.970> times<00:19:59.240> you 00:19:59.590 --> 00:19:59.600 align:start position:0% you do this some number of times you 00:19:59.600 --> 00:20:00.770 align:start position:0% you do this some number of times you know<00:19:59.720> there's<00:20:00.110> more 00:20:00.770 --> 00:20:00.780 align:start position:0% know there's more 00:20:00.780 --> 00:20:03.160 align:start position:0% know there's more and<00:20:01.110> there<00:20:01.200> are<00:20:01.350> math<00:20:01.560> executions<00:20:02.340> right<00:20:02.670> now 00:20:03.160 --> 00:20:03.170 align:start position:0% and there are math executions right now 00:20:03.170 --> 00:20:07.250 align:start position:0% and there are math executions right now so<00:20:04.170> you<00:20:04.500> do<00:20:04.650> this<00:20:04.800> and<00:20:05.130> each<00:20:05.520> lane<00:20:05.970> is<00:20:06.630> entirely 00:20:07.250 --> 00:20:07.260 align:start position:0% so you do this and each lane is entirely 00:20:07.260 --> 00:20:08.540 align:start position:0% so you do this and each lane is entirely independent<00:20:07.560> there's<00:20:07.980> like<00:20:08.130> supposed<00:20:08.400> to<00:20:08.460> be 00:20:08.540 --> 00:20:08.550 align:start position:0% independent there's like supposed to be 00:20:08.550 --> 00:20:10.460 align:start position:0% independent there's like supposed to be 32<00:20:09.150> lanes<00:20:09.330> I<00:20:09.480> think<00:20:09.690> you're<00:20:09.810> 16 00:20:10.460 --> 00:20:10.470 align:start position:0% 32 lanes I think you're 16 00:20:10.470 --> 00:20:13.310 align:start position:0% 32 lanes I think you're 16 so<00:20:11.040> each<00:20:11.270> independent<00:20:12.270> ake<00:20:12.450> its<00:20:12.750> math<00:20:13.020> from 00:20:13.310 --> 00:20:13.320 align:start position:0% so each independent ake its math from 00:20:13.320 --> 00:20:15.320 align:start position:0% so each independent ake its math from its<00:20:13.500> mix<00:20:13.770> take<00:20:14.040> take<00:20:14.760> some<00:20:14.970> stuff<00:20:15.150> from<00:20:15.210> the 00:20:15.320 --> 00:20:15.330 align:start position:0% its mix take take some stuff from the 00:20:15.330 --> 00:20:17.840 align:start position:0% its mix take take some stuff from the deck<00:20:15.540> do<00:20:16.350> some<00:20:16.620> math<00:20:16.770> together<00:20:17.190> and<00:20:17.490> then<00:20:17.610> send 00:20:17.840 --> 00:20:17.850 align:start position:0% deck do some math together and then send 00:20:17.850 --> 00:20:19.490 align:start position:0% deck do some math together and then send it<00:20:17.910> to<00:20:17.970> another<00:20:18.270> lane<00:20:18.510> and<00:20:19.170> you<00:20:19.260> knew<00:20:19.380> this 00:20:19.490 --> 00:20:19.500 align:start position:0% it to another lane and you knew this 00:20:19.500 --> 00:20:22.040 align:start position:0% it to another lane and you knew this about<00:20:19.710> 30<00:20:20.070> or<00:20:20.310> 40<00:20:20.610> times<00:20:20.640> you<00:20:21.180> get<00:20:21.300> that<00:20:21.510> mixed 00:20:22.040 --> 00:20:22.050 align:start position:0% about 30 or 40 times you get that mixed 00:20:22.050 --> 00:20:23.540 align:start position:0% about 30 or 40 times you get that mixed date<00:20:22.260> together<00:20:22.470> so<00:20:22.830> it's<00:20:22.980> designed<00:20:23.100> so<00:20:23.520> that 00:20:23.540 --> 00:20:23.550 align:start position:0% date together so it's designed so that 00:20:23.550 --> 00:20:26.050 align:start position:0% date together so it's designed so that the<00:20:24.330> computation<00:20:25.020> is<00:20:25.320> very<00:20:25.620> recognizable 00:20:26.050 --> 00:20:26.060 align:start position:0% the computation is very recognizable 00:20:26.060 --> 00:20:28.070 align:start position:0% the computation is very recognizable especially<00:20:27.060> in<00:20:27.120> context<00:20:27.540> of<00:20:27.660> a<00:20:27.750> GPU 00:20:28.070 --> 00:20:28.080 align:start position:0% especially in context of a GPU 00:20:28.080 --> 00:20:30.170 align:start position:0% especially in context of a GPU architecture<00:20:28.650> and<00:20:29.340> it<00:20:29.460> saturates<00:20:29.940> the<00:20:30.060> whole 00:20:30.170 --> 00:20:30.180 align:start position:0% architecture and it saturates the whole 00:20:30.180 --> 00:20:33.230 align:start position:0% architecture and it saturates the whole GPU<00:20:30.630> by<00:20:30.840> using<00:20:31.260> all<00:20:31.740> of<00:20:31.800> the<00:20:32.280> functions<00:20:32.820> of<00:20:32.910> GPU 00:20:33.230 --> 00:20:33.240 align:start position:0% GPU by using all of the functions of GPU 00:20:33.240 --> 00:20:35.420 align:start position:0% GPU by using all of the functions of GPU might<00:20:33.420> have<00:20:33.980> except<00:20:34.980> for<00:20:35.100> floating<00:20:35.400> point 00:20:35.420 --> 00:20:35.430 align:start position:0% might have except for floating point 00:20:35.430 --> 00:20:38.020 align:start position:0% might have except for floating point because<00:20:36.090> floating<00:20:36.630> point<00:20:36.900> is<00:20:36.990> kind<00:20:37.260> of 00:20:38.020 --> 00:20:38.030 align:start position:0% because floating point is kind of 00:20:38.030 --> 00:20:40.580 align:start position:0% because floating point is kind of emerging<00:20:39.030> across<00:20:39.360> all<00:20:39.660> the<00:20:39.780> vendors<00:20:40.050> integers 00:20:40.580 --> 00:20:40.590 align:start position:0% emerging across all the vendors integers 00:20:40.590 --> 00:20:43.040 align:start position:0% emerging across all the vendors integers is<00:20:41.040> you<00:20:41.940> know<00:20:42.060> if<00:20:42.210> you<00:20:42.300> can't<00:20:42.510> an<00:20:42.630> integer<00:20:42.810> math 00:20:43.040 --> 00:20:43.050 align:start position:0% is you know if you can't an integer math 00:20:43.050 --> 00:20:44.420 align:start position:0% is you know if you can't an integer math you<00:20:43.290> should<00:20:43.470> get<00:20:43.560> out<00:20:43.590> of<00:20:43.770> computer<00:20:44.070> science 00:20:44.420 --> 00:20:44.430 align:start position:0% you should get out of computer science 00:20:44.430 --> 00:20:45.920 align:start position:0% you should get out of computer science it's<00:20:45.060> pretty<00:20:45.330> simple 00:20:45.920 --> 00:20:45.930 align:start position:0% it's pretty simple 00:20:45.930 --> 00:20:47.480 align:start position:0% it's pretty simple pulling<00:20:46.590> points<00:20:46.830> is<00:20:46.890> where<00:20:47.010> things<00:20:47.160> get<00:20:47.340> weird 00:20:47.480 --> 00:20:47.490 align:start position:0% pulling points is where things get weird 00:20:47.490 --> 00:20:49.220 align:start position:0% pulling points is where things get weird so<00:20:48.180> they<00:20:48.300> love<00:20:48.480> that<00:20:48.630> out<00:20:48.840> of<00:20:48.930> the<00:20:48.990> spec 00:20:49.220 --> 00:20:49.230 align:start position:0% so they love that out of the spec 00:20:49.230 --> 00:20:52.640 align:start position:0% so they love that out of the spec because<00:20:49.500> it's<00:20:49.620> not<00:20:49.880> certain<00:20:50.880> enough<00:20:51.560> so<00:20:52.560> you 00:20:52.640 --> 00:20:52.650 align:start position:0% because it's not certain enough so you 00:20:52.650 --> 00:20:53.810 align:start position:0% because it's not certain enough so you take<00:20:52.830> all<00:20:52.980> that<00:20:53.130> stuff<00:20:53.190> you<00:20:53.520> catch<00:20:53.670> it 00:20:53.810 --> 00:20:53.820 align:start position:0% take all that stuff you catch it 00:20:53.820 --> 00:20:55.160 align:start position:0% take all that stuff you catch it together<00:20:54.060> at<00:20:54.270> the<00:20:54.300> end<00:20:54.510> and<00:20:54.660> take<00:20:54.840> that<00:20:54.960> final 00:20:55.160 --> 00:20:55.170 align:start position:0% together at the end and take that final 00:20:55.170 --> 00:20:57.380 align:start position:0% together at the end and take that final hash<00:20:55.440> take<00:20:55.710> your<00:20:56.370> on<00:20:56.430> a<00:20:56.460> file<00:20:56.730> to<00:20:56.880> check<00:20:56.940> hash 00:20:57.380 --> 00:20:57.390 align:start position:0% hash take your on a file to check hash 00:20:57.390 --> 00:20:59.810 align:start position:0% hash take your on a file to check hash against<00:20:57.900> it<00:20:58.020> and<00:20:58.200> then<00:20:59.070> that's<00:20:59.340> what<00:20:59.580> you 00:20:59.810 --> 00:20:59.820 align:start position:0% against it and then that's what you 00:20:59.820 --> 00:21:01.610 align:start position:0% against it and then that's what you that's<00:21:00.450> the<00:21:00.570> results<00:21:00.900> of<00:21:01.020> your<00:21:01.140> of<00:21:01.350> the<00:21:01.470> hash 00:21:01.610 --> 00:21:01.620 align:start position:0% that's the results of your of the hash 00:21:01.620 --> 00:21:02.900 align:start position:0% that's the results of your of the hash that<00:21:01.740> you<00:21:01.860> get<00:21:02.040> and<00:21:02.190> then<00:21:02.280> you<00:21:02.370> do<00:21:02.460> the<00:21:02.580> regular 00:21:02.900 --> 00:21:02.910 align:start position:0% that you get and then you do the regular 00:21:02.910 --> 00:21:04.850 align:start position:0% that you get and then you do the regular old<00:21:03.090> mining<00:21:03.960> stuff<00:21:04.200> where<00:21:04.410> you<00:21:04.500> check<00:21:04.710> it 00:21:04.850 --> 00:21:04.860 align:start position:0% old mining stuff where you check it 00:21:04.860 --> 00:21:06.200 align:start position:0% old mining stuff where you check it against<00:21:05.040> the<00:21:05.160> difficulty<00:21:05.760> see<00:21:05.970> if<00:21:06.030> it's 00:21:06.200 --> 00:21:06.210 align:start position:0% against the difficulty see if it's 00:21:06.210 --> 00:21:08.180 align:start position:0% against the difficulty see if it's successful<00:21:06.360> enough<00:21:06.840> if<00:21:06.990> not<00:21:07.200> it<00:21:07.680> hits<00:21:07.920> it<00:21:08.040> back 00:21:08.180 --> 00:21:08.190 align:start position:0% successful enough if not it hits it back 00:21:08.190 --> 00:21:10.340 align:start position:0% successful enough if not it hits it back and<00:21:08.520> if<00:21:08.610> you're<00:21:08.760> a<00:21:08.790> miner<00:21:09.090> out<00:21:09.360> there<00:21:09.630> you<00:21:10.230> have 00:21:10.340 --> 00:21:10.350 align:start position:0% and if you're a miner out there you have 00:21:10.350 --> 00:21:12.710 align:start position:0% and if you're a miner out there you have a<00:21:10.520> less<00:21:11.520> difficult<00:21:12.090> than<00:21:12.120> the<00:21:12.300> cult's<00:21:12.540> you<00:21:12.600> do 00:21:12.710 --> 00:21:12.720 align:start position:0% a less difficult than the cult's you do 00:21:12.720 --> 00:21:14.930 align:start position:0% a less difficult than the cult's you do to<00:21:12.840> prove<00:21:13.020> that<00:21:13.110> you<00:21:13.260> tried<00:21:13.530> and<00:21:13.710> failed<00:21:13.940> so 00:21:14.930 --> 00:21:14.940 align:start position:0% to prove that you tried and failed so 00:21:14.940 --> 00:21:16.520 align:start position:0% to prove that you tried and failed so there's<00:21:15.210> you<00:21:15.390> know<00:21:15.450> the<00:21:15.600> regular<00:21:16.050> old<00:21:16.200> mining 00:21:16.520 --> 00:21:16.530 align:start position:0% there's you know the regular old mining 00:21:16.530 --> 00:21:17.570 align:start position:0% there's you know the regular old mining techniques<00:21:16.920> that<00:21:17.070> go<00:21:17.130> on<00:21:17.280> from<00:21:17.400> that<00:21:17.520> but 00:21:17.570 --> 00:21:17.580 align:start position:0% techniques that go on from that but 00:21:17.580 --> 00:21:20.870 align:start position:0% techniques that go on from that but that's<00:21:17.910> a<00:21:18.210> high-level<00:21:18.930> overview<00:21:19.350> of<00:21:20.130> kind<00:21:20.760> of 00:21:20.870 --> 00:21:20.880 align:start position:0% that's a high-level overview of kind of 00:21:20.880 --> 00:21:24.140 align:start position:0% that's a high-level overview of kind of what<00:21:21.000> happens<00:21:21.420> I<00:21:21.720> have<00:21:21.990> code 00:21:24.140 --> 00:21:24.150 align:start position:0% what happens I have code 00:21:24.150 --> 00:21:27.990 align:start position:0% what happens I have code so<00:21:25.150> that's<00:21:25.330> also<00:21:25.630> how<00:21:25.900> its<00:21:26.410> implemented<00:21:26.770> in<00:21:27.070> go 00:21:27.990 --> 00:21:28.000 align:start position:0% so that's also how its implemented in go 00:21:28.000 --> 00:21:30.120 align:start position:0% so that's also how its implemented in go theremin<00:21:28.450> parity<00:21:28.870> when<00:21:29.470> you<00:21:29.590> implement<00:21:29.830> this 00:21:30.120 --> 00:21:30.130 align:start position:0% theremin parity when you implement this 00:21:30.130 --> 00:21:32.250 align:start position:0% theremin parity when you implement this for<00:21:30.310> a<00:21:30.370> chip<00:21:30.550> you<00:21:30.900> there's<00:21:31.900> also<00:21:32.080> this 00:21:32.250 --> 00:21:32.260 align:start position:0% for a chip you there's also this 00:21:32.260 --> 00:21:34.650 align:start position:0% for a chip you there's also this internal<00:21:32.680> period<00:21:33.100> on<00:21:33.280> the<00:21:33.730> books<00:21:34.150> I<00:21:34.300> think<00:21:34.330> you 00:21:34.650 --> 00:21:34.660 align:start position:0% internal period on the books I think you 00:21:34.660 --> 00:21:37.980 align:start position:0% internal period on the books I think you need<00:21:34.810> a<00:21:35.650> way<00:21:36.130> to<00:21:36.160> get<00:21:36.340> you<00:21:36.820> know<00:21:36.880> and<00:21:37.120> then<00:21:37.240> okay 00:21:37.980 --> 00:21:37.990 align:start position:0% need a way to get you know and then okay 00:21:37.990 --> 00:21:43.680 align:start position:0% need a way to get you know and then okay okay<00:21:38.740> for<00:21:39.400> later<00:21:39.640> for<00:21:39.760> the<00:21:41.040> for<00:21:42.040> the<00:21:42.160> next<00:21:42.760> spec 00:21:43.680 --> 00:21:43.690 align:start position:0% okay for later for the for the next spec 00:21:43.690 --> 00:21:47.460 align:start position:0% okay for later for the for the next spec of<00:21:44.110> work<00:21:44.440> pot<00:21:45.570> and<00:21:46.570> yet<00:21:46.780> one<00:21:46.930> of<00:21:47.020> the<00:21:47.110> reasons 00:21:47.460 --> 00:21:47.470 align:start position:0% of work pot and yet one of the reasons 00:21:47.470 --> 00:21:49.530 align:start position:0% of work pot and yet one of the reasons there<00:21:47.650> the<00:21:47.830> gift<00:21:48.070> program<00:21:48.550> hasn't<00:21:48.910> emerges 00:21:49.530 --> 00:21:49.540 align:start position:0% there the gift program hasn't emerges 00:21:49.540 --> 00:21:50.700 align:start position:0% there the gift program hasn't emerges that<00:21:49.660> we're<00:21:49.810> not<00:21:49.900> sure<00:21:49.960> if<00:21:50.200> we<00:21:50.320> should<00:21:50.350> march 00:21:50.700 --> 00:21:50.710 align:start position:0% that we're not sure if we should march 00:21:50.710 --> 00:21:55.320 align:start position:0% that we're not sure if we should march the<00:21:51.040> oh<00:21:51.310> nine<00:21:51.940> one<00:21:52.300> or<00:21:52.540> mine<00:21:52.990> next<00:21:53.890> anyway<00:21:54.550> so 00:21:55.320 --> 00:21:55.330 align:start position:0% the oh nine one or mine next anyway so 00:21:55.330 --> 00:21:57.480 align:start position:0% the oh nine one or mine next anyway so the<00:21:55.510> thing<00:21:55.630> is<00:21:55.660> on<00:21:56.110> if<00:21:56.350> you<00:21:56.410> run<00:21:56.590> from<00:21:56.710> GPU<00:21:57.190> what 00:21:57.480 --> 00:21:57.490 align:start position:0% the thing is on if you run from GPU what 00:21:57.490 --> 00:21:59.220 align:start position:0% the thing is on if you run from GPU what to<00:21:57.610> do<00:21:57.730> is<00:21:57.850> that<00:21:58.000> every<00:21:58.090> 50<00:21:58.630> blocks<00:21:58.840> you 00:21:59.220 --> 00:21:59.230 align:start position:0% to do is that every 50 blocks you 00:21:59.230 --> 00:22:02.520 align:start position:0% to do is that every 50 blocks you recompile<00:22:00.010> the<00:22:00.670> GPU<00:22:01.330> program<00:22:02.140> and<00:22:02.440> you 00:22:02.520 --> 00:22:02.530 align:start position:0% recompile the GPU program and you 00:22:02.530 --> 00:22:07.190 align:start position:0% recompile the GPU program and you reprogram<00:22:03.310> the<00:22:03.790> GPU<00:22:04.390> for<00:22:05.290> the<00:22:05.470> next<00:22:05.800> 50<00:22:06.490> blocks 00:22:07.190 --> 00:22:07.200 align:start position:0% reprogram the GPU for the next 50 blocks 00:22:07.200 --> 00:22:10.830 align:start position:0% reprogram the GPU for the next 50 blocks and<00:22:08.200> that's<00:22:08.580> the<00:22:09.580> kind<00:22:09.880> of<00:22:09.940> programmatic<00:22:10.240> part 00:22:10.830 --> 00:22:10.840 align:start position:0% and that's the kind of programmatic part 00:22:10.840 --> 00:22:14.100 align:start position:0% and that's the kind of programmatic part and<00:22:11.230> this<00:22:11.830> sheet<00:22:12.220> that<00:22:12.250> you<00:22:12.880> use<00:22:13.090> can<00:22:13.300> do<00:22:13.450> but 00:22:14.100 --> 00:22:14.110 align:start position:0% and this sheet that you use can do but 00:22:14.110 --> 00:22:16.110 align:start position:0% and this sheet that you use can do but which<00:22:14.410> makes<00:22:14.620> it<00:22:14.770> harder<00:22:15.280> to<00:22:15.310> implement<00:22:15.970> this 00:22:16.110 --> 00:22:16.120 align:start position:0% which makes it harder to implement this 00:22:16.120 --> 00:22:19.440 align:start position:0% which makes it harder to implement this as<00:22:16.390> a<00:22:16.420> that's<00:22:17.260> a<00:22:17.580> specific<00:22:18.580> server<00:22:18.940> circuit 00:22:19.440 --> 00:22:19.450 align:start position:0% as a that's a specific server circuit 00:22:19.450 --> 00:22:29.400 align:start position:0% as a that's a specific server circuit amazing<00:22:27.780> totally<00:22:28.780> I<00:22:28.810> mean<00:22:28.840> please<00:22:29.200> get<00:22:29.350> the 00:22:29.400 --> 00:22:29.410 align:start position:0% amazing totally I mean please get the 00:22:29.410 --> 00:22:33.030 align:start position:0% amazing totally I mean please get the program<00:22:29.920> apart<00:22:30.250> so<00:22:30.580> many<00:22:30.700> many<00:22:30.910> reasons<00:22:32.040> but 00:22:33.030 --> 00:22:33.040 align:start position:0% program apart so many many reasons but 00:22:33.040 --> 00:22:34.440 align:start position:0% program apart so many many reasons but one<00:22:33.310> of<00:22:33.490> the<00:22:33.610> interesting<00:22:33.670> things<00:22:34.150> that<00:22:34.330> one 00:22:34.440 --> 00:22:34.450 align:start position:0% one of the interesting things that one 00:22:34.450 --> 00:22:35.820 align:start position:0% one of the interesting things that one of<00:22:34.540> the<00:22:34.630> implementations<00:22:35.200> found<00:22:35.470> is<00:22:35.740> the 00:22:35.820 --> 00:22:35.830 align:start position:0% of the implementations found is the 00:22:35.830 --> 00:22:37.890 align:start position:0% of the implementations found is the actually<00:22:36.100> found<00:22:36.280> a<00:22:36.400> bug<00:22:36.610> in<00:22:36.820> a<00:22:36.910> GPU<00:22:37.270> compiler 00:22:37.890 --> 00:22:37.900 align:start position:0% actually found a bug in a GPU compiler 00:22:37.900 --> 00:22:39.540 align:start position:0% actually found a bug in a GPU compiler when<00:22:38.350> they<00:22:38.440> were<00:22:38.500> running<00:22:38.710> the<00:22:38.860> program<00:22:39.280> and 00:22:39.540 --> 00:22:39.550 align:start position:0% when they were running the program and 00:22:39.550 --> 00:22:42.180 align:start position:0% when they were running the program and had<00:22:40.090> a<00:22:40.120> very<00:22:40.270> simple<00:22:40.630> fix<00:22:40.870> by<00:22:41.680> the<00:22:41.740> thing<00:22:41.980> about 00:22:42.180 --> 00:22:42.190 align:start position:0% had a very simple fix by the thing about 00:22:42.190 --> 00:22:45.720 align:start position:0% had a very simple fix by the thing about these<00:22:42.340> programs<00:22:42.820> as<00:22:43.120> they<00:22:43.270> are<00:22:43.620> the<00:22:44.620> it's<00:22:45.520> not 00:22:45.720 --> 00:22:45.730 align:start position:0% these programs as they are the it's not 00:22:45.730 --> 00:22:47.460 align:start position:0% these programs as they are the it's not really<00:22:46.000> random<00:22:46.240> and<00:22:46.450> pseudo-random<00:22:46.930> and<00:22:47.350> the 00:22:47.460 --> 00:22:47.470 align:start position:0% really random and pseudo-random and the 00:22:47.470 --> 00:22:50.010 align:start position:0% really random and pseudo-random and the seed<00:22:47.740> is<00:22:47.770> the<00:22:48.040> block<00:22:48.550> number<00:22:48.940> of<00:22:49.120> the<00:22:49.630> period 00:22:50.010 --> 00:22:50.020 align:start position:0% seed is the block number of the period 00:22:50.020 --> 00:22:51.330 align:start position:0% seed is the block number of the period that's<00:22:50.140> going<00:22:50.440> on<00:22:50.560> with<00:22:50.740> it<00:22:50.860> so<00:22:51.010> you<00:22:51.070> can 00:22:51.330 --> 00:22:51.340 align:start position:0% that's going on with it so you can 00:22:51.340 --> 00:22:53.940 align:start position:0% that's going on with it so you can totally<00:22:51.760> run<00:22:52.570> all<00:22:52.750> your<00:22:52.840> combinations<00:22:53.530> up<00:22:53.710> to 00:22:53.940 --> 00:22:53.950 align:start position:0% totally run all your combinations up to 00:22:53.950 --> 00:22:56.760 align:start position:0% totally run all your combinations up to you<00:22:54.520> know<00:22:54.670> 10<00:22:55.090> million<00:22:55.420> 20<00:22:55.510> million<00:22:55.870> blocks<00:22:56.170> to 00:22:56.760 --> 00:22:56.770 align:start position:0% you know 10 million 20 million blocks to 00:22:56.770 --> 00:22:59.010 align:start position:0% you know 10 million 20 million blocks to make<00:22:56.800> sure<00:22:57.010> that<00:22:57.160> your<00:22:57.310> CPU<00:22:57.670> can<00:22:57.850> handle<00:22:58.120> it<00:22:58.270> so 00:22:59.010 --> 00:22:59.020 align:start position:0% make sure that your CPU can handle it so 00:22:59.020 --> 00:22:59.910 align:start position:0% make sure that your CPU can handle it so you<00:22:59.080> know<00:22:59.290> there's<00:22:59.470> some<00:22:59.530> can<00:22:59.740> there<00:22:59.860> were 00:22:59.910 --> 00:22:59.920 align:start position:0% you know there's some can there were 00:22:59.920 --> 00:23:01.800 align:start position:0% you know there's some can there were some<00:23:00.070> concerned<00:23:00.340> initially<00:23:00.550> that<00:23:01.330> this<00:23:01.540> might 00:23:01.800 --> 00:23:01.810 align:start position:0% some concerned initially that this might 00:23:01.810 --> 00:23:04.680 align:start position:0% some concerned initially that this might break<00:23:02.190> you<00:23:03.190> know<00:23:03.310> the<00:23:03.610> CPU<00:23:04.060> things<00:23:04.330> are<00:23:04.450> at<00:23:04.540> our 00:23:04.680 --> 00:23:04.690 align:start position:0% break you know the CPU things are at our 00:23:04.690 --> 00:23:07.650 align:start position:0% break you know the CPU things are at our risk<00:23:04.990> and<00:23:05.200> any<00:23:05.980> responsible<00:23:06.730> minor<00:23:06.970> what<00:23:07.360> you 00:23:07.650 --> 00:23:07.660 align:start position:0% risk and any responsible minor what you 00:23:07.660 --> 00:23:09.480 align:start position:0% risk and any responsible minor what you know<00:23:07.750> be<00:23:07.990> running<00:23:08.260> these<00:23:08.320> programs<00:23:08.380> out<00:23:08.920> and 00:23:09.480 --> 00:23:09.490 align:start position:0% know be running these programs out and 00:23:09.490 --> 00:23:10.800 align:start position:0% know be running these programs out and they<00:23:09.640> are<00:23:09.700> tuned<00:23:09.940> advanced<00:23:10.240> to<00:23:10.390> see<00:23:10.540> it<00:23:10.630> stuff 00:23:10.800 --> 00:23:10.810 align:start position:0% they are tuned advanced to see it stuff 00:23:10.810 --> 00:23:12.070 align:start position:0% they are tuned advanced to see it stuff blows<00:23:11.020> up<00:23:11.200> or<00:23:11.470> you<00:23:11.620> know 00:23:12.070 --> 00:23:12.080 align:start position:0% blows up or you know 00:23:12.080 --> 00:23:13.960 align:start position:0% blows up or you know they<00:23:12.440> just<00:23:13.039> have<00:23:13.190> you<00:23:13.309> just<00:23:13.370> need<00:23:13.580> to<00:23:13.669> have<00:23:13.789> one 00:23:13.960 --> 00:23:13.970 align:start position:0% they just have you just need to have one 00:23:13.970 --> 00:23:15.820 align:start position:0% they just have you just need to have one rig<00:23:14.240> to<00:23:14.840> test<00:23:15.049> to<00:23:15.140> make<00:23:15.169> sure<00:23:15.289> that<00:23:15.409> your<00:23:15.679> stuff 00:23:15.820 --> 00:23:15.830 align:start position:0% rig to test to make sure that your stuff 00:23:15.830 --> 00:23:21.370 align:start position:0% rig to test to make sure that your stuff works<00:23:18.549> awesome<00:23:19.549> answers<00:23:20.110> alright<00:23:21.110> any<00:23:21.320> other 00:23:21.370 --> 00:23:21.380 align:start position:0% works awesome answers alright any other 00:23:21.380 --> 00:23:24.660 align:start position:0% works awesome answers alright any other questions 00:23:24.660 --> 00:23:24.670 align:start position:0% 00:23:24.670 --> 00:23:28.150 align:start position:0% [Music] 00:23:28.150 --> 00:23:28.160 align:start position:0% [Music] 00:23:28.160 --> 00:23:31.090 align:start position:0% [Music] I<00:23:28.190> just<00:23:29.180> wonder<00:23:29.480> are<00:23:29.750> all<00:23:30.290> the<00:23:30.470> is<00:23:30.800> all<00:23:30.980> the 00:23:31.090 --> 00:23:31.100 align:start position:0% I just wonder are all the is all the 00:23:31.100 --> 00:23:34.000 align:start position:0% I just wonder are all the is all the controversy<00:23:32.320> non-technical<00:23:33.320> are<00:23:33.710> there<00:23:33.860> any 00:23:34.000 --> 00:23:34.010 align:start position:0% controversy non-technical are there any 00:23:34.010 --> 00:23:38.680 align:start position:0% controversy non-technical are there any technical<00:23:34.460> controversies<00:23:35.390> and<00:23:35.810> then<00:23:36.530> I<00:23:37.690> was 00:23:38.680 --> 00:23:38.690 align:start position:0% technical controversies and then I was 00:23:38.690 --> 00:23:40.180 align:start position:0% technical controversies and then I was curious<00:23:38.990> about<00:23:39.170> your<00:23:39.350> description<00:23:40.010> of<00:23:40.100> the 00:23:40.180 --> 00:23:40.190 align:start position:0% curious about your description of the 00:23:40.190 --> 00:23:43.720 align:start position:0% curious about your description of the tests<00:23:40.610> that<00:23:40.730> it<00:23:41.060> seemed<00:23:41.360> to<00:23:42.170> me<00:23:42.920> you<00:23:43.130> would<00:23:43.310> you 00:23:43.720 --> 00:23:43.730 align:start position:0% tests that it seemed to me you would you 00:23:43.730 --> 00:23:45.730 align:start position:0% tests that it seemed to me you would you want<00:23:43.910> to<00:23:44.060> have<00:23:44.150> a<00:23:44.210> very<00:23:44.480> rigorous<00:23:44.840> test<00:23:45.410> matter 00:23:45.730 --> 00:23:45.740 align:start position:0% want to have a very rigorous test matter 00:23:45.740 --> 00:23:51.790 align:start position:0% want to have a very rigorous test matter in<00:23:46.190> such<00:23:47.180> a<00:23:47.210> realistic<00:23:50.230> to<00:23:51.230> understand<00:23:51.620> first 00:23:51.790 --> 00:23:51.800 align:start position:0% in such a realistic to understand first 00:23:51.800 --> 00:23:54.930 align:start position:0% in such a realistic to understand first it's<00:23:52.250> our<00:23:52.400> second<00:23:52.760> question<00:23:52.910> first 00:23:54.930 --> 00:23:54.940 align:start position:0% it's our second question first 00:23:54.940 --> 00:23:58.420 align:start position:0% it's our second question first so<00:23:55.940> in<00:23:56.810> general<00:23:57.260> we'll<00:23:57.680> need<00:23:57.800> to<00:23:57.950> set<00:23:58.160> up<00:23:58.220> the 00:23:58.420 --> 00:23:58.430 align:start position:0% so in general we'll need to set up the 00:23:58.430 --> 00:24:01.060 align:start position:0% so in general we'll need to set up the test<00:23:58.640> and<00:23:58.940> tried<00:23:59.510> a<00:23:59.540> new<00:23:59.810> hard<00:24:00.050> work<00:24:00.410> what<00:24:00.890> we 00:24:01.060 --> 00:24:01.070 align:start position:0% test and tried a new hard work what we 00:24:01.070 --> 00:24:03.580 align:start position:0% test and tried a new hard work what we want<00:24:01.280> is<00:24:01.610> a<00:24:01.820> very<00:24:02.120> lively<00:24:02.390> test<00:24:02.870> then<00:24:03.140> so<00:24:03.380> that 00:24:03.580 --> 00:24:03.590 align:start position:0% want is a very lively test then so that 00:24:03.590 --> 00:24:05.980 align:start position:0% want is a very lively test then so that we<00:24:03.740> can<00:24:03.950> like<00:24:04.730> for<00:24:04.940> example<00:24:05.000> for<00:24:05.270> crops<00:24:05.750> done 00:24:05.980 --> 00:24:05.990 align:start position:0% we can like for example for crops done 00:24:05.990 --> 00:24:08.110 align:start position:0% we can like for example for crops done and<00:24:06.140> then<00:24:06.260> we<00:24:06.350> can<00:24:06.380> execute<00:24:07.190> transaction<00:24:07.970> and 00:24:08.110 --> 00:24:08.120 align:start position:0% and then we can execute transaction and 00:24:08.120 --> 00:24:10.150 align:start position:0% and then we can execute transaction and see<00:24:08.270> that<00:24:08.510> the<00:24:09.140> execution<00:24:09.830> of<00:24:09.860> transaction 00:24:10.150 --> 00:24:10.160 align:start position:0% see that the execution of transaction 00:24:10.160 --> 00:24:13.570 align:start position:0% see that the execution of transaction still<00:24:10.700> happens<00:24:11.090> the<00:24:11.870> way<00:24:12.020> they<00:24:12.170> would<00:24:12.460> the<00:24:13.460> way 00:24:13.570 --> 00:24:13.580 align:start position:0% still happens the way they would the way 00:24:13.580 --> 00:24:14.830 align:start position:0% still happens the way they would the way they<00:24:13.700> showed<00:24:13.940> them<00:24:14.120> that<00:24:14.240> the<00:24:14.360> variable 00:24:14.830 --> 00:24:14.840 align:start position:0% they showed them that the variable 00:24:14.840 --> 00:24:18.100 align:start position:0% they showed them that the variable sensors<00:24:15.310> for<00:24:16.310> profile<00:24:16.910> that's<00:24:17.360> hopefully<00:24:17.900> not 00:24:18.100 --> 00:24:18.110 align:start position:0% sensors for profile that's hopefully not 00:24:18.110 --> 00:24:20.650 align:start position:0% sensors for profile that's hopefully not needed<00:24:18.860> at<00:24:19.100> all<00:24:19.250> the<00:24:19.850> only<00:24:20.120> thing<00:24:20.330> that<00:24:20.540> we 00:24:20.650 --> 00:24:20.660 align:start position:0% needed at all the only thing that we 00:24:20.660 --> 00:24:23.320 align:start position:0% needed at all the only thing that we wanted<00:24:20.870> to<00:24:21.020> verify<00:24:21.230> is<00:24:21.590> the<00:24:22.070> envelope<00:24:22.310> of<00:24:23.000> the 00:24:23.320 --> 00:24:23.330 align:start position:0% wanted to verify is the envelope of the 00:24:23.330 --> 00:24:25.600 align:start position:0% wanted to verify is the envelope of the blocks<00:24:23.570> the<00:24:24.110> proof<00:24:24.980> of<00:24:25.100> work<00:24:25.250> and<00:24:25.550> the 00:24:25.600 --> 00:24:25.610 align:start position:0% blocks the proof of work and the 00:24:25.610 --> 00:24:28.930 align:start position:0% blocks the proof of work and the verification<00:24:25.850> and<00:24:26.330> the<00:24:26.470> mining<00:24:27.470> of<00:24:27.800> this<00:24:28.460> work 00:24:28.930 --> 00:24:28.940 align:start position:0% verification and the mining of this work 00:24:28.940 --> 00:24:31.540 align:start position:0% verification and the mining of this work so<00:24:29.660> we<00:24:29.810> totally<00:24:30.110> don't<00:24:30.590> care<00:24:30.680> anything<00:24:31.190> at<00:24:31.460> all 00:24:31.540 --> 00:24:31.550 align:start position:0% so we totally don't care anything at all 00:24:31.550 --> 00:24:33.880 align:start position:0% so we totally don't care anything at all about<00:24:31.790> the<00:24:31.940> content<00:24:32.570> of<00:24:32.750> the<00:24:32.840> gloves<00:24:33.080> so<00:24:33.380> as 00:24:33.880 --> 00:24:33.890 align:start position:0% about the content of the gloves so as 00:24:33.890 --> 00:24:36.400 align:start position:0% about the content of the gloves so as long<00:24:34.040> as<00:24:34.100> it's<00:24:34.610> what<00:24:34.790> we<00:24:34.910> wanted<00:24:35.240> to<00:24:35.480> do<00:24:35.630> was<00:24:36.230> to 00:24:36.400 --> 00:24:36.410 align:start position:0% long as it's what we wanted to do was to 00:24:36.410 --> 00:24:39.310 align:start position:0% long as it's what we wanted to do was to get<00:24:36.560> maximum<00:24:37.010> coverage<00:24:37.190> of<00:24:38.320> transitions 00:24:39.310 --> 00:24:39.320 align:start position:0% get maximum coverage of transitions 00:24:39.320 --> 00:24:41.560 align:start position:0% get maximum coverage of transitions because<00:24:39.560> we<00:24:40.160> realized<00:24:41.000> that<00:24:41.120> they<00:24:41.360> are<00:24:41.420> one 00:24:41.560 --> 00:24:41.570 align:start position:0% because we realized that they are one 00:24:41.570 --> 00:24:44.200 align:start position:0% because we realized that they are one one<00:24:41.870> of<00:24:42.020> the<00:24:42.400> interesting<00:24:43.400> points<00:24:44.000> where 00:24:44.200 --> 00:24:44.210 align:start position:0% one of the interesting points where 00:24:44.210 --> 00:24:45.700 align:start position:0% one of the interesting points where things<00:24:44.450> could<00:24:44.720> break<00:24:44.990> is<00:24:45.230> an<00:24:45.380> epoch 00:24:45.700 --> 00:24:45.710 align:start position:0% things could break is an epoch 00:24:45.710 --> 00:24:48.030 align:start position:0% things could break is an epoch transitions<00:24:46.370> because<00:24:46.610> that's<00:24:47.000> when<00:24:47.180> attack 00:24:48.030 --> 00:24:48.040 align:start position:0% transitions because that's when attack 00:24:48.040 --> 00:24:51.880 align:start position:0% transitions because that's when attack changes<00:24:49.040> and<00:24:49.420> if<00:24:50.420> I<00:24:50.750> recall<00:24:50.930> correctly<00:24:51.410> there 00:24:51.880 --> 00:24:51.890 align:start position:0% changes and if I recall correctly there 00:24:51.890 --> 00:24:57.580 align:start position:0% changes and if I recall correctly there was<00:24:52.130> there<00:24:52.670> is<00:24:52.820> some<00:24:53.180> minor<00:24:53.990> tweak<00:24:54.560> to<00:24:56.590> improve 00:24:57.580 --> 00:24:57.590 align:start position:0% was there is some minor tweak to improve 00:24:57.590 --> 00:25:01.150 align:start position:0% was there is some minor tweak to improve power<00:24:57.830> which<00:24:58.130> made<00:24:58.340> it<00:24:59.500> interesting<00:25:00.500> to<00:25:00.860> just 00:25:01.150 --> 00:25:01.160 align:start position:0% power which made it interesting to just 00:25:01.160 --> 00:25:04.530 align:start position:0% power which made it interesting to just see<00:25:01.340> that<00:25:01.490> we<00:25:01.700> would<00:25:02.510> be<00:25:02.720> able<00:25:02.810> to<00:25:02.990> manage 00:25:04.530 --> 00:25:04.540 align:start position:0% see that we would be able to manage 00:25:04.540 --> 00:25:07.330 align:start position:0% see that we would be able to manage moving<00:25:05.540> across<00:25:05.750> epochs<00:25:06.200> and<00:25:06.440> this<00:25:07.130> whole 00:25:07.330 --> 00:25:07.340 align:start position:0% moving across epochs and this whole 00:25:07.340 --> 00:25:11.440 align:start position:0% moving across epochs and this whole thing<00:25:07.580> about<00:25:07.760> the<00:25:08.690> clock<00:25:09.440> period<00:25:09.710> of<00:25:10.450> 5050 00:25:11.440 --> 00:25:11.450 align:start position:0% thing about the clock period of 5050 00:25:11.450 --> 00:25:16.510 align:start position:0% thing about the clock period of 5050 works<00:25:11.630> so<00:25:12.170> that<00:25:12.200> the<00:25:14.410> main<00:25:15.410> concern<00:25:16.100> about<00:25:16.280> the 00:25:16.510 --> 00:25:16.520 align:start position:0% works so that the main concern about the 00:25:16.520 --> 00:25:20.250 align:start position:0% works so that the main concern about the test<00:25:16.760> nut<00:25:16.940> is<00:25:17.180> to<00:25:17.630> have<00:25:18.260> it<00:25:18.440> running<00:25:19.130> over<00:25:19.280> long 00:25:20.250 --> 00:25:20.260 align:start position:0% test nut is to have it running over long 00:25:20.260 --> 00:25:26.350 align:start position:0% test nut is to have it running over long sequence<00:25:21.260> of<00:25:21.350> blocks<00:25:21.680> and<00:25:22.010> have<00:25:24.790> GPU<00:25:25.790> -<00:25:26.150> mine 00:25:26.350 --> 00:25:26.360 align:start position:0% sequence of blocks and have GPU - mine 00:25:26.360 --> 00:25:28.870 align:start position:0% sequence of blocks and have GPU - mine them<00:25:26.740> and<00:25:27.740> then<00:25:28.040> it<00:25:28.130> doesn't<00:25:28.430> really<00:25:28.460> matter 00:25:28.870 --> 00:25:28.880 align:start position:0% them and then it doesn't really matter 00:25:28.880 --> 00:25:31.930 align:start position:0% them and then it doesn't really matter how<00:25:29.540> many<00:25:29.600> clients<00:25:30.260> are 00:25:31.930 --> 00:25:31.940 align:start position:0% how many clients are 00:25:31.940 --> 00:25:34.660 align:start position:0% how many clients are and<00:25:32.030> not<00:25:32.930> even<00:25:33.290> matters<00:25:33.590> which<00:25:34.100> kinds<00:25:34.550> are 00:25:34.660 --> 00:25:34.670 align:start position:0% and not even matters which kinds are 00:25:34.670 --> 00:25:36.760 align:start position:0% and not even matters which kinds are only<00:25:34.820> tested<00:25:35.240> as<00:25:35.450> long<00:25:35.690> as<00:25:35.930> at<00:25:36.170> some<00:25:36.440> point 00:25:36.760 --> 00:25:36.770 align:start position:0% only tested as long as at some point 00:25:36.770 --> 00:25:39.280 align:start position:0% only tested as long as at some point when<00:25:37.460> we<00:25:37.550> take<00:25:37.760> apart<00:25:38.150> implementation<00:25:38.900> we 00:25:39.280 --> 00:25:39.290 align:start position:0% when we take apart implementation we 00:25:39.290 --> 00:25:41.080 align:start position:0% when we take apart implementation we check<00:25:39.560> that<00:25:39.590> yeah<00:25:39.890> I<00:25:39.920> can<00:25:40.190> import<00:25:40.490> block<00:25:40.730> zero 00:25:41.080 --> 00:25:41.090 align:start position:0% check that yeah I can import block zero 00:25:41.090 --> 00:25:45.280 align:start position:0% check that yeah I can import block zero to<00:25:41.720> two<00:25:42.530> million<00:25:42.800> and<00:25:43.690> it's<00:25:44.690> very<00:25:45.020> priced 00:25:45.280 --> 00:25:45.290 align:start position:0% to two million and it's very priced 00:25:45.290 --> 00:25:46.990 align:start position:0% to two million and it's very priced correctly<00:25:45.500> it<00:25:46.130> doesn't<00:25:46.370> need<00:25:46.550> to<00:25:46.640> do<00:25:46.760> it<00:25:46.880> in 00:25:46.990 --> 00:25:47.000 align:start position:0% correctly it doesn't need to do it in 00:25:47.000 --> 00:25:54.580 align:start position:0% correctly it doesn't need to do it in real<00:25:47.210> time<00:25:47.270> as<00:25:48.020> the<00:25:48.260> books<00:25:48.500> come<00:25:48.770> along<00:25:53.590> I'll 00:25:54.580 --> 00:25:54.590 align:start position:0% real time as the books come along I'll 00:25:54.590 --> 00:25:56.110 align:start position:0% real time as the books come along I'll take<00:25:54.890> some<00:25:55.100> of<00:25:55.160> the<00:25:55.220> technical<00:25:55.520> controversy 00:25:56.110 --> 00:25:56.120 align:start position:0% take some of the technical controversy 00:25:56.120 --> 00:25:58.150 align:start position:0% take some of the technical controversy questions<00:25:56.480> that's<00:25:56.750> what<00:25:56.960> I<00:25:57.170> was<00:25:57.800> fairly<00:25:58.010> new 00:25:58.150 --> 00:25:58.160 align:start position:0% questions that's what I was fairly new 00:25:58.160 --> 00:26:00.280 align:start position:0% questions that's what I was fairly new to<00:25:58.460> a<00:25:58.490> core<00:25:58.880> development<00:25:59.390> when<00:25:59.630> paka<00:26:00.140> was 00:26:00.280 --> 00:26:00.290 align:start position:0% to a core development when paka was 00:26:00.290 --> 00:26:02.350 align:start position:0% to a core development when paka was really<00:26:00.530> getting<00:26:00.650> its<00:26:00.860> main<00:26:01.010> push<00:26:01.250> so<00:26:01.610> I<00:26:01.910> was 00:26:02.350 --> 00:26:02.360 align:start position:0% really getting its main push so I was 00:26:02.360 --> 00:26:03.400 align:start position:0% really getting its main push so I was drawn<00:26:02.570> to<00:26:02.720> that<00:26:02.810> and<00:26:02.960> I<00:26:02.990> want<00:26:03.140> to<00:26:03.200> make<00:26:03.290> sure 00:26:03.400 --> 00:26:03.410 align:start position:0% drawn to that and I want to make sure 00:26:03.410 --> 00:26:04.360 align:start position:0% drawn to that and I want to make sure that<00:26:03.560> you<00:26:03.830> know<00:26:03.950> that<00:26:04.160> there<00:26:04.280> are<00:26:04.340> any 00:26:04.360 --> 00:26:04.370 align:start position:0% that you know that there are any 00:26:04.370 --> 00:26:05.890 align:start position:0% that you know that there are any technical<00:26:04.700> concerns<00:26:05.180> of<00:26:05.390> those<00:26:05.480> that<00:26:05.630> iron 00:26:05.890 --> 00:26:05.900 align:start position:0% technical concerns of those that iron 00:26:05.900 --> 00:26:07.870 align:start position:0% technical concerns of those that iron out<00:26:06.050> too<00:26:06.140> quick<00:26:06.350> I'm<00:26:07.070> one<00:26:07.280> of<00:26:07.340> the<00:26:07.400> first<00:26:07.550> poems 00:26:07.870 --> 00:26:07.880 align:start position:0% out too quick I'm one of the first poems 00:26:07.880 --> 00:26:09.550 align:start position:0% out too quick I'm one of the first poems that<00:26:08.000> had<00:26:08.240> is<00:26:08.510> the<00:26:08.660> spec<00:26:09.050> was<00:26:09.200> initially 00:26:09.550 --> 00:26:09.560 align:start position:0% that had is the spec was initially 00:26:09.560 --> 00:26:11.740 align:start position:0% that had is the spec was initially written<00:26:09.820> was<00:26:10.820> it<00:26:11.000> really<00:26:11.270> clean<00:26:11.570> room 00:26:11.740 --> 00:26:11.750 align:start position:0% written was it really clean room 00:26:11.750 --> 00:26:15.340 align:start position:0% written was it really clean room implementable<00:26:12.400> it<00:26:13.400> was<00:26:13.520> depending<00:26:13.880> upon<00:26:14.350> code 00:26:15.340 --> 00:26:15.350 align:start position:0% implementable it was depending upon code 00:26:15.350 --> 00:26:17.980 align:start position:0% implementable it was depending upon code blocks<00:26:15.680> and<00:26:15.920> test<00:26:16.130> vectors<00:26:16.520> that<00:26:16.990> weren't 00:26:17.980 --> 00:26:17.990 align:start position:0% blocks and test vectors that weren't 00:26:17.990 --> 00:26:21.220 align:start position:0% blocks and test vectors that weren't very<00:26:18.080> well<00:26:18.440> SPECT<00:26:18.920> out<00:26:19.040> test<00:26:19.370> wise<00:26:19.580> so<00:26:20.510> I<00:26:20.930> went 00:26:21.220 --> 00:26:21.230 align:start position:0% very well SPECT out test wise so I went 00:26:21.230 --> 00:26:23.100 align:start position:0% very well SPECT out test wise so I went and<00:26:21.320> I<00:26:21.410> implemented<00:26:21.830> in<00:26:21.950> Java<00:26:22.250> I<00:26:22.580> had<00:26:22.790> to<00:26:22.910> use 00:26:23.100 --> 00:26:23.110 align:start position:0% and I implemented in Java I had to use 00:26:23.110 --> 00:26:25.960 align:start position:0% and I implemented in Java I had to use Powell's<00:26:24.110> implementation<00:26:24.890> to<00:26:25.490> get<00:26:25.610> some<00:26:25.760> test 00:26:25.960 --> 00:26:25.970 align:start position:0% Powell's implementation to get some test 00:26:25.970 --> 00:26:27.400 align:start position:0% Powell's implementation to get some test vectors<00:26:26.270> out<00:26:26.360> of<00:26:26.510> it<00:26:26.600> severe<00:26:26.900> point<00:26:27.110> know<00:26:27.200> Java 00:26:27.400 --> 00:26:27.410 align:start position:0% vectors out of it severe point know Java 00:26:27.410 --> 00:26:28.570 align:start position:0% vectors out of it severe point know Java has<00:26:27.500> got<00:26:27.620> some<00:26:27.770> of<00:26:27.860> its<00:26:27.980> own<00:26:28.100> issues<00:26:28.430> it 00:26:28.570 --> 00:26:28.580 align:start position:0% has got some of its own issues it 00:26:28.580 --> 00:26:31.120 align:start position:0% has got some of its own issues it doesn't<00:26:28.850> have<00:26:29.200> unsigned<00:26:30.200> integers<00:26:30.560> which<00:26:30.800> you 00:26:31.120 --> 00:26:31.130 align:start position:0% doesn't have unsigned integers which you 00:26:31.130 --> 00:26:32.820 align:start position:0% doesn't have unsigned integers which you know<00:26:31.280> is<00:26:31.430> where<00:26:31.610> most<00:26:31.700> of<00:26:31.850> my<00:26:31.910> bugs<00:26:32.180> came<00:26:32.420> from 00:26:32.820 --> 00:26:32.830 align:start position:0% know is where most of my bugs came from 00:26:32.830 --> 00:26:35.340 align:start position:0% know is where most of my bugs came from but<00:26:33.830> from<00:26:33.980> those<00:26:34.160> I<00:26:34.340> was<00:26:34.400> able<00:26:34.520> to<00:26:34.730> create<00:26:34.970> some 00:26:35.340 --> 00:26:35.350 align:start position:0% but from those I was able to create some 00:26:35.350 --> 00:26:38.260 align:start position:0% but from those I was able to create some some<00:26:36.350> unit<00:26:36.710> tests<00:26:37.130> and<00:26:37.250> some<00:26:37.430> data<00:26:37.610> tests<00:26:38.090> for 00:26:38.260 --> 00:26:38.270 align:start position:0% some unit tests and some data tests for 00:26:38.270 --> 00:26:40.210 align:start position:0% some unit tests and some data tests for transition<00:26:39.050> to<00:26:39.080> prove<00:26:39.320> that<00:26:39.470> you<00:26:39.710> can<00:26:39.890> get<00:26:40.100> the 00:26:40.210 --> 00:26:40.220 align:start position:0% transition to prove that you can get the 00:26:40.220 --> 00:26:42.400 align:start position:0% transition to prove that you can get the particular<00:26:40.490> blocks<00:26:40.880> in<00:26:41.120> it<00:26:41.150> there's<00:26:42.020> so<00:26:42.290> many 00:26:42.400 --> 00:26:42.410 align:start position:0% particular blocks in it there's so many 00:26:42.410 --> 00:26:43.840 align:start position:0% particular blocks in it there's so many different<00:26:42.800> functions<00:26:43.160> there's<00:26:43.370> there's<00:26:43.790> a 00:26:43.840 --> 00:26:43.850 align:start position:0% different functions there's there's a 00:26:43.850 --> 00:26:45.190 align:start position:0% different functions there's there's a test<00:26:44.360> vector<00:26:44.660> now<00:26:44.780> for<00:26:44.930> each<00:26:44.990> of<00:26:45.140> the 00:26:45.190 --> 00:26:45.200 align:start position:0% test vector now for each of the 00:26:45.200 --> 00:26:46.420 align:start position:0% test vector now for each of the functions<00:26:45.560> and<00:26:45.620> that's<00:26:45.800> what<00:26:45.950> was<00:26:46.070> needed<00:26:46.250> so 00:26:46.420 --> 00:26:46.430 align:start position:0% functions and that's what was needed so 00:26:46.430 --> 00:26:50.410 align:start position:0% functions and that's what was needed so I<00:26:46.580> tighten<00:26:47.480> up<00:26:47.540> some<00:26:47.750> of<00:26:47.870> that<00:26:49.060> and<00:26:50.060> the<00:26:50.240> bit<00:26:50.390> I 00:26:50.410 --> 00:26:50.420 align:start position:0% I tighten up some of that and the bit I 00:26:50.420 --> 00:26:51.370 align:start position:0% I tighten up some of that and the bit I mentioned<00:26:50.780> about<00:26:50.900> the<00:26:51.020> concern<00:26:51.290> about 00:26:51.370 --> 00:26:51.380 align:start position:0% mentioned about the concern about 00:26:51.380 --> 00:26:52.840 align:start position:0% mentioned about the concern about compiler<00:26:51.800> bugs<00:26:52.040> was<00:26:52.160> another<00:26:52.430> technical 00:26:52.840 --> 00:26:52.850 align:start position:0% compiler bugs was another technical 00:26:52.850 --> 00:26:54.970 align:start position:0% compiler bugs was another technical controversy<00:26:53.540> but<00:26:53.690> that<00:26:53.870> is<00:26:54.110> you<00:26:54.890> know 00:26:54.970 --> 00:26:54.980 align:start position:0% controversy but that is you know 00:26:54.980 --> 00:26:56.620 align:start position:0% controversy but that is you know basically<00:26:55.400> how<00:26:55.670> good<00:26:55.910> are<00:26:56.060> miners<00:26:56.390> at<00:26:56.510> their 00:26:56.620 --> 00:26:56.630 align:start position:0% basically how good are miners at their 00:26:56.630 --> 00:26:58.360 align:start position:0% basically how good are miners at their DevOps<00:26:56.960> I<00:26:57.170> mean<00:26:57.320> this<00:26:57.380> is<00:26:57.530> their<00:26:57.650> business 00:26:58.360 --> 00:26:58.370 align:start position:0% DevOps I mean this is their business 00:26:58.370 --> 00:27:00.100 align:start position:0% DevOps I mean this is their business the<00:26:59.030> only<00:26:59.150> thing<00:26:59.360> is<00:26:59.480> there's<00:26:59.630> another<00:26:59.870> thing 00:27:00.100 --> 00:27:00.110 align:start position:0% the only thing is there's another thing 00:27:00.110 --> 00:27:01.450 align:start position:0% the only thing is there's another thing that<00:27:00.230> they<00:27:00.320> might<00:27:00.350> need<00:27:00.620> to<00:27:00.770> pay<00:27:00.890> attention<00:27:00.920> to 00:27:01.450 --> 00:27:01.460 align:start position:0% that they might need to pay attention to 00:27:01.460 --> 00:27:03.370 align:start position:0% that they might need to pay attention to but<00:27:02.240> you<00:27:02.540> know<00:27:02.630> the<00:27:02.750> good<00:27:02.870> ones<00:27:03.050> will<00:27:03.230> know 00:27:03.370 --> 00:27:03.380 align:start position:0% but you know the good ones will know 00:27:03.380 --> 00:27:05.500 align:start position:0% but you know the good ones will know what's<00:27:03.560> going<00:27:03.770> on<00:27:03.920> with<00:27:04.100> it<00:27:04.250> and<00:27:04.460> you<00:27:05.420> know 00:27:05.500 --> 00:27:05.510 align:start position:0% what's going on with it and you know 00:27:05.510 --> 00:27:06.940 align:start position:0% what's going on with it and you know these<00:27:05.660> as<00:27:05.960> long<00:27:06.080> as<00:27:06.230> your<00:27:06.380> communication<00:27:06.890> to 00:27:06.940 --> 00:27:06.950 align:start position:0% these as long as your communication to 00:27:06.950 --> 00:27:08.620 align:start position:0% these as long as your communication to each<00:27:06.980> other<00:27:07.190> like<00:27:07.400> you<00:27:07.640> know<00:27:07.670> like<00:27:08.330> a<00:27:08.360> lot<00:27:08.510> of 00:27:08.620 --> 00:27:08.630 align:start position:0% each other like you know like a lot of 00:27:08.630 --> 00:27:11.710 align:start position:0% each other like you know like a lot of them<00:27:08.750> are<00:27:09.220> it's<00:27:10.220> just<00:27:10.430> you<00:27:11.090> know<00:27:11.210> it's<00:27:11.510> another 00:27:11.710 --> 00:27:11.720 align:start position:0% them are it's just you know it's another 00:27:11.720 --> 00:27:13.180 align:start position:0% them are it's just you know it's another thing<00:27:11.900> you<00:27:12.020> got<00:27:12.140> to<00:27:12.170> worry<00:27:12.260> about<00:27:12.410> that's<00:27:12.770> it's 00:27:13.180 --> 00:27:13.190 align:start position:0% thing you got to worry about that's it's 00:27:13.190 --> 00:27:14.560 align:start position:0% thing you got to worry about that's it's totally<00:27:13.760> within<00:27:13.910> their<00:27:14.090> own<00:27:14.150> area<00:27:14.360> of<00:27:14.420> what 00:27:14.560 --> 00:27:14.570 align:start position:0% totally within their own area of what 00:27:14.570 --> 00:27:16.990 align:start position:0% totally within their own area of what they<00:27:14.690> can<00:27:14.750> handle<00:27:15.520> so<00:27:16.520> I<00:27:16.550> think<00:27:16.640> that<00:27:16.850> covers 00:27:16.990 --> 00:27:17.000 align:start position:0% they can handle so I think that covers 00:27:17.000 --> 00:27:18.300 align:start position:0% they can handle so I think that covers most<00:27:17.240> the<00:27:17.420> technical<00:27:17.870> content 00:27:18.300 --> 00:27:18.310 align:start position:0% most the technical content 00:27:18.310 --> 00:27:23.130 align:start position:0% most the technical content were<00:27:18.550> you<00:27:18.670> aware<00:27:18.820> of<00:27:18.880> any<00:27:19.060> others<00:27:19.300> I<00:27:22.140> think 00:27:23.130 --> 00:27:23.140 align:start position:0% were you aware of any others I think 00:27:23.140 --> 00:27:25.440 align:start position:0% were you aware of any others I think someone<00:27:23.500> said<00:27:23.530> that<00:27:23.800> nvidia<00:27:24.400> gpus<00:27:25.240> were 00:27:25.440 --> 00:27:25.450 align:start position:0% someone said that nvidia gpus were 00:27:25.450 --> 00:27:29.520 align:start position:0% someone said that nvidia gpus were faster<00:27:25.960> than<00:27:26.080> a<00:27:26.200> MDGs<00:27:27.330> and<00:27:28.330> I<00:27:28.930> think<00:27:29.260> there<00:27:29.440> was 00:27:29.520 --> 00:27:29.530 align:start position:0% faster than a MDGs and I think there was 00:27:29.530 --> 00:27:31.380 align:start position:0% faster than a MDGs and I think there was benchmarking<00:27:30.190> done<00:27:30.430> to<00:27:30.730> prove<00:27:30.940> that<00:27:31.060> wrong 00:27:31.380 --> 00:27:31.390 align:start position:0% benchmarking done to prove that wrong 00:27:31.390 --> 00:27:37.460 align:start position:0% benchmarking done to prove that wrong remember<00:27:34.020> it's<00:27:35.020> like<00:27:35.260> tweak<00:27:35.530> or<00:27:35.830> there<00:27:36.430> was 00:27:37.460 --> 00:27:37.470 align:start position:0% remember it's like tweak or there was 00:27:37.470 --> 00:27:41.490 align:start position:0% remember it's like tweak or there was yeah<00:27:38.470> there's<00:27:38.890> something<00:27:39.160> like<00:27:39.400> that<00:27:39.640> I<00:27:40.500> think 00:27:41.490 --> 00:27:41.500 align:start position:0% yeah there's something like that I think 00:27:41.500 --> 00:27:43.320 align:start position:0% yeah there's something like that I think that's<00:27:41.800> where<00:27:41.950> the<00:27:42.010> o9<00:27:42.280> 3<00:27:42.490> spec<00:27:42.730> came<00:27:42.910> from<00:27:43.090> can 00:27:43.320 --> 00:27:43.330 align:start position:0% that's where the o9 3 spec came from can 00:27:43.330 --> 00:27:44.970 align:start position:0% that's where the o9 3 spec came from can I<00:27:43.420> drop<00:27:43.600> some<00:27:43.810> of<00:27:43.840> the<00:27:43.930> numbers<00:27:44.200> to<00:27:44.650> make<00:27:44.800> sure 00:27:44.970 --> 00:27:44.980 align:start position:0% I drop some of the numbers to make sure 00:27:44.980 --> 00:27:47.550 align:start position:0% I drop some of the numbers to make sure and<00:27:45.520> to<00:27:45.910> say<00:27:46.090> that<00:27:46.270> the<00:27:46.330> AMD's<00:27:46.750> and<00:27:47.140> the<00:27:47.200> Nvidia 00:27:47.550 --> 00:27:47.560 align:start position:0% and to say that the AMD's and the Nvidia 00:27:47.560 --> 00:27:48.930 align:start position:0% and to say that the AMD's and the Nvidia is<00:27:47.620> are<00:27:47.860> stronger<00:27:48.190> it's<00:27:48.310> really<00:27:48.520> you<00:27:48.610> want<00:27:48.820> it 00:27:48.930 --> 00:27:48.940 align:start position:0% is are stronger it's really you want it 00:27:48.940 --> 00:27:51.540 align:start position:0% is are stronger it's really you want it as<00:27:49.240> for<00:27:50.230> a<00:27:50.260> particularly<00:27:50.560> ambi<00:27:50.950> modelers<00:27:51.340> like 00:27:51.540 --> 00:27:51.550 align:start position:0% as for a particularly ambi modelers like 00:27:51.550 --> 00:27:53.520 align:start position:0% as for a particularly ambi modelers like Nvidia<00:27:52.420> one<00:27:52.600> is<00:27:52.720> much<00:27:52.870> lower<00:27:53.170> than<00:27:53.290> the<00:27:53.440> other 00:27:53.520 --> 00:27:53.530 align:start position:0% Nvidia one is much lower than the other 00:27:53.530 --> 00:27:56.430 align:start position:0% Nvidia one is much lower than the other so<00:27:54.520> the<00:27:54.940> question<00:27:55.270> is<00:27:55.390> you<00:27:55.630> know<00:27:55.660> is<00:27:55.870> that<00:27:56.050> the 00:27:56.430 --> 00:27:56.440 align:start position:0% so the question is you know is that the 00:27:56.440 --> 00:27:58.350 align:start position:0% so the question is you know is that the Nvidia's<00:27:57.160> are<00:27:57.280> better<00:27:57.490> detach<00:27:57.910> or<00:27:58.240> that 00:27:58.350 --> 00:27:58.360 align:start position:0% Nvidia's are better detach or that 00:27:58.360 --> 00:28:00.870 align:start position:0% Nvidia's are better detach or that Andy's<00:27:58.750> worse<00:27:58.990> and<00:27:59.320> you<00:28:00.280> know<00:28:00.400> do<00:28:00.610> we<00:28:00.700> make<00:28:00.850> it 00:28:00.870 --> 00:28:00.880 align:start position:0% Andy's worse and you know do we make it 00:28:00.880 --> 00:28:02.640 align:start position:0% Andy's worse and you know do we make it so<00:28:01.180> it's<00:28:01.360> you<00:28:01.570> got<00:28:01.720> the<00:28:01.810> same<00:28:02.080> sort<00:28:02.470> of<00:28:02.530> that 00:28:02.640 --> 00:28:02.650 align:start position:0% so it's you got the same sort of that 00:28:02.650 --> 00:28:04.500 align:start position:0% so it's you got the same sort of that adjustment<00:28:03.070> and<00:28:03.610> it's<00:28:03.760> it's<00:28:04.060> a<00:28:04.150> lot<00:28:04.300> more 00:28:04.500 --> 00:28:04.510 align:start position:0% adjustment and it's it's a lot more 00:28:04.510 --> 00:28:06.060 align:start position:0% adjustment and it's it's a lot more within<00:28:04.720> ballpark<00:28:05.260> now<00:28:05.380> between<00:28:05.650> those<00:28:05.800> two<00:28:05.950> - 00:28:06.060 --> 00:28:06.070 align:start position:0% within ballpark now between those two - 00:28:06.070 --> 00:28:08.010 align:start position:0% within ballpark now between those two - there's<00:28:06.250> no<00:28:06.630> architectural<00:28:07.630> design 00:28:08.010 --> 00:28:08.020 align:start position:0% there's no architectural design 00:28:08.020 --> 00:28:09.750 align:start position:0% there's no architectural design decisions<00:28:08.500> done<00:28:08.770> that<00:28:09.040> particularly<00:28:09.370> favor 00:28:09.750 --> 00:28:09.760 align:start position:0% decisions done that particularly favor 00:28:09.760 --> 00:28:11.310 align:start position:0% decisions done that particularly favor Nvidia<00:28:10.210> or<00:28:10.300> AMD<00:28:10.480> not<00:28:11.020> that<00:28:11.110> I<00:28:11.170> know<00:28:11.230> anything 00:28:11.310 --> 00:28:11.320 align:start position:0% Nvidia or AMD not that I know anything 00:28:11.320 --> 00:28:12.930 align:start position:0% Nvidia or AMD not that I know anything about<00:28:11.650> how<00:28:11.830> to<00:28:11.860> do<00:28:12.040> their<00:28:12.160> architectures<00:28:12.730> the 00:28:12.930 --> 00:28:12.940 align:start position:0% about how to do their architectures the 00:28:12.940 --> 00:28:15.000 align:start position:0% about how to do their architectures the big<00:28:13.690> changes<00:28:14.080> were<00:28:14.230> to<00:28:14.320> take<00:28:14.530> a<00:28:14.560> lot<00:28:14.740> of<00:28:14.770> stuff 00:28:15.000 --> 00:28:15.010 align:start position:0% big changes were to take a lot of stuff 00:28:15.010 --> 00:28:17.520 align:start position:0% big changes were to take a lot of stuff down<00:28:15.190> at<00:28:15.340> 32<00:28:15.700> bits<00:28:15.940> and<00:28:16.150> all<00:28:16.240> GPUs<00:28:16.930> nowadays<00:28:17.350> or 00:28:17.520 --> 00:28:17.530 align:start position:0% down at 32 bits and all GPUs nowadays or 00:28:17.530 --> 00:28:20.160 align:start position:0% down at 32 bits and all GPUs nowadays or 32-bit<00:28:17.890> GPS<00:28:18.460> so<00:28:19.300> if<00:28:19.360> there<00:28:19.540> was<00:28:19.600> a<00:28:19.690> 32-bit 00:28:20.160 --> 00:28:20.170 align:start position:0% 32-bit GPS so if there was a 32-bit 00:28:20.170 --> 00:28:21.990 align:start position:0% 32-bit GPS so if there was a 32-bit version<00:28:20.380> of<00:28:20.740> a<00:28:21.010> particular<00:28:21.490> algorithm<00:28:21.700> that 00:28:21.990 --> 00:28:22.000 align:start position:0% version of a particular algorithm that 00:28:22.000 --> 00:28:23.940 align:start position:0% version of a particular algorithm that Sloan<00:28:22.330> was<00:28:22.420> preferred<00:28:22.840> and<00:28:23.170> that's<00:28:23.710> why<00:28:23.830> they 00:28:23.940 --> 00:28:23.950 align:start position:0% Sloan was preferred and that's why they 00:28:23.950 --> 00:28:26.130 align:start position:0% Sloan was preferred and that's why they went<00:28:24.070> to<00:28:24.130> could<00:28:24.370> check<00:28:24.580> at<00:28:24.850> 800<00:28:25.360> is<00:28:25.810> because 00:28:26.130 --> 00:28:26.140 align:start position:0% went to could check at 800 is because 00:28:26.140 --> 00:28:28.470 align:start position:0% went to could check at 800 is because it's<00:28:26.290> 32-bit<00:28:26.890> based<00:28:27.130> and<00:28:27.460> you<00:28:28.180> put<00:28:28.360> that 00:28:28.470 --> 00:28:28.480 align:start position:0% it's 32-bit based and you put that 00:28:28.480 --> 00:28:30.210 align:start position:0% it's 32-bit based and you put that through<00:28:28.630> a<00:28:28.690> GPU<00:28:29.080> through<00:28:29.650> the<00:28:29.770> 32-bit 00:28:30.210 --> 00:28:30.220 align:start position:0% through a GPU through the 32-bit 00:28:30.220 --> 00:28:31.740 align:start position:0% through a GPU through the 32-bit integers<00:28:30.550> those<00:28:30.790> things<00:28:31.000> are<00:28:31.090> like<00:28:31.180> optimized 00:28:31.740 --> 00:28:31.750 align:start position:0% integers those things are like optimized 00:28:31.750 --> 00:28:33.570 align:start position:0% integers those things are like optimized to<00:28:31.930> know<00:28:32.050> and<00:28:32.350> in<00:28:32.470> just<00:28:32.680> blazes<00:28:33.130> right<00:28:33.310> through 00:28:33.570 --> 00:28:33.580 align:start position:0% to know and in just blazes right through 00:28:33.580 --> 00:28:35.520 align:start position:0% to know and in just blazes right through so<00:28:34.180> that<00:28:34.330> was<00:28:34.510> part<00:28:34.720> of<00:28:34.840> the<00:28:34.930> decisions<00:28:35.320> of<00:28:35.410> why 00:28:35.520 --> 00:28:35.530 align:start position:0% so that was part of the decisions of why 00:28:35.530 --> 00:28:36.780 align:start position:0% so that was part of the decisions of why they<00:28:35.680> did<00:28:35.800> a<00:28:35.830> lot<00:28:36.010> of<00:28:36.040> their<00:28:36.220> changes<00:28:36.520> was<00:28:36.670> to 00:28:36.780 --> 00:28:36.790 align:start position:0% they did a lot of their changes was to 00:28:36.790 --> 00:28:39.150 align:start position:0% they did a lot of their changes was to make<00:28:36.940> it<00:28:37.260> optimized<00:28:38.260> for<00:28:38.470> the<00:28:38.650> general<00:28:38.950> class 00:28:39.150 --> 00:28:39.160 align:start position:0% make it optimized for the general class 00:28:39.160 --> 00:28:43.860 align:start position:0% make it optimized for the general class of<00:28:39.190> GPUs<00:28:39.760> not<00:28:40.360> one<00:28:40.630> over<00:28:40.870> the<00:28:40.990> other<00:28:42.870> and 00:28:43.860 --> 00:28:43.870 align:start position:0% of GPUs not one over the other and 00:28:43.870 --> 00:28:46.200 align:start position:0% of GPUs not one over the other and another<00:28:44.530> technical<00:28:45.250> I<00:28:45.610> wouldn't<00:28:46.090> say 00:28:46.200 --> 00:28:46.210 align:start position:0% another technical I wouldn't say 00:28:46.210 --> 00:28:49.620 align:start position:0% another technical I wouldn't say controversy<00:28:46.870> per<00:28:47.170> se<00:28:47.410> but<00:28:47.770> maybe<00:28:48.630> questions 00:28:49.620 --> 00:28:49.630 align:start position:0% controversy per se but maybe questions 00:28:49.630 --> 00:28:54.630 align:start position:0% controversy per se but maybe questions still<00:28:49.840> to<00:28:50.050> be<00:28:50.140> solved<00:28:50.680> is<00:28:51.090> if<00:28:52.090> going<00:28:52.960> from<00:28:53.320> E<00:28:53.680> - 00:28:54.630 --> 00:28:54.640 align:start position:0% still to be solved is if going from E - 00:28:54.640 --> 00:29:00.510 align:start position:0% still to be solved is if going from E - as<00:28:55.630> moto<00:28:56.140> to<00:28:56.410> propound<00:28:58.770> there<00:28:59.770> is<00:28:59.980> still<00:29:00.310> the 00:29:00.510 --> 00:29:00.520 align:start position:0% as moto to propound there is still the 00:29:00.520 --> 00:29:04.110 align:start position:0% as moto to propound there is still the difficulty<00:29:02.100> so<00:29:03.100> there<00:29:03.250> a<00:29:03.490> theorem<00:29:03.820> uses<00:29:04.090> a 00:29:04.110 --> 00:29:04.120 align:start position:0% difficulty so there a theorem uses a 00:29:04.120 --> 00:29:06.360 align:start position:0% difficulty so there a theorem uses a difficulty<00:29:04.750> formula<00:29:05.230> which<00:29:05.410> is<00:29:05.440> totally 00:29:06.360 --> 00:29:06.370 align:start position:0% difficulty formula which is totally 00:29:06.370 --> 00:29:10.980 align:start position:0% difficulty formula which is totally dependent<00:29:06.700> on<00:29:07.030> the<00:29:07.120> previous<00:29:07.510> book<00:29:07.750> and<00:29:09.990> if 00:29:10.980 --> 00:29:10.990 align:start position:0% dependent on the previous book and if 00:29:10.990 --> 00:29:17.090 align:start position:0% dependent on the previous book and if the<00:29:11.500> perfectly<00:29:12.430> proper<00:29:14.310> hashing<00:29:15.310> engine<00:29:16.000> is 00:29:17.090 --> 00:29:17.100 align:start position:0% the perfectly proper hashing engine is 00:29:17.100 --> 00:29:20.160 align:start position:0% the perfectly proper hashing engine is half<00:29:18.100> as<00:29:18.460> fast<00:29:18.760> that<00:29:19.360> means<00:29:19.630> that<00:29:19.840> it<00:29:19.990> will 00:29:20.160 --> 00:29:20.170 align:start position:0% half as fast that means that it will 00:29:20.170 --> 00:29:22.880 align:start position:0% half as fast that means that it will take<00:29:20.860> quite<00:29:21.280> a<00:29:21.400> bit<00:29:21.670> longer 00:29:22.880 --> 00:29:22.890 align:start position:0% take quite a bit longer 00:29:22.890 --> 00:29:26.930 align:start position:0% take quite a bit longer find<00:29:23.670> an<00:29:24.059> elaborately<00:29:24.770> difficult<00:29:25.770> block<00:29:26.100> so 00:29:26.930 --> 00:29:26.940 align:start position:0% find an elaborately difficult block so 00:29:26.940 --> 00:29:29.980 align:start position:0% find an elaborately difficult block so there<00:29:27.299> will<00:29:27.390> be<00:29:27.450> very<00:29:27.990> slow<00:29:28.290> blocks<00:29:28.940> unless 00:29:29.980 --> 00:29:29.990 align:start position:0% there will be very slow blocks unless 00:29:29.990 --> 00:29:35.419 align:start position:0% there will be very slow blocks unless maybe<00:29:30.990> a<00:29:31.640> housing<00:29:32.640> or<00:29:32.850> a<00:29:33.410> modification<00:29:34.410> to<00:29:35.250> the 00:29:35.419 --> 00:29:35.429 align:start position:0% maybe a housing or a modification to the 00:29:35.429 --> 00:29:37.039 align:start position:0% maybe a housing or a modification to the difficult<00:29:35.910> to<00:29:36.030> formula<00:29:36.540> difficult 00:29:37.039 --> 00:29:37.049 align:start position:0% difficult to formula difficult 00:29:37.049 --> 00:29:40.730 align:start position:0% difficult to formula difficult calculation<00:29:37.710> at<00:29:38.250> the<00:29:38.640> point<00:29:39.390> where<00:29:39.660> switch<00:29:40.020> is 00:29:40.730 --> 00:29:40.740 align:start position:0% calculation at the point where switch is 00:29:40.740 --> 00:29:44.390 align:start position:0% calculation at the point where switch is made<00:29:41.450> so<00:29:42.450> that's<00:29:42.690> still<00:29:43.440> something<00:29:43.799> that<00:29:44.190> can 00:29:44.390 --> 00:29:44.400 align:start position:0% made so that's still something that can 00:29:44.400 --> 00:29:47.150 align:start position:0% made so that's still something that can be<00:29:44.549> elaborated<00:29:45.330> with<00:29:45.360> ensure<00:29:45.990> that<00:29:46.170> progress 00:29:47.150 --> 00:29:47.160 align:start position:0% be elaborated with ensure that progress 00:29:47.160 --> 00:29:51.440 align:start position:0% be elaborated with ensure that progress is<00:29:47.400> nicely<00:29:49.549> some<00:29:50.549> take<00:29:50.730> a<00:29:50.790> picture<00:29:51.120> of<00:29:51.150> all<00:29:51.299> of 00:29:51.440 --> 00:29:51.450 align:start position:0% is nicely some take a picture of all of 00:29:51.450 --> 00:29:55.430 align:start position:0% is nicely some take a picture of all of us<00:29:51.540> before<00:29:51.750> Martinez<00:29:52.260> delete<00:29:53.600> reading<00:29:54.600> and 00:29:55.430 --> 00:29:55.440 align:start position:0% us before Martinez delete reading and 00:29:55.440 --> 00:30:02.470 align:start position:0% us before Martinez delete reading and then<00:29:55.530> to<00:29:55.650> be<00:29:55.740> difficult<00:29:56.190> happens<00:29:56.600> sit<00:29:57.600> down 00:30:02.470 --> 00:30:02.480 align:start position:0% 00:30:02.480 --> 00:30:04.000 align:start position:0% thanks<00:30:03.480> everyone 00:30:04.000 --> 00:30:04.010 align:start position:0% thanks everyone 00:30:04.010 --> 00:30:06.470 align:start position:0% thanks everyone okay<00:30:05.010> and<00:30:05.370> yeah<00:30:05.700> you<00:30:05.760> got<00:30:05.970> to<00:30:06.059> make<00:30:06.179> you<00:30:06.270> next 00:30:06.470 --> 00:30:06.480 align:start position:0% okay and yeah you got to make you next 00:30:06.480 --> 00:30:09.200 align:start position:0% okay and yeah you got to make you next time<00:30:06.630> over<00:30:07.110> there<00:30:07.679> longside<00:30:07.830> o<00:30:08.549> memory<00:30:08.970> the 00:30:09.200 --> 00:30:09.210 align:start position:0% time over there longside o memory the 00:30:09.210 --> 00:30:11.630 align:start position:0% time over there longside o memory the Pokemon<00:30:09.690> bubbly<00:30:10.380> okay<00:30:10.950> perfect 00:30:11.630 --> 00:30:11.640 align:start position:0% Pokemon bubbly okay perfect 00:30:11.640 --> 00:30:13.580 align:start position:0% Pokemon bubbly okay perfect all<00:30:12.090> right<00:30:12.299> any<00:30:12.750> more<00:30:12.780> technical<00:30:13.350> otherwise 00:30:13.580 --> 00:30:13.590 align:start position:0% all right any more technical otherwise 00:30:13.590 --> 00:30:15.890 align:start position:0% all right any more technical otherwise we'll<00:30:13.770> jump<00:30:13.980> in<00:30:14.100> the<00:30:14.160> political<00:30:14.510> I'll<00:30:15.510> be<00:30:15.630> fun 00:30:15.890 --> 00:30:15.900 align:start position:0% we'll jump in the political I'll be fun 00:30:15.900 --> 00:30:18.350 align:start position:0% we'll jump in the political I'll be fun there<00:30:16.470> are<00:30:16.559> some<00:30:16.679> things<00:30:16.830> you<00:30:17.120> mention<00:30:18.120> of<00:30:18.240> the 00:30:18.350 --> 00:30:18.360 align:start position:0% there are some things you mention of the 00:30:18.360 --> 00:30:20.060 align:start position:0% there are some things you mention of the block<00:30:18.630> jump<00:30:18.929> if<00:30:19.140> we<00:30:19.230> did<00:30:19.380> nothing<00:30:19.559> and<00:30:19.919> take 00:30:20.060 --> 00:30:20.070 align:start position:0% block jump if we did nothing and take 00:30:20.070 --> 00:30:21.799 align:start position:0% block jump if we did nothing and take about<00:30:20.160> three<00:30:20.580> or<00:30:20.610> four<00:30:20.790> hours<00:30:20.820> to<00:30:21.360> cut<00:30:21.510> in<00:30:21.600> half 00:30:21.799 --> 00:30:21.809 align:start position:0% about three or four hours to cut in half 00:30:21.809 --> 00:30:24.590 align:start position:0% about three or four hours to cut in half there's<00:30:22.530> also<00:30:22.770> a<00:30:22.919> slight<00:30:23.100> impact<00:30:23.880> on<00:30:24.210> the<00:30:24.419> ice 00:30:24.590 --> 00:30:24.600 align:start position:0% there's also a slight impact on the ice 00:30:24.600 --> 00:30:26.990 align:start position:0% there's also a slight impact on the ice age<00:30:24.870> and<00:30:25.169> that<00:30:25.860> impact<00:30:26.250> there<00:30:26.429> is<00:30:26.460> if<00:30:26.820> it<00:30:26.910> only 00:30:26.990 --> 00:30:27.000 align:start position:0% age and that impact there is if it only 00:30:27.000 --> 00:30:29.380 align:start position:0% age and that impact there is if it only felt<00:30:27.360> like<00:30:27.510> two<00:30:27.690> weeks<00:30:27.840> to<00:30:27.990> a<00:30:28.140> month<00:30:28.169> earlier 00:30:29.380 --> 00:30:29.390 align:start position:0% felt like two weeks to a month earlier 00:30:29.390 --> 00:30:31.610 align:start position:0% felt like two weeks to a month earlier because<00:30:30.390> of<00:30:30.660> the<00:30:30.720> exponential<00:30:31.260> nature<00:30:31.290> of<00:30:31.559> the 00:30:31.610 --> 00:30:31.620 align:start position:0% because of the exponential nature of the 00:30:31.620 --> 00:30:33.230 align:start position:0% because of the exponential nature of the ice<00:30:31.740> age<00:30:31.980> I<00:30:32.280> think<00:30:32.370> it<00:30:32.549> was<00:30:32.640> the<00:30:32.700> third<00:30:33.000> thing 00:30:33.230 --> 00:30:33.240 align:start position:0% ice age I think it was the third thing 00:30:33.240 --> 00:30:36.409 align:start position:0% ice age I think it was the third thing played<00:30:33.540> it<00:30:33.770> might<00:30:34.770> have<00:30:34.860> gone<00:30:34.950> in<00:30:35.160> but<00:30:35.419> it's 00:30:36.409 --> 00:30:36.419 align:start position:0% played it might have gone in but it's 00:30:36.419 --> 00:30:39.200 align:start position:0% played it might have gone in but it's not<00:30:36.840> too<00:30:37.350> critical<00:30:37.590> it's<00:30:37.950> arrogance<00:30:38.309> no 00:30:39.200 --> 00:30:39.210 align:start position:0% not too critical it's arrogance no 00:30:39.210 --> 00:30:41.180 align:start position:0% not too critical it's arrogance no worries<00:30:39.450> the<00:30:39.660> one<00:30:39.780> happened<00:30:40.200> when<00:30:40.380> they<00:30:40.590> when 00:30:41.180 --> 00:30:41.190 align:start position:0% worries the one happened when they when 00:30:41.190 --> 00:30:43.070 align:start position:0% worries the one happened when they when they<00:30:41.280> thought<00:30:41.549> the<00:30:41.910> transaction<00:30:42.720> rated<00:30:42.990> at 00:30:43.070 --> 00:30:43.080 align:start position:0% they thought the transaction rated at 00:30:43.080 --> 00:30:45.049 align:start position:0% they thought the transaction rated at the<00:30:43.140> beginning<00:30:43.380> again<00:30:43.530> it's<00:30:43.950> you<00:30:44.250> know<00:30:44.340> we 00:30:45.049 --> 00:30:45.059 align:start position:0% the beginning again it's you know we 00:30:45.059 --> 00:30:46.549 align:start position:0% the beginning again it's you know we communicated<00:30:45.660> another<00:30:45.900> time<00:30:46.140> I'll<00:30:46.230> be<00:30:46.350> fine 00:30:46.549 --> 00:30:46.559 align:start position:0% communicated another time I'll be fine 00:30:46.559 --> 00:30:48.770 align:start position:0% communicated another time I'll be fine or<00:30:46.770> we<00:30:46.919> went<00:30:47.070> go<00:30:47.220> ahead<00:30:47.460> and<00:30:47.730> do<00:30:48.210> a<00:30:48.240> difficulty 00:30:48.770 --> 00:30:48.780 align:start position:0% or we went go ahead and do a difficulty 00:30:48.780 --> 00:30:50.580 align:start position:0% or we went go ahead and do a difficulty cut<00:30:49.020> combine<00:30:49.410> that<00:30:49.590> with<00:30:49.650> a<00:30:49.799> nice 00:30:50.580 --> 00:30:50.590 align:start position:0% cut combine that with a nice 00:30:50.590 --> 00:30:58.410 align:start position:0% cut combine that with a nice you<00:30:51.130> know<00:30:51.250> I<00:30:51.280> think<00:30:51.370> it'll<00:30:51.580> be<00:30:51.670> fine 00:30:58.410 --> 00:30:58.420 align:start position:0% 00:30:58.420 --> 00:31:01.380 align:start position:0% do<00:30:59.410> you<00:30:59.500> talk<00:30:59.620> a<00:30:59.680> little<00:30:59.770> bit<00:30:59.890> about<00:30:59.980> the<00:31:00.790> fvg 00:31:01.380 --> 00:31:01.390 align:start position:0% do you talk a little bit about the fvg 00:31:01.390 --> 00:31:03.720 align:start position:0% do you talk a little bit about the fvg resistance<00:31:01.960> of<00:31:02.290> Prague<00:31:03.040> now<00:31:03.250> and<00:31:03.580> it's 00:31:03.720 --> 00:31:03.730 align:start position:0% resistance of Prague now and it's 00:31:03.730 --> 00:31:05.820 align:start position:0% resistance of Prague now and it's cost-effective<00:31:04.690> actually<00:31:05.290> try<00:31:05.500> to<00:31:05.560> run 00:31:05.820 --> 00:31:05.830 align:start position:0% cost-effective actually try to run 00:31:05.830 --> 00:31:16.530 align:start position:0% cost-effective actually try to run around<00:31:06.040> FPGA<00:31:12.210> I<00:31:13.620> think<00:31:14.620> the<00:31:15.270> talked<00:31:16.270> about 00:31:16.530 --> 00:31:16.540 align:start position:0% around FPGA I think the talked about 00:31:16.540 --> 00:31:23.460 align:start position:0% around FPGA I think the talked about three<00:31:17.310> and<00:31:18.480> the<00:31:19.480> period<00:31:19.890> the<00:31:20.890> 50<00:31:21.690> blocks<00:31:22.690> the 00:31:23.460 --> 00:31:23.470 align:start position:0% three and the period the 50 blocks the 00:31:23.470 --> 00:31:26.490 align:start position:0% three and the period the 50 blocks the random<00:31:23.830> max<00:31:24.100> period<00:31:24.730> we<00:31:25.660> need<00:31:25.810> to<00:31:25.900> recompile 00:31:26.490 --> 00:31:26.500 align:start position:0% random max period we need to recompile 00:31:26.500 --> 00:31:29.940 align:start position:0% random max period we need to recompile the<00:31:26.950> program<00:31:27.090> and<00:31:28.090> kept<00:31:28.330> a<00:31:28.510> few<00:31:28.840> blocks<00:31:29.110> that 00:31:29.940 --> 00:31:29.950 align:start position:0% the program and kept a few blocks that 00:31:29.950 --> 00:31:33.270 align:start position:0% the program and kept a few blocks that block<00:31:30.250> video<00:31:30.850> is<00:31:31.180> like<00:31:31.420> too<00:31:31.720> small<00:31:32.080> to<00:31:32.440> really 00:31:33.270 --> 00:31:33.280 align:start position:0% block video is like too small to really 00:31:33.280 --> 00:31:36.900 align:start position:0% block video is like too small to really be<00:31:33.460> compiled<00:31:34.170> PGA<00:31:35.170> pro<00:31:35.410> -<00:31:35.700> and<00:31:36.700> furthermore 00:31:36.900 --> 00:31:36.910 align:start position:0% be compiled PGA pro - and furthermore 00:31:36.910 --> 00:31:41.040 align:start position:0% be compiled PGA pro - and furthermore the<00:31:37.810> power<00:31:38.800> requirements<00:31:39.610> in<00:31:39.820> FPGA<00:31:40.210> is<00:31:40.450> a<00:31:40.690> lot 00:31:41.040 --> 00:31:41.050 align:start position:0% the power requirements in FPGA is a lot 00:31:41.050 --> 00:32:01.890 align:start position:0% the power requirements in FPGA is a lot more<00:31:41.350> that<00:31:47.610> much<00:31:48.610> harder<00:31:50.250> looking<00:31:51.250> at<00:31:51.370> that<00:32:00.900> so 00:32:01.890 --> 00:32:01.900 align:start position:0% more that much harder looking at that so 00:32:01.900 --> 00:32:05.370 align:start position:0% more that much harder looking at that so the<00:32:02.050> a<00:32:02.320> little<00:32:03.100> bit<00:32:04.230> today 00:32:05.370 --> 00:32:05.380 align:start position:0% the a little bit today 00:32:05.380 --> 00:32:08.400 align:start position:0% the a little bit today there<00:32:05.710> exists<00:32:06.250> FPGA<00:32:07.090> accelerators<00:32:07.990> that<00:32:08.020> you 00:32:08.400 --> 00:32:08.410 align:start position:0% there exists FPGA accelerators that you 00:32:08.410 --> 00:32:12.450 align:start position:0% there exists FPGA accelerators that you can<00:32:09.090> plug<00:32:10.090> into<00:32:10.150> the<00:32:10.690> GPU<00:32:11.260> to<00:32:11.530> offload<00:32:12.010> can 00:32:12.450 --> 00:32:12.460 align:start position:0% can plug into the GPU to offload can 00:32:12.460 --> 00:32:16.770 align:start position:0% can plug into the GPU to offload can change<00:32:13.470> political<00:32:14.470> track<00:32:14.920> for<00:32:15.130> bread<00:32:15.400> yeah<00:32:16.150> so 00:32:16.770 --> 00:32:16.780 align:start position:0% change political track for bread yeah so 00:32:16.780 --> 00:32:18.720 align:start position:0% change political track for bread yeah so to<00:32:16.840> offer<00:32:17.050> the<00:32:17.320> cat's-eye<00:32:17.710> calculation<00:32:18.460> from 00:32:18.720 --> 00:32:18.730 align:start position:0% to offer the cat's-eye calculation from 00:32:18.730 --> 00:32:23.400 align:start position:0% to offer the cat's-eye calculation from the<00:32:18.880> GPU<00:32:19.270> to<00:32:19.600> an<00:32:19.840> FPGA<00:32:20.320> and<00:32:21.840> it<00:32:22.840> so<00:32:23.020> that<00:32:23.170> works 00:32:23.400 --> 00:32:23.410 align:start position:0% the GPU to an FPGA and it so that works 00:32:23.410 --> 00:32:25.680 align:start position:0% the GPU to an FPGA and it so that works really<00:32:23.530> well<00:32:23.890> for<00:32:23.950> a<00:32:24.190> test<00:32:24.430> that's<00:32:24.760> I<00:32:25.300> think 00:32:25.680 --> 00:32:25.690 align:start position:0% really well for a test that's I think 00:32:25.690 --> 00:32:43.170 align:start position:0% really well for a test that's I think two<00:32:26.020> portions<00:32:26.680> of<00:32:27.450> catch<00:32:28.450> a<00:32:28.660> king<00:32:41.370> so<00:32:42.370> that<00:32:42.760> so 00:32:43.170 --> 00:32:43.180 align:start position:0% two portions of catch a king so that so 00:32:43.180 --> 00:32:45.920 align:start position:0% two portions of catch a king so that so using<00:32:43.630> one<00:32:43.750> of<00:32:43.780> these<00:32:43.930> accelerators<00:32:44.500> on<00:32:44.710> it<00:32:44.830> - 00:32:45.920 --> 00:32:45.930 align:start position:0% using one of these accelerators on it - 00:32:45.930 --> 00:32:48.120 align:start position:0% using one of these accelerators on it - tend<00:32:46.930> to<00:32:47.140> does<00:32:47.350> it<00:32:47.500> to<00:32:47.590> make<00:32:47.800> it<00:32:47.950> more 00:32:48.120 --> 00:32:48.130 align:start position:0% tend to does it to make it more 00:32:48.130 --> 00:32:53.580 align:start position:0% tend to does it to make it more effective<00:32:49.530> and<00:32:50.530> on<00:32:51.090> the<00:32:52.090> pro<00:32:52.390> pal<00:32:52.750> it's<00:32:53.260> not 00:32:53.580 --> 00:32:53.590 align:start position:0% effective and on the pro pal it's not 00:32:53.590 --> 00:32:57.140 align:start position:0% effective and on the pro pal it's not harder<00:32:54.190> to<00:32:54.460> get<00:32:54.700> that<00:32:54.940> kind<00:32:55.270> of<00:32:55.330> boost<00:32:55.630> from 00:32:57.140 --> 00:32:57.150 align:start position:0% harder to get that kind of boost from 00:32:57.150 --> 00:33:02.480 align:start position:0% harder to get that kind of boost from fpga<00:32:58.150> accelerator<00:32:59.130> because<00:33:00.130> the<00:33:00.610> portion<00:33:01.240> of 00:33:02.480 --> 00:33:02.490 align:start position:0% fpga accelerator because the portion of 00:33:02.490 --> 00:33:05.550 align:start position:0% fpga accelerator because the portion of power<00:33:03.490> that<00:33:03.880> is<00:33:04.000> spent<00:33:04.270> on<00:33:04.450> that<00:33:04.600> operation<00:33:05.230> is 00:33:05.550 --> 00:33:05.560 align:start position:0% power that is spent on that operation is 00:33:05.560 --> 00:33:11.290 align:start position:0% power that is spent on that operation is a<00:33:06.430> lot<00:33:06.970> less 00:33:11.290 --> 00:33:11.300 align:start position:0% 00:33:11.300 --> 00:33:14.480 align:start position:0% okay<00:33:12.300> so<00:33:12.930> we<00:33:13.020> have<00:33:13.110> about<00:33:13.260> 10<00:33:13.470> minutes<00:33:13.680> left 00:33:14.480 --> 00:33:14.490 align:start position:0% okay so we have about 10 minutes left 00:33:14.490 --> 00:33:16.130 align:start position:0% okay so we have about 10 minutes left little<00:33:15.090> by<00:33:15.270> little<00:33:15.300> less<00:33:15.690> than<00:33:15.810> that<00:33:15.900> maybe 00:33:16.130 --> 00:33:16.140 align:start position:0% little by little less than that maybe 00:33:16.140 --> 00:33:18.730 align:start position:0% little by little less than that maybe seven<00:33:16.500> so<00:33:16.950> let's<00:33:17.160> go<00:33:17.340> into<00:33:17.490> politics<00:33:17.880> I<00:33:18.060> guess 00:33:18.730 --> 00:33:18.740 align:start position:0% seven so let's go into politics I guess 00:33:18.740 --> 00:33:20.810 align:start position:0% seven so let's go into politics I guess something<00:33:19.740> for<00:33:19.890> the<00:33:19.980> politics<00:33:20.340> of<00:33:20.520> it<00:33:20.670> does 00:33:20.810 --> 00:33:20.820 align:start position:0% something for the politics of it does 00:33:20.820 --> 00:33:31.240 align:start position:0% something for the politics of it does anyone<00:33:21.030> have<00:33:21.150> any<00:33:21.270> questions<00:33:21.420> or<00:33:22.140> comments<00:33:30.140> I 00:33:31.240 --> 00:33:31.250 align:start position:0% anyone have any questions or comments I 00:33:31.250 --> 00:33:33.410 align:start position:0% anyone have any questions or comments I really<00:33:32.250> can't<00:33:32.490> real<00:33:32.610> question<00:33:33.000> you<00:33:33.240> know<00:33:33.330> what 00:33:33.410 --> 00:33:33.420 align:start position:0% really can't real question you know what 00:33:33.420 --> 00:33:35.420 align:start position:0% really can't real question you know what is<00:33:33.510> it<00:33:33.660> it's<00:33:33.840> product<00:33:34.140> that<00:33:34.260> the<00:33:34.440> last<00:33:34.710> mining 00:33:35.420 --> 00:33:35.430 align:start position:0% is it it's product that the last mining 00:33:35.430 --> 00:33:40.310 align:start position:0% is it it's product that the last mining algorithm<00:33:35.970> they<00:33:36.150> beat<00:33:36.420> one<00:33:36.720> point<00:33:36.990> ax<00:33:39.320> wasn't 00:33:40.310 --> 00:33:40.320 align:start position:0% algorithm they beat one point ax wasn't 00:33:40.320 --> 00:33:42.170 align:start position:0% algorithm they beat one point ax wasn't the<00:33:40.380> last<00:33:40.530> algorithm<00:33:41.220> so<00:33:41.730> I've<00:33:41.820> heard<00:33:42.060> that 00:33:42.170 --> 00:33:42.180 align:start position:0% the last algorithm so I've heard that 00:33:42.180 --> 00:33:44.630 align:start position:0% the last algorithm so I've heard that they<00:33:42.330> have<00:33:42.540> a<00:33:42.570> little<00:33:42.810> like<00:33:43.020> knobs<00:33:43.560> in<00:33:43.860> it<00:33:44.010> you 00:33:44.630 --> 00:33:44.640 align:start position:0% they have a little like knobs in it you 00:33:44.640 --> 00:33:47.900 align:start position:0% they have a little like knobs in it you can<00:33:44.940> might<00:33:45.090> adjust<00:33:45.240> to<00:33:45.990> like<00:33:46.560> make<00:33:46.860> it<00:33:46.910> harder 00:33:47.900 --> 00:33:47.910 align:start position:0% can might adjust to like make it harder 00:33:47.910 --> 00:33:52.010 align:start position:0% can might adjust to like make it harder yeah<00:33:48.630> I<00:33:48.990> don't<00:33:49.050> understand<00:33:49.710> it<00:33:49.950> but<00:33:50.900> you<00:33:51.900> know 00:33:52.010 --> 00:33:52.020 align:start position:0% yeah I don't understand it but you know 00:33:52.020 --> 00:33:55.250 align:start position:0% yeah I don't understand it but you know for<00:33:52.440> now<00:33:53.010> that's<00:33:53.250> a<00:33:53.400> question<00:33:53.580> for<00:33:54.020> for<00:33:55.020> the 00:33:55.250 --> 00:33:55.260 align:start position:0% for now that's a question for for the 00:33:55.260 --> 00:33:57.020 align:start position:0% for now that's a question for for the answers<00:33:56.160> of<00:33:56.280> that<00:33:56.370> is<00:33:56.520> we<00:33:56.640> would<00:33:56.730> even<00:33:56.940> know 00:33:57.020 --> 00:33:57.030 align:start position:0% answers of that is we would even know 00:33:57.030 --> 00:33:59.320 align:start position:0% answers of that is we would even know the<00:33:57.150> answer<00:33:57.180> when<00:33:57.690> 82.0<00:33:58.350> is<00:33:58.470> happening<00:33:58.890> and 00:33:59.320 --> 00:33:59.330 align:start position:0% the answer when 82.0 is happening and 00:33:59.330 --> 00:34:02.660 align:start position:0% the answer when 82.0 is happening and even<00:34:00.330> then<00:34:00.660> we<00:34:01.020> need<00:34:01.170> to<00:34:01.260> know<00:34:01.490> all<00:34:02.490> the 00:34:02.660 --> 00:34:02.670 align:start position:0% even then we need to know all the 00:34:02.670 --> 00:34:04.520 align:start position:0% even then we need to know all the details<00:34:02.820> which<00:34:03.390> we're<00:34:03.690> getting<00:34:04.050> really<00:34:04.380> close 00:34:04.520 --> 00:34:04.530 align:start position:0% details which we're getting really close 00:34:04.530 --> 00:34:06.230 align:start position:0% details which we're getting really close to<00:34:04.740> having<00:34:05.010> Melanie<00:34:05.340> tell<00:34:05.490> us<00:34:05.610> about<00:34:05.760> how<00:34:06.000> each 00:34:06.230 --> 00:34:06.240 align:start position:0% to having Melanie tell us about how each 00:34:06.240 --> 00:34:07.790 align:start position:0% to having Melanie tell us about how each one<00:34:06.450> point<00:34:06.750> though<00:34:06.900> is<00:34:07.080> going<00:34:07.290> to<00:34:07.410> interface 00:34:07.790 --> 00:34:07.800 align:start position:0% one point though is going to interface 00:34:07.800 --> 00:34:10.220 align:start position:0% one point though is going to interface with<00:34:07.860> either<00:34:08.129> 2.0<00:34:08.820> and<00:34:09.090> I<00:34:09.690> believe<00:34:09.960> the<00:34:10.080> latest 00:34:10.220 --> 00:34:10.230 align:start position:0% with either 2.0 and I believe the latest 00:34:10.230 --> 00:34:11.330 align:start position:0% with either 2.0 and I believe the latest answer<00:34:10.679> is<00:34:10.740> it's<00:34:10.919> going<00:34:11.010> to<00:34:11.100> be<00:34:11.190> in<00:34:11.250> an 00:34:11.330 --> 00:34:11.340 align:start position:0% answer is it's going to be in an 00:34:11.340 --> 00:34:14.690 align:start position:0% answer is it's going to be in an execution<00:34:11.610> environment<00:34:12.450> or<00:34:12.540> an<00:34:12.600> EE<00:34:13.700> which 00:34:14.690 --> 00:34:14.700 align:start position:0% execution environment or an EE which 00:34:14.700 --> 00:34:18.139 align:start position:0% execution environment or an EE which will<00:34:15.149> then<00:34:15.510> I<00:34:15.990> guess<00:34:16.770> be<00:34:17.010> decided<00:34:17.580> if<00:34:17.850> it<00:34:18.030> will 00:34:18.139 --> 00:34:18.149 align:start position:0% will then I guess be decided if it will 00:34:18.149 --> 00:34:19.530 align:start position:0% will then I guess be decided if it will go<00:34:18.600> indefinite 00:34:19.530 --> 00:34:19.540 align:start position:0% go indefinite 00:34:19.540 --> 00:34:24.690 align:start position:0% go indefinite for<00:34:20.169> a<00:34:20.200> while<00:34:20.410> stills<00:34:20.919> I<00:34:21.280> understand<00:34:23.340> it<00:34:24.340> might 00:34:24.690 --> 00:34:24.700 align:start position:0% for a while stills I understand it might 00:34:24.700 --> 00:34:27.210 align:start position:0% for a while stills I understand it might phase<00:34:25.090> out<00:34:25.300> naturally<00:34:25.960> or<00:34:26.320> there<00:34:26.860> might<00:34:27.040> be<00:34:27.070> a 00:34:27.210 --> 00:34:27.220 align:start position:0% phase out naturally or there might be a 00:34:27.220 --> 00:34:30.330 align:start position:0% phase out naturally or there might be a push<00:34:27.520> to<00:34:27.820> do<00:34:28.150> everything<00:34:28.630> from<00:34:28.900> 1.0<00:34:29.500> 2.0<00:34:30.100> where 00:34:30.330 --> 00:34:30.340 align:start position:0% push to do everything from 1.0 2.0 where 00:34:30.340 --> 00:34:32.340 align:start position:0% push to do everything from 1.0 2.0 where it'll<00:34:30.550> be<00:34:30.580> inside<00:34:31.000> chard<00:34:31.360> I've<00:34:31.960> heard<00:34:32.110> many 00:34:32.340 --> 00:34:32.350 align:start position:0% it'll be inside chard I've heard many 00:34:32.350 --> 00:34:33.570 align:start position:0% it'll be inside chard I've heard many different<00:34:32.440> things<00:34:32.860> as<00:34:33.070> they<00:34:33.160> what<00:34:33.280> happening 00:34:33.570 --> 00:34:33.580 align:start position:0% different things as they what happening 00:34:33.580 --> 00:34:38.280 align:start position:0% different things as they what happening yeah<00:34:34.620> so<00:34:35.620> my<00:34:35.860> answer<00:34:36.130> to<00:34:36.160> that<00:34:36.280> would<00:34:36.580> be<00:34:37.290> most 00:34:38.280 --> 00:34:38.290 align:start position:0% yeah so my answer to that would be most 00:34:38.290 --> 00:34:42.930 align:start position:0% yeah so my answer to that would be most likely<00:34:39.060> but<00:34:40.060> it's<00:34:40.870> really<00:34:41.080> nice<00:34:41.440> if<00:34:41.890> we<00:34:42.100> keep 00:34:42.930 --> 00:34:42.940 align:start position:0% likely but it's really nice if we keep 00:34:42.940 --> 00:34:47.159 align:start position:0% likely but it's really nice if we keep the<00:34:43.540> freedom<00:34:44.200> to<00:34:45.000> say<00:34:46.000> that<00:34:46.510> hey<00:34:46.870> we<00:34:47.080> don't 00:34:47.159 --> 00:34:47.169 align:start position:0% the freedom to say that hey we don't 00:34:47.169 --> 00:34:49.620 align:start position:0% the freedom to say that hey we don't promise<00:34:47.620> I<00:34:47.650> think<00:34:48.190> we<00:34:48.340> might<00:34:48.520> swap<00:34:48.910> out<00:34:49.090> praça 00:34:49.620 --> 00:34:49.630 align:start position:0% promise I think we might swap out praça 00:34:49.630 --> 00:34:52.169 align:start position:0% promise I think we might swap out praça we're<00:34:49.840> from<00:34:50.169> out<00:34:50.350> with<00:34:51.010> something<00:34:51.970> really 00:34:52.169 --> 00:34:52.179 align:start position:0% we're from out with something really 00:34:52.179 --> 00:34:54.510 align:start position:0% we're from out with something really silly<00:34:52.690> and<00:34:53.110> that<00:34:53.830> is<00:34:53.950> trivial<00:34:54.310> to<00:34:54.340> implement 00:34:54.510 --> 00:34:54.520 align:start position:0% silly and that is trivial to implement 00:34:54.520 --> 00:34:56.790 align:start position:0% silly and that is trivial to implement and<00:34:55.060> in<00:34:55.120> a<00:34:55.240> sec<00:34:55.480> or<00:34:56.020> we<00:34:56.200> might<00:34:56.380> do<00:34:56.560> something 00:34:56.790 --> 00:34:56.800 align:start position:0% and in a sec or we might do something 00:34:56.800 --> 00:35:00.020 align:start position:0% and in a sec or we might do something totally<00:34:57.190> different<00:34:57.430> you<00:34:58.030> never<00:34:58.750> know<00:34:58.990> just 00:35:00.020 --> 00:35:00.030 align:start position:0% totally different you never know just 00:35:00.030 --> 00:35:03.990 align:start position:0% totally different you never know just and<00:35:01.500> realistically<00:35:02.500> yeah<00:35:02.950> I<00:35:02.980> don't<00:35:03.250> think<00:35:03.580> I 00:35:03.990 --> 00:35:04.000 align:start position:0% and realistically yeah I don't think I 00:35:04.000 --> 00:35:06.270 align:start position:0% and realistically yeah I don't think I don't<00:35:04.720> think<00:35:04.900> I<00:35:05.200> mean<00:35:05.380> if<00:35:05.470> you<00:35:05.590> switch<00:35:05.770> proper 00:35:06.270 --> 00:35:06.280 align:start position:0% don't think I mean if you switch proper 00:35:06.280 --> 00:35:11.370 align:start position:0% don't think I mean if you switch proper now<00:35:06.460> I<00:35:06.790> don't<00:35:07.120> think<00:35:07.560> it<00:35:08.560> will<00:35:08.860> be<00:35:09.660> simple<00:35:10.660> to 00:35:11.370 --> 00:35:11.380 align:start position:0% now I don't think it will be simple to 00:35:11.380 --> 00:35:14.580 align:start position:0% now I don't think it will be simple to do<00:35:11.830> another<00:35:12.220> switch<00:35:12.700> later<00:35:13.440> obvious<00:35:14.440> I 00:35:14.580 --> 00:35:14.590 align:start position:0% do another switch later obvious I 00:35:14.590 --> 00:35:16.290 align:start position:0% do another switch later obvious I thought<00:35:14.800> proper<00:35:15.370> would<00:35:15.760> be<00:35:15.910> kind<00:35:16.210> of 00:35:16.290 --> 00:35:16.300 align:start position:0% thought proper would be kind of 00:35:16.300 --> 00:35:18.150 align:start position:0% thought proper would be kind of controversial<00:35:16.960> and<00:35:17.290> pretty<00:35:17.560> is<00:35:17.830> the<00:35:17.950> thing 00:35:18.150 --> 00:35:18.160 align:start position:0% controversial and pretty is the thing 00:35:18.160 --> 00:35:19.620 align:start position:0% controversial and pretty is the thing and<00:35:18.370> most<00:35:18.580> people<00:35:18.880> would<00:35:18.940> be<00:35:19.000> like<00:35:19.060> yeah 00:35:19.620 --> 00:35:19.630 align:start position:0% and most people would be like yeah 00:35:19.630 --> 00:35:20.630 align:start position:0% and most people would be like yeah whatever 00:35:20.630 --> 00:35:20.640 align:start position:0% whatever 00:35:20.640 --> 00:35:28.950 align:start position:0% whatever so<00:35:25.740> anybody<00:35:26.740> else<00:35:26.860> anything<00:35:27.460> else<00:35:27.610> okay<00:35:28.210> other 00:35:28.950 --> 00:35:28.960 align:start position:0% so anybody else anything else okay other 00:35:28.960 --> 00:35:37.270 align:start position:0% so anybody else anything else okay other questions 00:35:37.270 --> 00:35:37.280 align:start position:0% 00:35:37.280 --> 00:35:39.540 align:start position:0% yeah<00:35:37.610> I<00:35:37.640> just<00:35:37.730> I<00:35:38.090> didn't<00:35:38.420> know<00:35:38.510> if<00:35:38.690> you<00:35:39.290> know 00:35:39.540 --> 00:35:39.550 align:start position:0% yeah I just I didn't know if you know 00:35:39.550 --> 00:35:42.730 align:start position:0% yeah I just I didn't know if you know it's<00:35:40.550> gonna<00:35:40.640> turn<00:35:40.850> me<00:35:41.270> is<00:35:41.330> a<00:35:41.390> it's<00:35:41.840> a<00:35:41.930> four<00:35:42.470> core 00:35:42.730 --> 00:35:42.740 align:start position:0% it's gonna turn me is a it's a four core 00:35:42.740 --> 00:35:44.590 align:start position:0% it's gonna turn me is a it's a four core contentious<00:35:43.160> forward<00:35:43.460> so<00:35:43.700> I<00:35:44.000> mean<00:35:44.360> is<00:35:44.450> there 00:35:44.590 --> 00:35:44.600 align:start position:0% contentious forward so I mean is there 00:35:44.600 --> 00:35:46.300 align:start position:0% contentious forward so I mean is there any<00:35:44.750> evidence<00:35:44.900> and<00:35:45.440> I<00:35:45.530> apologize<00:35:46.070> I've<00:35:46.160> read 00:35:46.300 --> 00:35:46.310 align:start position:0% any evidence and I apologize I've read 00:35:46.310 --> 00:35:49.120 align:start position:0% any evidence and I apologize I've read the<00:35:46.370> report<00:35:46.670> that<00:35:47.500> eighty<00:35:48.500> six<00:35:48.710> bubble<00:35:49.010> was<00:35:49.100> a 00:35:49.120 --> 00:35:49.130 align:start position:0% the report that eighty six bubble was a 00:35:49.130 --> 00:35:50.680 align:start position:0% the report that eighty six bubble was a systemic<00:35:49.490> risk<00:35:49.850> to<00:35:50.030> the<00:35:50.120> system<00:35:50.420> where<00:35:50.570> there 00:35:50.680 --> 00:35:50.690 align:start position:0% systemic risk to the system where there 00:35:50.690 --> 00:35:52.720 align:start position:0% systemic risk to the system where there is<00:35:50.780> something<00:35:51.110> wrong<00:35:51.230> that<00:35:51.560> that<00:35:52.070> poses<00:35:52.460> to 00:35:52.720 --> 00:35:52.730 align:start position:0% is something wrong that that poses to 00:35:52.730 --> 00:35:54.310 align:start position:0% is something wrong that that poses to seventh<00:35:52.970> graders<00:35:53.270> is<00:35:53.420> just<00:35:53.660> a<00:35:53.750> really<00:35:53.870> appease 00:35:54.310 --> 00:35:54.320 align:start position:0% seventh graders is just a really appease 00:35:54.320 --> 00:35:58.090 align:start position:0% seventh graders is just a really appease the<00:35:54.560> GPU<00:35:54.920> miners<00:35:55.480> and<00:35:56.480> if<00:35:56.750> this<00:35:56.870> is<00:35:57.110> you<00:35:57.740> know<00:35:57.860> a 00:35:58.090 --> 00:35:58.100 align:start position:0% the GPU miners and if this is you know a 00:35:58.100 --> 00:35:59.950 align:start position:0% the GPU miners and if this is you know a short<00:35:58.490> term<00:35:58.670> I<00:35:59.060> think<00:35:59.210> before<00:35:59.690> we<00:35:59.900> would 00:35:59.950 --> 00:35:59.960 align:start position:0% short term I think before we would 00:35:59.960 --> 00:36:01.540 align:start position:0% short term I think before we would approve<00:36:00.230> a<00:36:00.350> stake<00:36:00.590> is<00:36:00.800> all<00:36:00.950> of<00:36:01.130> this<00:36:01.250> really 00:36:01.540 --> 00:36:01.550 align:start position:0% approve a stake is all of this really 00:36:01.550 --> 00:36:03.790 align:start position:0% approve a stake is all of this really needed<00:36:02.420> to<00:36:02.600> have<00:36:02.840> one<00:36:03.020> potential<00:36:03.440> contentious 00:36:03.790 --> 00:36:03.800 align:start position:0% needed to have one potential contentious 00:36:03.800 --> 00:36:08.440 align:start position:0% needed to have one potential contentious for<00:36:06.190> my<00:36:07.190> personal<00:36:07.610> opinions<00:36:07.880> been<00:36:08.060> developing 00:36:08.440 --> 00:36:08.450 align:start position:0% for my personal opinions been developing 00:36:08.450 --> 00:36:11.620 align:start position:0% for my personal opinions been developing over<00:36:08.540> time<00:36:08.720> on<00:36:09.320> this<00:36:09.530> and<00:36:10.390> personally<00:36:11.390> and 00:36:11.620 --> 00:36:11.630 align:start position:0% over time on this and personally and 00:36:11.630 --> 00:36:13.090 align:start position:0% over time on this and personally and this<00:36:11.780> is<00:36:11.900> not<00:36:12.020> necessarily<00:36:12.590> a<00:36:12.740> community 00:36:13.090 --> 00:36:13.100 align:start position:0% this is not necessarily a community 00:36:13.100 --> 00:36:14.320 align:start position:0% this is not necessarily a community perspective<00:36:13.280> but<00:36:13.760> one<00:36:13.970> of<00:36:14.000> the<00:36:14.180> most 00:36:14.320 --> 00:36:14.330 align:start position:0% perspective but one of the most 00:36:14.330 --> 00:36:18.160 align:start position:0% perspective but one of the most interesting<00:36:15.170> I<00:36:15.500> guess<00:36:16.310> ideas<00:36:17.240> behind<00:36:17.450> this<00:36:17.870> is 00:36:18.160 --> 00:36:18.170 align:start position:0% interesting I guess ideas behind this is 00:36:18.170 --> 00:36:20.920 align:start position:0% interesting I guess ideas behind this is the<00:36:18.350> fact<00:36:18.590> that<00:36:18.710> right<00:36:19.160> now<00:36:19.220> the<00:36:19.820> GP<00:36:20.540> mining 00:36:20.920 --> 00:36:20.930 align:start position:0% the fact that right now the GP mining 00:36:20.930 --> 00:36:23.290 align:start position:0% the fact that right now the GP mining pulls<00:36:21.170> the<00:36:21.380> major<00:36:21.590> ones<00:36:21.980> we<00:36:22.310> know<00:36:22.520> them<00:36:22.790> as 00:36:23.290 --> 00:36:23.300 align:start position:0% pulls the major ones we know them as 00:36:23.300 --> 00:36:26.110 align:start position:0% pulls the major ones we know them as then<00:36:23.630> you<00:36:24.020> can<00:36:24.200> go<00:36:24.380> to<00:36:24.410> a<00:36:25.040> chart<00:36:25.520> of<00:36:25.790> that<00:36:25.970> one 00:36:26.110 --> 00:36:26.120 align:start position:0% then you can go to a chart of that one 00:36:26.120 --> 00:36:28.720 align:start position:0% then you can go to a chart of that one either<00:36:26.300> scan<00:36:26.750> or<00:36:27.140> any<00:36:27.620> of<00:36:27.740> the<00:36:27.860> other<00:36:27.980> blog 00:36:28.720 --> 00:36:28.730 align:start position:0% either scan or any of the other blog 00:36:28.730 --> 00:36:30.610 align:start position:0% either scan or any of the other blog explorers<00:36:29.360> and<00:36:29.510> you<00:36:29.600> can<00:36:29.750> see<00:36:30.020> it<00:36:30.140> Sean<00:36:30.410> pie 00:36:30.610 --> 00:36:30.620 align:start position:0% explorers and you can see it Sean pie 00:36:30.620 --> 00:36:33.310 align:start position:0% explorers and you can see it Sean pie chart<00:36:30.920> it<00:36:31.040> says<00:36:31.280> like<00:36:31.520> either<00:36:31.790> mine<00:36:32.180> and<00:36:32.570> F<00:36:33.020> to 00:36:33.310 --> 00:36:33.320 align:start position:0% chart it says like either mine and F to 00:36:33.320 --> 00:36:36.580 align:start position:0% chart it says like either mine and F to pool<00:36:33.560> and<00:36:33.890> spark<00:36:34.220> pool<00:36:34.430> and<00:36:34.760> so<00:36:35.720> we<00:36:36.020> know<00:36:36.290> them 00:36:36.580 --> 00:36:36.590 align:start position:0% pool and spark pool and so we know them 00:36:36.590 --> 00:36:38.470 align:start position:0% pool and spark pool and so we know them we<00:36:36.980> know<00:36:37.160> that<00:36:37.430> spark<00:36:37.760> pulls<00:36:38.030> helped<00:36:38.330> out<00:36:38.450> in 00:36:38.470 --> 00:36:38.480 align:start position:0% we know that spark pulls helped out in 00:36:38.480 --> 00:36:40.450 align:start position:0% we know that spark pulls helped out in the<00:36:38.630> community<00:36:39.080> we<00:36:39.350> know<00:36:39.470> that<00:36:39.710> F<00:36:39.890> two<00:36:40.190> pool 00:36:40.450 --> 00:36:40.460 align:start position:0% the community we know that F two pool 00:36:40.460 --> 00:36:42.430 align:start position:0% the community we know that F two pool has<00:36:40.640> helped<00:36:40.940> out<00:36:41.090> a<00:36:41.120> little<00:36:41.420> bit<00:36:41.690> and<00:36:42.230> we<00:36:42.320> know 00:36:42.430 --> 00:36:42.440 align:start position:0% has helped out a little bit and we know 00:36:42.440 --> 00:36:45.940 align:start position:0% has helped out a little bit and we know that<00:36:42.560> ether<00:36:42.800> mines<00:36:42.980> help<00:36:43.220> out<00:36:43.400> a<00:36:43.640> lot<00:36:44.740> with<00:36:45.740> the 00:36:45.940 --> 00:36:45.950 align:start position:0% that ether mines help out a lot with the 00:36:45.950 --> 00:36:47.530 align:start position:0% that ether mines help out a lot with the technical<00:36:46.400> stuff<00:36:46.580> so<00:36:46.730> I<00:36:46.760> guess<00:36:47.060> either<00:36:47.330> might 00:36:47.530 --> 00:36:47.540 align:start position:0% technical stuff so I guess either might 00:36:47.540 --> 00:36:49.450 align:start position:0% technical stuff so I guess either might would<00:36:47.600> be<00:36:47.720> more<00:36:47.870> technical<00:36:48.170> help<00:36:48.560> smart<00:36:49.280> pool 00:36:49.450 --> 00:36:49.460 align:start position:0% would be more technical help smart pool 00:36:49.460 --> 00:36:50.620 align:start position:0% would be more technical help smart pool would<00:36:49.520> be<00:36:49.580> both<00:36:49.850> technical<00:36:50.360> and<00:36:50.480> community 00:36:50.620 --> 00:36:50.630 align:start position:0% would be both technical and community 00:36:50.630 --> 00:36:54.310 align:start position:0% would be both technical and community help<00:36:51.110> with<00:36:51.290> their<00:36:51.500> initiatives<00:36:52.460> to<00:36:52.610> do<00:36:53.320> stuff 00:36:54.310 --> 00:36:54.320 align:start position:0% help with their initiatives to do stuff 00:36:54.320 --> 00:36:57.670 align:start position:0% help with their initiatives to do stuff in<00:36:54.500> the<00:36:54.530> ecosystem<00:36:55.340> when<00:36:55.550> I<00:36:56.150> was<00:36:57.110> a<00:36:57.140> co-working 00:36:57.670 --> 00:36:57.680 align:start position:0% in the ecosystem when I was a co-working 00:36:57.680 --> 00:37:01.049 align:start position:0% in the ecosystem when I was a co-working spaces<00:36:58.100> in<00:36:58.400> China<00:36:58.700> and<00:36:59.650> conferences 00:37:01.049 --> 00:37:01.059 align:start position:0% spaces in China and conferences 00:37:01.059 --> 00:37:03.749 align:start position:0% spaces in China and conferences educational<00:37:02.049> sessions<00:37:02.529> so<00:37:03.219> we<00:37:03.249> know<00:37:03.609> they're 00:37:03.749 --> 00:37:03.759 align:start position:0% educational sessions so we know they're 00:37:03.759 --> 00:37:05.549 align:start position:0% educational sessions so we know they're all<00:37:03.880> good<00:37:04.059> actors<00:37:04.449> the<00:37:04.659> thing<00:37:04.839> with<00:37:05.079> that<00:37:05.380> I 00:37:05.549 --> 00:37:05.559 align:start position:0% all good actors the thing with that I 00:37:05.559 --> 00:37:07.229 align:start position:0% all good actors the thing with that I always<00:37:05.769> think<00:37:05.979> back<00:37:06.099> to<00:37:06.339> this<00:37:06.400> myth<00:37:06.669> an<00:37:07.029> era 00:37:07.229 --> 00:37:07.239 align:start position:0% always think back to this myth an era 00:37:07.239 --> 00:37:09.839 align:start position:0% always think back to this myth an era when<00:37:07.799> suddenly<00:37:08.799> there<00:37:08.979> was<00:37:09.039> a<00:37:09.099> lot<00:37:09.459> of<00:37:09.489> hash 00:37:09.839 --> 00:37:09.849 align:start position:0% when suddenly there was a lot of hash 00:37:09.849 --> 00:37:11.909 align:start position:0% when suddenly there was a lot of hash rate<00:37:10.179> that<00:37:10.659> dropped<00:37:10.929> off<00:37:11.109> after<00:37:11.349> the<00:37:11.619> fork 00:37:11.909 --> 00:37:11.919 align:start position:0% rate that dropped off after the fork 00:37:11.919 --> 00:37:13.559 align:start position:0% rate that dropped off after the fork that<00:37:12.130> we<00:37:12.219> hadn't<00:37:12.489> no<00:37:12.549> idea<00:37:12.819> who<00:37:12.939> they<00:37:13.059> were<00:37:13.119> and 00:37:13.559 --> 00:37:13.569 align:start position:0% that we hadn't no idea who they were and 00:37:13.569 --> 00:37:15.689 align:start position:0% that we hadn't no idea who they were and they<00:37:14.109> didn't<00:37:14.439> know<00:37:14.559> there<00:37:14.739> was<00:37:14.859> a<00:37:14.890> Benares<00:37:15.400> and 00:37:15.689 --> 00:37:15.699 align:start position:0% they didn't know there was a Benares and 00:37:15.699 --> 00:37:17.849 align:start position:0% they didn't know there was a Benares and it<00:37:15.759> wasn't<00:37:15.939> public<00:37:16.449> so<00:37:17.049> someone<00:37:17.469> built<00:37:17.739> an 00:37:17.849 --> 00:37:17.859 align:start position:0% it wasn't public so someone built an 00:37:17.859 --> 00:37:19.769 align:start position:0% it wasn't public so someone built an ease<00:37:17.979> that<00:37:18.009> they<00:37:18.759> started<00:37:19.089> mining<00:37:19.419> on<00:37:19.539> there 00:37:19.769 --> 00:37:19.779 align:start position:0% ease that they started mining on there 00:37:19.779 --> 00:37:21.659 align:start position:0% ease that they started mining on there and<00:37:20.019> so<00:37:20.529> they<00:37:20.709> could<00:37:20.890> basically<00:37:21.099> do<00:37:21.489> whatever 00:37:21.659 --> 00:37:21.669 align:start position:0% and so they could basically do whatever 00:37:21.669 --> 00:37:24.329 align:start position:0% and so they could basically do whatever they<00:37:21.909> wanted<00:37:22.119> to<00:37:22.239> anonymously<00:37:22.809> so<00:37:23.679> as<00:37:23.890> we<00:37:24.099> know 00:37:24.329 --> 00:37:24.339 align:start position:0% they wanted to anonymously so as we know 00:37:24.339 --> 00:37:26.219 align:start position:0% they wanted to anonymously so as we know all<00:37:24.369> the<00:37:24.549> actors<00:37:24.849> now<00:37:25.119> if<00:37:25.390> smart<00:37:25.689> people<00:37:25.959> tried 00:37:26.219 --> 00:37:26.229 align:start position:0% all the actors now if smart people tried 00:37:26.229 --> 00:37:28.620 align:start position:0% all the actors now if smart people tried to<00:37:26.259> do<00:37:26.469> a<00:37:26.499> double<00:37:26.859> spend<00:37:27.130> or<00:37:27.429> they<00:37:27.699> tried<00:37:28.029> to<00:37:28.059> I 00:37:28.620 --> 00:37:28.630 align:start position:0% to do a double spend or they tried to I 00:37:28.630 --> 00:37:30.569 align:start position:0% to do a double spend or they tried to I used<00:37:29.199> to<00:37:29.289> think<00:37:29.499> there<00:37:29.679> might<00:37:29.859> be<00:37:29.919> a<00:37:30.069> way<00:37:30.279> that 00:37:30.569 --> 00:37:30.579 align:start position:0% used to think there might be a way that 00:37:30.579 --> 00:37:31.919 align:start position:0% used to think there might be a way that like<00:37:30.729> they<00:37:30.939> could<00:37:31.059> mess<00:37:31.239> up<00:37:31.269> that's<00:37:31.539> you<00:37:31.689> point 00:37:31.919 --> 00:37:31.929 align:start position:0% like they could mess up that's you point 00:37:31.929 --> 00:37:33.659 align:start position:0% like they could mess up that's you point out<00:37:31.989> a<00:37:32.049> transition<00:37:32.619> that<00:37:32.650> is<00:37:32.979> less<00:37:33.219> likely<00:37:33.249> now 00:37:33.659 --> 00:37:33.669 align:start position:0% out a transition that is less likely now 00:37:33.669 --> 00:37:37.079 align:start position:0% out a transition that is less likely now after<00:37:33.969> talking<00:37:34.179> to<00:37:34.329> Danny<00:37:34.539> Ryan<00:37:35.019> but<00:37:36.089> there 00:37:37.079 --> 00:37:37.089 align:start position:0% after talking to Danny Ryan but there 00:37:37.089 --> 00:37:39.449 align:start position:0% after talking to Danny Ryan but there are<00:37:37.239> some<00:37:37.479> things<00:37:37.719> that<00:37:37.809> an<00:37:38.259> anonymous<00:37:38.589> large 00:37:39.449 --> 00:37:39.459 align:start position:0% are some things that an anonymous large 00:37:39.459 --> 00:37:41.789 align:start position:0% are some things that an anonymous large percentage<00:37:40.150> of<00:37:40.209> hash<00:37:40.479> power<00:37:40.749> could<00:37:41.049> do<00:37:41.319> like 00:37:41.789 --> 00:37:41.799 align:start position:0% percentage of hash power could do like 00:37:41.799 --> 00:37:43.559 align:start position:0% percentage of hash power could do like double<00:37:42.159> spending<00:37:42.579> right<00:37:42.939> before<00:37:43.359> because 00:37:43.559 --> 00:37:43.569 align:start position:0% double spending right before because 00:37:43.569 --> 00:37:44.999 align:start position:0% double spending right before because they<00:37:43.689> know<00:37:43.809> that<00:37:43.839> their<00:37:44.169> investments<00:37:44.859> about 00:37:44.999 --> 00:37:45.009 align:start position:0% they know that their investments about 00:37:45.009 --> 00:37:47.579 align:start position:0% they know that their investments about to<00:37:45.130> drop<00:37:45.309> off<00:37:45.459> completely<00:37:45.909> GPU<00:37:46.900> miners<00:37:47.289> can 00:37:47.579 --> 00:37:47.589 align:start position:0% to drop off completely GPU miners can 00:37:47.589 --> 00:37:50.759 align:start position:0% to drop off completely GPU miners can switch<00:37:47.919> to<00:37:48.279> other<00:37:48.640> algorithms<00:37:49.319> Asics<00:37:50.319> they're 00:37:50.759 --> 00:37:50.769 align:start position:0% switch to other algorithms Asics they're 00:37:50.769 --> 00:37:52.829 align:start position:0% switch to other algorithms Asics they're stuck<00:37:51.309> on<00:37:51.489> ET<00:37:51.759> cash<00:37:52.029> nor<00:37:52.269> they're<00:37:52.479> stuck<00:37:52.719> on 00:37:52.829 --> 00:37:52.839 align:start position:0% stuck on ET cash nor they're stuck on 00:37:52.839 --> 00:37:55.169 align:start position:0% stuck on ET cash nor they're stuck on product<00:37:53.229> pal<00:37:53.380> so<00:37:54.189> it's<00:37:54.459> more<00:37:54.609> the<00:37:54.759> only<00:37:54.999> major 00:37:55.169 --> 00:37:55.179 align:start position:0% product pal so it's more the only major 00:37:55.179 --> 00:37:57.630 align:start position:0% product pal so it's more the only major what<00:37:55.479> implemented<00:37:55.929> prog<00:37:56.169> pala<00:37:56.499> then<00:37:56.859> what<00:37:57.579> do 00:37:57.630 --> 00:37:57.640 align:start position:0% what implemented prog pala then what do 00:37:57.640 --> 00:37:58.709 align:start position:0% what implemented prog pala then what do you<00:37:57.699> what<00:37:57.849> do<00:37:57.909> they<00:37:57.999> have<00:37:58.119> to<00:37:58.269> lose<00:37:58.419> if<00:37:58.599> you're 00:37:58.709 --> 00:37:58.719 align:start position:0% you what do they have to lose if you're 00:37:58.719 --> 00:38:00.269 align:start position:0% you what do they have to lose if you're anonymous<00:37:58.959> and<00:37:59.559> just<00:37:59.739> want<00:37:59.890> to<00:37:59.949> do<00:38:00.039> a<00:38:00.069> double 00:38:00.269 --> 00:38:00.279 align:start position:0% anonymous and just want to do a double 00:38:00.279 --> 00:38:01.890 align:start position:0% anonymous and just want to do a double spend<00:38:00.640> on<00:38:00.729> an<00:38:00.819> exchange<00:38:01.059> because<00:38:01.479> our 00:38:01.890 --> 00:38:01.900 align:start position:0% spend on an exchange because our 00:38:01.900 --> 00:38:03.959 align:start position:0% spend on an exchange because our conformation<00:38:02.559> times<00:38:02.739> are<00:38:02.890> much<00:38:03.009> lower<00:38:03.249> so 00:38:03.959 --> 00:38:03.969 align:start position:0% conformation times are much lower so 00:38:03.969 --> 00:38:05.939 align:start position:0% conformation times are much lower so that's<00:38:04.150> the<00:38:04.359> best<00:38:04.659> argument<00:38:05.409> I've<00:38:05.529> heard<00:38:05.739> so 00:38:05.939 --> 00:38:05.949 align:start position:0% that's the best argument I've heard so 00:38:05.949 --> 00:38:10.079 align:start position:0% that's the best argument I've heard so far<00:38:05.979> in<00:38:06.489> favor<00:38:06.729> of<00:38:07.209> prog<00:38:08.049> pound<00:38:08.289> so<00:38:09.159> that's 00:38:10.079 --> 00:38:10.089 align:start position:0% far in favor of prog pound so that's 00:38:10.089 --> 00:38:12.179 align:start position:0% far in favor of prog pound so that's kind<00:38:10.569> of<00:38:10.659> where<00:38:10.900> I<00:38:11.169> met<00:38:11.529> as<00:38:11.650> far<00:38:11.829> as<00:38:11.890> a<00:38:11.979> good 00:38:12.179 --> 00:38:12.189 align:start position:0% kind of where I met as far as a good 00:38:12.189 --> 00:38:13.439 align:start position:0% kind of where I met as far as a good arguments<00:38:12.669> ago 00:38:13.439 --> 00:38:13.449 align:start position:0% arguments ago 00:38:13.449 --> 00:38:18.179 align:start position:0% arguments ago and<00:38:13.809> the<00:38:13.959> fact<00:38:14.169> that<00:38:14.319> I<00:38:15.099> knew<00:38:16.769> shoot<00:38:17.769> down<00:38:18.009> the 00:38:18.179 --> 00:38:18.189 align:start position:0% and the fact that I knew shoot down the 00:38:18.189 --> 00:38:22.949 align:start position:0% and the fact that I knew shoot down the idea<00:38:18.519> that<00:38:20.159> we<00:38:21.159> made<00:38:21.489> a<00:38:21.519> deal<00:38:21.759> with<00:38:22.059> GPU<00:38:22.509> miners 00:38:22.949 --> 00:38:22.959 align:start position:0% idea that we made a deal with GPU miners 00:38:22.959 --> 00:38:25.829 align:start position:0% idea that we made a deal with GPU miners or<00:38:23.199> that<00:38:23.439> because<00:38:23.679> of<00:38:24.039> the<00:38:24.839> issuance 00:38:25.829 --> 00:38:25.839 align:start position:0% or that because of the issuance 00:38:25.839 --> 00:38:27.059 align:start position:0% or that because of the issuance reduction<00:38:26.439> that<00:38:26.619> there<00:38:26.769> was<00:38:26.890> this 00:38:27.059 --> 00:38:27.069 align:start position:0% reduction that there was this 00:38:27.069 --> 00:38:28.920 align:start position:0% reduction that there was this implication<00:38:27.999> that<00:38:28.449> we<00:38:28.630> would 00:38:28.920 --> 00:38:28.930 align:start position:0% implication that we would 00:38:28.930 --> 00:38:30.569 align:start position:0% implication that we would doing<00:38:29.290> wrong<00:38:29.500> pal<00:38:29.829> because<00:38:30.099> I<00:38:30.250> know<00:38:30.309> at<00:38:30.490> the 00:38:30.569 --> 00:38:30.579 align:start position:0% doing wrong pal because I know at the 00:38:30.579 --> 00:38:32.040 align:start position:0% doing wrong pal because I know at the time<00:38:30.760> there<00:38:30.970> was<00:38:31.059> some<00:38:31.240> people<00:38:31.390> saying<00:38:31.780> that 00:38:32.040 --> 00:38:32.050 align:start position:0% time there was some people saying that 00:38:32.050 --> 00:38:34.980 align:start position:0% time there was some people saying that but<00:38:32.650> I<00:38:32.710> did<00:38:33.010> a<00:38:33.040> huge<00:38:33.490> block<00:38:33.849> reddit<00:38:34.510> post<00:38:34.720> that 00:38:34.980 --> 00:38:34.990 align:start position:0% but I did a huge block reddit post that 00:38:34.990 --> 00:38:36.990 align:start position:0% but I did a huge block reddit post that kind<00:38:35.260> of<00:38:35.380> dispelled<00:38:36.309> that<00:38:36.400> and<00:38:36.700> included 00:38:36.990 --> 00:38:37.000 align:start position:0% kind of dispelled that and included 00:38:37.000 --> 00:38:38.940 align:start position:0% kind of dispelled that and included timestamps<00:38:37.660> -<00:38:37.780> core<00:38:37.960> developer<00:38:38.380> calls<00:38:38.619> and 00:38:38.940 --> 00:38:38.950 align:start position:0% timestamps - core developer calls and 00:38:38.950 --> 00:38:40.470 align:start position:0% timestamps - core developer calls and things<00:38:39.130> like<00:38:39.339> that<00:38:39.609> where<00:38:39.790> we<00:38:39.819> discussed<00:38:40.300> not 00:38:40.470 --> 00:38:40.480 align:start position:0% things like that where we discussed not 00:38:40.480 --> 00:38:43.920 align:start position:0% things like that where we discussed not doing<00:38:40.809> that<00:38:40.960> so<00:38:42.150> as<00:38:43.150> far<00:38:43.359> as<00:38:43.420> this<00:38:43.599> is<00:38:43.809> there 00:38:43.920 --> 00:38:43.930 align:start position:0% doing that so as far as this is there 00:38:43.930 --> 00:38:45.900 align:start position:0% doing that so as far as this is there going<00:38:44.050> to<00:38:44.079> be<00:38:44.140> a<00:38:44.200> fork<00:38:44.470> or<00:38:44.559> not<00:38:44.730> there's<00:38:45.730> no<00:38:45.880> way 00:38:45.900 --> 00:38:45.910 align:start position:0% going to be a fork or not there's no way 00:38:45.910 --> 00:38:48.960 align:start position:0% going to be a fork or not there's no way to<00:38:46.059> know<00:38:46.410> and<00:38:47.410> it's<00:38:47.710> going<00:38:47.859> to<00:38:47.950> depend<00:38:48.040> on<00:38:48.579> I 00:38:48.960 --> 00:38:48.970 align:start position:0% to know and it's going to depend on I 00:38:48.970 --> 00:38:51.960 align:start position:0% to know and it's going to depend on I guess<00:38:49.869> my<00:38:50.349> main<00:38:50.950> opinion<00:38:51.339> on<00:38:51.460> a<00:38:51.490> personal 00:38:51.960 --> 00:38:51.970 align:start position:0% guess my main opinion on a personal 00:38:51.970 --> 00:38:53.819 align:start position:0% guess my main opinion on a personal level<00:38:52.000> is<00:38:52.300> that<00:38:52.420> there<00:38:52.569> won't<00:38:52.780> be<00:38:52.869> because<00:38:53.170> to 00:38:53.819 --> 00:38:53.829 align:start position:0% level is that there won't be because to 00:38:53.829 --> 00:38:56.069 align:start position:0% level is that there won't be because to have<00:38:53.920> a<00:38:53.980> successful<00:38:54.730> court<00:38:55.180> you<00:38:55.809> need<00:38:55.990> a 00:38:56.069 --> 00:38:56.079 align:start position:0% have a successful court you need a 00:38:56.079 --> 00:38:59.549 align:start position:0% have a successful court you need a dedicated<00:38:56.260> team<00:38:56.859> of<00:38:57.119> developers<00:38:58.119> who<00:38:58.809> can<00:38:58.990> at 00:38:59.549 --> 00:38:59.559 align:start position:0% dedicated team of developers who can at 00:38:59.559 --> 00:39:02.670 align:start position:0% dedicated team of developers who can at least<00:38:59.800> code<00:39:00.250> one<00:39:00.520> client<00:39:00.819> and<00:39:01.500> there<00:39:02.500> would<00:39:02.650> be 00:39:02.670 --> 00:39:02.680 align:start position:0% least code one client and there would be 00:39:02.680 --> 00:39:06.390 align:start position:0% least code one client and there would be people<00:39:02.829> maybe<00:39:03.250> from<00:39:03.520> PTC<00:39:03.940> or<00:39:04.680> other<00:39:05.680> ports<00:39:06.280> of 00:39:06.390 --> 00:39:06.400 align:start position:0% people maybe from PTC or other ports of 00:39:06.400 --> 00:39:09.089 align:start position:0% people maybe from PTC or other ports of aetherium<00:39:06.760> that<00:39:07.059> can<00:39:07.180> pick<00:39:07.300> that<00:39:07.450> up<00:39:07.800> but<00:39:08.800> I 00:39:09.089 --> 00:39:09.099 align:start position:0% aetherium that can pick that up but I 00:39:09.099 --> 00:39:10.620 align:start position:0% aetherium that can pick that up but I don't<00:39:09.280> see<00:39:09.490> any<00:39:09.700> of<00:39:09.790> them<00:39:09.910> speaking<00:39:10.210> up<00:39:10.420> right 00:39:10.620 --> 00:39:10.630 align:start position:0% don't see any of them speaking up right 00:39:10.630 --> 00:39:12.420 align:start position:0% don't see any of them speaking up right now<00:39:10.809> maybe<00:39:11.140> if<00:39:11.290> it<00:39:11.410> gets<00:39:11.530> closer<00:39:11.829> so<00:39:12.250> most 00:39:12.420 --> 00:39:12.430 align:start position:0% now maybe if it gets closer so most 00:39:12.430 --> 00:39:14.760 align:start position:0% now maybe if it gets closer so most become<00:39:12.760> and<00:39:13.030> they'll<00:39:13.119> say<00:39:13.359> yeah<00:39:14.290> we're<00:39:14.530> ready 00:39:14.760 --> 00:39:14.770 align:start position:0% become and they'll say yeah we're ready 00:39:14.770 --> 00:39:16.620 align:start position:0% become and they'll say yeah we're ready to<00:39:15.010> take<00:39:15.250> on<00:39:15.430> a<00:39:15.460> work<00:39:15.760> of<00:39:15.910> this<00:39:16.089> and<00:39:16.420> we're 00:39:16.620 --> 00:39:16.630 align:start position:0% to take on a work of this and we're 00:39:16.630 --> 00:39:18.569 align:start position:0% to take on a work of this and we're married<00:39:17.079> we're<00:39:17.260> against<00:39:17.500> this<00:39:17.680> so<00:39:17.980> much<00:39:18.190> it's 00:39:18.569 --> 00:39:18.579 align:start position:0% married we're against this so much it's 00:39:18.579 --> 00:39:19.799 align:start position:0% married we're against this so much it's the<00:39:18.700> principles<00:39:19.150> of<00:39:19.300> it<00:39:19.420> that<00:39:19.510> we're<00:39:19.630> going<00:39:19.720> to 00:39:19.799 --> 00:39:19.809 align:start position:0% the principles of it that we're going to 00:39:19.809 --> 00:39:21.780 align:start position:0% the principles of it that we're going to do<00:39:19.900> it<00:39:20.050> but<00:39:20.170> I<00:39:20.260> just<00:39:20.319> haven't<00:39:21.160> seen<00:39:21.400> that<00:39:21.579> yet 00:39:21.780 --> 00:39:21.790 align:start position:0% do it but I just haven't seen that yet 00:39:21.790 --> 00:39:24.210 align:start position:0% do it but I just haven't seen that yet so<00:39:22.059> it's<00:39:22.210> hard<00:39:22.420> for<00:39:22.569> me<00:39:22.690> to<00:39:22.780> believe<00:39:23.220> people 00:39:24.210 --> 00:39:24.220 align:start position:0% so it's hard for me to believe people 00:39:24.220 --> 00:39:26.099 align:start position:0% so it's hard for me to believe people underestimated<00:39:24.849> that<00:39:24.970> with<00:39:25.119> e.t.c<00:39:25.630> we<00:39:25.960> had 00:39:26.099 --> 00:39:26.109 align:start position:0% underestimated that with e.t.c we had 00:39:26.109 --> 00:39:28.260 align:start position:0% underestimated that with e.t.c we had never<00:39:26.290> had<00:39:26.500> that<00:39:26.530> before<00:39:26.680> again<00:39:27.250> so<00:39:27.579> I'm<00:39:28.030> not 00:39:28.260 --> 00:39:28.270 align:start position:0% never had that before again so I'm not 00:39:28.270 --> 00:39:29.730 align:start position:0% never had that before again so I'm not saying<00:39:28.540> it's<00:39:28.690> impossible<00:39:28.960> at<00:39:29.349> all<00:39:29.470> it's 00:39:29.730 --> 00:39:29.740 align:start position:0% saying it's impossible at all it's 00:39:29.740 --> 00:39:31.559 align:start position:0% saying it's impossible at all it's definitely<00:39:30.280> possible<00:39:30.520> but<00:39:31.000> I<00:39:31.210> don't<00:39:31.359> know<00:39:31.450> the 00:39:31.559 --> 00:39:31.569 align:start position:0% definitely possible but I don't know the 00:39:31.569 --> 00:39:34.020 align:start position:0% definitely possible but I don't know the percentage<00:39:31.869> right<00:39:32.200> now<00:39:32.319> a<00:39:32.349> possibility<00:39:33.000> no<00:39:34.000> I 00:39:34.020 --> 00:39:34.030 align:start position:0% percentage right now a possibility no I 00:39:34.030 --> 00:39:35.819 align:start position:0% percentage right now a possibility no I mean<00:39:34.210> if<00:39:34.780> that<00:39:34.900> did<00:39:35.109> happen<00:39:35.140> I'd<00:39:35.530> see<00:39:35.799> that 00:39:35.819 --> 00:39:35.829 align:start position:0% mean if that did happen I'd see that 00:39:35.829 --> 00:39:37.920 align:start position:0% mean if that did happen I'd see that arising<00:39:36.579> organically<00:39:37.180> in<00:39:37.299> that<00:39:37.450> same<00:39:37.690> point 00:39:37.920 --> 00:39:37.930 align:start position:0% arising organically in that same point 00:39:37.930 --> 00:39:43.440 align:start position:0% arising organically in that same point of<00:39:38.109> e.t.c<00:39:40.500> find<00:39:41.500> a<00:39:41.559> way<00:39:41.740> yet<00:39:42.549> is<00:39:42.760> that<00:39:42.790> there's 00:39:43.440 --> 00:39:43.450 align:start position:0% of e.t.c find a way yet is that there's 00:39:43.450 --> 00:39:47.520 align:start position:0% of e.t.c find a way yet is that there's a<00:39:43.540> lot<00:39:43.930> of<00:39:43.960> people<00:39:44.410> who<00:39:44.619> can<00:39:45.549> fork<00:39:46.420> a<00:39:46.569> repo<00:39:47.020> can 00:39:47.520 --> 00:39:47.530 align:start position:0% a lot of people who can fork a repo can 00:39:47.530 --> 00:39:50.700 align:start position:0% a lot of people who can fork a repo can run<00:39:48.420> continuous<00:39:49.420> integration<00:39:49.690> can<00:39:50.349> tweak 00:39:50.700 --> 00:39:50.710 align:start position:0% run continuous integration can tweak 00:39:50.710 --> 00:39:53.329 align:start position:0% run continuous integration can tweak parameters<00:39:51.119> may<00:39:52.119> not<00:39:52.299> have<00:39:52.510> the<00:39:52.630> ability<00:39:53.079> to 00:39:53.329 --> 00:39:53.339 align:start position:0% parameters may not have the ability to 00:39:53.339 --> 00:39:55.770 align:start position:0% parameters may not have the ability to move<00:39:54.339> them<00:39:54.579> you<00:39:55.150> know<00:39:55.240> improve<00:39:55.510> things<00:39:55.630> for 00:39:55.770 --> 00:39:55.780 align:start position:0% move them you know improve things for 00:39:55.780 --> 00:39:57.450 align:start position:0% move them you know improve things for much<00:39:56.200> beyond<00:39:56.559> that<00:39:56.589> that<00:39:56.980> they<00:39:57.099> can<00:39:57.160> at<00:39:57.339> least 00:39:57.450 --> 00:39:57.460 align:start position:0% much beyond that that they can at least 00:39:57.460 --> 00:39:59.819 align:start position:0% much beyond that that they can at least keep<00:39:57.700> the<00:39:57.849> network<00:39:58.030> going<00:39:58.390> they<00:39:59.049> can<00:39:59.530> do<00:39:59.799> a 00:39:59.819 --> 00:39:59.829 align:start position:0% keep the network going they can do a 00:39:59.829 --> 00:40:04.440 align:start position:0% keep the network going they can do a simple<00:40:00.130> and<00:40:00.910> then<00:40:01.290> hope<00:40:02.290> together<00:40:03.359> you<00:40:04.359> know 00:40:04.440 --> 00:40:04.450 align:start position:0% simple and then hope together you know 00:40:04.450 --> 00:40:06.180 align:start position:0% simple and then hope together you know that<00:40:04.480> I'll<00:40:04.839> be<00:40:05.020> behind<00:40:05.170> that<00:40:05.500> that's<00:40:05.799> how<00:40:06.010> I'd 00:40:06.180 --> 00:40:06.190 align:start position:0% that I'll be behind that that's how I'd 00:40:06.190 --> 00:40:08.579 align:start position:0% that I'll be behind that that's how I'd see<00:40:06.660> yeah<00:40:07.660> you<00:40:07.869> know<00:40:08.020> that<00:40:08.200> contention 00:40:08.579 --> 00:40:08.589 align:start position:0% see yeah you know that contention 00:40:08.589 --> 00:40:10.260 align:start position:0% see yeah you know that contention happening<00:40:09.130> they<00:40:09.460> could<00:40:09.670> happen<00:40:09.970> it<00:40:10.059> on<00:40:10.180> the 00:40:10.260 --> 00:40:10.270 align:start position:0% happening they could happen it on the 00:40:10.270 --> 00:40:11.359 align:start position:0% happening they could happen it on the other<00:40:10.329> direction 00:40:11.359 --> 00:40:11.369 align:start position:0% other direction 00:40:11.369 --> 00:40:14.400 align:start position:0% other direction there<00:40:12.369> was<00:40:12.520> actually<00:40:12.700> code<00:40:13.319> there<00:40:14.319> was 00:40:14.400 --> 00:40:14.410 align:start position:0% there was actually code there was 00:40:14.410 --> 00:40:15.809 align:start position:0% there was actually code there was actually<00:40:14.740> a<00:40:14.799> developer<00:40:15.309> who<00:40:15.430> was<00:40:15.549> on<00:40:15.730> the 00:40:15.809 --> 00:40:15.819 align:start position:0% actually a developer who was on the 00:40:15.819 --> 00:40:18.000 align:start position:0% actually a developer who was on the discourse<00:40:16.240> back<00:40:16.930> in<00:40:17.109> january/february<00:40:17.890> who 00:40:18.000 --> 00:40:18.010 align:start position:0% discourse back in january/february who 00:40:18.010 --> 00:40:20.190 align:start position:0% discourse back in january/february who was<00:40:18.130> about<00:40:18.400> to<00:40:18.579> do<00:40:18.760> a<00:40:18.790> prog<00:40:19.240> how<00:40:19.450> four<00:40:19.780> can<00:40:19.990> head 00:40:20.190 --> 00:40:20.200 align:start position:0% was about to do a prog how four can head 00:40:20.200 --> 00:40:22.260 align:start position:0% was about to do a prog how four can head code<00:40:20.440> ready<00:40:20.680> and<00:40:20.920> Bates<00:40:21.160> picked<00:40:21.460> I<00:40:21.700> don't<00:40:22.180> know 00:40:22.260 --> 00:40:22.270 align:start position:0% code ready and Bates picked I don't know 00:40:22.270 --> 00:40:23.400 align:start position:0% code ready and Bates picked I don't know why<00:40:22.450> he<00:40:22.599> backed<00:40:22.809> off<00:40:22.990> they<00:40:23.200> would<00:40:23.349> be 00:40:23.400 --> 00:40:23.410 align:start position:0% why he backed off they would be 00:40:23.410 --> 00:40:25.680 align:start position:0% why he backed off they would be persuaded<00:40:23.890> him<00:40:24.040> the<00:40:24.460> Bronco<00:40:24.910> wasn't<00:40:25.210> dead<00:40:25.390> but 00:40:25.680 --> 00:40:25.690 align:start position:0% persuaded him the Bronco wasn't dead but 00:40:25.690 --> 00:40:27.660 align:start position:0% persuaded him the Bronco wasn't dead but he<00:40:26.230> was<00:40:26.349> very<00:40:26.440> committed<00:40:27.099> to<00:40:27.130> make<00:40:27.339> it<00:40:27.490> happen 00:40:27.660 --> 00:40:27.670 align:start position:0% he was very committed to make it happen 00:40:27.670 --> 00:40:29.430 align:start position:0% he was very committed to make it happen so<00:40:27.819> he<00:40:28.030> actually<00:40:28.180> had<00:40:28.480> code<00:40:28.720> in<00:40:28.869> place<00:40:29.020> and 00:40:29.430 --> 00:40:29.440 align:start position:0% so he actually had code in place and 00:40:29.440 --> 00:40:31.079 align:start position:0% so he actually had code in place and people<00:40:29.980> in<00:40:30.220> place<00:40:30.430> and<00:40:30.609> connections<00:40:31.000> to 00:40:31.079 --> 00:40:31.089 align:start position:0% people in place and connections to 00:40:31.089 --> 00:40:33.059 align:start position:0% people in place and connections to actually<00:40:31.420> or<00:40:32.049> he<00:40:32.410> was<00:40:32.559> really<00:40:32.740> good<00:40:32.980> at 00:40:33.059 --> 00:40:33.069 align:start position:0% actually or he was really good at 00:40:33.069 --> 00:40:34.950 align:start position:0% actually or he was really good at bluffing<00:40:33.250> it's<00:40:33.520> hard<00:40:33.700> to<00:40:33.760> tell<00:40:33.970> but<00:40:34.690> that<00:40:34.839> an 00:40:34.950 --> 00:40:34.960 align:start position:0% bluffing it's hard to tell but that an 00:40:34.960 --> 00:40:36.720 align:start position:0% bluffing it's hard to tell but that an actual<00:40:35.200> work<00:40:35.500> the<00:40:36.369> other<00:40:36.460> thing<00:40:36.700> that 00:40:36.720 --> 00:40:36.730 align:start position:0% actual work the other thing that 00:40:36.730 --> 00:40:40.440 align:start position:0% actual work the other thing that happened<00:40:38.790> is<00:40:39.790> that<00:40:39.819> there<00:40:40.089> was<00:40:40.210> another 00:40:40.440 --> 00:40:40.450 align:start position:0% happened is that there was another 00:40:40.450 --> 00:40:42.870 align:start position:0% happened is that there was another proposal<00:40:41.109> which<00:40:41.859> was<00:40:42.069> sort<00:40:42.309> of<00:40:42.460> like<00:40:42.670> okay 00:40:42.870 --> 00:40:42.880 align:start position:0% proposal which was sort of like okay 00:40:42.880 --> 00:40:45.089 align:start position:0% proposal which was sort of like okay let's<00:40:43.210> maybe<00:40:43.390> do<00:40:43.660> one<00:40:43.869> so<00:40:44.680> we're<00:40:44.799> not<00:40:44.859> going<00:40:45.040> to 00:40:45.089 --> 00:40:45.099 align:start position:0% let's maybe do one so we're not going to 00:40:45.099 --> 00:40:48.870 align:start position:0% let's maybe do one so we're not going to fool<00:40:45.339> what<00:40:46.030> sanitarium<00:40:46.780> but<00:40:47.700> what<00:40:48.700> we're 00:40:48.870 --> 00:40:48.880 align:start position:0% fool what sanitarium but what we're 00:40:48.880 --> 00:40:50.099 align:start position:0% fool what sanitarium but what we're basically<00:40:48.970> going<00:40:49.299> to<00:40:49.359> start<00:40:49.630> from<00:40:49.750> scratch 00:40:50.099 --> 00:40:50.109 align:start position:0% basically going to start from scratch 00:40:50.109 --> 00:40:52.920 align:start position:0% basically going to start from scratch we'll<00:40:50.710> make<00:40:50.829> a<00:40:50.890> new<00:40:51.099> Genesis<00:40:51.609> yeah<00:40:52.420> yeah 00:40:52.920 --> 00:40:52.930 align:start position:0% we'll make a new Genesis yeah yeah 00:40:52.930 --> 00:40:54.329 align:start position:0% we'll make a new Genesis yeah yeah that's<00:40:53.319> like<00:40:53.500> finding<00:40:53.740> places<00:40:53.980> another 00:40:54.329 --> 00:40:54.339 align:start position:0% that's like finding places another 00:40:54.339 --> 00:40:56.579 align:start position:0% that's like finding places another possibility<00:40:54.819> so<00:40:55.569> our<00:40:55.960> time<00:40:56.230> is<00:40:56.260> up 00:40:56.579 --> 00:40:56.589 align:start position:0% possibility so our time is up 00:40:56.589 --> 00:40:58.200 align:start position:0% possibility so our time is up unfortunately<00:40:57.400> I'll<00:40:57.640> be<00:40:57.730> in<00:40:57.790> the<00:40:57.880> hallway<00:40:58.119> to 00:40:58.200 --> 00:40:58.210 align:start position:0% unfortunately I'll be in the hallway to 00:40:58.210 --> 00:41:00.870 align:start position:0% unfortunately I'll be in the hallway to talk<00:40:58.390> we<00:40:58.540> work<00:40:58.720> and<00:40:58.960> Martin<00:40:59.470> asked<00:40:59.619> right<00:40:59.880> so 00:41:00.870 --> 00:41:00.880 align:start position:0% talk we work and Martin asked right so 00:41:00.880 --> 00:41:02.760 align:start position:0% talk we work and Martin asked right so yeah<00:41:01.510> tell<00:41:01.750> me<00:41:01.839> on<00:41:01.960> Twitter<00:41:02.170> if<00:41:02.290> we<00:41:02.349> took<00:41:02.470> a<00:41:02.530> pic 00:41:02.760 --> 00:41:02.770 align:start position:0% yeah tell me on Twitter if we took a pic 00:41:02.770 --> 00:41:06.620 align:start position:0% yeah tell me on Twitter if we took a pic I'd<00:41:02.950> love<00:41:03.160> to<00:41:03.430> see<00:41:04.270> my<00:41:04.390> face<00:41:04.630> everywhere<00:41:05.190> right 00:41:06.620 --> 00:41:06.630 align:start position:0% I'd love to see my face everywhere right 00:41:06.630 --> 00:41:13.000 align:start position:0% I'd love to see my face everywhere right so<00:41:07.630> yeah<00:41:08.400> thank<00:41:09.400> you<00:41:09.430> all<00:41:09.579> for<00:41:09.760> coming<00:41:09.819> so<00:41:10.359> much 00:41:13.000 --> 00:41:13.010 align:start position:0% 00:41:13.010 --> 00:41:21.630 align:start position:0% [Applause] 00:41:21.630 --> 00:41:21.640 align:start position:0% 00:41:21.640 --> 00:41:23.700 align:start position:0% you