WEBVTT Kind: captions Language: en 00:00:00.000 --> 00:00:04.350 align:start position:0% foreign 00:00:04.350 --> 00:00:04.360 align:start position:0% 00:00:04.360 --> 00:00:16.369 align:start position:0% [Music] 00:00:16.369 --> 00:00:16.379 align:start position:0% 00:00:16.379 --> 00:00:19.250 align:start position:0% yeah<00:00:16.859> welcome<00:00:17.160> to<00:00:17.520> this<00:00:17.880> uh<00:00:18.240> ethereum<00:00:18.840> JS 00:00:19.250 --> 00:00:19.260 align:start position:0% yeah welcome to this uh ethereum JS 00:00:19.260 --> 00:00:20.510 align:start position:0% yeah welcome to this uh ethereum JS Workshop 00:00:20.510 --> 00:00:20.520 align:start position:0% Workshop 00:00:20.520 --> 00:00:25.009 align:start position:0% Workshop uh<00:00:21.240> I'm<00:00:21.420> Gabriel<00:00:21.960> from<00:00:22.740> the<00:00:23.039> ethereum<00:00:23.699> JS<00:00:24.119> team 00:00:25.009 --> 00:00:25.019 align:start position:0% uh I'm Gabriel from the ethereum JS team 00:00:25.019 --> 00:00:27.349 align:start position:0% uh I'm Gabriel from the ethereum JS team my<00:00:25.380> name<00:00:25.500> is<00:00:25.619> Scotty<00:00:26.039> also<00:00:26.580> from<00:00:26.760> the<00:00:26.880> ethereum 00:00:27.349 --> 00:00:27.359 align:start position:0% my name is Scotty also from the ethereum 00:00:27.359 --> 00:00:30.589 align:start position:0% my name is Scotty also from the ethereum JS<00:00:27.779> team<00:00:28.080> yeah<00:00:28.980> so<00:00:29.699> today<00:00:29.939> we're<00:00:30.240> just<00:00:30.420> going 00:00:30.589 --> 00:00:30.599 align:start position:0% JS team yeah so today we're just going 00:00:30.599 --> 00:00:33.470 align:start position:0% JS team yeah so today we're just going to<00:00:30.779> be<00:00:30.840> walking<00:00:31.380> you<00:00:31.740> through<00:00:32.279> our<00:00:32.759> model<00:00:32.940> repo 00:00:33.470 --> 00:00:33.480 align:start position:0% to be walking you through our model repo 00:00:33.480 --> 00:00:35.569 align:start position:0% to be walking you through our model repo called<00:00:33.899> you<00:00:34.200> know<00:00:34.260> the<00:00:34.500> ethereum<00:00:34.980> JS<00:00:35.399> motor 00:00:35.569 --> 00:00:35.579 align:start position:0% called you know the ethereum JS motor 00:00:35.579 --> 00:00:38.150 align:start position:0% called you know the ethereum JS motor repo<00:00:36.480> so<00:00:37.020> we're<00:00:37.200> basically<00:00:37.500> the<00:00:37.739> JavaScript 00:00:38.150 --> 00:00:38.160 align:start position:0% repo so we're basically the JavaScript 00:00:38.160 --> 00:00:40.369 align:start position:0% repo so we're basically the JavaScript team<00:00:38.399> of<00:00:38.700> the<00:00:38.760> ethereum<00:00:39.180> foundation<00:00:39.600> and<00:00:40.260> what 00:00:40.369 --> 00:00:40.379 align:start position:0% team of the ethereum foundation and what 00:00:40.379 --> 00:00:42.350 align:start position:0% team of the ethereum foundation and what we<00:00:40.620> do<00:00:40.800> with<00:00:41.399> the 00:00:42.350 --> 00:00:42.360 align:start position:0% we do with the 00:00:42.360 --> 00:00:45.229 align:start position:0% we do with the ethereum<00:00:43.200> JS<00:00:43.680> and<00:00:43.860> mono<00:00:44.160> repo<00:00:44.520> let<00:00:45.120> me 00:00:45.229 --> 00:00:45.239 align:start position:0% ethereum JS and mono repo let me 00:00:45.239 --> 00:00:46.670 align:start position:0% ethereum JS and mono repo let me actually<00:00:45.360> bring<00:00:45.660> up<00:00:45.840> the<00:00:46.020> slides<00:00:46.320> it's<00:00:46.559> going 00:00:46.670 --> 00:00:46.680 align:start position:0% actually bring up the slides it's going 00:00:46.680 --> 00:00:50.209 align:start position:0% actually bring up the slides it's going to<00:00:46.800> be<00:00:46.920> helpful 00:00:50.209 --> 00:00:50.219 align:start position:0% 00:00:50.219 --> 00:00:52.310 align:start position:0% so<00:00:50.520> yeah<00:00:50.640> what<00:00:50.820> we<00:00:50.940> do<00:00:51.120> with<00:00:51.300> ethereum<00:00:51.780> JS<00:00:52.140> is 00:00:52.310 --> 00:00:52.320 align:start position:0% so yeah what we do with ethereum JS is 00:00:52.320 --> 00:00:55.010 align:start position:0% so yeah what we do with ethereum JS is we<00:00:52.559> basically<00:00:52.860> build<00:00:53.219> a<00:00:53.760> set<00:00:54.059> of<00:00:54.180> tools<00:00:54.539> that 00:00:55.010 --> 00:00:55.020 align:start position:0% we basically build a set of tools that 00:00:55.020 --> 00:00:58.189 align:start position:0% we basically build a set of tools that people<00:00:55.260> can<00:00:55.620> build<00:00:55.860> upon<00:00:56.280> so<00:00:57.180> we're<00:00:57.480> used<00:00:57.780> by 00:00:58.189 --> 00:00:58.199 align:start position:0% people can build upon so we're used by 00:00:58.199 --> 00:01:01.729 align:start position:0% people can build upon so we're used by lots<00:00:59.160> of<00:00:59.280> uh<00:01:00.420> you<00:01:00.780> know<00:01:00.840> JavaScript<00:01:01.320> tooling 00:01:01.729 --> 00:01:01.739 align:start position:0% lots of uh you know JavaScript tooling 00:01:01.739 --> 00:01:03.229 align:start position:0% lots of uh you know JavaScript tooling that's<00:01:01.920> here<00:01:02.100> I'm<00:01:02.340> sure<00:01:02.520> you're<00:01:02.760> familiar 00:01:03.229 --> 00:01:03.239 align:start position:0% that's here I'm sure you're familiar 00:01:03.239 --> 00:01:04.070 align:start position:0% that's here I'm sure you're familiar with 00:01:04.070 --> 00:01:04.080 align:start position:0% with 00:01:04.080 --> 00:01:05.630 align:start position:0% with and<00:01:05.100> um 00:01:05.630 --> 00:01:05.640 align:start position:0% and um 00:01:05.640 --> 00:01:08.690 align:start position:0% and um yeah<00:01:06.299> and<00:01:06.840> it's<00:01:07.320> really<00:01:07.560> a<00:01:07.860> great<00:01:07.979> set<00:01:08.520> of 00:01:08.690 --> 00:01:08.700 align:start position:0% yeah and it's really a great set of 00:01:08.700 --> 00:01:11.390 align:start position:0% yeah and it's really a great set of tools<00:01:09.060> for<00:01:09.420> people<00:01:09.659> to<00:01:10.020> learn<00:01:10.260> uh<00:01:11.159> about 00:01:11.390 --> 00:01:11.400 align:start position:0% tools for people to learn uh about 00:01:11.400 --> 00:01:13.310 align:start position:0% tools for people to learn uh about blockchain<00:01:11.939> in<00:01:12.180> general<00:01:12.299> because<00:01:12.720> JavaScript 00:01:13.310 --> 00:01:13.320 align:start position:0% blockchain in general because JavaScript 00:01:13.320 --> 00:01:14.990 align:start position:0% blockchain in general because JavaScript is<00:01:13.560> a<00:01:13.860> you<00:01:13.979> know<00:01:14.100> really<00:01:14.340> easy<00:01:14.580> to<00:01:14.820> use 00:01:14.990 --> 00:01:15.000 align:start position:0% is a you know really easy to use 00:01:15.000 --> 00:01:17.149 align:start position:0% is a you know really easy to use language<00:01:15.240> that<00:01:15.600> a<00:01:15.840> lot<00:01:15.900> of<00:01:16.020> people<00:01:16.200> a<00:01:16.920> lot<00:01:17.040> of 00:01:17.149 --> 00:01:17.159 align:start position:0% language that a lot of people a lot of 00:01:17.159 --> 00:01:19.310 align:start position:0% language that a lot of people a lot of web<00:01:17.340> developers<00:01:17.820> are<00:01:18.000> familiar<00:01:18.420> with 00:01:19.310 --> 00:01:19.320 align:start position:0% web developers are familiar with 00:01:19.320 --> 00:01:22.429 align:start position:0% web developers are familiar with and<00:01:20.280> um<00:01:20.280> yeah<00:01:20.520> we're<00:01:20.759> focused<00:01:21.240> on<00:01:21.540> you<00:01:22.380> know 00:01:22.429 --> 00:01:22.439 align:start position:0% and um yeah we're focused on you know 00:01:22.439 --> 00:01:25.010 align:start position:0% and um yeah we're focused on you know helping<00:01:22.860> out<00:01:22.979> a<00:01:23.159> lot<00:01:23.280> with<00:01:23.640> research<00:01:24.180> as<00:01:24.360> well 00:01:25.010 --> 00:01:25.020 align:start position:0% helping out a lot with research as well 00:01:25.020 --> 00:01:27.109 align:start position:0% helping out a lot with research as well I<00:01:25.380> mean<00:01:25.500> we<00:01:25.740> have<00:01:25.920> a<00:01:26.100> for<00:01:26.340> example<00:01:26.580> a<00:01:26.820> client 00:01:27.109 --> 00:01:27.119 align:start position:0% I mean we have a for example a client 00:01:27.119 --> 00:01:28.789 align:start position:0% I mean we have a for example a client going<00:01:27.299> but<00:01:27.659> it's<00:01:27.780> not<00:01:27.960> a<00:01:28.200> production<00:01:28.500> ready 00:01:28.789 --> 00:01:28.799 align:start position:0% going but it's not a production ready 00:01:28.799 --> 00:01:32.450 align:start position:0% going but it's not a production ready client<00:01:29.220> like<00:01:29.460> like<00:01:29.700> get<00:01:30.000> and<00:01:30.420> and<00:01:30.780> others<00:01:31.619> and 00:01:32.450 --> 00:01:32.460 align:start position:0% client like like get and and others and 00:01:32.460 --> 00:01:34.730 align:start position:0% client like like get and and others and that's<00:01:32.880> kind<00:01:33.420> of<00:01:33.540> an<00:01:33.780> advantage<00:01:34.380> for<00:01:34.619> us 00:01:34.730 --> 00:01:34.740 align:start position:0% that's kind of an advantage for us 00:01:34.740 --> 00:01:36.950 align:start position:0% that's kind of an advantage for us because<00:01:35.040> we<00:01:35.340> can<00:01:35.460> jump<00:01:35.700> in<00:01:35.939> early<00:01:36.119> for<00:01:36.659> you 00:01:36.950 --> 00:01:36.960 align:start position:0% because we can jump in early for you 00:01:36.960 --> 00:01:40.130 align:start position:0% because we can jump in early for you know<00:01:37.200> in<00:01:37.680> your<00:01:37.979> eips<00:01:38.460> and<00:01:39.420> Implement<00:01:39.780> stuff 00:01:40.130 --> 00:01:40.140 align:start position:0% know in your eips and Implement stuff 00:01:40.140 --> 00:01:41.810 align:start position:0% know in your eips and Implement stuff because<00:01:40.380> we're<00:01:40.560> not<00:01:40.740> constrained<00:01:41.340> by<00:01:41.579> the 00:01:41.810 --> 00:01:41.820 align:start position:0% because we're not constrained by the 00:01:41.820 --> 00:01:43.550 align:start position:0% because we're not constrained by the maintenance<00:01:42.479> of<00:01:42.659> like<00:01:42.780> a<00:01:43.020> production<00:01:43.259> ready 00:01:43.550 --> 00:01:43.560 align:start position:0% maintenance of like a production ready 00:01:43.560 --> 00:01:45.109 align:start position:0% maintenance of like a production ready client<00:01:43.920> for<00:01:44.220> example 00:01:45.109 --> 00:01:45.119 align:start position:0% client for example 00:01:45.119 --> 00:01:47.450 align:start position:0% client for example so<00:01:45.659> yeah<00:01:45.840> we've<00:01:46.079> been<00:01:46.259> helping<00:01:46.680> out<00:01:46.799> with<00:01:47.040> lots 00:01:47.450 --> 00:01:47.460 align:start position:0% so yeah we've been helping out with lots 00:01:47.460 --> 00:01:50.749 align:start position:0% so yeah we've been helping out with lots of<00:01:47.520> you<00:01:48.000> know<00:01:48.060> newer<00:01:48.540> eips 00:01:50.749 --> 00:01:50.759 align:start position:0% of you know newer eips 00:01:50.759 --> 00:01:53.870 align:start position:0% of you know newer eips so<00:01:51.360> yeah<00:01:51.659> that's<00:01:52.020> just<00:01:52.380> you<00:01:52.979> know<00:01:53.100> an<00:01:53.520> example 00:01:53.870 --> 00:01:53.880 align:start position:0% so yeah that's just you know an example 00:01:53.880 --> 00:01:56.990 align:start position:0% so yeah that's just you know an example of<00:01:54.119> that<00:01:54.299> so<00:01:55.079> yeah<00:01:55.439> three<00:01:56.100> of<00:01:56.340> the<00:01:56.399> latest<00:01:56.579> like 00:01:56.990 --> 00:01:57.000 align:start position:0% of that so yeah three of the latest like 00:01:57.000 --> 00:01:58.850 align:start position:0% of that so yeah three of the latest like PRS<00:01:57.780> that<00:01:57.899> are<00:01:58.020> in<00:01:58.140> progress<00:01:58.439> in<00:01:58.619> the<00:01:58.740> modern 00:01:58.850 --> 00:01:58.860 align:start position:0% PRS that are in progress in the modern 00:01:58.860 --> 00:02:01.730 align:start position:0% PRS that are in progress in the modern repo<00:01:59.340> or<00:02:00.180> you<00:02:00.600> know<00:02:00.720> a<00:02:00.899> stateless<00:02:01.200> vehicle 00:02:01.730 --> 00:02:01.740 align:start position:0% repo or you know a stateless vehicle 00:02:01.740 --> 00:02:03.770 align:start position:0% repo or you know a stateless vehicle State<00:02:02.040> manager<00:02:02.520> to<00:02:02.880> help<00:02:03.000> out<00:02:03.180> with<00:02:03.420> vertical 00:02:03.770 --> 00:02:03.780 align:start position:0% State manager to help out with vertical 00:02:03.780 --> 00:02:05.749 align:start position:0% State manager to help out with vertical trees<00:02:04.140> that<00:02:04.560> game<00:02:04.860> and<00:02:05.159> a<00:02:05.340> bunch<00:02:05.520> of<00:02:05.579> other 00:02:05.749 --> 00:02:05.759 align:start position:0% trees that game and a bunch of other 00:02:05.759 --> 00:02:07.389 align:start position:0% trees that game and a bunch of other people<00:02:06.000> are<00:02:06.240> working<00:02:06.479> with 00:02:07.389 --> 00:02:07.399 align:start position:0% people are working with 00:02:07.399 --> 00:02:11.809 align:start position:0% people are working with Erp<00:02:08.660> 4844<00:02:09.660> which<00:02:10.500> I'm<00:02:10.860> sure<00:02:11.160> you've<00:02:11.640> heard 00:02:11.809 --> 00:02:11.819 align:start position:0% Erp 4844 which I'm sure you've heard 00:02:11.819 --> 00:02:14.510 align:start position:0% Erp 4844 which I'm sure you've heard about<00:02:11.940> like<00:02:12.180> Proto<00:02:12.660> then<00:02:12.840> charting<00:02:13.260> EIP 00:02:14.510 --> 00:02:14.520 align:start position:0% about like Proto then charting EIP 00:02:14.520 --> 00:02:16.729 align:start position:0% about like Proto then charting EIP and<00:02:15.120> uh<00:02:15.360> yeah<00:02:15.480> Beacon<00:02:15.900> chain<00:02:16.080> withdrawals 00:02:16.729 --> 00:02:16.739 align:start position:0% and uh yeah Beacon chain withdrawals 00:02:16.739 --> 00:02:18.770 align:start position:0% and uh yeah Beacon chain withdrawals which<00:02:16.980> are<00:02:17.099> going<00:02:17.280> to<00:02:17.400> be<00:02:17.520> uh<00:02:17.879> part<00:02:18.120> of<00:02:18.360> the 00:02:18.770 --> 00:02:18.780 align:start position:0% which are going to be uh part of the 00:02:18.780 --> 00:02:21.130 align:start position:0% which are going to be uh part of the Shanghai<00:02:19.200> uh<00:02:19.739> hard<00:02:19.980> folk<00:02:20.340> hard<00:02:20.640> Fork 00:02:21.130 --> 00:02:21.140 align:start position:0% Shanghai uh hard folk hard Fork 00:02:21.140 --> 00:02:23.510 align:start position:0% Shanghai uh hard folk hard Fork hopefully<00:02:22.140> I<00:02:22.379> think<00:02:22.500> Community<00:02:22.860> would<00:02:23.340> be 00:02:23.510 --> 00:02:23.520 align:start position:0% hopefully I think Community would be 00:02:23.520 --> 00:02:26.089 align:start position:0% hopefully I think Community would be pretty<00:02:23.760> mad<00:02:24.239> if<00:02:24.480> that<00:02:24.780> doesn't<00:02:24.900> get<00:02:25.140> in 00:02:26.089 --> 00:02:26.099 align:start position:0% pretty mad if that doesn't get in 00:02:26.099 --> 00:02:28.610 align:start position:0% pretty mad if that doesn't get in so 00:02:28.610 --> 00:02:28.620 align:start position:0% so 00:02:28.620 --> 00:02:30.550 align:start position:0% so yeah<00:02:29.280> you<00:02:29.640> want<00:02:29.879> to 00:02:30.550 --> 00:02:30.560 align:start position:0% yeah you want to 00:02:30.560 --> 00:02:33.770 align:start position:0% yeah you want to sure<00:02:31.560> I'd<00:02:32.040> also<00:02:32.520> like<00:02:32.640> to<00:02:32.819> just<00:02:33.000> say<00:02:33.180> hello<00:02:33.360> and 00:02:33.770 --> 00:02:33.780 align:start position:0% sure I'd also like to just say hello and 00:02:33.780 --> 00:02:35.510 align:start position:0% sure I'd also like to just say hello and if<00:02:34.140> you<00:02:34.319> get<00:02:34.379> a<00:02:34.500> sense<00:02:34.680> of<00:02:34.800> who's<00:02:34.980> with<00:02:35.340> us 00:02:35.510 --> 00:02:35.520 align:start position:0% if you get a sense of who's with us 00:02:35.520 --> 00:02:36.470 align:start position:0% if you get a sense of who's with us today 00:02:36.470 --> 00:02:36.480 align:start position:0% today 00:02:36.480 --> 00:02:39.890 align:start position:0% today um<00:02:37.020> people<00:02:37.440> used<00:02:37.920> our<00:02:38.340> mono<00:02:38.760> repo<00:02:39.120> yet<00:02:39.300> or<00:02:39.660> you 00:02:39.890 --> 00:02:39.900 align:start position:0% um people used our mono repo yet or you 00:02:39.900 --> 00:02:42.050 align:start position:0% um people used our mono repo yet or you adapt<00:02:40.739> developers 00:02:42.050 --> 00:02:42.060 align:start position:0% adapt developers 00:02:42.060 --> 00:02:42.770 align:start position:0% adapt developers um 00:02:42.770 --> 00:02:42.780 align:start position:0% um 00:02:42.780 --> 00:02:44.750 align:start position:0% um just<00:02:43.080> get<00:02:43.319> like<00:02:43.500> a<00:02:43.620> sample<00:02:43.980> from<00:02:44.220> the<00:02:44.340> crowd<00:02:44.640> of 00:02:44.750 --> 00:02:44.760 align:start position:0% just get like a sample from the crowd of 00:02:44.760 --> 00:02:45.890 align:start position:0% just get like a sample from the crowd of like<00:02:45.000> who 00:02:45.890 --> 00:02:45.900 align:start position:0% like who 00:02:45.900 --> 00:02:47.570 align:start position:0% like who what<00:02:46.260> what<00:02:46.319> brings<00:02:46.860> you<00:02:47.040> guys<00:02:47.160> to<00:02:47.400> this 00:02:47.570 --> 00:02:47.580 align:start position:0% what what brings you guys to this 00:02:47.580 --> 00:02:49.630 align:start position:0% what what brings you guys to this Workshop 00:02:49.630 --> 00:02:49.640 align:start position:0% Workshop 00:02:49.640 --> 00:02:51.770 align:start position:0% Workshop raise<00:02:50.640> your<00:02:50.879> hand<00:02:51.060> if<00:02:51.300> you've<00:02:51.540> already 00:02:51.770 --> 00:02:51.780 align:start position:0% raise your hand if you've already 00:02:51.780 --> 00:02:54.050 align:start position:0% raise your hand if you've already interacted<00:02:52.620> with<00:02:52.980> the<00:02:53.099> ethereum<00:02:53.519> JS<00:02:53.879> motor 00:02:54.050 --> 00:02:54.060 align:start position:0% interacted with the ethereum JS motor 00:02:54.060 --> 00:02:56.570 align:start position:0% interacted with the ethereum JS motor repo 00:02:56.570 --> 00:02:56.580 align:start position:0% repo 00:02:56.580 --> 00:02:59.150 align:start position:0% repo okay<00:02:57.180> so<00:02:57.720> this<00:02:57.959> is<00:02:58.140> relatively<00:02:58.560> new<00:02:58.739> to<00:02:58.980> most 00:02:59.150 --> 00:02:59.160 align:start position:0% okay so this is relatively new to most 00:02:59.160 --> 00:03:00.770 align:start position:0% okay so this is relatively new to most of<00:02:59.340> you<00:02:59.459> awesome<00:02:59.879> awesome 00:03:00.770 --> 00:03:00.780 align:start position:0% of you awesome awesome 00:03:00.780 --> 00:03:04.070 align:start position:0% of you awesome awesome um<00:03:00.840> and<00:03:01.379> that's<00:03:01.500> good<00:03:01.739> it's<00:03:02.519> um<00:03:02.599> part<00:03:03.599> of<00:03:03.780> our 00:03:04.070 --> 00:03:04.080 align:start position:0% um and that's good it's um part of our 00:03:04.080 --> 00:03:08.150 align:start position:0% um and that's good it's um part of our focus<00:03:04.500> is<00:03:04.980> having<00:03:05.780> these<00:03:06.780> tools<00:03:07.140> available<00:03:07.440> in 00:03:08.150 --> 00:03:08.160 align:start position:0% focus is having these tools available in 00:03:08.160 --> 00:03:10.490 align:start position:0% focus is having these tools available in a<00:03:08.340> language<00:03:08.640> that<00:03:09.180> devs<00:03:09.660> know<00:03:09.840> and<00:03:10.260> are 00:03:10.490 --> 00:03:10.500 align:start position:0% a language that devs know and are 00:03:10.500 --> 00:03:13.070 align:start position:0% a language that devs know and are building<00:03:10.680> in<00:03:11.040> and 00:03:13.070 --> 00:03:13.080 align:start position:0% building in and 00:03:13.080 --> 00:03:14.930 align:start position:0% building in and you<00:03:13.620> know<00:03:13.680> as<00:03:13.980> you're<00:03:14.220> as<00:03:14.459> you're<00:03:14.640> learning 00:03:14.930 --> 00:03:14.940 align:start position:0% you know as you're as you're learning 00:03:14.940 --> 00:03:16.550 align:start position:0% you know as you're as you're learning more<00:03:15.120> about<00:03:15.239> ethereum<00:03:15.780> and<00:03:15.959> about<00:03:16.140> how<00:03:16.440> all 00:03:16.550 --> 00:03:16.560 align:start position:0% more about ethereum and about how all 00:03:16.560 --> 00:03:18.830 align:start position:0% more about ethereum and about how all this<00:03:16.739> works<00:03:17.099> uh<00:03:17.700> hopefully<00:03:18.060> our<00:03:18.239> library<00:03:18.480> can 00:03:18.830 --> 00:03:18.840 align:start position:0% this works uh hopefully our library can 00:03:18.840 --> 00:03:27.589 align:start position:0% this works uh hopefully our library can help<00:03:19.019> you<00:03:19.200> get<00:03:19.379> there 00:03:27.589 --> 00:03:27.599 align:start position:0% 00:03:27.599 --> 00:03:29.449 align:start position:0% so<00:03:28.019> yeah<00:03:28.200> I've<00:03:28.440> been<00:03:28.620> with<00:03:28.800> the<00:03:28.920> team<00:03:29.099> since 00:03:29.449 --> 00:03:29.459 align:start position:0% so yeah I've been with the team since 00:03:29.459 --> 00:03:31.190 align:start position:0% so yeah I've been with the team since the<00:03:29.700> beginning<00:03:29.879> of<00:03:30.060> the<00:03:30.180> year<00:03:30.300> Gabriel's<00:03:31.019> been 00:03:31.190 --> 00:03:31.200 align:start position:0% the beginning of the year Gabriel's been 00:03:31.200 --> 00:03:32.990 align:start position:0% the beginning of the year Gabriel's been here<00:03:31.500> a<00:03:31.739> little<00:03:31.860> bit<00:03:31.980> longer 00:03:32.990 --> 00:03:33.000 align:start position:0% here a little bit longer 00:03:33.000 --> 00:03:33.710 align:start position:0% here a little bit longer um 00:03:33.710 --> 00:03:33.720 align:start position:0% um 00:03:33.720 --> 00:03:36.410 align:start position:0% um and 00:03:36.410 --> 00:03:36.420 align:start position:0% and 00:03:36.420 --> 00:03:37.509 align:start position:0% and yeah<00:03:36.720> yeah 00:03:37.509 --> 00:03:37.519 align:start position:0% yeah yeah 00:03:37.519 --> 00:03:40.729 align:start position:0% yeah yeah so<00:03:38.519> we<00:03:38.819> so<00:03:39.659> I'm<00:03:39.900> gonna<00:03:40.019> go<00:03:40.200> through<00:03:40.260> that<00:03:40.440> slide 00:03:40.729 --> 00:03:40.739 align:start position:0% so we so I'm gonna go through that slide 00:03:40.739 --> 00:03:42.350 align:start position:0% so we so I'm gonna go through that slide quickly<00:03:40.980> just<00:03:41.220> to<00:03:41.400> give<00:03:41.519> you<00:03:41.640> a<00:03:41.760> sense<00:03:41.940> of<00:03:42.120> the 00:03:42.350 --> 00:03:42.360 align:start position:0% quickly just to give you a sense of the 00:03:42.360 --> 00:03:45.830 align:start position:0% quickly just to give you a sense of the kinds<00:03:42.840> of<00:03:42.900> like<00:03:43.319> packages<00:03:43.739> that<00:03:44.040> we<00:03:44.159> have<00:03:44.840> so 00:03:45.830 --> 00:03:45.840 align:start position:0% kinds of like packages that we have so 00:03:45.840 --> 00:03:48.110 align:start position:0% kinds of like packages that we have so we<00:03:46.560> have<00:03:46.680> an<00:03:46.799> implementation<00:03:47.340> in<00:03:47.700> typescript 00:03:48.110 --> 00:03:48.120 align:start position:0% we have an implementation in typescript 00:03:48.120 --> 00:03:50.089 align:start position:0% we have an implementation in typescript I<00:03:48.420> mean<00:03:48.540> we're<00:03:48.900> calling<00:03:49.200> from<00:03:49.440> JavaScript<00:03:49.860> but 00:03:50.089 --> 00:03:50.099 align:start position:0% I mean we're calling from JavaScript but 00:03:50.099 --> 00:03:51.170 align:start position:0% I mean we're calling from JavaScript but technically<00:03:50.459> right<00:03:50.760> at<00:03:50.940> the<00:03:51.120> moment 00:03:51.170 --> 00:03:51.180 align:start position:0% technically right at the moment 00:03:51.180 --> 00:03:52.910 align:start position:0% technically right at the moment everything<00:03:51.420> is<00:03:51.720> typescript<00:03:52.140> we've<00:03:52.620> migrated 00:03:52.910 --> 00:03:52.920 align:start position:0% everything is typescript we've migrated 00:03:52.920 --> 00:03:55.850 align:start position:0% everything is typescript we've migrated to<00:03:53.099> typescript<00:03:53.580> about<00:03:53.819> two<00:03:54.060> years<00:03:54.239> ago<00:03:54.680> uh<00:03:55.680> so 00:03:55.850 --> 00:03:55.860 align:start position:0% to typescript about two years ago uh so 00:03:55.860 --> 00:03:57.350 align:start position:0% to typescript about two years ago uh so we<00:03:55.980> have<00:03:56.099> a<00:03:56.220> typescript<00:03:56.580> implementation<00:03:57.120> of 00:03:57.350 --> 00:03:57.360 align:start position:0% we have a typescript implementation of 00:03:57.360 --> 00:03:59.089 align:start position:0% we have a typescript implementation of the<00:03:57.480> ethereum<00:03:57.900> virtual<00:03:58.200> machine 00:03:59.089 --> 00:03:59.099 align:start position:0% the ethereum virtual machine 00:03:59.099 --> 00:04:01.610 align:start position:0% the ethereum virtual machine uh<00:04:00.060> we<00:04:00.360> also<00:04:00.599> provide<00:04:00.959> you<00:04:01.260> know<00:04:01.379> building 00:04:01.610 --> 00:04:01.620 align:start position:0% uh we also provide you know building 00:04:01.620 --> 00:04:04.670 align:start position:0% uh we also provide you know building blocks<00:04:02.099> like<00:04:02.819> transaction<00:04:03.360> block<00:04:04.019> block 00:04:04.670 --> 00:04:04.680 align:start position:0% blocks like transaction block block 00:04:04.680 --> 00:04:07.130 align:start position:0% blocks like transaction block block blockchain<00:04:04.980> we<00:04:05.760> also<00:04:06.000> had<00:04:06.180> to<00:04:06.420> have<00:04:06.840> a<00:04:06.959> bunch 00:04:07.130 --> 00:04:07.140 align:start position:0% blockchain we also had to have a bunch 00:04:07.140 --> 00:04:09.289 align:start position:0% blockchain we also had to have a bunch of<00:04:07.260> like<00:04:07.500> smaller<00:04:08.040> scope-like<00:04:08.580> utils<00:04:09.120> like 00:04:09.289 --> 00:04:09.299 align:start position:0% of like smaller scope-like utils like 00:04:09.299 --> 00:04:12.890 align:start position:0% of like smaller scope-like utils like for<00:04:09.480> example<00:04:09.720> if<00:04:10.019> you<00:04:10.200> want<00:04:10.379> a<00:04:10.680> rlp<00:04:11.659> uh<00:04:12.659> like 00:04:12.890 --> 00:04:12.900 align:start position:0% for example if you want a rlp uh like 00:04:12.900 --> 00:04:14.929 align:start position:0% for example if you want a rlp uh like recursive<00:04:13.319> line<00:04:13.560> prefixing<00:04:14.159> like<00:04:14.400> encode 00:04:14.929 --> 00:04:14.939 align:start position:0% recursive line prefixing like encode 00:04:14.939 --> 00:04:17.569 align:start position:0% recursive line prefixing like encode things<00:04:15.180> decode<00:04:15.959> things<00:04:16.260> uh<00:04:17.160> we<00:04:17.340> have<00:04:17.459> a 00:04:17.569 --> 00:04:17.579 align:start position:0% things decode things uh we have a 00:04:17.579 --> 00:04:19.550 align:start position:0% things decode things uh we have a typescript<00:04:17.940> implementation<00:04:18.600> of<00:04:18.900> uh<00:04:19.139> Merkel 00:04:19.550 --> 00:04:19.560 align:start position:0% typescript implementation of uh Merkel 00:04:19.560 --> 00:04:21.890 align:start position:0% typescript implementation of uh Merkel pituitary<00:04:20.040> as<00:04:20.699> well<00:04:20.880> which<00:04:21.359> is<00:04:21.479> you<00:04:21.660> know<00:04:21.780> the 00:04:21.890 --> 00:04:21.900 align:start position:0% pituitary as well which is you know the 00:04:21.900 --> 00:04:25.070 align:start position:0% pituitary as well which is you know the data<00:04:22.260> structure<00:04:22.500> that<00:04:22.740> ethereum<00:04:23.160> uses<00:04:23.840> uh<00:04:24.840> we 00:04:25.070 --> 00:04:25.080 align:start position:0% data structure that ethereum uses uh we 00:04:25.080 --> 00:04:27.290 align:start position:0% data structure that ethereum uses uh we have<00:04:25.199> a<00:04:25.320> Dev<00:04:25.500> p2b<00:04:25.979> package<00:04:26.340> and<00:04:27.060> an 00:04:27.290 --> 00:04:27.300 align:start position:0% have a Dev p2b package and an 00:04:27.300 --> 00:04:29.510 align:start position:0% have a Dev p2b package and an experimental<00:04:27.840> client<00:04:28.139> uh<00:04:28.919> it<00:04:29.100> has<00:04:29.220> sync 00:04:29.510 --> 00:04:29.520 align:start position:0% experimental client uh it has sync 00:04:29.520 --> 00:04:31.189 align:start position:0% experimental client uh it has sync magnet<00:04:29.940> there's<00:04:30.180> been<00:04:30.360> a<00:04:30.479> guy<00:04:30.600> who<00:04:30.840> was<00:04:30.960> was 00:04:31.189 --> 00:04:31.199 align:start position:0% magnet there's been a guy who was was 00:04:31.199 --> 00:04:32.990 align:start position:0% magnet there's been a guy who was was able<00:04:31.440> to<00:04:31.620> sync<00:04:31.860> magnet<00:04:32.220> up<00:04:32.400> to<00:04:32.520> the<00:04:32.639> tip<00:04:32.759> of<00:04:32.880> the 00:04:32.990 --> 00:04:33.000 align:start position:0% able to sync magnet up to the tip of the 00:04:33.000 --> 00:04:36.469 align:start position:0% able to sync magnet up to the tip of the chain<00:04:33.199> it's<00:04:34.199> not<00:04:34.380> really<00:04:34.740> performant<00:04:35.639> so<00:04:36.300> I 00:04:36.469 --> 00:04:36.479 align:start position:0% chain it's not really performant so I 00:04:36.479 --> 00:04:37.610 align:start position:0% chain it's not really performant so I mean<00:04:36.600> you<00:04:36.720> wouldn't<00:04:36.840> want<00:04:37.080> to<00:04:37.199> use<00:04:37.320> it<00:04:37.440> in 00:04:37.610 --> 00:04:37.620 align:start position:0% mean you wouldn't want to use it in 00:04:37.620 --> 00:04:38.870 align:start position:0% mean you wouldn't want to use it in production<00:04:37.860> and<00:04:38.100> we<00:04:38.280> don't<00:04:38.400> have<00:04:38.520> like<00:04:38.699> the 00:04:38.870 --> 00:04:38.880 align:start position:0% production and we don't have like the 00:04:38.880 --> 00:04:40.969 align:start position:0% production and we don't have like the mitigation<00:04:39.300> that<00:04:39.660> are<00:04:39.840> in<00:04:40.199> place<00:04:40.380> for<00:04:40.620> more 00:04:40.969 --> 00:04:40.979 align:start position:0% mitigation that are in place for more 00:04:40.979 --> 00:04:43.370 align:start position:0% mitigation that are in place for more like<00:04:41.160> production<00:04:41.520> ready<00:04:41.699> clients<00:04:42.240> but<00:04:42.960> it<00:04:43.139> is 00:04:43.370 --> 00:04:43.380 align:start position:0% like production ready clients but it is 00:04:43.380 --> 00:04:46.550 align:start position:0% like production ready clients but it is able<00:04:43.620> to<00:04:43.740> run<00:04:43.919> all<00:04:44.280> all<00:04:44.580> blocks<00:04:44.940> from<00:04:45.060> mainnet 00:04:46.550 --> 00:04:46.560 align:start position:0% able to run all all blocks from mainnet 00:04:46.560 --> 00:04:49.010 align:start position:0% able to run all all blocks from mainnet so<00:04:47.400> yeah<00:04:47.759> I<00:04:47.880> was<00:04:48.060> just<00:04:48.180> mentioning<00:04:48.540> it's<00:04:48.780> used 00:04:49.010 --> 00:04:49.020 align:start position:0% so yeah I was just mentioning it's used 00:04:49.020 --> 00:04:51.350 align:start position:0% so yeah I was just mentioning it's used by<00:04:49.199> a<00:04:49.320> bunch<00:04:49.440> of<00:04:49.560> tooling<00:04:49.919> so<00:04:50.340> all<00:04:50.940> these<00:04:51.180> are 00:04:51.350 --> 00:04:51.360 align:start position:0% by a bunch of tooling so all these are 00:04:51.360 --> 00:04:52.969 align:start position:0% by a bunch of tooling so all these are some<00:04:51.660> of<00:04:51.720> the<00:04:51.840> you<00:04:52.080> know<00:04:52.199> packages<00:04:52.500> that<00:04:52.800> I'm 00:04:52.969 --> 00:04:52.979 align:start position:0% some of the you know packages that I'm 00:04:52.979 --> 00:04:54.590 align:start position:0% some of the you know packages that I'm sure<00:04:53.100> you're<00:04:53.340> familiar<00:04:53.699> with<00:04:53.820> like<00:04:54.000> hard<00:04:54.240> hat 00:04:54.590 --> 00:04:54.600 align:start position:0% sure you're familiar with like hard hat 00:04:54.600 --> 00:04:58.550 align:start position:0% sure you're familiar with like hard hat truffle<00:04:54.960> metamask<00:04:55.380> remix<00:04:56.120> uh<00:04:57.120> webster.js<00:04:57.900> and 00:04:58.550 --> 00:04:58.560 align:start position:0% truffle metamask remix uh webster.js and 00:04:58.560 --> 00:05:01.010 align:start position:0% truffle metamask remix uh webster.js and a<00:04:58.800> bunch<00:04:58.919> of<00:04:59.040> other<00:04:59.160> you<00:04:59.580> know<00:04:59.699> projects<00:05:00.300> uh 00:05:01.010 --> 00:05:01.020 align:start position:0% a bunch of other you know projects uh 00:05:01.020 --> 00:05:04.430 align:start position:0% a bunch of other you know projects uh use<00:05:01.440> us<00:05:01.800> as<00:05:02.160> a<00:05:02.400> dependency<00:05:02.940> for<00:05:03.419> to<00:05:03.960> to<00:05:04.199> build 00:05:04.430 --> 00:05:04.440 align:start position:0% use us as a dependency for to to build 00:05:04.440 --> 00:05:07.969 align:start position:0% use us as a dependency for to to build upon 00:05:07.969 --> 00:05:07.979 align:start position:0% 00:05:07.979 --> 00:05:11.990 align:start position:0% so<00:05:08.460> yeah<00:05:08.639> let<00:05:09.000> us<00:05:09.180> give<00:05:09.419> you<00:05:09.600> uh<00:05:10.320> an<00:05:10.620> overview 00:05:11.990 --> 00:05:12.000 align:start position:0% so yeah let us give you uh an overview 00:05:12.000 --> 00:05:14.810 align:start position:0% so yeah let us give you uh an overview of<00:05:12.300> how<00:05:12.960> the<00:05:13.919> um 00:05:14.810 --> 00:05:14.820 align:start position:0% of how the um 00:05:14.820 --> 00:05:18.230 align:start position:0% of how the um ethereum<00:05:15.780> uh<00:05:16.259> JS<00:05:16.740> packages<00:05:17.220> kind<00:05:18.000> of<00:05:18.120> work 00:05:18.230 --> 00:05:18.240 align:start position:0% ethereum uh JS packages kind of work 00:05:18.240 --> 00:05:21.409 align:start position:0% ethereum uh JS packages kind of work together<00:05:18.479> right<00:05:19.199> so<00:05:20.040> at<00:05:20.220> the<00:05:20.340> very<00:05:20.520> bottom<00:05:20.820> we 00:05:21.409 --> 00:05:21.419 align:start position:0% together right so at the very bottom we 00:05:21.419 --> 00:05:24.350 align:start position:0% together right so at the very bottom we have<00:05:21.600> the<00:05:21.900> client<00:05:22.199> now<00:05:22.979> the<00:05:23.340> arrows<00:05:23.759> pointing 00:05:24.350 --> 00:05:24.360 align:start position:0% have the client now the arrows pointing 00:05:24.360 --> 00:05:26.210 align:start position:0% have the client now the arrows pointing to<00:05:24.539> the<00:05:24.720> client<00:05:24.960> mean<00:05:25.199> that<00:05:25.500> the<00:05:25.680> client<00:05:25.919> is 00:05:26.210 --> 00:05:26.220 align:start position:0% to the client mean that the client is 00:05:26.220 --> 00:05:29.510 align:start position:0% to the client mean that the client is importing<00:05:27.240> you<00:05:27.780> know<00:05:27.900> the<00:05:28.080> packages<00:05:28.620> uh<00:05:29.280> all 00:05:29.510 --> 00:05:29.520 align:start position:0% importing you know the packages uh all 00:05:29.520 --> 00:05:31.850 align:start position:0% importing you know the packages uh all these<00:05:29.759> other<00:05:29.940> you<00:05:30.240> know<00:05:30.300> packages<00:05:30.720> so<00:05:31.560> at<00:05:31.740> the 00:05:31.850 --> 00:05:31.860 align:start position:0% these other you know packages so at the 00:05:31.860 --> 00:05:33.529 align:start position:0% these other you know packages so at the very<00:05:31.979> bottom<00:05:32.280> we<00:05:32.460> have<00:05:32.580> client<00:05:32.880> which<00:05:33.060> Imports 00:05:33.529 --> 00:05:33.539 align:start position:0% very bottom we have client which Imports 00:05:33.539 --> 00:05:34.969 align:start position:0% very bottom we have client which Imports basically<00:05:33.840> everything<00:05:34.080> that<00:05:34.440> we've<00:05:34.620> built<00:05:34.919> in 00:05:34.969 --> 00:05:34.979 align:start position:0% basically everything that we've built in 00:05:34.979 --> 00:05:37.610 align:start position:0% basically everything that we've built in the<00:05:35.100> model<00:05:35.220> repo<00:05:35.759> or<00:05:36.240> as<00:05:36.479> common<00:05:36.840> is<00:05:37.440> just 00:05:37.610 --> 00:05:37.620 align:start position:0% the model repo or as common is just 00:05:37.620 --> 00:05:41.090 align:start position:0% the model repo or as common is just going<00:05:37.740> to<00:05:37.919> be<00:05:38.039> more<00:05:38.820> uh<00:05:39.180> like<00:05:39.960> General<00:05:40.740> things 00:05:41.090 --> 00:05:41.100 align:start position:0% going to be more uh like General things 00:05:41.100 --> 00:05:43.310 align:start position:0% going to be more uh like General things that<00:05:41.400> you<00:05:41.639> probably<00:05:41.940> wouldn't<00:05:42.240> use<00:05:42.600> uh<00:05:43.139> by 00:05:43.310 --> 00:05:43.320 align:start position:0% that you probably wouldn't use uh by 00:05:43.320 --> 00:05:44.629 align:start position:0% that you probably wouldn't use uh by themselves<00:05:43.680> but<00:05:43.860> are<00:05:44.039> going<00:05:44.160> to<00:05:44.280> be<00:05:44.340> helpful 00:05:44.629 --> 00:05:44.639 align:start position:0% themselves but are going to be helpful 00:05:44.639 --> 00:05:47.450 align:start position:0% themselves but are going to be helpful for<00:05:45.180> uh<00:05:45.840> like<00:05:46.080> for<00:05:46.560> example<00:05:46.800> in<00:05:46.979> common<00:05:47.160> you 00:05:47.450 --> 00:05:47.460 align:start position:0% for uh like for example in common you 00:05:47.460 --> 00:05:49.310 align:start position:0% for uh like for example in common you would<00:05:47.580> have<00:05:47.699> like<00:05:48.000> specifications<00:05:48.780> for<00:05:49.080> hard 00:05:49.310 --> 00:05:49.320 align:start position:0% would have like specifications for hard 00:05:49.320 --> 00:05:52.189 align:start position:0% would have like specifications for hard forks<00:05:49.860> and<00:05:50.400> stuff<00:05:50.699> like<00:05:50.880> that<00:05:51.060> which<00:05:51.539> if<00:05:52.080> you 00:05:52.189 --> 00:05:52.199 align:start position:0% forks and stuff like that which if you 00:05:52.199 --> 00:05:53.990 align:start position:0% forks and stuff like that which if you wanna<00:05:52.500> you<00:05:53.039> know<00:05:53.100> build<00:05:53.220> a<00:05:53.400> block<00:05:53.580> you<00:05:53.880> know 00:05:53.990 --> 00:05:54.000 align:start position:0% wanna you know build a block you know 00:05:54.000 --> 00:05:55.610 align:start position:0% wanna you know build a block you know you<00:05:54.180> need<00:05:54.360> to<00:05:54.479> know<00:05:54.600> like<00:05:54.840> which<00:05:55.020> hard<00:05:55.259> Fork 00:05:55.610 --> 00:05:55.620 align:start position:0% you need to know like which hard Fork 00:05:55.620 --> 00:05:56.810 align:start position:0% you need to know like which hard Fork You're<00:05:55.740> Building<00:05:55.919> you<00:05:56.220> know<00:05:56.340> a<00:05:56.460> block<00:05:56.580> for 00:05:56.810 --> 00:05:56.820 align:start position:0% You're Building you know a block for 00:05:56.820 --> 00:05:58.969 align:start position:0% You're Building you know a block for same<00:05:57.539> thing<00:05:57.660> with<00:05:57.780> a<00:05:57.960> transaction<00:05:58.320> same<00:05:58.860> thing 00:05:58.969 --> 00:05:58.979 align:start position:0% same thing with a transaction same thing 00:05:58.979 --> 00:06:00.770 align:start position:0% same thing with a transaction same thing if<00:05:59.160> you<00:05:59.340> want<00:05:59.460> to<00:05:59.580> run<00:05:59.639> a<00:05:59.820> block<00:06:00.000> in<00:06:00.180> the<00:06:00.300> evm 00:06:00.770 --> 00:06:00.780 align:start position:0% if you want to run a block in the evm 00:06:00.780 --> 00:06:02.749 align:start position:0% if you want to run a block in the evm and<00:06:01.259> stuff<00:06:01.440> like<00:06:01.620> that<00:06:01.740> so<00:06:01.979> that<00:06:02.100> all<00:06:02.280> lives<00:06:02.580> in 00:06:02.749 --> 00:06:02.759 align:start position:0% and stuff like that so that all lives in 00:06:02.759 --> 00:06:04.790 align:start position:0% and stuff like that so that all lives in common<00:06:02.880> we've<00:06:03.360> tried<00:06:03.600> to<00:06:03.720> modulize<00:06:04.320> it<00:06:04.440> in<00:06:04.680> a 00:06:04.790 --> 00:06:04.800 align:start position:0% common we've tried to modulize it in a 00:06:04.800 --> 00:06:06.529 align:start position:0% common we've tried to modulize it in a way<00:06:04.919> that's<00:06:05.160> more<00:06:05.520> that<00:06:06.000> makes<00:06:06.180> more<00:06:06.360> sense 00:06:06.529 --> 00:06:06.539 align:start position:0% way that's more that makes more sense 00:06:06.539 --> 00:06:09.830 align:start position:0% way that's more that makes more sense and<00:06:06.720> it<00:06:06.900> makes<00:06:07.080> it<00:06:07.259> easy<00:06:07.500> to<00:06:08.300> to<00:06:09.300> Import<00:06:09.539> and 00:06:09.830 --> 00:06:09.840 align:start position:0% and it makes it easy to to Import and 00:06:09.840 --> 00:06:12.050 align:start position:0% and it makes it easy to to Import and Export<00:06:10.139> things<00:06:10.380> without<00:06:10.740> them<00:06:11.520> being<00:06:11.759> all 00:06:12.050 --> 00:06:12.060 align:start position:0% Export things without them being all 00:06:12.060 --> 00:06:15.790 align:start position:0% Export things without them being all intertwined 00:06:15.790 --> 00:06:15.800 align:start position:0% 00:06:15.800 --> 00:06:18.469 align:start position:0% so<00:06:16.800> yeah<00:06:17.100> you<00:06:17.520> might<00:06:17.639> have<00:06:17.820> heard<00:06:17.940> like<00:06:18.180> the 00:06:18.469 --> 00:06:18.479 align:start position:0% so yeah you might have heard like the 00:06:18.479 --> 00:06:23.150 align:start position:0% so yeah you might have heard like the term<00:06:18.600> VM<00:06:19.340> evm<00:06:20.340> eei<00:06:21.120> we<00:06:21.960> also<00:06:22.199> have<00:06:22.380> you<00:06:22.680> know<00:06:22.740> a 00:06:23.150 --> 00:06:23.160 align:start position:0% term VM evm eei we also have you know a 00:06:23.160 --> 00:06:24.890 align:start position:0% term VM evm eei we also have you know a state<00:06:23.400> manager 00:06:24.890 --> 00:06:24.900 align:start position:0% state manager 00:06:24.900 --> 00:06:28.430 align:start position:0% state manager so<00:06:25.440> basically<00:06:25.919> uh<00:06:26.639> VM<00:06:27.120> is<00:06:27.479> like<00:06:27.720> a<00:06:28.020> higher 00:06:28.430 --> 00:06:28.440 align:start position:0% so basically uh VM is like a higher 00:06:28.440 --> 00:06:31.249 align:start position:0% so basically uh VM is like a higher level<00:06:28.620> like<00:06:29.280> virtual<00:06:29.759> machines<00:06:30.259> virtual 00:06:31.249 --> 00:06:31.259 align:start position:0% level like virtual machines virtual 00:06:31.259 --> 00:06:32.150 align:start position:0% level like virtual machines virtual machine 00:06:32.150 --> 00:06:32.160 align:start position:0% machine 00:06:32.160 --> 00:06:35.809 align:start position:0% machine which<00:06:32.819> uh<00:06:33.720> sends<00:06:34.620> you<00:06:34.860> know<00:06:35.220> you<00:06:35.699> would 00:06:35.809 --> 00:06:35.819 align:start position:0% which uh sends you know you would 00:06:35.819 --> 00:06:37.249 align:start position:0% which uh sends you know you would provide<00:06:36.120> that<00:06:36.300> like<00:06:36.419> a<00:06:36.600> block<00:06:36.780> you<00:06:37.020> would<00:06:37.139> tell 00:06:37.249 --> 00:06:37.259 align:start position:0% provide that like a block you would tell 00:06:37.259 --> 00:06:39.950 align:start position:0% provide that like a block you would tell the<00:06:37.440> VM<00:06:37.740> hey<00:06:38.160> I<00:06:38.520> want<00:06:38.759> you<00:06:38.880> to<00:06:39.000> run<00:06:39.120> a<00:06:39.240> block<00:06:39.419> or 00:06:39.950 --> 00:06:39.960 align:start position:0% the VM hey I want you to run a block or 00:06:39.960 --> 00:06:42.170 align:start position:0% the VM hey I want you to run a block or I<00:06:40.080> want<00:06:40.259> you<00:06:40.380> to<00:06:40.500> run<00:06:40.620> a<00:06:40.800> transaction<00:06:41.160> that<00:06:41.940> it 00:06:42.170 --> 00:06:42.180 align:start position:0% I want you to run a transaction that it 00:06:42.180 --> 00:06:45.110 align:start position:0% I want you to run a transaction that it would<00:06:42.360> forward<00:06:43.280> uh<00:06:44.280> an<00:06:44.580> individual<00:06:44.940> like 00:06:45.110 --> 00:06:45.120 align:start position:0% would forward uh an individual like 00:06:45.120 --> 00:06:47.150 align:start position:0% would forward uh an individual like message<00:06:45.419> calls<00:06:45.960> to<00:06:46.080> the<00:06:46.199> evm<00:06:46.620> which<00:06:46.979> would 00:06:47.150 --> 00:06:47.160 align:start position:0% message calls to the evm which would 00:06:47.160 --> 00:06:49.189 align:start position:0% message calls to the evm which would deal<00:06:47.400> with<00:06:47.580> like<00:06:47.699> the<00:06:47.880> op<00:06:48.000> codes<00:06:48.240> and<00:06:48.660> all<00:06:49.020> that 00:06:49.189 --> 00:06:49.199 align:start position:0% deal with like the op codes and all that 00:06:49.199 --> 00:06:51.650 align:start position:0% deal with like the op codes and all that sort<00:06:49.380> of<00:06:49.500> stuff<00:06:49.620> then<00:06:50.400> the<00:06:50.639> evm<00:06:51.120> would<00:06:51.479> report 00:06:51.650 --> 00:06:51.660 align:start position:0% sort of stuff then the evm would report 00:06:51.660 --> 00:06:53.390 align:start position:0% sort of stuff then the evm would report back<00:06:52.020> and<00:06:52.500> communicate<00:06:52.919> with<00:06:53.100> a<00:06:53.220> state 00:06:53.390 --> 00:06:53.400 align:start position:0% back and communicate with a state 00:06:53.400 --> 00:06:54.710 align:start position:0% back and communicate with a state manager<00:06:53.759> that's<00:06:53.940> going<00:06:54.120> to<00:06:54.240> update<00:06:54.539> like 00:06:54.710 --> 00:06:54.720 align:start position:0% manager that's going to update like 00:06:54.720 --> 00:06:56.930 align:start position:0% manager that's going to update like whatever<00:06:54.960> state<00:06:55.319> you<00:06:55.560> have<00:06:55.800> uh<00:06:56.460> in<00:06:56.759> your 00:06:56.930 --> 00:06:56.940 align:start position:0% whatever state you have uh in your 00:06:56.940 --> 00:06:58.670 align:start position:0% whatever state you have uh in your Miracle<00:06:57.419> particular<00:06:57.840> tree<00:06:58.080> so<00:06:58.380> it's<00:06:58.500> much 00:06:58.670 --> 00:06:58.680 align:start position:0% Miracle particular tree so it's much 00:06:58.680 --> 00:06:59.870 align:start position:0% Miracle particular tree so it's much easier<00:06:58.919> to<00:06:59.100> interact<00:06:59.400> with<00:06:59.520> the<00:06:59.699> state 00:06:59.870 --> 00:06:59.880 align:start position:0% easier to interact with the state 00:06:59.880 --> 00:07:01.969 align:start position:0% easier to interact with the state manager<00:07:00.300> because<00:07:00.600> then<00:07:00.840> you<00:07:01.080> can<00:07:01.199> just<00:07:01.380> for 00:07:01.969 --> 00:07:01.979 align:start position:0% manager because then you can just for 00:07:01.979 --> 00:07:04.070 align:start position:0% manager because then you can just for example<00:07:02.220> update<00:07:02.639> an<00:07:02.759> account<00:07:02.940> balance<00:07:03.539> rather 00:07:04.070 --> 00:07:04.080 align:start position:0% example update an account balance rather 00:07:04.080 --> 00:07:06.350 align:start position:0% example update an account balance rather than<00:07:04.259> like<00:07:04.620> finding<00:07:05.460> the<00:07:05.639> proper<00:07:05.940> key<00:07:06.060> in<00:07:06.240> the 00:07:06.350 --> 00:07:06.360 align:start position:0% than like finding the proper key in the 00:07:06.360 --> 00:07:08.150 align:start position:0% than like finding the proper key in the Merkel<00:07:06.660> particular<00:07:07.080> tree<00:07:07.259> updating<00:07:07.620> that<00:07:07.919> and 00:07:08.150 --> 00:07:08.160 align:start position:0% Merkel particular tree updating that and 00:07:08.160 --> 00:07:10.129 align:start position:0% Merkel particular tree updating that and recomputing<00:07:08.940> the<00:07:09.120> route<00:07:09.300> which<00:07:09.600> would<00:07:09.720> be<00:07:09.900> you 00:07:10.129 --> 00:07:10.139 align:start position:0% recomputing the route which would be you 00:07:10.139 --> 00:07:11.809 align:start position:0% recomputing the route which would be you know<00:07:10.259> super<00:07:10.500> tedious<00:07:10.979> obviously<00:07:11.340> so<00:07:11.580> we've 00:07:11.809 --> 00:07:11.819 align:start position:0% know super tedious obviously so we've 00:07:11.819 --> 00:07:13.610 align:start position:0% know super tedious obviously so we've abstracted<00:07:12.360> most<00:07:12.720> of<00:07:12.900> that<00:07:12.960> away<00:07:13.199> with<00:07:13.440> the 00:07:13.610 --> 00:07:13.620 align:start position:0% abstracted most of that away with the 00:07:13.620 --> 00:07:16.809 align:start position:0% abstracted most of that away with the the<00:07:13.800> state<00:07:14.039> manager 00:07:16.809 --> 00:07:16.819 align:start position:0% 00:07:16.819 --> 00:07:20.330 align:start position:0% yeah<00:07:17.819> I'll<00:07:18.240> leave<00:07:19.139> here<00:07:19.380> discarding<00:07:20.039> to<00:07:20.220> talk 00:07:20.330 --> 00:07:20.340 align:start position:0% yeah I'll leave here discarding to talk 00:07:20.340 --> 00:07:21.710 align:start position:0% yeah I'll leave here discarding to talk about<00:07:20.460> the<00:07:20.699> portal<00:07:21.060> Network<00:07:21.240> which<00:07:21.599> is 00:07:21.710 --> 00:07:21.720 align:start position:0% about the portal Network which is 00:07:21.720 --> 00:07:23.390 align:start position:0% about the portal Network which is another<00:07:21.840> thing<00:07:22.199> that<00:07:22.500> we<00:07:22.680> are<00:07:22.919> working<00:07:23.160> on 00:07:23.390 --> 00:07:23.400 align:start position:0% another thing that we are working on 00:07:23.400 --> 00:07:26.029 align:start position:0% another thing that we are working on right<00:07:24.180> portal<00:07:24.840> Network 00:07:26.029 --> 00:07:26.039 align:start position:0% right portal Network 00:07:26.039 --> 00:07:28.909 align:start position:0% right portal Network um<00:07:26.099> it's<00:07:26.400> actually<00:07:26.580> a<00:07:26.819> series<00:07:27.060> of<00:07:27.720> of<00:07:28.319> networks 00:07:28.909 --> 00:07:28.919 align:start position:0% um it's actually a series of of networks 00:07:28.919 --> 00:07:30.770 align:start position:0% um it's actually a series of of networks that<00:07:29.099> are<00:07:29.220> peer-to-peer<00:07:29.880> networks<00:07:30.360> special 00:07:30.770 --> 00:07:30.780 align:start position:0% that are peer-to-peer networks special 00:07:30.780 --> 00:07:33.589 align:start position:0% that are peer-to-peer networks special storage<00:07:31.319> networks<00:07:32.099> and<00:07:32.400> this<00:07:32.639> is 00:07:33.589 --> 00:07:33.599 align:start position:0% storage networks and this is 00:07:33.599 --> 00:07:35.930 align:start position:0% storage networks and this is all<00:07:34.199> in<00:07:34.560> under<00:07:34.919> construction<00:07:35.220> and<00:07:35.759> under 00:07:35.930 --> 00:07:35.940 align:start position:0% all in under construction and under 00:07:35.940 --> 00:07:37.610 align:start position:0% all in under construction and under design<00:07:36.240> at<00:07:36.539> the<00:07:36.720> moment<00:07:36.840> but<00:07:37.199> we<00:07:37.500> are 00:07:37.610 --> 00:07:37.620 align:start position:0% design at the moment but we are 00:07:37.620 --> 00:07:40.730 align:start position:0% design at the moment but we are implementing<00:07:38.479> portal<00:07:39.479> Network<00:07:39.660> clients<00:07:40.259> in 00:07:40.730 --> 00:07:40.740 align:start position:0% implementing portal Network clients in 00:07:40.740 --> 00:07:44.930 align:start position:0% implementing portal Network clients in typescript<00:07:41.220> using<00:07:41.819> ethereum<00:07:42.300> JS<00:07:42.720> libraries 00:07:44.930 --> 00:07:44.940 align:start position:0% typescript using ethereum JS libraries 00:07:44.940 --> 00:07:48.110 align:start position:0% typescript using ethereum JS libraries um<00:07:45.060> there<00:07:45.539> are<00:07:45.660> two<00:07:46.080> other<00:07:46.319> teams<00:07:46.740> working<00:07:47.039> in 00:07:48.110 --> 00:07:48.120 align:start position:0% um there are two other teams working in 00:07:48.120 --> 00:07:50.570 align:start position:0% um there are two other teams working in rust<00:07:48.840> and<00:07:49.139> Nim<00:07:49.380> at<00:07:49.800> the<00:07:49.919> same<00:07:50.039> time<00:07:50.280> to 00:07:50.570 --> 00:07:50.580 align:start position:0% rust and Nim at the same time to 00:07:50.580 --> 00:07:55.490 align:start position:0% rust and Nim at the same time to implement<00:07:50.880> this 00:07:55.490 --> 00:07:55.500 align:start position:0% 00:07:55.500 --> 00:07:57.650 align:start position:0% so<00:07:55.860> essentially<00:07:56.220> if<00:07:56.520> you<00:07:56.759> if<00:07:57.240> you<00:07:57.479> want<00:07:57.539> to 00:07:57.650 --> 00:07:57.660 align:start position:0% so essentially if you if you want to 00:07:57.660 --> 00:07:59.330 align:start position:0% so essentially if you if you want to interact<00:07:57.960> with<00:07:58.259> the<00:07:58.500> blockchain<00:07:58.860> right<00:07:59.160> now 00:07:59.330 --> 00:07:59.340 align:start position:0% interact with the blockchain right now 00:07:59.340 --> 00:08:01.550 align:start position:0% interact with the blockchain right now you<00:08:00.060> either<00:08:00.240> need<00:08:00.539> to<00:08:00.660> run<00:08:00.900> your<00:08:01.259> own<00:08:01.319> full 00:08:01.550 --> 00:08:01.560 align:start position:0% you either need to run your own full 00:08:01.560 --> 00:08:03.650 align:start position:0% you either need to run your own full node<00:08:01.919> which<00:08:02.220> is<00:08:02.400> a<00:08:02.759> very<00:08:02.940> heavy<00:08:03.300> process 00:08:03.650 --> 00:08:03.660 align:start position:0% node which is a very heavy process 00:08:03.660 --> 00:08:05.390 align:start position:0% node which is a very heavy process requiring<00:08:04.259> a<00:08:04.560> lot 00:08:05.390 --> 00:08:05.400 align:start position:0% requiring a lot 00:08:05.400 --> 00:08:07.390 align:start position:0% requiring a lot of<00:08:05.639> your<00:08:06.000> resources 00:08:07.390 --> 00:08:07.400 align:start position:0% of your resources 00:08:07.400 --> 00:08:09.409 align:start position:0% of your resources and<00:08:08.400> most 00:08:09.409 --> 00:08:09.419 align:start position:0% and most 00:08:09.419 --> 00:08:11.450 align:start position:0% and most most<00:08:09.840> people<00:08:10.259> aren't<00:08:10.620> going<00:08:10.800> to<00:08:10.919> do<00:08:11.039> that<00:08:11.220> and 00:08:11.450 --> 00:08:11.460 align:start position:0% most people aren't going to do that and 00:08:11.460 --> 00:08:13.309 align:start position:0% most people aren't going to do that and most<00:08:11.639> devices<00:08:12.000> aren't<00:08:12.360> going<00:08:12.599> to<00:08:12.780> want<00:08:12.960> to<00:08:13.139> do 00:08:13.309 --> 00:08:13.319 align:start position:0% most devices aren't going to want to do 00:08:13.319 --> 00:08:15.610 align:start position:0% most devices aren't going to want to do that<00:08:13.500> I<00:08:13.979> have<00:08:14.160> some<00:08:14.340> most<00:08:14.520> reach<00:08:14.880> out<00:08:15.000> to 00:08:15.610 --> 00:08:15.620 align:start position:0% that I have some most reach out to 00:08:15.620 --> 00:08:18.830 align:start position:0% that I have some most reach out to inferior<00:08:16.620> which<00:08:17.039> is<00:08:17.099> a<00:08:17.340> centralized 00:08:18.830 --> 00:08:18.840 align:start position:0% inferior which is a centralized 00:08:18.840 --> 00:08:21.290 align:start position:0% inferior which is a centralized access<00:08:19.500> to<00:08:19.860> the<00:08:19.979> blockchain<00:08:20.340> which<00:08:20.819> works 00:08:21.290 --> 00:08:21.300 align:start position:0% access to the blockchain which works 00:08:21.300 --> 00:08:22.670 align:start position:0% access to the blockchain which works fine<00:08:21.479> but<00:08:21.840> it 00:08:22.670 --> 00:08:22.680 align:start position:0% fine but it 00:08:22.680 --> 00:08:24.950 align:start position:0% fine but it is<00:08:23.280> a<00:08:23.520> centralized<00:08:24.000> access<00:08:24.180> to<00:08:24.479> blockchain 00:08:24.950 --> 00:08:24.960 align:start position:0% is a centralized access to blockchain 00:08:24.960 --> 00:08:26.689 align:start position:0% is a centralized access to blockchain which<00:08:25.379> is<00:08:25.560> kind<00:08:25.919> of<00:08:26.039> the<00:08:26.160> thing<00:08:26.280> we're<00:08:26.460> trying 00:08:26.689 --> 00:08:26.699 align:start position:0% which is kind of the thing we're trying 00:08:26.699 --> 00:08:27.890 align:start position:0% which is kind of the thing we're trying to<00:08:26.819> avoid 00:08:27.890 --> 00:08:27.900 align:start position:0% to avoid 00:08:27.900 --> 00:08:29.629 align:start position:0% to avoid so<00:08:28.500> it 00:08:29.629 --> 00:08:29.639 align:start position:0% so it 00:08:29.639 --> 00:08:31.369 align:start position:0% so it people<00:08:30.060> have<00:08:30.300> been<00:08:30.479> working<00:08:30.660> for<00:08:31.020> many<00:08:31.139> years 00:08:31.369 --> 00:08:31.379 align:start position:0% people have been working for many years 00:08:31.379 --> 00:08:33.529 align:start position:0% people have been working for many years trying<00:08:31.800> to<00:08:31.919> figure<00:08:32.039> out<00:08:32.339> what<00:08:32.700> goes<00:08:33.120> up<00:08:33.360> in 00:08:33.529 --> 00:08:33.539 align:start position:0% trying to figure out what goes up in 00:08:33.539 --> 00:08:35.810 align:start position:0% trying to figure out what goes up in that<00:08:33.659> top<00:08:33.899> left<00:08:34.140> box<00:08:34.800> where<00:08:35.279> we<00:08:35.520> can<00:08:35.640> have 00:08:35.810 --> 00:08:35.820 align:start position:0% that top left box where we can have 00:08:35.820 --> 00:08:37.550 align:start position:0% that top left box where we can have something<00:08:36.060> lightweight 00:08:37.550 --> 00:08:37.560 align:start position:0% something lightweight 00:08:37.560 --> 00:08:41.449 align:start position:0% something lightweight accessible<00:08:38.399> but<00:08:38.940> also<00:08:39.240> decentralized<00:08:40.140> and 00:08:41.449 --> 00:08:41.459 align:start position:0% accessible but also decentralized and 00:08:41.459 --> 00:08:44.089 align:start position:0% accessible but also decentralized and the<00:08:41.700> work<00:08:41.940> on<00:08:42.240> Les<00:08:42.839> light<00:08:43.200> clients<00:08:43.740> has 00:08:44.089 --> 00:08:44.099 align:start position:0% the work on Les light clients has 00:08:44.099 --> 00:08:45.949 align:start position:0% the work on Les light clients has eventually<00:08:44.700> led<00:08:45.060> us<00:08:45.180> this<00:08:45.360> concept<00:08:45.720> called 00:08:45.949 --> 00:08:45.959 align:start position:0% eventually led us this concept called 00:08:45.959 --> 00:08:49.009 align:start position:0% eventually led us this concept called the<00:08:46.140> portal<00:08:46.500> portal<00:08:47.040> Network 00:08:49.009 --> 00:08:49.019 align:start position:0% the portal portal Network 00:08:49.019 --> 00:08:49.970 align:start position:0% the portal portal Network um 00:08:49.970 --> 00:08:49.980 align:start position:0% um 00:08:49.980 --> 00:08:53.329 align:start position:0% um portal<00:08:50.700> network<00:08:50.880> is 00:08:53.329 --> 00:08:53.339 align:start position:0% portal network is 00:08:53.339 --> 00:08:55.070 align:start position:0% portal network is it's<00:08:53.760> an<00:08:54.000> in<00:08:54.180> it's<00:08:54.540> an<00:08:54.660> independent 00:08:55.070 --> 00:08:55.080 align:start position:0% it's an in it's an independent 00:08:55.080 --> 00:08:57.430 align:start position:0% it's an in it's an independent peer-to-peer<00:08:55.620> Network<00:08:55.800> it's<00:08:56.100> almost<00:08:56.279> like<00:08:56.700> a 00:08:57.430 --> 00:08:57.440 align:start position:0% peer-to-peer Network it's almost like a 00:08:57.440 --> 00:08:59.329 align:start position:0% peer-to-peer Network it's almost like a bittorrents<00:08:58.440> it's<00:08:58.620> working<00:08:58.800> on<00:08:59.100> that 00:08:59.329 --> 00:08:59.339 align:start position:0% bittorrents it's working on that 00:08:59.339 --> 00:09:01.670 align:start position:0% bittorrents it's working on that principle<00:08:59.940> where 00:09:01.670 --> 00:09:01.680 align:start position:0% principle where 00:09:01.680 --> 00:09:02.930 align:start position:0% principle where um 00:09:02.930 --> 00:09:02.940 align:start position:0% um 00:09:02.940 --> 00:09:07.310 align:start position:0% um if<00:09:03.300> you<00:09:03.480> need<00:09:03.660> access<00:09:04.019> to 00:09:07.310 --> 00:09:07.320 align:start position:0% 00:09:07.320 --> 00:09:09.110 align:start position:0% some<00:09:07.800> amount<00:09:08.100> of<00:09:08.220> information<00:09:08.459> from<00:09:08.940> the 00:09:09.110 --> 00:09:09.120 align:start position:0% some amount of information from the 00:09:09.120 --> 00:09:10.850 align:start position:0% some amount of information from the blockchain<00:09:09.540> you<00:09:09.959> don't<00:09:10.140> need<00:09:10.380> to<00:09:10.620> actually 00:09:10.850 --> 00:09:10.860 align:start position:0% blockchain you don't need to actually 00:09:10.860 --> 00:09:13.850 align:start position:0% blockchain you don't need to actually sync<00:09:11.399> to<00:09:11.519> the<00:09:11.700> entire<00:09:12.000> blockchain<00:09:12.540> to 00:09:13.850 --> 00:09:13.860 align:start position:0% sync to the entire blockchain to 00:09:13.860 --> 00:09:16.070 align:start position:0% sync to the entire blockchain to retrieve<00:09:14.700> your<00:09:15.000> you<00:09:15.600> know<00:09:15.720> your<00:09:15.899> block 00:09:16.070 --> 00:09:16.080 align:start position:0% retrieve your you know your block 00:09:16.080 --> 00:09:18.949 align:start position:0% retrieve your you know your block history<00:09:16.320> or<00:09:16.800> your<00:09:16.920> account<00:09:17.160> history<00:09:17.459> or<00:09:18.180> many 00:09:18.949 --> 00:09:18.959 align:start position:0% history or your account history or many 00:09:18.959 --> 00:09:21.170 align:start position:0% history or your account history or many of<00:09:19.080> the<00:09:19.320> things<00:09:19.500> that<00:09:19.980> human<00:09:20.160> driven<00:09:20.700> wallet 00:09:21.170 --> 00:09:21.180 align:start position:0% of the things that human driven wallet 00:09:21.180 --> 00:09:22.850 align:start position:0% of the things that human driven wallet interactions 00:09:22.850 --> 00:09:22.860 align:start position:0% interactions 00:09:22.860 --> 00:09:24.470 align:start position:0% interactions um 00:09:24.470 --> 00:09:24.480 align:start position:0% um 00:09:24.480 --> 00:09:27.290 align:start position:0% um need<00:09:25.440> so<00:09:26.160> that's<00:09:26.339> the<00:09:26.519> idea<00:09:26.820> we<00:09:27.060> we're 00:09:27.290 --> 00:09:27.300 align:start position:0% need so that's the idea we we're 00:09:27.300 --> 00:09:30.769 align:start position:0% need so that's the idea we we're building<00:09:28.220> networks<00:09:29.220> to<00:09:29.519> support<00:09:29.760> the<00:09:30.360> users 00:09:30.769 --> 00:09:30.779 align:start position:0% building networks to support the users 00:09:30.779 --> 00:09:33.590 align:start position:0% building networks to support the users of<00:09:31.019> this<00:09:31.200> protocol<00:09:31.560> not<00:09:31.980> necessarily 00:09:33.590 --> 00:09:33.600 align:start position:0% of this protocol not necessarily 00:09:33.600 --> 00:09:35.750 align:start position:0% of this protocol not necessarily building<00:09:34.080> up<00:09:34.380> the<00:09:34.560> protocol<00:09:34.860> itself<00:09:35.279> the<00:09:35.580> way 00:09:35.750 --> 00:09:35.760 align:start position:0% building up the protocol itself the way 00:09:35.760 --> 00:09:39.230 align:start position:0% building up the protocol itself the way a<00:09:35.940> real<00:09:36.120> full<00:09:36.540> node<00:09:37.440> does<00:09:37.680> and 00:09:39.230 --> 00:09:39.240 align:start position:0% a real full node does and 00:09:39.240 --> 00:09:42.710 align:start position:0% a real full node does and therefore<00:09:39.899> this<00:09:40.260> can<00:09:40.440> exist<00:09:40.800> on<00:09:41.399> very<00:09:42.300> light 00:09:42.710 --> 00:09:42.720 align:start position:0% therefore this can exist on very light 00:09:42.720 --> 00:09:44.810 align:start position:0% therefore this can exist on very light resource<00:09:43.440> constrained<00:09:43.920> devices<00:09:44.279> you<00:09:44.760> could 00:09:44.810 --> 00:09:44.820 align:start position:0% resource constrained devices you could 00:09:44.820 --> 00:09:47.870 align:start position:0% resource constrained devices you could build<00:09:45.060> it<00:09:45.300> into<00:09:45.740> the<00:09:46.740> back<00:09:46.860> end<00:09:47.040> of<00:09:47.399> a<00:09:47.580> wallet 00:09:47.870 --> 00:09:47.880 align:start position:0% build it into the back end of a wallet 00:09:47.880 --> 00:09:49.910 align:start position:0% build it into the back end of a wallet app<00:09:48.120> and<00:09:48.540> it<00:09:48.600> can<00:09:48.779> just<00:09:48.899> be<00:09:49.019> running<00:09:49.320> in<00:09:49.800> the 00:09:49.910 --> 00:09:49.920 align:start position:0% app and it can just be running in the 00:09:49.920 --> 00:09:52.250 align:start position:0% app and it can just be running in the background<00:09:50.279> of<00:09:51.000> your<00:09:51.300> phone<00:09:51.480> or<00:09:51.839> your<00:09:52.080> watch 00:09:52.250 --> 00:09:52.260 align:start position:0% background of your phone or your watch 00:09:52.260 --> 00:09:55.790 align:start position:0% background of your phone or your watch or<00:09:52.680> your<00:09:52.920> anything<00:09:53.399> and 00:09:55.790 --> 00:09:55.800 align:start position:0% or your anything and 00:09:55.800 --> 00:09:58.430 align:start position:0% or your anything and um<00:09:56.220> potentially<00:09:56.880> the<00:09:57.180> more<00:09:57.360> more<00:09:58.080> devices 00:09:58.430 --> 00:09:58.440 align:start position:0% um potentially the more more devices 00:09:58.440 --> 00:10:00.110 align:start position:0% um potentially the more more devices hooked<00:09:58.920> into<00:09:59.040> these<00:09:59.399> networks<00:09:59.760> the<00:09:59.940> better 00:10:00.110 --> 00:10:00.120 align:start position:0% hooked into these networks the better 00:10:00.120 --> 00:10:01.490 align:start position:0% hooked into these networks the better they<00:10:00.360> will<00:10:00.540> work 00:10:01.490 --> 00:10:01.500 align:start position:0% they will work 00:10:01.500 --> 00:10:04.250 align:start position:0% they will work and<00:10:02.160> part<00:10:02.880> of<00:10:03.060> that<00:10:03.240> is<00:10:03.480> that<00:10:03.720> you<00:10:03.899> don't<00:10:04.019> have 00:10:04.250 --> 00:10:04.260 align:start position:0% and part of that is that you don't have 00:10:04.260 --> 00:10:07.310 align:start position:0% and part of that is that you don't have to<00:10:04.440> sync<00:10:04.800> to<00:10:04.980> the<00:10:05.160> entire<00:10:05.399> blockchain 00:10:07.310 --> 00:10:07.320 align:start position:0% to sync to the entire blockchain 00:10:07.320 --> 00:10:08.930 align:start position:0% to sync to the entire blockchain because<00:10:07.560> that<00:10:07.800> takes<00:10:08.040> a<00:10:08.279> long<00:10:08.339> time<00:10:08.580> and 00:10:08.930 --> 00:10:08.940 align:start position:0% because that takes a long time and 00:10:08.940 --> 00:10:11.389 align:start position:0% because that takes a long time and doesn't<00:10:09.180> really<00:10:10.019> make<00:10:10.260> sense<00:10:10.500> for<00:10:10.920> a<00:10:11.040> small 00:10:11.389 --> 00:10:11.399 align:start position:0% doesn't really make sense for a small 00:10:11.399 --> 00:10:13.550 align:start position:0% doesn't really make sense for a small app<00:10:11.640> or<00:10:11.880> a<00:10:12.060> small<00:10:12.180> device<00:10:12.420> to<00:10:12.779> want<00:10:13.019> to<00:10:13.200> do<00:10:13.320> that 00:10:13.550 --> 00:10:13.560 align:start position:0% app or a small device to want to do that 00:10:13.560 --> 00:10:16.430 align:start position:0% app or a small device to want to do that takes<00:10:14.220> a<00:10:14.339> long<00:10:14.459> time<00:10:14.700> it's<00:10:15.000> very<00:10:15.240> heavy 00:10:16.430 --> 00:10:16.440 align:start position:0% takes a long time it's very heavy 00:10:16.440 --> 00:10:18.350 align:start position:0% takes a long time it's very heavy and<00:10:16.800> doesn't<00:10:16.980> really<00:10:17.279> get<00:10:17.519> you<00:10:17.760> where<00:10:18.180> you 00:10:18.350 --> 00:10:18.360 align:start position:0% and doesn't really get you where you 00:10:18.360 --> 00:10:20.269 align:start position:0% and doesn't really get you where you wanted<00:10:18.480> to<00:10:18.779> go 00:10:20.269 --> 00:10:20.279 align:start position:0% wanted to go 00:10:20.279 --> 00:10:21.949 align:start position:0% wanted to go so<00:10:20.640> with<00:10:20.760> the<00:10:20.880> portal<00:10:21.180> Network<00:10:21.300> you<00:10:21.839> could 00:10:21.949 --> 00:10:21.959 align:start position:0% so with the portal Network you could 00:10:21.959 --> 00:10:23.570 align:start position:0% so with the portal Network you could just<00:10:22.080> Reach<00:10:22.440> Out<00:10:22.500> get<00:10:22.800> the<00:10:22.980> tip<00:10:23.100> of<00:10:23.279> the<00:10:23.399> chain 00:10:23.570 --> 00:10:23.580 align:start position:0% just Reach Out get the tip of the chain 00:10:23.580 --> 00:10:26.090 align:start position:0% just Reach Out get the tip of the chain get<00:10:24.180> your<00:10:24.899> account<00:10:25.019> balanced<00:10:25.620> and<00:10:25.740> all<00:10:25.920> these 00:10:26.090 --> 00:10:26.100 align:start position:0% get your account balanced and all these 00:10:26.100 --> 00:10:28.730 align:start position:0% get your account balanced and all these things<00:10:26.220> and<00:10:26.640> be<00:10:26.820> immediately 00:10:28.730 --> 00:10:28.740 align:start position:0% things and be immediately 00:10:28.740 --> 00:10:33.410 align:start position:0% things and be immediately immediately<00:10:29.519> serve<00:10:30.000> your<00:10:30.180> purpose 00:10:33.410 --> 00:10:33.420 align:start position:0% 00:10:33.420 --> 00:10:35.030 align:start position:0% kind<00:10:33.839> of<00:10:33.959> explaining<00:10:34.320> the<00:10:34.500> same<00:10:34.680> thing<00:10:34.800> with 00:10:35.030 --> 00:10:35.040 align:start position:0% kind of explaining the same thing with 00:10:35.040 --> 00:10:37.009 align:start position:0% kind of explaining the same thing with interior<00:10:35.700> everyone's<00:10:36.180> reaching<00:10:36.540> out<00:10:36.660> to<00:10:36.839> the 00:10:37.009 --> 00:10:37.019 align:start position:0% interior everyone's reaching out to the 00:10:37.019 --> 00:10:39.650 align:start position:0% interior everyone's reaching out to the same<00:10:37.200> thing<00:10:37.500> with<00:10:38.160> the<00:10:38.399> Les<00:10:38.760> you<00:10:39.180> get<00:10:39.360> this 00:10:39.650 --> 00:10:39.660 align:start position:0% same thing with the Les you get this 00:10:39.660 --> 00:10:40.550 align:start position:0% same thing with the Les you get this kind<00:10:39.839> of 00:10:40.550 --> 00:10:40.560 align:start position:0% kind of 00:10:40.560 --> 00:10:43.790 align:start position:0% kind of pile<00:10:41.100> up<00:10:41.339> where<00:10:41.580> the<00:10:41.820> more<00:10:42.140> nodes<00:10:43.140> involved<00:10:43.680> in 00:10:43.790 --> 00:10:43.800 align:start position:0% pile up where the more nodes involved in 00:10:43.800 --> 00:10:46.009 align:start position:0% pile up where the more nodes involved in the<00:10:43.980> system<00:10:44.160> the<00:10:44.519> more<00:10:44.640> clunky<00:10:45.060> it<00:10:45.240> works<00:10:45.660> and 00:10:46.009 --> 00:10:46.019 align:start position:0% the system the more clunky it works and 00:10:46.019 --> 00:10:47.870 align:start position:0% the system the more clunky it works and the<00:10:46.140> harder<00:10:46.440> it<00:10:46.560> is<00:10:46.740> too 00:10:47.870 --> 00:10:47.880 align:start position:0% the harder it is too 00:10:47.880 --> 00:10:49.790 align:start position:0% the harder it is too actually<00:10:48.420> return<00:10:48.720> anything<00:10:49.079> but<00:10:49.620> a 00:10:49.790 --> 00:10:49.800 align:start position:0% actually return anything but a 00:10:49.800 --> 00:10:53.090 align:start position:0% actually return anything but a distributed<00:10:50.339> system<00:10:50.959> every<00:10:51.959> everybody's<00:10:52.800> got 00:10:53.090 --> 00:10:53.100 align:start position:0% distributed system every everybody's got 00:10:53.100 --> 00:10:54.889 align:start position:0% distributed system every everybody's got a<00:10:53.399> piece<00:10:53.640> a<00:10:53.820> little<00:10:53.940> piece<00:10:54.300> of<00:10:54.360> responsibility 00:10:54.889 --> 00:10:54.899 align:start position:0% a piece a little piece of responsibility 00:10:54.899 --> 00:10:57.230 align:start position:0% a piece a little piece of responsibility of<00:10:55.500> the<00:10:55.620> network<00:10:55.800> and<00:10:56.459> they 00:10:57.230 --> 00:10:57.240 align:start position:0% of the network and they 00:10:57.240 --> 00:10:59.509 align:start position:0% of the network and they hold<00:10:57.839> as<00:10:58.079> much<00:10:58.320> data<00:10:58.680> as<00:10:58.800> they're<00:10:58.980> willing<00:10:59.339> to 00:10:59.509 --> 00:10:59.519 align:start position:0% hold as much data as they're willing to 00:10:59.519 --> 00:11:01.850 align:start position:0% hold as much data as they're willing to as<00:11:00.240> they<00:11:00.720> serve 00:11:01.850 --> 00:11:01.860 align:start position:0% as they serve 00:11:01.860 --> 00:11:04.970 align:start position:0% as they serve much<00:11:02.279> as<00:11:02.579> they<00:11:02.820> can<00:11:03.060> or<00:11:03.300> want<00:11:03.540> to 00:11:04.970 --> 00:11:04.980 align:start position:0% much as they can or want to 00:11:04.980 --> 00:11:08.269 align:start position:0% much as they can or want to so<00:11:05.399> for<00:11:05.640> a<00:11:05.820> practical<00:11:06.060> example<00:11:06.540> in<00:11:07.019> a 00:11:08.269 --> 00:11:08.279 align:start position:0% so for a practical example in a 00:11:08.279 --> 00:11:11.150 align:start position:0% so for a practical example in a you<00:11:08.760> know<00:11:08.880> just<00:11:09.240> a<00:11:09.420> Json<00:11:10.019> RPC<00:11:10.560> call<00:11:10.800> for<00:11:11.040> each 00:11:11.150 --> 00:11:11.160 align:start position:0% you know just a Json RPC call for each 00:11:11.160 --> 00:11:13.730 align:start position:0% you know just a Json RPC call for each get<00:11:11.459> balance 00:11:13.730 --> 00:11:13.740 align:start position:0% get balance 00:11:13.740 --> 00:11:15.650 align:start position:0% get balance right<00:11:14.279> now<00:11:14.399> if<00:11:14.579> you're<00:11:14.700> running<00:11:14.880> a<00:11:15.180> node<00:11:15.420> you 00:11:15.650 --> 00:11:15.660 align:start position:0% right now if you're running a node you 00:11:15.660 --> 00:11:17.449 align:start position:0% right now if you're running a node you have<00:11:15.779> to<00:11:15.899> maintain<00:11:16.260> all<00:11:16.560> of<00:11:16.680> these<00:11:16.860> databases 00:11:17.449 --> 00:11:17.459 align:start position:0% have to maintain all of these databases 00:11:17.459 --> 00:11:19.790 align:start position:0% have to maintain all of these databases where<00:11:17.880> you<00:11:18.060> can<00:11:18.360> look<00:11:18.540> up<00:11:18.720> the<00:11:19.019> the<00:11:19.260> canonical 00:11:19.790 --> 00:11:19.800 align:start position:0% where you can look up the the canonical 00:11:19.800 --> 00:11:21.650 align:start position:0% where you can look up the the canonical index<00:11:20.220> you<00:11:20.459> can<00:11:20.579> look<00:11:20.700> up<00:11:20.880> storage<00:11:21.180> you<00:11:21.540> can 00:11:21.650 --> 00:11:21.660 align:start position:0% index you can look up storage you can 00:11:21.660 --> 00:11:24.370 align:start position:0% index you can look up storage you can look<00:11:21.779> up<00:11:21.899> State<00:11:22.200> and<00:11:22.800> return<00:11:23.339> these<00:11:23.820> things 00:11:24.370 --> 00:11:24.380 align:start position:0% look up State and return these things 00:11:24.380 --> 00:11:26.569 align:start position:0% look up State and return these things calculate<00:11:25.380> them<00:11:25.560> and<00:11:25.860> then<00:11:25.980> return<00:11:26.160> the 00:11:26.569 --> 00:11:26.579 align:start position:0% calculate them and then return the 00:11:26.579 --> 00:11:28.190 align:start position:0% calculate them and then return the balance 00:11:28.190 --> 00:11:28.200 align:start position:0% balance 00:11:28.200 --> 00:11:29.750 align:start position:0% balance portal<00:11:28.680> network<00:11:28.800> is<00:11:28.980> going<00:11:29.160> to<00:11:29.220> work<00:11:29.339> exactly 00:11:29.750 --> 00:11:29.760 align:start position:0% portal network is going to work exactly 00:11:29.760 --> 00:11:31.670 align:start position:0% portal network is going to work exactly the<00:11:30.000> same<00:11:30.180> but<00:11:30.600> instead<00:11:30.959> of<00:11:31.079> looking<00:11:31.380> into 00:11:31.670 --> 00:11:31.680 align:start position:0% the same but instead of looking into 00:11:31.680 --> 00:11:34.550 align:start position:0% the same but instead of looking into your<00:11:31.980> own<00:11:32.160> databases<00:11:32.880> your<00:11:33.240> own<00:11:33.480> huge<00:11:34.200> piles 00:11:34.550 --> 00:11:34.560 align:start position:0% your own databases your own huge piles 00:11:34.560 --> 00:11:37.730 align:start position:0% your own databases your own huge piles of<00:11:34.980> state<00:11:35.459> and<00:11:35.820> history<00:11:36.260> you<00:11:37.260> can<00:11:37.380> reach<00:11:37.620> out 00:11:37.730 --> 00:11:37.740 align:start position:0% of state and history you can reach out 00:11:37.740 --> 00:11:40.490 align:start position:0% of state and history you can reach out to<00:11:37.860> these<00:11:38.100> light<00:11:38.220> networks<00:11:38.880> you<00:11:39.240> can 00:11:40.490 --> 00:11:40.500 align:start position:0% to these light networks you can 00:11:40.500 --> 00:11:42.170 align:start position:0% to these light networks you can to<00:11:40.860> see<00:11:40.980> if<00:11:41.100> your<00:11:41.279> balance<00:11:41.579> receive<00:11:42.000> the 00:11:42.170 --> 00:11:42.180 align:start position:0% to see if your balance receive the 00:11:42.180 --> 00:11:45.170 align:start position:0% to see if your balance receive the history<00:11:42.360> receive<00:11:42.899> state<00:11:43.200> and<00:11:43.620> send<00:11:43.920> it<00:11:44.180> and 00:11:45.170 --> 00:11:45.180 align:start position:0% history receive state and send it and 00:11:45.180 --> 00:11:47.210 align:start position:0% history receive state and send it and return<00:11:45.300> it<00:11:45.540> in<00:11:45.660> the<00:11:45.779> exact<00:11:45.959> same<00:11:46.140> way<00:11:46.320> so<00:11:46.860> for 00:11:47.210 --> 00:11:47.220 align:start position:0% return it in the exact same way so for 00:11:47.220 --> 00:11:50.930 align:start position:0% return it in the exact same way so for for<00:11:48.180> the<00:11:48.480> user<00:11:48.839> using<00:11:49.260> a<00:11:49.380> Json<00:11:49.680> RPC<00:11:50.279> call<00:11:50.519> it 00:11:50.930 --> 00:11:50.940 align:start position:0% for the user using a Json RPC call it 00:11:50.940 --> 00:11:53.210 align:start position:0% for the user using a Json RPC call it feels<00:11:51.300> exactly<00:11:51.660> the<00:11:51.839> same<00:11:52.500> but<00:11:52.980> it<00:11:53.160> is 00:11:53.210 --> 00:11:53.220 align:start position:0% feels exactly the same but it is 00:11:53.220 --> 00:11:56.030 align:start position:0% feels exactly the same but it is possible<00:11:54.079> with<00:11:55.079> very<00:11:55.320> very<00:11:55.560> limited 00:11:56.030 --> 00:11:56.040 align:start position:0% possible with very very limited 00:11:56.040 --> 00:11:58.430 align:start position:0% possible with very very limited resources<00:11:56.640> and 00:11:58.430 --> 00:11:58.440 align:start position:0% resources and 00:11:58.440 --> 00:12:00.530 align:start position:0% resources and uh 00:12:00.530 --> 00:12:00.540 align:start position:0% uh 00:12:00.540 --> 00:12:02.630 align:start position:0% uh ours<00:12:01.019> is<00:12:01.079> called<00:12:01.260> ultralight<00:12:01.800> there's<00:12:02.399> two 00:12:02.630 --> 00:12:02.640 align:start position:0% ours is called ultralight there's two 00:12:02.640 --> 00:12:04.610 align:start position:0% ours is called ultralight there's two other<00:12:02.820> teams<00:12:03.240> one's<00:12:03.720> called<00:12:03.899> Trin<00:12:04.380> they're 00:12:04.610 --> 00:12:04.620 align:start position:0% other teams one's called Trin they're 00:12:04.620 --> 00:12:06.670 align:start position:0% other teams one's called Trin they're working<00:12:04.860> in 00:12:06.670 --> 00:12:06.680 align:start position:0% working in 00:12:06.680 --> 00:12:10.069 align:start position:0% working in their<00:12:07.680> rust<00:12:08.040> and<00:12:08.640> a<00:12:09.000> client<00:12:09.420> called<00:12:09.600> fluffy 00:12:10.069 --> 00:12:10.079 align:start position:0% their rust and a client called fluffy 00:12:10.079 --> 00:12:12.410 align:start position:0% their rust and a client called fluffy that<00:12:10.320> is<00:12:10.440> working<00:12:10.560> in<00:12:10.920> nem 00:12:12.410 --> 00:12:12.420 align:start position:0% that is working in nem 00:12:12.420 --> 00:12:14.269 align:start position:0% that is working in nem um<00:12:12.540> so<00:12:12.720> the<00:12:12.899> cool<00:12:13.200> thing<00:12:13.320> about<00:12:13.500> ours<00:12:13.980> is<00:12:14.100> that 00:12:14.269 --> 00:12:14.279 align:start position:0% um so the cool thing about ours is that 00:12:14.279 --> 00:12:16.670 align:start position:0% um so the cool thing about ours is that we<00:12:14.519> can<00:12:14.640> we<00:12:15.120> have<00:12:15.180> a<00:12:15.300> CLI<00:12:15.779> client<00:12:16.079> but<00:12:16.260> we<00:12:16.440> also 00:12:16.670 --> 00:12:16.680 align:start position:0% we can we have a CLI client but we also 00:12:16.680 --> 00:12:18.889 align:start position:0% we can we have a CLI client but we also have<00:12:16.740> it<00:12:16.860> working<00:12:17.040> in<00:12:17.339> a<00:12:17.459> browser<00:12:17.940> so<00:12:18.420> we<00:12:18.660> can 00:12:18.889 --> 00:12:18.899 align:start position:0% have it working in a browser so we can 00:12:18.899 --> 00:12:22.370 align:start position:0% have it working in a browser so we can open<00:12:19.740> up<00:12:19.920> a<00:12:20.100> browser<00:12:20.519> page<00:12:20.880> too 00:12:22.370 --> 00:12:22.380 align:start position:0% open up a browser page too 00:12:22.380 --> 00:12:25.370 align:start position:0% open up a browser page too and<00:12:22.860> we<00:12:23.160> built<00:12:23.399> like<00:12:23.519> a<00:12:23.760> stupid<00:12:23.940> uh<00:12:24.839> just<00:12:25.200> a 00:12:25.370 --> 00:12:25.380 align:start position:0% and we built like a stupid uh just a 00:12:25.380 --> 00:12:26.990 align:start position:0% and we built like a stupid uh just a small<00:12:25.560> block<00:12:25.800> Explorer<00:12:26.279> but<00:12:26.519> you<00:12:26.640> open<00:12:26.760> up 00:12:26.990 --> 00:12:27.000 align:start position:0% small block Explorer but you open up 00:12:27.000 --> 00:12:28.850 align:start position:0% small block Explorer but you open up your<00:12:27.180> browser<00:12:27.540> page<00:12:27.839> to<00:12:28.200> this<00:12:28.380> thing<00:12:28.500> and<00:12:28.740> the 00:12:28.850 --> 00:12:28.860 align:start position:0% your browser page to this thing and the 00:12:28.860 --> 00:12:32.630 align:start position:0% your browser page to this thing and the browser<00:12:29.279> itself<00:12:30.000> becomes<00:12:30.600> a<00:12:30.779> portal<00:12:31.079> client 00:12:32.630 --> 00:12:32.640 align:start position:0% browser itself becomes a portal client 00:12:32.640 --> 00:12:36.050 align:start position:0% browser itself becomes a portal client using<00:12:33.300> the<00:12:33.540> same<00:12:33.720> kind<00:12:34.079> of<00:12:34.200> uh<00:12:34.760> same<00:12:35.760> kind<00:12:36.000> of 00:12:36.050 --> 00:12:36.060 align:start position:0% using the same kind of uh same kind of 00:12:36.060 --> 00:12:38.569 align:start position:0% using the same kind of uh same kind of memory<00:12:36.480> and<00:12:36.959> and<00:12:37.200> storage<00:12:37.560> as<00:12:37.920> anything<00:12:38.100> else 00:12:38.569 --> 00:12:38.579 align:start position:0% memory and and storage as anything else 00:12:38.579 --> 00:12:40.970 align:start position:0% memory and and storage as anything else and 00:12:40.970 --> 00:12:40.980 align:start position:0% and 00:12:40.980 --> 00:12:43.550 align:start position:0% and you<00:12:41.040> know<00:12:41.399> can<00:12:41.579> both<00:12:41.760> can<00:12:42.060> both<00:12:42.300> look<00:12:42.480> up<00:12:42.660> uh 00:12:43.550 --> 00:12:43.560 align:start position:0% you know can both can both look up uh 00:12:43.560 --> 00:12:46.009 align:start position:0% you know can both can both look up uh look<00:12:44.160> up<00:12:44.339> and<00:12:44.579> serve 00:12:46.009 --> 00:12:46.019 align:start position:0% look up and serve 00:12:46.019 --> 00:12:48.230 align:start position:0% look up and serve yeah<00:12:46.079> what<00:12:46.860> else<00:12:47.040> am<00:12:47.220> I<00:12:47.339> saying 00:12:48.230 --> 00:12:48.240 align:start position:0% yeah what else am I saying 00:12:48.240 --> 00:12:50.810 align:start position:0% yeah what else am I saying yeah<00:12:48.899> essentially<00:12:49.320> your<00:12:49.680> your<00:12:49.920> app<00:12:50.220> can<00:12:50.519> be<00:12:50.639> a 00:12:50.810 --> 00:12:50.820 align:start position:0% yeah essentially your your app can be a 00:12:50.820 --> 00:12:52.970 align:start position:0% yeah essentially your your app can be a portal<00:12:51.240> client<00:12:51.480> if<00:12:51.959> you<00:12:52.200> if<00:12:52.380> you<00:12:52.620> were<00:12:52.680> to<00:12:52.800> bake 00:12:52.970 --> 00:12:52.980 align:start position:0% portal client if you if you were to bake 00:12:52.980 --> 00:12:55.569 align:start position:0% portal client if you if you were to bake this<00:12:53.220> into 00:12:55.569 --> 00:12:55.579 align:start position:0% this into 00:12:55.579 --> 00:12:57.889 align:start position:0% this into bake<00:12:56.579> it<00:12:56.700> into<00:12:56.820> your<00:12:57.060> app<00:12:57.180> it<00:12:57.420> can<00:12:57.600> basically 00:12:57.889 --> 00:12:57.899 align:start position:0% bake it into your app it can basically 00:12:57.899 --> 00:13:00.110 align:start position:0% bake it into your app it can basically just<00:12:58.079> be<00:12:58.200> running<00:12:58.440> in<00:12:58.800> the<00:12:58.920> backgrounds 00:13:00.110 --> 00:13:00.120 align:start position:0% just be running in the backgrounds 00:13:00.120 --> 00:13:01.670 align:start position:0% just be running in the backgrounds you<00:13:00.660> don't<00:13:00.720> even<00:13:00.899> really<00:13:01.200> have<00:13:01.380> to<00:13:01.500> think 00:13:01.670 --> 00:13:01.680 align:start position:0% you don't even really have to think 00:13:01.680 --> 00:13:04.069 align:start position:0% you don't even really have to think about<00:13:01.860> it<00:13:02.160> but<00:13:02.579> it's<00:13:02.880> Distributing<00:13:03.540> the<00:13:03.839> data 00:13:04.069 --> 00:13:04.079 align:start position:0% about it but it's Distributing the data 00:13:04.079 --> 00:13:06.290 align:start position:0% about it but it's Distributing the data among<00:13:04.500> a<00:13:04.680> large<00:13:04.800> large<00:13:05.100> network<00:13:05.399> of<00:13:05.820> pockets 00:13:06.290 --> 00:13:06.300 align:start position:0% among a large large network of pockets 00:13:06.300 --> 00:13:08.810 align:start position:0% among a large large network of pockets and<00:13:06.600> phones<00:13:06.959> and<00:13:07.139> laptops 00:13:08.810 --> 00:13:08.820 align:start position:0% and phones and laptops 00:13:08.820 --> 00:13:10.009 align:start position:0% and phones and laptops um 00:13:10.009 --> 00:13:10.019 align:start position:0% um 00:13:10.019 --> 00:13:12.410 align:start position:0% um essentially<00:13:10.620> taking<00:13:10.800> a<00:13:11.100> lot<00:13:11.220> of<00:13:11.399> the<00:13:11.639> load<00:13:12.060> off 00:13:12.410 --> 00:13:12.420 align:start position:0% essentially taking a lot of the load off 00:13:12.420 --> 00:13:15.410 align:start position:0% essentially taking a lot of the load off of<00:13:12.720> Full<00:13:13.139> clients<00:13:13.680> and<00:13:13.920> and<00:13:14.220> making<00:13:14.639> a<00:13:15.240> lot<00:13:15.300> of 00:13:15.410 --> 00:13:15.420 align:start position:0% of Full clients and and making a lot of 00:13:15.420 --> 00:13:17.690 align:start position:0% of Full clients and and making a lot of this<00:13:15.540> data<00:13:15.899> available<00:13:16.079> in<00:13:17.040> a<00:13:17.279> much<00:13:17.519> more 00:13:17.690 --> 00:13:17.700 align:start position:0% this data available in a much more 00:13:17.700 --> 00:13:19.910 align:start position:0% this data available in a much more lightweight<00:13:18.060> way 00:13:19.910 --> 00:13:19.920 align:start position:0% lightweight way 00:13:19.920 --> 00:13:22.370 align:start position:0% lightweight way uh<00:13:20.700> we<00:13:21.120> have<00:13:21.300> been<00:13:21.480> building<00:13:21.779> the<00:13:22.139> history 00:13:22.370 --> 00:13:22.380 align:start position:0% uh we have been building the history 00:13:22.380 --> 00:13:24.290 align:start position:0% uh we have been building the history Network<00:13:22.680> for<00:13:23.100> the<00:13:23.220> last<00:13:23.339> year<00:13:23.519> or<00:13:23.639> so<00:13:23.820> and<00:13:24.060> that 00:13:24.290 --> 00:13:24.300 align:start position:0% Network for the last year or so and that 00:13:24.300 --> 00:13:28.190 align:start position:0% Network for the last year or so and that is<00:13:24.480> imminently<00:13:25.260> operational 00:13:28.190 --> 00:13:28.200 align:start position:0% is imminently operational 00:13:28.200 --> 00:13:29.750 align:start position:0% is imminently operational and<00:13:28.680> then<00:13:28.800> the<00:13:28.980> idea<00:13:29.160> is<00:13:29.279> that<00:13:29.459> the<00:13:29.639> other 00:13:29.750 --> 00:13:29.760 align:start position:0% and then the idea is that the other 00:13:29.760 --> 00:13:31.850 align:start position:0% and then the idea is that the other networks<00:13:30.360> can<00:13:30.660> just<00:13:30.839> build<00:13:31.019> upon<00:13:31.440> that<00:13:31.620> but 00:13:31.850 --> 00:13:31.860 align:start position:0% networks can just build upon that but 00:13:31.860 --> 00:13:34.430 align:start position:0% networks can just build upon that but they<00:13:32.100> will<00:13:32.279> be<00:13:32.779> independent<00:13:33.779> networks<00:13:34.200> so<00:13:34.260> as 00:13:34.430 --> 00:13:34.440 align:start position:0% they will be independent networks so as 00:13:34.440 --> 00:13:36.350 align:start position:0% they will be independent networks so as a<00:13:34.620> portal<00:13:34.860> client<00:13:35.160> you<00:13:35.579> can 00:13:36.350 --> 00:13:36.360 align:start position:0% a portal client you can 00:13:36.360 --> 00:13:40.009 align:start position:0% a portal client you can participate<00:13:37.200> in<00:13:37.380> one<00:13:37.740> or<00:13:38.160> all<00:13:38.459> of<00:13:38.579> them<00:13:39.019> you 00:13:40.009 --> 00:13:40.019 align:start position:0% participate in one or all of them you 00:13:40.019 --> 00:13:41.629 align:start position:0% participate in one or all of them you can 00:13:41.629 --> 00:13:41.639 align:start position:0% can 00:13:41.639 --> 00:13:43.790 align:start position:0% can be<00:13:42.000> there<00:13:42.120> as<00:13:42.300> a<00:13:42.480> freeloader<00:13:43.079> and<00:13:43.440> not 00:13:43.790 --> 00:13:43.800 align:start position:0% be there as a freeloader and not 00:13:43.800 --> 00:13:45.230 align:start position:0% be there as a freeloader and not contribute<00:13:44.339> anything<00:13:44.579> and<00:13:45.000> it<00:13:45.120> really 00:13:45.230 --> 00:13:45.240 align:start position:0% contribute anything and it really 00:13:45.240 --> 00:13:46.970 align:start position:0% contribute anything and it really doesn't<00:13:45.480> take<00:13:45.720> much<00:13:45.959> away<00:13:46.200> from<00:13:46.440> it<00:13:46.620> if<00:13:46.860> you 00:13:46.970 --> 00:13:46.980 align:start position:0% doesn't take much away from it if you 00:13:46.980 --> 00:13:48.290 align:start position:0% doesn't take much away from it if you think<00:13:47.160> about 00:13:48.290 --> 00:13:48.300 align:start position:0% think about 00:13:48.300 --> 00:13:51.470 align:start position:0% think about you<00:13:48.720> know<00:13:48.779> BitTorrent<00:13:49.500> most<00:13:49.740> people<00:13:50.040> are 00:13:51.470 --> 00:13:51.480 align:start position:0% you know BitTorrent most people are 00:13:51.480 --> 00:13:53.269 align:start position:0% you know BitTorrent most people are most<00:13:51.839> people<00:13:52.079> don't<00:13:52.380> really<00:13:52.620> go<00:13:52.860> into<00:13:52.980> their 00:13:53.269 --> 00:13:53.279 align:start position:0% most people don't really go into their 00:13:53.279 --> 00:13:55.129 align:start position:0% most people don't really go into their torrent<00:13:53.700> apps<00:13:54.060> and<00:13:54.420> change<00:13:54.660> a<00:13:54.959> lot<00:13:55.019> of 00:13:55.129 --> 00:13:55.139 align:start position:0% torrent apps and change a lot of 00:13:55.139 --> 00:13:57.470 align:start position:0% torrent apps and change a lot of configurations<00:13:55.740> to<00:13:56.399> be<00:13:56.760> selfish<00:13:57.120> about<00:13:57.300> it 00:13:57.470 --> 00:13:57.480 align:start position:0% configurations to be selfish about it 00:13:57.480 --> 00:13:59.269 align:start position:0% configurations to be selfish about it most<00:13:57.720> people<00:13:57.899> just<00:13:58.320> download<00:13:58.500> the<00:13:58.860> thing<00:13:59.040> and 00:13:59.269 --> 00:13:59.279 align:start position:0% most people just download the thing and 00:13:59.279 --> 00:14:03.590 align:start position:0% most people just download the thing and use<00:13:59.459> it<00:13:59.639> as<00:14:00.000> it<00:14:00.180> comes 00:14:03.590 --> 00:14:03.600 align:start position:0% 00:14:03.600 --> 00:14:05.269 align:start position:0% essentially<00:14:04.320> you<00:14:04.560> don't<00:14:04.740> even<00:14:04.920> really<00:14:05.160> have 00:14:05.269 --> 00:14:05.279 align:start position:0% essentially you don't even really have 00:14:05.279 --> 00:14:07.009 align:start position:0% essentially you don't even really have to<00:14:05.459> know<00:14:05.579> that<00:14:05.820> it's<00:14:06.000> happening<00:14:06.300> but<00:14:06.660> you<00:14:06.899> are 00:14:07.009 --> 00:14:07.019 align:start position:0% to know that it's happening but you are 00:14:07.019 --> 00:14:11.210 align:start position:0% to know that it's happening but you are serving<00:14:07.500> the<00:14:07.860> entire<00:14:08.459> network<00:14:08.700> yourself 00:14:11.210 --> 00:14:11.220 align:start position:0% 00:14:11.220 --> 00:14:14.449 align:start position:0% so<00:14:11.700> that's<00:14:11.940> yeah<00:14:12.540> that's<00:14:13.079> a<00:14:13.380> side<00:14:13.680> project<00:14:13.980> but 00:14:14.449 --> 00:14:14.459 align:start position:0% so that's yeah that's a side project but 00:14:14.459 --> 00:14:16.730 align:start position:0% so that's yeah that's a side project but it's<00:14:14.760> very<00:14:15.060> exciting<00:14:15.480> and<00:14:15.959> is<00:14:16.200> definitely 00:14:16.730 --> 00:14:16.740 align:start position:0% it's very exciting and is definitely 00:14:16.740 --> 00:14:18.829 align:start position:0% it's very exciting and is definitely part<00:14:16.980> of<00:14:17.100> the<00:14:17.220> future<00:14:17.459> of<00:14:17.880> how 00:14:18.829 --> 00:14:18.839 align:start position:0% part of the future of how 00:14:18.839 --> 00:14:37.150 align:start position:0% part of the future of how these<00:14:19.260> things<00:14:19.380> will<00:14:19.560> work<00:14:19.740> yes<00:14:19.980> sir 00:14:37.150 --> 00:14:37.160 align:start position:0% 00:14:37.160 --> 00:14:40.370 align:start position:0% so<00:14:38.160> it's<00:14:38.399> a<00:14:38.639> distributed<00:14:39.180> distributed<00:14:40.079> hash 00:14:40.370 --> 00:14:40.380 align:start position:0% so it's a distributed distributed hash 00:14:40.380 --> 00:14:43.490 align:start position:0% so it's a distributed distributed hash table<00:14:40.620> both<00:14:41.220> of<00:14:41.399> content<00:14:41.880> and<00:14:42.360> user<00:14:43.019> addresses 00:14:43.490 --> 00:14:43.500 align:start position:0% table both of content and user addresses 00:14:43.500 --> 00:14:45.949 align:start position:0% table both of content and user addresses so<00:14:44.000> for<00:14:45.000> the<00:14:45.120> most<00:14:45.180> part<00:14:45.420> you're<00:14:45.660> going<00:14:45.779> to<00:14:45.899> be 00:14:45.949 --> 00:14:45.959 align:start position:0% so for the most part you're going to be 00:14:45.959 --> 00:14:47.810 align:start position:0% so for the most part you're going to be randomly<00:14:46.440> assigned<00:14:46.920> and<00:14:47.040> addressed<00:14:47.519> in<00:14:47.639> that 00:14:47.810 --> 00:14:47.820 align:start position:0% randomly assigned and addressed in that 00:14:47.820 --> 00:14:49.850 align:start position:0% randomly assigned and addressed in that in<00:14:48.060> that<00:14:48.240> sphere<00:14:48.480> and<00:14:48.779> you<00:14:48.959> can 00:14:49.850 --> 00:14:49.860 align:start position:0% in that sphere and you can 00:14:49.860 --> 00:14:52.910 align:start position:0% in that sphere and you can sort<00:14:50.399> of<00:14:50.579> configure<00:14:51.000> the<00:14:51.240> radius<00:14:51.720> of<00:14:52.320> of<00:14:52.560> data 00:14:52.910 --> 00:14:52.920 align:start position:0% sort of configure the radius of of data 00:14:52.920 --> 00:14:55.670 align:start position:0% sort of configure the radius of of data you're<00:14:53.040> willing<00:14:53.399> to<00:14:53.639> be<00:14:53.820> responsible<00:14:54.300> for 00:14:55.670 --> 00:14:55.680 align:start position:0% you're willing to be responsible for 00:14:55.680 --> 00:15:00.110 align:start position:0% you're willing to be responsible for [Music] 00:15:00.110 --> 00:15:00.120 align:start position:0% 00:15:00.120 --> 00:15:01.910 align:start position:0% so<00:15:00.420> you<00:15:00.660> you<00:15:00.959> would<00:15:01.199> be<00:15:01.380> up<00:15:01.500> here<00:15:01.620> on<00:15:01.800> the 00:15:01.910 --> 00:15:01.920 align:start position:0% so you you would be up here on the 00:15:01.920 --> 00:15:04.370 align:start position:0% so you you would be up here on the network<00:15:02.100> you<00:15:02.940> know<00:15:03.000> if<00:15:03.360> you<00:15:03.600> constrained 00:15:04.370 --> 00:15:04.380 align:start position:0% network you know if you constrained 00:15:04.380 --> 00:15:06.710 align:start position:0% network you know if you constrained yourself<00:15:04.500> to<00:15:04.800> only<00:15:04.980> holding<00:15:05.459> like<00:15:05.760> a<00:15:06.000> tiny<00:15:06.360> bit 00:15:06.710 --> 00:15:06.720 align:start position:0% yourself to only holding like a tiny bit 00:15:06.720 --> 00:15:08.210 align:start position:0% yourself to only holding like a tiny bit of<00:15:06.899> data<00:15:07.199> then<00:15:07.380> you're<00:15:07.620> not<00:15:07.740> going<00:15:07.920> to<00:15:08.040> be 00:15:08.210 --> 00:15:08.220 align:start position:0% of data then you're not going to be 00:15:08.220 --> 00:15:10.430 align:start position:0% of data then you're not going to be asked<00:15:08.760> for<00:15:08.880> it<00:15:09.000> very<00:15:09.300> often 00:15:10.430 --> 00:15:10.440 align:start position:0% asked for it very often 00:15:10.440 --> 00:15:12.590 align:start position:0% asked for it very often and<00:15:10.920> there<00:15:11.279> are<00:15:11.399> certainly<00:15:11.639> malicious<00:15:12.120> ways 00:15:12.590 --> 00:15:12.600 align:start position:0% and there are certainly malicious ways 00:15:12.600 --> 00:15:14.810 align:start position:0% and there are certainly malicious ways to 00:15:14.810 --> 00:15:14.820 align:start position:0% to 00:15:14.820 --> 00:15:16.370 align:start position:0% to just you<00:15:15.240> know<00:15:15.300> put<00:15:15.540> a<00:15:15.720> bunch<00:15:15.839> of<00:15:15.959> nodes<00:15:16.199> up 00:15:16.370 --> 00:15:16.380 align:start position:0% just you know put a bunch of nodes up 00:15:16.380 --> 00:15:21.590 align:start position:0% just you know put a bunch of nodes up that<00:15:16.620> aren't<00:15:16.800> doing<00:15:16.980> anything<00:15:17.279> but<00:15:18.420> um 00:15:21.590 --> 00:15:21.600 align:start position:0% 00:15:21.600 --> 00:15:24.290 align:start position:0% I<00:15:21.959> don't<00:15:22.079> know<00:15:22.199> the<00:15:22.740> it<00:15:23.639> just<00:15:23.820> kind<00:15:24.000> of<00:15:24.060> means 00:15:24.290 --> 00:15:24.300 align:start position:0% I don't know the it just kind of means 00:15:24.300 --> 00:15:25.490 align:start position:0% I don't know the it just kind of means that<00:15:24.480> we've<00:15:24.660> built<00:15:24.959> something<00:15:25.139> worth 00:15:25.490 --> 00:15:25.500 align:start position:0% that we've built something worth 00:15:25.500 --> 00:15:27.470 align:start position:0% that we've built something worth attacking<00:15:26.040> first<00:15:26.339> of<00:15:26.519> all<00:15:26.639> and<00:15:26.940> that<00:15:27.180> there 00:15:27.470 --> 00:15:27.480 align:start position:0% attacking first of all and that there 00:15:27.480 --> 00:15:29.449 align:start position:0% attacking first of all and that there are<00:15:27.720> solutions<00:15:28.260> to<00:15:28.500> those<00:15:28.680> problems<00:15:29.100> that<00:15:29.339> can 00:15:29.449 --> 00:15:29.459 align:start position:0% are solutions to those problems that can 00:15:29.459 --> 00:15:31.670 align:start position:0% are solutions to those problems that can be<00:15:29.579> worked<00:15:29.940> out 00:15:31.670 --> 00:15:31.680 align:start position:0% be worked out 00:15:31.680 --> 00:15:35.210 align:start position:0% be worked out and<00:15:32.279> just<00:15:32.459> I<00:15:32.699> think<00:15:33.120> we're<00:15:33.300> counting<00:15:33.720> on<00:15:34.139> the 00:15:35.210 --> 00:15:35.220 align:start position:0% and just I think we're counting on the 00:15:35.220 --> 00:15:38.030 align:start position:0% and just I think we're counting on the General<00:15:35.760> laziness<00:15:36.600> of<00:15:36.839> users<00:15:37.260> that<00:15:37.740> are<00:15:37.920> going 00:15:38.030 --> 00:15:38.040 align:start position:0% General laziness of users that are going 00:15:38.040 --> 00:15:39.650 align:start position:0% General laziness of users that are going to<00:15:38.279> download<00:15:38.519> a<00:15:38.820> wallet<00:15:39.120> app<00:15:39.300> that<00:15:39.480> somebody 00:15:39.650 --> 00:15:39.660 align:start position:0% to download a wallet app that somebody 00:15:39.660 --> 00:15:42.829 align:start position:0% to download a wallet app that somebody made<00:15:40.019> and<00:15:40.500> not<00:15:40.880> necessarily<00:15:41.880> configure<00:15:42.480> it<00:15:42.660> to 00:15:42.829 --> 00:15:42.839 align:start position:0% made and not necessarily configure it to 00:15:42.839 --> 00:15:45.110 align:start position:0% made and not necessarily configure it to be<00:15:43.079> like<00:15:43.380> weirdly<00:15:43.860> malicious<00:15:44.339> there's<00:15:44.880> no 00:15:45.110 --> 00:15:45.120 align:start position:0% be like weirdly malicious there's no 00:15:45.120 --> 00:15:47.689 align:start position:0% be like weirdly malicious there's no incentives<00:15:45.660> here<00:15:45.959> it's<00:15:46.320> all<00:15:46.500> just 00:15:47.689 --> 00:15:47.699 align:start position:0% incentives here it's all just 00:15:47.699 --> 00:15:50.210 align:start position:0% incentives here it's all just it's<00:15:47.820> all<00:15:48.180> just<00:15:48.480> there<00:15:49.199> because<00:15:49.500> it<00:15:49.800> benefits 00:15:50.210 --> 00:15:50.220 align:start position:0% it's all just there because it benefits 00:15:50.220 --> 00:15:52.970 align:start position:0% it's all just there because it benefits users<00:15:50.639> and<00:15:51.300> by<00:15:51.600> benefiting<00:15:52.199> one<00:15:52.440> user<00:15:52.860> you 00:15:52.970 --> 00:15:52.980 align:start position:0% users and by benefiting one user you 00:15:52.980 --> 00:15:54.829 align:start position:0% users and by benefiting one user you benefit<00:15:53.160> all<00:15:53.519> users 00:15:54.829 --> 00:15:54.839 align:start position:0% benefit all users 00:15:54.839 --> 00:15:56.750 align:start position:0% benefit all users um<00:15:54.899> so<00:15:55.019> yes<00:15:55.260> there<00:15:55.620> are<00:15:55.740> ways<00:15:55.980> to<00:15:56.160> attack<00:15:56.399> it 00:15:56.750 --> 00:15:56.760 align:start position:0% um so yes there are ways to attack it 00:15:56.760 --> 00:15:59.710 align:start position:0% um so yes there are ways to attack it there<00:15:56.940> are<00:15:57.120> ways<00:15:57.360> to 00:15:59.710 --> 00:15:59.720 align:start position:0% 00:15:59.720 --> 00:16:02.509 align:start position:0% be<00:16:00.720> mean<00:16:00.899> about<00:16:01.139> it<00:16:01.380> but<00:16:01.680> I<00:16:01.860> think<00:16:02.100> for<00:16:02.339> the 00:16:02.509 --> 00:16:02.519 align:start position:0% be mean about it but I think for the 00:16:02.519 --> 00:16:05.030 align:start position:0% be mean about it but I think for the most<00:16:02.639> part<00:16:02.880> as<00:16:03.300> long<00:16:03.480> as 00:16:05.030 --> 00:16:05.040 align:start position:0% most part as long as 00:16:05.040 --> 00:16:07.370 align:start position:0% most part as long as as<00:16:05.459> long<00:16:05.699> as<00:16:05.820> enough<00:16:06.120> users<00:16:06.660> are<00:16:06.899> just<00:16:07.079> kind<00:16:07.260> of 00:16:07.370 --> 00:16:07.380 align:start position:0% as long as enough users are just kind of 00:16:07.380 --> 00:16:10.009 align:start position:0% as long as enough users are just kind of passively<00:16:07.980> participating<00:16:08.940> then<00:16:09.360> that's<00:16:09.660> not 00:16:10.009 --> 00:16:10.019 align:start position:0% passively participating then that's not 00:16:10.019 --> 00:16:11.689 align:start position:0% passively participating then that's not as 00:16:11.689 --> 00:16:11.699 align:start position:0% as 00:16:11.699 --> 00:16:13.790 align:start position:0% as this<00:16:12.240> isn't<00:16:12.540> this<00:16:12.839> isn't<00:16:13.139> crucial<00:16:13.440> to<00:16:13.680> the 00:16:13.790 --> 00:16:13.800 align:start position:0% this isn't this isn't crucial to the 00:16:13.800 --> 00:16:15.350 align:start position:0% this isn't this isn't crucial to the protocol<00:16:14.100> itself<00:16:14.519> like<00:16:14.760> portal<00:16:15.120> that<00:16:15.240> we're 00:16:15.350 --> 00:16:15.360 align:start position:0% protocol itself like portal that we're 00:16:15.360 --> 00:16:17.269 align:start position:0% protocol itself like portal that we're going<00:16:15.540> down<00:16:15.720> does<00:16:16.079> not<00:16:16.260> affect<00:16:16.500> ethereum<00:16:17.040> in 00:16:17.269 --> 00:16:17.279 align:start position:0% going down does not affect ethereum in 00:16:17.279 --> 00:16:19.009 align:start position:0% going down does not affect ethereum in any<00:16:17.459> way 00:16:19.009 --> 00:16:19.019 align:start position:0% any way 00:16:19.019 --> 00:16:21.170 align:start position:0% any way so<00:16:19.560> we<00:16:20.220> can<00:16:20.399> build<00:16:20.519> this<00:16:20.760> thing<00:16:20.940> that's 00:16:21.170 --> 00:16:21.180 align:start position:0% so we can build this thing that's 00:16:21.180 --> 00:16:23.329 align:start position:0% so we can build this thing that's lightweight<00:16:21.720> and<00:16:22.079> hopefully<00:16:22.800> just<00:16:23.040> working 00:16:23.329 --> 00:16:23.339 align:start position:0% lightweight and hopefully just working 00:16:23.339 --> 00:16:25.550 align:start position:0% lightweight and hopefully just working on 00:16:25.550 --> 00:16:25.560 align:start position:0% on 00:16:25.560 --> 00:16:28.069 align:start position:0% on it's<00:16:25.620> working<00:16:25.980> on<00:16:26.279> like<00:16:26.459> natural<00:16:26.760> natural<00:16:27.660> law 00:16:28.069 --> 00:16:28.079 align:start position:0% it's working on like natural natural law 00:16:28.079 --> 00:16:30.769 align:start position:0% it's working on like natural natural law essentially<00:16:29.120> nobody<00:16:30.120> really<00:16:30.360> has<00:16:30.540> anything 00:16:30.769 --> 00:16:30.779 align:start position:0% essentially nobody really has anything 00:16:30.779 --> 00:16:33.050 align:start position:0% essentially nobody really has anything to<00:16:31.199> gain<00:16:31.440> by<00:16:31.740> trying<00:16:31.920> to<00:16:32.100> shut<00:16:32.279> it<00:16:32.459> down<00:16:32.639> and<00:16:32.940> it 00:16:33.050 --> 00:16:33.060 align:start position:0% to gain by trying to shut it down and it 00:16:33.060 --> 00:16:35.630 align:start position:0% to gain by trying to shut it down and it doesn't<00:16:33.300> really<00:16:33.839> affect<00:16:34.199> anything 00:16:35.630 --> 00:16:35.640 align:start position:0% doesn't really affect anything 00:16:35.640 --> 00:16:38.389 align:start position:0% doesn't really affect anything [Music] 00:16:38.389 --> 00:16:38.399 align:start position:0% [Music] 00:16:38.399 --> 00:16:40.310 align:start position:0% [Music] yeah<00:16:39.000> you<00:16:39.360> know<00:16:39.480> problems<00:16:40.019> that<00:16:40.139> we're 00:16:40.310 --> 00:16:40.320 align:start position:0% yeah you know problems that we're 00:16:40.320 --> 00:16:41.990 align:start position:0% yeah you know problems that we're working<00:16:40.560> out<00:16:40.800> we're<00:16:41.160> uh<00:16:41.459> we're<00:16:41.759> trying<00:16:41.880> to 00:16:41.990 --> 00:16:42.000 align:start position:0% working out we're uh we're trying to 00:16:42.000 --> 00:16:43.730 align:start position:0% working out we're uh we're trying to steam<00:16:42.240> ahead<00:16:42.540> with<00:16:42.720> like<00:16:42.959> building<00:16:43.199> the<00:16:43.560> thing 00:16:43.730 --> 00:16:43.740 align:start position:0% steam ahead with like building the thing 00:16:43.740 --> 00:16:45.230 align:start position:0% steam ahead with like building the thing and<00:16:44.100> then<00:16:44.220> like 00:16:45.230 --> 00:16:45.240 align:start position:0% and then like 00:16:45.240 --> 00:16:47.389 align:start position:0% and then like uh<00:16:45.899> solve<00:16:46.259> all<00:16:46.380> these<00:16:46.680> problems<00:16:46.980> along<00:16:47.160> the 00:16:47.389 --> 00:16:47.399 align:start position:0% uh solve all these problems along the 00:16:47.399 --> 00:16:48.769 align:start position:0% uh solve all these problems along the way 00:16:48.769 --> 00:16:48.779 align:start position:0% way 00:16:48.779 --> 00:16:52.850 align:start position:0% way but<00:16:49.740> yeah<00:16:49.920> please<00:16:50.160> uh<00:16:50.759> our<00:16:51.720> it's<00:16:52.199> Ultra<00:16:52.620> late 00:16:52.850 --> 00:16:52.860 align:start position:0% but yeah please uh our it's Ultra late 00:16:52.860 --> 00:16:55.430 align:start position:0% but yeah please uh our it's Ultra late team<00:16:53.040> is<00:16:53.279> just<00:16:53.519> two<00:16:53.820> people<00:16:54.120> it's<00:16:54.480> me<00:16:54.720> and<00:16:55.019> me 00:16:55.430 --> 00:16:55.440 align:start position:0% team is just two people it's me and me 00:16:55.440 --> 00:16:57.949 align:start position:0% team is just two people it's me and me and<00:16:55.620> Andrew<00:16:56.160> from<00:16:56.519> our<00:16:56.699> team<00:16:56.880> so 00:16:57.949 --> 00:16:57.959 align:start position:0% and Andrew from our team so 00:16:57.959 --> 00:17:01.850 align:start position:0% and Andrew from our team so uh<00:16:58.620> we're<00:16:58.800> always<00:16:59.100> looking<00:16:59.459> for<00:16:59.820> help<00:17:00.120> or<00:17:00.540> for 00:17:01.850 --> 00:17:01.860 align:start position:0% uh we're always looking for help or for 00:17:01.860 --> 00:17:03.590 align:start position:0% uh we're always looking for help or for whatever<00:17:02.160> kind<00:17:02.579> of<00:17:02.699> contributions<00:17:03.120> are<00:17:03.420> out 00:17:03.590 --> 00:17:03.600 align:start position:0% whatever kind of contributions are out 00:17:03.600 --> 00:17:05.870 align:start position:0% whatever kind of contributions are out there 00:17:05.870 --> 00:17:05.880 align:start position:0% 00:17:05.880 --> 00:17:08.390 align:start position:0% cool<00:17:06.660> other<00:17:06.959> questions<00:17:07.319> on<00:17:07.620> that<00:17:07.740> before<00:17:08.040> we 00:17:08.390 --> 00:17:08.400 align:start position:0% cool other questions on that before we 00:17:08.400 --> 00:17:11.030 align:start position:0% cool other questions on that before we move<00:17:08.760> back<00:17:08.939> to<00:17:09.179> more<00:17:09.299> like<00:17:09.480> the<00:17:09.720> actual<00:17:10.260> htmjs 00:17:11.030 --> 00:17:11.040 align:start position:0% move back to more like the actual htmjs 00:17:11.040 --> 00:17:16.850 align:start position:0% move back to more like the actual htmjs motor<00:17:11.280> repo 00:17:16.850 --> 00:17:16.860 align:start position:0% 00:17:16.860 --> 00:17:20.329 align:start position:0% so<00:17:17.819> we<00:17:18.120> uh<00:17:18.660> we<00:17:19.020> have<00:17:19.140> a<00:17:19.260> concept<00:17:19.799> of<00:17:19.980> a<00:17:20.160> bridge 00:17:20.329 --> 00:17:20.339 align:start position:0% so we uh we have a concept of a bridge 00:17:20.339 --> 00:17:23.270 align:start position:0% so we uh we have a concept of a bridge node<00:17:20.819> which<00:17:21.360> is<00:17:21.540> something<00:17:21.959> that<00:17:22.319> is 00:17:23.270 --> 00:17:23.280 align:start position:0% node which is something that is 00:17:23.280 --> 00:17:25.850 align:start position:0% node which is something that is um<00:17:23.339> is<00:17:23.819> synced<00:17:24.299> to<00:17:24.360> the<00:17:24.540> net<00:17:24.660> and<00:17:24.959> is<00:17:25.140> or<00:17:25.380> synced 00:17:25.850 --> 00:17:25.860 align:start position:0% um is synced to the net and is or synced 00:17:25.860 --> 00:17:28.850 align:start position:0% um is synced to the net and is or synced to<00:17:25.919> the<00:17:26.040> chain<00:17:26.400> and<00:17:27.299> is<00:17:27.419> just<00:17:27.600> feeding<00:17:28.020> feeding 00:17:28.850 --> 00:17:28.860 align:start position:0% to the chain and is just feeding feeding 00:17:28.860 --> 00:17:31.010 align:start position:0% to the chain and is just feeding feeding into<00:17:29.100> the<00:17:29.400> portal<00:17:29.700> Network 00:17:31.010 --> 00:17:31.020 align:start position:0% into the portal Network 00:17:31.020 --> 00:17:32.870 align:start position:0% into the portal Network if<00:17:31.320> we<00:17:31.380> have<00:17:31.559> enough<00:17:31.740> of<00:17:32.040> those<00:17:32.280> it<00:17:32.580> just<00:17:32.760> kind 00:17:32.870 --> 00:17:32.880 align:start position:0% if we have enough of those it just kind 00:17:32.880 --> 00:17:35.990 align:start position:0% if we have enough of those it just kind of<00:17:33.000> saturates<00:17:33.480> over<00:17:33.840> time<00:17:34.140> we<00:17:34.679> also<00:17:34.919> have<00:17:35.220> kind 00:17:35.990 --> 00:17:36.000 align:start position:0% of saturates over time we also have kind 00:17:36.000 --> 00:17:38.510 align:start position:0% of saturates over time we also have kind of<00:17:36.120> ideas<00:17:36.299> of<00:17:36.660> how<00:17:36.840> to 00:17:38.510 --> 00:17:38.520 align:start position:0% of ideas of how to 00:17:38.520 --> 00:17:40.070 align:start position:0% of ideas of how to I<00:17:38.820> don't<00:17:38.940> know<00:17:39.000> maybe<00:17:39.240> like<00:17:39.419> a<00:17:39.600> babysitter 00:17:40.070 --> 00:17:40.080 align:start position:0% I don't know maybe like a babysitter 00:17:40.080 --> 00:17:41.930 align:start position:0% I don't know maybe like a babysitter node<00:17:40.559> that<00:17:40.860> kind<00:17:41.039> of<00:17:41.100> like<00:17:41.280> circles<00:17:41.760> the 00:17:41.930 --> 00:17:41.940 align:start position:0% node that kind of like circles the 00:17:41.940 --> 00:17:44.090 align:start position:0% node that kind of like circles the network<00:17:42.120> and<00:17:42.480> looks<00:17:42.780> for<00:17:42.900> gaps<00:17:43.320> and<00:17:43.620> and<00:17:43.860> kind 00:17:44.090 --> 00:17:44.100 align:start position:0% network and looks for gaps and and kind 00:17:44.100 --> 00:17:46.730 align:start position:0% network and looks for gaps and and kind of<00:17:44.220> helps<00:17:44.580> helps<00:17:45.240> fill<00:17:45.419> in<00:17:45.600> the<00:17:45.720> gaps<00:17:46.080> uh<00:17:46.559> but 00:17:46.730 --> 00:17:46.740 align:start position:0% of helps helps fill in the gaps uh but 00:17:46.740 --> 00:17:48.110 align:start position:0% of helps helps fill in the gaps uh but yeah<00:17:46.919> it's<00:17:47.039> these<00:17:47.340> kind<00:17:47.460> of<00:17:47.520> bridge<00:17:47.640> nodes 00:17:48.110 --> 00:17:48.120 align:start position:0% yeah it's these kind of bridge nodes 00:17:48.120 --> 00:17:51.049 align:start position:0% yeah it's these kind of bridge nodes that<00:17:48.600> originally<00:17:49.440> saturate<00:17:49.980> the<00:17:50.160> network<00:17:50.400> and 00:17:51.049 --> 00:17:51.059 align:start position:0% that originally saturate the network and 00:17:51.059 --> 00:17:55.430 align:start position:0% that originally saturate the network and maybe<00:17:51.480> maintain<00:17:52.080> that 00:17:55.430 --> 00:17:55.440 align:start position:0% 00:17:55.440 --> 00:17:57.590 align:start position:0% I<00:17:55.860> put<00:17:56.039> around<00:17:56.280> with<00:17:56.640> the 00:17:57.590 --> 00:17:57.600 align:start position:0% I put around with the 00:17:57.600 --> 00:18:01.130 align:start position:0% I put around with the field 00:18:01.130 --> 00:18:01.140 align:start position:0% 00:18:01.140 --> 00:18:04.010 align:start position:0% the<00:18:02.100> boot<00:18:02.340> nodes<00:18:02.580> are<00:18:03.120> a 00:18:04.010 --> 00:18:04.020 align:start position:0% the boot nodes are a 00:18:04.020 --> 00:18:07.010 align:start position:0% the boot nodes are a H<00:18:04.500> we<00:18:04.919> have<00:18:04.980> devops<00:18:05.580> just<00:18:05.940> put<00:18:06.419> up<00:18:06.600> a<00:18:06.780> bunch<00:18:06.900> of 00:18:07.010 --> 00:18:07.020 align:start position:0% H we have devops just put up a bunch of 00:18:07.020 --> 00:18:09.110 align:start position:0% H we have devops just put up a bunch of nodes<00:18:07.320> for<00:18:07.620> us<00:18:07.799> that<00:18:08.340> that<00:18:08.520> are<00:18:08.760> acting<00:18:09.000> like 00:18:09.110 --> 00:18:09.120 align:start position:0% nodes for us that that are acting like 00:18:09.120 --> 00:18:10.730 align:start position:0% nodes for us that that are acting like boot<00:18:09.419> nodes 00:18:10.730 --> 00:18:10.740 align:start position:0% boot nodes 00:18:10.740 --> 00:18:12.470 align:start position:0% boot nodes there's<00:18:11.220> no<00:18:11.400> real<00:18:11.580> difference<00:18:11.880> between<00:18:12.240> a 00:18:12.470 --> 00:18:12.480 align:start position:0% there's no real difference between a 00:18:12.480 --> 00:18:15.230 align:start position:0% there's no real difference between a bridge<00:18:12.660> client<00:18:13.080> and<00:18:13.440> a<00:18:13.679> just<00:18:14.160> regular<00:18:14.940> client 00:18:15.230 --> 00:18:15.240 align:start position:0% bridge client and a just regular client 00:18:15.240 --> 00:18:19.010 align:start position:0% bridge client and a just regular client it's<00:18:15.480> more<00:18:15.799> uh<00:18:16.799> are<00:18:16.980> you 00:18:19.010 --> 00:18:19.020 align:start position:0% it's more uh are you 00:18:19.020 --> 00:18:20.930 align:start position:0% it's more uh are you are<00:18:19.380> you<00:18:19.559> doing<00:18:19.679> this<00:18:19.919> extra<00:18:20.100> work<00:18:20.400> to<00:18:20.760> like 00:18:20.930 --> 00:18:20.940 align:start position:0% are you doing this extra work to like 00:18:20.940 --> 00:18:23.510 align:start position:0% are you doing this extra work to like add<00:18:21.360> to<00:18:21.720> the<00:18:21.900> add<00:18:22.320> to<00:18:22.440> the<00:18:22.559> network<00:18:22.740> or<00:18:23.280> are<00:18:23.400> you 00:18:23.510 --> 00:18:23.520 align:start position:0% add to the add to the network or are you 00:18:23.520 --> 00:18:25.130 align:start position:0% add to the add to the network or are you just<00:18:23.700> helping<00:18:24.179> to<00:18:24.360> gossip<00:18:24.660> around<00:18:24.900> the 00:18:25.130 --> 00:18:25.140 align:start position:0% just helping to gossip around the 00:18:25.140 --> 00:18:28.549 align:start position:0% just helping to gossip around the network 00:18:28.549 --> 00:18:28.559 align:start position:0% 00:18:28.559 --> 00:18:32.029 align:start position:0% yeah<00:18:29.220> all<00:18:29.820> right<00:18:30.059> so<00:18:30.539> we'll<00:18:30.840> we'll<00:18:31.380> move<00:18:31.740> ahead 00:18:32.029 --> 00:18:32.039 align:start position:0% yeah all right so we'll we'll move ahead 00:18:32.039 --> 00:18:35.270 align:start position:0% yeah all right so we'll we'll move ahead with<00:18:32.520> a<00:18:32.880> demo<00:18:33.539> uh<00:18:33.840> video<00:18:34.140> m.js 00:18:35.270 --> 00:18:35.280 align:start position:0% with a demo uh video m.js 00:18:35.280 --> 00:18:37.850 align:start position:0% with a demo uh video m.js so<00:18:35.820> as<00:18:36.000> you<00:18:36.120> know<00:18:36.240> the<00:18:36.419> next<00:18:36.539> hard<00:18:36.780> for<00:18:37.080> hard 00:18:37.850 --> 00:18:37.860 align:start position:0% so as you know the next hard for hard 00:18:37.860 --> 00:18:40.610 align:start position:0% so as you know the next hard for hard Fork<00:18:38.220> is<00:18:38.400> going<00:18:38.520> to<00:18:38.640> be<00:18:38.700> named<00:18:39.120> Shanghai 00:18:40.610 --> 00:18:40.620 align:start position:0% Fork is going to be named Shanghai 00:18:40.620 --> 00:18:43.310 align:start position:0% Fork is going to be named Shanghai and<00:18:41.580> there's<00:18:42.059> a<00:18:42.240> test<00:18:42.360> net<00:18:42.600> running<00:18:42.960> at<00:18:43.200> the 00:18:43.310 --> 00:18:43.320 align:start position:0% and there's a test net running at the 00:18:43.320 --> 00:18:45.169 align:start position:0% and there's a test net running at the moment<00:18:43.440> it<00:18:43.799> was<00:18:44.039> down<00:18:44.220> for<00:18:44.400> a<00:18:44.520> couple<00:18:44.580> days<00:18:44.880> but 00:18:45.169 --> 00:18:45.179 align:start position:0% moment it was down for a couple days but 00:18:45.179 --> 00:18:46.970 align:start position:0% moment it was down for a couple days but it<00:18:45.360> got<00:18:45.660> back<00:18:45.840> up<00:18:46.020> I<00:18:46.260> think<00:18:46.380> this<00:18:46.500> morning<00:18:46.679> or 00:18:46.970 --> 00:18:46.980 align:start position:0% it got back up I think this morning or 00:18:46.980 --> 00:18:48.350 align:start position:0% it got back up I think this morning or last<00:18:47.340> night 00:18:48.350 --> 00:18:48.360 align:start position:0% last night 00:18:48.360 --> 00:18:51.590 align:start position:0% last night uh<00:18:49.260> it's<00:18:49.620> uh<00:18:50.340> it's<00:18:50.880> a<00:18:51.000> test<00:18:51.120> net<00:18:51.360> that 00:18:51.590 --> 00:18:51.600 align:start position:0% uh it's uh it's a test net that 00:18:51.600 --> 00:18:54.950 align:start position:0% uh it's uh it's a test net that basically<00:18:51.900> implements<00:18:52.440> a<00:18:52.559> subset<00:18:53.039> of<00:18:53.460> the<00:18:54.000> uh 00:18:54.950 --> 00:18:54.960 align:start position:0% basically implements a subset of the uh 00:18:54.960 --> 00:18:56.690 align:start position:0% basically implements a subset of the uh of<00:18:55.200> the<00:18:55.380> eips 00:18:56.690 --> 00:18:56.700 align:start position:0% of the eips 00:18:56.700 --> 00:18:59.270 align:start position:0% of the eips that<00:18:57.360> are<00:18:57.600> going<00:18:57.900> to<00:18:58.080> be<00:18:58.140> part<00:18:58.320> of<00:18:58.500> Shanghai<00:18:58.919> so 00:18:59.270 --> 00:18:59.280 align:start position:0% that are going to be part of Shanghai so 00:18:59.280 --> 00:19:00.830 align:start position:0% that are going to be part of Shanghai so there<00:18:59.460> might<00:18:59.640> be<00:18:59.760> additional<00:19:00.299> ones<00:19:00.539> the<00:19:00.720> one 00:19:00.830 --> 00:19:00.840 align:start position:0% there might be additional ones the one 00:19:00.840 --> 00:19:02.870 align:start position:0% there might be additional ones the one on<00:19:00.960> this<00:19:01.080> list<00:19:01.260> at<00:19:01.440> the<00:19:01.559> moment<00:19:01.740> but<00:19:02.400> that<00:19:02.640> like 00:19:02.870 --> 00:19:02.880 align:start position:0% on this list at the moment but that like 00:19:02.880 --> 00:19:04.970 align:start position:0% on this list at the moment but that like tentative<00:19:03.299> like<00:19:03.720> list<00:19:03.960> of<00:19:04.140> VIPs<00:19:04.440> that<00:19:04.860> are 00:19:04.970 --> 00:19:04.980 align:start position:0% tentative like list of VIPs that are 00:19:04.980 --> 00:19:06.529 align:start position:0% tentative like list of VIPs that are going<00:19:05.100> to<00:19:05.220> be<00:19:05.280> included<00:19:05.580> at<00:19:05.880> the<00:19:06.000> moment<00:19:06.120> is<00:19:06.360> is 00:19:06.529 --> 00:19:06.539 align:start position:0% going to be included at the moment is is 00:19:06.539 --> 00:19:08.990 align:start position:0% going to be included at the moment is is the<00:19:06.780> one<00:19:06.900> you<00:19:07.020> see<00:19:07.140> on<00:19:07.260> the<00:19:07.440> screen<00:19:07.760> so<00:19:08.760> the 00:19:08.990 --> 00:19:09.000 align:start position:0% the one you see on the screen so the 00:19:09.000 --> 00:19:10.730 align:start position:0% the one you see on the screen so the beacon<00:19:09.360> chain<00:19:09.480> withdrawals<00:19:10.200> and<00:19:10.380> the<00:19:10.559> the 00:19:10.730 --> 00:19:10.740 align:start position:0% beacon chain withdrawals and the the 00:19:10.740 --> 00:19:12.650 align:start position:0% beacon chain withdrawals and the the activate<00:19:10.980> self-destruct<00:19:11.700> aren't<00:19:12.240> deployment 00:19:12.650 --> 00:19:12.660 align:start position:0% activate self-destruct aren't deployment 00:19:12.660 --> 00:19:16.669 align:start position:0% activate self-destruct aren't deployment implemented<00:19:13.320> yet<00:19:13.559> in<00:19:13.919> our<00:19:14.160> uh<00:19:15.120> in<00:19:15.539> our<00:19:15.660> client 00:19:16.669 --> 00:19:16.679 align:start position:0% implemented yet in our uh in our client 00:19:16.679 --> 00:19:19.130 align:start position:0% implemented yet in our uh in our client but<00:19:17.280> uh<00:19:17.640> yeah<00:19:17.940> the<00:19:18.120> shandoned<00:19:18.600> testnet<00:19:18.900> is<00:19:19.020> up 00:19:19.130 --> 00:19:19.140 align:start position:0% but uh yeah the shandoned testnet is up 00:19:19.140 --> 00:19:20.690 align:start position:0% but uh yeah the shandoned testnet is up and<00:19:19.260> running<00:19:19.380> we<00:19:19.980> have<00:19:20.100> it<00:19:20.220> running<00:19:20.400> with 00:19:20.690 --> 00:19:20.700 align:start position:0% and running we have it running with 00:19:20.700 --> 00:19:24.110 align:start position:0% and running we have it running with lodestar<00:19:21.240> as<00:19:21.660> a<00:19:21.900> consensus<00:19:22.440> uh<00:19:23.280> client<00:19:23.940> which 00:19:24.110 --> 00:19:24.120 align:start position:0% lodestar as a consensus uh client which 00:19:24.120 --> 00:19:25.549 align:start position:0% lodestar as a consensus uh client which is<00:19:24.240> like<00:19:24.360> the<00:19:24.600> typescript<00:19:24.960> you<00:19:25.440> know 00:19:25.549 --> 00:19:25.559 align:start position:0% is like the typescript you know 00:19:25.559 --> 00:19:27.610 align:start position:0% is like the typescript you know consensus<00:19:26.520> client 00:19:27.610 --> 00:19:27.620 align:start position:0% consensus client 00:19:27.620 --> 00:19:30.830 align:start position:0% consensus client and<00:19:28.620> then<00:19:29.520> we<00:19:29.700> have<00:19:29.880> it<00:19:30.059> there<00:19:30.240> with<00:19:30.720> uh 00:19:30.830 --> 00:19:30.840 align:start position:0% and then we have it there with uh 00:19:30.840 --> 00:19:33.350 align:start position:0% and then we have it there with uh ethereum<00:19:31.200> js's<00:19:31.799> uh<00:19:31.980> the<00:19:32.220> execution<00:19:32.700> client<00:19:33.179> so 00:19:33.350 --> 00:19:33.360 align:start position:0% ethereum js's uh the execution client so 00:19:33.360 --> 00:19:36.650 align:start position:0% ethereum js's uh the execution client so that<00:19:33.480> testnet<00:19:33.960> is<00:19:34.140> so<00:19:34.380> it's<00:19:35.039> live<00:19:35.360> uh<00:19:36.360> you<00:19:36.539> can 00:19:36.650 --> 00:19:36.660 align:start position:0% that testnet is so it's live uh you can 00:19:36.660 --> 00:19:38.510 align:start position:0% that testnet is so it's live uh you can look<00:19:36.840> it<00:19:37.020> up<00:19:37.140> there's<00:19:37.380> a<00:19:37.620> block<00:19:37.740> explorer<00:19:38.340> that 00:19:38.510 --> 00:19:38.520 align:start position:0% look it up there's a block explorer that 00:19:38.520 --> 00:19:41.450 align:start position:0% look it up there's a block explorer that I<00:19:38.640> think<00:19:38.760> we<00:19:38.940> just<00:19:39.120> put<00:19:39.360> up<00:19:39.539> this<00:19:39.780> morning<00:19:40.460> uh 00:19:41.450 --> 00:19:41.460 align:start position:0% I think we just put up this morning uh 00:19:41.460 --> 00:19:43.610 align:start position:0% I think we just put up this morning uh and<00:19:41.940> as<00:19:42.419> far<00:19:42.600> as<00:19:42.720> I<00:19:42.840> know<00:19:43.020> like<00:19:43.260> the<00:19:43.500> only 00:19:43.610 --> 00:19:43.620 align:start position:0% and as far as I know like the only 00:19:43.620 --> 00:19:45.350 align:start position:0% and as far as I know like the only execution<00:19:44.039> client<00:19:44.400> that's<00:19:44.760> actually<00:19:45.120> running 00:19:45.350 --> 00:19:45.360 align:start position:0% execution client that's actually running 00:19:45.360 --> 00:19:48.350 align:start position:0% execution client that's actually running that<00:19:45.660> at<00:19:45.840> the<00:19:45.960> moment<00:19:46.080> is<00:19:46.500> ethereum<00:19:47.400> JR<00:19:48.120> so<00:19:48.240> the 00:19:48.350 --> 00:19:48.360 align:start position:0% that at the moment is ethereum JR so the 00:19:48.360 --> 00:19:50.150 align:start position:0% that at the moment is ethereum JR so the JavaScript<00:19:48.780> uh 00:19:50.150 --> 00:19:50.160 align:start position:0% JavaScript uh 00:19:50.160 --> 00:19:51.470 align:start position:0% JavaScript uh client 00:19:51.470 --> 00:19:51.480 align:start position:0% client 00:19:51.480 --> 00:19:54.049 align:start position:0% client so<00:19:52.020> what<00:19:52.320> I'll<00:19:52.440> do<00:19:52.620> is<00:19:52.799> just<00:19:53.039> uh<00:19:53.520> I<00:19:53.760> will<00:19:53.940> not 00:19:54.049 --> 00:19:54.059 align:start position:0% so what I'll do is just uh I will not 00:19:54.059 --> 00:19:56.510 align:start position:0% so what I'll do is just uh I will not like<00:19:54.360> run<00:19:54.780> I<00:19:55.200> will<00:19:55.440> not<00:19:55.559> access<00:19:55.740> like<00:19:56.100> the 00:19:56.510 --> 00:19:56.520 align:start position:0% like run I will not access like the 00:19:56.520 --> 00:19:58.490 align:start position:0% like run I will not access like the actual<00:19:57.240> you<00:19:57.480> know<00:19:57.660> Live<00:19:57.780> Test<00:19:57.960> net<00:19:58.140> but<00:19:58.380> I'll 00:19:58.490 --> 00:19:58.500 align:start position:0% actual you know Live Test net but I'll 00:19:58.500 --> 00:20:00.470 align:start position:0% actual you know Live Test net but I'll run<00:19:58.740> like<00:19:58.980> the<00:19:59.160> test<00:19:59.280> net<00:19:59.460> locally<00:19:59.820> to<00:20:00.299> give 00:20:00.470 --> 00:20:00.480 align:start position:0% run like the test net locally to give 00:20:00.480 --> 00:20:02.450 align:start position:0% run like the test net locally to give you<00:20:00.600> a<00:20:00.780> sense<00:20:00.960> of<00:20:01.200> how<00:20:01.860> you<00:20:02.039> would<00:20:02.220> go<00:20:02.340> about 00:20:02.450 --> 00:20:02.460 align:start position:0% you a sense of how you would go about 00:20:02.460 --> 00:20:03.950 align:start position:0% you a sense of how you would go about doing<00:20:02.760> that<00:20:03.000> and<00:20:03.179> you<00:20:03.299> might<00:20:03.419> be<00:20:03.600> interested 00:20:03.950 --> 00:20:03.960 align:start position:0% doing that and you might be interested 00:20:03.960 --> 00:20:05.750 align:start position:0% doing that and you might be interested in<00:20:04.140> running<00:20:04.559> that<00:20:04.860> yourself<00:20:05.039> when<00:20:05.340> we<00:20:05.520> go<00:20:05.640> into 00:20:05.750 --> 00:20:05.760 align:start position:0% in running that yourself when we go into 00:20:05.760 --> 00:20:08.450 align:start position:0% in running that yourself when we go into the<00:20:05.940> more<00:20:06.120> like<00:20:06.660> interactive<00:20:07.260> part<00:20:07.500> of<00:20:08.340> the 00:20:08.450 --> 00:20:08.460 align:start position:0% the more like interactive part of the 00:20:08.460 --> 00:20:11.810 align:start position:0% the more like interactive part of the workshop<00:20:08.820> so<00:20:09.419> I<00:20:09.600> just<00:20:09.840> need<00:20:10.080> to<00:20:10.799> check<00:20:11.160> out<00:20:11.460> the 00:20:11.810 --> 00:20:11.820 align:start position:0% workshop so I just need to check out the 00:20:11.820 --> 00:20:13.070 align:start position:0% workshop so I just need to check out the proper 00:20:13.070 --> 00:20:13.080 align:start position:0% proper 00:20:13.080 --> 00:20:17.510 align:start position:0% proper pull<00:20:13.559> request<00:20:14.039> from<00:20:14.640> our<00:20:14.880> molar<00:20:15.600> repo 00:20:17.510 --> 00:20:17.520 align:start position:0% pull request from our molar repo 00:20:17.520 --> 00:20:21.230 align:start position:0% pull request from our molar repo so<00:20:18.000> it's<00:20:18.120> just<00:20:18.360> that<00:20:18.539> here 00:20:21.230 --> 00:20:21.240 align:start position:0% 00:20:21.240 --> 00:20:23.150 align:start position:0% so<00:20:21.539> yeah<00:20:21.660> as<00:20:21.840> we<00:20:22.020> said<00:20:22.140> our<00:20:22.320> mono<00:20:22.679> repo<00:20:22.980> is 00:20:23.150 --> 00:20:23.160 align:start position:0% so yeah as we said our mono repo is 00:20:23.160 --> 00:20:25.250 align:start position:0% so yeah as we said our mono repo is broken<00:20:23.340> into<00:20:23.700> you<00:20:24.419> know<00:20:24.539> packages<00:20:24.840> can<00:20:25.140> you 00:20:25.250 --> 00:20:25.260 align:start position:0% broken into you know packages can you 00:20:25.260 --> 00:20:27.590 align:start position:0% broken into you know packages can you see<00:20:25.380> the<00:20:25.559> DS<00:20:25.919> code<00:20:26.100> yeah<00:20:26.580> cool 00:20:27.590 --> 00:20:27.600 align:start position:0% see the DS code yeah cool 00:20:27.600 --> 00:20:31.490 align:start position:0% see the DS code yeah cool awesome<00:20:27.960> so 00:20:31.490 --> 00:20:31.500 align:start position:0% 00:20:31.500 --> 00:20:34.190 align:start position:0% we'll<00:20:32.039> just<00:20:32.220> go<00:20:32.460> to<00:20:32.880> the<00:20:33.059> package<00:20:33.360> client<00:20:33.780> and 00:20:34.190 --> 00:20:34.200 align:start position:0% we'll just go to the package client and 00:20:34.200 --> 00:20:35.750 align:start position:0% we'll just go to the package client and I<00:20:34.320> have<00:20:34.500> you<00:20:34.860> know<00:20:34.919> a<00:20:34.980> couple<00:20:35.100> of<00:20:35.280> instructions 00:20:35.750 --> 00:20:35.760 align:start position:0% I have you know a couple of instructions 00:20:35.760 --> 00:20:38.390 align:start position:0% I have you know a couple of instructions I've<00:20:36.120> I've<00:20:36.539> done<00:20:36.780> here<00:20:37.020> so<00:20:37.260> basically<00:20:37.559> what<00:20:37.919> we 00:20:38.390 --> 00:20:38.400 align:start position:0% I've I've done here so basically what we 00:20:38.400 --> 00:20:40.730 align:start position:0% I've I've done here so basically what we first<00:20:38.940> want<00:20:39.720> to<00:20:39.840> do<00:20:39.960> is<00:20:40.080> we<00:20:40.260> want<00:20:40.440> to<00:20:40.559> create 00:20:40.730 --> 00:20:40.740 align:start position:0% first want to do is we want to create 00:20:40.740 --> 00:20:43.730 align:start position:0% first want to do is we want to create you<00:20:41.160> know<00:20:41.220> data<00:20:41.760> folders<00:20:42.299> for<00:20:42.960> about<00:20:43.140> you<00:20:43.620> know 00:20:43.730 --> 00:20:43.740 align:start position:0% you know data folders for about you know 00:20:43.740 --> 00:20:46.070 align:start position:0% you know data folders for about you know the<00:20:44.280> execution<00:20:44.880> layer<00:20:45.299> data<00:20:45.720> and<00:20:45.900> that 00:20:46.070 --> 00:20:46.080 align:start position:0% the execution layer data and that 00:20:46.080 --> 00:20:49.970 align:start position:0% the execution layer data and that consists<00:20:46.380> data<00:20:46.740> yeah 00:20:49.970 --> 00:20:49.980 align:start position:0% 00:20:49.980 --> 00:20:52.909 align:start position:0% zoom<00:20:50.940> in 00:20:52.909 --> 00:20:52.919 align:start position:0% zoom in 00:20:52.919 --> 00:20:55.850 align:start position:0% zoom in I'm<00:20:53.460> not<00:20:53.580> sure<00:20:53.760> if<00:20:53.940> I<00:20:54.120> can<00:20:54.299> zoom<00:20:54.720> in<00:20:55.200> notion 00:20:55.850 --> 00:20:55.860 align:start position:0% I'm not sure if I can zoom in notion 00:20:55.860 --> 00:20:59.150 align:start position:0% I'm not sure if I can zoom in notion actually<00:20:56.299> but<00:20:57.299> I<00:20:57.480> can<00:20:57.600> definitely<00:20:57.900> zoom<00:20:58.380> in<00:20:58.559> vs 00:20:59.150 --> 00:20:59.160 align:start position:0% actually but I can definitely zoom in vs 00:20:59.160 --> 00:21:01.909 align:start position:0% actually but I can definitely zoom in vs codes<00:20:59.400> at<00:20:59.880> least<00:21:00.059> that's<00:21:00.179> going<00:21:00.419> to<00:21:00.480> be<00:21:00.539> that 00:21:01.909 --> 00:21:01.919 align:start position:0% codes at least that's going to be that 00:21:01.919 --> 00:21:04.190 align:start position:0% codes at least that's going to be that is<00:21:02.340> that<00:21:02.460> better 00:21:04.190 --> 00:21:04.200 align:start position:0% is that better 00:21:04.200 --> 00:21:19.390 align:start position:0% is that better yeah<00:21:04.679> cool<00:21:04.919> no<00:21:05.220> worries 00:21:19.390 --> 00:21:19.400 align:start position:0% 00:21:19.400 --> 00:21:21.710 align:start position:0% oh<00:21:20.400> yeah<00:21:20.580> yeah<00:21:20.760> they're<00:21:21.120> actually<00:21:21.299> available 00:21:21.710 --> 00:21:21.720 align:start position:0% oh yeah yeah they're actually available 00:21:21.720 --> 00:21:24.289 align:start position:0% oh yeah yeah they're actually available on<00:21:22.559> that<00:21:22.740> pull<00:21:22.919> request<00:21:23.340> and<00:21:23.700> in<00:21:24.000> a<00:21:24.179> couple 00:21:24.289 --> 00:21:24.299 align:start position:0% on that pull request and in a couple 00:21:24.299 --> 00:21:27.169 align:start position:0% on that pull request and in a couple slides<00:21:24.980> there's<00:21:25.980> a<00:21:26.160> link<00:21:26.280> tree<00:21:26.520> with<00:21:26.880> all<00:21:27.059> of 00:21:27.169 --> 00:21:27.179 align:start position:0% slides there's a link tree with all of 00:21:27.179 --> 00:21:29.029 align:start position:0% slides there's a link tree with all of these<00:21:27.539> outlines<00:21:28.140> so<00:21:28.380> you<00:21:28.559> definitely<00:21:28.740> can 00:21:29.029 --> 00:21:29.039 align:start position:0% these outlines so you definitely can 00:21:29.039 --> 00:21:32.210 align:start position:0% these outlines so you definitely can access<00:21:29.640> all<00:21:29.940> of<00:21:30.120> these<00:21:30.240> nodes<00:21:30.620> and<00:21:31.620> yeah<00:21:31.980> it's 00:21:32.210 --> 00:21:32.220 align:start position:0% access all of these nodes and yeah it's 00:21:32.220 --> 00:21:34.190 align:start position:0% access all of these nodes and yeah it's it's<00:21:32.400> a<00:21:32.640> good<00:21:32.760> exercise<00:21:32.940> as<00:21:33.299> well<00:21:33.480> to<00:21:33.780> uh<00:21:33.960> you 00:21:34.190 --> 00:21:34.200 align:start position:0% it's a good exercise as well to uh you 00:21:34.200 --> 00:21:36.110 align:start position:0% it's a good exercise as well to uh you know<00:21:34.260> run<00:21:34.500> that<00:21:34.740> yourself<00:21:35.100> you<00:21:35.640> will<00:21:35.880> have 00:21:36.110 --> 00:21:36.120 align:start position:0% know run that yourself you will have 00:21:36.120 --> 00:21:37.909 align:start position:0% know run that yourself you will have time<00:21:36.360> for<00:21:36.539> that<00:21:36.659> and<00:21:36.840> we'll<00:21:37.020> be<00:21:37.260> happy<00:21:37.500> to<00:21:37.679> help 00:21:37.909 --> 00:21:37.919 align:start position:0% time for that and we'll be happy to help 00:21:37.919 --> 00:21:41.029 align:start position:0% time for that and we'll be happy to help everyone<00:21:38.159> get<00:21:39.120> that<00:21:39.299> running<00:21:39.620> so<00:21:40.620> yeah<00:21:40.860> the 00:21:41.029 --> 00:21:41.039 align:start position:0% everyone get that running so yeah the 00:21:41.039 --> 00:21:42.230 align:start position:0% everyone get that running so yeah the first<00:21:41.159> thing<00:21:41.340> we<00:21:41.460> want<00:21:41.580> to<00:21:41.640> do<00:21:41.760> is<00:21:41.880> just<00:21:42.059> create 00:21:42.230 --> 00:21:42.240 align:start position:0% first thing we want to do is just create 00:21:42.240 --> 00:21:44.270 align:start position:0% first thing we want to do is just create some<00:21:42.480> data<00:21:42.780> folders<00:21:43.080> where<00:21:43.440> the<00:21:43.679> the<00:21:43.860> state<00:21:44.159> of 00:21:44.270 --> 00:21:44.280 align:start position:0% some data folders where the the state of 00:21:44.280 --> 00:21:46.130 align:start position:0% some data folders where the the state of the<00:21:44.460> you<00:21:44.640> know<00:21:44.760> where<00:21:45.179> the<00:21:45.360> consensus<00:21:45.840> client 00:21:46.130 --> 00:21:46.140 align:start position:0% the you know where the consensus client 00:21:46.140 --> 00:21:48.049 align:start position:0% the you know where the consensus client data<00:21:46.500> and<00:21:46.740> the<00:21:46.919> execution<00:21:47.340> client<00:21:47.640> is<00:21:47.880> going 00:21:48.049 --> 00:21:48.059 align:start position:0% data and the execution client is going 00:21:48.059 --> 00:21:50.870 align:start position:0% data and the execution client is going to<00:21:48.120> live<00:21:48.320> so<00:21:49.320> we're<00:21:49.559> gonna<00:21:49.740> put<00:21:50.039> that<00:21:50.280> in<00:21:50.700> the 00:21:50.870 --> 00:21:50.880 align:start position:0% to live so we're gonna put that in the 00:21:50.880 --> 00:21:54.529 align:start position:0% to live so we're gonna put that in the data 00:21:54.529 --> 00:21:54.539 align:start position:0% 00:21:54.539 --> 00:21:57.470 align:start position:0% yeah<00:21:55.320> Shandong 00:21:57.470 --> 00:21:57.480 align:start position:0% yeah Shandong 00:21:57.480 --> 00:22:00.470 align:start position:0% yeah Shandong so<00:21:57.840> we're<00:21:58.020> going<00:21:58.140> to<00:21:58.260> create<00:21:58.440> an<00:21:58.740> ethereum 00:22:00.470 --> 00:22:00.480 align:start position:0% so we're going to create an ethereum 00:22:00.480 --> 00:22:02.870 align:start position:0% so we're going to create an ethereum folder<00:22:01.140> and<00:22:01.559> we're<00:22:01.679> going<00:22:01.799> to<00:22:01.919> create<00:22:02.100> a<00:22:02.460> load 00:22:02.870 --> 00:22:02.880 align:start position:0% folder and we're going to create a load 00:22:02.880 --> 00:22:05.810 align:start position:0% folder and we're going to create a load star<00:22:03.059> folder<00:22:03.840> as<00:22:03.960> well 00:22:05.810 --> 00:22:05.820 align:start position:0% star folder as well 00:22:05.820 --> 00:22:08.510 align:start position:0% star folder as well so<00:22:06.360> now<00:22:06.600> we're<00:22:07.020> good<00:22:07.200> to<00:22:07.380> go<00:22:07.440> for<00:22:07.620> that<00:22:07.799> part<00:22:07.980> so 00:22:08.510 --> 00:22:08.520 align:start position:0% so now we're good to go for that part so 00:22:08.520 --> 00:22:10.070 align:start position:0% so now we're good to go for that part so the<00:22:08.640> next<00:22:08.760> step<00:22:08.940> is<00:22:09.120> we're<00:22:09.480> already<00:22:09.659> going<00:22:09.900> to 00:22:10.070 --> 00:22:10.080 align:start position:0% the next step is we're already going to 00:22:10.080 --> 00:22:13.970 align:start position:0% the next step is we're already going to start<00:22:10.200> our<00:22:10.820> execution<00:22:11.960> like<00:22:12.960> assigned<00:22:13.440> and 00:22:13.970 --> 00:22:13.980 align:start position:0% start our execution like assigned and 00:22:13.980 --> 00:22:16.310 align:start position:0% start our execution like assigned and it's<00:22:14.159> going<00:22:14.340> to<00:22:14.460> use<00:22:14.640> a<00:22:15.179> Genesis<00:22:15.840> that's<00:22:16.020> been 00:22:16.310 --> 00:22:16.320 align:start position:0% it's going to use a Genesis that's been 00:22:16.320 --> 00:22:19.669 align:start position:0% it's going to use a Genesis that's been done<00:22:16.799> by<00:22:17.159> by<00:22:17.460> one<00:22:17.700> of<00:22:17.820> the<00:22:17.880> guys<00:22:18.000> on<00:22:18.299> our<00:22:19.020> team 00:22:19.669 --> 00:22:19.679 align:start position:0% done by by one of the guys on our team 00:22:19.679 --> 00:22:22.310 align:start position:0% done by by one of the guys on our team usually<00:22:20.159> likes<00:22:20.520> Shandong<00:22:20.940> at<00:22:21.320> genesis.json 00:22:22.310 --> 00:22:22.320 align:start position:0% usually likes Shandong at genesis.json 00:22:22.320 --> 00:22:24.770 align:start position:0% usually likes Shandong at genesis.json you'll<00:22:22.860> see<00:22:22.980> that<00:22:23.159> more<00:22:23.400> clearly 00:22:24.770 --> 00:22:24.780 align:start position:0% you'll see that more clearly 00:22:24.780 --> 00:22:27.850 align:start position:0% you'll see that more clearly here<00:22:25.380> here<00:22:25.740> in<00:22:25.980> packages 00:22:27.850 --> 00:22:27.860 align:start position:0% here here in packages 00:22:27.860 --> 00:22:30.830 align:start position:0% here here in packages what<00:22:28.860> now<00:22:29.220> you're<00:22:29.520> in<00:22:29.700> packages 00:22:30.830 --> 00:22:30.840 align:start position:0% what now you're in packages 00:22:30.840 --> 00:22:33.409 align:start position:0% what now you're in packages oh<00:22:31.320> yeah<00:22:31.500> yeah<00:22:31.679> you're<00:22:32.220> right 00:22:33.409 --> 00:22:33.419 align:start position:0% oh yeah yeah you're right 00:22:33.419 --> 00:22:36.590 align:start position:0% oh yeah yeah you're right thanks 00:22:36.590 --> 00:22:36.600 align:start position:0% 00:22:36.600 --> 00:22:39.169 align:start position:0% yeah<00:22:36.840> and<00:22:37.559> there<00:22:37.740> we<00:22:37.919> go 00:22:39.169 --> 00:22:39.179 align:start position:0% yeah and there we go 00:22:39.179 --> 00:22:40.970 align:start position:0% yeah and there we go hopefully<00:22:39.720> that<00:22:39.900> works<00:22:40.200> live<00:22:40.380> coding<00:22:40.860> is 00:22:40.970 --> 00:22:40.980 align:start position:0% hopefully that works live coding is 00:22:40.980 --> 00:22:42.710 align:start position:0% hopefully that works live coding is always<00:22:41.159> a<00:22:41.460> bit<00:22:41.580> uh 00:22:42.710 --> 00:22:42.720 align:start position:0% always a bit uh 00:22:42.720 --> 00:22:44.510 align:start position:0% always a bit uh sketchy<00:22:43.260> and<00:22:43.440> the<00:22:43.559> Wi-Fi<00:22:43.919> is<00:22:44.159> pretty<00:22:44.340> good 00:22:44.510 --> 00:22:44.520 align:start position:0% sketchy and the Wi-Fi is pretty good 00:22:44.520 --> 00:22:46.850 align:start position:0% sketchy and the Wi-Fi is pretty good actually<00:22:45.360> if<00:22:45.900> you<00:22:46.140> haven't<00:22:46.260> noticed<00:22:46.620> there's 00:22:46.850 --> 00:22:46.860 align:start position:0% actually if you haven't noticed there's 00:22:46.860 --> 00:22:49.190 align:start position:0% actually if you haven't noticed there's a<00:22:47.100> workshop<00:22:47.520> specific<00:22:48.059> Wi-Fi<00:22:48.600> network<00:22:48.840> that 00:22:49.190 --> 00:22:49.200 align:start position:0% a workshop specific Wi-Fi network that 00:22:49.200 --> 00:22:50.930 align:start position:0% a workshop specific Wi-Fi network that you<00:22:49.380> can<00:22:49.500> access<00:22:49.679> because<00:22:50.400> they're<00:22:50.700> the 00:22:50.930 --> 00:22:50.940 align:start position:0% you can access because they're the 00:22:50.940 --> 00:22:53.090 align:start position:0% you can access because they're the global<00:22:51.240> Wi-Fi<00:22:51.539> isn't<00:22:51.900> working<00:22:52.020> that<00:22:52.260> well<00:22:52.440> so 00:22:53.090 --> 00:22:53.100 align:start position:0% global Wi-Fi isn't working that well so 00:22:53.100 --> 00:22:55.190 align:start position:0% global Wi-Fi isn't working that well so yeah<00:22:53.280> we<00:22:53.520> see<00:22:53.700> that<00:22:53.820> we<00:22:54.120> have<00:22:54.240> a<00:22:54.419> Json<00:22:54.720> RPC 00:22:55.190 --> 00:22:55.200 align:start position:0% yeah we see that we have a Json RPC 00:22:55.200 --> 00:22:56.810 align:start position:0% yeah we see that we have a Json RPC server<00:22:55.559> started<00:22:55.919> because<00:22:56.100> we<00:22:56.340> started<00:22:56.640> you 00:22:56.810 --> 00:22:56.820 align:start position:0% server started because we started you 00:22:56.820 --> 00:22:58.850 align:start position:0% server started because we started you know<00:22:57.000> our<00:22:57.059> client<00:22:57.299> with<00:22:57.539> the<00:22:57.659> RPC<00:22:58.200> RPC<00:22:58.679> engine 00:22:58.850 --> 00:22:58.860 align:start position:0% know our client with the RPC RPC engine 00:22:58.860 --> 00:23:01.669 align:start position:0% know our client with the RPC RPC engine in<00:22:59.280> giant<00:22:59.580> flag<00:22:59.760> we<00:23:00.720> have<00:23:00.840> a<00:23:00.960> Genesis<00:23:01.320> that 00:23:01.669 --> 00:23:01.679 align:start position:0% in giant flag we have a Genesis that 00:23:01.679 --> 00:23:03.890 align:start position:0% in giant flag we have a Genesis that we've<00:23:01.919> specified<00:23:02.460> and<00:23:02.880> the<00:23:03.120> data<00:23:03.480> directory 00:23:03.890 --> 00:23:03.900 align:start position:0% we've specified and the data directory 00:23:03.900 --> 00:23:06.470 align:start position:0% we've specified and the data directory is<00:23:04.080> ethereum.js<00:23:04.860> which<00:23:05.159> we've<00:23:05.460> just<00:23:05.700> created 00:23:06.470 --> 00:23:06.480 align:start position:0% is ethereum.js which we've just created 00:23:06.480 --> 00:23:10.730 align:start position:0% is ethereum.js which we've just created so<00:23:06.840> that's<00:23:07.080> pretty<00:23:07.580> uh<00:23:08.580> fairly<00:23:08.940> simple<00:23:09.179> so<00:23:10.140> by 00:23:10.730 --> 00:23:10.740 align:start position:0% so that's pretty uh fairly simple so by 00:23:10.740 --> 00:23:13.130 align:start position:0% so that's pretty uh fairly simple so by default<00:23:11.159> when<00:23:11.520> you<00:23:11.880> run<00:23:12.179> the<00:23:12.419> ethereum<00:23:12.780> JS 00:23:13.130 --> 00:23:13.140 align:start position:0% default when you run the ethereum JS 00:23:13.140 --> 00:23:15.110 align:start position:0% default when you run the ethereum JS client<00:23:13.440> it's<00:23:13.679> gonna<00:23:13.919> consider<00:23:14.700> that<00:23:14.940> the 00:23:15.110 --> 00:23:15.120 align:start position:0% client it's gonna consider that the 00:23:15.120 --> 00:23:16.970 align:start position:0% client it's gonna consider that the merge<00:23:15.419> hard<00:23:15.600> Fork<00:23:16.080> has<00:23:16.380> been<00:23:16.620> activated 00:23:16.970 --> 00:23:16.980 align:start position:0% merge hard Fork has been activated 00:23:16.980 --> 00:23:18.770 align:start position:0% merge hard Fork has been activated because<00:23:17.220> we've<00:23:17.700> specified<00:23:18.120> you<00:23:18.600> know<00:23:18.659> a 00:23:18.770 --> 00:23:18.780 align:start position:0% because we've specified you know a 00:23:18.780 --> 00:23:21.470 align:start position:0% because we've specified you know a Genesis<00:23:19.320> after<00:23:20.100> that<00:23:20.340> so<00:23:20.640> at<00:23:20.760> the<00:23:20.880> moment<00:23:21.059> it's 00:23:21.470 --> 00:23:21.480 align:start position:0% Genesis after that so at the moment it's 00:23:21.480 --> 00:23:23.330 align:start position:0% Genesis after that so at the moment it's just<00:23:21.659> waiting<00:23:22.080> for<00:23:22.380> a<00:23:22.559> consensus<00:23:22.980> layer 00:23:23.330 --> 00:23:23.340 align:start position:0% just waiting for a consensus layer 00:23:23.340 --> 00:23:24.890 align:start position:0% just waiting for a consensus layer client<00:23:23.820> connection<00:23:24.000> without<00:23:24.480> that<00:23:24.780> it's 00:23:24.890 --> 00:23:24.900 align:start position:0% client connection without that it's 00:23:24.900 --> 00:23:26.750 align:start position:0% client connection without that it's going<00:23:25.140> to<00:23:25.200> be<00:23:25.320> not<00:23:25.740> going<00:23:25.860> to<00:23:25.980> be<00:23:26.100> able<00:23:26.220> to<00:23:26.340> you 00:23:26.750 --> 00:23:26.760 align:start position:0% going to be not going to be able to you 00:23:26.760 --> 00:23:28.310 align:start position:0% going to be not going to be able to you know<00:23:26.820> obviously<00:23:27.179> execute<00:23:27.840> blocks<00:23:28.140> because 00:23:28.310 --> 00:23:28.320 align:start position:0% know obviously execute blocks because 00:23:28.320 --> 00:23:31.010 align:start position:0% know obviously execute blocks because it's<00:23:28.500> not<00:23:28.740> getting<00:23:28.980> getting<00:23:29.580> any<00:23:29.940> so<00:23:30.659> this<00:23:30.900> is 00:23:31.010 --> 00:23:31.020 align:start position:0% it's not getting getting any so this is 00:23:31.020 --> 00:23:33.470 align:start position:0% it's not getting getting any so this is exactly<00:23:31.380> what<00:23:31.980> we're<00:23:32.400> gonna<00:23:32.640> do<00:23:32.940> we're<00:23:33.299> gonna 00:23:33.470 --> 00:23:33.480 align:start position:0% exactly what we're gonna do we're gonna 00:23:33.480 --> 00:23:35.990 align:start position:0% exactly what we're gonna do we're gonna start<00:23:34.260> the<00:23:34.799> load<00:23:35.100> star 00:23:35.990 --> 00:23:36.000 align:start position:0% start the load star 00:23:36.000 --> 00:23:38.390 align:start position:0% start the load star uh<00:23:36.659> consensus<00:23:37.200> client 00:23:38.390 --> 00:23:38.400 align:start position:0% uh consensus client 00:23:38.400 --> 00:23:40.669 align:start position:0% uh consensus client so<00:23:39.179> the<00:23:39.539> the<00:23:39.659> first<00:23:39.900> thing<00:23:40.080> we<00:23:40.200> need<00:23:40.320> to<00:23:40.440> do<00:23:40.559> is 00:23:40.669 --> 00:23:40.679 align:start position:0% so the the first thing we need to do is 00:23:40.679 --> 00:23:42.350 align:start position:0% so the the first thing we need to do is we're<00:23:40.860> going<00:23:41.039> to<00:23:41.159> need<00:23:41.280> to<00:23:41.640> specify<00:23:42.120> the 00:23:42.350 --> 00:23:42.360 align:start position:0% we're going to need to specify the 00:23:42.360 --> 00:23:45.770 align:start position:0% we're going to need to specify the Genesis<00:23:42.780> hash<00:23:43.200> to<00:23:43.799> the<00:23:44.520> um<00:23:44.580> to<00:23:45.120> the<00:23:45.240> consensus 00:23:45.770 --> 00:23:45.780 align:start position:0% Genesis hash to the um to the consensus 00:23:45.780 --> 00:23:48.590 align:start position:0% Genesis hash to the um to the consensus uh<00:23:46.380> layer<00:23:46.679> client<00:23:46.980> so<00:23:47.580> to<00:23:47.760> that<00:23:48.059> to<00:23:48.360> do<00:23:48.480> that 00:23:48.590 --> 00:23:48.600 align:start position:0% uh layer client so to that to do that 00:23:48.600 --> 00:23:50.750 align:start position:0% uh layer client so to that to do that I'm<00:23:48.900> actually<00:23:49.080> going<00:23:49.320> to<00:23:49.559> bring<00:23:49.860> up<00:23:50.100> you<00:23:50.640> know 00:23:50.750 --> 00:23:50.760 align:start position:0% I'm actually going to bring up you know 00:23:50.760 --> 00:23:53.289 align:start position:0% I'm actually going to bring up you know inferior<00:23:51.419> and<00:23:52.260> we're<00:23:52.440> just<00:23:52.620> going<00:23:52.740> to<00:23:52.860> query 00:23:53.289 --> 00:23:53.299 align:start position:0% inferior and we're just going to query 00:23:53.299 --> 00:23:56.750 align:start position:0% inferior and we're just going to query uh<00:23:54.299> the<00:23:54.600> hash<00:23:54.780> of<00:23:55.080> the<00:23:55.320> uh<00:23:56.100> I'm<00:23:56.400> not<00:23:56.520> going<00:23:56.700> to 00:23:56.750 --> 00:23:56.760 align:start position:0% uh the hash of the uh I'm not going to 00:23:56.760 --> 00:23:58.310 align:start position:0% uh the hash of the uh I'm not going to bring<00:23:56.880> up<00:23:57.000> info<00:23:57.419> actually<00:23:57.539> I'm<00:23:57.780> just<00:23:57.960> going<00:23:58.080> to 00:23:58.310 --> 00:23:58.320 align:start position:0% bring up info actually I'm just going to 00:23:58.320 --> 00:24:03.289 align:start position:0% bring up info actually I'm just going to query<00:23:58.740> uh<00:23:59.580> the<00:24:00.120> local<00:24:00.559> RPC<00:24:01.640> that<00:24:02.640> we<00:24:02.820> we've 00:24:03.289 --> 00:24:03.299 align:start position:0% query uh the local RPC that we we've 00:24:03.299 --> 00:24:07.370 align:start position:0% query uh the local RPC that we we've seen<00:24:03.480> specified<00:24:04.260> here<00:24:04.860> you<00:24:05.220> see<00:24:05.840> somewhere<00:24:06.840> up 00:24:07.370 --> 00:24:07.380 align:start position:0% seen specified here you see somewhere up 00:24:07.380 --> 00:24:08.690 align:start position:0% seen specified here you see somewhere up here 00:24:08.690 --> 00:24:08.700 align:start position:0% here 00:24:08.700 --> 00:24:13.490 align:start position:0% here start<00:24:09.179> Json<00:24:09.600> RPC<00:24:10.140> server<00:24:10.500> localhost<00:24:11.220> 8545 00:24:13.490 --> 00:24:13.500 align:start position:0% start Json RPC server localhost 8545 00:24:13.500 --> 00:24:15.470 align:start position:0% start Json RPC server localhost 8545 so<00:24:13.799> I'm<00:24:13.919> just<00:24:14.039> going<00:24:14.159> to<00:24:14.280> do<00:24:14.400> this<00:24:14.580> is<00:24:14.820> just<00:24:15.179> a 00:24:15.470 --> 00:24:15.480 align:start position:0% so I'm just going to do this is just a 00:24:15.480 --> 00:24:19.669 align:start position:0% so I'm just going to do this is just a tooling<00:24:16.200> to<00:24:16.559> like<00:24:16.799> visualize 00:24:19.669 --> 00:24:19.679 align:start position:0% 00:24:19.679 --> 00:24:22.430 align:start position:0% you<00:24:20.159> know<00:24:20.220> requests<00:24:20.880> a<00:24:21.480> bit<00:24:21.600> better<00:24:21.840> so<00:24:22.260> let's 00:24:22.430 --> 00:24:22.440 align:start position:0% you know requests a bit better so let's 00:24:22.440 --> 00:24:25.850 align:start position:0% you know requests a bit better so let's see<00:24:22.679> if<00:24:22.799> I<00:24:23.039> can<00:24:23.299> recall<00:24:24.299> how<00:24:25.020> to<00:24:25.080> do<00:24:25.320> that<00:24:25.500> by 00:24:25.850 --> 00:24:25.860 align:start position:0% see if I can recall how to do that by 00:24:25.860 --> 00:24:28.370 align:start position:0% see if I can recall how to do that by heart<00:24:26.280> we'll<00:24:27.059> see<00:24:27.299> so<00:24:27.960> we're<00:24:28.080> just<00:24:28.200> going<00:24:28.320> to 00:24:28.370 --> 00:24:28.380 align:start position:0% heart we'll see so we're just going to 00:24:28.380 --> 00:24:31.190 align:start position:0% heart we'll see so we're just going to send<00:24:28.559> a<00:24:28.740> standard<00:24:29.039> like<00:24:29.220> Json<00:24:29.640> RPC<00:24:30.299> request<00:24:30.840> to 00:24:31.190 --> 00:24:31.200 align:start position:0% send a standard like Json RPC request to 00:24:31.200 --> 00:24:33.529 align:start position:0% send a standard like Json RPC request to get<00:24:31.380> the<00:24:31.620> data<00:24:32.039> of<00:24:32.340> the<00:24:32.580> you<00:24:33.120> know<00:24:33.240> the<00:24:33.419> very 00:24:33.529 --> 00:24:33.539 align:start position:0% get the data of the you know the very 00:24:33.539 --> 00:24:35.529 align:start position:0% get the data of the you know the very first<00:24:33.780> block<00:24:34.020> in<00:24:34.320> that<00:24:34.559> you<00:24:34.860> know 00:24:35.529 --> 00:24:35.539 align:start position:0% first block in that you know 00:24:35.539 --> 00:24:37.090 align:start position:0% first block in that you know exit 00:24:37.090 --> 00:24:37.100 align:start position:0% exit 00:24:37.100 --> 00:24:42.230 align:start position:0% exit execution<00:24:38.100> client<00:24:39.059> state<00:24:39.620> so<00:24:40.620> method 00:24:42.230 --> 00:24:42.240 align:start position:0% execution client state so method 00:24:42.240 --> 00:24:44.750 align:start position:0% execution client state so method then<00:24:42.840> is<00:24:43.140> going<00:24:43.320> to<00:24:43.380> be<00:24:43.500> what<00:24:43.740> is<00:24:43.919> it<00:24:44.039> it's<00:24:44.400> eat 00:24:44.750 --> 00:24:44.760 align:start position:0% then is going to be what is it it's eat 00:24:44.760 --> 00:24:48.710 align:start position:0% then is going to be what is it it's eat get<00:24:45.179> blocked<00:24:45.780> by<00:24:46.020> number 00:24:48.710 --> 00:24:48.720 align:start position:0% 00:24:48.720 --> 00:24:51.230 align:start position:0% and<00:24:49.260> if<00:24:49.380> you<00:24:49.559> see<00:24:49.740> me<00:24:49.860> make<00:24:50.100> a<00:24:50.280> title<00:24:50.700> be<00:24:51.000> sure 00:24:51.230 --> 00:24:51.240 align:start position:0% and if you see me make a title be sure 00:24:51.240 --> 00:24:53.450 align:start position:0% and if you see me make a title be sure to<00:24:51.419> point<00:24:51.720> it<00:24:51.900> out<00:24:52.080> so<00:24:52.380> that<00:24:52.559> we<00:24:52.740> don't<00:24:52.919> break 00:24:53.450 --> 00:24:53.460 align:start position:0% to point it out so that we don't break 00:24:53.460 --> 00:24:55.490 align:start position:0% to point it out so that we don't break our<00:24:53.880> execution<00:24:54.299> live<00:24:54.480> client<00:24:54.840> by<00:24:55.080> sending<00:24:55.380> him 00:24:55.490 --> 00:24:55.500 align:start position:0% our execution live client by sending him 00:24:55.500 --> 00:24:57.649 align:start position:0% our execution live client by sending him like<00:24:55.740> bad<00:24:55.980> stuff 00:24:57.649 --> 00:24:57.659 align:start position:0% like bad stuff 00:24:57.659 --> 00:25:00.409 align:start position:0% like bad stuff and<00:24:58.740> um<00:24:58.740> so<00:24:59.280> we're<00:24:59.520> just<00:24:59.700> going<00:24:59.820> to<00:24:59.940> specify 00:25:00.409 --> 00:25:00.419 align:start position:0% and um so we're just going to specify 00:25:00.419 --> 00:25:02.270 align:start position:0% and um so we're just going to specify you<00:25:00.780> know<00:25:00.900> the<00:25:01.140> very<00:25:01.380> first<00:25:01.559> block<00:25:01.860> we<00:25:02.100> could 00:25:02.270 --> 00:25:02.280 align:start position:0% you know the very first block we could 00:25:02.280 --> 00:25:05.350 align:start position:0% you know the very first block we could specify<00:25:02.760> earliest<00:25:03.600> uh<00:25:04.320> as<00:25:04.679> well 00:25:05.350 --> 00:25:05.360 align:start position:0% specify earliest uh as well 00:25:05.360 --> 00:25:07.970 align:start position:0% specify earliest uh as well uh<00:25:06.360> this<00:25:06.659> second<00:25:06.780> option<00:25:07.140> is<00:25:07.380> just<00:25:07.500> if<00:25:07.740> we<00:25:07.860> want 00:25:07.970 --> 00:25:07.980 align:start position:0% uh this second option is just if we want 00:25:07.980 --> 00:25:10.250 align:start position:0% uh this second option is just if we want the<00:25:08.159> transactions<00:25:08.700> we'll<00:25:09.120> we'll<00:25:09.480> say<00:25:09.720> yes<00:25:09.900> but 00:25:10.250 --> 00:25:10.260 align:start position:0% the transactions we'll we'll say yes but 00:25:10.260 --> 00:25:12.830 align:start position:0% the transactions we'll we'll say yes but it<00:25:10.440> doesn't<00:25:10.740> really<00:25:11.220> uh<00:25:11.700> matter<00:25:12.360> all<00:25:12.659> that 00:25:12.830 --> 00:25:12.840 align:start position:0% it doesn't really uh matter all that 00:25:12.840 --> 00:25:13.750 align:start position:0% it doesn't really uh matter all that much 00:25:13.750 --> 00:25:13.760 align:start position:0% much 00:25:13.760 --> 00:25:17.390 align:start position:0% much then<00:25:14.760> we<00:25:15.360> need<00:25:15.539> to<00:25:15.780> specify<00:25:16.320> an<00:25:16.559> ID<00:25:16.860> I<00:25:17.220> think 00:25:17.390 --> 00:25:17.400 align:start position:0% then we need to specify an ID I think 00:25:17.400 --> 00:25:19.549 align:start position:0% then we need to specify an ID I think we'll<00:25:17.700> just<00:25:17.880> go<00:25:18.059> with<00:25:18.299> one 00:25:19.549 --> 00:25:19.559 align:start position:0% we'll just go with one 00:25:19.559 --> 00:25:21.289 align:start position:0% we'll just go with one can<00:25:20.039> you<00:25:20.159> see<00:25:20.280> properly 00:25:21.289 --> 00:25:21.299 align:start position:0% can you see properly 00:25:21.299 --> 00:25:24.289 align:start position:0% can you see properly yeah<00:25:21.600> cool<00:25:22.140> big<00:25:22.440> enough<00:25:22.620> so<00:25:23.460> let's<00:25:23.580> see<00:25:23.880> if 00:25:24.289 --> 00:25:24.299 align:start position:0% yeah cool big enough so let's see if 00:25:24.299 --> 00:25:26.870 align:start position:0% yeah cool big enough so let's see if that<00:25:24.539> works<00:25:24.779> cool<00:25:25.080> yeah<00:25:25.620> so<00:25:26.100> we've<00:25:26.340> got<00:25:26.520> you 00:25:26.870 --> 00:25:26.880 align:start position:0% that works cool yeah so we've got you 00:25:26.880 --> 00:25:28.250 align:start position:0% that works cool yeah so we've got you know<00:25:26.940> the<00:25:27.120> first<00:25:27.240> Genesis<00:25:27.659> block<00:25:27.900> we<00:25:28.140> should 00:25:28.250 --> 00:25:28.260 align:start position:0% know the first Genesis block we should 00:25:28.260 --> 00:25:29.630 align:start position:0% know the first Genesis block we should expect<00:25:28.440> like<00:25:28.679> the<00:25:28.860> parent<00:25:28.980> hash<00:25:29.279> is<00:25:29.460> going<00:25:29.580> to 00:25:29.630 --> 00:25:29.640 align:start position:0% expect like the parent hash is going to 00:25:29.640 --> 00:25:33.409 align:start position:0% expect like the parent hash is going to be<00:25:29.760> zero<00:25:30.059> uh<00:25:30.840> this<00:25:31.140> is<00:25:31.260> post<00:25:31.559> uh<00:25:32.100> merge<00:25:32.940> sort<00:25:33.299> of 00:25:33.409 --> 00:25:33.419 align:start position:0% be zero uh this is post uh merge sort of 00:25:33.419 --> 00:25:36.649 align:start position:0% be zero uh this is post uh merge sort of mixed<00:25:33.659> hash<00:25:33.840> is<00:25:34.020> zero<00:25:34.380> it's<00:25:34.679> uh<00:25:35.159> it's<00:25:36.059> unused 00:25:36.649 --> 00:25:36.659 align:start position:0% mixed hash is zero it's uh it's unused 00:25:36.659 --> 00:25:39.049 align:start position:0% mixed hash is zero it's uh it's unused and<00:25:37.140> denounces<00:25:37.740> one<00:25:38.279> two<00:25:38.400> three<00:25:38.580> four<00:25:38.760> not 00:25:39.049 --> 00:25:39.059 align:start position:0% and denounces one two three four not 00:25:39.059 --> 00:25:40.730 align:start position:0% and denounces one two three four not sure<00:25:39.240> what<00:25:39.480> that<00:25:39.779> is<00:25:39.900> but<00:25:40.140> that<00:25:40.320> is<00:25:40.500> probably 00:25:40.730 --> 00:25:40.740 align:start position:0% sure what that is but that is probably 00:25:40.740 --> 00:25:43.130 align:start position:0% sure what that is but that is probably like<00:25:40.980> a<00:25:41.220> default<00:25:41.520> value<00:25:41.700> or<00:25:42.600> something<00:25:42.720> so 00:25:43.130 --> 00:25:43.140 align:start position:0% like a default value or something so 00:25:43.140 --> 00:25:45.230 align:start position:0% like a default value or something so we're<00:25:43.320> just<00:25:43.500> gonna<00:25:43.679> take<00:25:43.919> the<00:25:44.100> hash<00:25:44.340> and<00:25:45.000> uh 00:25:45.230 --> 00:25:45.240 align:start position:0% we're just gonna take the hash and uh 00:25:45.240 --> 00:25:47.029 align:start position:0% we're just gonna take the hash and uh yeah<00:25:45.600> we're<00:25:45.840> just<00:25:46.080> gonna<00:25:46.200> copy<00:25:46.559> and<00:25:46.679> paste 00:25:47.029 --> 00:25:47.039 align:start position:0% yeah we're just gonna copy and paste 00:25:47.039 --> 00:25:48.590 align:start position:0% yeah we're just gonna copy and paste that 00:25:48.590 --> 00:25:48.600 align:start position:0% that 00:25:48.600 --> 00:25:51.049 align:start position:0% that so<00:25:49.380> then<00:25:49.799> the<00:25:50.220> only<00:25:50.340> other<00:25:50.520> thing<00:25:50.760> that<00:25:50.940> we 00:25:51.049 --> 00:25:51.059 align:start position:0% so then the only other thing that we 00:25:51.059 --> 00:25:52.669 align:start position:0% so then the only other thing that we need<00:25:51.179> is<00:25:51.360> we<00:25:51.600> need<00:25:51.720> to<00:25:51.900> specify<00:25:52.260> like<00:25:52.440> an 00:25:52.669 --> 00:25:52.679 align:start position:0% need is we need to specify like an 00:25:52.679 --> 00:25:55.370 align:start position:0% need is we need to specify like an initial<00:25:52.980> like<00:25:53.400> timestamp<00:25:53.820> so<00:25:54.000> I'm<00:25:54.120> just<00:25:54.299> gonna 00:25:55.370 --> 00:25:55.380 align:start position:0% initial like timestamp so I'm just gonna 00:25:55.380 --> 00:26:00.110 align:start position:0% initial like timestamp so I'm just gonna quickly 00:26:00.110 --> 00:26:00.120 align:start position:0% 00:26:00.120 --> 00:26:02.750 align:start position:0% get<00:26:00.720> the<00:26:00.900> timestamp<00:26:01.380> like<00:26:01.799> in<00:26:02.039> seconds<00:26:02.220> and 00:26:02.750 --> 00:26:02.760 align:start position:0% get the timestamp like in seconds and 00:26:02.760 --> 00:26:05.149 align:start position:0% get the timestamp like in seconds and we're<00:26:02.880> gonna<00:26:03.059> add<00:26:03.240> like<00:26:03.600> a<00:26:04.440> few<00:26:04.740> like<00:26:04.980> seconds 00:26:05.149 --> 00:26:05.159 align:start position:0% we're gonna add like a few like seconds 00:26:05.159 --> 00:26:07.010 align:start position:0% we're gonna add like a few like seconds to<00:26:05.400> that<00:26:05.580> when<00:26:05.760> we<00:26:05.940> do<00:26:06.059> that<00:26:06.240> you<00:26:06.539> know<00:26:06.659> right 00:26:07.010 --> 00:26:07.020 align:start position:0% to that when we do that you know right 00:26:07.020 --> 00:26:08.330 align:start position:0% to that when we do that you know right after 00:26:08.330 --> 00:26:08.340 align:start position:0% after 00:26:08.340 --> 00:26:11.450 align:start position:0% after so<00:26:09.000> I'm<00:26:09.539> gonna 00:26:11.450 --> 00:26:11.460 align:start position:0% so I'm gonna 00:26:11.460 --> 00:26:15.890 align:start position:0% so I'm gonna start<00:26:12.059> the<00:26:12.360> consensus<00:26:12.779> client<00:26:13.500> here<00:26:13.679> and 00:26:15.890 --> 00:26:15.900 align:start position:0% start the consensus client here and 00:26:15.900 --> 00:26:17.750 align:start position:0% start the consensus client here and this<00:26:16.320> is<00:26:16.380> a<00:26:16.559> fairly<00:26:16.860> you<00:26:17.159> know<00:26:17.220> long<00:26:17.400> command 00:26:17.750 --> 00:26:17.760 align:start position:0% this is a fairly you know long command 00:26:17.760 --> 00:26:19.549 align:start position:0% this is a fairly you know long command it's<00:26:17.880> running<00:26:18.120> with<00:26:18.659> Docker<00:26:19.260> like<00:26:19.380> I've 00:26:19.549 --> 00:26:19.559 align:start position:0% it's running with Docker like I've 00:26:19.559 --> 00:26:21.110 align:start position:0% it's running with Docker like I've already<00:26:19.740> installed<00:26:20.340> Little<00:26:20.640> Star<00:26:20.820> in<00:26:21.000> my 00:26:21.110 --> 00:26:21.120 align:start position:0% already installed Little Star in my 00:26:21.120 --> 00:26:23.029 align:start position:0% already installed Little Star in my machine<00:26:21.299> I<00:26:21.600> didn't<00:26:21.720> want<00:26:21.900> to<00:26:22.020> do<00:26:22.140> that<00:26:22.320> you 00:26:23.029 --> 00:26:23.039 align:start position:0% machine I didn't want to do that you 00:26:23.039 --> 00:26:24.710 align:start position:0% machine I didn't want to do that you know<00:26:23.159> here<00:26:23.340> but<00:26:23.640> we<00:26:23.820> can<00:26:24.000> help<00:26:24.179> you<00:26:24.360> you<00:26:24.539> know 00:26:24.710 --> 00:26:24.720 align:start position:0% know here but we can help you you know 00:26:24.720 --> 00:26:26.570 align:start position:0% know here but we can help you you know set<00:26:24.900> that<00:26:25.080> up<00:26:25.200> later<00:26:25.440> if<00:26:25.740> that's<00:26:26.039> what<00:26:26.460> you 00:26:26.570 --> 00:26:26.580 align:start position:0% set that up later if that's what you 00:26:26.580 --> 00:26:28.190 align:start position:0% set that up later if that's what you want<00:26:26.700> to<00:26:26.820> do<00:26:26.880> so<00:26:27.419> all<00:26:27.600> that<00:26:27.779> we're<00:26:27.960> going<00:26:28.080> to 00:26:28.190 --> 00:26:28.200 align:start position:0% want to do so all that we're going to 00:26:28.200 --> 00:26:30.289 align:start position:0% want to do so all that we're going to need<00:26:28.320> to<00:26:28.740> specify<00:26:29.340> is<00:26:29.640> we're<00:26:29.820> going<00:26:30.059> to<00:26:30.179> need 00:26:30.289 --> 00:26:30.299 align:start position:0% need to specify is we're going to need 00:26:30.299 --> 00:26:33.950 align:start position:0% need to specify is we're going to need to<00:26:30.480> specify<00:26:30.840> the<00:26:31.140> Genesis<00:26:31.679> eat<00:26:32.400> one<00:26:32.640> hash<00:26:33.000> and 00:26:33.950 --> 00:26:33.960 align:start position:0% to specify the Genesis eat one hash and 00:26:33.960 --> 00:26:35.870 align:start position:0% to specify the Genesis eat one hash and we<00:26:34.380> actually<00:26:34.620> have<00:26:34.919> that 00:26:35.870 --> 00:26:35.880 align:start position:0% we actually have that 00:26:35.880 --> 00:26:39.529 align:start position:0% we actually have that from<00:26:36.539> here 00:26:39.529 --> 00:26:39.539 align:start position:0% 00:26:39.539 --> 00:26:42.169 align:start position:0% so<00:26:40.020> we're<00:26:40.320> pasting 00:26:42.169 --> 00:26:42.179 align:start position:0% so we're pasting 00:26:42.179 --> 00:26:44.510 align:start position:0% so we're pasting that 00:26:44.510 --> 00:26:44.520 align:start position:0% that 00:26:44.520 --> 00:26:48.549 align:start position:0% that and<00:26:45.120> then<00:26:45.299> we<00:26:45.600> are<00:26:45.720> going<00:26:45.900> to<00:26:46.020> specify<00:26:46.559> a 00:26:48.549 --> 00:26:48.559 align:start position:0% and then we are going to specify a 00:26:48.559 --> 00:26:51.169 align:start position:0% and then we are going to specify a Genesis<00:26:49.559> time 00:26:51.169 --> 00:26:51.179 align:start position:0% Genesis time 00:26:51.179 --> 00:26:53.149 align:start position:0% Genesis time which<00:26:51.480> is<00:26:51.600> going<00:26:51.779> to<00:26:51.960> be<00:26:52.020> that<00:26:52.559> and<00:26:52.799> I'm<00:26:53.039> going 00:26:53.149 --> 00:26:53.159 align:start position:0% which is going to be that and I'm going 00:26:53.159 --> 00:26:56.450 align:start position:0% which is going to be that and I'm going to<00:26:53.220> add 00:26:56.450 --> 00:26:56.460 align:start position:0% 00:26:56.460 --> 00:26:57.890 align:start position:0% a<00:26:56.520> number<00:26:56.880> of 00:26:57.890 --> 00:26:57.900 align:start position:0% a number of 00:26:57.900 --> 00:27:01.490 align:start position:0% a number of seconds<00:26:58.200> to<00:26:58.559> it 00:27:01.490 --> 00:27:01.500 align:start position:0% 00:27:01.500 --> 00:27:03.529 align:start position:0% so<00:27:02.159> let's<00:27:02.340> see<00:27:02.520> if<00:27:02.580> this<00:27:02.760> works<00:27:03.059> so<00:27:03.179> we<00:27:03.360> should 00:27:03.529 --> 00:27:03.539 align:start position:0% so let's see if this works so we should 00:27:03.539 --> 00:27:06.769 align:start position:0% so let's see if this works so we should eventually<00:27:04.080> start<00:27:04.440> you<00:27:04.980> know<00:27:05.179> producing<00:27:06.179> uh 00:27:06.769 --> 00:27:06.779 align:start position:0% eventually start you know producing uh 00:27:06.779 --> 00:27:09.350 align:start position:0% eventually start you know producing uh blocks<00:27:07.320> oh<00:27:07.980> we<00:27:08.220> see<00:27:08.340> publishblock<00:27:08.880> that<00:27:09.059> looks 00:27:09.350 --> 00:27:09.360 align:start position:0% blocks oh we see publishblock that looks 00:27:09.360 --> 00:27:11.510 align:start position:0% blocks oh we see publishblock that looks pretty<00:27:09.539> good<00:27:09.720> and<00:27:10.559> then<00:27:10.620> if<00:27:10.799> we<00:27:10.980> go<00:27:11.159> back<00:27:11.340> to 00:27:11.510 --> 00:27:11.520 align:start position:0% pretty good and then if we go back to 00:27:11.520 --> 00:27:13.130 align:start position:0% pretty good and then if we go back to the<00:27:11.700> execution<00:27:12.059> layer<00:27:12.419> client<00:27:12.720> it<00:27:12.960> should 00:27:13.130 --> 00:27:13.140 align:start position:0% the execution layer client it should 00:27:13.140 --> 00:27:15.250 align:start position:0% the execution layer client it should have<00:27:13.320> picked<00:27:13.679> up<00:27:13.799> on<00:27:14.039> you<00:27:14.220> know<00:27:14.340> the<00:27:14.520> consensus 00:27:15.250 --> 00:27:15.260 align:start position:0% have picked up on you know the consensus 00:27:15.260 --> 00:27:17.570 align:start position:0% have picked up on you know the consensus client<00:27:16.260> starting<00:27:16.500> to<00:27:16.740> run<00:27:16.799> producing<00:27:17.279> blocks 00:27:17.570 --> 00:27:17.580 align:start position:0% client starting to run producing blocks 00:27:17.580 --> 00:27:20.870 align:start position:0% client starting to run producing blocks sending<00:27:18.000> them<00:27:18.179> back<00:27:19.020> to<00:27:19.919> it 00:27:20.870 --> 00:27:20.880 align:start position:0% sending them back to it 00:27:20.880 --> 00:27:24.169 align:start position:0% sending them back to it so<00:27:21.600> let's<00:27:21.960> see<00:27:22.260> if<00:27:22.740> we<00:27:22.919> yeah<00:27:23.279> it's<00:27:23.820> uh 00:27:24.169 --> 00:27:24.179 align:start position:0% so let's see if we yeah it's uh 00:27:24.179 --> 00:27:26.630 align:start position:0% so let's see if we yeah it's uh assembling<00:27:24.600> blocks<00:27:24.900> build<00:27:25.140> block<00:27:25.440> that<00:27:26.400> looks 00:27:26.630 --> 00:27:26.640 align:start position:0% assembling blocks build block that looks 00:27:26.640 --> 00:27:30.049 align:start position:0% assembling blocks build block that looks perfect<00:27:26.760> so<00:27:27.299> we<00:27:27.720> we<00:27:28.080> are<00:27:28.320> seeing<00:27:28.740> that<00:27:29.100> uh<00:27:29.400> we 00:27:30.049 --> 00:27:30.059 align:start position:0% perfect so we we are seeing that uh we 00:27:30.059 --> 00:27:31.789 align:start position:0% perfect so we we are seeing that uh we have<00:27:30.179> a<00:27:30.299> local<00:27:30.419> shangdong<00:27:31.380> blockchain 00:27:31.789 --> 00:27:31.799 align:start position:0% have a local shangdong blockchain 00:27:31.799 --> 00:27:34.789 align:start position:0% have a local shangdong blockchain running<00:27:32.039> with<00:27:32.460> a<00:27:32.640> bunch<00:27:32.820> of<00:27:33.000> newer<00:27:33.480> eips 00:27:34.789 --> 00:27:34.799 align:start position:0% running with a bunch of newer eips 00:27:34.799 --> 00:27:38.090 align:start position:0% running with a bunch of newer eips now<00:27:35.159> one<00:27:35.460> thing<00:27:35.700> we<00:27:36.419> can<00:27:36.539> do<00:27:36.779> we<00:27:37.200> have<00:27:37.380> a<00:27:37.740> test 00:27:38.090 --> 00:27:38.100 align:start position:0% now one thing we can do we have a test 00:27:38.100 --> 00:27:40.789 align:start position:0% now one thing we can do we have a test Suite<00:27:38.580> I<00:27:38.940> think<00:27:39.120> for 00:27:40.789 --> 00:27:40.799 align:start position:0% Suite I think for 00:27:40.799 --> 00:27:43.010 align:start position:0% Suite I think for like<00:27:41.159> it's 00:27:43.010 --> 00:27:43.020 align:start position:0% like it's 00:27:43.020 --> 00:27:45.110 align:start position:0% like it's so<00:27:43.380> we<00:27:43.500> have<00:27:43.620> a<00:27:43.740> bunch<00:27:43.860> of<00:27:43.980> tests<00:27:44.340> here 00:27:45.110 --> 00:27:45.120 align:start position:0% so we have a bunch of tests here 00:27:45.120 --> 00:27:47.510 align:start position:0% so we have a bunch of tests here that<00:27:45.539> we<00:27:45.720> can<00:27:45.779> run<00:27:46.020> to<00:27:46.380> see<00:27:46.559> if<00:27:46.919> the<00:27:47.100> you<00:27:47.400> know 00:27:47.510 --> 00:27:47.520 align:start position:0% that we can run to see if the you know 00:27:47.520 --> 00:27:51.049 align:start position:0% that we can run to see if the you know eips<00:27:47.880> have<00:27:48.299> been<00:27:48.480> properly<00:27:49.159> implemented<00:27:50.159> so<00:27:50.880> I 00:27:51.049 --> 00:27:51.059 align:start position:0% eips have been properly implemented so I 00:27:51.059 --> 00:27:52.909 align:start position:0% eips have been properly implemented so I won't<00:27:51.120> go<00:27:51.360> through<00:27:51.539> all<00:27:51.840> of<00:27:51.960> them<00:27:52.080> feel<00:27:52.740> free 00:27:52.909 --> 00:27:52.919 align:start position:0% won't go through all of them feel free 00:27:52.919 --> 00:27:56.269 align:start position:0% won't go through all of them feel free to<00:27:53.159> go<00:27:53.520> through<00:27:54.059> them<00:27:54.240> yourself<00:27:54.600> so<00:27:55.380> EIP<00:27:55.799> like 00:27:56.269 --> 00:27:56.279 align:start position:0% to go through them yourself so EIP like 00:27:56.279 --> 00:27:59.029 align:start position:0% to go through them yourself so EIP like 3670<00:27:57.179> is<00:27:57.539> a 00:27:59.029 --> 00:27:59.039 align:start position:0% 3670 is a 00:27:59.039 --> 00:28:03.409 align:start position:0% 3670 is a like<00:27:59.700> the<00:27:59.940> eof<00:28:00.620> uh<00:28:01.620> code<00:28:02.159> execution<00:28:02.640> the<00:28:03.000> code 00:28:03.409 --> 00:28:03.419 align:start position:0% like the eof uh code execution the code 00:28:03.419 --> 00:28:05.630 align:start position:0% like the eof uh code execution the code validation<00:28:03.900> so<00:28:04.200> if<00:28:04.380> you<00:28:04.500> try<00:28:04.679> to<00:28:04.799> publish<00:28:05.159> like 00:28:05.630 --> 00:28:05.640 align:start position:0% validation so if you try to publish like 00:28:05.640 --> 00:28:08.330 align:start position:0% validation so if you try to publish like a<00:28:06.000> contract<00:28:06.539> code<00:28:07.020> that<00:28:07.380> doesn't<00:28:07.740> conform<00:28:08.159> to 00:28:08.330 --> 00:28:08.340 align:start position:0% a contract code that doesn't conform to 00:28:08.340 --> 00:28:11.450 align:start position:0% a contract code that doesn't conform to the<00:28:08.640> eof<00:28:08.940> standard<00:28:09.419> it<00:28:09.840> will<00:28:09.960> get<00:28:10.260> uh<00:28:10.860> you<00:28:11.340> know 00:28:11.450 --> 00:28:11.460 align:start position:0% the eof standard it will get uh you know 00:28:11.460 --> 00:28:13.430 align:start position:0% the eof standard it will get uh you know rejected<00:28:11.940> we<00:28:12.539> have<00:28:12.659> a<00:28:12.779> bunch<00:28:12.960> of<00:28:13.080> related 00:28:13.430 --> 00:28:13.440 align:start position:0% rejected we have a bunch of related 00:28:13.440 --> 00:28:16.070 align:start position:0% rejected we have a bunch of related tests<00:28:13.980> so<00:28:14.159> we<00:28:14.580> have<00:28:14.880> uh 00:28:16.070 --> 00:28:16.080 align:start position:0% tests so we have uh 00:28:16.080 --> 00:28:19.669 align:start position:0% tests so we have uh can't<00:28:16.799> exactly<00:28:17.279> recall<00:28:17.580> what<00:28:18.179> this<00:28:18.960> one<00:28:19.140> is 00:28:19.669 --> 00:28:19.679 align:start position:0% can't exactly recall what this one is 00:28:19.679 --> 00:28:21.710 align:start position:0% can't exactly recall what this one is actually<00:28:20.220> a<00:28:20.520> bad<00:28:20.700> there 00:28:21.710 --> 00:28:21.720 align:start position:0% actually a bad there 00:28:21.720 --> 00:28:25.190 align:start position:0% actually a bad there that<00:28:22.020> label<00:28:22.440> here<00:28:22.559> just<00:28:22.860> fix<00:28:23.100> that<00:28:23.400> and 00:28:25.190 --> 00:28:25.200 align:start position:0% that label here just fix that and 00:28:25.200 --> 00:28:29.690 align:start position:0% that label here just fix that and yeah<00:28:25.799> so<00:28:26.279> we<00:28:26.640> can<00:28:26.820> try<00:28:27.080> and<00:28:28.080> see<00:28:28.260> if<00:28:28.440> we<00:28:28.620> can 00:28:29.690 --> 00:28:29.700 align:start position:0% yeah so we can try and see if we can 00:28:29.700 --> 00:28:34.909 align:start position:0% yeah so we can try and see if we can run<00:28:30.480> the<00:28:31.080> test 00:28:34.909 --> 00:28:34.919 align:start position:0% 00:28:34.919 --> 00:28:38.990 align:start position:0% I<00:28:35.340> think<00:28:35.520> it's<00:28:35.760> in<00:28:36.000> the<00:28:36.240> SIM 00:28:38.990 --> 00:28:39.000 align:start position:0% 00:28:39.000 --> 00:28:40.730 align:start position:0% all<00:28:39.419> right<00:28:39.539> so<00:28:39.840> it<00:28:39.960> should 00:28:40.730 --> 00:28:40.740 align:start position:0% all right so it should 00:28:40.740 --> 00:28:44.330 align:start position:0% all right so it should oh<00:28:41.159> I<00:28:41.279> have<00:28:41.520> to<00:28:41.700> specify<00:28:42.500> actual<00:28:43.500> run<00:28:44.100> through 00:28:44.330 --> 00:28:44.340 align:start position:0% oh I have to specify actual run through 00:28:44.340 --> 00:28:52.190 align:start position:0% oh I have to specify actual run through yeah<00:28:44.640> right 00:28:52.190 --> 00:28:52.200 align:start position:0% 00:28:52.200 --> 00:28:53.570 align:start position:0% so<00:28:52.559> this<00:28:52.679> is<00:28:52.799> going<00:28:52.980> to<00:28:53.039> interact<00:28:53.340> with<00:28:53.460> the 00:28:53.570 --> 00:28:53.580 align:start position:0% so this is going to interact with the 00:28:53.580 --> 00:28:56.269 align:start position:0% so this is going to interact with the chain<00:28:53.700> that<00:28:53.940> we<00:28:54.059> have<00:28:54.240> running<00:28:54.600> locally<00:28:55.279> and 00:28:56.269 --> 00:28:56.279 align:start position:0% chain that we have running locally and 00:28:56.279 --> 00:28:59.990 align:start position:0% chain that we have running locally and check<00:28:56.880> if<00:28:57.240> uh<00:28:57.600> everything<00:28:58.140> seems 00:28:59.990 --> 00:29:00.000 align:start position:0% check if uh everything seems 00:29:00.000 --> 00:29:01.610 align:start position:0% check if uh everything seems good<00:29:00.480> so<00:29:00.720> we've<00:29:00.960> been<00:29:01.080> able<00:29:01.260> to<00:29:01.380> make<00:29:01.500> a 00:29:01.610 --> 00:29:01.620 align:start position:0% good so we've been able to make a 00:29:01.620 --> 00:29:04.010 align:start position:0% good so we've been able to make a transfer<00:29:01.980> that's<00:29:02.880> already 00:29:04.010 --> 00:29:04.020 align:start position:0% transfer that's already 00:29:04.020 --> 00:29:05.750 align:start position:0% transfer that's already you<00:29:04.440> know<00:29:04.559> not<00:29:04.799> so<00:29:04.980> bad 00:29:05.750 --> 00:29:05.760 align:start position:0% you know not so bad 00:29:05.760 --> 00:29:09.110 align:start position:0% you know not so bad and<00:29:06.360> then<00:29:06.539> it's<00:29:06.900> going<00:29:07.080> to<00:29:07.200> test<00:29:07.380> eof<00:29:07.860> and<00:29:08.580> a 00:29:09.110 --> 00:29:09.120 align:start position:0% and then it's going to test eof and a 00:29:09.120 --> 00:29:14.570 align:start position:0% and then it's going to test eof and a couple<00:29:09.360> of<00:29:09.539> other<00:29:09.720> you<00:29:10.140> know<00:29:10.260> eips 00:29:14.570 --> 00:29:14.580 align:start position:0% 00:29:14.580 --> 00:29:16.430 align:start position:0% this<00:29:14.880> is<00:29:15.120> a<00:29:15.299> bit<00:29:15.360> slow<00:29:15.659> maybe<00:29:15.960> because<00:29:16.200> I'm 00:29:16.430 --> 00:29:16.440 align:start position:0% this is a bit slow maybe because I'm 00:29:16.440 --> 00:29:19.190 align:start position:0% this is a bit slow maybe because I'm sharing<00:29:16.799> the<00:29:16.919> stream<00:29:17.100> I'm<00:29:17.340> not<00:29:17.460> sure 00:29:19.190 --> 00:29:19.200 align:start position:0% sharing the stream I'm not sure 00:29:19.200 --> 00:29:23.690 align:start position:0% sharing the stream I'm not sure but<00:29:19.500> yeah<00:29:19.679> we<00:29:20.039> see<00:29:20.279> that<00:29:21.000> test<00:29:21.299> uh<00:29:21.840> running 00:29:23.690 --> 00:29:23.700 align:start position:0% but yeah we see that test uh running 00:29:23.700 --> 00:29:26.870 align:start position:0% but yeah we see that test uh running and<00:29:24.059> yeah<00:29:24.240> I'll<00:29:24.419> keep<00:29:24.659> that<00:29:24.779> running<00:29:25.200> while<00:29:25.740> I 00:29:26.870 --> 00:29:26.880 align:start position:0% and yeah I'll keep that running while I 00:29:26.880 --> 00:29:28.549 align:start position:0% and yeah I'll keep that running while I keep<00:29:27.240> it<00:29:27.419> up<00:29:27.539> and<00:29:27.840> go<00:29:28.200> back<00:29:28.320> to<00:29:28.440> the 00:29:28.549 --> 00:29:28.559 align:start position:0% keep it up and go back to the 00:29:28.559 --> 00:29:31.850 align:start position:0% keep it up and go back to the presentation 00:29:31.850 --> 00:29:31.860 align:start position:0% 00:29:31.860 --> 00:29:35.210 align:start position:0% slideshow 00:29:35.210 --> 00:29:35.220 align:start position:0% 00:29:35.220 --> 00:29:39.649 align:start position:0% it's<00:29:35.640> all<00:29:35.760> right 00:29:39.649 --> 00:29:39.659 align:start position:0% 00:29:39.659 --> 00:29:42.769 align:start position:0% all<00:29:40.440> right<00:29:40.679> so<00:29:41.039> this<00:29:41.340> is<00:29:41.520> a<00:29:41.880> where<00:29:42.539> we're<00:29:42.659> going 00:29:42.769 --> 00:29:42.779 align:start position:0% all right so this is a where we're going 00:29:42.779 --> 00:29:45.169 align:start position:0% all right so this is a where we're going to<00:29:42.840> start<00:29:43.020> like<00:29:43.260> the<00:29:43.559> more<00:29:43.799> interactive<00:29:44.580> and<00:29:45.000> I 00:29:45.169 --> 00:29:45.179 align:start position:0% to start like the more interactive and I 00:29:45.179 --> 00:29:46.789 align:start position:0% to start like the more interactive and I feel<00:29:45.299> like<00:29:45.419> interesting<00:29:45.960> part<00:29:46.200> of<00:29:46.559> this 00:29:46.789 --> 00:29:46.799 align:start position:0% feel like interesting part of this 00:29:46.799 --> 00:29:50.029 align:start position:0% feel like interesting part of this Workshop<00:29:47.720> where<00:29:48.720> I<00:29:49.140> mean<00:29:49.260> we<00:29:49.500> encourage<00:29:49.860> you 00:29:50.029 --> 00:29:50.039 align:start position:0% Workshop where I mean we encourage you 00:29:50.039 --> 00:29:52.190 align:start position:0% Workshop where I mean we encourage you like<00:29:50.340> to<00:29:50.520> bring<00:29:50.760> actually<00:29:51.240> your<00:29:51.600> laptop<00:29:51.960> style 00:29:52.190 --> 00:29:52.200 align:start position:0% like to bring actually your laptop style 00:29:52.200 --> 00:29:54.230 align:start position:0% like to bring actually your laptop style and<00:29:52.740> if<00:29:52.860> you<00:29:53.039> have<00:29:53.220> if<00:29:53.640> you<00:29:53.820> don't<00:29:53.940> have<00:29:54.120> a 00:29:54.230 --> 00:29:54.240 align:start position:0% and if you have if you don't have a 00:29:54.240 --> 00:29:55.850 align:start position:0% and if you have if you don't have a laptop<00:29:54.539> or<00:29:54.899> you<00:29:55.020> don't<00:29:55.140> feel<00:29:55.320> like<00:29:55.500> you<00:29:55.799> know 00:29:55.850 --> 00:29:55.860 align:start position:0% laptop or you don't feel like you know 00:29:55.860 --> 00:29:58.190 align:start position:0% laptop or you don't feel like you know coding<00:29:56.399> yourself<00:29:56.580> I<00:29:57.480> would<00:29:57.600> really<00:29:57.779> encourage 00:29:58.190 --> 00:29:58.200 align:start position:0% coding yourself I would really encourage 00:29:58.200 --> 00:30:00.529 align:start position:0% coding yourself I would really encourage you<00:29:58.320> like<00:29:58.559> to<00:29:58.919> to<00:29:59.220> meet<00:29:59.820> up<00:30:00.000> with<00:30:00.120> someone<00:30:00.299> or 00:30:00.529 --> 00:30:00.539 align:start position:0% you like to to meet up with someone or 00:30:00.539 --> 00:30:02.690 align:start position:0% you like to to meet up with someone or to<00:30:00.720> pair<00:30:00.840> with<00:30:01.080> someone<00:30:01.320> who<00:30:01.740> actually<00:30:01.860> has<00:30:02.340> a 00:30:02.690 --> 00:30:02.700 align:start position:0% to pair with someone who actually has a 00:30:02.700 --> 00:30:05.510 align:start position:0% to pair with someone who actually has a a<00:30:03.419> laptop<00:30:03.960> going<00:30:04.200> because<00:30:04.980> I<00:30:05.220> feel<00:30:05.340> like 00:30:05.510 --> 00:30:05.520 align:start position:0% a laptop going because I feel like 00:30:05.520 --> 00:30:06.769 align:start position:0% a laptop going because I feel like that's<00:30:05.880> probably<00:30:06.059> going<00:30:06.240> to<00:30:06.360> be<00:30:06.419> the<00:30:06.539> best<00:30:06.659> way 00:30:06.769 --> 00:30:06.779 align:start position:0% that's probably going to be the best way 00:30:06.779 --> 00:30:09.110 align:start position:0% that's probably going to be the best way that<00:30:07.080> you<00:30:07.260> can<00:30:07.440> we<00:30:08.039> can<00:30:08.220> show<00:30:08.340> you<00:30:08.520> about<00:30:08.700> the 00:30:09.110 --> 00:30:09.120 align:start position:0% that you can we can show you about the 00:30:09.120 --> 00:30:11.149 align:start position:0% that you can we can show you about the mono<00:30:09.419> repo<00:30:09.779> and<00:30:10.140> if<00:30:10.260> people<00:30:10.440> have<00:30:10.799> like 00:30:11.149 --> 00:30:11.159 align:start position:0% mono repo and if people have like 00:30:11.159 --> 00:30:13.430 align:start position:0% mono repo and if people have like different<00:30:11.340> degrees<00:30:11.580> of<00:30:12.059> uh<00:30:12.480> of<00:30:12.840> skill<00:30:13.080> levels 00:30:13.430 --> 00:30:13.440 align:start position:0% different degrees of uh of skill levels 00:30:13.440 --> 00:30:15.889 align:start position:0% different degrees of uh of skill levels or<00:30:13.620> familiarity<00:30:14.220> with<00:30:14.520> like<00:30:14.640> blockchain<00:30:15.299> in 00:30:15.889 --> 00:30:15.899 align:start position:0% or familiarity with like blockchain in 00:30:15.899 --> 00:30:17.990 align:start position:0% or familiarity with like blockchain in general<00:30:16.080> we<00:30:16.919> have<00:30:17.100> a<00:30:17.580> couple<00:30:17.700> of<00:30:17.820> like 00:30:17.990 --> 00:30:18.000 align:start position:0% general we have a couple of like 00:30:18.000 --> 00:30:20.870 align:start position:0% general we have a couple of like suggestions<00:30:18.600> as<00:30:19.020> to<00:30:19.200> what<00:30:19.440> we<00:30:19.740> suggest<00:30:20.520> you<00:30:20.700> to 00:30:20.870 --> 00:30:20.880 align:start position:0% suggestions as to what we suggest you to 00:30:20.880 --> 00:30:21.710 align:start position:0% suggestions as to what we suggest you to do 00:30:21.710 --> 00:30:21.720 align:start position:0% do 00:30:21.720 --> 00:30:23.210 align:start position:0% do so 00:30:23.210 --> 00:30:23.220 align:start position:0% so 00:30:23.220 --> 00:30:26.090 align:start position:0% so if<00:30:23.880> you're<00:30:24.120> and<00:30:24.480> that<00:30:24.899> QR<00:30:25.320> code<00:30:25.500> is<00:30:25.740> uh<00:30:25.860> the 00:30:26.090 --> 00:30:26.100 align:start position:0% if you're and that QR code is uh the 00:30:26.100 --> 00:30:27.830 align:start position:0% if you're and that QR code is uh the link<00:30:26.220> tree<00:30:26.460> I<00:30:26.640> was<00:30:26.760> mentioning<00:30:27.120> earlier<00:30:27.419> so<00:30:27.720> it 00:30:27.830 --> 00:30:27.840 align:start position:0% link tree I was mentioning earlier so it 00:30:27.840 --> 00:30:29.690 align:start position:0% link tree I was mentioning earlier so it has<00:30:28.020> links<00:30:28.380> to<00:30:28.500> all<00:30:28.799> all<00:30:29.100> of<00:30:29.279> these<00:30:29.520> things 00:30:29.690 --> 00:30:29.700 align:start position:0% has links to all all of these things 00:30:29.700 --> 00:30:32.269 align:start position:0% has links to all all of these things along<00:30:30.240> with<00:30:30.600> the<00:30:30.899> like<00:30:31.260> Shandong<00:30:31.799> test<00:30:32.039> net 00:30:32.269 --> 00:30:32.279 align:start position:0% along with the like Shandong test net 00:30:32.279 --> 00:30:34.450 align:start position:0% along with the like Shandong test net instructions<00:30:33.419> I<00:30:33.659> also<00:30:33.960> I<00:30:34.020> want<00:30:34.140> to<00:30:34.200> mention 00:30:34.450 --> 00:30:34.460 align:start position:0% instructions I also I want to mention 00:30:34.460 --> 00:30:37.669 align:start position:0% instructions I also I want to mention the<00:30:35.460> structure<00:30:35.820> of<00:30:35.940> our<00:30:36.480> mono<00:30:36.899> repo<00:30:37.260> you<00:30:37.500> can 00:30:37.669 --> 00:30:37.679 align:start position:0% the structure of our mono repo you can 00:30:37.679 --> 00:30:39.889 align:start position:0% the structure of our mono repo you can clone<00:30:37.980> the<00:30:38.279> whole<00:30:38.399> mono<00:30:38.820> repo<00:30:39.240> and<00:30:39.480> it'll<00:30:39.720> come 00:30:39.889 --> 00:30:39.899 align:start position:0% clone the whole mono repo and it'll come 00:30:39.899 --> 00:30:44.090 align:start position:0% clone the whole mono repo and it'll come with<00:30:40.200> what<00:30:41.039> is<00:30:41.220> it<00:30:41.399> 12<00:30:41.820> packages<00:30:42.419> however<00:30:43.140> all 00:30:44.090 --> 00:30:44.100 align:start position:0% with what is it 12 packages however all 00:30:44.100 --> 00:30:46.070 align:start position:0% with what is it 12 packages however all of<00:30:44.220> the<00:30:44.340> relevant<00:30:44.760> packages<00:30:45.059> will<00:30:45.480> come<00:30:45.720> in 00:30:46.070 --> 00:30:46.080 align:start position:0% of the relevant packages will come in 00:30:46.080 --> 00:30:47.750 align:start position:0% of the relevant packages will come in the<00:30:46.200> mono<00:30:46.500> repo<00:30:46.860> if<00:30:47.039> you<00:30:47.159> clone<00:30:47.399> that<00:30:47.580> from 00:30:47.750 --> 00:30:47.760 align:start position:0% the mono repo if you clone that from 00:30:47.760 --> 00:30:50.810 align:start position:0% the mono repo if you clone that from GitHub<00:30:48.179> but<00:30:48.960> each<00:30:49.260> individual<00:30:49.860> package<00:30:50.399> is 00:30:50.810 --> 00:30:50.820 align:start position:0% GitHub but each individual package is 00:30:50.820 --> 00:30:53.690 align:start position:0% GitHub but each individual package is also<00:30:51.179> installable<00:30:51.960> on<00:30:52.260> its<00:30:52.559> own 00:30:53.690 --> 00:30:53.700 align:start position:0% also installable on its own 00:30:53.700 --> 00:30:56.210 align:start position:0% also installable on its own um<00:30:54.179> so<00:30:54.720> you<00:30:54.899> can<00:30:55.020> you<00:30:55.260> can<00:30:55.440> install<00:30:55.559> just<00:30:55.980> the 00:30:56.210 --> 00:30:56.220 align:start position:0% um so you can you can install just the 00:30:56.220 --> 00:30:57.769 align:start position:0% um so you can you can install just the transaction<00:30:56.580> package<00:30:57.120> or<00:30:57.299> just<00:30:57.480> the<00:30:57.600> block 00:30:57.769 --> 00:30:57.779 align:start position:0% transaction package or just the block 00:30:57.779 --> 00:30:59.870 align:start position:0% transaction package or just the block package<00:30:58.200> and<00:30:58.440> you<00:30:58.620> don't<00:30:58.740> need<00:30:59.340> to<00:30:59.520> have<00:30:59.640> the 00:30:59.870 --> 00:30:59.880 align:start position:0% package and you don't need to have the 00:30:59.880 --> 00:31:02.210 align:start position:0% package and you don't need to have the whole<00:31:00.000> mono<00:31:00.360> repo<00:31:00.720> as<00:31:01.140> a<00:31:01.380> dependency<00:31:01.740> you<00:31:02.100> can 00:31:02.210 --> 00:31:02.220 align:start position:0% whole mono repo as a dependency you can 00:31:02.220 --> 00:31:08.269 align:start position:0% whole mono repo as a dependency you can have<00:31:02.399> each<00:31:03.000> individual<00:31:03.899> each<00:31:04.260> JS<00:31:04.740> package 00:31:08.269 --> 00:31:08.279 align:start position:0% 00:31:08.279 --> 00:31:10.010 align:start position:0% yeah<00:31:08.760> yeah<00:31:08.820> because<00:31:09.360> I<00:31:09.539> would<00:31:09.659> encourage<00:31:09.960> you 00:31:10.010 --> 00:31:10.020 align:start position:0% yeah yeah because I would encourage you 00:31:10.020 --> 00:31:11.510 align:start position:0% yeah yeah because I would encourage you today<00:31:10.200> to<00:31:10.500> maybe<00:31:10.679> clone<00:31:11.039> the<00:31:11.220> whole<00:31:11.340> model 00:31:11.510 --> 00:31:11.520 align:start position:0% today to maybe clone the whole model 00:31:11.520 --> 00:31:13.850 align:start position:0% today to maybe clone the whole model repo<00:31:12.059> so<00:31:12.240> you<00:31:12.360> can<00:31:12.539> see<00:31:12.659> everything<00:31:13.020> and<00:31:13.679> and 00:31:13.850 --> 00:31:13.860 align:start position:0% repo so you can see everything and and 00:31:13.860 --> 00:31:15.409 align:start position:0% repo so you can see everything and and get<00:31:14.159> a<00:31:14.279> sense<00:31:14.460> of<00:31:14.580> how<00:31:14.760> they<00:31:14.880> all<00:31:15.000> connect<00:31:15.179> to 00:31:15.409 --> 00:31:15.419 align:start position:0% get a sense of how they all connect to 00:31:15.419 --> 00:31:17.570 align:start position:0% get a sense of how they all connect to each<00:31:15.600> other<00:31:15.779> yeah<00:31:16.679> yeah<00:31:16.860> clothing<00:31:17.159> the<00:31:17.460> model 00:31:17.570 --> 00:31:17.580 align:start position:0% each other yeah yeah clothing the model 00:31:17.580 --> 00:31:19.070 align:start position:0% each other yeah yeah clothing the model repo<00:31:18.000> is<00:31:18.120> probably<00:31:18.240> the<00:31:18.419> way<00:31:18.600> to<00:31:18.720> go<00:31:18.840> if<00:31:18.960> you 00:31:19.070 --> 00:31:19.080 align:start position:0% repo is probably the way to go if you 00:31:19.080 --> 00:31:20.330 align:start position:0% repo is probably the way to go if you want<00:31:19.200> to<00:31:19.320> experiment<00:31:19.559> a<00:31:19.740> bit<00:31:19.860> especially 00:31:20.330 --> 00:31:20.340 align:start position:0% want to experiment a bit especially 00:31:20.340 --> 00:31:22.250 align:start position:0% want to experiment a bit especially since<00:31:20.640> some<00:31:20.820> of<00:31:20.940> these<00:31:21.059> packages<00:31:21.299> are<00:31:21.600> and 00:31:22.250 --> 00:31:22.260 align:start position:0% since some of these packages are and 00:31:22.260 --> 00:31:23.870 align:start position:0% since some of these packages are and they're<00:31:22.440> dependent<00:31:22.860> on<00:31:22.980> you<00:31:23.399> know<00:31:23.520> each<00:31:23.700> other 00:31:23.870 --> 00:31:23.880 align:start position:0% they're dependent on you know each other 00:31:23.880 --> 00:31:26.029 align:start position:0% they're dependent on you know each other but<00:31:24.539> if<00:31:24.720> you<00:31:24.840> were<00:31:25.020> for<00:31:25.260> example<00:31:25.440> building<00:31:25.799> a 00:31:26.029 --> 00:31:26.039 align:start position:0% but if you were for example building a 00:31:26.039 --> 00:31:27.409 align:start position:0% but if you were for example building a set<00:31:26.159> of<00:31:26.279> tooling<00:31:26.580> and<00:31:26.760> you<00:31:26.940> only<00:31:27.059> need<00:31:27.240> to 00:31:27.409 --> 00:31:27.419 align:start position:0% set of tooling and you only need to 00:31:27.419 --> 00:31:29.149 align:start position:0% set of tooling and you only need to build<00:31:27.600> blocks<00:31:28.020> from<00:31:28.380> data<00:31:28.799> or<00:31:29.039> build 00:31:29.149 --> 00:31:29.159 align:start position:0% build blocks from data or build 00:31:29.159 --> 00:31:30.830 align:start position:0% build blocks from data or build transactions<00:31:29.820> from<00:31:30.000> some<00:31:30.179> piece<00:31:30.480> of<00:31:30.539> data 00:31:30.830 --> 00:31:30.840 align:start position:0% transactions from some piece of data 00:31:30.840 --> 00:31:32.870 align:start position:0% transactions from some piece of data that<00:31:30.960> you<00:31:31.080> have<00:31:31.260> you<00:31:31.799> could<00:31:31.860> only<00:31:32.039> import<00:31:32.399> like 00:31:32.870 --> 00:31:32.880 align:start position:0% that you have you could only import like 00:31:32.880 --> 00:31:35.810 align:start position:0% that you have you could only import like app<00:31:33.179> ethereum<00:31:33.740> uh<00:31:34.740> Block<00:31:34.919> in<00:31:35.220> that<00:31:35.399> ethereum 00:31:35.810 --> 00:31:35.820 align:start position:0% app ethereum uh Block in that ethereum 00:31:35.820 --> 00:31:37.490 align:start position:0% app ethereum uh Block in that ethereum transaction<00:31:36.240> and<00:31:36.659> that<00:31:36.840> would<00:31:36.960> be<00:31:37.140> you<00:31:37.440> know 00:31:37.490 --> 00:31:37.500 align:start position:0% transaction and that would be you know 00:31:37.500 --> 00:31:38.810 align:start position:0% transaction and that would be you know all<00:31:37.620> that<00:31:37.799> you<00:31:37.980> need<00:31:38.100> you<00:31:38.279> don't<00:31:38.340> need<00:31:38.460> to<00:31:38.580> you 00:31:38.810 --> 00:31:38.820 align:start position:0% all that you need you don't need to you 00:31:38.820 --> 00:31:40.190 align:start position:0% all that you need you don't need to you know<00:31:38.940> import<00:31:39.120> the<00:31:39.360> whole<00:31:39.480> model<00:31:39.659> repo<00:31:40.080> it's 00:31:40.190 --> 00:31:40.200 align:start position:0% know import the whole model repo it's 00:31:40.200 --> 00:31:42.590 align:start position:0% know import the whole model repo it's just<00:31:40.380> package<00:31:40.799> based 00:31:42.590 --> 00:31:42.600 align:start position:0% just package based 00:31:42.600 --> 00:31:44.810 align:start position:0% just package based so<00:31:43.260> yeah<00:31:43.380> what<00:31:43.620> we<00:31:43.799> have<00:31:43.980> like<00:31:44.399> sort<00:31:44.700> of 00:31:44.810 --> 00:31:44.820 align:start position:0% so yeah what we have like sort of 00:31:44.820 --> 00:31:47.029 align:start position:0% so yeah what we have like sort of prepared<00:31:45.179> for<00:31:45.299> you<00:31:45.480> in<00:31:45.659> terms<00:31:45.899> of<00:31:46.020> uh<00:31:46.500> like 00:31:47.029 --> 00:31:47.039 align:start position:0% prepared for you in terms of uh like 00:31:47.039 --> 00:31:48.230 align:start position:0% prepared for you in terms of uh like paths 00:31:48.230 --> 00:31:48.240 align:start position:0% paths 00:31:48.240 --> 00:31:51.110 align:start position:0% paths if<00:31:48.840> you're<00:31:49.020> more<00:31:49.320> like<00:31:49.980> uh<00:31:50.520> I<00:31:50.820> would<00:31:50.940> say 00:31:51.110 --> 00:31:51.120 align:start position:0% if you're more like uh I would say 00:31:51.120 --> 00:31:52.549 align:start position:0% if you're more like uh I would say beginner<00:31:51.419> but<00:31:51.600> like<00:31:51.779> if<00:31:51.899> you're<00:31:52.020> more<00:31:52.260> novice 00:31:52.549 --> 00:31:52.559 align:start position:0% beginner but like if you're more novice 00:31:52.559 --> 00:31:54.350 align:start position:0% beginner but like if you're more novice or<00:31:52.799> if<00:31:53.039> you've<00:31:53.340> never<00:31:53.520> really<00:31:53.760> learned<00:31:54.179> about 00:31:54.350 --> 00:31:54.360 align:start position:0% or if you've never really learned about 00:31:54.360 --> 00:31:57.230 align:start position:0% or if you've never really learned about you<00:31:55.200> know<00:31:55.320> Merkel<00:31:55.799> Patricia<00:31:56.279> trees 00:31:57.230 --> 00:31:57.240 align:start position:0% you know Merkel Patricia trees 00:31:57.240 --> 00:31:59.930 align:start position:0% you know Merkel Patricia trees uh<00:31:58.140> a<00:31:58.440> good<00:31:58.500> way<00:31:58.740> like<00:31:58.980> to<00:31:59.220> explore<00:31:59.520> that<00:31:59.700> is 00:31:59.930 --> 00:31:59.940 align:start position:0% uh a good way like to explore that is 00:31:59.940 --> 00:32:02.210 align:start position:0% uh a good way like to explore that is with<00:32:00.240> a<00:32:00.419> tutorial<00:32:00.960> that<00:32:01.740> uh<00:32:01.919> have<00:32:02.159> been 00:32:02.210 --> 00:32:02.220 align:start position:0% with a tutorial that uh have been 00:32:02.220 --> 00:32:03.769 align:start position:0% with a tutorial that uh have been written<00:32:02.520> like<00:32:02.640> two<00:32:02.820> years<00:32:02.940> ago<00:32:03.120> and<00:32:03.299> has<00:32:03.600> been 00:32:03.769 --> 00:32:03.779 align:start position:0% written like two years ago and has been 00:32:03.779 --> 00:32:05.870 align:start position:0% written like two years ago and has been like<00:32:04.080> uh<00:32:04.500> updated<00:32:04.860> recently 00:32:05.870 --> 00:32:05.880 align:start position:0% like uh updated recently 00:32:05.880 --> 00:32:08.510 align:start position:0% like uh updated recently and<00:32:06.360> it<00:32:06.480> basically<00:32:06.840> goes<00:32:07.260> through<00:32:07.500> it<00:32:08.159> uses 00:32:08.510 --> 00:32:08.520 align:start position:0% and it basically goes through it uses 00:32:08.520 --> 00:32:11.269 align:start position:0% and it basically goes through it uses our<00:32:09.000> tree<00:32:09.480> package<00:32:09.960> to<00:32:10.500> teach<00:32:10.620> you<00:32:10.799> about<00:32:10.980> the 00:32:11.269 --> 00:32:11.279 align:start position:0% our tree package to teach you about the 00:32:11.279 --> 00:32:13.250 align:start position:0% our tree package to teach you about the very<00:32:11.460> fundamentals<00:32:12.179> of<00:32:12.360> that<00:32:12.539> data<00:32:12.899> structure 00:32:13.250 --> 00:32:13.260 align:start position:0% very fundamentals of that data structure 00:32:13.260 --> 00:32:15.769 align:start position:0% very fundamentals of that data structure so<00:32:13.559> it<00:32:13.679> just<00:32:13.799> starts<00:32:14.100> with<00:32:14.340> you<00:32:14.700> know<00:32:14.779> uh 00:32:15.769 --> 00:32:15.779 align:start position:0% so it just starts with you know uh 00:32:15.779 --> 00:32:17.870 align:start position:0% so it just starts with you know uh putting<00:32:16.140> a<00:32:16.260> value<00:32:16.440> inside<00:32:16.679> the<00:32:17.039> miracle<00:32:17.700> but 00:32:17.870 --> 00:32:17.880 align:start position:0% putting a value inside the miracle but 00:32:17.880 --> 00:32:20.389 align:start position:0% putting a value inside the miracle but you<00:32:18.059> should<00:32:18.179> try<00:32:18.419> database<00:32:19.260> getting<00:32:20.100> the 00:32:20.389 --> 00:32:20.399 align:start position:0% you should try database getting the 00:32:20.399 --> 00:32:22.730 align:start position:0% you should try database getting the value<00:32:20.640> uh<00:32:21.299> Computing<00:32:21.720> a<00:32:21.840> hash<00:32:22.080> looking<00:32:22.500> how 00:32:22.730 --> 00:32:22.740 align:start position:0% value uh Computing a hash looking how 00:32:22.740 --> 00:32:24.529 align:start position:0% value uh Computing a hash looking how you<00:32:22.919> can<00:32:23.039> you<00:32:23.220> know<00:32:23.340> make<00:32:23.520> proofs<00:32:24.000> from<00:32:24.299> these 00:32:24.529 --> 00:32:24.539 align:start position:0% you can you know make proofs from these 00:32:24.539 --> 00:32:27.950 align:start position:0% you can you know make proofs from these hashes<00:32:24.980> eventually<00:32:25.980> all<00:32:26.279> the<00:32:26.460> way<00:32:26.460> up<00:32:26.760> to<00:32:27.179> uh 00:32:27.950 --> 00:32:27.960 align:start position:0% hashes eventually all the way up to uh 00:32:27.960 --> 00:32:29.649 align:start position:0% hashes eventually all the way up to uh you<00:32:28.200> know<00:32:28.260> querying<00:32:28.799> data<00:32:29.100> on<00:32:29.159> the<00:32:29.279> blockchain 00:32:29.649 --> 00:32:29.659 align:start position:0% you know querying data on the blockchain 00:32:29.659 --> 00:32:33.230 align:start position:0% you know querying data on the blockchain and<00:32:30.659> uh<00:32:31.080> and<00:32:31.799> interacting<00:32:32.340> with<00:32:32.580> it<00:32:32.700> more 00:32:33.230 --> 00:32:33.240 align:start position:0% and uh and interacting with it more 00:32:33.240 --> 00:32:35.389 align:start position:0% and uh and interacting with it more dynamically<00:32:33.840> in<00:32:34.080> a<00:32:34.200> way<00:32:34.320> that's<00:32:34.440> more<00:32:34.740> similar 00:32:35.389 --> 00:32:35.399 align:start position:0% dynamically in a way that's more similar 00:32:35.399 --> 00:32:36.889 align:start position:0% dynamically in a way that's more similar to<00:32:35.520> what<00:32:35.640> you'd<00:32:35.880> expect<00:32:36.000> in<00:32:36.299> the<00:32:36.480> real<00:32:36.600> world 00:32:36.889 --> 00:32:36.899 align:start position:0% to what you'd expect in the real world 00:32:36.899 --> 00:32:38.570 align:start position:0% to what you'd expect in the real world context 00:32:38.570 --> 00:32:38.580 align:start position:0% context 00:32:38.580 --> 00:32:40.029 align:start position:0% context so 00:32:40.029 --> 00:32:40.039 align:start position:0% so 00:32:40.039 --> 00:32:42.470 align:start position:0% so I'm<00:32:41.039> super<00:32:41.220> happy<00:32:41.460> to<00:32:41.640> help<00:32:41.940> you<00:32:42.120> as<00:32:42.299> well 00:32:42.470 --> 00:32:42.480 align:start position:0% I'm super happy to help you as well 00:32:42.480 --> 00:32:44.810 align:start position:0% I'm super happy to help you as well answer<00:32:43.260> any<00:32:43.500> questions<00:32:43.740> on<00:32:44.039> trees<00:32:44.340> it's<00:32:44.640> the 00:32:44.810 --> 00:32:44.820 align:start position:0% answer any questions on trees it's the 00:32:44.820 --> 00:32:47.510 align:start position:0% answer any questions on trees it's the package<00:32:45.120> I've<00:32:45.360> worked<00:32:45.840> the<00:32:45.899> most<00:32:46.080> on 00:32:47.510 --> 00:32:47.520 align:start position:0% package I've worked the most on 00:32:47.520 --> 00:32:49.549 align:start position:0% package I've worked the most on uh<00:32:48.059> in<00:32:48.240> the<00:32:48.360> more<00:32:48.539> I<00:32:48.840> guess<00:32:48.960> intermediate 00:32:49.549 --> 00:32:49.559 align:start position:0% uh in the more I guess intermediate 00:32:49.559 --> 00:32:51.289 align:start position:0% uh in the more I guess intermediate track<00:32:49.799> although<00:32:50.159> I<00:32:50.279> mean<00:32:50.399> Merkel<00:32:50.760> pursuites 00:32:51.289 --> 00:32:51.299 align:start position:0% track although I mean Merkel pursuites 00:32:51.299 --> 00:32:54.049 align:start position:0% track although I mean Merkel pursuites are<00:32:51.539> certainly<00:32:51.840> like<00:32:52.080> not<00:32:52.559> super<00:32:53.159> easy<00:32:53.399> so<00:32:53.700> we 00:32:54.049 --> 00:32:54.059 align:start position:0% are certainly like not super easy so we 00:32:54.059 --> 00:32:55.010 align:start position:0% are certainly like not super easy so we could<00:32:54.179> have<00:32:54.299> put<00:32:54.480> that<00:32:54.659> in<00:32:54.840> their 00:32:55.010 --> 00:32:55.020 align:start position:0% could have put that in their 00:32:55.020 --> 00:32:57.889 align:start position:0% could have put that in their intermediate<00:32:55.740> track<00:32:55.919> as<00:32:56.159> well<00:32:56.360> uh<00:32:57.360> you<00:32:57.720> can 00:32:57.889 --> 00:32:57.899 align:start position:0% intermediate track as well uh you can 00:32:57.899 --> 00:33:00.470 align:start position:0% intermediate track as well uh you can experiment<00:32:58.260> with<00:32:58.500> like<00:32:58.679> rlp<00:32:59.220> encoding<00:33:00.179> or 00:33:00.470 --> 00:33:00.480 align:start position:0% experiment with like rlp encoding or 00:33:00.480 --> 00:33:04.130 align:start position:0% experiment with like rlp encoding or decoding<00:33:01.220> so<00:33:02.220> this<00:33:02.460> is<00:33:02.520> the<00:33:02.760> serializing<00:33:03.480> uh 00:33:04.130 --> 00:33:04.140 align:start position:0% decoding so this is the serializing uh 00:33:04.140 --> 00:33:07.789 align:start position:0% decoding so this is the serializing uh algorithm<00:33:04.860> currently<00:33:05.340> used<00:33:05.700> by<00:33:06.059> ethereum<00:33:06.799> and 00:33:07.789 --> 00:33:07.799 align:start position:0% algorithm currently used by ethereum and 00:33:07.799 --> 00:33:10.010 align:start position:0% algorithm currently used by ethereum and we<00:33:08.159> cover<00:33:08.340> a<00:33:08.640> bit<00:33:08.760> of<00:33:08.880> that<00:33:08.940> in<00:33:09.120> the<00:33:09.299> Patricia 00:33:10.010 --> 00:33:10.020 align:start position:0% we cover a bit of that in the Patricia 00:33:10.020 --> 00:33:12.110 align:start position:0% we cover a bit of that in the Patricia trees<00:33:10.380> tutorial<00:33:10.799> but<00:33:11.279> if<00:33:11.640> you<00:33:11.820> want<00:33:12.000> to 00:33:12.110 --> 00:33:12.120 align:start position:0% trees tutorial but if you want to 00:33:12.120 --> 00:33:14.690 align:start position:0% trees tutorial but if you want to experiment<00:33:12.539> with<00:33:12.779> like<00:33:12.899> oh<00:33:13.080> what<00:33:13.380> does<00:33:13.500> a<00:33:14.159> an 00:33:14.690 --> 00:33:14.700 align:start position:0% experiment with like oh what does a an 00:33:14.700 --> 00:33:16.730 align:start position:0% experiment with like oh what does a an area<00:33:14.880> containing<00:33:15.419> a<00:33:15.600> dog<00:33:15.779> and<00:33:16.080> cat<00:33:16.320> strings 00:33:16.730 --> 00:33:16.740 align:start position:0% area containing a dog and cat strings 00:33:16.740 --> 00:33:19.130 align:start position:0% area containing a dog and cat strings look<00:33:17.340> like<00:33:17.580> when<00:33:17.940> you<00:33:18.120> are<00:33:18.299> all<00:33:18.480> pin<00:33:18.779> code<00:33:18.899> them 00:33:19.130 --> 00:33:19.140 align:start position:0% look like when you are all pin code them 00:33:19.140 --> 00:33:21.169 align:start position:0% look like when you are all pin code them that's<00:33:19.500> the<00:33:19.740> package<00:33:20.039> you<00:33:20.220> would<00:33:20.340> go<00:33:20.460> for<00:33:20.640> it 00:33:21.169 --> 00:33:21.179 align:start position:0% that's the package you would go for it 00:33:21.179 --> 00:33:24.710 align:start position:0% that's the package you would go for it contains<00:33:21.600> two<00:33:21.840> methods<00:33:22.399> rlp.encode<00:33:23.720> rlp.d 00:33:24.710 --> 00:33:24.720 align:start position:0% contains two methods rlp.encode rlp.d 00:33:24.720 --> 00:33:27.049 align:start position:0% contains two methods rlp.encode rlp.d code<00:33:24.960> super<00:33:25.559> simple<00:33:25.860> and<00:33:26.580> you<00:33:26.700> have<00:33:26.820> a<00:33:26.940> bunch 00:33:27.049 --> 00:33:27.059 align:start position:0% code super simple and you have a bunch 00:33:27.059 --> 00:33:29.330 align:start position:0% code super simple and you have a bunch of<00:33:27.179> helpers<00:33:27.539> like<00:33:27.720> to<00:33:27.899> convert<00:33:28.200> hex<00:33:28.919> to 00:33:29.330 --> 00:33:29.340 align:start position:0% of helpers like to convert hex to 00:33:29.340 --> 00:33:31.310 align:start position:0% of helpers like to convert hex to Strings<00:33:29.640> and<00:33:29.940> stuff<00:33:30.419> like<00:33:30.600> that 00:33:31.310 --> 00:33:31.320 align:start position:0% Strings and stuff like that 00:33:31.320 --> 00:33:34.250 align:start position:0% Strings and stuff like that another<00:33:32.279> I<00:33:32.880> feel<00:33:33.000> like<00:33:33.179> exciting<00:33:33.659> thing<00:33:33.840> that 00:33:34.250 --> 00:33:34.260 align:start position:0% another I feel like exciting thing that 00:33:34.260 --> 00:33:38.029 align:start position:0% another I feel like exciting thing that you<00:33:34.440> could<00:33:34.620> use<00:33:35.580> are<00:33:35.960> packages<00:33:36.960> for 00:33:38.029 --> 00:33:38.039 align:start position:0% you could use are packages for 00:33:38.039 --> 00:33:41.269 align:start position:0% you could use are packages for is<00:33:38.640> uh<00:33:39.419> the<00:33:39.720> block<00:33:39.899> and<00:33:40.440> the<00:33:40.740> transaction 00:33:41.269 --> 00:33:41.279 align:start position:0% is uh the block and the transaction 00:33:41.279 --> 00:33:43.370 align:start position:0% is uh the block and the transaction packages<00:33:41.760> one<00:33:42.600> of<00:33:42.720> the<00:33:42.779> things<00:33:42.899> you<00:33:43.080> could<00:33:43.200> do 00:33:43.370 --> 00:33:43.380 align:start position:0% packages one of the things you could do 00:33:43.380 --> 00:33:46.070 align:start position:0% packages one of the things you could do for<00:33:43.620> example<00:33:43.860> is<00:33:44.399> query<00:33:44.880> uh<00:33:45.659> you<00:33:45.840> know<00:33:45.899> just 00:33:46.070 --> 00:33:46.080 align:start position:0% for example is query uh you know just 00:33:46.080 --> 00:33:47.870 align:start position:0% for example is query uh you know just like<00:33:46.320> we've<00:33:46.679> done 00:33:47.870 --> 00:33:47.880 align:start position:0% like we've done 00:33:47.880 --> 00:33:50.389 align:start position:0% like we've done here<00:33:48.539> we've<00:33:49.200> query<00:33:49.500> the<00:33:49.620> block<00:33:49.799> so<00:33:50.100> a<00:33:50.279> good 00:33:50.389 --> 00:33:50.399 align:start position:0% here we've query the block so a good 00:33:50.399 --> 00:33:53.090 align:start position:0% here we've query the block so a good exercise<00:33:50.640> would<00:33:51.059> be<00:33:51.240> to<00:33:51.480> recompute<00:33:52.200> the<00:33:52.860> hash 00:33:53.090 --> 00:33:53.100 align:start position:0% exercise would be to recompute the hash 00:33:53.100 --> 00:33:56.269 align:start position:0% exercise would be to recompute the hash of<00:33:53.220> that<00:33:53.399> block<00:33:53.720> from<00:33:54.720> that<00:33:55.080> data<00:33:55.500> we<00:33:56.100> have 00:33:56.269 --> 00:33:56.279 align:start position:0% of that block from that data we have 00:33:56.279 --> 00:33:58.669 align:start position:0% of that block from that data we have helpers<00:33:56.640> that<00:33:56.880> can<00:33:57.000> do<00:33:57.179> it<00:33:57.299> for<00:33:57.539> you<00:33:57.720> uh<00:33:58.440> like 00:33:58.669 --> 00:33:58.679 align:start position:0% helpers that can do it for you uh like 00:33:58.679 --> 00:34:00.169 align:start position:0% helpers that can do it for you uh like super<00:33:58.860> easily<00:33:59.279> where<00:33:59.519> you<00:33:59.700> basically<00:33:59.940> just 00:34:00.169 --> 00:34:00.179 align:start position:0% super easily where you basically just 00:34:00.179 --> 00:34:01.909 align:start position:0% super easily where you basically just paste<00:34:00.539> that<00:34:00.659> Json<00:34:01.019> object<00:34:01.380> and<00:34:01.559> it's<00:34:01.679> going<00:34:01.919> to 00:34:01.909 --> 00:34:01.919 align:start position:0% paste that Json object and it's going to 00:34:01.919 --> 00:34:03.830 align:start position:0% paste that Json object and it's going to recompute<00:34:02.460> like<00:34:02.640> the<00:34:02.940> hash<00:34:03.179> or<00:34:03.600> a<00:34:03.720> block 00:34:03.830 --> 00:34:03.840 align:start position:0% recompute like the hash or a block 00:34:03.840 --> 00:34:05.509 align:start position:0% recompute like the hash or a block object<00:34:04.260> for<00:34:04.559> which<00:34:04.740> you<00:34:04.860> can<00:34:04.980> get<00:34:05.100> the<00:34:05.279> hash 00:34:05.509 --> 00:34:05.519 align:start position:0% object for which you can get the hash 00:34:05.519 --> 00:34:08.750 align:start position:0% object for which you can get the hash but<00:34:06.360> it's<00:34:06.539> also<00:34:06.960> it<00:34:07.799> can<00:34:08.040> also<00:34:08.220> be<00:34:08.339> interesting 00:34:08.750 --> 00:34:08.760 align:start position:0% but it's also it can also be interesting 00:34:08.760 --> 00:34:10.369 align:start position:0% but it's also it can also be interesting to<00:34:09.000> just<00:34:09.119> take<00:34:09.300> those<00:34:09.540> fields<00:34:09.839> like<00:34:10.020> manually 00:34:10.369 --> 00:34:10.379 align:start position:0% to just take those fields like manually 00:34:10.379 --> 00:34:12.050 align:start position:0% to just take those fields like manually and<00:34:10.679> try<00:34:10.800> to<00:34:10.919> recompute<00:34:11.460> the<00:34:11.639> hash<00:34:11.820> yourself 00:34:12.050 --> 00:34:12.060 align:start position:0% and try to recompute the hash yourself 00:34:12.060 --> 00:34:14.270 align:start position:0% and try to recompute the hash yourself and<00:34:12.599> we<00:34:12.780> have<00:34:12.899> all<00:34:13.139> the<00:34:13.260> helper<00:34:13.619> methods<00:34:14.099> you 00:34:14.270 --> 00:34:14.280 align:start position:0% and we have all the helper methods you 00:34:14.280 --> 00:34:17.149 align:start position:0% and we have all the helper methods you would<00:34:14.399> you<00:34:14.760> would<00:34:14.940> need<00:34:15.240> to<00:34:16.020> to<00:34:16.260> do<00:34:16.560> that<00:34:16.740> and 00:34:17.149 --> 00:34:17.159 align:start position:0% would you would need to to do that and 00:34:17.159 --> 00:34:19.730 align:start position:0% would you would need to to do that and if<00:34:17.520> that<00:34:17.700> feels<00:34:18.119> a<00:34:18.300> bit<00:34:18.419> a<00:34:18.780> bit<00:34:19.020> hard<00:34:19.139> you<00:34:19.679> can 00:34:19.730 --> 00:34:19.740 align:start position:0% if that feels a bit a bit hard you can 00:34:19.740 --> 00:34:21.589 align:start position:0% if that feels a bit a bit hard you can look<00:34:19.859> at<00:34:20.099> how<00:34:20.280> we<00:34:20.520> actually<00:34:20.700> Implement<00:34:21.179> our 00:34:21.589 --> 00:34:21.599 align:start position:0% look at how we actually Implement our 00:34:21.599 --> 00:34:25.669 align:start position:0% look at how we actually Implement our helper<00:34:21.960> methods<00:34:22.440> and<00:34:23.099> you<00:34:23.399> know<00:34:23.520> try<00:34:23.879> that<00:34:24.119> out 00:34:25.669 --> 00:34:25.679 align:start position:0% helper methods and you know try that out 00:34:25.679 --> 00:34:28.490 align:start position:0% helper methods and you know try that out go<00:34:26.159> back<00:34:26.399> to<00:34:26.700> the<00:34:27.000> but<00:34:27.240> yeah 00:34:28.490 --> 00:34:28.500 align:start position:0% go back to the but yeah 00:34:28.500 --> 00:34:30.770 align:start position:0% go back to the but yeah but yeah<00:34:28.740> all<00:34:28.980> right<00:34:29.159> in<00:34:29.639> the<00:34:29.879> more<00:34:30.060> uh 00:34:30.770 --> 00:34:30.780 align:start position:0% but yeah all right in the more uh 00:34:30.780 --> 00:34:33.889 align:start position:0% but yeah all right in the more uh Advanced<00:34:31.500> I<00:34:32.099> guess<00:34:32.280> track<00:34:32.599> one<00:34:33.599> of<00:34:33.720> the<00:34:33.780> things 00:34:33.889 --> 00:34:33.899 align:start position:0% Advanced I guess track one of the things 00:34:33.899 --> 00:34:35.930 align:start position:0% Advanced I guess track one of the things you<00:34:34.020> could<00:34:34.200> do<00:34:34.379> is<00:34:34.740> invent<00:34:35.339> and<00:34:35.520> Implement 00:34:35.930 --> 00:34:35.940 align:start position:0% you could do is invent and Implement 00:34:35.940 --> 00:34:37.750 align:start position:0% you could do is invent and Implement your<00:34:36.240> own<00:34:36.540> EIP 00:34:37.750 --> 00:34:37.760 align:start position:0% your own EIP 00:34:37.760 --> 00:34:42.770 align:start position:0% your own EIP that<00:34:38.760> might<00:34:38.879> look<00:34:39.060> like<00:34:39.300> super<00:34:39.720> hard<00:34:40.700> but<00:34:41.780> we 00:34:42.770 --> 00:34:42.780 align:start position:0% that might look like super hard but we 00:34:42.780 --> 00:34:45.349 align:start position:0% that might look like super hard but we have<00:34:42.899> an<00:34:43.020> example<00:34:43.320> here<00:34:43.679> of<00:34:44.099> a<00:34:44.339> super<00:34:44.700> like 00:34:45.349 --> 00:34:45.359 align:start position:0% have an example here of a super like 00:34:45.359 --> 00:34:49.490 align:start position:0% have an example here of a super like minimalistic<00:34:46.820> EIP<00:34:47.820> and<00:34:48.720> I'm<00:34:48.839> actually<00:34:49.080> gonna 00:34:49.490 --> 00:34:49.500 align:start position:0% minimalistic EIP and I'm actually gonna 00:34:49.500 --> 00:34:52.070 align:start position:0% minimalistic EIP and I'm actually gonna show<00:34:50.220> that<00:34:50.399> to<00:34:50.580> you<00:34:50.700> just<00:34:51.060> so<00:34:51.240> that<00:34:51.480> you<00:34:51.780> see 00:34:52.070 --> 00:34:52.080 align:start position:0% show that to you just so that you see 00:34:52.080 --> 00:34:53.629 align:start position:0% show that to you just so that you see how 00:34:53.629 --> 00:34:53.639 align:start position:0% how 00:34:53.639 --> 00:34:58.190 align:start position:0% how small<00:34:54.480> like<00:34:55.139> uh<00:34:55.740> potential<00:34:56.359> EIP<00:34:57.359> can<00:34:57.780> be<00:34:57.900> so<00:34:58.080> I 00:34:58.190 --> 00:34:58.200 align:start position:0% small like uh potential EIP can be so I 00:34:58.200 --> 00:35:00.349 align:start position:0% small like uh potential EIP can be so I think<00:34:58.320> it's<00:34:58.440> 18<00:34:58.740> for<00:34:59.160> yeah<00:34:59.640> right 00:35:00.349 --> 00:35:00.359 align:start position:0% think it's 18 for yeah right 00:35:00.359 --> 00:35:03.170 align:start position:0% think it's 18 for yeah right so<00:35:00.960> it's<00:35:01.140> adding<00:35:01.859> like<00:35:02.040> 92<00:35:02.520> bytes<00:35:02.880> of<00:35:03.060> code 00:35:03.170 --> 00:35:03.180 align:start position:0% so it's adding like 92 bytes of code 00:35:03.180 --> 00:35:04.849 align:start position:0% so it's adding like 92 bytes of code removing<00:35:03.960> two 00:35:04.849 --> 00:35:04.859 align:start position:0% removing two 00:35:04.859 --> 00:35:06.950 align:start position:0% removing two pretty<00:35:05.339> simple<00:35:05.580> it's<00:35:06.119> in<00:35:06.300> the<00:35:06.420> IP<00:35:06.660> that<00:35:06.780> goes 00:35:06.950 --> 00:35:06.960 align:start position:0% pretty simple it's in the IP that goes 00:35:06.960 --> 00:35:08.810 align:start position:0% pretty simple it's in the IP that goes into<00:35:07.020> Shanghai<00:35:07.500> just<00:35:07.800> warms<00:35:08.220> the<00:35:08.339> coinbase 00:35:08.810 --> 00:35:08.820 align:start position:0% into Shanghai just warms the coinbase 00:35:08.820 --> 00:35:09.829 align:start position:0% into Shanghai just warms the coinbase address 00:35:09.829 --> 00:35:09.839 align:start position:0% address 00:35:09.839 --> 00:35:13.670 align:start position:0% address so<00:35:10.560> if<00:35:11.460> you<00:35:11.640> take<00:35:11.820> this<00:35:12.240> as<00:35:12.540> a 00:35:13.670 --> 00:35:13.680 align:start position:0% so if you take this as a 00:35:13.680 --> 00:35:15.230 align:start position:0% so if you take this as a as<00:35:13.740> an<00:35:14.220> example 00:35:15.230 --> 00:35:15.240 align:start position:0% as an example 00:35:15.240 --> 00:35:17.270 align:start position:0% as an example your<00:35:15.900> I<00:35:16.320> think<00:35:16.380> you're<00:35:16.560> easily<00:35:16.920> going<00:35:17.099> to<00:35:17.220> be 00:35:17.270 --> 00:35:17.280 align:start position:0% your I think you're easily going to be 00:35:17.280 --> 00:35:18.950 align:start position:0% your I think you're easily going to be able<00:35:17.460> to<00:35:17.579> you<00:35:17.940> know<00:35:18.000> reproduce<00:35:18.480> at<00:35:18.660> least<00:35:18.780> the 00:35:18.950 --> 00:35:18.960 align:start position:0% able to you know reproduce at least the 00:35:18.960 --> 00:35:22.430 align:start position:0% able to you know reproduce at least the scaffolding<00:35:19.560> for<00:35:19.920> an<00:35:20.160> EIP<00:35:20.599> and<00:35:21.599> you<00:35:22.140> can<00:35:22.200> like 00:35:22.430 --> 00:35:22.440 align:start position:0% scaffolding for an EIP and you can like 00:35:22.440 --> 00:35:25.190 align:start position:0% scaffolding for an EIP and you can like invent<00:35:23.040> this<00:35:23.400> perhaps<00:35:24.240> not<00:35:24.480> so<00:35:24.660> useful<00:35:24.960> but 00:35:25.190 --> 00:35:25.200 align:start position:0% invent this perhaps not so useful but 00:35:25.200 --> 00:35:27.950 align:start position:0% invent this perhaps not so useful but like<00:35:25.380> easy<00:35:25.619> one<00:35:25.920> where<00:35:26.700> it<00:35:27.060> just<00:35:27.359> modifies<00:35:27.780> the 00:35:27.950 --> 00:35:27.960 align:start position:0% like easy one where it just modifies the 00:35:27.960 --> 00:35:29.510 align:start position:0% like easy one where it just modifies the way<00:35:28.140> maybe<00:35:28.440> a<00:35:28.680> block<00:35:28.800> is<00:35:28.980> rounded<00:35:29.339> maybe 00:35:29.510 --> 00:35:29.520 align:start position:0% way maybe a block is rounded maybe 00:35:29.520 --> 00:35:32.270 align:start position:0% way maybe a block is rounded maybe modifies<00:35:30.119> the<00:35:30.540> the<00:35:30.900> name<00:35:31.140> of<00:35:31.260> field<00:35:31.500> or 00:35:32.270 --> 00:35:32.280 align:start position:0% modifies the the name of field or 00:35:32.280 --> 00:35:35.210 align:start position:0% modifies the the name of field or something<00:35:32.579> like<00:35:32.880> that<00:35:33.000> and<00:35:33.839> uh<00:35:34.140> yeah<00:35:34.440> that<00:35:34.800> I 00:35:35.210 --> 00:35:35.220 align:start position:0% something like that and uh yeah that I 00:35:35.220 --> 00:35:37.069 align:start position:0% something like that and uh yeah that I think<00:35:35.339> that<00:35:35.460> PR<00:35:35.640> can<00:35:36.060> serve<00:35:36.300> as<00:35:36.420> a<00:35:36.599> guideline 00:35:37.069 --> 00:35:37.079 align:start position:0% think that PR can serve as a guideline 00:35:37.079 --> 00:35:39.470 align:start position:0% think that PR can serve as a guideline for<00:35:37.320> how<00:35:37.619> to<00:35:37.740> do<00:35:37.859> that<00:35:38.040> and<00:35:38.640> yeah<00:35:38.820> most<00:35:39.060> of<00:35:39.240> the 00:35:39.470 --> 00:35:39.480 align:start position:0% for how to do that and yeah most of the 00:35:39.480 --> 00:35:41.390 align:start position:0% for how to do that and yeah most of the implementation<00:35:40.140> is<00:35:40.380> actually<00:35:40.619> like<00:35:40.980> it's 00:35:41.390 --> 00:35:41.400 align:start position:0% implementation is actually like it's 00:35:41.400 --> 00:35:44.329 align:start position:0% implementation is actually like it's basically<00:35:41.760> just<00:35:42.180> that<00:35:43.079> line<00:35:43.320> here<00:35:43.619> in 00:35:44.329 --> 00:35:44.339 align:start position:0% basically just that line here in 00:35:44.339 --> 00:35:46.550 align:start position:0% basically just that line here in addition<00:35:44.700> to<00:35:44.820> like<00:35:45.000> the<00:35:45.119> scaffolding<00:35:45.660> and<00:35:46.440> a 00:35:46.550 --> 00:35:46.560 align:start position:0% addition to like the scaffolding and a 00:35:46.560 --> 00:35:49.069 align:start position:0% addition to like the scaffolding and a bunch<00:35:46.740> of<00:35:46.859> tests<00:35:47.280> that<00:35:47.820> are<00:35:48.119> let's<00:35:48.900> just 00:35:49.069 --> 00:35:49.079 align:start position:0% bunch of tests that are let's just 00:35:49.079 --> 00:35:50.810 align:start position:0% bunch of tests that are let's just confirmed<00:35:49.500> that<00:35:49.740> the<00:35:49.980> EIP<00:35:50.280> has<00:35:50.640> been 00:35:50.810 --> 00:35:50.820 align:start position:0% confirmed that the EIP has been 00:35:50.820 --> 00:35:54.230 align:start position:0% confirmed that the EIP has been implemented<00:35:51.420> properly 00:35:54.230 --> 00:35:54.240 align:start position:0% implemented properly 00:35:54.240 --> 00:35:56.390 align:start position:0% implemented properly in<00:35:54.660> terms<00:35:54.960> of<00:35:55.079> other<00:35:55.440> things<00:35:55.680> that<00:35:56.040> you<00:35:56.160> could 00:35:56.390 --> 00:35:56.400 align:start position:0% in terms of other things that you could 00:35:56.400 --> 00:36:00.890 align:start position:0% in terms of other things that you could do<00:35:56.720> you<00:35:57.720> can<00:35:57.839> run<00:35:58.500> the<00:35:58.800> local<00:35:58.920> client<00:35:59.720> as<00:36:00.720> we 00:36:00.890 --> 00:36:00.900 align:start position:0% do you can run the local client as we 00:36:00.900 --> 00:36:03.349 align:start position:0% do you can run the local client as we you've<00:36:01.140> seen<00:36:01.320> us<00:36:01.440> do<00:36:01.680> and<00:36:02.460> you<00:36:02.579> can<00:36:02.760> run<00:36:03.000> the 00:36:03.349 --> 00:36:03.359 align:start position:0% you've seen us do and you can run the 00:36:03.359 --> 00:36:05.930 align:start position:0% you've seen us do and you can run the Shandong<00:36:04.020> test<00:36:04.440> net<00:36:04.619> with<00:36:04.920> lowestar<00:36:05.460> as<00:36:05.700> the 00:36:05.930 --> 00:36:05.940 align:start position:0% Shandong test net with lowestar as the 00:36:05.940 --> 00:36:08.870 align:start position:0% Shandong test net with lowestar as the consensus<00:36:06.540> client 00:36:08.870 --> 00:36:08.880 align:start position:0% consensus client 00:36:08.880 --> 00:36:12.470 align:start position:0% consensus client so<00:36:09.480> yeah<00:36:10.079> now<00:36:10.320> it's<00:36:10.560> of<00:36:10.859> to<00:36:11.579> the<00:36:11.820> races<00:36:12.180> as 00:36:12.470 --> 00:36:12.480 align:start position:0% so yeah now it's of to the races as 00:36:12.480 --> 00:36:16.430 align:start position:0% so yeah now it's of to the races as return<00:36:12.900> always<00:36:13.500> says 00:36:16.430 --> 00:36:16.440 align:start position:0% return always says 00:36:16.440 --> 00:36:19.130 align:start position:0% return always says so<00:36:16.920> any<00:36:17.220> uh<00:36:17.700> does<00:36:18.000> everyone<00:36:18.180> raise<00:36:18.780> your<00:36:18.960> hand 00:36:19.130 --> 00:36:19.140 align:start position:0% so any uh does everyone raise your hand 00:36:19.140 --> 00:36:21.230 align:start position:0% so any uh does everyone raise your hand if<00:36:19.320> you<00:36:19.500> don't<00:36:19.619> have<00:36:19.859> a<00:36:20.160> laptop 00:36:21.230 --> 00:36:21.240 align:start position:0% if you don't have a laptop 00:36:21.240 --> 00:36:24.530 align:start position:0% if you don't have a laptop well<00:36:21.780> I<00:36:22.020> have<00:36:22.140> one<00:36:22.260> so<00:36:22.380> I<00:36:22.500> won't<00:36:22.619> raise<00:36:22.859> my<00:36:23.099> hand 00:36:24.530 --> 00:36:24.540 align:start position:0% well I have one so I won't raise my hand 00:36:24.540 --> 00:36:26.710 align:start position:0% well I have one so I won't raise my hand so<00:36:24.960> everyone<00:36:25.260> has<00:36:25.560> one<00:36:25.740> awesome 00:36:26.710 --> 00:36:26.720 align:start position:0% so everyone has one awesome 00:36:26.720 --> 00:36:30.170 align:start position:0% so everyone has one awesome so<00:36:27.720> was<00:36:28.619> everyone<00:36:28.800> able<00:36:29.220> to<00:36:29.280> scan<00:36:29.579> that<00:36:29.940> uh 00:36:30.170 --> 00:36:30.180 align:start position:0% so was everyone able to scan that uh 00:36:30.180 --> 00:36:32.390 align:start position:0% so was everyone able to scan that uh link<00:36:30.420> tree<00:36:30.660> thing<00:36:31.260> all<00:36:31.619> right<00:36:31.740> cool<00:36:31.980> if<00:36:32.220> not 00:36:32.390 --> 00:36:32.400 align:start position:0% link tree thing all right cool if not 00:36:32.400 --> 00:36:36.190 align:start position:0% link tree thing all right cool if not the<00:36:32.579> link<00:36:32.760> is<00:36:33.000> just<00:36:33.119> linked<00:36:33.920> linktr.ee<00:36:35.119> slash 00:36:36.190 --> 00:36:36.200 align:start position:0% the link is just linked linktr.ee slash 00:36:36.200 --> 00:36:44.089 align:start position:0% the link is just linked linktr.ee slash ethereum.js<00:36:37.200> let<00:36:37.740> me<00:36:37.859> just<00:36:38.040> bring<00:36:38.160> it<00:36:38.339> up 00:36:44.089 --> 00:36:44.099 align:start position:0% 00:36:44.099 --> 00:36:47.630 align:start position:0% all<00:36:44.460> right 00:36:47.630 --> 00:36:47.640 align:start position:0% 00:36:47.640 --> 00:36:50.569 align:start position:0% so<00:36:48.119> do<00:36:48.720> I'm<00:36:49.560> wondering<00:36:49.800> how<00:36:49.980> to<00:36:50.099> best<00:36:50.280> like 00:36:50.569 --> 00:36:50.579 align:start position:0% so do I'm wondering how to best like 00:36:50.579 --> 00:36:53.390 align:start position:0% so do I'm wondering how to best like structure<00:36:51.180> this<00:36:51.359> so<00:36:51.720> either<00:36:52.020> I<00:36:52.320> can<00:36:52.560> go 00:36:53.390 --> 00:36:53.400 align:start position:0% structure this so either I can go 00:36:53.400 --> 00:36:55.609 align:start position:0% structure this so either I can go through<00:36:53.700> one<00:36:54.240> of<00:36:54.359> those<00:36:54.660> myself<00:36:54.960> for<00:36:55.380> those 00:36:55.609 --> 00:36:55.619 align:start position:0% through one of those myself for those 00:36:55.619 --> 00:36:57.650 align:start position:0% through one of those myself for those who<00:36:55.800> want<00:36:55.920> a<00:36:56.099> more<00:36:56.280> uh<00:36:56.760> follow<00:36:57.000> along<00:36:57.240> but<00:36:57.540> I 00:36:57.650 --> 00:36:57.660 align:start position:0% who want a more uh follow along but I 00:36:57.660 --> 00:36:59.450 align:start position:0% who want a more uh follow along but I think<00:36:57.780> what<00:36:57.960> would<00:36:58.140> be<00:36:58.320> helpful<00:36:58.680> is<00:36:58.920> maybe<00:36:59.160> if 00:36:59.450 --> 00:36:59.460 align:start position:0% think what would be helpful is maybe if 00:36:59.460 --> 00:37:02.089 align:start position:0% think what would be helpful is maybe if we<00:36:59.760> just<00:37:00.359> help<00:37:00.599> everyone<00:37:00.839> you<00:37:01.560> know<00:37:01.619> set<00:37:01.800> up<00:37:01.980> a 00:37:02.089 --> 00:37:02.099 align:start position:0% we just help everyone you know set up a 00:37:02.099 --> 00:37:04.790 align:start position:0% we just help everyone you know set up a local<00:37:02.220> environment<00:37:02.760> and<00:37:03.660> if<00:37:04.079> at<00:37:04.500> some<00:37:04.680> point 00:37:04.790 --> 00:37:04.800 align:start position:0% local environment and if at some point 00:37:04.800 --> 00:37:05.990 align:start position:0% local environment and if at some point you<00:37:04.980> want<00:37:05.040> to<00:37:05.160> follow<00:37:05.280> with<00:37:05.520> what<00:37:05.700> I'm<00:37:05.820> doing 00:37:05.990 --> 00:37:06.000 align:start position:0% you want to follow with what I'm doing 00:37:06.000 --> 00:37:07.730 align:start position:0% you want to follow with what I'm doing you<00:37:06.300> can<00:37:06.420> do<00:37:06.660> it<00:37:06.780> or<00:37:07.020> if<00:37:07.140> you<00:37:07.260> want<00:37:07.380> to<00:37:07.500> work<00:37:07.560> on 00:37:07.730 --> 00:37:07.740 align:start position:0% you can do it or if you want to work on 00:37:07.740 --> 00:37:09.230 align:start position:0% you can do it or if you want to work on your<00:37:07.859> own<00:37:07.980> thing<00:37:08.160> you<00:37:08.520> can<00:37:08.640> do<00:37:08.760> that<00:37:08.880> as<00:37:09.060> well 00:37:09.230 --> 00:37:09.240 align:start position:0% your own thing you can do that as well 00:37:09.240 --> 00:37:13.069 align:start position:0% your own thing you can do that as well does<00:37:09.839> that<00:37:10.140> sound<00:37:10.440> good<00:37:10.619> to<00:37:10.800> everybody 00:37:13.069 --> 00:37:13.079 align:start position:0% 00:37:13.079 --> 00:37:18.010 align:start position:0% yeah<00:37:13.680> all<00:37:14.040> right<00:37:14.280> cool 00:37:18.010 --> 00:37:18.020 align:start position:0% 00:37:18.020 --> 00:37:19.490 align:start position:0% [Music] 00:37:19.490 --> 00:37:19.500 align:start position:0% [Music] 00:37:19.500 --> 00:37:21.290 align:start position:0% [Music] all<00:37:19.980> right 00:37:21.290 --> 00:37:21.300 align:start position:0% all right 00:37:21.300 --> 00:37:24.710 align:start position:0% all right I'm<00:37:21.599> just<00:37:21.720> gonna<00:37:21.960> walk<00:37:22.740> around<00:37:23.359> might<00:37:24.359> not<00:37:24.540> be 00:37:24.710 --> 00:37:24.720 align:start position:0% I'm just gonna walk around might not be 00:37:24.720 --> 00:37:26.870 align:start position:0% I'm just gonna walk around might not be best<00:37:25.020> for<00:37:25.200> the<00:37:25.320> live<00:37:25.500> stream<00:37:25.680> not<00:37:26.579> that 00:37:26.870 --> 00:37:26.880 align:start position:0% best for the live stream not that 00:37:26.880 --> 00:37:28.970 align:start position:0% best for the live stream not that interesting<00:37:27.300> to<00:37:27.480> to<00:37:27.720> watch<00:37:27.900> an<00:37:28.260> empty<00:37:28.740> stage 00:37:28.970 --> 00:37:28.980 align:start position:0% interesting to to watch an empty stage 00:37:28.980 --> 00:37:33.829 align:start position:0% interesting to to watch an empty stage but<00:37:29.220> uh<00:37:29.400> I<00:37:29.700> will<00:37:29.760> be<00:37:29.940> walking<00:37:30.240> around 00:37:33.829 --> 00:37:33.839 align:start position:0% 00:37:33.839 --> 00:37:35.870 align:start position:0% and just<00:37:34.320> raise<00:37:34.500> your<00:37:34.740> hand<00:37:34.859> if<00:37:35.160> you<00:37:35.339> have<00:37:35.579> a 00:37:35.870 --> 00:37:35.880 align:start position:0% and just raise your hand if you have a 00:37:35.880 --> 00:37:38.450 align:start position:0% and just raise your hand if you have a an<00:37:36.420> issue<00:37:36.839> of<00:37:37.260> setting<00:37:37.619> up<00:37:37.680> your 00:37:38.450 --> 00:37:38.460 align:start position:0% an issue of setting up your 00:37:38.460 --> 00:37:40.550 align:start position:0% an issue of setting up your local<00:37:38.880> environment<00:37:39.420> just<00:37:39.900> clone<00:37:40.260> the<00:37:40.380> model 00:37:40.550 --> 00:37:40.560 align:start position:0% local environment just clone the model 00:37:40.560 --> 00:37:43.190 align:start position:0% local environment just clone the model repo<00:37:41.040> it's<00:37:41.760> linked<00:37:42.240> at<00:37:42.420> uh 00:37:43.190 --> 00:37:43.200 align:start position:0% repo it's linked at uh 00:37:43.200 --> 00:37:45.770 align:start position:0% repo it's linked at uh so<00:37:43.680> if<00:37:43.920> you<00:37:44.099> click<00:37:44.400> on<00:37:44.520> internment<00:37:45.000> yet<00:37:45.240> it's 00:37:45.770 --> 00:37:45.780 align:start position:0% so if you click on internment yet it's 00:37:45.780 --> 00:37:47.990 align:start position:0% so if you click on internment yet it's going<00:37:45.900> to<00:37:46.020> bring<00:37:46.140> you<00:37:46.320> to<00:37:46.740> uh<00:37:47.040> the<00:37:47.460> monorepo 00:37:47.990 --> 00:37:48.000 align:start position:0% going to bring you to uh the monorepo 00:37:48.000 --> 00:37:53.990 align:start position:0% going to bring you to uh the monorepo itself 00:37:53.990 --> 00:37:54.000 align:start position:0% 00:37:54.000 --> 00:37:56.089 align:start position:0% all<00:37:54.359> right<00:37:55.020> all<00:37:55.260> right<00:37:55.440> and<00:37:55.619> once<00:37:55.920> you've 00:37:56.089 --> 00:37:56.099 align:start position:0% all right all right and once you've 00:37:56.099 --> 00:37:58.310 align:start position:0% all right all right and once you've cloned<00:37:56.520> the<00:37:56.640> model<00:37:57.119> repo<00:37:57.599> the<00:37:57.839> way<00:37:57.960> to<00:37:58.140> install 00:37:58.310 --> 00:37:58.320 align:start position:0% cloned the model repo the way to install 00:37:58.320 --> 00:38:02.450 align:start position:0% cloned the model repo the way to install it<00:37:58.560> we<00:37:58.800> use<00:37:58.920> npm<00:37:59.460> so<00:37:59.760> just<00:38:00.000> npm<00:38:00.660> install<00:38:01.460> is 00:38:02.450 --> 00:38:02.460 align:start position:0% it we use npm so just npm install is 00:38:02.460 --> 00:38:06.950 align:start position:0% it we use npm so just npm install is anyone<00:38:02.820> running<00:38:03.180> on<00:38:03.599> the<00:38:03.720> windows 00:38:06.950 --> 00:38:06.960 align:start position:0% 00:38:06.960 --> 00:38:11.150 align:start position:0% very<00:38:07.440> happy<00:38:07.619> to<00:38:07.859> hear<00:38:08.099> that 00:38:11.150 --> 00:38:11.160 align:start position:0% 00:38:11.160 --> 00:38:13.069 align:start position:0% yeah<00:38:11.280> there's<00:38:11.940> the<00:38:12.119> door<00:38:12.240> here<00:38:12.480> for<00:38:12.720> Windows 00:38:13.069 --> 00:38:13.079 align:start position:0% yeah there's the door here for Windows 00:38:13.079 --> 00:38:16.910 align:start position:0% yeah there's the door here for Windows users<00:38:13.440> so<00:38:13.859> he's<00:38:14.099> I<00:38:14.460> assume<00:38:14.820> people<00:38:14.940> are<00:38:15.240> on<00:38:16.140> uh 00:38:16.910 --> 00:38:16.920 align:start position:0% users so he's I assume people are on uh 00:38:16.920 --> 00:38:19.670 align:start position:0% users so he's I assume people are on uh Mac<00:38:17.400> OS<00:38:17.760> or<00:38:18.000> Linux 00:38:19.670 --> 00:38:19.680 align:start position:0% Mac OS or Linux 00:38:19.680 --> 00:38:26.569 align:start position:0% Mac OS or Linux or<00:38:20.280> yeah<00:38:21.180> yeah 00:38:26.569 --> 00:38:26.579 align:start position:0% 00:38:26.579 --> 00:38:28.490 align:start position:0% okay<00:38:27.060> the<00:38:27.359> the<00:38:27.480> workshop<00:38:27.780> Wi-Fi's<00:38:28.380> password 00:38:28.490 --> 00:38:28.500 align:start position:0% okay the the workshop Wi-Fi's password 00:38:28.500 --> 00:38:32.390 align:start position:0% okay the the workshop Wi-Fi's password is<00:38:28.980> uh<00:38:29.400> build<00:38:29.820> it<00:38:30.119> 22. 00:38:32.390 --> 00:38:32.400 align:start position:0% is uh build it 22. 00:38:32.400 --> 00:38:36.109 align:start position:0% is uh build it 22. uh<00:38:33.180> lower<00:38:33.420> caps<00:38:33.900> build<00:38:34.140> it<00:38:34.380> and<00:38:34.619> 22<00:38:35.040> the 00:38:36.109 --> 00:38:36.119 align:start position:0% uh lower caps build it and 22 the 00:38:36.119 --> 00:38:40.010 align:start position:0% uh lower caps build it and 22 the the<00:38:36.420> number 00:38:40.010 --> 00:38:40.020 align:start position:0% 00:38:40.020 --> 00:38:42.290 align:start position:0% so<00:38:40.200> just<00:38:40.440> npm<00:38:40.920> install<00:38:41.099> from<00:38:41.460> the<00:38:41.640> mono<00:38:42.000> repo 00:38:42.290 --> 00:38:42.300 align:start position:0% so just npm install from the mono repo 00:38:42.300 --> 00:38:44.569 align:start position:0% so just npm install from the mono repo itself<00:38:42.480> make<00:38:43.020> sure<00:38:43.140> to<00:38:43.320> run<00:38:43.440> npm<00:38:43.980> install<00:38:44.160> in 00:38:44.569 --> 00:38:44.579 align:start position:0% itself make sure to run npm install in 00:38:44.579 --> 00:38:46.910 align:start position:0% itself make sure to run npm install in the<00:38:44.760> you<00:38:45.359> know<00:38:45.420> mono<00:38:45.960> repo<00:38:46.260> instead<00:38:46.560> of<00:38:46.680> in 00:38:46.910 --> 00:38:46.920 align:start position:0% the you know mono repo instead of in 00:38:46.920 --> 00:38:48.770 align:start position:0% the you know mono repo instead of in packages<00:38:47.280> themselves<00:38:47.820> so<00:38:48.359> that's<00:38:48.480> going<00:38:48.720> to 00:38:48.770 --> 00:38:48.780 align:start position:0% packages themselves so that's going to 00:38:48.780 --> 00:38:50.329 align:start position:0% packages themselves so that's going to build<00:38:48.900> the<00:38:49.079> whole<00:38:49.200> thing<00:38:49.380> which<00:38:49.740> is<00:38:49.859> what<00:38:50.160> we 00:38:50.329 --> 00:38:50.339 align:start position:0% build the whole thing which is what we 00:38:50.339 --> 00:38:53.390 align:start position:0% build the whole thing which is what we want 00:38:53.390 --> 00:38:53.400 align:start position:0% 00:38:53.400 --> 00:38:56.210 align:start position:0% is<00:38:53.880> everyone<00:38:54.060> good 00:38:56.210 --> 00:38:56.220 align:start position:0% is everyone good 00:38:56.220 --> 00:38:58.190 align:start position:0% is everyone good raise<00:38:56.640> your<00:38:56.880> hand<00:38:57.060> if<00:38:57.240> you<00:38:57.420> need<00:38:57.540> additional 00:38:58.190 --> 00:38:58.200 align:start position:0% raise your hand if you need additional 00:38:58.200 --> 00:39:01.490 align:start position:0% raise your hand if you need additional help 00:39:01.490 --> 00:39:01.500 align:start position:0% 00:39:01.500 --> 00:39:04.190 align:start position:0% okay<00:39:01.920> so<00:39:02.280> I<00:39:02.820> think<00:39:02.940> you<00:39:03.240> just<00:39:03.420> entered<00:39:03.780> so<00:39:04.079> yeah 00:39:04.190 --> 00:39:04.200 align:start position:0% okay so I think you just entered so yeah 00:39:04.200 --> 00:39:06.530 align:start position:0% okay so I think you just entered so yeah just<00:39:04.560> uh<00:39:04.800> you<00:39:05.220> can<00:39:05.339> clone<00:39:05.579> the<00:39:05.760> ethereum<00:39:06.240> JS 00:39:06.530 --> 00:39:06.540 align:start position:0% just uh you can clone the ethereum JS 00:39:06.540 --> 00:39:08.870 align:start position:0% just uh you can clone the ethereum JS motor<00:39:06.780> repo<00:39:07.260> uh 00:39:08.870 --> 00:39:08.880 align:start position:0% motor repo uh 00:39:08.880 --> 00:39:11.569 align:start position:0% motor repo uh the<00:39:09.540> second<00:39:09.720> link<00:39:10.020> intermediate<00:39:10.680> Link<00:39:10.800> in<00:39:11.400> the 00:39:11.569 --> 00:39:11.579 align:start position:0% the second link intermediate Link in the 00:39:11.579 --> 00:39:13.490 align:start position:0% the second link intermediate Link in the uh<00:39:11.820> in<00:39:12.060> the<00:39:12.240> link<00:39:12.359> tree<00:39:12.599> that<00:39:12.960> you<00:39:13.079> see<00:39:13.260> here 00:39:13.490 --> 00:39:13.500 align:start position:0% uh in the link tree that you see here 00:39:13.500 --> 00:39:16.910 align:start position:0% uh in the link tree that you see here and<00:39:14.460> then<00:39:14.640> uh<00:39:15.060> yeah<00:39:15.480> just<00:39:16.140> uh<00:39:16.500> make<00:39:16.800> sure 00:39:16.910 --> 00:39:16.920 align:start position:0% and then uh yeah just uh make sure 00:39:16.920 --> 00:39:18.349 align:start position:0% and then uh yeah just uh make sure you're<00:39:17.099> on<00:39:17.339> the<00:39:17.460> you're<00:39:17.820> on<00:39:18.000> the<00:39:18.180> master 00:39:18.349 --> 00:39:18.359 align:start position:0% you're on the you're on the master 00:39:18.359 --> 00:39:20.810 align:start position:0% you're on the you're on the master branch<00:39:18.780> that<00:39:19.140> should<00:39:19.320> be<00:39:19.440> default<00:39:19.859> and<00:39:20.640> then 00:39:20.810 --> 00:39:20.820 align:start position:0% branch that should be default and then 00:39:20.820 --> 00:39:23.569 align:start position:0% branch that should be default and then uh<00:39:21.300> yeah<00:39:21.599> just<00:39:21.900> pull<00:39:22.079> the<00:39:22.260> latest<00:39:22.440> and<00:39:22.920> npm 00:39:23.569 --> 00:39:23.579 align:start position:0% uh yeah just pull the latest and npm 00:39:23.579 --> 00:39:25.970 align:start position:0% uh yeah just pull the latest and npm I've<00:39:23.940> to<00:39:24.480> install<00:39:24.720> the<00:39:25.020> model<00:39:25.140> repo<00:39:25.680> that 00:39:25.970 --> 00:39:25.980 align:start position:0% I've to install the model repo that 00:39:25.980 --> 00:39:31.370 align:start position:0% I've to install the model repo that should<00:39:26.099> be<00:39:26.280> all<00:39:26.400> that<00:39:26.579> you<00:39:26.820> need 00:39:31.370 --> 00:39:31.380 align:start position:0% 00:39:31.380 --> 00:39:33.109 align:start position:0% so<00:39:32.099> just 00:39:33.109 --> 00:39:33.119 align:start position:0% so just 00:39:33.119 --> 00:39:35.030 align:start position:0% so just just<00:39:33.599> so<00:39:33.900> I<00:39:34.079> that<00:39:34.260> I<00:39:34.440> do<00:39:34.560> something<00:39:34.740> that's 00:39:35.030 --> 00:39:35.040 align:start position:0% just so I that I do something that's 00:39:35.040 --> 00:39:36.890 align:start position:0% just so I that I do something that's relevant<00:39:35.400> for<00:39:35.640> most<00:39:35.760> people<00:39:36.000> who's<00:39:36.540> thinking 00:39:36.890 --> 00:39:36.900 align:start position:0% relevant for most people who's thinking 00:39:36.900 --> 00:39:38.329 align:start position:0% relevant for most people who's thinking of<00:39:37.020> doing<00:39:37.320> the 00:39:38.329 --> 00:39:38.339 align:start position:0% of doing the 00:39:38.339 --> 00:39:43.250 align:start position:0% of doing the uh<00:39:38.940> Merkel<00:39:39.359> Patricia<00:39:39.839> trees<00:39:40.140> tutorial 00:39:43.250 --> 00:39:43.260 align:start position:0% 00:39:43.260 --> 00:39:45.170 align:start position:0% awesome 00:39:45.170 --> 00:39:45.180 align:start position:0% awesome 00:39:45.180 --> 00:39:48.530 align:start position:0% awesome okay<00:39:45.660> cool<00:39:46.040> I<00:39:47.040> wouldn't<00:39:47.220> quite<00:39:48.000> recommend<00:39:48.420> it 00:39:48.530 --> 00:39:48.540 align:start position:0% okay cool I wouldn't quite recommend it 00:39:48.540 --> 00:39:50.270 align:start position:0% okay cool I wouldn't quite recommend it it<00:39:48.720> does<00:39:48.839> cover<00:39:49.020> some<00:39:49.380> of<00:39:49.500> the<00:39:49.619> stuff<00:39:49.800> that 00:39:50.270 --> 00:39:50.280 align:start position:0% it does cover some of the stuff that 00:39:50.280 --> 00:39:52.730 align:start position:0% it does cover some of the stuff that were<00:39:50.720> uh<00:39:51.720> we<00:39:52.020> would<00:39:52.140> be<00:39:52.260> doing<00:39:52.380> in<00:39:52.560> Block 00:39:52.730 --> 00:39:52.740 align:start position:0% were uh we would be doing in Block 00:39:52.740 --> 00:39:55.010 align:start position:0% were uh we would be doing in Block transactions<00:39:53.339> in<00:39:53.460> the<00:39:53.640> rlp<00:39:54.060> but<00:39:54.660> it<00:39:54.839> just 00:39:55.010 --> 00:39:55.020 align:start position:0% transactions in the rlp but it just 00:39:55.020 --> 00:39:57.050 align:start position:0% transactions in the rlp but it just guides<00:39:55.440> you<00:39:55.500> through<00:39:55.680> them<00:39:55.920> rather<00:39:56.460> than<00:39:56.700> just 00:39:57.050 --> 00:39:57.060 align:start position:0% guides you through them rather than just 00:39:57.060 --> 00:40:01.250 align:start position:0% guides you through them rather than just showing<00:39:58.140> you<00:39:58.619> out<00:39:58.800> there<00:39:59.400> uh<00:40:00.300> who's<00:40:00.900> thinking 00:40:01.250 --> 00:40:01.260 align:start position:0% showing you out there uh who's thinking 00:40:01.260 --> 00:40:03.109 align:start position:0% showing you out there uh who's thinking of<00:40:01.560> just<00:40:01.800> going<00:40:01.980> straight<00:40:02.220> intermediate<00:40:02.880> and 00:40:03.109 --> 00:40:03.119 align:start position:0% of just going straight intermediate and 00:40:03.119 --> 00:40:06.349 align:start position:0% of just going straight intermediate and building<00:40:03.480> blocks<00:40:04.079> transactions 00:40:06.349 --> 00:40:06.359 align:start position:0% building blocks transactions 00:40:06.359 --> 00:40:07.790 align:start position:0% building blocks transactions all<00:40:06.780> right 00:40:07.790 --> 00:40:07.800 align:start position:0% all right 00:40:07.800 --> 00:40:09.950 align:start position:0% all right and<00:40:08.460> who's<00:40:08.820> thinking<00:40:09.180> of<00:40:09.420> trying<00:40:09.660> to 00:40:09.950 --> 00:40:09.960 align:start position:0% and who's thinking of trying to 00:40:09.960 --> 00:40:12.290 align:start position:0% and who's thinking of trying to implement<00:40:10.380> their<00:40:10.740> own<00:40:10.859> EIP<00:40:11.339> is<00:40:11.820> anyone 00:40:12.290 --> 00:40:12.300 align:start position:0% implement their own EIP is anyone 00:40:12.300 --> 00:40:16.550 align:start position:0% implement their own EIP is anyone motivated<00:40:13.260> all<00:40:14.160> right<00:40:14.339> awesome 00:40:16.550 --> 00:40:16.560 align:start position:0% motivated all right awesome 00:40:16.560 --> 00:40:19.790 align:start position:0% motivated all right awesome and<00:40:17.220> uh<00:40:17.579> what<00:40:18.180> about<00:40:18.359> running<00:40:18.780> the<00:40:19.140> client<00:40:19.440> or 00:40:19.790 --> 00:40:19.800 align:start position:0% and uh what about running the client or 00:40:19.800 --> 00:40:23.450 align:start position:0% and uh what about running the client or running<00:40:20.099> the<00:40:20.400> Shandong<00:40:20.940> test<00:40:21.180> net 00:40:23.450 --> 00:40:23.460 align:start position:0% 00:40:23.460 --> 00:40:25.550 align:start position:0% okay<00:40:23.880> yeah<00:40:24.119> so<00:40:24.359> I'll<00:40:24.540> just<00:40:24.780> be<00:40:24.960> going<00:40:25.200> through 00:40:25.550 --> 00:40:25.560 align:start position:0% okay yeah so I'll just be going through 00:40:25.560 --> 00:40:28.010 align:start position:0% okay yeah so I'll just be going through the<00:40:25.859> tutorial<00:40:26.460> as<00:40:27.060> well<00:40:27.180> in<00:40:27.540> front<00:40:27.720> since 00:40:28.010 --> 00:40:28.020 align:start position:0% the tutorial as well in front since 00:40:28.020 --> 00:40:29.930 align:start position:0% the tutorial as well in front since everyone<00:40:28.260> is<00:40:28.560> going<00:40:28.680> to<00:40:28.740> be<00:40:28.800> doing<00:40:28.980> that 00:40:29.930 --> 00:40:29.940 align:start position:0% everyone is going to be doing that 00:40:29.940 --> 00:40:31.310 align:start position:0% everyone is going to be doing that and<00:40:30.300> it's<00:40:30.480> going<00:40:30.599> to<00:40:30.720> be<00:40:30.780> more<00:40:30.900> interesting 00:40:31.310 --> 00:40:31.320 align:start position:0% and it's going to be more interesting 00:40:31.320 --> 00:40:32.450 align:start position:0% and it's going to be more interesting for 00:40:32.450 --> 00:40:32.460 align:start position:0% for 00:40:32.460 --> 00:40:34.250 align:start position:0% for people<00:40:32.940> who<00:40:33.180> watch<00:40:33.300> the<00:40:33.480> recording<00:40:33.900> rather 00:40:34.250 --> 00:40:34.260 align:start position:0% people who watch the recording rather 00:40:34.260 --> 00:40:35.810 align:start position:0% people who watch the recording rather than<00:40:34.380> just<00:40:34.619> looking<00:40:34.800> at<00:40:34.980> the<00:40:35.099> link<00:40:35.339> tree<00:40:35.579> for 00:40:35.810 --> 00:40:35.820 align:start position:0% than just looking at the link tree for 00:40:35.820 --> 00:40:40.790 align:start position:0% than just looking at the link tree for one<00:40:36.180> hour 00:40:40.790 --> 00:40:40.800 align:start position:0% 00:40:40.800 --> 00:40:43.910 align:start position:0% yeah<00:40:41.040> so<00:40:41.460> this<00:40:41.640> is<00:40:41.760> the<00:40:41.940> folder<00:40:42.300> that<00:40:42.900> you 00:40:43.910 --> 00:40:43.920 align:start position:0% yeah so this is the folder that you 00:40:43.920 --> 00:40:45.829 align:start position:0% yeah so this is the folder that you should<00:40:44.640> go<00:40:44.820> in<00:40:45.000> if<00:40:45.180> you<00:40:45.359> want<00:40:45.420> to<00:40:45.599> do<00:40:45.660> that 00:40:45.829 --> 00:40:45.839 align:start position:0% should go in if you want to do that 00:40:45.839 --> 00:40:48.410 align:start position:0% should go in if you want to do that tutorial<00:40:46.260> and<00:40:46.680> the<00:40:46.859> readme<00:40:47.220> is<00:40:47.880> is<00:40:48.119> you<00:40:48.359> know 00:40:48.410 --> 00:40:48.420 align:start position:0% tutorial and the readme is is you know 00:40:48.420 --> 00:40:51.710 align:start position:0% tutorial and the readme is is you know the<00:40:48.599> tutorial<00:40:49.020> itself<00:40:49.440> what<00:40:50.400> we<00:40:50.640> also<00:40:50.880> have<00:40:51.119> is 00:40:51.710 --> 00:40:51.720 align:start position:0% the tutorial itself what we also have is 00:40:51.720 --> 00:40:55.849 align:start position:0% the tutorial itself what we also have is a<00:40:51.960> set<00:40:52.200> of<00:40:52.320> examples<00:40:52.740> like<00:40:53.460> I<00:40:53.880> had<00:40:54.260> uh<00:40:55.260> written 00:40:55.849 --> 00:40:55.859 align:start position:0% a set of examples like I had uh written 00:40:55.859 --> 00:40:59.270 align:start position:0% a set of examples like I had uh written this<00:40:56.339> tutorial<00:40:56.820> in<00:40:57.119> JavaScript<00:40:57.960> just<00:40:58.859> so<00:40:59.040> that 00:40:59.270 --> 00:40:59.280 align:start position:0% this tutorial in JavaScript just so that 00:40:59.280 --> 00:41:01.250 align:start position:0% this tutorial in JavaScript just so that people<00:40:59.579> who<00:41:00.060> know<00:41:00.599> wanted<00:41:00.780> to<00:41:00.960> learn<00:41:01.079> about 00:41:01.250 --> 00:41:01.260 align:start position:0% people who know wanted to learn about 00:41:01.260 --> 00:41:02.690 align:start position:0% people who know wanted to learn about ethereum<00:41:01.680> didn't<00:41:01.920> know<00:41:02.099> about<00:41:02.220> typescript 00:41:02.690 --> 00:41:02.700 align:start position:0% ethereum didn't know about typescript 00:41:02.700 --> 00:41:05.630 align:start position:0% ethereum didn't know about typescript didn't<00:41:03.000> really<00:41:03.420> have<00:41:03.660> to<00:41:04.440> you<00:41:04.980> know<00:41:05.160> learn 00:41:05.630 --> 00:41:05.640 align:start position:0% didn't really have to you know learn 00:41:05.640 --> 00:41:07.730 align:start position:0% didn't really have to you know learn about<00:41:05.820> it<00:41:06.000> so<00:41:06.240> those<00:41:06.540> are<00:41:06.720> like<00:41:06.900> GS<00:41:07.260> files<00:41:07.619> that 00:41:07.730 --> 00:41:07.740 align:start position:0% about it so those are like GS files that 00:41:07.740 --> 00:41:11.870 align:start position:0% about it so those are like GS files that you<00:41:07.859> can<00:41:07.980> just<00:41:08.099> run<00:41:08.280> with<00:41:08.640> a<00:41:08.820> node 00:41:11.870 --> 00:41:11.880 align:start position:0% 00:41:11.880 --> 00:41:21.650 align:start position:0% let<00:41:12.240> me<00:41:12.780> check<00:41:13.260> out 00:41:21.650 --> 00:41:21.660 align:start position:0% 00:41:21.660 --> 00:41:25.069 align:start position:0% yeah<00:41:22.079> package<00:41:22.500> is<00:41:22.680> named<00:41:23.040> uh<00:41:23.280> try<00:41:23.660> so<00:41:24.660> once 00:41:25.069 --> 00:41:25.079 align:start position:0% yeah package is named uh try so once 00:41:25.079 --> 00:41:26.930 align:start position:0% yeah package is named uh try so once you've<00:41:25.320> uh 00:41:26.930 --> 00:41:26.940 align:start position:0% you've uh 00:41:26.940 --> 00:41:29.089 align:start position:0% you've uh let<00:41:27.420> me<00:41:27.599> actually<00:41:27.780> just<00:41:28.079> reinstall<00:41:28.619> since<00:41:28.920> the 00:41:29.089 --> 00:41:29.099 align:start position:0% let me actually just reinstall since the 00:41:29.099 --> 00:41:31.490 align:start position:0% let me actually just reinstall since the Shandong<00:41:29.640> thing<00:41:29.820> is<00:41:30.000> a<00:41:30.180> bit<00:41:30.300> uh 00:41:31.490 --> 00:41:31.500 align:start position:0% Shandong thing is a bit uh 00:41:31.500 --> 00:41:37.130 align:start position:0% Shandong thing is a bit uh a<00:41:31.859> bit<00:41:32.099> different 00:41:37.130 --> 00:41:37.140 align:start position:0% 00:41:37.140 --> 00:41:38.630 align:start position:0% yeah was<00:41:37.680> everyone<00:41:37.859> able<00:41:38.339> to<00:41:38.460> install 00:41:38.630 --> 00:41:38.640 align:start position:0% yeah was everyone able to install 00:41:38.640 --> 00:41:40.910 align:start position:0% yeah was everyone able to install successfully 00:41:40.910 --> 00:41:40.920 align:start position:0% successfully 00:41:40.920 --> 00:41:43.010 align:start position:0% successfully cool<00:41:41.460> no<00:41:41.760> issues 00:41:43.010 --> 00:41:43.020 align:start position:0% cool no issues 00:41:43.020 --> 00:41:44.210 align:start position:0% cool no issues huh 00:41:44.210 --> 00:41:44.220 align:start position:0% huh 00:41:44.220 --> 00:41:46.609 align:start position:0% huh you're<00:41:44.640> waiting<00:41:45.060> for<00:41:45.300> the<00:41:45.480> installation<00:41:45.839> all 00:41:46.609 --> 00:41:46.619 align:start position:0% you're waiting for the installation all 00:41:46.619 --> 00:41:47.990 align:start position:0% you're waiting for the installation all right<00:41:46.740> cool 00:41:47.990 --> 00:41:48.000 align:start position:0% right cool 00:41:48.000 --> 00:41:49.310 align:start position:0% right cool yeah<00:41:48.420> it<00:41:48.540> takes<00:41:48.720> a<00:41:48.839> while<00:41:48.960> because<00:41:49.140> it's 00:41:49.310 --> 00:41:49.320 align:start position:0% yeah it takes a while because it's 00:41:49.320 --> 00:42:01.430 align:start position:0% yeah it takes a while because it's building<00:41:49.500> every<00:41:49.800> package<00:41:50.220> so<00:41:50.640> uh<00:41:50.880> yeah 00:42:01.430 --> 00:42:01.440 align:start position:0% 00:42:01.440 --> 00:42:04.010 align:start position:0% uh<00:42:02.160> are<00:42:02.400> you<00:42:02.579> trying<00:42:02.820> to<00:42:03.060> run<00:42:03.300> uh<00:42:03.720> from<00:42:03.900> the 00:42:04.010 --> 00:42:04.020 align:start position:0% uh are you trying to run uh from the 00:42:04.020 --> 00:42:06.770 align:start position:0% uh are you trying to run uh from the monorepo<00:42:04.619> itself<00:42:04.800> npmram<00:42:05.520> test<00:42:05.760> uh<00:42:06.480> yeah<00:42:06.599> it 00:42:06.770 --> 00:42:06.780 align:start position:0% monorepo itself npmram test uh yeah it 00:42:06.780 --> 00:42:08.150 align:start position:0% monorepo itself npmram test uh yeah it might<00:42:06.960> be<00:42:07.079> just<00:42:07.320> because<00:42:07.680> there's<00:42:07.980> some 00:42:08.150 --> 00:42:08.160 align:start position:0% might be just because there's some 00:42:08.160 --> 00:42:10.670 align:start position:0% might be just because there's some modules<00:42:08.460> indeed<00:42:09.000> like<00:42:09.180> a<00:42:09.480> lot<00:42:09.660> of<00:42:09.780> the<00:42:09.900> uh<00:42:10.440> a 00:42:10.670 --> 00:42:10.680 align:start position:0% modules indeed like a lot of the uh a 00:42:10.680 --> 00:42:12.410 align:start position:0% modules indeed like a lot of the uh a lot<00:42:10.740> of<00:42:10.920> the<00:42:11.040> general<00:42:11.280> tests<00:42:11.760> we<00:42:11.940> have<00:42:12.060> depend 00:42:12.410 --> 00:42:12.420 align:start position:0% lot of the general tests we have depend 00:42:12.420 --> 00:42:15.710 align:start position:0% lot of the general tests we have depend on<00:42:12.599> that<00:42:12.780> those<00:42:13.320> sub<00:42:13.500> modules 00:42:15.710 --> 00:42:15.720 align:start position:0% on that those sub modules 00:42:15.720 --> 00:42:18.829 align:start position:0% on that those sub modules foreign 00:42:18.829 --> 00:42:18.839 align:start position:0% 00:42:18.839 --> 00:42:20.990 align:start position:0% yeah<00:42:19.500> they're<00:42:19.680> pretty<00:42:20.040> big<00:42:20.280> they're<00:42:20.760> pretty 00:42:20.990 --> 00:42:21.000 align:start position:0% yeah they're pretty big they're pretty 00:42:21.000 --> 00:42:23.150 align:start position:0% yeah they're pretty big they're pretty big<00:42:21.180> I<00:42:21.780> can't<00:42:22.140> say<00:42:22.380> for<00:42:22.500> sure<00:42:22.619> like<00:42:22.800> depending 00:42:23.150 --> 00:42:23.160 align:start position:0% big I can't say for sure like depending 00:42:23.160 --> 00:42:24.410 align:start position:0% big I can't say for sure like depending on<00:42:23.220> the<00:42:23.339> bandwidth<00:42:23.700> how<00:42:23.880> long<00:42:23.940> it's<00:42:24.060> going<00:42:24.300> to 00:42:24.410 --> 00:42:24.420 align:start position:0% on the bandwidth how long it's going to 00:42:24.420 --> 00:42:25.550 align:start position:0% on the bandwidth how long it's going to take 00:42:25.550 --> 00:42:25.560 align:start position:0% take 00:42:25.560 --> 00:42:27.410 align:start position:0% take my<00:42:26.160> own<00:42:26.280> machine<00:42:26.520> at<00:42:26.760> home<00:42:26.940> it<00:42:27.119> doesn't<00:42:27.300> take 00:42:27.410 --> 00:42:27.420 align:start position:0% my own machine at home it doesn't take 00:42:27.420 --> 00:42:29.390 align:start position:0% my own machine at home it doesn't take that<00:42:27.599> long<00:42:27.780> but<00:42:28.079> uh 00:42:29.390 --> 00:42:29.400 align:start position:0% that long but uh 00:42:29.400 --> 00:42:32.510 align:start position:0% that long but uh if<00:42:30.240> you<00:42:30.300> can<00:42:30.540> just<00:42:30.660> leave<00:42:31.020> it<00:42:31.260> running<00:42:31.859> and<00:42:32.220> see 00:42:32.510 --> 00:42:32.520 align:start position:0% if you can just leave it running and see 00:42:32.520 --> 00:42:43.370 align:start position:0% if you can just leave it running and see if 00:42:43.370 --> 00:42:43.380 align:start position:0% 00:42:43.380 --> 00:42:46.730 align:start position:0% oh<00:42:43.880> oh<00:42:44.880> that's<00:42:45.180> singular<00:42:45.480> test<00:42:45.780> okay 00:42:46.730 --> 00:42:46.740 align:start position:0% oh oh that's singular test okay 00:42:46.740 --> 00:42:48.349 align:start position:0% oh oh that's singular test okay uh 00:42:48.349 --> 00:42:48.359 align:start position:0% uh 00:42:48.359 --> 00:42:51.470 align:start position:0% uh let<00:42:48.900> me<00:42:49.020> give<00:42:49.200> you<00:42:49.320> an<00:42:49.500> example<00:42:49.800> of<00:42:50.160> running<00:42:50.400> a 00:42:51.470 --> 00:42:51.480 align:start position:0% let me give you an example of running a 00:42:51.480 --> 00:42:53.329 align:start position:0% let me give you an example of running a an<00:42:51.900> individual 00:42:53.329 --> 00:42:53.339 align:start position:0% an individual 00:42:53.339 --> 00:42:59.569 align:start position:0% an individual test<00:42:54.180> I'll<00:42:54.480> just<00:42:54.599> go 00:42:59.569 --> 00:42:59.579 align:start position:0% 00:42:59.579 --> 00:43:02.150 align:start position:0% okay<00:43:00.119> the<00:43:00.660> the<00:43:00.720> the<00:43:00.859> principle<00:43:01.859> is<00:43:01.980> going<00:43:02.099> to 00:43:02.150 --> 00:43:02.160 align:start position:0% okay the the the principle is going to 00:43:02.160 --> 00:43:03.589 align:start position:0% okay the the the principle is going to be<00:43:02.280> the<00:43:02.400> same<00:43:02.520> for<00:43:02.760> all<00:43:03.060> of<00:43:03.240> the<00:43:03.359> packages 00:43:03.589 --> 00:43:03.599 align:start position:0% be the same for all of the packages 00:43:03.599 --> 00:43:05.809 align:start position:0% be the same for all of the packages themselves<00:43:04.140> so<00:43:04.740> if<00:43:04.859> you<00:43:05.040> go<00:43:05.220> within<00:43:05.640> the 00:43:05.809 --> 00:43:05.819 align:start position:0% themselves so if you go within the 00:43:05.819 --> 00:43:07.670 align:start position:0% themselves so if you go within the individual<00:43:06.540> package<00:43:06.960> that<00:43:07.200> you're<00:43:07.319> trying<00:43:07.560> to 00:43:07.670 --> 00:43:07.680 align:start position:0% individual package that you're trying to 00:43:07.680 --> 00:43:11.510 align:start position:0% individual package that you're trying to run<00:43:07.800> the<00:43:07.980> test<00:43:08.160> in<00:43:08.339> just<00:43:08.940> do<00:43:09.180> npm<00:43:09.780> run<00:43:10.380> tape<00:43:10.920> and 00:43:11.510 --> 00:43:11.520 align:start position:0% run the test in just do npm run tape and 00:43:11.520 --> 00:43:13.010 align:start position:0% run the test in just do npm run tape and tape<00:43:11.760> is<00:43:11.880> like<00:43:12.060> the<00:43:12.240> testing<00:43:12.720> you<00:43:12.900> know 00:43:13.010 --> 00:43:13.020 align:start position:0% tape is like the testing you know 00:43:13.020 --> 00:43:15.890 align:start position:0% tape is like the testing you know framework<00:43:13.380> that<00:43:13.560> we<00:43:13.680> use<00:43:14.339> then<00:43:14.760> you<00:43:14.940> do<00:43:15.180> uh 00:43:15.890 --> 00:43:15.900 align:start position:0% framework that we use then you do uh 00:43:15.900 --> 00:43:18.349 align:start position:0% framework that we use then you do uh double<00:43:16.440> I<00:43:17.160> think<00:43:17.280> those<00:43:17.400> are<00:43:17.579> called<00:43:17.760> Dash<00:43:18.060> in 00:43:18.349 --> 00:43:18.359 align:start position:0% double I think those are called Dash in 00:43:18.359 --> 00:43:21.230 align:start position:0% double I think those are called Dash in English<00:43:18.480> I'm<00:43:18.780> not<00:43:18.900> even<00:43:19.020> sure<00:43:19.260> uh 00:43:21.230 --> 00:43:21.240 align:start position:0% English I'm not even sure uh 00:43:21.240 --> 00:43:22.990 align:start position:0% English I'm not even sure uh then 00:43:22.990 --> 00:43:23.000 align:start position:0% then 00:43:23.000 --> 00:43:25.970 align:start position:0% then test<00:43:24.000> to<00:43:24.540> look<00:43:24.720> at<00:43:24.839> the<00:43:24.960> test<00:43:25.079> folder<00:43:25.500> and<00:43:25.920> then 00:43:25.970 --> 00:43:25.980 align:start position:0% test to look at the test folder and then 00:43:25.980 --> 00:43:27.770 align:start position:0% test to look at the test folder and then you<00:43:26.160> just<00:43:26.280> select<00:43:26.520> the<00:43:26.640> file<00:43:26.880> basically<00:43:27.480> that 00:43:27.770 --> 00:43:27.780 align:start position:0% you just select the file basically that 00:43:27.780 --> 00:43:29.510 align:start position:0% you just select the file basically that you<00:43:28.140> uh 00:43:29.510 --> 00:43:29.520 align:start position:0% you uh 00:43:29.520 --> 00:43:31.490 align:start position:0% you uh that<00:43:30.000> you<00:43:30.060> want<00:43:30.180> to<00:43:30.300> run<00:43:30.420> right<00:43:30.900> so<00:43:31.140> if<00:43:31.319> I 00:43:31.490 --> 00:43:31.500 align:start position:0% that you want to run right so if I 00:43:31.500 --> 00:43:34.069 align:start position:0% that you want to run right so if I wanted<00:43:31.680> to<00:43:31.920> run<00:43:32.160> for<00:43:32.520> example<00:43:32.760> the 00:43:34.069 --> 00:43:34.079 align:start position:0% wanted to run for example the 00:43:34.079 --> 00:43:36.170 align:start position:0% wanted to run for example the I<00:43:34.440> don't<00:43:34.500> know<00:43:34.619> the<00:43:34.800> the<00:43:34.980> proof<00:43:35.579> that<00:43:35.880> spec 00:43:36.170 --> 00:43:36.180 align:start position:0% I don't know the the proof that spec 00:43:36.180 --> 00:43:40.550 align:start position:0% I don't know the the proof that spec test<00:43:36.599> I<00:43:37.020> would<00:43:37.140> just 00:43:40.550 --> 00:43:40.560 align:start position:0% 00:43:40.560 --> 00:43:42.650 align:start position:0% do<00:43:40.920> that<00:43:41.160> and<00:43:41.579> it's<00:43:41.700> going<00:43:41.880> to<00:43:41.940> run<00:43:42.119> that<00:43:42.359> test 00:43:42.650 --> 00:43:42.660 align:start position:0% do that and it's going to run that test 00:43:42.660 --> 00:43:46.010 align:start position:0% do that and it's going to run that test individually<00:43:43.640> if<00:43:44.640> you<00:43:44.819> do<00:43:44.940> npm<00:43:45.420> run<00:43:45.599> tests 00:43:46.010 --> 00:43:46.020 align:start position:0% individually if you do npm run tests 00:43:46.020 --> 00:43:48.530 align:start position:0% individually if you do npm run tests it's<00:43:46.140> just<00:43:46.319> gonna<00:43:46.560> run<00:43:46.920> like<00:43:47.460> a<00:43:47.760> massive<00:43:48.119> Suite 00:43:48.530 --> 00:43:48.540 align:start position:0% it's just gonna run like a massive Suite 00:43:48.540 --> 00:43:51.770 align:start position:0% it's just gonna run like a massive Suite of<00:43:49.800> um<00:43:50.339> of<00:43:50.880> tests<00:43:51.240> including<00:43:51.599> like 00:43:51.770 --> 00:43:51.780 align:start position:0% of um of tests including like 00:43:51.780 --> 00:43:53.450 align:start position:0% of um of tests including like integration<00:43:52.200> tests<00:43:52.560> that<00:43:52.619> depend<00:43:52.859> on<00:43:52.980> browser 00:43:53.450 --> 00:43:53.460 align:start position:0% integration tests that depend on browser 00:43:53.460 --> 00:43:55.250 align:start position:0% integration tests that depend on browser integration<00:43:53.819> stuff<00:43:54.180> like<00:43:54.300> that<00:43:54.480> and<00:43:54.839> that's 00:43:55.250 --> 00:43:55.260 align:start position:0% integration stuff like that and that's 00:43:55.260 --> 00:43:57.589 align:start position:0% integration stuff like that and that's typically<00:43:55.859> like<00:43:56.099> super<00:43:56.339> long<00:43:56.579> we<00:43:57.240> only<00:43:57.359> do 00:43:57.589 --> 00:43:57.599 align:start position:0% typically like super long we only do 00:43:57.599 --> 00:44:00.230 align:start position:0% typically like super long we only do that<00:43:57.720> like<00:43:57.960> in<00:43:58.079> the<00:43:58.440> CI<00:43:58.680> once<00:43:59.099> in<00:43:59.160> a<00:43:59.280> while<00:43:59.339> but 00:44:00.230 --> 00:44:00.240 align:start position:0% that like in the CI once in a while but 00:44:00.240 --> 00:44:03.050 align:start position:0% that like in the CI once in a while but locally<00:44:00.720> it's<00:44:00.900> a<00:44:01.020> bit<00:44:01.079> tedious<00:44:01.500> so<00:44:02.339> and<00:44:02.700> yeah 00:44:03.050 --> 00:44:03.060 align:start position:0% locally it's a bit tedious so and yeah 00:44:03.060 --> 00:44:05.650 align:start position:0% locally it's a bit tedious so and yeah then<00:44:03.359> you<00:44:03.540> see<00:44:03.720> the<00:44:03.900> the<00:44:04.140> result<00:44:04.800> of<00:44:04.980> the<00:44:05.099> test 00:44:05.650 --> 00:44:05.660 align:start position:0% then you see the the result of the test 00:44:05.660 --> 00:44:08.690 align:start position:0% then you see the the result of the test it<00:44:06.660> passes 00:44:08.690 --> 00:44:08.700 align:start position:0% it passes 00:44:08.700 --> 00:44:12.470 align:start position:0% it passes so<00:44:09.359> let<00:44:09.540> me<00:44:09.720> close<00:44:10.079> that<00:44:10.260> up 00:44:12.470 --> 00:44:12.480 align:start position:0% 00:44:12.480 --> 00:44:15.890 align:start position:0% all<00:44:13.020> right<00:44:13.200> so<00:44:13.980> let<00:44:14.160> me<00:44:14.339> open<00:44:14.640> up<00:44:14.940> the<00:44:15.480> tutorial 00:44:15.890 --> 00:44:15.900 align:start position:0% all right so let me open up the tutorial 00:44:15.900 --> 00:44:23.630 align:start position:0% all right so let me open up the tutorial again 00:44:23.630 --> 00:44:23.640 align:start position:0% 00:44:23.640 --> 00:44:25.670 align:start position:0% all<00:44:23.940> right<00:44:24.119> so<00:44:24.240> there's<00:44:24.540> you<00:44:25.079> know<00:44:25.200> a<00:44:25.380> bit<00:44:25.500> of 00:44:25.670 --> 00:44:25.680 align:start position:0% all right so there's you know a bit of 00:44:25.680 --> 00:44:28.010 align:start position:0% all right so there's you know a bit of preliminary<00:44:26.220> info<00:44:26.819> that<00:44:27.240> you<00:44:27.420> might<00:44:27.599> want<00:44:27.839> to 00:44:28.010 --> 00:44:28.020 align:start position:0% preliminary info that you might want to 00:44:28.020 --> 00:44:28.970 align:start position:0% preliminary info that you might want to read 00:44:28.970 --> 00:44:28.980 align:start position:0% read 00:44:28.980 --> 00:44:30.890 align:start position:0% read um<00:44:29.280> uh<00:44:29.579> you<00:44:29.760> know<00:44:29.880> data<00:44:30.540> structure<00:44:30.780> of 00:44:30.890 --> 00:44:30.900 align:start position:0% um uh you know data structure of 00:44:30.900 --> 00:44:32.990 align:start position:0% um uh you know data structure of ethereum<00:44:31.260> is<00:44:31.440> called<00:44:31.560> a<00:44:31.619> miracle<00:44:31.980> pituitary 00:44:32.990 --> 00:44:33.000 align:start position:0% ethereum is called a miracle pituitary 00:44:33.000 --> 00:44:35.150 align:start position:0% ethereum is called a miracle pituitary it's<00:44:33.599> a<00:44:33.839> basically<00:44:34.200> a<00:44:34.319> combination<00:44:34.740> of<00:44:34.859> a 00:44:35.150 --> 00:44:35.160 align:start position:0% it's a basically a combination of a 00:44:35.160 --> 00:44:37.490 align:start position:0% it's a basically a combination of a myrtle<00:44:35.579> tree<00:44:35.760> and<00:44:36.060> a<00:44:36.180> picture<00:44:36.300> should<00:44:36.599> try<00:44:36.839> a 00:44:37.490 --> 00:44:37.500 align:start position:0% myrtle tree and a picture should try a 00:44:37.500 --> 00:44:39.410 align:start position:0% myrtle tree and a picture should try a try<00:44:37.800> is<00:44:37.980> a<00:44:38.099> data<00:44:38.460> structure<00:44:38.700> in<00:44:38.819> which<00:44:39.000> Keys 00:44:39.410 --> 00:44:39.420 align:start position:0% try is a data structure in which Keys 00:44:39.420 --> 00:44:41.870 align:start position:0% try is a data structure in which Keys represent<00:44:39.780> the<00:44:39.960> path<00:44:40.200> leading<00:44:40.680> to<00:44:40.920> a<00:44:41.160> specific 00:44:41.870 --> 00:44:41.880 align:start position:0% represent the path leading to a specific 00:44:41.880 --> 00:44:44.569 align:start position:0% represent the path leading to a specific node<00:44:42.480> and<00:44:43.020> the<00:44:43.200> mergle<00:44:43.560> tree<00:44:43.740> is<00:44:44.099> a<00:44:44.220> structure 00:44:44.569 --> 00:44:44.579 align:start position:0% node and the mergle tree is a structure 00:44:44.579 --> 00:44:48.410 align:start position:0% node and the mergle tree is a structure in<00:44:44.700> which<00:44:44.940> a<00:44:45.240> parent<00:44:45.800> node<00:44:47.000> the<00:44:48.000> key<00:44:48.119> of<00:44:48.300> that 00:44:48.410 --> 00:44:48.420 align:start position:0% in which a parent node the key of that 00:44:48.420 --> 00:44:51.230 align:start position:0% in which a parent node the key of that is<00:44:48.900> the<00:44:49.200> hash<00:44:49.560> of<00:44:49.800> the<00:44:49.980> all<00:44:50.579> the<00:44:50.760> child<00:44:50.880> nodes 00:44:51.230 --> 00:44:51.240 align:start position:0% is the hash of the all the child nodes 00:44:51.240 --> 00:44:54.349 align:start position:0% is the hash of the all the child nodes uh<00:44:52.020> Miracle<00:44:52.500> 3<00:44:52.619> is<00:44:52.920> interesting<00:44:53.460> because<00:44:53.819> if 00:44:54.349 --> 00:44:54.359 align:start position:0% uh Miracle 3 is interesting because if 00:44:54.359 --> 00:44:55.730 align:start position:0% uh Miracle 3 is interesting because if you<00:44:54.480> want<00:44:54.599> to<00:44:54.720> prove<00:44:54.960> that<00:44:55.140> the<00:44:55.260> certain<00:44:55.500> value 00:44:55.730 --> 00:44:55.740 align:start position:0% you want to prove that the certain value 00:44:55.740 --> 00:44:58.130 align:start position:0% you want to prove that the certain value is<00:44:56.040> part<00:44:56.220> of<00:44:56.400> the<00:44:56.520> data<00:44:56.940> at<00:44:57.480> the<00:44:57.720> large<00:44:57.839> Market 00:44:58.130 --> 00:44:58.140 align:start position:0% is part of the data at the large Market 00:44:58.140 --> 00:45:00.050 align:start position:0% is part of the data at the large Market restructure<00:44:58.859> that<00:44:58.980> you<00:44:59.099> have<00:44:59.220> you<00:44:59.640> can<00:44:59.760> do<00:44:59.940> so 00:45:00.050 --> 00:45:00.060 align:start position:0% restructure that you have you can do so 00:45:00.060 --> 00:45:02.630 align:start position:0% restructure that you have you can do so by<00:45:00.420> providing<00:45:00.960> a<00:45:01.680> bunch<00:45:01.920> of<00:45:02.099> like<00:45:02.280> sister 00:45:02.630 --> 00:45:02.640 align:start position:0% by providing a bunch of like sister 00:45:02.640 --> 00:45:03.530 align:start position:0% by providing a bunch of like sister nodes 00:45:03.530 --> 00:45:03.540 align:start position:0% nodes 00:45:03.540 --> 00:45:06.950 align:start position:0% nodes we'll<00:45:04.200> see<00:45:04.440> uh<00:45:05.220> that<00:45:05.579> super<00:45:05.880> clearly<00:45:06.300> in<00:45:06.720> the 00:45:06.950 --> 00:45:06.960 align:start position:0% we'll see uh that super clearly in the 00:45:06.960 --> 00:45:08.630 align:start position:0% we'll see uh that super clearly in the tutorial<00:45:07.740> itself 00:45:08.630 --> 00:45:08.640 align:start position:0% tutorial itself 00:45:08.640 --> 00:45:10.069 align:start position:0% tutorial itself so<00:45:09.000> yeah<00:45:09.119> the<00:45:09.420> instructions<00:45:09.780> are<00:45:09.900> here 00:45:10.069 --> 00:45:10.079 align:start position:0% so yeah the instructions are here 00:45:10.079 --> 00:45:11.870 align:start position:0% so yeah the instructions are here they're<00:45:10.260> the<00:45:10.500> same<00:45:10.619> that<00:45:10.800> you've<00:45:11.099> just<00:45:11.280> ran<00:45:11.520> so 00:45:11.870 --> 00:45:11.880 align:start position:0% they're the same that you've just ran so 00:45:11.880 --> 00:45:13.849 align:start position:0% they're the same that you've just ran so clone<00:45:12.180> the<00:45:12.300> model<00:45:12.420> repo 00:45:13.849 --> 00:45:13.859 align:start position:0% clone the model repo 00:45:13.859 --> 00:45:17.030 align:start position:0% clone the model repo um<00:45:13.920> install<00:45:14.880> it<00:45:15.240> and<00:45:15.900> then<00:45:16.020> go<00:45:16.380> inside<00:45:16.560> of<00:45:16.920> that 00:45:17.030 --> 00:45:17.040 align:start position:0% um install it and then go inside of that 00:45:17.040 --> 00:45:19.849 align:start position:0% um install it and then go inside of that try<00:45:17.520> package 00:45:19.849 --> 00:45:19.859 align:start position:0% try package 00:45:19.859 --> 00:45:21.410 align:start position:0% try package so<00:45:20.099> I'll<00:45:20.280> Bing<00:45:20.520> going<00:45:20.700> through<00:45:20.940> these<00:45:21.240> like 00:45:21.410 --> 00:45:21.420 align:start position:0% so I'll Bing going through these like 00:45:21.420 --> 00:45:23.930 align:start position:0% so I'll Bing going through these like fairly<00:45:22.020> you<00:45:22.500> know<00:45:22.560> slowly<00:45:22.920> so<00:45:23.280> feel<00:45:23.520> free<00:45:23.700> if 00:45:23.930 --> 00:45:23.940 align:start position:0% fairly you know slowly so feel free if 00:45:23.940 --> 00:45:26.329 align:start position:0% fairly you know slowly so feel free if you're<00:45:24.240> you<00:45:24.900> know<00:45:25.020> want<00:45:25.260> to<00:45:25.440> go<00:45:25.619> a<00:45:25.980> bit<00:45:26.099> faster 00:45:26.329 --> 00:45:26.339 align:start position:0% you're you know want to go a bit faster 00:45:26.339 --> 00:45:28.849 align:start position:0% you're you know want to go a bit faster to<00:45:26.880> just<00:45:27.119> go<00:45:27.420> forward<00:45:27.599> and<00:45:27.960> don't<00:45:28.260> let<00:45:28.500> me<00:45:28.680> like 00:45:28.849 --> 00:45:28.859 align:start position:0% to just go forward and don't let me like 00:45:28.859 --> 00:45:30.589 align:start position:0% to just go forward and don't let me like slow<00:45:29.160> you<00:45:29.339> down 00:45:30.589 --> 00:45:30.599 align:start position:0% slow you down 00:45:30.599 --> 00:45:33.290 align:start position:0% slow you down but<00:45:31.380> the<00:45:31.680> so<00:45:31.920> the<00:45:32.099> first<00:45:32.220> example<00:45:32.640> we're<00:45:33.180> going 00:45:33.290 --> 00:45:33.300 align:start position:0% but the so the first example we're going 00:45:33.300 --> 00:45:35.349 align:start position:0% but the so the first example we're going to<00:45:33.420> use<00:45:33.599> the<00:45:33.900> try<00:45:34.319> you<00:45:34.680> know<00:45:34.800> library<00:45:35.040> before 00:45:35.349 --> 00:45:35.359 align:start position:0% to use the try you know library before 00:45:35.359 --> 00:45:39.349 align:start position:0% to use the try you know library before is<00:45:36.359> uh<00:45:36.599> creating<00:45:36.960> and<00:45:37.319> updating<00:45:37.880> uh<00:45:38.880> a<00:45:39.240> base 00:45:39.349 --> 00:45:39.359 align:start position:0% is uh creating and updating uh a base 00:45:39.359 --> 00:45:40.190 align:start position:0% is uh creating and updating uh a base Drive 00:45:40.190 --> 00:45:40.200 align:start position:0% Drive 00:45:40.200 --> 00:45:43.250 align:start position:0% Drive so<00:45:40.859> what<00:45:41.099> does<00:45:41.220> that<00:45:41.400> look<00:45:41.579> like<00:45:41.780> so<00:45:42.780> first<00:45:43.079> of 00:45:43.250 --> 00:45:43.260 align:start position:0% so what does that look like so first of 00:45:43.260 --> 00:45:46.490 align:start position:0% so what does that look like so first of all<00:45:43.319> we're<00:45:43.619> importing<00:45:44.220> the<00:45:44.819> try<00:45:45.140> uh<00:45:46.140> class 00:45:46.490 --> 00:45:46.500 align:start position:0% all we're importing the try uh class 00:45:46.500 --> 00:45:49.609 align:start position:0% all we're importing the try uh class from<00:45:47.280> the<00:45:47.460> the<00:45:47.640> try<00:45:47.880> package<00:45:48.420> and<00:45:49.200> we<00:45:49.319> can<00:45:49.440> look 00:45:49.609 --> 00:45:49.619 align:start position:0% from the the try package and we can look 00:45:49.619 --> 00:45:51.530 align:start position:0% from the the try package and we can look at<00:45:49.800> what<00:45:50.099> you<00:45:50.579> know<00:45:50.640> that<00:45:50.940> looks<00:45:51.240> like<00:45:51.300> it's 00:45:51.530 --> 00:45:51.540 align:start position:0% at what you know that looks like it's 00:45:51.540 --> 00:45:56.230 align:start position:0% at what you know that looks like it's probably<00:45:51.839> like<00:45:52.140> try<00:45:52.560> file<00:45:52.980> yeah 00:45:56.230 --> 00:45:56.240 align:start position:0% 00:45:56.240 --> 00:45:59.150 align:start position:0% so<00:45:57.240> try<00:45:57.420> is<00:45:57.599> simply<00:45:57.900> a<00:45:58.079> class 00:45:59.150 --> 00:45:59.160 align:start position:0% so try is simply a class 00:45:59.160 --> 00:46:02.270 align:start position:0% so try is simply a class and<00:45:59.819> uh<00:46:00.119> you<00:46:00.420> know<00:46:00.540> it<00:46:00.660> has<00:46:00.839> a<00:46:01.200> bunch<00:46:02.160> of 00:46:02.270 --> 00:46:02.280 align:start position:0% and uh you know it has a bunch of 00:46:02.280 --> 00:46:04.790 align:start position:0% and uh you know it has a bunch of properties<00:46:02.640> that<00:46:02.940> you<00:46:03.060> would<00:46:03.180> expect<00:46:03.560> uh<00:46:04.560> on 00:46:04.790 --> 00:46:04.800 align:start position:0% properties that you would expect uh on 00:46:04.800 --> 00:46:07.790 align:start position:0% properties that you would expect uh on the<00:46:04.980> you<00:46:05.280> know<00:46:05.339> database<00:46:05.940> like<00:46:06.480> structure<00:46:07.140> it 00:46:07.790 --> 00:46:07.800 align:start position:0% the you know database like structure it 00:46:07.800 --> 00:46:12.470 align:start position:0% the you know database like structure it does<00:46:07.980> use<00:46:08.220> like<00:46:08.700> uh<00:46:09.839> checkpoint<00:46:10.500> DB<00:46:10.800> is<00:46:11.040> a 00:46:12.470 --> 00:46:12.480 align:start position:0% does use like uh checkpoint DB is a 00:46:12.480 --> 00:46:14.990 align:start position:0% does use like uh checkpoint DB is a as<00:46:13.020> like<00:46:13.319> a<00:46:13.740> database<00:46:14.099> and<00:46:14.460> then<00:46:14.640> you<00:46:14.880> can 00:46:14.990 --> 00:46:15.000 align:start position:0% as like a database and then you can 00:46:15.000 --> 00:46:16.910 align:start position:0% as like a database and then you can provide<00:46:15.240> options<00:46:15.660> for<00:46:15.900> the<00:46:16.020> tree<00:46:16.260> so<00:46:16.619> some<00:46:16.800> of 00:46:16.910 --> 00:46:16.920 align:start position:0% provide options for the tree so some of 00:46:16.920 --> 00:46:19.490 align:start position:0% provide options for the tree so some of the<00:46:17.040> options<00:46:17.339> are<00:46:17.819> uh<00:46:18.720> do<00:46:18.960> you<00:46:19.140> want<00:46:19.260> to<00:46:19.380> use 00:46:19.490 --> 00:46:19.500 align:start position:0% the options are uh do you want to use 00:46:19.500 --> 00:46:21.589 align:start position:0% the options are uh do you want to use this<00:46:19.859> specific<00:46:20.160> type<00:46:20.520> of<00:46:20.700> keys<00:46:21.240> you<00:46:21.359> want<00:46:21.480> to 00:46:21.589 --> 00:46:21.599 align:start position:0% this specific type of keys you want to 00:46:21.599 --> 00:46:23.990 align:start position:0% this specific type of keys you want to use<00:46:21.839> like<00:46:22.140> plank<00:46:22.440> keys<00:46:22.800> or<00:46:23.040> hashed<00:46:23.460> Keys<00:46:23.760> like 00:46:23.990 --> 00:46:24.000 align:start position:0% use like plank keys or hashed Keys like 00:46:24.000 --> 00:46:27.710 align:start position:0% use like plank keys or hashed Keys like are<00:46:24.540> what<00:46:25.440> is<00:46:25.560> used<00:46:25.740> in<00:46:26.040> ethereum<00:46:26.819> then<00:46:27.480> we 00:46:27.710 --> 00:46:27.720 align:start position:0% are what is used in ethereum then we 00:46:27.720 --> 00:46:29.329 align:start position:0% are what is used in ethereum then we instantiate<00:46:28.200> database<00:46:28.680> you<00:46:28.920> could<00:46:29.040> provide 00:46:29.329 --> 00:46:29.339 align:start position:0% instantiate database you could provide 00:46:29.339 --> 00:46:31.430 align:start position:0% instantiate database you could provide like<00:46:29.640> your<00:46:30.000> own<00:46:30.119> database<00:46:30.540> here<00:46:31.020> where<00:46:31.260> you're 00:46:31.430 --> 00:46:31.440 align:start position:0% like your own database here where you're 00:46:31.440 --> 00:46:35.930 align:start position:0% like your own database here where you're instantiating<00:46:31.920> a<00:46:32.220> new<00:46:32.339> like<00:46:32.520> map<00:46:32.700> DB<00:46:33.540> and<00:46:34.500> um 00:46:35.930 --> 00:46:35.940 align:start position:0% instantiating a new like map DB and um 00:46:35.940 --> 00:46:39.170 align:start position:0% instantiating a new like map DB and um yeah<00:46:36.780> instantiating<00:46:37.500> a<00:46:37.920> new<00:46:38.160> tree<00:46:38.400> when<00:46:38.819> we 00:46:39.170 --> 00:46:39.180 align:start position:0% yeah instantiating a new tree when we 00:46:39.180 --> 00:46:42.230 align:start position:0% yeah instantiating a new tree when we you<00:46:39.540> know<00:46:39.660> construct<00:46:40.140> a<00:46:41.040> tree<00:46:41.520> with<00:46:41.880> the<00:46:41.940> tree 00:46:42.230 --> 00:46:42.240 align:start position:0% you know construct a tree with the tree 00:46:42.240 --> 00:46:44.809 align:start position:0% you know construct a tree with the tree class<00:46:42.740> and<00:46:43.740> you<00:46:43.980> can<00:46:44.099> see<00:46:44.220> you<00:46:44.400> have<00:46:44.460> a<00:46:44.579> set<00:46:44.700> of 00:46:44.809 --> 00:46:44.819 align:start position:0% class and you can see you have a set of 00:46:44.819 --> 00:46:46.730 align:start position:0% class and you can see you have a set of methods<00:46:45.180> here<00:46:45.359> you<00:46:45.660> can<00:46:45.839> for<00:46:46.020> example<00:46:46.319> you 00:46:46.730 --> 00:46:46.740 align:start position:0% methods here you can for example you 00:46:46.740 --> 00:46:50.530 align:start position:0% methods here you can for example you know<00:46:46.859> get<00:46:47.400> the<00:46:48.119> root<00:46:48.680> of<00:46:49.680> the<00:46:49.800> tree 00:46:50.530 --> 00:46:50.540 align:start position:0% know get the root of the tree 00:46:50.540 --> 00:46:54.050 align:start position:0% know get the root of the tree you<00:46:51.540> can<00:46:51.660> verify<00:46:52.079> if<00:46:52.619> a<00:46:52.859> certain<00:46:53.160> route<00:46:53.460> exists 00:46:54.050 --> 00:46:54.060 align:start position:0% you can verify if a certain route exists 00:46:54.060 --> 00:46:56.630 align:start position:0% you can verify if a certain route exists you<00:46:54.480> can<00:46:54.660> get<00:46:55.140> those<00:46:55.500> are<00:46:55.740> like<00:46:56.220> these<00:46:56.579> two 00:46:56.630 --> 00:46:56.640 align:start position:0% you can get those are like these two 00:46:56.640 --> 00:46:57.890 align:start position:0% you can get those are like these two methods<00:46:57.060> or<00:46:57.119> the<00:46:57.240> ones<00:46:57.420> we're<00:46:57.540> going<00:46:57.720> to<00:46:57.780> be 00:46:57.890 --> 00:46:57.900 align:start position:0% methods or the ones we're going to be 00:46:57.900 --> 00:47:00.050 align:start position:0% methods or the ones we're going to be using<00:46:58.140> the<00:46:58.319> most<00:46:58.440> so<00:46:58.980> we<00:46:59.220> have<00:46:59.339> a<00:46:59.460> get<00:46:59.579> method 00:47:00.050 --> 00:47:00.060 align:start position:0% using the most so we have a get method 00:47:00.060 --> 00:47:03.530 align:start position:0% using the most so we have a get method to<00:47:00.660> retrieve<00:47:01.140> a<00:47:01.319> value<00:47:01.640> by<00:47:02.640> providing<00:47:03.119> a<00:47:03.420> key 00:47:03.530 --> 00:47:03.540 align:start position:0% to retrieve a value by providing a key 00:47:03.540 --> 00:47:06.790 align:start position:0% to retrieve a value by providing a key and<00:47:04.200> then<00:47:04.319> we<00:47:04.560> have<00:47:04.800> a<00:47:05.339> put 00:47:06.790 --> 00:47:06.800 align:start position:0% and then we have a put 00:47:06.800 --> 00:47:10.250 align:start position:0% and then we have a put a<00:47:07.800> put<00:47:08.040> method<00:47:08.520> which<00:47:09.180> stores<00:47:09.540> a<00:47:09.780> given<00:47:10.079> value 00:47:10.250 --> 00:47:10.260 align:start position:0% a put method which stores a given value 00:47:10.260 --> 00:47:13.250 align:start position:0% a put method which stores a given value at<00:47:10.920> a<00:47:11.099> specific<00:47:11.400> key<00:47:11.640> so<00:47:12.000> fairly<00:47:12.420> standard<00:47:12.960> you 00:47:13.250 --> 00:47:13.260 align:start position:0% at a specific key so fairly standard you 00:47:13.260 --> 00:47:15.589 align:start position:0% at a specific key so fairly standard you know<00:47:13.319> database<00:47:13.920> stuff<00:47:14.160> but<00:47:15.000> this<00:47:15.300> is<00:47:15.359> going<00:47:15.540> to 00:47:15.589 --> 00:47:15.599 align:start position:0% know database stuff but this is going to 00:47:15.599 --> 00:47:17.329 align:start position:0% know database stuff but this is going to give<00:47:15.720> us<00:47:15.839> insight<00:47:16.200> into<00:47:16.380> how<00:47:16.800> you<00:47:17.040> know<00:47:17.160> the 00:47:17.329 --> 00:47:17.339 align:start position:0% give us insight into how you know the 00:47:17.339 --> 00:47:19.730 align:start position:0% give us insight into how you know the that<00:47:17.700> actual<00:47:18.119> data<00:47:18.540> structure<00:47:18.839> works<00:47:19.200> because 00:47:19.730 --> 00:47:19.740 align:start position:0% that actual data structure works because 00:47:19.740 --> 00:47:22.849 align:start position:0% that actual data structure works because it's<00:47:20.040> not<00:47:20.220> like<00:47:20.520> a<00:47:20.640> simple<00:47:20.760> database 00:47:22.849 --> 00:47:22.859 align:start position:0% it's not like a simple database 00:47:22.859 --> 00:47:25.430 align:start position:0% it's not like a simple database so<00:47:23.280> let<00:47:23.460> me<00:47:23.579> go<00:47:23.700> back<00:47:23.819> to<00:47:23.940> the<00:47:24.060> tutorial<00:47:24.480> so<00:47:25.260> the 00:47:25.430 --> 00:47:25.440 align:start position:0% so let me go back to the tutorial so the 00:47:25.440 --> 00:47:27.470 align:start position:0% so let me go back to the tutorial so the first<00:47:25.560> thing<00:47:25.859> we're<00:47:26.280> gonna<00:47:26.520> do<00:47:27.180> is<00:47:27.300> like 00:47:27.470 --> 00:47:27.480 align:start position:0% first thing we're gonna do is like 00:47:27.480 --> 00:47:31.490 align:start position:0% first thing we're gonna do is like instantiate<00:47:28.079> uh<00:47:28.500> the<00:47:28.680> tree<00:47:28.859> so<00:47:29.460> I'll<00:47:29.700> go<00:47:30.300> to<00:47:31.200> I 00:47:31.490 --> 00:47:31.500 align:start position:0% instantiate uh the tree so I'll go to I 00:47:31.500 --> 00:47:33.950 align:start position:0% instantiate uh the tree so I'll go to I think<00:47:31.619> it's<00:47:31.800> example<00:47:32.339> one<00:47:32.640> a 00:47:33.950 --> 00:47:33.960 align:start position:0% think it's example one a 00:47:33.960 --> 00:47:36.890 align:start position:0% think it's example one a yeah<00:47:34.380> I'm<00:47:34.859> just<00:47:34.980> gonna<00:47:35.160> comment<00:47:35.520> that 00:47:36.890 --> 00:47:36.900 align:start position:0% yeah I'm just gonna comment that 00:47:36.900 --> 00:47:42.290 align:start position:0% yeah I'm just gonna comment that out 00:47:42.290 --> 00:47:42.300 align:start position:0% 00:47:42.300 --> 00:47:43.370 align:start position:0% so<00:47:42.599> yeah 00:47:43.370 --> 00:47:43.380 align:start position:0% so yeah 00:47:43.380 --> 00:47:45.589 align:start position:0% so yeah to<00:47:43.680> run<00:47:43.800> a<00:47:44.040> specific<00:47:44.280> example<00:47:44.760> you're<00:47:45.359> just 00:47:45.589 --> 00:47:45.599 align:start position:0% to run a specific example you're just 00:47:45.599 --> 00:47:48.950 align:start position:0% to run a specific example you're just gonna<00:47:45.780> go<00:47:46.200> uh<00:47:46.920> node<00:47:47.400> examples<00:47:48.119> and<00:47:48.780> for 00:47:48.950 --> 00:47:48.960 align:start position:0% gonna go uh node examples and for 00:47:48.960 --> 00:47:53.210 align:start position:0% gonna go uh node examples and for example<00:47:49.200> example<00:47:49.859> one 00:47:53.210 --> 00:47:53.220 align:start position:0% 00:47:53.220 --> 00:47:56.150 align:start position:0% am<00:47:53.520> I<00:47:53.700> doing<00:47:53.880> yes<00:47:54.300> typo 00:47:56.150 --> 00:47:56.160 align:start position:0% am I doing yes typo 00:47:56.160 --> 00:47:59.329 align:start position:0% am I doing yes typo oh<00:47:56.579> it's<00:47:56.700> within<00:47:57.180> Merkel<00:47:57.660> trees<00:47:58.560> and<00:47:58.680> then 00:47:59.329 --> 00:47:59.339 align:start position:0% oh it's within Merkel trees and then 00:47:59.339 --> 00:48:01.670 align:start position:0% oh it's within Merkel trees and then example<00:48:00.180> one<00:48:00.720> a 00:48:01.670 --> 00:48:01.680 align:start position:0% example one a 00:48:01.680 --> 00:48:05.750 align:start position:0% example one a there<00:48:02.099> we<00:48:02.280> go<00:48:02.720> so<00:48:03.720> this<00:48:04.380> all<00:48:05.160> I'm<00:48:05.460> going<00:48:05.579> to<00:48:05.700> be 00:48:05.750 --> 00:48:05.760 align:start position:0% there we go so this all I'm going to be 00:48:05.760 --> 00:48:07.370 align:start position:0% there we go so this all I'm going to be doing<00:48:05.940> here<00:48:06.240> as<00:48:06.960> you<00:48:07.079> can<00:48:07.140> see<00:48:07.260> is 00:48:07.370 --> 00:48:07.380 align:start position:0% doing here as you can see is 00:48:07.380 --> 00:48:09.770 align:start position:0% doing here as you can see is instantiating<00:48:08.099> a<00:48:08.579> new<00:48:08.700> tree 00:48:09.770 --> 00:48:09.780 align:start position:0% instantiating a new tree 00:48:09.780 --> 00:48:13.370 align:start position:0% instantiating a new tree uh<00:48:10.500> with<00:48:10.740> you<00:48:11.040> know<00:48:11.160> the<00:48:11.640> the<00:48:11.819> try<00:48:12.599> package 00:48:13.370 --> 00:48:13.380 align:start position:0% uh with you know the the try package 00:48:13.380 --> 00:48:16.190 align:start position:0% uh with you know the the try package from<00:48:13.680> the<00:48:13.740> model<00:48:13.920> repo<00:48:14.400> and<00:48:15.119> then<00:48:15.240> logging<00:48:15.900> the 00:48:16.190 --> 00:48:16.200 align:start position:0% from the model repo and then logging the 00:48:16.200 --> 00:48:17.450 align:start position:0% from the model repo and then logging the root<00:48:16.500> of<00:48:16.619> that<00:48:16.740> tree 00:48:17.450 --> 00:48:17.460 align:start position:0% root of that tree 00:48:17.460 --> 00:48:19.370 align:start position:0% root of that tree and<00:48:17.940> this<00:48:18.180> is<00:48:18.300> going<00:48:18.420> to<00:48:18.599> give<00:48:18.720> us<00:48:18.900> the<00:48:19.260> the 00:48:19.370 --> 00:48:19.380 align:start position:0% and this is going to give us the the 00:48:19.380 --> 00:48:22.010 align:start position:0% and this is going to give us the the root<00:48:20.160> of<00:48:20.220> the<00:48:20.400> tree<00:48:20.579> which<00:48:21.060> is<00:48:21.240> uh<00:48:21.599> you<00:48:21.900> can 00:48:22.010 --> 00:48:22.020 align:start position:0% root of the tree which is uh you can 00:48:22.020 --> 00:48:23.450 align:start position:0% root of the tree which is uh you can look<00:48:22.140> up<00:48:22.260> in<00:48:22.440> the<00:48:22.560> Docks<00:48:22.800> but<00:48:22.920> it's<00:48:23.099> basically 00:48:23.450 --> 00:48:23.460 align:start position:0% look up in the Docks but it's basically 00:48:23.460 --> 00:48:27.710 align:start position:0% look up in the Docks but it's basically that<00:48:23.940> uh<00:48:24.480> the<00:48:25.440> the<00:48:25.800> the<00:48:25.980> encoding<00:48:26.940> of<00:48:27.300> uh<00:48:27.480> I 00:48:27.710 --> 00:48:27.720 align:start position:0% that uh the the the encoding of uh I 00:48:27.720 --> 00:48:29.750 align:start position:0% that uh the the the encoding of uh I think<00:48:27.780> an<00:48:27.960> empty<00:48:28.260> array 00:48:29.750 --> 00:48:29.760 align:start position:0% think an empty array 00:48:29.760 --> 00:48:32.809 align:start position:0% think an empty array um<00:48:29.819> rlp<00:48:30.480> encoding<00:48:30.839> of<00:48:30.960> an<00:48:31.020> empty<00:48:31.260> array 00:48:32.809 --> 00:48:32.819 align:start position:0% um rlp encoding of an empty array 00:48:32.819 --> 00:48:35.870 align:start position:0% um rlp encoding of an empty array so<00:48:33.359> yeah<00:48:33.540> we<00:48:33.900> see<00:48:34.079> like<00:48:34.560> pretty<00:48:35.099> fast<00:48:35.339> we<00:48:35.700> see 00:48:35.870 --> 00:48:35.880 align:start position:0% so yeah we see like pretty fast we see 00:48:35.880 --> 00:48:39.230 align:start position:0% so yeah we see like pretty fast we see we<00:48:36.060> output<00:48:36.359> a<00:48:36.480> buffer<00:48:36.839> which<00:48:37.740> is<00:48:37.980> a<00:48:38.819> uh<00:48:39.000> which 00:48:39.230 --> 00:48:39.240 align:start position:0% we output a buffer which is a uh which 00:48:39.240 --> 00:48:40.370 align:start position:0% we output a buffer which is a uh which is<00:48:39.359> that 00:48:40.370 --> 00:48:40.380 align:start position:0% is that 00:48:40.380 --> 00:48:42.170 align:start position:0% is that now<00:48:40.859> that<00:48:40.980> doesn't<00:48:41.220> tell<00:48:41.460> us<00:48:41.640> a<00:48:41.760> whole<00:48:41.880> lot<00:48:42.000> but 00:48:42.170 --> 00:48:42.180 align:start position:0% now that doesn't tell us a whole lot but 00:48:42.180 --> 00:48:44.270 align:start position:0% now that doesn't tell us a whole lot but we<00:48:42.359> could<00:48:42.480> look<00:48:42.900> up<00:48:43.020> in<00:48:43.200> the<00:48:43.319> docs<00:48:43.619> and<00:48:43.800> see 00:48:44.270 --> 00:48:44.280 align:start position:0% we could look up in the docs and see 00:48:44.280 --> 00:48:46.069 align:start position:0% we could look up in the docs and see that<00:48:44.460> this<00:48:44.700> is<00:48:44.880> actually<00:48:45.060> exactly<00:48:45.599> what<00:48:45.780> we'd 00:48:46.069 --> 00:48:46.079 align:start position:0% that this is actually exactly what we'd 00:48:46.079 --> 00:48:49.550 align:start position:0% that this is actually exactly what we'd expect<00:48:46.200> in<00:48:47.160> uh<00:48:47.460> as<00:48:48.060> the<00:48:48.240> root<00:48:48.480> of<00:48:48.599> Genesis<00:48:49.380> like 00:48:49.550 --> 00:48:49.560 align:start position:0% expect in uh as the root of Genesis like 00:48:49.560 --> 00:48:52.309 align:start position:0% expect in uh as the root of Genesis like root<00:48:49.859> of<00:48:49.980> a<00:48:50.220> of<00:48:50.819> a<00:48:51.060> try<00:48:51.240> like<00:48:51.480> data<00:48:51.960> data 00:48:52.309 --> 00:48:52.319 align:start position:0% root of a of a try like data data 00:48:52.319 --> 00:48:53.809 align:start position:0% root of a of a try like data data structure 00:48:53.809 --> 00:48:53.819 align:start position:0% structure 00:48:53.819 --> 00:48:55.670 align:start position:0% structure so<00:48:54.119> then<00:48:54.240> we're<00:48:54.480> going<00:48:54.599> to<00:48:54.660> move<00:48:54.780> on<00:48:54.960> to<00:48:55.200> a<00:48:55.440> more 00:48:55.670 --> 00:48:55.680 align:start position:0% so then we're going to move on to a more 00:48:55.680 --> 00:48:56.690 align:start position:0% so then we're going to move on to a more you<00:48:56.099> know 00:48:56.690 --> 00:48:56.700 align:start position:0% you know 00:48:56.700 --> 00:49:00.530 align:start position:0% you know a<00:48:57.119> more<00:48:57.300> interesting<00:48:57.720> test<00:48:57.960> I'd<00:48:58.680> say 00:49:00.530 --> 00:49:00.540 align:start position:0% a more interesting test I'd say 00:49:00.540 --> 00:49:03.530 align:start position:0% a more interesting test I'd say we're<00:49:01.079> gonna<00:49:01.260> we're<00:49:01.740> gonna<00:49:01.920> try<00:49:02.280> to<00:49:02.579> just<00:49:03.060> put 00:49:03.530 --> 00:49:03.540 align:start position:0% we're gonna we're gonna try to just put 00:49:03.540 --> 00:49:05.690 align:start position:0% we're gonna we're gonna try to just put a<00:49:03.660> value<00:49:03.780> in<00:49:04.079> it<00:49:04.200> and<00:49:04.680> see<00:49:04.800> if<00:49:04.980> we<00:49:05.160> can<00:49:05.339> actually 00:49:05.690 --> 00:49:05.700 align:start position:0% a value in it and see if we can actually 00:49:05.700 --> 00:49:07.910 align:start position:0% a value in it and see if we can actually retrieve<00:49:06.240> it<00:49:06.359> another<00:49:07.020> thing<00:49:07.319> we're<00:49:07.560> also 00:49:07.910 --> 00:49:07.920 align:start position:0% retrieve it another thing we're also 00:49:07.920 --> 00:49:10.609 align:start position:0% retrieve it another thing we're also gonna<00:49:08.040> be<00:49:08.520> able<00:49:08.700> to<00:49:08.819> see<00:49:09.119> is<00:49:09.300> uh<00:49:09.660> how<00:49:10.020> the<00:49:10.260> the 00:49:10.609 --> 00:49:10.619 align:start position:0% gonna be able to see is uh how the the 00:49:10.619 --> 00:49:13.790 align:start position:0% gonna be able to see is uh how the the route<00:49:10.859> you<00:49:11.400> know<00:49:11.520> has<00:49:11.940> been<00:49:12.119> updated<00:49:12.900> given 00:49:13.790 --> 00:49:13.800 align:start position:0% route you know has been updated given 00:49:13.800 --> 00:49:16.069 align:start position:0% route you know has been updated given that 00:49:16.069 --> 00:49:16.079 align:start position:0% 00:49:16.079 --> 00:49:18.650 align:start position:0% so<00:49:16.680> yeah<00:49:17.099> what<00:49:17.280> do<00:49:17.400> we<00:49:17.520> do<00:49:17.640> here<00:49:17.819> we're 00:49:18.650 --> 00:49:18.660 align:start position:0% so yeah what do we do here we're 00:49:18.660 --> 00:49:21.050 align:start position:0% so yeah what do we do here we're creating<00:49:19.079> a<00:49:19.319> key<00:49:19.440> I<00:49:19.740> mean<00:49:19.920> a<00:49:20.220> try<00:49:20.579> natively 00:49:21.050 --> 00:49:21.060 align:start position:0% creating a key I mean a try natively 00:49:21.060 --> 00:49:22.730 align:start position:0% creating a key I mean a try natively uses<00:49:21.359> buffers<00:49:21.720> so<00:49:21.900> we're<00:49:22.079> doing<00:49:22.200> like<00:49:22.380> buffer 00:49:22.730 --> 00:49:22.740 align:start position:0% uses buffers so we're doing like buffer 00:49:22.740 --> 00:49:25.089 align:start position:0% uses buffers so we're doing like buffer from<00:49:22.920> for<00:49:23.220> for<00:49:23.339> all<00:49:23.819> of<00:49:24.000> these 00:49:25.089 --> 00:49:25.099 align:start position:0% from for for all of these 00:49:25.099 --> 00:49:28.309 align:start position:0% from for for all of these so<00:49:26.099> we're<00:49:26.460> having<00:49:26.940> test<00:49:27.359> key<00:49:27.599> that's<00:49:28.079> going<00:49:28.260> to 00:49:28.309 --> 00:49:28.319 align:start position:0% so we're having test key that's going to 00:49:28.319 --> 00:49:30.530 align:start position:0% so we're having test key that's going to be<00:49:28.440> your<00:49:28.560> key<00:49:28.740> and<00:49:29.160> we<00:49:29.400> have<00:49:29.520> test<00:49:29.760> value<00:49:30.060> this 00:49:30.530 --> 00:49:30.540 align:start position:0% be your key and we have test value this 00:49:30.540 --> 00:49:32.450 align:start position:0% be your key and we have test value this is<00:49:30.599> going<00:49:30.720> to<00:49:30.780> be<00:49:30.839> our<00:49:31.020> value<00:49:31.200> and<00:49:31.800> then<00:49:31.980> we're 00:49:32.450 --> 00:49:32.460 align:start position:0% is going to be our value and then we're 00:49:32.460 --> 00:49:34.370 align:start position:0% is going to be our value and then we're doing<00:49:32.760> an<00:49:32.940> asynchronous<00:49:33.420> operation<00:49:33.900> like 00:49:34.370 --> 00:49:34.380 align:start position:0% doing an asynchronous operation like 00:49:34.380 --> 00:49:37.430 align:start position:0% doing an asynchronous operation like putting<00:49:35.040> that<00:49:35.880> key<00:49:36.240> value<00:49:36.420> pair<00:49:36.780> inside<00:49:37.140> of 00:49:37.430 --> 00:49:37.440 align:start position:0% putting that key value pair inside of 00:49:37.440 --> 00:49:38.390 align:start position:0% putting that key value pair inside of the<00:49:37.560> try 00:49:38.390 --> 00:49:38.400 align:start position:0% the try 00:49:38.400 --> 00:49:40.069 align:start position:0% the try and<00:49:38.940> then<00:49:39.060> we're<00:49:39.180> going<00:49:39.359> to<00:49:39.420> try<00:49:39.599> to<00:49:39.720> retrieve 00:49:40.069 --> 00:49:40.079 align:start position:0% and then we're going to try to retrieve 00:49:40.079 --> 00:49:42.589 align:start position:0% and then we're going to try to retrieve that<00:49:40.260> value<00:49:40.440> fairly<00:49:41.280> simple<00:49:41.460> what<00:49:42.300> we<00:49:42.480> should 00:49:42.589 --> 00:49:42.599 align:start position:0% that value fairly simple what we should 00:49:42.599 --> 00:49:45.530 align:start position:0% that value fairly simple what we should expect<00:49:42.780> here<00:49:43.200> is<00:49:44.040> a<00:49:44.640> uh<00:49:44.940> so<00:49:45.119> what<00:49:45.240> should<00:49:45.420> be 00:49:45.530 --> 00:49:45.540 align:start position:0% expect here is a uh so what should be 00:49:45.540 --> 00:49:47.630 align:start position:0% expect here is a uh so what should be the<00:49:45.660> value<00:49:45.780> well<00:49:46.140> it<00:49:46.380> should<00:49:46.500> be<00:49:46.619> the<00:49:46.800> you<00:49:47.520> know 00:49:47.630 --> 00:49:47.640 align:start position:0% the value well it should be the you know 00:49:47.640 --> 00:49:50.870 align:start position:0% the value well it should be the you know the<00:49:48.060> encoded<00:49:48.660> version<00:49:49.099> uh<00:49:50.099> the<00:49:50.400> buffer<00:49:50.700> from 00:49:50.870 --> 00:49:50.880 align:start position:0% the encoded version uh the buffer from 00:49:50.880 --> 00:49:52.849 align:start position:0% the encoded version uh the buffer from version<00:49:51.060> of<00:49:51.359> uh<00:49:51.599> test<00:49:51.900> value 00:49:52.849 --> 00:49:52.859 align:start position:0% version of uh test value 00:49:52.859 --> 00:49:54.950 align:start position:0% version of uh test value and<00:49:53.220> the<00:49:53.400> value<00:49:53.520> string<00:49:54.000> we<00:49:54.359> should<00:49:54.480> expect<00:49:54.660> to 00:49:54.950 --> 00:49:54.960 align:start position:0% and the value string we should expect to 00:49:54.960 --> 00:49:56.690 align:start position:0% and the value string we should expect to see<00:49:55.140> value<00:49:55.560> and<00:49:55.980> if<00:49:56.160> we<00:49:56.339> don't<00:49:56.460> there's 00:49:56.690 --> 00:49:56.700 align:start position:0% see value and if we don't there's 00:49:56.700 --> 00:49:58.550 align:start position:0% see value and if we don't there's there's<00:49:56.940> been<00:49:57.180> an<00:49:57.359> issue<00:49:57.599> either<00:49:57.900> you<00:49:58.319> know<00:49:58.380> in 00:49:58.550 --> 00:49:58.560 align:start position:0% there's been an issue either you know in 00:49:58.560 --> 00:50:00.890 align:start position:0% there's been an issue either you know in the<00:49:58.680> library<00:49:58.859> or<00:49:59.339> in<00:49:59.520> the<00:49:59.640> way<00:49:59.819> we've<00:50:00.180> used<00:50:00.660> it 00:50:00.890 --> 00:50:00.900 align:start position:0% the library or in the way we've used it 00:50:00.900 --> 00:50:03.290 align:start position:0% the library or in the way we've used it it<00:50:01.560> should<00:50:01.800> also<00:50:02.040> update<00:50:02.280> the<00:50:02.460> tree<00:50:02.579> root<00:50:02.940> so 00:50:03.290 --> 00:50:03.300 align:start position:0% it should also update the tree root so 00:50:03.300 --> 00:50:05.930 align:start position:0% it should also update the tree root so one<00:50:03.540> thing<00:50:03.660> I'm<00:50:03.900> gonna<00:50:04.079> do<00:50:04.380> is<00:50:05.040> I'm<00:50:05.280> gonna<00:50:05.400> also 00:50:05.930 --> 00:50:05.940 align:start position:0% one thing I'm gonna do is I'm gonna also 00:50:05.940 --> 00:50:12.650 align:start position:0% one thing I'm gonna do is I'm gonna also log 00:50:12.650 --> 00:50:12.660 align:start position:0% 00:50:12.660 --> 00:50:17.089 align:start position:0% the<00:50:13.079> try<00:50:13.260> route<00:50:13.500> before 00:50:17.089 --> 00:50:17.099 align:start position:0% 00:50:17.099 --> 00:50:19.609 align:start position:0% and<00:50:17.579> what<00:50:17.760> we<00:50:17.880> should<00:50:18.060> expect<00:50:18.180> is<00:50:18.900> uh<00:50:19.260> like 00:50:19.609 --> 00:50:19.619 align:start position:0% and what we should expect is uh like 00:50:19.619 --> 00:50:22.370 align:start position:0% and what we should expect is uh like each<00:50:20.040> Merkel<00:50:20.760> Patricia<00:50:21.240> Street<00:50:21.359> like<00:50:21.780> each 00:50:22.370 --> 00:50:22.380 align:start position:0% each Merkel Patricia Street like each 00:50:22.380 --> 00:50:24.650 align:start position:0% each Merkel Patricia Street like each state<00:50:22.859> tree<00:50:23.460> should<00:50:23.940> always<00:50:24.119> have<00:50:24.420> a 00:50:24.650 --> 00:50:24.660 align:start position:0% state tree should always have a 00:50:24.660 --> 00:50:27.589 align:start position:0% state tree should always have a different<00:50:24.839> uh<00:50:25.560> hash<00:50:25.859> if<00:50:26.220> it<00:50:26.700> differs<00:50:27.180> and<00:50:27.420> if 00:50:27.589 --> 00:50:27.599 align:start position:0% different uh hash if it differs and if 00:50:27.599 --> 00:50:30.349 align:start position:0% different uh hash if it differs and if it's<00:50:27.720> the<00:50:27.900> same<00:50:28.020> it<00:50:28.200> should<00:50:28.380> always<00:50:29.000> uh<00:50:30.000> have 00:50:30.349 --> 00:50:30.359 align:start position:0% it's the same it should always uh have 00:50:30.359 --> 00:50:33.290 align:start position:0% it's the same it should always uh have the<00:50:30.599> the<00:50:30.839> same<00:50:31.500> so<00:50:32.099> let's<00:50:32.220> try<00:50:32.460> running<00:50:33.000> this 00:50:33.290 --> 00:50:33.300 align:start position:0% the the same so let's try running this 00:50:33.300 --> 00:50:35.569 align:start position:0% the the same so let's try running this again 00:50:35.569 --> 00:50:35.579 align:start position:0% 00:50:35.579 --> 00:50:37.309 align:start position:0% so<00:50:36.000> what<00:50:36.119> do<00:50:36.300> we<00:50:36.420> have<00:50:36.540> here 00:50:37.309 --> 00:50:37.319 align:start position:0% so what do we have here 00:50:37.319 --> 00:50:40.609 align:start position:0% so what do we have here we<00:50:37.800> start<00:50:37.920> out<00:50:38.040> with<00:50:38.339> a<00:50:38.520> empty<00:50:39.200> try<00:50:40.200> route<00:50:40.380> yeah 00:50:40.609 --> 00:50:40.619 align:start position:0% we start out with a empty try route yeah 00:50:40.619 --> 00:50:42.589 align:start position:0% we start out with a empty try route yeah we<00:50:40.800> had<00:50:40.920> logged<00:50:41.220> that<00:50:41.280> before<00:50:41.460> actually<00:50:41.760> so 00:50:42.589 --> 00:50:42.599 align:start position:0% we had logged that before actually so 00:50:42.599 --> 00:50:44.210 align:start position:0% we had logged that before actually so the<00:50:42.780> try<00:50:42.960> route<00:50:43.140> before<00:50:43.380> you<00:50:43.800> know<00:50:43.859> is<00:50:43.980> the 00:50:44.210 --> 00:50:44.220 align:start position:0% the try route before you know is the 00:50:44.220 --> 00:50:47.089 align:start position:0% the try route before you know is the same<00:50:44.280> we<00:50:44.520> just<00:50:44.760> logged<00:50:45.180> the<00:50:45.359> same<00:50:45.480> thing<00:50:45.540> twice 00:50:47.089 --> 00:50:47.099 align:start position:0% same we just logged the same thing twice 00:50:47.099 --> 00:50:49.910 align:start position:0% same we just logged the same thing twice the<00:50:47.819> value<00:50:48.000> that<00:50:48.300> we've<00:50:48.540> retrieved<00:50:48.960> is<00:50:49.380> it's 00:50:49.910 --> 00:50:49.920 align:start position:0% the value that we've retrieved is it's 00:50:49.920 --> 00:50:52.549 align:start position:0% the value that we've retrieved is it's this<00:50:50.280> if<00:50:50.940> you<00:50:51.119> are<00:50:51.300> familiar<00:50:51.660> with<00:50:51.960> the<00:50:52.140> you 00:50:52.549 --> 00:50:52.559 align:start position:0% this if you are familiar with the you 00:50:52.559 --> 00:50:55.010 align:start position:0% this if you are familiar with the you know<00:50:52.680> this<00:50:52.859> just<00:50:53.160> uh<00:50:53.400> the<00:50:53.640> hex<00:50:54.240> correspondence 00:50:55.010 --> 00:50:55.020 align:start position:0% know this just uh the hex correspondence 00:50:55.020 --> 00:50:57.109 align:start position:0% know this just uh the hex correspondence for<00:50:55.380> all<00:50:55.680> of<00:50:55.859> the 00:50:57.109 --> 00:50:57.119 align:start position:0% for all of the 00:50:57.119 --> 00:51:00.950 align:start position:0% for all of the all<00:50:57.420> of<00:50:57.660> the<00:50:57.839> characters<00:50:58.680> and<00:50:59.579> then<00:50:59.640> if<00:50:59.940> we<00:51:00.420> uh 00:51:00.950 --> 00:51:00.960 align:start position:0% all of the characters and then if we uh 00:51:00.960 --> 00:51:02.690 align:start position:0% all of the characters and then if we uh convert<00:51:01.380> that<00:51:01.440> to<00:51:01.619> a<00:51:01.800> string<00:51:01.980> we<00:51:02.280> get<00:51:02.400> back<00:51:02.520> to 00:51:02.690 --> 00:51:02.700 align:start position:0% convert that to a string we get back to 00:51:02.700 --> 00:51:04.490 align:start position:0% convert that to a string we get back to this<00:51:02.880> value<00:51:03.059> this<00:51:03.660> is<00:51:03.839> exactly<00:51:04.200> what<00:51:04.319> we 00:51:04.490 --> 00:51:04.500 align:start position:0% this value this is exactly what we 00:51:04.500 --> 00:51:07.430 align:start position:0% this value this is exactly what we expect<00:51:04.880> then<00:51:05.880> we<00:51:06.180> see<00:51:06.300> that<00:51:06.540> the<00:51:06.839> try<00:51:07.140> route 00:51:07.430 --> 00:51:07.440 align:start position:0% expect then we see that the try route 00:51:07.440 --> 00:51:10.010 align:start position:0% expect then we see that the try route has<00:51:08.160> you<00:51:08.520> know<00:51:08.579> massively<00:51:09.059> changed<00:51:09.420> as<00:51:09.599> you 00:51:10.010 --> 00:51:10.020 align:start position:0% has you know massively changed as you 00:51:10.020 --> 00:51:11.990 align:start position:0% has you know massively changed as you would<00:51:10.140> expect<00:51:10.260> from<00:51:10.800> uh<00:51:11.160> any<00:51:11.400> kind<00:51:11.520> of<00:51:11.640> hashing 00:51:11.990 --> 00:51:12.000 align:start position:0% would expect from uh any kind of hashing 00:51:12.000 --> 00:51:14.450 align:start position:0% would expect from uh any kind of hashing if<00:51:12.359> it<00:51:12.540> differs<00:51:12.900> slightly<00:51:13.319> totally<00:51:14.160> different 00:51:14.450 --> 00:51:14.460 align:start position:0% if it differs slightly totally different 00:51:14.460 --> 00:51:16.190 align:start position:0% if it differs slightly totally different random<00:51:15.059> result 00:51:16.190 --> 00:51:16.200 align:start position:0% random result 00:51:16.200 --> 00:51:19.190 align:start position:0% random result all<00:51:16.680> right<00:51:16.680> that<00:51:17.460> clear<00:51:17.700> to<00:51:18.359> everybody<00:51:18.660> does 00:51:19.190 --> 00:51:19.200 align:start position:0% all right that clear to everybody does 00:51:19.200 --> 00:51:22.190 align:start position:0% all right that clear to everybody does that<00:51:19.440> feel<00:51:19.619> intuitive 00:51:22.190 --> 00:51:22.200 align:start position:0% that feel intuitive 00:51:22.200 --> 00:51:23.450 align:start position:0% that feel intuitive okay 00:51:23.450 --> 00:51:23.460 align:start position:0% okay 00:51:23.460 --> 00:51:51.290 align:start position:0% okay yeah<00:51:23.760> any<00:51:24.300> questions 00:51:51.290 --> 00:51:51.300 align:start position:0% 00:51:51.300 --> 00:51:54.650 align:start position:0% I<00:51:51.780> know<00:51:51.960> we're<00:51:52.200> always<00:51:52.380> at<00:51:52.859> so<00:51:53.640> a<00:51:53.940> normal<00:51:54.359> tree 00:51:54.650 --> 00:51:54.660 align:start position:0% I know we're always at so a normal tree 00:51:54.660 --> 00:51:56.690 align:start position:0% I know we're always at so a normal tree so<00:51:55.079> this<00:51:55.260> is<00:51:55.380> the<00:51:55.619> actual<00:51:55.859> Myrtle<00:51:56.400> Beach 00:51:56.690 --> 00:51:56.700 align:start position:0% so this is the actual Myrtle Beach 00:51:56.700 --> 00:51:59.049 align:start position:0% so this is the actual Myrtle Beach history<00:51:56.940> like<00:51:57.480> data<00:51:57.839> structure<00:51:58.200> that<00:51:58.559> we'd<00:51:58.800> be 00:51:59.049 --> 00:51:59.059 align:start position:0% history like data structure that we'd be 00:51:59.059 --> 00:52:01.370 align:start position:0% history like data structure that we'd be uh<00:52:00.059> that<00:52:00.420> would<00:52:00.540> be<00:52:00.599> used<00:52:00.720> like<00:52:00.900> in<00:52:01.079> production 00:52:01.370 --> 00:52:01.380 align:start position:0% uh that would be used like in production 00:52:01.380 --> 00:52:03.530 align:start position:0% uh that would be used like in production with<00:52:01.680> ethereum<00:52:02.099> the<00:52:02.579> the<00:52:02.880> only<00:52:03.180> slight 00:52:03.530 --> 00:52:03.540 align:start position:0% with ethereum the the only slight 00:52:03.540 --> 00:52:06.170 align:start position:0% with ethereum the the only slight difference<00:52:03.780> is<00:52:04.260> that<00:52:04.559> uh<00:52:05.099> Merkel<00:52:05.760> Patricia 00:52:06.170 --> 00:52:06.180 align:start position:0% difference is that uh Merkel Patricia 00:52:06.180 --> 00:52:08.089 align:start position:0% difference is that uh Merkel Patricia trees<00:52:06.420> use<00:52:06.720> like<00:52:06.960> hash<00:52:07.260> keys<00:52:07.680> so<00:52:07.800> instead<00:52:08.040> of 00:52:08.089 --> 00:52:08.099 align:start position:0% trees use like hash keys so instead of 00:52:08.099 --> 00:52:09.589 align:start position:0% trees use like hash keys so instead of using<00:52:08.339> the<00:52:08.460> key<00:52:08.579> we'd<00:52:08.940> use<00:52:09.000> like<00:52:09.240> the<00:52:09.420> the 00:52:09.589 --> 00:52:09.599 align:start position:0% using the key we'd use like the the 00:52:09.599 --> 00:52:12.710 align:start position:0% using the key we'd use like the the hashed<00:52:10.380> version<00:52:10.680> of<00:52:11.160> that<00:52:11.520> key<00:52:11.760> and<00:52:12.420> this<00:52:12.660> is 00:52:12.710 --> 00:52:12.720 align:start position:0% hashed version of that key and this is 00:52:12.720 --> 00:52:14.210 align:start position:0% hashed version of that key and this is only<00:52:12.839> to<00:52:13.140> balance<00:52:13.380> out<00:52:13.559> the<00:52:13.740> tree<00:52:13.859> so<00:52:14.099> that 00:52:14.210 --> 00:52:14.220 align:start position:0% only to balance out the tree so that 00:52:14.220 --> 00:52:15.650 align:start position:0% only to balance out the tree so that there's<00:52:14.339> no<00:52:14.520> Vector<00:52:14.880> of<00:52:14.940> attack<00:52:15.119> where<00:52:15.480> you 00:52:15.650 --> 00:52:15.660 align:start position:0% there's no Vector of attack where you 00:52:15.660 --> 00:52:17.750 align:start position:0% there's no Vector of attack where you always<00:52:15.780> update<00:52:16.319> like<00:52:16.619> values<00:52:17.280> in<00:52:17.400> a<00:52:17.520> similar 00:52:17.750 --> 00:52:17.760 align:start position:0% always update like values in a similar 00:52:17.760 --> 00:52:19.370 align:start position:0% always update like values in a similar region<00:52:18.059> and<00:52:18.240> make<00:52:18.420> it<00:52:18.540> more<00:52:18.660> costly<00:52:19.020> for<00:52:19.200> those 00:52:19.370 --> 00:52:19.380 align:start position:0% region and make it more costly for those 00:52:19.380 --> 00:52:23.089 align:start position:0% region and make it more costly for those to<00:52:19.680> run<00:52:19.800> operations<00:52:20.599> uh<00:52:21.599> the<00:52:22.140> so<00:52:22.619> what<00:52:22.859> I<00:52:22.980> think 00:52:23.089 --> 00:52:23.099 align:start position:0% to run operations uh the so what I think 00:52:23.099 --> 00:52:25.190 align:start position:0% to run operations uh the so what I think your<00:52:23.280> question<00:52:23.520> is<00:52:23.760> is<00:52:24.059> you<00:52:24.540> know<00:52:24.660> there<00:52:24.960> are 00:52:25.190 --> 00:52:25.200 align:start position:0% your question is is you know there are 00:52:25.200 --> 00:52:28.069 align:start position:0% your question is is you know there are there's<00:52:26.040> a<00:52:26.520> if<00:52:26.940> you<00:52:27.119> had<00:52:27.300> a<00:52:27.420> normal<00:52:27.599> little 00:52:28.069 --> 00:52:28.079 align:start position:0% there's a if you had a normal little 00:52:28.079 --> 00:52:29.870 align:start position:0% there's a if you had a normal little structure<00:52:28.619> like<00:52:28.740> this<00:52:28.980> you<00:52:29.579> would<00:52:29.700> always 00:52:29.870 --> 00:52:29.880 align:start position:0% structure like this you would always 00:52:29.880 --> 00:52:32.150 align:start position:0% structure like this you would always like<00:52:30.240> Traverse<00:52:30.900> every<00:52:31.440> single<00:52:31.680> loan<00:52:31.980> would 00:52:32.150 --> 00:52:32.160 align:start position:0% like Traverse every single loan would 00:52:32.160 --> 00:52:35.030 align:start position:0% like Traverse every single loan would only<00:52:32.400> give<00:52:32.579> you<00:52:32.700> one<00:52:32.940> hex<00:52:33.240> right<00:52:33.740> because<00:52:34.740> it's 00:52:35.030 --> 00:52:35.040 align:start position:0% only give you one hex right because it's 00:52:35.040 --> 00:52:38.210 align:start position:0% only give you one hex right because it's a<00:52:35.220> 16<00:52:35.760> like<00:52:36.180> width<00:52:36.660> tree 00:52:38.210 --> 00:52:38.220 align:start position:0% a 16 like width tree 00:52:38.220 --> 00:52:41.030 align:start position:0% a 16 like width tree so<00:52:38.700> if<00:52:38.880> you<00:52:39.000> have<00:52:39.119> a<00:52:39.300> key<00:52:39.480> of<00:52:40.020> like<00:52:40.319> uh<00:52:40.740> you<00:52:40.980> know 00:52:41.030 --> 00:52:41.040 align:start position:0% so if you have a key of like uh you know 00:52:41.040 --> 00:52:43.250 align:start position:0% so if you have a key of like uh you know 32<00:52:41.460> bytes<00:52:41.880> then<00:52:42.119> you<00:52:42.300> would<00:52:42.420> Traverse<00:52:42.839> like 00:52:43.250 --> 00:52:43.260 align:start position:0% 32 bytes then you would Traverse like 00:52:43.260 --> 00:52:45.170 align:start position:0% 32 bytes then you would Traverse like all<00:52:43.500> these<00:52:43.859> nodes<00:52:44.099> on<00:52:44.400> the<00:52:44.700> way<00:52:44.819> down<00:52:45.000> there 00:52:45.170 --> 00:52:45.180 align:start position:0% all these nodes on the way down there 00:52:45.180 --> 00:52:47.270 align:start position:0% all these nodes on the way down there now<00:52:45.720> Merkel<00:52:46.200> Patricia<00:52:46.619> trees<00:52:46.920> are<00:52:47.040> more 00:52:47.270 --> 00:52:47.280 align:start position:0% now Merkel Patricia trees are more 00:52:47.280 --> 00:52:49.670 align:start position:0% now Merkel Patricia trees are more efficient<00:52:47.880> than<00:52:48.119> that<00:52:48.300> because<00:52:48.660> if<00:52:49.140> if<00:52:49.440> they 00:52:49.670 --> 00:52:49.680 align:start position:0% efficient than that because if if they 00:52:49.680 --> 00:52:50.990 align:start position:0% efficient than that because if if they know<00:52:49.859> that<00:52:50.040> given<00:52:50.339> a<00:52:50.460> certain<00:52:50.520> path<00:52:50.819> there's 00:52:50.990 --> 00:52:51.000 align:start position:0% know that given a certain path there's 00:52:51.000 --> 00:52:52.970 align:start position:0% know that given a certain path there's only<00:52:51.240> one<00:52:51.599> possible<00:52:51.900> path<00:52:52.200> down<00:52:52.440> they're 00:52:52.970 --> 00:52:52.980 align:start position:0% only one possible path down they're 00:52:52.980 --> 00:52:55.250 align:start position:0% only one possible path down they're gonna<00:52:53.160> create<00:52:53.460> what's<00:52:53.819> called<00:52:54.059> uh<00:52:54.599> an 00:52:55.250 --> 00:52:55.260 align:start position:0% gonna create what's called uh an 00:52:55.260 --> 00:52:57.170 align:start position:0% gonna create what's called uh an extension<00:52:55.619> node<00:52:55.920> which<00:52:56.400> extends<00:52:56.880> all<00:52:57.000> the<00:52:57.119> way 00:52:57.170 --> 00:52:57.180 align:start position:0% extension node which extends all the way 00:52:57.180 --> 00:53:00.349 align:start position:0% extension node which extends all the way down<00:52:57.359> to<00:52:57.720> the<00:52:57.960> to<00:52:58.380> the<00:52:58.559> leaf<00:52:59.220> so<00:52:59.700> this<00:52:59.880> allows 00:53:00.349 --> 00:53:00.359 align:start position:0% down to the to the leaf so this allows 00:53:00.359 --> 00:53:02.990 align:start position:0% down to the to the leaf so this allows you<00:53:00.480> to<00:53:00.720> shortcut<00:53:01.140> unnecessary<00:53:01.920> paths<00:53:02.400> what 00:53:02.990 --> 00:53:03.000 align:start position:0% you to shortcut unnecessary paths what 00:53:03.000 --> 00:53:04.490 align:start position:0% you to shortcut unnecessary paths what you'd<00:53:03.300> see<00:53:03.420> if<00:53:03.599> you<00:53:03.720> didn't<00:53:03.839> have<00:53:04.079> that<00:53:04.260> is 00:53:04.490 --> 00:53:04.500 align:start position:0% you'd see if you didn't have that is 00:53:04.500 --> 00:53:06.349 align:start position:0% you'd see if you didn't have that is there<00:53:04.680> would<00:53:04.859> be<00:53:05.040> a<00:53:05.220> bunch<00:53:05.339> of<00:53:05.520> layers<00:53:06.000> in 00:53:06.349 --> 00:53:06.359 align:start position:0% there would be a bunch of layers in 00:53:06.359 --> 00:53:09.230 align:start position:0% there would be a bunch of layers in there<00:53:06.480> Merkel<00:53:06.900> pituitary<00:53:07.700> where<00:53:08.700> there's 00:53:09.230 --> 00:53:09.240 align:start position:0% there Merkel pituitary where there's 00:53:09.240 --> 00:53:11.329 align:start position:0% there Merkel pituitary where there's only<00:53:09.420> like<00:53:09.720> one<00:53:10.200> specific<00:53:10.500> branch<00:53:10.859> that<00:53:11.040> has<00:53:11.220> a 00:53:11.329 --> 00:53:11.339 align:start position:0% only like one specific branch that has a 00:53:11.339 --> 00:53:12.710 align:start position:0% only like one specific branch that has a value<00:53:11.460> and<00:53:11.819> then<00:53:11.940> you<00:53:12.059> go<00:53:12.180> down<00:53:12.359> and<00:53:12.540> there's 00:53:12.710 --> 00:53:12.720 align:start position:0% value and then you go down and there's 00:53:12.720 --> 00:53:15.410 align:start position:0% value and then you go down and there's only<00:53:12.960> one<00:53:13.260> specific<00:53:13.559> Branch<00:53:13.980> so<00:53:14.700> for<00:53:15.000> like 00:53:15.410 --> 00:53:15.420 align:start position:0% only one specific Branch so for like 00:53:15.420 --> 00:53:17.510 align:start position:0% only one specific Branch so for like sparse<00:53:16.020> trees<00:53:16.319> meaning<00:53:16.680> like<00:53:16.980> trees<00:53:17.400> that 00:53:17.510 --> 00:53:17.520 align:start position:0% sparse trees meaning like trees that 00:53:17.520 --> 00:53:19.670 align:start position:0% sparse trees meaning like trees that aren't<00:53:17.700> filled<00:53:18.300> like<00:53:18.420> with<00:53:18.780> data<00:53:19.380> all<00:53:19.500> over 00:53:19.670 --> 00:53:19.680 align:start position:0% aren't filled like with data all over 00:53:19.680 --> 00:53:21.890 align:start position:0% aren't filled like with data all over this<00:53:20.339> is<00:53:20.460> incredibly<00:53:20.940> more<00:53:21.300> you<00:53:21.780> know 00:53:21.890 --> 00:53:21.900 align:start position:0% this is incredibly more you know 00:53:21.900 --> 00:53:23.450 align:start position:0% this is incredibly more you know efficient<00:53:22.260> because<00:53:22.800> you<00:53:23.040> don't<00:53:23.160> have<00:53:23.280> to 00:53:23.450 --> 00:53:23.460 align:start position:0% efficient because you don't have to 00:53:23.460 --> 00:53:25.549 align:start position:0% efficient because you don't have to store<00:53:23.640> like<00:53:24.180> all<00:53:24.599> these<00:53:24.780> unnecessary<00:53:25.200> nodes 00:53:25.549 --> 00:53:25.559 align:start position:0% store like all these unnecessary nodes 00:53:25.559 --> 00:53:28.010 align:start position:0% store like all these unnecessary nodes and<00:53:25.800> just<00:53:26.099> collapse<00:53:26.520> collapse<00:53:27.180> those<00:53:27.359> back<00:53:27.720> up 00:53:28.010 --> 00:53:28.020 align:start position:0% and just collapse collapse those back up 00:53:28.020 --> 00:53:31.430 align:start position:0% and just collapse collapse those back up into<00:53:28.220> into<00:53:29.220> one<00:53:29.579> leaf<00:53:29.940> instead<00:53:30.359> of 00:53:31.430 --> 00:53:31.440 align:start position:0% into into one leaf instead of 00:53:31.440 --> 00:53:35.089 align:start position:0% into into one leaf instead of tree<00:53:32.040> with<00:53:32.280> only<00:53:32.460> one<00:53:32.700> leaf<00:53:33.059> yeah<00:53:33.420> absolutely 00:53:35.089 --> 00:53:35.099 align:start position:0% tree with only one leaf yeah absolutely 00:53:35.099 --> 00:53:37.069 align:start position:0% tree with only one leaf yeah absolutely so<00:53:35.760> yeah<00:53:35.940> I'll<00:53:36.180> go<00:53:36.359> ahead<00:53:36.480> and<00:53:36.599> check<00:53:36.780> what 00:53:37.069 --> 00:53:37.079 align:start position:0% so yeah I'll go ahead and check what 00:53:37.079 --> 00:53:40.849 align:start position:0% so yeah I'll go ahead and check what example<00:53:37.619> two 00:53:40.849 --> 00:53:40.859 align:start position:0% 00:53:40.859 --> 00:53:42.829 align:start position:0% is<00:53:41.280> about 00:53:42.829 --> 00:53:42.839 align:start position:0% is about 00:53:42.839 --> 00:53:45.470 align:start position:0% is about yeah<00:53:43.200> there's<00:53:43.319> a<00:53:43.559> couple<00:53:43.619> of<00:53:43.800> additional<00:53:44.220> like 00:53:45.470 --> 00:53:45.480 align:start position:0% yeah there's a couple of additional like 00:53:45.480 --> 00:53:46.849 align:start position:0% yeah there's a couple of additional like notes<00:53:46.079> Here 00:53:46.849 --> 00:53:46.859 align:start position:0% notes Here 00:53:46.859 --> 00:53:48.290 align:start position:0% notes Here that<00:53:47.160> you<00:53:47.339> might<00:53:47.460> be<00:53:47.640> interested<00:53:47.940> in<00:53:48.000> some<00:53:48.240> of 00:53:48.290 --> 00:53:48.300 align:start position:0% that you might be interested in some of 00:53:48.300 --> 00:53:50.809 align:start position:0% that you might be interested in some of them<00:53:48.420> I<00:53:48.540> mentioned<00:53:48.839> while<00:53:49.079> while<00:53:49.140> doing<00:53:49.619> it 00:53:50.809 --> 00:53:50.819 align:start position:0% them I mentioned while while doing it 00:53:50.819 --> 00:53:53.329 align:start position:0% them I mentioned while while doing it it's<00:53:51.420> also<00:53:51.599> talking<00:53:51.780> a<00:53:52.020> bit<00:53:52.140> about 00:53:53.329 --> 00:53:53.339 align:start position:0% it's also talking a bit about 00:53:53.339 --> 00:53:55.430 align:start position:0% it's also talking a bit about the<00:53:54.119> rlp 00:53:55.430 --> 00:53:55.440 align:start position:0% the rlp 00:53:55.440 --> 00:53:58.849 align:start position:0% the rlp you<00:53:55.800> know<00:53:55.920> encoding<00:53:56.460> uh<00:53:57.319> function<00:53:58.319> this<00:53:58.559> is<00:53:58.680> a 00:53:58.849 --> 00:53:58.859 align:start position:0% you know encoding uh function this is a 00:53:58.859 --> 00:54:01.130 align:start position:0% you know encoding uh function this is a actually<00:53:59.160> not<00:53:59.460> up<00:53:59.640> to<00:53:59.819> date<00:53:59.940> that<00:54:00.240> link<00:54:00.420> I 00:54:01.130 --> 00:54:01.140 align:start position:0% actually not up to date that link I 00:54:01.140 --> 00:54:03.410 align:start position:0% actually not up to date that link I think<00:54:01.319> it's<00:54:01.440> probably<00:54:01.680> here<00:54:02.280> yeah<00:54:02.760> yeah 00:54:03.410 --> 00:54:03.420 align:start position:0% think it's probably here yeah yeah 00:54:03.420 --> 00:54:06.589 align:start position:0% think it's probably here yeah yeah so<00:54:03.839> there's<00:54:04.020> some<00:54:04.380> very<00:54:04.619> nice<00:54:04.800> ducks<00:54:05.220> in<00:54:05.520> uh<00:54:06.240> on 00:54:06.589 --> 00:54:06.599 align:start position:0% so there's some very nice ducks in uh on 00:54:06.599 --> 00:54:08.390 align:start position:0% so there's some very nice ducks in uh on ethereum.org<00:54:07.440> for<00:54:07.619> developers<00:54:07.980> like<00:54:08.220> if 00:54:08.390 --> 00:54:08.400 align:start position:0% ethereum.org for developers like if 00:54:08.400 --> 00:54:10.609 align:start position:0% ethereum.org for developers like if you're<00:54:08.579> looking<00:54:08.819> to<00:54:09.180> learn<00:54:09.900> a<00:54:10.079> bit<00:54:10.200> more<00:54:10.380> about 00:54:10.609 --> 00:54:10.619 align:start position:0% you're looking to learn a bit more about 00:54:10.619 --> 00:54:13.609 align:start position:0% you're looking to learn a bit more about rlp<00:54:11.579> you<00:54:12.059> would<00:54:12.300> just<00:54:12.480> go<00:54:12.960> there<00:54:13.140> they<00:54:13.319> have<00:54:13.500> a 00:54:13.609 --> 00:54:13.619 align:start position:0% rlp you would just go there they have a 00:54:13.619 --> 00:54:14.930 align:start position:0% rlp you would just go there they have a bunch<00:54:13.680> of<00:54:13.800> examples<00:54:14.220> and<00:54:14.460> you<00:54:14.579> couldn't<00:54:14.700> even 00:54:14.930 --> 00:54:14.940 align:start position:0% bunch of examples and you couldn't even 00:54:14.940 --> 00:54:17.030 align:start position:0% bunch of examples and you couldn't even like<00:54:15.240> use<00:54:15.420> our<00:54:15.720> library<00:54:16.079> to<00:54:16.500> test<00:54:16.619> it<00:54:16.800> out<00:54:16.920> and 00:54:17.030 --> 00:54:17.040 align:start position:0% like use our library to test it out and 00:54:17.040 --> 00:54:20.750 align:start position:0% like use our library to test it out and play<00:54:17.160> around<00:54:17.280> with<00:54:17.579> it<00:54:18.079> uh<00:54:19.079> so<00:54:19.500> before<00:54:19.760> values 00:54:20.750 --> 00:54:20.760 align:start position:0% play around with it uh so before values 00:54:20.760 --> 00:54:22.490 align:start position:0% play around with it uh so before values or<00:54:21.240> so<00:54:21.480> there's<00:54:21.720> a<00:54:21.839> bunch<00:54:21.960> of<00:54:22.020> values<00:54:22.319> you 00:54:22.490 --> 00:54:22.500 align:start position:0% or so there's a bunch of values you 00:54:22.500 --> 00:54:23.690 align:start position:0% or so there's a bunch of values you could<00:54:22.619> want<00:54:22.859> to<00:54:22.980> store<00:54:23.099> in<00:54:23.339> the<00:54:23.520> miracle 00:54:23.690 --> 00:54:23.700 align:start position:0% could want to store in the miracle 00:54:23.700 --> 00:54:25.190 align:start position:0% could want to store in the miracle Patricia<00:54:24.180> tree<00:54:24.300> right 00:54:25.190 --> 00:54:25.200 align:start position:0% Patricia tree right 00:54:25.200 --> 00:54:27.410 align:start position:0% Patricia tree right and<00:54:25.619> those<00:54:25.800> need<00:54:26.040> to<00:54:26.160> be<00:54:26.220> serialized<00:54:26.880> before 00:54:27.410 --> 00:54:27.420 align:start position:0% and those need to be serialized before 00:54:27.420 --> 00:54:31.150 align:start position:0% and those need to be serialized before they<00:54:28.319> are<00:54:28.500> you<00:54:29.099> know<00:54:29.160> put<00:54:29.760> inside<00:54:29.940> of<00:54:30.180> the<00:54:30.300> tree 00:54:31.150 --> 00:54:31.160 align:start position:0% they are you know put inside of the tree 00:54:31.160 --> 00:54:34.190 align:start position:0% they are you know put inside of the tree uh<00:54:32.160> this<00:54:32.460> serialization<00:54:33.119> is<00:54:33.480> done<00:54:33.720> with<00:54:34.020> the 00:54:34.190 --> 00:54:34.200 align:start position:0% uh this serialization is done with the 00:54:34.200 --> 00:54:38.270 align:start position:0% uh this serialization is done with the recursive<00:54:34.859> lamp<00:54:35.480> prefix<00:54:36.480> encoding<00:54:37.380> function 00:54:38.270 --> 00:54:38.280 align:start position:0% recursive lamp prefix encoding function 00:54:38.280 --> 00:54:41.270 align:start position:0% recursive lamp prefix encoding function uh<00:54:39.599> and 00:54:41.270 --> 00:54:41.280 align:start position:0% uh and 00:54:41.280 --> 00:54:44.990 align:start position:0% uh and and<00:54:41.400> yeah<00:54:41.940> as<00:54:42.240> I<00:54:42.480> mentioned<00:54:42.960> uh<00:54:43.640> Keys<00:54:44.640> also<00:54:44.819> go 00:54:44.990 --> 00:54:45.000 align:start position:0% and yeah as I mentioned uh Keys also go 00:54:45.000 --> 00:54:47.650 align:start position:0% and yeah as I mentioned uh Keys also go in<00:54:45.300> additional<00:54:45.839> additional<00:54:46.520> transformation 00:54:47.650 --> 00:54:47.660 align:start position:0% in additional additional transformation 00:54:47.660 --> 00:54:51.109 align:start position:0% in additional additional transformation uh<00:54:48.660> they're<00:54:48.960> not<00:54:49.140> used<00:54:49.500> like<00:54:49.980> raw<00:54:50.460> uh<00:54:50.940> they're 00:54:51.109 --> 00:54:51.119 align:start position:0% uh they're not used like raw uh they're 00:54:51.119 --> 00:54:55.549 align:start position:0% uh they're not used like raw uh they're used<00:54:51.420> uh<00:54:52.200> we<00:54:52.559> we<00:54:52.680> first<00:54:52.920> take<00:54:53.040> the<00:54:53.220> keca<00:54:53.839> 256<00:54:54.839> of 00:54:55.549 --> 00:54:55.559 align:start position:0% used uh we we first take the keca 256 of 00:54:55.559 --> 00:54:59.630 align:start position:0% used uh we we first take the keca 256 of the<00:54:55.859> key<00:54:56.040> before<00:54:56.280> we<00:54:56.640> we<00:54:57.540> update<00:54:58.020> the<00:54:58.140> tree 00:54:59.630 --> 00:54:59.640 align:start position:0% the key before we we update the tree 00:54:59.640 --> 00:55:00.950 align:start position:0% the key before we we update the tree so 00:55:00.950 --> 00:55:00.960 align:start position:0% so 00:55:00.960 --> 00:55:02.569 align:start position:0% so here<00:55:01.500> we're<00:55:01.740> basically<00:55:02.040> going<00:55:02.220> to<00:55:02.339> do<00:55:02.400> the 00:55:02.569 --> 00:55:02.579 align:start position:0% here we're basically going to do the 00:55:02.579 --> 00:55:03.829 align:start position:0% here we're basically going to do the same<00:55:02.700> thing 00:55:03.829 --> 00:55:03.839 align:start position:0% same thing 00:55:03.839 --> 00:55:06.349 align:start position:0% same thing but<00:55:04.319> we<00:55:04.559> are<00:55:04.680> going<00:55:04.859> to<00:55:05.040> use<00:55:05.400> the<00:55:05.819> hashed 00:55:06.349 --> 00:55:06.359 align:start position:0% but we are going to use the hashed 00:55:06.359 --> 00:55:08.809 align:start position:0% but we are going to use the hashed version<00:55:07.140> of<00:55:07.440> the<00:55:07.559> key 00:55:08.809 --> 00:55:08.819 align:start position:0% version of the key 00:55:08.819 --> 00:55:11.089 align:start position:0% version of the key so<00:55:09.480> how<00:55:09.780> we're<00:55:09.900> going<00:55:10.079> to<00:55:10.200> do<00:55:10.319> that<00:55:10.500> is<00:55:10.740> we're 00:55:11.089 --> 00:55:11.099 align:start position:0% so how we're going to do that is we're 00:55:11.099 --> 00:55:14.089 align:start position:0% so how we're going to do that is we're just<00:55:11.520> gonna<00:55:11.700> you<00:55:12.300> know<00:55:12.359> import<00:55:12.780> the<00:55:13.380> kick<00:55:13.680> to 00:55:14.089 --> 00:55:14.099 align:start position:0% just gonna you know import the kick to 00:55:14.099 --> 00:55:16.790 align:start position:0% just gonna you know import the kick to 56<00:55:14.640> that<00:55:14.940> we<00:55:15.119> have<00:55:15.300> in<00:55:15.540> you<00:55:16.140> know<00:55:16.260> ethereum 00:55:16.790 --> 00:55:16.800 align:start position:0% 56 that we have in you know ethereum 00:55:16.800 --> 00:55:19.730 align:start position:0% 56 that we have in you know ethereum jazz<00:55:17.099> slash<00:55:17.940> util<00:55:18.839> package 00:55:19.730 --> 00:55:19.740 align:start position:0% jazz slash util package 00:55:19.740 --> 00:55:22.849 align:start position:0% jazz slash util package and<00:55:20.700> the<00:55:21.000> only<00:55:21.119> difference<00:55:21.420> is<00:55:21.960> we<00:55:22.260> are<00:55:22.440> going 00:55:22.849 --> 00:55:22.859 align:start position:0% and the only difference is we are going 00:55:22.859 --> 00:55:24.230 align:start position:0% and the only difference is we are going to<00:55:23.220> uh 00:55:24.230 --> 00:55:24.240 align:start position:0% to uh 00:55:24.240 --> 00:55:25.870 align:start position:0% to uh as<00:55:24.720> you<00:55:24.839> see<00:55:25.020> here 00:55:25.870 --> 00:55:25.880 align:start position:0% as you see here 00:55:25.880 --> 00:55:29.329 align:start position:0% as you see here put<00:55:26.880> the<00:55:27.180> value<00:55:27.359> at<00:55:28.079> the<00:55:28.260> Keck<00:55:28.680> of<00:55:29.099> the<00:55:29.220> key 00:55:29.329 --> 00:55:29.339 align:start position:0% put the value at the Keck of the key 00:55:29.339 --> 00:55:31.970 align:start position:0% put the value at the Keck of the key instead<00:55:29.880> of<00:55:29.940> the<00:55:30.180> key<00:55:30.420> itself<00:55:31.260> so<00:55:31.740> everything 00:55:31.970 --> 00:55:31.980 align:start position:0% instead of the key itself so everything 00:55:31.980 --> 00:55:34.250 align:start position:0% instead of the key itself so everything else<00:55:32.280> is<00:55:32.579> going<00:55:32.760> to<00:55:32.880> be<00:55:32.940> uh 00:55:34.250 --> 00:55:34.260 align:start position:0% else is going to be uh 00:55:34.260 --> 00:55:37.790 align:start position:0% else is going to be uh you<00:55:34.619> know<00:55:34.740> exactly<00:55:35.280> the<00:55:36.240> same 00:55:37.790 --> 00:55:37.800 align:start position:0% you know exactly the same 00:55:37.800 --> 00:55:48.950 align:start position:0% you know exactly the same so<00:55:38.160> let's<00:55:38.280> see 00:55:48.950 --> 00:55:48.960 align:start position:0% 00:55:48.960 --> 00:55:50.930 align:start position:0% yeah<00:55:49.440> similarly<00:55:49.920> we're<00:55:50.280> gonna<00:55:50.400> get<00:55:50.640> you<00:55:50.819> know 00:55:50.930 --> 00:55:50.940 align:start position:0% yeah similarly we're gonna get you know 00:55:50.940 --> 00:55:53.690 align:start position:0% yeah similarly we're gonna get you know an<00:55:51.059> updated<00:55:51.359> tree<00:55:51.660> root<00:55:51.960> so<00:55:52.740> that 00:55:53.690 --> 00:55:53.700 align:start position:0% an updated tree root so that 00:55:53.700 --> 00:55:56.870 align:start position:0% an updated tree root so that until<00:55:54.180> nothing<00:55:54.599> surprising<00:55:55.559> here<00:55:55.800> uh<00:55:56.700> it's 00:55:56.870 --> 00:55:56.880 align:start position:0% until nothing surprising here uh it's 00:55:56.880 --> 00:55:59.450 align:start position:0% until nothing surprising here uh it's basically<00:55:57.240> just<00:55:57.540> you<00:55:57.780> know<00:55:57.900> we<00:55:58.440> we<00:55:58.859> had<00:55:59.220> an 00:55:59.450 --> 00:55:59.460 align:start position:0% basically just you know we we had an 00:55:59.460 --> 00:56:02.690 align:start position:0% basically just you know we we had an alternative<00:56:00.000> key<00:56:00.359> which<00:56:00.660> is<00:56:00.720> the<00:56:00.900> key<00:56:01.800> we<00:56:02.460> got 00:56:02.690 --> 00:56:02.700 align:start position:0% alternative key which is the key we got 00:56:02.700 --> 00:56:05.450 align:start position:0% alternative key which is the key we got the<00:56:02.940> same<00:56:03.119> value<00:56:03.300> back<00:56:03.599> no<00:56:04.260> difference<00:56:04.500> there 00:56:05.450 --> 00:56:05.460 align:start position:0% the same value back no difference there 00:56:05.460 --> 00:56:30.349 align:start position:0% the same value back no difference there any<00:56:05.880> question<00:56:06.540> on<00:56:06.780> that 00:56:30.349 --> 00:56:30.359 align:start position:0% 00:56:30.359 --> 00:56:44.650 align:start position:0% performance 00:56:44.650 --> 00:56:44.660 align:start position:0% 00:56:44.660 --> 00:56:46.490 align:start position:0% industry 00:56:46.490 --> 00:56:46.500 align:start position:0% industry 00:56:46.500 --> 00:56:49.490 align:start position:0% industry okay<00:56:46.859> so<00:56:47.099> the<00:56:47.579> the<00:56:48.000> values<00:56:48.540> themselves<00:56:49.020> are 00:56:49.490 --> 00:56:49.500 align:start position:0% okay so the the values themselves are 00:56:49.500 --> 00:56:51.650 align:start position:0% okay so the the values themselves are enhatched<00:56:50.040> because<00:56:50.460> otherwise<00:56:51.300> we<00:56:51.540> wouldn't 00:56:51.650 --> 00:56:51.660 align:start position:0% enhatched because otherwise we wouldn't 00:56:51.660 --> 00:56:53.270 align:start position:0% enhatched because otherwise we wouldn't be<00:56:51.900> able<00:56:52.079> to<00:56:52.200> retrieve<00:56:52.619> them<00:56:52.740> since<00:56:52.980> you<00:56:53.160> know 00:56:53.270 --> 00:56:53.280 align:start position:0% be able to retrieve them since you know 00:56:53.280 --> 00:56:55.849 align:start position:0% be able to retrieve them since you know hashing<00:56:53.640> is<00:56:53.760> one<00:56:53.940> way<00:56:54.440> the<00:56:55.440> only<00:56:55.559> thing<00:56:55.740> that 00:56:55.849 --> 00:56:55.859 align:start position:0% hashing is one way the only thing that 00:56:55.859 --> 00:56:59.270 align:start position:0% hashing is one way the only thing that we<00:56:56.040> hash<00:56:56.339> is<00:56:57.240> I<00:56:57.660> mean<00:56:57.780> this<00:56:58.200> is<00:56:58.440> like<00:56:58.980> a<00:56:59.160> key 00:56:59.270 --> 00:56:59.280 align:start position:0% we hash is I mean this is like a key 00:56:59.280 --> 00:57:02.150 align:start position:0% we hash is I mean this is like a key value<00:56:59.579> you<00:57:00.000> know<00:57:00.059> data<00:57:00.480> structure<00:57:00.980> the<00:57:01.980> value 00:57:02.150 --> 00:57:02.160 align:start position:0% value you know data structure the value 00:57:02.160 --> 00:57:04.430 align:start position:0% value you know data structure the value we<00:57:02.400> keep<00:57:02.579> you<00:57:02.940> know<00:57:03.000> native<00:57:03.540> we<00:57:03.780> just<00:57:03.960> rlp 00:57:04.430 --> 00:57:04.440 align:start position:0% we keep you know native we just rlp 00:57:04.440 --> 00:57:06.829 align:start position:0% we keep you know native we just rlp encoded<00:57:04.920> for<00:57:05.099> you<00:57:05.460> know<00:57:05.579> serialization<00:57:06.180> so 00:57:06.829 --> 00:57:06.839 align:start position:0% encoded for you know serialization so 00:57:06.839 --> 00:57:08.329 align:start position:0% encoded for you know serialization so that<00:57:07.020> it's<00:57:07.200> compatible 00:57:08.329 --> 00:57:08.339 align:start position:0% that it's compatible 00:57:08.339 --> 00:57:10.910 align:start position:0% that it's compatible but<00:57:09.059> the<00:57:09.359> the<00:57:09.480> key<00:57:09.780> itself<00:57:10.140> that<00:57:10.740> we're 00:57:10.910 --> 00:57:10.920 align:start position:0% but the the key itself that we're 00:57:10.920 --> 00:57:13.670 align:start position:0% but the the key itself that we're hashing<00:57:11.339> we<00:57:12.000> could<00:57:12.119> very<00:57:12.359> well<00:57:12.540> well<00:57:12.960> have<00:57:13.380> a 00:57:13.670 --> 00:57:13.680 align:start position:0% hashing we could very well well have a 00:57:13.680 --> 00:57:15.589 align:start position:0% hashing we could very well well have a miracle<00:57:14.280> but<00:57:14.460> surgery<00:57:14.640> like<00:57:14.940> data<00:57:15.240> structure 00:57:15.589 --> 00:57:15.599 align:start position:0% miracle but surgery like data structure 00:57:15.599 --> 00:57:19.130 align:start position:0% miracle but surgery like data structure without<00:57:15.900> hash<00:57:16.380> keys<00:57:16.940> and<00:57:17.940> however<00:57:18.420> at<00:57:18.720> the<00:57:18.900> you 00:57:19.130 --> 00:57:19.140 align:start position:0% without hash keys and however at the you 00:57:19.140 --> 00:57:20.569 align:start position:0% without hash keys and however at the you know<00:57:19.260> early<00:57:19.500> days<00:57:19.680> of<00:57:19.859> ethereum<00:57:20.280> it<00:57:20.460> was 00:57:20.569 --> 00:57:20.579 align:start position:0% know early days of ethereum it was 00:57:20.579 --> 00:57:22.430 align:start position:0% know early days of ethereum it was chosen<00:57:20.940> that<00:57:21.240> the<00:57:21.420> keys<00:57:21.720> are<00:57:21.839> gonna<00:57:22.020> were 00:57:22.430 --> 00:57:22.440 align:start position:0% chosen that the keys are gonna were 00:57:22.440 --> 00:57:24.950 align:start position:0% chosen that the keys are gonna were gonna<00:57:22.680> be<00:57:22.859> hashed<00:57:23.280> uh<00:57:24.059> the<00:57:24.240> main<00:57:24.359> reason<00:57:24.599> why 00:57:24.950 --> 00:57:24.960 align:start position:0% gonna be hashed uh the main reason why 00:57:24.960 --> 00:57:26.630 align:start position:0% gonna be hashed uh the main reason why that<00:57:25.619> was<00:57:25.800> done 00:57:26.630 --> 00:57:26.640 align:start position:0% that was done 00:57:26.640 --> 00:57:30.589 align:start position:0% that was done is<00:57:27.180> so<00:57:27.420> that<00:57:27.660> it<00:57:28.020> uh<00:57:28.440> evens<00:57:29.040> out<00:57:29.160> uh<00:57:30.119> the<00:57:30.420> tree 00:57:30.589 --> 00:57:30.599 align:start position:0% is so that it uh evens out uh the tree 00:57:30.599 --> 00:57:33.349 align:start position:0% is so that it uh evens out uh the tree uh<00:57:31.200> naturally<00:57:31.619> so<00:57:32.339> it<00:57:32.520> mitigated<00:57:33.119> like 00:57:33.349 --> 00:57:33.359 align:start position:0% uh naturally so it mitigated like 00:57:33.359 --> 00:57:34.790 align:start position:0% uh naturally so it mitigated like vectors<00:57:33.720> of<00:57:33.900> attack<00:57:34.079> where<00:57:34.440> you<00:57:34.559> could<00:57:34.680> have 00:57:34.790 --> 00:57:34.800 align:start position:0% vectors of attack where you could have 00:57:34.800 --> 00:57:37.549 align:start position:0% vectors of attack where you could have people<00:57:35.040> like<00:57:35.339> constantly<00:57:35.819> update<00:57:36.180> like<00:57:36.540> a<00:57:37.140> a 00:57:37.549 --> 00:57:37.559 align:start position:0% people like constantly update like a a 00:57:37.559 --> 00:57:39.710 align:start position:0% people like constantly update like a a part<00:57:37.920> of<00:57:38.040> the<00:57:38.099> tree<00:57:38.220> like<00:57:38.520> very<00:57:38.700> easily<00:57:39.119> and 00:57:39.710 --> 00:57:39.720 align:start position:0% part of the tree like very easily and 00:57:39.720 --> 00:57:41.150 align:start position:0% part of the tree like very easily and now<00:57:39.900> if<00:57:40.020> you<00:57:40.200> wanted<00:57:40.319> to<00:57:40.500> do<00:57:40.559> that<00:57:40.680> you'd<00:57:40.980> have 00:57:41.150 --> 00:57:41.160 align:start position:0% now if you wanted to do that you'd have 00:57:41.160 --> 00:57:43.730 align:start position:0% now if you wanted to do that you'd have to<00:57:41.280> like<00:57:41.579> pre-compute<00:57:42.180> a<00:57:43.079> hash<00:57:43.319> and<00:57:43.619> since 00:57:43.730 --> 00:57:43.740 align:start position:0% to like pre-compute a hash and since 00:57:43.740 --> 00:57:45.349 align:start position:0% to like pre-compute a hash and since it's<00:57:43.920> like<00:57:44.099> non-deterministic<00:57:44.940> well<00:57:45.180> it's 00:57:45.349 --> 00:57:45.359 align:start position:0% it's like non-deterministic well it's 00:57:45.359 --> 00:57:46.790 align:start position:0% it's like non-deterministic well it's deterministic<00:57:45.960> but<00:57:46.079> you<00:57:46.200> can<00:57:46.319> like<00:57:46.500> predict 00:57:46.790 --> 00:57:46.800 align:start position:0% deterministic but you can like predict 00:57:46.800 --> 00:57:48.109 align:start position:0% deterministic but you can like predict an<00:57:46.980> event<00:57:47.160> what<00:57:47.400> the<00:57:47.520> hash<00:57:47.700> is<00:57:47.880> going<00:57:48.000> to<00:57:48.059> be 00:57:48.109 --> 00:57:48.119 align:start position:0% an event what the hash is going to be 00:57:48.119 --> 00:57:49.910 align:start position:0% an event what the hash is going to be obviously<00:57:48.480> you<00:57:49.020> basically<00:57:49.319> have<00:57:49.500> to<00:57:49.619> do<00:57:49.740> like 00:57:49.910 --> 00:57:49.920 align:start position:0% obviously you basically have to do like 00:57:49.920 --> 00:57:53.150 align:start position:0% obviously you basically have to do like proof<00:57:50.220> of<00:57:50.280> work<00:57:50.400> to<00:57:50.700> like<00:57:51.000> uh 00:57:53.150 --> 00:57:53.160 align:start position:0% proof of work to like uh 00:57:53.160 --> 00:57:55.250 align:start position:0% proof of work to like uh this<00:57:53.760> target<00:57:54.059> like<00:57:54.359> a<00:57:54.540> specific<00:57:54.780> part<00:57:55.020> of<00:57:55.200> the 00:57:55.250 --> 00:57:55.260 align:start position:0% this target like a specific part of the 00:57:55.260 --> 00:57:58.190 align:start position:0% this target like a specific part of the tree<00:57:55.440> it<00:57:56.040> imposes<00:57:56.760> some<00:57:57.000> Randomness<00:57:57.480> on<00:57:58.020> the 00:57:58.190 --> 00:57:58.200 align:start position:0% tree it imposes some Randomness on the 00:57:58.200 --> 00:57:59.990 align:start position:0% tree it imposes some Randomness on the the<00:57:58.380> actual<00:57:58.740> address<00:57:58.920> and<00:57:59.339> so<00:57:59.520> if<00:57:59.700> you<00:57:59.819> have 00:57:59.990 --> 00:58:00.000 align:start position:0% the actual address and so if you have 00:58:00.000 --> 00:58:03.109 align:start position:0% the actual address and so if you have keys<00:58:00.660> that<00:58:00.780> are<00:58:00.960> related<00:58:01.319> they<00:58:01.859> won't<00:58:02.119> cluster 00:58:03.109 --> 00:58:03.119 align:start position:0% keys that are related they won't cluster 00:58:03.119 --> 00:58:04.670 align:start position:0% keys that are related they won't cluster in<00:58:03.300> a<00:58:03.420> part<00:58:03.540> of<00:58:03.720> the<00:58:03.839> tree<00:58:03.960> they'll<00:58:04.380> be 00:58:04.670 --> 00:58:04.680 align:start position:0% in a part of the tree they'll be 00:58:04.680 --> 00:58:07.309 align:start position:0% in a part of the tree they'll be dispersed<00:58:05.220> evenly 00:58:07.309 --> 00:58:07.319 align:start position:0% dispersed evenly 00:58:07.319 --> 00:58:09.890 align:start position:0% dispersed evenly and<00:58:07.740> your<00:58:07.920> key<00:58:08.040> can<00:58:08.339> be<00:58:08.460> a<00:58:09.000> short<00:58:09.240> string<00:58:09.660> and 00:58:09.890 --> 00:58:09.900 align:start position:0% and your key can be a short string and 00:58:09.900 --> 00:58:12.530 align:start position:0% and your key can be a short string and it<00:58:10.079> ends<00:58:10.500> up<00:58:10.559> 32<00:58:10.980> bytes 00:58:12.530 --> 00:58:12.540 align:start position:0% it ends up 32 bytes 00:58:12.540 --> 00:58:15.530 align:start position:0% it ends up 32 bytes yep 00:58:15.530 --> 00:58:15.540 align:start position:0% 00:58:15.540 --> 00:58:17.630 align:start position:0% yeah<00:58:15.599> so<00:58:15.960> in<00:58:16.140> our<00:58:16.319> case<00:58:16.500> like<00:58:16.920> keys<00:58:17.400> are<00:58:17.520> always 00:58:17.630 --> 00:58:17.640 align:start position:0% yeah so in our case like keys are always 00:58:17.640 --> 00:58:20.210 align:start position:0% yeah so in our case like keys are always like<00:58:18.059> how<00:58:18.780> this<00:58:19.020> is<00:58:19.260> like<00:58:19.500> in<00:58:19.619> the<00:58:19.740> case<00:58:19.859> of<00:58:20.040> the 00:58:20.210 --> 00:58:20.220 align:start position:0% like how this is like in the case of the 00:58:20.220 --> 00:58:21.950 align:start position:0% like how this is like in the case of the the<00:58:20.460> state<00:58:20.760> tree<00:58:21.000> Keys<00:58:21.359> would<00:58:21.420> be<00:58:21.540> like<00:58:21.720> the 00:58:21.950 --> 00:58:21.960 align:start position:0% the state tree Keys would be like the 00:58:21.960 --> 00:58:25.690 align:start position:0% the state tree Keys would be like the the<00:58:22.140> account<00:58:22.740> addresses<00:58:23.400> but<00:58:24.359> uh<00:58:24.839> yeah<00:58:25.079> the 00:58:25.690 --> 00:58:25.700 align:start position:0% the account addresses but uh yeah the 00:58:25.700 --> 00:58:28.010 align:start position:0% the account addresses but uh yeah the like<00:58:26.700> hashing<00:58:27.059> something<00:58:27.240> obviously<00:58:27.720> also 00:58:28.010 --> 00:58:28.020 align:start position:0% like hashing something obviously also 00:58:28.020 --> 00:58:29.750 align:start position:0% like hashing something obviously also has<00:58:28.200> benefits<00:58:28.740> of<00:58:28.920> making<00:58:29.220> everything<00:58:29.460> equal 00:58:29.750 --> 00:58:29.760 align:start position:0% has benefits of making everything equal 00:58:29.760 --> 00:58:32.750 align:start position:0% has benefits of making everything equal length<00:58:30.240> which<00:58:30.660> you<00:58:31.200> want<00:58:31.440> in<00:58:31.680> like<00:58:31.980> data 00:58:32.750 --> 00:58:32.760 align:start position:0% length which you want in like data 00:58:32.760 --> 00:58:36.470 align:start position:0% length which you want in like data structures<00:58:33.059> like<00:58:33.240> this 00:58:36.470 --> 00:58:36.480 align:start position:0% 00:58:36.480 --> 00:58:40.069 align:start position:0% all<00:58:36.839> right<00:58:37.020> so<00:58:37.500> as<00:58:37.799> we<00:58:37.980> said<00:58:38.099> like<00:58:38.339> fairly 00:58:40.069 --> 00:58:40.079 align:start position:0% all right so as we said like fairly 00:58:40.079 --> 00:58:41.809 align:start position:0% all right so as we said like fairly fairly<00:58:40.559> straightforward<00:58:41.160> now<00:58:41.579> we're<00:58:41.700> going 00:58:41.809 --> 00:58:41.819 align:start position:0% fairly straightforward now we're going 00:58:41.819 --> 00:58:43.849 align:start position:0% fairly straightforward now we're going to<00:58:41.880> do<00:58:42.059> something<00:58:42.299> you<00:58:43.140> know<00:58:43.260> a<00:58:43.559> little<00:58:43.680> bit 00:58:43.849 --> 00:58:43.859 align:start position:0% to do something you know a little bit 00:58:43.859 --> 00:58:45.650 align:start position:0% to do something you know a little bit more<00:58:44.220> interesting 00:58:45.650 --> 00:58:45.660 align:start position:0% more interesting 00:58:45.660 --> 00:58:48.589 align:start position:0% more interesting now<00:58:46.079> what<00:58:46.319> we've<00:58:46.500> seen<00:58:46.680> is<00:58:46.920> that<00:58:47.220> the<00:58:47.579> the 00:58:48.589 --> 00:58:48.599 align:start position:0% now what we've seen is that the the 00:58:48.599 --> 00:58:52.849 align:start position:0% now what we've seen is that the the like<00:58:49.020> we've<00:58:49.140> used<00:58:49.319> the<00:58:49.559> kecac<00:58:50.099> 256<00:58:50.940> of<00:58:51.780> the<00:58:51.900> key 00:58:52.849 --> 00:58:52.859 align:start position:0% like we've used the kecac 256 of the key 00:58:52.859 --> 00:58:55.010 align:start position:0% like we've used the kecac 256 of the key but<00:58:53.339> there's<00:58:53.700> a<00:58:54.000> you<00:58:54.299> know<00:58:54.420> there's<00:58:54.720> a 00:58:55.010 --> 00:58:55.020 align:start position:0% but there's a you know there's a 00:58:55.020 --> 00:58:57.349 align:start position:0% but there's a you know there's a property<00:58:55.799> of<00:58:56.220> the<00:58:56.339> tree<00:58:56.520> that<00:58:56.819> we<00:58:57.000> can<00:58:57.119> just 00:58:57.349 --> 00:58:57.359 align:start position:0% property of the tree that we can just 00:58:57.359 --> 00:58:59.870 align:start position:0% property of the tree that we can just use<00:58:57.900> in<00:58:58.140> order<00:58:58.319> to<00:58:58.500> do<00:58:58.680> that<00:58:58.859> natively<00:58:59.400> that 00:58:59.870 --> 00:58:59.880 align:start position:0% use in order to do that natively that 00:58:59.880 --> 00:59:02.569 align:start position:0% use in order to do that natively that property<00:59:00.240> is<00:59:00.420> called<00:59:00.720> use<00:59:01.440> key<00:59:01.680> hashing<00:59:02.160> it's 00:59:02.569 --> 00:59:02.579 align:start position:0% property is called use key hashing it's 00:59:02.579 --> 00:59:06.230 align:start position:0% property is called use key hashing it's a<00:59:02.760> Boolean<00:59:03.180> that<00:59:03.960> defaults<00:59:04.619> to<00:59:04.740> false<00:59:05.640> but<00:59:06.119> as 00:59:06.230 --> 00:59:06.240 align:start position:0% a Boolean that defaults to false but as 00:59:06.240 --> 00:59:08.510 align:start position:0% a Boolean that defaults to false but as you<00:59:06.420> can<00:59:06.480> set<00:59:06.720> to<00:59:06.900> true<00:59:07.140> if<00:59:07.799> you<00:59:07.920> want<00:59:08.040> when 00:59:08.510 --> 00:59:08.520 align:start position:0% you can set to true if you want when 00:59:08.520 --> 00:59:10.069 align:start position:0% you can set to true if you want when playing<00:59:08.819> around<00:59:09.000> with<00:59:09.180> a<00:59:09.420> tree<00:59:09.540> is<00:59:09.720> just<00:59:09.900> more 00:59:10.069 --> 00:59:10.079 align:start position:0% playing around with a tree is just more 00:59:10.079 --> 00:59:12.770 align:start position:0% playing around with a tree is just more convenient<00:59:10.680> to<00:59:11.220> set<00:59:11.460> it<00:59:11.579> to<00:59:11.760> false<00:59:12.119> or<00:59:12.359> have<00:59:12.540> it 00:59:12.770 --> 00:59:12.780 align:start position:0% convenient to set it to false or have it 00:59:12.780 --> 00:59:14.750 align:start position:0% convenient to set it to false or have it you<00:59:12.960> know<00:59:13.079> default<00:59:13.440> to<00:59:13.619> false<00:59:14.040> just<00:59:14.579> because 00:59:14.750 --> 00:59:14.760 align:start position:0% you know default to false just because 00:59:14.760 --> 00:59:17.150 align:start position:0% you know default to false just because you<00:59:15.240> you<00:59:15.480> don't<00:59:15.660> have<00:59:15.839> like<00:59:16.020> to<00:59:16.260> to<00:59:16.440> all<00:59:16.680> do<00:59:16.980> all 00:59:17.150 --> 00:59:17.160 align:start position:0% you you don't have like to to all do all 00:59:17.160 --> 00:59:18.950 align:start position:0% you you don't have like to to all do all that<00:59:17.339> additional<00:59:17.760> computation<00:59:18.299> it's<00:59:18.660> also 00:59:18.950 --> 00:59:18.960 align:start position:0% that additional computation it's also 00:59:18.960 --> 00:59:21.530 align:start position:0% that additional computation it's also easier<00:59:19.319> if<00:59:19.559> you<00:59:19.680> want<00:59:19.799> to<00:59:19.920> debug<00:59:20.280> what<00:59:21.180> a<00:59:21.420> value 00:59:21.530 --> 00:59:21.540 align:start position:0% easier if you want to debug what a value 00:59:21.540 --> 00:59:22.910 align:start position:0% easier if you want to debug what a value uh 00:59:22.910 --> 00:59:22.920 align:start position:0% uh 00:59:22.920 --> 00:59:26.089 align:start position:0% uh you<00:59:23.400> know<00:59:23.520> if<00:59:23.760> you<00:59:24.000> if<00:59:24.480> you<00:59:24.780> only<00:59:25.079> have<00:59:25.319> the<00:59:25.619> the 00:59:26.089 --> 00:59:26.099 align:start position:0% you know if you if you only have the the 00:59:26.099 --> 00:59:27.829 align:start position:0% you know if you if you only have the the hash<00:59:26.280> of<00:59:26.520> the<00:59:26.579> key<00:59:26.760> you<00:59:27.119> can<00:59:27.180> never<00:59:27.299> know<00:59:27.540> like 00:59:27.829 --> 00:59:27.839 align:start position:0% hash of the key you can never know like 00:59:27.839 --> 00:59:29.690 align:start position:0% hash of the key you can never know like what<00:59:28.260> was<00:59:28.380> the<00:59:28.559> actual<00:59:28.799> key<00:59:28.980> that<00:59:29.220> I<00:59:29.400> used<00:59:29.520> to 00:59:29.690 --> 00:59:29.700 align:start position:0% what was the actual key that I used to 00:59:29.700 --> 00:59:31.069 align:start position:0% what was the actual key that I used to update<00:59:29.940> this<00:59:30.059> you<00:59:30.240> cannot<00:59:30.420> retrieve<00:59:30.839> it<00:59:30.960> back 00:59:31.069 --> 00:59:31.079 align:start position:0% update this you cannot retrieve it back 00:59:31.079 --> 00:59:34.190 align:start position:0% update this you cannot retrieve it back which<00:59:31.920> uh<00:59:32.339> is<00:59:32.640> actually<00:59:32.760> an<00:59:33.000> issue<00:59:33.299> that<00:59:33.599> has 00:59:34.190 --> 00:59:34.200 align:start position:0% which uh is actually an issue that has 00:59:34.200 --> 00:59:36.289 align:start position:0% which uh is actually an issue that has also<00:59:34.500> come<00:59:34.619> up<00:59:34.799> when<00:59:35.099> making<00:59:35.760> the<00:59:36.000> transition 00:59:36.289 --> 00:59:36.299 align:start position:0% also come up when making the transition 00:59:36.299 --> 00:59:38.329 align:start position:0% also come up when making the transition from<00:59:36.660> Myrtle<00:59:37.140> trees<00:59:37.380> to<00:59:37.500> Vertical<00:59:37.740> trees<00:59:38.040> but 00:59:38.329 --> 00:59:38.339 align:start position:0% from Myrtle trees to Vertical trees but 00:59:38.339 --> 00:59:40.250 align:start position:0% from Myrtle trees to Vertical trees but that's<00:59:38.579> a<00:59:38.819> different<00:59:39.000> uh<00:59:39.540> that's<00:59:40.020> a<00:59:40.140> different 00:59:40.250 --> 00:59:40.260 align:start position:0% that's a different uh that's a different 00:59:40.260 --> 00:59:44.089 align:start position:0% that's a different uh that's a different topic 00:59:44.089 --> 00:59:44.099 align:start position:0% 00:59:44.099 --> 00:59:49.490 align:start position:0% so<00:59:44.520> let's<00:59:44.700> see<00:59:44.940> what<00:59:45.180> example<00:59:45.720> 1C<00:59:46.440> is<00:59:47.280> about 00:59:49.490 --> 00:59:49.500 align:start position:0% 00:59:49.500 --> 00:59:53.930 align:start position:0% so 00:59:53.930 --> 00:59:53.940 align:start position:0% 00:59:53.940 --> 00:59:55.910 align:start position:0% I<00:59:54.299> think<00:59:54.599> it's<00:59:54.839> basically<00:59:55.200> the<00:59:55.619> same<00:59:55.740> thing 00:59:55.910 --> 00:59:55.920 align:start position:0% I think it's basically the same thing 00:59:55.920 --> 00:59:58.670 align:start position:0% I think it's basically the same thing but<00:59:56.160> just<00:59:56.400> using<00:59:56.760> the<00:59:57.059> use<00:59:57.240> key<00:59:57.420> hashing<00:59:57.839> so 00:59:58.670 --> 00:59:58.680 align:start position:0% but just using the use key hashing so 00:59:58.680 --> 01:00:00.650 align:start position:0% but just using the use key hashing so what<00:59:58.859> we<00:59:59.040> should<00:59:59.160> expect 01:00:00.650 --> 01:00:00.660 align:start position:0% what we should expect 01:00:00.660 --> 01:00:03.230 align:start position:0% what we should expect unless<01:00:01.440> our<01:00:01.680> yusuke<01:00:02.099> hashing<01:00:02.520> Boolean<01:00:02.880> is 01:00:03.230 --> 01:00:03.240 align:start position:0% unless our yusuke hashing Boolean is 01:00:03.240 --> 01:00:05.510 align:start position:0% unless our yusuke hashing Boolean is implemented<01:00:03.900> improperly<01:00:04.619> is<01:00:05.040> we<01:00:05.339> should 01:00:05.510 --> 01:00:05.520 align:start position:0% implemented improperly is we should 01:00:05.520 --> 01:00:08.870 align:start position:0% implemented improperly is we should expect<01:00:05.700> exactly<01:00:06.299> the<01:00:06.839> the<01:00:07.140> same<01:00:07.859> values<01:00:08.700> that 01:00:08.870 --> 01:00:08.880 align:start position:0% expect exactly the the same values that 01:00:08.880 --> 01:00:10.730 align:start position:0% expect exactly the the same values that we<01:00:09.000> have<01:00:09.119> here<01:00:09.299> including<01:00:09.839> the<01:00:10.140> updated<01:00:10.440> tree 01:00:10.730 --> 01:00:10.740 align:start position:0% we have here including the updated tree 01:00:10.740 --> 01:00:13.069 align:start position:0% we have here including the updated tree root<01:00:11.160> given<01:00:12.000> that<01:00:12.119> we're<01:00:12.359> using<01:00:12.839> the<01:00:12.960> same 01:00:13.069 --> 01:00:13.079 align:start position:0% root given that we're using the same 01:00:13.079 --> 01:00:15.109 align:start position:0% root given that we're using the same yeah<01:00:13.319> testing<01:00:13.799> this<01:00:14.040> valued 01:00:15.109 --> 01:00:15.119 align:start position:0% yeah testing this valued 01:00:15.119 --> 01:00:18.049 align:start position:0% yeah testing this valued that<01:00:15.540> should<01:00:15.720> work<01:00:16.040> so<01:00:17.040> let's<01:00:17.280> see<01:00:17.460> and<01:00:17.940> yeah 01:00:18.049 --> 01:00:18.059 align:start position:0% that should work so let's see and yeah 01:00:18.059 --> 01:00:20.510 align:start position:0% that should work so let's see and yeah as<01:00:18.359> expected<01:00:18.839> we've<01:00:19.260> created<01:00:19.380> a<01:00:19.740> new<01:00:19.859> tree<01:00:20.040> but 01:00:20.510 --> 01:00:20.520 align:start position:0% as expected we've created a new tree but 01:00:20.520 --> 01:00:22.430 align:start position:0% as expected we've created a new tree but we've<01:00:20.760> updated<01:00:21.119> it<01:00:21.359> with<01:00:21.599> the<01:00:21.839> same<01:00:22.079> key<01:00:22.260> value 01:00:22.430 --> 01:00:22.440 align:start position:0% we've updated it with the same key value 01:00:22.440 --> 01:00:25.089 align:start position:0% we've updated it with the same key value pair<01:00:22.799> and<01:00:23.700> we<01:00:23.880> are<01:00:24.000> getting<01:00:24.180> the<01:00:24.420> same<01:00:24.540> updated 01:00:25.089 --> 01:00:25.099 align:start position:0% pair and we are getting the same updated 01:00:25.099 --> 01:00:30.289 align:start position:0% pair and we are getting the same updated try<01:00:26.099> route 01:00:30.289 --> 01:00:30.299 align:start position:0% 01:00:30.299 --> 01:00:33.349 align:start position:0% okay<01:00:30.720> now<01:00:31.619> we're<01:00:31.799> going<01:00:31.920> to<01:00:31.980> do<01:00:32.220> a<01:00:32.760> a<01:00:33.119> different 01:00:33.349 --> 01:00:33.359 align:start position:0% okay now we're going to do a a different 01:00:33.359 --> 01:00:36.470 align:start position:0% okay now we're going to do a a different operation<01:00:34.040> so<01:00:35.040> among<01:00:35.880> the<01:00:36.000> operations<01:00:36.299> that 01:00:36.470 --> 01:00:36.480 align:start position:0% operation so among the operations that 01:00:36.480 --> 01:00:37.789 align:start position:0% operation so among the operations that are<01:00:36.660> possible<01:00:36.900> you<01:00:37.140> can<01:00:37.260> retrieve<01:00:37.559> a<01:00:37.619> value 01:00:37.789 --> 01:00:37.799 align:start position:0% are possible you can retrieve a value 01:00:37.799 --> 01:00:39.470 align:start position:0% are possible you can retrieve a value you<01:00:38.160> can<01:00:38.280> update<01:00:38.579> the<01:00:38.700> tree<01:00:38.819> by<01:00:39.059> adding<01:00:39.359> new 01:00:39.470 --> 01:00:39.480 align:start position:0% you can update the tree by adding new 01:00:39.480 --> 01:00:41.630 align:start position:0% you can update the tree by adding new values<01:00:39.780> you<01:00:40.260> can<01:00:40.319> also<01:00:40.619> delete<01:00:40.859> values<01:00:41.400> from 01:00:41.630 --> 01:00:41.640 align:start position:0% values you can also delete values from 01:00:41.640 --> 01:00:42.410 align:start position:0% values you can also delete values from the<01:00:41.760> tree 01:00:42.410 --> 01:00:42.420 align:start position:0% the tree 01:00:42.420 --> 01:00:44.930 align:start position:0% the tree so<01:00:43.140> let's<01:00:43.380> see<01:00:43.559> what<01:00:43.680> this<01:00:43.859> looks<01:00:44.099> like 01:00:44.930 --> 01:00:44.940 align:start position:0% so let's see what this looks like 01:00:44.940 --> 01:00:48.670 align:start position:0% so let's see what this looks like the<01:00:45.780> as<01:00:46.380> I<01:00:46.680> as<01:00:47.520> I<01:00:47.700> kind<01:00:47.819> of<01:00:47.940> mentioned<01:00:48.240> before 01:00:48.670 --> 01:00:48.680 align:start position:0% the as I as I kind of mentioned before 01:00:48.680 --> 01:00:52.069 align:start position:0% the as I as I kind of mentioned before every<01:00:49.680> tree<01:00:50.579> that<01:00:50.940> is<01:00:51.059> similar<01:00:51.480> that<01:00:51.660> has<01:00:51.839> all 01:00:52.069 --> 01:00:52.079 align:start position:0% every tree that is similar that has all 01:00:52.079 --> 01:00:53.870 align:start position:0% every tree that is similar that has all the<01:00:52.200> same<01:00:52.380> data<01:00:52.680> should<01:00:53.160> you<01:00:53.400> know<01:00:53.579> compute 01:00:53.870 --> 01:00:53.880 align:start position:0% the same data should you know compute 01:00:53.880 --> 01:00:55.609 align:start position:0% the same data should you know compute the<01:00:54.059> same<01:00:54.180> route<01:00:54.359> that's<01:00:54.780> how<01:00:55.140> we<01:00:55.260> get<01:00:55.380> you 01:00:55.609 --> 01:00:55.619 align:start position:0% the same route that's how we get you 01:00:55.619 --> 01:00:58.730 align:start position:0% the same route that's how we get you know<01:00:55.740> the<01:00:56.220> security<01:00:56.339> properties<01:00:56.880> of<01:00:57.180> these<01:00:57.740> uh 01:00:58.730 --> 01:00:58.740 align:start position:0% know the security properties of these uh 01:00:58.740 --> 01:01:00.770 align:start position:0% know the security properties of these uh of<01:00:59.339> these<01:00:59.579> trees 01:01:00.770 --> 01:01:00.780 align:start position:0% of these trees 01:01:00.780 --> 01:01:01.970 align:start position:0% of these trees so<01:01:00.960> what<01:01:01.200> we're<01:01:01.319> going<01:01:01.440> to<01:01:01.500> do<01:01:01.619> is<01:01:01.740> we're<01:01:01.859> going 01:01:01.970 --> 01:01:01.980 align:start position:0% so what we're going to do is we're going 01:01:01.980 --> 01:01:03.530 align:start position:0% so what we're going to do is we're going to<01:01:02.099> update<01:01:02.400> the<01:01:02.520> tree<01:01:02.700> it's<01:01:03.059> going<01:01:03.240> to<01:01:03.299> update 01:01:03.530 --> 01:01:03.540 align:start position:0% to update the tree it's going to update 01:01:03.540 --> 01:01:05.150 align:start position:0% to update the tree it's going to update the<01:01:03.720> route<01:01:03.839> and<01:01:04.380> then<01:01:04.440> we'll<01:01:04.619> we're<01:01:04.920> going<01:01:05.099> to 01:01:05.150 --> 01:01:05.160 align:start position:0% the route and then we'll we're going to 01:01:05.160 --> 01:01:06.829 align:start position:0% the route and then we'll we're going to delete<01:01:05.280> that<01:01:05.700> same<01:01:05.880> key<01:01:06.059> and<01:01:06.359> it<01:01:06.540> should<01:01:06.660> give 01:01:06.829 --> 01:01:06.839 align:start position:0% delete that same key and it should give 01:01:06.839 --> 01:01:08.809 align:start position:0% delete that same key and it should give us<01:01:07.020> back<01:01:07.260> the<01:01:07.799> exact<01:01:08.099> same<01:01:08.220> route<01:01:08.460> that<01:01:08.700> we 01:01:08.809 --> 01:01:08.819 align:start position:0% us back the exact same route that we 01:01:08.819 --> 01:01:13.250 align:start position:0% us back the exact same route that we started<01:01:09.119> with 01:01:13.250 --> 01:01:13.260 align:start position:0% 01:01:13.260 --> 01:01:19.430 align:start position:0% let's<01:01:13.859> look<01:01:14.099> at<01:01:14.400> the<01:01:14.700> code 01:01:19.430 --> 01:01:19.440 align:start position:0% 01:01:19.440 --> 01:01:22.309 align:start position:0% all<01:01:19.980> right<01:01:20.040> yeah<01:01:20.339> create<01:01:20.880> it<01:01:21.180> update<01:01:21.660> it<01:01:21.839> then 01:01:22.309 --> 01:01:22.319 align:start position:0% all right yeah create it update it then 01:01:22.319 --> 01:01:26.150 align:start position:0% all right yeah create it update it then delete<01:01:22.559> using<01:01:23.339> the<01:01:23.700> weight<01:01:24.420> deal<01:01:25.160> helper 01:01:26.150 --> 01:01:26.160 align:start position:0% delete using the weight deal helper 01:01:26.160 --> 01:01:30.170 align:start position:0% delete using the weight deal helper method<01:01:26.520> get<01:01:27.480> it<01:01:27.660> again<01:01:27.780> we 01:01:30.170 --> 01:01:30.180 align:start position:0% method get it again we 01:01:30.180 --> 01:01:33.589 align:start position:0% method get it again we we<01:01:30.240> shouldn't<01:01:31.020> be<01:01:31.200> getting<01:01:31.559> uh<01:01:32.520> a<01:01:32.940> value<01:01:33.119> when 01:01:33.589 --> 01:01:33.599 align:start position:0% we shouldn't be getting uh a value when 01:01:33.599 --> 01:01:37.549 align:start position:0% we shouldn't be getting uh a value when we<01:01:33.780> try<01:01:33.960> to<01:01:34.200> you<01:01:34.559> know<01:01:34.640> retrieve<01:01:35.640> at<01:01:36.540> that<01:01:36.780> key 01:01:37.549 --> 01:01:37.559 align:start position:0% we try to you know retrieve at that key 01:01:37.559 --> 01:01:39.230 align:start position:0% we try to you know retrieve at that key I'm<01:01:37.980> not<01:01:38.160> exactly<01:01:38.520> sure<01:01:38.640> what<01:01:38.880> we're<01:01:39.059> going<01:01:39.180> to 01:01:39.230 --> 01:01:39.240 align:start position:0% I'm not exactly sure what we're going to 01:01:39.240 --> 01:01:41.210 align:start position:0% I'm not exactly sure what we're going to get<01:01:39.359> I'm<01:01:39.540> not<01:01:39.720> sure<01:01:39.839> if<01:01:39.960> it<01:01:40.079> throws<01:01:40.440> or<01:01:40.680> oh<01:01:40.920> it 01:01:41.210 --> 01:01:41.220 align:start position:0% get I'm not sure if it throws or oh it 01:01:41.220 --> 01:01:42.470 align:start position:0% get I'm not sure if it throws or oh it looks<01:01:41.400> like<01:01:41.520> yeah<01:01:41.700> it's<01:01:41.880> going<01:01:42.059> to<01:01:42.119> be<01:01:42.180> null 01:01:42.470 --> 01:01:42.480 align:start position:0% looks like yeah it's going to be null 01:01:42.480 --> 01:01:48.170 align:start position:0% looks like yeah it's going to be null fair<01:01:43.260> enough<01:01:43.579> and<01:01:44.579> uh<01:01:45.000> let's<01:01:45.839> see<01:01:45.960> about<01:01:46.079> that 01:01:48.170 --> 01:01:48.180 align:start position:0% fair enough and uh let's see about that 01:01:48.180 --> 01:01:49.609 align:start position:0% fair enough and uh let's see about that all<01:01:48.720> right 01:01:49.609 --> 01:01:49.619 align:start position:0% all right 01:01:49.619 --> 01:01:52.490 align:start position:0% all right so<01:01:50.099> we<01:01:50.280> are<01:01:50.400> starting<01:01:50.700> out<01:01:51.000> with<01:01:51.359> the<01:01:51.540> M3<01:01:52.020> empty 01:01:52.490 --> 01:01:52.500 align:start position:0% so we are starting out with the M3 empty 01:01:52.500 --> 01:01:54.049 align:start position:0% so we are starting out with the M3 empty try<01:01:52.740> route<01:01:52.980> here 01:01:54.049 --> 01:01:54.059 align:start position:0% try route here 01:01:54.059 --> 01:01:57.349 align:start position:0% try route here it<01:01:54.299> starts<01:01:54.599> with<01:01:54.720> 56<01:01:55.319> E8 01:01:57.349 --> 01:01:57.359 align:start position:0% it starts with 56 E8 01:01:57.359 --> 01:02:01.370 align:start position:0% it starts with 56 E8 then<01:01:58.020> we<01:01:58.380> are<01:01:58.559> updating<01:01:59.220> uh<01:02:00.180> the<01:02:00.420> tree 01:02:01.370 --> 01:02:01.380 align:start position:0% then we are updating uh the tree 01:02:01.380 --> 01:02:04.250 align:start position:0% then we are updating uh the tree we're<01:02:01.799> getting<01:02:02.040> an<01:02:02.640> updated<01:02:02.940> tree<01:02:03.180> root<01:02:03.540> which 01:02:04.250 --> 01:02:04.260 align:start position:0% we're getting an updated tree root which 01:02:04.260 --> 01:02:07.430 align:start position:0% we're getting an updated tree root which is<01:02:04.500> uh<01:02:05.460> similar<01:02:06.119> to<01:02:06.240> the<01:02:06.420> like<01:02:06.660> unhashed<01:02:07.260> key 01:02:07.430 --> 01:02:07.440 align:start position:0% is uh similar to the like unhashed key 01:02:07.440 --> 01:02:09.049 align:start position:0% is uh similar to the like unhashed key one<01:02:07.740> we<01:02:07.980> had<01:02:08.099> before 01:02:09.049 --> 01:02:09.059 align:start position:0% one we had before 01:02:09.059 --> 01:02:11.150 align:start position:0% one we had before and<01:02:09.480> then<01:02:09.599> we<01:02:09.900> are<01:02:10.079> delaying<01:02:10.740> that<01:02:10.920> value 01:02:11.150 --> 01:02:11.160 align:start position:0% and then we are delaying that value 01:02:11.160 --> 01:02:13.010 align:start position:0% and then we are delaying that value again<01:02:11.400> and<01:02:11.760> what<01:02:11.880> do<01:02:12.000> we<01:02:12.119> get<01:02:12.240> back<01:02:12.420> when<01:02:12.720> we 01:02:13.010 --> 01:02:13.020 align:start position:0% again and what do we get back when we 01:02:13.020 --> 01:02:16.430 align:start position:0% again and what do we get back when we query<01:02:13.559> that<01:02:13.799> that<01:02:14.460> tree<01:02:14.700> for<01:02:14.880> that<01:02:15.059> key<01:02:15.260> we<01:02:16.260> uh 01:02:16.430 --> 01:02:16.440 align:start position:0% query that that tree for that key we uh 01:02:16.440 --> 01:02:18.829 align:start position:0% query that that tree for that key we uh we<01:02:16.680> get<01:02:16.799> back<01:02:16.980> now<01:02:17.220> which<01:02:17.700> means<01:02:18.000> like<01:02:18.240> empty 01:02:18.829 --> 01:02:18.839 align:start position:0% we get back now which means like empty 01:02:18.839 --> 01:02:21.410 align:start position:0% we get back now which means like empty no<01:02:19.200> it's<01:02:19.980> not<01:02:20.099> there 01:02:21.410 --> 01:02:21.420 align:start position:0% no it's not there 01:02:21.420 --> 01:02:23.690 align:start position:0% no it's not there and<01:02:22.200> the<01:02:22.440> tree<01:02:22.559> route<01:02:22.740> that<01:02:23.040> we<01:02:23.220> get<01:02:23.520> back 01:02:23.690 --> 01:02:23.700 align:start position:0% and the tree route that we get back 01:02:23.700 --> 01:02:26.450 align:start position:0% and the tree route that we get back after<01:02:24.119> the<01:02:24.540> deletion<01:02:25.020> is<01:02:25.740> the<01:02:25.980> same<01:02:26.099> that<01:02:26.280> we 01:02:26.450 --> 01:02:26.460 align:start position:0% after the deletion is the same that we 01:02:26.460 --> 01:02:29.270 align:start position:0% after the deletion is the same that we start<01:02:26.579> with<01:02:27.240> so<01:02:27.960> yeah<01:02:28.319> I<01:02:28.740> kind<01:02:29.160> of 01:02:29.270 --> 01:02:29.280 align:start position:0% start with so yeah I kind of 01:02:29.280 --> 01:02:31.670 align:start position:0% start with so yeah I kind of demonstrates<01:02:29.819> that<01:02:30.059> every<01:02:30.359> you<01:02:30.960> know<01:02:31.020> same 01:02:31.670 --> 01:02:31.680 align:start position:0% demonstrates that every you know same 01:02:31.680 --> 01:02:38.390 align:start position:0% demonstrates that every you know same tree<01:02:31.920> is<01:02:32.099> going<01:02:32.280> to<01:02:32.339> have<01:02:32.460> the<01:02:32.640> same<01:02:32.700> root 01:02:38.390 --> 01:02:38.400 align:start position:0% 01:02:38.400 --> 01:02:41.930 align:start position:0% yeah<01:02:38.880> so<01:02:39.180> now<01:02:39.359> we're<01:02:39.540> gonna<01:02:39.720> take<01:02:40.140> a<01:02:40.319> bit<01:02:40.440> of<01:02:40.619> a 01:02:41.930 --> 01:02:41.940 align:start position:0% yeah so now we're gonna take a bit of a 01:02:41.940 --> 01:02:45.470 align:start position:0% yeah so now we're gonna take a bit of a deeper<01:02:42.599> look<01:02:42.780> at<01:02:43.319> the<01:02:43.799> actual<01:02:44.339> you<01:02:44.760> know<01:02:44.880> data 01:02:45.470 --> 01:02:45.480 align:start position:0% deeper look at the actual you know data 01:02:45.480 --> 01:02:49.069 align:start position:0% deeper look at the actual you know data structure<01:02:45.839> of<01:02:46.680> uh 01:02:49.069 --> 01:02:49.079 align:start position:0% structure of uh 01:02:49.079 --> 01:02:52.250 align:start position:0% structure of uh the<01:02:49.619> Myrtle<01:02:49.920> producer<01:02:50.280> tree<01:02:51.000> so<01:02:51.480> it<01:02:51.660> has<01:02:51.839> you 01:02:52.250 --> 01:02:52.260 align:start position:0% the Myrtle producer tree so it has you 01:02:52.260 --> 01:02:55.250 align:start position:0% the Myrtle producer tree so it has you want<01:02:52.500> to<01:02:52.680> go<01:02:53.160> for<01:02:53.339> this<01:02:53.839> all<01:02:54.839> right<01:02:54.960> you<01:02:55.079> want 01:02:55.250 --> 01:02:55.260 align:start position:0% want to go for this all right you want 01:02:55.260 --> 01:02:57.230 align:start position:0% want to go for this all right you want me<01:02:55.380> to<01:02:55.440> take<01:02:55.500> over<01:02:55.680> yeah<01:02:56.040> I<01:02:56.940> feel<01:02:57.059> like<01:02:57.119> I've 01:02:57.230 --> 01:02:57.240 align:start position:0% me to take over yeah I feel like I've 01:02:57.240 --> 01:02:58.910 align:start position:0% me to take over yeah I feel like I've been<01:02:57.420> talking<01:02:57.540> about<01:02:57.720> it<01:02:57.960> no<01:02:58.260> you're<01:02:58.500> you're<01:02:58.680> a 01:02:58.910 --> 01:02:58.920 align:start position:0% been talking about it no you're you're a 01:02:58.920 --> 01:03:00.410 align:start position:0% been talking about it no you're you're a good<01:02:58.980> communicator<01:02:59.460> you<01:02:59.640> should<01:02:59.760> do<01:02:59.940> it<01:03:00.059> all 01:03:00.410 --> 01:03:00.420 align:start position:0% good communicator you should do it all 01:03:00.420 --> 01:03:03.770 align:start position:0% good communicator you should do it all right<01:03:00.599> all<01:03:00.780> right<01:03:00.980> so<01:03:01.980> there<01:03:02.940> are<01:03:03.119> four<01:03:03.480> kinds 01:03:03.770 --> 01:03:03.780 align:start position:0% right all right so there are four kinds 01:03:03.780 --> 01:03:04.849 align:start position:0% right all right so there are four kinds of<01:03:03.839> notes 01:03:04.849 --> 01:03:04.859 align:start position:0% of notes 01:03:04.859 --> 01:03:07.490 align:start position:0% of notes in<01:03:05.520> uh<01:03:05.700> Myrtle<01:03:06.059> Beach<01:03:06.240> trees 01:03:07.490 --> 01:03:07.500 align:start position:0% in uh Myrtle Beach trees 01:03:07.500 --> 01:03:10.069 align:start position:0% in uh Myrtle Beach trees so<01:03:07.920> there's<01:03:08.160> the<01:03:08.640> null<01:03:09.000> node<01:03:09.420> which<01:03:09.780> is<01:03:09.900> the 01:03:10.069 --> 01:03:10.079 align:start position:0% so there's the null node which is the 01:03:10.079 --> 01:03:12.289 align:start position:0% so there's the null node which is the one<01:03:10.200> we<01:03:10.440> just<01:03:10.619> queried<01:03:11.280> accidentally<01:03:11.760> by<01:03:12.059> you 01:03:12.289 --> 01:03:12.299 align:start position:0% one we just queried accidentally by you 01:03:12.299 --> 01:03:13.789 align:start position:0% one we just queried accidentally by you know<01:03:12.420> deleting<01:03:12.900> the<01:03:13.020> tree<01:03:13.200> that's<01:03:13.619> a 01:03:13.789 --> 01:03:13.799 align:start position:0% know deleting the tree that's a 01:03:13.799 --> 01:03:16.370 align:start position:0% know deleting the tree that's a non-existent<01:03:14.400> note<01:03:14.640> you<01:03:15.420> get<01:03:15.660> back<01:03:15.839> now<01:03:16.079> when 01:03:16.370 --> 01:03:16.380 align:start position:0% non-existent note you get back now when 01:03:16.380 --> 01:03:17.750 align:start position:0% non-existent note you get back now when you<01:03:16.619> query<01:03:16.859> for<01:03:17.099> something<01:03:17.339> that<01:03:17.579> doesn't 01:03:17.750 --> 01:03:17.760 align:start position:0% you query for something that doesn't 01:03:17.760 --> 01:03:20.930 align:start position:0% you query for something that doesn't exist<01:03:18.660> there<01:03:19.200> is<01:03:19.319> a<01:03:19.440> branch<01:03:19.680> note<01:03:19.920> what<01:03:20.700> a 01:03:20.930 --> 01:03:20.940 align:start position:0% exist there is a branch note what a 01:03:20.940 --> 01:03:23.150 align:start position:0% exist there is a branch note what a branch<01:03:21.119> node<01:03:21.420> does<01:03:21.660> is<01:03:22.260> it's<01:03:22.559> basically<01:03:22.920> an 01:03:23.150 --> 01:03:23.160 align:start position:0% branch node does is it's basically an 01:03:23.160 --> 01:03:25.910 align:start position:0% branch node does is it's basically an intermediary<01:03:23.819> node<01:03:24.180> that<01:03:24.780> points<01:03:25.140> to<01:03:25.319> a<01:03:25.799> bunch 01:03:25.910 --> 01:03:25.920 align:start position:0% intermediary node that points to a bunch 01:03:25.920 --> 01:03:27.470 align:start position:0% intermediary node that points to a bunch of<01:03:26.099> child<01:03:26.520> nodes 01:03:27.470 --> 01:03:27.480 align:start position:0% of child nodes 01:03:27.480 --> 01:03:30.230 align:start position:0% of child nodes there<01:03:28.020> is<01:03:28.200> then<01:03:28.319> the<01:03:28.500> leaf<01:03:28.740> node<01:03:29.099> which<01:03:29.520> is<01:03:29.700> you 01:03:30.230 --> 01:03:30.240 align:start position:0% there is then the leaf node which is you 01:03:30.240 --> 01:03:31.970 align:start position:0% there is then the leaf node which is you know<01:03:30.299> this<01:03:30.660> is<01:03:30.960> called<01:03:31.140> the<01:03:31.260> tree<01:03:31.380> the<01:03:31.619> leaves 01:03:31.970 --> 01:03:31.980 align:start position:0% know this is called the tree the leaves 01:03:31.980 --> 01:03:33.710 align:start position:0% know this is called the tree the leaves are<01:03:32.160> the<01:03:32.520> very<01:03:32.640> end<01:03:32.940> these<01:03:33.359> are<01:03:33.420> the<01:03:33.599> nodes 01:03:33.710 --> 01:03:33.720 align:start position:0% are the very end these are the nodes 01:03:33.720 --> 01:03:35.390 align:start position:0% are the very end these are the nodes that<01:03:33.960> contain<01:03:34.200> like<01:03:34.440> the<01:03:34.680> you<01:03:34.859> know<01:03:34.980> the<01:03:35.220> final 01:03:35.390 --> 01:03:35.400 align:start position:0% that contain like the you know the final 01:03:35.400 --> 01:03:36.650 align:start position:0% that contain like the you know the final values 01:03:36.650 --> 01:03:36.660 align:start position:0% values 01:03:36.660 --> 01:03:39.430 align:start position:0% values and<01:03:37.260> then<01:03:37.380> there<01:03:37.799> are<01:03:38.099> extension<01:03:39.000> nodes 01:03:39.430 --> 01:03:39.440 align:start position:0% and then there are extension nodes 01:03:39.440 --> 01:03:42.950 align:start position:0% and then there are extension nodes extension<01:03:40.440> nodes<01:03:40.740> are<01:03:41.040> the<01:03:41.339> shortcut<01:03:41.819> uh<01:03:42.660> I 01:03:42.950 --> 01:03:42.960 align:start position:0% extension nodes are the shortcut uh I 01:03:42.960 --> 01:03:44.930 align:start position:0% extension nodes are the shortcut uh I was<01:03:43.140> kind<01:03:43.559> of<01:03:43.680> hinting<01:03:44.040> to 01:03:44.930 --> 01:03:44.940 align:start position:0% was kind of hinting to 01:03:44.940 --> 01:03:48.589 align:start position:0% was kind of hinting to so<01:03:45.359> if 01:03:48.589 --> 01:03:48.599 align:start position:0% 01:03:48.599 --> 01:03:50.870 align:start position:0% if<01:03:48.900> you<01:03:49.200> have<01:03:49.319> a<01:03:49.440> key<01:03:49.559> for<01:03:50.040> example<01:03:50.339> I<01:03:50.760> mean 01:03:50.870 --> 01:03:50.880 align:start position:0% if you have a key for example I mean 01:03:50.880 --> 01:03:52.370 align:start position:0% if you have a key for example I mean we're<01:03:51.059> going<01:03:51.240> to<01:03:51.299> see<01:03:51.420> examples<01:03:51.780> actually<01:03:52.020> so 01:03:52.370 --> 01:03:52.380 align:start position:0% we're going to see examples actually so 01:03:52.380 --> 01:03:54.710 align:start position:0% we're going to see examples actually so it<01:03:52.500> might<01:03:52.619> be<01:03:52.799> easier 01:03:54.710 --> 01:03:54.720 align:start position:0% it might be easier 01:03:54.720 --> 01:03:56.990 align:start position:0% it might be easier any<01:03:55.319> question<01:03:55.680> before<01:03:55.980> we<01:03:56.280> dive<01:03:56.460> into<01:03:56.640> looking 01:03:56.990 --> 01:03:57.000 align:start position:0% any question before we dive into looking 01:03:57.000 --> 01:03:59.450 align:start position:0% any question before we dive into looking we're<01:03:57.359> going<01:03:57.540> to<01:03:57.660> look<01:03:57.780> at<01:03:57.900> all<01:03:58.319> these<01:03:58.619> four 01:03:59.450 --> 01:03:59.460 align:start position:0% we're going to look at all these four 01:03:59.460 --> 01:04:01.430 align:start position:0% we're going to look at all these four different<01:03:59.760> kinds<01:04:00.059> of<01:04:00.059> nodes<01:04:00.299> individually 01:04:01.430 --> 01:04:01.440 align:start position:0% different kinds of nodes individually 01:04:01.440 --> 01:04:12.890 align:start position:0% different kinds of nodes individually yep 01:04:12.890 --> 01:04:12.900 align:start position:0% 01:04:12.900 --> 01:04:18.309 align:start position:0% yep 01:04:18.309 --> 01:04:18.319 align:start position:0% 01:04:18.319 --> 01:04:20.990 align:start position:0% yeah<01:04:19.319> how<01:04:19.740> how<01:04:19.740> is<01:04:20.220> that<01:04:20.400> initial<01:04:20.700> route 01:04:20.990 --> 01:04:21.000 align:start position:0% yeah how how is that initial route 01:04:21.000 --> 01:04:25.430 align:start position:0% yeah how how is that initial route created<01:04:21.720> yeah<01:04:22.559> good<01:04:23.040> question<01:04:23.280> I'm 01:04:25.430 --> 01:04:25.440 align:start position:0% created yeah good question I'm 01:04:25.440 --> 01:04:28.430 align:start position:0% created yeah good question I'm I<01:04:25.500> think<01:04:25.920> it's<01:04:26.099> the<01:04:26.400> rlp<01:04:27.000> encoding<01:04:27.720> like<01:04:28.200> it 01:04:28.430 --> 01:04:28.440 align:start position:0% I think it's the rlp encoding like it 01:04:28.440 --> 01:04:30.710 align:start position:0% I think it's the rlp encoding like it has<01:04:28.859> basically<01:04:29.280> still<01:04:29.640> uh<01:04:30.240> you<01:04:30.480> know<01:04:30.540> it's 01:04:30.710 --> 01:04:30.720 align:start position:0% has basically still uh you know it's 01:04:30.720 --> 01:04:32.809 align:start position:0% has basically still uh you know it's it's<01:04:30.900> the<01:04:31.140> hash<01:04:31.319> of<01:04:31.559> the<01:04:31.680> value<01:04:31.859> at<01:04:32.280> that<01:04:32.460> root 01:04:32.809 --> 01:04:32.819 align:start position:0% it's the hash of the value at that root 01:04:32.819 --> 01:04:35.329 align:start position:0% it's the hash of the value at that root because<01:04:33.599> it's<01:04:34.140> initialized<01:04:34.619> with<01:04:34.799> a<01:04:34.920> value<01:04:35.040> if 01:04:35.329 --> 01:04:35.339 align:start position:0% because it's initialized with a value if 01:04:35.339 --> 01:04:37.010 align:start position:0% because it's initialized with a value if it<01:04:35.520> wasn't<01:04:35.760> initialized<01:04:36.359> with<01:04:36.480> a<01:04:36.599> value<01:04:36.720> would 01:04:37.010 --> 01:04:37.020 align:start position:0% it wasn't initialized with a value would 01:04:37.020 --> 01:04:40.130 align:start position:0% it wasn't initialized with a value would just<01:04:37.140> be<01:04:37.319> null<01:04:37.740> you<01:04:38.099> know<01:04:38.160> initially<01:04:38.720> uh<01:04:39.720> the 01:04:40.130 --> 01:04:40.140 align:start position:0% just be null you know initially uh the 01:04:40.140 --> 01:04:42.410 align:start position:0% just be null you know initially uh the way<01:04:40.380> they're<01:04:40.559> defined<01:04:41.040> I'm<01:04:41.880> sorry<01:04:42.119> are<01:04:42.299> you 01:04:42.410 --> 01:04:42.420 align:start position:0% way they're defined I'm sorry are you 01:04:42.420 --> 01:04:44.390 align:start position:0% way they're defined I'm sorry are you asking<01:04:42.660> about<01:04:42.780> the<01:04:43.020> extension<01:04:43.500> node<01:04:43.740> like<01:04:44.099> how 01:04:44.390 --> 01:04:44.400 align:start position:0% asking about the extension node like how 01:04:44.400 --> 01:04:47.210 align:start position:0% asking about the extension node like how how<01:04:44.819> that<01:04:45.119> route<01:04:45.359> comes<01:04:45.780> to<01:04:45.900> be 01:04:47.210 --> 01:04:47.220 align:start position:0% how that route comes to be 01:04:47.220 --> 01:04:52.849 align:start position:0% how that route comes to be the<01:04:47.700> very<01:04:47.880> first<01:04:48.059> yeah 01:04:52.849 --> 01:04:52.859 align:start position:0% 01:04:52.859 --> 01:04:54.950 align:start position:0% yeah 01:04:54.950 --> 01:04:54.960 align:start position:0% 01:04:54.960 --> 01:04:57.049 align:start position:0% yeah so<01:04:55.799> how<01:04:56.040> how<01:04:56.099> would<01:04:56.520> we<01:04:56.640> able<01:04:56.940> to 01:04:57.049 --> 01:04:57.059 align:start position:0% yeah so how how would we able to 01:04:57.059 --> 01:04:59.510 align:start position:0% yeah so how how would we able to calculate<01:04:57.839> ourselves<01:04:58.200> like<01:04:58.440> manually<01:04:58.859> the 01:04:59.510 --> 01:04:59.520 align:start position:0% calculate ourselves like manually the 01:04:59.520 --> 01:05:02.270 align:start position:0% calculate ourselves like manually the hash<01:04:59.819> of<01:05:00.359> the<01:05:00.780> the<01:05:01.020> root<01:05:01.380> node<01:05:01.619> and<01:05:01.859> the<01:05:02.040> empty 01:05:02.270 --> 01:05:02.280 align:start position:0% hash of the the root node and the empty 01:05:02.280 --> 01:05:04.069 align:start position:0% hash of the the root node and the empty root<01:05:02.520> of<01:05:02.819> an<01:05:03.000> empty<01:05:03.240> tree 01:05:04.069 --> 01:05:04.079 align:start position:0% root of an empty tree 01:05:04.079 --> 01:05:05.150 align:start position:0% root of an empty tree yeah 01:05:05.150 --> 01:05:05.160 align:start position:0% yeah 01:05:05.160 --> 01:05:06.589 align:start position:0% yeah so 01:05:06.589 --> 01:05:06.599 align:start position:0% so 01:05:06.599 --> 01:05:08.450 align:start position:0% so so<01:05:06.839> yeah<01:05:07.200> we<01:05:07.380> can<01:05:07.559> actually<01:05:07.799> look<01:05:08.099> at<01:05:08.280> that 01:05:08.450 --> 01:05:08.460 align:start position:0% so yeah we can actually look at that 01:05:08.460 --> 01:05:10.309 align:start position:0% so yeah we can actually look at that directly<01:05:08.940> in<01:05:09.299> the<01:05:09.420> code 01:05:10.309 --> 01:05:10.319 align:start position:0% directly in the code 01:05:10.319 --> 01:05:11.690 align:start position:0% directly in the code uh 01:05:11.690 --> 01:05:11.700 align:start position:0% uh 01:05:11.700 --> 01:05:15.770 align:start position:0% uh we<01:05:12.180> have<01:05:12.440> uh<01:05:13.440> we<01:05:14.220> set<01:05:14.400> empty<01:05:14.880> try<01:05:15.119> route<01:05:15.359> that's 01:05:15.770 --> 01:05:15.780 align:start position:0% we have uh we set empty try route that's 01:05:15.780 --> 01:05:17.809 align:start position:0% we have uh we set empty try route that's like<01:05:16.020> a<01:05:16.260> specific<01:05:16.740> like<01:05:16.980> constant<01:05:17.460> property 01:05:17.809 --> 01:05:17.819 align:start position:0% like a specific like constant property 01:05:17.819 --> 01:05:21.289 align:start position:0% like a specific like constant property when<01:05:18.240> so<01:05:18.839> when<01:05:19.020> we<01:05:19.200> construct<01:05:19.740> uh<01:05:20.460> when<01:05:21.180> we 01:05:21.289 --> 01:05:21.299 align:start position:0% when so when we construct uh when we 01:05:21.299 --> 01:05:23.450 align:start position:0% when so when we construct uh when we initialize<01:05:21.780> a<01:05:21.960> new<01:05:22.079> tree<01:05:22.319> what<01:05:22.740> runs<01:05:23.160> is<01:05:23.280> like 01:05:23.450 --> 01:05:23.460 align:start position:0% initialize a new tree what runs is like 01:05:23.460 --> 01:05:25.569 align:start position:0% initialize a new tree what runs is like this<01:05:23.700> Constructor<01:05:24.299> function 01:05:25.569 --> 01:05:25.579 align:start position:0% this Constructor function 01:05:25.579 --> 01:05:28.309 align:start position:0% this Constructor function if<01:05:26.579> we<01:05:26.700> don't<01:05:26.880> provide<01:05:27.180> options<01:05:27.599> and<01:05:27.960> we<01:05:28.140> we 01:05:28.309 --> 01:05:28.319 align:start position:0% if we don't provide options and we we 01:05:28.319 --> 01:05:29.630 align:start position:0% if we don't provide options and we we have<01:05:28.500> like<01:05:28.619> default<01:05:28.980> options<01:05:29.339> that<01:05:29.520> we 01:05:29.630 --> 01:05:29.640 align:start position:0% have like default options that we 01:05:29.640 --> 01:05:32.030 align:start position:0% have like default options that we provide<01:05:29.940> we<01:05:30.900> instantiate<01:05:31.380> the<01:05:31.500> database<01:05:31.859> and 01:05:32.030 --> 01:05:32.040 align:start position:0% provide we instantiate the database and 01:05:32.040 --> 01:05:33.829 align:start position:0% provide we instantiate the database and then<01:05:32.220> the<01:05:32.460> very<01:05:32.579> next<01:05:32.880> thing<01:05:33.059> we<01:05:33.299> do<01:05:33.420> is 01:05:33.829 --> 01:05:33.839 align:start position:0% then the very next thing we do is 01:05:33.839 --> 01:05:36.530 align:start position:0% then the very next thing we do is initialize<01:05:34.559> the<01:05:35.040> empty<01:05:35.520> try<01:05:35.819> root<01:05:36.180> which<01:05:36.420> is 01:05:36.530 --> 01:05:36.540 align:start position:0% initialize the empty try root which is 01:05:36.540 --> 01:05:38.630 align:start position:0% initialize the empty try root which is exactly<01:05:36.900> the<01:05:37.079> thing<01:05:37.200> you<01:05:37.440> know<01:05:37.559> you're<01:05:37.920> asking 01:05:38.630 --> 01:05:38.640 align:start position:0% exactly the thing you know you're asking 01:05:38.640 --> 01:05:41.930 align:start position:0% exactly the thing you know you're asking about<01:05:39.299> uh<01:05:39.960> this<01:05:40.200> is<01:05:40.319> actually<01:05:40.500> quite<01:05:40.920> simple 01:05:41.930 --> 01:05:41.940 align:start position:0% about uh this is actually quite simple 01:05:41.940 --> 01:05:45.770 align:start position:0% about uh this is actually quite simple so<01:05:42.480> what<01:05:42.720> it<01:05:42.839> is<01:05:42.960> is<01:05:43.319> uh<01:05:43.859> the<01:05:44.339> rlp<01:05:44.819> encoding<01:05:45.420> of 01:05:45.770 --> 01:05:45.780 align:start position:0% so what it is is uh the rlp encoding of 01:05:45.780 --> 01:05:47.150 align:start position:0% so what it is is uh the rlp encoding of an<01:05:45.900> empty<01:05:46.260> string 01:05:47.150 --> 01:05:47.160 align:start position:0% an empty string 01:05:47.160 --> 01:05:52.789 align:start position:0% an empty string which<01:05:47.880> uh 01:05:52.789 --> 01:05:52.799 align:start position:0% 01:05:52.799 --> 01:05:55.910 align:start position:0% yeah<01:05:53.220> Constance<01:05:53.760> okay<01:05:54.119> so<01:05:54.480> it's<01:05:54.720> buffer<01:05:55.140> Ox<01:05:55.440> 80 01:05:55.910 --> 01:05:55.920 align:start position:0% yeah Constance okay so it's buffer Ox 80 01:05:55.920 --> 01:05:58.910 align:start position:0% yeah Constance okay so it's buffer Ox 80 and<01:05:56.700> that's<01:05:56.940> that's<01:05:57.480> like<01:05:57.720> it<01:05:58.079> I<01:05:58.500> guess<01:05:58.619> sort 01:05:58.910 --> 01:05:58.920 align:start position:0% and that's that's like it I guess sort 01:05:58.920 --> 01:06:02.150 align:start position:0% and that's that's like it I guess sort of<01:05:59.040> a<01:05:59.160> universal<01:06:00.119> for<01:06:00.420> empty<01:06:00.900> tree<01:06:01.079> yeah 01:06:02.150 --> 01:06:02.160 align:start position:0% of a universal for empty tree yeah 01:06:02.160 --> 01:06:10.190 align:start position:0% of a universal for empty tree yeah all<01:06:02.579> right<01:06:02.640> so<01:06:02.940> we<01:06:03.059> empty<01:06:03.420> rlp 01:06:10.190 --> 01:06:10.200 align:start position:0% 01:06:10.200 --> 01:06:13.370 align:start position:0% well<01:06:11.099> it<01:06:11.400> there's<01:06:12.059> actually<01:06:12.359> the<01:06:12.660> idea<01:06:13.020> a 01:06:13.370 --> 01:06:13.380 align:start position:0% well it there's actually the idea a 01:06:13.380 --> 01:06:16.250 align:start position:0% well it there's actually the idea a desirable<01:06:13.740> property<01:06:14.220> yeah<01:06:14.640> that<01:06:15.420> all<01:06:15.720> you<01:06:16.200> can 01:06:16.250 --> 01:06:16.260 align:start position:0% desirable property yeah that all you can 01:06:16.260 --> 01:06:18.890 align:start position:0% desirable property yeah that all you can know<01:06:16.440> if<01:06:16.680> and<01:06:16.920> you<01:06:17.280> could<01:06:17.400> identify<01:06:18.240> all<01:06:18.540> empty 01:06:18.890 --> 01:06:18.900 align:start position:0% know if and you could identify all empty 01:06:18.900 --> 01:06:22.250 align:start position:0% know if and you could identify all empty trees<01:06:19.200> from<01:06:19.799> exactly<01:06:20.280> that<01:06:20.579> right<01:06:21.059> like<01:06:21.420> the 01:06:22.250 --> 01:06:22.260 align:start position:0% trees from exactly that right like the 01:06:22.260 --> 01:06:23.690 align:start position:0% trees from exactly that right like the same<01:06:22.380> tree<01:06:22.619> should<01:06:22.980> always<01:06:23.160> have<01:06:23.339> the<01:06:23.520> same 01:06:23.690 --> 01:06:23.700 align:start position:0% same tree should always have the same 01:06:23.700 --> 01:06:25.789 align:start position:0% same tree should always have the same route<01:06:23.940> same<01:06:24.780> with<01:06:24.960> an<01:06:25.140> empty<01:06:25.380> tree<01:06:25.559> every 01:06:25.789 --> 01:06:25.799 align:start position:0% route same with an empty tree every 01:06:25.799 --> 01:06:28.309 align:start position:0% route same with an empty tree every empty<01:06:26.220> tree<01:06:26.400> will<01:06:26.640> have<01:06:26.819> the<01:06:26.940> same<01:06:27.059> route 01:06:28.309 --> 01:06:28.319 align:start position:0% empty tree will have the same route 01:06:28.319 --> 01:06:32.270 align:start position:0% empty tree will have the same route yeah<01:06:28.859> and<01:06:29.160> if<01:06:29.400> we<01:06:29.760> let<01:06:30.539> me<01:06:30.780> take<01:06:31.140> that<01:06:31.740> example 01:06:32.270 --> 01:06:32.280 align:start position:0% yeah and if we let me take that example 01:06:32.280 --> 01:06:35.089 align:start position:0% yeah and if we let me take that example file<01:06:32.640> actually<01:06:33.059> and<01:06:33.480> just<01:06:33.660> compute 01:06:35.089 --> 01:06:35.099 align:start position:0% file actually and just compute 01:06:35.099 --> 01:06:44.210 align:start position:0% file actually and just compute that<01:06:35.700> you 01:06:44.210 --> 01:06:44.220 align:start position:0% 01:06:44.220 --> 01:06:46.250 align:start position:0% have<01:06:44.280> so<01:06:44.880> we're<01:06:45.119> gonna<01:06:45.420> need<01:06:45.720> what<01:06:46.020> we're 01:06:46.250 --> 01:06:46.260 align:start position:0% have so we're gonna need what we're 01:06:46.260 --> 01:06:53.390 align:start position:0% have so we're gonna need what we're gonna<01:06:46.440> need<01:06:46.740> something<01:06:47.220> from<01:06:47.640> rlp 01:06:53.390 --> 01:06:53.400 align:start position:0% 01:06:53.400 --> 01:07:01.309 align:start position:0% let<01:06:53.760> me<01:06:53.880> do<01:06:54.059> it<01:06:54.180> in<01:06:54.299> the<01:06:54.420> rlp<01:06:54.900> package<01:06:55.440> actually 01:07:01.309 --> 01:07:01.319 align:start position:0% 01:07:01.319 --> 01:07:02.750 align:start position:0% yeah<01:07:01.500> I'm<01:07:01.680> having<01:07:01.920> a<01:07:02.099> bit<01:07:02.280> of<01:07:02.520> trouble 01:07:02.750 --> 01:07:02.760 align:start position:0% yeah I'm having a bit of trouble 01:07:02.760 --> 01:07:05.270 align:start position:0% yeah I'm having a bit of trouble navigating<01:07:03.299> with<01:07:03.660> my<01:07:03.900> screens<01:07:04.319> so 01:07:05.270 --> 01:07:05.280 align:start position:0% navigating with my screens so 01:07:05.280 --> 01:07:11.990 align:start position:0% navigating with my screens so zoomed<01:07:06.119> in 01:07:11.990 --> 01:07:12.000 align:start position:0% 01:07:12.000 --> 01:07:14.210 align:start position:0% feel<01:07:12.480> free<01:07:12.720> to<01:07:12.900> throw<01:07:13.140> out<01:07:13.319> questions<01:07:13.559> or<01:07:13.920> call 01:07:14.210 --> 01:07:14.220 align:start position:0% feel free to throw out questions or call 01:07:14.220 --> 01:07:16.430 align:start position:0% feel free to throw out questions or call me<01:07:14.400> over<01:07:14.520> if<01:07:14.819> you<01:07:14.940> want<01:07:15.059> to 01:07:16.430 --> 01:07:16.440 align:start position:0% me over if you want to 01:07:16.440 --> 01:07:26.210 align:start position:0% me over if you want to chat<01:07:16.920> individually 01:07:26.210 --> 01:07:26.220 align:start position:0% 01:07:26.220 --> 01:07:28.430 align:start position:0% all<01:07:26.640> right<01:07:26.819> so<01:07:27.119> this<01:07:27.299> is<01:07:27.420> importing<01:07:27.960> the 01:07:28.430 --> 01:07:28.440 align:start position:0% all right so this is importing the 01:07:28.440 --> 01:07:32.990 align:start position:0% all right so this is importing the encode<01:07:29.299> method<01:07:30.299> from<01:07:30.720> the<01:07:30.900> rlp<01:07:31.380> library 01:07:32.990 --> 01:07:33.000 align:start position:0% encode method from the rlp library 01:07:33.000 --> 01:07:34.990 align:start position:0% encode method from the rlp library so<01:07:33.299> what<01:07:33.420> do<01:07:33.539> we<01:07:33.660> should<01:07:33.839> expect<01:07:34.020> to<01:07:34.319> get<01:07:34.559> back 01:07:34.990 --> 01:07:35.000 align:start position:0% so what do we should expect to get back 01:07:35.000 --> 01:07:38.349 align:start position:0% so what do we should expect to get back uh<01:07:36.000> from<01:07:36.420> you<01:07:36.660> know<01:07:36.780> an<01:07:36.960> empty<01:07:37.260> string 01:07:38.349 --> 01:07:38.359 align:start position:0% uh from you know an empty string 01:07:38.359 --> 01:07:41.630 align:start position:0% uh from you know an empty string rlp<01:07:39.359> encoding<01:07:39.780> would<01:07:40.020> be<01:07:40.140> Ox<01:07:40.500> 80<01:07:40.920> which<01:07:41.339> is<01:07:41.460> you 01:07:41.630 --> 01:07:41.640 align:start position:0% rlp encoding would be Ox 80 which is you 01:07:41.640 --> 01:07:45.529 align:start position:0% rlp encoding would be Ox 80 which is you know<01:07:41.760> the<01:07:41.940> buffer<01:07:42.299> we<01:07:42.960> we<01:07:43.200> just<01:07:43.740> saw<01:07:43.920> before 01:07:45.529 --> 01:07:45.539 align:start position:0% know the buffer we we just saw before 01:07:45.539 --> 01:07:47.750 align:start position:0% know the buffer we we just saw before so<01:07:46.020> I'm<01:07:46.200> gonna<01:07:46.380> have<01:07:46.559> to<01:07:46.740> move<01:07:47.099> out<01:07:47.400> of<01:07:47.579> that 01:07:47.750 --> 01:07:47.760 align:start position:0% so I'm gonna have to move out of that 01:07:47.760 --> 01:07:50.569 align:start position:0% so I'm gonna have to move out of that repo<01:07:48.420> going<01:07:49.140> to<01:07:49.319> the<01:07:49.500> example<01:07:49.980> solder<01:07:50.400> and 01:07:50.569 --> 01:07:50.579 align:start position:0% repo going to the example solder and 01:07:50.579 --> 01:07:57.170 align:start position:0% repo going to the example solder and then<01:07:50.760> run<01:07:51.059> this 01:07:57.170 --> 01:07:57.180 align:start position:0% 01:07:57.180 --> 01:08:08.690 align:start position:0% am<01:07:57.660> I<01:07:57.839> not<01:07:57.960> in<01:07:58.200> the<01:07:58.380> right<01:07:58.500> or<01:07:59.039> it's<01:07:59.400> test 01:08:08.690 --> 01:08:08.700 align:start position:0% 01:08:08.700 --> 01:08:20.090 align:start position:0% okay<01:08:09.180> so<01:08:09.599> why<01:08:09.900> is<01:08:10.079> it<01:08:10.260> not<01:08:10.559> a<01:08:10.980> logging 01:08:20.090 --> 01:08:20.100 align:start position:0% 01:08:20.100 --> 01:08:22.309 align:start position:0% always<01:08:20.520> interesting<01:08:20.940> when<01:08:21.179> you<01:08:21.359> do<01:08:21.540> live 01:08:22.309 --> 01:08:22.319 align:start position:0% always interesting when you do live 01:08:22.319 --> 01:08:24.950 align:start position:0% always interesting when you do live coding<01:08:22.799> so<01:08:23.520> figure<01:08:23.940> out<01:08:24.060> how<01:08:24.299> to<01:08:24.420> cancel<01:08:24.600> log 01:08:24.950 --> 01:08:24.960 align:start position:0% coding so figure out how to cancel log 01:08:24.960 --> 01:08:30.709 align:start position:0% coding so figure out how to cancel log something 01:08:30.709 --> 01:08:30.719 align:start position:0% 01:08:30.719 --> 01:08:34.789 align:start position:0% thank<01:08:31.199> you 01:08:34.789 --> 01:08:34.799 align:start position:0% 01:08:34.799 --> 01:08:44.650 align:start position:0% very<01:08:35.460> much 01:08:44.650 --> 01:08:44.660 align:start position:0% 01:08:44.660 --> 01:08:47.450 align:start position:0% yeah<01:08:45.660> I<01:08:45.839> switched<01:08:46.140> package<01:08:46.440> there 01:08:47.450 --> 01:08:47.460 align:start position:0% yeah I switched package there 01:08:47.460 --> 01:08:50.090 align:start position:0% yeah I switched package there before<01:08:47.759> the 01:08:50.090 --> 01:08:50.100 align:start position:0% 01:08:50.100 --> 01:09:04.610 align:start position:0% can<01:08:50.580> just<01:08:50.819> actually<01:08:51.060> import 01:09:04.610 --> 01:09:04.620 align:start position:0% 01:09:04.620 --> 01:09:08.450 align:start position:0% they<01:09:04.980> all<01:09:05.160> just<01:09:05.339> import<01:09:05.580> it<01:09:05.940> directly<01:09:06.239> from 01:09:08.450 --> 01:09:08.460 align:start position:0% they all just import it directly from 01:09:08.460 --> 01:09:10.309 align:start position:0% they all just import it directly from there 01:09:10.309 --> 01:09:10.319 align:start position:0% there 01:09:10.319 --> 01:09:22.970 align:start position:0% there this 01:09:22.970 --> 01:09:22.980 align:start position:0% 01:09:22.980 --> 01:09:42.470 align:start position:0% oh<01:09:23.400> it's<01:09:23.580> actually<01:09:23.699> in<01:09:23.880> bin<01:09:24.120> for<01:09:24.299> that<01:09:24.420> folder 01:09:42.470 --> 01:09:42.480 align:start position:0% 01:09:42.480 --> 01:09:43.849 align:start position:0% all<01:09:42.900> right<01:09:42.960> let's<01:09:43.140> see<01:09:43.380> if<01:09:43.440> we<01:09:43.560> can<01:09:43.679> get 01:09:43.849 --> 01:09:43.859 align:start position:0% all right let's see if we can get 01:09:43.859 --> 01:09:56.689 align:start position:0% all right let's see if we can get something<01:09:44.040> going<01:09:44.400> now 01:09:56.689 --> 01:09:56.699 align:start position:0% 01:09:56.699 --> 01:10:00.890 align:start position:0% let<01:09:57.300> me<01:09:57.480> just<01:09:57.719> rename<01:09:58.320> that<01:09:58.620> to<01:09:59.360> address<01:10:00.360> file 01:10:00.890 --> 01:10:00.900 align:start position:0% let me just rename that to address file 01:10:00.900 --> 01:10:12.470 align:start position:0% let me just rename that to address file actually 01:10:12.470 --> 01:10:12.480 align:start position:0% 01:10:12.480 --> 01:10:15.410 align:start position:0% right<01:10:13.199> it<01:10:13.679> is<01:10:13.860> not 01:10:15.410 --> 01:10:15.420 align:start position:0% right it is not 01:10:15.420 --> 01:10:22.250 align:start position:0% right it is not working<01:10:16.140> at<01:10:17.040> all 01:10:22.250 --> 01:10:22.260 align:start position:0% 01:10:22.260 --> 01:10:26.270 align:start position:0% all<01:10:22.860> right<01:10:23.040> okay<01:10:23.580> we're<01:10:24.420> finally<01:10:24.780> yeah<01:10:25.280> I'm 01:10:26.270 --> 01:10:26.280 align:start position:0% all right okay we're finally yeah I'm 01:10:26.280 --> 01:10:27.649 align:start position:0% all right okay we're finally yeah I'm getting<01:10:26.520> about<01:10:26.699> something<01:10:26.940> and<01:10:27.480> we're 01:10:27.649 --> 01:10:27.659 align:start position:0% getting about something and we're 01:10:27.659 --> 01:10:30.830 align:start position:0% getting about something and we're getting<01:10:27.840> back<01:10:28.199> uh<01:10:28.860> 128. 01:10:30.830 --> 01:10:30.840 align:start position:0% getting back uh 128. 01:10:30.840 --> 01:10:33.590 align:start position:0% getting back uh 128. is<01:10:31.320> that<01:10:31.440> ox80<01:10:32.040> in<01:10:32.520> HEX 01:10:33.590 --> 01:10:33.600 align:start position:0% is that ox80 in HEX 01:10:33.600 --> 01:10:36.649 align:start position:0% is that ox80 in HEX let<01:10:34.020> me<01:10:34.140> actually 01:10:36.649 --> 01:10:36.659 align:start position:0% 01:10:36.659 --> 01:10:44.930 align:start position:0% end<01:10:36.900> in<01:10:37.140> 20<01:10:37.320> minutes 01:10:44.930 --> 01:10:44.940 align:start position:0% 01:10:44.940 --> 01:10:46.010 align:start position:0% oh<01:10:45.120> yeah<01:10:45.300> it's<01:10:45.480> gonna<01:10:45.600> be<01:10:45.659> hard<01:10:45.780> to<01:10:45.900> import 01:10:46.010 --> 01:10:46.020 align:start position:0% oh yeah it's gonna be hard to import 01:10:46.020 --> 01:10:59.570 align:start position:0% oh yeah it's gonna be hard to import packages<01:10:46.500> in<01:10:46.800> a<01:10:46.920> JS<01:10:47.280> file<01:10:47.460> like<01:10:47.699> that 01:10:59.570 --> 01:10:59.580 align:start position:0% 01:10:59.580 --> 01:11:12.830 align:start position:0% foreign 01:11:12.830 --> 01:11:12.840 align:start position:0% 01:11:12.840 --> 01:11:15.110 align:start position:0% okay<01:11:13.380> yeah<01:11:13.560> so<01:11:13.739> 128<01:11:14.219> we<01:11:14.460> we<01:11:14.640> got<01:11:14.760> back<01:11:14.940> the 01:11:15.110 --> 01:11:15.120 align:start position:0% okay yeah so 128 we we got back the 01:11:15.120 --> 01:11:17.930 align:start position:0% okay yeah so 128 we we got back the decimal<01:11:15.480> value<01:11:15.719> but<01:11:16.140> 128<01:11:16.739> is<01:11:16.980> like<01:11:17.100> ox<01:11:17.400> 80<01:11:17.760> in 01:11:17.930 --> 01:11:17.940 align:start position:0% decimal value but 128 is like ox 80 in 01:11:17.940 --> 01:11:20.870 align:start position:0% decimal value but 128 is like ox 80 in decimals<01:11:18.480> which<01:11:19.080> is<01:11:19.260> the<01:11:19.560> the<01:11:19.800> value<01:11:20.520> that 01:11:20.870 --> 01:11:20.880 align:start position:0% decimals which is the the value that 01:11:20.880 --> 01:11:22.850 align:start position:0% decimals which is the the value that we're<01:11:21.120> using<01:11:21.960> inside<01:11:22.140> of<01:11:22.380> the<01:11:22.500> tree<01:11:22.620> to 01:11:22.850 --> 01:11:22.860 align:start position:0% we're using inside of the tree to 01:11:22.860 --> 01:11:24.530 align:start position:0% we're using inside of the tree to compute<01:11:23.159> the<01:11:23.400> root<01:11:23.640> hash 01:11:24.530 --> 01:11:24.540 align:start position:0% compute the root hash 01:11:24.540 --> 01:11:26.810 align:start position:0% compute the root hash so<01:11:25.020> we<01:11:25.260> are<01:11:25.440> basically<01:11:25.860> just<01:11:26.100> to<01:11:26.280> to<01:11:26.460> compute 01:11:26.810 --> 01:11:26.820 align:start position:0% so we are basically just to to compute 01:11:26.820 --> 01:11:28.669 align:start position:0% so we are basically just to to compute that<01:11:27.000> you<01:11:27.239> know<01:11:27.300> root<01:11:27.659> hash<01:11:27.780> we<01:11:28.260> are<01:11:28.440> just 01:11:28.669 --> 01:11:28.679 align:start position:0% that you know root hash we are just 01:11:28.679 --> 01:11:32.870 align:start position:0% that you know root hash we are just hashing<01:11:29.640> ox80<01:11:30.420> so<01:11:31.080> if<01:11:31.260> we<01:11:31.500> take<01:11:31.739> the<01:11:32.219> kecought 01:11:32.870 --> 01:11:32.880 align:start position:0% hashing ox80 so if we take the kecought 01:11:32.880 --> 01:11:37.010 align:start position:0% hashing ox80 so if we take the kecought hash<01:11:33.679> of<01:11:34.679> the 01:11:37.010 --> 01:11:37.020 align:start position:0% hash of the 01:11:37.020 --> 01:11:38.810 align:start position:0% hash of the let<01:11:37.380> me<01:11:37.560> look<01:11:37.739> back<01:11:37.920> at<01:11:38.040> a<01:11:38.219> place<01:11:38.340> where<01:11:38.640> we 01:11:38.810 --> 01:11:38.820 align:start position:0% let me look back at a place where we 01:11:38.820 --> 01:11:41.090 align:start position:0% let me look back at a place where we were<01:11:39.060> using<01:11:39.480> KitKat<01:11:40.320> so<01:11:40.500> I<01:11:40.620> don't<01:11:40.679> have<01:11:40.860> to 01:11:41.090 --> 01:11:41.100 align:start position:0% were using KitKat so I don't have to 01:11:41.100 --> 01:11:44.330 align:start position:0% were using KitKat so I don't have to re-import<01:11:42.060> manually 01:11:44.330 --> 01:11:44.340 align:start position:0% re-import manually 01:11:44.340 --> 01:11:48.169 align:start position:0% re-import manually so<01:11:44.760> if<01:11:44.940> we're<01:11:45.120> doing<01:11:45.360> the 01:11:48.169 --> 01:11:48.179 align:start position:0% 01:11:48.179 --> 01:11:52.189 align:start position:0% kecought<01:11:48.840> 256<01:11:49.800> of<01:11:50.219> a<01:11:50.520> buffer<01:11:51.060> from<01:11:51.360> like<01:11:51.659> ox80 01:11:52.189 --> 01:11:52.199 align:start position:0% kecought 256 of a buffer from like ox80 01:11:52.199 --> 01:11:53.810 align:start position:0% kecought 256 of a buffer from like ox80 we<01:11:52.679> should<01:11:52.800> expect<01:11:52.920> to<01:11:53.219> get<01:11:53.340> back<01:11:53.520> to<01:11:53.640> the 01:11:53.810 --> 01:11:53.820 align:start position:0% we should expect to get back to the 01:11:53.820 --> 01:11:57.050 align:start position:0% we should expect to get back to the exact<01:11:54.060> same<01:11:54.360> like<01:11:54.679> empty<01:11:55.679> hash<01:11:56.460> that<01:11:56.760> serves 01:11:57.050 --> 01:11:57.060 align:start position:0% exact same like empty hash that serves 01:11:57.060 --> 01:11:58.850 align:start position:0% exact same like empty hash that serves as<01:11:57.239> uh<01:11:57.540> the<01:11:57.780> root<01:11:58.020> of<01:11:58.140> an<01:11:58.260> empty<01:11:58.440> Miracle 01:11:58.850 --> 01:11:58.860 align:start position:0% as uh the root of an empty Miracle 01:11:58.860 --> 01:11:59.870 align:start position:0% as uh the root of an empty Miracle pituitary 01:11:59.870 --> 01:11:59.880 align:start position:0% pituitary 01:11:59.880 --> 01:12:02.810 align:start position:0% pituitary so<01:12:00.300> let's<01:12:00.480> see<01:12:00.600> if<01:12:00.719> we<01:12:00.840> can<01:12:00.960> reproduce<01:12:01.500> that 01:12:02.810 --> 01:12:02.820 align:start position:0% so let's see if we can reproduce that 01:12:02.820 --> 01:12:11.810 align:start position:0% so let's see if we can reproduce that ourself 01:12:11.810 --> 01:12:11.820 align:start position:0% 01:12:11.820 --> 01:12:13.490 align:start position:0% we'll<01:12:12.120> just<01:12:12.239> comment<01:12:12.540> out<01:12:12.719> the<01:12:12.900> rest<01:12:13.080> to 01:12:13.490 --> 01:12:13.500 align:start position:0% we'll just comment out the rest to 01:12:13.500 --> 01:12:17.270 align:start position:0% we'll just comment out the rest to remove<01:12:14.219> some<01:12:14.640> noise 01:12:17.270 --> 01:12:17.280 align:start position:0% 01:12:17.280 --> 01:12:31.850 align:start position:0% navigate<01:12:17.699> back<01:12:18.239> to<01:12:18.420> the<01:12:18.960> tree<01:12:19.500> package 01:12:31.850 --> 01:12:31.860 align:start position:0% 01:12:31.860 --> 01:12:34.550 align:start position:0% maybe<01:12:32.460> I<01:12:32.699> have<01:12:32.820> to 01:12:34.550 --> 01:12:34.560 align:start position:0% maybe I have to 01:12:34.560 --> 01:12:45.350 align:start position:0% maybe I have to that<01:12:35.400> as<01:12:35.820> this<01:12:36.179> string 01:12:45.350 --> 01:12:45.360 align:start position:0% 01:12:45.360 --> 01:12:47.330 align:start position:0% all<01:12:45.780> right<01:12:45.960> so<01:12:46.199> we're<01:12:46.320> getting<01:12:46.560> back<01:12:46.739> a<01:12:46.920> uint 01:12:47.330 --> 01:12:47.340 align:start position:0% all right so we're getting back a uint 01:12:47.340 --> 01:12:51.530 align:start position:0% all right so we're getting back a uint array 01:12:51.530 --> 01:12:51.540 align:start position:0% 01:12:51.540 --> 01:12:54.470 align:start position:0% I<01:12:51.960> just<01:12:52.140> need<01:12:52.260> to<01:12:52.380> convert<01:12:52.800> that<01:12:53.040> to 01:12:54.470 --> 01:12:54.480 align:start position:0% I just need to convert that to 01:12:54.480 --> 01:12:57.590 align:start position:0% I just need to convert that to hex 01:12:57.590 --> 01:12:57.600 align:start position:0% 01:12:57.600 --> 01:12:59.270 align:start position:0% then<01:12:57.960> we<01:12:58.199> should<01:12:58.320> be<01:12:58.440> getting<01:12:58.620> back<01:12:58.920> to<01:12:59.100> the 01:12:59.270 --> 01:12:59.280 align:start position:0% then we should be getting back to the 01:12:59.280 --> 01:13:01.070 align:start position:0% then we should be getting back to the same<01:12:59.580> route<01:12:59.760> that<01:13:00.120> we 01:13:01.070 --> 01:13:01.080 align:start position:0% same route that we 01:13:01.080 --> 01:13:19.250 align:start position:0% same route that we initially<01:13:01.739> started<01:13:02.159> with 01:13:19.250 --> 01:13:19.260 align:start position:0% 01:13:19.260 --> 01:13:22.370 align:start position:0% so<01:13:19.440> we<01:13:19.679> have<01:13:19.800> a<01:13:19.860> buffer<01:13:20.159> to<01:13:20.340> hex<01:13:20.699> util<01:13:21.659> in<01:13:22.260> the 01:13:22.370 --> 01:13:22.380 align:start position:0% so we have a buffer to hex util in the 01:13:22.380 --> 01:13:24.950 align:start position:0% so we have a buffer to hex util in the package<01:13:22.739> now<01:13:23.340> the<01:13:23.699> way<01:13:23.820> my<01:13:24.120> testing<01:13:24.600> thing<01:13:24.780> is 01:13:24.950 --> 01:13:24.960 align:start position:0% package now the way my testing thing is 01:13:24.960 --> 01:13:28.490 align:start position:0% package now the way my testing thing is set<01:13:25.140> up<01:13:25.320> might<01:13:25.560> not<01:13:25.800> allow<01:13:26.219> me<01:13:26.640> to<01:13:26.880> import<01:13:27.000> that 01:13:28.490 --> 01:13:28.500 align:start position:0% set up might not allow me to import that 01:13:28.500 --> 01:13:30.709 align:start position:0% set up might not allow me to import that yeah 01:13:30.709 --> 01:13:30.719 align:start position:0% yeah 01:13:30.719 --> 01:13:33.110 align:start position:0% yeah yeah so<01:13:31.679> I<01:13:31.860> would<01:13:31.980> need<01:13:32.159> to<01:13:32.219> do<01:13:32.340> buffer<01:13:32.640> to<01:13:32.820> hex 01:13:33.110 --> 01:13:33.120 align:start position:0% yeah so I would need to do buffer to hex 01:13:33.120 --> 01:13:36.649 align:start position:0% yeah so I would need to do buffer to hex here<01:13:33.980> uh<01:13:34.980> well<01:13:35.280> since<01:13:35.520> I'm<01:13:35.699> now<01:13:35.880> running<01:13:36.060> on<01:13:36.420> a 01:13:36.649 --> 01:13:36.659 align:start position:0% here uh well since I'm now running on a 01:13:36.659 --> 01:13:38.689 align:start position:0% here uh well since I'm now running on a like<01:13:37.140> JS<01:13:37.560> thing<01:13:37.800> I<01:13:37.980> would<01:13:38.159> need<01:13:38.280> to<01:13:38.400> build<01:13:38.520> it 01:13:38.689 --> 01:13:38.699 align:start position:0% like JS thing I would need to build it 01:13:38.699 --> 01:13:40.669 align:start position:0% like JS thing I would need to build it before<01:13:38.880> I'm<01:13:39.120> able<01:13:39.360> to<01:13:39.480> run<01:13:39.600> this<01:13:39.840> so<01:13:40.440> I<01:13:40.560> will 01:13:40.669 --> 01:13:40.679 align:start position:0% before I'm able to run this so I will 01:13:40.679 --> 01:13:43.130 align:start position:0% before I'm able to run this so I will not<01:13:40.800> do<01:13:41.040> this<01:13:41.219> here<01:13:41.640> but<01:13:42.239> those<01:13:42.480> are<01:13:42.719> we<01:13:43.020> can 01:13:43.130 --> 01:13:43.140 align:start position:0% not do this here but those are we can 01:13:43.140 --> 01:13:44.990 align:start position:0% not do this here but those are we can trust<01:13:43.320> that<01:13:43.560> you<01:13:43.860> know<01:13:43.920> the<01:13:44.219> values<01:13:44.580> that<01:13:44.820> are 01:13:44.990 --> 01:13:45.000 align:start position:0% trust that you know the values that are 01:13:45.000 --> 01:13:46.970 align:start position:0% trust that you know the values that are output<01:13:45.600> here<01:13:45.840> if<01:13:46.080> you<01:13:46.199> were<01:13:46.320> to<01:13:46.440> convert<01:13:46.739> every 01:13:46.970 --> 01:13:46.980 align:start position:0% output here if you were to convert every 01:13:46.980 --> 01:13:49.550 align:start position:0% output here if you were to convert every one<01:13:47.159> of<01:13:47.280> them<01:13:47.400> in<01:13:47.760> you<01:13:48.060> know<01:13:48.120> in<01:13:48.780> HEX<01:13:49.080> would<01:13:49.440> be 01:13:49.550 --> 01:13:49.560 align:start position:0% one of them in you know in HEX would be 01:13:49.560 --> 01:13:53.090 align:start position:0% one of them in you know in HEX would be the<01:13:49.679> exact<01:13:49.920> values<01:13:50.280> of<01:13:50.460> the<01:13:50.699> the<01:13:51.179> root<01:13:51.480> of<01:13:51.600> d 01:13:53.090 --> 01:13:53.100 align:start position:0% the exact values of the the root of d 01:13:53.100 --> 01:13:56.209 align:start position:0% the exact values of the the root of d of<01:13:53.400> the<01:13:53.580> miracle<01:13:53.820> pursuitry<01:13:54.420> that<01:13:54.840> we<01:13:55.080> had 01:13:56.209 --> 01:13:56.219 align:start position:0% of the miracle pursuitry that we had 01:13:56.219 --> 01:14:01.310 align:start position:0% of the miracle pursuitry that we had in<01:13:57.000> uh<01:13:57.780> the<01:13:57.800> example<01:13:58.800> d 01:14:01.310 --> 01:14:01.320 align:start position:0% in uh the example d 01:14:01.320 --> 01:14:10.189 align:start position:0% in uh the example d like<01:14:01.980> get<01:14:02.460> 68<01:14:03.300> nothing<01:14:04.140> here 01:14:10.189 --> 01:14:10.199 align:start position:0% 01:14:10.199 --> 01:14:12.590 align:start position:0% is<01:14:10.679> that<01:14:10.800> a<01:14:10.980> satisfactory<01:14:11.520> answer<01:14:11.940> to<01:14:12.420> your 01:14:12.590 --> 01:14:12.600 align:start position:0% is that a satisfactory answer to your 01:14:12.600 --> 01:14:14.750 align:start position:0% is that a satisfactory answer to your question<01:14:12.780> are<01:14:13.199> you 01:14:14.750 --> 01:14:14.760 align:start position:0% question are you 01:14:14.760 --> 01:14:16.970 align:start position:0% question are you yeah 01:14:16.970 --> 01:14:16.980 align:start position:0% 01:14:16.980 --> 01:14:17.980 align:start position:0% yeah 01:14:17.980 --> 01:14:17.990 align:start position:0% yeah 01:14:17.990 --> 01:14:21.649 align:start position:0% yeah [Music] 01:14:21.649 --> 01:14:21.659 align:start position:0% 01:14:21.659 --> 01:14:24.410 align:start position:0% cool<01:14:22.500> any<01:14:23.219> other<01:14:23.460> questions<01:14:23.699> before<01:14:23.940> we<01:14:24.179> move 01:14:24.410 --> 01:14:24.420 align:start position:0% cool any other questions before we move 01:14:24.420 --> 01:14:26.570 align:start position:0% cool any other questions before we move on<01:14:24.600> to<01:14:24.719> going<01:14:24.900> to<01:14:25.140> all<01:14:25.440> uh<01:14:25.860> specific<01:14:26.159> kinds<01:14:26.460> of 01:14:26.570 --> 01:14:26.580 align:start position:0% on to going to all uh specific kinds of 01:14:26.580 --> 01:14:29.090 align:start position:0% on to going to all uh specific kinds of notes 01:14:29.090 --> 01:14:29.100 align:start position:0% 01:14:29.100 --> 01:14:31.490 align:start position:0% we're<01:14:29.460> good<01:14:29.699> all<01:14:30.600> right<01:14:30.780> cool<01:14:30.900> everybody's 01:14:31.490 --> 01:14:31.500 align:start position:0% we're good all right cool everybody's 01:14:31.500 --> 01:14:33.530 align:start position:0% we're good all right cool everybody's following<01:14:31.800> along 01:14:33.530 --> 01:14:33.540 align:start position:0% following along 01:14:33.540 --> 01:14:36.649 align:start position:0% following along all<01:14:34.140> right<01:14:34.320> nice<01:14:34.940> so<01:14:35.940> yeah<01:14:36.179> we're<01:14:36.360> just<01:14:36.480> going 01:14:36.649 --> 01:14:36.659 align:start position:0% all right nice so yeah we're just going 01:14:36.659 --> 01:14:38.990 align:start position:0% all right nice so yeah we're just going to start<01:14:36.900> with<01:14:37.260> creating<01:14:37.800> and<01:14:37.980> looking<01:14:38.219> up<01:14:38.520> uh 01:14:38.990 --> 01:14:39.000 align:start position:0% to start with creating and looking up uh 01:14:39.000 --> 01:14:40.130 align:start position:0% to start with creating and looking up uh null<01:14:39.239> node 01:14:40.130 --> 01:14:40.140 align:start position:0% null node 01:14:40.140 --> 01:14:42.169 align:start position:0% null node so<01:14:40.620> how<01:14:40.860> do<01:14:40.980> we<01:14:41.159> we're<01:14:41.460> not<01:14:41.640> actually<01:14:41.820> really 01:14:42.169 --> 01:14:42.179 align:start position:0% so how do we we're not actually really 01:14:42.179 --> 01:14:43.550 align:start position:0% so how do we we're not actually really going<01:14:42.360> to<01:14:42.540> create<01:14:42.600> a<01:14:42.840> null<01:14:43.020> node<01:14:43.260> we're<01:14:43.440> just 01:14:43.550 --> 01:14:43.560 align:start position:0% going to create a null node we're just 01:14:43.560 --> 01:14:45.830 align:start position:0% going to create a null node we're just going<01:14:43.679> to<01:14:43.800> query<01:14:44.100> for<01:14:44.580> a<01:14:44.820> key<01:14:45.000> that<01:14:45.540> is<01:14:45.659> not 01:14:45.830 --> 01:14:45.840 align:start position:0% going to query for a key that is not 01:14:45.840 --> 01:14:48.470 align:start position:0% going to query for a key that is not present<01:14:46.260> in<01:14:46.620> the<01:14:46.860> Merkel<01:14:47.580> particular<01:14:48.060> tree<01:14:48.179> so 01:14:48.470 --> 01:14:48.480 align:start position:0% present in the Merkel particular tree so 01:14:48.480 --> 01:14:50.270 align:start position:0% present in the Merkel particular tree so it's<01:14:48.600> basically<01:14:48.900> the<01:14:49.199> simplest<01:14:49.620> like<01:14:49.980> test 01:14:50.270 --> 01:14:50.280 align:start position:0% it's basically the simplest like test 01:14:50.280 --> 01:14:53.030 align:start position:0% it's basically the simplest like test case<01:14:50.520> you<01:14:50.880> could<01:14:51.300> imagine<01:14:51.679> so<01:14:52.679> what<01:14:52.920> we're 01:14:53.030 --> 01:14:53.040 align:start position:0% case you could imagine so what we're 01:14:53.040 --> 01:14:57.110 align:start position:0% case you could imagine so what we're going<01:14:53.219> to<01:14:53.280> run<01:14:53.400> is<01:14:53.840> to<01:14:54.840> to<01:14:55.260> a<01:14:55.560> right 01:14:57.110 --> 01:14:57.120 align:start position:0% going to run is to to a right 01:14:57.120 --> 01:15:06.110 align:start position:0% going to run is to to a right let's<01:14:57.600> look<01:14:57.780> just<01:14:58.080> at<01:14:58.320> the 01:15:06.110 --> 01:15:06.120 align:start position:0% 01:15:06.120 --> 01:15:08.630 align:start position:0% that's<01:15:06.600> here<01:15:06.960> yes<01:15:07.560> we're<01:15:07.860> instantiating<01:15:08.400> a 01:15:08.630 --> 01:15:08.640 align:start position:0% that's here yes we're instantiating a 01:15:08.640 --> 01:15:09.850 align:start position:0% that's here yes we're instantiating a new<01:15:08.760> tree 01:15:09.850 --> 01:15:09.860 align:start position:0% new tree 01:15:09.860 --> 01:15:13.130 align:start position:0% new tree we<01:15:10.860> are<01:15:11.040> trying<01:15:11.340> to<01:15:11.520> find<01:15:11.699> a<01:15:11.940> path<01:15:12.179> you<01:15:12.659> know<01:15:12.780> to 01:15:13.130 --> 01:15:13.140 align:start position:0% we are trying to find a path you know to 01:15:13.140 --> 01:15:14.990 align:start position:0% we are trying to find a path you know to the<01:15:13.440> uh 01:15:14.990 --> 01:15:15.000 align:start position:0% the uh 01:15:15.000 --> 01:15:18.410 align:start position:0% the uh to<01:15:15.480> the<01:15:15.659> key<01:15:15.780> test<01:15:16.199> key<01:15:16.440> and<01:15:17.280> we'll<01:15:17.460> see<01:15:17.699> what 01:15:18.410 --> 01:15:18.420 align:start position:0% to the key test key and we'll see what 01:15:18.420 --> 01:15:20.990 align:start position:0% to the key test key and we'll see what kind<01:15:18.540> of<01:15:18.659> node<01:15:18.840> we'll<01:15:18.960> get<01:15:19.140> back<01:15:19.260> now<01:15:19.860> what<01:15:20.520> you 01:15:20.990 --> 01:15:21.000 align:start position:0% kind of node we'll get back now what you 01:15:21.000 --> 01:15:23.209 align:start position:0% kind of node we'll get back now what you will<01:15:21.600> see<01:15:21.780> now<01:15:22.020> is<01:15:22.199> that<01:15:22.440> we're<01:15:22.800> using 01:15:23.209 --> 01:15:23.219 align:start position:0% will see now is that we're using 01:15:23.219 --> 01:15:25.490 align:start position:0% will see now is that we're using findpath<01:15:23.820> which<01:15:24.239> is<01:15:24.420> going<01:15:24.600> to<01:15:24.840> provide<01:15:25.320> us 01:15:25.490 --> 01:15:25.500 align:start position:0% findpath which is going to provide us 01:15:25.500 --> 01:15:27.890 align:start position:0% findpath which is going to provide us with<01:15:25.860> the<01:15:25.980> actual<01:15:26.400> node<01:15:26.699> and<01:15:27.300> then<01:15:27.540> all<01:15:27.780> the 01:15:27.890 --> 01:15:27.900 align:start position:0% with the actual node and then all the 01:15:27.900 --> 01:15:29.330 align:start position:0% with the actual node and then all the object<01:15:28.080> instead<01:15:28.380> of<01:15:28.500> just<01:15:28.620> providing<01:15:28.980> us<01:15:29.100> with 01:15:29.330 --> 01:15:29.340 align:start position:0% object instead of just providing us with 01:15:29.340 --> 01:15:31.669 align:start position:0% object instead of just providing us with the<01:15:29.520> value<01:15:29.699> so<01:15:30.480> if<01:15:30.719> you<01:15:30.960> want<01:15:31.080> to<01:15:31.199> query<01:15:31.440> the 01:15:31.669 --> 01:15:31.679 align:start position:0% the value so if you want to query the 01:15:31.679 --> 01:15:33.770 align:start position:0% the value so if you want to query the the<01:15:31.920> three<01:15:32.100> four<01:15:32.340> actual<01:15:32.699> values<01:15:33.060> just<01:15:33.360> do<01:15:33.540> get 01:15:33.770 --> 01:15:33.780 align:start position:0% the three four actual values just do get 01:15:33.780 --> 01:15:35.450 align:start position:0% the three four actual values just do get but<01:15:34.320> if<01:15:34.440> you<01:15:34.620> want<01:15:34.739> to<01:15:34.860> get<01:15:35.100> more<01:15:35.280> information 01:15:35.450 --> 01:15:35.460 align:start position:0% but if you want to get more information 01:15:35.460 --> 01:15:37.130 align:start position:0% but if you want to get more information as<01:15:35.820> to<01:15:36.000> you<01:15:36.120> know<01:15:36.239> what<01:15:36.360> the<01:15:36.540> path<01:15:36.719> is<01:15:36.840> and<01:15:37.020> what 01:15:37.130 --> 01:15:37.140 align:start position:0% as to you know what the path is and what 01:15:37.140 --> 01:15:38.870 align:start position:0% as to you know what the path is and what the<01:15:37.260> node<01:15:37.440> looks<01:15:37.739> like<01:15:37.860> you<01:15:38.100> would<01:15:38.219> just<01:15:38.400> do<01:15:38.580> a 01:15:38.870 --> 01:15:38.880 align:start position:0% the node looks like you would just do a 01:15:38.880 --> 01:15:40.610 align:start position:0% the node looks like you would just do a fine<01:15:39.179> path 01:15:40.610 --> 01:15:40.620 align:start position:0% fine path 01:15:40.620 --> 01:15:43.010 align:start position:0% fine path so<01:15:40.980> we're<01:15:41.100> running<01:15:41.340> example<01:15:42.300> eight<01:15:42.540> this 01:15:43.010 --> 01:15:43.020 align:start position:0% so we're running example eight this 01:15:43.020 --> 01:15:45.169 align:start position:0% so we're running example eight this provides<01:15:43.440> us<01:15:43.560> with<01:15:43.860> uh<01:15:44.100> yeah<01:15:44.280> a<01:15:44.520> null<01:15:44.699> node<01:15:45.000> as 01:15:45.169 --> 01:15:45.179 align:start position:0% provides us with uh yeah a null node as 01:15:45.179 --> 01:15:47.270 align:start position:0% provides us with uh yeah a null node as we<01:15:45.360> would<01:15:45.600> uh<01:15:45.960> expect<01:15:46.199> we<01:15:46.679> could<01:15:46.800> change<01:15:47.040> that 01:15:47.270 --> 01:15:47.280 align:start position:0% we would uh expect we could change that 01:15:47.280 --> 01:15:49.970 align:start position:0% we would uh expect we could change that to<01:15:47.580> uh<01:15:47.940> pretty<01:15:48.179> much<01:15:48.300> you<01:15:48.600> know<01:15:48.719> anything 01:15:49.970 --> 01:15:49.980 align:start position:0% to uh pretty much you know anything 01:15:49.980 --> 01:15:53.149 align:start position:0% to uh pretty much you know anything and<01:15:50.699> uh<01:15:51.420> we<01:15:51.960> would<01:15:52.020> get<01:15:52.199> back<01:15:52.320> now<01:15:52.500> as<01:15:52.739> well<01:15:52.920> no 01:15:53.149 --> 01:15:53.159 align:start position:0% and uh we would get back now as well no 01:15:53.159 --> 01:15:55.070 align:start position:0% and uh we would get back now as well no difference 01:15:55.070 --> 01:15:55.080 align:start position:0% difference 01:15:55.080 --> 01:15:57.169 align:start position:0% difference now<01:15:55.679> one<01:15:56.040> thing<01:15:56.159> I'm<01:15:56.340> going<01:15:56.520> to<01:15:56.640> try<01:15:56.820> actually 01:15:57.169 --> 01:15:57.179 align:start position:0% now one thing I'm going to try actually 01:15:57.179 --> 01:16:00.050 align:start position:0% now one thing I'm going to try actually is<01:15:57.540> if<01:15:57.719> I<01:15:57.960> query<01:15:58.400> buffer<01:15:59.400> from<01:15:59.580> that<01:15:59.760> I'm<01:15:59.940> not 01:16:00.050 --> 01:16:00.060 align:start position:0% is if I query buffer from that I'm not 01:16:00.060 --> 01:16:01.310 align:start position:0% is if I query buffer from that I'm not sure<01:16:00.179> if<01:16:00.300> that's<01:16:00.420> going<01:16:00.600> to<01:16:00.659> be<01:16:00.719> a<01:16:00.840> null<01:16:01.020> node 01:16:01.310 --> 01:16:01.320 align:start position:0% sure if that's going to be a null node 01:16:01.320 --> 01:16:03.290 align:start position:0% sure if that's going to be a null node as<01:16:01.440> well<01:16:01.560> yeah<01:16:02.340> okay<01:16:02.520> that's<01:16:02.760> another<01:16:02.940> note 01:16:03.290 --> 01:16:03.300 align:start position:0% as well yeah okay that's another note 01:16:03.300 --> 01:16:14.030 align:start position:0% as well yeah okay that's another note interesting 01:16:14.030 --> 01:16:14.040 align:start position:0% 01:16:14.040 --> 01:16:19.130 align:start position:0% oh<01:16:14.580> yeah<01:16:14.699> the<01:16:14.940> thing<01:16:15.120> we<01:16:15.360> were<01:16:15.679> using<01:16:16.679> before 01:16:19.130 --> 01:16:19.140 align:start position:0% 01:16:19.140 --> 01:16:21.229 align:start position:0% yeah<01:16:19.199> I<01:16:19.739> think<01:16:19.920> it's<01:16:20.219> still<01:16:20.460> null<01:16:20.760> it's<01:16:21.060> since 01:16:21.229 --> 01:16:21.239 align:start position:0% yeah I think it's still null it's since 01:16:21.239 --> 01:16:24.470 align:start position:0% yeah I think it's still null it's since it<01:16:21.659> it's<01:16:22.020> like<01:16:22.260> defined<01:16:22.860> as<01:16:23.340> you<01:16:24.179> know<01:16:24.300> the 01:16:24.470 --> 01:16:24.480 align:start position:0% it it's like defined as you know the 01:16:24.480 --> 01:16:26.330 align:start position:0% it it's like defined as you know the initial<01:16:25.080> hash<01:16:25.320> is<01:16:25.500> defined<01:16:25.860> as<01:16:25.980> that<01:16:26.159> but 01:16:26.330 --> 01:16:26.340 align:start position:0% initial hash is defined as that but 01:16:26.340 --> 01:16:28.790 align:start position:0% initial hash is defined as that but there's<01:16:26.460> no<01:16:26.699> actual<01:16:27.000> node<01:16:27.360> that's<01:16:27.600> present<01:16:28.020> uh 01:16:28.790 --> 01:16:28.800 align:start position:0% there's no actual node that's present uh 01:16:28.800 --> 01:16:30.410 align:start position:0% there's no actual node that's present uh and<01:16:28.980> that<01:16:29.159> key<01:16:29.340> from<01:16:29.699> what<01:16:29.820> I<01:16:30.000> can<01:16:30.060> recall<01:16:30.300> of 01:16:30.410 --> 01:16:30.420 align:start position:0% and that key from what I can recall of 01:16:30.420 --> 01:16:36.290 align:start position:0% and that key from what I can recall of the<01:16:30.600> specs<01:16:30.960> so<01:16:31.440> so<01:16:31.920> there 01:16:36.290 --> 01:16:36.300 align:start position:0% 01:16:36.300 --> 01:16:38.030 align:start position:0% yeah 01:16:38.030 --> 01:16:38.040 align:start position:0% yeah 01:16:38.040 --> 01:16:40.490 align:start position:0% yeah yeah<01:16:38.179> it's<01:16:39.179> basically<01:16:39.540> a<01:16:39.719> way<01:16:39.900> to<01:16:40.080> bootstrap 01:16:40.490 --> 01:16:40.500 align:start position:0% yeah it's basically a way to bootstrap 01:16:40.500 --> 01:16:42.290 align:start position:0% yeah it's basically a way to bootstrap the<01:16:40.679> tree<01:16:40.800> so<01:16:40.980> that<01:16:41.100> it<01:16:41.219> starts<01:16:41.520> you<01:16:41.820> know<01:16:41.880> with 01:16:42.290 --> 01:16:42.300 align:start position:0% the tree so that it starts you know with 01:16:42.300 --> 01:16:45.649 align:start position:0% the tree so that it starts you know with something<01:16:43.100> uh<01:16:44.100> you<01:16:44.340> could<01:16:44.400> Define<01:16:44.580> like<01:16:45.060> a<01:16:45.360> new 01:16:45.649 --> 01:16:45.659 align:start position:0% something uh you could Define like a new 01:16:45.659 --> 01:16:47.990 align:start position:0% something uh you could Define like a new Mercury<01:16:46.140> patriotary<01:16:47.040> data<01:16:47.400> structure<01:16:47.699> that 01:16:47.990 --> 01:16:48.000 align:start position:0% Mercury patriotary data structure that 01:16:48.000 --> 01:16:49.910 align:start position:0% Mercury patriotary data structure that uses<01:16:48.300> like<01:16:48.719> something<01:16:49.080> different<01:16:49.380> obviously 01:16:49.910 --> 01:16:49.920 align:start position:0% uses like something different obviously 01:16:49.920 --> 01:16:52.250 align:start position:0% uses like something different obviously from<01:16:50.100> rlp<01:16:50.580> encoding<01:16:51.060> and<01:16:51.600> also<01:16:51.900> has<01:16:52.080> a 01:16:52.250 --> 01:16:52.260 align:start position:0% from rlp encoding and also has a 01:16:52.260 --> 01:16:53.870 align:start position:0% from rlp encoding and also has a different<01:16:52.440> like<01:16:52.739> root<01:16:53.159> hash<01:16:53.400> you<01:16:53.760> don't 01:16:53.870 --> 01:16:53.880 align:start position:0% different like root hash you don't 01:16:53.880 --> 01:16:56.030 align:start position:0% different like root hash you don't necessarily<01:16:54.300> have<01:16:54.659> to<01:16:55.199> use<01:16:55.320> it<01:16:55.500> it's<01:16:55.679> useful 01:16:56.030 --> 01:16:56.040 align:start position:0% necessarily have to use it it's useful 01:16:56.040 --> 01:16:58.250 align:start position:0% necessarily have to use it it's useful in<01:16:56.280> the<01:16:56.400> context<01:16:56.640> of<01:16:56.880> ethereum<01:16:57.420> because<01:16:57.840> we 01:16:58.250 --> 01:16:58.260 align:start position:0% in the context of ethereum because we 01:16:58.260 --> 01:16:59.450 align:start position:0% in the context of ethereum because we obviously<01:16:58.679> want<01:16:58.860> to<01:16:58.980> be<01:16:59.100> consistent 01:16:59.450 --> 01:16:59.460 align:start position:0% obviously want to be consistent 01:16:59.460 --> 01:17:01.669 align:start position:0% obviously want to be consistent throughout<01:16:59.820> like<01:17:00.000> implementations<01:17:00.600> but<01:17:01.500> it's 01:17:01.669 --> 01:17:01.679 align:start position:0% throughout like implementations but it's 01:17:01.679 --> 01:17:03.350 align:start position:0% throughout like implementations but it's not<01:17:01.860> it's<01:17:02.159> not<01:17:02.280> a<01:17:02.460> necessary<01:17:02.820> part<01:17:03.060> of<01:17:03.239> the 01:17:03.350 --> 01:17:03.360 align:start position:0% not it's not a necessary part of the 01:17:03.360 --> 01:17:04.910 align:start position:0% not it's not a necessary part of the data<01:17:04.080> structure<01:17:04.320> like<01:17:04.500> that<01:17:04.620> you<01:17:04.800> could 01:17:04.910 --> 01:17:04.920 align:start position:0% data structure like that you could 01:17:04.920 --> 01:17:08.630 align:start position:0% data structure like that you could Define<01:17:05.040> It<01:17:05.340> Anyway<01:17:05.520> any<01:17:06.179> way<01:17:06.420> you<01:17:06.600> want 01:17:08.630 --> 01:17:08.640 align:start position:0% Define It Anyway any way you want 01:17:08.640 --> 01:17:11.270 align:start position:0% Define It Anyway any way you want so<01:17:09.540> yeah<01:17:09.900> the<01:17:10.140> null<01:17:10.260> node<01:17:10.560> is<01:17:10.679> a<01:17:10.800> bit<01:17:10.920> you<01:17:11.219> know 01:17:11.270 --> 01:17:11.280 align:start position:0% so yeah the null node is a bit you know 01:17:11.280 --> 01:17:13.250 align:start position:0% so yeah the null node is a bit you know boring<01:17:12.060> it's<01:17:12.239> not<01:17:12.360> as<01:17:12.540> interesting<01:17:12.900> and<01:17:13.080> the 01:17:13.250 --> 01:17:13.260 align:start position:0% boring it's not as interesting and the 01:17:13.260 --> 01:17:15.709 align:start position:0% boring it's not as interesting and the ones<01:17:13.500> that<01:17:13.860> are<01:17:14.159> to<01:17:14.340> come 01:17:15.709 --> 01:17:15.719 align:start position:0% ones that are to come 01:17:15.719 --> 01:17:18.410 align:start position:0% ones that are to come uh<01:17:16.679> it's<01:17:16.920> also<01:17:17.400> like<01:17:17.699> slightly<01:17:18.120> more 01:17:18.410 --> 01:17:18.420 align:start position:0% uh it's also like slightly more 01:17:18.420 --> 01:17:20.810 align:start position:0% uh it's also like slightly more complicated<01:17:18.900> to<01:17:19.320> to<01:17:19.500> create<01:17:19.739> because<01:17:20.159> if<01:17:20.699> you 01:17:20.810 --> 01:17:20.820 align:start position:0% complicated to to create because if you 01:17:20.820 --> 01:17:22.910 align:start position:0% complicated to to create because if you think<01:17:21.000> about<01:17:21.179> how<01:17:21.659> you<01:17:22.140> know<01:17:22.260> these<01:17:22.679> kind<01:17:22.800> of 01:17:22.910 --> 01:17:22.920 align:start position:0% think about how you know these kind of 01:17:22.920 --> 01:17:26.030 align:start position:0% think about how you know these kind of keys<01:17:23.159> work<01:17:23.340> right<01:17:23.640> you<01:17:24.480> have<01:17:24.840> a<01:17:25.020> key<01:17:25.140> and<01:17:25.920> to 01:17:26.030 --> 01:17:26.040 align:start position:0% keys work right you have a key and to 01:17:26.040 --> 01:17:28.610 align:start position:0% keys work right you have a key and to retrieve<01:17:26.460> the<01:17:26.640> value<01:17:26.820> for<01:17:27.179> it<01:17:27.360> you<01:17:28.020> just<01:17:28.199> go 01:17:28.610 --> 01:17:28.620 align:start position:0% retrieve the value for it you just go 01:17:28.620 --> 01:17:32.510 align:start position:0% retrieve the value for it you just go down<01:17:28.980> each<01:17:29.640> note<01:17:29.880> is<01:17:30.360> a<01:17:30.900> hex<01:17:31.500> value<01:17:31.679> right<01:17:32.159> so 01:17:32.510 --> 01:17:32.520 align:start position:0% down each note is a hex value right so 01:17:32.520 --> 01:17:33.950 align:start position:0% down each note is a hex value right so let's<01:17:32.640> say<01:17:32.820> the<01:17:33.060> next<01:17:33.179> part<01:17:33.360> of<01:17:33.480> the<01:17:33.600> key<01:17:33.719> is 01:17:33.950 --> 01:17:33.960 align:start position:0% let's say the next part of the key is 01:17:33.960 --> 01:17:36.470 align:start position:0% let's say the next part of the key is like<01:17:34.140> seven<01:17:34.440> you<01:17:35.280> go<01:17:35.580> branch<01:17:36.060> number<01:17:36.239> seven 01:17:36.470 --> 01:17:36.480 align:start position:0% like seven you go branch number seven 01:17:36.480 --> 01:17:38.689 align:start position:0% like seven you go branch number seven and<01:17:37.020> then<01:17:37.140> if<01:17:37.320> it's<01:17:37.560> uh<01:17:37.800> you<01:17:37.980> know<01:17:38.159> four<01:17:38.340> like 01:17:38.689 --> 01:17:38.699 align:start position:0% and then if it's uh you know four like 01:17:38.699 --> 01:17:40.370 align:start position:0% and then if it's uh you know four like in<01:17:38.820> this<01:17:39.000> example<01:17:39.300> you<01:17:39.780> take<01:17:39.960> branch<01:17:40.199> number 01:17:40.370 --> 01:17:40.380 align:start position:0% in this example you take branch number 01:17:40.380 --> 01:17:43.189 align:start position:0% in this example you take branch number four<01:17:40.620> and<01:17:41.040> you<01:17:41.159> go<01:17:41.340> all<01:17:41.520> the<01:17:41.580> way<01:17:41.640> down<01:17:42.300> now 01:17:43.189 --> 01:17:43.199 align:start position:0% four and you go all the way down now 01:17:43.199 --> 01:17:46.189 align:start position:0% four and you go all the way down now since<01:17:43.800> like<01:17:44.280> murder<01:17:44.580> trees<01:17:45.480> are<01:17:45.719> like 01:17:46.189 --> 01:17:46.199 align:start position:0% since like murder trees are like 01:17:46.199 --> 01:17:48.350 align:start position:0% since like murder trees are like optimized<01:17:46.800> with<01:17:46.980> extension<01:17:47.400> nodes 01:17:48.350 --> 01:17:48.360 align:start position:0% optimized with extension nodes 01:17:48.360 --> 01:17:51.050 align:start position:0% optimized with extension nodes uh<01:17:48.960> you<01:17:49.140> wouldn't<01:17:49.260> get<01:17:49.560> a<01:17:49.920> branch<01:17:50.340> every<01:17:50.820> part 01:17:51.050 --> 01:17:51.060 align:start position:0% uh you wouldn't get a branch every part 01:17:51.060 --> 01:17:52.729 align:start position:0% uh you wouldn't get a branch every part of<01:17:51.179> the<01:17:51.300> way<01:17:51.420> down<01:17:51.600> what<01:17:51.900> you<01:17:52.020> would<01:17:52.199> see<01:17:52.380> is 01:17:52.729 --> 01:17:52.739 align:start position:0% of the way down what you would see is 01:17:52.739 --> 01:17:54.169 align:start position:0% of the way down what you would see is you<01:17:52.920> would<01:17:53.040> start<01:17:53.219> at<01:17:53.400> seven<01:17:53.520> let's<01:17:53.940> say<01:17:54.060> you 01:17:54.169 --> 01:17:54.179 align:start position:0% you would start at seven let's say you 01:17:54.179 --> 01:17:55.790 align:start position:0% you would start at seven let's say you only<01:17:54.239> had<01:17:54.480> like<01:17:54.600> one<01:17:54.780> of<01:17:54.900> the<01:17:54.960> keys<01:17:55.199> it<01:17:55.620> would 01:17:55.790 --> 01:17:55.800 align:start position:0% only had like one of the keys it would 01:17:55.800 --> 01:17:56.930 align:start position:0% only had like one of the keys it would start<01:17:55.920> at<01:17:56.100> seven<01:17:56.219> it<01:17:56.520> would<01:17:56.640> give<01:17:56.820> you 01:17:56.930 --> 01:17:56.940 align:start position:0% start at seven it would give you 01:17:56.940 --> 01:17:58.790 align:start position:0% start at seven it would give you straight<01:17:57.179> it<01:17:57.900> would<01:17:58.020> go<01:17:58.199> you<01:17:58.320> straight<01:17:58.560> to<01:17:58.679> the 01:17:58.790 --> 01:17:58.800 align:start position:0% straight it would go you straight to the 01:17:58.800 --> 01:18:00.470 align:start position:0% straight it would go you straight to the end<01:17:58.920> because<01:17:59.159> there's<01:17:59.460> only<01:17:59.640> one<01:17:59.940> value<01:18:00.179> that 01:18:00.470 --> 01:18:00.480 align:start position:0% end because there's only one value that 01:18:00.480 --> 01:18:02.570 align:start position:0% end because there's only one value that starts<01:18:00.719> with<01:18:00.840> seven<01:18:01.020> so<01:18:01.320> it<01:18:01.440> would<01:18:01.620> like<01:18:02.040> kind 01:18:02.570 --> 01:18:02.580 align:start position:0% starts with seven so it would like kind 01:18:02.580 --> 01:18:05.330 align:start position:0% starts with seven so it would like kind of<01:18:02.699> compress<01:18:02.940> the<01:18:03.120> tree<01:18:03.300> for<01:18:03.540> you<01:18:03.679> uh<01:18:04.679> so<01:18:04.920> if<01:18:05.100> we 01:18:05.330 --> 01:18:05.340 align:start position:0% of compress the tree for you uh so if we 01:18:05.340 --> 01:18:07.610 align:start position:0% of compress the tree for you uh so if we want<01:18:05.580> to<01:18:05.820> create<01:18:06.060> a<01:18:06.480> branch<01:18:06.780> node<01:18:07.080> that's<01:18:07.380> like 01:18:07.610 --> 01:18:07.620 align:start position:0% want to create a branch node that's like 01:18:07.620 --> 01:18:10.010 align:start position:0% want to create a branch node that's like acts<01:18:08.040> as<01:18:08.100> an<01:18:08.340> intermediary<01:18:08.940> node<01:18:09.239> you<01:18:09.900> would 01:18:10.010 --> 01:18:10.020 align:start position:0% acts as an intermediary node you would 01:18:10.020 --> 01:18:12.110 align:start position:0% acts as an intermediary node you would wanna<01:18:10.440> you<01:18:11.100> know<01:18:11.159> we<01:18:11.280> want<01:18:11.400> to<01:18:11.520> store<01:18:11.699> keys 01:18:12.110 --> 01:18:12.120 align:start position:0% wanna you know we want to store keys 01:18:12.120 --> 01:18:14.750 align:start position:0% wanna you know we want to store keys that<01:18:12.420> are<01:18:12.659> all<01:18:12.780> basically<01:18:13.260> in<01:18:13.500> the<01:18:13.620> same<01:18:13.739> spot 01:18:14.750 --> 01:18:14.760 align:start position:0% that are all basically in the same spot 01:18:14.760 --> 01:18:17.330 align:start position:0% that are all basically in the same spot and<01:18:15.360> then<01:18:15.480> Branch<01:18:15.840> out<01:18:16.020> at<01:18:16.199> some<01:18:16.320> point<01:18:16.920> and 01:18:17.330 --> 01:18:17.340 align:start position:0% and then Branch out at some point and 01:18:17.340 --> 01:18:19.130 align:start position:0% and then Branch out at some point and that's<01:18:17.520> actually<01:18:17.820> interesting<01:18:18.480> because<01:18:18.719> it's 01:18:19.130 --> 01:18:19.140 align:start position:0% that's actually interesting because it's 01:18:19.140 --> 01:18:21.290 align:start position:0% that's actually interesting because it's super<01:18:19.320> easy<01:18:19.560> to<01:18:19.800> do<01:18:19.920> that<01:18:20.100> you<01:18:20.460> know<01:18:20.580> with<01:18:20.880> what 01:18:21.290 --> 01:18:21.300 align:start position:0% super easy to do that you know with what 01:18:21.300 --> 01:18:23.450 align:start position:0% super easy to do that you know with what we're<01:18:21.600> going<01:18:21.780> to<01:18:21.840> do<01:18:21.960> in<01:18:22.080> this<01:18:22.199> example<01:18:22.560> but<01:18:23.219> if 01:18:23.450 --> 01:18:23.460 align:start position:0% we're going to do in this example but if 01:18:23.460 --> 01:18:25.610 align:start position:0% we're going to do in this example but if we<01:18:23.640> were<01:18:23.820> using<01:18:24.120> a<01:18:24.300> hash<01:18:24.480> tree<01:18:24.719> then<01:18:25.380> it's 01:18:25.610 --> 01:18:25.620 align:start position:0% we were using a hash tree then it's 01:18:25.620 --> 01:18:27.709 align:start position:0% we were using a hash tree then it's basically<01:18:26.040> you<01:18:26.460> know<01:18:26.580> impossible<01:18:27.000> to<01:18:27.420> do<01:18:27.540> that 01:18:27.709 --> 01:18:27.719 align:start position:0% basically you know impossible to do that 01:18:27.719 --> 01:18:29.570 align:start position:0% basically you know impossible to do that do<01:18:28.020> that<01:18:28.140> voluntarily<01:18:28.679> and<01:18:29.040> that<01:18:29.159> gives<01:18:29.280> you<01:18:29.460> a 01:18:29.570 --> 01:18:29.580 align:start position:0% do that voluntarily and that gives you a 01:18:29.580 --> 01:18:31.610 align:start position:0% do that voluntarily and that gives you a sense<01:18:29.699> of<01:18:29.880> why<01:18:30.179> that<01:18:30.540> was<01:18:30.659> chosen<01:18:31.140> in<01:18:31.500> the 01:18:31.610 --> 01:18:31.620 align:start position:0% sense of why that was chosen in the 01:18:31.620 --> 01:18:34.189 align:start position:0% sense of why that was chosen in the first<01:18:31.739> place<01:18:31.920> right<01:18:32.219> why<01:18:32.940> we're<01:18:33.120> choosing<01:18:33.659> uh 01:18:34.189 --> 01:18:34.199 align:start position:0% first place right why we're choosing uh 01:18:34.199 --> 01:18:35.930 align:start position:0% first place right why we're choosing uh to<01:18:34.320> Hash<01:18:34.560> keys<01:18:34.860> in<01:18:34.980> the<01:18:35.100> context<01:18:35.280> like<01:18:35.640> a 01:18:35.930 --> 01:18:35.940 align:start position:0% to Hash keys in the context like a 01:18:35.940 --> 01:18:38.209 align:start position:0% to Hash keys in the context like a production<01:18:36.360> you<01:18:37.140> know<01:18:37.140> database<01:18:37.679> in<01:18:37.800> ethereum 01:18:38.209 --> 01:18:38.219 align:start position:0% production you know database in ethereum 01:18:38.219 --> 01:18:40.910 align:start position:0% production you know database in ethereum to<01:18:38.460> prevent<01:18:38.760> like<01:18:38.940> dos<01:18:39.540> style<01:18:40.020> attacks<01:18:40.560> with 01:18:40.910 --> 01:18:40.920 align:start position:0% to prevent like dos style attacks with 01:18:40.920 --> 01:18:43.130 align:start position:0% to prevent like dos style attacks with uh<01:18:41.219> you<01:18:41.640> know<01:18:41.760> just<01:18:42.060> putting<01:18:42.659> keys<01:18:42.900> are<01:18:43.020> always 01:18:43.130 --> 01:18:43.140 align:start position:0% uh you know just putting keys are always 01:18:43.140 --> 01:18:47.450 align:start position:0% uh you know just putting keys are always in<01:18:43.440> the<01:18:43.560> same<01:18:43.679> spot 01:18:47.450 --> 01:18:47.460 align:start position:0% 01:18:47.460 --> 01:18:49.669 align:start position:0% all<01:18:48.000> right<01:18:48.179> so<01:18:48.600> let's<01:18:48.719> look<01:18:48.960> at<01:18:49.140> that<01:18:49.380> actual 01:18:49.669 --> 01:18:49.679 align:start position:0% all right so let's look at that actual 01:18:49.679 --> 01:18:53.390 align:start position:0% all right so let's look at that actual example<01:18:50.340> example<01:18:51.179> 2B 01:18:53.390 --> 01:18:53.400 align:start position:0% example example 2B 01:18:53.400 --> 01:18:59.330 align:start position:0% example example 2B foreign 01:18:59.330 --> 01:18:59.340 align:start position:0% 01:18:59.340 --> 01:19:06.649 align:start position:0% yeah<01:19:00.000> I'm<01:19:00.179> not<01:19:00.360> saving<01:19:00.840> any<01:19:01.080> of<01:19:01.260> that 01:19:06.649 --> 01:19:06.659 align:start position:0% 01:19:06.659 --> 01:19:20.510 align:start position:0% is 01:19:20.510 --> 01:19:20.520 align:start position:0% 01:19:20.520 --> 01:19:22.910 align:start position:0% what<01:19:20.580> it<01:19:21.239> is<01:19:21.480> that<01:19:21.659> like<01:19:21.960> native<01:19:22.260> format<01:19:22.679> that 01:19:22.910 --> 01:19:22.920 align:start position:0% what it is that like native format that 01:19:22.920 --> 01:19:25.189 align:start position:0% what it is that like native format that this<01:19:23.159> tree<01:19:23.400> accepts<01:19:23.940> like<01:19:24.480> you<01:19:24.600> could<01:19:24.780> do<01:19:24.960> it 01:19:25.189 --> 01:19:25.199 align:start position:0% this tree accepts like you could do it 01:19:25.199 --> 01:19:26.990 align:start position:0% this tree accepts like you could do it like<01:19:25.920> we<01:19:26.100> could<01:19:26.219> have<01:19:26.400> an<01:19:26.520> implementation 01:19:26.990 --> 01:19:27.000 align:start position:0% like we could have an implementation 01:19:27.000 --> 01:19:28.490 align:start position:0% like we could have an implementation that<01:19:27.239> just<01:19:27.480> basically<01:19:27.719> allows<01:19:28.080> you<01:19:28.140> to<01:19:28.260> input 01:19:28.490 --> 01:19:28.500 align:start position:0% that just basically allows you to input 01:19:28.500 --> 01:19:30.050 align:start position:0% that just basically allows you to input anything<01:19:28.679> but<01:19:29.040> it<01:19:29.159> would<01:19:29.280> still<01:19:29.460> be<01:19:29.640> converted 01:19:30.050 --> 01:19:30.060 align:start position:0% anything but it would still be converted 01:19:30.060 --> 01:19:31.370 align:start position:0% anything but it would still be converted into<01:19:30.179> something<01:19:30.540> that's<01:19:30.900> natively 01:19:31.370 --> 01:19:31.380 align:start position:0% into something that's natively 01:19:31.380 --> 01:19:33.709 align:start position:0% into something that's natively adjustable<01:19:31.980> by<01:19:32.340> the<01:19:32.460> tree<01:19:32.640> so<01:19:33.239> the<01:19:33.360> tree<01:19:33.540> is 01:19:33.709 --> 01:19:33.719 align:start position:0% adjustable by the tree so the tree is 01:19:33.719 --> 01:19:35.870 align:start position:0% adjustable by the tree so the tree is defined<01:19:34.020> as<01:19:34.140> a<01:19:34.320> like<01:19:34.560> hexary<01:19:35.040> hexiratory 01:19:35.870 --> 01:19:35.880 align:start position:0% defined as a like hexary hexiratory 01:19:35.880 --> 01:19:38.390 align:start position:0% defined as a like hexary hexiratory meaning<01:19:36.480> that<01:19:36.840> every<01:19:37.320> key<01:19:37.679> must<01:19:38.040> be<01:19:38.219> like 01:19:38.390 --> 01:19:38.400 align:start position:0% meaning that every key must be like 01:19:38.400 --> 01:19:40.910 align:start position:0% meaning that every key must be like hexadecimal<01:19:39.239> for<01:19:39.719> it<01:19:39.900> to<01:19:40.080> be<01:19:40.199> like<01:19:40.500> conformed 01:19:40.910 --> 01:19:40.920 align:start position:0% hexadecimal for it to be like conformed 01:19:40.920 --> 01:19:42.770 align:start position:0% hexadecimal for it to be like conformed to<01:19:41.040> the<01:19:41.159> data<01:19:41.460> structure<01:19:41.820> if<01:19:42.300> we<01:19:42.480> didn't<01:19:42.600> have 01:19:42.770 --> 01:19:42.780 align:start position:0% to the data structure if we didn't have 01:19:42.780 --> 01:19:44.990 align:start position:0% to the data structure if we didn't have small<01:19:43.560> values<01:19:43.920> we'd<01:19:44.219> have<01:19:44.340> to<01:19:44.460> convert<01:19:44.940> it 01:19:44.990 --> 01:19:45.000 align:start position:0% small values we'd have to convert it 01:19:45.000 --> 01:19:48.229 align:start position:0% small values we'd have to convert it anyways<01:19:45.540> so<01:19:45.780> that<01:19:46.020> I<01:19:46.320> mean<01:19:46.640> so<01:19:47.640> that<01:19:47.820> it<01:19:47.940> maps 01:19:48.229 --> 01:19:48.239 align:start position:0% anyways so that I mean so that it maps 01:19:48.239 --> 01:19:54.050 align:start position:0% anyways so that I mean so that it maps to<01:19:48.360> like<01:19:48.600> a<01:19:48.780> 16<01:19:49.020> uh<01:19:49.860> 16<01:19:50.400> width<01:19:51.360> key 01:19:54.050 --> 01:19:54.060 align:start position:0% to like a 16 uh 16 width key 01:19:54.060 --> 01:19:59.209 align:start position:0% to like a 16 uh 16 width key so<01:19:54.960> yeah 01:19:59.209 --> 01:19:59.219 align:start position:0% 01:19:59.219 --> 01:20:02.630 align:start position:0% yeah<01:19:59.659> absolutely<01:20:00.659> yeah 01:20:02.630 --> 01:20:02.640 align:start position:0% yeah absolutely yeah 01:20:02.640 --> 01:20:04.790 align:start position:0% yeah absolutely yeah so<01:20:03.120> and<01:20:03.239> also<01:20:03.540> like<01:20:03.659> rlp<01:20:04.080> encoding<01:20:04.500> encodes 01:20:04.790 --> 01:20:04.800 align:start position:0% so and also like rlp encoding encodes 01:20:04.800 --> 01:20:07.070 align:start position:0% so and also like rlp encoding encodes things<01:20:05.159> in<01:20:05.400> Exodus<01:20:06.000> mode<01:20:06.179> so<01:20:06.420> we're<01:20:06.659> all<01:20:06.840> like 01:20:07.070 --> 01:20:07.080 align:start position:0% things in Exodus mode so we're all like 01:20:07.080 --> 01:20:09.350 align:start position:0% things in Exodus mode so we're all like working<01:20:07.320> with<01:20:07.679> Native<01:20:08.040> like<01:20:08.400> hexadecimals 01:20:09.350 --> 01:20:09.360 align:start position:0% working with Native like hexadecimals 01:20:09.360 --> 01:20:12.110 align:start position:0% working with Native like hexadecimals here<01:20:09.600> it<01:20:10.140> was<01:20:10.320> in<01:20:10.500> that<01:20:10.620> tree 01:20:12.110 --> 01:20:12.120 align:start position:0% here it was in that tree 01:20:12.120 --> 01:20:16.189 align:start position:0% here it was in that tree uh<01:20:13.020> so<01:20:13.560> yeah<01:20:13.679> if<01:20:13.980> we 01:20:16.189 --> 01:20:16.199 align:start position:0% uh so yeah if we 01:20:16.199 --> 01:20:19.070 align:start position:0% uh so yeah if we like<01:20:16.500> unlike<01:20:16.920> like<01:20:16.920> hashes<01:20:17.760> uh<01:20:18.239> buffer<01:20:18.840> is 01:20:19.070 --> 01:20:19.080 align:start position:0% like unlike like hashes uh buffer is 01:20:19.080 --> 01:20:20.510 align:start position:0% like unlike like hashes uh buffer is going<01:20:19.380> to<01:20:19.500> be<01:20:19.560> it's<01:20:19.739> just<01:20:19.920> like<01:20:20.159> the<01:20:20.340> the 01:20:20.510 --> 01:20:20.520 align:start position:0% going to be it's just like the the 01:20:20.520 --> 01:20:23.270 align:start position:0% going to be it's just like the the hexary<01:20:21.360> like<01:20:21.719> encoding<01:20:22.260> of<01:20:22.380> the<01:20:22.560> these<01:20:22.980> keys 01:20:23.270 --> 01:20:23.280 align:start position:0% hexary like encoding of the these keys 01:20:23.280 --> 01:20:26.149 align:start position:0% hexary like encoding of the these keys so<01:20:23.699> we<01:20:23.820> should<01:20:24.000> expect<01:20:24.179> these<01:20:24.780> uh 01:20:26.149 --> 01:20:26.159 align:start position:0% so we should expect these uh 01:20:26.159 --> 01:20:28.970 align:start position:0% so we should expect these uh all<01:20:26.940> these<01:20:27.300> values<01:20:28.080> do<01:20:28.320> still<01:20:28.560> be<01:20:28.739> quite 01:20:28.970 --> 01:20:28.980 align:start position:0% all these values do still be quite 01:20:28.980 --> 01:20:31.070 align:start position:0% all these values do still be quite similar<01:20:29.280> and<01:20:29.580> that<01:20:29.699> is<01:20:29.820> what<01:20:30.060> we<01:20:30.239> see<01:20:30.360> here<01:20:30.659> so 01:20:31.070 --> 01:20:31.080 align:start position:0% similar and that is what we see here so 01:20:31.080 --> 01:20:33.709 align:start position:0% similar and that is what we see here so right<01:20:31.320> we<01:20:31.560> have<01:20:32.219> the<01:20:32.699> prefect<01:20:33.060> test<01:20:33.239> Keys<01:20:33.540> come 01:20:33.709 --> 01:20:33.719 align:start position:0% right we have the prefect test Keys come 01:20:33.719 --> 01:20:35.990 align:start position:0% right we have the prefect test Keys come in<01:20:33.840> for<01:20:33.960> all<01:20:34.080> of<01:20:34.199> them<01:20:34.320> and<01:20:35.040> test<01:20:35.280> key<01:20:35.580> is 01:20:35.990 --> 01:20:36.000 align:start position:0% in for all of them and test key is 01:20:36.000 --> 01:20:38.030 align:start position:0% in for all of them and test key is basically<01:20:36.239> that<01:20:36.540> part<01:20:36.780> you<01:20:37.260> know<01:20:37.380> of<01:20:37.620> the<01:20:37.860> uh 01:20:38.030 --> 01:20:38.040 align:start position:0% basically that part you know of the uh 01:20:38.040 --> 01:20:40.850 align:start position:0% basically that part you know of the uh let<01:20:38.820> me<01:20:38.880> zoom<01:20:39.179> in<01:20:39.300> a<01:20:39.540> little<01:20:39.659> bit<01:20:39.840> yeah<01:20:40.440> that 01:20:40.850 --> 01:20:40.860 align:start position:0% let me zoom in a little bit yeah that 01:20:40.860 --> 01:20:43.970 align:start position:0% let me zoom in a little bit yeah that part<01:20:41.040> of<01:20:41.219> the<01:20:41.340> of<01:20:41.880> the<01:20:42.060> buffer<01:20:42.900> now<01:20:43.320> we<01:20:43.500> have<01:20:43.620> 30 01:20:43.970 --> 01:20:43.980 align:start position:0% part of the of the buffer now we have 30 01:20:43.980 --> 01:20:47.030 align:start position:0% part of the of the buffer now we have 30 which<01:20:44.820> is<01:20:44.940> a<01:20:45.179> 0<01:20:45.480> and<01:20:45.780> 41<01:20:46.140> which<01:20:46.320> is<01:20:46.440> capital<01:20:46.620> A 01:20:47.030 --> 01:20:47.040 align:start position:0% which is a 0 and 41 which is capital A 01:20:47.040 --> 01:20:49.729 align:start position:0% which is a 0 and 41 which is capital A which<01:20:47.580> are<01:20:47.760> you<01:20:48.060> know<01:20:48.239> the<01:20:48.780> the<01:20:49.020> last<01:20:49.260> parts<01:20:49.500> of 01:20:49.729 --> 01:20:49.739 align:start position:0% which are you know the the last parts of 01:20:49.739 --> 01:20:51.530 align:start position:0% which are you know the the last parts of it<01:20:49.920> so<01:20:50.340> what<01:20:50.520> we<01:20:50.699> should<01:20:50.940> basically<01:20:51.300> expect 01:20:51.530 --> 01:20:51.540 align:start position:0% it so what we should basically expect 01:20:51.540 --> 01:20:53.630 align:start position:0% it so what we should basically expect right<01:20:51.960> is<01:20:52.440> uh 01:20:53.630 --> 01:20:53.640 align:start position:0% right is uh 01:20:53.640 --> 01:20:55.010 align:start position:0% right is uh would<01:20:54.179> you<01:20:54.300> agree<01:20:54.420> that<01:20:54.600> we<01:20:54.719> should<01:20:54.900> expect 01:20:55.010 --> 01:20:55.020 align:start position:0% would you agree that we should expect 01:20:55.020 --> 01:20:57.830 align:start position:0% would you agree that we should expect like<01:20:55.320> a<01:20:55.440> branch<01:20:55.679> node<01:20:55.980> at<01:20:56.219> 79<01:20:56.699> at<01:20:57.420> which<01:20:57.659> point 01:20:57.830 --> 01:20:57.840 align:start position:0% like a branch node at 79 at which point 01:20:57.840 --> 01:20:59.689 align:start position:0% like a branch node at 79 at which point you<01:20:58.080> know<01:20:58.140> it<01:20:58.320> branches<01:20:58.679> out<01:20:58.860> so<01:20:59.340> what<01:20:59.520> we 01:20:59.689 --> 01:20:59.699 align:start position:0% you know it branches out so what we 01:20:59.699 --> 01:21:00.709 align:start position:0% you know it branches out so what we would<01:20:59.820> see<01:20:59.940> is<01:21:00.060> like<01:21:00.179> there's<01:21:00.300> going<01:21:00.480> to<01:21:00.540> be<01:21:00.600> a 01:21:00.709 --> 01:21:00.719 align:start position:0% would see is like there's going to be a 01:21:00.719 --> 01:21:02.930 align:start position:0% would see is like there's going to be a value<01:21:00.840> at<01:21:01.080> 79<01:21:01.500> a<01:21:01.800> branch<01:21:02.100> that<01:21:02.340> you<01:21:02.760> know<01:21:02.820> can 01:21:02.930 --> 01:21:02.940 align:start position:0% value at 79 a branch that you know can 01:21:02.940 --> 01:21:04.669 align:start position:0% value at 79 a branch that you know can have<01:21:03.120> a<01:21:03.300> value<01:21:03.420> but<01:21:04.140> then<01:21:04.260> there's<01:21:04.440> going<01:21:04.679> to 01:21:04.669 --> 01:21:04.679 align:start position:0% have a value but then there's going to 01:21:04.679 --> 01:21:06.290 align:start position:0% have a value but then there's going to be<01:21:04.800> two<01:21:04.980> bats<01:21:05.400> there's<01:21:05.699> going<01:21:05.880> to<01:21:05.940> be<01:21:06.060> path 01:21:06.290 --> 01:21:06.300 align:start position:0% be two bats there's going to be path 01:21:06.300 --> 01:21:08.270 align:start position:0% be two bats there's going to be path number<01:21:06.480> three<01:21:06.719> and<01:21:07.199> path<01:21:07.500> number<01:21:07.620> four<01:21:07.860> like 01:21:08.270 --> 01:21:08.280 align:start position:0% number three and path number four like 01:21:08.280 --> 01:21:10.550 align:start position:0% number three and path number four like in<01:21:08.520> indexes<01:21:09.120> of<01:21:09.239> the<01:21:09.600> array<01:21:09.900> then<01:21:10.260> it's<01:21:10.440> going 01:21:10.550 --> 01:21:10.560 align:start position:0% in indexes of the array then it's going 01:21:10.560 --> 01:21:13.189 align:start position:0% in indexes of the array then it's going to<01:21:10.679> go<01:21:10.800> down<01:21:10.980> all<01:21:11.699> the<01:21:11.880> way<01:21:11.880> to<01:21:12.239> you<01:21:12.900> know<01:21:12.960> a 01:21:13.189 --> 01:21:13.199 align:start position:0% to go down all the way to you know a 01:21:13.199 --> 01:21:14.990 align:start position:0% to go down all the way to you know a leaf<01:21:13.500> node<01:21:13.739> because<01:21:13.980> it's<01:21:14.340> basically<01:21:14.699> the<01:21:14.880> end 01:21:14.990 --> 01:21:15.000 align:start position:0% leaf node because it's basically the end 01:21:15.000 --> 01:21:16.550 align:start position:0% leaf node because it's basically the end of<01:21:15.120> the<01:21:15.239> path<01:21:15.360> for<01:21:15.600> that<01:21:16.020> part<01:21:16.140> of<01:21:16.320> the<01:21:16.440> path 01:21:16.550 --> 01:21:16.560 align:start position:0% of the path for that part of the path 01:21:16.560 --> 01:21:18.770 align:start position:0% of the path for that part of the path and<01:21:17.400> then<01:21:17.460> 41<01:21:17.940> which<01:21:18.179> is<01:21:18.300> going<01:21:18.480> to<01:21:18.540> be<01:21:18.600> the 01:21:18.770 --> 01:21:18.780 align:start position:0% and then 41 which is going to be the 01:21:18.780 --> 01:21:20.570 align:start position:0% and then 41 which is going to be the another<01:21:19.260> part<01:21:19.560> for<01:21:19.800> that<01:21:19.980> you<01:21:20.340> know<01:21:20.460> other 01:21:20.570 --> 01:21:20.580 align:start position:0% another part for that you know other 01:21:20.580 --> 01:21:31.310 align:start position:0% another part for that you know other path<01:21:20.940> does<01:21:21.600> that<01:21:21.900> make<01:21:22.560> sense<01:21:22.800> to<01:21:23.460> everybody 01:21:31.310 --> 01:21:31.320 align:start position:0% 01:21:31.320 --> 01:21:43.130 align:start position:0% Aviation 01:21:43.130 --> 01:21:43.140 align:start position:0% 01:21:43.140 --> 01:21:46.130 align:start position:0% yeah<01:21:43.800> yeah<01:21:43.940> that's<01:21:44.940> uh<01:21:45.360> that's<01:21:45.840> really<01:21:46.020> the 01:21:46.130 --> 01:21:46.140 align:start position:0% yeah yeah that's uh that's really the 01:21:46.140 --> 01:21:48.470 align:start position:0% yeah yeah that's uh that's really the idea<01:21:46.320> of<01:21:46.500> the<01:21:46.800> the<01:21:47.219> Patricia<01:21:47.880> tree<01:21:48.060> is<01:21:48.300> that 01:21:48.470 --> 01:21:48.480 align:start position:0% idea of the the Patricia tree is that 01:21:48.480 --> 01:21:50.630 align:start position:0% idea of the the Patricia tree is that you're<01:21:48.659> following<01:21:49.080> the 01:21:50.630 --> 01:21:50.640 align:start position:0% you're following the 01:21:50.640 --> 01:21:52.970 align:start position:0% you're following the sort<01:21:51.360> of<01:21:51.420> following<01:21:51.840> the<01:21:52.020> keys<01:21:52.380> along<01:21:52.679> that 01:21:52.970 --> 01:21:52.980 align:start position:0% sort of following the keys along that 01:21:52.980 --> 01:21:55.669 align:start position:0% sort of following the keys along that path<01:21:53.219> and<01:21:53.520> everything<01:21:53.699> that<01:21:54.060> shares 01:21:55.669 --> 01:21:55.679 align:start position:0% path and everything that shares 01:21:55.679 --> 01:22:15.040 align:start position:0% path and everything that shares shares<01:21:56.400> bites 01:22:15.040 --> 01:22:15.050 align:start position:0% 01:22:15.050 --> 01:22:19.790 align:start position:0% [Music] 01:22:19.790 --> 01:22:19.800 align:start position:0% 01:22:19.800 --> 01:22:22.430 align:start position:0% yeah<01:22:20.340> yeah<01:22:20.940> and<01:22:21.480> something<01:22:21.719> like<01:22:22.020> to<01:22:22.260> mention 01:22:22.430 --> 01:22:22.440 align:start position:0% yeah yeah and something like to mention 01:22:22.440 --> 01:22:25.370 align:start position:0% yeah yeah and something like to mention here<01:22:22.739> this<01:22:23.460> is<01:22:23.640> only<01:22:23.820> keys<01:22:24.420> right<01:22:24.600> this<01:22:25.080> is<01:22:25.199> not 01:22:25.370 --> 01:22:25.380 align:start position:0% here this is only keys right this is not 01:22:25.380 --> 01:22:28.490 align:start position:0% here this is only keys right this is not the<01:22:25.620> values<01:22:25.920> themselves<01:22:26.280> and<01:22:27.120> like<01:22:27.960> later<01:22:28.260> a 01:22:28.490 --> 01:22:28.500 align:start position:0% the values themselves and like later a 01:22:28.500 --> 01:22:30.169 align:start position:0% the values themselves and like later a bit<01:22:28.560> in<01:22:28.739> the<01:22:28.860> tutorial<01:22:29.159> we<01:22:29.400> see<01:22:29.580> how<01:22:29.820> you<01:22:30.000> know 01:22:30.169 --> 01:22:30.179 align:start position:0% bit in the tutorial we see how you know 01:22:30.179 --> 01:22:32.090 align:start position:0% bit in the tutorial we see how you know the<01:22:30.300> hashes<01:22:30.719> of<01:22:31.020> every<01:22:31.260> like<01:22:31.440> parent<01:22:31.679> is 01:22:32.090 --> 01:22:32.100 align:start position:0% the hashes of every like parent is 01:22:32.100 --> 01:22:34.310 align:start position:0% the hashes of every like parent is computed<01:22:32.520> which<01:22:32.820> is<01:22:33.000> like<01:22:33.600> different<01:22:33.900> you 01:22:34.310 --> 01:22:34.320 align:start position:0% computed which is like different you 01:22:34.320 --> 01:22:37.310 align:start position:0% computed which is like different you know<01:22:34.440> from<01:22:34.739> this<01:22:34.980> but<01:22:35.880> uh<01:22:36.300> yeah<01:22:36.480> so<01:22:36.719> if<01:22:36.900> we<01:22:37.080> had 01:22:37.310 --> 01:22:37.320 align:start position:0% know from this but uh yeah so if we had 01:22:37.320 --> 01:22:40.669 align:start position:0% know from this but uh yeah so if we had like<01:22:37.679> uh<01:22:38.100> also<01:22:38.580> a<01:22:38.820> a<01:22:39.179> key<01:22:39.540> address<01:22:39.780> T<01:22:40.140> we<01:22:40.620> would 01:22:40.669 --> 01:22:40.679 align:start position:0% like uh also a a key address T we would 01:22:40.679 --> 01:22:42.410 align:start position:0% like uh also a a key address T we would see<01:22:40.860> like<01:22:41.040> that<01:22:41.280> that<01:22:41.460> would<01:22:41.640> be<01:22:41.760> only<01:22:41.880> 74 01:22:42.410 --> 01:22:42.420 align:start position:0% see like that that would be only 74 01:22:42.420 --> 01:22:45.709 align:start position:0% see like that that would be only 74 because<01:22:42.840> that<01:22:43.380> like<01:22:43.800> lowercase<01:22:44.280> T<01:22:44.520> is<01:22:44.699> 74<01:22:45.120> uh 01:22:45.709 --> 01:22:45.719 align:start position:0% because that like lowercase T is 74 uh 01:22:45.719 --> 01:22:47.149 align:start position:0% because that like lowercase T is 74 uh in<01:22:45.900> HEX 01:22:47.149 --> 01:22:47.159 align:start position:0% in HEX 01:22:47.159 --> 01:22:49.910 align:start position:0% in HEX and<01:22:47.880> uh<01:22:48.060> we<01:22:48.300> would<01:22:48.420> see<01:22:48.540> a<01:22:48.659> branch<01:22:48.840> note<01:22:49.080> at<01:22:49.380> 74. 01:22:49.910 --> 01:22:49.920 align:start position:0% and uh we would see a branch note at 74. 01:22:49.920 --> 01:22:51.770 align:start position:0% and uh we would see a branch note at 74. there<01:22:50.100> would<01:22:50.280> be<01:22:50.340> value<01:22:50.580> already<01:22:51.060> there<01:22:51.420> and 01:22:51.770 --> 01:22:51.780 align:start position:0% there would be value already there and 01:22:51.780 --> 01:22:54.590 align:start position:0% there would be value already there and then<01:22:51.900> there<01:22:52.080> would<01:22:52.260> be<01:22:52.440> like<01:22:53.100> nodes<01:22:53.699> uh<01:22:54.300> like 01:22:54.590 --> 01:22:54.600 align:start position:0% then there would be like nodes uh like 01:22:54.600 --> 01:22:56.810 align:start position:0% then there would be like nodes uh like paths<01:22:55.020> to<01:22:55.199> uh<01:22:55.739> all<01:22:55.920> the<01:22:56.040> way<01:22:56.100> down<01:22:56.280> to<01:22:56.520> you<01:22:56.699> know 01:22:56.810 --> 01:22:56.820 align:start position:0% paths to uh all the way down to you know 01:22:56.820 --> 01:22:58.729 align:start position:0% paths to uh all the way down to you know 79<01:22:57.239> it<01:22:57.719> would<01:22:57.840> be<01:22:57.960> like<01:22:58.080> we'll<01:22:58.320> see<01:22:58.500> that<01:22:58.620> after 01:22:58.729 --> 01:22:58.739 align:start position:0% 79 it would be like we'll see that after 01:22:58.739 --> 01:23:00.770 align:start position:0% 79 it would be like we'll see that after but<01:22:59.100> it<01:22:59.280> would<01:22:59.400> be<01:22:59.520> like<01:22:59.640> an<01:22:59.820> extension<01:23:00.540> node 01:23:00.770 --> 01:23:00.780 align:start position:0% but it would be like an extension node 01:23:00.780 --> 01:23:03.229 align:start position:0% but it would be like an extension node for<01:23:01.020> optimization<01:23:01.800> purposes<01:23:02.219> and<01:23:03.000> then<01:23:03.060> you 01:23:03.229 --> 01:23:03.239 align:start position:0% for optimization purposes and then you 01:23:03.239 --> 01:23:05.390 align:start position:0% for optimization purposes and then you have<01:23:03.480> well<01:23:03.960> branches<01:23:04.440> as<01:23:04.560> we've<01:23:04.739> said<01:23:04.920> to<01:23:05.100> 30 01:23:05.390 --> 01:23:05.400 align:start position:0% have well branches as we've said to 30 01:23:05.400 --> 01:23:07.250 align:start position:0% have well branches as we've said to 30 and<01:23:05.640> and<01:23:05.940> 41. 01:23:07.250 --> 01:23:07.260 align:start position:0% and and 41. 01:23:07.260 --> 01:23:08.450 align:start position:0% and and 41. so 01:23:08.450 --> 01:23:08.460 align:start position:0% so 01:23:08.460 --> 01:23:09.770 align:start position:0% so yeah<01:23:08.820> what<01:23:09.000> we're<01:23:09.120> going<01:23:09.239> to<01:23:09.300> do<01:23:09.420> is<01:23:09.480> update 01:23:09.770 --> 01:23:09.780 align:start position:0% yeah what we're going to do is update 01:23:09.780 --> 01:23:11.510 align:start position:0% yeah what we're going to do is update the<01:23:09.900> tree<01:23:10.080> with<01:23:10.320> all<01:23:10.500> those<01:23:10.620> keys<01:23:10.920> we're<01:23:11.340> going 01:23:11.510 --> 01:23:11.520 align:start position:0% the tree with all those keys we're going 01:23:11.520 --> 01:23:13.189 align:start position:0% the tree with all those keys we're going to<01:23:11.580> find<01:23:11.699> the<01:23:11.880> path<01:23:12.060> to<01:23:12.179> test<01:23:12.420> key<01:23:12.659> and<01:23:13.080> we're 01:23:13.189 --> 01:23:13.199 align:start position:0% to find the path to test key and we're 01:23:13.199 --> 01:23:14.930 align:start position:0% to find the path to test key and we're going<01:23:13.320> to<01:23:13.440> see<01:23:13.560> what<01:23:13.679> that<01:23:13.980> no<01:23:14.280> you<01:23:14.820> know 01:23:14.930 --> 01:23:14.940 align:start position:0% going to see what that no you know 01:23:14.940 --> 01:23:22.010 align:start position:0% going to see what that no you know actually<01:23:15.659> uh<01:23:16.320> looks<01:23:16.739> like 01:23:22.010 --> 01:23:22.020 align:start position:0% 01:23:22.020 --> 01:23:24.229 align:start position:0% all<01:23:22.500> right<01:23:22.679> so<01:23:23.460> that's<01:23:23.640> actually<01:23:23.880> a<01:23:24.120> pretty 01:23:24.229 --> 01:23:24.239 align:start position:0% all right so that's actually a pretty 01:23:24.239 --> 01:23:26.870 align:start position:0% all right so that's actually a pretty nice<01:23:24.480> like<01:23:24.900> visualization<01:23:25.739> I<01:23:26.159> think<01:23:26.219> of<01:23:26.580> what 01:23:26.870 --> 01:23:26.880 align:start position:0% nice like visualization I think of what 01:23:26.880 --> 01:23:28.610 align:start position:0% nice like visualization I think of what uh<01:23:27.060> of<01:23:27.300> what's<01:23:27.480> going<01:23:27.659> on<01:23:27.780> so<01:23:28.020> we<01:23:28.260> have<01:23:28.380> you 01:23:28.610 --> 01:23:28.620 align:start position:0% uh of what's going on so we have you 01:23:28.620 --> 01:23:30.709 align:start position:0% uh of what's going on so we have you know<01:23:28.739> for<01:23:28.860> the<01:23:29.159> three<01:23:29.280> buffers<01:23:29.699> then<01:23:30.540> we're 01:23:30.709 --> 01:23:30.719 align:start position:0% know for the three buffers then we're 01:23:30.719 --> 01:23:32.510 align:start position:0% know for the three buffers then we're updating<01:23:31.080> with<01:23:31.320> all<01:23:31.440> those<01:23:31.620> three<01:23:31.800> keys<01:23:32.280> so 01:23:32.510 --> 01:23:32.520 align:start position:0% updating with all those three keys so 01:23:32.520 --> 01:23:33.830 align:start position:0% updating with all those three keys so we're<01:23:32.640> updating<01:23:32.880> the<01:23:33.060> tree<01:23:33.179> with<01:23:33.420> desk<01:23:33.600> key 01:23:33.830 --> 01:23:33.840 align:start position:0% we're updating the tree with desk key 01:23:33.840 --> 01:23:35.930 align:start position:0% we're updating the tree with desk key test<01:23:34.080> key<01:23:34.260> zero<01:23:34.560> test<01:23:34.739> key<01:23:34.980> a<01:23:35.219> which<01:23:35.520> all<01:23:35.760> have 01:23:35.930 --> 01:23:35.940 align:start position:0% test key zero test key a which all have 01:23:35.940 --> 01:23:37.310 align:start position:0% test key zero test key a which all have the<01:23:36.120> same<01:23:36.239> prefix 01:23:37.310 --> 01:23:37.320 align:start position:0% the same prefix 01:23:37.320 --> 01:23:41.990 align:start position:0% the same prefix we<01:23:38.100> query<01:23:38.699> the<01:23:39.179> the<01:23:39.360> node<01:23:39.840> that<01:23:40.320> lives<01:23:40.679> at<01:23:40.980> Key 01:23:41.990 --> 01:23:42.000 align:start position:0% we query the the node that lives at Key 01:23:42.000 --> 01:23:44.510 align:start position:0% we query the the node that lives at Key test<01:23:42.360> key<01:23:42.659> which<01:23:43.260> is<01:23:43.380> the<01:23:43.620> the<01:23:43.860> common<01:23:44.100> prefix 01:23:44.510 --> 01:23:44.520 align:start position:0% test key which is the the common prefix 01:23:44.520 --> 01:23:47.750 align:start position:0% test key which is the the common prefix for<01:23:44.699> all<01:23:44.880> those<01:23:45.380> so<01:23:46.380> what<01:23:46.679> we<01:23:46.860> see<01:23:47.040> so<01:23:47.520> this<01:23:47.640> is 01:23:47.750 --> 01:23:47.760 align:start position:0% for all those so what we see so this is 01:23:47.760 --> 01:23:51.530 align:start position:0% for all those so what we see so this is index<01:23:48.120> you<01:23:48.420> know<01:23:48.480> zero<01:23:49.080> one<01:23:49.560> two<01:23:50.159> three<01:23:50.880> four 01:23:51.530 --> 01:23:51.540 align:start position:0% index you know zero one two three four 01:23:51.540 --> 01:23:54.169 align:start position:0% index you know zero one two three four which<01:23:52.500> correspond<01:23:53.040> to<01:23:53.219> numerical<01:23:53.760> values 01:23:54.169 --> 01:23:54.179 align:start position:0% which correspond to numerical values 01:23:54.179 --> 01:23:56.209 align:start position:0% which correspond to numerical values like<01:23:54.420> just<01:23:54.659> plus<01:23:54.960> one<01:23:55.140> since<01:23:55.440> indexes<01:23:55.980> start 01:23:56.209 --> 01:23:56.219 align:start position:0% like just plus one since indexes start 01:23:56.219 --> 01:23:57.470 align:start position:0% like just plus one since indexes start at<01:23:56.340> zero 01:23:57.470 --> 01:23:57.480 align:start position:0% at zero 01:23:57.480 --> 01:23:59.810 align:start position:0% at zero and<01:23:58.140> uh<01:23:58.320> actually<01:23:58.560> no<01:23:58.860> that's<01:23:59.159> not<01:23:59.280> true<01:23:59.460> just 01:23:59.810 --> 01:23:59.820 align:start position:0% and uh actually no that's not true just 01:23:59.820 --> 01:24:02.090 align:start position:0% and uh actually no that's not true just correspond<01:24:00.360> exactly<01:24:00.900> to<01:24:01.140> the<01:24:01.320> actual<01:24:01.679> values 01:24:02.090 --> 01:24:02.100 align:start position:0% correspond exactly to the actual values 01:24:02.100 --> 01:24:04.970 align:start position:0% correspond exactly to the actual values and<01:24:03.000> uh<01:24:03.360> and<01:24:03.900> we're<01:24:04.020> seeing<01:24:04.260> that<01:24:04.560> there<01:24:04.800> are 01:24:04.970 --> 01:24:04.980 align:start position:0% and uh and we're seeing that there are 01:24:04.980 --> 01:24:09.709 align:start position:0% and uh and we're seeing that there are two<01:24:05.540> uh<01:24:06.540> different<01:24:06.900> you<01:24:07.620> know<01:24:07.739> values<01:24:08.280> here 01:24:09.709 --> 01:24:09.719 align:start position:0% two uh different you know values here 01:24:09.719 --> 01:24:12.290 align:start position:0% two uh different you know values here so<01:24:10.199> that<01:24:10.380> is<01:24:10.500> what<01:24:10.800> we'd<01:24:11.100> expect<01:24:11.280> we<01:24:11.760> have<01:24:11.880> like 01:24:12.290 --> 01:24:12.300 align:start position:0% so that is what we'd expect we have like 01:24:12.300 --> 01:24:15.050 align:start position:0% so that is what we'd expect we have like this<01:24:12.780> is<01:24:12.900> basically<01:24:13.260> like<01:24:13.560> empty<01:24:14.100> so<01:24:14.699> like 01:24:15.050 --> 01:24:15.060 align:start position:0% this is basically like empty so like 01:24:15.060 --> 01:24:17.209 align:start position:0% this is basically like empty so like null<01:24:15.360> nodes<01:24:15.659> because<01:24:15.840> there's<01:24:16.080> no<01:24:16.380> path<01:24:16.620> uh<01:24:17.159> at 01:24:17.209 --> 01:24:17.219 align:start position:0% null nodes because there's no path uh at 01:24:17.219 --> 01:24:20.870 align:start position:0% null nodes because there's no path uh at that<01:24:17.400> point<01:24:17.520> like<01:24:17.960> uh<01:24:18.960> at<01:24:19.560> Key<01:24:20.100> zero<01:24:20.580> there's 01:24:20.870 --> 01:24:20.880 align:start position:0% that point like uh at Key zero there's 01:24:20.880 --> 01:24:22.790 align:start position:0% that point like uh at Key zero there's no<01:24:21.120> we<01:24:21.420> don't<01:24:21.540> have<01:24:21.719> any 01:24:22.790 --> 01:24:22.800 align:start position:0% no we don't have any 01:24:22.800 --> 01:24:25.010 align:start position:0% no we don't have any anything<01:24:23.340> uh<01:24:23.699> that<01:24:23.940> lives<01:24:24.120> at<01:24:24.239> zero<01:24:24.540> right<01:24:24.659> we 01:24:25.010 --> 01:24:25.020 align:start position:0% anything uh that lives at zero right we 01:24:25.020 --> 01:24:27.110 align:start position:0% anything uh that lives at zero right we don't<01:24:25.140> have<01:24:25.320> anything<01:24:25.500> that<01:24:25.800> lives<01:24:26.040> at<01:24:26.280> one 01:24:27.110 --> 01:24:27.120 align:start position:0% don't have anything that lives at one 01:24:27.120 --> 01:24:28.550 align:start position:0% don't have anything that lives at one so<01:24:27.480> we<01:24:27.600> have<01:24:27.719> nothing<01:24:27.900> that<01:24:28.080> leaves<01:24:28.320> it<01:24:28.440> two 01:24:28.550 --> 01:24:28.560 align:start position:0% so we have nothing that leaves it two 01:24:28.560 --> 01:24:31.430 align:start position:0% so we have nothing that leaves it two but<01:24:28.860> starting<01:24:29.040> from<01:24:29.280> tree<01:24:29.580> we<01:24:30.239> have<01:24:30.480> an<01:24:31.199> actual 01:24:31.430 --> 01:24:31.440 align:start position:0% but starting from tree we have an actual 01:24:31.440 --> 01:24:32.570 align:start position:0% but starting from tree we have an actual path 01:24:32.570 --> 01:24:32.580 align:start position:0% path 01:24:32.580 --> 01:24:35.630 align:start position:0% path and<01:24:33.120> we<01:24:33.360> see<01:24:33.540> that<01:24:33.780> complete<01:24:34.140> path<01:24:34.260> here 01:24:35.630 --> 01:24:35.640 align:start position:0% and we see that complete path here 01:24:35.640 --> 01:24:38.750 align:start position:0% and we see that complete path here we<01:24:36.060> also<01:24:36.300> have<01:24:36.480> the<01:24:36.659> same<01:24:36.840> for 01:24:38.750 --> 01:24:38.760 align:start position:0% we also have the same for 01:24:38.760 --> 01:24:43.250 align:start position:0% we also have the same for 41<01:24:39.600> which<01:24:40.380> is<01:24:40.560> you<01:24:40.800> know<01:24:40.920> index<01:24:41.580> 4. 01:24:43.250 --> 01:24:43.260 align:start position:0% 41 which is you know index 4. 01:24:43.260 --> 01:24:45.110 align:start position:0% 41 which is you know index 4. and<01:24:43.679> then<01:24:43.800> we<01:24:43.980> have<01:24:44.159> nothing<01:24:44.520> all<01:24:44.940> the<01:24:45.060> way 01:24:45.110 --> 01:24:45.120 align:start position:0% and then we have nothing all the way 01:24:45.120 --> 01:24:47.570 align:start position:0% and then we have nothing all the way down<01:24:45.300> an<01:24:46.199> interesting<01:24:46.560> thing<01:24:46.800> is<01:24:47.100> we<01:24:47.340> also 01:24:47.570 --> 01:24:47.580 align:start position:0% down an interesting thing is we also 01:24:47.580 --> 01:24:50.870 align:start position:0% down an interesting thing is we also have<01:24:47.760> a<01:24:48.000> value<01:24:48.239> already<01:24:48.960> here<01:24:49.380> at<01:24:49.980> address<01:24:50.400> you 01:24:50.870 --> 01:24:50.880 align:start position:0% have a value already here at address you 01:24:50.880 --> 01:24:53.570 align:start position:0% have a value already here at address you know<01:24:51.000> that's<01:24:51.719> basically<01:24:52.080> test<01:24:52.380> key<01:24:52.620> and<01:24:53.040> hex 01:24:53.570 --> 01:24:53.580 align:start position:0% know that's basically test key and hex 01:24:53.580 --> 01:24:55.910 align:start position:0% know that's basically test key and hex so<01:24:54.239> a<01:24:54.360> branch<01:24:54.659> node<01:24:54.960> is<01:24:55.320> not<01:24:55.440> only<01:24:55.620> an 01:24:55.910 --> 01:24:55.920 align:start position:0% so a branch node is not only an 01:24:55.920 --> 01:24:58.090 align:start position:0% so a branch node is not only an intermediary<01:24:56.520> node<01:24:56.820> it<01:24:57.000> can<01:24:57.179> also<01:24:57.420> contain 01:24:58.090 --> 01:24:58.100 align:start position:0% intermediary node it can also contain 01:24:58.100 --> 01:25:01.370 align:start position:0% intermediary node it can also contain values<01:24:59.100> you<01:24:59.640> know<01:24:59.760> itself<01:25:00.179> in<01:25:01.020> the<01:25:01.140> case<01:25:01.260> of 01:25:01.370 --> 01:25:01.380 align:start position:0% values you know itself in the case of 01:25:01.380 --> 01:25:02.990 align:start position:0% values you know itself in the case of keys<01:25:01.739> which<01:25:01.860> would<01:25:02.100> always<01:25:02.340> have<01:25:02.699> the<01:25:02.880> same 01:25:02.990 --> 01:25:03.000 align:start position:0% keys which would always have the same 01:25:03.000 --> 01:25:04.970 align:start position:0% keys which would always have the same length<01:25:03.360> you<01:25:03.600> might<01:25:03.900> not<01:25:03.960> see<01:25:04.199> like<01:25:04.380> values<01:25:04.800> at 01:25:04.970 --> 01:25:04.980 align:start position:0% length you might not see like values at 01:25:04.980 --> 01:25:06.470 align:start position:0% length you might not see like values at certain<01:25:05.159> intermediary<01:25:05.699> node<01:25:05.940> because<01:25:06.120> they 01:25:06.470 --> 01:25:06.480 align:start position:0% certain intermediary node because they 01:25:06.480 --> 01:25:08.450 align:start position:0% certain intermediary node because they all<01:25:06.600> leave<01:25:06.780> them<01:25:06.960> Leaf<01:25:07.380> nodes<01:25:07.679> but<01:25:08.100> you<01:25:08.280> can 01:25:08.450 --> 01:25:08.460 align:start position:0% all leave them Leaf nodes but you can 01:25:08.460 --> 01:25:10.250 align:start position:0% all leave them Leaf nodes but you can still<01:25:08.880> use<01:25:09.060> that<01:25:09.239> data<01:25:09.540> structure<01:25:09.840> for<01:25:10.080> other 01:25:10.250 --> 01:25:10.260 align:start position:0% still use that data structure for other 01:25:10.260 --> 01:25:11.990 align:start position:0% still use that data structure for other purposes<01:25:10.679> where<01:25:11.040> you<01:25:11.460> know<01:25:11.580> the<01:25:11.699> length<01:25:11.940> of 01:25:11.990 --> 01:25:12.000 align:start position:0% purposes where you know the length of 01:25:12.000 --> 01:25:20.330 align:start position:0% purposes where you know the length of keys<01:25:12.239> wouldn't<01:25:12.360> always<01:25:12.600> be<01:25:12.900> the<01:25:13.080> same 01:25:20.330 --> 01:25:20.340 align:start position:0% 01:25:20.340 --> 01:25:22.850 align:start position:0% all<01:25:20.820> right<01:25:20.940> yeah<01:25:21.360> so<01:25:21.719> that's<01:25:21.840> exactly<01:25:22.320> exactly 01:25:22.850 --> 01:25:22.860 align:start position:0% all right yeah so that's exactly exactly 01:25:22.860 --> 01:25:25.790 align:start position:0% all right yeah so that's exactly exactly uh<01:25:23.159> what<01:25:23.400> we<01:25:23.520> see<01:25:23.640> and<01:25:24.060> we<01:25:24.300> can<01:25:24.480> uh<01:25:25.080> we<01:25:25.560> can<01:25:25.679> take 01:25:25.790 --> 01:25:25.800 align:start position:0% uh what we see and we can uh we can take 01:25:25.800 --> 01:25:29.630 align:start position:0% uh what we see and we can uh we can take the<01:25:25.980> value<01:25:26.159> of<01:25:26.520> that<01:25:26.640> node<01:25:26.940> and<01:25:27.239> see<01:25:27.420> if<01:25:27.540> we<01:25:27.780> can 01:25:29.630 --> 01:25:29.640 align:start position:0% the value of that node and see if we can 01:25:29.640 --> 01:25:32.090 align:start position:0% the value of that node and see if we can like<01:25:30.000> the<01:25:30.179> value<01:25:30.360> here<01:25:30.600> we<01:25:31.020> can 01:25:32.090 --> 01:25:32.100 align:start position:0% like the value here we can 01:25:32.100 --> 01:25:34.850 align:start position:0% like the value here we can yeah<01:25:32.520> we<01:25:32.820> can<01:25:33.000> parse<01:25:33.900> it<01:25:34.080> to<01:25:34.199> string<01:25:34.500> let<01:25:34.679> me 01:25:34.850 --> 01:25:34.860 align:start position:0% yeah we can parse it to string let me 01:25:34.860 --> 01:25:36.250 align:start position:0% yeah we can parse it to string let me find<01:25:34.980> you<01:25:35.159> the<01:25:35.280> code<01:25:35.460> so<01:25:35.640> it's<01:25:35.820> more 01:25:36.250 --> 01:25:36.260 align:start position:0% find you the code so it's more 01:25:36.260 --> 01:25:40.130 align:start position:0% find you the code so it's more revelatory<01:25:37.260> of<01:25:37.500> what's<01:25:37.800> actually 01:25:40.130 --> 01:25:40.140 align:start position:0% revelatory of what's actually 01:25:40.140 --> 01:25:44.149 align:start position:0% revelatory of what's actually going<01:25:40.500> on<01:25:40.800> so<01:25:41.460> yeah<01:25:41.640> we<01:25:42.300> we<01:25:42.840> found<01:25:43.320> a<01:25:43.560> path<01:25:43.800> we 01:25:44.149 --> 01:25:44.159 align:start position:0% going on so yeah we we found a path we 01:25:44.159 --> 01:25:46.130 align:start position:0% going on so yeah we we found a path we found<01:25:44.280> a<01:25:44.460> node<01:25:44.699> we<01:25:45.000> take<01:25:45.179> that<01:25:45.360> node<01:25:45.659> we<01:25:45.960> look 01:25:46.130 --> 01:25:46.140 align:start position:0% found a node we take that node we look 01:25:46.140 --> 01:25:48.169 align:start position:0% found a node we take that node we look at<01:25:46.260> the<01:25:46.440> value<01:25:46.620> at<01:25:46.980> that<01:25:47.159> specific<01:25:47.460> point<01:25:47.760> and 01:25:48.169 --> 01:25:48.179 align:start position:0% at the value at that specific point and 01:25:48.179 --> 01:25:50.090 align:start position:0% at the value at that specific point and it<01:25:48.300> should<01:25:48.480> be<01:25:48.659> the<01:25:49.080> the<01:25:49.260> value<01:25:49.500> that<01:25:49.860> we've 01:25:50.090 --> 01:25:50.100 align:start position:0% it should be the the value that we've 01:25:50.100 --> 01:25:52.430 align:start position:0% it should be the the value that we've put<01:25:50.460> at<01:25:50.880> test<01:25:51.300> key 01:25:52.430 --> 01:25:52.440 align:start position:0% put at test key 01:25:52.440 --> 01:25:55.490 align:start position:0% put at test key now<01:25:52.980> if<01:25:53.340> we<01:25:53.460> were<01:25:53.640> to<01:25:53.820> take<01:25:54.179> a 01:25:55.490 --> 01:25:55.500 align:start position:0% now if we were to take a 01:25:55.500 --> 01:25:58.850 align:start position:0% now if we were to take a uh<01:25:55.920> the<01:25:56.699> value<01:25:56.880> of<01:25:57.480> a<01:25:57.719> of<01:25:58.199> one<01:25:58.380> of<01:25:58.500> the<01:25:58.620> nodes 01:25:58.850 --> 01:25:58.860 align:start position:0% uh the value of a of one of the nodes 01:25:58.860 --> 01:26:01.610 align:start position:0% uh the value of a of one of the nodes that<01:25:59.460> is<01:25:59.940> a<01:26:00.179> child<01:26:00.360> of<01:26:00.600> that<01:26:00.719> parent<01:26:00.900> node<01:26:01.320> we 01:26:01.610 --> 01:26:01.620 align:start position:0% that is a child of that parent node we 01:26:01.620 --> 01:26:04.610 align:start position:0% that is a child of that parent node we would<01:26:01.800> get<01:26:02.100> also<01:26:02.699> like<01:26:02.880> test<01:26:03.120> test<01:26:03.659> value<01:26:03.960> zero 01:26:04.610 --> 01:26:04.620 align:start position:0% would get also like test test value zero 01:26:04.620 --> 01:26:07.129 align:start position:0% would get also like test test value zero and<01:26:04.860> test<01:26:05.040> value<01:26:05.400> a<01:26:05.820> so<01:26:06.420> it<01:26:06.600> is<01:26:06.719> what<01:26:06.960> we're 01:26:07.129 --> 01:26:07.139 align:start position:0% and test value a so it is what we're 01:26:07.139 --> 01:26:09.890 align:start position:0% and test value a so it is what we're doing<01:26:07.560> you<01:26:07.980> know<01:26:08.100> a<01:26:08.280> bit<01:26:08.460> further<01:26:09.239> down<01:26:09.360> here 01:26:09.890 --> 01:26:09.900 align:start position:0% doing you know a bit further down here 01:26:09.900 --> 01:26:12.290 align:start position:0% doing you know a bit further down here so<01:26:10.739> let's<01:26:10.860> look<01:26:11.040> at<01:26:11.159> how<01:26:11.580> we're<01:26:11.880> you<01:26:12.179> know 01:26:12.290 --> 01:26:12.300 align:start position:0% so let's look at how we're you know 01:26:12.300 --> 01:26:17.209 align:start position:0% so let's look at how we're you know retrieving<01:26:12.780> that 01:26:17.209 --> 01:26:17.219 align:start position:0% 01:26:17.219 --> 01:26:19.850 align:start position:0% we<01:26:18.000> are<01:26:18.120> taking<01:26:18.480> you<01:26:18.960> know<01:26:19.080> the<01:26:19.320> third<01:26:19.500> branch 01:26:19.850 --> 01:26:19.860 align:start position:0% we are taking you know the third branch 01:26:19.860 --> 01:26:23.090 align:start position:0% we are taking you know the third branch and<01:26:20.580> the<01:26:20.760> the<01:26:21.139> second<01:26:22.139> element<01:26:22.380> that's<01:26:22.860> just 01:26:23.090 --> 01:26:23.100 align:start position:0% and the the second element that's just 01:26:23.100 --> 01:26:26.930 align:start position:0% and the the second element that's just the<01:26:23.340> that's<01:26:24.300> the<01:26:24.600> value<01:26:24.780> of<01:26:25.320> the<01:26:25.560> the<01:26:25.739> of<01:26:26.580> that 01:26:26.930 --> 01:26:26.940 align:start position:0% the that's the value of the the of that 01:26:26.940 --> 01:26:29.450 align:start position:0% the that's the value of the the of that leaf<01:26:27.540> end<01:26:27.780> node<01:26:28.020> converting<01:26:28.860> it<01:26:28.980> to<01:26:29.159> a<01:26:29.219> string 01:26:29.450 --> 01:26:29.460 align:start position:0% leaf end node converting it to a string 01:26:29.460 --> 01:26:31.850 align:start position:0% leaf end node converting it to a string and<01:26:29.639> then<01:26:29.820> we<01:26:29.940> get<01:26:30.060> we<01:26:30.420> retrieve<01:26:30.960> the<01:26:31.139> value 01:26:31.850 --> 01:26:31.860 align:start position:0% and then we get we retrieve the value 01:26:31.860 --> 01:26:34.550 align:start position:0% and then we get we retrieve the value back 01:26:34.550 --> 01:26:34.560 align:start position:0% 01:26:34.560 --> 01:26:36.229 align:start position:0% is<01:26:35.040> that<01:26:35.159> somewhat<01:26:35.520> clear 01:26:36.229 --> 01:26:36.239 align:start position:0% is that somewhat clear 01:26:36.239 --> 01:26:38.870 align:start position:0% is that somewhat clear breast<01:26:36.719> nodes<01:26:37.080> are<01:26:37.260> a<01:26:37.380> bit<01:26:37.500> trickier<01:26:38.100> but<01:26:38.520> is 01:26:38.870 --> 01:26:38.880 align:start position:0% breast nodes are a bit trickier but is 01:26:38.880 --> 01:26:44.750 align:start position:0% breast nodes are a bit trickier but is uh<01:26:39.239> is<01:26:39.780> everyone<01:26:39.900> sort<01:26:40.440> of<01:26:40.620> following<01:26:40.860> along 01:26:44.750 --> 01:26:44.760 align:start position:0% 01:26:44.760 --> 01:27:09.110 align:start position:0% yeah<01:26:45.060> yeah 01:27:09.110 --> 01:27:09.120 align:start position:0% 01:27:09.120 --> 01:27:13.610 align:start position:0% yeah<01:27:09.719> so<01:27:10.020> let<01:27:10.199> me 01:27:13.610 --> 01:27:13.620 align:start position:0% 01:27:13.620 --> 01:27:15.770 align:start position:0% think<01:27:14.159> we're 01:27:15.770 --> 01:27:15.780 align:start position:0% think we're 01:27:15.780 --> 01:27:19.490 align:start position:0% think we're there's<01:27:16.199> a<01:27:16.440> bit<01:27:16.560> more<01:27:16.800> clarity<01:27:17.699> about<01:27:18.480> that 01:27:19.490 --> 01:27:19.500 align:start position:0% there's a bit more clarity about that 01:27:19.500 --> 01:27:22.370 align:start position:0% there's a bit more clarity about that after<01:27:19.920> so<01:27:20.699> I<01:27:20.880> think<01:27:21.120> the<01:27:21.659> next<01:27:21.780> example<01:27:22.199> is 01:27:22.370 --> 01:27:22.380 align:start position:0% after so I think the next example is 01:27:22.380 --> 01:27:24.229 align:start position:0% after so I think the next example is going<01:27:22.560> to<01:27:22.679> clarify<01:27:23.100> that<01:27:23.340> for<01:27:23.699> you<01:27:23.820> and<01:27:24.000> if<01:27:24.120> it 01:27:24.229 --> 01:27:24.239 align:start position:0% going to clarify that for you and if it 01:27:24.239 --> 01:27:26.030 align:start position:0% going to clarify that for you and if it doesn't<01:27:24.360> we<01:27:24.659> can<01:27:24.780> come<01:27:24.960> back<01:27:25.080> to<01:27:25.199> it<01:27:25.380> and<01:27:25.560> play 01:27:26.030 --> 01:27:26.040 align:start position:0% doesn't we can come back to it and play 01:27:26.040 --> 01:27:28.850 align:start position:0% doesn't we can come back to it and play a<01:27:26.580> little<01:27:26.820> bit<01:27:26.940> more<01:27:27.060> with<01:27:27.300> it<01:27:27.420> it<01:27:27.840> is 01:27:28.850 --> 01:27:28.860 align:start position:0% a little bit more with it it is 01:27:28.860 --> 01:27:31.189 align:start position:0% a little bit more with it it is like<01:27:29.460> getting<01:27:29.820> like<01:27:30.120> nodes<01:27:30.480> in<01:27:30.659> how<01:27:30.900> they're 01:27:31.189 --> 01:27:31.199 align:start position:0% like getting like nodes in how they're 01:27:31.199 --> 01:27:33.229 align:start position:0% like getting like nodes in how they're structured<01:27:31.620> and<01:27:31.800> how<01:27:32.040> they<01:27:32.340> they<01:27:32.880> operate 01:27:33.229 --> 01:27:33.239 align:start position:0% structured and how they they operate 01:27:33.239 --> 01:27:35.030 align:start position:0% structured and how they they operate within<01:27:33.600> one<01:27:33.719> another<01:27:33.900> is<01:27:34.199> that<01:27:34.320> trickier<01:27:34.800> part 01:27:35.030 --> 01:27:35.040 align:start position:0% within one another is that trickier part 01:27:35.040 --> 01:27:37.430 align:start position:0% within one another is that trickier part but<01:27:35.760> uh<01:27:36.120> yeah<01:27:36.300> Branch<01:27:36.659> nodes<01:27:36.900> and<01:27:37.080> extension 01:27:37.430 --> 01:27:37.440 align:start position:0% but uh yeah Branch nodes and extension 01:27:37.440 --> 01:27:38.810 align:start position:0% but uh yeah Branch nodes and extension nodes<01:27:37.679> which<01:27:37.920> are<01:27:38.040> you<01:27:38.340> know<01:27:38.460> somewhat 01:27:38.810 --> 01:27:38.820 align:start position:0% nodes which are you know somewhat 01:27:38.820 --> 01:27:40.250 align:start position:0% nodes which are you know somewhat similar<01:27:39.179> in<01:27:39.300> structure<01:27:39.659> or<01:27:39.960> the<01:27:40.139> more 01:27:40.250 --> 01:27:40.260 align:start position:0% similar in structure or the more 01:27:40.260 --> 01:27:41.990 align:start position:0% similar in structure or the more configured<01:27:40.679> part<01:27:40.800> of<01:27:40.980> that<01:27:41.040> so<01:27:41.280> once<01:27:41.639> you<01:27:41.760> get 01:27:41.990 --> 01:27:42.000 align:start position:0% configured part of that so once you get 01:27:42.000 --> 01:27:43.729 align:start position:0% configured part of that so once you get that<01:27:42.420> and<01:27:42.719> it<01:27:42.900> kind<01:27:43.020> of<01:27:43.139> clicks<01:27:43.380> the<01:27:43.500> way<01:27:43.620> they 01:27:43.729 --> 01:27:43.739 align:start position:0% that and it kind of clicks the way they 01:27:43.739 --> 01:27:45.590 align:start position:0% that and it kind of clicks the way they work<01:27:43.920> together<01:27:44.100> you're<01:27:44.820> pretty<01:27:45.060> much<01:27:45.239> you 01:27:45.590 --> 01:27:45.600 align:start position:0% work together you're pretty much you 01:27:45.600 --> 01:27:47.689 align:start position:0% work together you're pretty much you know<01:27:45.659> done<01:27:46.260> understanding<01:27:46.920> that<01:27:47.100> that<01:27:47.280> data 01:27:47.689 --> 01:27:47.699 align:start position:0% know done understanding that that data 01:27:47.699 --> 01:27:48.950 align:start position:0% know done understanding that that data structure<01:27:48.000> so<01:27:48.300> it's<01:27:48.420> definitely<01:27:48.659> something 01:27:48.950 --> 01:27:48.960 align:start position:0% structure so it's definitely something 01:27:48.960 --> 01:27:50.510 align:start position:0% structure so it's definitely something that's<01:27:49.199> worth<01:27:49.380> you<01:27:49.739> know 01:27:50.510 --> 01:27:50.520 align:start position:0% that's worth you know 01:27:50.520 --> 01:27:53.149 align:start position:0% that's worth you know coming<01:27:51.060> back<01:27:51.239> to<01:27:51.360> and<01:27:51.540> making<01:27:51.719> sure<01:27:51.960> that<01:27:52.679> we 01:27:53.149 --> 01:27:53.159 align:start position:0% coming back to and making sure that we 01:27:53.159 --> 01:27:54.950 align:start position:0% coming back to and making sure that we understand<01:27:53.280> somebody<01:27:53.699> yeah<01:27:54.239> if<01:27:54.480> you<01:27:54.600> see<01:27:54.780> that 01:27:54.950 --> 01:27:54.960 align:start position:0% understand somebody yeah if you see that 01:27:54.960 --> 01:27:58.070 align:start position:0% understand somebody yeah if you see that array<01:27:55.320> of<01:27:55.560> 16<01:27:55.940> buffers<01:27:56.940> and<01:27:57.179> two<01:27:57.360> of<01:27:57.480> them<01:27:57.659> have 01:27:58.070 --> 01:27:58.080 align:start position:0% array of 16 buffers and two of them have 01:27:58.080 --> 01:28:01.669 align:start position:0% array of 16 buffers and two of them have have<01:27:58.560> keys<01:27:59.040> in<01:27:59.159> them<01:27:59.400> every<01:28:00.360> every<01:28:00.840> parent<01:28:01.260> as 01:28:01.669 --> 01:28:01.679 align:start position:0% have keys in them every every parent as 01:28:01.679 --> 01:28:03.229 align:start position:0% have keys in them every every parent as soon<01:28:01.920> as<01:28:02.040> that<01:28:02.280> branches<01:28:02.699> out<01:28:02.880> has 01:28:03.229 --> 01:28:03.239 align:start position:0% soon as that branches out has 01:28:03.239 --> 01:28:05.510 align:start position:0% soon as that branches out has automatically<01:28:03.840> 16<01:28:04.139> children<01:28:04.560> regardless<01:28:05.159> of 01:28:05.510 --> 01:28:05.520 align:start position:0% automatically 16 children regardless of 01:28:05.520 --> 01:28:07.970 align:start position:0% automatically 16 children regardless of how<01:28:06.360> many<01:28:06.480> values<01:28:06.840> are<01:28:07.020> actually<01:28:07.260> there<01:28:07.560> and 01:28:07.970 --> 01:28:07.980 align:start position:0% how many values are actually there and 01:28:07.980 --> 01:28:09.770 align:start position:0% how many values are actually there and like<01:28:08.159> where<01:28:08.460> they<01:28:08.639> go 01:28:09.770 --> 01:28:09.780 align:start position:0% like where they go 01:28:09.780 --> 01:28:11.870 align:start position:0% like where they go if<01:28:09.840> there's<01:28:10.320> only<01:28:10.620> one<01:28:10.980> then<01:28:11.219> we<01:28:11.400> can<01:28:11.520> compress 01:28:11.870 --> 01:28:11.880 align:start position:0% if there's only one then we can compress 01:28:11.880 --> 01:28:13.490 align:start position:0% if there's only one then we can compress it<01:28:12.060> down<01:28:12.179> and<01:28:12.360> call<01:28:12.540> it<01:28:12.719> an<01:28:12.840> extension<01:28:13.199> node 01:28:13.490 --> 01:28:13.500 align:start position:0% it down and call it an extension node 01:28:13.500 --> 01:28:15.709 align:start position:0% it down and call it an extension node but<01:28:13.800> here<01:28:14.520> where<01:28:14.699> there's<01:28:14.880> like<01:28:15.120> two<01:28:15.360> in<01:28:15.600> that 01:28:15.709 --> 01:28:15.719 align:start position:0% but here where there's like two in that 01:28:15.719 --> 01:28:17.570 align:start position:0% but here where there's like two in that array<01:28:16.020> you<01:28:16.260> just<01:28:16.440> automatically<01:28:16.980> have<01:28:17.280> the 01:28:17.570 --> 01:28:17.580 align:start position:0% array you just automatically have the 01:28:17.580 --> 01:28:18.950 align:start position:0% array you just automatically have the rest 01:28:18.950 --> 01:28:18.960 align:start position:0% rest 01:28:18.960 --> 01:28:24.229 align:start position:0% rest rest<01:28:19.560> of<01:28:19.800> its<01:28:20.100> siblings<01:28:20.520> are<01:28:21.060> empty<01:28:21.540> buffers 01:28:24.229 --> 01:28:24.239 align:start position:0% 01:28:24.239 --> 01:28:26.510 align:start position:0% um and<01:28:24.659> like<01:28:24.780> I<01:28:24.960> said<01:28:25.020> if<01:28:25.199> there's<01:28:25.440> only<01:28:25.679> one 01:28:26.510 --> 01:28:26.520 align:start position:0% um and like I said if there's only one 01:28:26.520 --> 01:28:28.850 align:start position:0% um and like I said if there's only one child<01:28:27.060> to<01:28:27.360> that<01:28:27.540> parent<01:28:27.719> we<01:28:28.080> can<01:28:28.260> collapse<01:28:28.739> it 01:28:28.850 --> 01:28:28.860 align:start position:0% child to that parent we can collapse it 01:28:28.860 --> 01:28:30.830 align:start position:0% child to that parent we can collapse it back<01:28:28.980> up<01:28:29.159> if<01:28:29.460> there's<01:28:30.000> at<01:28:30.179> least<01:28:30.300> two<01:28:30.540> then 01:28:30.830 --> 01:28:30.840 align:start position:0% back up if there's at least two then 01:28:30.840 --> 01:28:33.470 align:start position:0% back up if there's at least two then you're<01:28:31.080> going<01:28:31.320> to<01:28:31.500> have<01:28:31.620> an<01:28:31.800> array<01:28:32.040> of<01:28:32.219> 16. 01:28:33.470 --> 01:28:33.480 align:start position:0% you're going to have an array of 16. 01:28:33.480 --> 01:28:34.430 align:start position:0% you're going to have an array of 16. um 01:28:34.430 --> 01:28:34.440 align:start position:0% um 01:28:34.440 --> 01:28:37.129 align:start position:0% um regardless<01:28:35.159> of<01:28:35.340> how<01:28:35.580> many<01:28:35.699> actually<01:28:36.060> have 01:28:37.129 --> 01:28:37.139 align:start position:0% regardless of how many actually have 01:28:37.139 --> 01:28:40.250 align:start position:0% regardless of how many actually have actually<01:28:37.560> have<01:28:37.920> a<01:28:38.219> leaf 01:28:40.250 --> 01:28:40.260 align:start position:0% actually have a leaf 01:28:40.260 --> 01:28:42.890 align:start position:0% actually have a leaf yep<01:28:40.860> yeah<01:28:41.460> absolutely 01:28:42.890 --> 01:28:42.900 align:start position:0% yep yeah absolutely 01:28:42.900 --> 01:28:47.990 align:start position:0% yep yeah absolutely so<01:28:43.800> this<01:28:44.639> uh<01:28:45.440> clarifies<01:28:46.440> this<01:28:47.040> is<01:28:47.219> a<01:28:47.639> bit<01:28:47.760> like 01:28:47.990 --> 01:28:48.000 align:start position:0% so this uh clarifies this is a bit like 01:28:48.000 --> 01:28:50.390 align:start position:0% so this uh clarifies this is a bit like in<01:28:48.300> in<01:28:48.480> the<01:28:48.719> other<01:28:48.780> example<01:28:49.260> but<01:28:49.739> I<01:28:49.860> think<01:28:49.980> this 01:28:50.390 --> 01:28:50.400 align:start position:0% in in the other example but I think this 01:28:50.400 --> 01:28:53.689 align:start position:0% in in the other example but I think this clarifies<01:28:51.000> uh<01:28:52.080> you<01:28:52.620> know<01:28:52.739> what's<01:28:52.980> going<01:28:53.219> on<01:28:53.400> so 01:28:53.689 --> 01:28:53.699 align:start position:0% clarifies uh you know what's going on so 01:28:53.699 --> 01:28:55.610 align:start position:0% clarifies uh you know what's going on so it<01:28:53.880> might<01:28:54.239> look<01:28:54.780> a<01:28:54.960> bit<01:28:55.020> confusing<01:28:55.440> because 01:28:55.610 --> 01:28:55.620 align:start position:0% it might look a bit confusing because 01:28:55.620 --> 01:28:57.709 align:start position:0% it might look a bit confusing because we're<01:28:55.920> using<01:28:56.280> very<01:28:56.520> similar<01:28:56.820> keys<01:28:57.239> and<01:28:57.360> values 01:28:57.709 --> 01:28:57.719 align:start position:0% we're using very similar keys and values 01:28:57.719 --> 01:29:00.229 align:start position:0% we're using very similar keys and values so<01:28:58.440> this<01:28:58.679> is<01:28:58.920> actually<01:28:59.100> the<01:28:59.460> values<01:28:59.940> and 01:29:00.229 --> 01:29:00.239 align:start position:0% so this is actually the values and 01:29:00.239 --> 01:29:02.570 align:start position:0% so this is actually the values and they're<01:29:00.420> also<01:29:00.780> you<01:29:01.139> know<01:29:01.199> similar<01:29:01.739> but<01:29:02.400> we're 01:29:02.570 --> 01:29:02.580 align:start position:0% they're also you know similar but we're 01:29:02.580 --> 01:29:03.590 align:start position:0% they're also you know similar but we're not<01:29:02.760> really<01:29:02.880> concerned<01:29:03.239> with<01:29:03.420> this 01:29:03.590 --> 01:29:03.600 align:start position:0% not really concerned with this 01:29:03.600 --> 01:29:05.990 align:start position:0% not really concerned with this similarity<01:29:04.320> you<01:29:04.679> know<01:29:04.739> of<01:29:04.860> the<01:29:05.040> values<01:29:05.400> we're 01:29:05.990 --> 01:29:06.000 align:start position:0% similarity you know of the values we're 01:29:06.000 --> 01:29:08.450 align:start position:0% similarity you know of the values we're concerned<01:29:06.420> with<01:29:06.600> we<01:29:07.440> went<01:29:07.800> all<01:29:08.040> the<01:29:08.159> way<01:29:08.219> down 01:29:08.450 --> 01:29:08.460 align:start position:0% concerned with we went all the way down 01:29:08.460 --> 01:29:10.310 align:start position:0% concerned with we went all the way down to<01:29:08.880> a<01:29:09.120> branch<01:29:09.360> node 01:29:10.310 --> 01:29:10.320 align:start position:0% to a branch node 01:29:10.320 --> 01:29:13.430 align:start position:0% to a branch node we<01:29:10.980> had<01:29:11.159> two<01:29:11.520> paths<01:29:11.940> that<01:29:12.179> were<01:29:12.360> defined<01:29:12.780> and 01:29:13.430 --> 01:29:13.440 align:start position:0% we had two paths that were defined and 01:29:13.440 --> 01:29:16.729 align:start position:0% we had two paths that were defined and we<01:29:13.679> had<01:29:13.860> also<01:29:14.699> a<01:29:14.880> value<01:29:15.060> that<01:29:15.300> lived<01:29:15.600> there<01:29:15.739> so 01:29:16.729 --> 01:29:16.739 align:start position:0% we had also a value that lived there so 01:29:16.739 --> 01:29:19.129 align:start position:0% we had also a value that lived there so your<01:29:17.340> question<01:29:17.520> is<01:29:17.760> basically<01:29:18.000> well<01:29:18.239> why<01:29:18.540> is 01:29:19.129 --> 01:29:19.139 align:start position:0% your question is basically well why is 01:29:19.139 --> 01:29:21.830 align:start position:0% your question is basically well why is it<01:29:19.320> an<01:29:19.560> array<01:29:19.860> that<01:29:20.159> lives<01:29:20.340> there<01:29:20.460> right 01:29:21.830 --> 01:29:21.840 align:start position:0% it an array that lives there right 01:29:21.840 --> 01:29:23.870 align:start position:0% it an array that lives there right so<01:29:22.260> the<01:29:22.380> area<01:29:22.560> contains<01:29:23.100> the<01:29:23.219> two<01:29:23.400> pieces<01:29:23.699> of 01:29:23.870 --> 01:29:23.880 align:start position:0% so the area contains the two pieces of 01:29:23.880 --> 01:29:26.270 align:start position:0% so the area contains the two pieces of information<01:29:24.060> that<01:29:24.540> we<01:29:24.659> need<01:29:24.840> to<01:29:25.260> finally<01:29:25.980> like 01:29:26.270 --> 01:29:26.280 align:start position:0% information that we need to finally like 01:29:26.280 --> 01:29:28.970 align:start position:0% information that we need to finally like get<01:29:26.520> the<01:29:26.699> value<01:29:26.880> at<01:29:27.300> the<01:29:27.420> leaf<01:29:27.900> node<01:29:28.500> so<01:29:28.739> this 01:29:28.970 --> 01:29:28.980 align:start position:0% get the value at the leaf node so this 01:29:28.980 --> 01:29:31.490 align:start position:0% get the value at the leaf node so this is<01:29:29.159> pointing<01:29:29.580> you<01:29:30.420> know<01:29:30.540> to<01:29:30.719> an<01:29:30.840> old<01:29:31.020> and<01:29:31.320> it's 01:29:31.490 --> 01:29:31.500 align:start position:0% is pointing you know to an old and it's 01:29:31.500 --> 01:29:34.729 align:start position:0% is pointing you know to an old and it's telling<01:29:31.920> you<01:29:32.040> well<01:29:33.000> actually<01:29:33.620> the<01:29:34.620> the 01:29:34.729 --> 01:29:34.739 align:start position:0% telling you well actually the the 01:29:34.739 --> 01:29:36.890 align:start position:0% telling you well actually the the remaining<01:29:35.520> part<01:29:35.699> of<01:29:35.940> the<01:29:36.120> path 01:29:36.890 --> 01:29:36.900 align:start position:0% remaining part of the path 01:29:36.900 --> 01:29:40.610 align:start position:0% remaining part of the path is<01:29:37.320> going<01:29:37.440> to<01:29:37.560> be<01:29:37.679> 3<01:29:38.340> 0.<01:29:39.300> and<01:29:39.900> then<01:29:40.080> the 01:29:40.610 --> 01:29:40.620 align:start position:0% is going to be 3 0. and then the 01:29:40.620 --> 01:29:42.169 align:start position:0% is going to be 3 0. and then the remaining<01:29:40.980> part<01:29:41.159> of<01:29:41.280> the<01:29:41.400> path<01:29:41.580> is<01:29:41.940> going<01:29:42.060> to 01:29:42.169 --> 01:29:42.179 align:start position:0% remaining part of the path is going to 01:29:42.179 --> 01:29:44.930 align:start position:0% remaining part of the path is going to be<01:29:42.300> you<01:29:42.659> know<01:29:42.780> tree<01:29:43.139> one<01:29:43.380> and<01:29:43.800> then<01:29:43.980> the<01:29:44.699> value 01:29:44.930 --> 01:29:44.940 align:start position:0% be you know tree one and then the value 01:29:44.940 --> 01:29:47.270 align:start position:0% be you know tree one and then the value you're<01:29:45.239> going<01:29:45.420> to<01:29:45.500> retrieve<01:29:46.500> at<01:29:46.800> that<01:29:46.980> you 01:29:47.270 --> 01:29:47.280 align:start position:0% you're going to retrieve at that you 01:29:47.280 --> 01:29:49.850 align:start position:0% you're going to retrieve at that you know<01:29:47.340> and<01:29:47.580> end<01:29:47.940> point<01:29:48.179> is<01:29:48.900> going<01:29:49.080> to<01:29:49.199> be<01:29:49.260> you 01:29:49.850 --> 01:29:49.860 align:start position:0% know and end point is going to be you 01:29:49.860 --> 01:29:51.649 align:start position:0% know and end point is going to be you know<01:29:49.980> that<01:29:50.280> whole<01:29:50.460> thing<01:29:50.639> and<01:29:51.179> this<01:29:51.360> is<01:29:51.420> the 01:29:51.649 --> 01:29:51.659 align:start position:0% know that whole thing and this is the 01:29:51.659 --> 01:29:54.590 align:start position:0% know that whole thing and this is the thing<01:29:51.780> that<01:29:52.679> if<01:29:53.100> you<01:29:53.400> parse<01:29:54.060> it<01:29:54.179> to<01:29:54.300> a<01:29:54.420> string 01:29:54.590 --> 01:29:54.600 align:start position:0% thing that if you parse it to a string 01:29:54.600 --> 01:29:56.930 align:start position:0% thing that if you parse it to a string you<01:29:54.780> would<01:29:54.960> get<01:29:55.260> like<01:29:55.440> test<01:29:55.800> value<01:29:56.100> zero<01:29:56.760> and 01:29:56.930 --> 01:29:56.940 align:start position:0% you would get like test value zero and 01:29:56.940 --> 01:30:00.229 align:start position:0% you would get like test value zero and test<01:29:57.239> value<01:29:57.540> a<01:29:58.020> and<01:29:58.980> it's<01:29:59.400> the<01:29:59.639> reason<01:29:59.820> why 01:30:00.229 --> 01:30:00.239 align:start position:0% test value a and it's the reason why 01:30:00.239 --> 01:30:02.510 align:start position:0% test value a and it's the reason why when<01:30:00.719> we're 01:30:02.510 --> 01:30:02.520 align:start position:0% when we're 01:30:02.520 --> 01:30:04.070 align:start position:0% when we're um<01:30:02.580> trying<01:30:03.060> to<01:30:03.239> retrieve<01:30:03.659> you<01:30:03.840> know<01:30:03.900> the 01:30:04.070 --> 01:30:04.080 align:start position:0% um trying to retrieve you know the 01:30:04.080 --> 01:30:06.229 align:start position:0% um trying to retrieve you know the values<01:30:04.380> here<01:30:04.620> we<01:30:05.460> are 01:30:06.229 --> 01:30:06.239 align:start position:0% values here we are 01:30:06.239 --> 01:30:07.669 align:start position:0% values here we are you<01:30:06.600> know<01:30:06.719> taking<01:30:06.960> the<01:30:07.139> corresponding 01:30:07.669 --> 01:30:07.679 align:start position:0% you know taking the corresponding 01:30:07.679 --> 01:30:11.629 align:start position:0% you know taking the corresponding indexes<01:30:08.280> but<01:30:09.179> uh<01:30:09.659> then<01:30:09.840> taking<01:30:10.080> the<01:30:10.380> first<01:30:10.639> uh 01:30:11.629 --> 01:30:11.639 align:start position:0% indexes but uh then taking the first uh 01:30:11.639 --> 01:30:13.669 align:start position:0% indexes but uh then taking the first uh not<01:30:12.239> the<01:30:12.420> first<01:30:12.480> like<01:30:12.719> the<01:30:12.900> second<01:30:13.080> but<01:30:13.320> index 01:30:13.669 --> 01:30:13.679 align:start position:0% not the first like the second but index 01:30:13.679 --> 01:30:14.930 align:start position:0% not the first like the second but index number<01:30:13.860> one 01:30:14.930 --> 01:30:14.940 align:start position:0% number one 01:30:14.940 --> 01:30:18.290 align:start position:0% number one this<01:30:15.659> this<01:30:16.080> is<01:30:16.260> exactly<01:30:16.679> that's<01:30:17.040> the<01:30:17.280> value 01:30:18.290 --> 01:30:18.300 align:start position:0% this this is exactly that's the value 01:30:18.300 --> 01:30:20.870 align:start position:0% this this is exactly that's the value now<01:30:18.780> we're<01:30:19.260> working<01:30:19.679> with<01:30:19.980> like<01:30:20.219> fairly<01:30:20.639> small 01:30:20.870 --> 01:30:20.880 align:start position:0% now we're working with like fairly small 01:30:20.880 --> 01:30:23.810 align:start position:0% now we're working with like fairly small values<01:30:21.480> so<01:30:22.139> the<01:30:22.320> values<01:30:22.679> are<01:30:22.980> directly<01:30:23.520> inside 01:30:23.810 --> 01:30:23.820 align:start position:0% values so the values are directly inside 01:30:23.820 --> 01:30:26.450 align:start position:0% values so the values are directly inside of<01:30:24.120> the<01:30:24.239> tree<01:30:24.360> if<01:30:24.960> you<01:30:25.139> had<01:30:25.320> very<01:30:25.739> large<01:30:25.920> values 01:30:26.450 --> 01:30:26.460 align:start position:0% of the tree if you had very large values 01:30:26.460 --> 01:30:29.450 align:start position:0% of the tree if you had very large values it<01:30:26.820> would<01:30:27.179> Point<01:30:27.420> like<01:30:27.840> back<01:30:28.260> to<01:30:28.440> another<01:30:28.679> uh 01:30:29.450 --> 01:30:29.460 align:start position:0% it would Point like back to another uh 01:30:29.460 --> 01:30:31.610 align:start position:0% it would Point like back to another uh node<01:30:29.820> that<01:30:30.300> would<01:30:30.480> have<01:30:30.600> an<01:30:30.780> encoding<01:30:31.260> of<01:30:31.440> the 01:30:31.610 --> 01:30:31.620 align:start position:0% node that would have an encoding of the 01:30:31.620 --> 01:30:33.649 align:start position:0% node that would have an encoding of the of<01:30:31.980> the<01:30:32.219> value 01:30:33.649 --> 01:30:33.659 align:start position:0% of the value 01:30:33.659 --> 01:30:36.470 align:start position:0% of the value that<01:30:34.080> will<01:30:34.260> actually 01:30:36.470 --> 01:30:36.480 align:start position:0% 01:30:36.480 --> 01:30:38.629 align:start position:0% yeah 01:30:38.629 --> 01:30:38.639 align:start position:0% yeah 01:30:38.639 --> 01:30:40.669 align:start position:0% yeah well<01:30:39.239> at<01:30:39.300> that<01:30:39.480> point<01:30:39.540> it<01:30:39.780> would<01:30:39.960> be<01:30:40.080> like<01:30:40.320> the 01:30:40.669 --> 01:30:40.679 align:start position:0% well at that point it would be like the 01:30:40.679 --> 01:30:43.430 align:start position:0% well at that point it would be like the end<01:30:41.040> node<01:30:41.400> so<01:30:41.880> it<01:30:42.000> would<01:30:42.179> only<01:30:42.300> be<01:30:42.540> a<01:30:42.780> leaf<01:30:43.080> so 01:30:43.430 --> 01:30:43.440 align:start position:0% end node so it would only be a leaf so 01:30:43.440 --> 01:30:45.530 align:start position:0% end node so it would only be a leaf so all<01:30:43.739> the<01:30:43.920> leaf<01:30:44.159> contains<01:30:44.580> is<01:30:44.880> the<01:30:45.179> the<01:30:45.360> the 01:30:45.530 --> 01:30:45.540 align:start position:0% all the leaf contains is the the the 01:30:45.540 --> 01:30:48.050 align:start position:0% all the leaf contains is the the the last<01:30:46.260> remaining<01:30:46.739> part<01:30:46.920> of<01:30:47.040> the<01:30:47.159> path<01:30:47.340> that<01:30:47.880> was 01:30:48.050 --> 01:30:48.060 align:start position:0% last remaining part of the path that was 01:30:48.060 --> 01:31:15.110 align:start position:0% last remaining part of the path that was that<01:30:48.540> led<01:30:48.840> there<01:30:49.020> and<01:30:49.860> then<01:30:50.100> the<01:30:51.000> full<01:30:51.360> value 01:31:15.110 --> 01:31:15.120 align:start position:0% 01:31:15.120 --> 01:31:17.270 align:start position:0% and<01:31:15.540> then<01:31:15.659> yeah<01:31:15.960> that'll<01:31:16.440> be<01:31:16.560> the<01:31:16.739> root<01:31:17.040> of 01:31:17.270 --> 01:31:17.280 align:start position:0% and then yeah that'll be the root of 01:31:17.280 --> 01:31:20.510 align:start position:0% and then yeah that'll be the root of yeah<01:31:17.940> yeah<01:31:18.179> let's<01:31:18.780> do<01:31:18.960> that<01:31:19.139> actually<01:31:19.380> so<01:31:20.340> we 01:31:20.510 --> 01:31:20.520 align:start position:0% yeah yeah let's do that actually so we 01:31:20.520 --> 01:31:21.350 align:start position:0% yeah yeah let's do that actually so we can 01:31:21.350 --> 01:31:21.360 align:start position:0% can 01:31:21.360 --> 01:31:24.590 align:start position:0% can we're<01:31:21.840> gonna<01:31:21.960> create<01:31:22.560> uh<01:31:23.400> so<01:31:24.120> what<01:31:24.300> would<01:31:24.420> you 01:31:24.590 --> 01:31:24.600 align:start position:0% we're gonna create uh so what would you 01:31:24.600 --> 01:31:27.530 align:start position:0% we're gonna create uh so what would you suggest<01:31:24.840> this<01:31:25.080> key<01:31:25.440> one 01:31:27.530 --> 01:31:27.540 align:start position:0% suggest this key one 01:31:27.540 --> 01:31:28.310 align:start position:0% suggest this key one yeah 01:31:28.310 --> 01:31:28.320 align:start position:0% yeah 01:31:28.320 --> 01:31:29.810 align:start position:0% yeah let's<01:31:28.679> do<01:31:28.860> that<01:31:28.980> it's<01:31:29.159> going<01:31:29.340> to<01:31:29.400> be<01:31:29.520> test 01:31:29.810 --> 01:31:29.820 align:start position:0% let's do that it's going to be test 01:31:29.820 --> 01:31:31.970 align:start position:0% let's do that it's going to be test value<01:31:30.120> you<01:31:30.780> know<01:31:30.900> I<01:31:31.320> want<01:31:31.500> as<01:31:31.620> well<01:31:31.739> and 01:31:31.970 --> 01:31:31.980 align:start position:0% value you know I want as well and 01:31:31.980 --> 01:31:37.310 align:start position:0% value you know I want as well and actually<01:31:32.219> let<01:31:32.580> me 01:31:37.310 --> 01:31:37.320 align:start position:0% 01:31:37.320 --> 01:31:42.590 align:start position:0% put<01:31:37.800> like<01:31:38.159> some 01:31:42.590 --> 01:31:42.600 align:start position:0% 01:31:42.600 --> 01:31:44.629 align:start position:0% fairly<01:31:43.440> like<01:31:43.620> different<01:31:43.800> values<01:31:44.280> so<01:31:44.460> that 01:31:44.629 --> 01:31:44.639 align:start position:0% fairly like different values so that 01:31:44.639 --> 01:31:46.610 align:start position:0% fairly like different values so that we're<01:31:44.760> not<01:31:44.940> confused<01:31:45.360> by<01:31:45.600> the<01:31:45.780> similarity<01:31:46.260> of 01:31:46.610 --> 01:31:46.620 align:start position:0% we're not confused by the similarity of 01:31:46.620 --> 01:31:48.110 align:start position:0% we're not confused by the similarity of the<01:31:46.739> values<01:31:47.100> themselves<01:31:47.400> I<01:31:47.580> think<01:31:47.699> that<01:31:47.880> the 01:31:48.110 --> 01:31:48.120 align:start position:0% the values themselves I think that the 01:31:48.120 --> 01:31:49.910 align:start position:0% the values themselves I think that the values<01:31:48.600> themselves<01:31:49.020> don't 01:31:49.910 --> 01:31:49.920 align:start position:0% values themselves don't 01:31:49.920 --> 01:31:52.430 align:start position:0% values themselves don't determine<01:31:50.639> where<01:31:50.820> it<01:31:51.000> is<01:31:51.120> in<01:31:51.239> the<01:31:51.360> tree<01:31:51.480> yeah 01:31:52.430 --> 01:31:52.440 align:start position:0% determine where it is in the tree yeah 01:31:52.440 --> 01:31:55.430 align:start position:0% determine where it is in the tree yeah so<01:31:53.100> we're<01:31:53.460> gonna<01:31:53.639> run<01:31:54.239> that<01:31:54.480> again 01:31:55.430 --> 01:31:55.440 align:start position:0% so we're gonna run that again 01:31:55.440 --> 01:31:56.930 align:start position:0% so we're gonna run that again and<01:31:55.800> we're<01:31:55.920> gonna<01:31:56.100> all<01:31:56.639> that<01:31:56.760> we're 01:31:56.930 --> 01:31:56.940 align:start position:0% and we're gonna all that we're 01:31:56.940 --> 01:31:58.970 align:start position:0% and we're gonna all that we're interested<01:31:57.360> in<01:31:57.480> at<01:31:57.719> the<01:31:57.900> moment<01:31:58.020> for<01:31:58.440> you<01:31:58.860> know 01:31:58.970 --> 01:31:58.980 align:start position:0% interested in at the moment for you know 01:31:58.980 --> 01:32:00.649 align:start position:0% interested in at the moment for you know this<01:31:59.159> example<01:31:59.460> you've<01:31:59.820> suggested<01:32:00.300> is<01:32:00.480> that 01:32:00.649 --> 01:32:00.659 align:start position:0% this example you've suggested is that 01:32:00.659 --> 01:32:02.270 align:start position:0% this example you've suggested is that the<01:32:00.780> branch<01:32:01.139> note<01:32:01.380> like<01:32:01.620> what<01:32:01.860> does<01:32:01.980> it<01:32:02.100> look 01:32:02.270 --> 01:32:02.280 align:start position:0% the branch note like what does it look 01:32:02.280 --> 01:32:04.070 align:start position:0% the branch note like what does it look like<01:32:02.400> at<01:32:02.580> that<01:32:02.760> point<01:32:02.940> and<01:32:03.659> then<01:32:03.780> it's<01:32:03.900> going 01:32:04.070 --> 01:32:04.080 align:start position:0% like at that point and then it's going 01:32:04.080 --> 01:32:05.689 align:start position:0% like at that point and then it's going to<01:32:04.199> have<01:32:04.320> a<01:32:04.440> child<01:32:04.560> that's<01:32:04.920> also<01:32:05.280> going<01:32:05.460> to<01:32:05.639> be 01:32:05.689 --> 01:32:05.699 align:start position:0% to have a child that's also going to be 01:32:05.699 --> 01:32:07.850 align:start position:0% to have a child that's also going to be a<01:32:06.360> branched<01:32:06.840> out<01:32:06.960> right<01:32:07.320> that's<01:32:07.500> what<01:32:07.679> we 01:32:07.850 --> 01:32:07.860 align:start position:0% a branched out right that's what we 01:32:07.860 --> 01:32:10.250 align:start position:0% a branched out right that's what we would<01:32:08.040> you<01:32:08.400> know<01:32:08.520> expect 01:32:10.250 --> 01:32:10.260 align:start position:0% would you know expect 01:32:10.260 --> 01:32:13.129 align:start position:0% would you know expect so<01:32:10.739> let's<01:32:10.920> try<01:32:11.219> I<01:32:11.940> need<01:32:12.300> to<01:32:12.480> save<01:32:12.659> it<01:32:12.900> first 01:32:13.129 --> 01:32:13.139 align:start position:0% so let's try I need to save it first 01:32:13.139 --> 01:32:18.110 align:start position:0% so let's try I need to save it first let's<01:32:13.620> try<01:32:13.860> running<01:32:14.280> that 01:32:18.110 --> 01:32:18.120 align:start position:0% 01:32:18.120 --> 01:32:19.430 align:start position:0% all<01:32:18.480> right 01:32:19.430 --> 01:32:19.440 align:start position:0% all right 01:32:19.440 --> 01:32:21.890 align:start position:0% all right so<01:32:19.800> what<01:32:19.920> we<01:32:20.100> see<01:32:20.280> is<01:32:20.460> it's<01:32:20.760> actually<01:32:21.360> quite 01:32:21.890 --> 01:32:21.900 align:start position:0% so what we see is it's actually quite 01:32:21.900 --> 01:32:24.169 align:start position:0% so what we see is it's actually quite similar<01:32:22.620> to<01:32:22.920> what<01:32:23.040> it<01:32:23.159> was<01:32:23.280> before<01:32:23.520> but 01:32:24.169 --> 01:32:24.179 align:start position:0% similar to what it was before but 01:32:24.179 --> 01:32:26.750 align:start position:0% similar to what it was before but instead<01:32:24.480> of<01:32:24.600> getting<01:32:24.840> an<01:32:25.199> array 01:32:26.750 --> 01:32:26.760 align:start position:0% instead of getting an array 01:32:26.760 --> 01:32:30.470 align:start position:0% instead of getting an array we're<01:32:27.179> getting<01:32:27.480> a<01:32:28.080> larger<01:32:28.500> larger<01:32:29.219> buffer 01:32:30.470 --> 01:32:30.480 align:start position:0% we're getting a larger larger buffer 01:32:30.480 --> 01:32:32.810 align:start position:0% we're getting a larger larger buffer so<01:32:30.900> what<01:32:31.020> is<01:32:31.199> that<01:32:31.320> larger<01:32:31.560> browser<01:32:32.040> that 01:32:32.810 --> 01:32:32.820 align:start position:0% so what is that larger browser that 01:32:32.820 --> 01:32:36.530 align:start position:0% so what is that larger browser that larger<01:32:33.120> buffer<01:32:33.620> is<01:32:34.620> uh 01:32:36.530 --> 01:32:36.540 align:start position:0% larger buffer is uh 01:32:36.540 --> 01:32:38.330 align:start position:0% larger buffer is uh now<01:32:36.900> there's<01:32:37.199> two<01:32:37.440> kinds<01:32:37.679> of<01:32:37.739> keys<01:32:37.980> in<01:32:38.100> Myrtle 01:32:38.330 --> 01:32:38.340 align:start position:0% now there's two kinds of keys in Myrtle 01:32:38.340 --> 01:32:40.910 align:start position:0% now there's two kinds of keys in Myrtle Beach<01:32:38.520> trees<01:32:38.940> that's<01:32:39.420> just<01:32:39.719> a<01:32:40.020> hash<01:32:40.260> that 01:32:40.910 --> 01:32:40.920 align:start position:0% Beach trees that's just a hash that 01:32:40.920 --> 01:32:42.950 align:start position:0% Beach trees that's just a hash that points<01:32:41.219> to<01:32:41.340> a<01:32:41.580> different<01:32:41.699> node<01:32:42.120> right<01:32:42.360> so<01:32:42.840> it's 01:32:42.950 --> 01:32:42.960 align:start position:0% points to a different node right so it's 01:32:42.960 --> 01:32:45.050 align:start position:0% points to a different node right so it's not<01:32:43.139> about<01:32:43.320> you<01:32:43.739> know<01:32:43.860> path<01:32:44.159> path<01:32:44.699> is<01:32:44.880> still 01:32:45.050 --> 01:32:45.060 align:start position:0% not about you know path path is still 01:32:45.060 --> 01:32:47.450 align:start position:0% not about you know path path is still like<01:32:45.300> path<01:32:45.719> you<01:32:45.960> know<01:32:46.080> number<01:32:46.260> three<01:32:46.560> but<01:32:47.219> to 01:32:47.450 --> 01:32:47.460 align:start position:0% like path you know number three but to 01:32:47.460 --> 01:32:49.550 align:start position:0% like path you know number three but to know<01:32:47.639> like<01:32:47.940> what's<01:32:48.420> the<01:32:48.659> hash<01:32:48.780> of<01:32:49.020> that<01:32:49.260> other 01:32:49.550 --> 01:32:49.560 align:start position:0% know like what's the hash of that other 01:32:49.560 --> 01:32:52.370 align:start position:0% know like what's the hash of that other node<01:32:49.920> that<01:32:50.280> we're<01:32:50.400> trying<01:32:50.699> to<01:32:51.000> retrieve<01:32:51.600> this 01:32:52.370 --> 01:32:52.380 align:start position:0% node that we're trying to retrieve this 01:32:52.380 --> 01:32:53.870 align:start position:0% node that we're trying to retrieve this is<01:32:52.500> going<01:32:52.620> to<01:32:52.679> be<01:32:52.800> that<01:32:52.920> so<01:32:53.159> that's<01:32:53.400> just<01:32:53.639> a 01:32:53.870 --> 01:32:53.880 align:start position:0% is going to be that so that's just a 01:32:53.880 --> 01:32:56.590 align:start position:0% is going to be that so that's just a hash<01:32:54.239> of<01:32:54.659> the<01:32:54.900> the<01:32:55.500> the 01:32:56.590 --> 01:32:56.600 align:start position:0% hash of the the the 01:32:56.600 --> 01:32:59.689 align:start position:0% hash of the the the of<01:32:57.600> the<01:32:57.780> the<01:32:57.840> child<01:32:58.560> node<01:32:58.980> that<01:32:59.400> is<01:32:59.520> going<01:32:59.639> to 01:32:59.689 --> 01:32:59.699 align:start position:0% of the the child node that is going to 01:32:59.699 --> 01:33:02.390 align:start position:0% of the the child node that is going to be<01:32:59.760> the<01:32:59.880> one<01:33:00.060> that<01:33:00.360> contains<01:33:00.900> you<01:33:01.500> know<01:33:01.560> zero 01:33:02.390 --> 01:33:02.400 align:start position:0% be the one that contains you know zero 01:33:02.400 --> 01:33:05.330 align:start position:0% be the one that contains you know zero uh<01:33:03.239> what<01:33:03.480> was<01:33:03.719> it<01:33:03.840> like<01:33:03.960> zero<01:33:04.320> and<01:33:04.380> zero<01:33:04.800> zero 01:33:05.330 --> 01:33:05.340 align:start position:0% uh what was it like zero and zero zero 01:33:05.340 --> 01:33:06.770 align:start position:0% uh what was it like zero and zero zero one<01:33:05.400> right 01:33:06.770 --> 01:33:06.780 align:start position:0% one right 01:33:06.780 --> 01:33:14.209 align:start position:0% one right so<01:33:07.320> now 01:33:14.209 --> 01:33:14.219 align:start position:0% 01:33:14.219 --> 01:33:18.830 align:start position:0% yeah<01:33:14.760> yeah 01:33:18.830 --> 01:33:18.840 align:start position:0% 01:33:18.840 --> 01:33:22.790 align:start position:0% so<01:33:19.440> let's<01:33:19.620> see<01:33:19.860> how<01:33:20.040> we<01:33:20.159> can<01:33:20.280> go<01:33:20.520> about 01:33:22.790 --> 01:33:22.800 align:start position:0% 01:33:22.800 --> 01:33:25.850 align:start position:0% what<01:33:23.100> I'll<01:33:23.460> do<01:33:23.699> next<01:33:23.880> is<01:33:24.239> look<01:33:24.900> at<01:33:25.080> the<01:33:25.320> path<01:33:25.500> at 01:33:25.850 --> 01:33:25.860 align:start position:0% what I'll do next is look at the path at 01:33:25.860 --> 01:33:26.930 align:start position:0% what I'll do next is look at the path at test<01:33:26.100> key 01:33:26.930 --> 01:33:26.940 align:start position:0% test key 01:33:26.940 --> 01:33:28.850 align:start position:0% test key zero<01:33:27.600> right<01:33:27.780> and<01:33:28.260> we're<01:33:28.380> going<01:33:28.500> to<01:33:28.560> look<01:33:28.679> at 01:33:28.850 --> 01:33:28.860 align:start position:0% zero right and we're going to look at 01:33:28.860 --> 01:33:31.010 align:start position:0% zero right and we're going to look at what<01:33:29.040> you<01:33:29.520> know<01:33:29.580> that<01:33:29.880> actual<01:33:30.179> node 01:33:31.010 --> 01:33:31.020 align:start position:0% what you know that actual node 01:33:31.020 --> 01:33:45.290 align:start position:0% what you know that actual node looks<01:33:31.860> like<01:33:31.980> I<01:33:32.760> can<01:33:32.940> also<01:33:33.300> remove<01:33:33.900> that 01:33:45.290 --> 01:33:45.300 align:start position:0% 01:33:45.300 --> 01:33:48.430 align:start position:0% all<01:33:45.600> right 01:33:48.430 --> 01:33:48.440 align:start position:0% 01:33:48.440 --> 01:33:51.830 align:start position:0% so<01:33:49.440> what<01:33:49.620> do<01:33:49.860> we<01:33:50.100> have<01:33:50.820> here<01:33:51.120> what<01:33:51.480> are<01:33:51.659> my 01:33:51.830 --> 01:33:51.840 align:start position:0% so what do we have here what are my 01:33:51.840 --> 01:33:57.890 align:start position:0% so what do we have here what are my logging 01:33:57.890 --> 01:33:57.900 align:start position:0% 01:33:57.900 --> 01:33:59.930 align:start position:0% okay 01:33:59.930 --> 01:33:59.940 align:start position:0% okay 01:33:59.940 --> 01:34:02.689 align:start position:0% okay so<01:34:00.540> if<01:34:00.719> we<01:34:00.840> look<01:34:01.020> at<01:34:01.199> those<01:34:01.380> keys<01:34:01.739> you<01:34:02.280> have<01:34:02.460> a 01:34:02.689 --> 01:34:02.699 align:start position:0% so if we look at those keys you have a 01:34:02.699 --> 01:34:05.629 align:start position:0% so if we look at those keys you have a common<01:34:02.940> path<01:34:03.239> that<01:34:03.900> is<01:34:04.020> test<01:34:04.199> key<01:34:04.500> zero<01:34:04.920> and 01:34:05.629 --> 01:34:05.639 align:start position:0% common path that is test key zero and 01:34:05.639 --> 01:34:07.790 align:start position:0% common path that is test key zero and then<01:34:05.760> you<01:34:06.000> have<01:34:06.179> a<01:34:06.540> slightly<01:34:06.960> like<01:34:07.380> longer 01:34:07.790 --> 01:34:07.800 align:start position:0% then you have a slightly like longer 01:34:07.800 --> 01:34:10.610 align:start position:0% then you have a slightly like longer path<01:34:07.980> that<01:34:08.340> is<01:34:08.520> that's<01:34:08.880> q1<01:34:09.780> so<01:34:10.139> what<01:34:10.260> we<01:34:10.440> should 01:34:10.610 --> 01:34:10.620 align:start position:0% path that is that's q1 so what we should 01:34:10.620 --> 01:34:13.910 align:start position:0% path that is that's q1 so what we should expect<01:34:10.800> again<01:34:11.580> is<01:34:12.480> a<01:34:12.840> branch<01:34:13.080> node<01:34:13.380> at<01:34:13.800> that 01:34:13.910 --> 01:34:13.920 align:start position:0% expect again is a branch node at that 01:34:13.920 --> 01:34:15.890 align:start position:0% expect again is a branch node at that point<01:34:14.100> it's<01:34:15.000> going<01:34:15.239> to<01:34:15.360> contain<01:34:15.540> the<01:34:15.719> value 01:34:15.890 --> 01:34:15.900 align:start position:0% point it's going to contain the value 01:34:15.900 --> 01:34:17.870 align:start position:0% point it's going to contain the value itself<01:34:16.260> because<01:34:16.679> test<01:34:16.920> key<01:34:17.219> zero<01:34:17.580> is<01:34:17.699> actually 01:34:17.870 --> 01:34:17.880 align:start position:0% itself because test key zero is actually 01:34:17.880 --> 01:34:19.610 align:start position:0% itself because test key zero is actually defined<01:34:18.420> you<01:34:18.600> know<01:34:18.719> as<01:34:18.840> a<01:34:19.020> valid<01:34:19.260> key<01:34:19.440> that 01:34:19.610 --> 01:34:19.620 align:start position:0% defined you know as a valid key that 01:34:19.620 --> 01:34:21.649 align:start position:0% defined you know as a valid key that contains<01:34:19.920> a<01:34:19.980> value<01:34:20.159> but<01:34:20.880> it's<01:34:21.000> also<01:34:21.300> going<01:34:21.420> to 01:34:21.649 --> 01:34:21.659 align:start position:0% contains a value but it's also going to 01:34:21.659 --> 01:34:25.490 align:start position:0% contains a value but it's also going to continue<01:34:21.980> at<01:34:22.980> one<01:34:23.460> and<01:34:24.420> now<01:34:24.960> obviously<01:34:25.320> we're 01:34:25.490 --> 01:34:25.500 align:start position:0% continue at one and now obviously we're 01:34:25.500 --> 01:34:27.530 align:start position:0% continue at one and now obviously we're dealing<01:34:25.800> with<01:34:26.040> like<01:34:26.280> text<01:34:26.699> conversions<01:34:27.360> of 01:34:27.530 --> 01:34:27.540 align:start position:0% dealing with like text conversions of 01:34:27.540 --> 01:34:28.669 align:start position:0% dealing with like text conversions of this<01:34:27.659> so<01:34:27.780> it's<01:34:27.900> not<01:34:28.080> going<01:34:28.139> to<01:34:28.199> be<01:34:28.320> at<01:34:28.500> the 01:34:28.669 --> 01:34:28.679 align:start position:0% this so it's not going to be at the 01:34:28.679 --> 01:34:30.530 align:start position:0% this so it's not going to be at the actual<01:34:28.860> index<01:34:29.219> one<01:34:29.400> it's<01:34:29.580> going<01:34:29.760> to<01:34:29.820> be<01:34:29.880> at<01:34:30.360> a 01:34:30.530 --> 01:34:30.540 align:start position:0% actual index one it's going to be at a 01:34:30.540 --> 01:34:33.530 align:start position:0% actual index one it's going to be at a different<01:34:30.780> index<01:34:31.320> but<01:34:32.219> where<01:34:32.520> we<01:34:32.940> do<01:34:33.060> see<01:34:33.239> that 01:34:33.530 --> 01:34:33.540 align:start position:0% different index but where we do see that 01:34:33.540 --> 01:34:38.209 align:start position:0% different index but where we do see that there's<01:34:34.159> uh<01:34:35.179> exactly<01:34:36.179> one<01:34:36.860> valid<01:34:37.860> you<01:34:38.100> know 01:34:38.209 --> 01:34:38.219 align:start position:0% there's uh exactly one valid you know 01:34:38.219 --> 01:34:40.790 align:start position:0% there's uh exactly one valid you know branch<01:34:38.520> that<01:34:38.760> points<01:34:39.120> to<01:34:39.239> uh<01:34:39.719> another<01:34:40.320> node 01:34:40.790 --> 01:34:40.800 align:start position:0% branch that points to uh another node 01:34:40.800 --> 01:34:43.490 align:start position:0% branch that points to uh another node and<01:34:41.580> then<01:34:41.699> there's<01:34:42.000> an<01:34:42.300> actual<01:34:42.659> value<01:34:43.080> here 01:34:43.490 --> 01:34:43.500 align:start position:0% and then there's an actual value here 01:34:43.500 --> 01:34:46.729 align:start position:0% and then there's an actual value here and<01:34:44.219> if<01:34:44.400> we<01:34:44.639> were<01:34:44.880> to<01:34:45.060> uh<01:34:45.900> you<01:34:46.139> know<01:34:46.260> convert 01:34:46.729 --> 01:34:46.739 align:start position:0% and if we were to uh you know convert 01:34:46.739 --> 01:34:49.129 align:start position:0% and if we were to uh you know convert that<01:34:47.219> actual<01:34:47.520> value<01:34:47.760> to<01:34:48.000> a<01:34:48.179> string<01:34:48.420> we<01:34:49.020> would 01:34:49.129 --> 01:34:49.139 align:start position:0% that actual value to a string we would 01:34:49.139 --> 01:34:52.010 align:start position:0% that actual value to a string we would expect<01:34:49.320> to<01:34:49.620> get<01:34:49.800> back<01:34:50.040> uh<01:34:50.580> whatever<01:34:50.940> like<01:34:51.480> gar 01:34:52.010 --> 01:34:52.020 align:start position:0% expect to get back uh whatever like gar 01:34:52.020 --> 01:34:54.590 align:start position:0% expect to get back uh whatever like gar badge<01:34:52.620> I<01:34:52.800> I<01:34:52.920> typed<01:34:53.340> in<01:34:53.400> there<01:34:53.580> and<01:34:54.179> this<01:34:54.480> is 01:34:54.590 --> 01:34:54.600 align:start position:0% badge I I typed in there and this is 01:34:54.600 --> 01:34:57.470 align:start position:0% badge I I typed in there and this is actually<01:34:54.980> exactly<01:34:55.980> what<01:34:56.219> we<01:34:56.340> retrieve<01:34:56.820> here 01:34:57.470 --> 01:34:57.480 align:start position:0% actually exactly what we retrieve here 01:34:57.480 --> 01:35:03.410 align:start position:0% actually exactly what we retrieve here and<01:34:58.020> if<01:34:58.199> we<01:34:58.440> look<01:34:58.679> at<01:34:59.340> this<01:35:00.060> this<01:35:00.300> branch 01:35:03.410 --> 01:35:03.420 align:start position:0% 01:35:03.420 --> 01:35:05.330 align:start position:0% we're<01:35:03.840> going<01:35:04.020> to<01:35:04.080> try<01:35:04.199> to<01:35:04.380> retrieve<01:35:04.800> that<01:35:05.040> you 01:35:05.330 --> 01:35:05.340 align:start position:0% we're going to try to retrieve that you 01:35:05.340 --> 01:35:12.470 align:start position:0% we're going to try to retrieve that you know<01:35:05.400> number<01:35:05.940> three<01:35:06.239> thing<01:35:06.480> here 01:35:12.470 --> 01:35:12.480 align:start position:0% 01:35:12.480 --> 01:35:14.149 align:start position:0% I<01:35:12.840> can<01:35:13.020> just<01:35:13.139> do<01:35:13.320> it 01:35:14.149 --> 01:35:14.159 align:start position:0% I can just do it 01:35:14.159 --> 01:35:16.550 align:start position:0% I can just do it so<01:35:14.760> what's<01:35:15.179> the<01:35:15.480> index<01:35:15.780> of<01:35:15.960> this<01:35:16.139> it<01:35:16.320> looks 01:35:16.550 --> 01:35:16.560 align:start position:0% so what's the index of this it looks 01:35:16.560 --> 01:35:20.450 align:start position:0% so what's the index of this it looks like<01:35:16.679> okay<01:35:17.040> index<01:35:17.580> tree 01:35:20.450 --> 01:35:20.460 align:start position:0% 01:35:20.460 --> 01:35:24.050 align:start position:0% I<01:35:20.760> have<01:35:20.880> to<01:35:21.060> do<01:35:21.239> actually<01:35:21.540> branches<01:35:22.679> true<01:35:23.100> and 01:35:24.050 --> 01:35:24.060 align:start position:0% I have to do actually branches true and 01:35:24.060 --> 01:35:26.030 align:start position:0% I have to do actually branches true and then<01:35:24.239> this<01:35:24.600> would<01:35:24.719> be<01:35:24.840> the<01:35:25.020> remaining<01:35:25.800> part<01:35:25.920> of 01:35:26.030 --> 01:35:26.040 align:start position:0% then this would be the remaining part of 01:35:26.040 --> 01:35:27.890 align:start position:0% then this would be the remaining part of the<01:35:26.159> path<01:35:26.340> and<01:35:27.179> this<01:35:27.360> is<01:35:27.480> going<01:35:27.600> to<01:35:27.659> be<01:35:27.780> the 01:35:27.890 --> 01:35:27.900 align:start position:0% the path and this is going to be the 01:35:27.900 --> 01:35:30.470 align:start position:0% the path and this is going to be the value<01:35:28.080> so<01:35:28.440> if<01:35:28.620> we<01:35:28.800> do<01:35:28.980> the<01:35:29.580> string<01:35:29.940> we<01:35:30.360> should 01:35:30.470 --> 01:35:30.480 align:start position:0% value so if we do the string we should 01:35:30.480 --> 01:35:32.629 align:start position:0% value so if we do the string we should expect<01:35:30.659> to<01:35:30.900> retrieve<01:35:31.320> that<01:35:31.620> uh<01:35:31.920> number<01:35:32.400> three 01:35:32.629 --> 01:35:32.639 align:start position:0% expect to retrieve that uh number three 01:35:32.639 --> 01:35:34.910 align:start position:0% expect to retrieve that uh number three you<01:35:33.000> know<01:35:33.120> thing<01:35:33.300> that<01:35:33.600> we<01:35:33.719> had<01:35:33.960> above 01:35:34.910 --> 01:35:34.920 align:start position:0% you know thing that we had above 01:35:34.920 --> 01:35:39.110 align:start position:0% you know thing that we had above let's<01:35:35.520> see<01:35:35.820> if<01:35:36.300> that<01:35:36.480> works 01:35:39.110 --> 01:35:39.120 align:start position:0% 01:35:39.120 --> 01:35:42.050 align:start position:0% and<01:35:39.600> yeah<01:35:39.719> we're<01:35:40.020> getting<01:35:40.199> back<01:35:40.500> you<01:35:40.920> know 01:35:42.050 --> 01:35:42.060 align:start position:0% and yeah we're getting back you know 01:35:42.060 --> 01:35:44.689 align:start position:0% and yeah we're getting back you know number<01:35:42.360> three<01:35:42.719> uh<01:35:43.080> well<01:35:43.500> I<01:35:43.800> kind<01:35:43.920> of<01:35:44.100> messed 01:35:44.689 --> 01:35:44.699 align:start position:0% number three uh well I kind of messed 01:35:44.699 --> 01:35:46.010 align:start position:0% number three uh well I kind of messed this<01:35:44.760> up<01:35:44.940> I<01:35:45.179> should<01:35:45.300> have<01:35:45.480> come<01:35:45.600> into<01:35:45.719> this 01:35:46.010 --> 01:35:46.020 align:start position:0% this up I should have come into this 01:35:46.020 --> 01:36:05.750 align:start position:0% this up I should have come into this help 01:36:05.750 --> 01:36:05.760 align:start position:0% 01:36:05.760 --> 01:36:07.669 align:start position:0% s not<01:36:06.360> necessarily<01:36:06.780> this<01:36:07.139> is<01:36:07.260> just<01:36:07.440> because 01:36:07.669 --> 01:36:07.679 align:start position:0% s not necessarily this is just because 01:36:07.679 --> 01:36:12.110 align:start position:0% s not necessarily this is just because of<01:36:08.159> the<01:36:08.460> uh<01:36:08.940> the<01:36:09.659> actual<01:36:09.900> uh<01:36:10.560> ewts<01:36:11.460> so<01:36:11.820> it<01:36:11.940> put 01:36:12.110 --> 01:36:12.120 align:start position:0% of the uh the actual uh ewts so it put 01:36:12.120 --> 01:36:14.110 align:start position:0% of the uh the actual uh ewts so it put very<01:36:12.300> well<01:36:12.480> like<01:36:12.780> if<01:36:13.080> I 01:36:14.110 --> 01:36:14.120 align:start position:0% very well like if I 01:36:14.120 --> 01:36:18.169 align:start position:0% very well like if I choose<01:36:15.120> let's<01:36:15.659> say<01:36:15.840> I<01:36:15.960> do<01:36:16.020> two<01:36:16.199> here 01:36:18.169 --> 01:36:18.179 align:start position:0% choose let's say I do two here 01:36:18.179 --> 01:36:24.950 align:start position:0% choose let's say I do two here let<01:36:18.659> me<01:36:18.780> go<01:36:19.080> back<01:36:19.320> and<01:36:19.560> just<01:36:19.860> logging 01:36:24.950 --> 01:36:24.960 align:start position:0% 01:36:24.960 --> 01:36:43.090 align:start position:0% I<01:36:25.320> don't<01:36:25.380> expect 01:36:43.090 --> 01:36:43.100 align:start position:0% 01:36:43.100 --> 01:36:49.550 align:start position:0% can<01:36:44.100> you<01:36:44.219> can<01:36:44.340> you<01:36:44.460> repeat<01:36:44.580> that 01:36:49.550 --> 01:36:49.560 align:start position:0% 01:36:49.560 --> 01:36:54.310 align:start position:0% being<01:36:50.100> displayed<01:36:50.840> and<01:36:51.840> you<01:36:51.960> have 01:36:54.310 --> 01:36:54.320 align:start position:0% 01:36:54.320 --> 01:36:56.270 align:start position:0% referring<01:36:55.320> to<01:36:55.380> the<01:36:55.620> branches<01:36:55.980> in<01:36:56.159> the 01:36:56.270 --> 01:36:56.280 align:start position:0% referring to the branches in the 01:36:56.280 --> 01:36:58.750 align:start position:0% referring to the branches in the terminal<01:36:56.580> right<01:36:56.820> like<01:36:57.120> we<01:36:57.480> have<01:36:57.780> buffer 01:36:58.750 --> 01:36:58.760 align:start position:0% terminal right like we have buffer 01:36:58.760 --> 01:37:02.990 align:start position:0% terminal right like we have buffer placeholders<01:36:59.760> and<01:37:00.480> the<01:37:01.440> value<01:37:01.620> of<01:37:02.340> the<01:37:02.520> key<01:37:02.639> is 01:37:02.990 --> 01:37:03.000 align:start position:0% placeholders and the value of the key is 01:37:03.000 --> 01:37:07.550 align:start position:0% placeholders and the value of the key is being<01:37:03.500> shown<01:37:04.500> as<01:37:04.980> 0<01:37:05.340> 1<01:37:05.820> 2<01:37:06.420> 3<01:37:06.780> on<01:37:07.260> the<01:37:07.380> third 01:37:07.550 --> 01:37:07.560 align:start position:0% being shown as 0 1 2 3 on the third 01:37:07.560 --> 01:37:10.430 align:start position:0% being shown as 0 1 2 3 on the third element<01:37:07.940> is<01:37:08.940> that<01:37:09.120> right 01:37:10.430 --> 01:37:10.440 align:start position:0% element is that right 01:37:10.440 --> 01:37:13.729 align:start position:0% element is that right yeah<01:37:10.920> so<01:37:11.520> in<01:37:11.760> that<01:37:11.940> scenario<01:37:12.440> the<01:37:13.440> total 01:37:13.729 --> 01:37:13.739 align:start position:0% yeah so in that scenario the total 01:37:13.739 --> 01:37:16.790 align:start position:0% yeah so in that scenario the total number<01:37:13.980> of<01:37:14.400> uh<01:37:15.000> buffer<01:37:15.719> placeholders<01:37:16.560> are 01:37:16.790 --> 01:37:16.800 align:start position:0% number of uh buffer placeholders are 01:37:16.800 --> 01:37:19.430 align:start position:0% number of uh buffer placeholders are fifteen<01:37:17.280> one<01:37:17.520> five<01:37:17.880> is<01:37:18.540> that<01:37:18.719> right 01:37:19.430 --> 01:37:19.440 align:start position:0% fifteen one five is that right 01:37:19.440 --> 01:37:23.810 align:start position:0% fifteen one five is that right uh<01:37:20.159> yeah<01:37:20.820> it's<01:37:21.000> actually<01:37:21.239> uh<01:37:22.199> 16.<01:37:22.860> we<01:37:23.340> have<01:37:23.520> 16 01:37:23.810 --> 01:37:23.820 align:start position:0% uh yeah it's actually uh 16. we have 16 01:37:23.820 --> 01:37:26.930 align:start position:0% uh yeah it's actually uh 16. we have 16 uh<01:37:24.360> elements<01:37:24.780> in<01:37:24.840> the<01:37:25.020> array<01:37:25.560> I<01:37:25.980> believe<01:37:26.159> it 01:37:26.930 --> 01:37:26.940 align:start position:0% uh elements in the array I believe it 01:37:26.940 --> 01:37:29.570 align:start position:0% uh elements in the array I believe it then<01:37:27.120> the<01:37:27.300> end<01:37:27.840> index<01:37:28.440> is<01:37:28.620> 15<01:37:28.980> but<01:37:29.219> it<01:37:29.340> starts 01:37:29.570 --> 01:37:29.580 align:start position:0% then the end index is 15 but it starts 01:37:29.580 --> 01:37:41.470 align:start position:0% then the end index is 15 but it starts at<01:37:29.639> zero<01:37:29.940> so<01:37:30.060> we<01:37:30.179> have<01:37:30.300> 16. 01:37:41.470 --> 01:37:41.480 align:start position:0% 01:37:41.480 --> 01:37:46.370 align:start position:0% [Music] 01:37:46.370 --> 01:37:46.380 align:start position:0% 01:37:46.380 --> 01:37:51.950 align:start position:0% the<01:37:47.040> next<01:37:48.000> bite 01:37:51.950 --> 01:37:51.960 align:start position:0% 01:37:51.960 --> 01:38:13.209 align:start position:0% got<01:37:52.679> it<01:37:52.860> thank<01:37:53.219> you 01:38:13.209 --> 01:38:13.219 align:start position:0% 01:38:13.219 --> 01:38:20.030 align:start position:0% can<01:38:14.219> we<01:38:14.520> oh<01:38:15.360> yeah<01:38:15.480> it<01:38:15.659> works 01:38:20.030 --> 01:38:20.040 align:start position:0% 01:38:20.040 --> 01:38:22.570 align:start position:0% okay<01:38:20.580> I<01:38:20.880> know<01:38:21.000> what<01:38:21.120> that<01:38:21.300> is 01:38:22.570 --> 01:38:22.580 align:start position:0% okay I know what that is 01:38:22.580 --> 01:38:25.729 align:start position:0% okay I know what that is so<01:38:23.580> zero 01:38:25.729 --> 01:38:25.739 align:start position:0% so zero 01:38:25.739 --> 01:38:28.610 align:start position:0% so zero is<01:38:26.400> actually<01:38:26.639> like<01:38:27.540> it's<01:38:27.780> encoded<01:38:28.260> as<01:38:28.380> like 01:38:28.610 --> 01:38:28.620 align:start position:0% is actually like it's encoded as like 01:38:28.620 --> 01:38:32.510 align:start position:0% is actually like it's encoded as like two<01:38:28.860> hexary<01:38:30.060> you<01:38:30.540> know<01:38:30.860> number<01:38:31.860> is<01:38:32.100> only<01:38:32.219> like 01:38:32.510 --> 01:38:32.520 align:start position:0% two hexary you know number is only like 01:38:32.520 --> 01:38:35.149 align:start position:0% two hexary you know number is only like not<01:38:32.880> a<01:38:33.060> like<01:38:33.360> a<01:38:33.540> single<01:38:33.780> one<01:38:33.900> so<01:38:34.679> we're<01:38:34.920> seeing 01:38:35.149 --> 01:38:35.159 align:start position:0% not a like a single one so we're seeing 01:38:35.159 --> 01:38:37.070 align:start position:0% not a like a single one so we're seeing tree<01:38:35.460> because<01:38:35.880> that's<01:38:36.239> the<01:38:36.480> like<01:38:36.719> second 01:38:37.070 --> 01:38:37.080 align:start position:0% tree because that's the like second 01:38:37.080 --> 01:38:40.910 align:start position:0% tree because that's the like second number<01:38:37.440> of<01:38:38.100> the<01:38:38.219> zero<01:38:38.639> at<01:38:39.300> which<01:38:39.480> point<01:38:39.719> uh<01:38:40.440> you 01:38:40.910 --> 01:38:40.920 align:start position:0% number of the zero at which point uh you 01:38:40.920 --> 01:38:42.890 align:start position:0% number of the zero at which point uh you know<01:38:40.980> we<01:38:41.219> have<01:38:41.340> a<01:38:41.639> value<01:38:41.940> like<01:38:42.300> directly<01:38:42.659> there 01:38:42.890 --> 01:38:42.900 align:start position:0% know we have a value like directly there 01:38:42.900 --> 01:38:45.169 align:start position:0% know we have a value like directly there but<01:38:43.199> we<01:38:43.380> have<01:38:43.560> we're<01:38:44.100> branching<01:38:44.699> out<01:38:44.820> so<01:38:45.000> I 01:38:45.169 --> 01:38:45.179 align:start position:0% but we have we're branching out so I 01:38:45.179 --> 01:38:47.810 align:start position:0% but we have we're branching out so I think<01:38:45.300> if<01:38:45.540> I<01:38:45.719> created 01:38:47.810 --> 01:38:47.820 align:start position:0% think if I created 01:38:47.820 --> 01:38:53.390 align:start position:0% think if I created like<01:38:48.420> another<01:38:48.659> one 01:38:53.390 --> 01:38:53.400 align:start position:0% 01:38:53.400 --> 01:38:55.850 align:start position:0% might<01:38:53.880> be<01:38:54.000> a<01:38:54.179> bit<01:38:54.239> tricky<01:38:54.600> to<01:38:54.900> actually<01:38:55.199> create 01:38:55.850 --> 01:38:55.860 align:start position:0% might be a bit tricky to actually create 01:38:55.860 --> 01:39:00.110 align:start position:0% might be a bit tricky to actually create all<01:38:56.400> the<01:38:56.520> cases<01:38:56.760> that<01:38:57.000> we'd<01:38:57.179> want 01:39:00.110 --> 01:39:00.120 align:start position:0% 01:39:00.120 --> 01:39:02.510 align:start position:0% we<01:39:00.840> might<01:39:00.960> end<01:39:01.199> up<01:39:01.320> with<01:39:01.560> the<01:39:01.800> same<01:39:01.980> sort<01:39:02.400> of 01:39:02.510 --> 01:39:02.520 align:start position:0% we might end up with the same sort of 01:39:02.520 --> 01:39:14.270 align:start position:0% we might end up with the same sort of issue 01:39:14.270 --> 01:39:14.280 align:start position:0% 01:39:14.280 --> 01:39:18.830 align:start position:0% yeah<01:39:14.760> so<01:39:15.060> here<01:39:15.480> we're<01:39:15.659> getting<01:39:15.840> again<01:39:16.139> uh 01:39:18.830 --> 01:39:18.840 align:start position:0% yeah so here we're getting again uh 01:39:18.840 --> 01:39:20.510 align:start position:0% yeah so here we're getting again uh like<01:39:19.320> you<01:39:19.620> remember<01:39:19.739> how<01:39:20.040> we<01:39:20.159> were<01:39:20.340> getting 01:39:20.510 --> 01:39:20.520 align:start position:0% like you remember how we were getting 01:39:20.520 --> 01:39:22.310 align:start position:0% like you remember how we were getting like<01:39:20.820> a<01:39:21.000> path<01:39:21.239> in<01:39:21.480> the<01:39:21.600> value<01:39:21.719> that<01:39:22.199> was 01:39:22.310 --> 01:39:22.320 align:start position:0% like a path in the value that was 01:39:22.320 --> 01:39:24.169 align:start position:0% like a path in the value that was because<01:39:22.440> that<01:39:22.679> was<01:39:22.800> the<01:39:22.980> only<01:39:23.040> valued<01:39:23.520> F<01:39:23.699> now 01:39:24.169 --> 01:39:24.179 align:start position:0% because that was the only valued F now 01:39:24.179 --> 01:39:26.149 align:start position:0% because that was the only valued F now we're<01:39:24.360> again<01:39:24.480> getting<01:39:24.840> a<01:39:25.020> hash<01:39:25.260> pointing<01:39:26.040> to 01:39:26.149 --> 01:39:26.159 align:start position:0% we're again getting a hash pointing to 01:39:26.159 --> 01:39:28.490 align:start position:0% we're again getting a hash pointing to the<01:39:26.280> common<01:39:26.400> path<01:39:26.760> of<01:39:27.000> like<01:39:27.300> the<01:39:27.840> next<01:39:28.260> one 01:39:28.490 --> 01:39:28.500 align:start position:0% the common path of like the next one 01:39:28.500 --> 01:39:30.709 align:start position:0% the common path of like the next one it's<01:39:28.860> going<01:39:29.100> to<01:39:29.159> be<01:39:29.219> a<01:39:29.400> branch<01:39:29.520> note<01:39:29.820> again<01:39:30.060> we 01:39:30.709 --> 01:39:30.719 align:start position:0% it's going to be a branch note again we 01:39:30.719 --> 01:39:34.430 align:start position:0% it's going to be a branch note again we could<01:39:30.960> you<01:39:31.500> know<01:39:31.620> again<01:39:31.980> query<01:39:32.820> uh<01:39:33.600> find<01:39:34.260> the 01:39:34.430 --> 01:39:34.440 align:start position:0% could you know again query uh find the 01:39:34.440 --> 01:39:35.270 align:start position:0% could you know again query uh find the path 01:39:35.270 --> 01:39:35.280 align:start position:0% path 01:39:35.280 --> 01:39:38.510 align:start position:0% path to<01:39:35.880> that<01:39:36.179> in<01:39:36.900> this<01:39:37.080> case<01:39:37.199> there's<01:39:37.500> no<01:39:37.800> value<01:39:38.100> at 01:39:38.510 --> 01:39:38.520 align:start position:0% to that in this case there's no value at 01:39:38.520 --> 01:39:40.850 align:start position:0% to that in this case there's no value at that<01:39:38.699> node<01:39:39.000> that's<01:39:39.239> just<01:39:39.540> pointing<01:39:39.900> to 01:39:40.850 --> 01:39:40.860 align:start position:0% that node that's just pointing to 01:39:40.860 --> 01:39:42.590 align:start position:0% that node that's just pointing to child<01:39:41.340> nodes 01:39:42.590 --> 01:39:42.600 align:start position:0% child nodes 01:39:42.600 --> 01:39:44.930 align:start position:0% child nodes yeah<01:39:42.960> well<01:39:43.080> there's<01:39:43.260> a<01:39:43.800> value<01:39:44.040> like<01:39:44.520> if<01:39:44.699> I 01:39:44.930 --> 01:39:44.940 align:start position:0% yeah well there's a value like if I 01:39:44.940 --> 01:39:47.149 align:start position:0% yeah well there's a value like if I query<01:39:45.239> test<01:39:45.480> key<01:39:45.719> O2<01:39:46.139> there's<01:39:46.739> going<01:39:46.980> to<01:39:47.100> be 01:39:47.149 --> 01:39:47.159 align:start position:0% query test key O2 there's going to be 01:39:47.159 --> 01:39:49.430 align:start position:0% query test key O2 there's going to be again<01:39:47.400> a<01:39:47.760> value<01:39:48.000> here 01:39:49.430 --> 01:39:49.440 align:start position:0% again a value here 01:39:49.440 --> 01:39:51.649 align:start position:0% again a value here but<01:39:49.860> uh<01:39:50.100> yeah<01:39:50.400> I'm<01:39:50.520> not<01:39:50.760> actually<01:39:50.940> sure<01:39:51.300> why 01:39:51.649 --> 01:39:51.659 align:start position:0% but uh yeah I'm not actually sure why 01:39:51.659 --> 01:39:54.050 align:start position:0% but uh yeah I'm not actually sure why we're<01:39:52.139> always<01:39:52.380> at<01:39:52.800> this<01:39:53.040> index<01:39:53.460> I'd<01:39:53.699> have<01:39:53.940> to 01:39:54.050 --> 01:39:54.060 align:start position:0% we're always at this index I'd have to 01:39:54.060 --> 01:39:55.850 align:start position:0% we're always at this index I'd have to look<01:39:54.239> at<01:39:54.480> the 01:39:55.850 --> 01:39:55.860 align:start position:0% look at the 01:39:55.860 --> 01:39:57.709 align:start position:0% look at the the<01:39:56.040> way<01:39:56.280> this<01:39:56.400> is<01:39:56.520> in<01:39:56.639> code<01:39:56.760> I<01:39:57.000> suspect<01:39:57.480> it's 01:39:57.709 --> 01:39:57.719 align:start position:0% the way this is in code I suspect it's 01:39:57.719 --> 01:40:00.290 align:start position:0% the way this is in code I suspect it's like<01:39:57.900> the<01:39:58.080> always<01:39:58.260> the<01:39:58.679> the 01:40:00.290 --> 01:40:00.300 align:start position:0% like the always the the 01:40:00.300 --> 01:40:02.750 align:start position:0% like the always the the latter<01:40:01.080> part<01:40:01.380> of<01:40:01.620> the<01:40:01.800> number<01:40:01.980> two<01:40:02.219> is<01:40:02.520> what's 01:40:02.750 --> 01:40:02.760 align:start position:0% latter part of the number two is what's 01:40:02.760 --> 01:40:05.930 align:start position:0% latter part of the number two is what's used<01:40:03.120> here<01:40:03.360> instead<01:40:03.960> of<01:40:04.020> tree<01:40:04.380> itself 01:40:05.930 --> 01:40:05.940 align:start position:0% used here instead of tree itself 01:40:05.940 --> 01:40:07.129 align:start position:0% used here instead of tree itself um 01:40:07.129 --> 01:40:07.139 align:start position:0% um 01:40:07.139 --> 01:40:09.770 align:start position:0% um now<01:40:07.739> I<01:40:07.920> can<01:40:08.040> recall<01:40:08.460> exactly<01:40:08.880> why<01:40:09.120> that<01:40:09.420> is<01:40:09.600> but 01:40:09.770 --> 01:40:09.780 align:start position:0% now I can recall exactly why that is but 01:40:09.780 --> 01:40:12.470 align:start position:0% now I can recall exactly why that is but uh<01:40:10.080> yeah<01:40:10.560> we<01:40:11.040> in<01:40:11.400> the<01:40:11.580> normal<01:40:11.699> like<01:40:12.000> setting 01:40:12.470 --> 01:40:12.480 align:start position:0% uh yeah we in the normal like setting 01:40:12.480 --> 01:40:14.450 align:start position:0% uh yeah we in the normal like setting with<01:40:12.659> like<01:40:12.900> keys<01:40:13.440> and<01:40:13.560> stuff<01:40:13.739> we<01:40:14.280> wouldn't 01:40:14.450 --> 01:40:14.460 align:start position:0% with like keys and stuff we wouldn't 01:40:14.460 --> 01:40:17.209 align:start position:0% with like keys and stuff we wouldn't expect<01:40:14.760> like<01:40:15.179> every<01:40:15.540> basically<01:40:16.380> level<01:40:16.560> due<01:40:17.100> to 01:40:17.209 --> 01:40:17.219 align:start position:0% expect like every basically level due to 01:40:17.219 --> 01:40:19.370 align:start position:0% expect like every basically level due to to<01:40:17.340> Branch<01:40:17.639> out<01:40:17.820> and<01:40:18.239> and<01:40:18.540> the<01:40:18.780> fact<01:40:18.900> that<01:40:19.139> it's 01:40:19.370 --> 01:40:19.380 align:start position:0% to Branch out and and the fact that it's 01:40:19.380 --> 01:40:21.350 align:start position:0% to Branch out and and the fact that it's tree<01:40:19.800> at<01:40:20.040> the<01:40:20.159> moment<01:40:20.280> is<01:40:20.520> just<01:40:20.699> a<01:40:20.820> peculiarity 01:40:21.350 --> 01:40:21.360 align:start position:0% tree at the moment is just a peculiarity 01:40:21.360 --> 01:40:25.729 align:start position:0% tree at the moment is just a peculiarity of<01:40:21.600> the<01:40:21.659> test<01:40:21.840> case<01:40:22.080> I've<01:40:22.320> come<01:40:22.739> up<01:40:22.860> with 01:40:25.729 --> 01:40:25.739 align:start position:0% 01:40:25.739 --> 01:40:41.990 align:start position:0% yep 01:40:41.990 --> 01:40:42.000 align:start position:0% 01:40:42.000 --> 01:40:47.689 align:start position:0% and<01:40:42.480> lowercase<01:40:42.960> uppercase<01:40:43.500> yeah 01:40:47.689 --> 01:40:47.699 align:start position:0% 01:40:47.699 --> 01:40:49.850 align:start position:0% yeah it's<01:40:48.360> not<01:40:48.600> lining<01:40:48.960> up<01:40:49.020> perfectly<01:40:49.440> too 01:40:49.850 --> 01:40:49.860 align:start position:0% yeah it's not lining up perfectly too 01:40:49.860 --> 01:40:53.750 align:start position:0% yeah it's not lining up perfectly too yeah<01:40:50.760> exactly<01:40:51.719> so<01:40:51.900> if<01:40:52.080> we<01:40:52.260> wanted<01:40:52.440> to<01:40:52.739> do<01:40:53.040> like 01:40:53.750 --> 01:40:53.760 align:start position:0% yeah exactly so if we wanted to do like 01:40:53.760 --> 01:40:55.910 align:start position:0% yeah exactly so if we wanted to do like if<01:40:54.000> we<01:40:54.179> could<01:40:54.300> natively<01:40:54.780> like<01:40:55.020> compute<01:40:55.500> you 01:40:55.910 --> 01:40:55.920 align:start position:0% if we could natively like compute you 01:40:55.920 --> 01:40:58.129 align:start position:0% if we could natively like compute you know<01:40:55.980> buffers<01:40:56.940> and<01:40:57.120> hexes 01:40:58.129 --> 01:40:58.139 align:start position:0% know buffers and hexes 01:40:58.139 --> 01:40:59.750 align:start position:0% know buffers and hexes then<01:40:58.500> it<01:40:58.620> would<01:40:58.739> be<01:40:58.860> much<01:40:59.159> easier<01:40:59.460> to<01:40:59.580> see 01:40:59.750 --> 01:40:59.760 align:start position:0% then it would be much easier to see 01:40:59.760 --> 01:41:01.370 align:start position:0% then it would be much easier to see what's<01:40:59.880> going<01:41:00.120> on<01:41:00.239> now<01:41:00.719> we're<01:41:00.900> using<01:41:01.199> like 01:41:01.370 --> 01:41:01.380 align:start position:0% what's going on now we're using like 01:41:01.380 --> 01:41:03.709 align:start position:0% what's going on now we're using like human<01:41:01.500> readable<01:41:01.980> keys<01:41:02.400> so<01:41:03.120> I<01:41:03.480> mean<01:41:03.600> they're 01:41:03.709 --> 01:41:03.719 align:start position:0% human readable keys so I mean they're 01:41:03.719 --> 01:41:05.570 align:start position:0% human readable keys so I mean they're broken<01:41:03.960> down<01:41:04.199> to<01:41:04.440> that<01:41:04.679> they're<01:41:05.040> you<01:41:05.460> know 01:41:05.570 --> 01:41:05.580 align:start position:0% broken down to that they're you know 01:41:05.580 --> 01:41:08.930 align:start position:0% broken down to that they're you know they're<01:41:06.120> coming<01:41:06.300> to<01:41:06.600> hex<01:41:07.139> so<01:41:07.620> at<01:41:07.860> each<01:41:08.100> uh<01:41:08.340> each 01:41:08.930 --> 01:41:08.940 align:start position:0% they're coming to hex so at each uh each 01:41:08.940 --> 01:41:10.610 align:start position:0% they're coming to hex so at each uh each part<01:41:09.060> of<01:41:09.179> the<01:41:09.239> way<01:41:09.360> down<01:41:09.540> that<01:41:09.840> we<01:41:09.960> go<01:41:10.320> it 01:41:10.610 --> 01:41:10.620 align:start position:0% part of the way down that we go it 01:41:10.620 --> 01:41:12.590 align:start position:0% part of the way down that we go it doesn't<01:41:10.860> line<01:41:11.159> up<01:41:11.340> exactly<01:41:11.820> with<01:41:12.179> the<01:41:12.360> end<01:41:12.480> of 01:41:12.590 --> 01:41:12.600 align:start position:0% doesn't line up exactly with the end of 01:41:12.600 --> 01:41:15.169 align:start position:0% doesn't line up exactly with the end of the<01:41:12.719> key<01:41:12.840> there's<01:41:13.320> often<01:41:13.620> like<01:41:13.739> one<01:41:14.100> next<01:41:14.880> like 01:41:15.169 --> 01:41:15.179 align:start position:0% the key there's often like one next like 01:41:15.179 --> 01:41:17.990 align:start position:0% the key there's often like one next like character<01:41:15.780> necessary<01:41:16.620> to<01:41:16.860> to<01:41:17.100> finalize<01:41:17.699> that 01:41:17.990 --> 01:41:18.000 align:start position:0% character necessary to to finalize that 01:41:18.000 --> 01:41:20.870 align:start position:0% character necessary to to finalize that the<01:41:18.239> number<01:41:18.600> zero<01:41:19.080> for<01:41:19.320> example 01:41:20.870 --> 01:41:20.880 align:start position:0% the number zero for example 01:41:20.880 --> 01:41:23.330 align:start position:0% the number zero for example um 01:41:23.330 --> 01:41:23.340 align:start position:0% 01:41:23.340 --> 01:41:25.610 align:start position:0% all<01:41:23.760> right<01:41:23.940> so<01:41:24.120> I'll<01:41:24.300> go<01:41:24.540> over 01:41:25.610 --> 01:41:25.620 align:start position:0% all right so I'll go over 01:41:25.620 --> 01:41:27.669 align:start position:0% all right so I'll go over with<01:41:26.159> three<01:41:26.760> minutes 01:41:27.669 --> 01:41:27.679 align:start position:0% with three minutes 01:41:27.679 --> 01:41:30.709 align:start position:0% with three minutes so<01:41:28.679> I 01:41:30.709 --> 01:41:30.719 align:start position:0% so I 01:41:30.719 --> 01:41:32.570 align:start position:0% so I I think<01:41:31.139> maybe<01:41:31.320> open<01:41:31.620> up<01:41:31.860> to<01:41:32.040> just<01:41:32.340> like 01:41:32.570 --> 01:41:32.580 align:start position:0% I think maybe open up to just like 01:41:32.580 --> 01:41:35.030 align:start position:0% I think maybe open up to just like general<01:41:33.060> questions<01:41:33.600> or 01:41:35.030 --> 01:41:35.040 align:start position:0% general questions or 01:41:35.040 --> 01:41:36.050 align:start position:0% general questions or um 01:41:36.050 --> 01:41:36.060 align:start position:0% um 01:41:36.060 --> 01:41:38.390 align:start position:0% um comments<01:41:36.900> or<01:41:37.320> anything 01:41:38.390 --> 01:41:38.400 align:start position:0% comments or anything 01:41:38.400 --> 01:41:39.229 align:start position:0% comments or anything um 01:41:39.229 --> 01:41:39.239 align:start position:0% um 01:41:39.239 --> 01:41:41.810 align:start position:0% um you<01:41:39.659> know<01:41:39.719> we're<01:41:40.020> we're<01:41:40.380> building<01:41:41.280> this<01:41:41.580> for 01:41:41.810 --> 01:41:41.820 align:start position:0% you know we're we're building this for 01:41:41.820 --> 01:41:43.850 align:start position:0% you know we're we're building this for you<01:41:41.940> guys<01:41:42.119> so<01:41:42.540> if<01:41:42.900> there<01:41:43.020> are<01:41:43.199> things<01:41:43.380> that<01:41:43.679> are 01:41:43.850 --> 01:41:43.860 align:start position:0% you guys so if there are things that are 01:41:43.860 --> 01:41:46.430 align:start position:0% you guys so if there are things that are not<01:41:44.100> working<01:41:44.340> or<01:41:44.820> confusing<01:41:45.480> or<01:41:45.960> that<01:41:46.139> you'd 01:41:46.430 --> 01:41:46.440 align:start position:0% not working or confusing or that you'd 01:41:46.440 --> 01:41:48.109 align:start position:0% not working or confusing or that you'd like<01:41:46.500> to<01:41:46.739> see<01:41:46.920> where 01:41:48.109 --> 01:41:48.119 align:start position:0% like to see where 01:41:48.119 --> 01:41:50.090 align:start position:0% like to see where we're very<01:41:48.659> open<01:41:48.840> to<01:41:49.080> feedback<01:41:49.500> and 01:41:50.090 --> 01:41:50.100 align:start position:0% we're very open to feedback and 01:41:50.100 --> 01:41:53.990 align:start position:0% we're very open to feedback and suggestions<01:41:50.639> and<01:41:51.060> help 01:41:53.990 --> 01:41:54.000 align:start position:0% 01:41:54.000 --> 01:41:56.689 align:start position:0% yeah<01:41:54.659> so<01:41:54.960> like<01:41:55.320> most<01:41:55.560> of<01:41:55.739> what<01:41:55.860> we've<01:41:56.159> done<01:41:56.340> so 01:41:56.689 --> 01:41:56.699 align:start position:0% yeah so like most of what we've done so 01:41:56.699 --> 01:41:58.370 align:start position:0% yeah so like most of what we've done so far<01:41:56.820> has<01:41:57.000> been<01:41:57.179> like<01:41:57.480> working<01:41:57.780> on<01:41:58.080> you<01:41:58.320> know 01:41:58.370 --> 01:41:58.380 align:start position:0% far has been like working on you know 01:41:58.380 --> 01:42:00.050 align:start position:0% far has been like working on you know just<01:41:58.619> Miracle<01:41:59.100> Patricia<01:41:59.520> trees<01:41:59.760> uh 01:42:00.050 --> 01:42:00.060 align:start position:0% just Miracle Patricia trees uh 01:42:00.060 --> 01:42:02.390 align:start position:0% just Miracle Patricia trees uh themselves<01:42:00.480> uh<01:42:01.380> a<01:42:01.560> bit<01:42:01.619> further<01:42:01.920> down<01:42:02.100> in<01:42:02.280> that 01:42:02.390 --> 01:42:02.400 align:start position:0% themselves uh a bit further down in that 01:42:02.400 --> 01:42:04.070 align:start position:0% themselves uh a bit further down in that tutorial<01:42:02.699> like<01:42:02.940> I<01:42:03.119> encourage<01:42:03.420> you<01:42:03.540> to<01:42:03.780> just 01:42:04.070 --> 01:42:04.080 align:start position:0% tutorial like I encourage you to just 01:42:04.080 --> 01:42:06.109 align:start position:0% tutorial like I encourage you to just keep<01:42:04.320> going<01:42:04.500> at<01:42:04.679> home<01:42:04.860> and<01:42:05.040> ping<01:42:05.340> me<01:42:05.460> like<01:42:05.820> on 01:42:06.109 --> 01:42:06.119 align:start position:0% keep going at home and ping me like on 01:42:06.119 --> 01:42:07.970 align:start position:0% keep going at home and ping me like on Discord<01:42:06.600> or<01:42:06.719> telegram<01:42:07.139> or<01:42:07.320> Twitter<01:42:07.560> if 01:42:07.970 --> 01:42:07.980 align:start position:0% Discord or telegram or Twitter if 01:42:07.980 --> 01:42:09.830 align:start position:0% Discord or telegram or Twitter if anything<01:42:08.460> like<01:42:08.760> doesn't<01:42:09.000> work<01:42:09.239> as<01:42:09.420> you'd 01:42:09.830 --> 01:42:09.840 align:start position:0% anything like doesn't work as you'd 01:42:09.840 --> 01:42:12.770 align:start position:0% anything like doesn't work as you'd expect<01:42:10.219> uh<01:42:11.219> but<01:42:11.460> there<01:42:11.639> are<01:42:11.760> like<01:42:12.060> we're 01:42:12.770 --> 01:42:12.780 align:start position:0% expect uh but there are like we're 01:42:12.780 --> 01:42:14.330 align:start position:0% expect uh but there are like we're working<01:42:13.080> also<01:42:13.440> like<01:42:13.560> with<01:42:13.739> blocks<01:42:14.100> and<01:42:14.219> with 01:42:14.330 --> 01:42:14.340 align:start position:0% working also like with blocks and with 01:42:14.340 --> 01:42:17.209 align:start position:0% working also like with blocks and with transactions<01:42:14.940> and<01:42:15.119> rlp<01:42:15.659> encoding<01:42:16.139> uh<01:42:16.980> which 01:42:17.209 --> 01:42:17.219 align:start position:0% transactions and rlp encoding uh which 01:42:17.219 --> 01:42:19.370 align:start position:0% transactions and rlp encoding uh which is<01:42:17.280> quite<01:42:17.520> I<01:42:17.880> feel<01:42:18.060> like<01:42:18.480> it's<01:42:18.780> how<01:42:18.960> I<01:42:19.080> learned 01:42:19.370 --> 01:42:19.380 align:start position:0% is quite I feel like it's how I learned 01:42:19.380 --> 01:42:21.050 align:start position:0% is quite I feel like it's how I learned about<01:42:19.679> ethereum<01:42:20.219> initially<01:42:20.580> like<01:42:20.820> through 01:42:21.050 --> 01:42:21.060 align:start position:0% about ethereum initially like through 01:42:21.060 --> 01:42:23.510 align:start position:0% about ethereum initially like through learning<01:42:21.420> about<01:42:21.540> these<01:42:21.780> data<01:42:22.080> structures<01:42:22.520> and 01:42:23.510 --> 01:42:23.520 align:start position:0% learning about these data structures and 01:42:23.520 --> 01:42:25.129 align:start position:0% learning about these data structures and the<01:42:23.820> first<01:42:23.940> draft<01:42:24.119> of<01:42:24.420> that<01:42:24.540> tutorial<01:42:24.900> was 01:42:25.129 --> 01:42:25.139 align:start position:0% the first draft of that tutorial was 01:42:25.139 --> 01:42:26.510 align:start position:0% the first draft of that tutorial was actually<01:42:25.260> like<01:42:25.440> me<01:42:25.619> learning<01:42:26.040> you<01:42:26.280> know<01:42:26.340> about 01:42:26.510 --> 01:42:26.520 align:start position:0% actually like me learning you know about 01:42:26.520 --> 01:42:28.490 align:start position:0% actually like me learning you know about this<01:42:26.760> stuff<01:42:26.940> and<01:42:27.119> figuring<01:42:27.420> out<01:42:27.540> what's<01:42:28.320> going 01:42:28.490 --> 01:42:28.500 align:start position:0% this stuff and figuring out what's going 01:42:28.500 --> 01:42:31.189 align:start position:0% this stuff and figuring out what's going on<01:42:28.739> and<01:42:30.119> um 01:42:31.189 --> 01:42:31.199 align:start position:0% on and um 01:42:31.199 --> 01:42:34.910 align:start position:0% on and um and<01:42:31.739> yeah 01:42:34.910 --> 01:42:34.920 align:start position:0% 01:42:34.920 --> 01:42:36.709 align:start position:0% um<01:42:34.980> and<01:42:35.280> yeah<01:42:35.400> we're<01:42:35.760> we're<01:42:35.880> an<01:42:36.239> open<01:42:36.360> source 01:42:36.709 --> 01:42:36.719 align:start position:0% um and yeah we're we're an open source 01:42:36.719 --> 01:42:38.390 align:start position:0% um and yeah we're we're an open source project<01:42:36.900> you<01:42:37.199> can<01:42:37.320> find<01:42:37.500> us<01:42:37.619> on<01:42:37.739> GitHub<01:42:38.100> you 01:42:38.390 --> 01:42:38.400 align:start position:0% project you can find us on GitHub you 01:42:38.400 --> 01:42:40.790 align:start position:0% project you can find us on GitHub you can<01:42:38.580> find<01:42:38.760> us<01:42:38.940> on<01:42:39.119> Discord<01:42:39.540> and<01:42:39.840> chime<01:42:40.320> in<01:42:40.560> or 01:42:40.790 --> 01:42:40.800 align:start position:0% can find us on Discord and chime in or 01:42:40.800 --> 01:42:43.850 align:start position:0% can find us on Discord and chime in or ask<01:42:40.980> questions 01:42:43.850 --> 01:42:43.860 align:start position:0% 01:42:43.860 --> 01:42:46.250 align:start position:0% yeah<01:42:44.340> we<01:42:44.580> have<01:42:44.760> a<01:42:45.119> massive<01:42:45.360> number<01:42:45.600> of<01:42:46.020> uh 01:42:46.250 --> 01:42:46.260 align:start position:0% yeah we have a massive number of uh 01:42:46.260 --> 01:42:48.229 align:start position:0% yeah we have a massive number of uh external<01:42:46.679> contributors<01:42:47.219> who've<01:42:47.760> helped<01:42:48.060> you 01:42:48.229 --> 01:42:48.239 align:start position:0% external contributors who've helped you 01:42:48.239 --> 01:42:50.930 align:start position:0% external contributors who've helped you know<01:42:48.360> over<01:42:48.480> the<01:42:48.719> years<01:42:48.900> the<01:42:49.560> repo<01:42:49.920> is<01:42:50.280> uh 01:42:50.930 --> 01:42:50.940 align:start position:0% know over the years the repo is uh 01:42:50.940 --> 01:42:53.450 align:start position:0% know over the years the repo is uh fairly<01:42:51.480> old<01:42:51.659> I<01:42:52.020> think<01:42:52.139> it's<01:42:52.320> like<01:42:52.739> six<01:42:53.219> years 01:42:53.450 --> 01:42:53.460 align:start position:0% fairly old I think it's like six years 01:42:53.460 --> 01:42:55.430 align:start position:0% fairly old I think it's like six years old<01:42:53.699> or<01:42:54.000> perhaps<01:42:54.420> like<01:42:54.659> even<01:42:54.840> more<01:42:55.080> than<01:42:55.260> that 01:42:55.430 --> 01:42:55.440 align:start position:0% old or perhaps like even more than that 01:42:55.440 --> 01:42:57.109 align:start position:0% old or perhaps like even more than that sometimes<01:42:56.159> I'll<01:42:56.340> work<01:42:56.520> on<01:42:56.699> a<01:42:56.820> part<01:42:56.880> of<01:42:57.000> the 01:42:57.109 --> 01:42:57.119 align:start position:0% sometimes I'll work on a part of the 01:42:57.119 --> 01:42:58.850 align:start position:0% sometimes I'll work on a part of the code<01:42:57.239> and<01:42:57.480> I'm<01:42:57.780> seeing<01:42:58.020> like<01:42:58.260> the<01:42:58.380> get<01:42:58.500> blame 01:42:58.850 --> 01:42:58.860 align:start position:0% code and I'm seeing like the get blame 01:42:58.860 --> 01:43:00.290 align:start position:0% code and I'm seeing like the get blame like<01:42:59.040> five<01:42:59.280> five<01:42:59.340> years<01:42:59.760> ago<01:42:59.940> or<01:43:00.179> something 01:43:00.290 --> 01:43:00.300 align:start position:0% like five five years ago or something 01:43:00.300 --> 01:43:01.970 align:start position:0% like five five years ago or something like<01:43:00.600> that<01:43:00.719> so<01:43:01.139> it's<01:43:01.380> really<01:43:01.500> like<01:43:01.739> a<01:43:01.860> pretty 01:43:01.970 --> 01:43:01.980 align:start position:0% like that so it's really like a pretty 01:43:01.980 --> 01:43:05.510 align:start position:0% like that so it's really like a pretty old<01:43:02.159> repo<01:43:02.719> we<01:43:03.719> we<01:43:04.199> are<01:43:04.500> extremely<01:43:05.100> open<01:43:05.280> to 01:43:05.510 --> 01:43:05.520 align:start position:0% old repo we we are extremely open to 01:43:05.520 --> 01:43:07.370 align:start position:0% old repo we we are extremely open to external<01:43:05.940> contributors<01:43:06.540> like<01:43:07.080> sometimes 01:43:07.370 --> 01:43:07.380 align:start position:0% external contributors like sometimes 01:43:07.380 --> 01:43:08.810 align:start position:0% external contributors like sometimes we'll<01:43:07.560> have<01:43:07.739> people<01:43:07.920> come<01:43:08.159> up<01:43:08.280> and<01:43:08.460> just<01:43:08.639> help 01:43:08.810 --> 01:43:08.820 align:start position:0% we'll have people come up and just help 01:43:08.820 --> 01:43:11.030 align:start position:0% we'll have people come up and just help out<01:43:09.000> and<01:43:09.360> then<01:43:09.480> we<01:43:09.719> we<01:43:09.960> you<01:43:10.500> know<01:43:10.560> we<01:43:10.800> include 01:43:11.030 --> 01:43:11.040 align:start position:0% out and then we we you know we include 01:43:11.040 --> 01:43:12.709 align:start position:0% out and then we we you know we include them<01:43:11.280> in<01:43:11.520> the<01:43:11.639> the<01:43:11.760> team<01:43:11.940> like<01:43:12.119> not<01:43:12.360> in<01:43:12.540> the 01:43:12.709 --> 01:43:12.719 align:start position:0% them in the the team like not in the 01:43:12.719 --> 01:43:14.510 align:start position:0% them in the the team like not in the formal<01:43:12.960> like<01:43:13.260> team<01:43:13.440> itself<01:43:13.800> but<01:43:14.040> we<01:43:14.219> do<01:43:14.340> like 01:43:14.510 --> 01:43:14.520 align:start position:0% formal like team itself but we do like 01:43:14.520 --> 01:43:16.430 align:start position:0% formal like team itself but we do like chat<01:43:14.940> with<01:43:15.119> them<01:43:15.300> and<01:43:15.480> are<01:43:15.659> always<01:43:15.900> happy<01:43:16.199> to 01:43:16.430 --> 01:43:16.440 align:start position:0% chat with them and are always happy to 01:43:16.440 --> 01:43:18.709 align:start position:0% chat with them and are always happy to help<01:43:16.619> people<01:43:16.860> you<01:43:17.280> know<01:43:17.400> help<01:43:17.880> the<01:43:18.239> project 01:43:18.709 --> 01:43:18.719 align:start position:0% help people you know help the project 01:43:18.719 --> 01:43:21.709 align:start position:0% help people you know help the project we're<01:43:19.080> working<01:43:19.260> on<01:43:19.699> uh<01:43:20.699> our<01:43:20.940> future<01:43:21.119> projects 01:43:21.709 --> 01:43:21.719 align:start position:0% we're working on uh our future projects 01:43:21.719 --> 01:43:23.570 align:start position:0% we're working on uh our future projects are<01:43:22.199> we're<01:43:22.440> trying<01:43:22.679> to<01:43:22.800> improve<01:43:23.100> the<01:43:23.280> client 01:43:23.570 --> 01:43:23.580 align:start position:0% are we're trying to improve the client 01:43:23.580 --> 01:43:25.129 align:start position:0% are we're trying to improve the client thinking<01:43:23.940> at<01:43:24.119> the<01:43:24.239> moment<01:43:24.360> we<01:43:24.659> only<01:43:24.719> have<01:43:24.960> full 01:43:25.129 --> 01:43:25.139 align:start position:0% thinking at the moment we only have full 01:43:25.139 --> 01:43:26.930 align:start position:0% thinking at the moment we only have full sync<01:43:25.500> it's<01:43:25.679> super<01:43:25.860> slow<01:43:26.100> and<01:43:26.400> you<01:43:26.639> know<01:43:26.760> you 01:43:26.930 --> 01:43:26.940 align:start position:0% sync it's super slow and you know you 01:43:26.940 --> 01:43:28.189 align:start position:0% sync it's super slow and you know you know<01:43:27.119> that<01:43:27.239> would<01:43:27.420> never<01:43:27.540> use<01:43:27.780> that<01:43:27.960> you<01:43:28.139> know 01:43:28.189 --> 01:43:28.199 align:start position:0% know that would never use that you know 01:43:28.199 --> 01:43:30.709 align:start position:0% know that would never use that you know in<01:43:28.320> production<01:43:28.619> obviously<01:43:29.159> uh 01:43:30.709 --> 01:43:30.719 align:start position:0% in production obviously uh 01:43:30.719 --> 01:43:32.930 align:start position:0% in production obviously uh uh<01:43:31.619> we're<01:43:31.860> trying<01:43:32.100> to<01:43:32.280> do<01:43:32.400> you<01:43:32.580> know<01:43:32.760> General 01:43:32.930 --> 01:43:32.940 align:start position:0% uh we're trying to do you know General 01:43:32.940 --> 01:43:35.450 align:start position:0% uh we're trying to do you know General like<01:43:33.420> optimizations<01:43:33.960> as<01:43:34.260> well<01:43:34.440> so<01:43:34.980> if<01:43:35.159> anyone 01:43:35.450 --> 01:43:35.460 align:start position:0% like optimizations as well so if anyone 01:43:35.460 --> 01:43:37.189 align:start position:0% like optimizations as well so if anyone like<01:43:35.699> is<01:43:35.880> competent<01:43:36.239> that<01:43:36.480> we're<01:43:36.900> really 01:43:37.189 --> 01:43:37.199 align:start position:0% like is competent that we're really 01:43:37.199 --> 01:43:39.890 align:start position:0% like is competent that we're really happy<01:43:37.440> to<01:43:37.739> like<01:43:38.040> uh<01:43:38.639> get<01:43:38.940> you<01:43:39.119> started<01:43:39.540> on<01:43:39.719> that 01:43:39.890 --> 01:43:39.900 align:start position:0% happy to like uh get you started on that 01:43:39.900 --> 01:43:43.189 align:start position:0% happy to like uh get you started on that or<01:43:40.800> improving<01:43:41.280> like<01:43:41.580> the<01:43:41.880> Json<01:43:42.239> RPC<01:43:42.719> endpoints 01:43:43.189 --> 01:43:43.199 align:start position:0% or improving like the Json RPC endpoints 01:43:43.199 --> 01:43:46.430 align:start position:0% or improving like the Json RPC endpoints we<01:43:43.440> don't<01:43:43.619> yet<01:43:43.860> serve<01:43:44.280> all<01:43:44.520> the<01:43:44.820> RPC<01:43:45.480> calls<01:43:46.080> so 01:43:46.430 --> 01:43:46.440 align:start position:0% we don't yet serve all the RPC calls so 01:43:46.440 --> 01:43:48.290 align:start position:0% we don't yet serve all the RPC calls so that's<01:43:46.739> uh<01:43:46.980> it's<01:43:47.219> an<01:43:47.400> excellent<01:43:47.699> place<01:43:48.000> to 01:43:48.290 --> 01:43:48.300 align:start position:0% that's uh it's an excellent place to 01:43:48.300 --> 01:43:49.850 align:start position:0% that's uh it's an excellent place to start<01:43:48.420> if<01:43:48.719> you<01:43:48.840> want<01:43:48.960> to<01:43:49.080> help<01:43:49.199> out<01:43:49.440> just 01:43:49.850 --> 01:43:49.860 align:start position:0% start if you want to help out just 01:43:49.860 --> 01:43:53.030 align:start position:0% start if you want to help out just implements<01:43:50.580> a<01:43:50.760> new<01:43:51.260> RPC<01:43:52.260> endpoint<01:43:52.679> for<01:43:52.920> us 01:43:53.030 --> 01:43:53.040 align:start position:0% implements a new RPC endpoint for us 01:43:53.040 --> 01:43:54.830 align:start position:0% implements a new RPC endpoint for us exactly<01:43:53.699> you<01:43:54.000> can<01:43:54.060> just<01:43:54.239> go<01:43:54.420> through<01:43:54.540> the<01:43:54.719> list 01:43:54.830 --> 01:43:54.840 align:start position:0% exactly you can just go through the list 01:43:54.840 --> 01:43:56.570 align:start position:0% exactly you can just go through the list of<01:43:55.080> what<01:43:55.199> we've<01:43:55.440> implemented<01:43:55.920> and<01:43:56.159> just<01:43:56.400> you 01:43:56.570 --> 01:43:56.580 align:start position:0% of what we've implemented and just you 01:43:56.580 --> 01:43:59.330 align:start position:0% of what we've implemented and just you know<01:43:56.699> uh<01:43:57.060> come<01:43:57.300> up<01:43:57.420> you<01:43:57.780> know<01:43:57.900> with<01:43:58.320> easy<01:43:58.980> ones 01:43:59.330 --> 01:43:59.340 align:start position:0% know uh come up you know with easy ones 01:43:59.340 --> 01:44:00.590 align:start position:0% know uh come up you know with easy ones that<01:43:59.460> you<01:43:59.580> want<01:43:59.699> to<01:43:59.820> implement<01:44:00.060> and<01:44:00.300> it's<01:44:00.480> a 01:44:00.590 --> 01:44:00.600 align:start position:0% that you want to implement and it's a 01:44:00.600 --> 01:44:01.850 align:start position:0% that you want to implement and it's a good<01:44:00.719> way<01:44:00.840> to<01:44:00.960> get<01:44:01.139> started<01:44:01.440> learning<01:44:01.739> about 01:44:01.850 --> 01:44:01.860 align:start position:0% good way to get started learning about 01:44:01.860 --> 01:44:05.030 align:start position:0% good way to get started learning about our<01:44:02.040> repo<01:44:02.840> uh<01:44:03.840> my<01:44:04.020> side<01:44:04.260> I'm<01:44:04.500> working<01:44:04.619> more<01:44:04.860> on 01:44:05.030 --> 01:44:05.040 align:start position:0% our repo uh my side I'm working more on 01:44:05.040 --> 01:44:07.490 align:start position:0% our repo uh my side I'm working more on R<01:44:05.219> D<01:44:05.340> for<01:44:05.639> vehicle<01:44:06.540> freeze<01:44:06.900> and<01:44:06.960> statelessness 01:44:07.490 --> 01:44:07.500 align:start position:0% R D for vehicle freeze and statelessness 01:44:07.500 --> 01:44:09.050 align:start position:0% R D for vehicle freeze and statelessness which<01:44:07.800> is<01:44:07.920> you<01:44:08.100> know<01:44:08.219> sort<01:44:08.400> of<01:44:08.520> related<01:44:08.760> to<01:44:08.940> the 01:44:09.050 --> 01:44:09.060 align:start position:0% which is you know sort of related to the 01:44:09.060 --> 01:44:12.169 align:start position:0% which is you know sort of related to the Merkle<01:44:09.420> tree<01:44:09.600> stuff<01:44:10.080> we've<01:44:10.440> been<01:44:10.560> exploring 01:44:12.169 --> 01:44:12.179 align:start position:0% Merkle tree stuff we've been exploring 01:44:12.179 --> 01:44:15.530 align:start position:0% Merkle tree stuff we've been exploring uh<01:44:12.900> Scotty<01:44:13.380> works<01:44:13.739> on<01:44:13.920> ultralight<01:44:14.580> amongst 01:44:15.530 --> 01:44:15.540 align:start position:0% uh Scotty works on ultralight amongst 01:44:15.540 --> 01:44:16.669 align:start position:0% uh Scotty works on ultralight amongst other<01:44:15.600> things 01:44:16.669 --> 01:44:16.679 align:start position:0% other things 01:44:16.679 --> 01:44:19.070 align:start position:0% other things and<01:44:17.280> yeah<01:44:18.119> we're<01:44:18.300> just<01:44:18.540> improving<01:44:18.840> the<01:44:18.960> gold 01:44:19.070 --> 01:44:19.080 align:start position:0% and yeah we're just improving the gold 01:44:19.080 --> 01:44:21.290 align:start position:0% and yeah we're just improving the gold base<01:44:19.320> as<01:44:19.619> well<01:44:19.679> making<01:44:20.040> it<01:44:20.280> a<01:44:20.460> nicer<01:44:20.880> with 01:44:21.290 --> 01:44:21.300 align:start position:0% base as well making it a nicer with 01:44:21.300 --> 01:44:24.950 align:start position:0% base as well making it a nicer with nicer<01:44:21.719> types<01:44:22.020> and<01:44:22.260> a<01:44:22.619> better<01:44:23.159> performance 01:44:24.950 --> 01:44:24.960 align:start position:0% nicer types and a better performance 01:44:24.960 --> 01:44:34.609 align:start position:0% nicer types and a better performance and<01:44:25.380> the<01:44:25.500> last<01:44:25.679> questions 01:44:34.609 --> 01:44:34.619 align:start position:0% 01:44:34.619 --> 01:44:36.169 align:start position:0% that's<01:44:34.980> a<01:44:35.159> good<01:44:35.340> point<01:44:35.520> yeah<01:44:35.699> I<01:44:35.880> didn't<01:44:36.000> think 01:44:36.169 --> 01:44:36.179 align:start position:0% that's a good point yeah I didn't think 01:44:36.179 --> 01:44:38.870 align:start position:0% that's a good point yeah I didn't think of<01:44:36.360> adding<01:44:36.719> that<01:44:36.840> to<01:44:37.199> the<01:44:37.560> link<01:44:37.920> tree<01:44:38.219> how<01:44:38.639> will 01:44:38.870 --> 01:44:38.880 align:start position:0% of adding that to the link tree how will 01:44:38.880 --> 01:44:40.550 align:start position:0% of adding that to the link tree how will uh<01:44:39.239> that<01:44:39.360> link<01:44:39.600> tree<01:44:39.780> linked<01:44:40.199> above<01:44:40.380> all 01:44:40.550 --> 01:44:40.560 align:start position:0% uh that link tree linked above all 01:44:40.560 --> 01:44:42.890 align:start position:0% uh that link tree linked above all update<01:44:40.920> it<01:44:41.040> with<01:44:41.280> the<01:44:41.460> link<01:44:41.580> to<01:44:41.820> our<01:44:42.119> Discord 01:44:42.890 --> 01:44:42.900 align:start position:0% update it with the link to our Discord 01:44:42.900 --> 01:44:44.689 align:start position:0% update it with the link to our Discord so<01:44:43.260> that<01:44:43.440> then<01:44:43.619> you<01:44:43.860> can<01:44:43.980> come<01:44:44.159> in<01:44:44.340> it's<01:44:44.520> the 01:44:44.689 --> 01:44:44.699 align:start position:0% so that then you can come in it's the 01:44:44.699 --> 01:44:46.850 align:start position:0% so that then you can come in it's the ethereum<01:44:45.000> JS<01:44:45.420> Discord<01:44:45.780> probably<01:44:46.199> fairly<01:44:46.679> easy 01:44:46.850 --> 01:44:46.860 align:start position:0% ethereum JS Discord probably fairly easy 01:44:46.860 --> 01:44:48.890 align:start position:0% ethereum JS Discord probably fairly easy to<01:44:47.040> find<01:44:47.159> as<01:44:47.340> well<01:44:47.460> but<01:44:47.760> I'll<01:44:48.060> link<01:44:48.719> it 01:44:48.890 --> 01:44:48.900 align:start position:0% to find as well but I'll link it 01:44:48.900 --> 01:44:52.189 align:start position:0% to find as well but I'll link it nevertheless<01:44:49.580> yeah<01:44:50.580> I<01:44:50.940> feel<01:44:51.060> like<01:44:51.239> one<01:44:52.080> last 01:44:52.189 --> 01:44:52.199 align:start position:0% nevertheless yeah I feel like one last 01:44:52.199 --> 01:44:54.530 align:start position:0% nevertheless yeah I feel like one last question<01:44:52.440> I<01:44:52.800> had<01:44:52.980> a<01:44:53.159> friend<01:44:53.520> who<01:44:54.119> actually 01:44:54.530 --> 01:44:54.540 align:start position:0% question I had a friend who actually 01:44:54.540 --> 01:44:56.450 align:start position:0% question I had a friend who actually worked<01:44:54.960> with<01:44:55.080> ethereum<01:44:55.500> yes<01:44:55.739> and<01:44:55.980> he<01:44:56.159> was<01:44:56.280> like 01:44:56.450 --> 01:44:56.460 align:start position:0% worked with ethereum yes and he was like 01:44:56.460 --> 01:45:00.709 align:start position:0% worked with ethereum yes and he was like telling<01:44:56.880> me<01:44:57.420> uh<01:44:58.380> about<01:44:58.679> like<01:44:59.100> he<01:45:00.000> also<01:45:00.360> used 01:45:00.709 --> 01:45:00.719 align:start position:0% telling me uh about like he also used 01:45:00.719 --> 01:45:01.850 align:start position:0% telling me uh about like he also used that 01:45:01.850 --> 01:45:01.860 align:start position:0% that 01:45:01.860 --> 01:45:03.850 align:start position:0% that um<01:45:01.920> is<01:45:02.639> this<01:45:02.820> actually 01:45:03.850 --> 01:45:03.860 align:start position:0% um is this actually 01:45:03.860 --> 01:45:07.250 align:start position:0% um is this actually interconnected<01:45:04.860> just<01:45:05.100> for<01:45:05.400> a<01:45:05.639> 3dmgs<01:45:06.540> or<01:45:07.139> it 01:45:07.250 --> 01:45:07.260 align:start position:0% interconnected just for a 3dmgs or it 01:45:07.260 --> 01:45:10.430 align:start position:0% interconnected just for a 3dmgs or it can<01:45:07.380> be<01:45:07.500> like<01:45:08.000> interoperable<01:45:09.000> in<01:45:09.480> other 01:45:10.430 --> 01:45:10.440 align:start position:0% can be like interoperable in other 01:45:10.440 --> 01:45:13.609 align:start position:0% can be like interoperable in other like<01:45:11.159> I<01:45:11.639> don't<01:45:11.699> know<01:45:11.820> uh<01:45:12.600> proof<01:45:12.900> of<01:45:13.020> proof<01:45:13.560> of 01:45:13.609 --> 01:45:13.619 align:start position:0% like I don't know uh proof of proof of 01:45:13.619 --> 01:45:16.250 align:start position:0% like I don't know uh proof of proof of History<01:45:14.040> like<01:45:14.580> Solana<01:45:15.300> or<01:45:15.719> something<01:45:16.020> like 01:45:16.250 --> 01:45:16.260 align:start position:0% History like Solana or something like 01:45:16.260 --> 01:45:17.629 align:start position:0% History like Solana or something like that<01:45:16.380> I<01:45:16.739> don't<01:45:16.800> know<01:45:16.860> if<01:45:16.980> I'm<01:45:17.159> just<01:45:17.340> telling 01:45:17.629 --> 01:45:17.639 align:start position:0% that I don't know if I'm just telling 01:45:17.639 --> 01:45:19.370 align:start position:0% that I don't know if I'm just telling nonsense<01:45:18.060> but<01:45:18.300> he<01:45:18.600> was<01:45:18.780> telling<01:45:19.020> me<01:45:19.080> like<01:45:19.199> he 01:45:19.370 --> 01:45:19.380 align:start position:0% nonsense but he was telling me like he 01:45:19.380 --> 01:45:23.209 align:start position:0% nonsense but he was telling me like he used<01:45:19.679> that<01:45:19.920> for<01:45:20.400> uh<01:45:20.940> our<01:45:21.300> RCP<01:45:21.780> support<01:45:22.080> uh<01:45:23.040> kind 01:45:23.209 --> 01:45:23.219 align:start position:0% used that for uh our RCP support uh kind 01:45:23.219 --> 01:45:25.010 align:start position:0% used that for uh our RCP support uh kind of<01:45:23.340> the<01:45:23.400> thing<01:45:23.580> how<01:45:23.940> does<01:45:24.119> it<01:45:24.300> work<01:45:24.480> because<01:45:24.719> I 01:45:25.010 --> 01:45:25.020 align:start position:0% of the thing how does it work because I 01:45:25.020 --> 01:45:27.290 align:start position:0% of the thing how does it work because I I<01:45:25.260> was<01:45:25.440> kind<01:45:25.619> of<01:45:25.980> confusing<01:45:26.340> like 01:45:27.290 --> 01:45:27.300 align:start position:0% I was kind of confusing like 01:45:27.300 --> 01:45:29.629 align:start position:0% I was kind of confusing like he<01:45:27.900> was<01:45:28.080> actually<01:45:28.260> using<01:45:28.619> a<01:45:28.800> 300.js<01:45:29.400> for 01:45:29.629 --> 01:45:29.639 align:start position:0% he was actually using a 300.js for 01:45:29.639 --> 01:45:31.850 align:start position:0% he was actually using a 300.js for connecting<01:45:30.119> with<01:45:30.300> Solana 01:45:31.850 --> 01:45:31.860 align:start position:0% connecting with Solana 01:45:31.860 --> 01:45:34.729 align:start position:0% connecting with Solana yeah<01:45:32.460> so<01:45:32.760> it's<01:45:33.000> uh<01:45:33.360> interesting<01:45:33.840> question<01:45:34.020> so 01:45:34.729 --> 01:45:34.739 align:start position:0% yeah so it's uh interesting question so 01:45:34.739 --> 01:45:37.430 align:start position:0% yeah so it's uh interesting question so there's<01:45:35.040> there<01:45:35.639> are<01:45:35.940> we've<01:45:36.780> increasingly 01:45:37.430 --> 01:45:37.440 align:start position:0% there's there are we've increasingly 01:45:37.440 --> 01:45:41.870 align:start position:0% there's there are we've increasingly made<01:45:37.860> the<01:45:38.460> our<01:45:38.940> packages<01:45:39.860> uh<01:45:40.860> configurable<01:45:41.400> so 01:45:41.870 --> 01:45:41.880 align:start position:0% made the our packages uh configurable so 01:45:41.880 --> 01:45:43.189 align:start position:0% made the our packages uh configurable so one<01:45:42.119> of<01:45:42.239> the<01:45:42.300> things<01:45:42.420> we've<01:45:42.659> done<01:45:42.780> in<01:45:43.020> the<01:45:43.139> past 01:45:43.189 --> 01:45:43.199 align:start position:0% one of the things we've done in the past 01:45:43.199 --> 01:45:45.590 align:start position:0% one of the things we've done in the past here<01:45:43.440> is<01:45:43.739> we<01:45:43.980> allow<01:45:44.280> you<01:45:44.400> to<01:45:44.760> uh<01:45:45.060> provide<01:45:45.420> your 01:45:45.590 --> 01:45:45.600 align:start position:0% here is we allow you to uh provide your 01:45:45.600 --> 01:45:48.470 align:start position:0% here is we allow you to uh provide your own<01:45:45.719> VM<01:45:46.139> or<01:45:46.679> evm<01:45:47.159> implementation<01:45:47.760> so<01:45:48.360> you 01:45:48.470 --> 01:45:48.480 align:start position:0% own VM or evm implementation so you 01:45:48.480 --> 01:45:49.970 align:start position:0% own VM or evm implementation so you could<01:45:48.600> have<01:45:48.719> a<01:45:48.840> chain<01:45:48.960> that<01:45:49.260> is<01:45:49.619> not<01:45:49.800> like 01:45:49.970 --> 01:45:49.980 align:start position:0% could have a chain that is not like 01:45:49.980 --> 01:45:52.010 align:start position:0% could have a chain that is not like strictly<01:45:50.340> evm<01:45:50.880> or<01:45:51.420> maybe<01:45:51.540> that<01:45:51.719> has<01:45:51.900> like 01:45:52.010 --> 01:45:52.020 align:start position:0% strictly evm or maybe that has like 01:45:52.020 --> 01:45:54.350 align:start position:0% strictly evm or maybe that has like peculiarities<01:45:52.800> or<01:45:53.100> that<01:45:53.280> are<01:45:53.460> evm-like<01:45:54.179> but 01:45:54.350 --> 01:45:54.360 align:start position:0% peculiarities or that are evm-like but 01:45:54.360 --> 01:45:56.270 align:start position:0% peculiarities or that are evm-like but not<01:45:54.480> like<01:45:54.719> strictly<01:45:55.080> the<01:45:55.260> same<01:45:55.440> and<01:45:56.040> you<01:45:56.159> can 01:45:56.270 --> 01:45:56.280 align:start position:0% not like strictly the same and you can 01:45:56.280 --> 01:45:58.189 align:start position:0% not like strictly the same and you can just<01:45:56.460> like<01:45:56.760> parse<01:45:57.540> that<01:45:57.659> in<01:45:57.840> when<01:45:58.020> you 01:45:58.189 --> 01:45:58.199 align:start position:0% just like parse that in when you 01:45:58.199 --> 01:46:00.169 align:start position:0% just like parse that in when you instantiate<01:45:58.739> for<01:45:59.040> example<01:45:59.280> the<01:45:59.639> client<01:46:00.000> you 01:46:00.169 --> 01:46:00.179 align:start position:0% instantiate for example the client you 01:46:00.179 --> 01:46:02.330 align:start position:0% instantiate for example the client you can<01:46:00.300> provide<01:46:00.540> your<01:46:00.719> own<01:46:00.900> like<01:46:01.199> whatever<01:46:01.860> like 01:46:02.330 --> 01:46:02.340 align:start position:0% can provide your own like whatever like 01:46:02.340 --> 01:46:03.709 align:start position:0% can provide your own like whatever like rules<01:46:02.699> you<01:46:02.820> have<01:46:02.940> for<01:46:03.119> your<01:46:03.300> blockchain 01:46:03.709 --> 01:46:03.719 align:start position:0% rules you have for your blockchain 01:46:03.719 --> 01:46:06.229 align:start position:0% rules you have for your blockchain there's<01:46:04.619> obviously<01:46:05.340> like<01:46:05.460> a<01:46:05.699> limit<01:46:05.820> to<01:46:06.060> that 01:46:06.229 --> 01:46:06.239 align:start position:0% there's obviously like a limit to that 01:46:06.239 --> 01:46:07.490 align:start position:0% there's obviously like a limit to that like<01:46:06.420> there's<01:46:06.600> a<01:46:06.780> point<01:46:06.900> where<01:46:07.139> it's<01:46:07.320> probably 01:46:07.490 --> 01:46:07.500 align:start position:0% like there's a point where it's probably 01:46:07.500 --> 01:46:09.050 align:start position:0% like there's a point where it's probably better<01:46:07.739> just<01:46:08.100> to<01:46:08.280> build<01:46:08.400> something<01:46:08.639> else<01:46:08.820> if 01:46:09.050 --> 01:46:09.060 align:start position:0% better just to build something else if 01:46:09.060 --> 01:46:11.330 align:start position:0% better just to build something else if it's<01:46:09.179> like<01:46:09.360> super<01:46:09.600> different<01:46:09.900> but<01:46:10.860> it's<01:46:11.100> still 01:46:11.330 --> 01:46:11.340 align:start position:0% it's like super different but it's still 01:46:11.340 --> 01:46:12.229 align:start position:0% it's like super different but it's still quite 01:46:12.229 --> 01:46:12.239 align:start position:0% quite 01:46:12.239 --> 01:46:12.830 align:start position:0% quite um 01:46:12.830 --> 01:46:12.840 align:start position:0% um 01:46:12.840 --> 01:46:15.590 align:start position:0% um quite<01:46:13.380> configurable<01:46:13.920> so<01:46:14.699> you<01:46:15.000> could<01:46:15.119> also 01:46:15.590 --> 01:46:15.600 align:start position:0% quite configurable so you could also 01:46:15.600 --> 01:46:18.109 align:start position:0% quite configurable so you could also like<01:46:16.139> there<01:46:16.500> are<01:46:16.679> chains<01:46:17.040> like<01:46:17.219> Cela<01:46:17.880> I<01:46:18.000> think 01:46:18.109 --> 01:46:18.119 align:start position:0% like there are chains like Cela I think 01:46:18.119 --> 01:46:19.370 align:start position:0% like there are chains like Cela I think which<01:46:18.300> has<01:46:18.420> like<01:46:18.659> different<01:46:18.840> rules<01:46:19.199> for 01:46:19.370 --> 01:46:19.380 align:start position:0% which has like different rules for 01:46:19.380 --> 01:46:21.590 align:start position:0% which has like different rules for computing<01:46:19.800> transaction<01:46:20.159> hashes<01:46:20.760> and<01:46:21.420> stuff 01:46:21.590 --> 01:46:21.600 align:start position:0% computing transaction hashes and stuff 01:46:21.600 --> 01:46:23.990 align:start position:0% computing transaction hashes and stuff like<01:46:21.780> that<01:46:22.020> uh<01:46:22.980> I'm<01:46:23.219> not<01:46:23.400> like<01:46:23.699> I<01:46:23.880> haven't 01:46:23.990 --> 01:46:24.000 align:start position:0% like that uh I'm not like I haven't 01:46:24.000 --> 01:46:25.490 align:start position:0% like that uh I'm not like I haven't worked<01:46:24.480> with<01:46:24.540> that<01:46:24.659> so<01:46:24.840> I'm<01:46:24.960> not<01:46:25.139> sure<01:46:25.260> how 01:46:25.490 --> 01:46:25.500 align:start position:0% worked with that so I'm not sure how 01:46:25.500 --> 01:46:26.990 align:start position:0% worked with that so I'm not sure how easy<01:46:25.679> would<01:46:25.980> be<01:46:26.100> to<01:46:26.219> configure<01:46:26.580> it<01:46:26.699> but<01:46:26.880> you 01:46:26.990 --> 01:46:27.000 align:start position:0% easy would be to configure it but you 01:46:27.000 --> 01:46:28.550 align:start position:0% easy would be to configure it but you can<01:46:27.119> definitely<01:46:27.420> adjust<01:46:27.780> some<01:46:28.080> parts<01:46:28.260> of<01:46:28.440> the 01:46:28.550 --> 01:46:28.560 align:start position:0% can definitely adjust some parts of the 01:46:28.560 --> 01:46:30.290 align:start position:0% can definitely adjust some parts of the code<01:46:28.739> and<01:46:29.219> provide<01:46:29.460> your<01:46:29.639> own<01:46:29.760> like<01:46:29.940> hashing 01:46:30.290 --> 01:46:30.300 align:start position:0% code and provide your own like hashing 01:46:30.300 --> 01:46:33.649 align:start position:0% code and provide your own like hashing algorithm<01:46:30.780> and<01:46:31.560> uh<01:46:32.100> use<01:46:32.639> that<01:46:32.820> instead<01:46:33.239> same 01:46:33.649 --> 01:46:33.659 align:start position:0% algorithm and uh use that instead same 01:46:33.659 --> 01:46:35.510 align:start position:0% algorithm and uh use that instead same thing<01:46:33.840> with<01:46:34.020> like<01:46:34.199> the<01:46:34.440> Myrtle<01:46:34.860> Beach<01:46:35.040> trees 01:46:35.510 --> 01:46:35.520 align:start position:0% thing with like the Myrtle Beach trees 01:46:35.520 --> 01:46:37.070 align:start position:0% thing with like the Myrtle Beach trees thing<01:46:35.760> we've<01:46:36.179> been<01:46:36.300> working<01:46:36.480> with<01:46:36.719> you<01:46:36.960> could 01:46:37.070 --> 01:46:37.080 align:start position:0% thing we've been working with you could 01:46:37.080 --> 01:46:39.050 align:start position:0% thing we've been working with you could provide<01:46:37.320> your<01:46:37.500> own<01:46:37.679> hashing<01:46:38.340> algorithm<01:46:38.760> it 01:46:39.050 --> 01:46:39.060 align:start position:0% provide your own hashing algorithm it 01:46:39.060 --> 01:46:41.030 align:start position:0% provide your own hashing algorithm it defaults<01:46:39.480> to<01:46:39.540> caca<01:46:40.080> but<01:46:40.260> I<01:46:40.500> mean<01:46:40.619> you<01:46:40.800> can<01:46:40.860> use 01:46:41.030 --> 01:46:41.040 align:start position:0% defaults to caca but I mean you can use 01:46:41.040 --> 01:46:42.470 align:start position:0% defaults to caca but I mean you can use whatever<01:46:41.219> you<01:46:41.520> want 01:46:42.470 --> 01:46:42.480 align:start position:0% whatever you want 01:46:42.480 --> 01:46:44.870 align:start position:0% whatever you want okay<01:46:43.020> thank<01:46:43.500> you 01:46:44.870 --> 01:46:44.880 align:start position:0% okay thank you 01:46:44.880 --> 01:46:48.530 align:start position:0% okay thank you other<01:46:45.719> questions 01:46:48.530 --> 01:46:48.540 align:start position:0% 01:46:48.540 --> 01:46:51.650 align:start position:0% thanks<01:46:49.020> for<01:46:49.139> coming<01:46:49.320> yeah<01:46:49.980> thanks<01:46:50.219> for<01:46:50.400> coming 01:46:51.650 --> 01:46:51.660 align:start position:0% thanks for coming yeah thanks for coming 01:46:51.660 --> 01:46:56.120 align:start position:0% thanks for coming yeah thanks for coming [Applause]