WEBVTT Kind: captions Language: en 00:00:00.000 --> 00:00:11.070 align:start position:0% [Music] 00:00:11.070 --> 00:00:11.080 align:start position:0% [Music] 00:00:11.080 --> 00:00:12.950 align:start position:0% [Music] yeah<00:00:11.280> so<00:00:11.480> what<00:00:11.599> we're<00:00:11.840> talking<00:00:12.040> about<00:00:12.200> now<00:00:12.480> is 00:00:12.950 --> 00:00:12.960 align:start position:0% yeah so what we're talking about now is 00:00:12.960 --> 00:00:15.189 align:start position:0% yeah so what we're talking about now is is<00:00:13.160> the<00:00:13.639> is<00:00:13.759> the<00:00:13.880> ethereum<00:00:14.320> white<00:00:14.519> cin 00:00:15.189 --> 00:00:15.199 align:start position:0% is the is the ethereum white cin 00:00:15.199 --> 00:00:18.710 align:start position:0% is the is the ethereum white cin protocol<00:00:16.320> so<00:00:17.320> for<00:00:18.080> just<00:00:18.240> to<00:00:18.400> give<00:00:18.560> an 00:00:18.710 --> 00:00:18.720 align:start position:0% protocol so for just to give an 00:00:18.720 --> 00:00:20.590 align:start position:0% protocol so for just to give an introduction<00:00:19.279> to<00:00:19.520> why<00:00:19.680> you<00:00:19.920> like<00:00:20.119> clients<00:00:20.400> are 00:00:20.590 --> 00:00:20.600 align:start position:0% introduction to why you like clients are 00:00:20.600 --> 00:00:23.630 align:start position:0% introduction to why you like clients are needed<00:00:21.439> I<00:00:21.600> guess<00:00:22.039> uh<00:00:22.760> the<00:00:22.920> important<00:00:23.320> thing 00:00:23.630 --> 00:00:23.640 align:start position:0% needed I guess uh the important thing 00:00:23.640 --> 00:00:25.150 align:start position:0% needed I guess uh the important thing here<00:00:23.880> is<00:00:24.119> that<00:00:24.279> we<00:00:24.359> are<00:00:24.519> dealing<00:00:24.920> with 00:00:25.150 --> 00:00:25.160 align:start position:0% here is that we are dealing with 00:00:25.160 --> 00:00:27.669 align:start position:0% here is that we are dealing with distribut<00:00:25.640> with<00:00:25.840> distributed<00:00:26.359> consensus<00:00:27.199> and 00:00:27.669 --> 00:00:27.679 align:start position:0% distribut with distributed consensus and 00:00:27.679 --> 00:00:29.429 align:start position:0% distribut with distributed consensus and we're<00:00:27.840> dealing<00:00:28.240> with<00:00:28.400> a<00:00:28.560> system<00:00:28.960> where<00:00:29.199> every 00:00:29.429 --> 00:00:29.439 align:start position:0% we're dealing with a system where every 00:00:29.439 --> 00:00:31.429 align:start position:0% we're dealing with a system where every full<00:00:29.720> no<00:00:30.080> has<00:00:30.199> to<00:00:30.400> process<00:00:30.800> every<00:00:31.000> single 00:00:31.429 --> 00:00:31.439 align:start position:0% full no has to process every single 00:00:31.439 --> 00:00:33.790 align:start position:0% full no has to process every single transaction<00:00:32.439> so<00:00:32.920> you<00:00:33.040> know<00:00:33.280> right<00:00:33.440> now<00:00:33.640> with 00:00:33.790 --> 00:00:33.800 align:start position:0% transaction so you know right now with 00:00:33.800 --> 00:00:35.270 align:start position:0% transaction so you know right now with something<00:00:34.040> like<00:00:34.200> Bitcoin<00:00:34.559> It's<00:00:34.719> relatively 00:00:35.270 --> 00:00:35.280 align:start position:0% something like Bitcoin It's relatively 00:00:35.280 --> 00:00:36.990 align:start position:0% something like Bitcoin It's relatively fine<00:00:35.600> one<00:00:35.800> transaction<00:00:36.239> in<00:00:36.280> a<00:00:36.440> second<00:00:36.719> anyone 00:00:36.990 --> 00:00:37.000 align:start position:0% fine one transaction in a second anyone 00:00:37.000 --> 00:00:39.350 align:start position:0% fine one transaction in a second anyone can<00:00:37.160> do<00:00:37.360> it<00:00:38.040> even<00:00:38.239> although<00:00:38.840> although<00:00:39.079> you<00:00:39.200> do 00:00:39.350 --> 00:00:39.360 align:start position:0% can do it even although although you do 00:00:39.360 --> 00:00:41.750 align:start position:0% can do it even although although you do need<00:00:39.480> to<00:00:39.760> download<00:00:40.120> about<00:00:40.320> 20<00:00:40.559> GB<00:00:41.000> of<00:00:41.120> stuff<00:00:41.640> of 00:00:41.750 --> 00:00:41.760 align:start position:0% need to download about 20 GB of stuff of 00:00:41.760 --> 00:00:43.350 align:start position:0% need to download about 20 GB of stuff of stuff<00:00:42.000> by<00:00:42.160> now<00:00:42.360> which<00:00:42.520> is<00:00:42.680> a<00:00:42.920> which<00:00:43.039> is<00:00:43.160> a 00:00:43.350 --> 00:00:43.360 align:start position:0% stuff by now which is a which is a 00:00:43.360 --> 00:00:45.670 align:start position:0% stuff by now which is a which is a problem<00:00:44.200> now<00:00:44.360> with<00:00:44.520> something<00:00:44.760> like<00:00:44.920> ethereum 00:00:45.670 --> 00:00:45.680 align:start position:0% problem now with something like ethereum 00:00:45.680 --> 00:00:47.069 align:start position:0% problem now with something like ethereum you<00:00:45.800> know<00:00:46.000> in<00:00:46.120> some<00:00:46.280> ways<00:00:46.440> our<00:00:46.600> protocol<00:00:46.960> is 00:00:47.069 --> 00:00:47.079 align:start position:0% you know in some ways our protocol is 00:00:47.079 --> 00:00:48.430 align:start position:0% you know in some ways our protocol is more<00:00:47.239> efficient<00:00:47.600> in<00:00:47.719> some<00:00:47.879> ways<00:00:48.039> it's<00:00:48.239> less 00:00:48.430 --> 00:00:48.440 align:start position:0% more efficient in some ways it's less 00:00:48.440 --> 00:00:49.590 align:start position:0% more efficient in some ways it's less efficient<00:00:48.840> because<00:00:49.000> we<00:00:49.079> have<00:00:49.160> to<00:00:49.280> store<00:00:49.480> a 00:00:49.590 --> 00:00:49.600 align:start position:0% efficient because we have to store a 00:00:49.600 --> 00:00:52.910 align:start position:0% efficient because we have to store a bunch<00:00:49.800> more<00:00:50.039> stuff<00:00:50.960> but<00:00:51.680> if<00:00:51.840> scalability<00:00:52.600> get 00:00:52.910 --> 00:00:52.920 align:start position:0% bunch more stuff but if scalability get 00:00:52.920 --> 00:00:55.110 align:start position:0% bunch more stuff but if scalability get if<00:00:53.280> usage<00:00:53.719> gets<00:00:53.960> to<00:00:54.079> any<00:00:54.280> significant<00:00:54.760> points 00:00:55.110 --> 00:00:55.120 align:start position:0% if usage gets to any significant points 00:00:55.120 --> 00:00:56.430 align:start position:0% if usage gets to any significant points if<00:00:55.239> you<00:00:55.399> imagine<00:00:55.680> we<00:00:55.840> have<00:00:55.960> something<00:00:56.199> like<00:00:56.320> a 00:00:56.430 --> 00:00:56.440 align:start position:0% if you imagine we have something like a 00:00:56.440 --> 00:00:59.389 align:start position:0% if you imagine we have something like a th<00:00:56.719> transactions<00:00:57.239> a<00:00:57.399> second<00:00:58.399> then<00:00:59.000> you<00:00:59.120> know 00:00:59.389 --> 00:00:59.399 align:start position:0% th transactions a second then you know 00:00:59.399 --> 00:01:01.110 align:start position:0% th transactions a second then you know what<00:01:00.039> the<00:01:00.160> amount<00:01:00.359> of<00:01:00.519> resources<00:01:00.960> that<00:01:01.079> it 00:01:01.110 --> 00:01:01.120 align:start position:0% what the amount of resources that it 00:01:01.120 --> 00:01:02.549 align:start position:0% what the amount of resources that it will<00:01:01.280> take<00:01:01.440> to<00:01:01.559> run<00:01:01.719> a<00:01:01.920> full<00:01:02.120> Noe<00:01:02.320> on<00:01:02.440> the 00:01:02.549 --> 00:01:02.559 align:start position:0% will take to run a full Noe on the 00:01:02.559 --> 00:01:05.670 align:start position:0% will take to run a full Noe on the network<00:01:03.119> is<00:01:04.119> 100<00:01:04.320> to<00:01:04.640> 200<00:01:04.879> megabytes<00:01:05.320> per<00:01:05.439> hour 00:01:05.670 --> 00:01:05.680 align:start position:0% network is 100 to 200 megabytes per hour 00:01:05.680 --> 00:01:07.950 align:start position:0% network is 100 to 200 megabytes per hour just<00:01:05.880> processing<00:01:06.479> transactions<00:01:07.479> assuming 00:01:07.950 --> 00:01:07.960 align:start position:0% just processing transactions assuming 00:01:07.960 --> 00:01:09.710 align:start position:0% just processing transactions assuming 10%<00:01:08.400> of<00:01:08.520> those<00:01:08.680> transactions<00:01:09.200> increase<00:01:09.520> the 00:01:09.710 --> 00:01:09.720 align:start position:0% 10% of those transactions increase the 00:01:09.720 --> 00:01:11.270 align:start position:0% 10% of those transactions increase the state<00:01:10.159> which<00:01:10.280> is<00:01:10.479> about<00:01:10.759> accurate<00:01:11.080> for 00:01:11.270 --> 00:01:11.280 align:start position:0% state which is about accurate for 00:01:11.280 --> 00:01:13.230 align:start position:0% state which is about accurate for Bitcoin<00:01:11.960> that's<00:01:12.080> a<00:01:12.280> gigabyte<00:01:12.680> of<00:01:12.799> hard<00:01:13.000> disk 00:01:13.230 --> 00:01:13.240 align:start position:0% Bitcoin that's a gigabyte of hard disk 00:01:13.240 --> 00:01:15.749 align:start position:0% Bitcoin that's a gigabyte of hard disk space<00:01:13.520> every<00:01:13.720> 2<00:01:13.880> or<00:01:14.000> 4<00:01:14.280> days<00:01:15.080> thousand<00:01:15.439> gas 00:01:15.749 --> 00:01:15.759 align:start position:0% space every 2 or 4 days thousand gas 00:01:15.759 --> 00:01:17.429 align:start position:0% space every 2 or 4 days thousand gas transaction<00:01:16.360> that's<00:01:16.520> a<00:01:16.640> million<00:01:17.080> gas<00:01:17.280> a 00:01:17.429 --> 00:01:17.439 align:start position:0% transaction that's a million gas a 00:01:17.439 --> 00:01:20.109 align:start position:0% transaction that's a million gas a second<00:01:18.159> I<00:01:18.320> believe<00:01:18.759> that's<00:01:19.000> pretty<00:01:19.200> much<00:01:19.640> 100% 00:01:20.109 --> 00:01:20.119 align:start position:0% second I believe that's pretty much 100% 00:01:20.119 --> 00:01:23.789 align:start position:0% second I believe that's pretty much 100% of<00:01:20.640> go<00:01:20.759> ethereum<00:01:21.159> can<00:01:21.280> do<00:01:21.520> right<00:01:21.720> now<00:01:22.720> if<00:01:22.920> not 00:01:23.789 --> 00:01:23.799 align:start position:0% of go ethereum can do right now if not 00:01:23.799 --> 00:01:27.069 align:start position:0% of go ethereum can do right now if not more<00:01:24.799> yeah<00:01:25.720> we<00:01:25.840> will<00:01:26.040> have<00:01:26.520> just<00:01:26.759> en<00:01:26.880> time 00:01:27.069 --> 00:01:27.079 align:start position:0% more yeah we will have just en time 00:01:27.079 --> 00:01:33.069 align:start position:0% more yeah we will have just en time compilation<00:01:27.479> of<00:01:27.600> that<00:01:27.759> point<00:01:27.960> of<00:01:28.159> course<00:01:29.159> sure 00:01:33.069 --> 00:01:33.079 align:start position:0% 00:01:33.079 --> 00:01:36.109 align:start position:0% um<00:01:34.079> so<00:01:34.640> ultimately<00:01:35.200> it's<00:01:35.439> kind<00:01:35.560> of<00:01:35.720> important 00:01:36.109 --> 00:01:36.119 align:start position:0% um so ultimately it's kind of important 00:01:36.119 --> 00:01:39.310 align:start position:0% um so ultimately it's kind of important that<00:01:36.280> for<00:01:37.000> um<00:01:37.320> decentralized 00:01:39.310 --> 00:01:39.320 align:start position:0% that for um decentralized 00:01:39.320 --> 00:01:42.350 align:start position:0% that for um decentralized applications<00:01:40.320> uh<00:01:40.439> we<00:01:40.680> have<00:01:41.079> a<00:01:41.479> strategy<00:01:42.159> for 00:01:42.350 --> 00:01:42.360 align:start position:0% applications uh we have a strategy for 00:01:42.360 --> 00:01:45.709 align:start position:0% applications uh we have a strategy for using<00:01:42.680> these<00:01:42.880> things<00:01:43.240> on<00:01:43.520> mobile<00:01:43.880> devices<00:01:44.840> the 00:01:45.709 --> 00:01:45.719 align:start position:0% using these things on mobile devices the 00:01:45.719 --> 00:01:48.590 align:start position:0% using these things on mobile devices the uh<00:01:46.719> the<00:01:46.880> general<00:01:47.240> idea<00:01:47.600> is<00:01:47.799> to<00:01:48.000> replace<00:01:48.439> so 00:01:48.590 --> 00:01:48.600 align:start position:0% uh the general idea is to replace so 00:01:48.600 --> 00:01:50.230 align:start position:0% uh the general idea is to replace so many<00:01:48.960> massively<00:01:49.280> multi-user<00:01:49.840> applications 00:01:50.230 --> 00:01:50.240 align:start position:0% many massively multi-user applications 00:01:50.240 --> 00:01:51.990 align:start position:0% many massively multi-user applications are<00:01:50.399> things<00:01:50.600> we<00:01:50.719> tend<00:01:50.840> to<00:01:50.920> use<00:01:51.079> the<00:01:51.240> web<00:01:51.439> for 00:01:51.990 --> 00:01:52.000 align:start position:0% are things we tend to use the web for 00:01:52.000 --> 00:01:54.389 align:start position:0% are things we tend to use the web for that<00:01:52.399> uh<00:01:52.920> these<00:01:53.159> devices<00:01:53.479> are<00:01:53.600> going<00:01:53.719> to<00:01:53.799> be<00:01:54.280> uh 00:01:54.389 --> 00:01:54.399 align:start position:0% that uh these devices are going to be uh 00:01:54.399 --> 00:01:55.870 align:start position:0% that uh these devices are going to be uh super<00:01:54.719> important<00:01:55.079> for<00:01:55.280> actually<00:01:55.520> providing 00:01:55.870 --> 00:01:55.880 align:start position:0% super important for actually providing 00:01:55.880 --> 00:01:57.389 align:start position:0% super important for actually providing people<00:01:56.159> with<00:01:56.320> what<00:01:56.439> they 00:01:57.389 --> 00:01:57.399 align:start position:0% people with what they 00:01:57.399 --> 00:02:01.510 align:start position:0% people with what they want<00:01:58.399> um<00:01:59.399> so<00:01:59.920> we<00:02:00.079> have<00:02:00.240> two<00:02:00.520> problems<00:02:01.320> the 00:02:01.510 --> 00:02:01.520 align:start position:0% want um so we have two problems the 00:02:01.520 --> 00:02:06.429 align:start position:0% want um so we have two problems the first<00:02:01.880> is<00:02:03.079> um<00:02:04.079> given<00:02:04.680> that<00:02:05.119> a<00:02:05.799> uh<00:02:05.920> a<00:02:06.079> like 00:02:06.429 --> 00:02:06.439 align:start position:0% first is um given that a uh a like 00:02:06.439 --> 00:02:09.229 align:start position:0% first is um given that a uh a like client<00:02:07.439> um<00:02:07.920> knows<00:02:08.280> very<00:02:08.520> little<00:02:08.920> about<00:02:09.080> the 00:02:09.229 --> 00:02:09.239 align:start position:0% client um knows very little about the 00:02:09.239 --> 00:02:11.229 align:start position:0% client um knows very little about the blockchain<00:02:09.679> because<00:02:09.840> it<00:02:09.959> stores<00:02:10.479> very<00:02:10.679> little 00:02:11.229 --> 00:02:11.239 align:start position:0% blockchain because it stores very little 00:02:11.239 --> 00:02:14.949 align:start position:0% blockchain because it stores very little probably<00:02:11.640> only<00:02:11.959> the<00:02:12.280> headers<00:02:13.280> um<00:02:13.879> how<00:02:14.480> does<00:02:14.680> it 00:02:14.949 --> 00:02:14.959 align:start position:0% probably only the headers um how does it 00:02:14.959 --> 00:02:16.710 align:start position:0% probably only the headers um how does it find<00:02:15.239> out<00:02:15.480> about<00:02:15.879> events<00:02:16.200> that<00:02:16.280> are<00:02:16.440> going<00:02:16.599> on 00:02:16.710 --> 00:02:16.720 align:start position:0% find out about events that are going on 00:02:16.720 --> 00:02:18.190 align:start position:0% find out about events that are going on in<00:02:16.800> the<00:02:16.920> blockchain<00:02:17.319> that<00:02:17.440> the<00:02:17.560> decentralized 00:02:18.190 --> 00:02:18.200 align:start position:0% in the blockchain that the decentralized 00:02:18.200 --> 00:02:20.110 align:start position:0% in the blockchain that the decentralized application<00:02:18.680> might<00:02:18.840> be<00:02:19.000> interested<00:02:19.360> in<00:02:19.959> the 00:02:20.110 --> 00:02:20.120 align:start position:0% application might be interested in the 00:02:20.120 --> 00:02:22.110 align:start position:0% application might be interested in the second<00:02:20.480> is<00:02:21.040> assuming<00:02:21.440> that<00:02:21.560> it<00:02:21.680> now<00:02:21.840> knows 00:02:22.110 --> 00:02:22.120 align:start position:0% second is assuming that it now knows 00:02:22.120 --> 00:02:23.309 align:start position:0% second is assuming that it now knows about<00:02:22.360> these<00:02:22.519> events<00:02:22.840> perhaps<00:02:23.080> it's<00:02:23.200> a 00:02:23.309 --> 00:02:23.319 align:start position:0% about these events perhaps it's a 00:02:23.319 --> 00:02:24.830 align:start position:0% about these events perhaps it's a transaction<00:02:23.959> perhaps<00:02:24.200> it's<00:02:24.319> a<00:02:24.440> particular 00:02:24.830 --> 00:02:24.840 align:start position:0% transaction perhaps it's a particular 00:02:24.840 --> 00:02:26.990 align:start position:0% transaction perhaps it's a particular execution<00:02:25.280> and<00:02:25.360> a<00:02:25.519> particular<00:02:25.879> contract<00:02:26.800> um 00:02:26.990 --> 00:02:27.000 align:start position:0% execution and a particular contract um 00:02:27.000 --> 00:02:29.430 align:start position:0% execution and a particular contract um how<00:02:27.160> does<00:02:27.319> it<00:02:27.560> be<00:02:28.000> how<00:02:28.120> does<00:02:28.239> it<00:02:28.360> be<00:02:28.519> certain 00:02:29.430 --> 00:02:29.440 align:start position:0% how does it be how does it be certain 00:02:29.440 --> 00:02:32.910 align:start position:0% how does it be how does it be certain that<00:02:30.280> this<00:02:30.480> information<00:02:31.040> is<00:02:31.200> actually<00:02:31.920> true 00:02:32.910 --> 00:02:32.920 align:start position:0% that this information is actually true 00:02:32.920 --> 00:02:35.309 align:start position:0% that this information is actually true so<00:02:33.160> just<00:02:33.280> to<00:02:33.599> give<00:02:33.720> an<00:02:33.879> introduction<00:02:34.440> to<00:02:35.160> the 00:02:35.309 --> 00:02:35.319 align:start position:0% so just to give an introduction to the 00:02:35.319 --> 00:02:37.670 align:start position:0% so just to give an introduction to the fundamental<00:02:35.879> theory<00:02:36.200> behind<00:02:36.480> white<00:02:36.760> clients 00:02:37.670 --> 00:02:37.680 align:start position:0% fundamental theory behind white clients 00:02:37.680 --> 00:02:39.309 align:start position:0% fundamental theory behind white clients everything<00:02:38.080> is<00:02:38.280> based<00:02:38.480> on<00:02:38.680> this<00:02:38.800> wonderful 00:02:39.309 --> 00:02:39.319 align:start position:0% everything is based on this wonderful 00:02:39.319 --> 00:02:41.110 align:start position:0% everything is based on this wonderful construction<00:02:39.959> invented<00:02:40.319> by<00:02:40.480> Ralph<00:02:40.680> Merkel<00:02:41.040> in 00:02:41.110 --> 00:02:41.120 align:start position:0% construction invented by Ralph Merkel in 00:02:41.120 --> 00:02:43.869 align:start position:0% construction invented by Ralph Merkel in the<00:02:41.200> 1970s<00:02:41.920> Merkel<00:02:42.319> trees<00:02:43.319> so<00:02:43.480> the<00:02:43.599> idea 00:02:43.869 --> 00:02:43.879 align:start position:0% the 1970s Merkel trees so the idea 00:02:43.879 --> 00:02:45.350 align:start position:0% the 1970s Merkel trees so the idea behind<00:02:44.040> a<00:02:44.159> Merkel<00:02:44.480> tree<00:02:44.720> is<00:02:44.800> you<00:02:44.959> arrange 00:02:45.350 --> 00:02:45.360 align:start position:0% behind a Merkel tree is you arrange 00:02:45.360 --> 00:02:47.030 align:start position:0% behind a Merkel tree is you arrange thata<00:02:45.800> in<00:02:45.879> a<00:02:46.000> kind<00:02:46.120> of<00:02:46.239> tree<00:02:46.519> structure<00:02:46.920> where 00:02:47.030 --> 00:02:47.040 align:start position:0% thata in a kind of tree structure where 00:02:47.040 --> 00:02:48.830 align:start position:0% thata in a kind of tree structure where you<00:02:47.159> have<00:02:47.280> all<00:02:47.400> the<00:02:47.560> little<00:02:48.239> little<00:02:48.440> nodes<00:02:48.720> you 00:02:48.830 --> 00:02:48.840 align:start position:0% you have all the little little nodes you 00:02:48.840 --> 00:02:50.229 align:start position:0% you have all the little little nodes you know<00:02:48.959> keys<00:02:49.200> and<00:02:49.360> values<00:02:49.640> at<00:02:49.760> the<00:02:49.879> bottom<00:02:50.120> and 00:02:50.229 --> 00:02:50.239 align:start position:0% know keys and values at the bottom and 00:02:50.239 --> 00:02:51.670 align:start position:0% know keys and values at the bottom and then<00:02:50.319> you<00:02:50.440> take<00:02:50.560> a<00:02:50.680> few<00:02:50.800> nodes<00:02:51.080> to<00:02:51.200> make<00:02:51.319> a<00:02:51.440> hash 00:02:51.670 --> 00:02:51.680 align:start position:0% then you take a few nodes to make a hash 00:02:51.680 --> 00:02:53.589 align:start position:0% then you take a few nodes to make a hash of<00:02:51.840> them<00:02:52.400> then<00:02:52.480> you<00:02:52.640> take<00:02:53.080> and<00:02:53.239> then<00:02:53.480> that's 00:02:53.589 --> 00:02:53.599 align:start position:0% of them then you take and then that's 00:02:53.599 --> 00:02:54.990 align:start position:0% of them then you take and then that's the<00:02:53.720> next<00:02:54.000> level<00:02:54.280> and<00:02:54.360> then<00:02:54.480> you<00:02:54.560> take<00:02:54.680> a<00:02:54.800> few 00:02:54.990 --> 00:02:55.000 align:start position:0% the next level and then you take a few 00:02:55.000 --> 00:02:56.910 align:start position:0% the next level and then you take a few hashes<00:02:55.280> and<00:02:55.400> make<00:02:55.560> a<00:02:55.640> hash<00:02:55.879> of<00:02:56.080> those<00:02:56.640> and<00:02:56.760> it 00:02:56.910 --> 00:02:56.920 align:start position:0% hashes and make a hash of those and it 00:02:56.920 --> 00:02:58.390 align:start position:0% hashes and make a hash of those and it all<00:02:57.040> sort<00:02:57.239> of<00:02:57.360> bubbles<00:02:57.680> up<00:02:57.879> until<00:02:58.080> we<00:02:58.200> have<00:02:58.319> a 00:02:58.390 --> 00:02:58.400 align:start position:0% all sort of bubbles up until we have a 00:02:58.400 --> 00:03:00.550 align:start position:0% all sort of bubbles up until we have a single<00:02:58.680> rude<00:02:58.959> hash<00:02:59.200> at<00:02:59.360> the<00:02:59.519> top<00:03:00.200> and<00:03:00.319> you<00:03:00.400> can 00:03:00.550 --> 00:03:00.560 align:start position:0% single rude hash at the top and you can 00:03:00.560 --> 00:03:01.990 align:start position:0% single rude hash at the top and you can think<00:03:00.680> of<00:03:00.800> the<00:03:00.920> root<00:03:01.200> hash<00:03:01.440> as<00:03:01.640> kind<00:03:01.760> of 00:03:01.990 --> 00:03:02.000 align:start position:0% think of the root hash as kind of 00:03:02.000 --> 00:03:04.070 align:start position:0% think of the root hash as kind of representing<00:03:02.640> the<00:03:02.760> entire<00:03:03.120> tree<00:03:03.720> so<00:03:03.879> there's 00:03:04.070 --> 00:03:04.080 align:start position:0% representing the entire tree so there's 00:03:04.080 --> 00:03:06.149 align:start position:0% representing the entire tree so there's no<00:03:04.239> way<00:03:04.360> to<00:03:04.519> change<00:03:04.879> a<00:03:05.000> single<00:03:05.400> any<00:03:05.720> anything 00:03:06.149 --> 00:03:06.159 align:start position:0% no way to change a single any anything 00:03:06.159 --> 00:03:07.910 align:start position:0% no way to change a single any anything whatsoever<00:03:06.640> about<00:03:06.879> the<00:03:07.040> tree<00:03:07.599> without 00:03:07.910 --> 00:03:07.920 align:start position:0% whatsoever about the tree without 00:03:07.920 --> 00:03:09.149 align:start position:0% whatsoever about the tree without creating<00:03:08.280> changes<00:03:08.640> that<00:03:08.799> eventually 00:03:09.149 --> 00:03:09.159 align:start position:0% creating changes that eventually 00:03:09.159 --> 00:03:11.789 align:start position:0% creating changes that eventually propagate<00:03:09.560> up<00:03:09.680> the<00:03:09.799> tree<00:03:10.080> and<00:03:10.680> and<00:03:11.680> and 00:03:11.789 --> 00:03:11.799 align:start position:0% propagate up the tree and and and 00:03:11.799 --> 00:03:13.470 align:start position:0% propagate up the tree and and and ultimately<00:03:12.239> lead<00:03:12.400> to<00:03:12.519> a<00:03:12.599> change<00:03:12.799> in<00:03:12.920> the<00:03:13.360> in 00:03:13.470 --> 00:03:13.480 align:start position:0% ultimately lead to a change in the in 00:03:13.480 --> 00:03:15.110 align:start position:0% ultimately lead to a change in the in the<00:03:13.599> root<00:03:14.040> so<00:03:14.159> if<00:03:14.280> the<00:03:14.360> root<00:03:14.560> is<00:03:14.720> inside<00:03:15.000> the 00:03:15.110 --> 00:03:15.120 align:start position:0% the root so if the root is inside the 00:03:15.120 --> 00:03:16.550 align:start position:0% the root so if the root is inside the header<00:03:15.560> then<00:03:15.720> once<00:03:15.920> you<00:03:16.080> validated<00:03:16.480> the 00:03:16.550 --> 00:03:16.560 align:start position:0% header then once you validated the 00:03:16.560 --> 00:03:17.750 align:start position:0% header then once you validated the header<00:03:16.840> you've<00:03:16.959> sort<00:03:17.120> of<00:03:17.239> implicitly 00:03:17.750 --> 00:03:17.760 align:start position:0% header you've sort of implicitly 00:03:17.760 --> 00:03:20.670 align:start position:0% header you've sort of implicitly validated<00:03:18.159> the<00:03:18.280> entire<00:03:18.720> tree<00:03:19.720> so<00:03:20.200> idea<00:03:20.519> with 00:03:20.670 --> 00:03:20.680 align:start position:0% validated the entire tree so idea with 00:03:20.680 --> 00:03:22.710 align:start position:0% validated the entire tree so idea with like<00:03:20.879> clients<00:03:21.400> is<00:03:21.680> you<00:03:21.840> only<00:03:22.200> download<00:03:22.599> you 00:03:22.710 --> 00:03:22.720 align:start position:0% like clients is you only download you 00:03:22.720 --> 00:03:25.110 align:start position:0% like clients is you only download you only<00:03:23.080> download<00:03:23.840> the<00:03:23.959> block<00:03:24.239> header<00:03:24.480> Chain<00:03:24.840> by 00:03:25.110 --> 00:03:25.120 align:start position:0% only download the block header Chain by 00:03:25.120 --> 00:03:27.710 align:start position:0% only download the block header Chain by default<00:03:26.120> and<00:03:26.480> uh<00:03:26.599> if<00:03:26.720> you<00:03:26.879> need<00:03:27.200> if<00:03:27.280> you<00:03:27.440> need 00:03:27.710 --> 00:03:27.720 align:start position:0% default and uh if you need if you need 00:03:27.720 --> 00:03:29.390 align:start position:0% default and uh if you need if you need data<00:03:28.239> then<00:03:28.360> you<00:03:28.519> just<00:03:28.760> then<00:03:28.879> you<00:03:29.000> just<00:03:29.120> fetch 00:03:29.390 --> 00:03:29.400 align:start position:0% data then you just then you just fetch 00:03:29.400 --> 00:03:32.589 align:start position:0% data then you just then you just fetch whatever<00:03:29.920> whatever<00:03:30.200> data<00:03:30.439> you<00:03:30.560> want<00:03:31.319> and<00:03:32.319> and 00:03:32.589 --> 00:03:32.599 align:start position:0% whatever whatever data you want and and 00:03:32.599 --> 00:03:35.190 align:start position:0% whatever whatever data you want and and once<00:03:32.920> you<00:03:33.920> once<00:03:34.040> you<00:03:34.239> have<00:03:34.480> that<00:03:34.640> spe<00:03:35.040> that 00:03:35.190 --> 00:03:35.200 align:start position:0% once you once you have that spe that 00:03:35.200 --> 00:03:36.470 align:start position:0% once you once you have that spe that specific<00:03:35.560> set<00:03:35.680> of<00:03:35.840> data<00:03:36.080> you<00:03:36.159> can<00:03:36.319> just 00:03:36.470 --> 00:03:36.480 align:start position:0% specific set of data you can just 00:03:36.480 --> 00:03:38.509 align:start position:0% specific set of data you can just validate<00:03:36.879> it<00:03:37.120> by<00:03:37.599> just<00:03:37.840> making<00:03:38.040> sure<00:03:38.239> that<00:03:38.360> the 00:03:38.509 --> 00:03:38.519 align:start position:0% validate it by just making sure that the 00:03:38.519 --> 00:03:42.030 align:start position:0% validate it by just making sure that the hashes<00:03:38.959> hashes<00:03:39.319> match<00:03:39.519> all<00:03:39.640> the<00:03:39.760> way 00:03:42.030 --> 00:03:42.040 align:start position:0% 00:03:42.040 --> 00:03:46.509 align:start position:0% up<00:03:43.319> so<00:03:44.319> basic<00:03:44.680> idea<00:03:45.239> is<00:03:45.519> that<00:03:45.920> you<00:03:46.040> can<00:03:46.280> think 00:03:46.509 --> 00:03:46.519 align:start position:0% up so basic idea is that you can think 00:03:46.519 --> 00:03:49.429 align:start position:0% up so basic idea is that you can think of<00:03:47.519> so<00:03:47.680> you<00:03:47.799> can<00:03:48.000> think<00:03:48.159> of<00:03:48.360> a<00:03:48.599> proof<00:03:48.920> of<00:03:49.120> some 00:03:49.429 --> 00:03:49.439 align:start position:0% of so you can think of a proof of some 00:03:49.439 --> 00:03:51.830 align:start position:0% of so you can think of a proof of some of<00:03:49.840> of<00:03:50.000> something<00:03:50.400> as<00:03:50.599> being<00:03:51.200> the<00:03:51.400> subset<00:03:51.760> of 00:03:51.830 --> 00:03:51.840 align:start position:0% of of something as being the subset of 00:03:51.840 --> 00:03:53.949 align:start position:0% of of something as being the subset of tre<00:03:52.159> nodes<00:03:52.480> that<00:03:52.560> are<00:03:52.720> involved<00:03:53.400> involved<00:03:53.760> in 00:03:53.949 --> 00:03:53.959 align:start position:0% tre nodes that are involved involved in 00:03:53.959 --> 00:03:55.949 align:start position:0% tre nodes that are involved involved in accessing<00:03:54.319> or<00:03:54.519> processing<00:03:55.000> it<00:03:55.599> so<00:03:55.720> if<00:03:55.840> you 00:03:55.949 --> 00:03:55.959 align:start position:0% accessing or processing it so if you 00:03:55.959 --> 00:03:58.869 align:start position:0% accessing or processing it so if you want<00:03:56.200> a<00:03:56.400> proof<00:03:56.879> that<00:03:57.400> you<00:03:57.560> know<00:03:57.920> if<00:03:58.000> you<00:03:58.120> want<00:03:58.720> a 00:03:58.869 --> 00:03:58.879 align:start position:0% want a proof that you know if you want a 00:03:58.879 --> 00:04:00.309 align:start position:0% want a proof that you know if you want a proof<00:03:59.159> that<00:03:59.319> some<00:03:59.480> particular<00:03:59.920> that<00:04:00.040> you<00:04:00.159> know 00:04:00.309 --> 00:04:00.319 align:start position:0% proof that some particular that you know 00:04:00.319 --> 00:04:01.670 align:start position:0% proof that some particular that you know some<00:04:00.519> particular<00:04:00.920> account<00:04:01.280> has<00:04:01.480> some 00:04:01.670 --> 00:04:01.680 align:start position:0% some particular account has some 00:04:01.680 --> 00:04:04.030 align:start position:0% some particular account has some particular<00:04:02.120> State<00:04:03.000> then<00:04:03.159> you<00:04:03.319> take<00:04:03.519> the<00:04:03.680> nodes 00:04:04.030 --> 00:04:04.040 align:start position:0% particular State then you take the nodes 00:04:04.040 --> 00:04:05.710 align:start position:0% particular State then you take the nodes that<00:04:04.120> you<00:04:04.519> the<00:04:04.640> nodes<00:04:04.879> in<00:04:05.000> the<00:04:05.120> tree<00:04:05.480> that<00:04:05.560> you 00:04:05.710 --> 00:04:05.720 align:start position:0% that you the nodes in the tree that you 00:04:05.720 --> 00:04:08.309 align:start position:0% that you the nodes in the tree that you need<00:04:06.400> to<00:04:06.640> sort<00:04:06.840> of<00:04:07.040> go<00:04:07.280> all<00:04:07.400> the<00:04:07.519> way<00:04:07.760> go<00:04:08.159> all 00:04:08.309 --> 00:04:08.319 align:start position:0% need to sort of go all the way go all 00:04:08.319 --> 00:04:09.830 align:start position:0% need to sort of go all the way go all the<00:04:08.400> way<00:04:08.599> down<00:04:08.720> to<00:04:08.959> that<00:04:09.239> that<00:04:09.360> particular 00:04:09.830 --> 00:04:09.840 align:start position:0% the way down to that that particular 00:04:09.840 --> 00:04:12.429 align:start position:0% the way down to that that particular thing<00:04:10.640> and<00:04:11.360> that's<00:04:11.640> and<00:04:11.760> that<00:04:11.879> set<00:04:12.000> of<00:04:12.120> nodes 00:04:12.429 --> 00:04:12.439 align:start position:0% thing and that's and that set of nodes 00:04:12.439 --> 00:04:13.789 align:start position:0% thing and that's and that set of nodes basically<00:04:12.760> is<00:04:12.879> the<00:04:13.040> proof<00:04:13.439> so<00:04:13.560> the<00:04:13.640> way<00:04:13.720> you 00:04:13.789 --> 00:04:13.799 align:start position:0% basically is the proof so the way you 00:04:13.799 --> 00:04:15.470 align:start position:0% basically is the proof so the way you create<00:04:14.000> a<00:04:14.120> proof<00:04:14.400> is<00:04:14.519> literally<00:04:15.000> this<00:04:15.319> like 00:04:15.470 --> 00:04:15.480 align:start position:0% create a proof is literally this like 00:04:15.480 --> 00:04:16.710 align:start position:0% create a proof is literally this like this<00:04:15.560> is<00:04:15.879> this<00:04:15.959> is<00:04:16.079> how<00:04:16.199> it's<00:04:16.440> actually 00:04:16.710 --> 00:04:16.720 align:start position:0% this is this is how it's actually 00:04:16.720 --> 00:04:18.110 align:start position:0% this is this is how it's actually implemented<00:04:17.120> in<00:04:17.199> the<00:04:17.320> python<00:04:17.600> client<00:04:17.959> right 00:04:18.110 --> 00:04:18.120 align:start position:0% implemented in the python client right 00:04:18.120 --> 00:04:20.629 align:start position:0% implemented in the python client right now<00:04:18.639> you<00:04:19.040> just<00:04:19.440> if<00:04:19.519> you<00:04:19.600> want<00:04:19.720> to<00:04:20.120> prove<00:04:20.440> some 00:04:20.629 --> 00:04:20.639 align:start position:0% now you just if you want to prove some 00:04:20.639 --> 00:04:22.270 align:start position:0% now you just if you want to prove some particular<00:04:21.000> part<00:04:21.120> of<00:04:21.239> an<00:04:21.400> account<00:04:21.639> you<00:04:21.799> just 00:04:22.270 --> 00:04:22.280 align:start position:0% particular part of an account you just 00:04:22.280 --> 00:04:24.189 align:start position:0% particular part of an account you just grab<00:04:22.560> it<00:04:22.919> but<00:04:23.000> you<00:04:23.160> record<00:04:23.479> all<00:04:23.600> the<00:04:23.759> tree<00:04:23.960> noes 00:04:24.189 --> 00:04:24.199 align:start position:0% grab it but you record all the tree noes 00:04:24.199 --> 00:04:25.950 align:start position:0% grab it but you record all the tree noes that<00:04:24.280> you<00:04:24.479> accessed<00:04:25.160> and<00:04:25.280> the<00:04:25.360> way<00:04:25.440> you<00:04:25.560> verify 00:04:25.950 --> 00:04:25.960 align:start position:0% that you accessed and the way you verify 00:04:25.960 --> 00:04:27.830 align:start position:0% that you accessed and the way you verify the<00:04:26.080> proof<00:04:26.360> is<00:04:26.440> that<00:04:26.560> you<00:04:26.680> just<00:04:26.800> sort<00:04:26.960> of<00:04:27.160> run 00:04:27.830 --> 00:04:27.840 align:start position:0% the proof is that you just sort of run 00:04:27.840 --> 00:04:29.550 align:start position:0% the proof is that you just sort of run you<00:04:28.000> just<00:04:28.199> run<00:04:28.440> the<00:04:28.560> same<00:04:28.759> standard<00:04:29.120> algorithm 00:04:29.550 --> 00:04:29.560 align:start position:0% you just run the same standard algorithm 00:04:29.560 --> 00:04:31.510 align:start position:0% you just run the same standard algorithm but<00:04:29.759> using<00:04:30.000> the<00:04:30.160> proof<00:04:30.479> as<00:04:30.560> your<00:04:30.880> as<00:04:31.000> your 00:04:31.510 --> 00:04:31.520 align:start position:0% but using the proof as your as your 00:04:31.520 --> 00:04:34.390 align:start position:0% but using the proof as your as your database<00:04:32.520> so<00:04:33.440> like<00:04:33.600> the<00:04:33.720> nice<00:04:33.919> thing<00:04:34.080> is<00:04:34.280> that 00:04:34.390 --> 00:04:34.400 align:start position:0% database so like the nice thing is that 00:04:34.400 --> 00:04:35.710 align:start position:0% database so like the nice thing is that you<00:04:34.800> with<00:04:34.960> the<00:04:35.039> way<00:04:35.160> the<00:04:35.280> protocol<00:04:35.600> is 00:04:35.710 --> 00:04:35.720 align:start position:0% you with the way the protocol is 00:04:35.720 --> 00:04:36.950 align:start position:0% you with the way the protocol is designed<00:04:36.000> you<00:04:36.120> said<00:04:36.320> a<00:04:36.440> lot<00:04:36.560> of<00:04:36.639> this<00:04:36.800> stuff 00:04:36.950 --> 00:04:36.960 align:start position:0% designed you said a lot of this stuff 00:04:36.960 --> 00:04:38.430 align:start position:0% designed you said a lot of this stuff you<00:04:37.039> just<00:04:37.160> sort<00:04:37.320> of<00:04:37.440> get<00:04:37.680> automatically 00:04:38.430 --> 00:04:38.440 align:start position:0% you just sort of get automatically 00:04:38.440 --> 00:04:40.270 align:start position:0% you just sort of get automatically because<00:04:39.120> everything<00:04:39.440> is<00:04:39.680> based<00:04:39.919> on<00:04:40.080> these 00:04:40.270 --> 00:04:40.280 align:start position:0% because everything is based on these 00:04:40.280 --> 00:04:42.029 align:start position:0% because everything is based on these reverse<00:04:40.639> hash<00:04:40.880> lookups 00:04:42.029 --> 00:04:42.039 align:start position:0% reverse hash lookups 00:04:42.039 --> 00:04:44.629 align:start position:0% reverse hash lookups and<00:04:43.039> you<00:04:43.160> know<00:04:43.400> if<00:04:43.520> you<00:04:43.919> if<00:04:44.000> you<00:04:44.199> assume<00:04:44.520> that 00:04:44.629 --> 00:04:44.639 align:start position:0% and you know if you if you assume that 00:04:44.639 --> 00:04:46.230 align:start position:0% and you know if you if you assume that the<00:04:44.759> hashes<00:04:45.120> that<00:04:45.240> you<00:04:45.360> need<00:04:45.800> that<00:04:46.000> that<00:04:46.080> you 00:04:46.230 --> 00:04:46.240 align:start position:0% the hashes that you need that that you 00:04:46.240 --> 00:04:48.110 align:start position:0% the hashes that you need that that you need<00:04:46.560> to<00:04:46.840> that<00:04:46.919> you<00:04:47.039> need<00:04:47.400> actually<00:04:47.720> already 00:04:48.110 --> 00:04:48.120 align:start position:0% need to that you need actually already 00:04:48.120 --> 00:04:50.430 align:start position:0% need to that you need actually already exist<00:04:48.880> then<00:04:49.000> you<00:04:49.120> can<00:04:49.280> just<00:04:49.600> reuse<00:04:50.000> the<00:04:50.160> exact 00:04:50.430 --> 00:04:50.440 align:start position:0% exist then you can just reuse the exact 00:04:50.440 --> 00:04:51.710 align:start position:0% exist then you can just reuse the exact same<00:04:50.680> code<00:04:50.880> and<00:04:50.960> it's<00:04:51.080> just<00:04:51.199> a<00:04:51.320> matter<00:04:51.520> of 00:04:51.710 --> 00:04:51.720 align:start position:0% same code and it's just a matter of 00:04:51.720 --> 00:04:53.469 align:start position:0% same code and it's just a matter of which<00:04:52.080> you<00:04:52.199> know<00:04:52.360> which<00:04:52.560> hashes<00:04:52.840> do<00:04:52.919> you<00:04:53.039> need 00:04:53.469 --> 00:04:53.479 align:start position:0% which you know which hashes do you need 00:04:53.479 --> 00:04:54.629 align:start position:0% which you know which hashes do you need or<00:04:53.680> which<00:04:53.759> little<00:04:54.039> nodes<00:04:54.240> do<00:04:54.320> you<00:04:54.400> need<00:04:54.520> to 00:04:54.629 --> 00:04:54.639 align:start position:0% or which little nodes do you need to 00:04:54.639 --> 00:04:56.670 align:start position:0% or which little nodes do you need to download<00:04:54.960> to<00:04:55.080> make<00:04:55.160> sure<00:04:55.360> you<00:04:55.520> have 00:04:56.670 --> 00:04:56.680 align:start position:0% download to make sure you have 00:04:56.680 --> 00:05:00.270 align:start position:0% download to make sure you have everything<00:04:57.800> so<00:04:58.800> thing<00:04:59.039> you<00:04:59.160> know<00:04:59.720> in<00:04:59.840> ethereum 00:05:00.270 --> 00:05:00.280 align:start position:0% everything so thing you know in ethereum 00:05:00.280 --> 00:05:02.390 align:start position:0% everything so thing you know in ethereum we<00:05:00.360> have<00:05:00.520> three<00:05:00.680> Merkel<00:05:01.039> trees<00:05:01.919> we<00:05:02.080> have<00:05:02.240> a 00:05:02.390 --> 00:05:02.400 align:start position:0% we have three Merkel trees we have a 00:05:02.400 --> 00:05:04.230 align:start position:0% we have three Merkel trees we have a state<00:05:02.639> tree<00:05:03.120> state<00:05:03.400> tree<00:05:03.600> reords<00:05:04.000> account 00:05:04.230 --> 00:05:04.240 align:start position:0% state tree state tree reords account 00:05:04.240 --> 00:05:07.350 align:start position:0% state tree state tree reords account balances<00:05:04.880> stor<00:05:05.880> storage<00:05:06.479> a<00:05:06.600> little<00:05:07.080> merel 00:05:07.350 --> 00:05:07.360 align:start position:0% balances stor storage a little merel 00:05:07.360 --> 00:05:10.590 align:start position:0% balances stor storage a little merel tree<00:05:07.520> for<00:05:07.600> each<00:05:07.880> account<00:05:08.479> code<00:05:09.240> in<00:05:09.400> 1.1<00:05:10.320> maybe 00:05:10.590 --> 00:05:10.600 align:start position:0% tree for each account code in 1.1 maybe 00:05:10.600 --> 00:05:12.870 align:start position:0% tree for each account code in 1.1 maybe we'll<00:05:10.840> consider<00:05:11.160> we'll<00:05:11.400> consider<00:05:12.120> events<00:05:12.680> so 00:05:12.870 --> 00:05:12.880 align:start position:0% we'll consider we'll consider events so 00:05:12.880 --> 00:05:14.350 align:start position:0% we'll consider we'll consider events so a<00:05:13.039> wait<00:05:13.199> for<00:05:13.400> contracts<00:05:13.800> to<00:05:13.919> sort<00:05:14.080> of<00:05:14.160> do 00:05:14.350 --> 00:05:14.360 align:start position:0% a wait for contracts to sort of do 00:05:14.360 --> 00:05:15.390 align:start position:0% a wait for contracts to sort of do events<00:05:14.639> that<00:05:14.800> event<00:05:15.000> that<00:05:15.120> only<00:05:15.280> get 00:05:15.390 --> 00:05:15.400 align:start position:0% events that event that only get 00:05:15.400 --> 00:05:17.270 align:start position:0% events that event that only get propagated<00:05:15.919> processed<00:05:16.280> in<00:05:16.400> the<00:05:16.479> future<00:05:17.160> and 00:05:17.270 --> 00:05:17.280 align:start position:0% propagated processed in the future and 00:05:17.280 --> 00:05:18.629 align:start position:0% propagated processed in the future and then<00:05:17.520> those<00:05:17.720> events<00:05:17.960> have<00:05:18.080> to<00:05:18.160> be<00:05:18.240> stored<00:05:18.520> in 00:05:18.629 --> 00:05:18.639 align:start position:0% then those events have to be stored in 00:05:18.639 --> 00:05:21.110 align:start position:0% then those events have to be stored in the<00:05:18.759> state<00:05:19.240> in<00:05:19.319> the<00:05:19.639> meantime<00:05:20.639> transaction 00:05:21.110 --> 00:05:21.120 align:start position:0% the state in the meantime transaction 00:05:21.120 --> 00:05:22.590 align:start position:0% the state in the meantime transaction tree<00:05:21.400> just<00:05:21.520> stores<00:05:21.800> all<00:05:21.880> the<00:05:22.000> transactions<00:05:22.479> in 00:05:22.590 --> 00:05:22.600 align:start position:0% tree just stores all the transactions in 00:05:22.600 --> 00:05:24.510 align:start position:0% tree just stores all the transactions in the<00:05:22.759> block<00:05:23.199> so<00:05:23.479> the<00:05:23.600> receip<00:05:23.960> tree<00:05:24.319> that's 00:05:24.510 --> 00:05:24.520 align:start position:0% the block so the receip tree that's 00:05:24.520 --> 00:05:26.550 align:start position:0% the block so the receip tree that's pretty<00:05:24.759> important<00:05:25.160> and<00:05:25.319> we'll<00:05:26.160> talk<00:05:26.400> more 00:05:26.550 --> 00:05:26.560 align:start position:0% pretty important and we'll talk more 00:05:26.560 --> 00:05:28.590 align:start position:0% pretty important and we'll talk more about<00:05:26.840> that<00:05:27.000> later<00:05:27.639> but<00:05:27.800> the<00:05:27.919> idea<00:05:28.319> is<00:05:28.479> that 00:05:28.590 --> 00:05:28.600 align:start position:0% about that later but the idea is that 00:05:28.600 --> 00:05:30.430 align:start position:0% about that later but the idea is that it's<00:05:28.800> sort<00:05:28.960> of<00:05:29.039> store<00:05:29.680> specific<00:05:30.039> results<00:05:30.360> that 00:05:30.430 --> 00:05:30.440 align:start position:0% it's sort of store specific results that 00:05:30.440 --> 00:05:31.629 align:start position:0% it's sort of store specific results that are<00:05:30.560> related<00:05:30.880> to<00:05:31.080> processing<00:05:31.440> each 00:05:31.629 --> 00:05:31.639 align:start position:0% are related to processing each 00:05:31.639 --> 00:05:33.189 align:start position:0% are related to processing each individual 00:05:33.189 --> 00:05:33.199 align:start position:0% individual 00:05:33.199 --> 00:05:35.909 align:start position:0% individual transaction<00:05:34.199> so<00:05:35.120> what<00:05:35.240> do<00:05:35.360> we<00:05:35.479> care<00:05:35.680> about 00:05:35.909 --> 00:05:35.919 align:start position:0% transaction so what do we care about 00:05:35.919 --> 00:05:37.950 align:start position:0% transaction so what do we care about proving<00:05:36.759> or<00:05:36.960> what<00:05:37.080> do<00:05:37.199> we<00:05:37.319> care<00:05:37.520> about<00:05:37.759> light 00:05:37.950 --> 00:05:37.960 align:start position:0% proving or what do we care about light 00:05:37.960 --> 00:05:40.629 align:start position:0% proving or what do we care about light noes<00:05:38.240> being<00:05:38.440> able<00:05:38.639> to<00:05:38.800> securely<00:05:39.400> access<00:05:40.400> um 00:05:40.629 --> 00:05:40.639 align:start position:0% noes being able to securely access um 00:05:40.639 --> 00:05:42.270 align:start position:0% noes being able to securely access um account<00:05:40.960> balance<00:05:41.400> account<00:05:41.639> Nots<00:05:41.960> account 00:05:42.270 --> 00:05:42.280 align:start position:0% account balance account Nots account 00:05:42.280 --> 00:05:45.070 align:start position:0% account balance account Nots account code<00:05:42.880> account<00:05:43.199> storage<00:05:43.639> data<00:05:44.600> whether<00:05:44.800> or<00:05:44.960> not 00:05:45.070 --> 00:05:45.080 align:start position:0% code account storage data whether or not 00:05:45.080 --> 00:05:49.029 align:start position:0% code account storage data whether or not a<00:05:45.199> transaction<00:05:45.680> has<00:05:45.800> been<00:05:46.360> included<00:05:47.759> um<00:05:48.759> so 00:05:49.029 --> 00:05:49.039 align:start position:0% a transaction has been included um so 00:05:49.039 --> 00:05:51.189 align:start position:0% a transaction has been included um so one<00:05:49.240> thing<00:05:49.440> I<00:05:49.600> know<00:05:49.759> I<00:05:49.840> was<00:05:50.000> asked<00:05:50.280> a<00:05:50.360> couple<00:05:51.080> a 00:05:51.189 --> 00:05:51.199 align:start position:0% one thing I know I was asked a couple a 00:05:51.199 --> 00:05:53.230 align:start position:0% one thing I know I was asked a couple a couple<00:05:51.440> days<00:05:51.639> ago<00:05:51.880> is<00:05:52.080> how<00:05:52.199> does<00:05:52.360> a<00:05:52.520> node<00:05:52.840> even 00:05:53.230 --> 00:05:53.240 align:start position:0% couple days ago is how does a node even 00:05:53.240 --> 00:05:55.550 align:start position:0% couple days ago is how does a node even or<00:05:53.440> how<00:05:53.680> does<00:05:54.120> the<00:05:54.280> JavaScript<00:05:54.840> even<00:05:55.120> know 00:05:55.550 --> 00:05:55.560 align:start position:0% or how does the JavaScript even know 00:05:55.560 --> 00:05:57.670 align:start position:0% or how does the JavaScript even know that<00:05:55.960> a<00:05:56.160> particular<00:05:56.600> transaction<00:05:57.160> was<00:05:57.440> was 00:05:57.670 --> 00:05:57.680 align:start position:0% that a particular transaction was was 00:05:57.680 --> 00:05:59.309 align:start position:0% that a particular transaction was was processed<00:05:58.080> so<00:05:58.240> they<00:05:58.360> can<00:05:58.520> start<00:05:58.919> so<00:05:59.120> they<00:05:59.240> can 00:05:59.309 --> 00:05:59.319 align:start position:0% processed so they can start so they can 00:05:59.319 --> 00:06:01.510 align:start position:0% processed so they can start so they can start<00:05:59.639> sending<00:05:59.880> off<00:06:00.039> another<00:06:00.520> transaction 00:06:01.510 --> 00:06:01.520 align:start position:0% start sending off another transaction 00:06:01.520 --> 00:06:04.309 align:start position:0% start sending off another transaction and<00:06:02.479> you<00:06:02.600> know<00:06:02.880> this<00:06:03.360> is<00:06:03.639> one 00:06:04.309 --> 00:06:04.319 align:start position:0% and you know this is one 00:06:04.319 --> 00:06:06.909 align:start position:0% and you know this is one of<00:06:05.319> you<00:06:05.440> know<00:06:05.639> this<00:06:05.880> is<00:06:06.039> something<00:06:06.400> that<00:06:06.560> the 00:06:06.909 --> 00:06:06.919 align:start position:0% of you know this is something that the 00:06:06.919 --> 00:06:08.110 align:start position:0% of you know this is something that the that<00:06:07.000> the<00:06:07.080> white<00:06:07.319> client<00:06:07.599> should<00:06:07.759> be<00:06:07.840> able<00:06:08.000> to 00:06:08.110 --> 00:06:08.120 align:start position:0% that the white client should be able to 00:06:08.120 --> 00:06:10.110 align:start position:0% that the white client should be able to figure<00:06:08.319> out<00:06:08.479> from<00:06:08.599> the<00:06:08.720> blockchain<00:06:09.680> also 00:06:10.110 --> 00:06:10.120 align:start position:0% figure out from the blockchain also 00:06:10.120 --> 00:06:11.749 align:start position:0% figure out from the blockchain also potentially<00:06:10.680> if<00:06:10.759> he<00:06:10.919> wants<00:06:11.160> to<00:06:11.319> if<00:06:11.400> your<00:06:11.560> like 00:06:11.749 --> 00:06:11.759 align:start position:0% potentially if he wants to if your like 00:06:11.759 --> 00:06:13.029 align:start position:0% potentially if he wants to if your like clients<00:06:12.080> wants<00:06:12.319> to<00:06:12.479> start<00:06:12.759> actually 00:06:13.029 --> 00:06:13.039 align:start position:0% clients wants to start actually 00:06:13.039 --> 00:06:14.589 align:start position:0% clients wants to start actually probabilistically<00:06:13.840> validating<00:06:14.319> that<00:06:14.479> a 00:06:14.589 --> 00:06:14.599 align:start position:0% probabilistically validating that a 00:06:14.599 --> 00:06:16.270 align:start position:0% probabilistically validating that a block<00:06:14.919> was<00:06:15.240> that<00:06:15.440> a<00:06:15.599> block<00:06:15.800> was<00:06:15.919> produced 00:06:16.270 --> 00:06:16.280 align:start position:0% block was that a block was produced 00:06:16.280 --> 00:06:19.189 align:start position:0% block was that a block was produced correctly<00:06:16.800> they<00:06:17.000> can<00:06:18.000> they<00:06:18.120> can<00:06:18.280> do<00:06:18.560> that<00:06:18.960> and 00:06:19.189 --> 00:06:19.199 align:start position:0% correctly they can they can do that and 00:06:19.199 --> 00:06:20.510 align:start position:0% correctly they can they can do that and finally<00:06:19.560> a<00:06:19.680> thing<00:06:19.800> that<00:06:20.000> gav<00:06:20.160> will<00:06:20.319> probably 00:06:20.510 --> 00:06:20.520 align:start position:0% finally a thing that gav will probably 00:06:20.520 --> 00:06:22.430 align:start position:0% finally a thing that gav will probably talk<00:06:20.680> more<00:06:20.840> about<00:06:21.120> which<00:06:21.240> is 00:06:22.430 --> 00:06:22.440 align:start position:0% talk more about which is 00:06:22.440 --> 00:06:26.070 align:start position:0% talk more about which is logs<00:06:23.440> so<00:06:24.360> account<00:06:24.720> data<00:06:25.400> we<00:06:25.520> already<00:06:25.800> talked 00:06:26.070 --> 00:06:26.080 align:start position:0% logs so account data we already talked 00:06:26.080 --> 00:06:28.309 align:start position:0% logs so account data we already talked about<00:06:26.360> that<00:06:26.840> prove<00:06:27.199> existence<00:06:27.800> so<00:06:28.160> if<00:06:28.240> you 00:06:28.309 --> 00:06:28.319 align:start position:0% about that prove existence so if you 00:06:28.319 --> 00:06:29.670 align:start position:0% about that prove existence so if you want<00:06:28.440> to<00:06:28.560> fetch<00:06:28.800> account<00:06:29.039> data<00:06:29.199> you<00:06:29.280> just<00:06:29.560> to 00:06:29.670 --> 00:06:29.680 align:start position:0% want to fetch account data you just to 00:06:29.680 --> 00:06:31.990 align:start position:0% want to fetch account data you just to prove<00:06:29.840> an<00:06:30.039> existence<00:06:30.360> of<00:06:30.440> a<00:06:30.560> note<00:06:30.720> in<00:06:30.840> the<00:06:31.000> tree 00:06:31.990 --> 00:06:32.000 align:start position:0% prove an existence of a note in the tree 00:06:32.000 --> 00:06:33.510 align:start position:0% prove an existence of a note in the tree so<00:06:32.240> transaction<00:06:32.720> State 00:06:33.510 --> 00:06:33.520 align:start position:0% so transaction State 00:06:33.520 --> 00:06:35.629 align:start position:0% so transaction State transition<00:06:34.520> is<00:06:34.639> some<00:06:34.800> more<00:06:35.039> complicated 00:06:35.629 --> 00:06:35.639 align:start position:0% transition is some more complicated 00:06:35.639 --> 00:06:37.670 align:start position:0% transition is some more complicated thing<00:06:36.240> but<00:06:36.400> basically<00:06:36.840> if<00:06:36.919> he<00:06:37.039> wants<00:06:37.199> to<00:06:37.360> prove 00:06:37.670 --> 00:06:37.680 align:start position:0% thing but basically if he wants to prove 00:06:37.680 --> 00:06:39.110 align:start position:0% thing but basically if he wants to prove that<00:06:37.800> a<00:06:37.919> particular<00:06:38.319> transaction<00:06:38.840> was 00:06:39.110 --> 00:06:39.120 align:start position:0% that a particular transaction was 00:06:39.120 --> 00:06:41.589 align:start position:0% that a particular transaction was processed<00:06:39.599> or<00:06:39.919> correctly<00:06:40.880> then<00:06:41.000> you<00:06:41.160> take<00:06:41.360> the 00:06:41.589 --> 00:06:41.599 align:start position:0% processed or correctly then you take the 00:06:41.599 --> 00:06:43.909 align:start position:0% processed or correctly then you take the then<00:06:41.759> you<00:06:41.919> take<00:06:42.120> some<00:06:42.240> of<00:06:42.400> this<00:06:42.599> data<00:06:42.960> from<00:06:43.360> uh 00:06:43.909 --> 00:06:43.919 align:start position:0% then you take some of this data from uh 00:06:43.919 --> 00:06:45.390 align:start position:0% then you take some of this data from uh you<00:06:44.039> take<00:06:44.240> some<00:06:44.360> of<00:06:44.479> this<00:06:44.639> data<00:06:44.880> from<00:06:45.039> the<00:06:45.280> from 00:06:45.390 --> 00:06:45.400 align:start position:0% you take some of this data from the from 00:06:45.400 --> 00:06:47.589 align:start position:0% you take some of this data from the from the<00:06:45.560> receipt<00:06:45.880> tree<00:06:46.479> so<00:06:46.919> the<00:06:47.080> receipt<00:06:47.360> tree 00:06:47.589 --> 00:06:47.599 align:start position:0% the receipt tree so the receipt tree 00:06:47.599 --> 00:06:49.029 align:start position:0% the receipt tree so the receipt tree contains<00:06:48.000> an<00:06:48.160> intermediate<00:06:48.599> State<00:06:48.800> rout 00:06:49.029 --> 00:06:49.039 align:start position:0% contains an intermediate State rout 00:06:49.039 --> 00:06:50.950 align:start position:0% contains an intermediate State rout after<00:06:49.240> processing<00:06:49.599> every<00:06:49.880> transaction<00:06:50.759> take 00:06:50.950 --> 00:06:50.960 align:start position:0% after processing every transaction take 00:06:50.960 --> 00:06:52.150 align:start position:0% after processing every transaction take the<00:06:51.080> intermediate<00:06:51.479> State<00:06:51.680> Route<00:06:51.919> you<00:06:52.000> take 00:06:52.150 --> 00:06:52.160 align:start position:0% the intermediate State Route you take 00:06:52.160 --> 00:06:54.189 align:start position:0% the intermediate State Route you take the<00:06:52.319> transaction<00:06:53.199> and<00:06:53.319> you<00:06:53.440> make<00:06:53.720> sure<00:06:54.000> that 00:06:54.189 --> 00:06:54.199 align:start position:0% the transaction and you make sure that 00:06:54.199 --> 00:06:55.950 align:start position:0% the transaction and you make sure that if<00:06:54.319> you<00:06:54.440> just<00:06:54.639> run<00:06:54.880> the<00:06:55.039> transaction<00:06:55.599> on<00:06:55.800> top 00:06:55.950 --> 00:06:55.960 align:start position:0% if you just run the transaction on top 00:06:55.960 --> 00:06:57.510 align:start position:0% if you just run the transaction on top of<00:06:56.039> the<00:06:56.160> previous<00:06:56.440> intermediate<00:06:56.879> State<00:06:57.080> rout 00:06:57.510 --> 00:06:57.520 align:start position:0% of the previous intermediate State rout 00:06:57.520 --> 00:06:59.230 align:start position:0% of the previous intermediate State rout you<00:06:57.680> get<00:06:57.960> back<00:06:58.319> the<00:06:58.479> new<00:06:58.599> intermediate<00:06:59.039> state 00:06:59.230 --> 00:06:59.240 align:start position:0% you get back the new intermediate state 00:06:59.240 --> 00:07:00.350 align:start position:0% you get back the new intermediate state route 00:07:00.350 --> 00:07:00.360 align:start position:0% route 00:07:00.360 --> 00:07:02.270 align:start position:0% route and<00:07:00.840> why<00:07:01.039> is<00:07:01.199> this<00:07:01.360> stuff<00:07:01.639> necessary 00:07:02.270 --> 00:07:02.280 align:start position:0% and why is this stuff necessary 00:07:02.280 --> 00:07:04.869 align:start position:0% and why is this stuff necessary basically<00:07:03.280> so<00:07:03.520> one<00:07:03.759> reason<00:07:04.240> one<00:07:04.400> reason<00:07:04.759> is 00:07:04.869 --> 00:07:04.879 align:start position:0% basically so one reason one reason is 00:07:04.879 --> 00:07:06.350 align:start position:0% basically so one reason one reason is that<00:07:05.039> if<00:07:05.120> you<00:07:05.240> want<00:07:05.440> a<00:07:05.599> somewhat<00:07:06.039> stronger 00:07:06.350 --> 00:07:06.360 align:start position:0% that if you want a somewhat stronger 00:07:06.360 --> 00:07:07.670 align:start position:0% that if you want a somewhat stronger assurance<00:07:06.840> that<00:07:07.039> that<00:07:07.160> things<00:07:07.280> are<00:07:07.440> being 00:07:07.670 --> 00:07:07.680 align:start position:0% assurance that that things are being 00:07:07.680 --> 00:07:08.710 align:start position:0% assurance that that things are being done<00:07:07.879> correctly<00:07:08.280> and<00:07:08.400> if<00:07:08.479> you<00:07:08.560> don't 00:07:08.710 --> 00:07:08.720 align:start position:0% done correctly and if you don't 00:07:08.720 --> 00:07:10.430 align:start position:0% done correctly and if you don't necessarily<00:07:09.160> trust<00:07:09.440> the<00:07:09.560> majority<00:07:10.319> the 00:07:10.430 --> 00:07:10.440 align:start position:0% necessarily trust the majority the 00:07:10.440 --> 00:07:12.710 align:start position:0% necessarily trust the majority the majority<00:07:10.879> hash<00:07:11.199> power<00:07:11.800> once<00:07:12.039> proof<00:07:12.280> of<00:07:12.400> stake 00:07:12.710 --> 00:07:12.720 align:start position:0% majority hash power once proof of stake 00:07:12.720 --> 00:07:14.790 align:start position:0% majority hash power once proof of stake comes<00:07:12.919> along<00:07:13.199> and<00:07:13.319> you<00:07:13.440> can't<00:07:13.720> just<00:07:13.919> rely<00:07:14.400> on 00:07:14.790 --> 00:07:14.800 align:start position:0% comes along and you can't just rely on 00:07:14.800 --> 00:07:16.710 align:start position:0% comes along and you can't just rely on difficulty<00:07:15.039> as<00:07:15.160> a<00:07:15.680> as<00:07:15.800> a<00:07:15.879> sort<00:07:16.080> of<00:07:16.199> proxy<00:07:16.560> for 00:07:16.710 --> 00:07:16.720 align:start position:0% difficulty as a as a sort of proxy for 00:07:16.720 --> 00:07:18.150 align:start position:0% difficulty as a as a sort of proxy for security<00:07:17.120> might<00:07:17.280> become<00:07:17.520> even<00:07:17.680> more 00:07:18.150 --> 00:07:18.160 align:start position:0% security might become even more 00:07:18.160 --> 00:07:22.189 align:start position:0% security might become even more important<00:07:19.160> and<00:07:19.360> finally<00:07:19.759> Al 00:07:22.189 --> 00:07:22.199 align:start position:0% important and finally Al 00:07:22.199 --> 00:07:24.550 align:start position:0% important and finally Al so<00:07:23.199> one<00:07:23.360> of<00:07:23.560> the<00:07:23.720> things<00:07:23.960> that<00:07:24.080> we<00:07:24.199> want<00:07:24.319> to 00:07:24.550 --> 00:07:24.560 align:start position:0% so one of the things that we want to 00:07:24.560 --> 00:07:28.550 align:start position:0% so one of the things that we want to provide<00:07:25.039> with<00:07:25.319> with<00:07:25.520> that<00:07:26.360> is<00:07:27.120> um<00:07:27.479> the<00:07:27.639> ability 00:07:28.550 --> 00:07:28.560 align:start position:0% provide with with that is um the ability 00:07:28.560 --> 00:07:30.309 align:start position:0% provide with with that is um the ability to 00:07:30.309 --> 00:07:30.319 align:start position:0% to 00:07:30.319 --> 00:07:32.390 align:start position:0% to um<00:07:30.919> effectively<00:07:31.400> like<00:07:31.560> not<00:07:31.840> think<00:07:32.080> about<00:07:32.240> the 00:07:32.390 --> 00:07:32.400 align:start position:0% um effectively like not think about the 00:07:32.400 --> 00:07:33.990 align:start position:0% um effectively like not think about the blockchain<00:07:32.919> not<00:07:33.080> have<00:07:33.199> to<00:07:33.319> think<00:07:33.560> necessarily 00:07:33.990 --> 00:07:34.000 align:start position:0% blockchain not have to think necessarily 00:07:34.000 --> 00:07:35.950 align:start position:0% blockchain not have to think necessarily about<00:07:34.240> transactions<00:07:34.919> and<00:07:35.039> not<00:07:35.199> have<00:07:35.280> to<00:07:35.440> think 00:07:35.950 --> 00:07:35.960 align:start position:0% about transactions and not have to think 00:07:35.960 --> 00:07:38.189 align:start position:0% about transactions and not have to think particularly<00:07:36.479> about<00:07:36.720> State<00:07:37.520> the<00:07:37.639> idea<00:07:37.919> is<00:07:38.080> to 00:07:38.189 --> 00:07:38.199 align:start position:0% particularly about State the idea is to 00:07:38.199 --> 00:07:40.510 align:start position:0% particularly about State the idea is to provide<00:07:38.440> an<00:07:38.840> an<00:07:39.000> abstraction<00:07:39.560> mechanism<00:07:40.319> for 00:07:40.510 --> 00:07:40.520 align:start position:0% provide an an abstraction mechanism for 00:07:40.520 --> 00:07:42.029 align:start position:0% provide an an abstraction mechanism for the<00:07:40.680> blockchain<00:07:41.199> for<00:07:41.360> what<00:07:41.479> the<00:07:41.560> blockchain 00:07:42.029 --> 00:07:42.039 align:start position:0% the blockchain for what the blockchain 00:07:42.039 --> 00:07:44.270 align:start position:0% the blockchain for what the blockchain provides<00:07:42.960> and<00:07:43.080> this<00:07:43.280> abstraction<00:07:43.759> mechanism 00:07:44.270 --> 00:07:44.280 align:start position:0% provides and this abstraction mechanism 00:07:44.280 --> 00:07:46.230 align:start position:0% provides and this abstraction mechanism that<00:07:44.520> the<00:07:44.599> sort<00:07:44.759> of<00:07:44.879> interface<00:07:45.240> it<00:07:45.479> provides 00:07:46.230 --> 00:07:46.240 align:start position:0% that the sort of interface it provides 00:07:46.240 --> 00:07:47.430 align:start position:0% that the sort of interface it provides becomes<00:07:46.560> something<00:07:46.800> that<00:07:46.879> we're<00:07:47.039> a<00:07:47.120> bit<00:07:47.240> more 00:07:47.430 --> 00:07:47.440 align:start position:0% becomes something that we're a bit more 00:07:47.440 --> 00:07:49.070 align:start position:0% becomes something that we're a bit more familiar<00:07:47.840> with<00:07:48.000> the<00:07:48.120> notion<00:07:48.400> of<00:07:48.599> the<00:07:48.879> uh 00:07:49.070 --> 00:07:49.080 align:start position:0% familiar with the notion of the uh 00:07:49.080 --> 00:07:51.230 align:start position:0% familiar with the notion of the uh notion<00:07:49.280> of<00:07:49.400> a<00:07:49.479> sort<00:07:49.639> of<00:07:49.800> virtual 00:07:51.230 --> 00:07:51.240 align:start position:0% notion of a sort of virtual 00:07:51.240 --> 00:07:54.469 align:start position:0% notion of a sort of virtual machine<00:07:52.280> um<00:07:53.280> as<00:07:53.560> the<00:07:53.680> virtual<00:07:54.000> machine 00:07:54.469 --> 00:07:54.479 align:start position:0% machine um as the virtual machine 00:07:54.479 --> 00:07:57.909 align:start position:0% machine um as the virtual machine executes<00:07:55.479> um<00:07:55.720> it's<00:07:56.360> it's<00:07:56.879> useful<00:07:57.680> because 00:07:57.909 --> 00:07:57.919 align:start position:0% executes um it's it's useful because 00:07:57.919 --> 00:07:59.749 align:start position:0% executes um it's it's useful because it's<00:07:58.120> not<00:07:58.360> in<00:07:58.520> an<00:07:58.759> environment<00:07:59.199> that<00:07:59.280> you<00:07:59.599> have 00:07:59.749 --> 00:07:59.759 align:start position:0% it's not in an environment that you have 00:07:59.759 --> 00:08:01.350 align:start position:0% it's not in an environment that you have direct<00:08:00.080> access<00:08:00.360> to<00:08:00.560> you<00:08:00.680> have<00:08:00.800> to<00:08:01.080> uh<00:08:01.199> you<00:08:01.280> have 00:08:01.350 --> 00:08:01.360 align:start position:0% direct access to you have to uh you have 00:08:01.360 --> 00:08:03.589 align:start position:0% direct access to you have to uh you have to<00:08:01.479> do<00:08:01.560> it<00:08:01.680> in<00:08:01.759> terms<00:08:01.960> of<00:08:02.440> transactions<00:08:03.440> um 00:08:03.589 --> 00:08:03.599 align:start position:0% to do it in terms of transactions um 00:08:03.599 --> 00:08:04.909 align:start position:0% to do it in terms of transactions um it's<00:08:03.759> useful<00:08:04.080> to<00:08:04.199> be<00:08:04.280> able<00:08:04.440> to<00:08:04.560> put<00:08:04.720> things 00:08:04.909 --> 00:08:04.919 align:start position:0% it's useful to be able to put things 00:08:04.919 --> 00:08:06.670 align:start position:0% it's useful to be able to put things like<00:08:05.120> checkpoints<00:08:05.639> in<00:08:06.039> to<00:08:06.159> see<00:08:06.360> if<00:08:06.479> a 00:08:06.670 --> 00:08:06.680 align:start position:0% like checkpoints in to see if a 00:08:06.680 --> 00:08:07.909 align:start position:0% like checkpoints in to see if a particular<00:08:07.159> contract<00:08:07.639> that<00:08:07.759> you're 00:08:07.909 --> 00:08:07.919 align:start position:0% particular contract that you're 00:08:07.919 --> 00:08:09.869 align:start position:0% particular contract that you're interested<00:08:08.280> in<00:08:08.599> at<00:08:08.720> a<00:08:08.879> particular<00:08:09.319> point<00:08:09.720> in 00:08:09.869 --> 00:08:09.879 align:start position:0% interested in at a particular point in 00:08:09.879 --> 00:08:12.589 align:start position:0% interested in at a particular point in its<00:08:10.319> execution<00:08:11.319> such<00:08:11.520> a<00:08:11.680> point<00:08:11.960> for<00:08:12.159> example 00:08:12.589 --> 00:08:12.599 align:start position:0% its execution such a point for example 00:08:12.599 --> 00:08:14.950 align:start position:0% its execution such a point for example might<00:08:12.840> be<00:08:13.479> um<00:08:13.759> that<00:08:14.080> it<00:08:14.240> has<00:08:14.639> received<00:08:14.800> a 00:08:14.950 --> 00:08:14.960 align:start position:0% might be um that it has received a 00:08:14.960 --> 00:08:17.149 align:start position:0% might be um that it has received a payment<00:08:15.599> that<00:08:15.800> it<00:08:15.919> has<00:08:16.319> a<00:08:16.400> set<00:08:16.599> a<00:08:16.720> payment<00:08:17.000> has 00:08:17.149 --> 00:08:17.159 align:start position:0% payment that it has a set a payment has 00:08:17.159 --> 00:08:19.550 align:start position:0% payment that it has a set a payment has been<00:08:17.280> sent<00:08:17.720> from<00:08:18.240> uh<00:08:18.360> from<00:08:18.520> one<00:08:18.639> of<00:08:18.759> your 00:08:19.550 --> 00:08:19.560 align:start position:0% been sent from uh from one of your 00:08:19.560 --> 00:08:22.189 align:start position:0% been sent from uh from one of your accounts<00:08:20.560> or<00:08:20.919> um<00:08:21.280> that<00:08:21.440> one<00:08:21.560> of<00:08:21.680> the<00:08:21.800> orders 00:08:22.189 --> 00:08:22.199 align:start position:0% accounts or um that one of the orders 00:08:22.199 --> 00:08:23.390 align:start position:0% accounts or um that one of the orders that<00:08:22.280> you<00:08:22.360> might<00:08:22.479> have<00:08:22.599> put<00:08:22.720> on<00:08:22.840> an<00:08:23.000> exchange 00:08:23.390 --> 00:08:23.400 align:start position:0% that you might have put on an exchange 00:08:23.400 --> 00:08:25.710 align:start position:0% that you might have put on an exchange for<00:08:23.520> instance<00:08:23.800> has<00:08:24.000> actually<00:08:24.560> executed<00:08:25.560> so 00:08:25.710 --> 00:08:25.720 align:start position:0% for instance has actually executed so 00:08:25.720 --> 00:08:28.550 align:start position:0% for instance has actually executed so this<00:08:25.840> is<00:08:26.000> kind<00:08:26.120> of<00:08:26.319> like<00:08:26.599> the<00:08:26.919> uh<00:08:27.120> the<00:08:27.360> io<00:08:28.240> more 00:08:28.550 --> 00:08:28.560 align:start position:0% this is kind of like the uh the io more 00:08:28.560 --> 00:08:30.350 align:start position:0% this is kind of like the uh the io more the<00:08:28.720> O<00:08:29.000> from<00:08:29.120> the<00:08:29.199> block<00:08:29.560> chain<00:08:29.759> and<00:08:29.879> the<00:08:30.080> I 00:08:30.350 --> 00:08:30.360 align:start position:0% the O from the block chain and the I 00:08:30.360 --> 00:08:32.350 align:start position:0% the O from the block chain and the I into<00:08:30.639> the<00:08:30.759> rest<00:08:30.919> of<00:08:31.039> the<00:08:31.199> DAP<00:08:31.639> but<00:08:31.759> the<00:08:31.919> io 00:08:32.350 --> 00:08:32.360 align:start position:0% into the rest of the DAP but the io 00:08:32.360 --> 00:08:35.430 align:start position:0% into the rest of the DAP but the io between<00:08:32.680> blockchain<00:08:33.640> and<00:08:33.919> the<00:08:34.240> uh<00:08:34.959> the<00:08:35.080> DAP<00:08:35.360> as 00:08:35.430 --> 00:08:35.440 align:start position:0% between blockchain and the uh the DAP as 00:08:35.440 --> 00:08:37.310 align:start position:0% between blockchain and the uh the DAP as a<00:08:35.560> whole<00:08:35.800> the<00:08:35.959> JavaScript<00:08:36.560> portion<00:08:37.120> that's 00:08:37.310 --> 00:08:37.320 align:start position:0% a whole the JavaScript portion that's 00:08:37.320 --> 00:08:39.230 align:start position:0% a whole the JavaScript portion that's actually<00:08:37.640> executing<00:08:38.200> locally<00:08:39.000> in<00:08:39.120> the 00:08:39.230 --> 00:08:39.240 align:start position:0% actually executing locally in the 00:08:39.240 --> 00:08:42.269 align:start position:0% actually executing locally in the browser<00:08:40.240> now<00:08:40.440> originally<00:08:41.279> we<00:08:41.479> had<00:08:41.760> the<00:08:42.120> uh 00:08:42.269 --> 00:08:42.279 align:start position:0% browser now originally we had the uh 00:08:42.279 --> 00:08:45.470 align:start position:0% browser now originally we had the uh this<00:08:42.440> idea<00:08:42.839> of<00:08:43.080> of<00:08:43.279> messages<00:08:44.039> so<00:08:44.440> in<00:08:44.560> the<00:08:45.080> like 00:08:45.470 --> 00:08:45.480 align:start position:0% this idea of of messages so in the like 00:08:45.480 --> 00:08:46.949 align:start position:0% this idea of of messages so in the like transactions<00:08:46.000> messages<00:08:46.360> are<00:08:46.560> things<00:08:46.800> that 00:08:46.949 --> 00:08:46.959 align:start position:0% transactions messages are things that 00:08:46.959 --> 00:08:48.750 align:start position:0% transactions messages are things that can<00:08:47.320> um<00:08:47.640> that<00:08:47.800> actually<00:08:48.000> go<00:08:48.160> and<00:08:48.320> execute 00:08:48.750 --> 00:08:48.760 align:start position:0% can um that actually go and execute 00:08:48.760 --> 00:08:50.630 align:start position:0% can um that actually go and execute contracts<00:08:49.480> but<00:08:49.640> messages<00:08:50.000> can<00:08:50.160> also<00:08:50.360> be<00:08:50.480> the 00:08:50.630 --> 00:08:50.640 align:start position:0% contracts but messages can also be the 00:08:50.640 --> 00:08:53.350 align:start position:0% contracts but messages can also be the things<00:08:50.880> that<00:08:51.720> um<00:08:52.200> messages<00:08:52.720> execute 00:08:53.350 --> 00:08:53.360 align:start position:0% things that um messages execute 00:08:53.360 --> 00:08:54.910 align:start position:0% things that um messages execute transactions<00:08:53.920> of<00:08:54.080> course<00:08:54.279> always<00:08:54.560> come<00:08:54.760> from 00:08:54.910 --> 00:08:54.920 align:start position:0% transactions of course always come from 00:08:54.920 --> 00:08:56.190 align:start position:0% transactions of course always come from an<00:08:55.080> external<00:08:55.440> entity<00:08:55.760> and<00:08:55.920> that's<00:08:56.080> they're 00:08:56.190 --> 00:08:56.200 align:start position:0% an external entity and that's they're 00:08:56.200 --> 00:08:57.750 align:start position:0% an external entity and that's they're cryptographically<00:08:56.880> signed<00:08:57.360> and<00:08:57.480> we<00:08:57.560> have<00:08:57.680> the 00:08:57.750 --> 00:08:57.760 align:start position:0% cryptographically signed and we have the 00:08:57.760 --> 00:08:59.949 align:start position:0% cryptographically signed and we have the idea<00:08:58.000> of<00:08:58.120> message<00:08:58.519> tracking<00:08:59.160> so<00:08:59.640> message 00:08:59.949 --> 00:08:59.959 align:start position:0% idea of message tracking so message 00:08:59.959 --> 00:09:02.470 align:start position:0% idea of message tracking so message watching<00:09:00.560> whereby<00:09:01.040> the<00:09:01.320> the<00:09:01.440> Javas<00:09:01.959> the<00:09:02.079> local 00:09:02.470 --> 00:09:02.480 align:start position:0% watching whereby the the Javas the local 00:09:02.480 --> 00:09:05.069 align:start position:0% watching whereby the the Javas the local portion<00:09:03.240> of<00:09:03.399> the<00:09:03.640> uh<00:09:03.720> of<00:09:03.800> the<00:09:03.920> D<00:09:04.320> could<00:09:04.920> um 00:09:05.069 --> 00:09:05.079 align:start position:0% portion of the uh of the D could um 00:09:05.079 --> 00:09:06.750 align:start position:0% portion of the uh of the D could um watch<00:09:05.360> out<00:09:05.680> for<00:09:05.959> for<00:09:06.120> changes<00:09:06.480> on<00:09:06.640> the 00:09:06.750 --> 00:09:06.760 align:start position:0% watch out for for changes on the 00:09:06.760 --> 00:09:08.590 align:start position:0% watch out for for changes on the blockchain<00:09:07.480> that<00:09:07.640> involved<00:09:08.040> a<00:09:08.160> particular 00:09:08.590 --> 00:09:08.600 align:start position:0% blockchain that involved a particular 00:09:08.600 --> 00:09:10.310 align:start position:0% blockchain that involved a particular message<00:09:09.200> and<00:09:09.320> it<00:09:09.399> might<00:09:09.600> also<00:09:09.839> have<00:09:09.959> filtered 00:09:10.310 --> 00:09:10.320 align:start position:0% message and it might also have filtered 00:09:10.320 --> 00:09:12.829 align:start position:0% message and it might also have filtered it<00:09:10.519> by<00:09:11.079> what<00:09:11.200> the<00:09:11.320> input<00:09:11.600> to<00:09:11.720> the<00:09:11.839> message<00:09:12.160> was 00:09:12.829 --> 00:09:12.839 align:start position:0% it by what the input to the message was 00:09:12.839 --> 00:09:15.230 align:start position:0% it by what the input to the message was now<00:09:13.040> this<00:09:13.200> turned<00:09:13.519> out<00:09:13.720> to<00:09:13.920> be<00:09:14.640> um<00:09:14.839> less<00:09:15.040> than 00:09:15.230 --> 00:09:15.240 align:start position:0% now this turned out to be um less than 00:09:15.240 --> 00:09:17.030 align:start position:0% now this turned out to be um less than ideal<00:09:15.839> and<00:09:15.959> so<00:09:16.120> we<00:09:16.240> sort<00:09:16.360> of<00:09:16.519> evolved<00:09:16.920> this 00:09:17.030 --> 00:09:17.040 align:start position:0% ideal and so we sort of evolved this 00:09:17.040 --> 00:09:21.310 align:start position:0% ideal and so we sort of evolved this notion<00:09:17.320> of<00:09:17.440> a<00:09:17.560> log<00:09:18.279> now<00:09:18.440> the<00:09:18.640> log<00:09:19.480> is<00:09:20.040> a<00:09:20.640> uh<00:09:21.160> like 00:09:21.310 --> 00:09:21.320 align:start position:0% notion of a log now the log is a uh like 00:09:21.320 --> 00:09:23.870 align:start position:0% notion of a log now the log is a uh like a<00:09:21.480> breakpoint<00:09:22.000> or<00:09:22.120> a<00:09:22.320> record<00:09:22.839> it<00:09:22.959> allows<00:09:23.760> a 00:09:23.870 --> 00:09:23.880 align:start position:0% a breakpoint or a record it allows a 00:09:23.880 --> 00:09:27.710 align:start position:0% a breakpoint or a record it allows a message<00:09:24.200> a<00:09:24.399> contract<00:09:25.320> to<00:09:26.040> um<00:09:26.279> to<00:09:26.519> point<00:09:26.800> out<00:09:27.399> to 00:09:27.710 --> 00:09:27.720 align:start position:0% message a contract to um to point out to 00:09:27.720 --> 00:09:30.430 align:start position:0% message a contract to um to point out to to<00:09:28.079> to<00:09:28.240> an<00:09:28.440> interface<00:09:29.440> that<00:09:29.800> a<00:09:30.040> particular 00:09:30.430 --> 00:09:30.440 align:start position:0% to to an interface that a particular 00:09:30.440 --> 00:09:32.790 align:start position:0% to to an interface that a particular thing<00:09:30.600> has<00:09:30.800> happened<00:09:31.240> logs<00:09:31.880> can<00:09:32.120> include<00:09:32.560> a 00:09:32.790 --> 00:09:32.800 align:start position:0% thing has happened logs can include a 00:09:32.800 --> 00:09:34.949 align:start position:0% thing has happened logs can include a topic<00:09:33.120> or<00:09:33.320> many<00:09:33.640> topics<00:09:34.320> and<00:09:34.480> these<00:09:34.600> sort<00:09:34.800> of 00:09:34.949 --> 00:09:34.959 align:start position:0% topic or many topics and these sort of 00:09:34.959 --> 00:09:38.030 align:start position:0% topic or many topics and these sort of identify<00:09:35.480> the<00:09:35.680> type<00:09:35.880> of<00:09:36.040> Entry<00:09:36.920> logs<00:09:37.279> also<00:09:37.920> uh 00:09:38.030 --> 00:09:38.040 align:start position:0% identify the type of Entry logs also uh 00:09:38.040 --> 00:09:40.150 align:start position:0% identify the type of Entry logs also uh implicitly<00:09:38.680> include<00:09:39.240> the<00:09:39.399> address<00:09:39.839> of<00:09:40.000> the 00:09:40.150 --> 00:09:40.160 align:start position:0% implicitly include the address of the 00:09:40.160 --> 00:09:42.190 align:start position:0% implicitly include the address of the contract<00:09:40.680> that<00:09:40.880> created<00:09:41.320> the<00:09:41.480> log<00:09:42.079> and 00:09:42.190 --> 00:09:42.200 align:start position:0% contract that created the log and 00:09:42.200 --> 00:09:44.829 align:start position:0% contract that created the log and finally<00:09:42.519> logs<00:09:42.800> can<00:09:42.959> also<00:09:43.200> include<00:09:43.680> data<00:09:44.640> just 00:09:44.829 --> 00:09:44.839 align:start position:0% finally logs can also include data just 00:09:44.839 --> 00:09:47.670 align:start position:0% finally logs can also include data just arbitrary<00:09:45.360> unformatted<00:09:45.920> binary<00:09:46.399> data<00:09:47.399> and<00:09:47.560> of 00:09:47.670 --> 00:09:47.680 align:start position:0% arbitrary unformatted binary data and of 00:09:47.680 --> 00:09:49.069 align:start position:0% arbitrary unformatted binary data and of course<00:09:47.880> this<00:09:48.040> data<00:09:48.279> can<00:09:48.440> mean<00:09:48.640> whatever<00:09:48.920> the 00:09:49.069 --> 00:09:49.079 align:start position:0% course this data can mean whatever the 00:09:49.079 --> 00:09:51.829 align:start position:0% course this data can mean whatever the contract<00:09:49.440> wants<00:09:49.680> it<00:09:49.800> to<00:09:50.000> mean<00:09:51.000> um<00:09:51.680> the 00:09:51.829 --> 00:09:51.839 align:start position:0% contract wants it to mean um the 00:09:51.839 --> 00:09:53.150 align:start position:0% contract wants it to mean um the difference<00:09:52.240> between<00:09:52.480> the<00:09:52.600> topics<00:09:52.920> and<00:09:53.040> the 00:09:53.150 --> 00:09:53.160 align:start position:0% difference between the topics and the 00:09:53.160 --> 00:09:55.710 align:start position:0% difference between the topics and the data<00:09:53.519> is<00:09:53.600> that<00:09:53.720> the<00:09:53.959> topics<00:09:54.480> are<00:09:54.760> indexed<00:09:55.480> so 00:09:55.710 --> 00:09:55.720 align:start position:0% data is that the topics are indexed so 00:09:55.720 --> 00:09:57.750 align:start position:0% data is that the topics are indexed so topics<00:09:56.079> can<00:09:56.240> be<00:09:56.399> watched<00:09:56.720> out<00:09:56.959> for<00:09:57.360> by<00:09:57.560> the 00:09:57.750 --> 00:09:57.760 align:start position:0% topics can be watched out for by the 00:09:57.760 --> 00:09:59.870 align:start position:0% topics can be watched out for by the JavaScript<00:09:58.320> front<00:09:58.600> end<00:09:58.920> by<00:09:59.040> the<00:09:59.480> the<00:09:59.600> rest<00:09:59.760> of 00:09:59.870 --> 00:09:59.880 align:start position:0% JavaScript front end by the the rest of 00:09:59.880 --> 00:10:03.269 align:start position:0% JavaScript front end by the the rest of the<00:10:00.519> DAT<00:10:01.519> um<00:10:02.160> the<00:10:02.360> reason<00:10:02.640> that<00:10:02.760> we<00:10:02.839> have<00:10:03.000> logs 00:10:03.269 --> 00:10:03.279 align:start position:0% the DAT um the reason that we have logs 00:10:03.279 --> 00:10:05.750 align:start position:0% the DAT um the reason that we have logs at<00:10:03.440> all<00:10:03.880> is<00:10:04.040> so<00:10:04.279> that<00:10:04.560> we<00:10:04.720> can<00:10:04.920> we<00:10:05.000> can<00:10:05.200> very 00:10:05.750 --> 00:10:05.760 align:start position:0% at all is so that we can we can very 00:10:05.760 --> 00:10:08.750 align:start position:0% at all is so that we can we can very efficiently<00:10:06.760> um<00:10:07.200> uh<00:10:07.480> index<00:10:07.920> them<00:10:08.200> and<00:10:08.360> filter 00:10:08.750 --> 00:10:08.760 align:start position:0% efficiently um uh index them and filter 00:10:08.760 --> 00:10:13.910 align:start position:0% efficiently um uh index them and filter them<00:10:09.079> when<00:10:09.279> daps<00:10:10.480> required<00:10:11.680> now<00:10:12.760> because<00:10:13.760> the 00:10:13.910 --> 00:10:13.920 align:start position:0% them when daps required now because the 00:10:13.920 --> 00:10:16.389 align:start position:0% them when daps required now because the light<00:10:14.240> cine<00:10:14.560> is<00:10:14.680> an<00:10:14.880> important<00:10:15.720> um<00:10:16.040> part<00:10:16.200> of 00:10:16.389 --> 00:10:16.399 align:start position:0% light cine is an important um part of 00:10:16.399 --> 00:10:17.790 align:start position:0% light cine is an important um part of the<00:10:16.720> the<00:10:16.839> eventual<00:10:17.240> protocol<00:10:17.640> it<00:10:17.680> was 00:10:17.790 --> 00:10:17.800 align:start position:0% the the eventual protocol it was 00:10:17.800 --> 00:10:19.710 align:start position:0% the the eventual protocol it was important<00:10:18.079> to<00:10:18.240> get<00:10:18.440> this<00:10:18.920> this<00:10:19.040> interface<00:10:19.480> in 00:10:19.710 --> 00:10:19.720 align:start position:0% important to get this this interface in 00:10:19.720 --> 00:10:22.069 align:start position:0% important to get this this interface in now<00:10:20.240> so<00:10:20.440> we<00:10:20.560> can<00:10:20.920> uh<00:10:21.040> work<00:10:21.279> out<00:10:21.560> exactly<00:10:21.920> how 00:10:22.069 --> 00:10:22.079 align:start position:0% now so we can uh work out exactly how 00:10:22.079 --> 00:10:24.230 align:start position:0% now so we can uh work out exactly how like<00:10:22.399> clients<00:10:22.760> will<00:10:22.920> be<00:10:23.040> able<00:10:23.360> to<00:10:23.560> work<00:10:23.800> out 00:10:24.230 --> 00:10:24.240 align:start position:0% like clients will be able to work out 00:10:24.240 --> 00:10:26.750 align:start position:0% like clients will be able to work out efficiently<00:10:25.240> whether<00:10:25.959> any<00:10:26.120> of<00:10:26.320> these<00:10:26.519> log 00:10:26.750 --> 00:10:26.760 align:start position:0% efficiently whether any of these log 00:10:26.760 --> 00:10:28.710 align:start position:0% efficiently whether any of these log entries<00:10:27.200> in<00:10:27.600> in<00:10:27.760> on<00:10:27.920> the<00:10:28.040> blockchain<00:10:28.519> have 00:10:28.710 --> 00:10:28.720 align:start position:0% entries in in on the blockchain have 00:10:28.720 --> 00:10:31.190 align:start position:0% entries in in on the blockchain have actually<00:10:29.800> fired<00:10:30.399> whether<00:10:30.600> they're<00:10:30.920> there 00:10:31.190 --> 00:10:31.200 align:start position:0% actually fired whether they're there 00:10:31.200 --> 00:10:32.670 align:start position:0% actually fired whether they're there whether<00:10:31.519> new<00:10:31.720> records<00:10:32.079> have<00:10:32.200> come<00:10:32.360> along<00:10:32.560> that 00:10:32.670 --> 00:10:32.680 align:start position:0% whether new records have come along that 00:10:32.680 --> 00:10:35.110 align:start position:0% whether new records have come along that we're<00:10:32.880> interested<00:10:33.279> in<00:10:34.200> and<00:10:34.600> the<00:10:34.720> way<00:10:34.880> that<00:10:35.000> we 00:10:35.110 --> 00:10:35.120 align:start position:0% we're interested in and the way that we 00:10:35.120 --> 00:10:37.910 align:start position:0% we're interested in and the way that we do<00:10:35.399> this<00:10:36.079> as<00:10:36.440> vitalic<00:10:36.800> mentioned<00:10:37.160> before<00:10:37.720> is 00:10:37.910 --> 00:10:37.920 align:start position:0% do this as vitalic mentioned before is 00:10:37.920 --> 00:10:40.750 align:start position:0% do this as vitalic mentioned before is transaction 00:10:40.750 --> 00:10:40.760 align:start position:0% 00:10:40.760 --> 00:10:43.069 align:start position:0% receipts<00:10:41.760> so<00:10:42.200> first<00:10:42.399> of<00:10:42.519> all<00:10:42.720> just<00:10:42.839> to 00:10:43.069 --> 00:10:43.079 align:start position:0% receipts so first of all just to 00:10:43.079 --> 00:10:45.269 align:start position:0% receipts so first of all just to describe<00:10:43.519> how<00:10:43.720> logs<00:10:44.040> are<00:10:44.200> implemented<00:10:45.079> there 00:10:45.269 --> 00:10:45.279 align:start position:0% describe how logs are implemented there 00:10:45.279 --> 00:10:47.389 align:start position:0% describe how logs are implemented there is<00:10:45.399> an<00:10:45.560> OP<00:10:45.839> code<00:10:46.480> and<00:10:46.680> the<00:10:46.800> sort<00:10:46.959> of<00:10:47.079> Bitcoin 00:10:47.389 --> 00:10:47.399 align:start position:0% is an OP code and the sort of Bitcoin 00:10:47.399 --> 00:10:49.190 align:start position:0% is an OP code and the sort of Bitcoin each<00:10:47.720> Bitcoin<00:10:48.040> each<00:10:48.200> term<00:10:48.440> for<00:10:48.600> what<00:10:48.920> for<00:10:49.079> what 00:10:49.190 --> 00:10:49.200 align:start position:0% each Bitcoin each term for what for what 00:10:49.200 --> 00:10:50.790 align:start position:0% each Bitcoin each term for what for what the<00:10:49.279> log<00:10:49.519> op<00:10:49.720> code<00:10:49.920> does<00:10:50.120> is<00:10:50.279> proof<00:10:50.519> of 00:10:50.790 --> 00:10:50.800 align:start position:0% the log op code does is proof of 00:10:50.800 --> 00:10:52.990 align:start position:0% the log op code does is proof of publication<00:10:51.800> so<00:10:52.120> it<00:10:52.279> just<00:10:52.519> proves<00:10:52.839> that 00:10:52.990 --> 00:10:53.000 align:start position:0% publication so it just proves that 00:10:53.000 --> 00:10:54.910 align:start position:0% publication so it just proves that something<00:10:53.639> it<00:10:53.800> sort<00:10:53.920> of<00:10:54.079> publishes<00:10:54.519> an<00:10:54.680> event 00:10:54.910 --> 00:10:54.920 align:start position:0% something it sort of publishes an event 00:10:54.920 --> 00:10:56.590 align:start position:0% something it sort of publishes an event in<00:10:55.040> the<00:10:55.160> blockchain<00:10:55.600> by<00:10:55.720> connecting<00:10:56.240> by<00:10:56.440> just 00:10:56.590 --> 00:10:56.600 align:start position:0% in the blockchain by connecting by just 00:10:56.600 --> 00:10:58.509 align:start position:0% in the blockchain by connecting by just connecting<00:10:56.959> it<00:10:57.079> with<00:10:57.200> a<00:10:57.320> hash<00:10:57.519> tree<00:10:57.760> to<00:10:57.920> a<00:10:58.279> to<00:10:58.399> a 00:10:58.509 --> 00:10:58.519 align:start position:0% connecting it with a hash tree to a to a 00:10:58.519 --> 00:11:01.750 align:start position:0% connecting it with a hash tree to a to a state<00:10:58.720> rout<00:10:58.880> and<00:10:59.040> to<00:10:59.360> R<00:10:59.680> blog<00:11:00.240> header<00:11:01.240> log<00:11:01.519> op 00:11:01.750 --> 00:11:01.760 align:start position:0% state rout and to R blog header log op 00:11:01.760 --> 00:11:04.389 align:start position:0% state rout and to R blog header log op code<00:11:02.079> has<00:11:02.360> up<00:11:02.480> to<00:11:02.639> six<00:11:02.959> arguments<00:11:03.880> so<00:11:04.120> first<00:11:04.279> of 00:11:04.389 --> 00:11:04.399 align:start position:0% code has up to six arguments so first of 00:11:04.399 --> 00:11:06.430 align:start position:0% code has up to six arguments so first of all<00:11:04.560> it<00:11:04.720> has<00:11:04.880> two<00:11:05.120> arguments<00:11:05.560> to<00:11:05.839> grab<00:11:06.040> a<00:11:06.160> slice 00:11:06.430 --> 00:11:06.440 align:start position:0% all it has two arguments to grab a slice 00:11:06.440 --> 00:11:08.949 align:start position:0% all it has two arguments to grab a slice of<00:11:06.600> memory<00:11:07.000> that<00:11:07.399> that<00:11:07.480> it<00:11:07.600> keeps<00:11:07.839> as<00:11:08.120> data 00:11:08.949 --> 00:11:08.959 align:start position:0% of memory that that it keeps as data 00:11:08.959 --> 00:11:11.069 align:start position:0% of memory that that it keeps as data then<00:11:09.079> a<00:11:09.240> log<00:11:09.440> can<00:11:09.600> have<00:11:09.760> up<00:11:09.880> to<00:11:10.000> four<00:11:10.360> topics 00:11:11.069 --> 00:11:11.079 align:start position:0% then a log can have up to four topics 00:11:11.079 --> 00:11:13.230 align:start position:0% then a log can have up to four topics and<00:11:11.360> implicitly<00:11:12.000> a<00:11:12.160> log<00:11:12.440> always<00:11:12.720> has<00:11:13.079> as<00:11:13.160> a 00:11:13.230 --> 00:11:13.240 align:start position:0% and implicitly a log always has as a 00:11:13.240 --> 00:11:15.150 align:start position:0% and implicitly a log always has as a sort<00:11:13.399> of<00:11:13.560> argument<00:11:14.200> the<00:11:14.399> address<00:11:14.760> of<00:11:14.959> of<00:11:15.040> the 00:11:15.150 --> 00:11:15.160 align:start position:0% sort of argument the address of of the 00:11:15.160 --> 00:11:18.269 align:start position:0% sort of argument the address of of the contract<00:11:15.760> that<00:11:16.760> that<00:11:16.880> created<00:11:17.200> the<00:11:17.360> log<00:11:18.200> and 00:11:18.269 --> 00:11:18.279 align:start position:0% contract that that created the log and 00:11:18.279 --> 00:11:20.550 align:start position:0% contract that that created the log and the<00:11:18.440> data<00:11:18.760> structure<00:11:19.399> is<00:11:19.880> that'll<00:11:20.160> how<00:11:20.279> a<00:11:20.399> log 00:11:20.550 --> 00:11:20.560 align:start position:0% the data structure is that'll how a log 00:11:20.560 --> 00:11:24.389 align:start position:0% the data structure is that'll how a log is<00:11:20.680> stored<00:11:21.000> is<00:11:21.120> this<00:11:21.320> rlp<00:11:22.320> address<00:11:23.079> topics<00:11:23.800> and 00:11:24.389 --> 00:11:24.399 align:start position:0% is stored is this rlp address topics and 00:11:24.399 --> 00:11:28.389 align:start position:0% is stored is this rlp address topics and data<00:11:25.399> so<00:11:26.279> receipts<00:11:27.279> in<00:11:27.399> the<00:11:27.560> transaction<00:11:28.120> re 00:11:28.389 --> 00:11:28.399 align:start position:0% data so receipts in the transaction re 00:11:28.399 --> 00:11:29.870 align:start position:0% data so receipts in the transaction re so<00:11:28.560> the<00:11:28.639> way<00:11:28.760> that<00:11:28.839> the<00:11:28.920> transaction<00:11:29.600> so<00:11:29.760> how 00:11:29.870 --> 00:11:29.880 align:start position:0% so the way that the transaction so how 00:11:29.880 --> 00:11:32.470 align:start position:0% so the way that the transaction so how the<00:11:30.000> transaction<00:11:30.440> receipt<00:11:30.839> looks<00:11:31.639> is<00:11:31.920> that 00:11:32.470 --> 00:11:32.480 align:start position:0% the transaction receipt looks is that 00:11:32.480 --> 00:11:34.389 align:start position:0% the transaction receipt looks is that this<00:11:32.839> med<00:11:33.079> state<00:11:33.360> is<00:11:33.519> like<00:11:33.639> the<00:11:33.760> state<00:11:34.000> route 00:11:34.389 --> 00:11:34.399 align:start position:0% this med state is like the state route 00:11:34.399 --> 00:11:35.790 align:start position:0% this med state is like the state route after<00:11:34.720> processing<00:11:35.120> that<00:11:35.279> particular 00:11:35.790 --> 00:11:35.800 align:start position:0% after processing that particular 00:11:35.800 --> 00:11:38.069 align:start position:0% after processing that particular transaction<00:11:36.800> gas<00:11:37.040> used<00:11:37.320> is<00:11:37.440> a<00:11:37.519> counter<00:11:37.839> of<00:11:37.959> how 00:11:38.069 --> 00:11:38.079 align:start position:0% transaction gas used is a counter of how 00:11:38.079 --> 00:11:40.110 align:start position:0% transaction gas used is a counter of how much<00:11:38.240> gas<00:11:38.440> was<00:11:38.560> used<00:11:38.839> after<00:11:39.040> processing<00:11:39.440> the 00:11:40.110 --> 00:11:40.120 align:start position:0% much gas was used after processing the 00:11:40.120 --> 00:11:42.910 align:start position:0% much gas was used after processing the transaction<00:11:41.120> um<00:11:41.279> bloom<00:11:42.040> bloom<00:11:42.360> filter<00:11:42.760> we'll 00:11:42.910 --> 00:11:42.920 align:start position:0% transaction um bloom bloom filter we'll 00:11:42.920 --> 00:11:45.670 align:start position:0% transaction um bloom bloom filter we'll talk<00:11:43.079> about<00:11:43.279> that<00:11:43.399> a<00:11:43.519> bit<00:11:43.720> later<00:11:44.480> and<00:11:44.720> logs<00:11:45.440> so 00:11:45.670 --> 00:11:45.680 align:start position:0% talk about that a bit later and logs so 00:11:45.680 --> 00:11:47.230 align:start position:0% talk about that a bit later and logs so that's<00:11:45.880> just<00:11:46.040> a<00:11:46.240> list<00:11:46.560> a<00:11:46.720> list<00:11:46.920> you<00:11:47.000> know<00:11:47.120> the 00:11:47.230 --> 00:11:47.240 align:start position:0% that's just a list a list you know the 00:11:47.240 --> 00:11:49.750 align:start position:0% that's just a list a list you know the rlp<00:11:47.959> encoded<00:11:48.320> rlp<00:11:48.839> list<00:11:49.000> of<00:11:49.160> each<00:11:49.320> log<00:11:49.639> where 00:11:49.750 --> 00:11:49.760 align:start position:0% rlp encoded rlp list of each log where 00:11:49.760 --> 00:11:53.949 align:start position:0% rlp encoded rlp list of each log where each<00:11:49.959> log<00:11:50.240> is<00:11:50.760> en<00:11:51.440> encoded<00:11:52.440> like<00:11:52.680> this<00:11:53.600> and<00:11:53.839> in 00:11:53.949 --> 00:11:53.959 align:start position:0% each log is en encoded like this and in 00:11:53.959 --> 00:11:55.829 align:start position:0% each log is en encoded like this and in the<00:11:54.079> blog<00:11:54.320> in<00:11:54.519> the<00:11:54.600> blog<00:11:54.880> header<00:11:55.440> we<00:11:55.600> have<00:11:55.760> you 00:11:55.829 --> 00:11:55.839 align:start position:0% the blog in the blog header we have you 00:11:55.839 --> 00:11:56.910 align:start position:0% the blog in the blog header we have you know<00:11:56.000> the<00:11:56.079> end<00:11:56.279> state<00:11:56.480> to<00:11:56.600> match<00:11:56.800> the 00:11:56.910 --> 00:11:56.920 align:start position:0% know the end state to match the 00:11:56.920 --> 00:11:59.069 align:start position:0% know the end state to match the intermediate<00:11:57.399> States<00:11:57.800> gas<00:11:58.000> used<00:11:58.320> at<00:11:58.440> the<00:11:58.519> end 00:11:59.069 --> 00:11:59.079 align:start position:0% intermediate States gas used at the end 00:11:59.079 --> 00:12:01.629 align:start position:0% intermediate States gas used at the end and<00:11:59.320> and<00:11:59.560> we<00:11:59.800> have<00:12:00.399> a<00:12:00.639> sort<00:12:00.839> of<00:12:01.000> block<00:12:01.399> wide 00:12:01.629 --> 00:12:01.639 align:start position:0% and and we have a sort of block wide 00:12:01.639 --> 00:12:04.870 align:start position:0% and and we have a sort of block wide balloom<00:12:02.040> filter<00:12:03.040> so<00:12:03.279> each<00:12:03.480> balloom<00:12:03.800> filter<00:12:04.200> is 00:12:04.870 --> 00:12:04.880 align:start position:0% balloom filter so each balloom filter is 00:12:04.880 --> 00:12:07.269 align:start position:0% balloom filter so each balloom filter is is<00:12:05.000> 64<00:12:05.519> bytes<00:12:06.240> and<00:12:06.440> the<00:12:06.600> thing<00:12:06.800> so<00:12:07.040> the<00:12:07.120> way 00:12:07.269 --> 00:12:07.279 align:start position:0% is 64 bytes and the thing so the way 00:12:07.279 --> 00:12:09.230 align:start position:0% is 64 bytes and the thing so the way Bloom<00:12:07.480> filters<00:12:07.880> work<00:12:08.200> just<00:12:08.600> if<00:12:08.720> you<00:12:08.959> if<00:12:09.040> you're 00:12:09.230 --> 00:12:09.240 align:start position:0% Bloom filters work just if you if you're 00:12:09.240 --> 00:12:11.750 align:start position:0% Bloom filters work just if you if you're not<00:12:09.480> clear<00:12:09.800> it's<00:12:09.920> a<00:12:10.079> sort<00:12:10.279> of<00:12:11.000> mechanism<00:12:11.639> where 00:12:11.750 --> 00:12:11.760 align:start position:0% not clear it's a sort of mechanism where 00:12:11.760 --> 00:12:13.710 align:start position:0% not clear it's a sort of mechanism where you<00:12:11.920> can<00:12:12.440> where<00:12:12.560> you<00:12:12.639> can<00:12:12.839> put<00:12:13.079> Keys<00:12:13.399> into<00:12:13.639> the 00:12:13.710 --> 00:12:13.720 align:start position:0% you can where you can put Keys into the 00:12:13.720 --> 00:12:15.629 align:start position:0% you can where you can put Keys into the bloom<00:12:14.000> filter<00:12:14.639> and<00:12:14.760> the<00:12:14.839> bloom<00:12:15.079> filters<00:12:15.399> this 00:12:15.629 --> 00:12:15.639 align:start position:0% bloom filter and the bloom filters this 00:12:15.639 --> 00:12:17.150 align:start position:0% bloom filter and the bloom filters this really<00:12:15.920> compact<00:12:16.320> structure<00:12:16.760> where<00:12:16.880> you<00:12:16.959> can 00:12:17.150 --> 00:12:17.160 align:start position:0% really compact structure where you can 00:12:17.160 --> 00:12:18.829 align:start position:0% really compact structure where you can then<00:12:17.360> check<00:12:17.600> other<00:12:17.839> values<00:12:18.240> again<00:12:18.680> once 00:12:18.829 --> 00:12:18.839 align:start position:0% then check other values again once 00:12:18.839 --> 00:12:20.110 align:start position:0% then check other values again once you've<00:12:19.000> put<00:12:19.120> a<00:12:19.240> some<00:12:19.440> set<00:12:19.560> of<00:12:19.639> keys<00:12:19.880> into<00:12:20.040> the 00:12:20.110 --> 00:12:20.120 align:start position:0% you've put a some set of keys into the 00:12:20.120 --> 00:12:21.350 align:start position:0% you've put a some set of keys into the balloom<00:12:20.360> filter<00:12:20.639> you<00:12:20.720> can<00:12:20.839> check<00:12:21.040> some<00:12:21.199> new 00:12:21.350 --> 00:12:21.360 align:start position:0% balloom filter you can check some new 00:12:21.360 --> 00:12:23.230 align:start position:0% balloom filter you can check some new value<00:12:21.639> against<00:12:21.839> the<00:12:21.959> bloom<00:12:22.240> filter<00:12:23.000> and<00:12:23.120> the 00:12:23.230 --> 00:12:23.240 align:start position:0% value against the bloom filter and the 00:12:23.240 --> 00:12:25.870 align:start position:0% value against the bloom filter and the bloom<00:12:23.519> filter<00:12:23.880> either<00:12:24.279> returns<00:12:25.079> no<00:12:25.440> this<00:12:25.600> key 00:12:25.870 --> 00:12:25.880 align:start position:0% bloom filter either returns no this key 00:12:25.880 --> 00:12:28.069 align:start position:0% bloom filter either returns no this key this<00:12:26.040> key<00:12:26.240> is<00:12:26.720> is<00:12:27.240> definitely<00:12:27.680> not<00:12:27.839> in<00:12:27.959> the 00:12:28.069 --> 00:12:28.079 align:start position:0% this key is is definitely not in the 00:12:28.079 --> 00:12:31.110 align:start position:0% this key is is definitely not in the bloom<00:12:28.360> filter<00:12:29.000> or<00:12:29.240> or<00:12:29.720> maybe<00:12:30.120> this<00:12:30.519> maybe<00:12:30.920> this 00:12:31.110 --> 00:12:31.120 align:start position:0% bloom filter or or maybe this maybe this 00:12:31.120 --> 00:12:33.150 align:start position:0% bloom filter or or maybe this maybe this key<00:12:31.399> maybe<00:12:32.000> this<00:12:32.160> key<00:12:32.360> maybe<00:12:32.600> is<00:12:32.720> in<00:12:32.839> the<00:12:32.920> bloom 00:12:33.150 --> 00:12:33.160 align:start position:0% key maybe this key maybe is in the bloom 00:12:33.160 --> 00:12:35.189 align:start position:0% key maybe this key maybe is in the bloom filter<00:12:33.800> and<00:12:33.920> the<00:12:34.000> reason<00:12:34.320> why<00:12:34.440> it's<00:12:34.639> maybe<00:12:35.000> is 00:12:35.189 --> 00:12:35.199 align:start position:0% filter and the reason why it's maybe is 00:12:35.199 --> 00:12:36.670 align:start position:0% filter and the reason why it's maybe is because<00:12:35.399> it's<00:12:35.800> it's<00:12:35.880> a<00:12:35.959> sort<00:12:36.160> of<00:12:36.279> velocity 00:12:36.670 --> 00:12:36.680 align:start position:0% because it's it's a sort of velocity 00:12:36.680 --> 00:12:38.150 align:start position:0% because it's it's a sort of velocity compression<00:12:37.040> where<00:12:37.199> all<00:12:37.320> the<00:12:37.480> keys<00:12:37.680> are<00:12:37.880> like 00:12:38.150 --> 00:12:38.160 align:start position:0% compression where all the keys are like 00:12:38.160 --> 00:12:39.870 align:start position:0% compression where all the keys are like are<00:12:38.320> in<00:12:38.440> a<00:12:38.560> sense<00:12:38.800> hashed<00:12:39.079> and<00:12:39.240> packed<00:12:39.720> and 00:12:39.870 --> 00:12:39.880 align:start position:0% are in a sense hashed and packed and 00:12:39.880 --> 00:12:41.230 align:start position:0% are in a sense hashed and packed and packed<00:12:40.240> together<00:12:40.440> so<00:12:40.560> you're<00:12:40.680> losing<00:12:41.000> some 00:12:41.230 --> 00:12:41.240 align:start position:0% packed together so you're losing some 00:12:41.240 --> 00:12:43.790 align:start position:0% packed together so you're losing some data<00:12:42.079> so<00:12:42.279> the<00:12:42.399> point<00:12:42.720> is<00:12:43.000> that<00:12:43.160> so<00:12:43.360> the<00:12:43.480> way<00:12:43.639> the 00:12:43.790 --> 00:12:43.800 align:start position:0% data so the point is that so the way the 00:12:43.800 --> 00:12:46.790 align:start position:0% data so the point is that so the way the protocol<00:12:44.639> works<00:12:45.639> is<00:12:46.160> you<00:12:46.320> search<00:12:46.639> the 00:12:46.790 --> 00:12:46.800 align:start position:0% protocol works is you search the 00:12:46.800 --> 00:12:48.910 align:start position:0% protocol works is you search the blockchain<00:12:47.320> for<00:12:47.560> Bloom<00:12:48.000> for<00:12:48.160> Bloom<00:12:48.440> filters 00:12:48.910 --> 00:12:48.920 align:start position:0% blockchain for Bloom for Bloom filters 00:12:48.920 --> 00:12:50.629 align:start position:0% blockchain for Bloom for Bloom filters that<00:12:49.040> are<00:12:49.199> matching<00:12:49.639> some<00:12:49.880> particular<00:12:50.360> topic 00:12:50.629 --> 00:12:50.639 align:start position:0% that are matching some particular topic 00:12:50.639 --> 00:12:52.629 align:start position:0% that are matching some particular topic that<00:12:50.720> you're<00:12:50.880> sort<00:12:51.040> of<00:12:51.199> watching<00:12:51.519> for<00:12:52.320> if<00:12:52.440> you 00:12:52.629 --> 00:12:52.639 align:start position:0% that you're sort of watching for if you 00:12:52.639 --> 00:12:54.189 align:start position:0% that you're sort of watching for if you find<00:12:52.920> the<00:12:53.160> block<00:12:53.440> that<00:12:53.600> matches<00:12:53.959> what<00:12:54.079> you 00:12:54.189 --> 00:12:54.199 align:start position:0% find the block that matches what you 00:12:54.199 --> 00:12:56.670 align:start position:0% find the block that matches what you want<00:12:54.600> you<00:12:54.760> check<00:12:55.040> every<00:12:55.279> transaction<00:12:56.120> you<00:12:56.240> see 00:12:56.670 --> 00:12:56.680 align:start position:0% want you check every transaction you see 00:12:56.680 --> 00:12:58.670 align:start position:0% want you check every transaction you see which<00:12:56.880> transaction<00:12:57.399> or<00:12:57.560> which<00:12:57.720> transactions 00:12:58.670 --> 00:12:58.680 align:start position:0% which transaction or which transactions 00:12:58.680 --> 00:13:00.310 align:start position:0% which transaction or which transactions match<00:12:58.959> that<00:12:59.440> have<00:12:59.560> a<00:12:59.680> bloom<00:12:59.920> filter<00:13:00.199> that 00:13:00.310 --> 00:13:00.320 align:start position:0% match that have a bloom filter that 00:13:00.320 --> 00:13:02.470 align:start position:0% match that have a bloom filter that matches<00:13:00.600> that<00:13:00.800> particular<00:13:01.240> topic<00:13:02.160> and<00:13:02.279> then 00:13:02.470 --> 00:13:02.480 align:start position:0% matches that particular topic and then 00:13:02.480 --> 00:13:03.990 align:start position:0% matches that particular topic and then once<00:13:02.600> you<00:13:02.920> determine<00:13:03.519> once<00:13:03.639> you<00:13:03.720> find 00:13:03.990 --> 00:13:04.000 align:start position:0% once you determine once you find 00:13:04.000 --> 00:13:06.550 align:start position:0% once you determine once you find transactions<00:13:04.880> you<00:13:05.000> would<00:13:05.279> actually<00:13:05.680> ask<00:13:05.959> for 00:13:06.550 --> 00:13:06.560 align:start position:0% transactions you would actually ask for 00:13:06.560 --> 00:13:08.350 align:start position:0% transactions you would actually ask for you<00:13:06.680> would<00:13:06.839> actually<00:13:07.160> ask<00:13:07.360> for<00:13:07.639> know<00:13:07.800> the<00:13:07.920> are 00:13:08.350 --> 00:13:08.360 align:start position:0% you would actually ask for know the are 00:13:08.360 --> 00:13:10.790 align:start position:0% you would actually ask for know the are the<00:13:09.079> the<00:13:09.240> Merle<00:13:09.720> proof<00:13:10.079> going<00:13:10.279> going<00:13:10.480> down<00:13:10.639> to 00:13:10.790 --> 00:13:10.800 align:start position:0% the the Merle proof going going down to 00:13:10.800 --> 00:13:12.629 align:start position:0% the the Merle proof going going down to the<00:13:10.959> logs<00:13:11.680> which<00:13:11.800> would<00:13:11.959> tell<00:13:12.120> you<00:13:12.320> whether<00:13:12.480> or 00:13:12.629 --> 00:13:12.639 align:start position:0% the logs which would tell you whether or 00:13:12.639 --> 00:13:14.550 align:start position:0% the logs which would tell you whether or not<00:13:13.120> logs<00:13:13.399> were<00:13:13.600> actually<00:13:13.920> there<00:13:14.079> and<00:13:14.199> if<00:13:14.320> logs 00:13:14.550 --> 00:13:14.560 align:start position:0% not logs were actually there and if logs 00:13:14.560 --> 00:13:15.870 align:start position:0% not logs were actually there and if logs were<00:13:14.760> there<00:13:14.920> what<00:13:15.040> the<00:13:15.160> actual<00:13:15.440> content<00:13:15.760> of 00:13:15.870 --> 00:13:15.880 align:start position:0% were there what the actual content of 00:13:15.880 --> 00:13:19.389 align:start position:0% were there what the actual content of the<00:13:16.800> so<00:13:17.279> uh<00:13:17.480> the<00:13:18.199> minor<00:13:18.600> thing<00:13:18.800> that<00:13:18.959> has<00:13:19.120> been 00:13:19.389 --> 00:13:19.399 align:start position:0% the so uh the minor thing that has been 00:13:19.399 --> 00:13:21.629 align:start position:0% the so uh the minor thing that has been uh<00:13:19.519> missed<00:13:19.800> from<00:13:20.000> this<00:13:20.160> particular<00:13:20.600> list<00:13:21.360> is 00:13:21.629 --> 00:13:21.639 align:start position:0% uh missed from this particular list is 00:13:21.639 --> 00:13:24.870 align:start position:0% uh missed from this particular list is that<00:13:22.360> um<00:13:23.199> we<00:13:23.320> can<00:13:23.519> search<00:13:23.880> the<00:13:24.040> header<00:13:24.360> for<00:13:24.639> for 00:13:24.870 --> 00:13:24.880 align:start position:0% that um we can search the header for for 00:13:24.880 --> 00:13:26.629 align:start position:0% that um we can search the header for for blooms<00:13:25.360> that<00:13:25.600> that<00:13:25.839> tell<00:13:26.079> us<00:13:26.320> that<00:13:26.480> a 00:13:26.629 --> 00:13:26.639 align:start position:0% blooms that that tell us that a 00:13:26.639 --> 00:13:28.389 align:start position:0% blooms that that tell us that a particular<00:13:27.079> block<00:13:27.600> may<00:13:27.880> contain<00:13:28.240> a 00:13:28.389 --> 00:13:28.399 align:start position:0% particular block may contain a 00:13:28.399 --> 00:13:30.550 align:start position:0% particular block may contain a transaction<00:13:29.399> that<00:13:29.600> had<00:13:29.720> a<00:13:29.920> log<00:13:30.240> that<00:13:30.360> we're 00:13:30.550 --> 00:13:30.560 align:start position:0% transaction that had a log that we're 00:13:30.560 --> 00:13:33.350 align:start position:0% transaction that had a log that we're interested<00:13:31.000> in<00:13:31.760> following<00:13:32.360> that<00:13:33.000> we<00:13:33.120> can 00:13:33.350 --> 00:13:33.360 align:start position:0% interested in following that we can 00:13:33.360 --> 00:13:35.470 align:start position:0% interested in following that we can actually<00:13:33.720> request<00:13:34.240> the<00:13:34.440> transaction<00:13:35.040> receipt 00:13:35.470 --> 00:13:35.480 align:start position:0% actually request the transaction receipt 00:13:35.480 --> 00:13:38.110 align:start position:0% actually request the transaction receipt block<00:13:36.279> and<00:13:36.480> search<00:13:36.839> in<00:13:37.199> that<00:13:37.360> block<00:13:37.839> for<00:13:38.000> the 00:13:38.110 --> 00:13:38.120 align:start position:0% block and search in that block for the 00:13:38.120 --> 00:13:40.269 align:start position:0% block and search in that block for the bloom<00:13:38.440> filters<00:13:39.000> so<00:13:39.160> the<00:13:39.240> blooms<00:13:39.560> are<00:13:39.720> also<00:13:40.079> for 00:13:40.269 --> 00:13:40.279 align:start position:0% bloom filters so the blooms are also for 00:13:40.279 --> 00:13:41.829 align:start position:0% bloom filters so the blooms are also for each<00:13:40.519> transaction<00:13:41.079> actually<00:13:41.360> put<00:13:41.519> in<00:13:41.680> that 00:13:41.829 --> 00:13:41.839 align:start position:0% each transaction actually put in that 00:13:41.839 --> 00:13:43.550 align:start position:0% each transaction actually put in that block<00:13:42.360> before<00:13:42.639> we<00:13:42.839> actually<00:13:43.120> go<00:13:43.279> ahead<00:13:43.440> and 00:13:43.550 --> 00:13:43.560 align:start position:0% block before we actually go ahead and 00:13:43.560 --> 00:13:45.150 align:start position:0% block before we actually go ahead and search<00:13:43.839> for<00:13:43.959> the<00:13:44.040> log<00:13:44.240> entries<00:13:44.680> themselves<00:13:44.959> so 00:13:45.150 --> 00:13:45.160 align:start position:0% search for the log entries themselves so 00:13:45.160 --> 00:13:46.629 align:start position:0% search for the log entries themselves so it's<00:13:45.279> a<00:13:45.480> little<00:13:45.839> it's<00:13:46.000> a<00:13:46.199> little<00:13:46.440> more 00:13:46.629 --> 00:13:46.639 align:start position:0% it's a little it's a little more 00:13:46.639 --> 00:13:48.509 align:start position:0% it's a little it's a little more efficient<00:13:47.040> before<00:13:47.600> well<00:13:47.839> search<00:13:48.199> block 00:13:48.509 --> 00:13:48.519 align:start position:0% efficient before well search block 00:13:48.519 --> 00:13:50.590 align:start position:0% efficient before well search block search<00:13:48.839> for<00:13:49.079> search<00:13:49.360> blockchain<00:13:49.760> for<00:13:49.959> blocks 00:13:50.590 --> 00:13:50.600 align:start position:0% search for search blockchain for blocks 00:13:50.600 --> 00:13:52.069 align:start position:0% search for search blockchain for blocks search<00:13:50.920> block<00:13:51.160> for<00:13:51.279> transaction<00:13:51.759> search 00:13:52.069 --> 00:13:52.079 align:start position:0% search block for transaction search 00:13:52.079 --> 00:13:53.670 align:start position:0% search block for transaction search transaction<00:13:52.639> well<00:13:52.720> I<00:13:52.839> guess<00:13:53.199> what<00:13:53.320> not<00:13:53.480> to 00:13:53.670 --> 00:13:53.680 align:start position:0% transaction well I guess what not to 00:13:53.680 --> 00:13:55.829 align:start position:0% transaction well I guess what not to clear<00:13:53.839> but<00:13:53.959> oh<00:13:54.079> well 00:13:55.829 --> 00:13:55.839 align:start position:0% clear but oh well 00:13:55.839 --> 00:14:00.069 align:start position:0% clear but oh well so<00:13:56.839> yeah<00:13:57.519> so<00:13:57.920> basic<00:13:58.279> road<00:13:58.600> map<00:13:58.839> is<00:13:59.120> is<00:13:59.360> that<00:13:59.880> the 00:14:00.069 --> 00:14:00.079 align:start position:0% so yeah so basic road map is is that the 00:14:00.079 --> 00:14:01.710 align:start position:0% so yeah so basic road map is is that the client<00:14:00.399> that<00:14:00.519> we're<00:14:00.639> going<00:14:00.720> to<00:14:00.839> have<00:14:00.959> for<00:14:01.160> 1.0 00:14:01.710 --> 00:14:01.720 align:start position:0% client that we're going to have for 1.0 00:14:01.720 --> 00:14:03.269 align:start position:0% client that we're going to have for 1.0 is<00:14:01.920> archive<00:14:02.320> node<00:14:02.639> simplest<00:14:02.959> thing<00:14:03.120> to 00:14:03.269 --> 00:14:03.279 align:start position:0% is archive node simplest thing to 00:14:03.279 --> 00:14:05.990 align:start position:0% is archive node simplest thing to implement<00:14:03.639> it<00:14:03.759> stores<00:14:04.440> everything<00:14:05.440> um<00:14:05.720> then 00:14:05.990 --> 00:14:06.000 align:start position:0% implement it stores everything um then 00:14:06.000 --> 00:14:08.069 align:start position:0% implement it stores everything um then after<00:14:06.360> that<00:14:06.920> we<00:14:07.079> wants<00:14:07.279> to<00:14:07.399> get<00:14:07.560> into<00:14:07.839> is<00:14:07.959> he 00:14:08.069 --> 00:14:08.079 align:start position:0% after that we wants to get into is he 00:14:08.079 --> 00:14:09.670 align:start position:0% after that we wants to get into is he wants<00:14:08.240> to<00:14:08.480> move<00:14:08.720> from<00:14:08.880> archive<00:14:09.279> node<00:14:09.480> so<00:14:09.600> what 00:14:09.670 --> 00:14:09.680 align:start position:0% wants to move from archive node so what 00:14:09.680 --> 00:14:11.509 align:start position:0% wants to move from archive node so what we're<00:14:09.839> calling<00:14:10.040> full<00:14:10.320> node<00:14:10.839> so<00:14:11.040> full<00:14:11.279> node 00:14:11.509 --> 00:14:11.519 align:start position:0% we're calling full node so full node 00:14:11.519 --> 00:14:13.470 align:start position:0% we're calling full node so full node store<00:14:11.839> the<00:14:11.959> entire<00:14:12.320> state<00:14:13.000> but<00:14:13.160> they<00:14:13.279> only 00:14:13.470 --> 00:14:13.480 align:start position:0% store the entire state but they only 00:14:13.480 --> 00:14:15.230 align:start position:0% store the entire state but they only store<00:14:13.880> recent<00:14:14.199> history<00:14:14.560> so<00:14:14.680> you<00:14:14.759> can<00:14:14.920> imagine 00:14:15.230 --> 00:14:15.240 align:start position:0% store recent history so you can imagine 00:14:15.240 --> 00:14:17.310 align:start position:0% store recent history so you can imagine they<00:14:15.360> store<00:14:15.959> the<00:14:16.120> state<00:14:16.360> Roots<00:14:16.800> going<00:14:17.079> back 00:14:17.310 --> 00:14:17.320 align:start position:0% they store the state Roots going back 00:14:17.320 --> 00:14:19.230 align:start position:0% they store the state Roots going back maybe<00:14:17.560> a<00:14:17.720> week<00:14:18.160> and<00:14:18.279> then<00:14:18.399> they<00:14:18.519> just<00:14:18.680> store 00:14:19.230 --> 00:14:19.240 align:start position:0% maybe a week and then they just store 00:14:19.240 --> 00:14:21.030 align:start position:0% maybe a week and then they just store some<00:14:19.399> more<00:14:19.560> block<00:14:19.839> headers<00:14:20.240> going<00:14:20.519> going<00:14:20.839> back 00:14:21.030 --> 00:14:21.040 align:start position:0% some more block headers going going back 00:14:21.040 --> 00:14:24.150 align:start position:0% some more block headers going going back maybe<00:14:21.240> you<00:14:21.360> know<00:14:21.480> a<00:14:21.639> month<00:14:21.920> or<00:14:22.800> a<00:14:22.920> month<00:14:23.199> or<00:14:23.320> two 00:14:24.150 --> 00:14:24.160 align:start position:0% maybe you know a month or a month or two 00:14:24.160 --> 00:14:25.990 align:start position:0% maybe you know a month or a month or two and<00:14:24.560> next<00:14:24.759> store<00:14:24.959> transactions<00:14:25.560> going<00:14:25.800> going 00:14:25.990 --> 00:14:26.000 align:start position:0% and next store transactions going going 00:14:26.000 --> 00:14:27.870 align:start position:0% and next store transactions going going back<00:14:26.160> that<00:14:26.320> far<00:14:26.519> as<00:14:26.680> well<00:14:27.240> and<00:14:27.360> then<00:14:27.519> if<00:14:27.680> they 00:14:27.870 --> 00:14:27.880 align:start position:0% back that far as well and then if they 00:14:27.880 --> 00:14:29.829 align:start position:0% back that far as well and then if they wants<00:14:28.079> to<00:14:28.240> grab<00:14:28.480> ancient<00:14:28.759> history 00:14:29.829 --> 00:14:29.839 align:start position:0% wants to grab ancient history 00:14:29.839 --> 00:14:31.350 align:start position:0% wants to grab ancient history then<00:14:30.399> like<00:14:30.519> they<00:14:30.600> would<00:14:30.759> just<00:14:30.880> maintain<00:14:31.279> they 00:14:31.350 --> 00:14:31.360 align:start position:0% then like they would just maintain they 00:14:31.360 --> 00:14:32.829 align:start position:0% then like they would just maintain they would<00:14:31.480> just<00:14:31.600> maintain<00:14:32.040> some<00:14:32.399> some<00:14:32.560> block 00:14:32.829 --> 00:14:32.839 align:start position:0% would just maintain some some block 00:14:32.839 --> 00:14:34.509 align:start position:0% would just maintain some some block headers<00:14:33.279> and<00:14:33.440> they<00:14:33.560> would<00:14:33.759> use<00:14:34.199> basically 00:14:34.509 --> 00:14:34.519 align:start position:0% headers and they would use basically 00:14:34.519 --> 00:14:35.949 align:start position:0% headers and they would use basically they<00:14:34.639> would<00:14:34.800> use<00:14:35.040> the<00:14:35.240> like<00:14:35.480> light<00:14:35.680> node 00:14:35.949 --> 00:14:35.959 align:start position:0% they would use the like light node 00:14:35.959 --> 00:14:38.069 align:start position:0% they would use the like light node protocol<00:14:36.320> to<00:14:36.440> ask<00:14:36.600> for<00:14:36.720> ancient<00:14:37.079> history<00:14:37.920> and 00:14:38.069 --> 00:14:38.079 align:start position:0% protocol to ask for ancient history and 00:14:38.079 --> 00:14:39.470 align:start position:0% protocol to ask for ancient history and so<00:14:38.240> full<00:14:38.480> nodes<00:14:38.680> are<00:14:38.839> actually<00:14:39.079> much<00:14:39.240> closer 00:14:39.470 --> 00:14:39.480 align:start position:0% so full nodes are actually much closer 00:14:39.480 --> 00:14:41.069 align:start position:0% so full nodes are actually much closer to<00:14:39.600> light<00:14:39.759> nodes<00:14:39.959> than<00:14:40.040> the<00:14:40.360> archive<00:14:40.720> nodes<00:14:40.959> in 00:14:41.069 --> 00:14:41.079 align:start position:0% to light nodes than the archive nodes in 00:14:41.079 --> 00:14:42.829 align:start position:0% to light nodes than the archive nodes in some<00:14:41.279> sense<00:14:41.880> and<00:14:42.000> then<00:14:42.160> light<00:14:42.360> nodes<00:14:42.639> will 00:14:42.829 --> 00:14:42.839 align:start position:0% some sense and then light nodes will 00:14:42.839 --> 00:14:44.990 align:start position:0% some sense and then light nodes will just<00:14:43.000> download<00:14:43.399> Walkers<00:14:43.920> by<00:14:44.079> default<00:14:44.639> and<00:14:44.920> we 00:14:44.990 --> 00:14:45.000 align:start position:0% just download Walkers by default and we 00:14:45.000 --> 00:14:46.790 align:start position:0% just download Walkers by default and we are<00:14:45.199> expecting<00:14:45.560> it<00:14:45.680> will<00:14:45.920> take<00:14:46.199> quite<00:14:46.360> a<00:14:46.519> while 00:14:46.790 --> 00:14:46.800 align:start position:0% are expecting it will take quite a while 00:14:46.800 --> 00:14:49.030 align:start position:0% are expecting it will take quite a while for<00:14:47.360> the<00:14:47.519> full<00:14:47.839> sort<00:14:48.000> of<00:14:48.160> leline<00:14:48.639> technology 00:14:49.030 --> 00:14:49.040 align:start position:0% for the full sort of leline technology 00:14:49.040 --> 00:14:50.389 align:start position:0% for the full sort of leline technology to<00:14:49.160> get<00:14:49.279> rolled<00:14:49.560> out<00:14:49.800> just<00:14:50.000> because<00:14:50.240> it 00:14:50.389 --> 00:14:50.399 align:start position:0% to get rolled out just because it 00:14:50.399 --> 00:14:52.629 align:start position:0% to get rolled out just because it involves<00:14:50.880> a<00:14:51.440> it<00:14:51.600> it<00:14:51.759> involves<00:14:52.120> a<00:14:52.240> whole<00:14:52.440> bunch 00:14:52.629 --> 00:14:52.639 align:start position:0% involves a it it involves a whole bunch 00:14:52.639 --> 00:14:56.189 align:start position:0% involves a it it involves a whole bunch of<00:14:52.800> these<00:14:53.199> various 00:14:56.189 --> 00:14:56.199 align:start position:0% 00:14:56.199 --> 00:14:59.350 align:start position:0% prerequisites<00:14:57.199> yeah<00:14:57.839> so<00:14:58.120> from<00:14:58.680> right<00:14:58.800> so<00:14:59.240> how 00:14:59.350 --> 00:14:59.360 align:start position:0% prerequisites yeah so from right so how 00:14:59.360 --> 00:15:00.550 align:start position:0% prerequisites yeah so from right so how does<00:14:59.519> this<00:14:59.639> work<00:14:59.800> from<00:14:59.920> a<00:15:00.040> networking 00:15:00.550 --> 00:15:00.560 align:start position:0% does this work from a networking 00:15:00.560 --> 00:15:04.389 align:start position:0% does this work from a networking standpoint<00:15:01.480> so 00:15:04.389 --> 00:15:04.399 align:start position:0% standpoint so 00:15:04.399 --> 00:15:09.430 align:start position:0% standpoint so um<00:15:05.399> what's<00:15:06.000> important<00:15:07.000> is<00:15:07.560> that<00:15:08.560> when<00:15:08.959> a<00:15:09.120> light 00:15:09.430 --> 00:15:09.440 align:start position:0% um what's important is that when a light 00:15:09.440 --> 00:15:12.030 align:start position:0% um what's important is that when a light client<00:15:09.720> wants<00:15:09.959> to<00:15:10.279> operate<00:15:11.279> it<00:15:11.440> does<00:15:11.680> not<00:15:11.920> have 00:15:12.030 --> 00:15:12.040 align:start position:0% client wants to operate it does not have 00:15:12.040 --> 00:15:15.550 align:start position:0% client wants to operate it does not have to<00:15:12.560> request<00:15:13.560> a<00:15:14.000> proof<00:15:14.720> um<00:15:14.920> which<00:15:15.120> are 00:15:15.550 --> 00:15:15.560 align:start position:0% to request a proof um which are 00:15:15.560 --> 00:15:17.629 align:start position:0% to request a proof um which are necessarily<00:15:16.560> things<00:15:16.759> that<00:15:16.839> are<00:15:17.040> customized 00:15:17.629 --> 00:15:17.639 align:start position:0% necessarily things that are customized 00:15:17.639 --> 00:15:19.629 align:start position:0% necessarily things that are customized for<00:15:17.839> the<00:15:18.000> for<00:15:18.120> the<00:15:18.320> requester<00:15:19.160> from<00:15:19.360> some<00:15:19.519> of 00:15:19.629 --> 00:15:19.639 align:start position:0% for the for the requester from some of 00:15:19.639 --> 00:15:21.069 align:start position:0% for the for the requester from some of the<00:15:19.759> node<00:15:20.120> if<00:15:20.240> that<00:15:20.360> were<00:15:20.519> the<00:15:20.639> case<00:15:20.880> then 00:15:21.069 --> 00:15:21.079 align:start position:0% the node if that were the case then 00:15:21.079 --> 00:15:22.870 align:start position:0% the node if that were the case then effectively<00:15:21.639> like<00:15:21.880> clients<00:15:22.240> would<00:15:22.440> be 00:15:22.870 --> 00:15:22.880 align:start position:0% effectively like clients would be 00:15:22.880 --> 00:15:25.230 align:start position:0% effectively like clients would be literally<00:15:23.399> clients<00:15:24.399> and<00:15:24.720> the<00:15:24.839> nodes<00:15:25.120> that 00:15:25.230 --> 00:15:25.240 align:start position:0% literally clients and the nodes that 00:15:25.240 --> 00:15:27.189 align:start position:0% literally clients and the nodes that they<00:15:25.360> come<00:15:25.560> from<00:15:25.759> the<00:15:25.920> archive<00:15:26.279> nodes<00:15:26.680> or 00:15:27.189 --> 00:15:27.199 align:start position:0% they come from the archive nodes or 00:15:27.199 --> 00:15:29.949 align:start position:0% they come from the archive nodes or maybe<00:15:27.519> the<00:15:27.600> full<00:15:27.839> nodes<00:15:28.480> would<00:15:28.639> be<00:15:28.759> so<00:15:29.000> service 00:15:29.949 --> 00:15:29.959 align:start position:0% maybe the full nodes would be so service 00:15:29.959 --> 00:15:31.710 align:start position:0% maybe the full nodes would be so service and<00:15:30.120> that's<00:15:30.319> not<00:15:30.480> an<00:15:30.720> especially<00:15:31.240> nice<00:15:31.440> way<00:15:31.560> of 00:15:31.710 --> 00:15:31.720 align:start position:0% and that's not an especially nice way of 00:15:31.720 --> 00:15:33.710 align:start position:0% and that's not an especially nice way of doing<00:15:31.959> it<00:15:32.360> it<00:15:32.480> sort<00:15:32.639> of<00:15:33.120> reduces<00:15:33.560> the 00:15:33.710 --> 00:15:33.720 align:start position:0% doing it it sort of reduces the 00:15:33.720 --> 00:15:35.350 align:start position:0% doing it it sort of reduces the decentral<00:15:34.399> of<00:15:34.560> the 00:15:35.350 --> 00:15:35.360 align:start position:0% decentral of the 00:15:35.360 --> 00:15:37.309 align:start position:0% decentral of the network 00:15:37.309 --> 00:15:37.319 align:start position:0% network 00:15:37.319 --> 00:15:39.710 align:start position:0% network so<00:15:38.319> rather<00:15:38.680> than<00:15:38.839> so<00:15:39.000> as<00:15:39.079> an<00:15:39.199> alternative<00:15:39.600> to 00:15:39.710 --> 00:15:39.720 align:start position:0% so rather than so as an alternative to 00:15:39.720 --> 00:15:41.189 align:start position:0% so rather than so as an alternative to the<00:15:39.800> ask<00:15:40.000> for<00:15:40.120> the<00:15:40.240> proof<00:15:40.480> mechanism<00:15:41.079> which 00:15:41.189 --> 00:15:41.199 align:start position:0% the ask for the proof mechanism which 00:15:41.199 --> 00:15:42.389 align:start position:0% the ask for the proof mechanism which may<00:15:41.360> still<00:15:41.519> be<00:15:41.680> necessary<00:15:42.040> for<00:15:42.199> some 00:15:42.389 --> 00:15:42.399 align:start position:0% may still be necessary for some 00:15:42.399 --> 00:15:43.829 align:start position:0% may still be necessary for some particular<00:15:42.800> things<00:15:43.079> depending<00:15:43.480> on<00:15:43.639> whether 00:15:43.829 --> 00:15:43.839 align:start position:0% particular things depending on whether 00:15:43.839 --> 00:15:46.590 align:start position:0% particular things depending on whether the<00:15:43.959> state<00:15:44.279> tree<00:15:45.120> is<00:15:45.639> uh<00:15:45.920> is<00:15:46.199> is<00:15:46.360> well 00:15:46.590 --> 00:15:46.600 align:start position:0% the state tree is uh is is well 00:15:46.600 --> 00:15:48.030 align:start position:0% the state tree is uh is is well distributed<00:15:47.120> and<00:15:47.240> well<00:15:47.399> stored<00:15:47.720> by<00:15:47.839> the 00:15:48.030 --> 00:15:48.040 align:start position:0% distributed and well stored by the 00:15:48.040 --> 00:15:52.069 align:start position:0% distributed and well stored by the network<00:15:49.040> is<00:15:49.480> um<00:15:49.680> to<00:15:50.160> store<00:15:51.160> the<00:15:51.399> various 00:15:52.069 --> 00:15:52.079 align:start position:0% network is um to store the various 00:15:52.079 --> 00:15:55.230 align:start position:0% network is um to store the various portions<00:15:52.839> of<00:15:53.399> things<00:15:53.759> like<00:15:54.079> uh<00:15:54.240> headers 00:15:55.230 --> 00:15:55.240 align:start position:0% portions of things like uh headers 00:15:55.240 --> 00:15:58.069 align:start position:0% portions of things like uh headers blocks<00:15:56.079> and<00:15:56.319> transaction<00:15:56.920> receipts<00:15:57.759> on<00:15:57.920> the 00:15:58.069 --> 00:15:58.079 align:start position:0% blocks and transaction receipts on the 00:15:58.079 --> 00:15:59.670 align:start position:0% blocks and transaction receipts on the DHT<00:15:58.639> itself 00:15:59.670 --> 00:15:59.680 align:start position:0% DHT itself 00:15:59.680 --> 00:16:01.670 align:start position:0% DHT itself so<00:16:00.240> these<00:16:00.360> are<00:16:00.560> necess<00:16:00.920> these<00:16:01.040> are<00:16:01.240> naturally 00:16:01.670 --> 00:16:01.680 align:start position:0% so these are necess these are naturally 00:16:01.680 --> 00:16:03.550 align:start position:0% so these are necess these are naturally things<00:16:02.040> that<00:16:02.240> are<00:16:02.519> identified<00:16:03.040> by<00:16:03.160> the<00:16:03.279> hash 00:16:03.550 --> 00:16:03.560 align:start position:0% things that are identified by the hash 00:16:03.560 --> 00:16:05.430 align:start position:0% things that are identified by the hash they're<00:16:03.800> actually<00:16:04.120> identified<00:16:04.639> by<00:16:05.079> probably 00:16:05.430 --> 00:16:05.440 align:start position:0% they're actually identified by probably 00:16:05.440 --> 00:16:08.230 align:start position:0% they're actually identified by probably the<00:16:05.519> same<00:16:05.759> hash<00:16:06.079> within<00:16:06.399> the<00:16:06.720> um<00:16:07.639> within<00:16:07.959> the 00:16:08.230 --> 00:16:08.240 align:start position:0% the same hash within the um within the 00:16:08.240 --> 00:16:11.230 align:start position:0% the same hash within the um within the the<00:16:08.360> blockchain<00:16:09.079> itself<00:16:10.079> and<00:16:10.480> the<00:16:10.680> idea<00:16:11.040> is 00:16:11.230 --> 00:16:11.240 align:start position:0% the blockchain itself and the idea is 00:16:11.240 --> 00:16:14.990 align:start position:0% the blockchain itself and the idea is that<00:16:11.399> like<00:16:11.720> clients<00:16:12.480> themselves<00:16:13.480> are<00:16:14.199> a<00:16:14.800> a 00:16:14.990 --> 00:16:15.000 align:start position:0% that like clients themselves are a a 00:16:15.000 --> 00:16:17.710 align:start position:0% that like clients themselves are a a contributor<00:16:15.759> to<00:16:15.959> this<00:16:16.120> DHT<00:16:16.839> so<00:16:17.040> they<00:16:17.240> do<00:16:17.519> their 00:16:17.710 --> 00:16:17.720 align:start position:0% contributor to this DHT so they do their 00:16:17.720 --> 00:16:20.829 align:start position:0% contributor to this DHT so they do their own<00:16:18.480> um<00:16:18.720> bit<00:16:19.440> in<00:16:19.560> terms<00:16:19.839> of<00:16:20.000> storing<00:16:20.600> maybe 00:16:20.829 --> 00:16:20.839 align:start position:0% own um bit in terms of storing maybe 00:16:20.839 --> 00:16:22.749 align:start position:0% own um bit in terms of storing maybe some<00:16:21.040> transaction<00:16:21.519> receipts<00:16:22.000> some<00:16:22.199> blocks 00:16:22.749 --> 00:16:22.759 align:start position:0% some transaction receipts some blocks 00:16:22.759 --> 00:16:24.870 align:start position:0% some transaction receipts some blocks and<00:16:22.959> some<00:16:23.160> headers<00:16:24.000> um<00:16:24.199> that<00:16:24.360> they<00:16:24.519> can 00:16:24.870 --> 00:16:24.880 align:start position:0% and some headers um that they can 00:16:24.880 --> 00:16:26.749 align:start position:0% and some headers um that they can obviously<00:16:25.639> should<00:16:25.920> the<00:16:26.040> chance<00:16:26.319> happen<00:16:26.639> that 00:16:26.749 --> 00:16:26.759 align:start position:0% obviously should the chance happen that 00:16:26.759 --> 00:16:28.509 align:start position:0% obviously should the chance happen that they<00:16:26.880> need<00:16:27.079> it<00:16:27.279> they<00:16:27.399> can<00:16:27.480> use<00:16:27.880> themselves<00:16:28.360> but 00:16:28.509 --> 00:16:28.519 align:start position:0% they need it they can use themselves but 00:16:28.519 --> 00:16:30.470 align:start position:0% they need it they can use themselves but that<00:16:28.639> they<00:16:28.720> can<00:16:28.920> in<00:16:29.120> a<00:16:29.519> in<00:16:29.639> a<00:16:29.759> bit<00:16:29.959> torrent<00:16:30.319> like 00:16:30.470 --> 00:16:30.480 align:start position:0% that they can in a in a bit torrent like 00:16:30.480 --> 00:16:32.550 align:start position:0% that they can in a in a bit torrent like tip<00:16:30.680> Fort<00:16:30.880> tap<00:16:31.079> fashion<00:16:31.759> um<00:16:31.920> exchanged<00:16:32.440> with 00:16:32.550 --> 00:16:32.560 align:start position:0% tip Fort tap fashion um exchanged with 00:16:32.560 --> 00:16:35.110 align:start position:0% tip Fort tap fashion um exchanged with other<00:16:32.759> like<00:16:33.000> clients<00:16:33.560> in<00:16:33.680> order<00:16:33.959> to<00:16:34.319> provide 00:16:35.110 --> 00:16:35.120 align:start position:0% other like clients in order to provide 00:16:35.120 --> 00:16:36.550 align:start position:0% other like clients in order to provide information<00:16:35.560> across<00:16:35.839> the<00:16:35.920> network<00:16:36.319> without 00:16:36.550 --> 00:16:36.560 align:start position:0% information across the network without 00:16:36.560 --> 00:16:38.910 align:start position:0% information across the network without having<00:16:36.800> this<00:16:37.279> Reliance<00:16:37.759> upon<00:16:38.079> archive<00:16:38.560> or<00:16:38.800> or 00:16:38.910 --> 00:16:38.920 align:start position:0% having this Reliance upon archive or or 00:16:38.920 --> 00:16:40.550 align:start position:0% having this Reliance upon archive or or maybe<00:16:39.120> for 00:16:40.550 --> 00:16:40.560 align:start position:0% maybe for 00:16:40.560 --> 00:16:44.110 align:start position:0% maybe for modes<00:16:41.560> so<00:16:41.920> yeah<00:16:42.040> so<00:16:42.240> the<00:16:42.399> idea<00:16:42.839> is<00:16:43.240> that<00:16:43.800> once 00:16:44.110 --> 00:16:44.120 align:start position:0% modes so yeah so the idea is that once 00:16:44.120 --> 00:16:45.949 align:start position:0% modes so yeah so the idea is that once once<00:16:44.319> again<00:16:44.519> and<00:16:44.680> actually<00:16:45.040> sort<00:16:45.199> of<00:16:45.560> works 00:16:45.949 --> 00:16:45.959 align:start position:0% once again and actually sort of works 00:16:45.959 --> 00:16:48.389 align:start position:0% once again and actually sort of works nicely<00:16:46.720> from<00:16:46.920> an<00:16:47.079> implementation<00:16:47.759> standpoint 00:16:48.389 --> 00:16:48.399 align:start position:0% nicely from an implementation standpoint 00:16:48.399 --> 00:16:51.030 align:start position:0% nicely from an implementation standpoint is<00:16:48.600> that<00:16:49.399> the<00:16:49.560> way<00:16:49.839> that<00:16:50.360> it's<00:16:50.680> all<00:16:50.800> you're 00:16:51.030 --> 00:16:51.040 align:start position:0% is that the way that it's all you're 00:16:51.040 --> 00:16:52.670 align:start position:0% is that the way that it's all you're doing<00:16:51.440> is<00:16:51.600> that<00:16:51.720> you're<00:16:51.959> grab<00:16:52.319> instead<00:16:52.560> of 00:16:52.670 --> 00:16:52.680 align:start position:0% doing is that you're grab instead of 00:16:52.680 --> 00:16:54.590 align:start position:0% doing is that you're grab instead of grabbing<00:16:53.319> nodes<00:16:53.680> from<00:16:53.800> a<00:16:53.959> database<00:16:54.399> you're 00:16:54.590 --> 00:16:54.600 align:start position:0% grabbing nodes from a database you're 00:16:54.600 --> 00:16:57.350 align:start position:0% grabbing nodes from a database you're just<00:16:54.800> grabbing<00:16:55.120> nodes<00:16:55.519> from<00:16:55.800> this<00:16:56.120> DHT<00:16:57.120> so 00:16:57.350 --> 00:16:57.360 align:start position:0% just grabbing nodes from this DHT so 00:16:57.360 --> 00:16:58.910 align:start position:0% just grabbing nodes from this DHT so you're<00:16:57.480> just<00:16:57.600> sort<00:16:57.759> of<00:16:57.880> using<00:16:58.240> that<00:16:58.519> you<00:16:58.600> can 00:16:58.910 --> 00:16:58.920 align:start position:0% you're just sort of using that you can 00:16:58.920 --> 00:17:00.509 align:start position:0% you're just sort of using that you can think<00:16:59.040> of<00:16:59.160> it<00:16:59.279> as<00:16:59.440> like<00:16:59.560> using<00:16:59.839> the<00:16:59.959> internet 00:17:00.509 --> 00:17:00.519 align:start position:0% think of it as like using the internet 00:17:00.519 --> 00:17:03.189 align:start position:0% think of it as like using the internet as<00:17:00.959> a<00:17:01.079> sort<00:17:01.279> of<00:17:01.440> extra<00:17:01.759> hard<00:17:02.000> drive<00:17:02.920> and<00:17:03.079> this 00:17:03.189 --> 00:17:03.199 align:start position:0% as a sort of extra hard drive and this 00:17:03.199 --> 00:17:04.590 align:start position:0% as a sort of extra hard drive and this can<00:17:03.319> be<00:17:03.480> used<00:17:03.720> for<00:17:03.920> you<00:17:04.000> know<00:17:04.120> reading<00:17:04.400> the 00:17:04.590 --> 00:17:04.600 align:start position:0% can be used for you know reading the 00:17:04.600 --> 00:17:06.189 align:start position:0% can be used for you know reading the state<00:17:05.039> it<00:17:05.120> can<00:17:05.240> be<00:17:05.360> used<00:17:05.559> for<00:17:05.720> processing 00:17:06.189 --> 00:17:06.199 align:start position:0% state it can be used for processing 00:17:06.199 --> 00:17:08.829 align:start position:0% state it can be used for processing watches<00:17:06.799> potentially<00:17:07.240> probabilistic 00:17:08.829 --> 00:17:08.839 align:start position:0% watches potentially probabilistic 00:17:08.839 --> 00:17:12.270 align:start position:0% watches potentially probabilistic validation<00:17:09.880> so<00:17:10.880> as<00:17:11.039> far<00:17:11.199> as<00:17:11.360> what<00:17:11.480> we<00:17:11.640> want 00:17:12.270 --> 00:17:12.280 align:start position:0% validation so as far as what we want 00:17:12.280 --> 00:17:13.789 align:start position:0% validation so as far as what we want what<00:17:12.360> we<00:17:12.480> want<00:17:12.760> to<00:17:13.000> have<00:17:13.199> is<00:17:13.360> we<00:17:13.520> you<00:17:13.600> know<00:17:13.679> we 00:17:13.789 --> 00:17:13.799 align:start position:0% what we want to have is we you know we 00:17:13.799 --> 00:17:15.470 align:start position:0% what we want to have is we you know we want<00:17:13.880> to<00:17:14.039> store<00:17:14.679> we<00:17:14.880> want<00:17:15.000> to<00:17:15.120> store 00:17:15.470 --> 00:17:15.480 align:start position:0% want to store we want to store 00:17:15.480 --> 00:17:16.710 align:start position:0% want to store we want to store everything<00:17:15.799> that<00:17:15.959> light<00:17:16.160> nodes<00:17:16.360> are<00:17:16.520> going<00:17:16.640> to 00:17:16.710 --> 00:17:16.720 align:start position:0% everything that light nodes are going to 00:17:16.720 --> 00:17:19.669 align:start position:0% everything that light nodes are going to be<00:17:16.799> storing<00:17:17.160> by<00:17:17.439> themselves<00:17:17.919> in<00:17:18.319> this<00:17:18.559> kind<00:17:18.720> of 00:17:19.669 --> 00:17:19.679 align:start position:0% be storing by themselves in this kind of 00:17:19.679 --> 00:17:22.230 align:start position:0% be storing by themselves in this kind of specialized<00:17:20.319> DHD<00:17:21.319> we<00:17:21.520> don't<00:17:21.760> necessarily 00:17:22.230 --> 00:17:22.240 align:start position:0% specialized DHD we don't necessarily 00:17:22.240 --> 00:17:23.990 align:start position:0% specialized DHD we don't necessarily want<00:17:22.360> to<00:17:22.480> mix<00:17:22.640> it<00:17:22.799> with<00:17:22.959> swarm<00:17:23.480> just<00:17:23.679> because 00:17:23.990 --> 00:17:24.000 align:start position:0% want to mix it with swarm just because 00:17:24.000 --> 00:17:25.750 align:start position:0% want to mix it with swarm just because it's<00:17:24.199> better<00:17:24.439> to<00:17:24.640> have<00:17:25.240> first<00:17:25.400> of<00:17:25.480> all<00:17:25.640> it's 00:17:25.750 --> 00:17:25.760 align:start position:0% it's better to have first of all it's 00:17:25.760 --> 00:17:27.029 align:start position:0% it's better to have first of all it's better<00:17:25.959> to<00:17:26.079> have<00:17:26.199> the<00:17:26.319> different<00:17:26.600> protocols 00:17:27.029 --> 00:17:27.039 align:start position:0% better to have the different protocols 00:17:27.039 --> 00:17:28.350 align:start position:0% better to have the different protocols be<00:17:27.199> separate<00:17:27.640> I<00:17:27.720> think<00:17:27.880> people<00:17:28.079> should<00:17:28.240> be 00:17:28.350 --> 00:17:28.360 align:start position:0% be separate I think people should be 00:17:28.360 --> 00:17:30.430 align:start position:0% be separate I think people should be able<00:17:28.520> to<00:17:28.640> use<00:17:29.280> etherum<00:17:29.919> even<00:17:30.080> if<00:17:30.160> they<00:17:30.280> don't 00:17:30.430 --> 00:17:30.440 align:start position:0% able to use etherum even if they don't 00:17:30.440 --> 00:17:31.630 align:start position:0% able to use etherum even if they don't care<00:17:30.600> about<00:17:30.799> whisper<00:17:31.080> and<00:17:31.160> swarm<00:17:31.480> they<00:17:31.520> should 00:17:31.630 --> 00:17:31.640 align:start position:0% care about whisper and swarm they should 00:17:31.640 --> 00:17:32.830 align:start position:0% care about whisper and swarm they should be<00:17:31.720> able<00:17:31.840> to<00:17:31.919> use<00:17:32.039> swarm<00:17:32.360> if<00:17:32.440> they<00:17:32.559> don't<00:17:32.679> care 00:17:32.830 --> 00:17:32.840 align:start position:0% be able to use swarm if they don't care 00:17:32.840 --> 00:17:36.430 align:start position:0% be able to use swarm if they don't care about<00:17:33.000> whisper<00:17:33.320> and<00:17:33.440> so<00:17:33.760> forth<00:17:35.160> and<00:17:36.160> there's 00:17:36.430 --> 00:17:36.440 align:start position:0% about whisper and so forth and there's 00:17:36.440 --> 00:17:38.630 align:start position:0% about whisper and so forth and there's an<00:17:36.640> a<00:17:36.880> possibility<00:17:37.440> of<00:17:37.640> making<00:17:37.919> a<00:17:38.080> sort<00:17:38.280> of<00:17:38.400> tit 00:17:38.630 --> 00:17:38.640 align:start position:0% an a possibility of making a sort of tit 00:17:38.640 --> 00:17:41.510 align:start position:0% an a possibility of making a sort of tit forat<00:17:39.160> protocol<00:17:40.039> for<00:17:40.679> where<00:17:40.840> light<00:17:41.039> nodes<00:17:41.360> can 00:17:41.510 --> 00:17:41.520 align:start position:0% forat protocol for where light nodes can 00:17:41.520 --> 00:17:43.390 align:start position:0% forat protocol for where light nodes can sort<00:17:41.640> of<00:17:41.840> ask<00:17:42.039> each<00:17:42.160> other<00:17:42.799> give<00:17:42.960> each<00:17:43.080> other 00:17:43.390 --> 00:17:43.400 align:start position:0% sort of ask each other give each other 00:17:43.400 --> 00:17:45.430 align:start position:0% sort of ask each other give each other proofs<00:17:44.080> and<00:17:44.200> that<00:17:44.320> helps<00:17:44.559> incentivize<00:17:45.200> notes 00:17:45.430 --> 00:17:45.440 align:start position:0% proofs and that helps incentivize notes 00:17:45.440 --> 00:17:47.630 align:start position:0% proofs and that helps incentivize notes to<00:17:45.640> actually<00:17:45.880> store 00:17:47.630 --> 00:17:47.640 align:start position:0% to actually store 00:17:47.640 --> 00:17:49.789 align:start position:0% to actually store things 00:17:49.789 --> 00:17:49.799 align:start position:0% things 00:17:49.799 --> 00:17:53.230 align:start position:0% things so<00:17:51.080> long-term<00:17:52.080> like<00:17:52.360> clients<00:17:52.679> and<00:17:52.880> proof<00:17:53.080> of 00:17:53.230 --> 00:17:53.240 align:start position:0% so long-term like clients and proof of 00:17:53.240 --> 00:17:56.149 align:start position:0% so long-term like clients and proof of stake<00:17:54.000> it's<00:17:54.440> uh<00:17:54.960> actually<00:17:55.720> there<00:17:55.880> are 00:17:56.149 --> 00:17:56.159 align:start position:0% stake it's uh actually there are 00:17:56.159 --> 00:17:57.909 align:start position:0% stake it's uh actually there are potential<00:17:56.559> there<00:17:56.640> are<00:17:56.840> potential<00:17:57.320> tricks 00:17:57.909 --> 00:17:57.919 align:start position:0% potential there are potential tricks 00:17:57.919 --> 00:18:00.549 align:start position:0% potential there are potential tricks that<00:17:59.120> you<00:17:59.240> know<00:17:59.360> that<00:17:59.520> could<00:18:00.080> it's<00:18:00.240> obviously 00:18:00.549 --> 00:18:00.559 align:start position:0% that you know that could it's obviously 00:18:00.559 --> 00:18:02.590 align:start position:0% that you know that could it's obviously going<00:18:00.720> to<00:18:00.840> have<00:18:01.039> more<00:18:01.280> infoo<00:18:02.000> than<00:18:02.240> than<00:18:02.400> proof 00:18:02.590 --> 00:18:02.600 align:start position:0% going to have more infoo than than proof 00:18:02.600 --> 00:18:03.990 align:start position:0% going to have more infoo than than proof of<00:18:02.720> work<00:18:03.000> because<00:18:03.159> with<00:18:03.360> proof<00:18:03.520> of<00:18:03.600> stake<00:18:03.840> you 00:18:03.990 --> 00:18:04.000 align:start position:0% of work because with proof of stake you 00:18:04.000 --> 00:18:05.750 align:start position:0% of work because with proof of stake you actually<00:18:04.280> need<00:18:04.400> to<00:18:05.000> validate<00:18:05.400> that<00:18:05.520> people 00:18:05.750 --> 00:18:05.760 align:start position:0% actually need to validate that people 00:18:05.760 --> 00:18:07.470 align:start position:0% actually need to validate that people have<00:18:05.960> stake<00:18:06.520> there's<00:18:06.840> this<00:18:07.000> option<00:18:07.200> of<00:18:07.320> sort 00:18:07.470 --> 00:18:07.480 align:start position:0% have stake there's this option of sort 00:18:07.480 --> 00:18:08.950 align:start position:0% have stake there's this option of sort of<00:18:07.600> artificially<00:18:08.159> discretizing<00:18:08.799> the 00:18:08.950 --> 00:18:08.960 align:start position:0% of artificially discretizing the 00:18:08.960 --> 00:18:10.990 align:start position:0% of artificially discretizing the protocol<00:18:09.400> so<00:18:09.520> you<00:18:09.600> would<00:18:09.880> have<00:18:10.480> these<00:18:10.679> sort<00:18:10.840> of 00:18:10.990 --> 00:18:11.000 align:start position:0% protocol so you would have these sort of 00:18:11.000 --> 00:18:12.310 align:start position:0% protocol so you would have these sort of checkpoints<00:18:11.440> that<00:18:11.559> are<00:18:11.679> far<00:18:11.880> away<00:18:12.039> from<00:18:12.200> each 00:18:12.310 --> 00:18:12.320 align:start position:0% checkpoints that are far away from each 00:18:12.320 --> 00:18:14.470 align:start position:0% checkpoints that are far away from each other<00:18:12.520> and<00:18:12.720> each<00:18:12.960> checkpoint<00:18:13.960> and<00:18:14.080> the<00:18:14.400> is 00:18:14.470 --> 00:18:14.480 align:start position:0% other and each checkpoint and the is 00:18:14.480 --> 00:18:15.789 align:start position:0% other and each checkpoint and the is that<00:18:14.600> each<00:18:14.799> checkpoint<00:18:15.159> would<00:18:15.280> be<00:18:15.360> signed<00:18:15.679> by 00:18:15.789 --> 00:18:15.799 align:start position:0% that each checkpoint would be signed by 00:18:15.799 --> 00:18:17.149 align:start position:0% that each checkpoint would be signed by a<00:18:15.919> very<00:18:16.120> large<00:18:16.360> number<00:18:16.559> of<00:18:16.640> nodes<00:18:16.960> and<00:18:17.039> then 00:18:17.149 --> 00:18:17.159 align:start position:0% a very large number of nodes and then 00:18:17.159 --> 00:18:18.830 align:start position:0% a very large number of nodes and then you<00:18:17.240> would<00:18:17.360> see<00:18:17.640> that<00:18:18.039> hey<00:18:18.200> this<00:18:18.400> very<00:18:18.600> very 00:18:18.830 --> 00:18:18.840 align:start position:0% you would see that hey this very very 00:18:18.840 --> 00:18:20.430 align:start position:0% you would see that hey this very very large<00:18:19.039> set<00:18:19.159> of<00:18:19.280> signers<00:18:19.679> has<00:18:19.840> validated<00:18:20.280> this 00:18:20.430 --> 00:18:20.440 align:start position:0% large set of signers has validated this 00:18:20.440 --> 00:18:22.110 align:start position:0% large set of signers has validated this next<00:18:20.679> checkpoint<00:18:21.400> and<00:18:21.480> then<00:18:21.559> you<00:18:21.679> sort<00:18:21.840> of<00:18:22.000> go 00:18:22.110 --> 00:18:22.120 align:start position:0% next checkpoint and then you sort of go 00:18:22.120 --> 00:18:25.710 align:start position:0% next checkpoint and then you sort of go from<00:18:22.400> there<00:18:23.559> um<00:18:24.559> proof<00:18:24.880> provision<00:18:25.440> not 00:18:25.710 --> 00:18:25.720 align:start position:0% from there um proof provision not 00:18:25.720 --> 00:18:27.909 align:start position:0% from there um proof provision not incentivized<00:18:26.600> I<00:18:26.679> mean<00:18:27.280> said<00:18:27.480> for<00:18:27.640> Tad 00:18:27.909 --> 00:18:27.919 align:start position:0% incentivized I mean said for Tad 00:18:27.919 --> 00:18:29.549 align:start position:0% incentivized I mean said for Tad protocol<00:18:28.240> sort<00:18:28.440> of<00:18:28.559> does<00:18:28.919> sort<00:18:29.120> of<00:18:29.240> does<00:18:29.400> it 00:18:29.549 --> 00:18:29.559 align:start position:0% protocol sort of does sort of does it 00:18:29.559 --> 00:18:31.470 align:start position:0% protocol sort of does sort of does it putting<00:18:29.760> it<00:18:29.880> on<00:18:29.960> a<00:18:30.120> DHD<00:18:30.640> sort<00:18:30.840> of<00:18:30.960> solves<00:18:31.280> the 00:18:31.470 --> 00:18:31.480 align:start position:0% putting it on a DHD sort of solves the 00:18:31.480 --> 00:18:33.350 align:start position:0% putting it on a DHD sort of solves the problem<00:18:32.280> is<00:18:32.400> you<00:18:32.520> know<00:18:32.640> is<00:18:32.720> there<00:18:32.919> some<00:18:33.120> better 00:18:33.350 --> 00:18:33.360 align:start position:0% problem is you know is there some better 00:18:33.360 --> 00:18:34.909 align:start position:0% problem is you know is there some better solution<00:18:33.880> will<00:18:34.039> will<00:18:34.159> we<00:18:34.320> need<00:18:34.440> to<00:18:34.640> have<00:18:34.760> some 00:18:34.909 --> 00:18:34.919 align:start position:0% solution will will we need to have some 00:18:34.919 --> 00:18:37.669 align:start position:0% solution will will we need to have some better<00:18:35.200> solution<00:18:36.080> hard<00:18:36.280> to<00:18:36.440> say<00:18:37.159> like<00:18:37.400> clients 00:18:37.669 --> 00:18:37.679 align:start position:0% better solution hard to say like clients 00:18:37.679 --> 00:18:39.590 align:start position:0% better solution hard to say like clients at<00:18:37.799> ethereum<00:18:38.159> 2.0<00:18:38.720> depends<00:18:39.039> entirely<00:18:39.360> on<00:18:39.480> what 00:18:39.590 --> 00:18:39.600 align:start position:0% at ethereum 2.0 depends entirely on what 00:18:39.600 --> 00:18:43.110 align:start position:0% at ethereum 2.0 depends entirely on what ethereum<00:18:39.919> 2.0<00:18:40.280> is<00:18:40.360> going<00:18:40.480> to<00:18:40.640> look<00:18:40.880> like<00:18:42.120> um 00:18:43.110 --> 00:18:43.120 align:start position:0% ethereum 2.0 is going to look like um 00:18:43.120 --> 00:18:44.750 align:start position:0% ethereum 2.0 is going to look like um anything<00:18:43.360> else<00:18:43.520> you<00:18:43.640> want<00:18:43.720> to<00:18:43.919> add<00:18:44.360> no<00:18:44.559> that's 00:18:44.750 --> 00:18:44.760 align:start position:0% anything else you want to add no that's 00:18:44.760 --> 00:18:57.710 align:start position:0% anything else you want to add no that's about<00:18:44.919> it<00:18:45.240> all<00:18:45.400> right<00:18:45.760> that's<00:18:46.000> about 00:18:57.710 --> 00:18:57.720 align:start position:0% 00:18:57.720 --> 00:19:01.760 align:start position:0% it<00:18:58.760> for