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:15.550 align:start position:0% [Music] 00:00:15.550 --> 00:00:15.560 align:start position:0% 00:00:15.560 --> 00:00:18.410 align:start position:0% oops<00:00:16.560> can<00:00:16.920> I<00:00:17.160> think<00:00:17.580> I<00:00:17.760> left<00:00:17.880> my<00:00:18.060> water<00:00:18.240> over 00:00:18.410 --> 00:00:18.420 align:start position:0% oops can I think I left my water over 00:00:18.420 --> 00:00:20.269 align:start position:0% oops can I think I left my water over there<00:00:18.539> can<00:00:18.720> somebody<00:00:18.900> grab<00:00:19.260> that 00:00:20.269 --> 00:00:20.279 align:start position:0% there can somebody grab that 00:00:20.279 --> 00:00:22.670 align:start position:0% there can somebody grab that thank<00:00:20.699> you<00:00:20.820> everybody<00:00:20.939> who's<00:00:21.480> uh<00:00:22.020> here<00:00:22.439> to 00:00:22.670 --> 00:00:22.680 align:start position:0% thank you everybody who's uh here to 00:00:22.680 --> 00:00:24.590 align:start position:0% thank you everybody who's uh here to listen<00:00:23.220> to<00:00:23.400> this<00:00:23.640> talk 00:00:24.590 --> 00:00:24.600 align:start position:0% listen to this talk 00:00:24.600 --> 00:00:26.269 align:start position:0% listen to this talk um 00:00:26.269 --> 00:00:26.279 align:start position:0% um 00:00:26.279 --> 00:00:28.370 align:start position:0% um honored<00:00:26.880> to<00:00:27.000> be<00:00:27.119> speaking<00:00:27.359> at<00:00:27.539> Devcon<00:00:27.960> I<00:00:28.199> never 00:00:28.370 --> 00:00:28.380 align:start position:0% honored to be speaking at Devcon I never 00:00:28.380 --> 00:00:29.990 align:start position:0% honored to be speaking at Devcon I never really<00:00:28.619> imagined<00:00:28.980> I<00:00:29.160> would<00:00:29.340> be<00:00:29.460> doing<00:00:29.580> that<00:00:29.760> a 00:00:29.990 --> 00:00:30.000 align:start position:0% really imagined I would be doing that a 00:00:30.000 --> 00:00:31.189 align:start position:0% really imagined I would be doing that a couple<00:00:30.119> years<00:00:30.300> ago<00:00:30.539> when<00:00:30.720> I<00:00:30.840> first<00:00:30.960> got<00:00:31.080> into 00:00:31.189 --> 00:00:31.199 align:start position:0% couple years ago when I first got into 00:00:31.199 --> 00:00:33.590 align:start position:0% couple years ago when I first got into ethereum<00:00:31.740> so<00:00:32.040> uh 00:00:33.590 --> 00:00:33.600 align:start position:0% ethereum so uh 00:00:33.600 --> 00:00:35.810 align:start position:0% ethereum so uh honored<00:00:34.260> to<00:00:34.320> be<00:00:34.440> here<00:00:34.620> and 00:00:35.810 --> 00:00:35.820 align:start position:0% honored to be here and 00:00:35.820 --> 00:00:39.110 align:start position:0% honored to be here and um<00:00:35.880> happy<00:00:36.600> to<00:00:36.920> educate<00:00:37.920> or<00:00:38.340> communicate<00:00:38.940> what 00:00:39.110 --> 00:00:39.120 align:start position:0% um happy to educate or communicate what 00:00:39.120 --> 00:00:40.310 align:start position:0% um happy to educate or communicate what we've<00:00:39.239> been<00:00:39.360> working<00:00:39.540> on<00:00:39.660> here<00:00:39.899> with<00:00:40.140> the 00:00:40.310 --> 00:00:40.320 align:start position:0% we've been working on here with the 00:00:40.320 --> 00:00:41.869 align:start position:0% we've been working on here with the protocol<00:00:40.559> Guild 00:00:41.869 --> 00:00:41.879 align:start position:0% protocol Guild 00:00:41.879 --> 00:00:43.549 align:start position:0% protocol Guild so<00:00:42.239> the<00:00:42.300> title<00:00:42.600> of<00:00:42.660> the<00:00:42.780> talk<00:00:42.899> is<00:00:43.140> funding 00:00:43.549 --> 00:00:43.559 align:start position:0% so the title of the talk is funding 00:00:43.559 --> 00:00:45.709 align:start position:0% so the title of the talk is funding ethereum<00:00:43.860> with<00:00:44.040> the<00:00:44.100> protocol<00:00:44.340> Guild<00:00:44.640> uh<00:00:45.300> like 00:00:45.709 --> 00:00:45.719 align:start position:0% ethereum with the protocol Guild uh like 00:00:45.719 --> 00:00:47.450 align:start position:0% ethereum with the protocol Guild uh like Karthik<00:00:46.079> mentioned<00:00:46.440> my<00:00:46.620> name<00:00:46.739> is<00:00:46.860> Trent<00:00:47.280> van 00:00:47.450 --> 00:00:47.460 align:start position:0% Karthik mentioned my name is Trent van 00:00:47.460 --> 00:00:50.389 align:start position:0% Karthik mentioned my name is Trent van apps<00:00:47.940> I<00:00:48.420> am<00:00:48.660> a<00:00:48.899> member<00:00:49.140> of<00:00:49.320> this<00:00:49.440> Guild<00:00:49.680> however 00:00:50.389 --> 00:00:50.399 align:start position:0% apps I am a member of this Guild however 00:00:50.399 --> 00:00:53.209 align:start position:0% apps I am a member of this Guild however I<00:00:50.640> do<00:00:50.760> also<00:00:51.120> work<00:00:51.360> for<00:00:51.719> the<00:00:52.500> EF<00:00:52.800> on<00:00:53.039> the 00:00:53.209 --> 00:00:53.219 align:start position:0% I do also work for the EF on the 00:00:53.219 --> 00:00:56.750 align:start position:0% I do also work for the EF on the protocol<00:00:53.520> support<00:00:53.820> team<00:00:54.180> which<00:00:54.960> is<00:00:55.199> uh 00:00:56.750 --> 00:00:56.760 align:start position:0% protocol support team which is uh 00:00:56.760 --> 00:00:59.330 align:start position:0% protocol support team which is uh we<00:00:57.239> we<00:00:57.300> work<00:00:57.719> on<00:00:57.899> network<00:00:58.140> upgrades<00:00:58.739> and 00:00:59.330 --> 00:00:59.340 align:start position:0% we we work on network upgrades and 00:00:59.340 --> 00:01:01.250 align:start position:0% we we work on network upgrades and generally<00:01:00.239> coordinating<00:01:00.660> the<00:01:00.899> ecosystem 00:01:01.250 --> 00:01:01.260 align:start position:0% generally coordinating the ecosystem 00:01:01.260 --> 00:01:04.009 align:start position:0% generally coordinating the ecosystem around<00:01:01.620> where<00:01:02.520> the<00:01:02.820> protocol<00:01:03.180> is<00:01:03.420> going<00:01:03.600> and 00:01:04.009 --> 00:01:04.019 align:start position:0% around where the protocol is going and 00:01:04.019 --> 00:01:05.329 align:start position:0% around where the protocol is going and how<00:01:04.199> we<00:01:04.320> can<00:01:04.440> improve<00:01:04.739> this<00:01:04.920> coordination 00:01:05.329 --> 00:01:05.339 align:start position:0% how we can improve this coordination 00:01:05.339 --> 00:01:06.890 align:start position:0% how we can improve this coordination process 00:01:06.890 --> 00:01:06.900 align:start position:0% process 00:01:06.900 --> 00:01:10.010 align:start position:0% process so<00:01:07.560> a<00:01:08.100> brief<00:01:08.460> intro<00:01:08.820> I'm<00:01:09.240> assuming<00:01:09.600> most<00:01:09.900> of 00:01:10.010 --> 00:01:10.020 align:start position:0% so a brief intro I'm assuming most of 00:01:10.020 --> 00:01:12.109 align:start position:0% so a brief intro I'm assuming most of you<00:01:10.080> are<00:01:10.320> aware<00:01:10.560> of<00:01:10.680> this<00:01:10.799> but<00:01:11.100> uh<00:01:11.520> never<00:01:11.760> hurts 00:01:12.109 --> 00:01:12.119 align:start position:0% you are aware of this but uh never hurts 00:01:12.119 --> 00:01:13.550 align:start position:0% you are aware of this but uh never hurts to<00:01:12.299> step<00:01:12.479> back<00:01:12.659> and<00:01:12.840> think<00:01:13.020> about<00:01:13.140> what<00:01:13.439> we're 00:01:13.550 --> 00:01:13.560 align:start position:0% to step back and think about what we're 00:01:13.560 --> 00:01:16.130 align:start position:0% to step back and think about what we're what<00:01:14.040> this<00:01:14.220> topic<00:01:14.580> is<00:01:14.700> so<00:01:15.000> ethereum<00:01:15.720> generally 00:01:16.130 --> 00:01:16.140 align:start position:0% what this topic is so ethereum generally 00:01:16.140 --> 00:01:18.770 align:start position:0% what this topic is so ethereum generally is<00:01:16.619> a<00:01:16.979> globally<00:01:17.220> distributed<00:01:17.700> computer<00:01:17.939> that 00:01:18.770 --> 00:01:18.780 align:start position:0% is a globally distributed computer that 00:01:18.780 --> 00:01:21.350 align:start position:0% is a globally distributed computer that anyone<00:01:19.080> can<00:01:19.260> use<00:01:19.439> anyone<00:01:19.979> can<00:01:20.159> access 00:01:21.350 --> 00:01:21.360 align:start position:0% anyone can use anyone can access 00:01:21.360 --> 00:01:24.170 align:start position:0% anyone can use anyone can access um<00:01:21.560> uh<00:01:22.560> people<00:01:22.740> can<00:01:22.979> deploy<00:01:23.280> contracts<00:01:23.880> to<00:01:24.060> it 00:01:24.170 --> 00:01:24.180 align:start position:0% um uh people can deploy contracts to it 00:01:24.180 --> 00:01:26.390 align:start position:0% um uh people can deploy contracts to it they<00:01:24.479> can<00:01:24.600> send<00:01:24.780> transactions<00:01:25.619> and<00:01:26.040> interact 00:01:26.390 --> 00:01:26.400 align:start position:0% they can send transactions and interact 00:01:26.400 --> 00:01:28.429 align:start position:0% they can send transactions and interact with<00:01:26.520> it<00:01:26.700> anywhere<00:01:27.060> around<00:01:27.240> the<00:01:27.479> world 00:01:28.429 --> 00:01:28.439 align:start position:0% with it anywhere around the world 00:01:28.439 --> 00:01:30.649 align:start position:0% with it anywhere around the world this<00:01:29.040> means<00:01:29.280> that<00:01:29.340> ethereum<00:01:29.820> the<00:01:30.000> network<00:01:30.180> so 00:01:30.649 --> 00:01:30.659 align:start position:0% this means that ethereum the network so 00:01:30.659 --> 00:01:33.410 align:start position:0% this means that ethereum the network so mainnet<00:01:31.560> is<00:01:31.799> a<00:01:32.040> screenshot<00:01:32.460> from<00:01:32.700> etherscan 00:01:33.410 --> 00:01:33.420 align:start position:0% mainnet is a screenshot from etherscan 00:01:33.420 --> 00:01:34.190 align:start position:0% mainnet is a screenshot from etherscan there 00:01:34.190 --> 00:01:34.200 align:start position:0% there 00:01:34.200 --> 00:01:37.069 align:start position:0% there and<00:01:34.920> this<00:01:35.280> is<00:01:35.400> a<00:01:35.579> public<00:01:35.700> good<00:01:36.000> that<00:01:36.420> users<00:01:36.900> of 00:01:37.069 --> 00:01:37.079 align:start position:0% and this is a public good that users of 00:01:37.079 --> 00:01:38.390 align:start position:0% and this is a public good that users of the<00:01:37.200> network 00:01:38.390 --> 00:01:38.400 align:start position:0% the network 00:01:38.400 --> 00:01:42.530 align:start position:0% the network um<00:01:38.880> can<00:01:39.479> depend<00:01:39.840> on<00:01:40.020> and<00:01:40.740> use<00:01:41.540> throughout 00:01:42.530 --> 00:01:42.540 align:start position:0% um can depend on and use throughout 00:01:42.540 --> 00:01:44.749 align:start position:0% um can depend on and use throughout their<00:01:42.840> lives<00:01:43.140> they<00:01:43.860> can<00:01:44.040> trust<00:01:44.400> that<00:01:44.579> it's 00:01:44.749 --> 00:01:44.759 align:start position:0% their lives they can trust that it's 00:01:44.759 --> 00:01:46.730 align:start position:0% their lives they can trust that it's going<00:01:44.939> to<00:01:45.060> be<00:01:45.180> a<00:01:45.720> resource<00:01:46.079> for<00:01:46.200> them<00:01:46.380> nobody 00:01:46.730 --> 00:01:46.740 align:start position:0% going to be a resource for them nobody 00:01:46.740 --> 00:01:48.410 align:start position:0% going to be a resource for them nobody can<00:01:46.920> stop<00:01:47.100> them<00:01:47.280> from<00:01:47.460> using<00:01:47.759> it<00:01:47.880> this<00:01:48.180> is 00:01:48.410 --> 00:01:48.420 align:start position:0% can stop them from using it this is 00:01:48.420 --> 00:01:50.149 align:start position:0% can stop them from using it this is stretching<00:01:49.079> in<00:01:49.200> the<00:01:49.380> definition<00:01:49.680> of<00:01:49.979> public 00:01:50.149 --> 00:01:50.159 align:start position:0% stretching in the definition of public 00:01:50.159 --> 00:01:51.410 align:start position:0% stretching in the definition of public it<00:01:50.460> a<00:01:50.579> little<00:01:50.640> bit<00:01:50.759> because<00:01:51.000> we<00:01:51.299> have 00:01:51.410 --> 00:01:51.420 align:start position:0% it a little bit because we have 00:01:51.420 --> 00:01:53.810 align:start position:0% it a little bit because we have transaction<00:01:51.899> fees<00:01:52.259> but<00:01:52.500> generally 00:01:53.810 --> 00:01:53.820 align:start position:0% transaction fees but generally 00:01:53.820 --> 00:01:55.670 align:start position:0% transaction fees but generally um<00:01:53.880> we<00:01:54.240> can<00:01:54.540> we<00:01:54.840> can<00:01:54.960> understand<00:01:55.140> it<00:01:55.439> to<00:01:55.560> be 00:01:55.670 --> 00:01:55.680 align:start position:0% um we can we can understand it to be 00:01:55.680 --> 00:01:57.770 align:start position:0% um we can we can understand it to be this<00:01:55.860> and<00:01:56.460> if<00:01:56.579> we<00:01:56.759> take<00:01:56.880> a<00:01:57.060> step<00:01:57.180> back<00:01:57.420> looking 00:01:57.770 --> 00:01:57.780 align:start position:0% this and if we take a step back looking 00:01:57.780 --> 00:02:00.770 align:start position:0% this and if we take a step back looking at<00:01:58.020> the<00:01:58.200> yellow<00:01:58.320> paper<00:01:58.939> this<00:01:59.939> is<00:02:00.060> the<00:02:00.299> ethereum 00:02:00.770 --> 00:02:00.780 align:start position:0% at the yellow paper this is the ethereum 00:02:00.780 --> 00:02:03.590 align:start position:0% at the yellow paper this is the ethereum virtual<00:02:01.079> machine<00:02:01.320> this<00:02:01.799> is<00:02:01.920> a<00:02:02.520> another<00:02:02.939> public 00:02:03.590 --> 00:02:03.600 align:start position:0% virtual machine this is a another public 00:02:03.600 --> 00:02:06.410 align:start position:0% virtual machine this is a another public good<00:02:03.960> that<00:02:04.500> ethereum<00:02:05.460> developers<00:02:06.000> core 00:02:06.410 --> 00:02:06.420 align:start position:0% good that ethereum developers core 00:02:06.420 --> 00:02:08.270 align:start position:0% good that ethereum developers core contributors<00:02:06.899> they<00:02:07.079> maintain<00:02:07.439> and<00:02:08.099> many 00:02:08.270 --> 00:02:08.280 align:start position:0% contributors they maintain and many 00:02:08.280 --> 00:02:10.910 align:start position:0% contributors they maintain and many other<00:02:08.459> chains<00:02:09.060> uh<00:02:09.720> besides<00:02:10.140> ethereum<00:02:10.619> also 00:02:10.910 --> 00:02:10.920 align:start position:0% other chains uh besides ethereum also 00:02:10.920 --> 00:02:13.430 align:start position:0% other chains uh besides ethereum also use<00:02:11.099> the<00:02:11.280> evm<00:02:11.700> so<00:02:12.180> these<00:02:12.480> are<00:02:12.599> two<00:02:12.840> fundamental 00:02:13.430 --> 00:02:13.440 align:start position:0% use the evm so these are two fundamental 00:02:13.440 --> 00:02:15.710 align:start position:0% use the evm so these are two fundamental public<00:02:13.620> goods<00:02:14.099> infrastructure<00:02:14.819> that<00:02:15.540> people 00:02:15.710 --> 00:02:15.720 align:start position:0% public goods infrastructure that people 00:02:15.720 --> 00:02:18.650 align:start position:0% public goods infrastructure that people depend<00:02:16.200> on<00:02:16.319> they<00:02:16.620> build<00:02:16.800> companies<00:02:17.340> on<00:02:17.660> they 00:02:18.650 --> 00:02:18.660 align:start position:0% depend on they build companies on they 00:02:18.660 --> 00:02:21.470 align:start position:0% depend on they build companies on they store<00:02:19.020> their<00:02:19.379> finances<00:02:19.860> on<00:02:20.300> and<00:02:21.300> they're 00:02:21.470 --> 00:02:21.480 align:start position:0% store their finances on and they're 00:02:21.480 --> 00:02:23.630 align:start position:0% store their finances on and they're really<00:02:21.660> important<00:02:22.080> for<00:02:22.620> people<00:02:22.980> to<00:02:23.400> actually 00:02:23.630 --> 00:02:23.640 align:start position:0% really important for people to actually 00:02:23.640 --> 00:02:25.309 align:start position:0% really important for people to actually have<00:02:23.940> access<00:02:24.239> to 00:02:25.309 --> 00:02:25.319 align:start position:0% have access to 00:02:25.319 --> 00:02:27.290 align:start position:0% have access to and<00:02:26.099> if<00:02:26.459> we're<00:02:26.640> thinking<00:02:27.000> about<00:02:27.120> the 00:02:27.290 --> 00:02:27.300 align:start position:0% and if we're thinking about the 00:02:27.300 --> 00:02:29.150 align:start position:0% and if we're thinking about the different<00:02:27.480> categories<00:02:27.959> these<00:02:28.680> can<00:02:28.739> include 00:02:29.150 --> 00:02:29.160 align:start position:0% different categories these can include 00:02:29.160 --> 00:02:31.430 align:start position:0% different categories these can include you<00:02:30.000> know<00:02:30.060> the<00:02:30.540> research<00:02:30.840> about<00:02:31.020> where<00:02:31.319> the 00:02:31.430 --> 00:02:31.440 align:start position:0% you know the research about where the 00:02:31.440 --> 00:02:33.290 align:start position:0% you know the research about where the protocol<00:02:31.680> is<00:02:31.980> going<00:02:32.160> uh<00:02:32.940> the<00:02:33.120> client 00:02:33.290 --> 00:02:33.300 align:start position:0% protocol is going uh the client 00:02:33.300 --> 00:02:35.809 align:start position:0% protocol is going uh the client developers<00:02:33.840> who<00:02:34.319> are<00:02:34.620> implementing<00:02:35.280> the 00:02:35.809 --> 00:02:35.819 align:start position:0% developers who are implementing the 00:02:35.819 --> 00:02:37.850 align:start position:0% developers who are implementing the protocol<00:02:36.180> as<00:02:36.480> it<00:02:36.660> currently<00:02:36.959> is<00:02:37.200> the 00:02:37.850 --> 00:02:37.860 align:start position:0% protocol as it currently is the 00:02:37.860 --> 00:02:39.229 align:start position:0% protocol as it currently is the coordination<00:02:38.280> like<00:02:38.520> I<00:02:38.700> mentioned<00:02:38.879> the<00:02:39.120> work 00:02:39.229 --> 00:02:39.239 align:start position:0% coordination like I mentioned the work 00:02:39.239 --> 00:02:41.650 align:start position:0% coordination like I mentioned the work that<00:02:39.420> I<00:02:39.540> do<00:02:39.660> along<00:02:39.959> with<00:02:40.140> many<00:02:40.379> others<00:02:40.739> to 00:02:41.650 --> 00:02:41.660 align:start position:0% that I do along with many others to 00:02:41.660 --> 00:02:44.089 align:start position:0% that I do along with many others to shape<00:02:42.660> Network<00:02:42.900> coordination<00:02:43.500> and<00:02:43.920> then 00:02:44.089 --> 00:02:44.099 align:start position:0% shape Network coordination and then 00:02:44.099 --> 00:02:46.369 align:start position:0% shape Network coordination and then there's<00:02:44.640> tooling<00:02:45.060> so<00:02:45.300> what<00:02:45.900> developers 00:02:46.369 --> 00:02:46.379 align:start position:0% there's tooling so what developers 00:02:46.379 --> 00:02:49.009 align:start position:0% there's tooling so what developers actually<00:02:46.620> use<00:02:46.860> to<00:02:47.099> interact<00:02:47.340> with<00:02:47.519> the<00:02:47.700> chain 00:02:49.009 --> 00:02:49.019 align:start position:0% actually use to interact with the chain 00:02:49.019 --> 00:02:50.809 align:start position:0% actually use to interact with the chain and<00:02:49.680> then<00:02:49.920> that<00:02:50.099> brings<00:02:50.280> us<00:02:50.459> to<00:02:50.580> the<00:02:50.700> question 00:02:50.809 --> 00:02:50.819 align:start position:0% and then that brings us to the question 00:02:50.819 --> 00:02:54.050 align:start position:0% and then that brings us to the question of<00:02:51.060> how<00:02:51.239> are<00:02:51.420> these<00:02:51.860> uh<00:02:52.860> these<00:02:53.459> areas<00:02:53.819> of 00:02:54.050 --> 00:02:54.060 align:start position:0% of how are these uh these areas of 00:02:54.060 --> 00:02:55.670 align:start position:0% of how are these uh these areas of public<00:02:54.239> goods<00:02:54.660> funded<00:02:54.959> a<00:02:55.140> big<00:02:55.319> one<00:02:55.440> is<00:02:55.620> the 00:02:55.670 --> 00:02:55.680 align:start position:0% public goods funded a big one is the 00:02:55.680 --> 00:02:57.770 align:start position:0% public goods funded a big one is the ethereum<00:02:56.099> foundation 00:02:57.770 --> 00:02:57.780 align:start position:0% ethereum foundation 00:02:57.780 --> 00:02:59.630 align:start position:0% ethereum foundation um<00:02:57.840> you're<00:02:58.500> probably<00:02:58.920> aware<00:02:59.280> of<00:02:59.400> what<00:02:59.580> the 00:02:59.630 --> 00:02:59.640 align:start position:0% um you're probably aware of what the 00:02:59.640 --> 00:03:00.949 align:start position:0% um you're probably aware of what the ethereum<00:03:00.000> foundation<00:03:00.239> is<00:03:00.420> and<00:03:00.480> what<00:03:00.660> it<00:03:00.780> does 00:03:00.949 --> 00:03:00.959 align:start position:0% ethereum foundation is and what it does 00:03:00.959 --> 00:03:04.009 align:start position:0% ethereum foundation is and what it does it<00:03:01.920> funds<00:03:02.280> a<00:03:02.760> huge<00:03:03.120> number<00:03:03.239> of<00:03:03.420> initiatives<00:03:03.840> in 00:03:04.009 --> 00:03:04.019 align:start position:0% it funds a huge number of initiatives in 00:03:04.019 --> 00:03:06.050 align:start position:0% it funds a huge number of initiatives in the<00:03:04.200> space<00:03:04.640> sometimes<00:03:05.640> through<00:03:05.879> direct 00:03:06.050 --> 00:03:06.060 align:start position:0% the space sometimes through direct 00:03:06.060 --> 00:03:08.869 align:start position:0% the space sometimes through direct contributions<00:03:06.840> sometimes<00:03:07.879> delegating 00:03:08.869 --> 00:03:08.879 align:start position:0% contributions sometimes delegating 00:03:08.879 --> 00:03:12.710 align:start position:0% contributions sometimes delegating funding<00:03:09.720> to<00:03:09.959> specific<00:03:10.379> ecosystem<00:03:10.860> groups<00:03:11.720> or 00:03:12.710 --> 00:03:12.720 align:start position:0% funding to specific ecosystem groups or 00:03:12.720 --> 00:03:14.210 align:start position:0% funding to specific ecosystem groups or things<00:03:12.959> like<00:03:13.080> the<00:03:13.260> client<00:03:13.500> incentive<00:03:14.040> program 00:03:14.210 --> 00:03:14.220 align:start position:0% things like the client incentive program 00:03:14.220 --> 00:03:17.690 align:start position:0% things like the client incentive program where<00:03:15.000> it<00:03:15.599> it<00:03:15.840> gives<00:03:16.140> eth<00:03:16.560> directly<00:03:16.980> to<00:03:17.340> client 00:03:17.690 --> 00:03:17.700 align:start position:0% where it it gives eth directly to client 00:03:17.700 --> 00:03:19.490 align:start position:0% where it it gives eth directly to client teams<00:03:18.000> to<00:03:18.180> run<00:03:18.300> validators<00:03:18.840> and<00:03:19.019> it<00:03:19.140> unlocks 00:03:19.490 --> 00:03:19.500 align:start position:0% teams to run validators and it unlocks 00:03:19.500 --> 00:03:21.830 align:start position:0% teams to run validators and it unlocks over<00:03:19.680> a<00:03:19.860> specific<00:03:20.099> period<00:03:20.459> of<00:03:20.519> time<00:03:20.760> and<00:03:21.720> then 00:03:21.830 --> 00:03:21.840 align:start position:0% over a specific period of time and then 00:03:21.840 --> 00:03:22.970 align:start position:0% over a specific period of time and then outside<00:03:22.019> of<00:03:22.260> the<00:03:22.319> ethereum<00:03:22.680> foundation 00:03:22.970 --> 00:03:22.980 align:start position:0% outside of the ethereum foundation 00:03:22.980 --> 00:03:26.149 align:start position:0% outside of the ethereum foundation there's<00:03:23.480> groups<00:03:24.480> like<00:03:24.599> optimism<00:03:25.140> giveth<00:03:25.860> git 00:03:26.149 --> 00:03:26.159 align:start position:0% there's groups like optimism giveth git 00:03:26.159 --> 00:03:28.630 align:start position:0% there's groups like optimism giveth git coin<00:03:26.400> CLR<00:03:26.879> fund<00:03:27.120> who<00:03:27.300> run 00:03:28.630 --> 00:03:28.640 align:start position:0% coin CLR fund who run 00:03:28.640 --> 00:03:30.710 align:start position:0% coin CLR fund who run matching<00:03:29.640> rounds<00:03:29.940> quadratic<00:03:30.480> matching 00:03:30.710 --> 00:03:30.720 align:start position:0% matching rounds quadratic matching 00:03:30.720 --> 00:03:31.910 align:start position:0% matching rounds quadratic matching rounds<00:03:31.019> where<00:03:31.200> the<00:03:31.319> community<00:03:31.500> can 00:03:31.910 --> 00:03:31.920 align:start position:0% rounds where the community can 00:03:31.920 --> 00:03:34.490 align:start position:0% rounds where the community can participate<00:03:32.879> in<00:03:33.239> actually<00:03:33.420> funding<00:03:34.019> these 00:03:34.490 --> 00:03:34.500 align:start position:0% participate in actually funding these 00:03:34.500 --> 00:03:36.170 align:start position:0% participate in actually funding these important<00:03:34.980> public<00:03:35.159> goods<00:03:35.580> things<00:03:36.000> that 00:03:36.170 --> 00:03:36.180 align:start position:0% important public goods things that 00:03:36.180 --> 00:03:38.330 align:start position:0% important public goods things that people<00:03:36.360> depend<00:03:36.780> on<00:03:36.959> and<00:03:37.800> then<00:03:37.920> another 00:03:38.330 --> 00:03:38.340 align:start position:0% people depend on and then another 00:03:38.340 --> 00:03:39.589 align:start position:0% people depend on and then another smaller<00:03:38.760> project<00:03:38.879> which<00:03:39.120> you<00:03:39.300> may<00:03:39.420> not<00:03:39.480> be 00:03:39.589 --> 00:03:39.599 align:start position:0% smaller project which you may not be 00:03:39.599 --> 00:03:41.030 align:start position:0% smaller project which you may not be aware<00:03:39.720> of<00:03:39.840> is<00:03:39.959> called<00:03:40.200> open<00:03:40.379> grants<00:03:40.799> which 00:03:41.030 --> 00:03:41.040 align:start position:0% aware of is called open grants which 00:03:41.040 --> 00:03:43.729 align:start position:0% aware of is called open grants which does<00:03:41.280> vested<00:03:42.120> eth<00:03:42.540> to<00:03:42.959> specific<00:03:43.319> groups 00:03:43.729 --> 00:03:43.739 align:start position:0% does vested eth to specific groups 00:03:43.739 --> 00:03:45.170 align:start position:0% does vested eth to specific groups there's<00:03:44.040> a 00:03:45.170 --> 00:03:45.180 align:start position:0% there's a 00:03:45.180 --> 00:03:47.270 align:start position:0% there's a some<00:03:45.900> projects<00:03:46.260> that<00:03:46.379> are<00:03:46.500> using<00:03:46.739> this<00:03:46.920> to 00:03:47.270 --> 00:03:47.280 align:start position:0% some projects that are using this to 00:03:47.280 --> 00:03:49.490 align:start position:0% some projects that are using this to fund<00:03:47.879> public<00:03:48.060> goods 00:03:49.490 --> 00:03:49.500 align:start position:0% fund public goods 00:03:49.500 --> 00:03:51.589 align:start position:0% fund public goods so<00:03:49.920> yeah<00:03:50.040> there's<00:03:50.400> quite<00:03:50.760> a<00:03:50.940> diversity<00:03:51.299> and<00:03:51.480> I 00:03:51.589 --> 00:03:51.599 align:start position:0% so yeah there's quite a diversity and I 00:03:51.599 --> 00:03:54.470 align:start position:0% so yeah there's quite a diversity and I think<00:03:51.720> this<00:03:51.959> is<00:03:52.680> um<00:03:53.159> uh<00:03:53.819> one<00:03:54.000> of<00:03:54.120> the<00:03:54.180> strengths 00:03:54.470 --> 00:03:54.480 align:start position:0% think this is um uh one of the strengths 00:03:54.480 --> 00:03:56.570 align:start position:0% think this is um uh one of the strengths of<00:03:54.599> ethereum<00:03:55.080> is<00:03:55.260> that<00:03:55.440> it<00:03:55.739> has<00:03:55.980> a<00:03:56.220> diversity 00:03:56.570 --> 00:03:56.580 align:start position:0% of ethereum is that it has a diversity 00:03:56.580 --> 00:03:59.030 align:start position:0% of ethereum is that it has a diversity of<00:03:56.760> approaches<00:03:57.120> Kevin<00:03:57.360> owaki<00:03:58.019> uh<00:03:58.680> formerly 00:03:59.030 --> 00:03:59.040 align:start position:0% of approaches Kevin owaki uh formerly 00:03:59.040 --> 00:04:01.309 align:start position:0% of approaches Kevin owaki uh formerly the<00:03:59.220> founder<00:03:59.459> of<00:03:59.580> git<00:03:59.760> coin<00:04:00.120> uh<00:04:00.840> had<00:04:01.019> a<00:04:01.200> talk 00:04:01.309 --> 00:04:01.319 align:start position:0% the founder of git coin uh had a talk 00:04:01.319 --> 00:04:03.649 align:start position:0% the founder of git coin uh had a talk earlier<00:04:01.620> that<00:04:01.799> I<00:04:01.920> was<00:04:02.040> on<00:04:02.159> about<00:04:02.340> uh<00:04:03.299> practical 00:04:03.649 --> 00:04:03.659 align:start position:0% earlier that I was on about uh practical 00:04:03.659 --> 00:04:05.869 align:start position:0% earlier that I was on about uh practical pluralism<00:04:04.260> and<00:04:04.920> how<00:04:05.159> important<00:04:05.459> it<00:04:05.580> is<00:04:05.700> that 00:04:05.869 --> 00:04:05.879 align:start position:0% pluralism and how important it is that 00:04:05.879 --> 00:04:08.990 align:start position:0% pluralism and how important it is that we<00:04:06.120> have<00:04:06.500> these<00:04:07.500> many<00:04:08.099> overlapping 00:04:08.990 --> 00:04:09.000 align:start position:0% we have these many overlapping 00:04:09.000 --> 00:04:10.970 align:start position:0% we have these many overlapping approaches<00:04:09.840> to<00:04:10.140> how<00:04:10.379> to<00:04:10.500> fund<00:04:10.739> these 00:04:10.970 --> 00:04:10.980 align:start position:0% approaches to how to fund these 00:04:10.980 --> 00:04:13.190 align:start position:0% approaches to how to fund these important<00:04:11.400> initiatives<00:04:12.120> how<00:04:12.540> to<00:04:12.659> get<00:04:12.840> funding 00:04:13.190 --> 00:04:13.200 align:start position:0% important initiatives how to get funding 00:04:13.200 --> 00:04:14.449 align:start position:0% important initiatives how to get funding to<00:04:13.439> people<00:04:13.620> who<00:04:13.860> are<00:04:13.980> working<00:04:14.220> on 00:04:14.449 --> 00:04:14.459 align:start position:0% to people who are working on 00:04:14.459 --> 00:04:16.449 align:start position:0% to people who are working on infrastructure<00:04:15.120> and<00:04:15.900> this<00:04:16.019> is<00:04:16.139> a<00:04:16.320> great 00:04:16.449 --> 00:04:16.459 align:start position:0% infrastructure and this is a great 00:04:16.459 --> 00:04:19.189 align:start position:0% infrastructure and this is a great visualization<00:04:17.459> of<00:04:17.880> I'm<00:04:18.600> sure<00:04:18.900> I'm<00:04:19.019> leaving 00:04:19.189 --> 00:04:19.199 align:start position:0% visualization of I'm sure I'm leaving 00:04:19.199 --> 00:04:20.990 align:start position:0% visualization of I'm sure I'm leaving out<00:04:19.440> some<00:04:19.620> projects<00:04:19.919> so<00:04:20.040> I<00:04:20.160> apologize<00:04:20.579> but 00:04:20.990 --> 00:04:21.000 align:start position:0% out some projects so I apologize but 00:04:21.000 --> 00:04:23.689 align:start position:0% out some projects so I apologize but there<00:04:21.299> are<00:04:21.540> these<00:04:22.139> projects<00:04:22.560> on<00:04:23.220> the<00:04:23.340> on<00:04:23.520> the 00:04:23.689 --> 00:04:23.699 align:start position:0% there are these projects on the on the 00:04:23.699 --> 00:04:26.570 align:start position:0% there are these projects on the on the slide<00:04:23.880> and<00:04:24.120> many<00:04:24.240> more<00:04:24.540> who<00:04:25.100> do<00:04:26.100> the<00:04:26.280> important 00:04:26.570 --> 00:04:26.580 align:start position:0% slide and many more who do the important 00:04:26.580 --> 00:04:29.570 align:start position:0% slide and many more who do the important work<00:04:26.820> of<00:04:27.240> getting<00:04:27.840> money<00:04:28.199> to<00:04:28.740> public<00:04:29.100> goods 00:04:29.570 --> 00:04:29.580 align:start position:0% work of getting money to public goods 00:04:29.580 --> 00:04:31.310 align:start position:0% work of getting money to public goods infrastructure<00:04:30.360> the<00:04:30.600> developers<00:04:31.020> who<00:04:31.199> are 00:04:31.310 --> 00:04:31.320 align:start position:0% infrastructure the developers who are 00:04:31.320 --> 00:04:32.810 align:start position:0% infrastructure the developers who are actually<00:04:31.440> building<00:04:31.740> the<00:04:32.220> things<00:04:32.460> that<00:04:32.699> we 00:04:32.810 --> 00:04:32.820 align:start position:0% actually building the things that we 00:04:32.820 --> 00:04:33.830 align:start position:0% actually building the things that we depend<00:04:33.060> on 00:04:33.830 --> 00:04:33.840 align:start position:0% depend on 00:04:33.840 --> 00:04:36.710 align:start position:0% depend on and<00:04:34.500> I'll<00:04:34.680> Echo<00:04:35.040> that<00:04:35.160> by<00:04:35.280> by<00:04:35.400> saying<00:04:36.000> uh<00:04:36.479> many 00:04:36.710 --> 00:04:36.720 align:start position:0% and I'll Echo that by by saying uh many 00:04:36.720 --> 00:04:38.990 align:start position:0% and I'll Echo that by by saying uh many Community<00:04:36.960> funding<00:04:37.500> mechanisms<00:04:37.919> are<00:04:38.100> good<00:04:38.280> it 00:04:38.990 --> 00:04:39.000 align:start position:0% Community funding mechanisms are good it 00:04:39.000 --> 00:04:40.850 align:start position:0% Community funding mechanisms are good it decentralizes<00:04:39.660> power<00:04:39.960> and<00:04:40.139> influence<00:04:40.560> away 00:04:40.850 --> 00:04:40.860 align:start position:0% decentralizes power and influence away 00:04:40.860 --> 00:04:44.810 align:start position:0% decentralizes power and influence away from<00:04:41.340> uh<00:04:42.180> single<00:04:42.840> entities<00:04:43.340> it<00:04:44.340> celebrates 00:04:44.810 --> 00:04:44.820 align:start position:0% from uh single entities it celebrates 00:04:44.820 --> 00:04:47.150 align:start position:0% from uh single entities it celebrates pluralism<00:04:45.660> like<00:04:45.960> I<00:04:46.080> mentioned 00:04:47.150 --> 00:04:47.160 align:start position:0% pluralism like I mentioned 00:04:47.160 --> 00:04:49.129 align:start position:0% pluralism like I mentioned um<00:04:47.220> prevents<00:04:47.820> influence<00:04:48.300> from<00:04:48.479> being<00:04:48.660> siled 00:04:49.129 --> 00:04:49.139 align:start position:0% um prevents influence from being siled 00:04:49.139 --> 00:04:51.770 align:start position:0% um prevents influence from being siled with<00:04:49.620> individual<00:04:50.040> allocators<00:04:50.759> and<00:04:51.540> it 00:04:51.770 --> 00:04:51.780 align:start position:0% with individual allocators and it 00:04:51.780 --> 00:04:52.969 align:start position:0% with individual allocators and it strengths<00:04:52.199> strengthens<00:04:52.800> the 00:04:52.969 --> 00:04:52.979 align:start position:0% strengths strengthens the 00:04:52.979 --> 00:04:55.129 align:start position:0% strengths strengthens the intra-community<00:04:53.699> relationships 00:04:55.129 --> 00:04:55.139 align:start position:0% intra-community relationships 00:04:55.139 --> 00:04:57.110 align:start position:0% intra-community relationships however<00:04:55.680> uh 00:04:57.110 --> 00:04:57.120 align:start position:0% however uh 00:04:57.120 --> 00:04:59.030 align:start position:0% however uh especially<00:04:57.660> the<00:04:57.900> quadratic<00:04:58.560> funding 00:04:59.030 --> 00:04:59.040 align:start position:0% especially the quadratic funding 00:04:59.040 --> 00:05:00.469 align:start position:0% especially the quadratic funding mechanisms<00:04:59.520> they<00:04:59.759> often<00:05:00.000> use<00:05:00.060> similar 00:05:00.469 --> 00:05:00.479 align:start position:0% mechanisms they often use similar 00:05:00.479 --> 00:05:03.110 align:start position:0% mechanisms they often use similar curation<00:05:00.900> techniques<00:05:01.440> for<00:05:01.740> example<00:05:02.120> it 00:05:03.110 --> 00:05:03.120 align:start position:0% curation techniques for example it 00:05:03.120 --> 00:05:05.810 align:start position:0% curation techniques for example it weights<00:05:03.680> the<00:05:04.680> matching<00:05:05.040> pool<00:05:05.220> division 00:05:05.810 --> 00:05:05.820 align:start position:0% weights the matching pool division 00:05:05.820 --> 00:05:08.450 align:start position:0% weights the matching pool division according<00:05:06.360> to<00:05:06.720> how<00:05:07.380> many<00:05:07.500> people<00:05:07.680> donate<00:05:08.040> to<00:05:08.220> a 00:05:08.450 --> 00:05:08.460 align:start position:0% according to how many people donate to a 00:05:08.460 --> 00:05:11.030 align:start position:0% according to how many people donate to a specific<00:05:08.699> Grant<00:05:09.380> and<00:05:10.380> this<00:05:10.620> is<00:05:10.680> not<00:05:10.800> to<00:05:10.919> say 00:05:11.030 --> 00:05:11.040 align:start position:0% specific Grant and this is not to say 00:05:11.040 --> 00:05:13.189 align:start position:0% specific Grant and this is not to say that's<00:05:11.220> a<00:05:11.340> bad<00:05:11.460> thing<00:05:11.580> it<00:05:11.940> just<00:05:12.600> um 00:05:13.189 --> 00:05:13.199 align:start position:0% that's a bad thing it just um 00:05:13.199 --> 00:05:16.249 align:start position:0% that's a bad thing it just um it's<00:05:14.040> it<00:05:14.460> can<00:05:14.940> have<00:05:15.300> a<00:05:15.540> challenge<00:05:15.720> when<00:05:16.080> it 00:05:16.249 --> 00:05:16.259 align:start position:0% it's it can have a challenge when it 00:05:16.259 --> 00:05:18.950 align:start position:0% it's it can have a challenge when it comes<00:05:16.500> to<00:05:17.240> delegating<00:05:18.240> funding<00:05:18.600> or<00:05:18.780> getting 00:05:18.950 --> 00:05:18.960 align:start position:0% comes to delegating funding or getting 00:05:18.960 --> 00:05:20.570 align:start position:0% comes to delegating funding or getting funding<00:05:19.320> to<00:05:19.440> areas<00:05:19.740> of<00:05:19.860> the<00:05:19.979> protocol<00:05:20.220> that 00:05:20.570 --> 00:05:20.580 align:start position:0% funding to areas of the protocol that 00:05:20.580 --> 00:05:23.390 align:start position:0% funding to areas of the protocol that may<00:05:20.699> not<00:05:20.820> be<00:05:21.000> a<00:05:21.120> fit<00:05:21.300> for<00:05:21.540> quadratic<00:05:22.199> funding 00:05:23.390 --> 00:05:23.400 align:start position:0% may not be a fit for quadratic funding 00:05:23.400 --> 00:05:25.730 align:start position:0% may not be a fit for quadratic funding so<00:05:23.880> this<00:05:24.000> is<00:05:24.180> the<00:05:24.419> question<00:05:24.600> is<00:05:24.840> how<00:05:25.259> can<00:05:25.440> we 00:05:25.730 --> 00:05:25.740 align:start position:0% so this is the question is how can we 00:05:25.740 --> 00:05:28.310 align:start position:0% so this is the question is how can we curate<00:05:26.400> better<00:05:26.699> specifically<00:05:27.539> related<00:05:27.960> to 00:05:28.310 --> 00:05:28.320 align:start position:0% curate better specifically related to 00:05:28.320 --> 00:05:30.590 align:start position:0% curate better specifically related to the<00:05:28.860> core<00:05:28.979> protocol<00:05:29.400> and<00:05:29.940> then<00:05:30.060> even<00:05:30.360> more 00:05:30.590 --> 00:05:30.600 align:start position:0% the core protocol and then even more 00:05:30.600 --> 00:05:32.810 align:start position:0% the core protocol and then even more broadly<00:05:30.900> how<00:05:31.440> can<00:05:31.620> we<00:05:31.740> incentivize<00:05:32.280> long-term 00:05:32.810 --> 00:05:32.820 align:start position:0% broadly how can we incentivize long-term 00:05:32.820 --> 00:05:35.629 align:start position:0% broadly how can we incentivize long-term core<00:05:32.940> protocol<00:05:33.360> contributions<00:05:34.199> so<00:05:34.860> this<00:05:35.039> is<00:05:35.220> a 00:05:35.629 --> 00:05:35.639 align:start position:0% core protocol contributions so this is a 00:05:35.639 --> 00:05:37.430 align:start position:0% core protocol contributions so this is a a<00:05:36.060> big<00:05:36.300> question<00:05:36.539> that's<00:05:36.960> you<00:05:37.199> know<00:05:37.259> been 00:05:37.430 --> 00:05:37.440 align:start position:0% a big question that's you know been 00:05:37.440 --> 00:05:40.010 align:start position:0% a big question that's you know been around<00:05:37.620> as<00:05:37.860> long<00:05:38.100> as<00:05:38.280> open<00:05:38.639> source<00:05:39.180> software 00:05:40.010 --> 00:05:40.020 align:start position:0% around as long as open source software 00:05:40.020 --> 00:05:42.770 align:start position:0% around as long as open source software has<00:05:40.320> has<00:05:40.740> been<00:05:41.400> worked<00:05:41.699> on<00:05:41.759> and<00:05:42.060> it's<00:05:42.300> not<00:05:42.539> a 00:05:42.770 --> 00:05:42.780 align:start position:0% has has been worked on and it's not a 00:05:42.780 --> 00:05:45.050 align:start position:0% has has been worked on and it's not a new<00:05:42.900> problem<00:05:43.139> for<00:05:43.440> ethereum<00:05:43.919> uh<00:05:44.699> people<00:05:44.880> have 00:05:45.050 --> 00:05:45.060 align:start position:0% new problem for ethereum uh people have 00:05:45.060 --> 00:05:46.610 align:start position:0% new problem for ethereum uh people have talked<00:05:45.360> about<00:05:45.479> it<00:05:45.720> over<00:05:45.900> the<00:05:46.080> years<00:05:46.199> you<00:05:46.500> know 00:05:46.610 --> 00:05:46.620 align:start position:0% talked about it over the years you know 00:05:46.620 --> 00:05:48.409 align:start position:0% talked about it over the years you know people<00:05:47.100> join<00:05:47.460> core<00:05:47.639> development<00:05:48.060> they<00:05:48.240> leave 00:05:48.409 --> 00:05:48.419 align:start position:0% people join core development they leave 00:05:48.419 --> 00:05:50.749 align:start position:0% people join core development they leave core<00:05:48.600> development<00:05:49.100> it's<00:05:50.100> something<00:05:50.340> that 00:05:50.749 --> 00:05:50.759 align:start position:0% core development it's something that 00:05:50.759 --> 00:05:52.070 align:start position:0% core development it's something that will<00:05:50.940> be<00:05:51.120> with<00:05:51.300> us<00:05:51.419> as<00:05:51.600> long<00:05:51.780> as<00:05:51.840> we're 00:05:52.070 --> 00:05:52.080 align:start position:0% will be with us as long as we're 00:05:52.080 --> 00:05:54.529 align:start position:0% will be with us as long as we're producing<00:05:52.500> software<00:05:52.919> and<00:05:53.580> modifying<00:05:54.360> the 00:05:54.529 --> 00:05:54.539 align:start position:0% producing software and modifying the 00:05:54.539 --> 00:05:56.330 align:start position:0% producing software and modifying the protocol<00:05:54.840> so<00:05:55.380> these<00:05:55.680> are<00:05:55.740> these<00:05:56.039> are<00:05:56.100> the<00:05:56.160> big 00:05:56.330 --> 00:05:56.340 align:start position:0% protocol so these are these are the big 00:05:56.340 --> 00:05:57.469 align:start position:0% protocol so these are these are the big questions 00:05:57.469 --> 00:05:57.479 align:start position:0% questions 00:05:57.479 --> 00:06:00.409 align:start position:0% questions um<00:05:57.539> that<00:05:58.340> came<00:05:59.340> to<00:05:59.580> mind 00:06:00.409 --> 00:06:00.419 align:start position:0% um that came to mind 00:06:00.419 --> 00:06:02.210 align:start position:0% um that came to mind um<00:06:00.539> over<00:06:01.020> the<00:06:01.199> years<00:06:01.320> they've<00:06:01.680> been<00:06:02.039> a 00:06:02.210 --> 00:06:02.220 align:start position:0% um over the years they've been a 00:06:02.220 --> 00:06:04.670 align:start position:0% um over the years they've been a recurring<00:06:02.580> set<00:06:02.820> of<00:06:03.120> concerns<00:06:03.600> and<00:06:04.320> especially 00:06:04.670 --> 00:06:04.680 align:start position:0% recurring set of concerns and especially 00:06:04.680 --> 00:06:07.790 align:start position:0% recurring set of concerns and especially last<00:06:05.100> year<00:06:05.600> November<00:06:06.600> the<00:06:06.960> discussion<00:06:07.440> in<00:06:07.620> the 00:06:07.790 --> 00:06:07.800 align:start position:0% last year November the discussion in the 00:06:07.800 --> 00:06:10.129 align:start position:0% last year November the discussion in the community<00:06:07.919> began<00:06:08.580> again<00:06:08.820> about<00:06:09.180> how<00:06:09.780> can<00:06:09.960> we 00:06:10.129 --> 00:06:10.139 align:start position:0% community began again about how can we 00:06:10.139 --> 00:06:13.249 align:start position:0% community began again about how can we properly<00:06:10.740> incentivize<00:06:11.780> contributors<00:06:12.780> to 00:06:13.249 --> 00:06:13.259 align:start position:0% properly incentivize contributors to 00:06:13.259 --> 00:06:16.550 align:start position:0% properly incentivize contributors to stick<00:06:13.800> around<00:06:14.300> while<00:06:15.300> also<00:06:15.720> making<00:06:16.199> sure<00:06:16.380> that 00:06:16.550 --> 00:06:16.560 align:start position:0% stick around while also making sure that 00:06:16.560 --> 00:06:19.490 align:start position:0% stick around while also making sure that they're<00:06:16.740> financially<00:06:17.160> compensated 00:06:19.490 --> 00:06:19.500 align:start position:0% they're financially compensated 00:06:19.500 --> 00:06:22.730 align:start position:0% they're financially compensated so<00:06:20.280> uh<00:06:20.699> when<00:06:21.060> this<00:06:21.360> discussion<00:06:22.139> came<00:06:22.319> up<00:06:22.440> last 00:06:22.730 --> 00:06:22.740 align:start position:0% so uh when this discussion came up last 00:06:22.740 --> 00:06:24.529 align:start position:0% so uh when this discussion came up last year<00:06:22.919> there<00:06:23.280> were 00:06:24.529 --> 00:06:24.539 align:start position:0% year there were 00:06:24.539 --> 00:06:27.110 align:start position:0% year there were um<00:06:24.600> my<00:06:25.380> perspective<00:06:25.800> of<00:06:26.460> being<00:06:26.759> around<00:06:26.880> core 00:06:27.110 --> 00:06:27.120 align:start position:0% um my perspective of being around core 00:06:27.120 --> 00:06:29.090 align:start position:0% um my perspective of being around core development<00:06:27.600> for<00:06:27.900> a<00:06:27.960> few<00:06:28.199> years<00:06:28.319> now<00:06:28.620> and<00:06:28.979> then 00:06:29.090 --> 00:06:29.100 align:start position:0% development for a few years now and then 00:06:29.100 --> 00:06:30.890 align:start position:0% development for a few years now and then working<00:06:29.400> with<00:06:29.639> core<00:06:29.880> developers<00:06:30.360> directly 00:06:30.890 --> 00:06:30.900 align:start position:0% working with core developers directly 00:06:30.900 --> 00:06:33.770 align:start position:0% working with core developers directly some<00:06:31.800> researchers<00:06:32.400> we<00:06:33.180> started<00:06:33.479> to<00:06:33.600> think 00:06:33.770 --> 00:06:33.780 align:start position:0% some researchers we started to think 00:06:33.780 --> 00:06:36.650 align:start position:0% some researchers we started to think about<00:06:33.900> what<00:06:34.380> sort<00:06:34.620> of<00:06:34.740> challenges<00:06:35.419> uh<00:06:36.419> were 00:06:36.650 --> 00:06:36.660 align:start position:0% about what sort of challenges uh were 00:06:36.660 --> 00:06:39.050 align:start position:0% about what sort of challenges uh were most<00:06:36.840> important<00:06:37.259> to<00:06:37.560> address<00:06:37.919> when<00:06:38.639> thinking 00:06:39.050 --> 00:06:39.060 align:start position:0% most important to address when thinking 00:06:39.060 --> 00:06:41.090 align:start position:0% most important to address when thinking about<00:06:39.240> what<00:06:40.020> sort<00:06:40.139> of<00:06:40.259> mechanism<00:06:40.620> would<00:06:40.979> be 00:06:41.090 --> 00:06:41.100 align:start position:0% about what sort of mechanism would be 00:06:41.100 --> 00:06:44.210 align:start position:0% about what sort of mechanism would be best<00:06:41.340> to<00:06:41.840> design<00:06:42.840> and<00:06:43.500> if<00:06:43.740> I'll<00:06:43.979> go<00:06:44.100> through 00:06:44.210 --> 00:06:44.220 align:start position:0% best to design and if I'll go through 00:06:44.220 --> 00:06:45.590 align:start position:0% best to design and if I'll go through the<00:06:44.400> first<00:06:44.699> through<00:06:44.819> here<00:06:45.000> just<00:06:45.180> an<00:06:45.360> overview 00:06:45.590 --> 00:06:45.600 align:start position:0% the first through here just an overview 00:06:45.600 --> 00:06:48.409 align:start position:0% the first through here just an overview and<00:06:45.960> then<00:06:46.080> the<00:06:46.199> next<00:06:46.380> slides<00:06:47.000> detail<00:06:48.000> out<00:06:48.180> what 00:06:48.409 --> 00:06:48.419 align:start position:0% and then the next slides detail out what 00:06:48.419 --> 00:06:49.490 align:start position:0% and then the next slides detail out what these<00:06:48.600> challenges<00:06:48.840> are<00:06:49.020> so<00:06:49.199> the<00:06:49.380> first 00:06:49.490 --> 00:06:49.500 align:start position:0% these challenges are so the first 00:06:49.500 --> 00:06:51.770 align:start position:0% these challenges are so the first challenge<00:06:49.800> curation<00:06:50.699> is<00:06:50.940> hard<00:06:51.180> the<00:06:51.600> second 00:06:51.770 --> 00:06:51.780 align:start position:0% challenge curation is hard the second 00:06:51.780 --> 00:06:53.930 align:start position:0% challenge curation is hard the second the<00:06:52.500> incentives<00:06:52.860> are<00:06:53.039> imbalanced<00:06:53.580> and<00:06:53.819> the 00:06:53.930 --> 00:06:53.940 align:start position:0% the incentives are imbalanced and the 00:06:53.940 --> 00:06:56.330 align:start position:0% the incentives are imbalanced and the third<00:06:54.060> contributor<00:06:54.660> churn<00:06:54.960> is<00:06:55.259> bad<00:06:55.440> so<00:06:56.220> the 00:06:56.330 --> 00:06:56.340 align:start position:0% third contributor churn is bad so the 00:06:56.340 --> 00:06:58.969 align:start position:0% third contributor churn is bad so the first<00:06:56.580> challenge<00:06:57.120> about<00:06:57.660> curation<00:06:58.199> the 00:06:58.969 --> 00:06:58.979 align:start position:0% first challenge about curation the 00:06:58.979 --> 00:07:00.830 align:start position:0% first challenge about curation the ecosystem<00:06:59.460> is<00:07:00.120> very<00:07:00.300> interested<00:07:00.720> in 00:07:00.830 --> 00:07:00.840 align:start position:0% ecosystem is very interested in 00:07:00.840 --> 00:07:02.230 align:start position:0% ecosystem is very interested in sponsoring 00:07:02.230 --> 00:07:02.240 align:start position:0% sponsoring 00:07:02.240 --> 00:07:05.270 align:start position:0% sponsoring this<00:07:03.240> guy<00:07:03.419> The<00:07:03.720> Princess<00:07:03.900> and<00:07:04.500> the<00:07:04.740> magician 00:07:05.270 --> 00:07:05.280 align:start position:0% this guy The Princess and the magician 00:07:05.280 --> 00:07:07.850 align:start position:0% this guy The Princess and the magician the<00:07:05.880> ecosystem<00:07:06.240> of<00:07:06.539> broader<00:07:06.960> individuals 00:07:07.850 --> 00:07:07.860 align:start position:0% the ecosystem of broader individuals 00:07:07.860 --> 00:07:11.450 align:start position:0% the ecosystem of broader individuals Dows<00:07:08.600> protocols<00:07:09.600> l2s<00:07:10.440> they're<00:07:10.919> interested<00:07:11.280> in 00:07:11.450 --> 00:07:11.460 align:start position:0% Dows protocols l2s they're interested in 00:07:11.460 --> 00:07:12.890 align:start position:0% Dows protocols l2s they're interested in funding<00:07:11.759> the<00:07:11.880> core<00:07:12.000> protocol<00:07:12.360> but<00:07:12.660> they<00:07:12.780> don't 00:07:12.890 --> 00:07:12.900 align:start position:0% funding the core protocol but they don't 00:07:12.900 --> 00:07:15.409 align:start position:0% funding the core protocol but they don't have<00:07:13.080> a<00:07:13.319> single<00:07:13.620> mechanism<00:07:14.220> to<00:07:14.639> send<00:07:14.880> funds<00:07:15.240> to 00:07:15.409 --> 00:07:15.419 align:start position:0% have a single mechanism to send funds to 00:07:15.419 --> 00:07:18.010 align:start position:0% have a single mechanism to send funds to there's<00:07:16.139> uh<00:07:16.740> sometimes<00:07:17.160> projects<00:07:17.699> will 00:07:18.010 --> 00:07:18.020 align:start position:0% there's uh sometimes projects will 00:07:18.020 --> 00:07:20.390 align:start position:0% there's uh sometimes projects will publicize<00:07:19.020> their<00:07:19.440> you<00:07:19.860> know<00:07:19.919> ethereum 00:07:20.390 --> 00:07:20.400 align:start position:0% publicize their you know ethereum 00:07:20.400 --> 00:07:22.550 align:start position:0% publicize their you know ethereum address<00:07:20.639> that<00:07:21.539> you<00:07:21.660> can<00:07:21.780> send<00:07:21.900> donations<00:07:22.259> to 00:07:22.550 --> 00:07:22.560 align:start position:0% address that you can send donations to 00:07:22.560 --> 00:07:25.249 align:start position:0% address that you can send donations to but<00:07:23.340> it's<00:07:23.520> not<00:07:23.699> necessarily<00:07:24.240> easy<00:07:24.660> to<00:07:25.020> find 00:07:25.249 --> 00:07:25.259 align:start position:0% but it's not necessarily easy to find 00:07:25.259 --> 00:07:27.890 align:start position:0% but it's not necessarily easy to find all<00:07:25.500> of<00:07:25.620> them<00:07:25.740> in<00:07:25.979> a<00:07:26.099> single<00:07:26.340> location 00:07:27.890 --> 00:07:27.900 align:start position:0% all of them in a single location 00:07:27.900 --> 00:07:28.550 align:start position:0% all of them in a single location um 00:07:28.550 --> 00:07:28.560 align:start position:0% um 00:07:28.560 --> 00:07:31.010 align:start position:0% um similarly<00:07:29.280> protocol<00:07:29.639> contributors<00:07:30.360> are 00:07:31.010 --> 00:07:31.020 align:start position:0% similarly protocol contributors are 00:07:31.020 --> 00:07:34.070 align:start position:0% similarly protocol contributors are interested<00:07:31.560> in<00:07:32.160> receiving<00:07:33.060> funding<00:07:33.539> some<00:07:33.960> of 00:07:34.070 --> 00:07:34.080 align:start position:0% interested in receiving funding some of 00:07:34.080 --> 00:07:35.870 align:start position:0% interested in receiving funding some of them<00:07:34.199> may<00:07:34.380> not<00:07:34.560> be<00:07:34.860> directly<00:07:35.220> working<00:07:35.460> for<00:07:35.699> a 00:07:35.870 --> 00:07:35.880 align:start position:0% them may not be directly working for a 00:07:35.880 --> 00:07:36.950 align:start position:0% them may not be directly working for a team<00:07:36.000> but<00:07:36.240> they're<00:07:36.360> doing<00:07:36.539> important 00:07:36.950 --> 00:07:36.960 align:start position:0% team but they're doing important 00:07:36.960 --> 00:07:39.529 align:start position:0% team but they're doing important infrastructure<00:07:37.560> work<00:07:38.120> they're<00:07:39.120> interested 00:07:39.529 --> 00:07:39.539 align:start position:0% infrastructure work they're interested 00:07:39.539 --> 00:07:42.110 align:start position:0% infrastructure work they're interested in<00:07:40.080> receiving<00:07:40.860> some<00:07:41.460> form<00:07:41.699> of<00:07:41.940> financial 00:07:42.110 --> 00:07:42.120 align:start position:0% in receiving some form of financial 00:07:42.120 --> 00:07:43.490 align:start position:0% in receiving some form of financial compensation<00:07:42.720> for<00:07:42.960> the<00:07:43.080> work<00:07:43.199> that<00:07:43.380> they're 00:07:43.490 --> 00:07:43.500 align:start position:0% compensation for the work that they're 00:07:43.500 --> 00:07:45.170 align:start position:0% compensation for the work that they're doing<00:07:43.680> but<00:07:44.160> there's<00:07:44.340> no<00:07:44.520> single<00:07:44.819> mechanism 00:07:45.170 --> 00:07:45.180 align:start position:0% doing but there's no single mechanism 00:07:45.180 --> 00:07:47.150 align:start position:0% doing but there's no single mechanism for<00:07:45.479> them<00:07:45.599> to<00:07:45.780> plug<00:07:45.960> into<00:07:46.139> and<00:07:46.500> be<00:07:46.680> recognized 00:07:47.150 --> 00:07:47.160 align:start position:0% for them to plug into and be recognized 00:07:47.160 --> 00:07:49.610 align:start position:0% for them to plug into and be recognized for<00:07:47.400> their<00:07:47.580> work<00:07:47.960> and<00:07:48.960> then<00:07:49.020> on<00:07:49.259> top<00:07:49.380> of<00:07:49.500> that 00:07:49.610 --> 00:07:49.620 align:start position:0% for their work and then on top of that 00:07:49.620 --> 00:07:51.650 align:start position:0% for their work and then on top of that some<00:07:49.860> of<00:07:49.979> the<00:07:50.099> existing<00:07:51.000> Solutions<00:07:51.419> favor 00:07:51.650 --> 00:07:51.660 align:start position:0% some of the existing Solutions favor 00:07:51.660 --> 00:07:54.350 align:start position:0% some of the existing Solutions favor teams<00:07:52.199> due<00:07:52.500> to<00:07:52.620> the<00:07:52.800> difficulty<00:07:53.340> of<00:07:53.759> curation 00:07:54.350 --> 00:07:54.360 align:start position:0% teams due to the difficulty of curation 00:07:54.360 --> 00:07:55.809 align:start position:0% teams due to the difficulty of curation like<00:07:54.660> I<00:07:54.780> mentioned 00:07:55.809 --> 00:07:55.819 align:start position:0% like I mentioned 00:07:55.819 --> 00:07:58.129 align:start position:0% like I mentioned the<00:07:56.819> solutions<00:07:57.240> favor<00:07:57.419> teams<00:07:57.900> and<00:07:58.020> it's 00:07:58.129 --> 00:07:58.139 align:start position:0% the solutions favor teams and it's 00:07:58.139 --> 00:08:00.230 align:start position:0% the solutions favor teams and it's really<00:07:58.319> hard<00:07:58.560> for<00:07:58.740> them<00:07:58.860> to<00:07:59.099> surface<00:07:59.460> many 00:08:00.230 --> 00:08:00.240 align:start position:0% really hard for them to surface many 00:08:00.240 --> 00:08:02.270 align:start position:0% really hard for them to surface many individual<00:08:00.780> contributors<00:08:01.380> for<00:08:01.620> example<00:08:01.860> in<00:08:02.160> a 00:08:02.270 --> 00:08:02.280 align:start position:0% individual contributors for example in a 00:08:02.280 --> 00:08:05.210 align:start position:0% individual contributors for example in a grants<00:08:02.520> round 00:08:05.210 --> 00:08:05.220 align:start position:0% 00:08:05.220 --> 00:08:07.189 align:start position:0% um<00:08:05.280> and<00:08:05.880> we<00:08:06.180> can't<00:08:06.300> expect<00:08:06.539> a<00:08:06.900> single 00:08:07.189 --> 00:08:07.199 align:start position:0% um and we can't expect a single 00:08:07.199 --> 00:08:10.490 align:start position:0% um and we can't expect a single organization<00:08:07.800> to<00:08:08.940> uh<00:08:09.479> that's<00:08:09.720> outside<00:08:10.020> of 00:08:10.490 --> 00:08:10.500 align:start position:0% organization to uh that's outside of 00:08:10.500 --> 00:08:11.870 align:start position:0% organization to uh that's outside of this<00:08:10.800> core<00:08:10.979> development<00:08:11.400> or<00:08:11.580> this<00:08:11.699> core 00:08:11.870 --> 00:08:11.880 align:start position:0% this core development or this core 00:08:11.880 --> 00:08:14.510 align:start position:0% this core development or this core infrastructure<00:08:12.419> to<00:08:12.599> effectively<00:08:13.259> curate<00:08:13.800> the 00:08:14.510 --> 00:08:14.520 align:start position:0% infrastructure to effectively curate the 00:08:14.520 --> 00:08:15.770 align:start position:0% infrastructure to effectively curate the work<00:08:14.639> that<00:08:14.940> these<00:08:15.120> people<00:08:15.240> are<00:08:15.419> doing<00:08:15.539> you 00:08:15.770 --> 00:08:15.780 align:start position:0% work that these people are doing you 00:08:15.780 --> 00:08:18.589 align:start position:0% work that these people are doing you know<00:08:15.900> it's<00:08:16.020> very<00:08:16.380> deep<00:08:16.860> technically<00:08:17.460> uh<00:08:18.360> it 00:08:18.589 --> 00:08:18.599 align:start position:0% know it's very deep technically uh it 00:08:18.599 --> 00:08:20.330 align:start position:0% know it's very deep technically uh it requires<00:08:19.080> you<00:08:19.259> to<00:08:19.440> sort<00:08:19.680> of<00:08:19.800> be<00:08:19.860> embedded 00:08:20.330 --> 00:08:20.340 align:start position:0% requires you to sort of be embedded 00:08:20.340 --> 00:08:22.670 align:start position:0% requires you to sort of be embedded within<00:08:20.639> that<00:08:20.819> work<00:08:21.060> and<00:08:21.900> it's<00:08:22.199> it's<00:08:22.440> not 00:08:22.670 --> 00:08:22.680 align:start position:0% within that work and it's it's not 00:08:22.680 --> 00:08:23.930 align:start position:0% within that work and it's it's not reasonable<00:08:23.039> to<00:08:23.280> expect<00:08:23.400> a<00:08:23.699> single 00:08:23.930 --> 00:08:23.940 align:start position:0% reasonable to expect a single 00:08:23.940 --> 00:08:26.390 align:start position:0% reasonable to expect a single organization<00:08:24.360> like<00:08:24.599> Bitcoin<00:08:25.139> to<00:08:25.400> really 00:08:26.390 --> 00:08:26.400 align:start position:0% organization like Bitcoin to really 00:08:26.400 --> 00:08:28.309 align:start position:0% organization like Bitcoin to really effectively<00:08:26.819> curate<00:08:27.300> who's<00:08:27.780> doing<00:08:28.020> the<00:08:28.199> work 00:08:28.309 --> 00:08:28.319 align:start position:0% effectively curate who's doing the work 00:08:28.319 --> 00:08:30.290 align:start position:0% effectively curate who's doing the work at<00:08:28.500> the<00:08:28.620> core<00:08:28.740> protocol<00:08:29.160> and<00:08:29.580> and<00:08:29.759> how<00:08:30.120> they 00:08:30.290 --> 00:08:30.300 align:start position:0% at the core protocol and and how they 00:08:30.300 --> 00:08:32.810 align:start position:0% at the core protocol and and how they should<00:08:30.419> receive<00:08:30.720> the<00:08:31.020> funding<00:08:31.339> uh<00:08:32.339> so<00:08:32.580> the 00:08:32.810 --> 00:08:32.820 align:start position:0% should receive the funding uh so the 00:08:32.820 --> 00:08:35.089 align:start position:0% should receive the funding uh so the response<00:08:33.479> to<00:08:33.719> how<00:08:34.320> to<00:08:34.440> address<00:08:34.560> this<00:08:34.860> question 00:08:35.089 --> 00:08:35.099 align:start position:0% response to how to address this question 00:08:35.099 --> 00:08:36.589 align:start position:0% response to how to address this question is 00:08:36.589 --> 00:08:36.599 align:start position:0% is 00:08:36.599 --> 00:08:39.889 align:start position:0% is um we<00:08:37.080> should<00:08:37.320> uh<00:08:38.039> designate<00:08:38.880> a<00:08:39.060> contract<00:08:39.360> on 00:08:39.889 --> 00:08:39.899 align:start position:0% um we should uh designate a contract on 00:08:39.899 --> 00:08:42.649 align:start position:0% um we should uh designate a contract on on<00:08:40.260> chain<00:08:40.560> that<00:08:41.339> is<00:08:41.520> regularly<00:08:41.940> updated<00:08:42.300> by 00:08:42.649 --> 00:08:42.659 align:start position:0% on chain that is regularly updated by 00:08:42.659 --> 00:08:44.329 align:start position:0% on chain that is regularly updated by the<00:08:42.779> the<00:08:42.959> members<00:08:43.320> themselves<00:08:43.680> so<00:08:43.919> people<00:08:44.159> who 00:08:44.329 --> 00:08:44.339 align:start position:0% the the members themselves so people who 00:08:44.339 --> 00:08:46.430 align:start position:0% the the members themselves so people who are<00:08:44.399> doing<00:08:44.580> core<00:08:44.940> contributor<00:08:45.600> work<00:08:45.779> uh 00:08:46.430 --> 00:08:46.440 align:start position:0% are doing core contributor work uh 00:08:46.440 --> 00:08:47.690 align:start position:0% are doing core contributor work uh they're<00:08:46.620> updating<00:08:47.040> this<00:08:47.339> membership 00:08:47.690 --> 00:08:47.700 align:start position:0% they're updating this membership 00:08:47.700 --> 00:08:50.210 align:start position:0% they're updating this membership registry<00:08:48.300> the<00:08:49.019> second<00:08:49.200> problem<00:08:49.620> is<00:08:49.920> that<00:08:50.040> the 00:08:50.210 --> 00:08:50.220 align:start position:0% registry the second problem is that the 00:08:50.220 --> 00:08:52.550 align:start position:0% registry the second problem is that the incentives<00:08:50.519> are<00:08:50.700> unbalanced<00:08:51.240> uh<00:08:51.899> so<00:08:52.200> this<00:08:52.380> is 00:08:52.550 --> 00:08:52.560 align:start position:0% incentives are unbalanced uh so this is 00:08:52.560 --> 00:08:54.170 align:start position:0% incentives are unbalanced uh so this is maybe<00:08:52.920> a<00:08:53.100> little<00:08:53.160> self-explanatory<00:08:53.880> but<00:08:54.060> I'll 00:08:54.170 --> 00:08:54.180 align:start position:0% maybe a little self-explanatory but I'll 00:08:54.180 --> 00:08:57.410 align:start position:0% maybe a little self-explanatory but I'll go<00:08:54.300> into<00:08:54.420> it<00:08:54.860> l2s<00:08:55.860> D5<00:08:56.339> projects<00:08:57.060> token 00:08:57.410 --> 00:08:57.420 align:start position:0% go into it l2s D5 projects token 00:08:57.420 --> 00:08:59.570 align:start position:0% go into it l2s D5 projects token projects<00:08:57.779> things<00:08:58.019> that<00:08:58.320> have<00:08:58.500> Equity<00:08:58.980> there's 00:08:59.570 --> 00:08:59.580 align:start position:0% projects things that have Equity there's 00:08:59.580 --> 00:09:02.570 align:start position:0% projects things that have Equity there's a<00:08:59.760> stronger<00:09:00.060> incentive<00:09:00.480> for<00:09:01.019> uh<00:09:01.800> people<00:09:02.040> to<00:09:02.339> go 00:09:02.570 --> 00:09:02.580 align:start position:0% a stronger incentive for uh people to go 00:09:02.580 --> 00:09:03.769 align:start position:0% a stronger incentive for uh people to go work<00:09:02.760> on<00:09:02.940> them<00:09:03.060> rather<00:09:03.300> than<00:09:03.480> the<00:09:03.660> core 00:09:03.769 --> 00:09:03.779 align:start position:0% work on them rather than the core 00:09:03.779 --> 00:09:05.990 align:start position:0% work on them rather than the core protocol<00:09:04.140> and<00:09:04.500> this<00:09:04.680> is<00:09:04.920> completely<00:09:05.640> rational 00:09:05.990 --> 00:09:06.000 align:start position:0% protocol and this is completely rational 00:09:06.000 --> 00:09:08.090 align:start position:0% protocol and this is completely rational you<00:09:06.480> know<00:09:06.540> if<00:09:06.959> you're<00:09:07.200> weighing<00:09:07.680> your<00:09:07.800> options 00:09:08.090 --> 00:09:08.100 align:start position:0% you know if you're weighing your options 00:09:08.100 --> 00:09:09.250 align:start position:0% you know if you're weighing your options here 00:09:09.250 --> 00:09:09.260 align:start position:0% here 00:09:09.260 --> 00:09:11.449 align:start position:0% here ethereum<00:09:10.260> just<00:09:10.440> doesn't<00:09:10.620> have<00:09:10.860> token 00:09:11.449 --> 00:09:11.459 align:start position:0% ethereum just doesn't have token 00:09:11.459 --> 00:09:13.670 align:start position:0% ethereum just doesn't have token incentives<00:09:11.880> or<00:09:12.240> Equity<00:09:12.600> or<00:09:12.899> anything<00:09:13.080> that 00:09:13.670 --> 00:09:13.680 align:start position:0% incentives or Equity or anything that 00:09:13.680 --> 00:09:16.430 align:start position:0% incentives or Equity or anything that can<00:09:13.860> similarly<00:09:14.279> be<00:09:14.519> offered<00:09:14.940> by<00:09:15.440> applications 00:09:16.430 --> 00:09:16.440 align:start position:0% can similarly be offered by applications 00:09:16.440 --> 00:09:19.550 align:start position:0% can similarly be offered by applications or<00:09:16.800> l2s<00:09:17.399> however<00:09:17.940> it<00:09:18.540> still<00:09:18.720> needs<00:09:18.959> to<00:09:19.080> attract 00:09:19.550 --> 00:09:19.560 align:start position:0% or l2s however it still needs to attract 00:09:19.560 --> 00:09:21.290 align:start position:0% or l2s however it still needs to attract and<00:09:19.740> retain<00:09:20.040> talent<00:09:20.399> to<00:09:20.700> evolve<00:09:21.000> the<00:09:21.120> protocol 00:09:21.290 --> 00:09:21.300 align:start position:0% and retain talent to evolve the protocol 00:09:21.300 --> 00:09:23.750 align:start position:0% and retain talent to evolve the protocol you<00:09:21.540> know<00:09:21.660> ethereum<00:09:22.080> is<00:09:22.459> uh<00:09:23.459> an 00:09:23.750 --> 00:09:23.760 align:start position:0% you know ethereum is uh an 00:09:23.760 --> 00:09:25.670 align:start position:0% you know ethereum is uh an infrastructure<00:09:24.360> influx<00:09:24.959> there's<00:09:25.200> a<00:09:25.440> lot<00:09:25.560> of 00:09:25.670 --> 00:09:25.680 align:start position:0% infrastructure influx there's a lot of 00:09:25.680 --> 00:09:27.889 align:start position:0% infrastructure influx there's a lot of changes<00:09:26.040> that<00:09:26.279> we'd<00:09:26.459> like<00:09:26.580> to<00:09:26.760> make<00:09:26.880> to<00:09:27.240> better 00:09:27.889 --> 00:09:27.899 align:start position:0% changes that we'd like to make to better 00:09:27.899 --> 00:09:30.889 align:start position:0% changes that we'd like to make to better scale<00:09:28.380> to<00:09:28.680> become<00:09:28.920> more<00:09:29.160> secure<00:09:29.540> and<00:09:30.540> we<00:09:30.720> need 00:09:30.889 --> 00:09:30.899 align:start position:0% scale to become more secure and we need 00:09:30.899 --> 00:09:32.750 align:start position:0% scale to become more secure and we need we<00:09:31.500> need<00:09:31.620> really<00:09:31.800> smart<00:09:32.040> people<00:09:32.220> working<00:09:32.519> on 00:09:32.750 --> 00:09:32.760 align:start position:0% we need really smart people working on 00:09:32.760 --> 00:09:34.490 align:start position:0% we need really smart people working on these<00:09:32.940> problems<00:09:33.360> but<00:09:33.839> we<00:09:34.140> should<00:09:34.320> be 00:09:34.490 --> 00:09:34.500 align:start position:0% these problems but we should be 00:09:34.500 --> 00:09:35.870 align:start position:0% these problems but we should be compensating<00:09:34.980> them<00:09:35.160> fairly<00:09:35.399> it's<00:09:35.580> totally 00:09:35.870 --> 00:09:35.880 align:start position:0% compensating them fairly it's totally 00:09:35.880 --> 00:09:38.630 align:start position:0% compensating them fairly it's totally rational<00:09:36.180> to<00:09:36.540> pursue<00:09:36.899> something<00:09:37.200> with 00:09:38.630 --> 00:09:38.640 align:start position:0% rational to pursue something with 00:09:38.640 --> 00:09:40.070 align:start position:0% rational to pursue something with um you<00:09:38.820> know<00:09:38.880> greater<00:09:39.300> Financial<00:09:39.420> upside<00:09:39.839> and 00:09:40.070 --> 00:09:40.080 align:start position:0% um you know greater Financial upside and 00:09:40.080 --> 00:09:42.170 align:start position:0% um you know greater Financial upside and I<00:09:40.200> don't<00:09:40.320> follow<00:09:40.500> people<00:09:40.740> for<00:09:40.980> that<00:09:41.160> or<00:09:41.880> for 00:09:42.170 --> 00:09:42.180 align:start position:0% I don't follow people for that or for 00:09:42.180 --> 00:09:44.449 align:start position:0% I don't follow people for that or for other<00:09:42.420> protocols<00:09:43.080> leveraging<00:09:43.740> these<00:09:44.100> these 00:09:44.449 --> 00:09:44.459 align:start position:0% other protocols leveraging these these 00:09:44.459 --> 00:09:46.550 align:start position:0% other protocols leveraging these these incentives<00:09:44.820> however<00:09:45.540> as<00:09:45.899> the<00:09:46.140> broader 00:09:46.550 --> 00:09:46.560 align:start position:0% incentives however as the broader 00:09:46.560 --> 00:09:48.889 align:start position:0% incentives however as the broader ecosystem<00:09:47.279> continues<00:09:47.820> to<00:09:47.940> grow<00:09:48.120> competition 00:09:48.889 --> 00:09:48.899 align:start position:0% ecosystem continues to grow competition 00:09:48.899 --> 00:09:51.170 align:start position:0% ecosystem continues to grow competition for<00:09:49.140> these<00:09:49.380> talented<00:09:49.740> individuals<00:09:50.339> is<00:09:50.880> really 00:09:51.170 --> 00:09:51.180 align:start position:0% for these talented individuals is really 00:09:51.180 --> 00:09:52.930 align:start position:0% for these talented individuals is really going<00:09:51.360> to<00:09:51.600> only<00:09:51.959> increase 00:09:52.930 --> 00:09:52.940 align:start position:0% going to only increase 00:09:52.940 --> 00:09:55.730 align:start position:0% going to only increase of<00:09:53.940> course<00:09:54.060> Financial<00:09:54.720> motivations<00:09:55.260> aren't 00:09:55.730 --> 00:09:55.740 align:start position:0% of course Financial motivations aren't 00:09:55.740 --> 00:09:58.190 align:start position:0% of course Financial motivations aren't the<00:09:56.040> only<00:09:56.220> or<00:09:56.459> best<00:09:56.700> motivator<00:09:57.180> for<00:09:57.420> people<00:09:57.600> we 00:09:58.190 --> 00:09:58.200 align:start position:0% the only or best motivator for people we 00:09:58.200 --> 00:10:01.009 align:start position:0% the only or best motivator for people we just<00:09:58.260> want<00:09:58.440> to<00:09:58.560> recognize<00:09:58.920> that<00:09:59.839> it's<00:10:00.839> just 00:10:01.009 --> 00:10:01.019 align:start position:0% just want to recognize that it's just 00:10:01.019 --> 00:10:02.570 align:start position:0% just want to recognize that it's just one<00:10:01.200> tool<00:10:01.500> in<00:10:01.740> our<00:10:01.860> tool<00:10:02.100> set<00:10:02.220> that's<00:10:02.399> being 00:10:02.570 --> 00:10:02.580 align:start position:0% one tool in our tool set that's being 00:10:02.580 --> 00:10:04.610 align:start position:0% one tool in our tool set that's being under<00:10:02.700> leverage<00:10:03.060> so<00:10:03.480> the<00:10:04.080> problem<00:10:04.260> of 00:10:04.610 --> 00:10:04.620 align:start position:0% under leverage so the problem of 00:10:04.620 --> 00:10:07.449 align:start position:0% under leverage so the problem of imbalance<00:10:05.220> we<00:10:05.640> can<00:10:05.820> address<00:10:05.940> this<00:10:06.300> by 00:10:07.449 --> 00:10:07.459 align:start position:0% imbalance we can address this by 00:10:07.459 --> 00:10:11.150 align:start position:0% imbalance we can address this by tapping<00:10:08.459> into<00:10:08.820> the<00:10:09.480> the<00:10:09.839> financial<00:10:10.740> value 00:10:11.150 --> 00:10:11.160 align:start position:0% tapping into the the financial value 00:10:11.160 --> 00:10:12.769 align:start position:0% tapping into the the financial value that<00:10:11.459> all<00:10:11.640> of<00:10:11.760> these<00:10:11.940> amazing<00:10:12.240> projects<00:10:12.600> are 00:10:12.769 --> 00:10:12.779 align:start position:0% that all of these amazing projects are 00:10:12.779 --> 00:10:14.329 align:start position:0% that all of these amazing projects are building<00:10:12.899> on<00:10:13.140> top<00:10:13.260> of<00:10:13.380> ethereum<00:10:13.860> and<00:10:14.160> getting 00:10:14.329 --> 00:10:14.339 align:start position:0% building on top of ethereum and getting 00:10:14.339 --> 00:10:16.130 align:start position:0% building on top of ethereum and getting them<00:10:14.580> to<00:10:14.760> contribute<00:10:15.120> some<00:10:15.360> of<00:10:15.480> them<00:10:15.600> back<00:10:15.839> to 00:10:16.130 --> 00:10:16.140 align:start position:0% them to contribute some of them back to 00:10:16.140 --> 00:10:17.389 align:start position:0% them to contribute some of them back to the<00:10:16.440> people<00:10:16.620> who<00:10:16.740> are<00:10:16.920> working<00:10:17.040> on<00:10:17.220> the<00:10:17.339> core 00:10:17.389 --> 00:10:17.399 align:start position:0% the people who are working on the core 00:10:17.399 --> 00:10:19.910 align:start position:0% the people who are working on the core protocol<00:10:17.820> the<00:10:18.360> third<00:10:18.480> challenge<00:10:18.779> uh<00:10:19.500> exclu 00:10:19.910 --> 00:10:19.920 align:start position:0% protocol the third challenge uh exclu 00:10:19.920 --> 00:10:22.610 align:start position:0% protocol the third challenge uh exclu excuse<00:10:20.459> my<00:10:20.880> rushed<00:10:21.420> Graphics<00:10:21.839> here<00:10:22.019> but<00:10:22.260> the 00:10:22.610 --> 00:10:22.620 align:start position:0% excuse my rushed Graphics here but the 00:10:22.620 --> 00:10:24.230 align:start position:0% excuse my rushed Graphics here but the contributor<00:10:22.980> churn<00:10:23.279> is<00:10:23.580> a<00:10:23.700> challenge<00:10:23.880> when<00:10:24.120> it 00:10:24.230 --> 00:10:24.240 align:start position:0% contributor churn is a challenge when it 00:10:24.240 --> 00:10:26.329 align:start position:0% contributor churn is a challenge when it comes<00:10:24.360> to<00:10:24.480> the<00:10:24.540> core<00:10:24.660> protocol<00:10:25.080> it<00:10:25.980> can<00:10:26.160> take 00:10:26.329 --> 00:10:26.339 align:start position:0% comes to the core protocol it can take 00:10:26.339 --> 00:10:28.070 align:start position:0% comes to the core protocol it can take you<00:10:26.640> know<00:10:26.700> six<00:10:26.940> to<00:10:27.120> 12<00:10:27.240> months<00:10:27.660> for<00:10:27.899> somebody 00:10:28.070 --> 00:10:28.080 align:start position:0% you know six to 12 months for somebody 00:10:28.080 --> 00:10:31.130 align:start position:0% you know six to 12 months for somebody joining<00:10:28.620> a<00:10:28.920> client<00:10:29.100> team<00:10:29.339> to<00:10:29.760> really<00:10:30.360> start<00:10:30.720> to 00:10:31.130 --> 00:10:31.140 align:start position:0% joining a client team to really start to 00:10:31.140 --> 00:10:33.410 align:start position:0% joining a client team to really start to understand<00:10:31.620> how<00:10:32.399> that<00:10:32.640> they<00:10:32.940> can<00:10:33.060> contribute 00:10:33.410 --> 00:10:33.420 align:start position:0% understand how that they can contribute 00:10:33.420 --> 00:10:35.750 align:start position:0% understand how that they can contribute to<00:10:33.540> the<00:10:33.660> client<00:10:33.839> effectively<00:10:34.580> and<00:10:35.580> start 00:10:35.750 --> 00:10:35.760 align:start position:0% to the client effectively and start 00:10:35.760 --> 00:10:37.910 align:start position:0% to the client effectively and start making<00:10:36.120> a<00:10:36.720> meaningful<00:10:37.019> impact<00:10:37.380> on<00:10:37.620> the<00:10:37.800> work 00:10:37.910 --> 00:10:37.920 align:start position:0% making a meaningful impact on the work 00:10:37.920 --> 00:10:39.590 align:start position:0% making a meaningful impact on the work so<00:10:38.399> there's<00:10:38.519> a<00:10:38.760> steep<00:10:38.940> learning<00:10:39.240> curve<00:10:39.480> for 00:10:39.590 --> 00:10:39.600 align:start position:0% so there's a steep learning curve for 00:10:39.600 --> 00:10:41.470 align:start position:0% so there's a steep learning curve for new<00:10:39.779> contributors<00:10:40.200> to<00:10:40.440> to<00:10:40.680> deliver<00:10:40.920> value 00:10:41.470 --> 00:10:41.480 align:start position:0% new contributors to to deliver value 00:10:41.480 --> 00:10:44.090 align:start position:0% new contributors to to deliver value however<00:10:42.480> the<00:10:42.899> contributor<00:10:43.380> value<00:10:43.620> does<00:10:43.920> grow 00:10:44.090 --> 00:10:44.100 align:start position:0% however the contributor value does grow 00:10:44.100 --> 00:10:46.550 align:start position:0% however the contributor value does grow over<00:10:44.279> time<00:10:44.519> if<00:10:44.760> you<00:10:44.880> stick<00:10:45.060> around<00:10:45.560> but 00:10:46.550 --> 00:10:46.560 align:start position:0% over time if you stick around but 00:10:46.560 --> 00:10:47.870 align:start position:0% over time if you stick around but there's<00:10:46.680> less<00:10:46.860> incentives<00:10:47.339> to<00:10:47.519> stick<00:10:47.700> around 00:10:47.870 --> 00:10:47.880 align:start position:0% there's less incentives to stick around 00:10:47.880 --> 00:10:50.930 align:start position:0% there's less incentives to stick around if<00:10:48.540> you're<00:10:49.079> once<00:10:49.860> you're<00:10:49.980> an<00:10:50.100> expert<00:10:50.399> you<00:10:50.760> you 00:10:50.930 --> 00:10:50.940 align:start position:0% if you're once you're an expert you you 00:10:50.940 --> 00:10:52.310 align:start position:0% if you're once you're an expert you you sort<00:10:51.180> of<00:10:51.240> reach<00:10:51.540> a<00:10:51.660> certain<00:10:51.779> level<00:10:52.019> of 00:10:52.310 --> 00:10:52.320 align:start position:0% sort of reach a certain level of 00:10:52.320 --> 00:10:54.650 align:start position:0% sort of reach a certain level of expertise<00:10:53.160> with<00:10:53.519> a<00:10:53.760> client<00:10:53.940> code<00:10:54.120> base<00:10:54.360> for 00:10:54.650 --> 00:10:54.660 align:start position:0% expertise with a client code base for 00:10:54.660 --> 00:10:57.290 align:start position:0% expertise with a client code base for example<00:10:54.899> so<00:10:55.860> one<00:10:56.399> of<00:10:56.519> the<00:10:56.579> things<00:10:56.760> we<00:10:57.060> thought 00:10:57.290 --> 00:10:57.300 align:start position:0% example so one of the things we thought 00:10:57.300 --> 00:10:59.449 align:start position:0% example so one of the things we thought about<00:10:57.480> how<00:10:57.899> to<00:10:58.019> address<00:10:58.200> this<00:10:58.680> contributor 00:10:59.449 --> 00:10:59.459 align:start position:0% about how to address this contributor 00:10:59.459 --> 00:11:02.150 align:start position:0% about how to address this contributor churn<00:10:59.700> is<00:11:00.540> that<00:11:00.839> membership<00:11:01.200> eligibility<00:11:01.800> to 00:11:02.150 --> 00:11:02.160 align:start position:0% churn is that membership eligibility to 00:11:02.160 --> 00:11:03.710 align:start position:0% churn is that membership eligibility to any<00:11:02.399> sort<00:11:02.579> of<00:11:02.640> public<00:11:03.060> goods<00:11:03.480> funding 00:11:03.710 --> 00:11:03.720 align:start position:0% any sort of public goods funding 00:11:03.720 --> 00:11:05.930 align:start position:0% any sort of public goods funding mechanism<00:11:04.079> it<00:11:04.620> should<00:11:04.740> only<00:11:04.920> be<00:11:05.160> after<00:11:05.640> six 00:11:05.930 --> 00:11:05.940 align:start position:0% mechanism it should only be after six 00:11:05.940 --> 00:11:08.269 align:start position:0% mechanism it should only be after six months<00:11:06.180> of<00:11:06.300> regular<00:11:06.600> contributions<00:11:07.200> and<00:11:08.100> that 00:11:08.269 --> 00:11:08.279 align:start position:0% months of regular contributions and that 00:11:08.279 --> 00:11:10.490 align:start position:0% months of regular contributions and that assets<00:11:08.519> should<00:11:09.000> invest<00:11:09.540> over<00:11:09.839> time<00:11:10.079> in<00:11:10.380> order 00:11:10.490 --> 00:11:10.500 align:start position:0% assets should invest over time in order 00:11:10.500 --> 00:11:14.690 align:start position:0% assets should invest over time in order to<00:11:10.740> incentivize<00:11:11.279> this<00:11:12.140> to<00:11:13.140> incentivize<00:11:13.700> this 00:11:14.690 --> 00:11:14.700 align:start position:0% to incentivize this to incentivize this 00:11:14.700 --> 00:11:15.889 align:start position:0% to incentivize this to incentivize this knowledge<00:11:15.000> transfer<00:11:15.420> between<00:11:15.600> different 00:11:15.889 --> 00:11:15.899 align:start position:0% knowledge transfer between different 00:11:15.899 --> 00:11:18.350 align:start position:0% knowledge transfer between different cohorts<00:11:16.500> different<00:11:17.100> uh<00:11:17.640> generations<00:11:18.060> of 00:11:18.350 --> 00:11:18.360 align:start position:0% cohorts different uh generations of 00:11:18.360 --> 00:11:19.790 align:start position:0% cohorts different uh generations of people<00:11:18.540> working<00:11:18.839> on<00:11:19.019> the<00:11:19.140> core<00:11:19.260> protocol<00:11:19.560> you 00:11:19.790 --> 00:11:19.800 align:start position:0% people working on the core protocol you 00:11:19.800 --> 00:11:22.069 align:start position:0% people working on the core protocol you know<00:11:19.980> there<00:11:20.760> are<00:11:20.940> some<00:11:21.360> amazing<00:11:21.660> people<00:11:21.779> doing 00:11:22.069 --> 00:11:22.079 align:start position:0% know there are some amazing people doing 00:11:22.079 --> 00:11:24.889 align:start position:0% know there are some amazing people doing work<00:11:22.320> today<00:11:22.620> that<00:11:23.399> maintain<00:11:23.820> clients<00:11:24.420> and 00:11:24.889 --> 00:11:24.899 align:start position:0% work today that maintain clients and 00:11:24.899 --> 00:11:26.690 align:start position:0% work today that maintain clients and make<00:11:25.260> ethereum<00:11:25.740> infrastructure<00:11:26.279> in<00:11:26.519> the 00:11:26.690 --> 00:11:26.700 align:start position:0% make ethereum infrastructure in the 00:11:26.700 --> 00:11:28.370 align:start position:0% make ethereum infrastructure in the protocol<00:11:26.880> possible<00:11:27.360> but<00:11:27.899> eventually<00:11:28.140> they're 00:11:28.370 --> 00:11:28.380 align:start position:0% protocol possible but eventually they're 00:11:28.380 --> 00:11:30.769 align:start position:0% protocol possible but eventually they're going<00:11:28.500> to<00:11:28.620> move<00:11:28.740> on<00:11:28.920> or<00:11:29.339> retire<00:11:29.820> if<00:11:30.660> we're 00:11:30.769 --> 00:11:30.779 align:start position:0% going to move on or retire if we're 00:11:30.779 --> 00:11:33.230 align:start position:0% going to move on or retire if we're still<00:11:30.959> around<00:11:31.140> in<00:11:31.560> so<00:11:31.680> many<00:11:31.800> years<00:11:32.120> and<00:11:33.120> we 00:11:33.230 --> 00:11:33.240 align:start position:0% still around in so many years and we 00:11:33.240 --> 00:11:34.190 align:start position:0% still around in so many years and we need<00:11:33.300> to<00:11:33.420> make<00:11:33.540> sure<00:11:33.660> that<00:11:33.839> the<00:11:34.019> next 00:11:34.190 --> 00:11:34.200 align:start position:0% need to make sure that the next 00:11:34.200 --> 00:11:36.170 align:start position:0% need to make sure that the next generation<00:11:34.680> of<00:11:35.279> people<00:11:35.640> that<00:11:35.880> are<00:11:36.000> going<00:11:36.120> to 00:11:36.170 --> 00:11:36.180 align:start position:0% generation of people that are going to 00:11:36.180 --> 00:11:38.150 align:start position:0% generation of people that are going to be<00:11:36.240> maintaining<00:11:36.660> this<00:11:36.899> software<00:11:37.380> are<00:11:37.980> ready 00:11:38.150 --> 00:11:38.160 align:start position:0% be maintaining this software are ready 00:11:38.160 --> 00:11:39.829 align:start position:0% be maintaining this software are ready and<00:11:38.700> incentivized<00:11:39.420> to<00:11:39.540> stick<00:11:39.660> around 00:11:39.829 --> 00:11:39.839 align:start position:0% and incentivized to stick around 00:11:39.839 --> 00:11:42.410 align:start position:0% and incentivized to stick around similarly<00:11:40.440> so<00:11:41.160> as<00:11:41.640> you<00:11:41.820> may<00:11:41.880> have<00:11:42.060> guessed<00:11:42.300> I'm 00:11:42.410 --> 00:11:42.420 align:start position:0% similarly so as you may have guessed I'm 00:11:42.420 --> 00:11:43.970 align:start position:0% similarly so as you may have guessed I'm describing<00:11:42.779> the<00:11:42.959> protocol<00:11:43.200> Guild<00:11:43.500> which 00:11:43.970 --> 00:11:43.980 align:start position:0% describing the protocol Guild which 00:11:43.980 --> 00:11:46.550 align:start position:0% describing the protocol Guild which started<00:11:44.700> as<00:11:44.880> an<00:11:45.000> idea<00:11:45.300> last<00:11:45.480> November<00:11:46.019> and 00:11:46.550 --> 00:11:46.560 align:start position:0% started as an idea last November and 00:11:46.560 --> 00:11:48.710 align:start position:0% started as an idea last November and we've<00:11:46.800> been<00:11:46.920> building<00:11:47.160> it<00:11:47.459> since<00:11:47.760> then<00:11:48.000> we 00:11:48.710 --> 00:11:48.720 align:start position:0% we've been building it since then we 00:11:48.720 --> 00:11:50.690 align:start position:0% we've been building it since then we worked<00:11:49.019> with<00:11:49.140> a<00:11:49.380> team<00:11:49.500> called<00:11:49.680> Xerox<00:11:50.100> splits 00:11:50.690 --> 00:11:50.700 align:start position:0% worked with a team called Xerox splits 00:11:50.700 --> 00:11:54.110 align:start position:0% worked with a team called Xerox splits to<00:11:51.320> design<00:11:52.320> well<00:11:52.740> they<00:11:52.980> already<00:11:53.339> had<00:11:53.579> a<00:11:53.820> split 00:11:54.110 --> 00:11:54.120 align:start position:0% to design well they already had a split 00:11:54.120 --> 00:11:56.030 align:start position:0% to design well they already had a split contract<00:11:54.480> but<00:11:54.959> we<00:11:55.320> worked<00:11:55.620> with<00:11:55.740> them<00:11:55.860> to 00:11:56.030 --> 00:11:56.040 align:start position:0% contract but we worked with them to 00:11:56.040 --> 00:11:59.090 align:start position:0% contract but we worked with them to design<00:11:56.160> a<00:11:56.399> vesting<00:11:56.760> contract<00:11:57.380> and<00:11:58.380> it's<00:11:58.860> a 00:11:59.090 --> 00:11:59.100 align:start position:0% design a vesting contract and it's a 00:11:59.100 --> 00:12:01.370 align:start position:0% design a vesting contract and it's a collective<00:11:59.459> of<00:11:59.880> today<00:12:00.000> 119<00:12:00.779> ethereum 00:12:01.370 --> 00:12:01.380 align:start position:0% collective of today 119 ethereum 00:12:01.380 --> 00:12:03.410 align:start position:0% collective of today 119 ethereum contributors<00:12:01.920> and<00:12:02.579> we're<00:12:02.760> working<00:12:03.000> to 00:12:03.410 --> 00:12:03.420 align:start position:0% contributors and we're working to 00:12:03.420 --> 00:12:05.090 align:start position:0% contributors and we're working to rebalance<00:12:04.019> the<00:12:04.140> incentive<00:12:04.500> address<00:12:04.740> all 00:12:05.090 --> 00:12:05.100 align:start position:0% rebalance the incentive address all 00:12:05.100 --> 00:12:06.710 align:start position:0% rebalance the incentive address all those<00:12:05.220> challenges<00:12:05.579> like<00:12:05.880> I<00:12:06.060> laid<00:12:06.480> out<00:12:06.600> in 00:12:06.710 --> 00:12:06.720 align:start position:0% those challenges like I laid out in 00:12:06.720 --> 00:12:08.630 align:start position:0% those challenges like I laid out in those<00:12:06.899> previous<00:12:07.079> slides<00:12:07.620> and<00:12:08.160> here's<00:12:08.459> a<00:12:08.519> very 00:12:08.630 --> 00:12:08.640 align:start position:0% those previous slides and here's a very 00:12:08.640 --> 00:12:12.410 align:start position:0% those previous slides and here's a very simple<00:12:08.940> diagram<00:12:09.800> the<00:12:10.800> sponsors<00:12:11.220> these<00:12:12.180> can<00:12:12.300> be 00:12:12.410 --> 00:12:12.420 align:start position:0% simple diagram the sponsors these can be 00:12:12.420 --> 00:12:14.630 align:start position:0% simple diagram the sponsors these can be anybody<00:12:13.079> in<00:12:13.260> the<00:12:13.380> ecosystem<00:12:13.740> individuals 00:12:14.630 --> 00:12:14.640 align:start position:0% anybody in the ecosystem individuals 00:12:14.640 --> 00:12:17.269 align:start position:0% anybody in the ecosystem individuals projects<00:12:15.480> large<00:12:15.959> scale<00:12:16.320> small<00:12:16.800> doesn't 00:12:17.269 --> 00:12:17.279 align:start position:0% projects large scale small doesn't 00:12:17.279 --> 00:12:18.949 align:start position:0% projects large scale small doesn't matter<00:12:17.579> anybody<00:12:18.240> who's<00:12:18.360> interested<00:12:18.839> in 00:12:18.949 --> 00:12:18.959 align:start position:0% matter anybody who's interested in 00:12:18.959 --> 00:12:21.470 align:start position:0% matter anybody who's interested in giving<00:12:19.200> back<00:12:19.500> to<00:12:19.920> a<00:12:20.399> really<00:12:20.519> highly<00:12:21.000> curated 00:12:21.470 --> 00:12:21.480 align:start position:0% giving back to a really highly curated 00:12:21.480 --> 00:12:24.230 align:start position:0% giving back to a really highly curated set<00:12:22.320> of<00:12:22.560> core<00:12:22.740> protocol<00:12:23.160> contributors<00:12:23.700> they 00:12:24.230 --> 00:12:24.240 align:start position:0% set of core protocol contributors they 00:12:24.240 --> 00:12:26.329 align:start position:0% set of core protocol contributors they send<00:12:24.480> funds<00:12:24.959> in<00:12:25.320> whatever<00:12:25.500> form<00:12:25.860> they<00:12:26.100> are<00:12:26.160> to 00:12:26.329 --> 00:12:26.339 align:start position:0% send funds in whatever form they are to 00:12:26.339 --> 00:12:28.610 align:start position:0% send funds in whatever form they are to investing<00:12:26.760> contract<00:12:27.180> over<00:12:28.079> a<00:12:28.260> certain<00:12:28.380> amount 00:12:28.610 --> 00:12:28.620 align:start position:0% investing contract over a certain amount 00:12:28.620 --> 00:12:30.470 align:start position:0% investing contract over a certain amount of<00:12:28.800> time<00:12:28.980> and<00:12:29.459> then<00:12:29.820> it<00:12:30.000> goes<00:12:30.240> to<00:12:30.300> this 00:12:30.470 --> 00:12:30.480 align:start position:0% of time and then it goes to this 00:12:30.480 --> 00:12:32.509 align:start position:0% of time and then it goes to this weighted<00:12:30.899> registry<00:12:31.380> which<00:12:31.860> is<00:12:32.040> regularly 00:12:32.509 --> 00:12:32.519 align:start position:0% weighted registry which is regularly 00:12:32.519 --> 00:12:35.810 align:start position:0% weighted registry which is regularly updated<00:12:32.940> by<00:12:33.480> the<00:12:34.140> the<00:12:34.320> membership<00:12:34.740> itself<00:12:35.160> and 00:12:35.810 --> 00:12:35.820 align:start position:0% updated by the the membership itself and 00:12:35.820 --> 00:12:37.490 align:start position:0% updated by the the membership itself and that's<00:12:36.000> the<00:12:36.240> key<00:12:36.360> that<00:12:36.779> it's<00:12:36.899> self-curated 00:12:37.490 --> 00:12:37.500 align:start position:0% that's the key that it's self-curated 00:12:37.500 --> 00:12:39.170 align:start position:0% that's the key that it's self-curated because<00:12:37.980> you<00:12:38.220> know<00:12:38.339> you<00:12:38.459> have<00:12:38.640> a<00:12:38.820> really<00:12:38.880> high 00:12:39.170 --> 00:12:39.180 align:start position:0% because you know you have a really high 00:12:39.180 --> 00:12:43.009 align:start position:0% because you know you have a really high signal<00:12:39.660> for<00:12:40.560> the<00:12:41.519> membership<00:12:41.820> and<00:12:42.540> the<00:12:42.899> fact 00:12:43.009 --> 00:12:43.019 align:start position:0% signal for the membership and the fact 00:12:43.019 --> 00:12:44.329 align:start position:0% signal for the membership and the fact that<00:12:43.200> you<00:12:43.320> know<00:12:43.440> that<00:12:43.620> these<00:12:43.800> are<00:12:43.920> people<00:12:44.100> who 00:12:44.329 --> 00:12:44.339 align:start position:0% that you know that these are people who 00:12:44.339 --> 00:12:46.310 align:start position:0% that you know that these are people who are<00:12:44.459> doing<00:12:44.700> really<00:12:45.300> crucial<00:12:45.600> work<00:12:45.839> I'll<00:12:46.079> dive 00:12:46.310 --> 00:12:46.320 align:start position:0% are doing really crucial work I'll dive 00:12:46.320 --> 00:12:48.170 align:start position:0% are doing really crucial work I'll dive in<00:12:46.440> a<00:12:46.620> little<00:12:46.680> bit<00:12:46.800> into<00:12:47.339> eligibility<00:12:47.880> and 00:12:48.170 --> 00:12:48.180 align:start position:0% in a little bit into eligibility and 00:12:48.180 --> 00:12:50.210 align:start position:0% in a little bit into eligibility and self-curation<00:12:48.720> like<00:12:48.959> I<00:12:49.079> mentioned<00:12:49.380> to<00:12:50.040> be 00:12:50.210 --> 00:12:50.220 align:start position:0% self-curation like I mentioned to be 00:12:50.220 --> 00:12:52.430 align:start position:0% self-curation like I mentioned to be part<00:12:50.459> of<00:12:50.579> the<00:12:50.760> protocol<00:12:51.060> Guild<00:12:51.420> it<00:12:51.899> it<00:12:52.079> has<00:12:52.320> to 00:12:52.430 --> 00:12:52.440 align:start position:0% part of the protocol Guild it it has to 00:12:52.440 --> 00:12:54.829 align:start position:0% part of the protocol Guild it it has to be<00:12:52.620> you<00:12:52.980> know<00:12:53.040> something<00:12:53.519> Beyond<00:12:53.940> a<00:12:54.120> typo<00:12:54.420> in<00:12:54.660> a 00:12:54.829 --> 00:12:54.839 align:start position:0% be you know something Beyond a typo in a 00:12:54.839 --> 00:12:56.990 align:start position:0% be you know something Beyond a typo in a client<00:12:54.959> code<00:12:55.139> base<00:12:55.380> or<00:12:55.620> something<00:12:55.860> and<00:12:56.639> Beyond 00:12:56.990 --> 00:12:57.000 align:start position:0% client code base or something and Beyond 00:12:57.000 --> 00:12:59.389 align:start position:0% client code base or something and Beyond six<00:12:57.240> months<00:12:57.740> we<00:12:58.740> want<00:12:58.860> to<00:12:58.980> make<00:12:59.040> sure<00:12:59.160> there's 00:12:59.389 --> 00:12:59.399 align:start position:0% six months we want to make sure there's 00:12:59.399 --> 00:13:00.769 align:start position:0% six months we want to make sure there's a<00:12:59.579> there's<00:12:59.760> a<00:12:59.880> high<00:13:00.000> threshold<00:13:00.420> for<00:13:00.660> people 00:13:00.769 --> 00:13:00.779 align:start position:0% a there's a high threshold for people 00:13:00.779 --> 00:13:02.269 align:start position:0% a there's a high threshold for people who<00:13:01.019> are<00:13:01.139> actually<00:13:01.320> really<00:13:01.560> committed<00:13:01.980> to 00:13:02.269 --> 00:13:02.279 align:start position:0% who are actually really committed to 00:13:02.279 --> 00:13:05.569 align:start position:0% who are actually really committed to this<00:13:02.820> infrastructure<00:13:03.360> work<00:13:03.740> and<00:13:04.740> touching<00:13:05.459> on 00:13:05.569 --> 00:13:05.579 align:start position:0% this infrastructure work and touching on 00:13:05.579 --> 00:13:07.790 align:start position:0% this infrastructure work and touching on self-curation<00:13:06.180> again<00:13:06.480> the<00:13:07.260> the<00:13:07.380> reason<00:13:07.560> this 00:13:07.790 --> 00:13:07.800 align:start position:0% self-curation again the the reason this 00:13:07.800 --> 00:13:09.650 align:start position:0% self-curation again the the reason this is<00:13:07.980> super<00:13:08.160> important<00:13:08.519> is<00:13:08.639> because<00:13:08.880> it<00:13:09.300> avoids 00:13:09.650 --> 00:13:09.660 align:start position:0% is super important is because it avoids 00:13:09.660 --> 00:13:12.050 align:start position:0% is super important is because it avoids intermediation<00:13:10.380> between<00:13:11.160> external<00:13:11.700> curating 00:13:12.050 --> 00:13:12.060 align:start position:0% intermediation between external curating 00:13:12.060 --> 00:13:14.629 align:start position:0% intermediation between external curating entities<00:13:12.540> which<00:13:13.500> may<00:13:13.740> or<00:13:13.860> may<00:13:14.040> not<00:13:14.160> be<00:13:14.339> really 00:13:14.629 --> 00:13:14.639 align:start position:0% entities which may or may not be really 00:13:14.639 --> 00:13:16.190 align:start position:0% entities which may or may not be really close<00:13:14.880> to<00:13:15.120> the<00:13:15.300> work<00:13:15.420> that<00:13:15.660> people<00:13:15.779> are<00:13:16.019> doing 00:13:16.190 --> 00:13:16.200 align:start position:0% close to the work that people are doing 00:13:16.200 --> 00:13:18.530 align:start position:0% close to the work that people are doing so<00:13:16.560> like<00:13:16.980> I<00:13:17.100> said<00:13:17.220> you<00:13:17.399> get<00:13:17.579> a<00:13:17.940> really<00:13:18.120> high 00:13:18.530 --> 00:13:18.540 align:start position:0% so like I said you get a really high 00:13:18.540 --> 00:13:21.650 align:start position:0% so like I said you get a really high signal<00:13:19.019> curation<00:13:19.639> and<00:13:20.639> you<00:13:20.820> can<00:13:20.940> be<00:13:21.300> assured 00:13:21.650 --> 00:13:21.660 align:start position:0% signal curation and you can be assured 00:13:21.660 --> 00:13:22.910 align:start position:0% signal curation and you can be assured that<00:13:21.779> this<00:13:21.959> is<00:13:22.079> going<00:13:22.200> to<00:13:22.320> be<00:13:22.380> consistently 00:13:22.910 --> 00:13:22.920 align:start position:0% that this is going to be consistently 00:13:22.920 --> 00:13:25.790 align:start position:0% that this is going to be consistently updated<00:13:23.220> over<00:13:23.519> time<00:13:23.820> with<00:13:24.779> a<00:13:25.320> membership 00:13:25.790 --> 00:13:25.800 align:start position:0% updated over time with a membership 00:13:25.800 --> 00:13:27.230 align:start position:0% updated over time with a membership that's<00:13:26.160> really<00:13:26.399> contributing<00:13:26.880> to<00:13:27.000> the<00:13:27.120> core 00:13:27.230 --> 00:13:27.240 align:start position:0% that's really contributing to the core 00:13:27.240 --> 00:13:29.150 align:start position:0% that's really contributing to the core protocol<00:13:27.600> and<00:13:28.139> it's<00:13:28.260> incentive<00:13:28.740> compatible 00:13:29.150 --> 00:13:29.160 align:start position:0% protocol and it's incentive compatible 00:13:29.160 --> 00:13:30.069 align:start position:0% protocol and it's incentive compatible because 00:13:30.069 --> 00:13:30.079 align:start position:0% because 00:13:30.079 --> 00:13:32.509 align:start position:0% because adding<00:13:31.079> new<00:13:31.200> members<00:13:31.440> dilutes<00:13:31.920> existing<00:13:32.279> ones 00:13:32.509 --> 00:13:32.519 align:start position:0% adding new members dilutes existing ones 00:13:32.519 --> 00:13:36.050 align:start position:0% adding new members dilutes existing ones so<00:13:32.880> you<00:13:33.839> don't<00:13:33.899> have<00:13:34.079> to<00:13:34.260> worry<00:13:34.440> about<00:13:35.060> new 00:13:36.050 --> 00:13:36.060 align:start position:0% so you don't have to worry about new 00:13:36.060 --> 00:13:37.329 align:start position:0% so you don't have to worry about new members 00:13:37.329 --> 00:13:37.339 align:start position:0% members 00:13:37.339 --> 00:13:39.949 align:start position:0% members just<00:13:38.339> adding<00:13:38.760> anybody<00:13:39.180> in<00:13:39.420> the<00:13:39.540> ecosystem 00:13:39.949 --> 00:13:39.959 align:start position:0% just adding anybody in the ecosystem 00:13:39.959 --> 00:13:42.829 align:start position:0% just adding anybody in the ecosystem there's<00:13:40.860> a<00:13:41.100> cost<00:13:41.279> to<00:13:41.820> properly<00:13:42.420> curating 00:13:42.829 --> 00:13:42.839 align:start position:0% there's a cost to properly curating 00:13:42.839 --> 00:13:46.009 align:start position:0% there's a cost to properly curating however<00:13:43.620> if<00:13:44.519> eligible<00:13:45.000> contributors<00:13:45.540> are<00:13:45.839> not 00:13:46.009 --> 00:13:46.019 align:start position:0% however if eligible contributors are not 00:13:46.019 --> 00:13:47.690 align:start position:0% however if eligible contributors are not being<00:13:46.260> added<00:13:46.680> then<00:13:46.980> it<00:13:47.220> removes<00:13:47.519> any 00:13:47.690 --> 00:13:47.700 align:start position:0% being added then it removes any 00:13:47.700 --> 00:13:50.170 align:start position:0% being added then it removes any legitimacy<00:13:48.300> that's<00:13:48.660> built<00:13:48.959> up<00:13:49.019> over<00:13:49.200> time<00:13:49.500> and 00:13:50.170 --> 00:13:50.180 align:start position:0% legitimacy that's built up over time and 00:13:50.180 --> 00:13:53.290 align:start position:0% legitimacy that's built up over time and external<00:13:51.180> funders<00:13:51.600> won't<00:13:52.260> continue 00:13:53.290 --> 00:13:53.300 align:start position:0% external funders won't continue 00:13:53.300 --> 00:13:55.850 align:start position:0% external funders won't continue funding<00:13:54.300> this<00:13:54.540> mechanism<00:13:54.899> so<00:13:55.380> we<00:13:55.620> hope<00:13:55.740> that 00:13:55.850 --> 00:13:55.860 align:start position:0% funding this mechanism so we hope that 00:13:55.860 --> 00:13:58.250 align:start position:0% funding this mechanism so we hope that these<00:13:56.100> are<00:13:56.660> sufficiently<00:13:57.660> balanced<00:13:58.079> against 00:13:58.250 --> 00:13:58.260 align:start position:0% these are sufficiently balanced against 00:13:58.260 --> 00:14:00.769 align:start position:0% these are sufficiently balanced against each<00:13:58.500> other<00:13:58.680> but<00:13:59.100> this<00:14:00.060> this<00:14:00.240> next<00:14:00.480> year<00:14:00.600> is 00:14:00.769 --> 00:14:00.779 align:start position:0% each other but this this next year is 00:14:00.779 --> 00:14:03.230 align:start position:0% each other but this this next year is sort<00:14:00.959> of<00:14:01.019> a<00:14:01.139> learning<00:14:01.380> period<00:14:01.680> uh<00:14:02.579> over<00:14:02.820> yeah 00:14:03.230 --> 00:14:03.240 align:start position:0% sort of a learning period uh over yeah 00:14:03.240 --> 00:14:05.090 align:start position:0% sort of a learning period uh over yeah it's<00:14:03.779> a<00:14:04.019> learning<00:14:04.260> period<00:14:04.500> so<00:14:04.620> we've<00:14:04.800> launched 00:14:05.090 --> 00:14:05.100 align:start position:0% it's a learning period so we've launched 00:14:05.100 --> 00:14:07.190 align:start position:0% it's a learning period so we've launched a<00:14:05.220> one-year<00:14:05.519> pilot<00:14:05.940> to<00:14:06.240> test<00:14:06.540> out<00:14:06.720> the 00:14:07.190 --> 00:14:07.200 align:start position:0% a one-year pilot to test out the 00:14:07.200 --> 00:14:08.810 align:start position:0% a one-year pilot to test out the assumptions<00:14:07.560> about<00:14:07.800> the<00:14:08.279> challenges<00:14:08.519> that<00:14:08.700> we 00:14:08.810 --> 00:14:08.820 align:start position:0% assumptions about the challenges that we 00:14:08.820 --> 00:14:11.750 align:start position:0% assumptions about the challenges that we wanted<00:14:09.300> to<00:14:09.480> address<00:14:09.660> as<00:14:10.440> well<00:14:10.620> as<00:14:10.860> the 00:14:11.750 --> 00:14:11.760 align:start position:0% wanted to address as well as the 00:14:11.760 --> 00:14:13.730 align:start position:0% wanted to address as well as the assumptions<00:14:12.120> about<00:14:12.360> what<00:14:13.019> the<00:14:13.139> best<00:14:13.320> ways<00:14:13.620> to 00:14:13.730 --> 00:14:13.740 align:start position:0% assumptions about what the best ways to 00:14:13.740 --> 00:14:16.009 align:start position:0% assumptions about what the best ways to approach<00:14:13.980> them<00:14:14.220> are<00:14:14.720> how<00:14:15.720> long<00:14:15.839> should 00:14:16.009 --> 00:14:16.019 align:start position:0% approach them are how long should 00:14:16.019 --> 00:14:18.170 align:start position:0% approach them are how long should vesting<00:14:16.380> be<00:14:16.560> things<00:14:16.800> like<00:14:17.040> this<00:14:17.279> so<00:14:18.060> we're 00:14:18.170 --> 00:14:18.180 align:start position:0% vesting be things like this so we're 00:14:18.180 --> 00:14:20.150 align:start position:0% vesting be things like this so we're working<00:14:18.360> on<00:14:18.600> that<00:14:18.779> we<00:14:19.079> we<00:14:19.260> launched<00:14:19.680> the<00:14:19.920> the 00:14:20.150 --> 00:14:20.160 align:start position:0% working on that we we launched the the 00:14:20.160 --> 00:14:23.150 align:start position:0% working on that we we launched the the protocol<00:14:20.519> itself<00:14:21.000> in<00:14:21.600> May<00:14:22.500> of<00:14:22.680> this<00:14:22.860> year<00:14:22.980> and 00:14:23.150 --> 00:14:23.160 align:start position:0% protocol itself in May of this year and 00:14:23.160 --> 00:14:25.370 align:start position:0% protocol itself in May of this year and it'll<00:14:23.399> run<00:14:23.519> until<00:14:23.760> May<00:14:24.120> of<00:14:24.360> next<00:14:24.600> year<00:14:24.779> and<00:14:25.260> so 00:14:25.370 --> 00:14:25.380 align:start position:0% it'll run until May of next year and so 00:14:25.380 --> 00:14:27.110 align:start position:0% it'll run until May of next year and so far<00:14:25.560> we've<00:14:25.800> raised<00:14:26.160> 11<00:14:26.339> million<00:14:26.820> in 00:14:27.110 --> 00:14:27.120 align:start position:0% far we've raised 11 million in 00:14:27.120 --> 00:14:28.970 align:start position:0% far we've raised 11 million in sponsoring<00:14:27.540> assets<00:14:27.899> and<00:14:28.320> like<00:14:28.440> I<00:14:28.560> said<00:14:28.680> these 00:14:28.970 --> 00:14:28.980 align:start position:0% sponsoring assets and like I said these 00:14:28.980 --> 00:14:31.250 align:start position:0% sponsoring assets and like I said these will<00:14:29.100> vest<00:14:29.399> for<00:14:29.760> one<00:14:30.120> year<00:14:30.240> overtime<00:14:30.660> again<00:14:30.959> to 00:14:31.250 --> 00:14:31.260 align:start position:0% will vest for one year overtime again to 00:14:31.260 --> 00:14:33.050 align:start position:0% will vest for one year overtime again to incentivize<00:14:31.740> long-term<00:14:32.399> contributions 00:14:33.050 --> 00:14:33.060 align:start position:0% incentivize long-term contributions 00:14:33.060 --> 00:14:35.690 align:start position:0% incentivize long-term contributions knowledge<00:14:33.959> transfer<00:14:34.500> between<00:14:35.399> different 00:14:35.690 --> 00:14:35.700 align:start position:0% knowledge transfer between different 00:14:35.700 --> 00:14:37.810 align:start position:0% knowledge transfer between different cohorts<00:14:36.240> of<00:14:36.300> core<00:14:36.480> contributors 00:14:37.810 --> 00:14:37.820 align:start position:0% cohorts of core contributors 00:14:37.820 --> 00:14:40.910 align:start position:0% cohorts of core contributors and<00:14:38.820> it's<00:14:39.180> it's<00:14:39.480> been<00:14:39.779> very<00:14:40.139> awesome<00:14:40.440> to<00:14:40.800> plug 00:14:40.910 --> 00:14:40.920 align:start position:0% and it's it's been very awesome to plug 00:14:40.920 --> 00:14:42.650 align:start position:0% and it's it's been very awesome to plug into<00:14:41.100> existing<00:14:41.579> funding<00:14:41.880> infrastructure<00:14:42.420> to 00:14:42.650 --> 00:14:42.660 align:start position:0% into existing funding infrastructure to 00:14:42.660 --> 00:14:44.810 align:start position:0% into existing funding infrastructure to touch<00:14:42.839> on<00:14:43.079> this<00:14:43.680> idea<00:14:43.920> of<00:14:44.040> pluralism<00:14:44.519> in 00:14:44.810 --> 00:14:44.820 align:start position:0% touch on this idea of pluralism in 00:14:44.820 --> 00:14:47.329 align:start position:0% touch on this idea of pluralism in funding<00:14:45.240> there's<00:14:45.720> a<00:14:45.839> git<00:14:46.019> coin<00:14:46.320> Grant<00:14:46.620> we've 00:14:47.329 --> 00:14:47.339 align:start position:0% funding there's a git coin Grant we've 00:14:47.339 --> 00:14:49.490 align:start position:0% funding there's a git coin Grant we've tapped<00:14:47.699> into<00:14:47.760> some<00:14:48.060> Dow<00:14:48.300> treasuries<00:14:48.839> who<00:14:49.139> fund 00:14:49.490 --> 00:14:49.500 align:start position:0% tapped into some Dow treasuries who fund 00:14:49.500 --> 00:14:51.949 align:start position:0% tapped into some Dow treasuries who fund back<00:14:50.040> in<00:14:50.339> their<00:14:50.459> native<00:14:50.699> token<00:14:51.120> so<00:14:51.300> shout<00:14:51.899> out 00:14:51.949 --> 00:14:51.959 align:start position:0% back in their native token so shout out 00:14:51.959 --> 00:14:53.949 align:start position:0% back in their native token so shout out to<00:14:52.199> the<00:14:52.440> people<00:14:52.560> that<00:14:52.800> have<00:14:52.920> funded<00:14:53.220> including 00:14:53.949 --> 00:14:53.959 align:start position:0% to the people that have funded including 00:14:53.959 --> 00:14:58.670 align:start position:0% to the people that have funded including uniswap<00:14:54.959> Lido<00:14:56.000> ens<00:14:57.000> noun<00:14:57.839> style<00:14:58.079> to<00:14:58.320> name<00:14:58.500> a 00:14:58.670 --> 00:14:58.680 align:start position:0% uniswap Lido ens noun style to name a 00:14:58.680 --> 00:15:01.790 align:start position:0% uniswap Lido ens noun style to name a few<00:14:58.800> as<00:14:59.760> well<00:14:59.880> as<00:15:00.060> this<00:15:00.720> Norm<00:15:01.139> that<00:15:01.380> we<00:15:01.560> want<00:15:01.680> to 00:15:01.790 --> 00:15:01.800 align:start position:0% few as well as this Norm that we want to 00:15:01.800 --> 00:15:04.910 align:start position:0% few as well as this Norm that we want to pursue<00:15:02.100> of<00:15:02.600> one<00:15:03.600> way<00:15:03.779> to<00:15:03.959> scale<00:15:04.139> the<00:15:04.560> incentive 00:15:04.910 --> 00:15:04.920 align:start position:0% pursue of one way to scale the incentive 00:15:04.920 --> 00:15:08.990 align:start position:0% pursue of one way to scale the incentive uh<00:15:05.399> the<00:15:05.579> treasury<00:15:05.959> sorry<00:15:06.959> uh<00:15:08.279> to<00:15:08.760> build<00:15:08.880> the 00:15:08.990 --> 00:15:09.000 align:start position:0% uh the treasury sorry uh to build the 00:15:09.000 --> 00:15:10.970 align:start position:0% uh the treasury sorry uh to build the norm<00:15:09.120> around<00:15:09.360> allocating<00:15:09.959> a<00:15:10.320> percent<00:15:10.560> of<00:15:10.860> the 00:15:10.970 --> 00:15:10.980 align:start position:0% norm around allocating a percent of the 00:15:10.980 --> 00:15:13.490 align:start position:0% norm around allocating a percent of the initial<00:15:11.220> Supply<00:15:11.519> or<00:15:12.480> annual<00:15:12.779> revenue<00:15:13.139> so 00:15:13.490 --> 00:15:13.500 align:start position:0% initial Supply or annual revenue so 00:15:13.500 --> 00:15:15.350 align:start position:0% initial Supply or annual revenue so again<00:15:13.740> another<00:15:13.980> shout<00:15:14.399> out<00:15:14.459> to<00:15:14.639> True<00:15:14.940> Freeze 00:15:15.350 --> 00:15:15.360 align:start position:0% again another shout out to True Freeze 00:15:15.360 --> 00:15:17.389 align:start position:0% again another shout out to True Freeze gnosis<00:15:15.720> safe<00:15:16.019> and<00:15:16.320> texture<00:15:16.680> punks<00:15:17.040> and<00:15:17.160> nft 00:15:17.389 --> 00:15:17.399 align:start position:0% gnosis safe and texture punks and nft 00:15:17.399 --> 00:15:19.670 align:start position:0% gnosis safe and texture punks and nft project<00:15:17.820> uh<00:15:18.779> they've<00:15:19.079> committed<00:15:19.440> to 00:15:19.670 --> 00:15:19.680 align:start position:0% project uh they've committed to 00:15:19.680 --> 00:15:21.350 align:start position:0% project uh they've committed to contributing<00:15:20.220> some<00:15:20.459> some<00:15:20.760> of<00:15:20.880> their<00:15:21.060> revenue 00:15:21.350 --> 00:15:21.360 align:start position:0% contributing some some of their revenue 00:15:21.360 --> 00:15:23.689 align:start position:0% contributing some some of their revenue and<00:15:22.079> over<00:15:22.260> time<00:15:22.440> we<00:15:22.680> we<00:15:22.860> want<00:15:23.040> to<00:15:23.160> build<00:15:23.339> this 00:15:23.689 --> 00:15:23.699 align:start position:0% and over time we we want to build this 00:15:23.699 --> 00:15:25.250 align:start position:0% and over time we we want to build this more<00:15:24.240> and<00:15:24.360> more 00:15:25.250 --> 00:15:25.260 align:start position:0% more and more 00:15:25.260 --> 00:15:26.930 align:start position:0% more and more um<00:15:25.320> we're<00:15:25.800> not<00:15:25.920> saying<00:15:26.160> that<00:15:26.339> this<00:15:26.459> is<00:15:26.639> the 00:15:26.930 --> 00:15:26.940 align:start position:0% um we're not saying that this is the 00:15:26.940 --> 00:15:30.050 align:start position:0% um we're not saying that this is the only<00:15:27.180> or<00:15:27.420> best<00:15:27.600> way<00:15:27.899> to<00:15:28.440> fund<00:15:29.220> uh<00:15:29.579> through<00:15:29.760> you 00:15:30.050 --> 00:15:30.060 align:start position:0% only or best way to fund uh through you 00:15:30.060 --> 00:15:31.730 align:start position:0% only or best way to fund uh through you know<00:15:30.120> initial<00:15:30.600> token<00:15:30.959> allocation<00:15:31.380> but<00:15:31.620> we're 00:15:31.730 --> 00:15:31.740 align:start position:0% know initial token allocation but we're 00:15:31.740 --> 00:15:33.230 align:start position:0% know initial token allocation but we're very<00:15:31.920> excited<00:15:32.220> to<00:15:32.339> explore<00:15:32.639> this<00:15:32.880> with<00:15:33.120> the 00:15:33.230 --> 00:15:33.240 align:start position:0% very excited to explore this with the 00:15:33.240 --> 00:15:35.210 align:start position:0% very excited to explore this with the broader<00:15:33.540> ecosystem<00:15:33.959> we're<00:15:34.860> already<00:15:34.980> starting 00:15:35.210 --> 00:15:35.220 align:start position:0% broader ecosystem we're already starting 00:15:35.220 --> 00:15:37.370 align:start position:0% broader ecosystem we're already starting some<00:15:35.519> discussions<00:15:35.880> with<00:15:36.240> l2s<00:15:36.779> about<00:15:36.959> how<00:15:37.199> they 00:15:37.370 --> 00:15:37.380 align:start position:0% some discussions with l2s about how they 00:15:37.380 --> 00:15:39.170 align:start position:0% some discussions with l2s about how they can<00:15:37.500> directly<00:15:37.860> fund 00:15:39.170 --> 00:15:39.180 align:start position:0% can directly fund 00:15:39.180 --> 00:15:41.689 align:start position:0% can directly fund um<00:15:39.240> this<00:15:39.600> this<00:15:39.779> incentive<00:15:40.260> mechanism<00:15:40.680> and<00:15:41.220> one 00:15:41.689 --> 00:15:41.699 align:start position:0% um this this incentive mechanism and one 00:15:41.699 --> 00:15:42.949 align:start position:0% um this this incentive mechanism and one thing<00:15:41.820> we<00:15:41.940> really<00:15:42.120> want<00:15:42.300> to<00:15:42.420> be<00:15:42.540> intentional 00:15:42.949 --> 00:15:42.959 align:start position:0% thing we really want to be intentional 00:15:42.959 --> 00:15:45.949 align:start position:0% thing we really want to be intentional about<00:15:43.139> is<00:15:43.760> documenting<00:15:44.760> the<00:15:45.060> outcomes<00:15:45.420> to<00:15:45.779> see 00:15:45.949 --> 00:15:45.959 align:start position:0% about is documenting the outcomes to see 00:15:45.959 --> 00:15:48.889 align:start position:0% about is documenting the outcomes to see you<00:15:46.320> know<00:15:46.380> does<00:15:46.740> this<00:15:46.980> really<00:15:47.279> work<00:15:47.579> does<00:15:48.540> this 00:15:48.889 --> 00:15:48.899 align:start position:0% you know does this really work does this 00:15:48.899 --> 00:15:50.569 align:start position:0% you know does this really work does this increase<00:15:49.500> the<00:15:49.740> incentive<00:15:50.100> to<00:15:50.220> contribute<00:15:50.519> to 00:15:50.569 --> 00:15:50.579 align:start position:0% increase the incentive to contribute to 00:15:50.579 --> 00:15:53.509 align:start position:0% increase the incentive to contribute to the<00:15:50.760> core<00:15:50.880> protocol<00:15:51.680> we<00:15:52.680> hope<00:15:52.800> it<00:15:52.920> will<00:15:53.100> but<00:15:53.279> we 00:15:53.509 --> 00:15:53.519 align:start position:0% the core protocol we hope it will but we 00:15:53.519 --> 00:15:55.490 align:start position:0% the core protocol we hope it will but we want<00:15:53.579> to<00:15:53.760> make<00:15:53.880> sure<00:15:54.060> that<00:15:54.420> the<00:15:55.260> community 00:15:55.490 --> 00:15:55.500 align:start position:0% want to make sure that the community 00:15:55.500 --> 00:15:57.650 align:start position:0% want to make sure that the community hold<00:15:55.800> us<00:15:56.040> accountable<00:15:56.399> and<00:15:57.060> we<00:15:57.480> really 00:15:57.650 --> 00:15:57.660 align:start position:0% hold us accountable and we really 00:15:57.660 --> 00:15:59.329 align:start position:0% hold us accountable and we really iterate<00:15:58.139> and<00:15:58.320> improve<00:15:58.620> the<00:15:58.740> mechanism<00:15:59.100> over 00:15:59.329 --> 00:15:59.339 align:start position:0% iterate and improve the mechanism over 00:15:59.339 --> 00:16:01.610 align:start position:0% iterate and improve the mechanism over time<00:15:59.579> uh<00:16:00.240> one<00:16:00.420> of<00:16:00.540> the<00:16:00.600> cool<00:16:00.720> things<00:16:00.959> is 00:16:01.610 --> 00:16:01.620 align:start position:0% time uh one of the cool things is 00:16:01.620 --> 00:16:03.410 align:start position:0% time uh one of the cool things is because<00:16:01.860> this<00:16:02.160> is<00:16:02.279> all<00:16:02.399> on<00:16:02.519> chain<00:16:02.760> anybody<00:16:03.240> can 00:16:03.410 --> 00:16:03.420 align:start position:0% because this is all on chain anybody can 00:16:03.420 --> 00:16:06.470 align:start position:0% because this is all on chain anybody can track<00:16:03.600> it<00:16:03.779> so<00:16:03.959> if<00:16:04.199> you<00:16:04.320> go<00:16:04.500> to<00:16:04.940> Dune<00:16:05.940> analytics 00:16:06.470 --> 00:16:06.480 align:start position:0% track it so if you go to Dune analytics 00:16:06.480 --> 00:16:09.970 align:start position:0% track it so if you go to Dune analytics and<00:16:07.440> search<00:16:07.860> protocol<00:16:08.220> all<00:16:08.639> Guild<00:16:08.940> or 00:16:09.970 --> 00:16:09.980 align:start position:0% and search protocol all Guild or 00:16:09.980 --> 00:16:12.110 align:start position:0% and search protocol all Guild or something<00:16:10.980> monkey<00:16:11.279> sorry<00:16:11.699> I<00:16:11.820> can't<00:16:12.000> remember 00:16:12.110 --> 00:16:12.120 align:start position:0% something monkey sorry I can't remember 00:16:12.120 --> 00:16:13.970 align:start position:0% something monkey sorry I can't remember the<00:16:12.360> name<00:16:12.540> of<00:16:12.720> the<00:16:12.839> contributor<00:16:13.320> but<00:16:13.560> we've 00:16:13.970 --> 00:16:13.980 align:start position:0% the name of the contributor but we've 00:16:13.980 --> 00:16:16.189 align:start position:0% the name of the contributor but we've been<00:16:14.100> working<00:16:14.279> with<00:16:14.639> someone<00:16:15.180> to<00:16:15.720> put 00:16:16.189 --> 00:16:16.199 align:start position:0% been working with someone to put 00:16:16.199 --> 00:16:17.810 align:start position:0% been working with someone to put together<00:16:16.320> this<00:16:16.680> dashboard<00:16:16.980> and<00:16:17.279> anybody<00:16:17.639> can 00:16:17.810 --> 00:16:17.820 align:start position:0% together this dashboard and anybody can 00:16:17.820 --> 00:16:20.050 align:start position:0% together this dashboard and anybody can track<00:16:18.000> the<00:16:18.300> finances<00:16:18.779> of<00:16:19.139> this<00:16:19.320> on-chain 00:16:20.050 --> 00:16:20.060 align:start position:0% track the finances of this on-chain 00:16:20.060 --> 00:16:22.970 align:start position:0% track the finances of this on-chain protocol<00:16:21.139> incentivization<00:16:22.139> mechanism<00:16:22.620> which 00:16:22.970 --> 00:16:22.980 align:start position:0% protocol incentivization mechanism which 00:16:22.980 --> 00:16:24.889 align:start position:0% protocol incentivization mechanism which is<00:16:23.040> pretty<00:16:23.279> amazing<00:16:23.639> you<00:16:24.240> can<00:16:24.360> see<00:16:24.540> the 00:16:24.889 --> 00:16:24.899 align:start position:0% is pretty amazing you can see the 00:16:24.899 --> 00:16:27.829 align:start position:0% is pretty amazing you can see the membership<00:16:25.260> uh<00:16:26.160> the<00:16:26.399> the<00:16:26.519> total<00:16:26.880> weighting<00:16:27.360> of 00:16:27.829 --> 00:16:27.839 align:start position:0% membership uh the the total weighting of 00:16:27.839 --> 00:16:30.710 align:start position:0% membership uh the the total weighting of their<00:16:28.380> share<00:16:28.740> of<00:16:28.920> the<00:16:29.399> the<00:16:29.519> proceeds<00:16:30.240> who<00:16:30.540> has 00:16:30.710 --> 00:16:30.720 align:start position:0% their share of the the proceeds who has 00:16:30.720 --> 00:16:33.290 align:start position:0% their share of the the proceeds who has contributed<00:16:31.260> uh<00:16:32.220> really<00:16:32.399> great<00:16:32.579> data<00:16:33.000> source 00:16:33.290 --> 00:16:33.300 align:start position:0% contributed uh really great data source 00:16:33.300 --> 00:16:36.829 align:start position:0% contributed uh really great data source and<00:16:34.440> um<00:16:34.760> awesome<00:16:35.760> for<00:16:36.060> transparency<00:16:36.540> if 00:16:36.829 --> 00:16:36.839 align:start position:0% and um awesome for transparency if 00:16:36.839 --> 00:16:38.870 align:start position:0% and um awesome for transparency if anybody's<00:16:37.139> interested<00:16:37.500> in<00:16:37.620> tracking<00:16:38.040> that<00:16:38.220> so 00:16:38.870 --> 00:16:38.880 align:start position:0% anybody's interested in tracking that so 00:16:38.880 --> 00:16:40.310 align:start position:0% anybody's interested in tracking that so I'm<00:16:39.120> ending<00:16:39.360> a<00:16:39.480> little<00:16:39.540> early<00:16:39.720> if<00:16:40.019> there<00:16:40.199> are 00:16:40.310 --> 00:16:40.320 align:start position:0% I'm ending a little early if there are 00:16:40.320 --> 00:16:43.249 align:start position:0% I'm ending a little early if there are any<00:16:40.380> questions<00:16:41.060> I'd<00:16:42.060> love<00:16:42.300> to<00:16:42.540> talk<00:16:43.079> with 00:16:43.249 --> 00:16:43.259 align:start position:0% any questions I'd love to talk with 00:16:43.259 --> 00:16:44.569 align:start position:0% any questions I'd love to talk with anybody<00:16:43.560> who<00:16:43.860> wants<00:16:44.160> to<00:16:44.160> learn<00:16:44.279> more<00:16:44.459> about 00:16:44.569 --> 00:16:44.579 align:start position:0% anybody who wants to learn more about 00:16:44.579 --> 00:16:46.490 align:start position:0% anybody who wants to learn more about the<00:16:44.759> mechanism<00:16:45.180> if<00:16:45.779> you're<00:16:45.899> part<00:16:46.079> of<00:16:46.199> a<00:16:46.259> D5 00:16:46.490 --> 00:16:46.500 align:start position:0% the mechanism if you're part of a D5 00:16:46.500 --> 00:16:48.530 align:start position:0% the mechanism if you're part of a D5 project<00:16:46.800> or<00:16:47.220> something<00:16:47.399> that's<00:16:48.000> planning<00:16:48.480> to 00:16:48.530 --> 00:16:48.540 align:start position:0% project or something that's planning to 00:16:48.540 --> 00:16:51.410 align:start position:0% project or something that's planning to launch<00:16:48.779> a<00:16:48.899> token<00:16:49.579> please<00:16:50.579> do<00:16:50.759> come<00:16:50.940> talk<00:16:51.180> to<00:16:51.360> me 00:16:51.410 --> 00:16:51.420 align:start position:0% launch a token please do come talk to me 00:16:51.420 --> 00:16:52.910 align:start position:0% launch a token please do come talk to me or<00:16:51.600> any<00:16:51.779> of<00:16:51.899> the<00:16:52.019> members<00:16:52.320> there's<00:16:52.560> a<00:16:52.740> ton<00:16:52.860> of 00:16:52.910 --> 00:16:52.920 align:start position:0% or any of the members there's a ton of 00:16:52.920 --> 00:16:54.889 align:start position:0% or any of the members there's a ton of core<00:16:53.100> developers<00:16:53.519> here<00:16:53.759> who<00:16:54.000> are<00:16:54.120> part<00:16:54.720> of 00:16:54.889 --> 00:16:54.899 align:start position:0% core developers here who are part of 00:16:54.899 --> 00:16:57.170 align:start position:0% core developers here who are part of this<00:16:55.079> project<00:16:55.259> that<00:16:55.920> QR<00:16:56.220> code<00:16:56.399> I<00:16:56.699> think<00:16:56.820> takes 00:16:57.170 --> 00:16:57.180 align:start position:0% this project that QR code I think takes 00:16:57.180 --> 00:16:59.449 align:start position:0% this project that QR code I think takes you<00:16:57.300> to<00:16:57.600> the<00:16:57.899> docs<00:16:58.320> or<00:16:58.980> somewhere<00:16:59.339> else 00:16:59.449 --> 00:16:59.459 align:start position:0% you to the docs or somewhere else 00:16:59.459 --> 00:17:01.490 align:start position:0% you to the docs or somewhere else relevant<00:16:59.899> so<00:17:00.899> yeah<00:17:01.019> and<00:17:01.139> then<00:17:01.259> there's<00:17:01.380> some 00:17:01.490 --> 00:17:01.500 align:start position:0% relevant so yeah and then there's some 00:17:01.500 --> 00:17:03.410 align:start position:0% relevant so yeah and then there's some bitly<00:17:01.800> links<00:17:02.160> if<00:17:02.459> anybody's<00:17:02.880> curious<00:17:03.240> to 00:17:03.410 --> 00:17:03.420 align:start position:0% bitly links if anybody's curious to 00:17:03.420 --> 00:17:05.630 align:start position:0% bitly links if anybody's curious to explore<00:17:03.779> more<00:17:04.079> that's<00:17:04.740> my<00:17:04.919> handle<00:17:05.280> and<00:17:05.579> then 00:17:05.630 --> 00:17:05.640 align:start position:0% explore more that's my handle and then 00:17:05.640 --> 00:17:07.130 align:start position:0% explore more that's my handle and then you<00:17:05.819> can<00:17:05.939> follow<00:17:06.179> the<00:17:06.480> the<00:17:06.660> organization 00:17:07.130 --> 00:17:07.140 align:start position:0% you can follow the the organization 00:17:07.140 --> 00:17:10.610 align:start position:0% you can follow the the organization itself<00:17:07.559> at<00:17:08.160> protocol<00:17:08.579> Guild<00:17:08.939> on<00:17:09.240> Twitter<00:17:09.620> yeah 00:17:10.610 --> 00:17:10.620 align:start position:0% itself at protocol Guild on Twitter yeah 00:17:10.620 --> 00:17:12.710 align:start position:0% itself at protocol Guild on Twitter yeah so<00:17:10.799> thank<00:17:10.980> you<00:17:11.100> for<00:17:11.220> the<00:17:11.400> time<00:17:11.520> again<00:17:11.819> to<00:17:12.299> the 00:17:12.710 --> 00:17:12.720 align:start position:0% so thank you for the time again to the 00:17:12.720 --> 00:17:14.569 align:start position:0% so thank you for the time again to the Defcon<00:17:13.079> organizers<00:17:13.500> for<00:17:13.679> giving<00:17:13.919> me<00:17:14.100> space<00:17:14.280> to 00:17:14.569 --> 00:17:14.579 align:start position:0% Defcon organizers for giving me space to 00:17:14.579 --> 00:17:16.130 align:start position:0% Defcon organizers for giving me space to talk<00:17:14.699> about<00:17:14.819> this<00:17:15.059> public<00:17:15.299> goods<00:17:15.660> funding<00:17:15.959> is 00:17:16.130 --> 00:17:16.140 align:start position:0% talk about this public goods funding is 00:17:16.140 --> 00:17:19.789 align:start position:0% talk about this public goods funding is incredibly<00:17:16.500> important<00:17:16.939> and<00:17:17.939> uh<00:17:18.839> it's<00:17:19.559> it's 00:17:19.789 --> 00:17:19.799 align:start position:0% incredibly important and uh it's it's 00:17:19.799 --> 00:17:21.650 align:start position:0% incredibly important and uh it's it's important<00:17:20.459> to<00:17:20.640> have<00:17:20.760> also<00:17:21.059> a<00:17:21.299> variety<00:17:21.540> of 00:17:21.650 --> 00:17:21.660 align:start position:0% important to have also a variety of 00:17:21.660 --> 00:17:24.890 align:start position:0% important to have also a variety of approaches<00:17:22.459> different<00:17:23.459> curators<00:17:24.120> different 00:17:24.890 --> 00:17:24.900 align:start position:0% approaches different curators different 00:17:24.900 --> 00:17:27.530 align:start position:0% approaches different curators different uh<00:17:25.740> mechanisms<00:17:26.400> so<00:17:26.760> that<00:17:26.880> we<00:17:27.059> can<00:17:27.179> make<00:17:27.360> sure 00:17:27.530 --> 00:17:27.540 align:start position:0% uh mechanisms so that we can make sure 00:17:27.540 --> 00:17:30.710 align:start position:0% uh mechanisms so that we can make sure that<00:17:27.900> the<00:17:28.500> incentives<00:17:28.980> to<00:17:29.480> contributing<00:17:30.480> back 00:17:30.710 --> 00:17:30.720 align:start position:0% that the incentives to contributing back 00:17:30.720 --> 00:17:33.590 align:start position:0% that the incentives to contributing back to<00:17:30.960> the<00:17:31.140> ethereum<00:17:31.559> protocol<00:17:32.179> in<00:17:33.179> the<00:17:33.299> context 00:17:33.590 --> 00:17:33.600 align:start position:0% to the ethereum protocol in the context 00:17:33.600 --> 00:17:35.990 align:start position:0% to the ethereum protocol in the context of<00:17:34.080> amazing<00:17:34.559> application<00:17:35.039> layer<00:17:35.400> projects<00:17:35.760> is 00:17:35.990 --> 00:17:36.000 align:start position:0% of amazing application layer projects is 00:17:36.000 --> 00:17:38.390 align:start position:0% of amazing application layer projects is maintained<00:17:36.419> over<00:17:36.600> time<00:17:36.900> so<00:17:37.260> thank<00:17:37.919> you<00:17:38.100> and 00:17:38.390 --> 00:17:38.400 align:start position:0% maintained over time so thank you and 00:17:38.400 --> 00:17:39.770 align:start position:0% maintained over time so thank you and I'm<00:17:38.520> happy<00:17:38.700> to<00:17:38.880> take<00:17:39.000> questions<00:17:39.240> if<00:17:39.480> there<00:17:39.660> are 00:17:39.770 --> 00:17:39.780 align:start position:0% I'm happy to take questions if there are 00:17:39.780 --> 00:17:43.130 align:start position:0% I'm happy to take questions if there are any<00:17:39.900> we<00:17:40.740> have<00:17:41.039> a<00:17:41.460> question<00:17:41.700> here<00:17:41.940> we'll<00:17:42.419> give 00:17:43.130 --> 00:17:43.140 align:start position:0% any we have a question here we'll give 00:17:43.140 --> 00:17:44.570 align:start position:0% any we have a question here we'll give the<00:17:43.320> mic<00:17:43.500> to<00:17:43.620> the<00:17:43.799> gentleman<00:17:44.100> over<00:17:44.220> there<00:17:44.400> if 00:17:44.570 --> 00:17:44.580 align:start position:0% the mic to the gentleman over there if 00:17:44.580 --> 00:17:45.590 align:start position:0% the mic to the gentleman over there if you<00:17:44.760> have<00:17:44.820> more<00:17:45.000> questions<00:17:45.120> please<00:17:45.419> just 00:17:45.590 --> 00:17:45.600 align:start position:0% you have more questions please just 00:17:45.600 --> 00:17:46.970 align:start position:0% you have more questions please just raise<00:17:45.720> your<00:17:45.960> hand<00:17:46.080> or<00:17:46.260> get<00:17:46.440> to<00:17:46.559> the<00:17:46.620> end<00:17:46.740> of<00:17:46.860> the 00:17:46.970 --> 00:17:46.980 align:start position:0% raise your hand or get to the end of the 00:17:46.980 --> 00:17:48.470 align:start position:0% raise your hand or get to the end of the line<00:17:47.039> so<00:17:47.220> we<00:17:47.400> can<00:17:47.520> quickly<00:17:47.820> give<00:17:48.000> you<00:17:48.059> the<00:17:48.299> mic 00:17:48.470 --> 00:17:48.480 align:start position:0% line so we can quickly give you the mic 00:17:48.480 --> 00:17:51.350 align:start position:0% line so we can quickly give you the mic and<00:17:49.380> I'll<00:17:49.559> let's<00:17:50.039> begin<00:17:50.280> with<00:17:50.520> the<00:17:50.580> question 00:17:51.350 --> 00:17:51.360 align:start position:0% and I'll let's begin with the question 00:17:51.360 --> 00:17:53.990 align:start position:0% and I'll let's begin with the question Adrian<00:17:52.140> thanks<00:17:53.160> um<00:17:53.220> amazing<00:17:53.640> initiative 00:17:53.990 --> 00:17:54.000 align:start position:0% Adrian thanks um amazing initiative 00:17:54.000 --> 00:17:56.330 align:start position:0% Adrian thanks um amazing initiative thank<00:17:54.419> you<00:17:54.539> for<00:17:54.600> giving<00:17:54.780> the<00:17:54.960> speech<00:17:55.320> I<00:17:56.039> had<00:17:56.220> a 00:17:56.330 --> 00:17:56.340 align:start position:0% thank you for giving the speech I had a 00:17:56.340 --> 00:17:58.669 align:start position:0% thank you for giving the speech I had a question<00:17:56.460> about<00:17:56.700> the<00:17:57.299> recent<00:17:57.720> acquisition<00:17:58.200> of 00:17:58.669 --> 00:17:58.679 align:start position:0% question about the recent acquisition of 00:17:58.679 --> 00:18:00.770 align:start position:0% question about the recent acquisition of uh<00:17:59.160> prison 00:18:00.770 --> 00:18:00.780 align:start position:0% uh prison 00:18:00.780 --> 00:18:03.049 align:start position:0% uh prison um<00:18:00.900> I'm<00:18:01.860> curious<00:18:02.220> if<00:18:02.340> you<00:18:02.460> could<00:18:02.640> comment<00:18:02.880> on 00:18:03.049 --> 00:18:03.059 align:start position:0% um I'm curious if you could comment on 00:18:03.059 --> 00:18:04.730 align:start position:0% um I'm curious if you could comment on that<00:18:03.240> like<00:18:03.480> obviously<00:18:03.960> on<00:18:04.140> one<00:18:04.260> hand<00:18:04.440> that 00:18:04.730 --> 00:18:04.740 align:start position:0% that like obviously on one hand that 00:18:04.740 --> 00:18:06.950 align:start position:0% that like obviously on one hand that means<00:18:04.980> that<00:18:05.160> there's<00:18:05.400> I<00:18:05.940> guess<00:18:06.059> less<00:18:06.600> pressure 00:18:06.950 --> 00:18:06.960 align:start position:0% means that there's I guess less pressure 00:18:06.960 --> 00:18:08.750 align:start position:0% means that there's I guess less pressure on<00:18:07.260> the<00:18:07.440> protocol<00:18:07.679> Guild<00:18:08.039> to<00:18:08.220> fund<00:18:08.520> those 00:18:08.750 --> 00:18:08.760 align:start position:0% on the protocol Guild to fund those 00:18:08.760 --> 00:18:11.390 align:start position:0% on the protocol Guild to fund those developers<00:18:09.299> on<00:18:10.080> the<00:18:10.200> other<00:18:10.260> hand<00:18:10.500> is<00:18:11.039> that<00:18:11.160> the 00:18:11.390 --> 00:18:11.400 align:start position:0% developers on the other hand is that the 00:18:11.400 --> 00:18:13.370 align:start position:0% developers on the other hand is that the kind<00:18:11.520> of<00:18:11.700> outcome<00:18:12.000> that<00:18:12.240> we<00:18:12.419> strive<00:18:12.720> for<00:18:13.020> now 00:18:13.370 --> 00:18:13.380 align:start position:0% kind of outcome that we strive for now 00:18:13.380 --> 00:18:15.110 align:start position:0% kind of outcome that we strive for now obviously<00:18:13.799> arbitrum<00:18:14.400> they're<00:18:14.640> a<00:18:14.820> they're<00:18:15.000> a 00:18:15.110 --> 00:18:15.120 align:start position:0% obviously arbitrum they're a they're a 00:18:15.120 --> 00:18:16.190 align:start position:0% obviously arbitrum they're a they're a good<00:18:15.240> actor<00:18:15.480> I<00:18:15.600> think<00:18:15.720> they<00:18:15.840> have<00:18:15.960> a<00:18:16.080> great 00:18:16.190 --> 00:18:16.200 align:start position:0% good actor I think they have a great 00:18:16.200 --> 00:18:17.810 align:start position:0% good actor I think they have a great reputation 00:18:17.810 --> 00:18:17.820 align:start position:0% reputation 00:18:17.820 --> 00:18:20.570 align:start position:0% reputation um but<00:18:18.600> one<00:18:18.900> could<00:18:19.200> think<00:18:19.919> of<00:18:20.039> some<00:18:20.220> potential 00:18:20.570 --> 00:18:20.580 align:start position:0% um but one could think of some potential 00:18:20.580 --> 00:18:23.090 align:start position:0% um but one could think of some potential downsides<00:18:21.299> so<00:18:21.539> I'm<00:18:21.900> just<00:18:22.020> wondering<00:18:22.380> how<00:18:22.980> does 00:18:23.090 --> 00:18:23.100 align:start position:0% downsides so I'm just wondering how does 00:18:23.100 --> 00:18:25.070 align:start position:0% downsides so I'm just wondering how does a<00:18:23.220> protocol<00:18:23.460> Guild<00:18:24.000> feel<00:18:24.240> about<00:18:24.480> those<00:18:24.840> kind 00:18:25.070 --> 00:18:25.080 align:start position:0% a protocol Guild feel about those kind 00:18:25.080 --> 00:18:26.210 align:start position:0% a protocol Guild feel about those kind of<00:18:25.200> outcomes 00:18:26.210 --> 00:18:26.220 align:start position:0% of outcomes 00:18:26.220 --> 00:18:28.850 align:start position:0% of outcomes what<00:18:26.700> sort<00:18:26.940> of<00:18:27.059> downsides<00:18:27.600> do<00:18:27.780> you<00:18:27.900> see<00:18:28.080> undue 00:18:28.850 --> 00:18:28.860 align:start position:0% what sort of downsides do you see undue 00:18:28.860 --> 00:18:30.710 align:start position:0% what sort of downsides do you see undue influence<00:18:29.400> I<00:18:29.700> mean<00:18:29.820> obviously<00:18:30.120> we<00:18:30.299> have<00:18:30.480> like 00:18:30.710 --> 00:18:30.720 align:start position:0% influence I mean obviously we have like 00:18:30.720 --> 00:18:32.390 align:start position:0% influence I mean obviously we have like nine<00:18:31.020> teams<00:18:31.380> in<00:18:31.559> total<00:18:31.740> who<00:18:31.919> are<00:18:32.100> contributing 00:18:32.390 --> 00:18:32.400 align:start position:0% nine teams in total who are contributing 00:18:32.400 --> 00:18:34.370 align:start position:0% nine teams in total who are contributing to<00:18:32.520> this<00:18:32.640> if<00:18:32.760> I'm<00:18:32.880> not<00:18:33.000> mistaken 00:18:34.370 --> 00:18:34.380 align:start position:0% to this if I'm not mistaken 00:18:34.380 --> 00:18:36.350 align:start position:0% to this if I'm not mistaken um<00:18:34.440> and<00:18:34.919> so<00:18:35.220> you<00:18:35.520> know 00:18:36.350 --> 00:18:36.360 align:start position:0% um and so you know 00:18:36.360 --> 00:18:40.070 align:start position:0% um and so you know We<00:18:36.720> Trust<00:18:37.140> arbitrum<00:18:37.860> if<00:18:39.299> um<00:18:39.419> if<00:18:39.720> they<00:18:39.840> start 00:18:40.070 --> 00:18:40.080 align:start position:0% We Trust arbitrum if um if they start 00:18:40.080 --> 00:18:41.450 align:start position:0% We Trust arbitrum if um if they start doing<00:18:40.320> some<00:18:40.559> weird<00:18:40.740> stuff<00:18:40.980> you<00:18:41.220> know<00:18:41.340> there's 00:18:41.450 --> 00:18:41.460 align:start position:0% doing some weird stuff you know there's 00:18:41.460 --> 00:18:42.710 align:start position:0% doing some weird stuff you know there's other<00:18:41.640> options<00:18:42.000> for<00:18:42.179> people<00:18:42.299> to<00:18:42.480> choose 00:18:42.710 --> 00:18:42.720 align:start position:0% other options for people to choose 00:18:42.720 --> 00:18:44.270 align:start position:0% other options for people to choose different<00:18:42.900> clients 00:18:44.270 --> 00:18:44.280 align:start position:0% different clients 00:18:44.280 --> 00:18:45.770 align:start position:0% different clients um<00:18:44.340> and<00:18:44.520> obviously<00:18:44.820> if<00:18:44.940> we<00:18:45.059> have<00:18:45.240> many<00:18:45.419> more 00:18:45.770 --> 00:18:45.780 align:start position:0% um and obviously if we have many more 00:18:45.780 --> 00:18:49.190 align:start position:0% um and obviously if we have many more clients<00:18:46.320> their<00:18:46.919> influence<00:18:47.640> uh<00:18:48.179> you<00:18:48.780> know<00:18:48.840> they 00:18:49.190 --> 00:18:49.200 align:start position:0% clients their influence uh you know they 00:18:49.200 --> 00:18:51.409 align:start position:0% clients their influence uh you know they won't<00:18:49.320> really<00:18:49.500> have<00:18:49.799> an<00:18:49.980> influence 00:18:51.409 --> 00:18:51.419 align:start position:0% won't really have an influence 00:18:51.419 --> 00:18:53.450 align:start position:0% won't really have an influence um<00:18:51.539> but<00:18:51.900> nevertheless<00:18:52.500> you<00:18:52.860> know<00:18:52.919> they<00:18:53.220> have 00:18:53.450 --> 00:18:53.460 align:start position:0% um but nevertheless you know they have 00:18:53.460 --> 00:18:55.070 align:start position:0% um but nevertheless you know they have certain<00:18:53.820> interests 00:18:55.070 --> 00:18:55.080 align:start position:0% certain interests 00:18:55.080 --> 00:18:56.270 align:start position:0% certain interests um<00:18:55.200> they<00:18:55.440> might<00:18:55.620> like<00:18:55.919> they're<00:18:56.160> probably 00:18:56.270 --> 00:18:56.280 align:start position:0% um they might like they're probably 00:18:56.280 --> 00:18:58.130 align:start position:0% um they might like they're probably going<00:18:56.460> to<00:18:56.520> launch<00:18:56.700> a<00:18:56.880> token<00:18:57.240> tokenomics<00:18:57.960> how 00:18:58.130 --> 00:18:58.140 align:start position:0% going to launch a token tokenomics how 00:18:58.140 --> 00:18:59.870 align:start position:0% going to launch a token tokenomics how do<00:18:58.260> they<00:18:58.380> pump<00:18:58.559> their<00:18:58.799> token<00:18:59.220> you<00:18:59.520> know<00:18:59.640> these 00:18:59.870 --> 00:18:59.880 align:start position:0% do they pump their token you know these 00:18:59.880 --> 00:19:02.210 align:start position:0% do they pump their token you know these kind<00:19:00.000> of<00:19:00.120> questions<00:19:00.360> yeah<00:19:01.080> you<00:19:01.380> definitely<00:19:01.740> uh 00:19:02.210 --> 00:19:02.220 align:start position:0% kind of questions yeah you definitely uh 00:19:02.220 --> 00:19:03.950 align:start position:0% kind of questions yeah you definitely uh pick<00:19:02.460> the<00:19:02.700> hardest<00:19:03.000> question 00:19:03.950 --> 00:19:03.960 align:start position:0% pick the hardest question 00:19:03.960 --> 00:19:05.270 align:start position:0% pick the hardest question um<00:19:04.020> it's<00:19:04.200> given<00:19:04.559> they<00:19:04.740> announced<00:19:05.100> yesterday 00:19:05.270 --> 00:19:05.280 align:start position:0% um it's given they announced yesterday 00:19:05.280 --> 00:19:07.310 align:start position:0% um it's given they announced yesterday so<00:19:06.000> yeah<00:19:06.179> this<00:19:06.480> is<00:19:06.600> this<00:19:06.960> is<00:19:07.140> really 00:19:07.310 --> 00:19:07.320 align:start position:0% so yeah this is this is really 00:19:07.320 --> 00:19:09.289 align:start position:0% so yeah this is this is really interesting<00:19:07.740> and<00:19:08.100> digs<00:19:08.520> into<00:19:08.580> it<00:19:08.880> touches<00:19:09.179> a 00:19:09.289 --> 00:19:09.299 align:start position:0% interesting and digs into it touches a 00:19:09.299 --> 00:19:11.270 align:start position:0% interesting and digs into it touches a lot<00:19:09.419> of<00:19:09.539> different<00:19:09.600> areas<00:19:10.020> about<00:19:10.320> protocol 00:19:11.270 --> 00:19:11.280 align:start position:0% lot of different areas about protocol 00:19:11.280 --> 00:19:13.970 align:start position:0% lot of different areas about protocol governance<00:19:11.880> incentivization 00:19:13.970 --> 00:19:13.980 align:start position:0% governance incentivization 00:19:13.980 --> 00:19:16.370 align:start position:0% governance incentivization um<00:19:14.100> funding<00:19:14.700> the<00:19:14.880> core<00:19:15.000> protocol<00:19:15.419> work<00:19:15.780> and 00:19:16.370 --> 00:19:16.380 align:start position:0% um funding the core protocol work and 00:19:16.380 --> 00:19:18.049 align:start position:0% um funding the core protocol work and like<00:19:16.620> you<00:19:16.740> said<00:19:16.860> I<00:19:17.220> don't<00:19:17.340> I<00:19:17.640> know<00:19:17.760> them<00:19:17.940> all 00:19:18.049 --> 00:19:18.059 align:start position:0% like you said I don't I know them all 00:19:18.059 --> 00:19:19.070 align:start position:0% like you said I don't I know them all personally 00:19:19.070 --> 00:19:19.080 align:start position:0% personally 00:19:19.080 --> 00:19:21.230 align:start position:0% personally um<00:19:19.140> so<00:19:19.380> I<00:19:19.500> do<00:19:19.679> have<00:19:19.799> a<00:19:19.919> bias<00:19:20.220> here<00:19:20.340> but<00:19:20.580> I<00:19:21.059> do 00:19:21.230 --> 00:19:21.240 align:start position:0% um so I do have a bias here but I do 00:19:21.240 --> 00:19:23.090 align:start position:0% um so I do have a bias here but I do expect<00:19:21.780> that<00:19:22.260> they<00:19:22.440> will<00:19:22.559> maintain<00:19:22.860> their 00:19:23.090 --> 00:19:23.100 align:start position:0% expect that they will maintain their 00:19:23.100 --> 00:19:24.529 align:start position:0% expect that they will maintain their neutrality 00:19:24.529 --> 00:19:24.539 align:start position:0% neutrality 00:19:24.539 --> 00:19:26.390 align:start position:0% neutrality um<00:19:24.600> I<00:19:25.080> can't<00:19:25.200> comment<00:19:25.559> super<00:19:25.799> deeply<00:19:26.160> on<00:19:26.280> it 00:19:26.390 --> 00:19:26.400 align:start position:0% um I can't comment super deeply on it 00:19:26.400 --> 00:19:27.710 align:start position:0% um I can't comment super deeply on it again<00:19:26.520> because<00:19:26.760> it<00:19:26.940> just<00:19:27.120> happened<00:19:27.299> and<00:19:27.539> I'm 00:19:27.710 --> 00:19:27.720 align:start position:0% again because it just happened and I'm 00:19:27.720 --> 00:19:29.390 align:start position:0% again because it just happened and I'm still<00:19:27.900> digesting<00:19:28.380> still<00:19:28.679> understanding<00:19:29.220> the 00:19:29.390 --> 00:19:29.400 align:start position:0% still digesting still understanding the 00:19:29.400 --> 00:19:30.890 align:start position:0% still digesting still understanding the the<00:19:29.640> mechanics<00:19:30.059> of<00:19:30.179> it<00:19:30.299> but<00:19:30.419> I<00:19:30.600> don't<00:19:30.720> expect 00:19:30.890 --> 00:19:30.900 align:start position:0% the mechanics of it but I don't expect 00:19:30.900 --> 00:19:33.230 align:start position:0% the mechanics of it but I don't expect that<00:19:31.200> there<00:19:31.380> would<00:19:31.559> be<00:19:31.679> any<00:19:31.980> uh<00:19:32.820> undue 00:19:33.230 --> 00:19:33.240 align:start position:0% that there would be any uh undue 00:19:33.240 --> 00:19:35.630 align:start position:0% that there would be any uh undue influence<00:19:33.660> exerted<00:19:34.260> by<00:19:34.440> the<00:19:34.559> L2<00:19:34.919> and<00:19:35.400> like<00:19:35.520> you 00:19:35.630 --> 00:19:35.640 align:start position:0% influence exerted by the L2 and like you 00:19:35.640 --> 00:19:38.870 align:start position:0% influence exerted by the L2 and like you said<00:19:35.820> if<00:19:36.240> there<00:19:36.960> were<00:19:37.260> red<00:19:38.100> flags<00:19:38.520> starting<00:19:38.700> to 00:19:38.870 --> 00:19:38.880 align:start position:0% said if there were red flags starting to 00:19:38.880 --> 00:19:40.549 align:start position:0% said if there were red flags starting to appear<00:19:39.179> I'm<00:19:39.840> pretty<00:19:40.020> sure<00:19:40.140> the<00:19:40.380> community 00:19:40.549 --> 00:19:40.559 align:start position:0% appear I'm pretty sure the community 00:19:40.559 --> 00:19:43.450 align:start position:0% appear I'm pretty sure the community would<00:19:40.860> call<00:19:40.980> it<00:19:41.160> out<00:19:41.340> pretty<00:19:42.120> fast 00:19:43.450 --> 00:19:43.460 align:start position:0% would call it out pretty fast 00:19:43.460 --> 00:19:47.630 align:start position:0% would call it out pretty fast and<00:19:44.600> either<00:19:45.600> arbitrim<00:19:46.200> or<00:19:46.620> the<00:19:47.100> Prismatic 00:19:47.630 --> 00:19:47.640 align:start position:0% and either arbitrim or the Prismatic 00:19:47.640 --> 00:19:49.190 align:start position:0% and either arbitrim or the Prismatic team<00:19:47.760> would<00:19:48.000> adjust<00:19:48.179> course<00:19:48.480> pretty<00:19:48.840> quickly 00:19:49.190 --> 00:19:49.200 align:start position:0% team would adjust course pretty quickly 00:19:49.200 --> 00:19:51.470 align:start position:0% team would adjust course pretty quickly but<00:19:49.620> yeah<00:19:49.799> that's<00:19:50.100> the<00:19:50.280> short<00:19:50.400> answer 00:19:51.470 --> 00:19:51.480 align:start position:0% but yeah that's the short answer 00:19:51.480 --> 00:19:52.970 align:start position:0% but yeah that's the short answer I<00:19:51.780> saw<00:19:51.900> on<00:19:52.080> the<00:19:52.140> other<00:19:52.200> hand<00:19:52.320> do<00:19:52.620> we<00:19:52.740> have<00:19:52.860> more 00:19:52.970 --> 00:19:52.980 align:start position:0% I saw on the other hand do we have more 00:19:52.980 --> 00:19:54.230 align:start position:0% I saw on the other hand do we have more questions 00:19:54.230 --> 00:19:54.240 align:start position:0% questions 00:19:54.240 --> 00:19:56.690 align:start position:0% questions um<00:19:54.299> what's<00:19:54.600> the<00:19:54.900> like<00:19:55.500> let's<00:19:56.100> let's<00:19:56.100> say 00:19:56.690 --> 00:19:56.700 align:start position:0% um what's the like let's let's say 00:19:56.700 --> 00:19:58.070 align:start position:0% um what's the like let's let's say someone's<00:19:57.120> leaving<00:19:57.240> the<00:19:57.539> protocol<00:19:57.780> Guild 00:19:58.070 --> 00:19:58.080 align:start position:0% someone's leaving the protocol Guild 00:19:58.080 --> 00:19:59.630 align:start position:0% someone's leaving the protocol Guild what's<00:19:58.380> like<00:19:58.559> the<00:19:58.740> process<00:19:59.039> for<00:19:59.400> the 00:19:59.630 --> 00:19:59.640 align:start position:0% what's like the process for the 00:19:59.640 --> 00:20:01.250 align:start position:0% what's like the process for the off-boarding<00:20:00.240> like<00:20:00.360> do<00:20:00.539> they<00:20:00.660> have<00:20:00.780> an<00:20:00.960> amount 00:20:01.250 --> 00:20:01.260 align:start position:0% off-boarding like do they have an amount 00:20:01.260 --> 00:20:03.169 align:start position:0% off-boarding like do they have an amount of<00:20:01.380> time<00:20:01.620> or<00:20:02.039> has<00:20:02.520> that<00:20:02.700> been<00:20:02.880> thought<00:20:03.000> through 00:20:03.169 --> 00:20:03.179 align:start position:0% of time or has that been thought through 00:20:03.179 --> 00:20:06.230 align:start position:0% of time or has that been thought through much<00:20:03.419> uh<00:20:04.260> leaving<00:20:04.440> or<00:20:04.740> joining<00:20:05.160> leaving 00:20:06.230 --> 00:20:06.240 align:start position:0% much uh leaving or joining leaving 00:20:06.240 --> 00:20:07.909 align:start position:0% much uh leaving or joining leaving um if<00:20:06.419> they're<00:20:06.539> leaving<00:20:06.720> so<00:20:07.200> they<00:20:07.440> can<00:20:07.559> they 00:20:07.909 --> 00:20:07.919 align:start position:0% um if they're leaving so they can they 00:20:07.919 --> 00:20:10.310 align:start position:0% um if they're leaving so they can they can<00:20:08.100> claim<00:20:08.400> any<00:20:08.640> assets<00:20:09.059> from<00:20:09.299> vesting<00:20:09.780> at<00:20:10.140> any 00:20:10.310 --> 00:20:10.320 align:start position:0% can claim any assets from vesting at any 00:20:10.320 --> 00:20:12.470 align:start position:0% can claim any assets from vesting at any point<00:20:10.620> but<00:20:11.460> there<00:20:11.640> are<00:20:11.760> windows<00:20:12.179> in<00:20:12.360> the 00:20:12.470 --> 00:20:12.480 align:start position:0% point but there are windows in the 00:20:12.480 --> 00:20:15.169 align:start position:0% point but there are windows in the contract<00:20:12.840> so<00:20:13.080> once<00:20:13.500> they<00:20:13.679> leave<00:20:14.179> contributing 00:20:15.169 --> 00:20:15.179 align:start position:0% contract so once they leave contributing 00:20:15.179 --> 00:20:16.970 align:start position:0% contract so once they leave contributing core<00:20:15.299> protocol<00:20:15.660> work<00:20:15.900> they<00:20:16.200> can<00:20:16.380> they<00:20:16.860> won't 00:20:16.970 --> 00:20:16.980 align:start position:0% core protocol work they can they won't 00:20:16.980 --> 00:20:19.549 align:start position:0% core protocol work they can they won't receive<00:20:17.340> future<00:20:17.580> vesting<00:20:18.179> but<00:20:18.600> they<00:20:19.020> they<00:20:19.380> can 00:20:19.549 --> 00:20:19.559 align:start position:0% receive future vesting but they they can 00:20:19.559 --> 00:20:21.169 align:start position:0% receive future vesting but they they can claim<00:20:19.860> at<00:20:19.980> any<00:20:20.160> time<00:20:20.340> it's<00:20:20.580> permissionless 00:20:21.169 --> 00:20:21.179 align:start position:0% claim at any time it's permissionless 00:20:21.179 --> 00:20:24.230 align:start position:0% claim at any time it's permissionless like<00:20:21.840> that<00:20:22.020> does<00:20:22.440> that<00:20:22.679> answer<00:20:23.100> yes<00:20:23.400> anybody 00:20:24.230 --> 00:20:24.240 align:start position:0% like that does that answer yes anybody 00:20:24.240 --> 00:20:27.169 align:start position:0% like that does that answer yes anybody else<00:20:24.480> I<00:20:25.260> have<00:20:25.440> one<00:20:25.679> sure<00:20:26.220> how<00:20:26.820> do<00:20:26.940> you<00:20:27.000> think 00:20:27.169 --> 00:20:27.179 align:start position:0% else I have one sure how do you think 00:20:27.179 --> 00:20:28.070 align:start position:0% else I have one sure how do you think about 00:20:28.070 --> 00:20:28.080 align:start position:0% about 00:20:28.080 --> 00:20:30.230 align:start position:0% about deciding<00:20:28.919> what<00:20:29.280> should<00:20:29.460> be<00:20:29.580> funded<00:20:29.880> and<00:20:30.059> how 00:20:30.230 --> 00:20:30.240 align:start position:0% deciding what should be funded and how 00:20:30.240 --> 00:20:32.390 align:start position:0% deciding what should be funded and how do<00:20:30.299> you<00:20:30.419> sort<00:20:30.539> of<00:20:30.720> in<00:20:31.260> a<00:20:31.440> way<00:20:31.500> prevent<00:20:31.980> or<00:20:32.220> get 00:20:32.390 --> 00:20:32.400 align:start position:0% do you sort of in a way prevent or get 00:20:32.400 --> 00:20:34.130 align:start position:0% do you sort of in a way prevent or get ahead<00:20:32.640> of<00:20:32.760> not<00:20:32.940> having<00:20:33.120> favoritism<00:20:33.720> kind<00:20:34.020> of 00:20:34.130 --> 00:20:34.140 align:start position:0% ahead of not having favoritism kind of 00:20:34.140 --> 00:20:36.470 align:start position:0% ahead of not having favoritism kind of come<00:20:34.200> into<00:20:34.320> play<00:20:34.620> yeah 00:20:36.470 --> 00:20:36.480 align:start position:0% come into play yeah 00:20:36.480 --> 00:20:37.970 align:start position:0% come into play yeah um<00:20:36.600> this<00:20:37.020> is<00:20:37.080> something<00:20:37.260> that<00:20:37.559> we've<00:20:37.799> been 00:20:37.970 --> 00:20:37.980 align:start position:0% um this is something that we've been 00:20:37.980 --> 00:20:39.409 align:start position:0% um this is something that we've been trying<00:20:38.160> to<00:20:38.340> iterate<00:20:38.640> on<00:20:38.820> through<00:20:39.000> the<00:20:39.120> pilot 00:20:39.409 --> 00:20:39.419 align:start position:0% trying to iterate on through the pilot 00:20:39.419 --> 00:20:40.610 align:start position:0% trying to iterate on through the pilot and<00:20:39.660> one<00:20:39.780> of<00:20:39.840> the<00:20:39.900> reasons<00:20:40.140> we<00:20:40.320> wanted<00:20:40.440> to 00:20:40.610 --> 00:20:40.620 align:start position:0% and one of the reasons we wanted to 00:20:40.620 --> 00:20:42.549 align:start position:0% and one of the reasons we wanted to start<00:20:40.799> really<00:20:40.980> small<00:20:41.220> I<00:20:41.520> mean<00:20:41.640> 10<00:20:41.880> million<00:20:42.299> is 00:20:42.549 --> 00:20:42.559 align:start position:0% start really small I mean 10 million is 00:20:42.559 --> 00:20:44.870 align:start position:0% start really small I mean 10 million is uh<00:20:43.559> it<00:20:43.740> may<00:20:43.860> seem<00:20:44.039> like<00:20:44.160> a<00:20:44.280> large<00:20:44.400> number<00:20:44.580> but 00:20:44.870 --> 00:20:44.880 align:start position:0% uh it may seem like a large number but 00:20:44.880 --> 00:20:46.610 align:start position:0% uh it may seem like a large number but split<00:20:45.240> between<00:20:45.419> 120<00:20:46.200> different<00:20:46.380> core 00:20:46.610 --> 00:20:46.620 align:start position:0% split between 120 different core 00:20:46.620 --> 00:20:48.830 align:start position:0% split between 120 different core contributors<00:20:47.220> it's<00:20:47.460> not<00:20:48.120> not<00:20:48.240> that<00:20:48.480> massive 00:20:48.830 --> 00:20:48.840 align:start position:0% contributors it's not not that massive 00:20:48.840 --> 00:20:51.409 align:start position:0% contributors it's not not that massive but<00:20:49.200> we<00:20:49.740> were<00:20:49.980> very<00:20:50.520> intentional<00:20:50.940> about<00:20:51.179> the 00:20:51.409 --> 00:20:51.419 align:start position:0% but we were very intentional about the 00:20:51.419 --> 00:20:53.150 align:start position:0% but we were very intentional about the amount<00:20:51.660> of<00:20:51.780> money<00:20:51.900> that<00:20:52.080> we're<00:20:52.200> raising<00:20:52.620> and 00:20:53.150 --> 00:20:53.160 align:start position:0% amount of money that we're raising and 00:20:53.160 --> 00:20:54.529 align:start position:0% amount of money that we're raising and and<00:20:53.400> that's<00:20:53.580> one<00:20:53.820> of<00:20:53.880> the<00:20:53.940> main<00:20:54.059> reasons<00:20:54.360> is 00:20:54.529 --> 00:20:54.539 align:start position:0% and that's one of the main reasons is 00:20:54.539 --> 00:20:57.650 align:start position:0% and that's one of the main reasons is because<00:20:54.780> the<00:20:55.679> eligibility<00:20:56.299> framework<00:20:57.299> isn't 00:20:57.650 --> 00:20:57.660 align:start position:0% because the eligibility framework isn't 00:20:57.660 --> 00:20:59.510 align:start position:0% because the eligibility framework isn't going<00:20:57.780> to<00:20:57.900> be<00:20:58.020> exactly<00:20:58.799> right<00:20:58.980> the<00:20:59.220> first<00:20:59.340> time 00:20:59.510 --> 00:20:59.520 align:start position:0% going to be exactly right the first time 00:20:59.520 --> 00:21:01.070 align:start position:0% going to be exactly right the first time and<00:20:59.760> we're<00:20:59.880> going<00:21:00.000> to<00:21:00.120> need<00:21:00.179> to<00:21:00.299> iterate<00:21:00.720> on<00:21:00.900> it 00:21:01.070 --> 00:21:01.080 align:start position:0% and we're going to need to iterate on it 00:21:01.080 --> 00:21:02.990 align:start position:0% and we're going to need to iterate on it and<00:21:01.559> so<00:21:01.799> that's<00:21:01.980> part<00:21:02.220> of<00:21:02.340> this<00:21:02.400> pilot<00:21:02.820> is 00:21:02.990 --> 00:21:03.000 align:start position:0% and so that's part of this pilot is 00:21:03.000 --> 00:21:04.610 align:start position:0% and so that's part of this pilot is figuring<00:21:03.419> out 00:21:04.610 --> 00:21:04.620 align:start position:0% figuring out 00:21:04.620 --> 00:21:06.710 align:start position:0% figuring out um what<00:21:05.520> sort<00:21:05.700> of<00:21:05.760> scope<00:21:05.940> we<00:21:06.179> want<00:21:06.360> to<00:21:06.419> take<00:21:06.539> on 00:21:06.710 --> 00:21:06.720 align:start position:0% um what sort of scope we want to take on 00:21:06.720 --> 00:21:08.330 align:start position:0% um what sort of scope we want to take on and<00:21:06.960> I<00:21:07.080> think<00:21:07.140> what<00:21:07.320> we've<00:21:07.559> learned<00:21:07.860> over<00:21:08.160> the 00:21:08.330 --> 00:21:08.340 align:start position:0% and I think what we've learned over the 00:21:08.340 --> 00:21:11.690 align:start position:0% and I think what we've learned over the past<00:21:08.460> six<00:21:08.700> months<00:21:09.000> since<00:21:09.539> May<00:21:09.780> is<00:21:10.320> that<00:21:10.700> it's 00:21:11.690 --> 00:21:11.700 align:start position:0% past six months since May is that it's 00:21:11.700 --> 00:21:13.730 align:start position:0% past six months since May is that it's probably<00:21:11.880> better<00:21:12.179> for<00:21:12.539> a<00:21:12.840> more<00:21:13.080> narrow<00:21:13.440> scope 00:21:13.730 --> 00:21:13.740 align:start position:0% probably better for a more narrow scope 00:21:13.740 --> 00:21:18.529 align:start position:0% probably better for a more narrow scope and<00:21:14.700> to<00:21:15.299> be<00:21:15.419> as<00:21:15.660> explicit<00:21:16.200> as<00:21:16.380> possible<00:21:16.740> so<00:21:17.700> if 00:21:18.529 --> 00:21:18.539 align:start position:0% and to be as explicit as possible so if 00:21:18.539 --> 00:21:20.210 align:start position:0% and to be as explicit as possible so if you're<00:21:18.720> working<00:21:18.840> on<00:21:19.080> a<00:21:19.260> research<00:21:19.559> team<00:21:19.799> if 00:21:20.210 --> 00:21:20.220 align:start position:0% you're working on a research team if 00:21:20.220 --> 00:21:21.350 align:start position:0% you're working on a research team if you're<00:21:20.400> contributing<00:21:20.760> to<00:21:20.880> a<00:21:21.000> client<00:21:21.120> code 00:21:21.350 --> 00:21:21.360 align:start position:0% you're contributing to a client code 00:21:21.360 --> 00:21:23.870 align:start position:0% you're contributing to a client code base<00:21:21.480> or<00:21:21.720> doing<00:21:21.900> coordination<00:21:22.640> we<00:21:23.640> want<00:21:23.760> to 00:21:23.870 --> 00:21:23.880 align:start position:0% base or doing coordination we want to 00:21:23.880 --> 00:21:26.090 align:start position:0% base or doing coordination we want to make<00:21:23.940> sure<00:21:24.120> that<00:21:24.480> it's<00:21:25.080> it's<00:21:25.320> very<00:21:25.620> clear<00:21:25.799> that 00:21:26.090 --> 00:21:26.100 align:start position:0% make sure that it's it's very clear that 00:21:26.100 --> 00:21:27.230 align:start position:0% make sure that it's it's very clear that these<00:21:26.280> are<00:21:26.400> people<00:21:26.580> who<00:21:26.760> are<00:21:26.880> contributing 00:21:27.230 --> 00:21:27.240 align:start position:0% these are people who are contributing 00:21:27.240 --> 00:21:30.529 align:start position:0% these are people who are contributing value<00:21:27.539> because<00:21:28.320> if<00:21:28.860> you<00:21:29.100> aren't<00:21:29.340> explicit<00:21:29.940> or 00:21:30.529 --> 00:21:30.539 align:start position:0% value because if you aren't explicit or 00:21:30.539 --> 00:21:32.330 align:start position:0% value because if you aren't explicit or don't<00:21:30.780> maintain<00:21:31.140> rigor<00:21:31.620> in<00:21:31.799> the<00:21:31.919> eligibility 00:21:32.330 --> 00:21:32.340 align:start position:0% don't maintain rigor in the eligibility 00:21:32.340 --> 00:21:35.090 align:start position:0% don't maintain rigor in the eligibility process<00:21:32.820> again<00:21:33.539> the<00:21:33.840> mechanism<00:21:34.200> will<00:21:34.620> lose 00:21:35.090 --> 00:21:35.100 align:start position:0% process again the mechanism will lose 00:21:35.100 --> 00:21:38.810 align:start position:0% process again the mechanism will lose its<00:21:35.400> value<00:21:35.580> it'll<00:21:36.360> become<00:21:36.720> a<00:21:37.620> lossy<00:21:38.340> signal 00:21:38.810 --> 00:21:38.820 align:start position:0% its value it'll become a lossy signal 00:21:38.820 --> 00:21:40.549 align:start position:0% its value it'll become a lossy signal for<00:21:39.120> people<00:21:39.360> who<00:21:39.539> are<00:21:39.659> interested<00:21:40.080> in 00:21:40.549 --> 00:21:40.559 align:start position:0% for people who are interested in 00:21:40.559 --> 00:21:42.049 align:start position:0% for people who are interested in contributing<00:21:41.039> to<00:21:41.220> something<00:21:41.400> that's<00:21:41.760> that's 00:21:42.049 --> 00:21:42.059 align:start position:0% contributing to something that's that's 00:21:42.059 --> 00:21:44.750 align:start position:0% contributing to something that's that's uh<00:21:43.020> going<00:21:43.559> to<00:21:43.679> get<00:21:43.799> their<00:21:43.980> money<00:21:44.100> to<00:21:44.400> go<00:21:44.520> to<00:21:44.580> the 00:21:44.750 --> 00:21:44.760 align:start position:0% uh going to get their money to go to the 00:21:44.760 --> 00:21:46.490 align:start position:0% uh going to get their money to go to the right<00:21:44.880> place<00:21:45.059> so 00:21:46.490 --> 00:21:46.500 align:start position:0% right place so 00:21:46.500 --> 00:21:48.770 align:start position:0% right place so um<00:21:46.559> make<00:21:47.039> sure<00:21:47.100> that<00:21:47.280> we're<00:21:47.460> iterating<00:21:47.880> and 00:21:48.770 --> 00:21:48.780 align:start position:0% um make sure that we're iterating and 00:21:48.780 --> 00:21:50.510 align:start position:0% um make sure that we're iterating and starting<00:21:48.960> small<00:21:49.320> is<00:21:49.559> how<00:21:49.980> we've<00:21:50.159> approached 00:21:50.510 --> 00:21:50.520 align:start position:0% starting small is how we've approached 00:21:50.520 --> 00:21:52.250 align:start position:0% starting small is how we've approached it<00:21:50.700> that's<00:21:51.299> great<00:21:51.539> and<00:21:51.780> just<00:21:51.960> out<00:21:52.080> of 00:21:52.250 --> 00:21:52.260 align:start position:0% it that's great and just out of 00:21:52.260 --> 00:21:53.570 align:start position:0% it that's great and just out of curiosity<00:21:52.559> did<00:21:52.799> you<00:21:52.919> kind<00:21:53.100> of<00:21:53.159> compare<00:21:53.400> this 00:21:53.570 --> 00:21:53.580 align:start position:0% curiosity did you kind of compare this 00:21:53.580 --> 00:21:55.070 align:start position:0% curiosity did you kind of compare this thing<00:21:53.700> with<00:21:53.880> the<00:21:54.000> retroactive<00:21:54.539> funding<00:21:54.900> model 00:21:55.070 --> 00:21:55.080 align:start position:0% thing with the retroactive funding model 00:21:55.080 --> 00:21:57.590 align:start position:0% thing with the retroactive funding model and<00:21:55.440> sort<00:21:55.799> of<00:21:55.919> what<00:21:56.159> was<00:21:56.460> kind<00:21:56.640> of<00:21:56.760> the<00:21:57.000> the 00:21:57.590 --> 00:21:57.600 align:start position:0% and sort of what was kind of the the 00:21:57.600 --> 00:21:59.570 align:start position:0% and sort of what was kind of the the pros<00:21:58.320> and<00:21:58.440> cons<00:21:58.559> list<00:21:58.919> that<00:21:59.100> you<00:21:59.220> made<00:21:59.340> made 00:21:59.570 --> 00:21:59.580 align:start position:0% pros and cons list that you made made 00:21:59.580 --> 00:22:01.250 align:start position:0% pros and cons list that you made made you<00:21:59.820> kind<00:22:00.000> of<00:22:00.059> pick<00:22:00.179> this<00:22:00.299> model<00:22:00.480> sure<00:22:00.900> so 00:22:01.250 --> 00:22:01.260 align:start position:0% you kind of pick this model sure so 00:22:01.260 --> 00:22:03.649 align:start position:0% you kind of pick this model sure so resurrective<00:22:01.919> funding<00:22:02.280> is<00:22:02.640> great<00:22:02.880> in<00:22:03.179> that<00:22:03.419> we 00:22:03.649 --> 00:22:03.659 align:start position:0% resurrective funding is great in that we 00:22:03.659 --> 00:22:05.230 align:start position:0% resurrective funding is great in that we can<00:22:03.780> also<00:22:03.960> plug<00:22:04.140> into<00:22:04.320> that 00:22:05.230 --> 00:22:05.240 align:start position:0% can also plug into that 00:22:05.240 --> 00:22:08.690 align:start position:0% can also plug into that however<00:22:06.240> uh<00:22:07.200> these<00:22:07.860> individual<00:22:08.159> teams<00:22:08.520> they 00:22:08.690 --> 00:22:08.700 align:start position:0% however uh these individual teams they 00:22:08.700 --> 00:22:10.310 align:start position:0% however uh these individual teams they don't<00:22:08.820> have<00:22:09.000> to<00:22:09.120> apply<00:22:09.360> on<00:22:09.539> their<00:22:09.720> own<00:22:09.840> or<00:22:10.140> the 00:22:10.310 --> 00:22:10.320 align:start position:0% don't have to apply on their own or the 00:22:10.320 --> 00:22:12.830 align:start position:0% don't have to apply on their own or the the<00:22:10.500> because<00:22:11.280> protocol<00:22:11.760> protocol<00:22:12.240> Guild<00:22:12.539> is 00:22:12.830 --> 00:22:12.840 align:start position:0% the because protocol protocol Guild is 00:22:12.840 --> 00:22:14.930 align:start position:0% the because protocol protocol Guild is biased<00:22:13.260> towards<00:22:13.500> the<00:22:13.620> individual 00:22:14.930 --> 00:22:14.940 align:start position:0% biased towards the individual 00:22:14.940 --> 00:22:16.130 align:start position:0% biased towards the individual um<00:22:15.000> it's<00:22:15.240> you<00:22:15.419> can<00:22:15.539> imagine<00:22:15.659> it's<00:22:15.900> sort<00:22:16.080> of 00:22:16.130 --> 00:22:16.140 align:start position:0% um it's you can imagine it's sort of 00:22:16.140 --> 00:22:17.690 align:start position:0% um it's you can imagine it's sort of like<00:22:16.200> a<00:22:16.320> collective<00:22:16.679> or<00:22:16.919> a<00:22:17.159> union<00:22:17.340> that 00:22:17.690 --> 00:22:17.700 align:start position:0% like a collective or a union that 00:22:17.700 --> 00:22:20.450 align:start position:0% like a collective or a union that represents<00:22:18.240> them<00:22:18.419> and<00:22:19.260> makes<00:22:19.740> it<00:22:19.980> very<00:22:20.280> very 00:22:20.450 --> 00:22:20.460 align:start position:0% represents them and makes it very very 00:22:20.460 --> 00:22:23.149 align:start position:0% represents them and makes it very very straightforward<00:22:21.120> for<00:22:21.600> people<00:22:22.260> interested<00:22:23.039> in 00:22:23.149 --> 00:22:23.159 align:start position:0% straightforward for people interested in 00:22:23.159 --> 00:22:25.130 align:start position:0% straightforward for people interested in funding<00:22:23.460> like<00:22:23.580> like<00:22:23.760> optimisms<00:22:24.480> retroactive 00:22:25.130 --> 00:22:25.140 align:start position:0% funding like like optimisms retroactive 00:22:25.140 --> 00:22:28.190 align:start position:0% funding like like optimisms retroactive funding<00:22:25.919> program<00:22:26.220> they<00:22:27.120> can<00:22:27.360> just<00:22:27.780> point<00:22:28.020> it 00:22:28.190 --> 00:22:28.200 align:start position:0% funding program they can just point it 00:22:28.200 --> 00:22:29.690 align:start position:0% funding program they can just point it to<00:22:28.320> a<00:22:28.440> single<00:22:28.679> address<00:22:28.860> and<00:22:29.280> scale<00:22:29.520> it 00:22:29.690 --> 00:22:29.700 align:start position:0% to a single address and scale it 00:22:29.700 --> 00:22:31.190 align:start position:0% to a single address and scale it accordingly<00:22:30.179> however<00:22:30.539> much<00:22:30.659> they'd<00:22:30.960> like<00:22:31.080> to 00:22:31.190 --> 00:22:31.200 align:start position:0% accordingly however much they'd like to 00:22:31.200 --> 00:22:34.250 align:start position:0% accordingly however much they'd like to give<00:22:31.380> back<00:22:31.640> rather<00:22:32.640> than<00:22:32.940> uh<00:22:33.900> possibly 00:22:34.250 --> 00:22:34.260 align:start position:0% give back rather than uh possibly 00:22:34.260 --> 00:22:35.750 align:start position:0% give back rather than uh possibly missing<00:22:34.620> somebody<00:22:34.799> who<00:22:35.039> did<00:22:35.220> crucial<00:22:35.520> work 00:22:35.750 --> 00:22:35.760 align:start position:0% missing somebody who did crucial work 00:22:35.760 --> 00:22:38.330 align:start position:0% missing somebody who did crucial work over<00:22:36.059> the<00:22:36.240> past<00:22:36.360> two<00:22:36.600> years<00:22:37.100> they<00:22:38.100> can<00:22:38.220> rest 00:22:38.330 --> 00:22:38.340 align:start position:0% over the past two years they can rest 00:22:38.340 --> 00:22:40.130 align:start position:0% over the past two years they can rest assured<00:22:38.700> that<00:22:38.880> this<00:22:39.059> is<00:22:39.179> this<00:22:39.480> is<00:22:39.600> a<00:22:39.780> mechanism 00:22:40.130 --> 00:22:40.140 align:start position:0% assured that this is this is a mechanism 00:22:40.140 --> 00:22:41.450 align:start position:0% assured that this is this is a mechanism that's<00:22:40.380> going<00:22:40.559> to<00:22:40.679> be<00:22:40.740> very<00:22:40.980> very<00:22:41.100> tightly 00:22:41.450 --> 00:22:41.460 align:start position:0% that's going to be very very tightly 00:22:41.460 --> 00:22:44.510 align:start position:0% that's going to be very very tightly curated<00:22:41.900> but<00:22:42.900> yeah<00:22:43.080> I'm<00:22:43.440> super<00:22:43.860> excited<00:22:44.220> to 00:22:44.510 --> 00:22:44.520 align:start position:0% curated but yeah I'm super excited to 00:22:44.520 --> 00:22:46.549 align:start position:0% curated but yeah I'm super excited to plug<00:22:44.820> into<00:22:45.059> retroactive<00:22:45.960> funding<00:22:46.260> continue 00:22:46.549 --> 00:22:46.559 align:start position:0% plug into retroactive funding continue 00:22:46.559 --> 00:22:48.770 align:start position:0% plug into retroactive funding continue to<00:22:47.100> have<00:22:47.460> a<00:22:47.640> good<00:22:47.700> coin<00:22:48.059> Grant<00:22:48.299> things<00:22:48.600> like 00:22:48.770 --> 00:22:48.780 align:start position:0% to have a good coin Grant things like 00:22:48.780 --> 00:22:51.470 align:start position:0% to have a good coin Grant things like that<00:22:49.020> is<00:22:49.500> uh<00:22:49.980> all<00:22:50.460> possible<00:22:50.820> and<00:22:51.179> I'm<00:22:51.360> sure 00:22:51.470 --> 00:22:51.480 align:start position:0% that is uh all possible and I'm sure 00:22:51.480 --> 00:22:52.789 align:start position:0% that is uh all possible and I'm sure there<00:22:51.600> will<00:22:51.780> be<00:22:51.840> even<00:22:51.960> more<00:22:52.140> mechanisms<00:22:52.620> in 00:22:52.789 --> 00:22:52.799 align:start position:0% there will be even more mechanisms in 00:22:52.799 --> 00:22:55.250 align:start position:0% there will be even more mechanisms in the<00:22:52.919> future<00:22:53.039> that<00:22:53.520> are<00:22:54.000> a<00:22:54.179> good<00:22:54.299> fit<00:22:54.539> for<00:22:54.900> these 00:22:55.250 --> 00:22:55.260 align:start position:0% the future that are a good fit for these 00:22:55.260 --> 00:22:56.690 align:start position:0% the future that are a good fit for these types<00:22:55.440> of<00:22:55.500> things<00:22:55.679> awesome<00:22:55.980> to<00:22:56.340> any<00:22:56.580> other 00:22:56.690 --> 00:22:56.700 align:start position:0% types of things awesome to any other 00:22:56.700 --> 00:22:58.430 align:start position:0% types of things awesome to any other last<00:22:56.940> questions<00:22:57.179> great<00:22:57.780> well<00:22:58.020> please<00:22:58.260> give 00:22:58.430 --> 00:22:58.440 align:start position:0% last questions great well please give 00:22:58.440 --> 00:23:01.130 align:start position:0% last questions great well please give Trent<00:22:58.740> a<00:22:58.980> big<00:22:59.100> round<00:22:59.220> of<00:22:59.400> applause<00:22:59.700> thank<00:23:00.360> you 00:23:01.130 --> 00:23:01.140 align:start position:0% Trent a big round of applause thank you 00:23:01.140 --> 00:23:05.659 align:start position:0% Trent a big round of applause thank you [Applause]