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:18.370 align:start position:0% [Music] 00:00:18.370 --> 00:00:18.380 align:start position:0% 00:00:18.380 --> 00:00:20.630 align:start position:0% o<00:00:19.380> I'm<00:00:19.560> one<00:00:19.740> of<00:00:19.859> the<00:00:19.920> co-founders<00:00:20.400> in<00:00:20.580> the 00:00:20.630 --> 00:00:20.640 align:start position:0% o I'm one of the co-founders in the 00:00:20.640 --> 00:00:22.250 align:start position:0% o I'm one of the co-founders in the general<00:00:20.760> manager<00:00:21.180> for<00:00:21.359> infuri<00:00:21.960> and<00:00:22.199> I'm 00:00:22.250 --> 00:00:22.260 align:start position:0% general manager for infuri and I'm 00:00:22.260 --> 00:00:24.109 align:start position:0% general manager for infuri and I'm joined<00:00:22.560> today<00:00:22.680> with<00:00:22.920> my<00:00:23.220> colleague<00:00:23.400> Tim<00:00:23.699> Myers 00:00:24.109 --> 00:00:24.119 align:start position:0% joined today with my colleague Tim Myers 00:00:24.119 --> 00:00:27.290 align:start position:0% joined today with my colleague Tim Myers one<00:00:24.300> of<00:00:24.420> our<00:00:24.539> lead<00:00:24.660> engineers<00:00:25.140> at<00:00:25.500> inferior<00:00:26.640> so 00:00:27.290 --> 00:00:27.300 align:start position:0% one of our lead engineers at inferior so 00:00:27.300 --> 00:00:29.029 align:start position:0% one of our lead engineers at inferior so you've<00:00:27.779> seen<00:00:27.900> the<00:00:28.080> title<00:00:28.320> of<00:00:28.439> the<00:00:28.560> talk<00:00:28.740> you 00:00:29.029 --> 00:00:29.039 align:start position:0% you've seen the title of the talk you 00:00:29.039 --> 00:00:30.710 align:start position:0% you've seen the title of the talk you might<00:00:29.160> have<00:00:29.340> caught<00:00:29.699> our<00:00:30.000> announcement<00:00:30.480> at 00:00:30.710 --> 00:00:30.720 align:start position:0% might have caught our announcement at 00:00:30.720 --> 00:00:32.630 align:start position:0% might have caught our announcement at East<00:00:30.840> Berlin<00:00:31.260> a<00:00:31.500> month<00:00:31.619> ago<00:00:31.980> we're<00:00:32.340> here<00:00:32.520> to 00:00:32.630 --> 00:00:32.640 align:start position:0% East Berlin a month ago we're here to 00:00:32.640 --> 00:00:35.150 align:start position:0% East Berlin a month ago we're here to talk<00:00:32.820> about<00:00:33.000> decentralizing<00:00:33.840> inferior<00:00:34.440> it's 00:00:35.150 --> 00:00:35.160 align:start position:0% talk about decentralizing inferior it's 00:00:35.160 --> 00:00:37.190 align:start position:0% talk about decentralizing inferior it's something<00:00:35.340> that's<00:00:35.640> been<00:00:35.940> on<00:00:36.719> the<00:00:37.079> Twitter 00:00:37.190 --> 00:00:37.200 align:start position:0% something that's been on the Twitter 00:00:37.200 --> 00:00:39.350 align:start position:0% something that's been on the Twitter waves<00:00:37.739> and<00:00:37.920> crypto<00:00:38.219> Twitter<00:00:38.460> for<00:00:39.120> years 00:00:39.350 --> 00:00:39.360 align:start position:0% waves and crypto Twitter for years 00:00:39.360 --> 00:00:41.510 align:start position:0% waves and crypto Twitter for years something<00:00:40.260> that<00:00:40.500> people<00:00:40.620> ask<00:00:40.920> us<00:00:41.100> about<00:00:41.219> all 00:00:41.510 --> 00:00:41.520 align:start position:0% something that people ask us about all 00:00:41.520 --> 00:00:43.850 align:start position:0% something that people ask us about all the<00:00:41.700> time<00:00:41.940> like<00:00:42.600> is<00:00:42.780> inferior<00:00:43.379> centralized 00:00:43.850 --> 00:00:43.860 align:start position:0% the time like is inferior centralized 00:00:43.860 --> 00:00:46.010 align:start position:0% the time like is inferior centralized how<00:00:44.100> are<00:00:44.219> you<00:00:44.280> going<00:00:44.399> to<00:00:44.579> decentralize 00:00:46.010 --> 00:00:46.020 align:start position:0% how are you going to decentralize 00:00:46.020 --> 00:00:48.590 align:start position:0% how are you going to decentralize are<00:00:46.559> you<00:00:46.680> going<00:00:46.800> to<00:00:46.980> decentralize<00:00:47.640> this<00:00:48.420> is 00:00:48.590 --> 00:00:48.600 align:start position:0% are you going to decentralize this is 00:00:48.600 --> 00:00:50.690 align:start position:0% are you going to decentralize this is this<00:00:48.960> is<00:00:49.079> the<00:00:49.200> talk<00:00:49.320> where<00:00:49.559> we<00:00:49.739> answer<00:00:49.980> quite<00:00:50.579> a 00:00:50.690 --> 00:00:50.700 align:start position:0% this is the talk where we answer quite a 00:00:50.700 --> 00:00:53.150 align:start position:0% this is the talk where we answer quite a few<00:00:50.760> of<00:00:50.879> those<00:00:51.000> questions<00:00:51.300> for<00:00:51.719> you<00:00:51.899> we<00:00:52.860> gave 00:00:53.150 --> 00:00:53.160 align:start position:0% few of those questions for you we gave 00:00:53.160 --> 00:00:55.130 align:start position:0% few of those questions for you we gave you<00:00:53.340> a<00:00:53.460> preview<00:00:53.760> at<00:00:54.180> eath<00:00:54.539> Berlin<00:00:54.840> if<00:00:55.020> you're 00:00:55.130 --> 00:00:55.140 align:start position:0% you a preview at eath Berlin if you're 00:00:55.140 --> 00:00:56.689 align:start position:0% you a preview at eath Berlin if you're able<00:00:55.320> to<00:00:55.379> see<00:00:55.500> the<00:00:55.680> recording<00:00:56.039> from<00:00:56.219> that<00:00:56.399> talk 00:00:56.689 --> 00:00:56.699 align:start position:0% able to see the recording from that talk 00:00:56.699 --> 00:00:58.910 align:start position:0% able to see the recording from that talk this<00:00:57.480> is<00:00:57.600> going<00:00:57.780> to<00:00:57.960> go<00:00:58.199> more<00:00:58.440> into<00:00:58.620> the 00:00:58.910 --> 00:00:58.920 align:start position:0% this is going to go more into the 00:00:58.920 --> 00:01:01.670 align:start position:0% this is going to go more into the details<00:00:59.340> of<00:00:59.520> the<00:00:59.760> why<00:01:00.000> behind<00:01:00.660> it<00:01:00.840> the<00:01:01.199> why<00:01:01.379> now 00:01:01.670 --> 00:01:01.680 align:start position:0% details of the why behind it the why now 00:01:01.680 --> 00:01:04.969 align:start position:0% details of the why behind it the why now what<00:01:02.520> now<00:01:02.840> and<00:01:03.840> especially<00:01:04.260> the<00:01:04.619> technical 00:01:04.969 --> 00:01:04.979 align:start position:0% what now and especially the technical 00:01:04.979 --> 00:01:07.370 align:start position:0% what now and especially the technical details<00:01:05.460> that<00:01:05.700> go<00:01:05.939> into<00:01:06.380> decentralizing 00:01:07.370 --> 00:01:07.380 align:start position:0% details that go into decentralizing 00:01:07.380 --> 00:01:09.590 align:start position:0% details that go into decentralizing inferior 00:01:09.590 --> 00:01:09.600 align:start position:0% inferior 00:01:09.600 --> 00:01:10.670 align:start position:0% inferior so 00:01:10.670 --> 00:01:10.680 align:start position:0% so 00:01:10.680 --> 00:01:13.190 align:start position:0% so inferior<00:01:11.340> was<00:01:11.460> launched<00:01:11.760> in<00:01:11.880> 2016<00:01:12.420> with<00:01:13.020> the 00:01:13.190 --> 00:01:13.200 align:start position:0% inferior was launched in 2016 with the 00:01:13.200 --> 00:01:15.590 align:start position:0% inferior was launched in 2016 with the sole<00:01:13.439> purpose<00:01:13.740> of<00:01:14.220> providing<00:01:14.939> utility<00:01:15.299> for 00:01:15.590 --> 00:01:15.600 align:start position:0% sole purpose of providing utility for 00:01:15.600 --> 00:01:18.109 align:start position:0% sole purpose of providing utility for ethereum<00:01:16.080> and<00:01:16.200> ipfs<00:01:16.740> Developers 00:01:18.109 --> 00:01:18.119 align:start position:0% ethereum and ipfs Developers 00:01:18.119 --> 00:01:19.789 align:start position:0% ethereum and ipfs Developers it's<00:01:18.540> something<00:01:18.720> I<00:01:18.900> say<00:01:19.020> in<00:01:19.140> all<00:01:19.320> of<00:01:19.380> my<00:01:19.500> talks 00:01:19.789 --> 00:01:19.799 align:start position:0% it's something I say in all of my talks 00:01:19.799 --> 00:01:21.230 align:start position:0% it's something I say in all of my talks because<00:01:19.920> I<00:01:20.159> I<00:01:20.340> want<00:01:20.520> to<00:01:20.640> make<00:01:20.759> it<00:01:20.939> very<00:01:21.060> clear 00:01:21.230 --> 00:01:21.240 align:start position:0% because I I want to make it very clear 00:01:21.240 --> 00:01:23.090 align:start position:0% because I I want to make it very clear that<00:01:21.600> inferior<00:01:22.320> was<00:01:22.439> always<00:01:22.560> about<00:01:22.799> the 00:01:23.090 --> 00:01:23.100 align:start position:0% that inferior was always about the 00:01:23.100 --> 00:01:25.010 align:start position:0% that inferior was always about the developers<00:01:23.520> and<00:01:23.820> making<00:01:24.000> sure<00:01:24.299> that 00:01:25.010 --> 00:01:25.020 align:start position:0% developers and making sure that 00:01:25.020 --> 00:01:27.230 align:start position:0% developers and making sure that developers<00:01:25.619> that<00:01:25.979> are<00:01:26.159> building<00:01:26.400> on<00:01:26.820> web3 00:01:27.230 --> 00:01:27.240 align:start position:0% developers that are building on web3 00:01:27.240 --> 00:01:29.810 align:start position:0% developers that are building on web3 which<00:01:28.080> for<00:01:28.200> us<00:01:28.380> was<00:01:28.560> initially<00:01:28.860> ethereum<00:01:29.460> and 00:01:29.810 --> 00:01:29.820 align:start position:0% which for us was initially ethereum and 00:01:29.820 --> 00:01:33.050 align:start position:0% which for us was initially ethereum and ipfs<00:01:30.479> could<00:01:31.380> quickly<00:01:31.799> get<00:01:31.979> started<00:01:32.400> and<00:01:32.939> we 00:01:33.050 --> 00:01:33.060 align:start position:0% ipfs could quickly get started and we 00:01:33.060 --> 00:01:34.130 align:start position:0% ipfs could quickly get started and we did<00:01:33.240> that 00:01:34.130 --> 00:01:34.140 align:start position:0% did that 00:01:34.140 --> 00:01:36.530 align:start position:0% did that at<00:01:34.740> Devcon<00:01:35.400> 2. 00:01:36.530 --> 00:01:36.540 align:start position:0% at Devcon 2. 00:01:36.540 --> 00:01:38.810 align:start position:0% at Devcon 2. it<00:01:37.439> was<00:01:37.500> four<00:01:37.680> of<00:01:37.860> us<00:01:37.979> from<00:01:38.100> the<00:01:38.280> inferior<00:01:38.640> team 00:01:38.810 --> 00:01:38.820 align:start position:0% it was four of us from the inferior team 00:01:38.820 --> 00:01:41.390 align:start position:0% it was four of us from the inferior team we<00:01:39.060> flew<00:01:39.360> to<00:01:39.420> Devcon<00:01:39.900> at<00:01:40.619> the<00:01:40.740> time<00:01:40.860> we<00:01:41.100> were<00:01:41.220> a 00:01:41.390 --> 00:01:41.400 align:start position:0% we flew to Devcon at the time we were a 00:01:41.400 --> 00:01:44.030 align:start position:0% we flew to Devcon at the time we were a small<00:01:41.700> team<00:01:41.960> within<00:01:42.960> the<00:01:43.140> larger<00:01:43.380> consensus 00:01:44.030 --> 00:01:44.040 align:start position:0% small team within the larger consensus 00:01:44.040 --> 00:01:46.370 align:start position:0% small team within the larger consensus organization<00:01:44.759> focused<00:01:45.659> on<00:01:45.780> trying<00:01:46.079> to<00:01:46.259> build 00:01:46.370 --> 00:01:46.380 align:start position:0% organization focused on trying to build 00:01:46.380 --> 00:01:48.230 align:start position:0% organization focused on trying to build something<00:01:46.680> that<00:01:46.920> would<00:01:47.100> be<00:01:47.220> useful 00:01:48.230 --> 00:01:48.240 align:start position:0% something that would be useful 00:01:48.240 --> 00:01:49.910 align:start position:0% something that would be useful and<00:01:48.659> so<00:01:48.780> we<00:01:48.900> all<00:01:49.020> went<00:01:49.200> to<00:01:49.320> this<00:01:49.500> conference 00:01:49.910 --> 00:01:49.920 align:start position:0% and so we all went to this conference 00:01:49.920 --> 00:01:51.830 align:start position:0% and so we all went to this conference and<00:01:50.460> we<00:01:50.579> were<00:01:50.759> saying<00:01:51.119> that<00:01:51.420> we<00:01:51.540> were<00:01:51.659> going<00:01:51.780> to 00:01:51.830 --> 00:01:51.840 align:start position:0% and we were saying that we were going to 00:01:51.840 --> 00:01:54.289 align:start position:0% and we were saying that we were going to get<00:01:51.960> up<00:01:52.079> on<00:01:52.259> that<00:01:52.439> stage<00:01:52.680> and<00:01:53.040> say<00:01:53.280> there's<00:01:54.000> a 00:01:54.289 --> 00:01:54.299 align:start position:0% get up on that stage and say there's a 00:01:54.299 --> 00:01:55.490 align:start position:0% get up on that stage and say there's a lot<00:01:54.360> of<00:01:54.479> innovation<00:01:54.780> that's<00:01:55.020> happening<00:01:55.320> in 00:01:55.490 --> 00:01:55.500 align:start position:0% lot of innovation that's happening in 00:01:55.500 --> 00:01:57.230 align:start position:0% lot of innovation that's happening in this<00:01:55.680> space<00:01:55.920> we've<00:01:56.520> created<00:01:56.820> this<00:01:57.060> new 00:01:57.230 --> 00:01:57.240 align:start position:0% this space we've created this new 00:01:57.240 --> 00:01:59.389 align:start position:0% this space we've created this new service<00:01:57.420> called<00:01:57.720> inferior<00:01:58.380> and<00:01:59.100> it's<00:01:59.220> a 00:01:59.389 --> 00:01:59.399 align:start position:0% service called inferior and it's a 00:01:59.399 --> 00:02:01.010 align:start position:0% service called inferior and it's a traditional<00:01:59.759> SAS<00:02:00.119> service<00:02:00.360> that<00:02:00.659> you<00:02:00.780> can<00:02:00.840> use 00:02:01.010 --> 00:02:01.020 align:start position:0% traditional SAS service that you can use 00:02:01.020 --> 00:02:03.710 align:start position:0% traditional SAS service that you can use to<00:02:01.320> connect<00:02:01.500> to<00:02:01.860> blockchains 00:02:03.710 --> 00:02:03.720 align:start position:0% to connect to blockchains 00:02:03.720 --> 00:02:05.330 align:start position:0% to connect to blockchains and<00:02:04.079> we<00:02:04.200> had<00:02:04.320> a<00:02:04.439> lot<00:02:04.560> of<00:02:04.680> apprehension<00:02:05.159> about 00:02:05.330 --> 00:02:05.340 align:start position:0% and we had a lot of apprehension about 00:02:05.340 --> 00:02:07.910 align:start position:0% and we had a lot of apprehension about that<00:02:05.759> like<00:02:06.540> what<00:02:06.719> would<00:02:06.960> the<00:02:07.140> reception<00:02:07.560> to 00:02:07.910 --> 00:02:07.920 align:start position:0% that like what would the reception to 00:02:07.920 --> 00:02:09.770 align:start position:0% that like what would the reception to that<00:02:08.099> be<00:02:08.340> because<00:02:08.759> at<00:02:09.060> the<00:02:09.179> time<00:02:09.300> we<00:02:09.479> were<00:02:09.660> all 00:02:09.770 --> 00:02:09.780 align:start position:0% that be because at the time we were all 00:02:09.780 --> 00:02:11.449 align:start position:0% that be because at the time we were all running<00:02:09.959> our<00:02:10.440> own<00:02:10.560> infrastructure<00:02:11.099> we<00:02:11.340> were 00:02:11.449 --> 00:02:11.459 align:start position:0% running our own infrastructure we were 00:02:11.459 --> 00:02:13.850 align:start position:0% running our own infrastructure we were all<00:02:11.580> running<00:02:11.700> our<00:02:11.940> own<00:02:12.060> nodes<00:02:12.420> there<00:02:13.319> was<00:02:13.500> very 00:02:13.850 --> 00:02:13.860 align:start position:0% all running our own nodes there was very 00:02:13.860 --> 00:02:17.050 align:start position:0% all running our own nodes there was very much<00:02:14.099> a<00:02:14.760> lot<00:02:15.000> of<00:02:15.120> interest<00:02:15.360> in<00:02:15.720> like<00:02:16.319> clients 00:02:17.050 --> 00:02:17.060 align:start position:0% much a lot of interest in like clients 00:02:17.060 --> 00:02:20.750 align:start position:0% much a lot of interest in like clients verifiability<00:02:18.060> of<00:02:18.360> data<00:02:18.800> and<00:02:19.800> we<00:02:20.220> were<00:02:20.340> saying 00:02:20.750 --> 00:02:20.760 align:start position:0% verifiability of data and we were saying 00:02:20.760 --> 00:02:23.210 align:start position:0% verifiability of data and we were saying don't<00:02:21.599> run<00:02:21.900> your<00:02:22.080> own<00:02:22.200> infrastructure<00:02:22.800> trust 00:02:23.210 --> 00:02:23.220 align:start position:0% don't run your own infrastructure trust 00:02:23.220 --> 00:02:26.270 align:start position:0% don't run your own infrastructure trust us<00:02:23.400> to<00:02:23.580> run<00:02:23.700> your<00:02:23.879> infrastructure<00:02:24.480> and<00:02:25.379> so<00:02:25.680> the 00:02:26.270 --> 00:02:26.280 align:start position:0% us to run your infrastructure and so the 00:02:26.280 --> 00:02:29.330 align:start position:0% us to run your infrastructure and so the the<00:02:26.340> reception<00:02:26.940> at<00:02:27.300> Devcon<00:02:27.780> was<00:02:28.560> a<00:02:29.099> little 00:02:29.330 --> 00:02:29.340 align:start position:0% the reception at Devcon was a little 00:02:29.340 --> 00:02:31.010 align:start position:0% the reception at Devcon was a little mixed<00:02:29.760> some<00:02:30.000> people<00:02:30.180> were<00:02:30.300> like<00:02:30.480> okay<00:02:30.660> great 00:02:31.010 --> 00:02:31.020 align:start position:0% mixed some people were like okay great 00:02:31.020 --> 00:02:32.990 align:start position:0% mixed some people were like okay great I'm<00:02:31.260> going<00:02:31.379> to<00:02:31.440> use<00:02:31.620> that<00:02:31.800> other<00:02:32.459> people<00:02:32.700> said 00:02:32.990 --> 00:02:33.000 align:start position:0% I'm going to use that other people said 00:02:33.000 --> 00:02:35.030 align:start position:0% I'm going to use that other people said but<00:02:33.300> why<00:02:33.540> would<00:02:33.720> I<00:02:33.900> want<00:02:34.080> to<00:02:34.200> do<00:02:34.379> that<00:02:34.560> I<00:02:34.920> can 00:02:35.030 --> 00:02:35.040 align:start position:0% but why would I want to do that I can 00:02:35.040 --> 00:02:36.589 align:start position:0% but why would I want to do that I can just<00:02:35.220> run<00:02:35.400> my<00:02:35.640> own<00:02:35.760> node<00:02:36.060> and<00:02:36.239> it's<00:02:36.360> going<00:02:36.540> to 00:02:36.589 --> 00:02:36.599 align:start position:0% just run my own node and it's going to 00:02:36.599 --> 00:02:38.510 align:start position:0% just run my own node and it's going to sink<00:02:36.780> in<00:02:36.959> an<00:02:37.140> hour<00:02:37.319> and<00:02:37.800> then<00:02:37.920> I<00:02:38.220> don't<00:02:38.340> need 00:02:38.510 --> 00:02:38.520 align:start position:0% sink in an hour and then I don't need 00:02:38.520 --> 00:02:39.530 align:start position:0% sink in an hour and then I don't need you<00:02:38.640> anymore 00:02:39.530 --> 00:02:39.540 align:start position:0% you anymore 00:02:39.540 --> 00:02:43.130 align:start position:0% you anymore and<00:02:40.500> uh<00:02:40.860> so<00:02:41.700> we<00:02:42.180> said<00:02:42.420> well 00:02:43.130 --> 00:02:43.140 align:start position:0% and uh so we said well 00:02:43.140 --> 00:02:44.750 align:start position:0% and uh so we said well that<00:02:43.800> might<00:02:43.920> be<00:02:44.040> the<00:02:44.160> case<00:02:44.280> but<00:02:44.519> we're<00:02:44.640> going 00:02:44.750 --> 00:02:44.760 align:start position:0% that might be the case but we're going 00:02:44.760 --> 00:02:46.309 align:start position:0% that might be the case but we're going to<00:02:44.819> try<00:02:45.000> it<00:02:45.180> like<00:02:45.420> we're<00:02:45.599> just<00:02:45.780> here<00:02:45.959> to<00:02:46.080> try<00:02:46.200> to 00:02:46.309 --> 00:02:46.319 align:start position:0% to try it like we're just here to try to 00:02:46.319 --> 00:02:47.809 align:start position:0% to try it like we're just here to try to provide<00:02:46.620> something<00:02:46.860> useful<00:02:47.220> and<00:02:47.519> maybe<00:02:47.640> that 00:02:47.809 --> 00:02:47.819 align:start position:0% provide something useful and maybe that 00:02:47.819 --> 00:02:50.030 align:start position:0% provide something useful and maybe that will<00:02:47.940> be<00:02:48.060> useful<00:02:48.300> and<00:02:48.420> maybe<00:02:48.599> it<00:02:48.720> won't<00:02:48.900> be<00:02:49.080> and 00:02:50.030 --> 00:02:50.040 align:start position:0% will be useful and maybe it won't be and 00:02:50.040 --> 00:02:52.309 align:start position:0% will be useful and maybe it won't be and uh<00:02:50.340> so<00:02:50.580> we<00:02:50.700> went<00:02:50.879> up<00:02:51.060> on<00:02:51.239> stage<00:02:51.480> and<00:02:51.660> we<00:02:51.900> we 00:02:52.309 --> 00:02:52.319 align:start position:0% uh so we went up on stage and we we 00:02:52.319 --> 00:02:53.630 align:start position:0% uh so we went up on stage and we we announced<00:02:52.739> that<00:02:52.860> we<00:02:52.980> were<00:02:53.099> going<00:02:53.220> to<00:02:53.340> be<00:02:53.459> doing 00:02:53.630 --> 00:02:53.640 align:start position:0% announced that we were going to be doing 00:02:53.640 --> 00:02:54.589 align:start position:0% announced that we were going to be doing this 00:02:54.589 --> 00:02:54.599 align:start position:0% this 00:02:54.599 --> 00:02:57.110 align:start position:0% this and<00:02:55.019> then<00:02:55.140> during<00:02:55.379> Defcon<00:02:55.980> 2<00:02:56.280> the<00:02:56.760> ethereum 00:02:57.110 --> 00:02:57.120 align:start position:0% and then during Defcon 2 the ethereum 00:02:57.120 --> 00:02:59.990 align:start position:0% and then during Defcon 2 the ethereum network<00:02:57.300> was<00:02:57.780> uh<00:02:58.739> subjected<00:02:59.280> to<00:02:59.519> the<00:02:59.700> denial 00:02:59.990 --> 00:03:00.000 align:start position:0% network was uh subjected to the denial 00:03:00.000 --> 00:03:01.970 align:start position:0% network was uh subjected to the denial of<00:03:00.180> service<00:03:00.360> attacks<00:03:00.959> that<00:03:01.440> almost<00:03:01.620> brought 00:03:01.970 --> 00:03:01.980 align:start position:0% of service attacks that almost brought 00:03:01.980 --> 00:03:04.610 align:start position:0% of service attacks that almost brought down<00:03:02.160> the<00:03:02.340> network<00:03:02.599> and<00:03:03.599> some<00:03:03.840> of<00:03:03.959> the<00:03:04.080> many<00:03:04.379> of 00:03:04.610 --> 00:03:04.620 align:start position:0% down the network and some of the many of 00:03:04.620 --> 00:03:06.470 align:start position:0% down the network and some of the many of the<00:03:04.739> heroes<00:03:05.160> that<00:03:05.640> helped<00:03:06.000> save<00:03:06.180> the<00:03:06.360> network 00:03:06.470 --> 00:03:06.480 align:start position:0% the heroes that helped save the network 00:03:06.480 --> 00:03:08.030 align:start position:0% the heroes that helped save the network from<00:03:06.780> that<00:03:06.900> are<00:03:07.080> either<00:03:07.260> in<00:03:07.440> this<00:03:07.620> room<00:03:07.800> or 00:03:08.030 --> 00:03:08.040 align:start position:0% from that are either in this room or 00:03:08.040 --> 00:03:09.589 align:start position:0% from that are either in this room or definitely<00:03:08.340> at<00:03:08.640> this<00:03:08.819> conference<00:03:09.180> the<00:03:09.480> people 00:03:09.589 --> 00:03:09.599 align:start position:0% definitely at this conference the people 00:03:09.599 --> 00:03:11.990 align:start position:0% definitely at this conference the people that<00:03:09.900> helped<00:03:10.319> mitigate<00:03:11.159> the<00:03:11.340> attacks<00:03:11.700> on<00:03:11.879> the 00:03:11.990 --> 00:03:12.000 align:start position:0% that helped mitigate the attacks on the 00:03:12.000 --> 00:03:14.210 align:start position:0% that helped mitigate the attacks on the network<00:03:12.120> and<00:03:12.780> inferior's<00:03:13.440> role<00:03:13.680> in<00:03:13.739> that<00:03:13.920> at 00:03:14.210 --> 00:03:14.220 align:start position:0% network and inferior's role in that at 00:03:14.220 --> 00:03:16.309 align:start position:0% network and inferior's role in that at the<00:03:14.340> time<00:03:14.459> was<00:03:14.940> trying<00:03:15.300> to<00:03:15.540> keep<00:03:15.659> our<00:03:15.900> endpoint 00:03:16.309 --> 00:03:16.319 align:start position:0% the time was trying to keep our endpoint 00:03:16.319 --> 00:03:18.410 align:start position:0% the time was trying to keep our endpoint up<00:03:16.620> that<00:03:17.280> was<00:03:17.400> already<00:03:17.580> being<00:03:17.940> used<00:03:18.120> to<00:03:18.300> sort 00:03:18.410 --> 00:03:18.420 align:start position:0% up that was already being used to sort 00:03:18.420 --> 00:03:21.350 align:start position:0% up that was already being used to sort of<00:03:18.599> metamask<00:03:19.140> mother<00:03:19.800> mask<00:03:20.040> had<00:03:20.340> launched<00:03:20.700> uh 00:03:21.350 --> 00:03:21.360 align:start position:0% of metamask mother mask had launched uh 00:03:21.360 --> 00:03:24.649 align:start position:0% of metamask mother mask had launched uh two<00:03:21.959> three<00:03:22.260> months<00:03:22.560> beforehand<00:03:23.239> and<00:03:24.239> uh 00:03:24.649 --> 00:03:24.659 align:start position:0% two three months beforehand and uh 00:03:24.659 --> 00:03:26.210 align:start position:0% two three months beforehand and uh thousands<00:03:25.080> of<00:03:25.140> users<00:03:25.440> were<00:03:25.680> already<00:03:25.860> using 00:03:26.210 --> 00:03:26.220 align:start position:0% thousands of users were already using 00:03:26.220 --> 00:03:28.970 align:start position:0% thousands of users were already using metamask<00:03:26.700> every<00:03:27.000> day<00:03:27.180> to<00:03:27.599> send<00:03:28.019> ether<00:03:28.440> do<00:03:28.739> some 00:03:28.970 --> 00:03:28.980 align:start position:0% metamask every day to send ether do some 00:03:28.980 --> 00:03:31.309 align:start position:0% metamask every day to send ether do some basic<00:03:29.220> interactions<00:03:29.879> with<00:03:30.300> some<00:03:30.780> of<00:03:30.900> like<00:03:31.080> the 00:03:31.309 --> 00:03:31.319 align:start position:0% basic interactions with some of like the 00:03:31.319 --> 00:03:33.110 align:start position:0% basic interactions with some of like the early<00:03:31.500> maker<00:03:32.159> contracts<00:03:32.580> that<00:03:32.760> were<00:03:32.879> out 00:03:33.110 --> 00:03:33.120 align:start position:0% early maker contracts that were out 00:03:33.120 --> 00:03:34.250 align:start position:0% early maker contracts that were out there<00:03:33.300> some<00:03:33.599> of<00:03:33.720> the<00:03:33.840> early<00:03:33.959> other 00:03:34.250 --> 00:03:34.260 align:start position:0% there some of the early other 00:03:34.260 --> 00:03:35.449 align:start position:0% there some of the early other experiments<00:03:34.800> that<00:03:34.920> were<00:03:35.040> out<00:03:35.159> there<00:03:35.280> around 00:03:35.449 --> 00:03:35.459 align:start position:0% experiments that were out there around 00:03:35.459 --> 00:03:37.490 align:start position:0% experiments that were out there around that<00:03:35.819> 2016<00:03:36.360> time 00:03:37.490 --> 00:03:37.500 align:start position:0% that 2016 time 00:03:37.500 --> 00:03:39.530 align:start position:0% that 2016 time and<00:03:38.280> we<00:03:38.700> said 00:03:39.530 --> 00:03:39.540 align:start position:0% and we said 00:03:39.540 --> 00:03:41.449 align:start position:0% and we said well<00:03:40.080> we<00:03:40.379> can't<00:03:40.440> do<00:03:40.620> anything<00:03:40.799> actively<00:03:41.280> to 00:03:41.449 --> 00:03:41.459 align:start position:0% well we can't do anything actively to 00:03:41.459 --> 00:03:42.949 align:start position:0% well we can't do anything actively to fix<00:03:41.580> that<00:03:41.760> client<00:03:42.000> we're<00:03:42.239> not<00:03:42.420> the<00:03:42.659> protocol 00:03:42.949 --> 00:03:42.959 align:start position:0% fix that client we're not the protocol 00:03:42.959 --> 00:03:44.809 align:start position:0% fix that client we're not the protocol core<00:03:43.440> developers<00:03:43.860> the<00:03:44.099> core<00:03:44.220> developers<00:03:44.640> are 00:03:44.809 --> 00:03:44.819 align:start position:0% core developers the core developers are 00:03:44.819 --> 00:03:47.449 align:start position:0% core developers the core developers are solving<00:03:45.180> that<00:03:45.360> problem<00:03:45.799> but<00:03:46.799> there<00:03:47.340> was 00:03:47.449 --> 00:03:47.459 align:start position:0% solving that problem but there was 00:03:47.459 --> 00:03:49.430 align:start position:0% solving that problem but there was already<00:03:47.700> this<00:03:48.180> issue<00:03:48.599> where 00:03:49.430 --> 00:03:49.440 align:start position:0% already this issue where 00:03:49.440 --> 00:03:52.009 align:start position:0% already this issue where we<00:03:49.860> were<00:03:49.920> in<00:03:50.099> Shanghai<00:03:50.580> the<00:03:51.299> Wi-Fi<00:03:51.599> there<00:03:51.840> was 00:03:52.009 --> 00:03:52.019 align:start position:0% we were in Shanghai the Wi-Fi there was 00:03:52.019 --> 00:03:54.170 align:start position:0% we were in Shanghai the Wi-Fi there was awful<00:03:52.379> even<00:03:53.340> worse<00:03:53.640> than<00:03:53.819> at<00:03:54.000> most 00:03:54.170 --> 00:03:54.180 align:start position:0% awful even worse than at most 00:03:54.180 --> 00:03:56.930 align:start position:0% awful even worse than at most conferences<00:03:54.780> and<00:03:55.680> nobody<00:03:55.920> was<00:03:56.159> able<00:03:56.400> to<00:03:56.700> like 00:03:56.930 --> 00:03:56.940 align:start position:0% conferences and nobody was able to like 00:03:56.940 --> 00:03:58.910 align:start position:0% conferences and nobody was able to like get<00:03:57.360> access<00:03:57.599> to<00:03:57.959> their<00:03:58.140> infrastructure<00:03:58.680> to 00:03:58.910 --> 00:03:58.920 align:start position:0% get access to their infrastructure to 00:03:58.920 --> 00:04:00.890 align:start position:0% get access to their infrastructure to update<00:03:59.280> their<00:03:59.519> clients<00:03:59.819> once<00:04:00.360> the<00:04:00.599> actual 00:04:00.890 --> 00:04:00.900 align:start position:0% update their clients once the actual 00:04:00.900 --> 00:04:04.130 align:start position:0% update their clients once the actual client<00:04:01.440> development<00:04:01.860> teams<00:04:02.340> had<00:04:02.959> put<00:04:03.959> out 00:04:04.130 --> 00:04:04.140 align:start position:0% client development teams had put out 00:04:04.140 --> 00:04:06.949 align:start position:0% client development teams had put out these<00:04:04.379> updates<00:04:04.799> and<00:04:05.459> so<00:04:05.760> our<00:04:06.299> inferior<00:04:06.780> team 00:04:06.949 --> 00:04:06.959 align:start position:0% these updates and so our inferior team 00:04:06.959 --> 00:04:08.509 align:start position:0% these updates and so our inferior team was<00:04:07.080> sitting<00:04:07.379> there<00:04:07.560> in<00:04:07.799> the<00:04:08.040> lobby<00:04:08.220> of<00:04:08.400> the 00:04:08.509 --> 00:04:08.519 align:start position:0% was sitting there in the lobby of the 00:04:08.519 --> 00:04:11.449 align:start position:0% was sitting there in the lobby of the hotel<00:04:08.700> updating<00:04:09.659> our<00:04:09.900> endpoints<00:04:10.500> so<00:04:11.040> that<00:04:11.220> the 00:04:11.449 --> 00:04:11.459 align:start position:0% hotel updating our endpoints so that the 00:04:11.459 --> 00:04:12.830 align:start position:0% hotel updating our endpoints so that the thousands<00:04:11.879> of<00:04:12.060> users<00:04:12.360> that<00:04:12.540> were<00:04:12.659> using 00:04:12.830 --> 00:04:12.840 align:start position:0% thousands of users that were using 00:04:12.840 --> 00:04:14.210 align:start position:0% thousands of users that were using metamask<00:04:13.319> that<00:04:13.560> might<00:04:13.739> have<00:04:13.860> been<00:04:13.980> pointing 00:04:14.210 --> 00:04:14.220 align:start position:0% metamask that might have been pointing 00:04:14.220 --> 00:04:15.710 align:start position:0% metamask that might have been pointing metamask<00:04:14.700> at<00:04:14.879> their<00:04:15.000> own<00:04:15.120> infrastructure 00:04:15.710 --> 00:04:15.720 align:start position:0% metamask at their own infrastructure 00:04:15.720 --> 00:04:18.349 align:start position:0% metamask at their own infrastructure could<00:04:16.440> use<00:04:16.680> inferior<00:04:17.519> until<00:04:18.060> their 00:04:18.349 --> 00:04:18.359 align:start position:0% could use inferior until their 00:04:18.359 --> 00:04:20.270 align:start position:0% could use inferior until their infrastructure<00:04:18.900> came<00:04:19.139> back<00:04:19.320> online 00:04:20.270 --> 00:04:20.280 align:start position:0% infrastructure came back online 00:04:20.280 --> 00:04:22.550 align:start position:0% infrastructure came back online and<00:04:20.940> so<00:04:21.180> that<00:04:21.540> started<00:04:21.840> to<00:04:21.959> highlight<00:04:22.199> one<00:04:22.440> of 00:04:22.550 --> 00:04:22.560 align:start position:0% and so that started to highlight one of 00:04:22.560 --> 00:04:25.550 align:start position:0% and so that started to highlight one of the<00:04:22.620> value<00:04:22.800> props<00:04:23.220> that<00:04:23.400> we<00:04:23.520> saw<00:04:23.759> which<00:04:24.720> was<00:04:25.020> by 00:04:25.550 --> 00:04:25.560 align:start position:0% the value props that we saw which was by 00:04:25.560 --> 00:04:27.650 align:start position:0% the value props that we saw which was by having<00:04:25.740> this<00:04:26.040> centralized<00:04:26.580> point<00:04:26.820> we<00:04:27.479> could 00:04:27.650 --> 00:04:27.660 align:start position:0% having this centralized point we could 00:04:27.660 --> 00:04:29.090 align:start position:0% having this centralized point we could simplify 00:04:29.090 --> 00:04:29.100 align:start position:0% simplify 00:04:29.100 --> 00:04:31.730 align:start position:0% simplify um<00:04:29.520> or<00:04:30.060> try<00:04:30.540> to<00:04:30.720> eliminate<00:04:31.080> a<00:04:31.259> lot<00:04:31.320> of<00:04:31.440> the<00:04:31.500> pain 00:04:31.730 --> 00:04:31.740 align:start position:0% um or try to eliminate a lot of the pain 00:04:31.740 --> 00:04:34.490 align:start position:0% um or try to eliminate a lot of the pain for<00:04:31.979> these<00:04:32.220> users<00:04:32.580> by 00:04:34.490 --> 00:04:34.500 align:start position:0% for these users by 00:04:34.500 --> 00:04:36.830 align:start position:0% for these users by um<00:04:34.560> yes<00:04:34.979> we'll<00:04:35.220> take<00:04:35.460> on<00:04:35.639> this<00:04:35.820> like<00:04:36.060> aspect<00:04:36.660> of 00:04:36.830 --> 00:04:36.840 align:start position:0% um yes we'll take on this like aspect of 00:04:36.840 --> 00:04:38.870 align:start position:0% um yes we'll take on this like aspect of centralization<00:04:37.560> but<00:04:38.340> for<00:04:38.580> the<00:04:38.699> most<00:04:38.759> part 00:04:38.870 --> 00:04:38.880 align:start position:0% centralization but for the most part 00:04:38.880 --> 00:04:40.610 align:start position:0% centralization but for the most part it'll<00:04:39.240> be<00:04:39.360> beneficial<00:04:39.840> and<00:04:40.080> so<00:04:40.320> we're<00:04:40.500> going 00:04:40.610 --> 00:04:40.620 align:start position:0% it'll be beneficial and so we're going 00:04:40.620 --> 00:04:42.170 align:start position:0% it'll be beneficial and so we're going to<00:04:40.740> keep<00:04:40.800> doing<00:04:40.979> that<00:04:41.220> until<00:04:41.400> it<00:04:41.699> gets<00:04:41.940> to<00:04:42.000> the 00:04:42.170 --> 00:04:42.180 align:start position:0% to keep doing that until it gets to the 00:04:42.180 --> 00:04:43.790 align:start position:0% to keep doing that until it gets to the point<00:04:42.360> where<00:04:42.600> we<00:04:42.780> feel<00:04:42.960> like<00:04:43.080> it's<00:04:43.259> crossed<00:04:43.680> a 00:04:43.790 --> 00:04:43.800 align:start position:0% point where we feel like it's crossed a 00:04:43.800 --> 00:04:45.770 align:start position:0% point where we feel like it's crossed a Tipping<00:04:44.160> Point<00:04:44.340> and<00:04:44.940> we<00:04:45.060> need<00:04:45.180> to<00:04:45.300> try<00:04:45.419> to<00:04:45.600> do 00:04:45.770 --> 00:04:45.780 align:start position:0% Tipping Point and we need to try to do 00:04:45.780 --> 00:04:47.210 align:start position:0% Tipping Point and we need to try to do things<00:04:46.020> differently 00:04:47.210 --> 00:04:47.220 align:start position:0% things differently 00:04:47.220 --> 00:04:49.090 align:start position:0% things differently and<00:04:47.880> when<00:04:48.120> you<00:04:48.240> look<00:04:48.300> around<00:04:48.479> the<00:04:48.720> space 00:04:49.090 --> 00:04:49.100 align:start position:0% and when you look around the space 00:04:49.100 --> 00:04:51.530 align:start position:0% and when you look around the space there's<00:04:50.100> other<00:04:50.400> points<00:04:50.759> of<00:04:50.880> centralization 00:04:51.530 --> 00:04:51.540 align:start position:0% there's other points of centralization 00:04:51.540 --> 00:04:53.770 align:start position:0% there's other points of centralization that<00:04:52.139> have<00:04:52.320> paths<00:04:52.800> to<00:04:52.860> decentralization 00:04:53.770 --> 00:04:53.780 align:start position:0% that have paths to decentralization 00:04:53.780 --> 00:04:56.990 align:start position:0% that have paths to decentralization things<00:04:54.780> like<00:04:55.220> Fiat<00:04:56.220> on-ramps<00:04:56.880> and 00:04:56.990 --> 00:04:57.000 align:start position:0% things like Fiat on-ramps and 00:04:57.000 --> 00:04:59.390 align:start position:0% things like Fiat on-ramps and centralized<00:04:57.660> exchanges<00:04:58.199> and<00:04:58.800> how<00:04:58.979> there's<00:04:59.160> a 00:04:59.390 --> 00:04:59.400 align:start position:0% centralized exchanges and how there's a 00:04:59.400 --> 00:05:01.189 align:start position:0% centralized exchanges and how there's a transition<00:04:59.639> from<00:04:59.940> those<00:05:00.120> to<00:05:00.300> Alternatives<00:05:00.840> or 00:05:01.189 --> 00:05:01.199 align:start position:0% transition from those to Alternatives or 00:05:01.199 --> 00:05:03.590 align:start position:0% transition from those to Alternatives or decentralized<00:05:01.800> truly<00:05:02.160> decentralized<00:05:02.940> ways 00:05:03.590 --> 00:05:03.600 align:start position:0% decentralized truly decentralized ways 00:05:03.600 --> 00:05:06.830 align:start position:0% decentralized truly decentralized ways of<00:05:03.780> doing<00:05:04.080> the<00:05:04.440> same<00:05:04.680> operation<00:05:05.720> my<00:05:06.720> favorite 00:05:06.830 --> 00:05:06.840 align:start position:0% of doing the same operation my favorite 00:05:06.840 --> 00:05:09.530 align:start position:0% of doing the same operation my favorite example<00:05:07.440> is<00:05:07.919> when<00:05:08.340> you<00:05:08.520> talk<00:05:08.699> about<00:05:08.820> Roll-Ups 00:05:09.530 --> 00:05:09.540 align:start position:0% example is when you talk about Roll-Ups 00:05:09.540 --> 00:05:12.350 align:start position:0% example is when you talk about Roll-Ups and<00:05:09.900> how<00:05:10.199> initially<00:05:11.160> Roll-Ups<00:05:11.759> start<00:05:11.940> as 00:05:12.350 --> 00:05:12.360 align:start position:0% and how initially Roll-Ups start as 00:05:12.360 --> 00:05:14.330 align:start position:0% and how initially Roll-Ups start as having<00:05:12.900> a<00:05:13.199> single<00:05:13.440> entity<00:05:13.740> that's<00:05:14.040> creating 00:05:14.330 --> 00:05:14.340 align:start position:0% having a single entity that's creating 00:05:14.340 --> 00:05:16.909 align:start position:0% having a single entity that's creating the<00:05:14.460> Roll-Ups<00:05:15.000> and<00:05:15.419> the<00:05:15.600> roll-up<00:05:15.900> teams<00:05:16.320> have 00:05:16.909 --> 00:05:16.919 align:start position:0% the Roll-Ups and the roll-up teams have 00:05:16.919 --> 00:05:18.650 align:start position:0% the Roll-Ups and the roll-up teams have a<00:05:17.220> road<00:05:17.340> map<00:05:17.580> of<00:05:17.880> how<00:05:18.060> they<00:05:18.240> will<00:05:18.360> eventually 00:05:18.650 --> 00:05:18.660 align:start position:0% a road map of how they will eventually 00:05:18.660 --> 00:05:21.290 align:start position:0% a road map of how they will eventually get<00:05:18.900> to<00:05:19.139> being<00:05:19.320> more<00:05:19.680> decentralized<00:05:20.880> so 00:05:21.290 --> 00:05:21.300 align:start position:0% get to being more decentralized so 00:05:21.300 --> 00:05:22.550 align:start position:0% get to being more decentralized so that's<00:05:21.419> how<00:05:21.600> we<00:05:21.720> thought<00:05:21.840> of<00:05:22.080> ourselves<00:05:22.380> as 00:05:22.550 --> 00:05:22.560 align:start position:0% that's how we thought of ourselves as 00:05:22.560 --> 00:05:25.189 align:start position:0% that's how we thought of ourselves as inferior<00:05:23.160> started<00:05:23.940> to<00:05:24.120> centralize<00:05:24.479> and<00:05:24.960> we'll 00:05:25.189 --> 00:05:25.199 align:start position:0% inferior started to centralize and we'll 00:05:25.199 --> 00:05:27.050 align:start position:0% inferior started to centralize and we'll see<00:05:25.440> when<00:05:25.680> we<00:05:25.860> get<00:05:25.979> more<00:05:26.220> decentralized<00:05:26.880> and 00:05:27.050 --> 00:05:27.060 align:start position:0% see when we get more decentralized and 00:05:27.060 --> 00:05:28.790 align:start position:0% see when we get more decentralized and we're<00:05:27.180> going<00:05:27.300> to<00:05:27.419> have<00:05:27.539> a 00:05:28.790 --> 00:05:28.800 align:start position:0% we're going to have a 00:05:28.800 --> 00:05:31.850 align:start position:0% we're going to have a a<00:05:29.160> solution<00:05:29.520> for<00:05:29.759> how<00:05:29.940> we<00:05:30.120> do<00:05:30.240> that 00:05:31.850 --> 00:05:31.860 align:start position:0% a solution for how we do that 00:05:31.860 --> 00:05:34.129 align:start position:0% a solution for how we do that and<00:05:32.340> the<00:05:32.460> reason<00:05:32.580> is<00:05:32.759> because<00:05:33.000> we<00:05:33.840> had<00:05:33.960> to 00:05:34.129 --> 00:05:34.139 align:start position:0% and the reason is because we had to 00:05:34.139 --> 00:05:36.950 align:start position:0% and the reason is because we had to create<00:05:34.380> quite<00:05:35.039> a<00:05:35.220> bit<00:05:35.400> of<00:05:36.060> uh 00:05:36.950 --> 00:05:36.960 align:start position:0% create quite a bit of uh 00:05:36.960 --> 00:05:39.650 align:start position:0% create quite a bit of uh proprietary<00:05:37.740> infrastructure<00:05:38.520> to<00:05:39.240> serve<00:05:39.539> the 00:05:39.650 --> 00:05:39.660 align:start position:0% proprietary infrastructure to serve the 00:05:39.660 --> 00:05:41.810 align:start position:0% proprietary infrastructure to serve the traffic<00:05:39.840> that<00:05:40.199> we've<00:05:40.380> done<00:05:40.560> over<00:05:40.979> the<00:05:41.520> last 00:05:41.810 --> 00:05:41.820 align:start position:0% traffic that we've done over the last 00:05:41.820 --> 00:05:45.050 align:start position:0% traffic that we've done over the last six<00:05:42.060> seven<00:05:42.300> years<00:05:42.680> what<00:05:43.680> we<00:05:44.100> run<00:05:44.580> today<00:05:44.820> as 00:05:45.050 --> 00:05:45.060 align:start position:0% six seven years what we run today as 00:05:45.060 --> 00:05:48.650 align:start position:0% six seven years what we run today as inferior<00:05:45.720> is<00:05:46.380> far<00:05:46.919> more<00:05:47.160> complex<00:05:47.699> than<00:05:48.419> what 00:05:48.650 --> 00:05:48.660 align:start position:0% inferior is far more complex than what 00:05:48.660 --> 00:05:52.610 align:start position:0% inferior is far more complex than what we<00:05:48.840> ran<00:05:49.080> with<00:05:49.259> in<00:05:49.500> 2016.<00:05:50.360> if<00:05:51.360> uh<00:05:52.139> if<00:05:52.380> you<00:05:52.500> had 00:05:52.610 --> 00:05:52.620 align:start position:0% we ran with in 2016. if uh if you had 00:05:52.620 --> 00:05:55.370 align:start position:0% we ran with in 2016. if uh if you had tried<00:05:52.860> to<00:05:52.979> replicate<00:05:53.460> what<00:05:53.639> we<00:05:53.759> had<00:05:53.880> in<00:05:54.060> 2016 00:05:55.370 --> 00:05:55.380 align:start position:0% tried to replicate what we had in 2016 00:05:55.380 --> 00:05:56.810 align:start position:0% tried to replicate what we had in 2016 um<00:05:55.500> maybe<00:05:55.800> a<00:05:55.979> month<00:05:56.160> or<00:05:56.280> two<00:05:56.400> after<00:05:56.580> we 00:05:56.810 --> 00:05:56.820 align:start position:0% um maybe a month or two after we 00:05:56.820 --> 00:05:59.210 align:start position:0% um maybe a month or two after we launched<00:05:57.180> you<00:05:57.479> could<00:05:57.539> do<00:05:57.720> it<00:05:57.900> within<00:05:58.380> a<00:05:59.100> week 00:05:59.210 --> 00:05:59.220 align:start position:0% launched you could do it within a week 00:05:59.220 --> 00:06:01.310 align:start position:0% launched you could do it within a week or<00:05:59.460> two<00:05:59.580> now<00:06:00.300> it<00:06:00.600> would<00:06:00.660> take<00:06:00.900> you<00:06:01.020> probably 00:06:01.310 --> 00:06:01.320 align:start position:0% or two now it would take you probably 00:06:01.320 --> 00:06:03.110 align:start position:0% or two now it would take you probably years<00:06:01.620> to<00:06:01.860> try<00:06:01.979> to<00:06:02.100> replicate<00:06:02.520> the<00:06:02.759> systems 00:06:03.110 --> 00:06:03.120 align:start position:0% years to try to replicate the systems 00:06:03.120 --> 00:06:05.689 align:start position:0% years to try to replicate the systems that<00:06:03.360> we've<00:06:03.660> had<00:06:03.900> to<00:06:04.080> build<00:06:04.259> because 00:06:05.689 --> 00:06:05.699 align:start position:0% that we've had to build because 00:06:05.699 --> 00:06:08.890 align:start position:0% that we've had to build because between<00:06:06.240> 2016<00:06:06.900> and<00:06:07.259> now<00:06:07.500> we<00:06:07.919> went<00:06:08.100> through<00:06:08.400> the 00:06:08.890 --> 00:06:08.900 align:start position:0% between 2016 and now we went through the 00:06:08.900 --> 00:06:12.290 align:start position:0% between 2016 and now we went through the 2017-2018<00:06:09.900> Ico<00:06:10.560> bubble<00:06:11.039> the<00:06:11.220> 2019<00:06:11.699> crypto 00:06:12.290 --> 00:06:12.300 align:start position:0% 2017-2018 Ico bubble the 2019 crypto 00:06:12.300 --> 00:06:13.249 align:start position:0% 2017-2018 Ico bubble the 2019 crypto winter 00:06:13.249 --> 00:06:13.259 align:start position:0% winter 00:06:13.259 --> 00:06:16.909 align:start position:0% winter 2020<00:06:14.100> D5<00:06:14.759> summer<00:06:15.120> all<00:06:16.080> of<00:06:16.199> the<00:06:16.320> explosion<00:06:16.740> of 00:06:16.909 --> 00:06:16.919 align:start position:0% 2020 D5 summer all of the explosion of 00:06:16.919 --> 00:06:19.189 align:start position:0% 2020 D5 summer all of the explosion of nft<00:06:17.280> growth<00:06:17.880> and<00:06:18.180> with<00:06:18.360> every<00:06:18.600> single<00:06:18.900> one<00:06:19.020> of 00:06:19.189 --> 00:06:19.199 align:start position:0% nft growth and with every single one of 00:06:19.199 --> 00:06:20.810 align:start position:0% nft growth and with every single one of those<00:06:19.320> things<00:06:19.560> you<00:06:20.039> might<00:06:20.160> have<00:06:20.280> run<00:06:20.400> into<00:06:20.580> an 00:06:20.810 --> 00:06:20.820 align:start position:0% those things you might have run into an 00:06:20.820 --> 00:06:23.150 align:start position:0% those things you might have run into an inferior<00:06:21.360> production<00:06:21.720> incident<00:06:22.199> something 00:06:23.150 --> 00:06:23.160 align:start position:0% inferior production incident something 00:06:23.160 --> 00:06:26.629 align:start position:0% inferior production incident something uh<00:06:24.060> that<00:06:24.419> showed<00:06:24.840> Oh<00:06:25.139> this<00:06:25.919> didn't<00:06:26.280> scale 00:06:26.629 --> 00:06:26.639 align:start position:0% uh that showed Oh this didn't scale 00:06:26.639 --> 00:06:28.309 align:start position:0% uh that showed Oh this didn't scale exactly<00:06:27.060> right<00:06:27.240> and<00:06:27.600> every<00:06:27.720> time<00:06:27.960> it<00:06:28.139> didn't 00:06:28.309 --> 00:06:28.319 align:start position:0% exactly right and every time it didn't 00:06:28.319 --> 00:06:30.290 align:start position:0% exactly right and every time it didn't scale<00:06:28.740> exactly<00:06:29.160> right<00:06:29.340> we<00:06:29.699> improved<00:06:30.120> our 00:06:30.290 --> 00:06:30.300 align:start position:0% scale exactly right we improved our 00:06:30.300 --> 00:06:33.050 align:start position:0% scale exactly right we improved our system<00:06:30.539> right<00:06:31.319> and<00:06:31.800> so<00:06:32.039> it<00:06:32.520> forced<00:06:32.819> us<00:06:32.940> to 00:06:33.050 --> 00:06:33.060 align:start position:0% system right and so it forced us to 00:06:33.060 --> 00:06:35.090 align:start position:0% system right and so it forced us to innovate<00:06:33.479> every<00:06:33.780> single<00:06:34.020> time<00:06:34.199> take<00:06:34.680> data 00:06:35.090 --> 00:06:35.100 align:start position:0% innovate every single time take data 00:06:35.100 --> 00:06:37.730 align:start position:0% innovate every single time take data like<00:06:35.400> back<00:06:35.819> in<00:06:36.000> the<00:06:36.120> day<00:06:36.240> we<00:06:36.419> used<00:06:36.660> to<00:06:36.780> send 00:06:37.730 --> 00:06:37.740 align:start position:0% like back in the day we used to send 00:06:37.740 --> 00:06:41.450 align:start position:0% like back in the day we used to send requests<00:06:38.280> directly<00:06:38.819> to<00:06:39.319> ethereum<00:06:40.319> nodes<00:06:40.680> and 00:06:41.450 --> 00:06:41.460 align:start position:0% requests directly to ethereum nodes and 00:06:41.460 --> 00:06:43.909 align:start position:0% requests directly to ethereum nodes and there<00:06:41.639> was<00:06:41.819> really<00:06:42.060> no<00:06:42.300> virtualization<00:06:43.020> as<00:06:43.500> we 00:06:43.909 --> 00:06:43.919 align:start position:0% there was really no virtualization as we 00:06:43.919 --> 00:06:46.790 align:start position:0% there was really no virtualization as we call<00:06:44.100> it<00:06:44.660> custom<00:06:45.660> services<00:06:46.080> that<00:06:46.680> would 00:06:46.790 --> 00:06:46.800 align:start position:0% call it custom services that would 00:06:46.800 --> 00:06:48.650 align:start position:0% call it custom services that would handle<00:06:47.160> the<00:06:47.280> traffic<00:06:47.520> because<00:06:48.240> we<00:06:48.539> didn't 00:06:48.650 --> 00:06:48.660 align:start position:0% handle the traffic because we didn't 00:06:48.660 --> 00:06:50.510 align:start position:0% handle the traffic because we didn't ever<00:06:48.900> want<00:06:49.080> to<00:06:49.199> be<00:06:49.319> in<00:06:49.440> a<00:06:49.560> position<00:06:49.680> of 00:06:50.510 --> 00:06:50.520 align:start position:0% ever want to be in a position of 00:06:50.520 --> 00:06:52.790 align:start position:0% ever want to be in a position of providing<00:06:51.360> the<00:06:51.780> wrong<00:06:51.960> data<00:06:52.380> to<00:06:52.500> you<00:06:52.680> because 00:06:52.790 --> 00:06:52.800 align:start position:0% providing the wrong data to you because 00:06:52.800 --> 00:06:54.350 align:start position:0% providing the wrong data to you because that<00:06:52.979> would<00:06:53.160> be<00:06:53.280> really<00:06:53.460> bad<00:06:53.699> that'd<00:06:54.180> be<00:06:54.240> the 00:06:54.350 --> 00:06:54.360 align:start position:0% that would be really bad that'd be the 00:06:54.360 --> 00:06:55.790 align:start position:0% that would be really bad that'd be the end<00:06:54.479> of<00:06:54.600> our<00:06:54.660> service<00:06:54.840> if<00:06:55.080> we<00:06:55.259> ever<00:06:55.380> provided 00:06:55.790 --> 00:06:55.800 align:start position:0% end of our service if we ever provided 00:06:55.800 --> 00:06:57.590 align:start position:0% end of our service if we ever provided you<00:06:55.919> the<00:06:56.160> wrong<00:06:56.280> day<00:06:56.460> that<00:06:56.639> like<00:06:56.880> that 00:06:57.590 --> 00:06:57.600 align:start position:0% you the wrong day that like that 00:06:57.600 --> 00:07:01.370 align:start position:0% you the wrong day that like that and<00:06:58.500> especially<00:06:59.400> in<00:06:59.699> 2021<00:07:00.300> we<00:07:00.780> ran<00:07:00.960> into<00:07:01.139> this 00:07:01.370 --> 00:07:01.380 align:start position:0% and especially in 2021 we ran into this 00:07:01.380 --> 00:07:02.990 align:start position:0% and especially in 2021 we ran into this issue<00:07:01.740> where 00:07:02.990 --> 00:07:03.000 align:start position:0% issue where 00:07:03.000 --> 00:07:05.930 align:start position:0% issue where we<00:07:03.539> tried<00:07:03.780> to<00:07:03.900> be<00:07:04.139> very<00:07:04.500> uh<00:07:04.919> conservative<00:07:05.639> with 00:07:05.930 --> 00:07:05.940 align:start position:0% we tried to be very uh conservative with 00:07:05.940 --> 00:07:08.529 align:start position:0% we tried to be very uh conservative with how<00:07:06.180> often<00:07:06.479> we<00:07:06.600> updated<00:07:06.960> our<00:07:07.319> clients<00:07:07.800> because 00:07:08.529 --> 00:07:08.539 align:start position:0% how often we updated our clients because 00:07:08.539 --> 00:07:11.510 align:start position:0% how often we updated our clients because uh<00:07:09.539> early<00:07:09.900> on<00:07:10.139> the<00:07:10.560> clients<00:07:10.919> were<00:07:11.160> a<00:07:11.400> little 00:07:11.510 --> 00:07:11.520 align:start position:0% uh early on the clients were a little 00:07:11.520 --> 00:07:13.670 align:start position:0% uh early on the clients were a little bit<00:07:11.699> uh<00:07:12.240> bleeding<00:07:12.660> edge<00:07:12.780> and<00:07:13.259> a<00:07:13.380> little<00:07:13.500> bit 00:07:13.670 --> 00:07:13.680 align:start position:0% bit uh bleeding edge and a little bit 00:07:13.680 --> 00:07:16.370 align:start position:0% bit uh bleeding edge and a little bit unstable<00:07:14.639> the<00:07:14.940> closer<00:07:15.300> you<00:07:15.479> tracked<00:07:15.960> to<00:07:16.199> the 00:07:16.370 --> 00:07:16.380 align:start position:0% unstable the closer you tracked to the 00:07:16.380 --> 00:07:19.010 align:start position:0% unstable the closer you tracked to the latest<00:07:16.560> release<00:07:16.940> and<00:07:17.940> because<00:07:18.180> of<00:07:18.419> that<00:07:18.600> users 00:07:19.010 --> 00:07:19.020 align:start position:0% latest release and because of that users 00:07:19.020 --> 00:07:20.870 align:start position:0% latest release and because of that users were<00:07:19.259> complaining<00:07:19.680> like<00:07:19.919> maybe<00:07:20.280> give<00:07:20.639> us<00:07:20.759> a 00:07:20.870 --> 00:07:20.880 align:start position:0% were complaining like maybe give us a 00:07:20.880 --> 00:07:22.670 align:start position:0% were complaining like maybe give us a little<00:07:20.940> more<00:07:21.120> stability<00:07:21.419> less<00:07:21.960> of<00:07:22.380> the 00:07:22.670 --> 00:07:22.680 align:start position:0% little more stability less of the 00:07:22.680 --> 00:07:25.670 align:start position:0% little more stability less of the absolutely<00:07:23.580> latest<00:07:23.880> client<00:07:24.419> that<00:07:25.319> ended<00:07:25.560> up 00:07:25.670 --> 00:07:25.680 align:start position:0% absolutely latest client that ended up 00:07:25.680 --> 00:07:27.890 align:start position:0% absolutely latest client that ended up biting<00:07:25.979> Us<00:07:26.099> in<00:07:26.340> 2021<00:07:26.880> when<00:07:27.300> we<00:07:27.419> were<00:07:27.539> running<00:07:27.720> a 00:07:27.890 --> 00:07:27.900 align:start position:0% biting Us in 2021 when we were running a 00:07:27.900 --> 00:07:30.350 align:start position:0% biting Us in 2021 when we were running a client<00:07:28.080> that<00:07:28.259> was<00:07:28.380> about<00:07:28.500> six<00:07:28.800> months<00:07:29.160> old<00:07:29.360> and 00:07:30.350 --> 00:07:30.360 align:start position:0% client that was about six months old and 00:07:30.360 --> 00:07:34.129 align:start position:0% client that was about six months old and a<00:07:30.720> bug<00:07:30.960> was<00:07:31.199> triggered<00:07:31.680> by<00:07:32.220> by<00:07:32.520> a<00:07:32.759> team<00:07:32.940> that<00:07:33.840> I 00:07:34.129 --> 00:07:34.139 align:start position:0% a bug was triggered by by a team that I 00:07:34.139 --> 00:07:35.029 align:start position:0% a bug was triggered by by a team that I won't<00:07:34.259> mention<00:07:34.380> because<00:07:34.620> there<00:07:34.800> was<00:07:34.919> an 00:07:35.029 --> 00:07:35.039 align:start position:0% won't mention because there was an 00:07:35.039 --> 00:07:38.089 align:start position:0% won't mention because there was an accident<00:07:35.160> and<00:07:35.460> they<00:07:35.639> apologized<00:07:36.240> to<00:07:36.419> us<00:07:36.539> but 00:07:38.089 --> 00:07:38.099 align:start position:0% accident and they apologized to us but 00:07:38.099 --> 00:07:40.490 align:start position:0% accident and they apologized to us but um<00:07:38.580> it<00:07:39.120> took<00:07:39.300> down<00:07:39.479> inferior<00:07:39.960> for<00:07:40.139> six<00:07:40.319> hours 00:07:40.490 --> 00:07:40.500 align:start position:0% um it took down inferior for six hours 00:07:40.500 --> 00:07:42.469 align:start position:0% um it took down inferior for six hours and<00:07:40.800> that<00:07:40.919> was<00:07:41.039> our<00:07:41.280> first<00:07:41.460> multi-hour<00:07:42.060> outage 00:07:42.469 --> 00:07:42.479 align:start position:0% and that was our first multi-hour outage 00:07:42.479 --> 00:07:44.029 align:start position:0% and that was our first multi-hour outage that<00:07:42.720> we<00:07:42.900> have<00:07:43.020> ever<00:07:43.139> had<00:07:43.319> and<00:07:43.500> it's<00:07:43.680> still<00:07:43.919> our 00:07:44.029 --> 00:07:44.039 align:start position:0% that we have ever had and it's still our 00:07:44.039 --> 00:07:46.010 align:start position:0% that we have ever had and it's still our worst<00:07:44.220> outage<00:07:44.580> that<00:07:44.759> we've<00:07:44.940> ever<00:07:45.000> had<00:07:45.300> and<00:07:45.900> so 00:07:46.010 --> 00:07:46.020 align:start position:0% worst outage that we've ever had and so 00:07:46.020 --> 00:07:47.450 align:start position:0% worst outage that we've ever had and so that<00:07:46.139> really<00:07:46.319> made<00:07:46.500> us<00:07:46.680> think<00:07:46.860> maybe<00:07:47.160> that<00:07:47.400> was 00:07:47.450 --> 00:07:47.460 align:start position:0% that really made us think maybe that was 00:07:47.460 --> 00:07:49.129 align:start position:0% that really made us think maybe that was the<00:07:47.639> Tipping<00:07:47.880> Point<00:07:48.060> maybe<00:07:48.479> that's<00:07:48.720> the<00:07:48.960> point 00:07:49.129 --> 00:07:49.139 align:start position:0% the Tipping Point maybe that's the point 00:07:49.139 --> 00:07:50.689 align:start position:0% the Tipping Point maybe that's the point where<00:07:49.319> we<00:07:49.440> need<00:07:49.560> to<00:07:49.680> start<00:07:49.860> considering<00:07:50.340> Now's 00:07:50.689 --> 00:07:50.699 align:start position:0% where we need to start considering Now's 00:07:50.699 --> 00:07:52.490 align:start position:0% where we need to start considering Now's the<00:07:50.880> Time<00:07:51.120> to<00:07:51.599> do<00:07:51.900> things<00:07:52.080> differently 00:07:52.490 --> 00:07:52.500 align:start position:0% the Time to do things differently 00:07:52.500 --> 00:07:54.529 align:start position:0% the Time to do things differently because<00:07:53.039> for<00:07:53.280> us<00:07:53.400> decentralization<00:07:54.180> was 00:07:54.529 --> 00:07:54.539 align:start position:0% because for us decentralization was 00:07:54.539 --> 00:07:56.689 align:start position:0% because for us decentralization was always<00:07:54.780> the<00:07:55.080> plan<00:07:55.259> we<00:07:55.979> said<00:07:56.160> we're<00:07:56.340> going<00:07:56.520> to 00:07:56.689 --> 00:07:56.699 align:start position:0% always the plan we said we're going to 00:07:56.699 --> 00:07:58.730 align:start position:0% always the plan we said we're going to get<00:07:56.880> there<00:07:57.060> it's<00:07:57.419> just<00:07:57.599> not<00:07:57.900> the<00:07:58.199> first<00:07:58.380> step 00:07:58.730 --> 00:07:58.740 align:start position:0% get there it's just not the first step 00:07:58.740 --> 00:08:00.710 align:start position:0% get there it's just not the first step in<00:07:59.280> that<00:07:59.460> plan 00:08:00.710 --> 00:08:00.720 align:start position:0% in that plan 00:08:00.720 --> 00:08:02.930 align:start position:0% in that plan we<00:08:01.139> said<00:08:01.259> that<00:08:01.440> we<00:08:01.560> are<00:08:01.680> going<00:08:01.800> to<00:08:02.039> set<00:08:02.220> out<00:08:02.460> to 00:08:02.930 --> 00:08:02.940 align:start position:0% we said that we are going to set out to 00:08:02.940 --> 00:08:06.110 align:start position:0% we said that we are going to set out to prove<00:08:03.539> that<00:08:03.660> web<00:08:03.960> 3<00:08:04.259> could<00:08:04.979> be<00:08:05.160> served<00:08:05.520> by<00:08:05.759> SAS 00:08:06.110 --> 00:08:06.120 align:start position:0% prove that web 3 could be served by SAS 00:08:06.120 --> 00:08:08.390 align:start position:0% prove that web 3 could be served by SAS we're<00:08:06.720> going<00:08:06.960> to<00:08:07.139> say<00:08:07.380> that<00:08:07.680> we're<00:08:08.160> going<00:08:08.340> to 00:08:08.390 --> 00:08:08.400 align:start position:0% we're going to say that we're going to 00:08:08.400 --> 00:08:10.370 align:start position:0% we're going to say that we're going to run<00:08:08.520> a<00:08:08.699> SAS<00:08:08.940> service<00:08:09.180> and<00:08:09.720> that's<00:08:09.900> going<00:08:10.080> to<00:08:10.199> be 00:08:10.370 --> 00:08:10.380 align:start position:0% run a SAS service and that's going to be 00:08:10.380 --> 00:08:13.610 align:start position:0% run a SAS service and that's going to be beneficial<00:08:10.919> for<00:08:11.639> uh<00:08:12.300> the<00:08:12.479> ecosystem<00:08:12.960> and<00:08:13.500> it's 00:08:13.610 --> 00:08:13.620 align:start position:0% beneficial for uh the ecosystem and it's 00:08:13.620 --> 00:08:15.409 align:start position:0% beneficial for uh the ecosystem and it's going<00:08:13.800> to<00:08:13.919> bring<00:08:13.979> more<00:08:14.220> developers<00:08:14.699> in<00:08:15.000> it's 00:08:15.409 --> 00:08:15.419 align:start position:0% going to bring more developers in it's 00:08:15.419 --> 00:08:17.089 align:start position:0% going to bring more developers in it's going<00:08:15.660> to<00:08:15.780> bring<00:08:16.259> in<00:08:16.380> more<00:08:16.560> investor<00:08:16.919> interest 00:08:17.089 --> 00:08:17.099 align:start position:0% going to bring in more investor interest 00:08:17.099 --> 00:08:19.129 align:start position:0% going to bring in more investor interest a<00:08:17.699> lot<00:08:17.819> of<00:08:17.940> activity<00:08:18.300> is<00:08:18.479> going<00:08:18.599> to<00:08:18.780> come<00:08:18.960> into 00:08:19.129 --> 00:08:19.139 align:start position:0% a lot of activity is going to come into 00:08:19.139 --> 00:08:21.890 align:start position:0% a lot of activity is going to come into this<00:08:19.379> space<00:08:19.620> because<00:08:20.280> people<00:08:20.520> will<00:08:20.759> see<00:08:21.000> oh<00:08:21.240> I 00:08:21.890 --> 00:08:21.900 align:start position:0% this space because people will see oh I 00:08:21.900 --> 00:08:23.629 align:start position:0% this space because people will see oh I can<00:08:22.080> actually<00:08:22.379> make<00:08:22.979> a<00:08:23.099> living<00:08:23.220> and<00:08:23.460> support 00:08:23.629 --> 00:08:23.639 align:start position:0% can actually make a living and support 00:08:23.639 --> 00:08:26.029 align:start position:0% can actually make a living and support myself<00:08:24.000> running<00:08:24.539> a<00:08:24.780> business<00:08:24.900> in<00:08:25.139> web<00:08:25.379> 3<00:08:25.620> when 00:08:26.029 --> 00:08:26.039 align:start position:0% myself running a business in web 3 when 00:08:26.039 --> 00:08:27.770 align:start position:0% myself running a business in web 3 when at<00:08:26.220> the<00:08:26.340> time<00:08:26.520> it<00:08:26.819> wasn't<00:08:26.940> very<00:08:27.180> clear<00:08:27.419> Which 00:08:27.770 --> 00:08:27.780 align:start position:0% at the time it wasn't very clear Which 00:08:27.780 --> 00:08:31.430 align:start position:0% at the time it wasn't very clear Which models<00:08:28.259> would<00:08:28.440> work<00:08:29.160> and<00:08:29.759> so<00:08:29.940> now<00:08:30.599> inferior<00:08:31.319> is 00:08:31.430 --> 00:08:31.440 align:start position:0% models would work and so now inferior is 00:08:31.440 --> 00:08:33.469 align:start position:0% models would work and so now inferior is not<00:08:31.620> the<00:08:31.740> only<00:08:31.860> game<00:08:32.039> in<00:08:32.279> town<00:08:32.459> There's<00:08:32.940> dozens 00:08:33.469 --> 00:08:33.479 align:start position:0% not the only game in town There's dozens 00:08:33.479 --> 00:08:35.149 align:start position:0% not the only game in town There's dozens like<00:08:33.719> they<00:08:33.959> can't<00:08:34.260> even<00:08:34.380> fit<00:08:34.620> on<00:08:34.800> this<00:08:34.979> screen 00:08:35.149 --> 00:08:35.159 align:start position:0% like they can't even fit on this screen 00:08:35.159 --> 00:08:36.709 align:start position:0% like they can't even fit on this screen anymore<00:08:35.520> and<00:08:36.120> we<00:08:36.240> feel<00:08:36.360> like<00:08:36.479> we've 00:08:36.709 --> 00:08:36.719 align:start position:0% anymore and we feel like we've 00:08:36.719 --> 00:08:38.449 align:start position:0% anymore and we feel like we've accomplished<00:08:37.140> that<00:08:37.320> goal<00:08:37.560> we've<00:08:37.860> proved<00:08:38.219> that 00:08:38.449 --> 00:08:38.459 align:start position:0% accomplished that goal we've proved that 00:08:38.459 --> 00:08:41.269 align:start position:0% accomplished that goal we've proved that SAS<00:08:38.820> Works<00:08:39.180> in<00:08:39.300> web<00:08:39.419> 3<00:08:39.719> and<00:08:40.500> so<00:08:40.620> now<00:08:40.800> we<00:08:40.979> want<00:08:41.159> to 00:08:41.269 --> 00:08:41.279 align:start position:0% SAS Works in web 3 and so now we want to 00:08:41.279 --> 00:08:44.690 align:start position:0% SAS Works in web 3 and so now we want to prove<00:08:41.700> that<00:08:42.240> web<00:08:42.719> 3<00:08:43.020> models<00:08:43.560> can<00:08:44.039> be<00:08:44.219> used<00:08:44.399> to 00:08:44.690 --> 00:08:44.700 align:start position:0% prove that web 3 models can be used to 00:08:44.700 --> 00:08:47.990 align:start position:0% prove that web 3 models can be used to serve<00:08:45.000> SAS<00:08:45.360> and<00:08:46.200> that's<00:08:46.440> what<00:08:46.680> we<00:08:47.279> took<00:08:47.640> as<00:08:47.760> our 00:08:47.990 --> 00:08:48.000 align:start position:0% serve SAS and that's what we took as our 00:08:48.000 --> 00:08:49.970 align:start position:0% serve SAS and that's what we took as our approach<00:08:48.240> to<00:08:48.480> decentralizing<00:08:49.200> inferior<00:08:49.680> and 00:08:49.970 --> 00:08:49.980 align:start position:0% approach to decentralizing inferior and 00:08:49.980 --> 00:08:52.130 align:start position:0% approach to decentralizing inferior and that's<00:08:50.100> where<00:08:50.279> we<00:08:50.459> are<00:08:50.640> today<00:08:50.880> and<00:08:51.839> the<00:08:52.019> first 00:08:52.130 --> 00:08:52.140 align:start position:0% that's where we are today and the first 00:08:52.140 --> 00:08:54.110 align:start position:0% that's where we are today and the first step<00:08:52.320> to<00:08:52.500> that<00:08:52.680> is<00:08:52.920> open<00:08:53.220> collaboration<00:08:53.880> and 00:08:54.110 --> 00:08:54.120 align:start position:0% step to that is open collaboration and 00:08:54.120 --> 00:08:56.990 align:start position:0% step to that is open collaboration and transparency<00:08:54.800> we<00:08:55.800> don't<00:08:55.980> have<00:08:56.339> the<00:08:56.760> entire 00:08:56.990 --> 00:08:57.000 align:start position:0% transparency we don't have the entire 00:08:57.000 --> 00:08:59.210 align:start position:0% transparency we don't have the entire solution<00:08:57.540> in<00:08:58.200> a<00:08:58.380> white<00:08:58.500> paper<00:08:58.680> form<00:08:58.980> that 00:08:59.210 --> 00:08:59.220 align:start position:0% solution in a white paper form that 00:08:59.220 --> 00:09:01.009 align:start position:0% solution in a white paper form that we're<00:08:59.339> going<00:08:59.519> to<00:08:59.700> upload<00:09:00.000> to<00:09:00.180> ipfs<00:09:00.720> and<00:09:00.899> you're 00:09:01.009 --> 00:09:01.019 align:start position:0% we're going to upload to ipfs and you're 00:09:01.019 --> 00:09:02.570 align:start position:0% we're going to upload to ipfs and you're all<00:09:01.140> going<00:09:01.260> to<00:09:01.380> read<00:09:01.680> it<00:09:01.860> right<00:09:02.040> now<00:09:02.160> like 00:09:02.570 --> 00:09:02.580 align:start position:0% all going to read it right now like 00:09:02.580 --> 00:09:05.210 align:start position:0% all going to read it right now like we're<00:09:02.940> still<00:09:03.300> in<00:09:03.600> that<00:09:03.779> design<00:09:04.019> phase<00:09:04.500> but 00:09:05.210 --> 00:09:05.220 align:start position:0% we're still in that design phase but 00:09:05.220 --> 00:09:06.889 align:start position:0% we're still in that design phase but we've<00:09:05.640> already<00:09:05.760> started<00:09:06.240> collaborating<00:09:06.660> with 00:09:06.889 --> 00:09:06.899 align:start position:0% we've already started collaborating with 00:09:06.899 --> 00:09:08.509 align:start position:0% we've already started collaborating with other<00:09:07.019> people<00:09:07.200> in<00:09:07.440> the<00:09:07.500> ecosystem<00:09:07.980> on<00:09:08.279> that 00:09:08.509 --> 00:09:08.519 align:start position:0% other people in the ecosystem on that 00:09:08.519 --> 00:09:10.070 align:start position:0% other people in the ecosystem on that design<00:09:08.700> we've<00:09:09.240> been<00:09:09.360> working<00:09:09.480> on<00:09:09.720> it<00:09:09.839> for<00:09:10.019> a 00:09:10.070 --> 00:09:10.080 align:start position:0% design we've been working on it for a 00:09:10.080 --> 00:09:12.230 align:start position:0% design we've been working on it for a year<00:09:10.200> and<00:09:10.320> a<00:09:10.440> half<00:09:11.040> this<00:09:11.580> is<00:09:11.700> where<00:09:11.880> we<00:09:12.000> want<00:09:12.120> to 00:09:12.230 --> 00:09:12.240 align:start position:0% year and a half this is where we want to 00:09:12.240 --> 00:09:13.490 align:start position:0% year and a half this is where we want to start<00:09:12.360> showing<00:09:12.660> you<00:09:12.720> more<00:09:12.959> of<00:09:13.019> the<00:09:13.200> technical 00:09:13.490 --> 00:09:13.500 align:start position:0% start showing you more of the technical 00:09:13.500 --> 00:09:15.590 align:start position:0% start showing you more of the technical details<00:09:13.980> of<00:09:14.160> what<00:09:14.339> goes<00:09:14.640> into<00:09:14.760> that 00:09:15.590 --> 00:09:15.600 align:start position:0% details of what goes into that 00:09:15.600 --> 00:09:17.750 align:start position:0% details of what goes into that what<00:09:16.140> does<00:09:16.320> decentralizing<00:09:16.980> inferior<00:09:17.519> look 00:09:17.750 --> 00:09:17.760 align:start position:0% what does decentralizing inferior look 00:09:17.760 --> 00:09:19.850 align:start position:0% what does decentralizing inferior look like<00:09:17.880> it<00:09:18.720> could<00:09:18.899> people<00:09:19.140> have<00:09:19.380> said<00:09:19.560> oh<00:09:19.740> are 00:09:19.850 --> 00:09:19.860 align:start position:0% like it could people have said oh are 00:09:19.860 --> 00:09:21.410 align:start position:0% like it could people have said oh are you<00:09:19.980> just<00:09:20.100> going<00:09:20.220> to<00:09:20.279> create<00:09:20.399> a<00:09:20.640> dow<00:09:20.940> so<00:09:21.240> that 00:09:21.410 --> 00:09:21.420 align:start position:0% you just going to create a dow so that 00:09:21.420 --> 00:09:23.329 align:start position:0% you just going to create a dow so that we<00:09:21.660> can<00:09:21.779> like<00:09:22.019> have<00:09:22.200> some<00:09:22.440> governance<00:09:22.920> over 00:09:23.329 --> 00:09:23.339 align:start position:0% we can like have some governance over 00:09:23.339 --> 00:09:25.670 align:start position:0% we can like have some governance over what<00:09:24.120> inferior<00:09:24.600> does<00:09:24.839> is<00:09:25.140> that<00:09:25.320> good<00:09:25.500> enough 00:09:25.670 --> 00:09:25.680 align:start position:0% what inferior does is that good enough 00:09:25.680 --> 00:09:29.449 align:start position:0% what inferior does is that good enough or<00:09:26.399> is<00:09:26.640> it<00:09:26.940> some<00:09:27.660> sort<00:09:27.899> of<00:09:28.140> uh<00:09:29.040> utility 00:09:29.449 --> 00:09:29.459 align:start position:0% or is it some sort of uh utility 00:09:29.459 --> 00:09:32.150 align:start position:0% or is it some sort of uh utility function<00:09:30.420> that<00:09:30.839> we're<00:09:31.140> going<00:09:31.380> to<00:09:31.560> try<00:09:31.800> to<00:09:31.980> have 00:09:32.150 --> 00:09:32.160 align:start position:0% function that we're going to try to have 00:09:32.160 --> 00:09:34.250 align:start position:0% function that we're going to try to have as<00:09:32.459> part<00:09:32.700> of<00:09:32.820> this<00:09:32.940> network<00:09:33.240> what<00:09:34.019> are<00:09:34.140> the 00:09:34.250 --> 00:09:34.260 align:start position:0% as part of this network what are the 00:09:34.260 --> 00:09:36.710 align:start position:0% as part of this network what are the incentives<00:09:34.740> of<00:09:35.220> participating<00:09:35.880> how<00:09:36.480> do<00:09:36.600> we 00:09:36.710 --> 00:09:36.720 align:start position:0% incentives of participating how do we 00:09:36.720 --> 00:09:39.949 align:start position:0% incentives of participating how do we incentivize<00:09:37.200> the<00:09:37.380> right<00:09:37.560> behaviors<00:09:38.040> and 00:09:39.949 --> 00:09:39.959 align:start position:0% incentivize the right behaviors and 00:09:39.959 --> 00:09:43.130 align:start position:0% incentivize the right behaviors and what<00:09:40.800> people<00:09:40.980> were<00:09:41.220> especially<00:09:41.519> asking<00:09:42.000> was 00:09:43.130 --> 00:09:43.140 align:start position:0% what people were especially asking was 00:09:43.140 --> 00:09:45.530 align:start position:0% what people were especially asking was does<00:09:43.920> participating<00:09:44.519> in<00:09:44.700> this<00:09:44.940> decentralized 00:09:45.530 --> 00:09:45.540 align:start position:0% does participating in this decentralized 00:09:45.540 --> 00:09:47.750 align:start position:0% does participating in this decentralized infrastructure<00:09:46.200> Network<00:09:46.440> mean<00:09:46.920> like 00:09:47.750 --> 00:09:47.760 align:start position:0% infrastructure Network mean like 00:09:47.760 --> 00:09:49.490 align:start position:0% infrastructure Network mean like inferior<00:09:48.240> still<00:09:48.480> owns<00:09:48.899> and<00:09:49.019> controls 00:09:49.490 --> 00:09:49.500 align:start position:0% inferior still owns and controls 00:09:49.500 --> 00:09:51.050 align:start position:0% inferior still owns and controls everything<00:09:49.740> and<00:09:50.519> that's<00:09:50.700> the<00:09:50.940> biggest 00:09:51.050 --> 00:09:51.060 align:start position:0% everything and that's the biggest 00:09:51.060 --> 00:09:53.030 align:start position:0% everything and that's the biggest question<00:09:51.360> that<00:09:51.660> we<00:09:51.779> got<00:09:51.959> in<00:09:52.560> the<00:09:52.680> last<00:09:52.800> month 00:09:53.030 --> 00:09:53.040 align:start position:0% question that we got in the last month 00:09:53.040 --> 00:09:55.009 align:start position:0% question that we got in the last month since<00:09:53.279> we<00:09:53.459> announced<00:09:53.820> it<00:09:53.880> East<00:09:54.060> Berlin<00:09:54.480> and 00:09:55.009 --> 00:09:55.019 align:start position:0% since we announced it East Berlin and 00:09:55.019 --> 00:09:57.170 align:start position:0% since we announced it East Berlin and the<00:09:55.140> answer<00:09:55.260> to<00:09:55.440> that<00:09:55.680> no<00:09:56.160> it<00:09:56.519> that's<00:09:56.880> that 00:09:57.170 --> 00:09:57.180 align:start position:0% the answer to that no it that's that 00:09:57.180 --> 00:09:58.730 align:start position:0% the answer to that no it that's that defeats<00:09:57.600> the<00:09:57.720> purpose<00:09:58.019> of<00:09:58.260> what<00:09:58.440> we're<00:09:58.500> seeing 00:09:58.730 --> 00:09:58.740 align:start position:0% defeats the purpose of what we're seeing 00:09:58.740 --> 00:10:00.110 align:start position:0% defeats the purpose of what we're seeing with<00:09:58.920> a<00:09:59.040> decentralized<00:09:59.519> infrastructure 00:10:00.110 --> 00:10:00.120 align:start position:0% with a decentralized infrastructure 00:10:00.120 --> 00:10:01.970 align:start position:0% with a decentralized infrastructure Network<00:10:00.360> that's<00:10:01.200> supposed<00:10:01.440> to<00:10:01.620> be<00:10:01.740> a 00:10:01.970 --> 00:10:01.980 align:start position:0% Network that's supposed to be a 00:10:01.980 --> 00:10:04.490 align:start position:0% Network that's supposed to be a permissionless<00:10:02.760> network<00:10:03.120> so<00:10:03.600> inferior<00:10:04.380> is 00:10:04.490 --> 00:10:04.500 align:start position:0% permissionless network so inferior is 00:10:04.500 --> 00:10:06.710 align:start position:0% permissionless network so inferior is going<00:10:04.680> to<00:10:04.800> just<00:10:04.920> be<00:10:05.160> a<00:10:05.459> partner<00:10:05.820> in<00:10:06.480> a 00:10:06.710 --> 00:10:06.720 align:start position:0% going to just be a partner in a 00:10:06.720 --> 00:10:09.889 align:start position:0% going to just be a partner in a decentralized<00:10:07.440> permissionless<00:10:08.100> network<00:10:08.899> one 00:10:09.889 --> 00:10:09.899 align:start position:0% decentralized permissionless network one 00:10:09.899 --> 00:10:13.250 align:start position:0% decentralized permissionless network one of<00:10:10.260> an<00:10:10.680> equal<00:10:10.860> amount<00:10:11.160> of<00:10:11.339> or<00:10:11.880> one<00:10:12.180> of<00:10:12.420> equals 00:10:13.250 --> 00:10:13.260 align:start position:0% of an equal amount of or one of equals 00:10:13.260 --> 00:10:16.430 align:start position:0% of an equal amount of or one of equals in<00:10:13.620> operators 00:10:16.430 --> 00:10:16.440 align:start position:0% in operators 00:10:16.440 --> 00:10:19.009 align:start position:0% in operators so<00:10:17.279> now<00:10:17.760> I'm<00:10:17.940> going<00:10:18.060> to<00:10:18.120> pass<00:10:18.360> it<00:10:18.540> over<00:10:18.660> to<00:10:18.839> my 00:10:19.009 --> 00:10:19.019 align:start position:0% so now I'm going to pass it over to my 00:10:19.019 --> 00:10:20.150 align:start position:0% so now I'm going to pass it over to my colleague<00:10:19.200> Tim<00:10:19.440> and<00:10:19.680> we're<00:10:19.800> going<00:10:19.920> to<00:10:19.920> start 00:10:20.150 --> 00:10:20.160 align:start position:0% colleague Tim and we're going to start 00:10:20.160 --> 00:10:22.430 align:start position:0% colleague Tim and we're going to start sharing<00:10:20.640> some<00:10:20.940> of<00:10:21.060> the<00:10:21.420> technical<00:10:21.959> details 00:10:22.430 --> 00:10:22.440 align:start position:0% sharing some of the technical details 00:10:22.440 --> 00:10:23.690 align:start position:0% sharing some of the technical details with<00:10:22.620> you 00:10:23.690 --> 00:10:23.700 align:start position:0% with you 00:10:23.700 --> 00:10:27.110 align:start position:0% with you thanks<00:10:24.360> oh<00:10:24.779> sorry<00:10:25.200> uh<00:10:25.980> yeah<00:10:26.160> so<00:10:26.459> as<00:10:26.820> EG 00:10:27.110 --> 00:10:27.120 align:start position:0% thanks oh sorry uh yeah so as EG 00:10:27.120 --> 00:10:28.550 align:start position:0% thanks oh sorry uh yeah so as EG mentioned<00:10:27.600> we<00:10:27.839> don't<00:10:27.959> have<00:10:28.080> all<00:10:28.320> of<00:10:28.440> the 00:10:28.550 --> 00:10:28.560 align:start position:0% mentioned we don't have all of the 00:10:28.560 --> 00:10:29.990 align:start position:0% mentioned we don't have all of the details<00:10:28.920> of<00:10:29.040> this<00:10:29.220> figured<00:10:29.519> out<00:10:29.640> yet<00:10:29.760> we're 00:10:29.990 --> 00:10:30.000 align:start position:0% details of this figured out yet we're 00:10:30.000 --> 00:10:32.150 align:start position:0% details of this figured out yet we're still<00:10:30.180> pretty<00:10:30.360> deep<00:10:30.540> in<00:10:30.779> the<00:10:30.899> design<00:10:31.019> phase<00:10:31.500> uh 00:10:32.150 --> 00:10:32.160 align:start position:0% still pretty deep in the design phase uh 00:10:32.160 --> 00:10:33.829 align:start position:0% still pretty deep in the design phase uh but<00:10:32.339> the<00:10:32.459> next<00:10:32.580> 10<00:10:32.880> minutes<00:10:33.060> I'm<00:10:33.360> gonna<00:10:33.480> try 00:10:33.829 --> 00:10:33.839 align:start position:0% but the next 10 minutes I'm gonna try 00:10:33.839 --> 00:10:35.870 align:start position:0% but the next 10 minutes I'm gonna try and<00:10:34.019> walk<00:10:34.380> you<00:10:34.620> through<00:10:34.800> as<00:10:35.040> much<00:10:35.279> as<00:10:35.580> we<00:10:35.760> have 00:10:35.870 --> 00:10:35.880 align:start position:0% and walk you through as much as we have 00:10:35.880 --> 00:10:38.150 align:start position:0% and walk you through as much as we have figured<00:10:36.240> out<00:10:36.360> right<00:10:36.600> now<00:10:36.720> as<00:10:36.899> I<00:10:37.140> can<00:10:37.320> and<00:10:37.980> then 00:10:38.150 --> 00:10:38.160 align:start position:0% figured out right now as I can and then 00:10:38.160 --> 00:10:39.470 align:start position:0% figured out right now as I can and then hopefully<00:10:38.399> save<00:10:38.580> about<00:10:38.820> five<00:10:39.060> minutes<00:10:39.180> for 00:10:39.470 --> 00:10:39.480 align:start position:0% hopefully save about five minutes for 00:10:39.480 --> 00:10:41.329 align:start position:0% hopefully save about five minutes for any<00:10:39.600> questions<00:10:39.720> you<00:10:39.959> all<00:10:40.080> might<00:10:40.320> have<00:10:40.500> uh<00:10:41.160> so 00:10:41.329 --> 00:10:41.339 align:start position:0% any questions you all might have uh so 00:10:41.339 --> 00:10:42.530 align:start position:0% any questions you all might have uh so first<00:10:41.459> I<00:10:41.640> want<00:10:41.700> to<00:10:41.820> start<00:10:41.880> with<00:10:42.060> just<00:10:42.240> a<00:10:42.360> really 00:10:42.530 --> 00:10:42.540 align:start position:0% first I want to start with just a really 00:10:42.540 --> 00:10:44.930 align:start position:0% first I want to start with just a really high<00:10:42.779> level<00:10:43.140> overview<00:10:43.680> of<00:10:44.279> what<00:10:44.519> we<00:10:44.640> see<00:10:44.760> as 00:10:44.930 --> 00:10:44.940 align:start position:0% high level overview of what we see as 00:10:44.940 --> 00:10:46.790 align:start position:0% high level overview of what we see as the<00:10:45.060> network<00:10:45.180> participants<00:10:45.839> in<00:10:46.680> this 00:10:46.790 --> 00:10:46.800 align:start position:0% the network participants in this 00:10:46.800 --> 00:10:49.130 align:start position:0% the network participants in this decentralized<00:10:47.339> inferior<00:10:47.820> Network<00:10:48.060> so<00:10:48.959> first 00:10:49.130 --> 00:10:49.140 align:start position:0% decentralized inferior Network so first 00:10:49.140 --> 00:10:51.170 align:start position:0% decentralized inferior Network so first of<00:10:49.320> course<00:10:49.440> you<00:10:49.680> have<00:10:49.860> your<00:10:49.980> end<00:10:50.160> user<00:10:50.579> who 00:10:51.170 --> 00:10:51.180 align:start position:0% of course you have your end user who 00:10:51.180 --> 00:10:52.850 align:start position:0% of course you have your end user who wants<00:10:51.420> to<00:10:51.420> connect<00:10:51.600> to<00:10:51.779> a<00:10:51.899> web3<00:10:52.200> network<00:10:52.500> maybe 00:10:52.850 --> 00:10:52.860 align:start position:0% wants to connect to a web3 network maybe 00:10:52.860 --> 00:10:54.650 align:start position:0% wants to connect to a web3 network maybe they<00:10:53.100> just<00:10:53.220> need<00:10:53.399> to<00:10:53.579> send<00:10:53.760> a<00:10:53.940> transaction<00:10:54.300> to 00:10:54.650 --> 00:10:54.660 align:start position:0% they just need to send a transaction to 00:10:54.660 --> 00:10:56.690 align:start position:0% they just need to send a transaction to a<00:10:54.839> blockchain<00:10:55.200> maybe<00:10:55.920> they<00:10:56.160> need<00:10:56.279> to<00:10:56.399> read<00:10:56.519> a 00:10:56.690 --> 00:10:56.700 align:start position:0% a blockchain maybe they need to read a 00:10:56.700 --> 00:10:58.670 align:start position:0% a blockchain maybe they need to read a bunch<00:10:56.820> of<00:10:56.940> data<00:10:57.240> from<00:10:57.420> it<00:10:57.600> either<00:10:58.140> way<00:10:58.380> they 00:10:58.670 --> 00:10:58.680 align:start position:0% bunch of data from it either way they 00:10:58.680 --> 00:11:00.949 align:start position:0% bunch of data from it either way they need<00:10:58.860> some<00:10:59.100> way<00:10:59.279> to<00:10:59.459> access<00:10:59.700> the<00:11:00.180> API<00:11:00.540> that<00:11:00.779> a 00:11:00.949 --> 00:11:00.959 align:start position:0% need some way to access the API that a 00:11:00.959 --> 00:11:03.590 align:start position:0% need some way to access the API that a blockchain<00:11:01.260> node<00:11:01.560> typically<00:11:01.920> exposes<00:11:02.519> and<00:11:03.480> so 00:11:03.590 --> 00:11:03.600 align:start position:0% blockchain node typically exposes and so 00:11:03.600 --> 00:11:05.569 align:start position:0% blockchain node typically exposes and so the<00:11:03.839> first<00:11:03.959> participant<00:11:04.560> to<00:11:04.920> support<00:11:05.100> that 00:11:05.569 --> 00:11:05.579 align:start position:0% the first participant to support that 00:11:05.579 --> 00:11:07.550 align:start position:0% the first participant to support that are<00:11:05.940> the<00:11:06.180> infrastructure<00:11:06.660> providers<00:11:07.200> of 00:11:07.550 --> 00:11:07.560 align:start position:0% are the infrastructure providers of 00:11:07.560 --> 00:11:09.230 align:start position:0% are the infrastructure providers of course<00:11:07.680> and<00:11:08.579> they're<00:11:08.700> the<00:11:08.820> ones<00:11:09.000> that<00:11:09.120> are 00:11:09.230 --> 00:11:09.240 align:start position:0% course and they're the ones that are 00:11:09.240 --> 00:11:10.370 align:start position:0% course and they're the ones that are going<00:11:09.360> to<00:11:09.480> actually<00:11:09.660> be<00:11:09.899> writing<00:11:10.200> the 00:11:10.370 --> 00:11:10.380 align:start position:0% going to actually be writing the 00:11:10.380 --> 00:11:11.810 align:start position:0% going to actually be writing the blockchain<00:11:10.680> nodes<00:11:10.980> off<00:11:11.220> the<00:11:11.459> supporting 00:11:11.810 --> 00:11:11.820 align:start position:0% blockchain nodes off the supporting 00:11:11.820 --> 00:11:13.550 align:start position:0% blockchain nodes off the supporting infrastructure<00:11:12.480> that<00:11:12.779> makes<00:11:12.959> that<00:11:13.200> possible 00:11:13.550 --> 00:11:13.560 align:start position:0% infrastructure that makes that possible 00:11:13.560 --> 00:11:16.130 align:start position:0% infrastructure that makes that possible to<00:11:13.800> allow<00:11:14.220> for<00:11:14.579> high<00:11:15.180> throughput<00:11:15.540> of<00:11:15.720> requests 00:11:16.130 --> 00:11:16.140 align:start position:0% to allow for high throughput of requests 00:11:16.140 --> 00:11:17.990 align:start position:0% to allow for high throughput of requests to<00:11:16.380> send<00:11:16.560> all<00:11:16.740> the<00:11:16.860> transactions<00:11:17.519> to<00:11:17.820> read 00:11:17.990 --> 00:11:18.000 align:start position:0% to send all the transactions to read 00:11:18.000 --> 00:11:19.550 align:start position:0% to send all the transactions to read historical<00:11:18.420> data<00:11:18.779> all<00:11:18.899> of<00:11:19.079> those<00:11:19.200> things<00:11:19.380> that 00:11:19.550 --> 00:11:19.560 align:start position:0% historical data all of those things that 00:11:19.560 --> 00:11:20.930 align:start position:0% historical data all of those things that you<00:11:19.680> typically<00:11:19.980> do<00:11:20.160> with<00:11:20.339> the<00:11:20.459> centralized 00:11:20.930 --> 00:11:20.940 align:start position:0% you typically do with the centralized 00:11:20.940 --> 00:11:22.430 align:start position:0% you typically do with the centralized provider<00:11:21.300> and<00:11:21.779> they'll<00:11:22.019> provide<00:11:22.320> this 00:11:22.430 --> 00:11:22.440 align:start position:0% provider and they'll provide this 00:11:22.440 --> 00:11:24.530 align:start position:0% provider and they'll provide this service<00:11:22.620> in<00:11:22.860> return<00:11:22.980> for<00:11:23.220> a<00:11:23.339> reward 00:11:24.530 --> 00:11:24.540 align:start position:0% service in return for a reward 00:11:24.540 --> 00:11:25.850 align:start position:0% service in return for a reward um<00:11:24.600> which<00:11:24.779> is<00:11:24.899> what's<00:11:25.079> going<00:11:25.320> to<00:11:25.440> motivate 00:11:25.850 --> 00:11:25.860 align:start position:0% um which is what's going to motivate 00:11:25.860 --> 00:11:27.710 align:start position:0% um which is what's going to motivate them<00:11:25.980> to<00:11:26.160> want<00:11:26.279> to<00:11:26.399> do<00:11:26.519> this<00:11:26.760> uh<00:11:27.420> the<00:11:27.540> next 00:11:27.710 --> 00:11:27.720 align:start position:0% them to want to do this uh the next 00:11:27.720 --> 00:11:29.329 align:start position:0% them to want to do this uh the next participant<00:11:28.320> we're<00:11:28.740> calling<00:11:29.040> the<00:11:29.160> network 00:11:29.329 --> 00:11:29.339 align:start position:0% participant we're calling the network 00:11:29.339 --> 00:11:31.970 align:start position:0% participant we're calling the network status<00:11:29.700> Watchers<00:11:30.300> uh<00:11:31.019> this<00:11:31.380> party<00:11:31.500> will 00:11:31.970 --> 00:11:31.980 align:start position:0% status Watchers uh this party will 00:11:31.980 --> 00:11:33.470 align:start position:0% status Watchers uh this party will provide<00:11:32.339> performance<00:11:32.820> and<00:11:33.060> capability 00:11:33.470 --> 00:11:33.480 align:start position:0% provide performance and capability 00:11:33.480 --> 00:11:35.750 align:start position:0% provide performance and capability reports<00:11:34.079> of<00:11:34.440> the<00:11:34.740> infrastructure<00:11:35.160> providers 00:11:35.750 --> 00:11:35.760 align:start position:0% reports of the infrastructure providers 00:11:35.760 --> 00:11:37.790 align:start position:0% reports of the infrastructure providers uh<00:11:36.480> so<00:11:36.600> they'll<00:11:36.779> be<00:11:36.899> there<00:11:37.079> to<00:11:37.260> kind<00:11:37.440> of<00:11:37.560> check 00:11:37.790 --> 00:11:37.800 align:start position:0% uh so they'll be there to kind of check 00:11:37.800 --> 00:11:39.769 align:start position:0% uh so they'll be there to kind of check and<00:11:38.339> keep<00:11:38.579> them<00:11:38.760> honest<00:11:39.060> you<00:11:39.360> know<00:11:39.420> they'll 00:11:39.769 --> 00:11:39.779 align:start position:0% and keep them honest you know they'll 00:11:39.779 --> 00:11:41.030 align:start position:0% and keep them honest you know they'll they'll<00:11:40.140> see<00:11:40.320> that<00:11:40.440> they're<00:11:40.560> keeping<00:11:40.800> up<00:11:40.920> with 00:11:41.030 --> 00:11:41.040 align:start position:0% they'll see that they're keeping up with 00:11:41.040 --> 00:11:42.769 align:start position:0% they'll see that they're keeping up with the<00:11:41.160> head<00:11:41.279> of<00:11:41.459> the<00:11:41.579> chain<00:11:41.760> they'll<00:11:42.240> check<00:11:42.420> that 00:11:42.769 --> 00:11:42.779 align:start position:0% the head of the chain they'll check that 00:11:42.779 --> 00:11:44.690 align:start position:0% the head of the chain they'll check that they're<00:11:42.959> you<00:11:43.140> know<00:11:43.260> responding<00:11:43.800> quickly<00:11:44.279> that 00:11:44.690 --> 00:11:44.700 align:start position:0% they're you know responding quickly that 00:11:44.700 --> 00:11:47.030 align:start position:0% they're you know responding quickly that their<00:11:45.060> uh<00:11:45.360> answers<00:11:45.720> are<00:11:45.959> accurate<00:11:46.380> all<00:11:46.800> the 00:11:47.030 --> 00:11:47.040 align:start position:0% their uh answers are accurate all the 00:11:47.040 --> 00:11:49.250 align:start position:0% their uh answers are accurate all the things<00:11:47.220> that<00:11:47.579> you<00:11:47.700> would<00:11:47.880> hope<00:11:48.180> that<00:11:48.779> an<00:11:48.899> API 00:11:49.250 --> 00:11:49.260 align:start position:0% things that you would hope that an API 00:11:49.260 --> 00:11:51.769 align:start position:0% things that you would hope that an API does<00:11:49.560> and<00:11:50.459> finally<00:11:50.700> we<00:11:51.000> have<00:11:51.120> this<00:11:51.300> concept<00:11:51.600> of 00:11:51.769 --> 00:11:51.779 align:start position:0% does and finally we have this concept of 00:11:51.779 --> 00:11:54.230 align:start position:0% does and finally we have this concept of an<00:11:51.899> Ingress<00:11:52.200> node<00:11:52.620> they<00:11:53.459> kind<00:11:53.640> of<00:11:53.700> act<00:11:53.820> as<00:11:54.000> an 00:11:54.230 --> 00:11:54.240 align:start position:0% an Ingress node they kind of act as an 00:11:54.240 --> 00:11:57.110 align:start position:0% an Ingress node they kind of act as an intermediary<00:11:54.980> they<00:11:55.980> will<00:11:56.279> sell<00:11:56.579> the<00:11:56.820> actual 00:11:57.110 --> 00:11:57.120 align:start position:0% intermediary they will sell the actual 00:11:57.120 --> 00:11:58.730 align:start position:0% intermediary they will sell the actual network<00:11:57.300> resources<00:11:57.899> to<00:11:58.140> users<00:11:58.440> after 00:11:58.730 --> 00:11:58.740 align:start position:0% network resources to users after 00:11:58.740 --> 00:12:00.530 align:start position:0% network resources to users after purchasing<00:11:59.279> them<00:11:59.519> from<00:11:59.820> the<00:12:00.000> infrastructure 00:12:00.530 --> 00:12:00.540 align:start position:0% purchasing them from the infrastructure 00:12:00.540 --> 00:12:03.110 align:start position:0% purchasing them from the infrastructure providers<00:12:01.019> and<00:12:01.920> later<00:12:02.160> I'll<00:12:02.459> also<00:12:02.700> show<00:12:02.940> how 00:12:03.110 --> 00:12:03.120 align:start position:0% providers and later I'll also show how 00:12:03.120 --> 00:12:04.850 align:start position:0% providers and later I'll also show how they're<00:12:03.300> not<00:12:03.480> entirely<00:12:03.899> necessary<00:12:04.320> but<00:12:04.620> they 00:12:04.850 --> 00:12:04.860 align:start position:0% they're not entirely necessary but they 00:12:04.860 --> 00:12:07.670 align:start position:0% they're not entirely necessary but they can<00:12:04.980> provide<00:12:05.459> a<00:12:06.120> ux<00:12:06.600> option<00:12:07.019> that<00:12:07.260> I<00:12:07.380> think<00:12:07.500> is 00:12:07.670 --> 00:12:07.680 align:start position:0% can provide a ux option that I think is 00:12:07.680 --> 00:12:09.889 align:start position:0% can provide a ux option that I think is useful<00:12:08.000> so<00:12:09.000> more<00:12:09.360> detail<00:12:09.600> on<00:12:09.779> the 00:12:09.889 --> 00:12:09.899 align:start position:0% useful so more detail on the 00:12:09.899 --> 00:12:11.509 align:start position:0% useful so more detail on the infrastructure<00:12:10.260> providers<00:12:10.860> the<00:12:11.220> first<00:12:11.339> thing 00:12:11.509 --> 00:12:11.519 align:start position:0% infrastructure providers the first thing 00:12:11.519 --> 00:12:13.490 align:start position:0% infrastructure providers the first thing of<00:12:11.700> course<00:12:11.820> to<00:12:12.060> note<00:12:12.180> is<00:12:12.600> that<00:12:12.779> instead<00:12:13.200> of<00:12:13.260> now 00:12:13.490 --> 00:12:13.500 align:start position:0% of course to note is that instead of now 00:12:13.500 --> 00:12:15.290 align:start position:0% of course to note is that instead of now with<00:12:13.860> just<00:12:14.040> a<00:12:14.160> single<00:12:14.399> centralized<00:12:14.880> provider 00:12:15.290 --> 00:12:15.300 align:start position:0% with just a single centralized provider 00:12:15.300 --> 00:12:17.210 align:start position:0% with just a single centralized provider we'll<00:12:16.079> have<00:12:16.260> many<00:12:16.440> of<00:12:16.560> them<00:12:16.740> and<00:12:16.980> they<00:12:17.100> won't 00:12:17.210 --> 00:12:17.220 align:start position:0% we'll have many of them and they won't 00:12:17.220 --> 00:12:19.670 align:start position:0% we'll have many of them and they won't be<00:12:17.399> run<00:12:17.579> by<00:12:17.880> a<00:12:18.000> single<00:12:18.300> party<00:12:18.480> so<00:12:19.200> here<00:12:19.380> we<00:12:19.560> just 00:12:19.670 --> 00:12:19.680 align:start position:0% be run by a single party so here we just 00:12:19.680 --> 00:12:22.130 align:start position:0% be run by a single party so here we just have<00:12:19.860> a<00:12:20.100> little<00:12:20.279> simple<00:12:20.579> diagram<00:12:21.060> we<00:12:22.019> have 00:12:22.130 --> 00:12:22.140 align:start position:0% have a little simple diagram we have 00:12:22.140 --> 00:12:23.870 align:start position:0% have a little simple diagram we have inferior<00:12:22.620> we'll<00:12:22.920> probably<00:12:23.160> run<00:12:23.459> one<00:12:23.700> of 00:12:23.870 --> 00:12:23.880 align:start position:0% inferior we'll probably run one of 00:12:23.880 --> 00:12:26.389 align:start position:0% inferior we'll probably run one of course<00:12:24.000> uh<00:12:24.540> you'll<00:12:24.839> also<00:12:25.079> see<00:12:25.320> other<00:12:25.680> named 00:12:26.389 --> 00:12:26.399 align:start position:0% course uh you'll also see other named 00:12:26.399 --> 00:12:27.829 align:start position:0% course uh you'll also see other named providers<00:12:26.940> that<00:12:27.180> you're<00:12:27.300> used<00:12:27.480> to<00:12:27.600> seeing 00:12:27.829 --> 00:12:27.839 align:start position:0% providers that you're used to seeing 00:12:27.839 --> 00:12:29.269 align:start position:0% providers that you're used to seeing that<00:12:28.019> we<00:12:28.200> hope<00:12:28.320> will<00:12:28.500> collaborate<00:12:28.920> with<00:12:29.100> us 00:12:29.269 --> 00:12:29.279 align:start position:0% that we hope will collaborate with us 00:12:29.279 --> 00:12:30.889 align:start position:0% that we hope will collaborate with us and<00:12:29.820> you<00:12:30.000> might<00:12:30.120> also<00:12:30.300> have<00:12:30.420> Anonymous 00:12:30.889 --> 00:12:30.899 align:start position:0% and you might also have Anonymous 00:12:30.899 --> 00:12:32.329 align:start position:0% and you might also have Anonymous providers<00:12:31.320> so<00:12:31.500> you<00:12:31.680> never<00:12:31.800> really<00:12:31.980> know<00:12:32.160> who 00:12:32.329 --> 00:12:32.339 align:start position:0% providers so you never really know who 00:12:32.339 --> 00:12:34.250 align:start position:0% providers so you never really know who they<00:12:32.519> are<00:12:32.640> but<00:12:33.240> through<00:12:33.480> the<00:12:33.600> mechanisms<00:12:34.079> of 00:12:34.250 --> 00:12:34.260 align:start position:0% they are but through the mechanisms of 00:12:34.260 --> 00:12:36.410 align:start position:0% they are but through the mechanisms of the<00:12:34.380> network<00:12:34.560> you<00:12:35.519> can<00:12:35.579> come<00:12:35.700> to<00:12:35.880> trust<00:12:36.180> that 00:12:36.410 --> 00:12:36.420 align:start position:0% the network you can come to trust that 00:12:36.420 --> 00:12:37.730 align:start position:0% the network you can come to trust that they<00:12:36.600> are<00:12:36.779> going<00:12:36.899> to<00:12:37.019> provide<00:12:37.260> a<00:12:37.380> good<00:12:37.500> service 00:12:37.730 --> 00:12:37.740 align:start position:0% they are going to provide a good service 00:12:37.740 --> 00:12:40.310 align:start position:0% they are going to provide a good service so<00:12:38.399> these<00:12:38.700> infrastructure<00:12:39.120> providers<00:12:39.660> they 00:12:40.310 --> 00:12:40.320 align:start position:0% so these infrastructure providers they 00:12:40.320 --> 00:12:42.170 align:start position:0% so these infrastructure providers they commit<00:12:40.620> to<00:12:40.740> providing<00:12:41.220> capacity<00:12:41.760> on<00:12:42.060> the 00:12:42.170 --> 00:12:42.180 align:start position:0% commit to providing capacity on the 00:12:42.180 --> 00:12:44.569 align:start position:0% commit to providing capacity on the network<00:12:42.440> they'll<00:12:43.440> specify<00:12:43.740> the<00:12:44.040> protocols 00:12:44.569 --> 00:12:44.579 align:start position:0% network they'll specify the protocols 00:12:44.579 --> 00:12:46.790 align:start position:0% network they'll specify the protocols and<00:12:44.760> capabilities<00:12:45.240> that<00:12:45.600> they<00:12:45.779> support<00:12:45.959> so<00:12:46.680> we 00:12:46.790 --> 00:12:46.800 align:start position:0% and capabilities that they support so we 00:12:46.800 --> 00:12:48.769 align:start position:0% and capabilities that they support so we envision<00:12:47.160> this<00:12:47.459> network<00:12:47.760> working<00:12:48.480> for 00:12:48.769 --> 00:12:48.779 align:start position:0% envision this network working for 00:12:48.779 --> 00:12:51.170 align:start position:0% envision this network working for ethereum<00:12:49.260> but<00:12:49.560> we<00:12:49.680> also<00:12:49.920> Envision<00:12:50.339> Envision 00:12:51.170 --> 00:12:51.180 align:start position:0% ethereum but we also Envision Envision 00:12:51.180 --> 00:12:52.730 align:start position:0% ethereum but we also Envision Envision it<00:12:51.420> supporting<00:12:51.839> all<00:12:52.079> of<00:12:52.200> the<00:12:52.320> sort<00:12:52.500> of<00:12:52.620> new 00:12:52.730 --> 00:12:52.740 align:start position:0% it supporting all of the sort of new 00:12:52.740 --> 00:12:54.170 align:start position:0% it supporting all of the sort of new networks<00:12:53.100> that<00:12:53.160> inferior<00:12:53.639> has<00:12:53.760> added<00:12:54.000> over 00:12:54.170 --> 00:12:54.180 align:start position:0% networks that inferior has added over 00:12:54.180 --> 00:12:56.329 align:start position:0% networks that inferior has added over the<00:12:54.360> last<00:12:54.480> couple<00:12:54.720> of<00:12:54.899> years<00:12:55.079> the<00:12:55.740> layer<00:12:56.040> twos 00:12:56.329 --> 00:12:56.339 align:start position:0% the last couple of years the layer twos 00:12:56.339 --> 00:12:58.009 align:start position:0% the last couple of years the layer twos new<00:12:56.639> layer<00:12:56.940> ones<00:12:57.300> but<00:12:57.720> not<00:12:57.839> every 00:12:58.009 --> 00:12:58.019 align:start position:0% new layer ones but not every 00:12:58.019 --> 00:12:59.389 align:start position:0% new layer ones but not every infrastructure<00:12:58.500> provider<00:12:58.920> is<00:12:59.040> going<00:12:59.160> to<00:12:59.279> want 00:12:59.389 --> 00:12:59.399 align:start position:0% infrastructure provider is going to want 00:12:59.399 --> 00:13:00.889 align:start position:0% infrastructure provider is going to want to<00:12:59.579> serve<00:12:59.820> all<00:12:59.880> of<00:13:00.000> those<00:13:00.180> so<00:13:00.420> they<00:13:00.600> can<00:13:00.720> pick 00:13:00.889 --> 00:13:00.899 align:start position:0% to serve all of those so they can pick 00:13:00.899 --> 00:13:02.810 align:start position:0% to serve all of those so they can pick and<00:13:01.079> choose<00:13:01.380> and<00:13:01.740> specify<00:13:02.160> what<00:13:02.399> they<00:13:02.519> want<00:13:02.700> to 00:13:02.810 --> 00:13:02.820 align:start position:0% and choose and specify what they want to 00:13:02.820 --> 00:13:04.610 align:start position:0% and choose and specify what they want to support<00:13:03.079> they'll<00:13:04.079> also<00:13:04.320> say<00:13:04.440> the 00:13:04.610 --> 00:13:04.620 align:start position:0% support they'll also say the 00:13:04.620 --> 00:13:06.889 align:start position:0% support they'll also say the capabilities<00:13:05.100> so<00:13:05.639> you<00:13:06.300> might<00:13:06.480> be<00:13:06.600> used<00:13:06.779> to 00:13:06.889 --> 00:13:06.899 align:start position:0% capabilities so you might be used to 00:13:06.899 --> 00:13:08.509 align:start position:0% capabilities so you might be used to having<00:13:07.260> you<00:13:07.560> know<00:13:07.620> archive<00:13:07.980> nodes<00:13:08.279> for 00:13:08.509 --> 00:13:08.519 align:start position:0% having you know archive nodes for 00:13:08.519 --> 00:13:10.069 align:start position:0% having you know archive nodes for ethereum<00:13:08.940> and<00:13:09.240> then<00:13:09.360> sometimes<00:13:09.779> you<00:13:09.959> need 00:13:10.069 --> 00:13:10.079 align:start position:0% ethereum and then sometimes you need 00:13:10.079 --> 00:13:11.870 align:start position:0% ethereum and then sometimes you need that<00:13:10.260> sometimes<00:13:10.680> you<00:13:10.860> don't<00:13:11.040> and<00:13:11.519> running 00:13:11.870 --> 00:13:11.880 align:start position:0% that sometimes you don't and running 00:13:11.880 --> 00:13:14.449 align:start position:0% that sometimes you don't and running archive<00:13:12.480> traffic<00:13:12.720> is<00:13:13.139> a<00:13:13.260> lot<00:13:13.380> harder<00:13:13.740> so<00:13:14.220> some 00:13:14.449 --> 00:13:14.459 align:start position:0% archive traffic is a lot harder so some 00:13:14.459 --> 00:13:16.329 align:start position:0% archive traffic is a lot harder so some providers<00:13:14.820> might<00:13:15.060> do<00:13:15.240> that<00:13:15.420> some<00:13:15.660> might<00:13:15.899> not 00:13:16.329 --> 00:13:16.339 align:start position:0% providers might do that some might not 00:13:16.339 --> 00:13:19.250 align:start position:0% providers might do that some might not they'll<00:13:17.339> also<00:13:17.579> give<00:13:17.940> an<00:13:18.300> idea<00:13:18.600> of<00:13:18.839> the<00:13:19.019> amount 00:13:19.250 --> 00:13:19.260 align:start position:0% they'll also give an idea of the amount 00:13:19.260 --> 00:13:20.690 align:start position:0% they'll also give an idea of the amount of<00:13:19.380> throughput<00:13:19.800> that<00:13:20.100> they're<00:13:20.220> capable<00:13:20.519> of 00:13:20.690 --> 00:13:20.700 align:start position:0% of throughput that they're capable of 00:13:20.700 --> 00:13:22.910 align:start position:0% of throughput that they're capable of specifying<00:13:21.360> and<00:13:21.959> this<00:13:22.200> may<00:13:22.440> take<00:13:22.680> a<00:13:22.800> couple 00:13:22.910 --> 00:13:22.920 align:start position:0% specifying and this may take a couple 00:13:22.920 --> 00:13:24.590 align:start position:0% specifying and this may take a couple different<00:13:23.100> shapes<00:13:23.579> but<00:13:23.700> you<00:13:23.820> know<00:13:24.000> you<00:13:24.480> could 00:13:24.590 --> 00:13:24.600 align:start position:0% different shapes but you know you could 00:13:24.600 --> 00:13:25.790 align:start position:0% different shapes but you know you could think<00:13:24.720> of<00:13:24.779> it<00:13:24.839> as<00:13:24.959> like<00:13:25.139> a<00:13:25.200> thousand<00:13:25.440> requests 00:13:25.790 --> 00:13:25.800 align:start position:0% think of it as like a thousand requests 00:13:25.800 --> 00:13:27.470 align:start position:0% think of it as like a thousand requests per<00:13:25.920> minute<00:13:26.040> when<00:13:26.399> someone<00:13:26.579> registers<00:13:27.060> as<00:13:27.300> a 00:13:27.470 --> 00:13:27.480 align:start position:0% per minute when someone registers as a 00:13:27.480 --> 00:13:29.090 align:start position:0% per minute when someone registers as a provider<00:13:27.959> they're<00:13:28.380> saying<00:13:28.680> I<00:13:28.800> can<00:13:28.920> support 00:13:29.090 --> 00:13:29.100 align:start position:0% provider they're saying I can support 00:13:29.100 --> 00:13:30.710 align:start position:0% provider they're saying I can support this<00:13:29.459> much<00:13:29.639> and<00:13:29.820> so<00:13:30.000> that<00:13:30.120> people<00:13:30.300> can<00:13:30.600> then 00:13:30.710 --> 00:13:30.720 align:start position:0% this much and so that people can then 00:13:30.720 --> 00:13:32.690 align:start position:0% this much and so that people can then buy<00:13:30.959> that<00:13:31.200> back<00:13:31.380> and<00:13:32.040> of<00:13:32.220> course<00:13:32.339> they'll<00:13:32.519> be 00:13:32.690 --> 00:13:32.700 align:start position:0% buy that back and of course they'll be 00:13:32.700 --> 00:13:35.269 align:start position:0% buy that back and of course they'll be compensated<00:13:33.120> for<00:13:33.420> for<00:13:33.600> doing<00:13:33.839> this 00:13:35.269 --> 00:13:35.279 align:start position:0% compensated for for doing this 00:13:35.279 --> 00:13:37.009 align:start position:0% compensated for for doing this I<00:13:35.700> want<00:13:35.880> to<00:13:36.000> talk<00:13:36.120> a<00:13:36.240> little<00:13:36.360> bit<00:13:36.480> about<00:13:36.660> what 00:13:37.009 --> 00:13:37.019 align:start position:0% I want to talk a little bit about what 00:13:37.019 --> 00:13:39.889 align:start position:0% I want to talk a little bit about what it<00:13:37.139> actually<00:13:37.320> looks<00:13:37.740> to<00:13:37.980> be<00:13:38.279> a<00:13:38.459> node<00:13:38.639> provider 00:13:39.889 --> 00:13:39.899 align:start position:0% it actually looks to be a node provider 00:13:39.899 --> 00:13:42.230 align:start position:0% it actually looks to be a node provider um<00:13:39.959> and<00:13:40.380> so<00:13:40.500> this<00:13:40.740> is<00:13:40.860> a<00:13:41.040> diagram<00:13:41.339> of<00:13:41.940> what 00:13:42.230 --> 00:13:42.240 align:start position:0% um and so this is a diagram of what 00:13:42.240 --> 00:13:44.269 align:start position:0% um and so this is a diagram of what inferior<00:13:42.720> does<00:13:43.019> and<00:13:43.320> what<00:13:43.500> other<00:13:43.800> big 00:13:44.269 --> 00:13:44.279 align:start position:0% inferior does and what other big 00:13:44.279 --> 00:13:46.730 align:start position:0% inferior does and what other big centralized<00:13:44.880> providers<00:13:45.360> do<00:13:45.740> it's 00:13:46.730 --> 00:13:46.740 align:start position:0% centralized providers do it's 00:13:46.740 --> 00:13:48.530 align:start position:0% centralized providers do it's complicated<00:13:47.220> as<00:13:47.459> EG<00:13:47.639> said<00:13:47.940> it's<00:13:48.060> become<00:13:48.360> much 00:13:48.530 --> 00:13:48.540 align:start position:0% complicated as EG said it's become much 00:13:48.540 --> 00:13:51.170 align:start position:0% complicated as EG said it's become much more<00:13:48.720> complicated<00:13:49.139> since<00:13:49.380> 2016.<00:13:50.220> to<00:13:50.760> start<00:13:50.940> of 00:13:51.170 --> 00:13:51.180 align:start position:0% more complicated since 2016. to start of 00:13:51.180 --> 00:13:52.670 align:start position:0% more complicated since 2016. to start of course<00:13:51.300> you<00:13:51.540> have<00:13:51.660> your<00:13:51.839> blockchain<00:13:52.260> nodes 00:13:52.670 --> 00:13:52.680 align:start position:0% course you have your blockchain nodes 00:13:52.680 --> 00:13:54.710 align:start position:0% course you have your blockchain nodes these<00:13:53.100> are<00:13:53.220> the<00:13:53.519> the<00:13:53.820> ones<00:13:54.120> that<00:13:54.240> are<00:13:54.420> produced 00:13:54.710 --> 00:13:54.720 align:start position:0% these are the the ones that are produced 00:13:54.720 --> 00:13:56.329 align:start position:0% these are the the ones that are produced by<00:13:54.899> the<00:13:55.079> client<00:13:55.320> teams<00:13:55.680> that<00:13:55.860> interact<00:13:56.220> with 00:13:56.329 --> 00:13:56.339 align:start position:0% by the client teams that interact with 00:13:56.339 --> 00:13:58.370 align:start position:0% by the client teams that interact with the<00:13:56.459> peer-to-peer<00:13:57.000> Network<00:13:57.180> that<00:13:58.019> sync 00:13:58.370 --> 00:13:58.380 align:start position:0% the peer-to-peer Network that sync 00:13:58.380 --> 00:14:01.310 align:start position:0% the peer-to-peer Network that sync blocks<00:13:58.680> that<00:13:58.800> verify<00:13:59.220> it<00:13:59.399> but 00:14:01.310 --> 00:14:01.320 align:start position:0% blocks that verify it but 00:14:01.320 --> 00:14:02.389 align:start position:0% blocks that verify it but um there's<00:14:01.740> a<00:14:01.860> lot<00:14:01.980> of<00:14:02.100> supporting 00:14:02.389 --> 00:14:02.399 align:start position:0% um there's a lot of supporting 00:14:02.399 --> 00:14:03.889 align:start position:0% um there's a lot of supporting infrastructure<00:14:02.820> around<00:14:03.000> that<00:14:03.240> so<00:14:03.480> first<00:14:03.660> we 00:14:03.889 --> 00:14:03.899 align:start position:0% infrastructure around that so first we 00:14:03.899 --> 00:14:06.110 align:start position:0% infrastructure around that so first we have<00:14:04.019> a<00:14:04.139> snapshot<00:14:04.560> system<00:14:04.920> uh<00:14:05.700> if<00:14:05.880> you've<00:14:06.000> ever 00:14:06.110 --> 00:14:06.120 align:start position:0% have a snapshot system uh if you've ever 00:14:06.120 --> 00:14:07.550 align:start position:0% have a snapshot system uh if you've ever tried<00:14:06.300> to<00:14:06.360> sync<00:14:06.660> a<00:14:06.779> node<00:14:06.899> you'll<00:14:07.139> know<00:14:07.260> that<00:14:07.380> it 00:14:07.550 --> 00:14:07.560 align:start position:0% tried to sync a node you'll know that it 00:14:07.560 --> 00:14:09.949 align:start position:0% tried to sync a node you'll know that it takes<00:14:07.740> a<00:14:07.860> very<00:14:07.980> long<00:14:08.220> time<00:14:08.519> so<00:14:09.360> we<00:14:09.600> typically 00:14:09.949 --> 00:14:09.959 align:start position:0% takes a very long time so we typically 00:14:09.959 --> 00:14:12.590 align:start position:0% takes a very long time so we typically take<00:14:10.320> the<00:14:10.560> disk<00:14:10.920> of<00:14:11.399> a<00:14:11.700> blockchain<00:14:12.060> node<00:14:12.360> save 00:14:12.590 --> 00:14:12.600 align:start position:0% take the disk of a blockchain node save 00:14:12.600 --> 00:14:14.569 align:start position:0% take the disk of a blockchain node save it<00:14:12.779> to<00:14:12.899> our<00:14:13.019> own<00:14:13.200> private<00:14:13.560> Secure<00:14:13.860> Storage<00:14:14.100> and 00:14:14.569 --> 00:14:14.579 align:start position:0% it to our own private Secure Storage and 00:14:14.579 --> 00:14:15.889 align:start position:0% it to our own private Secure Storage and then<00:14:14.760> when<00:14:14.880> we<00:14:15.000> need<00:14:15.180> a<00:14:15.300> horizontally<00:14:15.660> scale 00:14:15.889 --> 00:14:15.899 align:start position:0% then when we need a horizontally scale 00:14:15.899 --> 00:14:17.629 align:start position:0% then when we need a horizontally scale out<00:14:16.079> those<00:14:16.260> nodes<00:14:16.440> we<00:14:16.740> use<00:14:16.920> that<00:14:17.100> as<00:14:17.279> a<00:14:17.399> seed 00:14:17.629 --> 00:14:17.639 align:start position:0% out those nodes we use that as a seed 00:14:17.639 --> 00:14:19.129 align:start position:0% out those nodes we use that as a seed for<00:14:17.880> new<00:14:18.060> blockchain<00:14:18.540> nodes<00:14:18.839> so<00:14:19.019> it's 00:14:19.129 --> 00:14:19.139 align:start position:0% for new blockchain nodes so it's 00:14:19.139 --> 00:14:21.230 align:start position:0% for new blockchain nodes so it's downloaded<00:14:19.620> onto<00:14:19.920> a<00:14:20.160> server<00:14:20.399> and<00:14:20.820> then<00:14:20.940> sync 00:14:21.230 --> 00:14:21.240 align:start position:0% downloaded onto a server and then sync 00:14:21.240 --> 00:14:22.550 align:start position:0% downloaded onto a server and then sync from<00:14:21.360> there<00:14:21.480> which<00:14:21.720> makes<00:14:21.839> it<00:14:22.019> much<00:14:22.200> faster 00:14:22.550 --> 00:14:22.560 align:start position:0% from there which makes it much faster 00:14:22.560 --> 00:14:24.590 align:start position:0% from there which makes it much faster you<00:14:23.399> also<00:14:23.639> have<00:14:23.700> various<00:14:23.940> indexers<00:14:24.420> and 00:14:24.590 --> 00:14:24.600 align:start position:0% you also have various indexers and 00:14:24.600 --> 00:14:28.009 align:start position:0% you also have various indexers and accelerators<00:14:25.639> so<00:14:26.639> if<00:14:27.240> you've<00:14:27.420> ever<00:14:27.540> tried<00:14:27.839> to 00:14:28.009 --> 00:14:28.019 align:start position:0% accelerators so if you've ever tried to 00:14:28.019 --> 00:14:30.650 align:start position:0% accelerators so if you've ever tried to do<00:14:28.200> like<00:14:28.440> a<00:14:28.740> big<00:14:28.920> wide<00:14:29.459> get<00:14:29.639> logs<00:14:30.120> query<00:14:30.420> for 00:14:30.650 --> 00:14:30.660 align:start position:0% do like a big wide get logs query for 00:14:30.660 --> 00:14:32.090 align:start position:0% do like a big wide get logs query for events<00:14:31.019> from<00:14:31.200> a<00:14:31.320> blockchain<00:14:31.680> node<00:14:31.860> you'll 00:14:32.090 --> 00:14:32.100 align:start position:0% events from a blockchain node you'll 00:14:32.100 --> 00:14:34.190 align:start position:0% events from a blockchain node you'll know<00:14:32.160> it's<00:14:32.279> really<00:14:32.399> slow<00:14:32.639> so<00:14:33.540> we<00:14:33.720> have<00:14:33.899> special 00:14:34.190 --> 00:14:34.200 align:start position:0% know it's really slow so we have special 00:14:34.200 --> 00:14:36.650 align:start position:0% know it's really slow so we have special indexers<00:14:34.740> to<00:14:34.920> speed<00:14:35.160> that<00:14:35.639> up<00:14:35.880> also<00:14:36.540> for 00:14:36.650 --> 00:14:36.660 align:start position:0% indexers to speed that up also for 00:14:36.660 --> 00:14:39.050 align:start position:0% indexers to speed that up also for things<00:14:36.839> like<00:14:36.959> nfts<00:14:37.620> in<00:14:38.519> front<00:14:38.639> of<00:14:38.760> that<00:14:38.880> you 00:14:39.050 --> 00:14:39.060 align:start position:0% things like nfts in front of that you 00:14:39.060 --> 00:14:40.430 align:start position:0% things like nfts in front of that you have<00:14:39.180> a<00:14:39.300> load<00:14:39.540> balancer<00:14:39.899> that<00:14:40.139> makes<00:14:40.260> the 00:14:40.430 --> 00:14:40.440 align:start position:0% have a load balancer that makes the 00:14:40.440 --> 00:14:42.290 align:start position:0% have a load balancer that makes the decision<00:14:40.740> of<00:14:41.100> what<00:14:41.279> accelerators<00:14:41.940> to<00:14:42.120> send 00:14:42.290 --> 00:14:42.300 align:start position:0% decision of what accelerators to send 00:14:42.300 --> 00:14:44.810 align:start position:0% decision of what accelerators to send your<00:14:42.540> request<00:14:42.839> to<00:14:43.139> maybe<00:14:43.920> for<00:14:44.220> just<00:14:44.459> sending<00:14:44.699> a 00:14:44.810 --> 00:14:44.820 align:start position:0% your request to maybe for just sending a 00:14:44.820 --> 00:14:46.069 align:start position:0% your request to maybe for just sending a transaction<00:14:45.120> it<00:14:45.360> goes<00:14:45.600> directly<00:14:45.779> to<00:14:45.899> the 00:14:46.069 --> 00:14:46.079 align:start position:0% transaction it goes directly to the 00:14:46.079 --> 00:14:47.930 align:start position:0% transaction it goes directly to the nodes<00:14:46.260> and<00:14:46.800> in<00:14:47.040> front<00:14:47.100> of<00:14:47.220> all<00:14:47.339> of<00:14:47.459> that<00:14:47.579> we 00:14:47.930 --> 00:14:47.940 align:start position:0% nodes and in front of all of that we 00:14:47.940 --> 00:14:49.910 align:start position:0% nodes and in front of all of that we often<00:14:48.240> have<00:14:48.360> a<00:14:48.540> consistency<00:14:49.139> system<00:14:49.500> that 00:14:49.910 --> 00:14:49.920 align:start position:0% often have a consistency system that 00:14:49.920 --> 00:14:51.410 align:start position:0% often have a consistency system that helps<00:14:50.160> make<00:14:50.339> sure<00:14:50.459> that<00:14:50.639> users<00:14:51.000> see<00:14:51.240> a 00:14:51.410 --> 00:14:51.420 align:start position:0% helps make sure that users see a 00:14:51.420 --> 00:14:53.269 align:start position:0% helps make sure that users see a canonical<00:14:51.779> view<00:14:52.019> of<00:14:52.139> the<00:14:52.320> chain<00:14:52.440> so<00:14:53.160> this 00:14:53.269 --> 00:14:53.279 align:start position:0% canonical view of the chain so this 00:14:53.279 --> 00:14:55.310 align:start position:0% canonical view of the chain so this helps<00:14:53.579> with<00:14:53.699> reorgs<00:14:54.480> to<00:14:54.720> make<00:14:54.839> those<00:14:55.079> a<00:14:55.260> little 00:14:55.310 --> 00:14:55.320 align:start position:0% helps with reorgs to make those a little 00:14:55.320 --> 00:14:57.470 align:start position:0% helps with reorgs to make those a little less<00:14:55.500> painful<00:14:55.860> for<00:14:56.040> the<00:14:56.220> user<00:14:56.519> and<00:14:57.060> also<00:14:57.300> make 00:14:57.470 --> 00:14:57.480 align:start position:0% less painful for the user and also make 00:14:57.480 --> 00:15:00.590 align:start position:0% less painful for the user and also make sure<00:14:57.660> that<00:14:58.079> if<00:14:58.980> they<00:14:59.100> like<00:14:59.279> query<00:14:59.639> a<00:14:59.820> block<00:14:59.940> it 00:15:00.590 --> 00:15:00.600 align:start position:0% sure that if they like query a block it 00:15:00.600 --> 00:15:03.110 align:start position:0% sure that if they like query a block it doesn't<00:15:00.720> change<00:15:00.959> in<00:15:01.199> between<00:15:01.320> requests<00:15:02.120> and 00:15:03.110 --> 00:15:03.120 align:start position:0% doesn't change in between requests and 00:15:03.120 --> 00:15:04.370 align:start position:0% doesn't change in between requests and this<00:15:03.360> is<00:15:03.480> something<00:15:03.720> that<00:15:03.959> is<00:15:04.079> altogether 00:15:04.370 --> 00:15:04.380 align:start position:0% this is something that is altogether 00:15:04.380 --> 00:15:06.170 align:start position:0% this is something that is altogether quite<00:15:04.800> complicated<00:15:05.220> there's<00:15:05.519> been<00:15:05.760> several 00:15:06.170 --> 00:15:06.180 align:start position:0% quite complicated there's been several 00:15:06.180 --> 00:15:09.170 align:start position:0% quite complicated there's been several uh<00:15:07.019> projects<00:15:07.500> out<00:15:07.740> in<00:15:08.040> open<00:15:08.160> source<00:15:08.579> land<00:15:08.699> that 00:15:09.170 --> 00:15:09.180 align:start position:0% uh projects out in open source land that 00:15:09.180 --> 00:15:11.150 align:start position:0% uh projects out in open source land that have<00:15:09.480> attempted<00:15:10.139> to<00:15:10.260> help<00:15:10.380> with<00:15:10.560> this<00:15:10.740> I<00:15:11.040> think 00:15:11.150 --> 00:15:11.160 align:start position:0% have attempted to help with this I think 00:15:11.160 --> 00:15:13.730 align:start position:0% have attempted to help with this I think most<00:15:11.459> of<00:15:11.639> them<00:15:11.760> are<00:15:12.180> you<00:15:13.079> know<00:15:13.139> more<00:15:13.380> on<00:15:13.560> just 00:15:13.730 --> 00:15:13.740 align:start position:0% most of them are you know more on just 00:15:13.740 --> 00:15:15.050 align:start position:0% most of them are you know more on just running<00:15:13.980> the<00:15:14.220> blockchain<00:15:14.579> nodes<00:15:14.880> running 00:15:15.050 --> 00:15:15.060 align:start position:0% running the blockchain nodes running 00:15:15.060 --> 00:15:16.610 align:start position:0% running the blockchain nodes running several<00:15:15.480> of<00:15:15.540> those<00:15:15.720> but<00:15:15.959> to<00:15:16.079> really<00:15:16.260> provide 00:15:16.610 --> 00:15:16.620 align:start position:0% several of those but to really provide 00:15:16.620 --> 00:15:17.930 align:start position:0% several of those but to really provide good<00:15:16.800> service<00:15:16.980> you<00:15:17.279> need<00:15:17.399> a<00:15:17.519> lot<00:15:17.579> more<00:15:17.760> than 00:15:17.930 --> 00:15:17.940 align:start position:0% good service you need a lot more than 00:15:17.940 --> 00:15:20.689 align:start position:0% good service you need a lot more than that<00:15:18.120> and<00:15:18.839> we<00:15:18.959> will<00:15:19.139> be<00:15:19.320> releasing<00:15:20.220> our<00:15:20.519> own 00:15:20.689 --> 00:15:20.699 align:start position:0% that and we will be releasing our own 00:15:20.699 --> 00:15:23.030 align:start position:0% that and we will be releasing our own open<00:15:20.940> source<00:15:21.420> infrastructure<00:15:22.019> kit<00:15:22.380> that<00:15:22.860> node 00:15:23.030 --> 00:15:23.040 align:start position:0% open source infrastructure kit that node 00:15:23.040 --> 00:15:24.889 align:start position:0% open source infrastructure kit that node providers<00:15:23.639> can<00:15:23.940> use<00:15:24.180> to<00:15:24.660> help<00:15:24.720> them 00:15:24.889 --> 00:15:24.899 align:start position:0% providers can use to help them 00:15:24.899 --> 00:15:26.750 align:start position:0% providers can use to help them participate<00:15:25.320> in<00:15:25.500> this<00:15:25.680> network<00:15:25.860> of<00:15:26.639> course 00:15:26.750 --> 00:15:26.760 align:start position:0% participate in this network of course 00:15:26.760 --> 00:15:27.889 align:start position:0% participate in this network of course there's<00:15:26.880> also<00:15:27.180> going<00:15:27.240> to<00:15:27.300> be<00:15:27.360> parties<00:15:27.720> that 00:15:27.889 --> 00:15:27.899 align:start position:0% there's also going to be parties that 00:15:27.899 --> 00:15:29.090 align:start position:0% there's also going to be parties that already<00:15:28.019> know<00:15:28.260> what<00:15:28.380> they're<00:15:28.500> doing<00:15:28.680> and 00:15:29.090 --> 00:15:29.100 align:start position:0% already know what they're doing and 00:15:29.100 --> 00:15:30.829 align:start position:0% already know what they're doing and we'll<00:15:29.339> probably<00:15:29.519> just<00:15:29.699> run<00:15:29.940> their<00:15:30.180> own<00:15:30.420> flavor 00:15:30.829 --> 00:15:30.839 align:start position:0% we'll probably just run their own flavor 00:15:30.839 --> 00:15:32.629 align:start position:0% we'll probably just run their own flavor of<00:15:31.079> infrastructure<00:15:31.680> to<00:15:32.100> provide<00:15:32.339> the<00:15:32.519> same 00:15:32.629 --> 00:15:32.639 align:start position:0% of infrastructure to provide the same 00:15:32.639 --> 00:15:34.550 align:start position:0% of infrastructure to provide the same service<00:15:32.820> in<00:15:33.120> the<00:15:33.240> end 00:15:34.550 --> 00:15:34.560 align:start position:0% service in the end 00:15:34.560 --> 00:15:36.110 align:start position:0% service in the end uh<00:15:35.100> next<00:15:35.339> we<00:15:35.519> have<00:15:35.639> the<00:15:35.699> network<00:15:35.880> status 00:15:36.110 --> 00:15:36.120 align:start position:0% uh next we have the network status 00:15:36.120 --> 00:15:38.269 align:start position:0% uh next we have the network status Watchers<00:15:36.720> again<00:15:37.260> there's<00:15:37.560> multiple<00:15:37.920> of<00:15:38.100> these 00:15:38.269 --> 00:15:38.279 align:start position:0% Watchers again there's multiple of these 00:15:38.279 --> 00:15:40.310 align:start position:0% Watchers again there's multiple of these run<00:15:38.519> by<00:15:38.760> different<00:15:38.940> parties<00:15:39.360> these<00:15:40.199> will 00:15:40.310 --> 00:15:40.320 align:start position:0% run by different parties these will 00:15:40.320 --> 00:15:41.750 align:start position:0% run by different parties these will periodically<00:15:40.860> test<00:15:41.100> the<00:15:41.339> infrastructure 00:15:41.750 --> 00:15:41.760 align:start position:0% periodically test the infrastructure 00:15:41.760 --> 00:15:43.670 align:start position:0% periodically test the infrastructure providers<00:15:42.300> by<00:15:42.600> sending<00:15:42.959> them<00:15:43.079> a<00:15:43.260> small<00:15:43.440> volume 00:15:43.670 --> 00:15:43.680 align:start position:0% providers by sending them a small volume 00:15:43.680 --> 00:15:45.350 align:start position:0% providers by sending them a small volume of<00:15:43.920> requests<00:15:44.399> they'll<00:15:44.940> measure<00:15:45.240> the 00:15:45.350 --> 00:15:45.360 align:start position:0% of requests they'll measure the 00:15:45.360 --> 00:15:47.449 align:start position:0% of requests they'll measure the performance<00:15:45.839> and<00:15:46.199> check<00:15:46.380> for<00:15:46.560> correctness<00:15:47.040> of 00:15:47.449 --> 00:15:47.459 align:start position:0% performance and check for correctness of 00:15:47.459 --> 00:15:50.210 align:start position:0% performance and check for correctness of those<00:15:47.699> responses<00:15:48.360> they'll<00:15:49.320> report<00:15:49.560> all<00:15:49.980> this 00:15:50.210 --> 00:15:50.220 align:start position:0% those responses they'll report all this 00:15:50.220 --> 00:15:52.009 align:start position:0% those responses they'll report all this to<00:15:50.399> a<00:15:50.519> Federated<00:15:50.880> status<00:15:51.120> page<00:15:51.600> so<00:15:51.779> if<00:15:51.899> you're 00:15:52.009 --> 00:15:52.019 align:start position:0% to a Federated status page so if you're 00:15:52.019 --> 00:15:54.050 align:start position:0% to a Federated status page so if you're thinking<00:15:52.320> about<00:15:52.500> using<00:15:53.339> this<00:15:53.519> network<00:15:53.639> you'll 00:15:54.050 --> 00:15:54.060 align:start position:0% thinking about using this network you'll 00:15:54.060 --> 00:15:55.610 align:start position:0% thinking about using this network you'll be<00:15:54.180> able<00:15:54.300> to<00:15:54.360> go<00:15:54.540> there<00:15:54.779> look<00:15:55.260> through<00:15:55.500> the 00:15:55.610 --> 00:15:55.620 align:start position:0% be able to go there look through the 00:15:55.620 --> 00:15:57.350 align:start position:0% be able to go there look through the different<00:15:55.800> providers<00:15:56.399> see<00:15:56.880> how<00:15:57.060> they<00:15:57.240> perform 00:15:57.350 --> 00:15:57.360 align:start position:0% different providers see how they perform 00:15:57.360 --> 00:15:59.750 align:start position:0% different providers see how they perform what<00:15:57.899> their<00:15:58.079> you<00:15:58.199> know<00:15:58.380> capabilities<00:15:58.860> are<00:15:59.220> of 00:15:59.750 --> 00:15:59.760 align:start position:0% what their you know capabilities are of 00:15:59.760 --> 00:16:04.449 align:start position:0% what their you know capabilities are of those<00:16:00.060> things<00:16:00.320> and<00:16:01.320> also<00:16:01.560> in<00:16:01.740> cases<00:16:02.220> of 00:16:04.449 --> 00:16:04.459 align:start position:0% those things and also in cases of 00:16:04.459 --> 00:16:07.069 align:start position:0% those things and also in cases of provably<00:16:05.459> incorrect<00:16:06.000> responses<00:16:06.480> so<00:16:06.779> there 00:16:07.069 --> 00:16:07.079 align:start position:0% provably incorrect responses so there 00:16:07.079 --> 00:16:09.710 align:start position:0% provably incorrect responses so there are<00:16:07.260> certain<00:16:07.760> requests<00:16:08.760> on<00:16:09.120> the<00:16:09.300> ethereum 00:16:09.710 --> 00:16:09.720 align:start position:0% are certain requests on the ethereum 00:16:09.720 --> 00:16:11.810 align:start position:0% are certain requests on the ethereum Json<00:16:10.079> RPC<00:16:10.620> API<00:16:11.100> that<00:16:11.279> you<00:16:11.399> could<00:16:11.519> prove<00:16:11.699> with 00:16:11.810 --> 00:16:11.820 align:start position:0% Json RPC API that you could prove with 00:16:11.820 --> 00:16:14.030 align:start position:0% Json RPC API that you could prove with Merkle<00:16:12.240> proofs<00:16:12.540> rather<00:16:12.720> easily<00:16:13.139> so<00:16:13.800> in<00:16:13.920> those 00:16:14.030 --> 00:16:14.040 align:start position:0% Merkle proofs rather easily so in those 00:16:14.040 --> 00:16:15.949 align:start position:0% Merkle proofs rather easily so in those cases<00:16:14.279> those<00:16:14.519> might<00:16:14.760> also<00:16:15.000> be<00:16:15.180> used<00:16:15.360> to<00:16:15.660> inform 00:16:15.949 --> 00:16:15.959 align:start position:0% cases those might also be used to inform 00:16:15.959 --> 00:16:18.350 align:start position:0% cases those might also be used to inform penalties<00:16:16.560> to<00:16:17.160> the<00:16:17.339> node<00:16:17.519> providers<00:16:17.940> and<00:16:18.240> we 00:16:18.350 --> 00:16:18.360 align:start position:0% penalties to the node providers and we 00:16:18.360 --> 00:16:21.110 align:start position:0% penalties to the node providers and we hope<00:16:18.540> over<00:16:18.720> time<00:16:19.019> as<00:16:19.699> stateless<00:16:20.699> clients 00:16:21.110 --> 00:16:21.120 align:start position:0% hope over time as stateless clients 00:16:21.120 --> 00:16:22.910 align:start position:0% hope over time as stateless clients start<00:16:21.360> to<00:16:21.540> improve<00:16:22.019> that<00:16:22.260> there<00:16:22.380> will<00:16:22.560> be<00:16:22.680> more 00:16:22.910 --> 00:16:22.920 align:start position:0% start to improve that there will be more 00:16:22.920 --> 00:16:26.269 align:start position:0% start to improve that there will be more and<00:16:23.040> more<00:16:23.339> of<00:16:23.880> that<00:16:24.380> API<00:16:25.380> surface<00:16:25.800> that<00:16:26.160> is 00:16:26.269 --> 00:16:26.279 align:start position:0% and more of that API surface that is 00:16:26.279 --> 00:16:28.490 align:start position:0% and more of that API surface that is verifiable 00:16:28.490 --> 00:16:28.500 align:start position:0% verifiable 00:16:28.500 --> 00:16:30.290 align:start position:0% verifiable a<00:16:29.100> picture<00:16:29.339> of<00:16:29.579> kind<00:16:29.699> of<00:16:29.820> what<00:16:29.940> it<00:16:30.060> looks<00:16:30.240> like 00:16:30.290 --> 00:16:30.300 align:start position:0% a picture of kind of what it looks like 00:16:30.300 --> 00:16:32.329 align:start position:0% a picture of kind of what it looks like to<00:16:30.420> run<00:16:30.600> a<00:16:30.779> network<00:16:30.899> status<00:16:31.139> Watcher<00:16:31.680> they 00:16:32.329 --> 00:16:32.339 align:start position:0% to run a network status Watcher they 00:16:32.339 --> 00:16:34.129 align:start position:0% to run a network status Watcher they will<00:16:32.519> have<00:16:32.699> to<00:16:32.820> run<00:16:33.120> some<00:16:33.540> small<00:16:33.779> amount<00:16:33.899> of 00:16:34.129 --> 00:16:34.139 align:start position:0% will have to run some small amount of 00:16:34.139 --> 00:16:36.110 align:start position:0% will have to run some small amount of blockchain<00:16:34.500> infrastructure<00:16:34.980> themselves<00:16:35.519> not 00:16:36.110 --> 00:16:36.120 align:start position:0% blockchain infrastructure themselves not 00:16:36.120 --> 00:16:37.129 align:start position:0% blockchain infrastructure themselves not nearly<00:16:36.360> on<00:16:36.540> the<00:16:36.660> scale<00:16:36.779> that<00:16:36.959> an 00:16:37.129 --> 00:16:37.139 align:start position:0% nearly on the scale that an 00:16:37.139 --> 00:16:38.269 align:start position:0% nearly on the scale that an infrastructure<00:16:37.500> provider<00:16:37.980> would<00:16:38.100> because 00:16:38.269 --> 00:16:38.279 align:start position:0% infrastructure provider would because 00:16:38.279 --> 00:16:39.590 align:start position:0% infrastructure provider would because they're<00:16:38.459> not<00:16:38.579> serving<00:16:38.880> a<00:16:39.000> high<00:16:39.120> volume<00:16:39.300> of 00:16:39.590 --> 00:16:39.600 align:start position:0% they're not serving a high volume of 00:16:39.600 --> 00:16:41.569 align:start position:0% they're not serving a high volume of requests<00:16:40.440> but<00:16:40.860> they<00:16:40.980> need<00:16:41.160> sort<00:16:41.339> of<00:16:41.459> a 00:16:41.569 --> 00:16:41.579 align:start position:0% requests but they need sort of a 00:16:41.579 --> 00:16:43.069 align:start position:0% requests but they need sort of a baseline<00:16:42.000> to<00:16:42.120> compare<00:16:42.420> to<00:16:42.600> they<00:16:42.839> want<00:16:42.959> to 00:16:43.069 --> 00:16:43.079 align:start position:0% baseline to compare to they want to 00:16:43.079 --> 00:16:44.870 align:start position:0% baseline to compare to they want to check<00:16:43.259> that<00:16:43.440> the<00:16:43.680> infrastructure<00:16:44.220> providers 00:16:44.870 --> 00:16:44.880 align:start position:0% check that the infrastructure providers 00:16:44.880 --> 00:16:46.790 align:start position:0% check that the infrastructure providers are<00:16:45.480> near<00:16:45.660> what<00:16:46.019> they<00:16:46.139> think<00:16:46.259> is<00:16:46.380> the<00:16:46.560> head<00:16:46.620> of 00:16:46.790 --> 00:16:46.800 align:start position:0% are near what they think is the head of 00:16:46.800 --> 00:16:47.689 align:start position:0% are near what they think is the head of the<00:16:46.920> chain 00:16:47.689 --> 00:16:47.699 align:start position:0% the chain 00:16:47.699 --> 00:16:48.949 align:start position:0% the chain um<00:16:47.820> and<00:16:48.120> then<00:16:48.240> of<00:16:48.360> course<00:16:48.480> they'll<00:16:48.660> have<00:16:48.839> all 00:16:48.949 --> 00:16:48.959 align:start position:0% um and then of course they'll have all 00:16:48.959 --> 00:16:50.509 align:start position:0% um and then of course they'll have all these<00:16:49.199> periodic<00:16:49.680> tests<00:16:50.100> that<00:16:50.399> they're 00:16:50.509 --> 00:16:50.519 align:start position:0% these periodic tests that they're 00:16:50.519 --> 00:16:52.850 align:start position:0% these periodic tests that they're running<00:16:50.699> to<00:16:51.120> see<00:16:51.360> if<00:16:51.660> the<00:16:52.259> providers<00:16:52.680> are 00:16:52.850 --> 00:16:52.860 align:start position:0% running to see if the providers are 00:16:52.860 --> 00:16:54.650 align:start position:0% running to see if the providers are operating<00:16:53.279> well<00:16:53.519> so<00:16:54.060> they'll<00:16:54.240> interact<00:16:54.540> with 00:16:54.650 --> 00:16:54.660 align:start position:0% operating well so they'll interact with 00:16:54.660 --> 00:16:55.970 align:start position:0% operating well so they'll interact with the<00:16:54.779> infrastructure<00:16:55.139> providers<00:16:55.560> they'll 00:16:55.970 --> 00:16:55.980 align:start position:0% the infrastructure providers they'll 00:16:55.980 --> 00:16:58.249 align:start position:0% the infrastructure providers they'll potentially<00:16:56.279> send<00:16:56.639> things<00:16:56.940> to<00:16:57.420> a<00:16:58.019> Smart 00:16:58.249 --> 00:16:58.259 align:start position:0% potentially send things to a Smart 00:16:58.259 --> 00:17:00.350 align:start position:0% potentially send things to a Smart contract<00:16:58.620> on<00:16:58.920> chain<00:16:59.100> for<00:16:59.459> those<00:16:59.699> provably 00:17:00.350 --> 00:17:00.360 align:start position:0% contract on chain for those provably 00:17:00.360 --> 00:17:02.749 align:start position:0% contract on chain for those provably incorrect<00:17:01.019> responses<00:17:01.560> and<00:17:02.160> then<00:17:02.279> they<00:17:02.519> will 00:17:02.749 --> 00:17:02.759 align:start position:0% incorrect responses and then they will 00:17:02.759 --> 00:17:05.329 align:start position:0% incorrect responses and then they will also<00:17:03.180> send<00:17:03.600> their<00:17:04.380> results<00:17:04.559> to<00:17:04.860> a<00:17:04.980> Federated 00:17:05.329 --> 00:17:05.339 align:start position:0% also send their results to a Federated 00:17:05.339 --> 00:17:06.770 align:start position:0% also send their results to a Federated status<00:17:05.640> page<00:17:06.000> where<00:17:06.179> you<00:17:06.299> can<00:17:06.419> view<00:17:06.540> more 00:17:06.770 --> 00:17:06.780 align:start position:0% status page where you can view more 00:17:06.780 --> 00:17:09.110 align:start position:0% status page where you can view more detailed<00:17:07.140> information<00:17:07.579> and<00:17:08.579> then<00:17:08.760> last<00:17:08.939> we 00:17:09.110 --> 00:17:09.120 align:start position:0% detailed information and then last we 00:17:09.120 --> 00:17:10.970 align:start position:0% detailed information and then last we have<00:17:09.240> the<00:17:09.299> Ingress<00:17:09.600> node<00:17:10.020> so<00:17:10.260> as<00:17:10.559> I<00:17:10.740> mentioned 00:17:10.970 --> 00:17:10.980 align:start position:0% have the Ingress node so as I mentioned 00:17:10.980 --> 00:17:12.530 align:start position:0% have the Ingress node so as I mentioned this<00:17:11.280> kind<00:17:11.459> of<00:17:11.520> serves<00:17:11.819> as<00:17:11.880> an<00:17:12.059> intermediary 00:17:12.530 --> 00:17:12.540 align:start position:0% this kind of serves as an intermediary 00:17:12.540 --> 00:17:14.449 align:start position:0% this kind of serves as an intermediary between<00:17:12.839> the<00:17:13.140> end<00:17:13.319> user<00:17:13.679> and<00:17:14.280> the 00:17:14.449 --> 00:17:14.459 align:start position:0% between the end user and the 00:17:14.459 --> 00:17:16.250 align:start position:0% between the end user and the infrastructure<00:17:14.939> providers<00:17:15.419> so<00:17:15.660> an<00:17:15.780> end<00:17:15.900> user 00:17:16.250 --> 00:17:16.260 align:start position:0% infrastructure providers so an end user 00:17:16.260 --> 00:17:18.530 align:start position:0% infrastructure providers so an end user will<00:17:16.740> send<00:17:16.980> their<00:17:17.100> Json<00:17:17.339> RPC<00:17:17.819> request<00:17:18.120> to<00:17:18.360> an 00:17:18.530 --> 00:17:18.540 align:start position:0% will send their Json RPC request to an 00:17:18.540 --> 00:17:20.569 align:start position:0% will send their Json RPC request to an Ingress<00:17:18.900> node<00:17:19.260> and<00:17:19.559> then<00:17:19.679> that<00:17:19.799> Ingress<00:17:20.160> node 00:17:20.569 --> 00:17:20.579 align:start position:0% Ingress node and then that Ingress node 00:17:20.579 --> 00:17:22.490 align:start position:0% Ingress node and then that Ingress node May<00:17:20.880> then<00:17:21.120> forward<00:17:21.540> that<00:17:21.900> to<00:17:22.140> multiple 00:17:22.490 --> 00:17:22.500 align:start position:0% May then forward that to multiple 00:17:22.500 --> 00:17:24.289 align:start position:0% May then forward that to multiple different<00:17:22.679> infrastructure<00:17:23.280> providers<00:17:23.760> maybe 00:17:24.289 --> 00:17:24.299 align:start position:0% different infrastructure providers maybe 00:17:24.299 --> 00:17:25.970 align:start position:0% different infrastructure providers maybe they<00:17:24.660> generally<00:17:24.959> send<00:17:25.140> it<00:17:25.260> to<00:17:25.380> one<00:17:25.559> and<00:17:25.799> if 00:17:25.970 --> 00:17:25.980 align:start position:0% they generally send it to one and if 00:17:25.980 --> 00:17:27.230 align:start position:0% they generally send it to one and if that<00:17:26.160> goes<00:17:26.339> down<00:17:26.459> they<00:17:26.640> have<00:17:26.760> a<00:17:26.880> fallback 00:17:27.230 --> 00:17:27.240 align:start position:0% that goes down they have a fallback 00:17:27.240 --> 00:17:29.510 align:start position:0% that goes down they have a fallback maybe<00:17:27.780> they<00:17:27.959> round<00:17:28.079> robin<00:17:28.439> in<00:17:28.980> maybe<00:17:29.280> they 00:17:29.510 --> 00:17:29.520 align:start position:0% maybe they round robin in maybe they 00:17:29.520 --> 00:17:30.950 align:start position:0% maybe they round robin in maybe they choose<00:17:29.760> to<00:17:29.880> actually<00:17:30.059> send<00:17:30.360> it<00:17:30.540> to<00:17:30.660> all<00:17:30.900> of 00:17:30.950 --> 00:17:30.960 align:start position:0% choose to actually send it to all of 00:17:30.960 --> 00:17:32.450 align:start position:0% choose to actually send it to all of them<00:17:31.140> and<00:17:31.380> do<00:17:31.559> a<00:17:31.620> quorum<00:17:31.919> of<00:17:32.040> that<00:17:32.220> and<00:17:32.340> return 00:17:32.450 --> 00:17:32.460 align:start position:0% them and do a quorum of that and return 00:17:32.460 --> 00:17:34.250 align:start position:0% them and do a quorum of that and return it<00:17:32.700> to<00:17:32.820> the<00:17:32.940> user<00:17:33.179> this<00:17:33.780> will<00:17:33.900> be<00:17:34.020> something 00:17:34.250 --> 00:17:34.260 align:start position:0% it to the user this will be something 00:17:34.260 --> 00:17:36.590 align:start position:0% it to the user this will be something that<00:17:34.620> the<00:17:34.799> Ingress<00:17:35.179> node<00:17:36.179> can<00:17:36.419> actually 00:17:36.590 --> 00:17:36.600 align:start position:0% that the Ingress node can actually 00:17:36.600 --> 00:17:39.350 align:start position:0% that the Ingress node can actually choose<00:17:36.960> how<00:17:37.140> they<00:17:37.320> want<00:17:37.500> to<00:17:37.620> do<00:17:37.740> it<00:17:38.400> and<00:17:39.179> one 00:17:39.350 --> 00:17:39.360 align:start position:0% choose how they want to do it and one 00:17:39.360 --> 00:17:42.049 align:start position:0% choose how they want to do it and one reason<00:17:39.600> for<00:17:39.960> having<00:17:40.260> this<00:17:40.559> Ingress<00:17:40.860> node<00:17:41.340> is 00:17:42.049 --> 00:17:42.059 align:start position:0% reason for having this Ingress node is 00:17:42.059 --> 00:17:43.970 align:start position:0% reason for having this Ingress node is that<00:17:42.240> you<00:17:42.539> can<00:17:42.600> use<00:17:42.780> it<00:17:42.960> to<00:17:43.140> give<00:17:43.260> the<00:17:43.500> same<00:17:43.679> web 00:17:43.970 --> 00:17:43.980 align:start position:0% that you can use it to give the same web 00:17:43.980 --> 00:17:46.610 align:start position:0% that you can use it to give the same web to<00:17:44.280> ux<00:17:44.760> of<00:17:45.419> the<00:17:45.600> centralized<00:17:46.020> providers<00:17:46.380> today 00:17:46.610 --> 00:17:46.620 align:start position:0% to ux of the centralized providers today 00:17:46.620 --> 00:17:48.529 align:start position:0% to ux of the centralized providers today so<00:17:47.100> I<00:17:47.700> think<00:17:47.880> there's<00:17:48.000> a<00:17:48.179> reason<00:17:48.299> that 00:17:48.529 --> 00:17:48.539 align:start position:0% so I think there's a reason that 00:17:48.539 --> 00:17:50.090 align:start position:0% so I think there's a reason that inferior<00:17:49.080> and<00:17:49.200> centralized<00:17:49.559> providers<00:17:49.919> have 00:17:50.090 --> 00:17:50.100 align:start position:0% inferior and centralized providers have 00:17:50.100 --> 00:17:52.669 align:start position:0% inferior and centralized providers have been<00:17:50.220> so<00:17:50.400> successful<00:17:50.760> it's<00:17:51.000> provided<00:17:51.600> a<00:17:52.440> an 00:17:52.669 --> 00:17:52.679 align:start position:0% been so successful it's provided a an 00:17:52.679 --> 00:17:54.710 align:start position:0% been so successful it's provided a an easy<00:17:52.860> entry<00:17:53.280> point<00:17:53.400> for<00:17:53.640> people<00:17:53.820> to<00:17:54.059> come<00:17:54.179> and 00:17:54.710 --> 00:17:54.720 align:start position:0% easy entry point for people to come and 00:17:54.720 --> 00:17:56.330 align:start position:0% easy entry point for people to come and swipe<00:17:55.080> their<00:17:55.200> credit<00:17:55.380> card<00:17:55.620> and<00:17:55.980> get<00:17:56.160> access 00:17:56.330 --> 00:17:56.340 align:start position:0% swipe their credit card and get access 00:17:56.340 --> 00:17:57.710 align:start position:0% swipe their credit card and get access to<00:17:56.580> the<00:17:56.760> network<00:17:56.880> and<00:17:57.299> that<00:17:57.539> doesn't 00:17:57.710 --> 00:17:57.720 align:start position:0% to the network and that doesn't 00:17:57.720 --> 00:17:59.090 align:start position:0% to the network and that doesn't necessarily<00:17:58.200> align<00:17:58.440> with<00:17:58.620> a<00:17:58.740> decentralized 00:17:59.090 --> 00:17:59.100 align:start position:0% necessarily align with a decentralized 00:17:59.100 --> 00:18:01.549 align:start position:0% necessarily align with a decentralized ethos<00:17:59.520> but<00:17:59.700> it's<00:17:59.880> also<00:18:00.240> brought<00:18:00.720> a<00:18:01.320> lot<00:18:01.440> more 00:18:01.549 --> 00:18:01.559 align:start position:0% ethos but it's also brought a lot more 00:18:01.559 --> 00:18:05.029 align:start position:0% ethos but it's also brought a lot more people<00:18:01.860> to<00:18:02.400> our<00:18:03.000> our<00:18:03.240> world<00:18:03.539> and<00:18:04.380> so<00:18:04.620> an 00:18:05.029 --> 00:18:05.039 align:start position:0% people to our our world and so an 00:18:05.039 --> 00:18:06.650 align:start position:0% people to our our world and so an Ingress<00:18:05.340> node<00:18:05.700> might<00:18:05.880> allow<00:18:06.120> users<00:18:06.480> to 00:18:06.650 --> 00:18:06.660 align:start position:0% Ingress node might allow users to 00:18:06.660 --> 00:18:08.450 align:start position:0% Ingress node might allow users to actually<00:18:06.780> pay<00:18:07.020> them<00:18:07.260> in<00:18:07.440> Fiat<00:18:07.799> and<00:18:08.220> then<00:18:08.340> give 00:18:08.450 --> 00:18:08.460 align:start position:0% actually pay them in Fiat and then give 00:18:08.460 --> 00:18:10.789 align:start position:0% actually pay them in Fiat and then give them<00:18:08.640> API<00:18:09.059> access<00:18:09.299> but<00:18:09.960> this<00:18:10.140> will<00:18:10.260> still<00:18:10.440> have 00:18:10.789 --> 00:18:10.799 align:start position:0% them API access but this will still have 00:18:10.799 --> 00:18:12.710 align:start position:0% them API access but this will still have better<00:18:11.280> results<00:18:11.760> than<00:18:12.179> the<00:18:12.360> current<00:18:12.480> model 00:18:12.710 --> 00:18:12.720 align:start position:0% better results than the current model 00:18:12.720 --> 00:18:14.330 align:start position:0% better results than the current model because<00:18:13.020> they<00:18:13.320> can<00:18:13.380> then<00:18:13.559> be<00:18:13.740> sending<00:18:14.100> the 00:18:14.330 --> 00:18:14.340 align:start position:0% because they can then be sending the 00:18:14.340 --> 00:18:15.650 align:start position:0% because they can then be sending the traffic<00:18:14.520> to<00:18:14.880> multiple<00:18:15.179> infrastructure 00:18:15.650 --> 00:18:15.660 align:start position:0% traffic to multiple infrastructure 00:18:15.660 --> 00:18:18.289 align:start position:0% traffic to multiple infrastructure providers<00:18:16.200> and<00:18:16.620> get<00:18:16.740> some<00:18:16.919> of<00:18:17.039> those<00:18:17.160> benefits 00:18:18.289 --> 00:18:18.299 align:start position:0% providers and get some of those benefits 00:18:18.299 --> 00:18:20.750 align:start position:0% providers and get some of those benefits uh<00:18:18.840> in<00:18:19.020> addition<00:18:19.260> to<00:18:19.500> that<00:18:19.679> though<00:18:19.980> an<00:18:20.400> Ingress 00:18:20.750 --> 00:18:20.760 align:start position:0% uh in addition to that though an Ingress 00:18:20.760 --> 00:18:23.090 align:start position:0% uh in addition to that though an Ingress node<00:18:21.120> might<00:18:21.360> purchase<00:18:21.900> resources<00:18:22.799> from 00:18:23.090 --> 00:18:23.100 align:start position:0% node might purchase resources from 00:18:23.100 --> 00:18:25.130 align:start position:0% node might purchase resources from several<00:18:23.340> node<00:18:23.580> providers<00:18:24.059> and<00:18:24.539> then<00:18:24.660> register 00:18:25.130 --> 00:18:25.140 align:start position:0% several node providers and then register 00:18:25.140 --> 00:18:27.650 align:start position:0% several node providers and then register themselves<00:18:25.860> as<00:18:26.160> a<00:18:26.280> node<00:18:26.460> provider<00:18:26.940> uh<00:18:27.480> with 00:18:27.650 --> 00:18:27.660 align:start position:0% themselves as a node provider uh with 00:18:27.660 --> 00:18:28.970 align:start position:0% themselves as a node provider uh with the<00:18:27.780> sort<00:18:27.960> of<00:18:28.080> the<00:18:28.200> you<00:18:28.380> know<00:18:28.440> the<00:18:28.559> sum<00:18:28.740> of<00:18:28.860> all 00:18:28.970 --> 00:18:28.980 align:start position:0% the sort of the you know the sum of all 00:18:28.980 --> 00:18:31.010 align:start position:0% the sort of the you know the sum of all of<00:18:29.160> that<00:18:29.280> capacity<00:18:29.700> and<00:18:30.299> then<00:18:30.419> an<00:18:30.539> end<00:18:30.660> user 00:18:31.010 --> 00:18:31.020 align:start position:0% of that capacity and then an end user 00:18:31.020 --> 00:18:33.350 align:start position:0% of that capacity and then an end user can<00:18:31.200> go<00:18:31.440> and<00:18:32.039> pay<00:18:32.280> for<00:18:32.520> that<00:18:32.700> provider<00:18:33.120> in 00:18:33.350 --> 00:18:33.360 align:start position:0% can go and pay for that provider in 00:18:33.360 --> 00:18:34.669 align:start position:0% can go and pay for that provider in crypto 00:18:34.669 --> 00:18:34.679 align:start position:0% crypto 00:18:34.679 --> 00:18:35.810 align:start position:0% crypto um and<00:18:34.860> then<00:18:34.980> you<00:18:35.100> have<00:18:35.220> a<00:18:35.340> fully<00:18:35.580> crypto 00:18:35.810 --> 00:18:35.820 align:start position:0% um and then you have a fully crypto 00:18:35.820 --> 00:18:37.549 align:start position:0% um and then you have a fully crypto native<00:18:36.120> experience<00:18:36.600> so<00:18:36.960> there's<00:18:37.260> options 00:18:37.549 --> 00:18:37.559 align:start position:0% native experience so there's options 00:18:37.559 --> 00:18:39.169 align:start position:0% native experience so there's options here<00:18:37.799> the<00:18:37.980> node<00:18:38.100> provider<00:18:38.520> lets<00:18:38.760> you<00:18:38.820> do<00:18:38.940> a<00:18:39.059> lot 00:18:39.169 --> 00:18:39.179 align:start position:0% here the node provider lets you do a lot 00:18:39.179 --> 00:18:41.690 align:start position:0% here the node provider lets you do a lot of<00:18:39.360> interesting<00:18:40.080> things<00:18:40.440> with<00:18:40.919> uh<00:18:41.160> combining 00:18:41.690 --> 00:18:41.700 align:start position:0% of interesting things with uh combining 00:18:41.700 --> 00:18:44.510 align:start position:0% of interesting things with uh combining other<00:18:42.000> providers<00:18:42.600> so<00:18:43.500> the<00:18:43.679> on<00:18:43.799> chain<00:18:44.039> registry 00:18:44.510 --> 00:18:44.520 align:start position:0% other providers so the on chain registry 00:18:44.520 --> 00:18:46.070 align:start position:0% other providers so the on chain registry is<00:18:44.820> what<00:18:45.000> we're<00:18:45.120> typically<00:18:45.480> calling<00:18:45.840> our 00:18:46.070 --> 00:18:46.080 align:start position:0% is what we're typically calling our 00:18:46.080 --> 00:18:47.990 align:start position:0% is what we're typically calling our smart<00:18:46.260> contract<00:18:46.740> that<00:18:47.220> kind<00:18:47.400> of<00:18:47.460> coordinates 00:18:47.990 --> 00:18:48.000 align:start position:0% smart contract that kind of coordinates 00:18:48.000 --> 00:18:49.789 align:start position:0% smart contract that kind of coordinates all<00:18:48.179> of<00:18:48.360> this<00:18:48.480> and<00:18:49.140> the<00:18:49.320> main<00:18:49.380> way<00:18:49.559> to<00:18:49.679> think 00:18:49.789 --> 00:18:49.799 align:start position:0% all of this and the main way to think 00:18:49.799 --> 00:18:51.650 align:start position:0% all of this and the main way to think about<00:18:49.919> it<00:18:50.100> is<00:18:50.280> it's<00:18:50.520> basically<00:18:50.880> the<00:18:51.360> data 00:18:51.650 --> 00:18:51.660 align:start position:0% about it is it's basically the data 00:18:51.660 --> 00:18:54.529 align:start position:0% about it is it's basically the data structure<00:18:52.020> of<00:18:52.440> your<00:18:52.679> node<00:18:52.980> providers<00:18:53.640> so<00:18:54.419> we 00:18:54.529 --> 00:18:54.539 align:start position:0% structure of your node providers so we 00:18:54.539 --> 00:18:57.049 align:start position:0% structure of your node providers so we have<00:18:54.720> a<00:18:55.020> very<00:18:55.140> simple<00:18:55.500> example<00:18:56.460> of<00:18:56.640> what<00:18:56.880> that 00:18:57.049 --> 00:18:57.059 align:start position:0% have a very simple example of what that 00:18:57.059 --> 00:18:59.330 align:start position:0% have a very simple example of what that kind<00:18:57.240> of<00:18:57.360> looks<00:18:57.600> like<00:18:57.720> this<00:18:58.020> is<00:18:58.260> uh<00:18:58.860> just<00:18:59.160> one 00:18:59.330 --> 00:18:59.340 align:start position:0% kind of looks like this is uh just one 00:18:59.340 --> 00:19:01.130 align:start position:0% kind of looks like this is uh just one detail<00:18:59.640> but<00:18:59.880> you<00:19:00.059> have<00:19:00.240> your<00:19:00.360> name<00:19:00.539> providers 00:19:01.130 --> 00:19:01.140 align:start position:0% detail but you have your name providers 00:19:01.140 --> 00:19:02.690 align:start position:0% detail but you have your name providers and<00:19:01.860> the<00:19:02.039> protocols<00:19:02.460> that<00:19:02.580> they're 00:19:02.690 --> 00:19:02.700 align:start position:0% and the protocols that they're 00:19:02.700 --> 00:19:04.789 align:start position:0% and the protocols that they're supporting<00:19:03.120> so<00:19:03.419> uh<00:19:03.720> as<00:19:03.900> inferior<00:19:04.440> maybe<00:19:04.559> we're 00:19:04.789 --> 00:19:04.799 align:start position:0% supporting so uh as inferior maybe we're 00:19:04.799 --> 00:19:07.029 align:start position:0% supporting so uh as inferior maybe we're supporting<00:19:05.280> the<00:19:05.880> five<00:19:06.000> that<00:19:06.240> are<00:19:06.360> listed<00:19:06.720> here 00:19:07.029 --> 00:19:07.039 align:start position:0% supporting the five that are listed here 00:19:07.039 --> 00:19:09.590 align:start position:0% supporting the five that are listed here but<00:19:08.039> maybe<00:19:08.160> operator<00:19:08.640> a<00:19:08.880> is<00:19:09.059> only<00:19:09.240> supporting 00:19:09.590 --> 00:19:09.600 align:start position:0% but maybe operator a is only supporting 00:19:09.600 --> 00:19:11.690 align:start position:0% but maybe operator a is only supporting Ethan<00:19:09.960> polygon<00:19:10.440> this<00:19:11.039> is<00:19:11.220> where<00:19:11.400> you<00:19:11.580> would 00:19:11.690 --> 00:19:11.700 align:start position:0% Ethan polygon this is where you would 00:19:11.700 --> 00:19:13.370 align:start position:0% Ethan polygon this is where you would also<00:19:11.880> be<00:19:12.000> able<00:19:12.240> to<00:19:12.299> see<00:19:12.660> things<00:19:13.020> like<00:19:13.200> maybe 00:19:13.370 --> 00:19:13.380 align:start position:0% also be able to see things like maybe 00:19:13.380 --> 00:19:15.950 align:start position:0% also be able to see things like maybe what<00:19:13.679> region<00:19:14.100> they<00:19:14.280> exist<00:19:14.640> in 00:19:15.950 --> 00:19:15.960 align:start position:0% what region they exist in 00:19:15.960 --> 00:19:17.750 align:start position:0% what region they exist in um whether<00:19:16.620> they<00:19:16.799> support<00:19:16.980> archive<00:19:17.400> nodes 00:19:17.750 --> 00:19:17.760 align:start position:0% um whether they support archive nodes 00:19:17.760 --> 00:19:19.669 align:start position:0% um whether they support archive nodes things<00:19:18.059> like<00:19:18.179> that 00:19:19.669 --> 00:19:19.679 align:start position:0% things like that 00:19:19.679 --> 00:19:22.130 align:start position:0% things like that uh<00:19:20.280> gonna<00:19:20.520> look<00:19:20.820> sort<00:19:21.000> of<00:19:21.120> of<00:19:21.360> the<00:19:21.600> timeline<00:19:21.960> of 00:19:22.130 --> 00:19:22.140 align:start position:0% uh gonna look sort of of the timeline of 00:19:22.140 --> 00:19:23.690 align:start position:0% uh gonna look sort of of the timeline of how<00:19:22.260> this<00:19:22.440> all<00:19:22.559> operates<00:19:22.919> so<00:19:23.100> first<00:19:23.340> of<00:19:23.580> course 00:19:23.690 --> 00:19:23.700 align:start position:0% how this all operates so first of course 00:19:23.700 --> 00:19:26.390 align:start position:0% how this all operates so first of course the<00:19:24.059> smart<00:19:24.179> contract<00:19:24.600> is<00:19:24.840> deployed<00:19:25.740> uh<00:19:26.220> some 00:19:26.390 --> 00:19:26.400 align:start position:0% the smart contract is deployed uh some 00:19:26.400 --> 00:19:28.070 align:start position:0% the smart contract is deployed uh some amount<00:19:26.580> of<00:19:26.820> time<00:19:27.000> later<00:19:27.299> your<00:19:27.660> infrastructure 00:19:28.070 --> 00:19:28.080 align:start position:0% amount of time later your infrastructure 00:19:28.080 --> 00:19:30.650 align:start position:0% amount of time later your infrastructure providers<00:19:28.620> come<00:19:28.919> in<00:19:29.039> and<00:19:29.700> they<00:19:29.940> register<00:19:30.240> they 00:19:30.650 --> 00:19:30.660 align:start position:0% providers come in and they register they 00:19:30.660 --> 00:19:32.510 align:start position:0% providers come in and they register they specify<00:19:31.020> the<00:19:31.200> protocols<00:19:31.860> the<00:19:32.100> capabilities 00:19:32.510 --> 00:19:32.520 align:start position:0% specify the protocols the capabilities 00:19:32.520 --> 00:19:35.210 align:start position:0% specify the protocols the capabilities and<00:19:32.820> the<00:19:32.940> throughput<00:19:33.240> that<00:19:33.419> they'll<00:19:33.600> support 00:19:35.210 --> 00:19:35.220 align:start position:0% and the throughput that they'll support 00:19:35.220 --> 00:19:37.250 align:start position:0% and the throughput that they'll support uh<00:19:35.820> some<00:19:36.000> amount<00:19:36.240> of<00:19:36.480> time<00:19:36.600> later<00:19:36.780> you'll<00:19:37.140> have 00:19:37.250 --> 00:19:37.260 align:start position:0% uh some amount of time later you'll have 00:19:37.260 --> 00:19:40.010 align:start position:0% uh some amount of time later you'll have Network<00:19:37.440> watches<00:19:37.980> that<00:19:38.160> will<00:19:38.340> register<00:19:39.020> they 00:19:40.010 --> 00:19:40.020 align:start position:0% Network watches that will register they 00:19:40.020 --> 00:19:42.049 align:start position:0% Network watches that will register they may<00:19:40.260> only<00:19:40.500> want<00:19:40.799> to<00:19:41.039> participate<00:19:41.580> watching 00:19:42.049 --> 00:19:42.059 align:start position:0% may only want to participate watching 00:19:42.059 --> 00:19:44.570 align:start position:0% may only want to participate watching for<00:19:42.299> certain<00:19:42.539> protocols<00:19:43.220> maybe<00:19:44.220> they're<00:19:44.460> only 00:19:44.570 --> 00:19:44.580 align:start position:0% for certain protocols maybe they're only 00:19:44.580 --> 00:19:46.370 align:start position:0% for certain protocols maybe they're only capable<00:19:44.940> of<00:19:45.179> checking<00:19:45.660> certain<00:19:45.900> capabilities 00:19:46.370 --> 00:19:46.380 align:start position:0% capable of checking certain capabilities 00:19:46.380 --> 00:19:47.750 align:start position:0% capable of checking certain capabilities maybe<00:19:46.740> you<00:19:46.919> have<00:19:47.039> a<00:19:47.100> watcher<00:19:47.400> that<00:19:47.580> can't 00:19:47.750 --> 00:19:47.760 align:start position:0% maybe you have a watcher that can't 00:19:47.760 --> 00:19:49.490 align:start position:0% maybe you have a watcher that can't check<00:19:48.000> that<00:19:48.240> a<00:19:48.480> node<00:19:48.720> or<00:19:49.140> that<00:19:49.380> an 00:19:49.490 --> 00:19:49.500 align:start position:0% check that a node or that an 00:19:49.500 --> 00:19:50.990 align:start position:0% check that a node or that an infrastructure<00:19:49.919> provider<00:19:50.520> can<00:19:50.760> support 00:19:50.990 --> 00:19:51.000 align:start position:0% infrastructure provider can support 00:19:51.000 --> 00:19:53.390 align:start position:0% infrastructure provider can support archive<00:19:51.539> access<00:19:51.720> but<00:19:52.140> they<00:19:52.320> want<00:19:52.500> to<00:19:52.740> help 00:19:53.390 --> 00:19:53.400 align:start position:0% archive access but they want to help 00:19:53.400 --> 00:19:55.549 align:start position:0% archive access but they want to help with<00:19:53.580> you<00:19:53.880> know<00:19:54.000> the<00:19:54.240> the<00:19:54.419> near<00:19:54.660> head<00:19:54.960> requests 00:19:55.549 --> 00:19:55.559 align:start position:0% with you know the the near head requests 00:19:55.559 --> 00:19:56.510 align:start position:0% with you know the the near head requests and<00:19:55.679> see<00:19:55.799> that<00:19:55.980> those<00:19:56.100> are<00:19:56.280> good<00:19:56.340> for 00:19:56.510 --> 00:19:56.520 align:start position:0% and see that those are good for 00:19:56.520 --> 00:19:57.650 align:start position:0% and see that those are good for providers 00:19:57.650 --> 00:19:57.660 align:start position:0% providers 00:19:57.660 --> 00:19:59.810 align:start position:0% providers and<00:19:58.320> then<00:19:58.440> finally<00:19:58.740> you<00:19:59.100> have<00:19:59.220> your<00:19:59.400> consumers 00:19:59.810 --> 00:19:59.820 align:start position:0% and then finally you have your consumers 00:19:59.820 --> 00:20:01.669 align:start position:0% and then finally you have your consumers who<00:20:00.000> come<00:20:00.179> in<00:20:00.299> and<00:20:00.419> purchase<00:20:00.720> throughput<00:20:01.080> so 00:20:01.669 --> 00:20:01.679 align:start position:0% who come in and purchase throughput so 00:20:01.679 --> 00:20:02.990 align:start position:0% who come in and purchase throughput so that<00:20:01.799> might<00:20:01.980> be<00:20:02.039> an<00:20:02.100> end<00:20:02.220> user<00:20:02.580> who<00:20:02.700> wants<00:20:02.940> to 00:20:02.990 --> 00:20:03.000 align:start position:0% that might be an end user who wants to 00:20:03.000 --> 00:20:04.850 align:start position:0% that might be an end user who wants to go<00:20:03.120> directly<00:20:03.360> to<00:20:03.539> a<00:20:03.660> node<00:20:03.780> provider<00:20:04.320> or<00:20:04.740> it 00:20:04.850 --> 00:20:04.860 align:start position:0% go directly to a node provider or it 00:20:04.860 --> 00:20:06.169 align:start position:0% go directly to a node provider or it could<00:20:04.980> be<00:20:05.100> an<00:20:05.160> Ingress<00:20:05.400> node<00:20:05.700> that<00:20:05.880> wants<00:20:06.120> to 00:20:06.169 --> 00:20:06.179 align:start position:0% could be an Ingress node that wants to 00:20:06.179 --> 00:20:08.390 align:start position:0% could be an Ingress node that wants to combine<00:20:06.539> them 00:20:08.390 --> 00:20:08.400 align:start position:0% combine them 00:20:08.400 --> 00:20:09.830 align:start position:0% combine them and<00:20:08.880> once<00:20:09.179> you<00:20:09.240> put<00:20:09.360> all<00:20:09.480> of<00:20:09.600> that<00:20:09.660> together 00:20:09.830 --> 00:20:09.840 align:start position:0% and once you put all of that together 00:20:09.840 --> 00:20:11.870 align:start position:0% and once you put all of that together you<00:20:10.320> get<00:20:10.440> sort<00:20:10.740> of<00:20:10.860> what<00:20:11.280> we<00:20:11.400> view<00:20:11.580> as<00:20:11.700> our 00:20:11.870 --> 00:20:11.880 align:start position:0% you get sort of what we view as our 00:20:11.880 --> 00:20:14.390 align:start position:0% you get sort of what we view as our decentralized<00:20:12.360> architecture<00:20:13.080> uh<00:20:13.919> so<00:20:14.100> in<00:20:14.220> the 00:20:14.390 --> 00:20:14.400 align:start position:0% decentralized architecture uh so in the 00:20:14.400 --> 00:20:15.770 align:start position:0% decentralized architecture uh so in the center<00:20:14.460> you<00:20:14.700> have<00:20:14.820> the<00:20:14.940> on-chain<00:20:15.299> registry 00:20:15.770 --> 00:20:15.780 align:start position:0% center you have the on-chain registry 00:20:15.780 --> 00:20:17.810 align:start position:0% center you have the on-chain registry you<00:20:16.380> have<00:20:16.559> your<00:20:16.679> network<00:20:16.799> Watchers<00:20:17.460> your 00:20:17.810 --> 00:20:17.820 align:start position:0% you have your network Watchers your 00:20:17.820 --> 00:20:19.909 align:start position:0% you have your network Watchers your infrastructure<00:20:18.360> providers<00:20:18.900> your<00:20:19.440> blockchain 00:20:19.909 --> 00:20:19.919 align:start position:0% infrastructure providers your blockchain 00:20:19.919 --> 00:20:22.430 align:start position:0% infrastructure providers your blockchain API<00:20:20.520> consumers<00:20:21.120> and<00:20:21.539> your<00:20:21.720> Ingress<00:20:22.020> nodes 00:20:22.430 --> 00:20:22.440 align:start position:0% API consumers and your Ingress nodes 00:20:22.440 --> 00:20:24.350 align:start position:0% API consumers and your Ingress nodes that<00:20:23.100> all<00:20:23.280> will<00:20:23.520> register<00:20:23.820> with<00:20:24.059> that<00:20:24.179> on 00:20:24.350 --> 00:20:24.360 align:start position:0% that all will register with that on 00:20:24.360 --> 00:20:26.270 align:start position:0% that all will register with that on chain<00:20:24.539> registry<00:20:25.080> and<00:20:25.559> then<00:20:25.740> once<00:20:25.980> that's<00:20:26.100> all 00:20:26.270 --> 00:20:26.280 align:start position:0% chain registry and then once that's all 00:20:26.280 --> 00:20:28.250 align:start position:0% chain registry and then once that's all set<00:20:26.460> up<00:20:26.580> your<00:20:26.820> blockchain<00:20:27.120> API<00:20:27.600> consumers<00:20:28.020> can 00:20:28.250 --> 00:20:28.260 align:start position:0% set up your blockchain API consumers can 00:20:28.260 --> 00:20:30.110 align:start position:0% set up your blockchain API consumers can send<00:20:28.440> their<00:20:28.620> requests<00:20:29.100> to<00:20:29.520> the<00:20:29.760> various 00:20:30.110 --> 00:20:30.120 align:start position:0% send their requests to the various 00:20:30.120 --> 00:20:32.029 align:start position:0% send their requests to the various infrastructure<00:20:30.600> providers<00:20:31.200> that<00:20:31.860> they've 00:20:32.029 --> 00:20:32.039 align:start position:0% infrastructure providers that they've 00:20:32.039 --> 00:20:34.310 align:start position:0% infrastructure providers that they've chosen<00:20:32.520> or<00:20:33.000> to<00:20:33.120> an<00:20:33.299> Ingress<00:20:33.660> node<00:20:33.960> which<00:20:34.200> is 00:20:34.310 --> 00:20:34.320 align:start position:0% chosen or to an Ingress node which is 00:20:34.320 --> 00:20:37.370 align:start position:0% chosen or to an Ingress node which is sort<00:20:34.500> of<00:20:34.620> helping<00:20:34.919> them<00:20:35.100> do<00:20:35.280> that<00:20:35.940> and<00:20:36.600> yeah<00:20:36.900> uh 00:20:37.370 --> 00:20:37.380 align:start position:0% sort of helping them do that and yeah uh 00:20:37.380 --> 00:20:38.990 align:start position:0% sort of helping them do that and yeah uh we<00:20:37.559> hope<00:20:37.740> once<00:20:38.220> we<00:20:38.280> have<00:20:38.400> that<00:20:38.520> all<00:20:38.640> figured 00:20:38.990 --> 00:20:39.000 align:start position:0% we hope once we have that all figured 00:20:39.000 --> 00:20:41.270 align:start position:0% we hope once we have that all figured out<00:20:39.120> that<00:20:39.600> it'll<00:20:40.200> give<00:20:40.380> us<00:20:40.500> a<00:20:40.620> self-sustaining 00:20:41.270 --> 00:20:41.280 align:start position:0% out that it'll give us a self-sustaining 00:20:41.280 --> 00:20:43.370 align:start position:0% out that it'll give us a self-sustaining reliable<00:20:41.820> and<00:20:42.120> robust<00:20:42.419> network<00:20:42.780> of 00:20:43.370 --> 00:20:43.380 align:start position:0% reliable and robust network of 00:20:43.380 --> 00:20:45.830 align:start position:0% reliable and robust network of infrastructure<00:20:43.980> providers<00:20:44.520> uh<00:20:45.299> that's<00:20:45.480> built 00:20:45.830 --> 00:20:45.840 align:start position:0% infrastructure providers uh that's built 00:20:45.840 --> 00:20:47.330 align:start position:0% infrastructure providers uh that's built to<00:20:45.960> really<00:20:46.140> serve<00:20:46.440> the<00:20:46.559> high<00:20:46.679> throughput<00:20:47.100> that 00:20:47.330 --> 00:20:47.340 align:start position:0% to really serve the high throughput that 00:20:47.340 --> 00:20:48.890 align:start position:0% to really serve the high throughput that inferior<00:20:47.700> can<00:20:47.940> today<00:20:48.120> or<00:20:48.360> other<00:20:48.480> centralized 00:20:48.890 --> 00:20:48.900 align:start position:0% inferior can today or other centralized 00:20:48.900 --> 00:20:51.289 align:start position:0% inferior can today or other centralized providers<00:20:49.320> can<00:20:49.500> today<00:20:49.740> uh<00:20:50.700> for<00:20:50.820> all<00:20:51.000> of<00:20:51.179> the 00:20:51.289 --> 00:20:51.299 align:start position:0% providers can today uh for all of the 00:20:51.299 --> 00:20:53.330 align:start position:0% providers can today uh for all of the blockchain<00:20:51.600> API<00:20:52.080> requests<00:20:52.620> that<00:20:52.980> you<00:20:53.160> you 00:20:53.330 --> 00:20:53.340 align:start position:0% blockchain API requests that you you 00:20:53.340 --> 00:20:54.470 align:start position:0% blockchain API requests that you you need 00:20:54.470 --> 00:20:54.480 align:start position:0% need 00:20:54.480 --> 00:20:56.570 align:start position:0% need um<00:20:54.600> but<00:20:54.840> instead<00:20:55.320> of<00:20:55.440> what<00:20:55.679> we<00:20:55.799> have<00:20:55.980> now<00:20:56.160> it'll 00:20:56.570 --> 00:20:56.580 align:start position:0% um but instead of what we have now it'll 00:20:56.580 --> 00:20:58.610 align:start position:0% um but instead of what we have now it'll remove<00:20:56.760> a<00:20:57.000> single<00:20:57.240> point<00:20:57.360> of<00:20:57.539> failure<00:20:57.900> uh<00:20:58.500> we 00:20:58.610 --> 00:20:58.620 align:start position:0% remove a single point of failure uh we 00:20:58.620 --> 00:21:00.230 align:start position:0% remove a single point of failure uh we help<00:20:58.860> to<00:20:59.100> hope<00:20:59.340> to<00:20:59.460> do<00:20:59.580> this<00:20:59.700> out<00:20:59.880> in<00:21:00.000> the<00:21:00.120> open 00:21:00.230 --> 00:21:00.240 align:start position:0% help to hope to do this out in the open 00:21:00.240 --> 00:21:01.789 align:start position:0% help to hope to do this out in the open as<00:21:00.480> much<00:21:00.600> as<00:21:00.840> possible<00:21:01.080> and<00:21:01.380> really<00:21:01.500> follow 00:21:01.789 --> 00:21:01.799 align:start position:0% as much as possible and really follow 00:21:01.799 --> 00:21:04.610 align:start position:0% as much as possible and really follow that<00:21:02.100> collaborative<00:21:02.580> web3<00:21:03.120> Spirit<00:21:03.419> uh<00:21:04.380> this 00:21:04.610 --> 00:21:04.620 align:start position:0% that collaborative web3 Spirit uh this 00:21:04.620 --> 00:21:06.409 align:start position:0% that collaborative web3 Spirit uh this is<00:21:04.740> we<00:21:05.039> hope<00:21:05.160> really<00:21:05.400> going<00:21:05.640> to<00:21:05.820> improve 00:21:06.409 --> 00:21:06.419 align:start position:0% is we hope really going to improve 00:21:06.419 --> 00:21:08.930 align:start position:0% is we hope really going to improve reliability<00:21:07.020> for<00:21:07.320> these<00:21:07.500> for<00:21:07.740> the<00:21:07.919> users<00:21:08.280> and 00:21:08.930 --> 00:21:08.940 align:start position:0% reliability for these for the users and 00:21:08.940 --> 00:21:10.549 align:start position:0% reliability for these for the users and get<00:21:09.179> a<00:21:09.299> lot<00:21:09.419> closer<00:21:09.780> to<00:21:09.960> that<00:21:10.200> kind<00:21:10.320> of<00:21:10.440> 100 00:21:10.549 --> 00:21:10.559 align:start position:0% get a lot closer to that kind of 100 00:21:10.559 --> 00:21:13.010 align:start position:0% get a lot closer to that kind of 100 uptime<00:21:11.460> dream 00:21:13.010 --> 00:21:13.020 align:start position:0% uptime dream 00:21:13.020 --> 00:21:15.169 align:start position:0% uptime dream um<00:21:13.080> but<00:21:13.620> also<00:21:13.980> which<00:21:14.400> I<00:21:14.580> think<00:21:14.700> is<00:21:14.820> important 00:21:15.169 --> 00:21:15.179 align:start position:0% um but also which I think is important 00:21:15.179 --> 00:21:17.450 align:start position:0% um but also which I think is important still<00:21:15.780> provide<00:21:16.140> the<00:21:16.320> ability<00:21:16.620> to<00:21:16.919> have<00:21:17.100> that 00:21:17.450 --> 00:21:17.460 align:start position:0% still provide the ability to have that 00:21:17.460 --> 00:21:19.850 align:start position:0% still provide the ability to have that really<00:21:17.640> easy<00:21:17.880> web<00:21:18.179> to<00:21:18.360> ux<00:21:18.720> if<00:21:18.960> you<00:21:19.080> want<00:21:19.200> it<00:21:19.380> uh 00:21:19.850 --> 00:21:19.860 align:start position:0% really easy web to ux if you want it uh 00:21:19.860 --> 00:21:22.190 align:start position:0% really easy web to ux if you want it uh we<00:21:20.039> could<00:21:20.160> also<00:21:20.340> have<00:21:20.400> the<00:21:20.520> crypto<00:21:20.760> native<00:21:21.539> uh 00:21:22.190 --> 00:21:22.200 align:start position:0% we could also have the crypto native uh 00:21:22.200 --> 00:21:24.110 align:start position:0% we could also have the crypto native uh and<00:21:22.380> yeah<00:21:22.500> that's<00:21:22.919> it<00:21:23.100> uh<00:21:23.460> we're<00:21:23.700> seeking 00:21:24.110 --> 00:21:24.120 align:start position:0% and yeah that's it uh we're seeking 00:21:24.120 --> 00:21:26.630 align:start position:0% and yeah that's it uh we're seeking strong<00:21:24.660> web<00:21:24.960> 3<00:21:25.200> infrastructure<00:21:25.860> providers<00:21:26.340> to 00:21:26.630 --> 00:21:26.640 align:start position:0% strong web 3 infrastructure providers to 00:21:26.640 --> 00:21:28.370 align:start position:0% strong web 3 infrastructure providers to work<00:21:26.760> together<00:21:27.059> with<00:21:27.419> us<00:21:27.600> if<00:21:28.200> you're 00:21:28.370 --> 00:21:28.380 align:start position:0% work together with us if you're 00:21:28.380 --> 00:21:29.930 align:start position:0% work together with us if you're interested<00:21:28.799> in<00:21:29.039> joining<00:21:29.340> and<00:21:29.520> participating 00:21:29.930 --> 00:21:29.940 align:start position:0% interested in joining and participating 00:21:29.940 --> 00:21:32.450 align:start position:0% interested in joining and participating in<00:21:30.179> this<00:21:30.299> network<00:21:30.480> I<00:21:30.840> encourage<00:21:31.140> you<00:21:31.320> to<00:21:31.740> snap 00:21:32.450 --> 00:21:32.460 align:start position:0% in this network I encourage you to snap 00:21:32.460 --> 00:21:34.190 align:start position:0% in this network I encourage you to snap this<00:21:32.700> QR<00:21:33.000> code<00:21:33.179> it<00:21:33.419> takes<00:21:33.539> you<00:21:33.659> to<00:21:33.780> a<00:21:33.900> form<00:21:34.080> that 00:21:34.190 --> 00:21:34.200 align:start position:0% this QR code it takes you to a form that 00:21:34.200 --> 00:21:35.330 align:start position:0% this QR code it takes you to a form that you<00:21:34.380> can<00:21:34.500> fill<00:21:34.620> out<00:21:34.740> provide<00:21:35.100> a<00:21:35.220> little 00:21:35.330 --> 00:21:35.340 align:start position:0% you can fill out provide a little 00:21:35.340 --> 00:21:37.250 align:start position:0% you can fill out provide a little information<00:21:35.580> on<00:21:36.179> your<00:21:36.299> experience<00:21:36.780> and<00:21:37.080> your 00:21:37.250 --> 00:21:37.260 align:start position:0% information on your experience and your 00:21:37.260 --> 00:21:40.250 align:start position:0% information on your experience and your interest<00:21:37.460> and<00:21:38.460> we'd<00:21:38.640> love<00:21:38.820> to<00:21:38.940> work<00:21:39.059> with<00:21:39.240> you 00:21:40.250 --> 00:21:40.260 align:start position:0% interest and we'd love to work with you 00:21:40.260 --> 00:21:41.870 align:start position:0% interest and we'd love to work with you um that's<00:21:40.500> it<00:21:40.679> I've<00:21:40.980> got<00:21:41.159> about<00:21:41.340> four<00:21:41.580> and<00:21:41.760> a 00:21:41.870 --> 00:21:41.880 align:start position:0% um that's it I've got about four and a 00:21:41.880 --> 00:21:43.250 align:start position:0% um that's it I've got about four and a half minutes<00:21:42.120> for<00:21:42.360> questions<00:21:42.539> if<00:21:42.840> anyone<00:21:43.080> has 00:21:43.250 --> 00:21:43.260 align:start position:0% half minutes for questions if anyone has 00:21:43.260 --> 00:21:45.470 align:start position:0% half minutes for questions if anyone has any 00:21:45.470 --> 00:21:45.480 align:start position:0% 00:21:45.480 --> 00:21:47.270 align:start position:0% thank<00:21:46.020> you<00:21:46.140> so<00:21:46.320> much 00:21:47.270 --> 00:21:47.280 align:start position:0% thank you so much 00:21:47.280 --> 00:21:49.190 align:start position:0% thank you so much um<00:21:47.400> please<00:21:47.880> raise<00:21:48.179> your<00:21:48.480> hand<00:21:48.720> if<00:21:48.900> you<00:21:49.080> have 00:21:49.190 --> 00:21:49.200 align:start position:0% um please raise your hand if you have 00:21:49.200 --> 00:21:51.110 align:start position:0% um please raise your hand if you have questions<00:21:49.380> so<00:21:49.679> our<00:21:49.919> volunteers<00:21:50.400> can<00:21:50.700> lend<00:21:51.000> you 00:21:51.110 --> 00:21:51.120 align:start position:0% questions so our volunteers can lend you 00:21:51.120 --> 00:21:52.970 align:start position:0% questions so our volunteers can lend you the<00:21:51.299> microphone 00:21:52.970 --> 00:21:52.980 align:start position:0% the microphone 00:21:52.980 --> 00:21:56.270 align:start position:0% the microphone one<00:21:53.580> two<00:21:53.820> yeah<00:21:54.120> so<00:21:54.780> do<00:21:55.020> you<00:21:55.200> plan<00:21:55.380> this<00:21:55.919> whole 00:21:56.270 --> 00:21:56.280 align:start position:0% one two yeah so do you plan this whole 00:21:56.280 --> 00:21:58.789 align:start position:0% one two yeah so do you plan this whole decentralization<00:21:56.880> to<00:21:57.299> be<00:21:57.480> more<00:21:57.659> creative<00:21:58.080> or 00:21:58.789 --> 00:21:58.799 align:start position:0% decentralization to be more creative or 00:21:58.799 --> 00:22:01.250 align:start position:0% decentralization to be more creative or censorship<00:21:59.400> resistant<00:22:00.419> sorry<00:22:00.780> what<00:22:01.020> was<00:22:01.140> the 00:22:01.250 --> 00:22:01.260 align:start position:0% censorship resistant sorry what was the 00:22:01.260 --> 00:22:03.230 align:start position:0% censorship resistant sorry what was the first<00:22:01.380> you<00:22:01.559> said<00:22:01.799> censorship<00:22:02.220> yes<00:22:02.820> so<00:22:03.059> either 00:22:03.230 --> 00:22:03.240 align:start position:0% first you said censorship yes so either 00:22:03.240 --> 00:22:05.210 align:start position:0% first you said censorship yes so either you<00:22:03.539> have<00:22:03.659> for<00:22:03.900> example<00:22:04.080> a<00:22:04.320> list<00:22:04.679> of<00:22:04.860> creative 00:22:05.210 --> 00:22:05.220 align:start position:0% you have for example a list of creative 00:22:05.220 --> 00:22:07.490 align:start position:0% you have for example a list of creative providers<00:22:05.820> for<00:22:06.120> quality<00:22:06.480> or<00:22:07.140> you<00:22:07.320> have<00:22:07.440> a 00:22:07.490 --> 00:22:07.500 align:start position:0% providers for quality or you have a 00:22:07.500 --> 00:22:09.169 align:start position:0% providers for quality or you have a censorship<00:22:07.919> persistently<00:22:08.460> so<00:22:08.700> providers 00:22:09.169 --> 00:22:09.179 align:start position:0% censorship persistently so providers 00:22:09.179 --> 00:22:11.289 align:start position:0% censorship persistently so providers that<00:22:09.480> will<00:22:09.600> treat<00:22:09.780> any<00:22:10.140> request<00:22:10.500> from<00:22:10.740> anyone 00:22:11.289 --> 00:22:11.299 align:start position:0% that will treat any request from anyone 00:22:11.299 --> 00:22:13.730 align:start position:0% that will treat any request from anyone regardless<00:22:12.299> of<00:22:12.539> definitely<00:22:13.200> improved 00:22:13.730 --> 00:22:13.740 align:start position:0% regardless of definitely improved 00:22:13.740 --> 00:22:16.190 align:start position:0% regardless of definitely improved censorship<00:22:14.360> censorship<00:22:15.360> resistance<00:22:15.960> because 00:22:16.190 --> 00:22:16.200 align:start position:0% censorship censorship resistance because 00:22:16.200 --> 00:22:17.630 align:start position:0% censorship censorship resistance because it's<00:22:16.440> permissionless<00:22:16.919> anybody<00:22:17.400> can 00:22:17.630 --> 00:22:17.640 align:start position:0% it's permissionless anybody can 00:22:17.640 --> 00:22:20.450 align:start position:0% it's permissionless anybody can participate<00:22:18.240> in<00:22:18.539> the<00:22:18.659> network<00:22:18.919> by<00:22:19.919> meeting 00:22:20.450 --> 00:22:20.460 align:start position:0% participate in the network by meeting 00:22:20.460 --> 00:22:22.190 align:start position:0% participate in the network by meeting the<00:22:20.760> criteria<00:22:21.120> to<00:22:21.299> join<00:22:21.539> the<00:22:21.659> network<00:22:21.840> which 00:22:22.190 --> 00:22:22.200 align:start position:0% the criteria to join the network which 00:22:22.200 --> 00:22:23.750 align:start position:0% the criteria to join the network which is<00:22:22.380> technical 00:22:23.750 --> 00:22:23.760 align:start position:0% is technical 00:22:23.760 --> 00:22:26.149 align:start position:0% is technical um technical<00:22:24.240> criteria<00:22:24.900> of<00:22:25.380> meeting<00:22:25.679> a<00:22:25.980> level 00:22:26.149 --> 00:22:26.159 align:start position:0% um technical criteria of meeting a level 00:22:26.159 --> 00:22:28.130 align:start position:0% um technical criteria of meeting a level of<00:22:26.400> performance<00:22:26.880> right<00:22:27.419> if<00:22:27.600> you<00:22:27.720> can<00:22:27.840> meet<00:22:27.960> a 00:22:28.130 --> 00:22:28.140 align:start position:0% of performance right if you can meet a 00:22:28.140 --> 00:22:29.570 align:start position:0% of performance right if you can meet a level<00:22:28.260> of<00:22:28.440> performance<00:22:28.799> you<00:22:29.039> can<00:22:29.159> participate 00:22:29.570 --> 00:22:29.580 align:start position:0% level of performance you can participate 00:22:29.580 --> 00:22:31.310 align:start position:0% level of performance you can participate in<00:22:29.760> the<00:22:29.880> network<00:22:30.059> we're<00:22:30.419> not<00:22:30.659> going<00:22:30.840> to<00:22:31.080> be 00:22:31.310 --> 00:22:31.320 align:start position:0% in the network we're not going to be 00:22:31.320 --> 00:22:34.190 align:start position:0% in the network we're not going to be selecting<00:22:32.220> who<00:22:32.640> can<00:22:32.820> participate<00:22:33.360> and<00:22:34.020> then 00:22:34.190 --> 00:22:34.200 align:start position:0% selecting who can participate and then 00:22:34.200 --> 00:22:36.710 align:start position:0% selecting who can participate and then as<00:22:34.440> a<00:22:34.500> consequence<00:22:34.980> what<00:22:35.640> if<00:22:35.820> a<00:22:36.120> provider 00:22:36.710 --> 00:22:36.720 align:start position:0% as a consequence what if a provider 00:22:36.720 --> 00:22:38.810 align:start position:0% as a consequence what if a provider constantly<00:22:37.380> perform<00:22:37.620> badly 00:22:38.810 --> 00:22:38.820 align:start position:0% constantly perform badly 00:22:38.820 --> 00:22:40.909 align:start position:0% constantly perform badly uh<00:22:39.539> they<00:22:39.840> would<00:22:39.900> be<00:22:40.020> penalized<00:22:40.559> by<00:22:40.740> the 00:22:40.909 --> 00:22:40.919 align:start position:0% uh they would be penalized by the 00:22:40.919 --> 00:22:42.830 align:start position:0% uh they would be penalized by the network<00:22:41.039> right<00:22:41.580> there's<00:22:41.940> there<00:22:42.360> would<00:22:42.539> be<00:22:42.659> a 00:22:42.830 --> 00:22:42.840 align:start position:0% network right there's there would be a 00:22:42.840 --> 00:22:44.390 align:start position:0% network right there's there would be a financial<00:22:43.080> incentive<00:22:43.740> to<00:22:43.980> provide<00:22:44.220> the 00:22:44.390 --> 00:22:44.400 align:start position:0% financial incentive to provide the 00:22:44.400 --> 00:22:47.570 align:start position:0% financial incentive to provide the minimum<00:22:44.700> level<00:22:44.940> of<00:22:45.299> performance<00:22:45.799> and<00:22:46.799> uh<00:22:47.280> they 00:22:47.570 --> 00:22:47.580 align:start position:0% minimum level of performance and uh they 00:22:47.580 --> 00:22:49.310 align:start position:0% minimum level of performance and uh they would<00:22:47.640> get<00:22:47.880> penalized<00:22:48.480> by<00:22:48.659> the<00:22:48.840> network<00:22:48.960> if 00:22:49.310 --> 00:22:49.320 align:start position:0% would get penalized by the network if 00:22:49.320 --> 00:22:50.450 align:start position:0% would get penalized by the network if they're<00:22:49.500> not<00:22:49.620> meeting<00:22:49.740> that<00:22:50.039> level<00:22:50.280> of 00:22:50.450 --> 00:22:50.460 align:start position:0% they're not meeting that level of 00:22:50.460 --> 00:22:52.610 align:start position:0% they're not meeting that level of performance<00:22:50.940> additionally<00:22:51.780> that<00:22:52.380> Network 00:22:52.610 --> 00:22:52.620 align:start position:0% performance additionally that Network 00:22:52.620 --> 00:22:55.370 align:start position:0% performance additionally that Network Watcher<00:22:53.220> that<00:22:53.580> or<00:22:54.120> in<00:22:54.419> status<00:22:54.659> monitor<00:22:55.260> that 00:22:55.370 --> 00:22:55.380 align:start position:0% Watcher that or in status monitor that 00:22:55.380 --> 00:22:57.590 align:start position:0% Watcher that or in status monitor that we're<00:22:55.559> talking<00:22:55.740> about<00:22:55.980> is<00:22:56.940> continuously 00:22:57.590 --> 00:22:57.600 align:start position:0% we're talking about is continuously 00:22:57.600 --> 00:22:59.510 align:start position:0% we're talking about is continuously checking<00:22:58.080> and<00:22:58.320> Reporting<00:22:58.740> on<00:22:59.100> both<00:22:59.280> the 00:22:59.510 --> 00:22:59.520 align:start position:0% checking and Reporting on both the 00:22:59.520 --> 00:23:01.490 align:start position:0% checking and Reporting on both the capabilities<00:23:00.000> of<00:23:00.299> the<00:23:00.480> network<00:23:00.659> as<00:23:01.260> well<00:23:01.380> as 00:23:01.490 --> 00:23:01.500 align:start position:0% capabilities of the network as well as 00:23:01.500 --> 00:23:04.190 align:start position:0% capabilities of the network as well as the<00:23:01.799> performance<00:23:02.220> so<00:23:02.760> you<00:23:03.000> can<00:23:03.120> see<00:23:03.360> here's<00:23:04.020> a 00:23:04.190 --> 00:23:04.200 align:start position:0% the performance so you can see here's a 00:23:04.200 --> 00:23:05.630 align:start position:0% the performance so you can see here's a new<00:23:04.260> provider<00:23:04.679> that<00:23:04.919> just<00:23:05.039> joined<00:23:05.400> they've 00:23:05.630 --> 00:23:05.640 align:start position:0% new provider that just joined they've 00:23:05.640 --> 00:23:07.190 align:start position:0% new provider that just joined they've only<00:23:05.760> been<00:23:05.940> part<00:23:06.120> of<00:23:06.240> the<00:23:06.360> network<00:23:06.539> for<00:23:06.960> seven 00:23:07.190 --> 00:23:07.200 align:start position:0% only been part of the network for seven 00:23:07.200 --> 00:23:10.010 align:start position:0% only been part of the network for seven days<00:23:07.440> they<00:23:08.159> support<00:23:08.340> seven<00:23:08.880> networks<00:23:09.539> of 00:23:10.010 --> 00:23:10.020 align:start position:0% days they support seven networks of 00:23:10.020 --> 00:23:11.630 align:start position:0% days they support seven networks of those<00:23:10.260> seven<00:23:10.440> networks<00:23:10.980> this<00:23:11.220> is<00:23:11.400> the 00:23:11.630 --> 00:23:11.640 align:start position:0% those seven networks this is the 00:23:11.640 --> 00:23:14.149 align:start position:0% those seven networks this is the performance<00:23:12.059> criteria<00:23:12.780> of<00:23:13.140> that<00:23:13.320> right<00:23:13.860> and 00:23:14.149 --> 00:23:14.159 align:start position:0% performance criteria of that right and 00:23:14.159 --> 00:23:16.010 align:start position:0% performance criteria of that right and all<00:23:14.340> of<00:23:14.460> that's<00:23:14.580> going<00:23:14.820> to<00:23:15.000> be<00:23:15.179> published<00:23:15.600> in<00:23:15.900> a 00:23:16.010 --> 00:23:16.020 align:start position:0% all of that's going to be published in a 00:23:16.020 --> 00:23:18.409 align:start position:0% all of that's going to be published in a stream<00:23:16.200> of<00:23:16.440> information<00:23:16.880> that<00:23:17.880> people<00:23:18.120> can 00:23:18.409 --> 00:23:18.419 align:start position:0% stream of information that people can 00:23:18.419 --> 00:23:20.870 align:start position:0% stream of information that people can consume<00:23:19.020> from<00:23:19.260> to<00:23:19.740> make<00:23:19.919> routing<00:23:20.460> decisions 00:23:20.870 --> 00:23:20.880 align:start position:0% consume from to make routing decisions 00:23:20.880 --> 00:23:24.590 align:start position:0% consume from to make routing decisions so<00:23:21.480> a<00:23:21.720> user<00:23:22.140> can<00:23:22.740> like<00:23:23.280> a<00:23:23.400> very<00:23:23.820> technical<00:23:24.120> user 00:23:24.590 --> 00:23:24.600 align:start position:0% so a user can like a very technical user 00:23:24.600 --> 00:23:26.630 align:start position:0% so a user can like a very technical user that<00:23:24.840> wants<00:23:25.260> to<00:23:25.320> be<00:23:25.440> in<00:23:25.620> control<00:23:25.799> of<00:23:26.100> that<00:23:26.280> can 00:23:26.630 --> 00:23:26.640 align:start position:0% that wants to be in control of that can 00:23:26.640 --> 00:23:28.909 align:start position:0% that wants to be in control of that can say<00:23:26.940> this<00:23:27.900> provider<00:23:28.260> is<00:23:28.320> coming<00:23:28.500> from<00:23:28.740> this 00:23:28.909 --> 00:23:28.919 align:start position:0% say this provider is coming from this 00:23:28.919 --> 00:23:30.529 align:start position:0% say this provider is coming from this region<00:23:29.280> or<00:23:29.520> this<00:23:29.640> providers<00:23:30.059> coming<00:23:30.360> from 00:23:30.529 --> 00:23:30.539 align:start position:0% region or this providers coming from 00:23:30.539 --> 00:23:31.730 align:start position:0% region or this providers coming from that<00:23:30.720> region<00:23:31.080> and<00:23:31.260> this<00:23:31.440> is<00:23:31.559> their 00:23:31.730 --> 00:23:31.740 align:start position:0% that region and this is their 00:23:31.740 --> 00:23:33.529 align:start position:0% that region and this is their performance<00:23:32.100> and<00:23:32.400> make<00:23:32.580> selection<00:23:33.000> criteria 00:23:33.529 --> 00:23:33.539 align:start position:0% performance and make selection criteria 00:23:33.539 --> 00:23:36.230 align:start position:0% performance and make selection criteria of<00:23:33.659> how<00:23:33.900> their<00:23:34.020> traffic<00:23:34.260> gets<00:23:34.620> routed<00:23:34.980> or<00:23:35.820> they 00:23:36.230 --> 00:23:36.240 align:start position:0% of how their traffic gets routed or they 00:23:36.240 --> 00:23:38.149 align:start position:0% of how their traffic gets routed or they can<00:23:36.419> pick<00:23:36.840> their<00:23:37.140> level<00:23:37.260> of<00:23:37.500> decentralization 00:23:38.149 --> 00:23:38.159 align:start position:0% can pick their level of decentralization 00:23:38.159 --> 00:23:40.490 align:start position:0% can pick their level of decentralization and<00:23:38.460> ease<00:23:38.640> of<00:23:38.700> of<00:23:39.120> years<00:23:39.299> by<00:23:39.840> going<00:23:40.080> through<00:23:40.260> an 00:23:40.490 --> 00:23:40.500 align:start position:0% and ease of of years by going through an 00:23:40.500 --> 00:23:42.529 align:start position:0% and ease of of years by going through an Ingress<00:23:40.799> operator<00:23:41.280> that<00:23:41.940> can<00:23:42.120> make<00:23:42.299> those 00:23:42.529 --> 00:23:42.539 align:start position:0% Ingress operator that can make those 00:23:42.539 --> 00:23:44.810 align:start position:0% Ingress operator that can make those routing<00:23:42.960> decisions<00:23:43.380> on<00:23:43.679> their<00:23:43.799> behalf 00:23:44.810 --> 00:23:44.820 align:start position:0% routing decisions on their behalf 00:23:44.820 --> 00:23:48.230 align:start position:0% routing decisions on their behalf can<00:23:45.360> you<00:23:45.840> um<00:23:45.840> give<00:23:46.380> an<00:23:47.100> example<00:23:47.400> of<00:23:47.640> what<00:23:48.120> the 00:23:48.230 --> 00:23:48.240 align:start position:0% can you um give an example of what the 00:23:48.240 --> 00:23:49.549 align:start position:0% can you um give an example of what the centralized<00:23:48.659> infrastructure<00:23:49.200> currently 00:23:49.549 --> 00:23:49.559 align:start position:0% centralized infrastructure currently 00:23:49.559 --> 00:23:51.649 align:start position:0% centralized infrastructure currently looks<00:23:49.799> like<00:23:49.860> in<00:23:50.159> terms<00:23:50.340> of<00:23:50.400> like<00:23:50.640> number<00:23:51.480> of 00:23:51.649 --> 00:23:51.659 align:start position:0% looks like in terms of like number of 00:23:51.659 --> 00:23:53.750 align:start position:0% looks like in terms of like number of servers<00:23:52.080> and<00:23:52.260> bandwidth<00:23:52.799> and<00:23:52.980> so<00:23:53.100> on<00:23:53.220> and<00:23:53.520> what 00:23:53.750 --> 00:23:53.760 align:start position:0% servers and bandwidth and so on and what 00:23:53.760 --> 00:23:55.010 align:start position:0% servers and bandwidth and so on and what you<00:23:53.880> expect<00:23:54.120> will<00:23:54.480> be<00:23:54.659> when<00:23:54.900> it's 00:23:55.010 --> 00:23:55.020 align:start position:0% you expect will be when it's 00:23:55.020 --> 00:23:56.510 align:start position:0% you expect will be when it's decentralized<00:23:55.679> will<00:23:55.860> there<00:23:56.039> be<00:23:56.159> overhead 00:23:56.510 --> 00:23:56.520 align:start position:0% decentralized will there be overhead 00:23:56.520 --> 00:23:59.149 align:start position:0% decentralized will there be overhead will<00:23:56.820> it<00:23:57.000> will<00:23:57.360> it<00:23:57.480> need<00:23:57.659> more<00:23:57.900> servers<00:23:58.380> to<00:23:58.559> do 00:23:59.149 --> 00:23:59.159 align:start position:0% will it will it need more servers to do 00:23:59.159 --> 00:24:00.890 align:start position:0% will it will it need more servers to do the<00:23:59.340> same<00:23:59.460> performance<00:23:59.880> that<00:24:00.120> kind<00:24:00.299> of<00:24:00.419> thing 00:24:00.890 --> 00:24:00.900 align:start position:0% the same performance that kind of thing 00:24:00.900 --> 00:24:02.750 align:start position:0% the same performance that kind of thing by<00:24:01.740> number<00:24:01.919> of<00:24:02.039> servers<00:24:02.400> are<00:24:02.520> you<00:24:02.640> talking 00:24:02.750 --> 00:24:02.760 align:start position:0% by number of servers are you talking 00:24:02.760 --> 00:24:06.230 align:start position:0% by number of servers are you talking about<00:24:02.880> inference<00:24:03.600> current<00:24:03.840> current<00:24:04.500> yeah 00:24:06.230 --> 00:24:06.240 align:start position:0% about inference current current yeah 00:24:06.240 --> 00:24:09.470 align:start position:0% about inference current current yeah um dozens<00:24:07.140> of<00:24:07.440> subsystems<00:24:08.400> hundreds<00:24:09.240> of 00:24:09.470 --> 00:24:09.480 align:start position:0% um dozens of subsystems hundreds of 00:24:09.480 --> 00:24:12.649 align:start position:0% um dozens of subsystems hundreds of different<00:24:10.140> instances<00:24:10.919> or<00:24:11.340> servers<00:24:11.940> providing 00:24:12.649 --> 00:24:12.659 align:start position:0% different instances or servers providing 00:24:12.659 --> 00:24:14.810 align:start position:0% different instances or servers providing different<00:24:12.900> types<00:24:13.320> of<00:24:13.440> functionality<00:24:14.100> so<00:24:14.640> like 00:24:14.810 --> 00:24:14.820 align:start position:0% different types of functionality so like 00:24:14.820 --> 00:24:16.909 align:start position:0% different types of functionality so like we<00:24:15.000> have<00:24:15.120> a<00:24:15.299> separate<00:24:15.539> subsystem<00:24:16.080> subsystem 00:24:16.909 --> 00:24:16.919 align:start position:0% we have a separate subsystem subsystem 00:24:16.919 --> 00:24:20.270 align:start position:0% we have a separate subsystem subsystem that<00:24:17.280> all<00:24:17.460> it<00:24:17.640> does<00:24:17.820> is<00:24:18.120> index<00:24:18.900> event<00:24:19.140> logs<00:24:19.740> and 00:24:20.270 --> 00:24:20.280 align:start position:0% that all it does is index event logs and 00:24:20.280 --> 00:24:24.529 align:start position:0% that all it does is index event logs and when<00:24:20.520> you<00:24:20.880> query<00:24:21.659> events<00:24:22.320> from<00:24:22.679> uh<00:24:23.520> like<00:24:23.700> erc20 00:24:24.529 --> 00:24:24.539 align:start position:0% when you query events from uh like erc20 00:24:24.539 --> 00:24:26.510 align:start position:0% when you query events from uh like erc20 token<00:24:25.080> events<00:24:25.380> and<00:24:25.559> things<00:24:25.740> like<00:24:26.039> that<00:24:26.220> it's 00:24:26.510 --> 00:24:26.520 align:start position:0% token events and things like that it's 00:24:26.520 --> 00:24:28.250 align:start position:0% token events and things like that it's pulling<00:24:26.880> from<00:24:27.000> that<00:24:27.240> subsystem<00:24:27.659> and<00:24:28.020> then<00:24:28.140> we 00:24:28.250 --> 00:24:28.260 align:start position:0% pulling from that subsystem and then we 00:24:28.260 --> 00:24:29.930 align:start position:0% pulling from that subsystem and then we have<00:24:28.380> this<00:24:28.620> consistency<00:24:29.100> system<00:24:29.460> that<00:24:29.700> tries 00:24:29.930 --> 00:24:29.940 align:start position:0% have this consistency system that tries 00:24:29.940 --> 00:24:32.090 align:start position:0% have this consistency system that tries to<00:24:30.000> keep<00:24:30.179> all<00:24:30.299> of<00:24:30.480> that<00:24:30.659> in<00:24:31.500> sync<00:24:31.799> when<00:24:31.980> you're 00:24:32.090 --> 00:24:32.100 align:start position:0% to keep all of that in sync when you're 00:24:32.100 --> 00:24:34.970 align:start position:0% to keep all of that in sync when you're querying<00:24:32.520> one<00:24:32.760> subsystem<00:24:33.299> versus<00:24:33.600> another 00:24:34.970 --> 00:24:34.980 align:start position:0% querying one subsystem versus another 00:24:34.980 --> 00:24:36.649 align:start position:0% querying one subsystem versus another um<00:24:35.100> so<00:24:35.340> that's<00:24:35.640> the<00:24:35.880> challenge<00:24:36.120> that<00:24:36.480> we've 00:24:36.649 --> 00:24:36.659 align:start position:0% um so that's the challenge that we've 00:24:36.659 --> 00:24:38.750 align:start position:0% um so that's the challenge that we've had<00:24:36.900> is<00:24:37.260> we<00:24:37.620> built<00:24:37.980> that<00:24:38.100> as<00:24:38.340> quickly<00:24:38.640> as 00:24:38.750 --> 00:24:38.760 align:start position:0% had is we built that as quickly as 00:24:38.760 --> 00:24:40.490 align:start position:0% had is we built that as quickly as possible<00:24:39.059> to<00:24:39.299> solve<00:24:39.600> problems<00:24:39.960> and<00:24:40.140> it's<00:24:40.320> very 00:24:40.490 --> 00:24:40.500 align:start position:0% possible to solve problems and it's very 00:24:40.500 --> 00:24:43.490 align:start position:0% possible to solve problems and it's very proprietary<00:24:41.220> Cloud<00:24:42.059> specific<00:24:42.659> and<00:24:43.260> we've 00:24:43.490 --> 00:24:43.500 align:start position:0% proprietary Cloud specific and we've 00:24:43.500 --> 00:24:46.310 align:start position:0% proprietary Cloud specific and we've been<00:24:43.620> working<00:24:43.860> on<00:24:44.159> how<00:24:44.520> do<00:24:44.700> we<00:24:44.880> retool<00:24:45.659> that<00:24:45.840> so 00:24:46.310 --> 00:24:46.320 align:start position:0% been working on how do we retool that so 00:24:46.320 --> 00:24:47.930 align:start position:0% been working on how do we retool that so that<00:24:46.559> it's<00:24:46.799> something<00:24:47.039> that<00:24:47.220> can<00:24:47.400> be<00:24:47.460> not<00:24:47.760> just 00:24:47.930 --> 00:24:47.940 align:start position:0% that it's something that can be not just 00:24:47.940 --> 00:24:49.610 align:start position:0% that it's something that can be not just open<00:24:48.179> source<00:24:48.720> and<00:24:48.900> something<00:24:49.260> that<00:24:49.440> somebody 00:24:49.610 --> 00:24:49.620 align:start position:0% open source and something that somebody 00:24:49.620 --> 00:24:53.090 align:start position:0% open source and something that somebody else<00:24:49.919> can<00:24:50.100> run<00:24:50.340> but<00:24:50.880> can<00:24:51.120> run<00:24:51.480> with<00:24:52.020> like<00:24:52.260> not<00:24:52.799> a 00:24:53.090 --> 00:24:53.100 align:start position:0% else can run but can run with like not a 00:24:53.100 --> 00:24:56.510 align:start position:0% else can run but can run with like not a team<00:24:53.280> of<00:24:53.640> dozens<00:24:54.059> of<00:24:54.720> operations<00:24:55.260> people<00:24:55.679> and 00:24:56.510 --> 00:24:56.520 align:start position:0% team of dozens of operations people and 00:24:56.520 --> 00:24:58.610 align:start position:0% team of dozens of operations people and so<00:24:57.059> it's<00:24:57.360> not<00:24:57.600> what<00:24:58.020> we're<00:24:58.200> going<00:24:58.380> to<00:24:58.500> release 00:24:58.610 --> 00:24:58.620 align:start position:0% so it's not what we're going to release 00:24:58.620 --> 00:25:00.830 align:start position:0% so it's not what we're going to release in<00:24:58.919> the<00:24:59.039> node<00:24:59.159> kit<00:24:59.520> is<00:24:59.700> what<00:24:59.880> we<00:25:00.000> think<00:25:00.120> is<00:25:00.360> an 00:25:00.830 --> 00:25:00.840 align:start position:0% in the node kit is what we think is an 00:25:00.840 --> 00:25:03.350 align:start position:0% in the node kit is what we think is an minimum<00:25:01.679> level<00:25:01.860> of<00:25:02.159> functionality<00:25:02.760> of 00:25:03.350 --> 00:25:03.360 align:start position:0% minimum level of functionality of 00:25:03.360 --> 00:25:05.990 align:start position:0% minimum level of functionality of performance<00:25:03.900> where<00:25:04.380> this<00:25:04.799> is<00:25:05.039> better<00:25:05.400> than 00:25:05.990 --> 00:25:06.000 align:start position:0% performance where this is better than 00:25:06.000 --> 00:25:07.909 align:start position:0% performance where this is better than running<00:25:06.360> a<00:25:06.780> bunch<00:25:06.900> of<00:25:07.020> nodes<00:25:07.260> behind<00:25:07.620> a<00:25:07.679> load 00:25:07.909 --> 00:25:07.919 align:start position:0% running a bunch of nodes behind a load 00:25:07.919 --> 00:25:09.169 align:start position:0% running a bunch of nodes behind a load balancer<00:25:08.220> because<00:25:08.400> it<00:25:08.520> now<00:25:08.640> has<00:25:08.820> some<00:25:09.000> of 00:25:09.169 --> 00:25:09.179 align:start position:0% balancer because it now has some of 00:25:09.179 --> 00:25:10.909 align:start position:0% balancer because it now has some of these<00:25:09.360> indexing<00:25:09.900> and<00:25:10.260> performance 00:25:10.909 --> 00:25:10.919 align:start position:0% these indexing and performance 00:25:10.919 --> 00:25:12.890 align:start position:0% these indexing and performance optimizing<00:25:11.580> systems<00:25:12.059> but<00:25:12.480> it's<00:25:12.659> something 00:25:12.890 --> 00:25:12.900 align:start position:0% optimizing systems but it's something 00:25:12.900 --> 00:25:14.990 align:start position:0% optimizing systems but it's something that<00:25:13.080> can<00:25:13.260> be<00:25:13.380> taken<00:25:13.740> on<00:25:13.860> by<00:25:14.460> hopefully<00:25:14.820> an 00:25:14.990 --> 00:25:15.000 align:start position:0% that can be taken on by hopefully an 00:25:15.000 --> 00:25:16.730 align:start position:0% that can be taken on by hopefully an individual<00:25:15.419> but 00:25:16.730 --> 00:25:16.740 align:start position:0% individual but 00:25:16.740 --> 00:25:18.470 align:start position:0% individual but um at<00:25:17.100> the<00:25:17.159> very<00:25:17.280> least<00:25:17.460> a<00:25:17.760> small<00:25:17.940> team<00:25:18.179> much 00:25:18.470 --> 00:25:18.480 align:start position:0% um at the very least a small team much 00:25:18.480 --> 00:25:20.210 align:start position:0% um at the very least a small team much smaller<00:25:18.900> team<00:25:19.020> than<00:25:19.320> the<00:25:19.559> current<00:25:19.740> inferior 00:25:20.210 --> 00:25:20.220 align:start position:0% smaller team than the current inferior 00:25:20.220 --> 00:25:21.409 align:start position:0% smaller team than the current inferior team 00:25:21.409 --> 00:25:21.419 align:start position:0% team 00:25:21.419 --> 00:25:25.250 align:start position:0% team do<00:25:21.840> you<00:25:22.020> think<00:25:22.260> it's<00:25:22.559> uh<00:25:23.039> likely<00:25:23.640> that<00:25:24.260> this 00:25:25.250 --> 00:25:25.260 align:start position:0% do you think it's uh likely that this 00:25:25.260 --> 00:25:27.950 align:start position:0% do you think it's uh likely that this unchain<00:25:25.860> registrations<00:25:26.700> of<00:25:27.240> the<00:25:27.419> providers 00:25:27.950 --> 00:25:27.960 align:start position:0% unchain registrations of the providers 00:25:27.960 --> 00:25:30.110 align:start position:0% unchain registrations of the providers will<00:25:28.500> be<00:25:28.740> a<00:25:29.100> new<00:25:29.220> yet<00:25:29.520> to<00:25:29.700> be<00:25:29.820> launched 00:25:30.110 --> 00:25:30.120 align:start position:0% will be a new yet to be launched 00:25:30.120 --> 00:25:32.029 align:start position:0% will be a new yet to be launched dedicated<00:25:30.539> chain<00:25:30.840> or<00:25:31.320> is<00:25:31.440> it<00:25:31.559> more<00:25:31.740> likely 00:25:32.029 --> 00:25:32.039 align:start position:0% dedicated chain or is it more likely 00:25:32.039 --> 00:25:33.409 align:start position:0% dedicated chain or is it more likely that<00:25:32.220> it<00:25:32.340> will<00:25:32.460> be<00:25:32.580> on<00:25:32.700> an<00:25:32.820> existing<00:25:33.240> chain 00:25:33.409 --> 00:25:33.419 align:start position:0% that it will be on an existing chain 00:25:33.419 --> 00:25:35.630 align:start position:0% that it will be on an existing chain like<00:25:33.659> this<00:25:33.779> you<00:25:34.080> remain<00:25:34.320> at 00:25:35.630 --> 00:25:35.640 align:start position:0% like this you remain at 00:25:35.640 --> 00:25:37.610 align:start position:0% like this you remain at uh<00:25:36.539> that's<00:25:36.779> one<00:25:36.960> of<00:25:37.080> the<00:25:37.140> things<00:25:37.320> that<00:25:37.440> we've 00:25:37.610 --> 00:25:37.620 align:start position:0% uh that's one of the things that we've 00:25:37.620 --> 00:25:39.950 align:start position:0% uh that's one of the things that we've been<00:25:37.740> considering<00:25:38.480> as<00:25:39.480> we're<00:25:39.600> going<00:25:39.779> through 00:25:39.950 --> 00:25:39.960 align:start position:0% been considering as we're going through 00:25:39.960 --> 00:25:42.529 align:start position:0% been considering as we're going through the<00:25:40.080> design<00:25:40.320> we're<00:25:40.860> leaning<00:25:41.220> towards<00:25:41.640> don't 00:25:42.529 --> 00:25:42.539 align:start position:0% the design we're leaning towards don't 00:25:42.539 --> 00:25:44.930 align:start position:0% the design we're leaning towards don't don't<00:25:43.140> start<00:25:43.500> a<00:25:43.679> new<00:25:43.860> chain<00:25:44.039> for<00:25:44.340> that<00:25:44.460> like 00:25:44.930 --> 00:25:44.940 align:start position:0% don't start a new chain for that like 00:25:44.940 --> 00:25:47.090 align:start position:0% don't start a new chain for that like try<00:25:45.240> to<00:25:45.419> use<00:25:45.600> something<00:25:45.960> that<00:25:46.320> exists<00:25:46.799> and 00:25:47.090 --> 00:25:47.100 align:start position:0% try to use something that exists and 00:25:47.100 --> 00:25:49.070 align:start position:0% try to use something that exists and that<00:25:47.400> goes<00:25:47.640> back<00:25:47.760> to<00:25:47.940> the<00:25:48.179> why<00:25:48.720> are<00:25:48.840> we<00:25:48.960> doing 00:25:49.070 --> 00:25:49.080 align:start position:0% that goes back to the why are we doing 00:25:49.080 --> 00:25:52.010 align:start position:0% that goes back to the why are we doing it<00:25:49.320> now<00:25:49.559> rather<00:25:49.980> than<00:25:50.100> in<00:25:50.400> 2016<00:25:50.940> when<00:25:51.840> people 00:25:52.010 --> 00:25:52.020 align:start position:0% it now rather than in 2016 when people 00:25:52.020 --> 00:25:53.450 align:start position:0% it now rather than in 2016 when people are<00:25:52.200> talking<00:25:52.320> about<00:25:52.440> like<00:25:52.679> micro<00:25:52.919> payments 00:25:53.450 --> 00:25:53.460 align:start position:0% are talking about like micro payments 00:25:53.460 --> 00:25:55.549 align:start position:0% are talking about like micro payments between<00:25:53.880> providers<00:25:54.539> and<00:25:54.840> like<00:25:54.960> you<00:25:55.140> use<00:25:55.320> State 00:25:55.549 --> 00:25:55.559 align:start position:0% between providers and like you use State 00:25:55.559 --> 00:25:57.049 align:start position:0% between providers and like you use State channels<00:25:55.980> for<00:25:56.159> that<00:25:56.340> and<00:25:56.580> all<00:25:56.760> these<00:25:56.940> other 00:25:57.049 --> 00:25:57.059 align:start position:0% channels for that and all these other 00:25:57.059 --> 00:25:59.090 align:start position:0% channels for that and all these other things<00:25:57.240> like<00:25:57.600> we<00:25:58.200> would<00:25:58.380> have<00:25:58.500> had<00:25:58.679> to<00:25:58.860> develop 00:25:59.090 --> 00:25:59.100 align:start position:0% things like we would have had to develop 00:25:59.100 --> 00:26:00.409 align:start position:0% things like we would have had to develop a<00:25:59.279> significant<00:25:59.580> amount<00:25:59.760> of<00:25:59.880> our<00:26:00.059> research 00:26:00.409 --> 00:26:00.419 align:start position:0% a significant amount of our research 00:26:00.419 --> 00:26:02.630 align:start position:0% a significant amount of our research just<00:26:00.840> on<00:26:01.020> that<00:26:01.320> problem<00:26:01.500> whereas<00:26:02.100> now<00:26:02.279> a<00:26:02.580> lot 00:26:02.630 --> 00:26:02.640 align:start position:0% just on that problem whereas now a lot 00:26:02.640 --> 00:26:04.730 align:start position:0% just on that problem whereas now a lot of<00:26:02.760> these<00:26:02.940> Primitives<00:26:03.360> are<00:26:03.720> out<00:26:03.900> there<00:26:04.080> and<00:26:04.559> we 00:26:04.730 --> 00:26:04.740 align:start position:0% of these Primitives are out there and we 00:26:04.740 --> 00:26:06.049 align:start position:0% of these Primitives are out there and we can<00:26:04.860> try<00:26:05.039> to<00:26:05.159> use<00:26:05.279> some<00:26:05.520> of<00:26:05.640> the<00:26:05.700> things<00:26:05.880> that 00:26:06.049 --> 00:26:06.059 align:start position:0% can try to use some of the things that 00:26:06.059 --> 00:26:08.390 align:start position:0% can try to use some of the things that already<00:26:06.240> exist<00:26:06.720> to<00:26:07.020> build<00:26:07.140> the<00:26:07.320> network<00:26:07.559> uh 00:26:08.390 --> 00:26:08.400 align:start position:0% already exist to build the network uh 00:26:08.400 --> 00:26:11.450 align:start position:0% already exist to build the network uh yeah<00:26:08.520> can<00:26:08.820> you<00:26:09.000> tell<00:26:09.120> me<00:26:09.240> who<00:26:10.020> is<00:26:10.500> the<00:26:11.159> entity 00:26:11.450 --> 00:26:11.460 align:start position:0% yeah can you tell me who is the entity 00:26:11.460 --> 00:26:13.310 align:start position:0% yeah can you tell me who is the entity or<00:26:11.700> people<00:26:11.880> who<00:26:12.120> decide<00:26:12.480> what<00:26:13.140> the 00:26:13.310 --> 00:26:13.320 align:start position:0% or people who decide what the 00:26:13.320 --> 00:26:16.090 align:start position:0% or people who decide what the requirements<00:26:13.919> are<00:26:14.039> to<00:26:14.460> become<00:26:14.820> an<00:26:15.779> operator 00:26:16.090 --> 00:26:16.100 align:start position:0% requirements are to become an operator 00:26:16.100 --> 00:26:20.330 align:start position:0% requirements are to become an operator and<00:26:17.419> who<00:26:18.419> decides<00:26:18.900> which<00:26:19.440> operators<00:26:20.039> or 00:26:20.330 --> 00:26:20.340 align:start position:0% and who decides which operators or 00:26:20.340 --> 00:26:22.490 align:start position:0% and who decides which operators or providers<00:26:20.760> would<00:26:21.179> meet<00:26:21.659> those<00:26:21.960> requirements 00:26:22.490 --> 00:26:22.500 align:start position:0% providers would meet those requirements 00:26:22.500 --> 00:26:23.990 align:start position:0% providers would meet those requirements and<00:26:22.799> then<00:26:22.919> how<00:26:23.159> they<00:26:23.340> would<00:26:23.460> change<00:26:23.640> in<00:26:23.820> the 00:26:23.990 --> 00:26:24.000 align:start position:0% and then how they would change in the 00:26:24.000 --> 00:26:24.710 align:start position:0% and then how they would change in the future 00:26:24.710 --> 00:26:24.720 align:start position:0% future 00:26:24.720 --> 00:26:27.890 align:start position:0% future okay<00:26:25.320> so<00:26:25.679> multi-part<00:26:26.279> so<00:26:26.760> who<00:26:27.059> decides<00:26:27.659> who 00:26:27.890 --> 00:26:27.900 align:start position:0% okay so multi-part so who decides who 00:26:27.900 --> 00:26:30.110 align:start position:0% okay so multi-part so who decides who can<00:26:28.020> be<00:26:28.140> an<00:26:28.320> operator<00:26:28.740> so<00:26:29.220> this<00:26:29.460> form<00:26:29.700> to<00:26:29.940> sign 00:26:30.110 --> 00:26:30.120 align:start position:0% can be an operator so this form to sign 00:26:30.120 --> 00:26:32.210 align:start position:0% can be an operator so this form to sign up<00:26:30.299> is<00:26:30.480> to<00:26:30.659> participate<00:26:31.559> in<00:26:31.860> like<00:26:32.039> a 00:26:32.210 --> 00:26:32.220 align:start position:0% up is to participate in like a 00:26:32.220 --> 00:26:35.090 align:start position:0% up is to participate in like a permission<00:26:32.520> beta<00:26:33.600> um<00:26:33.659> similarly<00:26:34.080> to<00:26:34.380> like<00:26:34.620> how 00:26:35.090 --> 00:26:35.100 align:start position:0% permission beta um similarly to like how 00:26:35.100 --> 00:26:37.789 align:start position:0% permission beta um similarly to like how uh<00:26:35.640> when<00:26:36.000> other<00:26:36.179> people<00:26:36.360> are<00:26:36.600> uh<00:26:37.320> developing 00:26:37.789 --> 00:26:37.799 align:start position:0% uh when other people are uh developing 00:26:37.799 --> 00:26:39.710 align:start position:0% uh when other people are uh developing new<00:26:37.980> networks<00:26:38.520> we're<00:26:38.940> going<00:26:39.179> to<00:26:39.360> have<00:26:39.539> to 00:26:39.710 --> 00:26:39.720 align:start position:0% new networks we're going to have to 00:26:39.720 --> 00:26:41.330 align:start position:0% new networks we're going to have to start<00:26:39.900> with<00:26:40.080> a<00:26:40.260> small<00:26:40.380> group<00:26:40.620> to<00:26:40.919> try<00:26:41.039> to<00:26:41.159> test 00:26:41.330 --> 00:26:41.340 align:start position:0% start with a small group to try to test 00:26:41.340 --> 00:26:43.370 align:start position:0% start with a small group to try to test and<00:26:41.580> iterate<00:26:41.940> iterate<00:26:42.480> with<00:26:42.659> and<00:26:43.080> for<00:26:43.200> that 00:26:43.370 --> 00:26:43.380 align:start position:0% and iterate iterate with and for that 00:26:43.380 --> 00:26:44.630 align:start position:0% and iterate iterate with and for that we're<00:26:43.500> looking<00:26:43.679> for<00:26:43.919> people<00:26:44.220> that<00:26:44.460> already 00:26:44.630 --> 00:26:44.640 align:start position:0% we're looking for people that already 00:26:44.640 --> 00:26:47.090 align:start position:0% we're looking for people that already have<00:26:45.120> experience<00:26:45.720> with<00:26:46.380> the<00:26:46.559> infrastructure 00:26:47.090 --> 00:26:47.100 align:start position:0% have experience with the infrastructure 00:26:47.100 --> 00:26:49.250 align:start position:0% have experience with the infrastructure and<00:26:47.460> that<00:26:47.760> we<00:26:47.880> can<00:26:48.000> reach<00:26:48.240> out<00:26:48.360> to<00:26:48.539> and<00:26:48.960> get 00:26:49.250 --> 00:26:49.260 align:start position:0% and that we can reach out to and get 00:26:49.260 --> 00:26:50.990 align:start position:0% and that we can reach out to and get feedback<00:26:49.679> from 00:26:50.990 --> 00:26:51.000 align:start position:0% feedback from 00:26:51.000 --> 00:26:52.669 align:start position:0% feedback from um<00:26:51.120> pretty<00:26:51.419> quickly<00:26:51.779> on<00:26:52.020> the<00:26:52.140> technical<00:26:52.440> front 00:26:52.669 --> 00:26:52.679 align:start position:0% um pretty quickly on the technical front 00:26:52.679 --> 00:26:54.649 align:start position:0% um pretty quickly on the technical front but<00:26:53.159> once<00:26:53.460> we<00:26:53.640> actually<00:26:53.760> launch<00:26:54.179> this<00:26:54.480> network 00:26:54.649 --> 00:26:54.659 align:start position:0% but once we actually launch this network 00:26:54.659 --> 00:26:57.289 align:start position:0% but once we actually launch this network it's<00:26:54.960> fully<00:26:55.260> permissionless<00:26:55.799> the<00:26:56.700> criteria 00:26:57.289 --> 00:26:57.299 align:start position:0% it's fully permissionless the criteria 00:26:57.299 --> 00:26:58.909 align:start position:0% it's fully permissionless the criteria of<00:26:57.480> that<00:26:57.600> is<00:26:57.840> what<00:26:58.020> we're<00:26:58.140> defining<00:26:58.559> as<00:26:58.740> a 00:26:58.909 --> 00:26:58.919 align:start position:0% of that is what we're defining as a 00:26:58.919 --> 00:27:01.909 align:start position:0% of that is what we're defining as a protocol<00:26:59.220> in<00:26:59.880> the<00:27:00.059> design<00:27:00.240> of<00:27:00.840> this<00:27:01.500> would<00:27:01.740> be 00:27:01.909 --> 00:27:01.919 align:start position:0% protocol in the design of this would be 00:27:01.919 --> 00:27:04.730 align:start position:0% protocol in the design of this would be you<00:27:02.400> know<00:27:02.520> the<00:27:03.000> amount<00:27:03.299> of<00:27:03.659> resources<00:27:04.500> that 00:27:04.730 --> 00:27:04.740 align:start position:0% you know the amount of resources that 00:27:04.740 --> 00:27:06.649 align:start position:0% you know the amount of resources that you<00:27:04.860> would<00:27:04.980> have<00:27:05.159> to<00:27:05.279> provide<00:27:05.580> or<00:27:06.179> this<00:27:06.419> would 00:27:06.649 --> 00:27:06.659 align:start position:0% you would have to provide or this would 00:27:06.659 --> 00:27:08.570 align:start position:0% you would have to provide or this would be<00:27:06.900> the<00:27:07.320> minimum<00:27:07.559> level<00:27:07.740> of<00:27:07.980> performance<00:27:08.400> so 00:27:08.570 --> 00:27:08.580 align:start position:0% be the minimum level of performance so 00:27:08.580 --> 00:27:10.549 align:start position:0% be the minimum level of performance so you<00:27:08.820> have<00:27:09.000> to<00:27:09.179> at<00:27:09.600> least<00:27:09.659> support<00:27:10.020> one<00:27:10.320> network 00:27:10.549 --> 00:27:10.559 align:start position:0% you have to at least support one network 00:27:10.559 --> 00:27:12.409 align:start position:0% you have to at least support one network you<00:27:11.159> have<00:27:11.279> to<00:27:11.460> at<00:27:11.580> least<00:27:11.700> support<00:27:11.880> this<00:27:12.240> level 00:27:12.409 --> 00:27:12.419 align:start position:0% you have to at least support this level 00:27:12.419 --> 00:27:14.450 align:start position:0% you have to at least support this level of<00:27:12.659> performance<00:27:13.080> and<00:27:13.799> then<00:27:13.919> as<00:27:14.159> long<00:27:14.279> as<00:27:14.400> you 00:27:14.450 --> 00:27:14.460 align:start position:0% of performance and then as long as you 00:27:14.460 --> 00:27:17.870 align:start position:0% of performance and then as long as you can<00:27:14.580> meet<00:27:14.760> that<00:27:15.059> it's<00:27:16.140> um<00:27:16.200> anybody<00:27:17.159> hey 00:27:17.870 --> 00:27:17.880 align:start position:0% can meet that it's um anybody hey 00:27:17.880 --> 00:27:20.450 align:start position:0% can meet that it's um anybody hey Lefteris<00:27:18.659> here<00:27:18.840> I'm<00:27:19.200> from<00:27:19.380> Rocky<00:27:19.799> right<00:27:20.279> in 00:27:20.450 --> 00:27:20.460 align:start position:0% Lefteris here I'm from Rocky right in 00:27:20.460 --> 00:27:22.909 align:start position:0% Lefteris here I'm from Rocky right in front<00:27:20.580> of<00:27:20.700> you<00:27:20.840> I<00:27:21.840> just<00:27:22.020> wanted<00:27:22.200> to<00:27:22.500> ask<00:27:22.679> about 00:27:22.909 --> 00:27:22.919 align:start position:0% front of you I just wanted to ask about 00:27:22.919 --> 00:27:25.669 align:start position:0% front of you I just wanted to ask about the<00:27:23.220> Ingress<00:27:23.520> nodes<00:27:23.880> will<00:27:24.720> there<00:27:24.900> be<00:27:25.200> a 00:27:25.669 --> 00:27:25.679 align:start position:0% the Ingress nodes will there be a 00:27:25.679 --> 00:27:28.310 align:start position:0% the Ingress nodes will there be a requirement<00:27:26.220> or<00:27:26.700> will<00:27:26.880> they<00:27:27.059> be<00:27:27.240> optional 00:27:28.310 --> 00:27:28.320 align:start position:0% requirement or will they be optional 00:27:28.320 --> 00:27:30.590 align:start position:0% requirement or will they be optional you<00:27:29.100> should<00:27:29.279> say<00:27:29.400> like<00:27:29.580> the<00:27:29.760> indexing<00:27:30.179> notes 00:27:30.590 --> 00:27:30.600 align:start position:0% you should say like the indexing notes 00:27:30.600 --> 00:27:33.230 align:start position:0% you should say like the indexing notes no<00:27:31.020> no<00:27:31.200> Ingrid<00:27:31.740> at<00:27:32.039> the<00:27:32.159> end<00:27:32.220> grass<00:27:32.580> yeah<00:27:32.880> it'll 00:27:33.230 --> 00:27:33.240 align:start position:0% no no Ingrid at the end grass yeah it'll 00:27:33.240 --> 00:27:35.450 align:start position:0% no no Ingrid at the end grass yeah it'll definitely<00:27:33.539> be<00:27:33.840> optional<00:27:34.799> um<00:27:34.860> so<00:27:35.100> I<00:27:35.340> can't 00:27:35.450 --> 00:27:35.460 align:start position:0% definitely be optional um so I can't 00:27:35.460 --> 00:27:36.830 align:start position:0% definitely be optional um so I can't quite<00:27:35.760> get<00:27:35.880> to<00:27:36.000> the<00:27:36.120> slides<00:27:36.360> it'll<00:27:36.600> take<00:27:36.659> too 00:27:36.830 --> 00:27:36.840 align:start position:0% quite get to the slides it'll take too 00:27:36.840 --> 00:27:39.110 align:start position:0% quite get to the slides it'll take too long<00:27:36.960> uh<00:27:37.620> but<00:27:37.740> you<00:27:38.220> can<00:27:38.340> still<00:27:38.580> have<00:27:38.880> a 00:27:39.110 --> 00:27:39.120 align:start position:0% long uh but you can still have a 00:27:39.120 --> 00:27:40.909 align:start position:0% long uh but you can still have a consumer<00:27:39.600> who<00:27:39.840> will<00:27:39.960> go<00:27:40.140> directly<00:27:40.500> to<00:27:40.740> the 00:27:40.909 --> 00:27:40.919 align:start position:0% consumer who will go directly to the 00:27:40.919 --> 00:27:43.130 align:start position:0% consumer who will go directly to the contract<00:27:41.340> to<00:27:41.520> purchase<00:27:41.820> resources<00:27:42.419> and<00:27:43.020> go 00:27:43.130 --> 00:27:43.140 align:start position:0% contract to purchase resources and go 00:27:43.140 --> 00:27:44.390 align:start position:0% contract to purchase resources and go directly<00:27:43.440> to<00:27:43.620> one<00:27:43.740> or<00:27:43.919> multiple<00:27:44.159> node 00:27:44.390 --> 00:27:44.400 align:start position:0% directly to one or multiple node 00:27:44.400 --> 00:27:46.370 align:start position:0% directly to one or multiple node providers<00:27:44.760> that<00:27:45.000> they<00:27:45.179> choose<00:27:45.419> the<00:27:46.080> Ingress 00:27:46.370 --> 00:27:46.380 align:start position:0% providers that they choose the Ingress 00:27:46.380 --> 00:27:48.169 align:start position:0% providers that they choose the Ingress node<00:27:46.740> is<00:27:46.919> kind<00:27:47.100> of<00:27:47.159> an<00:27:47.279> option<00:27:47.640> where<00:27:47.880> if<00:27:48.120> you 00:27:48.169 --> 00:27:48.179 align:start position:0% node is kind of an option where if you 00:27:48.179 --> 00:27:49.430 align:start position:0% node is kind of an option where if you don't<00:27:48.299> want<00:27:48.419> to<00:27:48.539> go<00:27:48.659> to<00:27:48.779> the<00:27:48.900> trouble<00:27:49.080> of<00:27:49.320> doing 00:27:49.430 --> 00:27:49.440 align:start position:0% don't want to go to the trouble of doing 00:27:49.440 --> 00:27:51.230 align:start position:0% don't want to go to the trouble of doing that<00:27:49.679> maybe<00:27:49.980> you<00:27:50.220> want<00:27:50.340> to<00:27:50.520> use<00:27:50.880> one<00:27:51.059> that 00:27:51.230 --> 00:27:51.240 align:start position:0% that maybe you want to use one that 00:27:51.240 --> 00:27:52.669 align:start position:0% that maybe you want to use one that allows<00:27:51.480> you<00:27:51.539> to<00:27:51.659> pay<00:27:51.779> in<00:27:51.900> Fiat<00:27:52.260> that<00:27:52.500> you<00:27:52.620> can 00:27:52.669 --> 00:27:52.679 align:start position:0% allows you to pay in Fiat that you can 00:27:52.679 --> 00:27:57.110 align:start position:0% allows you to pay in Fiat that you can but<00:27:53.039> it's<00:27:53.159> an<00:27:53.520> option 00:27:57.110 --> 00:27:57.120 align:start position:0% 00:27:57.120 --> 00:28:00.110 align:start position:0% this<00:27:57.840> this<00:27:58.080> was<00:27:58.380> our<00:27:58.860> last<00:27:59.279> question<00:27:59.520> but<00:27:59.940> if 00:28:00.110 --> 00:28:00.120 align:start position:0% this this was our last question but if 00:28:00.120 --> 00:28:01.909 align:start position:0% this this was our last question but if you<00:28:00.240> have<00:28:00.419> more<00:28:00.659> questions<00:28:00.960> please<00:28:01.380> reach<00:28:01.860> out 00:28:01.909 --> 00:28:01.919 align:start position:0% you have more questions please reach out 00:28:01.919 --> 00:28:04.070 align:start position:0% you have more questions please reach out to<00:28:02.100> our<00:28:02.279> speakers<00:28:02.580> that<00:28:03.120> we're<00:28:03.480> going<00:28:03.659> are 00:28:04.070 --> 00:28:04.080 align:start position:0% to our speakers that we're going are 00:28:04.080 --> 00:28:08.539 align:start position:0% to our speakers that we're going are going<00:28:04.320> to<00:28:04.440> be<00:28:04.559> here<00:28:05.159> thank<00:28:06.120> you<00:28:06.240> so<00:28:06.419> much