WEBVTT Kind: captions Language: en 00:00:00.000 --> 00:00:04.350 align:start position:0% foreign 00:00:04.350 --> 00:00:04.360 align:start position:0% 00:00:04.360 --> 00:00:12.730 align:start position:0% [Music] 00:00:12.730 --> 00:00:12.740 align:start position:0% 00:00:12.740 --> 00:00:15.530 align:start position:0% I've<00:00:13.740> been<00:00:13.920> with<00:00:14.099> the<00:00:14.280> guest<00:00:14.519> team<00:00:14.759> for<00:00:15.299> two 00:00:15.530 --> 00:00:15.540 align:start position:0% I've been with the guest team for two 00:00:15.540 --> 00:00:17.750 align:start position:0% I've been with the guest team for two years<00:00:15.719> now<00:00:15.960> what<00:00:16.740> were<00:00:16.920> you<00:00:17.039> doing<00:00:17.220> before<00:00:17.520> you 00:00:17.750 --> 00:00:17.760 align:start position:0% years now what were you doing before you 00:00:17.760 --> 00:00:20.269 align:start position:0% years now what were you doing before you were<00:00:17.880> in<00:00:18.000> the<00:00:18.119> guest<00:00:18.240> team<00:00:18.539> oh<00:00:18.960> I<00:00:19.140> was<00:00:19.680> working 00:00:20.269 --> 00:00:20.279 align:start position:0% were in the guest team oh I was working 00:00:20.279 --> 00:00:23.630 align:start position:0% were in the guest team oh I was working on<00:00:20.640> permanent<00:00:21.300> State<00:00:21.539> channels<00:00:22.039> and<00:00:23.039> actually 00:00:23.630 --> 00:00:23.640 align:start position:0% on permanent State channels and actually 00:00:23.640 --> 00:00:26.750 align:start position:0% on permanent State channels and actually mining<00:00:24.180> software<00:00:24.740> my<00:00:25.740> name<00:00:25.859> is<00:00:25.980> Guillaume 00:00:26.750 --> 00:00:26.760 align:start position:0% mining software my name is Guillaume 00:00:26.760 --> 00:00:28.490 align:start position:0% mining software my name is Guillaume I've<00:00:27.420> been<00:00:27.599> working<00:00:27.779> on<00:00:27.960> the<00:00:28.080> guest<00:00:28.260> team 00:00:28.490 --> 00:00:28.500 align:start position:0% I've been working on the guest team 00:00:28.500 --> 00:00:30.730 align:start position:0% I've been working on the guest team since<00:00:28.859> 2017 00:00:30.730 --> 00:00:30.740 align:start position:0% since 2017 00:00:30.740 --> 00:00:33.410 align:start position:0% since 2017 initially<00:00:31.740> on<00:00:31.859> a<00:00:32.040> project<00:00:32.160> called<00:00:32.399> whisper 00:00:33.410 --> 00:00:33.420 align:start position:0% initially on a project called whisper 00:00:33.420 --> 00:00:37.310 align:start position:0% initially on a project called whisper uh<00:00:34.260> didn't<00:00:34.620> work<00:00:34.860> out<00:00:35.040> so<00:00:35.520> I<00:00:36.000> moved<00:00:36.360> on<00:00:36.420> to<00:00:36.780> uh 00:00:37.310 --> 00:00:37.320 align:start position:0% uh didn't work out so I moved on to uh 00:00:37.320 --> 00:00:39.709 align:start position:0% uh didn't work out so I moved on to uh more<00:00:37.620> core<00:00:37.739> development<00:00:38.280> and<00:00:39.000> I'm<00:00:39.300> currently 00:00:39.709 --> 00:00:39.719 align:start position:0% more core development and I'm currently 00:00:39.719 --> 00:00:41.990 align:start position:0% more core development and I'm currently working<00:00:39.960> on<00:00:40.200> the<00:00:40.320> topic<00:00:40.620> of<00:00:41.000> stateless 00:00:41.990 --> 00:00:42.000 align:start position:0% working on the topic of stateless 00:00:42.000 --> 00:00:44.830 align:start position:0% working on the topic of stateless ethereum<00:00:42.899> and<00:00:43.559> vocal<00:00:43.920> trees 00:00:44.830 --> 00:00:44.840 align:start position:0% ethereum and vocal trees 00:00:44.840 --> 00:00:47.930 align:start position:0% ethereum and vocal trees uh<00:00:45.840> before<00:00:46.320> that<00:00:46.620> I<00:00:46.860> was<00:00:46.980> an<00:00:47.160> engineer<00:00:47.460> at<00:00:47.700> a 00:00:47.930 --> 00:00:47.940 align:start position:0% uh before that I was an engineer at a 00:00:47.940 --> 00:00:50.090 align:start position:0% uh before that I was an engineer at a various<00:00:48.180> non-crypto<00:00:48.960> related<00:00:49.320> companies<00:00:49.860> and 00:00:50.090 --> 00:00:50.100 align:start position:0% various non-crypto related companies and 00:00:50.100 --> 00:00:52.330 align:start position:0% various non-crypto related companies and I'm<00:00:50.280> very<00:00:50.520> glad<00:00:50.879> not<00:00:51.660> to<00:00:51.780> work<00:00:51.899> there<00:00:52.140> anymore 00:00:52.330 --> 00:00:52.340 align:start position:0% I'm very glad not to work there anymore 00:00:52.340 --> 00:00:55.910 align:start position:0% I'm very glad not to work there anymore I'm<00:00:53.340> Peter<00:00:53.820> I've<00:00:54.180> been<00:00:54.420> on<00:00:54.719> the<00:00:54.960> gas<00:00:55.260> team<00:00:55.559> for 00:00:55.910 --> 00:00:55.920 align:start position:0% I'm Peter I've been on the gas team for 00:00:55.920 --> 00:00:57.770 align:start position:0% I'm Peter I've been on the gas team for about<00:00:56.100> eight<00:00:56.399> years<00:00:56.640> now<00:00:56.879> I<00:00:57.239> started<00:00:57.539> working 00:00:57.770 --> 00:00:57.780 align:start position:0% about eight years now I started working 00:00:57.780 --> 00:01:00.110 align:start position:0% about eight years now I started working on<00:00:58.079> whisper<00:00:58.739> and<00:00:59.219> figured<00:00:59.520> out<00:00:59.640> that<00:00:59.820> it<00:00:59.940> won't 00:01:00.110 --> 00:01:00.120 align:start position:0% on whisper and figured out that it won't 00:01:00.120 --> 00:01:02.630 align:start position:0% on whisper and figured out that it won't work<00:01:00.300> out<00:01:00.480> in<00:01:00.600> about<00:01:00.780> two<00:01:01.079> months 00:01:02.630 --> 00:01:02.640 align:start position:0% work out in about two months 00:01:02.640 --> 00:01:04.910 align:start position:0% work out in about two months the<00:01:03.059> essential<00:01:03.660> ethereum<00:01:04.080> is<00:01:04.199> my<00:01:04.440> first<00:01:04.619> real 00:01:04.910 --> 00:01:04.920 align:start position:0% the essential ethereum is my first real 00:01:04.920 --> 00:01:07.969 align:start position:0% the essential ethereum is my first real job<00:01:05.220> so<00:01:05.580> hello<00:01:06.119> I<00:01:06.780> am<00:01:06.960> Matt<00:01:07.140> I've<00:01:07.619> been<00:01:07.740> on<00:01:07.860> the 00:01:07.969 --> 00:01:07.979 align:start position:0% job so hello I am Matt I've been on the 00:01:07.979 --> 00:01:10.910 align:start position:0% job so hello I am Matt I've been on the guest<00:01:08.100> team<00:01:08.340> for<00:01:08.700> four<00:01:08.939> months<00:01:09.439> uh<00:01:10.439> I've<00:01:10.680> been 00:01:10.910 --> 00:01:10.920 align:start position:0% guest team for four months uh I've been 00:01:10.920 --> 00:01:12.710 align:start position:0% guest team for four months uh I've been working<00:01:11.220> in<00:01:11.520> the<00:01:11.640> ethereum<00:01:12.060> space<00:01:12.299> for<00:01:12.659> about 00:01:12.710 --> 00:01:12.720 align:start position:0% working in the ethereum space for about 00:01:12.720 --> 00:01:15.770 align:start position:0% working in the ethereum space for about four<00:01:13.020> years<00:01:13.260> it's<00:01:13.740> also<00:01:14.159> my<00:01:14.460> first<00:01:14.640> real<00:01:15.000> job<00:01:15.299> I 00:01:15.770 --> 00:01:15.780 align:start position:0% four years it's also my first real job I 00:01:15.780 --> 00:01:18.410 align:start position:0% four years it's also my first real job I worked<00:01:16.140> on<00:01:16.260> the<00:01:16.380> cool<00:01:16.500> team<00:01:16.799> previously<00:01:17.520> doing 00:01:18.410 --> 00:01:18.420 align:start position:0% worked on the cool team previously doing 00:01:18.420 --> 00:01:23.149 align:start position:0% worked on the cool team previously doing various<00:01:19.260> r<00:01:19.920> d<00:01:20.299> efforts<00:01:21.299> on<00:01:21.600> future<00:01:22.500> ideas<00:01:22.860> for 00:01:23.149 --> 00:01:23.159 align:start position:0% various r d efforts on future ideas for 00:01:23.159 --> 00:01:24.770 align:start position:0% various r d efforts on future ideas for ethereum<00:01:23.700> and 00:01:24.770 --> 00:01:24.780 align:start position:0% ethereum and 00:01:24.780 --> 00:01:28.130 align:start position:0% ethereum and now<00:01:25.380> working<00:01:25.680> on<00:01:26.040> the<00:01:26.220> Json<00:01:26.460> RPC<00:01:27.060> for<00:01:27.479> the<00:01:27.900> Geth 00:01:28.130 --> 00:01:28.140 align:start position:0% now working on the Json RPC for the Geth 00:01:28.140 --> 00:01:30.410 align:start position:0% now working on the Json RPC for the Geth team<00:01:28.380> so<00:01:29.159> this<00:01:29.400> panel<00:01:29.759> was<00:01:29.880> supposed<00:01:30.060> to<00:01:30.119> be<00:01:30.240> an 00:01:30.410 --> 00:01:30.420 align:start position:0% team so this panel was supposed to be an 00:01:30.420 --> 00:01:33.050 align:start position:0% team so this panel was supposed to be an ask<00:01:30.600> me<00:01:30.720> anything<00:01:31.100> so<00:01:32.100> it<00:01:32.580> would<00:01:32.700> be<00:01:32.880> super 00:01:33.050 --> 00:01:33.060 align:start position:0% ask me anything so it would be super 00:01:33.060 --> 00:01:35.530 align:start position:0% ask me anything so it would be super nice<00:01:33.299> if<00:01:33.600> you<00:01:33.780> have<00:01:33.900> any<00:01:34.140> questions<00:01:34.380> starters 00:01:35.530 --> 00:01:35.540 align:start position:0% nice if you have any questions starters 00:01:35.540 --> 00:01:38.810 align:start position:0% nice if you have any questions starters we<00:01:36.540> woke<00:01:36.720> up<00:01:36.900> with<00:01:37.079> the<00:01:37.560> news<00:01:37.740> of<00:01:38.100> arbitrum 00:01:38.810 --> 00:01:38.820 align:start position:0% we woke up with the news of arbitrum 00:01:38.820 --> 00:01:42.170 align:start position:0% we woke up with the news of arbitrum acoustic<00:01:39.299> acquisition<00:01:40.259> for<00:01:40.920> prism<00:01:41.340> how<00:01:42.060> do 00:01:42.170 --> 00:01:42.180 align:start position:0% acoustic acquisition for prism how do 00:01:42.180 --> 00:01:44.450 align:start position:0% acoustic acquisition for prism how do you<00:01:42.420> how<00:01:43.079> your<00:01:43.320> team<00:01:43.500> looks<00:01:43.979> for<00:01:44.220> an 00:01:44.450 --> 00:01:44.460 align:start position:0% you how your team looks for an 00:01:44.460 --> 00:01:46.609 align:start position:0% you how your team looks for an acquisition<00:01:44.939> and<00:01:45.479> do<00:01:45.600> you<00:01:45.780> think<00:01:45.900> prism<00:01:46.259> will 00:01:46.609 --> 00:01:46.619 align:start position:0% acquisition and do you think prism will 00:01:46.619 --> 00:01:50.450 align:start position:0% acquisition and do you think prism will be<00:01:46.820> leader<00:01:47.820> consensus<00:01:48.420> clients<00:01:49.020> for<00:01:49.320> ethereum 00:01:50.450 --> 00:01:50.460 align:start position:0% be leader consensus clients for ethereum 00:01:50.460 --> 00:01:53.210 align:start position:0% be leader consensus clients for ethereum I<00:01:51.180> actually<00:01:51.360> just<00:01:51.720> heard<00:01:52.079> it<00:01:52.320> two<00:01:52.680> minutes<00:01:52.860> ago 00:01:53.210 --> 00:01:53.220 align:start position:0% I actually just heard it two minutes ago 00:01:53.220 --> 00:01:55.789 align:start position:0% I actually just heard it two minutes ago before<00:01:53.399> we<00:01:53.700> went<00:01:53.880> on<00:01:54.060> stage<00:01:54.420> so<00:01:55.259> I<00:01:55.439> didn't 00:01:55.789 --> 00:01:55.799 align:start position:0% before we went on stage so I didn't 00:01:55.799 --> 00:01:57.950 align:start position:0% before we went on stage so I didn't really<00:01:56.159> read<00:01:56.579> anything<00:01:56.880> about<00:01:57.180> it<00:01:57.420> or<00:01:57.600> made<00:01:57.780> up 00:01:57.950 --> 00:01:57.960 align:start position:0% really read anything about it or made up 00:01:57.960 --> 00:02:01.130 align:start position:0% really read anything about it or made up my<00:01:58.140> mind<00:01:58.259> about<00:01:58.500> it<00:01:58.799> I<00:01:59.640> think<00:02:00.140> consolidation 00:02:01.130 --> 00:02:01.140 align:start position:0% my mind about it I think consolidation 00:02:01.140 --> 00:02:03.710 align:start position:0% my mind about it I think consolidation is 00:02:03.710 --> 00:02:03.720 align:start position:0% is 00:02:03.720 --> 00:02:06.709 align:start position:0% is um<00:02:03.780> it's<00:02:04.500> always<00:02:04.920> this<00:02:05.460> two<00:02:05.700> side<00:02:05.939> of<00:02:06.240> the<00:02:06.420> side 00:02:06.709 --> 00:02:06.719 align:start position:0% um it's always this two side of the side 00:02:06.719 --> 00:02:09.589 align:start position:0% um it's always this two side of the side of<00:02:06.899> this<00:02:07.079> of<00:02:07.320> a<00:02:07.439> coin<00:02:07.979> right<00:02:08.160> we<00:02:08.940> want<00:02:09.119> to<00:02:09.239> be<00:02:09.360> as 00:02:09.589 --> 00:02:09.599 align:start position:0% of this of a coin right we want to be as 00:02:09.599 --> 00:02:12.010 align:start position:0% of this of a coin right we want to be as decentralized<00:02:10.200> we<00:02:10.440> want<00:02:10.619> to<00:02:10.739> be<00:02:10.979> as<00:02:11.879> um 00:02:12.010 --> 00:02:12.020 align:start position:0% decentralized we want to be as um 00:02:12.020 --> 00:02:14.270 align:start position:0% decentralized we want to be as um distributed<00:02:13.020> as<00:02:13.200> possible<00:02:13.500> and<00:02:13.739> that<00:02:13.980> also 00:02:14.270 --> 00:02:14.280 align:start position:0% distributed as possible and that also 00:02:14.280 --> 00:02:15.229 align:start position:0% distributed as possible and that also means 00:02:15.229 --> 00:02:15.239 align:start position:0% means 00:02:15.239 --> 00:02:18.650 align:start position:0% means um that<00:02:15.599> the<00:02:15.900> team<00:02:16.080> should<00:02:16.440> be<00:02:16.620> independent 00:02:18.650 --> 00:02:18.660 align:start position:0% um that the team should be independent 00:02:18.660 --> 00:02:21.290 align:start position:0% um that the team should be independent um<00:02:18.780> on<00:02:19.260> the<00:02:19.319> other<00:02:19.440> hand<00:02:19.680> if<00:02:20.099> you<00:02:20.340> have<00:02:20.520> uh<00:02:20.940> like 00:02:21.290 --> 00:02:21.300 align:start position:0% um on the other hand if you have uh like 00:02:21.300 --> 00:02:24.410 align:start position:0% um on the other hand if you have uh like a<00:02:21.540> bigger<00:02:22.080> company<00:02:22.580> uh<00:02:23.580> working<00:02:23.819> on<00:02:24.120> different 00:02:24.410 --> 00:02:24.420 align:start position:0% a bigger company uh working on different 00:02:24.420 --> 00:02:26.330 align:start position:0% a bigger company uh working on different uh<00:02:25.020> things 00:02:26.330 --> 00:02:26.340 align:start position:0% uh things 00:02:26.340 --> 00:02:31.190 align:start position:0% uh things um they<00:02:26.640> can<00:02:26.819> achieve<00:02:27.239> stuff<00:02:27.480> faster<00:02:28.160> and<00:02:29.160> so 00:02:31.190 --> 00:02:31.200 align:start position:0% um they can achieve stuff faster and so 00:02:31.200 --> 00:02:33.050 align:start position:0% um they can achieve stuff faster and so let's<00:02:31.739> see<00:02:31.980> what<00:02:32.099> the<00:02:32.280> future<00:02:32.400> holds<00:02:32.879> for<00:02:33.000> for 00:02:33.050 --> 00:02:33.060 align:start position:0% let's see what the future holds for for 00:02:33.060 --> 00:02:36.170 align:start position:0% let's see what the future holds for for arbitrary<00:02:33.780> and<00:02:33.959> prism<00:02:34.680> uh<00:02:35.400> plus<00:02:35.640> just<00:02:35.879> to<00:02:36.060> add 00:02:36.170 --> 00:02:36.180 align:start position:0% arbitrary and prism uh plus just to add 00:02:36.180 --> 00:02:39.229 align:start position:0% arbitrary and prism uh plus just to add to<00:02:36.360> that<00:02:36.480> I<00:02:36.720> think<00:02:36.900> the<00:02:37.860> ethereum<00:02:38.220> vision<00:02:38.520> long 00:02:39.229 --> 00:02:39.239 align:start position:0% to that I think the ethereum vision long 00:02:39.239 --> 00:02:42.589 align:start position:0% to that I think the ethereum vision long term<00:02:39.420> the<00:02:39.720> idea<00:02:40.020> is<00:02:40.500> that<00:02:40.920> the<00:02:41.400> clients<00:02:41.819> will 00:02:42.589 --> 00:02:42.599 align:start position:0% term the idea is that the clients will 00:02:42.599 --> 00:02:44.809 align:start position:0% term the idea is that the clients will be<00:02:42.780> more<00:02:42.959> the<00:02:43.379> most<00:02:43.680> important<00:02:44.099> clients<00:02:44.580> will 00:02:44.809 --> 00:02:44.819 align:start position:0% be more the most important clients will 00:02:44.819 --> 00:02:47.030 align:start position:0% be more the most important clients will be<00:02:45.060> maintained<00:02:45.540> by<00:02:45.959> fairly<00:02:46.500> important 00:02:47.030 --> 00:02:47.040 align:start position:0% be maintained by fairly important 00:02:47.040 --> 00:02:49.250 align:start position:0% be maintained by fairly important companies<00:02:47.459> whether<00:02:48.239> those<00:02:48.780> companies<00:02:49.080> grow 00:02:49.250 --> 00:02:49.260 align:start position:0% companies whether those companies grow 00:02:49.260 --> 00:02:51.470 align:start position:0% companies whether those companies grow out<00:02:49.440> of<00:02:49.560> the<00:02:49.680> ecosystem<00:02:50.160> or<00:02:50.700> our<00:02:50.879> external 00:02:51.470 --> 00:02:51.480 align:start position:0% out of the ecosystem or our external 00:02:51.480 --> 00:02:53.330 align:start position:0% out of the ecosystem or our external companies<00:02:51.900> that's<00:02:52.200> I<00:02:52.440> mean<00:02:52.560> out<00:02:52.739> for<00:02:52.980> debate 00:02:53.330 --> 00:02:53.340 align:start position:0% companies that's I mean out for debate 00:02:53.340 --> 00:02:55.490 align:start position:0% companies that's I mean out for debate but<00:02:53.700> I<00:02:54.239> think<00:02:54.360> in<00:02:54.660> general<00:02:54.780> it's<00:02:55.080> good<00:02:55.319> for 00:02:55.490 --> 00:02:55.500 align:start position:0% but I think in general it's good for 00:02:55.500 --> 00:02:58.130 align:start position:0% but I think in general it's good for ethereum<00:02:55.920> if<00:02:56.160> you<00:02:56.280> have<00:02:56.459> solid<00:02:57.140> well-funded 00:02:58.130 --> 00:02:58.140 align:start position:0% ethereum if you have solid well-funded 00:02:58.140 --> 00:03:01.070 align:start position:0% ethereum if you have solid well-funded teams<00:02:58.620> behind<00:02:58.920> them<00:02:59.099> so<00:02:59.879> whether<00:03:00.660> this 00:03:01.070 --> 00:03:01.080 align:start position:0% teams behind them so whether this 00:03:01.080 --> 00:03:02.990 align:start position:0% teams behind them so whether this particular<00:03:01.379> case<00:03:01.860> is<00:03:02.040> good<00:03:02.280> or<00:03:02.400> bad<00:03:02.580> I<00:03:02.879> mean 00:03:02.990 --> 00:03:03.000 align:start position:0% particular case is good or bad I mean 00:03:03.000 --> 00:03:05.930 align:start position:0% particular case is good or bad I mean that's<00:03:03.239> Up<00:03:03.480> For<00:03:03.660> Debate<00:03:04.019> but<00:03:04.379> the<00:03:05.220> idea<00:03:05.580> is 00:03:05.930 --> 00:03:05.940 align:start position:0% that's Up For Debate but the idea is 00:03:05.940 --> 00:03:06.710 align:start position:0% that's Up For Debate but the idea is okay 00:03:06.710 --> 00:03:06.720 align:start position:0% okay 00:03:06.720 --> 00:03:08.990 align:start position:0% okay all<00:03:07.319> right<00:03:07.500> I<00:03:07.739> have<00:03:07.920> a<00:03:08.099> question<00:03:08.280> for<00:03:08.640> you<00:03:08.819> guys 00:03:08.990 --> 00:03:09.000 align:start position:0% all right I have a question for you guys 00:03:09.000 --> 00:03:11.809 align:start position:0% all right I have a question for you guys right<00:03:09.420> here<00:03:10.080> so<00:03:10.739> thank<00:03:11.040> you<00:03:11.159> for<00:03:11.340> being<00:03:11.519> here 00:03:11.809 --> 00:03:11.819 align:start position:0% right here so thank you for being here 00:03:11.819 --> 00:03:15.110 align:start position:0% right here so thank you for being here you<00:03:12.300> guys<00:03:12.480> are<00:03:12.720> rock<00:03:13.080> stars<00:03:13.580> so<00:03:14.580> this<00:03:14.819> is<00:03:14.940> a 00:03:15.110 --> 00:03:15.120 align:start position:0% you guys are rock stars so this is a 00:03:15.120 --> 00:03:17.449 align:start position:0% you guys are rock stars so this is a question<00:03:15.360> for<00:03:16.080> the<00:03:16.440> you<00:03:16.739> know<00:03:16.920> the<00:03:17.040> ones<00:03:17.340> I 00:03:17.449 --> 00:03:17.459 align:start position:0% question for the you know the ones I 00:03:17.459 --> 00:03:20.509 align:start position:0% question for the you know the ones I have<00:03:17.580> been<00:03:17.760> here<00:03:18.060> many<00:03:18.360> years<00:03:18.739> about<00:03:19.739> the<00:03:20.159> what 00:03:20.509 --> 00:03:20.519 align:start position:0% have been here many years about the what 00:03:20.519 --> 00:03:22.790 align:start position:0% have been here many years about the what is<00:03:20.640> your<00:03:21.000> most<00:03:21.300> memorable<00:03:22.080> experience 00:03:22.790 --> 00:03:22.800 align:start position:0% is your most memorable experience 00:03:22.800 --> 00:03:25.850 align:start position:0% is your most memorable experience working<00:03:23.220> for<00:03:23.580> Geth<00:03:23.940> I<00:03:24.480> remember<00:03:24.599> Defcon<00:03:25.319> 2<00:03:25.560> the 00:03:25.850 --> 00:03:25.860 align:start position:0% working for Geth I remember Defcon 2 the 00:03:25.860 --> 00:03:29.030 align:start position:0% working for Geth I remember Defcon 2 the Shanghai<00:03:26.340> attacks<00:03:26.940> so<00:03:27.900> I<00:03:28.440> don't<00:03:28.560> know<00:03:28.680> what's 00:03:29.030 --> 00:03:29.040 align:start position:0% Shanghai attacks so I don't know what's 00:03:29.040 --> 00:03:32.630 align:start position:0% Shanghai attacks so I don't know what's your<00:03:29.519> experience<00:03:30.239> about<00:03:30.599> that<00:03:31.400> so<00:03:32.400> I<00:03:32.580> would 00:03:32.630 --> 00:03:32.640 align:start position:0% your experience about that so I would 00:03:32.640 --> 00:03:34.550 align:start position:0% your experience about that so I would like<00:03:32.819> to<00:03:33.000> know<00:03:33.180> what's<00:03:33.599> the<00:03:33.840> most<00:03:34.140> memorable 00:03:34.550 --> 00:03:34.560 align:start position:0% like to know what's the most memorable 00:03:34.560 --> 00:03:36.949 align:start position:0% like to know what's the most memorable experience<00:03:35.099> for<00:03:35.519> all<00:03:35.700> you<00:03:35.940> for<00:03:36.180> what<00:03:36.659> is<00:03:36.780> the 00:03:36.949 --> 00:03:36.959 align:start position:0% experience for all you for what is the 00:03:36.959 --> 00:03:38.990 align:start position:0% experience for all you for what is the fundest<00:03:37.379> experience<00:03:37.860> working<00:03:38.280> with<00:03:38.700> the<00:03:38.819> get 00:03:38.990 --> 00:03:39.000 align:start position:0% fundest experience working with the get 00:03:39.000 --> 00:03:40.369 align:start position:0% fundest experience working with the get team 00:03:40.369 --> 00:03:40.379 align:start position:0% team 00:03:40.379 --> 00:03:43.190 align:start position:0% team what<00:03:41.340> about<00:03:41.580> the<00:03:42.000> merch<00:03:42.360> like<00:03:42.659> how<00:03:42.900> do<00:03:43.080> you 00:03:43.190 --> 00:03:43.200 align:start position:0% what about the merch like how do you 00:03:43.200 --> 00:03:46.070 align:start position:0% what about the merch like how do you celebrate<00:03:43.799> it<00:03:43.980> is<00:03:44.940> that<00:03:45.180> was<00:03:45.360> that<00:03:45.540> a<00:03:45.780> happy 00:03:46.070 --> 00:03:46.080 align:start position:0% celebrate it is that was that a happy 00:03:46.080 --> 00:03:48.970 align:start position:0% celebrate it is that was that a happy celebration<00:03:46.739> was<00:03:47.099> that<00:03:47.340> full<00:03:48.120> of<00:03:48.299> anxiety 00:03:48.970 --> 00:03:48.980 align:start position:0% celebration was that full of anxiety 00:03:48.980 --> 00:03:53.089 align:start position:0% celebration was that full of anxiety where<00:03:49.980> the<00:03:50.700> the<00:03:50.879> merge<00:03:51.299> celebration<00:03:51.780> was 00:03:53.089 --> 00:03:53.099 align:start position:0% where the the merge celebration was 00:03:53.099 --> 00:03:55.850 align:start position:0% where the the merge celebration was basically<00:03:53.819> okay<00:03:54.239> it's<00:03:54.480> done<00:03:54.780> now<00:03:55.019> let's<00:03:55.500> let's 00:03:55.850 --> 00:03:55.860 align:start position:0% basically okay it's done now let's let's 00:03:55.860 --> 00:03:57.890 align:start position:0% basically okay it's done now let's let's move<00:03:56.280> on 00:03:57.890 --> 00:03:57.900 align:start position:0% move on 00:03:57.900 --> 00:04:00.289 align:start position:0% move on um<00:03:58.080> so<00:03:58.440> for<00:03:58.560> me<00:03:58.739> the<00:03:58.980> the<00:03:59.280> I<00:03:59.819> think<00:03:59.940> the<00:04:00.120> most 00:04:00.289 --> 00:04:00.299 align:start position:0% um so for me the the I think the most 00:04:00.299 --> 00:04:02.930 align:start position:0% um so for me the the I think the most memorable<00:04:00.799> I've<00:04:01.799> haven't<00:04:02.280> been<00:04:02.459> in<00:04:02.640> this<00:04:02.760> team 00:04:02.930 --> 00:04:02.940 align:start position:0% memorable I've haven't been in this team 00:04:02.940 --> 00:04:05.470 align:start position:0% memorable I've haven't been in this team for<00:04:03.120> for<00:04:03.360> that<00:04:03.659> long<00:04:03.840> uh<00:04:04.680> the<00:04:04.920> most<00:04:05.040> memorable 00:04:05.470 --> 00:04:05.480 align:start position:0% for for that long uh the most memorable 00:04:05.480 --> 00:04:08.990 align:start position:0% for for that long uh the most memorable thing<00:04:06.480> I<00:04:06.900> think<00:04:07.140> was<00:04:07.560> the<00:04:08.220> uh<00:04:08.640> Greece 00:04:08.990 --> 00:04:09.000 align:start position:0% thing I think was the uh Greece 00:04:09.000 --> 00:04:10.550 align:start position:0% thing I think was the uh Greece interrupt 00:04:10.550 --> 00:04:10.560 align:start position:0% interrupt 00:04:10.560 --> 00:04:12.530 align:start position:0% interrupt um<00:04:10.620> where<00:04:11.220> we<00:04:11.400> worked<00:04:11.700> on<00:04:11.819> the<00:04:12.000> merge<00:04:12.299> together 00:04:12.530 --> 00:04:12.540 align:start position:0% um where we worked on the merge together 00:04:12.540 --> 00:04:15.229 align:start position:0% um where we worked on the merge together with<00:04:13.080> all<00:04:13.379> of<00:04:13.500> the<00:04:13.860> different<00:04:14.220> client<00:04:14.760> teams 00:04:15.229 --> 00:04:15.239 align:start position:0% with all of the different client teams 00:04:15.239 --> 00:04:17.509 align:start position:0% with all of the different client teams uh<00:04:15.840> consensus<00:04:16.320> layer<00:04:16.680> client<00:04:17.100> teams 00:04:17.509 --> 00:04:17.519 align:start position:0% uh consensus layer client teams 00:04:17.519 --> 00:04:21.530 align:start position:0% uh consensus layer client teams execution<00:04:17.940> layer<00:04:18.299> client<00:04:18.600> teams<00:04:19.340> uh<00:04:20.340> in<00:04:21.000> a 00:04:21.530 --> 00:04:21.540 align:start position:0% execution layer client teams uh in a 00:04:21.540 --> 00:04:25.010 align:start position:0% execution layer client teams uh in a really<00:04:21.660> nice<00:04:21.900> hotel<00:04:22.139> in<00:04:22.680> Greece<00:04:23.180> and<00:04:24.180> we<00:04:24.720> spent 00:04:25.010 --> 00:04:25.020 align:start position:0% really nice hotel in Greece and we spent 00:04:25.020 --> 00:04:27.170 align:start position:0% really nice hotel in Greece and we spent like<00:04:25.500> the<00:04:26.100> whole<00:04:26.220> day<00:04:26.460> sitting<00:04:26.940> in<00:04:27.060> the 00:04:27.170 --> 00:04:27.180 align:start position:0% like the whole day sitting in the 00:04:27.180 --> 00:04:29.629 align:start position:0% like the whole day sitting in the basement<00:04:27.360> hunched<00:04:28.320> off<00:04:28.440> over<00:04:28.740> our<00:04:29.040> computers 00:04:29.629 --> 00:04:29.639 align:start position:0% basement hunched off over our computers 00:04:29.639 --> 00:04:32.870 align:start position:0% basement hunched off over our computers uh<00:04:30.600> working<00:04:31.020> while<00:04:31.680> there<00:04:31.919> was<00:04:32.100> it<00:04:32.520> was<00:04:32.699> like 00:04:32.870 --> 00:04:32.880 align:start position:0% uh working while there was it was like 00:04:32.880 --> 00:04:35.870 align:start position:0% uh working while there was it was like 30<00:04:33.120> degrees<00:04:33.479> outside<00:04:34.160> and<00:04:35.160> after<00:04:35.400> the<00:04:35.699> third 00:04:35.870 --> 00:04:35.880 align:start position:0% 30 degrees outside and after the third 00:04:35.880 --> 00:04:38.749 align:start position:0% 30 degrees outside and after the third day<00:04:36.060> I<00:04:36.360> I<00:04:36.720> made<00:04:37.380> the<00:04:37.500> decision<00:04:37.800> that 00:04:38.749 --> 00:04:38.759 align:start position:0% day I I made the decision that 00:04:38.759 --> 00:04:41.270 align:start position:0% day I I made the decision that after<00:04:39.419> dinner<00:04:39.840> after<00:04:40.380> lunch<00:04:40.680> I'm<00:04:40.979> going<00:04:41.160> to 00:04:41.270 --> 00:04:41.280 align:start position:0% after dinner after lunch I'm going to 00:04:41.280 --> 00:04:44.030 align:start position:0% after dinner after lunch I'm going to take<00:04:41.580> one<00:04:42.240> hour<00:04:42.419> or<00:04:42.780> two<00:04:42.960> hours<00:04:43.199> to<00:04:43.500> go<00:04:43.680> to<00:04:43.860> the 00:04:44.030 --> 00:04:44.040 align:start position:0% take one hour or two hours to go to the 00:04:44.040 --> 00:04:46.790 align:start position:0% take one hour or two hours to go to the beach<00:04:44.160> to<00:04:44.580> enjoy<00:04:44.880> life<00:04:45.360> a<00:04:45.600> bit<00:04:45.800> between 00:04:46.790 --> 00:04:46.800 align:start position:0% beach to enjoy life a bit between 00:04:46.800 --> 00:04:50.030 align:start position:0% beach to enjoy life a bit between working<00:04:47.280> uh<00:04:47.880> in<00:04:48.660> in<00:04:48.840> the<00:04:49.080> basement 00:04:50.030 --> 00:04:50.040 align:start position:0% working uh in in the basement 00:04:50.040 --> 00:04:51.530 align:start position:0% working uh in in the basement and<00:04:50.759> uh 00:04:51.530 --> 00:04:51.540 align:start position:0% and uh 00:04:51.540 --> 00:04:55.670 align:start position:0% and uh as<00:04:52.199> a<00:04:52.560> I'm<00:04:53.280> in<00:04:53.460> a<00:04:53.639> space<00:04:53.820> around<00:04:54.120> five<00:04:55.080> years<00:04:55.259> so 00:04:55.670 --> 00:04:55.680 align:start position:0% as a I'm in a space around five years so 00:04:55.680 --> 00:04:58.670 align:start position:0% as a I'm in a space around five years so as<00:04:55.919> I'm<00:04:56.220> a<00:04:56.580> co-developer<00:04:57.180> I<00:04:57.540> had<00:04:58.259> opportunity 00:04:58.670 --> 00:04:58.680 align:start position:0% as I'm a co-developer I had opportunity 00:04:58.680 --> 00:05:01.370 align:start position:0% as I'm a co-developer I had opportunity to<00:04:58.979> read<00:04:59.280> your<00:04:59.520> code<00:04:59.759> and<00:05:00.540> uh<00:05:00.840> participate 00:05:01.370 --> 00:05:01.380 align:start position:0% to read your code and uh participate 00:05:01.380 --> 00:05:04.670 align:start position:0% to read your code and uh participate something<00:05:01.740> in<00:05:02.280> your<00:05:02.699> Discord 00:05:04.670 --> 00:05:04.680 align:start position:0% something in your Discord 00:05:04.680 --> 00:05:08.930 align:start position:0% something in your Discord um<00:05:05.040> but<00:05:05.880> after<00:05:06.360> the<00:05:07.020> years<00:05:07.199> passing<00:05:07.860> I<00:05:08.460> I<00:05:08.759> was 00:05:08.930 --> 00:05:08.940 align:start position:0% um but after the years passing I I was 00:05:08.940 --> 00:05:11.749 align:start position:0% um but after the years passing I I was feeling<00:05:09.180> that<00:05:09.600> less<00:05:10.199> and<00:05:10.380> less<00:05:10.620> maybe<00:05:11.040> all 00:05:11.749 --> 00:05:11.759 align:start position:0% feeling that less and less maybe all 00:05:11.759 --> 00:05:14.629 align:start position:0% feeling that less and less maybe all Europe<00:05:12.060> so<00:05:12.540> occupied<00:05:13.199> or<00:05:13.800> with<00:05:14.100> less<00:05:14.340> support 00:05:14.629 --> 00:05:14.639 align:start position:0% Europe so occupied or with less support 00:05:14.639 --> 00:05:17.390 align:start position:0% Europe so occupied or with less support I<00:05:15.360> could<00:05:15.540> saw<00:05:16.020> you<00:05:16.199> less<00:05:16.440> and<00:05:16.620> less<00:05:16.800> in<00:05:17.040> Discord 00:05:17.390 --> 00:05:17.400 align:start position:0% I could saw you less and less in Discord 00:05:17.400 --> 00:05:19.670 align:start position:0% I could saw you less and less in Discord I<00:05:18.000> also<00:05:18.240> the<00:05:18.360> documentation<00:05:18.900> will<00:05:19.199> become 00:05:19.670 --> 00:05:19.680 align:start position:0% I also the documentation will become 00:05:19.680 --> 00:05:22.270 align:start position:0% I also the documentation will become more<00:05:20.100> and<00:05:20.280> more<00:05:20.580> outdated 00:05:22.270 --> 00:05:22.280 align:start position:0% more and more outdated 00:05:22.280 --> 00:05:26.330 align:start position:0% more and more outdated now<00:05:23.280> after<00:05:23.580> I<00:05:24.300> saw<00:05:24.539> Peter's<00:05:25.320> I<00:05:25.680> think<00:05:25.860> of<00:05:26.100> last 00:05:26.330 --> 00:05:26.340 align:start position:0% now after I saw Peter's I think of last 00:05:26.340 --> 00:05:28.850 align:start position:0% now after I saw Peter's I think of last year<00:05:26.580> one<00:05:27.120> of<00:05:27.240> her<00:05:27.360> tweets<00:05:27.780> that<00:05:28.139> say<00:05:28.380> oh<00:05:28.560> we 00:05:28.850 --> 00:05:28.860 align:start position:0% year one of her tweets that say oh we 00:05:28.860 --> 00:05:31.730 align:start position:0% year one of her tweets that say oh we need<00:05:28.979> more<00:05:29.280> support<00:05:29.639> the<00:05:30.060> other<00:05:30.300> stuff<00:05:30.960> did 00:05:31.730 --> 00:05:31.740 align:start position:0% need more support the other stuff did 00:05:31.740 --> 00:05:33.290 align:start position:0% need more support the other stuff did you<00:05:31.860> get<00:05:32.100> some<00:05:32.280> support<00:05:32.520> for<00:05:32.759> the<00:05:32.940> feeding 00:05:33.290 --> 00:05:33.300 align:start position:0% you get some support for the feeding 00:05:33.300 --> 00:05:35.390 align:start position:0% you get some support for the feeding Foundation<00:05:33.600> to<00:05:33.900> support<00:05:34.139> your<00:05:34.500> team<00:05:34.740> maybe<00:05:35.100> to 00:05:35.390 --> 00:05:35.400 align:start position:0% Foundation to support your team maybe to 00:05:35.400 --> 00:05:37.430 align:start position:0% Foundation to support your team maybe to hire<00:05:35.580> new<00:05:36.000> people<00:05:36.240> to<00:05:36.960> help<00:05:37.080> the 00:05:37.430 --> 00:05:37.440 align:start position:0% hire new people to help the 00:05:37.440 --> 00:05:40.189 align:start position:0% hire new people to help the documentation<00:05:38.039> the<00:05:38.520> stuff<00:05:38.699> because<00:05:39.479> you<00:05:40.020> did 00:05:40.189 --> 00:05:40.199 align:start position:0% documentation the stuff because you did 00:05:40.199 --> 00:05:43.129 align:start position:0% documentation the stuff because you did an<00:05:40.380> amazing<00:05:40.860> work<00:05:41.100> go<00:05:41.880> is<00:05:42.360> still<00:05:42.539> being<00:05:42.720> a<00:05:42.960> good 00:05:43.129 --> 00:05:43.139 align:start position:0% an amazing work go is still being a good 00:05:43.139 --> 00:05:46.070 align:start position:0% an amazing work go is still being a good platform<00:05:43.740> for<00:05:44.220> for<00:05:44.460> beauty<00:05:44.759> stuff<00:05:45.120> but<00:05:45.720> I<00:05:45.900> see 00:05:46.070 --> 00:05:46.080 align:start position:0% platform for for beauty stuff but I see 00:05:46.080 --> 00:05:47.870 align:start position:0% platform for for beauty stuff but I see a<00:05:46.199> lot<00:05:46.320> of<00:05:46.440> people<00:05:46.620> say<00:05:46.860> okay<00:05:47.100> you<00:05:47.580> are<00:05:47.759> going 00:05:47.870 --> 00:05:47.880 align:start position:0% a lot of people say okay you are going 00:05:47.880 --> 00:05:51.050 align:start position:0% a lot of people say okay you are going to<00:05:47.940> use<00:05:48.060> rust<00:05:48.539> other<00:05:49.020> stuff<00:05:49.320> but<00:05:50.100> you<00:05:50.520> you<00:05:50.759> have 00:05:51.050 --> 00:05:51.060 align:start position:0% to use rust other stuff but you you have 00:05:51.060 --> 00:05:53.210 align:start position:0% to use rust other stuff but you you have a<00:05:51.300> we<00:05:51.720> have<00:05:51.900> a<00:05:52.080> very<00:05:52.199> good<00:05:52.380> base<00:05:52.620> and<00:05:52.919> knowledge 00:05:53.210 --> 00:05:53.220 align:start position:0% a we have a very good base and knowledge 00:05:53.220 --> 00:05:56.629 align:start position:0% a we have a very good base and knowledge in<00:05:53.400> goal<00:05:53.759> that<00:05:54.120> you<00:05:54.300> guys<00:05:54.539> built<00:05:54.960> so<00:05:55.620> how<00:05:56.460> is 00:05:56.629 --> 00:05:56.639 align:start position:0% in goal that you guys built so how is 00:05:56.639 --> 00:05:59.629 align:start position:0% in goal that you guys built so how is the<00:05:56.820> future<00:05:57.120> for<00:05:57.780> gef<00:05:58.199> so<00:05:58.800> basically<00:05:59.160> this<00:05:59.520> is 00:05:59.629 --> 00:05:59.639 align:start position:0% the future for gef so basically this is 00:05:59.639 --> 00:06:01.010 align:start position:0% the future for gef so basically this is my<00:05:59.820> question 00:06:01.010 --> 00:06:01.020 align:start position:0% my question 00:06:01.020 --> 00:06:03.230 align:start position:0% my question yeah<00:06:01.860> so<00:06:02.220> that's<00:06:02.400> actually<00:06:02.699> a<00:06:02.880> very<00:06:03.060> good 00:06:03.230 --> 00:06:03.240 align:start position:0% yeah so that's actually a very good 00:06:03.240 --> 00:06:05.510 align:start position:0% yeah so that's actually a very good question<00:06:03.479> and<00:06:04.080> I'm<00:06:04.620> kind<00:06:04.919> of<00:06:04.979> happy<00:06:05.160> that<00:06:05.340> I 00:06:05.510 --> 00:06:05.520 align:start position:0% question and I'm kind of happy that I 00:06:05.520 --> 00:06:08.510 align:start position:0% question and I'm kind of happy that I have<00:06:05.639> a<00:06:05.699> positive<00:06:06.000> answer<00:06:06.180> for<00:06:06.419> that<00:06:06.600> is<00:06:07.560> that 00:06:08.510 --> 00:06:08.520 align:start position:0% have a positive answer for that is that 00:06:08.520 --> 00:06:11.210 align:start position:0% have a positive answer for that is that um well<00:06:09.240> in<00:06:09.479> the<00:06:09.600> past<00:06:09.780> we've<00:06:10.500> uh<00:06:10.740> most<00:06:10.979> of<00:06:11.100> the 00:06:11.210 --> 00:06:11.220 align:start position:0% um well in the past we've uh most of the 00:06:11.220 --> 00:06:13.129 align:start position:0% um well in the past we've uh most of the documentation<00:06:11.639> that<00:06:11.880> we<00:06:12.120> wrote<00:06:12.300> or<00:06:12.539> stuff<00:06:12.780> we 00:06:13.129 --> 00:06:13.139 align:start position:0% documentation that we wrote or stuff we 00:06:13.139 --> 00:06:15.770 align:start position:0% documentation that we wrote or stuff we we<00:06:13.620> published<00:06:14.100> were<00:06:14.340> all<00:06:14.520> written<00:06:14.820> by<00:06:15.060> us<00:06:15.360> and 00:06:15.770 --> 00:06:15.780 align:start position:0% we published were all written by us and 00:06:15.780 --> 00:06:18.170 align:start position:0% we published were all written by us and I<00:06:15.900> mean<00:06:16.080> that's<00:06:16.259> kind<00:06:16.560> of<00:06:16.680> nice 00:06:18.170 --> 00:06:18.180 align:start position:0% I mean that's kind of nice 00:06:18.180 --> 00:06:20.029 align:start position:0% I mean that's kind of nice it's<00:06:18.600> kind<00:06:18.780> of<00:06:18.900> we<00:06:19.020> have<00:06:19.259> to<00:06:19.380> be<00:06:19.500> the<00:06:19.680> origin 00:06:20.029 --> 00:06:20.039 align:start position:0% it's kind of we have to be the origin 00:06:20.039 --> 00:06:22.610 align:start position:0% it's kind of we have to be the origin for<00:06:20.280> those<00:06:20.520> but<00:06:21.180> uh<00:06:21.600> we<00:06:22.139> didn't<00:06:22.199> really<00:06:22.440> have 00:06:22.610 --> 00:06:22.620 align:start position:0% for those but uh we didn't really have 00:06:22.620 --> 00:06:25.490 align:start position:0% for those but uh we didn't really have the<00:06:22.740> capacity<00:06:23.160> to<00:06:23.460> do<00:06:23.580> it<00:06:23.699> and<00:06:24.419> uh 00:06:25.490 --> 00:06:25.500 align:start position:0% the capacity to do it and uh 00:06:25.500 --> 00:06:27.529 align:start position:0% the capacity to do it and uh for<00:06:25.979> the<00:06:26.100> past<00:06:26.340> couple<00:06:26.699> months<00:06:27.120> we've 00:06:27.529 --> 00:06:27.539 align:start position:0% for the past couple months we've 00:06:27.539 --> 00:06:29.270 align:start position:0% for the past couple months we've actually<00:06:27.600> had<00:06:27.900> somebody<00:06:28.080> on<00:06:28.440> the<00:06:28.560> team<00:06:28.680> who 00:06:29.270 --> 00:06:29.280 align:start position:0% actually had somebody on the team who 00:06:29.280 --> 00:06:32.510 align:start position:0% actually had somebody on the team who helps<00:06:30.000> write<00:06:30.360> documentation<00:06:31.080> I<00:06:31.979> kind<00:06:32.100> of<00:06:32.280> feel 00:06:32.510 --> 00:06:32.520 align:start position:0% helps write documentation I kind of feel 00:06:32.520 --> 00:06:34.850 align:start position:0% helps write documentation I kind of feel that<00:06:32.759> we<00:06:33.000> still<00:06:33.180> don't<00:06:33.360> help<00:06:33.660> him<00:06:34.080> enough 00:06:34.850 --> 00:06:34.860 align:start position:0% that we still don't help him enough 00:06:34.860 --> 00:06:39.170 align:start position:0% that we still don't help him enough but<00:06:35.580> we're<00:06:35.819> trying<00:06:36.120> our<00:06:36.479> best<00:06:36.800> plus<00:06:38.060> it<00:06:39.060> was 00:06:39.170 --> 00:06:39.180 align:start position:0% but we're trying our best plus it was 00:06:39.180 --> 00:06:41.990 align:start position:0% but we're trying our best plus it was seen<00:06:39.419> as<00:06:39.600> initiative<00:06:40.020> to<00:06:40.800> actually<00:06:41.400> revamp 00:06:41.990 --> 00:06:42.000 align:start position:0% seen as initiative to actually revamp 00:06:42.000 --> 00:06:46.129 align:start position:0% seen as initiative to actually revamp our<00:06:42.539> entire<00:06:42.840> website<00:06:43.259> which<00:06:43.680> will<00:06:44.400> come<00:06:45.060> in<00:06:45.419> a 00:06:46.129 --> 00:06:46.139 align:start position:0% our entire website which will come in a 00:06:46.139 --> 00:06:48.290 align:start position:0% our entire website which will come in a few<00:06:46.560> weeks<00:06:46.919> months<00:06:47.220> I'm<00:06:47.400> not<00:06:47.699> entirely<00:06:48.060> sure 00:06:48.290 --> 00:06:48.300 align:start position:0% few weeks months I'm not entirely sure 00:06:48.300 --> 00:06:50.930 align:start position:0% few weeks months I'm not entirely sure but<00:06:49.199> there<00:06:49.319> again<00:06:49.560> we<00:06:49.919> kind<00:06:50.160> of<00:06:50.340> a<00:06:50.460> huge<00:06:50.759> shout 00:06:50.930 --> 00:06:50.940 align:start position:0% but there again we kind of a huge shout 00:06:50.940 --> 00:06:53.350 align:start position:0% but there again we kind of a huge shout out<00:06:51.060> to<00:06:51.300> the<00:06:51.780> EF 00:06:53.350 --> 00:06:53.360 align:start position:0% out to the EF 00:06:53.360 --> 00:06:55.670 align:start position:0% out to the EF essential<00:06:54.360> ethereum.org<00:06:55.139> website<00:06:55.500> team 00:06:55.670 --> 00:06:55.680 align:start position:0% essential ethereum.org website team 00:06:55.680 --> 00:06:58.610 align:start position:0% essential ethereum.org website team because<00:06:55.919> they<00:06:56.280> are<00:06:56.400> the<00:06:56.580> ones<00:06:56.880> uh<00:06:57.479> doing<00:06:58.080> their 00:06:58.610 --> 00:06:58.620 align:start position:0% because they are the ones uh doing their 00:06:58.620 --> 00:07:02.689 align:start position:0% because they are the ones uh doing their our<00:06:58.860> new<00:06:59.100> website<00:06:59.479> and<00:07:00.800> so<00:07:01.800> we<00:07:02.220> know<00:07:02.400> that 00:07:02.689 --> 00:07:02.699 align:start position:0% our new website and so we know that 00:07:02.699 --> 00:07:04.610 align:start position:0% our new website and so we know that there's<00:07:03.120> a<00:07:03.300> lot<00:07:03.419> of<00:07:03.539> things<00:07:03.720> to<00:07:03.900> improve<00:07:04.259> but 00:07:04.610 --> 00:07:04.620 align:start position:0% there's a lot of things to improve but 00:07:04.620 --> 00:07:06.770 align:start position:0% there's a lot of things to improve but there<00:07:04.979> we<00:07:05.340> have<00:07:05.520> received<00:07:05.940> an<00:07:06.120> enormous<00:07:06.539> help 00:07:06.770 --> 00:07:06.780 align:start position:0% there we have received an enormous help 00:07:06.780 --> 00:07:10.010 align:start position:0% there we have received an enormous help from<00:07:07.080> the<00:07:07.319> EF<00:07:07.680> towards<00:07:08.520> improving<00:07:09.180> it<00:07:09.360> I'm 00:07:10.010 --> 00:07:10.020 align:start position:0% from the EF towards improving it I'm 00:07:10.020 --> 00:07:11.510 align:start position:0% from the EF towards improving it I'm sure<00:07:10.259> there<00:07:10.500> will<00:07:10.680> be<00:07:10.800> a<00:07:10.979> lot<00:07:11.039> of<00:07:11.160> things<00:07:11.280> that 00:07:11.510 --> 00:07:11.520 align:start position:0% sure there will be a lot of things that 00:07:11.520 --> 00:07:13.790 align:start position:0% sure there will be a lot of things that still<00:07:11.699> depend<00:07:12.000> on<00:07:12.120> us<00:07:12.300> but 00:07:13.790 --> 00:07:13.800 align:start position:0% still depend on us but 00:07:13.800 --> 00:07:16.129 align:start position:0% still depend on us but it<00:07:14.400> things<00:07:14.580> are<00:07:14.759> getting<00:07:14.940> better 00:07:16.129 --> 00:07:16.139 align:start position:0% it things are getting better 00:07:16.139 --> 00:07:19.969 align:start position:0% it things are getting better Also<00:07:16.919> regarding<00:07:18.020> support<00:07:19.020> on<00:07:19.380> our<00:07:19.560> Discord 00:07:19.969 --> 00:07:19.979 align:start position:0% Also regarding support on our Discord 00:07:19.979 --> 00:07:22.249 align:start position:0% Also regarding support on our Discord and<00:07:20.400> and<00:07:20.639> everywhere<00:07:21.120> I<00:07:21.660> think<00:07:21.720> with<00:07:22.020> the 00:07:22.249 --> 00:07:22.259 align:start position:0% and and everywhere I think with the 00:07:22.259 --> 00:07:24.830 align:start position:0% and and everywhere I think with the increasing<00:07:22.919> complexity<00:07:23.639> of<00:07:24.000> ethereum<00:07:24.479> and 00:07:24.830 --> 00:07:24.840 align:start position:0% increasing complexity of ethereum and 00:07:24.840 --> 00:07:25.969 align:start position:0% increasing complexity of ethereum and the<00:07:25.080> the 00:07:25.969 --> 00:07:25.979 align:start position:0% the the 00:07:25.979 --> 00:07:29.510 align:start position:0% the the increasing<00:07:26.759> demand<00:07:27.240> of<00:07:27.479> shipping<00:07:27.960> stuff 00:07:29.510 --> 00:07:29.520 align:start position:0% increasing demand of shipping stuff 00:07:29.520 --> 00:07:32.150 align:start position:0% increasing demand of shipping stuff um<00:07:29.639> just<00:07:30.180> being<00:07:30.479> there<00:07:30.900> like<00:07:31.380> our<00:07:31.620> time<00:07:31.919> being 00:07:32.150 --> 00:07:32.160 align:start position:0% um just being there like our time being 00:07:32.160 --> 00:07:34.249 align:start position:0% um just being there like our time being spent<00:07:32.460> on<00:07:32.699> supporting<00:07:33.300> individuals<00:07:33.900> in<00:07:34.139> the 00:07:34.249 --> 00:07:34.259 align:start position:0% spent on supporting individuals in the 00:07:34.259 --> 00:07:38.270 align:start position:0% spent on supporting individuals in the community<00:07:34.580> is<00:07:35.580> very<00:07:35.819> limited<00:07:36.300> and<00:07:37.259> we<00:07:38.160> need 00:07:38.270 --> 00:07:38.280 align:start position:0% community is very limited and we need 00:07:38.280 --> 00:07:40.850 align:start position:0% community is very limited and we need more<00:07:38.580> people<00:07:38.819> from<00:07:39.360> the<00:07:39.840> community<00:07:40.020> to<00:07:40.620> take 00:07:40.850 --> 00:07:40.860 align:start position:0% more people from the community to take 00:07:40.860 --> 00:07:44.930 align:start position:0% more people from the community to take over<00:07:41.099> to<00:07:41.520> to<00:07:42.060> help<00:07:42.539> educate<00:07:43.220> uh<00:07:44.220> educate 00:07:44.930 --> 00:07:44.940 align:start position:0% over to to help educate uh educate 00:07:44.940 --> 00:07:49.010 align:start position:0% over to to help educate uh educate others<00:07:45.419> about<00:07:46.380> how<00:07:46.800> to<00:07:46.919> use<00:07:47.099> gas<00:07:47.340> and 00:07:49.010 --> 00:07:49.020 align:start position:0% others about how to use gas and 00:07:49.020 --> 00:07:51.409 align:start position:0% others about how to use gas and this<00:07:49.740> kind<00:07:49.979> of<00:07:50.099> stuff 00:07:51.409 --> 00:07:51.419 align:start position:0% this kind of stuff 00:07:51.419 --> 00:07:53.990 align:start position:0% this kind of stuff uh<00:07:52.199> yeah<00:07:52.380> I<00:07:52.560> just<00:07:52.680> wanted<00:07:52.860> to<00:07:53.099> answer<00:07:53.580> the 00:07:53.990 --> 00:07:54.000 align:start position:0% uh yeah I just wanted to answer the 00:07:54.000 --> 00:07:55.610 align:start position:0% uh yeah I just wanted to answer the question<00:07:54.419> about<00:07:54.660> the<00:07:54.900> future<00:07:55.020> of<00:07:55.259> the<00:07:55.380> guest 00:07:55.610 --> 00:07:55.620 align:start position:0% question about the future of the guest 00:07:55.620 --> 00:07:58.670 align:start position:0% question about the future of the guest team<00:07:55.940> uh<00:07:56.940> so<00:07:57.240> far<00:07:57.419> people<00:07:57.660> were<00:07:58.080> were<00:07:58.319> quite 00:07:58.670 --> 00:07:58.680 align:start position:0% team uh so far people were were quite 00:07:58.680 --> 00:08:00.589 align:start position:0% team uh so far people were were quite positive<00:07:59.280> and<00:07:59.520> upbeat<00:07:59.940> so<00:08:00.060> I<00:08:00.180> wanted<00:08:00.300> to<00:08:00.479> be 00:08:00.589 --> 00:08:00.599 align:start position:0% positive and upbeat so I wanted to be 00:08:00.599 --> 00:08:03.529 align:start position:0% positive and upbeat so I wanted to be the<00:08:00.780> down<00:08:01.020> here<00:08:01.199> Downer<00:08:01.800> here<00:08:02.039> uh<00:08:02.880> I<00:08:03.120> think<00:08:03.240> I 00:08:03.529 --> 00:08:03.539 align:start position:0% the down here Downer here uh I think I 00:08:03.539 --> 00:08:05.570 align:start position:0% the down here Downer here uh I think I mean<00:08:03.660> it<00:08:03.840> makes<00:08:03.960> sense<00:08:04.319> that<00:08:04.800> so<00:08:05.340> much<00:08:05.400> of 00:08:05.570 --> 00:08:05.580 align:start position:0% mean it makes sense that so much of 00:08:05.580 --> 00:08:07.189 align:start position:0% mean it makes sense that so much of ethereum<00:08:06.000> has<00:08:06.180> been<00:08:06.360> relying<00:08:06.720> on<00:08:06.840> the<00:08:06.960> guest 00:08:07.189 --> 00:08:07.199 align:start position:0% ethereum has been relying on the guest 00:08:07.199 --> 00:08:10.189 align:start position:0% ethereum has been relying on the guest team<00:08:07.440> before<00:08:08.300> uh<00:08:09.300> there's<00:08:09.479> been<00:08:09.720> an<00:08:09.900> effort 00:08:10.189 --> 00:08:10.199 align:start position:0% team before uh there's been an effort 00:08:10.199 --> 00:08:12.050 align:start position:0% team before uh there's been an effort like<00:08:10.440> the<00:08:10.860> help<00:08:11.160> also<00:08:11.520> comes<00:08:11.759> from<00:08:11.880> other 00:08:12.050 --> 00:08:12.060 align:start position:0% like the help also comes from other 00:08:12.060 --> 00:08:16.129 align:start position:0% like the help also comes from other teams<00:08:12.479> like<00:08:13.080> for<00:08:13.380> example<00:08:14.060> uh<00:08:15.060> the<00:08:15.419> the<00:08:15.780> client 00:08:16.129 --> 00:08:16.139 align:start position:0% teams like for example uh the the client 00:08:16.139 --> 00:08:18.589 align:start position:0% teams like for example uh the the client sorry<00:08:16.440> the<00:08:16.680> consensus<00:08:17.039> layer<00:08:17.520> clients<00:08:18.060> are 00:08:18.589 --> 00:08:18.599 align:start position:0% sorry the consensus layer clients are 00:08:18.599 --> 00:08:21.650 align:start position:0% sorry the consensus layer clients are taking<00:08:18.780> part<00:08:19.139> of<00:08:19.379> the<00:08:19.680> the<00:08:20.520> trouble<00:08:21.300> the 00:08:21.650 --> 00:08:21.660 align:start position:0% taking part of the the trouble the 00:08:21.660 --> 00:08:23.809 align:start position:0% taking part of the the trouble the burden<00:08:21.960> away<00:08:22.139> from<00:08:22.379> us<00:08:22.500> there<00:08:23.460> will<00:08:23.699> probably 00:08:23.809 --> 00:08:23.819 align:start position:0% burden away from us there will probably 00:08:23.819 --> 00:08:26.930 align:start position:0% burden away from us there will probably be<00:08:24.120> this<00:08:24.419> kind<00:08:24.599> of<00:08:24.780> uh<00:08:25.259> of<00:08:25.800> other<00:08:26.220> efforts<00:08:26.759> in 00:08:26.930 --> 00:08:26.940 align:start position:0% be this kind of uh of other efforts in 00:08:26.940 --> 00:08:28.730 align:start position:0% be this kind of uh of other efforts in the<00:08:27.060> future<00:08:27.180> and<00:08:27.599> hopefully<00:08:28.080> we<00:08:28.319> can<00:08:28.500> just 00:08:28.730 --> 00:08:28.740 align:start position:0% the future and hopefully we can just 00:08:28.740 --> 00:08:32.949 align:start position:0% the future and hopefully we can just become<00:08:29.340> a<00:08:29.520> bit<00:08:29.639> more<00:08:30.259> uh<00:08:31.259> redundant<00:08:32.099> in<00:08:32.339> a<00:08:32.459> way 00:08:32.949 --> 00:08:32.959 align:start position:0% become a bit more uh redundant in a way 00:08:32.959 --> 00:08:37.730 align:start position:0% become a bit more uh redundant in a way and<00:08:33.959> uh<00:08:34.440> this<00:08:35.339> this<00:08:35.580> is<00:08:35.760> this<00:08:36.180> excuse<00:08:37.020> me<00:08:37.200> that 00:08:37.730 --> 00:08:37.740 align:start position:0% and uh this this is this excuse me that 00:08:37.740 --> 00:08:40.490 align:start position:0% and uh this this is this excuse me that would<00:08:37.919> be<00:08:38.039> uh<00:08:38.399> true<00:08:38.640> decentralization 00:08:40.490 --> 00:08:40.500 align:start position:0% would be uh true decentralization 00:08:40.500 --> 00:08:42.889 align:start position:0% would be uh true decentralization to<00:08:40.919> answer<00:08:41.099> as<00:08:41.339> well<00:08:41.539> also<00:08:42.539> talking<00:08:42.719> about 00:08:42.889 --> 00:08:42.899 align:start position:0% to answer as well also talking about 00:08:42.899 --> 00:08:44.410 align:start position:0% to answer as well also talking about support 00:08:44.410 --> 00:08:44.420 align:start position:0% support 00:08:44.420 --> 00:08:47.269 align:start position:0% support if<00:08:45.420> you<00:08:45.540> guys<00:08:45.720> have<00:08:45.959> experience<00:08:46.320> with<00:08:46.620> get<00:08:46.800> and 00:08:47.269 --> 00:08:47.279 align:start position:0% if you guys have experience with get and 00:08:47.279 --> 00:08:48.430 align:start position:0% if you guys have experience with get and want<00:08:47.580> to 00:08:48.430 --> 00:08:48.440 align:start position:0% want to 00:08:48.440 --> 00:08:53.329 align:start position:0% want to help<00:08:49.440> us<00:08:49.620> with<00:08:50.339> the<00:08:50.519> Discord 00:08:53.329 --> 00:08:53.339 align:start position:0% 00:08:53.339 --> 00:08:56.690 align:start position:0% yeah<00:08:54.000> we're<00:08:54.300> really<00:08:54.779> looking<00:08:55.560> for<00:08:56.040> for<00:08:56.339> people 00:08:56.690 --> 00:08:56.700 align:start position:0% yeah we're really looking for for people 00:08:56.700 --> 00:08:58.430 align:start position:0% yeah we're really looking for for people who<00:08:57.240> can<00:08:57.360> do<00:08:57.600> it 00:08:58.430 --> 00:08:58.440 align:start position:0% who can do it 00:08:58.440 --> 00:09:00.350 align:start position:0% who can do it although<00:08:58.980> I<00:08:59.100> know<00:08:59.279> if<00:08:59.459> you<00:08:59.640> guys<00:08:59.760> can<00:09:00.060> work 00:09:00.350 --> 00:09:00.360 align:start position:0% although I know if you guys can work 00:09:00.360 --> 00:09:02.570 align:start position:0% although I know if you guys can work with<00:09:00.660> guests<00:09:01.140> like<00:09:01.920> you<00:09:02.100> have<00:09:02.279> experience 00:09:02.570 --> 00:09:02.580 align:start position:0% with guests like you have experience 00:09:02.580 --> 00:09:04.790 align:start position:0% with guests like you have experience then<00:09:02.820> you<00:09:03.060> probably<00:09:03.240> get<00:09:03.899> better<00:09:04.500> jobs 00:09:04.790 --> 00:09:04.800 align:start position:0% then you probably get better jobs 00:09:04.800 --> 00:09:08.630 align:start position:0% then you probably get better jobs elsewhere<00:09:05.339> but<00:09:05.580> you<00:09:05.820> know<00:09:05.880> just 00:09:08.630 --> 00:09:08.640 align:start position:0% elsewhere but you know just 00:09:08.640 --> 00:09:12.829 align:start position:0% elsewhere but you know just yeah<00:09:09.420> for<00:09:10.260> technical<00:09:10.740> support<00:09:10.920> yeah 00:09:12.829 --> 00:09:12.839 align:start position:0% yeah for technical support yeah 00:09:12.839 --> 00:09:14.930 align:start position:0% yeah for technical support yeah this<00:09:13.380> is<00:09:13.500> Cena<00:09:13.740> by<00:09:14.040> the<00:09:14.160> way<00:09:14.220> he's<00:09:14.519> also<00:09:14.820> part 00:09:14.930 --> 00:09:14.940 align:start position:0% this is Cena by the way he's also part 00:09:14.940 --> 00:09:15.670 align:start position:0% this is Cena by the way he's also part of<00:09:15.060> the<00:09:15.180> guest<00:09:15.480> team 00:09:15.670 --> 00:09:15.680 align:start position:0% of the guest team 00:09:15.680 --> 00:09:19.310 align:start position:0% of the guest team [Applause] 00:09:19.310 --> 00:09:19.320 align:start position:0% [Applause] 00:09:19.320 --> 00:09:21.290 align:start position:0% [Applause] yeah<00:09:19.620> so<00:09:19.740> Cena<00:09:20.040> didn't<00:09:20.279> want<00:09:20.519> to<00:09:20.640> be<00:09:20.760> here<00:09:20.940> but 00:09:21.290 --> 00:09:21.300 align:start position:0% yeah so Cena didn't want to be here but 00:09:21.300 --> 00:09:24.530 align:start position:0% yeah so Cena didn't want to be here but uh 00:09:24.530 --> 00:09:24.540 align:start position:0% 00:09:24.540 --> 00:09:26.750 align:start position:0% thank<00:09:25.080> you<00:09:25.200> for<00:09:25.380> being<00:09:25.560> here 00:09:26.750 --> 00:09:26.760 align:start position:0% thank you for being here 00:09:26.760 --> 00:09:28.790 align:start position:0% thank you for being here but<00:09:27.300> Cena<00:09:27.660> gave<00:09:27.959> a<00:09:28.080> good<00:09:28.200> lead<00:09:28.260> into<00:09:28.500> my 00:09:28.790 --> 00:09:28.800 align:start position:0% but Cena gave a good lead into my 00:09:28.800 --> 00:09:31.730 align:start position:0% but Cena gave a good lead into my question<00:09:28.980> which<00:09:29.580> is<00:09:29.760> to<00:09:30.300> ask<00:09:30.540> everyone<00:09:31.200> who 00:09:31.730 --> 00:09:31.740 align:start position:0% question which is to ask everyone who 00:09:31.740 --> 00:09:34.610 align:start position:0% question which is to ask everyone who who's<00:09:32.220> in<00:09:32.519> the<00:09:32.700> Geth<00:09:32.940> team<00:09:33.180> either<00:09:34.080> on<00:09:34.380> stage 00:09:34.610 --> 00:09:34.620 align:start position:0% who's in the Geth team either on stage 00:09:34.620 --> 00:09:37.009 align:start position:0% who's in the Geth team either on stage or<00:09:34.800> off<00:09:34.980> stage<00:09:35.339> where<00:09:35.880> do<00:09:36.060> you<00:09:36.180> most<00:09:36.360> need<00:09:36.720> help 00:09:37.009 --> 00:09:37.019 align:start position:0% or off stage where do you most need help 00:09:37.019 --> 00:09:39.949 align:start position:0% or off stage where do you most need help individually<00:09:37.860> like<00:09:38.399> in<00:09:39.240> parts<00:09:39.360> of<00:09:39.600> projects 00:09:39.949 --> 00:09:39.959 align:start position:0% individually like in parts of projects 00:09:39.959 --> 00:09:41.269 align:start position:0% individually like in parts of projects you're<00:09:40.200> working<00:09:40.440> on<00:09:40.620> whether<00:09:40.860> it's<00:09:41.100> like 00:09:41.269 --> 00:09:41.279 align:start position:0% you're working on whether it's like 00:09:41.279 --> 00:09:43.009 align:start position:0% you're working on whether it's like strategic<00:09:41.820> stuff<00:09:42.000> for<00:09:42.240> the<00:09:42.420> future<00:09:42.540> or<00:09:42.899> like 00:09:43.009 --> 00:09:43.019 align:start position:0% strategic stuff for the future or like 00:09:43.019 --> 00:09:45.110 align:start position:0% strategic stuff for the future or like something<00:09:43.260> right<00:09:43.560> here<00:09:43.800> right<00:09:44.040> now<00:09:44.279> is<00:09:44.940> there 00:09:45.110 --> 00:09:45.120 align:start position:0% something right here right now is there 00:09:45.120 --> 00:09:46.670 align:start position:0% something right here right now is there anything<00:09:45.240> you<00:09:45.600> can<00:09:45.720> share<00:09:46.019> with<00:09:46.260> us<00:09:46.380> as 00:09:46.670 --> 00:09:46.680 align:start position:0% anything you can share with us as 00:09:46.680 --> 00:09:49.610 align:start position:0% anything you can share with us as Community<00:09:46.980> to<00:09:47.459> help<00:09:47.640> us<00:09:47.880> better<00:09:48.720> support<00:09:49.080> what 00:09:49.610 --> 00:09:49.620 align:start position:0% Community to help us better support what 00:09:49.620 --> 00:09:51.889 align:start position:0% Community to help us better support what you<00:09:49.800> guys<00:09:49.980> are<00:09:50.220> doing<00:09:50.399> like 00:09:51.889 --> 00:09:51.899 align:start position:0% you guys are doing like 00:09:51.899 --> 00:09:54.070 align:start position:0% you guys are doing like can<00:09:52.440> that<00:09:52.620> work 00:09:54.070 --> 00:09:54.080 align:start position:0% can that work 00:09:54.080 --> 00:09:56.389 align:start position:0% can that work the<00:09:55.080> first<00:09:55.200> thing<00:09:55.380> that<00:09:55.560> comes<00:09:55.920> to<00:09:56.040> mind<00:09:56.160> is 00:09:56.389 --> 00:09:56.399 align:start position:0% the first thing that comes to mind is 00:09:56.399 --> 00:09:58.550 align:start position:0% the first thing that comes to mind is please<00:09:56.640> be<00:09:56.820> polite<00:09:57.180> on<00:09:57.360> PRS 00:09:58.550 --> 00:09:58.560 align:start position:0% please be polite on PRS 00:09:58.560 --> 00:10:01.210 align:start position:0% please be polite on PRS yeah<00:09:59.100> so<00:09:59.339> I<00:09:59.580> guess<00:09:59.820> with<00:10:00.000> the<00:10:00.180> guest<00:10:00.300> team<00:10:00.540> our 00:10:01.210 --> 00:10:01.220 align:start position:0% yeah so I guess with the guest team our 00:10:01.220 --> 00:10:04.610 align:start position:0% yeah so I guess with the guest team our bottleneck<00:10:02.220> our<00:10:02.459> single<00:10:03.060> actually<00:10:04.019> single 00:10:04.610 --> 00:10:04.620 align:start position:0% bottleneck our single actually single 00:10:04.620 --> 00:10:07.430 align:start position:0% bottleneck our single actually single bottleneck<00:10:05.220> is<00:10:05.640> pull<00:10:06.000> request<00:10:06.360> reviews 00:10:07.430 --> 00:10:07.440 align:start position:0% bottleneck is pull request reviews 00:10:07.440 --> 00:10:09.949 align:start position:0% bottleneck is pull request reviews we<00:10:08.279> have<00:10:08.399> a<00:10:08.519> lot<00:10:08.640> of<00:10:08.760> very<00:10:09.060> nice 00:10:09.949 --> 00:10:09.959 align:start position:0% we have a lot of very nice 00:10:09.959 --> 00:10:12.170 align:start position:0% we have a lot of very nice members<00:10:10.620> on<00:10:10.860> the<00:10:10.980> team<00:10:11.160> who<00:10:11.459> can<00:10:11.640> really<00:10:11.880> churn 00:10:12.170 --> 00:10:12.180 align:start position:0% members on the team who can really churn 00:10:12.180 --> 00:10:14.030 align:start position:0% members on the team who can really churn out<00:10:12.420> code<00:10:12.660> super<00:10:12.899> fast 00:10:14.030 --> 00:10:14.040 align:start position:0% out code super fast 00:10:14.040 --> 00:10:16.250 align:start position:0% out code super fast maybe<00:10:14.760> a<00:10:15.060> few<00:10:15.180> people<00:10:15.360> way<00:10:15.660> too<00:10:15.839> fast<00:10:15.959> like 00:10:16.250 --> 00:10:16.260 align:start position:0% maybe a few people way too fast like 00:10:16.260 --> 00:10:18.829 align:start position:0% maybe a few people way too fast like Gary<00:10:16.560> and<00:10:17.160> we<00:10:17.339> can't<00:10:17.459> keep<00:10:17.640> up<00:10:17.820> with<00:10:17.940> him 00:10:18.829 --> 00:10:18.839 align:start position:0% Gary and we can't keep up with him 00:10:18.839 --> 00:10:21.590 align:start position:0% Gary and we can't keep up with him and<00:10:19.620> the<00:10:19.920> the<00:10:20.160> and<00:10:20.760> we<00:10:20.940> also<00:10:21.180> have<00:10:21.300> a<00:10:21.420> lot<00:10:21.480> of 00:10:21.590 --> 00:10:21.600 align:start position:0% and the the and we also have a lot of 00:10:21.600 --> 00:10:24.230 align:start position:0% and the the and we also have a lot of external<00:10:22.019> contributions<00:10:22.640> and<00:10:23.640> there's<00:10:23.880> the 00:10:24.230 --> 00:10:24.240 align:start position:0% external contributions and there's the 00:10:24.240 --> 00:10:25.790 align:start position:0% external contributions and there's the problem<00:10:24.360> is<00:10:24.660> that<00:10:24.959> the<00:10:25.200> code<00:10:25.380> is<00:10:25.620> super 00:10:25.790 --> 00:10:25.800 align:start position:0% problem is that the code is super 00:10:25.800 --> 00:10:28.490 align:start position:0% problem is that the code is super sensitive<00:10:26.279> so<00:10:26.820> it<00:10:27.660> kind<00:10:27.779> of<00:10:27.839> always<00:10:28.019> boils 00:10:28.490 --> 00:10:28.500 align:start position:0% sensitive so it kind of always boils 00:10:28.500 --> 00:10:30.290 align:start position:0% sensitive so it kind of always boils down<00:10:28.620> to<00:10:28.860> a<00:10:29.040> couple<00:10:29.160> people<00:10:29.459> having<00:10:29.880> to<00:10:30.180> review 00:10:30.290 --> 00:10:30.300 align:start position:0% down to a couple people having to review 00:10:30.300 --> 00:10:32.329 align:start position:0% down to a couple people having to review everything<00:10:30.779> and<00:10:31.440> having<00:10:31.620> to<00:10:31.860> do<00:10:31.980> a<00:10:32.160> lot<00:10:32.220> of 00:10:32.329 --> 00:10:32.339 align:start position:0% everything and having to do a lot of 00:10:32.339 --> 00:10:34.310 align:start position:0% everything and having to do a lot of context<00:10:32.760> jumps<00:10:33.120> to<00:10:33.300> review<00:10:33.420> them 00:10:34.310 --> 00:10:34.320 align:start position:0% context jumps to review them 00:10:34.320 --> 00:10:37.250 align:start position:0% context jumps to review them and<00:10:35.160> unfortunately<00:10:35.940> this<00:10:36.300> is<00:10:36.420> our<00:10:36.720> Achilles 00:10:37.250 --> 00:10:37.260 align:start position:0% and unfortunately this is our Achilles 00:10:37.260 --> 00:10:39.530 align:start position:0% and unfortunately this is our Achilles heel<00:10:37.620> because<00:10:37.800> we<00:10:38.220> have<00:10:38.399> absolutely<00:10:38.880> no<00:10:39.180> idea 00:10:39.530 --> 00:10:39.540 align:start position:0% heel because we have absolutely no idea 00:10:39.540 --> 00:10:41.090 align:start position:0% heel because we have absolutely no idea how<00:10:39.839> to<00:10:40.019> solve<00:10:40.320> it 00:10:41.090 --> 00:10:41.100 align:start position:0% how to solve it 00:10:41.100 --> 00:10:43.070 align:start position:0% how to solve it definitely<00:10:41.760> more<00:10:42.060> people<00:10:42.240> on<00:10:42.540> the<00:10:42.660> team<00:10:42.839> more 00:10:43.070 --> 00:10:43.080 align:start position:0% definitely more people on the team more 00:10:43.080 --> 00:10:44.630 align:start position:0% definitely more people on the team more reviews<00:10:43.380> help 00:10:44.630 --> 00:10:44.640 align:start position:0% reviews help 00:10:44.640 --> 00:10:47.750 align:start position:0% reviews help but<00:10:45.540> uh<00:10:45.959> it's<00:10:46.740> not<00:10:46.920> an<00:10:47.100> easy<00:10:47.279> to<00:10:47.459> solve 00:10:47.750 --> 00:10:47.760 align:start position:0% but uh it's not an easy to solve 00:10:47.760 --> 00:10:49.130 align:start position:0% but uh it's not an easy to solve situation<00:10:48.120> because<00:10:48.300> we<00:10:48.540> can't<00:10:48.720> just<00:10:48.839> hire 00:10:49.130 --> 00:10:49.140 align:start position:0% situation because we can't just hire 00:10:49.140 --> 00:10:52.850 align:start position:0% situation because we can't just hire somebody<00:10:49.380> to<00:10:49.800> do<00:10:50.040> code<00:10:51.000> reviews<00:10:51.300> since<00:10:52.140> I<00:10:52.740> mean 00:10:52.850 --> 00:10:52.860 align:start position:0% somebody to do code reviews since I mean 00:10:52.860 --> 00:10:54.530 align:start position:0% somebody to do code reviews since I mean the<00:10:52.980> entire<00:10:53.220> network<00:10:53.399> kind<00:10:53.760> of<00:10:53.880> depends<00:10:54.240> on<00:10:54.420> it 00:10:54.530 --> 00:10:54.540 align:start position:0% the entire network kind of depends on it 00:10:54.540 --> 00:10:56.630 align:start position:0% the entire network kind of depends on it so<00:10:55.320> that's<00:10:55.560> uh 00:10:56.630 --> 00:10:56.640 align:start position:0% so that's uh 00:10:56.640 --> 00:10:58.370 align:start position:0% so that's uh we're<00:10:57.000> really<00:10:57.120> open<00:10:57.360> for<00:10:57.600> suggestions<00:10:57.959> on<00:10:58.140> how 00:10:58.370 --> 00:10:58.380 align:start position:0% we're really open for suggestions on how 00:10:58.380 --> 00:10:59.690 align:start position:0% we're really open for suggestions on how to<00:10:58.560> solve<00:10:58.860> that 00:10:59.690 --> 00:10:59.700 align:start position:0% to solve that 00:10:59.700 --> 00:11:02.090 align:start position:0% to solve that I<00:11:00.240> think<00:11:00.360> two<00:11:00.720> things<00:11:00.899> also<00:11:01.260> come<00:11:01.440> to<00:11:01.560> mind<00:11:01.740> for 00:11:02.090 --> 00:11:02.100 align:start position:0% I think two things also come to mind for 00:11:02.100 --> 00:11:05.269 align:start position:0% I think two things also come to mind for me<00:11:02.220> the<00:11:02.760> first<00:11:03.000> is<00:11:03.680> helping<00:11:04.680> create<00:11:04.920> better 00:11:05.269 --> 00:11:05.279 align:start position:0% me the first is helping create better 00:11:05.279 --> 00:11:07.370 align:start position:0% me the first is helping create better onboarding<00:11:06.000> mechanisms<00:11:06.720> for<00:11:06.959> people<00:11:07.140> to 00:11:07.370 --> 00:11:07.380 align:start position:0% onboarding mechanisms for people to 00:11:07.380 --> 00:11:09.650 align:start position:0% onboarding mechanisms for people to contribute<00:11:07.680> to<00:11:07.860> Geth<00:11:08.519> right<00:11:09.060> now<00:11:09.180> it's<00:11:09.360> kind 00:11:09.650 --> 00:11:09.660 align:start position:0% contribute to Geth right now it's kind 00:11:09.660 --> 00:11:11.750 align:start position:0% contribute to Geth right now it's kind of<00:11:09.779> you<00:11:10.200> know<00:11:10.260> look<00:11:10.620> at<00:11:10.800> the<00:11:10.980> code<00:11:11.220> base<00:11:11.399> find 00:11:11.750 --> 00:11:11.760 align:start position:0% of you know look at the code base find 00:11:11.760 --> 00:11:13.250 align:start position:0% of you know look at the code base find something<00:11:12.000> to<00:11:12.180> fix<00:11:12.300> look<00:11:12.600> at<00:11:12.720> the<00:11:12.779> issues<00:11:13.019> find 00:11:13.250 --> 00:11:13.260 align:start position:0% something to fix look at the issues find 00:11:13.260 --> 00:11:14.870 align:start position:0% something to fix look at the issues find something<00:11:13.440> to<00:11:13.680> fix 00:11:14.870 --> 00:11:14.880 align:start position:0% something to fix 00:11:14.880 --> 00:11:16.250 align:start position:0% something to fix um I'm<00:11:15.180> taking<00:11:15.360> you<00:11:15.660> don't<00:11:15.899> like<00:11:16.079> your 00:11:16.250 --> 00:11:16.260 align:start position:0% um I'm taking you don't like your 00:11:16.260 --> 00:11:19.790 align:start position:0% um I'm taking you don't like your onboarding<00:11:16.800> experience 00:11:19.790 --> 00:11:19.800 align:start position:0% 00:11:19.800 --> 00:11:21.650 align:start position:0% no<00:11:20.160> I<00:11:20.279> think<00:11:20.519> my<00:11:20.700> onboarding<00:11:21.180> experience<00:11:21.420> has 00:11:21.650 --> 00:11:21.660 align:start position:0% no I think my onboarding experience has 00:11:21.660 --> 00:11:22.850 align:start position:0% no I think my onboarding experience has been<00:11:21.839> excellent 00:11:22.850 --> 00:11:22.860 align:start position:0% been excellent 00:11:22.860 --> 00:11:25.069 align:start position:0% been excellent it's<00:11:23.339> been<00:11:23.700> such<00:11:23.880> a<00:11:24.000> fun<00:11:24.120> time<00:11:24.360> working<00:11:24.720> on<00:11:24.959> the 00:11:25.069 --> 00:11:25.079 align:start position:0% it's been such a fun time working on the 00:11:25.079 --> 00:11:27.650 align:start position:0% it's been such a fun time working on the kids 00:11:27.650 --> 00:11:27.660 align:start position:0% 00:11:27.660 --> 00:11:29.690 align:start position:0% no<00:11:28.140> but<00:11:28.380> I<00:11:28.500> think<00:11:28.620> seriously<00:11:29.100> a<00:11:29.399> lot<00:11:29.519> of<00:11:29.640> people 00:11:29.690 --> 00:11:29.700 align:start position:0% no but I think seriously a lot of people 00:11:29.700 --> 00:11:31.670 align:start position:0% no but I think seriously a lot of people have<00:11:29.940> talked<00:11:30.300> to<00:11:30.360> me<00:11:30.540> saying<00:11:30.959> I<00:11:31.200> have<00:11:31.320> no<00:11:31.500> idea 00:11:31.670 --> 00:11:31.680 align:start position:0% have talked to me saying I have no idea 00:11:31.680 --> 00:11:33.470 align:start position:0% have talked to me saying I have no idea how<00:11:31.920> to<00:11:32.040> start<00:11:32.399> working<00:11:32.640> in<00:11:32.880> core<00:11:33.000> development 00:11:33.470 --> 00:11:33.480 align:start position:0% how to start working in core development 00:11:33.480 --> 00:11:36.050 align:start position:0% how to start working in core development and<00:11:34.140> you<00:11:34.800> know<00:11:34.860> some<00:11:35.459> people<00:11:35.640> like<00:11:35.880> work 00:11:36.050 --> 00:11:36.060 align:start position:0% and you know some people like work 00:11:36.060 --> 00:11:37.550 align:start position:0% and you know some people like work through<00:11:36.300> that<00:11:36.420> filter<00:11:36.600> themselves<00:11:37.079> and<00:11:37.380> they 00:11:37.550 --> 00:11:37.560 align:start position:0% through that filter themselves and they 00:11:37.560 --> 00:11:39.170 align:start position:0% through that filter themselves and they find<00:11:37.680> issues<00:11:38.100> and<00:11:38.279> they<00:11:38.459> start<00:11:38.579> contributing 00:11:39.170 --> 00:11:39.180 align:start position:0% find issues and they start contributing 00:11:39.180 --> 00:11:41.030 align:start position:0% find issues and they start contributing and<00:11:39.420> they<00:11:39.600> end<00:11:39.720> up<00:11:39.839> in<00:11:39.959> that<00:11:40.140> position<00:11:40.320> but<00:11:40.920> I 00:11:41.030 --> 00:11:41.040 align:start position:0% and they end up in that position but I 00:11:41.040 --> 00:11:42.050 align:start position:0% and they end up in that position but I think<00:11:41.160> that<00:11:41.279> we<00:11:41.399> could<00:11:41.579> build<00:11:41.760> some 00:11:42.050 --> 00:11:42.060 align:start position:0% think that we could build some 00:11:42.060 --> 00:11:43.790 align:start position:0% think that we could build some mechanisms<00:11:42.660> for<00:11:42.899> more<00:11:43.019> people<00:11:43.200> to<00:11:43.380> contribute 00:11:43.790 --> 00:11:43.800 align:start position:0% mechanisms for more people to contribute 00:11:43.800 --> 00:11:45.530 align:start position:0% mechanisms for more people to contribute and<00:11:44.220> I<00:11:44.339> had<00:11:44.459> this<00:11:44.640> idea<00:11:44.880> that<00:11:45.060> I've<00:11:45.180> started 00:11:45.530 --> 00:11:45.540 align:start position:0% and I had this idea that I've started 00:11:45.540 --> 00:11:46.670 align:start position:0% and I had this idea that I've started working<00:11:45.720> on<00:11:45.899> a<00:11:45.959> little<00:11:46.079> bit<00:11:46.200> is<00:11:46.380> like<00:11:46.560> having 00:11:46.670 --> 00:11:46.680 align:start position:0% working on a little bit is like having 00:11:46.680 --> 00:11:48.710 align:start position:0% working on a little bit is like having some<00:11:46.980> sort<00:11:47.160> of<00:11:47.220> like<00:11:47.339> capture<00:11:47.700> the<00:11:47.880> flag<00:11:48.060> that 00:11:48.710 --> 00:11:48.720 align:start position:0% some sort of like capture the flag that 00:11:48.720 --> 00:11:50.210 align:start position:0% some sort of like capture the flag that has<00:11:48.899> like<00:11:49.079> basic<00:11:49.440> flags<00:11:49.800> for<00:11:49.920> people<00:11:50.040> to 00:11:50.210 --> 00:11:50.220 align:start position:0% has like basic flags for people to 00:11:50.220 --> 00:11:52.250 align:start position:0% has like basic flags for people to capture<00:11:50.519> where<00:11:51.060> you<00:11:51.480> do<00:11:51.660> like<00:11:51.959> a<00:11:52.079> core 00:11:52.250 --> 00:11:52.260 align:start position:0% capture where you do like a core 00:11:52.260 --> 00:11:54.230 align:start position:0% capture where you do like a core development<00:11:52.740> task<00:11:52.980> like<00:11:53.339> add<00:11:53.579> a<00:11:53.760> new<00:11:53.820> OP<00:11:54.000> code 00:11:54.230 --> 00:11:54.240 align:start position:0% development task like add a new OP code 00:11:54.240 --> 00:11:56.870 align:start position:0% development task like add a new OP code or<00:11:54.540> fix<00:11:54.779> some<00:11:55.140> sort<00:11:55.320> of<00:11:55.440> bug<00:11:55.560> or<00:11:55.860> go<00:11:56.339> through<00:11:56.519> an 00:11:56.870 --> 00:11:56.880 align:start position:0% or fix some sort of bug or go through an 00:11:56.880 --> 00:11:59.750 align:start position:0% or fix some sort of bug or go through an invalid<00:11:57.660> trace<00:11:57.899> of<00:11:58.019> the<00:11:58.140> evm<00:11:58.620> and<00:11:59.399> you're<00:11:59.519> able 00:11:59.750 --> 00:11:59.760 align:start position:0% invalid trace of the evm and you're able 00:11:59.760 --> 00:12:01.250 align:start position:0% invalid trace of the evm and you're able to<00:11:59.880> resolve<00:12:00.240> it<00:12:00.360> and<00:12:00.480> run<00:12:00.660> a<00:12:00.839> program<00:12:00.959> and 00:12:01.250 --> 00:12:01.260 align:start position:0% to resolve it and run a program and 00:12:01.260 --> 00:12:03.170 align:start position:0% to resolve it and run a program and verify<00:12:01.620> that<00:12:01.800> you<00:12:01.920> did<00:12:02.040> it<00:12:02.160> correctly<00:12:02.519> and<00:12:03.060> so 00:12:03.170 --> 00:12:03.180 align:start position:0% verify that you did it correctly and so 00:12:03.180 --> 00:12:05.449 align:start position:0% verify that you did it correctly and so that's<00:12:03.360> like<00:12:03.540> a<00:12:03.779> very<00:12:03.959> you<00:12:04.680> know<00:12:04.740> binary 00:12:05.449 --> 00:12:05.459 align:start position:0% that's like a very you know binary 00:12:05.459 --> 00:12:07.370 align:start position:0% that's like a very you know binary system<00:12:05.760> of<00:12:06.060> like<00:12:06.240> I<00:12:06.600> did<00:12:06.720> this<00:12:06.899> right<00:12:07.019> and<00:12:07.260> so 00:12:07.370 --> 00:12:07.380 align:start position:0% system of like I did this right and so 00:12:07.380 --> 00:12:08.930 align:start position:0% system of like I did this right and so now<00:12:07.500> I<00:12:07.620> can<00:12:07.680> move<00:12:07.800> on<00:12:07.920> to<00:12:08.040> the<00:12:08.160> next<00:12:08.279> thing<00:12:08.459> and 00:12:08.930 --> 00:12:08.940 align:start position:0% now I can move on to the next thing and 00:12:08.940 --> 00:12:09.949 align:start position:0% now I can move on to the next thing and then<00:12:09.000> once<00:12:09.180> you<00:12:09.300> go<00:12:09.420> through<00:12:09.480> that<00:12:09.660> then<00:12:09.839> it's 00:12:09.949 --> 00:12:09.959 align:start position:0% then once you go through that then it's 00:12:09.959 --> 00:12:11.090 align:start position:0% then once you go through that then it's a<00:12:10.079> little<00:12:10.140> bit<00:12:10.260> easier<00:12:10.440> to<00:12:10.680> come<00:12:10.800> into<00:12:10.920> the 00:12:11.090 --> 00:12:11.100 align:start position:0% a little bit easier to come into the 00:12:11.100 --> 00:12:12.470 align:start position:0% a little bit easier to come into the whole<00:12:11.220> guest<00:12:11.519> process<00:12:11.760> and<00:12:11.940> figure<00:12:12.120> out<00:12:12.300> like 00:12:12.470 --> 00:12:12.480 align:start position:0% whole guest process and figure out like 00:12:12.480 --> 00:12:14.509 align:start position:0% whole guest process and figure out like okay<00:12:12.899> why<00:12:13.260> did<00:12:13.380> they<00:12:13.500> not<00:12:13.620> like<00:12:13.740> my<00:12:13.920> PR<00:12:14.100> how<00:12:14.459> do 00:12:14.509 --> 00:12:14.519 align:start position:0% okay why did they not like my PR how do 00:12:14.519 --> 00:12:16.970 align:start position:0% okay why did they not like my PR how do I<00:12:14.640> get<00:12:14.760> this<00:12:14.880> PR<00:12:15.380> to<00:12:16.380> be<00:12:16.500> accepted<00:12:16.860> and 00:12:16.970 --> 00:12:16.980 align:start position:0% I get this PR to be accepted and 00:12:16.980 --> 00:12:18.410 align:start position:0% I get this PR to be accepted and everything<00:12:17.160> so<00:12:17.760> I<00:12:17.820> think<00:12:18.000> that<00:12:18.120> would<00:12:18.240> be<00:12:18.360> a 00:12:18.410 --> 00:12:18.420 align:start position:0% everything so I think that would be a 00:12:18.420 --> 00:12:19.910 align:start position:0% everything so I think that would be a cool<00:12:18.660> thing<00:12:18.839> for<00:12:19.019> people<00:12:19.140> to<00:12:19.320> contribute<00:12:19.680> if 00:12:19.910 --> 00:12:19.920 align:start position:0% cool thing for people to contribute if 00:12:19.920 --> 00:12:21.230 align:start position:0% cool thing for people to contribute if that's<00:12:20.459> something<00:12:20.579> you<00:12:20.760> want<00:12:20.880> to<00:12:21.000> contribute 00:12:21.230 --> 00:12:21.240 align:start position:0% that's something you want to contribute 00:12:21.240 --> 00:12:23.449 align:start position:0% that's something you want to contribute to<00:12:21.360> I'm<00:12:21.899> happy<00:12:22.140> to<00:12:22.320> talk<00:12:22.680> offline<00:12:23.040> about<00:12:23.279> that 00:12:23.449 --> 00:12:23.459 align:start position:0% to I'm happy to talk offline about that 00:12:23.459 --> 00:12:25.250 align:start position:0% to I'm happy to talk offline about that and<00:12:24.000> the<00:12:24.180> other<00:12:24.300> thing<00:12:24.420> that<00:12:24.540> I<00:12:24.720> think<00:12:24.779> that<00:12:24.959> we 00:12:25.250 --> 00:12:25.260 align:start position:0% and the other thing that I think that we 00:12:25.260 --> 00:12:26.930 align:start position:0% and the other thing that I think that we could<00:12:25.380> use<00:12:25.440> help<00:12:25.620> with<00:12:25.800> I<00:12:25.980> think<00:12:26.100> like<00:12:26.279> all<00:12:26.820> of 00:12:26.930 --> 00:12:26.940 align:start position:0% could use help with I think like all of 00:12:26.940 --> 00:12:28.550 align:start position:0% could use help with I think like all of the<00:12:27.060> execution<00:12:27.300> layers<00:12:27.600> could<00:12:28.079> use<00:12:28.260> help<00:12:28.440> with 00:12:28.550 --> 00:12:28.560 align:start position:0% the execution layers could use help with 00:12:28.560 --> 00:12:31.550 align:start position:0% the execution layers could use help with is<00:12:29.000> working<00:12:30.000> on<00:12:30.180> the<00:12:30.300> Json<00:12:30.540> RPC<00:12:31.019> so<00:12:31.320> that<00:12:31.440> this 00:12:31.550 --> 00:12:31.560 align:start position:0% is working on the Json RPC so that this 00:12:31.560 --> 00:12:33.530 align:start position:0% is working on the Json RPC so that this is<00:12:31.680> an<00:12:31.740> interface<00:12:32.160> that's<00:12:32.339> a<00:12:32.579> little<00:12:32.640> bit<00:12:32.820> more 00:12:33.530 --> 00:12:33.540 align:start position:0% is an interface that's a little bit more 00:12:33.540 --> 00:12:36.470 align:start position:0% is an interface that's a little bit more standard<00:12:33.899> across<00:12:34.320> all<00:12:34.500> clients<00:12:34.920> I<00:12:35.579> think<00:12:35.700> the 00:12:36.470 --> 00:12:36.480 align:start position:0% standard across all clients I think the 00:12:36.480 --> 00:12:38.990 align:start position:0% standard across all clients I think the ideal<00:12:37.260> world<00:12:37.560> is<00:12:37.920> that<00:12:38.100> a<00:12:38.339> client<00:12:38.640> is<00:12:38.820> just 00:12:38.990 --> 00:12:39.000 align:start position:0% ideal world is that a client is just 00:12:39.000 --> 00:12:41.210 align:start position:0% ideal world is that a client is just simply<00:12:39.240> a<00:12:39.420> black<00:12:39.540> box<00:12:39.839> and<00:12:40.620> no<00:12:40.800> matter<00:12:40.920> what 00:12:41.210 --> 00:12:41.220 align:start position:0% simply a black box and no matter what 00:12:41.220 --> 00:12:42.350 align:start position:0% simply a black box and no matter what clients<00:12:41.519> you're<00:12:41.700> running<00:12:41.880> you<00:12:42.120> can<00:12:42.240> always 00:12:42.350 --> 00:12:42.360 align:start position:0% clients you're running you can always 00:12:42.360 --> 00:12:43.850 align:start position:0% clients you're running you can always interact<00:12:42.779> with<00:12:42.899> them<00:12:43.019> you<00:12:43.620> know<00:12:43.680> almost 00:12:43.850 --> 00:12:43.860 align:start position:0% interact with them you know almost 00:12:43.860 --> 00:12:45.889 align:start position:0% interact with them you know almost exactly<00:12:44.339> the<00:12:44.579> same<00:12:44.760> through<00:12:45.060> the<00:12:45.180> Json<00:12:45.420> RPC 00:12:45.889 --> 00:12:45.899 align:start position:0% exactly the same through the Json RPC 00:12:45.899 --> 00:12:47.449 align:start position:0% exactly the same through the Json RPC and<00:12:46.500> we're<00:12:46.620> trying<00:12:46.800> to<00:12:46.920> get<00:12:47.040> to<00:12:47.160> that<00:12:47.279> point 00:12:47.449 --> 00:12:47.459 align:start position:0% and we're trying to get to that point 00:12:47.459 --> 00:12:49.670 align:start position:0% and we're trying to get to that point but<00:12:47.760> we're<00:12:48.060> still<00:12:48.240> not<00:12:48.420> quite<00:12:48.660> there<00:12:48.839> and<00:12:49.500> it's 00:12:49.670 --> 00:12:49.680 align:start position:0% but we're still not quite there and it's 00:12:49.680 --> 00:12:50.750 align:start position:0% but we're still not quite there and it's just<00:12:49.860> generally<00:12:50.100> one<00:12:50.279> of<00:12:50.459> these<00:12:50.579> things 00:12:50.750 --> 00:12:50.760 align:start position:0% just generally one of these things 00:12:50.760 --> 00:12:53.990 align:start position:0% just generally one of these things that's<00:12:51.240> not<00:12:52.139> as<00:12:52.380> high<00:12:52.860> interest<00:12:53.279> for<00:12:53.700> a<00:12:53.820> lot<00:12:53.880> of 00:12:53.990 --> 00:12:54.000 align:start position:0% that's not as high interest for a lot of 00:12:54.000 --> 00:12:56.569 align:start position:0% that's not as high interest for a lot of people<00:12:54.120> and<00:12:54.420> so<00:12:54.720> it<00:12:55.560> gets<00:12:55.920> put<00:12:56.220> on<00:12:56.339> the<00:12:56.459> back 00:12:56.569 --> 00:12:56.579 align:start position:0% people and so it gets put on the back 00:12:56.579 --> 00:12:58.370 align:start position:0% people and so it gets put on the back burner<00:12:56.880> for<00:12:57.360> the<00:12:57.480> most<00:12:57.540> part 00:12:58.370 --> 00:12:58.380 align:start position:0% burner for the most part 00:12:58.380 --> 00:13:00.470 align:start position:0% burner for the most part and<00:12:58.980> I<00:12:59.160> guess<00:12:59.339> one<00:12:59.519> more<00:12:59.700> thing<00:12:59.820> I<00:13:00.120> would<00:13:00.240> add 00:13:00.470 --> 00:13:00.480 align:start position:0% and I guess one more thing I would add 00:13:00.480 --> 00:13:03.170 align:start position:0% and I guess one more thing I would add is<00:13:00.899> that<00:13:01.260> uh<00:13:02.040> no<00:13:02.459> shade<00:13:02.700> for<00:13:02.940> the<00:13:03.060> other 00:13:03.170 --> 00:13:03.180 align:start position:0% is that uh no shade for the other 00:13:03.180 --> 00:13:06.650 align:start position:0% is that uh no shade for the other execution<00:13:03.600> clients<00:13:04.139> but<00:13:04.940> very<00:13:05.940> often<00:13:06.240> I<00:13:06.540> do 00:13:06.650 --> 00:13:06.660 align:start position:0% execution clients but very often I do 00:13:06.660 --> 00:13:09.410 align:start position:0% execution clients but very often I do feel<00:13:06.959> that<00:13:07.380> we<00:13:08.040> the<00:13:08.279> guest<00:13:08.459> team<00:13:08.579> is<00:13:08.820> driving<00:13:09.000> a 00:13:09.410 --> 00:13:09.420 align:start position:0% feel that we the guest team is driving a 00:13:09.420 --> 00:13:11.870 align:start position:0% feel that we the guest team is driving a lot<00:13:09.540> of<00:13:09.720> the<00:13:10.500> changes<00:13:11.100> a<00:13:11.339> lot<00:13:11.399> of<00:13:11.579> protocol 00:13:11.870 --> 00:13:11.880 align:start position:0% lot of the changes a lot of protocol 00:13:11.880 --> 00:13:14.870 align:start position:0% lot of the changes a lot of protocol changes<00:13:12.360> networking<00:13:12.899> changes<00:13:13.320> so<00:13:13.700> it's<00:13:14.700> kind 00:13:14.870 --> 00:13:14.880 align:start position:0% changes networking changes so it's kind 00:13:14.880 --> 00:13:16.850 align:start position:0% changes networking changes so it's kind of<00:13:14.940> a<00:13:15.120> bit<00:13:15.240> asymmetric<00:13:15.959> in<00:13:16.079> that<00:13:16.260> we<00:13:16.560> are<00:13:16.740> the 00:13:16.850 --> 00:13:16.860 align:start position:0% of a bit asymmetric in that we are the 00:13:16.860 --> 00:13:19.009 align:start position:0% of a bit asymmetric in that we are the ones<00:13:17.160> bringing<00:13:17.700> the<00:13:18.120> for<00:13:18.660> example<00:13:18.839> the 00:13:19.009 --> 00:13:19.019 align:start position:0% ones bringing the for example the 00:13:19.019 --> 00:13:21.590 align:start position:0% ones bringing the for example the networking<00:13:19.560> eips<00:13:20.100> to<00:13:20.459> the<00:13:20.639> table<00:13:20.820> and 00:13:21.590 --> 00:13:21.600 align:start position:0% networking eips to the table and 00:13:21.600 --> 00:13:23.389 align:start position:0% networking eips to the table and everybody<00:13:21.779> else<00:13:22.200> just<00:13:22.500> well<00:13:22.740> okay<00:13:23.040> if<00:13:23.220> it's 00:13:23.389 --> 00:13:23.399 align:start position:0% everybody else just well okay if it's 00:13:23.399 --> 00:13:25.009 align:start position:0% everybody else just well okay if it's backed<00:13:23.760> out<00:13:23.820> and<00:13:24.000> it<00:13:24.180> gets<00:13:24.480> implemented<00:13:24.899> it 00:13:25.009 --> 00:13:25.019 align:start position:0% backed out and it gets implemented it 00:13:25.019 --> 00:13:27.350 align:start position:0% backed out and it gets implemented it then<00:13:25.200> we'll<00:13:25.320> just<00:13:25.500> roll<00:13:25.620> with<00:13:25.920> it<00:13:26.100> and<00:13:26.940> I<00:13:27.240> mean 00:13:27.350 --> 00:13:27.360 align:start position:0% then we'll just roll with it and I mean 00:13:27.360 --> 00:13:29.810 align:start position:0% then we'll just roll with it and I mean that's<00:13:27.660> perfectly<00:13:28.079> fine<00:13:28.620> just<00:13:29.279> it<00:13:29.519> kind<00:13:29.700> of 00:13:29.810 --> 00:13:29.820 align:start position:0% that's perfectly fine just it kind of 00:13:29.820 --> 00:13:33.290 align:start position:0% that's perfectly fine just it kind of means<00:13:30.060> that<00:13:30.360> our<00:13:30.720> our<00:13:31.139> tax<00:13:31.820> tasks<00:13:32.820> are<00:13:33.120> always 00:13:33.290 --> 00:13:33.300 align:start position:0% means that our our tax tasks are always 00:13:33.300 --> 00:13:35.389 align:start position:0% means that our our tax tasks are always not<00:13:33.779> only<00:13:33.959> to<00:13:34.200> maintain<00:13:34.500> gas<00:13:34.800> but<00:13:35.100> also 00:13:35.389 --> 00:13:35.399 align:start position:0% not only to maintain gas but also 00:13:35.399 --> 00:13:37.250 align:start position:0% not only to maintain gas but also somehow<00:13:35.700> to<00:13:35.880> try<00:13:36.120> to<00:13:36.240> advance<00:13:36.480> the<00:13:36.839> execution 00:13:37.250 --> 00:13:37.260 align:start position:0% somehow to try to advance the execution 00:13:37.260 --> 00:13:40.129 align:start position:0% somehow to try to advance the execution layer<00:13:37.740> features<00:13:38.459> whereas<00:13:39.420> the<00:13:39.600> other<00:13:39.720> clients 00:13:40.129 --> 00:13:40.139 align:start position:0% layer features whereas the other clients 00:13:40.139 --> 00:13:41.690 align:start position:0% layer features whereas the other clients are<00:13:40.320> kind<00:13:40.560> of<00:13:40.620> I<00:13:40.860> feel<00:13:41.220> that<00:13:41.399> they<00:13:41.579> are 00:13:41.690 --> 00:13:41.700 align:start position:0% are kind of I feel that they are 00:13:41.700 --> 00:13:43.970 align:start position:0% are kind of I feel that they are sometimes<00:13:42.060> just<00:13:42.300> playing<00:13:42.480> catch-up<00:13:43.079> and<00:13:43.860> this 00:13:43.970 --> 00:13:43.980 align:start position:0% sometimes just playing catch-up and this 00:13:43.980 --> 00:13:46.910 align:start position:0% sometimes just playing catch-up and this is<00:13:44.160> fine<00:13:44.279> for<00:13:44.579> them<00:13:44.760> which<00:13:45.240> is<00:13:45.540> less<00:13:46.320> fine<00:13:46.620> for 00:13:46.910 --> 00:13:46.920 align:start position:0% is fine for them which is less fine for 00:13:46.920 --> 00:13:49.670 align:start position:0% is fine for them which is less fine for us 00:13:49.670 --> 00:13:49.680 align:start position:0% 00:13:49.680 --> 00:13:52.430 align:start position:0% um I<00:13:49.920> think<00:13:50.100> that<00:13:50.399> that<00:13:50.760> also<00:13:51.480> goes<00:13:51.839> that<00:13:52.200> on 00:13:52.430 --> 00:13:52.440 align:start position:0% um I think that that also goes that on 00:13:52.440 --> 00:13:54.710 align:start position:0% um I think that that also goes that on not<00:13:52.680> only<00:13:52.800> goes<00:13:53.160> for<00:13:53.279> features<00:13:53.639> but<00:13:53.820> also<00:13:54.240> for 00:13:54.710 --> 00:13:54.720 align:start position:0% not only goes for features but also for 00:13:54.720 --> 00:13:57.590 align:start position:0% not only goes for features but also for uh<00:13:55.380> the<00:13:55.620> testing<00:13:55.980> so<00:13:56.700> a<00:13:56.880> lot<00:13:57.000> of<00:13:57.120> the<00:13:57.240> testing 00:13:57.590 --> 00:13:57.600 align:start position:0% uh the testing so a lot of the testing 00:13:57.600 --> 00:14:01.610 align:start position:0% uh the testing so a lot of the testing efforts<00:13:58.139> uh<00:13:58.860> right<00:13:59.160> now<00:13:59.339> are<00:14:00.000> driven<00:14:00.420> by<00:14:00.899> uh 00:14:01.610 --> 00:14:01.620 align:start position:0% efforts uh right now are driven by uh 00:14:01.620 --> 00:14:04.730 align:start position:0% efforts uh right now are driven by uh bright<00:14:01.860> by<00:14:02.220> Geth<00:14:02.540> and<00:14:03.540> we're<00:14:04.380> currently 00:14:04.730 --> 00:14:04.740 align:start position:0% bright by Geth and we're currently 00:14:04.740 --> 00:14:07.730 align:start position:0% bright by Geth and we're currently trying<00:14:05.100> to<00:14:05.399> build<00:14:05.639> out<00:14:06.000> a<00:14:06.839> new<00:14:07.079> team<00:14:07.320> within 00:14:07.730 --> 00:14:07.740 align:start position:0% trying to build out a new team within 00:14:07.740 --> 00:14:10.670 align:start position:0% trying to build out a new team within the<00:14:07.920> ethereum<00:14:08.279> foundation<00:14:08.959> uh<00:14:09.959> for 00:14:10.670 --> 00:14:10.680 align:start position:0% the ethereum foundation uh for 00:14:10.680 --> 00:14:12.410 align:start position:0% the ethereum foundation uh for specifically<00:14:11.579> for<00:14:11.880> testing<00:14:12.180> for 00:14:12.410 --> 00:14:12.420 align:start position:0% specifically for testing for 00:14:12.420 --> 00:14:14.389 align:start position:0% specifically for testing for cross-client<00:14:13.019> testing 00:14:14.389 --> 00:14:14.399 align:start position:0% cross-client testing 00:14:14.399 --> 00:14:18.829 align:start position:0% cross-client testing um<00:14:14.459> so<00:14:15.480> um<00:14:15.779> yeah<00:14:16.380> and<00:14:16.680> the<00:14:16.800> deposit<00:14:17.399> has<00:14:17.579> been 00:14:18.829 --> 00:14:18.839 align:start position:0% um so um yeah and the deposit has been 00:14:18.839 --> 00:14:22.550 align:start position:0% um so um yeah and the deposit has been Geth<00:14:19.680> is<00:14:19.980> the<00:14:20.100> majority<00:14:20.459> client<00:14:20.940> and<00:14:21.899> we<00:14:22.440> have 00:14:22.550 --> 00:14:22.560 align:start position:0% Geth is the majority client and we have 00:14:22.560 --> 00:14:24.230 align:start position:0% Geth is the majority client and we have to<00:14:22.680> take<00:14:22.860> care<00:14:23.040> of<00:14:23.160> the<00:14:23.339> network<00:14:23.459> so<00:14:23.880> we<00:14:24.060> have 00:14:24.230 --> 00:14:24.240 align:start position:0% to take care of the network so we have 00:14:24.240 --> 00:14:27.050 align:start position:0% to take care of the network so we have to<00:14:24.420> make<00:14:24.600> sure<00:14:24.779> that<00:14:25.200> everything<00:14:25.980> is<00:14:26.519> really 00:14:27.050 --> 00:14:27.060 align:start position:0% to make sure that everything is really 00:14:27.060 --> 00:14:31.430 align:start position:0% to make sure that everything is really well<00:14:27.300> tested<00:14:27.720> and<00:14:28.680> we<00:14:29.339> can<00:14:29.459> create<00:14:30.320> we<00:14:31.320> can 00:14:31.430 --> 00:14:31.440 align:start position:0% well tested and we can create we can 00:14:31.440 --> 00:14:34.190 align:start position:0% well tested and we can create we can create<00:14:31.740> tests<00:14:32.519> for<00:14:32.760> that<00:14:33.420> can<00:14:33.720> also<00:14:33.959> be<00:14:34.079> used 00:14:34.190 --> 00:14:34.200 align:start position:0% create tests for that can also be used 00:14:34.200 --> 00:14:36.590 align:start position:0% create tests for that can also be used by<00:14:34.440> the<00:14:34.620> other<00:14:34.740> clients<00:14:35.279> but<00:14:36.240> in<00:14:36.420> the<00:14:36.480> future 00:14:36.590 --> 00:14:36.600 align:start position:0% by the other clients but in the future 00:14:36.600 --> 00:14:38.170 align:start position:0% by the other clients but in the future we<00:14:36.899> would<00:14:37.019> like<00:14:37.260> to 00:14:38.170 --> 00:14:38.180 align:start position:0% we would like to 00:14:38.180 --> 00:14:42.530 align:start position:0% we would like to get<00:14:39.180> to<00:14:39.360> a<00:14:39.540> state<00:14:39.779> where<00:14:40.940> researchers<00:14:41.940> and<00:14:42.420> the 00:14:42.530 --> 00:14:42.540 align:start position:0% get to a state where researchers and the 00:14:42.540 --> 00:14:44.569 align:start position:0% get to a state where researchers and the testing<00:14:42.899> team<00:14:43.199> create<00:14:43.620> tests<00:14:44.160> for<00:14:44.339> everyone 00:14:44.569 --> 00:14:44.579 align:start position:0% testing team create tests for everyone 00:14:44.579 --> 00:14:47.090 align:start position:0% testing team create tests for everyone and<00:14:45.120> so<00:14:45.360> we<00:14:45.660> don't<00:14:45.899> like<00:14:46.320> and<00:14:46.560> they<00:14:46.740> don't<00:14:46.920> have 00:14:47.090 --> 00:14:47.100 align:start position:0% and so we don't like and they don't have 00:14:47.100 --> 00:14:50.090 align:start position:0% and so we don't like and they don't have to<00:14:47.399> rely<00:14:47.760> on<00:14:48.180> on<00:14:48.720> us<00:14:49.079> doing<00:14:49.380> doing<00:14:49.680> the<00:14:49.980> work 00:14:50.090 --> 00:14:50.100 align:start position:0% to rely on on us doing doing the work 00:14:50.100 --> 00:14:52.370 align:start position:0% to rely on on us doing doing the work for<00:14:50.339> testing 00:14:52.370 --> 00:14:52.380 align:start position:0% for testing 00:14:52.380 --> 00:14:55.910 align:start position:0% for testing uh<00:14:53.279> yeah<00:14:53.519> and<00:14:53.760> something<00:14:54.060> kind<00:14:54.959> of<00:14:55.079> uh<00:14:55.320> in<00:14:55.860> this 00:14:55.910 --> 00:14:55.920 align:start position:0% uh yeah and something kind of uh in this 00:14:55.920 --> 00:14:57.829 align:start position:0% uh yeah and something kind of uh in this area<00:14:56.160> is<00:14:56.519> also 00:14:57.829 --> 00:14:57.839 align:start position:0% area is also 00:14:57.839 --> 00:15:00.590 align:start position:0% area is also um<00:14:57.899> there's<00:14:58.500> there's<00:14:58.740> gas<00:14:59.100> gas<00:14:59.639> is<00:14:59.940> its<00:15:00.540> own 00:15:00.590 --> 00:15:00.600 align:start position:0% um there's there's gas gas is its own 00:15:00.600 --> 00:15:03.470 align:start position:0% um there's there's gas gas is its own monolithic<00:15:01.560> piece<00:15:01.860> of<00:15:01.980> software 00:15:03.470 --> 00:15:03.480 align:start position:0% monolithic piece of software 00:15:03.480 --> 00:15:05.750 align:start position:0% monolithic piece of software um<00:15:03.540> but<00:15:04.079> there's<00:15:04.440> a<00:15:04.560> lot<00:15:04.680> of<00:15:04.860> I<00:15:05.160> feel<00:15:05.279> there's<00:15:05.579> a 00:15:05.750 --> 00:15:05.760 align:start position:0% um but there's a lot of I feel there's a 00:15:05.760 --> 00:15:08.810 align:start position:0% um but there's a lot of I feel there's a huge<00:15:06.060> gap<00:15:06.300> still<00:15:06.600> between<00:15:07.500> the<00:15:08.399> solidity 00:15:08.810 --> 00:15:08.820 align:start position:0% huge gap still between the solidity 00:15:08.820 --> 00:15:11.329 align:start position:0% huge gap still between the solidity development<00:15:09.360> world<00:15:09.600> and<00:15:09.899> Geth<00:15:10.380> and<00:15:10.740> I<00:15:10.920> I<00:15:11.100> would 00:15:11.329 --> 00:15:11.339 align:start position:0% development world and Geth and I I would 00:15:11.339 --> 00:15:13.129 align:start position:0% development world and Geth and I I would really<00:15:11.459> love<00:15:11.699> to<00:15:11.880> see<00:15:12.180> a<00:15:12.300> lot<00:15:12.420> more<00:15:12.600> tooling 00:15:13.129 --> 00:15:13.139 align:start position:0% really love to see a lot more tooling 00:15:13.139 --> 00:15:15.110 align:start position:0% really love to see a lot more tooling developing<00:15:13.740> in<00:15:14.040> between<00:15:14.160> like<00:15:14.760> to<00:15:14.940> bridge 00:15:15.110 --> 00:15:15.120 align:start position:0% developing in between like to bridge 00:15:15.120 --> 00:15:17.569 align:start position:0% developing in between like to bridge this<00:15:15.420> Gap<00:15:15.600> so<00:15:15.959> I<00:15:16.380> don't<00:15:16.500> really<00:15:16.680> have<00:15:17.399> any 00:15:17.569 --> 00:15:17.579 align:start position:0% this Gap so I don't really have any 00:15:17.579 --> 00:15:19.490 align:start position:0% this Gap so I don't really have any suggestion<00:15:18.120> about<00:15:18.300> such<00:15:18.600> tooling<00:15:19.079> but<00:15:19.260> I<00:15:19.380> I 00:15:19.490 --> 00:15:19.500 align:start position:0% suggestion about such tooling but I I 00:15:19.500 --> 00:15:21.650 align:start position:0% suggestion about such tooling but I I feel<00:15:19.920> there's<00:15:20.220> a<00:15:20.339> there's<00:15:20.639> a<00:15:20.760> gap<00:15:20.940> here<00:15:21.180> that 00:15:21.650 --> 00:15:21.660 align:start position:0% feel there's a there's a gap here that 00:15:21.660 --> 00:15:23.870 align:start position:0% feel there's a there's a gap here that would<00:15:21.779> be<00:15:21.959> great<00:15:22.079> to<00:15:22.380> to<00:15:22.620> fill 00:15:23.870 --> 00:15:23.880 align:start position:0% would be great to to fill 00:15:23.880 --> 00:15:24.949 align:start position:0% would be great to to fill um<00:15:23.940> I<00:15:24.060> have<00:15:24.180> to<00:15:24.300> think<00:15:24.360> of<00:15:24.480> a<00:15:24.600> question<00:15:24.720> because 00:15:24.949 --> 00:15:24.959 align:start position:0% um I have to think of a question because 00:15:24.959 --> 00:15:26.329 align:start position:0% um I have to think of a question because what<00:15:25.199> I<00:15:25.320> really<00:15:25.380> want<00:15:25.560> to<00:15:25.680> do<00:15:25.740> is<00:15:26.040> just<00:15:26.220> use 00:15:26.329 --> 00:15:26.339 align:start position:0% what I really want to do is just use 00:15:26.339 --> 00:15:27.769 align:start position:0% what I really want to do is just use this<00:15:26.519> as<00:15:26.699> an<00:15:26.820> opportunity<00:15:27.120> that<00:15:27.360> I<00:15:27.540> may<00:15:27.660> never 00:15:27.769 --> 00:15:27.779 align:start position:0% this as an opportunity that I may never 00:15:27.779 --> 00:15:30.410 align:start position:0% this as an opportunity that I may never have<00:15:27.959> again<00:15:28.079> to<00:15:28.380> say<00:15:28.560> just<00:15:29.100> how<00:15:29.699> sincerely 00:15:30.410 --> 00:15:30.420 align:start position:0% have again to say just how sincerely 00:15:30.420 --> 00:15:32.509 align:start position:0% have again to say just how sincerely appreciative<00:15:30.959> I<00:15:31.199> am<00:15:31.380> of<00:15:31.920> everything<00:15:32.160> you<00:15:32.399> guys 00:15:32.509 --> 00:15:32.519 align:start position:0% appreciative I am of everything you guys 00:15:32.519 --> 00:15:33.710 align:start position:0% appreciative I am of everything you guys have<00:15:32.639> been<00:15:32.760> doing<00:15:32.880> over<00:15:33.060> the<00:15:33.240> last<00:15:33.360> couple 00:15:33.710 --> 00:15:33.720 align:start position:0% have been doing over the last couple 00:15:33.720 --> 00:15:33.950 align:start position:0% have been doing over the last couple years 00:15:33.950 --> 00:15:33.960 align:start position:0% years 00:15:33.960 --> 00:15:35.569 align:start position:0% years [Applause] 00:15:35.569 --> 00:15:35.579 align:start position:0% [Applause] 00:15:35.579 --> 00:15:36.590 align:start position:0% [Applause] um 00:15:36.590 --> 00:15:36.600 align:start position:0% um 00:15:36.600 --> 00:15:38.389 align:start position:0% um from<00:15:37.079> one<00:15:37.260> developer<00:15:37.620> to<00:15:37.740> another<00:15:37.920> I<00:15:38.279> know 00:15:38.389 --> 00:15:38.399 align:start position:0% from one developer to another I know 00:15:38.399 --> 00:15:39.829 align:start position:0% from one developer to another I know that<00:15:38.699> sometimes<00:15:39.240> that<00:15:39.420> doesn't<00:15:39.540> come<00:15:39.720> through 00:15:39.829 --> 00:15:39.839 align:start position:0% that sometimes that doesn't come through 00:15:39.839 --> 00:15:41.569 align:start position:0% that sometimes that doesn't come through as<00:15:40.019> much<00:15:40.139> as<00:15:40.199> it<00:15:40.320> needs<00:15:40.560> to<00:15:40.620> and<00:15:40.860> I<00:15:41.160> it's<00:15:41.339> just 00:15:41.569 --> 00:15:41.579 align:start position:0% as much as it needs to and I it's just 00:15:41.579 --> 00:15:42.769 align:start position:0% as much as it needs to and I it's just what<00:15:42.000> you<00:15:42.060> guys<00:15:42.180> have<00:15:42.300> done<00:15:42.480> has<00:15:42.600> really 00:15:42.769 --> 00:15:42.779 align:start position:0% what you guys have done has really 00:15:42.779 --> 00:15:45.470 align:start position:0% what you guys have done has really helped<00:15:43.079> me<00:15:43.620> um<00:15:43.680> help<00:15:43.920> me<00:15:44.160> personally<00:15:44.399> and<00:15:45.060> get 00:15:45.470 --> 00:15:45.480 align:start position:0% helped me um help me personally and get 00:15:45.480 --> 00:15:48.170 align:start position:0% helped me um help me personally and get me<00:15:45.600> involved<00:15:45.899> in<00:15:46.019> the<00:15:46.139> ecosystem<00:15:46.500> so<00:15:46.920> uh<00:15:47.820> if<00:15:48.120> I 00:15:48.170 --> 00:15:48.180 align:start position:0% me involved in the ecosystem so uh if I 00:15:48.180 --> 00:15:49.189 align:start position:0% me involved in the ecosystem so uh if I came<00:15:48.300> up<00:15:48.420> with<00:15:48.540> a<00:15:48.660> question<00:15:48.779> right<00:15:48.959> now<00:15:49.079> I 00:15:49.189 --> 00:15:49.199 align:start position:0% came up with a question right now I 00:15:49.199 --> 00:15:50.629 align:start position:0% came up with a question right now I guess<00:15:49.320> it<00:15:49.440> would<00:15:49.620> be 00:15:50.629 --> 00:15:50.639 align:start position:0% guess it would be 00:15:50.639 --> 00:15:53.449 align:start position:0% guess it would be uh<00:15:51.120> does<00:15:51.300> clef<00:15:51.779> have<00:15:52.260> any<00:15:52.500> future 00:15:53.449 --> 00:15:53.459 align:start position:0% uh does clef have any future 00:15:53.459 --> 00:15:56.389 align:start position:0% uh does clef have any future so<00:15:53.820> whether<00:15:54.000> it<00:15:54.240> has<00:15:54.420> a<00:15:54.540> future<00:15:54.660> or<00:15:55.019> not<00:15:55.560> um 00:15:56.389 --> 00:15:56.399 align:start position:0% so whether it has a future or not um 00:15:56.399 --> 00:15:58.910 align:start position:0% so whether it has a future or not um I<00:15:57.000> would<00:15:57.180> say<00:15:57.540> so<00:15:58.079> cleft<00:15:58.380> was<00:15:58.560> one<00:15:58.740> of<00:15:58.860> those 00:15:58.910 --> 00:15:58.920 align:start position:0% I would say so cleft was one of those 00:15:58.920 --> 00:16:01.370 align:start position:0% I would say so cleft was one of those projects<00:15:59.339> which<00:15:59.699> we<00:16:00.000> really<00:16:00.360> think<00:16:00.720> would<00:16:01.199> be 00:16:01.370 --> 00:16:01.380 align:start position:0% projects which we really think would be 00:16:01.380 --> 00:16:04.250 align:start position:0% projects which we really think would be very<00:16:01.680> very<00:16:01.800> useful<00:16:02.160> however<00:16:03.060> I<00:16:03.959> kind<00:16:04.019> of<00:16:04.139> feel 00:16:04.250 --> 00:16:04.260 align:start position:0% very very useful however I kind of feel 00:16:04.260 --> 00:16:06.650 align:start position:0% very very useful however I kind of feel that<00:16:04.500> we<00:16:04.800> as<00:16:05.220> developers<00:16:05.760> kind<00:16:06.000> of<00:16:06.120> took<00:16:06.420> it<00:16:06.540> to 00:16:06.650 --> 00:16:06.660 align:start position:0% that we as developers kind of took it to 00:16:06.660 --> 00:16:09.769 align:start position:0% that we as developers kind of took it to a<00:16:06.839> point<00:16:06.959> where<00:16:07.260> it's<00:16:07.800> uh<00:16:08.339> secure 00:16:09.769 --> 00:16:09.779 align:start position:0% a point where it's uh secure 00:16:09.779 --> 00:16:12.310 align:start position:0% a point where it's uh secure and<00:16:10.440> it's<00:16:10.620> highly<00:16:10.980> unusable<00:16:11.519> because<00:16:11.820> it's 00:16:12.310 --> 00:16:12.320 align:start position:0% and it's highly unusable because it's 00:16:12.320 --> 00:16:14.990 align:start position:0% and it's highly unusable because it's very<00:16:13.320> very<00:16:13.500> console<00:16:14.040> based<00:16:14.519> and<00:16:14.639> and 00:16:14.990 --> 00:16:15.000 align:start position:0% very very console based and and 00:16:15.000 --> 00:16:17.930 align:start position:0% very very console based and and everything<00:16:15.440> and<00:16:16.440> the<00:16:16.740> only<00:16:16.860> way<00:16:17.100> to<00:16:17.279> make<00:16:17.459> clef 00:16:17.930 --> 00:16:17.940 align:start position:0% everything and the only way to make clef 00:16:17.940 --> 00:16:21.170 align:start position:0% everything and the only way to make clef more<00:16:18.540> usable<00:16:18.899> or<00:16:19.380> friendly<00:16:20.040> at<00:16:20.579> even<00:16:21.000> the 00:16:21.170 --> 00:16:21.180 align:start position:0% more usable or friendly at even the 00:16:21.180 --> 00:16:23.210 align:start position:0% more usable or friendly at even the least<00:16:21.300> bit<00:16:21.540> is<00:16:21.899> to<00:16:22.139> actually<00:16:22.320> turn<00:16:22.620> it<00:16:22.740> into<00:16:22.920> a 00:16:23.210 --> 00:16:23.220 align:start position:0% least bit is to actually turn it into a 00:16:23.220 --> 00:16:26.509 align:start position:0% least bit is to actually turn it into a product<00:16:23.480> and<00:16:24.480> unfortunately<00:16:25.139> I<00:16:26.040> will<00:16:26.160> admit 00:16:26.509 --> 00:16:26.519 align:start position:0% product and unfortunately I will admit 00:16:26.519 --> 00:16:28.310 align:start position:0% product and unfortunately I will admit that<00:16:26.639> that<00:16:26.820> is<00:16:27.120> way<00:16:27.420> outside<00:16:27.660> our 00:16:28.310 --> 00:16:28.320 align:start position:0% that that is way outside our 00:16:28.320 --> 00:16:30.650 align:start position:0% that that is way outside our capabilities<00:16:28.920> because<00:16:29.399> there<00:16:29.880> you<00:16:30.540> would 00:16:30.650 --> 00:16:30.660 align:start position:0% capabilities because there you would 00:16:30.660 --> 00:16:32.689 align:start position:0% capabilities because there you would probably<00:16:30.839> need<00:16:31.079> a<00:16:31.320> UI<00:16:31.620> team<00:16:31.800> you<00:16:32.040> would<00:16:32.220> need<00:16:32.399> a 00:16:32.689 --> 00:16:32.699 align:start position:0% probably need a UI team you would need a 00:16:32.699 --> 00:16:34.790 align:start position:0% probably need a UI team you would need a completely<00:16:33.000> different<00:16:33.240> team<00:16:33.779> to<00:16:34.139> to<00:16:34.380> do<00:16:34.620> that 00:16:34.790 --> 00:16:34.800 align:start position:0% completely different team to to do that 00:16:34.800 --> 00:16:37.370 align:start position:0% completely different team to to do that work<00:16:35.040> and<00:16:35.940> whilst<00:16:36.300> I<00:16:36.600> do<00:16:36.720> think<00:16:36.839> it<00:16:37.019> would<00:16:37.259> be 00:16:37.370 --> 00:16:37.380 align:start position:0% work and whilst I do think it would be 00:16:37.380 --> 00:16:40.910 align:start position:0% work and whilst I do think it would be super<00:16:37.680> awesome<00:16:38.300> it's<00:16:39.300> uh<00:16:39.779> again<00:16:40.500> the<00:16:40.740> question 00:16:40.910 --> 00:16:40.920 align:start position:0% super awesome it's uh again the question 00:16:40.920 --> 00:16:42.050 align:start position:0% super awesome it's uh again the question is 00:16:42.050 --> 00:16:42.060 align:start position:0% is 00:16:42.060 --> 00:16:45.290 align:start position:0% is I<00:16:42.660> we<00:16:43.019> could<00:16:43.320> hire<00:16:44.220> somebody<00:16:44.519> or<00:16:44.940> multiple 00:16:45.290 --> 00:16:45.300 align:start position:0% I we could hire somebody or multiple 00:16:45.300 --> 00:16:47.090 align:start position:0% I we could hire somebody or multiple people<00:16:45.480> to<00:16:45.720> work<00:16:45.899> on<00:16:46.019> it<00:16:46.199> we<00:16:46.440> could<00:16:46.560> maybe<00:16:46.800> get 00:16:47.090 --> 00:16:47.100 align:start position:0% people to work on it we could maybe get 00:16:47.100 --> 00:16:49.730 align:start position:0% people to work on it we could maybe get an<00:16:47.279> EF<00:16:47.579> to<00:16:47.820> work<00:16:48.000> on<00:16:48.180> it<00:16:48.300> but<00:16:49.019> there<00:16:49.320> are<00:16:49.500> a<00:16:49.560> lot 00:16:49.730 --> 00:16:49.740 align:start position:0% an EF to work on it but there are a lot 00:16:49.740 --> 00:16:52.490 align:start position:0% an EF to work on it but there are a lot of<00:16:49.860> other<00:16:50.180> wallet<00:16:51.180> software<00:16:51.480> out<00:16:51.779> there 00:16:52.490 --> 00:16:52.500 align:start position:0% of other wallet software out there 00:16:52.500 --> 00:16:55.189 align:start position:0% of other wallet software out there and<00:16:52.920> the<00:16:53.040> question<00:16:53.220> is<00:16:53.459> is<00:16:53.820> it<00:16:54.360> worthwhile<00:16:54.899> to 00:16:55.189 --> 00:16:55.199 align:start position:0% and the question is is it worthwhile to 00:16:55.199 --> 00:16:57.769 align:start position:0% and the question is is it worthwhile to try<00:16:55.320> to<00:16:55.560> compete<00:16:56.040> with<00:16:56.220> them<00:16:56.399> I'm<00:16:57.180> not<00:16:57.300> sure<00:16:57.480> so 00:16:57.769 --> 00:16:57.779 align:start position:0% try to compete with them I'm not sure so 00:16:57.779 --> 00:16:59.689 align:start position:0% try to compete with them I'm not sure so I<00:16:58.019> would<00:16:58.079> say<00:16:58.259> clef<00:16:58.680> isn't<00:16:59.040> going<00:16:59.220> anywhere 00:16:59.689 --> 00:16:59.699 align:start position:0% I would say clef isn't going anywhere 00:16:59.699 --> 00:17:02.689 align:start position:0% I would say clef isn't going anywhere but<00:17:00.660> I<00:17:00.839> don't<00:17:00.959> really<00:17:01.139> see<00:17:01.500> it<00:17:01.680> going<00:17:02.040> into<00:17:02.399> a 00:17:02.689 --> 00:17:02.699 align:start position:0% but I don't really see it going into a 00:17:02.699 --> 00:17:06.409 align:start position:0% but I don't really see it going into a product<00:17:03.260> quality<00:17:04.260> either<00:17:04.860> so<00:17:05.579> it<00:17:06.059> probably<00:17:06.179> it 00:17:06.409 --> 00:17:06.419 align:start position:0% product quality either so it probably it 00:17:06.419 --> 00:17:09.049 align:start position:0% product quality either so it probably it will<00:17:06.600> be<00:17:06.780> a<00:17:07.020> bit<00:17:07.140> in<00:17:07.380> this<00:17:07.559> limbo<00:17:07.980> space<00:17:08.339> for 00:17:09.049 --> 00:17:09.059 align:start position:0% will be a bit in this limbo space for 00:17:09.059 --> 00:17:11.210 align:start position:0% will be a bit in this limbo space for now<00:17:09.240> but<00:17:09.780> something<00:17:09.959> that<00:17:10.380> we're<00:17:10.620> currently 00:17:11.210 --> 00:17:11.220 align:start position:0% now but something that we're currently 00:17:11.220 --> 00:17:13.669 align:start position:0% now but something that we're currently thinking<00:17:11.579> about<00:17:11.880> retiring<00:17:12.780> is<00:17:13.140> the<00:17:13.439> the 00:17:13.669 --> 00:17:13.679 align:start position:0% thinking about retiring is the the 00:17:13.679 --> 00:17:17.710 align:start position:0% thinking about retiring is the the personal<00:17:14.040> namespace<00:17:15.020> and<00:17:16.020> the<00:17:16.380> the<00:17:16.679> the<00:17:17.100> the 00:17:17.710 --> 00:17:17.720 align:start position:0% personal namespace and the the the the 00:17:17.720 --> 00:17:21.530 align:start position:0% personal namespace and the the the the wallet<00:17:18.720> within<00:17:19.260> uh<00:17:20.220> within<00:17:20.640> guess 00:17:21.530 --> 00:17:21.540 align:start position:0% wallet within uh within guess 00:17:21.540 --> 00:17:25.789 align:start position:0% wallet within uh within guess and<00:17:22.319> so<00:17:22.740> if<00:17:23.040> you're<00:17:23.280> depending<00:17:24.179> on<00:17:24.419> that<00:17:24.799> we're 00:17:25.789 --> 00:17:25.799 align:start position:0% and so if you're depending on that we're 00:17:25.799 --> 00:17:28.850 align:start position:0% and so if you're depending on that we're sorry<00:17:26.179> no<00:17:27.179> actually<00:17:27.660> there's<00:17:28.319> a<00:17:28.500> discussion 00:17:28.850 --> 00:17:28.860 align:start position:0% sorry no actually there's a discussion 00:17:28.860 --> 00:17:31.070 align:start position:0% sorry no actually there's a discussion to<00:17:28.980> be<00:17:29.160> had<00:17:29.340> but<00:17:29.880> we<00:17:30.360> would<00:17:30.540> really<00:17:30.720> like<00:17:30.900> to 00:17:31.070 --> 00:17:31.080 align:start position:0% to be had but we would really like to 00:17:31.080 --> 00:17:33.110 align:start position:0% to be had but we would really like to get<00:17:31.260> rid<00:17:31.380> of<00:17:31.559> this<00:17:31.799> yes<00:17:32.280> so<00:17:32.520> definitely<00:17:32.820> that's 00:17:33.110 --> 00:17:33.120 align:start position:0% get rid of this yes so definitely that's 00:17:33.120 --> 00:17:34.909 align:start position:0% get rid of this yes so definitely that's direction<00:17:33.480> we 00:17:34.909 --> 00:17:34.919 align:start position:0% direction we 00:17:34.919 --> 00:17:37.549 align:start position:0% direction we so<00:17:35.580> Geth<00:17:36.120> is<00:17:36.360> kind<00:17:36.480> of<00:17:36.600> like<00:17:36.720> this<00:17:37.140> huge 00:17:37.549 --> 00:17:37.559 align:start position:0% so Geth is kind of like this huge 00:17:37.559 --> 00:17:40.310 align:start position:0% so Geth is kind of like this huge monolithics<00:17:38.460> monster<00:17:38.940> and<00:17:39.840> that<00:17:39.960> was<00:17:40.080> kind<00:17:40.260> of 00:17:40.310 --> 00:17:40.320 align:start position:0% monolithics monster and that was kind of 00:17:40.320 --> 00:17:42.470 align:start position:0% monolithics monster and that was kind of borne<00:17:40.679> out<00:17:40.740> of<00:17:40.860> the<00:17:40.980> necessity<00:17:41.400> of<00:17:41.760> when 00:17:42.470 --> 00:17:42.480 align:start position:0% borne out of the necessity of when 00:17:42.480 --> 00:17:44.150 align:start position:0% borne out of the necessity of when ethereum<00:17:42.960> launched<00:17:43.260> there<00:17:43.440> was<00:17:43.679> no<00:17:43.919> other 00:17:44.150 --> 00:17:44.160 align:start position:0% ethereum launched there was no other 00:17:44.160 --> 00:17:45.710 align:start position:0% ethereum launched there was no other software<00:17:44.640> so<00:17:44.820> everything<00:17:45.000> the<00:17:45.299> clients<00:17:45.600> had 00:17:45.710 --> 00:17:45.720 align:start position:0% software so everything the clients had 00:17:45.720 --> 00:17:46.970 align:start position:0% software so everything the clients had to<00:17:45.840> do<00:17:45.900> everything 00:17:46.970 --> 00:17:46.980 align:start position:0% to do everything 00:17:46.980 --> 00:17:49.909 align:start position:0% to do everything but<00:17:47.640> obviously<00:17:48.260> having<00:17:49.260> your<00:17:49.559> accounts 00:17:49.909 --> 00:17:49.919 align:start position:0% but obviously having your accounts 00:17:49.919 --> 00:17:52.070 align:start position:0% but obviously having your accounts managed<00:17:50.220> by<00:17:50.340> a<00:17:50.520> node<00:17:50.700> is<00:17:50.880> a<00:17:51.059> bit<00:17:51.120> wonky<00:17:51.539> that 00:17:52.070 --> 00:17:52.080 align:start position:0% managed by a node is a bit wonky that 00:17:52.080 --> 00:17:53.450 align:start position:0% managed by a node is a bit wonky that was<00:17:52.260> partially<00:17:52.559> the<00:17:52.740> reason<00:17:52.860> why<00:17:53.039> we<00:17:53.220> built 00:17:53.450 --> 00:17:53.460 align:start position:0% was partially the reason why we built 00:17:53.460 --> 00:17:55.970 align:start position:0% was partially the reason why we built clef<00:17:53.760> and<00:17:54.419> we<00:17:54.840> will<00:17:55.020> definitely<00:17:55.320> try<00:17:55.620> to<00:17:55.740> take 00:17:55.970 --> 00:17:55.980 align:start position:0% clef and we will definitely try to take 00:17:55.980 --> 00:17:58.430 align:start position:0% clef and we will definitely try to take clef<00:17:56.580> up<00:17:56.940> until<00:17:57.179> the<00:17:57.480> point<00:17:57.720> where<00:17:58.020> we<00:17:58.320> can 00:17:58.430 --> 00:17:58.440 align:start position:0% clef up until the point where we can 00:17:58.440 --> 00:18:00.950 align:start position:0% clef up until the point where we can remove<00:17:58.740> account<00:17:59.100> management<00:17:59.460> from<00:17:59.880> Geth<00:18:00.240> and 00:18:00.950 --> 00:18:00.960 align:start position:0% remove account management from Geth and 00:18:00.960 --> 00:18:03.350 align:start position:0% remove account management from Geth and hopefully<00:18:01.260> it<00:18:01.380> should<00:18:01.620> be<00:18:01.799> as<00:18:02.640> easy<00:18:02.880> to<00:18:03.120> manage 00:18:03.350 --> 00:18:03.360 align:start position:0% hopefully it should be as easy to manage 00:18:03.360 --> 00:18:05.570 align:start position:0% hopefully it should be as easy to manage your<00:18:03.480> accounts<00:18:03.840> via<00:18:04.140> clef<00:18:04.500> as<00:18:04.799> if<00:18:05.160> you<00:18:05.400> were 00:18:05.570 --> 00:18:05.580 align:start position:0% your accounts via clef as if you were 00:18:05.580 --> 00:18:08.270 align:start position:0% your accounts via clef as if you were managing<00:18:06.120> it<00:18:06.299> via<00:18:06.600> Geth<00:18:07.320> but<00:18:07.740> I<00:18:07.860> think<00:18:07.980> that's 00:18:08.270 --> 00:18:08.280 align:start position:0% managing it via Geth but I think that's 00:18:08.280 --> 00:18:10.250 align:start position:0% managing it via Geth but I think that's the<00:18:08.580> that's<00:18:09.059> the<00:18:09.299> threshold<00:18:09.660> where<00:18:09.960> we<00:18:10.140> will 00:18:10.250 --> 00:18:10.260 align:start position:0% the that's the threshold where we will 00:18:10.260 --> 00:18:13.370 align:start position:0% the that's the threshold where we will probably<00:18:10.559> stop<00:18:11.400> and<00:18:12.059> if<00:18:12.660> somebody<00:18:12.840> picks<00:18:13.260> it 00:18:13.370 --> 00:18:13.380 align:start position:0% probably stop and if somebody picks it 00:18:13.380 --> 00:18:14.090 align:start position:0% probably stop and if somebody picks it up 00:18:14.090 --> 00:18:14.100 align:start position:0% up 00:18:14.100 --> 00:18:17.090 align:start position:0% up awesome<00:18:14.820> if<00:18:15.299> not<00:18:15.480> then<00:18:15.780> it<00:18:16.440> will<00:18:16.559> be<00:18:16.740> used<00:18:16.860> as 00:18:17.090 --> 00:18:17.100 align:start position:0% awesome if not then it will be used as 00:18:17.100 --> 00:18:19.070 align:start position:0% awesome if not then it will be used as kind<00:18:17.280> of<00:18:17.400> as<00:18:17.520> a<00:18:17.640> developer<00:18:18.059> tool<00:18:18.480> in<00:18:18.960> the 00:18:19.070 --> 00:18:19.080 align:start position:0% kind of as a developer tool in the 00:18:19.080 --> 00:18:21.890 align:start position:0% kind of as a developer tool in the future<00:18:19.220> so<00:18:20.220> a<00:18:20.520> long<00:18:20.760> time<00:18:21.000> ago<00:18:21.240> there<00:18:21.539> used<00:18:21.780> to 00:18:21.890 --> 00:18:21.900 align:start position:0% future so a long time ago there used to 00:18:21.900 --> 00:18:23.510 align:start position:0% future so a long time ago there used to be<00:18:22.020> a<00:18:22.140> very<00:18:22.260> nice<00:18:22.440> proof<00:18:22.799> of<00:18:22.860> concept<00:18:23.220> running 00:18:23.510 --> 00:18:23.520 align:start position:0% be a very nice proof of concept running 00:18:23.520 --> 00:18:26.570 align:start position:0% be a very nice proof of concept running that<00:18:23.820> on<00:18:24.059> Android<00:18:24.440> and<00:18:25.440> I<00:18:25.740> feel<00:18:25.919> that<00:18:26.280> now 00:18:26.570 --> 00:18:26.580 align:start position:0% that on Android and I feel that now 00:18:26.580 --> 00:18:31.730 align:start position:0% that on Android and I feel that now after<00:18:26.880> the<00:18:27.179> merge<00:18:28.020> maybe<00:18:29.000> it's<00:18:30.320> more<00:18:31.320> relevant 00:18:31.730 --> 00:18:31.740 align:start position:0% after the merge maybe it's more relevant 00:18:31.740 --> 00:18:34.490 align:start position:0% after the merge maybe it's more relevant and<00:18:32.400> it<00:18:33.059> can<00:18:33.179> be<00:18:33.419> actually<00:18:33.660> useful<00:18:34.140> that 00:18:34.490 --> 00:18:34.500 align:start position:0% and it can be actually useful that 00:18:34.500 --> 00:18:36.350 align:start position:0% and it can be actually useful that people<00:18:34.740> are<00:18:35.100> running<00:18:35.280> their<00:18:35.640> own<00:18:35.760> clients<00:18:36.179> on 00:18:36.350 --> 00:18:36.360 align:start position:0% people are running their own clients on 00:18:36.360 --> 00:18:39.409 align:start position:0% people are running their own clients on on<00:18:36.539> Android<00:18:37.280> is<00:18:38.280> there<00:18:38.400> any<00:18:38.520> work<00:18:38.820> being<00:18:39.179> done 00:18:39.409 --> 00:18:39.419 align:start position:0% on Android is there any work being done 00:18:39.419 --> 00:18:42.710 align:start position:0% on Android is there any work being done on<00:18:39.600> that<00:18:40.260> so<00:18:40.860> originally<00:18:41.280> we<00:18:41.640> when<00:18:41.940> we<00:18:42.240> shipped 00:18:42.710 --> 00:18:42.720 align:start position:0% on that so originally we when we shipped 00:18:42.720 --> 00:18:45.350 align:start position:0% on that so originally we when we shipped guest<00:18:43.140> for<00:18:43.320> Android<00:18:43.700> we<00:18:44.700> shipped<00:18:44.940> it<00:18:45.059> as<00:18:45.240> a 00:18:45.350 --> 00:18:45.360 align:start position:0% guest for Android we shipped it as a 00:18:45.360 --> 00:18:47.090 align:start position:0% guest for Android we shipped it as a full<00:18:45.480> node<00:18:45.840> which<00:18:46.200> obviously<00:18:46.620> doesn't<00:18:46.860> work 00:18:47.090 --> 00:18:47.100 align:start position:0% full node which obviously doesn't work 00:18:47.100 --> 00:18:50.090 align:start position:0% full node which obviously doesn't work anymore<00:18:47.480> then<00:18:48.480> later<00:18:48.780> jealous<00:18:49.559> shipped<00:18:49.919> the 00:18:50.090 --> 00:18:50.100 align:start position:0% anymore then later jealous shipped the 00:18:50.100 --> 00:18:52.190 align:start position:0% anymore then later jealous shipped the light<00:18:50.280> client<00:18:50.700> it's<00:18:51.419> still<00:18:51.600> I<00:18:51.840> wouldn't<00:18:51.960> call 00:18:52.190 --> 00:18:52.200 align:start position:0% light client it's still I wouldn't call 00:18:52.200 --> 00:18:53.810 align:start position:0% light client it's still I wouldn't call it<00:18:52.320> really<00:18:52.559> production<00:18:52.980> ready<00:18:53.220> but<00:18:53.520> it<00:18:53.640> kind 00:18:53.810 --> 00:18:53.820 align:start position:0% it really production ready but it kind 00:18:53.820 --> 00:18:56.770 align:start position:0% it really production ready but it kind of<00:18:53.880> worked<00:18:54.240> however<00:18:54.960> it<00:18:55.140> turned<00:18:55.440> out<00:18:55.500> that 00:18:56.770 --> 00:18:56.780 align:start position:0% of worked however it turned out that 00:18:56.780 --> 00:18:59.930 align:start position:0% of worked however it turned out that the<00:18:57.780> pre-merge<00:18:58.380> light<00:18:58.500> client<00:18:58.980> is<00:18:59.400> still<00:18:59.640> too 00:18:59.930 --> 00:18:59.940 align:start position:0% the pre-merge light client is still too 00:18:59.940 --> 00:19:02.690 align:start position:0% the pre-merge light client is still too heavy<00:19:00.299> for<00:19:00.539> a<00:19:00.780> phone<00:19:00.960> so<00:19:01.799> now<00:19:01.919> that<00:19:02.160> we<00:19:02.520> are 00:19:02.690 --> 00:19:02.700 align:start position:0% heavy for a phone so now that we are 00:19:02.700 --> 00:19:04.370 align:start position:0% heavy for a phone so now that we are post<00:19:02.880> merge<00:19:03.360> that's<00:19:03.840> actually<00:19:04.080> an 00:19:04.370 --> 00:19:04.380 align:start position:0% post merge that's actually an 00:19:04.380 --> 00:19:06.289 align:start position:0% post merge that's actually an interesting<00:19:04.679> discussion<00:19:05.100> to<00:19:05.280> be<00:19:05.400> had<00:19:05.580> whether 00:19:06.289 --> 00:19:06.299 align:start position:0% interesting discussion to be had whether 00:19:06.299 --> 00:19:08.870 align:start position:0% interesting discussion to be had whether we<00:19:06.480> could<00:19:06.660> just<00:19:06.840> somehow<00:19:07.200> pick<00:19:07.640> this<00:19:08.640> thread 00:19:08.870 --> 00:19:08.880 align:start position:0% we could just somehow pick this thread 00:19:08.880 --> 00:19:12.590 align:start position:0% we could just somehow pick this thread up<00:19:09.059> again<00:19:09.380> I<00:19:10.380> think<00:19:10.559> it<00:19:10.980> definitely<00:19:11.360> would<00:19:12.360> be 00:19:12.590 --> 00:19:12.600 align:start position:0% up again I think it definitely would be 00:19:12.600 --> 00:19:15.230 align:start position:0% up again I think it definitely would be interesting<00:19:13.260> however<00:19:13.980> usually<00:19:14.880> with<00:19:15.059> mobile 00:19:15.230 --> 00:19:15.240 align:start position:0% interesting however usually with mobile 00:19:15.240 --> 00:19:17.090 align:start position:0% interesting however usually with mobile phones<00:19:15.720> and<00:19:15.840> Android<00:19:16.020> you<00:19:16.440> have<00:19:16.620> very<00:19:16.860> very 00:19:17.090 --> 00:19:17.100 align:start position:0% phones and Android you have very very 00:19:17.100 --> 00:19:19.010 align:start position:0% phones and Android you have very very strict<00:19:17.400> limits<00:19:17.820> on<00:19:17.940> how<00:19:18.120> much<00:19:18.240> I<00:19:18.419> mean<00:19:18.600> okay<00:19:18.780> on 00:19:19.010 --> 00:19:19.020 align:start position:0% strict limits on how much I mean okay on 00:19:19.020 --> 00:19:20.570 align:start position:0% strict limits on how much I mean okay on iOS<00:19:19.260> you<00:19:19.559> have<00:19:19.679> very<00:19:19.799> strict<00:19:19.919> limits<00:19:20.340> on<00:19:20.460> how 00:19:20.570 --> 00:19:20.580 align:start position:0% iOS you have very strict limits on how 00:19:20.580 --> 00:19:22.490 align:start position:0% iOS you have very strict limits on how much<00:19:20.760> uh<00:19:21.179> your<00:19:21.360> background<00:19:21.660> process<00:19:22.020> can<00:19:22.320> run 00:19:22.490 --> 00:19:22.500 align:start position:0% much uh your background process can run 00:19:22.500 --> 00:19:24.650 align:start position:0% much uh your background process can run Android<00:19:23.039> is<00:19:23.400> a<00:19:23.580> bit<00:19:23.640> more<00:19:23.760> relaxed<00:19:24.179> but<00:19:24.480> you're 00:19:24.650 --> 00:19:24.660 align:start position:0% Android is a bit more relaxed but you're 00:19:24.660 --> 00:19:26.270 align:start position:0% Android is a bit more relaxed but you're eating<00:19:25.080> still<00:19:25.260> eating<00:19:25.620> battery<00:19:25.860> very<00:19:26.220> very 00:19:26.270 --> 00:19:26.280 align:start position:0% eating still eating battery very very 00:19:26.280 --> 00:19:29.750 align:start position:0% eating still eating battery very very fast<00:19:26.900> so<00:19:27.900> I<00:19:28.320> could<00:19:28.440> imagine 00:19:29.750 --> 00:19:29.760 align:start position:0% fast so I could imagine 00:19:29.760 --> 00:19:31.970 align:start position:0% fast so I could imagine some<00:19:30.360> Alias<00:19:30.840> clients<00:19:31.260> or<00:19:31.440> some<00:19:31.559> like<00:19:31.740> client 00:19:31.970 --> 00:19:31.980 align:start position:0% some Alias clients or some like client 00:19:31.980 --> 00:19:33.710 align:start position:0% some Alias clients or some like client on<00:19:32.220> demand<00:19:32.460> where<00:19:32.700> you<00:19:32.880> just<00:19:33.059> whenever<00:19:33.539> you 00:19:33.710 --> 00:19:33.720 align:start position:0% on demand where you just whenever you 00:19:33.720 --> 00:19:35.390 align:start position:0% on demand where you just whenever you just<00:19:33.840> want<00:19:34.020> to<00:19:34.140> interact<00:19:34.559> with<00:19:34.980> your<00:19:35.160> thing 00:19:35.390 --> 00:19:35.400 align:start position:0% just want to interact with your thing 00:19:35.400 --> 00:19:38.390 align:start position:0% just want to interact with your thing then<00:19:35.940> very<00:19:36.419> temporarily<00:19:37.020> just<00:19:37.440> pull<00:19:38.160> some 00:19:38.390 --> 00:19:38.400 align:start position:0% then very temporarily just pull some 00:19:38.400 --> 00:19:41.210 align:start position:0% then very temporarily just pull some data<00:19:38.700> from<00:19:38.820> the<00:19:38.940> network<00:19:39.120> and<00:19:39.600> and<00:19:39.960> that's<00:19:40.260> it 00:19:41.210 --> 00:19:41.220 align:start position:0% data from the network and and that's it 00:19:41.220 --> 00:19:44.390 align:start position:0% data from the network and and that's it then<00:19:42.059> I<00:19:42.360> think<00:19:42.480> the<00:19:42.660> the<00:19:43.080> post<00:19:43.320> merge<00:19:43.740> world<00:19:43.919> is 00:19:44.390 --> 00:19:44.400 align:start position:0% then I think the the post merge world is 00:19:44.400 --> 00:19:46.970 align:start position:0% then I think the the post merge world is kind<00:19:44.760> of<00:19:44.880> compatible<00:19:45.360> with<00:19:45.720> that<00:19:45.900> so<00:19:46.500> I<00:19:46.679> I 00:19:46.970 --> 00:19:46.980 align:start position:0% kind of compatible with that so I I 00:19:46.980 --> 00:19:49.070 align:start position:0% kind of compatible with that so I I think<00:19:47.160> that<00:19:47.460> would<00:19:47.640> be<00:19:47.760> interesting 00:19:49.070 --> 00:19:49.080 align:start position:0% think that would be interesting 00:19:49.080 --> 00:19:52.070 align:start position:0% think that would be interesting however<00:19:49.640> at<00:19:50.640> least<00:19:50.760> using<00:19:51.360> the<00:19:51.539> gath<00:19:51.780> code 00:19:52.070 --> 00:19:52.080 align:start position:0% however at least using the gath code 00:19:52.080 --> 00:19:54.950 align:start position:0% however at least using the gath code base<00:19:52.380> I<00:19:53.220> think<00:19:53.340> it<00:19:53.640> will<00:19:54.059> always<00:19:54.240> be<00:19:54.600> a<00:19:54.840> bit 00:19:54.950 --> 00:19:54.960 align:start position:0% base I think it will always be a bit 00:19:54.960 --> 00:19:58.430 align:start position:0% base I think it will always be a bit heavier<00:19:55.559> than<00:19:55.980> ideal<00:19:56.539> so<00:19:57.539> if<00:19:57.780> you<00:19:57.900> if<00:19:58.140> you<00:19:58.320> were 00:19:58.430 --> 00:19:58.440 align:start position:0% heavier than ideal so if you if you were 00:19:58.440 --> 00:20:01.070 align:start position:0% heavier than ideal so if you if you were to<00:19:58.620> really<00:19:59.100> so<00:19:59.640> the<00:19:59.940> get<00:20:00.059> light<00:20:00.360> client<00:20:00.780> even 00:20:01.070 --> 00:20:01.080 align:start position:0% to really so the get light client even 00:20:01.080 --> 00:20:03.230 align:start position:0% to really so the get light client even if<00:20:01.320> we<00:20:01.440> ship<00:20:01.679> it<00:20:01.860> as<00:20:01.980> production<00:20:02.340> ready<00:20:02.580> we're 00:20:03.230 --> 00:20:03.240 align:start position:0% if we ship it as production ready we're 00:20:03.240 --> 00:20:05.090 align:start position:0% if we ship it as production ready we're probably<00:20:03.480> more<00:20:03.780> cater<00:20:04.200> towards<00:20:04.559> running<00:20:04.740> on<00:20:04.980> a 00:20:05.090 --> 00:20:05.100 align:start position:0% probably more cater towards running on a 00:20:05.100 --> 00:20:06.770 align:start position:0% probably more cater towards running on a laptop<00:20:05.400> and<00:20:05.700> if<00:20:05.820> you<00:20:05.940> want<00:20:06.059> to<00:20:06.120> run<00:20:06.240> it<00:20:06.419> on<00:20:06.600> a 00:20:06.770 --> 00:20:06.780 align:start position:0% laptop and if you want to run it on a 00:20:06.780 --> 00:20:07.850 align:start position:0% laptop and if you want to run it on a mobile<00:20:06.960> phone 00:20:07.850 --> 00:20:07.860 align:start position:0% mobile phone 00:20:07.860 --> 00:20:10.850 align:start position:0% mobile phone in<00:20:08.400> a<00:20:08.580> production<00:20:08.820> at<00:20:09.120> the<00:20:09.240> environment<00:20:09.860> my 00:20:10.850 --> 00:20:10.860 align:start position:0% in a production at the environment my 00:20:10.860 --> 00:20:13.250 align:start position:0% in a production at the environment my guess<00:20:11.100> would<00:20:11.640> be<00:20:11.760> that<00:20:12.059> it<00:20:12.240> would<00:20:12.480> take<00:20:12.780> a 00:20:13.250 --> 00:20:13.260 align:start position:0% guess would be that it would take a 00:20:13.260 --> 00:20:15.049 align:start position:0% guess would be that it would take a different<00:20:13.380> team<00:20:13.799> maybe<00:20:14.220> a<00:20:14.640> slightly 00:20:15.049 --> 00:20:15.059 align:start position:0% different team maybe a slightly 00:20:15.059 --> 00:20:18.529 align:start position:0% different team maybe a slightly different<00:20:15.240> approach<00:20:15.900> to<00:20:16.679> to<00:20:17.039> get<00:20:17.340> there<00:20:17.520> no<00:20:18.179> so 00:20:18.529 --> 00:20:18.539 align:start position:0% different approach to to get there no so 00:20:18.539 --> 00:20:20.870 align:start position:0% different approach to to get there no so it's<00:20:18.780> it's<00:20:19.320> like<00:20:19.919> an<00:20:20.100> additional<00:20:20.460> thing<00:20:20.700> that 00:20:20.870 --> 00:20:20.880 align:start position:0% it's it's like an additional thing that 00:20:20.880 --> 00:20:22.370 align:start position:0% it's it's like an additional thing that we<00:20:21.059> have<00:20:21.179> to<00:20:21.360> maintain 00:20:22.370 --> 00:20:22.380 align:start position:0% we have to maintain 00:20:22.380 --> 00:20:25.610 align:start position:0% we have to maintain and<00:20:23.100> we<00:20:23.640> would<00:20:23.820> whatever<00:20:24.299> Android<00:20:24.720> users 00:20:25.610 --> 00:20:25.620 align:start position:0% and we would whatever Android users 00:20:25.620 --> 00:20:29.270 align:start position:0% and we would whatever Android users cross<00:20:25.980> compilation<00:20:27.080> is<00:20:28.080> always<00:20:28.440> broken<00:20:28.799> and 00:20:29.270 --> 00:20:29.280 align:start position:0% cross compilation is always broken and 00:20:29.280 --> 00:20:30.950 align:start position:0% cross compilation is always broken and there's<00:20:29.460> always<00:20:29.640> something<00:20:30.000> some<00:20:30.539> issues 00:20:30.950 --> 00:20:30.960 align:start position:0% there's always something some issues 00:20:30.960 --> 00:20:34.490 align:start position:0% there's always something some issues there<00:20:31.140> and<00:20:32.100> so<00:20:32.520> it<00:20:32.700> never<00:20:32.880> really<00:20:33.600> works<00:20:34.080> and 00:20:34.490 --> 00:20:34.500 align:start position:0% there and so it never really works and 00:20:34.500 --> 00:20:37.789 align:start position:0% there and so it never really works and sometimes<00:20:35.400> is<00:20:35.880> a<00:20:36.059> bit<00:20:36.120> clunky<00:20:36.600> the<00:20:37.380> code<00:20:37.500> that 00:20:37.789 --> 00:20:37.799 align:start position:0% sometimes is a bit clunky the code that 00:20:37.799 --> 00:20:39.950 align:start position:0% sometimes is a bit clunky the code that that<00:20:38.220> gets<00:20:38.760> produced 00:20:39.950 --> 00:20:39.960 align:start position:0% that gets produced 00:20:39.960 --> 00:20:43.310 align:start position:0% that gets produced and<00:20:40.799> so<00:20:41.220> I<00:20:41.400> think<00:20:41.700> another<00:20:42.539> team<00:20:42.900> just 00:20:43.310 --> 00:20:43.320 align:start position:0% and so I think another team just 00:20:43.320 --> 00:20:46.370 align:start position:0% and so I think another team just building<00:20:43.820> a<00:20:44.820> a<00:20:45.059> light<00:20:45.419> client<00:20:45.840> from<00:20:46.080> scratch 00:20:46.370 --> 00:20:46.380 align:start position:0% building a a light client from scratch 00:20:46.380 --> 00:20:49.789 align:start position:0% building a a light client from scratch for<00:20:47.100> for<00:20:47.460> mobile<00:20:47.880> phones<00:20:48.480> especially<00:20:49.440> after 00:20:49.789 --> 00:20:49.799 align:start position:0% for for mobile phones especially after 00:20:49.799 --> 00:20:54.169 align:start position:0% for for mobile phones especially after working<00:20:50.419> uh<00:20:51.419> would<00:20:51.900> we<00:20:52.799> will<00:20:52.919> definitely<00:20:53.280> some 00:20:54.169 --> 00:20:54.179 align:start position:0% working uh would we will definitely some 00:20:54.179 --> 00:20:57.169 align:start position:0% working uh would we will definitely some uh<00:20:54.539> see<00:20:54.840> some<00:20:55.260> stuff<00:20:55.500> there<00:20:55.740> and<00:20:56.520> I<00:20:56.640> hope<00:20:56.820> that 00:20:57.169 --> 00:20:57.179 align:start position:0% uh see some stuff there and I hope that 00:20:57.179 --> 00:20:59.029 align:start position:0% uh see some stuff there and I hope that at<00:20:57.600> that<00:20:57.780> point<00:20:57.960> we<00:20:58.200> can<00:20:58.380> just<00:20:58.559> get<00:20:58.740> rid<00:20:58.860> of 00:20:59.029 --> 00:20:59.039 align:start position:0% at that point we can just get rid of 00:20:59.039 --> 00:21:02.390 align:start position:0% at that point we can just get rid of this 00:21:02.390 --> 00:21:02.400 align:start position:0% 00:21:02.400 --> 00:21:05.870 align:start position:0% so<00:21:03.360> um<00:21:03.419> there's<00:21:03.900> also<00:21:04.559> a<00:21:04.799> bit<00:21:05.039> of<00:21:05.220> a<00:21:05.400> road<00:21:05.640> map 00:21:05.870 --> 00:21:05.880 align:start position:0% so um there's also a bit of a road map 00:21:05.880 --> 00:21:10.130 align:start position:0% so um there's also a bit of a road map issue<00:21:06.360> here<00:21:06.559> it<00:21:07.559> seems<00:21:07.919> that<00:21:08.220> you<00:21:08.940> know<00:21:09.059> uh<00:21:09.600> now 00:21:10.130 --> 00:21:10.140 align:start position:0% issue here it seems that you know uh now 00:21:10.140 --> 00:21:12.350 align:start position:0% issue here it seems that you know uh now the<00:21:10.380> direction<00:21:10.500> for<00:21:10.980> ethereum<00:21:11.520> is<00:21:11.700> to<00:21:12.000> have 00:21:12.350 --> 00:21:12.360 align:start position:0% the direction for ethereum is to have 00:21:12.360 --> 00:21:14.630 align:start position:0% the direction for ethereum is to have all<00:21:12.720> of<00:21:12.900> the<00:21:13.380> day-to-day<00:21:14.280> operation 00:21:14.630 --> 00:21:14.640 align:start position:0% all of the day-to-day operation 00:21:14.640 --> 00:21:17.270 align:start position:0% all of the day-to-day operation happening<00:21:15.179> in<00:21:15.360> rollups<00:21:15.960> and<00:21:16.620> having<00:21:16.860> the<00:21:17.100> core 00:21:17.270 --> 00:21:17.280 align:start position:0% happening in rollups and having the core 00:21:17.280 --> 00:21:20.750 align:start position:0% happening in rollups and having the core layer<00:21:17.700> be<00:21:18.660> something<00:21:19.020> more<00:21:19.440> I'm<00:21:20.280> not<00:21:20.460> going<00:21:20.640> to 00:21:20.750 --> 00:21:20.760 align:start position:0% layer be something more I'm not going to 00:21:20.760 --> 00:21:23.750 align:start position:0% layer be something more I'm not going to say<00:21:21.080> inaccessible<00:21:22.080> but<00:21:22.440> maybe<00:21:22.860> not<00:21:23.100> the<00:21:23.340> thing 00:21:23.750 --> 00:21:23.760 align:start position:0% say inaccessible but maybe not the thing 00:21:23.760 --> 00:21:26.810 align:start position:0% say inaccessible but maybe not the thing you<00:21:23.880> do<00:21:24.059> on<00:21:24.240> a<00:21:24.360> day-to-day<00:21:24.780> basis<00:21:25.520> if<00:21:26.520> that<00:21:26.700> is 00:21:26.810 --> 00:21:26.820 align:start position:0% you do on a day-to-day basis if that is 00:21:26.820 --> 00:21:29.149 align:start position:0% you do on a day-to-day basis if that is the<00:21:27.000> case<00:21:27.179> if<00:21:27.360> if<00:21:27.539> that<00:21:27.840> Trend<00:21:28.080> continues<00:21:28.559> I 00:21:29.149 --> 00:21:29.159 align:start position:0% the case if if that Trend continues I 00:21:29.159 --> 00:21:31.130 align:start position:0% the case if if that Trend continues I don't<00:21:29.220> think<00:21:29.400> it<00:21:29.580> makes<00:21:29.760> sense<00:21:30.000> to<00:21:30.419> to<00:21:30.600> worry 00:21:31.130 --> 00:21:31.140 align:start position:0% don't think it makes sense to to worry 00:21:31.140 --> 00:21:33.590 align:start position:0% don't think it makes sense to to worry about<00:21:31.440> mobile<00:21:31.799> because<00:21:32.280> no<00:21:32.940> one<00:21:33.059> is<00:21:33.299> going<00:21:33.419> to 00:21:33.590 --> 00:21:33.600 align:start position:0% about mobile because no one is going to 00:21:33.600 --> 00:21:36.230 align:start position:0% about mobile because no one is going to try<00:21:33.840> to<00:21:34.140> access<00:21:34.500> access<00:21:35.220> the<00:21:35.640> layer<00:21:35.880> one<00:21:36.000> from 00:21:36.230 --> 00:21:36.240 align:start position:0% try to access access the layer one from 00:21:36.240 --> 00:21:37.130 align:start position:0% try to access access the layer one from a<00:21:36.360> mobile 00:21:37.130 --> 00:21:37.140 align:start position:0% a mobile 00:21:37.140 --> 00:21:40.490 align:start position:0% a mobile one<00:21:37.980> more<00:21:38.159> thing<00:21:38.400> I<00:21:38.640> would<00:21:38.760> add<00:21:39.059> is<00:21:39.480> that<00:21:39.780> it's 00:21:40.490 --> 00:21:40.500 align:start position:0% one more thing I would add is that it's 00:21:40.500 --> 00:21:42.110 align:start position:0% one more thing I would add is that it's an<00:21:40.679> interesting<00:21:40.980> twist<00:21:41.340> post<00:21:41.520> merge<00:21:41.940> world 00:21:42.110 --> 00:21:42.120 align:start position:0% an interesting twist post merge world 00:21:42.120 --> 00:21:44.630 align:start position:0% an interesting twist post merge world that<00:21:42.900> before<00:21:43.080> the<00:21:43.320> merge<00:21:43.679> even<00:21:44.280> a<00:21:44.460> light 00:21:44.630 --> 00:21:44.640 align:start position:0% that before the merge even a light 00:21:44.640 --> 00:21:47.750 align:start position:0% that before the merge even a light client<00:21:45.000> had<00:21:45.240> to<00:21:45.419> have<00:21:45.659> a<00:21:46.020> lot<00:21:46.140> of<00:21:46.760> connections 00:21:47.750 --> 00:21:47.760 align:start position:0% client had to have a lot of connections 00:21:47.760 --> 00:21:49.490 align:start position:0% client had to have a lot of connections I<00:21:47.940> mean<00:21:48.059> you<00:21:48.179> either<00:21:48.360> connected<00:21:48.900> to<00:21:49.020> a<00:21:49.140> trusted 00:21:49.490 --> 00:21:49.500 align:start position:0% I mean you either connected to a trusted 00:21:49.500 --> 00:21:51.230 align:start position:0% I mean you either connected to a trusted server<00:21:50.039> which<00:21:50.340> kind<00:21:50.520> of<00:21:50.640> Beats<00:21:50.880> the<00:21:51.000> purpose 00:21:51.230 --> 00:21:51.240 align:start position:0% server which kind of Beats the purpose 00:21:51.240 --> 00:21:53.750 align:start position:0% server which kind of Beats the purpose or<00:21:52.080> you<00:21:52.260> had<00:21:52.440> to<00:21:52.620> connect<00:21:52.799> to<00:21:53.100> multiple<00:21:53.520> light 00:21:53.750 --> 00:21:53.760 align:start position:0% or you had to connect to multiple light 00:21:53.760 --> 00:21:55.850 align:start position:0% or you had to connect to multiple light servers<00:21:54.299> so<00:21:54.480> that<00:21:54.720> you<00:21:55.020> kind<00:21:55.380> of<00:21:55.440> got<00:21:55.620> the 00:21:55.850 --> 00:21:55.860 align:start position:0% servers so that you kind of got the 00:21:55.860 --> 00:21:57.470 align:start position:0% servers so that you kind of got the ground<00:21:55.980> truth<00:21:56.400> kind<00:21:56.700> of<00:21:56.820> follow<00:21:56.940> the<00:21:57.240> correct 00:21:57.470 --> 00:21:57.480 align:start position:0% ground truth kind of follow the correct 00:21:57.480 --> 00:21:59.450 align:start position:0% ground truth kind of follow the correct chain<00:21:57.659> based<00:21:58.020> on<00:21:58.080> proof<00:21:58.380> of<00:21:58.440> work<00:21:58.679> now<00:21:59.220> post 00:21:59.450 --> 00:21:59.460 align:start position:0% chain based on proof of work now post 00:21:59.460 --> 00:22:00.710 align:start position:0% chain based on proof of work now post merge 00:22:00.710 --> 00:22:00.720 align:start position:0% merge 00:22:00.720 --> 00:22:02.870 align:start position:0% merge you<00:22:01.260> don't<00:22:01.559> really<00:22:01.919> need<00:22:02.159> that<00:22:02.400> because<00:22:02.580> you 00:22:02.870 --> 00:22:02.880 align:start position:0% you don't really need that because you 00:22:02.880 --> 00:22:05.090 align:start position:0% you don't really need that because you have<00:22:03.000> the<00:22:03.179> signature<00:22:03.600> so<00:22:03.840> in<00:22:04.140> theory<00:22:04.440> post 00:22:05.090 --> 00:22:05.100 align:start position:0% have the signature so in theory post 00:22:05.100 --> 00:22:07.669 align:start position:0% have the signature so in theory post merge<00:22:05.520> you<00:22:05.700> could<00:22:06.059> connect<00:22:06.360> to<00:22:06.840> an<00:22:07.080> untrusted 00:22:07.669 --> 00:22:07.679 align:start position:0% merge you could connect to an untrusted 00:22:07.679 --> 00:22:10.669 align:start position:0% merge you could connect to an untrusted webto<00:22:08.640> provider<00:22:09.299> and<00:22:10.020> download<00:22:10.200> the 00:22:10.669 --> 00:22:10.679 align:start position:0% webto provider and download the 00:22:10.679 --> 00:22:12.590 align:start position:0% webto provider and download the necessary<00:22:11.039> data<00:22:11.460> you<00:22:11.640> could<00:22:11.760> still<00:22:12.000> verify<00:22:12.419> it 00:22:12.590 --> 00:22:12.600 align:start position:0% necessary data you could still verify it 00:22:12.600 --> 00:22:15.350 align:start position:0% necessary data you could still verify it so<00:22:13.320> this<00:22:13.799> kind<00:22:13.919> of<00:22:14.039> opens<00:22:14.400> up<00:22:14.520> a<00:22:14.820> bit<00:22:15.000> of<00:22:15.120> a 00:22:15.350 --> 00:22:15.360 align:start position:0% so this kind of opens up a bit of a 00:22:15.360 --> 00:22:17.810 align:start position:0% so this kind of opens up a bit of a different<00:22:15.600> design<00:22:16.200> direction<00:22:16.799> for<00:22:17.400> making 00:22:17.810 --> 00:22:17.820 align:start position:0% different design direction for making 00:22:17.820 --> 00:22:21.049 align:start position:0% different design direction for making ethereum<00:22:18.480> trustlessly<00:22:19.440> work<00:22:19.740> on<00:22:20.280> mobile 00:22:21.049 --> 00:22:21.059 align:start position:0% ethereum trustlessly work on mobile 00:22:21.059 --> 00:22:23.210 align:start position:0% ethereum trustlessly work on mobile phones 00:22:23.210 --> 00:22:23.220 align:start position:0% phones 00:22:23.220 --> 00:22:27.169 align:start position:0% phones uh<00:22:24.080> can<00:22:25.080> you<00:22:25.260> repeat<00:22:25.380> the<00:22:25.679> question<00:22:25.799> yes<00:22:26.340> this 00:22:27.169 --> 00:22:27.179 align:start position:0% uh can you repeat the question yes this 00:22:27.179 --> 00:22:29.750 align:start position:0% uh can you repeat the question yes this level<00:22:27.419> is<00:22:27.600> good<00:22:28.140> so 00:22:29.750 --> 00:22:29.760 align:start position:0% level is good so 00:22:29.760 --> 00:22:31.909 align:start position:0% level is good so what's<00:22:30.240> your<00:22:30.480> take<00:22:30.659> on<00:22:31.020> the<00:22:31.200> open<00:22:31.380> ethereum 00:22:31.909 --> 00:22:31.919 align:start position:0% what's your take on the open ethereum 00:22:31.919 --> 00:22:34.250 align:start position:0% what's your take on the open ethereum parity<00:22:32.460> Saga<00:22:33.000> and<00:22:33.600> what<00:22:33.720> can<00:22:33.960> the<00:22:34.140> community 00:22:34.250 --> 00:22:34.260 align:start position:0% parity Saga and what can the community 00:22:34.260 --> 00:22:35.990 align:start position:0% parity Saga and what can the community what<00:22:34.620> can<00:22:34.799> we<00:22:35.039> do<00:22:35.159> to<00:22:35.400> make<00:22:35.520> sure<00:22:35.700> that 00:22:35.990 --> 00:22:36.000 align:start position:0% what can we do to make sure that 00:22:36.000 --> 00:22:40.490 align:start position:0% what can we do to make sure that alternative<00:22:36.720> good<00:22:37.200> clients<00:22:37.740> don't<00:22:37.980> die<00:22:38.220> again 00:22:40.490 --> 00:22:40.500 align:start position:0% alternative good clients don't die again 00:22:40.500 --> 00:22:43.370 align:start position:0% alternative good clients don't die again I<00:22:41.100> think<00:22:41.340> that<00:22:42.360> um 00:22:43.370 --> 00:22:43.380 align:start position:0% I think that um 00:22:43.380 --> 00:22:45.230 align:start position:0% I think that um I<00:22:43.799> think<00:22:43.860> that's<00:22:44.039> inevitable 00:22:45.230 --> 00:22:45.240 align:start position:0% I think that's inevitable 00:22:45.240 --> 00:22:48.250 align:start position:0% I think that's inevitable so<00:22:45.600> in<00:22:45.720> my<00:22:45.900> opinion<00:22:46.260> good<00:22:47.039> clients<00:22:47.520> will<00:22:47.880> die 00:22:48.250 --> 00:22:48.260 align:start position:0% so in my opinion good clients will die 00:22:48.260 --> 00:22:50.630 align:start position:0% so in my opinion good clients will die it's<00:22:49.260> uh 00:22:50.630 --> 00:22:50.640 align:start position:0% it's uh 00:22:50.640 --> 00:22:53.690 align:start position:0% it's uh I<00:22:51.600> mean<00:22:51.780> look<00:22:52.620> at<00:22:52.799> the<00:22:52.919> gas<00:22:53.039> team<00:22:53.220> gas<00:22:53.460> team 00:22:53.690 --> 00:22:53.700 align:start position:0% I mean look at the gas team gas team 00:22:53.700 --> 00:22:57.289 align:start position:0% I mean look at the gas team gas team currently<00:22:54.179> has<00:22:54.659> is<00:22:54.960> about<00:22:55.200> 10<00:22:55.919> people<00:22:56.280> now<00:22:57.120> I 00:22:57.289 --> 00:22:57.299 align:start position:0% currently has is about 10 people now I 00:22:57.299 --> 00:22:59.270 align:start position:0% currently has is about 10 people now I would<00:22:57.419> say<00:22:57.600> that<00:22:57.960> out<00:22:58.500> of<00:22:58.679> these<00:22:58.919> 10<00:22:59.039> people 00:22:59.270 --> 00:22:59.280 align:start position:0% would say that out of these 10 people 00:22:59.280 --> 00:23:01.450 align:start position:0% would say that out of these 10 people you<00:22:59.640> have<00:22:59.820> probably<00:23:00.059> four<00:23:00.480> to<00:23:00.659> five<00:23:00.900> people 00:23:01.450 --> 00:23:01.460 align:start position:0% you have probably four to five people 00:23:01.460 --> 00:23:03.590 align:start position:0% you have probably four to five people that<00:23:02.460> are 00:23:03.590 --> 00:23:03.600 align:start position:0% that are 00:23:03.600 --> 00:23:06.590 align:start position:0% that are kind<00:23:04.260> of<00:23:04.380> more<00:23:04.679> familiar<00:23:05.159> with<00:23:05.760> the<00:23:06.059> very<00:23:06.419> very 00:23:06.590 --> 00:23:06.600 align:start position:0% kind of more familiar with the very very 00:23:06.600 --> 00:23:10.549 align:start position:0% kind of more familiar with the very very internal<00:23:07.559> details<00:23:08.100> now<00:23:09.020> should<00:23:10.020> these<00:23:10.440> four 00:23:10.549 --> 00:23:10.559 align:start position:0% internal details now should these four 00:23:10.559 --> 00:23:11.870 align:start position:0% internal details now should these four or<00:23:10.740> five<00:23:10.919> people 00:23:11.870 --> 00:23:11.880 align:start position:0% or five people 00:23:11.880 --> 00:23:14.630 align:start position:0% or five people leave<00:23:12.539> it<00:23:13.440> is<00:23:13.620> very<00:23:13.799> very<00:23:13.980> hard<00:23:14.280> to<00:23:14.460> find 00:23:14.630 --> 00:23:14.640 align:start position:0% leave it is very very hard to find 00:23:14.640 --> 00:23:16.070 align:start position:0% leave it is very very hard to find replacements<00:23:15.299> for<00:23:15.419> them<00:23:15.600> and<00:23:15.840> this<00:23:15.960> is 00:23:16.070 --> 00:23:16.080 align:start position:0% replacements for them and this is 00:23:16.080 --> 00:23:18.169 align:start position:0% replacements for them and this is essentially<00:23:16.380> what<00:23:16.559> happened<00:23:16.740> with<00:23:16.980> parity 00:23:18.169 --> 00:23:18.179 align:start position:0% essentially what happened with parity 00:23:18.179 --> 00:23:20.149 align:start position:0% essentially what happened with parity okay<00:23:18.659> they're<00:23:18.900> leaving<00:23:19.260> it<00:23:19.620> was<00:23:19.799> a<00:23:19.980> bit 00:23:20.149 --> 00:23:20.159 align:start position:0% okay they're leaving it was a bit 00:23:20.159 --> 00:23:22.310 align:start position:0% okay they're leaving it was a bit different<00:23:20.340> but<00:23:20.760> the<00:23:21.000> idea<00:23:21.480> is<00:23:21.600> that<00:23:21.780> if<00:23:22.080> you 00:23:22.310 --> 00:23:22.320 align:start position:0% different but the idea is that if you 00:23:22.320 --> 00:23:24.529 align:start position:0% different but the idea is that if you actually<00:23:22.919> manage<00:23:23.340> to<00:23:23.460> simultaneously<00:23:24.179> lose 00:23:24.529 --> 00:23:24.539 align:start position:0% actually manage to simultaneously lose 00:23:24.539 --> 00:23:27.350 align:start position:0% actually manage to simultaneously lose enough<00:23:24.840> of<00:23:25.140> your<00:23:25.500> main<00:23:26.340> contributors<00:23:27.059> then 00:23:27.350 --> 00:23:27.360 align:start position:0% enough of your main contributors then 00:23:27.360 --> 00:23:29.630 align:start position:0% enough of your main contributors then it's<00:23:27.600> very<00:23:27.900> very<00:23:28.140> hard<00:23:28.559> to<00:23:28.740> onboard<00:23:29.280> enough 00:23:29.630 --> 00:23:29.640 align:start position:0% it's very very hard to onboard enough 00:23:29.640 --> 00:23:31.490 align:start position:0% it's very very hard to onboard enough people<00:23:29.940> fast<00:23:30.360> enough<00:23:30.539> so<00:23:30.900> that<00:23:31.080> the<00:23:31.320> the 00:23:31.490 --> 00:23:31.500 align:start position:0% people fast enough so that the the 00:23:31.500 --> 00:23:34.570 align:start position:0% people fast enough so that the the project<00:23:31.799> survives<00:23:32.419> and<00:23:33.419> I<00:23:33.539> think<00:23:33.720> that<00:23:33.960> it's 00:23:34.570 --> 00:23:34.580 align:start position:0% project survives and I think that it's 00:23:34.580 --> 00:23:38.570 align:start position:0% project survives and I think that it's as<00:23:35.580> bad<00:23:35.940> as<00:23:36.179> it<00:23:36.419> is<00:23:36.659> to<00:23:37.020> lose<00:23:37.200> a<00:23:37.559> client<00:23:37.860> I<00:23:38.460> don't 00:23:38.570 --> 00:23:38.580 align:start position:0% as bad as it is to lose a client I don't 00:23:38.580 --> 00:23:40.370 align:start position:0% as bad as it is to lose a client I don't really<00:23:38.760> see<00:23:39.059> what<00:23:39.360> you<00:23:39.539> can<00:23:39.659> do<00:23:39.900> I<00:23:40.080> mean<00:23:40.200> the 00:23:40.370 --> 00:23:40.380 align:start position:0% really see what you can do I mean the 00:23:40.380 --> 00:23:41.990 align:start position:0% really see what you can do I mean the same<00:23:40.500> happens<00:23:40.740> in<00:23:40.980> open<00:23:41.159> source<00:23:41.580> software<00:23:41.820> too 00:23:41.990 --> 00:23:42.000 align:start position:0% same happens in open source software too 00:23:42.000 --> 00:23:43.130 align:start position:0% same happens in open source software too that 00:23:43.130 --> 00:23:43.140 align:start position:0% that 00:23:43.140 --> 00:23:45.169 align:start position:0% that eventually<00:23:43.980> you<00:23:44.220> have<00:23:44.340> a<00:23:44.520> couple<00:23:44.640> maintainers 00:23:45.169 --> 00:23:45.179 align:start position:0% eventually you have a couple maintainers 00:23:45.179 --> 00:23:46.190 align:start position:0% eventually you have a couple maintainers that<00:23:45.480> just 00:23:46.190 --> 00:23:46.200 align:start position:0% that just 00:23:46.200 --> 00:23:49.370 align:start position:0% that just I<00:23:46.679> mean<00:23:46.799> life<00:23:47.159> happens<00:23:47.520> they<00:23:48.120> go<00:23:48.480> do<00:23:49.080> something 00:23:49.370 --> 00:23:49.380 align:start position:0% I mean life happens they go do something 00:23:49.380 --> 00:23:51.409 align:start position:0% I mean life happens they go do something else<00:23:49.620> either<00:23:49.919> because<00:23:50.159> they<00:23:50.460> get<00:23:50.640> bored<00:23:51.059> or 00:23:51.409 --> 00:23:51.419 align:start position:0% else either because they get bored or 00:23:51.419 --> 00:23:52.970 align:start position:0% else either because they get bored or whatever<00:23:51.960> reason 00:23:52.970 --> 00:23:52.980 align:start position:0% whatever reason 00:23:52.980 --> 00:23:55.130 align:start position:0% whatever reason and 00:23:55.130 --> 00:23:55.140 align:start position:0% and 00:23:55.140 --> 00:23:56.810 align:start position:0% and I'm<00:23:55.500> not<00:23:55.740> sure<00:23:55.919> that 00:23:56.810 --> 00:23:56.820 align:start position:0% I'm not sure that 00:23:56.820 --> 00:23:59.029 align:start position:0% I'm not sure that um 00:23:59.029 --> 00:23:59.039 align:start position:0% 00:23:59.039 --> 00:24:02.330 align:start position:0% yeah<00:23:59.400> so<00:23:59.760> I<00:23:59.880> I<00:24:00.059> I<00:24:00.240> think<00:24:01.140> it<00:24:01.559> is<00:24:01.740> a<00:24:01.980> very<00:24:02.100> real 00:24:02.330 --> 00:24:02.340 align:start position:0% yeah so I I I think it is a very real 00:24:02.340 --> 00:24:04.250 align:start position:0% yeah so I I I think it is a very real chance<00:24:02.760> and<00:24:03.299> it<00:24:03.480> will<00:24:03.720> definitely<00:24:03.960> happen 00:24:04.250 --> 00:24:04.260 align:start position:0% chance and it will definitely happen 00:24:04.260 --> 00:24:09.669 align:start position:0% chance and it will definitely happen that<00:24:04.740> good<00:24:05.460> clients<00:24:06.059> will<00:24:06.960> die 00:24:09.669 --> 00:24:09.679 align:start position:0% 00:24:09.679 --> 00:24:12.529 align:start position:0% there's<00:24:10.679> always<00:24:10.799> a<00:24:11.159> I<00:24:11.520> mean<00:24:11.700> one<00:24:12.000> way<00:24:12.299> to 00:24:12.529 --> 00:24:12.539 align:start position:0% there's always a I mean one way to 00:24:12.539 --> 00:24:14.210 align:start position:0% there's always a I mean one way to protect<00:24:12.780> it<00:24:12.960> is<00:24:13.140> if<00:24:13.380> there's<00:24:13.679> a<00:24:13.980> very<00:24:14.100> very 00:24:14.210 --> 00:24:14.220 align:start position:0% protect it is if there's a very very 00:24:14.220 --> 00:24:16.610 align:start position:0% protect it is if there's a very very good<00:24:14.460> funding<00:24:14.820> behind<00:24:15.179> it<00:24:15.360> maybe<00:24:15.659> a<00:24:16.500> large 00:24:16.610 --> 00:24:16.620 align:start position:0% good funding behind it maybe a large 00:24:16.620 --> 00:24:19.610 align:start position:0% good funding behind it maybe a large corporation<00:24:17.220> but<00:24:17.700> again<00:24:17.940> if<00:24:18.299> there's<00:24:18.720> a<00:24:19.500> large 00:24:19.610 --> 00:24:19.620 align:start position:0% corporation but again if there's a large 00:24:19.620 --> 00:24:21.110 align:start position:0% corporation but again if there's a large corporation<00:24:20.039> behind<00:24:20.460> it<00:24:20.580> they<00:24:20.760> can<00:24:20.940> always 00:24:21.110 --> 00:24:21.120 align:start position:0% corporation behind it they can always 00:24:21.120 --> 00:24:22.970 align:start position:0% corporation behind it they can always decide<00:24:21.720> that<00:24:21.840> it's<00:24:22.020> not<00:24:22.200> worth<00:24:22.440> it<00:24:22.620> to<00:24:22.799> keep 00:24:22.970 --> 00:24:22.980 align:start position:0% decide that it's not worth it to keep 00:24:22.980 --> 00:24:24.830 align:start position:0% decide that it's not worth it to keep going<00:24:23.159> so<00:24:23.880> it's<00:24:24.059> a 00:24:24.830 --> 00:24:24.840 align:start position:0% going so it's a 00:24:24.840 --> 00:24:27.230 align:start position:0% going so it's a I<00:24:25.380> guess<00:24:25.559> that<00:24:25.799> it<00:24:26.340> boils<00:24:26.640> down<00:24:26.760> to<00:24:26.940> the<00:24:27.059> fact 00:24:27.230 --> 00:24:27.240 align:start position:0% I guess that it boils down to the fact 00:24:27.240 --> 00:24:28.909 align:start position:0% I guess that it boils down to the fact that<00:24:27.480> you<00:24:27.600> need<00:24:27.780> this<00:24:28.200> is<00:24:28.260> why<00:24:28.440> we<00:24:28.620> would<00:24:28.740> need 00:24:28.909 --> 00:24:28.919 align:start position:0% that you need this is why we would need 00:24:28.919 --> 00:24:30.590 align:start position:0% that you need this is why we would need client<00:24:29.340> diversity<00:24:29.880> because<00:24:30.120> that<00:24:30.419> kind<00:24:30.539> of 00:24:30.590 --> 00:24:30.600 align:start position:0% client diversity because that kind of 00:24:30.600 --> 00:24:33.590 align:start position:0% client diversity because that kind of affords<00:24:31.140> us<00:24:31.380> good<00:24:32.159> clients<00:24:32.700> occasionally 00:24:33.590 --> 00:24:33.600 align:start position:0% affords us good clients occasionally 00:24:33.600 --> 00:24:37.970 align:start position:0% affords us good clients occasionally disappearing 00:24:37.970 --> 00:24:37.980 align:start position:0% 00:24:37.980 --> 00:24:40.250 align:start position:0% and<00:24:38.580> and<00:24:38.580> I<00:24:38.940> think<00:24:39.059> within<00:24:39.600> the<00:24:39.840> guest<00:24:39.960> team 00:24:40.250 --> 00:24:40.260 align:start position:0% and and I think within the guest team 00:24:40.260 --> 00:24:42.049 align:start position:0% and and I think within the guest team we're<00:24:40.440> trying<00:24:40.740> to<00:24:41.039> prevent<00:24:41.340> this<00:24:41.640> by 00:24:42.049 --> 00:24:42.059 align:start position:0% we're trying to prevent this by 00:24:42.059 --> 00:24:44.090 align:start position:0% we're trying to prevent this by onboarding<00:24:42.659> new<00:24:42.840> people<00:24:43.140> and<00:24:43.559> making<00:24:43.799> sure 00:24:44.090 --> 00:24:44.100 align:start position:0% onboarding new people and making sure 00:24:44.100 --> 00:24:46.970 align:start position:0% onboarding new people and making sure the<00:24:44.460> the<00:24:44.940> uh<00:24:45.720> the<00:24:46.020> new<00:24:46.080> people<00:24:46.320> that<00:24:46.559> come<00:24:46.799> in 00:24:46.970 --> 00:24:46.980 align:start position:0% the the uh the new people that come in 00:24:46.980 --> 00:24:49.130 align:start position:0% the the uh the new people that come in get<00:24:47.640> familiar<00:24:48.120> with 00:24:49.130 --> 00:24:49.140 align:start position:0% get familiar with 00:24:49.140 --> 00:24:52.190 align:start position:0% get familiar with um a<00:24:49.860> lot<00:24:49.919> of<00:24:50.039> the<00:24:50.220> different<00:24:50.780> parts<00:24:51.780> of<00:24:52.020> the 00:24:52.190 --> 00:24:52.200 align:start position:0% um a lot of the different parts of the 00:24:52.200 --> 00:24:56.029 align:start position:0% um a lot of the different parts of the code<00:24:52.380> and<00:24:53.280> so<00:24:53.520> but<00:24:54.240> it's<00:24:54.419> very<00:24:54.659> hard<00:24:54.960> for<00:24:55.380> us 00:24:56.029 --> 00:24:56.039 align:start position:0% code and so but it's very hard for us 00:24:56.039 --> 00:24:58.610 align:start position:0% code and so but it's very hard for us being<00:24:56.340> relatively<00:24:57.059> new 00:24:58.610 --> 00:24:58.620 align:start position:0% being relatively new 00:24:58.620 --> 00:24:59.230 align:start position:0% being relatively new um 00:24:59.230 --> 00:24:59.240 align:start position:0% um 00:24:59.240 --> 00:25:02.870 align:start position:0% um to<00:25:00.240> meaningfully<00:25:00.960> contribute<00:25:01.440> because<00:25:01.980> there 00:25:02.870 --> 00:25:02.880 align:start position:0% to meaningfully contribute because there 00:25:02.880 --> 00:25:05.450 align:start position:0% to meaningfully contribute because there are<00:25:03.059> so<00:25:03.539> many<00:25:03.780> just<00:25:04.200> invariants<00:25:04.799> within<00:25:05.280> the 00:25:05.450 --> 00:25:05.460 align:start position:0% are so many just invariants within the 00:25:05.460 --> 00:25:09.830 align:start position:0% are so many just invariants within the code<00:25:05.659> that<00:25:06.659> are<00:25:06.900> not<00:25:07.580> explicitly<00:25:08.580> stated<00:25:08.940> and 00:25:09.830 --> 00:25:09.840 align:start position:0% code that are not explicitly stated and 00:25:09.840 --> 00:25:11.690 align:start position:0% code that are not explicitly stated and so<00:25:10.020> sometimes<00:25:10.440> it<00:25:10.679> happens<00:25:10.860> that<00:25:11.159> we<00:25:11.340> break<00:25:11.460> an 00:25:11.690 --> 00:25:11.700 align:start position:0% so sometimes it happens that we break an 00:25:11.700 --> 00:25:14.330 align:start position:0% so sometimes it happens that we break an invariant<00:25:12.240> and<00:25:12.960> it's<00:25:13.140> usually<00:25:13.440> Peter<00:25:13.860> who<00:25:14.159> has 00:25:14.330 --> 00:25:14.340 align:start position:0% invariant and it's usually Peter who has 00:25:14.340 --> 00:25:16.850 align:start position:0% invariant and it's usually Peter who has all<00:25:14.580> of<00:25:14.700> the<00:25:14.820> invariants<00:25:15.299> in<00:25:15.600> his<00:25:15.780> head<00:25:15.960> and 00:25:16.850 --> 00:25:16.860 align:start position:0% all of the invariants in his head and 00:25:16.860 --> 00:25:19.850 align:start position:0% all of the invariants in his head and and<00:25:17.159> says<00:25:17.700> okay<00:25:18.179> we're<00:25:19.020> breaking<00:25:19.500> in<00:25:19.620> and 00:25:19.850 --> 00:25:19.860 align:start position:0% and says okay we're breaking in and 00:25:19.860 --> 00:25:22.730 align:start position:0% and says okay we're breaking in and variant<00:25:20.220> here<00:25:20.460> don't<00:25:21.240> do<00:25:21.539> this<00:25:21.780> this<00:25:22.320> is<00:25:22.559> going 00:25:22.730 --> 00:25:22.740 align:start position:0% variant here don't do this this is going 00:25:22.740 --> 00:25:27.590 align:start position:0% variant here don't do this this is going to<00:25:22.919> to<00:25:23.340> to<00:25:23.400> fail<00:25:24.200> at<00:25:25.200> some<00:25:25.320> point<00:25:25.700> and<00:25:26.700> it<00:25:27.480> just 00:25:27.590 --> 00:25:27.600 align:start position:0% to to to fail at some point and it just 00:25:27.600 --> 00:25:31.549 align:start position:0% to to to fail at some point and it just takes<00:25:27.960> a<00:25:28.320> long<00:25:28.500> time<00:25:29.360> to<00:25:30.360> actually<00:25:30.659> learn<00:25:31.200> all 00:25:31.549 --> 00:25:31.559 align:start position:0% takes a long time to actually learn all 00:25:31.559 --> 00:25:34.549 align:start position:0% takes a long time to actually learn all of<00:25:31.740> these<00:25:32.039> invariants<00:25:32.840> that<00:25:33.840> are<00:25:34.020> implicitly 00:25:34.549 --> 00:25:34.559 align:start position:0% of these invariants that are implicitly 00:25:34.559 --> 00:25:37.909 align:start position:0% of these invariants that are implicitly in<00:25:34.919> the<00:25:35.100> code<00:25:35.600> plugging<00:25:36.600> back<00:25:36.720> to<00:25:36.960> one<00:25:37.320> idea<00:25:37.679> I 00:25:37.909 --> 00:25:37.919 align:start position:0% in the code plugging back to one idea I 00:25:37.919 --> 00:25:39.950 align:start position:0% in the code plugging back to one idea I was<00:25:38.100> talking<00:25:38.279> about<00:25:38.460> before<00:25:38.820> just<00:25:39.600> the<00:25:39.779> fact 00:25:39.950 --> 00:25:39.960 align:start position:0% was talking about before just the fact 00:25:39.960 --> 00:25:41.810 align:start position:0% was talking about before just the fact that<00:25:40.140> for<00:25:40.320> example<00:25:40.500> we<00:25:40.919> kind<00:25:41.279> of<00:25:41.340> spin<00:25:41.700> off 00:25:41.810 --> 00:25:41.820 align:start position:0% that for example we kind of spin off 00:25:41.820 --> 00:25:43.370 align:start position:0% that for example we kind of spin off consensus 00:25:43.370 --> 00:25:43.380 align:start position:0% consensus 00:25:43.380 --> 00:25:46.070 align:start position:0% consensus if<00:25:44.220> another<00:25:44.400> one<00:25:44.940> of<00:25:45.059> those<00:25:45.179> steps<00:25:45.480> happens<00:25:45.720> in 00:25:46.070 --> 00:25:46.080 align:start position:0% if another one of those steps happens in 00:25:46.080 --> 00:25:47.810 align:start position:0% if another one of those steps happens in the<00:25:46.140> future<00:25:46.260> like<00:25:46.919> maintaining<00:25:47.460> a<00:25:47.580> client 00:25:47.810 --> 00:25:47.820 align:start position:0% the future like maintaining a client 00:25:47.820 --> 00:25:49.909 align:start position:0% the future like maintaining a client becomes<00:25:48.360> easier<00:25:48.960> and<00:25:49.080> easier<00:25:49.380> so<00:25:49.559> that<00:25:49.740> would 00:25:49.909 --> 00:25:49.919 align:start position:0% becomes easier and easier so that would 00:25:49.919 --> 00:25:53.090 align:start position:0% becomes easier and easier so that would be<00:25:50.159> a<00:25:50.760> good 00:25:53.090 --> 00:25:53.100 align:start position:0% 00:25:53.100 --> 00:25:55.190 align:start position:0% I<00:25:53.279> forgot<00:25:53.580> the<00:25:53.700> word<00:25:53.820> but<00:25:54.059> it<00:25:54.720> would<00:25:54.840> be<00:25:54.960> a<00:25:55.080> good 00:25:55.190 --> 00:25:55.200 align:start position:0% I forgot the word but it would be a good 00:25:55.200 --> 00:25:58.730 align:start position:0% I forgot the word but it would be a good way<00:25:55.380> to<00:25:55.880> make<00:25:56.880> clients<00:25:57.360> not<00:25:57.720> be<00:25:58.200> at<00:25:58.380> risk<00:25:58.679> of 00:25:58.730 --> 00:25:58.740 align:start position:0% way to make clients not be at risk of 00:25:58.740 --> 00:26:01.430 align:start position:0% way to make clients not be at risk of dying<00:25:59.100> but<00:25:59.820> until<00:26:00.120> until<00:26:00.600> we<00:26:00.900> do<00:26:01.020> until<00:26:01.140> we 00:26:01.430 --> 00:26:01.440 align:start position:0% dying but until until we do until we 00:26:01.440 --> 00:26:03.649 align:start position:0% dying but until until we do until we simplify<00:26:01.799> the<00:26:02.039> protocol<00:26:02.340> it's<00:26:03.059> uh<00:26:03.240> yeah<00:26:03.480> it's 00:26:03.649 --> 00:26:03.659 align:start position:0% simplify the protocol it's uh yeah it's 00:26:03.659 --> 00:26:05.090 align:start position:0% simplify the protocol it's uh yeah it's going<00:26:03.840> to<00:26:03.960> happen 00:26:05.090 --> 00:26:05.100 align:start position:0% going to happen 00:26:05.100 --> 00:26:08.149 align:start position:0% going to happen and<00:26:05.760> one<00:26:06.240> thing<00:26:06.419> that<00:26:06.659> I<00:26:06.900> also<00:26:07.500> really<00:26:07.679> like<00:26:07.919> on 00:26:08.149 --> 00:26:08.159 align:start position:0% and one thing that I also really like on 00:26:08.159 --> 00:26:11.870 align:start position:0% and one thing that I also really like on the<00:26:08.279> roadmap<00:26:08.700> is<00:26:09.059> these<00:26:09.720> uh<00:26:10.200> the<00:26:10.860> perch<00:26:11.220> where 00:26:11.870 --> 00:26:11.880 align:start position:0% the roadmap is these uh the perch where 00:26:11.880 --> 00:26:14.210 align:start position:0% the roadmap is these uh the perch where we<00:26:12.120> try<00:26:12.360> to<00:26:12.539> get<00:26:12.779> try<00:26:13.200> to<00:26:13.380> eliminate<00:26:13.799> some<00:26:14.100> of 00:26:14.210 --> 00:26:14.220 align:start position:0% we try to get try to eliminate some of 00:26:14.220 --> 00:26:15.169 align:start position:0% we try to get try to eliminate some of the 00:26:15.169 --> 00:26:15.179 align:start position:0% the 00:26:15.179 --> 00:26:15.950 align:start position:0% the um 00:26:15.950 --> 00:26:15.960 align:start position:0% um 00:26:15.960 --> 00:26:18.890 align:start position:0% um all<00:26:16.860> outdated<00:26:17.760> stuff 00:26:18.890 --> 00:26:18.900 align:start position:0% all outdated stuff 00:26:18.900 --> 00:26:22.669 align:start position:0% all outdated stuff and<00:26:19.860> so<00:26:20.460> for<00:26:20.700> example<00:26:20.940> history<00:26:21.299> expiry<00:26:22.020> would 00:26:22.669 --> 00:26:22.679 align:start position:0% and so for example history expiry would 00:26:22.679 --> 00:26:25.789 align:start position:0% and so for example history expiry would allow<00:26:23.039> us<00:26:23.159> to<00:26:23.700> delete<00:26:24.059> all<00:26:24.600> of<00:26:24.720> the<00:26:25.020> rules<00:26:25.500> that 00:26:25.789 --> 00:26:25.799 align:start position:0% allow us to delete all of the rules that 00:26:25.799 --> 00:26:27.970 align:start position:0% allow us to delete all of the rules that we<00:26:25.919> have<00:26:26.039> for<00:26:26.279> executing<00:26:26.820> all<00:26:27.059> transactions 00:26:27.970 --> 00:26:27.980 align:start position:0% we have for executing all transactions 00:26:27.980 --> 00:26:32.149 align:start position:0% we have for executing all transactions and<00:26:29.360> at<00:26:30.360> some<00:26:30.779> point<00:26:31.020> if<00:26:31.440> there's<00:26:31.620> a<00:26:31.799> way<00:26:31.919> to 00:26:32.149 --> 00:26:32.159 align:start position:0% and at some point if there's a way to 00:26:32.159 --> 00:26:34.789 align:start position:0% and at some point if there's a way to execute<00:26:32.640> them<00:26:32.940> in<00:26:33.240> a<00:26:33.419> different<00:26:33.539> client<00:26:34.020> and 00:26:34.789 --> 00:26:34.799 align:start position:0% execute them in a different client and 00:26:34.799 --> 00:26:38.330 align:start position:0% execute them in a different client and and<00:26:35.039> all<00:26:35.700> of<00:26:35.820> these<00:26:35.940> caveats<00:26:36.539> but<00:26:37.320> it<00:26:38.100> would 00:26:38.330 --> 00:26:38.340 align:start position:0% and all of these caveats but it would 00:26:38.340 --> 00:26:41.649 align:start position:0% and all of these caveats but it would make<00:26:38.720> maintaining<00:26:39.720> a<00:26:39.960> client<00:26:40.200> a<00:26:40.440> lot<00:26:40.559> easier 00:26:41.649 --> 00:26:41.659 align:start position:0% make maintaining a client a lot easier 00:26:41.659 --> 00:26:44.690 align:start position:0% make maintaining a client a lot easier another<00:26:42.659> issue<00:26:43.020> that<00:26:43.200> we<00:26:43.380> always<00:26:43.559> run<00:26:43.860> into<00:26:44.100> is 00:26:44.690 --> 00:26:44.700 align:start position:0% another issue that we always run into is 00:26:44.700 --> 00:26:48.169 align:start position:0% another issue that we always run into is that<00:26:45.600> someone<00:26:45.919> wants<00:26:46.919> a<00:26:46.980> feature<00:26:47.340> and<00:26:48.000> we 00:26:48.169 --> 00:26:48.179 align:start position:0% that someone wants a feature and we 00:26:48.179 --> 00:26:50.090 align:start position:0% that someone wants a feature and we don't<00:26:48.419> really 00:26:50.090 --> 00:26:50.100 align:start position:0% don't really 00:26:50.100 --> 00:26:52.610 align:start position:0% don't really think<00:26:50.880> about<00:26:51.120> it<00:26:51.419> and<00:26:51.720> care<00:26:51.960> and<00:26:52.200> implement 00:26:52.610 --> 00:26:52.620 align:start position:0% think about it and care and implement 00:26:52.620 --> 00:26:56.269 align:start position:0% think about it and care and implement the<00:26:52.860> feature<00:26:53.279> and<00:26:53.400> and<00:26:53.640> merge<00:26:54.000> it<00:26:54.059> in<00:26:54.320> and<00:26:55.320> two 00:26:56.269 --> 00:26:56.279 align:start position:0% the feature and and merge it in and two 00:26:56.279 --> 00:26:59.769 align:start position:0% the feature and and merge it in and two years<00:26:56.520> later<00:26:56.820> or<00:26:57.360> sometime<00:26:58.080> sometime<00:26:58.799> later 00:26:59.769 --> 00:26:59.779 align:start position:0% years later or sometime sometime later 00:26:59.779 --> 00:27:02.870 align:start position:0% years later or sometime sometime later we<00:27:00.779> realized<00:27:01.380> that<00:27:01.559> this<00:27:01.740> features 00:27:02.870 --> 00:27:02.880 align:start position:0% we realized that this features 00:27:02.880 --> 00:27:06.529 align:start position:0% we realized that this features not<00:27:03.360> really<00:27:03.539> used<00:27:03.720> by<00:27:04.020> anyone<00:27:04.380> not<00:27:04.740> and<00:27:05.279> and<00:27:05.700> we 00:27:06.529 --> 00:27:06.539 align:start position:0% not really used by anyone not and and we 00:27:06.539 --> 00:27:08.810 align:start position:0% not really used by anyone not and and we cannot<00:27:06.900> change<00:27:07.260> something<00:27:07.559> because<00:27:08.039> we<00:27:08.640> would 00:27:08.810 --> 00:27:08.820 align:start position:0% cannot change something because we would 00:27:08.820 --> 00:27:12.409 align:start position:0% cannot change something because we would break<00:27:09.059> this<00:27:09.360> one<00:27:09.539> feature<00:27:10.500> and<00:27:11.400> at<00:27:12.000> that<00:27:12.240> point 00:27:12.409 --> 00:27:12.419 align:start position:0% break this one feature and at that point 00:27:12.419 --> 00:27:15.529 align:start position:0% break this one feature and at that point we<00:27:12.900> have<00:27:13.080> a<00:27:13.200> decision<00:27:13.500> to<00:27:13.679> make<00:27:13.860> either<00:27:14.400> we 00:27:15.529 --> 00:27:15.539 align:start position:0% we have a decision to make either we 00:27:15.539 --> 00:27:18.289 align:start position:0% we have a decision to make either we like<00:27:16.620> either<00:27:17.220> we 00:27:18.289 --> 00:27:18.299 align:start position:0% like either we 00:27:18.299 --> 00:27:20.930 align:start position:0% like either we just<00:27:19.080> don't<00:27:19.440> do<00:27:19.620> anything<00:27:19.860> or<00:27:20.340> we<00:27:20.460> delete<00:27:20.640> the 00:27:20.930 --> 00:27:20.940 align:start position:0% just don't do anything or we delete the 00:27:20.940 --> 00:27:22.909 align:start position:0% just don't do anything or we delete the feature<00:27:21.360> and<00:27:21.720> someone<00:27:21.900> is<00:27:22.140> going<00:27:22.320> to<00:27:22.380> be<00:27:22.559> upset 00:27:22.909 --> 00:27:22.919 align:start position:0% feature and someone is going to be upset 00:27:22.919 --> 00:27:25.070 align:start position:0% feature and someone is going to be upset and<00:27:24.419> um 00:27:25.070 --> 00:27:25.080 align:start position:0% and um 00:27:25.080 --> 00:27:27.470 align:start position:0% and um we<00:27:25.620> don't<00:27:25.799> want<00:27:25.980> to<00:27:26.100> make<00:27:26.220> people<00:27:26.400> upset<00:27:26.880> but 00:27:27.470 --> 00:27:27.480 align:start position:0% we don't want to make people upset but 00:27:27.480 --> 00:27:29.750 align:start position:0% we don't want to make people upset but it's<00:27:27.779> inevitable<00:27:28.380> I<00:27:29.039> think<00:27:29.159> with<00:27:29.400> the<00:27:29.580> with 00:27:29.750 --> 00:27:29.760 align:start position:0% it's inevitable I think with the with 00:27:29.760 --> 00:27:32.510 align:start position:0% it's inevitable I think with the with the<00:27:29.940> way<00:27:30.059> Geth<00:27:30.480> is<00:27:30.600> right<00:27:30.840> now 00:27:32.510 --> 00:27:32.520 align:start position:0% the way Geth is right now 00:27:32.520 --> 00:27:34.250 align:start position:0% the way Geth is right now yeah<00:27:32.820> and<00:27:32.940> I<00:27:33.120> guess<00:27:33.240> just<00:27:33.419> one<00:27:33.659> final<00:27:33.960> thought 00:27:34.250 --> 00:27:34.260 align:start position:0% yeah and I guess just one final thought 00:27:34.260 --> 00:27:35.750 align:start position:0% yeah and I guess just one final thought there 00:27:35.750 --> 00:27:35.760 align:start position:0% there 00:27:35.760 --> 00:27:38.149 align:start position:0% there um<00:27:35.820> Mario<00:27:36.240> said<00:27:36.659> that<00:27:36.900> uh<00:27:37.320> if<00:27:37.799> we<00:27:37.860> Implement 00:27:38.149 --> 00:27:38.159 align:start position:0% um Mario said that uh if we Implement 00:27:38.159 --> 00:27:39.409 align:start position:0% um Mario said that uh if we Implement The<00:27:38.279> Purge<00:27:38.580> and<00:27:38.700> get<00:27:38.820> rid<00:27:38.940> of<00:27:39.059> a<00:27:39.179> lot<00:27:39.299> of 00:27:39.409 --> 00:27:39.419 align:start position:0% The Purge and get rid of a lot of 00:27:39.419 --> 00:27:40.970 align:start position:0% The Purge and get rid of a lot of features<00:27:39.720> then<00:27:40.080> that<00:27:40.320> would<00:27:40.500> really<00:27:40.679> help 00:27:40.970 --> 00:27:40.980 align:start position:0% features then that would really help 00:27:40.980 --> 00:27:44.149 align:start position:0% features then that would really help other<00:27:41.520> clients<00:27:41.940> get<00:27:42.120> up<00:27:42.240> to<00:27:42.419> speed<00:27:42.659> I<00:27:43.559> think<00:27:43.679> if 00:27:44.149 --> 00:27:44.159 align:start position:0% other clients get up to speed I think if 00:27:44.159 --> 00:27:46.490 align:start position:0% other clients get up to speed I think if we<00:27:44.279> So<00:27:45.000> currently<00:27:45.299> it's<00:27:45.779> very<00:27:45.960> very<00:27:46.140> hard<00:27:46.320> to 00:27:46.490 --> 00:27:46.500 align:start position:0% we So currently it's very very hard to 00:27:46.500 --> 00:27:48.289 align:start position:0% we So currently it's very very hard to write<00:27:46.620> a<00:27:46.799> client<00:27:47.100> and 00:27:48.289 --> 00:27:48.299 align:start position:0% write a client and 00:27:48.299 --> 00:27:50.149 align:start position:0% write a client and starting<00:27:48.900> a<00:27:49.200> new<00:27:49.320> client<00:27:49.559> is<00:27:49.799> essentially 00:27:50.149 --> 00:27:50.159 align:start position:0% starting a new client is essentially 00:27:50.159 --> 00:27:52.610 align:start position:0% starting a new client is essentially impossible<00:27:50.580> because<00:27:50.940> ethereum<00:27:51.900> is<00:27:52.080> moving<00:27:52.380> so 00:27:52.610 --> 00:27:52.620 align:start position:0% impossible because ethereum is moving so 00:27:52.620 --> 00:27:55.909 align:start position:0% impossible because ethereum is moving so fast<00:27:52.860> that<00:27:53.220> you<00:27:53.400> you<00:27:53.640> never<00:27:53.880> catch<00:27:54.299> up<00:27:54.360> but<00:27:55.320> I 00:27:55.909 --> 00:27:55.919 align:start position:0% fast that you you never catch up but I 00:27:55.919 --> 00:27:58.130 align:start position:0% fast that you you never catch up but I guess<00:27:56.039> once<00:27:56.340> we<00:27:56.460> reach<00:27:56.700> the<00:27:56.880> point<00:27:57.120> when<00:27:57.539> uh 00:27:58.130 --> 00:27:58.140 align:start position:0% guess once we reach the point when uh 00:27:58.140 --> 00:28:00.830 align:start position:0% guess once we reach the point when uh when<00:27:58.620> ethereum<00:27:58.980> starts<00:27:59.340> to<00:27:59.400> ossify<00:28:00.000> that 00:28:00.830 --> 00:28:00.840 align:start position:0% when ethereum starts to ossify that 00:28:00.840 --> 00:28:02.750 align:start position:0% when ethereum starts to ossify that would<00:28:00.960> be<00:28:01.140> a<00:28:01.320> nice<00:28:01.440> place<00:28:01.679> when<00:28:02.039> actually<00:28:02.340> new 00:28:02.750 --> 00:28:02.760 align:start position:0% would be a nice place when actually new 00:28:02.760 --> 00:28:05.090 align:start position:0% would be a nice place when actually new client<00:28:03.059> developers<00:28:03.659> can<00:28:04.020> join<00:28:04.799> in<00:28:04.919> because 00:28:05.090 --> 00:28:05.100 align:start position:0% client developers can join in because 00:28:05.100 --> 00:28:06.710 align:start position:0% client developers can join in because then<00:28:05.400> you<00:28:05.580> can<00:28:05.700> actually<00:28:05.820> say<00:28:06.120> that<00:28:06.299> well<00:28:06.480> I 00:28:06.710 --> 00:28:06.720 align:start position:0% then you can actually say that well I 00:28:06.720 --> 00:28:08.930 align:start position:0% then you can actually say that well I want<00:28:06.840> to<00:28:06.960> make<00:28:07.080> a<00:28:07.320> client<00:28:07.620> just<00:28:08.400> specifically 00:28:08.930 --> 00:28:08.940 align:start position:0% want to make a client just specifically 00:28:08.940 --> 00:28:11.149 align:start position:0% want to make a client just specifically for<00:28:09.360> iOS<00:28:09.720> that<00:28:10.200> has<00:28:10.320> this<00:28:10.500> and<00:28:10.679> this<00:28:10.799> and<00:28:10.919> these 00:28:11.149 --> 00:28:11.159 align:start position:0% for iOS that has this and this and these 00:28:11.159 --> 00:28:13.370 align:start position:0% for iOS that has this and this and these properties<00:28:11.460> and<00:28:12.299> they<00:28:12.539> can<00:28:12.659> work<00:28:12.840> on<00:28:13.020> it<00:28:13.140> for 00:28:13.370 --> 00:28:13.380 align:start position:0% properties and they can work on it for 00:28:13.380 --> 00:28:14.570 align:start position:0% properties and they can work on it for three<00:28:13.500> years<00:28:13.679> without<00:28:13.980> the<00:28:14.279> protocol 00:28:14.570 --> 00:28:14.580 align:start position:0% three years without the protocol 00:28:14.580 --> 00:28:17.450 align:start position:0% three years without the protocol constantly<00:28:15.360> changing<00:28:15.900> the<00:28:16.080> invariance<00:28:16.559> and<00:28:17.279> I 00:28:17.450 --> 00:28:17.460 align:start position:0% constantly changing the invariance and I 00:28:17.460 --> 00:28:19.430 align:start position:0% constantly changing the invariance and I think<00:28:17.640> my<00:28:18.179> expectation<00:28:18.600> will<00:28:18.840> be<00:28:19.020> that<00:28:19.260> when 00:28:19.430 --> 00:28:19.440 align:start position:0% think my expectation will be that when 00:28:19.440 --> 00:28:22.250 align:start position:0% think my expectation will be that when we<00:28:19.620> reach<00:28:19.980> that<00:28:20.220> point<00:28:20.460> of<00:28:20.640> stability<00:28:21.140> we<00:28:22.140> will 00:28:22.250 --> 00:28:22.260 align:start position:0% we reach that point of stability we will 00:28:22.260 --> 00:28:25.430 align:start position:0% we reach that point of stability we will have<00:28:22.500> the<00:28:22.740> original<00:28:22.860> clients<00:28:24.020> be<00:28:25.020> quite 00:28:25.430 --> 00:28:25.440 align:start position:0% have the original clients be quite 00:28:25.440 --> 00:28:28.370 align:start position:0% have the original clients be quite marginalized<00:28:26.340> by<00:28:27.059> new<00:28:27.539> clients<00:28:27.960> that<00:28:28.200> are 00:28:28.370 --> 00:28:28.380 align:start position:0% marginalized by new clients that are 00:28:28.380 --> 00:28:31.430 align:start position:0% marginalized by new clients that are very<00:28:28.500> very<00:28:28.679> focused<00:28:29.159> to<00:28:29.400> some<00:28:29.760> specific<00:28:30.179> sub 00:28:31.430 --> 00:28:31.440 align:start position:0% very very focused to some specific sub 00:28:31.440 --> 00:28:35.510 align:start position:0% very very focused to some specific sub task<00:28:32.100> or<00:28:32.640> sub<00:28:32.940> some<00:28:33.900> use<00:28:34.260> case<00:28:34.500> thanks<00:28:35.340> again 00:28:35.510 --> 00:28:35.520 align:start position:0% task or sub some use case thanks again 00:28:35.520 --> 00:28:38.630 align:start position:0% task or sub some use case thanks again for<00:28:36.120> caring<00:28:36.779> so<00:28:37.320> much<00:28:37.500> of<00:28:37.679> the<00:28:37.919> ethereum 00:28:38.630 --> 00:28:38.640 align:start position:0% for caring so much of the ethereum 00:28:38.640 --> 00:28:41.269 align:start position:0% for caring so much of the ethereum ecosystem<00:28:38.940> on<00:28:39.240> your<00:28:39.360> shoulders<00:28:40.140> what<00:28:40.799> is<00:28:40.980> the 00:28:41.269 --> 00:28:41.279 align:start position:0% ecosystem on your shoulders what is the 00:28:41.279 --> 00:28:43.870 align:start position:0% ecosystem on your shoulders what is the current<00:28:41.520> yeah<00:28:42.320> sustainable<00:28:43.320> business<00:28:43.559> model 00:28:43.870 --> 00:28:43.880 align:start position:0% current yeah sustainable business model 00:28:43.880 --> 00:28:47.810 align:start position:0% current yeah sustainable business model for<00:28:44.880> get<00:28:45.179> and<00:28:45.600> probably<00:28:45.779> other<00:28:46.279> clients<00:28:47.279> that 00:28:47.810 --> 00:28:47.820 align:start position:0% for get and probably other clients that 00:28:47.820 --> 00:28:50.149 align:start position:0% for get and probably other clients that want<00:28:48.179> to<00:28:48.299> copy<00:28:48.600> that<00:28:48.779> and<00:28:49.740> the<00:28:49.860> follow-up 00:28:50.149 --> 00:28:50.159 align:start position:0% want to copy that and the follow-up 00:28:50.159 --> 00:28:52.370 align:start position:0% want to copy that and the follow-up question<00:28:50.400> is<00:28:50.580> what<00:28:51.360> is<00:28:51.539> the<00:28:51.659> plan<00:28:51.840> to<00:28:52.080> do 00:28:52.370 --> 00:28:52.380 align:start position:0% question is what is the plan to do 00:28:52.380 --> 00:28:54.590 align:start position:0% question is what is the plan to do something<00:28:52.679> similar<00:28:53.220> to<00:28:53.340> what's<00:28:53.760> been<00:28:54.419> done 00:28:54.590 --> 00:28:54.600 align:start position:0% something similar to what's been done 00:28:54.600 --> 00:28:56.450 align:start position:0% something similar to what's been done for<00:28:54.840> the<00:28:55.020> core<00:28:55.200> protocol<00:28:55.559> right<00:28:55.860> we<00:28:56.100> want<00:28:56.220> a 00:28:56.450 --> 00:28:56.460 align:start position:0% for the core protocol right we want a 00:28:56.460 --> 00:28:59.630 align:start position:0% for the core protocol right we want a certain<00:28:56.640> percentage<00:28:57.240> of<00:28:57.380> of<00:28:58.380> it<00:28:58.740> to<00:28:58.980> be<00:28:59.100> staked 00:28:59.630 --> 00:28:59.640 align:start position:0% certain percentage of of it to be staked 00:28:59.640 --> 00:29:02.510 align:start position:0% certain percentage of of it to be staked as<00:29:00.120> a<00:29:00.299> security 00:29:02.510 --> 00:29:02.520 align:start position:0% 00:29:02.520 --> 00:29:05.269 align:start position:0% um a<00:29:02.880> percentage<00:29:03.419> of<00:29:03.600> the<00:29:03.720> total<00:29:04.080> value<00:29:04.260> right 00:29:05.269 --> 00:29:05.279 align:start position:0% um a percentage of the total value right 00:29:05.279 --> 00:29:07.490 align:start position:0% um a percentage of the total value right so<00:29:05.820> is<00:29:05.940> there<00:29:06.179> some<00:29:06.659> sort<00:29:06.840> of<00:29:07.020> research<00:29:07.260> going 00:29:07.490 --> 00:29:07.500 align:start position:0% so is there some sort of research going 00:29:07.500 --> 00:29:09.769 align:start position:0% so is there some sort of research going on<00:29:07.679> on<00:29:07.919> how<00:29:08.520> do<00:29:08.640> we<00:29:08.760> get<00:29:08.940> certain<00:29:09.360> percentage 00:29:09.769 --> 00:29:09.779 align:start position:0% on on how do we get certain percentage 00:29:09.779 --> 00:29:11.510 align:start position:0% on on how do we get certain percentage of<00:29:09.960> the<00:29:10.140> development<00:29:10.500> effort<00:29:10.919> in<00:29:11.400> the 00:29:11.510 --> 00:29:11.520 align:start position:0% of the development effort in the 00:29:11.520 --> 00:29:15.289 align:start position:0% of the development effort in the ethereum<00:29:11.820> ecosystem<00:29:12.440> to<00:29:13.440> be<00:29:13.760> going<00:29:14.760> towards 00:29:15.289 --> 00:29:15.299 align:start position:0% ethereum ecosystem to be going towards 00:29:15.299 --> 00:29:17.390 align:start position:0% ethereum ecosystem to be going towards get<00:29:16.140> security 00:29:17.390 --> 00:29:17.400 align:start position:0% get security 00:29:17.400 --> 00:29:20.750 align:start position:0% get security well<00:29:18.059> to<00:29:18.539> answer<00:29:18.720> your<00:29:18.960> first<00:29:19.140> question<00:29:19.500> uh<00:29:20.460> it 00:29:20.750 --> 00:29:20.760 align:start position:0% well to answer your first question uh it 00:29:20.760 --> 00:29:22.430 align:start position:0% well to answer your first question uh it absolutely<00:29:21.059> makes<00:29:21.360> no<00:29:21.600> sense<00:29:21.720> to<00:29:22.020> write<00:29:22.200> a 00:29:22.430 --> 00:29:22.440 align:start position:0% absolutely makes no sense to write a 00:29:22.440 --> 00:29:24.769 align:start position:0% absolutely makes no sense to write a client<00:29:22.620> because<00:29:23.279> I<00:29:23.520> think<00:29:23.700> it's<00:29:23.940> a<00:29:24.179> there's<00:29:24.600> no 00:29:24.769 --> 00:29:24.779 align:start position:0% client because I think it's a there's no 00:29:24.779 --> 00:29:27.010 align:start position:0% client because I think it's a there's no business<00:29:24.899> model<00:29:25.260> behind<00:29:25.679> it 00:29:27.010 --> 00:29:27.020 align:start position:0% business model behind it 00:29:27.020 --> 00:29:29.870 align:start position:0% business model behind it it's<00:29:28.020> currently<00:29:28.440> most<00:29:28.799> of<00:29:28.919> the<00:29:29.100> clients<00:29:29.460> are 00:29:29.870 --> 00:29:29.880 align:start position:0% it's currently most of the clients are 00:29:29.880 --> 00:29:32.149 align:start position:0% it's currently most of the clients are funded<00:29:30.419> by<00:29:30.720> I<00:29:30.960> mean<00:29:31.080> we<00:29:31.260> are<00:29:31.440> fully<00:29:31.799> funded<00:29:32.039> by 00:29:32.149 --> 00:29:32.159 align:start position:0% funded by I mean we are fully funded by 00:29:32.159 --> 00:29:35.269 align:start position:0% funded by I mean we are fully funded by the<00:29:32.340> EF<00:29:32.640> we<00:29:33.240> have<00:29:33.360> absolutely<00:29:33.899> no 00:29:35.269 --> 00:29:35.279 align:start position:0% the EF we have absolutely no 00:29:35.279 --> 00:29:38.090 align:start position:0% the EF we have absolutely no income<00:29:36.120> I'm<00:29:37.020> assuming<00:29:37.500> other<00:29:37.740> clients 00:29:38.090 --> 00:29:38.100 align:start position:0% income I'm assuming other clients 00:29:38.100 --> 00:29:40.669 align:start position:0% income I'm assuming other clients usually<00:29:38.399> how<00:29:38.760> they<00:29:39.059> try<00:29:39.360> to<00:29:39.539> fund<00:29:40.380> themselves 00:29:40.669 --> 00:29:40.679 align:start position:0% usually how they try to fund themselves 00:29:40.679 --> 00:29:42.289 align:start position:0% usually how they try to fund themselves is<00:29:41.159> that 00:29:42.289 --> 00:29:42.299 align:start position:0% is that 00:29:42.299 --> 00:29:44.330 align:start position:0% is that many<00:29:42.840> clients<00:29:43.200> get<00:29:43.380> grants<00:29:43.740> from<00:29:44.039> other 00:29:44.330 --> 00:29:44.340 align:start position:0% many clients get grants from other 00:29:44.340 --> 00:29:46.549 align:start position:0% many clients get grants from other projects<00:29:44.820> so<00:29:45.179> that<00:29:45.360> they<00:29:45.539> support<00:29:45.779> different 00:29:46.549 --> 00:29:46.559 align:start position:0% projects so that they support different 00:29:46.559 --> 00:29:48.830 align:start position:0% projects so that they support different blockchains<00:29:47.279> different<00:29:47.460> layer<00:29:47.880> tools 00:29:48.830 --> 00:29:48.840 align:start position:0% blockchains different layer tools 00:29:48.840 --> 00:29:51.649 align:start position:0% blockchains different layer tools different<00:29:49.380> scaling<00:29:50.039> Solutions<00:29:50.480> that's<00:29:51.480> one 00:29:51.649 --> 00:29:51.659 align:start position:0% different scaling Solutions that's one 00:29:51.659 --> 00:29:53.330 align:start position:0% different scaling Solutions that's one way<00:29:51.840> to<00:29:52.080> somehow<00:29:52.380> try<00:29:52.679> to<00:29:52.860> build<00:29:52.980> a<00:29:53.220> business 00:29:53.330 --> 00:29:53.340 align:start position:0% way to somehow try to build a business 00:29:53.340 --> 00:29:56.570 align:start position:0% way to somehow try to build a business model<00:29:53.640> around<00:29:53.940> it<00:29:54.179> but<00:29:55.159> at<00:29:56.159> the<00:29:56.279> end<00:29:56.340> of<00:29:56.460> the 00:29:56.570 --> 00:29:56.580 align:start position:0% model around it but at the end of the 00:29:56.580 --> 00:29:58.070 align:start position:0% model around it but at the end of the day 00:29:58.070 --> 00:29:58.080 align:start position:0% day 00:29:58.080 --> 00:29:59.510 align:start position:0% day since<00:29:58.380> ethereum<00:29:58.860> is<00:29:58.980> kind<00:29:59.100> of<00:29:59.220> like<00:29:59.340> this 00:29:59.510 --> 00:29:59.520 align:start position:0% since ethereum is kind of like this 00:29:59.520 --> 00:30:01.430 align:start position:0% since ethereum is kind of like this public<00:29:59.700> platform 00:30:01.430 --> 00:30:01.440 align:start position:0% public platform 00:30:01.440 --> 00:30:03.769 align:start position:0% public platform a<00:30:01.919> client<00:30:02.279> as<00:30:02.700> a<00:30:02.880> client<00:30:03.000> you<00:30:03.240> cannot<00:30:03.539> really 00:30:03.769 --> 00:30:03.779 align:start position:0% a client as a client you cannot really 00:30:03.779 --> 00:30:08.330 align:start position:0% a client as a client you cannot really make<00:30:04.440> money<00:30:04.799> out<00:30:05.159> of<00:30:05.279> it<00:30:05.460> it's<00:30:06.179> a 00:30:08.330 --> 00:30:08.340 align:start position:0% make money out of it it's a 00:30:08.340 --> 00:30:10.190 align:start position:0% make money out of it it's a yeah<00:30:08.880> so<00:30:09.120> that<00:30:09.299> there's<00:30:09.600> no<00:30:09.720> business<00:30:09.899> model 00:30:10.190 --> 00:30:10.200 align:start position:0% yeah so that there's no business model 00:30:10.200 --> 00:30:14.090 align:start position:0% yeah so that there's no business model behind<00:30:10.740> uh<00:30:11.419> creating<00:30:12.419> the<00:30:12.659> client<00:30:12.899> itself<00:30:13.260> the 00:30:14.090 --> 00:30:14.100 align:start position:0% behind uh creating the client itself the 00:30:14.100 --> 00:30:16.669 align:start position:0% behind uh creating the client itself the only<00:30:14.220> thing<00:30:14.399> that<00:30:14.580> I<00:30:14.820> would<00:30:14.940> say<00:30:15.120> is<00:30:15.360> that<00:30:16.080> uh 00:30:16.669 --> 00:30:16.679 align:start position:0% only thing that I would say is that uh 00:30:16.679 --> 00:30:19.070 align:start position:0% only thing that I would say is that uh there's<00:30:16.980> the<00:30:17.220> the<00:30:17.460> Proto<00:30:18.059> what<00:30:18.539> what's<00:30:18.840> the 00:30:19.070 --> 00:30:19.080 align:start position:0% there's the the Proto what what's the 00:30:19.080 --> 00:30:23.450 align:start position:0% there's the the Proto what what's the protocol<00:30:19.580> protocol<00:30:20.580> Guild<00:30:21.120> yeah<00:30:21.779> exactly 00:30:23.450 --> 00:30:23.460 align:start position:0% protocol protocol Guild yeah exactly 00:30:23.460 --> 00:30:27.049 align:start position:0% protocol protocol Guild yeah exactly um<00:30:23.659> that<00:30:24.659> allows<00:30:25.200> projects<00:30:26.100> for<00:30:26.460> example<00:30:26.700> D5 00:30:27.049 --> 00:30:27.059 align:start position:0% um that allows projects for example D5 00:30:27.059 --> 00:30:31.250 align:start position:0% um that allows projects for example D5 projects<00:30:27.720> to<00:30:28.620> allocate<00:30:29.360> a<00:30:30.360> percentage<00:30:31.020> of 00:30:31.250 --> 00:30:31.260 align:start position:0% projects to allocate a percentage of 00:30:31.260 --> 00:30:35.510 align:start position:0% projects to allocate a percentage of their<00:30:31.440> token<00:30:31.860> distribution<00:30:32.779> uh<00:30:33.779> to<00:30:34.320> a<00:30:34.679> pot<00:30:34.980> and 00:30:35.510 --> 00:30:35.520 align:start position:0% their token distribution uh to a pot and 00:30:35.520 --> 00:30:38.269 align:start position:0% their token distribution uh to a pot and out<00:30:35.700> of<00:30:35.820> this<00:30:36.000> pot<00:30:36.299> uh<00:30:37.080> client<00:30:37.500> teams<00:30:37.980> get 00:30:38.269 --> 00:30:38.279 align:start position:0% out of this pot uh client teams get 00:30:38.279 --> 00:30:41.450 align:start position:0% out of this pot uh client teams get right<00:30:39.000> now<00:30:39.179> they<00:30:39.600> get<00:30:39.779> bonuses 00:30:41.450 --> 00:30:41.460 align:start position:0% right now they get bonuses 00:30:41.460 --> 00:30:42.049 align:start position:0% right now they get bonuses um 00:30:42.049 --> 00:30:42.059 align:start position:0% um 00:30:42.059 --> 00:30:45.110 align:start position:0% um uh<00:30:42.960> and<00:30:43.260> this<00:30:43.500> is<00:30:43.620> the<00:30:44.220> the<00:30:44.460> general<00:30:44.700> idea 00:30:45.110 --> 00:30:45.120 align:start position:0% uh and this is the the general idea 00:30:45.120 --> 00:30:47.389 align:start position:0% uh and this is the the general idea behind<00:30:45.480> it<00:30:45.600> was<00:30:45.840> not<00:30:46.200> to<00:30:46.500> fully<00:30:46.860> fund<00:30:47.100> client 00:30:47.389 --> 00:30:47.399 align:start position:0% behind it was not to fully fund client 00:30:47.399 --> 00:30:50.269 align:start position:0% behind it was not to fully fund client teams<00:30:47.820> but<00:30:48.419> to<00:30:48.600> provide<00:30:48.960> an<00:30:49.200> upside<00:30:49.500> that<00:30:49.980> they 00:30:50.269 --> 00:30:50.279 align:start position:0% teams but to provide an upside that they 00:30:50.279 --> 00:30:53.990 align:start position:0% teams but to provide an upside that they wouldn't<00:30:50.580> have<00:30:51.000> if<00:30:51.899> at<00:30:52.340> that<00:30:53.340> they<00:30:53.580> currently 00:30:53.990 --> 00:30:54.000 align:start position:0% wouldn't have if at that they currently 00:30:54.000 --> 00:30:55.850 align:start position:0% wouldn't have if at that they currently don't<00:30:54.179> have<00:30:54.419> and<00:30:54.779> that<00:30:54.960> they<00:30:55.200> would<00:30:55.380> have<00:30:55.500> if 00:30:55.850 --> 00:30:55.860 align:start position:0% don't have and that they would have if 00:30:55.860 --> 00:30:58.430 align:start position:0% don't have and that they would have if they<00:30:56.039> were<00:30:56.220> to<00:30:56.399> switch<00:30:56.580> to<00:30:56.820> be<00:30:57.059> uh<00:30:57.480> to<00:30:57.720> to<00:30:57.899> defy 00:30:58.430 --> 00:30:58.440 align:start position:0% they were to switch to be uh to to defy 00:30:58.440 --> 00:31:01.370 align:start position:0% they were to switch to be uh to to defy uh<00:30:59.159> because<00:30:59.340> we've<00:30:59.640> seen<00:30:59.880> a<00:31:00.059> lot<00:31:00.179> of<00:31:00.360> uh<00:31:01.020> good 00:31:01.370 --> 00:31:01.380 align:start position:0% uh because we've seen a lot of uh good 00:31:01.380 --> 00:31:04.430 align:start position:0% uh because we've seen a lot of uh good client<00:31:01.860> developers<00:31:02.460> uh<00:31:03.419> just<00:31:03.600> say<00:31:03.779> okay<00:31:03.960> I<00:31:04.260> can 00:31:04.430 --> 00:31:04.440 align:start position:0% client developers uh just say okay I can 00:31:04.440 --> 00:31:07.669 align:start position:0% client developers uh just say okay I can make<00:31:04.799> 10<00:31:05.460> times<00:31:05.700> the<00:31:06.059> the<00:31:06.299> money<00:31:06.659> if<00:31:06.960> I<00:31:07.080> if<00:31:07.440> I 00:31:07.669 --> 00:31:07.679 align:start position:0% make 10 times the the money if I if I 00:31:07.679 --> 00:31:10.010 align:start position:0% make 10 times the the money if I if I create<00:31:07.919> the<00:31:08.159> next<00:31:08.340> token 00:31:10.010 --> 00:31:10.020 align:start position:0% create the next token 00:31:10.020 --> 00:31:11.810 align:start position:0% create the next token um and<00:31:10.620> so 00:31:11.810 --> 00:31:11.820 align:start position:0% um and so 00:31:11.820 --> 00:31:15.070 align:start position:0% um and so the<00:31:12.600> protocol<00:31:12.960> support<00:31:13.320> a<00:31:13.799> protocol<00:31:14.279> Guild 00:31:15.070 --> 00:31:15.080 align:start position:0% the protocol support a protocol Guild 00:31:15.080 --> 00:31:19.909 align:start position:0% the protocol support a protocol Guild thingy<00:31:16.080> is<00:31:16.980> like<00:31:17.520> a<00:31:17.760> way<00:31:17.940> to<00:31:18.899> give<00:31:19.200> some<00:31:19.559> some 00:31:19.909 --> 00:31:19.919 align:start position:0% thingy is like a way to give some some 00:31:19.919 --> 00:31:22.730 align:start position:0% thingy is like a way to give some some of<00:31:20.399> that<00:31:20.580> upside<00:31:21.000> from<00:31:21.779> the<00:31:21.899> default<00:31:22.260> projects 00:31:22.730 --> 00:31:22.740 align:start position:0% of that upside from the default projects 00:31:22.740 --> 00:31:25.370 align:start position:0% of that upside from the default projects yeah<00:31:23.279> appreciate<00:31:23.820> like<00:31:24.299> I<00:31:24.840> was<00:31:24.899> wondering<00:31:25.140> if 00:31:25.370 --> 00:31:25.380 align:start position:0% yeah appreciate like I was wondering if 00:31:25.380 --> 00:31:26.930 align:start position:0% yeah appreciate like I was wondering if you<00:31:25.620> can<00:31:25.799> start<00:31:26.039> experimenting<00:31:26.580> with<00:31:26.700> things 00:31:26.930 --> 00:31:26.940 align:start position:0% you can start experimenting with things 00:31:26.940 --> 00:31:30.169 align:start position:0% you can start experimenting with things like<00:31:27.240> maybe<00:31:27.720> Kodak<00:31:28.380> funding<00:31:28.860> towards<00:31:29.460> PRS 00:31:30.169 --> 00:31:30.179 align:start position:0% like maybe Kodak funding towards PRS 00:31:30.179 --> 00:31:31.970 align:start position:0% like maybe Kodak funding towards PRS right<00:31:30.899> there's<00:31:31.080> you<00:31:31.380> said<00:31:31.500> there's<00:31:31.740> a<00:31:31.860> big 00:31:31.970 --> 00:31:31.980 align:start position:0% right there's you said there's a big 00:31:31.980 --> 00:31:33.590 align:start position:0% right there's you said there's a big backlog<00:31:32.399> of<00:31:32.520> PRS 00:31:33.590 --> 00:31:33.600 align:start position:0% backlog of PRS 00:31:33.600 --> 00:31:35.149 align:start position:0% backlog of PRS and<00:31:34.140> only<00:31:34.320> a<00:31:34.440> couple<00:31:34.559> of<00:31:34.679> people<00:31:34.799> that<00:31:35.039> are 00:31:35.149 --> 00:31:35.159 align:start position:0% and only a couple of people that are 00:31:35.159 --> 00:31:37.549 align:start position:0% and only a couple of people that are capable<00:31:35.520> of<00:31:35.700> reviewing<00:31:36.419> but<00:31:37.140> you<00:31:37.320> could 00:31:37.549 --> 00:31:37.559 align:start position:0% capable of reviewing but you could 00:31:37.559 --> 00:31:38.930 align:start position:0% capable of reviewing but you could imagine<00:31:37.799> that<00:31:38.220> with<00:31:38.460> some<00:31:38.640> sort<00:31:38.880> of 00:31:38.930 --> 00:31:38.940 align:start position:0% imagine that with some sort of 00:31:38.940 --> 00:31:42.169 align:start position:0% imagine that with some sort of codewriting<00:31:39.539> funding<00:31:39.960> you<00:31:40.919> can't<00:31:41.100> hire<00:31:41.460> or<00:31:42.059> at 00:31:42.169 --> 00:31:42.179 align:start position:0% codewriting funding you can't hire or at 00:31:42.179 --> 00:31:43.850 align:start position:0% codewriting funding you can't hire or at least<00:31:42.299> bounties<00:31:42.899> for<00:31:43.140> other<00:31:43.380> people<00:31:43.620> to 00:31:43.850 --> 00:31:43.860 align:start position:0% least bounties for other people to 00:31:43.860 --> 00:31:45.830 align:start position:0% least bounties for other people to layers<00:31:44.520> of<00:31:44.640> developers<00:31:45.000> to<00:31:45.179> review<00:31:45.360> and<00:31:45.659> write 00:31:45.830 --> 00:31:45.840 align:start position:0% layers of developers to review and write 00:31:45.840 --> 00:31:47.930 align:start position:0% layers of developers to review and write tests<00:31:46.260> and<00:31:46.380> integration<00:31:46.740> your<00:31:47.039> tests<00:31:47.399> before 00:31:47.930 --> 00:31:47.940 align:start position:0% tests and integration your tests before 00:31:47.940 --> 00:31:51.230 align:start position:0% tests and integration your tests before it<00:31:48.299> gets<00:31:48.539> to<00:31:48.720> core<00:31:49.260> developer 00:31:51.230 --> 00:31:51.240 align:start position:0% it gets to core developer 00:31:51.240 --> 00:31:54.110 align:start position:0% it gets to core developer so<00:31:51.659> I<00:31:51.899> guess<00:31:52.279> this<00:31:53.279> depends<00:31:53.640> on<00:31:53.880> the 00:31:54.110 --> 00:31:54.120 align:start position:0% so I guess this depends on the 00:31:54.120 --> 00:31:57.230 align:start position:0% so I guess this depends on the granularity<00:31:54.720> generally<00:31:55.320> people<00:31:55.860> do<00:31:56.700> do<00:31:57.000> that 00:31:57.230 --> 00:31:57.240 align:start position:0% granularity generally people do do that 00:31:57.240 --> 00:32:01.669 align:start position:0% granularity generally people do do that at<00:31:57.659> the<00:31:57.779> EIP<00:31:58.020> level<00:31:58.700> so<00:31:59.700> famously<00:32:00.539> uni<00:32:01.020> swap<00:32:01.320> is 00:32:01.669 --> 00:32:01.679 align:start position:0% at the EIP level so famously uni swap is 00:32:01.679 --> 00:32:03.889 align:start position:0% at the EIP level so famously uni swap is pushing<00:32:02.159> certain<00:32:02.399> eip's<00:32:03.120> very<00:32:03.240> very<00:32:03.419> hard<00:32:03.600> and 00:32:03.889 --> 00:32:03.899 align:start position:0% pushing certain eip's very very hard and 00:32:03.899 --> 00:32:05.450 align:start position:0% pushing certain eip's very very hard and I'm<00:32:04.080> assuming<00:32:04.440> they<00:32:04.740> are<00:32:04.860> actually<00:32:05.039> funding 00:32:05.450 --> 00:32:05.460 align:start position:0% I'm assuming they are actually funding 00:32:05.460 --> 00:32:07.490 align:start position:0% I'm assuming they are actually funding the<00:32:05.580> people<00:32:05.820> who<00:32:06.240> are<00:32:06.419> doing<00:32:06.960> the<00:32:07.200> necessary 00:32:07.490 --> 00:32:07.500 align:start position:0% the people who are doing the necessary 00:32:07.500 --> 00:32:09.529 align:start position:0% the people who are doing the necessary research<00:32:08.039> doing<00:32:08.279> necessary 00:32:09.529 --> 00:32:09.539 align:start position:0% research doing necessary 00:32:09.539 --> 00:32:12.230 align:start position:0% research doing necessary presentation<00:32:10.559> etc<00:32:10.980> etc<00:32:11.100> to 00:32:12.230 --> 00:32:12.240 align:start position:0% presentation etc etc to 00:32:12.240 --> 00:32:15.470 align:start position:0% presentation etc etc to get<00:32:12.659> an<00:32:12.840> EIP<00:32:13.140> through<00:32:13.640> now<00:32:14.640> that<00:32:15.120> I<00:32:15.360> don't 00:32:15.470 --> 00:32:15.480 align:start position:0% get an EIP through now that I don't 00:32:15.480 --> 00:32:17.990 align:start position:0% get an EIP through now that I don't think<00:32:15.600> that<00:32:15.840> really<00:32:16.020> works<00:32:16.500> at<00:32:16.860> the<00:32:17.220> client 00:32:17.990 --> 00:32:18.000 align:start position:0% think that really works at the client 00:32:18.000 --> 00:32:20.630 align:start position:0% think that really works at the client level<00:32:18.179> because 00:32:20.630 --> 00:32:20.640 align:start position:0% level because 00:32:20.640 --> 00:32:22.549 align:start position:0% level because we've<00:32:21.179> tried<00:32:21.360> for<00:32:21.600> example<00:32:21.779> at<00:32:22.020> some<00:32:22.140> point<00:32:22.260> we 00:32:22.549 --> 00:32:22.559 align:start position:0% we've tried for example at some point we 00:32:22.559 --> 00:32:25.730 align:start position:0% we've tried for example at some point we gave<00:32:23.100> out<00:32:23.279> a<00:32:23.520> couple<00:32:23.580> bounties<00:32:24.059> for<00:32:24.360> some<00:32:24.539> work 00:32:25.730 --> 00:32:25.740 align:start position:0% gave out a couple bounties for some work 00:32:25.740 --> 00:32:28.370 align:start position:0% gave out a couple bounties for some work the<00:32:26.399> the<00:32:26.580> place<00:32:27.240> where<00:32:27.419> it<00:32:27.539> kind<00:32:27.659> of<00:32:27.779> backfires 00:32:28.370 --> 00:32:28.380 align:start position:0% the the place where it kind of backfires 00:32:28.380 --> 00:32:30.830 align:start position:0% the the place where it kind of backfires is<00:32:28.740> twofold<00:32:29.279> one<00:32:29.640> of<00:32:29.760> them<00:32:29.820> is<00:32:30.059> that<00:32:30.419> you 00:32:30.830 --> 00:32:30.840 align:start position:0% is twofold one of them is that you 00:32:30.840 --> 00:32:33.289 align:start position:0% is twofold one of them is that you usually<00:32:31.200> get<00:32:31.380> contributions<00:32:32.039> of<00:32:32.580> not<00:32:33.059> the 00:32:33.289 --> 00:32:33.299 align:start position:0% usually get contributions of not the 00:32:33.299 --> 00:32:35.690 align:start position:0% usually get contributions of not the greatest<00:32:33.480> quality<00:32:34.080> because<00:32:34.740> a<00:32:35.100> lot<00:32:35.460> of<00:32:35.640> people 00:32:35.690 --> 00:32:35.700 align:start position:0% greatest quality because a lot of people 00:32:35.700 --> 00:32:37.970 align:start position:0% greatest quality because a lot of people see<00:32:35.940> that<00:32:36.120> oh<00:32:36.299> there's<00:32:36.659> a<00:32:36.960> I<00:32:37.620> don't<00:32:37.740> know<00:32:37.799> one 00:32:37.970 --> 00:32:37.980 align:start position:0% see that oh there's a I don't know one 00:32:37.980 --> 00:32:39.710 align:start position:0% see that oh there's a I don't know one ether<00:32:38.279> bounty<00:32:38.760> on<00:32:38.880> this<00:32:39.000> so<00:32:39.179> let's<00:32:39.299> just<00:32:39.480> jump 00:32:39.710 --> 00:32:39.720 align:start position:0% ether bounty on this so let's just jump 00:32:39.720 --> 00:32:41.510 align:start position:0% ether bounty on this so let's just jump on<00:32:39.899> it<00:32:40.080> so<00:32:40.679> you<00:32:40.799> will<00:32:40.919> have<00:32:41.100> 10<00:32:41.279> different 00:32:41.510 --> 00:32:41.520 align:start position:0% on it so you will have 10 different 00:32:41.520 --> 00:32:43.549 align:start position:0% on it so you will have 10 different implementations<00:32:42.299> all<00:32:42.720> just<00:32:43.020> kind<00:32:43.200> of<00:32:43.320> trying 00:32:43.549 --> 00:32:43.559 align:start position:0% implementations all just kind of trying 00:32:43.559 --> 00:32:45.710 align:start position:0% implementations all just kind of trying to<00:32:43.799> hack<00:32:43.980> it<00:32:44.159> as<00:32:44.340> fast<00:32:44.460> as<00:32:44.640> you<00:32:44.820> they<00:32:45.179> can<00:32:45.419> to 00:32:45.710 --> 00:32:45.720 align:start position:0% to hack it as fast as you they can to 00:32:45.720 --> 00:32:47.450 align:start position:0% to hack it as fast as you they can to get<00:32:46.020> the<00:32:46.200> bounty 00:32:47.450 --> 00:32:47.460 align:start position:0% get the bounty 00:32:47.460 --> 00:32:50.330 align:start position:0% get the bounty so<00:32:48.000> the<00:32:48.179> code<00:32:48.360> is<00:32:48.720> not<00:32:49.320> the<00:32:49.559> best<00:32:49.740> it<00:32:50.039> requires 00:32:50.330 --> 00:32:50.340 align:start position:0% so the code is not the best it requires 00:32:50.340 --> 00:32:52.250 align:start position:0% so the code is not the best it requires a<00:32:50.460> lot<00:32:50.580> of<00:32:50.640> effort<00:32:50.940> from<00:32:51.179> our<00:32:51.360> site<00:32:51.600> to<00:32:51.899> somehow 00:32:52.250 --> 00:32:52.260 align:start position:0% a lot of effort from our site to somehow 00:32:52.260 --> 00:32:54.590 align:start position:0% a lot of effort from our site to somehow try<00:32:52.860> to<00:32:52.980> fix<00:32:53.159> it<00:32:53.340> up<00:32:53.520> or<00:32:53.700> try<00:32:53.880> to<00:32:54.000> try<00:32:54.299> to<00:32:54.419> guide 00:32:54.590 --> 00:32:54.600 align:start position:0% try to fix it up or try to try to guide 00:32:54.600 --> 00:32:56.990 align:start position:0% try to fix it up or try to try to guide that<00:32:54.960> person<00:32:55.220> and<00:32:56.220> the<00:32:56.340> other<00:32:56.399> side<00:32:56.640> is<00:32:56.820> that 00:32:56.990 --> 00:32:57.000 align:start position:0% that person and the other side is that 00:32:57.000 --> 00:32:58.669 align:start position:0% that person and the other side is that after<00:32:57.179> the<00:32:57.419> bounty<00:32:57.720> has<00:32:57.899> been<00:32:58.020> paid<00:32:58.200> out<00:32:58.380> since 00:32:58.669 --> 00:32:58.679 align:start position:0% after the bounty has been paid out since 00:32:58.679 --> 00:33:00.529 align:start position:0% after the bounty has been paid out since this<00:32:58.919> was<00:32:59.100> a<00:32:59.279> bounty<00:32:59.700> work<00:32:59.880> they<00:33:00.299> just 00:33:00.529 --> 00:33:00.539 align:start position:0% this was a bounty work they just 00:33:00.539 --> 00:33:03.470 align:start position:0% this was a bounty work they just disappear<00:33:00.960> and<00:33:01.260> maintenance<00:33:01.740> is<00:33:02.100> our<00:33:02.399> problem 00:33:03.470 --> 00:33:03.480 align:start position:0% disappear and maintenance is our problem 00:33:03.480 --> 00:33:05.930 align:start position:0% disappear and maintenance is our problem so<00:33:03.960> we<00:33:04.260> kind<00:33:04.440> of<00:33:04.559> have<00:33:04.860> more<00:33:05.159> problems<00:33:05.640> than 00:33:05.930 --> 00:33:05.940 align:start position:0% so we kind of have more problems than 00:33:05.940 --> 00:33:08.269 align:start position:0% so we kind of have more problems than gains<00:33:06.480> with<00:33:06.779> uh 00:33:08.269 --> 00:33:08.279 align:start position:0% gains with uh 00:33:08.279 --> 00:33:10.730 align:start position:0% gains with uh funding<00:33:08.820> PRS<00:33:09.419> at<00:33:09.779> that<00:33:09.960> level 00:33:10.730 --> 00:33:10.740 align:start position:0% funding PRS at that level 00:33:10.740 --> 00:33:14.509 align:start position:0% funding PRS at that level the<00:33:11.220> what<00:33:11.520> we<00:33:11.700> have<00:33:11.940> done<00:33:12.559> previously<00:33:13.559> is<00:33:14.220> we 00:33:14.509 --> 00:33:14.519 align:start position:0% the what we have done previously is we 00:33:14.519 --> 00:33:16.850 align:start position:0% the what we have done previously is we have<00:33:14.640> funded<00:33:15.179> the<00:33:15.539> research<00:33:16.260> teams<00:33:16.620> for 00:33:16.850 --> 00:33:16.860 align:start position:0% have funded the research teams for 00:33:16.860 --> 00:33:19.430 align:start position:0% have funded the research teams for example<00:33:17.100> to<00:33:17.640> who<00:33:18.299> have<00:33:18.480> helped<00:33:18.840> us<00:33:18.960> on<00:33:19.260> the 00:33:19.430 --> 00:33:19.440 align:start position:0% example to who have helped us on the 00:33:19.440 --> 00:33:22.130 align:start position:0% example to who have helped us on the Discovery<00:33:19.980> protocol<00:33:20.340> the<00:33:20.700> Discovery<00:33:21.179> V5 00:33:22.130 --> 00:33:22.140 align:start position:0% Discovery protocol the Discovery V5 00:33:22.140 --> 00:33:26.090 align:start position:0% Discovery protocol the Discovery V5 we<00:33:22.620> I<00:33:22.919> think<00:33:23.240> Felix<00:33:24.240> was<00:33:24.419> managing<00:33:24.960> a<00:33:25.500> small 00:33:26.090 --> 00:33:26.100 align:start position:0% we I think Felix was managing a small 00:33:26.100 --> 00:33:27.950 align:start position:0% we I think Felix was managing a small research<00:33:26.519> team<00:33:26.760> at<00:33:27.000> I'm<00:33:27.360> not<00:33:27.539> entirely<00:33:27.840> sure 00:33:27.950 --> 00:33:27.960 align:start position:0% research team at I'm not entirely sure 00:33:27.960 --> 00:33:30.710 align:start position:0% research team at I'm not entirely sure which<00:33:28.200> university<00:33:28.580> and<00:33:29.580> the<00:33:29.760> EF<00:33:30.240> was<00:33:30.419> funding 00:33:30.710 --> 00:33:30.720 align:start position:0% which university and the EF was funding 00:33:30.720 --> 00:33:32.269 align:start position:0% which university and the EF was funding them<00:33:30.840> for<00:33:31.140> a<00:33:31.260> year<00:33:31.380> or<00:33:31.559> so<00:33:31.740> to<00:33:32.100> just 00:33:32.269 --> 00:33:32.279 align:start position:0% them for a year or so to just 00:33:32.279 --> 00:33:35.450 align:start position:0% them for a year or so to just investigate<00:33:33.059> find<00:33:33.899> possible<00:33:34.860> solutions<00:33:35.279> to 00:33:35.450 --> 00:33:35.460 align:start position:0% investigate find possible solutions to 00:33:35.460 --> 00:33:37.250 align:start position:0% investigate find possible solutions to different<00:33:35.700> challenges<00:33:36.299> write<00:33:36.659> some<00:33:36.899> papers 00:33:37.250 --> 00:33:37.260 align:start position:0% different challenges write some papers 00:33:37.260 --> 00:33:40.250 align:start position:0% different challenges write some papers that<00:33:37.919> one<00:33:38.100> works<00:33:38.940> so<00:33:39.419> that<00:33:39.600> definitely<00:33:39.899> works 00:33:40.250 --> 00:33:40.260 align:start position:0% that one works so that definitely works 00:33:40.260 --> 00:33:42.529 align:start position:0% that one works so that definitely works but<00:33:40.440> at<00:33:40.679> the<00:33:40.799> client<00:33:40.980> level<00:33:41.220> I<00:33:41.519> feel<00:33:41.700> it's<00:33:42.539> um 00:33:42.529 --> 00:33:42.539 align:start position:0% but at the client level I feel it's um 00:33:42.539 --> 00:33:44.990 align:start position:0% but at the client level I feel it's um it's<00:33:43.200> the<00:33:43.380> wrong<00:33:43.500> granularity<00:33:44.159> I<00:33:44.580> just<00:33:44.880> wanted 00:33:44.990 --> 00:33:45.000 align:start position:0% it's the wrong granularity I just wanted 00:33:45.000 --> 00:33:47.990 align:start position:0% it's the wrong granularity I just wanted to<00:33:45.240> say<00:33:45.419> to<00:33:46.019> the<00:33:46.140> original<00:33:46.260> question<00:33:46.740> of<00:33:47.340> like 00:33:47.990 --> 00:33:48.000 align:start position:0% to say to the original question of like 00:33:48.000 --> 00:33:50.149 align:start position:0% to say to the original question of like how<00:33:48.899> what<00:33:49.140> is<00:33:49.320> the<00:33:49.440> business<00:33:49.620> model<00:33:49.860> for 00:33:50.149 --> 00:33:50.159 align:start position:0% how what is the business model for 00:33:50.159 --> 00:33:52.250 align:start position:0% how what is the business model for clients<00:33:50.519> I<00:33:50.640> agree<00:33:50.940> like<00:33:51.179> no<00:33:51.720> there's<00:33:52.019> no 00:33:52.250 --> 00:33:52.260 align:start position:0% clients I agree like no there's no 00:33:52.260 --> 00:33:54.710 align:start position:0% clients I agree like no there's no reason<00:33:52.440> to<00:33:52.740> build<00:33:52.919> the<00:33:53.100> client<00:33:53.340> there's<00:33:53.580> not<00:33:53.940> a 00:33:54.710 --> 00:33:54.720 align:start position:0% reason to build the client there's not a 00:33:54.720 --> 00:33:56.630 align:start position:0% reason to build the client there's not a lot<00:33:54.779> of<00:33:54.960> money<00:33:55.140> in<00:33:55.440> doing<00:33:55.679> this<00:33:55.919> it's<00:33:56.399> always 00:33:56.630 --> 00:33:56.640 align:start position:0% lot of money in doing this it's always 00:33:56.640 --> 00:33:57.830 align:start position:0% lot of money in doing this it's always going<00:33:56.940> to<00:33:57.000> be<00:33:57.059> like<00:33:57.179> considered<00:33:57.600> a<00:33:57.659> public 00:33:57.830 --> 00:33:57.840 align:start position:0% going to be like considered a public 00:33:57.840 --> 00:33:59.630 align:start position:0% going to be like considered a public good<00:33:58.019> but<00:33:58.260> I<00:33:58.380> think<00:33:58.500> one<00:33:58.740> way<00:33:58.980> of<00:33:59.159> making<00:33:59.399> it 00:33:59.630 --> 00:33:59.640 align:start position:0% good but I think one way of making it 00:33:59.640 --> 00:34:01.370 align:start position:0% good but I think one way of making it sustainable<00:34:00.059> as<00:34:00.299> like<00:34:00.360> Maria<00:34:00.539> said<00:34:00.960> this 00:34:01.370 --> 00:34:01.380 align:start position:0% sustainable as like Maria said this 00:34:01.380 --> 00:34:03.649 align:start position:0% sustainable as like Maria said this protocol<00:34:01.679> Guild<00:34:02.039> project<00:34:02.399> in<00:34:03.179> a<00:34:03.299> way<00:34:03.419> that 00:34:03.649 --> 00:34:03.659 align:start position:0% protocol Guild project in a way that 00:34:03.659 --> 00:34:05.690 align:start position:0% protocol Guild project in a way that people<00:34:03.840> can<00:34:04.080> like<00:34:04.320> help<00:34:04.620> make<00:34:05.460> this 00:34:05.690 --> 00:34:05.700 align:start position:0% people can like help make this 00:34:05.700 --> 00:34:07.250 align:start position:0% people can like help make this sustainable<00:34:06.179> for<00:34:06.419> the<00:34:06.539> long<00:34:06.720> term<00:34:06.899> is 00:34:07.250 --> 00:34:07.260 align:start position:0% sustainable for the long term is 00:34:07.260 --> 00:34:09.349 align:start position:0% sustainable for the long term is whenever<00:34:07.980> you're<00:34:08.220> developing<00:34:08.700> new<00:34:08.940> projects 00:34:09.349 --> 00:34:09.359 align:start position:0% whenever you're developing new projects 00:34:09.359 --> 00:34:11.629 align:start position:0% whenever you're developing new projects to<00:34:09.599> consider<00:34:09.960> adding<00:34:10.500> a<00:34:10.800> small<00:34:10.919> allocation<00:34:11.399> to 00:34:11.629 --> 00:34:11.639 align:start position:0% to consider adding a small allocation to 00:34:11.639 --> 00:34:14.149 align:start position:0% to consider adding a small allocation to the<00:34:11.760> protocol<00:34:12.000> Guild<00:34:12.619> in<00:34:13.619> your<00:34:13.740> initial<00:34:13.980> like 00:34:14.149 --> 00:34:14.159 align:start position:0% the protocol Guild in your initial like 00:34:14.159 --> 00:34:16.430 align:start position:0% the protocol Guild in your initial like token<00:34:14.639> launch<00:34:15.119> if<00:34:15.599> some<00:34:15.780> of<00:34:15.899> these<00:34:16.020> are<00:34:16.200> if 00:34:16.430 --> 00:34:16.440 align:start position:0% token launch if some of these are if 00:34:16.440 --> 00:34:17.690 align:start position:0% token launch if some of these are if this<00:34:16.859> would<00:34:16.919> have<00:34:17.040> been<00:34:17.159> something<00:34:17.339> that<00:34:17.520> was 00:34:17.690 --> 00:34:17.700 align:start position:0% this would have been something that was 00:34:17.700 --> 00:34:20.210 align:start position:0% this would have been something that was around<00:34:18.060> in<00:34:18.540> 2018<00:34:18.659> or<00:34:19.200> 2019<00:34:19.619> when<00:34:19.919> a<00:34:20.099> lot<00:34:20.159> of 00:34:20.210 --> 00:34:20.220 align:start position:0% around in 2018 or 2019 when a lot of 00:34:20.220 --> 00:34:20.930 align:start position:0% around in 2018 or 2019 when a lot of these 00:34:20.930 --> 00:34:20.940 align:start position:0% these 00:34:20.940 --> 00:34:23.690 align:start position:0% these Blue<00:34:21.599> Chip<00:34:21.839> D5<00:34:22.200> protocols<00:34:22.679> we're<00:34:22.800> starting<00:34:23.040> we 00:34:23.690 --> 00:34:23.700 align:start position:0% Blue Chip D5 protocols we're starting we 00:34:23.700 --> 00:34:25.430 align:start position:0% Blue Chip D5 protocols we're starting we would<00:34:23.879> have<00:34:24.119> over<00:34:24.480> 100<00:34:24.659> million<00:34:25.139> dollars 00:34:25.430 --> 00:34:25.440 align:start position:0% would have over 100 million dollars 00:34:25.440 --> 00:34:28.190 align:start position:0% would have over 100 million dollars dedicated<00:34:26.099> just<00:34:26.460> to<00:34:26.639> core<00:34:26.820> development<00:34:27.359> and 00:34:28.190 --> 00:34:28.200 align:start position:0% dedicated just to core development and 00:34:28.200 --> 00:34:29.629 align:start position:0% dedicated just to core development and so<00:34:28.320> I<00:34:28.619> think<00:34:28.679> like<00:34:28.859> going<00:34:29.040> forward<00:34:29.280> it's<00:34:29.520> like 00:34:29.629 --> 00:34:29.639 align:start position:0% so I think like going forward it's like 00:34:29.639 --> 00:34:31.669 align:start position:0% so I think like going forward it's like a<00:34:29.760> good<00:34:29.879> thing<00:34:30.000> to<00:34:30.179> consider<00:34:30.480> because<00:34:31.080> you 00:34:31.669 --> 00:34:31.679 align:start position:0% a good thing to consider because you 00:34:31.679 --> 00:34:33.290 align:start position:0% a good thing to consider because you want<00:34:31.800> ethereum<00:34:32.220> to<00:34:32.460> be<00:34:32.520> around<00:34:32.700> for<00:34:33.060> a<00:34:33.179> long 00:34:33.290 --> 00:34:33.300 align:start position:0% want ethereum to be around for a long 00:34:33.300 --> 00:34:34.669 align:start position:0% want ethereum to be around for a long period<00:34:33.540> of<00:34:33.599> time<00:34:33.720> and<00:34:34.020> the<00:34:34.200> best<00:34:34.260> way<00:34:34.440> to<00:34:34.560> do 00:34:34.669 --> 00:34:34.679 align:start position:0% period of time and the best way to do 00:34:34.679 --> 00:34:36.109 align:start position:0% period of time and the best way to do that<00:34:34.740> is<00:34:34.919> to<00:34:35.099> make<00:34:35.220> sure<00:34:35.339> that<00:34:35.580> the<00:34:35.700> people<00:34:35.820> who 00:34:36.109 --> 00:34:36.119 align:start position:0% that is to make sure that the people who 00:34:36.119 --> 00:34:38.329 align:start position:0% that is to make sure that the people who are<00:34:36.240> making<00:34:36.780> it<00:34:37.020> happen<00:34:37.139> continue<00:34:37.500> having<00:34:37.919> the 00:34:38.329 --> 00:34:38.339 align:start position:0% are making it happen continue having the 00:34:38.339 --> 00:34:40.669 align:start position:0% are making it happen continue having the funding<00:34:38.580> that<00:34:38.700> they<00:34:38.879> need<00:34:39.000> to<00:34:39.119> do<00:34:39.300> it 00:34:40.669 --> 00:34:40.679 align:start position:0% funding that they need to do it 00:34:40.679 --> 00:34:43.510 align:start position:0% funding that they need to do it yeah<00:34:41.040> and<00:34:41.339> uh<00:34:41.760> adding<00:34:42.419> to<00:34:42.540> this 00:34:43.510 --> 00:34:43.520 align:start position:0% yeah and uh adding to this 00:34:43.520 --> 00:34:46.909 align:start position:0% yeah and uh adding to this we<00:34:44.520> not<00:34:44.879> only<00:34:45.060> do<00:34:45.419> is<00:34:46.379> there<00:34:46.500> no<00:34:46.740> business 00:34:46.909 --> 00:34:46.919 align:start position:0% we not only do is there no business 00:34:46.919 --> 00:34:49.129 align:start position:0% we not only do is there no business model<00:34:47.280> for<00:34:47.700> a<00:34:47.879> client<00:34:48.240> but<00:34:48.599> I<00:34:48.899> don't<00:34:49.020> think 00:34:49.129 --> 00:34:49.139 align:start position:0% model for a client but I don't think 00:34:49.139 --> 00:34:50.629 align:start position:0% model for a client but I don't think there<00:34:49.320> should<00:34:49.560> be<00:34:49.679> because<00:34:49.919> otherwise<00:34:50.399> you 00:34:50.629 --> 00:34:50.639 align:start position:0% there should be because otherwise you 00:34:50.639 --> 00:34:54.710 align:start position:0% there should be because otherwise you would<00:34:50.940> kind<00:34:51.480> of<00:34:51.599> adapt<00:34:52.020> your<00:34:53.179> strategy<00:34:54.179> to 00:34:54.710 --> 00:34:54.720 align:start position:0% would kind of adapt your strategy to 00:34:54.720 --> 00:34:58.070 align:start position:0% would kind of adapt your strategy to increasing<00:34:55.260> their<00:34:55.440> revenue<00:34:55.740> stream<00:34:56.180> and<00:34:57.180> you 00:34:58.070 --> 00:34:58.080 align:start position:0% increasing their revenue stream and you 00:34:58.080 --> 00:35:00.050 align:start position:0% increasing their revenue stream and you lose<00:34:58.200> your<00:34:58.380> Independence<00:34:58.859> basically 00:35:00.050 --> 00:35:00.060 align:start position:0% lose your Independence basically 00:35:00.060 --> 00:35:03.050 align:start position:0% lose your Independence basically my<00:35:00.540> question<00:35:00.720> is<00:35:01.080> related<00:35:01.680> but<00:35:02.040> with<00:35:02.700> what 00:35:03.050 --> 00:35:03.060 align:start position:0% my question is related but with what 00:35:03.060 --> 00:35:05.570 align:start position:0% my question is related but with what Marius<00:35:03.480> just<00:35:03.839> said<00:35:04.020> and<00:35:04.740> well<00:35:04.920> I'm<00:35:05.160> still<00:35:05.400> a 00:35:05.570 --> 00:35:05.580 align:start position:0% Marius just said and well I'm still a 00:35:05.580 --> 00:35:07.310 align:start position:0% Marius just said and well I'm still a student<00:35:05.700> and<00:35:06.359> I'm<00:35:06.540> still<00:35:06.780> trying<00:35:06.960> to<00:35:07.140> figure 00:35:07.310 --> 00:35:07.320 align:start position:0% student and I'm still trying to figure 00:35:07.320 --> 00:35:10.010 align:start position:0% student and I'm still trying to figure out<00:35:07.680> what<00:35:08.280> I<00:35:08.520> want<00:35:08.640> to<00:35:08.760> work<00:35:09.000> on<00:35:09.240> after<00:35:09.720> I 00:35:10.010 --> 00:35:10.020 align:start position:0% out what I want to work on after I 00:35:10.020 --> 00:35:13.069 align:start position:0% out what I want to work on after I graduate<00:35:10.440> I<00:35:11.040> see<00:35:11.220> their<00:35:11.700> stuff<00:35:12.180> that<00:35:12.599> you<00:35:12.960> guys 00:35:13.069 --> 00:35:13.079 align:start position:0% graduate I see their stuff that you guys 00:35:13.079 --> 00:35:16.130 align:start position:0% graduate I see their stuff that you guys do<00:35:13.320> and<00:35:13.619> I<00:35:13.859> think<00:35:14.040> it's<00:35:14.280> amazing<00:35:14.940> and<00:35:15.660> I<00:35:15.960> still 00:35:16.130 --> 00:35:16.140 align:start position:0% do and I think it's amazing and I still 00:35:16.140 --> 00:35:18.230 align:start position:0% do and I think it's amazing and I still see<00:35:16.320> something<00:35:16.680> bar<00:35:16.980> on<00:35:17.400> the<00:35:17.640> application 00:35:18.230 --> 00:35:18.240 align:start position:0% see something bar on the application 00:35:18.240 --> 00:35:20.329 align:start position:0% see something bar on the application side<00:35:18.480> of<00:35:18.720> things<00:35:18.900> so<00:35:19.560> my<00:35:19.800> question<00:35:19.920> is<00:35:20.160> really 00:35:20.329 --> 00:35:20.339 align:start position:0% side of things so my question is really 00:35:20.339 --> 00:35:22.849 align:start position:0% side of things so my question is really why<00:35:21.180> did<00:35:21.300> you<00:35:21.420> decide<00:35:21.720> to<00:35:21.900> go<00:35:22.140> to<00:35:22.680> core 00:35:22.849 --> 00:35:22.859 align:start position:0% why did you decide to go to core 00:35:22.859 --> 00:35:24.650 align:start position:0% why did you decide to go to core development<00:35:23.460> and<00:35:23.940> stay<00:35:24.240> in<00:35:24.480> court 00:35:24.650 --> 00:35:24.660 align:start position:0% development and stay in court 00:35:24.660 --> 00:35:26.329 align:start position:0% development and stay in court development<00:35:25.200> instead<00:35:25.800> of<00:35:25.859> going<00:35:26.040> to 00:35:26.329 --> 00:35:26.339 align:start position:0% development instead of going to 00:35:26.339 --> 00:35:29.510 align:start position:0% development instead of going to something<00:35:26.839> higher<00:35:27.839> in<00:35:28.079> this<00:35:28.320> in<00:35:28.859> the<00:35:29.040> stack 00:35:29.510 --> 00:35:29.520 align:start position:0% something higher in this in the stack 00:35:29.520 --> 00:35:31.790 align:start position:0% something higher in this in the stack because<00:35:30.060> it's<00:35:30.420> way<00:35:30.660> more<00:35:30.839> fun<00:35:31.079> and<00:35:31.380> way<00:35:31.619> more 00:35:31.790 --> 00:35:31.800 align:start position:0% because it's way more fun and way more 00:35:31.800 --> 00:35:36.530 align:start position:0% because it's way more fun and way more interesting<00:35:32.599> and<00:35:33.740> so<00:35:34.740> for<00:35:34.920> me<00:35:35.099> the<00:35:36.060> the<00:35:36.300> big 00:35:36.530 --> 00:35:36.540 align:start position:0% interesting and so for me the the big 00:35:36.540 --> 00:35:38.329 align:start position:0% interesting and so for me the the big thing<00:35:36.780> is<00:35:36.900> also<00:35:37.260> I<00:35:37.500> want<00:35:37.680> to<00:35:37.800> work<00:35:38.099> on 00:35:38.329 --> 00:35:38.339 align:start position:0% thing is also I want to work on 00:35:38.339 --> 00:35:40.370 align:start position:0% thing is also I want to work on something 00:35:40.370 --> 00:35:40.380 align:start position:0% something 00:35:40.380 --> 00:35:42.890 align:start position:0% something um that<00:35:40.920> makes<00:35:41.099> sense<00:35:41.460> to<00:35:41.880> me<00:35:42.060> where<00:35:42.540> I<00:35:42.720> have 00:35:42.890 --> 00:35:42.900 align:start position:0% um that makes sense to me where I have 00:35:42.900 --> 00:35:45.530 align:start position:0% um that makes sense to me where I have the<00:35:43.079> the<00:35:43.500> the<00:35:43.619> the<00:35:43.859> the<00:35:44.060> feeling<00:35:45.060> that<00:35:45.359> I'm 00:35:45.530 --> 00:35:45.540 align:start position:0% the the the the the feeling that I'm 00:35:45.540 --> 00:35:46.910 align:start position:0% the the the the the feeling that I'm doing<00:35:45.780> something 00:35:46.910 --> 00:35:46.920 align:start position:0% doing something 00:35:46.920 --> 00:35:51.170 align:start position:0% doing something good<00:35:47.820> for<00:35:48.240> the<00:35:48.480> creator<00:35:48.780> of<00:35:49.020> humanity<00:35:49.820> and<00:35:50.820> uh 00:35:51.170 --> 00:35:51.180 align:start position:0% good for the creator of humanity and uh 00:35:51.180 --> 00:35:53.450 align:start position:0% good for the creator of humanity and uh I<00:35:51.420> don't<00:35:51.480> think<00:35:51.599> diva<00:35:52.200> is<00:35:52.320> a<00:35:52.920> lot<00:35:53.220> of<00:35:53.339> the 00:35:53.450 --> 00:35:53.460 align:start position:0% I don't think diva is a lot of the 00:35:53.460 --> 00:35:58.310 align:start position:0% I don't think diva is a lot of the defense<00:35:53.880> stuff<00:35:54.119> is<00:35:54.300> is<00:35:54.839> uh<00:35:55.760> is<00:35:56.760> this<00:35:57.000> and<00:35:57.839> so 00:35:58.310 --> 00:35:58.320 align:start position:0% defense stuff is is uh is this and so 00:35:58.320 --> 00:36:00.829 align:start position:0% defense stuff is is uh is this and so that's<00:35:58.500> why<00:35:58.800> that's<00:35:59.339> why<00:35:59.640> I<00:36:00.000> I<00:36:00.420> was<00:36:00.599> so 00:36:00.829 --> 00:36:00.839 align:start position:0% that's why that's why I I was so 00:36:00.839 --> 00:36:02.810 align:start position:0% that's why that's why I I was so interested<00:36:01.260> in<00:36:01.560> in<00:36:01.740> working<00:36:02.040> on<00:36:02.280> the<00:36:02.400> merch 00:36:02.810 --> 00:36:02.820 align:start position:0% interested in in working on the merch 00:36:02.820 --> 00:36:06.290 align:start position:0% interested in in working on the merch and<00:36:03.000> and<00:36:03.420> helping<00:36:04.079> push<00:36:04.380> push<00:36:04.800> the<00:36:04.980> merge 00:36:06.290 --> 00:36:06.300 align:start position:0% and and helping push push the merge 00:36:06.300 --> 00:36:08.930 align:start position:0% and and helping push push the merge um because<00:36:07.020> I<00:36:07.380> felt<00:36:07.680> like<00:36:07.859> I'm 00:36:08.930 --> 00:36:08.940 align:start position:0% um because I felt like I'm 00:36:08.940 --> 00:36:11.390 align:start position:0% um because I felt like I'm this<00:36:09.599> is<00:36:09.720> like<00:36:09.900> the<00:36:10.200> biggest<00:36:10.320> thing<00:36:10.980> that<00:36:11.280> I'll 00:36:11.390 --> 00:36:11.400 align:start position:0% this is like the biggest thing that I'll 00:36:11.400 --> 00:36:14.690 align:start position:0% this is like the biggest thing that I'll ever<00:36:11.640> be<00:36:11.880> part<00:36:12.119> of<00:36:12.300> uh<00:36:12.900> regarding 00:36:14.690 --> 00:36:14.700 align:start position:0% ever be part of uh regarding 00:36:14.700 --> 00:36:15.650 align:start position:0% ever be part of uh regarding um 00:36:15.650 --> 00:36:15.660 align:start position:0% um 00:36:15.660 --> 00:36:20.089 align:start position:0% um like<00:36:16.380> the<00:36:16.760> CO2<00:36:17.760> consumption<00:36:18.240> and<00:36:18.420> everything 00:36:20.089 --> 00:36:20.099 align:start position:0% like the CO2 consumption and everything 00:36:20.099 --> 00:36:24.170 align:start position:0% like the CO2 consumption and everything um<00:36:20.160> and<00:36:21.060> so<00:36:21.420> just<00:36:21.720> having<00:36:21.960> this<00:36:22.500> big 00:36:24.170 --> 00:36:24.180 align:start position:0% um and so just having this big 00:36:24.180 --> 00:36:29.270 align:start position:0% um and so just having this big level<00:36:25.040> of<00:36:26.040> like<00:36:26.400> my<00:36:26.760> work<00:36:27.000> can<00:36:27.480> my 00:36:29.270 --> 00:36:29.280 align:start position:0% level of like my work can my 00:36:29.280 --> 00:36:31.670 align:start position:0% level of like my work can my small<00:36:29.880> work<00:36:30.119> can<00:36:30.480> have<00:36:30.720> a<00:36:30.960> really<00:36:31.079> big<00:36:31.260> impact 00:36:31.670 --> 00:36:31.680 align:start position:0% small work can have a really big impact 00:36:31.680 --> 00:36:33.890 align:start position:0% small work can have a really big impact that<00:36:32.220> was<00:36:32.400> something<00:36:32.640> that<00:36:33.000> was<00:36:33.180> pretty 00:36:33.890 --> 00:36:33.900 align:start position:0% that was something that was pretty 00:36:33.900 --> 00:36:37.010 align:start position:0% that was something that was pretty magical<00:36:34.260> from<00:36:34.619> the<00:36:34.800> beginning<00:36:35.359> and<00:36:36.359> uh<00:36:36.839> yeah 00:36:37.010 --> 00:36:37.020 align:start position:0% magical from the beginning and uh yeah 00:36:37.020 --> 00:36:39.170 align:start position:0% magical from the beginning and uh yeah that's<00:36:37.320> that's<00:36:37.619> that's<00:36:37.680> why<00:36:38.280> I<00:36:38.460> am<00:36:38.640> in<00:36:38.760> core 00:36:39.170 --> 00:36:39.180 align:start position:0% that's that's that's why I am in core 00:36:39.180 --> 00:36:41.870 align:start position:0% that's that's that's why I am in core development<00:36:39.599> I<00:36:39.900> don't<00:36:40.020> know<00:36:40.140> about<00:36:40.260> you<00:36:40.560> guys 00:36:41.870 --> 00:36:41.880 align:start position:0% development I don't know about you guys 00:36:41.880 --> 00:36:44.630 align:start position:0% development I don't know about you guys it's<00:36:42.420> it's<00:36:42.480> not<00:36:42.839> the<00:36:43.079> money<00:36:43.260> I<00:36:44.220> mean<00:36:44.339> I<00:36:44.460> would 00:36:44.630 --> 00:36:44.640 align:start position:0% it's it's not the money I mean I would 00:36:44.640 --> 00:36:47.089 align:start position:0% it's it's not the money I mean I would so<00:36:45.599> my<00:36:45.960> answer<00:36:46.140> is<00:36:46.380> kind<00:36:46.560> of<00:36:46.680> boring<00:36:46.920> because 00:36:47.089 --> 00:36:47.099 align:start position:0% so my answer is kind of boring because 00:36:47.099 --> 00:36:49.190 align:start position:0% so my answer is kind of boring because there<00:36:47.339> was<00:36:47.520> nothing<00:36:47.700> when<00:36:48.060> I<00:36:48.300> started<00:36:48.780> working 00:36:49.190 --> 00:36:49.200 align:start position:0% there was nothing when I started working 00:36:49.200 --> 00:36:51.589 align:start position:0% there was nothing when I started working at<00:36:49.440> ethereum<00:36:49.859> so<00:36:50.160> I<00:36:50.880> think<00:36:51.000> Matt's<00:36:51.480> answer 00:36:51.589 --> 00:36:51.599 align:start position:0% at ethereum so I think Matt's answer 00:36:51.599 --> 00:36:52.970 align:start position:0% at ethereum so I think Matt's answer would<00:36:51.839> be<00:36:51.960> much<00:36:52.140> much<00:36:52.380> more<00:36:52.619> interesting 00:36:52.970 --> 00:36:52.980 align:start position:0% would be much much more interesting 00:36:52.980 --> 00:36:55.730 align:start position:0% would be much much more interesting since<00:36:53.220> he<00:36:53.460> did<00:36:53.700> have<00:36:53.880> the<00:36:54.119> choice<00:36:54.300> of 00:36:55.730 --> 00:36:55.740 align:start position:0% since he did have the choice of 00:36:55.740 --> 00:36:58.190 align:start position:0% since he did have the choice of picking<00:36:56.400> one<00:36:56.579> or<00:36:56.700> the<00:36:56.880> other<00:36:57.000> picking<00:36:57.900> one<00:36:58.079> or 00:36:58.190 --> 00:36:58.200 align:start position:0% picking one or the other picking one or 00:36:58.200 --> 00:37:00.349 align:start position:0% picking one or the other picking one or the<00:36:58.320> other<00:36:58.440> isn't<00:36:58.920> I<00:36:59.520> mean<00:36:59.640> working<00:37:00.119> on 00:37:00.349 --> 00:37:00.359 align:start position:0% the other isn't I mean working on 00:37:00.359 --> 00:37:03.290 align:start position:0% the other isn't I mean working on protocol<00:37:00.960> versus<00:37:01.260> working<00:37:01.680> on<00:37:02.099> that<00:37:02.940> player 00:37:03.290 --> 00:37:03.300 align:start position:0% protocol versus working on that player 00:37:03.300 --> 00:37:06.170 align:start position:0% protocol versus working on that player stuff<00:37:03.540> right<00:37:03.839> I<00:37:04.560> mean<00:37:04.680> you<00:37:05.099> know<00:37:05.220> I<00:37:05.880> originally 00:37:06.170 --> 00:37:06.180 align:start position:0% stuff right I mean you know I originally 00:37:06.180 --> 00:37:08.210 align:start position:0% stuff right I mean you know I originally started<00:37:06.480> working<00:37:06.660> on<00:37:06.960> the<00:37:07.079> top<00:37:07.260> layer<00:37:07.680> like 00:37:08.210 --> 00:37:08.220 align:start position:0% started working on the top layer like 00:37:08.220 --> 00:37:10.910 align:start position:0% started working on the top layer like when<00:37:08.760> I<00:37:08.880> came<00:37:09.180> out<00:37:09.300> of<00:37:09.420> University<00:37:09.660> I<00:37:10.500> was<00:37:10.680> very 00:37:10.910 --> 00:37:10.920 align:start position:0% when I came out of University I was very 00:37:10.920 --> 00:37:14.089 align:start position:0% when I came out of University I was very interested<00:37:11.400> in<00:37:11.720> how<00:37:12.720> you<00:37:13.560> know<00:37:13.680> the<00:37:13.800> types<00:37:14.040> of 00:37:14.089 --> 00:37:14.099 align:start position:0% interested in how you know the types of 00:37:14.099 --> 00:37:15.290 align:start position:0% interested in how you know the types of applications<00:37:14.460> that<00:37:14.700> you<00:37:14.820> could<00:37:14.940> build<00:37:15.119> on 00:37:15.290 --> 00:37:15.300 align:start position:0% applications that you could build on 00:37:15.300 --> 00:37:16.910 align:start position:0% applications that you could build on ethereum<00:37:15.780> and<00:37:16.200> I<00:37:16.260> was<00:37:16.440> very<00:37:16.560> interested<00:37:16.859> in 00:37:16.910 --> 00:37:16.920 align:start position:0% ethereum and I was very interested in 00:37:16.920 --> 00:37:18.410 align:start position:0% ethereum and I was very interested in like<00:37:17.040> dispute<00:37:17.400> resolution<00:37:17.820> because<00:37:18.119> I<00:37:18.300> had 00:37:18.410 --> 00:37:18.420 align:start position:0% like dispute resolution because I had 00:37:18.420 --> 00:37:20.569 align:start position:0% like dispute resolution because I had done<00:37:18.599> a<00:37:18.780> lot<00:37:18.839> of<00:37:18.960> like<00:37:19.260> e-commerce<00:37:19.980> and<00:37:20.220> buying 00:37:20.569 --> 00:37:20.579 align:start position:0% done a lot of like e-commerce and buying 00:37:20.579 --> 00:37:21.609 align:start position:0% done a lot of like e-commerce and buying and<00:37:20.700> selling<00:37:20.940> things<00:37:21.060> on<00:37:21.300> the<00:37:21.420> internet 00:37:21.609 --> 00:37:21.619 align:start position:0% and selling things on the internet 00:37:21.619 --> 00:37:23.870 align:start position:0% and selling things on the internet growing<00:37:22.619> up<00:37:22.740> and<00:37:22.980> I<00:37:23.099> was<00:37:23.339> like<00:37:23.520> frustrated 00:37:23.870 --> 00:37:23.880 align:start position:0% growing up and I was like frustrated 00:37:23.880 --> 00:37:26.089 align:start position:0% growing up and I was like frustrated with<00:37:24.060> the<00:37:24.240> way<00:37:24.359> these<00:37:24.660> systems<00:37:25.079> were<00:37:25.680> built<00:37:25.920> so 00:37:26.089 --> 00:37:26.099 align:start position:0% with the way these systems were built so 00:37:26.099 --> 00:37:28.609 align:start position:0% with the way these systems were built so I<00:37:26.339> was<00:37:26.460> very<00:37:26.640> excited<00:37:27.000> about<00:37:27.119> this<00:37:27.540> as<00:37:28.200> a 00:37:28.609 --> 00:37:28.619 align:start position:0% I was very excited about this as a 00:37:28.619 --> 00:37:30.829 align:start position:0% I was very excited about this as a application<00:37:29.099> on<00:37:29.579> on<00:37:29.760> the<00:37:30.000> protocol<00:37:30.240> so<00:37:30.660> I 00:37:30.829 --> 00:37:30.839 align:start position:0% application on on the protocol so I 00:37:30.839 --> 00:37:32.329 align:start position:0% application on on the protocol so I joined<00:37:31.200> consensus<00:37:31.619> and<00:37:31.800> I<00:37:31.920> was<00:37:31.980> working<00:37:32.160> on 00:37:32.329 --> 00:37:32.339 align:start position:0% joined consensus and I was working on 00:37:32.339 --> 00:37:34.670 align:start position:0% joined consensus and I was working on something<00:37:32.579> pretty<00:37:32.880> similar<00:37:33.180> to<00:37:33.300> this<00:37:33.540> and<00:37:34.500> it 00:37:34.670 --> 00:37:34.680 align:start position:0% something pretty similar to this and it 00:37:34.680 --> 00:37:36.589 align:start position:0% something pretty similar to this and it just<00:37:34.920> immediately<00:37:35.339> realized<00:37:35.760> that 00:37:36.589 --> 00:37:36.599 align:start position:0% just immediately realized that 00:37:36.599 --> 00:37:39.589 align:start position:0% just immediately realized that you<00:37:37.260> know<00:37:37.460> a<00:37:38.460> the<00:37:38.760> user<00:37:39.119> experience<00:37:39.420> for 00:37:39.589 --> 00:37:39.599 align:start position:0% you know a the user experience for 00:37:39.599 --> 00:37:40.849 align:start position:0% you know a the user experience for ethereum<00:37:39.960> at<00:37:40.140> that<00:37:40.260> time<00:37:40.380> and<00:37:40.500> like<00:37:40.619> still 00:37:40.849 --> 00:37:40.859 align:start position:0% ethereum at that time and like still 00:37:40.859 --> 00:37:43.670 align:start position:0% ethereum at that time and like still today<00:37:41.040> was<00:37:41.520> too<00:37:42.119> bad<00:37:42.420> to<00:37:42.839> really<00:37:43.020> on<00:37:43.560> board 00:37:43.670 --> 00:37:43.680 align:start position:0% today was too bad to really on board 00:37:43.680 --> 00:37:46.250 align:start position:0% today was too bad to really on board like<00:37:43.980> hundreds<00:37:44.400> of<00:37:44.460> thousands<00:37:44.760> of<00:37:44.880> users<00:37:45.260> to 00:37:46.250 --> 00:37:46.260 align:start position:0% like hundreds of thousands of users to 00:37:46.260 --> 00:37:48.349 align:start position:0% like hundreds of thousands of users to you<00:37:47.220> know<00:37:47.280> have<00:37:47.640> this<00:37:47.880> kind<00:37:48.000> of<00:37:48.060> dispute 00:37:48.349 --> 00:37:48.359 align:start position:0% you know have this kind of dispute 00:37:48.359 --> 00:37:51.890 align:start position:0% you know have this kind of dispute resolution<00:37:48.780> system<00:37:49.339> and<00:37:50.339> even<00:37:50.940> if<00:37:51.119> 100<00:37:51.720> 000 00:37:51.890 --> 00:37:51.900 align:start position:0% resolution system and even if 100 000 00:37:51.900 --> 00:37:53.870 align:start position:0% resolution system and even if 100 000 users<00:37:52.440> decided<00:37:52.859> to<00:37:52.980> show<00:37:53.099> up<00:37:53.280> tomorrow<00:37:53.579> like 00:37:53.870 --> 00:37:53.880 align:start position:0% users decided to show up tomorrow like 00:37:53.880 --> 00:37:56.450 align:start position:0% users decided to show up tomorrow like we<00:37:54.119> didn't<00:37:54.300> have<00:37:54.599> the<00:37:54.859> scalability<00:37:55.859> to 00:37:56.450 --> 00:37:56.460 align:start position:0% we didn't have the scalability to 00:37:56.460 --> 00:37:58.849 align:start position:0% we didn't have the scalability to support<00:37:56.760> that<00:37:57.060> many<00:37:57.180> users<00:37:57.599> on<00:37:58.440> the<00:37:58.619> protocol 00:37:58.849 --> 00:37:58.859 align:start position:0% support that many users on the protocol 00:37:58.859 --> 00:38:00.589 align:start position:0% support that many users on the protocol and<00:37:59.579> so<00:37:59.700> that<00:37:59.820> was<00:37:59.940> kind<00:38:00.060> of<00:38:00.180> like<00:38:00.240> where<00:38:00.420> I 00:38:00.589 --> 00:38:00.599 align:start position:0% and so that was kind of like where I 00:38:00.599 --> 00:38:01.670 align:start position:0% and so that was kind of like where I started<00:38:00.900> getting<00:38:01.020> really<00:38:01.200> interested<00:38:01.560> in 00:38:01.670 --> 00:38:01.680 align:start position:0% started getting really interested in 00:38:01.680 --> 00:38:02.930 align:start position:0% started getting really interested in protocol<00:38:01.920> development<00:38:02.400> it's<00:38:02.579> like<00:38:02.700> I<00:38:02.820> was 00:38:02.930 --> 00:38:02.940 align:start position:0% protocol development it's like I was 00:38:02.940 --> 00:38:05.270 align:start position:0% protocol development it's like I was like<00:38:03.060> this<00:38:03.540> is<00:38:03.660> broken<00:38:04.079> we<00:38:04.619> need<00:38:04.740> to<00:38:04.800> fix<00:38:04.980> it<00:38:05.099> so 00:38:05.270 --> 00:38:05.280 align:start position:0% like this is broken we need to fix it so 00:38:05.280 --> 00:38:06.829 align:start position:0% like this is broken we need to fix it so that<00:38:05.400> we<00:38:05.520> can<00:38:05.579> build<00:38:05.760> an<00:38:06.000> application<00:38:06.420> on<00:38:06.720> it 00:38:06.829 --> 00:38:06.839 align:start position:0% that we can build an application on it 00:38:06.839 --> 00:38:08.750 align:start position:0% that we can build an application on it and<00:38:07.380> I've<00:38:07.560> just<00:38:07.740> like<00:38:07.920> slowly<00:38:08.280> become<00:38:08.579> more 00:38:08.750 --> 00:38:08.760 align:start position:0% and I've just like slowly become more 00:38:08.760 --> 00:38:11.210 align:start position:0% and I've just like slowly become more and<00:38:08.880> more<00:38:09.060> indoctrinated<00:38:09.660> in<00:38:10.380> the<00:38:10.500> idea<00:38:10.800> and 00:38:11.210 --> 00:38:11.220 align:start position:0% and more indoctrinated in the idea and 00:38:11.220 --> 00:38:13.370 align:start position:0% and more indoctrinated in the idea and now<00:38:11.339> I'm<00:38:11.520> kind<00:38:11.640> of<00:38:11.760> at<00:38:11.880> the<00:38:12.000> point<00:38:12.180> where<00:38:12.599> I 00:38:13.370 --> 00:38:13.380 align:start position:0% now I'm kind of at the point where I 00:38:13.380 --> 00:38:15.230 align:start position:0% now I'm kind of at the point where I feel<00:38:13.500> like<00:38:13.740> I<00:38:14.280> would<00:38:14.339> rather<00:38:14.579> be<00:38:14.880> a<00:38:15.060> small 00:38:15.230 --> 00:38:15.240 align:start position:0% feel like I would rather be a small 00:38:15.240 --> 00:38:17.150 align:start position:0% feel like I would rather be a small piece<00:38:15.599> of<00:38:15.720> a<00:38:15.900> very<00:38:15.960> large<00:38:16.140> puzzle<00:38:16.619> that<00:38:16.859> I<00:38:16.980> feel 00:38:17.150 --> 00:38:17.160 align:start position:0% piece of a very large puzzle that I feel 00:38:17.160 --> 00:38:19.790 align:start position:0% piece of a very large puzzle that I feel is<00:38:17.400> going<00:38:17.640> to<00:38:17.820> become<00:38:18.240> extremely<00:38:18.900> important 00:38:19.790 --> 00:38:19.800 align:start position:0% is going to become extremely important 00:38:19.800 --> 00:38:21.890 align:start position:0% is going to become extremely important and<00:38:19.859> impactful<00:38:20.339> for<00:38:20.640> Humanity<00:38:21.119> rather<00:38:21.780> than 00:38:21.890 --> 00:38:21.900 align:start position:0% and impactful for Humanity rather than 00:38:21.900 --> 00:38:23.569 align:start position:0% and impactful for Humanity rather than trying<00:38:22.140> to<00:38:22.260> build<00:38:22.440> an<00:38:22.619> application<00:38:23.040> that<00:38:23.400> may 00:38:23.569 --> 00:38:23.579 align:start position:0% trying to build an application that may 00:38:23.579 --> 00:38:25.730 align:start position:0% trying to build an application that may or<00:38:23.760> may<00:38:23.940> not<00:38:24.119> have<00:38:24.839> any<00:38:25.020> kind<00:38:25.200> of<00:38:25.260> impact<00:38:25.500> for 00:38:25.730 --> 00:38:25.740 align:start position:0% or may not have any kind of impact for 00:38:25.740 --> 00:38:26.750 align:start position:0% or may not have any kind of impact for anyone 00:38:26.750 --> 00:38:26.760 align:start position:0% anyone 00:38:26.760 --> 00:38:29.030 align:start position:0% anyone uh<00:38:27.420> so<00:38:27.599> I<00:38:27.720> guess<00:38:27.839> your<00:38:28.079> reasoning<00:38:28.560> for<00:38:28.680> joining 00:38:29.030 --> 00:38:29.040 align:start position:0% uh so I guess your reasoning for joining 00:38:29.040 --> 00:38:30.770 align:start position:0% uh so I guess your reasoning for joining platform<00:38:29.339> development<00:38:29.760> plus<00:38:30.060> you<00:38:30.420> guys<00:38:30.540> suck 00:38:30.770 --> 00:38:30.780 align:start position:0% platform development plus you guys suck 00:38:30.780 --> 00:38:34.010 align:start position:0% platform development plus you guys suck I'm<00:38:30.960> gonna<00:38:31.560> fix<00:38:31.680> it<00:38:31.920> myself 00:38:34.010 --> 00:38:34.020 align:start position:0% I'm gonna fix it myself 00:38:34.020 --> 00:38:36.170 align:start position:0% I'm gonna fix it myself naively<00:38:34.859> maybe<00:38:35.160> so 00:38:36.170 --> 00:38:36.180 align:start position:0% naively maybe so 00:38:36.180 --> 00:38:38.270 align:start position:0% naively maybe so yeah<00:38:36.720> I<00:38:36.900> don't<00:38:37.020> do<00:38:37.140> that<00:38:37.320> for<00:38:37.500> Humanity<00:38:37.980> sorry 00:38:38.270 --> 00:38:38.280 align:start position:0% yeah I don't do that for Humanity sorry 00:38:38.280 --> 00:38:39.970 align:start position:0% yeah I don't do that for Humanity sorry you<00:38:38.579> guys<00:38:38.760> suck 00:38:39.970 --> 00:38:39.980 align:start position:0% you guys suck 00:38:39.980 --> 00:38:43.730 align:start position:0% you guys suck no<00:38:40.980> yes<00:38:41.160> of<00:38:41.400> course<00:38:41.579> uh<00:38:42.420> I<00:38:42.599> think<00:38:42.720> also<00:38:43.079> it's<00:38:43.500> uh 00:38:43.730 --> 00:38:43.740 align:start position:0% no yes of course uh I think also it's uh 00:38:43.740 --> 00:38:45.829 align:start position:0% no yes of course uh I think also it's uh it's<00:38:44.040> where<00:38:44.220> the<00:38:44.460> the<00:38:44.700> biggest<00:38:44.940> problem<00:38:45.359> I 00:38:45.829 --> 00:38:45.839 align:start position:0% it's where the the biggest problem I 00:38:45.839 --> 00:38:48.950 align:start position:0% it's where the the biggest problem I mean<00:38:46.020> like<00:38:46.859> the<00:38:47.160> impact<00:38:47.579> indeed<00:38:48.480> is<00:38:48.660> going<00:38:48.839> to 00:38:48.950 --> 00:38:48.960 align:start position:0% mean like the impact indeed is going to 00:38:48.960 --> 00:38:52.370 align:start position:0% mean like the impact indeed is going to have<00:38:49.260> uh<00:38:49.980> like<00:38:50.579> reverberating<00:38:51.380> consequences 00:38:52.370 --> 00:38:52.380 align:start position:0% have uh like reverberating consequences 00:38:52.380 --> 00:38:54.170 align:start position:0% have uh like reverberating consequences in<00:38:53.040> the<00:38:53.099> future<00:38:53.280> so<00:38:53.579> that's<00:38:53.760> that's<00:38:53.940> where 00:38:54.170 --> 00:38:54.180 align:start position:0% in the future so that's that's where 00:38:54.180 --> 00:38:56.750 align:start position:0% in the future so that's that's where it's<00:38:54.300> the<00:38:54.480> most<00:38:54.599> interesting<00:38:55.020> but<00:38:55.980> uh<00:38:56.460> it's 00:38:56.750 --> 00:38:56.760 align:start position:0% it's the most interesting but uh it's 00:38:56.760 --> 00:38:59.210 align:start position:0% it's the most interesting but uh it's also<00:38:56.940> simply<00:38:57.359> because<00:38:57.599> uh 00:38:59.210 --> 00:38:59.220 align:start position:0% also simply because uh 00:38:59.220 --> 00:39:01.430 align:start position:0% also simply because uh yeah<00:38:59.820> you<00:39:00.060> want<00:39:00.240> to<00:39:00.359> have<00:39:00.540> good<00:39:00.780> tools<00:39:01.140> to 00:39:01.430 --> 00:39:01.440 align:start position:0% yeah you want to have good tools to 00:39:01.440 --> 00:39:03.470 align:start position:0% yeah you want to have good tools to build<00:39:01.619> better<00:39:01.920> societies<00:39:02.460> to<00:39:02.820> build<00:39:03.060> better 00:39:03.470 --> 00:39:03.480 align:start position:0% build better societies to build better 00:39:03.480 --> 00:39:07.130 align:start position:0% build better societies to build better companies<00:39:04.440> to<00:39:04.680> be<00:39:04.920> better<00:39:05.280> software<00:39:06.060> and<00:39:06.900> I 00:39:07.130 --> 00:39:07.140 align:start position:0% companies to be better software and I 00:39:07.140 --> 00:39:07.910 align:start position:0% companies to be better software and I think 00:39:07.910 --> 00:39:07.920 align:start position:0% think 00:39:07.920 --> 00:39:10.609 align:start position:0% think simply<00:39:08.579> the<00:39:09.000> core<00:39:09.240> I<00:39:09.660> mean<00:39:09.839> if<00:39:10.140> you<00:39:10.260> want<00:39:10.440> to 00:39:10.609 --> 00:39:10.619 align:start position:0% simply the core I mean if you want to 00:39:10.619 --> 00:39:12.470 align:start position:0% simply the core I mean if you want to work<00:39:10.859> on<00:39:10.980> your<00:39:11.160> tools<00:39:11.460> you<00:39:11.820> always<00:39:12.060> end<00:39:12.300> up 00:39:12.470 --> 00:39:12.480 align:start position:0% work on your tools you always end up 00:39:12.480 --> 00:39:14.870 align:start position:0% work on your tools you always end up working<00:39:13.020> on<00:39:13.260> the<00:39:13.380> core<00:39:13.560> no<00:39:13.920> matter<00:39:14.099> I've 00:39:14.870 --> 00:39:14.880 align:start position:0% working on the core no matter I've 00:39:14.880 --> 00:39:20.150 align:start position:0% working on the core no matter I've worked<00:39:15.720> on<00:39:15.900> uh<00:39:16.640> on<00:39:17.640> Linux<00:39:18.119> kernel<00:39:18.420> before<00:39:19.160> it 00:39:20.150 --> 00:39:20.160 align:start position:0% worked on uh on Linux kernel before it 00:39:20.160 --> 00:39:21.589 align:start position:0% worked on uh on Linux kernel before it was<00:39:20.280> the<00:39:20.460> same<00:39:20.579> thing<00:39:20.700> you<00:39:20.940> get<00:39:21.119> dragged<00:39:21.480> into 00:39:21.589 --> 00:39:21.599 align:start position:0% was the same thing you get dragged into 00:39:21.599 --> 00:39:23.690 align:start position:0% was the same thing you get dragged into the<00:39:22.020> you<00:39:22.619> can<00:39:22.800> get<00:39:23.099> dragged<00:39:23.400> into<00:39:23.460> the 00:39:23.690 --> 00:39:23.700 align:start position:0% the you can get dragged into the 00:39:23.700 --> 00:39:25.310 align:start position:0% the you can get dragged into the protocol<00:39:24.000> as<00:39:24.359> long<00:39:24.480> as<00:39:24.599> you<00:39:24.839> want<00:39:24.960> to<00:39:25.079> to 00:39:25.310 --> 00:39:25.320 align:start position:0% protocol as long as you want to to 00:39:25.320 --> 00:39:27.950 align:start position:0% protocol as long as you want to to improve<00:39:25.680> your<00:39:25.800> tools<00:39:26.099> hi<00:39:26.820> there 00:39:27.950 --> 00:39:27.960 align:start position:0% improve your tools hi there 00:39:27.960 --> 00:39:31.310 align:start position:0% improve your tools hi there um I<00:39:28.380> have<00:39:28.619> a<00:39:28.859> question<00:39:28.980> about<00:39:29.839> databases<00:39:30.839> the 00:39:31.310 --> 00:39:31.320 align:start position:0% um I have a question about databases the 00:39:31.320 --> 00:39:33.650 align:start position:0% um I have a question about databases the underlying<00:39:31.800> database<00:39:32.160> and<00:39:32.700> get<00:39:33.000> as<00:39:33.540> being 00:39:33.650 --> 00:39:33.660 align:start position:0% underlying database and get as being 00:39:33.660 --> 00:39:35.810 align:start position:0% underlying database and get as being viewed<00:39:33.960> as<00:39:34.079> a<00:39:34.200> database 00:39:35.810 --> 00:39:35.820 align:start position:0% viewed as a database 00:39:35.820 --> 00:39:37.370 align:start position:0% viewed as a database um<00:39:35.880> you<00:39:36.000> guys<00:39:36.180> have<00:39:36.300> talked<00:39:36.540> about<00:39:36.660> Geth<00:39:37.200> as 00:39:37.370 --> 00:39:37.380 align:start position:0% um you guys have talked about Geth as 00:39:37.380 --> 00:39:39.770 align:start position:0% um you guys have talked about Geth as being<00:39:37.619> a<00:39:37.859> monolithic<00:39:38.520> and<00:39:39.180> wanting<00:39:39.480> to<00:39:39.599> remove 00:39:39.770 --> 00:39:39.780 align:start position:0% being a monolithic and wanting to remove 00:39:39.780 --> 00:39:42.109 align:start position:0% being a monolithic and wanting to remove or<00:39:40.320> modularize<00:39:40.920> components<00:39:41.579> and<00:39:41.820> I<00:39:41.940> was 00:39:42.109 --> 00:39:42.119 align:start position:0% or modularize components and I was 00:39:42.119 --> 00:39:43.310 align:start position:0% or modularize components and I was wondering 00:39:43.310 --> 00:39:43.320 align:start position:0% wondering 00:39:43.320 --> 00:39:46.790 align:start position:0% wondering um<00:39:43.859> since<00:39:44.460> database<00:39:45.180> uh<00:39:45.780> throughput<00:39:46.140> had<00:39:46.560> been 00:39:46.790 --> 00:39:46.800 align:start position:0% um since database uh throughput had been 00:39:46.800 --> 00:39:48.950 align:start position:0% um since database uh throughput had been traditionally<00:39:47.460> uh<00:39:48.119> kind<00:39:48.300> of<00:39:48.359> constricting 00:39:48.950 --> 00:39:48.960 align:start position:0% traditionally uh kind of constricting 00:39:48.960 --> 00:39:51.829 align:start position:0% traditionally uh kind of constricting aspect<00:39:49.859> if<00:39:50.400> uh<00:39:50.700> there<00:39:51.000> were<00:39:51.119> any<00:39:51.300> changes<00:39:51.720> to 00:39:51.829 --> 00:39:51.839 align:start position:0% aspect if uh there were any changes to 00:39:51.839 --> 00:39:53.690 align:start position:0% aspect if uh there were any changes to that<00:39:51.960> coming<00:39:52.200> up<00:39:52.440> and<00:39:52.920> this<00:39:53.099> question<00:39:53.280> comes 00:39:53.690 --> 00:39:53.700 align:start position:0% that coming up and this question comes 00:39:53.700 --> 00:39:56.630 align:start position:0% that coming up and this question comes from<00:39:53.880> seeing<00:39:54.300> a<00:39:54.540> remote<00:39:54.720> DB<00:39:55.320> option<00:39:55.980> in<00:39:56.400> the 00:39:56.630 --> 00:39:56.640 align:start position:0% from seeing a remote DB option in the 00:39:56.640 --> 00:39:58.010 align:start position:0% from seeing a remote DB option in the command<00:39:56.880> line<00:39:57.000> options<00:39:57.359> and<00:39:57.599> not<00:39:57.720> being<00:39:57.839> able 00:39:58.010 --> 00:39:58.020 align:start position:0% command line options and not being able 00:39:58.020 --> 00:39:59.810 align:start position:0% command line options and not being able to<00:39:58.140> find<00:39:58.260> any<00:39:58.500> documentation<00:39:59.099> with<00:39:59.520> respect 00:39:59.810 --> 00:39:59.820 align:start position:0% to find any documentation with respect 00:39:59.820 --> 00:40:02.270 align:start position:0% to find any documentation with respect to<00:39:59.940> that<00:40:00.119> so<00:40:00.960> that's<00:40:01.320> a<00:40:01.560> very<00:40:01.800> nice<00:40:01.920> technical 00:40:02.270 --> 00:40:02.280 align:start position:0% to that so that's a very nice technical 00:40:02.280 --> 00:40:05.349 align:start position:0% to that so that's a very nice technical question<00:40:02.640> uh 00:40:05.349 --> 00:40:05.359 align:start position:0% question uh 00:40:05.359 --> 00:40:10.609 align:start position:0% question uh so<00:40:06.359> one<00:40:06.960> um<00:40:07.160> one<00:40:08.160> aspect<00:40:08.820> I'll<00:40:09.359> touch<00:40:09.960> I'll<00:40:10.440> ask 00:40:10.609 --> 00:40:10.619 align:start position:0% so one um one aspect I'll touch I'll ask 00:40:10.619 --> 00:40:12.109 align:start position:0% so one um one aspect I'll touch I'll ask a<00:40:10.800> previous<00:40:10.980> question<00:40:11.280> a<00:40:11.640> lot<00:40:11.760> of<00:40:11.880> people 00:40:12.109 --> 00:40:12.119 align:start position:0% a previous question a lot of people 00:40:12.119 --> 00:40:14.990 align:start position:0% a previous question a lot of people sometimes<00:40:12.660> ask<00:40:12.900> us<00:40:13.079> on<00:40:13.440> on<00:40:14.040> social<00:40:14.280> media<00:40:14.700> why 00:40:14.990 --> 00:40:15.000 align:start position:0% sometimes ask us on on social media why 00:40:15.000 --> 00:40:18.290 align:start position:0% sometimes ask us on on social media why did<00:40:15.420> we<00:40:15.599> pick<00:40:15.780> level<00:40:15.960> DB<00:40:16.859> and<00:40:17.640> that<00:40:18.119> was 00:40:18.290 --> 00:40:18.300 align:start position:0% did we pick level DB and that was 00:40:18.300 --> 00:40:19.849 align:start position:0% did we pick level DB and that was actually<00:40:18.660> also<00:40:18.900> my<00:40:19.140> question<00:40:19.260> when<00:40:19.500> I<00:40:19.619> joined 00:40:19.849 --> 00:40:19.859 align:start position:0% actually also my question when I joined 00:40:19.859 --> 00:40:22.130 align:start position:0% actually also my question when I joined the<00:40:19.980> team<00:40:20.160> and<00:40:20.579> Jeff's<00:40:21.300> answer<00:40:21.540> was<00:40:21.839> because 00:40:22.130 --> 00:40:22.140 align:start position:0% the team and Jeff's answer was because 00:40:22.140 --> 00:40:25.130 align:start position:0% the team and Jeff's answer was because Bitcoin<00:40:22.740> was<00:40:22.920> using<00:40:23.220> it<00:40:23.339> so<00:40:24.180> that's<00:40:24.420> uh<00:40:24.720> that's 00:40:25.130 --> 00:40:25.140 align:start position:0% Bitcoin was using it so that's uh that's 00:40:25.140 --> 00:40:27.230 align:start position:0% Bitcoin was using it so that's uh that's essentially<00:40:25.500> how<00:40:25.859> guests<00:40:26.400> started<00:40:26.700> out<00:40:26.820> using 00:40:27.230 --> 00:40:27.240 align:start position:0% essentially how guests started out using 00:40:27.240 --> 00:40:29.030 align:start position:0% essentially how guests started out using level<00:40:27.359> DB 00:40:29.030 --> 00:40:29.040 align:start position:0% level DB 00:40:29.040 --> 00:40:31.250 align:start position:0% level DB we've<00:40:29.760> actually<00:40:30.060> we've<00:40:30.480> tried<00:40:30.720> switching 00:40:31.250 --> 00:40:31.260 align:start position:0% we've actually we've tried switching 00:40:31.260 --> 00:40:34.849 align:start position:0% we've actually we've tried switching databases<00:40:31.859> many<00:40:32.460> times<00:40:33.260> generally<00:40:34.260> what's 00:40:34.849 --> 00:40:34.859 align:start position:0% databases many times generally what's 00:40:34.859 --> 00:40:37.190 align:start position:0% databases many times generally what's not<00:40:35.280> so<00:40:35.400> visible<00:40:35.760> from<00:40:36.000> the<00:40:36.119> outside<00:40:36.300> is<00:40:36.900> that 00:40:37.190 --> 00:40:37.200 align:start position:0% not so visible from the outside is that 00:40:37.200 --> 00:40:38.410 align:start position:0% not so visible from the outside is that uh 00:40:38.410 --> 00:40:38.420 align:start position:0% uh 00:40:38.420 --> 00:40:41.329 align:start position:0% uh databases<00:40:39.420> are<00:40:39.660> kind<00:40:39.780> of<00:40:39.900> built<00:40:40.260> up<00:40:40.380> have<00:40:41.099> two 00:40:41.329 --> 00:40:41.339 align:start position:0% databases are kind of built up have two 00:40:41.339 --> 00:40:43.069 align:start position:0% databases are kind of built up have two components<00:40:41.820> they<00:40:42.000> have<00:40:42.180> a<00:40:42.420> storage<00:40:42.599> layer 00:40:43.069 --> 00:40:43.079 align:start position:0% components they have a storage layer 00:40:43.079 --> 00:40:44.690 align:start position:0% components they have a storage layer which<00:40:43.500> is<00:40:43.619> kind<00:40:43.800> of<00:40:43.920> like<00:40:43.980> this<00:40:44.220> very<00:40:44.460> dumb 00:40:44.690 --> 00:40:44.700 align:start position:0% which is kind of like this very dumb 00:40:44.700 --> 00:40:46.069 align:start position:0% which is kind of like this very dumb layer<00:40:45.119> that<00:40:45.300> just 00:40:46.069 --> 00:40:46.079 align:start position:0% layer that just 00:40:46.079 --> 00:40:48.530 align:start position:0% layer that just has<00:40:46.619> some<00:40:46.859> very<00:40:47.040> primitive<00:40:47.820> ways<00:40:48.180> to<00:40:48.359> store 00:40:48.530 --> 00:40:48.540 align:start position:0% has some very primitive ways to store 00:40:48.540 --> 00:40:50.690 align:start position:0% has some very primitive ways to store data<00:40:48.900> and<00:40:48.960> retrieve<00:40:49.380> data<00:40:49.740> and<00:40:50.339> then<00:40:50.460> they 00:40:50.690 --> 00:40:50.700 align:start position:0% data and retrieve data and then they 00:40:50.700 --> 00:40:54.190 align:start position:0% data and retrieve data and then they build<00:40:50.880> on<00:40:51.119> top<00:40:51.380> various<00:40:52.380> transaction 00:40:54.190 --> 00:40:54.200 align:start position:0% build on top various transaction 00:40:54.200 --> 00:40:58.609 align:start position:0% build on top various transaction mechanisms<00:40:55.460> journaling<00:40:56.460> all<00:40:57.060> kinds<00:40:57.359> of<00:40:57.359> stuff 00:40:58.609 --> 00:40:58.619 align:start position:0% mechanisms journaling all kinds of stuff 00:40:58.619 --> 00:41:01.069 align:start position:0% mechanisms journaling all kinds of stuff and<00:40:59.339> most<00:40:59.640> people<00:40:59.820> kind<00:41:00.180> of<00:41:00.300> convolute<00:41:00.960> the 00:41:01.069 --> 00:41:01.079 align:start position:0% and most people kind of convolute the 00:41:01.079 --> 00:41:03.109 align:start position:0% and most people kind of convolute the two<00:41:01.260> and<00:41:02.040> most<00:41:02.160> people<00:41:02.339> don't<00:41:02.579> realize<00:41:02.940> that 00:41:03.109 --> 00:41:03.119 align:start position:0% two and most people don't realize that 00:41:03.119 --> 00:41:05.569 align:start position:0% two and most people don't realize that level<00:41:03.300> DB<00:41:03.780> is<00:41:04.260> essentially<00:41:04.560> a<00:41:04.859> storage<00:41:05.040> engine 00:41:05.569 --> 00:41:05.579 align:start position:0% level DB is essentially a storage engine 00:41:05.579 --> 00:41:08.390 align:start position:0% level DB is essentially a storage engine it's<00:41:06.060> not<00:41:06.300> a<00:41:06.720> full-fledged<00:41:07.380> database<00:41:07.740> and 00:41:08.390 --> 00:41:08.400 align:start position:0% it's not a full-fledged database and 00:41:08.400 --> 00:41:10.430 align:start position:0% it's not a full-fledged database and there<00:41:08.579> have<00:41:08.760> been<00:41:08.880> databases<00:41:09.780> built<00:41:10.140> on<00:41:10.260> top 00:41:10.430 --> 00:41:10.440 align:start position:0% there have been databases built on top 00:41:10.440 --> 00:41:12.410 align:start position:0% there have been databases built on top of<00:41:10.619> level<00:41:10.800> DB<00:41:11.220> which<00:41:11.460> have<00:41:11.700> all<00:41:11.880> the<00:41:12.060> bells<00:41:12.359> and 00:41:12.410 --> 00:41:12.420 align:start position:0% of level DB which have all the bells and 00:41:12.420 --> 00:41:13.310 align:start position:0% of level DB which have all the bells and whistles 00:41:13.310 --> 00:41:13.320 align:start position:0% whistles 00:41:13.320 --> 00:41:15.290 align:start position:0% whistles now<00:41:13.680> the<00:41:13.859> issue<00:41:14.099> is<00:41:14.280> that<00:41:14.579> the<00:41:14.760> moment<00:41:14.940> you<00:41:15.119> are 00:41:15.290 --> 00:41:15.300 align:start position:0% now the issue is that the moment you are 00:41:15.300 --> 00:41:17.930 align:start position:0% now the issue is that the moment you are adding<00:41:15.720> uh<00:41:16.260> if<00:41:16.859> we<00:41:17.160> were<00:41:17.339> to<00:41:17.400> use<00:41:17.640> something 00:41:17.930 --> 00:41:17.940 align:start position:0% adding uh if we were to use something 00:41:17.940 --> 00:41:20.870 align:start position:0% adding uh if we were to use something higher<00:41:18.599> level<00:41:18.780> then<00:41:19.680> essentially<00:41:20.099> we're<00:41:20.640> not 00:41:20.870 --> 00:41:20.880 align:start position:0% higher level then essentially we're not 00:41:20.880 --> 00:41:23.270 align:start position:0% higher level then essentially we're not only<00:41:21.180> paying<00:41:22.140> the<00:41:22.320> costs<00:41:22.680> of<00:41:22.920> the<00:41:23.040> storage 00:41:23.270 --> 00:41:23.280 align:start position:0% only paying the costs of the storage 00:41:23.280 --> 00:41:25.010 align:start position:0% only paying the costs of the storage layer<00:41:23.700> rather<00:41:24.000> we<00:41:24.180> also<00:41:24.420> have<00:41:24.540> to<00:41:24.660> pay<00:41:24.780> the 00:41:25.010 --> 00:41:25.020 align:start position:0% layer rather we also have to pay the 00:41:25.020 --> 00:41:26.930 align:start position:0% layer rather we also have to pay the cost<00:41:25.140> associated<00:41:25.680> with<00:41:25.859> running<00:41:26.220> running<00:41:26.640> the 00:41:26.930 --> 00:41:26.940 align:start position:0% cost associated with running running the 00:41:26.940 --> 00:41:28.370 align:start position:0% cost associated with running running the transactions 00:41:28.370 --> 00:41:28.380 align:start position:0% transactions 00:41:28.380 --> 00:41:32.089 align:start position:0% transactions running<00:41:28.920> indexing<00:41:29.640> the<00:41:29.820> tables<00:41:30.420> etc<00:41:30.839> etc<00:41:31.099> so 00:41:32.089 --> 00:41:32.099 align:start position:0% running indexing the tables etc etc so 00:41:32.099 --> 00:41:34.790 align:start position:0% running indexing the tables etc etc so at<00:41:33.000> this<00:41:33.180> point<00:41:33.359> since<00:41:33.960> Geth<00:41:34.320> was<00:41:34.560> kind<00:41:34.680> of 00:41:34.790 --> 00:41:34.800 align:start position:0% at this point since Geth was kind of 00:41:34.800 --> 00:41:36.770 align:start position:0% at this point since Geth was kind of architected<00:41:35.280> from<00:41:35.520> day<00:41:35.700> one<00:41:35.880> to<00:41:36.119> just<00:41:36.359> use<00:41:36.599> a 00:41:36.770 --> 00:41:36.780 align:start position:0% architected from day one to just use a 00:41:36.780 --> 00:41:39.290 align:start position:0% architected from day one to just use a storage<00:41:37.200> layer<00:41:37.619> as<00:41:37.800> his<00:41:37.980> database<00:41:38.400> if<00:41:39.060> we<00:41:39.180> were 00:41:39.290 --> 00:41:39.300 align:start position:0% storage layer as his database if we were 00:41:39.300 --> 00:41:41.990 align:start position:0% storage layer as his database if we were to<00:41:39.480> plug<00:41:40.200> in<00:41:40.440> any<00:41:40.800> full-fledged<00:41:41.640> database 00:41:41.990 --> 00:41:42.000 align:start position:0% to plug in any full-fledged database 00:41:42.000 --> 00:41:44.569 align:start position:0% to plug in any full-fledged database instead<00:41:42.420> of<00:41:42.540> it<00:41:42.720> everything<00:41:43.320> becomes<00:41:44.040> just 00:41:44.569 --> 00:41:44.579 align:start position:0% instead of it everything becomes just 00:41:44.579 --> 00:41:46.849 align:start position:0% instead of it everything becomes just insanely<00:41:45.119> slow<00:41:45.359> because<00:41:45.720> Geth<00:41:46.440> was<00:41:46.680> not 00:41:46.849 --> 00:41:46.859 align:start position:0% insanely slow because Geth was not 00:41:46.859 --> 00:41:48.290 align:start position:0% insanely slow because Geth was not architected<00:41:47.400> to<00:41:47.579> use<00:41:47.700> these<00:41:48.000> high-level 00:41:48.290 --> 00:41:48.300 align:start position:0% architected to use these high-level 00:41:48.300 --> 00:41:50.630 align:start position:0% architected to use these high-level Primitives<00:41:48.780> get<00:41:49.079> always<00:41:49.440> assumes<00:41:50.280> that<00:41:50.460> it 00:41:50.630 --> 00:41:50.640 align:start position:0% Primitives get always assumes that it 00:41:50.640 --> 00:41:52.670 align:start position:0% Primitives get always assumes that it has<00:41:50.880> more<00:41:51.359> or<00:41:51.540> less<00:41:51.599> direct<00:41:51.839> access<00:41:52.200> to<00:41:52.500> the 00:41:52.670 --> 00:41:52.680 align:start position:0% has more or less direct access to the 00:41:52.680 --> 00:41:55.250 align:start position:0% has more or less direct access to the data<00:41:52.980> and<00:41:53.760> because<00:41:53.940> of<00:41:54.119> that<00:41:54.300> it's<00:41:54.660> we've 00:41:55.250 --> 00:41:55.260 align:start position:0% data and because of that it's we've 00:41:55.260 --> 00:41:57.410 align:start position:0% data and because of that it's we've tried<00:41:55.500> we've<00:41:56.280> have<00:41:56.520> a<00:41:56.640> lot<00:41:56.700> of<00:41:56.760> PR's<00:41:57.300> trying 00:41:57.410 --> 00:41:57.420 align:start position:0% tried we've have a lot of PR's trying 00:41:57.420 --> 00:41:58.849 align:start position:0% tried we've have a lot of PR's trying different<00:41:57.660> databases<00:41:58.260> and<00:41:58.440> they<00:41:58.680> always 00:41:58.849 --> 00:41:58.859 align:start position:0% different databases and they always 00:41:58.859 --> 00:42:00.530 align:start position:0% different databases and they always crashed<00:41:59.400> and<00:41:59.520> burned 00:42:00.530 --> 00:42:00.540 align:start position:0% crashed and burned 00:42:00.540 --> 00:42:02.510 align:start position:0% crashed and burned one<00:42:01.140> thing<00:42:01.320> that<00:42:01.560> we<00:42:01.740> currently<00:42:02.040> are<00:42:02.280> working 00:42:02.510 --> 00:42:02.520 align:start position:0% one thing that we currently are working 00:42:02.520 --> 00:42:05.750 align:start position:0% one thing that we currently are working on<00:42:02.960> uh<00:42:03.960> actually<00:42:04.140> Jared<00:42:04.619> is<00:42:04.740> working<00:42:04.920> on<00:42:05.099> it<00:42:05.220> is 00:42:05.750 --> 00:42:05.760 align:start position:0% on uh actually Jared is working on it is 00:42:05.760 --> 00:42:08.329 align:start position:0% on uh actually Jared is working on it is to<00:42:05.940> switch<00:42:06.180> out<00:42:06.359> level<00:42:06.660> DB<00:42:07.140> to<00:42:07.380> Pebble 00:42:08.329 --> 00:42:08.339 align:start position:0% to switch out level DB to Pebble 00:42:08.339 --> 00:42:11.030 align:start position:0% to switch out level DB to Pebble pebble<00:42:09.240> is<00:42:09.480> kind<00:42:09.660> of<00:42:09.780> like<00:42:09.960> a 00:42:11.030 --> 00:42:11.040 align:start position:0% pebble is kind of like a 00:42:11.040 --> 00:42:14.329 align:start position:0% pebble is kind of like a Next<00:42:11.700> Generation<00:42:12.180> version<00:42:12.599> of<00:42:12.960> uh<00:42:13.320> level<00:42:13.920> DB 00:42:14.329 --> 00:42:14.339 align:start position:0% Next Generation version of uh level DB 00:42:14.339 --> 00:42:17.030 align:start position:0% Next Generation version of uh level DB but<00:42:14.579> it's<00:42:14.760> still<00:42:15.000> just<00:42:15.420> the<00:42:15.540> storage<00:42:15.720> engine 00:42:17.030 --> 00:42:17.040 align:start position:0% but it's still just the storage engine 00:42:17.040 --> 00:42:20.990 align:start position:0% but it's still just the storage engine as<00:42:17.579> for<00:42:17.760> remote<00:42:18.359> databases 00:42:20.990 --> 00:42:21.000 align:start position:0% as for remote databases 00:42:21.000 --> 00:42:22.970 align:start position:0% as for remote databases the<00:42:21.839> problem<00:42:22.079> is<00:42:22.260> that<00:42:22.440> one<00:42:22.619> of<00:42:22.740> the 00:42:22.970 --> 00:42:22.980 align:start position:0% the problem is that one of the 00:42:22.980 --> 00:42:24.950 align:start position:0% the problem is that one of the bottlenecks<00:42:23.760> of<00:42:23.820> ethereum<00:42:24.240> of<00:42:24.420> running<00:42:24.780> an 00:42:24.950 --> 00:42:24.960 align:start position:0% bottlenecks of ethereum of running an 00:42:24.960 --> 00:42:27.410 align:start position:0% bottlenecks of ethereum of running an ethereum<00:42:25.320> node<00:42:25.619> is<00:42:25.859> disk<00:42:26.400> access<00:42:26.579> i<00:42:27.240> o 00:42:27.410 --> 00:42:27.420 align:start position:0% ethereum node is disk access i o 00:42:27.420 --> 00:42:29.030 align:start position:0% ethereum node is disk access i o operations<00:42:27.780> per<00:42:28.020> second 00:42:29.030 --> 00:42:29.040 align:start position:0% operations per second 00:42:29.040 --> 00:42:30.950 align:start position:0% operations per second now<00:42:29.520> the<00:42:29.700> moment<00:42:29.940> you<00:42:30.119> move<00:42:30.300> the<00:42:30.480> data<00:42:30.780> away 00:42:30.950 --> 00:42:30.960 align:start position:0% now the moment you move the data away 00:42:30.960 --> 00:42:33.109 align:start position:0% now the moment you move the data away from<00:42:31.260> the<00:42:31.440> node<00:42:31.640> the<00:42:32.640> actually<00:42:32.880> the 00:42:33.109 --> 00:42:33.119 align:start position:0% from the node the actually the 00:42:33.119 --> 00:42:35.810 align:start position:0% from the node the actually the bottleneck<00:42:33.540> is<00:42:33.839> getting<00:42:34.020> way<00:42:34.380> way<00:42:34.560> worse 00:42:35.810 --> 00:42:35.820 align:start position:0% bottleneck is getting way way worse 00:42:35.820 --> 00:42:38.510 align:start position:0% bottleneck is getting way way worse so<00:42:36.420> it's<00:42:36.720> uh<00:42:37.079> instead<00:42:37.800> of<00:42:37.920> making<00:42:38.099> making 00:42:38.510 --> 00:42:38.520 align:start position:0% so it's uh instead of making making 00:42:38.520 --> 00:42:41.270 align:start position:0% so it's uh instead of making making things<00:42:38.880> better<00:42:39.180> you<00:42:39.599> are<00:42:39.780> making<00:42:40.079> them 00:42:41.270 --> 00:42:41.280 align:start position:0% things better you are making them 00:42:41.280 --> 00:42:44.089 align:start position:0% things better you are making them a<00:42:41.760> lot<00:42:41.880> worse<00:42:42.180> since<00:42:42.540> accessing<00:42:43.079> I<00:42:43.440> mean 00:42:44.089 --> 00:42:44.099 align:start position:0% a lot worse since accessing I mean 00:42:44.099 --> 00:42:46.970 align:start position:0% a lot worse since accessing I mean usually<00:42:44.760> you<00:42:45.060> have 00:42:46.970 --> 00:42:46.980 align:start position:0% usually you have 00:42:46.980 --> 00:42:49.250 align:start position:0% usually you have if<00:42:47.339> you<00:42:47.460> want<00:42:47.579> to<00:42:47.640> access<00:42:47.760> SSD<00:42:48.420> a<00:42:48.540> modern<00:42:48.720> SSD 00:42:49.250 --> 00:42:49.260 align:start position:0% if you want to access SSD a modern SSD 00:42:49.260 --> 00:42:51.770 align:start position:0% if you want to access SSD a modern SSD can<00:42:49.440> do<00:42:49.619> maybe<00:42:49.859> half<00:42:50.220> a<00:42:50.400> million<00:42:50.760> i<00:42:51.180> o<00:42:51.359> Ops<00:42:51.660> per 00:42:51.770 --> 00:42:51.780 align:start position:0% can do maybe half a million i o Ops per 00:42:51.780 --> 00:42:54.050 align:start position:0% can do maybe half a million i o Ops per second<00:42:52.020> that's<00:42:52.920> not<00:42:53.099> the<00:42:53.220> high<00:42:53.400> end<00:42:53.520> SSD 00:42:54.050 --> 00:42:54.060 align:start position:0% second that's not the high end SSD 00:42:54.060 --> 00:42:57.230 align:start position:0% second that's not the high end SSD that's<00:42:54.300> a<00:42:54.599> payable<00:42:55.320> affordable<00:42:56.099> SSD 00:42:57.230 --> 00:42:57.240 align:start position:0% that's a payable affordable SSD 00:42:57.240 --> 00:42:59.630 align:start position:0% that's a payable affordable SSD you<00:42:57.660> cannot<00:42:57.900> do<00:42:58.020> 100<00:42:58.140> million<00:42:58.800> round<00:42:59.400> trip 00:42:59.630 --> 00:42:59.640 align:start position:0% you cannot do 100 million round trip 00:42:59.640 --> 00:43:01.849 align:start position:0% you cannot do 100 million round trip times<00:42:59.880> on<00:43:00.119> the<00:43:00.180> network<00:43:00.300> per<00:43:00.660> second<00:43:00.839> so<00:43:01.619> it 00:43:01.849 --> 00:43:01.859 align:start position:0% times on the network per second so it 00:43:01.859 --> 00:43:04.849 align:start position:0% times on the network per second so it gets<00:43:02.520> a<00:43:03.300> lot<00:43:03.420> slower<00:43:03.900> if<00:43:04.200> we<00:43:04.319> go<00:43:04.500> down<00:43:04.680> that 00:43:04.849 --> 00:43:04.859 align:start position:0% gets a lot slower if we go down that 00:43:04.859 --> 00:43:07.670 align:start position:0% gets a lot slower if we go down that path<00:43:05.099> of<00:43:06.000> course<00:43:06.119> you<00:43:06.599> could<00:43:06.720> always<00:43:06.960> say<00:43:07.440> that 00:43:07.670 --> 00:43:07.680 align:start position:0% path of course you could always say that 00:43:07.680 --> 00:43:10.970 align:start position:0% path of course you could always say that why<00:43:07.920> we<00:43:08.280> could<00:43:08.460> create<00:43:09.079> an<00:43:10.079> ethereum<00:43:10.740> node 00:43:10.970 --> 00:43:10.980 align:start position:0% why we could create an ethereum node 00:43:10.980 --> 00:43:13.550 align:start position:0% why we could create an ethereum node architecture<00:43:11.579> which<00:43:12.060> has<00:43:12.660> a<00:43:12.839> remote<00:43:12.960> database 00:43:13.550 --> 00:43:13.560 align:start position:0% architecture which has a remote database 00:43:13.560 --> 00:43:15.290 align:start position:0% architecture which has a remote database and<00:43:13.800> then<00:43:13.920> you<00:43:14.099> could<00:43:14.220> have<00:43:14.339> multiple<00:43:14.760> clients 00:43:15.290 --> 00:43:15.300 align:start position:0% and then you could have multiple clients 00:43:15.300 --> 00:43:18.349 align:start position:0% and then you could have multiple clients using<00:43:15.780> that<00:43:16.079> same<00:43:16.319> database<00:43:17.160> that's<00:43:18.000> a<00:43:18.240> very 00:43:18.349 --> 00:43:18.359 align:start position:0% using that same database that's a very 00:43:18.359 --> 00:43:20.390 align:start position:0% using that same database that's a very interesting<00:43:18.660> architectural<00:43:19.260> decision<00:43:19.680> but 00:43:20.390 --> 00:43:20.400 align:start position:0% interesting architectural decision but 00:43:20.400 --> 00:43:22.490 align:start position:0% interesting architectural decision but that<00:43:20.700> is<00:43:21.000> essentially<00:43:21.420> writing<00:43:21.900> a<00:43:22.079> completely 00:43:22.490 --> 00:43:22.500 align:start position:0% that is essentially writing a completely 00:43:22.500 --> 00:43:24.589 align:start position:0% that is essentially writing a completely new<00:43:22.740> client<00:43:22.980> from<00:43:23.280> scratch<00:43:23.579> so<00:43:24.000> you<00:43:24.359> cannot 00:43:24.589 --> 00:43:24.599 align:start position:0% new client from scratch so you cannot 00:43:24.599 --> 00:43:27.530 align:start position:0% new client from scratch so you cannot really<00:43:25.099> retrospectively<00:43:26.099> retrofit<00:43:26.940> gas<00:43:27.240> to 00:43:27.530 --> 00:43:27.540 align:start position:0% really retrospectively retrofit gas to 00:43:27.540 --> 00:43:29.569 align:start position:0% really retrospectively retrofit gas to use<00:43:27.660> it<00:43:27.839> it<00:43:28.079> would<00:43:28.319> be<00:43:28.440> its<00:43:28.980> own<00:43:29.040> new<00:43:29.220> client 00:43:29.569 --> 00:43:29.579 align:start position:0% use it it would be its own new client 00:43:29.579 --> 00:43:31.790 align:start position:0% use it it would be its own new client hey<00:43:30.300> guys<00:43:30.540> seconding<00:43:31.260> all<00:43:31.500> the<00:43:31.619> previous 00:43:31.790 --> 00:43:31.800 align:start position:0% hey guys seconding all the previous 00:43:31.800 --> 00:43:33.349 align:start position:0% hey guys seconding all the previous comments<00:43:32.280> thank<00:43:32.520> you<00:43:32.640> for<00:43:32.819> the<00:43:33.000> incredible 00:43:33.349 --> 00:43:33.359 align:start position:0% comments thank you for the incredible 00:43:33.359 --> 00:43:34.790 align:start position:0% comments thank you for the incredible work<00:43:33.540> you're<00:43:33.780> doing<00:43:33.960> in<00:43:34.140> the<00:43:34.260> ecosystem<00:43:34.560> you 00:43:34.790 --> 00:43:34.800 align:start position:0% work you're doing in the ecosystem you 00:43:34.800 --> 00:43:37.250 align:start position:0% work you're doing in the ecosystem you guys<00:43:34.920> are<00:43:35.040> the<00:43:35.160> unsung<00:43:35.400> heroes<00:43:35.880> of<00:43:36.000> ethereum 00:43:37.250 --> 00:43:37.260 align:start position:0% guys are the unsung heroes of ethereum 00:43:37.260 --> 00:43:39.170 align:start position:0% guys are the unsung heroes of ethereum um<00:43:37.319> quick<00:43:37.859> question<00:43:38.099> if<00:43:38.760> you<00:43:38.880> were<00:43:39.060> to 00:43:39.170 --> 00:43:39.180 align:start position:0% um quick question if you were to 00:43:39.180 --> 00:43:41.809 align:start position:0% um quick question if you were to hypothetically<00:43:39.900> re-architect<00:43:40.800> Geth<00:43:41.460> from 00:43:41.809 --> 00:43:41.819 align:start position:0% hypothetically re-architect Geth from 00:43:41.819 --> 00:43:43.490 align:start position:0% hypothetically re-architect Geth from scratch<00:43:42.060> today<00:43:42.359> knowing<00:43:42.900> everything<00:43:43.079> we<00:43:43.319> know 00:43:43.490 --> 00:43:43.500 align:start position:0% scratch today knowing everything we know 00:43:43.500 --> 00:43:45.109 align:start position:0% scratch today knowing everything we know factoring<00:43:44.099> in<00:43:44.160> the<00:43:44.339> merge<00:43:44.579> what<00:43:44.760> would<00:43:44.880> you<00:43:45.000> do 00:43:45.109 --> 00:43:45.119 align:start position:0% factoring in the merge what would you do 00:43:45.119 --> 00:43:48.290 align:start position:0% factoring in the merge what would you do differently<00:43:45.480> uh<00:43:46.440> I<00:43:46.619> think<00:43:46.740> we<00:43:46.980> would<00:43:47.220> at<00:43:48.180> least 00:43:48.290 --> 00:43:48.300 align:start position:0% differently uh I think we would at least 00:43:48.300 --> 00:43:49.970 align:start position:0% differently uh I think we would at least I<00:43:48.599> would<00:43:48.839> be 00:43:49.970 --> 00:43:49.980 align:start position:0% I would be 00:43:49.980 --> 00:43:52.609 align:start position:0% I would be more<00:43:50.880> careful<00:43:51.240> about<00:43:51.480> the<00:43:51.839> features<00:43:52.200> that 00:43:52.609 --> 00:43:52.619 align:start position:0% more careful about the features that 00:43:52.619 --> 00:43:56.050 align:start position:0% more careful about the features that that<00:43:53.280> we<00:43:53.940> accept<00:43:54.119> into<00:43:54.839> the<00:43:55.260> code 00:43:56.050 --> 00:43:56.060 align:start position:0% that we accept into the code 00:43:56.060 --> 00:43:58.390 align:start position:0% that we accept into the code there's<00:43:57.060> some 00:43:58.390 --> 00:43:58.400 align:start position:0% there's some 00:43:58.400 --> 00:44:00.770 align:start position:0% there's some stuff<00:43:59.400> that 00:44:00.770 --> 00:44:00.780 align:start position:0% stuff that 00:44:00.780 --> 00:44:02.690 align:start position:0% stuff that barely 00:44:02.690 --> 00:44:02.700 align:start position:0% barely 00:44:02.700 --> 00:44:06.730 align:start position:0% barely anyone<00:44:03.359> uses<00:44:03.720> but<00:44:04.500> it's<00:44:04.680> it's<00:44:04.980> still<00:44:05.220> used 00:44:06.730 --> 00:44:06.740 align:start position:0% anyone uses but it's it's still used 00:44:06.740 --> 00:44:10.010 align:start position:0% anyone uses but it's it's still used and<00:44:07.740> uh 00:44:10.010 --> 00:44:10.020 align:start position:0% and uh 00:44:10.020 --> 00:44:12.230 align:start position:0% and uh something<00:44:10.500> that<00:44:10.740> that<00:44:11.280> kind<00:44:11.460> of<00:44:11.579> bugs<00:44:11.880> me<00:44:12.000> is 00:44:12.230 --> 00:44:12.240 align:start position:0% something that that kind of bugs me is 00:44:12.240 --> 00:44:15.230 align:start position:0% something that that kind of bugs me is that<00:44:12.480> we<00:44:12.660> write<00:44:12.900> a<00:44:13.200> lot<00:44:13.319> of<00:44:13.440> like<00:44:13.740> small<00:44:14.099> tools 00:44:15.230 --> 00:44:15.240 align:start position:0% that we write a lot of like small tools 00:44:15.240 --> 00:44:17.510 align:start position:0% that we write a lot of like small tools and<00:44:15.839> instead<00:44:16.200> of<00:44:16.319> having<00:44:16.560> them<00:44:16.859> separate<00:44:17.280> from 00:44:17.510 --> 00:44:17.520 align:start position:0% and instead of having them separate from 00:44:17.520 --> 00:44:19.809 align:start position:0% and instead of having them separate from the<00:44:17.760> client<00:44:18.060> they<00:44:18.540> end<00:44:18.660> up<00:44:18.839> somehow<00:44:19.260> in<00:44:19.500> Geth 00:44:19.809 --> 00:44:19.819 align:start position:0% the client they end up somehow in Geth 00:44:19.819 --> 00:44:23.150 align:start position:0% the client they end up somehow in Geth and<00:44:20.819> uh<00:44:21.240> yeah<00:44:21.480> I<00:44:21.960> would<00:44:22.079> I<00:44:22.319> would<00:44:22.560> have<00:44:22.680> like<00:44:22.980> a 00:44:23.150 --> 00:44:23.160 align:start position:0% and uh yeah I would I would have like a 00:44:23.160 --> 00:44:26.210 align:start position:0% and uh yeah I would I would have like a stronger<00:44:23.520> policy<00:44:24.000> of<00:44:24.500> not<00:44:25.500> including<00:44:26.040> them 00:44:26.210 --> 00:44:26.220 align:start position:0% stronger policy of not including them 00:44:26.220 --> 00:44:29.950 align:start position:0% stronger policy of not including them for<00:44:26.700> example<00:44:27.000> for<00:44:27.599> example<00:44:27.900> the<00:44:28.200> ABI<00:44:28.980> gen 00:44:29.950 --> 00:44:29.960 align:start position:0% for example for example the ABI gen 00:44:29.960 --> 00:44:33.470 align:start position:0% for example for example the ABI gen stuff<00:44:30.960> should<00:44:31.500> in<00:44:31.859> my<00:44:31.980> opinion<00:44:32.339> be<00:44:32.640> a 00:44:33.470 --> 00:44:33.480 align:start position:0% stuff should in my opinion be a 00:44:33.480 --> 00:44:35.569 align:start position:0% stuff should in my opinion be a different<00:44:33.900> thing 00:44:35.569 --> 00:44:35.579 align:start position:0% different thing 00:44:35.579 --> 00:44:38.569 align:start position:0% different thing um<00:44:35.640> but<00:44:36.240> I<00:44:36.540> I<00:44:36.780> I<00:44:37.020> already<00:44:37.680> know<00:44:37.920> what<00:44:38.099> Peter<00:44:38.400> is 00:44:38.569 --> 00:44:38.579 align:start position:0% um but I I I already know what Peter is 00:44:38.579 --> 00:44:40.190 align:start position:0% um but I I I already know what Peter is going<00:44:38.700> to<00:44:38.819> say<00:44:39.000> but<00:44:39.300> then<00:44:39.540> you<00:44:39.720> need<00:44:39.900> someone 00:44:40.190 --> 00:44:40.200 align:start position:0% going to say but then you need someone 00:44:40.200 --> 00:44:42.650 align:start position:0% going to say but then you need someone to<00:44:40.680> actually<00:44:40.859> maintain<00:44:41.460> it<00:44:41.640> and<00:44:42.180> if<00:44:42.359> it's<00:44:42.480> not 00:44:42.650 --> 00:44:42.660 align:start position:0% to actually maintain it and if it's not 00:44:42.660 --> 00:44:44.210 align:start position:0% to actually maintain it and if it's not in<00:44:42.839> the<00:44:42.960> client<00:44:43.200> it's<00:44:43.440> not<00:44:43.619> going<00:44:43.800> to<00:44:43.980> be 00:44:44.210 --> 00:44:44.220 align:start position:0% in the client it's not going to be 00:44:44.220 --> 00:44:45.670 align:start position:0% in the client it's not going to be maintained 00:44:45.670 --> 00:44:45.680 align:start position:0% maintained 00:44:45.680 --> 00:44:48.829 align:start position:0% maintained if<00:44:46.680> it's<00:44:46.859> not<00:44:47.040> in<00:44:47.160> our<00:44:47.339> code<00:44:47.579> base 00:44:48.829 --> 00:44:48.839 align:start position:0% if it's not in our code base 00:44:48.839 --> 00:44:51.849 align:start position:0% if it's not in our code base no<00:44:49.800> I<00:44:49.980> actually<00:44:50.160> agree<00:44:50.460> with<00:44:50.579> you 00:44:51.849 --> 00:44:51.859 align:start position:0% no I actually agree with you 00:44:51.859 --> 00:44:56.150 align:start position:0% no I actually agree with you no<00:44:52.859> so<00:44:53.160> I<00:44:53.520> uh<00:44:53.940> I<00:44:54.180> just<00:44:54.599> wanted<00:44:54.780> to<00:44:54.960> add<00:44:55.200> what 00:44:56.150 --> 00:44:56.160 align:start position:0% no so I uh I just wanted to add what 00:44:56.160 --> 00:44:57.650 align:start position:0% no so I uh I just wanted to add what Mary<00:44:56.339> said<00:44:56.579> previously<00:44:57.060> it<00:44:57.240> was<00:44:57.300> brought<00:44:57.540> up 00:44:57.650 --> 00:44:57.660 align:start position:0% Mary said previously it was brought up 00:44:57.660 --> 00:44:59.690 align:start position:0% Mary said previously it was brought up that<00:44:57.900> the<00:44:58.500> problem<00:44:58.619> is<00:44:58.800> that<00:44:59.040> one<00:44:59.160> get<00:44:59.339> was 00:44:59.690 --> 00:44:59.700 align:start position:0% that the problem is that one get was 00:44:59.700 --> 00:45:00.950 align:start position:0% that the problem is that one get was started 00:45:00.950 --> 00:45:00.960 align:start position:0% started 00:45:00.960 --> 00:45:03.109 align:start position:0% started we<00:45:01.440> had<00:45:01.619> to<00:45:01.740> be<00:45:01.920> this<00:45:02.160> monolithic<00:45:02.760> thing<00:45:02.880> that 00:45:03.109 --> 00:45:03.119 align:start position:0% we had to be this monolithic thing that 00:45:03.119 --> 00:45:05.990 align:start position:0% we had to be this monolithic thing that does<00:45:03.240> everything<00:45:03.680> and<00:45:04.680> this<00:45:05.160> kind<00:45:05.400> of<00:45:05.520> makes 00:45:05.990 --> 00:45:06.000 align:start position:0% does everything and this kind of makes 00:45:06.000 --> 00:45:08.950 align:start position:0% does everything and this kind of makes it<00:45:06.300> leaves<00:45:07.079> its<00:45:07.319> mark<00:45:07.380> on<00:45:07.619> the<00:45:07.740> code<00:45:07.859> base<00:45:08.160> and 00:45:08.950 --> 00:45:08.960 align:start position:0% it leaves its mark on the code base and 00:45:08.960 --> 00:45:12.050 align:start position:0% it leaves its mark on the code base and it's<00:45:09.960> very<00:45:10.140> very<00:45:10.319> hard<00:45:10.560> to<00:45:10.740> get<00:45:10.920> rid<00:45:11.099> of<00:45:11.280> stuff 00:45:12.050 --> 00:45:12.060 align:start position:0% it's very very hard to get rid of stuff 00:45:12.060 --> 00:45:15.109 align:start position:0% it's very very hard to get rid of stuff and<00:45:12.960> I<00:45:13.560> mean<00:45:13.680> we<00:45:13.859> could<00:45:13.980> get<00:45:14.160> rid<00:45:14.339> of<00:45:14.520> stuff<00:45:14.760> but 00:45:15.109 --> 00:45:15.119 align:start position:0% and I mean we could get rid of stuff but 00:45:15.119 --> 00:45:16.970 align:start position:0% and I mean we could get rid of stuff but some<00:45:15.420> people<00:45:15.599> somewhere<00:45:16.200> always<00:45:16.380> depend<00:45:16.800> on 00:45:16.970 --> 00:45:16.980 align:start position:0% some people somewhere always depend on 00:45:16.980 --> 00:45:19.790 align:start position:0% some people somewhere always depend on it<00:45:17.160> so<00:45:17.640> I<00:45:17.819> think<00:45:18.000> the<00:45:18.599> if<00:45:19.140> we<00:45:19.319> were<00:45:19.440> to<00:45:19.560> start 00:45:19.790 --> 00:45:19.800 align:start position:0% it so I think the if we were to start 00:45:19.800 --> 00:45:22.609 align:start position:0% it so I think the if we were to start over<00:45:20.040> get<00:45:20.579> from<00:45:21.359> way<00:45:21.599> back<00:45:21.839> eight<00:45:22.079> years<00:45:22.260> ago 00:45:22.609 --> 00:45:22.619 align:start position:0% over get from way back eight years ago 00:45:22.619 --> 00:45:24.050 align:start position:0% over get from way back eight years ago we<00:45:22.920> would<00:45:23.040> end<00:45:23.220> up<00:45:23.280> in<00:45:23.520> this<00:45:23.640> exact<00:45:23.880> same 00:45:24.050 --> 00:45:24.060 align:start position:0% we would end up in this exact same 00:45:24.060 --> 00:45:27.050 align:start position:0% we would end up in this exact same situation<00:45:24.920> because<00:45:25.920> uh 00:45:27.050 --> 00:45:27.060 align:start position:0% situation because uh 00:45:27.060 --> 00:45:29.450 align:start position:0% situation because uh we<00:45:27.599> would<00:45:27.720> need<00:45:27.900> to<00:45:28.079> make<00:45:28.260> the<00:45:28.440> same<00:45:28.619> tools<00:45:29.040> and 00:45:29.450 --> 00:45:29.460 align:start position:0% we would need to make the same tools and 00:45:29.460 --> 00:45:30.890 align:start position:0% we would need to make the same tools and we<00:45:29.579> would<00:45:29.700> and<00:45:29.940> so 00:45:30.890 --> 00:45:30.900 align:start position:0% we would and so 00:45:30.900 --> 00:45:33.290 align:start position:0% we would and so I<00:45:31.440> don't<00:45:31.560> think<00:45:31.859> the<00:45:32.579> fact<00:45:32.640> that<00:45:32.819> we<00:45:32.940> have<00:45:33.119> a 00:45:33.290 --> 00:45:33.300 align:start position:0% I don't think the fact that we have a 00:45:33.300 --> 00:45:35.150 align:start position:0% I don't think the fact that we have a lot<00:45:33.420> of<00:45:33.480> Legacy<00:45:33.960> junk<00:45:34.440> in<00:45:34.619> the<00:45:34.740> code<00:45:34.859> base 00:45:35.150 --> 00:45:35.160 align:start position:0% lot of Legacy junk in the code base 00:45:35.160 --> 00:45:39.170 align:start position:0% lot of Legacy junk in the code base that's<00:45:36.000> not<00:45:36.300> a<00:45:36.900> bug<00:45:37.319> it's<00:45:38.099> just<00:45:38.460> the<00:45:38.819> way<00:45:38.940> the 00:45:39.170 --> 00:45:39.180 align:start position:0% that's not a bug it's just the way the 00:45:39.180 --> 00:45:42.290 align:start position:0% that's not a bug it's just the way the ecosystem<00:45:39.599> evolved<00:45:40.280> so<00:45:41.280> I<00:45:41.760> don't<00:45:41.880> think<00:45:42.000> that 00:45:42.290 --> 00:45:42.300 align:start position:0% ecosystem evolved so I don't think that 00:45:42.300 --> 00:45:44.450 align:start position:0% ecosystem evolved so I don't think that would<00:45:42.420> have<00:45:42.599> been<00:45:42.780> preventable<00:45:43.440> if<00:45:44.160> we<00:45:44.280> were 00:45:44.450 --> 00:45:44.460 align:start position:0% would have been preventable if we were 00:45:44.460 --> 00:45:46.670 align:start position:0% would have been preventable if we were to<00:45:44.640> start<00:45:44.880> over<00:45:45.300> now<00:45:45.599> then<00:45:46.079> all<00:45:46.319> of<00:45:46.440> a<00:45:46.560> sudden 00:45:46.670 --> 00:45:46.680 align:start position:0% to start over now then all of a sudden 00:45:46.680 --> 00:45:49.190 align:start position:0% to start over now then all of a sudden you<00:45:47.099> can<00:45:47.220> rely<00:45:47.520> on<00:45:47.819> all<00:45:48.359> the<00:45:48.480> awesome<00:45:48.720> tools 00:45:49.190 --> 00:45:49.200 align:start position:0% you can rely on all the awesome tools 00:45:49.200 --> 00:45:50.930 align:start position:0% you can rely on all the awesome tools that<00:45:49.319> people<00:45:49.500> created<00:45:49.980> and<00:45:50.339> that<00:45:50.460> allows<00:45:50.819> the 00:45:50.930 --> 00:45:50.940 align:start position:0% that people created and that allows the 00:45:50.940 --> 00:45:53.750 align:start position:0% that people created and that allows the client<00:45:51.180> to<00:45:51.300> be<00:45:51.420> a<00:45:51.540> lot<00:45:51.660> Slimmer<00:45:52.079> hey<00:45:53.400> um<00:45:53.460> I 00:45:53.750 --> 00:45:53.760 align:start position:0% client to be a lot Slimmer hey um I 00:45:53.760 --> 00:45:55.430 align:start position:0% client to be a lot Slimmer hey um I think<00:45:53.880> it's<00:45:54.180> a<00:45:54.420> lot<00:45:54.540> of<00:45:54.660> stuff<00:45:54.780> changed<00:45:55.200> over 00:45:55.430 --> 00:45:55.440 align:start position:0% think it's a lot of stuff changed over 00:45:55.440 --> 00:45:57.349 align:start position:0% think it's a lot of stuff changed over the<00:45:55.619> last<00:45:55.800> like<00:45:56.040> one<00:45:56.280> year<00:45:56.520> and<00:45:56.700> a<00:45:56.880> half<00:45:56.940> but 00:45:57.349 --> 00:45:57.359 align:start position:0% the last like one year and a half but 00:45:57.359 --> 00:45:59.329 align:start position:0% the last like one year and a half but especially<00:45:57.720> what's<00:45:58.200> changed<00:45:58.859> significantly 00:45:59.329 --> 00:45:59.339 align:start position:0% especially what's changed significantly 00:45:59.339 --> 00:46:02.210 align:start position:0% especially what's changed significantly I<00:45:59.700> think<00:45:59.819> it's<00:46:00.240> that<00:46:00.720> a<00:46:01.560> lot<00:46:01.680> of<00:46:01.800> other 00:46:02.210 --> 00:46:02.220 align:start position:0% I think it's that a lot of other 00:46:02.220 --> 00:46:04.609 align:start position:0% I think it's that a lot of other networks<00:46:02.760> appeared<00:46:03.359> that<00:46:03.780> actually<00:46:03.960> locked<00:46:04.500> a 00:46:04.609 --> 00:46:04.619 align:start position:0% networks appeared that actually locked a 00:46:04.619 --> 00:46:07.309 align:start position:0% networks appeared that actually locked a lot<00:46:04.680> of<00:46:04.859> billions<00:46:05.339> of<00:46:05.579> dollars<00:46:06.119> like<00:46:06.540> somehow 00:46:07.309 --> 00:46:07.319 align:start position:0% lot of billions of dollars like somehow 00:46:07.319 --> 00:46:09.890 align:start position:0% lot of billions of dollars like somehow that<00:46:07.740> actually<00:46:07.980> are<00:46:08.400> like<00:46:08.579> Gaff<00:46:09.119> Forks<00:46:09.540> if 00:46:09.890 --> 00:46:09.900 align:start position:0% that actually are like Gaff Forks if 00:46:09.900 --> 00:46:11.569 align:start position:0% that actually are like Gaff Forks if some<00:46:10.260> changes 00:46:11.569 --> 00:46:11.579 align:start position:0% some changes 00:46:11.579 --> 00:46:14.210 align:start position:0% some changes and<00:46:12.180> was<00:46:12.480> it<00:46:12.720> somehow<00:46:13.079> like<00:46:13.440> useful<00:46:13.800> for<00:46:14.099> you 00:46:14.210 --> 00:46:14.220 align:start position:0% and was it somehow like useful for you 00:46:14.220 --> 00:46:16.069 align:start position:0% and was it somehow like useful for you to<00:46:14.520> take<00:46:14.760> a<00:46:14.940> look<00:46:15.060> on<00:46:15.240> it<00:46:15.300> are<00:46:15.599> you<00:46:15.780> somehow 00:46:16.069 --> 00:46:16.079 align:start position:0% to take a look on it are you somehow 00:46:16.079 --> 00:46:17.930 align:start position:0% to take a look on it are you somehow monitoring<00:46:16.619> what<00:46:16.859> is<00:46:17.040> happening<00:46:17.339> over<00:46:17.700> there 00:46:17.930 --> 00:46:17.940 align:start position:0% monitoring what is happening over there 00:46:17.940 --> 00:46:21.890 align:start position:0% monitoring what is happening over there and<00:46:18.540> if<00:46:19.319> so<00:46:19.560> were<00:46:20.280> there<00:46:20.520> any<00:46:20.700> cases<00:46:21.359> when<00:46:21.660> you 00:46:21.890 --> 00:46:21.900 align:start position:0% and if so were there any cases when you 00:46:21.900 --> 00:46:25.130 align:start position:0% and if so were there any cases when you somehow<00:46:22.440> wasn't<00:46:23.040> like<00:46:23.339> inspired<00:46:24.060> by<00:46:24.599> some 00:46:25.130 --> 00:46:25.140 align:start position:0% somehow wasn't like inspired by some 00:46:25.140 --> 00:46:26.990 align:start position:0% somehow wasn't like inspired by some changes<00:46:25.560> in<00:46:25.859> these<00:46:26.040> clients<00:46:26.339> and<00:46:26.579> you<00:46:26.700> want 00:46:26.990 --> 00:46:27.000 align:start position:0% changes in these clients and you want 00:46:27.000 --> 00:46:29.270 align:start position:0% changes in these clients and you want like<00:46:27.240> to<00:46:27.420> bring<00:46:27.540> them<00:46:27.780> into<00:46:28.020> the<00:46:28.260> Gap<00:46:28.560> like<00:46:29.160> the 00:46:29.270 --> 00:46:29.280 align:start position:0% like to bring them into the Gap like the 00:46:29.280 --> 00:46:31.910 align:start position:0% like to bring them into the Gap like the original<00:46:29.460> Gap<00:46:30.000> and<00:46:30.480> like<00:46:30.960> some<00:46:31.440> cases<00:46:31.740> when 00:46:31.910 --> 00:46:31.920 align:start position:0% original Gap and like some cases when 00:46:31.920 --> 00:46:35.030 align:start position:0% original Gap and like some cases when some<00:46:32.160> bugs<00:46:32.520> were<00:46:32.640> opened<00:46:33.180> in<00:46:33.720> like<00:46:34.200> get<00:46:34.560> Forks 00:46:35.030 --> 00:46:35.040 align:start position:0% some bugs were opened in like get Forks 00:46:35.040 --> 00:46:36.890 align:start position:0% some bugs were opened in like get Forks that<00:46:35.220> actually<00:46:35.520> are<00:46:35.880> pretty<00:46:36.119> close<00:46:36.359> to<00:46:36.720> the 00:46:36.890 --> 00:46:36.900 align:start position:0% that actually are pretty close to the 00:46:36.900 --> 00:46:39.589 align:start position:0% that actually are pretty close to the original<00:46:37.260> Gap<00:46:37.920> as<00:46:38.220> well<00:46:38.339> one<00:46:39.060> one<00:46:39.240> thing<00:46:39.420> I 00:46:39.589 --> 00:46:39.599 align:start position:0% original Gap as well one one thing I 00:46:39.599 --> 00:46:42.170 align:start position:0% original Gap as well one one thing I would<00:46:39.720> wanted<00:46:40.079> to<00:46:40.319> say<00:46:40.500> is<00:46:40.619> about<00:46:40.859> bugs<00:46:41.640> so 00:46:42.170 --> 00:46:42.180 align:start position:0% would wanted to say is about bugs so 00:46:42.180 --> 00:46:44.690 align:start position:0% would wanted to say is about bugs so whenever<00:46:42.480> we<00:46:42.720> find<00:46:42.960> a<00:46:43.200> buck<00:46:43.319> in<00:46:43.560> gas<00:46:43.740> then 00:46:44.690 --> 00:46:44.700 align:start position:0% whenever we find a buck in gas then 00:46:44.700 --> 00:46:48.250 align:start position:0% whenever we find a buck in gas then there's<00:46:45.000> usually<00:46:45.619> a<00:46:46.619> lot<00:46:46.740> of<00:46:46.920> different<00:46:47.220> uh 00:46:48.250 --> 00:46:48.260 align:start position:0% there's usually a lot of different uh 00:46:48.260 --> 00:46:52.130 align:start position:0% there's usually a lot of different uh clients<00:46:49.460> that<00:46:50.460> are 00:46:52.130 --> 00:46:52.140 align:start position:0% clients that are 00:46:52.140 --> 00:46:55.550 align:start position:0% clients that are um<00:46:52.260> that<00:46:52.980> are<00:46:53.160> also<00:46:53.579> vulnerable<00:46:54.540> to<00:46:54.839> this 00:46:55.550 --> 00:46:55.560 align:start position:0% um that are also vulnerable to this 00:46:55.560 --> 00:46:57.589 align:start position:0% um that are also vulnerable to this and<00:46:56.339> so<00:46:56.640> we<00:46:56.819> are 00:46:57.589 --> 00:46:57.599 align:start position:0% and so we are 00:46:57.599 --> 00:47:00.109 align:start position:0% and so we are looking<00:46:58.260> into<00:46:58.619> them<00:46:58.920> and<00:46:59.280> making<00:46:59.579> sure<00:46:59.880> that 00:47:00.109 --> 00:47:00.119 align:start position:0% looking into them and making sure that 00:47:00.119 --> 00:47:03.470 align:start position:0% looking into them and making sure that they<00:47:00.300> are<00:47:00.420> not<00:47:00.619> uh<00:47:01.619> before<00:47:01.859> we<00:47:02.220> actually 00:47:03.470 --> 00:47:03.480 align:start position:0% they are not uh before we actually 00:47:03.480 --> 00:47:04.130 align:start position:0% they are not uh before we actually um 00:47:04.130 --> 00:47:04.140 align:start position:0% um 00:47:04.140 --> 00:47:08.089 align:start position:0% um uh<00:47:04.800> before<00:47:05.040> we<00:47:05.400> actually<00:47:05.660> uh<00:47:06.660> fix<00:47:07.020> the<00:47:07.619> bug<00:47:07.800> and 00:47:08.089 --> 00:47:08.099 align:start position:0% uh before we actually uh fix the bug and 00:47:08.099 --> 00:47:10.309 align:start position:0% uh before we actually uh fix the bug and and<00:47:08.280> publish<00:47:08.940> it 00:47:10.309 --> 00:47:10.319 align:start position:0% and publish it 00:47:10.319 --> 00:47:13.010 align:start position:0% and publish it um<00:47:10.440> the<00:47:10.859> problem<00:47:11.040> there<00:47:11.400> is 00:47:13.010 --> 00:47:13.020 align:start position:0% um the problem there is 00:47:13.020 --> 00:47:15.530 align:start position:0% um the problem there is in<00:47:13.440> which<00:47:13.680> in<00:47:14.040> which<00:47:14.280> layer<00:47:14.760> ones<00:47:15.119> are<00:47:15.420> we 00:47:15.530 --> 00:47:15.540 align:start position:0% in which in which layer ones are we 00:47:15.540 --> 00:47:18.050 align:start position:0% in which in which layer ones are we going<00:47:15.660> to<00:47:15.839> look<00:47:16.020> and<00:47:16.920> are<00:47:17.220> we<00:47:17.339> only<00:47:17.640> going<00:47:17.940> to 00:47:18.050 --> 00:47:18.060 align:start position:0% going to look and are we only going to 00:47:18.060 --> 00:47:22.309 align:start position:0% going to look and are we only going to look<00:47:18.300> at<00:47:18.780> uh<00:47:19.680> ethereum<00:47:20.579> Alliance<00:47:21.240> uh<00:47:22.020> layer 00:47:22.309 --> 00:47:22.319 align:start position:0% look at uh ethereum Alliance uh layer 00:47:22.319 --> 00:47:26.030 align:start position:0% look at uh ethereum Alliance uh layer ones<00:47:22.619> or<00:47:23.520> or<00:47:23.819> not<00:47:24.180> and<00:47:24.720> so<00:47:25.020> I<00:47:25.319> think<00:47:25.440> the<00:47:25.680> way<00:47:25.800> we 00:47:26.030 --> 00:47:26.040 align:start position:0% ones or or not and so I think the way we 00:47:26.040 --> 00:47:30.170 align:start position:0% ones or or not and so I think the way we handled<00:47:26.339> it<00:47:26.640> up<00:47:27.420> until<00:47:27.780> now<00:47:28.260> is<00:47:28.680> that<00:47:28.980> we 00:47:30.170 --> 00:47:30.180 align:start position:0% handled it up until now is that we 00:47:30.180 --> 00:47:35.329 align:start position:0% handled it up until now is that we um<00:47:30.380> kinda<00:47:31.380> look<00:47:31.920> in<00:47:32.160> the<00:47:32.280> biggest<00:47:32.400> ones<00:47:33.000> and 00:47:35.329 --> 00:47:35.339 align:start position:0% um kinda look in the biggest ones and 00:47:35.339 --> 00:47:36.829 align:start position:0% um kinda look in the biggest ones and um 00:47:36.829 --> 00:47:36.839 align:start position:0% um 00:47:36.839 --> 00:47:40.849 align:start position:0% um just<00:47:37.680> sent<00:47:37.980> them<00:47:38.280> an<00:47:39.180> email<00:47:39.359> that<00:47:39.839> hey<00:47:40.140> you 00:47:40.849 --> 00:47:40.859 align:start position:0% just sent them an email that hey you 00:47:40.859 --> 00:47:43.490 align:start position:0% just sent them an email that hey you should<00:47:41.040> expect<00:47:41.460> an<00:47:42.119> announcement 00:47:43.490 --> 00:47:43.500 align:start position:0% should expect an announcement 00:47:43.500 --> 00:47:46.730 align:start position:0% should expect an announcement at<00:47:44.400> a<00:47:44.579> certain<00:47:44.700> point<00:47:45.060> and<00:47:45.960> then<00:47:46.380> we're<00:47:46.560> going 00:47:46.730 --> 00:47:46.740 align:start position:0% at a certain point and then we're going 00:47:46.740 --> 00:47:49.250 align:start position:0% at a certain point and then we're going to<00:47:46.859> make<00:47:47.040> a<00:47:47.220> public<00:47:47.339> announcement<00:47:48.000> because<00:47:48.960> we 00:47:49.250 --> 00:47:49.260 align:start position:0% to make a public announcement because we 00:47:49.260 --> 00:47:50.630 align:start position:0% to make a public announcement because we don't<00:47:49.380> want<00:47:49.500> to<00:47:49.619> be<00:47:49.740> king<00:47:49.920> makers<00:47:50.339> we<00:47:50.520> don't 00:47:50.630 --> 00:47:50.640 align:start position:0% don't want to be king makers we don't 00:47:50.640 --> 00:47:54.230 align:start position:0% don't want to be king makers we don't want<00:47:50.819> to<00:47:51.060> say<00:47:51.440> which<00:47:52.440> client<00:47:53.040> which<00:47:54.000> which 00:47:54.230 --> 00:47:54.240 align:start position:0% want to say which client which which 00:47:54.240 --> 00:47:58.190 align:start position:0% want to say which client which which Fork<00:47:55.140> gets<00:47:55.740> the<00:47:55.980> bucks<00:47:56.400> first<00:47:56.900> over<00:47:57.900> over 00:47:58.190 --> 00:47:58.200 align:start position:0% Fork gets the bucks first over over 00:47:58.200 --> 00:48:00.050 align:start position:0% Fork gets the bucks first over over another<00:47:58.500> Fork 00:48:00.050 --> 00:48:00.060 align:start position:0% another Fork 00:48:00.060 --> 00:48:00.970 align:start position:0% another Fork um 00:48:00.970 --> 00:48:00.980 align:start position:0% um 00:48:00.980 --> 00:48:04.970 align:start position:0% um and<00:48:01.980> yeah<00:48:02.579> there's<00:48:03.240> also<00:48:03.540> been<00:48:03.660> bugs<00:48:04.319> that 00:48:04.970 --> 00:48:04.980 align:start position:0% and yeah there's also been bugs that 00:48:04.980 --> 00:48:07.069 align:start position:0% and yeah there's also been bugs that have<00:48:05.099> been<00:48:05.400> exploited<00:48:05.940> on<00:48:06.180> other<00:48:06.359> networks 00:48:07.069 --> 00:48:07.079 align:start position:0% have been exploited on other networks 00:48:07.079 --> 00:48:12.550 align:start position:0% have been exploited on other networks before<00:48:08.040> they<00:48:08.520> were<00:48:09.020> exploited<00:48:10.020> on<00:48:10.200> ethereum 00:48:12.550 --> 00:48:12.560 align:start position:0% before they were exploited on ethereum 00:48:12.560 --> 00:48:14.630 align:start position:0% before they were exploited on ethereum and<00:48:13.560> uh 00:48:14.630 --> 00:48:14.640 align:start position:0% and uh 00:48:14.640 --> 00:48:16.910 align:start position:0% and uh we're<00:48:15.240> kind<00:48:15.420> of<00:48:15.480> like 00:48:16.910 --> 00:48:16.920 align:start position:0% we're kind of like 00:48:16.920 --> 00:48:19.670 align:start position:0% we're kind of like not<00:48:17.400> really<00:48:17.760> monitoring<00:48:18.359> the<00:48:18.660> the<00:48:19.260> other 00:48:19.670 --> 00:48:19.680 align:start position:0% not really monitoring the the other 00:48:19.680 --> 00:48:21.349 align:start position:0% not really monitoring the the other networks<00:48:20.220> but 00:48:21.349 --> 00:48:21.359 align:start position:0% networks but 00:48:21.359 --> 00:48:24.230 align:start position:0% networks but we're<00:48:21.900> trying<00:48:22.140> to<00:48:22.500> be<00:48:22.680> in<00:48:22.920> with<00:48:23.220> in<00:48:23.640> on<00:48:23.940> good 00:48:24.230 --> 00:48:24.240 align:start position:0% we're trying to be in with in on good 00:48:24.240 --> 00:48:26.690 align:start position:0% we're trying to be in with in on good terms<00:48:24.660> with<00:48:24.960> uh<00:48:25.260> with<00:48:25.500> the<00:48:25.619> other<00:48:25.740> client<00:48:26.160> uh 00:48:26.690 --> 00:48:26.700 align:start position:0% terms with uh with the other client uh 00:48:26.700 --> 00:48:29.390 align:start position:0% terms with uh with the other client uh client<00:48:27.000> devs 00:48:29.390 --> 00:48:29.400 align:start position:0% client devs 00:48:29.400 --> 00:48:31.670 align:start position:0% client devs I<00:48:29.579> guess<00:48:29.760> one<00:48:30.119> one<00:48:30.540> kind<00:48:31.200> of<00:48:31.260> satellite 00:48:31.670 --> 00:48:31.680 align:start position:0% I guess one one kind of satellite 00:48:31.680 --> 00:48:34.430 align:start position:0% I guess one one kind of satellite question<00:48:32.220> here<00:48:32.700> would<00:48:33.000> be<00:48:33.180> that<00:48:33.480> uh 00:48:34.430 --> 00:48:34.440 align:start position:0% question here would be that uh 00:48:34.440 --> 00:48:38.290 align:start position:0% question here would be that uh way<00:48:35.099> back<00:48:35.339> there<00:48:35.579> were<00:48:35.760> a<00:48:35.940> lot<00:48:36.180> of<00:48:36.660> um 00:48:38.290 --> 00:48:38.300 align:start position:0% way back there were a lot of um 00:48:38.300 --> 00:48:42.050 align:start position:0% way back there were a lot of um drama<00:48:39.300> around<00:48:39.960> when<00:48:40.500> it<00:48:41.460> turned<00:48:41.640> out<00:48:41.700> that<00:48:41.880> we 00:48:42.050 --> 00:48:42.060 align:start position:0% drama around when it turned out that we 00:48:42.060 --> 00:48:43.730 align:start position:0% drama around when it turned out that we fixed<00:48:42.359> a<00:48:42.480> bug<00:48:42.599> and<00:48:42.900> we<00:48:43.140> haven't<00:48:43.200> necessarily 00:48:43.730 --> 00:48:43.740 align:start position:0% fixed a bug and we haven't necessarily 00:48:43.740 --> 00:48:45.530 align:start position:0% fixed a bug and we haven't necessarily announced<00:48:44.040> it<00:48:44.160> other<00:48:44.339> networks<00:48:44.940> had<00:48:45.300> a 00:48:45.530 --> 00:48:45.540 align:start position:0% announced it other networks had a 00:48:45.540 --> 00:48:48.050 align:start position:0% announced it other networks had a problem<00:48:45.839> with<00:48:46.140> it<00:48:46.319> people<00:48:47.099> very<00:48:47.460> often<00:48:47.760> asked 00:48:48.050 --> 00:48:48.060 align:start position:0% problem with it people very often asked 00:48:48.060 --> 00:48:49.790 align:start position:0% problem with it people very often asked us<00:48:48.119> why<00:48:48.359> don't<00:48:48.540> we<00:48:48.720> have<00:48:48.900> a<00:48:49.079> standardized<00:48:49.619> way 00:48:49.790 --> 00:48:49.800 align:start position:0% us why don't we have a standardized way 00:48:49.800 --> 00:48:51.349 align:start position:0% us why don't we have a standardized way of<00:48:50.160> reporting<00:48:50.640> bugs<00:48:51.000> reporting 00:48:51.349 --> 00:48:51.359 align:start position:0% of reporting bugs reporting 00:48:51.359 --> 00:48:54.349 align:start position:0% of reporting bugs reporting vulnerabilities<00:48:52.020> have<00:48:52.859> um<00:48:52.859> usually<00:48:53.520> what<00:48:54.119> big 00:48:54.349 --> 00:48:54.359 align:start position:0% vulnerabilities have um usually what big 00:48:54.359 --> 00:48:55.970 align:start position:0% vulnerabilities have um usually what big web<00:48:54.599> 2<00:48:54.839> companies<00:48:55.200> do<00:48:55.380> is<00:48:55.500> that<00:48:55.680> they<00:48:55.859> have 00:48:55.970 --> 00:48:55.980 align:start position:0% web 2 companies do is that they have 00:48:55.980 --> 00:48:58.130 align:start position:0% web 2 companies do is that they have their<00:48:56.160> own<00:48:56.280> little<00:48:56.460> private<00:48:56.880> consortia<00:48:57.420> where 00:48:58.130 --> 00:48:58.140 align:start position:0% their own little private consortia where 00:48:58.140 --> 00:48:59.809 align:start position:0% their own little private consortia where they<00:48:58.319> share<00:48:58.560> bugs<00:48:58.980> and<00:48:59.220> then<00:48:59.339> when<00:48:59.579> they 00:48:59.809 --> 00:48:59.819 align:start position:0% they share bugs and then when they 00:48:59.819 --> 00:49:01.730 align:start position:0% they share bugs and then when they publish<00:49:00.119> it<00:49:00.300> everybody<00:49:00.599> in<00:49:01.020> that<00:49:01.200> consortia 00:49:01.730 --> 00:49:01.740 align:start position:0% publish it everybody in that consortia 00:49:01.740 --> 00:49:03.290 align:start position:0% publish it everybody in that consortia already<00:49:01.980> updated 00:49:03.290 --> 00:49:03.300 align:start position:0% already updated 00:49:03.300 --> 00:49:06.230 align:start position:0% already updated and<00:49:03.900> we<00:49:04.140> people<00:49:04.380> were<00:49:04.859> always<00:49:05.579> very<00:49:06.060> very 00:49:06.230 --> 00:49:06.240 align:start position:0% and we people were always very very 00:49:06.240 --> 00:49:09.290 align:start position:0% and we people were always very very vocal<00:49:06.900> that<00:49:07.079> we<00:49:07.260> should<00:49:07.380> do<00:49:07.619> the<00:49:07.800> same<00:49:07.980> thing 00:49:09.290 --> 00:49:09.300 align:start position:0% vocal that we should do the same thing 00:49:09.300 --> 00:49:10.970 align:start position:0% vocal that we should do the same thing we<00:49:09.780> kind<00:49:09.900> of<00:49:10.020> felt<00:49:10.260> that<00:49:10.380> that's<00:49:10.619> a<00:49:10.859> bit 00:49:10.970 --> 00:49:10.980 align:start position:0% we kind of felt that that's a bit 00:49:10.980 --> 00:49:13.609 align:start position:0% we kind of felt that that's a bit problematic<00:49:11.700> because<00:49:12.060> in<00:49:12.839> in<00:49:13.079> the<00:49:13.260> blockchain 00:49:13.609 --> 00:49:13.619 align:start position:0% problematic because in in the blockchain 00:49:13.619 --> 00:49:15.829 align:start position:0% problematic because in in the blockchain world<00:49:13.980> if<00:49:14.579> you<00:49:14.700> if<00:49:14.940> we<00:49:15.119> were<00:49:15.180> to<00:49:15.359> create<00:49:15.480> one<00:49:15.720> of 00:49:15.829 --> 00:49:15.839 align:start position:0% world if you if we were to create one of 00:49:15.839 --> 00:49:18.349 align:start position:0% world if you if we were to create one of these<00:49:16.020> consortia<00:49:17.099> it's<00:49:17.640> not<00:49:17.760> really<00:49:18.000> clear 00:49:18.349 --> 00:49:18.359 align:start position:0% these consortia it's not really clear 00:49:18.359 --> 00:49:21.230 align:start position:0% these consortia it's not really clear whether<00:49:19.140> everybody<00:49:19.500> in<00:49:20.339> that<00:49:20.520> group<00:49:20.760> would<00:49:21.119> be 00:49:21.230 --> 00:49:21.240 align:start position:0% whether everybody in that group would be 00:49:21.240 --> 00:49:23.690 align:start position:0% whether everybody in that group would be friendly<00:49:21.780> or<00:49:22.079> how<00:49:22.260> friendly<00:49:22.619> they<00:49:22.800> would<00:49:23.040> be 00:49:23.690 --> 00:49:23.700 align:start position:0% friendly or how friendly they would be 00:49:23.700 --> 00:49:25.849 align:start position:0% friendly or how friendly they would be so<00:49:24.180> usually<00:49:24.480> what<00:49:24.720> we<00:49:24.900> try<00:49:25.079> to<00:49:25.200> do<00:49:25.440> every<00:49:25.619> time 00:49:25.849 --> 00:49:25.859 align:start position:0% so usually what we try to do every time 00:49:25.859 --> 00:49:29.569 align:start position:0% so usually what we try to do every time we<00:49:26.040> found<00:49:26.280> a<00:49:26.880> hairy<00:49:27.660> vulnerability<00:49:28.140> or<00:49:28.560> bug<00:49:28.740> is 00:49:29.569 --> 00:49:29.579 align:start position:0% we found a hairy vulnerability or bug is 00:49:29.579 --> 00:49:31.790 align:start position:0% we found a hairy vulnerability or bug is that<00:49:29.819> depending<00:49:30.420> on<00:49:30.780> the<00:49:30.900> nature<00:49:31.319> we<00:49:31.680> always 00:49:31.790 --> 00:49:31.800 align:start position:0% that depending on the nature we always 00:49:31.800 --> 00:49:33.530 align:start position:0% that depending on the nature we always try<00:49:32.160> to 00:49:33.530 --> 00:49:33.540 align:start position:0% try to 00:49:33.540 --> 00:49:36.650 align:start position:0% try to announce<00:49:34.260> external<00:49:34.859> people<00:49:35.099> or<00:49:35.700> give<00:49:36.420> enough 00:49:36.650 --> 00:49:36.660 align:start position:0% announce external people or give enough 00:49:36.660 --> 00:49:38.630 align:start position:0% announce external people or give enough details<00:49:37.200> to<00:49:37.440> external<00:49:37.859> people<00:49:38.099> external 00:49:38.630 --> 00:49:38.640 align:start position:0% details to external people external 00:49:38.640 --> 00:49:41.329 align:start position:0% details to external people external teams<00:49:39.000> to<00:49:39.540> minimize<00:49:39.960> any<00:49:40.380> potential<00:49:40.920> damage 00:49:41.329 --> 00:49:41.339 align:start position:0% teams to minimize any potential damage 00:49:41.339 --> 00:49:44.089 align:start position:0% teams to minimize any potential damage now<00:49:42.300> for<00:49:42.540> example<00:49:42.900> in<00:49:43.020> the<00:49:43.140> case<00:49:43.440> of<00:49:43.619> ethereum 00:49:44.089 --> 00:49:44.099 align:start position:0% now for example in the case of ethereum 00:49:44.099 --> 00:49:46.670 align:start position:0% now for example in the case of ethereum what<00:49:44.760> we<00:49:44.940> did<00:49:45.119> is<00:49:45.300> that<00:49:45.540> if<00:49:45.780> we<00:49:46.020> knew<00:49:46.260> that<00:49:46.440> we 00:49:46.670 --> 00:49:46.680 align:start position:0% what we did is that if we knew that we 00:49:46.680 --> 00:49:49.490 align:start position:0% what we did is that if we knew that we are<00:49:46.920> going<00:49:47.040> to<00:49:47.220> fix<00:49:47.460> something<00:49:47.880> that<00:49:48.720> um 00:49:49.490 --> 00:49:49.500 align:start position:0% are going to fix something that um 00:49:49.500 --> 00:49:52.190 align:start position:0% are going to fix something that um that<00:49:50.099> only<00:49:50.280> affects<00:49:50.760> miners<00:49:51.180> or<00:49:51.660> if<00:49:52.079> the 00:49:52.190 --> 00:49:52.200 align:start position:0% that only affects miners or if the 00:49:52.200 --> 00:49:55.490 align:start position:0% that only affects miners or if the miners<00:49:52.619> are<00:49:53.160> good<00:49:53.579> then<00:49:54.240> the<00:49:54.960> words<00:49:55.079> that<00:49:55.380> have 00:49:55.490 --> 00:49:55.500 align:start position:0% miners are good then the words that have 00:49:55.500 --> 00:49:57.470 align:start position:0% miners are good then the words that have cap<00:49:55.800> happens<00:49:56.099> for<00:49:56.460> average<00:49:56.700> user<00:49:57.180> is<00:49:57.240> that 00:49:57.470 --> 00:49:57.480 align:start position:0% cap happens for average user is that 00:49:57.480 --> 00:49:59.630 align:start position:0% cap happens for average user is that their<00:49:57.540> note<00:49:57.780> crashes<00:49:58.260> usually<00:49:59.160> what<00:49:59.339> we<00:49:59.520> did 00:49:59.630 --> 00:49:59.640 align:start position:0% their note crashes usually what we did 00:49:59.640 --> 00:50:01.970 align:start position:0% their note crashes usually what we did is<00:49:59.819> that<00:50:00.000> we<00:50:00.240> just<00:50:00.480> gently<00:50:01.140> pinged<00:50:01.619> a<00:50:01.800> couple 00:50:01.970 --> 00:50:01.980 align:start position:0% is that we just gently pinged a couple 00:50:01.980 --> 00:50:05.150 align:start position:0% is that we just gently pinged a couple of<00:50:02.220> the<00:50:02.520> bigger<00:50:02.819> mining<00:50:03.180> pools<00:50:03.540> that<00:50:04.200> hey<00:50:04.500> we 00:50:05.150 --> 00:50:05.160 align:start position:0% of the bigger mining pools that hey we 00:50:05.160 --> 00:50:07.490 align:start position:0% of the bigger mining pools that hey we will<00:50:05.339> release<00:50:05.520> a<00:50:05.819> release<00:50:06.060> you<00:50:06.960> really<00:50:07.260> want 00:50:07.490 --> 00:50:07.500 align:start position:0% will release a release you really want 00:50:07.500 --> 00:50:09.290 align:start position:0% will release a release you really want to<00:50:07.680> be<00:50:07.859> on<00:50:08.160> this<00:50:08.339> release 00:50:09.290 --> 00:50:09.300 align:start position:0% to be on this release 00:50:09.300 --> 00:50:13.010 align:start position:0% to be on this release nothing<00:50:09.839> more<00:50:10.200> just<00:50:10.740> a<00:50:10.920> gentle<00:50:11.280> reminder<00:50:11.700> that 00:50:13.010 --> 00:50:13.020 align:start position:0% nothing more just a gentle reminder that 00:50:13.020 --> 00:50:15.290 align:start position:0% nothing more just a gentle reminder that it<00:50:13.380> contains<00:50:13.800> something<00:50:14.040> that<00:50:14.460> you<00:50:14.640> want<00:50:14.940> to 00:50:15.290 --> 00:50:15.300 align:start position:0% it contains something that you want to 00:50:15.300 --> 00:50:18.589 align:start position:0% it contains something that you want to run<00:50:15.720> and<00:50:16.619> by<00:50:16.920> having<00:50:17.400> the<00:50:17.940> majority<00:50:18.240> of<00:50:18.480> the 00:50:18.589 --> 00:50:18.599 align:start position:0% run and by having the majority of the 00:50:18.599 --> 00:50:21.170 align:start position:0% run and by having the majority of the hash<00:50:18.839> power<00:50:19.140> updated<00:50:19.980> the<00:50:20.520> network<00:50:20.640> is<00:50:20.940> kind 00:50:21.170 --> 00:50:21.180 align:start position:0% hash power updated the network is kind 00:50:21.180 --> 00:50:22.490 align:start position:0% hash power updated the network is kind of<00:50:21.300> safe 00:50:22.490 --> 00:50:22.500 align:start position:0% of safe 00:50:22.500 --> 00:50:24.470 align:start position:0% of safe and<00:50:22.980> there's<00:50:23.220> not<00:50:23.400> much<00:50:23.579> damage<00:50:24.000> that<00:50:24.240> can<00:50:24.359> be 00:50:24.470 --> 00:50:24.480 align:start position:0% and there's not much damage that can be 00:50:24.480 --> 00:50:26.450 align:start position:0% and there's not much damage that can be done<00:50:24.660> but<00:50:25.200> this<00:50:25.380> is<00:50:25.560> kind<00:50:25.680> of<00:50:25.800> a<00:50:25.980> completely 00:50:26.450 --> 00:50:26.460 align:start position:0% done but this is kind of a completely 00:50:26.460 --> 00:50:29.809 align:start position:0% done but this is kind of a completely arbitrary<00:50:27.180> bug<00:50:28.140> by<00:50:28.380> bug<00:50:28.619> decision<00:50:29.099> on<00:50:29.460> how 00:50:29.809 --> 00:50:29.819 align:start position:0% arbitrary bug by bug decision on how 00:50:29.819 --> 00:50:32.089 align:start position:0% arbitrary bug by bug decision on how best<00:50:30.000> to<00:50:30.240> proceed<00:50:30.540> how<00:50:30.780> best<00:50:31.260> to<00:50:31.440> minimize<00:50:31.800> any 00:50:32.089 --> 00:50:32.099 align:start position:0% best to proceed how best to minimize any 00:50:32.099 --> 00:50:34.790 align:start position:0% best to proceed how best to minimize any damage<00:50:32.520> to<00:50:32.819> anybody<00:50:33.420> in<00:50:33.839> the<00:50:34.020> either<00:50:34.440> in<00:50:34.680> the 00:50:34.790 --> 00:50:34.800 align:start position:0% damage to anybody in the either in the 00:50:34.800 --> 00:50:37.630 align:start position:0% damage to anybody in the either in the ethereum<00:50:35.099> network<00:50:35.280> or<00:50:35.760> or<00:50:36.240> the<00:50:36.540> external 00:50:37.630 --> 00:50:37.640 align:start position:0% ethereum network or or the external 00:50:37.640 --> 00:50:40.490 align:start position:0% ethereum network or or the external blockchains<00:50:38.640> that<00:50:38.760> use<00:50:38.940> ethereum<00:50:39.540> so<00:50:40.260> we 00:50:40.490 --> 00:50:40.500 align:start position:0% blockchains that use ethereum so we 00:50:40.500 --> 00:50:43.569 align:start position:0% blockchains that use ethereum so we really<00:50:41.160> try<00:50:41.520> to<00:50:41.700> be<00:50:41.940> as<00:50:42.300> friendly<00:50:42.780> as<00:50:43.079> possible 00:50:43.569 --> 00:50:43.579 align:start position:0% really try to be as friendly as possible 00:50:43.579 --> 00:50:46.069 align:start position:0% really try to be as friendly as possible within<00:50:44.579> the<00:50:44.700> limit<00:50:44.819> of<00:50:45.180> keeping<00:50:45.540> the<00:50:45.720> ethereum 00:50:46.069 --> 00:50:46.079 align:start position:0% within the limit of keeping the ethereum 00:50:46.079 --> 00:50:47.329 align:start position:0% within the limit of keeping the ethereum network<00:50:46.319> live 00:50:47.329 --> 00:50:47.339 align:start position:0% network live 00:50:47.339 --> 00:50:50.510 align:start position:0% network live hey<00:50:47.880> it's<00:50:48.000> me<00:50:48.180> again<00:50:48.500> uh<00:50:49.500> I<00:50:49.680> just<00:50:49.800> want<00:50:49.980> to<00:50:50.160> add 00:50:50.510 --> 00:50:50.520 align:start position:0% hey it's me again uh I just want to add 00:50:50.520 --> 00:50:53.930 align:start position:0% hey it's me again uh I just want to add that<00:50:51.359> um<00:50:51.839> apart<00:50:52.380> from<00:50:52.559> the<00:50:52.859> people<00:50:53.099> sitting 00:50:53.930 --> 00:50:53.940 align:start position:0% that um apart from the people sitting 00:50:53.940 --> 00:50:57.049 align:start position:0% that um apart from the people sitting here<00:50:54.180> and<00:50:54.720> some<00:50:54.960> of<00:50:55.079> us<00:50:55.200> off<00:50:55.680> stage<00:50:55.980> we<00:50:56.760> also 00:50:57.049 --> 00:50:57.059 align:start position:0% here and some of us off stage we also 00:50:57.059 --> 00:50:58.910 align:start position:0% here and some of us off stage we also have<00:50:57.240> people<00:50:57.720> watching<00:50:58.200> the<00:50:58.319> stream<00:50:58.500> from<00:50:58.740> the 00:50:58.910 --> 00:50:58.920 align:start position:0% have people watching the stream from the 00:50:58.920 --> 00:51:00.770 align:start position:0% have people watching the stream from the team<00:50:59.099> I<00:50:59.880> want<00:51:00.000> to<00:51:00.119> give<00:51:00.180> a<00:51:00.359> shout<00:51:00.540> out<00:51:00.599> to 00:51:00.770 --> 00:51:00.780 align:start position:0% team I want to give a shout out to 00:51:00.780 --> 00:51:03.109 align:start position:0% team I want to give a shout out to Martin<00:51:00.960> who<00:51:01.440> is<00:51:01.559> from<00:51:01.980> far<00:51:02.160> away<00:51:02.339> who<00:51:02.880> couldn't 00:51:03.109 --> 00:51:03.119 align:start position:0% Martin who is from far away who couldn't 00:51:03.119 --> 00:51:04.849 align:start position:0% Martin who is from far away who couldn't make<00:51:03.420> it<00:51:03.540> unfortunately 00:51:04.849 --> 00:51:04.859 align:start position:0% make it unfortunately 00:51:04.859 --> 00:51:06.950 align:start position:0% make it unfortunately and<00:51:05.640> uh 00:51:06.950 --> 00:51:06.960 align:start position:0% and uh 00:51:06.960 --> 00:51:08.870 align:start position:0% and uh yeah 00:51:08.870 --> 00:51:08.880 align:start position:0% yeah 00:51:08.880 --> 00:51:10.970 align:start position:0% yeah uh<00:51:09.540> who's<00:51:09.720> from<00:51:10.140> far<00:51:10.319> away<00:51:10.500> trying<00:51:10.800> to 00:51:10.970 --> 00:51:10.980 align:start position:0% uh who's from far away trying to 00:51:10.980 --> 00:51:13.370 align:start position:0% uh who's from far away trying to contribute<00:51:11.339> to<00:51:11.460> the<00:51:11.640> conversation<00:51:12.059> so<00:51:12.960> uh 00:51:13.370 --> 00:51:13.380 align:start position:0% contribute to the conversation so uh 00:51:13.380 --> 00:51:15.950 align:start position:0% contribute to the conversation so uh some<00:51:13.559> somebody<00:51:13.800> asked<00:51:14.579> about<00:51:14.700> the<00:51:15.300> remote<00:51:15.540> DB 00:51:15.950 --> 00:51:15.960 align:start position:0% some somebody asked about the remote DB 00:51:15.960 --> 00:51:19.670 align:start position:0% some somebody asked about the remote DB flag<00:51:16.400> uh<00:51:17.400> I<00:51:17.640> I<00:51:17.819> have<00:51:18.059> an<00:51:18.180> answer<00:51:18.359> to<00:51:18.720> that 00:51:19.670 --> 00:51:19.680 align:start position:0% flag uh I I have an answer to that 00:51:19.680 --> 00:51:22.849 align:start position:0% flag uh I I have an answer to that um<00:51:19.740> so<00:51:20.579> it's<00:51:20.880> basically 00:51:22.849 --> 00:51:22.859 align:start position:0% um so it's basically 00:51:22.859 --> 00:51:27.349 align:start position:0% um so it's basically um<00:51:22.920> it<00:51:23.880> does<00:51:24.119> the<00:51:24.480> low<00:51:24.839> level<00:51:25.079> uh<00:51:25.940> database<00:51:26.940> get 00:51:27.349 --> 00:51:27.359 align:start position:0% um it does the low level uh database get 00:51:27.359 --> 00:51:30.770 align:start position:0% um it does the low level uh database get over<00:51:28.020> RPC<00:51:28.740> so<00:51:29.640> basically<00:51:29.940> you<00:51:30.240> can<00:51:30.359> have<00:51:30.480> like 00:51:30.770 --> 00:51:30.780 align:start position:0% over RPC so basically you can have like 00:51:30.780 --> 00:51:34.010 align:start position:0% over RPC so basically you can have like what<00:51:30.960> you<00:51:31.260> have<00:51:31.500> a<00:51:31.680> node<00:51:32.160> on<00:51:32.940> a<00:51:33.059> server<00:51:33.300> and<00:51:33.839> you 00:51:34.010 --> 00:51:34.020 align:start position:0% what you have a node on a server and you 00:51:34.020 --> 00:51:38.089 align:start position:0% what you have a node on a server and you can<00:51:34.339> have<00:51:35.339> your<00:51:35.640> like<00:51:35.940> local<00:51:36.180> node 00:51:38.089 --> 00:51:38.099 align:start position:0% can have your like local node 00:51:38.099 --> 00:51:41.150 align:start position:0% can have your like local node um connect<00:51:38.460> to<00:51:39.240> that<00:51:39.480> to<00:51:39.839> the<00:51:39.960> remote<00:51:40.140> one<00:51:40.500> for 00:51:41.150 --> 00:51:41.160 align:start position:0% um connect to that to the remote one for 00:51:41.160 --> 00:51:43.609 align:start position:0% um connect to that to the remote one for some<00:51:41.339> like<00:51:41.520> only<00:51:41.819> read<00:51:42.480> upper<00:51:42.960> operations<00:51:43.319> so 00:51:43.609 --> 00:51:43.619 align:start position:0% some like only read upper operations so 00:51:43.619 --> 00:51:46.270 align:start position:0% some like only read upper operations so for<00:51:43.740> example<00:51:43.980> if<00:51:44.220> you<00:51:44.339> do<00:51:44.520> DB<00:51:45.300> metadata 00:51:46.270 --> 00:51:46.280 align:start position:0% for example if you do DB metadata 00:51:46.280 --> 00:51:49.730 align:start position:0% for example if you do DB metadata command<00:51:47.280> locally<00:51:47.880> then<00:51:48.420> it<00:51:48.720> would<00:51:48.900> basically 00:51:49.730 --> 00:51:49.740 align:start position:0% command locally then it would basically 00:51:49.740 --> 00:51:51.589 align:start position:0% command locally then it would basically get<00:51:50.040> give<00:51:50.280> you<00:51:50.460> the<00:51:50.640> metadata<00:51:51.180> of<00:51:51.359> the<00:51:51.480> remote 00:51:51.589 --> 00:51:51.599 align:start position:0% get give you the metadata of the remote 00:51:51.599 --> 00:51:54.170 align:start position:0% get give you the metadata of the remote node<00:51:52.020> yeah<00:51:52.740> that's<00:51:53.160> it 00:51:54.170 --> 00:51:54.180 align:start position:0% node yeah that's it 00:51:54.180 --> 00:51:58.970 align:start position:0% node yeah that's it uh<00:51:54.660> do<00:51:54.839> you<00:51:55.020> see<00:51:55.400> snapshots<00:51:56.400> as<00:51:57.119> the<00:51:57.740> get<00:51:58.740> as 00:51:58.970 --> 00:51:58.980 align:start position:0% uh do you see snapshots as the get as 00:51:58.980 --> 00:52:00.710 align:start position:0% uh do you see snapshots as the get as get<00:51:59.220> solution<00:51:59.579> for<00:51:59.880> the<00:52:00.059> state<00:52:00.240> database 00:52:00.710 --> 00:52:00.720 align:start position:0% get solution for the state database 00:52:00.720 --> 00:52:04.609 align:start position:0% get solution for the state database layout<00:52:01.079> for<00:52:01.380> the<00:52:01.500> first<00:52:01.740> UB<00:52:02.099> feature<00:52:02.700> yes 00:52:04.609 --> 00:52:04.619 align:start position:0% layout for the first UB feature yes 00:52:04.619 --> 00:52:06.770 align:start position:0% layout for the first UB feature yes what<00:52:05.280> one<00:52:05.460> question<00:52:05.760> we<00:52:06.119> are<00:52:06.240> in<00:52:06.420> this 00:52:06.770 --> 00:52:06.780 align:start position:0% what one question we are in this 00:52:06.780 --> 00:52:09.290 align:start position:0% what one question we are in this beautiful<00:52:07.020> Columbia<00:52:07.619> South<00:52:08.220> America<00:52:08.460> Bogota 00:52:09.290 --> 00:52:09.300 align:start position:0% beautiful Columbia South America Bogota 00:52:09.300 --> 00:52:11.270 align:start position:0% beautiful Columbia South America Bogota I<00:52:10.020> just<00:52:10.140> want<00:52:10.260> to<00:52:10.440> know<00:52:10.500> what<00:52:10.800> each<00:52:10.980> of<00:52:11.160> you 00:52:11.270 --> 00:52:11.280 align:start position:0% I just want to know what each of you 00:52:11.280 --> 00:52:15.290 align:start position:0% I just want to know what each of you have<00:52:11.700> like<00:52:12.180> most<00:52:12.660> loved<00:52:13.140> about<00:52:13.380> Bogota<00:52:13.920> so<00:52:14.400> far 00:52:15.290 --> 00:52:15.300 align:start position:0% have like most loved about Bogota so far 00:52:15.300 --> 00:52:19.430 align:start position:0% have like most loved about Bogota so far hiking<00:52:16.140> in<00:52:16.319> the<00:52:16.500> rain<00:52:16.619> at<00:52:17.099> the<00:52:17.220> waterfalls 00:52:19.430 --> 00:52:19.440 align:start position:0% hiking in the rain at the waterfalls 00:52:19.440 --> 00:52:23.030 align:start position:0% hiking in the rain at the waterfalls I<00:52:20.160> actually<00:52:20.359> I<00:52:21.359> actually<00:52:22.200> really<00:52:22.440> liked 00:52:23.030 --> 00:52:23.040 align:start position:0% I actually I actually really liked 00:52:23.040 --> 00:52:26.630 align:start position:0% I actually I actually really liked working<00:52:23.280> from<00:52:23.640> here<00:52:24.260> it<00:52:25.260> was<00:52:25.740> it<00:52:26.220> was<00:52:26.400> really 00:52:26.630 --> 00:52:26.640 align:start position:0% working from here it was it was really 00:52:26.640 --> 00:52:30.049 align:start position:0% working from here it was it was really fun<00:52:27.059> with<00:52:27.359> like<00:52:27.720> we<00:52:28.020> had<00:52:28.200> some<00:52:28.680> workshops<00:52:29.339> a 00:52:30.049 --> 00:52:30.059 align:start position:0% fun with like we had some workshops a 00:52:30.059 --> 00:52:33.650 align:start position:0% fun with like we had some workshops a day<00:52:30.420> with<00:52:30.660> like<00:52:30.960> all<00:52:31.079> of<00:52:31.260> the<00:52:31.440> client<00:52:32.059> devs<00:52:33.059> and 00:52:33.650 --> 00:52:33.660 align:start position:0% day with like all of the client devs and 00:52:33.660 --> 00:52:35.870 align:start position:0% day with like all of the client devs and today<00:52:33.780> we<00:52:34.140> had<00:52:34.260> a<00:52:34.500> really<00:52:34.619> nice<00:52:34.859> working<00:52:35.160> uh 00:52:35.870 --> 00:52:35.880 align:start position:0% today we had a really nice working uh 00:52:35.880 --> 00:52:37.680 align:start position:0% today we had a really nice working uh session<00:52:36.240> in<00:52:36.660> the<00:52:36.780> morning 00:52:37.680 --> 00:52:37.690 align:start position:0% session in the morning 00:52:37.690 --> 00:52:39.650 align:start position:0% session in the morning [Laughter] 00:52:39.650 --> 00:52:39.660 align:start position:0% [Laughter] 00:52:39.660 --> 00:52:41.750 align:start position:0% [Laughter] yes<00:52:40.140> if<00:52:40.319> you<00:52:40.440> haven't<00:52:40.559> noticed<00:52:40.920> Marius<00:52:41.400> is<00:52:41.640> the 00:52:41.750 --> 00:52:41.760 align:start position:0% yes if you haven't noticed Marius is the 00:52:41.760 --> 00:52:45.410 align:start position:0% yes if you haven't noticed Marius is the new<00:52:41.880> workaholic<00:52:42.480> on<00:52:42.660> the<00:52:42.839> team<00:52:43.460> it<00:52:44.460> was<00:52:44.640> it<00:52:45.240> was 00:52:45.410 --> 00:52:45.420 align:start position:0% new workaholic on the team it was it was 00:52:45.420 --> 00:52:47.809 align:start position:0% new workaholic on the team it was it was really<00:52:45.599> nice<00:52:45.839> just<00:52:46.140> getting<00:52:46.319> the<00:52:46.740> the<00:52:47.040> people 00:52:47.809 --> 00:52:47.819 align:start position:0% really nice just getting the the people 00:52:47.819 --> 00:52:50.569 align:start position:0% really nice just getting the the people in<00:52:48.720> the<00:52:48.839> room<00:52:48.960> that<00:52:49.200> need<00:52:49.319> to<00:52:49.440> be<00:52:49.559> in<00:52:49.740> the<00:52:49.859> room 00:52:50.569 --> 00:52:50.579 align:start position:0% in the room that need to be in the room 00:52:50.579 --> 00:52:53.569 align:start position:0% in the room that need to be in the room and<00:52:51.240> work<00:52:51.480> on<00:52:51.720> some<00:52:51.960> of<00:52:52.140> the<00:52:52.440> uh<00:52:53.099> interesting 00:52:53.569 --> 00:52:53.579 align:start position:0% and work on some of the uh interesting 00:52:53.579 --> 00:52:55.970 align:start position:0% and work on some of the uh interesting things<00:52:53.819> that<00:52:54.119> are<00:52:54.240> coming<00:52:54.420> up<00:52:54.660> and<00:52:55.500> I'm<00:52:55.740> really 00:52:55.970 --> 00:52:55.980 align:start position:0% things that are coming up and I'm really 00:52:55.980 --> 00:52:58.010 align:start position:0% things that are coming up and I'm really really<00:52:56.280> really<00:52:56.460> excited<00:52:57.240> about<00:52:57.480> the<00:52:57.900> new 00:52:58.010 --> 00:52:58.020 align:start position:0% really really excited about the new 00:52:58.020 --> 00:53:00.470 align:start position:0% really really excited about the new stuff<00:52:58.380> that<00:52:58.559> is<00:52:58.680> coming<00:52:58.859> for<00:52:59.160> ethereum 00:53:00.470 --> 00:53:00.480 align:start position:0% stuff that is coming for ethereum 00:53:00.480 --> 00:53:02.650 align:start position:0% stuff that is coming for ethereum I<00:53:01.020> also<00:53:01.260> enjoyed<00:53:01.619> the<00:53:01.740> hike<00:53:01.920> quite<00:53:02.280> a<00:53:02.400> bit 00:53:02.650 --> 00:53:02.660 align:start position:0% I also enjoyed the hike quite a bit 00:53:02.660 --> 00:53:05.030 align:start position:0% I also enjoyed the hike quite a bit that's<00:53:03.660> the<00:53:03.839> only<00:53:03.960> time<00:53:04.140> I've<00:53:04.380> got<00:53:04.619> a<00:53:04.859> hotel 00:53:05.030 --> 00:53:05.040 align:start position:0% that's the only time I've got a hotel 00:53:05.040 --> 00:53:07.849 align:start position:0% that's the only time I've got a hotel besides<00:53:05.579> coming<00:53:05.760> to<00:53:06.059> here<00:53:06.240> so<00:53:06.780> I<00:53:07.680> heard 00:53:07.849 --> 00:53:07.859 align:start position:0% besides coming to here so I heard 00:53:07.859 --> 00:53:10.670 align:start position:0% besides coming to here so I heard different<00:53:08.160> math<00:53:08.579> I<00:53:08.819> heard<00:53:09.000> different 00:53:10.670 --> 00:53:10.680 align:start position:0% different math I heard different 00:53:10.680 --> 00:53:12.950 align:start position:0% different math I heard different I<00:53:11.400> also<00:53:11.579> really<00:53:11.640> like<00:53:11.880> the<00:53:12.000> energy<00:53:12.180> at<00:53:12.540> Devcon 00:53:12.950 --> 00:53:12.960 align:start position:0% I also really like the energy at Devcon 00:53:12.960 --> 00:53:14.390 align:start position:0% I also really like the energy at Devcon it's<00:53:13.319> been<00:53:13.440> a<00:53:13.559> while<00:53:13.619> since<00:53:13.859> we've<00:53:14.099> all<00:53:14.220> been 00:53:14.390 --> 00:53:14.400 align:start position:0% it's been a while since we've all been 00:53:14.400 --> 00:53:15.950 align:start position:0% it's been a while since we've all been together<00:53:14.579> and<00:53:14.940> I<00:53:15.059> think<00:53:15.180> it's<00:53:15.300> easy<00:53:15.540> to<00:53:15.780> forget 00:53:15.950 --> 00:53:15.960 align:start position:0% together and I think it's easy to forget 00:53:15.960 --> 00:53:18.349 align:start position:0% together and I think it's easy to forget that<00:53:16.859> the<00:53:17.099> community<00:53:17.220> is<00:53:17.520> so<00:53:17.700> large<00:53:17.940> now<00:53:18.180> and 00:53:18.349 --> 00:53:18.359 align:start position:0% that the community is so large now and 00:53:18.359 --> 00:53:19.490 align:start position:0% that the community is so large now and there's<00:53:18.480> so<00:53:18.660> many<00:53:18.780> people<00:53:18.900> excited<00:53:19.380> about 00:53:19.490 --> 00:53:19.500 align:start position:0% there's so many people excited about 00:53:19.500 --> 00:53:21.349 align:start position:0% there's so many people excited about this<00:53:19.680> protocol<00:53:20.040> so<00:53:20.700> I<00:53:20.880> found<00:53:21.000> that<00:53:21.180> very 00:53:21.349 --> 00:53:21.359 align:start position:0% this protocol so I found that very 00:53:21.359 --> 00:53:24.589 align:start position:0% this protocol so I found that very energizing<00:53:21.960> for<00:53:22.200> myself<00:53:22.460> uh<00:53:23.460> Jared<00:53:23.880> tells<00:53:24.480> me 00:53:24.589 --> 00:53:24.599 align:start position:0% energizing for myself uh Jared tells me 00:53:24.599 --> 00:53:26.990 align:start position:0% energizing for myself uh Jared tells me the<00:53:25.079> food<00:53:25.260> the<00:53:25.619> food 00:53:26.990 --> 00:53:27.000 align:start position:0% the food the food 00:53:27.000 --> 00:53:29.690 align:start position:0% the food the food uh<00:53:27.780> no<00:53:28.020> yeah<00:53:28.260> it's<00:53:28.680> uh 00:53:29.690 --> 00:53:29.700 align:start position:0% uh no yeah it's uh 00:53:29.700 --> 00:53:32.829 align:start position:0% uh no yeah it's uh the<00:53:30.180> food<00:53:30.480> has<00:53:30.720> been<00:53:30.900> nice<00:53:31.140> uh 00:53:32.829 --> 00:53:32.839 align:start position:0% the food has been nice uh 00:53:32.839 --> 00:53:36.650 align:start position:0% the food has been nice uh I<00:53:33.839> like<00:53:33.960> the<00:53:34.140> hotel<00:53:34.380> as<00:53:34.800> well 00:53:36.650 --> 00:53:36.660 align:start position:0% I like the hotel as well 00:53:36.660 --> 00:53:39.589 align:start position:0% I like the hotel as well uh<00:53:37.200> no<00:53:37.440> but<00:53:37.619> uh<00:53:37.920> I<00:53:38.160> don't<00:53:38.220> know<00:53:38.339> uh<00:53:38.760> I<00:53:39.000> I<00:53:39.180> saw<00:53:39.420> the 00:53:39.589 --> 00:53:39.599 align:start position:0% uh no but uh I don't know uh I I saw the 00:53:39.599 --> 00:53:41.390 align:start position:0% uh no but uh I don't know uh I I saw the the<00:53:39.780> center<00:53:40.020> the<00:53:40.380> other<00:53:40.740> day<00:53:40.859> when<00:53:41.040> we<00:53:41.220> went 00:53:41.390 --> 00:53:41.400 align:start position:0% the center the other day when we went 00:53:41.400 --> 00:53:44.390 align:start position:0% the center the other day when we went when<00:53:42.359> uh<00:53:42.599> Luke's<00:53:43.140> looks<00:53:43.800> quite<00:53:43.980> interesting 00:53:44.390 --> 00:53:44.400 align:start position:0% when uh Luke's looks quite interesting 00:53:44.400 --> 00:53:47.030 align:start position:0% when uh Luke's looks quite interesting uh<00:53:45.359> I<00:53:45.599> guess<00:53:45.720> we<00:53:46.079> will<00:53:46.260> Explore<00:53:46.559> More<00:53:46.740> this 00:53:47.030 --> 00:53:47.040 align:start position:0% uh I guess we will Explore More this 00:53:47.040 --> 00:53:49.190 align:start position:0% uh I guess we will Explore More this weekend<00:53:47.220> after<00:53:47.579> the<00:53:47.819> work<00:53:48.000> is<00:53:48.180> done<00:53:48.359> one<00:53:49.079> last 00:53:49.190 --> 00:53:49.200 align:start position:0% weekend after the work is done one last 00:53:49.200 --> 00:53:51.049 align:start position:0% weekend after the work is done one last question<00:53:49.500> who<00:53:49.920> from<00:53:50.160> the<00:53:50.280> team<00:53:50.460> is<00:53:50.700> not<00:53:50.880> on 00:53:51.049 --> 00:53:51.059 align:start position:0% question who from the team is not on 00:53:51.059 --> 00:53:53.569 align:start position:0% question who from the team is not on stage<00:53:51.300> today<00:53:51.540> besides<00:53:52.079> Cena<00:53:52.859> who<00:53:53.220> from<00:53:53.460> the 00:53:53.569 --> 00:53:53.579 align:start position:0% stage today besides Cena who from the 00:53:53.579 --> 00:53:55.490 align:start position:0% stage today besides Cena who from the team<00:53:53.700> is<00:53:53.940> not<00:53:54.119> on<00:53:54.240> the<00:53:54.420> stage 00:53:55.490 --> 00:53:55.500 align:start position:0% team is not on the stage 00:53:55.500 --> 00:53:59.750 align:start position:0% team is not on the stage we<00:53:56.040> have<00:53:56.300> Jared<00:53:57.440> beside<00:53:58.440> you<00:53:58.559> so<00:53:59.339> shout<00:53:59.640> out 00:53:59.750 --> 00:53:59.760 align:start position:0% we have Jared beside you so shout out 00:53:59.760 --> 00:54:01.609 align:start position:0% we have Jared beside you so shout out huge<00:54:00.180> shout<00:54:00.359> out<00:54:00.420> to 00:54:01.609 --> 00:54:01.619 align:start position:0% huge shout out to 00:54:01.619 --> 00:54:05.630 align:start position:0% huge shout out to actually<00:54:02.040> in<00:54:02.520> the<00:54:02.579> back<00:54:02.900> uh<00:54:03.900> Felix<00:54:04.559> who's<00:54:05.040> uh 00:54:05.630 --> 00:54:05.640 align:start position:0% actually in the back uh Felix who's uh 00:54:05.640 --> 00:54:10.430 align:start position:0% actually in the back uh Felix who's uh in<00:54:06.240> Berlin<00:54:06.599> Martins<00:54:07.559> in<00:54:07.980> Stockholm<00:54:08.520> and<00:54:09.240> and<00:54:09.660> a 00:54:10.430 --> 00:54:10.440 align:start position:0% in Berlin Martins in Stockholm and and a 00:54:10.440 --> 00:54:12.829 align:start position:0% in Berlin Martins in Stockholm and and a giant<00:54:10.740> uh<00:54:11.339> actually<00:54:11.579> a<00:54:11.880> giant<00:54:12.180> shout<00:54:12.420> out<00:54:12.540> to 00:54:12.829 --> 00:54:12.839 align:start position:0% giant uh actually a giant shout out to 00:54:12.839 --> 00:54:17.329 align:start position:0% giant uh actually a giant shout out to Gary<00:54:13.579> who<00:54:14.579> wasn't<00:54:15.180> able<00:54:15.660> to<00:54:16.020> make<00:54:16.380> it<00:54:16.920> to<00:54:17.160> any 00:54:17.329 --> 00:54:17.339 align:start position:0% Gary who wasn't able to make it to any 00:54:17.339 --> 00:54:20.030 align:start position:0% Gary who wasn't able to make it to any of<00:54:17.520> the<00:54:17.640> guest<00:54:17.940> meetings<00:54:18.420> for<00:54:19.020> the<00:54:19.200> past<00:54:19.440> three 00:54:20.030 --> 00:54:20.040 align:start position:0% of the guest meetings for the past three 00:54:20.040 --> 00:54:22.609 align:start position:0% of the guest meetings for the past three plus<00:54:20.339> years<00:54:20.640> due<00:54:21.540> to<00:54:21.660> him<00:54:21.839> being<00:54:22.079> stuck<00:54:22.380> in 00:54:22.609 --> 00:54:22.619 align:start position:0% plus years due to him being stuck in 00:54:22.619 --> 00:54:25.190 align:start position:0% plus years due to him being stuck in China<00:54:22.800> and<00:54:23.460> the<00:54:23.700> Chinese<00:54:23.880> rules<00:54:24.540> on<00:54:24.839> leaving 00:54:25.190 --> 00:54:25.200 align:start position:0% China and the Chinese rules on leaving 00:54:25.200 --> 00:54:27.230 align:start position:0% China and the Chinese rules on leaving the<00:54:25.440> country<00:54:25.559> and<00:54:25.859> coming<00:54:26.280> back<00:54:26.460> due<00:54:26.640> to<00:54:26.819> kovid 00:54:27.230 --> 00:54:27.240 align:start position:0% the country and coming back due to kovid 00:54:27.240 --> 00:54:30.109 align:start position:0% the country and coming back due to kovid are<00:54:27.359> super<00:54:27.540> super<00:54:27.720> strict<00:54:28.140> so<00:54:28.640> and<00:54:29.640> insane 00:54:30.109 --> 00:54:30.119 align:start position:0% are super super strict so and insane 00:54:30.119 --> 00:54:33.650 align:start position:0% are super super strict so and insane shout<00:54:30.780> out<00:54:30.839> to<00:54:31.140> to<00:54:31.500> him<00:54:31.800> for<00:54:32.280> still<00:54:32.940> tolerating 00:54:33.650 --> 00:54:33.660 align:start position:0% shout out to to him for still tolerating 00:54:33.660 --> 00:54:35.450 align:start position:0% shout out to to him for still tolerating us<00:54:33.900> and<00:54:34.140> working<00:54:34.319> for<00:54:34.619> us<00:54:34.740> without<00:54:34.980> all<00:54:35.339> the 00:54:35.450 --> 00:54:35.460 align:start position:0% us and working for us without all the 00:54:35.460 --> 00:54:38.569 align:start position:0% us and working for us without all the upsides<00:54:36.000> of<00:54:36.359> uh<00:54:36.720> having<00:54:37.260> the<00:54:37.559> fun<00:54:37.740> like<00:54:38.280> we<00:54:38.460> are 00:54:38.569 --> 00:54:38.579 align:start position:0% upsides of uh having the fun like we are 00:54:38.579 --> 00:54:39.890 align:start position:0% upsides of uh having the fun like we are having<00:54:38.760> now 00:54:39.890 --> 00:54:39.900 align:start position:0% having now 00:54:39.900 --> 00:54:41.750 align:start position:0% having now big<00:54:40.380> round<00:54:40.559> of<00:54:40.740> applause<00:54:41.040> guys<00:54:41.220> thank<00:54:41.520> you<00:54:41.640> so 00:54:41.750 --> 00:54:41.760 align:start position:0% big round of applause guys thank you so 00:54:41.760 --> 00:54:43.940 align:start position:0% big round of applause guys thank you so much