WEBVTT Kind: captions Language: en 00:00:04.580 --> 00:00:10.629 align:start position:0% so<00:00:05.240> welcome<00:00:06.640> we<00:00:07.640> are<00:00:07.670> here<00:00:08.120> to<00:00:08.420> talk<00:00:09.020> about<00:00:09.639> in 00:00:10.629 --> 00:00:10.639 align:start position:0% so welcome we are here to talk about in 00:00:10.639 --> 00:00:13.000 align:start position:0% so welcome we are here to talk about in Fuhrer<00:00:11.059> how<00:00:11.450> we're<00:00:11.630> hooked<00:00:11.840> on<00:00:12.020> it<00:00:12.170> and<00:00:12.560> what 00:00:13.000 --> 00:00:13.010 align:start position:0% Fuhrer how we're hooked on it and what 00:00:13.010 --> 00:00:14.250 align:start position:0% Fuhrer how we're hooked on it and what we're<00:00:13.130> gonna<00:00:13.220> do<00:00:13.460> about<00:00:13.610> it 00:00:14.250 --> 00:00:14.260 align:start position:0% we're gonna do about it 00:00:14.260 --> 00:00:17.530 align:start position:0% we're gonna do about it my<00:00:15.260> name<00:00:15.440> is<00:00:15.530> Jason<00:00:16.070> Carver<00:00:16.460> I<00:00:16.670> work<00:00:17.090> at<00:00:17.330> the 00:00:17.530 --> 00:00:17.540 align:start position:0% my name is Jason Carver I work at the 00:00:17.540 --> 00:00:20.679 align:start position:0% my name is Jason Carver I work at the ethereum<00:00:18.260> foundation<00:00:18.970> on<00:00:19.970> all<00:00:20.270> sorts<00:00:20.630> of 00:00:20.679 --> 00:00:20.689 align:start position:0% ethereum foundation on all sorts of 00:00:20.689 --> 00:00:24.040 align:start position:0% ethereum foundation on all sorts of Python<00:00:21.110> tooling<00:00:21.590> as<00:00:21.829> well<00:00:22.250> as<00:00:22.550> the<00:00:23.210> Trinity 00:00:24.040 --> 00:00:24.050 align:start position:0% Python tooling as well as the Trinity 00:00:24.050 --> 00:00:29.380 align:start position:0% Python tooling as well as the Trinity Python<00:00:24.890> client<00:00:25.599> let's<00:00:26.599> get<00:00:26.779> started<00:00:27.259> so<00:00:28.390> why 00:00:29.380 --> 00:00:29.390 align:start position:0% Python client let's get started so why 00:00:29.390 --> 00:00:31.960 align:start position:0% Python client let's get started so why are<00:00:29.720> we<00:00:29.750> hooked<00:00:30.050> to<00:00:30.200> in<00:00:30.259> fear<00:00:30.560> obviously<00:00:31.399> it's 00:00:31.960 --> 00:00:31.970 align:start position:0% are we hooked to in fear obviously it's 00:00:31.970 --> 00:00:38.860 align:start position:0% are we hooked to in fear obviously it's delicious<00:00:33.730> it<00:00:34.730> is<00:00:36.219> an<00:00:37.219> obvious<00:00:37.820> thing<00:00:38.030> for<00:00:38.090> DAP 00:00:38.860 --> 00:00:38.870 align:start position:0% delicious it is an obvious thing for DAP 00:00:38.870 --> 00:00:43.000 align:start position:0% delicious it is an obvious thing for DAP developers<00:00:39.559> to<00:00:41.440> make<00:00:42.440> it<00:00:42.620> as<00:00:42.710> easy<00:00:42.890> as 00:00:43.000 --> 00:00:43.010 align:start position:0% developers to make it as easy as 00:00:43.010 --> 00:00:45.729 align:start position:0% developers to make it as easy as possible<00:00:43.100> for<00:00:43.730> new<00:00:43.760> people<00:00:44.030> to<00:00:44.379> sign<00:00:45.379> up<00:00:45.410> and 00:00:45.729 --> 00:00:45.739 align:start position:0% possible for new people to sign up and 00:00:45.739 --> 00:00:49.360 align:start position:0% possible for new people to sign up and use<00:00:45.980> their<00:00:46.190> app<00:00:46.340> and<00:00:47.649> similarly<00:00:48.649> plugins<00:00:49.190> like 00:00:49.360 --> 00:00:49.370 align:start position:0% use their app and similarly plugins like 00:00:49.370 --> 00:00:50.380 align:start position:0% use their app and similarly plugins like meta<00:00:49.609> masks 00:00:50.380 --> 00:00:50.390 align:start position:0% meta masks 00:00:50.390 --> 00:00:54.220 align:start position:0% meta masks ignosi<00:00:50.929> and<00:00:51.620> so<00:00:52.460> on<00:00:52.609> or<00:00:52.969> have<00:00:53.929> the<00:00:54.079> same 00:00:54.220 --> 00:00:54.230 align:start position:0% ignosi and so on or have the same 00:00:54.230 --> 00:00:58.180 align:start position:0% ignosi and so on or have the same incentives<00:00:54.769> right<00:00:55.070> so<00:00:55.660> in<00:00:56.660> fury<00:00:56.960> is<00:00:57.350> a<00:00:57.890> way<00:00:58.129> to 00:00:58.180 --> 00:00:58.190 align:start position:0% incentives right so in fury is a way to 00:00:58.190 --> 00:01:01.689 align:start position:0% incentives right so in fury is a way to skip<00:00:58.910> the<00:00:59.030> install<00:00:59.390> of<00:00:59.420> the<00:00:59.600> node<00:01:00.370> skip<00:01:01.370> the 00:01:01.689 --> 00:01:01.699 align:start position:0% skip the install of the node skip the 00:01:01.699 --> 00:01:03.610 align:start position:0% skip the install of the node skip the sinking<00:01:02.179> of<00:01:02.269> the<00:01:02.329> node<00:01:02.570> and<00:01:02.929> get<00:01:03.109> people<00:01:03.440> on 00:01:03.610 --> 00:01:03.620 align:start position:0% sinking of the node and get people on 00:01:03.620 --> 00:01:07.180 align:start position:0% sinking of the node and get people on board<00:01:04.030> fairly<00:01:05.030> obvious<00:01:05.620> setup<00:01:06.620> why<00:01:06.860> that's 00:01:07.180 --> 00:01:07.190 align:start position:0% board fairly obvious setup why that's 00:01:07.190 --> 00:01:09.640 align:start position:0% board fairly obvious setup why that's easier<00:01:08.000> and<00:01:08.330> more<00:01:08.720> pleasant<00:01:09.020> for<00:01:09.440> a<00:01:09.470> lot<00:01:09.620> of 00:01:09.640 --> 00:01:09.650 align:start position:0% easier and more pleasant for a lot of 00:01:09.650 --> 00:01:12.160 align:start position:0% easier and more pleasant for a lot of users<00:01:09.830> and<00:01:10.190> frankly<00:01:11.060> for<00:01:11.300> a<00:01:11.360> lot<00:01:11.660> of<00:01:11.780> casual 00:01:12.160 --> 00:01:12.170 align:start position:0% users and frankly for a lot of casual 00:01:12.170 --> 00:01:14.140 align:start position:0% users and frankly for a lot of casual users<00:01:12.530> you<00:01:12.890> know<00:01:12.980> 80<00:01:13.460> to<00:01:13.520> 90<00:01:13.850> percent<00:01:14.090> of 00:01:14.140 --> 00:01:14.150 align:start position:0% users you know 80 to 90 percent of 00:01:14.150 --> 00:01:16.030 align:start position:0% users you know 80 to 90 percent of people<00:01:14.420> they're<00:01:15.050> always<00:01:15.560> gonna<00:01:15.830> minimize 00:01:16.030 --> 00:01:16.040 align:start position:0% people they're always gonna minimize 00:01:16.040 --> 00:01:17.920 align:start position:0% people they're always gonna minimize effort<00:01:16.520> they're<00:01:16.760> they're<00:01:17.210> very<00:01:17.480> willing<00:01:17.660> to 00:01:17.920 --> 00:01:17.930 align:start position:0% effort they're they're very willing to 00:01:17.930 --> 00:01:21.150 align:start position:0% effort they're they're very willing to make<00:01:18.110> trade-offs<00:01:18.380> about<00:01:19.330> trust<00:01:20.330> and 00:01:21.150 --> 00:01:21.160 align:start position:0% make trade-offs about trust and 00:01:21.160 --> 00:01:25.960 align:start position:0% make trade-offs about trust and custodianship<00:01:22.160> to<00:01:22.750> to<00:01:23.750> make<00:01:24.110> it<00:01:24.230> easy<00:01:24.970> but 00:01:25.960 --> 00:01:25.970 align:start position:0% custodianship to to make it easy but 00:01:25.970 --> 00:01:28.960 align:start position:0% custodianship to to make it easy but there<00:01:26.480> is<00:01:26.630> a<00:01:26.960> set<00:01:27.920> of<00:01:28.100> users<00:01:28.520> that<00:01:28.730> were 00:01:28.960 --> 00:01:28.970 align:start position:0% there is a set of users that were 00:01:28.970 --> 00:01:31.870 align:start position:0% there is a set of users that were interested<00:01:29.600> in<00:01:29.750> the<00:01:30.500> sophisticated<00:01:31.460> users 00:01:31.870 --> 00:01:31.880 align:start position:0% interested in the sophisticated users 00:01:31.880 --> 00:01:34.420 align:start position:0% interested in the sophisticated users whether<00:01:32.210> that's<00:01:32.600> hobbyists<00:01:33.290> or<00:01:33.440> people 00:01:34.420 --> 00:01:34.430 align:start position:0% whether that's hobbyists or people 00:01:34.430 --> 00:01:36.130 align:start position:0% whether that's hobbyists or people writing<00:01:34.730> scripts<00:01:35.030> to<00:01:35.210> interact<00:01:35.600> with<00:01:35.900> the 00:01:36.130 --> 00:01:36.140 align:start position:0% writing scripts to interact with the 00:01:36.140 --> 00:01:37.890 align:start position:0% writing scripts to interact with the chain<00:01:36.350> and<00:01:36.620> they're<00:01:36.980> willing<00:01:37.250> to<00:01:37.280> do<00:01:37.460> more 00:01:37.890 --> 00:01:37.900 align:start position:0% chain and they're willing to do more 00:01:37.900 --> 00:01:39.730 align:start position:0% chain and they're willing to do more they're<00:01:38.900> willing<00:01:39.170> to<00:01:39.200> put<00:01:39.380> in<00:01:39.500> some<00:01:39.530> more 00:01:39.730 --> 00:01:39.740 align:start position:0% they're willing to put in some more 00:01:39.740 --> 00:01:44.080 align:start position:0% they're willing to put in some more effort<00:01:40.390> so<00:01:41.390> the<00:01:42.020> problem<00:01:42.410> is<00:01:42.560> when<00:01:42.860> they<00:01:43.090> try 00:01:44.080 --> 00:01:44.090 align:start position:0% effort so the problem is when they try 00:01:44.090 --> 00:01:46.120 align:start position:0% effort so the problem is when they try that<00:01:44.450> they<00:01:44.900> go<00:01:45.110> out<00:01:45.290> and<00:01:45.620> look<00:01:46.100> for 00:01:46.120 --> 00:01:46.130 align:start position:0% that they go out and look for 00:01:46.130 --> 00:01:49.450 align:start position:0% that they go out and look for documentation<00:01:47.380> they<00:01:48.380> look<00:01:48.680> for<00:01:48.980> help<00:01:49.190> in<00:01:49.340> the 00:01:49.450 --> 00:01:49.460 align:start position:0% documentation they look for help in the 00:01:49.460 --> 00:01:51.640 align:start position:0% documentation they look for help in the apps<00:01:49.640> and<00:01:50.090> they<00:01:50.780> don't<00:01:50.960> find<00:01:51.110> anything<00:01:51.380> it's 00:01:51.640 --> 00:01:51.650 align:start position:0% apps and they don't find anything it's 00:01:51.650 --> 00:01:55.600 align:start position:0% apps and they don't find anything it's all<00:01:51.800> built<00:01:52.070> for<00:01:52.430> that<00:01:52.460> 80%<00:01:53.240> user<00:01:53.750> and<00:01:54.050> so<00:01:54.890> they 00:01:55.600 --> 00:01:55.610 align:start position:0% all built for that 80% user and so they 00:01:55.610 --> 00:01:58.360 align:start position:0% all built for that 80% user and so they just<00:01:55.690> skip<00:01:56.690> over<00:01:56.840> it<00:01:56.990> and<00:01:57.260> and<00:01:58.040> they<00:01:58.220> often 00:01:58.360 --> 00:01:58.370 align:start position:0% just skip over it and and they often 00:01:58.370 --> 00:02:00.040 align:start position:0% just skip over it and and they often don't<00:01:58.520> have<00:01:58.670> any<00:01:58.880> trigger<00:01:59.330> or<00:01:59.510> later<00:01:59.660> to 00:02:00.040 --> 00:02:00.050 align:start position:0% don't have any trigger or later to 00:02:00.050 --> 00:02:03.820 align:start position:0% don't have any trigger or later to switch<00:02:00.950> over<00:02:01.100> to<00:02:01.280> something<00:02:02.000> different<00:02:02.830> so 00:02:03.820 --> 00:02:03.830 align:start position:0% switch over to something different so 00:02:03.830 --> 00:02:06.790 align:start position:0% switch over to something different so maybe<00:02:04.730> that's<00:02:05.030> okay<00:02:05.390> you<00:02:05.690> know<00:02:05.750> how<00:02:06.020> how<00:02:06.470> bad 00:02:06.790 --> 00:02:06.800 align:start position:0% maybe that's okay you know how how bad 00:02:06.800 --> 00:02:08.350 align:start position:0% maybe that's okay you know how how bad is<00:02:07.100> that<00:02:07.130> what<00:02:07.490> how<00:02:07.640> bigger<00:02:07.880> problem<00:02:08.239> is<00:02:08.330> that 00:02:08.350 --> 00:02:08.360 align:start position:0% is that what how bigger problem is that 00:02:08.360 --> 00:02:11.559 align:start position:0% is that what how bigger problem is that well<00:02:09.670> you<00:02:10.670> know<00:02:10.759> there's<00:02:10.940> some<00:02:11.060> obvious<00:02:11.180> ones 00:02:11.559 --> 00:02:11.569 align:start position:0% well you know there's some obvious ones 00:02:11.569 --> 00:02:14.890 align:start position:0% well you know there's some obvious ones like<00:02:11.720> concerns<00:02:12.710> about<00:02:12.890> downtime<00:02:13.580> you<00:02:14.420> know<00:02:14.810> in 00:02:14.890 --> 00:02:14.900 align:start position:0% like concerns about downtime you know in 00:02:14.900 --> 00:02:16.030 align:start position:0% like concerns about downtime you know in fear<00:02:15.110> is<00:02:15.200> gonna<00:02:15.350> be<00:02:15.470> a<00:02:15.500> single<00:02:15.740> point<00:02:15.920> of 00:02:16.030 --> 00:02:16.040 align:start position:0% fear is gonna be a single point of 00:02:16.040 --> 00:02:17.590 align:start position:0% fear is gonna be a single point of failure<00:02:16.100> and<00:02:16.760> no<00:02:16.970> matter<00:02:17.090> how<00:02:17.270> good<00:02:17.450> their 00:02:17.590 --> 00:02:17.600 align:start position:0% failure and no matter how good their 00:02:17.600 --> 00:02:18.430 align:start position:0% failure and no matter how good their systems<00:02:17.960> are<00:02:18.110> and 00:02:18.430 --> 00:02:18.440 align:start position:0% systems are and 00:02:18.440 --> 00:02:23.410 align:start position:0% systems are and they're<00:02:18.740> very<00:02:18.950> good<00:02:20.740> perhaps<00:02:21.850> the<00:02:22.850> worst<00:02:23.060> is 00:02:23.410 --> 00:02:23.420 align:start position:0% they're very good perhaps the worst is 00:02:23.420 --> 00:02:27.310 align:start position:0% they're very good perhaps the worst is that<00:02:23.810> in<00:02:24.470> fear<00:02:25.010> makes<00:02:25.250> a<00:02:25.310> bad<00:02:25.460> hire<00:02:25.730> or<00:02:26.320> someone 00:02:27.310 --> 00:02:27.320 align:start position:0% that in fear makes a bad hire or someone 00:02:27.320 --> 00:02:30.160 align:start position:0% that in fear makes a bad hire or someone cracks<00:02:27.680> into<00:02:27.860> their<00:02:28.040> systems<00:02:28.430> and<00:02:28.930> they<00:02:29.930> serve 00:02:30.160 --> 00:02:30.170 align:start position:0% cracks into their systems and they serve 00:02:30.170 --> 00:02:32.860 align:start position:0% cracks into their systems and they serve you<00:02:30.320> bad<00:02:30.500> data<00:02:30.740> now<00:02:31.430> they<00:02:31.640> can't<00:02:31.910> explicitly 00:02:32.860 --> 00:02:32.870 align:start position:0% you bad data now they can't explicitly 00:02:32.870 --> 00:02:35.950 align:start position:0% you bad data now they can't explicitly directly<00:02:33.790> say<00:02:34.790> send<00:02:35.090> your<00:02:35.270> funds<00:02:35.510> from<00:02:35.810> one 00:02:35.950 --> 00:02:35.960 align:start position:0% directly say send your funds from one 00:02:35.960 --> 00:02:38.860 align:start position:0% directly say send your funds from one account<00:02:36.170> to<00:02:36.290> another<00:02:36.380> or<00:02:36.770> your<00:02:36.950> assets<00:02:37.340> but<00:02:38.090> if 00:02:38.860 --> 00:02:38.870 align:start position:0% account to another or your assets but if 00:02:38.870 --> 00:02:42.730 align:start position:0% account to another or your assets but if they<00:02:39.650> can<00:02:39.860> control<00:02:40.540> the<00:02:41.540> view<00:02:42.260> of<00:02:42.440> the<00:02:42.560> world 00:02:42.730 --> 00:02:42.740 align:start position:0% they can control the view of the world 00:02:42.740 --> 00:02:45.910 align:start position:0% they can control the view of the world you<00:02:42.890> have<00:02:43.190> it<00:02:44.150> is<00:02:44.510> pretty<00:02:45.290> straightforward<00:02:45.890> to 00:02:45.910 --> 00:02:45.920 align:start position:0% you have it is pretty straightforward to 00:02:45.920 --> 00:02:48.670 align:start position:0% you have it is pretty straightforward to get<00:02:46.040> you<00:02:46.190> to<00:02:46.430> send<00:02:47.090> funds<00:02:47.420> or<00:02:47.810> assets<00:02:48.350> to<00:02:48.530> the 00:02:48.670 --> 00:02:48.680 align:start position:0% get you to send funds or assets to the 00:02:48.680 --> 00:02:50.710 align:start position:0% get you to send funds or assets to the whatever<00:02:49.550> address<00:02:49.850> they<00:02:50.180> choose<00:02:50.420> for<00:02:50.690> example 00:02:50.710 --> 00:02:50.720 align:start position:0% whatever address they choose for example 00:02:50.720 --> 00:02:53.830 align:start position:0% whatever address they choose for example by<00:02:51.350> resolving<00:02:51.740> an<00:02:52.070> ENS<00:02:52.460> name<00:02:52.730> to<00:02:53.420> a<00:02:53.450> different 00:02:53.830 --> 00:02:53.840 align:start position:0% by resolving an ENS name to a different 00:02:53.840 --> 00:02:57.190 align:start position:0% by resolving an ENS name to a different address<00:02:53.960> than<00:02:54.410> the<00:02:54.620> real<00:02:54.770> main<00:02:55.010> that<00:02:55.190> one<00:02:56.200> and 00:02:57.190 --> 00:02:57.200 align:start position:0% address than the real main that one and 00:02:57.200 --> 00:02:59.080 align:start position:0% address than the real main that one and some<00:02:57.680> other<00:02:57.830> things<00:02:58.100> like<00:02:58.220> leaking<00:02:58.790> private 00:02:59.080 --> 00:02:59.090 align:start position:0% some other things like leaking private 00:02:59.090 --> 00:03:00.610 align:start position:0% some other things like leaking private data<00:02:59.240> everything<00:02:59.900> about<00:03:00.050> who<00:03:00.230> you<00:03:00.380> are<00:03:00.410> and 00:03:00.610 --> 00:03:00.620 align:start position:0% data everything about who you are and 00:03:00.620 --> 00:03:03.550 align:start position:0% data everything about who you are and what<00:03:00.740> you're<00:03:00.890> doing<00:03:01.220> is<00:03:01.490> going<00:03:01.760> out<00:03:02.030> -<00:03:02.420> -<00:03:03.380> and 00:03:03.550 --> 00:03:03.560 align:start position:0% what you're doing is going out - - and 00:03:03.560 --> 00:03:05.940 align:start position:0% what you're doing is going out - - and Fuhrer<00:03:03.740> and<00:03:03.890> the<00:03:04.160> other<00:03:04.330> Absalon<00:03:05.330> way<00:03:05.540> and 00:03:05.940 --> 00:03:05.950 align:start position:0% Fuhrer and the other Absalon way and 00:03:05.950 --> 00:03:10.870 align:start position:0% Fuhrer and the other Absalon way and slightly<00:03:06.950> more<00:03:07.220> subtly<00:03:08.320> the<00:03:09.320> more<00:03:09.700> the<00:03:10.700> more 00:03:10.870 --> 00:03:10.880 align:start position:0% slightly more subtly the more the more 00:03:10.880 --> 00:03:12.610 align:start position:0% slightly more subtly the more the more people<00:03:11.150> the<00:03:11.720> fewer<00:03:11.990> people<00:03:12.170> that<00:03:12.320> are<00:03:12.530> running 00:03:12.610 --> 00:03:12.620 align:start position:0% people the fewer people that are running 00:03:12.620 --> 00:03:15.130 align:start position:0% people the fewer people that are running nodes<00:03:12.980> the<00:03:13.730> easier<00:03:14.090> it<00:03:14.210> is<00:03:14.300> to<00:03:14.360> spin<00:03:14.720> up<00:03:14.870> other 00:03:15.130 --> 00:03:15.140 align:start position:0% nodes the easier it is to spin up other 00:03:15.140 --> 00:03:19.180 align:start position:0% nodes the easier it is to spin up other nodes<00:03:15.500> and<00:03:15.890> do<00:03:16.610> slight<00:03:17.570> manipulations<00:03:18.350> like 00:03:19.180 --> 00:03:19.190 align:start position:0% nodes and do slight manipulations like 00:03:19.190 --> 00:03:25.270 align:start position:0% nodes and do slight manipulations like eclipse<00:03:19.460> attacks<00:03:22.120> so<00:03:23.650> it's<00:03:24.650> here<00:03:24.860> it's<00:03:25.190> a 00:03:25.270 --> 00:03:25.280 align:start position:0% eclipse attacks so it's here it's a 00:03:25.280 --> 00:03:26.710 align:start position:0% eclipse attacks so it's here it's a problem<00:03:25.610> what<00:03:26.150> are<00:03:26.209> we<00:03:26.270> gonna<00:03:26.390> do<00:03:26.510> about<00:03:26.540> it 00:03:26.710 --> 00:03:26.720 align:start position:0% problem what are we gonna do about it 00:03:26.720 --> 00:03:28.870 align:start position:0% problem what are we gonna do about it well<00:03:27.680> there's<00:03:28.310> a<00:03:28.340> lot<00:03:28.459> of<00:03:28.520> different<00:03:28.760> avenues 00:03:28.870 --> 00:03:28.880 align:start position:0% well there's a lot of different avenues 00:03:28.880 --> 00:03:32.760 align:start position:0% well there's a lot of different avenues to<00:03:29.630> approach<00:03:30.320> this<00:03:30.560> with<00:03:30.850> and<00:03:31.850> there<00:03:32.120> is 00:03:32.760 --> 00:03:32.770 align:start position:0% to approach this with and there is 00:03:32.770 --> 00:03:35.290 align:start position:0% to approach this with and there is dedicated<00:03:33.770> hardware<00:03:34.130> like<00:03:34.370> DAP<00:03:34.610> node<00:03:34.880> or<00:03:35.150> good 00:03:35.290 --> 00:03:35.300 align:start position:0% dedicated hardware like DAP node or good 00:03:35.300 --> 00:03:37.630 align:start position:0% dedicated hardware like DAP node or good plus<00:03:35.860> there's<00:03:36.860> people<00:03:37.160> looking<00:03:37.459> at<00:03:37.550> the 00:03:37.630 --> 00:03:37.640 align:start position:0% plus there's people looking at the 00:03:37.640 --> 00:03:40.990 align:start position:0% plus there's people looking at the problem<00:03:38.000> of<00:03:38.030> how<00:03:39.020> much<00:03:39.170> storage<00:03:39.500> it<00:03:39.800> takes<00:03:40.040> to 00:03:40.990 --> 00:03:41.000 align:start position:0% problem of how much storage it takes to 00:03:41.000 --> 00:03:42.940 align:start position:0% problem of how much storage it takes to to<00:03:41.690> use<00:03:41.840> on<00:03:41.990> your<00:03:42.080> computer<00:03:42.230> there's<00:03:42.800> people 00:03:42.940 --> 00:03:42.950 align:start position:0% to use on your computer there's people 00:03:42.950 --> 00:03:47.860 align:start position:0% to use on your computer there's people looking<00:03:43.220> at<00:03:43.520> peer<00:03:43.760> discovery<00:03:44.650> and<00:03:46.630> the<00:03:47.630> thing 00:03:47.860 --> 00:03:47.870 align:start position:0% looking at peer discovery and the thing 00:03:47.870 --> 00:03:50.260 align:start position:0% looking at peer discovery and the thing that<00:03:48.020> we've<00:03:48.260> found<00:03:48.530> to<00:03:48.980> be<00:03:49.459> one<00:03:50.120> of<00:03:50.180> the 00:03:50.260 --> 00:03:50.270 align:start position:0% that we've found to be one of the 00:03:50.270 --> 00:03:52.180 align:start position:0% that we've found to be one of the biggest<00:03:50.450> pain<00:03:50.720> points<00:03:51.170> is<00:03:51.350> just<00:03:51.410> the<00:03:51.890> amount 00:03:52.180 --> 00:03:52.190 align:start position:0% biggest pain points is just the amount 00:03:52.190 --> 00:03:53.830 align:start position:0% biggest pain points is just the amount of<00:03:52.280> time<00:03:52.520> that<00:03:52.550> it<00:03:52.850> takes<00:03:53.030> to<00:03:53.270> sink<00:03:53.510> from<00:03:53.750> a 00:03:53.830 --> 00:03:53.840 align:start position:0% of time that it takes to sink from a 00:03:53.840 --> 00:03:56.920 align:start position:0% of time that it takes to sink from a fresh<00:03:54.050> start<00:03:54.350> you<00:03:54.590> know<00:03:54.890> these<00:03:55.930> sophisticated 00:03:56.920 --> 00:03:56.930 align:start position:0% fresh start you know these sophisticated 00:03:56.930 --> 00:03:58.390 align:start position:0% fresh start you know these sophisticated users<00:03:57.260> who<00:03:57.470> are<00:03:57.530> willing<00:03:57.950> to<00:03:58.100> try<00:03:58.370> something 00:03:58.390 --> 00:03:58.400 align:start position:0% users who are willing to try something 00:03:58.400 --> 00:03:59.940 align:start position:0% users who are willing to try something out<00:03:58.760> there<00:03:58.910> hobbyist<00:03:59.270> they<00:03:59.360> like<00:03:59.540> to<00:03:59.690> tinker 00:03:59.940 --> 00:03:59.950 align:start position:0% out there hobbyist they like to tinker 00:03:59.950 --> 00:04:03.280 align:start position:0% out there hobbyist they like to tinker but<00:04:00.950> they'll<00:04:01.190> start<00:04:01.580> up<00:04:01.820> a<00:04:02.000> node<00:04:02.330> and<00:04:02.720> try<00:04:03.230> to 00:04:03.280 --> 00:04:03.290 align:start position:0% but they'll start up a node and try to 00:04:03.290 --> 00:04:06.220 align:start position:0% but they'll start up a node and try to sink<00:04:03.620> it<00:04:03.770> and<00:04:04.040> two<00:04:04.850> hours<00:04:05.209> later<00:04:05.300> have<00:04:05.870> no 00:04:06.220 --> 00:04:06.230 align:start position:0% sink it and two hours later have no 00:04:06.230 --> 00:04:08.470 align:start position:0% sink it and two hours later have no indication<00:04:06.830> about<00:04:06.920> how<00:04:07.070> far<00:04:07.790> they<00:04:08.030> are<00:04:08.150> into 00:04:08.470 --> 00:04:08.480 align:start position:0% indication about how far they are into 00:04:08.480 --> 00:04:11.530 align:start position:0% indication about how far they are into that<00:04:08.570> sink<00:04:08.930> and<00:04:09.310> say<00:04:10.310> screw<00:04:10.610> it<00:04:10.730> flip<00:04:11.270> it<00:04:11.390> off 00:04:11.530 --> 00:04:11.540 align:start position:0% that sink and say screw it flip it off 00:04:11.540 --> 00:04:13.930 align:start position:0% that sink and say screw it flip it off and<00:04:11.840> go<00:04:12.380> do<00:04:12.560> something<00:04:12.590> else<00:04:13.010> that's<00:04:13.340> more<00:04:13.640> fun 00:04:13.930 --> 00:04:13.940 align:start position:0% and go do something else that's more fun 00:04:13.940 --> 00:04:17.530 align:start position:0% and go do something else that's more fun to<00:04:14.060> tinker<00:04:14.300> with<00:04:14.650> so<00:04:15.910> we<00:04:16.910> want<00:04:17.120> to<00:04:17.209> fix<00:04:17.330> that 00:04:17.530 --> 00:04:17.540 align:start position:0% to tinker with so we want to fix that 00:04:17.540 --> 00:04:20.740 align:start position:0% to tinker with so we want to fix that problem<00:04:17.770> the<00:04:18.770> the<00:04:19.640> reigning<00:04:20.090> speed<00:04:20.299> champion 00:04:20.740 --> 00:04:20.750 align:start position:0% problem the the reigning speed champion 00:04:20.750 --> 00:04:24.880 align:start position:0% problem the the reigning speed champion is<00:04:21.109> guess<00:04:21.680> fast<00:04:21.980> sink<00:04:22.280> that's<00:04:22.640> the<00:04:23.260> the<00:04:24.260> one<00:04:24.740> to 00:04:24.880 --> 00:04:24.890 align:start position:0% is guess fast sink that's the the one to 00:04:24.890 --> 00:04:27.190 align:start position:0% is guess fast sink that's the the one to beat<00:04:25.040> that's<00:04:25.430> about<00:04:25.669> four<00:04:26.090> hours<00:04:26.300> according 00:04:27.190 --> 00:04:27.200 align:start position:0% beat that's about four hours according 00:04:27.200 --> 00:04:31.390 align:start position:0% beat that's about four hours according to<00:04:27.440> their<00:04:27.590> latest<00:04:28.010> benchmarks<00:04:29.530> so<00:04:30.530> you<00:04:31.310> know 00:04:31.390 --> 00:04:31.400 align:start position:0% to their latest benchmarks so you know 00:04:31.400 --> 00:04:32.120 align:start position:0% to their latest benchmarks so you know even 00:04:32.120 --> 00:04:32.130 align:start position:0% even 00:04:32.130 --> 00:04:36.440 align:start position:0% even is<00:04:32.310> gonna<00:04:32.730> be<00:04:33.060> a<00:04:33.660> problem<00:04:34.940> for<00:04:35.940> for<00:04:36.330> these 00:04:36.440 --> 00:04:36.450 align:start position:0% is gonna be a problem for for these 00:04:36.450 --> 00:04:39.230 align:start position:0% is gonna be a problem for for these users<00:04:36.690> and<00:04:37.170> so<00:04:37.890> we<00:04:38.190> want<00:04:38.370> to<00:04:38.460> take<00:04:38.940> a<00:04:38.970> look<00:04:39.150> at 00:04:39.230 --> 00:04:39.240 align:start position:0% users and so we want to take a look at 00:04:39.240 --> 00:04:41.110 align:start position:0% users and so we want to take a look at that<00:04:39.330> and<00:04:39.510> see<00:04:39.660> how<00:04:39.930> much<00:04:40.050> better<00:04:40.110> can<00:04:40.590> we<00:04:40.650> do 00:04:41.110 --> 00:04:41.120 align:start position:0% that and see how much better can we do 00:04:41.120 --> 00:04:43.640 align:start position:0% that and see how much better can we do and<00:04:42.120> part<00:04:42.840> of<00:04:42.900> the<00:04:42.990> reason<00:04:43.200> we're<00:04:43.320> asking<00:04:43.590> that 00:04:43.640 --> 00:04:43.650 align:start position:0% and part of the reason we're asking that 00:04:43.650 --> 00:04:46.580 align:start position:0% and part of the reason we're asking that question<00:04:43.860> is<00:04:44.460> if<00:04:44.760> we<00:04:45.330> directly<00:04:45.810> implement 00:04:46.580 --> 00:04:46.590 align:start position:0% question is if we directly implement 00:04:46.590 --> 00:04:48.680 align:start position:0% question is if we directly implement fast<00:04:46.860> sync<00:04:47.130> we're<00:04:47.640> gonna<00:04:47.760> do<00:04:47.940> a<00:04:48.180> lot<00:04:48.480> worse 00:04:48.680 --> 00:04:48.690 align:start position:0% fast sync we're gonna do a lot worse 00:04:48.690 --> 00:04:51.590 align:start position:0% fast sync we're gonna do a lot worse because<00:04:49.110> python<00:04:49.770> is<00:04:49.950> never<00:04:50.220> gonna<00:04:50.430> match<00:04:51.060> or 00:04:51.590 --> 00:04:51.600 align:start position:0% because python is never gonna match or 00:04:51.600 --> 00:04:53.570 align:start position:0% because python is never gonna match or beat<00:04:51.810> go<00:04:52.380> and<00:04:52.590> a<00:04:52.620> head-to-head<00:04:52.950> performance 00:04:53.570 --> 00:04:53.580 align:start position:0% beat go and a head-to-head performance 00:04:53.580 --> 00:04:59.150 align:start position:0% beat go and a head-to-head performance race<00:04:54.140> so<00:04:56.000> we<00:04:57.000> zoom<00:04:57.600> in<00:04:57.750> too<00:04:57.930> fast<00:04:58.200> sync<00:04:58.500> and<00:04:58.800> we 00:04:59.150 --> 00:04:59.160 align:start position:0% race so we zoom in too fast sync and we 00:04:59.160 --> 00:05:02.300 align:start position:0% race so we zoom in too fast sync and we say<00:04:59.600> we<00:05:00.600> look<00:05:00.810> at<00:05:00.990> what<00:05:01.230> parts<00:05:01.590> are<00:05:01.830> taking 00:05:02.300 --> 00:05:02.310 align:start position:0% say we look at what parts are taking 00:05:02.310 --> 00:05:05.120 align:start position:0% say we look at what parts are taking most<00:05:02.460> of<00:05:02.580> the<00:05:02.640> time<00:05:02.850> and<00:05:03.180> the<00:05:04.100> majority<00:05:05.100> of 00:05:05.120 --> 00:05:05.130 align:start position:0% most of the time and the majority of 00:05:05.130 --> 00:05:08.180 align:start position:0% most of the time and the majority of that<00:05:05.370> is<00:05:05.990> downloading<00:05:06.990> state<00:05:07.290> ok<00:05:07.950> there's 00:05:08.180 --> 00:05:08.190 align:start position:0% that is downloading state ok there's 00:05:08.190 --> 00:05:09.620 align:start position:0% that is downloading state ok there's things<00:05:08.580> like<00:05:08.670> downloading<00:05:09.000> the<00:05:09.390> headers 00:05:09.620 --> 00:05:09.630 align:start position:0% things like downloading the headers 00:05:09.630 --> 00:05:12.800 align:start position:0% things like downloading the headers downloading<00:05:10.430> receipts<00:05:11.430> but<00:05:12.090> downloading<00:05:12.660> the 00:05:12.800 --> 00:05:12.810 align:start position:0% downloading receipts but downloading the 00:05:12.810 --> 00:05:15.110 align:start position:0% downloading receipts but downloading the state<00:05:13.380> of<00:05:13.620> a<00:05:13.860> recent<00:05:14.220> block<00:05:14.460> which<00:05:14.730> includes 00:05:15.110 --> 00:05:15.120 align:start position:0% state of a recent block which includes 00:05:15.120 --> 00:05:18.290 align:start position:0% state of a recent block which includes all<00:05:15.240> the<00:05:15.390> things<00:05:15.570> like<00:05:15.690> accounts<00:05:16.380> and<00:05:17.300> storage 00:05:18.290 --> 00:05:18.300 align:start position:0% all the things like accounts and storage 00:05:18.300 --> 00:05:20.840 align:start position:0% all the things like accounts and storage for<00:05:18.570> contracts<00:05:19.170> that's<00:05:19.530> the<00:05:19.950> vast<00:05:20.610> majority 00:05:20.840 --> 00:05:20.850 align:start position:0% for contracts that's the vast majority 00:05:20.850 --> 00:05:24.050 align:start position:0% for contracts that's the vast majority so<00:05:21.750> what<00:05:21.900> are<00:05:21.960> we<00:05:22.050> gonna<00:05:22.110> do<00:05:22.670> it's<00:05:23.670> time<00:05:23.880> to 00:05:24.050 --> 00:05:24.060 align:start position:0% so what are we gonna do it's time to 00:05:24.060 --> 00:05:27.860 align:start position:0% so what are we gonna do it's time to upgrade<00:05:24.500> our<00:05:25.500> sync<00:05:25.830> process<00:05:26.010> so<00:05:26.730> this<00:05:27.240> next 00:05:27.860 --> 00:05:27.870 align:start position:0% upgrade our sync process so this next 00:05:27.870 --> 00:05:30.020 align:start position:0% upgrade our sync process so this next generation<00:05:28.410> of<00:05:28.530> sync<00:05:28.770> we're<00:05:28.890> calling<00:05:29.310> beam 00:05:30.020 --> 00:05:30.030 align:start position:0% generation of sync we're calling beam 00:05:30.030 --> 00:05:35.180 align:start position:0% generation of sync we're calling beam sync<00:05:30.300> and<00:05:31.610> the<00:05:33.020> the<00:05:34.020> ability<00:05:34.320> it<00:05:34.650> gives<00:05:34.830> us<00:05:35.010> is 00:05:35.180 --> 00:05:35.190 align:start position:0% sync and the the ability it gives us is 00:05:35.190 --> 00:05:39.280 align:start position:0% sync and the the ability it gives us is go<00:05:35.610> from<00:05:35.970> an<00:05:36.240> empty<00:05:36.780> node<00:05:37.460> no<00:05:38.460> data<00:05:38.730> to 00:05:39.280 --> 00:05:39.290 align:start position:0% go from an empty node no data to 00:05:39.290 --> 00:05:41.900 align:start position:0% go from an empty node no data to executing<00:05:40.290> a<00:05:40.410> recent<00:05:40.830> main<00:05:41.070> net<00:05:41.280> block<00:05:41.550> in 00:05:41.900 --> 00:05:41.910 align:start position:0% executing a recent main net block in 00:05:41.910 --> 00:05:46.370 align:start position:0% executing a recent main net block in minutes<00:05:42.840> asterisk<00:05:43.790> with<00:05:44.790> just<00:05:45.390> in<00:05:45.660> time<00:05:45.870> state 00:05:46.370 --> 00:05:46.380 align:start position:0% minutes asterisk with just in time state 00:05:46.380 --> 00:05:50.120 align:start position:0% minutes asterisk with just in time state downloads<00:05:46.800> that's<00:05:47.370> the<00:05:48.380> main<00:05:49.380> concept<00:05:50.010> behind 00:05:50.120 --> 00:05:50.130 align:start position:0% downloads that's the main concept behind 00:05:50.130 --> 00:05:53.600 align:start position:0% downloads that's the main concept behind it<00:05:50.400> so<00:05:51.530> asterisk<00:05:52.530> I<00:05:52.860> don't<00:05:53.250> want<00:05:53.400> to<00:05:53.460> lie<00:05:53.580> to 00:05:53.600 --> 00:05:53.610 align:start position:0% it so asterisk I don't want to lie to 00:05:53.610 --> 00:05:56.120 align:start position:0% it so asterisk I don't want to lie to you<00:05:53.810> it<00:05:54.810> takes<00:05:55.110> longer<00:05:55.470> than<00:05:55.500> that<00:05:55.770> right<00:05:55.920> now 00:05:56.120 --> 00:05:56.130 align:start position:0% you it takes longer than that right now 00:05:56.130 --> 00:05:58.100 align:start position:0% you it takes longer than that right now because<00:05:56.580> you<00:05:56.910> have<00:05:57.060> to<00:05:57.180> find<00:05:57.360> peers<00:05:57.810> and 00:05:58.100 --> 00:05:58.110 align:start position:0% because you have to find peers and 00:05:58.110 --> 00:06:00.860 align:start position:0% because you have to find peers and that's<00:05:59.090> unreasonably<00:06:00.090> difficult<00:06:00.300> right<00:06:00.720> now 00:06:00.860 --> 00:06:00.870 align:start position:0% that's unreasonably difficult right now 00:06:00.870 --> 00:06:03.320 align:start position:0% that's unreasonably difficult right now and<00:06:01.310> header<00:06:02.310> imports<00:06:02.700> can<00:06:02.880> take<00:06:03.060> a<00:06:03.090> while 00:06:03.320 --> 00:06:03.330 align:start position:0% and header imports can take a while 00:06:03.330 --> 00:06:05.750 align:start position:0% and header imports can take a while unless<00:06:03.780> you<00:06:04.230> use<00:06:04.350> a<00:06:04.380> checkpoint<00:06:05.160> which<00:06:05.610> has 00:06:05.750 --> 00:06:05.760 align:start position:0% unless you use a checkpoint which has 00:06:05.760 --> 00:06:09.130 align:start position:0% unless you use a checkpoint which has its<00:06:05.970> own<00:06:06.200> interesting<00:06:07.200> side<00:06:07.410> tracks<00:06:07.790> we<00:06:08.790> will 00:06:09.130 --> 00:06:09.140 align:start position:0% its own interesting side tracks we will 00:06:09.140 --> 00:06:11.870 align:start position:0% its own interesting side tracks we will get<00:06:10.140> back<00:06:10.290> to<00:06:10.470> those<00:06:10.590> things<00:06:10.830> but<00:06:11.130> we're<00:06:11.760> not 00:06:11.870 --> 00:06:11.880 align:start position:0% get back to those things but we're not 00:06:11.880 --> 00:06:13.220 align:start position:0% get back to those things but we're not we're<00:06:12.210> considering<00:06:12.480> that<00:06:12.690> out<00:06:12.780> of<00:06:12.900> scope<00:06:13.110> for 00:06:13.220 --> 00:06:13.230 align:start position:0% we're considering that out of scope for 00:06:13.230 --> 00:06:17.630 align:start position:0% we're considering that out of scope for beam<00:06:13.710> synchrony<00:06:15.200> so<00:06:16.200> high<00:06:17.100> level 00:06:17.630 --> 00:06:17.640 align:start position:0% beam synchrony so high level 00:06:17.640 --> 00:06:21.350 align:start position:0% beam synchrony so high level how<00:06:18.030> does<00:06:18.570> beam<00:06:18.900> sync<00:06:19.170> work<00:06:20.180> roughly<00:06:21.180> we 00:06:21.350 --> 00:06:21.360 align:start position:0% how does beam sync work roughly we 00:06:21.360 --> 00:06:23.300 align:start position:0% how does beam sync work roughly we combine<00:06:21.810> the<00:06:22.020> ideas<00:06:22.380> of<00:06:22.710> the<00:06:22.830> way<00:06:22.920> that<00:06:23.100> fast 00:06:23.300 --> 00:06:23.310 align:start position:0% combine the ideas of the way that fast 00:06:23.310 --> 00:06:25.820 align:start position:0% combine the ideas of the way that fast sync<00:06:23.550> works<00:06:23.760> and<00:06:24.090> the<00:06:24.630> way<00:06:24.750> that<00:06:25.110> stateless 00:06:25.820 --> 00:06:25.830 align:start position:0% sync works and the way that stateless 00:06:25.830 --> 00:06:27.890 align:start position:0% sync works and the way that stateless clients<00:06:26.220> work<00:06:26.370> so<00:06:26.730> stateless<00:06:27.330> client<00:06:27.690> gets 00:06:27.890 --> 00:06:27.900 align:start position:0% clients work so stateless client gets 00:06:27.900 --> 00:06:29.810 align:start position:0% clients work so stateless client gets all<00:06:28.080> the<00:06:28.200> data<00:06:28.350> I<00:06:28.620> mean<00:06:28.830> just<00:06:29.250> the<00:06:29.400> data<00:06:29.610> it 00:06:29.810 --> 00:06:29.820 align:start position:0% all the data I mean just the data it 00:06:29.820 --> 00:06:34.310 align:start position:0% all the data I mean just the data it means<00:06:30.000> to<00:06:30.330> run<00:06:30.630> and<00:06:30.780> block<00:06:30.930> and<00:06:31.550> it<00:06:33.170> dumps<00:06:34.170> it 00:06:34.310 --> 00:06:34.320 align:start position:0% means to run and block and it dumps it 00:06:34.320 --> 00:06:36.590 align:start position:0% means to run and block and it dumps it at<00:06:34.500> the<00:06:34.650> end<00:06:34.770> of<00:06:34.890> the<00:06:34.950> block<00:06:35.210> fast<00:06:36.210> sync<00:06:36.450> is 00:06:36.590 --> 00:06:36.600 align:start position:0% at the end of the block fast sync is 00:06:36.600 --> 00:06:39.350 align:start position:0% at the end of the block fast sync is about<00:06:36.810> getting<00:06:37.140> all<00:06:37.410> of<00:06:37.770> the<00:06:37.890> data<00:06:38.100> all<00:06:38.760> up 00:06:39.350 --> 00:06:39.360 align:start position:0% about getting all of the data all up 00:06:39.360 --> 00:06:42.290 align:start position:0% about getting all of the data all up front<00:06:39.600> and<00:06:39.810> save<00:06:40.110> it<00:06:40.229> to<00:06:40.320> disk<00:06:40.470> so<00:06:41.300> instead 00:06:42.290 --> 00:06:42.300 align:start position:0% front and save it to disk so instead 00:06:42.300 --> 00:06:44.629 align:start position:0% front and save it to disk so instead beam<00:06:42.780> sync<00:06:43.080> works<00:06:43.260> by<00:06:43.620> running 00:06:44.629 --> 00:06:44.639 align:start position:0% beam sync works by running 00:06:44.639 --> 00:06:47.450 align:start position:0% beam sync works by running a<00:06:44.669> VM<00:06:44.969> on<00:06:45.150> an<00:06:45.330> empty<00:06:45.599> state<00:06:46.129> pulling<00:06:47.129> the<00:06:47.249> data 00:06:47.450 --> 00:06:47.460 align:start position:0% a VM on an empty state pulling the data 00:06:47.460 --> 00:06:50.089 align:start position:0% a VM on an empty state pulling the data as<00:06:47.669> it's<00:06:47.939> needed<00:06:48.090> but<00:06:48.659> saving<00:06:48.960> it<00:06:49.259> and<00:06:49.379> storing 00:06:50.089 --> 00:06:50.099 align:start position:0% as it's needed but saving it and storing 00:06:50.099 --> 00:06:54.499 align:start position:0% as it's needed but saving it and storing it<00:06:50.249> for<00:06:50.699> future<00:06:51.569> executions<00:06:52.729> so<00:06:53.729> what<00:06:54.300> kind<00:06:54.479> of 00:06:54.499 --> 00:06:54.509 align:start position:0% it for future executions so what kind of 00:06:54.509 --> 00:06:56.239 align:start position:0% it for future executions so what kind of effect<00:06:54.840> does<00:06:54.960> that<00:06:54.990> have<00:06:55.110> well<00:06:55.439> there<00:06:55.979> are 00:06:56.239 --> 00:06:56.249 align:start position:0% effect does that have well there are 00:06:56.249 --> 00:07:01.369 align:start position:0% effect does that have well there are about<00:06:57.289> 375<00:06:58.289> million<00:06:59.150> try<00:07:00.150> notes<00:07:00.360> in<00:07:00.659> the<00:07:01.110> main 00:07:01.369 --> 00:07:01.379 align:start position:0% about 375 million try notes in the main 00:07:01.379 --> 00:07:04.189 align:start position:0% about 375 million try notes in the main that<00:07:01.529> state<00:07:01.800> database<00:07:02.460> and<00:07:02.990> there<00:07:03.990> are 00:07:04.189 --> 00:07:04.199 align:start position:0% that state database and there are 00:07:04.199 --> 00:07:07.719 align:start position:0% that state database and there are roughly<00:07:05.069> three<00:07:05.729> to<00:07:05.909> four<00:07:06.150> thousand<00:07:06.749> try<00:07:07.409> nodes 00:07:07.719 --> 00:07:07.729 align:start position:0% roughly three to four thousand try nodes 00:07:07.729 --> 00:07:10.700 align:start position:0% roughly three to four thousand try nodes that<00:07:08.729> are<00:07:08.849> used<00:07:09.120> per<00:07:09.479> block<00:07:09.749> so<00:07:10.409> that's<00:07:10.620> about 00:07:10.700 --> 00:07:10.710 align:start position:0% that are used per block so that's about 00:07:10.710 --> 00:07:12.980 align:start position:0% that are used per block so that's about one<00:07:11.099> one<00:07:11.340> hundred<00:07:11.729> thousandth<00:07:12.210> of<00:07:12.389> the<00:07:12.479> amount 00:07:12.980 --> 00:07:12.990 align:start position:0% one one hundred thousandth of the amount 00:07:12.990 --> 00:07:14.570 align:start position:0% one one hundred thousandth of the amount of<00:07:13.080> data<00:07:13.259> you<00:07:13.409> need<00:07:13.680> for<00:07:13.710> just<00:07:14.159> one<00:07:14.340> block 00:07:14.570 --> 00:07:14.580 align:start position:0% of data you need for just one block 00:07:14.580 --> 00:07:17.260 align:start position:0% of data you need for just one block versus<00:07:15.120> for<00:07:15.419> everything<00:07:15.900> in<00:07:16.020> the<00:07:16.110> state<00:07:16.349> and 00:07:17.260 --> 00:07:17.270 align:start position:0% versus for everything in the state and 00:07:17.270 --> 00:07:20.420 align:start position:0% versus for everything in the state and this<00:07:18.270> works<00:07:18.479> out<00:07:18.599> to<00:07:18.750> about<00:07:18.870> 250<00:07:19.740> times<00:07:19.979> fewer 00:07:20.420 --> 00:07:20.430 align:start position:0% this works out to about 250 times fewer 00:07:20.430 --> 00:07:24.200 align:start position:0% this works out to about 250 times fewer requests<00:07:21.090> on<00:07:21.300> the<00:07:21.360> network<00:07:22.009> before<00:07:23.009> the<00:07:23.819> first 00:07:24.200 --> 00:07:24.210 align:start position:0% requests on the network before the first 00:07:24.210 --> 00:07:26.119 align:start position:0% requests on the network before the first block<00:07:24.449> can<00:07:24.659> run<00:07:24.870> and<00:07:25.110> we'll<00:07:25.740> get<00:07:25.860> into<00:07:26.009> those 00:07:26.119 --> 00:07:26.129 align:start position:0% block can run and we'll get into those 00:07:26.129 --> 00:07:30.320 align:start position:0% block can run and we'll get into those numbers<00:07:26.250> a<00:07:26.430> little<00:07:26.639> bit<00:07:26.789> more<00:07:27.029> later<00:07:27.979> so<00:07:29.330> we 00:07:30.320 --> 00:07:30.330 align:start position:0% numbers a little bit more later so we 00:07:30.330 --> 00:07:32.420 align:start position:0% numbers a little bit more later so we are<00:07:30.569> approaching<00:07:31.199> halfway<00:07:31.770> through<00:07:32.069> and 00:07:32.420 --> 00:07:32.430 align:start position:0% are approaching halfway through and 00:07:32.430 --> 00:07:35.679 align:start position:0% are approaching halfway through and obviously<00:07:33.000> only<00:07:33.539> great<00:07:34.050> blaze<00:07:34.590> raced<00:07:35.129> over 00:07:35.679 --> 00:07:35.689 align:start position:0% obviously only great blaze raced over 00:07:35.689 --> 00:07:40.610 align:start position:0% obviously only great blaze raced over beam<00:07:36.689> sync<00:07:37.490> so<00:07:38.490> I've<00:07:38.849> got<00:07:39.029> a<00:07:39.060> talk<00:07:39.330> or<00:07:39.629> a<00:07:39.900> post 00:07:40.610 --> 00:07:40.620 align:start position:0% beam sync so I've got a talk or a post 00:07:40.620 --> 00:07:44.510 align:start position:0% beam sync so I've got a talk or a post here<00:07:40.949> rather<00:07:41.189> on<00:07:42.060> medium<00:07:42.680> that<00:07:43.680> goes<00:07:44.219> into<00:07:44.490> a 00:07:44.510 --> 00:07:44.520 align:start position:0% here rather on medium that goes into a 00:07:44.520 --> 00:07:46.700 align:start position:0% here rather on medium that goes into a bit<00:07:44.759> more<00:07:44.789> detail<00:07:45.089> compares<00:07:45.810> it<00:07:45.960> to<00:07:45.990> fasting 00:07:46.700 --> 00:07:46.710 align:start position:0% bit more detail compares it to fasting 00:07:46.710 --> 00:07:47.779 align:start position:0% bit more detail compares it to fasting and<00:07:46.830> all<00:07:46.889> that<00:07:47.039> so<00:07:47.249> I'll<00:07:47.310> give<00:07:47.430> people<00:07:47.639> a 00:07:47.779 --> 00:07:47.789 align:start position:0% and all that so I'll give people a 00:07:47.789 --> 00:07:52.279 align:start position:0% and all that so I'll give people a second<00:07:48.360> to<00:07:48.599> grab<00:07:48.870> that<00:07:49.050> link<00:07:50.150> and<00:07:51.199> also<00:07:52.199> I'm 00:07:52.279 --> 00:07:52.289 align:start position:0% second to grab that link and also I'm 00:07:52.289 --> 00:07:56.320 align:start position:0% second to grab that link and also I'm gonna<00:07:52.379> be<00:07:52.560> posting<00:07:53.120> further<00:07:54.120> beam<00:07:55.050> sync 00:07:56.320 --> 00:07:56.330 align:start position:0% gonna be posting further beam sync 00:07:56.330 --> 00:07:59.420 align:start position:0% gonna be posting further beam sync updates<00:07:57.330> as<00:07:57.659> well<00:07:58.139> as<00:07:58.469> talking<00:07:58.860> about<00:07:59.099> how<00:07:59.279> it 00:07:59.420 --> 00:07:59.430 align:start position:0% updates as well as talking about how it 00:07:59.430 --> 00:08:01.339 align:start position:0% updates as well as talking about how it impacts<00:07:59.939> the<00:08:00.029> whole<00:08:00.149> network<00:08:00.360> over<00:08:00.839> time<00:08:00.870> so 00:08:01.339 --> 00:08:01.349 align:start position:0% impacts the whole network over time so 00:08:01.349 --> 00:08:03.649 align:start position:0% impacts the whole network over time so feel<00:08:02.250> free<00:08:02.279> to<00:08:02.460> follow<00:08:02.789> up<00:08:03.060> me<00:08:03.149> there<00:08:03.330> to<00:08:03.449> find 00:08:03.649 --> 00:08:03.659 align:start position:0% feel free to follow up me there to find 00:08:03.659 --> 00:08:06.409 align:start position:0% feel free to follow up me there to find out<00:08:03.779> more<00:08:04.159> and<00:08:05.159> while<00:08:05.819> people<00:08:06.000> are<00:08:06.149> getting 00:08:06.409 --> 00:08:06.419 align:start position:0% out more and while people are getting 00:08:06.419 --> 00:08:09.379 align:start position:0% out more and while people are getting their<00:08:06.539> last<00:08:06.719> shot<00:08:06.960> of<00:08:07.020> that<00:08:08.089> you<00:08:09.089> may<00:08:09.240> have 00:08:09.379 --> 00:08:09.389 align:start position:0% their last shot of that you may have 00:08:09.389 --> 00:08:11.089 align:start position:0% their last shot of that you may have noticed<00:08:09.779> kind<00:08:10.169> of<00:08:10.229> a<00:08:10.289> discrepancy<00:08:10.649> in<00:08:10.919> the 00:08:11.089 --> 00:08:11.099 align:start position:0% noticed kind of a discrepancy in the 00:08:11.099 --> 00:08:12.769 align:start position:0% noticed kind of a discrepancy in the numbers<00:08:11.460> on<00:08:11.580> the<00:08:11.639> last<00:08:11.819> slide<00:08:12.000> if<00:08:12.419> there's<00:08:12.629> a 00:08:12.769 --> 00:08:12.779 align:start position:0% numbers on the last slide if there's a 00:08:12.779 --> 00:08:14.600 align:start position:0% numbers on the last slide if there's a hundred<00:08:13.050> thousandth<00:08:13.500> of<00:08:13.710> the<00:08:13.770> data<00:08:14.069> then<00:08:14.399> why 00:08:14.600 --> 00:08:14.610 align:start position:0% hundred thousandth of the data then why 00:08:14.610 --> 00:08:18.519 align:start position:0% hundred thousandth of the data then why is<00:08:14.669> it<00:08:15.149> only<00:08:15.500> 250<00:08:16.500> times<00:08:16.649> fewer<00:08:17.069> requests 00:08:18.519 --> 00:08:18.529 align:start position:0% is it only 250 times fewer requests 00:08:18.529 --> 00:08:24.469 align:start position:0% is it only 250 times fewer requests excellent<00:08:19.529> question<00:08:19.949> so<00:08:22.580> fast<00:08:23.580> sync<00:08:23.969> gets<00:08:24.300> to 00:08:24.469 --> 00:08:24.479 align:start position:0% excellent question so fast sync gets to 00:08:24.479 --> 00:08:26.659 align:start position:0% excellent question so fast sync gets to batch<00:08:24.689> together<00:08:25.199> it's<00:08:25.649> try<00:08:25.979> node<00:08:26.159> requests 00:08:26.659 --> 00:08:26.669 align:start position:0% batch together it's try node requests 00:08:26.669 --> 00:08:33.319 align:start position:0% batch together it's try node requests into<00:08:27.889> 340<00:08:28.889> no<00:08:29.839> 384<00:08:30.839> nodes<00:08:31.379> per<00:08:31.710> request<00:08:32.329> so 00:08:33.319 --> 00:08:33.329 align:start position:0% into 340 no 384 nodes per request so 00:08:33.329 --> 00:08:36.290 align:start position:0% into 340 no 384 nodes per request so beam<00:08:33.599> sync<00:08:33.899> as<00:08:34.110> implemented<00:08:34.680> now<00:08:35.209> can<00:08:36.209> only 00:08:36.290 --> 00:08:36.300 align:start position:0% beam sync as implemented now can only 00:08:36.300 --> 00:08:38.810 align:start position:0% beam sync as implemented now can only request<00:08:36.690> a<00:08:36.899> single<00:08:37.320> node<00:08:37.500> per<00:08:38.070> request<00:08:38.490> and 00:08:38.810 --> 00:08:38.820 align:start position:0% request a single node per request and 00:08:38.820 --> 00:08:41.719 align:start position:0% request a single node per request and because<00:08:39.750> the<00:08:40.289> latency<00:08:40.589> the<00:08:40.949> actual<00:08:41.219> time<00:08:41.459> that 00:08:41.719 --> 00:08:41.729 align:start position:0% because the latency the actual time that 00:08:41.729 --> 00:08:43.909 align:start position:0% because the latency the actual time that the<00:08:41.789> packet<00:08:42.180> is<00:08:42.409> round-tripping<00:08:43.409> between<00:08:43.769> you 00:08:43.909 --> 00:08:43.919 align:start position:0% the packet is round-tripping between you 00:08:43.919 --> 00:08:46.160 align:start position:0% the packet is round-tripping between you and<00:08:44.070> your<00:08:44.159> peer<00:08:44.399> makes<00:08:45.000> up<00:08:45.209> the<00:08:45.690> majority<00:08:45.810> of 00:08:46.160 --> 00:08:46.170 align:start position:0% and your peer makes up the majority of 00:08:46.170 --> 00:08:52.220 align:start position:0% and your peer makes up the majority of the<00:08:46.260> time<00:08:46.529> you<00:08:47.220> lose<00:08:47.850> a<00:08:47.910> factor<00:08:48.420> of<00:08:48.449> 384<00:08:51.199> okay 00:08:52.220 --> 00:08:52.230 align:start position:0% the time you lose a factor of 384 okay 00:08:52.230 --> 00:08:55.699 align:start position:0% the time you lose a factor of 384 okay so<00:08:53.480> we're<00:08:54.480> about<00:08:54.630> to<00:08:54.750> do<00:08:54.930> a<00:08:54.959> deep<00:08:55.170> dive<00:08:55.199> I'm 00:08:55.699 --> 00:08:55.709 align:start position:0% so we're about to do a deep dive I'm 00:08:55.709 --> 00:08:57.750 align:start position:0% so we're about to do a deep dive I'm sorry<00:08:56.310> for<00:08:56.610> the<00:08:56.760> folks<00:08:57.000> that 00:08:57.750 --> 00:08:57.760 align:start position:0% sorry for the folks that 00:08:57.760 --> 00:09:00.720 align:start position:0% sorry for the folks that I<00:08:57.790> might<00:08:57.970> lose<00:08:58.920> it<00:08:59.920> requires<00:09:00.279> a<00:09:00.370> little<00:09:00.519> bit<00:09:00.639> of 00:09:00.720 --> 00:09:00.730 align:start position:0% I might lose it requires a little bit of 00:09:00.730 --> 00:09:02.790 align:start position:0% I might lose it requires a little bit of understanding<00:09:01.060> about<00:09:01.240> EVM<00:09:01.720> and<00:09:02.139> the<00:09:02.500> way<00:09:02.620> that 00:09:02.790 --> 00:09:02.800 align:start position:0% understanding about EVM and the way that 00:09:02.800 --> 00:09:05.370 align:start position:0% understanding about EVM and the way that that<00:09:03.190> tries<00:09:03.550> work<00:09:03.880> I'm<00:09:04.449> not<00:09:04.720> gonna<00:09:04.870> have<00:09:05.199> time 00:09:05.370 --> 00:09:05.380 align:start position:0% that tries work I'm not gonna have time 00:09:05.380 --> 00:09:08.850 align:start position:0% that tries work I'm not gonna have time to<00:09:05.500> get<00:09:05.620> back<00:09:05.680> out<00:09:05.980> on<00:09:06.040> it<00:09:06.720> so<00:09:07.720> I'm<00:09:08.019> sorry<00:09:08.199> for 00:09:08.850 --> 00:09:08.860 align:start position:0% to get back out on it so I'm sorry for 00:09:08.860 --> 00:09:12.660 align:start position:0% to get back out on it so I'm sorry for everyone<00:09:09.100> else<00:09:09.250> I<00:09:09.670> hope<00:09:10.209> you<00:09:10.329> have<00:09:10.420> fun<00:09:11.670> so 00:09:12.660 --> 00:09:12.670 align:start position:0% everyone else I hope you have fun so 00:09:12.670 --> 00:09:14.430 align:start position:0% everyone else I hope you have fun so what<00:09:13.269> I'm<00:09:13.360> gonna<00:09:13.480> do<00:09:13.720> here<00:09:13.990> is<00:09:14.050> I'm<00:09:14.170> going<00:09:14.380> to 00:09:14.430 --> 00:09:14.440 align:start position:0% what I'm gonna do here is I'm going to 00:09:14.440 --> 00:09:16.980 align:start position:0% what I'm gonna do here is I'm going to paint<00:09:15.310> a<00:09:15.550> big<00:09:15.790> picture<00:09:16.149> of<00:09:16.300> kind<00:09:16.660> of<00:09:16.720> how<00:09:16.870> it 00:09:16.980 --> 00:09:16.990 align:start position:0% paint a big picture of kind of how it 00:09:16.990 --> 00:09:18.720 align:start position:0% paint a big picture of kind of how it works<00:09:17.199> but<00:09:17.410> I'm<00:09:17.529> gonna<00:09:17.649> put<00:09:17.949> it<00:09:18.070> on<00:09:18.370> the<00:09:18.550> slide 00:09:18.720 --> 00:09:18.730 align:start position:0% works but I'm gonna put it on the slide 00:09:18.730 --> 00:09:23.069 align:start position:0% works but I'm gonna put it on the slide bit<00:09:19.029> by<00:09:19.209> bit<00:09:19.240> so<00:09:20.230> that<00:09:20.880> we<00:09:21.880> can<00:09:22.060> kind<00:09:22.389> of<00:09:22.540> stitch 00:09:23.069 --> 00:09:23.079 align:start position:0% bit by bit so that we can kind of stitch 00:09:23.079 --> 00:09:25.650 align:start position:0% bit by bit so that we can kind of stitch it<00:09:23.260> together<00:09:23.410> the<00:09:24.010> understanding<00:09:24.880> so<00:09:25.300> the 00:09:25.650 --> 00:09:25.660 align:start position:0% it together the understanding so the 00:09:25.660 --> 00:09:30.180 align:start position:0% it together the understanding so the idea<00:09:25.959> here<00:09:26.320> is<00:09:27.300> we're<00:09:28.300> going<00:09:28.510> to<00:09:28.660> jump<00:09:29.139> into<00:09:29.410> a 00:09:30.180 --> 00:09:30.190 align:start position:0% idea here is we're going to jump into a 00:09:30.190 --> 00:09:33.269 align:start position:0% idea here is we're going to jump into a VM<00:09:30.760> code<00:09:31.029> execution<00:09:31.480> this<00:09:32.350> isn't<00:09:32.680> the<00:09:32.740> way<00:09:32.860> it 00:09:33.269 --> 00:09:33.279 align:start position:0% VM code execution this isn't the way it 00:09:33.279 --> 00:09:36.750 align:start position:0% VM code execution this isn't the way it really<00:09:33.579> works<00:09:34.199> but<00:09:35.199> it<00:09:35.500> it<00:09:35.920> gets<00:09:36.459> the<00:09:36.610> point 00:09:36.750 --> 00:09:36.760 align:start position:0% really works but it it gets the point 00:09:36.760 --> 00:09:41.069 align:start position:0% really works but it it gets the point across<00:09:36.880> so<00:09:37.980> let's<00:09:38.980> say<00:09:39.250> we<00:09:39.459> have<00:09:39.730> a<00:09:40.089> push<00:09:40.750> 20 00:09:41.069 --> 00:09:41.079 align:start position:0% across so let's say we have a push 20 00:09:41.079 --> 00:09:43.769 align:start position:0% across so let's say we have a push 20 opcode<00:09:41.500> we're<00:09:42.160> gonna<00:09:42.279> push<00:09:42.610> an<00:09:42.880> address<00:09:43.389> onto 00:09:43.769 --> 00:09:43.779 align:start position:0% opcode we're gonna push an address onto 00:09:43.779 --> 00:09:46.889 align:start position:0% opcode we're gonna push an address onto the<00:09:43.870> stack<00:09:44.110> that<00:09:45.149> doesn't<00:09:46.149> take<00:09:46.389> that<00:09:46.690> didn't 00:09:46.889 --> 00:09:46.899 align:start position:0% the stack that doesn't take that didn't 00:09:46.899 --> 00:09:48.870 align:start position:0% the stack that doesn't take that didn't require<00:09:47.019> any<00:09:47.199> state<00:09:47.709> that<00:09:47.949> was<00:09:48.070> just<00:09:48.310> in<00:09:48.610> the 00:09:48.870 --> 00:09:48.880 align:start position:0% require any state that was just in the 00:09:48.880 --> 00:09:51.420 align:start position:0% require any state that was just in the the<00:09:49.660> byte<00:09:49.839> code<00:09:49.870> so<00:09:50.500> even<00:09:50.980> though<00:09:51.100> our<00:09:51.130> state 00:09:51.420 --> 00:09:51.430 align:start position:0% the byte code so even though our state 00:09:51.430 --> 00:09:53.850 align:start position:0% the byte code so even though our state database<00:09:51.790> is<00:09:51.970> empty<00:09:52.139> we<00:09:53.139> can<00:09:53.170> continue<00:09:53.709> on 00:09:53.850 --> 00:09:53.860 align:start position:0% database is empty we can continue on 00:09:53.860 --> 00:09:56.819 align:start position:0% database is empty we can continue on okay<00:09:54.850> but<00:09:55.120> the<00:09:55.240> next<00:09:55.540> opcode<00:09:56.019> asks<00:09:56.589> for<00:09:56.709> the 00:09:56.819 --> 00:09:56.829 align:start position:0% okay but the next opcode asks for the 00:09:56.829 --> 00:09:59.819 align:start position:0% okay but the next opcode asks for the balance<00:09:57.160> of<00:09:57.279> that<00:09:57.430> address<00:09:57.790> so<00:09:58.540> now<00:09:58.750> the<00:09:59.560> VM 00:09:59.819 --> 00:09:59.829 align:start position:0% balance of that address so now the VM 00:09:59.829 --> 00:10:02.069 align:start position:0% balance of that address so now the VM has<00:09:59.980> to<00:10:00.130> check<00:10:00.370> the<00:10:00.970> state<00:10:01.300> database<00:10:01.660> which<00:10:01.899> is 00:10:02.069 --> 00:10:02.079 align:start position:0% has to check the state database which is 00:10:02.079 --> 00:10:06.480 align:start position:0% has to check the state database which is empty<00:10:02.410> and<00:10:04.170> and<00:10:05.170> try<00:10:05.680> to<00:10:05.740> extract<00:10:06.160> that 00:10:06.480 --> 00:10:06.490 align:start position:0% empty and and try to extract that 00:10:06.490 --> 00:10:08.819 align:start position:0% empty and and try to extract that balance<00:10:06.790> now<00:10:07.389> all<00:10:07.660> we<00:10:07.810> know<00:10:08.019> at<00:10:08.380> this<00:10:08.440> point 00:10:08.819 --> 00:10:08.829 align:start position:0% balance now all we know at this point 00:10:08.829 --> 00:10:10.680 align:start position:0% balance now all we know at this point all<00:10:08.949> the<00:10:08.980> node<00:10:09.279> knows<00:10:09.550> at<00:10:09.670> this<00:10:09.760> point<00:10:09.850> is<00:10:10.240> the 00:10:10.680 --> 00:10:10.690 align:start position:0% all the node knows at this point is the 00:10:10.690 --> 00:10:14.250 align:start position:0% all the node knows at this point is the hash<00:10:11.170> of<00:10:11.589> the<00:10:11.889> root<00:10:12.069> of<00:10:12.250> the<00:10:12.670> Tri<00:10:12.910> so<00:10:13.600> that<00:10:13.870> is 00:10:14.250 --> 00:10:14.260 align:start position:0% hash of the root of the Tri so that is 00:10:14.260 --> 00:10:19.280 align:start position:0% hash of the root of the Tri so that is we're<00:10:15.250> gonna<00:10:15.370> call<00:10:15.579> that<00:10:15.730> F<00:10:15.910> here<00:10:16.300> a<00:10:16.410> dot<00:10:17.410> and 00:10:19.280 --> 00:10:19.290 align:start position:0% we're gonna call that F here a dot and 00:10:19.290 --> 00:10:21.509 align:start position:0% we're gonna call that F here a dot and that's<00:10:20.290> that's<00:10:20.680> all<00:10:20.860> we've<00:10:21.010> got 00:10:21.509 --> 00:10:21.519 align:start position:0% that's that's all we've got 00:10:21.519 --> 00:10:23.430 align:start position:0% that's that's all we've got so<00:10:22.060> what<00:10:22.510> are<00:10:22.569> we<00:10:22.630> gonna<00:10:22.779> do<00:10:22.959> how<00:10:23.139> are<00:10:23.170> we<00:10:23.319> gonna 00:10:23.430 --> 00:10:23.440 align:start position:0% so what are we gonna do how are we gonna 00:10:23.440 --> 00:10:24.870 align:start position:0% so what are we gonna do how are we gonna get<00:10:23.529> the<00:10:23.620> balance<00:10:23.860> we're<00:10:24.399> gonna<00:10:24.519> find<00:10:24.760> a 00:10:24.870 --> 00:10:24.880 align:start position:0% get the balance we're gonna find a 00:10:24.880 --> 00:10:29.550 align:start position:0% get the balance we're gonna find a friendly<00:10:25.120> Pierre<00:10:25.649> and<00:10:27.329> we'll<00:10:28.329> ask<00:10:28.480> it<00:10:28.720> hey 00:10:29.550 --> 00:10:29.560 align:start position:0% friendly Pierre and we'll ask it hey 00:10:29.560 --> 00:10:31.620 align:start position:0% friendly Pierre and we'll ask it hey Pierre<00:10:29.920> do<00:10:30.250> you<00:10:30.339> know<00:10:30.519> what<00:10:30.850> the<00:10:30.970> node<00:10:31.209> is<00:10:31.389> that 00:10:31.620 --> 00:10:31.630 align:start position:0% Pierre do you know what the node is that 00:10:31.630 --> 00:10:34.680 align:start position:0% Pierre do you know what the node is that has<00:10:31.779> the<00:10:31.959> hash<00:10:32.139> chef<00:10:32.410> this<00:10:33.370> command<00:10:33.790> is<00:10:34.029> the 00:10:34.680 --> 00:10:34.690 align:start position:0% has the hash chef this command is the 00:10:34.690 --> 00:10:37.500 align:start position:0% has the hash chef this command is the exact<00:10:35.050> same<00:10:35.230> command<00:10:35.709> that<00:10:36.069> fast<00:10:36.910> Inc<00:10:37.149> uses 00:10:37.500 --> 00:10:37.510 align:start position:0% exact same command that fast Inc uses 00:10:37.510 --> 00:10:40.019 align:start position:0% exact same command that fast Inc uses right<00:10:37.899> so<00:10:38.170> we're<00:10:39.010> picking<00:10:39.220> backing<00:10:39.730> on<00:10:39.850> this 00:10:40.019 --> 00:10:40.029 align:start position:0% right so we're picking backing on this 00:10:40.029 --> 00:10:42.120 align:start position:0% right so we're picking backing on this we<00:10:40.180> don't<00:10:40.269> require<00:10:40.600> any<00:10:40.870> new<00:10:41.130> network 00:10:42.120 --> 00:10:42.130 align:start position:0% we don't require any new network 00:10:42.130 --> 00:10:44.970 align:start position:0% we don't require any new network protocols<00:10:42.639> to<00:10:42.970> make<00:10:43.000> them<00:10:43.510> sync<00:10:43.779> happen<00:10:44.110> so<00:10:44.860> we 00:10:44.970 --> 00:10:44.980 align:start position:0% protocols to make them sync happen so we 00:10:44.980 --> 00:10:46.980 align:start position:0% protocols to make them sync happen so we say<00:10:45.130> Pierre<00:10:45.370> give<00:10:45.670> us<00:10:45.790> can<00:10:46.240> you<00:10:46.329> give<00:10:46.449> us<00:10:46.540> F<00:10:46.720> and 00:10:46.980 --> 00:10:46.990 align:start position:0% say Pierre give us can you give us F and 00:10:46.990 --> 00:10:51.569 align:start position:0% say Pierre give us can you give us F and they<00:10:47.110> say<00:10:47.290> sure<00:10:48.269> the<00:10:49.269> node<00:10:49.839> F<00:10:50.230> has<00:10:50.829> children 00:10:51.569 --> 00:10:51.579 align:start position:0% they say sure the node F has children 00:10:51.579 --> 00:10:53.790 align:start position:0% they say sure the node F has children and<00:10:51.819> B<00:10:52.180> so<00:10:52.569> what<00:10:52.810> does<00:10:52.930> that<00:10:52.959> mean<00:10:53.260> it<00:10:53.560> means 00:10:53.790 --> 00:10:53.800 align:start position:0% and B so what does that mean it means 00:10:53.800 --> 00:10:56.460 align:start position:0% and B so what does that mean it means that<00:10:54.130> the<00:10:54.459> hashes<00:10:55.120> of<00:10:55.389> the<00:10:55.630> children<00:10:55.990> of<00:10:56.139> note 00:10:56.460 --> 00:10:56.470 align:start position:0% that the hashes of the children of note 00:10:56.470 --> 00:10:59.639 align:start position:0% that the hashes of the children of note F<00:10:56.680> are<00:10:57.010> a<00:10:57.040> and<00:10:57.459> B<00:10:57.519> you<00:10:58.449> know<00:10:59.079> I'm<00:10:59.170> lying<00:10:59.410> to<00:10:59.620> a 00:10:59.639 --> 00:10:59.649 align:start position:0% F are a and B you know I'm lying to a 00:10:59.649 --> 00:11:01.559 align:start position:0% F are a and B you know I'm lying to a little<00:10:59.920> bit<00:11:00.010> here<00:11:00.269> pretending<00:11:01.269> this<00:11:01.360> is<00:11:01.420> a 00:11:01.559 --> 00:11:01.569 align:start position:0% little bit here pretending this is a 00:11:01.569 --> 00:11:03.540 align:start position:0% little bit here pretending this is a binary<00:11:01.810> tree<00:11:02.050> or<00:11:02.410> other<00:11:02.589> than<00:11:02.860> a<00:11:02.889> modified 00:11:03.540 --> 00:11:03.550 align:start position:0% binary tree or other than a modified 00:11:03.550 --> 00:11:06.780 align:start position:0% binary tree or other than a modified Patricia<00:11:04.389> Merkle<00:11:04.810> tree<00:11:05.339> still<00:11:06.339> gets<00:11:06.550> a<00:11:06.610> point 00:11:06.780 --> 00:11:06.790 align:start position:0% Patricia Merkle tree still gets a point 00:11:06.790 --> 00:11:09.809 align:start position:0% Patricia Merkle tree still gets a point across<00:11:06.880> so<00:11:07.560> we<00:11:08.560> got<00:11:08.680> a<00:11:08.829> and<00:11:08.949> B<00:11:09.069> back<00:11:09.279> and<00:11:09.550> we 00:11:09.809 --> 00:11:09.819 align:start position:0% across so we got a and B back and we 00:11:09.819 --> 00:11:10.870 align:start position:0% across so we got a and B back and we store<00:11:10.029> it<00:11:10.060> in<00:11:10.180> my<00:11:10.240> database 00:11:10.870 --> 00:11:10.880 align:start position:0% store it in my database 00:11:10.880 --> 00:11:12.850 align:start position:0% store it in my database so<00:11:11.240> here's<00:11:11.630> what<00:11:11.930> our<00:11:12.050> local<00:11:12.230> try<00:11:12.620> it<00:11:12.680> looks 00:11:12.850 --> 00:11:12.860 align:start position:0% so here's what our local try it looks 00:11:12.860 --> 00:11:14.830 align:start position:0% so here's what our local try it looks like<00:11:13.040> now<00:11:13.220> we've<00:11:13.790> got<00:11:13.970> two<00:11:14.150> children<00:11:14.540> we<00:11:14.660> don't 00:11:14.830 --> 00:11:14.840 align:start position:0% like now we've got two children we don't 00:11:14.840 --> 00:11:16.900 align:start position:0% like now we've got two children we don't know<00:11:14.930> what<00:11:15.050> are<00:11:15.140> inside<00:11:15.470> them<00:11:15.710> we<00:11:16.490> have<00:11:16.700> the 00:11:16.900 --> 00:11:16.910 align:start position:0% know what are inside them we have the 00:11:16.910 --> 00:11:20.170 align:start position:0% know what are inside them we have the root<00:11:17.060> now<00:11:17.210> and<00:11:18.610> what<00:11:19.610> happens<00:11:19.760> at<00:11:20.000> this<00:11:20.090> point 00:11:20.170 --> 00:11:20.180 align:start position:0% root now and what happens at this point 00:11:20.180 --> 00:11:22.660 align:start position:0% root now and what happens at this point now<00:11:20.870> we're<00:11:21.590> looking<00:11:21.830> for<00:11:22.070> the<00:11:22.280> balance<00:11:22.430> of<00:11:22.610> a 00:11:22.660 --> 00:11:22.670 align:start position:0% now we're looking for the balance of a 00:11:22.670 --> 00:11:24.310 align:start position:0% now we're looking for the balance of a particular<00:11:23.180> address<00:11:23.360> and<00:11:23.840> we<00:11:23.960> know<00:11:24.110> which 00:11:24.310 --> 00:11:24.320 align:start position:0% particular address and we know which 00:11:24.320 --> 00:11:25.540 align:start position:0% particular address and we know which address<00:11:24.620> we're<00:11:24.800> looking<00:11:25.010> for<00:11:25.220> so<00:11:25.430> we<00:11:25.520> don't 00:11:25.540 --> 00:11:25.550 align:start position:0% address we're looking for so we don't 00:11:25.550 --> 00:11:27.430 align:start position:0% address we're looking for so we don't have<00:11:25.760> to<00:11:25.850> fill<00:11:26.030> out<00:11:26.060> the<00:11:26.270> whole<00:11:26.300> tree<00:11:26.690> we<00:11:27.260> can 00:11:27.430 --> 00:11:27.440 align:start position:0% have to fill out the whole tree we can 00:11:27.440 --> 00:11:28.990 align:start position:0% have to fill out the whole tree we can just<00:11:27.590> follow<00:11:27.770> the<00:11:27.980> path<00:11:28.190> to<00:11:28.430> the<00:11:28.520> address<00:11:28.850> we 00:11:28.990 --> 00:11:29.000 align:start position:0% just follow the path to the address we 00:11:29.000 --> 00:11:31.180 align:start position:0% just follow the path to the address we want<00:11:29.180> so<00:11:29.780> let's<00:11:30.020> say<00:11:30.170> the<00:11:30.320> path<00:11:30.530> takes<00:11:30.830> us<00:11:31.010> down 00:11:31.180 --> 00:11:31.190 align:start position:0% want so let's say the path takes us down 00:11:31.190 --> 00:11:35.830 align:start position:0% want so let's say the path takes us down down<00:11:32.150> a<00:11:32.450> and<00:11:32.720> so<00:11:33.670> we<00:11:34.670> want<00:11:34.850> to<00:11:34.970> know<00:11:35.090> what<00:11:35.720> the 00:11:35.830 --> 00:11:35.840 align:start position:0% down a and so we want to know what the 00:11:35.840 --> 00:11:38.110 align:start position:0% down a and so we want to know what the children<00:11:36.020> they<00:11:36.320> are<00:11:36.470> so<00:11:37.040> we<00:11:37.190> ask<00:11:37.340> our<00:11:37.550> peer<00:11:37.790> hey 00:11:38.110 --> 00:11:38.120 align:start position:0% children they are so we ask our peer hey 00:11:38.120 --> 00:11:40.060 align:start position:0% children they are so we ask our peer hey what's<00:11:38.420> what<00:11:38.870> are<00:11:38.990> the<00:11:39.080> children<00:11:39.260> of<00:11:39.440> a<00:11:39.530> it 00:11:40.060 --> 00:11:40.070 align:start position:0% what's what are the children of a it 00:11:40.070 --> 00:11:42.280 align:start position:0% what's what are the children of a it says<00:11:40.310> the<00:11:40.430> children<00:11:40.610> are<00:11:40.910> D<00:11:41.030> and<00:11:41.180> E<00:11:41.270> we<00:11:42.020> save 00:11:42.280 --> 00:11:42.290 align:start position:0% says the children are D and E we save 00:11:42.290 --> 00:11:45.490 align:start position:0% says the children are D and E we save that<00:11:42.500> into<00:11:42.710> our<00:11:42.920> database<00:11:43.120> okay<00:11:44.120> so<00:11:44.810> now<00:11:45.050> we're 00:11:45.490 --> 00:11:45.500 align:start position:0% that into our database okay so now we're 00:11:45.500 --> 00:11:48.100 align:start position:0% that into our database okay so now we're starting<00:11:45.800> to<00:11:46.070> build<00:11:46.280> just<00:11:46.850> a<00:11:47.180> few<00:11:47.660> pieces<00:11:47.900> that 00:11:48.100 --> 00:11:48.110 align:start position:0% starting to build just a few pieces that 00:11:48.110 --> 00:11:50.110 align:start position:0% starting to build just a few pieces that are<00:11:48.320> necessary<00:11:48.830> to<00:11:48.890> get<00:11:49.160> at<00:11:49.370> the<00:11:49.580> balance<00:11:49.940> of 00:11:50.110 --> 00:11:50.120 align:start position:0% are necessary to get at the balance of 00:11:50.120 --> 00:11:53.860 align:start position:0% are necessary to get at the balance of the<00:11:50.270> address<00:11:50.590> that<00:11:51.590> we<00:11:51.710> care<00:11:51.890> about<00:11:51.920> and<00:11:52.750> so<00:11:53.750> we 00:11:53.860 --> 00:11:53.870 align:start position:0% the address that we care about and so we 00:11:53.870 --> 00:11:55.360 align:start position:0% the address that we care about and so we do<00:11:53.990> the<00:11:54.110> same<00:11:54.230> thing<00:11:54.440> again<00:11:54.710> where<00:11:54.860> we<00:11:55.100> know<00:11:55.340> a 00:11:55.360 --> 00:11:55.370 align:start position:0% do the same thing again where we know a 00:11:55.370 --> 00:11:56.500 align:start position:0% do the same thing again where we know a particular<00:11:55.610> address<00:11:55.970> that<00:11:56.180> we're<00:11:56.330> looking 00:11:56.500 --> 00:11:56.510 align:start position:0% particular address that we're looking 00:11:56.510 --> 00:11:59.380 align:start position:0% particular address that we're looking for<00:11:56.660> the<00:11:56.720> balance<00:11:57.020> for<00:11:57.200> let's<00:11:58.040> say<00:11:58.190> it's<00:11:58.370> down 00:11:59.380 --> 00:11:59.390 align:start position:0% for the balance for let's say it's down 00:11:59.390 --> 00:12:01.870 align:start position:0% for the balance for let's say it's down you're<00:11:59.980> meant<00:12:00.980> to<00:12:01.010> follow<00:12:01.280> it<00:12:01.400> down<00:12:01.460> the<00:12:01.730> path 00:12:01.870 --> 00:12:01.880 align:start position:0% you're meant to follow it down the path 00:12:01.880 --> 00:12:05.410 align:start position:0% you're meant to follow it down the path to<00:12:02.120> e<00:12:02.150> and<00:12:02.950> we<00:12:03.950> ask<00:12:04.160> our<00:12:04.400> peer<00:12:04.760> and<00:12:05.000> they<00:12:05.240> say 00:12:05.410 --> 00:12:05.420 align:start position:0% to e and we ask our peer and they say 00:12:05.420 --> 00:12:07.600 align:start position:0% to e and we ask our peer and they say hey<00:12:05.630> e<00:12:05.990> is<00:12:06.260> actually<00:12:06.650> a<00:12:06.680> leaf<00:12:06.890> node<00:12:07.160> it 00:12:07.600 --> 00:12:07.610 align:start position:0% hey e is actually a leaf node it 00:12:07.610 --> 00:12:11.970 align:start position:0% hey e is actually a leaf node it contains<00:12:08.240> the<00:12:08.540> ROP<00:12:09.170> of<00:12:09.740> the<00:12:10.220> account<00:12:10.550> and 00:12:11.970 --> 00:12:11.980 align:start position:0% contains the ROP of the account and 00:12:11.980 --> 00:12:14.290 align:start position:0% contains the ROP of the account and which<00:12:12.980> includes<00:12:13.400> things<00:12:13.640> like<00:12:13.760> the<00:12:14.000> balance 00:12:14.290 --> 00:12:14.300 align:start position:0% which includes things like the balance 00:12:14.300 --> 00:12:16.600 align:start position:0% which includes things like the balance that<00:12:14.780> you're<00:12:14.960> interested<00:12:15.380> in<00:12:15.530> so<00:12:15.920> we<00:12:16.130> save 00:12:16.600 --> 00:12:16.610 align:start position:0% that you're interested in so we save 00:12:16.610 --> 00:12:20.950 align:start position:0% that you're interested in so we save that<00:12:16.640> in<00:12:17.080> in<00:12:18.080> the<00:12:19.010> state<00:12:19.910> database<00:12:20.270> so<00:12:20.780> now 00:12:20.950 --> 00:12:20.960 align:start position:0% that in in the state database so now 00:12:20.960 --> 00:12:22.300 align:start position:0% that in in the state database so now we've<00:12:21.110> got<00:12:21.320> three<00:12:21.620> nodes<00:12:21.890> in<00:12:22.040> the<00:12:22.100> state 00:12:22.300 --> 00:12:22.310 align:start position:0% we've got three nodes in the state 00:12:22.310 --> 00:12:24.760 align:start position:0% we've got three nodes in the state database<00:12:22.700> that's<00:12:23.060> enough<00:12:23.360> to<00:12:23.690> not<00:12:24.380> only<00:12:24.530> know 00:12:24.760 --> 00:12:24.770 align:start position:0% database that's enough to not only know 00:12:24.770 --> 00:12:26.500 align:start position:0% database that's enough to not only know the<00:12:24.890> balance<00:12:25.040> but<00:12:25.460> prove<00:12:25.790> that<00:12:26.060> that<00:12:26.180> balance 00:12:26.500 --> 00:12:26.510 align:start position:0% the balance but prove that that balance 00:12:26.510 --> 00:12:29.200 align:start position:0% the balance but prove that that balance is<00:12:26.990> part<00:12:27.770> of<00:12:27.950> the<00:12:28.340> state<00:12:28.640> route<00:12:28.910> from<00:12:29.120> the 00:12:29.200 --> 00:12:29.210 align:start position:0% is part of the state route from the 00:12:29.210 --> 00:12:34.540 align:start position:0% is part of the state route from the previous<00:12:29.750> block<00:12:31.450> and<00:12:32.950> so<00:12:33.950> at<00:12:34.040> this<00:12:34.130> point<00:12:34.400> we 00:12:34.540 --> 00:12:34.550 align:start position:0% previous block and so at this point we 00:12:34.550 --> 00:12:36.910 align:start position:0% previous block and so at this point we can<00:12:34.820> read<00:12:35.390> the<00:12:35.570> balance<00:12:35.900> out<00:12:36.110> of<00:12:36.410> that<00:12:36.590> leaf 00:12:36.910 --> 00:12:36.920 align:start position:0% can read the balance out of that leaf 00:12:36.920 --> 00:12:39.180 align:start position:0% can read the balance out of that leaf node<00:12:37.160> and<00:12:37.430> push<00:12:38.180> it<00:12:38.300> onto<00:12:38.420> the<00:12:38.540> stack<00:12:38.630> and 00:12:39.180 --> 00:12:39.190 align:start position:0% node and push it onto the stack and 00:12:39.190 --> 00:12:42.760 align:start position:0% node and push it onto the stack and continue<00:12:40.190> resume<00:12:40.610> going<00:12:41.180> down<00:12:41.300> the<00:12:41.420> EBM<00:12:41.770> so 00:12:42.760 --> 00:12:42.770 align:start position:0% continue resume going down the EBM so 00:12:42.770 --> 00:12:44.710 align:start position:0% continue resume going down the EBM so let's<00:12:43.010> say<00:12:43.220> you<00:12:43.580> know<00:12:43.670> the<00:12:43.970> the<00:12:44.060> byte<00:12:44.690> code 00:12:44.710 --> 00:12:44.720 align:start position:0% let's say you know the the byte code 00:12:44.720 --> 00:12:46.360 align:start position:0% let's say you know the the byte code wants<00:12:45.110> to<00:12:45.170> know<00:12:45.290> if<00:12:45.530> the<00:12:45.710> balance<00:12:46.130> was 00:12:46.360 --> 00:12:46.370 align:start position:0% wants to know if the balance was 00:12:46.370 --> 00:12:50.770 align:start position:0% wants to know if the balance was non-empty<00:12:48.220> so<00:12:49.220> this<00:12:50.000> is<00:12:50.150> the<00:12:50.240> gist<00:12:50.450> of<00:12:50.540> it<00:12:50.660> you 00:12:50.770 --> 00:12:50.780 align:start position:0% non-empty so this is the gist of it you 00:12:50.780 --> 00:12:55.270 align:start position:0% non-empty so this is the gist of it you can<00:12:50.960> see<00:12:51.370> you<00:12:52.370> know<00:12:53.470> later<00:12:54.470> on<00:12:54.560> it<00:12:54.920> may<00:12:55.130> be<00:12:55.190> a 00:12:55.270 --> 00:12:55.280 align:start position:0% can see you know later on it may be a 00:12:55.280 --> 00:12:56.890 align:start position:0% can see you know later on it may be a different<00:12:55.550> balances<00:12:55.910> asked<00:12:56.150> for<00:12:56.330> again<00:12:56.690> you'd 00:12:56.890 --> 00:12:56.900 align:start position:0% different balances asked for again you'd 00:12:56.900 --> 00:12:58.960 align:start position:0% different balances asked for again you'd be<00:12:57.050> asking<00:12:57.320> for<00:12:57.380> nodes<00:12:57.890> one<00:12:58.130> by<00:12:58.280> one<00:12:58.460> you<00:12:58.850> get 00:12:58.960 --> 00:12:58.970 align:start position:0% be asking for nodes one by one you get 00:12:58.970 --> 00:13:03.490 align:start position:0% be asking for nodes one by one you get to<00:12:59.120> skip<00:12:59.390> the<00:12:59.420> root<00:12:59.690> node<00:12:59.900> next<00:13:00.290> time<00:13:01.180> but<00:13:02.500> you 00:13:03.490 --> 00:13:03.500 align:start position:0% to skip the root node next time but you 00:13:03.500 --> 00:13:07.920 align:start position:0% to skip the root node next time but you know<00:13:03.620> the<00:13:04.010> same<00:13:04.250> concept<00:13:05.030> applies<00:13:05.680> similarly 00:13:07.920 --> 00:13:07.930 align:start position:0% know the same concept applies similarly 00:13:07.930 --> 00:13:10.420 align:start position:0% know the same concept applies similarly this<00:13:08.930> is<00:13:08.990> showing<00:13:09.410> you<00:13:09.800> know<00:13:09.890> three<00:13:10.190> layers 00:13:10.420 --> 00:13:10.430 align:start position:0% this is showing you know three layers 00:13:10.430 --> 00:13:12.730 align:start position:0% this is showing you know three layers the<00:13:10.850> real<00:13:11.060> mean<00:13:11.390> that's<00:13:11.630> closer<00:13:12.050> to<00:13:12.290> six<00:13:12.590> or 00:13:12.730 --> 00:13:12.740 align:start position:0% the real mean that's closer to six or 00:13:12.740 --> 00:13:15.310 align:start position:0% the real mean that's closer to six or seven<00:13:13.450> probably<00:13:14.450> at<00:13:14.540> this<00:13:14.630> point<00:13:14.690> depending 00:13:15.310 --> 00:13:15.320 align:start position:0% seven probably at this point depending 00:13:15.320 --> 00:13:20.410 align:start position:0% seven probably at this point depending on<00:13:15.440> you<00:13:15.980> know<00:13:16.010> where<00:13:16.280> the<00:13:16.460> accounts<00:13:16.910> so<00:13:19.420> how 00:13:20.410 --> 00:13:20.420 align:start position:0% on you know where the accounts so how 00:13:20.420 --> 00:13:21.970 align:start position:0% on you know where the accounts so how long<00:13:20.570> does<00:13:20.690> that<00:13:20.750> take 00:13:21.970 --> 00:13:21.980 align:start position:0% long does that take 00:13:21.980 --> 00:13:25.570 align:start position:0% long does that take so<00:13:22.520> let's<00:13:22.820> say<00:13:23.000> there<00:13:23.210> are<00:13:23.240> 3000<00:13:24.200> nodes<00:13:24.580> per 00:13:25.570 --> 00:13:25.580 align:start position:0% so let's say there are 3000 nodes per 00:13:25.580 --> 00:13:28.980 align:start position:0% so let's say there are 3000 nodes per block<00:13:26.330> and<00:13:26.740> we<00:13:27.740> only<00:13:27.890> get<00:13:28.070> to<00:13:28.220> request<00:13:28.610> one 00:13:28.980 --> 00:13:28.990 align:start position:0% block and we only get to request one 00:13:28.990 --> 00:13:32.890 align:start position:0% block and we only get to request one node<00:13:29.990> in<00:13:30.350> each<00:13:30.590> request<00:13:30.920> and<00:13:31.510> we're<00:13:32.510> connected 00:13:32.890 --> 00:13:32.900 align:start position:0% node in each request and we're connected 00:13:32.900 --> 00:13:35.020 align:start position:0% node in each request and we're connected to<00:13:33.020> peers<00:13:33.350> but<00:13:33.590> we<00:13:33.920> can<00:13:34.070> only<00:13:34.160> ask<00:13:34.430> one<00:13:34.700> peer<00:13:34.940> at 00:13:35.020 --> 00:13:35.030 align:start position:0% to peers but we can only ask one peer at 00:13:35.030 --> 00:13:37.540 align:start position:0% to peers but we can only ask one peer at a<00:13:35.090> time<00:13:35.300> so<00:13:35.450> we<00:13:35.510> get<00:13:35.600> to<00:13:35.720> ask<00:13:35.900> our<00:13:36.230> best<00:13:36.770> peer<00:13:37.190> we 00:13:37.540 --> 00:13:37.550 align:start position:0% a time so we get to ask our best peer we 00:13:37.550 --> 00:13:40.000 align:start position:0% a time so we get to ask our best peer we get<00:13:37.730> the<00:13:38.180> one<00:13:38.330> that<00:13:38.630> in<00:13:38.990> this<00:13:39.170> case<00:13:39.410> best<00:13:39.740> means 00:13:40.000 --> 00:13:40.010 align:start position:0% get the one that in this case best means 00:13:40.010 --> 00:13:41.710 align:start position:0% get the one that in this case best means we're<00:13:40.250> closest<00:13:40.700> to<00:13:40.880> that'll<00:13:41.180> round-trip 00:13:41.710 --> 00:13:41.720 align:start position:0% we're closest to that'll round-trip 00:13:41.720 --> 00:13:44.800 align:start position:0% we're closest to that'll round-trip fastest<00:13:42.230> so<00:13:42.830> let's<00:13:43.130> say<00:13:43.280> that<00:13:43.310> our<00:13:44.240> best<00:13:44.480> peer 00:13:44.800 --> 00:13:44.810 align:start position:0% fastest so let's say that our best peer 00:13:44.810 --> 00:13:48.190 align:start position:0% fastest so let's say that our best peer is<00:13:45.080> 100<00:13:45.440> milliseconds<00:13:46.010> away<00:13:46.420> so<00:13:47.420> you<00:13:47.510> work 00:13:48.190 --> 00:13:48.200 align:start position:0% is 100 milliseconds away so you work 00:13:48.200 --> 00:13:50.590 align:start position:0% is 100 milliseconds away so you work that<00:13:48.380> all<00:13:48.500> out<00:13:48.680> you<00:13:48.860> get<00:13:49.010> 300<00:13:49.520> seconds<00:13:50.000> of<00:13:50.240> time 00:13:50.590 --> 00:13:50.600 align:start position:0% that all out you get 300 seconds of time 00:13:50.600 --> 00:13:53.590 align:start position:0% that all out you get 300 seconds of time waiting<00:13:51.320> for<00:13:51.470> state<00:13:51.800> for<00:13:52.070> a<00:13:52.130> block<00:13:52.400> and<00:13:52.790> that 00:13:53.590 --> 00:13:53.600 align:start position:0% waiting for state for a block and that 00:13:53.600 --> 00:13:56.170 align:start position:0% waiting for state for a block and that kind<00:13:54.200> of<00:13:54.290> sounds<00:13:54.560> like<00:13:54.590> a<00:13:54.680> problem<00:13:55.100> you<00:13:56.030> can 00:13:56.170 --> 00:13:56.180 align:start position:0% kind of sounds like a problem you can 00:13:56.180 --> 00:13:57.610 align:start position:0% kind of sounds like a problem you can imagine<00:13:56.360> if<00:13:56.660> it<00:13:56.780> takes<00:13:56.960> five<00:13:57.140> minutes<00:13:57.350> to 00:13:57.610 --> 00:13:57.620 align:start position:0% imagine if it takes five minutes to 00:13:57.620 --> 00:13:59.140 align:start position:0% imagine if it takes five minutes to download<00:13:57.920> the<00:13:58.160> state<00:13:58.340> for<00:13:58.520> a<00:13:58.550> block<00:13:58.760> then 00:13:59.140 --> 00:13:59.150 align:start position:0% download the state for a block then 00:13:59.150 --> 00:14:01.450 align:start position:0% download the state for a block then you're<00:13:59.630> gonna<00:13:59.810> lag<00:14:00.050> behind<00:14:00.260> than<00:14:01.100> that<00:14:01.280> and 00:14:01.450 --> 00:14:01.460 align:start position:0% you're gonna lag behind than that and 00:14:01.460 --> 00:14:04.180 align:start position:0% you're gonna lag behind than that and then<00:14:02.000> as<00:14:02.990> you<00:14:03.290> process<00:14:03.560> the<00:14:03.830> next<00:14:03.920> block 00:14:04.180 --> 00:14:04.190 align:start position:0% then as you process the next block 00:14:04.190 --> 00:14:06.820 align:start position:0% then as you process the next block you're<00:14:04.400> gonna<00:14:04.520> lag<00:14:04.730> further<00:14:05.530> that<00:14:06.530> would<00:14:06.680> not 00:14:06.820 --> 00:14:06.830 align:start position:0% you're gonna lag further that would not 00:14:06.830 --> 00:14:08.830 align:start position:0% you're gonna lag further that would not be<00:14:06.950> tenable<00:14:07.280> but<00:14:07.490> the<00:14:07.790> good<00:14:07.940> news<00:14:07.970> is<00:14:08.300> we<00:14:08.720> don't 00:14:08.830 --> 00:14:08.840 align:start position:0% be tenable but the good news is we don't 00:14:08.840 --> 00:14:10.510 align:start position:0% be tenable but the good news is we don't have<00:14:08.930> to<00:14:09.050> wait<00:14:09.290> for<00:14:09.920> the<00:14:09.980> first<00:14:10.130> block<00:14:10.370> to 00:14:10.510 --> 00:14:10.520 align:start position:0% have to wait for the first block to 00:14:10.520 --> 00:14:12.340 align:start position:0% have to wait for the first block to finish<00:14:10.820> before<00:14:11.480> we<00:14:11.600> start<00:14:11.810> executing<00:14:12.050> the 00:14:12.340 --> 00:14:12.350 align:start position:0% finish before we start executing the 00:14:12.350 --> 00:14:15.130 align:start position:0% finish before we start executing the second<00:14:12.710> one<00:14:12.800> so<00:14:13.520> what<00:14:14.090> ends<00:14:14.300> up<00:14:14.360> happening<00:14:14.420> is 00:14:15.130 --> 00:14:15.140 align:start position:0% second one so what ends up happening is 00:14:15.140 --> 00:14:19.030 align:start position:0% second one so what ends up happening is you<00:14:16.300> continue<00:14:17.300> to<00:14:17.560> run<00:14:18.560> these<00:14:18.710> all<00:14:18.920> in 00:14:19.030 --> 00:14:19.040 align:start position:0% you continue to run these all in 00:14:19.040 --> 00:14:22.750 align:start position:0% you continue to run these all in parallel<00:14:19.460> and<00:14:20.080> and<00:14:21.080> you<00:14:21.410> catch<00:14:22.040> up<00:14:22.220> along<00:14:22.610> the 00:14:22.750 --> 00:14:22.760 align:start position:0% parallel and and you catch up along the 00:14:22.760 --> 00:14:25.000 align:start position:0% parallel and and you catch up along the way<00:14:22.880> but<00:14:23.150> you<00:14:23.600> know<00:14:23.660> maybe<00:14:23.990> stay<00:14:24.290> perpetual<00:14:24.890> in 00:14:25.000 --> 00:14:25.010 align:start position:0% way but you know maybe stay perpetual in 00:14:25.010 --> 00:14:28.930 align:start position:0% way but you know maybe stay perpetual in five<00:14:25.190> minutes<00:14:25.520> behind<00:14:25.670> main<00:14:26.060> that<00:14:27.070> in<00:14:28.070> reality 00:14:28.930 --> 00:14:28.940 align:start position:0% five minutes behind main that in reality 00:14:28.940 --> 00:14:30.540 align:start position:0% five minutes behind main that in reality it<00:14:29.150> might<00:14:29.300> look<00:14:29.600> something<00:14:29.990> more<00:14:30.020> like 00:14:30.540 --> 00:14:30.550 align:start position:0% it might look something more like 00:14:30.550 --> 00:14:33.040 align:start position:0% it might look something more like fluctuating<00:14:31.550> between<00:14:31.820> fifteen<00:14:32.750> minutes 00:14:33.040 --> 00:14:33.050 align:start position:0% fluctuating between fifteen minutes 00:14:33.050 --> 00:14:35.650 align:start position:0% fluctuating between fifteen minutes behind<00:14:33.170> and<00:14:33.650> one<00:14:34.100> minute<00:14:34.280> behind<00:14:34.660> depending 00:14:35.650 --> 00:14:35.660 align:start position:0% behind and one minute behind depending 00:14:35.660 --> 00:14:36.670 align:start position:0% behind and one minute behind depending on<00:14:35.750> the<00:14:35.900> blocks<00:14:36.110> that<00:14:36.230> you're<00:14:36.380> running<00:14:36.440> into 00:14:36.670 --> 00:14:36.680 align:start position:0% on the blocks that you're running into 00:14:36.680 --> 00:14:43.240 align:start position:0% on the blocks that you're running into and<00:14:37.280> your<00:14:37.790> peers<00:14:39.190> okay<00:14:40.190> so<00:14:40.850> at<00:14:41.150> this<00:14:41.210> point<00:14:42.250> you 00:14:43.240 --> 00:14:43.250 align:start position:0% and your peers okay so at this point you 00:14:43.250 --> 00:14:44.710 align:start position:0% and your peers okay so at this point you know<00:14:43.370> you're<00:14:43.850> a<00:14:43.880> few<00:14:44.120> minute<00:14:44.300> you've<00:14:44.420> turned 00:14:44.710 --> 00:14:44.720 align:start position:0% know you're a few minute you've turned 00:14:44.720 --> 00:14:48.010 align:start position:0% know you're a few minute you've turned on<00:14:44.870> your<00:14:45.320> node<00:14:45.560> you're<00:14:46.510> five<00:14:47.510> minutes<00:14:47.870> in 00:14:48.010 --> 00:14:48.020 align:start position:0% on your node you're five minutes in 00:14:48.020 --> 00:14:49.660 align:start position:0% on your node you're five minutes in maybe<00:14:48.500> some<00:14:48.770> more<00:14:48.920> minutes<00:14:49.100> for<00:14:49.430> a<00:14:49.460> pure 00:14:49.660 --> 00:14:49.670 align:start position:0% maybe some more minutes for a pure 00:14:49.670 --> 00:14:52.530 align:start position:0% maybe some more minutes for a pure discovery<00:14:50.090> and<00:14:50.210> headers<00:14:50.540> and<00:14:51.220> you've<00:14:52.220> got 00:14:52.530 --> 00:14:52.540 align:start position:0% discovery and headers and you've got 00:14:52.540 --> 00:14:55.510 align:start position:0% discovery and headers and you've got main<00:14:53.540> net<00:14:53.750> blocks<00:14:54.020> executing<00:14:54.890> on<00:14:55.040> your<00:14:55.190> local 00:14:55.510 --> 00:14:55.520 align:start position:0% main net blocks executing on your local 00:14:55.520 --> 00:14:57.970 align:start position:0% main net blocks executing on your local node<00:14:55.840> this<00:14:56.840> is<00:14:56.900> already<00:14:57.200> a<00:14:57.320> way<00:14:57.710> better 00:14:57.970 --> 00:14:57.980 align:start position:0% node this is already a way better 00:14:57.980 --> 00:15:00.550 align:start position:0% node this is already a way better experience<00:14:58.100> than<00:14:58.910> four<00:14:59.330> hours<00:14:59.510> or<00:14:59.990> sometimes 00:15:00.550 --> 00:15:00.560 align:start position:0% experience than four hours or sometimes 00:15:00.560 --> 00:15:05.320 align:start position:0% experience than four hours or sometimes days<00:15:01.130> to<00:15:01.700> run<00:15:02.030> fast<00:15:02.390> sync<00:15:02.830> but<00:15:04.060> it's<00:15:05.060> not<00:15:05.180> good 00:15:05.320 --> 00:15:05.330 align:start position:0% days to run fast sync but it's not good 00:15:05.330 --> 00:15:10.540 align:start position:0% days to run fast sync but it's not good enough<00:15:05.470> so<00:15:06.470> how<00:15:07.370> can<00:15:07.490> we<00:15:07.580> do<00:15:07.700> better<00:15:09.460> one<00:15:10.460> of 00:15:10.540 --> 00:15:10.550 align:start position:0% enough so how can we do better one of 00:15:10.550 --> 00:15:13.540 align:start position:0% enough so how can we do better one of the<00:15:10.640> things<00:15:10.820> we<00:15:11.000> can<00:15:11.210> do<00:15:11.390> is<00:15:11.720> to<00:15:12.050> find<00:15:12.500> out<00:15:12.860> from 00:15:13.540 --> 00:15:13.550 align:start position:0% the things we can do is to find out from 00:15:13.550 --> 00:15:17.620 align:start position:0% the things we can do is to find out from our<00:15:13.670> peers<00:15:14.980> which<00:15:15.980> nodes<00:15:16.400> which<00:15:17.060> try<00:15:17.390> nodes 00:15:17.620 --> 00:15:17.630 align:start position:0% our peers which nodes which try nodes 00:15:17.630 --> 00:15:20.620 align:start position:0% our peers which nodes which try nodes are<00:15:18.070> going<00:15:19.070> to<00:15:19.190> be<00:15:19.310> needed<00:15:19.640> in<00:15:19.820> a<00:15:19.940> block<00:15:20.150> right 00:15:20.620 --> 00:15:20.630 align:start position:0% are going to be needed in a block right 00:15:20.630 --> 00:15:22.230 align:start position:0% are going to be needed in a block right so<00:15:20.930> we're<00:15:21.170> gonna<00:15:21.260> call<00:15:21.530> that<00:15:21.680> the<00:15:21.890> block 00:15:22.230 --> 00:15:22.240 align:start position:0% so we're gonna call that the block 00:15:22.240 --> 00:15:24.940 align:start position:0% so we're gonna call that the block Witness<00:15:23.240> metadata<00:15:24.140> where<00:15:24.410> the<00:15:24.530> witness<00:15:24.800> is 00:15:24.940 --> 00:15:24.950 align:start position:0% Witness metadata where the witness is 00:15:24.950 --> 00:15:26.590 align:start position:0% Witness metadata where the witness is all<00:15:25.070> the<00:15:25.220> state<00:15:25.490> needed<00:15:25.790> to<00:15:26.060> execute<00:15:26.360> the 00:15:26.590 --> 00:15:26.600 align:start position:0% all the state needed to execute the 00:15:26.600 --> 00:15:28.690 align:start position:0% all the state needed to execute the block<00:15:26.780> and<00:15:27.050> the<00:15:27.800> metadata<00:15:28.160> is<00:15:28.370> just<00:15:28.580> the 00:15:28.690 --> 00:15:28.700 align:start position:0% block and the metadata is just the 00:15:28.700 --> 00:15:30.340 align:start position:0% block and the metadata is just the hashes<00:15:29.090> of<00:15:29.360> the<00:15:29.510> state<00:15:29.720> that's<00:15:29.960> needed<00:15:30.260> to 00:15:30.340 --> 00:15:30.350 align:start position:0% hashes of the state that's needed to 00:15:30.350 --> 00:15:33.660 align:start position:0% hashes of the state that's needed to execute<00:15:30.560> the<00:15:30.740> block<00:15:31.000> so 00:15:33.660 --> 00:15:33.670 align:start position:0% execute the block so 00:15:33.670 --> 00:15:37.110 align:start position:0% execute the block so what<00:15:34.180> that<00:15:34.300> allows<00:15:34.540> us<00:15:34.570> to<00:15:34.750> do<00:15:35.140> is<00:15:36.090> match<00:15:37.090> up 00:15:37.110 --> 00:15:37.120 align:start position:0% what that allows us to do is match up 00:15:37.120 --> 00:15:40.890 align:start position:0% what that allows us to do is match up the<00:15:37.660> requests<00:15:38.110> again<00:15:38.410> into<00:15:39.060> 384<00:15:40.060> nodes<00:15:40.690> per 00:15:40.890 --> 00:15:40.900 align:start position:0% the requests again into 384 nodes per 00:15:40.900 --> 00:15:43.530 align:start position:0% the requests again into 384 nodes per request<00:15:41.200> and<00:15:41.560> it<00:15:42.520> allows<00:15:42.730> us<00:15:42.760> to<00:15:43.090> spread<00:15:43.270> those 00:15:43.530 --> 00:15:43.540 align:start position:0% request and it allows us to spread those 00:15:43.540 --> 00:15:48.510 align:start position:0% request and it allows us to spread those requests<00:15:44.020> across<00:15:44.170> multiple<00:15:44.860> Pierce<00:15:47.040> so<00:15:48.040> a 00:15:48.510 --> 00:15:48.520 align:start position:0% requests across multiple Pierce so a 00:15:48.520 --> 00:15:50.220 align:start position:0% requests across multiple Pierce so a quick<00:15:49.000> look<00:15:49.270> this<00:15:49.510> is<00:15:49.630> going<00:15:49.750> to<00:15:49.810> look<00:15:49.930> very 00:15:50.220 --> 00:15:50.230 align:start position:0% quick look this is going to look very 00:15:50.230 --> 00:15:52.320 align:start position:0% quick look this is going to look very similar<00:15:50.860> to<00:15:51.430> the<00:15:51.670> past<00:15:51.820> one<00:15:52.000> so<00:15:52.120> we'll<00:15:52.240> go 00:15:52.320 --> 00:15:52.330 align:start position:0% similar to the past one so we'll go 00:15:52.330 --> 00:15:55.170 align:start position:0% similar to the past one so we'll go through<00:15:52.570> a<00:15:52.600> little<00:15:52.810> bit<00:15:52.930> faster<00:15:53.520> of<00:15:54.520> what<00:15:55.060> that 00:15:55.170 --> 00:15:55.180 align:start position:0% through a little bit faster of what that 00:15:55.180 --> 00:15:58.200 align:start position:0% through a little bit faster of what that might<00:15:55.360> look<00:15:55.420> like<00:15:55.570> so<00:15:56.500> push<00:15:56.980> an<00:15:57.100> address<00:15:57.460> on<00:15:57.790> to 00:15:58.200 --> 00:15:58.210 align:start position:0% might look like so push an address on to 00:15:58.210 --> 00:16:01.650 align:start position:0% might look like so push an address on to the<00:15:58.330> stack<00:15:58.650> ask<00:15:59.650> for<00:15:59.920> its<00:16:00.040> balance<00:16:00.540> hit<00:16:01.540> the 00:16:01.650 --> 00:16:01.660 align:start position:0% the stack ask for its balance hit the 00:16:01.660 --> 00:16:03.540 align:start position:0% the stack ask for its balance hit the empty<00:16:01.900> state<00:16:02.170> database<00:16:02.560> all<00:16:02.860> we<00:16:03.040> know<00:16:03.220> is<00:16:03.400> the 00:16:03.540 --> 00:16:03.550 align:start position:0% empty state database all we know is the 00:16:03.550 --> 00:16:07.550 align:start position:0% empty state database all we know is the root<00:16:03.700> hash<00:16:04.590> find<00:16:05.590> a<00:16:05.680> peer<00:16:05.920> to<00:16:06.040> help<00:16:06.190> us<00:16:06.310> out<00:16:06.460> and 00:16:07.550 --> 00:16:07.560 align:start position:0% root hash find a peer to help us out and 00:16:07.560 --> 00:16:10.680 align:start position:0% root hash find a peer to help us out and now<00:16:08.560> instead<00:16:08.950> of<00:16:09.100> asking<00:16:09.610> for<00:16:09.640> that<00:16:09.850> root<00:16:10.420> node 00:16:10.680 --> 00:16:10.690 align:start position:0% now instead of asking for that root node 00:16:10.690 --> 00:16:13.290 align:start position:0% now instead of asking for that root node what<00:16:11.050> we<00:16:11.140> do<00:16:11.320> is<00:16:11.590> we<00:16:11.890> get<00:16:12.520> a<00:16:12.580> witness<00:16:12.760> really 00:16:13.290 --> 00:16:13.300 align:start position:0% what we do is we get a witness really 00:16:13.300 --> 00:16:14.940 align:start position:0% what we do is we get a witness really I'd<00:16:13.420> probably<00:16:13.570> call<00:16:13.840> it<00:16:13.960> witness<00:16:14.230> metadata<00:16:14.710> or 00:16:14.940 --> 00:16:14.950 align:start position:0% I'd probably call it witness metadata or 00:16:14.950 --> 00:16:18.390 align:start position:0% I'd probably call it witness metadata or something<00:16:15.480> and<00:16:16.480> we<00:16:17.380> know<00:16:17.590> which<00:16:17.890> block<00:16:18.220> we're 00:16:18.390 --> 00:16:18.400 align:start position:0% something and we know which block we're 00:16:18.400 --> 00:16:20.430 align:start position:0% something and we know which block we're on<00:16:18.490> of<00:16:18.670> course<00:16:18.850> so<00:16:19.090> we<00:16:19.240> can<00:16:19.480> say<00:16:19.870> hey<00:16:20.080> Pierre 00:16:20.430 --> 00:16:20.440 align:start position:0% on of course so we can say hey Pierre 00:16:20.440 --> 00:16:23.220 align:start position:0% on of course so we can say hey Pierre can<00:16:21.010> you<00:16:21.100> tell<00:16:21.370> us<00:16:21.400> which<00:16:22.360> hashes<00:16:22.930> we're<00:16:23.110> gonna 00:16:23.220 --> 00:16:23.230 align:start position:0% can you tell us which hashes we're gonna 00:16:23.230 --> 00:16:25.830 align:start position:0% can you tell us which hashes we're gonna need<00:16:23.470> for<00:16:23.830> block<00:16:24.010> G<00:16:24.190> you<00:16:24.970> say<00:16:25.150> sure<00:16:25.330> we're 00:16:25.830 --> 00:16:25.840 align:start position:0% need for block G you say sure we're 00:16:25.840 --> 00:16:29.870 align:start position:0% need for block G you say sure we're gonna<00:16:25.960> need<00:16:26.110> FA<00:16:26.530> and<00:16:26.710> E<00:16:26.860> from<00:16:27.730> last<00:16:28.690> time<00:16:28.960> so 00:16:29.870 --> 00:16:29.880 align:start position:0% gonna need FA and E from last time so 00:16:29.880 --> 00:16:32.820 align:start position:0% gonna need FA and E from last time so you<00:16:30.880> know<00:16:30.970> at<00:16:31.150> this<00:16:31.270> point<00:16:31.510> we<00:16:32.410> actually<00:16:32.500> can't 00:16:32.820 --> 00:16:32.830 align:start position:0% you know at this point we actually can't 00:16:32.830 --> 00:16:34.290 align:start position:0% you know at this point we actually can't store<00:16:33.130> anything<00:16:33.400> in<00:16:33.580> the<00:16:33.700> database<00:16:34.030> we<00:16:34.180> just 00:16:34.290 --> 00:16:34.300 align:start position:0% store anything in the database we just 00:16:34.300 --> 00:16:35.430 align:start position:0% store anything in the database we just have<00:16:34.390> a<00:16:34.420> bunch<00:16:34.630> of<00:16:34.720> keys<00:16:34.930> we<00:16:35.080> don't<00:16:35.230> have<00:16:35.320> any 00:16:35.430 --> 00:16:35.440 align:start position:0% have a bunch of keys we don't have any 00:16:35.440 --> 00:16:37.350 align:start position:0% have a bunch of keys we don't have any key<00:16:35.590> value<00:16:35.860> pairs<00:16:36.130> and<00:16:36.490> in<00:16:36.970> fact<00:16:37.120> we<00:16:37.270> don't 00:16:37.350 --> 00:16:37.360 align:start position:0% key value pairs and in fact we don't 00:16:37.360 --> 00:16:39.720 align:start position:0% key value pairs and in fact we don't know<00:16:37.510> how<00:16:37.660> these<00:16:37.840> stitch<00:16:38.200> together<00:16:38.550> all<00:16:39.550> we 00:16:39.720 --> 00:16:39.730 align:start position:0% know how these stitch together all we 00:16:39.730 --> 00:16:44.100 align:start position:0% know how these stitch together all we really<00:16:39.850> know<00:16:40.090> is<00:16:40.120> F<00:16:40.360> so<00:16:40.480> at<00:16:40.570> the<00:16:40.660> root<00:16:42.720> but<00:16:43.720> we 00:16:44.100 --> 00:16:44.110 align:start position:0% really know is F so at the root but we 00:16:44.110 --> 00:16:45.990 align:start position:0% really know is F so at the root but we can<00:16:44.290> use<00:16:44.470> it<00:16:44.500> to<00:16:44.830> now<00:16:44.950> make<00:16:45.160> the<00:16:45.310> next<00:16:45.490> requests 00:16:45.990 --> 00:16:46.000 align:start position:0% can use it to now make the next requests 00:16:46.000 --> 00:16:48.690 align:start position:0% can use it to now make the next requests so<00:16:46.270> we<00:16:46.390> can<00:16:46.600> match<00:16:47.590> them<00:16:47.860> together<00:16:48.010> put<00:16:48.550> them 00:16:48.690 --> 00:16:48.700 align:start position:0% so we can match them together put them 00:16:48.700 --> 00:16:50.310 align:start position:0% so we can match them together put them in<00:16:48.790> a<00:16:48.850> single<00:16:49.150> request<00:16:49.240> we<00:16:49.780> can<00:16:49.930> send<00:16:50.140> it<00:16:50.200> to<00:16:50.230> a 00:16:50.310 --> 00:16:50.320 align:start position:0% in a single request we can send it to a 00:16:50.320 --> 00:16:52.470 align:start position:0% in a single request we can send it to a different<00:16:50.440> peer<00:16:50.800> we<00:16:50.920> can<00:16:51.070> send<00:16:51.310> it<00:16:51.430> to<00:16:51.460> we<00:16:52.330> can 00:16:52.470 --> 00:16:52.480 align:start position:0% different peer we can send it to we can 00:16:52.480 --> 00:16:53.970 align:start position:0% different peer we can send it to we can split<00:16:52.660> it<00:16:52.810> up<00:16:52.870> and<00:16:53.140> send<00:16:53.440> it<00:16:53.530> to<00:16:53.680> a<00:16:53.710> bunch<00:16:53.770> of 00:16:53.970 --> 00:16:53.980 align:start position:0% split it up and send it to a bunch of 00:16:53.980 --> 00:16:56.910 align:start position:0% split it up and send it to a bunch of different<00:16:54.130> peers<00:16:55.380> we<00:16:56.380> have<00:16:56.470> a<00:16:56.530> lot<00:16:56.650> of<00:16:56.680> options 00:16:56.910 --> 00:16:56.920 align:start position:0% different peers we have a lot of options 00:16:56.920 --> 00:17:00.360 align:start position:0% different peers we have a lot of options and<00:16:57.430> so<00:16:58.000> we<00:16:58.390> get<00:16:58.630> back<00:16:58.980> essentially<00:16:59.980> all<00:17:00.220> the 00:17:00.360 --> 00:17:00.370 align:start position:0% and so we get back essentially all the 00:17:00.370 --> 00:17:03.180 align:start position:0% and so we get back essentially all the data<00:17:00.580> that<00:17:00.670> that<00:17:01.120> was<00:17:01.510> requested<00:17:02.110> in<00:17:02.470> the 00:17:03.180 --> 00:17:03.190 align:start position:0% data that that was requested in the 00:17:03.190 --> 00:17:07.110 align:start position:0% data that that was requested in the previous<00:17:03.520> slide<00:17:03.760> so<00:17:04.750> we<00:17:04.870> know<00:17:04.990> F<00:17:05.790> has<00:17:06.790> children 00:17:07.110 --> 00:17:07.120 align:start position:0% previous slide so we know F has children 00:17:07.120 --> 00:17:10.319 align:start position:0% previous slide so we know F has children a<00:17:07.270> and<00:17:07.420> B<00:17:07.540> a<00:17:07.839> has<00:17:07.930> children<00:17:08.650> D<00:17:08.890> and<00:17:09.040> E<00:17:09.160> and<00:17:09.430> E<00:17:10.150> is 00:17:10.319 --> 00:17:10.329 align:start position:0% a and B a has children D and E and E is 00:17:10.329 --> 00:17:11.460 align:start position:0% a and B a has children D and E and E is the<00:17:10.540> account<00:17:10.810> ROP 00:17:11.460 --> 00:17:11.470 align:start position:0% the account ROP 00:17:11.470 --> 00:17:13.410 align:start position:0% the account ROP so<00:17:11.680> we<00:17:11.770> save<00:17:11.949> it<00:17:12.070> into<00:17:12.220> the<00:17:12.339> database<00:17:12.490> that's 00:17:13.410 --> 00:17:13.420 align:start position:0% so we save it into the database that's 00:17:13.420 --> 00:17:15.449 align:start position:0% so we save it into the database that's enough<00:17:13.750> we<00:17:13.930> can<00:17:14.079> look<00:17:14.230> up<00:17:14.350> and<00:17:14.560> prove<00:17:15.100> the 00:17:15.449 --> 00:17:15.459 align:start position:0% enough we can look up and prove the 00:17:15.459 --> 00:17:17.670 align:start position:0% enough we can look up and prove the account<00:17:16.089> balance<00:17:16.420> and<00:17:16.660> push<00:17:17.350> it<00:17:17.470> onto<00:17:17.589> the 00:17:17.670 --> 00:17:17.680 align:start position:0% account balance and push it onto the 00:17:17.680 --> 00:17:19.530 align:start position:0% account balance and push it onto the stack<00:17:17.740> and<00:17:18.100> then<00:17:18.370> ask<00:17:19.030> follow-up<00:17:19.449> questions 00:17:19.530 --> 00:17:19.540 align:start position:0% stack and then ask follow-up questions 00:17:19.540 --> 00:17:23.100 align:start position:0% stack and then ask follow-up questions like<00:17:20.170> is<00:17:20.410> that<00:17:20.589> balance<00:17:20.740> zero<00:17:21.570> which<00:17:22.570> is<00:17:22.780> you 00:17:23.100 --> 00:17:23.110 align:start position:0% like is that balance zero which is you 00:17:23.110 --> 00:17:26.670 align:start position:0% like is that balance zero which is you know<00:17:23.199> a<00:17:23.230> stateless<00:17:23.589> call<00:17:24.870> okay<00:17:25.870> so<00:17:26.350> how<00:17:26.560> much 00:17:26.670 --> 00:17:26.680 align:start position:0% know a stateless call okay so how much 00:17:26.680 --> 00:17:29.400 align:start position:0% know a stateless call okay so how much does<00:17:26.860> that<00:17:26.920> help<00:17:27.220> us<00:17:27.420> well<00:17:28.420> let's<00:17:29.200> run<00:17:29.350> some 00:17:29.400 --> 00:17:29.410 align:start position:0% does that help us well let's run some 00:17:29.410 --> 00:17:32.100 align:start position:0% does that help us well let's run some numbers<00:17:29.680> so<00:17:30.160> let's<00:17:30.370> say<00:17:30.580> again<00:17:30.940> 3000<00:17:31.840> try 00:17:32.100 --> 00:17:32.110 align:start position:0% numbers so let's say again 3000 try 00:17:32.110 --> 00:17:36.180 align:start position:0% numbers so let's say again 3000 try nodes<00:17:32.410> per<00:17:32.590> block<00:17:33.240> rough<00:17:34.240> number<00:17:34.600> and<00:17:35.190> but 00:17:36.180 --> 00:17:36.190 align:start position:0% nodes per block rough number and but 00:17:36.190 --> 00:17:38.460 align:start position:0% nodes per block rough number and but this<00:17:36.310> time<00:17:36.520> we<00:17:36.610> get<00:17:36.700> to<00:17:36.850> group<00:17:37.030> it<00:17:37.150> into<00:17:37.380> 384<00:17:38.380> at 00:17:38.460 --> 00:17:38.470 align:start position:0% this time we get to group it into 384 at 00:17:38.470 --> 00:17:41.400 align:start position:0% this time we get to group it into 384 at a<00:17:38.530> time<00:17:38.740> and<00:17:39.180> you<00:17:40.180> know<00:17:40.270> we're<00:17:40.480> again<00:17:41.050> assuming 00:17:41.400 --> 00:17:41.410 align:start position:0% a time and you know we're again assuming 00:17:41.410 --> 00:17:43.500 align:start position:0% a time and you know we're again assuming and<00:17:41.950> this<00:17:42.250> looks<00:17:42.520> about<00:17:42.910> right<00:17:43.120> from 00:17:43.500 --> 00:17:43.510 align:start position:0% and this looks about right from 00:17:43.510 --> 00:17:45.570 align:start position:0% and this looks about right from empirical<00:17:44.020> test<00:17:44.350> that<00:17:44.590> most<00:17:45.130> of<00:17:45.340> the<00:17:45.430> time 00:17:45.570 --> 00:17:45.580 align:start position:0% empirical test that most of the time 00:17:45.580 --> 00:17:47.470 align:start position:0% empirical test that most of the time spent<00:17:45.850> is<00:17:45.940> latency 00:17:47.470 --> 00:17:47.480 align:start position:0% spent is latency 00:17:47.480 --> 00:17:50.210 align:start position:0% spent is latency we<00:17:48.480> get<00:17:48.600> to<00:17:48.690> group<00:17:48.870> it<00:17:48.990> up<00:17:49.080> and<00:17:49.320> we<00:17:49.680> get<00:17:49.800> to<00:17:49.920> also 00:17:50.210 --> 00:17:50.220 align:start position:0% we get to group it up and we get to also 00:17:50.220 --> 00:17:51.650 align:start position:0% we get to group it up and we get to also split<00:17:50.400> it<00:17:50.550> up<00:17:50.640> so<00:17:50.700> we<00:17:51.000> get<00:17:51.090> to<00:17:51.240> send<00:17:51.450> these 00:17:51.650 --> 00:17:51.660 align:start position:0% split it up so we get to send these 00:17:51.660 --> 00:17:53.960 align:start position:0% split it up so we get to send these requests<00:17:52.230> to<00:17:52.500> let's<00:17:53.220> say<00:17:53.370> four<00:17:53.640> different 00:17:53.960 --> 00:17:53.970 align:start position:0% requests to let's say four different 00:17:53.970 --> 00:17:57.740 align:start position:0% requests to let's say four different peers<00:17:54.210> at<00:17:54.450> at<00:17:54.720> once<00:17:55.020> and<00:17:56.420> now<00:17:57.420> that<00:17:57.630> we're 00:17:57.740 --> 00:17:57.750 align:start position:0% peers at at once and now that we're 00:17:57.750 --> 00:17:59.270 align:start position:0% peers at at once and now that we're sending<00:17:58.050> it<00:17:58.230> to<00:17:58.290> more<00:17:58.470> than<00:17:58.590> our<00:17:58.740> best<00:17:58.920> peer 00:17:59.270 --> 00:17:59.280 align:start position:0% sending it to more than our best peer 00:17:59.280 --> 00:18:01.460 align:start position:0% sending it to more than our best peer you<00:17:59.850> know<00:17:59.910> maybe<00:18:00.090> the<00:18:00.240> average<00:18:00.660> round-trip 00:18:01.460 --> 00:18:01.470 align:start position:0% you know maybe the average round-trip 00:18:01.470 --> 00:18:04.010 align:start position:0% you know maybe the average round-trip time<00:18:01.980> actually<00:18:02.580> goes<00:18:02.790> up<00:18:03.030> you<00:18:03.390> know<00:18:03.510> that<00:18:03.810> we 00:18:04.010 --> 00:18:04.020 align:start position:0% time actually goes up you know that we 00:18:04.020 --> 00:18:05.480 align:start position:0% time actually goes up you know that we have<00:18:04.140> to<00:18:04.290> rely<00:18:04.650> on<00:18:04.680> some<00:18:05.010> peers<00:18:05.220> that<00:18:05.370> are<00:18:05.460> a 00:18:05.480 --> 00:18:05.490 align:start position:0% have to rely on some peers that are a 00:18:05.490 --> 00:18:09.230 align:start position:0% have to rely on some peers that are a little<00:18:05.640> further<00:18:05.910> away<00:18:06.770> and<00:18:07.770> so<00:18:08.460> maybe<00:18:08.850> each 00:18:09.230 --> 00:18:09.240 align:start position:0% little further away and so maybe each 00:18:09.240 --> 00:18:11.540 align:start position:0% little further away and so maybe each peer<00:18:09.660> takes<00:18:09.960> 500<00:18:10.560> milliseconds<00:18:11.400> to 00:18:11.540 --> 00:18:11.550 align:start position:0% peer takes 500 milliseconds to 00:18:11.550 --> 00:18:16.670 align:start position:0% peer takes 500 milliseconds to round-trip<00:18:12.620> and<00:18:13.620> so<00:18:13.950> all<00:18:14.370> of<00:18:14.430> that<00:18:15.590> throw<00:18:16.590> it 00:18:16.670 --> 00:18:16.680 align:start position:0% round-trip and so all of that throw it 00:18:16.680 --> 00:18:19.520 align:start position:0% round-trip and so all of that throw it into<00:18:17.360> you<00:18:18.360> know<00:18:18.420> throw<00:18:18.720> some<00:18:18.870> arithmetic<00:18:19.410> at 00:18:19.520 --> 00:18:19.530 align:start position:0% into you know throw some arithmetic at 00:18:19.530 --> 00:18:22.160 align:start position:0% into you know throw some arithmetic at it<00:18:19.680> and<00:18:19.860> you<00:18:20.460> get<00:18:20.670> one<00:18:21.210> second<00:18:21.690> of<00:18:21.840> time 00:18:22.160 --> 00:18:22.170 align:start position:0% it and you get one second of time 00:18:22.170 --> 00:18:26.540 align:start position:0% it and you get one second of time waiting<00:18:23.100> on<00:18:23.220> try<00:18:23.610> note<00:18:23.820> requests<00:18:24.300> so<00:18:25.340> this<00:18:26.340> is 00:18:26.540 --> 00:18:26.550 align:start position:0% waiting on try note requests so this is 00:18:26.550 --> 00:18:32.060 align:start position:0% waiting on try note requests so this is a<00:18:29.780> prediction<00:18:30.780> all<00:18:31.320> right<00:18:31.410> the<00:18:31.560> other<00:18:31.590> one<00:18:31.920> is 00:18:32.060 --> 00:18:32.070 align:start position:0% a prediction all right the other one is 00:18:32.070 --> 00:18:34.460 align:start position:0% a prediction all right the other one is is<00:18:32.340> known<00:18:32.850> but<00:18:33.630> this<00:18:33.900> is<00:18:34.050> a<00:18:34.080> fairly 00:18:34.460 --> 00:18:34.470 align:start position:0% is known but this is a fairly 00:18:34.470 --> 00:18:36.920 align:start position:0% is known but this is a fairly straightforward<00:18:34.830> extension<00:18:35.720> that<00:18:36.720> we're 00:18:36.920 --> 00:18:36.930 align:start position:0% straightforward extension that we're 00:18:36.930 --> 00:18:39.530 align:start position:0% straightforward extension that we're looking<00:18:37.020> at<00:18:37.290> that<00:18:37.590> would<00:18:37.770> be<00:18:38.280> pretty<00:18:39.210> much<00:18:39.270> the 00:18:39.530 --> 00:18:39.540 align:start position:0% looking at that would be pretty much the 00:18:39.540 --> 00:18:41.630 align:start position:0% looking at that would be pretty much the whole<00:18:39.660> game<00:18:39.900> right<00:18:40.260> if<00:18:40.500> you<00:18:40.620> can<00:18:40.860> download<00:18:41.280> all 00:18:41.630 --> 00:18:41.640 align:start position:0% whole game right if you can download all 00:18:41.640 --> 00:18:43.580 align:start position:0% whole game right if you can download all the<00:18:41.790> state<00:18:42.000> in<00:18:42.240> one<00:18:42.510> second<00:18:42.930> for<00:18:43.140> a<00:18:43.170> block<00:18:43.380> you 00:18:43.580 --> 00:18:43.590 align:start position:0% the state in one second for a block you 00:18:43.590 --> 00:18:45.770 align:start position:0% the state in one second for a block you can<00:18:43.650> keep<00:18:44.040> up<00:18:44.220> with<00:18:45.150> me<00:18:45.300> and<00:18:45.360> that<00:18:45.540> quite 00:18:45.770 --> 00:18:45.780 align:start position:0% can keep up with me and that quite 00:18:45.780 --> 00:18:49.220 align:start position:0% can keep up with me and that quite easily<00:18:47.030> from<00:18:48.030> the<00:18:48.180> beginning<00:18:48.570> of<00:18:48.810> launching 00:18:49.220 --> 00:18:49.230 align:start position:0% easily from the beginning of launching 00:18:49.230 --> 00:18:53.480 align:start position:0% easily from the beginning of launching an<00:18:49.320> empty<00:18:49.620> node<00:18:50.390> so<00:18:51.770> how<00:18:52.770> close<00:18:52.920> are<00:18:53.100> we 00:18:53.480 --> 00:18:53.490 align:start position:0% an empty node so how close are we 00:18:53.490 --> 00:18:57.350 align:start position:0% an empty node so how close are we well<00:18:54.060> v-0<00:18:54.960> is<00:18:55.320> prototyped<00:18:56.040> in<00:18:56.340> Trinity<00:18:57.000> alpha 00:18:57.350 --> 00:18:57.360 align:start position:0% well v-0 is prototyped in Trinity alpha 00:18:57.360 --> 00:19:02.200 align:start position:0% well v-0 is prototyped in Trinity alpha the<00:18:58.140> that<00:18:59.010> works<00:18:59.340> on<00:18:59.640> main<00:19:00.600> net<00:19:00.840> right<00:19:00.990> now<00:19:01.050> so 00:19:02.200 --> 00:19:02.210 align:start position:0% the that works on main net right now so 00:19:02.210 --> 00:19:07.160 align:start position:0% the that works on main net right now so we<00:19:03.210> have<00:19:03.600> executed<00:19:04.290> many<00:19:04.620> main<00:19:04.890> networks<00:19:06.170> over 00:19:07.160 --> 00:19:07.170 align:start position:0% we have executed many main networks over 00:19:07.170 --> 00:19:12.020 align:start position:0% we have executed many main networks over and<00:19:07.290> over<00:19:07.850> and<00:19:09.920> you<00:19:10.920> know<00:19:11.010> generated<00:19:11.520> local 00:19:12.020 --> 00:19:12.030 align:start position:0% and over and you know generated local 00:19:12.030 --> 00:19:14.420 align:start position:0% and over and you know generated local witnesses<00:19:12.450> that<00:19:12.660> kind<00:19:12.870> of<00:19:12.930> thing<00:19:13.110> but<00:19:13.770> it's 00:19:14.420 --> 00:19:14.430 align:start position:0% witnesses that kind of thing but it's 00:19:14.430 --> 00:19:17.060 align:start position:0% witnesses that kind of thing but it's not<00:19:14.580> production<00:19:15.000> ready<00:19:15.440> you<00:19:16.440> know<00:19:16.560> it's<00:19:16.710> this 00:19:17.060 --> 00:19:17.070 align:start position:0% not production ready you know it's this 00:19:17.070 --> 00:19:18.910 align:start position:0% not production ready you know it's this is<00:19:17.130> meant<00:19:17.520> for<00:19:17.580> experimentation<00:19:18.450> right<00:19:18.750> now 00:19:18.910 --> 00:19:18.920 align:start position:0% is meant for experimentation right now 00:19:18.920 --> 00:19:22.220 align:start position:0% is meant for experimentation right now but<00:19:19.920> there's<00:19:20.190> nothing<00:19:20.610> left<00:19:20.880> to<00:19:21.870> research 00:19:22.220 --> 00:19:22.230 align:start position:0% but there's nothing left to research 00:19:22.230 --> 00:19:25.340 align:start position:0% but there's nothing left to research there's<00:19:22.890> no<00:19:23.480> there's<00:19:24.480> no<00:19:24.630> open<00:19:24.960> questions 00:19:25.340 --> 00:19:25.350 align:start position:0% there's no there's no open questions 00:19:25.350 --> 00:19:27.710 align:start position:0% there's no there's no open questions really<00:19:25.560> on<00:19:25.860> on<00:19:26.190> d0<00:19:26.910> and<00:19:26.970> how<00:19:27.180> it<00:19:27.270> works<00:19:27.420> just 00:19:27.710 --> 00:19:27.720 align:start position:0% really on on d0 and how it works just 00:19:27.720 --> 00:19:30.680 align:start position:0% really on on d0 and how it works just more<00:19:28.050> coding<00:19:28.290> to<00:19:28.530> do<00:19:28.700> now<00:19:29.700> the<00:19:29.760> witness 00:19:30.680 --> 00:19:30.690 align:start position:0% more coding to do now the witness 00:19:30.690 --> 00:19:33.980 align:start position:0% more coding to do now the witness metadata<00:19:31.850> surveying<00:19:32.850> is<00:19:33.120> in<00:19:33.390> its<00:19:33.630> design 00:19:33.980 --> 00:19:33.990 align:start position:0% metadata surveying is in its design 00:19:33.990 --> 00:19:36.230 align:start position:0% metadata surveying is in its design phase<00:19:34.230> right<00:19:34.710> so<00:19:35.040> we<00:19:35.610> have<00:19:35.700> ideas<00:19:36.000> about<00:19:36.150> how 00:19:36.230 --> 00:19:36.240 align:start position:0% phase right so we have ideas about how 00:19:36.240 --> 00:19:37.490 align:start position:0% phase right so we have ideas about how to<00:19:36.300> do<00:19:36.480> that<00:19:36.630> that's<00:19:36.900> gonna<00:19:37.080> be<00:19:37.200> coming<00:19:37.440> up 00:19:37.490 --> 00:19:37.500 align:start position:0% to do that that's gonna be coming up 00:19:37.500 --> 00:19:40.340 align:start position:0% to do that that's gonna be coming up next<00:19:37.920> right<00:19:38.040> after<00:19:38.190> DEFCON<00:19:39.020> you<00:19:40.020> know<00:19:40.110> follow 00:19:40.340 --> 00:19:40.350 align:start position:0% next right after DEFCON you know follow 00:19:40.350 --> 00:19:45.350 align:start position:0% next right after DEFCON you know follow us<00:19:40.500> to<00:19:40.620> see<00:19:41.390> how<00:19:42.390> that<00:19:42.600> progresses<00:19:42.750> and<00:19:44.360> people 00:19:45.350 --> 00:19:45.360 align:start position:0% us to see how that progresses and people 00:19:45.360 --> 00:19:46.940 align:start position:0% us to see how that progresses and people sometimes<00:19:45.600> ask<00:19:45.840> the<00:19:45.960> question<00:19:46.260> well<00:19:46.560> why 00:19:46.940 --> 00:19:46.950 align:start position:0% sometimes ask the question well why 00:19:46.950 --> 00:19:49.760 align:start position:0% sometimes ask the question well why hasn't<00:19:47.190> anyone<00:19:47.490> done<00:19:47.610> this<00:19:47.820> before<00:19:48.030> and<00:19:48.770> the 00:19:49.760 --> 00:19:49.770 align:start position:0% hasn't anyone done this before and the 00:19:49.770 --> 00:19:53.840 align:start position:0% hasn't anyone done this before and the answer<00:19:49.980> is<00:19:50.430> that<00:19:51.800> no<00:19:52.800> one<00:19:52.920> had<00:19:53.070> to<00:19:53.250> you<00:19:53.580> know<00:19:53.670> we 00:19:53.840 --> 00:19:53.850 align:start position:0% answer is that no one had to you know we 00:19:53.850 --> 00:19:55.610 align:start position:0% answer is that no one had to you know we were<00:19:54.000> forced<00:19:54.330> to<00:19:54.510> do<00:19:54.630> it<00:19:54.660> because<00:19:54.960> python<00:19:55.470> is 00:19:55.610 --> 00:19:55.620 align:start position:0% were forced to do it because python is 00:19:55.620 --> 00:19:58.690 align:start position:0% were forced to do it because python is slow<00:19:55.770> so<00:19:56.190> we<00:19:56.310> had<00:19:56.460> to<00:19:56.580> ask<00:19:56.700> these<00:19:56.910> questions 00:19:58.690 --> 00:19:58.700 align:start position:0% slow so we had to ask these questions 00:19:58.700 --> 00:20:00.500 align:start position:0% slow so we had to ask these questions there<00:19:59.700> was<00:19:59.760> a<00:19:59.850> chicken<00:20:00.060> in<00:20:00.210> the<00:20:00.240> egg 00:20:00.500 --> 00:20:00.510 align:start position:0% there was a chicken in the egg 00:20:00.510 --> 00:20:04.550 align:start position:0% there was a chicken in the egg problem<00:20:00.900> with<00:20:01.230> why<00:20:02.180> why<00:20:03.180> we<00:20:03.330> can't<00:20:03.600> couldn't 00:20:04.550 --> 00:20:04.560 align:start position:0% problem with why why we can't couldn't 00:20:04.560 --> 00:20:06.440 align:start position:0% problem with why why we can't couldn't use<00:20:04.680> witnesses<00:20:05.160> right<00:20:05.370> away<00:20:05.550> and<00:20:05.760> v-0<00:20:06.090> because 00:20:06.440 --> 00:20:06.450 align:start position:0% use witnesses right away and v-0 because 00:20:06.450 --> 00:20:08.120 align:start position:0% use witnesses right away and v-0 because there<00:20:06.570> were<00:20:06.660> no<00:20:06.780> serve<00:20:07.050> servers<00:20:07.800> of<00:20:07.980> those 00:20:08.120 --> 00:20:08.130 align:start position:0% there were no serve servers of those 00:20:08.130 --> 00:20:11.150 align:start position:0% there were no serve servers of those witnesses<00:20:08.610> and<00:20:08.850> so<00:20:09.360> Trinity<00:20:09.950> can't<00:20:10.950> serve 00:20:11.150 --> 00:20:11.160 align:start position:0% witnesses and so Trinity can't serve 00:20:11.160 --> 00:20:13.460 align:start position:0% witnesses and so Trinity can't serve them<00:20:11.430> until<00:20:12.240> it<00:20:12.330> sinks<00:20:12.510> so<00:20:12.780> we're<00:20:12.870> gonna<00:20:12.990> boot 00:20:13.460 --> 00:20:13.470 align:start position:0% them until it sinks so we're gonna boot 00:20:13.470 --> 00:20:17.210 align:start position:0% them until it sinks so we're gonna boot strap<00:20:13.770> with<00:20:13.980> v-0<00:20:14.430> in<00:20:14.730> order<00:20:15.300> to<00:20:15.420> sync<00:20:15.810> v1<00:20:16.350> so 00:20:17.210 --> 00:20:17.220 align:start position:0% strap with v-0 in order to sync v1 so 00:20:17.220 --> 00:20:20.450 align:start position:0% strap with v-0 in order to sync v1 so that's<00:20:17.550> it<00:20:17.730> we're<00:20:18.510> we're<00:20:19.470> doing<00:20:19.500> this<00:20:19.980> now 00:20:20.450 --> 00:20:20.460 align:start position:0% that's it we're we're doing this now 00:20:20.460 --> 00:20:21.590 align:start position:0% that's it we're we're doing this now we're<00:20:20.580> talking<00:20:20.820> to<00:20:20.880> other<00:20:21.000> clients<00:20:21.180> to<00:20:21.390> get<00:20:21.480> it 00:20:21.590 --> 00:20:21.600 align:start position:0% we're talking to other clients to get it 00:20:21.600 --> 00:20:23.240 align:start position:0% we're talking to other clients to get it done<00:20:21.750> for<00:20:21.900> them<00:20:22.050> it's<00:20:22.770> a<00:20:22.830> great<00:20:22.920> thing<00:20:23.160> about 00:20:23.240 --> 00:20:23.250 align:start position:0% done for them it's a great thing about 00:20:23.250 --> 00:20:25.640 align:start position:0% done for them it's a great thing about working<00:20:23.580> at<00:20:23.640> the<00:20:23.820> foundation<00:20:24.630> is<00:20:24.930> we<00:20:25.470> get<00:20:25.590> to 00:20:25.640 --> 00:20:25.650 align:start position:0% working at the foundation is we get to 00:20:25.650 --> 00:20:28.250 align:start position:0% working at the foundation is we get to share<00:20:25.920> all<00:20:25.980> the<00:20:26.250> fun<00:20:26.490> toys<00:20:26.700> that<00:20:26.970> we<00:20:27.090> make<00:20:28.080> up 00:20:28.250 --> 00:20:28.260 align:start position:0% share all the fun toys that we make up 00:20:28.260 --> 00:20:32.060 align:start position:0% share all the fun toys that we make up and<00:20:29.120> we're<00:20:30.120> we're<00:20:30.750> cranking<00:20:31.170> away<00:20:31.380> so<00:20:31.530> follow 00:20:32.060 --> 00:20:32.070 align:start position:0% and we're we're cranking away so follow 00:20:32.070 --> 00:20:34.490 align:start position:0% and we're we're cranking away so follow us<00:20:32.250> and<00:20:32.520> see<00:20:33.420> what's<00:20:33.630> new<00:20:33.780> it<00:20:34.110> looks<00:20:34.260> like<00:20:34.380> we 00:20:34.490 --> 00:20:34.500 align:start position:0% us and see what's new it looks like we 00:20:34.500 --> 00:20:36.950 align:start position:0% us and see what's new it looks like we don't<00:20:34.590> have<00:20:34.770> time<00:20:34.950> for<00:20:35.010> questions<00:20:35.550> but<00:20:35.960> you 00:20:36.950 --> 00:20:36.960 align:start position:0% don't have time for questions but you 00:20:36.960 --> 00:20:38.720 align:start position:0% don't have time for questions but you can<00:20:37.170> find<00:20:37.560> me<00:20:37.650> on<00:20:37.860> the<00:20:37.950> side<00:20:38.130> or<00:20:38.370> in<00:20:38.400> the<00:20:38.520> hall 00:20:38.720 --> 00:20:38.730 align:start position:0% can find me on the side or in the hall 00:20:38.730 --> 00:20:40.540 align:start position:0% can find me on the side or in the hall I'm<00:20:38.910> happy<00:20:39.330> to<00:20:39.420> talk<00:20:39.570> thanks<00:20:40.110> for<00:20:40.200> your<00:20:40.260> time 00:20:40.540 --> 00:20:40.550 align:start position:0% I'm happy to talk thanks for your time 00:20:40.550 --> 00:20:49.670 align:start position:0% I'm happy to talk thanks for your time [Applause] 00:20:49.670 --> 00:20:49.680 align:start position:0% 00:20:49.680 --> 00:20:51.740 align:start position:0% you